Designing and Managing Behavior Models - Creating Multi-Alarm Behavior Models - IfUpDownStatusByType - Interface-type Alarms -
Previous: IF-SelectType Perl Subroutine     Next: IF-IfFramePVC

Interface-type Alarms

The IfUpDownStatusByType behavior model has an alarm for each interface type (ATM, ISDN, FDDI, and so on) that it monitors. The interface alarms (with the exception of IF-IfFramePVCStatus) are identical. The definition for these alarms, is shown below.

The interface-type alarms (with the exception of IF-IfFramePVCStatus) contain the following states:

• Ground

  No evidence that the interface is down, or in testing mode.

• IfNotAdminOp

  An initial indication that an interface is either down or in testing mode has been received by a poll. The interface is categorized (ATM, FDDI, LAN, and so on) and the appropriate alarm is transitioned.

• IfUpDownTrap

  Mask indicates that a link is either up or down. The interface is polled. If the interface is up, NerveCenter sends a 1512 Inform to the platform and returns to Ground. If a cold or warm start is detected, returns to Ground. If the interface is down or in testing, NerveCenter sends a 1514 Inform to the platform and goes to IfDown.

• IfDown

  Poll indicates that an interface down. NerveCenter sends a 1514 Inform to the platform. The interface is polled. If the interface is up, NerveCenter sends a 1512 Inform to the platform and returns to Ground. If a cold or warm start is detected, returns to Ground. If the interface is in some test mode, NerveCenter sends a 1513 Inform to the platform and goes to IfTesting.

• IfTesting

  Poll indicates that an interface is in some test mode. NerveCenter sends a 1513 Inform to the platform. The interface is polled. If the interface is up, NerveCenter sends a 1512 Inform to the platform and returns to Ground. If a cold or warm start is detected, returns to Ground. If the interface is down, NerveCenter sends a 1514 Inform to the platform and goes to IfDown.