Lab: vSAN Witness Configuration (2-Node)
Objectives
- Deploy a vSAN witness appliance and build a 2-node cluster (Obj 2.3)
- Set the preferred fault domain and explain partition behaviour
- Explain protection after a host failure, including nested fault domains
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. Two data sites and a third witness site are simulated with nested hosts; witness RTT targets apply to real WAN links.
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 vSAN Witness Configuration (2-Node)
Build 2x ESX hosts (data sites A and B) + 1x vSAN witness appliance (an ESX VM deployed from the OVA) on a third site or host outside the cluster (VCF 9.0.1 docs p.1699); an NFS share cannot act as a witness
Add the witness appliance to vCenter as a host outside the 2-node cluster, then Cluster → Configure → vSAN → Services → Configure → Two-node vSAN cluster → select the witness host
Witness deployed from the vSAN witness appliance OVA at a profile size: Tiny (≤750 components, ≤10 VMs — OSA only; vSAN ESA does not support Tiny), Medium (≤21,833 components, ≤500 VMs — the ESA minimum), Large or Extra Large (VCF 9.0.1 docs pp.1699-1700). The profile fixes the appliance's vCPU/RAM/disk.
Test quorum loss: Power down one ESXi host → Remaining host + witness maintain quorum
Verify: vSAN health dashboard → Witness health = green
Validation Gate
Check: After configuring 2-node vSAN with witness: verify witness connectivity to both hosts, confirm preferred fault domain assignment, and simulate a host failure to validate HA behavior
Expected: Witness shows connected to both data hosts. Preferred host is set. During simulated failure of non-preferred host: VMs restart on preferred host, vSAN objects degrade to single copy but remain accessible.
Common Errors
Final Validation
Gate: every check below passes with the evidence recorded in the lab log.
✓ Witness → Witness host connected to both data hosts
✓ Preferred site → Preferred fault domain set in Configure → vSAN → Fault Domains
✓ Failure test → VMs restart on the surviving host and objects stay accessible
Cleanup / Restore
• Remove the 2-node test cluster and the witness appliance if they are not needed later
Design Reflection (VCDX)
2-node vSAN is relevant for edge/ROBO architectures in VCDX defense. Panelists test whether you understand the limitations (mirroring between hosts, nested fault domains for in-host protection, single host failure tolerance) and when to recommend 2-node vs 4-node clusters.
Requirements
- Deploy 2-node vSAN with witness for edge/ROBO site
- Configure preferred fault domain for predictable partition behavior
- Understand single-host-failure tolerance limitations
Constraints
- 2-node vSAN mirrors between hosts (FTT=1); nested fault domains add protection inside each host
- Witness must be in separate failure domain
- Network partition behavior depends on preferred fault domain config
Assumptions
- WAN connectivity to witness site is reliable
- Edge workloads can tolerate single-copy risk during host failure, or nested fault domains are configured
Risks
- Both hosts failing simultaneously — total data loss
- Witness network failure causing quorum loss and vSAN offline