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 -
What is Alarm Scope?      Creating the Second Alarm of a Multi-alarm Behavior Model

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.

   

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

    

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.