Academy/vSphere Foundation 9.0 Administrator (2V0-16.25)/Lab: Deploy 3-Node vSAN Cluster with ESA
This lab targets VCF 9.0

Lab: Deploy 3-Node vSAN Cluster with ESA

VCF 9.0Intermediatevcp-foundation⏱ 135 min

VVF 9.0 administrator lab (2V0-16.25). Built for a Holodeck VVF instance.

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

SystemUsernamePassword
vCenteradministrator@vsphere.localHolodeck documented default (Post Deployment table)
Nested ESX hostsrootHolodeck documented default (Post Deployment table)

Tasks

Task 1 Deploy 3-Node vSAN Cluster with ESA

vSAN cluster deployment with ESA requires understanding the single-tier NVMe architecture, host compatibility, and the critical importance of network validation before enabling vSAN. A single misconfigured host can prevent cluster formation.
Step 1

Provision 3x ESX 9.0 hosts with ≥2 NICs (management/vSAN) each

Step 2

Create vDS with vSAN port group (VLAN 100, MTU 9000)

Step 3

vCenter UI → Clusters → Create new cluster → Enable vSAN (Intelligent Storage Management)

Step 4

Add all 3 hosts to cluster

Step 5

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)

Step 6

Verify quorum: vSAN cluster UI → vSAN health check → Cluster quorum = 3/3 healthy

Step 7

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)

Step 8

Deploy test VM on vSAN datastore using policy

Step 9

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

Enabling vSAN before verifying network connectivity between all hosts
Fix: vSAN needs a vSAN-enabled VMkernel adapter on every host, with one consistent MTU end-to-end (9000 recommended). Before enabling vSAN, run: vmkping -d -s 8972 <peer_vSAN_IP> from each host to every other host. If any ping fails, do not enable vSAN — hosts that cannot reach each other on the vSAN network form a partitioned cluster (objects inaccessible on the minority side); vSAN requires one consistent MTU across all vSAN traffic, and 9000 is the VCF recommendation (VCF-NET-RCMD-MTU-003, p.586), not a hard requirement.
Mixing NVMe and SAS/SATA drives in an ESA cluster
Fix: vSAN ESA requires ALL-NVMe drives. Mixing NVMe with SAS/SATA forces the cluster into OSA mode (or fails entirely). Verify all drives are NVMe via: esxcli storage core device list | grep -i nvme. If any non-NVMe drives are present, remove them from vSAN claim before enabling ESA.
Not setting the correct storage policy after cluster creation
Fix: On ESA the default storage policy depends on cluster size (auto-policy management generates it from the topology), so it is not a fixed RAID-1 rule. If the design calls for a different layout, create a custom policy and set it as the datastore default. RAID-5 on ESA is 2+1 below six hosts (1.5×) and 4+1 from six hosts (1.25×), against 2× for RAID-1; 1.33× is the OSA 3+1 figure (VCF 9.0.1 docs p.1713).
Expecting deduplication on vSAN ESA in 9.0
Fix: The 9.0 documentation states that deduplication is not available on a vSAN ESA cluster (VCF 9.0.1 docs p.1651, p.1775); ESA compression is on by default through the storage policy. Cluster-wide, post-process global deduplication for ESA arrives in VCF 9.1. The 'full data rewrite on enablement' applies to OSA deduplication and compression, which reformats each disk group.

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

⚠ Known Pitfalls

Enabling vSAN without verifying MTU consistency (vmkping -d -s 8972 when using jumbo frames) — a mixed MTU partitions the cluster; a consistent 1500 works but forgoes the jumbo-frame efficiency VCF recommends.
Planning capacity on ESA deduplication in 9.0 — it is not available on ESA (p.1651); size on compression only. On OSA, enabling deduplication and compression later reformats every disk group.

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.