SNMPv3 IP discovery fails using both seedfile and the Smarts IP GUI, but SNMPv3 sm_snmpwalk using same credentials is successful
Device added to Smarts IP pending list with the following message:
No response from SNMP agent, V3, agent SNMP-E-EAGENTUSMUSER-Agent
REPORT [USM]: Unknown User Name '<userName>'
Following messages seen in Smarts IP log file:
ADTM-N-AD_LOG-23-Jun-2009 10:37:16 AM, at 'Callback, bad response', while
discovering '192.168.111.5',. SNMPError = SNMP-E-ERESPONSE-No response from 192.168.111.5, port 161
. SNMP-ETIMEOUT-Timed out
Smarts - 10.1.x
TCSA - 2.x
Multiple SNMP agents are running the same EngineID. If more than one device is using the same EngineID, there will be collisions in the LCD (Local Configuration Datastore) table and will get the "Unknown User" messages described above. This scenario is unsupported because of the way the RFCs define how the LCD is to be indexed (by engine id and user id). This tuple is the unique key pair into the credentials table where passwords are stored.
This is important when either authentication or privacy are used for the v3 devices. In essence, you are "spoofing" one agent with another but duplicating its engine ID and credentials. The engine IDs need to be unique as they are used as part of the encryption key. Once this uniqueness is broken, you cannot guarantee that an authenticated packet came from where it claims to have come from.
P.S: Correcting UserName and EngineID is responsibility of device owner. This article can be used for reference however support will have limited knowledge and access.