Re: [Pysnmp-dev] endofmib broken?

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

Pardon me for replying that late. I hope to be faster from now on.

At first, I do not see that end-of-mib condition detection is totally
broken in bulkwalk app. I'm now trying to bulkwalk several OIDs within a
single request so the whole walk stops at some point.

There *is* a [hopefully] minor misfeature with current code that shows up
when you walk multiple OIDs within a single request. In that case bulkwalk
stops whenever all of those OIDs reach EOM condition. If one of them hits
EOM prior to other, the dead one would still be reported to an app but with
value part set to None (what could be filtered out at the app level).

Is this what you observe? Please, clarify what exactly fails and in what
way.

Speaking of design of this part of pysnmp API, maybe it would be better to
simplify this redundant None-as-EOM-flag protocol in favor of leaving
original error object as is in var-binding value.  Whenever App notices
an endOfMib (or other v2c error objects) in value part of var-binding, App
may stop walking. Although, this approach would impose certain  difficulties
on SNMPv1 PDU processing as there is no error objects in var-binding...

Anyway, I'd have to know more about the problem you've reported to figure
out what's going wrong.

Thanks,
ilya

On Wed, 7 Dec 2005, Olivier [ISO-8859-1] Cr?te wrote:

> Hi,
>
> I've been trying to use pysnmp to write a manager app that fetches some
> data from an snmp agent (built with net-snmp) and pushes it into a DB..
>
> But, pysnmp using BulkCommandGenerator does not stop properly when it
> receives a endOfMib. The tools from net-snmp do. Maybe its because its
> returned as a success and not an error? Anyways, it should stop there.
>
>