Designing and Managing Behavior Models
-
Performing Actions Conditionally
(Action Router) -
When an alarm transition occurs, all the actions associated with that transition are performed unconditionally. However, the responsibility of one action -- Action Router -- is to send information about the transition to the Action Router facility, which performs actions conditionally. That is, the Action Router action always takes place, but the Action Router facility may or may not initiate some other action.
Whether the Action Router facility performs one or more actions -- such as executing a command or logging data to a file -- depends on rules that you've set up using the Action Router. For example, you might want to specify that if a particular alarm transition occurs at night or on the weekend, an administrator should be paged. In this case, the alarm transition has the Action Router action associated with it, and the Action Router rule looks like this:
$DayOfWeek >= MONDAY and $DayOfWeek <= FRIDAY and ($Time < 08:00 or
$Time > 17:00)or ($DayOfWeek == SATURDAY or $DayOfWeek == SUNDAY)
-> Paging 5551234567:911:#
All actions that can be performed from an alarm transition can be performed from the Action Router, except for the Alarm Counter and Action Router actions. Also, rule conditions can be built using many types of data, for example:
For a complete list of the variables that can be used in an Action Router rule condition, see the table NerveCenter Variables on page 293.
The remainder of this chapter explains how to determine what Action Router rules have already been defined and how to create new rules. See the following sections:
Section | Description |
---|---|
Explains how to display a list of the Action Router rules currently defined in the NerveCenter database. | |
SNMP Set | Listing Existing Action Router Rules |
29 July 2003 |