After creating the new vDS ,Skyline health reported an error " Distributed port groups: Not Compliant"

Products

• VMware vSAN

Issue/Introduction

Following error noticed on Vcenter under skyline health troubleshoot section:

Distributed Port Group on Distributed Switch ######## is missing. 

Environment

ESXi 8.X

Cause

The issue observed with vSAN quickstart configuration guide. Since the original VDS was created using vSAN quickstart configuration guide and then new VDS was created following which the skyline alert says that it's not matching the configuration of original VDS.

 

Resolution

 Follow this Step-by-Step guide:

1. Create new Cluster on same vcenter, enable VSAN same as original VSAN cluster

2.  Run the following command on all nodes in the cluster to temporarily ignore "Cluster Member List Updates" coming from vCenter.

          ^{esxcfg-advcfg -s 1 /VSAN/IgnoreClusterMemberListUpdates}

          Note: If this step is skipped then cluster will report network partition

 

3. Disconnect host from old cluster and drag drop host to new cluster on vcenter.

4. Connect host back to vcenter in newly created cluster, after reconnect all VMs associated with host become available.    

5. Validate the Host which was just moved into the Cluster

• Log into via SSH/Putty and run: esxcli vsan cluster get
• Make a note of the "Sub-Cluster: Member Count".
• It should reflect the number of Hosts showing in the Web Client under the vSAN Cluster.
• If there is a mismatch, then the newly added Hosts cannot communicate to the other Hosts. Check step 2, do not move remaining host till issue get resolve,
• do not proceed with the next steps, instead proceed with opening a Ticket with VMware by Broadcom Support.

         Sample output

^{root@esx01] esxcli vsan cluster get
Cluster Information
Enabled: true
Current Local Time: 2025-04-01T17:09:04Z
Local Node UUID: #########-####-####-####-########
Local Node Type: NORMAL
Local Node State: MASTER
Local Node Health State: HEALTHY
Sub-Cluster Master UUID:#########-####-####-####-########
Sub-Cluster Backup UUID: #########-####-####-####-########
Sub-Cluster UUID: #########-####-####-####-########
Sub-Cluster Membership Entry Revision: 1
Sub-Cluster Member Count: 5   <=========================================
Sub-Cluster Member UUIDs: #########-####-####-####-########, #########-####-####-####-########,#########-####-####-####-########, #########-####-####-####-########, #########-####-####-####-########0
Sub-Cluster Member HostNames: esx01,esx02,esx03,esx04,esx05
Sub-Cluster Membership UUID: #########-####-####-####-########
Unicast Mode Enabled: true
Maintenance Mode State: OFF
Config Generation: #########-####-####-####-######## 2024-04-01T10:11:03.006
Mode: REGULAR
vSAN ESA Enabled: true}

 

• If any disconnected host reported any issue during  drag drop to the new cluster then  power off VMs belonging to that      host and unregister from inventory  and try to move, after successfully moving registered back all vms or move to another host of cluster.
• If no issue is reported on host movement across the cluster then please proceed with remaining hosts and perform step4 for validation.

6.Apply license to newly created VSAN cluster

7.Once all Hosts have been successfully added to the new Cluster,On each vSAN Host, log into via SSH/Putty and run the following command  to enable the "Cluster Member List Updates" again on all the nodes in the cluster

^{esxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListUpdates}

 

Additional Information

vSAN Health Service - Hyperconverged cluster configuration compliance - vDS compliance check for hyperconverged cluster configuration