vSAN Health Service - Hyperconverged cluster configuration compliance alerts triggered after replacing vSAN NICs
search cancel

vSAN Health Service - Hyperconverged cluster configuration compliance alerts triggered after replacing vSAN NICs

book

Article ID: 394266

calendar_today

Updated On:

Products

VMware vSAN VMware NSX

Issue/Introduction

vSAN Skyline Health is reporting alerts pertaining to Hyperconverged cluster configuration compliance

NICs were replaced/added to the host changing the vSAN network configuration that was created via Quickstart

vSAN cluster was created with Quickstart

Environment

VMware vSAN (All Versions)

VMware NSX 4.x

Cause

https://techdocs.broadcom.com/us/en/vmware-cis/vsan/vsan/7-0/vsan-planning-and-deployment/creating-a-virtual-san-cluster/using-quickstart-to-configure-a-vsan-cluster.htmlThis is caused due to once a vSAN cluster is created via Quickstart you can't make any changes to the cluster outside of Quickstart as the cluster will be come non-compliant to the Quickstart workflow. Which triggers the Hyperconverged cluster configuration compliance warnings in vSAN Skyline Health.

Resolution

There are three options for resolving this.

  1. Consider creating your vSAN cluster manually as this gives you more configuration control of your cluster compared to using Quickstart
  2. Silence the Hyperconverged warnings in vSAN Skyline Health as these are mainly cosmetic warnings and your cluster will still function
  3. Create a new cluster in vCenter, enable vSAN, Skip Quickstart, and 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 in use 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.

    Following these steps:

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

    2. Verify settings of old cluster, then create a new cluster with identical settings to the old one. (Deduplication and compression,  encryption, advanced options, etc.) 

    3. SSH into each host and run the following command to avoid any potential partitions: esxcfg-advcfg -s 1 /VSAN/IgnoreClusterMemberListupdates

    4. Disconnect each host from the old cluster. Then drag each disconnected host up into the new cluster. (Run esxcli vsan cluster get each step to make sure no partitions are happening if desired.)

    5. Once all hosts moved to new cluster, right click and re-connect into the new cluster. 

    6. Navigate to cluster > monitor > skyline health and 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. 

    7. Verify that is the only alarm being triggered and that are configurations are correct and identical between old cluster and new. 

    8. SSH into hosts and reverse step 3: esxcfg-advcfg -s 0 /VSAN/IgnoreClusterMemberListupdates

    9. Navigate back to skyline health, click 'troubleshoot' on vCenter state is authoritative alarm. Then click 'remediate inconsistent configuration.' 

    The cluster should now be in working order without the 'Host compliance check for hyperconverged cluster configuration' alarm being triggered. 

Additional Information

Powered by Wolken Software