Designing and Managing Behavior Models - Behavior Models and Their Components - Constructing Behavior Models - An Example of a Behavior Model -
Previous: How the Pieces Fit Together     Next: NerveCenter Support for SNMP v3

An Example of a Behavior Model

This section presents an overview of the set of steps you would need to perform to create a behavior model that monitors node interfaces. The possible interface conditions are link up and link down.

  1. Create a property group named CheckLink.
  2. Add to this property group the properties ifEntry (base object) and
    checkLink (user defined).
  3. Assign the property group CheckLink to all of the managed nodes whose interfaces you want to monitor.
  4. Create two masks: LinkUp and LinkDown.

    The values you use to create LinkUp are shown in the table below.

    Values Needed to Create LinkUp

    Attribute Value

    Name

    LinkUp

    Generic

    LinkUp=3

    Trigger Type

    Simple Trigger

    Enabled

    On


    The definition for LinkDown is the same as the definition of LinkUp except for the name of the mask and Generic SNMP trap number (LinkDown=2).

  5. Create the alarm shown below.

    An Alarm: IfLinkUpDown

    alarm_iflinkupdown.gif

    Once this alarm is enabled, the behavior model will become functional.

    The IfLinkUpDown alarm contains the property ifEntry, which is in the property group CheckLink. Even though a trap mask filters all traps sent to NerveCenter, the IfLinkUpDown alarm will only become instantiated when the SNMP agent sending the trap belongs to a node in the CheckLink property group.

Here's how the behavior model might interact with one port on a workstation that belongs to the property group:

  1. The mask LinkDown will cause a transition to the DownTrap state, as well as start a three-minute timer (linkTimer).
  2. If the agent comes back up, then the alarm transitions back to Ground and the timer is cleared.
  3. If three minutes has past, and the interface remains down, then the alarm transitions to LinkDown, and sends a 7004 Inform to the network management platform.


Previous: How the Pieces Fit Together Next: NerveCenter Support for SNMP v3
Please send comments or corrections to Information Development
This file was last updated on 10 October 2000