librenms / librenms

Community-based GPL-licensed network monitoring system
https://www.librenms.org
Other
3.94k stars 2.3k forks source link

No CPU graphing on Cisco 9148 switch whic is based on NX-OS #6251

Closed breeman1 closed 7 years ago

breeman1 commented 7 years ago

DO NOT DELETE THIS INFORMATION.

Please read this information carefully.

GitHub issues is for bugs, please do not post issues asking for help or how to do X, Y or Z. You can use our irc channel ##librenms on freenode to ask questions or our community site. If you have a feature request please post this on our community site.

Please confirm each of the sections below by putting an x in the box like [x].

The CPU utilization is not being graphed on LibreNMS even though it is supported by this device. Your help will be appreciated. Please note that we poll this device via SNMPv3 for security reasons without an option to use version 2. CiscoNX-OS_discovery.txt CiscoNX-OS_poller.txt CiscoNX-OS_snmpbulkwalk.txt image

ghost commented 7 years ago

I've a SAN fabric using 4x MDS 9148S 16G and it's working. But I'm using release 6.2.x, can be OS related?

laf commented 7 years ago

Also running a MDS 9148S 16G 48 FC (1 Slot) on 6.2.x release with no issues.

ghost commented 7 years ago

Just noticed the version, 5.0(1a)! This is a very very very very very very very old version.

geordish commented 7 years ago

I'm running MDS 9124 (1 Slot) on 5.0a with no issues.

Do you have views configured on this device?

SNMP[/usr/bin/snmpget -v3 -n '' -l 'authPriv' -a 'MD5' -A 'String_one' -u 'tester' -x 'AES' -X 'String_two' -Oqv -M /opt/librenms/mibs:/opt/librenms/mibs/cisco udp:HOSTNAME:161 .1.3.6.1.4.1.9.2.1.58.0] No Such Object available on this agent at this OID

Your device is not reporting CPU information.

breeman1 commented 7 years ago

Hi @geordish, Are you using snmpv2 or snmpv3 on your devices?

breeman1 commented 7 years ago

Please see the first comment on issue #2872 where I was having issues adding this device via the CLI using the snmpv3. I have dumped the screenshots for your information. Obviosly this is an old install and the CPU and RAM graphing issues have been resolved since then. However it seems that the issue is more related to the snmpv2 versus snmpv3 polling; looking at the old pictures below, rather than it being an OS issue. I am not discounting the later though. In this old issue, the CPU was graphed only when using snmpv2 and not when using snmpv3. image image

geordish commented 7 years ago

@breeman1 I'm using SNMPv2.

Your device simply isn't responding that it has a CPU. It could be a bug in the SNMP agent, or it could be a misconfiguration, with a view restricting access to that OID.

This is the same in your previous issue. From the discovery you posted:

/usr/bin/snmpget -v3 -n '' -l 'authPriv' -a 'MD5' -A 'test123' -u 'nms_user' -x 'AES' -X 'try234' -Oqv -M /opt/librenms/mibs udp:HOSTNAME:161 .1.3.6.1.4.1.9.2.1.58.0
No Such Object available on this agent at this OID
laf commented 7 years ago

And we use a mix of v2c and v3 (mostly v3). Works fine for all of them.

laf commented 7 years ago

@breeman1 any feedback on this, it seems various hardware/software/v2c/v3 users all see this working ok.

breeman1 commented 7 years ago

Hi @laf, I will close this issue until I can get our network engineer to look into this for me.

lock[bot] commented 6 years ago

This thread has been automatically locked since there has not been any recent activity after it was closed.