Description | This article describes the process of migrating to a single configuration for NetFlow for a FortiGate running Muti-VDOMs environment. |
Scope | FortiGate with Mutli-VDOM enabled and NetFlow configured. |
Solution |
NetFlow Configured on multiple VDOMs:
FortiGate-60E (global) # diagnose test application sflowd 3 ===== Netflow Vdom Configuration ===== ____ vdom: root, index=0, is master, collector: disabled (use global config) (mgmt vdom) ____ vdom: Security, index=3, is master, collector: enabled ____ vdom: Sales, index=4, is master, collector: enabled
As seen in the above output, each VDOM has a unique collector and source IP address.
By unsetting each VDOMs NetFlow configuration they will take on the Global VDOM configuration:
FortiGate-60E # config vdom FortiGate-60E (vdom) # edit Security FortiGate-60E (Security) # config system vdom-netflow FortiGate-60E (vdom-netflow) # unset vdom-netflow FortiGate-60E (vdom-netflow) # end FortiGate-60E (Security) # next FortiGate-60E (vdom) # edit Sales FortiGate-60E (Sales) # config system vdom-netflow FortiGate-60E (vdom-netflow) # unset vdom-netflow FortiGate-60E (vdom-netflow) # end FortiGate-60E (Sales) # end FortiGate-60E # config global FortiGate-60E (global) # diagnose test application sflowd 3 ===== Netflow Vdom Configuration ===== ____ vdom: root, index=0, is master, collector: disabled (use global config) (mgmt vdom) ____ vdom: Security, index=3, is master, collector: disabled (use global config) ____ vdom: Sales, index=4, is master, collector: disabled (use global config) |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.