Network Management
Example NetFlow Config - Cisco 7600
This is an example device config for exporting flow data from Cisco 7600's.
First published date
Last published date
Overview
Product section
Resolution
mls netflow // This enables NetFlow on the Supervisor. mls nde sender version 5 mls aging long 64 // This breaks up long-lived flows into (roughly) one-minute segments. mls aging normal 32 // This ensures that flows that have finished are exported in a timely manner.
If you have Supervisor Engine 32 or 720, you need to execute the following two commands to put the interface information in the netflow packets:
mls flow ip interface-full mls nde interface
The next two commands will help to enable NetFlow data export for bridged traffic, which is optional. You can specify the list of VLANs here to enable bridged traffic:
ip flow ingress layer2-switched vlan <vlanlist> ip flow export layer2-switched vlan <vlanlist>
You can also find more information about these commands in Configuring NetFlow Data Export (NDE) (© 1992 -2018 Cisco Systems, Inc., available at https://www.cisco.com, obtained on January 20, 2019)
Apart from this, configure the routing module (MSFC) to enable NetFlow data export using the following commands:
ip route-cache flow or ip flow ingress // (This command has to be executed on all the L3/VLAN interfaces).
ip flow-export destination {hostname|ip_address} 2055 // The hostname or IP address for SolarWinds Netflow Traffic Analyzer.
ip flow-export source {interface} // the interface through which NetFlow packets are exported. eg: FastEthernet 0/0
ip flow-export version 5
ip flow-cache timeout active 1
ip flow-cache timeout inactive 15
snmp-server ifindex persist
Note: Switch ports connected to an ether channel or a trunk cannot be configured to export NetFlow data.