HA Admission Control Validation
Objectives
- Understand HA admission control policies (slot-based and percentage-based)
- Calculate slot sizes for different VM profiles in a 4-host cluster
- Evaluate admission control scenarios and policy recommendations
- Design N+1 HA policy for VCF management domain
Prerequisites
VCF 9.0 lab environment deployed with 4-host management cluster
Prior labs: vcp-architect-01: Cluster Basics
Required skills:
- Understanding vSphere HA concepts
- Basic cluster architecture knowledge
Lab Environment
4-host VCF management cluster (each host: 96GB RAM, 16 vCPU cores, 2.5GHz)
Cluster specification
| Item | Value |
|---|---|
| hosts | 4 |
| host ram gb | 96 |
| host cores | 16 |
| host frequency ghz | 2.5 |
Tasks
Task 1 Understand HA Admission Control Policies
Establish foundational knowledge of slot-based and percentage-based admission control mechanisms and their impact on cluster capacity planning.
Review the 4-host VCF management cluster. From each host's Summary tab record the CPU and memory available to VMs (the host's root resource pool, which already excludes the resources used for virtualization): in this lab assume 36,000 MHz and 88 GB per host, so 144,000 MHz and 352 GB for the cluster. vSphere HA uses these root-resource-pool figures, not the physical totals, and considers only connected hosts that are not in maintenance mode and have no HA errors.
Define three VM profiles with reservations, because the slot policy works on reservations, not on configured vCPU or vRAM: Small 2 vCPU/4 GB with a 500 MHz and 4 GB reservation; Medium 4 vCPU/16 GB with 2,000 MHz and 16 GB; Large 8 vCPU/64 GB with 4,000 MHz and 32 GB (memory overhead for the Large VM about 0.4 GB). Slot size (vSphere 9.0 Availability, Slot Policy Admission Control): CPU component = the largest CPU reservation of any powered-on VM (32 MHz if none is set; das.vmcpuminmhz changes the default); memory component = the largest memory reservation plus memory overhead of any powered-on VM (no default). Compute the slot size for a cluster where at least one VM of each profile is powered on.
Determine the slots per host: divide the host's available CPU by the CPU slot component and round down; do the same for memory; the smaller result is the host's slot count. Here: floor(36,000 / 4,000) = 9 and floor(88 / 32.4) = 2, so 2 slots per host and 8 slots in the 4-host cluster. Record how many VMs are powered on (for this lab: 6).
Compute the Current Failover Capacity for Host Failures Cluster Tolerates = 1: remove hosts starting from the largest and check whether the remaining slots still satisfy every powered-on VM. With 6 powered-on VMs and 8 slots: one host fails, 6 slots remain, 6 VMs fit, so capacity = 1; two hosts fail, 4 slots remain, insufficient. Admission control therefore allows 8 - 2 - 6 = 0 further power-ons; a seventh VM is refused.
Validation Gate
Check: Verify admission control calculations and N+1 capacity planning
Expected: Slot size in MHz and MB from the profile reservations, slots per host and per cluster, Current Failover Capacity for Host Failures Cluster Tolerates = 1, and the available-slot count for new power-ons
Common Errors
Task 2 Evaluate Admission Control Scenarios
Apply admission control calculations to real-world scenarios and compare policy approaches (slot-based vs. percentage-based) for cluster design decisions.
Scenario 1: a new VM with a 96 GB memory reservation (plus about 0.6 GB overhead) is requested for the management cluster. Recompute the slot policy from Task 1: the memory slot component becomes 96.6 GB, so each host supports floor(88 / 96.6) = 0 slots and the cluster has 0 slots; admission control refuses the power-on (and would also flag the existing VMs as unprotected). Determine the alternatives: lower the reservation, cap the slot with das.slotmeminmb (the 96 GB VM then needs several slots), or switch to the Cluster resource Percentage policy.
Calculate the impact of losing one host. From Task 1: 4 hosts, 2 slots each, 8 slots, 6 VMs powered on, Current Failover Capacity 1. After one host fails: 3 hosts, 6 slots; all 6 admitted VMs restart (each takes one slot). Now test the oversubscribed case: if admission control had been disabled and 7 VMs were powered on, 6 slots remain for 7 VMs and one VM cannot be restarted with its reservation honoured.
Compare slot-based vs. percentage-based admission control for this cluster. Slot policy: one cluster-wide slot (here 4,000 MHz / 32.4 GB set by the Large reservation), 2 slots per host, 8 slots, 6 VMs admitted; hard limit, predictable, but wasteful when reservations differ widely. Percentage-based: Reserves a percentage (e.g., 25%) of cluster resources for failover; allows heterogeneous workloads without recalculation. For this cluster: the slot policy holds back the largest host's 2 slots (25% of the slots) and strands most of the 352 GB; Cluster resource Percentage with 25% CPU and 25% memory reserved admits VMs until their reservations reach 75% of the cluster's resources, so mixed reservations (vCenter, NSX, SDDC Manager, VCF Operations) fit without a common slot. Recommendation: Compare predictability vs. flexibility trade-off.
Comparison table:
- Slot-based: Predictable, hard limits, requires slot recalculation for new VM types, prevents oversubscription
- Percentage-based: Flexible, accommodates heterogeneous workloads, simpler to understand, less granular control
For this VCF management cluster the appliances carry different reservations (vCenter, NSX Manager nodes, SDDC Manager, VCF Operations), so the slot policy is distorted by the largest one; Cluster resource Percentage (25%) is the practical choice, or a slot policy with a das.slotmeminmb cap.
Formulate a policy recommendation for this VCF management cluster. Decision: Which admission control method and why? Justification: 'Recommend Cluster resource Percentage admission control (25% CPU, 25% memory, equal to one of four hosts) for this cluster because: (1) the management appliances carry different reservations, so a single slot set by the largest one strands capacity; (2) the percentage reserve still guarantees one host failure; (3) new appliance sizes need no slot recalculation; (4) if deterministic slot accounting is required, use the slot policy with das.slotmeminmb capped at the typical appliance reservation and accept multi-slot VMs.' Document the policy choice with rationale.
Validation Gate
Check: Verify scenario calculations and policy recommendation
Expected: Documented capacity impact analysis, policy comparison, and justified recommendation
Common Errors
Task 3 Design HA Policy for VCF Management Domain
Create a comprehensive HA design document for the VCF management domain that demonstrates N+1 availability architecture and applies admission control concepts to production VCF components.
Identify the management VMs and their resource requirements in the VCF management domain. The inventory below is illustrative and partial (it omits NSX Edge nodes, VCF Automation and Operations for Logs) — take the real figures from the VCF 9.0 Planning and Preparation Workbook and each product's deployment sizing. List: vCenter (Medium: 8 vCPU, 30 GB — vSphere 9.0 docs: Hardware Requirements for the vCenter Appliance), NSX Manager cluster nodes (Medium form factor: 6 vCPU, 24 GB each, 3 nodes = 18 vCPU/72 GB — VCF 9.0.1 docs p.2757), SDDC Manager (4 vCPU, 16 GB — the VCF Installer appliance specification; deployed in the management domain it switches to SDDC Manager mode, VCF 9.0.1 docs p.1273, p.1265), VCF Operations analytics cluster in the High Availability model (3 nodes, p.859; Medium nodes 8 vCPU, 32 GB each = 24 vCPU/96 GB — KB 397782 VCF Operations 9.0 Sizing Guidelines), VCF Operations fleet management appliance (4 vCPU, 12 GB — p.1353) and one collector (Classic Small cloud proxy: 2 vCPU, 8 GB — p.2965 Table 934). Total: 8+18+4+24+4+2 = 60 vCPU and 30+72+16+96+12+8 = 234 GB RAM across the listed management VMs.
Documented inventory of management domain VMs with resource specifications (figures from the cited sizing sources; confirm against the Planning and Preparation Workbook for your release). Example table:
| VM | vCPU | RAM GB | Notes |
|---|---|---|---|
| vCenter (Medium) | 8 | 30 | HA restart; vCenter HA not supported in VCF |
| NSX Manager-1 (Medium) | 6 | 24 | Part of 3-node cluster |
| NSX Manager-2 (Medium) | 6 | 24 | Part of 3-node cluster |
| NSX Manager-3 (Medium) | 6 | 24 | Part of 3-node cluster |
| SDDC Manager | 4 | 16 | Single appliance, HA restart |
| VCF Operations analytics node ×3 | 8 each | 32 each | High Availability model (p.859) |
| VCF Operations fleet management | 4 | 12 | Single appliance (p.1353) |
| VCF Operations collector (Classic Small) | 2 | 8 | Cloud proxy (Table 934) |
| Total | 60 | 234 |
Calculate the minimum cluster size to maintain N+1 availability for the listed management VMs, using the usable capacity from Task 1 (88 GB and 16 cores per host after the hypervisor's own use). Memory: 234 GB / 88 GB = 2.66 host equivalents; add the N+1 reserve: 2.66 + 1 = 3.66, round up to 4 hosts. vCPU at the 1:1 assumption: 60 vCPU / 16 cores = 3.75 host equivalents; 3.75 + 1 = 4.75, round up to 5 hosts. The limiting resource is vCPU, so the minimum cluster size is 5 hosts.
Document the HA design decision (DD format). Create a formal design decision document with sections: (1) Requirement: 'Maintain N+1 availability for VCF management domain to support 99.95% uptime SLA (max 22 minutes downtime/month)'; (2) Constraints: 'Cluster must survive single host failure without VM restart cascades'; (3) Assumptions: 'VMs are distributed across all 5 hosts (DRS anti-affinity for the NSX Manager and VCF Operations nodes)'; (4) Design Decision: 'Deploy a 5-host management cluster with HA admission control for one host failure using percentage-based failover capacity (VCF-CLS-RCMD-CFG-001, VCF 9.0.1 docs p.550); vSphere calculates the reserve from the host failures to tolerate (20% in 5 hosts). Slot policy is rejected because the management VMs carry differing reservations (a 32 GB VCF Operations node sets an oversized slot). Admit only management VMs to this cluster (no user workloads)'; (5) Justification: 'Sizing calculation: 234 GB management workload must fit on the 4 surviving hosts: 4 × 88 GB = 352 GB usable, leaving 118 GB for growth; 60 vCPU on 4 × 16 = 64 cores at 1:1. N+1 compliant on both resources.'
Formal HA Design Decision document:
VCF Management Domain HA Design (v9.0)
Requirement: N+1 availability for VCF management domain
Current State: 4-host cluster (insufficient for management workload)
Proposed Design: 5-host cluster, HA admission control for 1 host failure, percentage-based (VCF-CLS-RCMD-CFG-001)
Rationale: Management workload totals 234 GB RAM / 60 vCPU; after one host failure the 4 surviving hosts offer 352 GB usable and 64 cores, so the workload fits with 118 GB headroom. Provides N+1 failover coverage on both memory and CPU.
Impact: Requires upgrade from 4-host to 5-host cluster.
Test the design with a what-if scenario: what if 2 hosts fail simultaneously (N+2)? The design assumes N+1. With 2 host failures: 5 − 2 = 3 hosts remain. Memory: 3 × 88 GB = 264 GB usable against 234 GB of management VMs — fits. vCPU at the 1:1 assumption: 3 × 16 = 48 cores against 60 vCPU — does NOT fit. Conclusion: the design is N+1 only; it does not survive two host failures without CPU overcommit on the management stack. Document: 'Current HA design supports N+1 (single host failure). N+2 is not a requirement per the business SLA; if an N+2 requirement emerges the cluster grows to 6 hosts (4 survivors × 16 = 64 cores ≥ 60 vCPU, 352 GB ≥ 234 GB).'
Validation Gate
Check: Verify HA design document and what-if scenario analysis
Expected: Formal design decision document with justification and what-if scenario analysis
Common Errors
Final Validation
HA admission control lab completed with slot-based vs percentage-based analysis, scenario evaluation, and VCF management cluster design
✓ Admission control calculations (Task 1, Steps 1-4) → Documented slot sizes for all VM profiles, N+1 capacity calculations
✓ Scenario evaluation and policy recommendation (Task 2, Steps 1-4) → 96GB VM admissibility determination, failover impact analysis, slot vs. percentage comparison, and justified policy choice
✓ VCF management design decision (Task 3, Steps 1-4) → Management VM inventory, minimum cluster sizing, formal DD document, N+2 what-if scenario
Cleanup / Restore
• Revert to initial snapshot if any lab VMs were created
• Document all design decisions and calculations for VCDX study
Design Reflection (VCDX)
During a VCDX defense, panelists will probe your HA design with questions like: 'You sized the cluster for 5 hosts. What happens if a host fails during a maintenance window when a 3rd host is offline?' Or: 'How would you handle a scenario where NSX Managers are concentrated on 2 hosts and one host fails?' Be prepared to explain admission control trade-offs, justify why you chose percentage-based over slot-based (VCF-CLS-RCMD-CFG-001), and articulate what would change if requirements shifted to N+2 or if workload profiles expanded. Panelists expect designers to show flexibility—how would you adjust the design if vCF Ops expanded from 64GB to 128GB?
Requirements
- VCF management domain must maintain N+1 availability for 99.95% uptime SLA
- Cluster must support heterogeneous management VMs (vCenter, NSX Managers, SDDC Manager, VCF Ops)
- Admission control must prevent oversized VM admissions that would violate HA during failover
- Design must be documented in formal DD format with sizing calculations and assumptions
- Must address minimum cluster size, slot calculation methodology, and what-if failure scenarios
Constraints
- Each host in the management cluster has fixed capacity (96GB RAM, 16 vCPU cores)
- NSX Manager requires 3-node cluster for quorum and HA
- VCF management domain must not share hosts with user workloads (isolation requirement)
- Admission control policy chosen must apply consistently across all admitted VMs
- One full host capacity must always be reserved for failover (N+1 requirement)
Assumptions
- All management VMs will be distributed across available hosts (no single-host concentration)
- Hypervisor reserves ~8GB per host, leaving 88GB available for VMs
- vCPU allocation is 1:1 (no oversubscription) for deterministic performance
- Management VM resource requirements are stable (no dynamic scaling)
- Slot size is calculated once and remains stable (no mid-cluster addition of different-sized VMs)
- Network and storage are not the limiting factors (CPU and memory are the constraints)
- Single host failure is the design-basis failure scenario; N+2 is not required
Risks
- Risk: Cluster growth adds larger VMs without recalculating slot size. Mitigation: Document when slot size becomes invalid and requires cluster redesign.
- Risk: VCF Ops or another management VM is unexpectedly resized upward. Mitigation: Establish change control requiring HA impact analysis before VM resize in management domain.
- Risk: Operational team over-admits VMs by disabling HA or ignoring admission control. Mitigation: Use vSphere admission control policies that are enforced and non-bypassable without explicit approval.
- Risk: Network or storage becomes the limiting factor instead of CPU/memory. Mitigation: Extend this analysis to validate network (NSX bandwidth) and storage (IOPS, capacity) separately.
- Risk: A third host fails within 15 minutes of the first host failure (before first host VMs have fully restarted). Mitigation: Monitor first host failure recovery time; if recovery takes >15 min and concurrent failures are possible, increase cluster size or add recovery time SLA.
Self-Assessment Discussion Prompts
- You proposed a 5-host management cluster to maintain N+1 availability. A business stakeholder asks: 'Why do we need 5 hosts? We currently run on 4, and nothing has failed in 2 years.' How would you justify the upgrade? What specific risks does the 4-host cluster face during a single host failure?
- Compare slot-based vs. percentage-based admission control. In a cluster with heterogeneous VM sizes (2GB to 64GB), which method provides better capacity utilization and why? What are the trade-offs?
- VCF Ops is a 64GB VM (the largest in your cluster). A second ops tool is proposed that also requires 64GB. How would your HA design need to change? What's the new minimum cluster size?
- Your cluster is sized for N+1 but a compliance requirement emerges: 'Infrastructure must survive simultaneous failure of any 2 hosts.' How do you redesign the cluster? What's the new minimum size and cost implications?
- During a post-mortem after a host failure, you discover that all NSX Manager VMs restarted on a single surviving host, overloading it momentarily. Which DRS VM-VM anti-affinity rule (VCF-NSX-LM-RCMD-CFG-002) would have kept the managers apart, and why can no HA admission control policy do that job? Should you separate management VMs across multiple failure zones?
- You're asked to design HA for a smaller regional VCF instance with only vCenter and SDDC Manager (no NSX, no Ops). How does this change your admission control calculations? Could a 3-host cluster suffice?
Extensions
Extend to Multi-Region HA Design
Design HA for a VCF environment spanning 2 geographic regions with asynchronous replication. How would you adapt admission control policies? What is minimum cluster size per region?
Integrate Storage Admission Control
Extend the CPU/memory analysis to include storage constraints. If each management VM requires 500GB storage and the cluster has 10TB total, does storage change the minimum cluster size calculation?
Dynamic Workload Scenario
Model a scenario where VCF Ops is expanded from 64GB to 128GB. Recalculate cluster sizing. At what point does slot size change? What remediation steps would you take during the upgrade?
⚠ Known Pitfalls
References
- vSphere 9.0 Availability — vSphere HA Admission ControlTier 1 — Official
Core reference for vSphere HA concepts, admission control, and slot calculation - VMware Cloud Foundation 9.0 documentation (design guidance and sizing)Tier 1 — Official
Defines minimum management VM profiles and cluster sizing guidelines - vCenter 9.0 appliance sizing (vSphere 9.0 installation and setup)Tier 1 — Official
Reference for vCenter sizing and NSX Manager cluster requirements