Hi there,
we have a customer that uses two 2-node VSAN clusters in one vCenter.
vCenter Foundation
Cluster 1: 2 Servers with VSAN Witness Appliance on datacenter level
Cluster 2: 2 Servers with VSAN Witness Appliance on datacenter level
When they updated their environment, updating the ESX-Servers went smooth.
However, after they patched one of their Witness Appliances, vCenter regognized the rebooting Witness as full ESX-Host, and since vCenter Foundation can only manage 4 ESX Hosts, the Witness Appliance got disconnected which left VSAN in Error state.
The only way to solve this was to temporarily change the vCenter license to Standard and add the virtual Witness. After adding, changing back to Foundation worked without issues.
Was this a stupid coincidence or did anybody have similar issues?
I found similar things when building 2+2+1 Stretched Clusters from scratch, and the workaround was to add the Witness Appliance to vCenter before the physical hosts. However this one doesn't work in production environment.
Thanks everybody
