Learning How to Create Behavior Models - How to Use Alarms - How to Create an Alarm - Enabling an Alarm -
How to Create an Alarm      Modifying an Alarm's State Diagram

Enabling an Alarm

You have just completed creating the 1HighTraffic alarm. You designed the state diagram to transition the alarm from the Ground state to the Busy state when NerveCenter fires the trigger portTraffic.

This next activity will step you through the process of enabling your new 1HighTraffic alarm.

 
  To enable an alarm:

1. From the Admin menu, choose Poll List.

   

   NerveCenter displays the Poll List window.

   The 1CheckTraffic poll should have Enabled listed as On.

2. If the 1CheckTraffic poll is not enabled, turn it on.
3. From the Admin menu, choose Alarm Definition List.

   

   NerveCenter displays the Alarm Definition List window.

   

   The Alarm Definition list should include the new 1HighTraffic alarm.

4. Right-click on the alarm 1HighTraffic.

   Notice the pop-up menu gives you several ways to alter the alarm without entering the Alarm Definition window.

5. Select On.

   This enables the 1HighTraffic alarm.

   You soon should hear beeps.

   ---

      When the alarm is in the Busy state, NerveCenter will not send the poll out to the node again because of smart polling.

   ---

6. From the Admin menu, choose Alarm Summary.

   

   NerveCenter displays the Alarm Summary window.

   

   The Alarm Summary window presents information about the active alarms for the active server. The alarm summary tree on the left displays folders for the different levels of alarm severity.

   On the right is a list of all the current alarm instances. It includes the following information:

   • The name of the alarm
   • The time and date the alarm was instantiated
   • The node and subobject which had the conditions of interest
   • The name and the severity of the alarm's current state
   • The name of the trigger that caused the transition
   • The type and name of trigger generator

     In the alarm summary tree, there should be numbers beside Low, Traffic, and Severity. In the alarm instances list, 1HighTraffic probably has several alarm instances.

     You originally set the alarm's Scope to SubObject. The alarm 1HighTraffic, therefore, monitors each of your node's ports separately. Because of this there may be more than one alarm instance per node in your CriticalDevices group. If you had set Scope to Node, it would have shown no more than one instance per node.

7. Turn the 1CheckTraffic poll and the 1HighTraffic alarm to Off.

You just created, enabled, and viewed instances of your first poll. Now it is time to modify the 1HighTraffic alarm to make it easier to read and more useful. The next two activities will show you how to do that.