Academy/vSphere Foundation 9.0 Support (2V0-18.25)/Lab: vSAN Skyline Health Interpretation
This lab targets VCF 9.0

Lab: vSAN Skyline Health Interpretation

VCF 9.0Intermediatevcp-foundation⏱ 105 min

VVF 9.0 support lab (2V0-18.25). Built for a Holodeck VVF instance.

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

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

Tasks

Task 1 Skyline Health interpretation, simulated failure and recovery check

Interpreting vSAN Skyline Health is a Day-2 operational essential. Knowing what each health check tests, which findings indicate an active problem, and when a finding (such as resync in progress) means let vSAN self-heal rather than intervene separates skilled operators from reactive firefighters.

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.

Step 1

vSphere Client → Cluster → Monitor → vSAN → Skyline Health → Retest (VCF 9.0.1 docs p.1809).

Step 2

Review the results: note any yellow or red findings and open each for its description and remediation.

Step 3

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).

Step 4

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>.

Step 5

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.

Step 6

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.

Step 7

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

Panicking during vSAN resync and attempting manual intervention
Fix: vSAN resync is automatic — after a host failure, disk failure, or policy change, vSAN rebuilds/moves components automatically. DO NOT add/remove hosts or change storage policies during resync. Monitor progress in Cluster → Monitor → vSAN → Resyncing Objects, or with esxcli vsan debug resync list (per-object bytes left; VCF 9.0.1 docs p.1824). Duration depends on the data to move and vSAN network bandwidth.
Ignoring 'Objects with reduced availability' warning
Fix: This warning means some vSAN objects are running on fewer copies than the configured FTT. For RAID-1 FTT=1: objects should have 2 copies. If showing 1 copy, one mirror is missing — likely a host or disk failure is in progress. Check host status immediately. A second failure while in this state causes data loss.
Not understanding vSAN health check categories
Fix: vSAN health checks are grouped: Hardware compatibility (HCL check), Network (connectivity, unicast — vSAN uses unicast, p.1601 — MTU, latency), Data (object health, disk balance), Cluster (capacity, member health), Stretch cluster (witness, preferred domain). Focus on Data and Network categories — these indicate active issues. Treat hardware compatibility warnings as real findings too: an uncertified controller, driver or firmware is a supportability risk and should be planned for correction, not ignored.
Running vSAN health check only during incidents instead of proactively
Fix: vSAN health check should run continuously (it does by default) with alerts forwarded to monitoring. Don't wait for an incident to check health. Schedule weekly health review: check disk balance, capacity utilization trending, and any persistent warnings. Address warnings before they escalate during a failure event.

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

Manually intervening during vSAN resync — adding/removing hosts or changing policies disrupts the automatic rebuild.
Ignoring 'reduced availability' warnings — this is the critical window where a second failure causes data loss.

References

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