Behavior Models Cookbook
-
Vendor Models - CiscoMemGetCheck -
Path: /model/vendors/cisco/cisco_mem_get_check.mod
This multi-alarm model monitors the available free memory for Cisco routers.
The CiscoMemGet alarm obtains the memory installed in a Cisco router. The alarm will poll routers every six hours to ensure the memory configuration has not changed. It also listens for warm and cold starts which causes the router to be polled in case memory has been installed or removed.
The CiscoMemCheck alarm checks to see if the problem persists over three polling intervals. The free memory is tested for: low (6-10%), very low (< 6%), and zero-free-memory available conditions. On each state a poll is run, passing the resulting data through a Perl subroutine which uses the total memory installed in the router -- along with the free memory just polled -- to determine the percentage available.
Two additional alarms, CiscoMemCheck_LogToDB and CiscoMemCheck_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 memory utilization can be produced.
The following property must be in the property group for the nodes you want to monitor:
chassis (CiscoMemGet) and lsystem (CiscoMemCheck)
Below is a list of the objects that generate triggers:
Events Sent to OpenView by CiscoMemGetCheck summarizes the events this behavior model sends to OpenView:
Events Sent to OpenView by CiscoMemGetCheck
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.
| CiscoFanCheck | CiscoPacketsDrop |
| 29 July 2003 |