The storage views tab in the vSphere client disappeared, and vCenter System Services displayed some of the following errors: unable to retrieve health data from https://localhost:443/vsm/health.xmlunable to retrieve health data from https://localhost:443/eam/eamService-web/health.xmlunable to retrieve health data from https://localhost:443/SMS/health.xml VMware KB article 2016177 (vCenter Server Health status reports the error: Error retrieving health from url (2016177)) had the fix. This issue & kb is only for vCenter 5.
Everyone else has done one, so I hope there’s something unique that comes out of this.
The Study I made some notes as I was studying for VCAP-DCA, so these may not necessarily reflect what was on the exam.
I found an awesome ESXTOP poster at vmworld.net. No idea how I hadn’t come across this before.
I’d never really used esxcli much. I’d cut & paste esxcfg/vicfg lines that I’ve been hanging on to, but these commands were mainly for ESX3/4.
By accident while in Cluster Settings / Datastore Heartbeating, I noticed a datastore wasn’t available of one of the hosts.
Trying to mount it from the vSphere client failed with a popup:
Call “HostStorageSystem.ResolveMultipleUnresolvedVmfsVolumes” for object “storageSystem-326” on vCenter Server “vcenter” failed.
The command to force mount a snapshot that is persistent has changed from ESX(i)4.x to ESXi5.0.
The details are at http://kb.vmware.com/kb/1011387.
Use SSH or ESXi Shell and run: