Yep,
That's one thing that may be going on. May also a case where version 1 and 2c react differently or both cases aren't being handled correctly for some devices? I have some wireless units that work and other that don't, they appear to be two different linux variants. This unit does not work but used to before the upgrade: nagios:~$ /usr/local/nagios/libexec/check_snmp_linkstatus -H 10.84.221.20 -v1 -C 'public' -I'eth0' WARNING: Running from command line. This could change statistics for the next run from Nagios UNKNOWN - Received noSuchName(2) error-status at error-index 4| nagios:~$ snmpwalk -v1 -cpublic 10.84.221.20 SNMPv2-MIB::sysDescr SNMPv2-MIB::sysDescr.0 = STRING: Linux 2.4.27-ubnt0 #30 Sat Feb 14 15:00:57 EET 2009 mips nagios:~$ snmpwalk -v1 -cpublic 10.84.221.20 .1.3.6.1.2.1.31.1.1.1.18 nagios:~$ snmpwalk -v2c -cpublic 10.84.221.20 .1.3.6.1.2.1.31.1.1.1.18 Timeout: No Response from 10.84.221.20 (Maybe version 2c is disabled on device not sure??) This unit works but would break if I were using version 1. SNMP Version 1 dies nagios:~$ /usr/local/nagios/libexec/check_snmp_linkstatus -H 10.84.222.28 -v1 -C 'public' -I'eth0' WARNING: Running from command line. This could change statistics for the next run from Nagios UNKNOWN - Received noSuchName(2) error-status at error-index 4| SNMP Version 2 works nagios:~$ /usr/local/nagios/libexec/check_snmp_linkstatus -H 10.84.222.28 -v2c -C 'public' -I'eth0' WARNING: Running from command line. This could change statistics for the next run from Nagios OK - eth0 (noSuchObject) is up, throughput (in/out) 0.66 bps/1.37 bps, 0%/0%|throughput_in=0.66b throughput_out=1.37b nagios:~$ snmpwalk -v1 -cpublic 10.84.222.28 SNMPv2-MIB::sysDescr SNMPv2-MIB::sysDescr.0 = STRING: Linux WILIBOX 2.6.18.8 #1 Wed Apr 23 02:29:28 EEST 2008 mips nagios:~$ snmpwalk -v1 -cpublic 10.84.222.28 .1.3.6.1.2.1.31.1.1.1.18 nagios:~$ snmpwalk -v2c -cpublic 10.84.222.28 .1.3.6.1.2.1.31.1.1.1.18 IF-MIB::ifAlias = No Such Object available on this agent at this OID Hope this helps, I would like to get to the bottom of this as we are doing a lot of interface checks. Thanks, James Whittington VC3, Inc. From: [email protected] [mailto:[email protected]] On Behalf Of Ton Voon Sent: Tuesday, May 19, 2009 12:13 PM To: Opsview Users Subject: Re: [opsview-users] UNKNOWN - Received noSuchName(2) error-statusat error-index 4 from interface: eth0 check after 3.0.4 upgrade Frederic, James, Can you try running: snmpget -c {community} -v {version} {hostname} .1.3.6.1.2.1.31.1.1.1.18.{interfaceid} My theory is that the ifAlias information is not available on these systems. Ton On 19 May 2009, at 16:59, Frederic Jacquet wrote: I face the same issue on all my solaris boxes but not on linux strange ... 2009/5/19 James Whittington <[email protected]> I just did the upgrade from Opsview 3.0.2 to 3.0.4 , reverse ssh master/slave setup and everything appeared to go well except: I have a lot if eth0 checks that are getting this error on wireless access points. "UNKNOWN - Received noSuchName(2) error-status at error-index 4" I know some new stuff was added to the build in check interfaces opsview script so don't know if its related to that or not. I'm getting ready to go connect to that network to troubleshoot a bit further but if anyone knows what the error is feel free to share.
_______________________________________________ Opsview-users mailing list [email protected] http://lists.opsview.org/listinfo/opsview-users
