Designing and Managing Behavior Models - Creating Multi-Alarm Behavior Models - IfUpDownStatusByType - Interface-type Alarms -
IF-SelectType Perl Subroutine      IfNmDemand Alarm

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 in Interface-type Alarms State Diagram.

Interface-type Alarms State Diagram

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.

IF-IfFramePVC

Unlike the other interface-type alarms, the IF-IfFramePVC relies on a frame relay MIB with which to monitor frame relay permanent virtual circuit (PVC) subinterfaces. NerveCenter instantiates IF-IfFramePVC when a frame relay PVC interface is non-active. The definition for IF-IfFramePVC, is shown in .

IF-IfFramePVC State Diagram

IF-IfFramePVCStatus contains the following states:

• Ground

  No evidence that the interface is down. If the interface is down, goes to FramePVCUp/Down. If the interface is active, goes to IfFramePVC.

• FramePVCUp/Down

  Mask indicates that a link is either up or down. The interface is polled. If the interface is up, NerveCenter sends a 1510 Inform to the platform and returns to IfFramePVC. If a cold or warm start is detected, returns to Ground. If the interface is down, NerveCenter sends a 1511 Inform to the platform and goes to IfFramePVCDown.

• IfFramePVCDown

  Poll indicates that an interface down. NerveCenter sends a 1511 Inform to the platform. The interface is polled. If the interface is up, NerveCenter sends a 1510 Inform to the platform and goes to IfFramePVC. If a cold or warm start is detected, returns to Ground. If the interface is up or down, goes to FramePVCUp/Down.

• IfFramePVC

  Interface is active. If a cold or warm start is detected, returns to Ground. If the interface is up or down, goes to FramePVCUp/Down. If the interface is down, NerveCenter sends a 1511 Inform to the platform and goes to IfFramePVCDown.

IfColdWarmStart Alarm

The IfColdWarmStart alarm detects that a device has been restarted and fires a trigger that causes all the interface-type alarms monitoring that device to return to Ground state.

IF-IfColdWarmStart Alarm

The IfColdWarmStart alarm also fires a trigger that causes a transition in an IfNmDemand alarm.