Looking for some help with SNMP monitoring

[dpasacritacrown]

Hi everyone, I'm experimenting with the trial version of Nagios, and one area where I'm having some trouble is SNMP monitoring. I've noticed that, when I do an SNMP walk on some devices, I'm really not getting everything I'm hoping for.

For example, I've added a cisco catalyst 4507 switch to Nagios through SNMP, but I'm not seeing any option for monitoring CPU or memory. I have a large amount of MIBs available, including many for cisco products, but I'm having some difficulty locating documentation for adding that kind of product to Nagios. Anyone have any tips or suggestions? Thanks a lot.

[tmcdonald]

The interface in the video is a little old, but here's how you upload MIBs into XI:

https://www.youtube.com/watch?v=LUpSFs0vyss

From there, try the snmpwalk from the command line and compare the results to what you get from the SNMP Walk wizard. Or are you talking about the CLI snmpwalk in the first place?

[dpasacritacrown]

Hmm, so I tried the command line SNMP walk after uploading all of the MIBs to Nagios, but still nothing....I don't see anything related to monitoring CPU or Ram.

[Box293]

Hmm, so I tried the command line SNMP walk after uploading all of the MIBs to Nagios, but still nothing....I don't see anything related to monitoring CPU or Ram.

Can you show us the command you are using and what output it produces please.

[dpasacritacrown]

This is the command I was using the test it:

snmpwalk -v 2c -c *****-M ./ 192.168.1.1 > /home/*******/snmpwalk.log

The *s are the community and user, which I hit. I ran this on the nagios server with the mib directory selected, and it poured hundreds upon hundreds of OIDs to monitor but none that looked at all like CPU or anything useful. I can't paste the output because it was just too massive.

[gormank]

A few weeks ago a helpful person posted and pointed out that SNMP is fickle--it doesn't always tell you everything. For some MIBs you have to ask.
Try adding an OID at the end:

snmpwalk -t 300 -v 2c -Cc -On -c <community> <hostname> <OID>

You can compress: gzip /home/*******/snmpwalk.log

[Box293]

Right OK I understand what you are saying now.

SNMP is one of those beasts that sometimes you need to know the object before you can go and get it.

An snmpwalk is great for testing, but as you've found, unless you know what you need it can be too much information.

You could use Cisco's SNMP Object Navigator to find information:
http://tools.cisco.com/Support/SNMP/do/ ... e=1&step=1
That URL does a search for the word cpu

Have a look at the "SNMP" wizard, it gives you some example OID's / object names. OR the Linux SNMP wizard gets into CPU and Memory usage checks. A lot of these are just generic SNMP objects that may do exactly what you need.

Does any of this help?