NetFlow is configured only in the ingress direction.

Netflow exporter packet does not transport support TCP.

A source interface or source address must be configured to enable the exporter. If you do not configure a source interface, the exporter remains in a disabled state. If both a source interface and a source address are configured, the source address takes precedence.

NetFlow supports export format Version 9 and IPFIX.

NetFlow filtering using ACL is not supported.

A valid record type such as IPv4, IPv6, or MPLS must be configured for every flow monitor map.

NetFlow is not supported on Bridge Virtual Interface (BVI).

Destination-based NetFlow accounting is not supported.

Output interface field is not updated in data and flow records when the traffic is routed through ACL-based forwarding (ABF).

The data and flow records for GRE transit traffic do not have the output interface, source, and destination prefix lengths fields set.

Full Packet Capture (FPC) feature is not supported.

We do not recommend using the management interface to export the NetFlow packets.

We do not recommend using the management interface to export the NetFlow packets.

If IPFIX 315 is enabled on a line card, then all the ports on that line card should have IPFIX315 configured.

IPFIX 315 is supported on main interface only. The traffic on all sub-interfaces (on which netflow is enabled) under the main interface is exported.

The incoming and outgoing interface will have information of main interface and not the sub-interface even if the packet is routed via sub-interface. Incase of bundles it will point to bundle main interface for IPFIX 315.

IPFIX 315 sampling rate for bundles is per member-link and not per bundle interface.

For IPFIX 315, the outgoing interface information may not be correct incase of packets that are multicasted or broadcasted on multiple ports.