vSAN -- Hyperconverged Cluster Configuration alarm "Host compliance check for hyperconverged cluster configuration" / "VDS compliance check for Hyperconverged Cluster Config"

Products

• VMware vSAN 7.x
• VMware vSAN 8.x
• VMware vSAN

Issue/Introduction

Symptoms:

• Despite not having any vSAN issues with Functionality and/or Configuration, vSAN Health is showing one or both of the following alerts:

- VDS compliance check for Hyperconverged Cluster Config
- Host Compliance Check for Hyperconverged Cluster Config

• No other Alerts are shown in regards to Network
• In some cases, the alerts might only show up since the Environment was upgraded from 7.x to 8.x

 

Example Screenshots:

 

 

 

 

Environment

vSAN 7.x
vSAN 8.x

Cause

The vSAN cluster was originally created using Quickstart. Later there were changes made in the cluster like Networking related configuration changes or hosts added to the cluster not using Quickstart.. 

Once the Cluster is configured through Quickstart, you cannot use Quickstart to modify the Cluster Network configuration.

When expanding the cluster the new hosts need to be added via Quickstart.

 

If any of the stored information is changed, QuickStart loses the ability to expand the cluster and the warning appears.

This does not impact any functionality of vSAN or configuration changes made on cluster.

Resolution

A.) Recommended Solution: Silence any vSAN Health Alarm referring to "Hyperconverged Cluster Configuration"

 

 

B.) If silencing the alert is not desired, create a new identical Cluster in the vSphere Client, skip Quickstart, then move the Hosts to the new Cluster.

Notes:

• This is not recommended if using Horizon or any other application that auto deploys VMs as it will require re-configuration with the new Cluster.
• If NSX is used, make sure Transport Node Profiles are in use otherwise this will result in NSX getting uninstalled from the Hosts. Transport Node Profiles (TNP) allows for Hosts to be able to move from one Cluster into another Cluster within the same vCenter without the NSX getting uninstalled from the Hosts.

 

Steps to create a new identical Cluster in the vSphere Client:

 

1.) Re-name current Cluster and add -old to end of it

2.) Verify the settings of the old Cluster and then create a new Cluster with identical settings ( e.g. Deduplication and Compression, Encryption, Advanced options, etc.) 

3.) SSH into each vSAN Host and run the following command to avoid any potential partitions:

esxcfg-advcfg -s 1 /VSAN/IgnoreClusterMemberListupdates

 

4.) Disconnect each vSAN Host 

5.) Drag each disconnected vSAN Host into the new Cluster

(If desired, verify Cluster Membership by running esxcli vsan cluster get on each Host)

 

6.) Once all vSAN Hosts have been moved to the new Cluster, right click each vSAN Host and select "connect" 

7.) Navigate to Cluster --> Monitor > vSAN Health

All alarms should be the same as before except for the following will be triggered: vSAN Skyline Health Service - Cluster health – vCenter state is authoritative

This is expected due to the Advanced configuration that was set in Step 3. 

Verify that this is the only Alarm being triggered and that configurations are correct and identical between old and new Cluster. 

 

8.) SSH into the vSAN Hosts and reverse Step 3 by executing on each:

esxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListupdates

 

9.) Navigate to Cluster --> Monitor > vSAN Health
Click 'Troubleshoot' on the Alarm "vCenter state is authoritative" and click "Remediate Inconsistent Configuration"

The Cluster should now be in working order without the appearance of any Alarms referring to "Hyperconverged Cluster Configuration"