Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Netflow Traffic Analyzer (NTA) > Troubleshoot no data on a specific interface in NetFlow Traffic Analyzer

Troubleshoot no data on a specific interface in NetFlow Traffic Analyzer

Updated February 8th, 2017


This article describes the issue when a port is monitored by NTA and the last received flow does not display any data. 



All versions of NTA


This problem occurs when there is a device configuration issue.



Troubleshooting Basic Interfaces:


  1. Prepare a filter directly from the wireshark GUI.
    1. Highlight one of the frames.
    2. Find the filed you are looking for.
    3. Expand Flow Set.
    4. Expand Flow 1.
    5. Right-click InputInt:3 > click Prepare a Filter > Selected.
    • This now add the Input Interface as the filter.

  1. Modify the filter to include any interface Index you wish to filter on.
  2. Get interface indexes id, use the interface table form the Solwarwinds Orion database.


  • If there are flows being received then they will appear here.
  • If the screen is blank after applying the filter, then the device is not configured correctly to send flows to the Orion Server.


Troubleshooting Tunnel Interfaces:

If no data is seen for tunnel interfaces. What can happen is tunneling is setup through several different interfaces and the last interface is sending the NetFlow data to the wrong SolarWinds server. 

Troubleshooting Virtual Interfaces:

If you add sub interfaces on a physical interface say a Palo Alto. In this case they will show up as Virtual interfaces. This will show up in the NTA events with the ifindex. Add this to start getting Netflow data in the NTA application. It will allow you to edit the name and interface speed for that Virtual interface. Run Wireshark to look at these ifindexes to sort this out in the NTA events to find the one you need to add.  

Check to see if any other interfaces are added with the same ifindex:  

It could be possible that another virtual interface was added previously with the same ifindex. If this happens you will not see flow information for the new interface you are trying to add with the same ifindex. You can find the ifindex from the NPM interface details page of the node/interface in question.



Last modified