On Wed, Sep 01, 2010 at 07:25:21PM +0000, Yehiel Samson wrote:
> There is a strange behavior with the SNMP walker, if I perform the following
> command:
>
> snmpwalk -One -v2c -c public "IP" 1.3.6.1.4.1.4491.2.1.20.1.23
>
> I receive this answer:
>
> .1.3.6.1.4.1.4491.2.1.20.1.23.1.2.536870914.256 = Hex-STRING: 01 02 03 04
> .1.3.6.1.4.1.4491.2.1.20.1.23.1.2.536870914.16777217 = Hex-STRING: 01 02 03
> .1.3.6.1.4.1.4491.2.1.20.1.23.1.2.536870914.16777218 = Hex-STRING: 01 02 03 04
> But if I perform a full complete SNMP walk
>
> snmpwalk -One -v2c -c public "IP" > /tmp/file
>
> These values do not appear in the output file.
The latter is not a complete walk. From the snmpwalk man page:
If no OID argument is present, snmpwalk will search the subtree rooted
at SNMPv2-SMI::mib-2
If you really want a full walk, I normally walk starting at .1 (though there
is probably a better way)
Also, snmpbulkwalk is going to be a lot faster for you; try it like this:
snmpbulkwalk -One -v2c -c public "IP" .1 > /tmp/file
Steve
--
Stephen J Friedl | Security Consultant | UNIX Wizard | 714 694-0494
[email protected] | Orange County, CA | Microsoft MVP | unixwiz.net
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
