If the device is already in DCR, check the v3 credentials under Common Services > Device and Credentials > Device Management. The first packet will go out incomplete so that Discovery can discover the SNMP engine ID, engine time, and boots. Once these values are sent from the device, the actual request packet should go out with valid AuthData, engine time, and boot count.
snmp-server user CiscoWorks OurGroup v3 auth md5 yyyy
Doing a Device Credentials Verification Job a couple of minutes ago I got this message:
Setting v3 Param mode to authNoPriv. querying sysLocation.obtained exception while g/setting sysLocation com.cisco.nm.lib.snmp.futureapi.SnmpReqTimeoutException: SnmpRequestTimeout on 192.168.1.1 while performing SnmpGet at index = -1. Wrong Credentials.
That's strange because I re-checked the parameters and they are correct.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...