Lab: Configure Custom Alarms & vSAN Health Check
Objectives
- Create a two-level custom CPU alarm with email action and reset rule (Obj 4.3)
- Trigger it with stress-ng and confirm the notification
- Run vSAN Skyline Health and remediate an MTU finding
Prerequisites
Holodeck VVF 9.0 instance; a Linux test VM with stress-ng installed; an SMTP sink VM reachable from vCenter
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. Needs an SMTP sink VM and a Linux test VM; both can run in Holodeck.
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 Configure Custom Alarms & vSAN Health Check
vCenter → Configure → Settings → General → Mail: set the SMTP server and sender (lab: any SMTP sink VM), then Alarms → Alarm Definitions → Add
Target VM; rule 1: VM CPU usage above 75% for 5 min = Warning; rule 2: above 85% for 5 min = Critical; reset rule: back to normal below 75%
Actions: send email notification to the ops mailbox on Warning and on Critical (and optionally on reset)
Power on VM, run stress-ng cpu benchmark: stress-ng --cpu 8 --timeout 300s
Verify alarm fires (may delay 5-10min)
vSAN cluster → Health Check → Run now
Review results: Any yellow/red warnings indicate misconfigurations
Remediate: if the MTU check fails, verify that the vDS MTU and each host's vSAN VMkernel MTU match end to end (and that the physical switch ports carry it)
Validation Gate
Check: Create a custom CPU alarm for critical VMs (warn at 75%, alert at 85%, notify via email), verify it triggers, and confirm email notification is received
Expected: Alarm triggers at 75% CPU, sends warning email. At 85%, sends critical email. When CPU drops below 75%, alarm auto-resets. Alarm actions log shows successful notification delivery.
Common Errors
Final Validation
Gate: every check below passes with the evidence recorded in the lab log.
✓ Alarm → Warning at 75% and Critical at 85% fire with email; alarm resets below 75%
✓ Skyline Health → Retest run; any finding explained and fixed
Cleanup / Restore
• Disable or delete the test alarm
• Power off the stress-ng VM
Design Reflection (VCDX)
Monitoring and alerting design is part of operational architecture in VCDX. Panelists ask: how does your ops team know something is wrong? Custom alarms, notification integration, and vSAN health monitoring are expected components of a complete design.
Requirements
- Configure custom alarm thresholds per workload tier
- Set up notification actions (email, SNMP, webhook)
- Monitor vSAN health checks proactively
Constraints
- Default alarms are generic — must be customized for SLAs
- SMTP/SNMP infrastructure must be available for notifications
- Too many alarms cause alert fatigue
Assumptions
- Organization has email/paging infrastructure for notifications
- Operations team reviews and acts on alerts within SLA timeframes
Risks
- Alert fatigue from uncustomized thresholds flooding notifications
- Silent failures from alarms without configured actions
⚠ Known Pitfalls
References
- vSphere 9.0 documentation — Alarm definitions and actionsTier 1 — Official
- VCF 9.0 documentation — vSAN Skyline Health (p.1809)Tier 1 — Official