Interfaces collecting Netflow data do not show up in NPM Traffic Reports

Question

Anyone ever seen/have any ideas on how interfaces that are successfully collecting Netflow data for NTA do not show up in some of my NPM historical Traffic Reports?   I need to look at 95th percentile usage of our data circuits for sizing/capacity, and my collection interfaces are not included in these specific reports.  They do show up in other traffic reports.   I also have another segregate instance of Solarwinds where this behaviour does not occur.  Any help/ideas would be appreciated.  I'll float this for a day or two then will open an incident with Solarwinds.

Thanks,

Lee

mmgm76 · Answer

This turned out to be a timing issue.   At the time I had caught this problem, the ISP that owns responsibility for the edge circuits/routers in that office had changed the SNMP information on the router without telling us.   When they corrected, we were able to see the flows and report the interface again.   Human error.

Thanks,

George

Yann · Answer

Hi Lee,

Could you give an example of a report that is working plus another one that does not show some of your interfaces? You can attach the report to your post (located in \Program Files\Solarwinds\Orion\Reports\).

NTA computes the NetFlow,JFlow, SFlow protocols which is not related with the statistics gathered by SNMP to report the Traffic Utilization of your interfaces you see in the reports. So you might get NetFlow statistics whereas you are not collecting the traffic utilization by SNMP and vice versa.

Can you check that you selected the "Interface Traffic Charts" option for the interfaces missing in your reports when you list the resources of your equipment in System Manager or the Web Console?

Start > All Programs > Solarwinds Orion > System Manager

Right-Click on a device and select List Resources.

The option must be selected under the interface name.

yet I do not know why the interfaces would show up in some reports if that option is not selected. If you attach two reports this would give us a better idea of the issue as we can analyze the SQL query run by the report.

Thanks,

Yann