Re^4: SNMP from script conflicts with snmpwalk

I see. So, even though the output from snmpwalk turns out OK, I still get erroneous results when autointerpreting MIB values. So for that reason, it would be safe to use OIDs instead names? If so, it seems odd that snmpwalk returns what I expect, but perl returns another.

For example, when I run the script, I get:

q - "A6_1640_cn", comment -
q - "D1_319_CN3", comment - ""
q - "130_1016_4+", comment - "61.134"
q - "130_1035_4+", comment - "61.116"
[download]

So, it seems that the script is seeing blank values for the first two queues, and is getting messed up. However, when I check those values using snmpwalk, things are what I expect:

[burvil@localhost printer-list]$ foreach p ( A6_1640_cn D1_319_CN3 )
foreach? snmpwalk server-ip-address public .1.3.6.1.4.1.77.1.2.27.1.1 
+| egrep $p
foreach? end
enterprises.77.1.2.27.1.1.10.65.54.95.49.54.52.48.95.99.110 = "A6_1640
+_cn"
enterprises.77.1.2.27.1.1.10.68.49.95.51.49.57.95.67.78.51 = "D1_319_C
+N3"


[burvil@localhost printer-list]$ foreach p ( 10.65.54.95.49.54.52.48.9
+5.99.110 10.68.49.95.51.49.57.95.67.78.51)
foreach? snmpwalk server-ip-address public .1.3.6.1.4.1.77.1.2.27.1.3 
+| egrep $p
foreach? end
enterprises.77.1.2.27.1.3.10.65.54.95.49.54.52.48.95.99.110 = "57.13"
enterprises.77.1.2.27.1.3.10.68.49.95.51.49.57.95.67.78.51 = "61.88"
[burvil@localhost printer-list]$
[download]

Somewhat annoying, since one of the main reasons I chose SNMP over Net::SNMP or SNMP_Session was because it could parse MIBs, allowing me to write (in theory at least) more maintainable code.

Comment on Re^4: SNMP from script conflicts with snmpwalk Select or Download Code

Replies are listed 'Best First'.
Re^5: SNMP from script conflicts with snmpwalk by monarch (Priest) on Nov 15, 2005 at 02:07 UTC
I haven't used SNMP, I've only ever used Net::SNMP myself.. But it appears that you must be calling getnext in an invalid manner. Try breaking down the problem a little. Firstly, use 'getnext' on 'svPrintQName' only. Then identify the row number that is returned to you (in the above examples you were returned `10.65.54.95.49.54.52.48.95.99.110` and `10.68.49.95.51.49.57.95.67.78.51`). Then perform a 'get' on the 'svShareComment' object with the rowID that you just extracted from the result of 'getnext svPrintQName'.. The `snmpwalk` command line tool is showing you that the SNMP Agent you're querying has the results you want, so it's a matter of digging through the documentation you have for the module you're using and learning how to use it correctly.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: SNMP from script conflicts with snmpwalk
by monarch (Priest) on Nov 15, 2005 at 02:07 UTC

Net::SNMP

But it appears that you must be calling getnext in an invalid manner. Try breaking down the problem a little.

Firstly, use 'getnext' on 'svPrintQName' only. Then identify the row number that is returned to you (in the above examples you were returned 10.65.54.95.49.54.52.48.95.99.110 and 10.68.49.95.51.49.57.95.67.78.51). Then perform a 'get' on the 'svShareComment' object with the rowID that you just extracted from the result of 'getnext svPrintQName'..

The snmpwalk command line tool is showing you that the SNMP Agent you're querying has the results you want, so it's a matter of digging through the documentation you have for the module you're using and learning how to use it correctly.

[reply]
[d/l]
[select]