VMs on vSAN Datastore Displaying as Invalid on Host UI.
Article ID: 392275
Updated On:
Products
Issue/Introduction
Symptoms:
vSAN cluster shows the VMs as invalid and inaccessible.
vCenter also inaccessible as it is also hosted on the vSAN cluster.
Environment
vSAN 7.x
vSAN 8.x
Cause
The VMs running on the vSAN datastore can show up invalid or inaccessible when the backing objects are inaccessible.
The objects can go inaccessible when there is a partition created on the vSAN cluster
On checking the unicastagent list, we will see the table being incomplete in one or more ESXi hosts.
The Unicastagent table should have one entry less than the number of hosts part of the vSAN cluster.
For example:
If a vSAN cluster is of 4 nodes, the unicastagent table should have 3 entries.
If the unicastagent table has lesser entries, the partition issue can occur.
Resolution
Update the unicastagent table on the hosts showing incomplete details using the following kb Configuring vSAN Unicast networking from the command line
After fixing the unicastagent list, the partition issue will be resolved, and the objects will be back to healthy state.
Feedback
