Network Management
NTA shows Data Not Available
NTA charts display No Data Available, even though the Last Received Netflow time stamp is the current time stamp.
First published date
Last published date
Overview
NTA displays Data Not Available in all resources for some or all devices. If the Last Received Netflow time stamp shows Never the device/s are not configured correctly in order for the flow data to be processed, or flow data is not reaching the Netflow collector. If the timestamp shows a current timestamp, but charts are still not showing any data, there is an issue with either the NTA Flow Storage database or with the NetFlow service.
Product section
Cause
- No Flow data can occur because of storage problems or because flows are not sent from the device to the SolarWinds Platform collector.
- The NetFlow service is unable to establish a connection to the Flow Storage database.
- The NetFlow Collector Services provides status information about current Flow collectors. By default, NTA listens for Flow data on port 2055, but some Flow‑enabled devices, including some Nortel IPFIX‑enabled devices, send Flow data on port 9995 and sFlow default port is 6343.
Resolution
Flow Data Missing
Explanation:
In case your Flow‑enabled device configuration requires status information about current Flow collectors, the following procedure resets or adds Flow collection ports on which your NTA collector listens for Flow data. You can also delete a collector, if necessary.
Notes:
- If you are employing a firewall on your NetFlow collector, all ports on which the NetFlow collector listens for Flow data should be listed as firewall exceptions for UDP communications.
- If you delete all collectors, you must either run the Configuration wizard again to restore your initial settings or provide another collector from a different SolarWinds Platform poller.
- Click Start > All Programs > SolarWinds Platform > NetFlow Traffic Analyzer > NetFlow Web Console.
- Log in using a User ID with a Solarwinds account with administrative privileges.
- Click Settings in the top right corner of the Web Console.
- Click NTA Settings in the Settings grouping of the SolarWinds Platform Website Administration page.
- Click NetFlow Collector Services.
- If you want to add or reset a collection port, type the new port number in the Collection Port(s) field of the collector that you want to edit.
- Separately list ports with a single comma, as in 2055,9995.
- A colored icon displays your collector status visually. Green indicates that the collector can receive Flow data, and red indicates that it can not. Server Name provides the network identification of your collector, and Receiver Status is a verbal statement of collector status.
- If you want to delete a collector, click Delete.
- Click Submit when you finish configuring your NetFlow collectors.
NTA Data Not Available, but Flows are showing in Wireshark, but not in Performance Monitor
- Run Performance Monitor on the server and load the Netflow counters:
- Select the view to Report and you should see packets coming in for Netflow:
- If nothing displays here and you can see flows are coming into Wireshark and the packets have the required fields, then the Firewall on the server is likely turned on.
- Verify on NTA events if you see the following:
Windows FireWall is turned on and its current exceptions do not allow the NetFlow Service to receive packets. Run the Configuration wizard for ‘Services’ to remedy. - Either turn off the firewall or create a Firewall inbound rule to allow traffic for the port that is being used to listen to ex: 2055.
Related Articles:
No flow data seen for light traffic interfaces due to Top Talker Optimization setting
Error: Connection to NTA Flow Storage Database has been lost. NTA cannot save any flows now
Wireshark filters and links to Troubleshooting with Wireshark:
Wireshark Operators
| OPERATOR | WIRESHARK COMMAND |
|---|---|
| equals | == |
| or | || |
| and | && |
| WHAT YOU ARE LOOKING FOR | WIRESHARK FILTER |
|---|---|
| SNMP traffic using a specific community string: | snmp.community == "public" |
| SNMP traffic NOT using a specific community string: | snmp and !(snmp.community == "public") |
| All traffic to/from the specified target | ip.addr==192.168.1.254 |
| All ICMP (ping) traffic | icmp |
| All SNMP traffic | snmp |
| Specific SNMP OID traffic | snmp.name==1.3.6.1.2.1.2.2.1.2.11111 |
| Specific SNMP traffic containing an OID string | snmp.name contains 1.3.6.1.2.1.2.2.1.2.11111 |
| Specific SNMP OID traffic from a particular IP address | ip.addr==192.168.1.252 and snmp.name==1.3.6.1.2.1.2.2.1.2.11111 |
| All traffic on UDP port 161 (typically just SNMP) | udp.port==161 |
NPM Filters
NTA Filters
| WHAT YOU ARE LOOKING FOR | WIRESHARK FILTER(S) |
|---|---|
| All NetFlow data arriving on the box |
cflow |
| NetFlow data arriving from a particular IP | ip.addr==1.2.3.4 and cflow |
| All traffic on the default NetFlow port | udp.port==2055 |
| JFlow and SFlow traffic | udp.port==9995 |
| NetFlow data - specific endpoint source |
cflow.srcaddr == 1.2.3.4 |
| NetFlow data - specific endpoint destination |
cflow.dstaddr == 1.2.3.4 |
| NetFlow on a specific vlan | cflow.vlanid==1 |
| NetFlow Endpoint destination port | cflow.dstport == 1234 |
| NetFlow Endpoint source port | cflow.srcport == 1234 |
| NetFlow Input interface (ifindex of 15 in this example) | cflow.inputint == 15 |
| NetFlow Output interface (ifindex of 15 in this example) | cflow.outputint == 15 |
| sFlow source | ip.src==1.2.3.4 and sflow |