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

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

book

Article ID: 315505

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

This article explains the Cluster Health - vSphere cluster members match vSAN cluster members check in vSAN Health Service and provides details on why it might report an error.




Environment

VMware vSAN (All Versions)

Resolution

Q: What does the Cluster Health - vSphere cluster members match vSAN cluster members test do?

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

Q: What does it mean when it is in an error state?

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.

Q: How does one troubleshoot and fix the error state?

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:

Scenario 1:

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

Refernce KB: Permanently Decommissioning a node from a vSAN Cluster

Scenario 2 :
Host is part of the vSphere Cluster but not joined to vSAN Cluster, in this scenario we should join the affected Node back to vSAN Cluster using below cmd

esxcli vsan cluster join -u uuid 

Reference KB : How to add a host back to a vSAN cluster after an ESXi host rebuild/reimage




General Validation Steps:

  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 Broadcom Support.

 

Additional Information

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

Also, see:

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

Attachments

VMware-Ruby-vSphere-Console-Command-Reference-For-Virtual-SAN.pdf get_app