VMware VirtualCenter 1.1 Support Documentation
Features |
Documentation |
Knowledge Base |
Discussion Forums
 Prev
Contents
Last
Next 
Working with Alarms
Alarms send notification messages when selected events occur to or on hosts or virtual machines. Alarms indicate the status levels of an object, or collection of objects, in the hierarchy. Alarms can be defined at all hierarchical levels, including farms, groups, hosts and virtual machines.
Alarms are inherited from parent levels, and cannot be changed or overridden at a child level. Add new alarms to any object, and contribute to the collection of alarms that are in force at any of its child levels.
When an alarm is created, VirtualCenter verifies the user permissions to perform the actions on the relevant farms, hosts, and virtual machines. Once the alarm is created, the alarm is performed even if the creating user no longer has permission to create the alarm.
Alarms are applied to either hosts or virtual machines. Each alarm has a triggering event and a notification method.
There are two kinds of alarm triggers:
- Percentage — Monitors host CPU usage, host memory usage, virtual machine CPU usage, virtual machine memory, and virtual machine heartbeat
The triggering options are: Is Above (percent) and Is Below (percent). Default monitor for virtual machine heartbeat is set to Is Below. Default monitor for all other percentage options is set to Is Above.
- State — Monitor host state and virtual machine state
The triggering options are: Is (state) and Is Not (state)
There are several types of alarm notification methods:
- Send a notification email message
SMTP sends an email message. The SMTP must be ready when the email message is sent. There are two ways to set SMTP: through VirtualCenter, or through Microsoft Outlook Express. The VirtualCenter setup is not always needed if the SMTP setting in Outlook Express is correct.
The VirtualCenter server generates the subject and body text of the email message. Only the To list (receiver) is required from user input. Specify the email message address where the message should be sent. Separate the names of multiple receivers with commas or semi-colons.
- Send a notification trap
The VirtualCenter server is the default SNMP notification receiver. An SNMP trap viewer is required to view a sent trap. The VirtualCenter server host must be configured to receive SNMP traps.
- Run a script
The user script command and its arguments need to be formatted into one string.
The user script is running as separate process and does not block the VirtualCenter server processes. But the script does run and consume the resources on the VirtualCenter server machine, such as CPU and memory.
- Suspend the virtual machine
- Power off the virtual machine
- Reset the virtual machine
The actions available with alarms are described in the following sections:
Preparing for Email Message SMTP Alarm Notification
Preparing for Email Message SMTP Alarm Notification
If you are going to use email message to send SMTP notification, you need to:
- Define the SMTP and email message addressing information.
- Specify the email message address for those to receive the notification when you create the alarm.
To define the SMTP and email message addressing information:
- From the VirtualCenter client, display the VirtualCenter Settings, Advanced tab dialog box.
Select File > VirtualCenter Settings > Advanced tab.
- Enter the SNMP and mail addressing, as appropriate. Click OK.
For email message notification set the SMTP server, SMTP port, and email message sender.
- mail.sender — The email message address of sender, for example, mail_server@datacenter.com
- mail.smtp.server — The DNS name or IP address of the SMTP gateway to use for sending email message.
- mail.smtp.port — The port number for the SMTP gateway.
If the port value is empty, VirtualCenter uses the default port. The default port is 25.
Scroll through the Advanced tab options. Enter data into the fields. Click OK.
Preparing for SNMP Alarm Notification
Preparing for SNMP Alarm Notification
To use SNMP traps, you must configure:
- The VirtualCenter server host.
- The SNMP receiver server to accept the traps from VirtualCenter.
When you create an alarm, only one trap is triggered and sent. The alarm parameters include:
- Type — The state VirtualCenter is monitoring for the alarm. Options include: Host CPU usage, Host Memory Usage, Host State, Virtual Machine CPU usage, Virtual Machine Memory Usage, Virtual Machine State, Virtual Machine Heartbeat
- Name — The name of the host or virtual machine that triggers the alarm.
- Old Status — The alarm status before the alarm was triggered.
- New Status — The alarm status when the alarm is triggered.
- Object Value — The object value when the alarm is triggered.
To define the SNMP information:
- From the VirtualCenter client, display the VirtualCenter Settings, Advanced tab dialog box.
Select File > VirtualCenter Settings > Advanced tab.
- Enter the SNMP and mail addressing, as appropriate.
Configure up to four receivers of SNMP traps. They must be configured in numerical order, 1, 2, 3, and 4. Each SNMP trap requires a corresponding host name, port and community. For example:
- snmp.reciever.1.name — The DNS name, and IP address of the SNMP receiver.
- snmp.reciever.1.port — The port number of the receiver.
If the port value is empty, VirtualCenter uses the default port. The default port is 162.
- snmp.reciever.1.community — The community identifier.
Scroll through the Advanced tab options. Enter the data into the fields. Click OK.
Using MIBs with Your SNMP Traps
Using MIBs with Your SNMP Traps
VirtualCenter allows you to configure SNMP traps for alarm notification of events occurring in VirtualCenter. Though do continue to use your GSX Server or ESX Server MIBs for host related alarms.
The traps defined here are sent typically to other management programs. These management programs need to know how to interpret the SNMP traps sent by VirtualCenter.
To configure your management program to interpret VirtualCenter SNMP traps:
- Download the management information base (MIB) definitions.
- Modify your management program to include and interpret the VMware MIBs.
Refer to your management program documentation for information on adding MIB definitions to your program.
SNMP Trap and Variable Definitions
SNMP Trap and Variable Definitions
There are two groups of SNMP MIB definitions. These can be downloaded for your use. Refer to Using MIBs with Your SNMP Traps.
The VMware enterprise tree is at .iso.dod.org.internet.private.enterprises.vmware. (.1.3.6.1.4.1.6876.).
The tree consists of several groups. The SNMP traps are at 1.3.6.1.4.1.6876.50.301 and labeled vpxdTrap. System uptime is measured in ticks.
Identification Map
|
Labels
|
1.3.6.1.2.1.1.3.0
|
System up time = ticks
|
1.3.6.1.6.3.1.1.4.1.0
|
Trap name = 1.3.6.1.4.1.6876.50.301 = vpxdTrap
|
1.3.6.1.6.3.1.1.4.3.0
|
Enterprise = 1.3.6.1.4.1.6876 = vmware
|
The table below lists the identification mapping for each VirtualCenter MIB group.
Identification Map
|
Label
|
1.3.6.1.4.1.6876.50.301
|
vpxdTrap Type
|
1.3.6.1.4.1.6876.50.302
|
vpxdHostName
|
1.3.6.1.4.1.6876.50.303
|
vpxdVMName
|
1.3.6.1.4.1.6876.50.304
|
vpxdOldStatus
|
1.3.6.1.4.1.6876.50.305
|
vpxdNewStatus
|
1.3.6.1.4.1.6876.50.306
|
vpxObjValue
|
The following tables describe the VMware SNMP MIB root and primary subtrees. Currently each subtree has its own MIB file. The tables list the variables used in the SNMP Trap groups.
From VMWARE-ROOT-MIB.mib the following definition mapping.
Label
|
Identification Mapping
|
vmware
|
enterprises 6876
|
vmwSystem
|
vmware 1
|
vmwVirtMachines
|
vmware 2
|
vmwResources
|
vmware 3
|
vmwProductSpecific
|
vmware 4
|
vmwTraps
|
vmware 50
|
vmwOID
|
vmware 60
|
vmwExperimental
|
vmware 700
|
From VMWARE-TRAPS-MIB.mib, the following trap types.
Trap Label
|
Description
|
Variables
|
vmPoweredOn
|
This trap is sent when a virtual
machine is powered ON from a
suspended or a powered off
state.
|
vmID, vmConfigFile
|
vmPoweredOff
|
This trap is sent when a virtual
machine is powered OFF.
|
vmID, vmConfigFile
|
vmHBLost
|
This trap is sent when a virtual
machine detects a loss in guest
heartbeat.
|
vmID, vmConfigFile
|
vmHBDetected
|
This trap is sent when a virtual
machine detects or regains the
guest heartbeat.
|
vmID, vmConfigFile
|
vmSuspended
|
This trap is sent when a virtual
machine is suspended.
|
vmID, vmConfigFile
|
vpxdTrap
|
This trap is sent when entity
status changed.
|
vpxdObjValue, vpxdNewStatus,
vpxdOldStatus, vpxdVMName,
vpxdTrapType, vpxdHostName
|
The following tables describe the variables and parameters used in the VMware VirtualCenter defined SNMP traps.
Note: All variables are read-only. The data type field refers to the SNMP version 1
type described by the structure of management information (SMI). And all variables
and parameters are mandatory.
Variable
|
Description
|
Syntax
|
vmID
|
This is the ID of the affected virtual machine generating
the trap. If the vmID is non-existent, (such as for a
power-off trap) -1 is returned.
|
INTEGER
|
vmConfigFile
|
This is the configuration file of the affected vm
generating the trap.
|
DisplayString
|
vpxdTrapType
|
This is the trap type in the preceding traps.
|
DisplayString
|
vpxdHostName
|
This is the name of the host in the preceding traps.
|
DisplayString
|
vpxdVMName
|
This is the name of the VM in the preceding traps.
|
DisplayString
|
vpxdOldStatus
|
This is the old status in the preceding traps.
|
DisplayString
|
vpxdNewStatus
|
This is the new status in the preceding traps.
|
DisplayString
|
vpxdObjValue
|
This is the current object value in the preceding traps.
|
DisplayString
|
Creating Alarms
Creating Alarms
If you are going to use email message or SNMP notification, refer to Preparing for Email Message SMTP Alarm Notification and define the address information before you create your alarm.
To create an alarm:
- From the VirtualCenter client, display the inventory panel and expand the appropriate object.
Click the Inventory option in the navigation bar. Expand the inventory as needed, and click the appropriate object.
- Display the alarm properties.
Select the object on which you want to apply the alarm.
- Enter the alarm general information.
Specify a name for the alarm, the object to be monitored (host or virtual machine), and whether to enable this alarm.
To define the alarm, but not have it active, uncheck the Enable box.
Click OK.
- Specify the triggering parameters for the alarm.
There are two kinds of triggers:
- Percentage — Monitors host CPU usage, host memory usage, virtual machine CPU usage, virtual machine memory, and virtual machine heartbeat
The triggering options are: Is Above (percent) and Is Below (percent). Default monitor for virtual machine heartbeat is set to Is Below. Default monitor for all other percentage options is set to Is Above.
- State — Monitor host state and virtual machine state
The triggering options are: Is (state) and Is Not (state)
- Click the Triggers tab.
- Using the pull-down menus, indicate the type and condition of the state.
- Optionally, define multiple conditions for the alarm triggering event. Click Add. Enter the parameters for each condition.
- Click OK.
- Specify the action to be taken when the alarm is triggered.
- Click the Actions tab.
- Select a transition state at which to notify.
Select at which transition state the alarm should be triggered. For example, select to trigger the alarm when the CPU usage transitions from a 15% yellow state to a 5% red state, as defined in the Triggers tab, and cause the alarm to suspend the virtual machine.
- Click the appropriate check box.
There are four different level changes: green to yellow, yellow to red, red to yellow, and yellow to green. Attach an action for each level change.
- Select a notification type and provide related information.
Click Add to add as many notifications as needed. The notification options are:
- Send an email message.
Provide the email message address for the notification recipient.
SMTP sends an email message. The SMTP must be ready when the email message is sent. There are two ways to set SMTP: through VirtualCenter, or through Microsoft Outlook Express. VirtualCenter setup is not always needed if the SMTP setting in Outlook Express is correct.
VirtualCenter server generates the email message subject and body text. Only the "to" list (receiver) is required from user input. Specify the email message address to which the message should be sent. Separate multiple receivers with commas or semi-colons.
- Send a notification trap.
There is a default SNMP notification receiver, the VirtualCenter server. An SNMP trap viewer is required to view a sent trap. The VirtualCenter server host must be configured to receive SNMP traps.
- Run a script.
Provide the path to the script to run.
The user script command and its arguments need to be formatted into one string.
The user script is running in other process and does not block the VirtualCenter server from running. But the script does consume the resources on the server, such as CPU and memory.
- Suspend the virtual machine.
This applies to a virtual machine alarm.
- Power off the virtual machine.
This applies to a virtual machine alarm.
- Reset the virtual machine.
This applies to a virtual machine alarm.
- Complete the alarm. Click OK.
VirtualCenter verifies the configuration of the alarm and adds the alarm to the list of alarms for the selected object.
Editing Alarms
Editing Alarms
To edit an existing alarm:
- From the VirtualCenter client, display the inventory panel and expand the appropriate object.
Click the Inventory option in the navigation bar. Expand the inventory as needed,.
- Identify and select the object where the alarm is defined.
- Select an object where the alarm is applied.
- Display the Alarms list. Click the Alarms tab.
- Click the linked object in the Defined in column.
VirtualCenter displays the Alarms panel for the object where the alarm was defined.
- Display the alarm properties.
The entry in the Defined in column for the alarm must be This Object.
Select the alarm to edit. Select Properties from either the main or right-click menu.
- Edit the alarm general information, as needed. Click OK.
VirtualCenter verifies the configuration of the alarm and edits the alarm in the list of alarms for the selected object.
Removing Alarms
Removing Alarms
Remove alarms from the object in which they were defined. You cannot remove them from a child level.
To remove an alarm:
- From the VirtualCenter client, display the inventory panel and expand the appropriate object.
Click the Inventory option in the navigation bar. Expand the inventory as needed,.
- Identify and select the object where the alarm is defined.
- Select an object where the alarm is applied.
- Display the Alarms list. Click the Alarms tab.
- Click the linked object in the Defined in column.
VirtualCenter displays the Alarms panel for the object where the alarm was defined.
- Remove an alarm.
Select the alarm and click Remove from the right-click menu.
Click Yes to confirm removing the alarm.
Prev
Contents
Last
Next
|
