vSAN Health Service - Cluster Health - vSphere cluster members match vSAN cluster members

Products

• VMware vSAN

Issue/Introduction

This health check validates that the hosts in the vSphere cluster matches the hosts in the vSAN cluster.



If this check fails, it means that vSphere cluster members are not identical to the vSAN cluster members.

This issue might occur when vSAN is not enabled on certain hosts in the vSphere cluster, or when certain hosts in the vSAN cluster are not managed by the vSphere cluster.

If this health check fails, several cluster configuration operations might fail or not complete properly for each host in this cluster, leading to inconsistent states between hosts.

Environment

VMware vSAN 7.#

VMware vSAN 8.#

Resolution

1. Validate the correct number of hosts in the cluster by visualizing the vCenter UI.
2. Validate if there are no other vSAN Health alarms via vSAN Health.
If the issue does not automatically resolve, please contact VMware Support.

For more information on collecting VMware vSAN logs, see Collecting vSAN support logs and uploading to VMware by Broadcom.

Also, see:

• vSAN Monitoring and Troubleshooting
• VMware Ruby vSphere Console Command Reference for vSAN (Attached to this KB)
• VMware vSAN Design and Sizing Guide

See KB vSAN Skyline Health Check Information for a complete list of vSAN Skyline Health checks

Additional Information

Hosts that are not matching their vSphere Cluster and vSAN Cluster membership can be determined by navigating to: Cluster level > Monitor > Skyline Health, as seen in the screenshot below:

In this scenario, user should remove the affected host from the vSAN cluster and then re-add it to the cluster to resolve the issue.