Designing and Managing Behavior Models - Alarm Actions -
Previous: Enabling an Alarm Next: Action Router

Alarm Actions

When you create an alarm, you can specify that one or more alarm actions take place on any alarm transition. These actions fall into two categories: those that affect how the alarm works and those that perform some type of corrective action. An example of the first type of action is the Fire Trigger action. This action (as its name implies) fires a trigger that can cause a transition in its own or another alarm. An example of the second type of action is the Command action, which enables you to run any script or executable when a transition occurs.

Note

The remainder of this chapter discusses how to use each of the NerveCenter alarm actions:

Chapter Contents

Section	Description
Action Router	Explains how to send information about an alarm transition to the Action Router facility. The Action Router enables you to performs actions if certain conditions are met.
Alarm Counter	Explains how to count the number of times that a particular transition has occurred.
Beep	Explains how to send audible alarm to the workstation at which the NerveCenter Client is running.
Clear Trigger	Explains how to clear a trigger that was fired on a delayed basis.
Command	Explains how to execute a program or script from an alarm action.
Delete Node	Explains how to delete the node being monitored by an alarm instance.
EventLog	Explains how to log information about an alarm transition to a system log file (UNIX) or the Event Log (Windows NT).
Fire Trigger	Explains how to fire a trigger as an alarm action.
Inform	Explains how to send the equivalent of an SNMP trap to OpenView Network Node Manager, NetView, or another NerveCenter when a significant network event is detected.
Inform OpC	Explains how to send a message to HP OpenView IT/Operations.
Inform Platform	Explains how to send an event to the following network management platforms: MicroMuse Netcool/OMNIbus, IBM Tivoli Enterprise Console, or Computer Associates Unicenter TNG.
Log to Database	Explains how to log information about an alarm transition to the NerveCenter database.
Log to File	Explains how to log information about an alarm transition to a file.
Microsoft Mail	Explains how to send e-mail to a client of a Microsoft Exchange server.
Notes	Explains how to display the notes (documentation) for an alarm.
Paging	Explains how to send a page as an alarm action.
Perl Subroutine	Explains how to execute a Perl script as an alarm action. Perl scripts are different from other scripts in that they have access to a great deal of internal NerveCenter information.
Send Trap	Explains how to send an SNMP trap as an alarm action.
Set Attribute	Explains how to set an attribute of an alarm, a mask, a node, or a poll as an alarm action.
SMTP Mail	Explains how to send SMTP mail.
SNMP Set	Explains how to send an SNMP SetRequest to set the value of an attribute in an agent's MIB.

Previous: Enabling an Alarm	Next: Action Router
Please send comments or corrections to Information Development	This file was last updated on 10 October © 2002