Warning "Host is in a vSAN cluster but does not have vSAN service enabled" seen in the Summary Tab of the ESXi host

Products

• VMware vSAN

Issue/Introduction

Host(s) in vSAN cluster displays error message:

"Host is in a vSAN cluster but does not have vSAN service enabled"

Environment

VMware vSAN (All Versions)

 

Cause

• The warning "Host is in a vSAN cluster but does not have vSAN service enabled" typically gets triggered during the configuration of vSAN when the cluster in vCenter has been configured for vSAN but the hosts are mid process of being configured but the warning should clear once the task completes.
• vSAN Cluster UUID is out of sync between vCenter and ESXi
• In very rare circumstances this warning fails to clear. 

 

Resolution

• Confirm vSAN is configured correctly on all hosts in the cluster as per vSAN Planning and Deployment. If anything is not configured correctly correct the vSAN configuration for the impacted host and the warning should clear.
• If vSAN is configured correctly and functioning upgrade vCenter to 8.0U1 as this warning has been deprecated.
  Note: If the environment is VxRail or SDDC a full environment upgrade to 8.0U1 may be required. 
• If confirmed the vSAN cluster is configured correctly and functioning without issue this warning can be safely ignored as it's just cosmetic if an upgrade to 8.0U1 is not possible at this time.
• If an upgrade to 8.0U1 is not possible ensure the vSAN cluster is healthy and no inaccessible objects, then make a small configuration change to the host(s) with the warning such as un-tagging/retagging the vmk for vSAN or a change in the fault domain. This will trigger vCenter to recalculate the vSAN configuration between vCenter and ESXi.
  Note: If multiple hosts are showing this warning ensure to make the configuration change one host at a time ensuring the vSAN reconfiguration tasks complete on one host before continuing on to any other hosts.
• To confirm if the vSAN Cluster UUID is out of sync between vCenter and ESXi and to resolve this if it is follow KB vSAN Cluster UUID not in sync between vCenter and ESXi
  Note: If all hosts in the cluster are displaying the warning "Host is in a vSAN cluster but does not have vSAN service enabled" then it's a good indicator that potentially the vSAN Cluster UUID is out of sync between vCenter and ESXi.

 

Additional Information

vSAN Network Design

After upgrade to ESXi 7.0 U1, vsanperf daemon no longer starts citing 'No module named 'urllib3' During handling of the above exception'