Hi Robert,
If rediscovering the engine ID improves the behavior
(even only for a short time) then you most likely
encountered one of the most frequent SNMPv3
errors: Two SNMPv3 entities with the same
engine ID.
Make sure that the engine IDs in your network
are unique (as the standard requires
Hi,
I believe USM table model will keep lastly updated password for the same
user and it is not possible to have one user with two different passwords
Always one USER one PWD(recently updated).
Regards,
Velu.
On Mon, Sep 19, 2011 at 4:03 PM, Robert Pierce rpie...@actionpacked.comwrote:
Hi,
Hi,
Thank guys for your help. So I tried getting the authorization ID via the
snmp class, that seemed to help for the most part. However, I'm seeing
something strange on a pair of devices. If I execute the code below, on the
first request the data comes back ok but on all subsequent request one of
