Lab: Deploy 3-Node vSAN Cluster with ESA
Objectives
- Enable vSAN ESA on three hosts and claim NVMe devices into the storage pool (Obj 2.3)
- Create an ESA storage policy (RAID-5 2+1 or RAID-1) and explain the capacity overhead
- Validate vSAN network MTU with vmkping before enabling vSAN
Prerequisites
Holodeck VVF 9.0 instance deployed and healthy
Lab Environment
Holodeck vSphere Foundation 9.0 instance (New-HoloDeckInstance -VVF; -vSANMode OSA by default, ESA where the physical layer supports it): vCenter managing one vSAN cluster of nested ESX hosts, plus VCF Operations. VVF has no SDDC Manager and no NSX. ESA needs NVMe devices on the physical layer; with OSA nested hosts follow the OSA notes in the steps.
Credentials
| System | Username | Password |
|---|---|---|
| vCenter | administrator@vsphere.local | Holodeck documented default (Post Deployment table) |
| Nested ESX hosts | root | Holodeck documented default (Post Deployment table) |
Tasks
Task 1 Deploy 3-Node vSAN Cluster with ESA
Provision 3x ESX 9.0 hosts with ≥2 NICs (management/vSAN) each
Create vDS with vSAN port group (VLAN 100, MTU 9000)
vCenter UI → Clusters → Create new cluster → Enable vSAN (Intelligent Storage Management)
Add all 3 hosts to cluster
Claim devices (vSAN ESA): Cluster → Configure → vSAN → Disk Management → Claim Unused Disks → select the certified NVMe devices on each host into the single ESA storage pool (ESA has no cache/capacity tiers and no disk groups — VCF 9.0.1 docs p.1652)
Verify quorum: vSAN cluster UI → vSAN health check → Cluster quorum = 3/3 healthy
Create VM storage policy: vCenter UI → Policies and Profiles → VM Storage Policies → Create → vSAN ESA rules: Failures to tolerate = 1 failure (RAID-5 2+1 on three hosts, or RAID-1 mirroring); compression stays on by default (VCF 9.0.1 docs p.1651)
Deploy test VM on vSAN datastore using policy
Monitor: vSAN cluster → Performance → Latency/Throughput graphs
Validation Gate
Check: After enabling vSAN ESA on 3 nodes, verify: vSAN health is green, all disks are claimed, storage policy matches design, and cross-host vmkping with jumbo frames succeeds
Expected: vSAN health dashboard shows all checks green, 3 hosts contributing capacity, default storage policy matches design specification (RAID-1 or RAID-5 as planned)
Common Errors
Final Validation
Gate: every check below passes with the evidence recorded in the lab log.
✓ Skyline Health → All checks green
✓ Devices → All intended devices claimed on 3 hosts
✓ Policy → The design policy is the datastore default and VMs are compliant
Cleanup / Restore
• Keep the cluster for later labs
Design Reflection (VCDX)
vSAN cluster design decisions — RAID level, compression policy, storage-pool device count and host sizing (ESA has no disk groups) — are common VCDX defense questions. Be prepared to justify your RAID choice with capacity waterfall math and performance data.
Requirements
- Deploy 3-node vSAN ESA cluster with all-NVMe
- Configure appropriate RAID policy per workload tier
- Keep ESA compression enabled (default) for space efficiency
Constraints
- ESA requires all-NVMe — no mixed drive types
- ESA: 3 hosts for RAID-1 or RAID-5 (2+1); 4 hosts for RAID-5 when auto-policy management is on
- Consistent MTU on the vSAN network end-to-end (9000 recommended — VCF-NET-RCMD-MTU-003)
Assumptions
- All NVMe drives pass VMware Compatibility Guide check
- Network infrastructure supports jumbo frames
Risks
- vSAN cluster partition from an inconsistent MTU or VLAN on the vSAN network
- Capacity planning error from wrong default storage policy