Behavior Models Cookbook - Vendor Models - CiscoPacketsDrop -
CiscoMemGetCheck      CiscoPwrSupplyCheck

CiscoPacketsDrop

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

Looks for a significant number of dropped inbound, outbound, or both types of packets on Cisco router interfaces. It checks to see if the problem persists over three polling intervals. Also monitors when both inbound and outbound packets are being dropped during the poll periods.

Two additional alarms, CiscoPacketsDrop_LogToDB and CiscoPacketsDrop_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 packet errors 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:

lifEntry

Trigger Generators

Below is a list of the objects that generate triggers:

• CiscoPktsDropCheck (poll)

Events Sent to OpenView

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

Events Sent to OpenView by CiscoPacketsDrop

For complete information about events sent to OpenView, see the trapd.conf.txt file shipped with these behavior models residing in:

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.

---

• Set counters for persistence
• Poll intervals
• Poll conditions for input and output queue lengths
• 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)