Triggered when basic (unicast) connectivity check (normal ping) has failed on the vSAN host due to network misconfiguration.

Triggered when a check of free space on physical disks in the vSAN cluster results in an error or warning.

Triggered when CLOMD process on the host has issues and impacting the functionality of vSAN cluster.

Triggered when disk load variance between some vSAN disks exceeded the threshold value.

vSAN cannot perform the load balance properly.

Host ESXi version and the vSAN disk format version is incompatible with the other hosts and disks in a vSAN cluster.

Triggered when the host has invalid unicast agent and impacting the health of vSAN Stretched Cluster.

An invalid unicast agent on the host can cause a communication malfunction with the witness host.

Triggered when the host in a vSAN cluster does not have a VMkernel NIC configured for vSAN traffic.

Even if an ESXi host is part of the vSAN cluster, but is not contributing storage, it must still have a VMkernel NIC configured for vSAN traffic.

Triggered when the host in a vSAN cluster has connectivity issues and vCenter Server does not know its state.

Triggered when the host in a vSAN cluster has IP multicast connectivity issue. It means that multicast is most likely the root cause of a vSAN network partition.

Triggered when the host is either running an outdated version of the vSAN Health Service VIB or It is not installed on the host.

Triggered if network latency check of vSAN hosts is greater than or equal to 1 ms RTT.

Triggered when one or more hosts in the vSAN cluster have misconfigured multicast addresses.

Triggered when one or more physical disks on vSAN host is experiencing software state health issues.

Triggered when one or more vSAN enabled hosts are not in the same IP subnet.

Triggered when overall health of the physical disks in a vSAN Cluster is impacted. See the health status of each physical disk individually on all the hosts.

Triggered when overall health of the VMs on a vSAN datastore is impacted.

Triggered when overall health of vSAN objects is reporting issues.

Triggered when ping test with large packet size between all VMKernel adapter with vMotion traffic enabled is impacted.

Triggered when ping test with small packet size between all VMKernel adapter with vMotion traffic enabled is impacted.

Site latency between two fault domains and the witness host has exceeded the recommended threshold values in a vSAN Stretched cluster.

Triggered when statistics collection of vSAN performance service is not working correctly.

This means that statistics collection or writing statistics data to storage have failed for three consecutive intervals.

Triggered when MTU check (ping with large packet size) has failed on vSAN environment due to some MTU misconfiguration in the vSAN network.

Triggered when the preferred fault domain is not set for the witness host in a vSAN Stretched cluster and affecting the operations of vSAN Stretched cluster.

Triggered when unicast agent is not configured on the host and affecting operations of vSAN Stretched cluster.

Triggered when the host that is part of a vSAN cluster is in disconnected state or not responding and vCenter Server does not know its state.

Triggered when vSAN Cluster contains host whose ESXi version does not support vSAN Stretched Cluster.

Triggered when vSAN cluster has issues in electing stats controller of vSAN Performance service.

Triggered when vSAN cluster has multiple network partitions due to a network issue.

Triggered when vSAN cluster has issues in electing stats controller of vSAN Performance service.

This affects the functionality of vSAN Performance service.

Triggered when vSAN disk group has incorrect deduplication and compression configuration.

Triggered when vSAN has encountered an issue while reading the metadata of a physical disk and cannot use this disk.

Triggered when vSAN health service is not installed on the host.

Triggered when vSAN host and its disks have inconsistent deduplication and compression configuration with the cluster.

Triggered when vSAN is unable to retrieve the physical disk information from host. vSAN Health Service may not be working properly on this host.

Triggered when vSAN Performance Service is not enabled.

Triggered when vSAN Performance Service is unable to communicate and retrieve statistics from host.

Triggered when vSAN Stretched cluster contains a witness host without a valid disk group.

If the witness host does not have any disk claimed by vSAN then its fault domain is not available.

Triggered when vSAN Stretched cluster does not contain a valid witness host.

This affects the operations of vSAN Stretched cluster.

Triggered when vSAN Stretched cluster does not contain two valid fault domains.

Triggered when vSAN Stretched cluster contains multiple unicast agents.

This means multiple unicast agents were set on non-witness hosts.

Triggered when vSAN witness host has an invalid preferred fault domain.

Triggered when witness host is a part of the vCenter cluster, which forms vSAN Stretched cluster.

Triggered when witness host resides in one of the data fault domains.

This affects the operations of vSAN Stretched cluster.

Triggered when the flash read cache reservation in a vSAN cluster is less than 20%.

Cleared by adding more flash storage to the read-cache.

Triggered when after one additional host failure, vSAN Cluster will not have enough resources to rebuild all objects.

Triggered when a capacity disk used for vSAN is smaller than 255 GB (default max component size), so virtual machines that run on the vSAN Datastore might experience disk space issues.

Triggered when a capacity disk used for vSAN is smaller than 255 GB (default max component size), so virtual machines that run on the vSAN Datastore might experience disk space issues.

Triggered when a controller with pass-through and RAID disks has issues.

Triggered when the disk format version of one or more vSAN disks is out of date and is not compatible with other vSAN disks. This can lead to problems in creating or powering on VMs, performance degradation, and EMM failures.

Triggered when the ESXi host issues retrieving hardware info.

Triggered when a firmware provider has not met all its dependencies or is not functioning as expected.

Triggered when a host with inconsistent extended configurations is detected.

vSAN cluster extended configurations are set as object repair timer is 60 minutes, site read locality is Enabled, customized swap object is Enabled, large scale cluster support is Disabled; For host with inconsistent extended configurations, vSAN cluster remediation is recommended, for host doesn't support any extended configuration, ESXi software upgrade is needed; And to make cluster scalability configuration take effect, host reboot could be required.

Triggered when there is inconsistent configuration (like dedup/compression, encryption) setup on hosts or disks with the cluster.

Triggered when the network adapter driver is not VMware certified.

Triggered when the network adapter firmware is not VMware certified.

Triggered when the network adapter is not VMware certified.

Triggered when the network configuration of the vSAN iSCSI target service is not valid.

This health check validates the presence of the default vmknic for the vSAN iSCSI target service, and verifies that all the existing targets have valid vmknic configurations.

Triggered when non-vSAN disks are used for VMFS or Raw Device Mappings (RDMs).

Triggered when the number of vSAN components on a disk is reaching or has reached its limit. This will cause failure in the deployment of new Virtual Machines and also impact rebuild operations.

Triggered when the number of vSAN components on a host is reaching or has reached its limit.

This will cause failure in the deployment of new Virtual Machines and also impact rebuild operations.

Triggered when one or more hosts in the cluster do not support CPU AES-NI or have it disabled. As a result, the system might use the software encryption that is significantly slower than AES-NI.

Triggered when the RAID controller configuration has issues.

Triggered when the stability and integrity of vSAN may be at risk as the storage I/O controller driver is not VMware certified.

Triggered when the stability and integrity of vSAN may be at risk as the storage I/O controller driver is not supported with the current version of ESXi running on the host.

Triggered when the storage I/O Controller firmware not is VMware certified.

Triggered when the vSAN environment may be at risk as the Storage I/O controller on the ESXi hosts that are participating in a vSAN cluster are not compatible with the VMware Compatibility Guide.

Triggered when the current status of the Customer Experience Improvement Program (CEIP) not is enabled.

Triggered when internet connectivity is not available for vCenter Server.

Triggered when resync operations are throttled. Please clear the limit, unless you need it for particular cases like a potential cluster meltdown.

Triggered when the time of hosts and VC are not synchronized within 1 minute.

Any difference larger than 60 seconds will lead this check to fail. If the check fails, it is recommended that you check the NTP server configuration.

Triggered when the vCenter Server or any of the hosts experience problems when connecting to KMS.

Triggered when the vCenter server state was not pushed to ESXi due to vCenter server being out of sync.

During normal operation, the vCenter server state is regarded as source of truth, and ESXi hosts are automatically updated with the latest host membership list. When vCenter server is replaced or recovered from backup, the host membership list in vCenter server may be out of sync. This health check detects such cases, and alerts if vCenter server state was not pushed to ESXi due to vCenter server being out of sync. In such cases, first fully restore the membership list in vCenter server, and then perform 'Update ESXi configuration' action if required.

Triggered when the vSAN and VMFS datastores are on a same Dell H730 controller with the lsi_mr3driver.

Triggered when the vSAN build is not compatible with available releases and VCG compatibility guide.

This is the ESXi build that vSAN recommends as the most appropriate, given the hardware, its compatibility per the VMware Compatibility Guide and the available releases from VMware.

Triggered when the vSAN build recommendation engine has issues.

The vSAN Build Recommendation Engine relies on the VMware compatibility guide and VMware release metadata for its recommendation. To provide build recommendations, it also requires VMware Update Manager service availability, internet connectivity, and valid credentials for my.vmware.com. This health check ensures that all dependencies are met and that the recommendation engine is functioning correctly.

Triggered when the disk usage in a vSAN cluster reaches 90% of capacity.

Cleared by removing virtual machines that are no longer in use or adding more disks to the cluster.

Triggered when the disk usage in a vSAN cluster reaches 70% of capacity.

Cleared by removing virtual machines that are no longer in use or adding more disks to the cluster.

Triggered when the vSAN cluster is reaching or has reached its limit for components, free disk space and read cache reservations.

Triggered when the number of virtual disks per host in the vSAN cluster reaches 95% of capacity.

Cleared by adding most hosts to the cluster.

Triggered when the number of virtual disks per host in the vSAN cluster reaches 75% of capacity.

Cleared by adding most hosts to the cluster.

Triggered when the vSAN configuration for LSI 3108-based controller has issues.

Triggered when the vSAN disk group type (All-Flash or Hybrid) for the used SCSI controller is not VMware certified.

Triggered when some advanced configuration settings have different values on different hosts in the vSAN cluster.

Triggered when the vSAN has encountered an integrity issue with the metadata of an individual component on a physical disk.

Triggered when the vSAN HCL DB auto updater is not working properly. This means that vSAN cannot download and update its HCL DB automatically.

Triggered when the vSAN HCL DB is not up-to-date.

Triggered when the vSAN Health Service is not able to find the appropriate controller utility for the storage controller on the ESXi host.

Triggered when the vSAN is running low on the vital memory pool (heaps) needed for the operation of physical disks.

This can lead to a variety of performance issues such as virtual machine storage performance degradation, operation failures, or even ESXi hosts going unresponsive.

Triggered when the vSAN is running low on the vital memory pool (slabs) needed for the operation of physical disks.

This can lead to a variety of performance issues such as virtual machine storage performance degradation, operation failures, or even ESXi hosts going unresponsive.

Triggered when the vSAN is using a physical disk which has high congestion value.

This can lead to a variety of performance issues such as virtual machine storage performance degradation, operation failures, or even ESXi hosts going unresponsive.

Triggered when the vSAN iSCSI target service home object has issues.

This health check verifies the integrity of the vSAN iSCSI target service home object. It also verifies that the configuration of the home object is valid.

Triggered when the vSAN iSCSI target service is not running properly or is not correctly enabled on the host.

This health check verifies the service runtime status of the vSAN iSCSI target service, and checks whether the service is correctly enabled on each host.

Triggered when the vSAN performance service statistics database object is reporting issues.

Triggered when the vSphere cluster members do not match vSAN cluster members.

Triggered when the Read Cache (RC) in the vSAN cluster reaches 80% of capacity.

Cleared by adding flash storage to the read cache.

Triggered when the Read Cache (RC) in the vSAN cluster reaches 95% of capacity.

Cleared by adding flash storage to the read cache.

Triggered when the vSAN adapter instance failed to collect data from vSAN Health Service. The health Service might have issues.

Triggered when the vSAN disk group read cache hit rate is less than 90%.

Cleared by adding more cache to accommodate the workload.

Triggered when the vSAN disk group read cache hit rate is less than 90% and the vSAN disk group write buffer free space is less than 10%.

Cleared by adding more flash capacity to the vSAN disk group.

Triggered when the vSAN host has encryption disabled, while the vSAN cluster has encryption enabled.

Cleared by enabling encryption on vSAN host.

Triggered when the vSAN host has encryption enabled, while the vSAN cluster has encryption disabled.

Cleared by enabling encryption on vSAN cluster.

Triggered when the vSAN capacity disk has encryption disabled, while the vSAN cluster has encryption enabled.

Cleared by enabling encryption on vSAN capacity disk.

Triggered when the vSAN capacity disk has encryption enabled, while the vSAN cluster has encryption disabled.

Cleared by enabling encryption on vSAN cluster.

Triggered when the vSAN cache disk has encryption disabled, while the vSAN cluster has encryption enabled.

Cleared by enabling encryption on vSAN cache disk.

Triggered when the vSAN cache disk has encryption enabled, while the vSAN cluster has encryption disabled.

Cleared by enabling encryption on vSAN cluster.

Triggered when there is an issue with file service infrastructure health state of an ESXi host in the vSAN cluster.

Triggered when the vSAN File Server health is not in a good state.