Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

False alerts saying ESXi 6.5 hosts have rebooted

shattori

Ever since we upgraded to vSphere 6.5, we keep getting random alerts saying the host has rebooted.

It happens randomly but to all 6.5 hosts and we have confirmed that is not the case.

I ran across this article saying that it's an SNMP Timetick issue:

False reboot alert for specific node - SolarWinds Worldwide, LLC. Help and Support

However, there is no section for VMware and the custom UnDP did not resolve this issue.

Any ideas on how to fix this?

Find more posts tagged with

Accepted answers

rharland2012

Does this sound similar to your issue? I think it would create the same notification. You could verify by checking snmpd status on a host that has fired the reboot notification.

SNMPd stops on ESXi 6.5 | VMware Communities

All comments

shattori

I have an open case on this. No one has been able to resolve it, it's been escalated up a few levels at this point and am waiting on a response.

rharland2012

Does this sound similar to your issue? I think it would create the same notification. You could verify by checking snmpd status on a host that has fired the reboot notification.

SNMPd stops on ESXi 6.5 | VMware Communities

shattori

There are no logs stating out of memory or anything related to snmpd on the hosts.

rharland2012

Okay. Replication attempt time, then.

Restart the snmpd daemon on one of the problem hosts and verify that you get the bogus reboot alert. Just a sanity check - I'm very close to sure this will in fact trigger the reboot alert on the next poll.

When I walk to 1.3.6.1.2.1.25.1.1 (the UnDP referred to in your original post) on my 6.0 hosts, it reflects the appropriate value - but if snmpd restarts, I would imagine this counter will reset as well. That might explain why you didn't get a fix out of it.

Barring better info from Solarwinds, my assumption has been that ESXi hosts' uptime when polled via SNMP is reported using a standard OID, but I could be wrong there.

Re logging - you may need to up the loglevel for snmpd on the host to get meaningful info out of the logs.

Anyway, it certainly sounds like either a) snmpd is restarting due to bug or some other issue or b) SW polling is looking at the wrong counter for uptime. I sort of doubt the latter, but it's good to know for sure.