Re: [pysnmp-users] Unknown SNMP engine ID encountered - but only on one device

[Craig S. <cs...@en...>]

On Sat, 21 Oct 2017 at 00:01 Whitesell, Ken via pysnmp-users <
pys...@li...> wrote:

> $ snmpget.py -v 3 -u xxxxxxxx -A xxxxxxxx -X xxxxxxxx -l authPriv
> udp6:device-2 SNMPv2-MIB::sysLocation.0
>
> Unknown SNMP engine ID encountered
>
Hi Ken,
   Everyone gets caught by this message at times. It basically means
"something went wrong".  I'm not sure why, perhaps the first check pysnmp
does is the engine ID so it fails first.
So, the system is responding with something the code doesn't like.  You
need to turn on the backtrace to see what the real problem is.

I've found some client tools play free and loose with the standards and are
perfectly happy about getting back garbage that pysnmp doesn't like, which
may be why you are seeing the problem in pysnmp only.

So while it says engine id, mentally translate it to "responded with bad
things" to help with your debugging.

 - Craig

>
> --
Craig Small             https://dropbear.xyz/     csmall at : enc.com.au
Debian GNU/Linux        https://www.debian.org/   csmall at : debian.org
Mastodon: @smallsees@social.dropbear.xyz             Twitter: @smallsees
GPG fingerprint:      5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5