Learning How to Create Behavior Models - How to Use Alarm Scope in Behavior Models - How to Use Alarm Scope in a Multi-alarm Behavior Model -
Previous: What is Alarm Scope?     Next: Review and Summary

How to Use Alarm Scope in a Multi-alarm Behavior Model

In this next scenario you want to monitor a specific node within the CriticalDevices property group because it has been experiencing unusually high traffic. The overworked device has four key ports. You don't care to be notified when just one port is busy. However, you would like to know when all four ports are busy.

Creating just one alarm with SubObject scope will not be enough, since NerveCenter would then only track one instance on each individual port. Creating an alarm with Node scope will not be enough, since you need to track more than one instance on the same node.

For this scenario, you will need to create a multi-alarm behavior model that uses NerveCenter's alarm scope feature to keep track of the different instances.

The scenario includes the following three activities:

1. Creating the First Alarm of a Multi-alarm Behavior Model
2. Creating the Second Alarm of a Multi-alarm Behavior Model
3. Adding Reset Capabilities to a Multi-alarm Behavior Model

Creating the First Alarm of a Multi-alarm Behavior Model

This first activity will step you through the process of creating an alarm that monitors your network at the SubObject Scope level.

 
  To create the first alarm of a multi-alarm behavior model:

1. Create a new alarm, naming it 1BusyPort and setting the property to myNodes.
2. Set the Scope field of the new alarm to SubObject.

   By setting the alarm scope to SubObject, you are telling 1BusyPort to track a separate instance for each port on the overworked node.

3. In the alarm's state diagram, add a state, naming it BusyOnce with a traffic severity of Medium.

   

4. Add another state, naming it BusyTwice with a traffic severity of Very High.
5. In the alarm's state diagram, add a transition that moves from Ground to BusyOnce when the trigger portTraffic is fired.

   

6. Add another transition that moves from BusyOnce to BusyTwice when the trigger portTraffic is fired.
7. In the Transition definition window, select New Action. Then, select FireTrigger.

   The Fire Trigger Action window appears.

   Fire Trigger Action Window

   

8. In the Trigger Name field, type portTooBusy.
9. Leave the NerveCenter defaults in the SubObject, Node, and Property fields.

   The defaults ensure that the resulting trigger will drive only alarm instances that monitor the same subobject and node as the current alarm instances.

10. Since there is no need for a timer in this behavior model, leave the delay time set to zero.
11. In the Fire Trigger Action window, select OK.

    The Fire Trigger Action is added to the transition's Actions list.

12. In the Transition Definition window, select OK.
13. Resize and position the state diagrams icons as needed.

    The Completed State Diagram for 1BusyPort

    

    Click the thumbnail above to view full-sized image.

14. In the Alarm Definition window, select Save.

In this activity you created the first alarm of a multi-alarm behavior model. This alarm will fire a trigger called portTooBusy. However, no alarm is currently listening for this trigger. The next activity will step you through the process of creating the second alarm of this behavior model.

Creating the Second Alarm of a Multi-alarm Behavior Model

In the last activity you created the first alarm of a multi-alarm behavior model for monitoring traffic on an overworked node. In that alarm, high-traffic conditions on a single subobject (port) would cause the portTooBusy trigger to be fired.

This next activity will step you through the process of creating a second-level node scope alarm involving the portTooBusy trigger.

 
  To create the second alarm of a multi-alarm behavior model:

1. Create a new alarm, naming it 1BusyNode. You can leave the property at NO_PROP.

   Setting the property to myNodes is unnecessary since all the triggers for this alarm will be fired by the alarm created in the last activity.

2. Set the alarm's Scope field to Node.

   By selecting Node Scope, you are indicating that this alarm should keep track of instances for the entire node.

3. In the state diagram, add the following states.

   

   1. 1PortBusy with a traffic severity of Low
   2. 2PortsBusy with a traffic severity of Medium
   3. 3PortsBusy with a traffic severity of High
   4. 4PortsBusy with a traffic severity of Very High

      If you add a new state and cannot see the state's icon, it may be hidden behind another state icon. Resizing and positioning your icons will make the state diagram easier to read.

4. In the state diagram, add a transition that moves from the Ground state to the 1PortBusy state, when the portTooBusy trigger is fired.

   

5. In the Transition Definition window, select New Action. From the alarm action list, select Log to File. In the File Name field, type BusyLog.
6. Repeat the last step to add the following transitions:
   1. 1PortBusy --> portTooBusy --> 2PortsBusy
   2. 2PortsBusy --> portTooBusy --> 3PortsBusy
7. Add another transition that moves from the 3PortsBusy state to the 4PortsBusy state when the portTooBusy trigger is fired.
8. In the Transition Definition window, select New Action. From the alarm action list, select Paging.

   The Paging Action window appears.

   Paging Action Window

   

   ---

   Note    Before you can use the Paging action, someone must have configured NerveCenter to handle paging actions correctly. If this has not been done, or you do not use a pager, substitute an alarm action of your choice.

   ---

9. In the Pager Number field, type your pager's phone number.

   The pager number is the sequence of digits and special Hayes AT commands needed by the Paging action to reach the pager. For a list of valid commands, see your modem manual.

10. In the Alarm Code field, either type a number that identifies the network situation being reported or leave it set to the default.

    The alarm code is a sequence of digits that is displayed on the pager. The maximum number of digits that a pager can display varies from pager to pager. If you don't supply an alarm code, a default value of 911 is used.

11. In the Terminate field, type the character that terminates the paging connection on your pager.

    This character is a key the paging system uses to terminate the connection and send the page. If differs from system to system, but is usually # (pound sign) or * (asterisk). Consult your paging system manual to determine the correct key for your system. If you don't specify a key, the Paging action uses the default value #.

12. In the Paging Action window, select OK.

    The Paging action is added to the Transition Definition window's action list.

13. In the Transition Definition window, select OK.
14. In the Alarm Definition window, select Save.

You have now created the second alarm of the multi-alarm behavior model to monitor high-traffic conditions on an overworked node.

However, what if the other ports are free again by the time the fourth port becomes too busy? The next activity will step you through the process of modifying the two alarms to allow for the behavior model to be reset should lower traffic conditions arise.

Adding Reset Capabilities to a Multi-alarm Behavior Model

In the previous two activities you created a multi-alarm behavior model that will monitor high-traffic conditions on different ports of a single node.

NerveCenter will page you as soon as the fourth port on a node reports high-traffic conditions. However, what if traffic on one of the ports drops off? You need some way for your behavior model to reset itself to keep track of the ebb and flow of traffic conditions on your network.

This next activity will step you through the process of modifying the first and second alarm of your multi-alarm behavior model to allow for it to reset conditions.

 
  To add reset capabilities to a multi-alarm behavior model

1. In the Alarm Definition window of 1BusyPort, add a transition that moves from BusyOnce to Ground when the trigger notBusy is fired.

   

2. Add another transition that moves from BusyTwice to Ground when the notBusy trigger is fired. Have the transition fire the backUpOne trigger.
3. In the Alarm Definition window, arrange the state diagrams so they are easier to read. Then select Save.
4. In the Alarm Definition window of 1BusyNode, add the following transitions:
   1. 4PortsBusy --> backUpOne --> 3PortsBusy
   2. 3PortsBusy --> backUpOne --> 2PortsBusy
   3. 2PortsBusy --> backUpOne --> 1PortBusy
   4. 1PortBusy --> backUpOne --> Ground
5. In the state diagram, resize and position the icons as necessary.
6. In the Alarm Definition window, select Save.
7. Turn the 1CheckTraffic poll and the 1BusyPort and 1BusyNode alarms on.

   Unless one of the nodes in the CriticalDevices property group has four interfaces, the alarm 1BusyNode will not reach the final state.

   

   Click the thumbnail above to view full-sized image.

You have just completed creating a sophisticated multi-alarm behavior model using alarm scope to limit NerveCenter's monitoring activities.

The next chapter will explain how to use the Action Router to tell NerveCenter when to perform certain actions.