Nagios Support Forum

Hi Guys,

Not sure you can help but I thought I'd ask...

I downloaded this plugin: http://exchange.nagios.org/directory/Pl ... rs/details

and get this when I fire it at a router (or two) that I want to check the OSPF counters on.

./check_ospf -H a.real.ip.address -f /tmp
WARNING: Received noSuchName(2) error-status at error-index 0,public,1.3.6.1.2.1.14.10.1.7

Any ideas?

Thanks!

Nick

Try running an snmpget on that oid first:

from the v2c:

SNMPv2-SMI::mib-2.14.10.7 = No Such Object available on this agent at this OID

So this means I'd need to approach the plug-in author I suppose?

Thanks!

Try reinstalling your MIB file to be sure it isn't missing any definitions.

I got a fresh MIB file (it was nicely out of date) and added it to /usr/share/snmp/mibs overwriting the old one.

I did NOT restart anything.

Command output is identical...

This output means that your device is not responding to the requested oid, it does not mean that your mibs are wrong in this case. Most devices offer different security levels per community string, I would make sure that yours has adequate access to this part of the snmp tree. It might be possible that it needs to be updated for a different oid due to a software update or something else on the router as well. Finally, you could certainly do an snmpwalk from .1 and see if more is reported and there are similar or identical oids that we can query.

So running: snmpwalk -c public x.x.x.x .1 -v 2c -m ALL

(which I assume is right?) then gives me a LOT of info...

What's my best bet for narrowing this down? I understand enough to know that an OID is a counter and nagios generally queries one or more to then generate an OK/WARN/CRIT but I then fall over at the part of discovering which OIDs I want and how I can translate the 1.x.x.x.x.x into something readable?

Your best bet is to get a mib browser from that will browse the MIB from the vendor or get documentation from the vedor with a list and explanation of the snmp oids. Once you know which oids you want to monitor, you can then use the snmpwalk wizard to configure checks from them.

Well, since we know that snmp is definitely responding to a walk, let's start taking a look at if this oid exists and is accessible from your system. The walk we just did, should walk the entire snmp tree, so we should be able to grep for specific oid's and see if they are shown.

snmpwalk -c public x.x.x.x .1 -v 2c -m ALL | grep '1.3.6.1.2.1.14.10'

This should give us a much smaller list of results if any. If that doesn't display anything, try taking of the 10, then the 14 if it fails again. I wouldn't go much past that, as it opens up too much to be helpful. Removing just those two if needed should give us an idea if those oids are available, or if they have changed location just a bit.

So sadly:

[root@localhost ~]# snmpwalk -c public x.x.x.x -v 2c -m ALL | grep '1.3.6.1.2.1.14.10'
[root@localhost ~]# snmpwalk -c public x.x.x.x -v 2c -m ALL | grep '1.3.6.1.2.1.14'
[root@localhost ~]# snmpwalk -c public x.x.x.x -v 2c -m ALL | grep '1.3.6.1.2.1'
[root@localhost ~]#

This is as good as it gets :/

[root@localhost ~]# snmpwalk -c public x.x.x.x -v 2c -m ALL | grep '1.3.6'
SNMPv2-SMI::mib-2.47.1.1.1.1.3.6 = OID: SNMPv2-SMI::zeroDotZero.0

What would you recommend as next steps?