snmp mib checks

[abrist]

You need to identify the oid that you wish to check. It may be better to dump the walk's output to a file from the cli and then attach it to your next post so that we can look at the walk and help you identify the oid you are looking for:
V1:

Code: Select all

snmpwalk -v1 -c <community> <device ip> > /tmp/walk.txt

V2c:

Code: Select all

snmpwalk -v2c -c <community> <device ip> > /tmp/walk.txt

Attach /tmp/walk.txt to your next post.

[JohnFLi]

Ok, got the file, and attached

This device has 7 external temperature sensors and 16 External Switch Sensors.
The external Switch's need to alert when the state is 'Closed' (they are currently all open----good)

the temperature settings should alert at 65.

[abrist]

Well, that walk was *very* spartan.

Is there a chance that these values/oids are not pollable, and are only reported as events through snmp traps?

[JohnFLi]

Hopefully, this will help
Using iReasoning MIB Browser, I was able to find this:

[abrist]

Well, we can try to snmpget those oids:

Code: Select all

snmpget -c <community> <device ip> 1.3.6.1.4.1.20916.1.8.1.3.1
snmpget -c <community> <device ip> 1.3.6.1.4.1.20916.1.8.1.2.1.1

[JohnFLi]

[root@localhost tmp]# snmpget -c public 10.100.3.121 1.3.6.1.4.1.20916.1.8.1.2.1.1
No log handling enabled - turning on stderr logging
snmpget: Timeout

[tmcdonald]

My guess is access control on the device:

http://www.net-snmp.org/wiki/index.php/ ... t#Timeouts

Specifically, if there is a web interface where you can configure the device I would look around for something like "Access List" or "Blocklist" or something similar where you can allow the Nagios IP to query.

[JohnFLi]

but the snmp walk that nagios does do, the fact that it returns info shows its responding isn't it?

[tmcdonald]

It might be configured to allow certain OIDs to all IPs, but others must be allowed e.g. for security-related gets.

[abrist]

Or these oids are only event-based traps. Can you contact the vendor for clarification?