Submit a ticketCall us

Training Class Getting Started with SolarWinds Backup - February 28

This course offers customers an introduction to SolarWinds Backup, focusing on configuring the backup technology, taking backups, data restoration and data security. It is a great primer and will get you up to speed quickly on SolarWinds Backup.
Register for class.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Understanding NetFlow Bandwidth Traffic IN and Traffic OUT display

NTA - Understanding NetFlow Bandwidth Traffic IN and Traffic OUT display

Table of contents
Created by Joseph Esquitin, last modified by MindTouch on Jun 23, 2016

Views: 1,883 Votes: 2 Revisions: 5


Understanding NetFlow Bandwidth Traffic IN and Traffic OUT display. 

This not how much NetFlow is using in bandwidth utilization or Netflow data traversing through the circuit.  Customer will submit a case thinking that just because bandwidth is populated they are receiving Netflow data.   This is not the case.  Traffic In and Traffic Out is gathered from the NPM interface utilization and it is not related to Netflow data. 



  • Any Netflow version
  • Any NPM version


  • The information pointed out below is gathered from NPM Interface polling.  It is displayed here in order to make it easy and convenient to see bandwidth utilization without having to flip back and forth between NPM Interface details page and Netflow



If there is data for a specific interface in NTA but "TRAFFIC IN" and "TRAFFIC OUT" is "0 bps" please verify that traffic statistics collection is enabled in NPM. This is a common issue if the interface is added via NTA.

You can enable traffic polling for the interface by doing the following:

  1. From Settings -> Manage Nodes
  2. Select Node in question
  3. Click on List Resources
  4. Expand the required interface
  5. Select the following 3 options
    1. Interface Availability Statistics
    2. Interface Traffic Statistics
    3. Interface Errors Statistics
  6. Click on Submit
  7. Wait for a couple polling cycles and check the results on the web console




Last modified