Guest

IP Application Services

Adding Cisco Traps in NetView and HP OpenView

Hierarchical Navigation

Document ID: 13444

Updated: Oct 26, 2005

   Download PDF
   Print

Introduction

This document provides details and examples about how to add and modify traps in Netview and HP OpenView.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on these software versions:

  • HP OpenView 4.1 and later

  • IBM NetView 5.1 and later

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

To Add Cisco Traps

The most recent versions of the popular network management system (NMS) applications load traps in the event management portion when you load the MIBs (refer to MIB Compilers and Loading MIBs). This method is by far the easiest, but you can also load only the traps directly into the NMS if you follow this procedure:

  1. Download the latest Cisco Network Management Integration Data Bundle (NMIDB) from the CiscoView Planner (registered customers only) .

  2. Get the trapd.41x Cisco traps definition file, which resides in the /traps directory of the archive.

    This file contains trap definitions for HP OpenView and IBM NetView.

  3. Merge the trapd.41x file with your existing trapd.conf file.

    In order to do so in HP OpenView, use the xnmevents command. In order to do so in IBM NetView, use the nvaddtrapdconf command. Consult your HP or IBM documentation for more details, as the products can change.

To Add or Modify Traps

In both HP OpenView and IBM NetView, you can add and modify traps with the GUI, which you can access with either of these methods:

  • Type xnmtrap at the command line.

  • From the menu, choose Options > Event customization > Trap customization: SNMP.

Example

This example uses the GUI to add the demandNbrCallInformation trap in CISCO-ISDN-MIB_V1SMI.my.

Bring up the GUI and look for the name of the enterprise in the top area. In this example, the name is cisco-isdn. Next, complete these steps:

  1. If the enterprise is not present, choose Add.

  2. Type the relevant details in the Enterprise Name and Enterprise ID fields.

    In this case, cisco-isdn is the enterprise name and 1.3.6.1.4.1.9.9.26.2 is the enterprise ID.

  3. Click Add when you are done.

  4. Highlight the enterprise in the top area (which is cisco-isdn in this example).

  5. If the name of the trap is not in the bottom area, click Add and complete the fields.

    For this example:

    • Event name is demandNbrCallInformation.

    • The trap is enterprise-specific.

    • The specific trap number is 1.

    • This description is taken from the MIB:

      This trap-inform is sent to the manager whenever a successful call 
clears, or a failed call attempt is determined to have ultimately 
failed. In the event that call retry is active, then this is after 
all retry attempts have failed. However, only one such trap is sent 
in between successful call attempts; subsequent call attempts result 
in no trap.

    • Leave the Event Source field blank.

    • You can configure the Event Category, Status, and Severity fields. (Click Help or look at the HP OpenView or IBM NetView documentation for an explanation of these fields.)

    • You can configure the Event Log Message field, but you can complete this information in this example as:

      Trap received from enterprise $E with $# arguments:
demandNbrLogIf=$1;
demandNbrNAME=$2;
demandNbrAddress=$3;
demandNbrLastDuration=$4;
demandNbrClearReason=$5;
demandNbrClearCode=$6

    • The Popup Notification and Command for Automatic Action fields are optional and are described in the HP OpenView or IBM NetView documentation.

  6. Click Add when you are done.

Related Information

Updated: Oct 26, 2005
Document ID: 13444