A vSAN network partitioned host is the only host HA protected
Article ID: 402529
Updated On:
Products
Issue/Introduction
A host in a vSAN cluster is network partitioned from the other hosts. It cannot reach the other hosts on the vSAN network with ping as well as unable to receive vSAN traffic.
HA is enabled at the cluster level and the other hosts timeout in vCenter tasks when attempting to enable, while the network isolated hosts succeeds the enabling.
Environment
vSAN 7.x
vSAN 8.x
Cause
The partitioned vSAN host was picked up as vSAN network partition 1 and considered its own vSAN and HA cluster leader/primary.
When vSAN is enabled the vSAN network is used as the HA network.
When a host is found to be the HA primary node only other hosts clustered with it on the HA network will be enabled for HA regardless of how they are placed into a vSphere cluster.
When a host is isolated in its own vSAN network partition and detected to be the HA primary of its cluster, other hosts in the vSphere cluster cannot enable HA as they are not part of that HA cluster.
Resolution
Place the vSAN network partitioned host into maintenance mode. Leave the host in maintenance mode until the underlying network partition issues are resolved.
When a host is in maintenance mode it is disabled for HA. This allows the other hosts to be enabled as the isolated host is no longer eligible to utilize HA and excluded from the process.
It may be necessary to disable and re-enable HA once the partitioned host is in maintenance mode to resolve the issue for the other hosts.
Additional Information
Feedback
