This article explains the vDS compliance check for hyperconverged cluster configuration check in the vSAN Health Service and provides details on why it might report an error.

When configuring a vSAN cluster via Quickstart all changes need to go through Quickstart, otherwise, if any manual changes are made to the cluster outside of Quickstart the hyperconverged warnings will be triggered in vSAN Skyline Health.

The hyperconverged warnings are mainly cosmetic and the cluster will still function with these warnings triggered.

testID: com.vmware.vsan.health.test.dvshciconfig

Q: What does it mean when it is in an error state, and how to address it?

A: This health check will validate the state of the configured distributed virtual switch and the distributed port groups in cluster setup via QuickStart.
 

Is VDS alive - if it shows 'Not compliant', it means the vDS is no longer valid per Quickstart as manual changes have been made to the vDS outside of Quickstart or the vDS has been removed. In the health check recommendation, you will find more information about the invalid vDS, such as the vDS name. Navigate to the 'Network' configuration view, and check the vDS status. Recover the vDS to the settings as configured with Quickstart if possible, otherwise, the user has to recreate the cluster with Quickstart in order for the warning to clear.

Distributed port groups - The port groups configured for the vSAN network are not valid or missing from the vDS. Navigate to the 'Network' configuration view and check the distributed port groups under the configured vDS. If the distributed port groups have been removed or changed in any way, the user has to reconfigure the cluster network settings back to what they were when configured with Quickstart.

Alternatively, you can use the Manual method for creating your vSAN cluster as this will provide more control over the configuration of your vSAN cluster.