Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA - Knowledgebase Articles > NTA does not recognize flows from a non-primary address

NTA does not recognize flows from a non-primary address

Updated November 29, 2017


NTA intermittently does not recognized flows form a non-primary address. 

The NTA BL logs may include entries such as:

  • Adding node: 0 with IP
  • error processing packet
  • node ID is invalid

Below is a log fragment containing the errors.

2016-11-16 02:58:08,427 STP SmartThreadPool Thread #49294 INFO SolarWinds.Netflow.Processing.NodeCache - Adding node: 0 with IP: aaa.bbb.ccc.ddd to the cache. IsICMP: False, IsUnmanaged: True, FlowType: None, FlowVersion: 0, IsPrimaryIpAddress: False
2016-11-16 02:58:08,427 STP SmartThreadPool Thread #49294 INFO SolarWinds.Orion.Common.SWEventLogging - NetFlow Receiver Service [NTA Collector] is receiving a NetFlow data stream from an unmanaged device (aaa.bbb.ccc.ddd). The NetFlow data stream from aaa.bbb.ccc.ddd will be discarded. Please use Orion Node management to manage this IP address in order to process this NetFlow data stream, or just use <a href="/Orion/TrafficAnalysis/Utils/AddNode.aspx?IPAddress=aaa.bbb.ccc.ddd"><u><b>Manage this device</u></b></a>.
2016-11-16 02:58:08,442 STP SmartThreadPool Thread #49294 ERROR SolarWinds.Netflow.Processing.Workflow.PacketProcessingWorkflow - error processing packet
System.ArgumentException: node ID is invalid
Parameter name: nodeID


  • NTA 4.2.1


Bug in product.


Upgrade your NTA software. This issue was resolved in NTA 4.2.2.




Last modified