Behavior Models Cookbook - Interface Status Models - IfUpDownStatus -
IfLoad      IfUpDownStatusByType

IfUpDownStatus

Path: /model/interface_status/updown/ifupdownstatus.mod

This multi-alarm behavior model determines whether each interface on a managed node is up, down, or testing. If an interface is down, NerveCenter sends a 7002 Inform to the network management platform.

Two additional alarms, IfUpDownStatus_LogToDB and IfUpDownStatus_LogToFile, are part of this model. When you enable these alarms, they perform a Log To Database or a Log to File alarm action, respectively, on each transition so that reports on interface status can be produced.

---

   The LogToDB alarm, works on Windows only.

---

Property

The following property must be in the property group for the nodes you want to monitor:

ifEntry

Trigger Generators

Below is a list of the objects that generate triggers:

• IfStatus (poll)

Events Sent to OpenView

Events Sent to OpenView by IfUpDownStatus summarizes the events this behavior model sends to OpenView:

Events Sent to OpenView by IfUpDownStatus

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.

Optional Customization

Below is a list of behavior model settings that you might want to customize to suit the requirements of your site.

---

   It's a good practice to rename the behavior model objects that you modify. Whenever you import a model, NerveCenter will overwrite objects with the same name.

---

• Change Inform to Inform Platform for Netcool, TME, Unicenter
• Log To File alarm action options
  (file pathname, log action variables, verbose or non-verbose output)
• Log To Database alarm action options
  (log identity number and log action variables)