API-Only polled nodes are not showing NTA Flow data

4/8/2026 5:03 PM

4/8/2026 5:03 PM

After adding or converting a node to API-Only polling, NTA stops displaying flow data for the device. The following symptoms are observed:

• NetFlow/IPFIX flow packets are confirmed arriving at the SolarWinds NetFlow Receiver (verified via packet capture or FPS counters).

• The interface index values in the incoming flow data match the interface indexes assigned to the API-polled node's interfaces in the Interfaces table.

• NTA does not associate the received flows with the monitored interfaces.

• The Last Received Flows timestamp does not update on the NTA resources for the node.

• No traffic data appears on any NTA widget for the affected node.

Netflow Traffic Analyzer

When a node is polled via the API-Only method, the interfaces are assigned an InterfaceSubType value that differs from SNMP-polled interfaces (which use InterfaceSubType = 0). The NTA NetFlow Service internally builds interface mappings using a query that filters on specific InterfaceSubType values. API-polled interface subtypes are excluded from this filter, which prevents NTA from creating a mapping between the incoming flow data and the monitored interfaces.

Note: This issue affects any device type using API-Only polling, including but not limited to Aruba SD-WAN devices. You need to perform the steps if you added a new node via API-Only polling specially if that node is configured to send Netflow data to Solarwinds Server.

 

 

Workaround

Warning: Before running any SQL script against the SolarWinds Platform database, ensure you have a valid backup. Modifying database tables directly can cause unintended results if not done carefully. SolarWinds recommends testing in a non-production environment first.

To work around this issue, run the following SQL script against the SolarWinds Platform database to manually reconcile the NetFlowInterfaceSources_Mapping table with the correct InterfaceID:

-- Scripts are not supported under any SolarWinds support program or service.
-- Scripts are provided AS IS without warranty of any kind. SolarWinds further
-- disclaims all warranties including, without limitation, any implied warranties
-- of merchantability or of fitness for a particular purpose. The risk arising
-- out of the use or performance of the scripts and documentation stays with you.
-- In no event shall SolarWinds or anyone else involved in the creation,
-- production, or delivery of the scripts be liable for any damages whatsoever
-- (including, without limitation, damages for loss of business profits, business
-- interruption, loss of business information, or other pecuniary loss) arising
-- out of the use of or inability to use the scripts or documentation.

UPDATE NetFlowInterfaceSources_Mapping
SET EntityID = i.InterfaceID, Managed = 1, Enabled = 1
FROM NetFlowInterfaceSources_Mapping nm
INNER JOIN Interfaces i
    ON i.InterfaceIndex = nm.InterfaceIndex AND i.NodeID = nm.NodeId
WHERE nm.EntityType = 'Orion.NPM.Interfaces'
    AND nm.EntityID IS NULL
    AND nm.LastTimeAsked IS NOT NULL

After executing the script, NTA should begin associating incoming flows with the correct interfaces within the next polling cycle.

 

Note: This workaround must be re-executed each time a new API-Only polled node is added that is also configured to export NetFlow/IPFIX traffic data to the SolarWinds collector.

Fix

A fix is planned for a future NTA release. Watch this article for updates.