Cisco Nexus 7000 Series NX-OS System Management Configuration Guide, Release 4.0 - Configuring NetFlow [Cisco Nexus 7000 Series Switches]

Table Of Contents

Configuring NetFlow

Information About NetFlow

NetFlow Overview

Flow Record Maps

Exporter Maps

Export Formats

Monitor Maps

Sampler Maps

High Availability

Virtualization Support

Licensing Requirements for NetFlow

Prerequisites for NetFlow

Configuration Guidelines and Limitations

Configuring NetFlow

Enabling the NetFlow Feature

Creating a Flow Record

Specifying the Match Parameters

Specifying the Collect Parameters

Creating a Flow Exporter

Creating a Flow Monitor

Creating a Sampler

Applying a Flow to an Interface

Configuring Bridged NetFlow on a VLAN

Configuring NetFlow Timeouts

Verifying NetFlow Configuration

NetFlow Example Configuration

Default Settings

Additional References

Related Documents

Standards

MIBs

Configuring NetFlow

This chapter describes how to configure the NetFlow feature for Cisco NX-OS.

This chapter includes the following sections:

•Information About NetFlow

•Licensing Requirements for NetFlow

•Prerequisites for NetFlow

•Configuration Guidelines and Limitations

•Configuring NetFlow

•Verifying NetFlow Configuration

•NetFlow Example Configuration

•Default Settings

•Additional References

Information About NetFlow

NetFlow identifies packet flows for both ingress and egress IP packets and provides statistics based on these packet flows. NetFlow does not require any change to either the packets themselves or to any networking device.

This section includes the following topics:

•NetFlow Overview

•High Availability

•Virtualization Support

NetFlow Overview

NetFlow uses flows to provide statistics for accounting, network monitoring, and network planning. A flow is a unidirectional stream of packets that arrives on a source interface (or VLAN), and has the same values for the keys. A key is an identified value for a field within the packet. You create a flow using a flow record map to define the unique keys for your flow. Cisco NX-OS supports Flexible NetFlow. You can use common keys, such as source and destination IP addresses, or define your own keys. For more information on the flow record maps, see the"Flow Record Maps" section.

All key values must match for the packet to count in a given flow. A flow might gather other fields of interest, depending on the export record version that you configure. Flows are stored in the NetFlow cache.

You can export the data that NetFlow gathers for your flow by using an export map and export this data to a remote NetFlow collector. Cisco NX-OS exports a flow as part of a NetFlow export User Datagram Protocol (UDP) datagram under the following circumstances:

•The flow has been inactive or active for too long.

•The flow cache is getting full.

•One of the counters (packets or bytes) has exceeded its maximum value.

•You have forced the flow to export.

For more information on exporter maps, see the "Exporter Maps" section.

You define the size of the data that you want to collect for a flow using a monitor map. The monitor map combines the flow record map and exporter map with the NetFlow cache information. For more information on monitor maps, see the "Monitor Maps" section.

Cisco NX-OS can gather NetFlow statistics in either full or sampled mode. Cisco NX-OS analyzes all packets on the interface or subinterface for full NetFlow mode. For sampled mode, you configure the sampling algorithm and rate that Cisco NX-OS analyzes packets. For more information on sampler maps, see the "Sampler Maps" section.

Flow Record Maps

A flow record map defines the keys that NetFlow uses to identify packets in the flow as well as other fields of interest that NetFlow gathers for the flow. You can define a flow record map with any combination of keys and fields of interest. Cisco NX-OS supports a rich set of keys including layer 2 and Layer 3 parameters. A flow record also defines the types of counters gathered per flow. You can configure 32-bit or 64-bit packet or byte counters. Cisco NX-OS enables the following match fields when you create a flow record:

•match interface input

•match interface output

•match flow direction

For more information, see the "Creating a Flow Record" section.

Exporter Maps

An exporter map contains network layer and transport layer details for the NetFlow export packet. You can configure the following information in an exporter map:

•Export destination IP address

•Source interface

•UDP port number (where the collector is listening for NetFlow packets)

•Export format

Note NetFlow export packets use the IP address that is assigned to the source interface. If the source interface does not have an IP address assigned to it, the exporter will be inactive.

Cisco NX-OS exports data to the collector whenever a timeout occurs or when the flow is terminated (TCP Fin or Rst received, for example). You can configure the following timers to force a flow export:

•Active timeout—Cisco NX-OS does not remove the cache entries from the cache.

•Inactive timeout—Cisco NX-OS removes the cache entries from the cache.

Export Formats

Cisco NX-OS supports the Version 9 export format for most flows. Version 9, which combines hardware-aggregated flow records and non-aggregated flow records in the same export frame, also supports the following features:

•Immediate Flow Aging—Allows Cisco NX-OS to send flow records when the flow is created.Cisco NX-OS supports this feature in sampled mode to avoid performance degradation on the device.

•Adaptive Flexible NetFlow—Defines how the device behaves as it runs out of system resources reserved for NetFlow.

•Packet Chunk Fields—Copies part of the packet and sends it to the collector. This feature can only be used in sampled mode and can negatively impact the performance of the device.

Cisco NX-OS supports multiple Netflow export destinations— up to 2 destinations per flow monitor.

Note Cisco NX-OS supports UDP as the transport protocol for exports to up to four collectors.

You can configure IPv4 to use the Version 5 export format, but you must limit flows using this format to use the keys and fields predefined by the Version 5 export format.

Monitor Maps

A monitor map references the flow record map and flow exporter map. You apply a monitor map to an interface.

Sampler Maps

If you are using sampled mode, you use the sampler map to specify the rate at which packets are sampled. On high bandwidth interfaces, applying NetFlow processing to every single packet can result in high CPU utilization. Sampler map configuration is typically geared towards such high speed interfaces. You can configure samples in one of the following options:

•M out of N—For example, 100 out of every 10,000 packets are sampled.

•Time-base—For example, sample a packet every 100 milliseconds.

If you do not associate a sampler map with an interface, NetFlow gathers statistics on every packet that matches the flow keys on that interface.

High Availability

Cisco NX-OS supports stateless restarts for NetFlow. After a reboot or supervisor switchover, Cisco NX-OS applies the running configuration.

Virtualization Support

Cisco NX-OS defines NetFlow flows within a virtual device context (VDC). By default, Cisco NX-OS places you in the default VDC and any flows that you define in this mode are only available for interfaces in the default VDC. See the Cisco NX-OS Virtual Device Context Configuration Guide at the following URL:

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_0/nx-os/virtual_device_context/configuration/guide/vdc_nx-os_book.html

Licensing Requirements for NetFlow

The following table shows the licensing requirements for this feature:

Product

License Requirement

NX-OS

NetFlow requires no license. Any feature not included in a license package is bundled with the Cisco NX-OS system images and is provided at no extra charge to you. For a complete explanation of the NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide at the following URL:

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_0/nx-os/licensing/configuration/guide/nx-os_licensing.html.

Prerequisites for NetFlow

NetFlow has the following prerequisites:

•You must understand the resources required on your device because NetFlow consumes additional memory and CPU resources.

If you configure VDCs, install the Advanced Services license and enter the desired VDC (see to the Cisco NX-OS Virtual Device Context Configuration Guide at the following URL:

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_0/nx-os/virtual_device_context/configuration/guide/vdc_nx-os_book.html).

Configuration Guidelines and Limitations

NetFlow has the following configuration guidelines and limitations:

•You must configure a source interface. If you do not configure a source interface, the exporter will remain in a disabled state.

•You can configure a maximum of 2 export destinations per flow monitor.

•You must configure a valid record map name for every flow monitor map.

In Cisco NX-OS, NetFlow map configuration takes place in map-specific submodes.

Use the global configuration mode to create a flow record map and enter the flow record submode:
switch(config)# flow record Test
switch(config-flow-record)# 
Use the global configuration mode to create a flow exporter map and enter the flow exporter submode:
switch(config)# flow exporter ExportTest
switch(config-flow-exporter)# 
From the flow exporter submode, you can specify the exporter version. If you specify version 9, you enter the flow exporter version submode:
switch(config)-flow-exporter# version 9
switch(config-flow-exporter-version-9)# 
Use the global configuration mode to create a flow monitor map and enter the flow monitor submode:
switch(config)# flow monitor MonitorTest
switch(config-flow-monitor)# 
Tip From a submode, you can type ? to get a list of all commands available in the submode.

Configuring NetFlow

To configure NetFlow, follow these steps:

Step 1 Enable the Netflow feature (see the "Enabling the NetFlow Feature" section).

Step 2 Define a flow record by specifying keys and fields to the flow (see the "Creating a Flow Record" section).

Step 3 Define an optional flow exporter by specifying export format, protocol, destination and other parameters (see the "Creating a Flow Exporter" section).

Step 4 Define a flow monitor based on the flow record and flow exporter (see the "Creating a Flow Monitor" section).

Step 5 Apply the flow monitor to a source interface, subinterface, VLAN interface (see the "Applying a Flow to an Interface" section), or a VLAN (see the "Configuring Bridged NetFlow on a VLAN" section).

This section includes the following topics:

•Enabling the NetFlow Feature

•Creating a Flow Record

•Creating a Flow Exporter

•Creating a Flow Monitor

•Creating a Sampler

•Applying a Flow to an Interface

•Configuring Bridged NetFlow on a VLAN

•Configuring NetFlow Timeouts

Note If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might differ from the Cisco IOS commands that you would use.

Enabling the NetFlow Feature

You must globally enable NetFlow before you can configure any flows.

To enable NetFlow, use the following command in global configuration mode:
Command

Purpose
feature netflow
Example:
switch(config)# feature netflow
Enables the NetFlow feature.
To disable NetFlow and remove all flows, use the following command in global configuration mode:
Command

Purpose
no feature netflow
Example:
switch(config)# no feature netflow
Disables the NetFlow feature. Default is disabled.
Creating a Flow Record

You can create a flow record and add associate keys and fields to the flow. Cisco NX-OS enables the following match fields when you create a flow record:

•match interface input

•match interface output

•match flow direction

BEFORE YOU BEGIN

Ensure that you have enabled the NetFlow feature (see the "Enabling the NetFlow Feature" section).

Ensure that you are in the correct VDC (or use the switchto vdc command).

SUMMARY STEPS

1. config t

2. flow record name

3. description string

4. match type

5. collect type

6. show flow record [name]

7. copy running-config startup-config

DETAILED STEPS
Command

Purpose
Step 1
config t
Example:
switch# config t
switch(config)#
Enters configuration mode.
Step 2
flow record name
Example:
switch(config)# flow record Test
switch(config-flow-record)#
Creates a flow record and enters flow record configuration mode.
Step 3
description string
Example:
switch(config-flow-record)# description Ipv4Flow
(Optional) Describes this flow record as a maximum 63 character string.
Step 4
match type
Example:
switch(config-flow-record)# match interface input
Specifies a match key. See the "Specifying the Match Parameters" section for more information on the type argument.
Step 5
collect type
Example:
switch(config-flow-record)# collect counter packets
Specifies the collection field. See the "Specifying the Collect Parameters" section for more information on the type argument.
Step 6
show flow record [name]
Example:
switch(config-flow-exporter)# show flow record
(Optional) Displays information about NetFlow flow records.
Step 7
copy running-config startup-config
Example:
switch(config-flow-exporter)# copy running-config startup-config
(Optional) Saves this configuration change.
Specifying the Match Parameters

You must configure at lease one of the following match parameters for flow record maps:
Command

Purpose
match flow direction
Example:
switch(config-flow-record)# match flow direction
Specifies the flow direction as a key.
match interface
Example:
switch(config-flow-record)# match interface
Specifies the interface input or output attribute as a key.
match ip {protocol | tos}
Example:
switch(config-flow-record)# match ip protocol
Specifies the IP protocol or ToS fields as keys.
match ipv4 {destination | source} address
Example:
switch(config-flow-record)# match ipv4 destination address
Specifies the IPv4 source or destination address as a key.
match transport {destination-port | source-port}
Example:
switch(config-flow-record)# match transport destination-port
Specifies the transport source or destination port as a key.
Specifying the Collect Parameters

You must configure at lease one of the following collect parameters for flow record maps:
Command

Purpose
collect counter {bytes | packets} [long]
Example:
switch(config-flow-record)# collect counter packets
Collects either packet-based or byte counters from the flow. You can optionally specify that 64-bit counters are used.
collect flow {direction | sampler id}
Example:
switch(config-flow-record)# collect flow direction
Collects the direction of the flow or the sampler identifier used for the flow.
collect interface {input | output}
Example:
switch(config-flow-record)# collect interface input
Collects the input or output interface attribute.
collect routing {destination | source} as [peer]
Example:
switch(config-flow-record)# collect routing destination as
Collects the source or destination AS number of the local device or the peer.
collect routing forwarding-status
Example:
switch(config-flow-record)# collect routing forwarding-status
Collects the forwarding status of the packet.
collect routing next-hop address ipv4 [bgp]
Example:
switch(config-flow-record)# collect routing next-hop address ipv4
Collects the next-hop address.
collect timestamp sys-uptime {first | last}
Example:
switch(config-flow-record)# collect timestamp sys-uptime last
Collects the system up time for the first or last packet in the flow.
collect transport tcp flags
Example:
switch(config-flow-record)# collect transport tcp flags
Collects the TCP transport layer flags for the packets in the flow.
Creating a Flow Exporter

You can create a flow export to define the export parameters for a flow.

BEFORE YOU BEGIN

•Make sure that you have enabled the NetFlow feature (see the "Enabling the NetFlow Feature" section).

•Make sure that you are in the correct VDC (or use the switchto vdc command).

•NX-OS supports multiple Netflow export destinations, up to 2 destinations per flow monitor.

SUMMARY STEPSOK

1. config t

2. flow exporter name

3. destination {ipv4-address | ipv6-address} [use-vrf name]

4. source interface-type number

5. version {5 | 9}

6. show flow exporter [name]

7. copy running-config startup-config

DETAILED STEPS
Command

Purpose
Step 1
config t
Example:
switch# config t
switch(config)#
Enters configuration mode.
Step 2
flow exporter name
Example:
switch(config)# flow exporter ExportTest
switch(config-flow-exporter)#
Creates a flow exporter map and enters flow exporter map configuration mode.
Step 3
destination {ipv4-address | ipv6-address} [use-vrf name]
Example:
switch(config-flow-exporter)# destination 192.0.2.1
Sets the destination IPv4 or IPv6 address for this exporter map. You can optionally configure the VRF to use to reach the NetFlow collector.
Step 4
source interface-type number
Example:
switch(config-flow-exporter)# source ethernet 2/1
Specifies the interface to use to reach the NetFlow collector at the configured destination.
Step 5
version {5 | 9}
Example:
switch(config-flow-exporter)# version 9
switch(config-flow-exporter-version-9)#
Specifies the NetFlow export version. Version 9 enters the export version configuration submode.
Step 6
show flow exporter [name]
Example:
switch(config-flow-exporter)# show flow exporter
(Optional) Displays information about NetFlow flow exporter maps.
Step 7
copy running-config startup-config
Example:
switch(config-flow-exporter)# copy running-config startup-config
(Optional) Saves this configuration change.
You can optionally configure the following parameters for flow exporters:
Command

Purpose
description string
Example:
switch(config-flow-exporter)# description ExportV9
Describes this flow exporter map as a maximum 63-character string.
dscp value
Example:
switch(config-flow-exporter)# dscp 0
Specifies the differentiated services codepoint value. The range is from 0 to 63.
transport udp number
Example:
switch(config-flow-exporter)# transport udp 200
Specifies the UDP port to use to reach the NetFlow collector. The range is from 0 to 65535.
You can optionally configure the following parameters in flow exporter version configuration submode:
Command

Purpose
option {exporter-stats | interface-table | sampler-table} timeout seconds
Example:
switch(config-flow-exporter-version-9)# option exporter-stats timeout 1200
Sets the exporter resend timer. The range is from 1 to 86400 seconds.
template data timeout seconds
Example:
switch(config-flow-exporter-version-9)# template data timeout 1200
Sets the template data resend timer. The range is from 1 to 86400 seconds.
Creating a Flow Monitor

You can create a flow monitor and associate it with a flow record and a flow exporter.

BEFORE YOU BEGIN

Ensure that you have enabled the NetFlow feature (see the "Enabling the NetFlow Feature" section).

Ensure that you are in the correct VDC (or use the switchto vdc command).

SUMMARY STEPS

1. config t

2. flow monitor name

3. description string

4. exporter name

5. record name

6. show flow monitor [name]

7. copy running-config startup-config

DETAILED STEPS
Command

Purpose
Step 1
config t
Example:
switch# config t
switch(config)#
Enters configuration mode.
Step 2
flow monitor name
Example:
switch(config)# flow monitor MonitorTest
switch(config-flow-monitor)#
Creates a flow monitor map and enters flow monitor map configuration mode.
Step 3
description string
Example:
switch(config-flow-monitor)# description Ipv4Monitor
(Optional) Describes the flow monitor map with an alphanumeric string up to 63 characters.
Step 4
exporter name
Example:
switch(config-flow-monitor)# exporter Exportv9
Associates a flow exporter map with this flow monitor map.
Step 5
record name
Example:
switch(config-flow-monitor)# record IPv4Flow
Associates a flow record map with this flow monitor map.
Step 6
show flow monitor [name]
Example:
switch(config-flow-monitor)# show flow monitor
(Optional) Displays information about NetFlow flow monitor maps.
Step 7
copy running-config startup-config
Example:
switch(config-flow-monitor)# copy running-config startup-config
(Optional) Saves this configuration change.
Creating a Sampler

You can create a sampler to define the NetFlow sampling rate for a flow.

BEFORE YOU BEGIN

Ensure that you have enabled the NetFlow feature (see the "Enabling the NetFlow Feature" section).

Ensure that you are in the correct VDC (or use the switchto vdc command).

SUMMARY STEPS

1. config t

2. sampler name

3. description string

4. mode samples out-of packets

5. show sampler [name]

6. copy running-config startup-config

DETAILED STEPS
Command

Purpose
Step 1
config t
Example:
switch# config t
switch(config)#
Enters configuration mode.
Step 2
sampler name
Example:
switch(config)# sampler SampleTest
switch(config-flow-sampler)#
Creates a sampler map and enters flow sampler map configuration mode.
Step 3
description string
Example:
switch(config-flow-sampler)# description Samples
(Optional) Describes the sampler map with an alphanumeric string up to 63 characters.
Step 4
mode samples out-of packets
Example:
switch(config-flow-sampler)# mode 1 out-of 100
Defines the number of samples to take per the number of packets received. The samples range is from 1 to 64. The packets range is from 1 to 8192 packets.
Step 5
show sampler [name]
Example:
switch(config-flow-sampler)# show sampler
(Optional) Displays information about NetFlow sampler maps.
Step 6
copy running-config startup-config
Example:
switch(config-flow-sampler)# copy running-config startup-config
(Optional) Saves this configuration change.
Applying a Flow to an Interface

You can apply a flow monitor map and an optional sampler map to an interface.

BEFORE YOU BEGIN

Ensure that you have enabled the NetFlow feature (see the "Enabling the NetFlow Feature" section).

Ensure that you are in the correct VDC (or use the switchto vdc command).

SUMMARY STEPS

1. config t

2. interface interface-type number

3. ip flow monitor name {input | output} [sampler name]

4. show flow interface [interface-type number]

5. copy running-config startup-config

DETAILED STEPS
Command

Purpose
Step 1
config t
Example:
switch# config t
switch(config)#
Enters configuration mode.
Step 2
interface interface-type number
Example:
switch(config)# interface ethernet 2/1
switch(config-if)#
Enters interface configuration mode. The interface type can be Ethernet, port channel, mgmt, VLAN interface, or a subinterface.
Step 3
ip flow monitor name {input | output} [sampler name]
Example:
switch(config-if)# ip flow monitor MonitorTest input
Associates a flow monitor map and an optional sampler map to the interface for input or output packets.
Step 4
show flow interface [interface-type number]
Example:
switch(config-if# show flow interface
(Optional) Displays information about NetFlow on an interface.
Step 5
copy running-config startup-config
Example:
switch(config-if)# copy running-config startup-config
(Optional) Saves this configuration change.
Configuring Bridged NetFlow on a VLAN

You can apply a flow monitor map and an optional sampler map to a VLAN.

BEFORE YOU BEGIN

Ensure that you have enabled the NetFlow feature (see the "Enabling the NetFlow Feature" section).

Ensure that you are in the correct VDC (or use the switchto vdc command).

SUMMARY STEPS

1. config t

2. vlan vlan-id

3. ip flow monitor name {input | output} [sampler name]

4. copy running-config startup-config

DETAILED STEPS
Command

Purpose
Step 1
config t
Example:
switch# config t
switch(config)#
Enters configuration mode.
Step 2
vlan vlan-id
Example:
switch(config)# vlan 30 switch(config-vlan)#
Enters VLAN configuration mode. The vlan-id range is from 1 to 3967, or from 4048 to 4093
Step 3
ip flow monitor name {input | output} [sampler name]
Example:
switch(config-vlan)# ip flow monitor MonitorTest input
Associates a flow monitor map and an optional sampler map to the VLAN for input or output packets.
Step 4
copy running-config startup-config
Example:
switch(config-vlan)# copy running-config startup-config
(Optional) Saves this configuration change.
Configuring NetFlow Timeouts

You can optionally configure global NetFlow timeouts that apply to all flows.

To configure NetFlow timeout parameters, use the following commands in global configuration mode:
Command

Purpose
flow timeout active seconds
Example:
switch(config)# flow timeout active 90
Sets the active timeout value. The range is from 60 to 4092 seconds.
flow timeout aggressive threshold percent
Example:
switch(config)# flow timeout aggressive threshold 90
Sets the percentage that you want the NetFlow table to be before aggressive aging starts. The range is from 50 to 99 percent.
flow timeout fast seconds threshold packets
Example:
switch(config)# flow timeout fast 40 threshold 1200
Sets the fast timeout value and the number of packets in a flow before aging begins. The fast timeout range is from 32 to 512 seconds. The packets range is from 1 to 4000.
flow timeout inactive seconds
Example:
switch(config)# flow timeout inactive 900
Sets the inactive timeout value. The range is from 15 to 4092 seconds.
flow timeout session
Example:
switch(config)# flow timeout session
Enables TCP session aging.
Verifying NetFlow Configuration

To verify NetFlow configuration information, use these commands:

Command

Purpose

show flow exporter [name]

Displays information about NetFlow flow exporter maps.

show flow interface [interface-type number]

Displays information about NetFlow interfaces.

show flow monitor [name] [cache [detailed]]

Displays information about NetFlow flow monitor maps.

show flow record [name]

Displays information about NetFlow flow record maps.

show flow timeout

Displays information about NetFlow timeouts.

show hardware flow aging [vdc vdc_id] [detail] [module module]

Displays information about NetFlow aging flows in hardware.

show hardware flow entry address table-address type {ip | ipv6} [module module]

Displays information about NetFlow table entries in hardware.

show hardware flow ip [interface type number | monitor monitor_name | profile profile-id | vdc vdc_id | vlan vlan_id] [detail] [module module]

Displays information about NetFlow IPv4 flows in hardware.

show hardware flow sampler [all | count | index number | name sampler-name | vdc vdc_id] [detail] [module module]

Displays information about NetFlow sampler in hardware.

show hardware flow utilization [module module]

Displays information about NetFlow table utilization in hardware.

show sampler [name]

Displays information about NetFlow sampler maps.

NetFlow Example Configuration

This example creates a flow and applies it to an interface:
feature netflow
flow exporter ee
 version 9
flow record rr
 match ipv4 source address
 match ipv4 destination address
 collect counter bytes
 collect counter packets
flow monitor foo
 record rr
 exporter ee
interface Ethernet2/45
 ip flow monitor foo output
 ip address 10.20.1.1/24
 no shutdown
Default Settings

Table 13-1 lists the default settings for NetFlow parameters.

Table 13-1 Default NetFlow Parameters

Parameters

Default

Accounting cache size

8K

Egress and Ingress cache size

512K

Additional References

For additional information related to implementing NetFlow, see the following sections:

•Related Documents

•Standards

•MIBs

Related Documents

Related Topic

Document Title

NetFlow CLI commands

Cisco Nexus 7000 Series NX-OS System Management Command Reference, Release 4.0 at the following URL:

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_0/nx-os/system_management/command/reference/sm_cmd_ref.html

VDCs and VRFs

Cisco Nexus 7000 Series NX-OS Virtual Device Context Configuration Guide, Release 4.0 at the following URL:

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_0/nx-os/virtual_device_context/configuration/guide/vdc_nx-os_book.html

Cisco NetFlow Overview

http://cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html

Standards

Standards

Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.

—

MIBs

MIBs

MIBs Link

•CISCO-NETFLOW-MIB

To locate and download MIBs, go to the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml