Users may encounter a warning banner in the vSphere Client stating: Insufficient configured resources to satisfy the desired vSphere HA failover level on the cluster <cluster-name> in <datacenter-name>
In some instances, it may appear that resource usage is not being reflected properly, or that the cluster has sufficient resources despite the alert. This issue is often reported after attempting to reconfigure HA or disabling/enabling HA without a change in the status.
This alert can trigger when the Desired failover capacity (Define host failover capacity by > Cluster resource Percentage in Admission Control) exceeds the Current available failover capacity.
In the logs (vpxd.log), the failure can be identified by comparing the requested reservations against available resources:
Desired: CPU-reservation: 293960, Mem-reservation: 3906338 vs. Current: CPU-reservation: 294372, Mem-reservation: 3890128The primary cause is typically a misalignment between the Percentage of Cluster Resources Reserved and the actual number of host failures the cluster is intended to tolerate (N+X redundancy). For example, in a 10-host cluster:
To resolve this alert, align the Admission Control percentage with your specific host failure requirements and current cluster size.
Number of Host Failures to Tolerate / Total Number of Hosts) * 100.
(4 / 10) * 100 = 40%.Note: Before adjusting these values, consult with your Architecture team to ensure the new redundancy level (e.g., switching from 50% to 40%) aligns with your internal Service Level Agreements (SLAs).