False Reboot When SNMP Service Restart

This may disable the alert but Orion still reports that the device rebooted anyway, for example in the "Last events" section.

After modifying the alerts, it no longer triggers, but Orion still reports it rebooted.

Does that get overwritten when you do an upgrade?  It feels like it might be but otherwise that is a pretty slick workaround!

You can modify or disable the Alert called "Alert me when a node Lastboot changes" AND Disable EventType 14 (Node Rebooted) events by running the following SQL Query:

UPDATE EventTypes SET Record=0 WHERE EventType = 14

I tested this and the above query does indeed stop the pesky alerts which are confusing my end users because it says the node rebooted but the node did not reboot, it was just that the SNMP Agent was cycled.

arodrigo.oliveira@gmail.com This is a known "issue" with NPM, but it is based on some decent logic.  If the SNMP service restarts then it was likely due to a server reboot, but I agree that it does cause some problems.  I would build a custom poller (universal device poller) for the hrSystemUptime OID (OID repository - {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) host(25) hrSystem(1) hrSystemUpt…) and replace assign it to your nodes using Settings > Manage Pollers.

There is a really good discussion on this issue over at https://thwack.solarwinds.com/ideas/1703.

Gino, good morning!

You don´t understand.

When I restart de SNMP service in the server, the NPM understand that was a reboot. The last reboot in the server change in the NPM, but was only reboot on the SNMP service.

Regards,

Rodrigo Almeida.

For node reboot alerts there should be other criteria besides SNMP being restarted. NPM could also look at uptime and maybe log files are well. It could also do a ping to verify that the node is really offline or not.

Maybe this could be added for node down verification before an alert is generated.

HTH,

Gino