Cisco ONS 15200 Series Metropolitan DWDM Systems

Document ID: 5702

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Description of ONS 15252 Traps
Structure of a Trap from ONS 15252
Determining the Severity of a Trap
      Case 1: clipClientRxPower-Trap Received When a Critical Alarm Occurs
      Case 2: clipClientRx-Power-Trap Received When This Alarm Clears
Action to Be Taken 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 ONS 15252, and recommends Cisco Information Center (CIC) as the Network Management System (NMS) to monitor network-wide faults and alarms. This document has been prepared for a scenario where a customer wnts to use an existing fault management platform, such as Hewlett-Packard OpenView (HPoV) to be used as the primary interface to view faults.

This document is intended to create a better understanding of how ONS 15252 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. This document assumes that the reader has at least a limited understanding of the working of Simple Network Management Protocol (SNMP) traps and an interpretation of the contents in a Management Information Base System (MIBS) defining the trap.

Prerequisites

Requirements

Readers of this document should have knowledge of these topics:

• A basic understanding of how Simple Network Management Protocol (SNMP) traps work

• The ability to interpret of the contents in a Management Information Base System (MIBS) defining the trap

Components Used

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

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.

Description of ONS 15252 Traps

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

• QEY-SMI.my

• QEY-TC.my

• CLIP.my

The procedure for configuring the ONS 15252 to send traps can be found in the SNMP chapter of the Cisco ONS 15200 Command Line Interface. This is a part of the user documentation for ONS 15252.

Structure of a Trap from ONS 15252

These traps of ONS 15252 are defined in the CLIP.my file. Each one of the traps contains the Object Identifier (OID) and the value of the OID of the object defined by the trap. For example, if a clipClientRxPower trap was received, this trap would contain the OID for clipClientRxPower-State and the value for clipClientRxPower-State.

The OID of the CLIP that is the source of a trap is identified by the leaf ID of the trap object that has the source of the trap data. For example, the clipPower trap has an object with the actual state. The OID of the state is clipMIB.clipTable.clipTableEntry.clipPower-State.n. The n is the CLIP ID, and this ID is static, unless the SunNet Manager (SNM) software is rebooted.

Knowing the value of n, if an SNMP GET is done on lipMIB.clipTable.clipTableEntry.clipPosition.n, the actual position of the CLIP in the rack of the ONS 15252 that originated the trap can be determined. Thus, determining the actual position of the CLIP in the rack of ONS 15252 is a two-step procedure. Once the trap is received, look at the index and do a SNMP query of the clipPosition to know the actual position of the CLIP.

clipServiceState-Trap

clipSummaryAlarm-Trap

clipClientRxPower-Trap

clipClientLaserBiasCurrent-Trap

clipDwdmSwitchMode-Trap

clipDwdmActiveOk-Trap

clipDwdmStandbyOk-Trap

clipDwdmInUse-Trap

clipDwdmLOC-Trap

clipDwdmRxPower-Trap

clipDwdmRxPower-sideA-Trap

clipDwdmRxPower-sideB-Trap

clipDwdmLaserTemp-Trap

clipDwdmLaserBiasCurrent-Trap

clipDwdmPeltier-Trap

clipQpp-Trap

clipQppA-Trap

clipQppB-Trap

clipCan-Trap

clipBoardTemp-Trap

clipFlashLog-Trap

clipDAC-Trap

clipPower-Trap

clipDataRate-Trap 

Determining the Severity of a Trap

The type of the 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. A trap is sent whenever the value of an OID, as defined in the trap definition of a trap, changes. For example, a clipClientRxPower-Trap is sent by an ONS 15252, whenever the value of clipClientRxPower-State changes. The syntax of clipClientRxPower-State is of type AlarmSeverity. The definition of AlarmSeverity is defined in the file QEY-TC.my.

Case 1: clipClientRxPower-Trap Received When a Critical Alarm Occurs

During normal operations, the value of clipClientRxPower-State is 1 (normal). When the optical input power from the client falls to an unacceptable value, the value of clipClientRxPower-State may change from 1 to 5 (critical). This change triggers the SNMP agent to send a clipClientRxPower-Trap. This trap would contain the OID clipClientRxPower-State.n, and have the value of 5 for the OID clipClientRxPower-State.n, where n is the index of the CLIP that originated the trap.

Case 2: clipClientRx-Power-Trap Received When This Alarm Clears

From the previous example, you can assume the alarm condition has cleared and the optical input power has returned to normal conditions. In this case, the value of clipClientRxPower-State changes from 5 to 1 (normal), which indicates a normal condition. This change triggers the SNMP agent to send a clipClientRxPower-Trap. This trap would contain the OID clipClientRxPower-State.n and have the new value of 1 for the OID clipClientRxPower-State.n, where n is the index of the CLIP that originated the trap. This condition should be interpreted as the clearing of the previous alarm.

Action to Be Taken in HPoV

Complete these steps:

1. Compile QEY-SMI.my, QEY-TC.my, and CLIP.my files into HPoV.

2. Configure HPoV in its Event Configuration section to display the traps that are defined in the CLIP.my file.

3. Configure HPoV in its Event Configuration section to display the contents of the trap. Thus, the severity of the alarm can be determined by contents of trap displayed in HPoV's Event browser.

NetPro Discussion Forums - Featured Conversations

Related Information

• Optical Devices
• Optical Technologies
• Technical Support & Documentation - Cisco Systems