Re: [pysnmp-users] snmpwalk.py and switch stack members

[Ilya E. <il...@gl...>]

A list for users of pure-Python SNMP framework <pysnmp-users.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/pysnmp-users>,
	<mailto:pys...@li...?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum=pysnmp-users>

This happens b/c snmpwalk.py tries to get the first OID into search range
by means of a leading GET request followed by one or more GETNEXT's. It
appears to be dangerous (initial OID may not be accessible) so I'm
going to fix snmpwalk.py to behave in the same way as NetSNMP snmpwalk
does:

  - (snmpwalk.c):
    - New ability to peform a get on the requested OID when either no
      results are returned or when the user requests an inclusive
      option.

Hope to do that tomorrow. Will let you know then.

> I have done a "packet trace" and the only difference I can spot is in the snmp 
> section of the packet where snmpwalk.py produces this line:
> 
> PDU type: GET (0)
> 
> But two other snmpwalk utilities I have tried produce this line:
> 
> PDU type: GET-NEXT (1)
> 
> When I use snmpwalk.py I actually get a response.  This is an error
> 
> Error Status: NO SUCH NAME (2)