Designing and Managing Behavior Models
-
Using Alarms - Listing Alarms -
This section explains how to display a list of the alarms currently defined in the NerveCenter database. The section also explains how to view the definition of a particular alarm.
For information on creating a new alarm, see Defining an Alarm.
To display a list of alarms and then display a particular alarm's definition:
From the client's
Admin
menu, choose Alarm Definition List
.
The Alarm Definition List window is displayed.
This window lists all the currently defined NerveCenter alarms and provides a brief definition of each. For each alarm, the window specifies a name and the following information:
Open
buttonNerveCenter displays the Alarm Definition window.
The alarm defined in this figure is named ifLinkUpDown. Each instance of it monitors a single interface (subobject scope) on a device whose property group contains the property ifEntry. If NerveCenter receives a generic trap 2 for an interface, an alarm instance is instantiated, and the current state becomes DownTrap. If a linkUp trap for the same interface arrives within three minutes, the state returns to Ground; otherwise, the state becomes LinkDown. The state color indicates that LinkDown is a state of Major severity.
With a little investigation, you can find out much more about this alarm. For instance, if you right-click a transition, you'll see a pop-up menu that enables you to find out what masks, polls, and alarms can produce the trigger that causes the transition. Trigger Sources shows what objects can fire the triggers that affect this alarm.
Transition | Related Trigger Generator |
---|---|
You can also determine what actions will occur on a particular transition. Simply double-click the transition to bring up the Transition Definition dialog. If you perform this task for each transition in this alarm, you'll find that the transition actions in Transition Actionshave been defined.
Transition | Actions |
---|---|
Inform a network management platform that the interface is down. |
Using Alarms | Defining an Alarm |
29 July 2003 |