Configuring vCenter Server to send alarms when virtual machines are running from snapshots
search cancel

Configuring vCenter Server to send alarms when virtual machines are running from snapshots

book

Article ID: 328627

calendar_today

Updated On:

Products

VMware

Issue/Introduction

This article provides information on configuring VMware vCenter Server to send alerts when virtual machines are running from snapshots.


Resolution



Prerequisites
  • Determine the level of the hierarchy you want to configure the alarm for.
    • The object hierarchy is vCenter > Datacenter > Cluster > Host(s) > Datastore > Folder > Resource Pool > Virtual Machine.
    • Alarms are inherited by all child objects.
    • Once configured you can see the alarm settings from the child objects but it is configurable only from the object where it was created.

  • To create alarms, the vSphere Client or vSphere Web Client must be connected to a vCenter Server with the appropriate user with permissions on all relevant objects. After an alarm is created, it is enabled even if the user who created it no longer has permissions.

To open the Alarm Settings dialog, perform one of these operations:

vSphere Client:
  1. Click File > Prerequisites > Alarm.
  2. Click Inventory > object_type > Alarm > Add Alarm.
  3. Right-click the object and click Alarm > Add Alarm.
  4. In the Alarms tab, select the Definitions tab, right-click in the pane, and click New > Alarm.
  5. Click on the object in the inventory and press Ctrl+A.

Alarm Settings – General tab

To create a new alarm:
    1. Enter an alarm name and description.
    2. Define the type of alarm:
      1. In the Monitor list, click Virtual Machines.
      2. Select Monitor for specific conditions or state.
    3. Select Enable this alarm.

Alarm Settings – Triggers tab

State triggers are set off as soon as a state threshold or condition is achieved. You cannot define condition lengths for state alarms.

Note: You cannot use a virtual machine's Total Size on Disk or VM Snapshot Size triggers in combination with any other triggers.

To add a new alarm trigger:
    1. Click Add.
    2. In the Trigger Type dropdown, click VM Snapshot Size (GB).
    3. In the On Condition dropdown, click Is above.
    4. Double-click the Warning field and enter the desired value.
    5. Double-click the Alert field and enter the desired value.

Define tolerance ranges and trigger frequencies for condition or state triggers.

Alarm Settings – Actions tab

To define an action:
    1. Fill in the Configuration tab with the details required for the configured Action.
    2. Select if you want the action to be executed with a specific frequency, or just when there is a status change from normal to warning, warning to alert, alert to warning, and warning to normal.
    3. Click OK and the alarm is ready.
vSphere Web Client:
    1. Log in to the vSphere Web Client with an administrative user.
    2. Click Hosts and Clusters.
    3. Right-click the object you want to add the alarm to.
    4. Navigate to Alarms > New Alarm Definition...
    5. Enter an alarm name and description.
    6. Select the Monitor dropdown and click Virtual Machines.
    7. Under Monitor for select specific conditions or state, for example CPU usage.
    8. Select Enable this alarm.
    9. Press Next.
    10. Click Add.
    11. In the Trigger Type dropdown, click VM Snapshot Size (GB).
    12. In the Operator dropdown, click Is above.
    13. Double-click the Warning Condition field and enter the desired value.
    14. Double-click the Critical Condition field and enter the desired value.
    15. Press Next.
    16. Click Add.
    17. Select the action you want to occur when the alarm is triggered.
    18. Set the Repeat actions every time if needed.
    19. Set the actions for state changes as needed.
    20. Click Finish.


Additional Information

For more information on investigating why vCenter Server does not send email alerts, see Diagnosing why vCenter Server is not sending email alerts (1004070).

For more information on diagnosing alarms being triggered when no snapshots are present on a virtual machine, see VM Snapshot Size (GB) alarm incorrectly triggers on virtual machines with no snapshots (2037464)

For more information about the settings related to alarms, see Working with Alarms in:

Note: The Delete all snapshots process is improved with these ESX patches:


For translated versions of this article, see:
Diagnosing why VMware vCenter Server is not sending email alerts
VMware ESX 4.0, Patch ESX400-201006201-UG: Updates the VMware ESX 4.0 Core and CIM components
VMware ESXi 4.0, Patch ESXi400-201006201-UG: Updates Firmware
VMware ESXi 3.5, Patch ESXe350-201006401-I-SG: Updates firmware
VMware ESX 3.5, Patch ESX350-201006401-SG: Updates VMkernel, VMware Tools, hostd, VMX, VMnix
Configurando o VMware vCenter Server para enviar alarmes quando as máquinas virtuais estão rodando a partir de instantâneos
Configurar VMware vCenter Server para enviar alarmas cuando las máquinas virtuales se están ejecutando desde snapshots
将 VMware vCenter Server 配置为当虚拟机从快照运行时发送警报
VM Snapshot Size (GB) alarm incorrectly triggers on virtual machines with no snapshots
仮想マシンがスナップショットから実行されている場合にアラームを送信するように VMware vCenter Server を構成する
Konfigurieren von vCenter Server zum Senden von Alarmen, wenn virtuelle Maschinen von Snapshots aus ausgeführt werden

Powered by Wolken Software