Designing and Managing Behavior Models - Using Alarms -
Previous: Enabling an OpC Mask     Next: Listing Alarms

Using Alarms

Alarms enable you to monitor the state of objects such as interfaces and devices. The figure below depicts the role that an alarm typically plays in a behavior model.

alarms14a.gif

The alarm contains a state transition diagram, and transitions are caused by triggers that are usually generated by polls and trap masks. (Triggers can also be generated by alarms.) When the alarm manager sees a trigger whose key attributes -- such as name, subobject, and node -- match those of a pending transition in an alarm, the manager causes this transition to take place. Any actions associated with the transition are performed when the transition occurs.

The remainder of this chapter explains in detail how to create and work with alarms. Refer to the following sections:

Chapter Contents

Section Description

Listing Alarms

Explains how to display a list of the alarms currently defined in the NerveCenter database.

Defining an Alarm

Explains the procedure for creating a new alarm.

Alarm Scope

Discusses an alarm's scope property. This property defines what an alarm monitors: the entire enterprise, a single device, a subcomponent of a device such as an interface, or multipe MIB objects in a single alarm instance.

Defining States

Explains how to define a state in an alarm's state diagram.

Defining Transitions

Explains how to define a transition in an alarm's state diagram.

Documenting an Alarm

Explains how to write notes (documentation) for an alarm.

Enabling an Alarm

Explains how to turn an alarm on and off.



Previous: Enabling an OpC Mask Next: Listing Alarms
Please send comments or corrections to Information Development
This file was last updated on 10 October © 2002