323-1851-543.1 (6500 R9.3 AlarmClearing) Issue1

6500 Packet-Optical Platform
Fault Management - Alarm Clearing,

Part 1 of 2
Release 9.3
What’s inside...
Alarm and trouble clearing strategy
Alarm surveillance
Alarm hierarchies and alarm severities
Alarm clearing procedures—A to H
See Part 2 for the following...

Alarm clearing procedures—I to Z
323-1851-543 - Standard Issue 1

June 2013
Copyright© 2010-2013 Ciena® Corporation. All rights reserved.
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 PUBLISHING; HOWEVER, THE INFORMATION CONTAINED IN THIS
DOCUMENT IS SUBJECT TO CHANGE.
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to
in writing CIENA PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND,
EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change
with out notice.
Copyright© 2010-2013 Ciena® Corporation. 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.
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 or 800-921-1144 www.ciena.com

Customer Technical Support/Warranty
In North America 1-800-CIENA24 (243-6224)
410-865-4961
In Europe, Middle East, 800-CIENA-24-7 (800-2436-2247)
and Africa +44-207-012-5508
In Asia-Pacific 800-CIENA-24-7 (800-2436-2247)
+81-3-6367-3989
+91-124-4340-600
In Caribbean and Latin 800-CIENA-24-7 (800-2436-2247)
America 410-865-4944 (USA)
Sales and General Information 410-694-5700 E-mail: [email protected]
In North America 410-694-5700 or 800-207-3714 E-mail: [email protected]
In Europe +44-207-012-5500 (UK) E-mail: [email protected]
In Asia +81-3-3248-4680 (Japan) E-mail: [email protected]
In India +91-124-434-0500 E-mail: [email protected]
In Latin America 011-5255-1719-0220 (Mexico City) E-mail: [email protected]
877-CIENA-TD (243-6283)
Training E-mail: [email protected]
or 410-865-8996
For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.
6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

Release 9.3 323-1851-543 Standard Issue 1
Copyright© 2010-2013 Ciena® Corporation June 2013
IMPORTANT: PLEASE READ THIS LICENSE AGREEMENT ("AGREEMENT") CAREFULLY BEFORE
INSTALLING OR USING CIENA CORPORATION ("Ciena") SOFTWARE, HARDWARE OR DOCUMENTATION
(COLLECTIVELY, THE "EQUIPMENT").
BY INSTALLING OR USING THE EQUIPMENT, YOU ACKNOWLEDGE THAT YOU HAVE READ THIS
AGREEMENT AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS.
1. Right to Use License; Restrictions. Subject to these terms, and the payment of all applicable license fees, Ciena
grants to you, as end user, a non-exclusive license to use the Ciena software (the "Software") in object code form
solely in connection with, and as embedded within, the Equipment,. You shall have the right to use the Software solely
for your own internal use and benefit. You may make one copy of the Software and documentation solely for backup
and archival purpose, however you must reproduce and affix all copyright and other proprietary rights notices that
appear in or on the original. You may not, without Ciena's prior written consent, (i) sublicense, assign, sell, rent, lend,
lease, transfer or otherwise distribute the Software; (ii) grant any rights in the Software or documentation not expressly
authorized herein; (iii) modify the Software nor provide any third person the means to do the same; (iv) create
derivative works, translate, disassemble, recompile, reverse engineer or attempt to obtain the source code of the
Software in any way; or (v) alter, destroy, or otherwise remove any proprietary notices or labels on or embedded within
the Software or documentation. You acknowledge that this license is subject to Section 365 of the U.S. Bankruptcy
Code and requires Ciena's consent to any assignment related to a bankruptcy proceeding. Sole title to the Software
and documentation, to any derivative works, and to any associated patents and copyrights, remains with Ciena or its
licensors. Ciena reserves to itself and its licensors all rights in the Software and documentation not expressly granted
to you. You shall preserve intact any notice of copyright, trademark, logo, legend or other notice of ownership from any
original or copies of the Software or documentation.
2. Audit: Upon Ciena's reasonable request, but not more frequently than annually without reasonable cause, you
shall permit Ciena to audit the use of the Software at such times as may be mutually agreed upon to ensure
compliance with this Agreement.
3. Confidentiality. You agree that you will receive confidential or proprietary information ("Confidential Information")
in connection with the purchase, deployment and use of the Equipment. You will not disclose Confidential Information
to any third party without prior written consent of Ciena, will use it only for purposes for which it was disclosed, use your
best efforts to prevent and protect the contents of the Software from unauthorized disclosure or use, and must treat it
with the same degree of care as you do your own similar information, but with no less than reasonable care. You
acknowledge that the design and structure of the Software constitute trade secrets and/or copyrighted materials of
Ciena and agree that the Equipment is Confidential Information for purposes of this Agreement.
4. U.S. Government Use. The Software is provided to the Government only with restricted rights and limited rights.
Use, duplication, or disclosure by the Government is subject to restrictions set forth in FAR Sections 52-227-14 and
52-227-19 or DFARS Section 52.227-7013(C)(1)(ii), as applicable. The Equipment and any accompanying technical
data (collectively "Materials") are commercial within the meaning of applicable Federal acquisition regulations. These
Materials were developed fully at private expense. U.S. Government use of the Materials is restricted by this
Agreement, and all other U.S. Government use is prohibited. In accordance with FAR 12.212 and DFAR Supplement
227.7202, software delivered to you is commercial computer software and the use of that software is further restricted
by this Agreement.
5. Term of License. This license is effective until terminated. Customer may terminate this license at any time by
giving written notice to Ciena [or] and destroying or erasing all copies of Software including any documentation. Ciena
may terminate this Agreement and your license to the Software immediately by giving you written notice of termination
in the event that either (i) you breach any term or condition of this Agreement or (ii) you are wound up other than
voluntarily for the purposes of amalgamation or reorganization, have a receiver appointed or enter into liquidation or
bankruptcy or analogous process in your home country. Termination shall be without prejudice to any other rights or
remedies Ciena may have. In the event of any termination you will have no right to keep or use the Software or any
copy of the Software for any purpose and you shall destroy and erase all copies of such Software in its possession or
control, and forward written certification to Ciena that all such copies of Software have been destroyed or erased.

6. Compliance with laws. You agree to comply with all applicable laws, including all import regulations, and to obtain
all required licenses and permits related to installation and use of Equipment. Software, including technical data, is
subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and
may be subject to export or import regulations in other countries. Customer agrees to comply strictly with all such
regulations and acknowledges that it has the responsibility to obtain licenses to export, re-export, or import Software.
7. Limitation of Liability. ANY LIABILITY OF Ciena SHALL BE LIMITED IN THE AGGREGATE TO THE AMOUNTS
PAID BY YOU FOR THE SOFTWARE. THIS LIMITATION APPLIES TO ALL CAUSES OF ACTION, INCLUDING
WITHOUT LIMITATION BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY,
MISREPRESENTATION AND OTHER TORTS. THE LIMITATIONS OF LIABILITY DESCRIBED IN THIS SECTION
ALSO APPLY TO ANY THIRD-PARTY SUPPLIER OF Ciena. NEITHER Ciena NOR ANY OF ITS THIRD-PARTY
SUPPLIERS SHALL BE LIABLE FOR ANY INJURY, LOSS OR DAMAGE, WHETHER INDIRECT, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL INCLUDING WITHOUT LIMITATION ANY LOST PROFITS, CONTRACTS,
DATA OR PROGRAMS, AND THE COST OF RECOVERING SUCH DATA OR PROGRAMS, EVEN IF INFORMED
OF THE POSSIBILITY OF SUCH DAMAGES IN ADVANCE
8. General. Ciena may assign this Agreement to any Ciena affiliate or to a purchaser of the intellectual property rights
in the Software, but otherwise neither this Agreement nor any rights hereunder may be assigned nor duties delegated
by either party, and any attempt to do so will be void. This Agreement shall be governed by the laws of the State of
Maryland (without regard to the conflict of laws provisions) and shall be enforceable in the courts of Maryland. The
U.N. Convention on Contracts for the International Sale of Goods shall not apply hereto. This Agreement constitutes
the complete and exclusive statement of agreement between the parties relating to the license for the Software and
supersedes all proposals, communications, purchase orders, and prior agreements, verbal or written, between the
parties. If any portion hereof is found to be void or unenforceable, the remaining provisions shall remain in full force
and effect.

v
Contents 0
New in this release and documentation roadmap xiii
Alarm and trouble clearing strategy 1-1

Site level alarm correlation 1-1
Network level alarm correlation 1-5
Backwards Defect Indicators (BDI) 1-8
Provisionable severity for alarms and events 1-8
Alarm clearing strategy 1-9
Alarm priority 1-10
LED indications 1-13
Alarm unit 1-13
Circuit pack/module LEDs 1-14
LED sequences 1-21
Lamp test 1-22
Viewing active alarms and events 1-23
Color-coded alarm severity 1-23
Viewing active alarms 1-24
Auto In Service (AINS) 1-24
Viewing events 1-25
Alarm profiles 1-26
Alarm hold-off 1-27
Viewing disabled alarms 1-28
External alarm provisioning and controls 1-28
Power cycling of the network element 1-28
Signal conditioning for 10G AM1/AM2 DWDM 1-29
Signal conditioning for SuperMux circuit packs 1-30
Signal conditioning for 40G circuit packs 1-31
Signal conditioning for 100G circuit packs 1-35
Signal conditioning for 2x10G OTR 4x10-11.3G XFP and 4x10G OTR circuit
packs 1-40
Terminal configuration 1-40
Signal conditioning for FC400/FC800/FC1200 (applicable to 2x10G OTR
(NTK530PME5), 4x10G OTR, the 4x10G MUX (NTK525CFE5), and the
10x10G MUX (NTK529BAE5/NTK529BBE5)) 1-48
Signal conditioning for 5G IBM PSIFB on 2x10GOTR (NTK530PME5 variant only)
and 5G IBM PSIFB or ISC3 on 4x10G OTR (NTK530QA variant only) 1-50
Signal conditioning for 10GEL WT circuit packs 1-51
Signal conditioning for 10G OC-192/STM-64 WT circuit packs 1-53

vi Contents
Signal conditioning for 10G OTU2 WT circuit packs 1-55

Signal conditioning for 10G OTR 1-56
Signal conditioning for 10G OTSC circuit packs 1-57
10G OTSC standalone configuration 1-57
Signal conditioning for 2.5G MOTR circuit packs 1-62
Signal conditioning for FLEX MOTR (NTK531YA) circuit packs 1-66
Signal conditioning for 8xSFP OTN Flex MOTR (NTK532BA) and (1+8) OTN Flex
MOTR (NTK532DA) circuit packs 1-68
Signal conditioning for OTN I/F Flex 16xSFP, 4x10G PKT I/F, and OTN XC I/F 40G
circuit packs 1-102
Signal conditioning for L2 MOTR 2xXFP/10xSFP circuit packs 1-111
Signal conditioning for OC-n/STM-n 20G circuit packs 1-112
Automatic laser shutdown (MSPP and Broadband services) 1-114
Automatic Power Reduction (APR) (Photonic services) 1-115
Automatic Line Shut Off (ALSO) (Photonic services) 1-116
Alarm surveillance 2-1

Abbreviations used in this chapter 2-1
Alarm parameters 2-2
External control types 2-2
Environmental alarm labels 2-3
Autonomous events 2-5
Site Manager navigation 2-9
Procedures for alarms and events 2-10
Procedures for alarm provisioning and alarm profiles 2-10
Procedures for alarm monitoring and management 2-10
Procedures for external alarm provisioning and external controls 2-10
Procedures for Photonic system maintenance 2-11
Associated procedures 2-11
List of procedures
2-1 Setting the time zone for network element or Site Manager timestamps 2-12
2-2 Retrieving active alarms for one or more network elements 2-13
2-3 Retrieving events for a network element 2-15
2-4 Retrieving active disabled alarms 2-18
2-5 Allowing or inhibiting the display of log, inventory, and database change
events 2-19
2-6 Clearing security alarms 2-20
2-7 Retrieving alarm profiles 2-21
2-8 Editing an alarm profile 2-22
2-9 Setting a default profile 2-25
2-10 Setting a profile as active 2-27
2-11 Restarting a circuit pack or shelf processor 2-29
2-12 Identifying the circuit pack, pluggable module/port, or facility that has raised
an alarm 2-38
2-13 Clearing audible alarms and performing lamp tests 2-39
2-14 Provisioning environmental alarm attributes 2-42
2-15 Provisioning, operating, and releasing external controls 2-44
2-16 Locating a reflective event 2-46
2-17 Preparing to perform fiber work on a Photonic system 2-49

Contents vii
2-18 Measuring Photonic amplifier output power 2-52
Alarm hierarchies and alarm severities 3-1

Alarm severities 3-1
Service-affecting and non-service-affecting severities 3-2
Alarm hierarchies 3-4
Overall alarm hierarchy 3-7
Equipment alarm hierarchy (circuit packs and modules) 3-8
Equipment alarm hierarchy (pluggable I/O panels and I/O carriers) 3-9
Equipment alarm hierarchy (provisioned pluggables) 3-10
Equipment alarm hierarchy (unprovisioned pluggables) 3-10
Shelf equipment alarm hierarchy 3-11
DS1 service module alarm hierarchy 3-12
DS3 facility alarm hierarchy - coax to optics direction 3-13
DS3 facility alarm hierarchy - optics to coax direction 3-14
E1 hardware alarm hierarchy 3-15
E1 line alarm hierarchy 3-15
E3 alarm hierarchy - coax to optics direction 3-16
E3 alarm hierarchy - optics to coax direction 3-17
EC-1 facility alarm hierarchy 3-18
ETH10G and FC1200 facility alarm hierarchy 3-19
FC1200 alarm hierarchy for 2x10G OTR, 4x10G OTR, and 4x10G MUX circuit
packs 3-20
FC400/FC800 alarm hierarchy for 2x10G OTR, 4x10G OTR, and 4x10G MUX circuit
packs 3-21
4x10G OTR (NTK530QA) circuit pack infiniband alarm hierarchy 3-22
100G OCI circuit pack ETH100G facility alarm hierarchy 3-23
40G OCI+ CFP circuit pack ETH40G facility alarm hierarchy 3-24
40G MUX OCI circuit pack 10GbE WAN facility alarm hierarchy 3-25
LAN/WAN EPL facilities alarm hierarchy (ETH, ETH100, FC100/FC200/FC400, GE,
and WAN facilities) 3-26
EFM alarm hierarchy for SuperMux circuit pack ETH facility 3-28
L2SS, 20G L2SS, and PDH gateway circuit pack alarm hierarchy 3-29
20G L2SS and L2 MOTR circuit pack maintenance alarm hierarchy 3-30
FLEX MOTR, 8xOTN Flex MOTR, and (1+8)xOTN Flex MOTR circuit packs
OC-n/STM-n client protocols alarm hierarchy 3-30
FLEX MOTR and Broadband circuit packs Fiber Channel, 8B10B, and Transparent
client protocols alarm hierarchy 3-31
8xOTN Flex MOTR and (1+8)xOTN Flex MOTR circuit packs Fiber Channel, 8B10B,
and Transparent client protocols alarm hierarchy 3-32
8xOTN Flex MOTR and (1+8)xOTN Flex MOTR circuit packs WAN facility alarm
hierarchy 3-33
(1+8)xOTN Flex MOTR client port facility OTM mapping layer alarm hierarchy 3-34
(1+8)xOTN Flex MOTR client port facility (low-order ODU0, ODU1, and ODUFLEX
facilities) alarm hierarchy 3-35
4x10G PKT I/F circuit pack OTN PKT facility alarm hierarchy - faceplate to fabric
direction (RX) 3-36
4x10G PKT I/F circuit pack OTN mapped Ethernet facility alarm hierarchy 3-37
4x10G PKT I/F circuit pack (terminated) Ethernet facility OTN alarm hierarchy 3-38
OC-n/STM-n facility alarm hierarchy (Broadband circuit packs) 3-39

viii Contents
OC-n/STM-n and STS/VT/VC facility alarm hierarchy (MSPP optical interface circuit
packs) 3-40
L2 MOTR circuit pack ETH100/ETH/ETH10G facility alarm hierarchy 3-41
L2 MOTR circuit pack WAN facility alarm hierarchy 3-42
OTM1/OTM2/OTM3 facility alarm hierarchy 3-43
100G OCLD circuit packs line port OTM4 facility alarm hierarchy 3-44
10x10GE MUX OCI circuit pack backplane port 100 OTM4 facility alarm
hierarchy 3-45
100G OCI circuit pack client port OTM4 facility alarm hierarchy 3-46
100G OCI circuit pack client port OTM4 mapping layer facility alarm hierarchy 3-47
OTM2 mapping facility (associated with FC1200, OC-192/STM-64, and ETH10G
facility) alarm hierarchy 3-48
TCM facility alarm hierarchy - faceplate to backplane direction 3-49
TCM facility alarm hierarchy - backplane to faceplate direction 3-50
Photonic optical signal facilities alarm hierarchy 3-51
RPR circuit pack alarm hierarchy 3-52
RPR circuit pack LAN port alarm hierarchy 3-53
STM-1e alarm hierarchy 3-53
Alarm clearing procedures—A to H 4-1

Abbreviations used in this chapter 4-1
Associated procedures 4-5
List of alarms 4-5
4-1 1+1/MSP linear and 1+1 TPT APS alarms 4-22
4-2 Adjacency Discovery Unreliable 4-25
4-3 Adjacency Far End Not Discovered 4-27
4-4 Adjacency Mismatch 4-30
4-5 Adjacency Provisioning Error 4-33
4-6 Alarm and Event Throttling Active 4-36
4-7 Alarm Provisioning Near Limit 4-37
4-8 All Provisioned RADIUS Accounting Servers Unavailable 4-38
4-9 All Provisioned RADIUS Servers Unavailable 4-40
4-10 ALS Disabled 4-41
4-11 ALS Triggered - Laser is shutdown 4-42
4-12 Automatic Power Reduction Active 4-43
4-13 Automatic Shutoff 4-47
4-14 Automatic Shutoff Compromised 4-48
4-15 Automatic Shutoff Disabled 4-49
4-16 Auto Protection Switch Acknowledge Time Out 4-51
4-17 Autoprovisioning Mismatch 4-53
4-18 Autoprovisioning Mismatch - Pluggable 4-55
4-19 Backplane ID Module 1/2 Failed 4-56
4-20 Calibration Required 4-58
4-21 CCM Error 4-59
4-22 Channel Controller: Failure Detected 4-60
4-23 Channel Controller: Unexpected Loss Detected 4-64
4-24 Channel Degrade 4-70
4-25 Channel Opacity Error 4-74
4-26 Circuit Pack Configuration Save Failed 4-75
4-27 Circuit Pack Failed 4-76

Contents ix
4-28 Circuit Pack Failed - Pluggable 4-82

4-29 Circuit Pack Failed-Sync and Circuit Pack Failed-Traffic 4-84
4-30 Circuit Pack Latch Open 4-86
4-31 Circuit Pack Mate Mismatch 4-88
4-32 Circuit Pack Mismatch 4-89
4-33 Circuit Pack Mismatch - Pluggable 4-95
4-34 Circuit Pack Missing 4-96
4-35 Circuit Pack Missing - Pluggable 4-105
4-36 Circuit Pack 3rd Party - Pluggable 4-106
4-37 Circuit Pack Operational Capability Exceeded 4-107
4-38 Circuit Pack Unknown 4-109
4-39 Circuit Pack Unknown - Pluggable 4-112
4-40 Circuit Pack Upgrade Failed 4-114
4-41 Client Service Mismatch 4-116
4-42 CMF UPI Mismatch 4-118
4-43 Cold Restart Required: FPGA Changed 4-120
4-44 Config Mismatch - LCAS 4-122
4-45 Configuration Mismatch 4-124
4-46 Configuration Mismatch - Adv BW Limit 4-125
4-47 Configuration Mismatch - Common ID 4-126
4-48 Configuration Mismatch - Concatenation 4-127
4-49 Configuration Mismatch - Link ID 4-128
4-50 Configuration Mismatch - Node 4-129
4-51 Configuration Mismatch - Primary State 4-130
4-52 Corrupt Inventory Data 4-131
4-53 CPE Discovery Protocol Fail 4-134
4-54 CP Loss of Host Timing Ref. 4-136
4-55 CPU2 Unreachable 4-137
4-56 CPU2 Warm Restart Required 4-138
4-57 Craft Load Missing 4-139
4-58 Craft Load Unpacking Aborted - Low Disk Space 4-140
4-59 Cross-connection Mismatch 4-141
4-60 Cross connect Error 4-145
4-61 Crossed Fibers Suspected 4-146
4-62 Database Auto Save in Progress 4-147
4-63 Database Integrity Fail 4-148
4-64 Database Integrity Fail - CPU2 4-149
4-65 Database Not Recovered For Slot 4-150
4-66 Database Recovery Incomplete 4-151
4-67 Database Restore in Progress 4-153
4-68 Database Save and Restore Failed 4-154
4-69 Database Commit Failed 4-157
4-70 Database Save in Progress 4-159
4-71 DCC Link Fail alarms 4-160
4-72 Debug Port in Use 4-166
4-73 Delay Measurement Enabled on Slave Node (6500) 4-167
4-74 Delay Measurement Failed (6500) 4-168
4-75 Delay Measurement Mismatch Capability (6500) 4-169
4-76 Disk Full alarms 4-170
4-77 DOC Action: Channel Add In Progress 4-172

x Contents
4-78 DOC Action: Channel Delete In Progress 4-173

4-79 DOC Action Failed: Add 4-174
4-80 DOC Action Failed: Delete 4-177
4-81 DOC Action Failed: Monitor 4-180
4-82 DOC Action Failed: Optimize 4-183
4-83 DOC Action: Fault Detected 4-186
4-84 DOC Consecutive Re-Opt Threshold Crossed 4-189
4-85 DOC Domain Not Optimized 4-192
4-86 DOC Invalid Photonic Domain 4-194
4-87 DOC Power Audit Failed 4-199
4-88 Domain Optical Controller Disabled 4-201
4-89 DS1 Receive alarms 4-202
4-90 DS3 and E3 Receive alarms 4-209
4-91 Dormant Account Detected 4-218
4-92 DSM-Host Misconnection 4-219
4-93 Duplicate Adjacency Discovered 4-222
4-94 Duplicate IP Address 4-223
4-95 Duplicate Primary Shelf 4-225
4-96 Duplicate Shelf Detected 4-227
4-97 Duplicate Site ID 4-229
4-98 E1 Receive alarms 4-231
4-99 E1 Transmit alarms 4-236
4-100 EC-1 Receive alarms 4-243
4-101 Equipment Configuration Mismatch 4-248
4-102 Equipment OOS with Subtending Facilities IS 4-251
4-103 Equipment Reconfiguration In Progress 4-253
4-104 Error alarms (ETH, ETH10, ETH40G, ETH100G, FLEX, WAN, ETTP) 4-254
4-105 Error alarms (OC/STM, STS/HO VC, and VT/LO VC) 4-261
4-106 ESI alarms 4-270
4-107 Event Log full 4-276
4-108 Excessive Input Power 4-277
4-109 Facility Reconfiguration In Progress 4-278
4-110 Facility Reconfiguration Required 4-279
4-111 Fan Failed 4-280
4-112 Fan Failed (DSM) 4-284
4-113 Fan Housing Missing 4-285
4-114 Fan Incompatible 4-287
4-115 Fan Missing (DSM) 4-289
4-116 Far End Client Signal Fail 4-290
4-117 Far End Protection Line Fail 4-292
4-118 Fiber Channel Link Not operational 4-293
4-119 Fiber Loss Detection Disabled 4-294
4-120 Fiber Type Manual Provisioning Required 4-295
4-121 Filler Card Missing 4-296
4-122 Filter Replacement Timer Expired 4-297
4-123 Flash Banks Mismatch 4-299
4-124 Frequency Out of Range (OC192/STM64, ETH10G) 4-300
4-125 Gauge Threshold Crossing Alert Summary 4-301
4-126 GCC0/GCC1/GCC2 Link Failure 4-306
4-127 Group Loss of Signal 4-310

Contents xi
4-128 High Fiber Loss 4-312

4-129 High Received Span Loss 4-316
4-130 High Temperature 4-318
4-131 High Temperature Warning 4-322

xii Contents

xiii
New in this release and documentation

roadmap 0
Attention: This document is presented in two parts: Part 1 and Part 2. Each
part has its own table of contents. The table of contents in Part 1 contains
topics found in Part 1 only. The table of contents in Part 2 contains topics
found in Part 2 only. Part 2 continues sequential chapter numbering from
Part 1.
The alarm clearing procedures are presented in two chapters, “Alarm
clearing procedures—A to H” and “Alarm clearing procedures—I to Z”. The
complete “List of alarms” is included in both chapters.
You are reading Part 1 of Fault Management - Alarm Clearing, 323-1851-543.
The following section details what’s new in Fault Management - Alarm

Clearing, Part 1 of 2, 323-1851-543, Standard Issue 1 for Release 9.3.
This Technical Publication supports 6500 Packet-Optical Platform

Release 9.3 software.

xiv New in this release and documentation roadmap
New features in Release 9.3 Issue 1

The following new/enhanced features are covered in this document:
— Single Line Raman Amplifier (SRA C-Band) w/Optical Service
Channel (OSC) 1xSFP 10/100 BT WSC circuit pack (NTK552JA)
— Service Access Module (SAM C-Band) w/Optical Service Channel
(OSC) 1xSFP 10/100 BT WSC circuit pack (NTK552JN)
— Enhanced Service Access Module (ESAM C-Band) w/Optical Service
Channel (OSC) 1xSFP 10/100 BT WSC circuit pack (NTK552JT)
— Switchable Line Amplifier (XLA C-Band) circuit pack (NTK552KA)
— eMOTR 4xXFP/8xSFP+ circuit pack (NTK536AA)
— eMOTR 4xXFP/8xSFP+/32xSFP circuit pack (NTK536FA)
• new software features
— Photonic enhancements (OSC reach for RAMAN spans, RAMAN
system configurations, OTDR Functionality)
— 2-port OPM enhancements
• upgrade support from Releases 7.02/8.00/8.10/9.00/9.01/9.12/9.20/9.21
Supporting documentation
The following is a list of application-specific documents that are applicable to
the 6500.
• The 6500 Packet-Optical Platform Data Application Guide, NTRN15BA,
provides detailed information on data concepts, applications, and
engineering rules.
• The Universal AC Rectifier Application Note for Packet-Optical Transport,
009-2012-900, provides configuration, installation, operating,
maintenance and planning information related to this AC Rectifier solution.
• The 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA,
provides detailed information on Photonic concepts, applications, and
engineering rules.
• The 6500 Packet-Optical Platform Submarine Networking Application
Guide, NTRN72AA, provides detailed information on Submarine
applications and engineering rules.
• The SAOS-based Packet Services Command Reference, 323-1851-610,
the SAOS-based Packet Services Configuration, 323-1851-630,
the SAOS-based Packet Services Fault and Performance, 323-1851-650,
and the SAOS-based Packet Services MIB Reference, 323-1851-690,
provide detailed information for the eMOTR and PKT/OTN cross-connect
circuit packs. eMOTR and PKT/OTN cross-connect circuit packs use an
operating system based on the Service Aware Operating System (SAOS)
for Layer 2 services.

New in this release and documentation roadmap xv
6500 Packet-Optical Platform technical publications

The following roadmap illustrates the structure of the 6500 technical
publications library.
Planning a Network Installing, Managing and Maintaining and Circuit Pack-Based

Commissioning and Provisioning Troubleshooting Documentation
Testing a Network a Network a Network
Documentation Installation, Administration Fault Management - Common Eqpt

Roadmap Parts 1 and 2 and Security Performance (323-1851-102.1)
(323-1851-090) (323-1851-201) (323-1851-301) Monitoring
(323-1851-520) Electrical
Planning - Commissioning Configuration - (323-1851-102.2)
Ordering Information and Testing Provisioning Fault Management -
(323-1851-151) (323-1851-221) and Operating Alarm Clearing OC-n/STM-n
Parts 1 and 2 Parts 1 and 2 (323-1851-102.3)
TL-1 Description (323-1851-310) (323-1851-543)
(323-1851-190) 40G/100G/
Configuration - Fault Management - OSIC/SLIC10
Planning - Bandwidth and Module (323-1851-102.4)
Parts 1, 2, 3, and 4 Data Services Replacement
(NTRN10CF) Parts 1, 2 and 3 (323-1851-545)
(323-1851-320) Broadband/SMUX
OTN FLEX MOTR
Site Manager for Fault Management - (323-1851-102.5)
6500 and CPL Configuration - Customer Visible
Fundamentals Control Plane Logs
(323-1851-195) (323-1851-330) (323-1851-840) Photonic Equipment
(323-1851-102.6)
Data and Layer 2

(323-1851-102.7)
OTN I/F and PKT I/F

(323-1851-102.8)
SAOS-based Command Fault and MIB

Configuration
Packet Services Reference Performance Reference
(323-1851-630)
(323-1851-610) (323-1851-650) (323-1851-690)
Documentation
6500 Photonic 6500 Data Network Common

Layer Guide Application Guide Interworking Guide Photonic Layer
Supporting (NTRN15DA) (NTRN15BA) (NTCA68CA) Technical Publications
Documentation 6500 Control Plane
Submarine Networking Universal AC Rectifier
Application Guide Application Guide Application Note
(NTRN72AA) (NTRN71AA) (009-2012-900)

xvi New in this release and documentation roadmap

323-1851-543
1-1
Alarm and trouble clearing strategy 1-
This release of 6500 Packet-Optical Platform (6500) supports the MSPP,

Broadband, PKT/OTN transport and switched, and Photonic services for
different circuit packs. The combination of two or all services is also
supported.
For more information on the services (and the circuit packs related to each
service), refer to the Introduction chapter in Part 1 of 6500 Planning,
NTRN10CF.
Site level alarm correlation

The site level alarm correlation feature reduces the number of alarms reported
at each site to a minimum. It does not reduce the number of sites in a network
reporting alarms. This is done by Network level alarm correlation feature.
Once Alarm Correlation is enabled, it automatically enables both Site level
and Network level alarm correlation. One cannot exist without the other.
The feature requires the system to have full knowledge of topology and
connectivity within the network, including channel routing at OADM sites. The
physical topology of the network is represented by adjacency objects. The
shelf level correlator uses these adjacency objects to notify downstream
facilities that an upstream failure has occurred and suppresses alarms on
circuit packs within the same site. The service photonic layer interoperability
module is responsible for messaging and auditing the fault information which
spans shelves within the site.
Alarm correlation requires that physical adjacency information be provisioned

between Photonic equipment at a site. For DOC controlled systems, no extra
information is required from a user perspective as this adjacency information
already exists in order to build the channel topology information (to
automatically add/delete photonic channels). For passive photonic systems,
which do not use DOC, the adjacency information is necessary to enable
features such as SPLI and Site Level Alarm correlation. In order for alarm
correlation to work all the way down to the service layer (that is, service circuit
packs connected to the photonic equipment), physical adjacency information
needs to be provisioned. The Physical Adjacency information between the
service layer equipment and the CMD is provided by the Service and Photonic

1-2 Alarm and trouble clearing strategy
Layer Interoperability (SPLI) feature. The adjacency information between

service layer equipment (for example, between a 40G MUX OCI and a 10G
OTSC) must be manually provisioned. Also, Alarm Correlation requires that
the Transponder connections between an OCLD and an OCI be provisioned.
Transponder connections are also required to carry traffic.
Alarm correlation has the ability to correlate the service circuit pack faults
“backwards” to the CMD44, OMD4, OMX, OMDF4, OMDF8, BS1, BS2, BS3,
or BS5 when all “in-use” channels are faulted. Alarm Correlation software
considers a channel “in-use” when the channel’s service circuit pack facility
connected to the CMD44, OMD4, OMX, OMDF4, or OMDF8 Channel Output
port has a non-nil discovered far-end address. A non-nil discovered far-end
address implies a SPLI match exists.
Attention: In passive photonic configurations, the DSCM, which is

provisioned as excess loss on a given filter port, is not involved in alarm
correlation.
If the discovered far-end address is nil then that channel is not considered
when calculating the “all in-use channels failed” condition.
At least two channels must be in-use before the “backwards” alarm correlation
is initiated.
A new virtual OPTMON facility is created for the CMD44, OMD4, OMX,
OMDF4, OMDF8, BS1, BS2, BS3, or BS5 Common Input (or NTWK Rx) port
and the Common In (or NTWK Rx) fault is reported as an OPTMON Loss of
Signal, or OPTMON Group Loss of Signal alarm, depending upon the
scenario.
Unlike CMD44 Channel Input ports, the Common In port defaults to “IS” rather
than “IS-ANR,MON” when no channel is provisioned and changes to
“OOS-AU,FAF” when the LOS condition is asserted.
For the OPS circuit packs, Loss of Signal (LOS) at SW1 IN/SW2 IN does not
result in an alarm against OPS SW1/SW2 ports if SLC (Site Level Correlation)
is enabled and a correlated upstream alarm within the same site co-exists with
the OPS LOS fault.
The Alarm Correlation parameter within the Site Manager Node Information
application and the System tab must be set to On for the “backwards” alarm
correlation to function.

Backwards alarm correlation only functions if all service circuit packs

connected to the CMD44, OMD4, OMX, OMDF4, OMDF8, BS1, BS2, BS3, or
BS5 support alarm correlation.
Site level alarm correlation is supported on the OMX, CMD44, OMDF4,

OMDF8, BS1, BS2, BS3, BS5, and OMD4 configurations provided that all of
the following conditions apply:
• Alarm correlation is set to On in the Site Manager Node Information
application and the System tab.
• All adjacencies are manually provisioned. Refer to the “Editing facility
parameters” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
• All cascading equipment (CMD44, OMD4, OMX, OMDF4, OMDF8, BS1,
BS2, BS3, BS5) are provisioned in the same shelf.
• Service circuit packs used in the configuration must support alarm
correlation.
See 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA, for

detailed information on OMD4 based single-span applications, and passive
photonic layer applications.
Site level alarm correlation is supported on the RAMAN amplifiers in the

following configurations.
• SRA - XLA – SRA
• SRA - XLA – ESAM/SAM
• ESAM/SAM - XLA – SRA
• ESAM/SAM – XLA – ESAM/SAM (any combination)
All traffic related alarms are masked when the “OTDR Trace in Progress”
alarm is raised.
Figure 1-1 on page 1-4 and Figure 1-2 on page 1-5 show an example of
alarms to be raised in a line fiber cut scenario with and without alarm
correlation on a DOC controlled system.

Figure 1-1
Line fiber cut without alarm correlation on a DOC controlled system
Loss Shutoff Loss

of threshold of
signal crossed signal
Gauge
TCA
summary
OSC OSC OSC OSC OSC
OPM OPM
WSS WSS
Automatic
CMD44 CMD44 shutoff
Optical Optical
line fail line fail
TR
ADJ Far End Automatic Shutoff
not discovered shutoff threshold
OCI crossed
Loss of
signal
ODU AIS

Figure 1-2
Line fiber cut with alarm correlation on a DOC-controlled system
Gauge Shutoff Optical

TCA threshold line fail
summary crossed
OSC OSC OSC OSC OSC
OPM OPM
WSS WSS
CMD44 CMD44 Automatic Shutoff

shutoff threshold
crossed
TR
OCI
For the list of supported circuit pack combinations refer to the “CMD Tx/Rx
type discovery, Tx power & Tx wavelength autoprovisioning, network & site
alarm correlation per circuit pack type support” table in chapter 2 of Part 1 of
6500 Planning, NTRN10CF.
Alarm Correlation is supported for DIA OADM configurations.
The alarm correlation functionality can be enabled/disabled on a per shelf

basis by editing the Alarm correlation parameter using the Site Manager Node
Information application and the System tab. Refer to the “Editing the nodal
system parameters” procedure in Administration and Security, 323-1851-301
for more information.
Network level alarm correlation

Network level alarm correlation (NLC) builds on the Site Level Alarm
Correlation feature. Site Level Alarm Correlation masks alarms within a site
based on a detected fault. However, Site Level Alarm Correlation does not
share fault information with neighboring nodes in the network. It also does not
track per-channel failures when channels are muxed and mixed together with
non-failed channels.

Essentially, NLC will do site level alarm correlation but it will also do network
level alarm correlation. Network Level Alarm Correlation addresses the gaps
of the SLC feature based on wavelength topology. Network Level Alarm
Correlation expands adjacency discovery (AD) messaging to support OTS to
OTS (intra-node and inter-node) Network Level Alarm Correlation messaging.
NLC shares and collects channel status information with neighbors. With a
knowledge of the channel statuses, NLC performs alarm correlation and
masks alarms.
Network Level Alarm Correlation:

• Suppresses symptomatic (downstream and lower level) alarms
• Suppresses “Hard” faults if all channels on that port are failed (Hard faults
are the faults that affect all channels on a port; for example, LOS, AIS,
Shutoff Crossed)
• Suppresses “Soft” faults if any channel on that port is failed (Soft faults are
the faults that affect only some channels or partial power loss; for example,
PM TCAs, Unexpected Loss)
• Suppresses alarms in the network within one minute of the failure
When the photonic network is single-channel, the NLC may be unable to

distinguish between a hard fault and a soft fault since there is only one
channel within the line port. In these situations, manual isolation of the fault
may be required to determine where the root cause of the failure is within the
photonic network.
For the OPS circuit packs, Loss Of Signal (LOS) at SW1 IN/SW2 IN does not
result in an alarm against OPS SW1/SW2 ports if NLC is enabled and a
correlated upstream alarm co-exists with the OPS LOS fault.
Figure 1-3 on page 1-7 shows an example of Network Level Alarm

Correlation.
Figure 1-4 on page 1-7 and Figure 1-5 on page 1-8 show examples of data
flow and alarm suppression using channel status indicators.

Figure 1-3
Network level alarm correlation
Network Level Alarm Correlation

Example: Line Amp Failure - Network Level Correlation
1 2 2
DOC "I" AMP AMP AMP "E" "F"
Site (OADM) (OADM) (OADM)
Fault Detected 1
Alarms
Loss of Signal
Optical Line Fail 1 1
Automatic Shutoff 1 1
Shutoff Threshold Crossed
Unexpected Loss Detected
Gauge TCA Summary
ADJ Far End Not Discovered
Circuit Pack Failed
OSC Loss of Signal
OTU BDI
ODU BDI
ODU AIS
Note: Bubbles indicate number of alarms raised per site
Figure 1-4
Data flow of channel status indicators

Figure 1-5
Alarm suppression using channel status indicators
Backwards Defect Indicators (BDI)

OTMn facilities raise BDI alarm to indicate a problem exists at the other end
of the link. By definition BDI is always a “symptomatic” alarm. When Alarm
Correlation is On (default), Conditioning Override can be Standing Condition,
Profile (default) or Off. When Alarm Correlation is Off, Conditioning Override
can be Standing Condition, or Profile.
Provisionable severity for alarms and events

Two types of events are supported on the 6500, Standing Conditions (SC) for
which a raised and a clear Autonomous Output (AO) are generated and
Transient Conditions (TC) for which a raised AO is generated but not a clear.
Site Manager supports Critical, Major, Minor, and Warning severity types for
alarms. If a Warning severity is selected for a given alarm, the alarm will be
raised by the Network Element (NE) as an SC. The Warning severity can be
applied to all alarms independently of their default severity (Critical, Major, or
Minor). By default, the Warning severity of Standing Conditions is also
provisionable in the Alarms Profile application to any of Critical, Major or
Minor.

By default each alarm has two severities assigned to it, a Service Affecting
(SA) and a Non-Service Affecting (NSA) severity, both of which are generally
provisionable in the Alarms Profile application. Some alarms on the 6500
support only one severity, which could be either the SA or the NSA. In the
Alarms Profile application Site Manager displays a "-" for a non-provisionable
severity and disables the capability to edit the field. If for any of the SA or NSA
severities a Warning is selected, the alarm would be raised as a Standing
Condition (SC) for the selected severity.
The severity of an alarm is indicated by the following designations: Critical (C),

Major (M) or minor (m). A warning (w) is used for Standing Conditions. It is
important to note that the impact of a Standing Condition (SC), SA or NSA, is
not reported by the Network Element (NE), hence the Active Alarms
application in Site Manager would report the SC as a "w" and displays a "-" in
the Service column.
The capability to provision the severity does not apply to Transient Conditions,
non provisionable alarms, or environmental alarms.
Alarm clearing strategy

The 6500 hardware and software perform automatic fault detection and
identification. When a network element detects a fault, it issues autonomous
alarms, activates office alarms, and displays alarms through LEDs.
In addition to raising alarms on a shelf, 6500 also supports the generation of

northbound simple network management protocol (SNMP) traps for network
element alarms and events. Refer to the “Editing and deleting SNMP trap
destinations” procedure in Part 2 of Configuration - Provisioning and
Operating, 323-1851-310.
The alarm clearing strategy is based on several assumptions:

• No external problem causes the alarm, such as power fluctuation.
• Primary fault generates primary and secondary alarms that you can clear
with a single fault clearing procedure.
• The network element is provisioned correctly, and works until the time of
the alarm.
• If protection circuitry exists, traffic is switched before performing the alarm
clearing.

The network elements report alarms in the following ways:

• alarm LEDs on the network element and circuit packs
• lamps and audible alarms on the
— MIC and BIP in a 14-slot 6500 shelf. The MIC indicates alarms for the
shelf and the BIP indicates alarms for the 6500 shelves in a bay.
— access panel in a 32-slot 6500 shelf.
— cooling unit in a 7-slot 6500 shelf.
• northbound SNMP trap reporting for the NE-level alarms
• network element alarm messages retrieved locally through Site Manager
or TL1
• office alarms (optional)
The following steps make up the strategy for fault and alarm clearing:
• Detect there is a fault.
• Identify the network element that raised the alarm.
• Check for illuminated Fail LEDs on the circuit packs or modules.
• If a Fail LED is illuminated, perform the procedure to replace a failed circuit
pack, module, or pluggable module.
• If the Fail LED is not illuminated, retrieve alarm messages through Site
Manager.
• Identify the local and remote alarms during the procedure.
• Identify the alarm severity.
• Identify which network element to clear.
• Perform trouble-clearing procedures.
• Determine if there are additional alarms.
• If alarms continue to be active, begin the process again.
• If the alarms are cleared, end the process.
For more information on the steps, see Fault clearing strategy on page 1-12.
Alarm priority
Critical alarms have the highest priority and are reported before Major, minor
or Warning alarms. Major alarms are reported before minor alarms and minor
alarms are reported before warnings. Clear alarms in order of severity:
• critical, service-affecting (C, SA) alarm
• major, service-affecting (M, SA) alarm
• major, non-service-affecting (M, NSA) alarm

• failed circuit pack non-service-affecting (NSA) alarm

• minor, service-affecting (m, SA) alarm
• minor, non-service-affecting (m, NSA) alarm
One fault can cause more than one alarm. Clear the alarm with the highest
severity and some other alarms often clear.
You can change the alarm severity of both high and low entities using the
Alarms Profile application in Site Manager. Refer to Procedure 2-8, “Editing
an alarm profile” in Chapter 2, “Alarm surveillance”.
The alarm notification codes (service affecting, SA, or non-service affecting,

NSA) are unaffected by change of alarm severity. The alarm severities in the
ALL ENABLED, ALL DISABLED, and FACTORY DEFAULT alarm profiles
cannot be changed.
Refer to the Service-affecting and non-service-affecting severities on page

3-2 for further details on alarm severities.

Figure 1-6
Fault clearing strategy
Alarm
detected
Yes Press ACO

Audible ?
button
No
Swap failed Yes Circuit pack or

circuit pack or
module failed ?
module
No
Login local
Retrieve
alarms
ID faults
&
severity
Go to trouble
clearing
procedure
Clear fault
Alarm ?
Yes
No
End

LED indications
The 6500 uses an LED indication scheme, where:
• red indicates failure (requires replacement)
• green indicates active (powered and operational)
For the DS1 DSM circuit pack, the green LED illuminates when its OC-3
facility is in service and at least one DS1 facility is in service and has
cross-connects.
• yellow indicates warning (something missing or activity in progress)
For DS1 DSM circuit pack, the yellow LED illuminates when there is Loss
of Signal on the OC-3 facility, Loss of synchronization reference signal, or
OAM Link to SP failed.
• blue indicates do not unseat (removing the circuit pack will impact service)
Alarm unit
The alarm unit (AU) contains LEDs to provide visual indication of alarms active
for the 6500 installed on the rack. The alarm unit illuminates the appropriate
LEDs (critical, major and minor) on the front panel of the BIP based on alarm
signals received from the 6500 shelves through the alarm input interface and
close the appropriate alarm relay contacts on the alarm output interface.
The alarm unit contains the following LEDs:

• red and yellow alarm LEDs fed from the input alarm signals illuminate to
indicate the following conditions:
— critical alarm (red)
— major alarm (red)
— minor alarm (yellow)
• red power LED illuminates to indicate either or both of the following
conditions:
— tripped circuit breaker on either side (A or B)
— open alarm unit fuse
The alarm unit contains a lamp test button on the front panel of the BIP. When
pressed, all LEDs illuminate. The alarm unit also contains a push button
switch (ACO) on the BIP front panel to reset all BIP alarm relays. The alarm
unit is field replaceable on the NTK599BA variant.
Note that the 1U BIP/FIP does not have an alarm unit.

Circuit pack/module LEDs

After a circuit pack is inserted, reseated, or a cold restart is performed, all of
the LEDs turn on for approximately five seconds.
Each circuit pack contains the following status LEDs:

• triangular red Fail LED
• rectangular green Ready LED
• diamond blue In Use LED
Exceptions include the Power Input Card, fan module, MIC, filler cards, DSM,
and any equipment connected to external slots (with an RJ45 inventory cable)
such as a PPC6, CMD44, OMD4, OMX, BMD2, UBMD2, MBMD2, or DSCM
module.
Some MSPP and BB circuit packs also contain a:

• circular yellow LOS LED
• circular yellow Synchronization status LED
• circular red/yellow bi-color Optical Fail/LOS LED
The 84xDS1 DSM has five LEDs: Status, Active, LOS, OAM, and RefSync.
Figure 1-7
Circuit pack LEDs
Fail
Ready
In Use
Red Fail LED

The triangular red Fail LED indicates a hardware or software failure state of
the circuit pack.
The red LED turns on when an equipment failure has been isolated to that
circuit pack and the circuit pack must be replaced (for example, a Circuit Pack
Failed alarm is active on the circuit pack).
The red LED turns on for approximately 30 seconds when a lamp test is
initiated.
The red LED flashes when a user intervention flash test is being performed.

The Red LED turns on while Green LED stays on to indicate that the circuit
pack has partial failure. Partial failures are normally indicated by some circuit
pack related alarms. It is recommended to verify every alarm raised against
the circuit pack to identify the partial failure.
Green Ready LED

The rectangular green Ready LED indicates the circuit pack is powered-up
and does not have a circuit pack fail condition.
The green LED turns on when the circuit pack initialization is completed and
a circuit pack fail condition is not present.
The green LED turns off when a circuit pack fail condition is detected on the
circuit pack.
The green LED turns on for approximately 30 seconds when a lamp test is
initiated.
The green LED flashes when:

• a circuit pack is initializing
• a software auto-upgrade is being performed
• a user intervention flash test is being performed
Blue In Use LED

The diamond blue In Use LED indicates the circuit pack is in-service.
The blue LED turns on when the circuit pack is in-service.
Attention: When the shelf processor or the OTN cross-connect circuit packs
power up in a shelf (after the shelf is decommissioned), the blue/green LED
on both cross-connect circuit packs will turn on.
The blue LED turns on for approximately 30 seconds when a lamp test is
initiated.
The blue LED flashes when an user intervention flash test is being performed.

The blue LED turns off when the:

• circuit pack is out-of-service
• a circuit pack has been inserted or cold restarted and cannot be
provisioned by the shelf processor. This occurs for failed circuit packs,
mismatched circuit packs, or circuit packs that have their database rebuilt.
CAUTION
Risk of traffic loss
Do not remove a circuit pack while the blue In Use LED is
illuminated.
Yellow LOS LED

The circular LOS LED is used to indicate Rx Loss of Signal condition.
The yellow LED turns on for approximately 30 seconds when a lamp test is
initiated.
The yellow LED flashes when a user intervention flash test is being
performed.
Red/yellow bi-color circle (Fail/LOS) LED

The circular LOS LED located to the left of each port is used to communicate
optical module (SFP/XFP/SFP+) fail and receive loss of signal (for the CFP
module this LED is located below the module):
• The red LED turns on when a pluggable is present and the pluggable has
failed.
• The yellow LED turns on when a receive loss of signal condition is
detected on the port (and the corresponding facility is provisioned) and the
pluggable is present and has not failed.
Some circuit packs contain additional LEDs as detailed in the following

sections.
Power Input Card

With the exception of the NTK503MAE5 and NTK503NAE5 variants of the
2-slot shelf, all 6500 shelves use field-replaceable Power Input Cards to
interface between the shelf's power connection points and the backplane.
With the NTK503MAE5 and NTK503NAE5 variants of the 2-slot shelf, the
Power Input Cards and associated green Power OK LEDs for feeds A and B
are integrated into the shelf. Depending on the shelf or equipped Power Input
Card variant, power may be supplied by -48/60 V dc feeds, 24 V dc feeds or
100-240 V ac (50Hz or 60Hz) feeds.

The Power Input Cards have one or more Power OK LED (circular shape
except the NTK605CAE5, NTK605EAE5 variants of the 3x60A Power Input
Cards where a rectangle is used). The green LED turns on to indicate the
Power Input Card is active and a minimum voltage is detected and flowing
through to the backplane (through any breaker, fuse or power converter if
applicable to the equipped Power Input Card). In the case of a DC Power Input
Cards, the feed must also be in the correct polarity for its associated Power
OK LED to illuminate. In any case where the Power OK LED is not illuminated
and the Power Input Card is working correctly, an operational shelf processor
should assert any applicable alarms such as Power Failure -A/B, Power
Failure - Low Voltage or Power Failure - Fuse Blown. However, in some cases
a Power OK LED may be illuminated indicating that a minimum voltage is
detected on a feed but the shelf processor may still assert one or more of the
following alarms based on the shelf's operating specification: Power Failure
-A/B, Power Failure - Low Voltage or Power Failure - Fuse Blown (if
applicable). See Part 2 of Fault Management - Alarm Clearing, 323-1851-543
for details.
With the exception of the NTK605CAE5 and NTK605EAE5 variants of the

3x60A Power Input Cards, Power Input Cards that terminate more than one
feed have a Power OK LED per feed (i.e. Power OK for each of feed L1, L2,
etc). For the NTK605CAE5 and NTK605EAE5 variants of the 3x60A Power
Input Card (Breakered and fused), the green LED turns on to indicate that all
three feeds (L1, L2 and L3) are at least approximately -40 Vdc and all three
breakers are on (or all 3 fuse cartridges with fuses are in place and working).
Power OK LED ON means that there are no "Power Failure" alarms against
any feeds on that module.
For the 3x60A Power Input Cards Type 2 (NTK605FA, NTK605FE) and the
4x60A Power Input Cards Type 2 (NTK605GA and NTK605GE), the Lx Power
OK LED (Lx=L1, L2, L3 for 3x60A and Lx=L1, L2, L3, L4 for 4x60A) indicates
that the feed is live (has a minimum voltage applied). The SP raises an alarm
if the voltage is not at least -40V on a feed). The LED may remain illuminated
until there is insufficient voltage on the feed to illuminate it.
For the NTK605CAE5 and NTK605EAE5 variants of the 3x60A Power Input
Card, the rectangular amber LED labeled “Low voltage” indicates that at least
one of the feed voltages is below approximately -40Vdc. The LED turns off
when all feed voltages fall below approximately -24Vdc. The "Low Voltage"
LED could also mean that one or two breakers are off/tripped (or one or two
fuses missing/blown) and the remaining feed is at least approximately -24
Vdc. If all three breakers are off/tripped (or fuses missing/blown) both LEDs
will be off (because there is no voltage to activate the Low Voltage LED). Low
Voltage LED ON means that there is at least one "Power Failure" alarm
against a feed on that module.

Attention: Use of the alarm indicator fuse provided with Fused Power Input
Card kits (NTK505EAE5, NTK605EAE5, or NTK505EEE5) is optional and
requires careful consideration. The fuse cartridge connects the main fuse
and alarm indicator fuse in parallel. If the main fuse is missing or already
blown on installation, the electrical path through the parallel alarm indicator
fuse may provide sufficient current to activate the Power OK LED on the card
but insufficient current to blow the fuse. Neither a Power Failure nor a Power
Failure - Fuse Blown alarm would be asserted giving the impression of power
redundancy. Alarm indicator fuses are intended for use where required by
the installation practice, otherwise, the indicator fuse position must be
covered with the label provided with the Power Input Card.
Maintenance interface card

The maintenance interface card (MIC) contains five circular LEDs that indicate
the alarm status of the shelf:
• The green Power LED turns on if power is present on the shelf.
• The red Critical LED turns on if one or more Critical alarm exists on the
shelf.
• The red Major LED turns on if one or more Major alarm exists on the shelf.
• The yellow Minor LED turns on if one or more minor alarm exists on the
shelf.
• The white ACO LED turns on when the ACO button is pressed and at least
one Critical, Major, or Minor alarm exists on the shelf. The ACO LED turns
off if:
— no alarms exist on the shelf
— a new Major or Critical alarm is raised
Fan modules
The fan modules have a triangular red LED and a rectangular green LED.
• The red LED turns on to indicate a fan module failure.
• The green LED turns on to indicate an operational fan module.
The fan modules in the 7-slot shelf include alarm LEDs and Alarm Cut-off
(ACO)/Lamp test button.
Ethernet ports
Each Ethernet port on the shelf processor and access panel has two LEDs
(one green and one yellow) integrated in the RJ45 connector.
• The green LED turns on when a link pulse is received.
• The yellow LED turns on when data is being received on the receive port.

The Ethernet port LEDs are not turned on during a power-up or a cold restart
sequence of the shelf processor.
Interface circuit packs without pluggable optics

Circuit packs without pluggable optics (for example, 1xOC-192/STM-64,
16xSTM-1e, 63xE1, 24xDS3/E3, 24xDS3/EC-1, port 1 of SuperMux,
40G OCI, 40G OCLD or Wavelength-Selective 40G OCLD) have a circular
yellow LED (16 yellow LEDs for STM-1e, one yellow LED for E1, and 24 yellow
LEDs for DS3/E3 or DS3/EC-1). The yellow LED turns on when a receive loss
of signal condition is detected on the port and the corresponding facility is
provisioned.
If a terminal loopback is applied to the optical facility while a loss of signal

condition exists, the yellow LED turns off as the loss of signal detection circuit
is bypassed.
Interface circuit packs with pluggable optics

Circuit packs with pluggable optics (for example, 4xGE, 1x10GE EPL,
8xOC-3/12/STM-1/4, 8xOC-n/STM-n 5G VT1.5/LO SFP, 2xOC-48/STM-16,
16xOC-3/12/48/STM-1/4/16, L2SS VT1.5/LO 4xGE, L2SS PDH gateway, 20G
L2SS, 24x10/100BT EPL with 8xSFP, RPR, or ports 2 to 11 of SuperMux)
have a circular bi-color red/yellow LED located to the left of each port.
The red LED turns on when a pluggable is present and the pluggable has
failed.
For an 8xOC-3/12/STM-1/4, 2xOC-48/STM-16, 16xOC-3/12/48/STM-1/4/16,

or MXC circuit pack, the yellow LED turns on when a receive loss of signal
condition is detected on the port (and the corresponding facility is provisioned)
and the pluggable is present and has not failed.
For a 4xGE, 1x10GE EPL, 24x10/100BT EPL with 8xSFP, L2SS, PDH
gateway or RPR circuit packs, the yellow LEDs turns on when a receive loss
of signal condition is detected on the port (and the corresponding facility is
provisioned) and the pluggable is present and has not failed.
For a SuperMux circuit pack, the yellow LED behavior depends on whether the
OC-3/12/STM-1/4 or 4xGE pluggable is present.
For a 4xGE, 1x10GE EPL, 24x10/100BT EPL with 8xSFP, L2SS, PDH
gateway, RPR, or MXC circuit pack, a red/yellow bi-color LED (one for each
SFP port), is used to communicate module fail or Loss of Signal on pluggable
modules.
For a 20G L2SS circuit pack, a red/yellow bi-color LED (one for each SFP/XFP
port), is used to communicate module fail or Loss of Signal/Loss of data
synch/Link Down on pluggable modules.

If a terminal loopback is applied to the optical facility while a loss of signal

is bypassed.
Fast Ethernet 24x10/100BT EPL ports

The Fast Ethernet 24x10/100BT EPL port circuit packs have the following
LEDs on the front of the circuit pack:
• Red LED
• Green LED
• Blue LED
• On the 48x10/100BT I/O panel, a yellow LED is associated with each of
the 24 I/O panel LAN ports.
• On the 24x10/100BT EPL and 24x10/100BT EPL with 8xSFP circuit
packs, a yellow Loss of Sync group LED on the faceplate will be
illuminated if at least one of the I/O panel LAN ports are indicating a link
failure condition.
For the 24x10/100BT EPL and 24x10/100BT EPL with 8xSFP circuit packs,
one mono-color yellow LED is associated with each of the 24 I/O panel LAN
ports.
On the 24x10/100BT EPL with 8xSFP circuit pack, ports 1 to 8 can either be
an SFP port or an I/O panel port. For ports 1 to 8, only the LED of the selected
port will be illuminated to indicate the failure. For example, if a LAN loss of
signal condition exists and the SFP has been selected as the physical
interface then only the LED associated with the SFP will be illuminated, and
not the corresponding I/O panel LED.
Electrical interface circuit packs

The 63xE1 working and 63xE1 protection circuit packs have a yellow LED that
turns on if any provisioned E1 facility (in-service or out-of-service) detects loss
of signal.
If a terminal loopback is applied to the E1 facility while a loss of signal

is bypassed (unless a loss of signal condition exists on another E1 facility).
The DS3/EC-1 or DS3/E3 circuit pack has 24 yellow LEDs (one for each port)
that turn on if any provisioned facility detects loss of signal.
E1 protection module
The protection modules required for 1:N protection of the E1 circuit packs in
an optical/front electrical shelf have a blue LED that turns on if 1:N protection
is provisioned against the supporting circuit pack and the protection circuit
pack is not locked out. Do not remove the module when the blue LED is lit.

Cross-connect circuit pack

The cross-connect circuit packs, including the MXC, have four circular yellow
LEDs (LOS Ref 1, Ref 2, Ref 3, and Ref 4), one for each of the four possible
reference sources in the timing generation hierarchy. The yellow LED turns on
when a loss of synchronization reference is detected for the associated
provisioned timing reference source.
LED sequences
During a power up (circuit pack insertion or reseat) or a restart, the red Fail,
the green Ready, and the blue In Use status LEDs on the front of the circuit
pack go through a sequence as detailed in the subsequent sections.
Circuit pack insertion/reseat and cold restart LED sequence

For a circuit pack insertion/reseat or a cold restart, the red Fail, the green
Ready, and the blue In Use status LEDs go through the following sequence:
• The red LED turns on momentarily.
• After a few seconds, the red, green and blue LEDs turn on.
• After a few seconds, the red and blue LEDs turn off and the green LED
flashes to indicate the software is initializing.
• When software initialization is complete, the green status LED turns on
(does not flash).
• If the circuit pack is in-service, the blue LED turns on after the green LED
while the circuit pack is in use. If the circuit pack has failed, the green LED
turns off and the red LED turns on.
During a circuit pack insertion/reseat or a cold restart, the port and Ethernet
port status LEDs remain off.
When the green LED is steadily lit (after the software initialization), an
auto-upgrade of the circuit pack may occur. During an auto-upgrade, the
green LED remains steadily lit and the blue LED remains off (a Software
Auto-Upgrade in progress alarm is raised and clears after the auto-upgrade is
complete).
Warm restart sequence

For a warm restart, the red Fail, the green Ready and the blue In Use status
LEDs go through the following sequence:
• The red and blue LEDs remain in the state they were before the restart.
• After a few seconds, the green LED flashes to indicate the software is
initializing.


(does not flash).
• If the circuit pack has failed, the green LED turns off and the red LED turns
on.
Lamp test
A lamp test can be initiated using the ACO/Lamp Test (ACO/LT) button found
near the shelf's Critical, Major and Minor LEDs or using Site Manager.
When initiated, the lamp test is performed on all the LEDs on the network
element (does not apply to any shelf peripherals provisioned in virtual slots or
connected to RJ45 external slot inventory interfaces). A lamp test times out
after approximately 30 seconds and the LEDs revert to the correct status. For
bi-color port LEDs, one color is lit for first 15 seconds and the other color is lit
for the remaining 15 seconds.
In the 32-slot shelf, the lamp test button (labeled ACO/LT) is on the Access
Panel (AP). In the 14-slot shelf, the lamp test button (labeled ACO/Lamp Test)
is on the Maintenance interface card (MIC). The lamp test function will activate
all LEDs in the system if at least one SP is present and in a ready state.
Depressing the button will have no effect if both SPs are missing or are not
ready.
In the 7-slot shelf, the lamp test button (labeled ACO/Lamp Test) is on the fan
module. The lamp test function will activate all LEDs in the system if the SP is
present and in a ready state. Depressing the button will have no effect if the
SP is missing or is not ready.
In the 2-slot shelf, there is no Lamp test button on the shelf. The software
initiated lamp test is performed using Site Manager.
When initiated from Site Manager, the test can be performed on all the LEDs
on the network element or on a single circuit pack.
Attention: You cannot perform a lamp test on the LEDs on the Power Input
Cards. On some access panels, the RJ45 external slot inventory interfaces
appear to have two LEDs but there is only one that is used during normal
operation and that will illuminate during a lamp test.

In addition, the user has the option to perform a user intervention flash test on
a slot or port basis that causes the LEDs to flash, allowing a user at the site
to identify a circuit pack or pluggable. When initiated for a slot, the status LEDs
(red Fail, green Ready, and blue In Use) on the specified circuit pack flash for
15 minutes and status of all port LEDs remain the same. When initiated for a
port, the status LEDs (red Fail, green Ready, and blue In Use) on the circuit
pack and the specified port LED flash for 15 minutes (if the port LED is
bi-color, only the yellow color flashes).
Consider the following:

• Only ports on circuit packs with pluggables physically present can be
selected for a port user intervention flash test.
• A user intervention flash test cannot be performed on the LEDs on the
MIC, the Power Input Card, the access panel, the fan modules, or the LAN
on the shelf processor.
• A user intervention flash test can be stopped by performing a non-flash
lamp test or using the on/off radio buttons on Site Manager.
For information on initiating a lamp test:

• using the ACO button, refer to Procedure 2-13, "Clearing audible alarms
and performing lamp tests" on page 39
• from Site Manager, refer to the “Performing a lamp test and clearing
audible alarms using the Visualization tool” procedures in Administration
and Security 323-1851-301
Viewing active alarms and events

Active alarms are indicated on the 6500 equipment and are visible from the
Site Manager user interface. Alarm history, events, and logs are stored on the
network element. Login sessions using Site Manager craft user interface,
Optical Manager Element Adapter, and Optical Application Platform provide
details of network element alarms.
The types of 6500 network element alarms are:

• equipment
• common equipment
• facility
Color-coded alarm severity

Color is used to highlight the severity value in the application summary tables
for the following Site Manager applications:
• Consolidated Alarms
• Active Alarms

• Historical Fault Browser

• Active Disabled Alarms
• Visualization tool display of filtered active alarms
The color coding is defined as follows in Table 1-1 on page 1-24.
Table 1-1
Alarm severity color coding
Alarm severity Site Manager alarm

color coding
Critical, service-affecting (C, SA) red

Critical, non-service-affecting (C, NSA) red
Major, service-affecting (M, SA) red
Major, non-service-affecting (M, NSA) orange
Minor, service-affecting (m, SA) orange
Minor, non-service-affecting (m, NSA) orange
Warning (w, -) yellow
Viewing active alarms

Site Manager provides the user with a visual summary of all active alarms for
all 6500 network elements logged in to, through the alarm banner. The user
views a list of active alarms on a 6500 shelf by selecting the Active Alarms
application on the Fault menu of Site Manager. A maximum of 4600 active
alarms are supported on the 6500 network element.
The active alarm application provides the user with the ability to filter and sort
alarms and perform manual or automatic refresh of the active alarm list.
Alarms details are available for each active alarm in the list.
Alarm reports can be affected by the primary state of the circuit pack and
facilities. For example, an alarm is not reported until the primary state of a
circuit pack or facility changes from out-of-service to in-service.
Auto In Service (AINS)

AINS is the ability to setup traffic on a network without alarms prior to the end
user signal being applied and error-free. This allows entities to be put
in-service, but remain alarm free until a card is inserted or cables (traffic)
plugged into the circuit pack.

When a facility is created with AINS enabled, or edited to set AINS to enabled,
primary and secondary states indicate that the facility is in an alarmed
condition, but alarms are not generated off the NE.
When a clean signal is detected for a facility in AINS, a timer starts. If the
facility remains alarm free for the specified AINS timeout value, the facility will
automatically transition from the AINS state. Subsequent conditions that
result in alarms will result in alarms being generated off the NE.
AINS timeout value is editable using a system wide parameter, applicable to

all entities supporting AINS on the shelf. Supported AINS timeout value range
is from five minutes to 96 hours. AINS timeout value can be set in increments
of five minutes. Refer to the “Editing a login profile” procedure in
Administration and Security, 323-1851-301.
When a facility is in an AINS state, suppressed alarms can be retrieved in the

Active Disabled Alarms application within Site Manager
Traffic alarms and events are suppressed for the facility with the AINS state,
explicitly including the following:
• Traffic faults, near end and far end
• PM TCA reports
• WAN alarms/PMs on a LAN facility
• Path alarms within OC-n facilities
• Alarms which require manual action to clear, such as “Loopback Active”
Protection switch alarms/events are not suppressed. Refer to Part 1 of

Configuration - Provisioning and Operating, 323-1851-310 for more
information.
PM collection is also inhibited when a facility is in an AINS state. PM counts

will not be recorded/calculated for facilities and paths. Analog PMs, such as
power levels which are measured, will continue to be recorded. Bins will be set
to IDF when the AINS state is active.
Viewing events
The Historical Fault Browser application supports the following functionality:
• viewing of historical (current and cleared) alarms for the 6500 network
element
• viewing of logs
• filtering of alarms based on severity
• details for specific events (alarms or logs)

The 6500 also supports the generation of northbound SNMP traps for network
element alarms and events. For more details on supported SNMP
functionality, refer to the:
• “SNMP support” section in chapter 5 of Part 2 of 6500 Planning,
NTRN10CF
• external alarm provisioning, external controls, and SNMP procedures in
Chapter 2, “Alarm surveillance”
The 6500 network element stores up to 5500 events. 5000 of those are from
alarms/events that were enabled, and the other 500 are for alarms/events that
were disabled at the time they were generated. The Historical Fault Browser
application provides the user with the ability to filter and sort events and
perform manual refresh of the event list.
Alarm profiles
The alarm profiles application gives to the user the ability to view, edit, and
delete alarm profiles.
A profile contains all the alarm points applicable for the alarm class and a
status, enabled or disabled, for each alarm point. A profile can be applied to
an individual facility or circuit pack of that alarm class to quickly disable
multiple alarm points. A default profile can be set for an alarm class so that
when a new facility or circuit pack of that class is first provisioned, the default
alarm profile is applied to it automatically.
The alarm profile also contains the severity (C, M, m, w) for each alarm, which
can be edited by the user.
The 6500 network element provides two non-editable predefined profiles (All
Enabled which is the default, and All Disabled) and allows for three more
predefined profiles to be user editable on the network element.
The Common alarm class supports an additional non-editable profile, Factory

Default. For the Common alarm class, this profile enables all common alarms
except for the Disk 75 percent Full, Disk 90 percent Full, LAN-15 Port Failure,
and LAN-16 Port Failure alarms, which are disabled.
The low order (VT1.5/VC11 and VT2/VC12 for MSPP services) path facilities
on interface circuit packs also support the Factory Default profile. The Factory
Default profile disables the reporting and logging of the VT1.5/VC11 and
VT2/VC12 defects. By default, all VT1.5/VC11 and VT2/VC12 facilities are set
to Factory Default. Alarm monitoring of VT1.5/VC11 and VT2/VC12 facilities
is limited to 1344 for each optical interface circuit pack, any request to monitor
more than this limit is rejected.

The following is a list of alarms that do not appear in any alarm profile (which
means these alarm points cannot be disabled):
• Alarm and Event Throttling Active
• Automatic shutoff disabled
• Autoprovisioning Mismatch
• Autoprovisioning Mismatch - pluggable
• Circuit pack operational capability exceeded
• Circuit pack unknown
• Circuit pack unknown - pluggable
• Equipment Configuration Mismatch
• Fan Failed
• Filler Card Missing
• FPGA Load Tag Mismatch
• Manual Area Address Dropped
• Number of Level 1 NEs Exceeded
• Provisioning Incompatible
• Provisioning Incompatible - pluggable
• Redundant Release Synch Failed
• Shelf Data Missing
Alarm hold-off
Alarm hold-off period is time delay between the time that the alarm condition
occurs and the time that the alarm is raised. The user can manually change
the alarm hold-off from 2.5 seconds (default) to 0 seconds for alarms
associated with MSPP, Broadband, OTN I/F, PKT I/F, and Photonic circuit
packs. Alarm hold-off feature applies to AMP, OPTMON, OSC, and CHC
facilities in Photonic circuit packs, OCn/STMn facilities on MSPP, and all
facilities on Broadband, PKT I/F and OTN I/F circuit packs including OTN Flex
MOTR, Flex MOTR and L2 MOTR circuit packs.
This feature allows you to see alarms for fast transient conditions that would
normally be filtered by the 2.5 second hold-off. The alarm hold-off period is
changed using the System tab in the Node Information application in Site
Manager. Refer to the “Editing the nodal system parameters” procedure in
Attention: When Alarm hold-off set to 2.5, alarms which are raised and
cleared within 2.5 seconds time-frame are not acknowledged.

Viewing disabled alarms

Alarms that have been disabled from the alarm profiles application are not
displayed in the Active Alarms application. Active alarms that have been
disabled can be viewed in the Active Disabled Alarms application in the
Faults menu of Site Manager.
Attention: Disabled alarms will not be displayed in the Active Disabled

Alarms application against a WAN, OTM0 or OTM1 mapping layer facility
when the mapping layer of the port is connected in a client hairpin.
External alarm provisioning and controls

The 6500 network element and each provisioned DSM has 16 parallel
telemetry input points and four external control relays.
The input points allow remote monitoring of other equipment in the office in
which the network element is located. For example, the input points can
monitor room temperature alarms or office door open alarms. Specific
external alarms must be set up during provisioning. The alarm types are
assigned to a specific contact pin.
The External Alarm Provisioning application in the Configuration menu of

Site Manager supports the following functionalities:
• displaying external alarm attributes (telemetry input points)
• editing the environmental alarm attributes on the network element
• editing the environmental alarm attributes on a DSM
• deleting defined environmental alarm attributes on the network element
• deleting defined environmental alarm attributes on a DSM
The external controls application allows the user to retrieve and display the
labels and status of the four external controls relays for the 6500 network
element and DSM. The 6500 network element and DSM allow the user to
operate or release these relays to turn external equipment on and off (for
example, air conditioning, fan, sprinkler) and edit the labels of the relays.
Power cycling of the network element

If the network element time is not provisioned to retrieve its time of day from
an NTP server and a power cycle occurs on the network element, you must
reprovision the network element date and time as the date and time are reset
to the default values. If the time of day (TOD) synchronization feature is
enabled, you do not have to reprovision the date and time. Refer to the “Editing
the nodal general parameters” procedure in Administration and Security,
323-1851-301.

Signal conditioning for 10G AM1/AM2 DWDM

10G signal failure
The following signal conditioning is applied for port 1 triggered events.
Table 1-2
10G AM1/AM2 DWDM signal conditioning—10G signal failure
Trigger Tx conditioning
Condition Facility Signal Output Facility
OTM2 p1 Facility OOS (Note 1) OTM2 p1 ODU2 AIS OTM2 p1
OTM2 p1 Rx ODU2 AIS (Note 2) OTM2 p1 ODU2 BDI OTM2 p1

RFI-L OC192/STM64 p1
OTM2 p1 Rx OPU2 PN11 OTM2 p1 No conditioning OTM2 p1

(OPU2 PN11 condition is not RFI-L (Note 3) OC192/STM64 p1
alarmed)
OTM2 p1 Rx OTU2 LOS, LOF, OTM2 p1 OTU2 BDI and ODU2 BDI OTM2 p1
LOMF or Pre-FEC Signal Fail RFI-L OC192/STM64 p1
(Note 4)
OTM2 p1 Rx OTU2 BDI or ODU2 BDI OTM2 p1 No conditioning OTM2 p1

(Note 5) No conditioning OC192/STM64 p1
PTI Mismatch (Note 6) OTM2 p1 No conditioning OTM2 p1
OC192/STM64 p1 LOF OC192/STM64 p1 No conditioning OTM2 p1

OC192/STM64 p1 AIS OC192/STM64 p1 No conditioning OTM2 p1

Note 1: When the OTM2 facility is OOS the OC192/STM64 facility is automatically OOS.
Note 2: ODU2 AIS masks all OC192/STM64 alarms.
Note 3: AIS-L is raised.
Note 4: OTU2 alarms mask all OC192/STM64 alarms.
Note 5: OTU2 BDI and ODU2 BDI mask RFI-L.
Note 6: PTI Mismatch will trigger RFI-L for OC192/STM64 facility on port 1.

10G circuit pack equipment failure

The following signal conditioning is applied for circuit pack failures.
Table 1-3
10G AM1/AM2 DWDM signal conditioning—10G circuit pack equipment failure
Condition Signal Output Facility
Circuit Pack Fail ODU2 AIS OTM2 p1

Line/MS AIS OC192/STM64 p1
Signal conditioning for SuperMux circuit packs

SuperMux 10G signal failure
The following signal conditioning is applied for port 1 triggered events.
Table 1-4
SuperMux signal conditioning—10G signal failure
OTM2 p1 Facility OOS (Note 1) OTM2 p1 ODU2 LCK OTM2 p1
OTM2 p1 Rx ODU2 AIS (Note 2) OTM2 p1 ODU2 BDI OTM2 p1

OTM2 p1 Rx OPU2 AIS OTM2 p1 OPU2 AIS OTM2 p1

LOMF or Pre-FEC Signal Fail RFI-L OC192/STM64 p1
OTM2 p1 Rx OTU2 BDI or ODU2 BDI OTM2 p1 No conditioning OTM2 p1

(Note 3) No conditioning OC192/STM64 p1
PTI mismatch (Note 4) OTM2 p1 No conditioning OTM2 p1


Note 4: PTI mismatch will trigger RFI-L for OC192/STM64 facility on port 1.

SuperMux 10G circuit pack equipment failure

The following signal conditioning is applied for circuit pack failures.
Table 1-5
SuperMux signal conditioning—10G circuit pack equipment failure
Condition Signal Output Facility
Circuit Pack Fail ODU2 AIS OTM2 p1

Line/MS AIS OC192/STM64 p1
Signal conditioning for 40G circuit packs

40G OCLD/Wavelength-Selective 40G OCLD unprotected configuration
The following signal conditioning is applied to the 40G OCLD and
Wavelength-Selective 40G OCLD circuit packs in an unprotected
configuration.
Attention: When using a 1+1 protection configuration, the OCLD

conditioning towards its mated circuit pack may not trigger conditioning on
the mated circuit pack if that circuit pack can successfully switch to the
protection path. However, if both the working and the protection OCLD circuit
packs are conditioning towards the mated circuit pack, then conditioning will
be triggered on the mated circuit pack.
Table 1-6
40G OCLD/Wavelength-Selective 40G OCLD signal conditioning (unprotected)
Fault Condition Signal conditioning Towards Signal Conditioning Towards

Mated Circuit Pack Line Port
No ODU Connection None (no connection) ODU3 OCI
p1 SF (OTM3 on-ramp) No conditioning ODU3 AIS
p1 Facility OOS ODU3 LCK ODU3 LCK
p1 LOS, LOC, LOF, LOMF, ODU3 AIS OTU3 SM-BDI

Pre-FEC SF

40G MUX OCI signal conditioning

The following signal conditioning is applied to the 40G Mux OCI circuit pack.
Table 1-7
Fault Condition 40G MUX OCI Signal Conditioning Signal Conditioning

p1-4 Facility Towards Mated Towards Client Port
Circuit Pack (Laser off if LOFEF
enabled)
No ODU3 Connection OC192/STM64 None (no connection) AIS-L

ETH10G None (no connection) LF
OTM2 None (no connection) ODU2 AIS
FC800 None (no connection) NOS
FC1200 None (no connection) LF
p100 ODU3 AIS, ODU3 LCK, OC192/STM64 ODU3 PM-BDI AIS-L

ODU3 OCI, SF (OTM3 ETH10G ODU3 PM-BDI LF
off-ramp)
OTM2 ODU3 PM-BDI ODU2 AIS
FC800 ODU3 PM-BDI NOS
FC1200 ODU3 PM-BDI LF
p100 OPU3 PT Mismatch, OC192/STM64 No conditioning AIS-L

OPU3 AIS (OTM3 off-ramp) ETH10G No conditioning LF
OTM2 No conditioning ODU2 AIS
FC800 No conditioning NOS
FC1200 No conditioning LF
p1-4 ODU2 AIS, ODU2 LCK, OC192/STM64 ODU2 PM-BDI AIS-L

ODU2 OCI (OTM2 off-ramp) ETH10G ODU2 PM-BDI LF
OTM2 No conditioning No conditioning (Note 1)
FC800 ODU2 PM-BDI NOS
FC1200 ODU2 PM-BDI LF
p1-4 OPU2 PT Mismatch, OC192/STM64 No conditioning AIS-L

OPU2 AIS (OTM2 off-ramp) ETH10G No conditioning LF
OTM2 No conditioning No conditioning
FC800 No conditioning NOS
p1-4 WAN Link Down, WAN ETH10G No conditioning LF

Loss of Frame Delineation
(WAN off-ramp, GFP only)

Table 1-7 (continued)

Fault Condition 40G MUX OCI Signal Conditioning Signal Conditioning

p1-4 Facility Towards Mated Towards Client Port
enabled)
p1-4 Facility OOS OC192/STM64 ODU2 LCK AIS-L

ETH10G ODU2 LCK LF
OTM2 ODU2 LCK ODU2 LCK
FC800 ODU2 LCK NOS
FC1200 ODU2 LCK LF
p1-4 LOS, LOC, LOF OC192/STM64 OPU2 AIS No conditioning

FC800 OPU2 AIS No conditioning
p1-4 LOS, LOC, LOF LOMF, OTM2 OPU2 AIS OTU2 PM-BDI
Pre-FEC SF
p1-4 LOS, LOC, LOF, HiBER ETH10G ODU2 AIS No conditioning (Note 2)
FC1200 ODU2 AIS No conditioning
Service-affecting Circuit Pack OC192/STM64 ODU3 AIS AIS-L

Fail ETH10G ODU3 AIS LF
OTM2 ODU3 AIS ODU2 AIS
FC800 ODU3 AIS NOS
FC1200 ODU3 AIS LF
Note 1: There is no conditioning unless LOFEF is enabled; in which case, the laser is turned off.
Note 2: For the NTK525CA, there is no conditioning occurs when operating in 11.05 and 11.09
proportional wrap. However, in GFP mode RF is conditioned. For the NTK525CF, there is no
conditioning.
40G OCI signal conditioning

The following signal conditioning is applied for the 40G OC circuit packs.
Table 1-8
Fault Condition 40G OCI p1 Signal Conditioning Signal Conditioning

Facility Towards Mated Towards Client Port
enabled)
No ODU Connection OC768/STM256 None (no connection) AIS-L

OTM3 None (no connection) ODU3 OCI
ETH40G None (no connection) LF


Fault Condition 40G OCI p1 Signal Conditioning Signal Conditioning

Facility Towards Mated Towards Client Port
enabled)
p1 SF (OTM3 off-ramp) OC768/STM256 ODU3 PM-BDI AIS-L

OTM3 No conditioning ODU3 OCI
ETH40G ODU PM-BDI LF
p1 ODU3 AIS, ODU3 LCK, OC768/STM256 ODU3 PM-BDI AIS-L

ODU3 OCI (OTM3 off-ramp) OTM3 No conditioning No conditioning (Note 1)
ETH40G ODU3 PM-BDI LF
p1 OPU PT Mismatch, OPU3 OC768/STM256 None (no connection) AIS-L

AIS (OTM3 off-ramp) OTM3 None (no connection) No conditioning
p1 OPU PT Mismatch, OPU3 ETH40G None (no connection) LF

AIS, OPU3 CSF (OTM3
off-ramp) (Note 2)
p1 Facility OOS OC768/STM256 ODU3 LCK AIS-L

ETH40G ODU3 LCK LF
p1 LOS, LOF OC768/STM256 OPU3 AIS No conditioning
p1 LOS, LOC, LOF, LOM, OTM3 ODU3 AIS OTU3 SM-BDI

Pre-FEC SF
p1 LOS, LOF, HiBER ETH40G OPU3 CSF No conditioning
Service-affecting Circuit Pack OC768/STM256 ODU3 AIS AIS-L

Fail OTM3 ODU3 AIS ODU3 AIS
ETH40G ODU3 AIS LF
Note 2: OPU CSF is alarmed as Far End Client Signal Fail.

Signal conditioning for 100G circuit packs

Optical muxponder configuration (10x10GE MUX, 10x10G MUX, 100G
WaveLogic 3 OCLD, Flex2 WaveLogic 3 OCLD, and 100G OCLD)
The following signal conditioning is applied for the 10x10GE MUX, 10x10G
MUX, 100G WaveLogic 3 OCLD, Flex2 WaveLogic 3 OCLD, and 100G OCLD
circuit packs in optical muxponder configuration.
Table 1-9
10x10GE MUX, 10x10G MUX, 100G WaveLogic 3 OCLD, Flex2 WaveLogic 3 OCLD, and 100G
OCLD signal conditioning—optical muxponder configuration
Condition 10x10GE 100G OCLD/100G 10x10GE

MUX/10x10G WaveLogic 3 MUX/10x10G MUX
MUX OCLD/Flex2 p1-10 (client)
p1-10 Facility WaveLogic 3 OCLD Signal Output
p1 (OTM4) (Laser off if LOFEF
Signal Output enabled)
No Transponder Connection OC192/STM64 ODU4 OCI AIS-L

ETH10G ODU4 OCI LF
OTM2 ODU4 OCI ODU2 AIS
p1 (100G OCLD) Facility OOS OC192/STM64 ODU4 LCK AIS-L

ETH10G ODU4 LCK LF
OTM2 ODU4 LCK ODU2 AIS
p1 (100G OCLD) LOS, LOC, LOF, OC192/STM64 OTU4 BDI, ODU4 BDI AIS-L
LOMF, OTU PreFEC-SF ETH10G OTU4 BDI, ODU4 BDI LF
OTM2 OTU4 BDI, ODU4 BDI ODU2 AIS
p1 (100G OCLD) ODU AIS, ODU LCK, OC192/STM64 ODU4 BDI AIS-L
ODU OCI ETH10G ODU4 BDI LF
OTM2 ODU4 BDI ODU2 AIS
p1 (100G OCLD) OPU AIS OC192/STM64 No conditioning AIS-L

ETH10G No conditioning LF
OTM2 No conditioning ODU2 AIS
p1-10 (10x10GE MUX/10x10G MUX) OC192/STM64 No conditioning AIS-L

OTM2 OPU2 PT Mismatch ETH10G No conditioning LF
OTM2 No conditioning No conditioning
p1-10 (10x10G MUX) WAN Link Down WAN No conditioning LF
p1-10 (10x10G MUX) WAN Loss of WAN No conditioning LF

Frame Delineation


10x10GE MUX, 10x10G MUX, 100G WaveLogic 3 OCLD, Flex2 WaveLogic 3 OCLD, and 100G
OCLD signal conditioning—optical muxponder configuration
Condition 10x10GE 100G OCLD/100G 10x10GE

MUX/10x10G WaveLogic 3 MUX/10x10G MUX
MUX OCLD/Flex2 p1-10 (client)
p1-10 Facility WaveLogic 3 OCLD Signal Output
p1 (OTM4) (Laser off if LOFEF
p1-10 (10x10GE MUX/10x10G MUX) ETH10G OPU2 AIS No conditioning

HiBER
p1-10 (10x10GE MUX/10x10G MUX) OC192/STM64 ODU2 LCK AIS-L

Facility OOS ETH10G ODU2 LCK LF
p1-10 (10x10G MUX) ODU AIS, ODU OTM2 ODU2 AIS, ODU2 No conditioning
LCK, ODU OCI (onramp, at OTM2 LCK, ODU2 OCI
client facility Rx)
p1-10 (10x10GE MUX/10x10G MUX) OC192/STM64 OC192/STM64: p1-10 OC192/STM64:

ODU AIS, ODU LCK, ODU OCI ETH10G = ODU2 BDI p1-10 = AIS-L
(offramp, at OTM2 layer facility) OTM2 ETH10G: p1-10 = ETH10G: p1-10 = LF
ODU2 BDI OTM2: p1-10 = No
OTM2: p1-10 = No conditioning (laser
conditioning off, See Note
p1-10 (10x10GE MUX/10x10G MUX) OC192/STM64 OPU2 AIS No conditioning

LOS, LOC, LOF ETH10G OPU2 AIS No conditioning
LOMF (OTM2 client)
OTM2 ODU2 AIS OTU2 BDI
p1-10 (10x10G MUX) Pre-FEC SF OTM2 ODU2 AIS OTU2 BDI
Service-affecting Circuit Pack Fail OC192/STM64 ODU4 AIS AIS-L

ETH10G ODU4 AIS LF
OTM2 ODU4 AIS ODU2 AIS
Note: There is no conditioning unless LOFEF is enabled; in which case, the laser is turned off.

Optical transponder configuration (100GE OCI, 100G WaveLogic 3 OCLD,

and 100G OCLD)
The following signal conditioning is applied for the 100GE OCI,100G
WaveLogic 3 OCLD, and 100G OCLD circuit packs in optical transponder
configuration.
Table 1-10
100GE OCI, 100G WaveLogic 3 OCLD, and 100G OCLD signal conditioning—optical transponder
configuration
Condition 100GE OCI 100G OCLD/100G 100GE OCI (client)

p1 (OTM4) WaveLogic 3 OCLD Signal Output
Facility p1 (OTM4) (Laser off if LOFEF
No Transponder Connection ETH100G ODU4 OCI LF
p1 (100GE OCI and 100G OCLD) ETH100G ODU4 LCK LF

Facility OOS
p1 (100GE OCI and 100G OCLD) ETH100G OTU4 BDI, ODU4 BDI LF
OCLD LOS, LOC, LOF, LOMF, OTU
PreFEC-SF
p1 (100GE OCI) ODU AIS, ODU LCK, ETH100G ODU4 BDI LF

ODU OCI
p1 (100GE OCI) OPU4 CFS ETH100G No conditioning LF
p1 (100GE OCI) LOS, LOC, LOF, ETH100G OPU4 CSF No conditioning

HiBER
Service-affecting Circuit Pack Fail ETH100G ODU4 AIS LF

OTR configuration (100G OCI,100G WaveLogic 3 OCLD, Flex2

WaveLogic 3 OCLD, and 100G OCLD)
The following signal conditioning is applied for the 100G OCI, 100G
WaveLogic 3 OCLD, Flex2 WaveLogic 3 OCLD, and 100G OCLD OTR circuit
packs.
Table 1-11
100G OCI, 100G WaveLogic 3 OCLD, Flex2 WaveLogic 3 OCLD, and 100G OCLD signal
conditioning—OTR configuration
Condition 100G OCI P1 100G OCLD/100G 100G OCI p1 Signal

WaveLogic 3 OCLD/ Output (Laser off if
Flex2 WaveLogic 3 LOFEF enabled)
OCLD p1 Signal Output
No Transponder Connection OTM4 ODU OCI ODU OCI
p1 (100G OCLD) Facility OOS OTM4 ODU LCK ODU LCK
p1 (100G OCLD) LOS, LOC, LOF, OTM4 OTU BDI ODU AIS
LOMF, OTU PreFEC-SF
OCLD CP MISSING OTM4 No conditioning ODU AIS
100G OCLD ODU AIS, ODU LCK, OTM4 No conditioning ODU AIS, ODU LCK,
ODU OCI ODU OCI, see Note
P1 (OCI) Facility OOS OTM4 ODU LCK ODU LCK
P1 (OCI) LOS, LOF, LOMF, OTU OTM4 ODU AIS OTU BDI
PreFEC-SF
OCI CP MISSING OTM4 ODU AIS No conditioning
P1 (OCI) ODU AIS, ODU LCK, OTM4 ODU AIS, ODU LCK, No conditioning
ODU OCI ODU OCI
No Transponder Connection ETH100G ODU OCI LF
p1 (100G OCLD) Facility OOS ETH100G ODU LCK LF
p1 (100G OCLD) LOS, LOC, ETH100G OTU BDI, ODU BDI LF

LOMF, OTU PreFEC-SF
100G OCLD ODU AIS, ODU LCK, ETH100G ODU BDI LF

ODU AIS
p1 (100G OCLD) OPU CSF, PTM ETH100G No conditioning LF


100G OCI, 100G WaveLogic 3 OCLD, Flex2 WaveLogic 3 OCLD, and 100G OCLD signal
conditioning—OTR configuration
Condition 100G OCI P1 100G OCLD/100G 100G OCI p1 Signal

WaveLogic 3 OCLD/ Output (Laser off if
Flex2 WaveLogic 3 LOFEF enabled)
OCLD p1 Signal Output
P1 (OCI) Facility OOS ETH100G ODU LCK LF
P1 (OCI) LOS, LOC, LOF, HiBER ETH100G OPU CSF RF
Note: No RF conditioning on 100G OCI Tx when LOS is received.
Optical Regen configuration (100G OCLD and 100G WaveLogic 3 OCLD)

The following signal conditioning is applied for the 100G OCLD and 100G
WaveLogic 3 OCLD circuit packs in optical regen configuration.
Table 1-12
100G OCLD and 100G WaveLogic 3 OCLD signal conditioning—optical Regen configuration
Condition 100G OCLD/100G WaveLogic 3 Facility

OCLD p1 (OTM4)
Signal Output
No Transponder Connection ODU OCI p1 (left mate)

ODU OCI p1 (right mate)
Left slot service-affecting Circuit Pack Fail ODU AIS p1 (left mate)
ODU AIS p1 (right mate)
Left slot p1 Facility OOS ODU LCK p1 (left mate)

ODU LCK p1 (right mate)
Left slot p1 LOS, LOF, LOMF, PreFFEC OTU BDI p1 (left mate)
SF ODU AIS p1 (right mate)
Right slot service-affecting Circuit Pack ODU AIS p1 (left mate)

Fail ODU AIS p1 (right mate)
Right slot p1 Facility OOS ODU LCK p1 (left mate)

ODU LCK p1 (right mate)
Right slot p1 LOS, LOF, LOMF, PreFFEC ODU AIS p1 (left mate)
SF OTU BDI p1 (right mate)

Signal conditioning for 2x10G OTR 4x10-11.3G XFP and 4x10G OTR
circuit packs
Terminal configuration
The following signal conditioning is applied for the 2x10G OTR and 4x10G
OTR circuit packs in terminal configuration.
Note that when FLEX Facilities are set to OOS, the client laser is shutdown
irrespective of the LOFEF or TXCON settings (not applicable to FC800 or
FC1200).
Attention: No conditioning is done for Ethernet when the client receives a

Local Fault or a Remote Fault condition.
For the 2x10GOTR circuit pack, the client ports are ports 2 and 4 and the Line
ports are ports 1 and 3.
The 4x10G OTR 8xXFP (NTK530QM) circuit pack implements a different port
association between ULL equipment mode and OTR equipment mode. The
port associations are 1-5, 2-6, 3-7, 4-8 for OTR equipment mode and 1-2, 3-4,
5-6, 7-8 for ULL equipment mode. For the 4x10G OTR 4xXFP/4xSFP+
(NTK530QA) circuit pack, port associations are 1-5, 2-6, 3-7, 4-8 for both the
OTR equipment mode and the ULL equipment mode.

Table 1-13
2x10G OTR and 4x10G OTR signal conditioning—terminal configuration
Trigger Condition Client Port Line Port Conditioning Client Port

(Laser off is LOFEF Conditioning
enabled) (Laser off is LOFEF
enabled)
No client port facility UAS ODU OCI Laser Off
Line port facility OOS OC192 ODU LCK (P-UEQ for AIS-L
4x10G OTR)
OC-192 Hairpin AIS-L
ETH10G (10.7) LF
ETH10G (11.05) LF
See Note 1
ETH10G (11.09) LF
ETH10G Hairpin LF
ETH10G ULL LF
OTM2 ODU LCK

See Note 2
Port 1/3 (for 2x10G OTR) OC192 OTU BDI, RFI-L AIS-L
Port 5/6/7/8 (for 4x10G OTR) OTU BDI (laser off does AIS-L
LOS/LOF/LOMF/OTU SF OC-192 Hairpin
not apply)
ETH10G (10.7) LF
ETH10G (11.05) LF
See Note 1
ETH10G (11.09) LF
ETH10G Hairpin LF
ETH10G ULL LF
OTM2 ODU AIS

See Note 2



enabled)
Port 1/3 (for 2x10G OTR) OC192 ODU BDI, RFI-L (laser AIS-L
Port 5/6/7/8 (for 4x10G OTR) off does not apply)
ODU AIS/ODU LCK/ OC-192 Hairpin AIS-L
None
ODU OCI ETH10G (10.7) LF
ETH10G (11.05) LF
See Note 1
ETH10G (11.09) LF
ETH10G Hairpin LF
ETH10G ULL LF
OTM2 None
See Note 2
Port 2/4 (for 2x10G OTR) OC192 None AIS-L

Port 1/2/3/4 (for 4x10G OTR)
OPU AIS OC-192 Hairpin AIS-L
See Note 3 ETH10G (10.7) LF
ETH10G (11.05) LF
See Note 1
ETH10G (11.09) LF
ETH10G Hairpin LF
ETH10G ULL LF
OTM2 None
See Note 2



enabled)
Port 2/4 (for 2x10G OTR) OC192 None AIS-L

OTM2 OPU2 PT Mismatch OC-192 Hairpin AIS-L
See Note 3 ETH10G (10.7) LF
ETH10G (11.05) LF
See Note 1
ETH10G (11.09) LF
ETH10G Hairpin LF
ETH10G ULL LF
OTM2 None
See Note 2
Port 2/4 (for 2x10G OTR) WAN None LF

(WAN) Link Down
Port 2/4 (for 2x10G OTR) WAN None LF

(WAN) Loss of Frame
Delineation
Port 2/4 (for 2x10G OTR) ETH10G (10.7) P-AIS RF (2x10G OTR only)
EBER ETH10G (11.05) None
See Note 1
ETH10G (11.09) None
ETH10G Hairpin LF
ETH10G ULL LF



enabled)
Port 2/4 (for 2x10G OTR) OC192 ODU LCK AIS-L

facility OOS OC-192 Hairpin AIS-L
ETH10G (10.7) LF
ETH10G (11.05) LF
See Note 1
ETH10G (11.09) LF
ETH10G Hairpin LF
ETH10G ULL LF
OTM2 ODU LCK

See Note 2
Port 2/4 (for 2x10G OTR) OC192 OPU AIS None

Port 1/2/3/4 (for 4x10G OTR) See Note 5
LOS/LOF/LOMF OC-192 Hairpin AIS-L
ODU AIS
ETH10G (10.7) For NTK530PAE5:
RF (GFP only) (laser off
does not apply)
For NTK530PGE5 and
NTK530PME5:
None
ETH10G (11.05) None

See Note 1
ETH10G (11.09) None
ETH10G Hairpin LF
ETH10G ULL LF
OTM2 OTU BDI (laser off does

See Note 2 not apply)
Port 2/4 (for 2x10G OTR) OTM2 ODU AIS OTU BDI (laser off does
Port 1/2/3/4 (for 4x10G OTR) See Note 2 not apply)
Pre-FEC SF



enabled)
Service affecting circuit pack OC192 ODU AIS AIS-L

fail
OC-192 Hairpin AIS-L
ETH10G (10.7) LF
ETH10G (11.05) LF
See Note 1
ETH10G (11.09) LF
ETH10G Hairpin LF
ETH10G ULL LF
OTM2 ODU AIS

See Note 2
Port 2/4 (for 2x10G OTR) OC192 None Laser off

DWDM XFP pluggable fail OC-192 Hairpin
ETH10G (10.7)
ETH10G (11.05)
See Note 1
ETH10G (11.09)
ETH10G Hairpin
ETH10G ULL
OTM2
See Note 2



enabled)
Port 1/3 (for 2x10G OTR) OC192 Laser off None

DWDM XFP pluggable fail OC-192 Hairpin
ETH10G (10.7)
ETH10G (11.05)
See Note 1
ETH10G (11.09)
ETH10G Hairpin
ETH10G ULL
OTM2
See Note 2
Note 1: Not supported on the 4x10G OTR circuit packs.

Note 2: Not supported on the client ports (1,2,3,4) of the NTK530QA 4x10G OTR circuit packs.
Note 3: By default, these faults received from the line facing equipment will be alarmed against the
OTM2 layer facility on P2/P4 as the ODU monitor flag is enabled by default for P2/P4. The ODU monitor
flag can be changed to enabled on the OTM2 facility on P1/P3 and the alarm can be seen at these ports.
Note 4: Any conditioning that is not explicitly identified in the table, should not be assumed.
Note 5: In the special case of a 10GE to GFP to STS192c to OPU2 mapping a P-AIS would be
conditioned instead of an OPU AIS.

Regenerator configuration
The following signal conditioning is applied for the 2x10G OTR and 4x10G
OTR (NTK530QM variant only) circuit packs in regenerator configuration.
Table 1-14
2x10G OTR and 4x10G OTR (NTK530QM variant only) signal conditioning—regen configuration
Trigger Condition Conditioning
Port 1/3 (for 2x10G OTR) Port 2/4 (for 2x10G OTR)
Port 1/2/3/4 (for 4x10G OTR) Port 1/2/3/4 (for 4x10G OTR)
Service affecting circuit pack fail ODU AIS ODU AIS
Port 1/3 (for 2x10G OTR) ODU LCK ODU LCK

facility OOS
Port 1/3 (for 2x10G OTR) OTU BDI ODU AIS

LOS/LOF/LOMF/OTU SF
Port 2/4 (for 2x10G OTR) ODU LCK ODU LCK

facility OOS
Port 2/4 (for 2x10G OTR) ODU AIS OTU BDI

LOS/LOF/LOMF/OTU SF

Signal conditioning for FC400/FC800/FC1200 (applicable to 2x10G

OTR (NTK530PME5), 4x10G OTR, the 4x10G MUX (NTK525CFE5), and
the 10x10G MUX (NTK529BAE5/NTK529BBE5))
The following signal conditioning is applied for FC400/FC800 and FC1200.
FC400 applies to the 4x10G OTR NTK530QA variant only.
Table 1-15
FC800 and FC1200 signal conditioning
Trigger Condition FC400/FC800 Signal FC1200 Signal Conditioning

Conditioning
TXCOND = TXCOND= TXCOND= LF TXCOND=

NOS LOFEF LOFEF
OTU LOS, OTU LOF, OTU LOMF or Egress from Client Laser Egress from Client Laser Off
pre-FEC SF detected on ingress of Client Port: Off Client Port: LF
corresponding OTM2/OTM3/OTM4 NOS
line facility
Corresponding OTM2/OTM3/OTM4 Egress from Client Laser Egress from Client Laser Off
line facility is put out-of-service Client Port: Off Client Port: LF
NOS
ODU AIS, ODU LCK, ODU OCI, Egress from Client Laser Egress from Client Laser Off
OPU AIS or OPU PT Mismatch Client Port: Off Client Port: LF
detected from the connection facing NOS
direction of a corresponding OTM2
layer facility
Client (FLEX) facility is put Egress from Client Laser Egress from Client Laser Off
out-of-service Client Port: Off Client Port: LF
NOS
ODU LCK in the connection facing direction of the corresponding

OTM2 layer facility
LOS, LOC, or Loss of Data Synch OPU AIS in the connection N/A
detected on ingress of an facing direction of the
FC400/FC800 client (FLEX) facility corresponding OTM2 layer
facility
NOS or OLS detected on ingress of Passed transparently through N/A

an FC400/FC800 client (FLEX) the corresponding OTM2
facility line/layer facility in the Tx
direction
NOS or OLS detected on ingress of Passed transparently through N/A

corresponding OTM2 line/layer the corresponding
facility FC400/FC800 client facility in
the Tx direction


FC800 and FC1200 signal conditioning
Trigger Condition FC400/FC800 Signal FC1200 Signal Conditioning

Conditioning
TXCOND = TXCOND= TXCOND= LF TXCOND=

NOS LOFEF LOFEF
LOS, LOC, LOF, EBER detected on N/A OPU AIS in the connection
ingress of an FC1200 client (FLEX) facing direction of the
facility corresponding OTM2 layer
facility
LF or RF detected on ingress of an N/A Passed transparently through

FC1200 client (FLEX) facility the corresponding OTM2
line/layer facility in the Tx
direction
LF or RF detected on ingress of N/A Passed transparently through

corresponding OTM2 line/layer the corresponding FC1200 client
facility facility in the Tx direction

Signal conditioning for 5G IBM PSIFB on 2x10GOTR (NTK530PME5

variant only) and 5G IBM PSIFB or ISC3 on 4x10G OTR (NTK530QA
variant only)
The following signal conditioning is applied to 5G IBM PSIFB on the
2x10G OTR, and 5G IBM PSIFB or ISC3 on the 4x10G OTR.
Table 1-16
5G IBM PSIFB on 2x10GOTR (NTK530PME5 variant only) and 5G IBM PSIFB or ISC3 on 4x10G
OTR (NTK530QA variant only) signal conditioning
Trigger Condition Signal Conditioning
OOS, OTU LOS, OTU LOF, OTU LOMF or Egress from the client port: client facility laser is shutoff
pre-FEC SF detected on ingress of See Note 1
corresponding OTM2 line facility
ODU AIS, ODU LCK, ODU OCI, OPU AIS or Egress from the client port: client facility laser is shutoff
OPU PT Mismatch detected from the See Note 1
connection facing direction of a
corresponding OTM2 layer facility
LOF or LOC detected on ingress of a client OPU AIS in the connection facing direction of the
facility. See Note 2 corresponding OTM2 layer facility
Client facility is put out-of-service ODU LCK in the connection facing direction of the
corresponding OTM2 layer facility
Client facility is put out-of-service Egress from the client port: client facility laser is shutoff
See Note 1
K30.7 signal conditioning detected on ingress Passed transparently through the corresponding OTM2
of a client facility line facility in the Tx direction
K30.7 signal conditioning detected on ingress Passed transparently through the corresponding client
of corresponding OTM2 line facility facility in the Tx direction
Note 1: The client facility laser is shutoff when LOFEF is enabled.

Note 2: LOC is not supported on the 4x10G OTR circuit packs.

Signal conditioning for 10GEL WT circuit packs

10GEL WT OTM2 port 1 trigger
The following signal conditioning is applied for OTM2 port 1 triggered events.
For a list of abbreviations used in the following tables, see “Abbreviations used
in this chapter” in the Alarm clearing procedures chapters of this document.
Table 1-17
10GEL WT signal conditioning—OTM2 port 1 trigger
OTM2 p1 Facility OOS OTM2 p1 ODU2 AIS OTM2 p1

802.3 LF – LOFEF Off ETH10G p2
Laser Off – LOFEF On ETH10G p2
OTM2 p1 Rx ODU2 AIS OTM2 p1 ODU2 BDI OTM2 p1


(OPU2 PN11 condition is not 802.3 LF – LOFEF Off ETH10G p2
alarmed)
LOMF or Pre-FEC Signal Fail 802.3 LF – LOFEF Off ETH10G p2
OTM2 p1 Rx OTU2 or ODU2 BDI OTM2 p1 No conditioning n/a

10GEL WT ETH10G port 2 trigger

The following signal conditioning is applied for ETH10G port 2 triggered
events.
Table 1-18
10GEL WT signal conditioning—ETH10G port 2 trigger
ETH10G p2 LOS or LOF ETH10G p2 OPU2 PN11 OTM2 p1

No conditioning ETH10G p2
ETH10G p2 Facility OOS ETH10G p2 OPU2 PN11 OTM2 p1

ETH10G p2 Rx Local Fault or ETH10G p2 No conditioning (Transparent) OTM2 p1

Remote Fault No conditioning ETH10G p2
ETH10G p2 Rx Power Out of ETH10G p2 No conditioning OTM2 p1

Range No conditioning ETH10G p2
10GEL WT circuit pack equipment failure

The following signal conditioning is applied for Circuit Pack or Pluggable
Failure conditions where traffic is affected.
Table 1-19
10GEL WT signal conditioning—circuit pack equipment failure
Circuit Pack Fail OTM2 p1 ODU2 AIS OTM2 p1

Local Fault – LOFEF Off ETH10G p2
Pluggable Fail ETH10G p2 OPU2 PN11 OTM2 p1

Local Fault – LOFEF Off ETH10G p2

Signal conditioning for 10G OC-192/STM-64 WT circuit packs

10G OC-192/STM-64 WT OTM2 port 1 trigger
Table 1-20
10G OC-192/STM-64 WT signal conditioning—OTM2 port 1 trigger

Line/MS AIS – LOFEF Off OC192/STM64 p2
Laser Off – LOFEF On OC192/STM64 p2
OTM2 p1 Rx ODU2 AIS OTM2 p1 ODU2 BDI OTM2 p1


(OPU2 PN11 condition is not Line/MS AIS – LOFEF Off OC192/STM64 p2
alarmed)
LOMF or Pre-FEC Signal Fail Line/MS AIS – LOFEF Off OC192/STM64 p2
OTM2 p1 Rx OTU2 or ODU2 BDI OTM2 p1 No conditioning OTM2 p1

No conditioning OC192/STM64 p2

10G OC-192/STM-64 WT OC192/STM64 port 2 trigger

The following signal conditioning is applied for OC192/STM64 port 2 triggered
events.
Table 1-21
10G OC-192/STM-64 WT signal conditioning—OC192/STM64 port 2 trigger
OC192/STM64 p2 LOS or OC192/STM64 p2 OPU2 PN11 OTM2 p1

LOF No conditioning OC192/STM64 p2
OC192/STM64 p2 Facility OC192/STM64 p2 OPU2 PN11 OTM2 p1

OOS Line/MS AIS – LOFEF Off OC192/STM64 p2
OC192/STM64 p2 Rx SF, OC192/STM64 p2 No conditioning (Transparent) OTM2 p1

AIS, RFI or RDI No conditioning OC192/STM64 p2
OC192/STM64 p2 Rx Power OC192/STM64 p2 No conditioning OTM2 p1

Out of Range No conditioning OC192/STM64 p2
10G OC-192/STM-64 WT circuit pack equipment failure

Table 1-22
10G OC-192/STM-64 WT signal conditioning—circuit pack equipment failure

Pluggable Fail OC192/STM64 p2 OPU2 PN11 OTM2 p1


Signal conditioning for 10G OTU2 WT circuit packs

10G OTU2 WT OTM2 port 1 trigger
Table 1-23
10G OTU2 WT signal conditioning—OTM2 port 1 trigger

ODU2 AIS – LOFEF Off OTM2 p2
Laser Off – LOFEF On OTM2 p2
OTM2 p1 Rx ODU2 AIS OTM2 p1 No conditioning OTM2 p1

OTM2 p1 Rx OPU2 PN11 or OTM2 p1 No conditioning OTM2 p1

ODU2 BDI No conditioning OTM2 p2
(OPU2 PN11 condition is not (transparent)
alarmed)
OTM2 p1 Rx OTU2 LOS, LOF, OTM2 p1 OTU2 BDI OTM2 p1

LOMF or Pre-FEC Signal Fail ODU2 AIS – LOFEF Off OTM2 p2
10G OTU2 WT OTM2 port 2 trigger

Table 1-24
OTM2 p2 LOS, LOF or LOMF OTM2 p2 ODU2 AIS OTM2 p1

No conditioning OTM2 p2



OTM2 p2 Rx OTU BDI OTM2 p2 No conditioning OTM2 p1

OTM2 p2 Rx OPU2 PN11, OTM2 p2 No conditioning (transparent) OTM2 p1

ODU2 BDI or ODU2 AIS No conditioning OTM2 p2
(OPU2 PN11 condition is not
alarmed)
OTM2 p2 Rx Power Out of OTM2 p2 No conditioning OTM2 p1

Range No conditioning OTM2 p2
10G OTU2 WT circuit pack equipment failure

Table 1-25
10G OTU2 WT signal conditioning—circuit pack equipment failure

Pluggable Fail OTM2 p2 ODU2 AIS OTM2 p1

Signal conditioning for 10G OTR

Signal conditioning for the 10G OTR circuit pack is the same as signal
conditioning applied for the 10G OTSC circuit pack in standalone
configuration. However, the FC1200 facility is not supported on the 10G OTR
circuit pack. Refer to “Signal conditioning for 10G OTSC circuit packs” on page
1-57.

Signal conditioning for 10G OTSC circuit packs

10G OTSC standalone configuration
The following signal conditioning is applied for the 10G OTSC circuit pack in
standalone configuration.
Table 1-26
10G OTSC signal conditioning—standalone configuration
Condition p2 Facility p1 (OTM2) p2 (client)

Signal Output Signal Output
(Laser off if LOFEF
enabled)
Connection is down OC192/STM64 ODU OCI AIS-L

ETH10G ODU OCI LF
FC1200 ODU OCI LF
OTM2 ODU OCI ODU OCI
p1 Facility OOS OC192/STM64 ODU LCK AIS-L

ETH10G ODU LCK LF
FC1200 ODU LCK LF
OTM2 ODU LCK ODU LCK
p1 LOS, LOF, LOMF, OTU SF OC192/STM64 OTU BDI, ODU BDI AIS-L
ETH10G OTU BDI, ODU BDI LF
FC1200 OTU BDI, ODU BDI LF
OTM2 OTU BDI ODU AIS
p1 ODU AIS, ODU LCK, ODU OCI OC192/STM64 ODU BDI AIS-L
ETH10G ODU BDI LF
FC1200 ODU BDI LF
OTM2 No conditioning (Note 1) No conditioning (laser
off)
p1 OPU AIS OC192/STM64 No conditioning AIS-L

ETH10G No conditioning LF
off)


10G OTSC signal conditioning—standalone configuration
Condition p2 Facility p1 (OTM2) p2 (client)

Signal Output Signal Output
(Laser off if LOFEF
enabled)
p1 OTM2 OPU2 PT Mismatch OC192/STM64 No conditioning AIS-L

ETH10G No conditioning LF (GFP only)
FC1200 No conditioning No conditioning
off)
p2 (WAN) UPI Mismatch WAN No conditioning No conditioning
p2 (WAN) Link Down WAN No conditioning LF
p2 (WAN) Loss of Frame Delineation WAN No conditioning LF
p2 HiBER ETH10G OPU AIS RF (GFP only) (Note 2)

FC1200 OPU AIS No conditioning
p2 Facility OOS OC192/STM64 ODU LCK AIS-L

ETH10G ODU LCK LF
FC1200 ODU LCK LF
OTM2 ODU LCK ODU LCK
p2 ODU AIS, ODU LCK, ODU OCI OTM2 No conditioning (Note 1) No conditioning (laser
off)
p2 LOS, LOF OC192/STM64 OPU AIS No conditioning

LOMF (OTM2 client) ETH10G OPU AIS RF (GFP only) (Note 2)
FC1200 OPU AIS No conditioning
OTM2 ODU AIS OTU BDI
p2 Pre-FEC SF OTM2 ODU AIS OTU BDI
Service-affecting Circuit Pack Fail OC192/STM64 ODU AIS AIS-L

ETH10G ODU AIS LF
FC1200 ODU AIS LF
OTM2 ODU AIS ODU AIS
Note 2: No RF conditioning occurs when operating in 11.05 and 11.09 proportional wrap. Conditioning
only occurs when operating in GFP mode.

10G OTSC 1+1 configuration

The following signal conditioning is applied for the 10G OTSC 1+1
configuration.
Table 1-27
10G OTSC signal conditioning—1+1 configuration
Trigger condition Tx conditioning
Working circuit pack (WC) Protection circuit pack (PC)
Signal Output Facility Signal Output Facility
Service-affecting conditions
Connection down ODU OCI p1 ODU OCI p1

Yes (Note) p2
WC p2 Facility OOS ODU LCK p1 ODU LCK p1

Yes (Note) p2
WC p2 LOS, LOF, LOMF, pre-FEC SF, OPU AIS p1 OPU AIS p1

HiBER ODU AIS p1 ODU AIS p1
(OTM2 client) (OTM2 client)
Yes (Note) p2
WC service-affecting Circuit Pack Fail ODU AIS p1 ODU AIS p1

Yes (Note) p2
WC p1 Facility OOS, PC p1 Facility OOS ODU LCK p1 ODU LCK p1

Yes (Note) p2
WC and PC p1 LOS, LOF, LOMF, OTU ODU BDI, OTU BDI p1 ODU BDI, OTU BDI p1
SF Yes (Note) p2
(non-OTM2 client)
WC and PC p1 LOS, LOF, LOMF, OTU OTU BDI p1 OTU BDI p1

SF Yes (Note) p2
(OTM2 client)
WC and PC p1 ODU AIS, ODU LCK, ODU BDI p1 ODU BDI p1

ODU OCI (non-OTM2 Client) Yes (Note) p2
WC and PC p1 ODU AIS, ODU LCK, No conditioning p1 No conditioning p1

ODU OCI No conditioning p2
(OTM2 client)
WC and PC p1 OPU AIS No conditioning p1 No conditioning p1

(non-OTM2 client) Yes (Note) p2


WC and PC p1 OPU AIS (OTM2 client) No conditioning p1 No conditioning p1

No conditioning p2
WC p2 (WAN) UPI Mismatch No conditioning p1 No conditioning p1

No conditioning p2
WC p1 OPU2 PT Mismatch No conditioning p1 No conditioning p1

Yes (Note) p2
Non-service-affecting conditions
WC p1 Facility OOS ODU LCK p1 No conditioning p1

No conditioning p2
WC p1 LOS, LOF, LOMF, OTU SF ODU BDI, OTU BDI p1 No conditioning p1

(non-OTM2 client) No conditioning p2
WC p1 LOS, LOF, LOMF, OTU SF OTU BDI p1 No conditioning p1

(OTM2 client) No conditioning p2
WC p1 ODU AIS, ODU LCK, ODU OCI ODU BDI p1 No conditioning p1

WC p1 ODU AIS, ODU LCK, ODU OCI No conditioning p1 No conditioning p1

WC p1 OPU AIS No conditioning p1 No conditioning p1

WC p1 OPU AIS No conditioning p1 No conditioning p1

PC p1 Facility OOS No conditioning p1 ODU LCK p1

No conditioning p2
PC p1 LOS, LOF, LOMF, OTU SF No conditioning p1 ODU BDI, OTU BDI p1

(WC non-OTM2 client) No conditioning p2
PC p1 LOS, LOF, LOMF, OTU SF No conditioning p1 OTU BDI p1

(WC OTM2 client) No conditioning p2


PC p1 ODU AIS, ODU LCK, ODU OCI No conditioning p1 ODU BDI p1

PC p1 ODU AIS, ODU LCK, ODU OCI No conditioning p1 No conditioning p1

PC p1 OPU AIS No conditioning p1 No conditioning p1

PC p1 OPU AIS No conditioning p1 No conditioning p1

Note: Yes indicates that p2 conditioning is as per the 10G OTSC standalone configuration
p2 conditioning. Refer to Table 1-26 on page 1-57.
10G OTSC Regenerator configuration

The following signal conditioning is applied for the 10G OTSC regen
configuration.
.
Table 1-28
10G OTSC signal conditioning—regen configuration
Trigger Condition Tx conditioning
Signal Output Facility
Connection is down ODU OCI p1 (odd slot)

ODU OCI p1 (even slot)
Odd slot service-affecting Circuit Pack Fail ODU AIS p1 (odd slot)
ODU AIS p1 (even slot)
Odd slot p1 Facility OOS ODU LCK p1 (odd slot)

ODU LCK p1 (even slot)
Odd slot p1 LOS, LOF, LOMF, OTU SF OTU BDI p1 (odd slot)
ODU AIS (odd slot) p1 (even slot)


10G OTSC signal conditioning—regen configuration
Trigger Condition Tx conditioning
Signal Output Facility
Even slot service-affecting Circuit Pack Fail ODU AIS p1 (odd slot)
ODU AIS p1 (even slot)
Even slot p1 Facility OOS ODU LCK p1 (odd slot)

ODU LCK p1 (even slot)
Even slot p1 LOS, LOF, LOMF, OTU SF ODU AIS p1 (odd slot)
OTU BDI p1 (even slot)
Signal conditioning for 2.5G MOTR circuit packs

2.5G MOTR OTM2 port 1 trigger
Table 1-29
2.5G MOTR signal conditioning—OTM2 port 1 trigger
OTM2 p1 Facility OOS OTM2 p1 ODU2 LCK OTM2 p1
ODU1 AIS OTM1 p2-p5
Line/MS AIS OC48/STM16 p2-p5
OTM2 p1 Rx ODU2 AIS, LCK or OTM2 p1 ODU2 BDI OTM2 p1

OCI
ODU1 AIS OTM1 p2-p5
OTM2 p1 Rx OTU2 BDI or ODU2 OTM2 p1 No conditioning OTM2 p1

BDI
No conditioning OTM1 p2-p5
No conditioning OC48/STM16 p2-p5
LOMF, or AIS
ODU1 AIS OTM1 p2-p5


2.5G MOTR signal conditioning—OTM2 port 1 trigger
OTM1 p1 Rx OPU1 PN11 Not user No conditioning OTM2 p1

visible
(Transparent)
OTM1 p1 Rx ODU1 AIS, LCK or Not user No conditioning OTM2 p1

OCI visible
(Transparent)
OTM2 p1 Rx OTU Signal OTM2 p1 No conditioning OTM2 p1

Degrade
2.5G MOTR OC48/STM16 port 2 to 5 trigger

The following signal conditioning is applied for OC48/STM16 port 2-5
triggered events.
Table 1-30
2.5G MOTR signal conditioning—OC48/STM16 or OTU1 port 2-5 trigger
OC48/STM16 p2-p5 LOS OC48/STM16 p2-p5 OPU1 PN11 OTM2 p1

or LOF
OC48/STM16 p2-p5 OC48/STM16 p2-p5 ODU1 LCK OTM2 p1

Facility OOS
OC48/STM16 p2-p5 Rx OC48/STM16 p2-p5 No conditioning (Transparent) OTM2 p1

SF, AIS, RFI or RDI
OC48/STM16 p2-p5 Rx OC48/STM16 p2-p5 No conditioning OTM2 p1

Power Out of Range


2.5G MOTR signal conditioning—OC48/STM16 or OTU1 port 2-5 trigger
OTU1 p2-p5 LOS, LOF or OTM1 p2-p5 OTU BDI OTM1 p2-p5
OTU1 AIS
ODU1 AIS OTM2 p1
OTU1 p2-p5 Facility OOS OTM1 p2-p5 ODU1 LCK OTM1 p2-p5
ODU1 LCK OTM2 p1
OTU1 p2-p5 Rx ODU1 OTM1 p2-p5 No conditioning OTM1 p2-p5

AIS, LCK or OCI
No conditioning (Transparent) OTM2 p1
OTU1 p2-p5 Rx OTU1 BDI OTM1 p2-p5 No conditioning OTM1 p2-p5

or ODU1 BDI
OTU1 p2-p5 Rx Power OTM1 p2-p5 No conditioning OTM1 p2-p5

Out of Range

2.5G MOTR circuit pack equipment failure

Table 1-31
2.5G MOTR signal conditioning—circuit pack equipment failure
ODU1 AIS OTM1 p2-p5
Pluggable Fail OTM2 p1 ODU2 AIS OTM2 p1
ODU1 AIS OTM1 p2-p5
OTM1 p2-p5 ODU1 AIS OTM2 p1
ODU1 AIS OTM1 p2-p5
OC48/STM16 p2-p5 OPU1 PN11 OTM2 p1

Signal conditioning for FLEX MOTR (NTK531YA) circuit packs

Table 1-32
FLEX MOTR signal conditioning—OTM2 port 1 and 2 trigger
Condition Facility ETH10G OTM2 1+1 Connected Signal Output Facility
Provisioned/ Client
Client 1+1 treatment
Port TPT
Protection
See Note 2
OTM2 p1-p2 OTM2 p1-p2 No Switched to OTM2/ETH ODU2 LCK OTM2 p1-p2
Facility OOS conditioning Standby 10G
See Note 1 OTM2 conditioning
See Note 2
OTM2 p1-p2 OTM2 p1-p2 Remote Fault Switched to OTM2/ETH ODU2 BDI OTM2 p1-p2
Rx ODU2 AIS conditioning Standby 10G ETH10G
See Note 3 OTM2 conditioning conditioning
See Note 2
OTM2 p1-p2 OTM2 p1-p2 BDI Traffic No No OTM2 p1-p2

Rx OTU2 BDI No remain on the conditioning conditioning
conditioning Active OTM2 See Note 4
OTM2 p1-p2 OTM2 p1-p2 Remote Fault Switched to OTM2/ETH OTU2 BDI OTM2 p1-p2
Rx OTU2 LOS, conditioning Standby 10G and ODU2
LOF, LOMF, or See Note 3 OTM2 conditioning BDI, ETH10G
PreFEC SF See Note 2 conditioning


FLEX MOTR signal conditioning—OTM2 port 1 and 2 trigger
Condition Facility ETH10G OTM2 1+1 Connected Signal Output Facility
Provisioned/ Client
Client 1+1 treatment
Port TPT
Protection
See Note 2
OTM2 p1-p2 OTM2 p1-p2 No Switched to OTM2/ETH OTU2 SD OTM2 p1-p2

Rx OTU Signal conditioning Standby 10G alarm No
Degrade (SD OTM2 conditioning conditioning
conditioning) See Note 2 when FEC is
disabled
OTM2 p1-p2 OTM2 p1-p2 Remote Fault Switched to OTM2/ETH ODU2 BDI OTM2 p1-p2
Rx ODU2 OCI conditioning Standby 10G
See Note 2
Note 1: If the ETH10G is mapped into this OTM2 being placed OOS-MA, the Ethernet datapath is
disabled such that no L2 traffic can be carried in either direction on the endpoint
Note 2: The OTM2/ETH10G is the line side endpoint for any EVPL connection with a FLEX client (by
way of connections created with ENT-CRS-VCE) and all client facilities connected to this port will be
conditioned based on their TXCON and HOLDOFF attribute values. The HOLDOFF value of 100ms is
recommended for all TPT Protected services. For the TXCON attribute values, refer to chapter 1 of
Part 1 of Configuration - Provisioning and Operating, 323-1851-310.
Note 3: ETH10G is in a Rx Local Fault state which disables datapath in both directions and sends
Remote Fault to far-end.
Note 4: No FLEX client conditioning will occur if the OTM2/ETH10G line for this client receives a BDI.

Signal conditioning for 8xSFP OTN Flex MOTR (NTK532BA) and (1+8)
OTN Flex MOTR (NTK532DA) circuit packs
The following tables list the signal conditioning for the 8xSFP OTN Flex MOTR
and (1+8) OTN Flex MOTR circuit packs.
Table 1-33
8xSFP OTN Flex MOTR and (1+8) OTN Flex MOTR Tx Conditioning parameters
Tx conditioning parameter
Protocol Options Default
See Note 1 to Note 4
OC3 LOFEF AIS-L

OC12 AIS-L
OC48
STM1 LOEFEF MS-AIS

STM4 MS-AIS
STM16
SRM250G LOFEF AIS-L

ESRM250G AIS-L
1000Base-X LOEFEF LOFEF

1000Base-T 8B10B
K30_7
100Base-X LOEFEF LOEFEF
Fiber Channel 100 LOEFEF NOS

FICON 8B10B
NOS
Fiber Channel 200 LOEFEF NOS

FICON Express 8B10B
NOS
Fiber Channel 400 LOEEF NOS

FICON 4G 8B10B
NOS
IBM ISC-3 Peer Mode LOEEF LOEEF

1 Gbps and 2 Gbps 8B10B


8xSFP OTN Flex MOTR and (1+8) OTN Flex MOTR Tx Conditioning parameters
Tx conditioning parameter
Protocol Options Default
See Note 1 to Note 4
ESCON LOEEF 8B10B

8B10B
DVB-AIS LOEEF 8B10B

8B10B
Note 1: LOFEF is "Laser Off Far End Failure" and means the pluggable transmitter will be disabled
Note 2: 8B10B is an invalid 10B codeword as specified in G.7041 (sometimes referred to as 10B_ERR)
Note 3: K30_7 is the 802.3 specified Error Propagation signal /K30.7/
Note 4: NOS is the Fibre Channel defined "Not Operational" ordered set

Table 1-34
8xSFP OTN Flex MOTR and (1+8) OTN Flex MOTR Hold-off parameters
Hold-off Parameter (in ms)

Protocol Range Default Signal Output Recommended Setting for Protected
During Hold-0ff configurations
Unprotected 1+1 Line 1+1 Port TPT

See Note 1 See Note 2
and Note 5
OC3 0 to 0 AIS-L 0 100 100
OC12 1000 in
OC48 100
intervals
STM1 0 AIS-L 0 100 100
STM4
STM16
SRM250G 0 AIS-L 0 100 100

ESRM250G
1000Base-X 0 802.3 Idle 0 100 100

1000Base-T /l2/
100Base-X 0 PN11 0 100 100
Fiber Channel 100 100 Fibre Channel 100 100 100

FICON See Note 3 IDLE See Note 4

FICON Express See Note 3 IDLE See Note 4

FICON 4G See Note 3 IDLE See Note 4


8xSFP OTN Flex MOTR and (1+8) OTN Flex MOTR Hold-off parameters
Hold-off Parameter (in ms)

Protocol Range Default Signal Output Recommended Setting for Protected
During Hold-0ff configurations
Unprotected 1+1 Line 1+1 Port TPT

and Note 5
IBM ISC-3 Peer 0 to 0 8B10B 0 100 100
Mode 1000 in
(1 Gbps and 2 Gbps) 100
intervals
ESCON 0 8B10B 0 100 100
DVB-AIS 0 8B10B 0 100 100
Note 1: For a 1+1 Line protected client service, holdoff is set to 100ms to allow the protection switch to
complete without applying a Tx conditioning treatment to the client.
Note 2: During a protection switch for a 1+1 Port TPT protected client there is a brief period where the
transmitter is off on both ports. This may cause an interruption to be detected at the subtending device.
Note 3: The hold-off value for a FC interface is 100ms to align with FC standard R_T_TOV value in
order to provide a seamless transition during short failures, such as that of a protection switch.
Note 4: Unprotected Fibre Channel hold-off should be 0ms if the subtending FC switch is providing
protection.
Note 5: For a 1+1 Port TPT protected client service, the holdoff timer does not delay the system's ability
to disable/enable the transmitter during a switch. The holdoff timer will only have an impact in the case
that both paths are failed -- in which case the configured Tx Conditioning treatment is not applied until
the defect lasts longer than the holdoff timer.

Table 1-35
8xSFP OTN Flex MOTR (NTK532BA) (Port with Condition)
Trigger Port with Condition

Facility Condition Facility Signal Output 1+1 Line Protection
(toward line)
Line OTM1 p1-p4 Facility OTM1 p1-p4 ODU1 OCI N/A

Facility Unconnected
OTM1 p1-p4 Facility OTM1 p1-p4 Unconnected TS: N/A

Partially ODU0 OCI
Unconnected Connected TS: Traffic
See Note 1
OTM1 p1-p4 Facility OOS OTM1 p1-p4 ODU1 LCK Switch to standby
OTM1
OTM1 p1-p4 LOS, LOF, OTM1 p1-p4 Traffic + OTU1 BDI + Switch to standby
LOMF, ODU1 BDI OTM1
Pre-FEC SF
OTM1 p1-p4 Pre-FEC SD OTM1 p1-p4 Traffic + No No switch

Conditioning
OTM1 p1-p4 OTU1 BDI OTM1 p1-p4 Traffic + No No switch

Conditioning
OTM1 p1-p4 OTU1 TTI OTM1 p1-p4 Traffic + No No switch

Mismatch Conditioning
OTM1 p1-p4 ODU1 AIS, OTM1 p1-p4 Traffic + ODU1 BDI Switch to standby
OCI, LCK OTM1
OTM1 p1-p4 ODU1 BDI OTM1 p1-p4 Traffic + No No switch

Conditioning
OTM1 p1-p4 ODU1 TTI OTM1 p1-p4 Traffic + No No switch

OTM1 p1-p4 OPU1 PT OTM1 p1-p4 Traffic + No Switch to standby

Mismatch Conditioning OTM1
See Note 2
OTM1 p1-p4 OPU1 Far End OTM1 p1-p4 Traffic + No Switch to standby
Client Signal Conditioning OTM1
Failure
OTM1 p1-p4 OPU1 AIS OTM1 p1-p4 Traffic + No Switch to standby

Conditioning OTM1



(toward line)
Client OTM1 p1-p8 Facility OTM1 p1-p8 No Action N/A

Mapping Unconnected
Layer
Facility OTM1 p1-p8 Facility OOS OTM1 p1-p8 ODU1 LCK N/A
OTM1 p1-p8 ODU1 AIS, OTM1 p1-p8 Traffic + ODU1 BDI N/A
OCI, LCK
OTM1 p1-p8 ODU1 BDI OTM1 p1-p8 Traffic + No N/A

Conditioning
OTM1 p1-p8 ODU1 TTI OTM1 p1-p8 Traffic + No N/A

OTM1 p1-p8 OPU1 PT OTM1 p1-p8 Traffic + No N/A

OTM1 p1-p8 OPU1 Far End OTM1 p1-p8 Traffic + No N/A

Client Signal Conditioning
Failure
OTM1 p1-p8 OPU1 AIS OTM1 p1-p8 Traffic + No N/A

Conditioning
FLEX p1-p8 LOS, LOL, FLEX p1-p8 OPU1 AIS + CSF N/A
LODS
FLEX p1-p8 Rx Power OOR FLEX p1-p8 Traffic + No N/A

Conditioning
OC-n p1-p8 LOF, SF OTM1 p1-p8 OPU1 AIS + CSF N/A
OC-n p1-p8 SF, SD OTM1 p1-p8 Traffic + No N/A

Conditioning
OC-n p1-p8 AIS-L OTM1 p1-p8 Traffic + No N/A

Conditioning
OC-n p1-p8 RDI-L OTM1 p1-p8 Traffic + No N/A

Conditioning
OC-n p1-p8 Section Trace OTM1 p1-p8 Traffic + No N/A




(toward line)
Client OTM0 p1-p8 Facility OTM0 p1-p8 No Action N/A

Mapping Unconnected
Layer
OCI, LCK

Conditioning



Failure

Conditioning
FLEX p1-p8 LOS, LOL, OTM0 p1-p8 GE: OPU0 CSF N/A
LODS non-GE: OPU0 AIS +
CSF
FLEX p1-p8 Rx Power OOR OTM0 p1-p8 Traffic + No N/A

Conditioning

Conditioning

Conditioning

Conditioning




(toward line)
Client WAN p1-p8 Loss of Frame WAN p1-p8 Traffic + No N/A

Mapping Delineation Conditioning
Layer
Facility WAN p1-p8 Client Service WAN p1-p8 Traffic + No N/A
WAN p1-p8 Far End Client WAN p1-p8 N/A N/A

Signal Failure
FLEX p1-p8 Facility OOS WAN p1-p8 GFP CMF LOS N/A
(or user configured
CMF)
FLEX p1-p8 LOS, LOL, WAN p1-p8 Traffic + No N/A

LODS Conditioning
FLEX p1-p8 Rx Power OOR WAN p1-p8 Traffic + No N/A

Conditioning
Client FLEX p1-p8 Facility FLEX p1-p8 FLEX TXCON setting N/A
FLEX p1-p8 Facility OOS FLEX p1-p8 FLEX TXCON setting N/A
FLEX p1-p8 LOS, LOL FLEX p1-p8 Traffic + No N/A

Conditioning
FLEX p1-p8 Loss of Data FLEX p1-p8 Traffic + No N/A

Synch Conditioning
OC-n p1-p8 LOF OC-n p1-p8 Traffic + No N/A

Conditioning
OC-n p1-p8 SF, SD OC-n p1-p8 Traffic + No N/A

Conditioning
OC-n p1-p8 AIS-L OC-n p1-p8 Traffic + No N/A

Conditioning
OC-n p1-p8 RDI-L OC-n p1-p8 Traffic + No N/A

Conditioning
OC-n p1-p8 Section Trace OC-n p1-p8 Traffic + No N/A

Note 1: This means 1xODU0 connection is in place.

Note 2: Not applicable if OTM1 p1-p4 is ODU1 connected to another OTM1 p1-p4 line interface

Table 1-36
8xSFP OTN Flex MOTR (NTK532BA) Connected/Associated Client Port
Trigger Connected/Associated Client Port

facility Condition Facility Treatment 1+1 Port TPT
Protection
Line OTM1 p1-p4 Facility N/A N/A N/A

OTM1 p1-p4 Facility N/A N/A N/A

Partially
Unconnected
See Note 1
OTM1 p1-p4 Facility OOS FLEX p1-p8 FLEX TXCON setting Switch to standby
FLEX
OTM1 p1-p4 LOS, LOF, FLEX p1-p8 FLEX TXCON setting Switch to standby
LOMF, FLEX
Pre-FEC SF
OTM1 p1-p4 Pre-FEC SD FLEX p1-p8 Traffic + No No switch

Conditioning
OTM1 p1-p4 OTU1 BDI FLEX p1-p8 Traffic + No No switch

Conditioning
OTM1 p1-p4 OTU1 TTI FLEX p1-p8 Traffic + No No switch

OTM1 p1-p4 ODU1 AIS, FLEX p1-p8 FLEX TXCON setting Switch to standby
OCI, LCK FLEX
OTM1 p1-p4 ODU1 BDI FLEX p1-p8 Traffic + No No switch

Conditioning
OTM1 p1-p4 ODU1 TTI FLEX p1-p8 Traffic + No No switch

OTM1 p1-p4 OPU1 PT FLEX p1-p8 FLEX TXCON setting Switch to standby
Mismatch FLEX
See Note 2
OTM1 p1-p4 OPU1 Far End FLEX p1-p8 FLEX TXCON setting Switch to standby
Client Signal FLEX
Failure
OTM1 p1-p4 OPU1 AIS FLEX p1-p8 FLEX TXCON setting Switch to standby
FLEX



Protection
Client Client Facility associated with this mapping layer facility

Mapping
Layer OTM1 p1-p8 Facility FLEX p1-p8 FLEX TXCON setting N/A
FLEX
OCI, LCK FLEX

Conditioning
OTM1 p1-p8 ODU1 TTI FLEX p1-p8 Traffic + No Switch to standby

Mismatch Conditioning FLEX
Mismatch FLEX
Client Signal FLEX
Failure
OTM1 p1-p8 OPU1 AIS FLEX p1-p8 Traffic + No No switch

Conditioning
FLEX p1-p8 LOS, LOL, FLEX p1-p8 Traffic + No No switch

LODS Conditioning
FLEX p1-p8 Rx Power OOR FLEX p1-p8 Traffic + No No switch

Conditioning
OTM1 p1-p8 LOF, SF FLEX p1-p8 Traffic + No No switch

Conditioning
OTM1 p1-p8 SF, SD FLEX p1-p8 Traffic + No No switch

Conditioning
OTM1 p1-p8 AIS-L FLEX p1-p8 Traffic + No No switch

Conditioning
OTM1 p1-p8 RDI-L FLEX p1-p8 Traffic + No No switch

Conditioning
OTM1 p1-p8 Section Trace FLEX p1-p8 Traffic + No No switch




Protection
Client Facility associated with this mapping layer facility
Client OTM0 p1-p8 Facility FLEX p1-p8 FLEX TXCON setting N/A
Mapping Unconnected
Layer
Facility OTM0 p1-p8 Facility OOS FLEX p1-p8 FLEX TXCON setting Switch to standby
FLEX
OCI, LCK FLEX

Conditioning
OTM0 p1-p8 ODU0 TTI FLEX p1-p8 Traffic + No No switch

Mismatch FLEX
Client Signal FLEX
Failure
FLEX
FLEX p1-p8 LOS, LOL, FLEX p1-p8 Traffic + No No switch

LODS Conditioning
FLEX p1-p8 Rx Power OOR FLEX p1-p8 Traffic + No No switch

Conditioning
OTM0 p1-p8 LOF, SF FLEX p1-p8 Traffic + No No switch

Conditioning
OTM0 p1-p8 SF, SD FLEX p1-p8 Traffic + No No switch

Conditioning
OTM0 p1-p8 AIS-L FLEX p1-p8 Traffic + No No switch

Conditioning
OTM0 p1-p8 RDI-L FLEX p1-p8 Traffic + No No switch

Conditioning
OTM0 p1-p8 Section Trace FLEX p1-p8 Traffic + No No switch




Protection
Client WAN p1-p8 Loss of Frame FLEX p1-p8 FLEX TXCON setting Switch to standby
Mapping Delineation FLEX
Layer
Facility WAN p1-p8 Client Service FLEX p1-p8 FLEX TXCON setting Switch to standby
Mismatch FLEX
WAN p1-p8 Far End Client FLEX p1-p8 FLEX TXCON setting Switch to standby
Signal Failure FLEX
FLEX p1-p8 Facility OOS FLEX p1-p8 No action No switch
FLEX p1-p8 LOS, LOL, FLEX p1-p8 No action No switch

LODS
FLEX p1-p8 Rx Power OOR FLEX p1-p8 No action No switch
Client-to-Client Connection (hairpin)
Client FLEX p1-p8 Facility FLEX p1-p8 FLEX TXCON setting Not Supported
FLEX p1-p8 Facility OOS FLEX p1-p8 FLEX TXCON setting Not Supported
FLEX p1-p8 LOS, LOL FLEX p1-p8 FLEX TXCON setting Not Supported
FLEX p1-p8 Loss of Data FLEX p1-p8 FLEX TXCON setting Not Supported
Synch
OC-n p1-p8 LOF FLEX p1-p8 FLEX TXCON setting Not Supported
OC-n p1-p8 SF, SD FLEX p1-p8 Traffic + No Not Supported

Conditioning
OC-n p1-p8 AIS-L FLEX p1-p8 Traffic + No Not Supported

Conditioning
OC-n p1-p8 RDI-L FLEX p1-p8 Traffic + No Not Supported

Conditioning
OC-n p1-p8 Section Trace FLEX p1-p8 Traffic + No Not Supported

Note 1: This means 1xODU0 connection is in place.

Note 2: Not applicable if OTM1 p1-p4 is ODU1 connected to another OTM1 p1-p4 line interface

Table 1-37
8xSFP OTN Flex MOTR (Connected Line Port)
Trigger Connected Line Port

facility Condition Facility Connection Type Treatment 1+1 Line
Protection
Line OTM1 p1-p4 Facility N/A N/A N/A N/A

OTM1 p1-p4 Facility N/A N/A N/A N/A

Partially
Unconnected
See Note
OTM1 p1-p4 Facility OOS OTM1 p1-p4 ODU0 ODU0 AIS

ODU1 ODU1 LCK
OTM1 p1-p4 LOS, LOF, OTM1 p1-p4 ODU0 ODU0 AIS

LOMF, ODU1 ODU1 AIS
Pre-FEC SF
OTM1 p1-p4 Pre-FEC SD OTM1 p1-p4 ODU0 No

ODU1 Conditioning
OTM1 p1-p4 OTU1 BDI OTM1 p1-p4 ODU0 No

ODU1 Conditioning
OTM1 p1-p4 OTU1 TTI OTM1 p1-p4 ODU0 No

Mismatch ODU1 Conditioning
OTM1 p1-p4 ODU1 AIS, OTM1 p1-p4 ODU0 ODU0 AIS

OCI, LCK ODU1 Received
signal
passes
through
OTM1 p1-p4 ODU1 BDI OTM1 p1-p4 ODU0 No

ODU1 Conditioning
OTM1 p1-p4 ODU1 TTI OTM1 p1-p4 ODU0 N/A

Mismatch ODU1
OTM1 p1-p4 OPU1 PT OTM1 p1-p4 ODU0 ODU0 AIS

Mismatch ODU1 No
Conditioning
OTM1 p1-p4 OPU1 Far End OTM1 p1-p4 ODU0 N/A

Client Signal ODU1
Failure
OTM1 p1-p4 OPU1 AIS OTM1 p1-p4 ODU0 N/A

ODU1



Protection
ODU1 Encapsulated Client connected to OTM1 line
Client OTM1 p1-p8 Facility N/A N/A N/A N/A

Mapping Unconnected
Layer
Facility OTM1 p1-p8 Facility OOS OTM1 p1-p4 ODU1 Signal from No switch
mapping
layer
OTM1 p1-p8 ODU1 AIS, OTM1 p1-p4 ODU1 Signal from No switch
OCI, LCK mapping
layer
OTM1 p1-p8 ODU1 BDI OTM1 p1-p4 ODU1 No action No switch
OTM1 p1-p8 ODU1 TTI OTM1 p1-p4 ODU1 No action No switch

Mismatch
OTM1 p1-p8 OPU1 PT OTM1 p1-p4 ODU1 No action No switch

Mismatch
OTM1 p1-p8 OPU1 Far End OTM1 p1-p4 ODU1 No action No switch
Client Signal
Failure
OTM1 p1-p8 OPU1 AIS OTM1 p1-p4 ODU1 No action No switch
FLEX p1-p8 LOS, LOL, OTM1 p1-p4 ODU1 Signal from No switch
LODS mapping
layer
FLEX p1-p8 Rx Power OOR OTM1 p1-p4 ODU1 No action No switch
OTM1 p1-p8 LOF, SF OTM1 p1-p4 ODU1 Signal from No switch

mapping
layer
OTM1 p1-p8 SF, SD OTM1 p1-p4 ODU1 No action No switch
OTM1 p1-p8 AIS-L OTM1 p1-p4 ODU1 No action No switch
OTM1 p1-p8 RDI-L OTM1 p1-p4 ODU1 No action No switch
OTM1 p1-p8 Section Trace FLEX p1-p8 ODU1 No action No switch

Mismatch



Protection
ODU0 Encapsulated Client connected to OTM1 line

Mapping Unconnected
Layer
Facility OTM0 p1-p8 Facility OOS OTM1 p1-p4 ODU0 Signal from No switch
mapping
layer
OTM0 p1-p8 ODU0 AIS, OTM1 p1-p4 ODU0 Signal from No switch
OCI, LCK mapping
layer
OTM0 p1-p8 ODU0 BDI OTM1 p1-p4 ODU0 No action No switch
OTM0 p1-p8 ODU0 TTI OTM1 p1-p4 ODU0 No action No switch

Mismatch
OTM0 p1-p8 OPU0 PT OTM1 p1-p4 ODU0 No action No switch

Mismatch
OTM0 p1-p8 OPU0 Far End OTM1 p1-p4 ODU0 No action No switch
Client Signal
Failure
OTM0 p1-p8 OPU0 AIS OTM1 p1-p4 ODU0 No action No switch
FLEX p1-p8 LOS, LOL, OTM1 p1-p4 ODU0 Signal from No switch
LODS mapping
layer
OTM0 p1-p8 LOF, SF OTM1 p1-p4 ODU0 Signal from No switch

mapping
layer
OTM0 p1-p8 SF, SD OTM1 p1-p4 ODU0 No action No switch
OTM0 p1-p8 AIS-L OTM1 p1-p4 ODU0 No action No switch
OTM0 p1-p8 RDI-L OTM1 p1-p4 ODU0 No action No switch
OTM0 p1-p8 Section Trace OTM1 p1-p4 ODU0 No action No switch

Mismatch



Protection
Client WAN p1-p8 Loss of Frame OTM1 p1-p4 ODU0 No action No switch
Mapping Delineation
Layer
Facility WAN p1-p8 Client Service OTM1 p1-p4 ODU0 No action No switch
Mismatch
WAN p1-p8 Far End Client OTM1 p1-p4 ODU0 No action No switch
Signal Failure
FLEX p1-p8 Facility OOS OTM1 p1-p4 ODU0 No action No switch
FLEX p1-p8 LOS, LOL, OTM1 p1-p4 ODU0 No action No switch

LODS
Note: 1+1 Port TPT Protection is not supported.

Table 1-38
(1+8)xOTN Flex MOTR (NTK532DA) (Signal Conditioning)
Trigger Signal Conditioning

facility Condition Facility Signal Output 1+1 Line Protection
(toward line)
Line OTM2 p1 Facility OTM2 p1 ODU2 OCI Not Supported

OTM2 p1 Facility OTM2 p1 Unconnected TS: Not Supported

Partially ODU1 OCI
Unconnected Connected TS:
(PT= 0x20) Traffic
OTM2 p1 Facility OTM2 p1 Unconnected TS: Not Supported

Partially MSI=Unused
(PT= 0x21) Traffic
OTM2 p1 Facility OOS OTM2 p1 ODU2 LCK Not Supported
OTM2 p1 LOS, LOF, OTM2 p1 Traffic+ OTU2 BDI + Not Supported

LOMF, ODU2 BDI
Pre-FEC SF
OTM2 p1 Pre-FEC SD OTM2 p1 Traffic + No Not Supported

Conditioning
OTM2 p1 OTU2 BDI OTM2 p1 Traffic + No Not Supported

Conditioning
OTM2 p1 OTU2 TTI OTM2 p1 Traffic + No Not Supported

OTM2 p1 ODU2 AIS, OTM2 p1 Traffic + ODU2 BDI Not Supported

OCI, LCK
OTM2 p1 OTU2 BDI OTM2 p1 Traffic + No Not Supported

Conditioning
OTM2 p1 OTU2 TTI OTM2 p1 Traffic + No Not Supported

OTM2 p1 OPU2 PT OTM2 p1 Traffic + No Not Supported

OTM2 p1 OPU2 Far End OTM2 p1 Traffic + No Not Supported

Failure
OTM2 p1 OPU2 AIS OTM2 p1 Traffic + No Not Supported

Conditioning



(toward line)
Line OTM1 p2-p9 Facility OTM1 p2-p9 ODU1 OCI N/A

OTM1 p2-p9 Facility OTM1 p2-p9 Unconnected TS: N/A

Partially ODU0 OCI
Traffic
OTM1 p2-p9 Facility OOS OTM1 p2-p9 ODU1 LCK Switch to standby
OTM1
OTM1 p2-p9 LOS, LOF, OTM1 p2-p9 Traffic + OTU1 BDI Switch to standby
LOMF, + ODU1 BDI OTM1
Pre-FEC SF
OTM1 p2-p9 Pre-FEC SD OTM1 p2-p9 Traffic + No No switch

Conditioning
OTM1 p2-p9 OTU1 BDI OTM1 p2-p9 Traffic + No No switch

Conditioning
OTM1 p2-p9 OTU1 TTI OTM1 p2-p9 Traffic + No No switch

OTM1 p2-p9 ODU1 AIS, OTM1 p2-p9 Traffic + ODU1 BDI Switch to standby
OCI, LCK OTM1
OTM1 p2-p9 ODU1 BDI OTM1 p2-p9 Traffic + No No switch

Conditioning
OTM1 p2-p9 ODU1 TTI OTM1 p2-p9 Traffic + No No switch

OTM1 p2-p9 OPU1 PT OTM1 p2-p9 Traffic + No Switch to standby

Mismatch Conditioning OTM1
OTM1 p2-p9 OPU1 Far End OTM1 p2-p9 Traffic + No Switch to standby
Client Signal Conditioning OTM1
Failure
OTM1 p2-p9 OPU1 AIS OTM1 p2-p9 Traffic + No Switch to standby

Conditioning OTM1



(toward line)
Client OTMFLEX Facility OTMFLEX No Action N/A

Mapping p2-p9 Unconnected p2-p9
Layer
Facility OTMFLEX Facility OOS OTMFLEX ODUflex LCK N/A
p2-p9 p2-p9
OTMFLEX ODUflex AIS, OTMFLEX Traffic+ ODUflex BDI N/A

p2-p9 OCI, LCK, p2-p9
Loss of Frame
and Multiframe
OTMFLEX ODUflex BDI OTMFLEX Traffic + No N/A

p2-p9 p2-p9 Conditioning
OTMFLEX ODUflex TTI OTMFLEX Traffic + No N/A

p2-p9 Mismatch p2-p9 Conditioning
OTMFLEX ODUflex PT OTMFLEX Traffic + No N/A

p2-p9 Mismatch p2-p9 Conditioning
OTMFLEX OPUflex AIS OTMFLEX Traffic + No N/A

OTMFLEX MSI Mismatch OTMFLEX Traffic + No N/A

OTMFLEX MSI Mismatch OTMFLEX Traffic + No N/A

FLEX p2-p9 LOS, LOL, OTMFLEX OPUflex AIS+CSF N/A

LODS p2-p9
FLEX p2-p9 Rx Power OOR OTMFLEX Traffic + No N/A

p2-p9 Conditioning
OTM1 p2-p9 Facility OTM1 p2-p9 No action N/A

Unconnected
OTM1 p2-p9 Facility OOS OTM1 p2-p9 ODU1 LCK N/A
OCI, LCK,
Loss of Frame
and Multiframe



(toward line)
Client OTM1 p2-p9 ODU1 BDI OTM1 p2-p9 Traffic + No N/A

Mapping Conditioning
Layer
Facility OTM1 p2-p9 ODU1 TTI OTM1 p2-p9 Traffic + No N/A


Failure

Conditioning
OTM1 p2-p9 MSI Mismatch OTM1 p2-p9 Traffic + No N/A

Conditioning
FLEX p2-p9 LOS, LOL, OTM1 p2-p9 OPU1 AIS + CSF N/A
LODS

Conditioning

Conditioning

Conditioning

Conditioning




(toward line)
Client OTM0 p2-p9 Facility OTM0 p2-p9 No action N/A

Mapping Unconnected
Layer
OCI, LCK,
Loss of Frame
and Multiframe

Conditioning



Failure

Conditioning
OTM0 p2-p9 MSI Mismatch OTM0 p2-p9 Traffic + No N/A

Conditioning
FLEX p2-p9 LOS, LOL, OTM0 p2-p9 OPU0 AIS + CSF N/A
LODS

Conditioning

Conditioning

Conditioning

Conditioning




(toward line)
Client WAN p2-p9 Loss of Frame WAN p2-p9 Traffic + No N/A

Mapping Delineation Conditioning
Layer
Facility WAN p2-p9 Client Service WAN p2-p9 Traffic + No N/A
WAN p2-p9 Far End Client WAN p2-p9 Traffic + No N/A

Signal Failure Conditioning
FLEX p2-p9 Facility OOS WAN p2-p9 N/A N/A
FLEX p2-p9 LOS, LOL, WAN p2-p9 GFP CMF LOS N/A
LODS (or user configured
CMF)
FLEX p2-p9 Rx Power OOR WAN p2-p9 Traffic + No N/A

Conditioning
Client FLEX p2-p9 Facility FLEX p2-p9 FLEX TXCON setting N/A
FLEX p2-p9 Facility OOS FLEX p2-p9 FLEX TXCON setting N/A
FLEX p2-p9 LOS, LOL, FLEX p2-p9 Traffic + No N/A

LODS Conditioning
FLEX p2-p9 Loss of Data FLEX p2-p9 Traffic + No N/A

Synch Conditioning
OC-n p2-p9 LOF OC-n p2-p9 Traffic + No N/A

Conditioning
OC-n p2-p9 SF, SD OC-n p2-p9 Traffic + No N/A

Conditioning
OC-n p2-p9 AIS-L OC-n p2-p9 Traffic + No N/A

Conditioning
OC-n p2-p9 RDI-L OC-n p2-p9 Traffic + No N/A

Conditioning
OC-n p2-p9 Section Trace OC-n p2-p9 Traffic + No N/A


Table 1-39
(1+8)xOTN Flex MOTR (NTK532DA) (Connected/Associated Client Port)

Protection
(*mut-ex w/ 1+1 Line)
Line OTM2 p1 Facility N/A N/A N/A

OTM2 p1 Facility N/A N/A N/A

Partially
Unconnected
(PT= 0x20)
OTM2 p1 Facility N/A N/A N/A

Partially
Unconnected
(PT= 0x21)
OTM2 p1 Facility OOS FLEX p2-p9 FLEX TXCON setting Switch to standby
FLEX
OTM2 p1 LOS, LOF, FLEX p2-p9 FLEX TXCON setting Switch to standby
LOMF, FLEX
Pre-FEC SF
OTM2 p1 Pre-FEC SD FLEX p2-p9 Traffic + No No Switch

Conditioning
OTM2 p1 OTU2 BDI FLEX p2-p9 Traffic + No No Switch

Conditioning
OTM2 p1 OTU2 TTI FLEX p2-p9 Traffic + No No Switch

OTM2 p1 ODU2 AIS, FLEX p2-p9 FLEX TXCON setting Switch to standby
OCI, LCK FLEX
OTM2 p1 OTU2 BDI FLEX p2-p9 Traffic + No No Switch

Conditioning
OTM2 p1 OTU2 TTI FLEX p2-p9 Traffic + No No Switch

OTM2 p1 OPU2 PT FLEX p2-p9 FLEX TXCON setting Switch to standby

Mismatch FLEX
OTM2 p1 OPU2 Far End FLEX p2-p9 FLEX TXCON setting Switch to standby
Client Signal FLEX
Failure



Protection
Line OTM2 p1 OPU2 AIS FLEX p2-p9 Traffic + No Switch to standby

Facility Conditioning FLEX

Unconnected

Partially
Unconnected
FLEX
OTM1 p2-p9 LOS, LOF, FLEX p2-p9 FLEX TXCON setting Switch to standby
LOMF, FLEX
Pre-FEC SF
OTM1 p2-p9 Pre-FEC SD FLEX p2-p9 Traffic + No No Switch

Conditioning
OTM1 p2-p9 OTU1 BDI FLEX p2-p9 Traffic + No No Switch

Conditioning
OTM1 p2-p9 OTU1 TTI FLEX p2-p9 Traffic + No No Switch

OCI, LCK FLEX
OTM1 p2-p9 ODU1 BDI FLEX p2-p9 Traffic + No No Switch

Conditioning
OTM1 p2-p9 ODU1 TTI FLEX p2-p9 Traffic + No No Switch

Mismatch FLEX
Client Signal FLEX
Failure
FLEX



Protection
Client OTMFLEX Facility FLEX p2-p9 FLEX TXCON setting N/A

Mapping p2-p9 Unconnected
Layer
Facility OTMFLEX Facility OOS FLEX p2-p9 FLEX TXCON setting Switch to standby
p2-p9 FLEX
OTMFLEX ODUflex AIS, FLEX p2-p9 FLEX TXCON setting Switch to standby
p2-p9 OCI, LCK FLEX
OTMFLEX ODUflex BDI FLEX p2-p9 Traffic + No No Switch

p2-p9 Conditioning
OTMFLEX ODUflex TTI FLEX p2-p9 Traffic + No No Switch

p2-p9 Mismatch Conditioning
OTMFLEX ODUflex PT FLEX p2-p9 FLEX TXCON Switch to standby

p2-p9 Mismatch settingS FLEX
OTMFLEX OPUflex AIS FLEX p2-p9 FLEX TXCON setting Switch to standby
p2-p9 FLEX
OTMFLEX MSI Mismatch FLEX p2-p9 FLEX TXCON Switch to standby

p2-p9 settingS FLEX
OTMFLEX MSI Mismatch FLEX p2-p9 FLEX TXCON setting Switch to standby
p2-p9 FLEX
FLEX p2-p9 LOS, LOL, FLEX p2-p9 Traffic + No No Switch

LODS Conditioning
FLEX p2-p9 Rx Power OOR FLEX p2-p9 Traffic + No No Switch

Conditioning
Mapping Unconnected
Layer
Facility



Protection
Client OTM1 p2-p9 Facility OOS FLEX p2-p9 FLEX TXCON setting Switch to standby
Mapping FLEX
Layer
Facility OTM1 p2-p9 ODU1 AIS, FLEX p2-p9 FLEX TXCON setting Switch to standby
OCI, LCK FLEX

Conditioning

Mismatch FLEX
Client Signal FLEX
Failure
FLEX
OTM1 p2-p9 MSI Mismatch FLEX p2-p9 FLEX TXCON setting Switch to standby
FLEX
FLEX p2-p9 LOS, LOL, FLEX p2-p9 Traffic + No No Switch

LODS Conditioning

Conditioning
OC-n p2-p9 LOF, SF FLEX p2-p9 Traffic + No No Switch

Conditioning
OC-n p2-p9 SF, SD FLEX p2-p9 Traffic + No No Switch

Conditioning
OC-n p2-p9 AIS-L FLEX p2-p9 Traffic + No No Switch

Conditioning
OC-n p2-p9 RDI-L FLEX p2-p9 Traffic + No No Switch

Conditioning
OC-n p2-p9 Section Trace FLEX p2-p9 Traffic + No No Switch




Protection
Mapping Unconnected
Layer
Facility OTM0 p2-p9 Facility OOS FLEX p2-p9 FLEX TXCON setting Switch to standby
FLEX
OCI, LCK FLEX

Conditioning

Mismatch FLEX
Client Signal FLEX
Failure
FLEX
OTM0 p2-p9 MSI Mismatch FLEX p2-p9 FLEX TXCON setting Switch to standby
FLEX
FLEX p2-p9 LOS, LOL, FLEX p2-p9 OPU0 AIS + CSF No Switch
LODS

Conditioning
OC-n p2-p9 LOF, SF FLEX p2-p9 Traffic + No No Switch

Conditioning
OC-n p2-p9 SF, SD FLEX p2-p9 Traffic + No No Switch

Conditioning
OC-n p2-p9 AIS-L FLEX p2-p9 Traffic + No No Switch

Conditioning



Protection
Client OC-n p2-p9 RDI-L FLEX p2-p9 Traffic + No No Switch

Mapping Conditioning
Layer
Facility OC-n p2-p9 Section Trace FLEX p2-p9 Traffic + No No Switch
Client WAN p2-p9 Loss of Frame FLEX p2-p9 FLEX TXCON setting Switch to standby
Mapping Delineation FLEX
Layer
Facility WAN p2-p9 Client Service FLEX p2-p9 FLEX TXCON setting Switch to standby
Mismatch FLEX
WAN p2-p9 Far End Client FLEX p2-p9 FLEX TXCON setting Switch to standby
Signal Failure FLEX
FLEX p2-p9 Facility OOS FLEX p2-p9 No Action No Switch
FLEX p2-p9 LOS, LOL, FLEX p2-p9 No Action No Switch

LODS
FLEX p2-p9 Rx Power OOR FLEX p2-p9 No Action No Switch
Table 1-40
(1+8)xOTN Flex MOTR (NTK532DA) (Connected Line Port)

facility Condition Facility Connection Treatment 1+1 Line
Type Protection
Line OTM2 p1 Facility N/A N/A N/A Not Supported

OTM2 p1 Facility N/A N/A N/A Not Supported

Partially
Unconnected
(PT= 0x20)
OTM2 p1 Facility N/A N/A N/A Not Supported

Partially
Unconnected
(PT= 0x21)



Type Protection
Line OTM2 p1 Facility OOS OTM1 p2-p9 ODU0 ODU0 AIS Not Supported
Facility OTM2 p1 ODU1 ODU1 AIS
ODUflex ODUflex AIS
ODU2 Not Supported
OTM2 p1 LOS, LOF, OTM1 p2-p9 ODU0 ODU0 AIS Not Supported
LOMF, OTM2 p1 ODU1 ODU1 AIS
Pre-FEC SF ODUflex ODUflex AIS
ODU2 Not Supported
OTM2 p1 Pre-FEC SD OTM1 p2-p9 ODU0 No Conditioning Not Supported

OTM2 p1 ODU1 No Conditioning
ODUflex No Conditioning
ODU2 Not Supported
OTM2 p1 OTU2 BDI OTM1 p2-p9 ODU0 No Conditioning Not Supported

ODU2 Not Supported
OTM2 p1 OTU2 TTI OTM1 p2-p9 ODU0 No Conditioning Not Supported

Mismatch OTM2 p1 ODU1 No Conditioning
ODU2 Not Supported
OTM2 p1 ODU2 AIS, OTM1 p2-p9 ODU0 ODU0 AIS Not Supported
OCI, LCK OTM2 p1 ODU1 ODU1 AIS
ODUflex ODUflex AIS
ODU2 Not Supported
OTM2 p1 OTU2 BDI OTM1 p2-p9 ODU0 No Conditioning Not Supported

ODU2 Not Supported
OTM2 p1 OTU2 TTI OTM1 p2-p9 ODU0 No Conditioning Not Supported

ODU2 Not Supported
OTM2 p1 OPU2 PT OTM1 p2-p9 ODU0 ODU0 AIS Not Supported

Mismatch OTM2 p1 ODU1 ODU1 AIS
ODUflex ODUflex AIS
ODU2 Not Supported



Type Protection
Line OTM2 p1 OPU2 Far End OTM1 p2-p9 ODU0 N/A Not Supported
Facility Client Signal OTM2 p1 ODU1 N/A
Failure ODUflex N/A
ODU2 Not Supported
OTM2 p1 OPU2 AIS OTM1 p2-p9 ODU0 N/A Not Supported

OTM2 p1 ODU1 N/A
ODUflex N/A
ODU2 Not Supported
OTM2 p1 Service OTM1 p2-p9 ODU0 ODU0 AIS Not Supported

Mismatch OTM2 p1 ODU1 ODU1 AIS
ODUflex ODUflex AIS
ODU2 Not Supported
Line OTM1 p2-p9 Facility N/A N/A N/A N/A

OTM1 p2-p9 Facility N/A N/A N/A N/A

Partially
Unconnected
OTM1 p2-p9 Facility OOS OTM1 p2-p9 ODU0 ODU0 AIS Not Supported
OTM2 p1 ODU1 ODU1 LCK
OTM1 p2-p9 LOS, LOF, OTM1 p2-p9 ODU0 ODU0 AIS Not Supported
LOMF, OTM2 p1 ODU1 ODU1 AIS
Pre-FEC SF
OTM1 p2-p9 Pre-FEC SD OTM1 p2-p9 ODU0 No Conditioning Not Supported

OTM2 p1 ODU1
OTM1 p2-p9 OTU1 BDI OTM1 p2-p9 ODU0 No Conditioning Not Supported
OTM2 p1 ODU1
OTM1 p2-p9 OTU1 TTI OTM1 p2-p9 ODU0 No Conditioning Not Supported
Mismatch OTM2 p1 ODU1
OTM1 p2-p9 ODU1 AIS, OTM1 p2-p9 ODU0 ODU0 AIS Not Supported
OCI, LCK OTM2 p1 ODU1 Rx signal
passes through



Type Protection
Line OTM1 p2-p9 ODU1 BDI OTM1 p2-p9 ODU0 No Conditioning Not Supported
Facility OTM2 p1 ODU1
OTM1 p2-p9 ODU1 TTI OTM1 p2-p9 ODU0 N/A N/A

Mismatch OTM2 p1 ODU1
OTM1 p2-p9 OPU1 PT OTM1 p2-p9 ODU0 ODU0 AIS Not Supported
OTM1 p2-p9 OPU1 Far End OTM1 p2-p9 ODU0 N/A N/Ad
Client Signal OTM2 p1 ODU1
Failure
OTM1 p2-p9 OPU1 AIS OTM1 p2-p9 ODU0 N/A N/A

OTM2 p1 ODU1
ODUflex Encapsulated Client connected to OTM1/OTM2 line
Client OTMFLEX Facility N/A N/A N/A N/A

Mapping p2-p9 Unconnected
Layer
Facility OTMFLEX Facility OOS OTM1 p2-p9 ODUflex Signal from Not Supported
p2-p9 OTM2 p1 mapping layer
OTMFLEX ODUflex AIS, OTM1 p2-p9 ODUflex Signal from Not Supported
p2-p9 OCI, LCK OTM2 p1 mapping layer
OTMFLEX ODUflex BDI OTM1 p2-p9 ODUflex No Action Not Supported

p2-p9 OTM2 p1
OTMFLEX ODUflex TTI OTM1 p2-p9 ODUflex No Action Not Supported

p2-p9 Mismatch OTM2 p1
OTMFLEX ODUflex PT OTM1 p2-p9 ODUflex No Action Not Supported

p2-p9 Mismatch OTM2 p1
OTMFLEX OPUflex AIS OTM1 p2-p9 ODUflex No Action Not Supported

p2-p9 OTM2 p1
OTMFLEX MSI Mismatch OTM1 p2-p9 ODUflex No Action Not Supported

p2-p9 OTM2 p1



Type Protection
Client OTMFLEX MSI Mismatch OTM1 p2-p9 ODUflex No Action Not Supported
Mapping p2-p9 OTM2 p1
Layer
Facility FLEX p2-p9 LOS, LOL, OTM1 p2-p9 ODUflex Signal from Not Supported
LODS OTM2 p1 mapping layer
FLEX p2-p9 Rx Power OOR OTM1 p2-p9 ODUflex Signal from Not Supported
OTM2 p1 mapping layer
ODU1 Encapsulated Client connected to OTM1/OTM2 line

Mapping Unconnected
Layer
Facility OTM1 p2-p9 Facility OOS OTM1 p2-p9 ODU1 Signal from Not Supported
OTM1 p2-p9 ODU1 AIS, OTM1 p2-p9 ODU1 Signal from Not Supported
OCI, LCK OTM2 p1 mapping layer
OTM1 p2-p9 ODU1 BDI OTM1 p2-p9 ODU1 No Action Not Supported
OTM2 p1
OTM1 p2-p9 ODU1 TTI OTM1 p2-p9 ODU1 No Action Not Supported
Mismatch OTM2 p1
OTM1 p2-p9 OPU1 PT OTM1 p2-p9 ODU1 No Action Not Supported

Mismatch OTM2 p1
OTM1 p2-p9 OPU1 Far End OTM1 p2-p9 ODU1 No Action Not Supported
Client Signal OTM2 p1
Failure
OTM1 p2-p9 OPU1 AIS OTM1 p2-p9 ODU1 No Action Not Supported
OTM2 p1
OTM1 p2-p9 MSI Mismatch OTM1 p2-p9 ODU1 No Action Not Supported
OTM2 p1
FLEX p2-p9 LOS, LOL, OTM1 p2-p9 ODU1 Signal from Not Supported



Type Protection
Client FLEX p2-p9 Rx Power OOR OTM1 p2-p9 ODU1 No Action Not Supported
Mapping OTM2 p1
Layer
Facility OC-n p2-p9 LOF, SF OTM1 p2-p9 ODU1 Signal from Not Supported
OC-n p2-p9 SF, SD OTM1 p2-p9 ODU1 No Action Not Supported

OTM2 p1
OC-n p2-p9 AIS-L OTM1 p2-p9 ODU1 No Action Not Supported

OTM2 p1
OC-n p2-p9 RDI-L OTM1 p2-p9 ODU1 No Action Not Supported

OTM2 p1
OC-n p2-p9 Section Trace OTM1 p2-p9 ODU1 No Action Not Supported
Mismatch OTM2 p1
ODU0 Encapsulated Client connected to OTM1/OTM2 line

Mapping Unconnected
Layer
Facility OTM0 p2-p9 Facility OOS OTM1 p2-p9 ODU0 Signal from Not Supported
OTM0 p2-p9 ODU0 AIS, OTM1 p2-p9 ODU0 Signal from Not Supported
OCI, LCK OTM2 p1 mapping layer
OTM0 p2-p9 ODU0 BDI OTM1 p2-p9 ODU0 No Action Not Supported
OTM2 p1
OTM0 p2-p9 ODU0 TTI OTM1 p2-p9 ODU0 No Action Not Supported
Mismatch OTM2 p1
OTM0 p2-p9 OPU0 PT OTM1 p2-p9 ODU0 No Action Not Supported

Mismatch OTM2 p1
OTM0 p2-p9 OPU0 Far End OTM1 p2-p9 ODU0 No Action Not Supported
Client Signal OTM2 p1
Failure



Type Protection
Client OTM0 p2-p9 OPU0 AIS OTM1 p2-p9 ODU0 No Action Not Supported
Mapping OTM2 p1
Layer
Facility OTM0 p2-p9 MSI Mismatch OTM1 p2-p9 ODU0 No Action Not Supported
OTM2 p1
FLEX p2-p9 LOS, LOL, OTM1 p2-p9 ODU0 Signal from Not Supported
FLEX p2-p9 Rx Power OOR OTM1 p2-p9 ODU0 No Action Not Supported
OTM2 p1
OC-n p2-p9 LOF, SF OTM1 p2-p9 ODU0 Signal from Not Supported
OC-n p2-p9 SF, SD OTM1 p2-p9 ODU0 No Action Not Supported

OTM2 p1
OC-n p2-p9 AIS-L OTM1 p2-p9 ODU0 No Action Not Supported

OTM2 p1
OC-n p2-p9 RDI-L OTM1 p2-p9 ODU0 No Action Not Supported

OTM2 p1
OC-n p2-p9 Section Trace OTM1 p2-p9 ODU0 No Action Not Supported
Mismatch OTM2 p1
Client WAN p2-p9 Loss of Frame OTM1 p2-p9 ODU0 No Action Not Supported
Mapping Delineation
Layer
Facility WAN p2-p9 Client Service OTM1 p2-p9 ODU0 No Action Not Supported
Mismatch
WAN p2-p9 Far End Client OTM1 p2-p9 ODU0 No Action Not Supported
Signal Failure
FLEX p2-p9 Facility OOS OTM1 p2-p9 ODU0 No Action Not Supported
FLEX p2-p9 LOS, LOL, OTM1 p2-p9 ODU0 No Action Not Supported
LODS
FLEX p2-p9 Rx Power OOR OTM1 p2-p9 ODU0 No Action Not Supported

Signal conditioning for OTN I/F Flex 16xSFP, 4x10G PKT I/F, and OTN
XC I/F 40G circuit packs
Attention: No defects and no conditioning are applicable to the FTTP facility
object.
The following signal conditioning is applied for OTN I/F Flex 16xSFP, 4x10G
PKT I/F, and OTN XC I/F 40G triggered events.
Table 1-41
OTN I/F Flex 16xSFP, 4x10G PKT I/F and OTN XC I/F 40G signal conditioning—PTP facility
Defect Faceplate Conditioning Fabric Conditioning Notes
SA CP Fail PTP_CONDTYPE Not applicable
Terminal Loopback Laser off Not applicable Occurs when OTU TTP,
ETTP or STTP is in
terminal loopback
Facility Loopback None (Laser on) Not applicable Occurs when OTU TTP,
ETTP or STTP is in facility
loopback
OOS-MA PTP_CONDTYPE Not applicable
Child ODU term CTP PTP_CONDTYPE Not applicable

OOS-MA
No Cross Connections Laser off Not applicable PTP service type of ETTP,
on child ODU term-CTP STTP, etc. (non-OTU)
None (no conditioning Not applicable PTP service type of OTU

as to not interfere with
GCC0 (OTU) and GCC
1 & 2 (ODU)
No CTP PTP_CONDTYPE Not applicable No child ODU CTPs

present
Loss of Signal None Send Faceplate Defect

indication to children
XC Intercard Fail PTP_CON DTYPE Not applicable
Receive at least one PTP_CONDTYPE Not applicable WAN defect, Rx ODU

Fabric Defect indication defect on ODU term-CTP
from children only

Table 1-42
OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—OTUTTP facility
SA CP Fail None Not applicable
Loopback None Not applicable Clears active conditioning

when a facility or terminal
loopback is active
OOS-MA None Not applicable
Faceplate Signal Fail OTU BDI Send Faceplate Defect OTU LOS, LOF, LOC,
indication to children LOM, SF, TIM, AIS
OTU IAE OTU BIAE Not applicable
OTU Signal Degrade OTU BEI Not applicable
Table 1-43
OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—ETTP facility
SA CP Fail ETTP_CONDTYPE Not applicable
Loopback None Not applicable Clears any active hold

timer or conditioning
loopback is active
OOS-MA ETTP_CONDTYPE Not applicable
Child ODU term CTP ETTP_CONDTYPE Not applicable

OOS-MA
XC Intercard Fail Holdoff/ETTP_CONDTYPE Not applicable ETH IDLE conditioning

during holdoff period
Faceplate Signal Fail None Send Faceplate LOS, LOC, LODS, Link
Defect indication to Down, EER
children
Receive at least one Holdoff/ETTP_CONDTYPE Not applicable ETH IDLE conditioning

Fabric Defect from during holdoff period
children (WAN or ODU
term-CTP)

Table 1-44
OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—STTP facility
SA CP Fail AIS-L Not applicable

loopback is active
OOS-MA AIS-L Not applicable
Child ODU term CTP Not applicable

OOS-MA
XC Intercard Fail AIS-L Not applicable
Faceplate Signal Fail AIS-L Send Faceplate LOS, LOF, LOC, SF/B2
Defect indication to BER
children
Receive at least one AIS-L Not applicable

Fabric Defect from
children (WAN or ODU
term-CTP)
Table 1-45
OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—ODUTTP facility
SA CP Fail ODU AIS Not applicable

loopback is active
OOS-MA ODU LCK Not applicable
XC Intercard Fail ODU AIS Not applicable
PST = USPC None Not applicable Placeholder ODU TTP

until ODU TTP/CTP is
provisioned by end user
Receive Faceplate ODU BDI Not applicable

Defect from parents


OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—ODUTTP facility
Faceplate ODU Sig Fail ODU BDI Send Faceplate Defect Rx ODU LCK, OCI, AIS,
indication to children LOF, TIM
Faceplate OPU MSIM ODU BDI Send Faceplate Defect Detected at Higher-Order
indication to children ODU TTP
Faceplate OPU Signal None Send Faceplate Defect Rx OPU PTM, MSIM,
Fail indication to children CSF, AIS
Table 1-46
OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—WAN facility
SA CP Fail Not applicable None
OOS-MA Not applicable None
Terminal Loopback Not applicable None Clears active conditioning

loopback is active
Facility Loopback Not applicable WAN_CONDTYPE
Receive Faceplate Not applicable WAN_CONDTYPE

Defect from parent
Fabric FESF Send Fabric Defect None

indication to parents
(ETTP & PTP)
Fabric CSM Send Fabric Defect None

(ETTP & PTP)
Fabric LOFD Send Fabric Defect None

(ETTP & PTP)

Table 1-47
OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—ODU mon-CTP, ODU trans-CTP
facilities
SA CP Fail ODU AIS ODU AIS
Facility Loopback None ODU AIS Faceplate traffic is looped

back
Terminal Loopback None None All active conditioning is

cleared when a facility or
terminal loopback is active
OOS-MA ODU LCK ODU LCK
OPU MSIM None ODU AIS Detected at Higher-Order

ODU TTP
XC Intercard Fail ODU AIS None
Mate Intercard Fail None ODU AIS XCIF only
Receive Faceplate ODU BDI ODU AIS

Defect from parent
No rx_conn None ODU OCI No CRS from XCIF/trib

faceplate to XC
No tx_conn ODU OCI None No CRS from XC to

XCIF/trib faceplate
No tx_conn & no ODU OCI ODU OCI No CRS in either direction

rx_conn
Fabric ODU defect None None
Fabric OPU defect None None ODU/OPU Defects are

passed from fabric to
faceplate
Table 1-48
OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—ODU term-CTP facility
SA CP Fail Not applicable ODU AIS
Facility Loopback Not applicable None Faceplate traffic is looped

back
Terminal Loopback Not applicable ODU AIS All active conditioning is



OOS-MA Not applicable ODU LCK
Mate Intercard Fail Not applicable ODU AIS XCIF only
Receive at least one Not applicable CTP_CONDTYPE (If

Faceplate Defect from CTP_CONDTYPE is
parent 'OPUK_NONE',
conditioning is ODU
AIS)
Fabric ODU Signal Fail Send Fabric Defect ODU BDI ODU LCK, OCI, AIS, LOF,
indication to parents TIM
Fabric OPU Signal Fail Send Fabric Defect None OPU PTM, MSIM, CSF,
indication to parents AIS
No rx_conn & existing Not applicable ODU OCI No CRS from XC to

tx_conn XCIF/trib faceplate
Existing rx_conn & no Not applicable None

tx_conn
No rx_conn & no Tell parent PTP and ODU OCI

tx_conn xTTP there are no CRSs
Table 1-49
SA CP Fail Not applicable ODU AIS
Facility Loopback Not applicable None Faceplate traffic is looped

back
Terminal Loopback Not applicable ODU AIS All active conditioning is

OOS-MA Not applicable ODU LCK
Mate Intercard Fail Not applicable ODU AIS XCIF only
Receive at least one Not applicable CTP_CONDTYPE (If

Faceplate Defect from CTP_CONDTYPE is
parent 'OPUK_NONE',
conditioning is ODU
AIS)


Fabric ODU Signal Fail Send Fabric Defect ODU BDI ODU LCK, OCI, AIS, LOF,
indication to parents TIM
Fabric OPU Signal Fail Send Fabric Defect None OPU PTM, MSIM, CSF,
indication to parents AIS
No rx_conn & existing Not applicable ODU OCI No CRS from XC to

tx_conn XCIF/trib faceplate
Existing rx_conn & no Not applicable None

tx_conn
No rx_conn & no Tell parent PTP and ODU OCI

tx_conn xTTP there are no CRSs
Table 1-50
OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—TCM TTP facility
SA CP Fail TCM AIS Not applicable
Loopback None Not applicable All active conditioning is

OOS-MA TCM LCK Not applicable
No Connection on TCM OCI Not applicable

sibling ODU
XC Intercard Fail TCM AIS Not applicable
Receive Faceplate TCM BDI Not applicable

Defect from parents
Faceplate TCM defect TCM BDI Not applicable TCM AIS, LCK, OCI, LTC,
LOF, TIM
Faceplate TCM IAE TCM BIAE Not applicable
Faceplate TCM Signal TCM BEI Not applicable

Degrade

Table 1-51
OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—TCM mon-CTP facility
SA CP Fail TCM AIS TCM AIS
Terminal Loopback None None All active conditioning is

Facility Loopback None TCM AIS
OOS TCM LCK TCM LCK
No Connection on TCM OCI TCM OCI

sibling ODU
XC Intercard Fail TCM AIS TCM AIS
Mate intercard Fail None None
Receive Faceplate None None

Defect from parents
Faceplate TCM defect None None TCM AIS, LCK, OCI, LTC,
LOF, TIM - all defects are
passed through from
faceplate to fabric
Faceplate TCM IAE None None Passed through from

faceplate to fabric
Fabric TCM Defect None None TCM AIS, LCK, OCI, LTC,
LOF, TIM - all defects are
passed through from
fabric to faceplate
Fabric TCM IAE None None Passed through from

fabric to faceplate

Table 1-52
OTN I/F Flex 16xSFP and OTN XC I/F 40G signal conditioning—TCM term-CTP facility
SA CP Fail Not applicable TCM AIS
Terminal Loopback Not applicable None All active conditioning is

Facility Loopback Not applicable TCM AIS
OOS Not applicable TCM LCK
No Connection on Not applicable TCM OCI

sibling ODU
Mate Intercard Fail Not applicable TCM AIS
Receive Faceplate Not applicable TCM AIS

Defect from parents
Fabric TCM Defect Not applicable TCM BDI TCM AIS, LCK, OCI, LTC,
LOF, TIM
Fabric TCM IAE Not applicable TCM BIAE

TCM BEI
Fabric TCM Signal Not applicable TCM BIAE

Degrade TCM BEI

Signal conditioning for L2 MOTR 2xXFP/10xSFP circuit packs

L2 MOTR OTM2 port 1 and 2 trigger
Signal conditioning behavior on L2 MOTR is affected by the following:
• ETH versus ETH10G facility
• OTM2 mapped with ETH10G in a particular mode (11.05/11.09 versus
10.709)
• ETH10G in ByPass-OTN mode (EVPL versus L2 mode)
• TXCON attribute on ETH or ETH10G facilities in EVPL mode
• OTM2 1+1 Line Protection provisioned or not
• The ETH and ETH100 facilities will raise two additional alarms under the
same conditioning scenarios compared to the ETH10G facilities.
Conditioning example: Remote Port Unreachable.
— ETH10G: Alarms raised, Remote Port Unreachable
— ETH, ETH100, Alarms raised, Remote Port Unreachable, Link Down,
Loss Of Datasync
The following signal conditioning is applied for OTM2 port 1 and 2 triggered
events.
Table 1-53
L2 MOTR signal conditioning—OTM2 port 1 and 2 trigger
Condition Facility ETH10G OTM2 1+1 TxCon/EVPL Signal Output Facility
Provisioned
OTM2 p1-p2 OTM2 p1-p2 No Switched to OTM2/ETH ODU2 LCK OTM2 p1-p2
Facility OOS conditioning Standby 10G
See Note 2
OTM2 p1-p2 OTM2 p1-p2 Remote Switched to OTM2/ETH ODU2 BDI OTM2 p1-p2
Rx ODU2 AIS Fault Standby 10G ETH10G
conditioning OTM2 conditioning conditioning
OTM2 p1-p2 OTM2 p1-p2 BDI Traffic No ODU2 BDI OTM2 p1-p2
Rx OTU2 BDI No remain on conditioning alarm
conditioning the Active See Note 4 No conditioning
OTM2
OTM2 p1-p2 OTM2 p1-p2 Remote Switched to OTM2/ETH OTU2 BDI and OTM2 p1-p2
Rx OTU2 Fault Standby 10G ODU2 BDI,
LOS, LOF, conditioning OTM2 conditioning ETH10G
LOMF, or See Note 3 See Note 2 conditioning
PreFEC SF


L2 MOTR signal conditioning—OTM2 port 1 and 2 trigger
Condition Facility ETH10G OTM2 1+1 TxCon/EVPL Signal Output Facility
Provisioned
OTM2 p1-p2 OTM2 p1-p2 Remote Traffic OTM2/ETH No conditioning OTM2 p1-p2
Rx OPU2 Fault remain on 10G
PN11 conditioning the Active conditioning
See Note 3 OTM2 See Note 2
OTM2 p1-p2 OTM2 p1-p2 No Switched to OTM2/ETH OTU2 SD alarm OTM2 p1-p2
Rx OTU conditioning Standby 10G No conditioning
Signal (SD OTM2 conditioning when FEC is
Degrade conditioning) See Note 2 disabled
OTM2 p1-p2 OTM2 p1-p2 Remote Switched to OTM2/ETH ODU2 BDI OTM2 p1-p2
Rx ODU2 OCI Fault Standby 10G
conditioning OTM2 conditioning
Note 1: If the ETH10G is mapped into this OTM2 being placed OOS-MA, the Ethernet datapath is
disabled such that no L2 traffic can be carried in either direction on the endpoint
Note 2: If the OTM2/ETH10G is the NNI Line for any ETH EVPL UNI clients (by way of EVPL
connections with ENT-CRS-VCE), those client facilities will be conditioned based on their TXCON
attribute value (that is either laser conditioning or 10B Error injection)
Note 3: ETH10G is in a Rx Local Fault state which disables datapath in both directions and sends
Remote Fault to far-end.
Note 4: No ETH EVPL UNI client conditioning will occur if the OTM2/ETH10G NNI Line for this ETH
client receives BDI.
Signal conditioning for OC-n/STM-n 20G circuit packs

Signal conditioning behavior on the following 20G OC-n/STM-n is affected by
the ODU LCK Signal conditioning when port 1 is OOS:
• (2+8)xOC-n/STM-n STS-1/VC-3 20G
• (2+8)xOC-n/STM-n STS-1/VC-3 OTN 20G
• (2+8)xOC-n/STM-n LO 20G
• (2+8)xOC-n/STM-n LO OTN 20G

The following signal conditioning is applied for OTM2 port 1 or port 2 triggered
events.
Table 1-54
HO 10 port, OC-n/STM-n 20G STS-1/VC-3 2x XFP/8x SFP
OTM2 p1 or p2 Facility OTM2 p1 or p2 ODU2 LCK OTM2 p1or P2

OOS (Note 1)
OTM2 p1 Rx ODU2 AIS, OTM2 p1 ODU2 BDI OTM2 p1

ODU LCK, and ODU OCI RFI-L OC192/STM64 p1
(Note 2)

RFI-L (Note 3) OC192/STM64 p1
OTM2 p1 Rx OTU2 LOS, OTM2 p1 OTU2 BDI and ODU2 OTM2 p1

LOF, LOMF or Pre-FEC BDI OC192/STM64 p1
Signal Fail (Note 4) RFI-L
OTM2 p1 Rx OTU2 BDI OTM2 p1 No conditioning OTM2 p1

or ODU2 BDI (Note 5) No conditioning OC192/STM64 p1
PTI Mismatch (Note 6) OTM2 p1 No conditioning OTM2 p1

RFI-L


Note 3: AIS-L is raised.
Note 4: OTU2 alarms mask all OC192/STM64 alarms.
Note 6: PTI Mismatch will trigger RFI-L for OC192/STM64 facility on port 1.

Automatic laser shutdown (MSPP and Broadband services)

Automatic laser shutdown (ALS) on the optical interface circuit pack shuts
down a laser source if a Loss of Signal (LOS) alarm condition is detected on
the associated receive interface. ALS can be enabled/disabled on an optical
port basis (default is disabled for SONET mode and enabled for SDH/SDH-J
mode enabled).
If enabled, the ALS circuit shuts down the laser in the event of an LOS alarm
on the associated receive interface. The laser remains shutdown until the LOS
alarm clears. If the alarm does not clear, an automatic restart is attempted:
• For non-DWDM circuit packs, the laser is turned on for two seconds every
100 seconds.
• For DWDM circuit packs, the laser is turned on for five seconds
(100 + (6 x Lambda index) seconds) after the LOS signal is detected and
then every 379 seconds. The Lambda index depends on the wavelength
of the optical interface and ensures that all the DWDM optical interfaces
feeding an optical amplifier are not all turned on/off at the same time.
Attention: The 10G AM1/AM2 DWDM and SuperMux circuit packs do not
support ALS.

Automatic Power Reduction (APR) (Photonic services)

The APR feature is a controlled ramp-down and recovery mechanism used to
limit potential exposure to instances of high optical power with a view of
protecting personnel and preventing equipment damage on detection of high
reflections, breaks, or disconnects in the optical line. It is non-provisionable,
and is activated when an amplifier circuit pack is placed in service.
When the optical return loss (ORL) of an amplifier falls below the threshold,
the system reduces the amplifier output power level to minimize the danger of
personal eye injury. A regulatory-deemed safe level of optical power is
transmitted in the period of optical discontinuity on the line to facilitate
automatic detection of line restoration and recovery to normal state. It is used
by lowering the optical output to a residual level suitable for making OR
measurements and facilitating auto recovery on resumption of the normal
system connectivity.
The 6500 Amplifier Module EDFA facility APR system is triggered by low
return loss detected at the line out. This detection affects the EDFA
immediately preceding the reflection point invoking APR on this EDFA. The
low return loss condition may be due to:
• poor connection at output connector or subsequent connections in the line
• fiber break downstream
When an APR condition is triggered, an Automatic Power Reduction Active

alarm is raised against any amplifier with reduced power.

Automatic Line Shut Off (ALSO) (Photonic services)

The ALSO feature is a safety laser shutdown mechanism. It is
non-provisionable, and is activated when an amplifier circuit pack is placed in
service or during some SLAT procedures. Amplifier power levels are turned
down or turned off when a fiber break or intermediate connector disconnect
occurs between two neighboring sites, where optical radiation is being fed into
both ends of the optical fiber and generating a hazard on both ends of a fiber
break.
When an ALSO condition is triggered, an Automatic Shutoff alarm is raised

against any transmitter that was shut off.
Attention: For the ALSO feature to function correctly, you must properly
configure the OTS first.
ALSO can be disabled on the SAM, ESAM or LIM circuit packs (C-Band and
L-Band) by setting the ALSO_Disable flag to TRUE for the OPTMON facility.
This action must only be performed when there is no OSC in the OTS for
automatic recovery from optical line fail condition.

323-1851-543
2-1
Alarm surveillance 2-
This chapter provides information and procedures about alarm profiles,

external alarm provisioning, network alarm monitoring and events
surveillance.
For a description of the 6500 Packet-Optical Platform (6500) alarm features,

refer to Chapter 1, “Alarm and trouble clearing strategy” of this document.
Abbreviations used in this chapter

ACO Alarm Cut-Off
BLSR Bidirectional Line Switched Ring
CFP 100G transceiver form factor pluggable
CIR Committed Information Rate
DCC Data Communications Channel
DPO DWDM Pluggable Optics
BDI Backward Defect Identifier
GCC General Communications Channel
HERS Head End Ring Switching
LAN Local Area Network
LED Light-emitting Diode
MIC Maintenance Interface Card
MS Multiplex Section
MSP Multiplex Section Protection
MS-SPRing Multiplex Section - Shared Protection Ring
MXC Multiservice Cross-connect
RPR Resilient Packet Ring
RS Regenerator Section
SFP Small form Factor Pluggable
SNMP Simple Network Management Protocol
S/R Save/Restore
SSM Synchronization Status Messaging
STS Synchronous Transport Signal

2-2 Alarm surveillance
TOD Time Of Day

UPC User Privilege Code
VC Virtual Container
VCE Virtual Circuit Endpoints
VT Virtual Tributary
VTG Virtual Tributary Group
WAN Wide Area Network
XFP 10G transceiver form factor pluggable
Alarm parameters
External control types
The external control relays support the external control types listed in
Table 2-1 on page 2-2.
Table 2-1
External control labels
External control label External control type
Air conditioning Air conditioning
Engine Engine
Fan Fan
Generator Generator
Heat Heater
Light Lighting
Miscellaneous Miscellaneous
Sprinkler Sprinkler
(Null) No label is associated

with the specific relay.
However, some pieces of
external equipment can
be connected to this relay.

Environmental alarm labels

Table 2-2 on page 2-3 lists the labels and associated condition types available
for the environmental alarms.
Table 2-2
Environmental alarm labels and associated condition types
Alarm label (default description) Condition Type
48-V power supply failure (see Note) PWR-48
Air compressor failure AIRCOMPR
Air conditioning failure AIRCOND
Air dryer failure AIRDRYR
Battery discharging BATDSCHRG
Battery failure BATTERY
Commercial power failure CLFAN
Cooling fan failure POWER
Engine failure ENGINE
Engine operating ENGOPRG
Explosive gas EXPLGS
Fire FIRDETR
Fire detector failure FIRE
Flood FLOOD
Fuse failure FUSE
Generator failure GEN
High airflow HIAIR
High humidity HIHUM
High temperature HITEMP
High water HIWTR
Intrusion INTRUDER
Low battery voltage LWBATVG
Low cable pressure LWFUEL
Low fuel LWHUM
Low humidity LWPRES
Low temperature LWTEMP
Low water LWWTR
Miscellaneous MISC
Open door OPENDR
Pump failure PUMP
Rectifier failure RECT


Environmental alarm labels and associated condition types
Rectifier high voltage RECTHI
Rectifier low voltage RECTLO
Smoke SMOKE
Toxic gas TOXICGAS
Ventilation system failure VENTN
Note: "-48 Vdc" is expressed as "48-V" in the label and default
description.

Autonomous events
Autonomous events do not require action. Events are raised with a severity of
“Log”. Events report the activity status on the network elements. To retrieve
events, refer to Procedure 2-3, "Retrieving events for a network element" on
page 15. The events listed in the Historical Fault Browser application include
the alarms that have been raised, both cleared or not cleared, and the logged
alerts and events that do not require action.
Table 2-3 on page 2-5 lists the logged alerts that do not require action. For a
complete list of alarms that can be raised, refer to the “List of alarms” on page
4-5 in this document.
Table 2-3
Autonomous events
Event category (Note) Description

Files file 'ftp://<host>[:port]/<path>/<filename>' has started
file 'ftp://<host>[:port]/<path>/<filename>' has completed
file 'ftp://<host>[:port]/<path>/<filename>' has failed
file 'sftp://<host>[:port]/<path>/<filename>' has started
file 'sftp://<host>[:port]/<path>/<filename>' has completed
file 'sftp://<host>[:port]/<path>/<filename>' has failed
Upgrades Redundant Release Synch Complete
Load installation Load Installation: Cancel Passed
Load Installation: Check Failed
Load Installation: Check Passed
Load Installation: Commit Failed
Load Installation: Commit Passed
Load Installation: Committing New Release
Load Installation: Invoke Failed
Load Installation: Invoke Passed
Load Installation: Load Failed
Load Installation: Load Passed
Load Installation: Programming Load to FLASH
Load Installation: Running from incorrect FLASH bank
Load Installation: Unable to Access Release Files
Load Installation: Unable to Program Load to FLASH


Autonomous events

Performance Monitoring 15-Min Threshold Crossing
1-Day Threshold Crossing
Untimed Threshold Crossing
Photonics DOC Channel Add Completed
DOC Channel Delete Completed
DOC Pre-Check Fail
DOC Pre-Check Pass
DOC Reset TCA Baselines Failed
Protection Protection Exerciser Complete
Protection Switch Initiated
Save and restore Cancel S/R Completed
Cancel S/R Failed
Cancel S/R Failed: Save/Restore not in progress
Check S/R Failed: Blocked by another application
Check S/R Failed: Blocked by presence of alarms
Check S/R Failed: Could not connect to destination
Check S/R Failed: FTP access denied
Check S/R Failed: SFTP access denied
Check S/R Failed: Invalid destination
Check S/R Completed
Check S/R Failed
Check S/R Failed: Blocked by remote application
Check S/R: Restore Blocked by another application
Check S/R: Save Blocked by another application
Database Commit Failed
Database Commit Failed: Restored backup is corrupt
Database Commit: Restart in progress
Database Restore Completed
Database Restore Failed


Autonomous events

Save and restore (continued) Database Restore Failed: Backup not from this node
Database Restore Failed: Backup not from this shelf type
Database Restore Failed: Backup not from this SP family
Database Restore Failed: Backup requires SP protection
provisioning
Database Restore Failed: Blocked by another application
Database Restore Failed: CPU2 Application Unsupported
Database Restore Failed: Incompatible Shelf Assembly
Database Restore Failed: Incompatible SP
Database Restore Failed: SP Protection Not Provisioned
Database Restore Failed: Blocked by presence of alarms
Database Restore Failed: Blocked by remote application
Database Restore Failed: Blocked by unsaved XC config
Database Restore Failed: Blocked By Unsaved CLI Config
Database Restore Failed: Could not connect to source
Database Restore Failed: Failure transferring file
Database Restore Failed: FTP access denied
Database Restore Failed: SFTP access denied
Database Restore Failed: Incompatible options
Database Restore Failed: Incompatible S/R options specified
Database Restore Failed: Interrupted by card restart
Database Restore Failed: Invalid source
Database Restore Failed: Mismatched Software Releases
Save and restore (continued) Database Restore Failed: Restored backup is corrupt
Database Restore in progress
Database Save Failed
Database Restore Failed
Database Save Completed
Database Save Failed


Autonomous events

Database Save Failed: Blocked by another application
Database Save Failed: Blocked by presence of alarms
Database Save Failed: Blocked by remote application
Database Save Failed: Blocked By unsaved SAOS CLI config
Database Save Failed: Blocked by unsaved XC config
Database Save Failed: Could not connect to destination
Database Save Failed: Failure transferring file
Database Save Failed: FTP access denied
Database Save Failed: SFTP access denied
Database Save Failed: Interrupted by card restart
Database Save Failed: Invalid destination
Database Validate Failed
Database Validate Failed: Restored backup is corrupt
Redundant database synch complete
Redundant database synch in progress
Security Password has expired. Contact your Admin.
Password has expired. Change it now
Password will expire in <n> day(s)
Value of n can be between1 to 14 days.
Password will expire today
Intrusion Attempt: <n> time(s) by “intruder”
n= number of intrusion attempt(s)
Signal (for MSPP services) Idle Code Detected
Test Signal Out of Sync
Test Signal Error Received
NPU Lockup
Timing and synchronization Secondary SETS Locking to Primary
Timing Distribution Reference Switch Complete
Timing Generation Reference Switch Complete
Timing Generation Entry to Freerun
Timing Generation Entry to Holdover


Autonomous events

Restart Remote Cold Restart
Cold Restart
Warm Restart
Note: Site Manager does not display the events as event categories. Event categories are used to
organize this table only. In Site Manager, the severity of alerts and events is Log.
Site Manager navigation

The following figures provide an overview of the Site Manager navigation
associated with the Faults and Configuration menus for the 6500. The figure
shows the path from the Site Manager menu bar.

Procedures for alarms and events

Action Details
Setting the time zone for network element or Site Manager timestamps Procedure 2-1 on page 2-12
Retrieving active alarms for one or more network elements Procedure 2-2 on page 2-13
Retrieving events for a network element Procedure 2-3 on page 2-15
Retrieving active disabled alarms Procedure 2-4 on page 2-18
Allowing or inhibiting the display of log, inventory, and database change Procedure 2-5 on page 2-19
events
Clearing security alarms Procedure 2-6 on page 2-20
Procedures for alarm provisioning and alarm profiles

Action Details
Retrieving alarm profiles Procedure 2-7 on page 2-21
Editing an alarm profile Procedure 2-8 on page 2-22
Setting a default profile Procedure 2-9 on page 2-25
Setting a profile as active Procedure 2-10 on page 2-27
Procedures for alarm monitoring and management

Action Details
Restarting a circuit pack or shelf processor Procedure 2-11 on page 2-29
Identifying the circuit pack, pluggable module/port, or facility that has Procedure 2-12 on page 2-38
raised an alarm
Clearing audible alarms and performing lamp tests Procedure 2-13 on page 2-39
Procedures for external alarm provisioning and external controls

Action Details
Provisioning environmental alarm attributes Procedure 2-14 on page 2-42
Provisioning, operating, and releasing external controls Procedure 2-15 on page 2-44

Procedures for Photonic system maintenance

Action Details
Locating a reflective event Procedure 2-16 on page 2-46
Preparing to perform fiber work on a Photonic system Procedure 2-17 on page 2-49
Measuring Photonic amplifier output power Procedure 2-18 on page 2-52
Associated procedures
Some procedures require the user to perform procedures relating to other
topics. Before performing a procedure, if necessary ensure that the
information about the associated procedures is available.
All procedures assume that you have logged in to the network element. Refer
to the interface login and logout procedures in chapter 1 of Administration and
Security, 323-1851-301.

Procedure 2-1
Setting the time zone for network element or Site
Manager timestamps
Use this procedure to set the time zone used for displaying timestamps. The
user can select either the network element time zone or the local operating
system (OS) time zone.
Changes do not take effect until the next launch of Site Manager.
Step Action
1 Select the network element in the navigation tree.

2 Select Preferences from the Edit drop-down menu.
The Preferences dialog box opens.
3 Select 6500 from the Nodal Manager option in the navigation area on the left
of the Preferences dialog box.
4 Select the required radio button (Network Element or Local OS) to set the
time zone used for displaying timestamps.
— Select the Set Defaults button to return the setting to the default
(Network Element).
— The OK and Apply buttons are disabled if the current active time
zone setting is selected.
5 Click OK.
The applied changes do not take effect until the next launch of the Site
Manager. To restart Site Manager, refer to the interface login and logout
procedures in chapter 1 of Administration and Security, 323-1851-301.
—end—

Procedure 2-2
Retrieving active alarms for one or more network
elements
Use this procedure to:
• retrieve the active alarms and alarm details
• access the alarm clearing procedure
• sort active alarms
• filter active alarms
• update active alarms
Step Action
1 Select the desired network element in the navigation tree.

2 Select Consolidated Alarms from the Tools drop-down menu or Active
Alarms from the Fault drop-down menu.
The Consolidated Alarms application opens in a separate window, and
displays the active alarms according to your last filter settings and the alarm
points that are not disabled. Alarms from all logged in network elements are
displayed by default. You can choose to show alarms for one or a set of
specific network elements.
The Active Alarms application opens in a separate tab, and displays the
active alarms according to your last filter settings and the alarm points that
are not disabled. Alarms from all shelves are displayed by default. You can
choose to show alarms from one specific shelf.
3 If you Then
want to sort the active alarms go to step 4
want to filter the active alarms go to step 6
want to update the active alarms go to step 8
want to view details of an active alarm go to step 9
have the required information displayed the procedure is complete
4 Click on a column header to sort the alarms by that column, in ascending

order.
When you first open the Consolidated Alarms application, the columns are
sorted from highest to lowest severity and then from most recent to oldest. All
columns are sorted in alphabetical order except the Time Raised column. The
Time Raised column is sorted by date, then time.

Procedure 2-2 (continued)

Retrieving active alarms for one or more network elements
Step Action
5 Click again on the same column header to sort the alarms in descending
order.
Go to step 3.
6 To hide alarms of a specific severity from the Alarm List, clear the appropriate
check box in the Show area. By default, the Consolidated Alarms or Active
Alarms application displays active alarms of all severities.
The Consolidated Alarms or Active Alarms application updates and no
longer shows the alarms of that severity.
7 To display alarms filtered from the list, select the appropriate check box again
in the Show area.
The Consolidated Alarms or Active Alarms application updates.
Go to step 3.
8 By default, the Auto refresh check box is checked and the alarm list is
updated automatically. To manually update the active alarms, clear the Auto
refresh check box to enable the Refresh button. Click Refresh.
The Last refresh field displays the date (yyyy-mm-dd) and time (hh:mm:ss)
of the most recent update of the Consolidated Alarms or Active Alarms
application.
Go to step 3.
9 To view the details of an alarm, click on the row for the alarm that you want to
see in detail from the list of active alarms.
The Alarm details area at the bottom of the Consolidated Alarms or Active
Alarms application displays the details of the alarm.
You can view the details of only one alarm at a time.
In the Active alarms application, you can click on the How to Clear button to
access the alarm clearing procedure for the selected alarm.
Go to step 3.
—end—

Procedure 2-3
Retrieving events for a network element
• retrieve all events or only disabled alarm events
• retrieve detailed information about an event. For a list of autonomous
events, refer to Table 2-3 on page 2-5.
• sort the event list
• filter the events to display (event severities are critical, major, minor,
warning, cleared, and logged)
• update the events
The timestamp of alarm entries in the Historical Fault Browser application

represents the date and time of the alarm being raised or cleared and not the
actual system occurrences (alarm timestamps include the hold-on and
hold-off periods). As a result, there may be a time discrepancy between an
event and the corresponding alarms being raised or cleared. See the
following:
• Time Raised column will be updated for all raise Events.
• Clear Time column will be updated for all Clear Events and for those Raise
Events, which got Cleared.
• Date Time column indicated the date and time of both Raise and Clear
events. For Raise events, this column will be same as Time Raised column
and for Clear events, this column will be same as Clear Time column.
Attention: When retrieving event counts, the Historical Fault Browser

application includes Events + Events (disabled alarms only) and give the
status bar message as the total. For example if maximum count is 500 for
retrieving events, the status bar message indicates 521. That is, it includes
Events + Events (disabled alarms only).
Step Action

2 Select Historical Fault Browser from the Faults drop-down menu.
You can identify the events by looking for Log in the Severity column. Alerts
also have the Log severity.
If you return to the Historical Fault Browser application during a session, the
application displays the events according to the previous filter settings.


Step Action
3 In the Show area, select the:

• Events radio button to display all events
• Events (Disabled Alarms Only) radio button to display only events
associated with disabled alarms
Attention: If the Events (Disabled Alarms Only) option is selected for a

consolidated node, the Historical Fault Browser application retrieves and
displays information for the primary shelf only. To retrieve events associated
with disabled alarms on member shelves, you must execute the appropriate
TL1 command on individual shelves.
4 If you Then
want to sort the event list go to step 5
want to filter events go to step 7
want to update the Historical Fault go to step 9
Browser application
want to retrieve events details go to step 10
5 Click on a column header to sort the events by that column, in ascending

order.
When you first open the Historical Fault Browser application, the columns
are sorted from most recent to oldest. All columns are sorted in alphabetical
order except the Time Raised column, Clear Time column, and Date, Time
column. The Time Raised column and the Clear Time columns are sorted
by date and then time.
6 Click again on the same column header to sort the events in descending
order.
Go to step 4.
7 To hide events of a specific severity from the events list, clear the appropriate
check box in the Show area.
The Historical Fault Browser application updates and no longer shows the
events of that severity.
8 To display events filtered from the list, select the appropriate check box again
in the Show area.
Go to step 4.


Step Action
9 If the Events radio button is selected, by default, the Auto refresh check box
is checked and the event list is updated automatically. To manually update the
events, clear the Auto refresh check box to enable the Refresh button. Click
Refresh.
If the Events (Disabled Alarms Only) radio button is selected, only manual
refresh is supported. Click Refresh.
of the most recent update of the Historical Fault Browser application.
Go to step 4.
10 From the event list, click on the row for the event that you want to see in detail.
The Event details area at the bottom of the Historical Fault Browser
application displays the details of the event.
You can view the details of only one event at a time.
Go to step 4.
—end—

Procedure 2-4
Retrieving active disabled alarms
• retrieve list of active alarms that are raised against disabled alarm points
• retrieve detailed information about a disabled alarm
• access the alarm clearing procedure
• sort the alarms list
• update the Active Disabled Alarms application manually
Step Action

2 Select Active Disabled Alarms from the Faults drop-down menu.
The Active Disabled Alarms application opens, and displays a list of active
alarms that are raised against disabled alarm points.
3 If you Then
want to sort the active alarms go to step 4
want to update the active alarms go to step 6
want to view details of an active alarm go to step 7
4 Click on a column header to sort the alarms by that column, in ascending

order.
5 Click again on the same column header to sort the alarms in descending
order.
Go to step 3.
6 To update the active alarms, click Refresh.
of the most recent update of the Active Disabled Alarms application.
Go to step 3.
7 To view the details of an alarm, click on the row for the alarm that you want to
see in detail from the list of inhibited alarms.
The Alarm details area at the bottom of the Active Disabled Alarms
application displays the details of the alarm.
You can view the details of only one alarm at a time. Click on the How to
Clear button to access the alarm clearing procedure for the selected alarm.
Go to step 3.
—end—

Procedure 2-5
Allowing or inhibiting the display of log, inventory,
and database change events
Use this procedure to allow or inhibit TL1 autonomous events used for
application refreshes (except for alarms that operate independently of this
option). The TL1 autonomous events are allowed by default.
Step Action

2 Select the Faults drop-down menu. The Update on Data Changes menu
option appears at the bottom of this menu.
If a checkmark appears next to the Update on Data Changes option, the
option is enabled and the TL1 autonomous events used for application
refreshes are allowed.
If a checkmark does not appear next to the Update on Data Changes option,
the option is disabled and the TL1 autonomous events used for application
refreshes are inhibited.
3 To change the status of the Update on Data Changes menu option (to either
allowed or inhibited), select this option from the Faults drop-down menu.
—end—

Procedure 2-6
Clearing security alarms
Use this procedure to clear security alarms (except those raised against the
Primary and Secondary RADIUS servers) on a network element (for example,
Intrusion Attempt).
Step Action

2 Select Clear Security Alarms from the Faults drop-down menu.
3 Click Yes in the confirmation dialog box.
All security alarms (except those raised against the Primary and Secondary
RADIUS servers) are cleared.
The procedure does not unlock channels associated with an Intrusion
Attempt alarm. Refer to the “Unlocking source addresses/users” procedure in
—end—

Procedure 2-7
Retrieving alarm profiles
Use this procedure to retrieve information about alarm profiles and profile
details.
For more information on alarm profiles, refer to “Alarm profiles” on page 1-26.
Step Action

2 Select Alarms & Controls from the Configuration drop-down menu.
3 Select Alarm Profiles.
4 Select an alarm class from the Alarm Class drop-down list.
5 Select a Type from the Type drop-down list.
6 As applicable, select the required criteria from the Shelf, Slot, Port,
Wavelength, MD ID (MA Alarm Class), MA ID (MA Alarm Class) and
STS/VTG/VT (SONET mode) or J/K/L/M (SDH or SDH-J mode) drop-down
lists that are available.
Depending on the shelf function and equipment or facility type you select, the
Shelf, Slot, Port, Wavelength, MD ID (MA Alarm Class), MA ID (MA Alarm
Class) and STS/VTG/VT (SONET mode) or J/K/L/M (SDH or SDH-J mode)
drop-down lists become available as more selections are made.
7 Click Retrieve.
The Profiles table in the upper section of the Alarm Profiles application
displays all of the available alarm profiles for the selection. The Active Profiles
table in the centre section of the Alarm Profiles application displays the
active profiles for the selection.
8 If you want to display details about an alarm profile, select the profile from the
Profiles table in the upper section of the Alarm Profiles application.
The Profile Details table at the bottom of the Alarm Profiles application
displays all the alarm points applicable to the selected profile and their status.
—end—

Procedure 2-8
Editing an alarm profile
CAUTION
Risk of unidentified problem conditions
Disabling an alarm point prevents alarm notification if a
fault occurs.
Use this procedure to edit an existing alarm profile. The procedure allows the
user to change the:
• name of the alarm profile
• status (enabled/disabled) of the alarm points
• Service affecting severity (SA) or Not service affecting (NSA)
severities (Critical, Major, minor, warning)
Alarm provisioning only affects alarm notification and has no effect on the
alarm function.
Attention: You cannot edit the ALL ENABLED, ALL DISABLED, or

FACTORY DEFAULT profiles that the system has defined.
Prerequisites
To perform this procedure, you require an account with at least a level 3 UPC.
Attention: An account with a level 4 UPC or higher is required to edit the

Alarm class of Security alarm points.
Step Action
1 Retrieve the alarm profiles of the network element. Refer to Procedure 2-7,
"Retrieving alarm profiles" on page 21.
2 Select the profile to edit.
You cannot edit the ALL ENABLED, ALL DISABLED, and FACTORY
DEFAULT profiles that the system has defined.


Step Action
3 If you Then
want to change the alarm profile name go to step 4
want to change the status of the alarm points go to step 9
want to change the SA and NSA severity go to step 15
have completed the required changes the procedure is complete
4 Click Edit in the alarm profile list area to open the Edit Profile dialog box.
The Edit Profile dialog box contains the current name of the selected profile.
5 Click in the profile name field and highlight the profile name.
6 Type in the new alarm profile name.
The alarm profile name can be up to 20 characters.
7 Select the Apply to all available shelves within the TID check box if you
want to apply the profile name change to all available shelves.
8 Click OK.
Go to step 3.
9 Select one or more alarm points that you want to enable or disable.
To select multiple alarm points, hold down the Shift or Ctrl key when you
select the alarm points.
10 Click Edit in the alarm point list area to open the Edit Alarm Point dialog box.
11 Click Enabled or Disabled as applicable from the Alarm status drop-down
list.
want to apply the alarm point change to all available shelves.
13 Click OK.
14 Repeat step 9 to step 11 until you have finished editing all the alarm points.
The edited alarm point status is displayed in the Profile details table at the
bottom of the Alarm Profiles application.
Go to step 3.
15 Select one or more alarm points that you want to change the severity.
To select multiple alarm points, hold down the Shift or Ctrl key when you
select the alarm points.
16 Click Edit in the alarm point list area to open the Edit Alarm Point dialog box.


Step Action
17 Select the desired severity for the alarm from the Service affecting severity
or Not service affecting severity drop-down list.
You can provision alarm severities (SA or NSA) as ‘Critical’, ‘Major’, ‘minor’ or
‘warning’.
For BB (except the Supermux circuit pack) and Photonics services, protection
is not supported, therefore most alarms are only raised as service affecting
(SA). As a result, changing the NSA severity has no impact.
want to apply the alarm point change to all available shelves.
19 Click OK.
Go to step 3.
—end—

Procedure 2-9
Setting a default profile
Use this procedure to set the alarm profile of an alarm class as the default
profile.
CAUTION
fault occurs.
Alarm provisioning only affects alarm notification and has no effect on the
alarm function.
Attention: If the 5G 16xOCn circuit pack’s OCn and STSnc facility alarms
were masked by alarm profile in release 5.2/5.3 by the user, after upgrading
to release 6.0, those alarm provisioning profiles for OCn and STSnc on 5G
16xOCn will be enabled automatically.
Attention: You cannot set the default alarm profile for an alarm class for
which the default is fixed at FACTORY DEFAULT (for example, VT1.5/VC11
and VT2/VC12 facilities).
Prerequisites

Step Action
1 Retrieve the alarm profiles of the network element by alarm class. Refer to
Procedure 2-7, "Retrieving alarm profiles" on page 21.
2 Select a profile from the profiles table in the upper section of the Alarm
Profiles application.
3 Click Set As Default.


Setting a default profile
Step Action
4 If you want to apply the default profile to all available shelves, click Yes in the
confirmation dialog.
5 If you do not want to apply the default profile to all available shelves, click No
in the confirmation dialog.
The word Default is displayed in the Alarm Class Default column on the row
of the selected profile.
—end—

Procedure 2-10
Setting a profile as active
CAUTION
fault occurs.
Use this procedure to set the alarm profile of an alarm class as the active
profile.

• Alarm provisioning only affects alarm notification and has no effect on the
alarm function.
• Selecting the ALL DISABLED profile for an alarm class or a specific
equipment/facility disables all alarms for the alarm class or the specific
equipment or facility.
• Selecting the FACTORY DEFAULT profile for Common alarm class
enables all alarms in this class (except LAN-15 and LAN-16, which are
disabled).
Additionally, for MSPP services:

• Selecting the FACTORY DEFAULT profile for VT1.5/VC11 and VT2/VC12
facilities sets the status of the alarm to Not Monitored (disables the
reporting and logging of the defects).
• Alarm monitoring of VT1.5/VC11 and VT2/VC12 facilities is limited to 1344
for each optical interface circuit pack. By default, all VT1.5/VC12 facilities
are set to FACTORY DEFAULT and alarms are not monitored/reported). If
you attempt to provision alarm monitoring (that is, to a profile other than
FACTORY DEFAULT) for greater than 1344 VT1.5/VC11 and VT2/VC12
facilities on an optical interface circuit pack, the request is rejected.
• For MRO, Legacy OCN and MXC cards, all VT1.5/VC11 alarms are not
monitored/reported if the active profile is set to "ALL DISABLED".
Prerequisites



Setting a profile as active
Step Action
1 Retrieve the alarm profiles of the network element. Refer to Procedure 2-7,
"Retrieving alarm profiles" on page 21.
2 Select a profile from the profiles table.
3 Click Set as Active.
The Active profiles table in the centre section of the Alarm Profiles
application displays the active profiles for the selected alarm class.
The Set as Active button is disabled if there are no equipment/facilities
provisioned for the selected alarm class.
—end—

Procedure 2-11
Restarting a circuit pack or shelf processor
CAUTION
A cold restart on an unprotected circuit pack causes traffic
loss. A cold restart on an active protected circuit pack causes
a protection switch that impacts traffic.
As cold restarts can be traffic affecting, you must only perform
a cold restart to restore functionality when all other trouble
clearing procedures have been performed. Before performing
a cold restart, if possible, put the circuit pack out-of-service and
unless it contains unprotected services, contact your next level
of support or your Ciena support group for assistance.
CAUTION
A warm or cold restart of the 2xOSC circuit pack causes a
Wayside Channel (WSC) traffic hit.
CAUTION
A warm or cold restart of the SP in 2-slot shelf w/SP + OTN
Flex MOTR 8xSFP (NTK503MAE5 and NTK503NAE5) can
impact the integrated OTN Flex MOTR traffic.
CAUTION
For Broadband circuit packs that support 1+1 TPT protection,
disconnect the client fibers from the inactive circuit pack prior
to a circuit pack cold restart to avoid causing traffic hits on the
active circuit pack in the protection group.
Use this procedure to initialize a circuit pack or the shelf processor (SP) in a
warm restart or cold restart mode.

• A loss of connectivity to the shelf processor occurs when you restart the
shelf processor. You must wait up to 10 minutes before logging back in.
• In case of SP redundancy a “Redundant Database Synch Failed” alarm is
expected after a warm or cold restart. The alarm will clear automatically


• If SP redundancy is provisioned, both SPs are healthy and available, and

all provisioning data is synchronized between the SP pair:
— a user-initiated warm restart will not result in a shelf processor switch
of activity.
— a user-initiated cold restart will result in a shelf processor switch of
activity.
• If SP redundancy is provisioned and the mate/inactive SP is unhealthy,
unavailable or is unsynchronized:
— a user initiated warm restart will not result in a switch of activity.
— a user initiated cold restart will not result in a switch of activity. The
exception is if the mate/inactive SP is an “IS-ANR,FLT” (In-service,
Abnormal, Fault Detected) state, in which case, there will be a switch
of activity.
• If SP redundancy is not provisioned, a user-initiated restart will not result
in a switch of activity.
• For the L2 MOTR circuit pack, when traffic is on the protection LAG
members and the 1+1 OTN protection facilities, a cold restart of the
inactive L2 MOTR circuit pack will cause traffic hit. A traffic hit will occur
once when the circuit pack begins the cold restart and once again when
the circuit pack comes out of the restart. There is no traffic hit on warm
restarts. For more information on engineering rules of 1+1 LAG protection,
refer to the “1+1 LAG protection” section in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310.
• The SP is integrated into the SPAP circuit pack for a 2-slot shelf variant
(NTK503LA).
Impact of circuit-pack restarts on PM counts

For non-Photonic circuit-packs, current and previous bin PM counts are stored
on the circuit-pack. For Photonic circuit-packs, current and previous bin PM
statistics are stored on the shelf processor. Therefore, a restart of any type on
a non-Photonic circuit-pack clears untimed, current and previous bin PM
counts, and displays "0" for each monitor type along with the invalid data flag
(?). Similarly, a restart of the shelf processor clears untimed, current and
previous bin PM counts for Photonic circuit packs provisioned on the shelf.


For MSPP services:

• For the DSM 84xDS1 TM, equipment protection is 1+1 in a non-revertive
mode.
• If you perform a warm or cold restart on an 8xOC-3/12/STM-1/4 or circuit
pack that is hosting a DSM 84xDS1 TM, you will lose the SDCC link to the
DSM 84xDS1 TM. The SDCC link is re-established automatically.
• After a shelf processor is restarted, the Duplicate Shelf alarm is masked
for 20 minutes.
• A warm or cold restart of the shelf processor causes a transient Line/MS
DCC Link Failure or Section/RS DCC Link Failure alarm on the adjacent
network elements for any circuit pack in the shelf with DCC enabled. The
Line/MS DCC Link Failure or Section/RS DCC Link Failure alarm occurs
towards the end of the restart and lasts for approximately five seconds
before clearing automatically.
• After a shelf processor restart or a time change, the protection exerciser
will resume its schedule on the next calendar day at the provisioned start
time. Also, if you provisioned the number of times the exerciser runs, this
counter is restarted when the exerciser resumes the next day.
• A warm or cold restart of an OC-n/STM-m circuit pack with DCC enabled
causes a Line/MS DCC Link Failure or Section/RS DCC Link Failure alarm
on the adjacent network elements for that circuit pack. The Line/MS DCC
Link Failure or Section/RS DCC Link Failure alarm will clear automatically.
• If the time of day (TOD) synchronization feature is enabled, you do not
have to reprovision the date and time.
• A cold restart of a cross-connect circuit pack can affect traffic if the timing
on the mate cross-connect circuit pack is not locked (Secondary SETS
Locking to Primary warning is present).
Prerequisites
For MSPP and BB services, a warm or cold restart of an interface circuit pack
or shelf processor with GCC0/GCC1 enabled causes a GCC0/GCC1 Link Fail
alarm on the adjacent network elements. The GCC0/GCC1 Link Fail alarm will
clear automatically.
For Photonic services, restarts are only supported on the LIM (SLA, MLA,
MLA2, MLA2 w/VOA, MLA3, and LIM), SAM, ESAM, XLA, SRA, WSS w/OPM,
and 2xOSC circuit packs.


Step Action

2 If you want to perform a Then go to
cold restart step 3
warm restart step 13
3 If the circuit pack you are performing a cold restart on Then go to

contains facilities in an 1+1/MSP linear, 1+1 TPT,1+1 port TPT, step 4
UPSR/SNCP (“From” or “Switch Mate” nodes), 2-Fiber
BLSR/MS-SPRing, 4-Fiber BLSR/MS-SPRing/HERS, and/or
RPR configuration
contains facilities that are all in unprotected or in the “To” node step 7
of UPSR/SNCP configurations
is an 16xSTM1e, 63xE1, 24xDS3/EC-1 or 24xDS3/E3 circuit step 9
pack in an 1:N protection scheme
is an 16xSTM1e, 63xE1, 24xDS3/EC-1 or 24xDS3/E3 circuit step 13
pack in an unprotected scheme
is an interface circuit pack step 11
is a cross-connect circuit pack step 12
is a shelf processor step 13
4 For each facility/path on the circuit pack in an 1+1/MSP linear, 1+1 TPT,1+1
port TPT, UPSR/SNCP, 2-Fiber BLSR/MS-SPRing, 4-Fiber
BLSR/MS-SPRing/HERS, or RPR configuration, perform a manual switch to
verify the inactive path. Refer to the “Operating a protection switch” procedure
in Part 2 of Configuration - Provisioning and Operating, 323-1851-310.
If traffic switches back autonomously to the active path, contact your next
level of support or your Ciena support group.
5 For each facility on the circuit pack in an 1+1/MSP linear,1+1 port TPT, or 1+1
TPT configuration, perform a protection switch. Refer to the “Operating a
protection switch” procedure in Part 2 of Configuration - Provisioning and
Operating, 323-1851-310.
• If the circuit pack to be restarted is the working one (odd slot), operate a
forced switch.
• If the circuit pack to be restarted is the protection one (even slot), operate
a lockout.
6 For each facility/path on the circuit pack in an 2-Fiber BLSR/MS-SPRing,
UPSR/SNCP, 4-Fiber BLSR/MS-SPRing/HERS, or RPR configuration,
operate a forced switch. Refer to the “Operating a protection switch”
procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310.


Step Action
7 If necessary, perform a synchronization protection switch for any line facility

on the circuit pack that is a synchronization reference.
• Retrieve the synchronization details for timing generation and timing
distribution of the circuit pack. Refer to the “Retrieving synchronization
protection status details” procedure in Part 2 of Configuration -
• Perform a manual synchronization protection switch for any active
synchronization facility. Refer to the “Operating a synchronization
Operating, 323-1851-310.
• Perform a lockout synchronization protection switch for the facility. Refer
to the “Operating a synchronization protection switch” procedure in Part
2 of Configuration - Provisioning and Operating, 323-1851-310.
8 If you are performing cold restart on a Broadband circuit pack that supports
1+1 TPT protection, disconnect the client fibers from the inactive circuit pack
prior to the cold restart to avoid causing traffic hits on the active circuit pack
in the protection group.
Go to step 10.
9 Perform a protection switch on the 16xSTM1e, 63xE1, 24xDS3/EC-1 or
24xDS3/E3 circuit pack. Refer to the “Operating a protection switch”
323-1851-310.
• If the circuit pack to be restarted is a working circuit pack, operate a
forced switch.
• If the circuit pack to be restarted is a protection circuit pack, operate a
lockout of protection.
contains facilities which are all in MSP/1+1 linear, 1+1 TPT, step 11
SNCP/UPSR (“From” or “Switch Mate” nodes), 2-Fiber
BLSR/MS-SPRing, 4-Fiber BLSR/MS-SPRing/HERS, and/or
RPR configurations
is a 16xSTM1e, 63xE1, 24xDS3/EC-1 or 24xDS3/E3 working step 12
circuit pack
is a protection circuit pack step 13
11 Change the facility states to out-of-service for all facilities on the circuit pack.
Refer to the “Changing the primary state of a facility” procedure in Part 1 of
Configuration - Provisioning and Operating, 323-1851-310.
To display the Facility details, you must first select the equipment from the
Equipment area of the Equipment & Facility Provisioning application.


Step Action
12 Change the equipment state of the circuit pack to out-of-service. Refer to the
“Changing the primary state of a circuit pack, module, or pluggable”
323-1851-310.
When you place the circuit pack out-of-service, any pluggable modules on
that circuit pack are automatically placed out-of-service.
13 Select Restart from the Faults drop-down menu.
14 If applicable, select the required shelf from the Shelf drop-down list.
15 Select the circuit pack or shelf processor you want to restart from the Card
drop-down list.
16 Select the restart type (warm or cold) from the Restart type drop-down list.
17 Click OK.
18 A Confirm Restart dialog box appears.
If you have chosen the ACTIVE SP to be restarted in the previous menu, then
the confirmation dialog box appears with “CPU1 (main CPU)”, “CPU2” and
“Capture logs before restart” checkboxes.
If you have chosen any other circuit pack to be restarted in the previous menu,
then the confirmation dialog box appears with only “Capture logs before
restart” checkbox. This box will be unchecked by default if you have chosen
a warm restart. For cold restart, the box will be checked by default. For more
information about the “Capture logs” feature, refer to Fault Management -
Customer Visible Logs, 323-1851-840.
Attention: The following circuit packs do not support “Capture logs before
restart” option:
SLA, MLA, MLA2, MLA3, LIM, WSS, OPM, SCMD4, SLIC10, SLIC10 Flex
SMD, CCMD12, DS1TM (DSM which is not inskin), E1, DS3/E3, DS3/EC1,
MXC.


Step Action
19 Click Restart. For an active SP, the restart will take eight to 15 minutes. For
other circuit packs, the restart will take four to 10 minutes to complete. If after
the expected time the retrieve log is not completed, Site Manager will
automatically issue the restart command.
For a warm restart, the red Fail, the green Ready and the blue In Use status
LEDs on the front of the circuit pack go through the following sequence:
• The red and blue LEDs remain in the state they were before the restart.
• After a few seconds, the green LED flashes to indicate the software is
initializing.
(does not flash).
• If the circuit pack has failed, the green LED turns off and the red LED
turns on.
For a cold restart, the red Fail, the green Ready and the blue In Use status
LEDs on the front of the circuit pack go through the following sequence:
• The red LED turns on momentarily.
• After a few seconds, the red, green and blue LEDs turn on.
• After a few seconds, the red and blue LEDs turn off and the green LED
flashes to indicate the software is initializing.
(does not flash).
• If the circuit pack is in-service, the blue LED turns on after the green LED
once the circuit pack is in use. If the circuit pack has failed, the green LED
turns off and the red LED turns on.
20 If you have performed a Then
warm restart the procedure is complete
cold restart on a shelf processor the procedure is complete
cold or warm restart on an 16xSTM1e, 63xE1, the procedure is complete
24xDS3/EC-1 or 24xDS3/E3 circuit pack in an
unprotected scheme
cold restart on an 16xSTM1e, 63xE1, go to step 21
24xDS3/EC-1 or 24xDS3/E3 working circuit
pack
cold restart on a cross-connect circuit pack go to step 21
cold restart on a MSPP circuit pack not listed go to step 22
above
cold restart on an interface circuit pack go to step 21
(converged BB and Photonic services)


Step Action
21 Change the equipment state of the circuit pack to in-service. Refer to the
“Changing the primary state of a circuit pack, module, or pluggable”
323-1851-310.
If the circuit pack you are performing a cold Then
restart on is
a cross-connect circuit pack (MSPP services) the procedure is complete
an 16xSTM1e, 63xE1, 24xDS3/EC-1 or go to step 26
24xDS3/E3 working circuit pack (MSPP
services)
any other circuit pack go to step 23

contains facilities that are all in MSP/1+1 linear, 1+1 TPT,1+1 step 21
port TPT, SNCP/UPSR (“From” or “Switch Mate” nodes),
2-Fiber BLSR/MS-SPRing, 4-Fiber BLSR/MS-SPRing/HERS,
and/or RPR configurations
contains at least one facility in an unprotected or in the “To” step 24
node of UPSR/SNCP configuration
is an 16xSTM1e, 63xE1, 24xDS3/EC-1 or 24xDS3/E3 working step 21
circuit pack
is an 16xSTM1e, 63xE1, 24xDS3/EC-1 or 24xDS3/E3 step 27
protection circuit pack
23 Change the facility states to in-service for all facilities on the circuit pack.
Refer to the “Changing the primary state of a facility” procedure in Part 1 of
For MSPP circuit packs, go to step 24. Otherwise, the procedure is complete.
24 Release any synchronization protection switches performed in step 7. Refer
to the “Releasing a synchronization protection switch” procedure in Part 2 of
25 If applicable, return traffic to the circuit pack by releasing the protection switch
for all facilities on the circuit pack that you performed in step 5. Refer to the
“Operating a protection switch” procedure in Part 2 of Configuration -
The procedure is complete.


Step Action
26 Return traffic to the working 16xSTM1e, 63xE1, 24xDS3/EC-1 or 24xDS3/E3

circuit pack by releasing the forced protection switch for the working circuit
pack that you performed in step 9. Refer to the “Operating a protection switch”
323-1851-310.
27 Release the lockout of protection for the 16xSTM1e, 63xE1, 24xDS3/EC-1 or
24xDS3/E3 protection circuit pack performed in step 9. Refer to the
“Operating a protection switch” procedure in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310. The protection circuit pack is now
available for protection switches.
—end—

Procedure 2-12
Identifying the circuit pack, pluggable module/port, or
facility that has raised an alarm
Use this procedure to identify which circuit pack, module/port, or facility has
raised an alarm.
Note: DPO-related steps only apply to MSPP services.
Step Action
1 Retrieve the active alarms on the network element. Refer to Procedure 2-2,
"Retrieving active alarms for one or more network elements" on page 13.
2 Identify the alarm in the Alarm List. The Unit column in the Consolidated
Alarms or Active Alarms application specifies the circuit pack and circuit
pack slot/port using the following format:
<circuit pack>-<shelf-id>-slot#-subslot# (for subslot equipment alarms) or
<facility type>-<shelf-id>-slot#-subslot# (for subslot facility alarms).
For example, OC3/STM1-8-5-1 refers to an alarm raised by SFP port 1 of the
8xOC-3/12/STM-1/4 optical interface circuit pack in slot 5 on shelf 8.
For circuit packs that do not have SFP/SFP+/XFP/CFP/DPOs, the port
number is used instead of the SFP/SFP+/XFP/CFP/DPO number. For
example, 10GELWT-7-4-1 refers to an alarm raised by the 10GELWT optical
interface circuit pack in shelf 7, slot 4, port 1.
To view details of an alarm, select the alarm in the alarm list.
The Alarm details area displays the details of the alarm.
—end—

Procedure 2-13
Clearing audible alarms and performing lamp tests
Use this procedure to clear audible alarms and perform lamp tests on network
elements and DS1 service modules (DSM) using the ACO button. When you
clear an audible alarm, the alarmed LEDs and fault are not cleared.
This procedure does not apply to 2-slot shelf variants. The Lamp Test on the
2-slot shelf can only be performed using Site Manager.
As of Release 9.2, the SPAP-2 w/2xOSC 2xSFP (NTK555NA) works in the

new 7-slot optical Type 2 shelf (NTK503KA); however, the ACO/Lamp Test
button and LED are located on the fan. Therefore, the Lamp Test button can
be applied, but there will be no Audible alarms to cut-off since there will be no
audible alarm contacts on a shelf with an SPAP-2 w/2xOSC 2xSFP.
The network element and DSM have relay contacts that you can connect to
both visual and audible alarms. There are four contact pairs for a network
element and four contact pairs for a DSM. Therefore, you can connect critical,
major, minor, and remote alarms to separate audible alarms for a network
element or a DSM.
To clear audible alarms and perform lamp tests using the Site Manager
Visualization tool, refer to the “Performing a lamp test and clearing audible
alarms using the Visualization tool” procedure in Administration and Security,
323-1851-301.
Prerequisites
To perform the clearing audible alarms using Site Manager steps, you require
an account with at least a level 2 UPC.
Step Action
1 If you want to Then go to

clear audible alarms manually step 2
clear audible alarms using Site Manager Faults menu step 5
perform a lamp test using the ACO button step 10
perform a lamp test using Site Manager see Note
Note: Refer to the “Performing a lamp test and clearing audible alarms using
the Visualization tool” procedure in Administration and Security
323-1851-301.


Step Action
Clearing audible alarms manually

2 Locate the network element or DSM with the audible alarm.
3 Press the ACO button once to reset the audible alarm relays for the network
element, including all the connected DSMs.
The ACO LED is lit.
Attention: The ACO button and LED is located with the shelf's Critical, Major
and Minor alarm LEDs. For example, they are found on the cooling fan
module Type 2 in a 7-slot shelf, on the maintenance interface card (MIC) in a
14-slot shelf or on the access panel in a 32-slot shelf.
4 If applicable, press the ACO button on the DSM once to reset the audible
alarm relays for the DSM.
Clearing audible alarms using Site Manager Faults menu
6 Select Alarm Cut-Off from the Faults drop-down menu.
The Alarm Cut-Off dialog box is displayed.
7 If applicable, select the required shelf from the Shelf drop-down list.
8 Select All from the Source drop-down list.
If DSMs provisioned, you also have option to clear audible alarms on a
selected DSM (by selecting host OC3 port).
9 Click OK.


Step Action
Performing a lamp test using the ACO button

10 Locate the required network element.
11 Press the ACO button for two seconds, and then release (See the “Attention”
below). If there are:
• no audible alarms, this press performs a lamp test.
• audible alarms, this press clears the audible alarms (ACO LED is lit). A
second press is required to perform a lamp test.
Attention: The ACO button and LED is located with the shelf's Critical, Major
and Minor alarm LEDs. For example, they are found on the cooling fan
module Type 2 in a 7-slot shelf, on the maintenance interface card (MIC) in a
14-slot shelf or on the access panel in a 32-slot shelf.
The ACO LED remains lit until a new major alarm is raised. Upon detection
of a major alarm, the ACO releases and the LED turns off.
Attention: On some access panels, the RJ45 external slot inventory

interfaces appear to have two LEDs but only one is activated during a lamp
test or when the external slot is in use (properly connected to provisioned
external equipment such as a PPC6, CMD44, DSCM, OMD4, BMD2,
UBMD2, MBMD2, or DSCM).
—end—

Procedure 2-14
Provisioning environmental alarm attributes
• retrieve environmental alarm attributes
• set up or change environmental alarm attributes on the network element
or on a DS1 service module (DSM)
• delete defined environmental alarm attributes on the network element or
DSM
Note: DSM-related information and steps only apply to MSPP services.
Environmental alarm attributes require resetting if you replace an existing

environmental alarm with a different type of input. For example, when you
replace a humidity alarm with a toxic gas detector, you must edit the
environmental alarm attributes.
Attention: When you remove a device for detecting an environmental alarm,

delete the environmental alarm attributes.
Prerequisites
Step Action

2 Select Alarms & Controls from the Configuration menu.
3 Select External Alarm Provisioning.
4 Select a shelf from the Shelf drop-down list.
5 Select a source from the Source drop-down list.
edit the environmental alarm attributes step 7
delete the environmental alarm attributes step 16
7 Select any entry in the contact list to enable the Edit button.
8 Click Edit to open the Edit External Alarm dialog box.
9 Select the contact you want to set or edit from the Contact drop-down list.


Provisioning environmental alarm attributes
Step Action
10 Select the label from the Label drop-down list. Refer to “Environmental alarm
labels” on page 2-3.
11 Select the severity from the Severity drop-down list.
12 Edit the description if you want to describe the alarm with specific text.
The description can contain a maximum of 40 characters.
Attention: Do not use apostrophes “ ‘ ” in the alarm text. Using apostrophes

in the alarm text will cause display errors in the OneControl active events list
(AEL).
13 Click Apply.
14 Repeat step 9 through step 13 if you want to set or edit more contacts.
15 Click OK.
16 Select the provisioned contact from which you want to delete attributes in the
contact list as follows:
If you want to delete Then
one entry click the entry you want to delete
some, but not all entries select the first entry in the list and hold down
the Ctrl key while individually clicking on each
required entry
all entries select the first entry in the list and hold down
the Shift key while clicking once on the last
entry in the list
or
select any desired entry in the list and then
Ctrl_A to select all entries
17 Click Clear Entry.

—end—

Procedure 2-15
Provisioning, operating, and releasing external
controls
• retrieve the labels and status of all external controls
• provision control labels and types to control relays on the network element
or DS1 service module (DSM). The network element allows four external
control relays to turn external equipment on and off. There are four contact
pairs on a DSM.
• operate external controls
• release external controls
Prerequisites
To edit external controls, you require an account with at least a level 3 UPC.
To operate or release external control equipment, you require an account with

at least a level 2 UPC.
Step Action
1 Select the required network element in the navigation tree.

2 Select Alarms & Controls from the Configuration drop-down menu.
3 Select External Controls.
4 Select a shelf from the Shelf drop-down list.
5 Select a source from the Source drop-down list.
edit external control attributes step 7
operate (turn on) external control equipment step 11
release external control equipment step 14
7 Click Edit.
8 Select the relay label from the drop-down list at the relay for which you want
to set or edit attributes. Refer to “External control types” on page 2-2.
9 Repeat step 8 if you want to set or edit more relays.
10 Click OK.


Provisioning, operating, and releasing external controls
Step Action
11 Select the required relay.

12 Click Operate.
14 Select the required relay.
15 Click Release.
—end—

Procedure 2-16
Locating a reflective event
Use this procedure to locate connector losses or a reflective event at a line
amplifier site.
In this procedure you will attempt to isolate the connector losses by starting at
the connector that is furthest from the alarmed amplifier and then working
back towards the alarmed amplifier. Refer to Figure 2-1 on page 2-48 for an
example of an alarmed amplifier at a line amplifier site.
Attention: This procedure involves wrapping optical fiber around a mandrel

to create optical power attenuations. Winding the fiber too tightly will damage
optical fibers and the optical power attenuations can generate additional
alarms on the system.
Prerequisites
To perform this procedure, you must:
• observe all safety requirements described in Part 1 of Installation,
323-1851-201 or Fault Management - Module Replacement,
323-1851-545
• have a network diagram that identifies all connection points at the site of
the alarmed module that can be cleaned
Step Action
1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage.
Connect the wrist strap to the ESD jack on the shelf or module.
2 Review the network diagram, and locate the connector that is furthest from
the alarmed amplifier within the site.
3 Wind the optical fiber patch cord attached to the connector, identified in
step 2, four turns around a 15-mm mandrel. You can use a screwdriver handle
or other similar sized cylinder in place of a mandrel.
This step checks for high reflection (low return loss) by causing attenuation of
the optical power in the direction back towards the amplifier output.


Step Action
4 If the original alarm Then

does not clear, and there are more the reflective event is closer to the
optical fiber patch cords before the alarmed amplifier.
alarmed amplifier Go to step 5.
does not clear, and there are no more If you were sent from another
optical fiber patch cords before the procedure, return to the step in the
alarmed amplifier at this site (you are procedure that referred you to this
now at the output of the alarmed procedure. Otherwise, contact your
amplifier) next level of support or your Ciena
support group.
clears Go to step 6.
5 Locate the next furthest connector from the alarmed amplifier and go to
step 3.
6 Place the alarmed amplifier out-of-service (OOS). Refer to the “Changing the
primary state of a facility” procedure in Part 1 of Configuration - Provisioning
and Operating, 323-1851-310.
7
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.
CAUTION
Risk of damage to circuit packs
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical am-
plifier is out of service (OOS), then disconnect or recon-
nect the fiber.
CAUTION
Risk of damage to circuit packs
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.
Clean and then reconnect the output fibers and connectors at the amplifier.
Refer to the “Inspecting and cleaning optical interface connectors” and
“Cleaning optical connectors and adapters on patch cords” procedures in
Part 2 of Installation, 323-1851-201.


Step Action
8 Place the amplifier back in-service (IS). Refer to the “Changing the primary
state of a facility” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
9 If the original alarm Then
clears the procedure is complete
does not clear return to the step in the procedure that referred you to
this procedure or contact your next level of support or
your Ciena support group
—end—
Figure 2-1
Locating connector losses at a Photonic line amplifier site (with DSCM)
Automatic Power Reduction Active (APR) alarm
Amplifier Amplifier
DSCM
Patch panel #1
Patch panel #2
Patch panel #3
Patch panel #4
B A
Out In
3 3
DSCM
A 1 B
2 In Out
Legend
Indicates the reflection point (actual problem point in this example).
1 Perform mandrel test on optical fiber patch cord at 1 . In this

example, the APR alarm is not cleared, because the
optical power attenuation is occurring after the reflection point ( ).
2 Backtrack in direction towards alarmed amplifier port. Perform mandrel

test on optical fiber patch cord 2 . In this example the alarm clears
because attenuated optical power is reflected.
3 Clean connectors at 3 on both sides of the DSCM. Ensure amplifier

is OOS before cleaning connectors.
Note 1: If alarm does not clear, the problem is likely with the patch panel or DSCM.
Note 2: Although the measurement is done at the output port, the APR alarm is raised
against the AMP facility attached to the input port. Therefore, the APR alarm is raised
against the input port.

Procedure 2-17
Preparing to perform fiber work on a Photonic system
Use this procedure to record existing power levels and amplifier gain settings
before performing fiber maintenance/repair and to re-adjust these parameters
if the fiber maintenance/repair causes power levels to change.
Note that this procedure cannot be used to repair a fiber cut that occurred.
This procedure can only be used to prepare in advance for a fiber cut that you
know will occur (for example, related to scheduled maintenance activities).
CAUTION
Placing an amplifier circuit pack OOS causes traffic loss. It is
recommended that this procedure be performed during a
maintenance window (when traffic is lightest), or that all traffic
be routed away from the affected network element before
performing this procedure.
CAUTION
Risk of damage to downstream amplifier
You must complete this procedure on an amplifier that is
downstream of the location where the fiber cut or maintenance
activity will be performed. Not performing this procedure can
result in power levels at the amplifier that are high enough to
damage the module.
Prerequisites
• use an account with at least a level 3 UPC
323-1851-545
Step Action
1 Log into the network element containing the amplifier that is downstream of
the location where the fiber cut or maintenance activity will be performed.
2 From the Configuration menu, select Equipment & Facility Provisioning.


Step Action
3 Select the LIM circuit pack supporting the AMP facility (of the amplifier that is
downstream of the location where the fiber cut or maintenance activity will be
performed) in the Equipment area.
4 From the Facility Type drop-down menu, select AMP.
5 Record the Target Gain for the AMP facility of the amplifier that is
downstream of the location where the fiber cut or maintenance activity will be
performed.
6 From the Performance menu, select Performance Monitoring and then
New.
7 From the Type drop-down list, select AMP.
8 From the Facility drop-down list, select the AMP facility of the amplifier that
is downstream of the location where the fiber cut or maintenance activity will
be performed.
9 Retrieve the PMs for the AMP facility.
10 Record the current (Untimed) Input Power (OPIN).
11 From the Configuration menu, select Photonics Services and then
Domain Optical Controller (DOC).
12 Change the DOC Primary State to out of service (OOS). Refer to the “Editing
the DOC Settings” procedure in Part 2 of Configuration - Provisioning and
Operating, 323-1851-310.
13
CAUTION
Placing an amplifier circuit pack OOS causes traffic
loss. It is recommended that this procedure be
performed during a maintenance window (when traffic
is lightest), or that all traffic be routed away from the
affected network element before performing this
procedure.
Place the amplifier downstream of the fiber cut/maintenance OOS. Refer to

the “Changing the primary state of a facility” procedure in Part 1 of
14 Perform the maintenance/repair fiber according to the safety requirements of
your company and the safety requirements described in Part 1 of Installation,
323-1851-201 or Fault Management - Module Replacement, 323-1851-545.
15 Repeat step 1 to step 10.
16 Compare the current (Untimed) Input Power (OPIN) to the previously
recorded value in step 10.


Step Action
17 If the Input Power (OPIN) Then

value has
decreased by more than 3 dB check the fiber splice and fiber connections.
It is likely that the splice is poor or there is a
dirty connection. Correct the problem and
go to step 18.
increased by more than 3 dB provision the downstream OOS amplifier
Target Gain downwards by the difference in
the input power. For example, if the input
power increased by 4 dB and the previous
amplifier Target Gain was 18 dB, the new
amplifier Target Gain will be
18 dB - 4 dB = 14 dB.
Go to step 18.
otherwise go to step 18
18 Place the amplifier downstream of the fiber cut/maintenance from step 13

back in service (IS). Refer to the “Changing the primary state of a facility”
323-1851-310.
19 Place the DOC Primary state back in service (IS). Refer to the “Editing the
DOC Settings” procedure in Part 2 of Configuration - Provisioning and
Operating, 323-1851-310.
20 Reset all threshold crossing alert (TCA) baselines for the DOC domain. Refer
to the “Resetting TCA baselines” procedure in Part 2 of Configuration -
21 Record the current DOC Automation mode. Change the DOC Automation
mode to “Enhanced”. Refer to the “Editing the DOC Settings” procedure in
22 Wait for DOC to perform optimization. This may take up to five minutes to
begin.
23 Once optimization is complete, return the DOC Primary state and DOC
Automation mode to their original settings.
—end—

Procedure 2-18
Measuring Photonic amplifier output power
Use this procedure to measure the output power of an amplifier to facilitate
Photonic line troubleshooting.
Prerequisites
323-1851-545
• have a high-powered optical power meter with the same optical
connectors as the network element that can read power levels as high as
+11 dB
• have a 10 dB fixed-pad optical attenuator (ensure the attenuator loss value
has been calibrated)
CAUTION
Disconnecting fibers causes traffic loss on the associated
facilities. It is recommended that this procedure be performed
during a maintenance window (when traffic is lightest), or that
all traffic be routed away from the affected network element
before performing this procedure.
Step Action
1 In the Domain Optical Controller (DOC) application in Site Manager, record

the current Automation mode for the two DOC network elements that
manage each optical direction of the amplifier.
Change the Automation mode to “Enhanced Auto Monitor Only” (if not
already). Refer to the “Editing the DOC Settings” procedure in Part 2 of
2 Wear an antistatic wrist strap to protect the shelf from static damage. Connect
the wrist strap to the ESD jack on the shelf.
3 Place a 10 dB fixed-pad optical attenuator at the input to the optical power
meter (to prevent raising the Automatic Power Reduction Active alarm).


Step Action
4 If you want to measure the amplifier output power of Then go to

port 5 (Line B) step 5
port 7 (Line A) step 10
5 In the Equipment & Facility Provisioning application in Site Manager,

record the current AMP facility Shut Off Threshold (dBm) value for Line A
(port 8) on both line-facing ends of the amplifier. Refer to the “Retrieving
equipment and facility details” procedure in Part 1 of Configuration -
6 Provision the AMP facility Shutoff Threshold to -60 dBm for Line A (port 8)
on both line-facing ends of the amplifier. This must be performed using the
ED-AMP TL1 command:
ED-AMP::<AID>:CTAG:::,,,,,,SHUTTHRES=-60,,,,,:,,;
Refer to ED-AMP command in TL1 Description, 323-1851-190.
Attention: Provisioning the SAM, ESAM or AMP facility Shutoff Threshold

to -60 dBm disables the ALSO safety feature, and injury can occur.
The Automatic Shutoff Disabled alarm will raise.
Attention: ALSO can be disabled on the LIM cards (C-Band and L-Band) by
setting the ALSO_Disable flag to TRUE for the OPTMON facility. This action
should only be performed when there is no OSC in the OTS for automatic
recovery from optical line fail condition.
7 Remove the OSC B In (port 3) fiber from the amplifier. This allows you to
measure the amplifier output only. If the OSC B In (port 3) fiber is not
removed, you are also including the OSC channel in the measurement.


Step Action
8
DANGER
CAUTION
Disconnecting fibers causes traffic loss on the
associated facilities. It is recommended that this
procedure be performed during a maintenance window
(when traffic is lightest), or that all traffic be routed away
from the affected network element before performing
this procedure.
Measure the port 5 (Line B) amplifier output power using the high-powered
optical power meter. Add the calibrated attenuator loss to the measured
value. This total power is 10 dB lower due to the attenuator inserted into the
power meter.
9 Clean and reinstall the OSC B In (port 3) fiber removed in step 7. Refer to the
cleaning connectors procedures in chapter 7 of Part 2 of Installation,
323-1851-201.
Go to step 11.
10
DANGER
CAUTION
Disconnecting fibers causes traffic loss on the
associated facilities. It is recommended that this
procedure be performed during a maintenance window
(when traffic is lightest), or that all traffic be routed away
from the affected network element before performing
this procedure.
Measure the port 7 (Line A) amplifier output power using the optical power
meter. Add the calibrated attenuator loss to the measured value. This total
power is 10 dB lower due to the attenuator inserted into the power meter.


Step Action
11 When the power measurement is complete, clean all connections of the

optical fiber link following your company standards, and restore the fiber
connection to the amplifier output port. Refer to the cleaning connectors
procedures in chapter 7 of Part 2 of Installation, 323-1851-201.
12 If port 5 (Line B) was measured, then restore the AMP facility Shut Off
Threshold (dBm) value for Line A (port 8) to the original settings recorded in
step 5 for both line-facing ends of the amplifier. This must be performed using
the ED-AMP TL1 command:
ED-AMP::<AID>:CTAG:::,,,,,,SHUTTHRES=<step 5 recorded
value>,,,,,:,,;
13 In the Domain Optical Controller (DOC) application in Site Manager, restore
the Automation mode to the original settings recorded in step 1 for both
DOC network elements. Refer to the “Editing the DOC Settings” procedure in
—end—


323-1851-543
3-1
Alarm hierarchies and alarm severities 3-
Attention: Alarm severities described in this chapter are the default alarm
severities provisioned on the system. Alarm severities can be modified by
using different alarm profiles. Refer to Chapter 2, “Alarm surveillance” of this
document for details on how to change alarm severities.
Alarm severities
The levels of severity for alarms are critical (C), major (M), and minor (m).
Alarm reports always contain a notification code that identifies the alarm
severity, or the code CL to indicate that the fault has been cleared. The w code
indicates a warning. The A code indicates an alert (only applicable to alarm
banner). Event reports have a Logged (Log) severity.
Attention: Alarm severities can be modified (protected/unprotected). Refer

to Procedure 2-8, “Editing an alarm profile” on page 2-22 of this document.
Critical alarms (C)

Critical alarms are the most severe. Critical alarms always indicate a
service-affecting fault. For example, unprotected facility losses and
unprotected facility-carrying equipment failures raise critical alarms.
Major alarms (M)

Major alarms are less severe than critical alarms but can be service-affecting
or non-service-affecting.
Major alarms are raised when something has an effect on a low-speed facility.
For example, a major alarm is raised when tributary signals fail or unprotected
provisioned circuit packs are missing.

3-2 Alarm hierarchies and alarm severities
Minor alarms (m)

Minor alarms are less severe but can be service-affecting or
non-service-affecting.
For example, a non-service-affecting minor alarm is raised when a protected

circuit fails. However, an AIS service-affecting minor alarm raises when a
1+1/MSP linear protected configuration does not have protection available.
Cleared alarm notification (CL)

The cleared notification code indicates that the fault no longer exists. The
automatic output cache stores the cleared alarm reports.
Warning (w)
Warning events are raised by the Network Element as Standing Conditions
(SC), and are less severe than minor alarms. A warning is an indication a
problem exists on the network element that can eventually escalate into an
alarm of higher severity.
Alert (A)
Threshold-crossing alerts are less severe than alarms. An alert can indicate
that the threshold crossed does not affect service but requires further
investigation.
Alerts are indicated in the alarm banner and appear with a Logged (Log)
severity in the Events window.
Logged (Log)
Event reports are generated from changes of state and other important
transient conditions.
Service-affecting and non-service-affecting severities

By default, alarms generally have both a service-affecting (high impact)
severity and non-service-affecting (low impact) severity. The triggered severity
depends on the system state when the alarmed conditions occurred. For
some alarms, there is only one severity. The user can perform alarm
provisioning, which can be used to enable/disable alarm points, and change
the service-affecting (high impact) severity and non-service-affecting (low
impact) severities of alarms. Refer to “Procedures for alarm provisioning and
alarm profiles” on page 2-10.

For example, a Circuit Pack Fail alarm can be raised with a:

• high impact of Critical, service-affecting (C, SA) for a circuit pack in an
unprotected configuration with cross-connects
• low impact of Minor, non-service-affecting (m, NSA) for a circuit pack
without cross-connects
MSPP and Broadband services circuit pack alarms

The service-affecting (high impact) severity is applicable when the circuit pack
is unprotected (that is, either it cannot be protected, or can be protected but
currently is not) and has a connected traffic facility.
The non-service-affecting (low impact) severity is applicable when the circuit

pack is:
• protected but inactive
• unprotected and has a traffic facility that is either disconnected or
protected but inactive
MSPP and Broadband services facility alarms

The service-affecting (high impact) severity is applicable when the facility is
connected (Broadband facilities are connected but not through the
cross-connect circuit pack) and unprotected.
The non-service-affecting (low impact) severity is applicable when the facility

is:
• disconnected
• protected, but inactive
Photonic services alarms

Photonic alarms do not support multiple severity levels. That is, there is only
one severity per alarm .

Alarm hierarchies
The following alarm hierarchy diagrams are made to be as generic and simple
as possible. Therefore, not every alarm or circumstance shown applies to all
circuit packs.
• Overall alarm hierarchy on page 3-7
• Equipment alarm hierarchy (circuit packs and modules) on page 3-8
• Equipment alarm hierarchy (pluggable I/O panels and I/O carriers) on
page 3-9
• Equipment alarm hierarchy (provisioned pluggables) on page 3-10
• Equipment alarm hierarchy (unprovisioned pluggables) on page 3-10
• Shelf equipment alarm hierarchy on page 3-11
• DS1 service module alarm hierarchy on page 3-12
• DS3 facility alarm hierarchy - coax to optics direction on page 3-13
• DS3 facility alarm hierarchy - optics to coax direction on page 3-14
• E1 hardware alarm hierarchy on page 3-15
• E1 line alarm hierarchy on page 3-15
• E3 alarm hierarchy - coax to optics direction on page 3-16
• E3 alarm hierarchy - optics to coax direction on page 3-17
• EC-1 facility alarm hierarchy on page 3-18
• ETH10G and FC1200 facility alarm hierarchy on page 3-19
• FC1200 alarm hierarchy for 2x10G OTR, 4x10G OTR, and 4x10G MUX
circuit packs on page 3-20
• FC400/FC800 alarm hierarchy for 2x10G OTR, 4x10G OTR, and
4x10G MUX circuit packs on page 3-21
• 4x10G OTR (NTK530QA) circuit pack infiniband alarm hierarchy on page
3-22
• 100G OCI circuit pack ETH100G facility alarm hierarchy on page 3-23
• 40G OCI+ CFP circuit pack ETH40G facility alarm hierarchy on page 3-24
• 40G MUX OCI circuit pack 10GbE WAN facility alarm hierarchy on page
3-25
• LAN/WAN EPL facilities alarm hierarchy (ETH, ETH100,
FC100/FC200/FC400, GE, and WAN facilities) on page 3-26
• EFM alarm hierarchy for SuperMux circuit pack ETH facility on page 3-28
• L2SS, 20G L2SS, and PDH gateway circuit pack alarm hierarchy on page
3-29

• 20G L2SS and L2 MOTR circuit pack maintenance alarm hierarchy on

page 3-30
• FLEX MOTR, 8xOTN Flex MOTR, and (1+8)xOTN Flex MOTR circuit
packs OC-n/STM-n client protocols alarm hierarchy on page 3-30
• FLEX MOTR and Broadband circuit packs Fiber Channel, 8B10B, and
Transparent client protocols alarm hierarchy on page 3-31
• 8xOTN Flex MOTR and (1+8)xOTN Flex MOTR circuit packs Fiber
Channel, 8B10B, and Transparent client protocols alarm hierarchy on
page 3-32
• 8xOTN Flex MOTR and (1+8)xOTN Flex MOTR circuit packs WAN facility
alarm hierarchy on page 3-33
• (1+8)xOTN Flex MOTR client port facility OTM mapping layer alarm
hierarchy on page 3-34
• (1+8)xOTN Flex MOTR client port facility (low-order ODU0, ODU1, and
ODUFLEX facilities) alarm hierarchy on page 3-35
• 4x10G PKT I/F circuit pack OTN PKT facility alarm hierarchy - faceplate to
fabric direction (RX) on page 3-36
• 4x10G PKT I/F circuit pack OTN mapped Ethernet facility alarm hierarchy
on page 3-37
• 4x10G PKT I/F circuit pack (terminated) Ethernet facility OTN alarm
• OC-n/STM-n facility alarm hierarchy (Broadband circuit packs) on page
3-39
• OC-n/STM-n and STS/VT/VC facility alarm hierarchy (MSPP optical
interface circuit packs) on page 3-40
• L2 MOTR circuit pack ETH100/ETH/ETH10G facility alarm hierarchy on
page 3-41
• L2 MOTR circuit pack WAN facility alarm hierarchy on page 3-42
• OTM1/OTM2/OTM3 facility alarm hierarchy on page 3-43
• 100G OCLD circuit packs line port OTM4 facility alarm hierarchy on page
3-44
• 10x10GE MUX OCI circuit pack backplane port 100 OTM4 facility alarm
• 100G OCI circuit pack client port OTM4 facility alarm hierarchy on page
3-46
• 100G OCI circuit pack client port OTM4 mapping layer facility alarm
• OTM2 mapping facility (associated with FC1200, OC-192/STM-64, and
ETH10G facility) alarm hierarchy on page 3-48

• TCM facility alarm hierarchy - faceplate to backplane direction on page

3-49
• TCM facility alarm hierarchy - backplane to faceplate direction on page
3-50
• Photonic optical signal facilities alarm hierarchy on page 3-51
• RPR circuit pack alarm hierarchy on page 3-52
• RPR circuit pack LAN port alarm hierarchy on page 3-53
• STM-1e alarm hierarchy on page 3-53

Overall alarm hierarchy
Equipment Alarms
Exceptions
1. The Line/MS DCC Link Failure and

Section/RS DCC Link Failure alarms are
masked by OCn/STMm equipment failure
alarms and the STMm facility alarms
LOS and LOF.
2. Line/MS DCC Link Failure and

Section/RS DCC Link Failure alarms will
raise once the LOS/LOF alarm is cleared.
Facility Alarms
Line (OC/STM)
Alarms
Path (STS/HO
VC) Alarms
Path (VT/LO
VC) Alarms

Equipment alarm hierarchy (circuit packs and modules)
Higher priority
Circuit Pack
Missing
Provisioning
Incompatible
Circuit Pack
Mismatch
Circuit Pack
Failed
Interface
Circuit Pack
XC
Intercard
SP Intercard Suspected
Suspected
Internal Mgmt
Comms Suspected Internal Mgmt
Internal Mgmt Comms Suspected
Comms Suspected
Incomplete
Software Lineup
Duplicate SID Circuit Pack Circuit Pack Circuit Pack

Detected Failed - Sync Failed - Traffic Upgrade Failed
Software Circuit Pack

Mismatch Circuit Pack Latch Open
Latch Open
Circuit Pack
Latch Open
Lower priority

Equipment alarm hierarchy (pluggable I/O panels and I/O carriers)
Higher priority
Pluggable I/O Panel Missing

Circuit Pack Missing/
Mismatch/Failed
alarms
Pluggable I/O Panel Mismatch
Pluggable I/O Carrier Missing
Pluggable I/O Carrier Mismatch
Pluggable I/O Carrier Mismatch
Intercard Suspected
(SP and Pluggable I/O Carrier)
Pluggable I/O Carrier Fail
Pluggable equipment alarms
Lower priority

Equipment alarm hierarchy (provisioned pluggables)
Higher priority
Circuit Pack
Missing - Pluggable
Circuit Pack
Mismatch - Pluggable
Circuit Pack
Failed - Pluggable
Intercard
Suspected - Pluggable
Lower priority
Equipment alarm hierarchy (unprovisioned pluggables)
Higher priority
Circuit Pack Unknown - Pluggable
Autoprovisioning Mismatch - Pluggable
Lower priority

Shelf equipment alarm hierarchy
Power Failure -
Low Voltage
Power Power
Failure A Failure B
Software Config- Loss of Signal

uration Unknown ESI -A/ESI - B
Software Loss of Frame

Upgrade Failed ESI -A/ESI - B
Software Upgrade Timing Distribution Timing Generation AIS

in Progress Loss of Reference Loss of Reference ESI -A/ESI - B
Timing Generation Excessive Error

Failure to Lock Rate ESI -A/ESI - B
Fan Failed
Circuit Pack Missing Shelf Power Near
Fan Failed
(power input cards) Limit
Equipment
Configuration
Mismatch
Equipment Configuration
Mismatch
Corrupt Inventory
Data
Fan Incompatible
Circuit Pack Missing Circuit Pack Missing

(power input cards) (MIC, Access Panel)
Power Failure - Corrupt Inventory Equipment Corrupt Inventory

Power Failure Data Configuration
Fuse Blown (note) Data
Mismatch
Power Failure - A/B
Note: This alarm is raised only against fused power cards equipped with an optional alarms indicator fuse. If
the alarm indicator fuse or the fuse holder cartridge is physically removed, this alarm will be masked by the
Power Failure - A/B alarm.

DS1 service module alarm hierarchy
DSM CP Hierachy
DSM CP alarms
DSM mate is
CP missing reporting that
it is missing/
not available
and CP missing
OAM not
available
Mate OAM is
unavailable
CP Mismatch/
Unknown
CP failed
CP Loss of Host Intercard

Timing Ref. suspect
DSM shelf Hierachy
DSM SITE provisioning required OAM not available

(All provisioned DSM CPs
have no OAM link to the DSM)
DSM shelf alarms DSM CP alarms
Low Voltage
Fan Missing Power Failure A/B
Fan Failure

DS3 facility alarm hierarchy - coax to optics direction
DS3 Rx LOS
DS3 Rx LOF
DS3 Rx AIS DS3 Rx BPV DS3 Rx FREQ
DS3 Rx FFM
DS3 Rx RAI Signal Degrade
Legend
AIS = alarm indication signal
BPV = bipolar violation
LOF = loss of frame
LOS = loss of signal

DS3 facility alarm hierarchy - optics to coax direction
STS1 AIS
STS1 LOP
STS1 UEQ
STS1 SLM
DS3 Tx LOF STS1 PTM
STS1 RFI
DS3 Tx AIS
DS3 Tx FREQ
DS3 Tx RAI
Legend
LOF = loss of frame
LOP = loss of pointer
PTM = path trace monitoring
RFI = remote fault indicator
SLM = signal label mismatch
UEQ = unequipped

E1 hardware alarm hierarchy
Higher priority I/O Panel

Missing
I/O Panel
Unknown
I/O Panel
Mismatch
Protection Sub-module
Missing
Protection Sub-module
Unknown
Lower priority Protection Sub-module

Mismatch
E1 line alarm hierarchy
Loss of Signal Higher priority
Excessive Error
Rate
AIS
Loss of Frame
Loss of Multiframe
Lower priority

E3 alarm hierarchy - coax to optics direction
E3 Rx LOS
E3 Rx LOF
E3 Rx AIS E3 Rx BPV
E3 Rx RDI
Legend
BPV = bipolar violation
LOF = loss of frame
RDI = remote defect indicator

E3 alarm hierarchy - optics to coax direction
STS1 AIS
STS1 LOP
STS1 UEQ
STS1 SLM
E3 Tx LOF STS1 PTM
E3 Tx AIS STS1 RFI
Legend
LOF = loss of frame
PTM = path trace monitoring
UEQ = unequipped

EC-1 facility alarm hierarchy
EC1 Rx LOS
Higher priority
EC1 Rx LOF
EC1 Rx AIS
EC1 Rx RFI EC1 Rx SD STS Rx LOP
STS Rx AIS
STS Rx UEQ
STS Rx SLM
STS Rx RFI VT Rx LOP
VT Rx AIS
Lower priority
VT Rx UEQ
Legend
LOF = loss of frame
SD = signal degrade
UEQ = unequipped

ETH10G and FC1200 facility alarm hierarchy

The ETH10G facility on the 1x10GE EPL circuit pack follows this ETH10G
alarm hierarchy, but does not raise the OCH alarms. For the LAN/WAN alarm
hierarchy, refer to the “LAN/WAN EPL facilities alarm hierarchy (ETH,
ETH100, FC100/FC200/FC400, GE, and WAN facilities)” on page 3-26.
EG =
UNI ETHn
drop facility
OOS
CP and
pluggable
equipment
alarms
Ethernet
Loss of signal
Loss of
Clock
Loss of Data Synch
Loss of frame
Loopback
Excessive Error Enable
Ratio
No masking
Local fault Remote fault
OCH
RX power
LOFEF triggered
out of range

FC1200 alarm hierarchy for 2x10G OTR, 4x10G OTR, and 4x10G MUX
circuit packs
EG =
UNI ETHn
drop facility
OOS
CP and
pluggable
equipment
alarms
Ethernet
Loss of signal
Loss of Clock
(Not applicable to 4x10G OTR)
Excessive Error Loss of Data Synch

Ratio
Loopback
Enable
No masking
Local fault Remote fault
OCH
RX power
LOFEF triggered
out of range

FC400/FC800 alarm hierarchy for 2x10G OTR, 4x10G OTR, and

4x10G MUX circuit packs
Note that FC400 applies to the 4x10G OTR NTK530QA variant only.
EG =
UNI ETHn
drop facility
OOS
CP and
pluggable
equipment
alarms
Ethernet
Loss of signal
Loss of Clock
(Not applicable to 4x10G OTR)
Loss of Data Synch
Fiber Channel Link

Not Operational
Loopback
Enable
No masking
OCH
RX power
LOFEF triggered
out of range

4x10G OTR (NTK530QA) circuit pack infiniband alarm hierarchy

The infiniband alarm hierarchy for the 4x10G OTR NTK530QA variant circuit
pack applies to PSIFB PROTOCOL FLEX facilities.
All alarms in Rx direction

unless specified otherwise
Equipment alarms or Facilities OOS
Loss of Signal LOFEF Triggered (Tx)
Rx Power Out Of Range

100G OCI circuit pack ETH100G facility alarm hierarchy

The ETH100G facility on the client port of 100G OCI circuit pack supports the
following alarm hierarchy.
CP and Plug Equipment Alarms, 100 GE Fac OOS, AINS, MT
100GE
Loss of Signal LOFEF Triggered
Loss of Clock Power Out of Range
Loss of Frame
Loss of Data Sync

Excess Error Ratio
Local Fault Remote Fault

40G OCI+ CFP circuit pack ETH40G facility alarm hierarchy

The ETH40G facility on the client port of 40G OCI+ CFP circuit pack supports
the following alarm hierarchy.
CP and Plug Equipment Alarms, 40 GE FAC OOS, AINS, MT
40GE
Loss of Signal LOFEF Triggered
Loss of Clock Power Out of Range
Loss of Frame
Loss of Data Sync

Excess Error Ratio
Local Fault Remote Fault

40G MUX OCI circuit pack 10GbE WAN facility alarm hierarchy
Circuit Pack Fail, pluggable equipment alarms,

OTM2 mapping layer, WAN OOS
Loss of Frame Delineation Link Down (WAN)
Client Service
Far-End client Rx SF
Mismatch

LAN/WAN EPL facilities alarm hierarchy (ETH, ETH100,

FC100/FC200/FC400, GE, and WAN facilities)
For the ETH10G alarm hierarchy, refer to the “ETH10G and FC1200 facility
alarm hierarchy” on page 3-19.
For the ETH100G alarm hierarchy, refer to the “FC1200 alarm hierarchy for
2x10G OTR, 4x10G OTR, and 4x10G MUX circuit packs” on page 3-20.
The VT alarms apply only to the 24x10/100BT EPL with 8xSFP circuit pack.
The EFM alarms apply only to the 24x10/100BT EPL with 8xSFP and 4xGE
EPL EFM circuit packs.
For EFM alarm hierarchy on SuperMux ETH, refer to “EFM alarm hierarchy for
SuperMux circuit pack ETH facility” on page 3-28.

Release 9.3
(L) Remote Power Fail (L) LOS/Link Pulse Missing
(L) Remote Receiver Fail (L) Loss of Data Synch

(W) WAN Link Down
(L) Remote Invalid Config (L) EFM Link Fail alarms STS/VT Path alarms
(not raised on EPL cards)
(L) Discovery Protocol Fail (L) LAN Link Down
(L) Rx Ethernet Idle
(L) Subtended
(L) Remote Client
Client Link Down (VT) Ext-PLM
Copyright© 2010-2013 Ciena® Corporation

(L) Excessive Error Ratio
Link Down
(L) Signal Degrade (S,VT,P) Loss of Multiframe - VCAT
(S,VT,P) Loss of Sequence - VCAT

(L) Loopback Fail - Remote (L) Loopback Active - Facility
(S,VT,P) Loss of Alignment - VCAT
(L) Loopback Active - Terminal
(L) Loopback Active - Remote
(W) Loss of Frame Delineation
(W) Excessive Error Ratio (W) Client Service Mismatch
Legend (W) Signal Degrade (W) Far End Client Signal Failure
(L) = alarm per LAN port
(W) = alarm per WAN port
(S) = alarm per STS
(VT) = alarm per VT
June 2013
323-1851-543 Standard Issue 1
Fault Management - Alarm Clearing, Part 1 of 2
EFM alarm hierarchy for SuperMux circuit pack ETH facility
LOS/Link Pulse Missing Remote Loopback Fail
Loss of Data Synch Remote Loopback Active
Remote Power Fail Indication
Remote Invalid Configuration

LAN Link Down
CPE Discovery Protocol Fail
Remote Client Circuit Pack Remote Client Circuit Pack Remote Power Remote Line High Received
Unknown - Pluggable Missing - Pluggable Supply 1/2 Missing Optical Power / Remote Line
Low Received Optical Power
Remote Client Circuit Pack Remote Client Circuit Pack
Mismatch - Pluggable Failed - Pluggable
Remote Client Link Down
Rx Ethernet Idle Remote Client High Received

Optical Power / Remote Client
Excessive Error Ratio Low Received Optical Power
Signal Degrade

(G) LAG Fail
Release 9.3
(G) LAG Partial Fail (L) Remote Port Unreachable (L) LACP Failed
(L) LOS/Link Pulse Missing (L) Remote Port OOS
(L) Remote Power Fail (L) Loss of Data Synch

(L) Far End Client Rx Signal Failure

(L) Remote Reciever Fail
(L) EFM Link Fail Alarms (VT) Extended Payload Mismatch

(L) Remote
(L) Remote Client Link Down
Invalid Config (W) WAN Link Down
(P) AIS*
(L) Excessive Error Ratio (L) LAN Link Down
(L) Discovery Protocol Fail

(P) Loss of Frame*
(L) Remote Client Link Down (L) Signal Degrade
(W) LCAS Rx Mismatch (P) Loss of Multiframe**
(W) LCAS Tx Total

Loss of Capacity (P) RDI
(L) Loopback Fail - Remote
(W) LCAS Rx Total Loss of Capacity
(S,V,T,P) Loss of Multiframe - VCAT
(W) LCAS Tx Partial
(L) Loopback Active - Remote Loss of Capacity
(W) LCAS Rx Partial Loss of Capacity (S,V,T,P) Loss of Sequence - VCAT
(S,V,T,P) Loss of Alignment - VCAT

(W) Loopback Traffic Detect
LEGEND
* - On DS3, Loss of Frame masks AIS (W) Loss of Frame Delineation
** - Only applicable to E1
(L) - alarm per LAN port
(W) - alarm per WAN port (W) Excessive Error Ratio (W) Client Service Mismatch
(S) - alarm per STS
(V) - alarm per VT (non STS) (W) Signal Degrade (W) Far End Client Signal Failure
(G) - alarm per LAG port
(P) - alarm per PDH (DS1/E1/DS3/E3)
- Alarms below are not masked when LCAS is enabled, unless all VCG members have defects.
NOTE : Only the PDH facilities (DS1/E1/DS3/E3) are supported on the PDH gateway circuit pack
L2SS, 20G L2SS, and PDH gateway circuit pack alarm hierarchy
June 2013
20G L2SS and L2 MOTR circuit pack maintenance alarm hierarchy
(M) Cross connect Error
(M) CCM Error
(M) Remote CCM Error
(M) MAC Status Defect
(M) Remote Defect Indication
(M) – alarm per Maintenance Association
FLEX MOTR, 8xOTN Flex MOTR, and (1+8)xOTN Flex MOTR circuit
packs OC-n/STM-n client protocols alarm hierarchy
l l l l
l l l
l
l
l l l l
l l
l
l l

FLEX MOTR and Broadband circuit packs Fiber Channel, 8B10B, and
Transparent client protocols alarm hierarchy
l Plug larms
l l Client Signal lure
l
l
l Client
l l l l
l
l l Applies only
l l Applies only
l Applies only

8xOTN Flex MOTR and (1+8)xOTN Flex MOTR circuit packs Fiber
Channel, 8B10B, and Transparent client protocols alarm hierarchy

8xOTN Flex MOTR and (1+8)xOTN Flex MOTR circuit packs WAN
facility alarm hierarchy

(1+8)xOTN Flex MOTR client port facility OTM mapping layer alarm
hierarchy
HO OTM1 and OTM2 FLEX/OTM0, 1, FLEX

faults Facility OOS
ODU0/1/FLEX
Connection OOS
Loss of Frame
OTM0 and MultiFrame
OTM1 ODU Loss of
OTMFLEX Multi Frame
ODU LCK ODU AIS ODU OCI

OPU
HO OTM1 ODU ODU TTI LO OTMn and OPU PTI Mismatch

BDI ODU BDI
Mismatch Payload alarms
Far End Client

Signal Failure
OPU AIS

(1+8)xOTN Flex MOTR client port facility (low-order ODU0, ODU1, and
ODUFLEX facilities) alarm hierarchy
HO OTM1 and OTM2

faults
MSI Mismatch
Loss of Frame
and MultiFrame
ODU
ODU LCK ODU AIS ODU OCI
ODU BDI

4x10G PKT I/F circuit pack OTN PKT facility alarm hierarchy -
faceplate to fabric direction (RX)

4x10G PKT I/F circuit pack OTN mapped Ethernet facility alarm
hierarchy

4x10G PKT I/F circuit pack (terminated) Ethernet facility OTN alarm
hierarchy

OC-n/STM-n facility alarm hierarchy (Broadband circuit packs)
CP Equipment
Facility OOS
Alarms
(masked by
(masked by
SP)
SP)
Section
LOFEF Initialization in
Loss of Signal triggered Progress
Loss of Clock Rx Power Out

of Range
Loss of Frame Loss of Frame
Trace Identifier
Mismatch
Line * If the Trace Fail mode is set to Line Fail

** If the Trace Fail mode is set to Alarm Only
Loss of Frame
* Trace Identifier
Mismatch (section)
AIS
Signal Fail RFI ** Trace Identifier

Mismatch (section)

OC-n/STM-n and STS/VT/VC facility alarm hierarchy (MSPP optical

interface circuit packs)
Higher Loss of Signal Laser Off Far End Failure

priority (OC/STM) Triggered (Broadband)
Loss of Frame RX Power Out

(OC/STM) of Range
Note:
DCC Link Fail * Trace Identifier * Position of the Trace Identifier Mismatch
(OC/STM) Mismatch (OC/STM) (OC/STM) alarm in the hierarchy if the
section trace fail mode is on.
AIS ** Position of the Trace Identifier Mismatch
(OC/STM) (OC/STM) alarm in the hierarchy if the
section trace fail mode is off.
RFI/RDI Traffic Squelched Signal Fail ** Trace Identifier DCC Link Fail
(OC/STM) (STS/HO VC) (OC/STM) Mismatch (OC/STM) (OC/STM)
AIS Signal Degrade

(STS/ HO VC) (OC/STM)
Loss of Pointer
(STS/HO VC)
Unequipped Excessive Error

(STS/HO VC) Rate (STS/HO VC)
Signal Label Mismatch Signal Degrade

(STS/HO VC) (STS/HO VC)
Trace Identifier Traffic Squelched

Mismatch (STS/HO VC) (VT/LO VC)
RFI/RDI AIS
(STS/HO VC) (VT/LO VC)
Loss of Pointer
(VT/LO VC)
Unequipped Excessive Error

(VT/LO VC) Rate (VT/LO VC)
Signal Label Mismatch Signal Degrade

(VT/LO VC) (VT/LO VC)
Trace Identifier
Mismatch (VT/LO VC)
Lower
RFI/RDI
priority
(VT/LO VC)

Release 9.3
(G) LAG Fail
(G) LAG Partial Fail
(L) * LOS/Link Pulse Missing (L) LAN Link Down

(L) * Remote Power Fail (L) * Loss of Data Synch
(L) * Remote Reciever Fail
(L) EFM Link Fail Alarms (L) Local Fault (L) Remote Fault (L) Remote Port Unreachable (L) LACP Failed
(L) * Remote Invalid Config

(L) * Discovery Protocol Fail (L) Excessive Error Ratio (L) Remote Port OOS
(L) Signal Degrade

(L) * Remote Client Link Down
(L) Far End Client Rx Signal Failure
(L) Loopback Fail - Remote

(M) Cross connect Error
(L) Loopback Active - Facility
(L) Loopback Active - Remote
(L) Loopback Active - Terminal
(M) CCM Error
(M) Remote CCM Error
NOTES (M) MAC Status Defect

(L) alarm per LAN port
(G) alarm per LAG port
(M) alarm per Maintenance Association (M) Remote Defect Indication
L2 MOTR circuit pack ETH100/ETH/ETH10G facility alarm hierarchy
June 2013
L2 MOTR circuit pack WAN facility alarm hierarchy
Circuit Pack Failed
SFP Missing/Failed/Unknown
(W) WAN Link Down

(W) Loss of Frame Delineation
(W) Client Service Mismatch (W) Excessive Error Ratio
(W) Far End Client Rx Signal Failure (W) Signal Degrade
NOTE
(W) alarm per WAN port

OTM1/OTM2/OTM3 facility alarm hierarchy

OTM1/OTM2/OTM3 facility alarms are masked by upstream facility failures.
Ocn Facility CP & Plug

OOS (masked Equipment Alarms
by SP) (masked by SP)
OTU OCH * only applicable

Loss of Signal LOFEF to WT circuit
triggered *** packs
** not applicable
Loss of Clock ***,**** Manual to 40G circuit
Rx Power Out packs
of Range Provisioning
Required
FEC Enable **,
Loss of Frame *** ****
FEC Enable
TR Control *** not applicable
**, ****
Disabled *, *** to L2MOTR/Flex
Tx Tuning in MOTR circuit packs
Pre-FEC OTU Signal Progress
Signal Fail ***,**** Fail *** **** not applicable
TR Control to OTM1 client
Echo Trace Facilities on the
GCC1
Mismatch *** OTN MOTR 4x2.5G
deleted ****
Loopback
TR Control Enable
GCC0 Pre-FEC Signal OTU Loss of
Initialization in
Link Fail Degrade***,**** BDI Multiframe
Progress *, ***
OTU Trace TR Control IS

Identifier Optimization in
Mismatch Progress *, ***
ODU
Multiplexed Rate
Mismatch ***, ****
Loss of
GCC1 Multiframe
deleted ****
GCC1 Link
Fail ODU LCK ODU AIS ODU OCI
OPU
ODU Trace OCn/STMm alarms OPU AIS

ODU BDI (refer to OCn/STMm
Identifier
Mismatch facility alarm
hierarchy) ***
OPU Payload
Type
Mismatch
Note 1: Regen and mated configurations: only OTU alarms apply
Note 2: Protected and unmated configurations: OTU and ODU alarms apply

100G OCLD circuit packs line port OTM4 facility alarm hierarchy
CP Equipment Alarms, OTM4 FAC OOS, AINS, MT
OTM4
RX Power Out of range
Loss of Signal
* RX Channel Power
OTU * Loss of Channel Out of range
Loss of Clock TR Control Disabled
OTU Loss of Frame TR Control Echo Trace Mismatch
TR Control Initialization in
OTL Skew Out of Range Progress
FEC TR Control is Optimization in
Disable Progress FEC
OTU SF (preFEC) OTU SD (BIP 8)
Enable
GCC0
FEC
Deleted
GCC0 Link Fail Loss of Multi Frame Disable
OTU BDI OTU SD (PreFEC)
CP Alarm
ODU-AIS **OTL Skew Out of Range OTU TTI Mismatch OTM4
ODU-OCI Manual FAC
ODU-LCK Provisioning OOS
Required
ODU ODU-OCI ODU-AIS ODU-LCK TX tuning

In progress
OCH
ODU TTI Mismatch ODU-BDI
* Only applicable to colorless capable 100G OCLD variants when they are
deployed on colorless system
** Only applicable to BPSK Mode. Detection and report are disabled if maintenance
signal is present.
Note1: Regen and mated configurations: only OTU alarms apply
Note 2: Protected and unmated configurations: OTU and ODU alarms apply

10x10GE MUX OCI circuit pack backplane port 100 OTM4 facility
alarm hierarchy
CP & Plug Equipment Alarms, OTM4 Fac OOS, AINS, MT
OTM4
OTU OCH
GCC1
Deleted ODU-OCI ODU-AIB ODU-LCK
GCC1 Link Fail
OPU
ODU-BDI ODU TTI Mismatch OPU-AIS PT Mismatch
ODU

100G OCI circuit pack client port OTM4 facility alarm hierarchy
CP Equipment Alarms, OTM4 FAC OOS, AINS ON
OTM4
OTU Loss of Signal
RX Power Out
of range
Loss of Clock
OTU Loss of Frame

FEC
Disable
OTU PreFEC SF OTU SD (BIP 8)
GCC0 FEC
Deleted Enable
GCC0 Link Fail Loss of Multi Frame OTU BDI OTU PreFEC SD FEC
Disable
OTU TTI Mismatch
ODU ODU-OCI ODU-AIS ODU-LCK
ODU-BDI ODU TTI Mismatch
OCH

100G OCI circuit pack client port OTM4 mapping layer facility alarm
hierarchy
CP Equipment Alarms, OTM4 FAC OOS, AINS ON

OTM4
OTU OCH
ODU
GCC1
Deleted ODU-OCI ODU-AIS ODU-LCK
GCC1 Link Fail
ODU-BDI ODU TTI Mismatch
OPU
R8+ OPU-CSF PT Mismatch OPU-AIS R7XP1

OTM2 mapping facility (associated with FC1200, OC-192/STM-64, and

ETH10G facility) alarm hierarchy
ODU3
OCI/LCK/
ODU2 AIS
connection
OOS Loss of
ODU Multiframe
Multiplexed Rate
Mismatch
GCC1
deleted
GCC1 Link
Fail ODU LCK ODU AIS ODU OCI
OPU
ODU3
BDI
ODU Trace OPU AIS
ODU BDI
Identifier
Mismatch
Path Trace
Identifier
Mismatch

TCM facility alarm hierarchy - faceplate to backplane direction

TCM facility alarm hierarchy - backplane to faceplate direction

Photonic optical signal facilities alarm hierarchy

Photonic facility alarms are masked by upstream facility failures.
Optical Line
Fail Automatic Shutoff
Disabled
Automatic
Shutoff
Shutoff Threshold Automatic Power

Crossed Reduction Active
AMP Facility
Input Loss
of Signal
Output Loss
of Signal
Gage TCA
Summary
OPTMON facility OSC facility
Optical Line Fail OSC Loss of Signal
OSC OSPF
Loss of Signal OSC Signal Degrade
Adjacency Loss
Gauge TCA
Summary

RPR circuit pack alarm hierarchy
Circuit Pack (S) AIS Event

Failed
SFP Missing/ (G) LAG Fail (S) Loss of Multiframe

Failed/Unknown
(G) LAG
Partial Fail (S) Loss of Sequence
(L) LOS/Link
Pulse Missing
(L) LAN
Link Down (S) Loss of Alignment
(L) Loss of
Data Synch (W) Loss of
(L) LAN
timeout Event Frame Delineation
(L) Excessive
Error Ratio
(W) Excessive (W) Client
Error Ratio Service Mismatch
(L) Signal
Degrade
(W) Signal
Degrade (W) WAN
Link Down
(W) Forced Ring (R) Topology (R) Max Stations (R) Isolated (W) Ring
Switch Active Instability Exceeded Station Failure
(W) Manual Ring (R) Topology (W) Ringlet

Switch Active Failure Failure
Legend
(L) = alarm per LAN port
(W) = alarm per WAN port
(S) = alarm per STS
(R) = alarm per RPR port
(G) = alarm per LAG
= Alarm triggers

RPR circuit pack LAN port alarm hierarchy
Loss of signal
Loss of Data Synch (LAN) Link down
Rx Excessive Error Ratio
Rx Signal Degrade
STM-1e alarm hierarchy
EQPT Fail
STM1e Rx Line LOS
STM1e Rx Line LOF
STM1e Rx Line AIS
STM1e Rx Line Trace STM1e Rx Line RFI STM1e Rx Line EBER

Identifier Mismatch
STM1e Rx Line SD


323-1851-543
4-1
Alarm clearing procedures—A to H 4-
Attention: The alarm clearing procedures are presented in two chapters,

“Alarm clearing procedures—A to H” (this chapter) and Alarm clearing
procedures—I to Z (in Part 2 of this document). The complete “List of alarms”
is included in both chapters. The numbers in brackets after the alarm names
are the alarm IDs.
This release of 6500 Packet-Optical Platform (6500) supports the MSPP,

Broadband, PKT/OTN transport and switched, and Photonic services for
different MSPP, Broadband, PKT/OTN I/F, and Photonic circuit packs. The
combination of two or all services is also supported.
For more information on the services (and the circuit packs related to each
service) offered in this release, refer to chapter 2 in Part 1 of 6500 Planning,
NTRN10CF.
This chapter provides procedures for clearing single and generic alarms.
Generic procedures are used for clearing more than one alarm type.
A complete list of alarms is provided in this document. Refer to the List of

alarms on page 4-5 to determine whether you must perform a specific or a
generic alarm clearing procedure to clear the alarm.
A list of alarms per alarm class is provided for each circuit pack in the 6500
circuit pack-based documents (323-1851-102.x).
Abbreviations used in this chapter

AIS Alarm Indication Signal
ALS Automatic Laser Shutdown
AM1/AM2 Analog Maintenance version 1/2
AMP Amplifier
APS Automatic Protection Switching
ASE Amplified Spontaneous Emission

4-2 Alarm clearing procedures—A to H
BDI Backward Defect Indication

BIP Breaker Interface Panel
BLSR Bidirectional Line-Switched Ring
BMD Broadband Mux/Demux
BPV Bipolar Violation
CFP 100G transceiver form factor pluggable
CHMON Channel Monitoring
CMD44 44 Channel Mux/Demux
CMF Client Management Frame
CP Circuit Pack
CPE Customer Premise Equipment
DCC Data Communications Channel
DCN Data Communications Network
DIP Dual In-line Package
DOC Domain Optical Controller
DPO DWDM pluggable optics
DS1 Digital Signal Level 1
DSCM Dispersion Slope Compensation Modules
DSM DS1 Service Module
DUS Do not Use for Synchronization
DWDM Dense Wavelength Division Multiplexing
EDP Engineering Documentation Package
EFM Ethernet in the First Mile
EPL Ethernet Private Line
ES Errored Second
ESD Electrostatic Discharge
ESI External Synchronization Input
ESO External Synchronization Output
ETH Ethernet
FC Fiber Channel
FE Fast Ethernet
FEC Forward Error Correction
FICON Fiber Connection
FPGA Field Programmable Gate Array
GCC General Communication Channel
GE Gigabit Ethernet
GFP-F Generic Framing Procedure - Framed
GFP-T Generic Framing Procedure - Transparent
HERS Head End Ring Switching
HO High Order

IOP I/O Panel

IS In-Service
L2SS Layer 2 Service Switch
LACP Link Aggregation Control Protocol
LAG Link Aggregation Group
LAN Local Area Network
LCAS Link Capacity Adjustment Scheme
LED Light-Emitting Diode
LIM Line Interface Module
LO Low Order
LOFEF Laser Off Far-End Fail
LOF Loss of Frame
LOS Loss of Signal
MIC Maintenance Interface Card
MLA Midstage Line Amplifier
MS Multiplex Section
MSP Multiplex Section Protection
MS-SPRing Multiplex Section-Shared Protection Ring
NNS Network Name Server
NSA Non-Service-Affecting
OBM Optical Bandwidth Manager
OC Optical Carrier
OCI Optical Channel Interface
OCLD Optical Channel and Laser Detector
ODU Optical Channel Data Unit
OMD4 4 Channel Optical Mux/Demux
OMX Optical Multiplexers
OOS Out-of-Service
OPU Optical Channel Payload Unit
OPM Optical Power Monitor
OSC Optical Service Channel
OSI Open Systems Interconnection
OSNR Optical Signal to Noise ratio
OST Optical System Topology
OTDR Optical Time Domain Reflectometer
OTR Optical Transponder
OTM Optical Transport Module
OTN Optical Transport Network
OTSC Optical Transponder and Service Channel
OTU Optical Channel Transport Unit

PDH Plesiosynchronous Digital Hierarchy

PEC Product Engineering Code
PSI Payload Structure Identifier
RAI Remote Alarm Indication
RDI Remote Defect Indicator
RFI Remote Fault Indicator
ROADM Re-configurable Optical Add-Drop Multiplexer
RPR Resilient Packet Ring
RS Regenerator Section
SA Service-Affecting
SD Signal Degrade
SDH Synchronous Digital Hierarchy
SETS Synchronization Equipment Timing Source
SLA Single Line Amplifier
SLAT System Lineup and Test
SFP Small Form Factor Pluggable
SNCP Subnetwork Connection Protection
SONET Synchronous Optical Network
SP Shelf Processor
SPLI Service Photonic Layer Interoperability
SPPC Section Peak Power Controller
SSH Secure Shell Protocol
SSM Synchronization Status Message
SSU Synchronization Supply Unit
STM Synchronous Transport Module
STM-1e Synchronous Transport Signal Level-1 Electrical
STS Synchronous Transport Signal
SWT Shelf Wavelength Topology
TOD Time of Day
TPT Transponder protection tray
TTI Trail Trace Identifier
UNI Uni-directional
UPI User Payload Identifier
UPC User Privilege Code
UPSR Unidirectional Path-Switched Ring
VCAT Virtual Concatenation

VC Virtual Container
VCG Virtual Concatenation Group
VCS Virtual Circuit Segment
VT Virtual Tributary
WAN Wide Area Network
WSS w/OPM Wavelength Selective Switch with Optical Power Monitor
WT Wavelength Translator
XC Cross-Connect
XFP 10G transceiver form factor pluggable
XLA Switchable Line Amplifier
Associated procedures
Some procedures require the user to perform procedures relating to other
topics. Before performing a procedure, if necessary, ensure the information
about the associated procedures is available.
All procedures assume that you have logged in to the network element. Refer
to the “Interface login and logout” procedures in chapter 1 of Administration
and Security, 323-1851-301.
List of alarms
The complete list of alarms is included here. However, the alarm clearing
procedures are presented in two parts (A to H and I to Z). The alarm clearing
procedures beginning with A to H are included in this chapter. Additionally,
non-hyperlinked references to procedures beginning with I to Z (included in
Part 2 of this document) are provided here.
A
1+1/MSP linear and 1+1 TPT APS alarms on page 4-22
Adjacency Discovery Unreliable on page 4-25
Adjacency Far End Not Discovered on page 4-27
Adjacency Mismatch on page 4-30
Adjacency Provisioning Error on page 4-33
AIS (DS1), see DS1 Receive alarms on page 4-202
AIS (DS3/E3), see DS3 and E3 Receive alarms on page 4-209
AIS (E1), see E1 Receive alarms on page 4-231
AIS (EC-1), see EC-1 Receive alarms on page 4-243
AIS (ESI), see ESI alarms on page 4-270
AIS (OC/STM), see Secondary alarms in Part 2 of this document
AIS (STS/HO VC), see Secondary alarms in Part 2 of this document

AIS (VT/LO VC), see Secondary alarms in Part 2 of this document

AIS (OC48/192/768/STM16/64/256 for BB services), see Secondary
alarms in Part 2 of this document
AIS (OTUTTP, STTP), see Secondary alarms in Part 2 of this document
Alarm and Event Throttling Active on page 4-36
Alarm Provisioning Near Limit on page 4-37
All Provisioned RADIUS Accounting Servers Unavailable on page 4-38
All Provisioned RADIUS Servers Unavailable on page 4-40
ALS Disabled on page 4-41
ALS Triggered - Laser is shutdown on page 4-42
Automatic Power Reduction Active on page 4-43
Automatic Shutoff on page 4-47
Automatic Shutoff Compromised on page 4-48
Automatic Shutoff Disabled on page 4-49
Auto Protection Switch Acknowledge Time Out on page 4-51
Autoprovisioning Mismatch on page 4-53
Autoprovisioning Mismatch - Pluggable on page 4-55
B
Backplane ID Module 1/2 Failed on page 4-56
Bipolar Violations (DS1), see DS1 Receive alarms on page 4-202
Bipolar Violations (DS3/E3), see DS3 and E3 Receive alarms on page
4-209
Bipolar Violations (E1), see E1 Receive alarms on page 4-231
C
Calibration Required on page 4-58
CCM Error on page 4-59
Channel Controller: Failure Detected on page 4-60
Channel Controller: Unexpected Loss Detected on page 4-64
Channel Degrade on page 4-70
Channel Opacity Error on page 4-74
Circuit Pack Configuration Save Failed on page 4-75
Circuit Pack Failed on page 4-76
Circuit Pack Failed - Pluggable on page 4-82
Circuit Pack Failed-Sync and Circuit Pack Failed-Traffic on page 4-84

Circuit Pack Latch Open on page 4-86

Circuit Pack Mate Mismatch on page 4-88
Circuit Pack Mismatch on page 4-89
Circuit Pack Mismatch - Pluggable on page 4-95
Circuit Pack Missing on page 4-96
Circuit Pack Missing - Pluggable on page 4-105
Circuit Pack 3rd Party - Pluggable on page 4-106
Circuit Pack Operational Capability Exceeded on page 4-107
Circuit Pack Unknown on page 4-109
Circuit Pack Unknown - Pluggable on page 4-112
Circuit Pack Upgrade Failed on page 4-114
Client Service Mismatch on page 4-116
CMF UPI Mismatch on page 4-118
COLAN-A OSPF Adjacency Loss, see OSPF Adjacency Loss alarms in
Part 2 of this document
COLAN-A Port Failure, see LAN alarms in Part 2 of this document
COLAN-X OSPF Adjacency Loss, see OSPF Adjacency Loss alarms in
COLAN-X Port Failure, see LAN alarms in Part 2 of this document
Cold Restart Required: FPGA Changed on page 4-120
Config Mismatch - LCAS on page 4-122
Configuration Mismatch on page 4-124
Configuration Mismatch - Adv BW Limit on page 4-125
Configuration Mismatch - Common ID on page 4-126
Configuration Mismatch - Concatenation on page 4-127
Configuration Mismatch - Link ID on page 4-128
Configuration Mismatch - Node on page 4-129
Configuration Mismatch - Primary State on page 4-130
Corrupt Inventory Data on page 4-131
CPE Discovery Protocol Fail on page 4-134
CP Loss of Host Timing Ref. on page 4-136
CPU2 Unreachable on page 4-137
CPU2 Warm Restart Required on page 4-138
Craft Load Missing on page 4-139

Craft Load Unpacking Aborted - Low Disk Space on page 4-140

Cross-connection Mismatch on page 4-141
Cross connect Error on page 4-145
Crossed Fibers Suspected on page 4-146
D
Database Auto Save in Progress on page 4-147
Database Integrity Fail on page 4-148
Database Integrity Fail - CPU2 on page 4-149
Database Not Recovered For Slot on page 4-150
Database Recovery Incomplete on page 4-151
Database Restore in Progress on page 4-153
Database Save and Restore Failed on page 4-154
Database Commit Failed on page 4-157
Database Save in Progress on page 4-159
DCC Link Fail alarms on page 4-160
Debug Port in Use on page 4-166
Delay Measurement Enabled on Slave Node (6500) on page 4-167
Delay Measurement Failed (6500) on page 4-168
Delay Measurement Mismatch Capability (6500) on page 4-169
Disk 75 percent Full, see Disk Full alarms on page 4-170
Disk 90 percent Full, see Disk Full alarms on page 4-170
Disk Full, see Disk Full alarms on page 4-170
DOC Action: Channel Add In Progress on page 4-172
DOC Action: Channel Delete In Progress on page 4-173
DOC Action Failed: Add on page 4-174
DOC Action Failed: Delete on page 4-177
DOC Action Failed: Monitor on page 4-180
DOC Action Failed: Optimize on page 4-183
DOC Action: Fault Detected on page 4-186
DOC Consecutive Re-Opt Threshold Crossed on page 4-189
DOC Domain Not Optimized on page 4-192
DOC Invalid Photonic Domain on page 4-194
DOC Power Audit Failed on page 4-199

Domain Optical Controller Disabled on page 4-201

DS1 Receive alarms on page 4-202
DS3 and E3 Receive alarms on page 4-209
Dormant Account Detected on page 4-218
DSM-Host Misconnection on page 4-219
Duplicate Adjacency Discovered on page 4-222
Duplicate IP Address on page 4-223
Duplicate Primary Shelf on page 4-225
Duplicate Shelf Detected on page 4-227
Duplicate Site ID on page 4-229
E
E1 Receive alarms on page 4-231
E1 Transmit alarms on page 4-236
EC-1 Receive alarms on page 4-243
Equipment Configuration Mismatch on page 4-248
Equipment OOS with Subtending Facilities IS on page 4-251
Equipment Reconfiguration In Progress on page 4-253
Error alarms (ETH, ETH10, ETH40G, ETH100G, FLEX, WAN, ETTP) on
page 4-254
Error alarms (OC/STM, STS/HO VC, and VT/LO VC) on page 4-261
ESI alarms on page 4-270
Ethernet LAN Port failure, see LAN alarms in Part 2 of this document
Event Log full on page 4-276
Loss of Frame (ESI), see ESI alarms on page 4-270
Excessive Error Rate (STS/HO VC and VT/LO VC), see Error alarms
(OC/STM, STS/HO VC, and VT/LO VC) on page 4-261
Excessive Error Ratio (ETH, ETH10, ETH40G, ETH100G, ETH100,
FC800, FC1200, FLEX, WAN, ETTP), see Error alarms (ETH, ETH10,
ETH40G, ETH100G, FLEX, WAN, ETTP) on page 4-254
Excessive Input Power on page 4-277
Excessive Pointer Adjustments (EC-1), see EC-1 Receive alarms on page
4-243
F
Facility Reconfiguration In Progress on page 4-278
Facility Reconfiguration Required on page 4-279

Fan Failed on page 4-280

Fan Failed (DSM) on page 4-284
Fan Housing Missing on page 4-285
Fan Incompatible on page 4-287
Fan Missing (DSM) on page 4-289
Far End Client Signal Fail on page 4-290
Far End Protection Line Fail on page 4-292
Fiber Channel Link Not operational on page 4-293
Fiber Loss Detection Disabled on page 4-294
Fiber Type Manual Provisioning Required on page 4-295
Filler Card Missing on page 4-296
Filter Replacement Timer Expired on page 4-297
Flash Banks Mismatch on page 4-299
Forced Ring Switch Active, see Protection Switch Active alarms in Part 2
of this document
Forced Switch Active, see Protection Switch Active alarms in Part 2 of this
document
Frame Format Mismatch (DS3), see DS3 and E3 Receive alarms on page
4-209
Frequency Out of Range (DS1), see DS1 Receive alarms on page 4-202
Frequency Out of Range (DS3), see DS3 and E3 Receive alarms on page
4-209
Frequency Out of Range (OC192/STM64, ETH10G) on page 4-300
G
Gauge Threshold Crossing Alert Summary on page 4-301
GCC0/GCC1/GCC2 Link Failure on page 4-306
GCC/GCC0/GCC1/GCC2 OSPF Adjacency Loss, see OSPF Adjacency
Loss alarms in Part 2 of this document
Group Loss of Signal on page 4-310
H
High Fiber Loss on page 4-312
High Received Span Loss on page 4-316
High Temperature on page 4-318
High Temperature Warning on page 4-322

I
ILAN-IN OSPF Adjacency Loss, see Part 2 of this document
ILAN-IN Port Failure, see Part 2 of this document
ILAN-OUT OSPF Adjacency Loss, see Part 2 of this document
ILAN-OUT Port Failure, see Part 2 of this document
Incomplete Software Lineup, see Part 2 of this document
Input Loss of Signal, see Part 2 of this document
Integrated Test Set Configured, see Part 2 of this document
Integrated Test Set Data Save In Progress, see Part 2 of this document
Intercard Suspected, see Part 2 of this document
Intercard Suspected - Pluggable, see Part 2 of this document
Intercard Suspected - Pluggable I/O Carrier 1, see Part 2 of this document
Intercard Suspected - Pluggable I/O Carrier 2, see Part 2 of this document
Internal Database Sync in Progress, see Part 2 of this document
Internal Mgmt Comms Suspected, see Part 2 of this document
Intrusion Attempt, see Part 2 of this document
Invalid Site Topology, see Part 2 of this document
I/O Module Mismatch, see Part 2 of this document
I/O Module Missing, see Part 2 of this document
I/O Module Unknown, see Part 2 of this document
I/O Panel Mismatch, see Part 2 of this document
I/O Panel Missing, see Part 2 of this document
I/O Panel Unknown, see Part 2 of this document
Isolated Station, see Part 2 of this document
L
LACP Failed, see Part 2 of this document
LAN alarms, see Part 2 of this document
Laser Off Far End Failure Triggered (OC-192/STM-64, OC-768/STM-256,
ETH10G, OTM2, FC1200), see Part 2 of this document
Line A Input OTDR High Loss detected, see Part 2 of this document
Line A Input OTDR High Reflection detected, see Part 2 of this document
Line DCC Link Failure, see DCC Link Fail alarms on page 4-160
Link Aggregation Group Fail, see Part 2 of this document
Link Aggregation Group Partial Fail, see Part 2 of this document

LINE/MS DCC OSPF Adjacency Loss, see Part 2 of this document

Link Down, see Part 2 of this document
Link Pulse Missing, see Part 2 of this document
Local Fault (ETH10G, FC1200), see Part 2 of this document
Lockout Active, see Part 2 of this document
Lockout of Protection Active, see Part 2 of this document
Lockout of Working Active, see Part 2 of this document
Lockout Protection Active, see Part 2 of this document
Lockout Working Ring Active, see Part 2 of this document
Log Collection In Progress, see Part 2 of this document
Log Save In Progress, see Part 2 of this document
Loopback Active, see Part 2 of this document
Loopback Active - Facility, see Part 2 of this document
Loopback Active - Terminal, see Part 2 of this document
Loopback Traffic Detected, see Part 2 of this document
Loss of Alignment - VCAT, see Part 2 of this document
Loss of Channel, see Part 2 of this document
Loss of Clock, see Part 2 of this document
Loss of Data Synch, see Part 2 of this document
Loss of Extra Traffic, see Part 2 of this document
Loss of Frame (DS1), see DS1 Receive alarms on page 4-202
Loss of Frame (DS3/E3), see DS3 and E3 Receive alarms on page 4-209
Loss of Frame (E1), see E1 Receive alarms on page 4-231
Loss of Frame (EC-1), see EC-1 Receive alarms on page 4-243
Loss Of Frame (OC/STM), see Part 2 of this document
Loss Of Frame (OTM1, OTM2, OTM3, OTM4, OTUTTP, ETTP, STTP), see
Loss of Frame Delineation, see Part 2 of this document
Loss of Lock, see Part 2 of this document
Loss of Multiframe (E1), see E1 Receive alarms on page 4-231
Loss Of Multiframe (OTM1, OTM2, OTM3, OTM4), see Part 2 of this
document
Loss Of Multiframe (WAN), see Part 2 of this document
Loss of Multiframe - VCAT, see Part 2 of this document

Loss of Pointer, see Part 2 of this document

Loss of Sequence - VCAT, see Part 2 of this document
Loss of Signal (DS1), see DS1 Receive alarms on page 4-202
Loss of Signal (DS3/E3), see DS3 and E3 Receive alarms on page 4-209
Loss of Signal (E1), see E1 Receive alarms on page 4-231
Loss of Signal (EC-1), see EC-1 Receive alarms on page 4-243
Loss of Signal (ESI), see ESI alarms on page 4-270
Loss Of Signal (ETH10G/ETH40G/ETH100G), see Part 2 of this
document
Loss Of Signal (Ethernet), see Part 2 of this document
Loss of Signal (FC100/FC200/FC400, FC800, FC1200, FLEX), see Part 2
of this document
Loss of Signal (OC/STM), see Part 2 of this document
Loss of Signal (OC48/192/768/STM16/64/256), see Part 2 of this
document
Loss of Signal (OPTMON, VOA), see Part 2 of this document
Loss Of Signal (OTM1, OTM2, OTM3, OTM4, PTP), see Part 2 of this
document
Low Optical Return Loss at Input, see Part 2 of this document
Low Optical Return Loss at Output, see Part 2 of this document
Low Order Bandwidth Near Limit, see Part 2 of this document
Low Received Span Loss, see Part 2 of this document
Low Voltage (DSM), see Part 2 of this document
M
MAC Database Near Capacity, see Part 2 of this document
MAC Flapping Detected, see Part 2 of this document
MAC Status Defect, see Part 2 of this document
Manual Area Address Dropped, see Part 2 of this document
Manual Ring Switch Active, see Part 2 of this document
Manual Switch Active, see Part 2 of this document
Mapping Mismatch, see Part 2 of this document
Max Stations Exceeded, see Part 2 of this document
Member Shelf Mismatch, see Part 2 of this document
Member Shelf Unknown, see Part 2 of this document
Member Shelf Unreachable, see Part 2 of this document

Minimum Gain, see Part 2 of this document

MS DCC Link Failure, see DCC Link Fail alarms on page 4-160
MSI Mismatch (ODUTTP, ODUCTP, OTM0, OTM1, OTMFLEX), see Part 2
of this document
Multiplexed Rate Mismatch, see Part 2 of this document
N
NE Mode Unknown, see Part 2 of this document
Network Trace Identifier Mismatch (FLEX), see Part 2 of this document
Node ID Mismatch, see Part 2 of this document
Number of Level 1 NEs Exceeded, see Part 2 of this document
O
OAM Not Available, see Part 2 of this document
OCH Link Data Retrieval In Progress, see Part 2 of this document
OCH Link Data Save In Progress, see Part 2 of this document
ODU AIS (OTM1, OTM2, OTM3, OTM4, ODUTTP, ODUCTP), see Part 2
of this document
ODU BDI (OTM1, OTM2. OTM3, OTM4, ODUTTP, ODUCTP), see Part 2
of this document
ODU LCK (OTM1, OTM2, OTM3, OTM4, ODUTTP, ODUCTP), see Part
2 of this document
ODU Loss of Frame and Multiframe (ODUTTP, ODUCTP), see Part 2 of
this document
ODU OCI (OTM1, OTM2, OTM3, OTM4, ODUTTP, ODUCTP), see Part 2
of this document
ODU Signal Degrade (ODUTTP, ODUCTP, TCM), see Part 2 of this
document
ODU Signal Fail (OTM), see Part 2 of this document
ODU/OTU Trace Identifier Mismatch, see Part 2 of this document
Optical Line Fail, see Part 2 of this document
OPU AIS (OTM0, OTM1, OTM2, OTM3, OTM4, ODUTCTP, ETTP, STTP),
see Part 2 of this document
OPU Payload Type Mismatch, see Part 2 of this document
OSC Loss of Signal, see Part 2 of this document
OSC Signal Degrade, see Part 2 of this document
OSC OSPF Adjacency Loss, see Part 2 of this document
OSPF Max Capacity Reached, see Part 2 of this document

OSRP CCI Session Down, see Part 2 of this document

OSRP CCI Session Out of Sync, see Part 2 of this document
OSRP Database Integrity Failed on page 5-197
OSRP Port Capability Mismatch, see Part 2 of this document
OSRP Node Operationally Blocked, see Part 2 of this document
OSRP Redundant Database Synch Failed, see Part 2 of this document
OTDR Trace In Progress, see Part 2 of this document
OTS Provisioning Error, see Part 2 of this document
OTU BDI (OTM1, OTM2, OTM3, OTM4), see Part 2 of this document
OTU Signal Degrade, see Part 2 of this document
OTU Signal Fail (OTM), see Part 2 of this document
OTU Skew Out Of Range, see Part 2 of this document
OTU Trace Identifier Mismatch, see Part 2 of this document
Output Loss of Signal, see Part 2 of this document
P
Packet Rate Limit Exceeded, see Part 2 of this document
Packet Rate Limit Exceeded - CU2, see Part 2 of this document
Payload Extended Label Mismatch, see Part 2 of this document
Payload Label Mismatch, see Part 2 of this document
Pluggable I/O Carrier 1 Fail, see Part 2 of this document
Pluggable I/O Carrier 2 Fail, see Part 2 of this document
Pluggable I/O Carrier 1 Missing, see Part 2 of this document
Pluggable I/O Carrier 2 Missing, see Part 2 of this document
Pluggable I/O Carrier 1 Unknown, see Part 2 of this document
Pluggable I/O Carrier 2 Unknown, see Part 2 of this document
Pluggable I/O Panel Mismatch, see Part 2 of this document
Pluggable I/O Panel Missing, see Part 2 of this document
Pluggable I/O Panel Unknown, see Part 2 of this document
Port Bandwidth Near Limit, see Part 2 of this document
Power Failure, see Part 2 of this document
Power Failure - A or Power Failure - B, see Part 2 of this document
Power Failure - A (DSM) or Power Failure - B (DSM), see Part 2 of this
document
Power Failure - Fuse Blown, see Part 2 of this document

Power Failure - Low Voltage, see Part 2 of this document

Pre-FEC Signal Fail, see Part 2 of this document
Pre-FEC Signal Degrade, see Part 2 of this document
Primary RADIUS Server Unavailable, see Part 2 of this document
Primary Shelf Unreachable, see Part 2 of this document
Protection Channel Match Fail, see 1+1/MSP linear and 1+1 TPT APS
alarms on page 4-22
Protection Default K-bytes, see Part 2 of this document
Protection Exerciser Failed, see Part 2 of this document
Protection Exerciser Failed Protection, see Part 2 of this document
Protection Exerciser Failed Working, see Part 2 of this document
Protection Invalid K-bytes, see Part 2 of this document
Protection Locked, see Part 2 of this document
Protection Mode Mismatch, see Part 2 of this document
Protection Scheme Mismatch, see Part 2 of this document
Protection Sub-module Mismatch, see Part 2 of this document
Protection Sub-module Missing, see Part 2 of this document
Protection Sub-module Unknown, see Part 2 of this document
Protection Switch Active, see Part 2 of this document
Protection Switch Byte Fail, see 1+1/MSP linear and 1+1 TPT APS alarms
on page 4-22
Protection Switch Complete, see Part 2 of this document
Protection Switch Complete - Revertive, see Part 2 of this document
Provisioning Database Freeze Enable, see Part 2 of this document
Provisioning Incompatible, see Part 2 of this document
Provisioning Incompatible - Pluggable, see Part 2 of this document
Provisioning Mismatch, see Part 2 of this document
R
RAMAN Failed To Turn On, see Part 2 of this document
RFI (VT), see Part 2 of this document
Redundant Database Synch Failed, see Part 2 of this document
Redundant Database Synch Failed - CPU2, see Part 2 of this document
Redundant Database Synch in Progress, see Part 2 of this document
Redundant Release Synch Failed, see Part 2 of this document

Redundant Release Synch in Progress, see Part 2 of this document

Release Server Mismatch, see Part 2 of this document
Release Server URL Fail, see Part 2 of this document
Remote Alarm Indication (DS1), see DS1 Receive alarms on page 4-202
Remote Alarm Indication (DS3), see DS3 and E3 Receive alarms on page
4-209
Remote CCM Error, see Part 2 of this document
Remote Client Circuit Pack Failed - Pluggable, see Part 2 of this document
Remote Client Circuit Pack Missing - Pluggable, see Part 2 of this
document
Remote Client Circuit Pack Unknown - Pluggable, see Part 2 of this
document
Remote Client High Received Optical Power, see Part 2 of this document
Remote Client Link Down, see Part 2 of this document
Remote Client Low Received Optical Power, see Part 2 of this document
Remote Defect Indication, see Part 2 of this document
Remote Fault (ETH10G, ETH40G, ETH100G, FC800, FC1200 for BB
services, ETTP), see Part 2 of this document
Remote Invalid Configuration, see Part 2 of this document
Remote Inventory Not Supported, see Part 2 of this document
Remote Line High Received Optical Power, see Part 2 of this document
Remote Line Low Received Optical Power, see Part 2 of this document
Remote Loopback Active, see Part 2 of this document
Remote Loopback Fail, see Part 2 of this document
Remote Node Unreachable, see Part 2 of this document
Remote Port OOS, see Part 2 of this document
Remote Port Unreachable, see Part 2 of this document
Remote Power Fail Indication, see Part 2 of this document
Remote Power Supply 1 Missing, see Part 2 of this document
Remote Power Supply 2 Missing, see Part 2 of this document
Remote Receiver Fail, see Part 2 of this document
RFI (EC-1), see EC-1 Receive alarms on page 4-243
RFI (OC), see Part 2 of this document
RFI (STS), see Part 2 of this document

RFI (VT), see Part 2 of this document

RFI (STTP), see Part 2 of this document
Ring Failure, see Part 2 of this document
Ringlet Failure, see Part 2 of this document
Ring Protection Exerciser Fail, see Part 2 of this document
Ring Protection Switch Complete, see Part 2 of this document
Ring Protection Switch Fail, see Part 2 of this document
Rollover in Progress, see Part 2 of this document
Root Directory Has Reached Maximum File Entry Limit, see Part 2 of this
document
Routing Table Overflow, see Part 2 of this document
RS DCC Link Failure, see DCC Link Fail alarms on page 4-160
Rx Channel Power Out of Range, see Part 2 of this document
Rx Ethernet Idle, see Part 2 of this document
Rx Partial Loss of Capacity - LCAS, see Part 2 of this document
Rx Power Out of Range, see Part 2 of this document
Rx Total Loss of Capacity - LCAS, see Part 2 of this document
S
Secondary RADIUS Accounting Server Unavailable, see Part 2 of this
document
Secondary RADIUS Server Unavailable, see Part 2 of this document
Secondary Service Failed, see Part 2 of this document
Secondary SETS Locking to Primary, see Part 2 of this document
Section DCC Link Failure, see DCC Link Fail alarms on page 4-160
SECTION/RS DCC OSPF Adjacency Loss, see OSPF Adjacency Loss
alarms in Part 2 of this document
Service Defect Indication, see Part 2 of this document
Shelf Bandwidth Near Limit, see Part 2 of this document
Shelf Data Missing, see Part 2 of this document
Shelf Power Near Limit, see Part 2 of this document
Shutoff Threshold Crossed, see Part 2 of this document
Signal Degrade (DS3/E3), see DS3 and E3 Receive alarms on page
4-209
Signal Degrade (EC-1), see EC-1 Receive alarms on page 4-243

Signal Degrade (ETH, ETH100, ETH10G, WAN), see Error alarms (ETH,
ETH10, ETH40G, ETH100G, FLEX, WAN, ETTP) on page 4-254
Signal Degrade (OC/STM, STTP, STS/HO VC and VT/LO VC), see Error
alarms (OC/STM, STS/HO VC, and VT/LO VC) on page 4-261
Signal Fail (EC-1), see EC-1 Receive alarms on page 4-243
Signal Fail (OC/STM MSPP), see Error alarms (OC/STM, STS/HO VC,
and VT/LO VC) on page 4-261
Signal Fail (OC48/192/768/STM16/64/256, STTP), see Part 2 of this
document
Site Provisioning Required (DSM), see Part 2 of this document
SNC Takeover Failed, see Part 2 of this document
SNC Unavailable, see Part 2 of this document
SNMP Proxy Config Failed on Member, see Part 2 of this document
SNMP Proxy Trap Config Failed on Member, see Part 2 of this document
SNMP Proxy Config Failed on Primary, see Part 2 of this document
Software Auto-Upgrade Failed, see Part 2 of this document
Software Auto-Upgrade in Progress, see Part 2 of this document
Software Configuration Unknown, see Part 2 of this document
Software Delivery Incomplete, see Part 2 of this document
Software Delivery In Progress, see Part 2 of this document
Software Mismatch, see Part 2 of this document
Software Upgrade Failed, see Part 2 of this document
Software Upgrade in Progress, see Part 2 of this document
Span protection Switch Complete, see Part 2 of this document
Span protection Switch Fail, see Part 2 of this document
Span Protection Exerciser Fail on page 5-393
Switch Shelf ID Mismatch Detected, see Part 2 of this document
Synchronization Protection alarms, see Part 2 of this document
T
Target Unachievable, see Part 2 of this document
TCM Loss of Tandem Connection, see Part 2 of this document
Telemetry Loss of Signal, see Part 2 of this document
Test Access in Progress alarms, see Part 2 of this document
Threshold AIS ESO-A/ESO-B, see Part 2 of this document
Time Out, see Part 2 of this document

Timing Distribution Forced Switch - n Ref, see Part 2 of this document

Timing Distribution Lockout - n Ref, see Part 2 of this document
Timing Distribution Loss of Reference - n Ref, see Part 2 of this document
Timing Generation Entry to Freerun, see Part 2 of this document
Timing Generation Entry to Holdover, see Part 2 of this document
Timing Generation Failure To Lock, see Part 2 of this document
Timing Generation Forced Switch - n Ref, see Part 2 of this document
Timing Generation Lockout - n Ref, see Part 2 of this document
Timing Generation Loss of Reference - n Ref, see Part 2 of this document
TOD Server Not Provisioned, see Part 2 of this document
Topology Failure, see Part 2 of this document
Topology Instability, see Part 2 of this document
Trace Identifier Mismatch (OC/STM), see Part 2 of this document
Trace Identifier Mismatch (STS/HO VC and VT/LO VC), see Part 2 of this
document
Traffic Squelched, see Part 2 of this document
Transport Data Recovery Failed, see Part 2 of this document
TR Control Disabled, see Part 2 of this document
TR Control Echo Trace Mismatch, see Part 2 of this document
TR Control Initialization in Progress, see Part 2 of this document
TR Control IS Optimization in Progress, see Part 2 of this document
Tx AIS (DS1), see Part 2 of this document
Tx AIS (DS3/E3), see Part 2 of this document
Tx AIS (E1), see E1 Transmit alarms on page 4-236
Tx Frequency Out of Range (DS1), see Part 2 of this document
Tx Frequency Out of Range (DS3/E3), see Part 2 of this document
Tx Loss of Frame (DS1), see Part 2 of this document
Tx Loss of Frame (DS3/E3), see Part 2 of this document
Tx Loss of Frame (E1), see E1 Transmit alarms on page 4-236
Tx Loss of Multiframe (E1), see E1 Transmit alarms on page 4-236
Tx Loss of Signal, see Part 2 of this document
Tx Manual Provisioning Required, see Part 2 of this document
Tx Partial Loss of Capacity - LCAS, see Part 2 of this document
Tx Remote Alarm Indication, see Part 2 of this document

Tx Remote Defect Indication, see Part 2 of this document

Tx Total Loss of Capacity - LCAS, see Part 2 of this document
Tx Tuning in Progress, see Part 2 of this document
U
Unable to Synchronize TOD, see Part 2 of this document
Unequipped, see Part 2 of this document
Unpaired SSH Key, see Part 2 of this document
V
VOA Output LOS, see Part 2 of this document
VT-STS bandwidth near limit, see Part 2 of this document
W
Warm Restart Required, see Part 2 of this document
Wavelength Measurement Error, see Part 2 of this document
Wavelength Measurement Warning, see Part 2 of this document
WAYSIDE 1/2 Port Failure, see Part 2 of this document

Procedure 4-1
1+1/MSP linear and 1+1 TPT APS alarms
Protection Channel Match Fail
Alarm ID: 263, 291, 953, 1018, 1108, 1324, 1336, 1701
Probable cause
This alarm is raised when:
• the received channel ID on the protection interface circuit pack is not as
expected. This is normally because of a failure in the interface circuit pack.
• the automatic protection switching (APS) communications protocol
between the two optical interfaces is not working because the optical fiber
is not connected to the correct slot at either end
• the protection engine does not receive APS bytes from the far end
• the protection engine receives invalid APS bytes from the far end
This alarm is only raised on the OTN 1+1 line-side protection, 1+1/MSP linear,
1+1 port TPT, and 1+1 TPT protected configurations.
For OTN protection, this alarm is applicable only if the protection scheme is
1+1 port TPT and Bi-directional.
Impact
Major, non-service-affecting (M, NSA) alarm
Protection Switch Byte Fail

Alarm ID: 260, 290, 952, 1017, 1107, 1323, 1335, 1391, 1700
Probable cause
This alarm is raised when the received channel protection switching control
bytes (APS bytes) on the protection interface circuit pack are not valid codes.
This is normally because of a failure in the interface circuit pack or crossed
fibers.
This alarm is raised on 1+1/MSP linear, 1+1 port TPT, and 1+1 TPT protected
configurations.
Impact


Prerequisites
To perform this procedure, you must
• observe all safety requirements described in the “Observing product and
personnel safety guidelines” chapter in Part 1 of Installation,
323-1851-545
• have the optical fiber connection information (that is, how the optical
modules on each network element connect to other network elements)
Step Action
1 Identify the interface circuit pack raising the alarm. Refer to the “Identifying
the circuit pack, pluggable module/port, or facility that has raised an alarm”
procedure in this document.
2 Identify the protection provisioning on the circuit pack raising the alarm.
Ensure that the protection scheme is 1+1/MSP linear, 1+1 port TPT, or 1+1
TPT. Refer to the “Retrieving protection parameters” procedure in Part 2 of
Configuration - Provisioning and Operating, 323-1851-310. If the protection
is not 1+1/MSP linear, 1+1 port TPT, or 1+1 TPT, contact your next level of
support or your Ciena support group.
3 Identify the protection provisioning on the far end. Ensure that the protection
scheme is 1+1/MSP linear, 1+1 port TPT, or 1+1 TPT. If the same alarm
appears at the other end, two fibers have been swapped. If a different alarm
condition exists at the far end, investigate the alarm to identify and localize
the fault.
If the original alarm was Then go to
Protection Channel Match Fail step 5
Protection Switch Byte Fail step 7
5 Verify that the optical fibers/cables are connected to the correct ports at each
node. The working port of the protection pair at the near end must be fibered
to the working port of the protection pair at the remote end. The protection
port of the protection pair at the near end must be fibered to the protection
port of the protection pair at the remote end.
Use Section Trace to identify fiber connectivity. Refer to the “Retrieving and
editing section trace messages” procedure in Part 1 of Configuration -


Step Action
6 If the original alarm has Then

cleared the procedure is complete
not cleared go to step 7
7 Replace the interface circuit pack raising the alarm. Refer to the equipment
replacement procedures in chapter 2 of Fault Management - Module
Replacement, 323-1851-545. Select the appropriate procedure from the
“Module replacement procedures list” table. Wait 30 seconds.
9 Use the optical fiber connection information to determine the network

element and interface circuit pack on the far end of the optical fiber link.
10 Replace the remote interface circuit pack. Refer to the equipment
“Module replacement procedures list” table.
11 If the alarm does not clear, contact your next level of support or your Ciena
support group.
—end—

Procedure 4-2
Adjacency Discovery Unreliable
Alarm ID: 1072
Probable cause
This alarm is raised when a remote shelf that the SPLI feature is tracking has
not communicated (UDP) with the SPLI application for more than 10 minutes.
This could happen:
• if the remote shelf has changed their SiteID or TID
• if the remote shelf is isolated from the network
• if the remote shelf is constantly restarting
Impact
Minor, non-service-affecting (m, NSA) alarm
Prerequisites
• have a network plan or other documents that allow you to determine the
SPLI connectivity
323-1851-545
Step Action
1 Determine which shelves are unreliable using the SPLI tab in the Node
Information application. Find the nodes and shelves with a status of
Unreliable.
Refer to the “Displaying node information” procedure in chapter 4 of
Administration and Security, 323-1851-301, for more information about the
Node Information application.
2 Verify whether the TID or siteID has changed on those nodes. If changes
have been made, change the TID or siteID of those nodes back to the original
ones if necessary.
3 If changes have not been made, verify that comms are working correctly by
logging into the network element.
4 Click the Refresh button in the SPLI tab of the Node Information window to
retrieve the latest statuses.


Adjacency Discovery Unreliable
Step Action
5 If SPLI is not matching to all the TID-shelves that are listed as unreliable, click
on the Delete button. This will remove all the unreliable entries from the table.
Note that any OMD4, OMX and CMD44 Tx/Rx Adjacency with the Auto
Discovered parameter set to Auto, which is associated with the remote
TID-Shelf entries that are being deleted will be deprovisioned if their DOC
Care parameter is set to False. As well the discovered Far End Addresses
will be set to Unknown.
7 Contact your next level of support or your Ciena support group.

—end—

Procedure 4-3
Adjacency Far End Not Discovered
Alarm ID: 538
Probable cause
This alarm is raised against an ADJ-LINE facility when the adjacency cannot
be automatically discovered from the far-end. Possible reasons for this
far-end adjacency not being discovered include:
• the two adjacency end points have not been fibered
• the two adjacency end points have been fibered but some other problem
exists with the fiber or connection
• there is a comms provisioning error, where the OSPF circuit is incorrectly
provisioned or not provisioned at one or both ends of the alarmed span
• an upstream network element has undergone a restart operation. The
alarm will clear once the restart completes.
• fibers at the Line AMP NE are swapped (misconnected/crossed)
• the ADJ-LINE Expected Far End Address is incorrectly provisioned
• the appropriate OSC is not provisioned in the OTS or in the OTS Slot
Sequence or is not functioning correctly.
In the case of a line adjacency, the discovered provisioned expected far end
address is the photonics circuit pack at the other end of the fiber span. Refer
to Figure 4-1 on page 4-29 for an example of line adjacency far end
addresses.
Impact
Prerequisites
323-1851-545
• have the engineering documentation package (EDP) for shelf details


Step Action
1 Verify and correct the adjacency provisioning information as required. Refer

to the “Editing facility parameters” procedure in Part 1 of Configuration -
2 If applicable, check the OSC facility states and confirm provisioning of the
OSC in the OTS or in the Slot Sequence.
4 If this adjacency Then

is fibered, but a fiber break, reflective go to step 5
event, or disconnect is suspected
was provisioned for future use, and disable this alarm so that it no longer
you do not want this alarm to be appears in the active alarms list.
displayed in the active alarm list Refer to alarm provisioning and
alarm profiles procedures in chapter
2 of this document.
was provisioned for future use and no action is required. The procedure
you want this alarm to be displayed in is complete.
the active alarms list for informational
purposes
requires fibering fiber the adjacency end points. Refer
to engineering documentation
package (EDP).
5 Clear any alarms that indicate a fiber break or disconnect, such as:
• Automatic Power Reduction Active
• Automatic Shutoff
• Input Loss of Signal
• Loss of Signal (OPTMON)
• Optical Line Fail
6 Verify the fibers at the Line AMP NE for any reversed fiber connections and
correct if necessary.
7 Verify that the provisioned values for ADJ-LINE Expected Far End Address
Format or Expected Far End Address are correct.


Step Action
8 Edit the provisioned values as appropriate to correct the Expected values.

Refer to the “Editing facility parameters” procedure in Part 1 of Configuration
- Provisioning and Operating, 323-1851-310.
support group.
—end—
Figure 4-1
Line adjacency far end address examples
Site F Site G
MLA MLA
slot 1 slot 2
8 In 5 Out
5 Out 8 In
Legend
Line adjacency ADJ-1-1-5
far end address SiteG-1-2-8
far end address SiteF-1-1-8
shelf slot port

Procedure 4-4
Adjacency Mismatch
Alarm ID: 539
Probable cause
This alarm is raised against an ADJ-LINE facility when the Expected far end
address parameter of the line adjacency is manually provisioned, but does
not match the discovered address (Actual Far End Address) listed for the
ADJ-LINE facility.
If the provisioned information is correct, mis-fibering can be the cause for this
alarm.
This alarm is expected on network elements adjacent to network elements

undergoing a TID consolidation re-configuration. These alarms clear after the
inter-shelf adjacencies are updated with the Node name.
In the case of a line adjacency, the discovered far end address is the photonics
circuit pack at the other end of the fiber span. Refer to Figure 4-2 on page 4-32
for an example of line adjacency far end addresses.
This alarm is also raised against an ADJ-TX or ADJ-RX facility when either the
ADJ-TX or ADJ-RX facility has a discovered type that does not match the
transmitter or receiver type.
Change to the discovered type occurs when the expected far end addresses
that establish the connection between the transmitter circuit packs and the
CMD44 ports have changed or the provisioning on the transmitter circuit pack
has changed.
Normally when the ADJ-TX or ADJ-RX facility has Auto Discovered set to
Auto, any change to the discovered type will be automatically populated to the
transmitter or receiver type. However, if the change happens while the ADJ-TX
or the ADJ-RX is managed by DOC (DOC Care is True), a cross-connect
exists, or if the "Synch Provisioned" parameter is false, this auto-population is
not possible and causes a mismatch.
Impact
Prerequisites
• know the correct far end address for the alarmed adjacency


Adjacency Mismatch
Step Action
1 If this alarm is raised against Then go to

an ADJ-LINE facility step 2
an ADJ-TX or ADJ-RX facility step 7
2 Using the network planning diagram, verify if the Expected far end address
adjacency parameter is correct. Refer to the “Retrieving equipment and
facility details” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
3 If the actual far end address is Then
correct go to step 4
incorrect verify that the line-side fiber is correctly
connected. Go to step 6.
4 Edit the Expected far end address and Expected far end address format
adjacency parameters so that they match the Actual Far End Address and
Actual Far End Address Format listed for the ADJ-LINE facility. Refer to the
“Editing facility parameters” procedure in Part 1 of Configuration -
5 Make sure that the "Synch Provisioned" parameter on the CMD44 ADJ-TX is
set to true.
support group.
This procedure is complete.
7 Using the network planning diagram, verify that the actual far end address
parameter is correct.
8 If the actual far end address is Then go to
correct step 9
incorrect step 11
9 Verify that the transmitter circuit pack (that the ADJ actual far end address
points to) is provisioned correctly. Correct the provisioning on the transmitter
circuit pack in order for it to match the ADJ Tx/Rx's transmitter/receiver type.
support group.


Adjacency Mismatch
Step Action
11 If the actual far end address is NULL, provision the correct expected far end
address between the transmitter circuit pack and the CMD44 ADJ-TX port.
Otherwise, clear the SPLI match that is discovered by setting the expected far
end address to NULL at the CMD44 ADJ-TX and transmitting circuit pack (if
it supports ADJ provisioning). Then reprovision with the correct expected far
end address.
support group.
—end—
Figure 4-2
Line adjacency far end address examples
Site F Site G
MLA MLA
slot 1 slot 2
8 In 5 Out
5 Out 8 In
Legend
far end address SiteG-1-2-8
far end address SiteF-1-1-8
shelf slot port

Procedure 4-5
Adjacency Provisioning Error
Alarm ID: 707
Probable cause
This alarm is raised against an ADJ facility when the inter-shelf provisioning
is missing, and there is a channel with an optical cross-connect or
inter-domain passthrough (over that adjacency or over the paired adjacency)
in the opposite direction.
This alarm is also raised against a DSCM adjacency facility that is provisioned
in the OTS when the OTS "Enhanced Topology" attribute is Enabled and the
DSCM does not have its DISP facility properly provisioned.
Attention: If unpaired channels are to be used, you must provision

inter-shelf adjacencies in both directions.
The conditions that raise this alarm are listed below:

• a passthrough channel is provisioned, but the far end address does not
match the discovered shelf
• an optical cross-connect is provisioned, but the far end address does not
match a shelf at the same site and in a different domain
• the adjacency type does not match the circuit pack function (for example,
WSSOPM on a ROADM, CMD or LIM on a TOADM)
• A passthrough channel is provisioned at a TOADM, but a CMD for that
same group is provisioned or the inter-OTS adjacencies are missing or
they are incorrectly provisioned. In a TOADM configuration, the adjacency
corresponding to the CMD channel OUT port for that wavelength is
alarmed.
• if no passthrough adjacency is provisioned on a ROADM, the alarm is
raised against all candidate passthrough ports. The alarm is cleared
against all candidate passthrough ports when a passthrough adjacency is
provisioned.
• A skip channel originating from a CMD44/ROADM is provisioned as
passthrough at a TOADM. This channel cannot be optically passed
through the node. For more information on unavailable skip channels, refer
to the table (unavailable 50 GHz channels) in the Photonic Guide,
NTRN15DA.
• There was a change in the TID of the node after some adjacencies were
provisioned.


Impact
Prerequisites
• have the engineering documentation package (EDP) for shelf details
Step Action
1 If this is a Then go to
ROADM site step 2
TOADM site step 5
2 Verify if the WSS-to-WSS adjacency of the ROADM site is provisioned and

correct. In particular, verify that the provisioned Expected far end address
is correct. Refer to the “Retrieving equipment and facility details” procedure
3 If the WSS-to-WSS adjacency Then go to
has not been manually provisioned or has an error step 4
is provisioned and correct step 10
4 Create or edit the WSS-to-WSS adjacency. Refer to the “Editing facility

Operating, 323-1851-310.
Go to step 10.
5 Verify that the CMD-to-CMD adjacencies at the end of SCMD Cascading
Order are provisioned and correct.
In particular, for inter-OTS adjacencies, confirm that the Upgrade OUT to
Upgrade IN adjacencies for the cascading CMD are provisioned correctly.
Verify that the provisioned far end address is correct. Select
Configuration->Equipment & Facility Provisioning.
For intra-OTS adjacencies, confirm that the cascading SCMD order is
provisioned correctly. Select the Configuration->Photonic Services->SCMD
Cascading Order.
6 If the CMD-to-CMD adjacency at the end of the SCO Then go to
has an error step 7
is provisioned and correct step 10


Step Action
7 Edit the CMD-to-CMD adjacency. See Configuration, 323-1661-310.

8 Verify that CMDs are not provisioned for the same groups that are intended
to passthrough the site. If this occurs, the system will need to be
re-engineered to use a channel that does not drop at this site. See your
Engineering Documentation Package (EDP) for more information.
9 Verify that a skip channel is not provisioned to pass through this node. If it is,
de-provision the illegal channel and/or re-engineer the network.
Go to step 14.
10 If the alarm is raised against Then go to
a DSCM port step 11
the inter-OTS adjacency step 12
11 Check the DSCM has its DISP facility properly provisioned. Refer to the
“Retrieving equipment and facility details” procedure in Part 1 of
12 Check the inter-OTS adjacency is properly provisioned. Refer to the
13 Check if there is a TID changed on the local shelf. Refer to the “Displaying
node information” procedure in Administration and Security, 323-1851-301.
support group.
—end—

Procedure 4-6
Alarm and Event Throttling Active
Alarm ID: 705
Probable cause
This alarm is raised when the generation of alarms surpasses an average of
four alarms per second over a 10 minute period.
If this alarm is raised, other alarms can still be raised and retrieved, but their
output to the alarm banner is stopped. Once this alarm is cleared, the output
of other alarms to the alarm banner resumes.
Impact
Critical, non-service-affecting (C, NSA) alarm
Step Action
1 Reduce the generation of alarms to less than four alarms a second.

support group.
—end—

Procedure 4-7
Alarm Provisioning Near Limit
Alarm ID: 653
Probable cause
This alarm is raised when the number of VTs provisioned as monitored on a
given circuit pack is approaching the allowed limit.
Impact
Warning, non-service-affecting (w, NSA) alarm
Prerequisites
Step Action
1 Delete any provisioned VTs that are not required. Refer to the “Deleting path
cross-connects” procedure in Part 1 of Configuration - Bandwidth and Data
Services, 323-1851-320.
2 If the alarm did not clear, set the provisioning for another VT back to the
default profile.
3 If more VT provisioning is required, contact your network administrator to
determine your course of action.
—end—

Procedure 4-8
All Provisioned RADIUS Accounting Servers
Unavailable
Alarm ID: 1518
Probable cause
This alarm is raised when no response is received from any provisioned
RADIUS accounting server during user-provisioned timeout.
This alarm is also raised when the RADIUS accounting server provisioning on
the network element is incorrect.
This security alarm is raised against an SP, SPAP-2 w/ 2xOSC, or an

Integrated SP with 8xOTN Flex MOTR circuit pack.
Impact
Prerequisites
Step Action
1 Disable the server on 6500.

2 Re-enable the server and log in or log out of the server.
3 If the alarm is raised again, disable the RADIUS accounting feature and log
in or log out of the server.
4 If the alarm is raised, ensure the following RADIUS accounting server
provisioning values on the network element are correct:
• server IP address
• server port
• shared secret
• timeout - if this value is too small the server may not be able to respond
quickly enough.
Refer to the “Provisioning the primary or secondary RADIUS server”

procedure in Administration and Security, 323-1851-301.
5 Check the status of the RADIUS accounting server. Ensure the status is ON.


All Provisioned RADIUS Accounting Servers Unavailable
Step Action
6 Log in or log out of the network element.

This will send a RADIUS accounting message to all provisioned RADIUS
accounting servers. The alarm will clear if a response is received from the
server(s) within the provisioned timeout.
support group.
—end—

Procedure 4-9
All Provisioned RADIUS Servers Unavailable
Alarm ID: 582
Probable cause
• all requests to the primary and secondary RADIUS servers of a shelf
processor time out
• all requests to a RADIUS server of a shelf processor time out and only one
RADIUS server has been provisioned (primary or secondary)
If the All Provisioned RADIUS servers Unavailable alarm is raised and only a
single RADIUS server is provisioned (primary or secondary), provisioning the
second RADIUS server will cause the All Provisioned RADIUS servers
Unavailable alarm to clear and either the Primary RADIUS Server Unavailable
or Secondary RADIUS Server Unavailable alarm to be raised for the original
RADIUS server.
The alarm is not raised due to server time out.
If the alternate method for security is Challenge/Response, the user can log
in using the challenge response generated by Site Manger. The shared secret
is required to generate the correct response.
If the alternate method for security is Local, the user can log in using a local
userid and password.
Impact
Prerequisites
Step Action
1 Ensure the primary and secondary RADIUS servers of the shelf processor
are enabled and have a valid IP address. Refer to the “Provisioning the
primary or secondary RADIUS server” procedure in chapter 2 of
2 Log into the network element again using the RADIUS authentication
(centralized security administration).
support group.
—end—

Procedure 4-10
ALS Disabled
Alarm ID: 1112
Probable cause
This alarm is raised when the ALS feature has been disabled on a port.
CAUTION
Risk of personal injury
Disabling the ALS feature creates a potentially dangerous
situation since the laser no longer shuts down when a Loss of
Signal alarm is raised.
Impact
Prerequisites
Before you perform this procedure, you must observe all safety requirements
described in Installation, 323-1851-201 or Module Replacement Procedures,
323-1851-545.
Step Action
1 Check whether ALS should be disabled on the circuit pack port.

If ALS should Then
be disabled no action is required
not be disabled go to step 2
2 Enable ALS on the port. Refer to the “Editing facility parameters” procedure
support group.
—end—

Procedure 4-11
ALS Triggered - Laser is shutdown
Alarm ID: 1111
Probable cause
This alarm is raised to indicate the ALS feature has shutdown the laser after
detecting a Loss of Signal alarm.
Impact
Critical, service-affecting (C, SA) alarm for an active circuit pack
Major, non-service-affecting (m, NSA) alarm for an inactive circuit pack
Prerequisites
Before you perform this procedure, you must observe all safety requirements
described in Installation, 323-1851-201 or Module Replacement Procedures,
323-1851-545.
Step Action
1 Identify the circuit pack/port raising the alarm and check if a Loss of Signal
alarm is present on the same port. See Identifying the circuit pack, pluggable
module/port, or facility that has raised an alarm on page 2-38.
2 If a Loss of Signal alarm Then
is present on the port clear the Loss of Signal alarm, see the
“Loss of Signal” alarm clearing procedure
in Part 2 of this document.
is not present on the port contact your next level of support or your
Ciena support group
support group.
—end—

Procedure 4-12
Automatic Power Reduction Active
Alarm ID: 542, 941
Probable cause
This alarm is raised against an SLA/MLA/XLA C-Band/MLA L-Band/MLA2
C-Band/MLA3 C-Band AMP facility, SRA RAMAN facility, or a MLA2v VOA
facility when the optical return loss (ORL) drops below a fixed threshold
(17 dB). When the ORL falls below the threshold, the system reduces the
amplifier output power level to minimize the danger of personal eye injury.
For amplifiers, Automatic Power Reduction (APR) indicates reflection at the

output. For RAMAN amplifiers, APR either indicates reflection at the input or
output depending on the location of the ORL problem.
Although the APR alarm is raised against the input port of a AMP/VOA facility,
the APR condition is caused by a reflection somewhere downstream from the
AMP/VOA. This reflection can be caused by:
• dirty optical connectors

• improper optical cable mating
• a disconnected optical fiber at the amplifier output
• an optical fiber cut
• a degraded optical fiber
• a disconnected or missing termination
• misprovisioning of an amplifier resulting in excessive power being injected
into the mid-stage DSCM or fiber-plant
When the ORL reading is not valid because the power into the backward
reflective monitor tap is too low and cannot be measured accurately, the ORL
PM reading(s) report “OOR”. The true ORL reading(s) cannot be determined
in this case.
Attention: This alarm indicates a condition on the output port of an

amplifier; however, the alarm is raised against the input port of the
corresponding SLA/MLA/XLA C-Band, MLA L-Band, MLA2 C-Band, MLA2
w/VOA, SRA, or MLA3 C-Band circuit pack. Therefore, ensure you
troubleshoot the appropriate port. See the block diagrams of the amplifiers
in Photonics Equipment, 323-1851-102.6.


Impact
Major, service-affecting (M, SA) alarm
Prerequisites
323-1851-545
• have the engineering documentation package (EDP)
• have a fiber cleaning kit
• have a replacement module
Step Action
1 If this alarm Then

was raised as a result of no action is required. The alarm will clear
maintenance or SLAT that has when the maintenance activity or SLAT is
not been completed completed.
is unexpected go to step 2
2 Confirm that the amplifier's provisioning matches what is defined in the EDP.
The amplifier's provisioning can be checked by using the
Configuration->Equipment and Facility Provisioning screen in Site Manager.
Edit the power level values as required. Refer to the “Retrieving equipment
and facility details” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
4 If the alarmed amplifier is Then go to

Port 8 (Line A) step 5
otherwise step 9
5 Ensure that all LC/SC connectors located after the amplifier output are
properly mated. Verify this on both ends of the connector-mating receptacles.


Step Action

7 Ensure that the termination plugs are present and are mated properly on
unused ports.
9
DANGER
CAUTION
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical am-
plifier is out of service (OOS), then disconnect or recon-
nect the fiber.
CAUTION
Place the alarmed AMP/RAMAN facility out of service (OOS) using the "Edit"
button in the Configuration->Equipment and Facility Provisioning screen of
Site Manager. For further instructions refer to the “Changing the primary state
of a facility” procedure in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
Note that for the MLA2V, you should place the amp with the same port
number as the alarmed VOA facility OOS.


Step Action
10
CAUTION
Only disconnect the output fiber of the alarmed optical
amplifier. It is not necessary to disconnect any other
output fibers, which could affect service.
Disconnecting the Line B out fiber will impact traffic in

both directions, as this triggers Automatic Laser Shut
Off (ALSO).
Disconnect the output fiber of the alarmed optical amplifier, clean the output
fiber and connectors at the amplifier, then reconnect the fiber.
11 Place the AMP/RAMAN facility back in-service (IS) using the "Edit" button in
the Configuration->Equipment and Facility Provisioning screen of Site
Manager. For further instructions refer to the “Changing the primary state of
a facility” procedure in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
Note that for the MLA2V, you should place the amp with the same port
number as the alarmed VOA facility IS.
13 You may have to clean a specific connector or connectors that may not be
immediately connected to the alarmed amplifier output. For information on
isolating connector losses, complete Procedure 2-16, "Locating a reflective
event" on page 46.
support group.
—end—

Procedure 4-13
Automatic Shutoff
Alarm ID: 590, 942
Probable cause
This alarm is raised against an AMP facility or SRA RAMAN facility when an
ALSO condition is triggered, and is raised against any amplifier that has been
shut off. An ALSO condition is cleared when the OSC receives a clean signal
or in case of SRA circuit pack, receives a clean telemetry signal from an
upstream network element.
Attention: This alarm indicates a condition on the output port of an

amplifier; however, the alarm is raised against the input port of the
corresponding SLA/MLA C-Band, MLA L-Band, MLA2 C-Band, MLA2
w/VOA, SRA, XLA, or MLA3 C-Band circuit pack. Therefore, ensure you
troubleshoot the appropriate port.
DANGER
Risk of radiation exposure
If light is used to test the broken fiber (for example, with a light
source or an OTDR), certain Automatic Laser Shut Off (ALSO)
and loss of signal alarms can clear. When the shelf detects
light, the alarms clear and the amplifier facility is powered up.
This is an expected behavior because a shelf cannot
distinguish between a light source from an optical test set and
a light source from a shelf.
Ensure the adjacent optical amplifiers are out of service (OOS)
when performing fiber repairs.
Impact
Prerequisites
Step Action
1 Complete the Optical Line Fail alarm clearing procedure in Part 2 of this
document.
support group.
—end—

Procedure 4-14
Automatic Shutoff Compromised
Alarm ID: 1775
Probable cause
This alarm is raised when the Rx/Tx fibers of the OSC on an SRA/SAM/ESAM
circuit pack are crossed at one or both ends of a photonic span.
Impact
Prerequisites
323-1851-545
• have the engineering documentation package (EDP)
Step Action
1 Ensure that the OSC fibers are correctly connected at both ends of their
spans.
support group.
—end—

Procedure 4-15
Automatic Shutoff Disabled
Alarm ID: 1035, 1746
Probable cause
This alarm is raised on AMP or OPTMON facilities when the Shutoff Threshold
is provisioned to be -60 dBm or when we enable the Also Disable Attribute
through Site Manager for the AMP or OPTMON facility. The AMP facility is put
in Shutoff Disabled mode when the user is adding the first optical channel.
This alarm is also raised temporarily when DOC performs a power audit.
During the power audit, DOC disables the automatic laser shutoff (ALSO)
feature on the XLA so that the XLA can generate amplifier noise (ASE) for the
SRA calibration. At the end of the power audit, DOC re-enables the automatic
laser shutoff feature and the alarm will clear.
CAUTION
During this procedure the fiber plant does not have to be
disrupted and the system remains a Class 1(IEC)/Class I
(FDA) product.
If the fiber downstream of the MLA2 C-Band/MLA2

w/VOA/MLA3 C-Band Line A output connector becomes
disconnected accidentally while the Amp Auto Shutoff
Disabled feature is active, the radiation at the exposed fiber
can be at hazard level 1M (IEC 60825-2). In this situation, you
must take all safety precautions appropriate to hazard level 1M
(IEC 60825-2). The ORL based APR safety mechanism
remains active.
Impact
Prerequisites
To perform this procedure, you require an account with a level 4 or higher user
privilege code (UPC).


Automatic Shutoff Disabled
Step Action
1 Make sure that the maintenance work has been completed.

2 Immediately after the maintenance work has been completed, enable Auto
Shutoff:
• Select Facilities -> AMP/OPTMON.
• Set the ALSO Disabled Attribute to False in the AMP facility or OPTMON
facility.
This action also stops the timer and clears the alarm. (Note that this alarm
also clears when the amplifier facility comes out of Shutoff Disabled mode
because the time specified by the Automatic Shutoff Disabled Time
parameter ends.)
support group.
—end—

Procedure 4-16
Auto Protection Switch Acknowledge Time Out
Alarm IDs: 427, 428, 429, 430, 954, 1016, 1109, 1325, 1337, 1395, 1702
Probable cause
This alarm is raised for 1+1 OTN protection, 1+1/MSP linear, 1+1 port TPT,
and 1+1 TPT protection groups if an expected reverse request is not received
by the tail end of a switch within 50 ms.
This alarm can be raised if a local 6500 1+1/MSP linear protection group is set
to bidirectional mode and the far end is operating in unidirectional mode.
Impact
Prerequisites
To perform this procedure, you must have the optical fiber/cable connection
information (that is, how the circuit packs on each network element connect to
other network elements and if applicable, how each OC-3 connects to the
DSM).
Step Action
1 Identify the circuit pack raising the alarm. Refer to the “Identifying the circuit
pack, pluggable module/port, or facility that has raised an alarm” procedure
in this document.
2 Ensure the fibering of the network is done properly. If not, make changes to
correct the problem. If the alarm did not clear, continue with the next step.
3 From your company records, determine the correct switch mode for the link.
If the correct mode is Then go to
unidirectional step 4
bidirectional step 5
4 At the local network element, change the switch mode of the optical interface
pair identified in step 1. Refer to the “Changing the protection parameters for
a pair of facilities or equipment” procedure in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310. Go to step 7.
Attention: Changing the protection switch mode for one of the optical
interface circuit packs in a pair automatically changes the protection switch
mode for the other circuit pack in the pair.
5 Use the optical fiber/cable connection information to identify the network

element and optical interface modules that are on the remote end of the link.


Auto Protection Switch Acknowledge Time Out
Step Action
6 Log into the remote network element and change the mode of the optical
interface modules to bidirectional.
support group.
—end—

Procedure 4-17
Autoprovisioning Mismatch
Alarm ID: 60
Probable cause
• a circuit pack is installed in an unprovisioned slot that does not support
that circuit pack, for example, a photonic circuit pack inserted in a slot
reserved by an OTS for a different EQPT type. There is no effect on shelf
operations.
• more than the expected number of circuit packs on a shelf are provisioned,
for example, more than four WSS w/OPM circuit packs in a 14-slit shelf
type.
• a SCMD4 variant that is identical to one that is already provisioned in the
OTS is inserted into a slot that is reserved for a SCMD4 in that OTS.
• a 40G, 100G or ULH circuit pack is inserted in a non-40G/100G shelf type.
When auto equipping is disabled, this alarm is not raised if you install a circuit
pack in an unprovisioned slot that does not support that circuit pack.
Impact
Prerequisites
323-1851-545
• if necessary, obtain a replacement circuit pack or a filler card
Step Action
in this document.
2 Make sure you do not have more than two 2xOSC circuit packs or more than
four WSS w/OPM circuit packs installed in the shelf.
4 Verify whether the slot is reserved by an OTS for a different equipment type.


Autoprovisioning Mismatch
Step Action
5 If Then go to
the alarmed slot is reserved by an OTS for a different step 6
equipment type
otherwise step 7
6 You can edit the OTS instance using the OTS Management application to
release the slot. Then go to step 9.
If you do not want to edit the OTS instance, go to step 10.
7 If Then go to
the circuit pack in the alarmed slot is a spare circuit pack you step 8
want to store in that slot
otherwise step 10
8 Disable auto equipping for the alarmed slot. Refer to the “Enabling/disabling
slot-based automatic equipping” procedure in Administration and Security,
323-1851-301.
9 Reseat the circuit pack in the same slot. Refer to the equipment replacement
procedures in chapter 2 of Fault Management - Module Replacement,
323-1851-545. Go to step 11.
10 Remove the circuit pack in the alarmed slot and replace it with a circuit pack
that is supported in the slot (refer to the “Shelf circuit packs and slot numbers”
table in chapter 1 of Planning - Ordering Information, 323-1851-151), a circuit
pack of the correct equipment type, or a filler card. Refer to the equipment
Replacement, 323-1851-545.
support group.
—end—

Procedure 4-18
Autoprovisioning Mismatch - Pluggable
Alarm ID: 343
Probable cause
This alarm is raised when an SFP/SFP+/XFP/CFP/DPO installed in an
unprovisioned port of a circuit pack is not supported for that circuit pack.
When auto equipping is disabled, this alarm is not raised.
Impact
Minor, non-service-affecting (m, NSA) alarm for inactive pluggable
Critical, service-affecting (C, SA) alarm for active pluggable
Prerequisites
323-1851-545
• obtain a supported replacement SFP/SFP+/XFP/CFP/DPO for the
corresponding circuit pack (refer to the “Supported
SFP/SFP+/XFP/CFP/DPO modules for interface circuit packs” table in
chapter 7 of 6500 Planning, NTRN10CF)
Step Action
in this document. The Unit field in the Active Alarms application specifies
the circuit pack, shelf ID, circuit pack slot, and SFP/SFP+/XFP/CFP/DPO port
using the following format:
<circuit pack>-<shelf-id>-slot#-SFP/SFP+/XFP/CFP/DPO port#
3 Replace the SFP/SFP+/XFP/CFP/DPO you identified in step 1 with a
supported SFP/SFP+/XFP/CFP/DPO. Refer to the “Replacing an
SFP/SFP+/XFP/CFP module” or “Replacing an OC-48/STM-16 DWDM
plug-in optics (DPO) module” procedure in Fault Management - Module
support group.
—end—

Procedure 4-19
Backplane ID Module 1/2 Failed
Alarm IDs: 679, 680
Use this procedure to clear the following alarms:
• Backplane ID Module 1 Failed
• Backplane ID Module 2 Failed
Probable cause
This alarm is raised when the shelf identifier unit 1 or unit 2 on the backplane
has failed, is missing, has invalid data, or cannot be read.
Impact
Step Action
2 If Then go to
the shelf has 2 shelf processors with protection step 6
provisioned
otherwise step 3
3 Cold Restart the shelf processor. Wait five minutes for the shelf processor to
restart. Refer to the “Restarting a circuit pack or shelf processor” procedure
in chapter 2 of this document.
4 If the alarm is Then go to
cleared This procedure is complete.
not cleared step 5
5 Reseat the shelf processor. Wait five minutes for the shelf processor to
restart. Refer to the “Reseating a circuit pack” procedure in Fault
Management - Module Replacement, 323-1851-545. Go to step 15.
6 Perform a manual shelf processor protection switch. Refer to the “Operating
a protection switch” procedure in Part 2 of Configuration - Provisioning and
Operating, 323-1851-310.
7 If the alarm is Then go to
cleared step 8
not cleared step 9
8 Perform a protection switch to switch back to the originally active SP (if

needed). This procedure is complete.


Backplane ID Module 1/2 Failed
Step Action
9 Cold Restart the Standby SP. Wait five minutes for the shelf processor to
restart.
10 If the alarm has not cleared, perform another manual shelf processor
protection switch. Refer to the “Operating a protection switch” procedure in
11 Cold Restart the Standby SP and wait 5 minutes.
12 If the alarm has not cleared, reseat the standby shelf processor and wait 5
minutes. Refer to the equipment replacement procedures in chapter 2 of Fault
Management - Module Replacement, 323-1851-545.
13 If the alarm is Then
cleared This procedure is complete.
14 Reseat the active shelf processor. This will cause an automatic shelf
processor protection switch. Wait five minutes for the shelf processor to
restart. Refer to the “Reseating a circuit pack” procedure in Fault
15 If the alarm did not clear, contact your next level of support or your Ciena
support group.
—end—

Procedure 4-20
Calibration Required
Alarm ID: 1716
Probable cause
This alarm is raised when calibration of the RAMAN amplifier is required.
Impact
Step Action
1 Perform a manual calibration on the RAMAN amplifier. The alarm clears when
the calibration is successful. Refer to the “Performing a manual power audit”
323-1851-310.
support group.
—end—

Procedure 4-21
CCM Error
Alarm ID: 1208
Probable cause
This alarm is raised against a Maintenance Association (MA) entity when a
Maintenance End Point (MEP) receives at least one Continuity Check
Message (CCM) with an incorrect transmission interval, or same MEPID as
the receiving MEP, or with unknown MEPID (but the MA and MD level are
correct).
Attention: It takes 3.5 times the “incorrect transmission interval received” to

clear the alarm. If the “incorrect transmission interval received” is 10 minutes
(maximum value allowed), it will take approximately 35 minutes to clear the
alarm once the problem is fixed.
Impact
Major, Service-affecting (M, SA) alarm
Step Action
1 Verify the MEPs on both nodes (local MEP and the remote MEP) are
transmitting CCM with the same CCM interval value. Refer to the “Data
services Ethernet OAM provisioning” chapter in Part 3 of Configuration -
Bandwidth and Data Services, 323-1851-320.
2 If the CCM interval values are different, ensure that the service is not
cross-connected to another service.
Attention: If there are multiple RMEPs, use the "RTRV-MEP-DEFECTS2"

TL1 command (or) the 'Defects' tab in Ethernet OAM provisioning window in
Site Manager to isolate the alarm condition against a specific RMEP.
support group.
—end—

Procedure 4-22
Channel Controller: Failure Detected
Alarm ID: 709
Probable cause
This alarm is raised against a WSSOPM circuit pack when the WSS controller
is unable to function properly. Conditions that can cause this alarm include:
• the WSS w/OPM circuit pack has failed
• there is a loss of signal on one of the channels carried by the WSSOPM
circuit pack
• the OPM is not provisioned against LIM (SLA, MLA C-Band, MLA2
C-Band, MLA2 w/VOA, MLA3 C-Band, LIM C-Band) monitor ports (there
is an adjacency provisioning error)
• the WSSOPM circuit pack provisioning data is invalid
• the fibers to the WSSOPM circuit pack monitor ports are crossed or
connected to a wrong OSC card.
Attention: Use optical terminators on unused input faceplate connectors of

installed WSS w/OPM circuit packs. If dust caps are used instead of optical
terminators on “Switch In” ports, PMs can be reported against the ports and
the ports may appear in-service.
Impact
Prerequisites
• have the engineering documentation package (EDP) containing shelf
details
• have a replacement circuit pack if required


Step Action
1 Check for and clear any active Circuit Pack Failed alarm if raised against the
WSS w/OPM circuit pack.
3 Check for and clear any of the following adjacency alarms:

• Adjacency Mismatch
• Adjacency Far End Not Discovered
5 Check for and clear any of the following alarms on all network elements
before clearing the Channel Controller: Failure Detected alarm:
• Loss of Signal
• Output Loss of Signal
• Shutoff Threshold Crossed
• Channel Controller: Unexpected Loss Detected
7 Verify the LIM (SLA, MLA C-Band, MLA2 C-Band, MLA2 w/VOA, MLA3
C-Band, LIM C-Band) adjacency of the LIM monitor port to ensure that the
Expected far end address field has the correct WSS OPM module port
listed, and that the corresponding Adjacency type field has the correct
adjacency type listed (OPM). Refer to the “Retrieving equipment and facility
details” procedure in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.


Step Action
9 Verify the derived OPM to LIM adjacency. Check the OPM adjacency of the
OPM monitor port to ensure that the Expected far end address field has the
correct LIM module port listed, and that the corresponding Adjacency type
field has the correct adjacency type listed (LIM). Refer to the “Retrieving
equipment and facility details” procedure in Part 1 of Configuration -
11 Verify that the CHC facilities associated with the WSSOPM circuit pack have
the correct Switch Selector provisioned. Correct any discrepancies. Refer to
the “Retrieving equipment and facility details” and “Editing facility parameters”
procedures in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
13 Check the Secondary State of the CHC facilities associated with the
WSSOPM circuit pack. Refer to the “Retrieving equipment and facility details”
323-1851-310.
If only certain (not all) CHC facilities indicate a FAF condition (facility failure),
this can indicate a problem with the channel(s) added from a CMD44 module.
15 Check the shelf-to-shelf association. The Associated OTS field should list
the adjacent OTS (TID-shelf-instance), and the Actual Associated OTS
should be the same as the Associated OTS. Refer to the “Retrieving OTS
Management, OTS Equipment, and Facility Details” procedure in Part 2 of
16 If the Then
Associated OTS shows the incorrect correct the Associated OTS field
adjacent OTS
Actual Associated OTS is not the verify the inter-shelf
same as the Associated OTS communications
17 If necessary, repeat step 15 and step 16 on each adjacent shelf.


Step Action

19 Verify that all LIM (SLA, MLA C-Band, MLA2 C-Band, MLA2 w/VOA, MLA3
C-Band, LIM C-Band) to OPM fibers are connected to the correct ports and
that the fiber is clean. Refer to cleaning connectors procedures in chapter 7
of Part 2 of Installation, 323-1851-201.
21 Perform a warm restart on the WSSOPM circuit pack. Refer to the “Restarting
a circuit pack or shelf processor” procedure in chapter 2 of this document.
23
CAUTION
A cold restart on an unprotected circuit pack causes
traffic loss. A cold restart on an active protected circuit
pack causes a protection switch that impacts traffic.
Perform a cold restart on the WSSOPM circuit pack. Refer to the “Restarting
a circuit pack or shelf processor” procedure in chapter 2 of this document.
support group.
—end—

Procedure 4-23
Channel Controller: Unexpected Loss Detected
Alarm ID: 877
Probable cause
This alarm is raised against a Selective Mux/Demux (SMD) 50 GHz C-Band
8x1 or WSS w/OPM circuit pack when the WSS controller is unable to function
properly. Conditions that can cause this alarm include:
• the WSS w/OPM circuit pack has failed
• the difference between the expected loss and the measured loss is greater
than 6 dB
• there is a loss of signal on one of the channels carried by the WSS w/OPM
circuit pack
• wrong wavelength provisioning of channels
• the OPM is not provisioned against LIM (SLA, MLA C-Band, MLA2
C-Band, MLA2 w/VOA, MLA3 C-Band, LIM C-Band) monitor ports (there
is an adjacency provisioning error)
• the WSS w/OPM circuit pack provisioned data is invalid
• the fibers to the OPM monitor ports are crossed or connected to a wrong
OSC card
• the transmitter power at the CMD44 ingress port is not within +/- 3 dBm of
the provisioned Max/Typical Launch Power for that Tx adjacency. The
alarm is raised on managed channels that have this unexpected power
level, or on inactive channels that are being manually pre-checked with
this unexpected power level. This condition only applies to the CMD44
module.
• this alarm will be raised against the WSS, if there is a fiber break between
a CMD44 common out (or a BMD2 common out, or a WSS switch output)
and the corresponding WSS switch input port.
• there is a problem with the SMD switch out to CCMD12 common in fiber,
the DIA LIM Line B Monitor to DIAWSS monitor in fiber, or the CCMD12
mon to SMD OPM fiber



Impact
Prerequisites
details
• have a replacement circuit pack if required
Step Action
1 If the alarm Then go to

is raised against the WSS circuit pack step 2
is raised against the SMD circuit pack step 3
otherwise step 9
2 At the WSS site, check the CHC facility status against the affected WSS
equipment. Note that in Site Manager you can click the switch selector
column to sort the channels by port.
3 Check for channels with a secondary state of SGEO. Refer to the “Primary
and secondary states” section in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
4 Verify whether all channels from a particular port, or just a subset are
affected. If all channels on a switch port are SGEO, then there is a problem
with the fiber connection between the WSS switch input port and the
connected equipment (CMD44, BMD2, or WSS). If a subset (or single)
channel on a particular switch port are SGEO, and the channel is not locally
added at that node, then this may indicate a WSS hardware fault. Replace the
WSS circuit pack. Refer to the “Replacing the WSS w/OPM or SMD 50GHz
w/OPM circuit pack” procedure in Fault Management - Module Replacement,
323-1851-545.
5 For the SMD circuit pack, if all pixels on a given switch are SGEO and it is in
the demux direction, check the fiber between the SMD switch out and the
CCMD12 common in. Check the DIA LIM LINE B OPM fiber. Check the
CCMD12 mon to SMD OPM fiber.


Step Action
7 Verify the facility and equipment secondary state of the connected

equipment. Refer to the “Primary and secondary states” section in Part 1 of
8 If secondary states such as; Supporting entity outage, FAF, Auto in-service,
or SGEO exist, verify the failure. See the “Facility secondary states” table in
Part 1 of Configuration - Provisioning and Operating, 323-1851-310 for
description of each failure.
9 Check for and clear any active Circuit Pack Failed alarm raised against the
WSS w/OPM circuit pack.
11 Check for and clear any of the following adjacency alarms:


before clearing the Channel Controller: Failure Detected alarm:
• Loss of Signal



Step Action
15 Check the wavelength provisioning of the line cards to make sure that it
matches the wavelength of the CMD port the card is connected to. Refer to
the “Retrieving equipment and facility details” procedure in Part 1 of
For OTM2, OTM3 or OTM4 parameters, refer to the “OTM2 facility
parameters” table, “OTM3 facility parameters” table, or “OTM4 facility
parameters” table in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
17 Verify the LIM (SLA, MLA C-Band, MLA2 C-Band, MLA2 w/VOA, MLA3
C-Band, LIM C-Band, XLA) adjacency of the LIM monitor port to ensure that
the Expected far end address field has the correct WSS OPM module port
listed, and that the corresponding Adjacency type field has the correct
adjacency type listed (OPM). Refer to the “Editing facility parameters”
323-1851-310.
Refer to the “ADJ/ADJ-LINE/ADJ-TX/ADJ-RX/ADJ-FIBER facility
parameters” table in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
19 Verify the derived OPM to LIM adjacency. Check the OPM adjacency of the
WSS OPM monitor port to ensure that the Expected far end address field
has the correct LIM module port listed, and that the corresponding
Adjacency type field has the correct adjacency type listed (LIM). Refer to the
21 Check the shelf-to-shelf association. The Associated OTS field should list
the adjacent OTS (TID-shelf-instance), and the Actual Associated OTS
should be the same as the Associated OTS. Refer to the “Retrieving OTS
Management, OTS Equipment, and Facility Details” procedure in Part 2 of


Step Action
22 If the Then
Associated OTS shows the incorrect correct the Associated OTS field
adjacent OTS
Actual Associated OTS is not the verify the inter-shelf
same as the Associated OTS communications
23 If necessary, repeat step 21 and step 22 on each adjacent shelf.

25 Verify that all LIM (SLA, MLA C-Band, MLA2 C-Band, MLA2 w/VOA, MLA3
C-Band, LIM C-Band, XLA) to WSS OPM fibers are connected to the correct
ports. Refer to Engineering Documentation Package (EDP). Verify that the
fiber is clean. Refer to chapter 7, “Cleaning connectors” in Part 2 of
Installation, 323-1851-201.
27 Using the Domain Optical Controller (DOC) application, check for channels
that have a channel condition of “Pre-Check Fail” or “Fault Detected”. From
the Site Manager window, click on Configuration - Domain Optical Controller
(DOC) window and verify channel condition. If these channel conditions are
the cause of this alarm, the DOC Action: Fault Detected alarm will be raised.
28 Check the DOC logs to determine which channel has the unexpected ingress
power. (From the Site Manager window, click on Configuration - Domain
Optical Controller (DOC) window and then select DOC Logs button in Site
Manger.) For this channel, verify (and if necessary, adjust) the power level at
the source.
30 Perform a warm restart on the WSS w/OPM circuit pack. Refer to the
“Restarting a circuit pack or shelf processor” procedure in chapter 2 of this
document.


Step Action
32
CAUTION
A cold restart on an unprotected circuit pack causes
traffic loss. A cold restart on an active protected circuit
pack causes a protection switch that impacts traffic.
Perform a cold restart on the WSS w/OPM circuit pack. Refer to the
“Restarting a circuit pack or shelf processor” procedure in chapter 2 of this
document.
support group.
—end—

Procedure 4-24
Channel Degrade
Alarm ID: 1283
Probable cause
This alarm is raised when the WSS (or SMD) CHC facility ‘Derived Input
Power’ is less than the value of ‘Reference Input Power Profile’ minus the
‘Minor or Major Degrade Threshold’.
The Minor Degrade Threshold defaults to 3 dB and can be user-provisioned

between 0 to 30 dB using the Site Manager Node Information application and
the Systems settings.
Attention: Major Degrade Threshold has to be greater than the Minor

Degrade Threshold. An attempt to edit major degrade threshold lower than
minor degrade threshold, will be blocked by the system.
The Major Degrade Threshold defaults to 6 dB and can be user-provisioned

between 0 to 30 dB and has a function as described below.
The “Reference Input Power Profile” parameter displays a referenced or

baselined value for the Derived Input Power parameter. This power profile
helps determine how the channel power changes over time. The power profile
is system reset after a capacity change (i.e., a channel add or delete) or can
be user reset using the “Reset Power Profile” button in the Equipment and
Facility Provisioning application or can be user reset using the Reset TCA
Baselines button in the DOC application.
If a channel is found to be below its previously stored value by more than a

threshold, a minor degrade alarm is raised and the CFS is updated for that
channel.
System behavior due to change in Derived Input Power

• Up to 3 dB low in derived input power
— No alarms or CFS change. Re-optimize the channels
• 3 to 6 dB low in derived input power
— Channel Degrade (minor, NSA) alarm, CFS set to “Degrade Minor”
channel dropped from control list, hold channel at current pixel setting
• 6 dB low in derived input power
— Channel Degrade (minor, NSA) alarm, CFS set to “Degrade Major”
channel dropped from control list, hold channel at current pixel setting


Channel Degrade
On a CHC facility of a WSS in a ROADM OTS (or DIA OADM OTS), or on a

CHC facility of an SMD in a COADM OTS, if:
• the ‘Derived Input Power’ of a channel is less than the value of ‘Reference
Input Power Profile’ minus the ‘Minor Degrade Threshold’, then the
‘Channel Degrade’ minor, NSA alarm is raised. This triggers the freezing
of the pixel of the affected channel on the WSS (or SMD) circuit pack. The
Channel Fault Status (CFS) in the DOC application displays ‘Degrade
Minor’ when the Minor degrade condition exists on the affected channel.
• the ‘Derived Input Power’ of a channel is less than the value of ‘Reference
Input Power Profile’ minus the ‘Major Degrade Threshold’, then the
‘Channel Degrade’ minor, NSA alarm is raised. This triggers the freezing
of the pixels of the affected channels on the WSS (or SMD) circuit pack.
The Channel Fault Status (CFS) in the DOC application displays ‘Degrade
Major’ when the Major degrade condition exists on the affected channel.
Note that one Channel Degrade alarm is raised per affected channel, which
means, more than one ‘Channel Degrade’ alarm can be raised against the
same WSS (or SMD) equipment.
It is strongly recommended that the Minor Degrade and Major Degrade

Thresholds remain at their default values.
Any drop in power that occurs prior to the WSS input could lead to the degrade
condition.

Impact


Channel Degrade
Prerequisites
• have the optical fiber/cable connection information (that is, how the circuit
packs on each network element connect to other network elements)
• have an optical power meter with the same optical connectors as the
network element
323-1851-545
Step Action
in this document.
2 If there are any Photonic alarms active, troubleshoot those alarms in the
system first before trying to troubleshoot this alarm.
3 If no Photonic alarm is active, try to identify and fix any potential drop in power
along the channel's path all the way to the head end service circuit pack.
Attention: If the CHC facility 'Reset Power Profile' button is used to reset the
power profile, it will affect the channels that were selected before clicking the
button. If the DOC reset TCA Baseline button is used, it will affect the whole
domain Power Profile
5 If the fiber degrade is a known issue to the system and you want to clear the
alarm, update the input power profile of the affected WSS CHC facility on the
WSS by clicking on the "Reset Power Profile" button in the equipment and
facilities screen after selecting one or more affected channels.


Channel Degrade
Step Action

Attention: Clicking the Reset TCA Baselines Button from the DOC facility
not only resets the 'Reference Input Power Profile' of each and every CHC
facility of that domain but also resets the 'TCA Baselines' of the applicable
facilities of the whole domain.
7 If the fiber degrades in DOC domain is a known issue to the system and you
want to clear the alarms of the whole domain rapidly, click the ‘Reset TCA
Baselines’ Button from the DOC facility. The reset TCA Baseline command
will reset all Channel Degrade alarms in that domain. If the Channel Degrade
alarm(s) cleared, then the procedure is complete.
support group.
—end—

Procedure 4-25
Channel Opacity Error
Alarm ID: 1433
Probable cause
This alarm is raised when a WSS pixel of a ROADM OTS is incorrectly set to
Opaque (the CHC facility Opaque parameter is set to Yes), while a DOC-
managed channel is meant to be using it.
The alarm is raised against the CHC facility at the shelf where the problem is
detected
Impact
Prerequisites
323-1851-545
Step Action
1 Ensure that the CHC facility against which the alarm is raised, is used by a
DOC managed channel.
2 Change the WSS pixel to OPAQUE = NO. Refer to the “Editing facility
parameters” procedures in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
support group.
—end—

Procedure 4-26
Circuit Pack Configuration Save Failed
Alarm ID: 1766
Probable cause
This alarm is raised when the shelf processor fails to backup L2 configuration
from an eMOTR circuit pack.
Impact
Step Action
1 No action is necessary. The NE automatically retries to save the configuration

data. If the action is successful, the alarm clears.
2 If the alarm does not clear after five minutes, contact your next level of
support or your Ciena support group.
—end—

Procedure 4-27
Circuit Pack Failed
Alarm IDs: 56, 581
Probable cause
This alarm is raised in the following situations:
• the trouble detection circuits of a circuit pack detect a failure
• the shelf processor detects a major failure on another circuit pack
Both the alarm and LED alarm indicators can report the failure at the same
time. If not, verify that a shelf processor problem does not exist. The status
LED comes on (red indicates a failure) after a circuit pack is inserted until it is
completely booted. The circuit pack is not failed in this case. This LED must
clear one minute after insertion.
When the 63xE1 circuit pack fails, all 63xE1 facility states show as OOS-AU.
The unprotected E1 ports will function on a best effort basis and can be
carrying traffic even if the equipment shows as failed and the E1 facilities show
as OOS-AU.
For WSS w/OPM equipment, this alarm is raised when two or more
wavelengths have a drift frequency of more than 25 GHz.
When a Circuit Pack Failed alarm is raised, some hardware may not be
operational. This can cause inaccuracies in the PM counts for facilities on this
circuit pack.
For a Submarine Line Idler 10 Channel (SLIC10 C-Band or SLIC10 Flex

C-Band) circuit pack, this alarm is also raised when all five idler facility pairs
have a laser failure condition.
For the XLA circuit pack, this alarm is raised when the amplifier cannot switch
modes (cannot set the switch selector to either Low/High Gain).
For the SRA circuit pack, this alarm is raised when there are failures (for
example, laser pumps, analog/digital converter) during powerup or when the
RAMAN pump does not turn on due to hardware failure.
Impact
Critical, service-affecting (C, SA) alarm for:
• circuit packs in 2-Fiber/4-Fiber BLSR/MS-SPRing/HERS configuration
with protection circuit pack faulty/unavailable
• circuit packs in UPSR/SNCP configuration with cross-connects


Circuit Pack Failed
• working circuit pack in 1+1/MSP linear configuration with protection circuit

pack faulty/unavailable
• working circuit pack in 1:N protection configuration with protection circuit
pack faulty/unavailable
• circuit pack in unprotected configuration with cross-connects
Minor, non-service-affecting (m, NSA) alarm for

• circuit pack in 2-Fiber/4-Fiber BLSR/MS-SPRing/HERS configuration with
protected circuit pack available
• inactive or protected circuit pack in 1+1/MSP linear configuration
• circuit pack without cross-connects
• 1:N protection configuration
• working circuit pack with protection circuit pack available or for protection
circuit pack with all working circuit packs available
MSPP alarm severity depends on the circuit pack and the following
conditions:
• If both XC circuit packs fail, two C, SA alarms are raised.
• An OC-n/STM-n UPSR/SNCP configuration raises critical,
service-affecting alarms whether protected or unprotected.
• Alarms with critical, service-affecting severity occur when the 4xGE,
1x10GE EPL or an unprotected active circuit pack is faulty.
• Alarms with minor, non-service-affecting (m, NSA) severity occur when
the circuit pack is protected or when the circuit pack is unprotected and
active without cross-connects, or when the circuit pack is unprotected and
inactive.
• For multi-port circuit packs with ports configured with different protection
schemes, the circuit pack assumes the highest alarm severity.
Broadband services
Critical, service-affecting (C, SA) alarm for:
• an active circuit pack or unprotected SuperMux circuit pack
• working circuit pack in 1+1/MSP linear, 1+1 port TPT, or 1+1 TPT
configuration with protection circuit pack faulty/unavailable


Circuit Pack Failed
Minor, non-service-affecting (m, NSA) alarm for:

• an inactive circuit pack (with no cross-connects for SuperMux and OTSC
circuit packs)
• inactive or protected circuit pack in 1+1/MSP linear, 1+1 port TPT, or 1+1
TPT configuration
Photonic services
Critical, service-affecting (C, SA) alarm
Major, service-affecting (C, SA) alarm for XLA, SRA, SAM, and ESAM circuit
packs
Table 4-1 on page 4-79 lists severities for the shelf processor and circuit
packs.
Prerequisites
323-1851-545
• have a replacement circuit pack for the failed circuit pack
Step Action
1 Perform a DGN-EQPT command. If the alarm did not clear, continue to the
next step.
2 Determine the time since the “Circuit Pack Failed” alarm was raised. Design
expert data is automatically saved after a “Circuit Pack Failed” condition. This
will take 5 minutes for the TRIB circuit packs and 10 minutes for the SP. It is
recommended that circuit packs are not replaced during this time after the
“Circuit Pack Failed” alarm has raised. The design expert data will not be
captured if you do not wait.
in this document.
If the failure is against the shelf processor, it may not be possible to log into
the network element to determine the active alarms.


Circuit Pack Failed
Step Action
5 Replace the faulty circuit pack. Refer to the equipment replacement

323-1851-545.
6 Retrieve all alarms and ensure the system is restored to its original state.
If the original alarm has Then go to
cleared step 7
not cleared step 10
7 Select Shelf Level View from the Configuration menu. (This takes you to
the Physical Shelf view of the Visualization tool) Alternatively, select
Visualization from the Tools menu, and then select Physical Shelf from the
drop-down menu in the Control area.
8 Ensure that the new circuit pack is displayed in the Physical Shelf view of the
Visualization tool.
9 For a SLIC10 or SLIC10 Flex C-Band circuit packs this alarm is a latched
alarm which means it is not cleared on the circuit pack even if the fault is
cleared. Perform a restart on the circuit pack. See Restarting a circuit pack or
shelf processor on page 2-29.
support group.
—end—
Table 4-1
Circuit Pack Failed alarm severities
Circuit pack/configuration Inactive/protected Active or

or active without unprotected with
cross-connects cross-connects
DSM 84xDS1 termination module m, NSA C, SA
OC-3 as host for DS1 service module C, SA C, SA
48 Channel Trans Mux (portless) m, NSA C, SA
63xE1 m, NSA C, SA
24xDS3/EC-1 m, NSA C, SA
24xDS3/E3 m, NSA C, SA
16xSTM-1e m, NSA C, SA
4xGE m, NSA C, SA
L2SS VT1.5/LO 4xGE m, NSA C, SA



L2SS DS1/E1/DS3/E3 4xGE (PDH gateway) m, NSA C, SA
20G L2SS m, NSA C, SA
RPR 10G STS-1/HO 4xGE m, NSA C, SA
L2 MOTR m, NSA C, SA
100G OCLD m, NSA C, SA
10x10GE MUX m, NSA C, SA
10x10G MUX m, NSA C, SA
100G OCI m, NSA C, SA
100GE OCI m, NSA C, SA
4x10G Mux m, NSA C, SA
40G UOCLD m, NSA C, SA
FLEX MOTR m, NSA C, SA
8xOTN Flex MOTR m, NSA C, SA
(1+8)xOTN Flex MOTR) m, NSA C, SA
24x10/100BT EPL m, NSA C, SA
1x10GE EPL m, NSA C, SA
1+1/MSP linear (16xOC-3/12/48/STM-1/4/16, HO 10 port, 20G m, NSA C, SA

OC-n/STM-n, 8xOC-3/12/STM-1/4, 8xOC-n/STM-n 5G
VT1.5/LO SFP, 2xOC-48/STM-16, 1xOC-192/STM-64)
UPSR/SNCP configuration (16xOC-3/12/48/STM-1/4/16, HO C, SA C, SA

10 port, 20G OC-n/STM-n, 8xOC-3/12/STM-1/4,
8xOC-n/STM-n 5G VT1.5/LO SFP, 2xOC-48/STM-16,
1xOC-192/STM-64))
2-Fiber/4-Fiber BLSR/MS-SPRing/HERS (2xOC-48/STM-16, m, NSA C, SA

1xOC-192/STM-64, HO 10 port, 20G OC-n/STM-n) (Note 1)
1xOC-192/STM-64 AM1/AM2 DWDM m, NSA C, SA

tunable LO
1xOC-192/STM-64 AM1/AM2 DWDM m, NSA C, SA

tunable HO



XC (Note 2) m, NSA C, SA
MXC m, NSA C, SA
SP (Note 3) m, NSA (Note 4) NA

M, SA (when the
SP is Active)
MIC NA m, NSA
SRA m, NSA C, SA
SAM m, NSA C, SA
ESAM m, NSA C, SA
Note 1: In a 2-Fiber/4-Fiber BLSR/MS-SPRing/HERS configuration, both circuit packs are active.

Note 2: If both XC circuit packs are failed, the alarm severity is C, SA on both slots.
Note 3: The severity of the “Circuit Pack Fail” alarm for the SP is not affected by the presence/absence
of cross-connects.
Note 4: The minor, non-service affecting severity only applies if there are two shelf processors
provisioned and equipped.

Procedure 4-28
Circuit Pack Failed - Pluggable
Alarm ID: 340
Probable cause
This alarm is raised when a provisioned SFP/SFP+/XFP/CFP/DPO fails.
This alarm can be raised on an OC-48/STM-16 DPO circuit pack, when the
optical input power is too high.
Impact
Prerequisites
323-1851-545
network element
• obtain a supported replacement SFP/SFP+/XFP/CFP/DPO for the
corresponding circuit pack (refer to the “Supported
SFP/SFP+/XFP/CFP/DPO modules for interface circuit packs” table in
chapter 7 of 6500 Planning, NTRN10CF)
Step Action


Circuit Pack Failed - Pluggable
Step Action
3 If the alarm is raised on an OC-48/STM-16 DPO circuit pack, measure the

receive power using an optical power meter. if the receive power is above the
maximum, add the necessary attenuation to try to reduce the receive power
to a value below the maximum receive optical power (but above the minimum
receive optical power).
4 If the alarm did not clear, replace the SFP/SFP+/XFP/CFP/DPO you
identified in step 1 with a supported SFP/SFP+/XFP/CFP/DPO. Refer to the
equipment replacement procedures in chapter 2 of Fault Management -
Module Replacement, 323-1851-545.
support group.
—end—

Procedure 4-29
Circuit Pack Failed-Sync and Circuit Pack
Failed-Traffic
Alarm ID: 88, 90
Use this procedure to clear an XC double fault scenario. If the XC double fault
conditions do not exist, follow the circuit pack fail procedure. Refer to Circuit
Pack Failed on page 4-76.
Probable cause
This alarm indicates that the XC circuit packs failed in their bandwidth
management or synchronization.
If a XC double fault scenario exists, follow this procedure to replace the XC

circuit pack. Both circuit packs are partially functioning. If you remove either
circuit pack, you will cause shelf traffic loss.
Use this procedure to clear an XC double fault scenario. If the XC double fault
conditions do not exist, follow the circuit pack fail procedure. Refer to Circuit
Pack Failed on page 4-76.
Use this procedure if on one XC circuit pack, the Circuit Pack Failed - Sync
alarm is indicated by the red LED being ON; and on the other XC circuit pack,
the Circuit Pack Failed - Traffic alarm is indicated by the red LED being ON.
Impact
CAUTION
The procedure to clear the XC double fault scenario will result
in a 90 second traffic loss. This traffic loss can be up to five
minutes if the replacement circuit pack requires an
auto-upgrade. It is recommended that this procedure be
performed during a maintenance window (when traffic is
lightest), or that all traffic be routed away from the affected
network element before performing this procedure.
Critical, service-affecting (C, SA) alarm if active with cross-connects

Minor, non-service-affecting (m, NSA) alarm if unprotected or with no
provisioned cross-connects
Prerequisites
To perform this procedure, you must observe all safety requirements
described in the “Observing product and personnel safety guidelines” chapter
in Part 1 of Installation, 323-1851-201 or Fault Management - Module


Circuit Pack Failed-Sync and Circuit Pack Failed-Traffic
Step Action
1 Determine if an XC double fault scenario exists. Refer to the Probable cause

section for this alarm.
2 Wait for an appropriate maintenance window when traffic is minimal.
Perform step 4 through step 6 as quickly as possible to minimize traffic loss.
4 Replace the XC circuit pack raising the Circuit Pack Failed - Sync alarm.
Refer to the equipment replacement procedures in chapter 2 of Fault
5 Wait for the green active LED to come on. This normally takes 10 seconds,
but can take five minutes if the circuit pack requires an auto-upgrade.
6 Replace the XC circuit pack raising the Circuit Pack Failed - Traffic alarm.
Removing both XC circuit packs can cause the shelf processor to raise
alarms against other circuit packs, such as Circuit Pack Failed alarms. If this
occurs, remove the alarmed circuit pack for five seconds and then insert it.
support group.
—end—

Procedure 4-30
Circuit Pack Latch Open
Alarm ID: 100
Probable cause
This alarm is raised when the bottom/lower locking lever on the circuit pack is
not fully closed and the circuit pack is inserted into a slot, or the latch on the
circuit pack is broken.
This alarm is not supported on the following circuit packs:

• all variants of amplifiers (MLA C-Band, MLA L-Band, MLA2 C-Band, MLA2
w/VOA, MLA3 C-Band, LIM C-Band, LIM L-Band and FGA)
• all variants of the WSS and sCMD4
• the SMD, CCMD12, OPM, and OSC

Impact
Prerequisites
Step Action
in this document.
3 Ensure that the circuit pack raising the alarm is pushed all the way into its slot,
until the locking levers touch their latches.


Circuit Pack Latch Open
Step Action
4 Lock the circuit pack into its slot by pushing the upper locking lever down and
the lower lever up at the same time.
Attention: Do not force the locking levers. If the levers do not close correctly,
gently re-insert the circuit pack. If the circuit pack cannot be re-inserted,
remove the circuit pack and go to step 5.
support group.
—end—

Procedure 4-31
Circuit Pack Mate Mismatch
Alarm ID: 589
Probable cause
This alarm is raised by both cross-connect circuit packs when incompatible
cross-connect circuit packs are paired in slots 7 and 8 of the 14-slot shelf or
slots 9 and 10 of the 32-slot shelf. Slot 7 and 8 of the 14-slot shelf or slots 9
and 10 of the 32-slot shelf must contain the same type of cross-connect circuit
pack, with the same PEC.
This alarm is the result of an incorrect cross-connect circuit pack replacement

or installation, and is raised during cross-connect configuration or
reconfiguration.
Impact
Prerequisites
Step Action
1 If you are performing a cross-connect circuit pack reconfiguration procedure,

complete the reconfiguration before proceeding to the next step. Refer to the
Module Replacement, 323-1851-545 for details. If the alarm is still present
after the reconfiguration procedure is complete, go to step 2.
2 Select Shelf Level View from the Configuration menu to open the network
element Shelf Level View and check the details (PEC) of the cross-connect
circuit packs in slots 7 and 8 of the 14-slot shelf or slots 9 and 10 of the 32-slot
shelf.
If the PECs of both cross-connect circuit packs Then go to
are different step 3
are the same step 4
3 Provision the PEC on the cross-connect circuit pack with the incorrect PEC
to the correct PEC (same as the mate cross-connect circuit pack). Refer to
the “Changing the provisioned PEC, the SuperMux equipment profile, or 40G
XCIF equipment mode” procedure in Part 1 of Configuration - Provisioning
support group.
—end—

Procedure 4-32
Circuit Pack Mismatch
Alarm ID: 36, 580
Probable cause
This alarm is raised when a circuit pack is equipped in or inserted into a slot
provisioned for:
• a circuit pack of another type
• a circuit pack of the same type that supports additional features (in this
case, the circuit packs have different/mismatched PECs)
During provisioning, a slot is assigned a specific facility and circuit pack type.
The assignments are recorded in the provisioning database.
For passive modules (such as CMD44, DSCM, OMD4, OMX, TPT, BMD2,
UBMD2, MBMD2, TPT, PPC6, passive photonic chassis) this alarm is raised
when, the module connected to the Access Panel External slot port does not
match the provisioned module. This alarm is raised when a passive photonics
module (such as a OMDF4, OMDF8, BS1, BS2, BS3, BS5 or OSCF) is
inserted into a PPC6 sub-slot that does not match the provisioned module.
The alarm clears if the circuit pack in the specified slot is manually put
out-of-service.
Impact
Critical, service-affecting (C, SA) alarm for unprotected shelf processor circuit
pack
Minor, non-service-affecting (m, NSA) alarm for protected shelf processor
circuit pack
MSPP services
Critical, service-affecting (C, SA) alarm for 2-Fiber/4-Fiber
BLSR/MS-SPRing/HERS, unprotected circuit pack
Critical, service-affecting (C, SA) alarm for UPSR/SNCP configuration with
cross-connects
Critical, service-affecting (C, SA) alarm if active 1+1/MSP linear or
unprotected with cross-connects
Critical, service-affecting (C, SA) alarm for working circuit pack in 1:N
protection configuration with protection circuit pack faulty/unavailable
Minor, non-service-affecting (m, NSA) alarm for 2-Fiber/4-Fiber

BLSR/MS-SPRing/HERS, protected circuit pack
Minor, non-service-affecting (m, NSA) alarm if inactive 1+1/MSP linear,
protected 1+1/MSP linear, or without cross-connects


Minor, non-service-affecting (m, NSA) alarm for 1:N protection configuration

working circuit pack with protection circuit pack available or protection circuit
pack with all working circuit packs available
An equipment protection switch occurs if protection is available. If the circuit

pack is unprotected, shelf functions can be disrupted.
For multi-port circuit packs with ports configured with different protection
BB services
Critical, service-affecting (C, SA) alarm for an active circuit pack or
unprotected SuperMux circuit pack
Critical, service-affecting (C, SA) alarm for working circuit pack in 1+1/MSP
linear, 1+1 port TPT, or 1+1 TPT configuration with protection circuit pack
faulty/unavailable
Minor, non-service-affecting (m, NSA) alarm for an inactive circuit pack (with
no cross-connects for SuperMux and OTSC circuit packs)
Minor, non-service-affecting (m, NSA) alarm for inactive or protected circuit
pack in 1+1/MSP linear, 1+1 port TPT, or 1+1 TPT configuration
Photonic services
Table 4-2 on page 4-92 lists expected severities for each circuit pack if any
cross-connects are provisioned.
Prerequisites
Replacement, 323-1851-545
Step Action
1 Use one of the options below to view the shelf inventory:

• select Inventory from the Configuration menu
• select Equipment & Facility Provisioning from the Configuration
menu
• select Shelf Level View (Physical Shelf view in the Visualization tool)
from the Configuration menu


Step Action
3 Verify the shelf inventory using one of the methods below:
• If using the Shelf Inventory application, compare the slot assignments
and physical PECs listed with the actual circuit packs in the shelf until you
identify the mismatched circuit pack.
• If using the Equipment & Facility Provisioning application, compare
the slot assignments and provisioned PECs listed in the with the actual
circuit packs in the shelf until you identify the mismatched circuit pack.
• If using the Shelf Level View application, compare the slot assignments
in the Circuit Pack Details tab of the with the actual circuit packs in the
shelf until you identify the mismatched circuit pack.
Mismatched circuit packs can be the same type, but have different PECs (for
example, redundant shelf processor or MSPP circuit packs). In these cases,
ensure PECs match. Refer to the Probable cause section for this alarm.
If you are not on site, use one of the following methods to identify any
mismatches between the physical PEC and provisioned PEC by comparing
the:
• Phys. PEC and the Prov. PEC in the Circuit Pack Details tab in the
Shelf Level View application
• Provisioned PEC in the Equipment & Facility Provisioning application
and the Physical PEC in the Shelf Inventory application
A mismatch can indicate a PEC provisioning error or an incorrect circuit pack
is installed.
4 If you have Then go to
identified the mismatched circuit pack step 5
not identified the mismatched circuit pack step 7
5 Replace the mismatched circuit pack with an appropriate circuit pack. Refer
to the equipment replacement procedures in chapter 2 of Fault Management
- Module Replacement, 323-1851-545.
in this document.


Step Action
8 Replace the circuit pack you identified in step 7. Refer to the equipment
If the alarm clears, the circuit pack you identified in step 7 is damaged.
support group.
—end—
Table 4-2
Circuit Pack Mismatch alarm severities
Circuit pack/configuration Inactive Active
63xE1 m, NSA C, SA
4xGE m, NSA C, SA


(1+8)xOTN Flex MOTR) m, NSA C, SA
1+1/MSP linear (16xOC-3/12/48/STM-1/4/16, 8xOC-3/12/STM-1/4, m, NSA C, SA

8xOC-n/STM-n 5G VT1.5/LO SFP, 2xOC-48/STM-16, 1xOC-192/STM-64, HO 10
port, 20G OC-n/STM-n)
UPSR/SNCP configuration (16xOC-3/12/48/STM-1/4/16, HO 10 port, 20G C, SA C, SA

OC-n/STM-n, 8xOC-3/12/STM-1/4, 8xOC-n/STM-n 5G VT1.5/LO SFP,
2xOC-48/STM-16, 1xOC-192/STM-64)
2-Fiber/4-Fiber BLSR/MS-SPRing/HERS (16xOC-3/12/48/STM-1/4/16, HO 10 m, NSA C, SA

port, 20G OC-n/STM-n, 2xOC-48/STM-16, 1xOC-192/STM-64) (Note 1)
1xOC-192/STM-64 AM1/AM2 DWDM tunable LO m, NSA C, SA
1xOC-192/STM-64 AM1/AM2 DWDM tunable HO m, NSA C, SA
10G OTSC m, NSA C, SA
SuperMux m, NSA C, SA
MXC m, NSA C, SA
16xFLEX OTN I/F m, NSA C, SA
XC I/F 40G STS-1/HO m, NSA C, SA
4x10G PKT I/F m, NSA C, SA
6-slot Passive photonic chassis C, SA C, SA
SP m, NSA C, SA
(Note 3)
SRA m, NSA C, SA


SAM m, NSA C, SA
ESAM m, NSA C, SA

Note 2: If both XC circuit packs are mismatched, the alarm severity is C, SA on both slots.
Note 3: The minor, non-service affecting severity is only applicable if there are two shelf processors
provisioned and equipped in the shelf.

Procedure 4-33
Circuit Pack Mismatch - Pluggable
Alarm ID: 342
Probable cause
This alarm is raised when the SFP/SFP+/XFP/CFP/DPO installed, is different
from Provisioned PEC on the circuit pack.
Impact
Prerequisites
323-1851-545
• obtain a supported SFP/SFP+/XFP/CFP/DPO for the corresponding
circuit pack (refer to the “Supported SFP/SFP+/XFP/CFP/DPO modules
for interface circuit packs” table in chapter 7 of 6500 Planning,
NTRN10CF.
Step Action
supported SFP/SFP+/XFP/CFP/DPO. Refer to the equipment replacement
323-1851-545.
support group.
—end—

Procedure 4-34
Circuit Pack Missing
Alarm ID: 35, 579, 681
Probable cause
This alarm is raised when a slot is provisioned and the following occurs:
• no circuit pack is in the designated slot
• circuit pack failure makes the circuit pack undetectable
• the access panel, MIC, or Power Input Cards A/B have been removed from
the system. This alarm masks any existing alarm on that unit. For
example, the Circuit Pack Missing alarm raised against Power Input Card
B masks the Power Failure - B alarm.
• when both the A and B power feeds to one or more zones that supply
power to a circuit pack have failed, the associated “Power Failure A/B” and
“Power Failure - Fuse Blown” alarms must be cleared first in order to clear
this alarm. Refer to the alarm clearing procedures in Part 2 of this
document.
Attention: A Circuit Pack Missing alarm against an access panel

masks/clears certain BITSIN and comms alarms (ILAN, COLAN, etc.) raised
against the access panel before its removal.
Attention: For the X-Conn 1600G PKT/OTN (NTK616AA) and

cross-connect 600G PKT/OTN circuit pack (NTK615AA) circuit packs, it may
take up to five minutes for the “Circuit Pack Missing” alarm to clear after the
inventory displays the circuit pack information.
• DSM 84xDS1 termination module (TM) indicates that its mate is missing
• a provisioned passive module (such as CMD44, DSCM, OMD4, OMX,
TPT, BMD2, UBMD2, MBMD2, TPT, PPC6 Passive Photonic chassis) is
disconnected from the shelf Access Panel External Slot port.
• a provisioned passive module (such as a OMDF4, OMDF8, BS1, BS2,
BS3, BS5 or OSCF) has an open latch or is missing from a sub-slot in an
PPC6 connected to an External Slot. Note that if the External Slot
interface cable to between the PPC6 and host shelf is disconnected or
faulty, the alarm will be raised against the PPC6 external slot number, not
against the passive modules' sub-slot(s).
If you change the state of the circuit pack raising this alarm to OOS, this alarm
clears and the Filler Card Missing alarm is raised.


Attention: Loss of an OAM link to a provisioned DSM 84xDS1 TM while the

OAM link of the mate remains intact, masks all alarms against the circuit
pack except the Circuit Pack Missing alarm. A Circuit Pack Missing alarm
against a DSM 84xDS1 TM masks the OAM Not Available alarm, if it has a
mate with an OAM link (the mate informs the shelf processor that the circuit
pack is missing).
Attention: In some cases, a Circuit Pack Missing alarm is simultaneously

active with a Circuit Pack Upgrade Failed alarm for a particular slot. This
condition can be cleared either by performing a minimal delivery of the
corresponding software release, or by configuring a software release server
for the network element. Refer to the “Transferring a software load to a
network element” procedure in chapter 7 of Administration and Security,
323-1851-301.
Impact
Critical, service-affecting (C, SA) alarm for unprotected shelf processor circuit
pack
Minor, non-service-affecting (m, NSA) alarm for protected shelf processor
circuit pack
MSPP services
Critical, service-affecting (C, SA) alarm for 2-Fiber/4-Fiber
BLSR/MS-SPRing/HERS, unprotected circuit pack
Critical, service-affecting (C, SA) alarm for UPSR/SNCP configuration with
cross-connects
Critical, service-affecting (C, SA) alarm for active 1+1/MSP linear or
Critical, service-affecting (C, SA) alarm for working circuit pack in 1:N
protection configuration with protection circuit pack faulty/unavailable
Minor, non-service-affecting (m, NSA) alarm for 2-Fiber/4-Fiber

BLSR/MS-SPRing/HERS, protected circuit pack
Minor, non-service-affecting (m, NSA) alarm for inactive 1+1/MSP linear,
protected 1+1/MSP linear, or without cross-connects.
Minor, non-service-affecting (m, NSA) alarm for 1:N protection configuration
for working circuit pack with protection circuit pack available or for protection
circuit pack with all working circuit packs available


Alarm severity depends on the following conditions:

• Alarms with critical, service-affecting severity are raised when both circuit
packs in a protection group are pulled out of their slots. In this case, a
m, NSA alarm and a C, SA alarm are raised.
Attention: When both XC circuit packs are removed, a Critical,

service-affecting alarm is raised for each XC circuit pack removed.
An OC-n/STM-n UPSR/SNCP configuration raises critical, service-affecting

Circuit Pack Missing alarms whether protected or unprotected.
• Alarms with critical, service-affecting severity are raised when the 63xE1,
24xDS3/EC-1, 4xGE or 1x10GE EPL circuit pack is not in its provisioned
slot.
• Alarms with critical, service-affecting severity are raised when missing
circuit packs are unprotected.
For multi-port circuit packs with ports configured with different protection
BB services
Critical, service-affecting (C, SA) alarm for an active circuit pack or
unprotected SuperMux circuit pack
Critical, service-affecting (C, SA) alarm for working circuit pack in 1+1/MSP
linear, 1+1 port TPT, or 1+1 TPT configuration with protection circuit pack
faulty/unavailable
Minor, non-service-affecting (m, NSA) alarm for an inactive circuit pack (with
no cross-connects for SuperMux and OTSC circuit packs)
Minor, non-service-affecting (m, NSA) alarm for inactive or protected circuit
pack in 1+1/MSP linear, 1+1 port TPT, or 1+1 TPT configuration
Photonic services
Table 4-3 on page 4-103 lists expected severities for each circuit pack if any
cross-connects are provisioned.


Prerequisites
323-1851-545
• obtain replacement circuit packs
Step Action
in this document.
3 If Then go to
both XC circuit packs are reported missing step 5
the DSM 84xDS1 TM is reported missing step 8
a Type 6 DSCM (PECs NPAD01DB through NPAD17DB) is step 9
reported missing
an equipment connected to External Slots is reported missing step 10
a Passive module in a PPC6 sub-slot is reported missing step 11
any other circuit pack is reported missing step 4
4 If Then
the slot is empty insert a circuit pack of
the correct type into the
slot. Go to step 7.
a circuit pack of the correct type is in the slot go to step 12.
5 Insert the XC circuit pack in slot 7 of the 14-slot shelf or slot 9 of the 32-slot
shelf first.
6 Insert the second XC circuit pack in slot 8 of the 14-slot shelf or slot 10 of the
32-slot shelf.
Slot 7 and 8 or slot 9 and 10 must contain the same type cross-connect circuit
pack with the same PEC.


Step Action
7 Wait 30 seconds and retrieve all alarms to determine if the original alarm has
cleared.
If the original alarm has Then
cleared the procedure is complete.
not cleared go to step 12.
8 If a DSM 84xDS1 TM is missing, insert the required DSM 84xDS1 TM and

link by fiber. Refer to the “Replacing the DSM 84xDS1 TM circuit pack”
procedure in Fault Management - Module Replacement, 323-1851-545 for
details.
Go to step 23.
9 If a Type 6 DSCM is provisioned in slots 83 through 90, delete the associated
facility and equipment and reprovision in virtual slots 91 through 99. Refer to
the “Provisioning a circuit pack, module, or SFP/SFP+/XFP/CFP/DPO
manually” and “Deleting a circuit pack, module, or
SFP/SFP+/XFP/CFP/DPO” procedures in Part 1 of Configuration -
Go to step 23.
10 Verify that the cable between the shelf External Slot Inventory port and the
external peripheral is connected and not damaged.
Go to step 23.
11 If the slot is empty, insert a Passive module of the correct type in a PPC6
sub-slot. Otherwise, make sure that the module is fully inserted and latches
tightly closed. If the card (or their replacement) in the PPC6 or the PPC6 itself
can't be inventoried after replacing the cable, etc., the PPC6 itself will need to
be replaced.
Go to step 23.
12 If the circuit pack Then go to
is still carrying traffic and providing all services step 13
is not carrying traffic and providing all services step 18
13 If the SP Then go to
is in a redundant configuration step 14
is not in a redundant configuration step 17


Step Action
14 Initiate a switch to the backup SP. Refer to the “Operating a protection switch”
323-1851-310. After the system recovers, check if the alarm has cleared.
cleared step 15
not cleared step 18
15 Reseat the previously active SP. Refer to the “Reseating a circuit pack”
procedure in Fault Management - Module Replacement, 323-1851-545.
When it has finished booting initiate a switch back to the originally active SP.
After the system recovers, check if the alarm has cleared.
16 Initiate a switch back to the backup SP. Replace the original SP. Refer to the
“Replacing the shelf processor” procedure in Fault Management - Module
Replacement, 323-1851-545. Initiate a switch back to the newly inserted SP.
After the system recovers, check if the alarm has cleared.
17 Reseat the SP. Refer to the “Reseating a circuit pack” procedure in Fault
18 Reseat the circuit pack raising the alarm. Refer to the “Reseating a circuit
pack” procedure in Fault Management - Module Replacement,
323-1851-545.


Step Action
19 Replace the circuit pack against which the alarm is raised. Refer to the
20 Re-install the original circuit pack into the shelf.

21 If the SP Then go to
is in a redundant configuration step 23
is not in a redundant configuration step 22
22 Replace the SP. Refer to the “Replacing the shelf processor” procedure in
Fault Management - Module Replacement, 323-1851-545.
support group.
—end—

Table 4-3
Circuit Pack Missing alarm severities
63xE1 m, NSA C, SA
4xGE m, NSA C, SA
4x10G Mux m, NSA C, SA
(1+8)xOTN Flex MOTR m, NSA C, SA


Circuit Pack Missing alarm severities
1+1/MSP linear (16xOC-3/12/48/STM-1/4/16, HO 10 port, 20G OC-n/STM-n, m, NSA C, SA

8xOC-3/12/STM-1/4, 8xOC-n/STM-n 5G VT1.5/LO SFP, 2xOC-48/STM-16,
1xOC-192/STM-64)
UPSR/SNCP configuration (16xOC-3/12/48/STM-1/4/16, HO 10 port, 20G C, SA C, SA

OC-n/STM-n, 8xOC-3/12/STM-1/4, 8xOC-n/STM-n 5G VT1.5/LO SFP,
2xOC-48/STM-16, 1xOC-192/STM-64)
2-Fiber/4-Fiber BLSR/MS-SPRing/HERS (16xOC-3/12/48/STM-1/4/16, HO 10 m, NSA C, SA

port, 20G OC-n/STM-n 2xOC-48/STM-16, 1xOC-192/STM-64) (Note 1)
1xOC-192/STM-64 AM1/AM2 DWDM tunable LO m, NSA C, SA
1xOC-192/STM-64 AM1/AM2 DWDM tunable HO m, NSA C, SA
1xOC-192/STM-64 DWDM OTSC m, NSA C, SA
MXC m, NSA C, SA
16xFLEX OTN I/F m, NSA C, SA
XC I/F 40G STS-1/HO m, NSA C, SA
4x10G PKT I/F m, NSA C, SA
6-slot Passive photonic chassis C, SA C, SA
SP (Note 3) m, NSA C, SA
(Note 4)
Access Panel, MIC, or Power Input Cards A/B NA m, NSA

(Note 5)
SRA m, NSA C, SA
SAM m, NSA C, SA
ESAM m, NSA C, SA

Note 2: If both XC circuit packs are removed, the alarm severity is C, SA on both slots.
Note 3: When there is no redundant SP equipped and provisioned, a major audible alarm is the only
indication that the shelf processor is missing.
Note 4: The minor, non-service affecting severity only applies if there are two shelf processors
provisioned and equipped.
Note 5: If the AC Power Input Cards are missing from a 7-slot Type 2 shelf, the alarm is C, SA.

Procedure 4-35
Circuit Pack Missing - Pluggable
Alarm ID: 339
Probable cause
This alarm is raised when a provisioned SFP/SFP+/XFP/CFP/DPO is not
physically installed in the circuit pack.
Impact
Prerequisites
323-1851-545.
circuit pack (refer to the “Supported SFP/SFP+/XFP/CFP/DPO modules
NTRN10CF)
Step Action
3 Install a supported SFP/SFP+/XFP/CFP/DPO module in the port you
identified in step 1. Refer to the “Replacing an SFP/SFP+/XFP/CFP module”
or “Replacing an OC-48/STM-16 DWDM plug-in optics (DPO) module”
support group.
—end—

Procedure 4-36
Circuit Pack 3rd Party - Pluggable
Alarm ID: 1142
Probable cause
This alarm is raised when a third-party pluggable module is inserted into a
provisioned pluggable port and “Third Party Transceivers supported” is
activated.
Impact
Step Action

—end—

Procedure 4-37
Circuit Pack Operational Capability Exceeded
Alarm ID: 1064
Probable cause
This alarm is raised against a 40G OCLD/Wavelength-Selective 40G OCLD,
40G UOCLD, 100G WaveLogic 3 OCLD, Flex2 WaveLogic 3 OCLD, or 100G
OCLD circuit packs when equipment specifications are exceeded. This alarm
indicates that at least one of the measurements, reach or PMD (Polarization
Mode Dispersion) DGD (differential group delay), exceeded the specifications
of the circuit pack. If the client is not connected yet, the severity of the alarm
is NSA since it does not impact client traffic. However, it still can impact line
traffic. Line signal conditioning will be applied if the condition which caused
this alarm to be raised was present during optical signal acquisition (for
example, after connecting fibre, or after card insertion or cold restart
operation). It is possible for this alarm to be raised without impacting traffic, if
traffic was already running prior to the condition being detected. Actions must
be taken to clear this alarm as soon as possible.
You can confirm the presence of signal conditioning in the OTM3 PM or OTM4
PM screen where the OTU-SEFS PM count would be incrementing.
The alarm is latched even if all measurements, reach or PMD (Polarization

Mode Dispersion) DGD (differential group delay), do not exceed the
specifications of the circuit pack and does not get re-evaluated until either a
cold restart of the circuit pack or a line fault condition toggles (for example:
fiber pull and reinsertion).
Impact
Prerequisites
323-1851-545
• obtain a replacement circuit pack suitable for the configuration


Circuit Pack Operational Capability Exceeded
Step Action
in this document.
3 Verify that the circuit pack is connected to the correct optical link using
ODU/OTU TTI. There should be no “ODU/OTU Trace Identifier Mismatch”
alarm.
4 If the circuit pack Then go to
is connected to the correct optical link step 6
is connected to the wrong optical link step 5
5 Break the existing fiber connections and re-connect the circuit pack to the
correct optical link.
If the alarm Then
clears the procedure is complete
does not clear go to step 6
6 Contact your next level of support to find out and order the suitable circuit
pack for the configuration.
8 Replace the circuit pack with a circuit pack suitable for the configuration. You
can replace the 40G OCLD, Wavelength-Selective 40G OCLD, or 100G
OCLD circuit packs in one of the two ways below:
a. Delete the provisioning data (COMM, connection, facility and equipment).
Remove the old circuit pack from the slot. Insert the new circuit pack. The
equipment and facility will auto-provision. You can re-provision the
connection and COMM if necessary.
b. Remove the old circuit pack from the slot. Insert the new circuit pack. Edit
the provisioned PEC to the PEC of the new circuit pack.
Refer to the “Reconfiguration of an optical interface circuit pack” procedure in
Fault Management - Module Replacement, 323-1851-545 for the detailed
procedure.
Provisioned PEC editing is not supported between any of the 40G UOCLD
variants. You have to replace the circuit pack with an identical circuit pack.
support group.
—end—

Procedure 4-38
Circuit Pack Unknown
Alarm ID: 58
Probable cause
This alarm is raised in the following situations:
• when the on-board processor of a circuit pack cannot communicate with
the shelf processor after you insert the circuit pack into the shelf
• when an unknown circuit pack is inserted into an unprovisioned slot
• when a circuit pack is in the wrong slot
• when both the A and B power feeds to the zone powering a circuit pack
have failed “Power Failure A/B” and “Power Failure - Fuse Blown” alarms
have to be cleared first in order to clear this alarm. Refer to the alarm
clearing procedures in part 2 of this document.
• when external equipment connected to an External Slot inventory port on
the access panel is unknown
• when a module equipped in a sub-slot of connected external equipment is
unknown
Attention: A circuit pack in the wrong slot only occurs if the circuit pack
keying is removed. Circuit packs are keyed to fit into specific slots. Do not
remove the circuit pack keying for any reason.
Impact
Prerequisites


Step Action
in this document.
If the circuit pack is Then go to
a newly inserted or manually provisioned step 2
cross-connect circuit pack
not a cross-connect circuit pack step 4
2 Perform a warm restart of the shelf processor. Refer to the “Restarting a

circuit pack or shelf processor” procedure in this document. Do not insert any
circuit packs while the shelf processor is restarting.
5 Ensure that the circuit pack reporting the alarm is supported for the software
release running on the shelf. You can check this against the hardware
baseline report.
If the circuit pack is Then
not supported by the software release the circuit pack cannot be equipped
in the shelf. Remove it. Go to step 6.
supported by the software release go to step 7
6 Wait 30 seconds, and retrieve all alarms.

7 Compare the circuit pack raising the alarm with the supported circuit packs
for each slot on the shelf. Refer to the “6500 interface circuit packs and
modules” table in chapter 3 of in Part 1of 6500 Planning, NTRN10CF.
If the circuit pack raising the alarm is in Then
an unsupported slot go to step 8
a supported slot the circuit pack may be damaged.
Go to step 9.


Step Action
8 Replace the circuit pack raising the alarm with a circuit pack supported in that
slot. Refer to the equipment replacement procedures in chapter 2 of Fault
Management - Module Replacement, 323-1851-545. Select the appropriate
procedure from the “Module replacement procedures list” table.
Go to step 10.
9 Replace the circuit pack with an identical circuit pack. Refer to the equipment
10 Wait 30 seconds and retrieve all alarms.
If the alarm Then
is cleared the procedure is complete. If you replaced a circuit pack in
step 9, the circuit pack you replaced is damaged.
is not cleared contact your next level of support or your Ciena support group
—end—

Procedure 4-39
Alarm ID: 341
Probable cause
This alarm is raised when an unrecognized SFP/SFP+/XFP/CFP/DPO is
installed in an unprovisioned port.
The Circuit Pack Unknown - Pluggable alarm cannot be disabled. Use the
following steps to clear the alarm.
Impact
Prerequisites
323-1851-545
circuit pack (Refer to the “Supported SFP/SFP+/XFP/CFP/DPO modules
NTRN10CF)
Step Action
supported SFP/SFP+/XFP/CFP/DPO. Refer to the “Replacing an
SFP/SFP+/XFP/CFP module” or “Replacing an OC-48/STM-16 DWDM
plug-in optics (DPO) module” procedure in Fault Management - Module


Step Action
support group.
—end—

Procedure 4-40
Circuit Pack Upgrade Failed
Alarm ID: 124
Probable cause
This alarm is raised against a circuit pack when the upgrade process of the
circuit pack fails.
This alarm can also be raised after a shelf processor replacement when the
inserted shelf processor is running a different software release than the active
release on the network element.
Attention: In some cases, a “Circuit Pack Missing” or “Circuit Pack

Unknown” alarm is simultaneously active with a “Circuit Pack Upgrade
Failed” alarm for a particular slot. This condition can be cleared either by
performing a minimal delivery of the corresponding software release, or by
configuring a software release server for the network element. Refer to the
“Transferring a software load to a network element” procedure in chapter 7
of Administration and Security, 323-1851-301.
Impact
Prerequisites
323-1851-545.
Step Action
1 Check the upgrade state of all the circuit packs from Site Manager. Refer to
the “Upgrading a software load” procedure in chapter 8 of Administration and
Security, 323-1851-301. If a circuit pack upgrade has failed, the system
attempts to auto-upgrade it.
Attention: Do not attempt to clear any alarms during the upgrade.


Circuit Pack Upgrade Failed
Step Action

4 If Then go to
the alarm was raised after a shelf step 5
processor replacement
otherwise step 6
5 Refer to the “Replacing the shelf processor” procedure in Fault Management

- Module Replacement, 323-1851-545, to clear this alarm.
Go to step 9.
6 Reseat the circuit pack raising the alarm. Refer to the “Reseating a circuit
pack” procedure in Fault Management - Module Replacement,
323-1851-545. Select the appropriate procedure from the “Module
replacement procedures list” table.
8 Replace the circuit pack. Refer to the equipment replacement procedures in

chapter 2 of Fault Management - Module Replacement, 323-1851-545.
Select the appropriate procedure from the “Module replacement procedures
list” table.
support group.
—end—

Procedure 4-41
Client Service Mismatch
Alarm ID: 350, 369, 696, 830, 869, 1245
Probable cause
This alarm is raised against:
• an Ethernet facility of a 4xGE, 1x10GE EPL, or 24x10/100BT circuit pack
• a WAN facility of a L2SS, PDH gateway, 20G L2SS, L2 MOTR, RPR, 10GE
EPL, 10G OTR, 2x10G OTR, 4x10G PKT I/F, 4x10G OTR, 40G MUX OCI,
8xOTN Flex MOTR, (1+8) OTN FLEX MOTR, eMOTR, 10G OTSC,
10x10GE MUX, 4x10G MUX, 16xOTNFLEX, or 40G MUX OCI circuit pack
• an Ethernet or Fiber Channel facility of a SuperMux circuit pack
• 2x10G XFP, 8xSFP, FLEX MOTR circuit pack.
The alarm is raised when the GFP UPI Tx byte provisioned on the remote
circuit pack does not match the GFP UPI expected Byte on the local circuit
pack. When this alarm is active, traffic from the far end is lost.
The alarm point is identified at the generic framing procedure (GFP) level to
indicate a provisioning mismatch between the near-end and far-end facility
provisioning. For example, one end is configured to preserve the preamble
and the other is configured to discard the preamble. The GFP user payload
identifier (UPI) byte is used for this purpose.
When using 10GE with a mapping of GFPMACOSTR, GFPMACOSTR192, or

GFPMACOSTR64, frames which have a GFP-UPI mismatch will be discarded
by the OTN Mapper and the Client Service Mismatch alarm will be raised. This
applies to both ordered set frames (UPI_O) and data frames (UPI_D).
Impact
Critical, service-affecting (C, SA) alarm if not protected
Minor, non-service-affecting (m, NSA) alarm if protected


Client Service Mismatch
Prerequisites
• have the network connection information (that is, how the optical modules
on each network element connect to other network elements)
323-1851-545
Step Action
1 Trace the cross-connect information to determine the corresponding facility

of the far-end circuit pack.
2 Ensure that the nodal cross-connects are provisioned correctly. Refer to the
“Retrieving path cross-connects” procedure in Part 1 of Configuration -
3 Determine if the client facility provisioned at the corresponding far-end circuit
pack matches the near end. Correct any mismatches. Refer to the “Retrieving
equipment and facility details” and “Editing facility parameters” procedures in
4 Determine if the corresponding far-end Ethernet, Fiber Channel, or WAN
facility parameters match the parameters at the end reporting the Client
Service Mismatch alarm. Correct any mismatches. Refer to the “Retrieving
equipment and facility details” and “Editing facility parameters” procedures in
support group.
—end—

Procedure 4-42
CMF UPI Mismatch
Alarm ID: 1377
Probable cause
This alarm is raised for the WAN facility under the following conditions;
• At least three consecutive GFP layer Client Management Frames (CMF)
UPI received with a value equal to 83/84/85 when the ETH10G WAN
facility Transparent Ordered Sets parameter is G.7041 CMF.
• At least three consecutive GFP layer CMF UPI received with a value equal
to 03/04/05 when the ETH10G WAN facility Transparent Ordered Sets
parameter is Legacy CMF.
When the ETH10G WAN facility Order Sets Transparency parameter is

G.7041 CMF, the CMF UPI values transmitted and expected are as follows for
ordered sets:
• CMF-LF(FDI) = 04
• CMF-RF(RDI) = 05
• CMF-ALL Clear (DCI) = 03
When the ETH10G WAN facility Transparent Ordered Sets parameter is

Legacy CMF, the CMF UPI values transmitted and expected are as follows:
• CMF-LF(FDI) = 83
• CMF-RF(RDI) = 84
• CMF-ALL Clear (DCI) = 85
Note that when this alarm is active, Transparent Ordered Sets cannot be
guaranteed and there is no signal conditioning.
The 10x10G MUX circuit pack (NTK529BBE5) circuit pack support G.7041
compliant CMF and Ordered Set Transparency on 10x10G MUX circuit pack
(NTK529BBE5). This provides compliance to G.7041 Sub-clause 7.9.2.2.
Mapping mode that preserves the Ordered Set information of the 10GBase-R
client signal by mapping Ordered Sets into their own GFP-F frames (Client
Data Frame). This mapping mode does not require the GFP CMF to
communicate local, remote fault, all clear and other PCS layer ordered set
information.
Impact


CMF UPI Mismatch
Prerequisites
Step Action
1 Determine the corresponding far-end client and WAN facility parameters.

Refer to the “Retrieving equipment and facility details” and “Editing facility
Operating, 323-1851-310.
2 Set the ETH10G WAN facility Transparent Ordered Sets parameter to equal
values on both sides. Refer to the “Retrieving equipment and facility details”
and “Editing facility parameters” procedures in Part 1 of Configuration -
support group.
—end—

Procedure 4-43
Cold Restart Required: FPGA Changed
Alarm ID: 646
Probable cause
This alarm is raised when a new functionality is introduced on a circuit pack
that requires FPGA Loads. The circuit pack needs to be restarted to be loaded
with the new feature. Some reasons that can cause this alarm are as follows:
• A circuit pack loses its FPGA load from within the file system, and the
FPGA load maintained on the circuit pack is older than the required load
for this release.
• A SuperMux circuit pack is running an older version of its FPGA load and
you try to use functionality supported only by a newer version of its FPGA
load.
• Upgrading a TCS card running an older PCP FPGA load that supports
less LDCC channels (ex; a 16xOCn 5G card supports 2 LDCC. This card
has the new PCP FPGA load applied in Release 6.0 to support 16 LDCC
channels). The alarm will be cleared when the new FPGA load is applied.
• In 1+1 client TPT, 1+1 port TPT, or 1+1 TPT Protection configurations the
FPGA opportunistic upgrade is not done and the user attempts to
provision 1+1 client TPT, 1+1 port TPT, or 1+1 TPT protection.
If this alarm is raised as part of a network element software upgrade, the 6500
“Software Upgrade Procedures” for this release must be referenced for
instructions.
Impact
Prerequisites


Cold Restart Required: FPGA Changed
Step Action
CAUTION
Performing the following step is traffic affecting.
1 Perform a cold restart on the circuit pack raising the alarm. Refer to the
“Restarting a circuit pack or shelf processor” procedure in this document.
2 If the alarm does not clear following the restart of the circuit pack, contact your
next level of support or your Ciena support group.
—end—

Procedure 4-44
Config Mismatch - LCAS
Alarm ID: 922
Probable cause
This alarm is raised against an LCAS-enabled WAN facility of an L2SS, 20G
L2SS, PDH gateway or SuperMux circuit pack, or circuit pack when the
near-end WAN facility detects that the far-end WAN facility does not have
LCAS enabled.
Impact
Minor, non-service-affecting (m, NSA) alarm, protected
Minor, service-affecting (m, SA) alarm, unprotected
Prerequisites
• have the network connection information (that is, how the optical modules
on each network element connect to other network elements)
Step Action
1 Trace the cross-connect information to determine the corresponding facility of

the far-end circuit pack. This alarm is also raised against the corresponding
facility if the circuit pack at the far end is an L2SS, 20G L2SS, PDH gateway
or SuperMux circuit pack.
2 Ensure the VCAT cross-connects are provisioned correctly. Refer to the
“Retrieving path cross-connects” procedure in Part 1 of Configuration -
3 Ensure the corresponding WAN facility VCAT and LCAS setting at the far end
matches the WAN facility VCAT and LCAS setting at the end reporting the
Config Mismatch alarm. Refer to the “Retrieving equipment and facility
details” procedure in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.


Config Mismatch - LCAS
Step Action
4 If LCAS must be Then

disabled on the WAN disable LCAS on the WAN facility raising the Config
link Mismatch - LCAS alarm
enabled on the WAN enable LCAS on the WAN facility at the far end from
link the facility raising the Config Mismatch - LCAS alarm
To change the LCAS parameter provisioned on the far-end circuit pack to

match the near-end circuit pack, refer to the “Editing facility parameters”
procedures in Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
support group.
—end—

Procedure 4-45
Configuration Mismatch
Alarm ID: 1415
Probable cause
This alarm is raised if the admin weight or bundle id is different on both sides
of a Optical Signaling and Routing Protocol (OSRP) link.
Impact
Attention: Shelf function is not affected by this alarm.
Requirements
Step Action
1 Launch the OSRP Provisioning application and click on Links Tab to

determine if both ends of the OSRP link have the same admin weight and
bundle id assigned.
2 If different, provision the OSRP link to have the same admin weight and
bundle id assigned. Refer to the “Editing an OSRP link” procedure in
Configuration - Control Plane, 323-1851-330.
support group.
—end—

Procedure 4-46
Configuration Mismatch - Adv BW Limit
Alarm ID: 1416
Probable cause
This alarm is raised when there is a configuration mismatch due to advertised
bandwidth (Adv BW) limit being different on adjacent OSRP links.
Impact
Requirements
Step Action
1 Identify the Advertisement BW limit on each side of the link. Refer to the
“Editing an OSRP link” procedure in Configuration - Control Plane,
323-1851-330.
2 Ensure that both ends have the same Advertisement BW limit.
support group.
—end—

Procedure 4-47
Configuration Mismatch - Common ID
Alarm ID: 1411
Probable cause
This alarm is raised when the Common Line ID field of the OSRP line on either
side is different.
Impact
Requirements
Step Action
1 Identify the common id value of the OSRP line at the node raising the alarm.
See the “Editing an OSRP link” procedure in Configuration - Control Plane,
323-1851-330.
2 Verify common id value of the node at the other ends of the OSRP line and
compare it to the values found in step 1.
3 If the common id values on both ends of the OSRP line are not the same,
change the values to be the same. Refer to the “Editing an OSRP link”
procedure in Configuration - Control Plane, 323-1851-330
support group.
—end—

Procedure 4-48
Configuration Mismatch - Concatenation
Alarm ID: 1414
Probable cause
This alarm is raised when there is a concatenation mismatch between the
local and the remote lines while an OSRP line is configured as standard
concatenation at one node and transparent concatenation at the other node.
Impact
Requirements
Step Action
1 Identify the port that raised the alarm. See “Identifying the circuit pack,
pluggable module/port, or facility that has raised an alarm” on page 2-38.
2 The 6500 nodes are configured as standard. Ensure that the remote node is
a 6500. If the remote node is not a 6500 node, ensure that the node is
configured as standard concatenation. Refer to non-6500 documentation for
configuration information.
support group.
—end—

Procedure 4-49
Configuration Mismatch - Link ID
Alarm ID: 1420
Probable cause
This alarm is raised when in a link aggregation one end of the aggregation
contains OSRP lines that are part of a different OSRP link.
Impact
Requirements
Step Action
1 Identify the OSRP lines in a link aggregation on each side of the link. See the
“Adding an OSRP link” procedure in Configuration - Control Plane,
323-1851-330.
2 Ensure all OSRP lines in a link aggregation on each side is part of only one
OSRP link.
support group.
—end—

Procedure 4-50
Configuration Mismatch - Node
Alarm ID: 1421
Probable cause
This alarm is raised when there is a configuration mismatch due to mismatch
in aggregated OSRP line node IDs between adjacent OSRP links. The alarm
raises when in a link aggregation at one end of the aggregation reports OSRP
lines that are part of a different node.
Impact
Requirements
Step Action
1 Identify the OSRP lines in a link aggregation on each side of the link. See the
“Adding an OSRP link” procedure in Configuration - Control Plane,
323-1851-330.
2 Ensure that all OSRP lines in a link aggregation on each side are part of the
same node.
support group.
—end—

Procedure 4-51
Configuration Mismatch - Primary State
Alarm ID: 1410
Probable cause
This alarm is raised when the administrative state of the ends of the
OSRPLINE is mismatched with the remote end.
Impact
Requirements
Step Action
1 Identify the administrative state of the OSRPLINE on each side of the link.
See the “Adding an OSRP link” procedure in Configuration - Control Plane,
323-1851-330.
2 Ensure the administrative state of the OSRPLINE on each side is the same.
support group.
—end—

Procedure 4-52
Corrupt Inventory Data
Alarm ID: 656
Probable cause
The alarm is raised against the cooling unit housing, cooling fan module,
access panel, MIC, Power Input Card, external equipment connected to the
remote inventory ports on the access panel and module in a sub-slot of
connected external equipment which is:
• not recognized by the NE
• not fully inserted
• defective
• connected via a defective cable
Impact
Critical, service-affecting (C, SA) alarm if active on cooling unit housing or fans
(when at least one other fan related alarm is present)
Major, non-service-affecting (M, NSA) alarm if active on fan (when no other
fan related alarm is present) or when raised on external slot inventory
interface of the shelf
Minor, non-service-affecting (m, NSA) alarm if active on access panel, MIC, or
power circuit packs.
Prerequisites
Step Action
DANGER
Risk of eye injury
Wear eye protection such as safety goggles or safety
glasses with side guards when you work with fan
modules or in proximity to the shelf air exhaust.

the cooling unit housing step 2
the cooling unit module (fans) step 12
any other unit step 16


Step Action
3 Remove all fans from the cooling unit housing, one at a time (if present),
starting with any fans that have alarms. Refer to the “Replacing a cooling fan
module” procedure in Fault Management - Module Replacement,
323-1851-545.
Attention: Fans with Corrupt Inventory Data or Fan Incompatible alarms

must be removed from the housing before any other fans are removed.
4 Verify that Fan Failed alarms are raised for each fan, and any existing fan
alarms are cleared.
5 Remove the cooling unit housing from the 6500 shelf. Refer to the “Replacing
the cooling unit assembly” procedure in Fault Management - Module
You cannot remove the cooling unit housing on the Metro front electrical shelf,
as it is an integral part of the shelf.
6 Verify that Corrupt Inventory Data alarm for cooling unit housing has cleared.
7 Replace with new housing. Refer to the “Replacing the cooling unit assembly”
8 Wait 30 seconds to verify that no new Corrupt Inventory Data alarm is raised
against cooling unit housing.
Fan Incompatible alarm is masked for any incompatible fans inserted after a
Corrupt Inventory Data alarm has been raised against the cooling unit
housing. If the cooling unit housing has corrupt inventory data upon system
bootup or replacement, any incompatible fans in the housing will not have
their incompatibility alarmed.
9 Reinsert fan 1. Verify that Fan Failed alarm has cleared. Wait at least 15
seconds before proceeding.
10 Repeat step 9 for fan 2 and 3.
Fans must be inserted one at a time, with at least 15 seconds of waiting time
between fan insertions. Verify that all Fan Failed alarms clear.
11 If the Then
original alarm has cleared the procedure is complete
alarm is raised against the fan go to step 12
module
Fan Incompatible alarm is raised perform the alarm clearing procedure for


Step Action
12 Remove alarmed fan from cooling unit housing.

The Fan Failed alarm is raised for the removed fan and the Corrupt Inventory
Data alarm for that fan clears.
13 Wait at least 15 seconds. Insert a new fan into the slot. Ensure that the fan is
fully inserted and the bolt is attached to the fan housing.
14 Verify that Fan Failed alarm has cleared and that no new alarm is raised.
15 If the Then
original alarm has cleared the procedure is complete
Fan Incompatible alarm is raised perform the alarm clearing procedure for
16 Verify that the alarmed unit is fully inserted.

17 Verify that the cable between the shelf External Slot Inventory port and the
external peripheral is connected and not damaged.
18 If applicable, perform a restart of the alarmed unit, Refer to the “Restarting a
circuit pack or shelf processor” procedure in this document.
If a restart is not possible on the unit, go to step 20.
20 Reseat the alarmed unit, or disconnect and reconnect the cable connecting
the alarmed module (the cable between the shelf External Slot Inventory port
and the external peripheral). Refer to the “Reseating a circuit pack” procedure
in Fault Management - Module Replacement, 323-1851-545.
22 Replace the alarmed unit. Refer to the equipment replacement procedures in

The Circuit Pack Missing alarm is raised for that unit and the Corrupt
Inventory Data for that unit clears.
support group.
—end—

Procedure 4-53
Alarm ID: 702, 905
Probable cause
This alarm is raised when the Ethernet First Mile (EFM) discovery protocol (a
discovery mechanism that allows the exchange/negotiation of protocol
operational parameters) fails to execute successfully.
This alarm will be raised on a SuperMux ETH facility if EFM is enabled and no
cross-connections are provisioned on that facility.
Note that EFM on SuperMux and L2 MOTR supports interworking with

OME1110 only.
For more information about OME1110, refer to OME1110 Deployment Guide,

323-1851-250. The OME1110 Deployment Guide is included in the 6500
technical publication libraries from Release 7.0 to Release 9.1.
For more information on interworking, see the Network Interworking Guide,

NTCA68CA.
Impact
Critical, service-affecting (C, SA) alarm if active
Minor, non-service-affecting (m, NSA) alarm if inactive (6500 GE circuit pack
only)
Prerequisites
Replacement, 323-1851-545,
Step Action
1 If the 6500 GE or FE facility Then go to

is connected to a port on an OME1000 CPE module step 2
is not connected to a port on an OME1000 CPE module step 8
2 For a SuperMux ETH facility, verify that there is at least one cross-connection
provisioned.
3 Verify that the OME1000 line side is connected to a GE or FE circuit pack and
only one of the ports on the line side is connected. Also verify that the
subtending equipment is connected to the OME1000 client side.


Step Action
4 Ensure the Control Frame Profile is set properly. Refer to tables in chapter 1
of the Part 1 of Configuration - Provisioning and Operating, 323-1851-310 for
the correct EFM values (there are multiple possibilities depending on
configuration).
7 Replace with an OME1000 CPE module. Refer to the latest OME1000
Installation and User Guide, NTK972xx.
8 Ensure the Control Frame Profile is set to 4: P2P Tunnel. This alarm will only
be present if an EFM CFPRF is provisioned, once the profile is changed to 4
the alarm should clear.
support group.
—end—

Procedure 4-54
CP Loss of Host Timing Ref.
Alarm ID: 17
Probable cause
This alarm is raised when the frequency gap between the reference source
from the OC-3 host and the DSM 84xDS1 termination module (TM) internal
source is too large. A timing reference is considered invalid if the absolute
frequency offset from the internal DSM 84xDS1 TM clock is greater than
-230/+205 ppm.
This alarm does not result in circuit pack conviction, and clears when the
conditions that caused the alarm change.
Impact
Critical, service-affecting (C, SA) alarm if active
Major, non-service-affecting (M, NSA) alarm if inactive
Prerequisites
Step Action
in this document.
2 Look for any other alarms in the active alarm list that are against the DSM
84xDS1 TM. Use the appropriate alarm clearing procedure to clear the alarm.
3 Verify the timing reference is correct. Refer to the “Retrieving synchronization
data for a network element” procedure in Part 2 of Configuration -
5 If the alarm does not clear, replace the DSM 84xDS1 TM. Refer to the
“Replacing the DSM 84xDS1 TM circuit pack” procedure in Fault
support group.
—end—

Procedure 4-55
CPU2 Unreachable
Alarm ID: 1157
Probable cause
This alarm is raised when the secondary processor on SP-2 is not reachable
from the primary processor. This alarm applies to SP-2 Dual CPU circuit pack.
You must refer to 6500 Packet-Optical Platform Control Plane Application

Guide (NTRN71AA), for detailed information on Control Plane concepts,
applications, and engineering rules supported in this release of 6500.
Attention: This alarm is a diagnostics alarm to indicate the link is down, in

most cases the alarm is raised during CPU2 restart and will clear once CPU2
is back in service.
Impact
Major, non-service-affecting (M, NSA) alarm (for the Control Plane, when the
CPU2 is warm restarted with Control Plane provisioned, this alarm is raised
as NSA)
Prerequisites
323-1851-545
Step Action
1 Restart the shelf processor. Wait five minutes for it to restart. Refer to the
support group.
—end—

Procedure 4-56
CPU2 Warm Restart Required
Alarm ID: 1425
Probable cause
This alarm is raised when a SP-2 Dual CPU Processor (CPU2) warm restart
is required after a SONET/SDH ORSP instance is added or deleted.
Impact
Requirements
Before you perform this procedure, you must use an account with level 3 or
higher UPC.
Step Action
1 Perform a warm restart of the CPU2 of the active SP-2 Dual CPU. See
Procedure 2-11, Restarting a circuit pack or shelf processor on page 2-29.
2 If the alarm does not clear following the restart of the shelf processor, contact
your next level of support or your Ciena support group.
—end—

Procedure 4-57
Craft Load Missing
Alarm ID: 627
Probable cause
This alarm is raised when the shelf processor does not contain a craft (that is,
NE Java Webstart SiteManager) load. The craft load is loaded when the shelf
processor is upgraded.
Impact
Prerequisites
Step Action
1 Deliver the software load to the network element. Refer to the “Transferring a
software load to a network element” procedure in chapter 7 of Administration
support group.
—end—

Procedure 4-58
Craft Load Unpacking Aborted - Low Disk Space
Alarm ID: 1156
Probable cause
This alarm is raised when the SP is running low in disk space, such that NE
Java Webstart SiteManager cannot be installed in the NE.
Impact
Prerequisites
Step Action
1 Free disk space by deleting unused release in the NE with DLT-RELEASE.

Refer to the “Deleting a software load” procedure in chapter 7 of
When there is sufficient free disk space after DLT-RELEASE, the NE Java
Webstart SiteManager will be installed automatically. After installation, the
alarm will be clear.
support group.
—end—

Procedure 4-59
Cross-connection Mismatch
Alarm ID: 863
Probable cause
This alarm is raised against the shelf when:
• one or more optical cross-connections recorded in the Optical Bandwidth
Manager (OBM) database are mismatched with the existing configuration
in the Shelf Wavelength Topology (SWT) database.
• There are SWT instances that have no corresponding photonic
cross-connections.
• A passthrough channel is provisioned at a TOADM, but a CMD for that
same group is provisioned, or the inter-OTS adjacencies are missing or
they are incorrectly provisioned
For Direction Independent Access (DIA), OBM audit raises this alarm if it
detects an OCH with routing OBM_DI_ADD or OBM_DI_DROP and the
corresponding Tx/Rx adjacency is OOS.
Impact
Prerequisites
Step Action
1 Using the Photonic Connections application in Site Manager, retrieve the

Photonic cross-connects with an OCH rate for the affected shelf. From the
Mismatch column, note the wavelength and the direction of the connection(s)
with a mismatch value other than “NONE”. Refer to the “Retrieving Photonic
Services, 323-1851-320.
2 If you can, switch traffic away from the link with the mismatch.
3 If the mismatch value identified in step 1 is Then go to
TO step 4
FROM step 6
BOTH step 8
4 Sort the data in the Photonic cross-connect list from step 1 by the To column.
Find and record all the cross-connects that share the same value in the To
column.


Step Action
5 Only one cross-connection is permitted to use a given To value. Correct the

provisioning error(s) so that only a single cross-connect exists for the
duplicated To value. This may require:
• deleting a cross-connect. Refer to the “Deleting Photonic cross-connects”
procedure in Part 1 of Configuration - Bandwidth and Data Services,
323-1851-320.
• placing an ADJ-RX facility OOS (provision the CMD44 ADJ-RX Receiver
type to UNKNOWN) to delete a channel for which a derived pass-through
cross-connect was created. Refer to the “Editing facility parameters”
323-1851-310. Following the channel deletion, verify the channel no
longer appears in channel listing of the Domain Optical Controller
(DOC) application in Site Manager. Refer to the “Retrieving Domain
Optical Controller summary and details view” procedure in Part 2 of
• placing an ADJ-TX facility OOS (provision the CMD44 ADJ-TX
Transmitter type to UNKNOWN) to delete a channel for which a derived
pass-through cross-connect was created. Refer to the “Editing facility
Operating, 323-1851-310. Following the channel deletion, verify the
channel no longer appears in channel listing of the Domain Optical
Controller (DOC) application in Site Manager. Refer to the “Retrieving
Domain Optical Controller summary and details view” procedure in Part 2
of Configuration - Provisioning and Operating, 323-1851-310.
Go to step 10.
6 Sort the data in the Photonic cross-connect list from step 1 by the From
column. Find and record all the cross-connects that share the same value in
the From column.


Step Action
7 The following rules apply to the cross-connects that share a given From
value:
• a maximum of one local drop cross-connection is allowed.
• a maximum of one non-broadcast pass-through cross-connection is
allowed.
Correct the provisioning error(s) so that the cross-connections sharing the
same From value comply with the above rules. This may require:
• deleting a cross-connect. Refer to the “Deleting Photonic cross-connects”
323-1851-320.
• placing an ADJ-RX facility OOS (provision the CMD44 ADJ-RX Receiver
type to UNKNOWN) to delete a channel for which a derived pass-through
cross-connect was created. Refer to the “Editing facility parameters”
323-1851-310. Following the channel deletion, verify the channel no
longer appears in channel listing of the Domain Optical Controller
(DOC) application in Site Manager. Refer to the “Retrieving Domain
Optical Controller summary and details view” procedure in Part 2 of
• placing an ADJ-TX facility OOS (provision the CMD44 ADJ-TX
Transmitter type to UNKNOWN) to delete a channel for which a derived
pass-through cross-connect was created. Refer to the “Editing facility
Operating, 323-1851-310. Following the channel deletion, verify the
channel no longer appears in channel listing of the Domain Optical
Controller (DOC) application in Site Manager. Refer to the “Retrieving
Domain Optical Controller summary and details view” procedure in Part 2
of Configuration - Provisioning and Operating, 323-1851-310.
Go to step 10.
8 Follow step 4 and step 6 to resolve the mismatches (of the To and From
values) identified in step 1.
9 If the original alarm has Then go to
cleared step 10
not cleared step 13
10 Wait 15 minutes for the next Optical Bandwidth Manager (OBM) audit to run.
11 Using the Photonic Connections application in Site Manager, retrieve the
Photonic cross-connects and verify the mismatch is resolved.
12 Switch traffic back to the link (if you have removed it in step 2).
You have completed this procedure.


Step Action
13 Select Configuration->Photonic Services->Shelf Wavelength Topology and

retrieve the SWT instances from all the shelves in the node.
14 Select Configuration->Cross Connections->Photonic Connections and
retrieve the cross-connection information in the node.
15 Determine which SWT instances have missing cross-connections:
• Each SWT instance of routing Drop must have a corresponding derived
cross-connection.
• Each SWT instance of routing Add must have a corresponding derived
cross-connection.
• Two SWT instances of routing Passthrough must have a corresponding
cross-connection, one SWT instance for the “From OCH” portion of the
cross-connection, and one SWT instance for the “To OCH” portion of the
cross-connection.
16 Select your next step for SWT instances that are missing a cross-connection.
If this is Then
a ROADM site perform the same steps as when a cross-connection
has a Mismatch value of From and/or To, that is, step 2
to step 12.
a TOADM see “Adjacency Provisioning Error” on page 4-33 for
the steps required to clear the alarm.
support group.
—end—

Procedure 4-60
Cross connect Error
Alarm ID: 1207
Probable cause
This alarm is raised against a Maintenance Association (MA) entity when a
Maintenance End Point (MEP) receives at least one Continuity Check
Message (CCM) encoded with a different Maintenance Association ID (MAID)
(than its own) or receives a CCM with a lower Maintenance Domain (MD) level
(than its own).
This alarm typically indicates a configuration error in the network.
Impact
Prerequisites
Step Action
1 Verify the MEPs on both nodes (local MEP and the remote MEP) belong to
the same MD/MA pair. That is, the MD name and the short MA name are
identical. Refer to the “Data services Ethernet OAM provisioning” chapter in
Part 3 of Configuration - Bandwidth and Data Services, 323-1851-320.
2 Verify the associated MD's are configured against the same MD level.
Attention: If there are multiple RMEPs, use the "RTRV-MEP-DEFECTS2"

TL1 command (or) the 'Defects' tab in Ethernet OAM provisioning window in
Site Manager to isolate the alarm condition against a specific RMEP.
support group.
—end—

Procedure 4-61
Crossed Fibers Suspected
Alarm ID: 1508
Probable cause
This alarm is raised against OPM ports when the received power by the far
end is higher than the transmitting end due to a crossed fiber.
Crossed OPM fiber is only detectable when there is a delta of at least 3dB in
the expected powers at the OPM ports. One port will have higher than
expected power, the other port will have lower than expected power. The port
with the higher than expected power (more than 3dB) will raise the “Crossed
Fibers Suspected” alarm. The port with lower than expected power will raise
the “High Fiber loss” alarm if Fiber Loss Detection is enabled.
Impact
Prerequisites
To perform this procedure
• you require an account with at least a level 3 UPC.
323-1851-545
Step Action
1 Verify the adjacency of the OPM ports and the system diagrams of the shelf.
2 Trace the fiber from the OPM port to the associated monitor port on the LIM.
3 Ensure the fibering is exactly the same as the adjacencies.
4 If the fibers are crossed, uncross them.
support group.
—end—

Procedure 4-62
Database Auto Save in Progress
Alarm ID: 1047
Probable cause
This alarm is raised when an automatic database backup is initiated.
Impact
Step Action
1 No action is required. The alarm clears when the database backup is

completed.
support group.
—end—

Procedure 4-63
Database Integrity Fail
Alarm ID: 8
Probable cause
This alarm is raised when there is a possibility that provisioning data on the
shelf processor is in a corrupted state.
Impact
Step Action

—end—

Procedure 4-64
Database Integrity Fail - CPU2
Alarm ID: 1241
Probable cause
This alarm is raised when the provisioning data on the CPU2 is corrupted and
the database cache integrity has failed. The alarm is also raised when you
restore from backup and then commit fails.
Impact
Step Action

—end—

Procedure 4-65
Database Not Recovered For Slot
Alarm ID: 1390
Probable cause
This alarm is raised if provisioning data for a provisioned circuit pack is not
recovered over a system or shelf processor power-up/restart. The alarm
indicates the slot for which data corruption is detected.
The alarm clears when the provisioning data is corrected or a data restore is
performed as a result of clearing related higher severity alarms.
Impact
Step Action
1 No action is required. The alarm clears as a result of clearing higher severity

alarm “Database Recovery Incomplete”, that is associated with provisioning
data. Refer to the “Database Recovery Incomplete” procedure in this
document.
support group.
—end—

Procedure 4-66
Database Recovery Incomplete
Alarm ID: 205
Probable cause
This alarm is raised when the shelf processor is replaced and there is a
missing, mismatched or failed circuit pack in the shelf. The alarm is the result
of a data consistency audit depending on whether any equipment data was
not recovered.
The DSM site address, PM, and alarm profiles will be lost if the host OC-3
circuit pack to the DSM 84xDS1 termination module is missing or in a failed
state when you replace the shelf processor.
The data consistency audit detects problems when a shelf processor is

replaced and a transport circuit pack is not able to send its data to the shelf
processor. The audit runs on every restart to ensure the integrity of data such
as connections, synchronization, and protection.
For each slot, the audit compares provisioned equipment known to the shelf
processor to that recovered from the cards. If there is a mismatch in the
comparison, this alarm is raised and the no data will be sent to the cards.
Database save operations will also be blocked.
The data consistency audit requires at least one XC circuit pack, and does not
run if it detects that it was run and previously found problems.
Attention: Do not remove or insert any circuit packs during this procedure.
Impact
The data transfer to the transport circuit pack is blocked until the data
consistency audit is successfully completed.


Database Recovery Incomplete
Prerequisites
Step Action
1 Retrieve the current events and alarms. Refer to the “Viewing events” section
in chapter 1 of this document.
Attention: If there is a Software Upgrade In Progress alarm, complete the

upgrade before continuing this procedure.
2 From the list of alarms find the “Database Not Recovered For Slot” alarm. The
“Database Not Recovered For Slot” alarm is raised against the slot for which
data is missing.
3 Complete a database restore. Refer to the backup and restore procedures in
chapter 6 of Administration and Security, 323-1851-301 for more information.
support group.
—end—

Procedure 4-67
Database Restore in Progress
Alarm ID: 143
Probable cause
This alarm is raised when the shelf processor detects that the circuit pack is
restoring its provisioning files from a remote source.
Impact
Prerequisites
• be able to connect to the shelf processor
Step Action
1 Wait until the database successfully restores the provisioning data. Refer to
the “Restoring provisioning data” procedure in chapter 6 of Administration
To abort the database restore, click Cancel in the Backup and Restore
application. Canceling stops the action and cleans up any backup files left in
invalid states.
support group.
—end—

Procedure 4-68
Database Save and Restore Failed
Alarm ID: 144
Probable cause
This alarm is raised when the shelf processor detects that a save, restore, or
commit command sent to the shelf processor fails.
Impact
Prerequisites
Step Action
Perform either step 1 or step 2.

1 Click Cancel in the Backup and Restore application. Refer to the “Restoring
provisioning data” procedure in chapter 6 of Administration and Security,
323-1851-301 for more information.
Canceling cleans up any backup files left in invalid states.
2 This alarm can also clear if you try to backup or restore the provisioning data
again. The alarm clears if the backup or restore action is successful. Refer to
and Security, 323-1851-301 for more information.


Step Action
3 If the alarm does not clear, verify that the URL parameters are correct. Refer
to the “URL Formats” section in chapter 6 of Administration and Security,
323-1851-301 for more information. Check the network element to determine
whether a condition exists that can prevent a save or restore. These
conditions include:
• a software upgrade is in progress
• a database save and restore is already in progress
• a Software Mismatch alarm is active
• the software version on the shelf processor is different from the other
circuit packs
• a “Disk Full” alarm is active
• a corruption in the network element database is detected (indicated by a
Transport Data Recovery Failed, a Database Recovery Incomplete, or a
Switch Shelf ID Mismatch detected alarm)
• active alarms are present unless you specify the backup to ignore active
alarms
• the NE mode is ‘Unknown’
Checklist for Database Save and Restore specific failure (these failures are
popped up in Site Manager when a database save or restored is failed).
Invalid source
• Check the database filename prefix. If the file identifier is used in the
database filename then user must use the Use filename starting with
checkbox option to match with the database filename prefix.
• Check the shelf number in the database filename prefix. If it does not
match with the NE shelf number then user must use the Use filename
with shelf number checkbox option to match with the database shelf
number prefix.
Backup not from this node
• This failure indicates the node name saved in the database and the NE
node name don’t match. This is because either the database was saved
in the different shelf or the current NE node name had been changed after
the database save. You can specify the restore to ignore the node name
check by unchecking the “Do not restore if data was not backed up from
this NE” checkbox.


Step Action
FTP/SFTP access denied, Failure transferring file, Invalid destination, Could

not connect to destination, Could not connect to source
• Ensure the IP address, directory path, userid and password are valid for
the remote host
• Ensure that the remote host has adequate disk space and the correct
attributes (permissions) are set for writing to the remote directory.
• Ensure there are no issues with FTP server on the remote host.
Mismatched Software Releases
• Ensure the database software release is not different from the NE
software release.
Incompatible S/R options
• If the database was saved with the communication setting option by
checking the “Do not restore if data was not backed up from this NE”
check box. Ensure this checkbox is checked on the restore.
• If the database was saved without checking the “Do not restore if data
was not backed up from this NE” check box. Ensure this checkbox is not
checked on the restore.
support group.
—end—

Procedure 4-69
Alarm ID: 1265
Probable cause
This alarm is raised when the shelf processor detects that a Commit
command sent to the shelf processor fails.
Impact
Prerequisites
Step Action
1 Select your next step.

If you want to Then go to
clear the alarm by canceling the action step 2
clear the alarm and retry the action step 3
2 Click Cancel in the Backup and Restore application. Refer to the “Restoring
provisioning data” procedure in chapter 6 of Administration and Security,
323-1851-301 for more information.
Canceling cleans up any backup files left in invalid states.
3 This alarm can also clear if you try to backup or restore the provisioning data
again. The alarm clears if the backup or restore action is successful. Refer to
and Security, 323-1851-301 for more information.


Step Action
4 If the alarm does not clear, check the network element to determine whether
a condition exists that can prevent a commit. These conditions include:
• a “Software Upgrade in Progress” alarm is active
• a database save is already in progress
• a “Software Mismatch” alarm is active
• the software version on the shelf processor is different from the other
circuit packs
• a “Disk Full” alarm is active
• a corruption in the network element database is detected (indicated by a
Transport Data Recovery Failed, a Database Recovery Incomplete, or a
Switch Shelf ID Mismatch detected alarm)
• active alarms are present unless you specify the backup to ignore active
alarms
• the NE mode is “Unknown”
support group.
—end—

Procedure 4-70
Database Save in Progress
Alarm ID: 147
Probable cause
This alarm is raised while a database save is in progress and clears when the
save is completed or has failed.
Impact
Step Action
1 No action is required. The alarm clears when database save is completed or

failed.
—end—

Procedure 4-71
DCC Link Fail alarms
Use this procedure to clear alarms associated with the Data Communications
Channel (DCC) link failures.
Line DCC Link Failure

MS DCC Link Failure
Alarm ID: 449, 450, 451, 452, 1105,1528, 1695
Probable cause
These alarms are raised when one of the following conditions occurs:
• The shelf processor cannot communicate with the devices at the far end
of an SONET/SDH link through the LDCC/MS DCC (bytes D4-D12 of the
line/multiplex section overhead).
• Overhead communications across an SONET/SDH link are down.
Remote login sessions are dropped. This condition does not affect traffic.
• The protection and working optical fibers/cables on a 1+1/MSP linear, 1+1
port TPT, or 1+1 TPT configuration protected optical interface link are
reversed (working optical interface on network element 1 to protection
optical interface on network element 2).
• LDCC/MS DCC has not been enabled at the far-end network element.
• There are missing OSPF circuits.
• Fiber-optic cables may be disconnected.
• Incorrectly provisioned manual area addresses.
• Provisioning mismatch between near and far-end network elements.
Impact
Section DCC Link Failure

RS DCC Link Failure
Alarm ID: 19, 123, 130, 245, 286, 1104, 1687
Probable cause
These alarms are raised when one of the following conditions occurs:
• The shelf processor cannot communicate with the devices at the far end
of an SONET/SDH link through the SDCC/RS DCC (bytes D1-D3 of the
section/regenerator section overhead).
• Overhead communications across an SONET/SDH link are down.
Remote login sessions are dropped. This condition does not affect traffic.


• The protection and working optical fibers/cables on a 1+1/MSP linear, 1+1

port TPT, or 1+1 TPT configuration protected optical interface link are
reversed (working optical interface on network element 1 to protection
optical interface on network element 2).
• SDCC/RS DCC has not been enabled on the corresponding facility at the
far-end network element.
• Fiber-optic cables may be disconnected.
• Incorrectly provisioned manual area addresses.
Impact
Prerequisites
323-1851-545
• if the DCC link failure alarms are not present at the far-end, clear all
remote alarms present against the optical fiber
Step Action
1 Ensure there are no other alarms that would impact DCC against this facility
(such as LOS, Circuit Pack Missing, Circuit Pack Failed, etc.)
2 Identify the facility raising the alarm. Refer to the “Identifying the circuit pack,
pluggable module/port, or facility that has raised an alarm” procedure in this
document.
If the alarm is Then go
toggling step 3
constant step 6


Step Action
3 The problem is due to incorrectly provisioned manual area addresses (invalid

or incorrectly enter data). Provision the correct manual area addresses. Refer
to the “Adding a new entry in the communications settings” and “Deleting an
entry in the communications settings” procedures in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310 for details. You may require a
LAN connection to the network element.
If the alarm does not stop toggling, contact your next level of support or your
Ciena support group.
4 Check if there are any related alarms on the facility with the DCC alarm. Clear
any related alarms on the facility with the DCC alarm using the appropriate
procedures.
6 Use the optical fiber connection information to identify the network element
and the circuit pack that is the source of the signal reporting the alarm.
Check if there are any related alarms on the source facility with the DCC
alarm. Clear any related alarms on the facility with the DCC alarm using the
appropriate procedures.
7 Ensure that the alarm has been raised for more than five minutes, in case a
shelf processor or interface circuit pack restart at the remote terminal caused
the alarm.
8 Verify whether the alarm is present on both ends of the link. If not, verify the
alarms and provisioning on the node that does not have the alarm.
9 Verify that both network elements have the same protection scheme. Refer to
the “Retrieving protection parameters” procedure in Part 2 of Configuration -
a. If the facility protection group is provisioned the same for both network
elements and the alarm continues, go to step 11.
b. If the facility protection group is provisioned differently at the two network
elements, one of the network elements is not correctly configured. Verify
from your company record and repair the incorrectly provisioned
protection scheme.


Step Action
11 Verify that all lower layer DCC parameters provisioned at both network
elements match. Refer to the “Retrieving communications settings” in Part 1
of Configuration - Provisioning and Operating, 323-1851-310, for information
about lower layer DCC parameters.
a. Retrieve lower layer DCC at the local and remote network elements.
Refer to the “Retrieving communications settings” procedure in Part 1 of
b. Record settings of all lower layer DCC parameters.
c. Compare all lower layer DCC parameter settings. Ensure all parameters
provisioned at both network elements match. Repair any incorrectly
provisioned parameters. Refer to the “Editing the communications
settings” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
13 Verify that there are no missing OSPF circuits.

a. Retrieve the OSPF circuits at the local and remote network elements.
b. Verify against company records if any circuits are missing. Provision any
missing circuits. Refer to the “Adding a new entry in the communications
settings” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.


Step Action
14 Verify the optical fibers/cables on the network element. For a 1+1/MSP linear,
1+1 port TPT, or 1+1 TPT configuration protected optical interface:
• the odd slot transmit must connect to the odd slot receive on the far-end
network element
• the even slot transmit must connect to the even slot receive on the far-end
network element
• reconnect any faulty connections
CAUTION
Swapping fibers can cause loss of traffic. Before
swapping fibers use section trace to confirm that fibers
have been already swapped. Swapping fibers should
be done after all provisioning have been verified.
For information on the optical fibering of a 2-Fiber/4-Fiber

BLSR/MS-SPRing/HERS protected optical interface, refer to the “Retrieving
BLSR/MS-SPRing/HERS configuration information” procedure in Part 1 of
Configuration - Bandwidth and Data Services, 323-1851-320.
17 If the alarm does not clear, log into the remote network element using the
external IP address.
• If the login is successful, go to step 18.
• If the login fails, see Note, then contact your next level of support or your
Note: If the remote network element is only accessible through DCC, the
login may not be possible, as the DCC has failed. If this is the case, go to
step 18.
18 Restart the shelf processor. Wait five minutes for it to restart. Refer to the


Step Action
20 Reseat the shelf processor at the site that originally reported the alarm. Refer
to the “Reseating a circuit pack” procedure in Fault Management - Module
Replacement, 323-1851-545. Wait five minutes for the shelf processor to
restart.
22 Restart and reseat the shelf processor at the remote site you determined in
step 6 if this was not already done in step 17.
24 Restart and reseat the required circuit pack at the remote site determined in
step 6.
26 Replace the required circuit pack at the network element originally reporting
the alarm. Refer to the equipment replacement procedures in Fault
support group.
—end—

Procedure 4-72
Debug Port in Use
Alarm ID: 1132
Probable cause
This alarm is raised when a user with UPC 4 or greater logs in to the debug
port.
The “Debug Port In Use” alarm is disabled by default and can be enabled
using the Site Manager Configuration->Alarms & Controls->Alarm Profiles
application.
The alarm severity can also be provisioned.
Impact
Step Action
1 No action is required. The alarm clears when there is no more debug login
left.
support group.
—end—

Procedure 4-73
Delay Measurement Enabled on Slave Node (6500)
Alarm ID: 1418
Probable cause
This alarm is raised when latency discovery is enabled on an OSRP slave
node.
Impact
Step Action
1 Disable latency discovery on slave node. Refer to the “Editing an OSRP link”
procedure in Configuration - Control Plane, 323-1851-330. If the alarm does
not clear, contact your next level of support or your Ciena support group.
—end—

Procedure 4-74
Delay Measurement Failed (6500)
Alarm ID: 1419
Probable cause
This alarm is raised when latency measurements have failed.
Impact
Step Action

—end—

Procedure 4-75
Delay Measurement Mismatch Capability (6500)
Alarm ID: 1417
Probable cause
This alarm is raised when a link is up between master node and the slave
node and the user enables latency discovery on master node on that link.
Then the master OSRP node will be capable of delay measurements while the
salve node is not capable of performing delay announcements.
Impact
Step Action
1 Disable latency discovery flag on master node. Refer to the “Editing an OSRP
link” procedure in Configuration - Control Plane, 323-1851-330.
support group.
—end—

Procedure 4-76
Disk Full alarms
Use this procedure to clear alarms associated with the shelf processor disk
capacity.
Disk 75 percent Full

Alarm ID: 374
Probable cause
This alarm is raised when the disk is 75% full on the shelf processor, and
clears when there is at least 30% free space.
As of release 6.0, the “Disk 75 percent full” alarm is not supported on SP-1.
SP-2 or SPAP2 w/2xOSC will raise this alarm due to lack of file space. This
alarm is enabled by default.
For the 2-slot shelf, this alarm is disabled by default since there is no SP-2.
The alarm needs to be enabled manually.
The Disk 75 percent Full alarm is for information only and does not affect the
operation of the shelf. It is recommended that you attempt to clear this alarm
to prevent possible future problems if the disk becomes too full.
Impact
Disk 90 percent Full

Alarm ID: 375
Probable cause
This alarm is raised when the disk is 90% full on the shelf processor, and
clears when there is at least 15% free space.
As of release 6.0, the “Disk 90 percent full” alarm is not supported on SP-1.
SP-2 or SPAP2 w/2xOSC will raise this alarm due to lack of file space. This
alarm is enabled by default.
For the 2-slot shelf, this alarm is disabled by default since there is no SP-2.
The alarm needs to be enabled manually.
The Disk 90 percent Full alarm is for information only and does not affect the
operation on the shelf. It is recommended that you attempt to clear this alarm
to prevent possible future problems if the disk becomes too full.
Impact


Disk Full alarms
Disk Full
Alarm ID: 146
Probable cause
This alarm is raised when the disk is full on the shelf processor.
Impact
Attention: Any time a Disk Full condition is reached, some applications or

operations are blocked. For example, system blocks upgrades, circuit pack
provisioning, and initializations.
Prerequisites
Step Action
1 Delete any loads that you do not require on the disk. Refer to the “Deleting a
software load” in Administration and Security, 323-1851-301.
support group.
—end—

Procedure 4-77
DOC Action: Channel Add In Progress
Alarm ID: 875
Probable cause
This alarm is raised by DOC as soon as the Add channel command enters the
EXECUTING state. This alarm is only active at the DOC site where the Add
command is executing.
This alarm provides a warning to users who want to perform system

maintenance or provisioning.
Impact
Prerequisites
Step Action
1 No action is required. Wait for the DOC add to complete (successfully,

unsuccessfully, or by the Stop DOC Action command). DOC will then clear
the alarm.
support group.
—end—

Procedure 4-78
DOC Action: Channel Delete In Progress
Alarm ID: 876
Probable cause
This alarm is raised by the DOC as soon as the Delete or Forced Delete
command enters the EXECUTING state. The EXECUTING state begins after
the “Delete: Waiting” state. This alarm is only active at the DOC site where the
Delete or Forced Delete command is executing.
This alarm provides a warning to users who want to perform system

maintenance or provisioning.
Impact
Prerequisites
Step Action
1 No action is required. Wait for DOC delete to complete (successfully,

unsuccessfully, or by the Stop DOC Action command). DOC will then clear
the alarm.
support group.
—end—

Procedure 4-79
DOC Action Failed: Add
Alarm ID: 576
Probable cause
This alarm is raised when an Channel Add command (automatic or manual)
in DOC is requested and fails. Conditions that can cause this failure include:
• maintenance activities, such as module replacement, module restart, and
fiber cut, occurred during the Channel Add command
• an internal communications issue (for example, ILAN is not cabled)
• a provisioning error on the Rx or Tx adjacency
• an associated adjacency or AMP facility is deleted
• the DOC Action: Channel Add was stopped before the addition was
completed
This alarm appears only on the affected DOC shelf.
This alarm is cleared if the Clear DOC Alarms button is clicked in the DOC
application. However, this will not clear the underlying problem.
Attention: It is recommended that DOC be placed OOS before inserting a

standby shelf processor (SP). If it is not, and the DOC is set to automatically
add channels or you manually add a channel during the standby SP
insertion, the DOC Action Failed: Add alarm can be raised after the insertion.
In this case, the alarm will clear in approximately five minutes. For details on
adding channels, refer to the “Adding optical channels” procedure in
Commissioning and Testing, 323-1851-221.
Impact
Prerequisites
• have the engineering documentation package (EDP) containing
provisioning details


Step Action
1 If maintenance activities, such as module replacement, module restart, or

fiber cut, occurred during the Add channel operation, then this alarm will be
active. Ensure that the maintenance activities have completed.
2 Check for and clear any active DOC Invalid Photonic Domain alarm using the
3 Check for and clear any of the following alarms on all of the network elements
that are active within the DOC span of control:
• Adjacency Provisioning Error
• Circuit Pack Failed
• Circuit Pack Mismatch
• Circuit Pack Missing
• Circuit Pack Unknown
• Gauge Threshold Crossing Alert Summary
• OSC Loss of Signal
Attention: If the Optical Line Fail alarm is active, clear this alarm first.
4 Clear all other active alarms on the network elements within the DOC span of
control. For optimal DOC operation, the system must be alarm free.
Use the DOC Logs window to view the DOC logs to determine if another
network element reported an error. Review the DOC logs from the other
network element. Refer to the “Displaying the DOC logs for the summary
table” procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310.


Step Action
5 Delete the channels that were unsuccessfully added under DOC control.
Refer to the “Deleting optical channels” procedures in Commissioning and
Testing, 323-1851-221.
If the delete operation fails, perform a Force Delete operation
(service-affecting action).
Note: You must successfully delete the channels that were
unsuccessfully added under DOC control before re-attempting to add
them.
6 Verify, and if necessary, correct the following provisioned data (reference the
EDP):
• Tx and Rx adjacency parameters (Adjacency type and all power-related
parameters)
• Line adjacency parameter (Fiber Type)
• AMP optical facility parameters (Mode, Target Gain, Target Power, and
Target Peak Power)
Operating, 323-1851-310, for information on how to display and edit
adjacency and optical facility parameters.
7 Check the subtending connections to CMD44. Make sure that the
connections, power levels and wavelengths are good.
8 Re-attempt to add the channels.
9 If the alarm does not clear, or clears then returns, or the channels cannot be
added, contact your next level of support or your Ciena support group.
—end—

Procedure 4-80
DOC Action Failed: Delete
Alarm ID: 577
Probable cause
This alarm is raised when a Channel Delete command (automatic or manual)
in DOC is requested and fails. Conditions that can cause this failure include:
fiber cut, occurred during the Channel Delete operation
• an optical disconnect, such as a fiber break, within the DOC span of
control
• a provisioning error on the Rx or Tx adjacency
• an associated adjacency or AMP facility is deleted
• the DOC Action: Channel Delete was stopped before the deletion was
completed
This alarm is cleared if the Clear DOC Alarms button is clicked in the DOC
application. However, this will not clear the underlying problem.

standby shelf processor (SP). If it is not, and the DOC is set to automatically
delete channels or you manually delete a channel during the standby SP
insertion, the DOC Action Failed: Delete alarm can be raised after the
insertion. In this case, the alarm will clear in approximately five minutes. For
details on deleting channels, refer to the “Deleting optical channels”
procedure in Commissioning and Testing, 323-1851-221.
Impact
Prerequisites


Step Action

fiber cut, occurred during the Delete channel operation, then this alarm will
be active. Ensure that the maintenance activities have completed.
2 Check for and clear an active DOC Invalid Photonic Domain alarm using the
323-1851-310.


Step Action
EDP):
parameters)
• Line adjacency parameter (Fiber Type)
• AMP optical facility parameters (Mode, Target Gain, Target Power, and
Target Peak Power)
6 If the Channel Condition field displays Then go to
a condition other than “Partially Deleted” step 7
“Partially Deleted” step 10
7 Click the Clear DOC Alarms button in the DOC window. This clears that
alarm; however, the underlying problem is not cleared.
8 Click the Re-optimize button, and wait until the optimization completes.
9 If the optimization Then go to
fails Procedure 4-82, “DOC Action
Failed: Optimize” on page 4-183
succeeds step 10
10 Re-attempt the Delete operation.
Attention: Any channels that were in the delete queue are returned to their
previous state when the deletion fails. These channels must be re-selected
for deletion.
support group.
—end—

Procedure 4-81
DOC Action Failed: Monitor
Alarm ID: 549
Probable cause
This alarm is raised when DOC is unable to monitor, and thus unable to
determine if the Photonic Domain is optimal. Conditions that can cause this
failure include:
control
• a circuit pack or module within the DOC photonic domain was replaced or
restarted
This alarm appears only on the affected DOC shelf. For details on provisioning
the automation mode, refer to the “Editing the DOC Settings” procedure in
This alarm is cleared if the DOC Primary state is changed to OOS. However,
this will not clear the underlying problem. Refer to the “Editing the DOC
Settings” procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310, for details on how to change the Primary State.
When the DOC Automation Mode is 'Enhanced Auto Monitor Only', then the
“DOC Action Failed: Monitor” alarm is raised only after two consecutive auto
monitor failures. The alarm is cleared when there is a successful auto monitor
or a successful optimization action, or when there is no longer any managed
channels on the DOC facility against which the alarm was raised.
Attention: If the DOC Automation Mode is set to 'Enhanced', then the 'DOC
Action Failed: Monitor' alarm is never raised. Auto monitor failures will feed
into raising the 'DOC Action Failed: Optimize' alarm.

standby shelf processor (SP). If it is not, the DOC Action Failed: Monitor
alarm can be raised after the insertion. In this case, the alarm will clear in
approximately five minutes. For details on provisioning the automation mode,
refer to the Domain Optical Controller (DOC) procedures in Part 2 of


Attention: When this alarm is raised, it indicates that DOC cannot

determine the optimization state of the system. As a result, DOC maintains
the current optimization state. If this alarm resulted from a comms issue, the
optimization state displayed in DOC is most likely correct. If this alarm
resulted from a system fault, such as a fiber cut, DOC may indicate the
system is optimized when it is not. Once the fault is repaired, the system
returns to its optimal state.
Impact
Prerequisites
Step Action

fiber cut, occurred while DOC automatic monitoring was running, then this
alarm will be active.
If this is the case, and the maintenance activities are complete, the alarm
should clear autonomously during the next DOC Auto Monitor run. DOC Auto
Monitor runs two minutes after the last DOC Auto Monitor operation
completes.
After the DOC Invalid Photonic Domain alarm clears, the DOC Action Failed:
Monitor alarm should clear autonomously during the next DOC Auto Monitor
run.


Step Action
After the above alarms clear, the DOC Action Failed: Monitor alarm should
clear autonomously during the next DOC Auto Monitor run.
323-1851-310.
After the other alarms and conditions clear, the DOC Action Failed: Monitor
alarm should clear autonomously during the next DOC Auto Monitor run.
support group.
—end—

Procedure 4-82
DOC Action Failed: Optimize
Alarm ID: 550
Probable cause
This alarm is raised when DOC is unable to perform a manual or automatic
re-optimization. The conditions that can cause this failure include:
fiber cut, occurred while DOC auto monitoring was running
control
• a circuit pack or module within the DOC photonic domain was replaced or
restarted
This alarm appears only on the affected DOC shelf. For details on provisioning
the automation mode, refer to the “Editing the DOC Settings” procedure in
This alarm can be raised when DOC is operating in either enhanced mode or
enhanced auto monitor only mode. The alarm hold off time is about 3-5
minutes.
This alarm is cleared if the DOC Primary state is changed to OOS. (Refer to
the “Editing the DOC Settings” procedure in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310, for details on how to change the
Primary state.) However, this will not clear the underlying problem.

standby shelf processor (SP). If it is not or you click Re-Optimize during the
standby SP insertion, the DOC Action Failed: Optimize alarm can be raised
after the insertion. In this case, the alarm will clear in approximately five
minutes. For details on provisioning the automation mode, refer to the
Domain Optical Controller procedures (DOC) in Part 2 of Configuration -
Impact


Prerequisites
Step Action

fiber cut, occurred while occurred while DOC auto re-optimize was running,
then this alarm will be active.
If this is the case, and the maintenance activities are complete, the alarm
should clear autonomously during the next DOC auto re-optimize run.
After the DOC Invalid Photonic Domain alarm clears, the DOC Action Failed:
Optimize alarm will clear autonomously during the next DOC Auto Monitor
run.
After the above alarms clear, the DOC Action: Fault Detected alarm should
clear autonomously during the next DOC auto re-optimize run.


Step Action

323-1851-310.
After the other alarms and conditions clear, the DOC Action Failed: Optimize
alarm should clear autonomously during the next DOC auto re-optimize run.
support group.
—end—

Procedure 4-83
DOC Action: Fault Detected
Alarm ID: 873
Probable cause
This alarm is raised during DOC automatic fault detection, when DOC detects
a fault or the action is not completed. The conditions that can cause this failure
include:
fiber cut, occurred while DOC monitoring was running
• a module power value crossed the operating threshold
• a module within the DOC photonic domain was replaced or restarted
• an optical disconnect (such as a fiber break) within the DOC span of
control
• malfunctioning hardware
• incorrect provisioning
This alarm appears only on the affected DOC network element.
This alarm is cleared if the DOC Primary state is changed to OOS. However,
this will not clear the underlying problem. Refer to the “Editing the DOC
Settings” procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310, for details on how to change the Primary state.
For the MLA2 w/VOA circuit pack if the VOA facility primary state is OOS, a
“DOC Action: Fault Detected” alarm is raised.
Attention: It is recommended that DOC be placed OOS before inserting the

standby shelf processor (SP). If it is not, and no DOC action is being
executed, the DOC Action: Fault Detected alarm can be raised after the
standby SP insertion. In this case, the alarm will clear in approximately one
minute.
Attention: When this alarm is raised, the Channel Fault Status (CFS) is not
necessarily updated.


Impact
Prerequisites
adjacency details
Step Action

fiber cut, occurred during the fault detection operation, then this alarm will be
active. Ensure that the maintenance activities have completed.


Step Action

323-1851-310.
EDP):
parameters)
• Line adjacency parameter (Fiber type)
• AMP optical facility parameters (Primary state, Mode, Target Gain,
Target Power, and Target Peak Power)
• OPTMON facility parameters (Primary state)
• CHC facility parameters primary state
10 Run DOC fault detection again (wait at least one minute).

support group.
—end—

Procedure 4-84
DOC Consecutive Re-Opt Threshold Crossed
Alarm ID: 874
Probable cause
This alarm is raised when DOC performs 25 re-optimizations in a row, with no
separation by successful auto-monitoring cycles. That is, when DOC
completes an optimization, the next monitoring cycle detects that another
re-optimization is required. This can occur when there are continuous power
fluctuations of greater than 1.0 dB, which causes DOC to detect that an
optimization is required.
The optimization type can either be an 'SPPC-only optimization' or a 'full

optimization', which includes both SPPC and incremental OSNR optimization.
For more information on various optimization types, refer to Photonic Layer
Guide, NTRN15DA.
Impact
Prerequisites
Step Action
1 If the alarm occurs during maintenance activities, such as module

replacement, module restart, or fiber cut, complete the activities.
After the maintenance activities are complete, wait five minutes (two minutes
if Enhanced DOC Automation mode is on). The alarm should clear
autonomously during the next DOC auto re-optimize as necessary run.
After the DOC Invalid Photonic Domain alarm clears, the DOC Consecutive
Re-Opt Threshold Crossed alarm should clear autonomously during the next
DOC auto re-optimize as necessary run.


Step Action

After the above alarms clear, the DOC Consecutive Re-Opt Threshold
Crossed alarm should clear autonomously during the next DOC auto
re-optimize as necessary run.
6 Use any active Gauge Threshold Crossing Alert Summary alarms to help
determine the exact cause of the power fluctuation. Fix the cause of the
power fluctuation, and let the system re-optimize.


Step Action
Use the DOC Logs window to view the DOC logs to determine which section
is reporting not-optimal and for what reason, and if another network element
reported an error. If necessary, review the DOC logs from the other network
element. Refer to the “Displaying the DOC logs for the summary table”
323-1851-310.
After the other alarms and conditions clear, the DOC Consecutive Re-Opt
Threshold Crossed alarm should clear autonomously during the next DOC
auto re-optimize as necessary run.
support group.
—end—

Procedure 4-85
DOC Domain Not Optimized
Alarm ID: 551
Probable cause
This alarm is raised when the system is not optimal, and the conditions that
cause the alarm cannot be cleared by automatic re-optimization or automatic
monitoring. The conditions that can cause this alarm include:
• a channel addition or deletion has failed (in the case of the alarm raised in
a broadcast domain, the failed addition or deletion may have occurred
within the primary domain where the traffic is broadcast)
• DOC has determined that the system is not optimal
• DOC Automation Mode is Enhanced Auto Monitor Only
This alarm is only raised if the DOC Automation mode is set to ‘Enhanced
Auto Monitor Only’. In this mode, if auto monitor DOC action declares that the
domain is not optimal, the 'DOC Domain Not Optimized' alarm is raised with
no hold off. The alarm clears when there is a successful full optimization or the
domain is found optimal by auto monitor DOC action or there is no managed
channel on the DOC facility on which the alarm is raised.
Note that when the DOC Automation mode is set to ‘Enhanced’, the “DOC
Domain Not Optimized” alarm is not raised even if the Channel Optimize State
(COS) of a channel is not optimal. Instead of “DOC Action Failed: Monitor” and
“DOC Domain Not Optimized” alarms, only the “DOC Action Failed: Optimize”
alarm is raised.
Impact
Prerequisites
adjacency details


DOC Domain Not Optimized
Step Action
1 If Then go to
the DOC Action Failed: Add alarm is Procedure 4-79, “DOC Action Failed:
active Add” on page 4-174
the DOC Action Failed: Delete alarm Procedure 4-80, “DOC Action Failed:
is active Delete” on page 4-177
the DOC Action Failed: Monitor Procedure 4-81, “DOC Action Failed:
alarm is active Monitor” on page 4-180
the DOC Action Failed: Optimize Procedure 4-82, “DOC Action Failed:
alarm is active Optimize” on page 4-183
the DOC Action: Fault Detected Procedure 4-83, "DOC Action: Fault
alarm is active Detected" on page 186
none of the above alarms are active step 2
2 Wait for the re-optimization or DOC Auto Monitor run to complete, or click the
Re-Optimize button to trigger an immediate re-optimization. Refer to the
“Re-optimizing channels” procedure in Part 2 of Configuration - Provisioning
If the re-optimization fails, follow the appropriate alarm clearing procedure(s)
in this document for any alarms raised as a result of the failed optimization.
323-1851-310.
support group.
—end—

Procedure 4-86
DOC Invalid Photonic Domain
Alarm ID: 552
Probable cause
This alarm is active during system lineup and test (SLAT), and only appears
on the affected DOC shelf.
This alarm is raised when DOC cannot retrieve a valid Network Topology.
Conditions that can cause this include:
control
• there is an incorrectly provisioned shelf parameter
• an upstream circuit pack has undergone a restart operation. The alarm
clears once the restart has completed.
• there are more than two DOC shelves provisioned within the optical
system
• a channel has been optimized in the system, and an upstream Tx on the
same channel has been provisioned. (To prevent this alarm from being
raised, enter the second Rx adjacency for the reused wavelength before
provisioning the second Tx adjacency.)
• DOC detecting that a DOC-controlled channel is expanded past its
previous egress point. (In this case, the alarm clears when DOC detects
that the expanded DOC-controlled channel is contracted back to its
original egress point.)
• DOC detecting that a DOC-controlled channel is contracted prior to its
previous egress point. (In this case, the alarm clears when DOC detects
that the contracted DOC-controlled channel is expanded back to its
original egress point.)
Impact
Prerequisites
details


Step Action
1 If the system is Then

being SLATed no action is required. The alarm clears after
SLAT.
already SLATed go to step 2
2 Verify that both DOC site network elements are commissioned and
connected to the network.
4 Verify that the shelf parameters are correctly provisioned. Correct any
discrepancies. Refer to the “Editing the nodal shelf parameters” procedure in
6 If a channel has been optimized in the system and an upstream Tx on the

same channel has been provisioned, remove the Tx adjacency or add an Rx
adjacency to terminate the wavelength properly. DOC clears the alarm after
the topology rebuilds. Refer to the “Editing facility parameters” procedure in


Step Action
8 Check if any of the following alarms, which indicate an internal

communications or equipment problem, are active within the DOC span of
control, and clear them using the procedures in this document:
• Circuit Pack Upgrade Failed
• Database Integrity Fail
• Database Recovery Incomplete
• Database Restore in Progress
• Database Save Failed
• Database Restore Failed
• Database Commit Failed
• Duplicate IP Address
• Duplicate Shelf Detected
• LAN-15 Port Failure
• LAN-16 Port Failure
• OSPF Adjacency Loss alarms
• Packet Rate Limit Exceeded
• Shelf Data Missing
• Software Auto-Upgrade in Progress
9 If you have cleared any alarms in step 8, wait at least 15 minutes.



Step Action
11 If you have cleared any alarms in step 10, wait at least 15 minutes.
14 Use the Domain Optical Controller to determine if a DOC-controlled channel

is expanded past its previous egress point. The Overall Status for the
channel appears as “Network Topology unavailable”. Refer to the Domain
Optical Controller (DOC) procedures in Part 2 of Configuration - Provisioning
The DOC logs may show a message such as:
<date> <time> Invalid topology, controlled
wavelength=<wavelength> starting in section <TID-SHELF-TX
PathID> was expanded beyond its egress point.
If any expanded channels are identified, contract the channel back to its
original egress point by placing the corresponding ADJ-RX facility OOS
(provision the CMD44 ADJ-RX Receiver type to UNKNOWN). Refer to the
“Editing facility parameters” procedure in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310. The Domain Optical Controller
Destination TID-Shelf-RxPathID column (specifically the last part of the
entry) of the expanded channel indicates where to edit the ADJ-RX.


Step Action

16 Use the Domain Optical Controller to determine if a DOC-controlled channel

is contracted prior to its previous egress point. The Overall Status for the
channel appears as “Network Topology unavailable”. Refer to the “Retrieving
Domain Optical Controller summary and details view” procedure in Part 2 of
The DOC logs may show a message such as:
<date> <time> Invalid topology, controlled
wavelength=<wavelength> starting in section <TID-SHELF-TX
PathID> was contracted from section <TID-SHELF-TX PathID> to
section <TID-SHELF-TX PathID>.
If any contracted channels are identified, expand the channel back to its
original egress point by placing the corresponding ADJ-RX facility IS (change
the CMD44 ADJ-RX Receiver type from UNKNOWN to the required value).
Refer to the “Editing facility parameters” procedure in Part 1 of Configuration
- Provisioning and Operating, 323-1851-310.
18 Use the DOC Logs window to view the DOC logs to determine if another
323-1851-310.
support group.
—end—

Procedure 4-87
DOC Power Audit Failed
Alarm ID: 1719
Probable cause
This alarm is raised against the DOC facility when the Domain Optical
Controller (DOC) Power Audit action fails.
This alarm can be caused by the following conditions:

• Unable to collect topology
• Fiber type not provisioned on a RAMAN facility
• OTDR Trace failed on a TELEMETRY facility, and the RAMAN facility is not
ready for calibration
• Optical Line Fail alarm raised against a RAMAN facility
• RAMAN or AMP facility primary state is not IS
• RAMAN or AMP facility in shutoff or APR
• Communication failure with card that has RAMAN facility
• RAMAN Calibration Failed
The specific cause of the alarm can be found by checking the DOC logs.
Impact
Warning, non-service-affecting (W, NSA)
Prerequisites
• be able to connect to the network element


DOC Power Audit Failed
Step Action
1 Use the DOC Logs window to view the DOC logs to determine if another
network element. This alarm clears when there is a successful Power Audit,
or a channel has been added successfully.
that are active within the DOC span of control, and then retry the Power Audit
• Automatic Power Reduction Active (visible in the historical fault list)
• Fiber Type Manual Provisioning Required
• OTDR High Reflection Detected
• Telemetry Loss Of Signal
• OTDR Trace Failed
3 Ensure all RAMAN and XLA primary states are in-service.

support group.
—end—

Procedure 4-88
Domain Optical Controller Disabled
Alarm ID: 1145
Probable cause
This alarm is raised when the Domain Optical Controller (DOC) facility has
been put into an out-of-service state by the user or due to an upgrade activity.
This alarm is raised against the DOC facility itself.
Impact
Prerequisites
• be able to connect to the network element
Step Action
1 Ensure that there is no software upgrade or network maintenance in progress

on the network and the DOC facility can be put in-service state.
2 Manually put the DOC facility in-service from Site Manager, or use the
RST-DOC TL-1 command. Refer to the “Editing the DOC Settings” procedure
support group.
—end—

Procedure 4-89
DS1 Receive alarms
Use this procedure to clear alarms associated with DS1 receive signals.
The 48 Channel Trans Mux (portless) and the PDH gateway circuit packs are
“portless”. In this procedure, the term “input signal” refers to ported circuit
packs. The generic term “receive signal” applies to both the ported and
portless circuit packs.
AIS (DS1)
Alarm ID: 23
Probable cause
This alarm is raised when there is a far-end failure that causes traffic loss or
the far-end equipment is out of service. The DS1 Rx AIS alarm is raised when
the network element detects an AIS on the DS1 receive signal.
For the Trans Mux and PDH gateway circuit packs, the DS1 AIS is received
from the VT1.5/VC11 envelope.
Impact
Bipolar Violations (DS1)

Alarm ID: 27
Probable cause
This alarm is raised when a DS1 or DSM 84xDS1 termination module (TM) is
faulty or the received signal from the outside DS1 source is degraded. A
Bipolar Violation (BPV) means that two +V or two -V binary ones are
transmitted consecutively without an opposite voltage binary one in between.
DS1 protocol uses ground as a binary zero and both +1 V and -1 V as binary
ones. The polarity of ones is always toggled, which gives the signal desirable
electrical characteristics and can be used to detect signal errors. This system
is called a bipolar system.
This alarm does not apply to the Trans Mux and PDH gateway circuit packs.
Impact
The DS1 signal is severely degraded.


DS1 Receive alarms
Frequency Out of Range (DS1)

Alarm ID: 30
Probable cause
This alarm is raised when the network element detects a DS1 input signal that
it cannot lock onto because of a frequency difference.
Impact
The impacted DS1 service cannot carry traffic.
Loss of Frame (DS1)

Alarm ID: 21
Probable cause
This alarm is raised when the DSM 84xDS1 termination module (TM) is
unable to detect the provisioned framing pattern in the DS1 input signal.
For the Trans Mux and PDH gateway circuit packs, this alarm is raised when
the circuit pack is faulty, or the framing format from the received DS1 is not
compatible, or the incoming quality of the signal is degraded.
According to Telcordia GR-253-CORE, LOF on an async mapped DS1 does

not result in AIS insertion. An alarm is raised, and the LOF signal passes
downstream.
Impact
Loss of Signal (DS1)

Alarm ID: 20
Probable cause
This alarm is raised when one of the following conditions exists:
• the DS1 signal is not received due to external cabling or connector
problem
• the DS1 signal stops transmitting from the adjacent network element
• the corresponding DS1 I/O module was removed


DS1 Receive alarms
• the corresponding DS1 I/O module is not fully inserted and locked into
position
• the DSM 84xDS1 termination module (TM) is faulty
Impact
Remote Alarm Indication (DS1)

Alarm ID: 25
Probable cause
This alarm is raised when the far-end network element detects a problem with
the DS1 receive signal, and responds with a Remote Alarm Indication (RAI).
An RAI is commonly called the yellow alarm signal.
The alarm is raised as soon as any one of four alarm signals is detected on
the far end:
• Circuit Pack fail
• Loss of Signal
• Loss of Frame
• AIS
Impact
Attention: The remote system is reporting traffic is down.
Prerequisites
323-1851-545.


DS1 Receive alarms
Step Action
1 Identify the DS1, Trans Mux, or PDH gateway circuit pack raising the alarm.
Refer to the “Identifying the circuit pack, pluggable module/port, or facility that
has raised an alarm” procedure in this document.
3 For the Trans Mux and PDH gateway circuit packs, verify that VT alarms are
enabled on the network element and at all points along the path. The default
alarm point status for VT alarms is not monitored. Edit the Alarm Profile if
necessary. Refer to the “Editing an alarm profile” procedure in this document.
4 Verify all cross-connects between the near-end and far-end network
elements. Refer to the “Retrieving path cross-connects” procedure in Part 1
of Configuration - Bandwidth and Data Services, 323-1851-320.
5 Retrieve all alarms at the far-end network element. Refer to the “Retrieving
active alarms for one or more network elements” procedure in this document.
Clear any alarms by following the appropriate alarm clearing procedure.
6 Ensure that the far-end facility is in-service.
7 If the original alarm was Then go to

AIS step 12
Bipolar Violation step 8
Frequency Out of Range step 8
Loss of Frame step 8
Loss of Signal step 8
Remote Alarm Indication step 12
8 Inspect the cabling and connectors. The cabling may be loose or damaged.
Repair any damage.
9 If the original alarm has not cleared, and was Then go to

Frequency Out of Range step 18
10 Ensure the corresponding I/O module is fully inserted and locked into
position.


DS1 Receive alarms
Step Action
11 Use a DS1 test set to determine if a valid DS1 signal is on the DS1
cross-connect for that facility.
If there is no valid DS1 signal, the problem is with the DS1 source and the
shelf is reporting a valid condition. Perform troubleshooting on the source
system according to your company procedures.
If the alarm has not cleared, go to step 20.
12 Verify the required frame format provisioning for the entire DS1 traffic path
(refer to your company records). Edit the frame format if necessary. If the
local DS1 facility frame format requires correction, refer to the “Editing facility
Operating, 323-1851-310.
13 If the alarm has not cleared, check if there is any signal degradation of the
upstream DS1 traffic path, including any DS1 and/or optical facilities carrying
the DS1 signal. Signal degradation can be indicated by alarms such as Signal
Degrade, Signal Fail, Excessive Error Rate, or similar; or by performance
monitoring Threshold Crossing Alerts (TCA). If applicable, resolve the signal
degradation of the DS1 traffic path associated with these alarms and/or
TCAs.

AIS step 15
Remote Alarm Indication step 16
15 Use a DS1 test set to determine if a valid DS1 signal is on the DS1
If there is an AIS, the problem is with the DS1 source and the shelf is reporting
a valid condition. Perform troubleshooting on the source system according to
your company procedures. The procedure is complete.
16 Use a DS1 test set to test the signal source.
• If there is a valid signal on the transmit side and there is RAI on the
receive side, the problem is in the source system. Perform
troubleshooting on the source system according to your company
procedures. The procedure is complete.
• If there are no such conditions, go to step 27.


DS1 Receive alarms
Step Action
17 Use a DS1 test set to test the signal source.

• If there are bipolar violations (BPV), the problem is in the DS1 source and
the shelf is reporting a valid condition. Perform troubleshooting on the
source system according to your company procedures. The procedure is
complete.
• If there are no BPVs, go to step 20.
18 Use a DS1 test set to determine if the DS1 signal frequency is out of range.
• If there is a frequency that is out of range for a DS1, the problem is in the
DS1 source and the shelf is reporting a valid condition. Perform
• If there is no such condition, go to step 20.
19 Determine if a valid DS1 signal is on the cross-connect for the facility raising
the alarm. For ported circuit packs, use a DS1 test set. For portless circuit
packs, use a test access session. Refer to the “Creating a test access session
(TAS)” procedure in Part 2 of Configuration - Provisioning and Operating,
323-1851-310.
• If there is an Loss of Frame or incorrect framing, the problem is in the DS1
source and the shelf is reporting a valid condition. Perform
20 If the circuit pack identified in step 1 is Then go to

a protected DS1, Trans Mux, or PDH gateway circuit pack with step 21
no Protection Switch Active alarms present
a protected DS1, Trans Mux, or PDH gateway circuit pack with step 22
Protection Switch Active alarms present
an unprotected DS1, Trans Mux, or PDH gateway circuit pack step 26
21 Perform a manual switch on the working circuit pack identified in step 1. Refer
to the “Operating a protection switch” procedure in Part 2 of Configuration -
Go to step 23.
22 Clear the Protection Switch Active alarms. Refer to the “Protection Switch
Active Alarms” alarm clearing procedure in Part 2 of this document.


DS1 Receive alarms
Step Action
23 Wait for 30 seconds. Retrieve all alarms to determine if the original alarm has
cleared.
cleared step 24
not cleared step 27
24 Replace the DS1, Trans Mux, or PDH gateway working circuit pack identified
in step 1. Refer to the equipment replacement procedures in chapter 2 of
25 If applicable, release the lockout of protection on the DS1, Trans Mux, or PDH
gateway working circuit pack.
not cleared step 27

—end—

Procedure 4-90
DS3 and E3 Receive alarms
Use this procedure to clear alarms associated with DS3 and E3 receive
signals.
“portless”. In this procedure, the terms “port” and “input signal” refer to ported
circuit packs, such as 24xDS3/EC-1 and 24xDS3/E1. The generic term
“receive signal” applies to both the ported and portless circuit packs.
AIS (DS3/E3)
Alarm ID: 42, 856
Probable cause
This alarm is raised when the network element detects an AIS on the DS3/E3
receive signal. The upstream equipment generates an AIS signal to tell
downstream equipment that a failure occurred. This alarm indicates that the
DS3/E3 source has a failure.
Impact
Bipolar Violations (DS3/E3)

Alarm ID: 43, 857
Probable cause
This alarm is raised when the 24xDS3/EC-1 or the 24xDS3/E3 circuit pack
becomes faulty, or the signal from the outside DS3 or E3 source is degraded.
A bipolar violation alarm means that two +1 V or two -1 V binary ones
transmitted consecutively without an opposite voltage binary one in between
and the errors occurred at a rate greater than 1E-3 a second.
DS3 protocol uses ground as a binary zero and both +1 V and -1 V as binary
ones. The polarity of ones is always toggled, which gives the signal desirable
electrical characteristics and can be used to detect signal errors. This system
is called a bipolar system.
Impact
The DS3/E3 signal is severely degraded.


Frame Format Mismatch (DS3)

Alarm ID: 641
Probable cause
This alarm is raised when the frame format provisioned for a DS3 facility on a
24xDS3/EC-1, 24xDS3/E3, Trans Mux, or PDH gateway circuit pack does not
match the frame format of the received signal. That is, one format uses M23
framing and the other format uses C-bit framing.
If a DS3 facility on a 24xDS3/EC-1, 24xDS3/E3, Trans Mux, or PDH gateway

circuit pack is provisioned for C-bit framing but the received signal uses M23
framing, then the channelized DS3 signal cannot be demultiplexed into DS1
signals. In this case, DS1 AIS signals are transmitted toward the optics.
When the framing format is C-bit framed, the CP-bit parity errors cause the
Frame Format Mismatch alarm to raise, which masks the Signal Degrade
alarm. Therefore, a Frame Format Mismatch alarm can result from conditions
that cause a Signal Degrade to raise.
Impact
Frequency Out of Range (DS3)

Alarm ID: 87
Probable cause
This alarm is raised when the network element detects a signal on a DS3 input
that is out of the normal frequency range of the 24xDS3/EC-1 or 24xDS3/E3
circuit pack.
Impact
The shelf may be unable to carry traffic.
Loss of Frame (DS3/E3)

Alarm ID: 41, 855
Probable cause
This alarm is raised when the 24xDS3/EC-1, 24xDS3/E3, Trans Mux, or PDH
gateway circuit pack is faulty, or the framing format from the received DS3 is
not compatible, or the incoming quality of the signal is degraded.
This alarm will be raised for E3 when the E3 facility detects an incoming loss
of framing.


This procedure assumes that the provisioned framing is correct and was not
changed to create the alarm.
This procedure assumes that the upstream and downstream network

elements have been operating with the same frame format configuration. It
also assumes that the alarm is not caused by provisioning activity.
Impact
The shelf cannot carry traffic.
Loss of Signal (DS3/E3)

Alarm ID: 40, 854
Probable cause
This alarm is raised when one of the following conditions exists:
• the cable/interconnection has been disconnected or faulty
• the DS3/E3 signal stopped transmitting from the adjacent network
element
• the I/O module was removed
• the I/O module is not fully inserted and locked into position
• the 24xDS3/EC-1or 24xDS3/E3 circuit pack is faulty
Impact
Remote Alarm Indication (DS3)

Alarm ID: 44
Probable cause
This alarm is raised when the remote network element detects a defective
DS3 signal from the 6500 network element and returns a Remote Alarm
Indication signal in the DS3 overhead.
For the 24xDS3/E3, Trans Mux and PDH gateway circuit pack, the alarm is
raised as soon as any one of four alarm signals is detected at the far-end:
• Circuit Pack fail
• Loss of Signal


• Loss of Frame
• AIS
Impact
Traffic is being reported down by the remote system.
Remote Defect Indication (E3)

Alarm ID: 858
Probable cause
Refer to the “Remote Defect Indication” alarm in Part 2 of this document.
Impact
Signal Degrade (DS3/E3)

Alarm ID: 122
Probable cause
This alarm is raised when a 24xDS3/EC-1or 24xDS3/E3 circuit pack detects
parity errors coming from the DS3/E3 input signal. In particular, a DS3 signal
degrade is (P-bit or CP-bit) parity at a rate exceeding 10E-6. When the
framing format is C-bit framed, the CP-bit parity errors cause the Frame
Format Mismatch alarm to raise, which masks the Signal Degrade alarm.
The alarm is caused by one of the following conditions:

• faulty DS3/E3 input cable or connector
• problem with the DS3/E3 signal source
• faulty 24xDS3/EC-1 or 24xDS3/E3 circuit pack
Impact


Prerequisites
323-1851-545.
Step Action
1 Identify the 24xDS3/EC-1, 24xDS3/E3, Trans Mux, or PDH gateway circuit

pack raising the alarm. Refer to the “Identifying the circuit pack, pluggable
module/port, or facility that has raised an alarm” procedure in this document.
3 Retrieve all alarms at the far-end network element and all network elements
along the path. Refer to the “Retrieving active alarms for one or more network
elements” procedure in this document. Clear any alarms by following the
appropriate alarm clearing procedure.

AIS (DS3/E3) step 11
Bipolar Violation (DS3/E3) step 6
Frequency Out of Range (DS3) step 6
Loss of Frame (DS3/E3) step 6
Loss of Signal (DS3/E3) step 6
Frame Format Mismatch (DS3) step 11
Remote Alarm Indication (DS3) step 11
Signal Degrade (DS3/E3) step 26
6 Inspect the cabling and connectors on the I/O panel. The cabling may be
loose or damaged. Repair any damage.


Step Action

Bipolar Violation (DS3/E3) step 16
Frequency Out of Range (DS3) step 17
Loss of Frame (DS3/E3) step 11
Loss of Signal (DS3/E3) step 9
position.
10 Use a DS3/E3 test set to determine if a valid DS3/E3 signal is on the DS3/E3
If there is no valid DS3/E3 signal, the problem is in the DS3/E3 source and
the shelf is reporting a valid condition. Perform troubleshooting on the source
system according to your company procedures.
11 Verify the required frame format provisioning for the entire DS3/E3 traffic path
local DS3/E3 facility frame format requires correction, refer to the “Editing
facility parameters” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
12 If the alarm has not cleared, check if there is any signal degradation of the
upstream DS3/E3 traffic path, including any DS3/E3 and/or optical facilities
carrying the DS3/E3 signal. Signal degradation can be indicated by alarms
such as Signal Degrade, Signal Fail, Excessive Error Rate, or similar; or by
performance monitoring Threshold Crossing Alerts (TCA). If applicable,
resolve the signal degradation of the DS3/E3 traffic path associated with
these alarms and/or TCAs.
Note that determination of the frame format from the DS3 signal is dependent
in part on the parity bits in the DS3 traffic overhead so in some cases if the
parity error rate is high enough the Frame Format Mismatch alarm can be
raised for a DS3 facility on 24xDS3/EC-1, 24xDS3/E3, Trans Mux, or PDH
gateway circuit pack.
AIS (DS3/E3) step 14
Frame Format Mismatch step 29
Remote Alarm Indication (DS3) step 15


Step Action
14 Use a DS3/E3 test set to determine if a valid DS3/E3 signal is on the DS3/E3
If there is an AIS, the problem is with the DS3/E3 source and the shelf is
reporting a valid condition. Perform troubleshooting on the source system
according to your company procedures.
15 Use a DS3/E3 test set to test the signal source.
• If there is a valid signal on the transmit side and there is RAI on the
receive side, the problem is in the source system. Perform
If there are no such conditions, go to step 29.
16 Use a DS3/E3 test set to test the signal source.
• If there are bipolar violations (BPV), the problem is in the DS3/E3 source
and the shelf is reporting a valid condition. Perform troubleshooting on
the source system according to your company procedures. The
procedure is complete.
• If there are no BPVs, go to step 19.
17 Use a DS3 test set to determine if DS3 signal frequency is out of range.
• If there is a frequency that is out of range for a DS3, the problem is in the
DS3 source and the shelf is reporting a valid condition. Perform
18 Determine if a valid DS3/E3 signal is on the cross-connect for the facility
raising the alarm. For ported circuit packs, use a DS3/E3 test set. For portless
circuit packs, use a test access session. Refer to the “Creating a test access
session (TAS)” procedure in Part 2 of Configuration - Provisioning and
Operating, 323-1851-310.
• If there is an Loss of Frame or incorrect framing, the problem is in the
DS3/E3 source and the shelf is reporting a valid condition. Perform


Step Action

a protected 24xDS3/EC-1, 24xDS3/E3, Trans Mux, or PDH step 20
gateway circuit pack with no Protection Switch Active alarms
present
a protected 24xDS3/EC-1, 24xDS3/E3, Trans Mux, or PDH step 21
gateway circuit pack with Protection Switch Active alarms
present
an unprotected 24xDS3/EC-1, 24xDS3/E3, Trans Mux, or PDH step 29
gateway circuit pack
21 Clear the Protection Switch Active alarms. Refer to the “Protection Switch
Active Alarms” in Part 2 of this document.
cleared.
cleared step 23
not cleared step 29
23 Replace the 24xDS3/EC-1, 24xDS3/E3, Trans Mux, or PDH gateway

working circuit pack identified in step 1. Refer to the equipment replacement
323-1851-545.
24 If applicable, release the lockout of protection on the 24xDS3/EC-1,
24xDS3/E3, Trans Mux, or PDH gateway circuit pack.
25 Retrieve all alarms to determine if the original alarm has cleared.
not cleared step 29
26 Unplug the DS3/E3 cable and connect it to a DS3/E3 receiver test set. Verify
that a DS3/E3 signal is on the cable and the test set does not detect any
errors.
CAUTION
Risk of service loss
Ensure that the correct DS3/E3 cable is unplugged.
Removing the wrong cable will cause another DS3/E3
signal to be lost.


Step Action
27 If there is no signal, repair and reconnect the DS3/E3 cable.

If there are errors, repair the source generating the DS3/E3 signal.
28 If the alarm does not clear, replace the 24xDS3/EC-1, 24xDS3/E3 or PDH
gateway circuit pack carrying this facility. Refer to the equipment replacement
323-1851-545.
support group.
—end—

Procedure 4-91
Dormant Account Detected
Alarm ID: 1372
Probable cause
This alarm is raised when there is at least one user account that has become
dormant. This can be verified by opening the User Profile Application in Site
Manager and look at "Password status" column. The alarm clears when there
is "NO" DORMANT account left in the system.
Impact
Prerequisites
To perform this procedure, you must use an account with at least a level 4
UPC.
Step Action
1 Change the status of the dormant account to "Valid" account, "Disabled"

account, or delete the dormant user account.
If you want to Then go to
change the status of the dormant account to Valid step 2
change the status of the dormant account to Disabled step 3
Delete the dormant user account step 4
2 In Site Manager, open a User Profile Application, select DORMANT account,

select "Enable" button. This will change the password status from Dormant to
Valid.
3 In Site Manager, open a User Profile Application, select DORMANT account,
select "Disable" button. This will change the password status from Dormant
to Disabled.
4 Site Manager, open a User Profile Application, select DORMANT account,
select "Delete" button. This will delete the Dormant user account.
support group.
—end—

Procedure 4-92
DSM-Host Misconnection
Alarm ID: 264
Probable cause
This alarm is raised against a host optical interface (OC-3) facility if the Host
OC-3 facility is a prov-link of one DSM 84xDS1 termination module (TM) but
• is linked by fiber to an OC-3 port in another optical interface circuit pack
• is linked by fiber to an OC-3 port in another optical interface circuit pack in
another network element
• is linked by fiber to the incorrect DSM 84xDS1 TM of the same DS1
service module (DSM)
• is linked by fiber to a DSM 84xDS1 TM in another DSM (if this is a
protected scenario only)
• has a misconnected DSM 84xDS1 TM in the same DSM 84xDS1 TM
This alarm is also raised when the working and protection host cards have
different variant types (5G MRO LO, 5G MRO HO, 10G MRO LO, 10G MRO
HO).
Impact
Critical, service-affecting (C, SA) alarm if the OC-3 facility is active
Major, non-service-affecting (M, NSA) alarm if not active
Prerequisites
Step Action
1 Select Inventory from the Configuration menu to see if the DSM 84xDS1
TM is displayed in the inventory list.
If the DSM 84xDS1 TM inventory is displayed then an OAM link exists. Go to
step 2.
If the DSM 84xDS1 TM is not displayed in the inventory list, there is no OAM
link, verify the fiber-links.


Step Action
3 If you want an unprotected connection, verify that the Host OC-3 is

fiber-linked to the slot 1 DSM 84xDS1 TM of the correct DSM and that
provisioning is for that slot 1 DSM 84xDS1 TM.
4
CAUTION
Risk of misconnection
Ensure the fibers from the OC-3 hosts are connected to
the intended DSM. If you have two DSMs that will use
two different OC-3 facilities, perform a lamp test to
verify that you have connected the fiber to the intended
DSM. Refer to the “Lamp Test” section in chapter 1 of
this document.
If the fiber is not connected to the intended DSM, link the fiber to the
appropriate OC-3 line facility of the DSM 84xDS1 TM in the correct DSM.
5 If you want a protected connection, verify that the DSM 84xDS1 TM in slot 2
of the DSM is not connected:
• to another network element
• to another DSM 84xDS1 TM in another DSM
• to the wrong OC-3 on the same network element
If two DSMs are misconnected, the condition can appear as only one
misconnection alarm.
6 If any situation from step 5 is true, link the fiber to the appropriate OC-3 line
facility for the DSM 84xDS1 TM on the correct DSM.
7 If the alarm does not clear, look for an “Intercard suspected” alarm on both
the DSM 84xDS1 TMs and clear them first. Refer to the “Intercard Suspected”
alarm in Part 2 of this document.
8 Select Active Alarms from the Faults menu to retrieve alarms and determine
if the misconnection alarm cleared.
9 If the alarm does not clear, verify the fiber connection:
• Host OC-3 odd slot-port to DSM 84xDS1 termination module-1
• Host OC-3 even slot-port to DSM 84xDS1 termination module-2
Resolve any mis-configuration if needed.
10 Link the fiber from the OC-3 line facility to the DSM 84xDS1 TM in the
appropriate DSM.


Step Action
11 If the alarm does not clear, verify that the even slot Host OC-3 is connected
to the same DSM as the odd slot Host OC-3.
Match the serial numbers of the working and mate circuit packs from the
inventory list to verify the connection is to the same DSM.
support group.
—end—

Procedure 4-93
Duplicate Adjacency Discovered
Alarm ID: 1071
Probable cause
This alarm is raised against an ADJ facility when two or more ports at the far
end have the same TID-SHELF-SLOT-PORT Addresses.
Impact
Prerequisites
• use an account with at least a level 3 UPC on the shelves with a duplicate
Far End Address
correct Far End Address
Step Action
1 Identify the shelves raising this alarm.

2 Note the TID-SHELF-SLOT-PORT that the alarm is raised against. In the
Active Alarms table, the TID appears in the Network Element column, and the
SHELF-SLOT-PORT appears after “ADJ-” in the Unit column.
3 In the Site Manager Equipment and Facility Provisioning application, examine
the ADJ facility type lists for each applicable equipment and each shelf.
Search for the TID-SHELF-SLOT-PORT noted in step 2 in the Expected Far
End Address column. Note all matches found for all shelves within the siteID.
4 Determine which port has the correct Far End Address and remove the
duplicate entries by setting their Expected Far End Address formats to NULL
or the correct value.
support group.
—end—

Procedure 4-94
Duplicate IP Address
Alarm ID: 545
Probable cause
This alarm is raised when the system detects another network element with
the same Internet protocol (IP) address. The alarm occurs at the same time at
all network elements that share the same IP.
This alarm will also be raised on all connected network elements (visible to
each other).
Attention: This alarm is displayed in the Additional Information column of

the AID and the IP address of the port the alarm is detected on. The
additional information is only available on SP-2.
Impact
Prerequisites
• use an account with at least a level 3 UPC on the nodes with a duplicate IP
correct IPs
Step Action
1 Identify the network elements raising this alarm.

2 Determine from network plans or other documents which network element
has the correct IP.


Duplicate IP Address
Step Action
3 Log into the network element with the duplicate IP and correct the IP address
As follows:
• From the Configuration menu, open the Comms Setting Management
• In the Comms Setting Management click on Interfaces tab
• In the Interface Type drop down menu, select IP.
• Choose the Edit button to change the IP address.
If a remote log in is not possible, log in locally using the RS-232 serial modem
port or the craft 10/100BT port.
CAUTION
Risk of loss of functionality
Ensure every network element has an unique IP. If you
are changing the IP of a network element, ensure that
the new IP is correct.
4 Ensure no other Duplicate IP Address alarms exist. If there are other

Duplicate IP Address alarms, repeat this procedure.
support group.
—end—

Procedure 4-95
Duplicate Primary Shelf
Alarm ID: 714
Probable cause
This alarm indicates there are duplicate primary shelves within a consolidated
node, and is raised against all primary shelves within a consolidated node that
are provisioned to be a primary shelf.
Attention: A primary shelf will not auto-enroll or allow manual addition of

new member shelves while a duplicate primary shelf exists on the same
network.
Impact
Major, non-service-affecting (M, NSA)
Prerequisites
• be able to log into both shelves in the duplicate primary condition
correct primary shelves
Step Action
1 Identify the network elements raising the alarm. Refer to the “Identifying the
circuit pack, pluggable module/port, or facility that has raised an alarm”
procedure in this document
2 Determine from network plans or other documents which shelf should be the
primary shelf.
3 Log into the network element that is incorrectly enabled as a primary shelf.


Duplicate Primary Shelf
Step Action
4
CAUTION
Disabling the primary shelf will cause an administrative
restart of the affected shelf. It will be unavailable for
management during this time frame, and may require
re-provisioning of the network element. Ensure you
have removed the appropriate duplicate primary.
Record all of the provisioning information required to re-add the incorrectly

provisioned member shelf to the consolidated node. Then delete the invalid
primary shelf from the consolidated node. Refer to the “Deleting a member
shelf of a consolidated node” procedure in Administration and Security,
323-1851-301.
5 Re-add the deleted shelf as a member shelf of the consolidated node with the
Primary shelf parameter set to Disabled. Refer to the “Adding a shelf to a
consolidated node” procedure in Administration and Security, 323-1851-301.
6 Ensure no other Duplicate Primary Shelf alarms exist. If there are other
Duplicate Primary Shelf alarms, repeat this procedure for the new duplicate.
support group.
—end—

Procedure 4-96
Duplicate Shelf Detected
Alarm ID: 70
Probable cause
This alarm is raised when the shelf processor detects another network
element with the same shelf number and TID (also referred to as node name).
The alarm occurs at the same time on all network elements that share the
same shelf number and TID. Each shelf processor of the network element with
the same shelf number and TID detects the condition.
After a shelf processor restart, this alarm is masked for 20 minutes.
Impact
Prerequisites
• ensure that you are the only active user logged into the network element
• be able to log into the nodes that do not have a unique shelf number and
TID
correct shelf numbers and TIDs
Step Action
procedure in this document
2 Determine from network plans or other documents which shelf has incorrectly
provisioned information.


Duplicate Shelf Detected
Step Action
3 Note that changing the shelf number requires decommissioning and

recommissioning of the network element.
If the network is mixed 6500 and 565, 5100 and 5200 Advanced Services
Platform, change the Shelf number on the 5100/5200 which requires a warm
restart, instead of full recommission of the 6500.
CAUTION
Traffic and data communications will be lost
Decommissioning a shelf results in a loss of all traffic
and data communications associated with the shelf that
is being decommissioned.
CAUTION
Ensure that you have identified the correct duplicate. A
software configuration restart is required to properly
recover, removing network visibility of the member
node for the duration of the restart.
If the Then
shelf Name (TID) is correct the shelf name. Refer to the “Editing the
incorrectly provisioned shelf number” procedure in Administration and
Security, 323-1851-301.
Shelf number is Record all of the provisioning information
incorrectly provisioned required to recommission the shelf.
Decommission the shelf and re-add it with the
correct shelf number. Refer to the “Deleting all
shelf provisioning” procedure in Administration
and Security, 323-1851-301 and
“Commissioning a network element” procedure
in Commissioning and Testing, 323-1851-221.
4 Ensure no other Duplicate Shelf Detected alarms exist. If other duplicate shelf
alarms exist, repeat this procedure for the new duplicate(s).
5 If the alarm does not clear, contact your next level of support or Ciena support
group.
—end—

Procedure 4-97
Duplicate Site ID
Alarm ID: 871
Probable cause
This alarm is raised when both the site identifier and the shelf number of two
or more shelves are the same. The alarm occurs at the same time on all
network elements that share the same site identifier and shelf number. (The
alarm is not raised when the site identifier is 0.) Each shelf processor detects
the condition and raises the alarm against the shelf.
After a shelf processor restart, this alarm can be masked for 20 minutes.
Attention: You can edit the site identifier, however changing the shelf
number requires decommissioning and recommissioning of the network
element.
Impact
Prerequisites
• be able to log into the nodes that do not have a unique site identifier and
shelf number
correct site identifiers and shelf numbers
Step Action


Duplicate Site ID
Step Action
2
CAUTION
Traffic and data communications will be lost
Decommissioning a shelf results in a loss of all traffic and
data communications associated with the shelf that is being
decommissioned.
If the Then go to
site identifier is incorrectly provisioned step 3
shelf number is incorrectly provisioned step 4
3 Determine from network plans or other documents which network element
has the incorrect site identifier. Edit the incorrect site identifier to be
something unique from all other shelves in the network. Refer to the “Editing
the nodal shelf parameters” procedure in Administration and Security,
323-1851-301.
Go to step 5.
4 If the network is mixed 6500 and 5100/5200, change the Shelf number on the
5100/5200 which requires a warm restart, instead of full recommission of the
6500.
If the network is 6500, record all the provisioning information required to
recommission the shelf. Decommission the shelf and re-provision it with the
correct information. Refer to the “Deleting all shelf provisioning” procedure in
Administration and Security, 323-1851-301 and “Commissioning a network
element” procedure in Commissioning and Testing, 323-1851-221.
5 Verify that no other Duplicate Site ID alarms exist.
If Then
no other Duplicate Site ID alarms exist the procedure is complete
other Duplicate Site ID alarms exist repeat step 1 to step 4 for the
other duplicate(s).
Go to step 6.
6 If the alarm does not clear, contact your next level of support or Ciena support
group.
—end—

Procedure 4-98
E1 Receive alarms
Use this procedure to clear alarms associated with E1 receive signals.
“portless”. In this procedure, the terms E1 “port” and “input signal” refer to
ported circuit packs, such as 63xE1. The generic term “E1 receive signal”
applies to both the ported and portless circuit packs.
AIS (E1)
Alarm ID: 227
Probable cause
This alarm is raised when the network element detects an AIS on the E1
receive signal. The upstream equipment generates an AIS signal to tell
downstream equipment that a failure occurred. This alarm indicates that the
E1 source has a failure.
Impact
Bipolar Violations (E1)

Alarm ID: 229
Probable cause
This alarm is raised when the network element detects HDB3 bipolar
violations (BPV) on the incoming E1 port and the error rate is rate greater than
1E-3.
Impact
Loss of Frame (E1)

Alarm ID: 226
Probable cause
This alarm is raised when the network element is unable to detect the
provisioned framing pattern of the E1 receive signal.
Impact


E1 Receive alarms
Loss of Multiframe (E1)

Alarm ID: 230
Probable cause
This alarm is raised when the network element is unable to recover the
multiframe information from the E1 receive signal when the facility is
configured to multiframe.
Impact
Loss of Signal (E1)

Alarm ID: 225
Probable cause
This alarm is raised when one of the following conditions exist:
• 63xE1 circuit pack faulty
• fault on equipment generating the E1 signal
• faulty cables or connectors
Impact
Remote Defect Indication (E1)

Alarm ID: 927
Probable cause
Impact
Prerequisites
323-1851-545


E1 Receive alarms
Step Action
in this document.
4 Retrieve all alarms at the far-end network element. Refer to the “Retrieving
Clear any alarms by following the appropriate alarm clearing procedure.

AIS step 8
Loss of Multiframe step 8
7 Inspect the cabling and connectors on the I/O panel. The cabling may be
loose or damaged. Repair any damage.
Go to step 9.
8 Verify the required frame format provisioning for the entire E1 traffic path
local DS3/E3 facility frame format requires correction, refer to the “Editing
facility parameters” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
10 If the original alarm was raised on a Then go to

ported circuit pack (for example, 63xE1) step 11
portless circuit pack (for example, Trans Mux or step 15
PDH gateway)


E1 Receive alarms
Step Action
11 For E1 on optical/front electrical shelf, if the signal impedance is 75 ohm,

confirm that 120 ohm converter modules are not present for the indicated
circuit pack. If the signal impedance is 120 ohm, confirm that 120 ohm
converter modules are present for the indicated circuit pack (for E1 on a
Metro front electrical shelf, use either 75 ohm or 120 ohm I/O modules).
12 Use an appropriate test set to determine if the E1 port has a valid E1 signal.
The E1 ports are on the I/O panel associated with the 63xE1 circuit pack
raising the alarm. For information about I/O panels, refer to the “I/O and
protection hardware” section in chapter 3 of Part 1 of 6500 Planning,
NTRN10CF.
13 If Then go to
there is an AIS, bipolar violation, loss of frame, loss of step 14
multiframe, or loss of signal condition
the signal is valid step 15
14 The problem is in the E1 source equipment and the 6500 shelf is reporting a
valid condition. Perform troubleshooting on the E1 source equipment
according to your company procedure.

a protected 63xE1, Trans Mux, or PDH gateway circuit pack step 16
with no Protection Switch Active alarms present
a protected 63xE1, Trans Mux, or PDH gateway circuit pack step 17
with Protection Switch Active alarms present
an unprotected 63xE1, Trans Mux, or PDH gateway circuit pack step 21
Go to step 18.
17 Clear the Protection Switch Active alarms. Refer to Protection Switch Active
Alarms in Part 2 of this document.
cleared.
cleared step 19
not cleared step 22


E1 Receive alarms
Step Action
19 Replace the 63xE1, Trans Mux, or PDH gateway working circuit pack
identified in step 1. Refer to the equipment replacement procedures in
20 If applicable, release the lockout of protection on the 63xE1, Trans Mux, or
PDH gateway working circuit pack.
not cleared step 22

—end—

Procedure 4-99
E1 Transmit alarms
Use this procedure to clear alarms associated with E1 transmit signals.
Tx AIS (E1)
Alarm ID: 231
Probable cause
This alarm is raised when the network element detects a failed E1 signal
upstream on the other side of the connection. The network element is
transmitting an AIS to the remote end of the input. This alarm indicates a
warning to the downstream network element that the signal is not usable.
This alarm occurs because of:

• an E1 receive fault (for example, Loss of signal, Loss of frame, AIS) where
the signal enters the network
• a SONET/SDH fault condition (OC-n/STM-n or VT2/VC12 alarms)
• a DS3 or E3 fault for Trans Mux E1 signals carried by a DS3 or E3 signal
• no cross-connect assigned for the E1
This alarm can also be raised if an intrusive test access session is in progress.
no action is required if this is the cause.
Impact
Tx Loss of Frame (E1)

Alarm ID: 236
Probable cause
For the 63xE1 circuit pack, this alarm is raised when the local network element
detects that the E1 payload from the VT1.5/VT2/VC12 transmitted from the
shelf is not framed in the same format as the commissioned port.
For the Trans Mux circuit pack, this alarm is raised when the local network
element detects that the E1 payload within the DS3 or E3 signal (sent from the
XC circuit pack to the Trans Mux circuit pack) transmitted from the shelf
(within a VT2 signal) is not framed in the same format as the commissioned
port. Note that the E1 signal is then transmitted from the Trans Mux to the XC
within a VT2.
This procedure assumes that the system was operating alarm free before the
Tx Loss of Frame alarm. If this alarm is raised during E1 provisioning, verify
the provisioned framing with the test traffic you are running.


E1 Transmit alarms
Impact
The payload continues to transmit to the input. However, the change of

framing can cause the equipment to reject the E1 signal.
Tx Loss of Multiframe (E1)

Alarm ID: 237
Probable cause
For the 63xE1 circuit pack, this alarm is raised when the local network element
cannot recover the multiframe information in the E1 payload from the
VT2/VC12 and the port is configured to multiframe.
For the Trans Mux circuit pack, this alarm is raised when the local network
element cannot recover the multiframe information in the E1 payload within
the DS3 or E3 signal (sent from the XC circuit pack to the Trans Mux circuit
pack) transmitted from the shelf (within a VT2 signal) and the port is
configured to multiframe. Note that the E1 signal is then transmitted from the
Trans Mux to the XC within a VT2.
This procedure assumes that the system was operating alarm free before the
Tx Loss of Multiframe alarm. If this alarm is raised during E1 provisioning,
verify the provisioned framing with the test traffic you are running.
Impact
The payload continues to transmit to the input. However, the change of

framing can cause the equipment to reject the E1 signal.
Prerequisites
• clear all SONET/SDH (OC-n/STM-n or VT2/VC12) alarms and E1 receive
alarms related to the circuit path in the network
• clear all DS3 or E3 alarms related to the E1 circuit path in the network (if
the E1 is carried within a DS3 or E3 payload on a Trans Mux circuit pack)
• have the network connection information (that is, how the network element
connects to other network elements)


E1 Transmit alarms
Step Action
1 Another failure in the system normally causes this alarm. Clear any other
OC-n/STM-n or VT2/VC12 alarms or E1 receive alarms on the system first.
Perform this procedure if the Tx AIS or Tx Loss of Frame, or Tx Loss of
Multiframe alarms are the only active alarms on the system.
2 Identify the 63xE1, Trans Mux or PDH gateway circuit pack and port raising
the alarm. Refer to the “Identifying the circuit pack, pluggable module/port, or
facility that has raised an alarm” procedure in this document.
Record the 63xE1 or PDH gateway circuit pack, slot, and port number.
The simplest configuration involves an E1 between two 63xE1 circuit packs
or two Trans Mux circuit packs. For simplicity, we call the network element
with the 63xE1 or Trans Mux circuit pack that raised the alarm NE B, and the
source network element NE A in this procedure.
NE A NE B
E1 E1
Source
network element E1 circuit pack
raising the alarm
For Trans Mux applications, the configuration can be quite complex, as

shown in the example configuration below. Note that some configurations can
contain non-6500 equipment. For example, in the electrical network cloud,
there can be other equipment providing E1 to DS3 multiplexing (and vice
versa) or transport of DS3 or E3 traffic. Furthermore, there can be additional
optical hops between the network elements, and some equipment can be
located in the same network element. For example, the 63xE1 and Trans Mux
circuit packs can reside in the same network element, or the 24xDS3/E3 or
24xDS3/EC-1 circuit packs and Trans Mux circuit packs can reside in the
same NE; it is even possible to have 63xE1, Trans Mux, and 24xDS3/E3
circuit packs all in the same network element.


E1 Transmit alarms
Step Action
The diagram below shows the direction of E1 traffic from NE A to NE F, and

helps show the alarm-clearing procedure for E1 transmit alarms raised at
NE F (on 63xE1) and/or NE E (on Trans Mux).
NE C NE D
NE A NE B DS3E3x24 Electrical DS3E3x24 NE E NE F
63xE1 Tmux or Network or Tmux 63xE1
DS3EC1x24 DS3EC1x24
3 For E1 on an optical/front electrical shelf, if the signal impedance is 75 ohm,

confirm that 120 ohm converter modules are not present for the indicated
circuit pack. If the signal impedance is 120 ohm, confirm that 120 ohm
converter modules are present for the indicated circuit pack (for E1 on a
Metro front electrical shelf, use either 75 ohm or 120 ohm I/O modules).

Tx AIS step 5
Tx Loss of Frame or Tx Loss of Multiframe step 9
5 Retrieve the cross-connects. Refer to the “Retrieving path cross-connects”

323-1851-320.
6 Look for cross-connects provisioned for the E1 raising the alarm. If there are
no cross-connects for the E1, verify that there are no missing cross-connects.
If there are no missing cross-connects, and the E1 is in service (IS) without
connections, place the E1 facility out of service (OOS). If there are missing
cross-connects, provision the required cross-connects. Refer to the “Adding
a 2WAY, 1WAY, 2WAYPR, 1WAYPR, or 2WAYDPR path cross-connect”
323-1851-320.
7 Determine where the E1 signal enters the network. Refer to the path
connections management procedures in Part 1 of Configuration - Bandwidth
and Data Services, 323-1851-320. If it is a OC-n/STM-n signal, verify the
connecting equipment and ensure that it is correctly transmitting a E1 signal.


E1 Transmit alarms
Step Action

9 Check that the frame format of the E1 facility is provisioned correctly (from
company records). For E1 facilities on Trans Mux circuit packs, check that the
frame format of the DS3 or E3 is provisioned correctly (from company
records).
If the frame format is Then go to
incorrect step 10
correct step 13
10 Edit the frame format. Refer to the “Editing facility parameters” procedure in
12 Record the circuit pack and the network element of the E1 facility of the
source (NE A).
13 On NE A, check that the frame format is provisioned correctly (from company
records).
If the frame format of the NE A is Then go to
incorrect step 14
correct step 16
14 Edit the frame format of the NE A. Refer to the “Editing facility parameters”
323-1851-310.
16 If the circuit pack you identified as the source in step 12 is Then go to

a protected 63xE1, Trans Mux or PDH gateway circuit pack step 17
an unprotected 63xE1, Trans Mux or PDH gateway circuit pack step 19


E1 Transmit alarms
Step Action
17 Manually switch the traffic of the 63xE1, Trans Mux or PDH gateway circuit
pack on NE A to the protection circuit pack. Refer to the “Operating a
Operating, 323-1851-310.
Attention: Ensure the protection circuit pack is not carrying traffic for another
working module/circuit pack before you switch traffic from a working
module/circuit pack to the protection module/circuit pack. This note does not
apply to Trans Mux circuit packs.
18 Wait 30 seconds.
cleared the working circuit pack you identified as the
source in step 12 is faulty. Go to step 19.
not cleared release the protection switches. Go to step 23.
20 On NE A, replace the 63xE1, Trans Mux or PDH gateway circuit pack you
identified as the source in step 12. Refer to the equipment replacement
323-1851-545.
21 If applicable, release the manual protection switch you performed in step 17.
23 If the E1 circuit pack you identified in step 2 as the origin of Then go to

the alarm on NE B is
a protected 63xE1, Trans Mux or PDH gateway circuit pack step 24
an unprotected 63xE1, Trans Mux or PDH gateway circuit step 26
pack


E1 Transmit alarms
Step Action
24 Manually switch the circuit pack you identified in step 2 as the circuit pack
raising the alarm, to the protection circuit pack. Refer to the “Operating a
Operating, 323-1851-310.
Attention: Ensure the protection circuit pack is not carrying traffic for another
working circuit pack before you switch traffic from a working circuit pack to the
protection circuit pack. This note does not apply to Trans Mux circuit packs.
25 Wait 30 seconds.
cleared the working circuit pack you identified as the
source is faulty. Go to step 26.
26 On NE B, replace the 63xE1, Trans Mux or PDH gateway circuit pack you
identified in step 2 as the circuit pack raising the alarm. Refer to the
27 If applicable, release the manual protection switch you performed in step 24.
support group.
—end—

Procedure 4-100
EC-1 Receive alarms
Use this procedure to clear alarms associated with EC-1 receive signals.
AIS (EC-1)
Alarm ID: 95
Probable cause
This alarm is raised when the network element detects an alarm indication
signal (AIS) on the EC-1 traffic stream at the input.
Impact
Excessive Pointer Adjustments (EC-1)

Alarm ID: 632
Probable cause
This alarm is raised when the payload frequency drift of the incoming EC-1
signal exceeds 20 ppm.
Excessive pointer adjustments can indicate a problem with network

synchronization that, if not corrected, can cause errors when the signal is
demultiplexed.
Impact
Loss of Frame (EC-1)

Alarm ID: 94
Probable cause
The 24xDS3/EC-1 circuit pack is faulty or a signal is being transmitted from
the adjacent network element without properly formatted frames.
Impact


EC-1 Receive alarms
Loss of Signal (EC-1)

Alarm ID: 93
Probable cause
• the EC-1 input cable is disconnected or misconnected from the I/O module
or along the path from the other end
• the EC-1 signal stops transmitting from the adjacent network element
• the I/O module is not fully inserted and locked into position
• the I/O module was removed
• the 24xDS3/EC-1 circuit pack is faulty
Impact
RFI (EC-1)
Alarm ID: 99
Probable cause
This alarm is raised when the remote network element detects a faulty EC-1
signal from the network element and returns a remote fault indicator (RFI)
signal in the SONET/SDH overhead.
Impact
Signal Degrade (EC-1)

Alarm ID: 328
Probable cause
This alarm is raised when the 24xDS3/EC-1 circuit pack is faulty or the EC-1
signal is degraded. Signal quality is measured using the bit interleaved parity
(BIP) information from the B2 byte of the line overhead. This alarm is raised
when the BIP error rate is above the 1E-6 threshold.
Impact
Minor, service-affecting (m, SA) alarm


EC-1 Receive alarms
Signal Fail (EC-1)

Alarm ID: 639
Probable cause
This alarm is raised when the received signal is degraded to the point where
it is unusable.
One of the following conditions causes this alarm:

• excessive attenuation
• improper connector seating
• transmit laser degrade
Impact
Prerequisites
323-1851-545
Step Action
1 If the original alarm is Then go to

RFI step 2
otherwise step 3
2 Verify the remote system at the other end of the EC-1 and clear any alarms
you find.
in this document.


EC-1 Receive alarms
Step Action

RFI step 7
otherwise step 8
position. Go to step 8.
7 Use an EC-1 test set to determine if a valid EC-1 signal is on the transmit and
receive sides of the cross-connect for that facility.
If a valid signal is Then
on the transmit side and RFI is the problem is in the source system. Perform
on the receive side troubleshooting on the source system
according to your company procedures.
not on the transmit side and go to step 10
RFI is not on the receive side
8 Use an EC-1 test set to determine if a valid EC-1 signal is on the EC-1
• If there is AIS, excessive pointer adjustment, Loss of frame, Loss of
Signal, RFI, or Signal Degrade (contains B2 errors) the problem is in the
EC-1 source and the shelf is reporting a valid condition. Perform
• If there is no AIS, excessive pointer adjustment, Loss of frame, Loss of
Signal, RFI, or Signal Degrade, go to step 9.
otherwise step 11
10 If the alarm does not clear, inspect the 24xDS3/EC-1 cabling and physical
connections. The connection may be loose or damaged. Repair any damage.
11 Operate a manual switch on the 24xDS3/EC-1 circuit pack raising the alarm.
Refer to the “Operating a protection switch” procedure in Part 2 of


EC-1 Receive alarms
Step Action
12 Wait 30 seconds. If the alarm clears, the working 24xDS3/EC1 circuit pack is
faulty. Replace the circuit pack that is detecting the alarm. Refer to the
“Replacing the 24xDS3/EC1 or 24xDS3/E3 circuit pack” procedure in Fault
support group.
—end—

Procedure 4-101
Equipment Configuration Mismatch
Alarm ID: 970
Probable cause
This alarm is raised against regular flow cooling fans when the Minimum
provisioned cooling shelf attribute (minimum shelf-cooling required) is set to
“High flow”, or when circuit packs requiring high flow cooling (such as
SuperMux, 20G L2SS, 100G OCLD, 100GE OCI, 40G+ CFP OCI, 10x10G
MUX, 10x10GE MUX, 40G UOCLD, 40G OCLD, Wavelength-Selective 40G
OCLD, 40G XCIF, 40G OCI, 40/43G OCI, or 40G MUX OCI circuit packs
equipped in a 14-slot 6500 shelf) are provisioned. This alarm masks all alarms
raised against a given fan, except the Fan Failed alarm. Refer to the
“Equipment provisioning validation based on shelf cooling capacity” section in
“Node Information” chapter of Administration and Security, 323-1851-301 for
further details.
This alarm is raised against a Power Input Card that does not support the shelf
powering configuration (or current rating) specified by the Provisioned shelf
current shelf attribute (provisioned shelf power configuration and feeder
amperage). The alarm is also raised against the Power Input Card with the
lower amperage capacity, in the case of two mismatched Power Input Cards.
Refer to the “Equipment provisioning validation based on shelf power
capacity” section in Administration and Security, 323-1851-301 for further
details.
For the 7-slot optical Type 2 shelf, this alarm is raised against a Power Input
Card that is in the incorrect slot or is not compatible with the configuration
specified by the Provisioned shelf current shelf attribute or when DC and
AC Power Input Cards are mixed in the shelf. For equipping rules for power
modules on the 7-slot Type 2 shelf, refer to Planning - Ordering Information,
323-1851-151.
This alarm is raised if a Type 3 high flow cooling fan module (NTK507LS or
NTK507MS) is inserted in a 14-slot packet-optical shelf that is also equipped
with Power Input Cards that are not compatible with Type 3 fans. Unless
equipped in the center fan slot (Fan-2), Type 3 fans will not energize or light
any LEDs unless there is a compatible Power Input Card in the shelf. The
2x50A Power Input Card (NTK505ES) is compatible with Type 3 fans.
This alarm is also raised when mixing Type 3 and other cooling fan module
types in 14-slot packet-optical shelf. This alarm will clear once the shelf is
equipped with three compatible fans (either three Type 3 fans or three other
matching fans).


When an SP restart is performed on 14-slot packet-optical shelf and it is

equipped with a mix of Type 3 and other fan types (there is a mismatch
between at least two fans), this alarm is raised against all the three fans.
Impact
Against fans
Critical, service-affecting (C, SA) alarm if two or more fan alarms exist
Major, non-service-affecting (M, NSA) alarm if one fan alarm exists
Against Power Input Cards

Prerequisites
Step Action
DANGER
Risk of eye injury

fans step 2
Power Input Cards step 9
2 If the shelf is Then go to

provisioned with circuit packs requiring high flow cooling, or step 3
such circuit packs are physically present in the shelf
not provisioned with circuit packs requiring high flow cooling, step 7
and no such circuit packs are physically present in the shelf
3 If the circuit packs requiring high flow cooling are Then go to

required step 4
not required step 6


Step Action
5 Replace any regular flow cooling fans or any Type 3 high flow cooling fans
with high flow cooling fans. Refer to the “Replacing a cooling fan module”
procedure in Fault Management - Module Replacement, 323-1851-545. Go
to step 14.
6 Deprovision and remove all equipment requiring high flow cooling. Refer to
the “Deleting a circuit pack, module, or SFP/XFP/DPO” procedure in Part 1
of Configuration - Provisioning and Operating, 323-1851-310. Go to step 7.
7 Change the fan to the regular flow fans. Refer to the “Replacing a cooling fan
module” procedure in Fault Management - Module Replacement,
323-1851-545.
9 Retrieve and record the Provisioned shelf current value, and the inventory
information for the Power Input Cards. Refer to the “Displaying node
information” procedure in Administration and Security, 323-1851-301.
10 If the equipped Power Input Cards are the same type, set the Provisioned
Shelf Current to a setting that is compatible with the Power Input Cards and
their configuration but does not exceed the current rating of the feeders or of
any equipped fuses (for the case of fused Power Input Cards). Refer to the
"Determining the provisioned shelf current" procedure in Administration and
Security, 323-1851-301.
12 Remove from the shelf the alarmed Power Input Card or the Power Input
Card that is not compatible with the required Provisioned Shelf Current
setting. Refer to the “Replacing the Power Input Card A or B” procedure in
The “Circuit Pack Missing” alarm is raised for that Power Input Card, and the
“Equipment Configuration Mismatch” alarm clears.
13 Insert a replacement Power Input Card into the shelf. Ensure that the
equipped Power Input Cards are compatible with the retrieved Provisioned
Shelf Current setting in step 9, and that all equipped Power Input Cards have
the same amperage capacity (which is greater than or equal to the current
associated with the Provisioned shelf current setting).
support group.
—end—

Procedure 4-102
Equipment OOS with Subtending Facilities IS
Alarm ID: 625
Probable cause
The 63xE1, 24xDS3/E3, 24xDS3/EC-1 or 16xSTM-1e working circuit pack in
a 1:N protection configuration; or the 20G L2SS, L2SS, PDH gateway or 48
Channel Trans Mux (portless) working circuit pack in 1+1 protection
configuration was taken out-of-service while some facilities are in-service.
Attention: The alarm is usually only raised during maintenance when the
63xE1, 24xDS3/E3, 24xDS3/EC-1, 16xSTM-1e, 20G L2SS, L2SS or PDH
gateway working circuit pack is being replaced. For the 63xE1, 24xDS3/E3,
24xDS3/EC-1, 16xSTM-1e, 20G L2SS, L2SS or PDH gateway working
circuit pack, the user is allowed to take the circuit pack out-of-service without
first taking all the facilities out-of-service (as required on other traffic circuit
packs).
If the 63xE1, 24xDS3/E3, 24xDS3/EC-1 or 16xSTM-1e working circuit pack is

in a 1:N protection group or if the 20G L2SS, L2SS or PDH gateway working
circuit pack is in a 1+1 protection group, taking the circuit pack out-of-service
will initiate a protection switch.
Impact
Critical, service-affecting (C, SA) alarm for a 63xE1, 24xDS3/E3,
24xDS3/EC-1, 16xSTM-1e, 20G L2SS, L2SS, PDH gateway or 48 Channel
Trans Mux working circuit pack with cross-connects if switch to protection
circuit pack fails
Minor, non-service-affecting (m, NSA) alarm for a 63xE1, 24xDS3/E3,

24xDS3/EC-1, 16xSTM-1e, 20G L2SS, L2SS or PDH gateway circuit pack
without cross-connects or a 63xE1, 24xDS3/E3, 24xDS3/EC-1, 16xSTM-1e,
20G L2SS, L2SS, PDH gateway or 48 Channel Trans Mux circuit pack with
cross-connects and switch to protection circuit is successful


Equipment OOS with Subtending Facilities IS
Step Action
1 If the 63xE1, 24xDS3/E3, 24xDS3/EC-1, 16xSTM-1e, 20G L2SS, L2SS,

PDH gateway or 48 Channel Trans Mux circuit pack is being replaced,
complete the replacement procedure and then put the circuit pack in-service.
Refer to the “Changing the primary state of a circuit pack, module, or
SFP/XFP/DPO” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
support group.
—end—

Procedure 4-103
Equipment Reconfiguration In Progress
Alarm ID: 1345
Probable cause
This alarm is raised to indicate the equipment reconfiguration is in progress.
Impact
Step Action
1 Perform a warm restart the active shelf processor to complete the

reconfiguration. Wait five minutes for it to restart. Refer to the “Restarting a
circuit pack or shelf processor” procedure in this document.
support group.
—end—

Procedure 4-104
Error alarms (ETH, ETH10, ETH40G, ETH100G, FLEX,
WAN, ETTP)
Use this procedure to clear alarms associated with the error alarms on the
4xGE, 1x10GE EPL, 24x10/100BT, L2SS, PDH gateway, RPR, 100G OCI,
and SuperMux circuit packs.
Excessive Error Ratio (ETH, ETH10, ETH40G, ETH100G, ETH100, FC800,

FC1200, FLEX, WAN, ETTP)
Alarm ID: 346, 352, 364, 823, 841, 1257, 1298, 1454
Probable cause
• an ETH or WAN facility of a 4xGE, 20G L2SS, L2SS, PDH gateway, or
RPR circuit pack
• an ETH10G or WAN facility of a 1x10GE EPL or 10x10G MUX circuit pack
• an ETH100 or WAN facility of a 24x10/100BT circuit pack
• a WAN facility of a SuperMux circuit pack in GFP-T mode
• an ETH, ETH100, or WAN facility of a SuperMux circuit pack in GFP-F
mode
• FC1200 facility of 2x10G OTR, 4x10G OTR, and 40G MUX OCI circuit
pack
• ETH10G facility of the 2x10G OTR and 4x10G OTR circuit pack
• an ETTP facility of 16XOTNFLEX, 4x10G MUX, 4x10G PKT I/F, and 40G
OCI circuit packs
This alarm is raised against an ETH, ETH10, ETH100 facility when at least 20
percent of the received frames are errored each second for three consecutive
seconds and is raised against a WAN facility when one of the following
conditions occurs:
• for GFP-F encapsulation, at least 20% of the received frames are errored
each second for three consecutive seconds
• for GFP-T encapsulation, at least 20% of the received superblocks are
errored each second for three consecutive seconds
For ETH10G facilities on the 10x10G MUX circuit pack, this alarm is raised
when the client 64B/66B Rx interface is detecting a BER greater than or equal
to 1E-4. This occurs when 16 or more invalid sync headers are detected by
the 64B/66B Rx interface within the current 125 µs period.


Error alarms (ETH, ETH10, ETH40G, ETH100G, FLEX, WAN, ETTP)
For the ETH40G facility on the 40G+ CFP OCI, this alarm is raised when 97
invalid 66-bit sync headers are detected within a 1.25 ms window. The high
BER state is exited once there are less than 97 invalid sync headers in the
same window.
For the ETH100G facility on the 100G OCI, this alarm is raised when 97
invalid 66-bit sync headers are detected within a 500 s window. The high
BER state is exited once there are less than 97 invalid sync headers in the
same window.
For the WAN facility on the 4xGE,1x10GE EPL, 24x10/100BT circuit packs,
the alarm is raised when these circuit packs are interconnected to another
circuit pack with an FCS (Frame CheckSum) parameter value that does not
match the provisioned value on the alarmed circuit pack. The alarm clears
when the FCS parameter value is changed so that both interconnected circuit
packs have matching values.
For FC1200 facility on the 2x10G OTR, 4x10G OTR, or 40G MUX OCI circuit
pack, this alarm is raised when the client 64B/66B Rx interface is detecting a
BER greater than or equal to 1E-3. This occurs when 16 or more invalid sync
headers are detected by the 64B/66B Rx interface within the current 125 µs
period.
The alarm clears when these conditions do not occur for 10 consecutive
seconds.
This alarm is also raised against a PDH WAN (DS1, DS3, E1, or E3) when the
PDHVLI setting is mismatched between two ends.
Impact
Major, service-affecting (M, SA) alarm if not protected
Signal Degrade (ETH, ETH100, ETH10G, WAN)

Alarm ID: 345, 351, 822, 866
Probable cause
• an ETH or WAN facility of a 4xGE, 20G L2SS, L2SS, PDH gateway, or
RPR circuit pack
• an ETH10G or WAN facility of a 10x10G MUX circuit pack
• an ETH10G or WAN facility of a 100G OCI circuit pack
• an ETH10G or WAN facility of a 1x10GE EPL circuit pack

• an ETH100 or WAN facility of a 24x10/100BT circuit pack


• a WAN facility of a SuperMux circuit pack in GFP-T mode

• an ETH, ETH100, or WAN facility of a SuperMux circuit pack in GFP-F
mode
This alarm is raised against an ETH, ETH100, or ETH10G facility when at

least 1% of the received frames are errored each second for three
consecutive seconds and is raised against WAN facility when one of the
following conditions occurs:
• for GFP-F encapsulation, at least 1% of the received frames are errored
each second for three consecutive seconds
• for GFT-T encapsulation, at least 1% of the received superblocks are
errored each second for three consecutive seconds
The alarm clears when these conditions do not occur for 10 consecutive
seconds.
Impact
Minor, service-affecting (m, SA) alarm if not protected
Prerequisites
network element
• if required, obtain a supported SFP optical transceiver module
323-1851-545
Step Action
1 Verify if there are alarms of higher order from the alarm hierarchy. Refer to
chapter 3 of this document. Clear any alarms of higher order on the hierarchy
first using the appropriate procedures.
3 From the Class field in the Active Alarms application, determine if the alarm
is raised against an Ethernet or WAN facility.


Step Action
4 If this alarm is raised against Then go to

an Ethernet or ETTP facility step 5
a WAN facility step 18
Alarm raised against an Ethernet facility

CAUTION
Ensure that the correct module is identified. Removing
the wrong optical fiber causes a traffic loss on an
in-service facility.
CAUTION
Laser radiation is present on the optical fiber. Do not
look into the optical fiber.
6 Use the optical power meter to measure the receive power at the LAN port.
For information about technical specifications (minimum and maximum
receive optical power) for the SFPs supported with the 4xGE, 1x10GE EPL,
24x10/100BT EPL with 8xSFP, 20G L2SS, L2SS, PDH gateway, and
SuperMux circuit pack, refer to the “Technical specifications” chapter in Part
3 of 6500 Planning, NTRN10CF.
7 If the receive power at the LAN port is Then go to
below the minimum receive optical power step 8
between the minimum and maximum receive optical power step 12
above the maximum receive optical power step 13
Receive power is below the minimum receive optical power

8 Decrease the local attenuation, if equipped, to try to increase the receive
power to a value above the minimum receive optical power (but below the
maximum receive optical power).
9 the adjusted receive power is Then go to
still below the minimum receive optical power step 10
within range (between the minimum and the maximum step 12
receive optical power)


Step Action
10 Remove the Tx optical fiber from the far-end subtending client equipment.
11 Measure the transmit power at the far-end subtending client equipment.
• If the transmit power of the far-end equipment is above the minimum
launch power, the optical fiber attenuation is too high, the optical fiber
connections are dirty, or the optical fiber is damaged.
• If the transmit power of the far-end equipment is below the minimum
launch power, there is a problem with the far-end equipment.
Use your company procedure to determine and clear the problem, then go to
step 14.
Receive power is between the minimum and the maximum receive optical power
12 Clean all connections at both ends of the optical fiber link following your
company standards and re-attach the optical fibers.
Go to step 14.
Receive power is above the maximum receive optical power
13 Add the necessary attenuation to reduce the receive power to a value
between the minimum and maximum receive optical power.
Determining if the alarm cleared
not cleared replace the SFP corresponding to the facility raising
the alarm. Refer to the “Replacing an
SFP/SFP+/XFP/CFP module” procedure in Fault

not cleared replace the 4xGE, 1x10GE EPL, 24x10/100BT,
L2SS, or PDH gateway, or SuperMux (in GFP-F
mode) circuit pack reporting the alarm. Refer to
the equipment replacement procedures in
chapter 2 of Fault Management - Module
16 Clean and re-attach the optical fibers. Refer to the cleaning connectors
support group.


Step Action
Alarm raised against a WAN facility

18 Retrieve the performance monitoring counts for the STS/VC paths connected
to the WAN facility to determine if the path ES counts are increasing.
19 If the path ES counts are increasing, use the appropriate alarm clearing
procedure to clear any STS/VC path alarms on the interface circuit pack
connected to the 4xGE, 1x10GE EPL, 24x10/100BT, 20G L2SS, L2SS, PDH
gateway, RPR, or SuperMux circuit pack. The STS/VC path alarms include
Signal Degrade and Excessive Error Rate alarms.
20 For PDH WANs (DS1, DS3, E1, or E3), verify the PDHVLI setting at both
ends of the link. If there is a mismatch, correct the PDHVLI setting. Refer to
the “Editing facility parameters” procedure in Part 1 of Configuration -
support group.
—end—

Procedure 4-105
Error alarms (OC/STM, STS/HO VC, and VT/LO VC)
Use this procedure to clear alarms associated with the errors on the OC/STM
line, STS/HO VC path, and VT/LO VC path.
Attention: By the nature of the SONET/SDH protocol definition, the

detection accuracy of BER diminishes with higher error rates. Path BER
detection accuracy further diminishes with high-order payload sizes greater
than STS-1/VC-3 and low-order payload sizes greater than VT1.5/VC11.
The diminished accuracy is due to the Bit Interleaved Parity (BIP) scheme
and associated overhead bytes used to check the previously received data
block for BIP errors. The B1, B2, B3 and V5 bytes are not ideal for
communicating more than one bit error per associated data block. At the
equivalent BER corresponding to one or more bit errors per block, the effects
of error cancellation and error count saturation become more apparent. For
example, a path BER threshold setting of 1e-03 on an STS-3c/VC-4 payload
can be tripped by an incoming BER less than 1e-03 since the BIP error
signature of some error distributions between 1e-03 and 1e-05 are
indistinguishable from an actual 1e-03 BER.
Signal Degrade (OC/STM, STTP, STS/HO VC and VT/LO VC)

Alarm ID: 3, 9, 39, 54, 65, 120, 151, 244, 271, 281, 464, 470, 1103, 1465, 1692
Probable cause
This alarm is raised when the received OC/STM, STTP, STS/HO VC, or
VT/LO VC signal is significantly degraded.
One of the following conditions can cause this alarm:

• dirty optical fibers
• dirty connectors
• threshold set too high
• incorrect or faulty cabling at source end


For the (2+8)OC-n/STM-n 20G circuit packs, the line signal degrade threshold
and the Excessive Bit Error (EBER) threshold for OC-n/STM-n facilities are
defined on a per line facility basis. The OC-n/STM-n line signal degrade
threshold is editable to 5, 6 (default), 7, 8, 9. These values are explicitly 10E-5,
10E-6 (default), 10E-7, 10E-8, and 10E-9 respectively. The OC-n/STM-n line
EBER threshold is editable to 3 (default), 4, 5. These values are explicitly
10E-3 (default), 10E-4 and 10E-5 respectively.
For MSPP services, this alarm can also be raised momentarily on the far-end
network element when you reinsert the OC-3 circuit pack connected to DSM.
Releasing the terminal loopback on an OC/STM facility can cause a transient

line Signal Degrade alarm to raise and clear. This will only be noticed if the
facility is placed back in service before alarm clearing.
This alarm is raised on the OC-192/STM64 facilities when using the ETH10G
to GFP to STS-192c/STM-64c to OTU2 mapping.
This alarm is raised on the OC-n/STM-n client ports with provisionable

thresholds of the following Broadband circuit packs:
• 2x10G OTR (NTK530PG/NTK530PM)
• 4x10G OTR (NTK530QA/NTK530QM)
• 4x10G MUX OCI (NTK525CF)
• 10x10G MUX OCI (NTK529BB)
• 40G Multi-Protocol OCI (NTK529SJ)
OC-n/STM-n thresholds can be user-provisioned to a value in the range of

1E-5 to 1E-9. The default value is 1E-6.
For 2x10G OTR circuit packs, this alarm can be raised when there is a
OC-192/STM-64 Out Of Frame (OOF) condition at low alarm thresholds
(1E-9).
Impact
OC/STM
Minor, service-affecting (m, SA) alarm for a UPSR/SNCP configuration with
cross-connects
Minor, service-affecting (m, SA) alarm, if active 1+1/MSP linear or
Minor, non-service-affecting (m, NSA) alarm, if inactive 1+1/MSP linear,
Minor, non-service-affecting (m, NSA) alarm, if on an inactive


BLSR/MS-SPRing/HERS
Minor, service-affecting (m, SA) alarm, if on an active
BLSR/MS-SPRing/HERS
The alarm status is service-affecting on a ring system because the OC/STM

line is not protected. The system cannot determine if path protection will be
successful because that occurs where the path terminates. If the protection
path is available, the path-terminating network element switches to that path
to protect traffic.
STS/HO VC (MSPP services)

Minor, service-affecting (m, SA) alarm, if on active path
Minor, non-service-affecting (m, NSA), if on inactive path in a UPSR/SNCP
configuration

to protect traffic.
VT/LO VC (MSPP services)

Minor, non-service-affecting (m, NSA), if on inactive path in a UPSR/SNCP
configuration
STTP
Minor, non-service-affecting (m, NSA), if on inactive path
Signal Fail (OC/STM MSPP)

Alarm ID: 38, 150, 897, 1691
Probable cause
This alarm is raised when the received OC/STM signal is degraded to the
point where it is unusable, and the circuit pack is unable to detect the framing
bytes in the received signal.
This alarm is also raised on the OC-192/STM64 when using the ETH10G to
GFP to STS-192c/STM-64c to OTU2 mapping.
One of the following conditions causes this alarm:




This alarm is raised on the OC-n/STM-n client ports with provisionable

thresholds of the following Broadband circuit packs:
• 2x10G OTR (NTK530PG/NTK530PM)
• 4x10G OTR (NTK530QA/NTK530QM)
• 4x10G MUX OCI (NTK525CF)
• 10x10G MUX OCI (NTK529BB)
• 40G Multi-Protocol OCI (NTK529SJ)
OC-n/STM-n thresholds can be user-provisioned to a value in the range of

1E-3 to 1E-5. The default value is 1E-3.
Impact
Critical, service-affecting (C, SA) alarm for a UPSR/SNCP configuration with
cross-connects
Critical, service-affecting (C, SA) alarm, if active 1+1/MSP linear, or
unprotected with cross-connects)
Critical, service-affecting (C, SA) alarm if on an active
BLSR/MS-SPRing/HERS
Minor, non-service-affecting (m, NSA) alarm if inactive 1+1/MSP linear,
Minor, non-service-affecting (m, NSA) alarm for a non-active
BLSR/MS-SPRing/HERS
The network element cannot clear a Loss of Signal alarm until a framed
OC-n/STM-n signal is detected. The first time an optical fiber/cable is
disconnected, the Loss of Frame alarm clears and a Loss of Signal alarm is
raised that will not change back to Loss of Frame when the optical fiber/cable
is re-attached.
Excessive Error Rate (STS/HO VC and VT/LO VC)

Alarm ID: 15, 53, 63, 118, 127, 193, 242, 273, 463, 469
Probable cause
This alarm is raised when the received STS/HO VC or VT/LO VC path is
degraded to the point where it is unusable.
This alarm is caused by one of the following conditions:




• improper connection provisioned (STS/HO VC signal received is at a
different rate to the provisioned STS/HO VC signal)
Impact
to protect traffic.
STS/HO VC
Major, service-affecting (M, SA) alarm, if on active path
Minor, non-service-affecting (m, NSA) alarm, if on inactive path in a
UPSR/SNCP configuration
VT/LO VC
Major, service-affecting (M, SA) alarm, if on active path
Minor, non-service-affecting (m, NSA) alarm, if on inactive path in a
UPSR/SNCP configuration
Prerequisites
• have the optical fiber/cable connection information (that is, how the circuit
packs on each network element connect to other network elements)
network element
323-1851-545
Step Action
1 Verify if there are alarms of higher order from the alarm hierarchy. Refer to
chapter 3 of this document. Clear any alarms of higher order on the hierarchy
first using the appropriate procedures.


Step Action
in this document.
4 Use the optical fiber/cable connection information to identify the transmit and
receive sites of the alarmed signal.
5 Log into the remote network element at the transmit end.
If you cannot log in remotely from the local network element, you need to
have someone present at the remote site.
6 Retrieve all alarms at the transmit end. Clear any higher order alarms using
the appropriate procedure. The following alarms can be ignored:
• RFI/RDI alarm if the local alarm is Signal Degrade or Signal Fail
• Excessive Error Rate alarm if the local alarm is Excessive Error Rate
7 Retrieve the SDTH and compare the SDTH with the network diagram. Refer
to the “Displaying node information” procedure in Administration and
Security, 323-1851-301.
If the provisioned SDTH Then
matches the SDTH on the go to step 9
network diagram
does not match the SDTH on edit the SDTH as required. Refer to the
the network diagram “Editing the nodal system parameters”
procedure in Administration and Security,
323-1851-301.
Go to step 9.
8 Ensure that the cross-connect signal rate on the entire path matches the
optical fiber/cable connection information. Refer to the “Retrieving path
Services, 323-1851-320.


Step Action
10
CAUTION
Disabling ALS causes the laser to be permanently
active. Laser radiation is present on the optical fiber. Do
not look into the optical fiber.
If enabled, disable ALS at both ends. Refer to the “Editing facility parameters”
323-1851-310.
optical interface step 13
STM-1e step 19
13
CAUTION
Ensure that the correct module is identified. Removing
the wrong optical fiber/cable drops all traffic on the local
shelf.
CAUTION
Laser radiation is present on the optical fiber. Do not
look into the optical fiber.
Remove the optical fiber from the circuit pack raising the alarm and use the
optical power meter to measure the receive power.
14 If the power is Then go to
below the receiver sensitivity for this circuit pack step 15
above the receiver sensitivity for this circuit pack step 18
For information about circuit pack technical specifications, Refer to the

“Technical specifications” chapter in Part 3 of 6500 Planning, NTRN10CF.
Power is below the receiver sensitivity
15 Adjust the local attenuation, if equipped, to try to get the receive power above
the receiver sensitivity level.


Step Action
16 If the receive power after adjustment is Then go to

still below the receiver sensitivity step 17
above the receiver sensitivity but below step 18
the maximum receiver power
17 Remove the Tx optical fiber from the far-end circuit pack and measure the
transmit power at the far end.
If the transmit power at the Then
far end is
above the launch power the optical fiber attenuation is too high, the
(minimum) optical fiber connections are dirty, or the optical
fiber is damaged. Use your company procedure
to determine and clear the problem.
Go to step 19.
below the launch power if the circuit pack at the transmit end supports
(minimum) SFP/SFP+/XFP/CFP or DPO module, replace
the module that corresponds to the facility
raising the alarm. Refer to the “Replacing an
SFP/SFP+/XFP/CFP module” or “Replacing an
OC-48/STM-16 DWDM plug-in optics (DPO)
module” procedure in Fault Management -
if the circuit pack at the transmit end does not
support SFPs/DPOs, replace the required circuit
pack at the transmit end. Refer to the equipment
replacement procedures in chapter 2 of Fault
Management - Module Replacement,
323-1851-545.
Go to step 19.
Power is above the receiver sensitivity

18 Clean all connections at both ends of the optical fiber link following your
company standards and re-attach the optical fibers.


Step Action
Determining if the alarm has cleared

not cleared if the circuit pack supports SFP/SFP+/XFP/CFP
or DPO module, replace the module that
corresponds to the facility raising the alarm. Refer
to the “Replacing an SFP/SFP+/XFP/CFP
module” or “Replacing an OC-48/STM-16 DWDM
plug-in optics (DPO) module” procedure in Fault
Management - Module Replacement,
323-1851-545. Clean and re-attach both optical
fibers. Refer to the cleaning connectors
procedures in chapter 7 of Part 2 of Installation,
323-1851-201.

not cleared replace the circuit pack reporting the alarm. Refer
to the equipment replacement procedures in
chapter 2 of Fault Management - Module
Replacement, 323-1851-545. Clean and re-attach
both optical fibers. Refer to the cleaning
connectors procedures in chapter 7 of Part 2 of
Installation, 323-1851-201.
21 For optical interface, if ALS was disabled in step 10, enable the ALS at both
the near end and far end. Refer to the “Editing facility parameters” procedure
support group.
—end—

Procedure 4-106
ESI alarms
Use this procedure to clear alarms associated with ESI-A or ESI-B.
AIS (ESI)
Alarm ID: 104, 111
Probable cause
This alarm is raised when a XC circuit pack detects an AIS on the incoming
ESI timing reference signal. The upstream equipment generates an AIS signal
to tell downstream equipment that a failure occurred. This alarm indicates that
the ESI source (external clock source equipment) for this shelf has a failure.
This is not applicable to a 2 MHz ESI signal.
Impact
The ESI source is not available to the shelf. If this is the active source, a timing
protection switch occurs if another source is provisioned and available.
Otherwise, the shelf enters timing holdover mode.
Loss of Frame (ESI)

Alarm ID: 103, 110
Probable cause
This alarm is raised when the XC circuit pack detects a loss of frame on the
incoming ESI timing reference signal.
This procedure assumes that the signal has been in service and is alarm free.
Ensure that frame provisioning for the shelf and ESI source (external clock
source equipment) is correct. This is not applicable to a 2 MHz ESI signal.
Impact
The ESI source is not available to the shelf. If this is the active source, a timing
protection switch occurs when another source is provisioned and available.
Otherwise, the shelf enters timing holdover mode.
Loss of Signal (ESI)

Alarm ID: 102, 108
Probable cause
This alarm is raised when the XC circuit pack cannot detect a signal on the
incoming ESI timing reference.
Impact


ESI alarms
The ESI source (external clock source equipment) is not available to the shelf.
If this is the active reference, a timing protection switch occurs when another
source is provisioned and available. Otherwise, the shelf enters timing
holdover mode.
Prerequisites
Step Action
2 Use an appropriate test set to determine if the ESI port has a valid DS1, E1,
or 2 MHz signal. The ESI ports are on the access panel of the shelf raising
the alarm. Refer to Figure 4-3 on page 4-273, Figure 4-4 on page 4-274, and
Figure 4-5 on page 4-275.
3 If Then go to
there is an AIS, LOF or LOS condition (AIS and loss of frame step 4
do not apply to a 2 MHz signal)
the signal is valid step 5
4 The problem is with cabling or the external clock source equipment and the
6500 shelf is reporting a valid condition. Perform troubleshooting on the
cabling or external clock source equipment according to your company
procedure.
5 Identify the timing generation references in use on the network element.
Refer to the “Retrieving synchronization data for a network element”
323-1851-310.
6 Look for the alarmed timing references for Timing Generation in the
Synchronization window and note the corresponding reference.
7 Go to the site. Look at the XC circuit packs in slots 7 and 8 of the 14-slot shelf
or slots 9 and 10 of the 32-slot shelf. Look at the synchronization status LED
(yellow circle) that corresponds to the reference you determined.


ESI alarms
Step Action
8 If the LEDs are not off on both XC circuit packs, reseat the circuit pack and
check the LEDs again. If The LEDs are on, replace the circuit pack that has
the synchronization status LED on. Refer to the equipment replacement
323-1851-545.
support group.
—end—

Figure 4-3
Synchronization interface pinout for SONET access panel (with connections for 8 external slots)
External 83 84 85 86 87 88 89 90 DTE ESI/ESO/ 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 Telemetry COLAN-A COLAN-B ILAN In ILAN Out COLAN-X
Slots Alarms A
1 8
Pin EIA/TIA 568B Function with
Colour Code 6500 shelf
RJ-45
1 White/Orange GND: Ground
Female 2
Socket Orange/White CP: Card Present
3 White/Green SCL: Serial Clock
4 Blue/White SDA: Serial Data
5 White/Blue 5VDC: Power
6 Green/White GND: Ground
7 White/Brown GND: Ground
8 Brown/White GND: Ground
Telemetry DB25 interface pinout

(female end)
13 12 11 10 9 8 7 6 5 4 3 2 1
25 24 23 22 21 20 19 18 17 16 15 14
Pin Signal Pin Signal Pin Signal Pin Signal Pin Signal
1 OUT3_NO 6 IN8 11 IN4 16 OUT4_COM 21 IN14
2 OUT1_NO 7 IN5 12 IN1 17 OUT2_COM 22 IN11
3 OUT4_NO 8 IN6 13 IN2 18 IN15 23 IN12
4 OUT2_NO 9 GND 14 OUT3_COM 19 IN16 24 IN9
5 IN7 10 IN3 15 OUT1_COM 20 IN13 25 IN10
DTE ESI/ESO/ 2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32 Tel

Alarms A
2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32
A ESI1_P N/C ESO1_P N/C ESI2_P N/C ESO2_P N/C GND N/C VIS_MN_ VIS_MJ_ VIS_CR_ AUD_MN_ AUD_MJ_ AUD_CR_
(TIP) (TIP) (TIP) (TIP) NO NO NO NO NO NO
C ESI1_N N/C ESO1_N N/C ESI2_P N/C ESO2_P N/C ACO N/C VIS_MN_ VIS_MJ_ VIS_CR_ AUD_MN_ AUD_MJ_ AUD_CR_
(RING) (RING) (RING) (RING) COM COM COM COM COM COM
E GND N/C GND N/C GND N/C GND N/C GND N/C VIS_MN_ VIS_MJ_ VIS_CR_ AUD_MN_ AUD_MJ_ AUD_CR_
(SHIELD) (SHIELD) (SHIELD) (SHIELD) NC NC NC NC NC NC

Figure 4-4
Synchronization interface pinout for SDH and SONET/SDH-J access panel
SDH Access Panel

A ESI B A ESO B ESI/ESO DTE Alarm Telemetry COLAN-A COLAN-B ILAN In ILAN Out COLAN-X
Synchronization interface pinout Pin Signal Pin Signal

(female end) 1 ESI1_N 6 ESI1_P
2 ESO1_N 7 ESO1_P
5 4 3 2 1 3 ESI2_N 8 ESI2_P
9 8 7 6 4 ESO2_N 9 ESO2_P
5 GND
SONET/SDH-J Access Panel

A Japan Clock B ESI/ESO ACO Visual / Audible Alarms Telemetry COLAN-A COLAN-B ILAN In ILAN Out COLAN-X
DTE
Pin Signal Pin Signal

2A 4A 6A 8A 2A ESI1_P 2C ESI1_N
4A ESI2_P 4C ESI2_N
6A ESO1_P 6C ESO1_N
2C 4C 6C 8C
8A ESO2_P 8C ESO2_N

Figure 4-5
Synchronization interface pinout for SDH-J access panel

Procedure 4-107
Event Log full
Alarm ID: 1523, 1524, 1525, 1526, 1632, 1633, 1634, 1635
Probable cause
This alarm is raised when the event log for the Integrated Test Set is full.
Impact
Prerequisites
Step Action
1 In the Test Configuration tab, click the Stop Test button to stop the test.
2 Click Clear Results to clear the test results.
3 Restart the test. Refer to the “Performing a test with the integrated test set”
323-1851-310.
support group.
—end—

Procedure 4-108
Excessive Input Power
Alarm ID: 1566
Probable cause
This alarm is raised on a Fixed Gain Amplifier (FGA) when the input power
exceeds maximum power (-5.5dBm) at the amp input.
For the MLA L-Band circuit pack, this alarm is raised against the AMP facility
if the input power exceeds -3 dBm, and clears if the power is -4 dBm or below
1 dB hysteresis.
Impact
Prerequisites
Step Action
1 Measure the input power to determine the amount of exceeding power

comparing to the maximum power (-5.5dBm for FGA, -3.0 dBm for L-band
MLA). Refer to the PM procedures in Fault Management - Performance
Monitoring, 323-1851-520.
2 Verify the fibering connections between modules and correct if needed.
Clean and then reconnect the input/output fibers, monitor ports fibers, and
connectors at the corresponding equipment. Refer to the cleaning connectors
3 Verify the provisioned parameters values of the alarmed AMP facility against
the EDP. Edit power levels as required. Refer to the “Editing facility
Operating, 323-1851-310.
4 Ensure that required pads are in place as per the system design.
support group.
—end—

Procedure 4-109
Facility Reconfiguration In Progress
Alarm ID: 1346
Probable cause
This alarm is raised to indicate facility reconfiguration is in progress
Impact
Step Action
1 Perform a warm restart the shelf processor to complete the reconfiguration.

Wait five minutes for it to restart. Refer to the “Restarting a circuit pack or
shelf processor” procedure in this document.
support group.
—end—.

Procedure 4-110
Facility Reconfiguration Required
Alarm ID: 1347, 1348, 1349, 1710
Probable cause
This alarm is raised to indicate the facility reconfiguration is required. The
alarmed facility is the 1+1 APS/MSP mate of a facility that has already been
upgraded.
Impact
Step Action
1 Perform the Line reconfiguration procedure on this facility to reconfigure it to

the same line rate as its 1+1 APS/MSP mate. Refer to the “Upgrading an
OCn/STMn facility line rate” procedure in Part 1 of Configuration -
support group.
—end—

Procedure 4-111
Fan Failed
Alarm ID: 224
Probable cause
This alarm is raised when a cooling fan module is:
• not fully inserted
• provisioned but is missing
• equipped but has failed
For cooling fan modules which have more than one integrated fan, the shelf
will raise the alarm when the module is not inserted in the fan slot or when one
or more of the integrated fans is in a failed state.
This alarm is also raised when a Type 3 high flow cooling fan module
(NTK507LS or NTK507MS) is inserted in a shelf other than the 14-slot
packet-optical shelf. Because they are not compatible with the shelf, Type 3
fans will not energize or light any LEDs.
Impact
In a 14-slot shelf, the alarm will be raised as Major, non-service-affecting (M,

NSA) when a single cooling fan module is missing or fails and it will escalate
to Critical, service-affecting (C, SA) if more than one cooling fan module is
missing or fails. For a missing or failed cooling fan module in the 2-slot, 7-slot
and 32-slot shelves, the alarm will be raised as Critical, service-affecting (C,
SA).
If a fan module is missing for more than 60 seconds the shelf's cooling may
be compromised and as a precaution, a “High Temperature” alarm will be
raised as described in this document.
Prerequisites


Fan Failed
Attention: Ensure that you have the right fan type. After removal of a
cooling fan module from a 14-slot or 32-slot shelf, the cooling fan module
must be replaced within one minute to prevent the circuit packs from
overheating due to insufficient airflow. If the cooling fan module is removed
from a 2-slot or 7-slot shelf, it must be replaced within 30 seconds. Have a
replacement fan module ready before removing the fan module.
Step Action
DANGER
Risk of eye injury
2 Select your next step.
If the alarm is raised on Then go to
a 2-slot, 7-slot, or 32-slot shelf step 3
otherwise step 10
3 Verify that the fan module is fully inserted.

4 Make any necessary adjustments.
cleared this procedure is completed
6 Loosen and remove the retaining screw(s).


Fan Failed
Step Action
7 Pull out the failed cooling fan module from the 2-slot, 7-slot, or 32-slot shelf.
CAUTION
Risk of personal injury
Use the handle on the front of the fan module to extract
it. Do not hold or carry the fan modules in a manner that
could cause detrimental contact to the fan blades
(which will stop rotating when power is disconnected
due to module extraction). You can provide extra
support for the 2-slot or 7-slot shelf fan modules by
holding the bottom of the fan module during extraction
and insertion. A fan module for a 32-slot shelf should be
handled by firmly grabbing the left and right sides
taking care not to touch the fan blades.
8 Insert the replacement module into the slot in the shelf until it is fully inserted
and then insert and tighten the retaining screw(s).
9 Verify that the fan green LED turns on. Go to step 24.
Removing the snap-on shelf cover or opening the hinged cover (if equipped)
10 On the hinged shelf cover, move the latches to the unlock position and rotate
the shelf cover to open the cover.
Removing the grill/air deflector (if equipped)
11 On the left side of the shelf, pull on the spring-loaded pins of the grill/air
deflector; at the same time pull the left end of the grill/air deflector just enough
to disengage the pin from the shelf hole.
12 On the right side of the shelf, pull on the spring-loaded pins of the grill/air
deflector; at the same time pull the right end of the grill/air deflector just
enough to disengage the pin from the shelf hole.
13 Pull out the grill/air deflector and store it in a safe place.
14 Check whether the identified fan module is missing, has failed, or is not
compatible with the shelf or its equipped Power Input Cards. Fan status is
indicated by the LEDs on each fan module. A green LED is lit when the
module is working properly. A red LED is lit when the fan fails but is receiving
power. No LEDs are lit if the fan control circuit is damaged or if the fan is not
receiving power because it is not compatible with the shelf or its Power Input
Cards. Treat a fan with no LEDs lit as a failed fan.
15 If the fan module Then go to
has failed step 16
is missing step 19


Fan Failed
Step Action
Verifying the fan module

16 Verify that the fan module is fully inserted.
17 Make any necessary adjustments.
cleared step 22
not cleared step 19
Installing/replacing the fan module

19 Install the missing fan module(s) or replace the failed fan module(s). Refer to
the “Replacing a cooling fan module” procedure in Fault Management -
Ensure you use the correct fan type.
cleared go to step 22
not cleared install the grill/air deflector (step 22 and step 23)
and contact your next level of support or your
Installing the snap-on shelf cover or closing the hinged cover (if previously equipped)
21 Close the hinged cover and lock it on the shelf.
Installing the grill/air deflector (if previously equipped)
22 Pull on the spring-loaded pins of the sides grill/air deflector, insert the grill/air
deflector into the shelf, and release the pins.
23 Align the pins with the holes in the sides of the shelf and push the grill/air
deflector until the pins enter the holes.
support group.
—end—

Procedure 4-112
Fan Failed (DSM)
Alarm ID: 135
Probable cause
This alarm is raised when a fan module in the cooling unit of the DS1 service
module (DSM) is equipped but fails.
Impact
Prerequisites
Step Action
DANGER
Risk of eye injury
2 Replace the fan module of the DSM. Ensure the red LED is off. Refer to the
“Replacing a cooling fan module” procedure in Fault Management - Module
support group.
—end—

Procedure 4-113
Fan Housing Missing
Alarm ID: 736
Probable cause
This alarm is raised when a cooling unit housing is physically not present in a
shelf that is provisioned for fan modules.
Impact
Prerequisites
323-1851-545
• obtain a cooling unit housing and fan modules
Step Action
DANGER
Risk of eye injury
1 Determine if fans are required for the shelf in the current configuration. Refer
to the “Cooling configurations” section in chapter 3 of Part 1 of 6500 Planning,
NTRN10CF.
You cannot install a cooling unit housing for a Metro front electrical shelf, as
the cooling unit housing is an integral part of the shelf.


Fan Housing Missing
Step Action
3 If fan modules are Then

not required deprovision the fan modules (set fan monitor status to
off). Refer to the “Editing the nodal system parameters”
required install a cooling unit housing and the fans in the shelf.
Refer to the “Installing the 6500 shelf and the access
panel” procedure in Part 1 of Installation, 323-1851-201.
When the cooling unit housing is installed in the shelf,
Fan Failed alarms is raised until the fans are installed
and working.
support group.
—end—

Procedure 4-114
Fan Incompatible
Alarm ID: 655
Probable cause
This alarm is raised when cooling fan modules with one exhaust air direction
are inserted into a cooling unit housing that has a different exhaust air
direction (for example, inserting front blowing fan in rear venting cooling unit
housing).
In 14-slot shelf types that have an integrated cooling unit housing (such as
metro front-electrical, a converged or a packet-optical shelf) with three
working fans present, where one of the fans exhausts air in a different
direction (front or rear), the alarm is raised against that different fan. In a shelf
with two working fans present and both fans exhaust air in a different direction,
the alarm is raised against the fan in the slot that is farthest.
Impact
Critical, service-affecting (C, SA) alarm if two or more fans are incompatible
Major, non-service-affecting (M, NSA) alarm if less than two fans are
incompatible in the cooling unit housing.
Prerequisites
323-1851-545
• obtain a compatible fan module


Fan Incompatible
Step Action
DANGER
Risk of eye injury
Attention: After removing a cooling fan module from a 14-slot shelf, the
cooling fan module must be replaced within one minute to prevent the circuit
packs from overheating due to insufficient airflow. Have a replacement fan
module ready before removing the fan module.
1 Check the shelf inventory to determine which fan is incompatible. Obtain the
compatible fan for replacement. Refer to the “Displaying shelf inventory
information” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
3 Remove the alarmed fan from the shelf or the cooling unit housing. Refer to
the “Replacing a cooling fan module” procedure in Fault Management -
The Fan Failed alarm is raised for the removed fan and the Fan Incompatible
alarm for that fan clears.
4 Wait at least 15 seconds but not more than 60 seconds and then insert a new
fan into the slot.
5 Verify that Fan Failed alarm has cleared. Retrieve all alarms to determine if
the original alarm has cleared.
—end—

Procedure 4-115
Fan Missing (DSM)
Alarm ID: 136
Probable cause
This alarm is raised on a DS1 service module (DSM) when the cooling unit fan
module is missing.
Impact
Prerequisites
Step Action
DANGER
Risk of eye injury
2 Insert the fan module into the empty slot. Refer to the “Replacing a cooling
fan module” procedure in Fault Management - Module Replacement,
323-1851-545.
support group.
—end—

Procedure 4-116
Far End Client Signal Fail
Alarm IDs: 349, 368, 695, 831, 870, 1247, 1306, 1307,1364, 1382,1488, 1625,
1671, 1678
Probable cause
This alarm is raised at the OTM2 layer facility of 2x10G OTR, 4x10G OTR,
OTM0/OTM1/OTMFLEX layer facility of the (1+8)xOTN Flex MOTR, or
OTM0/OTM1 layer facility of the 8xOTN Flex MOTR to indicate that there is a
client signal failure such as LOS/LOF/LOL, SFP missing, etc.
This alarm is raised for a OC-192/STM-64 client mapped to OTU2 line when
the FECSFMONITOR flag is enabled on the line side and when there is a
P-AIS detected on the line side. The WAN Far End Client Signal Fail alarm is
raised only with GFP CMF conditioning and there is a far-end client signal
failure.
This alarm is also raised against an OTM3/OTM4 layer facility of a 40G OCI,
40G+ CFP OCI, or 100G OCI circuit pack when service is terminated at the
near-end while the far-end CBR and Ethernet private line client signal is failed
(such as LOS or LOF). The alarm is masked by line OTU-LOS/LOF/pre-FEC
SF, LOMF, and ODU-AIS/LCK/OCI.
For the 16xOTN FLEX circuit pack, this alarm is raised against the WAN or
ODUCTP facility when the far-end mate port for this service is experiencing a
client Rx signal fault.
For the 4x10G MUX circuit pack, this alarm is raised against the STTP, ETTP
and WAN facilities when the far-end mate port for this service is experiencing
a client Rx signal fault.
For circuit packs with WAN facilities, this alarm is raised when the far-end
mate port for this service is experiencing a client Rx signal fault.
For 4x10G PKT I/F or eMOTR circuit packs, this alarm is raised against the
ODUTTP or WAN facility when the far-end mate port has a client Rx signal
fault. Note that the far-end mate port can not be a 4x10G PKT I/F or an
eMOTR circuit pack, as these circuit packs do not generate a Client Signal
Fail indication.
Impact
Critical, service-affecting (C, SA) alarm, if the alarm is raised on an active
traffic path
minor, non-service-affecting (m, NSA) alarm, if the alarm is raised on an
inactive traffic path


Far End Client Signal Fail
Prerequisites
323-1851-545
details
Step Action
1 Verify the fibers are connected and not crossed, looped back, or
misconnected.
2 Retrieve alarms from the corresponding far-end circuit pack. Refer to the
“Retrieving active alarms for one or more network elements” procedure in this
document.
3 Use the appropriate alarm clearing procedure to clear any alarms raised at
the far end.
support group.
—end—

Procedure 4-117
Far End Protection Line Fail
Alarm IDs: 521, 522, 523, 524, 961, 1019, 1125,1332, 1344, 1392, 1706
Probable cause
This alarm is raised to indicate that a protection line signal failure was
received in the APS bytes sent by the far-end protection engine. This indicates
that the far-end protection engine cannot switch traffic to the protection line
because a fault was detected downstream. This alarm is raised for a 1+1
OTN, 1+1/MSP linear, 1+1 port TPT, or 1+1 TPT configuration protection
group.
This alarm is cleared if a signal failure condition prevents the reception of valid
APS bytes.
This alarm only applies to bidirectional mode protection switching.
Impact
Prerequisites
• To perform this procedure, you must observe all safety requirements
described in the “Observing product and personnel safety guidelines”
chapter in Part 1 of Installation, 323-1851-201 or Fault Management -
• Ensure that you have the optical fiber connection information (information
on how the optical modules on each network element connect to other
network elements)
Step Action
1 Starting at the far-end network element and going upstream, check all
network elements for alarms against the protection line. Refer to the
“Retrieving active alarms for one or more network elements” procedure in this
document. Clear all far-end alarms related to the protection line.
2 Clear all other unexpected standing alarms on the local 6500 network
element by following the related trouble clearing procedures.
3 If the “Far End Protection Line Fail” alarm does not clear, contact your next
level of support or your Ciena support group.
—end—

Procedure 4-118
Fiber Channel Link Not operational
Alarm ID: 1258
Probable cause
This alarm is raised when fiber channel NOS primitive is being received from
the subtending equipment.
This alarm is raised against the FLEX facility when the protocol is FC400 or
FC800.
Impact
Critical, service-affecting (C, SA) alarm if not protected
Step Action
1 Verify the transmitting subtending equipment is functioning correctly and

transmitting a valid signal.
2 Log into the remote network element at the transmit end.
3 Retrieve all alarms from the remote network element at the transmit end.
4 Look for an alarm message for the remote network element circuit pack
connected to the original shelf.
If there are Then
no alarms at the ensure that the equipment and facility or the client and
transmit end line facilities of the remote circuit pack are in-service
and connected. Refer to the “Retrieving equipment
and facility details” procedure in Part 1 of
Configuration - Provisioning and Operating,
323-1851-310.
Go to step 5.
additional alarms refer to the appropriate alarm clearing procedures. Go
at the transmit end to step 5.

—end—

Procedure 4-119
Fiber Loss Detection Disabled
Alarm ID: 1581
Probable cause
This alarm is raised when the “High Fiber Loss Detection Alarm” system
parameter is set to Disabled on a shelf equipped with a Colorless OADM OTS.
Colorless OADM OTS requires High Fiber Loss Detection.
The “High Fiber Loss Detection Alarm” parameter can be found in the Site
Manager Node Information application under the System tab.
Impact
Prerequisites
Step Action
1 Enable the “High Fiber Loss Detection Alarm” system parameter. Refer to the
“Editing the nodal system parameters” procedure in Administration and
Security, 323-1851-301.
support group.
—end—

Procedure 4-120
Fiber Type Manual Provisioning Required
Alarm ID: 907
Probable cause
This alarm is raised against a ADJ-LINE facility when the fiber type for the line
adjacency is set to ‘Unknownfiber type’ (not provisioned) putting the line
adjacency out of service.
Impact
Prerequisites
Step Action
1 Provision the Fiber Type value of the alarmed line adjacency to a value other
than ‘Unknownfiber type’. Refer to the “Editing facility parameters” procedure
support group.
—end—

Procedure 4-121
Filler Card Missing
Alarm ID: 379
Probable cause
This alarm is raised when an unprovisioned or out-of-service slot is empty.
To ensure sufficient air flow for cooling the shelf, you must install filler cards
in all slots that do not contain a circuit pack. Failure to do so can cause the
shelf to exceed the maximum temperature which may cause component
damage (refer to Procedure 4-130, “High Temperature” on page 4-318).
Impact
Prerequisites
323-1851-545
• obtain a filler card or a circuit pack to install in the empty slot
Step Action
1 Identify the slot raising the alarm. Refer to the Procedure 2-4, “Retrieving
3 Insert a filler card or a circuit pack into the slot raising the alarm. Refer to the
“Installing circuit packs in the 6500 shelf” procedure in Part 2 of Installation,
323-1851-201.
support group.
—end—

Procedure 4-122
Filter Replacement Timer Expired
Alarm ID: 1580
Probable cause
This alarm is raised to indicate that you need to replace the air filter in the
shelf.
Default value of Replacement Time Interval is 24 months.
Impact
Prerequisites
323-1851-545
• obtain a replacement air filter to install in the empty slot
Step Action
1 Choose your next step.

If you want to Then
replace the filter step 2
set a new replacement time step 3
reset the filter timer step 4
disable the filter timer step 5
2 Replace the air filter in the shelf. Refer to the “Replacing the shelf air filter”
procedure in Fault Management - Module Replacement, 323-1851-545. Go
to step 4.
3 Provision a new replacement time interval using Site Manager. Refer to the
"Resetting the air filter replacement timer" procedure in Administration and
Security, 323-1851-301. Go to step 6.
4 Reset the timer. The timer will reset to the value given by replacement
interval. Refer to the “Resetting the air filter replacement timer” procedure in
Administration and Security, 323-1851-301. Go to step 6.


Filter Replacement Timer Expired
Step Action
5 Disable the timer. Refer to the “Editing the nodal shelf parameters” procedure
in Administration and Security, 323-1851-301.
Attention: Disabling and re-enabling the timer that has already expired,
does not cause the timer to reset. The alarm is raised after re-enabling the
timer.
support group.
—end—

Procedure 4-123
Flash Banks Mismatch
Alarm ID: 222
Probable cause
This alarm is raised when an upgrade is interrupted. If an upgrade is
interrupted, there can be different loads present on the shelf processor.
The alarm can also be raised during a shelf processor replacement procedure
when a software load on either flash bank of the network element is not up to
date with respect to the release that is running on the network element.
Impact
Step Action
1 If the alarm is raised during a shelf processor replacement, it will clear once
the shelf processor replacement procedure is completed.
support group.
—end—

Procedure 4-124
Frequency Out of Range (OC192/STM64, ETH10G)
Alarm ID: 1613, 1614
Probable cause
This alarm is raised when the frequency limits exceed the IEEE 802.3 Tx
frequency offset specifications of +/- 20ppm for 10GBASE-W and +/-100ppm
for 10GBASE-R.
More specifically, for the following 6500 transport cards: NTK525CA,

NTK525CF, NTK529BB, and NTK529BX this alarm is raised when the
measured frequency of the input client clock is greater than +/-27.5ppm
(OC192/STM64) or +/-107.5ppm (ETH10G).
This alarm applies to OC192/STM64 and ETH10G facility client types on the
40G MUX OCI (NTK525CA/NTK525CF) and 10x10G MUX (NTK529BB). The
“Frequency Out of Range” alarm does not apply to NTK525CA when ETH10G
is provisioned with GFP mapping. The Frequency Out of Range alarm does
not force conditioning.
Attention: This alarm does not apply to 40G MUX OCI (NTK525CA) when
ETH10G is provisioned with GFP mapping.
Impact
Step Action
1 If possible, clear all OC-192/STM-64 and Eth10G alarms from the network.
2 If the alarm did not clear, verify the subtending equipment to ensure that it
meets the frequency specification. If the equipment does not meet the
specification, change the client signal to use subtending equipment that is
within specifications.
support group.
—end—

Procedure 4-125
Gauge Threshold Crossing Alert Summary
Alarm ID: 724, 725, 726, 1034
Probable cause
This is a summary alarm for each AMP, VOA, RAMAN, and OPTMON facility,
and is raised if one or more of the physical gauge power values crosses its
provisioned PM threshold.
This alarm is masked by the Loss of Signal and Circuit Pack Failed alarms.
Attention: PM thresholds stored in PM Profiles define the maximum

deviation from the currently set baseline for a gauge power value. Resetting
baselines of gauge power values is normally done by DOC, but may also be
manually triggered by the user.
The typical cause for this alarm is reduced power levels on the port reporting
the alarm. Conditions that can result in reduced power levels at a port include:
• a PM threshold setting that is too low for a gauge power value
• a faulty or incorrectly provisioned transmitter module
• a faulty or incorrectly provisioned receive module
• an optical signal degradation caused by a bent optical fiber or dirty optical
connector
• a wrong DSCM type for a link
• improper optical cable mating
• a disconnected optical fiber at the amplifier output
• an optical fiber cut
• a disconnected or missing termination
• misprovisioning of an amplifier resulting in excessive power being injected
into the mid-stage DSCM or fiber-plant
• a power value has been reported as outside of range (OOR) and the
baseline has been set as out of range (OOR) and the power fluctuates to
a non-OOR value, then the alarm can be raised
• new transponders connected to DIA
• channels added in a downstream domain of a branched network


Use this alarm to resolve the causes of the threshold crossings before a
service-affecting problem occurs.
This alarm clears automatically when all gauge readings fall within their
threshold boundaries.
Attention: This alarm can be cleared manually from the Site Manager PM
screen by resetting the baseline. Refer to the “Resetting the PM physical
baseline power level” procedure in Fault Management - Performance
Monitoring, 323-1851-520.
Impact
Prerequisites
323-1851-545
details
• obtain a replacement module or fiber patch cord, if required
Step Action
1 If this alarm Then

was raised as a result of a main- no action is required. The alarm will clear
tenance activity or during SLAT when the maintenance activity or SLAT
and it is expected is completed.
is not expected continue with step 2
2 Verify that the PM threshold values for the alarmed facility are correctly
provisioned. Adjust the value if required. Refer to the PM parameter
definitions table for Photonic circuit packs” in Fault Management -
Performance Monitoring, 323-1851-520.


Step Action

4 If Then
there are new transponders manually update of TCA thresholds. See
connected to or disconnected Performance Monitoring, 323-1851-520.
from a DIA or channels were If the alarm did not clear, go to step 5
added or deleted on downstream
domains
otherwise go to step 5
5 Verify that the optical power is within range. Refer to the PM procedures in
Fault Management - Performance Monitoring, 323-1851-520.
If both the minimum and maximum values are outside of range, you can
enable automatic in-service (AINS) for the facility until a valid signal is
present. Refer to the “Editing facility parameters” procedure in Part 1 of
If the power level is too close to the Input Loss of Signal Threshold configured
in the Amp properties, the alarm is going to be toggled. In this case, edit the
Threshold 1 dB below the threshold level on the Amp settings.
7 Using the alarm details for the Gauge Threshold Crossing Alert Summary
alarm, note the Unit and Class the alarm is raised against.
8 Retrieve the PMs for the Shelf, Type, and Facility based on the information
noted in step 7.
9 From the PM application, note the facility parameter that has an Untimed
value that crossed the threshold value.


Step Action
before clearing this alarm:
• Loss of Signal (OPTMON)

12 Determine if there are other Gauge Threshold Crossing Alert Summary

alarms raised in the network and begin by troubleshooting the most upstream
Gauge Threshold Crossing Alert Summary alarm. To troubleshoot the most
upstream Gauge Threshold Crossing Alert Summary alarm, verify the optical
patch cord connected to the port reporting the alarm:
Attention: Ensure the optical patch cord is connected at both ends and that
there is no problem with the optical patch cord. Clean the connectors. Refer
to the cleaning connectors procedures in chapter 7 of Part 2 of Installation,
323-1851-201.

14 If the alarm is reported against the OPIN parameter of a LIM amplifier Line A
In (port 8) facility (or the OPR parameter of a LIM OPTMON Line A In (port 8)
facility) AND the OPR parameter of a LIM OSC A Out (port 4) facility, then
verify the outside fiber plant.
15 If the alarm is reported against the OPOUT parameter of CMD or SCMD
Channel In VOA facility, make sure that the transmitting subtending
equipment is functioning correctly and transmitting a valid signal.


Step Action
16 If the alarm is reported against the GRPOPOUT parameter of a SCMD4

Common In VOA facility or the OPR parameter of a SCMD4 Common In
OPTMON facility, it may be a problem at the head end site where the SCMDs
are interconnected using the upgrade ports. Check the patch cords used at
the upgrade ports.
support group.
—end—

Procedure 4-126
GCC0/GCC1/GCC2 Link Failure
Alarm ID: 672, 834, 996, 1009, 1164, 1179, 1430, 1431, 1432, 1723, 1724,
1725
Probable cause
This alarm is raised when the network element communications fail on the
ITU-T G.709 general communication channel (GCC0, GCC1, or GCC2) link.
This alarm can also be raised if the facility (OTM1, OTM2, OTM3, OTM4,
GCCTTP, ODUCTP, ODUTTP, or OTUTTP) is physically looped back (Tx
interface connected to Rx interface).
For NGM WT circuit packs, the GCC link (via PPP) is controlled by LLSDCC,
not circuit (IISIS or OSPF). Therefore, even if there are no IISIS or OSPF
circuits provisioned, GCC link will still be up between near and far ends and
no GCC Link Failure alarm will be raised.
For the rest of the circuit packs supporting GCC such as SuperMux, 40G
OCLD, 40G OCI, 40G MUX, 16xOTNFLEX, 4x10G PK I/F, 2.5G MOTR, 10G
OTR/OTSC, 4x10G OTR, 2x10G OTR, and 100G circuit packs, GCC link is
controlled by IISIS or OSPF circuits. Therefore, GCC Link Failure alarm will
be raised if there are no IISIS or OSPF circuits provisioned.
The "GCC1 Link Failure" alarm is also raised on the 4x10G MUX (NTK525CF)
circuit pack when OTM3 facility is placed OOS.
If only one end of a GCC PPP link is provisioned while the other end is not,
the link state of the PPP link at the first end will toggle up and down. Therefore,
you will see this alarm toggle on the SP, until the PPP link gets provisioned at
the other end.
Impact
Prerequisites
323-1851-545


• clear all remote alarms present against the optical fiber

Step Action
1 Identify the facility raising the alarm. Refer to the “Identifying the circuit pack,
pluggable module/port, or facility that has raised an alarm” procedure in this
document.
2 Use the optical fiber connection information to identify the network element
and the circuit pack that is the source of the signal reporting the alarm.
3 Wait five minutes after the alarm was raised in case a shelf processor or
interface circuit pack restart at the remote terminal caused the alarm.
5 Ensure the following comms parameters (in the Site Manager Comms
Setting Management application) exist at each end of the
GCC/GCC0/GCC1/GCC2 link for the circuit pack reporting the alarm:
— GCC/GCC0/GCC1/GCC2 IISIS or OSPF circuit (under Routers,
Router Type=IISIS Circuit or OSPF circuit)
— GCC/GCC0/GCC1/GCC2 PPP interface (under Interfaces,
Interface type=PPP)
— GCC/GCC0/GCC1/GCC2 Lower Layer DCC/GCC interface (under
Interfaces, Interface type=Lower Layer DCC/GCC)
6 If the original alarm has cleared, the procedure is complete. Otherwise go to
step 7.
8 Log into the remote network element using the external IP address.
• If the login is successful, go to step 10.
• If the login fails, go to step 9.


Step Action
9 If Then
the remote network element the login may not be possible, as the
is only accessible through GCC/GCC0/GCC1/GCC2 has failed. Go to
GCC/GCC0/GCC1/GCC2 step 10
otherwise replace the shelf processor at the remote site.
Refer to the “Replacing the shelf processor”
procedure in Fault Management - Module
Replacement, 323-1851-545. Wait at least five
minutes for the shelf processor to boot, then
log in. Go to step 11.
10 Reseat the shelf processor. Wait five minutes for it to restart. Refer to the
“Reseating a circuit pack” procedure in Fault Management - Module
12 Replace the shelf processor at the site that originally reported the alarm.
Refer to the “Replacing the shelf processor” procedure in Fault Management
- Module Replacement, 323-1851-545. Wait five minutes for the shelf
processor to restart.
14 Replace the shelf processor at the remote site you determined in step 2 if this
has not already been done in step 12. Refer to the “Replacing the shelf
processor” procedure in Fault Management - Module Replacement,
323-1851-545. Wait five minutes for the shelf processor to restart.
16 Replace the required circuit pack at the remote site determined in step 2.


Step Action
18 Replace the required circuit pack at the network element originally reporting
the alarm. Refer to the equipment replacement procedures in chapter 2 of
19 If the alarm is still active, the alarm can be the result of mis-fibering causing
a physical loopback along the photonic layer. Check the optical fibering along
the path of the channel.
support group.
—end—

Procedure 4-127
Group Loss of Signal
Alarm ID: 710, 832
Probable cause
The alarm is raised against port 1 of SCMD4, OMD4 or OMX modules (that
is, the common in port of SCMD4, OMD4 or OTS in port of OMX). For OMD4
and OMX, it is a logical alarm resulting from alarm correlation when loss of
signal conditions are detected on all the line receivers connected on the
optical channels of the module. This alarm is raised only when alarm
correlation is turned on. For SCMD44, this alarm is raised if the LOS condition
is detected got the group on the card after the group is split.
The conditions can be caused by a faulty module or a fault that impact all
channels of the module. for example:
• a line fiber cut
• excessive power loss on the line fiber that exceeded link budget
• a disconnected, or defective fiber optic patch cord
• a dirty optical fiber connector
• a provisioning error
• a reflective event, indicated by an Automatic Power Reduction Active
• alarms at an upstream booster amplifier or pre-amplifier (DSCM)
This condition is also possible if there is a disconnected, defective patch cord

or dirty optical fiber connected between the OMD4/OMx module and every
line receiver.
Impact
Prerequisites
323-1851-201 or Module Replacement Procedures, 323-1851-545
• have a network and site diagram
• obtain a replacement circuit pack, if required


Group Loss of Signal
Step Action
1 Check for and clear any of the following alarms before clearing this alarm:


OMD4 or OMX step 4
SCMD4 step 8
4 Consult with the network configuration chart.

5 Verify that the adjacency provisioning is correct for itself and all other
OMD/OMX connected their upgrade/through ports.
6 Identify all OMX/OMD4 connected through the upgrade/through ports. Check
if these OMX/OMD4 are reporting G-LOS or LOS.
7 Identify all the upstream line fiber, patch cord and equipment that are
common to those groups raised LOS/G-LOS.
8 Clean the fibers, patch cords and verify the equipment. Refer to the cleaning
connectors procedures in chapter 7 of Part 2 of Installation, 323-1851-201.
10 Clear any upstream (either at the local to the network element reporting the
alarm or other upstream remote network elements) alarms that could be
causing this alarm, such as Circuit Pack Failed, Circuit Pack Missing, or Loss
of Signal (OPTMON).
support group.
—end—

Procedure 4-128
High Fiber Loss
Alarm ID: 1239
Probable cause
This alarm is raised against the originating ADJ-FIBER facility when the
measured loss between this port and the far end port is greater than either of
the provisioned loss thresholds. A 0.5 dB hysteresis is also applied which
prevents the alarm from clearing until the measured loss has gone below the
threshold(s) by more than 0.5 dB. The calculated fiber loss is reported against
the ADJ-FIBER facility.
This alarm is supported for the following interconnections:

• LIM to WSS
• LIM to CASLIM
• CASLIM to WSS
• WSS to DROPLIM
• DROPLIM to WSS
• WSS to WSS
• LIM Monitor Out to WSS Monitor In
• SRA/SAM/ESAM to XLA
• XLA to SRA/SAM/ESAM
• XLA to WSS
• XLA to LIM
• XLA Monitor Out to WSS Monitor In
• Amplifier monitor port to 2-Port OPM port
For the COADM (Colorless) OTS, the alarm is supported for the following
interconnections (in addition to those described above):
• LIM to SMD
• SMD to LIM
• CCMD12 MON (port-27) to SMD OPM (ports 1-8)
• CCMD12 to SMD
• OCLD Tx to CCMD12 (alarm is raised against the CCMD12 ADJ-FIBER
(receive direction) in this instance, not against the OCLD OTM3 port and
is based on the CCMD12 ADJ-TX facility provisioned Nominal Tx power)


High Fiber Loss
The fiber loss is calculated between the above Photonic equipment and it
takes into account any excess loss (such as the placement of an attenuator
pad) provisioned at the originating ADJ-FIBER facility as well as any
provisioned DSCM/Pad.
The “High Fiber Loss” Alarm Detection Alarm parameter in the Site Manager
Node Information application and the System tab is enabled by default.
Impact
When fiber loss exceeds user-provisioned Fiber Loss Minor Threshold

(default is 3 dB), the alarm is raised with minor severity.
“Fiber Loss Minor Threshold” threshold possible values are 0 to 30 with 0.01
resolution.
When fiber loss exceeds user-provisioned Fiber Loss Major Threshold

(default is 10 dB), the alarm is raised with major severity.
“Fiber Loss Major Threshold” threshold possible values are 0 to 30 with 0.01
resolution but must be greater than the “Fiber Loss Minor Threshold” value.
Prerequisites
323-1851-545
• obtain a fiber patch cord, if required


High Fiber Loss
Step Action
1
CAUTION
Check the fibers involved in the High Fiber Loss alarm (all fibers between the
port where the alarm is raised and the port specified as the Far End Address
for this adjacency):
• verify the fibers are connected, and not crossed, looped back, or
misconnected
• check and clean any dirty fibers. Refer to the “Cleaning connectors”
chapter in Part 2 of Installation, 323-1851-201.

3 If Then go to
you are using DSCM step 4
otherwise step 5
4 Check that the DSCM provisioning is correct. For information on provisioning

the DSCM in OTS, refer to the "Retrieving OTS Management, OTS
Equipment, and Facility Details" procedure in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310. For information on the facility
provisioning for the DISP facility on DSCM, refer to the "Retrieving equipment
and facility details" procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
To change the provisioning, refer to the "Editing facility parameters"
323-1851-310 or the "Editing an OTS instance" procedure in Part 2 of
5 Check Excess Loss provisioning. If there are lossy elements (patch panels
and pads are typical examples of lossy elements) between the two ports, the
loss of the element itself should be provisioned in the Excess Loss field. Refer
to the "Editing facility parameters" procedure in Part 1 of Configuration -


High Fiber Loss
Step Action
6 If the reported loss is less than the Major or Minor threshold, but not by
0.5 dB, the alarm is being held on due to a 0.5 dB hysteresis. The threshold
is likely too low. Adjust the threshold.
7 If the reported loss is greater than 1.5 dB, this is likely a problem in the circuit
packs or fibering that needs to be resolved. Contact your next level of support
or your Ciena support group.
8 For losses less than 1.5 dB if all other steps have been taken, clear the alarm
by adjusting the threshold.

disable detection without addressing the fault step 11
otherwise step 12
11 Disable the “High Fiber Loss Detection” alarm as follows:
Attention: You can disable the "High Fiber Loss" alarm per-port basis by
setting the appropriate Major or Minor alarm threshold to 0 for that port.
• Select Node Information from the Configuration drop-down menu.

• Select the Node Information tab
• Select the row of the required shelf from the Node Information table.
• Select the System sub-tab.
• Click Edit in the System sub-tab to open the Edit System dialog box.
• Select Disable from the High Fiber Loss Detection alarm drop-down
menu.
For more information, refer to the “Editing the nodal system parameters”
support group.
—end—

Procedure 4-129
High Received Span Loss
Alarm ID: 1155
Probable cause
This alarm is raised against the LIM, SRA, SAM, or ESAM circuit packs (at the
tail end of the span) when the incoming estimated Span Loss for the span is
higher than the Target Span Loss plus the Span Loss Margin.
For SRA circuit packs, the Telemetry Gain Signal value is used for Span Loss
calculation. Refer to the Photonic Layer Guide, NTRN15DA for more
information.
The alarm clears when the span loss drops 1.0 dB below the raise threshold.
Target Span Loss and Margin are user provisionable. (Target Span Loss +
Span Loss Margin) + 1 dB.
Attention: Span Loss for an optical span is stored as a PM with full

retrievable history. Refer to the “Retrieving performance monitoring data” in
the Fault Management - Performance Monitoring, 323-1851-520.
Impact
Prerequisites
323-1851-545
• obtain a fiber patch cord, if required


High Received Span Loss
Step Action
1
CAUTION
Check the fibers of the alarmed facility (at the network element raising the
alarm and at the upstream network element):
• verify the fibers are connected, and not crossed, looped back, or
misconnected
• check and clean any dirty fibers. Refer to the “Cleaning connectors”
chapter in Part 2 of Installation, 323-1851-201.
3 If Then go to
you want to clear the alarm (and disable step 4
detection) without addressing the fault
otherwise step 5
4 Provision the Target Span Loss to 0. Refer to the “Editing facility parameters”
323-1851-310.
support group.
—end—

Procedure 4-130
High Temperature
Alarm ID: 378
Probable cause
This alarm is raised when the shelf's ambient temperature is too high, a circuit
pack's temperature is too high, or when the shelf cooling system is not
functioning correctly. The following conditions are applicable:
• The central office temperature is too high.
• There are empty slots in the shelf which need to be filled with filler cards.
• The shelf cooling system is not functioning correctly.
• The shelf is operating for more than 60 seconds without any cooling fans
equipped (fan modules are missing or not fully inserted).
• Air exhaust port or air inlet plenum is blocked.
• Air filter has a blockage.
• The shelf's exhaust air is being trapped in an enclosed space or cabinet
and is re-circulating into the air inlet plenum.
• There is a problem with a circuit pack or module in the shelf.
• For a 7-slot optical shelf, a missing or improperly seated access panel (the
access panel contains a temperature sensor that is linked to the cooling
fan module via the backplane).
• For a 2-slot or 7-slot optical Type 2 shelf, an improperly seated Shelf
processor w/access panel (the SPAP contains a temperature sensor that
is linked to the cooling fan module via the backplane) or SPAP2 w/2xOSC.
Attention: High temperature alarm is latched. This means that the alarm is
not cleared automatically when temperature is back to normal. This situation
requires immediate attention. Temperature can be monitored through
inventory retrieval which displays the current and average temperature on
the supported cards. Refer to the “Displaying shelf inventory information”
323-1851-310.
Attention: It may take some time for a shelf to cool off and the alarm to clear
after the cause is corrected.
Impact


High Temperature
Prerequisites
Step Action
DANGER
Risk of eye injury
modules, air filters or in proximity to the shelf air
exhaust.
1 Make sure that the central office temperature does not exceed the operating
temperature requirements of the equipment. Refer to the “Operating
environmental specifications for 6500 system” table in chapter 8 of Part 3 of
6500 Planning, NTRN10CF.
3 If the office temperature is Then
within the operating temperature go to step 4
not within the operating temperature correct the office temperature
4 Retrieve the shelf inventory or visually inspect the shelf to confirm that all
slots are filled. Refer to the "Displaying shelf inventory information" procedure
in Part 1 of Configuration - Provisioning and Operating, 323-1851-310. Note
that the cross-connect slots on a 32-slot shelf do not support filler card
detection and must be visually checked to confirm if they are equipped with a
2-slot x 2-row filler cards.
5 If the shelf has Then go to
all slots filled step 9
empty slots step 6
6 Re-insert any missing circuit packs or install filler cards into any empty slots.
Refer to the equipment replacement procedures in Part 2 of Fault


High Temperature
Step Action
7 Monitor the temperatures on the circuit packs by retrieving the inventory and
check if current temperature of all the supported circuit packs decreases. If
the temperature decreases, perform a warm restart of the shelf processor.
Refer to the "Restarting a circuit pack or shelf processor" procedure in this
document. If temperature did not decrease even after ten minutes or if the
shelf processor is still reporting a current temperature of 50 C or greater,
proceed to the next step.
cleared after six minutes the procedure is complete
not cleared even after all the circuit packs are step 9
at normal temperature for more than six
minutes
9 Inspect the grill at the air exhaust of the cooling unit or the grill integrated into
the shelf cover/door, the grill on the cooling fan module and the grill on the air
inlet plenum. If any have an accumulation of dust, vacuum the grill.
check if current temperature of all the supported circuit packs decreases. If
the temperature decreases, perform a warm restart of the shelf processor.
Refer to the “Restarting a circuit pack or shelf processor” procedure in this
12 Remove and inspect the shelf air filter and replace it with a new one if there
is a visible accumulation of dust. Refer to the “Replacing the shelf air filter”
13 Monitor the temperatures on the cards by retrieving the inventory and check
if current temperature of all the supported circuit packs decreases. If the
temperature decreases, perform a warm restart of the shelf processor. Refer
to the “Restarting a circuit pack or shelf processor” procedure in this


High Temperature
Step Action
15 For the 2-slot or 7-slot optical shelves, ensure the AP, SPAP, or SPAP2
w/2xOSC are fully seated. If not, loosen the faceplate screws on the AP,
SPAP, or SPAP2 w/2xOSC circuit pack, push the circuit pack in fully and
tighten the screws to the prescribed torque. Refer to the “Installing the 6500
shelf and the access panel” procedure in Part 1 of Installation, 323-1851-201.
16 Restart the Shelf Processor. Refer to the "Restarting a circuit pack or shelf
processor" procedure in this document.
18 Replace the cooling fan module(s) or the entire cooling unit in the case of
14-slot shelves equipped with a top-mounted cooling unit shelf assembly.
Refer to the “Replacing the cooling unit assembly” and “Replacing a cooling
fan module” procedures in Fault Management - Module Replacement,
323-1851-545.
19 Monitor the temperatures on the cards by retrieving the inventory and check
if current temperature of all the supported circuit packs decreases. If the
temperature decreases, perform a warm restart of the shelf processor. Refer
to the “Restarting a circuit pack or shelf processor” procedure in this
proceed to step 21.
21 If the alarm does not clear, it could be due to a problem with a circuit pack.
Contact your next level of support or your Ciena support group.
—end—

Procedure 4-131
High Temperature Warning
Alarm ID: 1143
Probable cause
This alarm is raised as a warning to user when the shelf’s ambient
temperature is high or when a circuit pack's temperature is high which can
result from one of the following conditions:
• The central office temperature is too high.
• There are empty slots in the shelf which need to be filled with filler cards.
• The shelf cooling system is not functioning correctly.
• Air exhaust port or air inlet plenum is blocked.
• Air filter has a blockage.
• The shelf's exhaust air is being trapped in an enclosed space or cabinet
and is re-circulating into the air inlet plenum.
• There is a problem with a circuit pack or module in the shelf.
Attention: If a high temperature warning condition prevails for a while, it

could potentially lead to “High Temperature” condition. Refer to High
Temperature on page 4-318 for high temperature condition information.
The Raised temperature warning condition is cleared on the shelf

automatically if the temperature on these circuit packs decreases to an
acceptable level.
Temperature can be monitored through inventory retrieval which displays the

current and average temperature on the supported circuit packs. Refer to the
“Displaying shelf inventory information” procedure in Part 1 of Configuration -
Impact
Major, non service-affecting (M, NSA) alarm
Prerequisites


Step Action
DANGER
Risk of eye injury
modules, air filters or in proximity to the shelf air
exhaust.
1 Make sure that the central office temperature does not exceed the operating
temperature requirements of the equipment. Refer to the “Environmental
specifications” section in chapter 8 of Part 3 of 6500 Planning, NTRN10CF.
3 If the office temperature is Then
within the operating temperature go to step 4
not within the operating temperature correct the office temperature
4 Retrieve the shelf inventory or visually inspect the shelf to confirm that all
slots are filled. Refer to the "Displaying shelf inventory information" procedure
in Part 1 of Configuration - Provisioning and Operating, 323-1851-310. Note
that the cross-connect slots on a 32-slot shelf do not support filler card
detection and must be visually checked to confirm if they are equipped with a
2-slot x 2-row filler card.
5 If the shelf has Then go to
all slots filled step 9
empty slots step 6
6 Re-insert any missing circuit packs or install filler cards into any empty slots.
Refer to the equipment replacement procedures in Part 2 of Fault
check if the current temperature of all the supported circuit packs decreases
after 10 minutes. If the temperature decreases, perform a warm restart of the
shelf processor. Refer to the "Restarting a circuit pack or shelf processor"
procedure in this document. If temperature does not decrease after ten
minutes or if the shelf processor is still reporting a current temperature of
50 C or greater, proceed to step 9.


Step Action

not cleared even after all the circuit go to step 10
packs are at normal temperature for
more than six minutes
9 Inspect the grill at the air exhaust of the cooling unit or the grill integrated into
the shelf cover/door, the grill on the cooling fan module and the grill on the air
inlet plenum. If any have an accumulation of dust, vacuum the grill.
see if the current temperature decreases on all the supported circuit packs. If
temperature does not decrease after ten minutes proceed to step 12.
If the temperature falls to normal on all the supported circuit packs wait for 6
minutes for the alarm to clear.
not cleared even after all the circuit packs are at go to step 18
normal temperature for more than six minutes
12 Remove and inspect the shelf air filter and replace it with a new one if there
is a visible accumulation of dust. Refer to the “Replacing the shelf air filter”
see if the current temperature decreases on all the supported circuit packs. If
temperature does not decrease after ten minutes or if the shelf processor is
still reporting a current temperature of 50 C or greater, proceed to step 15.
If the temperature falls to normal on all the supported circuit packs wait for six
15 Replace the cooling fans module(s) or the entire cooling unit in the case of
14-slot shelves equipped with a top-mounted cooling unit shelf assembly.
Refer to the “Replacing the cooling unit assembly” and “Replacing a cooling
fan module” procedures in Fault Management - Module Replacement,
323-1851-545.


Step Action
see if the current temperature decreases on all the supported cards. If
temperature does not decrease after ten minutes or if the shelf processor is
still reporting a current temperature of 50 C or greater, proceed to step 18.
If the temperature falls to normal on all the supported circuit packs wait for six
18 If the alarm does not clear, it could be due to a problem with a circuit pack.
Contact your next level of support or your Ciena support group.
—end—


Copyright© 2010-2013 Ciena® Corporation. All Rights Reserved.
Release 9.3
Publication: 323-1851-543
Document status: Standard
Issue 1
Document release date: June 2013
CONTACT CIENA
For additional information, office locations, and phone numbers, please visit the Ciena web site at
www.ciena.com

323-1851-543.1 (6500 R9.3 AlarmClearing) Issue1

Uploaded by

Copyright:

Available Formats

323-1851-543.1 (6500 R9.3 AlarmClearing) Issue1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

323-1851-543.1 (6500 R9.3 AlarmClearing) Issue1

Uploaded by

Copyright:

Available Formats

6500 Packet-Optical Platform

Fault Management - Alarm Clearing,

See Part 2 for the following...

323-1851-543 - Standard Issue 1

Ciena® Confidential and Proprietary

Corporate Headquarters 410-694-5700 or 800-921-1144 www.ciena.com

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

New in this release and documentation roadmap xiii

Alarm and trouble clearing strategy 1-1

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

Signal conditioning for 10G OTU2 WT circuit packs 1-55

Alarm surveillance 2-1

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

2-18 Measuring Photonic amplifier output power 2-52

Alarm hierarchies and alarm severities 3-1

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

Alarm clearing procedures—A to H 4-1

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

4-28 Circuit Pack Failed - Pluggable 4-82

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

4-78 DOC Action: Channel Delete In Progress 4-173

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

4-128 High Fiber Loss 4-312

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

New in this release and documentation

You are reading Part 1 of Fault Management - Alarm Clearing, 323-1851-543.

The following section details what’s new in Fault Management - Alarm

This Technical Publication supports 6500 Packet-Optical Platform

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

New features in Release 9.3 Issue 1

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

6500 Packet-Optical Platform technical publications

Planning a Network Installing, Managing and Maintaining and Circuit Pack-Based

Documentation Installation, Administration Fault Management - Common Eqpt

Data and Layer 2

OTN I/F and PKT I/F

SAOS-based Command Fault and MIB

6500 Photonic 6500 Data Network Common

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

Alarm and trouble clearing strategy 1-

This release of 6500 Packet-Optical Platform (6500) supports the MSPP,

Site level alarm correlation

Alarm correlation requires that physical adjacency information be provisioned

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

Layer Interoperability (SPLI) feature. The adjacency information between

Attention: In passive photonic configurations, the DSCM, which is

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

Backwards alarm correlation only functions if all service circuit packs

Site level alarm correlation is supported on the OMX, CMD44, OMDF4,

See 6500 Packet-Optical Platform Photonic Layer Guide, NTRN15DA, for

Site level alarm correlation is supported on the RAMAN amplifiers in the

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2

Loss Shutoff Loss

OSC OSC OSC OSC OSC

6500 Packet-Optical Platform Fault Management - Alarm Clearing, Part 1 of 2