Below are the most common issues encountered on SolarWinds NTA charts.
If your devices are configured to export NetFlow on both ingress and egress interfaces, you might see duplicate traffic in your resources.
Duplicate flows can occur in the following cases:
ip flow ingressand
ip flow egresscommands, make sure NetFlow is enabled only for ingress interfaces.
The Top XX Endpoints and Top XX Domains resources display double data by design. Each flow has two distinct endpoints. To display statistics for top endpoints, SolarWinds NTA disregards that one endpoint is the source and the other endpoint is the target of flows, and treats both as endpoints only. This effectively doubles the total amount of data displayed by the Top XX Endpoints resource.
Let us take two flows and look at what you see in most resources and in the Top XX Endpoints resource.
|Flow||Source IP||Destination IP||Protocol||Bytes Transferred|
|Total bytes transferred:||50+40=90|
If your resources show the "no data" message, it can be caused by one of the following:
No data to be displayed
There are no data to be displayed for the current time and flow direction settings.
To resolve the issue, check the time settings for both the resource and the view.
Too long time period selected for the view
If SolarWinds NTA needs more than one hour to process data that you want to see in the resources, the query times out and the resources show the "no data" message.
To resolve the issue, define a shorter time period for both the view and the resource.
If you remove a shaping policy from a class, post-policy charts with the chart type set to % of Class Utilization may display unexpected spikes.
This is normal behavior, because devices affected by the policy change temporarily report huge amounts of data, which is reflected by the post-policy spike.