Behavior Models Cookbook
-
Vendor Models - CiscoFanCheck -
Path: /model/vendors/cisco/cisco_fan_check.mod
This behavior model monitors the fan status in a Cisco router. If a trap or a poll shows a problem, the alarm transitions to the FanWarning state which then polls the fan status again for verification. If the problem persists, NerveCenter sends a 6006 Inform to the platform. Once the problem has been corrected, the alarm returns to ground.
Two additional alarms, CiscoFanCheck_LogToDB and CiscoFanCheck_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 fan conditions can be produced.
The following property must be in the property group for the nodes you want to monitor:
Below is a list of the objects that generate triggers:
Events Sent to OpenView by CiscoFanCheck summarizes the events this behavior model sends to OpenView:
Events Sent to OpenView by CiscoFanCheck
| Event Name | Inform Number | Description |
|---|---|---|
For complete information about events sent to OpenView, see the trapd.conf.txt file shipped with these behavior models residing in:
/model/vendors/cisco
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.
| CiscoCRCCheck | CiscoMemGetCheck |
| 29 July 2003 |