Behavior Models Cookbook - Vendor Models - CiscoCPUUtilization -
Previous: CiscoBufferUtilization     Next: CiscoCRCCheck

CiscoCPUUtilization

Path: /model/vendors/cisco/cisco_cpu_utilization.mod

This behavior model monitors the CPU utilization on Cisco routers. NerveCenter sends a 6001 Inform to the platform only when the utilization reaches a very busy state and remains there for one hour.

Two additional alarms, CiscoCpuUtilization_LogToDB and CiscoCpuUtilization_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 CPU utilization can be produced.

---

Note    The LogToDB alarm, works on Windows NT only.

---

Property

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

lsystem

Trigger Generators

Below is a list of the objects that generate triggers:

• CiscoCpuCheck (poll)
• CiscoCpuUtilization (alarm)
• CiscoCpuUtilization_LogToDB (alarm)
• CiscoCpuUtilization_LogToFile (alarm)

Events Sent to OpenView

The table below summarizes the events this behavior model sends to OpenView:

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.

Optional Customization

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

---

Tip    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.

---

• Set timers for persistence
• Poll intervals
• Poll conditions for CPU utilization thresholds
• 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)