Skip to content

How to silence VMware vSAN Health Checks

A new feature in vSAN 6.6 is the ability to silence Health Checks. In previous versions, it was already possible to disable alerts that are triggered by health checks. Silencing health checks is one step further and enables you to have a clean vSAN health. Silenced checks are displayed with a green checkmark and are marked as "Skipped".

Especially for home labs, where unsupported hardware is used, this is a great feature.

Currently, it is not possible to silence health checks with the vSphere Web Client and it is not described in the documentation. The feature is available in the RVC or by using the vSAN Management API. This article is focused on the RVC. If you are unfamiliar with RVC, see this article.

Add a check to the silent list: -a <Check ID> <CLUSTER>

Remove a check from the silent list: -r <Check ID> <CLUSTER>

The following Check IDs are available:

Description Check ID
Cloud Health
Controller utility is installed on hostvendortoolpresence
Controller with pass-through and RAID disksmixedmode
Customer experience improvement program (CEIP)vsancloudhealthceipexception
Disks usage on storage controllerdiskusage
Online health connectivityvsancloudhealthconnectionexception
vSAN and VMFS datastores on a Dell H730 controller with the lsi_mr3 drivermixedmodeh730
vSAN configuration for LSI-3108 based controllerh730
vSAN max component sizesmalldiskstest
Advanced vSAN configuration in syncadvcfgsync
Deduplication and compression configuration consistencyphysdiskdedupconfig
Deduplication and compression usage healthphysdiskdedupusage
Disk format versionupgradelowerhosts
ESXi vSAN Health service installationhealtheaminstall
Resync operations throttlingresynclimit
Software version compatibilityupgradesoftware
Time is synchronized across hosts and VCtimedrift
vSAN CLOMD livenessclomdliveness
vSAN Disk Balancediskbalance
vSAN Health Service up-to-datehealthversion
vSAN cluster configuration consistencyconsistentconfig
vSphere cluster members match vSAN cluster membersclustermembership
vSAN VM healthvmhealth
vSAN object healthobjecthealth
CPU AES-NI is enabled on hostshostcpuaesni
vCenter and all hosts are connected to Key Management Serverskmsconnection
Hardware compatibility
Controller disk group mode is VMware certifiedcontrollerdiskmode
Controller driver is VMware certifiedcontrollerdriver
Controller firmware is VMware certifiedcontrollerfirmware
Controller is VMware certified for ESXi releasecontrollerreleasesupport
Host issues retrieving hardware infohclhostbadstate
SCSI controller is VMware certifiedcontrolleronhcl
vSAN HCL DB Auto Updateautohclupdate
vSAN HCL DB up-to-datehcldbuptodate
After 1 additional host failurelimit1hf
Current cluster situationlimit0hf
Host component limitnodecomponentlimit
Active multicast connectivity checkmulticastdeepdive
All hosts have a vSAN vmknic configuredvsanvmknic
All hosts have matching multicast settingsmulticastsettings
All hosts have matching subnetsmatchingsubnet
Hosts disconnected from VChostdisconnected
Hosts with connectivity issueshostconnectivity
Multicast assessment based on other checksmulticastsuspected
Network latency checkhostlatencycheck
vMotion: Basic (unicast) connectivity checkvmotionpingsmall
vMotion: MTU check (ping with large packet size)vmotionpinglarge
vSAN cluster partitionclusterpartition
vSAN: Basic (unicast) connectivity checksmallping
vSAN: MTU check (ping with large packet size)largeping
Performance service
All hosts contributing statshostsmissing
Performance data collectioncollection
Performance service statusperfsvcstatus
Stats DB objectstatsdb
Stats DB object conflictsrenameddirs
Stats master electionmasterexist
Verbose modeverbosemode
Physical disk
Component limit healthphysdiskcomplimithealth
Component metadata healthcomponentmetadata
Disk capacityphysdiskcapacity
Memory pools (heaps)lsomheap
Memory pools (slabs)lsomslab
Metadata healthphysdiskmetadata
Overall disks healthphysdiskoverall
Physical disk health retrieval issuesphysdiskhostissues
Software state healthphysdisksoftware
Stretched cluster
Invalid preferred fault domain on witness hostwitnesspreferredfaultdomaininvalid
Invalid unicast agenthostwithinvalidunicastagent
No disk claimed on witness hostwitnesswithnodiskmapping
Preferred fault domain unsetwitnesspreferredfaultdomainnotexist
Site latency healthsiteconnectivity
Unexpected number of fault domainsclusterwithouttwodatafaultdomains
Unicast agent configuration inconsistentclusterwithmultipleunicastagents
Unicast agent not configuredhostunicastagentunset
Unsupported host versionhostwithnostretchedclustersupport
Witness host fault domain misconfiguredwitnessfaultdomaininvalid
Witness host not foundclusterwithoutonewitnesshost
Witness host within vCenter clusterwitnessinsidevccluster
vSAN iSCSI target service
Home objectiscsihomeobjectstatustest
Network configurationiscsiservicenetworktest
Service runtime statusiscsiservicerunningtest


Silence all HCL related checks in an unsupported home lab configuration. This typically includes the following Check IDs:

  • controllerdiskmode
  • controllerdriver
  • controllerfirmware
  • controllerreleasesupport
  • controlleronhcl
  1. Connect to the vCSA with SSH
  2. Open RVC
    # rvc administrator@vc.virten.lab
  3. Mark the vSAN Cluster.
    This step is not required but allows you to use commands with ~vsan66 as target

    > mark vsan66 vc.virten.lab/Datacenter/computers/vSAN66/
  4. Silence health checks
    > -a controllerdiskmode ~vsan66
    Successfully add check "Controller disk group mode is VMware certified" to silent health check list for vSAN66
    > -a controllerdriver ~vsan66
    Successfully add check "Controller driver is VMware certified" to silent health check list for vSAN66
    > -a controllerfirmware ~vsan66
    Successfully add check "Controller firmware is VMware certified" to silent health check list for vSAN66
    > -a controllerreleasesupport ~vsan66
    Successfully add check "Controller is VMware certified for ESXi release" to silent health check list for vSAN66
    > -a controlleronhcl ~vsan66
    Successfully add check "SCSI controller is VMware certified" to silent health check list for vSAN66
  5. Verify the status with
    > ~vsan66
    Silent Status of Cluster vSAN66:
    | Health Check                                       | Health Check Id           | Silent Status |
    | Hardware compatibility                             |                           |               |
    |   Controller disk group mode is VMware certified   | controllerdiskmode        | Silent        |
    |   Controller driver is VMware certified            | controllerdriver          | Silent        |
    |   Controller firmware is VMware certified          | controllerfirmware        | Silent        |
    |   Controller is VMware certified for ESXi release  | controllerreleasesupport  | Silent        |
    |   Host issues retrieving hardware info             | hclhostbadstate           | Normal        |
    |   SCSI controller is VMware certified              | controlleronhcl           | Silent        |
    |   vSAN HCL DB Auto Update                          | autohclupdate             | Silent        |
    |   vSAN HCL DB up-to-date                           | hcldbuptodate             | Normal        |


4 thoughts on “How to silence VMware vSAN Health Checks”

  1. In order to see if the changes worked, go to the cluster > Monitor > vSAN > Health > Retest and it should turn the previously failed tests green :-)

  2. I have tried the commands ( but in rvc they are not available.

    root@vcenter [ ~ ]# rvc administrator@n00b.local@localhost
    Install the "ffi" gem for better tab completion.
    0 /
    1 localhost/

    did I miss something?

    1. Your commands were a bit off and either need the vsan cluster path added on to the end or you have to drill down to the vSAN cluster level then run the commands with a "." to tell it to run from where you are.

      More simply put, when you see
      and 1 localhost

      you need to "cd 1" then do "ls" and select the , then ls again and select then ls again and it should list the then cd to that.

      At that point you need to then follow the formating like this, -a diskbalance .

      that would turn off disk balance from the vSAN health check. Also the period you see at the end after the space is supposed to be there. That is telling it the vSAN is where we already are (because we drilled down to the vSAN up above)

Leave a Reply

Your email address will not be published. Required fields are marked *