snmptrapd issue with v3 traps and reboots

[joniem]

Hello,

I'm using Nagios XI to monitor SNMPv3 traps from an external device. The traps are displayed in Nagios, so everything seems to be configured correctly in general.

It works fine until the external device reboots. After a restart, the traps reach the Nagios VM (verified with tcpdump), but they are not processed any more. Additionally disabling snmptt shows that they are also not stored in the spool folder, thus there might to be an issue with snmptrapd. After waiting a couple of minutes, it seems to be fixed automatically somehow, and the new traps are listed in Nagios again (if snmptt was enabled).

Another solution is to restart snmptrapd manually right after the external device has rebooted. In this case Nagios is also able to recognize all traps.

Using informs instead of traps does also not cause any problems after reboots.

Does anybody know why snmptrapd ignores the traps after the reboot of the external device, and how to fix it?
Thank you.

[pbroste]

Hello joniem,

Thanks for reaching out.

After the reboot, let's log the snmptrapd on that server to see what is logged.

You will need to stop or disable to snmptrapd service so you can bring it up with logging:

Code: Select all

snmptrapd -f -Le -A -Lf /var/log/snmptrapd.log

When you have captured enough events you can then break out and send the '/var/log/snmptrapd.log, over for review.

Thanks,
Perry