Behavior Models Cookbook
-
Interface Status Models - IfUpDownStatusByType -
Path: /model/interface_status/updown_bytype/ifupdownstatus_bytype.mod
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:
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 interface status alarms are listed below:
The model file also includes three other alarms: IF-IfStatus, IF-IfColdWarmStart, and IF-IfNmDemand.
The following property must be in the property group for the nodes you want to monitor:
frCircuitEntry (IF-IfFramePVCStatus) and ifEntry (all other alarms)
Below is a list of the objects that generate triggers:
Events Sent to OpenView by IfUpDownStatusByType summarizes the events this behavior model sends to OpenView:
Events Sent to OpenView by IfUpDownStatusByType
For more information about integrating NerveCenter with OpenView, or the other NerveCenter-supported network manager platforms, refer to the book Integrating NerveCenter with a Network Management Platform.
Below is a list of behavior model settings that you might want to customize to suit the requirements of your site.
| IfUpDownStatus | Node Status Models |
| 29 July 2003 |