Dual Netflow Stream Causing Bogus Interfaces
search cancel

Dual Netflow Stream Causing Bogus Interfaces


Article ID: 3979


Updated On:


CA Network Flow Analysis (NetQos / NFA)


With Flexible Netflow becoming more prominent in Cisco IOS Netflow Configurations, we are starting to see a common issue in configurations that causes a major issue with CA Network Flow Analysis.

If there are interfaces configured to use Flexible Netflow on a device, you absolutely can NOT have a Standard Netflow configuration set up as well as it will result in 2 separate Netflow flow streams being generated from the router.  NFA will look at this as that the router is constantly rebooting and it will start to add thousands of bogus interfaces.

  • These thousands of interfaces will cause an assortment of issues ranging from the Harvester to the Console server.
  • Slow performance throughout the GUI due to hundreds of thousands of BOGUS interfaces being generated into the databases.
  • Interfaces will be named "Interface xxx" and will not have a valid ifIndex.
  • .FLT file processing issues on the NFA Console causing a backup of .FLT files and .RPR files due to the Pump Process clogging up. (Console Server Backup: D:/CA/NFA/reporter/datafiles/input & D:/CA/NFA/reporter/datafiles/Staging and on the Harvester: D:/CA/NFA/Netflow/Datafiles/NFMinput)
  •      Last Flow times will not process, EOV data will stop processing, and 15 minute data will stop processing (on 3-Tier only).
  •      Java errors in the Harvester logs: WrapperSimpleApp Error: java.lang.OutOfMemoryError: Java heap space
  •      Harvester process can stop pulling in new data all together.



Release: RAIB1H99000-9.3-Network Flow Analysis-Interface Bundle-Hardware


Assuming the router configuration issue was already resolved, you can proceed.

  1. Upgrade to NFA 9.3.8 or NFA 9.5.0 (fix is included) to eliminate this issue.
  2. Download the NFA 9.3.8 Bogus Interface Patch.
  3. To clean up the interfaces WITH losing data on the device follow the following steps.
  4. Sort the Enable Interfaces page by ‘Total Int’.
  5. Look for Devices with the highest ‘Total Int’.
  6. Expand the device and then sort by ‘ifIndex’.
  7. Determine by looking at the total interface count for the device if it seems valid or bogus.
  8. You can also determine by looking at the interfaces on a device and seeing if the highest of the ifIndex numbers seem valid or bogus.
  9. Ultimately we are looking for high interface count devices with interfaces that are named ‘Interface xxx’ which is confirmed not valid.
  10. If you find a device with bogus interfaces it is important to note that those bogus interfaces may have been created during a transition period of when the networking team switched from Standard Netflow to Flexible Netflow and that there may not be an issue anymore.
  11. If the number of interfaces is in the 10’s to 100 thousands it is safe to assume there is still an issue and it worth investigating on the router.
  12. Fix the Netflow Configuration of the router to use only Standard or Flexible Netflow only.
  13. Delete the device from Enable Interfaces (this will result in loss of historical data).
  14. If the data is very valuable please contact CA Support or use this doc: How to cleanup bogus interfaces in NFA without losing data
  15. Once the Device has been deleted it should come back in without any bogus interfaces as long as the Netflow configuration has been fixed. 

Additional Information

Use How to cleanup bogus interfaces in NFA without losing data for cleanup procedures that will not delete data.