On Mon, 29 Jul 2019 15:59:55 +0000 Brian Mock bmock@getunwired.com wrote:
To confirm your question, we are using SNMP v2c. I don't believe the issue is with the devices themselves. We currently use another monitoring tool that polls traffic data via SNMP and is reporting correctly on all of the interfaces in question within NAV.
If you think it would make sense to still test the snmp results from the nav box command line I'd be happy to try but to incorrect data appears to be isolated to just that server.
No, having a second monitoring system that reports correctly is equivalent to what I was asking for (and less work) :-)
Graphite can be a bit finicky if data is not inserted at the expected intervals, and this can lead to strange results in graphs. Sometimes, Graphite's expectations are wrong, due to misconfiguration. Sometimes, NAV's insertion of data is not happening at the expected intervals because of performance problems.
These issues are discussed in the documentation [1], which I urge you to read through.
Some of these issues may already be known to you, but because the graphs you attached seem pretty strange, I would also like you to graph the raw data. NAV sends the traffic counter values verbatim to the carbon backend, and only asks Graphite to derive a rate from those data as it renders graphs of it. It would be interesting to see a graph of the (what should be) ever-increasing counter values of one of your Ten-gig ports.
NAV would produce a graph of a port's ifInOctets with a Graphite target equivalent to this long string (which asks Graphite to scale and derive the octet counter values into a rate of bits per second):
scaleToSeconds(nonNegativeDerivative(scale(nav.devices.knwt-mnda-bh1_example_org.ports.Te0_1.ifInOctets,8)),1)
To get the raw data, you would simply use a target of:
nav.devices.knwt-mnda-bh1_example_org.ports.Te0_1.ifInOctets
To have Graphite-web render a graph of the last day of raw values, you could use something like this URL:
https://your-nav-server/graphite/render?from=-1day&until=now&target=...
As for the neighbor relationships, I'll talk with the rest of our engineering team to see if it'd make sense to move over to lldp instead of cdp.
Great, let me know how it goes :)
[1] https://nav.uit.no/doc/faq/graph_gaps.html