05-22-2023 06:16 AM
Hi,
I have several devices setup in Solarwinds. Solarwinds is getting most of the current information from these devices but its unable to do reporting functions. When I test these functions and watch debugging I see:
SrParseV3SnmpMessage: No matching Engine ID
SrDoSnmp: authentication failure, Unknown Engine ID
I'm unsure what is casing this. I've added the snmp host with and without an engine id. Here is my current setup.
snmp-server engineID remote 10.224.219.41 udp-port 161 800000090300A47806A27EE9
snmp-server group ABCDblack v3 priv read myview access SNMP
snmp-server group svc_monitor v3 priv
snmp-server view myview iso included
snmp-server view ILMview iso included
snmp-server host 10.224.219.41 version 3 priv svc_monitor
User name: svc_monitor
Engine ID: 800000090300A47806A27EE9
storage-type: nonvolatile active access-list: SNMP
Authentication Protocol: SHA
Privacy Protocol: AES256
Group-name: ABCDblack
Any help is greatly appreciated.
05-22-2023 08:06 AM
Hello @KGrev,
"No matching Engine ID" and "authentication failure, Unknown Engine ID," suggests that there is a mismatch between the SNMP Engine IDs configured on your devices and SolarWinds.
--Ensure that the SNMP Engine ID configured in SolarWinds matches the Engine ID configured on your devices. The Engine ID is a unique identifier that must match on both ends for SNMP communication to work correctly.
--Verify the SNMP Engine ID configured on the devices. In your case, you have configured an Engine ID using the command snmp-server zngineID remote <IP_add> udp-port 161 800000090300A47806A27EE9.
Make sure that this Engine ID matches the Engine ID configured in SolarWinds.
Also, I consider that you have verified SNMPv3 credentials.
05-22-2023 12:03 PM
M02@rt37Thanks for your reply.
--Ensure that the SNMP Engine ID configured in SolarWinds matches the Engine ID configured on your devices. The Engine ID is a unique identifier that must match on both ends for SNMP communication to work correctly.
There isnt a place in solarwinds to set the engine id per device. Of note also we have many cisco switches and routers configured into solarwinds but recently a large batch of them were added. The configuration appears to be the same as the old switches but obviously something must be different for this to happen.
--Verify the SNMP Engine ID configured on the devices. In your case, you have configured an Engine ID using the command snmp-server zngineID remote <IP_add> udp-port 161 800000090300A47806A27EE9.
Each switch had its engine id manually entered based off of "show snmp user" or "show snmp engineid"
The credentials can be tested to the device within solarwinds with a test button. The test passes.
05-22-2023 08:15 AM
snmp-server enable <<- must generate automatic engine ID
please
show snmp enable
05-22-2023 12:07 PM
@MHM Cisco Worldthanks for your response.
"Show snmp enable" isnt a command on a 9400 switch. But "snmp-server enable (logging/traps)" is configured on the switch. The device does have a unique engineID.
09-21-2023 12:28 PM
@KGrev Wondering if you ever found a solution for this problem. I'm experiencing the same issue on a 9300 platform.
09-21-2023 12:50 PM
09-22-2023 05:02 AM
Thanks for the response. I may be dealing with a PEBCAK issue here, but i don't think so, given the number of times I've done this. You never know. I'll respond here for anyone else who may encounter this issue.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide