Search the VMware Knowledge Base (KB)
View by Article ID

Adding alarms to vCenter Server for vSAN 5.5 monitoring (2091347)

  • 5 Ratings
Language Editions

Purpose

This article outlines how to define alarms for these vSAN state changes:
  • Disk removal/loss
  • Disk failure
  • Congestion affecting performance
  • Cluster is approaching component maximums

Note: vCenter Server does not have default alarms for certain vSAN host, cluster or disk state-changes.

Resolution

Notes
  • Defining the alarm is demonstrated with screen shots for the first alarm and required parameters are provided for all alarms.
  • This procedure is not required in VSAN 6.x because these alarms are present by default.

To define alarms for vSAN state changes, for example, disk removal/loss:
  1. Log in to vCenter Server through the vSphere Web Client.
  2. From the Hosts and Clusters view, right-click vCenter and click Alarms > New Alarm Definition.
  3. Under New Alarm Definition Window, click General.
  4. In General section, provide an Alarm name/Description, the monitoring scope, and select specific event occurring on this object, for example VM power ON.



    Note: Ensure that the Enable this alarm check box is selected.

  5. Click Triggers.
  6. Type the applicable VOB as the event trigger, with a status = Alert:



    Note: The VOB is not pre-populated in the event drop-down. You need to type it manually or copy/paste into the field and finish by pressing the ENTER key. If you do not press the ENTER key, it may result in the field reverting to another value from the drop-down.

  7. Proceed through the wizard and select applicable actions (Email should be sent, SNMP traps sent, and so on.)
  8. Complete the wizard.
Perform the preceding process for all four commonly useful VOBs. You must configure the four alarms with these parameters:
  • vSAN Disk Removal/Loss

    Name: vSAN Disk Offline
    Description: Alarm will trigger when a vSAN disk goes offline or enters a PDL state.
    Monitor: Hosts
    Monitor for: Specific event occurring on this object.
    Event: esx.problem.vob.vsan.pdl.offline
    Status: Alert
    Actions: As desired.
  • vSAN Disk Under Permanent Error

    Name: vSAN Disk Permanent Error
    Description: Alarm will trigger when a vSAN disk enters a permanent-error state.
    Monitor: Hosts
    Monitor for: Specific event occurring on this object.
    Event: esx.problem.vob.vsan.lsom.diskerror
    Status: Alert
    Actions: As desired.
  • vSAN Congestion Threshold Reached

    Name: vSAN Congestion Threshold Reached
    Description: Alarm will trigger when a vSAN host is under congestion to that point that performance will be significantly degraded.
    Monitor: Hosts
    Monitor for: Specific event occurring on this object.
    Event: esx.problem.vsan.lsom.congestionthreshold
    Status: Warning
    Actions: As desired.
  • vSAN Component limit approaching

    Name: vSAN Component Limit Approaching
    Description: Alarm will trigger when a vSAN host is approaching its maximum number of objects/components.
    Monitor: Hosts
    Monitor for: Specific event occurring on this object.
    Event: esx.problem.vob.vsan.lsom.componentthreshold
    Status: Warning
    Actions: As desired.

See Also

Update History

03/09/2015 - Updated note about event dropdown box, to be more comprehensive.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 5 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 5 Ratings
Actions
KB: