More OIDs returned when calling walk on snmp.Session about snimpy HOT 2 CLOSED

❦ 17 mai 2015 14:11 -0700, Andreas Bontozoglou [email protected] :

I try to call walk directly on a Session instance. The data returned
do start at the correct point/OID, however there are extra OIDs at the
end. I suspect I am doing something wrong when calling it. Minimal
example:

No, that's expected. We receive more OID that we need when walking and
they should be discarded. This is done at the higher level within the
manager.

Shouldn't it stop at 1.3.6.1.2.1.2.2.1.22.3? Why am I getting the
extra ones? I also tried the walk using a string instead of a tuple...
same output. Any help would be appreciated.

Walk requests are translated to GETBULK. We ask for the 10 next
OID. SNMP doesn't restrict this operation to a subtree (because it

wouldn't know which subtree it is). The client has to filter itself.

Write clearly - don't be too clever.
- The Elements of Programming Style (Kernighan & Plauger)

from snimpy.

Hmm... I will write a wrapper function for this then. The problem is that I have to query without MIBs.

Thanks for the fast response,

Andreas

from snimpy.