Observability

NetFlow and CBQoS Data Not Available for Node in SolarWinds Network Traffic Analyzer

The issue is caused by NetFlow/CBQoS data not being received by SolarWinds Network Traffic Analyzer. Validate device configuration, ensure flow traffic delivery, and confirm required services and compatibility to restore NetFlow data visibility.

First published date

5/5/2026 3:33 PM

Last published date

5/5/2026 3:33 PM

Overview

NetFlow logs are not visible for a monitored device. 

In the SolarWinds Network Traffic Analyzer dashboard, the following message is displayed:

Details for node are not available because NetFlow and CBQoS data are not available.

This indicates that the platform is not receiving or processing flow data from the device, preventing visibility into traffic analytics and QoS statistics.

Product section

Hybrid Cloud Observability

Cause

The issue occurs when NetFlow or CBQoS data is not being received or processed by NTA. Common causes include:

  • NetFlow export not configured or incorrectly configured on the device
  • Incorrect destination IP/port for NetFlow collector (default: UDP 2055)
  • Network/firewall blocking flow traffic
  • Required services not running on the NTA server
  • Device compatibility issues (e.g., unsupported NetFlow version like v5 on certain devices such as Cisco Nexus)
  • Device not properly added or recognized as a flow source in NTA

Resolution

  • Verify NetFlow Configuration on Device
  • Validate Flow Traffic Reception
  • Check Flow and CBQoS Sources Widget
    • Navigate to NTA → Flow and CBQoS Sources
    • Verify:
      • The device is listed
      • Recent timestamps are visible
    • Drill down to the interface level if needed
    • Documentation: Flow and CBQoS Sources and CBQoS issues in NTA
  • Verify Required Services
    Ensure the following services are running on the NTA server:
    • SolarWinds NetFlow Service
    • SolarWinds Platform Module Engine
  • Validate Device Compatibility
    • For devices like Cisco Nexus, avoid NetFlow v5
    • Configure Flexible NetFlow (FNF) instead to prevent processing issues
  • Confirm NPM Integration