Hi Paul,
I too have observed this that trapsess directive, was requiring the engine-id
for properly sending the traps. Otherwise, though we were able to generate and
send the traps from our device, but they were not able to be detected at the
receiving manager. Once we gave the engine-id of
Version: 5.7.2
Hi all,
I'm currently experiencing strange behaviour while experimenting with
SNMPv3 traps. Every time I define a trapsess directive like followed I get
an error about an unknown user:
trapsess -v3 -u trapuser -l authPriv -n -a MD5 -A authPass1 -x AES -X
privPass1 192.168.2.240
