Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

NetFlow, 6500, export packets were dropped due to no fib

Hi

I have a problem with the 6500 not exporting netflow data. They are not exported due to no fib.

I have read somewhere that this has something to do with VRF. VRF are running on the router.

ip flow ingress has been applied to desired ip int.

Is there anything I could do to make it export netflow data?

Thank you guys.

VSS-core-XXX-rs1#sh ip flow export

Flow export v5 is enabled for main cache

  Export source and destination details :

  VRF ID : Default

    Source(1)       xxx.xxx.83.253 (Unknown)

    Destination(1)  xxx.xxx.10.39 (8824)

  Version 5 flow records

  111863 flows exported in 12928 udp datagrams

  0 flows failed due to lack of export packet

  0 export packets were sent up to process level

12927 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

  0 export packets were dropped due to Card not being able to export

VSS-core-XXX-rs1# sh mls nde

Netflow Data Export enabled

Exporting flows to  XXX.XXX.10.39 (8824)

Exporting flows from XXX.XXX.83.253 (62044)

Version: 5

Layer2 flow creation is disabled

Layer2 flow export is disabled

Include Filter not configured

Exclude Filter not configured

Total Netflow Data Export Packets are:

    8181094 packets, 0 no packets, 222662738 records

Total Netflow Data Export Send Errors:

IPWRITE_NO_FIB = 0

IPWRITE_ADJ_FAILED = 0

IPWRITE_PROCESS = 0

IPWRITE_ENQUEUE_FAILED = 0

IPWRITE_IPC_FAILED = 0

IPWRITE_OUTPUT_FAILED = 0

IPWRITE_MTU_FAILED = 0

IPWRITE_ENCAPFIX_FAILED = 0

IPWRITE_CARD_FAILED = 0

Netflow Aggregation Disabled

VSS-core-XXX-rs1#sh  run | inc mls

mls ip slb purge global

mls aging long 300

mls netflow interface

mls flow ip interface-full

mls nde sender version 5

VSS-core-XXX-rs1#sh  run | inc flow

ip flow-export source Loopback0

ip flow-export version 5

ip flow-export destination 161.4.10.39 8824

VSS-core-XXX-rs1#sh ver

Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_WAN-M), Version 12.2(33)SXI1, RELEASE SOFTWARE (fc3)

cisco WS-C6509-V-E (R7000) processor (revision 1.0) with 983008K/65536K bytes of memory.

Processor board ID FOX1242H2K4

SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache

VSS-core-XXX-rs1#sh mod

Mod Ports Card Type                              Model              Serial No.

--- ----- -------------------------------------- ------------------ -----------

  1    4  CEF720 4 port 10-Gigabit Ethernet      WS-X6704-10GE      SAL1326SRQB

  5    5  Supervisor Engine 720 10GE (Active)    VS-S720-10G        SAL1307JM4T

  8   48  CEF720 48 port 1000mb SFP              WS-X6748-SFP       SAL084869KU

  9   24  CEF720 24 port 1000mb SFP              WS-X6724-SFP       SAL1328TTH1

Everyone's tags (2)
9 REPLIES
New Member

NetFlow, 6500, export packets were dropped due to no fib

I have the exact same problem today...

so am hoping someone will reply..

Have you managed to resolve this yourself at all?

Re: NetFlow, 6500, export packets were dropped due to no fib

Hi,

VSS-core-XXX-rs1#sh ip flow export

Flow export v5 is enabled for main cache

  Export source and destination details :

  VRF ID : Default

    Source(1)       xxx.xxx.83.253 (Unknown)

    Destination(1)  xxx.xxx.10.39 (8824)

If he was using VRFs , and the DST and SRC were not in the global routing table , then this could be his issue

ip flow-export destination vrf

Dan

Bronze

Re: NetFlow, 6500, export packets were dropped due to no fib

Hi,

Can you check if "ip cef" is enabled on the switch? If not, apply "ip cef" global command and check the issue and in case cef is disabled at the interface level for certain interfaces, enable cef for all those interfaces and check the issue.

Regards,

Don Thomas Jacob

www.netflowanalyzer.com

NOTE: Please rate posts and close questions if your query has been answered

Regards, Don Thomas Jacob http://www.solarwinds.com/netflow-traffic-analyzer.aspx Head Geek @ SolarWinds NOTE: Please rate and close questions if you found any of the answers helpful.
Cisco Employee

NetFlow, 6500, export packets were dropped due to no fib

Hi,

Your destination is not configured to be in a VRF... should it be?

Anyway from the outputs

111863 flows exported in 12928 udp datagrams     <<<<<

....

12927 export packets were dropped due to no fib #     <<<<<

The box says that 111863 flows were created and put in 12928 udp datagrams which are supposed to be sent to the collector and 12927 of them (basically all of them) were dropped due to no fib.

It seems that your VSS has issue in reaching the collector, which is the host with IP 161.4.10.39.

Is it directly connected? If yes do you have the ARP entry for it? If not do you have the route to reach it?

check

show ip arp 161.4.10.39 (if directly connected)

and/or

show ip route 161.4.10.39

show ip cef 161.4.10.39

show mls cef lookup 161.4.10.39

likely the issue lies somehwere there.

Riccardo

New Member

Re: NetFlow, 6500, export packets were dropped due to no fib

Thank you guys for the feedback. I will get back to you when I am back in work, and get a chance to work with the 6500.

New Member

NetFlow, 6500, export packets were dropped due to no fib

Hey.

The problem was that there is no global routing on this 6500 and the version it is running does not support netflow exporting to VRF . So I need to wait untill we can upgrade it to a newer release.

the correct command is :

ip flow-export destination 1.1.1.2 63636 vrf ANALYSER

Cheers!

Cisco Employee

NetFlow, 6500, export packets were dropped due to no fib

Hi Tor,

Indeed that box was telling that it did not have a route to the collector, and in fact this is what I initially asked you 

so you just needed an IOS version with vrf aware nde.

glad issue is solved.

Riccardo

New Member

NetFlow, 6500, export packets were dropped due to no fib

Hi,

I am also having similar problem with 3845 where I am unable to export the flow in whats up gold.

R01#sh ip flow export

Flow export v5 is enabled for main cache

  Export source and destination details :

  VRF ID : Default (I dont have any VRF.)

    Source(1)       192.168.18.xxx (GigabitEthernet0/0)

    Destination(1)  10.50.50.xxx (9999)

  Version 5 flow records

  300038055 flows exported in 10006552 udp datagrams

  0 flows failed due to lack of export packet

  0 export packets were sent up to process level

2 export packets were dropped due to no fib (What does this means.)

  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

Bronze

NetFlow, 6500, export packets were dropped due to no fib

The packets dropped due to "no fib" means 'number of export packets that CEF was unable to switch or forward up to the process level.

Your issue seems to be different from what the original thread was about. Have you checked whether the Whatsupgold server itself is receiving packets from the router using Wireshark? And then you could check for ACL and firewalls blocking packets, availability of routes to the the flow analyzer server, and if you have CEF enabled.

Regards,
Don Thomas Jacob
http://www.solarwinds.com/netflow-traffic-analyzer.aspx


NOTE: Please rate and close questions if you found any of the answers helpful

Regards, Don Thomas Jacob http://www.solarwinds.com/netflow-traffic-analyzer.aspx Head Geek @ SolarWinds NOTE: Please rate and close questions if you found any of the answers helpful.
4087
Views
19
Helpful
9
Replies
CreatePlease login to create content