VMware vSphere 5.5, vSphere 5.1 and vSphere 5.0 offer an integrated monitoring of the existing server hardware. The status of these components is checked by VMware through already built-in checks (eg for IPMI sensors) and corresponding CIM providers, such as for hardware RAID controllers. The Plug-in checkesxihardware.py allows for easy monitoring of hardware components with Nagios or Icinga.
We're running a large production cluster of ESXi 5.5 and vCenter server 5.5 and starting last night at around 8pm hosts decided to start sending off alarms about being unable to talk to our vCenter server.
I plan on putting in a ticket but I'm wondering if anyone has experienced something similiar. So far the only information I've found is a kb article related to 4.0, 5.0, and 5.1 stating that the vpxa service isn't able to talk to the vCenter and that there is a patch for those versions and that all other versions to just disconnect the host manually and reconnect it.
It appears the only fix at this time was to reset my vcenter virtual machine and everything reconnected. Could this be something to do with my vcenter database?
Thanks,
EDIT: Could heat have caused this but not thrown any hardware alerts? the temperature in our server room climbed to 82F last night before our maintenance people were able to get the 3rd air handler back online and I was told the rack containing all our UCS gear was blowing hot air out but sucking plenty of cool air in. Could the hardware have decided to slow its self down so much to lower temps that everything started to crawl?
![Esxi 5.5 hardware monitor service on this host tv Esxi 5.5 hardware monitor service on this host tv](http://cdn.techgenix.com/media/upls/Monitoring%20vSphere%20Virtual%20Machines%20in%20the%20vSphere%20Web%20Client%20-%20Part%201-fig1.jpg)