Cisco ONS 15400 Series

Document ID: 5701

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Description of ONS 15454 Traps
Structure of a Trap from ONS 15454
Determine the Severity of a Trap
Action to take in HPoV
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

Cisco recommends using Cisco Transport Manager (CTM) as the Element Management System (EMS) to monitor traps from a Cisco ONS 15454, and recommends Cisco Information Center (CIC) as the Network Management System (NMS) to monitor network wide faults and alarms. Use this document with an existing fault management platform, such as Hewlett-Packard OpenView (HPOV) as the primary interface to view faults.

This document explains how an ONS 15454 sends traps, the contents of a trap, and what action should be taken on a fault management platform, such as HPOV, to decipher the traps. Since there are minor differences in name in the various releases of ONS 15454, this document highlights the differences when applicable.

Prerequisites

Requirements

This document assumes that you have a basic understanding of Simple Network Management Protocol (SNMP) traps, and can interpret the contents in a Management Information Base System (MIBS) defining the trap.

Read this document in conjunction with the ONS 15454 User Documentation.

Components Used

This document is not restricted to specific software and hardware versions.

Conventions

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

Description of ONS 15454 Traps

The ONS 15454 uses SNMP traps as one mechanism to inform its upper level management systems of any alarm condition experienced during its operation. The MIBS for ONS 15454 Software Release 2.2 is defined in these three files:

• cerentRegistry.mib

• cerentTC.mib

• cerent454.mib

The names of these files have been changed since Release 4.6 of the ONS 15454 system software to indicate the name of the MIBS modules. The names of these MIBS files are:

• CERENT-GLOBAL-REGISTRY.mib

• CERENT-TC.mib

• CERENT-454-MIB.mib

• CERENT-GENERIC-MIB.mib (for ONS 15327 only)

• CISCO-SMI.mib

• CISCO-VOA-MIB.mib

• CERENT-MSDWDM-MIB.mib

• CISCO-OPTICAL-MONITOR-MIB.mib

• CERENT-FC-MIB.mib

Note: The CERENT-MSDWDM-MIB.mib and CERENT-FC-MIB.mib in the CiscoV2 directory support 64-bit performance monitoring counters. However, the respective SNMPv1 MIB in the CiscoV1 directory does not contain 64-bit performance monitoring counters, but supports the lower and higher word values of the corresponding 64-bit counter. The other MIB files in the CiscoV1 and CiscoV2 directories are identical in content and differ only in format.

Note: Different MIB files are used for the ONS 15454 (or ONS 15454 SDH) and the ONS 15327, respectively. The file CERENT-454-MIB.mib contains the object and trap definitions pertaining to the ONS 15454 (both SONET and SDH platforms). The file CERENT-GENERIC-MIB.mib contains the object and trap definitions pertaining to the ONS 15327. When provisioning the Network Management System for the ONS 15454 or ONS 15454 SDH, use the file CERENT-454-MIB.mib. When provisioning the Network Management System for the ONS 15327, use the file CERENT-GENERIC-MIB.mib.

A unique feature of SNMP is that a particular version of a MIBS is always compatible with all the earlier versions of the same file. For instance, the CERENT-454-MIB.mib file from the Release 3.0 distribution CD is compatible with software version Release 2.2.3, 2.2.1, 2.0, and so on. This is a mandatory property of every SNMP MIBS, and Cisco Optical Transport Business Unit (OTBU) proprietary MIBS files are no exception.

Structure of a Trap from ONS 15454

The traps of the ONS 15454 are defined in the cerent454.mib file. This is the CERENT-454-MIB.mib file in release 3.0. Traps generated by the ONS 15454 contain an object ID that uniquely identifies the alarm. An entity identifier uniquely identifies which entity generated the alarm (slot, port, Synchronous Transport Signal [STS], Virtual Tributary [VT], Bidirectional Line Switched Rings [BLSR], Spanning-Tree Protocol [STP], and so on). The traps give the severity of the alarm (critical, major, minor, event, and so on), and indicate whether the alarm is service affecting or non-service affecting. The traps also contain a date/time stamp that shows the date and time the alarm occurred. The ONS 15454 also generates a trap for each alarm when the alarm condition clears. Each SNMP trap contains ten variable bindings.

This table shows the structure of an ONS 15454 trap:

The IETF standard documents, known as requests for comments (RFCs), contain MIB object definitions with detailed descriptions. These definitions are extracted from the RFCs and made available as MIB files on the CD. RFCs can be obtained from many sources such as the official IETF website .

These standard MIB files, included on the CD, must be loaded into your network management system. They are located in the Standard directory.

The ONS 15454 supports generic and Internet Engineering Task Force (IETF) traps. The Standard category consists of all the IETF and IANA standard MIB files you need for your operations.

This table lists the traps supported in the ONS 15454:

Determine the Severity of a Trap

The type of trap received cannot alone determine the severity of a trap. You must view the inside contents of the trap to determine the severity of the trap. The alarm/trap severities can be provisioned in the ONS 15454. The Object Identifier (OID) cerent454AlarmState specifies the severity of the alarm and the service affecting status. The possible values for cerent454AlarmState are other (1), crucial (10), administrative (20), diagnostic (30), cleared (40), minorNonServiceAffecting (50), majorNonServiceAffecting (60), criticalNonServiceAffecting (70), minorServiceAffecting (80), majorServiceAffecting (90), criticalServiceAffecting (100). The current implementations for Release 2.2 and Release 3.0 do not have any traps that are of type crucial and diagnostic.

Action to take in HPoV

These steps are written for HP Network Node Manager (NNM) Version 6.1. Consult the user documentation of your version of HP NNM for more information on how to compile an MIB and on changing contents in the trapd.conf file. Use this procedure as a guideline:

1. Compile cerentRegistry.mib, cerentTC.mib, and cerent454.mib in the same order as mentioned here into HPoV.

2. Copy the current trapd.conf as trapd.conf.old. This is an important step. In the event that something missed, you can always revert the file name and return the original setup.

3. In trapd.conf file, replace the string NO FORMAT DEFINED with $N $2 Object:$3 Index:$4 Slot:$5 Port:$6, using any text editor (VI, Emacs, Wordpad, and so on). Ensure this replacement is done only for traps loaded from Cisco OTBU proprietary MIBS files.

4. In trapd.conf file, replace the string LOGONLY with Error Alarms, using any text editor (VI, Emacs, Wordpad, and so on). Ensure this replacement is done only for traps loaded from Cisco OTBU proprietary MIBS files.

5. This makes every trap received from the 15454 appear appropriately on the alarm browser.

6. Save and restart HPoV.

NetPro Discussion Forums - Featured Conversations

Related Information

• Optical Technology Support Page
• Technical Support & Documentation - Cisco Systems