201, vCenter

VSAN and vSphere 6.5…

There is a not so nice feature in vSphere 6.5 which makes VSAN explicitly dependent on vCenter. It is detailed in the release notes but easily overlooked… http://pubs.vmware.com/Release_Notes/en/vsan/66/vmware-virtual-san-66-release-notes.html

Fixed in the latest update of vSphere/vCenter, but just be aware of the following steps before bouncing vCenter for maintenance or upgrade…

Rebooting, restoring, or replacing the VC server can cause cluster partitioning:

If the vCenter Server is replaced or recovered from backup, the host membership list might become out-of-date. This can cause ESXi hosts to become partitioned from the cluster.

Workaround: Use the following procedure to make sure all hosts are added to the vSAN cluster as the vCenter Server reboots.

Before you reboot vCenter Server, configure hosts to ignore cluster member list updates. Run the following command on each host in the vSAN cluster:

# esxcfg-advcfg -s1 /VSAN/IgnoreClusterMemberListUpdates

After vCenter Server is running and all hosts are present in the cluster, configure hosts to use cluster member list updates. Run the following command on each host in the cluster:

# esxcfg-advcfg -s0 /VSAN/IgnoreClusterMemberListUpdates

Refer document : https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.virtualsan.doc/GUID-7799D2D7-2513-4372-92EA-4A1FB510E012.html

Related Posts
NSX-vSphere 6.2 VIB’s and VXLAN Troubleshooting
NSX Multi Hypervisor and NTP
NSX Multi Hypervisor using vSphere ESXi