Showing results for 
Search instead for 
Did you mean: 
Join Customer Connection to register!

NetFlow viz WS-X6724-SFP w/WS-F6700-CFC, & WS-X6748-GE-TX w/WS-F6700-CFC


I have searched diligently, both here and through the Cisco docs and product matrices as best I can manage. I still cannot find the answer I seek. I hope posting here might save time and effort.

My situation: I have a C6509, with a WS-X6748-GE-TX w/WS-F6700-CFC as module 1, and a WS-X6724-SFP w/WS-F6700-CFC as module 4. There is a WS-SUP720-3B as module 5, with a WS-F6K-PFC3B and a WS-SUP720 daughterboard.

There are no NetFlow-related commands available for the ports on either of the module 1 or 4 cards (i.e., ip flow ingress).

It is easy to conclude that NetFlow is not supported for these two types of cards.

My question: why or why not?

I cannot determine from the Cisco docs I have read the nature of how a SUP720 interacts (or does not interact) with a particular card to support NetFlow.

Any ideas, help or explanations, especially in regard to the WS-X6748-GE-TX and WS-X6724-SFP cards?

Infinitely appreciated.




addendum --

photon#sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(33)SXJ1, RELEASE SOFTWARE (fc2)
ROM: System Bootstrap, Version 12.2(17r)S4, RELEASE SOFTWARE (fc1)

System image file is "disk0:s72033-ipservicesk9_wan-mz.122-33.SXJ1.bin"

cisco WS-C6506 (R7000) processor (revision 3.0) with 458720K/65536K bytes of memory.
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
4294967295 Ethernet interfaces
45 Virtual Ethernet interfaces
48 FastEthernet interfaces
90 Gigabit Ethernet interfaces
8 Ten Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.

65536K bytes of Flash internal SIMM (Sector size 512K).

photon#sh mod
Mod Ports Card Type                              Model              Serial No.
--- ----- -------------------------------------- ------------------ -----------
  1   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6748-GE-TX     SAL09402BQH
  2   16  SFM-capable 16 port 1000mb GBIC        WS-X6516A-GBIC     SAL1034Z862
  3   48  48-port 10/100 mb RJ45                 WS-X6148-RJ45V     SAL06499HY6
  4   24  CEF720 24 port 1000mb SFP              WS-X6724-SFP       SAD1151048Y
  5    2  Supervisor Engine 720 (Active)         WS-SUP720-3B       SAL1035ZQK3
  6    8  CEF720 8 port 10GE with DFC            WS-X6708-10GE      SAL1231ZCGK

Mod MAC addresses                       Hw    Fw           Sw           Status
--- ---------------------------------- ------ ------------ ------------ -------
  1  0015.63b7.c9d4 to 0015.63b7.ca03   2.3   12.2(14r)S5  12.2(33)SXJ1 Ok
  2  0018.ba3c.8c60 to 0018.ba3c.8c6f   4.4   7.2(1)       12.2(33)SXJ1 Ok
  3  000b.5f95.5538 to 000b.5f95.5567   1.2   5.4(2)       12.2(33)SXJ1 Ok
  4  001e.be60.27e6 to 001e.be60.27fd   3.0   12.2(18r)S1  12.2(33)SXJ1 Ok
  5  0017.5a34.b6d0 to 0017.5a34.b6d3   5.2   8.4(2)       12.2(33)SXJ1 Ok
  6  001e.f7f8.5a28 to 001e.f7f8.5a2f   1.4   12.2(18r)S1  12.2(33)SXJ1 Ok

Mod  Sub-Module                  Model              Serial       Hw     Status
---- --------------------------- ------------------ ----------- ------- -------
  1  Centralized Forwarding Card WS-F6700-CFC       SAL09073VZK  2.0    Ok
  3  Inline Power Module         WS-F6K-VPWR                     2.0    Ok
  4  Centralized Forwarding Card WS-F6700-CFC       SAL1202CCDZ  4.0    Ok
  5  Policy Feature Card 3       WS-F6K-PFC3B       SAL1035ZTDL  2.3    Ok
  5  MSFC3 Daughterboard         WS-SUP720          SAL1032XKVV  2.5    Ok
  6  Distributed Forwarding Card WS-F6700-DFC3C     SAL1228WVZR  1.0    Ok

Mod  Online Diag Status
---- -------------------
  1  Pass
  2  Pass
  3  Pass
  4  Pass
  5  Pass
  6  Pass

photon#sh inv
NAME: "WS-C6506", DESCR: "Cisco Systems Catalyst 6500 6-slot Chassis System"
PID: WS-C6506          ,                     VID:    , SN: TSC0716004D

PID: WS-C6K-VTT        ,                     VID:    , SN: SMT0712C274

PID: WS-C6K-VTT        ,                     VID:    , SN: SMT0712C289

PID: WS-C6K-VTT        ,                     VID:    , SN: SMT0712C270

NAME: "WS-C6000-CL 1", DESCR: "C6K Clock FRU 1"
PID: WS-C6000-CL       ,                     VID:    , SN: SMT0710D319

NAME: "WS-C6000-CL 2", DESCR: "C6K Clock FRU 2"
PID: WS-C6000-CL       ,                     VID:    , SN: SMT0710D375

NAME: "1", DESCR: "WS-X6748-GE-TX CEF720 48 port 10/100/1000mb Ethernet Rev. 2.3"
PID: WS-X6748-GE-TX    ,                     VID: V01, SN: SAL09402BQH

NAME: "WS-F6700-CFC Centralized Forwarding Card sub-module of 1", DESCR: "WS-F6700-CFC Centralized Forwarding Card Rev. 2.0"
PID: WS-F6700-CFC      ,                     VID:    , SN: SAL09073VZK

NAME: "2", DESCR: "WS-X6516A-GBIC SFM-capable 16 port 1000mb GBIC Rev. 4.4"
PID: WS-X6516A-GBIC    ,                     VID: V01, SN: SAL1034Z862

NAME: "3", DESCR: "WS-X6148-RJ45V 48-port 10/100 mb RJ45 Rev. 1.2"
PID: WS-X6148-RJ45V    ,                     VID:    , SN: SAL06499HY6

NAME: "4", DESCR: "WS-X6724-SFP CEF720 24 port 1000mb SFP Rev. 3.0"
PID: WS-X6724-SFP      ,                     VID: V03, SN: SAD1151048Y

NAME: "WS-F6700-CFC Centralized Forwarding Card sub-module of 4", DESCR: "WS-F6700-CFC Centralized Forwarding Card Rev. 4.0"
PID: WS-F6700-CFC      ,                     VID: V05, SN: SAL1202CCDZ

NAME: "5", DESCR: "WS-SUP720-3B 2 ports Supervisor Engine 720 Rev. 5.2"
PID: WS-SUP720-3B      ,                     VID: V02, SN: SAL1035ZQK3

NAME: "msfc sub-module of 5", DESCR: "WS-SUP720 MSFC3 Daughterboard Rev. 2.5"
PID: WS-SUP720         ,                     VID:    , SN: SAL1032XKVV

NAME: "WS-F6K-PFC3B Policy Feature Card 3 sub-module of 5", DESCR: "WS-F6K-PFC3B Policy Feature Card 3 Rev. 2.3"
PID: WS-F6K-PFC3B      ,                     VID: V01, SN: SAL1035ZTDL

NAME: "6", DESCR: "WS-X6708-10GE CEF720 8 port 10GE with DFC Rev. 1.4"
PID: WS-X6708-10GE     ,                     VID: V04, SN: SAL1231ZCGK

NAME: "WS-F6700-DFC3C Distributed Forwarding Card 3 sub-module of 6", DESCR: "WS-F6700-DFC3C Distributed Forwarding Card 3 Rev. 1.0"
PID: WS-F6700-DFC3C    ,                     VID: V01, SN: SAL1228WVZR

NAME: "Transceiver Te6/1", DESCR: "X2 Transceiver 10Gbase-LR Te6/1"
PID: X2-10GB-LR        ,                     VID: V03 , SN: ECL111700AB

NAME: "Transceiver Te6/2", DESCR: "X2 Transceiver 10Gbase-LX4 Te6/2"
PID: X2-10GB-LX4       ,                     VID: V04 , SN: HCT12300314

NAME: "Transceiver Te6/3", DESCR: "X2 Transceiver 10Gbase-LX4 Te6/3"
PID: X2-10GB-LX4       ,                     VID: V04 , SN: OPC12368007

NAME: "Transceiver Te6/4", DESCR: "X2 Transceiver 10Gbase-LX4 Te6/4"
PID: X2-10GB-LX4       ,                     VID: V04 , SN: HCT12390992

NAME: "Transceiver Te6/5", DESCR: "X2 Transceiver 10Gbase-LR Te6/5"
PID: X2-10GB-LR        ,                     VID: V03 , SN: ECL111600Y8

NAME: "Transceiver Te6/6", DESCR: "X2 Transceiver 10Gbase-LR Te6/6"
PID: X2-10GB-LR        ,                     VID: V04 , SN: ECL1235064J

NAME: "Transceiver Te6/7", DESCR: "X2 Transceiver 10Gbase-LR Te6/7"
PID: X2-10GB-LR        ,                     VID: V01 , SN: ONJ0913005D

NAME: "fan-tray 1", DESCR: "Chassis fan-tray 1"
PID: WS-C6K-6SLOT-FAN2 ,                     VID:    , SN:

NAME: "PS 1 WS-CAC-6000W", DESCR: "AC power supply, 6000 watt 1"
PID: WS-CAC-6000W      ,                     VID: V05, SN: AZS12280MXK

NAME: "PS 2 WS-CAC-6000W", DESCR: "AC power supply, 6000 watt 2"
PID: WS-CAC-6000W      ,                     VID: V02, SN: AZS10020M93

handoko wiyanto


i have no experience using netflow in 6500 before.

but there is this thread in the old days:


Thank you, Handoko. This is a good link, with good information.



I include here a response I received internally from one of our other engineers (didn't think to ask my fellow engineers first...) --

" I did a little digging.

Here is what I found. Netflow is actually supported for all of the line cards on .

netflow is enabled only for routed interfaces by default. All of the switchports on the 1g line cards are configured as layer2 trunk ports.... But because of the way we handle routing here we just need to enable flow on the vlan interface to get the flow that would come across those interfaces.

As an alternative we could enable layer2 flow collection for the vlans, but I dont think that really does anything for us above and beyond enabling flow on the routed vlan interface."

Kudos to this person, if he reads this.



well, happy that you resolve the issue.