This topic provides information about the different aspects of an alert action.

You assign actions to an alert definition on the Alert Definition page, which appears when you save a new alert definition or edit an existing alert definition.

The Alert Definition page is similar to the New Alert page, with the addition of Edit controls in the Alert Properties and Condition Set sections, and tabs at the bottom of the page for defining alert actions.

You can specify multiple actions to be performed automatically when an alert fires. The types of actions available in the Alert Definition page vary based on: (1) the type of resource the alert applies to, (2) your version of vCenter Hyperic, and (3) whether you've configured vCenter Hyperic for the types of actions that must be enabled before you can use them, such as escalations, OpenNMS trap actions, and in vCenter Hyperic, SNMP notifications.

To define an alert action, select one of the tabs and supply the required information.

Select an escalation from the Escalation Scheme pulldown; the tab refreshes and shows the escalation steps. You must define an escalation before you can assign it to an alert definition. Using an escalation that is configured to repeat until the alert is fixed is a good way to prevent redundant alerts firing for the same problem. To create an escalation, click Escalation Schemes Configuration on the Administration tab.

In vCenter Hyperic, you can define a resource control action to perform when the alert fires. The control action can target the current resource (the one to which the alert definition is assigned) or a different resource on the same platform, as long as the resource type has supported control actions.

To configure a control action for the alert:

1

Select the Control Action tab and click Edit.

You can only assign a single control action to an alert definition.

You cannot assign a control action to a resource type alert.

In vCenter Hyperic you can specify one or more roles as notification recipients. vCenter Hyperic users with a role you specify will be notified when an alert is fired.

1

Click Add to List on the Notify Roles tab.

2

On the roles selection page, choose the role(s) to be notified when the alert fires.

Click Add to List on this tab to specify non-vCenter Hyperic user email recipients for alert notifications.

In vCenter Hyperic, to assign a script action to the alert definition, click the Script tab, enter the full path to the script, and click Set. vCenter Hyperic will run the script when the alert fires. Scripts can reference alert-related vCenter Hyperic environment variables to perform custom notification logic.

If vCenter Hyperic server is configured for OpenNMS integration, you can use this tab to configure vCenter Hyperic to send an SNMP trap to OpenNMS when the alert fires. The notification will be generated by opennms_notify.gsp alert notification template.

To configure an OpenNMS trap action, enter:

Server - Listen address for the OpenNMS server.

Port for the OpenNMS server.

If the vCenter Hyperic server is configured to send SNMP notifications to your NMS, you can use this tab to configure a trap notification action.

The notification sent when the alert fires will contain three variable bindings:

sysUptimeOID.0 - No configuration is required for this binding.

snmpTrapOID.0 - This binding is configured on the HQ Server settings page.

A variable binding for the alert data specified in the snmp_trap.gsp alert notification template - the alert definition name and the short reason for firing.

To configure an SNMP notification action enter:

IP Address - the address and port of the target NMS.

OID -

The OID of the notification to send, which will contain the alert details specified in the snmp_trap.gsp, template.

Notification Mechanism

v1 Trap

v2C Trap

Inform