SNMP problems checking switch

[florian.beese at infoconsult.nu]

I've made it working with your tip to watch snmpwalk output, which was realy
enlightning. :) Thanks a lot for your help, Andreas. The reason why it
wasn't working simply was, that 3COM didn't start with port 1 as number 1
instead with number 101 (for port 1).

so this works properly on our 3COM:
./check_snmp -H 1.1.1.1 -C public -o 1.3.6.1.2.1.2.2.1.8.101
for the first interface and so on until .112

quote "Andreas Ericsson":
> .1.3.6.1.2.1.2.2.1.8 means 'status of first logical interface'.
> .1.3.6.1.2.1.2.2.2.8 means 'status of second logical interface'.

I think in your explanation of the OID you have got a mistake at the last
two numbers. Is this realy working at your machine? It shouldn't, i think -
refering to the RFC 1213. You will get another ifEntry (instead of
interface) this way to the ifTable everytime requesting for interface 8, i
think. Feel free correcting me, if I am wrong.

kind regards
        Florian Beese

-----Ursprüngliche Nachricht-----
Von: Andreas Ericsson [mailto:ae at op5.se]
Gesendet: Mittwoch, 3. November 2004 12:39
An: nagios-users at lists.sourceforge.net
Betreff: Re: [Nagios-users] SNMP problems checking switch


Florian Beese wrote:
> Hi,
> 
> I got a problem using SNMP on a 3COM Super Stack II Switch.
> 
> I am using the MIB-2 (described in RFC 1213), which is supported for this 
> switch.
> 
> Now, when I do the following:
> ./check_snmp -H 1.1.1.1 -C public -o 1.3.6.1.2.1.2.1.0
> I get an "SNMP OK - 34" for the number of interfaces, which is a bit
strange 
> (34? on 12-port), but seems ok so far.

It includes NULL, loopback, and possibly a plethora of different interfaces.

> When I don't put the 0 at the end it isn't working anymore. But on some
other 
> machines we monitor with SNMP it works. I looked it up in the
documentation and 
> with the 0 it should work properly... As long as I don't want to access
any 
> tables.
> 
> When I do the following:
> ./check_snmp -H 1.1.1.1 -C public -o 1.3.6.1.2.1.2.2.1.8.1
> to check the status of the first interface on the switch I don't get a 
> respone "SNMP problem - No data received from host".  With other switches
it 
> works properly. I tried some other values of the table and of another
table and 
> got no response, too.
> 
> Any idea, why this isn't working?
> 

Yes.
.1.3.6.1.2.1.2.2.1.8 means 'status of first logical interface'.
.1.3.6.1.2.1.2.2.2.8 means 'status of second logical interface'.

I'm sure you get the drift.

snmpwalk -v 1 -c public host .1.3.6.1.2.1.2.2
should be somewhat enlightening as well.

> Thanks in advance!
> 

You're welcome.

> regards
>     Florian Beese
> 
> PS: Excuse my bad english.
> 

It's far better than most native english speakers on this list, so don't 
apologize for it.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue. 
::: Messages without supporting info will risk being sent to /dev/null



____________
Virus checked by G DATA AntiVirusKit
Version: AVK 15.0.817 from 03.11.2004


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id065&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null