NetFlow Fundamentals
Key Components
Type |
Definition |
||
---|---|---|---|
Flow Records |
A flow record defines the keys that NetFlow uses to identify packets and other fields of interest that NetFlow gathers for the flow. You can define a flow record with any combination of keys and fields of interest. Cisco NX-OS supports a rich set of keys. A flow record also defines the types of counters gathered per flow. You can configure 32- or 64-bit packet or byte counters. The key fields are specified with the match keyword. The fields of interest and counters are specified under the collect keyword. Cisco NX-OS enables the following match fields as the defaults when you create a flow record:
|
||
Flow Monitors |
A flow monitor references the flow record and flow exporter. You apply a flow monitor to an interface. |
||
Flow Exporters |
A flow exporter contains network layer and transport layer details for the NetFlow export packet. You can configure the following information in a flow exporter:
Cisco NX-OS exports data to the NetFlow Collector whenever a timeout occurs. You can configure a flush cache timeout (using the flow timeout command) to flush the cache and force a flow export. |
||
Layer 2 NetFlow Keys |
You can define Layer 2 keys in flexible NetFlow records that you can use to capture flows in Layer 2 interfaces. The Layer 2 keys are as follows:
You can apply Layer 2 NetFlow to the following interfaces for the ingress direction:
|
||
NetFlow Output Interface |
The NetFlow output interface on Cisco Nexus switches have the following features:
|
![]() Note |
Cisco NX-OS supports the Version 9 export format. This format supports a more efficient network utilization than the older Version 5 export format and supports IPv6 and Layer 2 fields. In addition, the Version 9 export format supports the full 32-bit SNMP ifIndex values at the NetFlow Collector. |
![]() Note |
Cisco NX-OS supports stateful restarts for NetFlow. After a reboot, Cisco NX-OS applies the running configuration. The flow cache is not preserved across restarts, and packets that come to the software during restarts cannot be processed. |
Architecture
Cisco Nexus 9000 Series switches separate NetFlow processing into two layers:
-
The first layer supports per-packet visibility for line-rate traffic. Packets do not need to be sampled and statistically analyzed. Instead, the packets can be processed and aggregated at line rate.
-
The second layer enables the gathering of flows at scale. It can maintain hundreds of thousands of flows without losing any flows and periodically exports them to an external collector.
Types
From Cisco NX-OS Release 10.4(1)F, NetFlow consists of two types configurations:
Type |
Definition |
---|---|
Ingress Netflow |
Ingress NetFlow identifies packet flows for ingress IP packets and provides statistics based on the packet flows. Ingress NetFlow uses flows to provide statistics for accounting, network monitoring, and network planning. |
Egress Netflow |
Egress NetFlow identifies packet flows for outgoing IP packets and Layer 2 flows and provides statistics based on these packet flows. On Cisco Nexus Cloudscale 9000 switches, egress NetFlow uses ingress pipeline and ingress TCAM carving egr-netflow to record flow information egressing out of the switch. All parameters and restrictions of NetFlow such as flow records, flow exporters, and flow monitors are applicable to egress NetFlow. |