RE: check_snmp oddity

I had actually copied the command wrong from my other window. 

#snmpget -v 1 -c <community> cosap3 1.3.6.1.4.1.522.3.12.1.8.0
SNMPv2-SMI-v1::enterprises.522.3.12.1.8.0 = INTEGER: 25
 
#check_snmp -H cosap3 -C <community> -o 1.3.6.1.4.1.522.3.12.1.8.0
It seems to hang forever.   


I compiled all the plugins and the Net:SNMP perl module on another machine
and getting the same results. Any ideas?

Russ


-----Original Message-----
From: Subhendu Ghosh [mailto:sghosh-5S6al/Htfwsdnm+yROfE0A@xxxxxxxxxxxxxxxx]
Sent: Thursday, January 15, 2004 5:56 PM
To: Hubbard, Russ
Cc: 'nagiosplug-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx'
Subject: Re: [Nagiosplug-help] check_snmp oddity


On Thu, 15 Jan 2004, Hubbard, Russ wrote:

> Hello,
>    I'm trying to get check_snmp to work with a Cisco AP350 Wireless acess
> point. The OID I'm using is for listing "Connected Nodes".  I'm using the
> nagios-plugins-HEAD-200311201747 tarball for the plugin. When I check the
> OID with snmpget, it works fine. Here's what I get:
> 
> #snmpget -v 1 -c <community> cosap3 1.3.6.1.4.1.522.3.12.1.8.0
> SNMPv2-SMI-v1::enterprises.522.3.12.1.8.0 = INTEGER: 25
> 
> When I try it via 'check_snmp':
> 
> #check_snmp -H cosap3 -C <community> -o 1.3.6.1.4.1.52.3.12.1.8.0
> 
> It seems to hang forever.   
> 
> 
> I have tried adding the version argument (-P) and changing the OID to it's
> text form(awcFtClientSTASelf) and they don't help. 


the above OIDs are not the same 52 vs 522

-- 

-sg


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Nagiosplug-help mailing list
Nagiosplug-help-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
::: Please include plugins version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null