SNMP V3 Listener will not receive traps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-24-2019 12:11 PM
We have setup a V3 SNMP Trap Listener configured with Security Level: noAuthNoPriv.
We have tested sending test traps from a storage application to this listener IP address using No Authentication, but we get an ERROR > TEST SNMP Failed: Wrong user name.
The Storage application requires a Security user name configuration to send the traps. We have tested using the following Security User Names: public, noAuthUser, and created test credentials that were created in the MidServer which were used as the user name still receiving the same error. TEST SNMP Failed: Wrong user name
Has anyone come across this issue or know what Security User Name should be used to send the v3 traps?
Thanks,
Dan
- Labels:
-
Event Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-19-2020 03:32 PM
Hi,
Did you manage to get this working? We have a similar issue where SNMP traps with SNMP V3 not working.
Your feedback will be appreciated.
thx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-21-2020 08:39 AM
No, we were never able to get this SNMPv3 processing in Event Management correctly. We figured it may have been a configuration issue from the source/application, but the users continue to monitor from their consoles and email created from that source.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-22-2020 02:51 PM
Hi All,
its important to note whether or not you're sending SNMPv3 traps or informs - here is a good explanation taken from an outside source ::
SNMP V3 traps and informs are both forms of SNMP notification however the difference is in who is deemed to be the 'authoritative engine'.
In SNMP the authoritative peer must know the engineId of the authoritative peer to successfully communicate.
When a TRAP is used, the SENDER is the Authoritative engine and therefore the receiver must be aware of the senders engineId.
When an INFORM is used, the RECEIVER is the Authoritative engine and therefore the sender must be aware of the receiver's engineId.
so in order to send us informs, when the snmpv3 listener is up and running (via your instance), you'll note the engineID that is displayed on the form - this needs to be given to whomever is sending the inform.
Let me know if this helps.
Thanks,
-Ryan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-22-2020 03:48 PM
Hi Ryan,
One of our client's configred Oracle OEM to send SNMP traps via SNMP v3 and it didn't work. Once we configured OEM to send SNMP v1/v2 the traps arrived into instance.
Is SNMP traps works with SNMP v3 at all? Why there is no ServiceNow docs about it at all and no docs on what you are saying?
Regards