009-2003-078 alarm and trouble clearing.pdf

7/29/2019 009-2003-078 Alarm and Trouble Clearing.pdf

1/106

CIENA CONFIDENTIAL AND PROPRIETARY

ONLINE7000/9000/11000TRANSPORT PLATFORM

ALARMAND TROUBLECLEARING MANUAL

Software Release 6.0

CIENA Part Number: 009-2003-078

Revision A

April 30, 2003


2/106

CIENA

CONFIDENTIAL AND PROPRIETARY

LEGAL NOTICES

THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF CIENA CORPORATION

AND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS TO REPRODUCE OR DISCLOSE ITS

CONTENTS, OR TO MANUFACTURE, USE, OR SELL ANYTHING THAT IT MAY DESCRIBE. REPRODUCTION,

DISCLOSURE, OR USE IN WHOLE OR IN PART WITHOUT THE SPECIFIC WRITTEN AUTHORIZATION OF CIENA

CORPORATION IS STRICTLY FORBIDDEN.

EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS DOCUMENT IS COMPLETE

AND ACCURATE AT THE TIME OF PRINTING; HOWEVER, THE INFORMATION CONTAINED IN THIS DOCUMENT

IS SUBJECT TO CHANGE.

Copyright 2003 CIENA Corporation

Unpublished All Rights Reserved

The material contained in this document is also protected by copyright laws of the United States of America and other

countries. It may not be reproduced or distributed in any form by any means, altered in any fashion, or stored in a data

base or retrieval system, without express written permission of the CIENA Corporation.

Required Customer InformationPart 15 of the Federal Communications Commission (FCC): Interference

CIENA NOTE: Every effort has been made to ensure that this equipment is designed to comply with the limits for a

Class A digital device, as described in the FCC Rules. Equipment limitations are designed to provide reasonable

protection against harmful interference when the equipment is operated in a commercial environment. This equipment,

if not installed and used properly, and in accordance with guidelines established by CIENA Corporation may cause

interference with other communications equipment. Operation of this equipment in a residential environment may

cause interference and is the responsibility of the user to correct the interference at his own expense.

Security

CIENA cannot be responsible for unauthorized use of equipment and will not make allowance or credit for

unauthorized use or access.

Contacting CIENA

Corporate Headquarters 410-694-5700 www.ciena.com

Customer Technical Support/Warranty

In North America 1-800-CIENA24 (243-6224) E-mail: [email protected]

In Europe00800 843 52 322

or +44 181 843 52 322E-mail: [email protected]

In Asia 0120-884-766

Sales and General Information 410-694-5700 E-mail: [email protected]

In North America 410-694-5700 E-mail: [email protected]

In Europe 44 207 389 7100 E-mail: [email protected]

In Asia +81-3-3248-4680 E-mail: [email protected]

Training and Documentation

Training877-CIENA-TD (243-6283)

or 410-694-8120E-mail: [email protected]

Documentation877-CIENA-TD (243-6283)

or 410-694-8125E-mail: [email protected]


3/106

ONLINETM7000/9000/11000 PREFACE

Alarm and Trouble Clearing Manual

April 30, 2003 - Revision A

009-2003-078 i


PREFACE

The ONLINE 7000/9000/11000 Transport PlatformAlarm and Trouble Clearing Manual describes the

ONLINE alarm tools that are available from the various ONLINE control applicationsat the graphical craft

interface terminal (GCIT), command line interface (CLI), Transaction Language 1 (TL1) messages, and

SNMP. This manual is also a resource that explains the basic ONLINE system fault management principles,

describes each ONLINE system alarm, and identifies the actions needed to correct the alarm condition.

This preface defines the purpose, readership, and organization of the ONLINE Alarm and Trouble Clearing

Manual in the following sections:

! Objectives

! Audience

! Content Organization

! Related Documentation

! Contacting CIENA System Technical Field Return Information

! Lab Evaluation and Field Trials

OBJECTIVES

This manual provides overviews of the alarm tools available from all of the ONLINE software application

platforms. You can use this manual as a quick resource to decipher the meanings of alarms, and to locate

recommended actions to take in response to alarms. This manual supplements the information found in

other ONLINE manuals, as listed in the Related Documentationsection of this preface.

AUDIENCE

This manual is intended for network technicians who perform routine maintenance and deal with alarm

conditions that arise after the network element (NE) has been installed successfully according to the

ONLINE Install, Turn-Up, & Test Manualand has been in operation for some time.

DISCLAIMER

Portions of this document are intended solely as an outline of methodologies to be followed during the

maintenance and upgrade of an ONLINE Transport Platform. It is not intended as a step-by-step guide or

a complete set of all procedures necessary and sufficient to complete an upgrade.

While every effort has been made to ensure that this document is complete and accurate at the time of

printing, the information that it contains is subject to change. CIENA is not responsible for any additions to

or alterations of the original document. Networks vary widely in their configurations, topologies, and traffic

conditions. This document is intended as a general guide only. It has not been tested for all possible

applications, and it may not be complete or accurate for some situations.

Users of this document are urged to heed warnings interspersed throughout the document, such as traffic

disruption warnings.


4/106

PREFACE ONLINETM7000/9000/11000



ii 009-2003-078


CONTENT ORGANIZATION

This manual contains the following sections:

! CHAPTER 1, FAULT MANAGEMENT

! CHAPTER 2, USER ALARMS

! CHAPTER 3, ALARM CLEARING PROCEDURES

! APPENDIX A, ALARM MESSAGE LIST

RELATED DOCUMENTATION

This manual assumes that the reader is already familiar with the following ONLINE manuals:

! ONLINE Install, Turn-Up, & Test Manual: Includes instructions for installing and turning up an

NE. If your NE has not yet been successfully installed, or has not operated successfully, refer

to these guides.

! Circuit Pack Reference Guide: Contains specific information about each circuit pack (CP) in

the NE, including block diagrams and part numbers.

! OPTX Management Suite Graphical CIT User Guide: Provides the information to provision anode and perform any required maintenance and troubleshooting tasks.

! ONLINE CLI Reference: Provides details for all currently supported ONLINE system CLI

instructions and responses.

! ONLINE TL1 Reference: Provides details for all currently supported ONLINE system

Transaction Language 1 (TL1) instructions and messages.

! ONLINE SNMP Reference: Provides details about all SNMP MIBs and the SNMP master

agent.

COMPLIANCE INFORMATION

Food and Drug Administration (FDA) Laser Safety Warning

This product contains a laser diode. CIENA Corporation strongly recommends that users, maintenance, and

service personnel comply with the following standards and regulations in the design, modification,

operation, maintenance, an service of lasers and fiber-optic devices:

It is further recommended that the owner of this equipment determine and ensure conformance with any

specific and applicable local regulations.

Jurisdiction Type Title

Federal, US Regulation FDA 21 CFR 1040.10/.11

Federal, US Guidelines OSHA

International Standard ANSI Z136 series

International Standard IEC-825 series

International Standard EN-60825


5/106




009-2003-078 iii


Class I Laser Product Notice

The CIENA Corporation ONLINE Metro Transport Platform product is a Class 1 Laser product as

identified by US FDA/CDRH 21CFR1040.10/.11; Class 1 Laser product as defined by IEC825/EN-60825;

and OFCS SG1 as defined by ANSI Z136.1/.2/

Part 15 of the Federal Communications Commission (FCC): Interference

Every effort has been made to ensure that this equipment is designed to comply with the limits for a Class

A digital device, as described in the FCC Rules. Equipment limitations are designed to provide reasonable

protection against harmful interference when the equipment is operated in a commercial environment. This

equipment, if not installed and used properly, and in accordance with guidelines established by CIENA

Corporation may cause interference with other communications equipment. Operations of this equipment in

a residential environment may cause interference and is the responsibility of the user to correct the

interference at the users own expense.

Environmental Impact Statement

CIENA equipment contains no hazardous materials as defined by the United States Environmental

Protection Agency (USEPA). CIENA

recommends that all failed product be returned to CIENA

for failureanalysis and proper disposal.

Toxic Emissions

CIENA equipment releases no toxic emissions.

Telcordia Document Standards

The format and structure of this document is derived from the Telcordia Generic Requirements for Supplier-

Provided Documentation, GR-454-CORE.

TRADEMARK ACKNOWLEDGEMENTS

! CIENA is a registered trademark of CIENA Corporation.

! ONLINE7000/9000/11000 Transport Platform is a trademark of CIENA Corporation.

! Windows 95/98/2000 and Windows NT are registered trademarks of the Microsoft

Corporation.

! UNIX is a registered trademark licensed exclusively through X/Open Company, Ltd.

! Pentium is a registered trademark of Intel Corporation.

! Sun, Sun Microsystems, JAVA, Java Secure Socket Extension, Solaris, and JAVAX are

trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. or other countries.

This product includes code licensed from RSA Data Security.

RELEASE NOTES AND DOCUMENT UPDATES

The hard copy and Compact Disc Read Only Memory (CD-ROM) versions of this document are revised only

at major releases and, therefore, may not always contain the latest product information. As needed,

Software Release Documents (SRDs), Hardware Release Documents (HRDs), Application Notes, Field

Service Bulletins (FSBs), and/or Document Maintenance Bulletins (DMBs) are provided between major

releases to describe any new information or document changes.


6/106

THIS PAGE INTENTIONALLY LEFT BLANK




iv 009-2003-078


CONTACTING CIENASYSTEM TECHNICAL FIELD RETURN

INFORMATION

NOTE: CIENAretains the sole right to determine if a problem is an emergency or a non-emergency.

Validate Requirements with Customer Support: Customer needs to contact CIENA Worldwide

Customer Services and Support to ensure that a replacement product is in fact required. CIENA

encourages all Customers to work with its technicians for a reasonable period to determine whether a

solution or workaround exists that does not require immediate component replacement. CIENA will not

accept any returns for warranty replacement without prior approval and adequate proof of purchase.

Warranty Replacement: Customer must furnish a receipt, purchase order, or other standard sales

document, or have the specific component serial number on file with CIENA Worldwide Customer Services

and Support to determine if a product is under warranty.

Warranty Claims: In the event of any warranty claim, Customer must

(a) Request a Return Material Authorization (RMA) number from CIENA by calling the appropriate

number listed above and (a) Comply with the terms and procedures described in the governing Purchase

and License Agreement(s).

Corporate Headquarters 410-694-5700 www.ciena.com

Customer Technical Support/

Warranty

In North America 1-800-CIENA24 (243-

6224)

E-mail:

[email protected]

In Europe 00800 843 52 322

or +44 181 843 52 322

E-mail: [email protected]

In Asia 0120-884-766

Sales and General Information 410-694-5700 E-mail: [email protected]

In North America 410-694-5700 E-mail: [email protected]

In Europe 44 207 389 7100 E-mail: [email protected]

In Asia +81-3-3248-4680 E-mail: [email protected]

Training and Documentation

Training 877-CIENA-TD (243-6283)

or 410-694-8120


Documentation 877-CIENA-TD (243-6283)

or 410-694-8125



7/106




009-2003-078 v


Returning CIENA Product: Customer will receive an RMA number after contacting an

CIENA Worldwide Customer Services and Support representative.

To Prepare Product for Return to CIENACorporation

STEP 1: Package the product, using the original container, and return it to CIENA Corporation.

STEP 2: Write the RMA number on the outside of the box where it can be easily identified, and includeany additional information useful in determining the root cause of the failure.

STEP 3: Always remember to include Customers name and return address, with a completed returnaddress label always appreciated.

STEP 4: Ensure that the product you are shipping complies with all applicable Export Laws for and withinthe country you are shipping from and to. By shipping the product the customer agrees tocomply with all such laws and regulations.

STEP 5: Ship the product using a reputable and insured carrier.

LAB EVALUATION AND FIELD TRIALS

In accordance with trial-agreement escalation procedures, any problem encountered during laboratory

evaluations and field trials should be referred to the CIENA Corporation field trial coordinator.


8/106





vi 009-2003-078



9/106

ONLINETM7000/9000/11000 TABLE OF CONTENTS

TOC



009-2003-078 vii


TABLE OF CONTENTS

PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i

LIST OF FIGURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

LIST OF TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvii

CHAPTER 1 FAULT MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Common Alarm Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Alarm Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Alarm Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Alarm Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Alarm Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Alarm Audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Alarm Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

CIT Alarm Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

CLI Alarm Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7

TL1 Alarm Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8

To view alarm severities using TL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

To View All Alarms Using TL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

Autonomous Alarm Messages in TL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

To view user alarms using TL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9

CHAPTER 2 USER ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

User Alarms Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

User Alarm Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

User Alarm Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2

CHAPTER 3 ALARM CLEARING PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

AIS (Alarm Indication Signal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Alarm Card Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

BER Test Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Card Provisioning Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

Communications Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2

Configuration Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

Cooling Fan Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3


10/106

TABLE OF CONTENTS ONLINETM7000/9000/11000

TOC



viii 009-2003-078


DCC Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4

Diagnostics Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4

Diagnostics Failure Component Mgr_Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4

Diagnostics Failure FPGA Program Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5

Diagnostics Failure Slot Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5

Drive Mount Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5

Duplicate SIDs in Subnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5

East Audit Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5

East Default K Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6

East ENUT Table Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6

East Improper APS Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6

East Inconsistent APS Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6East Interface Side Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6

East Node ID Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

East Protection Switch Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

East Ring Map Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

East Ring Map ID Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

East Squelch Table Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

EEPROM Data Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8

EEPROM Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8

Ethernet Link A Failure Ethernet Link B Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8

Ethernet Switch Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8

Ethernet Switch Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9

Excessive Data Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9

Excessive Input Power (Preamplifiers, Postamplifiers, PMM, or OLM) Excessive

Input Power Line (WCI CP) Excessive Input Power Trib (WCI CP) . . . . . . . . . . . . . . . . . .3-9

For Excessive Input Power Trib: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9

For Excessive Input Power Line: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10

For Excessive Input Power (Pre-amp, Post-amp, VGA): . . . . . . . . . . . . . . . . . . . . . . .3-10

External Reference Failed SYNC (A/B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

External Reference Locked Out (SYNC A) External Reference Locked Out (SYNC B) . . .3-11

Fast Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11


11/106


TOC



009-2003-078 ix


FPGA Failure, Line FPGA Failure, Trib FPGA Power Failure, Line

FPGA Power Failure, Trib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11

Forced Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12

Forced Switch On Line Port Forced Switch On Trib Port . . . . . . . . . . . . . . . . . . . . . . . . . .3-12

Forced Sync Switch Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12

Free Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12

High Order Path AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12

High Order Path Remote Failure Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

High Order Path Trace Identifier Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13

High Order Path Unequipped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13

High Peak Voltage Violation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13

High Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14

Holdover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14

HUB OSC Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14

Invalid Data Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15

Laser Bias Current Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15

Laser Bias Current Failure, Line Laser Bias Current Failure, Trib . . . . . . . . . . . . . . . . . . . .3-15

Laser Wavelength Lock Failure, Line Laser Wavelength Lock Failure, Trib . . . . . . . . . . . .3-16

Line AIS (ADM, ESCON Mux, or STMX CP), 10GSMX Line AIS Line (WCI CP)

Line AIS Trib (WCI CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16

Line Remote Failure Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16

Lockout of Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17

Lockout of Protection On Line Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17

Lockout of Protection On Trib Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17

Lockout of Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17

Lockout of Working On Line Port Lockout of Working On Trib Port . . . . . . . . . . . . . . . . . .3-17

Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18

Loss of Clock (ADM, or STMX CP) Loss of Clock Line (WCI CP)

Loss of Clock Trib (WCI CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18

Loss of Frame (ADM, ESCON Mux, GRDM, or STMX CP), 10GSMXLoss of Frame Line (WCI CP) Loss of Frame Trib (WCI CP) . . . . . . . . . . . . . . . . . . . . . . .3-18

Loss of Pointer (ADM, ESCON MUX, Data MUX, STMX) . . . . . . . . . . . . . . . . . . . . . . . . . .3-19

Loss of Signal (ADM I & II, ESCON MUX I & II, GRDM I & II, STMX, 10G SMX) . . . . . . . .3-19

Loss of Signal (OSC/OSH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19

Loss of Signal on Line Port (WCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20


12/106


TOC



x 009-2003-078


Loss of Signal on Trib Port (WCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20

Loss of Signal (Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

Loss of Signal Mux (CWDM-U) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

Loss of Signal Demux (CWDM-U) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22

Loss of Signal OLM Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22

Loss of Signal OSM Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22

Loss of Signal OLM Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23

Loss of SIgnal OSM Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23

Loss of Signal PMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23

Loss of Signal Preamp (Preamp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-24

Loss of Signal Postamp (Postamp) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-24

Loss of Signal PreVGA (VGA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25Loss of Signal PostVGA (VGA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25

Loss of Signal (SYNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-26

Loss of Signal WPS - (WPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-26

Loss Values Out of Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

Low Peak Voltage Violation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-27

Low System Resource Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-27

Low System Resource Handle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-27

Low System Resource Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-27

Manual Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

Manual Switch On Line Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

Manual Switch On Trib Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

Memory Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

PSM Database is Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

Multiplex Section AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

Multiplex Section Remote Failure Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29

Node in Hitless State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29

Node in Partially Turned Up State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29Node in Selective Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29

NVRAM Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30

OCH AIS On Line Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30

ODPR Protection Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30

OOS Diagnostics Performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30


13/106


TOC



009-2003-078 xi


Optical Switch Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31

OSC4080 Device Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31

OSPR Protection Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31

Out of Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-32

Path AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-32

Path Remote Failure Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33

Path Trace Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33

Path Unequipped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

Payload Mapping Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33

Peer Communications Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-34

PMA Is Locked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-34

Power ACO Card Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-35Power Entry Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-35

Power Management Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-35

Power Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-36

Processor Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-36

Program Memory Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-37

Program Memory Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-37

Protection Path Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-37

Provisioning Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-38

Receiver Failure Line Receiver Failure Trib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-38

Reference Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-38

Reference Locked Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39

Reference Out of Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39

Regenerator Section Trace Identifier Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39

Replaceable Unit Missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39

Replaceable Unit Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40

Replaceable Unit Type Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-40

Section Trace Mismatch Section Trace Mismatch Line Section Trace Mismatch Trib . . . .3-40Shelf ID Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-41

Shelf Interconnect Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-41

Shelf Type Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-41

Signal Degrade BER (ADM, OSC, or STMX CP), 10GSMX

Signal Degrade BER Line (WCI CP) Signal Degrade BER Trib (WCI CP) . . . . . . . . . . . . .3-42


14/106


TOC



xii 009-2003-078


Signal Fail BER (ADM, OSC, or STMX CP), 10GSMX

Signal Fail BER Line (WCI CP) Signal Fail BER Trib (WCI CP) . . . . . . . . . . . . . . . . . . . . .3-42

Signal Frequency Invalid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-42

Signal Squelched Line Signal Squelched Trib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42Signaling Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-43

Software Download Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-43

Software Environment Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-43

Wrong software loads on the current drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-43

Wrong software loads on the alternate drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

Activated on the wrong drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-44

Manual cold reboot required to upgrade FPGA version to most recent . . . . . . . . . . . .3-44

Load repository corrupt on current drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-44

Load repository corrupt on alternate drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-44

Unable to set software version in EEPROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-44

Wrong software loads on the alternate flash region . . . . . . . . . . . . . . . . . . . . . . . . . . .3-44

Synchronization Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-45

Temperature Sensor Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-45

Temperature Out Of Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46

Threshold Crossed LBC Line Threshold Crossed LBC Trib . . . . . . . . . . . . . . . . . . . . . . . .3-46

Threshold Crossed OPR (Extended OSC, Preamp, Postamp)

Threshold Crossed OPR Line, OPR Trib (WCI CP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-46

Threshold NM Crossed Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-47

Topology Discovering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-48

Topology Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-48

Trail Trace Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-50

Transmit Fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-50

Transmitter Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-50

Transmitter Failure Post VGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-51

Transmitter Failure Pre VGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-51

Transmitter Failure Trib Transmitter Failure Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-51

Trib Optical Monitoring Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-51

Underlying Resource Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-52

User Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52

VOA Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-52

VOA Motor Missing Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-52


15/106


TOC



009-2003-078 xiii


VOA Motor Not Stepping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-52

VOA POT Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-53

Wavelength Management Unavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-53

West Audit Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-54

West Default K Byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-54

West ENUT Table Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-54

West Improper APS Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-55

West Inconsistent APS Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-55

West Interface Side Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-55

West Node ID Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-55

West Protection Switch Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-55

West Ring Map Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-56West Ring Map ID Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-56

West Squelch Table Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-56

APPENDIX A ALARM MESSAGE LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .I-1


16/106



TOC



xiv 009-2003-078



17/106

ONLINETM7000/9000/11000 LIST OF FIGURES

LOF

FIGURE # FIGURE NAME PAGE #



009-2003-078 xv


LIST OF FIGURES

Figure 1-1. Viewing Alarm Type Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Figure 2-1. User Alarms Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Figure 2-2. Enable/Disable User Alarm Outputs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . 2-3


18/106


LIST OF FIGURES ONLINETM7000/9000/11000

LOF



xvi 009-2003-078



19/106

ONLINETM7000/9000/11000 LIST OF TABLES

LOT

TABLE # TABLE NAME PAGE #



009-2003-078 xvii


LIST OF TABLES

Table 1-1. Interpreting Alarm Detail Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Table 1-2. Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Table 1-3. CIT Alarm Information Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Table 3-1. Corrective Actions for the OSPR Protection Unavailable Alarm . . . . . . . . . . . 3-32

Table 3-2. Corrective actions for Wavelength Management Unavailable alarm . . . . . . . . 3-53

Table A-1. List of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1


20/106


LIST OF TABLES ONLINETM7000/9000/11000

LOT



xviii 009-2003-078



21/106

ONLINETM7000/9000/11000 FAULT MANAGEMENT

1



009-2003-078 1 - 1


CHAPTER 1

FAULT MANAGEMENT

This chapter includes procedures and guidelines for using the various ONLINE 7000/9000/11000

Transport Platform command tools to prioritize alarm indications, filter alarms, and determine the cause(s)

of alarm(s) in the following sections:! Common Alarm Sources on page 1-1

! Alarm Characteristics on page 1-1

! Alarm Tools on page 1-4

COMMON ALARM SOURCES

Alarms typically occur as a result of the following conditions:

! Fiber breaks

! Equipment failure

! Software failure

! Operator error

When isolating the source of an alarm, start by examining if the cause of the alarm may be due to one of

the common errors prior to escalating your troubleshooting efforts. You can use the descriptions provided

in the alarm logs and reports to assist in isolating the source of alarms.

ALARM CHARACTERISTICS

This section explains the ONLINE system alarm components in the following sections:

! Alarm Conditions on page 1-1

! Alarm Detail on page 1-2

! Alarm Severity on page 1-3

ALARM CONDITIONS

Each alarm is categorized in a displayat the graphical craft interface terminal (CIT), command line

interface (CLI), Transaction Language 1 (TL1), or SNMP interfacesin accordance with the equipment

source from which the alarm is triggered. Although the fundamental range of alarm types is identical

regardless of the display platform, the manner in which the alarm types are identified differs in accordance

with the application you are using.

The CIT presents graphical alarm indicators, which are displayed for all equipment objects, in both the

hierarchical tree pane and the graphical pane. You can access information about a selected topology

object by using the View -> Alarms and Failures menu from the CIT main menu bar, to display an Alarm

and Failure List (Figure 1-1), in which to view the alarm type associated with the selected network object.

The illustration also demonstrates a typical display of the alarm type in a CLI message.


22/106

FAULT MANAGEMENT ONLINETM7000/9000/11000

1



1 - 2 009-2003-078


Figure 1-1. Viewing Alarm Type Information

ALARM DETAIL

At the CIT Alarm and Failure List window, you can view a wide range of information about specified

alarms in a graphical presentation. The same information is also available in the CLI and TL1 formats.

Table 1-1. Interpreting Alarm Detail Messages

Alarm Detail Description

New A black circle indicates a new alarm. If a new alarm is selected, the black

changes to white.

Affected Object The alarm location; for example "node57: Facilities: Trib: 3-2-E"

Time Day, date, and time the alarm was raised by the network element (NE). Time

stamp will be in GMT.

Severity Critical, major, minor, warning, or indeterminate

Probable Cause Most likely cause of the alarm, for example, "Loss of Signal."

Acknowledged If a checkbox in this column is filled in, the alarm has been acknowledged.

Operator The user ID of the operator who acknowledged the alarm.

CIT Alarm Type View

CLI Alarm Type View


23/106


1



009-2003-078 1 - 3


ALARM SEVERITY

Alarms are typically corrected in accordance with severity, type, and probable cause.

Alarms have the following severities:

! Critical (reported as CR in CLI, and *C in TL1)

!

Major (reported as MJ in CLI, and ** in TL1)! Minor (reported as MN in CLI, and *^ in TL1)

! Warning (reported as WN in CLI)

! Indeterminate

The alarm severity meanings are as described in Table 1-2.

The CIT provides color indicators throughout the interface to keep you apprised of current alarm conditions.

When enabled, the colors of the topology objects indicate the following conditions:

Type Equipment alarm, Processing error alarm, Environmental alarm, or

Communications alarm.

Notes Operator-entered supplemental information (usually, why an alarm was

acknowledged).

Additional Text Descriptive text, if any.

Table 1-2. Alarm Severities

Alarm Severity Definition

Critical Critical alarms indicate that a severe, service-affecting condition has occurred andthat immediate corrective action is imperative, regardless of the time of day or day

of the week.

Major Major alarms indicate hardware or software conditions causing a serious disruption

of service or the malfunctioning or failure of important circuits. These troubles

require the immediate attention and response of a craftsperson to restore or

maintain system capability. The urgency is less than in critical situations because

of a lesser immediate or impending effect on service or system performance.

Minor Minor alarms are used for troubles that do not have a serious effect on service to

customers or for troubles in circuits that are not essential to NE operation. For

example, a carrier line problem where transmission was switched to a protection

line is a minor alarm because it is non-service affecting.

Warning Warnings are alarm conditions that do not affect the functioning of the NE.

Indeterminate An indeterminate alarm indicates a problem of unknown severity (possibly a

multiple failure case) has been detected.

Table 1-1. Interpreting Alarm Detail Messages (Continued)

Alarm Detail Description


24/106


1



1 - 4 009-2003-078


! GREEN = normal

! RED = critical alarm

! ORANGE = major alarm

! YELLOW = minor, warning, or indeterminate alarm

Alarm Audio

Alarm audio (also known as alarm enunciation), can be configured at the CIT to provide a sound indicator

as alarms are detected at the ONLINE NE. For more information, refer to To Use the Audible and Visible

alarm alert Tool at the CIT on page 1-6, and the OPTX Management Suite Graphical CIT User Guide

(OPN 310).

ALARM TOOLS

The alarm LEDs on the NE shelves and circuit packs (CPs) provide a first glance indication about

problems on the ONLINE system. To further examine details about the alarms, you can use the ONLINE

command interfaces to gather information to assist in identifying the source of the alarm situation.

This section describes the ONLINE system command applications that provide various methods for viewing,

modifying, and filtering alarms, in the following sections:

! CIT Alarm Tools on page 1-4

! CLI Alarm Tools on page 1-7

! TL1 Alarm Tools on page 1-8

NOTE: Do not begin removing CPs or connections until you have examined the alarm detail atthe CIT, or other ONLINE interface.

CIT Alarm ToolsThe CIT provides a graphical user interface (GUI) with which to view, delete, and monitor both ONLINE

system alarms and user alarms. System alarms are associated with various severities of malfunctioning

equipment, service, transmission paths, or software. User alarms are associated with possibly

unacceptable conditions that arise in the site environment in which the system is located.

NOTE: The description in this section does not contain screen captures of the CIT GUI alarmmanagement tools. To see the GUI components, please refer to the OPTX Graphical CITUser Guide (OPN 310)

The CIT GUI tools that are used for troubleshooting faults within the ONLINE network are accessed fromthe alarm menus (either from the CIT main menu bar or as popup menus derived from selected network

topology objects). The alarm menus provide options to generate alarm reports, acknowledge and

unacknowledge alarms, delete alarm(s), and view alarm details.


25/106


1



009-2003-078 1 - 5


TOVIEWALLALARMSATTHE CIT

Use the Fault-View Alarms and Failures menu to present the Subnetwork Alarm and Failure List

window. The information in this window describes alarm associations to NEs, time, severity, causes, and

actions performed in response to the alarm indications (Table 1-3).

TOVIEWSEVERITY-SPECIFICALARMSATTHE CITThe columns and column entries in the Alarm and Failure List window can be sorted to customize the

arrangement of the columns. You can use the single-sorting mechanism to organize alarms by criticality (as

well as by other criteria). You can also show, hide, and reorder the alarm columns to customize the view in

accordance with your filtering preferences.

To find out how to use the Select Sort Columns and Column Options menu at the CIT, see the OPTX

Graphical CIT User Guide (OPN 310).

Table 1-3. CIT Alarm Information Categories

Column Label Description

Affected Identifier of the ONLINE NE affected by the alarm.

Time Hour, minute, and second of the alarm occurrence.

Severity Level of severity as either critical (red), major (orange),

minor (yellow), warning (yellow), or indeterminate

(yellow).

Probable Cause Condition detected by the ONLINE system that

triggered the alarm.

Acknowledge Checkbox that indicates whether or not the alarm has

been acknowledged. If checked, the alarm has been

acknowledged. If not checked, the alarm has not been

acknowledged.

Operator User ID of the operator who acknowledged the alarm.

Type Alarm type, as either equipment, processing error,

environmental, or communications.

Notes Supplemental information provided by the operator,

which may include information about why the alarm

was acknowledged, or contain plan detail for rectifying

the alarm condition.

Addition Additional text area in which to provide information

about the alarm.

Cleared Checkbox that indicates that the alarm has been fixed

and/or is no longer considered an alarm condition.

When checked, the alarm is cleared. When not

checked, the alarm is not yet cleared. Cleared alarms

are not removed from the alarm list until deleted.


26/106


1



1 - 6 009-2003-078


TODELETEALARMSATTHE CIT

At the CIT, use the tools provided in the Alarm Retirement Setup dialog box, or the Fault-Delete Cleared

Alarms menu, or the Alarm and Failure Report view to remove specified alarms.

! The Alarm Retirement Setup dialog box allows you to instruct the ONLINE system to

automatically delete alarms that are cleared and acknowledged.

! Using the Fault-Delete menu enables you to select and confirm removal of specified alarms.

! Right-clicking on a selected row in the Alarm and Failure Report view presents a popup

menu from which you can delete selected alarms.

To view the CIT GUI elements associated with these tasks, please refer to the OPTX Graphical CIT User

Guide (OPN 310).

TOVIEWTHEALARMHISTORYLOGATTHE CIT

Use the alarm report functions in the CIT to view alarm history logs. The various report types are accessed

by clicking anywhere on the heading row of the Subnetwork Alarm and Failure List, or by using the Fault

menu from the CIT main menu. Alarm reports are categorized as follows:

! Custom Alarm Report (HTML)

Use the Custom Alarm Report (HTML) option if you want to view filtered and/or sorted alarm detail in a

web browser window. The view presented in this custom report is based on your customization of the

alarm list details (as described in To view severity-specific alarms at the CIT on page 1-5).

! Custom Alarm Report (CSV)

Use the Custom Alarm Report (CSV) option if you want to write the filtered and/or sorted alarm report

as an Excel file to a specified location.

! Complete Alarm Report (HTML)

Use the Complete Alarm Report (HTML) option if you want to view all, unfiltered alarm detail in a web

browser window. The view presented in this custom report is based on your customization of the alarm

list details.

! Complete Alarm Report (CSV)Use the Complete Alarm Report (CSV) option if you want to write all alarm detail reported to the CIT as

an Excel file to a specified location.

TO USETHE AUDIBLEAND VISIBLEALARMALERT TOOLATTHE CIT

At the CIT, present the Audible and Visible Alerts dialog box; available from Fault-Alerts option from the

CIT main menu. This dialog box enables activation and deactivation of the audible and visible alerts at the

local workstation. You can filter the alerts by specifying the severity level to be associated with the alerts,

and whether or not you want to view alerts only, hear sound only, or use both alert mechanisms.

Activating visible result in display of a message box that contains information associated with the alarm.

To view the CIT GUI elements associated with these tasks, please refer to the OPTX Graphical CIT User

Guide (OPN 310).


27/106


1



009-2003-078 1 - 7


CLI Alarm Tools

The CLI commands that are used for troubleshooting faults within the ONLINE network are show alarm

and show log.

NOTE: The CLI also includes the unlock alarm command, which is used only to take the alarmcard out of the administrative service state.

TOVIEWALLALARMSUSINGTHE CLI

Use the show alarm command to view active alarms on the NE. This command is resource level sensitive;

meaning the alarm information displayed is limited in scope to the level set by the resource command.

Example: View unfiltered list of all current alarms

MyNode> show alarm

Alarms for node: MyNode

Identifier Status Type Date Time-UTC Probable Cause

----------------------------------------------------------------------

OT-E WN comm 08/09/00 17:47:36 thresholdCrossedOPR

OT-W WN comm 08/09/00 17:47:13 thresholdCrossedOPR

OCH-6-1-W CR comm 08/09/00 17:48:33 lossOfFrameTrib

OCH-6-1-W CR comm 08/09/00 17:49:24 lossOfFrameLine

OCH-6-1-W WN comm 08/09/00 17:47:05 thresholdCrossedOPRLine

OCH-8-3-W WN comm 08/09/00 17:47:21 thresholdCrossedOPRTrib

OCH-3-2-E CR comm 08/09/00 17:48:45 lossOfFrameLine

OCH-3-2-E CR comm 08/09/00 17:48:45 aISTrib

TOVIEWSEVERITY-SPECIFICALARMSUSINGTHE CLI

Example: An instruction to the NE to issue a list of all critical alarms.

MyNode> show alarm critical

Alarms for node: MyNode

Identifier Status Type Date Time-UTC Probable Cause

-------------------------------------------------------------------

OCH-6-1-W CR comm 08/09/00 17:48:33 lossOfFrameTrib

OCH-6-1-W CR comm 08/09/00 17:49:24 lossOfFrameLine

OCH-3-2-E CR comm 08/09/00 17:48:45 lossOfFrameLine

OCH-3-2-E CR comm 08/09/00 17:48:45 aISTrib

MyNode>


28/106


1



1 - 8 009-2003-078


TOVIEWTHEALARMHISTORYLOGUSINGTHE CLI

Use the show log command to view alarm log entries for a specified NE. This command is resource level

sensitive; meaning the alarm information displayed is limited in scope to the level set by the resource

command.

Example: Viewing an alarm log filtered to show alarm severity as well as time period.

MyNode> show log critical 2000/8/9/17/45 2000/8/9/17/50

Alarm Log for node: MyNode

No. Date Time-UTC Identifier Status Type Probable Cause

----------------------------------------------------------------------

1 08/09/00 17:46:11 rtp_node2 CR proccess powerManagementProblem

2 08/09/00 17:47:33 OCH-8-3-W CR comm lossOfSignalLine

3 08/09/00 17:47:32 OCH-3-2-E CR comm lossOfSignalLine

4 08/09/00 17:47:32 OCH-3-2-E CR comm lossOfSignalTrib

5 08/09/00 17:48:28 rtp_node2 CR proccess powerManagementProblem

6 08/09/00 17:48:37 OT-E CR comm lossOfSignalPostamp

7 08/09/00 17:48:42 OCH-3-2-E CR comm lossOfFrameTrib

8 08/09/00 17:48:41 OCH-8-3-W CR comm lossOfFrameLine

9 08/09/00 17:47:04 OCH-6-1-W CR comm lossOfSignalTrib10 08/09/00 17:47:04 OCH-6-1-W CR comm lossOfSignalLine

11 08/09/00 17:48:33 OCH-6-1-W CR comm lossOfFrameTrib

12 08/09/00 17:48:38 OCH-8-3-W CR comm lossOfFrameTrib



15 08/09/00 17:48:45 OCH-3-2-E CR comm lossOfFrameLine

16 08/09/00 17:48:45 OCH-3-2-E CR comm aISTrib

17 08/09/00 17:49:11 OCH-6-1-W CR comm signalFailBER

18 08/09/00 17:47:20 OCH-8-3-W CR comm lossOfSignalTrib

MyNode>

TL1 ALARM TOOLS

To view alarm severities using TL1

! *C = Critical

! ** = Major

! *^ = Minor

! A^ = Clear

The almcde in TL1 indicates the severity of the autonomous messages. Where multiple alarms are reported

in the same message, the displayed alarm code is the most severe.


29/106


30/106



1



1 - 10 009-2003-078



31/106

ONLINETM7000/9000/11000 USER ALARMS

2



009-2003-078 2 - 1


CHAPTER 2

USER ALARMS

This chapter describes the User Alarms feature, in the following sections:

! User Alarms Description on page 2-1

! User Alarm Dialog Box on page 2-1

! User Alarm Outputs on page 2-2

USER ALARMS DESCRIPTION

The Alarm I/O card has detectors to receive inputs from customer equipment that raise user alarms.

Besides the systems pre-defined probable causes, there are eight user alarm probable causes

(User Alarm 1 through User Alarm 8) in systems with a Vertical 19" (19V) or Vertical 23" (23V) main shelf,

and 12 User Alarm Probable Causes (User Alarm 1 through User Alarm 12) in systems with a 23" (23) main

shelf.

The user alarms represent alarms raised outside of the network element (NE), for example a fire alarm,

power surge, flooding, air conditioning or fan failure, or similar condition.

Since these user alarms may severely affect the proper working condition of the system, the detected failure

is passed to the NE, and can be raised as a system failure alarm. Users can decide whether to raise a user

alarm against the NE or not by assigning the alarm severity value as follows:

! If the severity value is notReported, the NEs alarm LEDs will not be lit, the user alarm is not

counted, and the user alarm event will be not sent to CIT/EMS. However, the user alarm will

be added to the NEs current problem list.

! If the severity value is warning, the NEs alarm LEDs will be not lit, the user alarm is not

counted; but the user alarm event will be sent to CIT/EMS, and it will be added to the NEs

current problem list.

! If the severity value is minor or higher, the NEs alarm LEDs will be lit, the user alarm is

counted, the user alarm event will be sent to CIT/NM, and it will be added to the NEs currentproblem list.

USER ALARM DIALOG BOX

The User Alarm dialog box is used for defining the additional text associated with each user alarm.

A meaningful description should be entered for each of the user alarms.

STEP 1: In the CIT select an NE object from the tree and select FaultUser Alarms.

The UserAlarmsDialog box appears, as shown in Figure 2-1. This dialog box shows the listof User Alarms and the corresponding Additional Text.

STEP 2: To edit a user alarm, click in the Additional Text field and enter the description.

STEP 3: When you are have completed your entries, click OK.


32/106

USER ALARMS ONLINETM7000/9000/11000

2



2 - 2 009-2003-078


Figure 2-1. User Alarms Dialog Box

USER ALARM OUTPUTS

This dialog box is used to operate the remote control (contact closures) for the audible and visible outputs.

Select FaultUser Alarm Outputs. The Enable/Disable User Alarm Outputs dialog box appears, as

shown in Figure 2-2. A check in the Enabled column indicates that a particular alarms outputs are enabled.

If there is no check, the alarms outputs are disabled.

To enable or disable a User Alarms outputs, check or uncheck the checkbox in the Enabled field for that

alarm. When you are done enabling or disabling the User Alarms outputs, click OK.


33/106

ONLINETM7000/9000/11000 USER ALARMS

2



009-2003-078 2 - 3


Figure 2-2. Enable/Disable User Alarm Outputs Dialog Box


34/106


USER ALARMS ONLINETM7000/9000/11000

2



2 - 4 009-2003-078



35/106

ONLINETM7000/9000/11000 ALARM CLEARING PROCEDURES

3



009-2003-078 3 - 1


CHAPTER 3

ALARM CLEARING PROCEDURES

These procedures identify the actions needed to correct the alarm conditions. Before replacing any circuit

pack (CP), be sure to check the connections and label them clearly, so that they can be reconnected in the

proper positions easily.Communications alarms caused by equipment failure within the node should be accompanied by related

equipment alarms. If so, correcting the equipment problem should resolve both the equipment and the

communications alarms. Therefore, deal with equipment alarms first.

Communications alarms without equipment alarms can indicate a problem elsewhere in the network

(outside the node), or a problem with one or more of the fibers in the node.

NOTE: Alarms are listed alphabetically in this section by Probable Cause.

AIS (ALARM INDICATION SIGNAL)Explanation The Sync CP receives a clock source input directly from BITS or indirectly through a daisy

chain configuration. This alarm indicates that there is a fault condition upstream for the clock source of

the Sync CP.

Affected Object External Sync reference object

Alarm Type Communications

Default Severity Major

Recommended Action A possible fault condition could be an LOS or OOF alarm in the BITS source

itself, or one of the Sync CPs in the middle.

ALARM CARD FAILURE

Explanation Indicates that the alarm card is either missing or has suffered a hardware failure.

Affected Object Shelf

Alarm Type Environmental

Default Severity Minor

Recommended Action If the Alarm Card is missing, install it. If the Alarm Card is present, reset it by

removing and reinserting it. If this does not clear the alarm, replace the alarm

card.

BER TEST RUNNING

Explanation This alarm is raised when the BER test starts and cleared when the BER test ends.

Affected Object GRDM Circuit Pack

Alarm Type Equipment Alarm

Default Severity Warning

Recommended Action None.


36/106

ALARM CLEARING PROCEDURES ONLINETM7000/9000/11000

3



3 - 2 009-2003-078


CARD PROVISIONING MISMATCH

Explanation Provisioning in the circuit pack does not match the information stored in the PEM.

Affected Object Circuit Pack

Alarm Type Equipment Alarm

Default Severity MinorRecommended Action Reboot the circuit pack using the Warm Reboot With Provisioning Re sync

option. If the alarm is raised again once the circuit pack recovers from the

warm reboot, then contact CIENA Worldwide Customer Services and

Support.

COMMUNICATIONS FAILURE

Explanation This alarm will be raised by OPTX Management Suite GCIT or OPTX NM when a node

is not reachable.

The additional text is: Primary/GNE/ww.xx.yy.zz unreachable

Affected Object GNEAlarm Type Communication


Recommended Action Verify if the OPTX NM Client or OPTX GCIT has valid data communications

connectivity to the subnetwork by pinging the GNE or establishing a

connection via an alternate interface such as the Command Line Interface

(CLI) or TL1. If connectivity is valid, the PEM at the GNE may have rebooted,

so allow up to 5 minutes for the GNE to recover and for communications to

restore. If this alarm persists, contact CIENA Worldwide Customer Services

and Support.

Explanation This alarm will be raised by OPTX Management Suite GCIT or OPTX NM when a node

is not reachable

The additional text is: Network element (id=x) is unreachable

Affected Object NE

Alarm Type Communication

Default Severity Critical

Recommended Action If the GNE is affected, then see the recommended actions above. If a remote

NE is affected, there may be various reasons for the communications loss,

including a PEM reboot, line fiber break, or other connectivity issues which

may be denoted by additional alarms. If this alarm persists for more than 5

minutes, then contact CIENA Worldwide Customer Services and Support.


37/106


3



009-2003-078 3 - 3


Explanation The PEM cannot communicate to the affected circuit pack over either Ethernet link.

Affected Object CP

Alarm Type Equipment


Recommended Action This alarm may denote that the affected circuit pack is rebooting and will

clear when the circuit pack recovers. If the alarm persists, then there may bea failure on the the circuit pack requiring it to be replaced. Typically, the

affected circuit pack should not be reseated as it may still be functioning

properly but will fail to recover to an operational state if the communications

failure condition persists. If the CP LED is solid red, replace the circuit pack.

Otherwise, contact CIENA Worldwide Customer Services and Support.

If this alarm is raised against multiple circuit packs, it is often due to some

other condition that will typically be denoted by one or more additional alarms

such as Ethernet Switch Failure, Shelf Interconnect Failure, or Node in

Hitless State. Investigate the other alarms and contact CIENA Worldwide

Customer Services and Support as needed.

CONFIGURATION ERROR

Explanation This alarm is raised when the NE restarts with a new database (i.e. after restoring an NE

from a backup file or performing hitless database recovery) and there is a provisioned circuit with

unprovisioned supporting equipment.

The additional text is: Equipment not available to support circuit

Affected Object Network element



Recommended Action Provision the equipment that supports the existing circuit.

COOLING FAN FAILURE

Explanation This alarm indicates that the cooling fan is not functioning. The lack of a functioning

cooling fan can cause a High Temperature alarm in the CPs, which has a default priority of Critical.

For the 23" shelf (23") the default severity is major if fans A and B both fail.

Affected Object Shelf


Default Severity Minor/Major

Recommended Action Check the cooling fan. If it is not working, remove the unit and replace it.


38/106


3



3 - 4 009-2003-078


DCC LINK FAILURE

Explanation This alarm will be raised if DCC is configured but there is a problem with the

communication.

Affected Object ADM Circuit Pack

Alarm Type ProcessingDefault Severity Major

Recommended Action Verify DCC is configured on the remote circuit pack and the circuit pack is

up. If the remote circuit pack is provisioned correctly with DCC, then verify

the fibers are physically connected properly. Also, ensure the fibers are fully

seated in their respective bulkhead connectors and have proper signal.

DIAGNOSTICS FAILURE

Explanation Diagnostics are run in the background by the system software once a circuit pack

recovers from a restart. It then runs periodically every 15 minutes. Diagnostics can also be manually

invoked by the user. A failure of a diagnostic test results in Diagnostics Failure alarm and will clear if the

failing diagnostic subsequently passes.

Affected Object Circuit pack



DIAGNOSTICS FAILURE COMPONENT MGR_TEST

Explanation This alarm is raised when the microboot file version in the circuit pack is incorrect.




Recommended Action Warm reboot the circuit pack. If the alarm does not clear, then call CIENA

Worldwide Customer Services and Support.

diagnosticsFailureEEPromTest diagnosticsFailureDeviceEEProm

diagnosticsFailureSpiBusTest diagnosticsFailureDeviceSwitch

diagnosticsFailureHDLCTests diagnosticsFailureDeviceEDFA

diagnosticsFailureEthernetCpm0 diagnosticsFailureDeviceGrdmPhy

diagnosticsFailureEthernetCpm1 diagnosticsFailureDeviceLM81

diagnosticsFailure48VbusA diagnosticsFailureDeviceLEDdiagnosticsFailure48VbusB diagnosticsFailureDevice4080

diagnosticsFailureDevice3270_3110 diagnosticsFailureDeviceI2c

diagnosticsFailureDeviceParallel diagnosticsFailureDeviceCommonLed

diagnosticsFailureDeviceDio diagnosticsFailureADCLoopbackTest

diagnosticsFailureOscMRV diagnosticsFailureDeviceGrdmYukon

diagnosticsFailureDeviceSigFpga diagnosticsFailureDeviceDACad8412

diagnosticsFailureDeviceGrdmEpld diagnosticsFailureDeviceADClm12458

diagnosticsFailureDevicePM5347


39/106


3



009-2003-078 3 - 5


DIAGNOSTICS FAILURE FPGA PROGRAM FAILURE

Explanation This alarm is raised when there has been a failure to program the FPGA.



Default Severity MajorRecommended Action Cold reboot the circuit pack to make a second attempt to program the FPGA.

If the alarm persists after the cold reboot, then call CIENA Worldwide

Customer Services and Support to obtain a Return Material Authorization

(RMA) for the circuit pack.

DIAGNOSTICS FAILURE SLOT MISMATCH

Explanation This alarm is raised when the slot ID obtained from the backplane does not match the

provisioned slot of the circuit pack.

Affected Object Circuit pack/Chassis Backplane



Recommended Action Call CIENA Worldwide Customer Services and Support.

DRIVE MOUNT FAILURE

Explanation This alarm indicates that the PEM is not able to mount the C: drive or D: drive of the PSM.

Affected Object PSM circuit pack



Recommended Action Reboot or replace the PSM circuit pack.

DUPLICATE SIDS IN SUBNETExplanation The user set the SID table entry, and entered duplicate SID values for two different

nodes.

Affected Object Network element

Alarm Type Processing error


Recommended Action Correct the SID table entry.

EAST AUDIT FAILURE

Explanation This alarm is raised when the audit engine in the ADM circuit pack is not able to

communicate with its east neighbor.


Alarm Type Processing


Recommended Action Verify continuity to the east neighbor.


40/106


3



3 - 6 009-2003-078


EAST DEFAULT K BYTE

Explanation This alarm is raised when the east side of the ADM pair has received a default K byte in

three consecutive frames. A default K byte is an indication of a misconfigured node.


Alarm Type CommunicationDefault Severity Major

Recommended Action Verify continuity and node protection provisioning and make adjustments as

necessary to clear the alarm.

EAST ENUT TABLE MISMATCH

Explanation This alarm is raised when the audit engine in the ADM circuit pack detects a mismatch

of the ENUT table with the east neighbor.




Recommended Action Compare and verify the ENUT tables on both nodes.

EAST IMPROPER APS CODE

Explanation This alarm is raised when the east side of the ADM pair has received APS code which is

not consistent with the state of the receiving node.




Recommended Action

EAST INCONSISTENT APS CODEExplanation This alarm is raised when the east side of the ADM pair is observing that out of 12 frames,

no three frames contain identical APS code.




Recommended Action

EAST INTERFACE SIDE MISMATCH

Explanation This alarm is raised when the audit engine of the ADM circuit pack is provisioned to the

same interfaceSide as the east neighbors.Affected Object ADM Circuit Pack



Recommended Action When provisioning the SONET BLSR protection, the user must identify the

west and east side of the ADM pair of ports involved in the protection. Verify

the west and east side is provisioned correctly on both nodes and verify fiber

connections.


41/106


3



009-2003-078 3 - 7


EAST NODE ID MISMATCH

Explanation This alarm is raised when the east side of the ADM pair has received three consecutive

and identical frames that contain a source node ID that does not match any entry in the ring map.


Alarm Type CommunicationDefault Severity Major

Recommended Action Verify the node ID and ring map provisioning to resolve any inconsistencies.

EAST PROTECTION SWITCH FAILURE

Explanation This alarm is raised by the BLSR switch engine when an attempt to switch had failed.




Recommended Action This alarm will clear when the switching condition does not exist any longer

or the switching was completed.

EAST RING MAP MISMATCH

Explanation This alarm is raised when the audit engine of the ADM circuit pack detects its ring map

is different from its east neighbors.




Recommended Action Compare the local and east neighbors ring map to identify any

inconsistencies.

EAST RING MAP ID MISMATCHExplanation This alarm is raised when the audit engine of the ADM circuit pack detects an ID from its

east neighbor which does not match the ring map.




Recommended Action The additional text field for the alarm will indicated the neighbors ring map

ID. Use this information to correct the ring map inconsistencies.

EAST SQUELCH TABLE MISMATCH

Explanation This alarm is raised by the audit engine of the ADM circuit pack when its squelch tableid different from its east neighbors.




Recommended Action Verify squelch tables from the local node and east neighbor. The additional

text field associated with the alarm will indicate the first timeslot where the

mismatches start.


42/106


3



3 - 8 009-2003-078


EEPROM DATA ERROR

Explanation Indicates an error with the EEPROM in the circuit pack.

Affected Object CWDM-U, OLM, OSM, PMM


Default Severity CriticalRecommended Action Call CIENA Worldwide Customer Services and Support for assistance.

EEPROM PROBLEM

Explanation Raised by an internal audit when some EEPROM fields are invalid. Additional text will

indicate the invalid field. This alarm is not service affecting.

Affected Object Network Element



Recommended Action Call CIENA Worldwide Customer Services and Support for assistance.

ETHERNET LINK A FAILURE

ETHERNET LINK B FAILURE

Explanation These alarms are raised when one of the OSC or COM cards