i have a lab server which has the SNMP SERVICE running.
i have it discovered into Orion.
if I 'restart' the windows SNMP SERVICE on this server it generates an Orion event for 'Server ... rebooted'.
being curious...i did this same restart on the SNMP SERVICE at another box and it did the same exact event 'server 2 ...rebooted'.
anyone else seen this strange phenomenon with Events? or is this perhaps by design?
if so, help me to understand it's design purpose before i write any Alerts for 'reboots'.
the restarted messages go off of uptime, which is a 32 bit counter that increments every 1/10 th second. Restarting the snmp service restarts the counter. the real kicker is that after about 419 days, the counter rolls over and starts over. this will also trigger a restart message.
Restarting the snmp service restarts the counter.
Yeah, it's a real annoyance having to spend time going through the exercise of determining whether the event is the result of a real reboot, SNMP service restart or counter rollover. I'm no SNMP MIB expert but you would think that there must be another MIB variable that could be interrogated to distinguish whether the sysuptime was reset as the result of a Windows restart, a SNMP service restart or a counter rollover? I'd like to see SW find a way to fix it and revise the event message.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.