Re: SNMPv3 bulkwalk()/callback blocking during background EngineID queries

Paul S <[email protected]> writes:

> From packet analysis, I see that when bulkwalk() is called, the SNMP
> library first queries that device's EngineID if this is not already
> cached.

SNMPv3 does have a larger start up cost because of this while it does
engine synchronization.  It would surprise me that bulkwalk is the only
function with this problem.  Are you sure the same symptoms don't occur
with other types of requests (walks or even gets)?
-- 
Wes Hardaker
Please mail all replies to [email protected]