cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
891
Views
0
Helpful
2
Replies

Netflow Data Export on Sup2 w/MSFC and Hybrid IOS/CatOS

richard.martin
Level 1
Level 1

We are trying to get Netflow data export running on a Sup2/MSFC.  We have followed Cisco docs 70974 with native IOS and stumbled through the CatOS equivalents on the switch side.  However, we see two commands in the IOS docs we have no equivalent to in either the CatOS or IOS on the MSFC. They are:

> Switch(config)#ip flow ingress layer2-switched vlan X,Y

Switch(config)#ip flow export layer2-switched vlan X,Y

Our S/W versions on Cat are:

System Boot Image File is 'bootflash:cat6000-sup2k8.7-6-3a.bin'
System Configuration register is 0x2102

Mod Port Model               Serial #    Versions
--- ---- ------------------- ----------- -------------------------------
1   2    WS-X6K-S2U-MSFC2    SAL0637680S Hw : 3.10
                                         Fw : 7.1(1)
                                         Fw1: 6.1(3)
                                         Sw : 7.6(3a)
                                         Sw1: 7.6(3a)

IOS in MSFC2 is:

Cisco Internetwork Operating System Software
IOS (tm) MSFC2 Software (C6MSFC2-JSV-M), Version 12.1(13)E11, EARLY DEPLOYMENT RELEASE SOFTWARE

BOOTLDR: MSFC2 Software (C6MSFC2-BOOT-M), Version 12.1(13)E11, EARLY DEPLOYMENT RELEASE

System image file is "bootflash:c6msfc2-jsv-mz.121-13.E11.bin"

Here are outputs from our router and switch:

cr01a#show ip flow export
Flow export is enabled
  Exporting flows to 10.30.184.41 (2055)
  Exporting using source interface Loopback1
  Version 5 flow records
  0 flows exported in 0 udp datagrams
  0 flows failed due to lack of export packet
  0 export packets were sent up to process level
  0 export packets were dropped due to no fib
  0 export packets were dropped due to adjacency issues
  0 export packets were dropped due to fragmentation failures
  0 export packets were dropped due to encapsulation fixup failures
  0 export packets were dropped enqueuing for the RP
  0 export packets were dropped due to IPC rate limiting

cs01a> (enable) show mls netflow ip
Software installed purging time = 0
IP flows aging time = 64 seconds
IP flows fast aging time = 0 seconds, packet threshold = 0
IP Current flow mask is Full flow
Total netflow forwarding entries = 0
Netflow Data Export version: 5
Netflow Data Export enabled
Netflow Data Export configured for port 2055 on host 10.30.184.41
Total packets exported = 14364
Destination Ifindex export is enabled
Source Ifindex export is enabled
Bridged flow statistics is disabled on vlan(s) 1-5,8-12,15,50-52,55,122-125,141,146,1
311-316,350,422,501,532,555,777,888.

Thanks in advance for your help!

2 Replies 2

Giuseppe Larosa
Hall of Fame
Hall of Fame

Hello Richard,

that document is about 12.2(18)SXF native IOS

follow the following about CaTOS 7.6

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/catos/7.x/configuration/guide/nde.html#wp1031925

You must enable NetFlow switching on the MSFC Layer 3 interfaces to support NDE.

First you need to configure MSFC

set mls nde enable

on supervisor

and

http://www.cisco.com/en/US/partner/docs/switches/lan/catalyst6500/ios/12.1E/configuration/guide/nde.html#wp1047637

Hope to help

Giuseppe

Jan Nejman
Level 3
Level 3

Hello,

  I assume the 'ingress' means, that the box will use packets with internal hardware -> create flows in TCAM,

but the 'export' means, that these flows will be exported to the outside collector.

Without 'export' command you will be able to see flows only via show commands.

I recommend you config ingress and export commands together.

Be aware the switch-layer2 command can export a huge flow stream!

Kind regards,

Jan Nejman

Caligare, co.

http://www.caligare.com/

Review Cisco Networking products for a $25 gift card