help on check_snmp
help on check_snmp
Hi all
i'm using Nagios Core 4.4.2 on my raspberry pi 4b to monitor my devices status.
i'm trying to monitor my 3 Alcatel.Lucante AP1101 Access point thei are answering to my check_ping but when i try to get more info via
./check_snmp -H xxx.xxx.xxx.xxx -C myPrivate -o 1.3.6.1.4.1.6486.802.1.1.2.1.2.1
i got the following errors
External command error: Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: iso.3.6.1.4.1.6486.802.1.1.2.1.2.1
Note: i'm using Alcatel-Lucent AWOS_3_0_6_MIBs.
please help me to understand what's wrong.
Thanks in advance
i'm using Nagios Core 4.4.2 on my raspberry pi 4b to monitor my devices status.
i'm trying to monitor my 3 Alcatel.Lucante AP1101 Access point thei are answering to my check_ping but when i try to get more info via
./check_snmp -H xxx.xxx.xxx.xxx -C myPrivate -o 1.3.6.1.4.1.6486.802.1.1.2.1.2.1
i got the following errors
External command error: Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: iso.3.6.1.4.1.6486.802.1.1.2.1.2.1
Note: i'm using Alcatel-Lucent AWOS_3_0_6_MIBs.
please help me to understand what's wrong.
Thanks in advance
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: help on check_snmp
Can you do a snmpwalk to see if that OID exists on the device
If you get "No Such Instance currently exists at this OID" back lets make sure we can connect to to the device from a walk from the top
Code: Select all
snmpwalk -v 2c -On -c 'myPrivate' xxx.xxx.xxx.xxx .1.3.6.1.4.1.6486.802.1.1.2.1.2.1
Code: Select all
snmpwalk -v 2c -On -c 'myPrivate' xxx.xxx.xxx.xxx
Re: help on check_snmp
Hi @scottwilkerson
this is the output of the command
snmpwalk -v 2c -On -c 'MyPrivate' xxx.xxx.xxx.xxx .1.3.6.1.4.1.6486.802.1.1.2.1.2.1
.1.3.6.1.4.1.6486.802.1.1.2.1.2.1 = STRING: "XX:XX:XX:XX:XX:XX"
Error: OID not increasing: .1.3.6.1.4.1.6486.802.1.1.2.1.2.1
>= .1.3.6.1.4.1.6486.802.1.1.2.1.2.1
if I omit the OId I get a list of OId of which I report the first part
.1.3.6.1.2.1.1.1.0 = STRING: OAW-AP1101 3.0.6
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.6486.802.1.1.2.1.2.1
.1.3.6.1.2.1.1.3.0 = Timeticks: (20683382) 2 days, 9:27:13.82
.1.3.6.1.2.1.1.4.0 = STRING: http://www.al-enterprise.com
.1.3.6.1.2.1.1.5.0 = STRING: MyAccessPointName
.1.3.6.1.2.1.1.6.0 = STRING: MyLocation
.1.3.6.1.2.1.1.7.0 = INTEGER: 78
.1.3.6.1.2.1.1.9.1.2.1 = OID: .1.3.6.1.2.1.4
.1.3.6.1.2.1.1.9.1.2.2 = OID: .1.3.6.1.6.3.1
.1.3.6.1.2.1.1.9.1.2.3 = OID: .1.3.6.1.2.1.49
.1.3.6.1.2.1.1.9.1.2.4 = OID: .1.3.6.1.2.1.50
.1.3.6.1.2.1.1.9.1.2.5 = OID: .1.3.6.1.6.3.16.2.2.1
.1.3.6.1.2.1.1.9.1.2.6 = OID: .1.3.6.1.6.3.10.3.1.1
.1.3.6.1.2.1.1.9.1.2.7 = OID: .1.3.6.1.6.3.11.3.1.1
.1.3.6.1.2.1.1.9.1.2.8 = OID: .1.3.6.1.6.3.15.2.1.1
.1.3.6.1.2.1.1.9.1.2.9 = OID: .1.3.6.1.2.1.10.131
.1.3.6.1.2.1.1.9.1.3.1 = STRING: The MIB module for managing IP and ICMP implementations
.1.3.6.1.2.1.1.9.1.3.2 = STRING: The MIB module for SNMPv2 entities
.1.3.6.1.2.1.1.9.1.3.3 = STRING: The MIB module for managing TCP implementations
.1.3.6.1.2.1.1.9.1.3.4 = STRING: The MIB module for managing UDP implementations
.1.3.6.1.2.1.1.9.1.3.5 = STRING: View-based Access Control Model for SNMP.
.1.3.6.1.2.1.1.9.1.3.6 = STRING: The SNMP Management Architecture MIB.
.1.3.6.1.2.1.1.9.1.3.7 = STRING: The MIB for Message Processing and Dispatching.
.1.3.6.1.2.1.1.9.1.3.8 = STRING: The management information definitions for the SNMP User-based Security Model.
.1.3.6.1.2.1.1.9.1.3.9 = STRING: RFC 2667 TUNNEL-MIB implementation for Linux 2.2.x kernels.
this is the output of the command
snmpwalk -v 2c -On -c 'MyPrivate' xxx.xxx.xxx.xxx .1.3.6.1.4.1.6486.802.1.1.2.1.2.1
.1.3.6.1.4.1.6486.802.1.1.2.1.2.1 = STRING: "XX:XX:XX:XX:XX:XX"
Error: OID not increasing: .1.3.6.1.4.1.6486.802.1.1.2.1.2.1
>= .1.3.6.1.4.1.6486.802.1.1.2.1.2.1
if I omit the OId I get a list of OId of which I report the first part
.1.3.6.1.2.1.1.1.0 = STRING: OAW-AP1101 3.0.6
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.6486.802.1.1.2.1.2.1
.1.3.6.1.2.1.1.3.0 = Timeticks: (20683382) 2 days, 9:27:13.82
.1.3.6.1.2.1.1.4.0 = STRING: http://www.al-enterprise.com
.1.3.6.1.2.1.1.5.0 = STRING: MyAccessPointName
.1.3.6.1.2.1.1.6.0 = STRING: MyLocation
.1.3.6.1.2.1.1.7.0 = INTEGER: 78
.1.3.6.1.2.1.1.9.1.2.1 = OID: .1.3.6.1.2.1.4
.1.3.6.1.2.1.1.9.1.2.2 = OID: .1.3.6.1.6.3.1
.1.3.6.1.2.1.1.9.1.2.3 = OID: .1.3.6.1.2.1.49
.1.3.6.1.2.1.1.9.1.2.4 = OID: .1.3.6.1.2.1.50
.1.3.6.1.2.1.1.9.1.2.5 = OID: .1.3.6.1.6.3.16.2.2.1
.1.3.6.1.2.1.1.9.1.2.6 = OID: .1.3.6.1.6.3.10.3.1.1
.1.3.6.1.2.1.1.9.1.2.7 = OID: .1.3.6.1.6.3.11.3.1.1
.1.3.6.1.2.1.1.9.1.2.8 = OID: .1.3.6.1.6.3.15.2.1.1
.1.3.6.1.2.1.1.9.1.2.9 = OID: .1.3.6.1.2.1.10.131
.1.3.6.1.2.1.1.9.1.3.1 = STRING: The MIB module for managing IP and ICMP implementations
.1.3.6.1.2.1.1.9.1.3.2 = STRING: The MIB module for SNMPv2 entities
.1.3.6.1.2.1.1.9.1.3.3 = STRING: The MIB module for managing TCP implementations
.1.3.6.1.2.1.1.9.1.3.4 = STRING: The MIB module for managing UDP implementations
.1.3.6.1.2.1.1.9.1.3.5 = STRING: View-based Access Control Model for SNMP.
.1.3.6.1.2.1.1.9.1.3.6 = STRING: The SNMP Management Architecture MIB.
.1.3.6.1.2.1.1.9.1.3.7 = STRING: The MIB for Message Processing and Dispatching.
.1.3.6.1.2.1.1.9.1.3.8 = STRING: The management information definitions for the SNMP User-based Security Model.
.1.3.6.1.2.1.1.9.1.3.9 = STRING: RFC 2667 TUNNEL-MIB implementation for Linux 2.2.x kernels.
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: help on check_snmp
Ok, I noticed in you test command you were not specifying the protocol vumber
Can you try
Can you try
Code: Select all
./check_snmp -H xxx.xxx.xxx.xxx -P 2c -C myPrivate -o 1.3.6.1.4.1.6486.802.1.1.2.1.2.1
Re: help on check_snmp
mmm .. maybe my previous post was not so clear, sorry
using
snmpwalk -v 2c -On -c MyPrivate xxx.xxx.xxx.xxx > snmpwalk.log
i get a list of over 4800 OIDs, but i dont understand the hierarchy
if y run
./check_snmp -H xxx.xxx.xxx.xxx -C MyPrivate -o .1.3.6.1.2.1.25.1.4.0
i can get this result
SNMP OK - "ramdisk_size=128M mem=126M board=AP152_AFI console=ttyS0,115200 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1536k(kernel)," |
there is no way to get all information hierarchy??
please find attached snmpwalk.log
using
snmpwalk -v 2c -On -c MyPrivate xxx.xxx.xxx.xxx > snmpwalk.log
i get a list of over 4800 OIDs, but i dont understand the hierarchy
if y run
./check_snmp -H xxx.xxx.xxx.xxx -C MyPrivate -o .1.3.6.1.2.1.25.1.4.0
i can get this result
SNMP OK - "ramdisk_size=128M mem=126M board=AP152_AFI console=ttyS0,115200 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env)ro,1536k(kernel)," |
there is no way to get all information hierarchy??
please find attached snmpwalk.log
- Attachments
-
- snmpwalk.txt
- (210.51 KiB) Downloaded 164 times
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: help on check_snmp
Based on the walk results file you posted, .1.3.6.1.4.1.6486.802.1.1.2.1.2.1 isn't a valid OID in the tree
Re: help on check_snmp
ok it's clear that this OID is not valid but ho can i check my access point with a single check_snmp? which is the tree root?
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: help on check_snmp
The tree root is always .1attilay2k wrote:ok it's clear that this OID is not valid but ho can i check my access point with a single check_snmp? which is the tree root?
But you cannot "check" a whole tree, if you just want to verify connectivity you can use .1.3.6.1.2.1.1.1.0 and it should return the string OAW-AP1101 3.0.6
Re: help on check_snmp
thanks for your reply, last question:
based on snmpwalk log file previously attached, how can i relate a vlan, a network interface, and all the devixes connected with theyr ip?
there must be a way to relate them togheter
based on snmpwalk log file previously attached, how can i relate a vlan, a network interface, and all the devixes connected with theyr ip?
there must be a way to relate them togheter
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: help on check_snmp
This one you're gonna be on your own.... I would suggest asking that question the the manufacturer.attilay2k wrote:thanks for your reply, last question:
based on snmpwalk log file previously attached, how can i relate a vlan, a network interface, and all the devixes connected with theyr ip?
there must be a way to relate them togheter