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) > NTA Virtual Interface reporting traffic instead of desired interface

NTA Virtual Interface reporting traffic instead of desired interface

Created by Daniel Polaske, last modified by Daniel Polaske on Aug 04, 2017

Views: 1,814 Votes: 2 Revisions: 8


This article discusses the issue where a number of unmonitored interfaces are reported data as the following:


NTA Virtual Interface #### 


*where #### is a sequential number


This implies that the NTA Collector is receiving flows from a managed node but one that is not responding via SNMP, and thus unable to associate a known interface with the flow conversation data.


All NTA environments


Devices configured to export NetFlow are sometimes able to export the NetFlow summarization packets to the NTA Collector with a source address that does not match an existing node.  In addition, this can be caused by using the Null interface to export data.


Configure the device to export Netflow using the source address that matches the existing node IP address (which should also respond via SNMP).  Alternatively, please do not use the Null interface to export flow data. The steps for making this configuration change can vary from device to device. SolarWinds recommends searching for vendor documentation as this is can be very different depending on make/model/IOS version.


Last modified