Hi, good afternoon!
I found a problem in NPM, that when I restart de SNMP Service the Networki Performace Monitor understand that the node had a reboot, because se sysuptime change to 0.
Att,
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
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,
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.
Does that get overwritten when you do an upgrade? It feels like it might be but otherwise that is a pretty slick workaround!
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.
