Designing and Managing Behavior Models - Creating Multi-Alarm Behavior Models - IfUpDownStatusByType -
Creating Multi-Alarm Behavior Models      IF-IfStatus Alarm

IfUpDownStatusByType

IfUpDownStatusByType is one of the multi-alarm behavior models shipped with NerveCenter and provides interface management for devices that can be managed using the MIB-II and Frame Relay MIBs. This model manages the following types of interfaces:

• Asynchronous Transfer Mode (ATM)
• Integrated Services Digital Network (ISDN)
• Fiber Distributed Data Interface (FDDI)
• Frame Relay Permanent Virtual Circuit (PVC) subinterfaces
• Frame Relay
• Local Area Network (LAN)
• Switched Multimegabit Data Service (SMDS)
• Synchronous Optical Network (SONET)
• Wide Area Network (WAN)

The majority of the alarms in this model are subobject scope alarms that categorize an interface (the possible categories are listed above) and then monitor its status. For most interfaces, the interface can be up, down, or in testing mode. (The exception is a Frame Relay PVC, which can only be up or down.)

When an alarm instance transitions to one of these states, it executes an Inform action to notify OpenView Network Node Manager of the new state. For this Inform action to have the desired effect, you must integrate the trapd.conf.txt file supplied with these models with the standard NerveCenter trapd.conf. The trapd.conf.txt file along with the .mod file resides in the /model/interface_status/updown_bytype directory. For information about importing behavior models into NerveCenter, see Importing Node, Object, and Behavior Model Files on page 362.

The interface status alarms are listed below:

• IF-IfATMStatus
• IF-IfFDDIStatus
• IF-IfFramePVCStatus
• IF-IfFrameRelayStatus
• IF-IfISDNStatus
• IF-IfLANStatus
• IF-IfSMDSStatus
• IF-IfSonetStatus
• IF-IfWANStatus

The model file also includes three other alarms: IF-IfStatus, IF-IfColdWarmStart, and IF-IfNmDemand.