Lab: vSAN Skyline Health Interpretation
Objectives
- Run vSAN Skyline Health and interpret its network, data and cluster findings, including the description and remediation each finding links to (Obj 5.6)
- Read how a simulated host failure surfaces in the health and object views: components Absent and the 60-minute Object Repair Timer
- Confirm recovery from the health view: Resyncing Objects back to 0 and all objects compliant (the full resync-after-failure exercise is lab vvf-support-07)
Prerequisites
Holodeck VVF 9.0 instance with a healthy vSAN cluster (all Skyline Health checks green before starting)
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.
Credentials
| System | Username | Password |
|---|---|---|
| vCenter | administrator@vsphere.local | Holodeck documented default (Post Deployment table) |
| VCF Operations | admin | Holodeck documented default (Post Deployment table) |
| Nested ESX hosts | root | Holodeck documented default (Post Deployment table) |
Tasks
Task 1 Skyline Health interpretation, simulated failure and recovery check
Use vSAN Skyline Health as the diagnostic lens: retest, interpret each finding category with its description and remediation, then read how a simulated failure and its recovery show up in the health and object views. Resync is observed here only as far as the health view shows it; the full resync-after-failure exercise is lab vvf-support-07.
vSphere Client → Cluster → Monitor → vSAN → Skyline Health → Retest (VCF 9.0.1 docs p.1809).
Review the results: note any yellow or red findings and open each for its description and remediation.
Check the network findings: RTT must stay under 1 ms between hosts in a single-site cluster (5 ms between stretched-cluster sites, 200 ms to the witness — VCF 9.0.1 docs p.1664).
If the MTU check fails: MTU is a distributed-switch property, not a port-group field — Distributed Switch → Configure → Properties → Advanced → MTU = 9000, and check the vSAN VMkernel adapter's MTU. Test end to end with vmkping -I <vsan vmk> -d -s 8972 <peer vSAN IP>.
Simulate a failure (lab only): power off one nested ESX host, or remove a virtual disk from a nested host's VM configuration. Do not use the vSphere Client remove-disk workflow — that is a planned evacuation, not a failure, and vSAN ESA has no disk groups to remove from.
Monitor the effect: Cluster → Monitor → vSAN → Resyncing Objects (objects, bytes left, ETA). A powered-off host's components are Absent, so vSAN waits for the 60-minute Object Repair Timer before rebuilding; a removed device that reports errors is Degraded and rebuilds at once. On a host, esxcli vsan debug resync list shows the same. This lab only checks that the health view reflects the failure; the full resync-after-failure exercise (repair timer, resync to completion, workload latency and throttling decisions) is lab vvf-support-07.
Recover: power the host back on (or re-attach the disk). Confirm Resyncing Objects returns to 0 and Skyline Health shows all objects compliant. (For resync monitoring end to end, use lab vvf-support-07.)
Validation Gate
Check: Run vSAN health check, identify any warnings/errors, verify resync status (if any), and confirm all objects have full component count
Expected: vSAN health: all green (or yellow with known/documented exceptions). Resync: no active resyncs (or resync completing with expected ETA). Object health: all objects at full component count per storage policy.
Common Errors
Final Validation
Gate: every check below passes with the evidence recorded in the lab log.
✓ Skyline Health retest → Findings noted and explained; network RTT within the documented limits
✓ Simulated failure → Components Absent; no rebuild before the repair timer
✓ Recovery → Resyncing Objects returns to 0; all objects compliant
Cleanup / Restore
• Power on any nested host left off
• Restore any changed Object Repair Timer to its default (60 minutes)
Design Reflection (VCDX)
vSAN operational health is a common VCDX defense topic. Panelists test whether you understand resync behavior, health check interpretation, and when manual intervention is appropriate vs when to let vSAN self-heal.
Requirements
- Monitor vSAN health checks continuously
- Understand resync behavior and timing
- Interpret object health status correctly
Constraints
- Do not intervene during active resync
- Resync consumes network bandwidth — may impact workload I/O
- Health checks must be reviewed proactively, not just during incidents
Assumptions
- vSAN health check service is running and alerts are forwarded
- Network bandwidth is sufficient for resync operations
Risks
- Data loss from second failure during reduced-availability state
- Resync impacting workload I/O during peak hours
⚠ Known Pitfalls
References
- VCF 9.0 documentation — vSAN Skyline Health (p.1809)Tier 1 — Official
- VCF 9.0 documentation — Monitor the resynchronization tasks (p.1803)Tier 1 — Official
- VCF 9.0 documentation — vSAN network requirements (p.1601, p.1608)Tier 1 — Official