Operational Defect Database
BugZero updated this defect 44 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 2108740
vSAN Health Service - Limits Health – Current Cluster Situation
Last update date:
4/5/2024
Affected products:
vSAN
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
ESXi Versions 6.x
Purpose
This article explains the Limits Health – Current Cluster Situation check in the vSAN Health Service and provides details on why it might report an error.
Resolution
Q: What does the Limits Health – Current Cluster Situation check do? This particular health check looks at free disk capacity and ensures that the components per host limit has not been exceeded, and that there is some flash read cache capacity remaining (Note: Flash read cache is only relevant to hybrid configurations and is not relevant on all-flash configurations). Note: VMware recommends that the disk capacity maintains a slack space of 30% to avoid excessive re-balance operations. Also note that this way of looking at the resources has some limitations. For example, if there are 3 ESXi hosts in a vSAN cluster, and 2 ESXi hosts are filled to capacity while one is empty, the cluster summaries may look like there are plenty of free resources across all 3 ESXi hosts. However, virtual machine provisioning may fail, as vSAN will require capacity on at least 2 ESXi hosts for the 2 replicas that it needs to create. Q: What does it mean when it is in an error state? If this check has a warning or error, it may means that the number of components has reached its ESXi host limit, or that there is no free storage capacity, or that the flash read cache reservations have been exhausted. If components limits have been reached, or there is no free capacity, the deployment of new virtual machines fails, nor a rebuild operations can be allowed. If the flash read cache is exhausted, it means that there is very little read cache available for those virtual machines that do not have reservations. This will impact the performance of these virtual machines.The following thresholds apply to this Current Cluster Situation health check.Component utilization :- • Red: utilization > 90% for any host in this cluster;• Yellow: utilization <= 90% while utilization > 80% for any host in this cluster;• Green: utilization <= 80% for any host in this cluster; Disk space utilization :- • Red: utilization > 90% for any disks of any host in this cluster;• Yellow: utilization <= 90% while utilization > 80% for any disks of any hosts in this cluster;• Green: utilization <= 80% for any all the disks in this cluster; Read cache reservations :- • Red: utilization > 90% for any host in this cluster;• Yellow: utilization <= 90% while utilization > 70% for any host in this cluster;• Green: utilization <= 70% for any host in this cluster; This table displays the thresholds at which warnings and errors are displayed in this health check: Resourcevsan.check_limits and vsan.disks_stats. For more information, see the Troubleshooting vSAN Storage section in the VMware vSAN Diagnostics and Troubleshooting Reference Manual . For component limits per host and cluster, refer below article :- vSAN Health Service - Limits - Host component : https://kb.vmware.com/s/article/2146130vSAN Component Limit per Cluster : https://kb.vmware.com/s/article/74695
Related Information
For more information on collecting VMware vSAN logs, see Collecting vSAN support logs and uploading to VMware (2072796).Also, see: VMware vSAN Diagnostics and Troubleshooting Reference ManualVMware Ruby vSphere Console Command Reference for vSANVMware vSAN Design and Sizing Guide vSAN Health Service - Cluster Health - vSAN Health Service up-do-datevSAN Health Service - Cluster Health - Advanced vSAN configuration in syncvSAN Health Service - Network Health - Hosts disconnected from vCenter ServervSAN Health Service - Network Health - Unexpected vSAN cluster membersvSAN Health Service - Network Health - vSAN Cluster PartitionvSAN Health Service - Network Health – Hosts with vSAN disabledvSAN Health Service - Network Health - All hosts have a vSAN vmknic configuredvSAN Health Service - Network Health - All hosts have matching subnets vSAN Health Service - Network Health - All hosts have matching multicast settingsvSAN Health Service - Network Health - Hosts small ping test (connectivity check) and Hosts large ping test (MTU check)vSAN Health Service - Network Health - Hosts with connectivity issuesvSAN Health Service - Network Health – Multicast assessment based on other checksvSAN Health Service - Data Health – vSAN Object HealthvSAN Health Service - Physical Disk Health - Metadata HealthvSAN Health Service - Physical Disk Health - Overall Disk HealthvSAN Health Service - Limits Health – After one additional host failurevSAN Health Service - Physical Disk Health - Disk CapacityvSAN Health Service – Physical Disk Health – Software State HealthvSAN Health Service – Physical Disk Health – Component Metadata HealthvSAN Health Service - Physical Disk Health – CongestionvSAN Health Service - Physical Disk Health – Memory poolsvSAN Health Service - vSAN HCL Health - Controller Release SupportvSAN Health Service – vSAN HCL Health – Controller DrivervSAN Health Service - vSAN HCL Health – vSAN HCL DB up-to-datevSAN Health Service - vSAN HCL Health – SCSI Controller on vSAN HCLvSAN Health Service - Cluster Health – CLOMD liveness checkvSAN Health Service - Cluster Health - vSAN Health service installationvSAN Health Check InformationvSAN Health Service - Network Health - Active Multicast connectivity checkvSAN 运行状况服务 - 限制运行状况 – 当前群集情况vSAN 健全性サービス - 制限値の健全性 – 現在のクラスタの状態
