I’ve seen this one on the VMTN forum a couple of times. When the Health Status isn’t showing you could do the following to fix it:
- Restart VirtualCenter service on the VC Server
- Restart mgmt-vmware service on the hosts that are affected (service mgmt-vmware restart)
- Restart vmware-vpxa on the hosts that are affected (service vmware-vpxa restart)
If the above did not fix the issue:
- Disconnect the affected Host from Inventory on VC
- Reconnect the affected Host from Inventory on VC
And if that doesn’t work this is also a possible solution:
- Restart the Pegasus service (service pegasus restart)
vSphere 4.0 Quick Start Guide
When this happens for me I go to the top-most level of alarms and adjust one of the two preset VM alarm Definitions in the Yellow trigger by one and then the grey health marks change to where they should be.
Thanks for the great information! Saved me some searching today!
http://www.vmwareinfo.com/2008/08/missing-health-status.html
Disconnecting and reconnecting fixed it for me.
We had just updated VC and ESX to 2.5U2 and 3.5U2 respectively, so all services had just been restarted.
The hosts may go through and inventory process as part of their being connected that creates the health objects.
This issue is fixed via adding the Alarm to heartbeat VM.
And allso combined with an alarm to monitor a VMs State will help determine the satyus of the VM, not the Host..
If you are running HP Proliant or blade hardware it is also worth checking your BIOS revision. We had a number of BL4xx blades which would not show the health status. Updating the BIOS solved this.
Disconnecting / reconnecting only seems to partially fix the issue for me. Only 3 of the hardware monitors are shown. Reinstalling the cim/pegasus rpms solved the problem.