vSAN -- vSAN Healthcheck -- Host compliance check for hyperconverged Cluster configuration (58896)
search cancel

vSAN -- vSAN Healthcheck -- Host compliance check for hyperconverged Cluster configuration (58896)

book

Article ID: 326900

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

Q: What does it mean when it is in an error state?
A: If this check fails, it indicates at least one Host in the vSAN Cluster is not compliant with the hyperconverged Cluster configuration.
See below for details on which Configurations this check will validate and how to address reported issues.

Related TestID (if needed): 
com.vmware.vsan.health.test.hosthciconfig


Environment

VMware vSAN 8.0.x
VMware vSAN 6.7.x
VMware vSAN 7.0.x

Resolution

Screenshot of Healthcheck Warning showing the various Host Compliance categories where it can fail.
Notice the column "Recommendation" to retrieve further details.





1.) "Configured for Cluster" shows "No" 
New Host added to the Cluster should be configured via QuickStart which is to apply HCI specifications to the Host. 
If that was not done, the Compliance Check will show "Configured for Cluster" with "No" along with a yellow Warning.

To address this:
Navigate to "QuickStart", and click "configure", follow the steps to apply HCI configurations to Host.
Click "Retest" to rerun the vSAN Healthcheck to evaluate if the "Host compliance check for hyperconverged Cluster configuration" has now turned to green (= resolved).

QuickStart can be accessed in the Web Client via (select installed Build):
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vsan-planning.doc/GUID-CF9767B6-B3F5-4787-9AF3-D661987AE525.html


2.) "Distributed Switch" shows "No" 
All Hosts should attach to the same virtual Distributed Switch, which is created via QuickStart. 
If that is not the case, the Compliance Check will show "Distributed Switch" with "No" along with a yellow Warning.

To address this:
Add the Host mentioned in the Warning to the same virtual Distributed Switch the other vSAN Hosts are assigned to:
Right-click on the related Distributed Switch select 'Add and Manage Hosts...', then add the 'Not compliant' Host. 
Click "Retest" to rerun the vSAN Healthcheck to evaluate if the "Host compliance check for hyperconverged Cluster configuration" has now turned to green (= resolved).

See here on how to add Hosts to a Distributed Switch (select installed Build):
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.networking.doc/GUID-E90C1B0D-82CB-4A3D-BE1B-0FDCD6575725.html


3.) "VMkernel adapters" shows "No" 
vSAN enabled VMkernel adapters should be present and on the correct Distributed Switch Port groups. 
If that is not the case, the Compliance Check will show "VMkernel adapters" with "No" along with a yellow Warning.

To address this:
Navigate to the Host -> Configure -> VMkernel adapters
and configure vSAN vmknic with correct Distributed Switch and Port Groups.
Click "Retest" to rerun the vSAN Healthcheck to evaluate if the "Host compliance check for hyperconverged Cluster configuration" has now turned to green (= resolved).

See here on how to configure vSAN VMKernel Networking (select installed Build):
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vsan-planning.doc/GUID-6989ECAC-B485-4ACC-BA97-09E440A36A4E.html
https://kb.vmware.com/s/article/2058368


4.) "NTP setting" shows "No"
NTP setting should be identical on all vSAN Hosts.
If that is not the case, the Compliance Check will show "NTP setting" with "No" along with a yellow Warning.
If NTP has not been configured via QuickStart, the Health check will not validate the NTP compliance status, then the User can configure it on the Host later.

To address this:
Configure NTP on vSAN Host to match with other vSAN Hosts.
Click "Retest" to rerun the vSAN Healthcheck to evaluate if the "Host compliance check for hyperconverged Cluster configuration" has now turned to green (= resolved).

See here on how to configure NTP (select installed Build):
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcenterhost.doc/GUID-8756D419-A878-4AE0-9183-C6D5A91A8FB1.html


5.) "Lockdown mode" shows "No"
Lockdown mode setting should be identical on all vSAN Hosts.
If that is not the case, the Compliance Check will show "Lockdown mode" with "No" along with a yellow Warning.

To address this:
Configure the Lockdown mode on vSAN Host to match with other vSAN Hosts.
Click "Retest" to rerun the vSAN Healthcheck to evaluate if the "Host compliance check for hyperconverged Cluster configuration" has now turned to green (= resolved).

See here on how to configure Lockdown mode (select installed Build):
https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.security.doc/GUID-88B24613-E8F9-40D2-B838-225F5FF480FF.html

See here for additional information:
https://kb.vmware.com/s/article/1008077