Friday, June 2, 2017

"No host data available" error in the Hardware Status

So having upgraded our environment and several of our customers as well to vSphere 6.5, we realized that the Hardware Status button under the Monitor tab for the ESXi 6.5 hosts are showing "No host data available" for the sensors.

Well apparently this is a known issue as VMware has created KB 2148520 in relation to it.
Apparently, after upgrade, there is a stale Service ID that needs to be removed.

Here are the steps from the KB.  Below are my screenshots showing the actual steps:

This is a known issue affecting the vCenter Server 6.5.
Currently, there is no resolution.
To work around this issue, remove the stale serviceID:
  1. From a Web browser, connect to the vCenter Server Managed Object Browser (MOB) at:
  2. Login as the administrator@vsphere.local user.
  3. Click Search.
  4. Edit the Value column to only have these lines:


  5. Click Invoke Method.
  6. Press Ctrl+F and search for cis.vws.servicename.
  7. Copy the serviceID string directly above cis.vws.servicename.

  8. Exit this window.
  9. Click UnregisterService.
  10. Under the Value column, enter the string copied in step 7.
  11. Click Invoke Method.

 My Steps in pictures:

The link for the KB Is here:

  "No host data available" error in the Hardware Status tab after upgrading to vCenter Server 6.5
Let us know how this works for you.

Friday, May 5, 2017

The Vitual SAN host cannot be moved to the destination cluster: destination cluster vim.ClusterComputeResource:domain-### is Virtual SAN disabled

So today while I was teaching class, a student created an interesting problem.  We were doing a lab on DRS where they create a single Host Cluster for DRS and all add their hosts.

Well, one student created his own cluster, apparently checked the box for VSAN cluster in the process, added his host to it, then realized he was supposed to be in the "shared" DRS Host Cluster.

He deleted the cluster he had created, re-added his host to vCenter and when he tried to move his host into the DRS Cluster, he got the following error:

It turns out there was a VSAN datastore created with no disks in it and, his host still had an affiliation with the VSAN Cluster that no longer existed.

To resolve the problem we did the following:


  1. From Storage inventory view in vCenter, verify a VSAN datastore still exists.
  2. If it does, Putty into the ESXi host or access it via its ESXi Shell & execute the command:
    esxcli vsan cluster get
  3. If results appear, proceed to the solution ...


  1. From previous command line (SSH or ESXi Shell) to the affected host, execute the following command:
    esxcli vsan cluster leave
  2. Now add the host to the existing Host Cluster...
Both Verification and Solution steps together look like this:

Wednesday, April 26, 2017

vCenter Server Windows & VCSA 6.5.0d is Out!!

Well that was fast... 5 days after the release of VCSA 6.5.0c, comes 6.5.0d for both Windows & Photon OS versions of vCenter.

Primary reason is bug fix support for VSAN 6.6 that was just released.

What's New

The vCenter Server 6.5.0d release includes new features and bug fixes related to vSAN 6.6. For more information, see the vSAN 6.6 Release Notes and the vSAN 6.6 documentation.

The new build is:
 Name: VMware-VCSA-all-6.5.0-5318154.iso
Release Date: 2017-04-18
Build Number: 5318154

The new patch is: