usmStatsUnknownUserNames as terminating error? about gosnmp HOT 3 CLOSED

As soon as I submitted this I found an indication that a bug with RFC3414 compliance was resolved in a recent version of the firmware for these devices, though the context of the fix doesn't match exactly with this behavior. I will update a device and test to see if this behavior is actually a failure to adhere to RFC compliance on the device.

from gosnmp.

Latest firmware does not fix this issue. Reading the RFC, it says there should also be an accompanying error and not just the returned counter -- am I reading this correctly? If that is the case, should the error from gosnmp not take into account the accompanying error code as well as the returned counter?

       Information about the value of the msgUserName and
       msgAuthoritativeEngineID fields is extracted from the Local
       Configuration Datastore (LCD, usmUserTable).  If no information
       is available for the user, then the usmStatsUnknownUserNames
       counter is incremented and an error indication
       (unknownSecurityName) together with the OID and value of the
       incremented counter is returned to the calling module.

from gosnmp.

Sorry for the lively chatter -- it appears the firmware patch did in fact resolve this on the device, i left an errant flag in my test after the patch.

from gosnmp.