As an enterprise Administrator, at the Edge level, you can override the Netflow settings specified in the Profile by selecting the Enable Edge Override checkbox.


  1. From the SD-WAN Orchestrator, go to Configure > Edges.
  2. Select an Edge you want to override Netflow settings and click the icon under the Device column.
    The Device Setting page for the selected Edge appears.
  3. From the Configure Segment drop-down menu, select a profile segment to configure Netflow settings.
  4. Go to the Netflow Settings area and select the Enable Edge Override check box.
  5. Select the Netflow Enabled check box.
    At the edge level, the Observation ID field is auto-populated with 8 bits segment ID and 24 bits edge ID and it cannot be edited. The Observation ID is unique to an Exporting Process per segment per enterprise.
  6. Override the collector, filter, and Netflow export interval information specified in the Profile by referring to the Step 4 in Configure Netflow Settings for Profiles.
  7. From the Source Interface drop-down menu, select an Edge interface configured in the segment as the source interface, to choose the source IP for the NetFlow packets.

    Make sure you manually select the Edge’s non-WAN interface (Loopback Interfaces/ VLAN/Routed/Sub-Interface) with 'Advertise' flag enabled as the source interface. If none is selected, the Edge automatically selects a LAN interface, which is ‘UP’ and 'Advertise' enabled from the corresponding segment as the source interface for that collector. If the Edge doesn’t have interfaces which is ‘UP’ and 'Advertise' enabled, then the source interface will not be chosen and the Netflow packets will not be generated.


    When the Edge transmits the traffic, the packet header will have the IP address of the selected source interface, whereas the packets can be sent through any interface based on the destination route.

  8. Click Save Changes.


After you enable Netflow on the VMware SD-WAN Edge, it periodically sends messages to the configured collector. The contents of these messages are defined using IPFIX templates. For more information on templates, see IPFIX Templates.