Hi Emilio,
Let me share my experience here.
I have observed that to receive a V3 Trap with net-snmp library, its Engine
ID need to be defined in the snmptrap.conf file of the reciever. Otherwise
the trap is not identified by usm engine.
I am also stuck for a solution where I can recieve SNMPv3 tr
Since there is no SNMP engine ID discovery being performed for SNMPv3 TRAP
messages, your Notification
Receiver must have [the authoritative] SNMP engine ID of your Notification
Originator explicitly configured
to its LCD. Technically, it’s engineID + username.
In other words, there is no need t
Some news about my issue: it seems something related to engine ID.
If I'm going to send the same V3 trap to two peers I have to define two
unique engine IDs (one for each remote peer) in my trap sender.
If I use the same engine ID only the first trap sending works.
Someone could confirm this?
Thank
Hi,
following my code used in order to send the same V3 trap to multiple hosts.
Now, this is en example scenario: Host #1 with wrong V3 credentials Host #2
with correct V3 credentials
V3 trap not sent to host #1 => OK because I've wrong credentials V3 trap
*not* sent to host #2 => NOK because I'
