Academy/vSphere Foundation 9.0 Administrator (2V0-16.25)/Lab: Configure Custom Alarms & vSAN Health Check
This lab targets VCF 9.0

Lab: Configure Custom Alarms & vSAN Health Check

VCF 9.0Intermediatevcp-foundation⏱ 120 min

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

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

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

Tasks

Task 1 Configure Custom Alarms & vSAN Health Check

Custom alarms and vSAN health checks form the operational monitoring foundation. Default alarms are a starting point — production environments need customized thresholds and notification targets specific to the organization's SLAs and on-call procedures.
Step 1

vCenter → Configure → Settings → General → Mail: set the SMTP server and sender (lab: any SMTP sink VM), then Alarms → Alarm Definitions → Add

Step 2

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%

Step 3

Actions: send email notification to the ops mailbox on Warning and on Critical (and optionally on reset)

Step 4

Power on VM, run stress-ng cpu benchmark: stress-ng --cpu 8 --timeout 300s

Step 5

Verify alarm fires (may delay 5-10min)

Step 6

vSAN cluster → Health Check → Run now

Step 7

Review results: Any yellow/red warnings indicate misconfigurations

Step 8

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

Relying solely on default vCenter alarms without customization
Fix: Default alarms use generic thresholds that suit no particular workload (check the built-in definitions in Alarm Definitions). For latency-sensitive workloads like databases, 75% CPU may be the appropriate warning threshold. Create custom alarm definitions for each workload tier: critical VMs at lower thresholds, dev VMs at higher thresholds.
Not configuring alarm actions (notifications)
Fix: An alarm without an action is invisible. Configure alarm actions: email notification (SMTP settings in vCenter), SNMP trap (to monitoring platform), or script execution (for auto-remediation). Most production incidents are discovered by users, not monitoring — because alarm actions were never configured.
Ignoring vSAN health check warnings
Fix: vSAN health check warnings (yellow) indicate degraded but functional state. Common warnings: 'Controller driver is VMware certified' (driver update needed), 'vSAN disk balance' (>30% imbalance), 'Network: All hosts have a vSAN vmknic configured' (misconfigured host). Address warnings proactively — they escalate to critical during host failures.
Setting alarm frequency too high causing notification flood
Fix: An alarm that triggers every minute for CPU utilization generates 1,440 alerts/day per VM. Configure: frequency (once every 30 min), tolerance (trigger only after condition persists for 5 min), and reset condition (auto-clear when condition resolves). This reduces noise and makes alerts actionable.

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

Presenting a VCDX design with no custom alarm definitions — this signals lack of operational planning.
Setting identical thresholds for all VM types — database VMs need different thresholds than web servers.

References

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