FSP 3000r7

Fiber Service Platform 3000R7
Maintenance and
Troubleshooting Manual
Product Release 16.2

Document Issue A (4/5/2017)
Document Number 80000042876
Copyright © 2001-2017 ADVA Optical Networking SE
All rights reserved. Hardware and software mentioned in this document includes software developed by ADVA
Optical Networking SE ("ADVA Optical Networking"), the Apache Software Foundation
(http://www.apache.org), Teodor Danciu (http://jasperreports.sourceforge.net), and/or other open source
software. Some software was created using ORBacus for Java by Object-Oriented Concepts, Inc.
Patents
The content described in this document may be covered by patents or pending patent applications of ADVA
Optical Networking. The furnishing of this document does not give you any license to these patents.
Disclaimers
Nothing in this document shall be construed as granting any license or rights with respect to its content or the
patents and trademarks mentioned above. The content of this document may include technical inaccuracies or
typographical errors, and is subject to change at any time without notice. Reliance on this content is at the relying
party's sole risk and will not create any liability or obligation for ADVA Optical Networking. Any references in this
document to publications and/or Internet sites that are not from ADVA Optical Networking are provided for
convenience only and do not in any manner serve as an endorsement of those publications and/or Internet sites.
The materials within those publications and/or Internet sites are not part of the materials for any ADVA Optical
Networking information, product, or service, and use of those publications and/or Internet sites is at your own
risk.
THE CONTENT OF THIS DOCUMENT IS PROVIDED ''AS IS'' AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL ADVA OPTICAL NETWORKING, ITS AFFILIATES, EMPLOYEES, OFFICERS OR ITS SUPPLIERS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND BASED ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. THE SAME APPLIES FOR
ANY HARDWARE OR SOFTWARE COVERED BY THIS DOCUMENT, UNLESS A SIGNED AGREEMENT
WITH ADVA OPTICAL NETWORKING OR THE APPLICABLE PRODUCT LIABILITY LAW EXPRESSLY
STATES OTHERWISE.
ADVA Optical Networking SE
Fraunhoferstr. 9a
82152 Martinsried/Muenchen
Germany
Phone +49(0)89-890665-0
Fax +49(0)89-890665-699
http://www.advaoptical.com
Table of Contents
Related Documents Overview 11
Preface 15
Purpose and Scope 16
Audience 16
Documentation Revision History 16
Document Conventions 23
Typographic Conventions 23
Safety Symbol and Message Conventions 24
Obtaining Documentation 25
World Wide Web 25
Ordering Documentation 25
Documentation Feedback 25
Obtaining Technical Assistance 25
Customer Portal 26
Technical Services 26
Contact ADVA Optical Networking 26
Preparation for Troubleshooting 29

Requirements 30
Cleaning and Inspecting Fibers and Ports 32
General Reminders and Warnings 33
Reminders 33
Best Practices 34
Required Tools 34
Cleaning Fiber-Optic Connector Plugs 34
Cleaning and Inspecting Connector Receptacles 37
Cleaning and Inspecting Fiber Jumpers 38
Dry Cleaning Technique Using Cartridge and Pocket-Style Cleaners 38
Dry Cleaning Technique Using Lint-Free Wipes 40
Wet Cleaning Technique Using Lint-Free Wipes 41
Wet Cleaning Using Lint-Free Swabs 42
Dry Cleaning Using Lint-Free Swabs 43
Vendor-Specific Cleaning Techniques 44
Cleaning MTP Fiber Cable Ends 44
Cleaning Recommendation for Optical Ports of Pluggable Transceivers 45
Handling Equipment 47
Handling a Shelf 47
Handling Modules 48
Handling Pluggable Transceivers 49
Handling Fiber-Optic Cables 50
Optical Fiber Requirements 51
Finding Your Problem - Follow the Light 53
FSP 3000R7 Maintenance and Troubleshooting Manual - Product Release 16.2 - Document Issue A 3
Shelves and Power Supply Units 59
Troubleshooting Shelves 60
SH1HU-F/2DC, SH1HU-HP/2DC and SH1HU-HP/E-TEMP/2DC Shelf LEDs 60
SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-TEMP/2DC Fan Status LED 62
SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-TEMP/2DC Slot Status LEDs 63
SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-TEMP/2DC Power Status LEDs 65
SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-TEMP/2DC Network Element Status
LEDs 66
SH1HU-R(/PF) Shelf LEDs 68
SH1HU-R(/PF) Fan Status LED 69
SH1HU-R(/PF) Slot Status LEDs 70
SH1HU-R(/PF) Power Status LEDs 72
SH1HU-R(/PF) Network Element Status LEDs 73
SH7HU(-R) Shelf LEDs 75
SH7HU(-R) Fan Status LEDs 76
SH7HU(-R) Slot Status LEDs 77
SH7HU(-R) Network Element Status LEDs 79
SH9HU and SHX9HU Shelf LEDs 81
SH9HU and SHX9HU Fan Status LEDs 82
SH9HU and SHX9HU Slot Status LEDs 83
SH9HU and SHX9HU Network Element Status LEDs 85
OTDR Shelf LEDs 87
Troubleshooting Power Supply Units 88
PSU/1HU-R-AC and PSU/1HU-R-DC-200 89
PSU/7HU-AC and PSU/9HU-AC 90
PSU/7HU-DC, PSU/7HU-DC-HP, PSU/7HU-DC-800, PSU/X9HU-DC-800, and PSU/9HU-DC 91
PSU/7HU-R-DC 92
Core Type Channel Modules 95

Troubleshooting Core Type TDM Channel Modules 96
4TCC-PCN-2G1U+2G5 97
4TCC-PCTN-2G7+10G 104
4TCC-PCTN-10G+40G-L#DC 111
10TCC-PCN-2G7US+10G 120
10TCC-PCTN-4GU(S)+10G 127
10TCC-PCTN-10G+100GB and 10TCC-PCTN-10G+100GC 134
10TCC-PCN-3GSDI+10G 143
10TCC-PCN-40GU+100G 150
16TCC-PCN-4GUS+10G 157
Troubleshooting Core Type WDM Channel Modules 165
2TWCC-PCN-2G7U 166
2WCC-PCN-10G 173
4WCC-PCN-10G 180
WCC-PC1N-2G7U 187
WCC-PCTN-10G 194
WCC-PCTN-100G(A,B) 202
WCC-PCN-100G 210
WCC-TN-40G-L#DC 220
10WXC-PCN-10G 226
4 FSP 3000R7 Maintenance and Troubleshooting Manual - Product Release 16.2 - Document Issue A
Access Type Channel Modules 231
Troubleshooting Access Type TDM Channel Modules 232
2PCA-PCN-10G 233
2TCA-PCN-1G3+2G5 239
2TCA-PCN-622M+2G5 246
4TCA-LS+1G3-V 252
4TCA-PCN-4GU(S)+4G 257
8TCA-PC-2G1U+10G-V 264
10PCA-PCN-1G3+10G 270
Troubleshooting Access Type WDM Channel Modules 276
2WCA-PCN-10G 277
WCA-PC-10G-V 281
WCA-PCN-2G5U 286
5WCA-PCN-16GU 297
Enterprise Type Channel Modules 301

Troubleshooting Enterprise Type TDM Channel Modules 302
5TCE-PCTN-8GU+(AES)10GS 303
5TCE-PCN-8GU+(AES)10GS 312
5TCE-PCTN-10GU+(AES)10G 321
5TCE-PCN-10GU+(AES)10G 330
8TCE-ESCON+2G5-V 339
8TCE-GLINK+2G5-V 343
10TCE-PCN-10G+100G(-GF) 347
10TCE-PCN-16GU+(AES)100G and 10TCE-PCN-16GU+AES100G-BSI 353
Troubleshooting Enterprise Type WDM Channel Modules 368
WCE-PCN-100G(B) 369
4WCE-PCN-16GFC 377
Management and Switch Modules 385

Troubleshooting Management Modules 386
NCU 386
Troubleshooting Serial Connection Issues 387
Troubleshooting Ethernet Connection Issues 388
Troubleshooting NCU Configuration Issues 389
NCU LED Status 390
NCU-II-P 392
NCU-S 394
SCU 396
SCU-II 399
SCU-S 401
OSCM 403
UTM and UTM-S 405
PSCU 408
CEM/9HU 411
Troubleshooting Switch Modules 414
OPPM 415
VSM 418
RSM-OLM#1630 420
RSM-SF 423
Reconfigurable Optical Layer Devices 425
ROADM-C40/40/OPM-3HU/2DC 426
ROADM and CCM Modules 429
4-OPCM 434
Optical Filters (Passive Modules and Shelves) 437
Optical Amplifiers 441

Fixed Pump-Power EDFA Modules 442
Fixed Gain-Controlled EDFA Modules 444
Fixed Gain-Controlled, Single-Stage EDFA Modules 445
Fixed Gain-Controlled, Double-Stage EDFA Modules 447
Variable Gain(-Controlled) EDFA Modules 451
Variable Gain-Controlled EDFA Modules 452
Variable-Gain EDFA Modules 458
RAMAN-C10 Module 459
2RAMAN-C15-LL Module 467
AMP-S20H-C15 and AMP-S20L-C15 Modules 475
EDFA-S20H and EDFA-S20L Modules 486
2EDFA-S20L-S10L Modules 495
Dispersion Compensation Modules 507
NCU Troubleshooting 509

Viewing IP Addresses 510
Setting NCU Passwords to Default Values 511
Resetting Passwords in First Generation NCUs 512
Resetting Passwords in Second Generation NCUs 514
Controlling Boot Loader Access 516
Restarting the NCU 517
Warm-Starting the NCU 517
Cold-Starting the NCU 518
Deleting the Active Database 520
Replacing the NCU Compact Flash 521
Removing the NCU Compact Flash 521
Installing Compact Flash in an NCU 523
Replacing an NCU 526
Basic Requirements 527
Required Information 527
Required Equipment 529
Replacing a Malfunctioning NCU 530
Replacing a First Generation NCU with an NCU-II 537
Control Plane Maintenance and Troubleshooting 543

Maintaining Tunnels and Services 544
Converting an Existing Service to Control Plane Management 544
About WDM Cross-Connections 548
Converting a Service from Control to Management Plane Ownership 550
Repairing Tunnels after Replacing a Network Element 551
Viewing Traffic Engineering Information in an NE 555
Manually Restoring a Path 559
Troubleshooting Control Plane Issues 560
Checking Status of TE Links 560
Verifying List of TE Routers 560
Checking Synchronization Status of TE Links 561
Verifying Logical Interfaces 562
Verifying Physical Connections 562
Checking OSPF Settings 563
Verifying All Nodes are Listed 563
Ensuring the Correct Topology 564
Verifying OSPF Neighbors 565
Resolving Connection Failures Resulting from MTU Size Mismatches 566
Tracing a Channel Through the Node 568
General Module and Management Configuration 569

Configuring SNMP Settings 570
Configuring In-band Management 571
In-band Management on Channel Modules 571
In-band Management Configuration Example 571
Example of Configuring the ECC 572
Example of Configuring the NCU 573
Example of Disabling the Far-End LAN IP Interface 574
Example of Verifying Connectivity 574
Configuring Loopbacks 575
Configuring a Client Interface Loopback 576
Configuring a Network Interface Loopback 576
Configuring Clock Speeds 578
Setting Auto Laser Shutdown 579
Forcing and Releasing Lasers 581
Checking for Higher-Level NTP Servers 583
Configuring an OSCM 584
Configuring OSPF 585
Tracking a Channel in a Node 586
Tracking a Channel through a Node 586
Configuring Trace Monitoring 589
Configuring SONET/SDH Traces 589
Configuring OTN Traces 590
Configuring Wavelengths 593
Reconfiguring Wavelengths 593
Restarting Modules 595
Exporting Network Element Logs 597
Configuring Equipment Capabilities 598
Increasing Capability 598
Viewing Capability Level 598
Updating Software, Firmware, and Database 601

About Software and Database Files 602
The Software Package 602
Handling of Files 603
Software and Database Compatibility 604
Software Update and Switchback 604
About NE Software Version and File Names 606
Database Restoration Guidelines for Control Plane Users 607
Fixing Corrupted Database on a Single NE 607
Ideal Case 607
Case 1: Signaling state for tunnel is present in the network, but the restored database
has no knowledge of it 607
Case 2: Restored database has a tunnel marked "in-service", but no signaling state
(connections) is present in the network 607
Case 3: Restored database has a tunnel marked "in-service", signaling state for the tun-
nel is present, but the connections in the database do not match those in the network 608
Case 4: Database was restored while tunnels were in service 608
Provisioning a Green-field Network 609
Backing Up and Restoring the Database 610
Backing Up the Database 610
Backing Up the Database at a Scheduled Time 611
Viewing Files Stored on the NE 613
Restoring the Database 614
Viewing Module Firmware Versions 616
Updating the NE Software Release 617
Transferring Software to the NCU 620
Transferring Firmware Packages to All Modules (Native) 621
Activating Software 623
Scheduling Software Activation 624
Transferring and Activating Firmware on All Modules 625
Performing Other Software Update Actions 628
Reverting to the Previous Software Release 628
Updating Modules with Encryption 628
Enabling Update of Modules with Encryption 629
Updating Encryption Module Firmware 629
Updating HD Module Firmware 630
Updating a Module 631
Updating Modules of the Same Type 632
Transferring Files To/From the NE 633
Uploading Files from the NCU 633
Downloading Files to the NCU 634
Downloading Files from the SCU to the NCU 635
Performance Management 637

Introduction 638
Performance Monitoring at the Physical Layer 639
Recorded Measurements 639
Real Time Measurements 640
Physical Layer Counter 641
Performance Monitoring at the Data Layer 642
SDH/SONET Performance 643
OTN Performance 644
Physical Coding Sublayer (PCS) Performance 644
Sub-aggregate Layer Performance 645
Ethernet Performance 646
GFP Frame Performance 648
EVC Frame Performance 649
Performance Records 650
Record Types 650
Record Content 651
Record Storage 652
Saving Performance Monitoring History Records 652
Exchanging Equipment 653

Replacing an Optical Module 656
Removing an Optical Module 656
Installing an Optical Module 660
Replacing an Encryption Module 668
Removing an Encryption Module 668
Installing an Encryption Module 671
Replacing a Raman Amplifier 676
Replacing Pluggable Transceivers 677
General Information 677
Safety Guidelines 678
Removing an SFP or XFP Transceiver 679
Installing an SFP or XFP Transceiver 682
Removing a CFP Transceiver 686
Installing a CFP Transceiver 689
Replacing Pluggable Transceivers in a Control Plane-based network 694
Replacing an N Port Pluggable Transceiver with the Same Type 694
Replacing an N Port Pluggable Transceiver with a Different Type - Method 1 695
Replacing an N Port Pluggable Transceiver with a Different Type - Method 2 695
Replacing a C Port Pluggable Transceiver 696
Replacing Power Supply Units 697
General Information 697
Replacing a PSU/1HU-R-AC(-200) or PSU/1HU-R-DC-200 699
Replacing a PSU/7HU-AC, PSU/7HU-AC-HP, or PSU/7HU-AC-800 704
Replacing a PSU/7HU-DC, PSU/7HU-DC-HP, or PSU/7HU-DC-800 709
Replacing a PSU/7HU-R-DC or PSU/7HU-R-DC-HP 716
Replacing a PSU/9HU-DC, PSU/X9HU-DC-800, or PSU/9HU-AC 721
Replacing, Upgrading, or Downgrading PSUs in a Mixed PSU Configuration 726
PSU Power Requirements During Insertion and Removal 733
Replacing Fan Units and Fan Modules 737
Replacing a FAN/Plug-In 737
Replacing a FAN/9HU or FAN/X9HU 739
Replacing a FAN/1HU 742
Replacing Air Filter Pads 746
Replacing a PSU/1HU-R-AC-200 Air Filter Pad 746
Replacing a 7HU/9HU-Shelf Air Filter Pad 747
Replacing the SH1HU-R/PF Shelf Air Filter Pad 749
Replacing an SH1HU Shelf 752
Replacing an SH7HU(-R), SHX9HU, or SH9HU Shelf 759
Final Steps When Replacing a Master Shelf 760
Final Steps When Replacing a Main Shelf 761
Replacing a 40CSM/2HU Shelf 763
Removing and Mounting Front Covers 768
Removing an SH7HU, SH9HU, or SHX9HU Front Cover 768
Mounting an SH7HU, SH9HU, or SHX9HU Front Cover 769
Removing the 40CSM/2HU Front Cover 770
Mounting the 40CSM/2HU Front Cover 771
Removing and Inserting a Dummy Module 773
Inserting a Dummy Module 773
Removing a Dummy Module 775
Generating a Support Data File 777

Collecting Support Data using NED 778
Collecting Support Data using Shell 779
Alarm and Event List 783

Alarm and Event Nomenclature 784
Standing Conditions 785
Transient Conditions 1076
Database Change Events 1131
Related Documents Overview
Refer to these documents when planning, installing, provisioning, operating,
troubleshooting, and working with FSP 3000R7 equipment and management tools:
Planning
• System Description
This reference document describes the architecture and principles behind major
features such as transport protocols, protection, optical amplification, reconfigurable
OADMs, DCN, control plane, and management-related features.
• Hardware Description
This describes physical details about each module such as front plate pictures and
markings, signal path description with block diagrams, and allowed placement and
labeling of the modules. For details related to the supported configurations of each
module, parameter values, and other management related data, refer to the
Management Data Guide.
Starting with Release 13.1, the System Description and Hardware

Description replace the Planning and Engineering Guide.
Note
• Module and System Specification

This document contains the technical specifications for the FSP 3000R7.
• Pluggable Transceiver Module Specification
This document contains the descriptions and technical specifications for pluggable
transceiver modules used in ADVA Optical Networking products.
• SH1PCS Technical Description
This document provides information about the FSP 3000R7 Ethernet NT (SH1PCS)
system such as PCP mode, automatic management provisioning, Ethernet ring
protection switching, Network topology, and service applications. It also describes
the hardware, such as:
l SH1PCS system shelf including connectors

l access port interface modules (XG-1S-CC, GE-8S-CC, GE-8E-CC)
l fan module
l power supply units (PSU/AC-200 and PSU/DC-200)
l power cables
l supported pluggable interfaces,
and presents detailed technical specifications.
Installing
• Critical Warnings
This document lists the most important safety requirements. Read this document
before installing, provisioning, or operating the FSP 3000R7.
• Safety Guide
This document describes important safety precautions that are to be read and
observed before attempting to install, provision, configure, or operate the FSP
3000R7. Therefore, read this document first.
• Installation and Commissioning Manual
This document includes procedures describing how to install an FSP 3000R7 node.
It covers everything from unpacking the shipment, rack-mounting the equipment,
connecting optical fibers, and includes basic commissioning.
• SH1PCS Installation and Operations Manual
This document provides detailed information required to successfully install the FSP
3000R7 Ethernet NT (SH1PCS) as well as how to provision, and operate the system
using the eVision Web Browser Management Tool. It also contains rules and
dependencies needed for configurations.
Provisioning and Operating

• Network Element Director Online Help
This document describes how to provision, operate, and monitor the FSP 3000R7
system using Network Element Director. For detailed information about configuration
and management options, refer to the Management Data Guide.
• Provisioning and Operations Manual
This document describes how to provision, operate, and monitor the FSP 3000R7
system using the Craft Console. Refer to the Management Data Guide while
following the procedures in the Provisioning and Operations Manual to look up
provisioning and management-related details.
• SH1PCS Installation and Operations Manual
This document provides detailed information required to successfully install the FSP
3000R7 Ethernet NT (SH1PCS) as well as how to provision, and operate the system
using the eVision Web Browser Management Tool. It also contains rules and
dependencies needed for configurations.
Working with Management Tools

• Management Data Guide
This document contains all provisionable and read-only parameters for each module,
as well as the performance counters for the modules. This is a useful reference both
when planning and engineering a network and while following the instructions in the
management tool procedural documentation.
• TL1 Commands and Syntax Guide
This document describes the TL1 commands available to provision, configure,
operate, and monitor the FSP 3000R7.
• TL1 Module Parameters Guide
This document provides reference information about all TL1-based provisioning and
performance monitoring options for the FSP 3000R7 modules, as well as the
conditions for them.
• SH1PCS CLI Handbook
This document provides reference information about Command Line Interface
commands of the FSP 3000R7 Ethernet NT (SH1PCS) used for performance
monitoring, provisioning, operation, administration, and maintenance.
Troubleshooting
• Maintenance and Troubleshooting Manual
This document describes how to troubleshoot the FSP 3000R7 hardware and
software and perform maintenance tasks such as software and firmware upgrades.
• TL1 Maintenance and Troubleshooting Manual
This document describes how to troubleshoot the FSP 3000R7 when managing it by
using TL1.
• SH1PCS Maintenance and Troubleshooting Manual
This document describes how to troubleshoot the FSP 3000R7 Ethernet NT
(SH1PCS) system and perform Etherjack test procedures such as loopback,
Etherjack service assurance, connectivity fault management, and service activation.
This page intentionally left blank.
Preface
The Preface gives general information for the effective use of the Fiber Service Platform
(FSP 3000R7) Maintenance and Troubleshooting Manual.
This publication is provided "as is" without express or implied warranty for accuracy and
completeness.
This chapter consists of these sections:
Purpose and Scope 16

Audience 16
Documentation Revision History 16
Document Conventions 23
Obtaining Documentation 25
Documentation Feedback 25
Obtaining Technical Assistance 25
Contact ADVA Optical Networking 26
Purpose and Scope
Purpose and Scope

The purpose of the FSP 3000R7 Maintenance and Troubleshooting Manual is to provide
information for troubleshooting the FSP 3000R7.
This document contains step-by-step procedures and information to identify and resolve
issues and alarms resulting while operating the FSP 3000R7.
Audience
This documentation is primarily intended to be read by experienced users, especially for
trained and authorized personnel or service personnel.
It is assumed that personnel responsible for general troubleshooting have the training
required in electronic equipment maintenance.
It assumes that personnel responsible for optical troubleshooting have training in laser-
based technology.
It assumes that personnel have skills in safety information concerning the laser
classification system and the hazard levels of the FSP 3000R7.
Please use the Network Element Director (NED) to execute the

procedures in this manual, unless a procedure specifically references the
Craft Interface.
Note
Documentation Revision History

For an overview of the content of any one product release, please refer to the Release
Notes provided with your system.
Product Document Document Issue Date Description

Release Number Issue
8.3 80000003740 Issue A February Update of alarm and event list and updated
2009 according to the content of this release.
Issue B February Updated according to the content of this

2009 release.
Issue C May 2009 Added and corrected the section in Chapter

1.

9.1 80000003772 Issue A June 2009 Updated according to the content of this
release.
Issue B September Updated information about LEDs

2009
9.2 80000008782 Issue A November Updated according to the content of this

2009 release.
9.3 80000010469 Issue A March 2010 Updated according to the content of this
release.
Issue B April 2010 Updated LEDs of the Reconfigurable

Optical Layer Devices and the Node
Channel Trace description.
10.1 80000011730 Issue A September Updated according to the content of this

2010 release.
10.2 80000014008 Issue A October Updated according to the content of this

2010 release.
Issue B December
2010
Issue C March 2011 This issue covers fixes included in

R10.2.2.
10.3 80000014670 Issue A May 2011 Updated according to the content of this
release.
Issue B July 2011
release.
Issue B April 2012 Content improvements in Chapter 12 and

14 as well as updates in the Alarm and
Event List, Appendix A.

11.2 80000020926 Issue A October Updated according to the content of this

2012 release.
Issue B January Updated per R11.2.2, including the

2013 following new alarms in Appendix A: SF-
LINK__VECTOR, ODU-TRIB-MSIM.
The following alarms in Appendix A were
modified: SF-LINK, SD-LINK__VECTOR,
MEA-ALW.
Issue C April 2013 Updated per R11.2.3, including the

following changes:
Appendix A:
New alarm LKDO-AMP-APS.
Removed event NTPSYNC-CHG.
Modified troubleclearing steps for HWFLT
alarm.
Chapter 16:
Added subsection "General Information" to
section "Power Supply Units"
12.1 80000024436 Issue A August 2013 Updated according to the content of this
release, including the following changes to
Appendix A:
• New standing conditions: MEA-CONF,
CDC_CONDITION, CRYOFFEN_
CONDITION, FWDASEPILOT_
CONDITION, FWDASEPILOT-FAIL,
LKDO-AIS-ODU-RCV, LKDO-AIS-
ODU-TRMT, LKDO-GAIS,
OOSDSBLD-LCK-ODU-RCV,
OOSDSBLD-LCK-ODU-TRMT,
SWDX-INHIBIT.
• New transient conditions: DBACT,
EQLZ-RAMAN.
• Deleted standing conditions:
INHIBITED, T-SE-PCS-HT_15MIN.
• Deleted transient condition: T-SE-
PCS-HT_1DAY.
• Modified conditions: EQLZ_
CONDITION, EQLZ-ADJUST,
FANANR, FANFLT, SPEQ-LOCKED,
TIFALM.

12.2 80000026932 Issue A December Updated according to the content of this

2013 release, including the following changes to
Appendix A:
• Modified ASETAB-FAIL_ASELOW,
ASETAB-FAIL_BR, ASETAB-FAIL_
OSC, ASETAB-FAIL_PILOT,
ASETAB-FAIL_SIG, FANANR,
HWANR, KEXLFT-DEG, SPEQ-
LOCKED, and T-SUBTEMP-FHT
conditions.
• Added new condition WARM-UP.
Issue B January Added client channel card protection-

2014 related LED troubleshooting steps for
2TWCC-PCN-2G7U modules.
Appendix A:
• Modified HIBER, LKDO-OCI-ODU,
LOCAL_FAULT, FWPM-NSA,
FWPM-SA, OCI-ODU, and SD-
ATRCV conditions.
• Added the RESTNNUM-CHANGED
condition.

13.1 80000028834 Issue A August 2014 Updated according to the content of this
Appendix A:
• Added AVLNDP-RESTRICTED,
CLEANUP-COMPL, CPY-FILE-
PRTL, CSF-VF, EQLZ-AUTO, EQLZ-
COMPL, EQLZ-START, FILE-PA-
COMPL, FILE-PA-FAIL, FILE-PA-
START, INSTALL__COMPL,
INSTALL__FAIL, INSTALL__START,
LKDO-CSF-VF, LKDO-TEMPA,
LOOMFI-OPU, OTDR, RVSN-BLKD,
RVSN-NOTREADY, RVSN-READY,
RVSN-UNKNOWN, SWITCH__
COMPL, SWITCH__FAIL, SWITCH_
_REJECT, SWITCH__START, and
TNL-ANR conditions.
• Deleted the BOOT__INSTCOMPL,
BOOT__REJECT, CPY-FILE-PRTL__
00, and CPY-FILE-PRTL__50
transient conditions.
• Modified the BOOT__COMP, BOOT__
START, BOOT__FAIL, EQLZ-DENY,
EQLZ-FAIL, EQLZ-NULL, EQLZ-
PASS, EQLZ-RAMAN, EQLZ-WAIT,
PWRCONS-EQUD, PWRCONS-
PROV, SPEQ-PPCLIMIT, SYSRES_
_RELOAD conditions.


Appendix A:
• Added the EQLZ-RESTORE condition.
• Modified T-LATENCY-HT, T-
LATENCY-LT, and
VOLTIN conditions.
Issue B November Implemented these changes:

2014 • Corrected the probable cause and
suggested corrective action for the T-
DGD-HT condition.
• Corrected the default severity of the
KEXLFT-DEG condition.
• Added a note regarding installation of
optical modules.
• Revised the replacement, upgrade,
and downgrade procedure for mixed
PSU configurations.
Appendix A:
• Modified INSTALL__COMPL,
INSTALL__FAIL, INSTALL__START,
SPGAIN-OOR-LO, SWITCH
conditions.
• Added EPT-UAV, PEER-AID1-
RMVD, PEER-AID2-RMVD, PEER-
AID3-RMVD, PEER-AID4-RMVD,
PEER-LINK1, PEER-LINK2, PEER-
LINK3, PEER-LINK4, SF-
COM conditions.
Issue B May 2015 Added Craft-based steps to provision SCU

ring interconnections after replacing
SH7HU/SH9HU shelves.


Appendix A:
Added ACP-LINK, ACP-APS-UAV, ACP-
RMVD, ACP-UAS, FRCDWKSWBK,
FRCDWKSWPR, LKDO-OCI-ODU-TRMT
conditions.
Modified LKDO-AIS-ODU-RCV condition.
Issue B October Updated troubleshooting guidelines for the

2015 LASER (Laser-Fail) condition.
Added a note in "Installing an Optical
Module" about properly seating 10WXC
modules in SHX9HU shelves.
15.2 80000035929 Issue A January Updated according to the content of this

Appendix A:
Added FLAT-BAT, FWPHASH-FAIL,
FWPHASH-PASS, TAG-FAIL, TAG-
LFTDEG, TAG-RESET conditions.
Modified ASETAB-FAIL__SIG condition.
Issue B January Updated according to the content of this

2016 release.
16.1 80000037345 Issue A April 2016 Updated according to the content of this
Appendix A:
Added CRYINTFAIL and MEA-AUTOSRV
conditions.
Issue B August 2016 Added PSU/7HU-DC-HP revision 2.02 to

the section, "Replacing, Upgrading, or
Downgrading PSUs in a Mixed PSU
Configuration."
Modified PAUSE-CRYPW condition.
16.2 80000042876 Issue A April 2017 Updated according to the content of this
release, including these chages to
Appendix A:
Added AMPOUT-FAIL, BPCOMMLOSS,
LOA, LOCAL_FAULT-RX, LOCAL_
FAULT-TX, LOS-P, MEA-ALW, MEA-
RED, MODEMSYNC, PWRNOAVAIL,
SSF-OTU, SSF-RX, T-PWRUSED-FHT,
T-PWROUT-FHT, VOLTIN-LOW,
VOLTOUT-FAIL conditions.
Modified HWFLT condition.
Document Conventions
This section lists the common typographical conventions and symbols used throughout
this documentation.
Typographic Conventions
The documentation follows these typographic conventions:
Convention Description
boldface font Indicates keywords and emphasized words when appearing

in main text areas. All warnings are in boldface font.
blue font Indicates a reference to a chapter, section, figure, table or

related documentation when appearing in main text areas.
CAPITALIZED font Refers to the keys on your keyboard, e.g. ENTER marked ↵.
courier Courier font is used to identify words that can be read from
or typed into the command line interface.
[ ] Elements in square brackets are optional.
| Alternative elements are separated by a vertical bar.
^ The symbol ^ represents the key labeled Control - for

example, the key combination ^D means that you have to
hold down the Control key while you press the D key.
<> References are enclosed in angle brackets, for example:

<Esc> The escape key, marked Esc
<Enter> The Enter key, marked ↵
<username> This reference, including the angle brackets, is
replaced by the appropriate user name.
Nonprinting characters, such as passwords.
“ ” Double inverted commas are used to enclose quoted text.
• (bullet symbol) Used in bulleted list of items where the sequence of items is
not relevant.
1, 2, 3 ...or These numbering styles are used in lists of items where the
a), b), c)... sequence of items is relevant.
* or 1, 2 etc. These are used to point to table footnotes. The markers in

the text are arranged as continuous superscript numbers.
Footnote text (in smaller typeface) is placed at the bottom of
a table and starts with a superscript number.
-> Refers you to additional information.
Safety Symbol and Message Conventions

The safety alert symbols with the appropriate signal words and the note signs below are
used throughout this documentation to identify warnings, cautions, and notes.
This symbol accompanies any instruction that draws attention to

the risks caused by electricity. These risks could result in death or
serious injury if the instruction is ignored or not followed correctly.
WARNING
This symbol accompanies any instruction that draws attention to a

potentially hazardous situation/condition. This situation/condition, may
result in minor or moderate injury, if the instruction is ignored or not
CAUTION followed correctly.
This symbol accompanies any instruction that draws attention to the risk
of possible laser radiation. This risk may result in serious eye injury, if
the instruction is ignored or not followed correctly.
CAUTION
This symbol accompanies any instruction that draws attention to the

possibility of equipment damage due to electrostatic discharge (ESD).
Damage can occur, if the ESD-prevention instructions are ignored or not
followed correctly.
This symbol accompanies any instruction that draws attention to the risk of
equipment damage, malfunction, process interruption, or negative impacts on
surroundings. These events can occur if the instruction is ignored or not followed
correctly.
A symbol that draws attention to the necessity and importance of

carefully reading all instructions before any installation or operation takes
place. Failure to do so may result in personal injury or damage to
equipment.
This symbol accompanies any instruction that draws attention to the

proper disposal of waste electrical or electronic equipment and its
components. Disregard of the instruction can threaten the environment.
This symbol accompanies any statement, supplemental information, or

helpful recommendation that should be observed.
Note
Obtaining Documentation
Obtaining Documentation
World Wide Web

You can access the most current ADVA Optical Networking documentation on the World
Wide Web by using the Customer Portal at:
http://portal.advaoptical.com/
Contact your ADVA Optical Networking sales representative for details.
Ordering Documentation
ADVA Optical Networking customers can order the FSP 3000R7 User Documentation
Suite and additional literature through a local ADVA Optical Networking sales
representative. For more current product release information, please refer to the home
page or contact Technical Services. See “Obtaining Technical Assistance” on p. 25 and
“Contact ADVA Optical Networking” on p. 26 for contact details.
Documentation Feedback
We want our FSP 3000R7 documentation to be as helpful as possible. Feedback
regarding the manual is therefore always welcome.
You can email your comments/suggestions to:
[email protected]
To submit your comments/suggestions by mail, use the following address:
ADVA Optical Networking SE
Technical Documentation
Märzenquelle 1-3
98617 Meiningen-Dreissigacker
Germany
We appreciate and value your comments/suggestions to improve the quality of the
manual.
Obtaining Technical Assistance

Product Maintenance Agreements and other customer assistance agreements are
available for ADVA Optical Networking products through your ADVA Optical Networking
distribution channel. Our service options include:
• 24 x7 telephone support
• Web-based support tools
Contact ADVA Optical Networking
• On-site support
• Technical training, both on-site and at ADVA facilities in Germany and the USA
• Expedited repair service
• Extended hardware warranty service
Customer Portal
The ADVA Optical Networking Customer Portal provides a suite of interactive networking
services that provide immediate access to company information and resources at any
time, from anywhere in the world. This highly integrated internet application is a powerful,
easy-to-use tool for doing business with ADVA Optical Networking.
The broad range of features and services provided by the portal helps customers and
partners to streamline business processes and to improve productivity. Through your
portal login, you will find information tailored especially for you, including networking
solutions, services, and programs. In addition, you can resolve technical issues by using
online support services, download and test software packages, and order ADVA Optical
Networking training materials.
Access the Customer Portal by using the ADVA Optical Networking home page at:
http://portal.advaoptical.com
Email questions regarding the Customer Portal to:
[email protected]
Technical Services
Technical services are available to warranty or maintenance contract customers who
need technical assistance with a product from ADVA Optical Networking that is under
warranty or covered by a maintenance contract. To contact ADVA Optical Networking
Technical Services, go to the ADVA Optical Networking home page at:
http://www.advaoptical.com/en/about-us/contact-us.aspx
To contact ADVA Optical Networking by email, use the following address:
[email protected]

ADVA Optical Networking Europe, Middle East and Africa
Martinsried/Munich, Germany
+49 (0)89 89 06 65 0
ADVA Optical Networking America

Norcross, GA, USA
+1 687 728 8600
ADVA Optical Networking Asia

Shenzhen, China
+86 755 8621 7400
www.advaoptical.com
Chapter 1
Preparation for Troubleshooting

This chapter describes the requirements and preparatory steps for troubleshooting.
It contains the following sections:
“Requirements” on p. 30, which describes the devices and tools needed additionally to
troubleshoot the FSP 3000R7.
“Cleaning and Inspecting Fibers and Ports” on p. 32, which describes the steps before
troubleshooting can be started.
“Handling Equipment” on p. 47, which gives guidelines for correctly handling FSP 3000R7
shelves, optical modules, pluggable transceivers and fiber-optic cables. Furthermore, it
addresses the requirements optical fiber connectors must fulfill to be used in the optical
fiber system.
Requirements
Requirements
Before you start with troubleshooting, ensure the following:
• The FSP 3000R7 is properly powered.
• Each optical connector is cleaned by using the optical cleaning kit (see “Cleaning and
Inspecting Fibers and Ports” on p. 32).
• Unconnected optical fiber connectors are protected with caps.
• Unconnected optical ports are protected.
• All equipment is updated to the firmware versions that match the NCU software (no
firmware mismatch alarms are raised). If needed, update the firmware with the
instructions in “Updating Software, Firmware, and Database” on p. 601.
Required Personnel
For some tasks, personnel are needed on all sites involved in the link, e.g. to insert
attenuators or measure OSNRs remotely.
Recommended Equipment
The following tools are required to troubleshoot the FSP 3000R7.
• Optical Cleaning Kit or Pen-Type Ferrule Cleaner
Optical connectors have to be cleaned with an optical cleaning kit or a pen-type
ferrule cleaner. ADVA Optical Networking accepts the usage of any of the standard
kits or pen-type ferrule cleaners. The cleaning kit must be equipped with an alcohol-
based cleaner and a dry wipe.
• Optical Power Meter with Patch Cables
The optical power meter is used to measure the amount of power being transmitted
across a fiber optic cable. There are many different types of connectors available for
fiber cable. You need a series of patch cables that are terminated with ST, SC,
FC/PC, ESCON, FDDI (MIC) and E2000.
• Wrist Strap
A wrist strap for grounding is needed while you troubleshoot the FSP.
As the FSP 3000R7 contains electrostatic discharge-sensitive devices,

a grounded anti-static wrist or heel strap is required when handling the
unit.
• Optical Time Domain Reflectometer

The Optical Time Domain Reflectometer is used very seldom to troubleshoot the
FSP 3000R7 and therefore not strongly required. The Optical Time Domain
Reflectometer informs you of the length of any given fiber cable, of the location of
splices, connectors and bends, of the attenuation of the link and of the back
reflection of the link.
• Bit Error Rate or Protocol Tester
A Bit Error Rate Tester or Protocol Tester drive a healthy load of data across the link
before considering your issue resolved.
• Optical Spectrum Analyzer
Requirements
An optical spectrum analyzer allows you to see which optical channels are present
and determine the power level and optical signal/noise ratio of each channel.
• Optical Caps and Blind Plugs
Optical caps and blind plugs are needed to protect and close the connectors and
interfaces.
• Screwdriver
The following screwdrivers are required for any troubleshooting procedure:
o
one Pozi screwdriver No.1
o
one Pozi screwdriver No.2
o
one Torx screwdriver size 20
o
one Phillips screwdriver No.2
Cleaning and Inspecting Fibers and Ports

Perform the procedures in this section to clean and inspect optical cabling and port
connections. Inspection and cleaning are critical and must be performed prior to each
mating.
Risk of equipment damage:

Dirty fiber can impair system performance.
The network fiber and patch panels used to connect ADVA equipment to
the network fiber must have discrete back reflection level values
measured with an optical time-domain reflectometer (OTDR) to be below
-27 dB. For spans using Raman amplifiers, the discrete back reflection
levels are required to be < -32 dB.
Higher back reflection levels may cause BER penalties through in-band
crosstalk generated by multipath interference. The OTDR
Note measurements need to be taken with a fiber spool having a length
exceeding the OTDR “dead-zone.” One end of the spool is connected to
the OTDR and the other to the patch panel. This ensures reliable back
reflection and loss measurement of the near-end patch panel. OTDR
measurements should be taken in both directions of a fiber.
Quality connections between fiber-optic equipment require clean fiber-optic components.

Cleaning the fiber-optic equipment is one of the most basic and important procedures for
maintaining fiber-optic systems. Any contamination in the fiber connection can cause
failure of the component or failure of the entire system.
Even microscopic dust particles can cause a variety of problems for optical connections.
A particle that partially or completely blocks the core generates strong back reflections,
which can destabilize the laser system. Dust particles trapped between two fiber
endfaces can scratch the glass surfaces. A particle on the cladding or on the edge of the
endface can cause an air gap or a misalignment between the fiber cores, which
significantly degrades the optical signal. You must remove all foreign materials and debris
from the fiber endface before mating the connectors.
Common contaminants include:
• Oils (frequently from human hands)
• Film residues (condensed from vapors in the air)
• Powdery coatings (remaining after water or other solvents evaporate)
If they are not removed, these contaminants can be more difficult to remove than dust
particles and can also cause damage to equipment.
Risk of equipment damage:

With high-powered lasers, such as Raman amplifiers, any contaminant can be
burned into the fiber endface if it blocks the core while the laser is turned on. This
burning may damage the optical surface enough that it cannot be cleaned.
This section contains these sub-sections:

“General Reminders and Warnings” on p. 33
“Cleaning Fiber-Optic Connector Plugs” on p. 34
“Cleaning and Inspecting Connector Receptacles” on p. 37
“Cleaning and Inspecting Fiber Jumpers” on p. 38
“Cleaning Recommendation for Optical Ports of Pluggable Transceivers” on p. 45
General Reminders and Warnings

Review these reminders and warnings before inspecting and cleaning your fiber-optic
connections.
Reminders
• Always turn off any laser sources before you inspect fiber connectors, optical
components, or fiber-optic bulkhead connectors (FOBCs).
• Always make sure that the cable is disconnected at both ends or that the card or
pluggable receiver is removed from the chassis.
• Always inspect the connectors or adapters before you clean them.
• Always inspect and clean the connectors before you make a connection.
• Always use the connector housing to plug or unplug a fiber.
• Always keep a protective cap on unplugged fiber connectors to prevent
contamination.
• Always store unused protective caps in a resealable container to avoid transferring
dust to the fibers. Locate the containers near the connectors for easy access.
• Always discard used tissues and swabs properly.
• Always wear the appropriate safety glasses as required in your area.

Be sure that your laser safety glasses meet all applicable federal and
local regulations and are matched to the lasers used within your
environment.
• Never look into a fiber while the system lasers are turned on.
CAUTION • Never use unfiltered handheld magnifiers or focusing optics to

inspect fiber connectors.
• Never connect a fiber to a fiber scope while the system lasers are
on.
Never use alcohol for wet cleaning without a way to ensure that it does not leave
residue on the endface. Alcohol residue can damage the equipment.
o
Never clean bulkhead connectors or receptacle devices without a means to
inspect them.
o
Never touch the endface of the fiber connectors.
o
Never twist or pull forcefully on the fiber cable.
o
Never reuse any tissue, swab, or cleaning cassette reel.
o
Never touch the clean area of a tissue, swab, or cleaning fabric.
o
Never touch any portion of a tissue or swab where alcohol was applied.
o
To prevent contamination, never touch the dispensing tip of an alcohol bottle.
Never touch products without being properly grounded.
Best Practices
Use resealable containers to store all cleaning tools, and store endcaps in a separate
container. The inside of these containers must be kept very clean and the lid should be
kept tightly closed to avoid contamination of the contents during fiber connection.
Never allow cleaning alcohol to evaporate from the ferrule, as it can leave residual
material on the cladding and fiber core. This is extremely difficult to clean off without
another wet cleaning, which is usually more difficult to remove than the original
contaminant. Liquid alcohol can also remain in small crevices or cavities, where it may re-
emerge.
Required Tools
You will need the following tools to perform cleaning and inspection of optical cabling and
port connections:
• hand-held fiber scope
• 1.25 mm cotton swabs
• video scope
• CLETOP or clean-room tissues
• optical-grade isopropyl alcohol and canned, oil-free compressed air
These tools should be present on site before beginning the cleaning procedure.
Cleaning Fiber-Optic Connector Plugs

Use this procedure to inspect and clean all optical plugs before cabling.
Materials used for cleaning fiber-optic connectors should be consistent

with the function. (In other words, wiping cloths should be made of lint-
free, non-abrasive materials.) Use cotton swabs only if they have a
tightly wrapped tip and are talcum-free. Pure optical-grade isopropyl
alcohol (IPA) is the only solvent that should be used for cleaning optical
Note
contact surfaces. Use canned, oil-free compressed air for removing dust
from connectors.
Only Service Personnel are allowed to perform this procedure.

CAUTION
Raman amplifiers are high-powered devices. Always set the Network Port on a
Raman amplifier to disabled before removing an optical cable. Failure to disable the
network port can result optical connector damage.
Step 1 Review the contents of the Safety Guide. Also observe all caution statements
in this section.
Laser Radiation is present when the equipment is open and the

interlocks are defeated. Avoid exposure to the beam.
CAUTION
Step 2 Switch any forced laser back to auto (or off).

Step 3 Disconnect the fiber-optic cables. If no fiber-optic cables are connected,
remove the protective cover from the plugs.
Step 4 Use an optical power meter to check the output power of the common output
ports.
Handle the connectors carefully, to avoid leaving fingerprints or

otherwise contaminating the ferrule endface.
Note
Step 5 Blow off any accumulated dust or loose debris from the ferrules with canned,
oil-free compressed air.
Do not use commercial, compressed air due to the risk of oil

contamination of the fiber-optic connectors and receptacles. Always use
canned, oil-free compressed air.
Note
Step 6 Use a video scope (as shown in Figure 1 on p. 36) to inspect the ports and to
ensure that the port connectors are clean. (See Figure 2 on p. 36 for
comparison examples of clean and contaminated fiber endfaces).
Never look directly into an optical fiber connector or into an un-terminated

receptacle during service operations by using optical instruments, such
as a magnifier or video scope, unless you are absolutely certain that no
CAUTION laser radiation is being emitted from the receptacle or the fiber.
Figure 1: Video Scope
Figure 2: Clean, damaged, and dirty fiber ends
Step 7 If the ports require cleaning, open one or more port connector hinged caps from
the circuit packs.
Step 8 Blow off any accumulated dust or loose debris from the ferrules with canned,
oil-free compressed air.
Step 9 Clean the ports by using 1.25 mm cotton swabs.
Figure 3: 1.25 mm Cotton Swabs.
Step 10 After cleaning and inspecting a port, close the cap immediately on any port that
you are not cabling, to prevent contamination of the connector.
Step 11 If the connector is still dirty, repeat the dry cleaning technique.
Step 12 Inspect the connector again using the video scope. If the connector is still dirty
after a second dry cleaning, clean it with a wet cleaning technique, followed
immediately with another dry cleaning, to ensure that no residue is left on the
endface.
To perform a wet cleaning, gently wipe the ferrules and endface surfaces of the
connector plugs using a pad saturated with optical-grade isopropyl alcohol.
Make sure that the pad makes full contact with the endface surfaces.
Dry the connector surfaces with canned, oil-free compressed air or let them air
dry for 5 seconds.
Wet cleaning is not recommended for bulkheads and receptacles. Damage to the
equipment can occur.
Step 13 Inspect the connector again. If the contaminant still cannot be removed, repeat
the cleaning procedure using a fresh surface on the pad.
Do not touch the connector surfaces after cleaning.

If the endface surface of the connector remains dirty after repeated
Note cleaning, replace the fiber-optic cable.
Step 14 Attach the fiber connector plug to the corresponding receptacle. If the cleaned
connectors are not going to be used right away, cover them with protective
caps/plugs to prevent contamination.
Never use alcohol or wet cleaning without a way to ensure that it does not leave
residue on the endface. Alcohol residue can cause equipment damage.
Cleaning and Inspecting Connector Receptacles

The procedure described above for fiber-optic connector plugs should not be applied
routinely to fiber-optic connector receptacles. The receptacles in the modules have been
cleaned and connected by the manufacturer.
The operation of the system should be free of errors if the customer provides clean
connector plugs on the application side.
Do not clean the inside of the receptacles unless you suspect light power
is reduced due to contamination.
Note
Only authorized personnel are allowed to perform this procedure.

CAUTION
Step 1 Review the contents of the Safety Guide. Also observe all caution statements
in this section.
Step 2 Check the operating status of the equipment and the current hazard level. If
any module in the system is operating in “Forced On” mode, this could have an
effect on the hazard level of the NE.
Laser Radiation is present when the equipment is open and the

interlocks are defeated. Avoid exposure to the beam.
CAUTION
Step 3 Clean fiber-optic connectors, as described in “Cleaning Fiber-Optic Connector

Plugs” on p. 34, before plugging them into the receptacles.
Step 4 If the optical receptacle is contaminated, carefully insert the extension tube of
the compressed air can into the optical receptacle and blow dry, oil-free air into
the connector. Avoid touching the adaptor receptacle.
Step 5 Carefully reconnect the optical connector plug, and check for proper function. If
the performance is not sufficient, repeat the cleaning procedure.
If problems persist after repeated cleaning, replace the optical module.

Send the removed module to ADVA Optical Networking Technical
Services.
Note
Step 6 If no optical fiber cable is reconnected, cover the connector receptacle with
plugs to avoid contamination.
Cleaning and Inspecting Fiber Jumpers

Use these procedures to inspect and clean fiber jumpers (fiber patch cords).
Dry Cleaning Technique Using Cartridge and Pocket-

Style Cleaners
This section describes dry cleaning techniques using cartridge and pocket-style cleaners.
Step 1 Make sure that the lasers are turned off before beginning the inspection.
Invisible laser radiation may be emitted from disconnected fibers or

connectors. Do not stare into beams or view directly with optical
instruments.
CAUTION
Step 2 Remove the fiber caps from one or more jumpers and store them in a small,
resealable container.
Step 3 Inspect the fiber using a fiber scope (as shown in Figure 4).
Figure 4: Fiber Scope
Refer to Figure 2 on p. 36 for examples of clean, damaged, and dirty fiber
endfaces.
Step 4 If the connector is dirty, clean it with a cartridge or pocket cleaner, using one of
these methods:
a) For cartridge cleaners, press down and hold the thumb lever. The shutter
slides back, exposing a new cleaning area. Proceed to Step 5.
b) For pocket cleaners, peel back the protective film for one cleaning surface.
Proceed to Step 5.
c) For manual advance cleaners, pull on the cleaning material from the
bottom of the device until a new strip appears in the cleaning window.
Proceed to Step 5.
Step 5 Hold the fiber tip lightly against the cleaning area.
a) For single, non-APC fiber connectors, rotate the fiber once through a
quarter turn (90 degrees).
b) For APC connector endfaces, hold the cleaning area at the same angle as
the endface.
Step 6 Pull the fiber tip lightly down the exposed cleaning area in the direction of the
arrow, or from top to bottom.
Do not scrub the fiber against the fabric or clean over the same surface more than
once. This can potentially contaminate or damage your connector.
a) For pocket-style cleaners, go to Step 8.

b) For single fiber connectors with the type A CLETOP, repeat the cleaning
process in the second clean slot (Step 5 and Step 6).
Step 7 Release the thumb lever to close the cleaning window (if you are using
cartridge-type cleaners).
Step 8 Inspect the connector again with the fiber scope. Refer to “Cleaning Fiber-
Optic Connector Plugs” on p. 34.
Step 9 Repeat the inspection and cleaning processes, as necessary.
Throw away any used cleaning material (either cards or material

cartridges) after use.
Note
Dry Cleaning Technique Using Lint-Free Wipes

This section describes dry cleaning techniques using lint-free wipes.
Tools - Lint-free wipes (preferably clean room quality).
Read the reminders and warnings before beginning this process.

instruments.
CAUTION
Step 2 Remove the protective end cap and store it in a small resealable container.
Step 3 Fold the wipe into a square (about four to eight layers thick). See Figure 5 on
p. 41.
Step 4 Inspect the connector with a fiber scope. Refer to “Cleaning Fiber-Optic
Connector Plugs” on p. 34. If the connector is dirty, clean it with a lint-free
wipe.
Be careful not to contaminate the cleaning area of the wipe with your
hands or on a surface during folding.
Note
Step 5 If the connector is dirty, lightly wipe the ferrule tip in the central portion of the
wipe, using a “figure 8” motion.
Figure 5: Cleaning the end of a jumper with a clean-room tissue
Do not scrub the fiber against the wipe. Doing so could cause scratches
and further contamination.
Note
Step 6 Repeat the “figure 8” wiping action on another clean section of the wipe.
Step 7 Properly dispose of the wipe.
Step 8 Inspect the connector again by using the fiber scope.
Step 9 Repeat this process as necessary.
Wet Cleaning Technique Using Lint-Free Wipes

If a “dry” cleaning procedure does not remove the dirt from the fiber endface, try this wet
cleaning method.
o
Improper cleaning can cause damage to the equipment. Isopropyl alcohol
should be removed completely from the connector or adapter. Residual liquid
alcohol can act as a transport mechanism for loose dirt on the endface. If the
alcohol is allowed to evaporate slowly off the ferrule, it can leave residual
material on the cladding and fiber core. This is extremely difficult to clean off
without another wet cleaning, which is usually more difficult to remove than the
original contaminant. Liquid alcohol can also remain in small crevices or
cavities, where it can re-emerge during fiber connection.
o
On female multi-fiber connectors, ensure that no alcohol gets into the guide pin
holes. The alcohol may come out during mating and could contaminate your
connection.
o
Read the Safety Guide before beginning this process, and observe all caution
statements in this section.

instruments.
CAUTION
Step 3 Inspect the connector with a fiber scope. Refer to “Cleaning Fiber-Optic
Connector Plugs” on p. 34.
Step 4 Fold the wipe into a square (about four to eight layers thick), as shown in Figure
5 on p. 41.
Step 5 Moisten one section of the wipe with one drop of 99% alcohol. Be sure that a
portion of the wipe remains dry.
Step 6 Lightly wipe the ferrule tip in the alcohol-moistened portion of the wipe with a
“figure 8” motion. Immediately repeat the “figure 8” wiping action on the dry
section of the wipe, to remove any residual alcohol.
Do not scrub the fiber against the wipe because doing so can scratch the endface.
Step 7 Properly dispose of the wipe. Never reuse a wipe.

Step 8 Inspect the connector again with a fiber scope.
Step 9 Repeat the process as necessary.
Wet Cleaning Using Lint-Free Swabs

This section describes wet cleaning techniques using lint-free swabs.
o
Improper cleaning can cause damage to the equipment. Isopropyl alcohol
should be removed completely from the connector or adapter. Residual liquid
alcohol can act as a transport mechanism for loose dirt on the endface. If the
alcohol is allowed to evaporate slowly off the ferrule, it can leave residual
material on the cladding and fiber core. This is extremely difficult to clean off
without another wet cleaning, which is usually more difficult to remove than the
original contaminant. Liquid alcohol can also remain in small crevices or
cavities, where it can re-emerge during fiber connection.
o
On female multi-fiber connectors, ensure that no alcohol gets into the guide pin
holes. The alcohol may come out during mating and could contaminate your
connection.
o
Do not use wet cleaning on E-2000 or F-3000 connectors because the
connector can trap the alcohol and re-contaminate the connector.
Step 1 Make sure lasers are turned off before beginning the inspection.

instruments.
CAUTION
Step 2 Remove protective end cap and store it in a small resealable container.
Step 3 Inspect the connector with a fiber scope. Refer to the “Cleaning Fiber-Optic
Connector Plugs” on p. 34 section.
Step 4 If the dry cleaning procedure did not remove the dirt from the fiber endface,
place one drop of 99% alcohol to lightly moisten a new lint-free swab. Do not
oversaturate the swab.
Have a dry lint-free swab available for drying immediately after the
cleaning. Make sure that drying swab stays clean.
Note
Step 5 Lightly press and turn the dampened swab to clean the ferrule face.
Step 6 Immediately after cleaning, lightly press and turn the second swab (dry) to dry
any remaining alcohol from the ferrule face.
Step 7 Properly dispose of the wet and dry swab. Never reuse a swab.
Step 8 Inspect the connector again.
Dry Cleaning Using Lint-Free Swabs

This section describes dry cleaning techniques using lint-free swabs.
o
Never clean bulkheads or receptacles without a way to inspect them
afterwards.
o
Read the reminders and warnings before beginning this process.

instruments.
CAUTION
Step 3 Inspect the fiber connector in the adapter or bulkhead with a fiber scope probe.
Refer to the “Cleaning Fiber-Optic Connector Plugs” on p. 34 section.
Step 4 If the adapter is dirty, select the appropriate lint-free swab according to the
connector ferrule size.
Step 5 Inspect the connector in the adapter again by using a fiber scope probe.
Step 6 Insert the clean lint-free swab into the adapter.
Step 7 Turn the swab several complete revolutions in the same direction.
Step 8 Properly dispose of the swab. Never reuse a swab.
Step 9 Repeat the cleaning process as necessary.
Vendor-Specific Cleaning Techniques

Due to the proprietary nature of many cleaning techniques the supplier should be
contacted for detailed information.
Cleaning MTP Fiber Cable Ends

One of the most important aspects of fiber cabling is ensuring the cleanliness of the cable
ends. One speck of dust or a fingerprint can severely compromise cable transmission
capability. With MTP cables, this possible hazard is compounded because of multiple
fibers and channels per cable.
• Possible loss of service

• Before inserting MTP connectors into OADM or breakout panel
ports, you must clean them with the procedure below. Failure to
Note follow this procedure may result in loss of service.
This procedure outlines proper MTP cable cleaning procedures.
Step 1 Using a 2.5 mm clean-room swab (See Figure 6), clean dust and debris from
the fiber termination area (See Figure 7 on p. 45) between the MTP alignment
pins.
Swabs as shown can be purchased from clean-room and optical

communications equipment suppliers.
Note
Figure 6: Using the Clean-room Swab
Figure 7: MTP Male Connector Tip Diagram

MTP tip face
Alignment pin
Fiber termination area
Step 2 Use the tip of a 2.5 mm clean-room swab to clean the fiber termination area on
the female MTP connector.
Step 3 Using a fiber scope or videoscope outfitted with an MTP tip, inspect the
connectors you have just cleaned.
Step 4 Contact ADVA Optical Networking to obtain a list of MTP inspection
equipment suppliers.
Step 5 Mate the MTP connectors together.
Cleaning Recommendation for Optical Ports of Pluggable

Transceivers
The contamination of the optical port of a pluggable transceiver may also lead to network
failure. Therefore, optical ports of pluggable transceivers also require proper cleaning to
ensure the fiber transmission performance.
When to Clean?
In general, if you have cleaned your optical connectors, but still experience low-power
output from an optical transceiver or a fault signal from your equipment, you should clean
the optical port of the transceiver. Try cleaning, if necessary only, e.g. if the OPT or OPR
differs more than 3dB from the real value.
How to Clean?
Do not use wet cleaning on the optical port of a pluggable transceiver because the
connectors can trap the alcohol and re-contaminate the connector.
For cleaning no use of any chemical solutions is allowed. Only mechanical wiping
method is considered to be developed.
Improper cleaning with solvents can cause possible damage to electronics.
1 For cleaning the transmitter or receiver of optical transceivers only dry cleaning is
recommended to use with lint-free sticks.
2 Do not use clean blast at all.
3 Do not use liquid cleaner or alcohol. Liquid cleaner may pollute the fiber stub or the
receiver lens. Alcohol is hygroscopic. A thin water film will remain on the lens after
the alcohol has evaporated. This water film may attract dust.
4 Do not use compressed air. There is a high risk that blowing gas will condense at the
receiver lens or the fiberstub of the transmitter. This blowing gas may attract dust as
well.
5 Do not use one-click cleaner. Depending on the type it will not reach the lens.
The dry cleaning technique recommended is secribed below:
Step 1 If required, remove the pluggable transceiver from the interface cage of the
module.
Step 2 Place the transceiver on a clean and static-free area, such as an antistatic
mat.
Step 3 If required, remove the dust cap from the optical port of the transceiver and
store it in a small resealable container.
Step 4 Do not use alcohol-based cleaning sticks. Use dry cleaning sticks. Insert a
lint-free cleaning stick of the appropriate size and turn it around with caution.
Do not apply too much force. This can be done at a maximum of three times.
Step 5 Remove the stick and throw away the used stick. Never reuse a stick.
Step 6 If no optical fiber cable is reconnected, cover the transceiver port with the dust
cap to avoid contamination. Always keep the dust cap inserted in the
transceiver port when not in use.
Step 7 Always make sure that the fiber-optic connector that will be plugged into the
transceiver port is also clean — to prevent cross contamination.
Properly dispose of any used cleaning material after use.

Note
Handling Equipment
Handling Equipment
This section gives guidelines for the correct handling of the FSP 3000R7 equipment.
Furthermore, it is described which requirements optical fiber connectors have to be
observed for the use in the optical fiber system.
This section contains the following sub-sections:
“Handling a Shelf” on p. 47
“Handling Modules” on p. 48
“Handling Pluggable Transceivers” on p. 49
“Handling Fiber-Optic Cables” on p. 50
“Optical Fiber Requirements” on p. 51
Handling a Shelf
In the following, the term shelf refers to 9HU Shelf, 7HU Shelf or 1HU Shelf.
When handling a shelf, observe the following guidelines:
The shelf contains electrostatic sensitive devices. They can be

damaged or effectively destroyed by electrostatic discharge (ESD)
during unpacking, installation, removal, storage, or shipment. Please
note that discharge might go unnoticed by a technician. Always follow
the ESD-prevention instructions mentioned below! For more details, see
the European Standards EN 100015-1 to 4.
• Handle a shelf as an electrostatic discharge sensitive device.

• Always wear a properly grounded wrist strap when unpacking and mounting the shelf
or working on the shelf.
• Transport or store a shelf (even temporarily) in its original static-protective package
and shipping container.
• Do not use brushes with synthetic bristles or acid brushes to clean a shelf.
• Do not remove a shelf from its shipping container until you are ready to mount it into a
rack.
• Prevent any unauthorized person from having access to preconfigured shelves
containing encryption modules, either classified or not classified to ensure the
integrity of these modudules.
Lifting hazard: Heavy object!

A fully equipped 9HU Shelf or 7HU Shelf is too heavy to be lifted by one
person.
CAUTION
To avoid personal injury and damage to the equipment two persons are needed to lift fully
equipped 7HU Shelf when removing from the shipping container and mounting into a rack.
Do not install a shelf in dusty environments or near equipment with strong
electromagnetic characteristics. In the latter case external interferences could affect
operation.
Handling Equipment
The equipment has been evaluated for use in a Pollution Degree 2

environment (IP20 according to IEC 60529). For indoor controlled office
environments use only.
Note
• Do not expose the shelf to direct sunlight! Doing so might cause temperatures to
exceed the specified limits and result in incorrect operation or damage to the
equipment.
• Do not operate the shelf with open slots.
Risk of electromagnetic disturbances and insufficient cooling!

To ensure that all components are adequately cooled, and EMC compliance is
achieved, do not operate the shelf without having either modules or the supplied
dummy modules fitted in the slots.
• Use the front cover to protect the fiber-optic cabling on the front of the 7HU Shelf.
Once a necessary work on the shelf has been completed at a later date, mount the
front cover again.
• Make sure that adequate air cooling always is provided.
• Do not dispose of a waste shelf with the normal trash.
The final disposal of any shelf with or without modules should be handled
according to all relevant national laws and regulations of your country.
For more information, refer to the Safety Guide, Section "Equipment
Disposal and Recycling Information".
Handling Modules
In the following, the term module refers to all types of channel modules, passive optical
modules, optical amplifiers as well as management and optical switch modules.
When handling a module, observe the following guidelines:
Modules containing static-sensitive components can be damaged or

effectively destroyed by electrostatic discharge (ESD) during
installation, removal, storage, or shipment. Please note that discharge
might go unnoticed by a technician. Always follow the ESD-prevention
instructions mentioned below! For more details, see the European
Standards EN 100015-1 to 4.
• Handle all modules as electrostatic sensitive devices, unless you are sure the
module concerned does not contain electrostatic discharge sensitive components.
• Always wear a properly grounded wrist strap and use a grounded work surface
whenever handling a module.
• Do not remove a module from its static-protective package until you are ready to
install it.
• Hold a module at its edges or faceplate only. Avoid touching the electronic
components or any exposed printed circuitry.
• When pulling and inserting modules, use the knurled screws on the faceplate.
Handling Equipment
• Do not pass a module to other people.

• Do not handle a module unnecessarily.
• Transport or store a module (even temporarily) in its original static-protective package
and shipping box.
• When unattended, the modules containing sensitive information, e.g. encryption
modules and NCUs, should be stored in a secured and locked location (cabinets,
lock boxes, etc) where access is limited.
• Do not use brushes with synthetic bristles or acid brushes to clean a module.
• Handle a defective module with same care as an intact module.
• When pulling and inserting modules, use the screws on the faceplate.
• Do not touch hot components on the channel module
Hot Surface!
Some channel module components such as heat sinks may attain high
temperatures during operation. Touching very hot components is likely to
CAUTION result in skin burns.
Allow such a module to cool before removing it from the shelf slot. or before placing it
in an static-protective package. Put only cooled modules into the static-protective
package.
• The connector receptacles of the optical ports (integrated inter-faces) are equipped
with protective plugs on delivery to prevent impurities. When storing a module always
keep plugs in the receptacles.
• Keep protective plugs in the receptacles as long as the module is not installed in a
running system or fiber-optic cables are not plugged in.
• The transceiver cages of pluggable-based channel modules are equipped with dust
plugs on delivery to prevent impurities. When storing a pluggable-based channel
module always keep the dust plugs in the cages.
• Keep dust plugs in the transceiver cages as long as the channel module is not
installed in a running system. Make sure to insert a dust plug into the transceiver
cage where no transceiver is present.
• Prevent any unauthorized person from having access to encryption modules, either
classified or not classified to ensure the integrity of these modules.
• Do not dispose of a waste module with the normal trash because of it is an electronic
product.
The final disposal of any module should be handled according to all

relevant national laws and regulations of your country.
For more information, refer to the Safety Guide, Section "Equipment
Disposal and Recycling Information".
Handling Pluggable Transceivers

In the following, the term pluggable transceiver refers to all types of SFP transceivers and
XFP transceivers used.
When handling a transceiver, observe the following guidelines:
Handling Equipment
Pluggable transceivers can be damaged or effectively destroyed by

electrostatic discharge (ESD) during installation, removal, storage, or
shipment. Please note that discharge might go unnoticed by a
technician. Always follow the ESD-prevention instructions mentioned
below! For more details, see the European Standards EN 100015-1 to 4.
• Handle all pluggable transceivers as electrostatic sensitive devices.

• Always wear a properly grounded wrist strap and use a grounded work surface
whenever handling pluggable transceivers.
• Do not remove a pluggable transceiver from its static-protective package until you
are ready to install it.
• Always transport and store a pluggable transceiver (even temporarily) in its original
static-protective package and shipping box.
• Do not touch the host connector of the pluggable transceiver.
• The optical ports of a pluggable transceiver are equipped with a dust cover on
delivery to prevent impurities. Always keep the dust cover in the receptacles as long
as the pluggable transceiver is stored or fiber-optic cables are not plugged in.
• Do not dispose of a waste pluggable transceiver with the normal trash because of it is
an electronic product.
The final disposal of any pluggable transceiver should be handled

according to all relevant national laws and regulations of your country.
Handling Fiber-Optic Cables

In the following, the term fiber-optic cable refers to all types of glass fibers used by the
FSP 3000R7.
Fiber-optic cables require special handling and connecting procedures.

They can be damaged when handled or routed improperly.
Note
To avoid damaging the glass fiber you are strongly advised to observe the following
guidelines:
• Fiber-optic cables should never be bent at sharp angles (less than a 30 mm (1.2 in)
radius. The minimum bend radius of optical fiber cables is about 30 mm – 50 mm (1.2
in – 2.0 in).
• Make sure to only use fiber-optic cables with a flexible bending protection.
• Do not knot or extremely flex fiber-optic cables.
• Without support, fiber-optic cables should only be routed over short distances to
avoid mechanical stress. Frequent over-stressing can cause progressive
degeneration of the cables.
• Avoid tightening or pressuring fiber-optic cables.
• Avoid twisting or crossing one cable over another.
• Avoid excess cable length in breakout area. Use spiral wrap.
• Do not bunch the cables in a tight clump with a cable clamp or tie strap.
Handling Equipment
• Do not stand on fiber-optic cables. Keep the cables off the floor.
• Do not allow a greater static load on any section of the fiber-optic cable.
• Do not pull fiber-optic cables too hard. When pulling at fiber-optic cables, do not pull
directly on the connector or on the cable immediately behind the connector. The cable
should be pulled from a point several centimeters or inches away from the connector.
• The most vulnerable areas of a fiber-optic cable are its connector plugs. Use extreme
care when removing or installing fiber-optic connector plugs to avoid damaging the
connector housing or scratching the end-face surface of the fiber.
• Make sure to put protective caps on fiber-optic connectors when not in use.
• Remove protective caps only immediately before you connect a fiber-optic cable.
• Never use tools when connecting or disconnecting fiber-optic cables because
excessive force can damage or misalign the connection system.
• Store unused fiber-optic cables in a cabinet or on a cable rack.
• Clean fiber-optic equipment as described in “Cleaning and Inspecting Fibers and
Ports” on p. 32.
Optical Fiber Requirements

Fiber-optic connectors differ from electrical or microwave connectors. In a fiber-optic
system, light is transmitted through an extremely small fiber core. Since fiber cores are
often 62.5 microns or less in diameter, and dust particles range from a tenth of a micron to
several microns in diameter, dust and any contamination at the end of the fiber core can
degrade the performance of the connector interface where the two cores meet.
Proper Cleaning and Connection

The connection quality depends on the following two factors: the type of connector and
the proper cleaning and connection techniques. The connectors must be precisely aligned
and the connector interfaces must be absolutely free of trapped foreign material. In a
communication system proper fiber-optic connections become a critical factor.
Fiber-optic cable connectors can be damaged by improper cleaning and connection
procedures. Dirty or damaged fiber-optic connectors can result in not repeatable or
inaccurate communication.
Connector Loss
Connector loss is another critical performance characteristic of a fiber-optic connector.
Typical values are less than 0,3 dB loss, and sometimes as little as 0.1 dB loss when
using high performance connectors.
Return Loss
Return loss specifies the amount of reflected light; the lower the reflection the better the
connection (the smaller the return loss, the smaller the reflection). The best physical
contact connectors have return losses better than -40 dB, although -20 dB to -30 dB is
more common.
Handling Equipment
Periodical Maintenance
Fiber-optic cable connectors need periodical care and maintenance. Unless the
equipment is installed in a hermetic environment, dust particles will eventually collect
within the fiber-optic connections. Over time, this can cause signal degradation. Dirty
fiber-optic connectors are a common source of light loss, especially for 9 µm core single-
mode fibers. As a general rule, whenever there is a significant, unexplained loss of light,
check the connectors.
Chapter 2
Finding Your Problem - Follow the

Light
This chapter describes how to use the measurements taken to determine the most likely
cause of your problem. It involves following the path of the light as it exits the application
and passes through the FSP 3000R7, for an example 64-channel setup.
Execute the following procedure only if all required power measurements were made
AND you have determined that one or more of the measurements are out of specification.
If all of your measurements are within the limits specified by the application and the FSP
3000R7, proceed to the following chapters in this manual.
Always measure optical power directly at the channel module, not at the
patch panel!
Note
Step 1 If the optical power transmitted by the application is within its specification,
proceed to Step 2. Otherwise, correct the application.
Step 2 If the optical power received at the FSP 3000R7 module's C/R is within the
limits indicated in the Module and System Specification, proceed to Step 3.
Please note, however, that you need to take measurements at the FSP
3000R7 module's C/R interface, not at an intermediate patch panel. By not
measuring at the precisely correct point, you risk excluding the cable or
connector that was causing the problem you are now experiencing.
a) If the received optical power is greater than the value allowed for the FSP
3000R7, select an attenuator to reduce the optical power to an acceptable
range.
b) If the received optical power is less than the value allowed for the FSP
3000R7, then you need to determine where the undesired loss is occurring.
If the loss is in the range of 1 dB or 2 dB, it is likely that there is little or
nothing that can be done, as inherent connector loss is difficult to reduce
reliably.
If the loss is greater than 2 dB, there may be a sloppy patch connection, a
bad connector, or a bad cable. Trace the power back from the FSP 3000R7
to the application, taking measurements at each possible point. Eventually
you should find a solution.
Unfortunately, if you are unable to locate the point causing the significant
drop, there is nothing that an ADVA Optical Networking Technical
Services Representative can do to help you. This is strictly an in-house
issue.
Step 3 If the power transmitted by the N/T is within the ADVA Optical Networking
specification, please proceed to Step 4. As with Step 1, you must measure
directly at the N/T connector, to avoid confusing a bad transmitter with a bad
cable.
a) If the optical power transmitted by the N/T is below specification, there is
very little that can be done. Either the network transmitter is defective or
the connector is dirty. Try cleaning the interface using a can of
compressed air, as the problem may simply be dirt. However, be advised
that this may lodge the dirt even more firmly into the connector.
b) If cleaning the interface with canned air does not clear the reading, use a
fiber scope/camera kit to inspect the female connector of the module. If
the connector surface still appears dirty, clean the connector again.
c) Inspect the connectors with a fiber scope. If the connectors still appear
dirty, return the unit to ADVA Optical Networking for repair. Please be
advised, however, that cleaning dirty connectors is not covered under the
product's warranty.
Step 4 If the channel module is not connected to an OPPM (Optical Path Protection
switch Module), proceed to Step 5.
If the channel module is connected to an OPPM, use the measurements you
have already taken to check the loss over the OPPM. In this case, we need to
determine how much light is lost over both line NW and line NE paths.
If the loss from going into the network link is within the limits specified in the
Module and System Specification, proceed to the next step.
If the loss exceeds the limits, clean the OPPM connectors. If this does not
resolve the issue, return the OPPM to ADVA Optical Networking for repair.
Step 5 We need to determine how much loss is induced as the signal passes into and
out of the CSM (Channel Splitter Module). If the power difference between the
channel module's N/T (or OPPM NE/NW) and the CSM N/M interface is within
the limits indicated in the Module and System Specification, proceed to Step 6.
However, if the loss exceeds the limit, the problem may be either at the cable
that connects the channel module/OPPM to the CSM, or with the CSM M
interface.
a) To check whether the cable is faulty, measure the loss over the cable. If
you lack the appropriate adaptors to connect the cable to a power meter,
try connecting a working cable instead of the suspected cable. If the loss
is still significant with the working cable, there is a problem with the
passive module.
b) Clean the N/M interface, as well as the interface connecting the C/M
interface to the channel module/OPPM. If this does not resolve the issue,
return the MDXM to ADVA Optical Networking for repair.
If there is a power gain through the CSM instead of a loss, there may be
multiple channel modules/OPPMs connected to the CSM with their
network transmitters turned ON. When measuring the loss through the
CSM N/M interface, ensure that only one channel module is transmitting a
signal.
Step 6 If the CSM is not connected to an OPPM (Optical Path Protection switch
Module), proceed to Step 7.
If the CSM is connected to an OPPM, use the measurements you have
already taken to check the loss over the OPPM.
In this case, we need to determine how much light is lost over both line NW
and line NE paths. If the loss from going into the network link is within the
limits specified in the Module and System Specification, proceed to the next
step.
If the loss exceeds the limits, clean the OPPM connectors. If this does not
Step 7 Use the measurements you have already taken to check the loss over the
GSM (Group Splitter Module). If no GSM is installed, please proceed to Step 8.
If this group contains multiple channels and only one channel exhibits power
levels which are not in specification, please proceed to Step 8, since the GSM
is probably not the root cause.
a) If the loss from the CSM N/M interface (or OPPM) to the GSM N/M
interface is within the limits indicated in the Module and System
Specification, then this GSM group is functioning correctly. Note,
however, that you need to measure the loss across the same group which
is experiencing poor power measurements.
b) If the loss across the GSM is too high, despite all attempts to clean its
interfaces, return it to ADVA Optical Networking for repair.
If there is a power gain over the GSM, channels in another group may be
transmitting optical power through the system. Ensure only one channel is
present when measuring loss over the GSM.
2BSM (Band Splitter Module). If no 2BSM is installed, please proceed to Step
9.
If this group contains multiple channels and only one channel exhibits power
levels which are not in specification, please proceed to Step 9, since the
2BSM is probably not the root cause.
a) If the loss from the GSM N/M interface to the 2BSM N/M interface is
within the limits indicated in the Module and System Specification, then
this 2BSM is functioning correctly. Note, however, that you need to
measure the loss across the same group which is experiencing poor power
measurements.
b) If the loss across the 2BSM is too high, despite all attempts to clean its
If there is a power gain over the 2BSM, channels in another group/band
may be transmitting optical power through the system. Ensure only one
channel is present when measuring loss over the 2BSM.
CLSM (C-band/L-band Splitter Module). If no CLSM is installed, please
proceed to Step 10.
If multiple channels are running over the C band and/or the L band, and only
one channel exhibits power levels which are not in specification, please
proceed to Step 10, since the CLSM is probably not the root cause,
a) If the loss from the 2BSM N/M interface to the CLSM N/M interface is
this CLSM is functioning properly. Note, however, that you need to
measure the loss across the same band which is experiencing poor power
measurements.
b) If the loss across the CLSM is too high, despite all attempts to clean its
If there is a power gain over the CLSM, channels in another group/band
may be transmitting optical power through the system. Ensure only one
channel is present when measuring loss over the CLSM.
OSFM (Optical Supervisory Channel Filter Module). If no OSFM is installed,
please proceed to Step 11.
If multiple channels are running over the system, and only one channel exhibits
power levels which are not in specification, please proceed to Step 11, since
the OSFM is probably not the root cause,
a) If the loss from the CLSM N/M interface to the OSFM N/M interface is
this OSFM is functioning properly.
b) If the loss across the OSFM is too high, despite all attempts to clean its
If there is a power gain over the OSFM, channels in another group/band or
the 1630nm Optical Supervisory Channel coming from the OSCM may be
transmitting optical power through the system. Ensure only one channel is
present when measuring loss over the OSFM. Disconnect the OSCM from
the OSFM.
RSM (Remote Switch Module) or VSM (Versatile Switch Module). If an RSM
or VSM is not present, proceed to Step 12.
In this case, we need to determine how much light is lost over both line NW
and line NE paths. If the loss from going into the network link is within the
limits indicated in the Module and System Specification, proceed to the next
step. If the loss exceeds the limits, the RSM or VSM may be defective.
Step 12 Network Link. If the loss on the network link is within the limits specified in the
Module and System Specification for the given configuration, proceed to Step
13. Please note that you need to check each fiber used on the network link.
If the loss on the network link is too high, clean the interfaces into the network
link. If the loss still exceeds the allowed range, contact the service provider
who supplied the link.
Step 13 Network side of the network link. If an RSM or VSM is not present, please
proceed to Step 14.
a) If you have not already done so, measure the optical power coming into the
RSM or VSM on both NW and NE links, and the loss through the RSM or
VSM when on a selected link.
b) If the loss through the incoming side of the RSM or VSM exceeds the
limits specified in the Module and System Specification, even after all
attempts to clean its interfaces, return it to ADVA Optical Networking for
repair.
The lack of direct synchronization of VSM switch positions may, in rare

cases, lead to transversed switch positions. This is rectified by
performing a manual switch on one of the VSMs to re-align the switch
Note positions.
Step 14 If an OSFM is not present, proceed to Step 15.

a) If you have not already done so, measure the loss through the OSFM on
the incoming patch which is experiencing problems.
b) If the loss through the OSFM exceeds the limits specified in the Module
and System Specification, even after all attempts to clean its interfaces,
return it to ADVA Optical Networking for repair.
Step 15 If a CLSM is not present, proceed to Step 16.
a) If you have not already done so, measure the loss through the CLSM on
the incoming patch which is experiencing problems.
b) If the loss through the CLSM exceeds the limits specified in the Module
and System Specification, even after all attempts to clean its interfaces,
return it to ADVA Optical Networking for repair.
Step 16 If a GSM is not present, proceed to Step 17.
a) If you have not already done so, measure the loss through the GSM on the
incoming patch which is experiencing problems.
b) If the loss through the GSM exceeds the limits specified in the Module and
System Specification, even after all attempts to clean its interfaces, return
it to ADVA Optical Networking for repair.
Step 17 If an OPPM is not present, please proceed to Step 18.
OPPM on both NW and NE links, and the loss through the OPPM when on
a selected link.
b) If the loss through the incoming side of the OPPM is within the limit
specified in the Module and System Specification, proceed to the next
step.
If the loss exceeds the limit, clean the OPPM connectors. If this does not
Step 18 If you have not already done so, measure the loss through the CSM (CxD) for
the channel(s) experiencing problems. Then execute the following steps:
a) Combine the loss from the CxM with the loss through the CxD for each
channel measured. That is, add the loss of the CxM for channel 1 to the
loss on the CxD for channel 1.
b) If the loss through either the CxM or CxD exceeds the limits specified in
the Module and System Specification, even after all attempts to clean its
Step 19 If an OPPM is not present, please proceed to Step 20.
OPPM on both NW and NE links, and the loss through the OPPM when on
a selected link.
b) If the loss through the incoming side of the OPPM is within the limit
specified in the Module and System Specification, proceed to the next
step.
If the loss exceeds the limit, clean the OPPM connectors. If this does not
Step 20 Network receiver for the module. If you have not already done so, measure
the power received by the channel module's network receiver. Please
remember to include the patch cable from the CSM (CxD) or OPPM to the
channel module, as this cable can be faulty. Excluding it may be mean ignoring
the root cause of the issue you are experiencing.
a) If the received optical power is within the channel module's specification,
proceed to Step 21.
b) If the received optical power is not within specification, measure the
optical power coming from the CSM (CxD) or OPPM.
The difference between the power reading from the CSM (CxD) or OPPM
and the power reading from the end of the cable which plugs into the
module's network receiver is the loss induced by the cable.
c) If the loss induced by this cable is significantly greater than 1 dB, repeat
step (b) with another cable of the same or longer length. If both cables
exhibit losses significantly greater than 1 dB, the mechanism you are
using for measurement may be inducing loss. Verify your measurement
tools and search for a cable that has the desired loss of 1 dB or less.
d) If the cable does not induce significant loss and the power coming into the
network receiver is still not within specification, please contact your ADVA
Optical Networking Technical Services Representative for assistance.
Step 21 The only remaining aspect of the light path is the client transmitter back to the
application. If the optical power emitted by the module's client transmitter is
within the channel module's specification, proceed to Step 22.
If the optical power is significantly below the channel module's specification,
clean the interface. If the optical power remains significantly below
specification, return the module to ADVA Optical Networking for repair.
Step 22 If the power received by the application exceeds the application's
specification, follow these steps:
a) Calculate the difference between the optical power transmitted by the FSP
3000R7 channel module and the power level received by the application.
Usually, there is plenty of margin in the ADVA Optical Networking
specification for patch field loss, with the possible exception of the TDM
module, which only allows for a few dB of loss.
b) If only a few dB of loss is induced by the cable and connections between
the FSP 3000R7 channel module and the application, and this causes the
application to exceed specification, clean the connections between the
application and the FSP 3000R7. If the application continues to exceed
specfication, contact your ADVA Optical Networking Technical Services
Representative for assistance.
c) If the loss induced by the patch field between the FSP 3000R7 channel
module and the application is significantly greater than 2 dB, follow the
light either from the application back to the FSP 3000R7, or from the FSP
3000R7 to the application. In either case, take power measurements at
each patch field until you locate the connection or cable which induces the
undesired loss.
If you cannot locate the faulty connection or cable, contact your ADVA Optical
Networking Technical Services Representative.
Chapter 3
Shelves and Power Supply Units

This chapter addresses the various shelves and power supplies available at the
publication date of this manual.
This chapter consists of these sections:
“Troubleshooting Shelves” on p. 60, which addresses LED indicators and troubleshooting
guidelines for shelves.
“Troubleshooting Power Supply Units” on p. 88, which addresses LED indicators and
troubleshooting guidelines for PSUs.
Troubleshooting Shelves
This section addresses LED indicators and troubleshooting guidelines for all available
shelves. Refer to these subsections for appropriate information of each shelf:
“SH1HU-F/2DC, SH1HU-HP/2DC and SH1HU-HP/E-TEMP/2DC Shelf LEDs” on p. 60
“SH1HU-R(/PF) Shelf LEDs” on p. 68
“SH7HU(-R) Shelf LEDs” on p. 75
“SH9HU and SHX9HU Shelf LEDs” on p. 81
“OTDR Shelf LEDs” on p. 87
SH1HU-F/2DC, SH1HU-HP/2DC and SH1HU-HP/E-

TEMP/2DC Shelf LEDs
The SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-TEMP/2DC shelf LEDs are
located on their front panels as illustrated in Figure 8 and Figure 9 on p. 61. These shelves
have the same LED indicators.
Figure 8: SH1HU-F/2DC Front Panel LED Indicators
Figure 9: SH1HU-HP/2DC and SH1HU-HP/E-TEMP/2DC Front Panel LED

Indicators
These subsections address LED indicators and troubleshooting guidelines for the
SH1HU-F/2DC, SH1HU-HP/2DC and SH1HU-HP/E-TEMP/2DC shelves.
“SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-TEMP/2DC Fan Status LED” on
p. 62
“SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-TEMP/2DC Slot Status LEDs”
on p. 63
“SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-TEMP/2DC Power Status LEDs”
on p. 65
“SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-TEMP/2DC Network Element
Status LEDs” on p. 66
SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-

TEMP/2DC Fan Status LED
There is one LED named “fan”, which indicates the operating status of the six cooling fans. This LED always
shows the failure with the highest severity. If the LED is lit green, the fans are working properly. If the LED is lit
yellow, red, or is off, one or more fans are faulty.
It is recommended to have a replacement shelf available at all times.
If multiple fans malfunction or fail, Service Personnel must replace the shelf within 48 hours after failure.
To restore system cooling, ensure that the replacement procedure does not exceed 3 minutes! To replace a
shelf, refer to “Replacing an SH1HU Shelf” on p. 752.
Table 1: SH1HU-F/2DC, SH1HU-HP/2DC and SH1HU-HP/E-TEMP/2DC Fan Status LED
LED LED Colors Potential Cause Solution for Troubleshooting

Names
Fan Red Firmware Mismatch 1 Check if a firmware mismatch is displayed in

or the management and update the firmware if
More than one fan has available. If no firmware mismatch is
failed. Fan speed has displayed in the management, a hardware
deviated by 30% from the mismatch has occurred.
target speed or has failed.
2 Have Service Personnel replace the shelf
within 48 hours after failure and return it to
ADVA Optical Networking.
Yellow Firmware / Hardware 1 Check if a firmware mismatch is displayed in

blinking to off Mismatch the management and update the firmware if
or available. If no firmware mismatch is
Communication is broken displayed in the management, a hardware
between FCU and mismatch of the SCU/SCU-S has occurred.
SCU/SCU-S.
2 First remove and reinsert the SCU/SCU-S.
• If the LED is still blinking yellow to off,
replace the SCU/SCU-S.
• If the LED is still blinking yellow to off, either
have Service Personnel replace the shelf or
contact your ADVA Optical Networking
Technical Services Representative.
Yellow One fan has failed. The No action is required..

fan speed has deviated
from the target speed by
over 15%, or the voltage
applied to the fan is out of
specification.
Green All fans are operating No action is required.

properly.

TEMP/2DC Slot Status LEDs
These shelves have four slot LEDs each, one LED per slot. The slot LEDs indicate the operating status of the
inserted modules and the communication status to the management.
Each slot has its corresponding LED as follows:
• “A” and “B” indicate the operating status of the half-sized modules SCU or SCU-S and NCU.
• “1” and “2” indicate the communication status of the respective module to the SCU or SCU-S and NCU.
If the LED of the operating module is lit green, the module is working properly and there is no failure. If the LED is
lit yellow, red, or off, the module has a failure or does not work.
Table 2 on p. 64 describes the cause of the status that each color of the LED indicator represents and if it
indicates a failure. This table also lists troubleshooting guidelines.
Before you start with troubleshooting, ensure that the NE is operating with the required NCU
software and module firmware. For details on updating NCU software and module firmware,
refer to “Updating the NE Software Release” on p. 617 and “Performing Other Software Update
Note Actions” on p. 628.
Before you start with troubleshooting be sure that the admin status on the affected module is set
to “Maintenance”.
Note
If your module has an LED status that is not represented in Table 2 on p. 64, please contact your
ADVA Optical Networking Technical Services Representative.
Note
Table 2: SH1HU-F/2DC and SH1HU-HP/2DC Slot Status LEDs

Names
A, B; Yellow blinking Firmware / Hardware 1 Check if a firmware mismatch is displayed

1, 2 to off Mismatch in the management and update the firmware
or if available. If the facility admin state
Connection to the NCU or settings are not configured to
SCU is disrupted “Maintenance”, the connection to the
or NCU or SCU is disrupted, or a hardware
Module admin state is in mismatch of the SCU or SCU-S has
“Maintenance” to force on occurred.
the laser or to configure a
2 Remove and reinsert the SCU or SCU-S.
loop.
replace the SCU or SCU-S.
Red Database Mismatch Check if the module power LED (P) lights up
or green.
Module major and critical
• If the module power LED lights up red, a
alarms
hardware error has occurred and the module
has to be replaced.
• If the module power LED lights up green,
but the slot status LED lights up red, check
the fault management table.
Off flashing to The installed module does 1 Compare the provided module in the
red not match the provisioned management with the installed module in
module in the database. the slot.
2 Delete the incorrect module from the
management and provision the installed
module.
Off Module admin state is • If the management displays “unassigned”,

“unassigned” (the module is check if the correct module is provided to
not provided in the the management. If the wrong module is
management), provided, delete the module and create the
"management", or correct one.
"disabled". • If the management displays “management”
or "disabled", change the admin state to “In
Service”.
Yellow Module minor alarms Check the fault management table.
Green Module operates properly No action is required.

or
Module admin state is
"automatic in service".

TEMP/2DC Power Status LEDs
Power redundancy is achieved by two separate power inputs labeled “pwr 1” and “pwr 2” left to the shelf display
on the front panel. In this case, power should be received from two independent power sources. If one of the two
power feeds fails, the power supply will continue to provide the required power to the shelf until the fault is
cleared.
Please follow the troubleshooting steps in Table 3 based upon the states of the LEDs.
If your module has a power LED status that is not represented in Table 3, please contact your
Note
Table 3: SH1HU-F/2DC, SH1HU-HP/2DC and SH1HU-HP/E-TEMP/2DC Power Status LEDs
LED LED Potential Cause Solution for Troubleshooting

Name Colors
pwr1 Red An overload of circa 110% is A hardware error has occurred. Return the
reached. SH1HU shelf to ADVA Optical Networking.
This unit is not receiving DC power,

but the redundant power feed
provides power to the shelf.
Yellow The maximum output power is Check the power connection according to the
reached or exceeded. SH1HU power supply specification.
Off DC power source connected to 1 Check the power connection. If power

power feed 1 has failed. connection is OK, a hardware error has
occurred.
2 Return the shelf to ADVA Optical
Networking.
If the polarity for connecting the power cord
has not been considered, connect the power
supply to a system safety ground lead.
Green The unit is receiving DC power No action is required.

through power feed 1.
The input voltage is in the admissible

range.
pwr2 Red An overload of circa 110% is A hardware error has occurred. Return the
reached. SH1HU shelf to ADVA Optical Networking.
This unit is not receiving DC power,

but the redundant power feed
provides power to the shelf.
Table 3: SH1HU-F/2DC, SH1HU-HP/2DC and SH1HU-HP/E-TEMP/2DC Power Status LEDs

Name Colors
pwr2 Yellow The maximum output power is Check the power connection according to the
reached or exceeded. SH1HU power supply specification.
Off DC power source connected to 1 Check the power connection. If power

power feed 2 has failed. connection is OK, a hardware error has
occurred.
Networking.
Green The unit is receiving DC power No action is required.

through power feed 2.

range.

TEMP/2DC Network Element Status LEDs
There are three NE LEDs on the shelf front panel:
• Critical
• Major
• Minor
The NE Status LEDs (critical, major, minor) are active only on the master shelf, i.e. only once for
a network element. The NE status LEDs of the remaining shelves within the network element
will be off.
Note
The three LEDs indicate a failure of the network element. Only the highest failure level within the NE will be
indicated. Therefore, only one of the three LEDs is lit at a given time.
Table 4 on p. 67 describes the cause of the status that each color of the NE status LED indicators represents and
the recommended troubleshooting steps. If there is no failure of the network element, the three LEDs are lit
green.
If your module has an LED status that is not represented in Table 4 on p. 67, please contact your
Note
Table 4: SH1HU-F/2DC, SH1HU-HP/2DC and SH1HU-HP/E-TEMP/2DC Network Element Status LEDs

Names Colors
Critical Off Communication is broken Check if a firmware mismatch is displayed in the

(FCU—SCU/SCU-S or management and update the firmware if available.
SCU/SCU-S—NCU) • If no firmware mismatch is displayed in the
or management, a hardware mismatch of the
Shelf is not the master/main
SCU/SCU-S has occurred. Replace the
shelf.
SCU/SCU-S.
• If the LED is still off, verify that the shelf is a
master or main shelf.
Red A critical error detected as Check the status of the modules in the fault
highest severity in the NE. management table.
At least one of the modules
has a critical error.
Major Off Communication is broken Check if a firmware mismatch is displayed in the

shelf.
SCU/SCU-S.
Red A major error detected as Check the status of the modules in the fault
has a major error.
Minor Off Communication is broken Check if a firmware mismatch is displayed in the

or management, a hardware mismatchof the
shelf.
SCU/SCU-S.
Yellow A minor error detected as Check the status of the modules in the fault
has a minor error.
SH1HU-R(/PF) Shelf LEDs

The LED indicators of the SH1HU-R shelf and SH1HU-R/PF shelf are located on their
front panels as illustrated in Figure 10 and Figure 11. Both shelves have the same LED
indicators.
Figure 10: SH1HU-R Front Panel LED Indicators
Figure 11: SH1HU-R/PF Front Panel LED Indicators
Refer to these subsections describing the different LEDs and their behavior of the
SH1HU-R(/PF) shelves.
“SH1HU-R(/PF) Fan Status LED” on p. 69
“SH1HU-R(/PF) Slot Status LEDs” on p. 70
“SH1HU-R(/PF) Power Status LEDs” on p. 72
“SH1HU-R(/PF) Network Element Status LEDs” on p. 73
SH1HU-R(/PF) Fan Status LED

There is one LED named “fan”, which indicates the operating status of the six cooling fans. This LED always
shows the failure with the highest severity. If the LED lights up green, the fans are working properly and there is
no failure. If the LED lights up yellow, red, or is off, one or more fans are faulty or do not work.
It is recommended to have a replacement shelf available at all times.
If a fan in an SH1HU-R malfunctions or fails, Service Personnel must replace the shelf within 48 hours
after failure. To restore system cooling, ensure that the replacement procedure does not exceed 3 minutes!
To replace a shelf, refer to “Replacing an SH1HU Shelf” on p. 752.
If a fan in an SH1HU-R/PF malfunctions or fails, Service Personnel must replace the fan unit within 48
hours after failure. To maintain system cooling, ensure the corresponding fan module slot does not remain
empty for longer than 1 minute during the replacement process! To replace a fan unit, refer to “Replacing a
FAN/1HU” on p. 742.
Table 5: SH1HU-R(/PF) Fan Status LED

Names Colors
Fan Red Firmware Mismatch 1 Check if a firmware mismatch is displayed

or in the management and update the firmware
One or more fans have failed. if available. If no firmware mismatch is
Fan speed has deviated by displayed in the management, a hardware
30% from the target speed or mismatch has occurred.
has failed.
2 Have Service Personnel replace the shelf
within 48 hours after failure and return it to
Yellow Firmware / Hardware 1 Check if a firmware mismatch is displayed

blinking to Mismatch in the management and update the firmware
off or if available. If no firmware mismatch is
Communication is broken displayed in the management, a hardware
between FCU and mismatch of the SCU/SCU-S has
SCU/SCU-S. occurred.
2 First remove and reinsert the SCU/SCU-S.
replace the SCU/SCU-S.
either have Service Personnel replace the
shelf or contact your ADVA Optical
Networking Technical Services
Representative.
Table 5: SH1HU-R(/PF) Fan Status LED

Names Colors
Fan Yellow SH1HU-R: One fan has No action is required.

failed. The fan speed has
deviated
from the target speed by over
15%, or the voltage applied to
the fan is out of specification.

properly.
SH1HU-R(/PF) Slot Status LEDs

This shelf has four slot LEDs, one LED per slot. The slot LEDs indicate the operating status of the inserted
modules and the communication status to the management.
• “A” and “B” indicate the operating status of the half-sized modules SCU or SCU-S and NCU.
• “1” and “2” indicate the communication status from the respective module to the SCU or SCU-S and NCU.
If the LED of the operating module lights up green, the module is working properly and there is no failure. If the
LED lights up yellow, red, or off, the module has a failure or does not work.
Table 6 describes the cause of the status that each color of the LED indicator represents and if it indicates a
failure. This table also lists troubleshooting guidelines.
Note
If your module has an LED status that is not represented in Table 6, please contact your ADVA
Optical Networking Technical Services Representative.
Note
Table 6: SH1HU-R(/PF) Slot Status LEDs

Names
A, B; Yellow Firmware / Hardware 1 Check if a firmware mismatch is displayed

1, 2 blinking to off Mismatch in the management and update the
or firmware if available. If the facility admin
Connection to the NCU or state settings are not configured to
Module admin state is in mismatch of the SCU or SCU-S has
“Maintenance” to force on the occurred.
laser or to configure a loop.
2 Remove and reinsert the SCU or SCU-S.
replace the SCU or SCU-S.
Red Database Mismatch Check if the module power LED (P) lights up
or green.
• If the module power LED lights up red, a
alarms
hardware error has occurred and the
module has to be replaced.
• If the module power LED lights up green,
but the slot status LED lights up red,
check the fault management table.
Off flashing to The installed module does not 1 Compare the provided module in the
red match the provisioned module management with the installed module in
in the database. the slot.
module.

“unassigned” (the module is check if the correct module is provided to
not provided in the the management. If the wrong module is
management), provided, delete the module and create the
"management", or "disabled". correct one.
• If the management displays
“management” or "disabled", change the
admin state to “In Service”.

or
SH1HU-R(/PF) Power Status LEDs

Power redundancy is achieved by two separate power inputs labeled “PSU1“ and “PSU2” left to the shelf display
on the front panel. In this case, power should be received from two independent power sources. If one of the two
power feeds fails, the power supply will continue to provide the required power to the shelf until the fault is
cleared.
This shelf uses the PSU/1HU-R-AC(-200) as power source. This PSU has a single tri-color LED indicator
marked “P” on its faceplate providing more detailed information on the operational status of the unit. Refer to
“PSU/1HU-R-AC and PSU/1HU-R-DC-200” on p. 89 for more information.
Please follow the troubleshooting steps in Table 7 on p. 72 based upon the states of the LEDs.
If your module has a power LED status that is not represented in Table 7 on p. 72, please contact
your ADVA Optical Networking Technical Services Representative.
Note
Table 7: SH1HU-R(/PF) Power Status LEDs

Name Colors
PSU1 Red An overload of circa 110% is reached. A hardware error has occurred. Return the
SH1HU shelf to ADVA Optical
This unit is not receiving DC power, Networking.
but the redundant power feed provides
power to the shelf.
Yellow The maximum output power is reached Check the power connection according to
or exceeded. the SH1HU power supply specification.
Off DC power source connected to power 1 Check the power connection. If power
feed 1 has failed. connection is OK, a hardware error
has occurred.
Networking.
If the polarity for connecting the power
cord has not been considered, connect the
power supply to a system safety ground
lead.
Green The unit is receiving DC power through No action is required.

power feed 1.

range.
Table 7: SH1HU-R(/PF) Power Status LEDs

Name Colors
PSU2 Red An overload of circa 110% is reached. A hardware error has occurred. Return the
SH1HU shelf to ADVA Optical
This unit is not receiving DC power, Networking.
but the redundant power feed provides
power to the shelf.
Yellow The maximum output power is reached Check the power connection according to
or exceeded. the SH1HU power supply specification.
Off DC power source connected to power 1 Check the power connection. If power
feed 2 has failed. connection is OK, a hardware error
has occurred.
Networking.
lead.
Green The unit is receiving DC power through No action is required.

power feed 2.

range.
SH1HU-R(/PF) Network Element Status LEDs

There are three NE LEDs on the shelf front panel:
• Critical
• Major
• Minor
will be off.
Note
indicated. Therefore, only one of the three LEDs lights up at the same time.
Table 8 describes the cause of the status that each color of the NE status LED indicators represents and the
solution for troubleshooting. If there is no failure of the network element, the three LEDs light up green.
Note
Table 8: SH1HU-R(/PF) Network Element Status LEDs

Names Colors

shelf.
SCU/SCU-S.
Red A critical error detected as Check the status of the modules in the fault

shelf.
SCU/SCU-S.
Red A major error detected as Check the status of the modules in the fault

or management, a hardware mismatchof the
shelf.
SCU/SCU-S.
Yellow A minor error detected as Check the status of the modules in the fault
SH7HU(-R) Shelf LEDs

This section describes the LEDs of the SH7HU and SH7HU-R shelves. Both shelf types
feature the same LED behavior. Their LED indicators are located on the fan unit
(FAN/Plug-In) front panel.
SH7HU Versus SH7HU-R

Figure 12 shows the SH7HU shelf supporting the PSU/7HU-AC(-HP) or PSU/7HU-DC(-
HP). A mix of both PSU types in one shelf is also possible.
The SH7HU-R shelf as rear-access shelf is identical to the SH7HU shelf. The SH7HU-R
shelf only differs in the power supply unit as it supports the PSU/7HU-R-DC(-HP).
For more information about PSUs and a figure of the SH7HU-R shelf, refer to “Shelves
and Components” in the Hardware Description.
Figure 12: SH7HU Fan Unit LED Indicators
Refer to these subsections describing the different LEDs and their behavior of the
SH7HU shelf and SH7HU-R shelf.
“SH7HU(-R) Fan Status LEDs” on p. 76
“SH7HU(-R) Slot Status LEDs” on p. 77
“SH7HU(-R) Network Element Status LEDs” on p. 79
For information about the shelf power status, refer to “Troubleshooting Power Supply
Units” on p. 88.
SH7HU(-R) Fan Status LEDs

There is one LED named “fan”, which indicates the operating status of the fan unit. This LED always shows the
failure with the highest severity. If the LED is lit green, the fans are working properly. If the LED is lit yellow, red,
or is off, one or more fans are faulty.
It is recommended to have a replacement fan unit available at all times.
If a fan malfunctions or fails, Service Personnel must replace the fan unit within 48 hours after failure. To
restore system cooling, ensure that the replacement procedure does not exceed 3 minutes! To replace a fan
unit, refer to “Replacing a FAN/Plug-In” on p. 737.
Table 9: SH7HU(-R) Fan Unit LED Status

Names
Fan Red Firmware Mismatch Check if a firmware mismatch is displayed in

or the management and update the firmware if
More than one fan has failed. available.
Fan speed has deviated by
• If no firmware mismatch is displayed in
30% from the target speed or
the management, a hardware mismatch
has failed.
has occurred. Remove the fan unit and
reinsert it again.
• If the LED of the fan unit still lights up
red, have Service Personnel replace the
fan unit and return it to ADVA Optical
Networking.
Yellow One fan has failed. Fan speed No action is required.

has deviated by 30% from the
target speed or has failed.
Yellow Firmware / Hardware Mismatch 1 Check if a firmware mismatch is

blinking to off or displayed in the management and update
Communication is broken the firmware if available. If no firmware
between FCU and SCU. mismatch is displayed in the
management, a hardware mismatch of
the fan unit or SCU has occurred.
2 First remove and reinsert the fan unit. If
the LED is blinking yellow to off, remove
and reinsert the SCU.
have Service Personnel replace the fan
unit and SCU.
Green All fans are operating properly. No action is required.
SH7HU(-R) Slot Status LEDs

This fan unit has one status LED indicator per slot. The slot LEDs indicate the operating status of the inserted
modules and the communication status to the management. An SH7HU shelf has 22 slots.
• “A” and “B” indicate the operating status of the half-sized modules SCU and NCU.
• “1” ... “20” indicate the communication status from the respective module to the SCU and NCU.
If the LED of the operating module lights up green, the module is working properly and there is no failure. If the
LED lights up yellow, red, or off, the module is faulty or does not work.
Table 10 on p. 78 describes the cause of the status that each LED color represents and if it indicates a failure.
This table also lists troubleshooting guidelines.
Note
If your module has an LED status that is not represented in Table 10 on p. 78, please contact
Note
Table 10: SH7HU(-R) Slot Status LEDs

Names
A, B; Yellow blinking Firmware / Hardware 1 Check if a firmware mismatch is

1 - 20 to off Mismatch displayed in the management and update
or the firmware if available. If the facility
Connection to the NCU or admin state settings are not configured to
Module admin state is in mismatch of the SCU has occurred.
“Maintenance” to force on the
2 Remove and reinsert the SCU.
laser or to configure a loop.
replace the SCU.
Red Database Mismatch Check if the PSU Power LED (P) lights up
or green.
• If the PSU Power LED lights up red, a
alarms
module has to be replaced.
• If the PSU Power LED lights up green,
but the slot status LED lights up red,
check the fault management table.
Off flashing to The installed module does not 1 Compare the provided module in the
red match the provisioned module management with the installed module in
in the database. the slot.
module.
Off Module admin state is • If the management displays

“unassigned” (the module is “unassigned”, check if the correct module
not provided in the is provided to the management. If the
management), "management", wrong module is provided, delete the
or "disabled". module and create the correct one.
“management” or "disabled", change the

or
SH7HU(-R) Network Element Status LEDs

There are three NE LEDs on the fan unit front panel of the shelf:
• Critical
• Major
• Minor
will be off.
Note
indicated. Therefore, only one of the three LEDs lights up at the same time.
Table 11 describes the cause of the status that each color of the NE status LED represents and the solution for
troubleshooting. If there is no NE fail, the three LEDs are lit green.
Note
Table 11: SH7HU(-R) Network Element Status LEDs

Names Colors

(FCU—SCU or SCU—NCU) management and update the firmware if available.
or • If no firmware mismatch is displayed in the
management, a hardware mismatch of the fan
shelf.
unit or SCU has occurred. First have Service
Personnel replace the fan unit and if the LED is
off, replace the SCU.
• If the LED is still off, verify that the shelf is the
• If the LED is still off, have Service Personnel
replace the fan unit and SCU.
Red A critical error is detected as Check the status of the modules in the fault
Table 11: SH7HU(-R) Network Element Status LEDs

Names Colors

shelf.
off, replace the SCU.
Red A major error is detected as Check the status of the modules in the fault

shelf.
off replace the SCU.
Yellow A minor error is detected as Check the status of the modules in the fault
SH9HU and SHX9HU Shelf LEDs

SH9HU and SHX9HU shelf LEDs are located on the front panel of the Common
Equipment Module (CEM/9HU) plug-in module. The CEM/9HU is designed specifically
for SH9HU and SHX9HU shelves.
Figure 13 illustrates the shelf LEDs of a SH9HU shelf, a similar setup exists for the
SHX9HU.
Figure 13: SH9HU Shelf LED Indicators
Refer to these subsections for SH9HU and SHX9HU shelf LED troubleshooting
guidelines:
“SH9HU and SHX9HU Fan Status LEDs” on p. 82
“SH9HU and SHX9HU Slot Status LEDs” on p. 83
“SH9HU and SHX9HU Network Element Status LEDs” on p. 85
For more information about CEM/9HU LED troubleshooting, refer to “CEM/9HU” on
p. 411.
For details about the shelf power status, refer to “Troubleshooting Power Supply Units” on
p. 88. The Module and System Specification identifies the power supply units supported
by each shelf.
SH9HU and SHX9HU Fan Status LEDs

The SH9HU contains three independent plug-in fan modules (FAN/9HU), as shown in Figure 14. They are
located on top of the SH9HU shelf above the CEM/9HU as illustrated in Figure 13 on p. 81.
Similarly, the SHX9HU contains three independent plug-in fan modules (FAN/X9HU). They are located on top of
the SHX9HU shelf above the CEM/9HU.
Each FAN/9HU and FAN/X9HU module has one “Status” LED to indicate the operating status. The LED always
shows the failure with the highest severity. If the LED is lit green, the module is operating properly. If the LED is
lit yellow, red, or is off, the fan has a failure.
It is recommended to have replacement fans available at all times.
Table 12 on p. 83 addresses LED troubleshooting guidelines for the SH9HU and SHX9HU fan status LEDs.
If a fan malfunctions or fails, Service Personnel must replace this faulty fan module within 48 hours after
failure. To maintain system cooling, ensure the corresponding fan tray slot does not remain empty for longer
than 1 minute during the replacement process. To replace a fan module, refer to “Replacing a FAN/9HU or
FAN/X9HU” on p. 739.
Figure 14: SH9HU Fans (FAN/9HU)
Table 12: LED Status of the FAN/9HU and FAN/X9HU

Names Colors
Status Red Fan speed has Check the fault being reported by the faulty fan, by selecting
deviated by 30% FAN-x-y FAN9HU (SH9HU shelf) or FAN-x-y FANXHU
from the target (SHX9HU shelf), where x is the shelf number and y is the
speed or has failed. fan number.
If the fault is VOLTANR:
Yellow The fan speed has
1 Verify that the main supply feeding the associated
deviated from the
power supply units is operating within specifications.
target speed by over
15%, or the voltage 2 Verify that the power supply modules have not failed,
applied to the fan and that the shelf is equipped according to engineering
exceeds guidelines for power consumption with respect to the
specifications. power supply modules used within the shelf.
3 If there are multiple modules within the same shelf
reporting this condition, replace the associated power
supply units.
4 If there are multiple fan modules within the same shelf
but only one is reporting this condition, replace that
module.
Or, if the FANANR condition is raised, replace the fan at the
earliest opportunity.

properly.
SH9HU and SHX9HU Slot Status LEDs

The SH9HU and SHX9HU slot status LEDs are located on the CEM/9HU front panel. The CEM/9HU has one
status LED indicator per slot. Slot LEDs indicate the operating status of the inserted modules and the
communication status to the management. Each SH9HU/SHX9HU shelf has 22 slots.
Each slot has its corresponding LED:
• “A” and “B” indicate the operating status of the half-sized modules SCU and NCU.
• “1” ... “20” indicate the communication status from the respective module to the SCU and NCU.
If the LED of the operating module is lit green, the module is operating properly and there is no failure. If the LED
is lit yellow, red, or off, the module is faulty or does not work.
Table 13 on p. 84 provides troubleshooting guidelines for SH9HU and SHX9HU slot status LEDs.
Before you start with troubleshooting, be sure that the admin status on the affected module is set
Note
Note
Table 13: SH9HU and SHX9HU Slot Status LEDs

Names
A, B; Yellow blinking Firmware / Hardware 1 Check if the NED indicates a firmware

1 - 20 to off Mismatch mismatch condition and update the
or firmware, if required.
Connection to the NCU or
2 Check if the facility admin state is set to
SCU is disrupted
"Maintenance".
or
Module admin state is in If the facility admin state is not set to
“Maintenance” to force on the “Maintenance”, the connection to the
laser or to configure a loop. NCU or SCU is disrupted, or an SCU
hardware mismatch has occurred.
3 Remove and reinsert the SCU.
replace the SCU.
contact ADVA Optical Networking
Technical Services.
Red Database Mismatch Check the PSU Power LED (P):

or • If the PSU Power LED is lit red, a
alarms
module must be replaced.
• If the PSU Power LED is lit green, but
the slot status LED is lit red, check the
alarm list.
Off flashing to The installed module does not 1 Check if the module displayed in the
red match the provisioned module NED is the same type as the one
in the database. installed.
2 If a mismatch exists, delete the incorrect
module from the NED and provision the
installed module.
Off Module admin state is • If the NED displays “unassigned”, check

“unassigned” (the module is if the correct module is provisioned. If the
not provided in the wrong module is provisioned, delete the
management), module and provision the correct one.
"management", or "disabled". • If the NED displays “management” or
"disabled", change the admin state to “In
Service”.
Table 13: SH9HU and SHX9HU Slot Status LEDs

Names
A, B; Yellow Module minor alarms Check the alarm list.

1 - 20
or
SH9HU and SHX9HU Network Element Status LEDs

There are three NE LEDs on the CEM/9HU front panel of SH9HU and SHX9HU shelves:
• Critical
• Major
• Minor
will be off.
Note
indicated. Therefore, only one of the three LEDs is lit red, yellow or is off at any given time. The three LEDs are lit
green when no failures exist at the NE. Table 14 addresses LED troubleshooting guidelines for the SH9HU and
SHX9HU NE status LEDs.
Note
Table 14: SH9HU and SHX9HU Network Element Status LEDs

Names Colors
Critical Off Communication is broken 1 Check if a firmware mismatch condition is

(FCU—SCU or SCU—NCU) displayed in NED and update the firmware, if
or required.
2 Verify that the shelf is the master or main shelf.
shelf.
3 If the LED remains off, replace the fan unit.
4 If the LED remains off, replace the SCU.
5 If the LED remains off, contact your ADVA
Optical Networking Technical Services
Representative.
Red A critical error is detected as 1 Check the NED alarm list to determine which
highest severity in the NE. module(s) has the critical failure condition(s).
At least one of the modules 2 Follow the troubleshooting guidelines specified
has a critical error. in the “Alarm and Event List” on p. 783.
Major Off Communication is broken 1 Check if a firmware mismatch condition is

or required.
shelf.
Representative.
Red A major error is detected as 1 Check the NED alarm list to determine which
highest severity in the NE. module(s) has the major failure condition(s).
has a major error. in the “Alarm and Event List” on p. 783.
Minor Off Communication is broken 1 Check if a firmware mismatch condition is

or required.
shelf.
Representative.
Yellow A minor error is detected as 1 Check the NED alarm list to determine which
highest severity in the NE. module(s) has the minor failure condition(s).
has a minor error. in the “Alarm and Event List” on p. 783.
OTDR Shelf LEDs

The OTDR/THC/2HU/AC (THC) and OTDR/8-OTH/1HU/AC (OTH) shelves are
equipped with LED indicators that provide operational status information about the
shelves. The front panel of the shelves display the LEDs for the OTDR. The LEDs are
labeled “THC”, “OTH”, , and “Server”.

Refer to the OTDR Installation, Provisioning, and Operations Manual for more information
about interpreting the LEDs and troubleshooting.
Figure 15: LED Indicators of the OTDR
Troubleshooting Power Supply Units

This section will help you resolve issues that can be experienced on the power supply
units of the SH1HU, SH7HU, and SH9HU shelves. The SH9HU and SH7HU shelves
may optionally be powered by hot-swappable AC or DC power supply units (PSU/9HU-
DC, PSU/9HU-AC, PSU/7HU-ACs or PSU/7HU-DCs).
The SH1HU-F/2DC, SH1HU-HP/2DC, and SH1HU-HP/E-TEMP/2DC shelves (1HU
shelves) are DC-powered shelves with integrated PSUs. Power is available from the
front side of the shelf via terminal block (block barrier type connectors) comprising 4
screw terminals and a plastic cover on top.
Do not open the power supply unit under any circumstances! There
are no user-serviceable parts inside. A faulty unit should be
returned to ADVA Optical Networking for repair.
WARNING
This section contains the following subsections, describing the LED behavior of
exchangeable power supply units and their variants:
“PSU/1HU-R-AC and PSU/1HU-R-DC-200” on p. 89
including the PSU/1HU-R-AC-200 variant
“PSU/7HU-AC and PSU/9HU-AC” on p. 90
including the PSU/7HU-AC-HP variant
“PSU/7HU-DC, PSU/7HU-DC-HP, PSU/7HU-DC-800, PSU/X9HU-DC-800, and
PSU/9HU-DC” on p. 91
including the PSU/7HU-DC-HP variant
“PSU/7HU-R-DC” on p. 92
including the PSU/7HU-R-DC-HP variant
PSU/1HU-R-AC and PSU/1HU-R-DC-200

This PSU/1HU-R-AC is available in the following variants:
• PSU/1HU-R-AC
• PSU/1HU-R-AC-200
In the following, PSU/1HU-R-AC refers to all its variants available with this release.
The PSU/1HU-R-AC and PSU/1HU-R-DC-200 have a single tri-color LED indicator marked “P”. The LED is
located on the faceplate of the PSU.
Note
Hazardous voltage! Always disconnect the power cord from the appliance coupler before
removing the PSU/1HU-R-AC(-200) or PSU/1HU-R-DC-200 from the shelf.
WARNING
Table 15: LED Status of the PSU/1HU-R-AC(-200) and PSU/1HU-R-DC-200

Name
P Red Over-current Verify that the combined power consumption of the

modules present in the shelf does not exceed the
maximum output power of the PSU.
If the power consumption of the modules is within the
specification, remove and reinsert the PSU.
Please note, the module should lose power for at least 10
seconds to allow any and all capacitance to dissipate.
If the condition continues, the module has been removed
and inserted, it should be returned to ADVA Optical
Networking for repair.
Yellow 90% load achieved The PSU is operating close to its limits. Check if the
power consumption can be reduced. Do not introduce any
additional hardware which might increase the power
consumption.
Off Input power failure Make sure the PSU is supplied the correct power level.
Green The unit is receiving No action is required.

the required power
level.
PSU/7HU-AC and PSU/9HU-AC

The PSU/7HU-AC is available in the following variants:
• PSU/7HU-AC
• PSU/7HU-AC-HP
• PSU/7HU-AC-800
In the following, PSU/7HU-AC refers to all its variants available with this release.
The PSU/7HU-AC and PSU/9HU-AC have a single tri-color LED indicator marked “P”. The LED is located on the
faceplate of each PSU.
Note
Hazardous voltage!
Always disconnect the AC power cord from the appliance coupler, before removing the
PSU/7HU-AC or PSU/9HU-AC from the shelf.
WARNING
Table 16: LED Status of the PSU/7HU-AC and PSU/9HU-AC
LED Name LED Colors Potential Cause Solution for Troubleshooting
P Red An overload of 100% to A hardware error has occurred. Return the PSU to
110% is reached. ADVA Optical Networking.
This unit is not receiving A hardware error has occurred. Return the PSU to
AC power, but the ADVA Optical Networking.
redundant power supply
unit provides AC power to
the shelf.
Yellow An overload of 90% to Check the power connection according to the

100% is reached. PSU specification.
Off Main supply has failed. No 1 Check the power connection. If the power
AC power is provided to connection is operational, a hardware error
the shelf. has occurred.
2 Return the PSU to ADVA Optical
Networking.
Green The unit is receiving No action is required.

adequate AC power.
The output voltage is

within the admissible
range.
PSU/7HU-DC, PSU/7HU-DC-HP, PSU/7HU-DC-800,

PSU/X9HU-DC-800, and PSU/9HU-DC
The PSU/7HU-DC is available in these variants:
• PSU/7HU-DC
• PSU/7HU-DC-HP
• PSU/7HU-DC-800
PSU/7HU-DC, PSU/7HU-DC-HP, PSU/7HU-DC-800, PSU/X9HU-DC-800, and PSU/9HU-DC units have a
single tri-color LED indicator marked “P”. The LED is located on the faceplate of each PSU.
Note
When connecting dual DC power sources, both sources must be the same polarity. Opposite-polarity
sources will damage the unit.
Hazardous voltage! Always disconnect the DC power cord from the terminal block before
removing the PSU from the shelf.
WARNING
Table 17: LED Status of the PSU/7HU-DC, PSU/7HU-DC-HP, PSU/7HU-DC-800, PSU/X9HU-DC-800,

and PSU/9HU-DC

Name Colors
P Red An overload of circa 110% is A hardware error has occurred. Return the
reached. PSU to ADVA Optical Networking.
This unit is not receiving DC 1 Check the power connection and ensure
power, but the redundant power the power feed is operational.
supply unit provides power to the 2 If the issue persists, a hardware error has
shelf. occurred. Return the PSU to ADVA
Optical Networking.
Yellow The maximum output current has Check the power connection according to the
been reached or exceeded. PSU specification.
Table 17: LED Status of the PSU/7HU-DC, PSU/7HU-DC-HP, PSU/7HU-DC-800, PSU/X9HU-DC-800,

and PSU/9HU-DC

Name Colors
P Off DC power source has failed or the 1 Check the power connection and ensure
polarity for connecting the power the power feed is operational.
cord has not been considered. No 2 If the issue persists, a hardware error has
power is provided to the shelf occurred. Return the PSU to ADVA
Optical Networking.
Green The unit is receiving DC power. No action is required.
The output voltage is in the admiss-

ible range
PSU/7HU-R-DC
The PSU/7HU-R-DC is available in the following variants:
• PSU/7HU-R-DC
• PSU/7HU-R-DC-HP
The PSU/7HU-R-DC(-HP) is exclusively designed for use in the USA.

Note
The PSU/7HU-R-DC(-HP) has a single tri-color LED indicator marked “P”. The LED is located on the faceplate of
each PSU.
Note
When connecting dual DC power sources, both sources must be the same polarity. Opposite-polarity
sources will damage the unit.
Hazardous voltage! Always turn off the corresponding power switch of the DC power
source that is connected to the faulty PSU/7HU-R-DC(-HP) before removed from the
shelf.
WARNING
Table 18: LED Status of the PSU/7HU-R-DC(-HP)

Name
P Red An overload of circa 110% is reached. A hardware error has occurred. Replace
the PSU as described in “Replacing a
This unit is not receiving DC power, PSU/7HU-R-DC or PSU/7HU-R-DC-HP”
but the redundant power supply unit on p. 716 and return the PSU to ADVA
provides power to the shelf. Optical Networking.
Yellow The maximum output current has Check the power connection according to
been reached or exceeded. the PSU specification.
Off DC power source has failed or the 1 Check the power connection. If power
polarity for connecting the power cord connection is OK, a hardware error
has not been considered. No power is has occurred.
provided to the shelf. 2 Replace the PSU as described in
“Replacing a PSU/7HU-R-DC or
PSU/7HU-R-DC-HP” on p. 716 and
return the PSU to ADVA Optical
Networking.
lead.
Green The unit is receiving DC power. No action is required.
The output voltage is in the

admissible range.
Chapter 4
Core Type Channel Modules

This chapter addresses all core type channel modules available at the publication date of
this manual.
This chapter contains these sections:
“Troubleshooting Core Type TDM Channel Modules” on p. 96, which addresses LED
indicators and troubleshooting guidelines for TDM core channel modules.
“Troubleshooting Core Type WDM Channel Modules” on p. 165, which addresses LED
indicators and troubleshooting guidelines for WDM core channel modules.
A green client/network port LED indicates no conditions are present at

the port that require troubleshooting this port, to resolve fault(s)
associated with the transported signal(s). Conditions informing about
consequent actions (e.g. LKDO-OFF) are not indicated by these LEDs,
Note since they require troubleshooting the fault upstream (at another port of
the same module or a remote module).
Troubleshooting Core Type TDM Channel Modules
Troubleshooting Core Type TDM Channel

Modules
This section will help you resolve issues that can be experienced on TDM core channel
modules. One very important difference between the single application and TDM core
channel modules is that the single application modules require that an application signal
be present before it attempts to establish a network link.
The TDM core channel modules, however, will attempt to establish the network link
immediately upon power on. This leads to slight differences in what you could expect to
see as normal LED states.
The LEDs are located on the faceplate of every TDM core channel module. This section
contains the following subsections:
“4TCC-PCN-2G1U+2G5” on p. 97
“4TCC-PCTN-2G7+10G” on p. 104
“4TCC-PCTN-10G+40G-L#DC” on p. 111
“10TCC-PCN-2G7US+10G” on p. 120
“10TCC-PCTN-4GU(S)+10G” on p. 127
“10TCC-PCTN-10G+100GB and 10TCC-PCTN-10G+100GC” on p. 134
“10TCC-PCN-3GSDI+10G” on p. 143
“10TCC-PCN-40GU+100G” on p. 150
“16TCC-PCN-4GUS+10G” on p. 157
4TCC-PCN-2G1U+2G5
This subsection will help you resolve issues that can be experienced on 4TCC-PCN-2G1U+2G5 modules.
It assumes that all measurements for the C1/R, C1/T, C2/R, C2/T, C3/R, C3/T, C4/R, C4/T, N/R West, N/R
East and N/T West, N/T East interfaces are within ADVA Optical Networking specifications and that you have
verified that the application wavelength is the same as the wavelength for the FSP 3000R7 module client
interfaces. If not, please refer to “Finding Your Problem - Follow the Light” on p. 53 in this document.
Follow all the instructions precisely. If you do not supply the specified attenuation on given
steps, you could destroy the module being tested. As soon as the near-end and the far-end
4TCC-PCN-2G1U+2G5 modules in a link are synchronized, the network link is up. The network
interface LEDs light up solid green or blink green depending on the configured transmission
CAUTION
mode: Multiplexer NE Only, Multiplexer NW Only, Multiplexer NE & NW, or Regenerator 1-Way.
Before you start with troubleshooting, be sure that the current firmware package is installed on
the 4TCC-PCN-2G1U+2G5 module. For details on updating module firmware, refer to “Updating
the NE Software Release” on p. 617 and “Performing Other Software Update Actions” on p. 628.
Note
Before you start with troubleshooting, ensure that the admin status on the affected module is
configured to “Maintenance”.
Note
The near-end and far-end modules must be configured in the same transmission mode to
guarantee proper function.
Note
The use of pluggable transceivers other than those approved by ADVA Optical Networking will
result in loss of safety approval for the FSP 3000R7. Pluggable transceivers not approved by
ADVA Optical Networking will not function properly. Depending on the channel module type, Rx
and Tx of the affected interfaces may be disabled automatically or not. Only approved pluggable
CAUTION
transceivers will guarantee the behavior in conjunction with the channel module as specified.
Note
The steps in this subsection may need to be completed on both sides of the link. Please follow the
troubleshooting steps in Table 19 on p. 98 based upon the states of the LEDs.
The 4TCC-PCN-2G1U-2G5 has eight LEDs on the faceplate:
• “P” to indicate the power supply status
• “Mod” to indicate the operation status of the module
• “C1”, “C2”, “C3”, “C4”, “NW” and “NE to indicate the interface status
This module has 4 client interfaces (C1 to C4). The LED status in Table 19 on p. 98 refers to one client interface
(Cx) as an example for all client interfaces on the module.
When a module is removed, it should not be reinserted for at least 10 seconds to allow all power
on the module to dissipate.
Note
Table 19: LED Status of the 4TCC-PCN-2G1U+2G5

Name
All LEDs Red A serious error in card initialization. Remove and reinsert the module.
If the condition continues, return the
P Yellow Power is abnormal. module to ADVA Optical Networking for
Off Power failure repair.
Green Power is OK. No action is required.
Mod Yellow Communication between protected Check the Config tab on the port
channel modules has failed. associated with the protection and verify
that the module AIDs for the protected
modules are correct.
Yellow blinking Management communication to the 1 Check the SCU firmware version
to off module has failed. and compare it to the version listed
on the NCU. If they are different,
update the SCU firmware as
described in “Performing Other
Software Update Actions” on p. 628.
2 Remove and reinsert the module.
If the LED is still blinking yellow to off,
Off Module admin state is disabled. 1 In case the module is installed and
provisioned, check the admin state
settings.
2 If the management displays
“disabled”, change the admin state
to “In Service”.
Module admin state is unassigned. 1 If the management displays

“unassigned”, check if the module is
provisioned.
2 If required, provision the module.
Green Module provisioned, admin state is No action is required.

“Maintenance”, “Management” or
“In Service”

Name
Cx Red Pluggable transceiver was inserted Reinsert the pluggable transceiver.

and interface provisioned, then the
pluggable transceiver was
removed.
Pin max too high, receiver damage Measure the optical input power on the
threshold exceeded. receiver connector and compare the
measured value with the channel
module/pluggable transceiver
specification.
Adjust the optical input power (i.e.,
install the appropriate attenuators) to
fulfill the Optical Input Power
requirements.
Yellow Loss of clock Verify that the provisioned service type

matches the incoming signal type.
Check optical power measurements.
Refer to the procedure in “Finding Your
Problem - Follow the Light” on p. 53 in
this document.
Signal degrade The number of bit/block errors exceeded

the configured threshold. To identify the
failure location, refer to the
troubleshooting instructions for the
relevant signal degrade condition
outlined in Alarm and Event List.
Loss of character sync Unable to synchronize on the characters

in the incoming data stream.
Verify that fiber cables are connected.
Check optical power levels. Refer to
“Finding Your Problem - Follow the Light”
on p. 53 in this document.
Loss of signal Verify that fiber cables are connected.

Check optical power levels. Refer to

Name
Cx Yellow Optical Input Power out of range Measure the optical input power on the
receiver connector.
Compare the measured value with the
channel module/pluggable transceiver
specification.
Adjust the optical input power (i.e.,
requirements.
Loss of frame - No frame sync Verify that the provisioned service type
detected matches the incoming signal type.
Check optical power measurements.
Refer to the procedure in “Finding Your
this document.
Loss of input power - Power non- Refer to “Finding Your Problem - Follow
existing or below the defined the Light” on p. 53 in this document..
minimum level is detected at the
input.
Loss of output power - Power non-

existing or below the defined
output. Normally a consequence of
loss of optical input power. Also
may be due to failure/degeneration
of an internal component or splice.
Off No Ch Interface (Facility) Install an appropriate pluggable

provisioned on that pluggable transceiver.
transceiver. Provision the pluggable transceiver.
Enable the admin state - Configure the
pluggable transceiver admin state to “In
Service”.
Provision a Ch Interface (Facility) on the
pluggable transceiver.
Enable the Ch Interface (Facility) admin
state - Configure the Ch Interface
(Facility) admin state to “In Service”.
Ch Interface (Facility) admin state Change Ch Interface (Facility) admin

is disabled. state.

Name
Cx Off flashing to Pluggable transceiver mismatch – Compare the supported data rates of the
red None of the data rates supported board with the pluggable transceiver
by the installed pluggable data rates.
transceiver match the data rates Install the correct pluggable transceiver.
supported by the channel module.
Pluggable transceiver is not Consult your technical

approved by ADVA Optical servicesrepresentative about obtaining a
Networking - no traffic. pluggable transceiver approved by
Green Interface is active, valid signal, No action is required.

valid hardware, no alarms
NW, NE Red Pluggable transceiver was inserted Reinsert the pluggable transceiver.
removed.
Pin max too high, receiver damage 1 Measure the optical input power on
threshold exceeded. the receiver connector and compare
the measured value with the channel
specification.
2 Adjust the optical input power (i.e.,
requirements.
Yellow Loss of clock 1 Verify that the provisioned service

type matches the incoming signal
type.
2 Check optical power
measurements. Refer to the
procedure in “Finding Your Problem -
Follow the Light” on p. 53 in this
document.


Name
NW, NE Yellow Loss of signal 1 Verify that fiber cables are

connected.
2 Check optical power levels. Refer to
“Finding Your Problem - Follow the
Light” on p. 53 in this document.
Optical Input Power out of range 1 Measure the optical input power on
the receiver connector.
2 Compare the measured value with
the channel module/pluggable
transceiver specification.
requirements.
Loss of frame - No frame sync 1 Verify that the provisioned service

detected type matches the incoming signal
type.
document.
existing or below the defined the Light” on p. 53 in this document.
input.

Yellow flashing Loss of output power Channel module is configured to

to off Interface in a protection Transmission Mode “Multiplexer NE &
configuration (i.e. interface not NW”. Data is transmitted via the active
capable of taking over traffic). line. The backup line is not available.
Check the cabling. Refer to “Finding
Your Problem - Follow the Light” on
p. 53.

Name
NW, NE Yellow off for ALS pulse received. Network link is not coming up.
500 ms 1 Verify that fiber cables are
connected.
Green flashing Interface in a protection group and No action is required - Channel module
to off running error free (i.e. interface is is working in the Transmission Mode
capable of taking over traffic). “Multiplexer NE & NW”
Off No Ch Interface (Facility) 1 Install an appropriate pluggable

transceiver. 2 Provision the pluggable transceiver.
3 Enable the admin state - Configure
the pluggable transceiver admin
state to “In Service”.
4 Provision a Ch Interface (Facility) on
the pluggable transceiver.
5 Enable the Ch Interface (Facility)
admin state - Configure the Ch
Interface (Facility) admin state to “In
Service”.

is disabled. state.
Off flashing to Pluggable transceiver mismatch – 1 Compare the supported data rates of
red None of the data rates supported the board with the pluggable
by the installed pluggable transceiver data rates.
transceiver match the data rates 2 Install the correct pluggable
supported by the channel module. transceiver.
Pluggable transceiver is not Consult your technical

approved by ADVA Optical servicesrepresentative about obtaining a
Networking - no traffic pluggable transceiver approved by

4TCC-PCTN-2G7+10G
This subsection will help you resolve issues that can be experienced on the 4TCC-PCTN-2G7+10G.
This module is available in different variants that are described in the Hardware Description.
It assumes that all measurements for the C1/R, C1/T, C2/R, C2/T, C3/R, C3/T, C4/R, C4/T and the network
interface are within ADVA Optical Networking specifications and that you have verified that the application
wavelength is the same as the wavelength for the client pluggable transceiver interface. If not, refer to “Finding
Your Problem - Follow the Light” on p. 53 in this document.
4TCC-PCTN-2G7+10G module are synchronized in a link the network link is up and the network
CAUTION interface LED will light up solid green.
Before you start with troubleshooting, ensure that the current firmware package is installed on
the 4TCC-PCTN-2G7+10G module. For details on updating module firmware, refer to “Updating
Note
Note
CAUTION
Note
Scrambling of virtual facilities can be enabled or disabled on this module. Enabled is according to standard.
Notice that the default setting is disabled. If the modules at each end of the link are configured differently, this will
result in ODU-AIS or SD-ODU on all four VCHs. To fix: ensure that the setting is the same at both ends of the
link. Use the "Facility Scramble" field on the module’s Config tab.
The 4TCC-PCTN-2G7+10G features seven LEDs on the faceplate:
• “C1”, “C2”, “C3”, “C4” and “N” to indicate the interface status
This module has 4 client interfaces (C1 to C4). The LED states in Table 20 on p. 105 refer to one client interface
(Cx) as an example for all client interfaces on the module.
Note
Table 20: LED Status of the 4TCC-PCTN-2G7+10G

Name
If the condition continues, return this
to off module has failed. and compare it to the SCU firmware
version as listed on the NCU. If they
are different, update the SCU
firmware as described in
“Performing Other Software Update
Actions” on p. 628.
2 Remove and insert the module.
Off Module admin state is disabled. 1 If the module is installed and

settings.
to “In Service”, “Management” or
“Maintenance”.

provisioned.
2 If required provision the module.

“In Service”

Name

removed.
specification.
requirements.

type.
measurements. Refer to “Finding
p. 53 in this document.


1 Verify that fiber cables are
connected.

Name
Cx Yellow Loss of signal 1 Verify that fiber cables are

connected.
the procedure, “Finding Your
Problem - Follow the Light” on p. 53
in this document.
receiver connector.
requirements.

type.
Trace identifier mismatch Check the values of expected and

received trace on the affected interface.
Also verify the trace identifier sent to the
affected interface.
input.


Name
Cx Off No Ch Interface (Facility) 1 Install an appropriate pluggable

Service”.

is disabled. state.
Pluggable transceiver is not Consult your technical services

approved by ADVA Optical representative about obtaining a

N Red Pin max too high, receiver damage 1 Measure the optical input power on
specification.
requirements.

Name
N Yellow Loss of clock 1 Verify that the provisioned service

type.


connected.
Loss of signal 1 Verify that fiber cables are

connected.
requirements.

Name
N Yellow Loss of frame - No frame sync 1 Verify that the provisioned service
type.
input.
Loss of output power - Power non- Refer to “Finding Your Problem - Follow
Trace identifier mismatch (ODU- Check the values of expected and

TIM/ITU-TIM). received trace on the affected interface.
affected interface.
Yellow flashing Module is acting as standby in There seems to be a problem with the
to off channel card protection and fiber connectivity of the protection path.
protection path is not available. Refer to “Finding Your Problem - Follow
the Light” on p. 53 in this document.
Yellow off for ALS pulse received. Network link is not coming up.
500 ms ALS pulse detected. 1 Verify that fiber cables are
connected.
Green flashing Module is acting as standby in No action is required.

to off channel card protection and
protection path is not available.

Name
N Off No Ch Interface (Facility) 1 Install an appropriate pluggable

Service”.

is disabled. state.

Networking - no traffic pluggable transceiver that is approved
by ADVA Optical Networking.

4TCC-PCTN-10G+40G-L#DC
This subsection will help you resolve issues that can be experienced on the 4TCC-PCTN-10G+40G-L#DC.
It assumes that all measurements for the C1/R, C1/T, C2/R, C2/T, C3/R, C3/T, C4/R, C4/T and the network
interface are within ADVA Optical Networking specifications and that you have verified that the application
Your Problem - Follow the Light” on p. 53 in this document.
steps, you could destroy the module being tested. As soon as the near-end and far-end 4TCC-
PCTN-10G+40G-L#DC modules are synchronized in a link, the network link is up and the
CAUTION network interface LED will light up solid green.
the 4TCC-PCTN-10G+40G-L#DC module. For details on updating module firmware, refer to
“Updating the NE Software Release” on p. 617 and “Performing Other Software Update Actions”
Note on p. 628.
Note
CAUTION
Note
The multi-frame alignment signal is not included when creating ODU-AIS on 4TCC-PCTN-
10G+40G-L#DC channel modules. A LOM will be raised and any allowed traces are not usable
during ODU-AIS insertion.
Note
Please follow the troubleshooting steps in Table 21, based upon the states of the LEDs.
The 4TCC-PCTN-10G+40G-L#DC features seven LEDs on the faceplate:
• “C1”, “C2”, “C3”, “C4” and “N” to indicate the interface status
This module has 4 client interfaces (C1 to C4). The LED states in Table 21 refer to one client interface (Cx) as an
example for all client interfaces on the module.
Note
Table 21: LED Status of the 4TCC-PCTN-10G+40G-L#DC

Name
If the condition continues, the module
P Yellow Power is abnormal. should be returned to ADVA Optical
Off Power failure. Networking for repair.

Name
settings.

provisioned.

“In Service”

and the interface provisioned, then
the pluggable transceiver was
removed.

Name
Cx Red Pin max too high, receiver damage 1 Measure the optical input power on
specification.
requirements.

type.
document.


connected.
the procedure in “Finding Your
in this document.

connected.
in this document.

Name
Cx Yellow Optical Input Power out of range 1 Measure the optical input power on
receiver connector.
requirements.

type.
document.

affected interface.
input.


Name

Service”.

is disabled. state.
Pluggable transceiver is not Consult your ADVA Optical Networking

approved by ADVA Optical Representative about obtaining a
Networking - no traffic. pluggable transceiver that is approved

valid hardware, no alarms.
specification.
requirements.

Name

type.
document.


connected.

connected.
requirements.

Name
type.
document.
input.

Trace identifier mismatch (ODU- Check the values of expected and

TIM/ITU-TIM). received trace on the affected interface.
affected interface.
connected.


Name
N Off No Ch Interface (Facility) 1 Install an appropriate pluggable

Service”.

is disabled. state.
Pluggable transceiver not approved Consult your ADVA Optical Networking

by ADVA Optical Networking - no Representative about obtaining a
traffic pluggable transceiver approved by

10TCC-PCN-2G7US+10G
This subsection will help you resolve issues that can be experienced on the 10TCC-PCN-2G7US+10G.
It assumes that all measurements for C1/R through C10/R, C1/T through C10/T and the network interface are
within ADVA Optical Networking specifications and that you have verified that the application wavelength is the
same as the wavelength for the client SFP interface. If not, refer to “Finding Your Problem - Follow the Light” on
steps, you will destroy the module being tested. As soon as the near-end and the far-end
10TCC-PCN-2G7US+10G module are synchronized in a link the network link is up and the
Before you start with troubleshooting, ensure that the current software package is installed on
the 10TCC-PCN-2G7US+10G module. For details on updating module firmware, refer to
Note on p. 628.
Before you start with troubleshooting, ensure that the administrative state on the affected
module is configured to “Maintenance”.
Note
The module supports configuring ‘disparity correction’. It is set to “enabled” by default. For more
information about this parameter, refer to the Management Data Guide.
Note
result in loss of safety approval for the FSP 3000R7. SFPs/XFPs not approved by ADVA Optical
Networking will not function properly. Depending on the channel module type, Rx and Tx of the
affected interfaces may be disabled automatically or not. Only approved SFPs/XFPs will
CAUTION
guarantee the behavior in conjunction with the channel module as specified.
Note
The steps in this subsection will need to be completed on both sides of the link. Please follow the troubleshooting
steps in Table 22 on p. 121 based upon the states of the LEDs.
The 10TCC-PCN-2G7US+10G features fourteen LEDs on the faceplate:
• “C1”, “C2”, “C3”, “C4”, C5”, “C6”, “C7”, “C8”, “C9”, “C10”, "NW", and “NE” to indicate the interface status
This module has 10 client interfaces (C1 to C10). The LED states in Table 22 on p. 121 refer to one client
interface (Cx) as an example for all client interfaces on the module.
Please note, the module should lose power for at least 10 seconds to allow any and all
capacitance to dissipate.
Note
Table 22: LED Status of the 10TCC-PCN-2G7US+10G

Name
All LEDs Red A serious error in card initialization Remove and reinsert the module.
Mod Yellow Communication between protected 1 Check the Protection AID

channel modules configuration of the channel module.
has failed. 2 For the verification go to the network
interface, to the “Config” tab. The
Protection AID points to the paired
active protection channel modules.
Only same module types can be
configured to a protection pair.
Yellow flashing Management communication is 1 Check the management for an SCU

to off broken. and channel module firmware
update. If so, execute the update
procedure. To update software, refer
to “Performing Other Software
Update Actions” on p. 628.
If the LED is still flashing yellow to off,
Technical Representative.
Off Module admin state is disabled. • If the module is installed and

settings.
“Maintenance”.
Module admin state is unassigned. • If the management displays

provided to the management.
• If the module is not provided, make
a module provisioning.

Name
Mod Green Module provisioned, admin state is No action is required.

“In Service”

removed.
specification.
requirements.
Tx Laser Failure Replace the malfunctioning pluggable

transceiver, if a replacement is
available.
Otherwise, return the malfunctioning
pluggable transceiver to ADVA Optical
Red flashing to Pluggable transceiver mismatch – 1 Compare the supported data rates of
off None of the data rates supported the board with the pluggable

Yellow Loss of clock 1 Verify that clock is set to match

application speed (if multi clock
module).
measurements.

Name
Cx Yellow Signal degrade The number of bit/block errors exceeded


connected.
in this document.

connected.
in this document.
Optical Input Power out of range. 1 Measure the optical input power on
receiver connector.
requirements.
Loss of frame - No frame sync Check the physical connection to

detected. prevent a module mismatch within a link.

Name
Cx Yellow Loss of input power - Power non- Refer to “Finding Your Problem - Follow
input.

Yellow flashing In a client channel card protection Refer to “Finding Your Problem - Follow
to off configuration, the protection path the Light” on p. 53 in this document.
corresponding to this standby port
is unavailable.
Green flashing Pluggable transceiver is not No action is required.

to red approved by ADVA Optical
Networking, but transmits traffic.

Service”.

is disabled. state.
Green flashing In a client channel card protection No action is required.

to off configuration, this standby port is
operating error-free. Hence, the
interface is capable of taking over
traffic.


Name
NW, NE Red Pin max too high, receiver damage 1 Measure the optical input power on
specification.
requirements.
Red flashing to Pluggable transceiver mismatch – 1 Compare the supported data rates of
off None of the data rates supported the board with the pluggable
Yellow Pluggable transceiver is not Consult your technical services

Loss of clock Check the correct clock settings on the

channel modules according the
connected application.


connected.

connected.

Name
NW, NE Yellow Optical Input Power out of range. 1 Measure the optical input power on
requirements.

detected. prevent a module mismatch within a link.
input.

Yellow off for ALS pulse received or detected. Network link is not coming up.
connected.
Green flashing Pluggable transceiver is not Consult your technical services

to red approved by ADVA Optical representative about obtaining a
Networking, but is transmitting pluggable transceiver approved by
traffic. ADVA Optical Networking.
Off Interface admin state is disabled. • If the module is installed and

settings.
“Maintenance”.

Name
NW, NE Off Interface admin state is Change Ch Interface (Facility) admin

unassigned. state.

10TCC-PCTN-4GU(S)+10G
This subsection will help you resolve issues that can be experienced on the 10TCC-PCTN-4GU+10G and
10TCC-PCTN-4GUS+10G.
The modules are available in different variants that are described in the Hardware Description.
same as the wavelength for the client pluggable transceiver interface. If not, refer to “Finding Your Problem -
Follow the Light” on p. 53 in this document.
10TCC-PCTN-4GU(S)+10G modules are synchronized in a link, the network link is up and the
the 10TCC-PCTN-4GU(S)+10G module. For details on updating module firmware, refer to
Note on p. 628.
Note
The 10TCC-PCTN-4GUS+10G module supports configuring ‘disparity correction’. It is set to

“enabled” by default. For more information about this parameter, refer to the Management Data
Guide.
Note
CAUTION
Note
The 10TCC-PCTN-4GU(S)+10G features thirteen LEDs on the faceplate:
• “C1”, “C2”, “C3”, “C4”, C5”, “C6”, “C7”, “C8”, “C9”, “C10” and “N” to indicate the interface status
This module has 10 client interfaces (C1 to C10). The LED states in Table 23 on p. 128 refer to one client
Note
Table 23: LED Status of the 10TCC-PCTN-4GU(S)+10G

Name
P Yellow Power is abnormal. should be returned to ADVA Optical
Off Power failure Networking for repair.
channel modules associated with the protection and verify
has failed. that the module AIDs for the protected
Yellow flashing Management communication to the 1 Check the SCU firmware version

Name
Mod Off Module admin state is disabled. 1 If the module is installed and
settings.
“Maintenance”.

provisioned.

“In Service”

removed.
specification.
requirements.

type.
document.

Name
Cx Yellow Loss of character sync Unable to synchronize on the characters

connected.
in this document.

connected.
in this document.
receiver connector.
requirements.
input.


Name

Service”.

is disabled. state.

Networking - no traffic. pluggable transceiver that is approved

specification.
requirements.

Name
N Yellow Loss of clock. 1 Verify that the provisioned service

type.
document.


connected.
requirements.

type.
document.
input.

Name
N Yellow Loss of output power - Power non- Refer to “Finding Your Problem - Follow
connected.


Service”.

is disabled. state.

Name
N Off flashing to Pluggable transceiver is not Consult your technical services

red approved by ADVA Optical representative about obtaining a

10TCC-PCTN-10G+100GB and 10TCC-PCTN-10G+100GC

This subsection provides troubleshooting guidelines for 10TCC-PCTN-10G+100GB and 10TCC-PCTN-
10G+100GC modules, henceforth referred to as 10TCC-PCTN-10G+100GB/C in this document.
10TCC-PCTN-10G+100GB/C modules are synchronized in a link, the network link is up and the
the 10TCC-PCTN-10G+100GB/C module. For details on updating module firmware, refer to
Note on p. 628.
Note
The 10TCC-PCTN-10G+100GB/C module supports configuring ‘disparity correction’. It is set to

Guide.
Note
CAUTION
Note
The 10TCC-PCTN-10G+100GB/C features thirteen LEDs on the faceplate:
• “Mod” to indicate the operating status of the module
• For 10G operation, “C1”, “C2”, “C3”, “C4”, C5”, “C6”, “C7”, “C8”, “C9”, “C10” indicates the status of the
respective client interface.
• When C1 through C4 are used for 40G operation, "C1" indicates the logical "OR" of the C1C4 40G client
interface status and the C1 OTL physical layer status, while "C2" through "C4" indicate the physical layer
status of the respective OTL. Similarly, when C5 through C9 are used for 40G operation, "C5" indicates the
logical "OR" of the C6C9 40G client interface status and the C6 OTL physical layer status, while "C7"
through "C9" indicate the physical layer status of the respective OTL.
• “N” to indicate the operating status of the network interface
This module has 10 SFP client interfaces (C1 to C10).
Note
Table 24: LED Status of the 10TCC-PCTN-10G+100GB/C

Name
Mod Red Critical or major equipment alarms Use the network management system to
are raised on the module. view the equipment alarm(s) raised on
this module.
Next, refer to the “Alarm and Event List”
on p. 783 to resolve the alarm condition
(s).
Yellow Communication between protected Check the Config tab on the port

Name
Mod Yellow flashing Management communication to the 1 Check the SCU firmware version

settings.
“Maintenance”.

provisioned.

“In Service”

removed.
Yellow Tx Laser Failure. Replace the malfunctioning pluggable

available.

Name
Cx Yellow Pin max too high, receiver damage 1 Measure the optical input power on
specification.
2 Adjust the optical input power (by
installing appropriate attenuators) to
meet the Optical Input Power
requirements.
Loss of clock 1 Verify that the provisioned service

type.
document.

connected.
in this document.

Name

connected.
2 If a 40G client is active on C1C4 or
C6C9 and C1 or C6 is lit yellow, first
troubleshoot any "Loss of clock",
"Loss of character sync", or "Loss of
signal" failures indicated on the
other Cx LEDs associated with this
40G client.
3 If a filter cable1 or a breakout cable2
is connected to this port for 40G
operation, ensure that the
filter/breakout cable is properly
connected to the 40G signal source
in this document.
receiver connector.
requirements.
1J/SM/4CS-#C1270-#C1330/LC/0400
2J/MM50/MPO12-LC08/0300 or J/MM50/MPO12-LC08/1000

Name
C1, C6 Yellow Loss of lane 1 If any of the other Cx LEDs

(40G associated with this 40G client
traffic signal are lit yellow, follow the
only) troubleshooting steps outlined
earlier for "Loss of clock", "Loss of
character sync", and "Loss of
signal".
2 Inspect the physical cable
associated with this port and clean
the fiber connections as needed.
Replace the cable assembly if
required.
3 If the condition persists, replace the
corresponding pluggable
transceiver.
Cx Yellow flashing In a client channel card protection Refer to the procedure in “Finding Your
(10G to off configuration, the protection path Problem - Follow the Light” on p. 53 in
traffic) corresponding to this standby port this document.
is unavailable. Either no power is
C1, C6 detected at the input, or a power
(40G level below the defined minimum
traffic) value is detected.

operating error-free. Hence the
traffic.
Cx Green Interface is active, valid signal, No action is required.

C5 Off A 40G client is active on C1C4. If a 40G client is active on C1C4, no

action is required.
C10 Off A 40G client is active on C6C9. If a 40G client is active on C6C9, no
action is required.
Cx Off A 40G client is active on C1C4 or If C5 or C10 is off and a 40G client is act-
C6C9. ive on C1C4 or C6C9, corrective actions
are not required.

Name
Cx Off No Ch Interface (Facility) pro- 1 Install an appropriate pluggable

visioned on that pluggable trans- transceiver.
ceiver. 2 Provision the pluggable transceiver.
Service”.

is disabled. state.
Off flashing to Pluggable transceiver mismatch 1 Compare the supported data rates of
red (MEA-ACCEPT) – None of the data the board with the pluggable
rates supported by the installed transceiver data rates.
pluggable transceiver match the 2 Install the correct pluggable
data rates supported by the transceiver.
channel module.

Networking (MEA-APPROVE) - no pluggable transceiver that is approved
traffic. by ADVA Optical Networking.
N Red Tx Laser Failure Replace the module, if a replacement is

available.
Otherwise, return the module to ADVA
Optical Networking for repair.
threshold exceeded the receiver port and compare the
measured value with the module
input specification.
requirements.
Yellow Loss of clock Check optical power measurements.

Refer to the procedure, “Finding Your
this document.

Name
N Yellow Signal Degrade The number of bit/block errors exceeded

failure location, refer to the troubleshoot-
ing instructions for the relevant signal
degrade condition outlined in Alarm and
Event List.

connected.
Loss of lane 1 Inspect the physical cable

required.
2 Verify that each optical span along
the path taken by the multi-lane
channel signal conforms to the
engineering specifications for the
link, especially that each link
conforms to the specified PMD
limitations.
3 Verify that each dispersion
compensation entity along the path
of the multi-lane channel signal
conforms to the engineering
requirements.
associated module.
far-end module.

Name
N Yellow Auto shutdown (Temp) 1 Verify that the equipment operating

environment for the corresponding
shelf meets specifications, and that
the air filter is clean and
unobstructed.
2 Verify the fan units in this shelf are
operating correctly.
3 Verify the module placement and the
equipment within this shelf
conforms to the product's
engineering guidelines.
module.
the module network port input
specification.
requirements.
Loss of frame - No frame sync Check optical power measurements.

detected Refer to the procedure, “Finding Your
this document.
input.


(ODU-TIM/ITU-TIM) received trace on the affected interface.
affected interface.

Name
N Off The network channel (facility) has 1 Provision the network channel
not been provisioned. (facility).
2 Enable the network channel (facility)
admin state as described below in
“Change the network channel
(facility) admin state”.
The network channel (facility) Change the network channel (facility)

admin state is disabled. admin state - If the admin state is set to
“Disabled”, change it to “In Service”,
“Management” or “Maintenance”. For
information when to use these admin
states and what they mean, refer to the
System Description, “Management”
chapter.

10TCC-PCN-3GSDI+10G
This subsection provides LED troubleshooting guidelines for 10TCC-PCN-3GSDI+10G modules.
within ADVA Optical Networking specifications and that you have verified that the application wavelength
matches the wavelength for the client SFP interface. If not, refer to “Finding Your Problem - Follow the Light” on
steps, you will destroy the module being tested. As soon as the near-end and the far-end
10TCC-PCN-3GSDI+10G module are synchronized in a link, the network link is up and the
CAUTION network interface LED will be lit solid green.
the 10TCC-PCN-3GSDI+10G module. For details on updating module firmware, refer to
Note on p. 628.
Note
Note
affected interfaces may be disabled automatically. Only approved SFPs/XFPs will guarantee
CAUTION
the behavior in conjunction with the channel module as specified.
steps in Table 25 based upon the LED states.
The 10TCC-PCN-3GSDI+10G features fourteen LEDs on the faceplate:
• “C1”, “C2”, “C3”, “C4”, C5”, “C6”, “C7”, “C8”, “C9”, “C10” to indicate the client interface status
• "NW" and “NE” to indicate the network interface status
Note
Table 25: LED Status of the 10TCC-PCN-3GSDI+10G

Name
P Yellow Power is abnormal. module to ADVA Optical Networking
Off Power failure for repair.
Mod Red Initialization failure Remove and reinsert the module.

module to ADVA Optical Networking
for repair.
Yellow Communication between protected 1 Check the Protection AID

channel modules configuration of the channel
has failed. module.
2 For the verification go to the
network interface, to the “Config”
tab. The Protection AID points to
the paired active protection channel
modules. Only same module types
can be configured to a protection
pair.

Name
Mod Yellow flashing Management communication is 1 Check the management for an

to off broken. SCU and channel module firmware
procedure. To update software,
refer to “Performing Other Software

settings.
“Maintenance”.
Module admin state is unassigned. • If the management displays

“unassigned”, check if the module
is provided to the management.

“Maintenance”, “Management” or “In
Service”

pluggable transceiver was removed.
threshold exceeded. the receiver connector and
compare the measured value with
2 If this port supports two active
unidirectional services, repeat Step
1 for the second service.
3 Adjust the optical input power
(install the appropriate attenuators)
at the receiver(s) to ensure the
optical input power requirements
are met.

Name
Cx Yellow Tx Laser Failure Replace the malfunctioning pluggable

available.
Loss of character sync1 Unable to synchronize on the

characters in the incoming data stream.
connected properly.
2 Check optical power levels. Refer
to the procedure in “Finding Your
in this document.
unidirectional services, repeat
steps 1 and 2 for the second
service.

connected properly.
in this document.
service.
1Only indicated if the client channel entity is cross connected to the network-facing channel entity.

Name
Cx Yellow Optical Input Power out of range. 1 Measure the optical input power on
service.
are met.
minimum level is detected at the If this port supports two active
input. unidirectional services, repeat this step
for the second service.
loss of optical input power. Also may
be due to failure/degeneration of an
internal component or splice.


provisioned on the pluggable transceiver.
transceiver. 2 Provision the pluggable
transceiver.
4 Provision a Ch Interface (Facility)
on the pluggable transceiver.
Interface (Facility) admin state to
“In Service”.

Name
Cx Off Ch Interface (Facility) admin state is Change Ch Interface (Facility) admin

disabled. state.
Off flashing to Pluggable transceiver mismatch – 1 Compare the supported data rates
red None of the data rates supported by of the board with the pluggable
the installed pluggable transceiver transceiver data rates.
match the data rates supported by 2 Install the correct pluggable
the channel module. transceiver.
Pluggable transceiver is not Consult your technical services rep-

approved by ADVA Optical resentative about obtaining a pluggable
Networking - no traffic. transceiver approved by ADVA Optical
Networking.
Green Interface is active, valid signal, valid No action is required.

hardware, no alarms

available.
install the appropriate attenuators)
to fulfill the Optical Input Power
requirements.
Yellow Signal degrade The number of bit/block errors

exceeded the configured threshold. To
identify the failure location, refer to the

Name

connected.
to “Finding Your Problem - Follow
requirements.

detected. prevent a module mismatch within a
link.
input.

to red approved by ADVA Optical rerepresentative about obtaining a
Networking, but is transmitting pluggable transceiver approved by
traffic. ADVA Optical Networking.

settings.
“Maintenance”.
Interface admin state is unassigned. Change Ch Interface (Facility) admin

state.

Name
NW, NE Off flashing to Pluggable transceiver mismatch – 1 Compare the supported data rates

approved by ADVA Optical Net- resentative about obtaining a pluggable
working - no traffic. transceiver approved by ADVA Optical
Networking.

hardware, no alarms
10TCC-PCN-40GU+100G
This subsection provides troubleshooting guidelines for 10TCC-PCN-40GU+100G.
10TCC-PCN-40G+100G modules are synchronized, the network link is up and the network
the 10TCC-PCN-40G+100G module. For details on updating module firmware, refer to “Updating
Note
Note
CAUTION
Note
troubleshooting steps in Table 26 based upon the states of the LEDs.
Each 10TCC-PCN-40GU+100G module has 16 LEDs on its faceplate:
• "Cx" to indicate the operation of the corresponding client interface
• "Nx" to indicate the operation of the network interface
In Table 26, Cx refers to the corresponding client interface, Nx refers to the corresponding network interface.
• If the CFP has a single connector
l "N" LED indicates the status of the network interface
l "N2" LED remains off
• If the CFP has four connectors
l “N” LED indicates the overall status and the status of the optical transport lane connected to N
l "N2" LED indicates the status of the optical transport lane connected to N2
• For 10G client services, each interface supports a single client service
l “Cx” (x = 1 through 10) LED indicates the status of the client service connected to the port
When a module is removed, it should not be reinserted for at least 10 seconds to allow residual
power on the module to dissipate.
Note
Table 26: LED Status of the 10TCC-PCN-40GU+100G

Name
All LEDs Red A serious error in card ini- Remove and reinsert the module. If the con-
tialization. dition persists, return the module to ADVA
Optical Networking.
P Yellow Power is abnormal.
Off Power failure
Mod Yellow Communication failure Using NED, verify that the module AID val-
between channel modules ues for the protected modules are correct.
that use client channel card
protection.

Name
Mod Yellow blinking Management 1 Check the SCU firmware version, and
to off communication to the compare it to the SCU firmware version
module has failed. as listed on the NCU. If they are
different, update the SCU firmware, as
described in “Performing Other Software
Off Module admin state is 1 If the module is installed and provisioned,

disabled. check the administrative state settings.
2 If the module administrative state is set
to “Disabled,” change it to “In Service,”
“Management,” or “Maintenance.” For
information about the administrative
states, refer to the System Description,
"Management" chapter.
Off Module admin state is 1 If the management displays “UAS”

unassigned. (unassigned), check whether the module
is provisioned.
Green Module is provisioned, No action is required.

admin state is set to
“Maintenance,”
“Management,” or “In
Service.”
Cx Red Pluggable transceiver is Install the pluggable transceiver.

provisioned, but not
installed.
Laser failure If a replacement pluggable transceiver is

available, exchange the malfunctioning plug-
gable transceiver. Return the malfunctioning
pluggable transceiver to ADVA Optical Net-
working.
Yellow Loss of clock 1 Verify that the provisioned service type

2 Check optical power measurements.
this document.

Name
Cx Yellow Loss of signal • Verify that fiber cables are connected.

• Check optical power levels. Refer to the
procedure, “Finding Your Problem -
document.
Optical Input Power out of 1 Measure the optical input power on

range receiver connector.
2 Compare the measured value with the
pluggable transceiver module input
power specification.
3 Adjust the optical input power (i.e., install
the appropriate attenuators) to fulfill the
pluggable transceiver optical input power
requirements.
Loss of output power - Refer to “Finding Your Problem - Follow the

Power non-existing or Light” on p. 53 in this document.
below the defined minimum
level is detected at the
output.
(Normally a consequence of
loss of optical input power.
Also may be due to
failure/degeneration of an
internal component or
splice.)
Yellow flashing In a client channel card pro- Refer to “Finding Your Problem - Follow the
to off tection configuration, the Light” on p. 53 in this document.
protection path cor-
responding to this standby
port is unavailable.
Off flashing to The installed pluggable 1 Compare the supported data rates of the
red transceiver does not match module with the pluggable transceiver
the provisioned type. MEA- data rates.
ACCEPT condition is 2 Install the correct pluggable transceiver.
raised.
The installed pluggable Contact your Technical Services

transceiver is not approved Representative to obtain a pluggable
by ADVA Optical transceiver approved by ADVA Optical
Networking - no traffic. Networking.
MEA-APPROVE and MEA-
PHYS conditions are
raised.

Name
Cx Off No channel interface 1 Install an appropriate pluggable

(facility) provisioned on the transceiver module.
pluggable transceiver. 2 Provision the pluggable transceiver.
3 Enable the administrative state: If the
administrative state is set to “Disabled,”
change it to “In Service,” “Management,”
or “Maintenance.” For information about
administrative states, refer to the
System Description, "Management"
chapter.
4 Provision a channel interface (facility) on
5 Enable the client channel (facility)
administrative state.
Channel interface (facility) Change channel interface (facility) admin

admin state is disabled. state.
The installed pluggable Install the correct pluggable transceiver.

transceiver does not meet
one or more provisioned
physical layer properties,
such as data rate, reach, or
wavelength. MEA-PHYS
condition is raised.
Green flashing In a client channel card pro- No action is required.

to off tection configuration, this
standby port is operating
error-free. Therefore, the
interface is capable of tak-
ing over traffic.
Green Interface is active, with a No action is required.

valid signal, valid hardware,
and no alarms.
N Red Pluggable transceiver was Reinsert the pluggable transceiver.

(N2, N3, and inserted and the interface
N4 are Off) provisioned, but then the
removed.

Name
Nx Yellow Laser failure If a replacement module is available,

exchange the malfunctioning pluggable trans-
ceiver. Otherwise, return the malfunctioning
pluggable transceiver to ADVA Optical Net-
working.
Loss of clock 1 Verify that the provisioned service type

Refer to “Finding Your Problem - Follow
Loss of signal 1 Verify that fiber cables are connected.

Optical Input Power out of 1 Measure the optical input power on the
specification.
3 Adjust the optical input power (i.e., the
appropriate attenuators) to fulfill the
optical input power requirements.
Loss of frame - No 1 Verify that the provisioned service type

frame sync detected matches the incoming signal type.

level is detected at the out-
put. Normally a con-
sequence of loss of optical
input power. Also may be
due to failure/degeneration
of an internal component or
splice.
N2, N3, and Off The corresponding CFP has If the associated CFP has a single interface,
N4 (N not Off) a single connector (for no action is required. Please refer to the
example, LR10), is not explanation pertaining to network LEDs
installed, or is not approved. earlier in this section.

Name
Nx Off The CFP transceiver 1 Install an appropriate CFP transceiver

module has not been module.
provisioned or is not 2 Provision the CFP transceiver module.
installed.
3 Enable the CFP transceiver module
admin state: If the admin state is set to
“Disabled,” change it to “In Service,”
“Management,” or “Maintenance.” For
information about admin states, refer to
the System Description, “Management”
chapter.
4 Provision a channel interface on the
client facility.
5 Enable the client channel (facility) admin
state.
The network channel Change the client channel (facility) admin

(facility) admin state is state: If the admin state is set to “Disabled,”
disabled. change it to “In Service,” “Management,” or
“Maintenance.” For information about admin
states, refer to the System Description,
“Management” chapter.

transceiver does not meet
one or more provisioned
physical layer properties
wavelength. MEA-PHYS
N Off flashing to The installed pluggable Install the correct pluggable transceiver.
red transceiver does not match
the provisioned type. MEA-
ACCEPT condition is
raised.
The installed pluggable Contact your Technical Services Rep-

transceiver is not approved resentative to obtain a pluggable transceiver
by ADVA Optical approved by ADVA Optical Networking.
Networking - no traffic.
MEA-APPROVE and MEA-
PHYS conditions are
raised.
Nx Green Interface is active, with a No action is required.

valid signal, valid hardware,
and no alarms.
16TCC-PCN-4GUS+10G
This subsection provides LED troubleshooting guidelines for 16TCC-PCN-4GUS+10G modules.
within ADVA Optical Networking specifications and that you have verified that the application wavelength
matches the wavelength for the client SFP interface. If not, refer to “Finding Your Problem - Follow the Light” on
steps, you may destroy the module. As soon as the near-end and far-end 16TCC-PCN-
4GUS+10G modules are synchronized in a link, the network link is up and the network interface
CAUTION LED will be lit solid green.
the 16TCC-PCN-4GUS+10G module. For details on updating module firmware, refer to
Note on p. 628.
Note
affected interfaces may be disabled automatically. Only approved SFPs/XFPs will guarantee
CAUTION
the behavior in conjunction with the channel module as specified.
steps in Table 27 based upon the LED states.
The 16TCC-PCN-4GUS+10G features fourteen LEDs on the faceplate:
• “C1” through "C16” to indicate the client interface status, hereafter referred to as "Cx".
• "NW" and “NE” to indicate the network interface status
The module should lose power for at least 10 seconds to allow any capacitance to dissipate.
Note
Table 27: LED Status of the 16TCC-PCN-4GUS+10G

Name

module to ADVA Optical Networking
for repair.
Yellow Communication between protected 1 Check the Config tab on the port
channel modules associated with the protection and
has failed. verify that the module AIDs for the
protected modules are correct.
Yellow flashing Management communication is 1 Check the management for an

to off broken. SCU and channel module firmware
procedure. To update software,

settings.
“Maintenance”.
Off Module admin state is unassigned. • If the management displays

“unassigned”, check if the module
is provided to the management.

“Maintenance”, “Management” or “In
Service”

Name

unidirectional services, repeat Step
1 for the second service.
are met.
Yellow Tx Laser Failure Replace the malfunctioning pluggable

available.
Loss of clock 1 Verify that the provisioned service

type.
in this document.

Name
Cx Yellow Signal degrade The number of bit/block errors

troubleshooting instructions for the rel-
evant signal degrade condition outlined
in Alarm and Event List.
Loss of character sync Unable to synchronize on the

characters in the incoming data stream.
connected properly.
in this document.
service.

connected properly.
in this document.
service.
service.
are met.

Name
Cx Yellow Loss of input power - Power non- Refer to “Finding Your Problem - Follow
minimum level is detected at the If this port supports two active
input. unidirectional services, repeat this step
for the second service.
Yellow flashing In a client channel card protection Refer to the procedure in “Finding Your
to off configuration, the protection path cor- Problem - Follow the Light” on p. 53 in
responding to this standby port is this document.
unavailable. Either no power is detec-
ted at the input, or a power level
below the defined minimum value is
detected.

operating error-free. Hence the inter-
face is capable of taking over traffic.


transceiver.
4 Provision a Ch Interface (Facility)
Interface (Facility) admin state to
“In Service”.
Ch Interface (Facility) admin state is Change Ch Interface (Facility) admin

disabled. state.

Name
Cx Off flashing to Pluggable transceiver mismatch – 1 Compare the supported data rates

approved by ADVA Optical resentative about obtaining a pluggable
Networking - no traffic. transceiver approved by ADVA Optical
Networking.

hardware, no alarms

available.
requirements.
Yellow Signal degrade The number of bit/block errors


connected.

Name
NW, NE Yellow Optical Input Power out of range. 1 Measure the optical input power on
requirements.

detected. prevent a module mismatch within a
link.
input.
connected.

to red approved by ADVA Optical rerepresentative about obtaining a
Networking, but transmits traffic. pluggable transceiver approved by

settings.
“Maintenance”.

Name
NW, NE Off Interface admin state is unassigned. Change Ch Interface (Facility) admin
state.
Off flashing to Pluggable transceiver mismatch – 1 Compare the supported data rates

approved by ADVA Optical Net- resentative about obtaining a pluggable
working - no traffic. transceiver approved by ADVA Optical
Networking.

hardware, no alarms
Troubleshooting Core Type WDM Channel Modules
Troubleshooting Core Type WDM Channel

Modules
This section will help you resolve issues that can be experienced on WDM core channel
Modules. One very important difference between the Single Application and WDM core
channel modules is that the Single Application modules require that an application signal
be present before it attempts to establish a network link. The WDM core channel
modules, however, will attempt to establish the network link immediately upon power on.
This leads to slight differences in what you could expect to see as normal LED states.
The LEDs are located on the faceplate of every WDM core channel module.
The following subsections identify and resolve issues of:
“2TWCC-PCN-2G7U ” on p. 166
“2WCC-PCN-10G” on p. 173
“4WCC-PCN-10G” on p. 180
“WCC-PC1N-2G7U” on p. 187
“WCC-PCTN-10G” on p. 194
“WCC-PCTN-100G(A,B)” on p. 202
“WCC-PCN-100G” on p. 210
“WCC-TN-40G-L#DC” on p. 220
“10WXC-PCN-10G” on p. 226
2TWCC-PCN-2G7U
This subsection will help you resolve issues that can be experienced on the 2TWCC-PCN-2G7U module.
It assumes that all measurements for the client and network interface are within ADVA Optical Networking
specifications and that you have verified that the application wavelength is the same as the wavelength for the
client interface. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this document.
2TWCC-PCN-2G7U module in a link are synchronized the network link is up and the network
the 2TWCC-PCN-2G7U module. For details on updating module firmware, refer to “Updating the
NE Software Release” on p. 617 and “Performing Other Software Update Actions” on p. 628.
Note
Note
and Tx of the affected interfaces may be disabled automatically. Only approved pluggable
CAUTION
Note
The 2TWCC-PCN-2G7U has six LEDs on the faceplate:
• “C1” and “C2” to indicate the status of the client port 1 and client port 2
• “NW” and “NE” to indicate the status of the network port west and network port east
Note
Table 28: LED Status of the 2TWCC-PCN-2G7U

Name
Green Power is ok. No action is required.
Mod Red Critical or major equipment alarms Use the management system to view
are raised on the module. the equipment alarm(s) raised on this
module.
(s).
Yellow Communication between protected Check the Config tab on the port
Off Module admin state is disabled. 1 If module is installed and

settings.
2 If the management system displays
“Maintenance”.
Module admin state is unassigned. 1 If the management system displays

provisioned.
Green Module is enabled, no alarms are No action is required.

raised.

Name
C1 and Red Pluggable transceiver was inserted Reinsert the pluggable transceiver.
C2 and interface provisioned, then the
removed.

available.
specification.
requirements.

type.


connected.

Name
C1 and Yellow Loss of signal 1 Verify that fiber cables are

C2 connected.
requirements.

type.

affected interface.
minimum level is detected at the .
input.

Yellow flashing In a client channel card protection

to off configuration, the protection path
corresponding to this standby port
is unavailable.

Name
C1 and Off No Ch Port (Facility) provisioned 1 Install an appropriate pluggable

C2 on that pluggable transceiver. transceiver.
2 Provision the pluggable transceiver.
Service”.

is disabled. state.


traffic.
Green Interface is active, valid signal,

threshold exceeded. the receiver port and compare the
specification.
2 Install the appropriate attenuators to
requirements.

Name
NW, NE Yellow Loss of clock - Wrong bit rate or no 1 Verify that the provisioned service
clock detection. Either traffic with type matches the incoming signal
the wrong bit rate is applied or there type.
is a fault on the module. 2 Check optical power levels. Refer to


connected.

connected.
3 Install appropriate attenuators to
requirements.

detected, possibly due to type matches the incoming signal
connection of a cable carrying the type.
wrong traffic type. 2 Check optical power levels. Refer to

Name
NW, NE Yellow Loss of input power - The power Refer to “Finding Your Problem - Follow
level detected at the input is below the Light” on p. 53 in this document.
the defined minimum value.
Loss of output power - The power Refer to “Finding Your Problem - Follow
level detected at the output is the Light” on p. 53 in this document.
below the defined minimum value.
Normally a consequence of loss of
optical input power. Also may be
due to failure/degeneration of an
Yellow flashing In a channel protection There seems to be a problem with the

to off configuration, the protection path fiber connectivity of the protection path.
corresponding to this standby port Refer to “Finding Your Problem - Follow
is unavailable. the Light” on p. 53 in this document.
connected.
Green flashing In a channel protection No action is required.

traffic


Name
NW, NE Off No Ch Port (Facility) provisioned 1 Install an appropriate pluggable

on that pluggable transceiver. transceiver.
Service”.

is disabled. state.

2WCC-PCN-10G
This subsection will help you resolve issues that can be experienced on the 2WCC-PCN-10G module.
It assumes that all measurements for the C/R, C/T, N/R and N/T interfaces are within ADVA Optical Networking
FSP 3000R7 module client interfaces. If not, please refer to “Finding Your Problem - Follow the Light” on p. 53 in
this document.
steps, you could destroy the module being tested.
CAUTION
Before you start with the troubleshooting, ensure that the current software package is installed
on the 2WCC-PCN-10G module. For details on updating module firmware, refer to “Updating the
Note
Note
CAUTION
Note
The 2WCC-PCN-10G has six LEDs on the faceplate:
• “C1” and “C2” to indicate the status of the client port 1 and client port 2
• “NW” and “NE” to indicate the status of the network port west and network port east
Note
Table 29: LED Status of the 2WCC-PCN-10G

Name
Mod Red Equipment fault(s) Use the management system to view

the equipment alarm(s) raised on this
module.
(s).
.
Yellow Communication between channel Check the Config tab on the port
modules using client channel card associated with the protection and verify
protection has failed. that the module AIDs for the protected

Name
firmware. To update firmware, refer
to “Performing Other Software
Update Actions” on p. 628 for more
information.
Off Module admin state is disabled. 1 In the case that the module is
installed and provisioned, check the
admin state settings.
“Maintenance”.

provisioned.

“In Service”
C1 and Red Pluggable transceiver was inserted Reinsert the pluggable transceiver.
C2 and the interface provisioned, then
the pluggable transceiver was
removed.
Tx Laser Failure If a replacement module is available

exchange the malfunctioning pluggable
transceiver. Otherwise return the
malfunctioning pluggable transceiver to
ADVA Optical Networking for repair.

Name
C1 and Red Pin max too high, receiver damage 1 Measure the optical input power on
C2 threshold exceeded. the receiver connector and compare
specification.
requirements.

type.


connected.

connected.

Name
C1 and Yellow Optical Input Power out of range 1 Measure the optical input power on
C2 the receiver connector.
requirements.

type.
to off client channel card protection and signal quality of the protection path.
Off No Ch Port (Facility) provisioned 1 Install an appropriate pluggable

Service”.

is disabled. state.

Name
C1 and Off flashing to Pluggable transceiver is not Consult your ADVA Optical Networking
C2 red approved by ADVA Optical Representative about obtaining a

Green flashing Module is acting as standby in

to off client channel card protection and
specification.
requirements.

type.


connected.

Name

connected.
requirements.

type.

Service”.

is disabled. state.

Name
NW, NE Off flashing to Pluggable transceiver is not Consult your ADVA Optical Networking
red approved by ADVA Optical representative about obtaining a

4WCC-PCN-10G
This section provides troubleshooting guidelines for 4WCC-PCN-10G modules.
It assumes that all measurements for the C/R, C/T, N/R, and N/T interfaces are within ADVA Optical
Networking specifications and that you have verified that the application wavelength matches the wavelength for
the FSP 3000R7 module client interfaces. If not, please refer to “Finding Your Problem - Follow the Light” on p. 53
in this document.
CAUTION
Before you start with the troubleshooting, ensure that the current software package is installed
on the 4WCC-PCN-10G module. For details on updating module firmware, refer to “Updating the
Note
configured to “Maintenance.”
Note
ADVA Optical Networking may not function properly. Depending on the channel module type,
Rx and Tx of the affected interfaces may be disabled automatically. Only approved pluggable
CAUTION
Note
troubleshooting steps in Table 30 based upon the LED states.
The 4WCC-PCN-10G has ten LEDs on the faceplate:
• “C1”, "C2", "C3", and “C4” to indicate the status of the client ports
• “N1”, "N2", "N3", and “N4” to indicate the status of the network ports
When a module is removed, it should not be reinserted for at least 10 seconds, to allow all power
Note

Name
P Yellow Voltage out of range (Power to the module to ADVA Optical Networking for
module is abnormal). repair.
Off Power failure
Mod Red Equipment fault(s) Use the management system to view

the equipment alarm(s) raised on this
module.
(s).
Yellow Communication between channel Use your management system to check

modules using client channel card the port associated with the protection,
protection has failed. and verify that the module AIDs for the
protected modules are correct.
firmware. To update the firmware,
Update Actions” on p. 628 for more
information.

settings.
2 If the admin state is “disabled,”
change the admin state to “In
Service,” “Management” or
“Maintenance.”

Name
Mod Off Module admin state is unassigned. 1 If the admin state is “unassigned,”
verify that the module is
provisioned.

“Maintenance,” “Management,” or
“In Service.”
C1, C2, Red Pluggable transceiver was Reinsert the pluggable transceiver.
C3, C4 inserted, and the interface
provisioned. Then the pluggable
transceiver was removed.
Tx Laser Failure If a replacement module is available,

transceiver. Otherwise, return the
threshold exceeded. the receiver connector, and compare
specification.
2 Adjust the optical input power by
adding the appropriate attenuation,
requirements.

type.
Loss of multiframe 1 Verify that the fiber cables are

connected properly.
2 Check the optical power levels.
Refer to “Finding Your Problem -
document.

Name
C1, C2, Yellow OPU payload mismatch 1 Verify that the fiber cables are
C3, C4 connected properly.
2 Ensure that the channel modules at
either end of the optical path are of
the same type.
3 Use your management system to
verify that the facilities are
provisioned correctly.

outlined in the Alarm and Event List.

1 Verify that the fiber cables are
connected properly.
Loss of signal 1 Verify that the fiber cables are

connected properly.
the receiver connector, and compare
specification.
requirements.

type.

Name
C1, C2, Yellow flashing The port is acting as standby in There seems to be a problem with the
C3, C4 to off client channel card protection, and signal quality of the protection path.
the protection path is not available. Refer to “Finding Your Problem - Follow

3 Enable the admin state: Provision
state to “In Service.”
admin state: Provision the Ch
Service.”

is disabled. state.
Off flashing to Pluggable transceiver mismatch: 1 Compare the supported data rates of

Networking: no traffic. pluggable transceiver approved by

Green flashing The port is acting as standby in

to off client channel card protection, and
the protection path is available.

Name
N1, N2, Red Pin max too high, receiver damage 1 Measure the optical input power on
N3, N4 threshold exceeded. the receiver port, and compare the
specification.
requirements.

type.
document.
Loss of multiframe 1 Verify that the fiber cables are

connected properly.
document.
OPU payload mismatch 1 Verify that the fiber cables are

connected properly.
2 Ensure that the channel modules at
both ends of the optical path are of
the same type.
3 Use your management system to
verify that the facilities are

the provisioned threshold. To identify the
relevant signal degrade condition in the
Alarm and Event List.

Name
N1, N2, Yellow Loss of character sync Unable to synchronize on the characters
N3, N4 in the incoming data stream.
1 Verify that the fiber cables are
connected properly.
Loss of signal 1 Verify that the fiber cables are

connected properly.
the receiver port and compare the
specification.
requirements.

type.

3 Enable the admin state: Configure
state to “In Service.”
Service.”

Name
N1, N2, Off Ch Interface (Facility) admin state Change Ch Interface (Facility) admin
N3, N4 is disabled. state.
Off flashing to Pluggable transceiver mismatch: 6 Install the correct pluggable

red None of the data rates supported transceiver.
by the installed pluggable
transceiver match the data rates
supported by the channel module.

Networking: no traffic pluggable transceiver approved by

WCC-PC1N-2G7U
This subsection will help you resolve issues that can be experienced on WCC-PC1N-2G7U modules.
It assumes that all measurements for the client and network interface are within ADVA Optical Networking
client interface. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this document.
WCC-PC1N-2G7U module in a link are synchronized the network link is up and the network
the WCC-PC1N-2G7U module. For details on updating module firmware, refer to “Updating the
Note
Note
The use of pluggable transceivers other than those approved by ADVA Optical Networking result
in loss of safety approval for the FSP 3000R7. Pluggable transceivers not approved by ADVA
Optical Networking will not function properly. Depending on the channel module type, Rx and Tx
of the affected interfaces may be disabled automatically. Only approved pluggable transceivers
CAUTION
will guarantee the behavior in conjunction with the channel module as specified.
Note
The WCC-PC1N-2G7U has four LEDs on the faceplate:
• “C” and “N” to indicate the interface status
When a module is removed, it should lose power for at least 10 seconds to allow any and all
Note
Table 31: LED Status of the WCC-PC1N-2G7U

Name

Name
Mod Off Module admin state is disabled. 1 In case the module is installed and
settings.
“Maintenance”.

provisioned.

“In Service”
C Red Pluggable transceiver was inserted Reinsert the pluggable transceiver.

removed.
specification.
requirements.

type.
document.


Name
C Yellow Loss of character sync Unable to synchronize on the characters

connected.

connected.
requirements.

type.
document.
input.


Name
C Off No Ch Port (Facility) provisioned 1 Install an appropriate pluggable

Service”.

is disabled. state.


specification.
requirements.

Name

type.
document.


connected.

connected.
requirements.

Name
type.
document.
input.


configuration (i.e. interface not NW”. Data is transmitted via the active
capable of taking over traffic) line. The backup line is not available.
p. 53.
Module is acting as standby in There seems to be a problem with the

channel card protection and fiber connectivity of the protection path.
connected.


Name
N Off No Ch Port (Facility) provisioned 1 Install an appropriate pluggable

Service”.

is disabled. state.


WCC-PCTN-10G
This subsection will help you resolve issues that can be experienced on the WCC-PCTN-10G.
FSP 3000R7 module‘s client interfaces. If not, please refer to “Finding Your Problem - Follow the Light” on p. 53 in
this document.
CAUTION
Before you start with the troubleshooting, ensure that the current firmware package is installed
on the WCC-PCTN-10G module. For details on updating module firmware, refer to “Updating the
Note
Note
CAUTION
Note
The WCC-PCTN-10G has four LEDs on the faceplate:
Note
Table 32: LED Status of the WCC-PCTN-10G

Name
Green Power is OK.

Name
installed and provisioned check the
“Maintenance”.

provisioned.
Green Module is enabled; no alarms No action is required.
C Red Pluggable transceiver was inserted Reinsert the pluggable transceiver.

removed.
Yellow Pin max too high, receiver damage 1 Measure the optical input power on
specification.
requirements.

Name
C Yellow Loss of clock 1 Verify that the provisioned service

type.
document.


connected.

connected.
requirements.

Name
C Yellow Loss of frame - No frame sync 1 Verify that the provisioned service
type.
document.

affected interface.
input.


Service”.

is disabled. state.

Name
C Off flashing to Pluggable transceiver mismatch - 1 Compare the supported data rates of
red Features of the installed pluggable the board with the pluggable
transceivers do not match to the transceiver data rates.
channel module. 2 Install the correct pluggable
transceiver.


specification.
requirements.

type.
document.


connected.

Name
N Yellow Optical Input Power out of range 1 Measure the optical input power on
requirements.

type.
document.
input.

affected interface.

configuration (i.e. interface not NW”. Data is retransmitted via the
capable of taking over traffic) active line. The backup line is not
available. Check the cabling. Refer to
on p. 53.

Name
N Yellow off for ALS pulse received. Network link is not coming up.
connected.
Green flashing Interface in a protection group and No action is required.

to off running error free (i.e. interface is
capable of taking over traffic)

Service”.

is disabled. state.


WCC-PCTN-100G(A,B)
This subsection provides LED troubleshooting guidelines for WCC-PCTN-100GA and WCC-PCTN-100GB
modules.
this document.
CAUTION
on the WCC-PCTN-100GA/WCC-PCTN-100GB module. For details on updating module
firmware, refer to “Updating the NE Software Release” on p. 617 and “Performing Other Software
Note Update Actions” on p. 628.
Note
CAUTION
Note
The WCC-PCTN-100GA/WCC-PCTN-100GB has four LEDs on the faceplate:
Note
Table 33: LED Status of the WCC-PCTN-100GA/WCC-PCTN-100GB

Name
All LEDs Red A serious error in card initialization Remove and insert the module. If the
has occurred. condition continues, return the module to
Off Power failure.
module.
(s).

settings.
2 If the module admin state is set to
information when to use these
admin states and what they mean,
refer to the System Description,

“UAS” (unassigned), check if the
module is provisioned.

Name
Mod Off and P The module may be 1 Initiate a warm restart of the WCC-
LED is green unresponsive1. This occurs if the PCTN-100GB module, as described
module was reseated during a in “Restarting Modules” on p. 595.
small window of a boot cycle. 2 If the Mod LED remains off, perform
a cold restart of the module, as
described in “Restarting Modules”
on p. 595.
Green Module is enabled; no alarms. No action is required.
C Red CFP pluggable module was Reinsert the CFP pluggable module.
inserted and interface provisioned,
then the CFP module was
removed.

available.
the measured value with the CFP
input power specification.
fulfill the CFP Optical Input Power
requirements.

type.
document.
1WCC-PCTN-100GB modules only.

Name
C Yellow Signal degrade The number of bit/block errors exceeded


connected.

connected.
the CFP input power specification.
requirements.

type.
document.

affected interface.

Name
C Yellow Loss of input power - Power non- Refer to “Finding Your Problem - Follow
input.

Yellow flashing Channel runs in protection group

to off1 “standby” mode and experiences
loss of input power - Power non-
existing or below the defined min-
imum level detected at the input.
Off The CFP module has not been 1 Install an appropriate CFP pluggable
provisioned or is not installed. module.
2 Provision the CFP module.
3 Enable the CFP module admin
state: If the admin state is set to
refer to the System
Description,“Management” chapter.
client facility.
”Change the client channel (facility)
admin state”.

Name
C Off The client channel (facility) admin Change the client channel (facility)
state is disabled. admin state: If the admin state is set to
chapter.
Off flashing to CFP pluggable module mismatch 1 Compare the supported data rates of
red (MEA-ACCEPT): Features of the the WCC-PCTN-100GA with the
installed CFP module do not match CFP pluggable module data rates.
with the channel module. 2 Install the correct CFP pluggable
module.
Installed CFP module is not Consult your technical services

approved by ADVA Optical representative about obtaining a CFP
Networking (MEA-APPROVE) - no pluggable module approved by ADVA
traffic. Optical Networking.
Green flashing Port in a protection group and run- No action is required.

to off1 ning error-free (i.e. interface is cap-
able of taking over traffic).


available.
requirements.

this document.

Name
N Yellow Signal degrade The number of bit/block errors exceeded

Event List.

connected.
Loss of lane 1 Inspect the physical cable

required.
limitations.
requirements.
associated module.
far-end module.

Name
N Yellow Auto shutdown (Temp) 1 Verify that the equipment operating

unobstructed.
module.
specification.
requirements.

this document.
input.


affected interface.

Name
N Off The network channel (facility) has 1 Provision the network channel

chapter.

WCC-PCN-100G
This subsection provides LED troubleshooting guidelines for WCC-PCN-100G modules.
this document.
CAUTION
on the WCC-PCN-100G module. For details on updating module firmware, refer to “Updating the
Note
Note
CAUTION
Note
The WCC-PCN-100G has four LEDs on the faceplate:
Note
Table 34: LED Status of the WCC-PCN-100G

Name
All LEDs Red A serious error in card initialization Remove and insert the module. If the
has occurred. condition continues, return the module to
Off Power failure.
module.
(s).

Name
Mod Off Module admin state is disabled. 1 If the module is installed and
settings.

“UAS” (unassigned), check if the
Off and P The module may be unresponsive. 1 Initiate a warm restart of the module,
LED is green This occurs if the module was as described in “Restarting
reseated during a small window of Modules” on p. 595.
a boot cycle. 2 If the Mod LED remains off, perform
a cold restart of the module, as
described in “Restarting Modules”
on p. 595.
Green Module is enabled; no alarms. No action is required.
C Red CFP pluggable module was Reinsert the CFP pluggable module.
inserted and interface provisioned,
removed.

available.
the measured value with the CFP
input power specification.
requirements.

Name
C Yellow Loss of clock 1 Verify that the provisioned service

type.
document.


connected.

connected.
the CFP input power specification.
requirements.

Name
C Yellow Loss of frame - No frame sync 1 Verify that the provisioned service
type.
document.

affected interface.
input.

Yellow flashing Channel runs in protection group

to off “standby” mode and experiences
loss of input power - Power non-
existing or below the defined min-
imum level detected at the input.

Name
C Off The CFP module has not been 1 Install an appropriate CFP pluggable
provisioned or is not installed. module.
refer to the System
client facility.
admin state”.
The client channel (facility) admin Change the client channel (facility)
chapter.
red (MEA-ACCEPT): Features of the the WCC-PCTN-100GA with the
installed CFP module do not match CFP pluggable module data rates.
module.

approved by ADVA Optical representative about obtaining a CFP
Networking (MEA-APPROVE) - no pluggable module approved by ADVA
Green flashing Port in a protection group and run- No action is required.

to off ning error-free (i.e. interface is cap-
able of taking over traffic).


Name

available.
CFP pluggable module was inser- Re-insert the CFP pluggable module.
ted and the interface provisioned,
removed.
requirements.

this document.

Event List.

connected.

Name
N Yellow Loss of lane 1 Inspect the physical cable

required.
limitations.
requirements.
associated module.
far-end module.
Auto shutdown (Temp) 1 Verify that the equipment operating

unobstructed.
module.

Name
N Yellow Optical Input Power out of range 1 Measure the optical input power on
specification.
requirements.

this document.
input.

affected interface.

Name
N Off The CFP module has not been pro- 1 Install the appropriate CFP
visioned or is not installed. pluggable module.
refer to the System
client facility.
admin state”.
The network channel (facility) has 1 Provision the network channel


chapter.
red (MEA-ACCEPT): Features of the the module with the CFP pluggable
installed CFP module do not match module data rates.
module.

approved by ADVA Optical representative about obtaining the
Networking (MEA-APPROVE) - no correct CFP pluggable module.
traffic.

WCC-TN-40G-L#DC
This subsection will help you resolve issues that can be experienced on the WCC-TN-40G-L#DC module.
FSP 3000R7 module‘s client interfaces. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this
document.
CAUTION
the WCC-TN-40G-L#DC module. For details on updating module firmware, refer to “Updating the
Note
Note
Note
The WCC-TN-40G-L#DC has four LEDs on the faceplate:
The following table provides information about troubleshooting the WCC-TN-40G-L#DC.
Note
Table 35: LED Status of the WCC-TN-40G-L#DC

Name
All LEDs Red A serious error in card initialization. Remove and reinsert the module. If the
condition continues, return the module to
P Yellow Power is abnormal. ADVA Optical Networking for repair.
Off Power failure

Name
P Green Power is OK. No action required.
provisioned check the admin state
settings.
“Maintenance”.

provisioned.
Green Module is enabled; no alarms No action required.
C Red Pin max too high, receiver damage 1 Measure the optical input power on
specification.
requirements.

type.
document.

Name
C Yellow Signal degrade The number of bit/block errors exceeded


connected.

connected.
requirements.

type.
document.

affected interface.

Name
C Yellow Loss of input power - Power non- Refer to “Finding Your Problem - Follow
input.

Off No Ch Interface (Facility) 1 Provision the client port.

provisioned on that pluggable 2 Enable the admin state - Configure
transceiver. the client port admin state to “In
Service”.
the client port.
Service”.

is disabled. state.
Green Interface is active, valid signal, No action required.

N Red Pin max too high, APD damage 1 Measure the optical input power on
specification.
requirements.

Name

type.
document.


connected.
the channel module specification.
requirements.

type.
document.

Name
N Yellow Loss of input power - Power non- Refer to “Finding Your Problem - Follow
input.


affected interface.
connected.
Green flashing Interface in a protection group and No action required.

to off running error free (i.e. interface is
capable of taking over traffic)
Off No Ch Interface (Facility) 1 Provision the network port.

transceiver. the network port admin state to “In
Service”.
the network port.
Service”.

is disabled. state.

10WXC-PCN-10G
This subsection provides LED troubleshooting guidelines for the 10WXC-PCN-10G module.
It assumes that all measurements for the client and network interfaces are within ADVA Optical Networking
FSP 3000R7 module‘s client interfaces. If not, please refer to “Finding Your Problem - Follow the Light” on p. 53 in
this document.
CAUTION
on the 10WXC-PCN-10G module. For details on updating module firmware, refer to “Updating
Note
Note
CAUTION
Note
The 10WXC-PCN-10G has 12 LEDs on the faceplate:
• “P1” to “P10” to indicate the status of each port
Note
Table 36: LED Status of the 10WXC-PCN-10G

Name
Green Power is OK. No action required.
provisioned check the admin state
settings.
“Maintenance”.

provisioned.
Green Module is enabled; no alarms No action required.
P1 to P10 Red Pin max too high, receiver damage 1 Measure the optical input power on
specification.
requirements.

Name
P1 to P10 Yellow Loss of clock 1 Verify that the provisioned service

type.
document.


connected.

connected.
requirements.

Name
P1 to P10 Yellow Loss of frame - No frame sync 1 Verify that the provisioned service
type.
document.

affected interface.
input.

Off No Ch Interface (Facility) 1 Provision the client port.

transceiver. the client port admin state to “In
Service”.
the client port.
Service”.

is disabled. state.

Chapter 5
Access Type Channel Modules

This chapter addresses all access type channel modules available at the publication date
of this manual.
This chapter provides these sections:
“Troubleshooting Access Type TDM Channel Modules” on p. 232, which addresses LED
indicators and troubleshooting guidelines for TDM access channel modules.
“Troubleshooting Access Type WDM Channel Modules” on p. 276, which addresses LED
indicators and troubleshooting guidelines for WDM access channel modules.

consequent actions (e.g. LKDO-OFF) are not indicated by these LEDs,
Note since they require troubleshooting the fault upstream (at another port of
the same module or a remote module).
Troubleshooting Access Type TDM Channel Modules
Troubleshooting Access Type TDM Channel

Modules
This section will help you resolve issues that can be experienced on TDM access
channel modules.
One very important difference between the Single Application and TDM access channel
modules is that the Single Application modules require that an application signal be
present before it attempts to establish a network link. The TDM access channel modules,
however, will attempt to establish the network link immediately upon power on. This
leads to slight differences in what you could expect to see as normal LED states. The
LEDs are located on the faceplate of every TDM access channel Module.
“2PCA-PCN-10G” on p. 233
“2TCA-PCN-1G3+2G5” on p. 239
“2TCA-PCN-622M+2G5” on p. 246
“4TCA-LS+1G3-V” on p. 252
“4TCA-PCN-4GU(S)+4G” on p. 257
“8TCA-PC-2G1U+10G-V” on p. 264
“10PCA-PCN-1G3+10G” on p. 270
2PCA-PCN-10G
This subsection will help you resolve issues that can be experienced on 2PCA-PCN-10G modules.
It assumes that all measurements for the Cx, N East, and N West interfaces are within ADVA Optical
Networking specifications and that you have verified that the application wavelength is the same as the
wavelength for the FSP 3000R7 module’s client interface. If not, refer to “Finding Your Problem - Follow the Light”
on p. 53.
2PCA-PCN-10G modules in a link are synchronized, the network link is up. The network
CAUTION
mode: Multiplexer NE Only, Multiplexer NW Only, Multiplexer NE & NW or Regenerator 1-Way.
the 2PCA-PCN-10G module. For details on updating module firmware, refer to “Updating the NE
Software Release” on p. 617 and “Performing Other Software Update Actions” on p. 628.
Note
Note
CAUTION
Note
The 2PCA-PCN-10G has 6 LEDs on the faceplate:

• “Mod” to indicate the looping back on the client or network interfaces
• “C1”, “C2”, “NW” and “NE” to indicate the interface status.
Note
Table 37: LED Status of the 2PCA-PCN-10G

Name
All LEDs Red A serious error in card ini- Remove and reinsert the module.
tialization. If the condition continues, return the module to
Off Power failure
Mod Yellow blinking Management 1 Check the SCU firmware version and
to off communication to the compare it to the SCU firmware version as
module has failed. listed on the NCU. If they are different,
update the SCU firmware as described in
If the LED is still blinking yellow to off, contact
your ADVA Optical Networking Technical
Services Representative.
Off Module admin state is 1 In the case that the module is installed and
disabled. provisioned, check the admin state
settings.
2 If the management displays “disabled”,
change the admin state to “In Service”,
“Management” or “Maintenance”.
Module admin state is 1 If the management displays “unassigned”,

unassigned. check if the module is provisioned.
Green Module provisioned, admin No action is required.

state is “Maintenance”,
“Management” or “In
Service”
Cx Red Pluggable transceiver was Reinsert the pluggable transceiver.

inserted and interface
provisioned, then the
removed.

Name
Cx Red Pin max too high, receiver 1 Measure the optical input power on the
damage threshold receiver connector and compare the
exceeded measured value with the channel
specification.
Optical Input Power requirements.
Yellow Loss of character sync Unable to synchronize on the characters in the

incoming data stream.
1 Verify that fiber cables are connected.

pluggable transceiver specification.
Loss of frame - No frame 1 Verify that the provisioned service type

sync detected matches the incoming signal type.
Loss of input power - Refer to “Finding Your Problem - Follow the

input.

Name
Cx Yellow Loss of output power - Refer to “Finding Your Problem - Follow the
output. Normally a
consequence of loss of
optical input power. Also
may be due to
splice.
Off flashing to Pluggable transceiver 1 Compare the supported data rates of the
red mismatch – None of the board with the pluggable transceiver data
data rates supported by the rates.
installed pluggable 2 Install the correct pluggable transceiver.
transceiver match the data
rates supported by the
channel module.
Pluggable transceiver is Consult your ADVA Optical Networking

not approved by ADVA Representative about obtaining a pluggable
Optical Networking - no transceiver approved by ADVA Optical
traffic Networking.

provisioned on that transceiver.
3 Enable the admin state - Configure the
Service”.
4 Provision a Ch Interface (Facility) on the
5 Enable the Ch Interface (Facility) admin
Ch Interface (Facility) Change Ch Interface (Facility) admin state.

admin state is disabled.
Green Interface is active, valid No action is required.

signal, valid hardware, no
alarms

Name
NW, NE Red Pluggable transceiver was Reinsert the pluggable transceiver.

removed.
Pin max too high, receiver 1 Measure the optical input power on the
specification.
Yellow, Loss of character sync Unable to synchronize on the characters in the

Yellow flashing incoming data stream.
to off 1 Verify that fiber cables are connected.

specification.


Name
NW, NE Off flashing to Pluggable transceiver 1 Compare the supported data rates of the
channel module.

traffic Networking.

Service”.


alarms
2TCA-PCN-1G3+2G5
This subsection will help you resolve issues that can be experienced on 2TCA-PCN-1G3+2G5 modules. It
assumes that all measurements for the C1/R, C1/T, C2/R, C2/T, N/R West, N/R East and N/T West, N/T East
interfaces are within ADVA Optical Networking specifications and that you have verified that the application
Your Problem - Follow the Light” on p. 53.
2TCA-PCN-1G3+2G5 modules in a link are synchronized, the network link is up. The network
interface LEDs light up solid green or green blinking depending on the configured transmission
CAUTION
ode: Multiplexer NE Only, Multiplexer NW Only, or Multiplexer NE & NW.
the 2TCA-PCN-1G3+2G5 module. For details on updating module firmware, refer to “Updating
Note
Note
The near-end and far-end modules must be provisioned to the same transmission mode to
guarantee proper operation.
Note
Note
CAUTION
Note
The 2TCA-PCN-1G3+2G5 has six LEDs on the faceplate:

• “C1”, “C2”, “NW” and “NE” to indicate the interface status
This module has 2 client interfaces (C1 and C2). The LED states Table 38 refer to one client interface (Cx) as an
example for all client interfaces on the module.
Note
Table 38: LED Status of the 2TCA-PCN-1G3+2G5

Name
condition continues, return the module to
P Yellow Power is abnormal. ADVA Optical Networking for repair.
Off Power failure
“Maintenance”.

Name
Mod Off Module admin state is unassigned. 1 If the management displays

provisioned.

“In Service”.

removed.
threshold exceeded the receiver connector and compare
specification.
requirements.

type.


connected.

Name

connected.
the pluggable transceiver
specification.
requirements.

type.
input.



Name

the pluggable transceiver Plug
Service”.
Yellow Ch Interface (Facility) admin state Change Ch Interface (Facility) admin

is disabled. state.

removed.
threshold exceeded the receiver connector and compare
specification.
requirements.

type.

Name
NW, NE Yellow Signal degrade The number of bit/block errors exceeded


connected.

connected.
requirements.

type.
Yellow flashing Interface in a protection group, but Channel module is configured to

to off showing errors (i.e. interface not Transmission Mode “Multiplexer NE &
capable of taking over traffic). NW”. Data are transmitted via active
line. The backup line is not available.
Your Problem - Follow the Light” on p. 53
in this document.

Name
connected.
Chapter 5: Finding Your Problem -
Follow the Light in this document.
Green flashing Interface in a protection group and Nothing - Channel module is working in
to off running error free (i.e. interface is the Transmission Mode “Multiplexer NE
capable of taking over traffic). & NW”.


Service”.

is disabled. state.

2TCA-PCN-622M+2G5
This subsection will help you resolve issues that can be experienced on 2TCA-PCN-622M+2G5 modules. It
assumes that all measurements for the C1/R, C1/T, C2/R, C2/T, N/R West, N/R East and N/T West, N/T East
interfaces are within ADVA Optical Networking specifications and that you have verified that the application
Your Problem - Follow the Light” on p. 53.
2TCA-PCN-622M+2G5 module in a link are synchronized the network link is up. The network
interface LEDs light up solid green or green blinking depending on the configured transmission
CAUTION
mode: Multiplexer NE Only, Multiplexer NW Only, or Multiplexer NE & NW.
the 2TCA-PCN-622M+2G5 module. For details on updating module firmware, refer to “Updating
Note
Note
Note
CAUTION
Note
The 2TCA-PCN-622M+2G5 has six LEDs on the faceplate:
This module has 2 client interfaces (C1 and C2). The LED states in Table 39 on p. 247 will refer to one client
Note
Table 39: LED Status of the 2TCA-PCN-622M+2G5

Name
Off Power failure
Mod Yellow Communication between Check the Config tab on the port associated with
protected channel modules the protection and verify that the module AIDs for
has failed. the protected modules are correct.
Yellow Management 1 Check the SCU firmware version and

blinking to off communication to the compare it to the SCU firmware version as
“Performing Other Software Update Actions”
on p. 628.
disabled. provisioned, check the admin state settings.


Service”

removed.

Name
module/pluggable transceiver specification.
2 Adjust the optical input power (i.e., install the
appropriate attenuators) to fulfill the Optical
Input Power requirements.
Yellow Signal degrade The number of bit/block errors exceeded the

configured threshold. To identify the failure
location, refer to the troubleshooting instructions
for the relevant signal degrade condition outlined
Loss of character sync Unable to synchronize on the characters in the

2 Check optical power levels. Refer to “Finding
Your Problem - Follow the Light” on p. 53 in
this document.

this document.

2 Check optical power measurements. Refer
to “Finding Your Problem - Follow the Light”

Name
Cx Yellow Loss of input power - Power Refer to “Finding Your Problem - Follow the Light”
non-existing or below the on p. 53 in this document.
defined minimum level is
detected at the input.
Loss of output power -

Power non-existing or
output. Normally a
may be due to failure or
degeneration of an internal
component or splice.
channel module.

approved by ADVA Optical Representative about obtaining a pluggable
Networking - no traffic transceiver approved by ADVA Optical
Networking.
Off No Ch Interface (Facility) 1 Install an appropriate pluggable transceiver.

provisioned on that 2 Provision the pluggable transceiver.
3 Enable the admin state. Configure the
Service”.
state. Configure the Ch Interface (Facility)


alarms

Name

removed.
Yellow Signal degrade The number of bit/block errors exceeded the


this document.

this document.
specification.


Name
NW, NE Yellow Interface is in a protection Channel module is configured to transmission

flashing to off group, but showing errors mode “Multiplexer NE & NW”. Data is
(i.e. interface not capable of transmitted via the active line. The backup line is
taking over traffic) not available. Check the cabling, refer to “Finding
Your Problem - Follow the Light” on p. 53 in this
document.
500 ms 1 Verify that fiber cables are connected.
this document.
Green flashing Interface is in a protection Nothing - Channel module is working in the

to off group and running error free transmission mode “Multiplexer NE & NW”.
(i.e. interface is capable of
taking over traffic)
channel module.

approved by ADVA Optical Representative about obtaining a pluggable
Networking - no traffic transceiver approved by ADVA Optical
Networking.
Off No Ch Interface (Facility) 1 Install an appropriate pluggable transceiver.

provisioned on that 2 Provision the pluggable transceiver.
Service”.
state - Configure the Ch Interface (Facility)


alarms
4TCA-LS+1G3-V
This subsection will help you resolve issues that can be experienced on the 4TCA-LS+1G3-V module. This module is available in different variants that are described in the
Hardware Description.
It assumes that all measurements for the C1/R, C1/T, C2/R, C2/T, C3/R, C3/T, C4/R, C4/T, N/R and N/T interfaces are within ADVA Optical Networking specifications
and that you have verified that the application wavelength is the same as the wavelength for the FSP 3000R7 module’s client interface. If not, refer to “Finding Your
Problem - Follow the Light” on p. 53 in this document.
Follow all the instructions precisely. If you do not supply the specified attenuation on given steps, you could destroy the module being tested. As soon as
the near-end and the far-end 4TCA-LS+1G3-V module in a link are synchronized the network link is up. The network interface LEDs light up solid green or
green blinking depending on the configured transmission mode: Multiplexer NE Only, Multiplexer NW Only, Multiplexer NE & NW or Regenerator 1-Way.
CAUTION
Before you start with troubleshooting, ensure that the current firmware package is installed on the 4TCA-LS+1G3-V module. For details on updating
module firmware, refer to “Updating the NE Software Release” on p. 617 and “Performing Other Software Update Actions” on p. 628.
Note
Before you start with troubleshooting, ensure that the admin status on the affected module is configured to “Maintenance”.
Note
If your module has an LED status that is not represented in Table 40 on p. 253, please contact your ADVA Optical Networking Technical Services
Representative.
Note
The steps in this subsection may need to be completed on both sides of the link. Please follow the troubleshooting steps in Table 40 on p. 253 based upon the states of the
LEDs.
The 4TCA-LS+1G3-V provides twelve LEDs on the faceplate:

• “On” to indicate the power supply status
• “Err” to indicate the operation status of the module
• “C1/T”, “C2/T”, “C3/T”, “C4/T”, “C1/R”, “C2/R”, C3/R”, C4/R”, N/T and “N/R” to indicate the interface status
This module has 4 client interfaces (C1 to C4). The LED status in Table 40 will refer to the transmit connector and receive connector of one client interface (Cx/T and Cx/R)
as an example for all client interfaces on the module.
Table 40: LED Status of the 4TCA-LS+1G3-V
LED-Status Potential Cause Solution for Troubleshooting
On Err Cx/R Cx/T N/R N/T
Red Off Off Off Off Off Module is broken. Return the module to ADVA Optical
Green Red blinking Off Off Off Off A temporary setting is If the condition continues once the module
enabled on the module. has lost and regained power or all loops and
Manually disable transmitters have been turned off, it should
setting or reset module be returned to ADVA Optical Networking for
in the frame. repair.
Please note, the module should lose power
for at least 10 seconds to allow any and all
Green Green Yellow Yellow Client loop is set. Disable the loop.
Green Off Green Off Green blinks Green Attempting If all power measurements are in
every 10 s unsuccessfully to specification on both sides of the link, then it
establish network link. is possible that the network receiver of one
of the modules is damaged. Loop N/T to N/R
with a 20 dB attenuated patch cable.
• If the N/R and Cx/R LEDs do not light up
once the attenuated patch cable has
been applied, then the module is
damaged and has to be returned to
• If N/R and Cx/T do light up, repeat the
test on the other side of the link.
• If both sides of the link light up with the
patch cable, but not when the network
link is connected, please contact your
ADVA Optical Networking Technical
Note – If you do not use a 20 dB attenuated
patch cable for the test above, you will
destroy the module being tested.
Green Off Yellow Off Green Green Data received from a Check the connected data rate.
client interface, but
incoming data rate does
not match to the
supported data rates of
the module.
Off Green Green Green The module detects an You have probably swapped your transmit
application signal only and receive connections to the application.
on the network side of Exchange Cx/T and Cx/R connectors on the
the link. interface in question.
Green Off Green Green Although the module Exchange Cx/T and Cx/R connectors on the
receives an application interface in question on the other side of the
signal coming from the link.
client side, it does not
detect one coming from
the network side.
Red blinking Green Green Green Green Network laser is forced Turn laser forced off.
on.
Off Green Off Green Green Client interface is Enable client interface.
blinking disabled. Data rate
matches the set clock
frequency.
Yellow Off Green Green Client interface is Enable client interface and set the clock.
does not matches the
set clock frequency.
4TCA-PCN-4GU(S)+4G
This subsection will help you resolve issues that can be experienced on a 4TCA-PCN-4GU+4G and 4TCA-PCN-
4GUS+4G module. It assumes that all measurements for the C1/R, C1/T, C2/R, C2/T, C3/R, C3/T, C4/R, C4/T,
N/R West, N/R East and N/T West, N/T East interfaces are within ADVA Optical Networking specifications and
that you have verified that the application wavelength is the same as the wavelength for the client pluggable
transceiver interface. If not, refer to “Finding Your Problem - Follow the Light” on p. 53.
Follow the instructions precisely. If you do not supply the specified attenuation on given steps,
you could destroy the module being tested. As soon as the near-end and far-end 4TCA-PCN-
4GU(S)+4G modules in a link are synchronized, the network link is up. The network interface
LEDs light up solid green or green blinking according to the configured transmission mode:
CAUTION
Multiplexer NE Only, Multiplexer NW Only, or Multiplexer NE & NW.
the 4TCA-PCN-4GU(S)+4G module. For details on updating module firmware, refer to “Updating
Note
Before you start with troubleshooting, ensure that the admin state on the affected module is
Note
Note
Note
CAUTION
Note
The 4TCA-PCN-4GU(S)+4G has eight LEDs on the faceplate:

• “C1”, “C2”, “C3”, “C4”, “NW” and “NE” to indicate the interface status
This module has 4 client interfaces (C1, C2, C3 and C4). The LED states Table 41 will refer to one client
Note
Table 41: LED Status of the 4TCA-PCN-4GU(S)+4G

Name
All LEDs Red A serious error in card Remove and reinsert the module.
initialization. If the condition continues, return the module to
Off Power failure
Mod Yellow Communication Check the Config tab on the port associated with
between protected the protection and verify that the module AIDs
channel modules has for the protected modules are correct.
failed.
Yellow blinking Management 1 Check the SCU firmware version and

to off communication to the compare it to the SCU firmware version as
“Performing Other Software Update Actions”
on p. 628.
Off Module admin state is 1 In case the module is installed and



Name
Mod Green Module provisioned, No action is required.

admin state is
“Maintenance”,
Service”
Cx Red Pluggable transceiver Reinsert the pluggable transceiver.

was inserted and
interface provisioned,
then the pluggable
transceiver was
removed.
Pin max too high, 1 Measure the optical input power on the
receiver damage receiver connector and compare the
threshold exceeded measured value with the channel

Signal degrade The number of bit/block errors exceeded the


“Finding Your Problem - Follow the Light” on


Name
Cx Yellow Optical Input Power out 1 Measure the optical input power on the
of range receiver connector.


below the defined
minimum level is
Loss of output power -

Power non-existing or
below the defined
minimum level is
detected at the output.
Normally a
optical input power.
Also may be due to
failure/degeneration of
an internal component
or splice.
data rates supported by rates.
the installed pluggable 2 Install the correct pluggable transceiver.
transceiver match the
data rates supported by
the channel module.
Pluggable transceiver Consult your ADVA Optical Networking

is not approved by Representative about obtaining a pluggable
ADVA Optical transceiver approved by ADVA Optical
Networking - no traffic Networking.

Name
Cx Off No Ch Interface 1 Install an appropriate pluggable transceiver.

(Facility) provisioned on 2 Provision the pluggable transceiver.
that pluggable
transceiver.
Service”.


signal, valid hardware,
no alarms
NW, NE Red Pin max too high, 1 Measure the optical input power on the
receiver damage receiver connector and compare the
threshold exceeded measured value with the channel




Name
NW, NE Yellow Loss of signal 1 Verify that fiber cables are connected.
Optical Input Power out 1 Measure the optical input power on the
of range receiver connector.
specification.


below the defined
minimum level is

below the defined
minimum level is
Normally a
optical input power.
Also may be due to
failure/degeneration of
an internal component
or splice.
Yellow flashing Module is acting as There is a problem with the fiber connectivity of
to off standby in channel card the protection path. Refer to “Finding Your
protection; protection Problem - Follow the Light” on p. 53 in this
path is not available document.

Name
500 ms ALS pulse detected. 1 Verify that fiber cables are connected.
Green flashing to Module is acting as Nothing - Channel module is working in the

off standby in channel card Transmission Mode “Multiplexer NE & NW”.
protection; protection
path is not available
data rates supported by rates.
the installed pluggable 2 Install the correct pluggable transceiver.
data rates supported by
the channel module.
Pluggable transceiver Consult your ADVA Optical Networking

is not approved by Representative about obtaining a pluggable
ADVA Optical transceiver approved by ADVA Optical
Networking - no traffic Networking.
Off No Ch Interface 1 Install an appropriate pluggable transceiver.

(Facility) provisioned on 2 Provision the pluggable transceiver.
that pluggable
transceiver.
Service”.


signal, valid hardware,
no alarms
8TCA-PC-2G1U+10G-V
This subsection will help you resolve issues that can be experienced on 8TCA-PC-2G1U+10G-V modules. It
assumes that all measurements for both C1 to C8 and the network interface are within ADVA Optical Networking
client pluggable transceiver interface. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this
document.
steps, you may destroy the module being tested. As soon as the near-end and the far-end 8TCA-
PC-2G1U+10G-V module in a link are synchronized the network link is up and the network
the 8TCA-PC-2G1U+10G-V module. For details on updating module firmware, refer to “Updating
Note
Note
Note
Restrictions
A clock sync. loss status is not signaled on the client and network interface LEDs.
Data Rates vs. Client Interface Groups and Client Interfaces
Not each supported data rate is configurable in each client pluggable transceiver slot. Client
interfaces in bold support 2125 Mbit/s only.
Note
The 8TCA-PC-2G1U+10G-V channel module supports following data rates:

• 1062 Mbit/s
• 1250 Mbit/s
• 2125 Mbit/s
The following table lists supported data rates.
Table 42: Supported Data Rates
Group 1 Group 2 Group 3 Group 4
Client Client Client Client Client Client Client Client

Interfac Interfac Interfac Interfac Interfac Interfac Interfac Interfac
e1 e2 e3 e4 e5 e6 e7 e8
- 1062 - 1062 - 1062 - 1062 - 1062 - 1062 - 1062 - 1062

Mbit/s Mbit/s Mbit/s Mbit/s Mbit/s Mbit/s Mbit/s Mbit/s
- 1250 - 1250 - 1250 - 1250 - 1250 - 1250 - 1250 - 1250
Mbit/s Mbit/s Mbit/s Mbit/s Mbit/s Mbit/s Mbit/s Mbit/s
- 2125 - 2125 - 2125 - 2125
Mbit/s Mbit/s Mbit/s Mbit/s
Mixtures of Data Rates

Mixtures of data rates in a group are not possible.
Table 43: Example of an Impossible Group Mixture
Group 1
Client Interface 1 Client Interface 2
- 1062 Mbit/s - 1250 Mbit/s
Different Groups Configured to Different Data Rates

Different groups can be configured to different data rates. As soon as one client interface is configured to a
supported date rate (1062 Mbit/s or 1250 Mbit/s) the second client interface in this group is configured
automatically:
Table 44: Example of Different Groups Configured to Different Data Rates
Group 1 Group 2
Client Interface 1 Client Interface 2 Client Interface 3 Client Interface 4
- 1062 Mbit/s - 1062 Mbit/s - 1250 Mbit/s - 1250 Mbit/s
LED Status
CAUTION
Note
troubleshooting steps in Table 45 based upon the states of the LEDs structured.
The 8TCA-PC-2G1U+10G-V has twenty LEDs on the faceplate:
• “C1/T”, “C2/T”, “C3/T”, “C4/T”, “C5/T”, “C6/T”, “C7/T”, “C8/T”, “C1/R”, “C2/R”, “C3/R”, “C4/R”, “C5/R”,
“C6/R”, “C7/R”, “C8/R” “N/T” and “N/R” to indicate the interface status
This module has 8 client interfaces (C1 to C8). The LED status in Table 45 will refer to the transmit connector and
receive connector of one client interface (Cx/T and Cx/R) as an example for all client interfaces on the module.
Note
Table 45: LED Status of the 8TCA-PC-2G1U+10G-V

Name
On Off Power failure Remove and reinsert the module. If the

condition continues, the module should be
returned to ADVA Optical Networking for
repair.
Err Red blinking Module forced settings Laser Laser Forced ON is activated.
forced on Check the Facility (Ch) Operation settings.
Note: The C/T and N/T LEDs If the condition continues once the module
are green even if no signal is has lost and regained power or all Forced
received from the far-end. ON settings have been turned off, return it to
Module forced settings Loopback is activated

Loopback present on this Check the Facility (Ch) Operation settings.
module. If the condition continues once the module
Note: In case a signal is has lost and regained power or all loops
connected to the C/R, the C/R have been turned off, return it to ADVA
and C/T LEDs are yellow. Optical Networking for repair.
In case a signal is connected to
the C/R, the C/R LED is yellow
and the C/T LED is yellow
blinking to green.
The remote link to the far end
module has to be established to
make this loop operational.
The N/R LED is yellow and N/T
LED is yellow blinking to green.
Off There is no error. The normal No action is required.

state is Off.

Name
Cx/R Red blinking Pluggable transceiver is No action is required.

one time inserted and detected (lights up
only during insertion of the
device into the respective
cage).*
Yellow Module forced settings Loopback is activated

has lost and regained power or all loops
have been turned off, return it to ADVA
Green flashing Interface is disabled and Check the Facility (Ch) Operation settings.
to off receives a signal from the If the condition continues once the module
connected application. has lost and regained power or all loops
have been turned off, return it to ADVA
Off No data is being received from Check the fiber connectivity towards the
the CPE. client equipment. Refer to “Finding Your
Problem - Follow the Light” on p. 53 in this
document.
Green Data is being received from the No action is required.

CPE on the client interfaces.
Cx/T Red A colored pluggable transceiver Replace pluggable transceiver with a correct
has been inserted into the client grey pluggable transceiver (850nm or
interface. Corresponding 1310nm).
transmitter is disabled.
Red blinking Pluggable transceiver is No action is required.

one time inserted and detected (lights up
only during insertion of the
device into the respective
cage).*
Yellow Module forced settings Loopback is activated

Note: In case no signal is has lost and regained power or all loops
connected to this port. have been turned off, return it to ADVA

Name
Cx/T Off flashing to Pluggable transceiver is not Consult your ADVA Optical Networking
red approved by ADVA Optical Representative about obtaining a pluggable
Networking, but is transmitting transceiver approved by ADVA Optical
traffic Networking.
Off No data is being received from Check the fiber connectivity towards the
the CPE. client equipment. Refer to “Finding Your
document.
Green blinking Module forced settings

to yellow loopback present on this
module.
Note: In case a signal is
connected to this port.
Green Data (as received from far-end No action is required.

of the link) is being transmitted
to the CPE.
N/R Yellow Loss of frame - No frame sync 1 Verify that the provisioned service type
detected matches the incoming signal type.
Module forced settings Loopback is activated

module If the condition continues once the module
Note: N/T LED is Green/Yellow has lost and regained power or all loops
blinking. have been turned off, return it to ADVA
Off No data is being received from Check the fiber connectivity between the
the far-end of the link. nodes. Refer to “Finding Your Problem -
Green Valid data is being received No action is required.

from the far-end of the link.
N/T Yellow The network laser is warming If the condition continues, the module has
blinking up. During the warm-up phase lost and regained power or all loops have
(approximately 30 s) the been turned off, return it to ADVA Optical
network laser cannot be Networking for repair.
enabled. After setting process
the LED stops blinking.

Name
N/T Green flashing Auto Laser Shutdown Module is trying to bring up the network link.
If this status persists, check the fiber
connectivity between the nodes using.
Refer to “Finding Your Problem - Follow the
Green blinking Module forced settings Loopback is activated

to Yellow Loopback present on this Check the Facility (Ch) Operation settings.
module If the condition continues once the module
Note: N/R LED is has lost and regained power or all loops
Green/Yellow blinking. have been turned off, return it to ADVA
Off No data is being received from Check the fiber connectivity between the
the far-end of the link. nodes. Refer to “Finding Your Problem -
Green Data is being transmitted to the No action is required.

far-end of the link or the
network interface transmitter is
forced on.
10PCA-PCN-1G3+10G
This subsection will help you resolve issues that can be experienced on 10PCA-PCN-1G3+10G modules. It
assumes that all measurements for the Cx, N East, and N West interfaces are within ADVA Optical Networking
FSP 3000R7 module’s client interface. If not, refer to “Finding Your Problem - Follow the Light” on p. 53.
10PCA-PCN-1G3+10G modules in a link are synchronized, the network link is up. The network
CAUTION
the 10PCA-PCN-1G3+10G module. For details on updating module firmware, refer to “Updating
Note
Note
CAUTION
Note
The 10PCA-PCN-1G3+10G has 14 LEDs on the faceplate:

• “Mod” to indicate the looping back on the client or network interfaces
• “C1”, “C2”, “C3”, “C4”, “C5”, “C6”, “C7”, “C8”, “C9”, “C10”, “NW” and “NE” to indicate the interface status.
Note
Table 46: LED Status of the 10PCA-PCN-1G3+10G

Name
tialization. If the condition continues, return the module
to ADVA Optical Networking for repair.
Off Power failure
Mod Yellow blinking Management 1 Check the SCU firmware version and
to off communication to the compare it to the SCU firmware version
module has failed. as listed on the NCU. If they are
different, update the SCU firmware as
Off Module admin state is 1 In the case that the module is installed
disabled. and provisioned, check the admin state
settings.
Module admin state is 1 If the management displays

unassigned. “unassigned”, check if the module is
provisioned.

Service”

removed.

Name
specification.
Yellow Loss of character sync Unable to synchronize on the characters in

the incoming data stream.



input.

Name
Cx Yellow Loss of output power - Refer to “Finding Your Problem - Follow the
output. Normally a
may be due to
splice.
channel module.

traffic Networking.

Service”.


alarms

Name

removed.
specification.
Yellow Loss of character sync Synchronization to the far-end lost. Unable to

synchronize on the characters in the

specification.
3 Install appropriate attenuators to fulfill
the Optical Input Power requirements.


Name
NW, NE Off flashing to Pluggable transceiver 1 Compare the supported data rates of the
channel module.

traffic Networking.

Service”.


alarms
Troubleshooting Access Type WDM Channel Modules
Troubleshooting Access Type WDM Channel

Modules
This section will help you resolve issues that can be experienced on WDM access
channel modules. One very important difference between the Single Application and
WDM access channel modules is that the Single Application modules require that an
application signal be present before it attempts to establish a network link. The WDM
access channel modules, however, will attempt to establish the network link immediately
upon power on. This leads to slight differences in what you could expect to see as normal
LED states.
The LEDs are located on the faceplate of every WDM access channel module.
“2WCA-PCN-10G” on p. 277
“WCA-PC-10G-V” on p. 281
“WCA-PCN-2G5U” on p. 286
“5WCA-PCN-16GU” on p. 297
2WCA-PCN-10G
This subsection will help you resolve issues that can be experienced on 2WCA-PCN-10G modules.
It assumes that all measurements for the Cx, N East, and N West interfaces are within ADVA Optical
wavelength for the FSP 3000R7 module’s client interface. If not, refer to “Finding Your Problem - Follow the Light”
on p. 53.
2WCA-PCN-10G modules in a link are synchronized, the network link is up. The network
CAUTION
the 2WCA-PCN-10G module. For details on updating module firmware, refer to “Updating the
Note
Note
CAUTION
Note
The 2WCA-PCN-10G has six LEDs on the faceplate:

Note
Table 47: LED Status of the 2WCA-PCN-10G

Name
tialization. If the condition continues, return the
module to ADVA Optical Networking for
P Yellow Power is abnormal repair.
Off Power failure
Green Power is ok No action is required.
Mod Yellow flashing to Management communication 1 Check the SCU firmware version and
off to the module has failed. compare it to the SCU firmware
are different, update the SCU firmware
as described in “Performing Other
Off Module admin state is 1 In the case that the module is installed
“disabled” and provisioned, check the admin
state settings.
change the admin state settings to “In
Service”, “Management” or
“Maintenance”.
Module admin state is 1 If the management displays

“unassigned” “unassigned”, check if the module is
provisioned.

status is “Maintenance”,
“Management”, or “In
Service”.
C1, C2, Red Pluggable transceiver was Reinsert the pluggable transceiver.
NE, NW inserted and the interface
removed.

Name
C1, C2, Yellow Loss of clock 1 Verify that the provisioned service
NE, NW type matches the incoming signal
type.
document.

the procedure, “Finding Your Problem -
document.
requirements.
Green flashing to Pluggable transceiver in No action is required.

off protection group, standby
path
Green flashing to ALS pulse received No action is required.

off - one time
Off flashing to red Pluggable transceiver 1 Compare the supported data rates of
mismatch - None of the data the board with the pluggable
rates supported by the transceiver data rates.
installed pluggable 2 Install the correct pluggable
transceiver match the data transceiver.
channel module.

Networking - no traffic. pluggable transceiver approved by ADVA
Optical Networking.

Name
C1, C2, Off There is no Ch port (Facility) 1 Install an appropriate pluggable

NE, NW provisioned on that pluggable transceiver.
transceiver 2 Provision the pluggable transceiver.
pluggable transceiver admin state to
“In Service”.
4 Provision a Ch interface (Facility) on
5 Enable the Ch interface (Facility)
interface (Facility) admin state to “In
Service”.
Ch interface (Facility) admin Change Ch interface (Facility) admin state.

state is disabled.

alarms
WCA-PC-10G-V
This subsection will help you resolve issues that can be experienced on the WCA-PC-10G-V module. This module is available in different variants that are described in the
It assumes that all measurements for the C/R, C/T, N/R and N/T interfaces are within ADVA Optical Networking specifications and that you have verified that the
application wavelength is the same as the wavelength for the FSP 3000R7 module’s client interface. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this
document.
the near-end and the far-end WCA-PC-10G-V modules in a link are synchronized, the network link is up.
CAUTION
Before you start with troubleshooting, ensure that the current firmware package is installed on the WCA-PC-10G-V module. For details on updating module
firmware, refer to “Updating the NE Software Release” on p. 617 and “Performing Other Software Update Actions” on p. 628.
Note
Note
The use of pluggable transceivers other than those approved by ADVA Optical Networking will result in loss of safety approval for the FSP 3000R7.
Pluggable transceivers not approved by ADVA Optical Networking will not function properly. Depending on the channel module type, Rx and Tx of the
affected interfaces may be disabled automatically or not. Only approved pluggable transceivers will guarantee the behavior in conjunction with the channel
CAUTION module as specified.
Representative.
Note
The WCA-PC-10G-V has six LEDs on the faceplate:

• “On/Err” to indicate the power supply status
• “Loop” to indicate the looping back on the client or network interfaces
• “C/T”, “C/R”, “N/T” and “N/R” to indicate the interface status
The steps in this subsection may need to be completed on both sides of the link. Please follow the troubleshooting steps in Table 48 based upon the states of the LEDs.
When a module is removed, it should not be reinserted for at least 10 seconds to allow all power on the module to dissipate.
Note
Table 48: LED Status of the WCA-PC-10G-V
O/E Loop C/R C/T N/R N/T
Off Off Off Off Off Off The module receives Check the module whether it has been inserted correctly
no power. (remove and reinsert).
Green Off Off Off Off Yellow This is normal behavior during the install procedure. The network laser temperature
blinking will be modulated. After approximately 30 seconds, this procedure is finished and the
N/T LED is off.
solid Red Off Off Off Off Off An internal error If the condition continues once the module has been
condition exists. removed and reinserted, it should be returned to ADVA
Green Off Green Off Off blinks Green Attempting • If all power measurements are in specification on both
(flashing every 10 unsuccessfully to sides of the link, then it is possible that the network
Red/ seconds establish network receiver of one of the modules is damaged. Loop N/T to
Green) link. N/R with a 20 dB attenuated patch cable.
• If the N/R and C/R LEDs do not illuminate once the
attenuated patch cable has been applied, then the
module is damaged and must be returned to ADVA
• If N/R and C/T do illuminate, repeat the test on the other
side of the link.
• If both sides of the link illuminate with the patch cable,
but not when the network link is connected, please
contact your ADVA Optical Networking Technical
Note – If you do not use a 20 dB attenuated patch cable for
the test above, you will destroy the module being tested.
solid Red Off solid Green solid Green solid solid Green Clock frequency on Check the client clock setting
Yellow the client interface
does not match to the Note – The pluggable transceiver is not able to detect a clock
data rate of the mismatch, in fact of it a clock mismatch will be not signalled
connected on the C/R LED.
application. Network
clock is set
automatically
depending on the
client clock settings.
N/R lights up solid
yellow, because the
clock setting of the
far-end module does
match to the data
rates of the
connected
application.
Red/ solid solid Greed solid Green Off Off Client loop is Check the client interface settings.
Green Yellow (flashing activated. If the condition continues once the module has lost and
blinking Red/ regained power or all loops have been turned off, it should be
Green) returned to ADVA Optical Networking for repair.
Red/ solid solid Green Off solid solid Green Network loop is Check the network interface settings
Green Yellow (flashing Green activated. If the condition continues once the module has lost and
blinking Red) regained power or all loops have been turned off, it should be
Red/ solid solid Green Off solid solid Green Network loop Check all loop settings.
Green Yellow (flashing Green (Regenerator Mode) If the condition continues once the module has lost and
blinking Red/ and client loop are regained power or all loops have been turned off, it should be
Green) activated. returned to ADVA Optical Networking for repair.
Red/ Off solid Green Off solid solid Green Client laser is set to Check the client interface settings.
Green (flashing Green forced on. If the condition continues once the module has lost and
Red/ Off solid Green Off solid solid Green Network laser is set Check the network interface settings.
Green (flashing Green to forced on. If the condition continues once the module has lost and
If no signal is connected on the C/R the N/R LED of the far-
end module lights up yellow, because the forced on network
laser transmitted CW light and this does not match to the
network clock recovery frequency.
solid Off Off Off solid solid Green Regenerator Mode is Check the Regenerator settings
Green (flashing Green activated. If the condition continues once the module has lost and
Red) regained power or all loops have been turned off, it should be
blinking Off Off Off solid solid Green Regenerator Mode 1 Check the Regenerator settings.
Red/ (flashing Green and network laser are 2 Check the network laser setting.
Green Red) activated.
If the condition continues once the module has lost and
regained power or all loops have been turned off, it should be
solid Red Off Off flashing solid solid Green Regenerator Mode is Check the Regenerator settings
Red Yellow activated, but the If the condition continues once the module has lost and
network clock setting regained power or all loops have been turned off, it should be
does not match to the returned to ADVA Optical Networking for repair.
transmitted data rate.
WCA-PCN-2G5U
This subsection will help you resolve issues that can be experienced on WCA-PCN-2G5U modules.
It assumes that all measurements for the C/R, C/T, N/R East, N/R West, N/T West and N/T East interfaces are within ADVA Optical Networking specifications and that
you have verified that the application wavelength is the same as the wavelength for the FSP 3000R7 module’s client interface. If not, refer to “Finding Your Problem -
Follow the Light” on p. 53.
the near-end and the far-end WCA-PCN-2G5U modules in a link are synchronized, the network link is up. The network interface LEDs light up solid green
or blink green depending on the configured transmission mode: Multiplexer NE Only, Multiplexer NW Only, Multiplexer NE & NW or Regenerator 1-Way.
CAUTION
Before you start with troubleshooting, ensure that the current firmware package is installed on the WCA-PCN-2G5U module. For details on updating
Note
Note
The use of pluggable transceivers other than those approved by ADVA Optical Networking will result in loss of safety approval for the FSP 3000R7.
Pluggable transceivers not approved by ADVA Optical Networking will not function properly. Depending on the channel module type, Rx and Tx of the
affected interfaces may be disabled automatically or not. Only approved pluggable transceivers will guarantee the behavior in conjunction with the channel
CAUTION module as specified.
Representative.
Note
The WCA-PCN-2G5U provides eight LEDs on the faceplate:

• “LP” to indicate the looping back on the client or network interfaces
• “C/T”, “C/R”, “NW/T”, “NE/T”, “NW/R” and “NE/R” to indicate the interface status
LEDs.
When a module is removed, it should not be reinserted for at least 10 seconds to allow all power on the module to dissipate.
Note
Table 49: LED Status of the WCA-PCN-2G5U
O/E Lp C/R C/T NW/R or NW/T or

NE/R NE/T
Off Off Off Off Off Off The module receives no Check the module whether it has been inserted
power. correctly (remove and reinsert).
solid Red Off Off Off/Red Off Off/Red An internal error condition If the condition continues once the module has been
flashing flashing exists. removed and reinserted, it should be returned to ADVA

NE/R NE/T
Green Off Green Off/Red Off blinks Green Attempting Check the Transmission Mode setting for Converter on
flashing every 10 unsuccessfully to Mode West respective on Mode East, both PLR
seconds establish network link. modules must be set to the same Transmission Mode.
• If all power measurements are in specification on
both sides of the link, then it is possible that the
network receiver of one of the modules is
damaged. With a 20 dB attenuated patch cable,
loop NW/T to NW/R respective NE/T to NE/R.
• If the NW/R respective NE/R and C/R LEDs do
not illuminate once the attenuated patch cable has
been applied, then the swap the network pluggable
transceiver. If the symptom is not resolved, the
module is damaged and has to be returned to
• If NW/R respective NE/R and C/T illuminate,
repeat the test on the other side of the link.

NE/R NE/T
Green Off Green Off/Red Off blinks Green Attempting • If both sides of the link illuminate with the patch
flashing every 10 unsuccessfully to cable, but not when the network link is connected,
seconds establish network link. please contact your ADVA Optical Networking
Note – If you do not use a 20 dB attenuated patch cable
for the test above, you will destroy the module being
tested.
solid Red Off solid solid Red solid solid Green Clock frequency on the Check the client clock setting.
Yellow Yellow flashing Red/ client interface does not
Green) match to the data rate of
the connected
clock is set automatically
depending on the client
clock settings. NW/R
respective NE/R lights
up solid yellow, because
the clock setting of the
far-end module does
match to the data rates of
the connected
application.

NE/R NE/T
Red/ solid solid solid Green Off Off (flashing Client loop is activated Check the client interface settings.
Green Yellow Green flashing Red) If the condition continues once the module has lost and
blinking Red/ Green) regained power or all loops have been turned off, it
should be returned to ADVA Optical Networking for
repair.
Red/ solid solid Off (flashing solid Green solid Green Network loop is activated Check the network interface settings
Green Yellow Green Red) (flashing Red/ If the condition continues once the module has lost and
blinking Green) regained power or all loops have been turned off, it
repair.
Red/ Off solid Off (flashing solid Green solid Green Client laser is set to Check the client interface settings.
Green Green Red/ Green) (flashing Red/ forced on If the condition continues once the module has lost and
repair.
Red/ Off solid Off (flashing solid Green solid Green Network laser is set to Check the network interface settings.
Green Green Red/ Green) (flashing Red/ forced on If the condition continues once the module has lost and
repair.
Red/ Off solid Off (flashing solid Green solid Green Transmission Mode is Protected network receiver does not get a signal from
Green Green Red/ Green) (flashing Red/ set to Multiplexer NE & the far-end, because there is only one network laser
blinking Green) NW working (Converter on Mode West or on Mode East)

NE/R NE/T
solid Red Off solid solid Red solid solid Green Clock frequency on the Check the client clock setting.
Yellow Yellow (flashing Red/ client interface does not
Green) match to the data rate of
the connected
clock is set automatically
depends on the client
clock settings. NW/R
respective NE/R lights
up solid yellow, because
the clock setting of the
far-end module does
match to the data rates of
the connected
application.
solid Off solid solid Green NE/R - Off (flashing Transmission Mode Check the Transmission Mode setting.
Green Green (flashing solid Red) setting on the far-end
Red/ Green) Yellow module (set to Converter
on Mode A) does not
NW/R - match to the near-end
blinking Transmission Mode
Red setting

NE/R NE/T
solid Off solid solid Green NW/R - NW/T - Off Transmission Mode Check the Transmission Mode setting.
Green Green (flashing solid Green (flashing Red) setting on the far-end
Red/ Green) NE/R - module (set to Converter
blinking NE/T - solid on Mode A) does not
Red Green match to the near-end
/flashing Red/ Transmission Mode
Green) setting
solid Blinking solid solid Green NW/R - NW/T - Off The Line Mode in Hot Set the Line Mode to Auto, in order to guarantee a
Green Yellow Green (flashing solid Green (flashing Red) Standby Parameter is set proper switching.
Red/ Green) NE/R - NE/T - solid to the active line. Note: This module cannot switch to the protected line,
blinking Green traffic to this module is interrupted as soon as the
Red /flashing Red/ working line is broken.
Green)

NE/R NE/T
solid Off solid Off (flashing Off Off (flashing In order to troubleshoot For the bidirectional Regenerator Mode, CWDM and
Green Green Red) Red) the near-end and the far- DWDM pluggable transceivers approved by ADVA
end OTM modules, refer Optical Networking are supported only.
to the first LED Status The pluggable transceiver laser turn on time has to be
section in Transmission lower than 1ms in order to support the ALS
Mode: Converter on functionality, this is guarantied by pluggable
Mode West / Converter transceivers approved by ADVA Optical Networking
on Mode East only.
Regenerator Inline: Note – If you do not use a 20 dB attenuated patch cable
Attempting for the test below, you will destroy the module being
unsuccessfully to tested.
establish network link. • If all power measurements are in specification on
both sides of the link, then it is possible that the
network receiver of one of the modules is
damaged.
Loop NW/R with NE/T respective NE/R with
NW/T with a 20 dB attenuated patch cable.
• If the NW/R respective NE/R LEDs do not
illuminate once the attenuated patch cable has
been applied, then the swap the network pluggable
transceiver. Is not resolved the problem the module
is damaged and has to be returned to ADVA
• If both sides of the link illuminate with the patch
cable, but not when the network link is connected,
please contact your ADVA Optical Networking

NE/R NE/T
solid Off Off Off (flashing solid solid Green Clock frequency on the Check the network clock setting.
Green Red) Yellow flashing Red/ network interface does
Green) not match to the received
data rate.
Red/ solid Off Off (flashing solid Green Off (flashing Network loop is activated Check the network interface settings.
Green Yellow Red) Red) on both network Note: Network link does not come up in both directions,
blinking pluggable transceivers. network LEDs on the near and far-end OTM modules
are off.
Red/ solid Off Off (flashing NW/R - NW/T - Off Network loop is activated Check the network west loop settings.
Green Yellow Red) solid Green (flashing Red) on both network Note: Network link does not come up in one direction,
blinking NE/R - Off NE/T - solid pluggable transceivers network LEDs on the near and far-end OTM modules
Green line West. are off.
(flashing Red/
Green)

NE/R NE/T
Red/ Off Off Off solid Green (flashing Red) Network laser is set to Check the network interface settings.
Green forced on. • If the condition continues once the module has lost
blinking and regained power or all loops have been turned
off, it should be returned to ADVA Optical
• Please note, the module should lose power for at
least 10 seconds to allow any and all capacitance
to dissipate.
• If not a signal is connected on the C/R of the near-
end OTM module the NE/R respective NE/R LED
of the Regenerator Inline module lights up yellow
and the C/T LED of the far-end OTM module lights
up red, because the forced on network laser
transmitted CW light and this does not match to
the network clock recovery frequency.
5WCA-PCN-16GU
This subsection provides troubleshooting guidelines for 5WCA-PCN-16GU modules.
It assumes that all measurements for the Cx and Nx interfaces are within ADVA Optical Networking
steps, you could destroy the module. As soon as the near-end and the far-end 5WCA-PCN-
16GU modules in a link are synchronized, the network link is up.
CAUTION
the 5WCA-PCN-16GU module. For details on updating module firmware, refer to “Updating the
Note
Before you start with troubleshooting, ensure that the Admin state of the affected module is
Note
CAUTION
Note
The 5WCA-PCN-16GU has twelve LEDs on the faceplate:

• “C1”, “C2”, “C3”, “C4”, and “C5” to indicate the client port status
• “N1”, “N2”, “N3”, “N4”, and “N5” to indicate the network port status
Note
Table 50: LED Status of the 5WCA-PCN-16GU

Name
tialization. If the condition continues, return the
P Yellow Power is abnormal repair.
Off Power failure

repair.
Yellow flashing to No management 1 Check the SCU firmware version and

off communication. compare it to the SCU firmware
are different, update the SCU firmware
as described in “Performing Other
Off Admin state is “disabled” If the module is to be used, set the Admin
State to "In Service”, “Management” or
“Maintenance”.
Admin state is “unassigned” If the module is to be used, provision the

module.
Green Module operation is normal. No action is required.
Cx, Nx Red Pluggable transceiver was Reinsert the pluggable transceiver.

inserted and the interface
removed.

transceiver, if a replacement is available.

Name
Cx, Nx Yellow Loss of clock 1 Verify that the provisioned service

type.
document.

the procedure, “Finding Your Problem -
document.
range receiver connector and compare the
specification.
2 Adjust the optical input power (install
the appropriate attenuators) at the
receiver(s) to ensure the optical input
power requirements are met.
Off flashing to red Pluggable transceiver 1 Compare the supported data rates of
mismatch - None of the data the board with the pluggable
rates supported by the transceiver data rates.
installed pluggable 2 Install the correct pluggable
transceiver match the data transceiver.
channel module.

Networking - no traffic. pluggable transceiver approved by ADVA
Optical Networking.

Name
Cx, Nx Off There is no Ch port (Facility) 1 Install an appropriate pluggable

transceiver 2 Provision the pluggable transceiver.
pluggable transceiver admin state to
“In Service”.
4 Provision a Ch interface (Facility) on
5 Enable the Ch interface (Facility)
interface (Facility) admin state to “In
Service”.
Ch interface (Facility) Admin Change Ch interface (Facility) Admin

state is disabled. state.
Green Interface operation is normal No action is required.
Cx Yellow flashing to In a client channel card pro- Refer to “Finding Your Problem - Follow the
off tection configuration, the pro- Light” on p. 53 in this document.
tection path corresponding to
this standby port is unavail-
able.
Green flashing to In a client channel card pro- No action is required

off tection configuration, this
standby port is operating
error-free. Hence, the inter-
face is capable of taking over
traffic.
Chapter 6
Enterprise Type Channel Modules

This chapter addresses all enterprise type channel modules available at the publication
date of this manual.
“Troubleshooting Enterprise Type TDM Channel Modules” on p. 302, which addresses
LED indicators and troubleshooting guidelines for TDM enterprise channel modules.
“Troubleshooting Enterprise Type WDM Channel Modules” on p. 368, which addresses
LED indicators and troubleshooting guidelines for WDM enterprise channel modules.

consequent actions (for example, LKDO-OFF) are not indicated by these
Note LEDs, since they require troubleshooting the fault upstream (at another
port of the same module or a remote module).
Troubleshooting Enterprise Type TDM Channel Modules
Troubleshooting Enterprise Type TDM Channel

Modules
This section will help you resolve issues that can be experienced on TDM enterprise
channel modules.
One very important difference between the Single Application and TDM enterprise
channel modules is that the Single Application modules require that an application signal
be present before it attempts to establish a network link. The TDM enterprise channel
modules, however, will attempt to establish the network link immediately upon power on.
This leads to slight differences in what you could expect to see as normal LED states.
The LEDs are located on the faceplate of every TDM enterprise channel module.
“5TCE-PCTN-8GU+(AES)10GS” on p. 303
“5TCE-PCN-8GU+(AES)10GS” on p. 312
“5TCE-PCTN-10GU+(AES)10G” on p. 321
“5TCE-PCN-10GU+(AES)10G” on p. 330
“8TCE-ESCON+2G5-V” on p. 339
“8TCE-GLINK+2G5-V” on p. 343
“10TCE-PCN-10G+100G(-GF)” on p. 347
“10TCE-PCN-16GU+(AES)100G and 10TCE-PCN-16GU+AES100G-BSI” on p. 353
5TCE-PCTN-8GU+(AES)10GS
This subsection will help you resolve issues that can be experienced on a 5TCE-PCTN-8GU+10GS and 5TCE-
PCTN-8GU+AES10GS module.
The modules are available in different variants that are described in the Hardware Description.
It assumes that all measurements for the Cx/R, Cx/T and the network interface are within ADVA Optical
wavelength for the FSP 3000R7 module’s client interfaces. If not, refer to “Finding Your Problem - Follow the
you could destroy the module being tested. As soon as the near-end and the far-end 5TCE-
PCTN-8GU+(AES)10GS modules in a link are synchronized, the network link is up and the
the 5TCE-PCTN-8GU+(AES)10GS module. For details on updating module firmware, refer to
Note on p. 628.
Note
Note
The 5TCE-PCTN-8GU+(AES)10GS module supports configuring ‘disparity correction’. It is set

to “enabled” by default. For more information about this parameter, refer to the Management Data
Guide.
Note
Note
The 5TCE-PCTN-8GU+(AES)10GS has eight LEDs on its faceplate:
• “C1”, “C2”, “C3”, “C4”, “C5” and “N” to indicate the interface status
This module has 5 client interfaces (C1 to C5). The LED status in Table 51 on p. 304 will refer to the transmit
connector and receive connector of one client interface (Cx/T and Cx/R) as an example for all client interfaces on
the module.
Note
Table 51: LED Status of the 5TCE-PCTN-8GU+(AES)10GS

Name
All LEDs Red A serious error in card Remove and reinsert the module. If the condition per-
initialization. sists, return the module to ADVA Optical Networking
for repair.
Off Power failure
Mod Red Encryption Failure 1 Check the module for any active or passive
attacks.
2 Check the module settings, e.g. authentication
password, temperature or voltage values.
3 If you are assigned as Crypto Officer, adapt the
settings, if appropriate. Otherwise, consult the
corresponding person configured as Crypto
Officer on this module.
For more information about the module settings, refer
to the Network Element Director Online Help.
Tamper event • Check for any visible damages to the module

occurred. cover.
• If the module had been removed, reinsert it.
• Check the temperature and voltage values of the
module.
Yellow Communication Check the Config tab on the port associated with the
between channel protection and verify that the module AIDs for the
modules using client protected modules are correct.
channel card
protection has failed.

Name
Mod Yellow Crypto-Officer 1 Check the Crypto-Officer settings.

password has failed 2 If you are assigned as Crypto Officer, adapt the
or is missing. settings if appropriate. Otherwise, consult the
For more information about configuring the Crypto
Officer, refer to the Network Element Director Online
Help.
Self tests or key- 1 Check the module for any active or passive
exchange process attacks.
has failed. 2 If there are no attacks and you are assigned as
Crypto Officer, manually re-enable the key-
exchange process. Otherwise, consult the
Module runs in • Check for any visible damages to the module

“degraded” mode. cover.
module.
3 If the LED behavior persists and you are assigned
as Crypto Officer, adapt the module settings if
appropriate. Otherwise, consult the corresponding
person configured as Crypto Officer on this
module.
Yellow Management 1 Check the SCU firmware version and compare it

blinking to off communication to the to the SCU firmware version as listed on the
module has failed. NCU. If they are different, update the SCU
firmware as described in “Performing Other
If the LED is still blinking yellow to off, contact your
ADVA Optical Networking Technical Services
Representative.

Name
Mod Off Module admin state is 1 If the module is installed and provisioned, check
disabled. the admin state settings.
2 If the management displays “disabled”, change
the admin state to “In Service”, “Management” or
“Maintenance”.
Module admin state is 1 If the management displays “unassigned”, check

unassigned. if the module is provisioned.
Green Module provisioned, No action is required.

admin state is
“Maintenance”,
Service”
Cx Red Pluggable transceiver Reinsert the correct pluggable transceiver.

was inserted and the
then the pluggable
transceiver was
removed.
Tx Laser Failure If a replacement module is available exchange the

malfunctioning pluggable transceiver. Otherwise
return the malfunctioning pluggable transceiver to
Pin max too high 1 Measure the optical input power on the receiver
connector and compare the measured value with
the channel module/pluggable transceiver
specification.
appropriate attenuators) to fulfill the Optical Input
Power requirements.
Yellow Loss of character The client signal does not match and therefore, the
synchronization incoming data-stream characters cannot be
synchronized.
1 Ensure that the fiber cables are properly
connected.
2 Check that the data rate and protocol matches.
document.

Name
Cx Yellow Loss of signal 1 Verify that fiber cables are properly connected.
2 Check optical power levels. Refer to the
procedure, “Finding Your Problem - Follow the
Optical Input Power 1 Measure the optical input power on receiver

out of range connector.
2 Compare the measured value with the channel
Power requirements.
Loss of input power - Refer to “Finding Your Problem - Follow the Light” on
Power non-existing or p. 53 in this document.
below the defined
minimum level
Yellow Channel runs in Refer to “Finding Your Problem - Follow the Light” on
flashing to off protection group p. 53 in this document.
“standby” mode and
experiences loss of
input power - Power
non-existing or below
the defined minimum
level detected at the
input.

(Facility) provisioned 2 Provision the pluggable transceiver.
on that pluggable
3 Enable the admin state - Configure the pluggable
transceiver.
transceiver admin state to “In Service”.
5 Enable the Ch Interface (Facility) admin state -
Configure the Ch Interface (Facility) admin state

admin state is
disabled.

Name
Cx Off flashing Pluggable transceiver 1 Compare the supported data rates of the board
to red mismatch – None of with the pluggable transceiver data rates.
the data rates 2 Install the correct pluggable transceiver.
supported by the
installed pluggable
data rates supported
by the channel
module.
Off flashing Pluggable transceiver Consult your technical services representative about
to red is not approved by obtaining a pluggable transceiver approved by ADVA
ADVA Optical Optical Networking.
Networking - no
traffic.
Green Interface is active, No action is required.

valid signal, valid
hardware, no alarms
Green Module runs in Refer to “Finding Your Problem - Follow the Light” on
flashing Protection Group p. 53 in this document.
Standby mode.
Green Pluggable transceiver Consult your technical services representative about

flashing to is not approved by obtaining a pluggable transceiver approved by ADVA
red ADVA Optical Optical Networking.
Networking.
N Red Tx Laser Failure If a replacement module is available, exchange the

malfunctioning pluggable transceiver. Otherwise,
specification.
Power requirements.

Name
N Red Session-key has 1 Check the module for any active or passive
expired. attacks.
3 If you are assigned as Crypto Officer,
o
adapt the module settings if appropriate.
o
manually re-enable the key-exchange
process if appropriate.
Otherwise, consult the corresponding person
configured as Crypto Officer on this module.
Yellow Loss of clock 1 Verify that the provisioned service type matches
the incoming signal type.
document.
Loss of signal 1 Verify that there is a network connection

available.
2 Verify that fiber cables are properly connected.
document.
Loss of frame - No 1 Verify that the provisioned service type matches

frame sync detected the incoming signal type.
document.
Optical Input Power 1 Measure the optical input power on the receiver
3 Adjust the optical input power (i.e., the appropriate
attenuators) to fulfill the Optical Input Power
requirements.

Name
N Yellow Loss of input power - Refer to “Finding Your Problem - Follow the Light” on
below the defined
minimum level is
Key-exchange 1 Verify that s a network connection available.

process has failed. 2 Check the module for any active or passive
attacks.
3 If there are no attacks and you are assigned as
Module runs in If you are assigned as Crypto Officer, set the module
transparent (bypass) back to encryption mode or consult the corresponding
mode; no data person configured as Crypto Officer on this module.
encryption. For more information, refer to the Network Element
Director Online Help.
Module 1 Check the module for any active or passive

authentication attacks.
password has failed 2 Check the authentication password settings.
or is missing.
settings if appropriate. Otherwise, consult the
Yellow First key has been No action is required.

flashing exchanged after a
module cold restart.
document.

Name
N Off No Ch Interface 1 Provision a Ch Interface (Facility).

(Facility) provisioned. 2 Enable the Ch Interface (Facility) admin state -

admin state is
disabled.

valid signal, valid
hardware, no alarms
5TCE-PCN-8GU+(AES)10GS
This subsection addresses LED indications and troubleshooting guidelines for 5TCE-PCN-8GU+10GS and
5TCE-PCN-8GU+AES10GS modules, henceforth referred to as 5TCE-PCN-8GU+(AES)10GS.
you could destroy the module being tested. As soon as the near-end and the far-end 5TCE-PCN-
8GU+(AES)10GS modules in a link are synchronized, the network link is up and the network
the 5TCE-PCN-8GU+(AES)10GS module. For details on updating module firmware, refer to
Note on p. 628.
Note
Note
The 5TCE-PCN-8GU+(AES)10GS module supports configuring ‘disparity correction’. It is set to

Guide.
Note
Note
troubleshooting steps in Table 52 on p. 313 based on the LED states.
The 5TCE-PCN-8GU+(AES)10GS has eight LEDs on its faceplate:
• Cx (x = 1 through 5) to indicate the status of the client interface
• “N” to indicate the status of the network interface
Note
Table 52: LED Status of the 5TCE-PCN-8GU+(AES)10GS

Name
All LEDs Red A serious error in card Remove and reinsert the module. If the condition per-
initialization. sists, return the module to ADVA Optical Networking
for repair.
Off Power failure
attacks.
settings, if appropriate. Otherwise, consult the
Tamper event • Check for any visible damage to the module

occurred. cover.
module.
channel card
Crypto-Officer 1 Check the Crypto-Officer settings.

password has failed or 2 If you are assigned as Crypto Officer, adapt the
is missing. settings if appropriate. Otherwise, consult the
Help.

Name
Mod Yellow Self tests or key- 1 Check the module for any active or passive
exchange process has attacks.
failed. 2 If there are no attacks and you are assigned as
Module runs in • Check for any visible damages to the module

module.
3 If the LED behavior persists and you are
assigned as Crypto Officer, adapt the module

Representative.
Off Module admin state is 1 If the module is installed and provisioned, check
“Maintenance”.
Module admin state is 1 If the management displays “unassigned”, check


Name

admin state is
“Maintenance”,
Service”

then the pluggable
transceiver was
removed.
Tx Laser Failure If a replacement module is available exchange the

specification.
Power requirements.
synchronized.
connected.
document.
Loss of signal 1 Verify that fiber cables are properly connected.


Name
Cx Yellow Optical Input Power 1 Measure the optical input power on receiver
Power requirements.
below the defined
minimum level
flashing to protection group p. 53 in this document.
off “standby” mode and
experiences loss of
input power - Power
the defined minimum
input.

on that pluggable
transceiver.

admin state is
disabled.

Name
supported by the
installed pluggable
by the channel
module.
Pluggable transceiver Consult your technical services representative about

is not approved by obtaining a pluggable transceiver approved by ADVA

valid signal, valid
hardware, no alarms
Standby mode.

Networking.

malfunctioning pluggable transceiver. Otherwise,
specification.
Power requirements.

Name
expired. attacks.
o
o
Pluggable transceiver Reinsert the pluggable transceiver.

was inserted and inter-
face provisioned, then
the pluggable trans-
ceiver was removed.
document.

available.
document.

document.

Name
N Yellow Optical Input Power 1 Measure the optical input power on the receiver
Power requirements.
below the defined
minimum level is
Key-exchange 1 Verify that s a network connection available.

attacks.
Module authentication 1 Check the module for any active or passive

password has failed or attacks.
is missing. 2 Check the authentication password settings.


Name
N Yellow off for ALS pulse received. Network link is not coming up.
document.
Off No Ch Interface 1 Provision a Ch Interface (Facility).


admin state is
disabled.
Off flashing The installed plug- Install the correct pluggable transceiver.
to red gable transceiver does
not match the pro-
visioned type. MEA-
ACCEPT condition is
raised.
The installed plug- Consult your Technical Services Representative

gable transceiver is about obtaining a pluggable transceiver approved by
not approved by ADVA Optical Networking.
ADVA Optical Net-
working - no traffic.
MEA-
APPROVE condition
is raised

valid signal, valid
hardware, no alarms
Green flash- The installed plug- Consult your technical services representative about
ing to red gable transceiver is obtaining a pluggable transceiver approved by ADVA
not approved by Optical Networking.
ADVA Optical Net-
working but is trans-
mitting traffic.
5TCE-PCTN-10GU+(AES)10G
This subsection addresses LED indications and troubleshooting guidelines for 5TCE-PCTN-10GU+10G and
5TCE-PCTN-10GU+AES10G modules, The modules are available in different variants that are described in the
PCTN-10GU+(AES)10G modules in a link are synchronized, the network link is up and the
the 5TCE-PCTN-10GU+(AES)10G module. For details on updating module firmware, refer to
Note on p. 628.
Note
Note
The 5TCE-PCTN-10GU+(AES)10G module supports configuring ‘disparity correction’. It is set

to “enabled” by default. For more information about this parameter, refer to the Management Data
Guide.
Note
Note
The 5TCE-PCTN-10GU+(AES)10G has eight LEDs on its faceplate:
• “C1”, “C2”, “C3”, “C4”, “C5” and “N” to indicate the interface status
This module has 5 client interfaces (C1 to C5). The LED status in Table 53 on p. 322 refers to the transmit
the module.
Note
Table 53: LED Status of the 5TCE-PCTN-10GU+(AES)10G

Name
initialization. If the condition persists, return the module to ADVA
Off Power failure
Mod Red Tamper event 1 Check for any visible damages to the module
occurred. cover.
2 If the module had been removed, reinsert it.
3 Check the temperature and voltage values of the
module.
Encryption Failure 1 Check the module for any active or passive

attacks.
3 If you are assigned as Crypto Officer adapt the
corresponding person configured as Crypto Officer
on this module.
channel card

password has failed or 2 If you are assigned as Crypto Officer adapt the
on this module.
Help.

Name
exchange process attacks.
has failed. 2 If there are no attacks and you are assigned as
on this module.
Module operates in 1 Check for any visible damages to the module

module.
as Crypto Officer adapt the module settings if
module.

blinking to off communication to the to the SCU firmware version as listed on the NCU.
module has failed. If they are different, update the SCU firmware as
described in “Performing Other Software Update
Representative.
Off Module admin state is • If the module is installed and provisioned, check
• If the management displays “disabled”, change the
admin state to “In Service”, “Management” or
“Maintenance”.
Module admin state is • If the management displays “unassigned”, check if

unassigned. the module is provisioned.
• If required provision the module

Name

admin state is
“Maintenance”,
Service”

then the pluggable
transceiver was
removed.
Tx Laser Failure If a replacement module is available, exchange the

malfunctioning pluggable transceiver. Otherwise return
the malfunctioning pluggable transceiver to ADVA
specification.
Power requirements.
synchronized.
connected.
3 Check optical power levels. Refer to “Finding Your
document.


Name
Power requirements.
below the defined
minimum level
experiences loss of
input power - Power
the defined minimum
input.

on that pluggable
transceiver.
4 Provision a Ch Interface (Facility) on the pluggable
transceiver.
Configure the Ch Interface (Facility) admin state to
“In Service”.

admin state is
disabled.

Name
supported by the
installed pluggable
by the channel
module.
Pluggable transceiver Consult your technical services representative about

is not approved by obtaining a pluggable transceiver approved by ADVA
Networking - no
traffic.

valid signal, valid
hardware, no alarms
Standby mode.

Networking.

malfunctioning pluggable transceiver. Otherwise return
the malfunctioning pluggable transceiver to ADVA
specification.
Power requirements.

Name
expired. attacks.
o
o
manually re-enable the key-exchange process
if appropriate.
document.
Loss of signal 1 Verify that there is a network connection available.

document.

document.
requirements.
below the defined
minimum level is

Name
N Yellow Key-exchange 1 Verify that there is a network connection available.

attacks.
on this module.

on this module.

document.

Configure the Ch Interface (Facility) admin state to
“In Service”.

Name
N Off Ch Interface (Facility) Change Ch Interface (Facility) admin state.

admin state is
disabled.

valid signal, valid
hardware, no alarms
5TCE-PCN-10GU+(AES)10G
This subsection addresses LED indications and troubleshooting guidelines for 5TCE-PCN-10GU+10G and
5TCE-PCN-10GU+AES10G modules, henceforth referred to as 5TCE-PCN-10GU+(AES)10G.
you could destroy the module being tested. As soon as the near-end and the far-end 5TCE-PCN-
10GU+(AES)10G modules in a link are synchronized, the network link is up and the network
the 5TCE-PCN-10GU+(AES)10G module. For details on updating module firmware, refer to
Note on p. 628.
Note
Note
The 5TCE-PCN-10GU+(AES)10G module supports configuring ‘disparity correction’. It is set to

Guide.
Note
Note
The 5TCE-PCN-10GU+(AES)10G has eight LEDs on its faceplate:
• Cx (x = 1 through 5) to indicate the status of the client interface
Note
Table 54: LED Status of the 5TCE-PCN-10GU+(AES)10G

Name
initialization. If the condition persists, return the module to ADVA
Optical Networking for repair
Off Power failure
attacks.
3 If you are assigned as Crypto Officer adapt the
Tamper event 1 Check for any visible damages to the module

occurred. cover.
module.
Yellow Communication Using NED, verify that the module AIDs for the
between channel protected modules are correct.
modules using client
channel card

password has failed or 2 If you are assigned as Crypto Officer adapt the
Help.

Name
exchange process has attacks.
failed. 2 If there are no attacks and you are assigned as
Module operates in 1 Check for any visible damages to the module

module.
as Crypto Officer adapt the module settings if
module.

Representative.
Off Module admin state is • If the module is installed and provisioned, check
• If the management displays “disabled”, change
“Maintenance”.
Module admin state is • If the management displays “unassigned”, check

• If required provision the module

Name

admin state is
“Maintenance”,
Service”

then the pluggable
transceiver was
removed.
Tx Laser Failure If a replacement module is available, exchange the

specification.
Power requirements.
synchronized.
connected.
document.


Name
Power requirements.
below the defined
minimum level
experiences loss of
input power - Power
the defined minimum
input.

on that pluggable
transceiver.

admin state is
disabled.
Off flashing Pluggable transceiver 1 Compare the supported data rates of the board
supported by the
installed pluggable
by the channel module.

Name
Cx Off flashing Pluggable transceiver Consult your technical services representative about
to red is not approved by obtaining a pluggable transceiver approved by ADVA

valid signal, valid
hardware, no alarms
Standby mode.

Networking.

specification.
Power requirements.
Session-key has 1 Check the module for any active or passive

expired. attacks.
o
o

Name
N Red Pluggable transceiver Reinsert the pluggable transceiver.

was inserted and
then the pluggable
transceiver was
removed.
document.

available.
document.

document.
requirements.
below the defined
minimum level is

Name
N Yellow Key-exchange process 1 Verify that there is a network connection

has failed. available.
2 Check the module for any active or passive
attacks.

Yellow First key was not yet No action is required.

document.


admin state is
disabled.

Name
N Off flashing The installed pluggable Install the correct pluggable transceiver.
to red transceiver does not
match the provisioned
type. MEA-ACCEPT
The installed pluggable Consult your Technical Services Representative

transceiver is not about obtaining a pluggable transceiver approved by
approved by ADVA ADVA Optical Networking.
Optical Networking -
no traffic. MEA-
APPROVE condition
is raised

valid signal, valid
hardware, no alarms
Green flash- The installed pluggable Consult your technical services representative about
ing to red transceiver is not obtaining a pluggable transceiver approved by ADVA
approved by ADVA Optical Networking.
Optical Networking but
is transmitting traffic.
8TCE-ESCON+2G5-V
This subsection will help you resolve issues that can be experienced on an 8TCE-ESCON+2G5-V module.
It assumes that all measurements for the Cx/R, Cx/T, N/R and N/T interfaces are within ADVA Optical Networking specifications and that you have verified that the
application wavelength is the same as the wavelength for the FSP 3000R7 module’s client interfaces. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in
this document.
Follow the instructions precisely. If you do not supply the specified attenuation on given steps, you could destroy the module being tested. As soon as the
near-end and the far-end 8TCE-ESCON+2G5-V modules in a link are synchronized the network link is up.
CAUTION
Before you start with troubleshooting, ensure that the current firmware package is installed on the 8TCE-ESCON+2G5-V module. For details on updating
Note
Note
Representative.
Note
LEDs.
The 8TCE-ESCON+2G5-V provides twenty LEDs on the faceplate:

• “C1/T”, “C2/T”, “C3/T”, “C4/T”, “C5/T”, “C6/T”, “C7/T”, “C8/T”, “C1/R”, “C2/R”, “C3/R”, “C4/R”, “C5/R”, “C6/R”, “C7/R”, “C8/R” “N/T” and “N/R” to indicate the interface
status
Table 55: LED Status of the 8TCE-ESCON+2G5-V
Red Off Off Off Off Off Module is broken. Return the module to ADVA Optical Networking for repair.
Green Red Off Off Off Off A temporary setting is If the condition continues once the module has lost and
blinking enabled on the module. regained power or all loops and transmitters have been
Manually disable turned off, it should be returned to ADVA Optical Networking
setting or reset module for repair.
in the frame. Note - The module should lose power for at least 10 sec. to
allow any and all capacitance to dissipate.
Green Red Green Green Yellow Yellow Client Loop is set. Disable the Loop.
blinking
Green Off Green Off Green blinks Attempting • If all power measurements are in specification on both
Green unsuccessfully to sides of the link, then it is possible that the network
every 10 establish network link. receiver of one of the modules is damaged. With a 20 dB
seconds attenuated patch cable, loop N/T to N/R.
• If the N/R and Cx/R LEDs do not illuminate once the
module is damaged and return it to ADVA Optical
• If N/R and Cx/T illuminate, repeat the test on the other
side of the link.
the test above, you will destroy the tested module.
Green Off Yellow Off Green Green Data received from a client interface, but incoming data rate does not match the
supported data rates.
Green Off Off Green Green Green The module is seeing You have probably swapped your transmit and receive
an application signal connections to the application. Exchange Cx/T and Cx/R
only on the network connectors on the interface in question.
side of the link.
Green Off Green Off Green Green Although the module Exchange Cx/T and Cx/R connectors on the interface in
see an application question on the other side of the link.
signal coming from the
client side, it does not
see one coming from
the network side.
Green Red Green Green Green Green Network laser is forced Turn laser forced off.
blinking on.
Green Off Green Off Green Green Client interface is Enable client interface.
matches the set clock
frequency.
Green Off Yellow Off Green Green Client interface is Enable client interface and set the clock.
blinking disabled.
Data rate does not
match the set clock
frequency.
8TCE-GLINK+2G5-V
This subsection will help you resolve issues that can be experienced on an 8TCE-GLINK+2G5-V module.
It assumes that all measurements for the Cx/R, Cx/T, N/R and N/T interfaces are within ADVA Optical Networking specifications and that you have verified that the
application wavelength is the same as the wavelength for the FSP 3000R7 module’s client interfaces. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in
this document.
Follow the instructions precisely. If you do not supply the specified attenuation on given steps, you could destroy the module being tested. As soon as the
near-end and the far-end 8TCE-GLINK+2G5-V modules in a link are synchronized, the network link is up.
CAUTION
Before you start with troubleshooting, ensure that the current firmware package is installed on the 8TCE-GLINK+2G5-V module. For details on updating
Note
Note
Representative.
Note
LEDs.
The 8TCE-GLINK+2G5-V has twenty LEDs on the faceplate:

• “C1/T”, “C2/T”, “C3/T”, “C4/T”, “C5/T”, “C6/T”, “C7/T”, “C8/T”, “C1/R”, “C2/R”, “C3/R”, “C4/R”, “C5/R”, “C6/R”, “C7/R”, “C8/R” “N/T” and “N/R” to indicate the interface
status
Table 56: LED Status of the 8TCE-GLINK+2G5-V
Red Off Off Off Off Off Module is broken. Return the module to ADVA Optical Networking for repair.
Green Red Off Off Off Off A temporary setting is If the condition continues once the module has lost and
blinking enabled on the module. regained power or all loops and transmitters have been
Manually disable setting or turned off, it should be returned to ADVA Optical Networking
reset module in the frame. for repair.
Note - The module should lose power for at least 10 sec. to
allow any and all capacitance to dissipate.
Green Red Green Green Yellow Yellow Client Loop is set. Disable the Loop.
blinking
Green Off Green Off Green blinks Attempting unsuccessfully • If all power measurements are in specification on both
Green to establish network link. sides of the link, then it is possible that the network
every 10 receiver of one of the modules is damaged. With a 20 dB
seconds attenuated patch cable, loop N/T to N/R.
• If the N/R and Cx/R LEDs do not illuminate once the
module is damaged and return it to ADVA Optical
• If N/R and Cx/T illuminate, repeat the test on the other
side of the link.
the test above, you will destroy the tested module.
Green Off Yellow Off Green Green Data received from a client interface, but incoming data rate does not match the supported
data rates.
Green Off Off Green Green Green The module is seeing an You have probably swapped your transmit and receive
application signal only on the connections to the application. Exchange Cx/T and Cx/R
network side of the link. connectors on the interface in question.
Green Off Green Off Green Green Although the module see an Exchange Cx/T and Cx/R connectors on the interface in
application signal coming question on the other side of the link.
from the client side, it does
not see one coming from the
network side.
Green Red Green Green Green Green Network laser is forced on. Turn laser forced off.
blinking
Green Off Green Off Green Green Client interface is disabled. Enable client interface.
blinking Data rate matches the set
clock frequency.
Green Off Yellow Off Green Green Client interface is disabled. Enable client interface and set the clock.
blinking Data rate does not match the
set clock frequency.
10TCE-PCN-10G+100G(-GF)
This subsection will help you resolve issues that can be experienced on a 10TCE-PCN-10G+100G-GF and
10TCE-PCN-10G+100G module, in the following referred to as 10TCE-PCN-10G+100G(-GF).
FSP 3000R7 module’s client interfaces. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this
document.
PCN-10G+100G(-GF) modules in a link are synchronized, the network link is up, and the
the 10TCE-PCN-10G+100G(-GF) module. For details on updating module firmware, refer to
Note on p. 628.
Note
CAUTION
Note
The 10TCE-PCN-10G+100G(-GF) has 13 LEDs on its faceplate:
• “Cx” (x = 1 through 10) to indicate the status of the client interface
This module has 10 client interfaces (C1 to C10). The LED status in Table 57 on p. 348 will refer to the transmit
the module.
The module should lose power for at least 10 seconds to allow any and all capacitance to
dissipate before it is reinserted.
Note
Table 57: LED Status of the 10TCE-PCN-10G+100G(-GF)

Name Colors
condition continues, the module should
P Yellow Power is abnormal. be returned to ADVA Optical Networking
Mod Yellow Management communication to the 1 Check the SCU firmware version
blinking to module has failed. and compare it to the SCU firmware
off version as listed on the NCU. If they
firmware as described in “Performing
Other Software Update Actions” on
p. 628.
states and what they mean, refer to
the System Description,
Management chapter.
Module admin state is unassigned. 1 If the management displays “UAS”

(unassigned), check if the module is
provisioned.
Green Module is provisioned, admin state No action is required.

is set to “Maintenance”,
“Management” or “In Service”
Cx Red SFP transceiver was inserted and Reinsert the SFP transceiver module.
interface provisioned, then the SFP
transceiver was removed.

Name Colors
Cx Yellow Loss of clock 1 Verify that the provisioned service

type.
document.
Loss of character synchronization Unable to synchronize on the characters

connected properly.
2 Check that the data rate and
protocol matches.

connected.
the procedure, “Finding Your
in this document.
receiver connector.
the SFP transceiver module input
power specification.
fulfill the SFP transceiver Optical
minimum level detected at the
input.

Name Colors
Cx Yellow Loss of output power - Power non- Refer to “Finding Your Problem - Follow
output.
(Normally a consequence of loss of
optical input power. Also may be
due to failure/degeneration of an
internal component or splice.)
Off SFP transceiver module mismatch: 1 Compare the supported data rates of
flashing to Features of the installed SFP the 10TCE-PCN-10G+100G(-
red transceiver module, e.g. data rates, GF)with the SFP transceiver module
do not match with the channel data rates.
module. 2 Install the correct SFP transceiver
module.
SFP transceiver is not approved by Consult your Technical Services

ADVA Optical Networking - no Representative about obtaining a SFP
traffic transceiver module approved by ADVA
Optical Networking.
Off The SFP transceiver module has 1 Install an appropriate SFP

not been provisioned or is not transceiver module.
installed. 2 Provision the SFP transceiver
module.
3 Enable the SFP transceiver module
admin state: If the admin state is set
to “Disabled”, change it to “In
“Maintenance”. For information when
to use these admin states and what
they mean, refer to the System
Description, “Management” chapter.
client facility.
admin state”.

Name Colors
Cx Off The client channel (facility) admin Change the client channel (facility)
chapter.


type.


connected.
the appropriate attenuators) to fulfill
the Optical Input Power
requirements.

Name Colors
N Yellow Loss of frame - No 1 Verify that the provisioned service

frame sync detected type matches the incoming signal
type.
input.
Off The CFP transceiver module has 1 Install an appropriate CFP

not been provisioned or is not transceiver module.
installed. 2 Provision the CFP transceiver
module.
admin state: If the admin state is set
to “Disabled”, change it to “In
“Maintenance”. For information when
to use these admin states and what
they mean, refer to the System
Description, “Management” chapter.
client facility.
admin state”.
The network channel (facility) Change the client channel (facility)

admin state is disabled. admin state: If the admin state is set to
chapter.

10TCE-PCN-16GU+(AES)100G and 10TCE-PCN-

16GU+AES100G-BSI
This subsection provides LED troubleshooting guidelines for 10TCE-PCN-16GU+100G, 10TCE-PCN-
16GU+AES100G, and 10TCE-PCN-16GU+AES100G-BSI modules. 10TCE-PCN-16GU+100G and 10TCE-
PCN-16GU+AES100G modules are hereafter referred to as 10TCE-PCN-16GU+(AES)100G.
Only Service Personnel who is security-cleared may do troubleshooting on 10TCE-PCN-

16GU+AES100G-BSI modules.
Note
This section assumes that all measurements for the client and network interfaces are within ADVA Optical
wavelength for the FSP 3000R7 module client interfaces. If not, refer to “Finding Your Problem - Follow the Light”
Follow these instructions precisely. If you do not supply the specified attenuation where
required, you could damage the module. As soon as the near-end and the far-end 10TCE-PCN-
16GU+(AES)100G or 10TCE-PCN-16GU+AES100G-BSI modules in a link are synchronized,
CAUTION the network link is operating, and the network interface LED is solid green.
the 10TCE-PCN-16GU+(AES)100G or 10TCE-PCN-16GU+AES100G-BSI module. For details
on updating module firmware, refer to “Updating the NE Software Release” on p. 617 and
Note “Performing Other Software Update Actions” on p. 628.
Before you start with troubleshooting, ensure that the admin status of the affected module is set
to “Maintenance.”
Note
The use of pluggable transceivers other than those approved by ADVA Optical Networking
results in loss of safety approval for the FSP 3000R7. Pluggable transceivers not approved by
ADVA Optical Networking do not function properly. Depending on the channel module type, Rx
and Tx of the affected interfaces may be disabled automatically. Approved pluggable
CAUTION
transceivers are required for the proper operation of the channel modules.
If your module shows an LED status that is not represented in Table 58 on p. 354, please contact
Note
Each 10TCE-PCN-16GU+(AES)100G or 10TCE-PCN-16GU+AES100G-BSI module has 16 LEDs on its

faceplate:
• For 10G operation, “Cx” (x = 1 through 10) to indicate the status of the client interface
status of the respective OTL. Similarly, when C6 through C9 are used for 40G operation, "C6" indicates the
logical "OR" of the C6C9 40G client interface status and the C6 OTL physical layer status, while "C7"
through "C9" indicate the physical layer status of the respective OTL.
status of the respective OTL.
• “N”, "N2", "N3", and "N4" to indicate the status of the network interface, hereafter referred to as "Nx."
In Table 58, Cx refers to the transmit connector and receive connector of a client interface, while Nx refers to the
transmit connector and receive connector of a network interface, based on the following usage:
• The LEDs N2, N3, and N4 remain switched off if the CFP has a single interface (for example, LR10). The
optical lanes are internally multiplexed/demultiplexed. In this case, only the N LED indicates the status of the
network interface.
• All network LEDs (N, N2, N3, and N4) are used if the CFP does not have an integrated
multiplexer/demultiplexer and supports four independent interfaces (for example, DWDM CFP).
Note
Table 58: LED Status of the 10TCE-PCN-16GU+(AES)100G and 10TCE-PCN-16GU+AES100G-BSI

Name
All LEDs Red A serious error in card initialization. Remove and reinsert the module. If
the condition persists, return the

Name
Mod Red Encryption-related failure1 1 Check the module for any active
(Self test failure) or passive attacks.
2 Check the module settings such
as authentication password,
temperature, and voltage
values.
3 If you are assigned as Crypto
Officer, adapt the settings, as
required. Otherwise, consult the
Crypto Officer assigned to this
module.
4 The Crypto-Officer should
restart the tests. If they still fail,
the module must be replaced.
For more information about the
module settings, refer to the
Network Element Director Online
Help.
Self test tamper event occurred2. 1 Check for any visible damage to
the module cover.
2 If the module had been
removed, reinsert it.
3 Check the temperature and
voltage values of the module.
Yellow Communication failure between chan- Using NED, verify that the module
nel modules that use client channel AID values for the protected mod-
card protection. ules are correct.
Crypto Officer password is missing 1 Check the Crypto Officer

or has failed1. settings.
(CO access locked for 10 minutes 2 If you are assigned as Crypto
because of wrong crypto-officer Officer, adapt the settings, as
password) required. Otherwise, consult the
module.
For more information about
configuring the Crypto Officer, refer
to the Network Element Director
Online Help.
1Only in 10TCE-PCN-16GU+AES100G and 10TCE-PCN-16GU+AES100G-BSI.


Name
Mod Yellow Self tests or key-exchange process 1 Check the module for any active
has failed1. or passive attacks.
2 If there are no attacks, and you
are assigned as Crypto Officer,
manually re-enable the key-
exchange process. Otherwise,
consult the Crypto Officer
assigned to this module.
3 The Crypto Officer can execute
self-test. This is service-
affecting!
Help.
Module operates in “degraded” 1 Check for any visible damage to

mode1. the module cover.
2 If the module had been
removed, reinsert it.
3 Check the temperature and
voltage values of the module.
4 If the LED behavior persists,
and you are assigned as Crypto
Officer, adapt the module
settings, as required.
Otherwise, consult the Crypto
Officer assigned to this module.
Help.
The module battery is low. The Replace the module during the next
module will continue to operate, but maintenance window.
passwords may not be backed up in
case of a power outage2.

2Only in 10TCE-PCN-16GU+AES100G-BSI.

Name
Mod Yellow blinking to Management communication to the 1 Check the SCU firmware
off module has failed. version, and compare it to the
SCU firmware version as listed
on the NCU. If they are
different, update the SCU
firmware, as described in
“Performing Other Software
If the LED is still blinking yellow to
off, contact your ADVA Optical
Representative.

provisioned, check the
administrative state settings.
2 If the module administrative
state is set to “Disabled,”
change it to “In Service,”
“Management,” or
“Maintenance.” For information
about the administrative states,

“UAS” (unassigned), check
whether the module is
provisioned.
2 If required, provision the
module.
Green Module is provisioned, admin state is No action is required.

set to “Maintenance,” “Management,”
or “In Service.”

and the interface provisioned, but
then the pluggable transceiver was
removed.

Name
Cx Yellow Laser failure If a replacement module is available,

exchange the malfunctioning plug-
gable transceiver. Otherwise, return
the malfunctioning pluggable trans-
ceiver to ADVA Optical Networking
for repair.
Loss of clock If a 40G client is active on C1C4

(or C6C9) and C1 (or C6) is
yellow, first troubleshoot any
"loss of clock" failures indicated
by the other Cx LEDs associated
with this 40G client.
Similarly, if a 100G client is active
on C1C10 and C1 is yellow, first
troubleshoot any "loss of
clock" failures indicated by the
other Cx LEDs.
1 Verify that the provisioned
service type matches the
incoming signal type.
procedure, “Finding Your
Problem - Follow the Light” on

Name
Cx Yellow Loss of signal If a 40G client is active on C1C4

(or C6C9) and C1 (or C6) is
"loss of signal" failures indicated
by the other Cx LEDs associated
with this 40G client.
troubleshoot any "loss of
signal" failures indicated by the
other Cx LEDs.
connected.
2 If a filter cable1 or a breakout
cable2 is connected to this port
for 40G/100G operation, ensure
that the filter/breakout cable is
properly connected to the
40G/100G signal source.
3 Check optical power levels.
Refer to the procedure, “Finding
Your Problem - Follow the Light”
1J/SM/4CS-#C1270-#C1330/LC/0400
2J/MM50/MPO12-LC08/0300 or J/MM50/MPO12-LC08/1000 for 40G operation and J/MM50/MPO24-LC20/0300
or J/MM50/MPO24-LC20/1000 for 100G operation.

Name
Cx Yellow Optical Input Power out of range If a 40G client is active on C1C4
(or C6C9) AND C1 (or C6) is
"optical input power out of
range" failures indicated by the
other Cx LEDs associated with
this 40G client.
troubleshoot any "optical input
power out of range" failures
indicated by the other Cx LEDs.
1 Measure the optical input power
on receiver connector.
2 Compare the measured value
with the pluggable transceiver
module input power
specification.
(i.e., install the appropriate
attenuators) to fulfill the
pluggable transceiver optical
input power requirements.
Loss of output power - Power non- If a 40G client is active on C1C4

existing or below the defined (or C6C9) and C1 (or C6) is
minimum level is detected at the yellow, first troubleshoot any
output. "loss of output power" failures
(Normally a consequence of loss of indicated by the other Cx LEDs
optical input power. Also may be due associated with this 40G client.
to failure/degeneration of an internal Similarly, if a 100G client is active
component or splice.) on C1C10 and C1 is yellow, first
troubleshoot any "loss of output
power" failures indicated by the
other Cx LEDs.

document.

Name
Cx Yellow flashing In a client channel card protection Refer to “Finding Your Problem - Fol-
(10G to off configuration, the protection path cor- low the Light” on p. 53 in this doc-
operation) responding to this standby port is ument.
unavailable.
C1, C6
(40G
operation)
C1
(100G
operation)
Cx Off flashing to The installed pluggable transceiver 1 Compare the supported data
red does not match the provisioned type. rates of the module with the
MEA-ACCEPT condition is raised. pluggable transceiver data
rates.
2 Install the correct pluggable
transceiver.
The installed pluggable transceiver is Contact your Technical Services

not approved by ADVA Optical Representative to obtain a pluggable
Networking - no traffic. MEA- transceiver approved by ADVA
APPROVE and MEA-PHYS Optical Networking.
conditions are raised.
Off No channel interface (facility) 1 Install an appropriate pluggable

provisioned on the pluggable transceiver module.
transceiver.
3 Enable the administrative state:
If the administrative state is set
to “Disabled,” change it to “In
Service,” “Management,” or
about administrative states,
4 Provision a channel interface
(facility) on the pluggable
transceiver.
5 Enable the client channel
(facility) administrative state.
Channel interface (facility) admin Change channel interface (facility)

state is disabled. admin state.

Name
Cx Off The installed pluggable transceiver Install the correct pluggable trans-
does not meet one or more pro- ceiver.
visioned physical layer properties,
wavelength. MEA-PHYS condition is
raised.
Cx Green flashing to In a client channel card protection No action is required.

(10G off configuration, this standby port is
traffic) operating error-free. Therefore, the
C1, C6 traffic.
(40G
traffic)
C1
(100G
operation)
Cx Green Interface is active, with a valid No action is required.

signal, valid hardware, and no
alarms.
N Red Pluggable transceiver was inserted Reinsert the pluggable transceiver.

(N2, N3, and N4 and the interface provisioned, but
are Off) then the pluggable transceiver was
removed.

Name
N Red Session-key lifetime has expired1. 1 Check the module for any active
or passive attacks.
2 Check the module settings,
such as authentication
password, temperature, and
voltage values.
Officer,
o
adapt the module settings,
as required.
o
exchange process, as
required.
Otherwise, consult the Crypto
Officer assigned to this module.
Help.
GHash failure alarm 2 ("Tag Error 1 Check the module for any active
Limit Reached")2, or passive attacks.
Traffic is interrupted. 2 Once any security breach is
resolved, the Crypto Officer
needs to reset the Tag Errors
counter to enable data traffic
again.
Nx Yellow Laser failure If a replacement module is available,

exchange the malfunctioning plug-
gable transceiver. Otherwise, return
the malfunctioning pluggable trans-
ceiver to ADVA Optical Networking
for repair.


Name
Nx Yellow Loss of clock 1 Verify that the provisioned

service type matches the
measurements. Refer to
“Finding Your Problem - Follow
the Light” on p. 53 in this
document.

connected.
2 Check optical power levels.
document.
Optical Input Power out of range 1 Measure the optical input power
on the receiver connector.
2 Compare the measured value
with the channel
specification.
(i.e., the appropriate
attenuators) to fulfill the optical
input power requirements.
Loss of frame - No 1 Verify that the provisioned

frame sync detected service type matches the
measurements. Refer to
“Finding Your Problem - Follow
the Light” on p. 53 in this
document.
Loss of output power - Power non- Refer to “Finding Your Problem - Fol-
existing or below the defined min- low the Light” on p. 53 in this doc-
imum level is detected at the output. ument.
Normally a consequence of loss of
optical input power. Also may be due
to failure/degeneration of an internal
component or splice.

Name
N Yellow Key-exchange process has failed1. 1 Verify that a network connection

is available.
2 Check the module for any active
or passive attacks.
3 If there are no attacks and you
are assigned as Crypto Officer,
exchange process. Otherwise,
consult the Crypto Officer
assigned to this module.
Help.
Key-exchange inband channel is 1 Verify that a network connection

unavailable2. is available.
2 Check the configuration for
inband communication (used
TCM byte).
3 Check the module for any active
or passive attacks.
Module runs in transparent (bypass) If you are assigned as Crypto

mode; no data encryption3. Officer, set the module back to
encryption mode or consult the
Crypto Officer assigned to this mod-
ule. For more information, refer to
the Network Element Director
Online Help.

3Only in 10TCE-PCN-16GU+AES100G.

Name
N Yellow Module authentication password has 1 Check the module for any active
failed or is missing1,2. or passive attacks.
2 Check the authentication
password settings.
Officer, adapt the settings, as
required. Otherwise, consult the
module.
Help.
First key was not yet exchanged No action is required.

after a module cold restart2.
GHash failure alarm 1 ("Tag Error"), 1 Check the module for any active
A single tag error occurred1. or passive attacks.
2 Once any security breach is
resolved, the Crypto Officer
may reset the Tag Errors
counter, or single tag error will
be cleared automatically when
the line is error-free.
N2, N3, Off The corresponding CFP has a single If the associated CFP has a single
and N4 (N not Off) interface (for example, LR10), is not interface, no action is required.
installed, or is not approved. Please refer to the explanation per-
taining to network LEDs earlier in
this section.

Name
Nx Off The CFP transceiver module has not 1 Install an appropriate CFP
been provisioned or is not installed. transceiver module.
2 Provision the CFP transceiver
module.
3 Enable the CFP transceiver
module admin state: If the
admin state is set to “Disabled,”
change it to “In Service,”
“Management,” or
about admin states, refer to the
System Description,
4 Provision a channel interface on
the client facility.
5 Enable the client channel
(facility) admin state.
The network channel (facility) admin Change the client channel (facility)
state is disabled. admin state: If the admin state is set
to “Disabled,” change it to “In
Service,” “Management,” or
about admin states, refer to the
chapter.
The installed pluggable transceiver Install the correct pluggable trans-

does not meet one or more pro- ceiver.
visioned physical layer properties
such as data rate, reach,or
wavelength. MEA-PHYS condition is
raised.
N Off flashing to The installed pluggable transceiver Install the correct pluggable trans-
red does not match the provisioned type. ceiver.
MEA-ACCEPT condition is raised.
The installed pluggable transceiver is Contact your Technical Services

not approved by ADVA Optical Representative to obtain a pluggable
Networking - no traffic. MEA- transceiver approved by ADVA
APPROVE and MEA-PHYS Optical Networking.
Nx Green Interface is active, with a valid No action is required.

signal, valid hardware, and no
alarms.
Troubleshooting Enterprise Type WDM Channel Modules
Troubleshooting Enterprise Type WDM Channel

Modules
This section will help you resolve issues that can be experienced on WDM enterprise
channel modules. One very important difference between the Single Application and
WDM enterprise channel modules is that the Single Application modules require that an
application signal be present before it attempts to establish a network link. The WDM
enterprise channel modules, however, will attempt to establish the network link
immediately upon power on. This leads to slight differences in what you could expect to
see as normal LED states.
The LEDs are located on the faceplate of every WDM enterprise channel module.
The following subsection identifies and resolves issues of:
“WCE-PCN-100G(B)” on p. 369
“4WCE-PCN-16GFC” on p. 377
WCE-PCN-100G(B)
This section addresses LED indicators and troubleshooting guidelines for WCE-PCN-100G and WCE-PCN-
100GB modules, in the following referred to as WCE-PCN-100G.
FSP 3000R7 module’s client interfaces. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this
document.
you could destroy the module being tested. As soon as the near-end and the far-end WCE-PCN-
100G modules in a link are synchronized, the network link is up, and the network interface LED
CAUTION will light up solid green.
the WCE-PCN-100G module. For details on updating module firmware, refer to “Updating the
Note
Note
CAUTION
Note
The WCE-PCN-100G has four LEDs on its faceplate:
• “C” to indicate the status of the client interface
Note
Table 59: LED Status of the WCE-PCN-100G

Name
Off Power failure
Mod Yellow Management communication to 1 Check the SCU firmware version and
blinking to off the module has failed. compare it to the SCU firmware version
as listed on the NCU. If they are
Off Module admin state is disabled. 1 In the case that the module is installed
and provisioned, check the admin state
settings.
System Description, Management
chapter.
Module admin state is 1 If the management system displays

unassigned. “UAS” (unassigned), check if the module
is provisioned.
Green Module is provisioned, admin No action is required.

state is set to “Maintenance”,
C Red CFP transceiver was inserted Reinsert the CFP transceiver module.
and interface provisioned, then
the CFP transceiver was
removed.

Name
C Red Pin max too high, receiver 1 Measure the optical input power on the
damage threshold exceeded. receiver connector and compare the
measured value with the CFP
transceiver module input power
specification.
CFP transceiver Optical Input Power
requirements.
Yellow Loss of Clock 1 Verify that the provisioned service type

this document.

location, refer to the troubleshooting
instructions for the relevant signal degrade
condition outlined in Alarm and Event List.
Loss of character Unable to synchronize on the characters in

synchronization the incoming data stream.
1 Verify that fiber cables are connected
properly.
2 Check that the data rate and protocol
matches.

document.

Name
C Yellow Loss of lane 1 Inspect the physical cable associated

with this port and clean the fiber
connections as needed. Replace the
cable assembly if required.
2 Verify that each optical span along the
path taken by the multi-lane channel
signal conforms to the engineering
specifications for the link, especially that
each link conforms to the specified PMD
limitations.
compensation entity along the path of the
multi-lane channel signal conforms to the
engineering requirements.
4 If the condition persists, replace the far-
end module.
associated module.
Optical Input Power out of 1 Measure the optical input power on

CFP transceiver module input power
specification.
CFP transceiver Optical Input Power
requirements.
Loss of input power - Power Refer to “Finding Your Problem - Follow the
non-existing or below the Light” on p. 53 in this document.
defined minimum level
Loss of output power - Power

non-existing or below the
(Normally a consequence of
Also may be due to
internal component or splice.)

Name
C Yellow flash- In a client channel card pro- Refer to “Finding Your Problem - Follow the
ing to off tection configuration, the Light” on p. 53 in this document.
standby port is not capable of
taking over the traffic as an
error is present.
Off The CFP transceiver module 1 Install an appropriate CFP transceiver

has not been provisioned or is module.
not installed. 2 Provision the CFP transceiver module.
chapter.
client facility.
state as described below in ”Change the
client channel (facility) admin state”.
The client channel (facility) Change the client channel (facility) admin
admin state is disabled. state: If the admin state is set to “Disabled”,
change it to “In Service”, “Management” or
“Maintenance”. For information when to use
these admin states and what they mean,
Off flashing to CFP transceiver module 1 Compare the supported data rates of the
red mismatch: Features of the WCE-PCN-100G with the CFP
installed CFP transceiver transceiver module data rates.
module do not match with the 2 Install the correct CFP transceiver
channel module. module.
Installed CFP transceiver Consult your Technical Services

module is not approved by Representative about obtaining a CFP
ADVA Optical Networking - no transceiver module approved by ADVA

Name
C Green flashing In a client channel card pro- No action is required.

to off tection configuration, this
standby port is operating error-
free. Hence the interface is cap-
able of taking over the traffic.

N Red CFP transceiver was inserted Reinsert the CFP transceiver module.
and interface provisioned, then
the CFP transceiver was
removed.
measured value with the CFP
transceiver module specification.


location, refer to the troubleshooting
instructions for the relevant signal degrade
condition outlined in Alarm and Event List.


Name
N Yellow Loss of lane 1 Inspect the physical cable associated

with this port and clean the fiber
connections as needed. Replace the
cable assembly if required.
2 Verify that each optical span along the
path taken by the multi-lane channel
signal conforms to the engineering
specifications for the link, especially that
each link conforms to the specified PMD
limitations.
compensation entity along the path of the
multi-lane channel signal conforms to the
engineering requirements.
4 If the condition persists, replace the far-
end module.
associated module.
specification.
appropriate attenuators) to fulfill the
Loss of frame - No frame sync Check optical power measurements. Refer to

detected “Finding Your Problem - Follow the Light” on

Name
N Yellow Loss of output power - Power Refer to “Finding Your Problem - Follow the
Normally a consequence of
Also may be due to
Off The CFP transceiver module 1 Install an appropriate CFP transceiver

has not been provisioned or is module.
not installed. 2 Provision the CFP transceiver module.
chapter.
client facility.
state as described below in ”Change the
client channel (facility) admin state”.
The network channel (facility) Change the client channel (facility) admin
admin state is disabled. state: If the admin state is set to “Disabled”,
change it to “In Service”, “Management” or
“Maintenance”. For information when to use
these admin states and what they mean,

4WCE-PCN-16GFC
This subsection addresses LED indications and troubleshooting guidelines on 4WCE-PCN-16GFC modules.
It assumes that all measurements for the Cx and Nx interfaces are within ADVA Optical Networking
CAUTION
Before you start with troubleshooting, ensure that the newest firmware package is installed on
the 4WCE-PCN-16GFC module. For details on updating module firmware, refer to “Updating the
Note
Note
CAUTION
Note
The 4WCE-PCN-16GFC has ten LEDs on the faceplate:
• “C1”, “C2”, “C3”, “C4”, “N1”, “N2”, “N3” and “N4” to indicate the interface status
This module has 4 client interfaces (C1 to C4) and four network interfaces (N1 to N4). The LED status in Table 60
on p. 378 refers to one client interface (Cx) and one network interface (Nx) as example for all client and network
interfaces on the module.
Note
Table 60: LED Status of the 4WCE-PCN-16GFC

Name
Off Power failure
Mod Yellow Management communication 1 Check the SCU firmware version and
blinking to off to the module has failed. compare it to the SCU firmware version
as listed on the NCU. If they are
Off Module admin state is 1 In case the module is installed and

settings.
System Description, Management
chapter.
Module admin state is 1 If the management system displays

unassigned. “UAS” (unassigned), check if the
2 If required provision the module as
described in the Network Element


Name

removed.
Laser failure If a replacement module is available

specification.
requirements.
Yellow Loss of signal 1 Verify that fiber cables are connected.

specification.
requirements.

Name
Cx Yellow Loss of output power - Power Refer to “Finding Your Problem - Follow the
Also may be due to

3 Enable the admin state: If the admin
state is set to “Disabled”, change it to
“In Service”, “Management” or
“Maintenance”. For information when to
use these admin states and what they
mean, refer to the System Description,
Management chapter.
4 Provision a channel interface (facility)
admin state”.
Channel interface (facility) Change channel interface (facility) admin

admin state is disabled. state.

transceiver does not meet one
or more provisioned physical
layer properties, such as data
rate, reach, or wavelength.
MEA-PHYS condition is
raised.
Off flashing to The installed pluggable trans- Install the correct pluggable transceiver.
red ceiver does not match the pro-
visioned type. MEA-ACCEPT

Name
Cx Off flashing to The installed pluggable Consult your Technical Services

red transceiver is not approved by Representative about obtaining a pluggable
ADVA Optical Networking - transceiver approved by ADVA Optical
no traffic. MEA- Networking.
APPROVE and MEA-PHYS

alarms
Nx Red Pluggable transceiver was Reinsert the pluggable transceiver.

removed.
Yellow Laser failure If a replacement module is available

specification.
requirements.

specification.
requirements.

Name
Nx Yellow Loss of input power - Power Refer to “Finding Your Problem - Follow the
Loss of output power - Power

non-existing or below the
Also may be due to

Service”.
4 Provision a channel interface (facility)
5 Enable the channel interface (facility)
admin state - Configure the channel
interface (facility) admin state to “In
Service”.
Ch Interface (Facility) admin Change channel interface (facility) admin

state is disabled. state.

transceiver does not meet one
or more provisioned physical
layer properties such as data
rate, reach,or wavelength.
MEA-PHYS condition is
raised.
Off flashing to The installed pluggable trans- Install the correct pluggable transceiver.
red ceiver does not match the pro-
visioned type. MEA-ACCEPT

Name
Nx Off flashing to The installed pluggable Consult your Technical Services

red transceiver is not approved by Representative about obtaining a pluggable
ADVA Optical Networking - transceiver approved by ADVA Optical
no traffic. MEA- Networking.
APPROVE and MEA-PHYS

alarms.
Chapter 7
Management and Switch Modules

This chapter addresses all management and optical protection switch modules available
at the publication date of this manual.
“Troubleshooting Management Modules” on p. 386, which addresses LED indicators and
troubleshooting guidelines for management modules.
“Troubleshooting Switch Modules” on p. 414, which addresses LED indicators and
troubleshooting guidelines for switch modules.
Troubleshooting Management Modules

All management modules have LED indicators named “P” and “Mod” for the module
operation status. To identify the interface status, every management module provides its
own LEDs. These LEDs are located on the faceplate of the management modules.
The following subsections provide troubleshooting guidelines for:
“NCU” on p. 386
“NCU-II-P” on p. 392
“NCU-S” on p. 394
“SCU” on p. 396
“SCU-II” on p. 399
“SCU-S” on p. 401
“OSCM” on p. 403
“UTM and UTM-S” on p. 405
“PSCU” on p. 408
“CEM/9HU” on p. 411
NCU
This section describes the LED behavior of the NCU (NCU2E), and NCU-II. The LED
behavior is identical for these NCU types.
Figure 16: LED Indicators and Reset Button of the NCU (NCU2E)
Figure 17: LED Indicators and Reset Button of the NCU-II
Before starting with troubleshooting, ensure the correct software

package is installed on the NCU module. For more information about
updating the NE software, refer to “Updating the NE Software Release”
Note on p. 617.
Before starting with troubleshooting, ensure the admin state of the

affected module is set to “Maintenance”.
Note
Troubleshooting Serial Connection Issues

The following table provides troubleshooting guidelines for the most common problems
encountered when using the serial port.
Configuring an NCU IP address and setting up the serial interface take a few minutes to
complete. Additionally, it is assumed that you are familiar with IP addressing and basic
serial and Ethernet cabling.
Table 61: Troubleshooting Serial Connection Issues
Problem Potential Cause and Suggested Troubleshooting
When attempting to log This is a classic symptom of an improperly pinned cable.

in, the “login:” prompt is Use the cable that was shipped with the NCU.
visible, but the NCU Hint – the NCU requires a signal on pin 1 of the DB 9
does not seem to connector and many store-bought cables do not bring this
recognize anything you pin through.
type.
Table 61: Troubleshooting Serial Connection Issues
When pressing the Enter 1 Reboot the NCU to clear up any problems that could
key, you get useless lead to the situation and start with a fresh connection.
data (or garbage) as a For details on rebooting the NCU, please refer to “NCU
response. Troubleshooting” on p. 509.
2 If the symptom persists, check whether the serial port
on your PC is configured to the same settings as the
NCU serial port. The default configuration for the
NCUs serial port is 19200 baud, 8 bits, no parity bit,
one stop bit, no handshake.
3 If your PC is already configured to these settings, then
it is possible that the serial port may have been
changed to a different speed. Try all the allowed
speeds on your serial port, but reboot the NCU and
restart your PC communication program each time you
change the speed.
Invalid characters caused by the wrong baud rate can
sometimes confuse the serial port. This effect can be
seen in terminal emulation applications as well.
Additionally, please wait two minutes and check if the
serial port sends any characters even when nothing is
typed. If it does, see the next symptom.
Troubleshooting Ethernet Connection Issues

The following table provides troubleshooting guidelines for the most common problems
encountered when using an Ethernet connection.
Table 62: Troubleshooting Ethernet Connection Issues
The NCU does not If the link LED shows a valid Ethernet link, but the NCU does
respond to a ping. not respond to pings, then it is likely that the IP address is
different from the expected value. The default IP address of
the NCU is 192.168.1.1. Please verify that your PC is in the
same IP network as the NCU and the NCU IP address is the
expected value.
The NCU stops This is a common symptom of duplicate IP addresses.

responding to pings. Change the IP address of the NCU.
Troubleshooting NCU Configuration Issues

The following table provides troubleshooting guidelines for the most common NCU
configuration issues.
Table 63: Troubleshooting NCU Configuration Issues
Symptom Potential Cause and Solution for Troubleshooting
You forgot the Please refer to “NCU Troubleshooting” on p. 509 to reset the
password for the root NCU password.
account
You forgot the Log on as root using the serial interface and select User
password for any Management from System Security Management. User
account other than Management displays the user account for which you wish
root to change the password.
Traps are not being 1 View the list of all management stations that receive
received by all of the traps from this NE using the System Management >
trap recipients SNMP Configuration > Trap Recipients tab. For details
configured. on configuring SNMP settings, please refer to the
Provisioning and Operations Manual.
2 If the symptom persists, ensure the address entered is
correct.
3 If the symptom continues, it is also possible that there is
no route to the trap recipient. This can happen when the
trap recipient is in a network other than the NCU. Log on
to the NCU and attempt to ping the IP address of the trap
recipient. If you receive no response, the routing may be
incorrect.
4 If the ping works, then try an outbound or inbound telnet
from the trap recipient. It is possible that there is a
duplicate address on the network – either the NCU or the
trap recipient. A ping can sometimes work even when
addresses are duplicated.
Finally, please be advised that SNMP and the traps it sends
run over UDP. As UDP (User Datagram Protocol) is not
connection-oriented, it cannot be guaranteed that traps sent
will always be received. However, it is unlikely that any trap
recipient will receive none of the intended traps.
NCU LED Status

Note
The NCU has four LEDs on the faceplate:

• two LAN LEDs on every interface to indicate the interface status
Table 64: LED Status of the NCU
P Green The unit receives No action is required.

power. Power OK.
Red Module error. Return the NCU to ADVA Optical Networking.
Off Power source has An internal error condition has occurred.

failed. The NCU If the condition persists once the module has been
receives no power. removed and reinserted, return it to ADVA Optical
Networking.
Please note, the module should lose power for at
least 10 seconds to allow all capacitance to
dissipate.
Mod Green NCU is enabled. No action is required.
Green blinking NCU is starting up. No action is required.

When the NCU startup is complete, it emits 4
beeps and the LED is lit solid green. The NCU is
then available for management tasks.

unassigned or check if the NCU is provisioned in the
“disabled”. management.
• If the NCU is not provisioned, create the NCU.
upper LAN Green blinking Network line is No action is required.

Link LED established. Note: If the LAN interface is “disabled” (ADMIN
State = disabled), the LAN LED is still lit green.
Table 64: LED Status of the NCU
upper LAN Off There are three basic • The most common cause is a faulty or
Link LED causes of this incorrect cable. To establish a direct
symptom: connection from the NCU to a PC, use the
• The cable used is crossover-cable delivered with the NCU. To
faulty or incorrect. connect the NCU to a hub or switch, use a
straight-through cable. To check if the cable is
• The NCU reset
faulty, swap it with another of the same type.
button is
continuously • Check if the NCU reset button remains
depressed. continuously depressed. If the NCU does not
emit the normal 5 beeps and connecting a valid
• The PC or hub
interface to the RJ45 port does not cause the
connected to the
“Link” LED to illuminate, push a paper clip or
NCU is faulty.
other narrow object into the reset button once
and release. The button should return to its
normal state.
• Try using a different PC or a different interface
on the hub or switch.
lower LAN Green Network line is No action is required.

Link LED established. Note: If the LAN interface is “disabled” (ADMIN
State = disabled), the LAN LEDs is still lit green.
lower LAN Off There are three basic • The most common cause is a faulty or
Link LED causes of this incorrect cable. To establish a direct
symptom: connection from the NCU to a PC, use the
• The cable used is crossover-cable delivered with the NCU. To
faulty or incorrect. connect the NCU to a hub or switch, use a
straight-through cable. To check if the cable is
• The NCU reset
faulty, swap it with another of the same type.
button is
continuously • Check if the NCU reset button remains
depressed. continuously depressed. If the NCU does not
emit the normal 5 beeps and connecting a valid
• The PC or hub
interface to the RJ45 port does not cause the
connected to the
“Link” LED to illuminate, push a paper clip or
NCU is faulty.
other narrow object into the reset button once
and release. The button should return to its
normal state.
• Try using a different PC or a different interface
on the hub or switch.
NCU-II-P
Note
The NCU-II-P has three LEDs on the faceplate:

• “H/S” to indicate hot standby status of the module
Table 65: LED Status of the NCU-II-P

power. Power OK.
Red Module error. Return the NCU-II-P to ADVA Optical

Networking.

failed. The NCU-II-P If the condition continues once the module has
receives no power. been removed and reinserted, it should be
least 10 seconds to allow any and all
capacitance to dissipate
Mod Green NCU-II-P is enabled. No action is required.
Green blinking NCU-II-P is starting No action is required.

up. When the NCU-II-P is completely booted up, the
LED becomes solid and 4 beeps sound. The
NCU-II-P is then available for management
tasks.
Yellow N/A N/A

blinking
Off Module admin state • If the management displays “unassigned”,

is unassigned or check if the NCU-II-P is provisioned in the
Module admin state management.
is “disabled”. • If the NCU-II-P is not provisioned, create
the NCU-II-P.
Table 65: LED Status of the NCU-II-P
H/S Green Protection is • No action is required.

Primary provisioned, no • Primary module with backup module
related alarms. present and synchronized.
• Check status via user interface.
Green blinking Role change or No action is required.

to yellow graceful reboot in
progress.
Yellow Protection not Primary module present. Backup module not

available. present
or not synchronized.
• Check status via user interface
• Check that backup NCU-II-P is installed.
Red N/A N/A
H/S Green blinking Backup NCU-II-P • No action is required.

Backup to off ready to take over, • Backup module with primary module
no related alarms. present and synchronized.
• Check status via user interface using the
primary module.
Yellow blinking N/A N/A

to off
Off Module ADMIN • Spare module with/without primary module

State 'Disabled' present:
Module ADMIN o
if the primary module is present, check
State 'Unassigned” status via user interface using the
primary module,
o
if the primary module is absent, use the
serial connection + craft interface to
put it into operation.
• If the management displays “unassigned”,
check if the NCU-II-P is provisioned in the
management.
• If the NCU-II-P is not provisioned, create
the NCU-II-P.
NCU-S
Note
The NCU-S has six LEDs on the faceplate:

• “Mod” to indicate the module operating status
• two LAN LEDs per Ethernet port, one to indicate the link status and the other to indicate the traffic status.
The Ethernet ports are labeled "C1" and "D".
Table 66: LED Status of the NCU-S

power. Power OK.
Red Module error. Return the NCU-S to ADVA Optical Networking.

failed. The NCU-S If the condition continues once the module has
receives no power. been removed and reinserted, it should be returned
least 10 seconds to allow any and all capacitance
to dissipate
Mod Green NCU-S is enabled. No action is required.
Green blinking NCU-S is starting up. No action is required.

When the NCU-S startup is complete, the LED is
lit solid green and 4 beeps sound. The NCU-S is
then available for management tasks.

unassigned or Module check if the NCU-S is provisioned.
admin state is • If the NCU is not provisioned, create the NCU-
“disabled”. S.
Link status Green Link is established. No action is required.

for port C1
Link status Off The link cannot be • Ensure the correct cable is used.
for port C1 established due to one To establish a direct connection from the NCU-
of these reasons: S to a PC, use the crossover-cable delivered
• Faulty or incorrect with the NCU-S. To connect the NCU-S to a
cable. hub or switch, use a straight-through cable.
If the cable used is the correct type, swap it
• The NCU-S reset
with another cable of the same type to
button is pressed
determine if the cable is faulty.
continuously.
• Check if the NCU-S reset button remains
• The PC or hub
pressed.
connected to the
If the NCU does not emit the normal 5 beeps
NCU-S is faulty.
and connecting a valid interface to the RJ45
port does not cause the “Link” LED to
illuminate, then push a paper clip or other
narrow object into the reset button once and
release. The button should return to its normal
state.
• Use a different PC or interface on the hub or
switch.
Traffic Green blinking Traffic is received. No action is required.

status for
port C1 Off No signal is received. • Ensure the correct cable is used.
To establish a direct connection from the NCU-
S to a PC, use the crossover-cable delivered
with the NCU-S. To connect the NCU-S to a
hub or switch, use a straight-through cable.
If the cable used is the correct type, swap it
with another cable of the same type to
determine if the cable is faulty.
• Check if the NCU-S reset button remains
pressed.
If the NCU does not emit the normal 5 beeps
and connecting a valid interface to the RJ45
port does not cause the “Link” LED to
illuminate, then push a paper clip or other
narrow object into the reset button once and
release. The button should return to its normal
state.
• Use a different PC or interface on the hub or
switch.
Link status Green Link is established. No action is required.

for port D
Off • The cable • Check the fiber cable connection to the second
connecting this shelf.
NCU-S to the • Check the SCU in the second shelf.
second shelf is
faulty or incorrect.
• The SCU in the
second shelf is
faulty.
Traffic Green blinking Traffic is received. No action is required.

status for
port D Off • The cable • Check the fiber cable connection to the second
connecting this shelf.
NCU-S to the • Check the SCU in the second shelf.
second shelf is
faulty or incorrect.
• The SCU in the
second shelf is
faulty.
SCU
The SCU has eight LEDs on the faceplate:
• “U-R”, “D-R”, “X-R”, “U-T”, “D-T” and “X-T” to indicate the interface status.
the SCU module. For details on updating module firmware, refer to “Updating the NE Software
Release” on p. 617 and “Performing Other Software Update Actions” on p. 628.
Note
Before you start with troubleshooting, ensure that the administrative state of the affected module
is configured to “Maintenance”.
Note
CAUTION
Note
Table 67: LED Status of the SCU
All LEDs Red A serious error in Remove and reinsert the module.
card initialization. If the condition continues, return the module to ADVA
P Off Power source has Check the LED of the PSUs.

failed. The NCU • If the LED of the PSUs does not light up green,
receives no power. refer to “Troubleshooting Power Supply Units” on
p. 88.
• If the LED of the PSUs lights up green, a hardware
error of the SCU has occurred. Return the SCU to
Green Power OK No action is required.
Mod Red Hardware error. Remove and reinsert the module.

If the condition continues, the module should be
Please note, the module should lose power for at least
10 seconds to allow any and all capacitance to
dissipate.
Yellow Management 1 Check the fan unit LED behavior, in case all fan
blinking to off communication is unit LEDs are blinking yellow remove and insert
broken the SCU.
or 2 Check the fiber cable connection between the
Protection partner
SCUs, check the installed pluggable transceivers
communication fails.
for a proper working as well as a proper listing in
the management.
3 If the issue not resolved replace the SCU.
Off Module admin state • If the management displays “unassigned”, check if

is unassigned. the SCU is provided to the management.
• If the SCU is not provided, create the SCU.
Green Module is enabled; No action is required.

no alarms
Table 67: LED Status of the SCU
U-R, Red Pluggable Install the provisioned pluggable transceiver.

D-R, transceiver missing
X-R (when pluggable
(Rx) transceiver assigned/
necessary)
Off flashing Pluggable 1 Check the pluggable transceiver inventory in the

to red transceiver management.
mismatch/pluggable 2 Install an appropriate pluggable transceiver.
transceiver is not
approved by ADVA
Optical Networking
Yellow no signal connected Check the fiber cable connection between the SCUs.
Green Tx on, signal OK No action is required.
Off Power supply failure Replace the pluggable transceiver.

for pluggable
transceiver.
Interface admin state Enable the interface, configure the admin status to up.
“down”
U-T, Red Pluggable Install the provisioned pluggable transceiver.

D-T, transceiver missing
X-T (when pluggable
(Tx) transceiver assigned/
necessary)
Off flashing Pluggable 1 Check the pluggable transceiver inventory in the

to red transceiver management.
transceiver is not
approved by ADVA
Optical Networking
Yellow No output signal Check for faulty pluggable transceiver.
Green Link established No action is required.
Green No link, but light Replace the pluggable transceiver.

blinking to off
Off Power supply failure Enable the interface, configure the admin status to up.
for pluggable
transceiver.
SCU-II
The SCU-II has seven LEDs on the faceplate:
• H/S to indicate hot standby status of the module
• “U-R”, “U-T”, “D-T” and “D-R” to indicate the interface status.
the SCU-II module. For details on updating module firmware, refer to “Updating the NE Software
Note
Note
CAUTION
Note
Table 68: LED Status of the SCU-II
All LEDs Red A serious error in Remove and reinsert the module.
card initialization. If the condition continues, return the module to ADVA
P Off Power source has Check the LED of the PSUs.

failed. The NCU • If the LED of the PSUs does not light up green,
receives no power. refer to “Troubleshooting Power Supply Units” on
p. 88.
• If the LED of the PSUs lights up green, a
hardware error of the SCU-II has occurred.
Return the SCU-II to ADVA Optical Networking.
Green Power OK No action is required.

least 10 seconds to allow any and all capacitance to
dissipate.
Yellow blinking Management 1 Check the fan unit LED behavior, in case all fan
to off communication is unit LEDs are blinking yellow remove and insert
broken the SCU-II.
or 2 Check the fiber cable connection between the
Protection partner
SCU-IIs, check the installed pluggable
transceivers for a proper working as well as a
proper listing in the management.
3 If the issue not resolved replace the SCU-II.
Off Module admin state • If the management displays “unassigned”, check

is unassigned. if the SCU-II is provided to the management.
• If the SCU-II is not provided, create the SCU-II.
Green Module is enabled; No action is required.

no alarms
H/S Green Primary/Active No action is required.

module
Green blinking Backup / hot standby

to off module capable of
taking over.
Yellow flashing Backup / hot standby Replace module.

to off module incapable of
taking over
U-R, Red Pluggable Install the provisioned pluggable transceiver.

D-R transceiver missing
(when pluggable
transceiver
assigned/
necessary)
Off flashing to Pluggable 1 Check the pluggable transceiver inventory in the

red transceiver management.
transceiver is not
approved by ADVA
Optical Networking
Yellow no signal connected Check the fiber cable connection between the SCU-
IIs.
U-R, Green Tx on, signal OK No action is required.

D-R
Off Power supply failure Replace the pluggable transceiver.
for pluggable
transceiver.
Interface admin state Enable the interface, configure the admin status to
“down” up.
U-T, Red Pluggable Install the provisioned pluggable transceiver.

D-T transceiver missing
(when pluggable
transceiver
assigned/
necessary)
Off flashing to Pluggable 1 Check the pluggable transceiver inventory in the

red transceiver management.
transceiver is not
approved by ADVA
Optical Networking
Yellow No output signal Check for faulty pluggable transceiver.
Green Link established No action is required.
Green blinking No link, but light Replace the pluggable transceiver.

to off
Off Power supply failure

for pluggable
transceiver.
SCU-S
The SCU-S has two LEDs on the faceplate:
• “Mod” to indicate the operation status of the module.
the SCU-S module. For details on updating module firmware, refer to “Updating the NE Software
Note
Note
Note
The following table provides information about the LED status of the SCU-S.
Table 69: LED Status of the SCU-S
P None (Off) Power source has Check the LED of the PSUs.
failed. The NCU • If the LED of the PSUs does not light up
receives no power. green, refer to “Troubleshooting Power
Supply Units” on p. 88.
hardware error of the SCU-S has occurred.
Return the SCU-S to ADVA Optical
Networking.
Green Power OK. No action is required.

If the condition continues, the module should
be returned to ADVA Optical Networking for
repair.
Please note, the module should lose power for
at least 10 seconds to allow any and all
Yellow blinking Management 1 Check the fan unit LED behavior. If all fan
to off communication has unit LEDs are blinking yellow, remove and
broken off reinsert the SCU-S.
or 2 Check the cable connection between the
Protection partner
SCU-S modules.
3 If the issue not resolved, replace the SCU-
S.

unassigned. check if the SCU-S is provisioned to the
management.
• If the SCU-S is not provisioned, create the
SCU-S.
Green Module is enabled; no No action is required.

alarms
Table 69: LED Status of the SCU-S
UP Link LED Green blinking Network line is No action is required.

established.
None (Off) • The cable used is

faulty or incorrect
• The NCU
connected to the
SCU-S is bad.
DOWN Link Green Network line is No action is required.

LED established.
None (Off) • The cable used is

faulty or incorrect
• The NCU
connected to the
SCU-S is bad.
OSCM
This subsection will help you resolve issues that might be experienced with OSC modules. The following
variants are available:
OSCM-PN, OSCM-V#1630, 2OSCM-V#1630.
Troubleshooting an OSC module is only necessary in case of management or communication problems between
the nodes.
The OSCM-V#1630 has nine LEDs, while the 2OSCM-V#1630 and OSCM-PN each has ten LEDs on the
faceplate:
• “N”, (“NE” and “NW” at the 2OSCM-V#1630 and OSCM-PN) to indicate the operating status of the network
port (“NE” - network port east, “NW” - network port west)
• Two LAN LEDs per Ethernet port to indicate the interface status
This section assumes that all measurements for the N, NE, NW interfaces are within ADVA Optical Networking
specifications. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this document.
Table 70 on p. 404 provides troubleshooting guidelines for the OSCM based upon the LED states.
the OSC module. For details on updating module firmware, refer to “Updating the NE Software
Note
Note
Note
and Tx of the affected interfaces may be disabled automatically or not. Only approved Pluggable
CAUTION
Table 70: LED Status of the OSCM

Names
P Off Power source has failed. Check the PSU LEDs.

The OSCM receives no • If the PSU LEDs do not light up green,
power. refer to “Troubleshooting Power Supply
Units” on p. 88.
• If the PSU LEDs light up green, a
hardware error of the OSCM has occurred.
Replace the OSCM.
Mod Red Module major and critical Check the fault management table.
alarms
Yellow blinking Management com- 1 Check the SCU firmware version and
to off1 munication to the module compare it to the SCU firmware version as
has failed. listed on the NCU. If they are different,

alarms
Off Module admin state is • If the management displays “Unassigned”,

unassigned. check if the OSCM is provisioned in the
management.
• If the OSCM is not provisioned, create the
OSCM.
1This indication applies only to OSCM-PNv2 modules.
Table 70: LED Status of the OSCM

Names
N, NW, NE Red Laser transmitter error Replace the module.
Yellow Optical signal: loss of Check the fiber connection to the far-end
clock, loss of signal, input OSCM and measure the optical power.
power too high/low

signal, no maintenance
settings required
upper LAN Green blinking Ethernet packets are being No action is required.
interface received. Note: If the LAN interface is “disabled”
Link LED (ADMIN State = disabled) the LAN LEDs still
light up green.
Off No Ethernet packets are 1 Check the connected LAN cable.

being received. 2 Check the NCU-IP settings. Refer to
“Viewing IP Addresses” on p. 510.
lower LAN Green Ethernet link is established. No action is required.

interface Note: If the LAN interface is “disabled”
Link LED (ADMIN State = disabled) the LAN LEDs still
light up green.
Off Ethernet link is not 1 Check the connected LAN cable.

established. 2 Check the NCU-IP settings. Refer to
UTM and UTM-S

This subsection provides troubleshooting guidelines for Utility Modules (UTM and UTM-S).
UTM and UTM-S have the following LED indicators on their faceplates:
• 20 telemetry interface (TIF) contact LEDs labeled "1" through "20" (UTM only)
• Two LAN LEDs per Ethernet port to indicate the interface status (UTM only)
• 10 TIF contact LEDs, 5 labeled "Inputs" and 5 labeled "Outputs" (UTM-S only)
the UTM/UTM-S module. For details on updating module firmware, refer to “Updating the NE
Note
is set to “Maintenance”.
Note
Note
Table 71: LED Status of the UTM and UTM-S
P None (Off) Power source has failed. Check the PSU LEDs.
The UTM/UTM-S • If the PSU LEDs do not light up green,
receives no power. refer to “Troubleshooting Power Supply
Units” on p. 88.
• If the PSU LEDs are lit green, an
UTM/UTM-S hardware error occurred.
Replace the UTM/UTM-S. Return the
defective module to ADVA Optical
Networking.
Green Power ok. No action is required.
Mod Red Hardware Error Remove and reinsert the module.

If the condition continues, return the module to
Please note, the module should lose power for
at least 10 seconds to allow any and all
Yellow Management Remove and reinsert the UTM/UTM-S.

blinking to off communication is • If the LED is still blinking yellow to off,
broken. replace the UTM/UTM-S.
None (Off) Module admin state is • If the management displays

unassigned. “Unassigned”, check if the UTM/UTM-S is
provisioned in the management.
• If the UTM/UTM-S is not provisioned,
create the UTM/UTM-S.

alarms
Table 71: LED Status of the UTM and UTM-S
upper LAN Green blinking Network line is No action is required.

interface Link established. Ethernet
LED1 data are being received.
Off No Ethernet packages 1 Check the connected LAN cable. The

are being received. admin state is configured to “Disabled”.
Change the admin state to “In Service”.
2 Check the NCU-IP settings. Refer to
lower LAN Green Network line is No action is required.

interface Link established. Ethernet
LED1 data are being received.
Off No Ethernet packages 1 Check the connected LAN cable. The

are being received. admin state is configured to “Disabled”.
Change the admin state to “In Service”.
2 Check the NCU-IP settings. Refer to
Inputs (UTM-S) Yellow External alarm received. No action is required.

This triggers an audible Pressing the "Reset" button clears the audible
1 to 16 (UTM) alarm in the UTM-S. alarm in the UTM-S, though it does not affect
the LED or external alarm status.
Off No alarm received. No action is required.
Outputs (UTM- Yellow Telemetry contact is No action is required.

S) active. Pressing the "Reset" button clears the audible
This triggers an audible alarm in the UTM-S, though it does not affect
17 to 20 (UTM) alarm in the UTM-S. the LED or external alarm status.
Off No telemetry contact act- No action is required.

ive
1This LED is only applicable to the UTM.
PSCU
The Passive Shelf Control Unit (PSCU) has two kinds of tri-color LED indicators on the faceplate: two module
LEDs (labeled P and Mod) and eight interconnect port LEDs (labeled I1 through I8).
The LED colors represent different operating states. “P” indicates the power supply status, and “Mod” indicates
the operation status of the module. The colors of the interconnect port LEDs (one LED per interface) indicate
different states of the connected 40CSM/2HU-#Dxx-#Dyy shelves.
the PSCU module. For details on updating module firmware, refer to “Updating the NE Software
Note
Note
Note
Note
Table 72: LED Status of the PSCU
P Yellow Power abnormal Remove and reinsert the module.

None (Off) Power source has Check the LED of the PSUs.
failed. The PSCU • If the LED of the PSUs does not light up green,
receives no power. refer to “Troubleshooting Power Supply Units”
on p. 88.
hardware error of the PSCU has occurred.
Replace the PSCU. Return the defective
module to ADVA Optical Networking.
Green Power ok No action is required.
Mod Red Module alarm Remove and reinsert the module.

(critical/major If the condition continues, the module should be
equipment alarms) returned to ADVA Optical Networking for repair.
Yellow Management Remove and reinsert the PSCU.

blinking to off communication has • If the LED is still blinking yellow to off, replace
been cut off. The the PSCU.
connection has failed.
Representative.
None (Off) Module admin state is • If the management displays “unassigned”,

unassigned. check if the PSCU is provisioned in the
management.
• If the PSCU is not provisioned, create the
PSCU.
Green The module is No action is required.

operating properly
(Module is enabled
and not unassigned.)
Interconnect Red Passive shelf missing Verify that the fiber cables between the PSCU and
Ports I1 to I8 (when passive shelf are properly connected.
assigned/necessary)
Off flashing to Passive shelf Contact your ADVA Optical Networking Technical
red mismatch (MEA- Services Representative.
ACCEPT)
Yellow Power abnormal 1 Remove the passive shelf.

(short circuit or no 2 Remove and reinsert the module.
power draw although
3 If the condition continues, the module should be
shelf is connected)
4 If the condition disappears, the passive shelf
may generate a short circuit and should be
repaired.
Yellow Loss of 1 Verify that the fiber cables between the PSCU
blinking to off communication to and passive shelf are properly connected and
passive shelf check the optical power levels. Refer to the
(40CSM/2HU-#Dxx- procedure, “Finding Your Problem - Follow the
#Dyy) Light” on p. 53 of this document.
2 Check for a power abnormal alarm and refer to
the solution above.
Interconnect Green The connected No action is required.

Ports I1 to I8 passive shelf is
working properly.
None (Off) Port admin state is Check the admin state settings. If the management
disabled. displays “disabled”, change the admin state settings
to “In Service”, “Management” or “Maintenance”.
Port admin state is 1 If the management displays “unassigned”,

unassigned. check if the PSCU is provisioned in the
management.
2 If the module is not provisioned, create the
PSCU.
CEM/9HU
Aside from the shelf, slot and fan status LEDs as described in “Troubleshooting Shelves” on p. 60, the CEM/9HU
(Common Equipment Module) has 4 different types of LED indicators on the faceplate:
“Mod” to indicate the operating status of the module
20 telemetry interface (TIF) contact LEDs (labeled 1 through 20),
Two LAN LEDs per Ethernet port to indicate the interface status
Four interconnect port LEDs (labeled I1 through I4)
the CEM/9HU module. For details on updating module firmware, refer to “Updating the NE
Note
Before you start with troubleshooting, ensure that the administrative states of the affected
Note
Note
Table 73: LED Status of the CEM/9HU
Mod Red Module alarm Remove and reinsert the module.

(critical/major If the condition continues, the module should be
equipment alarms) returned to ADVA Optical Networking for repair.
Yellow Internal supply Remove and reinsert the CEM/9HU.

voltage is out of 1 If the LED is still yellow, replace the
range (too low or too CEM/9HU.
high). Note: A defective module must remain in the
Note: The module shelf until a replacement module is available.
fans run at full speed A shelf without CEM/9HU module must not
in such a condition. be operated for longer than one minute.
2 If the LED is still yellow, return the module to
ADVA Optical Networking for repair or contact
your Technical Services Representative.
Mod Yellow blinking Management Remove and reinsert the CEM/9HU.

to off communication has 1 If the LED is still blinking yellow to off, replace
been cut off. The the CEM/9HU.
connection has Note: A defective module must remain in the
failed. shelf until a replacement module is available.
Note: The module A shelf without CEM/9HU module must not
fans run at full speed be operated for longer than one minute.
in such a condition.
2 If the LED is still blinking yellow to off, return
the module to ADVA Optical Networking for
repair or contact your Technical Services
Representative.
None (Off) Module admin state • If the management displays “unassigned”,

is unassigned. check if the CEM/9HU is provisioned in the
management.
• If the CEM/9HU is not provisioned, then
create it.
Green The module is No action is required.

operating properly
(module is enabled
and not unassigned.)
1 to 20 Yellow Alarm received No action required.
Telemetry contact is
active
Off No alarm received No action required.
Inter- connect Red Passive shelf Verify that the fiber cables between the CEM/9HU
Ports I1 to I4 missing (when and passive shelf are properly connected.
assigned/necessary)
Off flashing to Passive shelf Contact your ADVA Optical Networking Technical
red mismatch (MEA- Services Representative.
ACCEPT)
Yellow Power abnormal Remove and reinsert the CEM/9HU.

(short circuit or no 1 If the LED is still yellow, replace the
power draw although CEM/9HU.
shelf is connected) Note: A defective module must remain in the
Note: The module shelf until a replacement module is available.
fans run at full speed A shelf without CEM/9HU module must not
in such a condition. be operated for longer than one minute.
2 If the LED is still yellow, return the module to
ADVA Optical Networking for repair or contact
your Technical Services Representative.
Inter- connect Yellow blinking Loss of 1 Verify that the fiber cables between the
Ports I1 to I4 to off communication to CEM/9HU and passive shelf are properly
passive shelf connected and check the optical power levels.
(40CSM/2HU-#Dxx- Refer to the procedure, “Finding Your Problem
#Dyy) - Follow the Light” on p. 53 of this document.
2 Check for a power abnormal alarm and refer to
the solution above.
Green The connected No action is required.

passive shelf is
working properly.
None (Off) Port admin state is Check the admin state settings. If the
disabled. management displays “disabled”, change the
admin state settings to “In Service”,
Port admin state is 1 If the management displays “unassigned”,

unassigned. check if the CEM/9HU is provisioned in the
management.
2 If the module is not provisioned, create the
CEM/9HU.
Troubleshooting Switch Modules

This section will help you resolve issues that can be experienced on the switch modules.
“OPPM” on p. 415
“VSM” on p. 418
“RSM-OLM#1630” on p. 420
“RSM-SF” on p. 423
OPPM
Please follow the troubleshooting steps in based upon the states of the LEDs.
The OPPM has five LEDs on the faceplate:
• "C" to indicate the client interface status
• “NW” and “NE” to indicate the network interface status
the OPPM module. For details on updating module firmware, refer to “Updating the NE Software
Note
is set to “Maintenance”.
Note
Note
Table 74: LED Status of the OPPM
LED Names Colors Potential Cause Solution for Troubleshooting
All LEDs Red Initialization error 1 Remove the module, wait 10 seconds, then
insert the module into the slot.
2 If the indication persists, return the module.
P Off Power source is 1 Ensure the module is properly inserted in the

missing, disabled or slot.
failed 2 Check PSU "P" LED.
o
If the LED is off, refer to “Troubleshooting
Power Supply Units” on p. 88.
o
If the LED is green, return the module.
Internal power failure 1 Remove the module, wait 10 seconds, then

Yellow Power is abnormal 1 Remove the module, wait 10 seconds, then

P Green Power operation is No action is required.

normal
Mod Off Admin state is "unas- If the module is to be used, provision the module.
signed"
Admin state is "dis- If the module is to be used, set the Admin State to
abled" "In Service”, “Management” or “Maintenance”.
Red Module major and critical Check the alarm list in NED and troubleshoot the
alarms. alarm(s) as indicated in the “Standing Conditions” on
p. 785.
Switch error - the 1 Remove the OPPM, wait 10 seconds, then

OPPM is unable to insert it into the slot.
execute a validated 2 If the indication persists, contact ADVA Optical
switch request. Networking Technical Services.
Yellow No management com- 1 Make sure the SCU fiber connections are
flashing to munication correct. Refer to the "Interconnecting
off Shelves" section in the Installation and
Commissioning Manual.
2 Make sure the NCU communicates with the
SCU.
3 Make sure the module is properly inserted.
4 Remove the module, wait 10 seconds, then
5 If the indication persists, return the module to
Green Module operation is nor- No action is required.

mal
C Off Admin state is "unas- If the port is to be used, provision the port.
signed" No action is required if the port is not in use.
Admin state is "dis- If the port should be in operation, set the Admin
abled" State to "In Service”, “Management” or “Main-
tenance”.
Yellow Loss of signal 1 Ensure the fiber connections are correct.

2 Ensure the fiber connections are clean.
Refer to the procedure, “Finding Your Problem -
Green Port operation is normal No action is required.
NW, NE Off Admin state is "unas- If the port is to be used, provision the port.
signed" No action is required if the port is not in use.
NW, NE Off Admin state is "dis- If the port should be in operation, set the Admin
abled" State to "In Service”, “Management” or “Main-
tenance”.
Yellow In a provisioned pro- If the root cause is local (LOS is raised at the
flashing to tection configuration, the OPPM):
off protection path cor- 1 Ensure the fiber connections are correct.
responding to this
2 Verify that the fiber connections are clean.
standby port is unavail-
Refer to the procedure in “Finding Your Problem
able. Either no power is
- Follow the Light” on p. 53 in this document.
detected at the input, or
a power level below the
defined minimum value If the root cause is a defect communicated by a
is detected. protection trigger partner (SF-COM is raised at
the OPPM):
1 Check for any signal failure alarms reported by
the protection trigger partners.
2 Follow the troubleshooting steps in “Alarm and
Event List” on p. 783 to resolve these alarms.
Green In a provisioned pro- No action is required.

flashing to tection configuration,
off this standby port is oper-
ating error-free. Hence
the interface is capable
of taking over traffic.
Green Port operation is normal.
VSM
The VSM has four LEDs on the faceplate:
• “NW” and “NE” to indicate the interface status
the VSM module. For details on updating module firmware, refer to “Updating the NE Software
Note
Note
Note
Table 75: LED Status of the VSM
Please note - The module should lose power for at
least 10 seconds to allow any and all capacitance to
dissipate.
P Off Power source has failed. Check the LED of the PSUs.
The NCU receives no • If the LED of the PSUs does not light up green,
power. refer to “Troubleshooting Power Supply Units”
on p. 88.
hardware error of the VSM has occurred. Return
the VSM to ADVA Optical Networking.
Mod Red Module major and critical Check the fault management table.
alarms.
Table 75: LED Status of the VSM
Mod Yellow Management com- Remove and reinsert the VSM.

blinking to munication is broken • If the LED is still blinking yellow to off, replace
off the VSM.
• If the LED is still blinking yellow to off, contact

alarms

unassigned. check if the VSM is provisioned in the
management.
• If the VSM is not provisioned, create the VSM.
NW Green Line West is active. No action is required.
Red Switch error VSM was not able to switch to the backup line.
1 Check the backup line availability.
2 Check the VSM configuration settings (VSM is
locked).
Off West line interface is not Check the network line west availability and the
active. internal cabling.
NE Green Line East is active. No action is required.
Red Switch error VSM was not able to switch to the backup line.
1 Check the backup line availability.
2 Check the VSM configuration settings (VSM is
locked).
Off East line interface is not Check the network line west availability and the
active. internal cabling.
RSM-OLM#1630
This section will help you resolve issues that can be experienced on the RSM-OLM#1630 module. It assumes
that all measurements for all interfaces are within the ADVA Optical Networking specifications. If not, refer to
“Finding Your Problem - Follow the Light” on p. 53 in this document.
The steps in this section will need to be completed on both sides of the link. Please follow the troubleshooting
All installed RSM-OLM modules must be working with the same settings. They will not function
with different switch modes (LOS or Optical Input Power) and line modes (Auto, Forced West or
Forced East).
Note
The RSM-OLM#1630 has four LEDs on the faceplate:

• “Lk” to indicate the operation status of the module
the RSM-OLM#1630 module. For details on updating module firmware, refer to “Updating the NE
Note
Note
Note
Table 76: LED Status of the RSM-OLM#1630
LED-Status Potential Cause Solution for

Troubleshooting
On Lk NW NE
Red Off Red Red Loss of signal was detected on 1 Both network lines might
blinking both network lines. Active line be broken, measure and
is red. The protected line is red check the network lines.
blinking. 2 Sending and receiving
direction of the network
lines are reversed,
check the NW/T, NW/R,
NE/T and NE/R
connectors for the
correct network line.
3 A hardware error has
occurred. Replace or
return the module to
ADVA Optical
Red Orange Red Red blink- OTDR Time Interval is 1 Check the OTDR
ing activated (data transmission is setting.
not interrupted) or both RSM- 2 Check the line mode
OLM modules are locked to settings of both RSM-
different lines (data OLM modules. Set both
transmission is interrupted). line modes to “Auto” or
lock both RSM-OLM
modules to the same
line.
Green Orange Green Green RSM-OLM is locked to a line. Set the line mode to “Auto”.
blinking Both lines are available, active
line is green, protected line is
blinking green.
Green Orange Green Red RSM-OLM is locked to the Check the protected network
blinking active line. Protected line is not line and set the line mode to
available (red blinking). No “Auto”.
switching possible.
Note – If the protected line is
red blinking on both RSM-OLM
modules, the protected line is
not available in both directions.
If the protected line is red
blinking on only one RSM-
OLM, the transmit direction of
this RSM-OLM is not available.
Table 76: LED Status of the RSM-OLM#1630
LED-Status Potential Cause Solution for

Troubleshooting
On Lk NW NE
Green Off Green Red blink- Data transmission via active Check the protected network
ing line. Protected line is not lines.
available (red blinking).
Note – If the protected line is
red blinking on both RSM-OLM
modules, the protected line is
not available in both directions.
If the protected line is red
blinking on only one RSM-
OLM, the transmit direction of
this RSM-OLM is not available.
Green Off Green / Green / Configuration error, data Check the current
Red Red transmission is not interrupted attenuation of both lines and
blinking flashing Switch mode is set to Optical set the threshold to a value
Input Power and the switch above the current line
threshold of one RSM-OLM is attenuation.
set below the current
attenuation of both lines.
Green Off Green Green / Configuration error, data Check the current
Red flash- transmission is not interrupted attenuation of the protected
ing Switch mode is set to Optical line and set the threshold to a
Input Power Data transmission value above the protected
via active line (green) line attenuation.
Protected line is available, but
the switch threshold is below
the current line attenuation.
RSM-SF
This section will help you resolve issues that might be experienced with the RSM-SF#1310 and RSM-SF#1510
modules. It assumes that all measurements for all interfaces are within the ADVA Optical Networking
specifications. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this document.
The steps in this section will need to be completed on both sides of the link. Please follow the troubleshooting
All installed RSM-SF modules must be working with the same settings. They will not function
with different switch modes (LOS or Optical Input Power) and line modes (Auto, Forced West or
Forced East).
Note
The RSM-SF#1310 and RSM-SF#1510 are partners. Both module variants must work in tandem
in a configuration.
Note
The RSM-SF has four LEDs on the faceplate:

• “Lk” to indicate the operation status of the module
the RSM-SF module. For details on updating module firmware, refer to “Updating the NE
Note
Note
Note
Note
Table 77: LED Status of the RSM-SF
On Red Internal error Remove and reinsert the module.

Red blinking Loss of signal on both Investigate for a fiber break on both network
network lines. lines.
Hardware error or Remove and reinsert the module.
both network lines If the condition continues, the module should be
might be broken. returned to ADVA Optical Networking for repair.
Off Power failure Remove and reinsert the module.

Green No error No action is required.
Lk Yellow Automatic protection RSM-SF is locked to NW or NE. Press the

switching is disabled. "Auto" button to enable automatic protection
switching.
Off Automatic protection No action is required.

switching is enabled.
NW Red Active west line is It is likely there is a fiber break on the west line.
broken. Refer to “Finding Your Problem - Follow the
Light” on p. 53.
Red flashing Inactive west line is It is likely there is a fiber break on the west line.
broken; no protection Refer to “Finding Your Problem - Follow the
switching possible. Light” on p. 53.
Green flashing West line is inactive; No action is required.

west line is ok.
Green West line is active

(traffic goes via the
west line).
NE Red Active east line is It is likely there is a fiber break on the east line.
broken. Refer to “Finding Your Problem - Follow the
Light” on p. 53.
Red flashing Inactive east line is
broken; no protection
switching possible.
Green flashing East line is inactive; No action is required.

east line is ok.
Green East line is active

(traffic goes via the
east line).
Chapter 8
Reconfigurable Optical Layer

Devices
This chapter addresses LED indicators and troubleshooting guidelines for these modules:
“ROADM-C40/40/OPM-3HU/2DC” on p. 426
“ROADM and CCM Modules” on p. 429
“4-OPCM” on p. 434
ROADM-C40/40/OPM-3HU/2DC
This section addresses LED indicators and troubleshooting guidelines for the ROADM-C40/40/OPM-3HU/2DC.
ROADM-C40/40/OPM-3HU/2DC shelves have these LEDs:
• “Power A” indicates input and output power status related to the A input
• “Power B” indicates input and output power status related to the B input
• “P” indicates the power status
• “Mod” indicates the shelf status
• “N” indicates the Network port status
• “U” indicates the Upgrade port status
• “MGT U” indicates the Up port status (shelf management connection)
• “MGT D” indicates the Down port status (shelf management connection)
Table 78: ROADM-C40/40/OPM-3HU/2DC LED Indications
LED Name LED Color Potential Cause Troubleshooting Steps
All LEDs Red Initialization error 1 Turn Power A and B off, wait 10 seconds, then
turn Power A and B on.
2 If the indication persists, return the shelf.
Power A Off Input power is not Make sure Power Feeds A and B are receiving power.
Power B present
Input power Change the input power polarity (reverse power

polarity is reversed connections).
Red Input power is not Turn ON the power switch.

turned on
Yellow Input power is out Make sure the input power voltage is within spe-
of range (low or cifications.
high)
Green Power operation is No action is required.

normal
P Off Power is not Make sure Power Feeds A and B are receiving power.
present at Power
Feeds
Power A and B are Make sure Power A and B are on.

both off
Internal power 1 Turn Power A and B off, wait 10 seconds,then

failure turn Power A and B on.
P Yellow A power supply 1 Make sure Power Feeds A and B are receiving
has no output power.
power 2 Make sure Power A and B are on.
Green Power operation is No action is required.

normal
Mod Off Admin state is If the shelf is to be used, provision the shelf.
“unassigned”
Admin state is “dis- If the shelf is to be used, set the Admin State to "In
abled” Service”, “Management” or “Maintenance”.
Yellow flash to No management 1 Make sure the MGT U and/ or MGT D fiber

Off communication connections are correct. Refer to the
"Interconnecting Shelves" section in the
Installation and Commissioning Manual.
2 Make sure all management ports are provisioned
and the ports' Admin States are set to "In
Service”, “Management” or “Maintenance”.
Green Shelf operation is No action is required.

normal
N Off Admin state is If the port is to be used, provision the port.

U “unassigned” No action is required if the port is not in use.
Admin state is “dis- If the port should be in operation, set the Admin State
abled” to "In Service”, “Management” or “Maintenance”.
Red Optical Power 1 Measure the received optical power .

Receive High (out 2 Install the appropriate attenuator to reduce optical
of range) power to within specifications.
Yellow Loss of Signal Make sure the fiber connections are correct.
Optical Power Measure the optical power receive.

Receive Low Refer to the procedure, “Finding Your Problem -
Optical Power 1 Measure the optical power receive.

Receive High 2 Install the appropriate attenuator to reduce the
optical input power to be within specifications.
N Green Port operation is No action is required.

U normal
MGT U Off Admin State is If the port is to be used, provision the port.
MGT D "unassigned" No action is required if the port is not in use.
Admin state is “dis- If the port should be in operation, set the Admin State
abled” to "In Service”, “Management” or “Maintenance”.
Red SFP is not Install an approved SFP that matches provisioning or

installed delete the port.
Red flash to SFP mismatch Replace the SFP with one approved by ADVA
Off Optical Networking.
Yellow Loss of Signal 1 Make sure the fiber connections are correct.
2 If necessary, replace the failed SFP connected to
the port.
Yellow flash to SFP does not Change provisioning to match the SFP or change the
Off match provisioning SFP to match provisioning.
Green flash to External Link Fail - 1 Remove the SFP, wait 10 seconds and insert the
Off No management SFP.
connection but 2 If the indication persists, replace the SFP or
optical power connected SFP as required.
received.
Green Port operation is No action is required.

normal.
Management
connection is
established.
ROADM and CCM Modules

This section addresses LED indications and troubleshooting guidelines for the following ROADM and
CCM modules:
• ROADM-C80
• 8ROADM-C40/0/OPM
• 4ROADM-E-C96/0/OPM
• MROADM-C96
• CCM-C40/8
• CCM-C80/8
• CCM-C96/9
ROADM and CCM modules may have these LEDs:
• “P” indicates the Power supply status
• “Mod”indicates the Module status
• “N” indicates the Network port status
• “U” indicates the Upgrade port status
• “C”, "C1", "C2", "C3", "C4", "C5", "C6", "C7", "C8", "C9" indicates the Client port status
ROADM and CCM modules require optical channel power to be present for proper operation.
Therefore, channel modules with channels that pass through these modules must be set as
follows:
l Auto Laser Shutdown must be set to Disable
Note l Error Forwarding Mode must not be set to Laser Off.
These parameters can cause the channel module laser to be turned off.
Table 79: ROADM Module LED Indications
LED Name LED Colors Potential Cause Troubleshooting Steps
All LEDs Red Initialization error 1 Remove the module, wait 10 seconds,
then insert the module into the slot.
2 If the indication persists, return the
module.
P Off Power source is missing, 1 Make sure the module is properly

disabled or failed inserted in the slot.
2 Check PSU "P" LED.
o
If the LED is off, refer to
“Troubleshooting Power Supply
Units” on p. 88.
o
If the LED is green, return the
module.
Internal power failure 1 Remove the module, wait 10 seconds,

module.
Yellow Power is abnormal 1 Remove the module, wait 10 seconds,

module.
Green Power operation is normal No action is required.
Mod Off Admin state is “unassigned” If the module is to be used, provision the
module.
Admin state is “disabled” If the module is to be used, set the Admin

“Maintenance”.
Yellow flash No management com- 1 Make sure the SCU fiber connections are
to Off munication correct. Refer to the "Interconnecting
Shelves" section in the Installation and
2 Make sure the NCU communicates with
the SCU.
3 Make sure the module is properly
inserted.
4 Remove the module, wait 10 seconds,
module.
Green Module operation is normal No action is required.
N Off Admin state is “unassigned” If the port is to be used, provision the port.
U No action is required if the port is not in use.
C
C1-C9 Admin state is “disabled” If the port should be in operation, set the
P1, P2 Admin State to "In Service”, “Management” or
“Maintenance”.
Blink Red to Fiber-Connect Invalid The fiber connection is invalid (does not com-
Off ply to rules). Disconnect the fiber and con-
nect it to a valid port.
Fiber-Connect Error The fiber connection does no match the con-

nection saved in the database. Disconnect
the fiber and connect it to port listed in Phys-
ical Connections.
Yellow Loss of Signal Make sure the fiber connections are correct.
document.
Optical Power Rx Low Measure the optical power receive.

document.
Optical Power Rx High 1 Measure the optical power receive.

2 Install the appropriate attenuator to
reduce optical power to be within
specifications.
document.
OPT - Signal Fail Refer to the procedure, “Finding Your Prob-

lem - Follow the Light” on p. 53 in this doc-
Optical Power Tx Low ument.
Optical Power Tx High
N Yellow Fiber-Loss of Signal 1 Make sure the fiber connections are

U correct.
C
2 Make sure the fiber connections are
C1-C9
clean.
P1, P2
3 Make sure the remote port supports fiber
detection, fiber detection is enabled and
is transmitting the fiber detect signal.
4 Check the fiber for damage, replace it if
necessary.
5 If the issue persists, replace the module.
Fiber-Tx Signal Failure 1 Make sure fiber detection is enabled and

the transmitted fiber detect signal is
within specifications.
module.
Fiber-Communicate Fail 1 Make sure the fiber connections are

correct.
3 Perform a warm restart of the module.
Fiber-Protocol Fail 1 Make sure the fiber connections are

correct.
3 Perform a warm restart of the module.
Fiber-Data Mismatch 1 Make sure the fiber connections are

correct.
2 Make sure the modules are inserted in
the correct shelf and slot.
Blink Yellow Fiber Detection: Non- Make sure the fiber connection is desired
to Green standard fiber connection connection.
o
If the connection is correct, no action
is required.
o
If connection is incorrect, remove
the fiber, then delete the connection
listed in Physical Connections.
N Blink Green Fiber Detection: Standard No action is required.

U to Off fiber connection.
C
C1-C9
Green Port operation is normal.
P1, P2
4-OPCM
4-OPCM
This section addresses LED indications and troubleshooting guidelines for the 4-OPCM modules.
4-OPCM modules have the following LEDs:
• “P” indicates the Power supply status
• “Mod” indicates the Module status
• “1", "2", "3", "4" indicates the corresponding port status
Table 80: 4-OPCM LED Indications
All LEDs Red Initialization error 1 Remove the module, wait 10 seconds,
module.
P Off Power source is missing, 3 Make sure the module is properly

disabled or failed inserted in the slot.
4 Check PSU "P" LED.
l If the LED is off, refer to
“Troubleshooting Power Supply
Units” on p. 88.
l If the LED is green, return the mod-
ule.
Internal power failure 1 Remove the module, wait 10 seconds,

module.
Yellow Power is abnormal 1 Remove the module, wait 10 seconds,

module.
Green Power operation is normal No action is required.
Mod Off Admin state is “unassigned” If the module is to be used, provision the
module.
Admin state is “disabled” If the module is to be used, set the Admin

“Maintenance”.
4-OPCM
Mod Yellow flash No management com- 1 Make sure the SCU fiber connections are
to Off munication correct. Refer to the "Interconnecting
Shelves" section in the Installation and
2 Make sure the NCU communicates with
the SCU.
3 Make sure the module is properly
inserted.
4 Remove the module, wait 10 seconds,
module.
Green Module operation is normal No action is required.
1-4 Off Admin state is “unassigned” If the port is to be used, provision the port.
No action is required if the port is not in use.
Admin state is “disabled” If the port should be in operation, set the

Admin State to "In Service”, “Management” or
“Maintenance”.
Yellow Optical Power Tx Low 1 Make sure the fiber connections are
correct.
2 Make sure fiber connections are clean.
3 Make sure Optical Power Rx is within
specifications.
document.
Optical Power Tx High 1 Make sure the fiber connections are

correct.
2 Install the appropriate attenuator to
reduce the optical power receive to be
document.
4-OPCM
1-4 Yellow Power Control Fail-Low 1 Make sure the fiber connections are
correct.
2 Make sure the fiber connections are
clean.
3 Make sure the Optical Power Rx is within
specifications.
document.
Power Control Fail-High 1 Make sure the fiber connections are

correct.
2 Make sure the Optical Power Rx is within
specifications.
document.
Attenuator-Control Fail 1 Make sure the Optical Power Rx is within

specifications.
2 If Optical Power Rx is within
specifications, return the module.
Green Port operation is normal. No action is required.
Chapter 9
Optical Filters (Passive Modules

and Shelves)
This chapter addresses LED indicators and troubleshooting guidelines for the passive
units (modules and shelves) specified in Table 81. The passive units have a single status
LED labeled "P" on the faceplate.
Table 81: Passive Optical Filter Module Types
Module Classification Module Type
Interleaver Modules ILM50-#DC
C/L Splitter Modules (CLSM) 2CLSM-#D01-#D64, 2CLSM-#D01-#D64-SFx
Band Splitter Modules (BSM) 2BSM-#Dxx-#Dyy, 2ABSM-#C1470-#C1610,

3BSM-#G1310-#C1610,
3BSM-#G1310-#C1610-E/W
Group Splitter Modules 1GSM+#Dxx-#Dyy, 4GSM-#Dxx-#Dyy,

(GSM) 5GSM-#19590-#19200, 8GSM-#Dxx-#Dyy
Channel Splitter Modules 1CSM+#Cxxxx, 1CSM+#Cxxxx-E/W,

(CSM) 1CSM+#19xxx,
1CSM+#19xxx-E/W, 1CSM+#G1310,
2CSM+#G1310-#Cxxxx-E/W,
4CSM-#Cxxxx-#Cyyyy, 4CSM-#Dxx-#Dyy,
4CSM+#Dxx-#Dyy, 4CSM+#19xxx-#19yyy,
8CSM-#19xxx-#19yyy, 8CSM/P-#19xxx-#19yyy,
16CSM-#D01-#D32-SFx, 16CSM-#D33-#D64-SFx,
40CSM-#Dxx-#Dyy, 40CSM/2HU-#Dxx-#Dyy
40CSM/2HU-#19595-#19205,
40CSM-C80/2HU-#19xxx-#19yyy,
96CSM/4HU-#19600-#19125,
FD-128D
Optical Supervisory Channel OSFM+#1510, OSFM+#1630, OSFM+#1490-SFA,

Modules (OSFM) OSFM+#1510-SFB, OSFMA+1510
Optical Power Splitter Mod- 1PM/MM, 1PM/SM, 2PM/MM, 2PM/MM-OM3,

ules 2PM/SM, PSM-95/5, 2PSM-95/5, 5PSM, 8PSM,
PSM40-MROADM
Optical Time-Domain Reflec- 2-OTFM+#1650

tometer Filter Module
Table 82: LED Status of the Passive Optical Filter Modules

Name Colors
P Red Initialization error. Remove the module, wait 10

seconds, insert module into the
slot.
If the fault condition persists, return
the passive unit.
Off Power operation Module:

is not normal or Make sure the module is properly
has failed. inserted in the slot.
Check PSU "P" LED.
o
If the LED is off, refer to
“Troubleshooting Power
o
If the LED is green, return
the passive unit.
Shelf:
Ensure the shelf is properly
connected to a CEM or PSCU
passive equipment port ("I").
Make sure the passive equipment
port is provisioned and the port's
Admin State is set to "In Service”,
Green Power operation No action is required.

is normal.
Mod Yellow Communication Check the Config tab on the port

between associated with the protection and
protected channel verify that the module AIDs for the
modules has protected modules are correct.
failed.
Yellow Management 1 Check the SCU firmware

flashing to communication to version and compare it to the
off the module has SCU firmware version as listed
failed. on the NCU. If they are
different, update the SCU
“Performing Other Software
If the LED is still flashing yellow to
off, contact your ADVA Optical
Representative.

Name Colors
Mod Off Module admin 1 If the module is installed and

state is disabled. provisioned, check the admin
state settings.
“disabled”, change the admin
state to “In Service”,
“Management” or
“Maintenance”.
Module admin 1 If the management displays

state is “unassigned”, check if the
unassigned. module is provisioned.
2 If required provision the
module.
Green Module No action is required.

provisioned,
admin state is
“Maintenance”,
“Management” or
“In Service”
R Off Admin state is Provision the module.

"unassigned"
Admin state is Set the module Admin State to "In

"disabled" Service", "Management" or
"Maintenance".
Yellow Loss of Signal Make sure the fiber connections are

correct.
Optical Power Rx Measure the optical power receive.

Low Refer to the procedure, “Finding

Name Colors
R Yellow Optical Power Rx 1 Measure the optical power

High receive.
2 Install the appropriate
attenuator to reduce optical
power to be within
specifications.
Optical Power Tx Refer to the procedure, “Finding

Low Your Problem - Follow the Light” on
Optical Power Tx Refer to the procedure, “Finding

High Your Problem - Follow the Light” on
Green Power operation No action is required.

is normal.
Chapter 10
Optical Amplifiers
This chapter addresses LED indicators and troubleshooting guidelines for optical
amplifiers. The following subsections identify and resolve issues of:
“Fixed Pump-Power EDFA Modules” on p. 442
“Fixed Gain-Controlled EDFA Modules” on p. 444
“Variable Gain(-Controlled) EDFA Modules” on p. 451
“RAMAN-C10 Module” on p. 459
“2RAMAN-C15-LL Module” on p. 467
“AMP-S20H-C15 and AMP-S20L-C15 Modules” on p. 475
“EDFA-S20H and EDFA-S20L Modules” on p. 486
“2EDFA-S20L-S10L Modules” on p. 495
Fixed Pump-Power EDFA Modules

This subsection will help you resolve issues that might be experienced with EDFA-C-S10 modules. It is
assumed that the measurements for all interfaces are within ADVA Optical Networking specifications. If not,
please refer to “Finding Your Problem - Follow the Light” on p. 53 in this document.
For information about installing EDFAs, refer to the deployment rules for amplifiers in the
Hardware Description, "Laser Safety Compliant Amplifier Configurations" chapter.
Note
steps, you will destroy the module being tested.
Note
Note
The fixed pump-power EDFA modules have four LEDs on their faceplate:
• “1/R” and “1/T” to indicate the amplifier port status
The following table provides information about troubleshooting fixed pump-power EDFA modules.
Table 83: LED Status of Fixed Pump-Power EDFA Modules

Name
All LEDs Red A serious error in card Remove and reinsert the module. If the
initialization. condition continues, return the module
Please note, the module should lose
power for at least 10 seconds to allow
any and all capacitance to dissipate.
On Green Power is OK. No action is required.
Err Red flashing to off Module boot in No action is required.

(once) progress (once after
insertion into slot
only).
Off There is no error. The

normal state is Off.
Table 83: LED Status of Fixed Pump-Power EDFA Modules

Name
1/R Yellow Incoming signal level 1 Measure the optical input power on
near threshold the receiver connector to verify that
the value is within specifications.
2 Apply optical attenuators as
necessary.
Green Optical input power is No action is required.

OK
Off No signal received Measure the optical input power on the

(LOS). receiver connector to confirm the LOS.
the Light” on p. 53 in this document for
further troubleshooting.
1/T Yellow Output level below 1 Measure the optical input power on
threshold the receiver connector to verify that
the value is indeed within
specifications.
should be returned to ADVA Optical
Please note, the module should lose
power for at least 10 seconds to allow
any and all capacitance to dissipate.
Green Output power level is No action is required.

OK.
Off Module turned off. Activate the module.
Fixed Gain-Controlled EDFA Modules

This subsection will help you resolve issues that might be experienced with EDFA-C-
D17-GC, EDFA-L-D17-GC, EDFA-C-S18-GC, EDFA-C-S18-GCB, EDFA-C-D20-GC,
EDFA-C-S20-GCB and EDFA-C-S20-GCB-DM modules. It is assumed that the
measurements for all interfaces are within ADVA Optical Networking specifications. If
not, please refer to “Finding Your Problem - Follow the Light” on p. 53 in this document.
• Refer to “Fixed Gain-Controlled, Single-Stage EDFA Modules” on p. 445 for a
description of the LEDs for these EDFA module types.
• Refer to “Fixed Gain-Controlled, Double-Stage EDFA Modules” on p. 447 for a
description of the LEDs for these EDFA module types.
Follow all the instructions precisely. If you do not supply the specified
attenuation on given steps, you will destroy the module being tested.
CAUTION
Fixed Gain-Controlled, Single-Stage EDFA Modules

Single-stage, fixed gain-controlled EDFA modules have three LEDs on their faceplate:
• “1” to indicate the amplifier port status
Note
Note
Table 84: LED Status of Single-Stage, Fixed Gain-Controlled EDFA Modules

Name
All LEDs Red A serious error in card Remove and reinsert the module. If the condition
initialization. continues, return the module to ADVA Optical
P Yellow Power abnormal
Off Power failure
Mod Yellow Not applicable.
Yellow Management 1 Check the SCU and EDFA firmware versions.

blinking to communication is broken. Update the firmware if required.
off 2 If the issue is not resolved, remove and reinsert
the SCU.
Representative.
“disabled”. provisioned, check the admin state settings.
the admin state to “In Service”.
Module admin state is Module is not provisioned, start the provisioning

“unassigned”. process.
Table 84: LED Status of Single-Stage, Fixed Gain-Controlled EDFA Modules

Name

admin status
“Maintenance”,
Service”
1 Red Input power is in range, 1 Measure the optical input power on the receiver
but the amplified output connector to verify that the value is indeed
power does not reach within specifications.
target level. 2 Remove and reinsert the module.
Red EDFA off due to EOP Measure the optical input power on the receiver
flashing to (Excessive Output connector to verify that the value is within
off Power) event. specifications.
If the condition continues once the module has been
removed and inserted, it should be returned to
Yellow Optical Input Power out of 1 Measure the optical input power on the receiver
range connector and compare the measured value
with the specification.
2 Install appropriate attenuators to fulfill the
Laser EOL Replace module.
Laser Degrade Replace module.
Green Input power is in range; No action is required.

output power reaches
target level; valid
hardware; interface is
disabled or unassigned
Gain of stage 1 reaches

target level; interface is
Off Interface admin state is 1 In the case that the module is installed and
the admin state to “In Service”, “Management”
or “Maintenance”.
Interface admin state is The module is not provisioned. Start provisioning

unassigned. the module.
Fixed Gain-Controlled, Double-Stage EDFA Modules

Double-stage, fixed gain-controlled EDFA modules have four LEDs on their faceplate:
• “1” to indicate the amplifier port status
• “2” to indicate the amplifier midstage port status
Note
Note
Table 85: LED Status of Double-Stage, Fixed Gain-Controlled EDFA Modules

Name
All LEDs Red A serious error in card Remove and reinsert the module. If the condition
initialization. continues, return the module to ADVA Optical
Off Power failure
Mod Yellow Not applicable
Yellow blinking Management 1 Check the SCU and EDFA firmware

to off communication is versions. Update the firmware if required.
broken. 2 If the issue not resolved, remove and reinsert
the SCU.
“disabled”. provisioned, check the admin state settings.
change the admin state to “In Service”.

Name
Mod Off Module admin state is Module is not provisioned, start the provisioning
“unassigned”. process.
Green Module provisioned, No action is required.

admin status
“Maintenance”,
Service”
1 Red Input power is in range 1 Measure the optical input power on the
and the amplifier receiver connector to verify that the value is
midstage attenuation is indeed within specifications.
OK, but the amplified 2 Remove and reinsert the module.
output power does not
If the condition continues the module should be
reach target level.
(Gain of stage 2 does returned to ADVA Optical Networking for repair.
not reach target level.)
Red flashing to EDFA off due to EOP Measure the optical input power on the receiver
off (Excessive Output connector to verify that the value is within
Power) event. specifications.
If the condition continues once the module has
been removed and inserted, it should be returned
Yellow Optical Input Power out 1 Measure the optical input power on the
of range receiver connector and compare the
measured value with the specification.
2 Install appropriate attenuators to fulfill the
Laser Degrade Replace module.
Yellow flashing Input power is in range, Verify that the attenuation between port 2-T and
to off but the amplifier port 2-R is within specification.
midstage attenuation is
not OK - amplified
output power does not
reach target level.
(Gain of stage 2 does
not reach target level
due to incorrect
midstage attenuation.)

Name
1 Green Input power is in range; No action is required.

target level; valid

target level and the
received power of stage
2 is sufficient; interface
is disabled or
unassigned
Interface admin state is The module is not provisioned. start the

unassigned. provisioning process.
2 Red Input power is in range, Remove and reinsert the module.

but gain of stage 1 does If the condition continues, the module should be
not reach target level. returned to ADVA Optical Networking for repair.
Red flashing to EDFA off due to EOP Measure the optical input power on the receiver
off (Excessive Output connector to verify that the value is within
Power) event. specifications.
If the condition continues once the module has
been removed and inserted, it should be returned
Yellow Input power is in range Verify that the attenuation between the 2T port
and gain of stage 1 and the 2R port is within specification.
reaches target level, but
receive power of stage
2 is insufficient. The
amplifier midstage
attenuation is not OK.
Yellow flashing Input power is out of Measure the optical power on the receiver
to off range and as a result, interface and compare the measured value with
gain of stage 1 does not the specification. Install appropriate attenuators
reach target level. to fulfill the Optical Input Power requirements.

Name
2 Green Input power is in range; No action is required.

target level; valid

received power of stage
2 is sufficient; interface
is disabled or
unassigned
Variable Gain(-Controlled) EDFA Modules

This subsection will help you resolve issues that might be experienced in:
• “Variable Gain-Controlled EDFA Modules” on p. 452
• “Variable-Gain EDFA Modules” on p. 458
Refer to the appropriate section for information.
It is assumed that the measurements for all interfaces are within ADVA Optical
Networking specifications. If not, please refer to “Finding Your Problem - Follow the Light”
Follow all the instructions precisely. If you do not supply the specified
attenuation on given steps, you will destroy the module being tested.
CAUTION
Variable Gain-Controlled EDFA Modules

The following table lists all variable gain-controlled EDFA modules and provides an overview of their LEDs:
Module Variants
EDFA-C-D20-VGC, EDFA-C-S26-VGC-DM,
EDFA-C-D20-VGC-DM, EDFA-C-S26-VGCB-DM1
EDFA-C-D20-VLGC-DM
(EDFA-C-D20 refers to all these
EDFA types)
Module LEDs • “P” to indicate the power supply • “P” to indicate the power supply
status status
• “Mod” to indicate the operation • “Mod” to indicate the operation
status of the module status of the module
• “1” to indicate the amplifier port • “N” to indicate the network port
status status
• “2” to indicate the amplifier
midstage port status
LED Description Refer to Table 86 on p. 453 for a Refer to Table 87 on p. 456 for a
description of these LEDs. description of these LEDs.
If your module has an LED status that is not represented in Table 86 on p. 453 or Table 87 on
p. 456, please contact your ADVA Optical Networking Technical Services Representative.
Note
Note
1The EDFA-C-S26-VGCB-DM and the EDFA-C-S26-VGC-DM are identical, except that the EDFA-C-S26-
VGCB-DM has a 1528.77 nm OSC filter whereas the EDFA-C-S26-VGC-DM has a 1510 nm OSC filter.
Table 86: LED Status of the EDFA-C-D20 Modules

Name
All LEDs Red A serious error in card Remove and reinsert the module. If
initialization. the condition continues, the module
P Yellow Power abnormal Networking for repair.
Off Power failure
Green Power is OK No action is required.
Mod Yellow Not applicable
Yellow blinking to off Management 1 Check the SCU and EDFA

communication is broken. firmware versions. Update the
firmware if required.
2 If the issue not resolved, remove
and reinsert the SCU.
contact your ADVA Optical
Representative.
Off Module admin state is 1 In the case that the module is

“disabled”. installed and provisioned, check
the admin state settings.
Module admin state is Module is not provisioned, start the

“unassigned”. provisioning process.

status “Maintenance”,
Service”
1 Red Input power is in range and 1 Measure the optical input power
the amplifier midstage on the receiver connector to verify
attenuation is OK, but the that the value is indeed within
amplified output power specifications.
does not reach target level. 2 Remove and reinsert the module.
(Gain of stage 2 does not
reach target level.) If the condition continues, the module

Name
1 Red flashing to off EDFA off due to EOP Measure the optical input power on the
(Excessive Output Power) receiver connector to verify that the
event. value is within specifications.
If the condition continues once the
module has been removed and
inserted, it should be returned to
Yellow Optical Input Power out of 1 Measure the optical input power
range on the receiver connector and
the specification.
2 Install appropriate attenuators to
requirements.
Laser Degrade
Yellow flashing to off Input power is in range, but Verify that the attenuation between
the amplifier midstage port 2-T and port 2-R is within
attenuation is not OK - specification.
amplified output power
does not reach target level.
(Gain of stage 2 does not
reach target level due to
incorrect midstage
attenuation.)

target level; valid hardware;
interface is disabled or
unassigned

received power of stage 2
is sufficient; interface is

Name
1 Off Interface admin state is 1 In the case that the module is

disabled. installed and provisioned, check
the admin state settings.
“Maintenance”.
Interface admin state is The module is not provisioned. start

unassigned. the provisioning process.
2 Red Input power is in range, but Remove and reinsert the module.
gain of stage 1 does not If the condition continues, the module
reach target level. should be returned to ADVA Optical
Red flashing to off EDFA off due to EOP Measure the optical input power on the
(Excessive Output Power) receiver connector to verify that the
event. value is within specifications.
If the condition continues once the
module has been removed and
inserted, it should be returned to
Yellow Input power is in range and Verify that the attenuation between the
gain of stage 1 does reach 2T port and the 2R port is within
target level, but receive specification.
power of stage 2 is
insufficient. The amplifier
midstage attenuation is not
OK.
Yellow flashing to off Input power is out of range Measure the optical power on the
and as a result, gain of receiver interface and compare the
stage 1 does not reach measured value with the specification.
target level. Install appropriate attenuators to fulfill
the Optical Input Power requirements.

target level; valid hardware;
interface is disabled or
unassigned

received power of stage 2
is sufficient; interface is
Table 87: LED Status of the EDFA-C-S26-VGC[B]-DM Module

Name
All Red A serious error in card Remove and reinsert the module. If the
LEDs initialization. condition continues, the module should be
returned to ADVA Optical Networking for
P Yellow Power abnormal repair.
Off Power failure
Green Power is OK No action is required.
Mod Yellow Not applicable.
Yellow Management communication is 1 Check the SCU and EDFA firmware

blinking to broken. versions. Update the firmware if required.
off 2 If the issue is not resolved, remove and
reinsert the SCU.
Off Module admin state is “disabled”. 1 In the case that the module is installed and
settings.
change the admin state to “In Service”.
Module admin state is Module is not provisioned, start the

“unassigned”. provisioning process.

status “Maintenance”,
Table 87: LED Status of the EDFA-C-S26-VGC[B]-DM Module

Name
N Red Not applicable. Remove and reinsert the module.

repair.
Red flashing Auto shut down 1 Make sure Optical Input Power is within
to off range and gain is not too high.
Yellow Laser EOL Replace module.
Laser Degrade
Laser Temperature Remove and reinsert the module.

repair.
Input power OOR Make sure Optical Input Power is within range.
Output power OOR Make sure gain is not too high.
Apr/Opt Limit Make sure pilot signal is present and gain is not
too high.
Gain/Tilt Alarm Make sure that the pilot signal level is not too
low or gain is not too high.
Green Everything is ok. No action is required.
settings.
Interface admin state is The module is not provisioned. Start

unassigned. provisioning the module.
Variable-Gain EDFA Modules
The EDFA-C-D27-GCB-DM is a variable-gain EDFA module with the following three LEDs on its faceplate:
• “N” to indicate the network port status
Another variant of the EDFA-C-D27-GCB-DM is the EDFA-C-S26-VGC-DM, which is a variable gain-controlled
EDFA.
The LED description of the EDFA-C-S26-VGC-DM also applies to the EDFA-C-D27-GCB-DM. Refer to Table 87
on p. 456 for information about the LEDs of the EDFA-C-D27-GCB-DM.
RAMAN-C10 Module
RAMAN-C10 Module
This subsection will help you resolve issues that might be experienced with the RAMAN-C10 module. It is assumed that the measurements for all interfaces are within
ADVA Optical Networking specifications. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this document.
Follow all the instructions precisely. If you do not supply the specified attenuation on given steps, you will destroy the module being tested.
CAUTION
Representative.
Note
The RAMAN-C10 module has three LEDs on its faceplate:

• “N” to indicate the relative operating status of the network port and the upgrade port
Please note, the module should lose power for at least 10 seconds to allow any and all capacitance to dissipate.
Note
RAMAN-C10 Module
Table 88: LED Status of the RAMAN-C10 Module
All LEDs Red Remove and reinsert the module. If the condition continues, return the module to ADVA
Off Power failure
Green Power normal No action required.
Mod Yellow Not Applicable
Yellow blinking to Management communication is 1 Check the SCU and RAMAN firmware version. Update the firmware if required.
off broken. 2 If the issue is not resolved then remove and reinsert the SCU.
Off Module admin state is “disabled”. 1 In the case that the module is installed and provisioned, check the admin state
settings.
2 If the management displays “disabled”, change in the admin state settings to “In
Service”.
Module admin state is “unassigned”. Module is not provisioned, start the provisioning process.
Green Module provisioned, admin status is No action is required.

“Maintenance”, “Management”, “In
Service” or “Auto In Service”
RAMAN-C10 Module
N (Alarms at Red blinking to off Raman Shutdown due to defect, (BR, 1 Verify that the network port is correctly cabled.
Network port) No OSC Signal/Data Signal) LKDO- 2 Verify that there are no payload optical signals arriving at the network port of the
APS module. Note that the OSC signal must be present. If there is payload signal power
present at this point, then find its source and remove from the system. To
successfully create an ASE table, there must not be any payload signal power
present at the Raman network port receiver.
3 Proceeding back along the incoming network signal fiber path, inspect each of the
fiber connectors along the path and clean or replace them as needed if they are dirty
or damaged. While disconnected, test each optical segment to ensure it is not
broken (i.e. verify the optical continuity or the segment and that the loss of the
segment is within expected limits). Replace any segment which are found to
contain a break or to exhibit excessive loss. Also verify that the fiber in the segment
is of the correct type, and replace any segments containing an incorrect fiber type.
4 Perform the ASE table build process on the amplifier module.
5 Replace module.
Raman Shutdown due to temp This condition occurs in order to avoid or at least minimize possible damage to the
(LKDO-TEMP) Raman module due to excessive temperatures encountered by the module.
1 Verify that the equipment operating environment for the shelf containing the module
meets specifications, and that the air filter is clean and unobstructed.
2 Verify that there are no abnormal conditions or failures of the fan units within the
shelf containing the module.
3 Verify that the module placement and that the surrounding equipment contained
within the same shelf conform to the product’s engineering guidelines.
4 Replace the plug or module supporting the facility.
RAMAN-C10 Module
N (Alarms at Yellow Raman ASE Table build failure (any 1 Verify that the correct fiber is connected to the network side input port of the Raman
Network port) ASE table build failure) module, and correct any cabling issues if they exist.
2 Verify that there are no payload optical signals arriving at the network port of the
module. Note that the OSC signal should be present. If there is payload signal
power present at this point, then find its source and remove from the system. To
successfully create an ASE table, there should be no payload signal power present
at the Raman network port receiver.
3 Perform the ASE table build process on the Raman module.
4 Replace the Raman module.
RAMAN-C10 Module
Raman off due to No ASE Table Perform the ASE table build process on the Raman module.
Available
Pump Power (high/low) 1 Verify that the module and facility are provisioned correctly and that the PUMPWR-
CTRL attribute of the facility is set to the correct value for the transmission span.
2 Verify that the incoming cable carrying the service is the correct cable and that the
transmit and receive ports are connected to their properly.
4 Verify that a signal is present at the cable termination and that the signal conforms
to the input power level specifications. If the signal meets the required
specifications proceed to the next step below, otherwise locate the source of the
signal problem upstream and repair the problem. The upstream problem may be the
result of excessive span length, excessive span loss or inadequate launch power
from the far end.
Laser-Current Abnormal (high/low Replace the plug or Raman module supporting the facility, as appropriate.
threshold)
RAMAN-C10 Module
N (Alarms at Yellow Temperature high/low threshold 1 Verify that the equipment operating environment for the shelf containing the module
Network port) (LSRTEMP1, LSRTEMP2, Raman meets specifications, and that the air filter is clean and unobstructed.
module temperature, pump block 2 Verify that there are no abnormal conditions or failures of the fan units within the
temperature) shelf containing the module.
N (Alarms at Loss of OSC 1 Verify that the network port is correctly connected.
Upgrade port) 2 Verify that the OSC facility transmitted by the far end is correctly configured, that it
is operating normally, and that it is correctly connected into the transmission fiber.
3 Verify that the incoming fiber connector is clean and firmly connected to the receive
port associated with the facility. Clean the connection or replace the cable, plug or
module, as appropriate.
to the required specifications If the signal meets the required specifications proceed
to the next step below, otherwise locate the source of the signal problem upstream
and repair the problem.
5 Replace the module supporting the facility.
RAMAN-C10 Module
N (Alarms at Yellow Loss of Signal 1 Verify that the facility is provisioned correctly.
Upgrade port) 2 Verify that the network port is correctly cabled.
3 Verify that the incoming cable is clean and firmly connected to the receive port
associated with the facility. Clean the connector or replace the cable, plug or
to the required specifications. If the signal meets the required specifications
proceed to the next step below, otherwise locate the source of the signal problem
upstream and repair the problem.
OSC OPR high/low threshold 1 Verify that the threshold level is provisioned correctly.
2 Verify that the network port is correctly connected and that the transmit and receive
ports are connected.
to the maximum power level specifications. If the signal meets the required
specifications proceed to the next step below, otherwise locate the source of the
signal problem upstream and repair the problem. It may be necessary to pad the
span to bring the attenuation within the specified minimum range required by the
system.
LASER EOL Replace the RAMAN module.
LASER Degrade Replace the RAMAN module.
RAMAN-C10 Module
N (Alarms at Yellow blinking to ASE Table Build No action is required.

Upgrade port) off
Green Pumps are up. Output power is within

limit. Amplifier is operating without
error. Port provisioned, admin status
is "Maintenance", "Management", "In
Service" or "Auto In Service".
Off Interface admin state is disabled. 1 In the case that the module is installed and provisioned, check the admin state
settings.
2 If the management displays “disabled”, change the admin state to “In Service”.
Interface admin state is unassigned. The module is not provisioned, start the provisioning process.
Yellow APR This condition is informative, and no corrective action is required. Corrective action will
need to be taken in response to the associated signal failure condition.
OPT Threshold low/high 1 Verify that the optical pump power applied to the network span by the Raman
amplifier is within the engineered limits for that span. Adjust the power settings as
needed to bring the power level within the specified limits.
2 Verify that the optical signal from the preceding module in the span falls within the
engineered limits. Adjust the power settings as needed to bring the power level
within the specified limits.
3 Examine the network span and correct all factors causing excessive loss, such as
bent or damaged fibers, optical attenuators with values higher than appropriate, or
loose or damaged optical connectors.
2RAMAN-C15-LL Module
This subsection will help you resolve issues that might be experienced with the 2RAMAN-C15-LL module. It is assumed that the measurements for all interfaces are within
CAUTION
Representative.
Note
The 2RAMAN-C15-LL module has four LEDs on its faceplate:

• “N” to indicate the operating status of the network port
• “U” to indicate the operating status of the upgrade port
The module should lose power for at least 10 seconds to allow any and all capacitance to dissipate.
Note
Table 89: LED Status of the 2RAMAN-C15-LL Module
All LEDs Red A serious error in card initialization. Remove and reinsert the module. If the condition continues, the module should be
Off Power failure
Green Power normal No action required.
Yellow blinking to Management communication is 1 Check the SCU and RAMAN firmware version. Update the firmware if required.
off broken. 2 If the issue is not resolved, then remove and reinsert the SCU.
If the LED is still blinking yellow to off, contact your ADVA Optical Networking
Off Module admin state is “disabled”. 1 In the case that the module is installed and provisioned, check the admin state
settings.
Service”.
Module admin state is “unassigned”. Module is not provisioned, start the provisioning process.
Green Module provisioned, admin status is No action is required.

“Maintenance”, “Management”, “In
Service” or “Auto In Service”
N Red blinking to off Raman Shutdown due to APS, due to 1 Verify that the network port is correctly cabled.
shut down of FWD or BWD or both 2 APS occurs at the BWD Raman if OSC and data signal are lost. Or at the FWD
amplifiers. (LKDO-APS) Raman if the BWD Raman pumps are not on. Note that the BWD Raman must be
operational for the FWD to start. OSC must be present for the BWD to start.
3 Proceeding back along the incoming network signal fiber path, inspect each of the
fiber connectors along the path and clean or replace them as needed if they are dirty
or damaged. While disconnected, test each optical segment to ensure it is not
broken (i.e. verify the optical continuity or the segment and that the loss of the
segment is within expected limits). Replace any segment which are found to
contain a break or to exhibit excessive loss. Also verify that the fiber in the segment
is of the correct type, and replace any segments containing an incorrect fiber type.
4 Verify that an ASE table is present. If not, then initiate an ASE Table build. Perform
the ASE table build process on the amplifier module.
5 Replace module.
Raman Shutdown due to temp This condition occurs to avoid possible damage to the Raman module due to excessive
(LKDO-TEMP) component temperatures.
4 Replace the module.
N Yellow Raman ASE Table build failure due to 1 Verify that the correct fiber is connected to the network side of the Raman module
shut down of FWD or BWD or both and correct any cabling issues if they exist.
amplifiers. 2 Verify that there are no payload optical signals (for FWD Raman at the U port, for
BWD Raman at the Network port). Note that the OSC signal must be present. If
there is payload signal power present, then find its source and remove from the
system. To successfully create an ASE table, there must be no payload signal
power present.
Raman pumps off due to No ASE Perform the ASE table build process on the respective amplifier, either FWD or BWD or
Table available due to shut down of both.
FWD or BWD or both amplifiers.
OSC OPT Power Control (high/low) 1 Verify that the Raman module is connected to the OSC module and that OSC
signal is present at the Raman module.
2 Verify the setting of the OSC power provisioning.
3 Based on indicator (high or low); check the OSC optical power level from the OSC
module and verify that it is within specificaiton.
Pump Power (high/low) 1 Verify that the network side fiber is the correct type and connected correctly.
1 Verify that the amplifier is provisioned for the correct fiber type.
N Yellow Temperature high/low threshold 1 Verify that the equipment operating environment for the shelf containing the module
(Pump LASER temperature) meets specifications, and that the air filter is clean and unobstructed.
Loss of OSC 1 Verify that the network port is correctly connected.

2 Verify that the OSC facility transmitted by the far end is correctly configured, that it
is operating normally, and that it is correctly connected into the transmission fiber.
N Yellow Loss of Signal 1 Verify that the facility is provisioned correctly.

2 Verify that the network port is correctly cabled.
3 Verify that all fibers are clean and firmly connected. Clean connectors if needed.
LASER EOL Replace the RAMAN module.
LASER Degrade
Off Interface admin state is “disabled”. 1 In the case that the module is installed and provisioned, check the admin state
settings.
Service”.
Interface admin state is Module is not provisioned, start the provisioning process.
“unassigned”.
Green Pumps are up. Output power is within No action is required.

error. Interface provisioned, admin
status is "Maintenance",
"Management", "In Service" or "Auto
In Service".
U Yellow Loss of Signal 1 Verify that the facility is provisioned correctly.

OPR (high/low threshold) 1 Verify that a signal is present at the cable termination and that the signal conforms
to power level specifications. If the signal meets the required specifications
upstream and repair the problem. It may be necessary to pad the span to bring the
attenuation within the specified minimum range required by the system.
OPT (high/low threshold) 1 Verify the provisioning of the OPT thresholds and that the thresholds meet the
expected signal levels.
2 Verify that the optical signal from the preceding module in the span falls within the
engineered limits. Adjust the power settings as needed to bring the power level
3 Examine the network span and correct all factors causing excessive loss, such as
bent or damaged fibers, optical attenuators with values higher than appropriate, or
loose or damaged optical connectors.
U Off Interface admin state is disabled. 1 In the case that the module is installed and provisioned, check the admin state
settings.
2 If the management displays “disabled”, change the admin state to “In Service”.
Interface admin state is unassigned. The module is not provisioned, start the provisioning process.
Green Pumps are up. Output power is within No action is required.

error. Port provisioned, admin status
is "Maintenance", "Management", "In
Service" or "Auto In Service"
AMP-S20H-C15 and AMP-S20L-C15 Modules

This subsection will help you resolve issues that might be experienced with the high gain AMP-S20H-C15 and the low gain AMP-S20L-C15 modules. It is assumed that the
measurements for all interfaces are within ADVA Optical Networking specifications. If not, refer to “Finding Your Problem - Follow the Light” on p. 53 in this document.
CAUTION
Representative.
Note
The AMP-S20H-C15 and AMP-S20L-C15 modules have four LEDs on its faceplate:
Note
Table 90: LED Status of the AMP-S20H-C15 and AMP-S20L-C15 Modules
initialization. If the condition continues, return the module to ADVA Optical Networking for repair.
P Yellow Power abnormal Remove and reinsert the EDFA Raman module. If the condition continues, the module should be
Green Power normal No action is required.
Off Power failed Return EDFA Raman module to ADVA Optical Networking for repair.
Yellow Management communication is 1 Check the SCU and amplifier firmware version. Update the firmware if required.
blinking to off broken. 2 If the issue is not resolved then remove and reinsert the SCU.
Green Module provisioned, admin 1 In the case that the EDFA Raman module is installed and provisioned, check the admin state
status is “Maintenance”, settings.
“Management”, “In Service” or 2 If the management displays “disabled”, change in the admin state settings to “In Service”.
“Auto In Service”
Off Module admin state is “disabled” The EDFA Raman module is not provisioned. Start the provisioning process.
or UAS.
N Red blinking EDFA shut down due to This condition occurs to avoid possible damage to the EDFA Raman module due to excessive
to off temperature. component temperatures.
1 Verify that the equipment operating environment for the shelf containing the module meets
specifications, and that the air filter is clean and unobstructed.
2 Verify that there are no abnormal conditions or failures of the fan units within the shelf containing
the module.
3 Verify that the module placement and that the surrounding equipment contained within the same
shelf conform to the product’s engineering guidelines.
4 Replace the EDFA Raman module.
EDFA shut down due to Make sure pilot signal is present and gain is not too high.
OPTLMT
Yellow OSC OPT power control high or 1 Verify that the EDFA Raman module is connected to the OSC module and that OSC signal is
low present at the EDFA Raman module.
3 Based on indicator (high or low); check the OSC optical power level from the OSC module and
verify that it is within specificaiton.
EDFA GAIN/TILT Abnormal, 1 Verify that the network side fiber is the correct type and connected correctly.
VOACTRL Fail 2 Verify that the amplifier is provisioned for the correct fiber type.
3 Perform the ASE table build process on the EDFA Raman module.
N Yellow Loss of OSC 1 Verify that the network port is correctly connected.
2 Verify that the OSC facility transmitted by the far end is correctly configured, that it is operating
normally, and that it is correctly connected into the transmission fiber.
3 Verify that the incoming fiber connector is clean and firmly connected to the receive port
associated with the facility. Clean the connection or replace the cable, plug or module, as
appropriate.
4 Verify that a signal is present at the cable termination and that the signal conforms to the required
specifications. If the signal meets the required specifications proceed to the next step below,
otherwise locate the source of the signal problem upstream and repair the problem.
Loss of data signal 1 Verify that the facility is provisioned correctly.

EDFA LASER EOL Replace the EDFA Raman module.
N Yellow EDFA Temp high/low threshold 1 Verify that the equipment operating environment for the shelf containing the module meets
the module.
Off Port admin state DSBLD or 1 In the case that the module is installed and provisioned, check the admin state settings.
UAS 2 If the management displays “disabled”, change in the admin state settings to “In Service”.
3 EDFA Raman module is not provisioned. Start the provisioning process.
Green Normal, EDFA operational no No action is required.

facility defects
U Red flashing Fiber connection invalid, Tx 1 Carefully trace the fiber to the far-end port and determine to which port the fiber is connected. If
to off and/or Rx required, adjust the fiber connections at either or both ends, so they conform to the intended fiber
connection provisioning plan.
Fiber connection mismatch, Tx 2 If the condition persists, replace the module at the far-end of the fiber.
and/or Rx
3 If the condition fails to clear, replace the module supporting this facility.
U Red flashing BWD Raman pump shut down This condition occurs to avoid possible damage to the EDFA Raman module due to excessive
to off due to temp component temperatures.
1 Verify that the equipment operating environment for the shelf containing the module meets
the module.
BWD Raman shut down due to 1 Verify that the network port is correctly cabled.
APS (but only if EDFA amplifier 2 APS occurs at the BWD Raman if OSC and data signal are lost.
is enabled)
3 Proceeding back along the incoming network signal fiber path, inspect each of the fiber
connectors along the path and clean or replace them as needed if they are dirty or damaged.
While disconnected, test each optical segment to ensure it is not broken (i.e. verify the optical
continuity or the segment and that the loss of the segment is within expected limits). Replace any
segment which are found to contain a break or to exhibit excessive loss. Also verify that the fiber
in the segment is of the correct type, and replace any segments containing an incorrect fiber type.
4 Verify that an ASE table is present. If not, then initiate an ASE Table build.
5 Replace module.
U Yellow Fiber Connection Loss of Signal 1 Verify that the facility is provisioned correctly.
3 Verify that the incoming cable is clean and firmly connected to the receive port associated with
the facility. Clean the connector or replace the cable, plug or module, as appropriate.
OPR (high/low threshold) 1 Verify that a signal is present at the cable termination and that the signal conforms to power level
otherwise locate the source of the signal problem upstream and repair the problem. It may be
necessary to pad the span to bring the attenuation within the specified minimum range required by
the system.
OPT (high/low threshold) 1 Verify the provisioning of the OPT thresholds and that the thresholds meet the expected signal
levels.
2 Verify that the optical signal from the preceding module in the span falls within the engineered
limits. Adjust the power settings as needed to bring the power level within the specified limits.
3 Examine the network span and correct all factors causing excessive loss, such as bent or
damaged fibers, optical attenuators with values higher than appropriate, or loose or damaged
optical connectors.
U Yellow BWD Raman ASE Table build 1 Verify that the correct fiber is connected to the network side input port of the EDFA Raman
fail module, and correct any cabling issues if they exist.
2 Verify that there are no payload optical signals arriving at the Network port of the module. Note
that the OSC signal should be present. If there is payload signal power present at this point, then
find its source and remove from the system. To successfully create an ASE table, there should
be no payload signal power present at the EDFA Raman Network port receiver.
3 Perform the ASE table build process on the EDFA Raman module.
BWD Raman pumps off due to Perform the ASE table build process on the EDFA Raman module.
No ASE Table available
BWD Gain/Tilt abnormal Verify the gain setting, the fiber type, and the fiber connections.
Fiber Connection Optical Power Replace the module supporting this facility.
Tx Fault
Fiber Connection 1 Verify that the fiber detection termination point entity is provisioned and in-service at the far-end
Communications error of the fiber, and that fiber detection is enabled. Correct any provisioning errors.
2 Verify that the module at the far-end is correctly provisioned and equipped, and is operating error-
free. Address any error conditions reported at the far-end module or by the far-end fiber detection
termination point.
3 If the condition persists, replace the module supporting the facility.
U Yellow Fiber connection protocol fault 1 Check if the firmware revision level of the modules at both ends of the fiber is the appropriate
version for the software generic and module type. Upgrade any module found to contain an
incorrect firmware load revision level.
2 Verify that the optical connectors associated with each end of the fiber are securely attached, and
tighten/firmly insert any loose connectors.
3 Inspect the fiber. Replace any fiber which is of the wrong type or specification, which has been
bent beyond the allowable minimum bend radius, or which has sustained any physical damage.
4 Inspect the fiber connectors at each end of the fiber and clean each connector. Verify that the
connectors are undamaged. Test the optical fiber cable to verify that it meets engineering
specifications for the application, and that there are no internal fiber breaks or excessive loss due
to failures which are not readily apparent from visual inspection. Replace any damaged
component (cable or module, if the connector on the module is damaged).
5 Verify that the optical source for the fiber connectivity check signals of the modules at the far-end
of the fiber is operating within expected optical signal power limits. Replace any module found to
operate outside the specified limits.
6 If the condition still fails to clear, replace the module reporting the failure.
Fiber connection data fault 1 Verify that the facility is provisioned correctly.
U Yellow BWD LASER EOL Replace EDFA Raman module
BWD Raman Temp high/low 1 Verify that the equipment operating environment for the shelf containing the module meets
Threshold specifications, and that the air filter is clean and unobstructed.
the module.
Yellow BWD ASE Table Build No action required.

flashing to off
Fiber Detection Attenuation 1 Verify that the optical connectors associated with each end of the fiber are securely attached, and
High, Tx and/or Rx tighten/firmly insert any loose connectors.
2 Inspect the fiber. Replace any fiber which is of the wrong type or specification, which has been
bent beyond the allowable minimum bend radius, or which has sustained any physical damage.
3 Inspect the fiber connectors at each end of the fiber and clean each connector. Verify that the
connectors are undamaged. Test the optical fiber cable to verify that it meets engineering
specifications for the application, and that there are no internal fiber breaks or excessive loss due
to failures which are not readily apparent from visual inspection. Replace any damaged
component (cable or module, if the connector on the module is damaged).
4 Verify that the optical source for the fiber connectivity check signals of the modules at the far-end
of the fiber is operating within expected optical signal power limits. Replace any module found to
U Green No defects. Pumps are up. No action is required.

Output power is within limit.
Amplifier is operating without
error. Port provisioned, admin
status is “Maintenance”,
"Management", "In Service" or
"Auto In Service"
Off U interface admin state is 1 If the module is installed and provisioned, check the admin state settings.
"disabled" or "UAS" and 2 If the management displays “disabled”, change the admin state to “In Service”.
Fiber Detection feature is
disabled or Fiber Detection 3 The EDFA Raman module is not provisioned. Start the provisioning process.
feature is enabled and PTP
ADMIN state is DSBLD or no
Fiber detect conditions exist.
1 Fiber Detection LED operation may be controlled via the NCU.

2 Fiber Detection LED operation appear on the "port" LED of interest but are actually against the PTP and are not dependent on the ADMIN state of the port itself.
3 If PTP is DSBLD, then LED actions due to fiber detection should not impact LED.
4 Fiber Detection feature must be "enabled" for the fiber detection conditions to influence the LED. IF the fiber detection function is "disabled", then the fiber detection
conditions have NO influence on the LED.
5 If U port is UAS or DSBLD and Fiber detection feature is "enabled" and ADMIN state of the PTP is NOT DSBLD, then the U LED will be off unless there is a fiber
detection condition. If U port is UAS or DSBLD and Fiber detection feature is "enabled" and PTP is DSBLD, then U port LED is off. If U port is UAS or DSBLD and
Fiber detection feature is "disabled", then U port LED is off.
EDFA-S20H and EDFA-S20L Modules

This subsection will help you resolve issues that might be experienced on extended variable gain EDFAs, namely the high gain EDFA-S20H and the low gain EDFA-S20L
modules. It is assumed that the measurements for all interfaces are within ADVA Optical Networking specifications. If not, refer to “Finding Your Problem - Follow the
CAUTION
Representative.
Note
Each EDFA-S20H/EDFA-S20L module has four LEDs on its faceplate:

Note
Table 91: LED Status of the EDFA-S20H and EDFA-S20L Modules

Name Colors
All Red A serious error in card Remove and reinsert the module.
LEDs initialization. If the condition continues, return the module to ADVA Optical Networking for repair.
P Yellow Power abnormal Remove and reinsert the EDFA module. If the condition continues, return the module to ADVA Optical Networking for
repair.
Off Power failed Return the EDFA module to ADVA Optical Networking for repair.
Yellow Management 1 Check the SCU and amplifier firmware version. Update the firmware if required.
blinking to communication is 2 If the issue is not resolved, remove and reinsert the SCU.
off broken.
Green Module provisioned, 1 If the EDFA module is installed and provisioned, check the administrative state settings.
administrative state 2 If the management system displays “disabled”, change the administrative state to “In Service”.
is “Maintenance”,
“Management”, “In
Service” or “Auto In
Service”
Off The EDFA module is Initiate the provisioning process, or set the administrative state to "In Service", "Maintenance", "Management", or "Auto
disabled or not In Service".
provisioned.

Name Colors
N Red EDFA shut down due This condition occurs to avoid possible damage to the EDFA module due to excessive component temperatures.
blinking to to temperature. 1 Verify that the equipment operating environment for the shelf containing the module meets specifications, and that
off the air filter is clean and unobstructed.
2 Verify that there are no abnormal conditions or failures of the fan units within the shelf containing the module.
3 Verify the module placement and that the surrounding equipment contained within the same shelf conform to the
product’s engineering guidelines.
4 If the issue is not resolved, replace the EDFA module.
The EDFA pumps are 1 Ensure the input power to the amplifier is in the recommended range.
shut down for laser 2 Make sure pilot signal is present and the gain is not too high.
safety reasons, since
the output power
exceeded the
recommended range.
EDFA pumps are Troubleshoot the LOS condition at the U port.

shut down due to an
LOS condition at the
upgrade (U) port.

Name Colors
N Yellow OSC OPT power 1 Verify that the EDFA module is connected to the OSC module and that OSC signal is present at the EDFA module.
control high or low 2 Verify the setting of the OSC power provisioning.
3 Based on indicator (high or low); check the OSC optical power level from the OSC module and verify it is within
specification.
4 If the issue is not resolved, replace the EDFA module
Pump temperature 1 Verify that the equipment operating environment for the shelf containing the module meets specifications, and that
high/low threshold the air filter is clean and unobstructed.
2 Verify that there are no abnormal conditions or failures of the fan units within the shelf containing the module.
3 Verify that the module placement and that the surrounding equipment contained within the same shelf conform to
the product’s engineering guidelines.
EDFA GAIN/TILT 1 Measure the optical input power on the receiver connector to verify that the value is within specifications.
abnormal, 2 Check gain/tilt settings.
VOACTRL Fail
3 Remove and reinsert the module. If the condition persists, return this EDFA to ADVA Optical Networking for repair.
Pump laser EOL Replace the EDFA module.
Green The EDFA is oper- No action is required.

ating normally
without any facility
defects.

Name Colors
N Off The port 1 If the EDFA module is installed and provisioned (including the N and U interfaces), check the administrative state
administrative state settings. If the management system displays “disabled”, change the administrative state to “In Service”.
is disabled or this 2 If the EDFA module is not provisioned, or the N interface is not provisioned, initiate the provisioning process.
interface is
unassigned.
U Red Fiber connection 1 Carefully trace the fiber to the far-end port and determine to which port the fiber is connected. If required, adjust the
blinking to invalid, Tx and/or Rx fiber connections at either or both ends, so they conform to the intended fiber connection provisioning plan.
off 2 If the condition persists, replace the module at the far-end of the fiber.
Fiber connection
mismatch, Tx and/or 3 If the condition fails to clear, replace the module supporting this facility.
Rx
Yellow Loss of signal 1 Verify that the upgrade port is correctly connected.
2 Verify that the OSC facility transmitted by the far end is correctly configured, that it is operating normally, and that it
is correctly connected into the transmission fiber.
3 Verify that the incoming fiber connector is clean and firmly connected to the receive port associated with the
facility. Clean the connection or replace the cable, plug or module, as appropriate.
4 Verify that a signal is present at the cable termination and that the signal conforms to the required specifications.
5 If the signal meets the required specifications, locate the source of the signal problem upstream and repair the
problem.
6 If the problem continues, replace the module supporting the facility.

Name Colors
U Yellow OPR (high/low 1 Verify that a signal is present at the cable termination and that the signal conforms to power level specifications.
threshold) 2 If the signal meets the required specifications, locate the source of the signal problem upstream and repair the
problem. It may be necessary to pad the span to bring the attenuation within the required minimum range.
Fiber connection 1 Verify that the facility is provisioned correctly.

Loss of Signal 2 Verify that the upgrade port is correctly cabled.
3 Verify that the incoming cable is clean and firmly connected to the receive port associated with the facility. Clean
the connector or replace the cable, plug or module, as appropriate.
problem.
6 If problem continues, replace the module supporting the facility.
Fiber connection Replace the module supporting this facility.

Optical Power Tx
(OPT) Fault
Fiber connection 1 Verify that the fiber detection termination point entity is provisioned and in-service at the far-end of the fiber, and
Communications that fiber detection is enabled. Correct any provisioning errors.
error 2 Verify that the module at the far-end is correctly provisioned and equipped, and is operating error-free. Address any
error conditions reported at the far-end module or by the far-end fiber detection termination point.

Name Colors
U Yellow Fiber connection 1 Check if the firmware revision level of the modules at both ends of the fiber is the appropriate version for the
protocol fault software generic and module type. Upgrade any module found to contain an incorrect firmware load revision level.
2 Verify that the optical connectors associated with each end of the fiber are securely attached, and tighten/firmly
insert any loose connectors.
3 Inspect the fiber. Replace any fiber which is of the wrong type or specification, which has been bent beyond the
allowable minimum bend radius, or which has sustained any physical damage.
4 Inspect the fiber connectors at each end of the fiber and clean each connector. Verify that the connectors are
undamaged. Test the optical fiber cable to verify that it meets engineering specifications for the application, and
that there are no internal fiber breaks or excessive loss due to failures which are not readily apparent from visual
inspection. Replace any damaged component (cable or module, if the connector on the module is damaged).
5 Verify that the optical source for the fiber connectivity check signals of the modules at the far-end of the fiber is
operating within expected optical signal power limits. Replace any module found to operate outside the specified
limits.
Fiber connection data 1 Verify that the facility is provisioned correctly.

fault 2 Verify that the network port is correctly cabled.
problem.

Name Colors
U Yellow Fiber Detection 1 Verify that the optical connectors associated with each end of the fiber are securely attached, and tighten/firmly
flashing to Attenuation High, Tx insert any loose connectors.
off and/or Rx 2 Inspect the fiber. Replace any fiber which is of the wrong type or specification, which has been bent beyond the
allowable minimum bend radius, or which has sustained any physical damage.
3 Inspect the fiber connectors at each end of the fiber and clean each connector. Verify that the connectors are
undamaged. Test the optical fiber cable to verify that it meets engineering specifications for the application, and
that there are no internal fiber breaks or excessive loss due to failures which are not readily apparent from visual
inspection. Replace any damaged component (cable or module, if the connector on the module is damaged).
4 Verify that the optical source for the fiber connectivity check signals of the modules at the far-end of the fiber is
operating within expected optical signal power limits. Replace any module found to operate outside the specified
limits.
Green No defects on this No action is required.

port. Pumps are up.
Output power is
within required limits.
The amplifier is
operating without
error.

Name Colors
U Off This port's 1 If the EDFA module is installed and provisioned (including the N and U interfaces), check the administrative state
administrative state settings. If the management system displays “disabled”, change the administrative state to “In Service”.
is "disabled" or the 2 Ensure Fiber Detection is enabled.
module is unassigned
3 If the EDFA module is not provisioned or the N and U interfaces are not yet provisioned, initiate the provisioning
and
Fiber Detection process.
feature is disabled, or
Fiber Detection
feature is enabled
and PTP ADMIN
state is disabled, or
no fiber detection
conditions exist.
2EDFA-S20L-S10L Modules
This subsection will help you resolve issues that might be experienced on 2EDFA-S20L-S10L modules. It is assumed that the measurements for all interfaces are within
CAUTION
Representative.
Note
Each 2EDFA-S20L-S10L module has four LEDs on its faceplate:

Note
Table 92: LED Status of the 2EDFA-S20L-S10L Modules
If the condition continues, return the module to ADVA Optical Networking for repair.
P Yellow Power abnormal Remove and reinsert the EDFA module. If the condition continues, return the module to
Off Power failed Return the EDFA module to ADVA Optical Networking for repair.
Yellow blinking to Management communication is 1 Check the SCU and amplifier firmware version. Update the firmware if required.
off broken. 2 If the issue is not resolved, remove and reinsert the SCU.
Green Module provisioned, administrative 1 If the EDFA module is installed and provisioned, check the administrative state
state is “Maintenance”, settings.
“Management”, “In Service” or 2 If the management system displays “disabled”, change the administrative state to
“Auto In Service” “In Service”.
Off The EDFA module is disabled or Initiate the provisioning process, or set the administrative state to "In Service",
not provisioned. "Maintenance", "Management", or "Auto In Service".
N Red blinking to Booster EDFA shut down due to This condition occurs to avoid possible damage to the EDFA module due to excessive
off temperature. component temperatures.
3 Verify the module placement and that the surrounding equipment contained within
the same shelf conform to the product’s engineering guidelines.
The Booster EDFA pump shut 1 Ensure the input power to the amplifier is in the recommended range.
down for laser safety reasons, 2 Ensure the pilot signal is present and the gain is not too high.
since the output power exceeded
the recommended range.
The Booster EDFA pump shut Troubleshoot the LOS condition at the far-end amplifier.
down due to Automatic Power
Shutdown (APS)1, indicating a
possible LOS condition at the far-
end amplifier.
1The APS feature must be supported and enabled.
N Yellow Loss of Signal (LOS) 1 Verify that the facility is provisioned correctly.
to the required specifications.
4 If the signal meets the required specifications, locate the source of the signal
problem upstream and repair the problem.
OSC OPT power control high or 1 Verify that the EDFA module is connected to the OSC module and that OSC signal
low is present at the EDFA module.
3 Based on indicator (high or low); check the OSC optical power level from the OSC
module and verify it is within specification.
4 If the issue is not resolved, replace the EDFA module
Booster EDFA temperature 1 Verify that the equipment operating environment for the shelf containing the module
high/low threshold meets specifications, and that the air filter is clean and unobstructed.
N Yellow Booster EDFA GAIN/TILT 1 Measure the optical input power on the receiver connector to verify that the value is
abnormal, VOACTRL Fail within specifications.
2 Check gain/tilt settings.
3 Remove and reinsert the module. If the condition persists, return this EDFA to
Loss of OSC (LOSC) 1 Verify that the network port is correctly connected.
2 Verify that the OSC facility transmitted by the far end is correctly configured,
operating normally, and is correctly connected to the transmission fiber.
Booster EDFA laser EOL Replace the EDFA module.
Green The EDFA is operating normally No action is required.

without any facility defects.
Off The port administrative state is 1 If the EDFA module is installed and provisioned (including the N and U interfaces),
disabled or this interface is ensure that the administrative state is “In Service”.
unassigned. 2 If the EDFA module or the N interface is not provisioned, provision it.
U Red blinking to Fiber connection invalid, Tx and/or 1 Carefully trace the fiber to the far-end port and determine to which port the fiber is
off Rx connected. If required, adjust the fiber connections at either or both ends, so they
conform to the intended fiber connection provisioning plan.
2 If the condition persists, replace the module at the far-end of the fiber.
Fiber connection mismatch, Tx 1 Carefully trace the fiber to the far-end port and determine to which port the fiber is
and/or Rx connected. If required, adjust the fiber connections at either or both ends, so they
conform to the intended fiber connection provisioning plan.
2 If the condition persists, replace the module at the far-end of the fiber.
Pre-amplifier EDFA shut down due This condition occurs to avoid possible damage to the EDFA module due to excessive
to temperature component temperatures.
Pre-amplifier EDFA pump shut Troubleshoot the LOS condition at the N port.
down due to a LOS condition at the
network (N) port.
U Yellow Pre-amplifier temperature high/low 1 Verify that the equipment operating environment for the shelf containing the module
threshold meets specifications, and that the air filter is clean and unobstructed.
Loss of signal 1 Verify that the facility is provisioned correctly.

2 Verify that the upgrade port is correctly cabled.
Pre-amplifier Gain/Tilt abnormal 1 Measure the optical input power on the receiver connector to verify that the value is
2 Check gain/tilt settings.
3 Remove and reinsert the module. If the condition persists, return this EDFA to
U Yellow OPR Threshold (high/low) 1 Verify that a signal is present at the cable termination and that the signal conforms
to power level specifications.
problem upstream and repair the problem. It may be necessary to pad the span to
bring the attenuation within the required minimum range.
OPT Threshold (high/low) 1 Verify that a signal is present at the cable termination and that the signal conforms
to power level specifications.
Fiber connection Loss of Signal 1 Verify that the facility is provisioned correctly.
2 Verify that the upgrade port is correctly cabled.
Fiber connection Optical Power Tx Replace the module supporting this facility.
(OPT) Fault
U Yellow Fiber connection Communications 1 Verify that the fiber detection termination point entity is provisioned and in-service
error at the far-end of the fiber, and that fiber detection is enabled. Correct any
provisioning errors.
2 Verify that the module at the far-end is correctly provisioned and equipped, and is
operating error-free. Address any error conditions reported at the far-end module or
by the far-end fiber detection termination point.
Fiber connection protocol fault 1 Check if the firmware revision level of the modules at both ends of the fiber is the
appropriate version for the software generic and module type. Upgrade any module
found to contain an incorrect firmware load revision level.
2 Verify that the optical connectors associated with each end of the fiber are securely
attached, and tighten/firmly insert any loose connectors.
3 Inspect the fiber. Replace any fiber which is of the wrong type or specification,
which has been bent beyond the allowable minimum bend radius, or which has
sustained any physical damage.
4 Inspect the fiber connectors at each end of the fiber and clean each connector.
Verify that the connectors are undamaged. Test the optical fiber cable to verify that
it meets engineering specifications for the application, and that there are no internal
fiber breaks or excessive loss due to failures which are not readily apparent from
visual inspection. Replace any damaged component (cable or module, if the
connector on the module is damaged).
5 Verify that the optical source for the fiber connectivity check signals of the modules
at the far-end of the fiber is operating within expected optical signal power limits.
Replace any module found to operate outside the specified limits.
U Yellow Fiber connection data fault 1 Verify that the facility is provisioned correctly.
Pre-amplifier EDFA Laser EOL Replace the EDFA module.
Yellow flashing to Fiber Detection Attenuation High, 1 Verify that the optical connectors associated with each end of the fiber are securely
off Tx and/or Rx attached, and tighten/firmly insert any loose connectors.
2 Inspect the fiber. Replace any fiber which is of the wrong type or specification,
which has been bent beyond the allowable minimum bend radius, or which has
3 Inspect the fiber connectors at each end of the fiber and clean each connector.
Verify that the connectors are undamaged. Test the optical fiber cable to verify that
it meets engineering specifications for the application, and that there are no internal
fiber breaks or excessive loss due to failures which are not readily apparent from
visual inspection. Replace any damaged component (cable or module, if the
4 Verify that the optical source for the fiber connectivity check signals of the modules
at the far-end of the fiber is operating within expected optical signal power limits.
Replace any module found to operate outside the specified limits.
U Green No defects on this port. Pumps are No action is required.

up. Output power is within required
limits. The amplifier is operating
without error.
Off This port's administrative state is 1 If the EDFA module is installed and provisioned (including the N and U interfaces),
"disabled" or the module is check the administrative state settings. If the management system displays
unassigned and Fiber Detection “disabled”, change the administrative state to “In Service”.
feature is disabled, or Fiber 2 Ensure Fiber Detection is enabled.
Detection feature is enabled and
3 If the EDFA module is not provisioned or the N and U interfaces are not yet
PTP ADMIN state is disabled, or
provisioned, initiate the provisioning process.
no fiber detection conditions exist.
Chapter 11
Dispersion Compensation Modules

This chapter addresses LED indicators and troubleshooting guidelines for dispersion
compensation modules (DCMs).
The following dispersion compensation module types are available:
• DCF-M/xxx/SSMF (Dispersion compensation fiber module)
• DCG-M/xxx/SSMF (Fiber-Bragg-Grating Dispersion Compensation Module)
• DCG50-M/xxx/SSMF (Fiber-Bragg-Grating Dispersion Compensation Module for 50
GHz channel grid)
• DCG-M/xxx/TWRS (Fiber-Bragg-Grating Dispersion Compensation Module)
• DCG50-M/xxx/TWRS (Fiber-Bragg-Grating Dispersion Compensation Module for 50
GHz channel grid)
All dispersion compensation modules provide the same single LED indicator on the
faceplate. This indicator is named “P” and it indicates the operation status of the module.
This section assists you to resolve issues that you may encounter when installing or
operating dispersion compensation modules.
Before you begin troubleshooting, ensure that the current firmware

package is installed on the DCM. For details on updating module
firmware, refer to “Updating the NE Software Release” on p. 617 and
Note “Performing Other Software Update Actions” on p. 628.
Before you start with troubleshooting, ensure that the administrative

state of the affected module is in maintenance mode.
Note
If your module has an LED status that is not represented in Table 93 on

p. 508, please contact your ADVA Optical Networking Technical
Note
Table 93: LED Status of the Dispersion Compensation Modules

Name Colors
P Red A serious error in card Remove the module from its shelf
initialization. slot for 10 seconds to allow the
capacitor(s) to discharge, and then
reinsert the module into the shelf
slot. If the fault condition persists,
return the module to ADVA Optical
Off Power source has failed. Check the LED of the PSUs.
The NCU receives no • If the status LED indicator (P)
power. on the PSU module is not lit,
refer to “Troubleshooting Power
• If the status LED indicator on
the PSU module is green, then
the hardware is faulty. Return
the module to ADVA Optical
Networking.
Chapter 12
NCU Troubleshooting
This chapter provides procedures for troubleshooting first and second generation NCUs.
First generation NCUs are:
• NCU-A
• NCU-B
• NCU-GDPS
• NCU2E
The second generation NCUs are:
• NCU-II
• NCU-II-P
• NCU-S
In the following sections, NCU is used to refer to any NCU type:
“Viewing IP Addresses” on p. 510
“Setting NCU Passwords to Default Values” on p. 511
“Restarting the NCU” on p. 517
“Deleting the Active Database” on p. 520
“Replacing the NCU Compact Flash” on p. 521
“Replacing an NCU” on p. 526
For hardware and equipping details of the different NCU types, refer to
the “Management and Switch Modules” chapter in the Hardware
Description.
Note For details on NCU-II-P and associated SCU-II modules, refer to the
“High Availability” chapter in the System Description.
Viewing IP Addresses
Viewing IP Addresses
Follow this procedure to view the IP addresses used in the NE.
Step 1 Select .
Step 2 In the Navigation Tree, select Management Network.
Step 3 In the Main Pane:
• The system IP address is under the System blade.
• The NCU port IP addresses are under the Management Ports blade.
• The management channels (for example, GCCs) IP addresses are under
the Management Channels blade.
• Routing information can be found under the Routes, OSPF Areas, and
OSPF Neighbors blades.
Setting NCU Passwords to Default Values

This section describes the procedures for resetting NCU passwords to default for first
and second generation NCUs.
Access to the boot loader must be enabled to reset NCU passwords

during NCU reboot. Access to the boot loader is disabled if the following
messages do NOT appear on serial port during the boot process:
“Press space to abort autoboot in 2 seconds” (first
generation NCU)
Note or
“Autobooting in 3 seconds” (second generation NCU)
Password reset via boot loader is not possible in this case.
About Default Passwords

When using the boot loader feature to reset the password, NE user settings are reset to
default, while all other NE settings remain unchanged.
After the reset, there is only a single user ADMIN with admin privileges. The security
mode is not changed by the reset:
• When in BASIC security mode, the default user <ADMIN> has the password
<CHGME.1A>.
• When in ENHANCED security mode, the default user <ADMIN> has the password
<ChangeMe.1Now!2>.
The security mode is visible from the Security > Access > Password Management
blade, under the application.

Follow the procedure that corresponds to the NCU type in the NE to reset the password
to default:
“Resetting Passwords in First Generation NCUs” on p. 512
“Resetting Passwords in Second Generation NCUs” on p. 514
“Controlling Boot Loader Access” on p. 516
Requirements
• Your computer must be connected to the NE with a serial cable.
• For information about establishing a serial connection, refer to the “Connecting to the
Network Element” section in the Provisioning and Operations Manual.
Resetting Passwords in First Generation NCUs

Follow this procedure to reset the NCU-A, NCU-B, NCU-GDPS, or NCU2E password to
default.
Step 1 Set the COM port for the serial interface on the PC as follows:
Step 2 Log on to the NCU.

Step 3 Press the Reset button located on the faceplate of the NCU to restart it.
In response, the boot loader output is displayed. Figure 18 on p. 513 shows an
example output.
Figure 18: Boot Loader Output of a First Generation NCU
Step 4 As soon as the line “Press space to abort autoboot in 2

seconds” is displayed in the boot loader output, press the space bar on your
keyboard.
The NCU boot process is interrupted and a => prompt appears. Follow these
steps to reset the password:
a) Type setenv resetpasswords yes and press ENTER.
b) Type saveenv and press ENTER.
The screen displays the following text:

Saving Environment to EEPROM...
c) Type reset and press ENTER.
The following actions take place:
• The NCU will restart.
• When the restart is complete, all previously provisioned user accounts are
deleted..
• The default user accounts are restored:
• You may now logon with the ADMIN privilege level user account
(username "admin") and the password (depending on the security
mode, this is either “CHGME.1A” or “ChangeMe.1Now!2”).
• You may then reprovision user accounts.
No other provisioning information in the system is affected by this procedure.
Resetting Passwords in Second Generation NCUs

Follow this procedure to reset the NCU-II, NCU-S, or NCU-II-P users and password to
the defaults.
Step 1 Set the COM port for the serial interface on the PC as follows.
Step 2 Log on to the NCU.

Step 3 Press the Reset button located on the faceplate of the NCU to restart it.
In response, the boot loader output is displayed. Figure 19 on p. 515 shows an
example output.
Figure 19: Boot Loader Output of a Second Generation NCU
Step 4 As soon as the line “Autobooting in 3 seconds” is displayed in the

boot loader output, press “q” or “Q” on your keyboard.
The NCU boot process is interrupted and a => prompt appears. Follow these
steps to reset the password:
a) Type setenv resetpasswords yes and press ENTER.
b) Type saveenv and press ENTER.
The screen displays the following text:

Saving Environment to EEPROM...
c) Type reset and press ENTER.
The following actions take place:
• The NCU will restart.
• When the restart is complete, all previously provisioned user accounts are
deleted..
• The default user accounts are restored:
• You may now logon with the ADMIN privilege level user account
(username "admin") and the password (depending on the security
mode, this is either “CHGME.1A” or “ChangeMe.1Now!2”).
• You may then reprovision user accounts.
No other provisioning information in the system is affected by this procedure.
Controlling Boot Loader Access

Access to the boot loader allows full access to the system. By default, this is enabled.
This can be disabled for security reasons.
If boot loader access is disabled, a reset to the default password is not

possible.
Note
Requirement
You must be logged on with an ADMIN privilege level user account.
Step 1 Select .
Step 2 In the Navigation Tree, select Security > Access.
Step 3 Within the Access Management blade, set NCU Boot Loader Access:
• Select Disable to disable the boot loader process.
Disable means that the boot process cannot be interrupted to access

the boot loader.
Note
• Select Enable to enable the boot loader process. This setting will allow
you to interrupt the boot loader process to reset NCU passwords to default
values.
Step 4 Select to activate this setting.
Restarting the NCU
Restarting the NCU

The NCU can be restarted using one of these methods.
• A warm start is non-service affecting and is executed remotely using the
management system, as described in “Warm-Starting the NCU” on p. 517.
• A cold start clears any active loopbacks, interferes with protection functions, and
interrupts management traffic. It requires a technician to be present on-site. Hence
cold starts should only be executed in rare situations such as when the NCU is
inaccessible to the management system. For further details, refer to “Cold-Starting
the NCU” on p. 518.
After an NCU restart is complete, ROADM-C80/0/OPM, 8ROADM-

C40/0/OPM, and 8ROADM-C80/0/OPM modules are equalized
automatically.
Note
Warm-Starting the NCU

The NCU may be restarted without interrupting traffic. The restart performs the following:
• Restarts the NCU software
• Clears any alarm which is no longer present
• Clears the alarm log
• Clears current and historical performance records
Requirements
You must be logged in to the NE with an ADMIN privilege level user account.
Step 1 Select .
Step 2 In the Navigation Tree, select Shelf 1 > NCU Slot.
In a redundant NCU-II configuration, select the active NCU slot.
Step 3 In the NCU equipment view, select .

The following warning appears:
Restarting the NCU
Step 4 Select to proceed or Cancel to abort.
In response to , the NCU shuts down. You will lose connection to

the NE.
The NE is ready for operation within approximately five minutes. After four
consecutive beeps, the NCU MOD LED changes from blinking to solid green.
This indicates that the NCU has completed the restart and you can log in.
Cold-Starting the NCU
Cold-starting the NCU should only be executed in rare cases, e.g. if no

logon is possible.
Note
A cold start of the NCU initializes all hardware and any configurations of the NE.
A cold start may be applied after powering up the system or after upgrading software
(including a new NCU load).
The initiation of a cold start can result in the following:
• reloading and reprovisioning of all hardware
• clearing of all alarms for which the condition to raise that alarm is no longer present
• clearing of the alarm log
• clearing of all performance data, current records and historical records
• removal of all active loopback settings
• management traffic interruption
To cold start the NCU, press and release the Reset button located on the NCU faceplate,
as shown in Figure 20 on p. 519. If required, use a pointed tool.
Restarting the NCU
Figure 20: Example of the Reset Button on the NCU2E Faceplate
After pressing the Reset button, the NCU shuts down and you will lose connection to the
NE. Traffic will not be affected. The NE is ready for operation within approximately five
minutes. After four consecutive beeps, the NCU MOD LED changes from blinking to
solid green. This indicates that the NCU has completed the restart and you can log in.
Deleting the Active Database
Deleting the Active Database
This procedure sets the active database to its default settings. Resetting the database to
factory defaults does not affect traffic. However, rebooting the NCU after the database
has been reset to factory defaults will cause a traffic outage!
Deleting the active database should only be done for special cases such as de-
commissioning the NE. The default settings resulting from this action depend on the
release. For an overview of default settings in this release, refer to the “Security
Management” chapter in the System Description.
In an NE operating with redundant controllers, resetting the database to

default causes the NCU-II-P in the lower numbered slot to become the
active controller.
Note
Requirements
You must be logged on with an ADMIN privilege level account.
Step 1 Select .
Step 2 In the Navigation Tree, select Database > Manage.
Step 3 In the Reset to Defaults blade, select .

The following warning appears:
Reset of the NCU database also resets the IP configuration to the

default settings. Remote IP connectivity will be lost, the NE can only be
accessed while on site with a serial connection or via an NCU Ethernet
Note connection using the default IP address.
Step 4 Confirm with .

The active database switches to the standby partition on the NCU in case
recovery is needed at a later time.
Replacing the NCU Compact Flash

This section is divided into the following subsections:
“Removing the NCU Compact Flash ” on p. 521
“Installing Compact Flash in an NCU” on p. 523
Removing the NCU Compact Flash

This section describes the procedure to remove the compact flash card from a defective
NCU.

CAUTION
To avoid ESD damage to the equipment take normal static precautions

for removing modules.
It is assumed that you are familiar with handling NCU modules and are aware of the
precautions that should be taken to avoid damage to the equipment.
The Compact Flash card can only be removed when the NCU has been extracted from
the shelf. The photos shown in this section are examples for NCUs that fit in slots A and
B.
Requirements
• ESD-preventive wrist strap or other personal grounding device.
• Suitable grounded surface or an antistatic mat to place the NCU.
Step 1 Place an antistatic mat on a flat, stable surface to receive the NCU.
Step 2 Attach a wrist strap to your wrist and insert the grounding cable into the ESD
grounding point.
Step 3 Place the NCU on the antistatic mat as shown in Figure 21 on p. 522.
Figure 21: NCU Placement for Compact Flash Card Removal
Step 4 Using your fingers, grasp the locking plate on both sides and pull it out of the
NCU completely, as shown in Figure 22.
Figure 22: Remove the Locking Plate from the Slot
Step 5 Insert the locking plate through the opening in the cover into the gaps between
the connector and the Compact Flash card, as shown in Figure 23.
Figure 23: Unlock the Compact Flash Card
Step 6 Push the locking plate in the direction of the arrow to unlock the Compact
Flash card. It slides out of the slot slightly, as shown in Figure 24 on p. 523.
Figure 24: Remove the Compact Flash Card from the Slot
Step 7 Remove the locking plate from the opening and lay it aside.
Step 8 Pull the Compact Flash card the rest of the way out of the NCU.
Step 9 Place the Compact Flash card on the antistatic mat for insertion in the
replacement NCU, or in an electrostatic bag for later use.
Step 10 Keep the locking plate in a safe place for later use.
Installing Compact Flash in an NCU

This section describes the procedure to insert the Compact Flash card into a replacement
NCU.

CAUTION

for removing modules.
It is assumed that you are familiar with handling NCU modules and are aware of the
precautions that should be taken to avoid damage to the equipment.
The Compact Flash card can only be inserted into the replacement NCU if the unit has
been extracted from the shelf. The photos shown in this section are examples for NCUs
that fit in slots A and B.
Requirements
• ESD-preventive wrist strap or other personal grounding device.
• Suitable grounded surface or an antistatic mat for the NCU.
• Compact Flash card to be installed.
Step 1 Attach a wrist strap to your wrist and insert the grounding cable onto the ESD
grounding point.
Step 2 Place the NCU on the antistatic mat as shown in Figure 25.
Step 3 Ensure that the Compact Flash card is the correct type.
Step 4 Locate the electrical connector on the Compact Flash card.
Step 5 Hold the Compact Flash card on the narrow sides so the electrical connector is
pointing toward the slot opening and the product label is up.
Figure 25: Placement of the NCU for Inserting the Compact Flash Card
Step 6 Insert the CF card as follows:
The Compact Flash card can only be inserted completely when properly
aligned.
Note
a) In front of the slot opening on the NCU, align the narrow sides of the card
with the left and right tracks in the slot.
b) Once the card is in the correct position, gently slide it into the slot while
guiding the left-hand and right-hand edges of the card in the tracks as
shown in Figure 26.
Figure 26: Insert the Compact Flash Card into the Slot
The card is completely inserted when its front side is flush with the edge of the board
cover. If you are unable to fully insert the CF card, the alignment is probably incorrect.
Step 7 When the Compact Flash card is seated properly, insert the locking plate into
the slot to lock the Compact Flash card. Proceed as follows:
a) Hold the locking plate on the narrow sides so that its fingers face the slot
and the guide above is visible.
b) Align the locking plate with the slot and slide it into the gap above the
Compact Flash card, as shown in Figure 27.
Figure 27: Lock the Compact Flash Card by Inserting the Locking Plate
c) Gently push until the locking plate is flush with the aluminum shield on the
NCU. The Compact Flash card is locked into position.
Replacing an NCU
Replacing an NCU
This section describes the procedures to replace an NCU. Replacement is necessary
when:
• The NCU is malfunctioning.
• A newer NCU type is required.
The NCU should be replaced with the same NCU type or a newer version. The
replacement NCU needs to support all of the equipment installed in the NE.Generally:
• A first generation NCU (NCU-A, NCU-B, NCU-GDPS, or NCU2E) can be replaced
with another first generation NCU, or an NCU-II.
• An NCU-II can only be replaced with another NCU-II.
• An NCU-S can only be replaced with another NCU-S.
• An NCU-II-P can only be replaced with another NCU-II-P.
Examples in this chapter may slightly differ from your setup. Especially data such as IP
addresses and subnet masks are NE specific.
Please pay attention to the safety notices and additional information provided in this
section.
To avoid ESD damage to modules, take anti-static precautions when

replacing the NCU.
Table 94: Considerations when replacing a malfunctioning NCU
Database Backup Database Restoration
Database stored on SCU Database Auto Restore was set to Restore

from SCU prior to the malfunction. The SCU
will automatically restore the database when
the replacement NCU is installed. Follow
“Replacing a Malfunctioning NCU” on p. 530
through Step 13.
Database Auto Restore was set to None prior

to the malfunction. Follow “Replacing a
Malfunctioning NCU” on p. 530 and refer to
“Restoring the Database” on p. 614.
Database stored on a remote server Follow “Replacing a Malfunctioning NCU” on

p. 530 and refer to “Restoring the Database” on
p. 614.
Replacing an NCU
Table 95: Considerations when Replacing an NCU with a newer type
Database Backup Database Restoration
Database stored on SCU (set The SCU will automatically restore the database
Database Auto Restore to when the replacement NCU is installed. Follow
Restore from SCU prior to the “Replacing a First Generation NCU with an
replacement) NCU-II” on p. 537 through Step 13.
Database stored on a remote Follow “Replacing a First Generation NCU with an

server. NCU-II” on p. 537 and refer to “Restoring the
Database” on p. 614.
All requirements and additional information about replacing an NCU are addressed in
these sections:
“Basic Requirements” on p. 527
“Required Information” on p. 527
“Required Equipment” on p. 529
The following replacement procedures are based on the requirements provided in this
section:
“Replacing a Malfunctioning NCU” on p. 530
“Replacing a First Generation NCU with an NCU-II” on p. 537
Basic Requirements
The following requirements must be met before starting the replacement procedure:
• A current database backup has already been created and is accessible.
• A replacement NCU packaged in the shipping box is available and has the same
software version as the NCU to be replaced.
Required Information
Only Service Personnel are allowed to replace an NCU.

CAUTION
It is assumed that you are familiar with handling management modules, and are aware of
the precautions that should be taken to avoid damage to the equipment. In addition, you
should be familiar with FSP 3000R7 management software.
Connection Scenarios
During the replacement procedure, you will need to connect your management computer
to the NE. You also will need to have a connection between the NE and an FTP server to
download software updates and back up and restore database files. There are several
ways to make these connections, some of these scenarios are shown in Figure 28 on
p. 528. The database backup file can also be stored exclusively on the SCU, which
requires an SCU with hardware revision 2.01 or higher, an SCU-II, or an SCU-S. For
Replacing an NCU
information about backing up the database, refer to “Backing Up and Restoring the
Figure 28: NE, Management, and FTP Server Connection Options
1 2 3
NCU
NCU2E NCU Ser
USB2 Ser
USB1
C2 C
FTP C1 FTP C
FTP
4 5 6
NCU2E NCU2E
NCU
USB2
USB2
Ser
USB1
USB1
C2
C2
C1
FTP C1 C
FTP
front cable
OSCM
N
C3
FTP C2
C1
7 8 9
NCU
Ser
NCU2E NCU2E
USB2 USB2
USB1 USB1
C2 C2
C
C1 C1
front cable
FTP
backplane backplane
OSCM
N
OSCM OSCM
N N
C3
C2
C3 FTP C3
C2 C2
C1
C1 C1
FTP
You can manage the NE using a serial connection or an Ethernet connection. In general,
when you use a serial connection to manage the NE, you should not have any problems
accessing the NE after a reboot.
When you use an Ethernet connection between the management computer and the NCU,
pay attention to the following to successfully access the NCU:
• You must always know the IP address of the NCU Ethernet port.
• Ensure that the NCU Ethernet port is not disabled.
The NCU must have an Ethernet connection to an FTP server. The FTP server can either
be located on the management computer or in the same subnet as the NE.
If the FTP server is located on the management computer, use a direct Ethernet
connection between the management computer and the NCU. In this case, keep note of
the following:
• At all times you must know the IP address of the NCU Ethernet port that your
management computer is connected to.
• Adjust the management computer IP address to be in the same subnet if the NCU IP
address changes (for example, after a reboot following a database restoration you
may also have to adjust the computer IP address).
Replacing an NCU
If the FTP server is located in the network, connect the NE to the network. In this case,
keep note of the following:
• Set up the IP address of the NCU Ethernet port to have access to the network.
• Ensure that the NCU Ethernet port is not disabled.
• Ensure that routers are set up in a way that the NE and FTP server can reach each
other.
• Check if the OSCM Ethernet port needs to be connected to the network.
For reference, make note of the factory default IP addresses:
• NCU Ethernet port marked C or C1: 192.168.1.1
• NCU Ethernet port marked C2: 192.168.2.1
• NCU Ethernet port marked C3: 192.168.3.1
The default IP subnet mask is 255.255.255.0 for all NCU Ethernet ports.
The default system IP address is 192.168.254.1.
Gather the following information before beginning the replacement procedure:
• The IP address, user account name, and password for an FTP server that is
reachable from the NE (only if a database backup file will be moved from the NCU to
the management computer using FTP).
• If the replacement module is not a new NCU and an Ethernet connection will be used
for management, you will need the IP address that the NCU last had.
Required Equipment
This equipment should be present on site before starting the replacement procedure:
• Torx screwdriver TX10 for loosening the knurled screws, if necessary
• ESD-preventive wrist strap or other personal grounding device
• Suitable grounded surface or an antistatic mat for placing the NCU
• Management computer or laptop with
o
an FTP server installed (only if a database backup file will be moved from the
NCU to the management computer using FTP)
o
a free serial port (EIA/TIA-232) for connecting to NCU-A/NCU-B/NCU-
GDPS/NCU-II/NCU-II-P or a free USB port for connecting to the
NCU2E/NCU-II/NCU-S/NCU-II-P
• a serial null modem cable or a standard USB cable
• an Ethernet cable or Ethernet crossover cable
USB connections require a respective driver on the management

computer. This driver is available on the User Documentation Suite CD
or can be obtained from ADVA Optical Networking.
Note
Replacing an NCU
Replacing a Malfunctioning NCU

This section describes how to replace a malfunctioning NCU with an NCU of the same
type or of any other available type, given the following conditions:
• A first generation NCU (NCU-A, NCU-B, NCU-GDPS, or NCU2E) can be replaced
with another first generation NCU, or an NCU-II (the latter case is considered an
upgrade, as detailed in “Replacing a First Generation NCU with an NCU-II” on
p. 537).
• An NCU-II can only be replaced with another NCU-II.
• An NCU-S can only be replaced with another NCU-S.
• An NCU-II-P can only be replaced with another NCU-II-P.
A malfunctioning NCU can be swapped out while the shelf is up and running.
Replacement does not affect the operation of other modules installed in the shelf or data
services.
If the malfunctioning module is a first generation NCU, an NCU-II, an NCU-S, or an
NCU-II-P in an unprotected configuration, or if both NCU-II-IPs in a protected
configuration are malfunctioning, management services may have already been
interrupted depending on the malfunction. The NCU is the controlling device for
management services. As soon as the NCU is removed from the shelf, management
traffic is definitely interrupted.
For a malfunctioning NCU-II-P in a protected (redundant) configuration where the partner
NCU-II-P is operating normally, management traffic is not interrupted. Only Step 1 to
Step 11 of this procedure are relevant for replacing this NCU-II-P. Once replaced, the
new NCU-II-P synchronizes with the partner NCU-II-P, copying over all relevant
configuration information.
Table 96 summarizes the NCU replacement scenarios addressed in this section. In a
system equipped with an NCU-S, the database backup is only available on a remote
server.
Table 96: NCU Replacement Scenarios
Database backup Auto Restore from NCU Status Database Outcome

available in SCU? SCU enabled?
Yes Yes New Database copied from SCU

automatically.
Yes No New Restore database from SCU.
No Not Applicable New Restore database from a remote

server/NMS.
If a database backup is unavailable,

create services manually1.
Yes Yes NCU from another Database copied from SCU

chassis with factory automatically.
default database
1This action is service-affecting!
Replacing an NCU
Yes No NCU from another 1 If auxiliary database is displayed,

chassis with factory reset to factory default.
default database 2 Restore database from the SCU.
No Not Applicable NCU from another 1 If auxiliary database is displayed,

chassis with factory reset to factory default.
default database 2 Restore database from a remote
server/NMS.
1 If auxiliary database is displayed,

reset to factory default.
2 Given that a database backup is
unavailable, create services
manually1.
Yes Yes NCU from another Database copied from SCU

chassis with existing automatically.
database
Yes No NCU from another Auxiliary database displayed. Set to

chassis with existing factory default, then restore database
database from SCU.
No Not Applicable NCU from another Auxiliary database displayed. Set to

chassis with existing factory default, then restore database
database from a remote server/NMS.
Auxiliary database displayed. Reset to

factory default, then create services
manually if a database backup is
unavailable1.
Each NCU can be replaced without the use of any tools. However, to loosen a knurled
screw that is screwed in too tightly, use an appropriate torx driver.
Ensure you have met all requirements described in these sections:
• “Basic Requirements” on p. 527
• “Required Information” on p. 527
• “Required Equipment” on p. 529
“Management and Switch Modules” in the Hardware Description.
Note
Step 1 Attach a wrist strap to your wrist and fasten the grounding wire onto the ESD
grounding point on the shelf (if available) or to a bare metal surface onto the
rack.
Step 2 If mounted, remove the front cover from the master shelf.
1This action is service-affecting!
Replacing an NCU
Step 3 Identify the NCU to be replaced.

Step 4 Remove all cables from the NCU:
a) Disconnect any serial null modem cable/USB cable and Ethernet cable
from the NCU and lay them aside.
b) If the NCU is connected to an OSCM, disconnect the cable.
Step 5 Remove the NCU from the shelf slot as follows:
a) Using your fingers or a Torx screwdriver TX10, turn the two knurled
screws in a counter-clockwise direction until they are free from the shelf.
Hot Surface!
The NCU can become very hot during operation. Touching a very hot
component may cause skin burns. Allow the module to cool before
removing it from the shelf slot. Place only cooled modules in the static-
CAUTION
protective package.
b) Firmly pull on the screws until the module is free from the shelf and
carefully slide the module straight out of the slot while holding it by both
screws as shown in Figure 29.
The slot position shown in Figure 29 apply to first generation NCUs and
NCU-II. NCU-S modules are equipped in slot B in the slimline shelves,
while NCU-II-P modules are equipped in slots 3 and 18 in SH9HU
shelves.
Figure 29: Removing an NCU Module from Slot A of an SH7HU Shelf
Never reach into the vacant shelf slot. Contact with the adjacent modules or the
connectors on the backplane could result in damage to the equipment.
Replacing an NCU
c) Put the module onto a grounded surface or an antistatic mat and let it cool
down.
d) As soon as the module has cooled down, place it in the original static-
protective package to avoid ESD damage to the module.
e) Put the static-protective package back into the original shipping box and
lay the box aside.
Step 6 Take the replacement module out of the shipping box.
Step 7 Remove it from the static-protective package and immediately place it onto a
grounded surface or an antistatic mat to avoid ESD damage to the module.
Step 8 Check and prepare the replacement module as follows:
a) Make sure that the module is the correct one for installation (type and
specifications). To quickly obtain this information, refer to the faceplate
markings and the labels on the board cover.
b) Inspect the module visually for damage and impurities. If necessary, use
canned, dry, oil-free compressed air to blow off any possible dust
particles. If a contact strip is loose, torn, or otherwise defective, do not
install this module. Return the module for repair.
Risk of electromagnetic disturbances!

Make sure that the EMC contact strips are not damaged before inserting the module.
Otherwise, EMC compliance cannot be achieved.
Step 9 Insert the replacement module into the empty slot as follows:
a) Hold the module by both screws, as shown in Figure 30 on p. 534, or by
the faceplate.
The slot position shown in Figure 30 on p. 534 apply to first generation
NCUs and NCU-II. NCU-S modules are equipped in slot B in slimline
shelves, while NCU-II-P modules are equipped in slots 3 and 18 in
SH9HU shelves.
Replacing an NCU
Figure 30: Inserting an NCU into Slot A of an SH7HU Shelf
b) Align the upper and lower edges of the module with the upper and lower
tracks in the slot. If the module is in the correct position, carefully slide it
into the slot a few millimeters while guiding the upper and lower edges of
the module in the tracks.
c) Using moderate force, push gently until the module connectors mate
properly with the backplane connectors.
Risk of module damage!

If you need a force greater than 45 Newton (10.1 lbf) to push in the module, stop
immediately.
d) Ensure that the module is properly and completely inserted into the slot.
The module is properly and completely inserted when
• its faceplate is flush with the faceplates of the adjacent modules and
the shelf panels
• it receives power.
Step 10 While the replacement module restarts, the MOD LED blinks. The restart is
completed when the NCU beeps four times and the MOD LED changes from
blinking to solid green. Check also the P LED to ensure that the module is
operating correctly. Refer to the module LED indicator description in
“Management and Switch Modules” on p. 385.
If the module does not respond, remove it from the slot. Insert a dummy
module into the empty slot.
Note
Replacing an NCU
Step 11 When the replacement module operates properly, secure it tightly in the slot as
follows:
a) Hold the module in place with your left hand and simultaneously turn the
two attached knurled screws clockwise into the threaded holes using the
thumb and forefinger of your right hand.
b) Tighten the screws.
Step 12 Skip the remaining steps of this procedure for these scenarios:
• If you just replaced an NCU-II-P in a protected configuration where the
partner NCU-II-P is operating normally.
• If the database backup is stored on the SCU, Database Auto Restore
was set to Restore from SCU before the NCU malfunction, and the
database backup is based on the same software version as the
replacement NCU.
For all other scenarios and NCU types, including NCU-II-Ps in a protected
configuration where the partner NCU-II-P also needs to be replaced, proceed
to Step 13.
Step 13 Connect your management computer to the NCU using a serial connection, as
described in “Connecting to the Network Element” in the Provisioning and
Operations Manual.
Step 14 Log on the replaced NCU using HyperTerminal and open the Craft Console.
The communication between the management computer and the NCU will run
over the serial cable. The following warning window is displayed:
Since the new NCU has been detected in the shelf for the first time, the
“DBACT_MEA” condition will be present. This alarm indicates that there could
be a database mismatch. An auxiliary database is therefore used to prevent
services interruption. In this case, proceed to Step 15.
However, if the replaced NCU was never installed in another shelf previously,
the above message will not be displayed and the “DBACT_MEA” condition is
not raised. In this case, proceed to Step 16.
Step 15 Select OK to acknowledge the warning related to the “DBACT_MEA”
condition.
The NCU must now be reset to use the default database instead of the
auxiliary database. To reset the NCU, follow these steps:
a) Navigate to System Management > Software and Database Control
and select the Database tab.
b) Select [Reset to Factory Default] and confirm with [OK].
In response, the NE restarts and you will lose connection to the NE. After
four consecutive beeps, the NCU MOD LED changes from blinking to
solid green. This indicates that the NCU has completed the restart and you
can log in.
Replacing an NCU
c) Log on to the NE using HyperTerminal to access the Craft Console.

Step 16 Configure the NE IP address to the value that the previous NCU had:
a) Connect an Ethernet cable between the network and the NCU’s Ethernet
port.
NCU-A, NCU-B and NCU-GDPS have Ethernet port C
NCU2E and NCU-II have Ethernet ports C1 and C2
NCU-S has Ethernet port C1
NCU-II-P has Ethernet ports C1, C2 and C3
b) Navigate to System Management > System IP Settings > Default
Gateway, and enter the default gateway.
c) For first generation NCUs, NCU-S, and NCU-II, enter the correct IP
address and range for SC-1-A-{C|C1|C2} by selecting Service
Management > SHELF-1 > MOD-1-A NCU{2E|-II|-X}.
For NCU-II-P, enter the correct IP address and range for SC-NCU-
{C1|C2|C3} by selecting Service Management > SHELF-1 > MOD-1-x
NCU-II-P.
d) Check which NCU port (C, C1, C2, or C3) was used for the Ethernet
connection, depending on the NCU type:
For first generation NCUs, NCU-S, and Assign (create) it.

NCU-II, if the dependent entity SC-1-A-
{C|C1|C2} is displayed with the text “[UAS]”
beside it, the entity is unassigned.
For NCU-II-P, if the dependent entity SC-
NCU-{C1|C2|C3} is displayed with the text
“[UAS]” beside it, the entity is unassigned.
For first generation NCUs, NCU-S, and Configure the IP address and
NCU-II, if the dependent entity SC-1-A- range for this entity.
{C|C1|C2} is displayed without the text
“[UAS]” beside it, the entity is assigned.
For NCU-II-P, if the dependent entity SC-
NCU-{C1|C2|C3} is displayed without the text
“[UAS]” beside it, the entity is assigned.
For more information about assigning and configuring the LAN IP

interface, refer to “Configuring Ethernet Interfaces” in the Provisioning
and Operations Manual.
Note
Step 17 After you have provisioned the LAN IP interface, a window will be displayed,
prompting you to restart the NCU. Select OK.
You will lose connection to the NE. After four consecutive beeps, the
NCU MOD LED changes from blinking to solid green. This indicates that the
NCU has completed the restart and you can log in.
Step 18 Log on to the NE using NED.
Step 19 Check whether the new NCU's software version matches the software version
associated with the database backup.
Step 20 If required, update the NCU software to match the software version associated
with the database backup, as described in “Updating the NE Software
Release” on p. 617.
Replacing an NCU
Step 21 If the database backup is located on a remote server and it was renamed
during storage, ensure its name has the extension *.DBS.
Step 22 Restore the database from the remote server or SCU, as described in
“Restoring the Database” on p. 614.
If you just replaced and configured an NCU-II-P in a protected configuration
where the partner NCU-II-P also needs to be replaced, repeat Step 1 to Step
11 of this procedure to replace the partner NCU-II-P.
Replacing a First Generation NCU with an NCU-II

This section describes how to replace a first generation NCU with an NCU-II. First
generation NCUs are the NCU-A, NCU-B, NCU-GDPS, and NCU2E.
Replacement can be carried out while the shelf is up and running. It does not affect the
operation of other modules installed in the shelf or data services. However, management
services will be interrupted as soon as the NCU has been removed from the shelf
because the NCU is the managing device for these types of services.
Each NCU can be replaced without the use of any tools. However, to loosen a knurled
screw that is screwed in too tightly, use an appropriate torxdriver.
Ensure you have met all requirements described in these sections:
• “Basic Requirements” on p. 527
• “Required Information” on p. 527
• “Required Equipment” on p. 529
“Management and Switch Modules” in the Hardware Description.
Note
Connections associated with PTP-1-A-C are removed after exchanging

a first generation NCU with an NCU-II.
Note
Step 1 Back up the active database as described in “Backing Up the Database” on

p. 610. Back up the database to the SCU and set Database Auto Restore to
Restore from SCU, or upload the backup file to a remote server.
To upload the database backup to a remote server, refer to “Uploading Files
from the NCU” on p. 633.
rack.
Step 3 If mounted, remove the front cover from the master shelf.
Step 4 Identify the NCU to be replaced.
Replacing an NCU
Step 5 Remove all cables from the NCU:

Step 6 Remove the present NCU from the shelf slot as follows:
Hot Surface!
removing it from the shelf slot. Put only cooled modules into the static-
CAUTION
protective package.
screws as shown in Figure 31.
Figure 31: Removing an NCU Module from Slot A of an SH7HU Shelf
down.
Replacing an NCU
lay the box aside.
Step 7 Take the replacement module (NCU-II) out of the shipping box.
Step 8 Remove it from the static-protective package and immediately place it onto a
grounded surface or an antistatic mat to avoid ESD damage to the module.
Step 9 Check and prepare the replacement module as follows:
a) Ensure the module is the correct one you want to install (type and
specifications). To quickly obtain the adequate information, refer to the
faceplate markings and the labels on the board cover.
b) Inspect the module visually for damage and impurities. If necessary, use
particles. If a contact strip is loose, torn, or otherwise defective, do not
install this module. Return the module for repair.

Otherwise EMC compliance cannot be achieved.
Step 10 Insert the replacement module into the empty slot as follows:
a) Hold the module by both screws as shown in Figure 32 or by the faceplate.
Figure 32: Inserting an NCU-II into Slot A of an SH7HU Shelf
Replacing an NCU

immediately.
The module is properly and completely inserted when
• its faceplate is flush with the faceplates of the adjacent modules and
the shelf panels
• it receives power.
Step 11 While the replacement module restarts, the MOD LED blinks. The restart is
completed when the NCU beeps four times and the MOD LED changes from
blinking to solid green. Check also the P LED to ensure that the module is
operating correctly. Refer to the module LED indicator description in
“Management and Switch Modules” on p. 385.
If the module does not respond, remove it from the slot. Insert a dummy
module into the empty slot.
Note
Step 12 When the replacement module operates properly, secure it tightly in the slot as
follows:
If the database backup is stored on the SCU, Database Auto Restore was
set to Restore from SCU before the NCU replacement, and the database
backup is based on the same software version as the replacement NCU, skip
the remaining steps of this procedure.
Step 13 Connect your management computer to the NCU using a serial connection, as
Operations Manual.
Step 14 Log on the replaced NCU using HyperTerminal and open the Craft Console.
The communication between the management computer and the NCU will run
over the serial cable. The following warning window is displayed:
Replacing an NCU
Since the new NCU has been detected in the shelf for the first time, the
“DBACT_MEA” alarm will be present. This alarm indicates that there could be
a database mismatch. An auxiliary database is therefore used to prevent
services interruption. In this case, proceed to Step 15.
However, if the replaced NCU is new and was never installed in another shelf
previously, the above message will not be displayed and the “DBACT_MEA”
condition is not raised. In this case, proceed to Step 16.
Step 15 Select OK to acknowledge the warning related to the “DBACT_MEA”
condition.
The NCU must now be reset to use the default database instead of the
auxiliary database. To reset the NCU, follow these steps:
a) Navigate to System Management > Software and Database Control
and select the Database tab.
b) Select [Reset to Factory Default] and confirm with [OK].
In response, the NE restarts and you will lose connection to the NE. After
four consecutive beeps, the NCU MOD LED changes from blinking to
solid green. This indicates that the NCU has completed the restart and you
can log in.
c) Log on to the NE using HyperTerminal to access the Craft Console.
Step 16 Configure the NE IP address to the value that the previous NCU had:
a) Connect an Ethernet cable between the network and the NCU-II port C1 or
C2.
b) Navigate to System Management > System IP Settings > Default
Gateway, and enter the default gateway.
c) Enter the correct IP address and range for SC-1-A-{C1|C2} by selecting
Service Management > SHELF-1 > MOD-1-A NCU-II.
d) Check which NCU-II port (C1 or C2) you have used for the Ethernet
connection:
If the dependent entity SC-1-A-{C1|C2} is Assign (create) it.

displayed with the text “[UAS]” beside it, the
entity is unassigned
If the dependent entity SC-1-A-{C1|C2} is Configure the IP address and

displayed without the text “[UAS]” beside it, range for this entity.
the entity is assigned.
For more information about assigning and configuring the LAN IP interface,
refer to “Assigning the Ethernet IP Addresses” in the Provisioning and
Operations Manual.
Step 17 After you have provisioned the LAN IP interface, a window will be displayed,
prompting you to restart the NCU. Select OK.
You will lose connection to the NE. After four consecutive beeps, the
NCU MOD LED changes from blinking to solid green. This indicates that the
NCU has completed the restart and you can log in.
Step 18 Log on to the NE using NED.
Step 19 Check whether the new NCU's software version matches the software version
associated with the database backup.
Replacing an NCU
Step 20 If required, update the NCU software to match the software version associated
with the database backup, as described in “Updating the NE Software
Release” on p. 617.
Step 21 If the database backup is located on a remote server and it was renamed
during storage, ensure its name has the extension *.DBS.
Step 22 Restore the database as described in “Restoring the Database” on p. 614.
Chapter 13
Control Plane Maintenance and

Troubleshooting
This chapter addresses maintenance and troubleshooting tasks to perform on the control
plane using the Craft Interface. Refer to the following sections:
“Maintaining Tunnels and Services” on p. 544
“Troubleshooting Control Plane Issues” on p. 560
Refer to the Provisioning and Operations Manual for details on enabling

the control plane and provisioning associated entities.
Note
Maintaining Tunnels and Services

The following subsections describe how to maintain tunnels and services:
“Converting an Existing Service to Control Plane Management” on p. 544
“About WDM Cross-Connections” on p. 548
“Converting a Service from Control to Management Plane Ownership” on p. 550
“Repairing Tunnels after Replacing a Network Element” on p. 551
“Viewing Traffic Engineering Information in an NE” on p. 555
“Manually Restoring a Path” on p. 559
Converting an Existing Service to Control Plane

Management
Unmanaged data-plane services may be converted to control plane management. This
conversion is accomplished by creating a Tunnel entity to represent the end-to-end
transport capability already provisioned in the data plane. When you activate this Tunnel
entity, the service that the Tunnel entity represents is adopted by the control plane. A
Tunnel may only be adopted by the control plane when all of the data-plane entities
associated with the Tunnel have been properly provisioned. This includes the
corresponding network facilities, ROADM cross-connections, protection groups, and
WDM cross-connections.
This section describes how to convert an existing service to be managed by a new tunnel
entity.
Requirements
The control plane functionality must already have been configured and enabled in the
network configuration, as described in the Provisioning and Operations Manual, section
"Enabling the Control Plane". Ensure all of the data-plane entities associated with the
Tunnel have been properly provisioned.
Step 1 Log on to the NE where the transport connection originates.

Step 2 You may explicitly specify the working and protection paths of the existing
transport connection.
While not strictly necessary, this does ensure that the control plane managed
transport connection follows the precise path of the existing transport
connection being converted.
If relevant, define the explicit paths as described in the Provisioning and
Operations Manual, section "Configuring Restoration for Existing Tunnels".
Step 3 Initiate the creation of the Tunnel by selecting Control Plane > CP-WDM >
Tunnels WDM.
In response, the Tunnels WDM window appears.
This window gives an overview of the existing Tunnels in the NE. If the list is
empty, no Tunnels have been provisioned.
Step 4 Select Add to provision the Tunnel entity that will be the bearer channel for the
service.
In response the Create window appears.
+------------------------Create: TNL-WDM-------------------------+
| Enter relevant values |
| Facility Type: [--choose-- ] |
| Direction: Bi |
| Destination node TID: [ ] |
| Source equipment AID: [ ] |
| Dest. equipment AID: [ ] |
| Tunnel Name: [ ] |
| Recovery Type: [NONE ] |
| Pinning: Yes |
| Tunnel Type: Point to Point |
| Tunnel Number: [0 ] |
| |
| [ Cancel ] [ Refresh ] [ Next ] |
+----------------------------------------------------------------+
Step 5 The Tunnel is the bearer channel of the payload, so its facility type must match
the facility type that your payload is going into. Use the Facility Type drop-
down list to specify this facility type.
Step 6 Enter into the Source equipment AID field the access identifier (AID) of the
endpoint service adaptation module (in the source network element).
Step 7 Enter information about the far end of the Tunnel as follows:
• Enter into the Destination node TID/Node IP field the terminal identifier
(TID) or the IP address of the network element in the far end of the tunnel.
• Enter into the Dest. equipment AID field the access identifier (AID) of the
endpoint service adaptation module (in the destination network element).
Step 8 Enter a text string that to identify the Tunnel by a name in the Tunnels WDM
window’s list of Tunnels.
The Tunnel’s access identifier is based on this text string; TNL-WDM-<tunnel
name>.
Step 9 Both protected and unprotected transport connections are supported by the
control plane. Protection is treated in an end-to-end fashion, i.e. the
establishment of protection associations occurs at the ingress and egress
network element only (mixing of protected and unprotected spans in the same
end-to-end transport connection is not currently supported). Do not provision
the working path with the control plane and the protection path manually, or the
reverse. Let the control plane provision the protected transport connection.
Use the Recovery Type drop-down list to specify any protection for the
tunnel, in harmony with the existing service’s protection type.
The options are:
• NONE, indicating an unprotected tunnel.
• Protection Desired, which indicates that protection is requested, but it
may not be possible.
When adopting an existing data-plane service, the recommended protection
type is Protection Desired. Upon calculation, the control plane will attempt to
fulfil these requirements.
Step 10 The rest of the fields can be left at their default values. Continue to the next
page of the wizard by selecting Next.
The content that now is displayed in the Create page will depend on the facility
type you selected for the tunnel. The following is an example where the Tunnel
facility type is OTU2.
+-----------------------Create: TNL-WDM------------------------+
| |
| Forward Error Correction: [G709 Standard FEC ] |
| Termination Level: [Phys ] |
| Stuffing: [Yes] |
| Admin State: Pre Post Signalling |
| |
| [ Cancel ] [ Refresh ] [ Prev ] [ Next ] [ Apply ] |
+--------------------------------------------------------------+
Step 11 Tunnels may describe certain attributes of the WDM path or paths associated
with it, to align devices along the transport connection path or paths, such as
attributes like termination level, FEC mode, and bit stuffing.
Enter the relevant settings for these attributes in harmony with the existing
service. For information about the options, consult the Management Data
Guide for the module in question.
Step 12 The administrative state of the Tunnel is at this point Pre Post Signalling.
This indicates that the Tunnel path has not been calculated, nor has any
provisioning been signalled yet.
Select Next to continue.
In response, the following content is displayed in the Create page.
+--------------------------Create: TNL-WDM---------------------------+
| |
| Provisioned Paths: |
| +------------------------------------------------+ |
| | | |
| +------------------------------------------------+ |
| Select Path in the above list to remove it from Provisioned Paths. |
| |
| Available Paths: |
| +------------------------------------------------+ |
| |NONE | |
| |PATH-WDM-Path 71-72 | |
| +------------------------------------------------+ |
| Select Path in the above list to add it to Provisioned Paths. |
| |
| [ Cancel ] [ Refresh ] [ Prev ] [ Apply ] |
+--------------------------------------------------------------------+
Step 13 Before you can adopt a newly provisioned tunnel, you must ensure, as always,
that all of the necessary data plane entities have already been provisioned.
This includes the WDM cross-connection entities indicating current channel
usage within the network element. For more information about how to create
WDM cross-connections, see “Building WDM Cross-Connections” on p. 549.
Step 14 You may choose to explicitly specify the working and, if relevant, the
protection path for the existing service. While not strictly necessary, doing so
ensures that the control plane managed transport connection follows the
precise path of the existing service being converted.
The Available Paths section displays all previously provisioned paths (see the
Provisioning and Operations Manual, section "Configuring Restoration for
Existing Tunnels") and the item NONE. NONE represents no specific/explicit
path.
If choosing to explicitly-specify one or more service paths, perform these steps
as follows. The sequence is important.
a) Enter the desired working path into the Provisioned Paths list as follows:
• If you want to specify the explicit path of the existing service: Select it
in the Available Paths list. In response it will be added to top of the
Provisioned Paths list.
• If you want to use the computed path: Select the item NONE in the
Available Paths list. In response it will be added to the top of the
b) If the Tunnel holds a protected transport connection, enter the desired
protection path into the Provisioned Paths list as follows:
• If you want to specify the explicit path of the existing service: Select it
in the Available Paths list. In response it will be added as the second
item in the Provisioned Paths list.
• If the computed path shall be used, select the item NONE in the
Available Paths list. In response it will be added as the second item in
the Provisioned Paths list.
Step 15 Select [Apply] to complete the provisioning of the Tunnel.
When application is complete, a message window appears.
+----------------------------------+
| |
| Entity was successfully created. |
| |
| [ OK ] |
| |
+----------------------------------+
Step 16 Select [OK] to close the informational window.

You are returned to the Tunnels WDM window.
Step 17 Check that the newly added Tunnel is displayed in the list of tunnels. You can
use the search function to search for the Tunnel by its name. Alternatively use
the provided controls to page up and down, or to the top or bottom of the list.
Step 18 Select the new Tunnel.
In response, the Tunnel facts window displays.
Step 19 Set the administrative state to In Service using the Admin State drop-down
list.
In response, the displayed window content changes.
Step 20 Select the Adopt check box.
This indicates that the Tunnel shall reuse the data plane provisioning done for
the existing service.
Step 21 Select [Apply] to activate the Tunnel.
Setup of the Tunnel can take a significant amount of time, up to several
minutes in the case where long paths and/or many ROADMs are present.
During the setup, the message “Tunnel setup in progress...” will appear in the
State tab window, and remain displayed until the activation is completed.
Step 22 If the requested end-to-end transport connection is not successfully

established: A message window will appear to inform of the failure. Consult the
following resources as necessary to understand what the problem is:
• The Tunnel Flt Log and Fault tabs. The Fault tab show all standing
conditions related to the Tunnel, while the Flt Log lists all conditions that
have occurred on the tunnel or on connections related to the Tunnel. This
log may be used to trace the process of setting up the Tunnel.
• The Control Plane Log Table window (Use Service Logging > Control
Plane Log Table).
• The TE Routers window (Use Control Plane > TE Information >
TE Routers). This window gives you access to an overview of all control
plane enabled NEs. If any TE router is incorrectly configured, this can
affect the successful establishment of the requested end-to-end transport
connection. For more information see “Viewing TE Router Information” on
p. 556.
• The TE Links Numbered or TE Links Unnumbered window (Use
Control Plane > TE Information > TE Links WDM > TE Links
Numbered or TE Links Unnumbered). This window gives an overview of
transport links with traffic engineering capabilities. The TE links describe
the arcs in the graph representing the transport network topology as
discovered by the control plane. If any TE link is advertised incorrectly,
this can affect the successful establishment of the requested end-to-end
transport connection. For more information see “Viewing TE Link
Information” on p. 557.
Step 23 If the requested end-to-end transport connection is successfully established,
the control plane will automatically create connection entities at all network
elements along the paths associated with the originating Tunnel entity. These
connection entities provide each network element that is associated with the
end-to-end transport connection complete visibility to and correlation with that
service.
About WDM Cross-Connections

WDM cross-connections logically associate a channel with some particular application or
use within a network element. An optical channel can originate at, terminate at, or transit
through a network element, and WDM cross-connections indicate which of these uses or
applications employs a given optical channel. While an ADM or ROADM cross-
connection is a one-way connection between two channel entities or network virtual
channels in the management plane, a WDM cross-connection is a logical representation
of a fixed or dynamic cross-connection in the data plane.
The control plane requires WDM cross-connections to identify which WDM channels
within a transport link are currently allocated to some particular use. Therefore, before you
can convert an existing service to control plane management, you must first create WDM
cross-connections for each channel and at each node carrying the service that you wish
to convert.
Building WDM Cross-Connections

WDM cross-connections and ADM and ROADM cross-connections are created and
deleted in a similar manner. However, because WDM cross-connections represent
existing channel assignments, the various client or network port channel entities involved
in those connections are presumed to have been created before you attempt this
procedure. Whether a WDM cross-connection is add, drop, or pass-through is determined
by the connection type of the endpoints being cross-connected. If you create WDM
cross-connections in preparation for adoption by the control plane, they should always be
created as bidirectional. Pass-through connections link WCH entities (if passed through
at that node), and add/drop connections link WCH and CH entities (if added or dropped at
that node).
Perform the steps in this procedure to create a WDM cross-connection.
Step 1 Log on to the NE where the service transport connection shall be terminated.
Step 2 Under Service Management, select the optical line (OL) for the Network
Degree (e.g. West, East) for the Network Element. The OL menu displays.
Step 3 Select Service Management > Virtual Optical Channels to display a list of
the current virtual optical channels. Select Add to create a new virtual optical
channel.
Step 4 The Create: WCH menu displays. For the AID, select the relevant WCH
entry from the drop-down menu, in the form WCH-X-yyyy, where X represents
the OL, and yyyy represents the channel number. Refer to your engineering
plan for the appropriate values. Select Next.
Step 5 Select Apply to create the WCH. The system displays a message indicating
that the WCH was created successfully.
Step 6 Use Service Management > WDM layer cross connections to display the
list of connection entities for this NE.
Step 7 Click Add to create a new WDM cross-connection for the channel at this
node.
Step 8 The Create WDM Layer Cross-connection menu appears. Enter the From
AID name value from the drop-down menu. For an add connection, select CH,
the Shelf number value, and the Slot-Port value from the drop-down menus.
For a pass-through connection, select WCH from the drop-down menu for the
From AID name value. Select the appropriate index and channel values.
Step 9 Enter the To AID name value from the drop-down menu. If you chose CH for
the From AID name value, WCH is preselected. Select the appropriate index
and channel values. For a drop connection, select CH, the Shelf number
value, and the Slot-Port value from the drop-down menus. For a pass-through
connection, select WCH from the To AID name drop-down menu. Select the
appropriate index and channel values.
Step 10 Select Next. The system shows that the cross-connection is bidirectional by
default.
Step 11 Select Create to create the one-way cross-connection primitive. The system
displays a message to indicate that you successfully created the cross-
connection and also asks whether you would like to create the primitive in the
opposite direction.
Step 12 Select OK. The system displays a message to indicate that the cross-
connection was successfully created.
Converting a Service from Control to Management Plane

Ownership
In some cases it is relevant to use the control plane capabilities to automate the difficult
process of initial provisioning, and then decide whether to continue to monitor the service
using control plane capabilities over time. For example, it may be desirable to temporarily
suspend ongoing control plane activity for some reason (e.g. to enable some significant
maintenance operation on the DCN), while not affecting transport traffic. This can also be
relevant in connection with software upgrade/downgrade, or in general where the user
wishes to place transport services under direct control of the management plane (e.g.
NMS/EMS) for some administrative reason.
Transferring a service from control plane to management plane ownership can be
achieved through use of the "abandon" feature. Abandoning a service causes the control
plane entities relating to a transport service to be removed from the network (e.g.
connection entities), but leaves the corresponding data plane entities intact (e.g. cross-
connects and facilities remain).
This section describes how to convert a Tunnel from control plane management to
ownership by the management plane.
Step 1 Open the Tunnels WDM window by selecting Control Plane > CP-WDM >
Tunnels WDM.
Step 2 From the list of Tunnels that is displayed, find the Tunnel that you wish to
transfer from control plane to management plane ownership.
You can use the search function to search for the Tunnel by its name.
Alternatively use the controls to page up and down, or to the top or bottom of
the list.
Step 4 Set the administrative state to Pre Post Signalling using the Admin State
drop-down list.
Step 5 Select the Abandon check box.
This indicates that control plane management of the Tunnel shall be
abandoned, but the data plane provisioning done for the Tunnel shall be kept.
If you do not place a check mark in the Abandon check box, the Tunnel will be
deleted both from the control plane and the data plane.
Step 6 Select [Apply] to start the process.
During the process, the message “Tunnel teardown in progress...” will appear
in the State tab window, and remain displayed until the activation is
completed.
Step 7 When completed, the service will continue to be running, but the control plane
no longer manages it.
Repairing Tunnels after Replacing a Network Element

If a network element fails and must be replaced, this will have effect on existing control-
plane managed transport connections originating from this network element. If the
database from the failed element is not restored properly on the replacement element, any
Tunnel entities originally provisioned at the failed network element will need to be
recreated. The connection entities for the Tunnel will still exist in the NEs that are
traversed by the original Tunnel.
Thus in order to repair such a Tunnel, a new Tunnel must be created, and in effect “re-
joined” to the connections left in place by the original Tunnel. Each Tunnel is identified by
an user entered name, and in addition a number that the control plane generates. The
Tunnel number is created as a measure to ensure that no Tunnels have the same identity.
This section describes how to create a new Tunnel entity to replace the missing one, and
how to glue it to the existing Tunnel.
Requirements
The control plane functionality must already have been configured and enabled in the
network configuration, as described in the Provisioning and Operations Manual, section
"Enabling the Control Plane".
Step 1 Find out the Tunnel number of the existing Tunnel. The tunnel number can be
found by selecting any existing connection entity that still exists at some other
network element in the network and is associated with this Tunnel. Use
Control Plane > CP-WDM > Connections WDM to open the Connections
WDM table which shows all connection entities on the NE, and select the
Tunnel to view all information about it.
Step 2 Log on to the replacement NE.
Step 3 Initiate creation of the Tunnel by selecting Control Plane > CP-WDM >
Tunnels WDM.
Step 4 Select Add to provision the Tunnel entity that will be the bearer channel for the
service.
In response, the Create window appears.
Step 5 The Tunnel is the bearer channel of the payload, so its facility type must match
the facility type that your payload is going into. Use the Facility Type drop-
down list to specify this facility type.
Step 6 Enter the into the Source equipment AID field the access identifier (AID) of
the endpoint service adaptation module (in the source network element).
Step 7 Enter information about the far end of the Tunnel as follows:
• Enter into the Destination node TID/Node IP field the terminal identifier
(TID) or the IP address of the network element in the far end of the tunnel.
• Enter into the Dest. equipment AID field the access identifier (AID) of the
endpoint service adaptation module (in the destination network element).
Step 8 Enter a text string to identify the Tunnel by in Tunnels WDM window list of
Tunnels.
The Tunnel access identifier is based on this text string; TNL-WDM-<tunnel
name>.
Step 9 Both protected and unprotected transport connections are supported by the
control plane. Protection is treated in an end-to-end fashion, e.g. the
establishment of protection associations occurs at the ingress and egress
network element only; mixing of protected and unprotected spans in the same
end-to-end transport connection is not currently supported. Do not provision
the working path with the control plane and the protection path manually, or the
other way around. Let the control plane provision the protected transport
connection.
Use the Recovery Type drop-down list to specify any protection for the
tunnel.
The options are:
• NONE, indicating an unprotected tunnel.
• Protection requested, which indicates that protection is requested, but it
may not be possible.
• Protection required, which indicates that protection is an absolute
requirement.
Upon calculation, the control plane will attempt to fulfil these requirements.
Step 10 Enter the Tunnel number of the existing Tunnel that you found in Step 1 into the
Tunnel Number field.
Continue to the next page of the wizard by selecting Next.
Step 11 The content that now is displayed in the Create page will depend on the facility
type you selected for the tunnel. The following is an example where the Tunnel
facility type is OTU2.
Step 12 Tunnels may describe certain attributes of the WDM path or paths associated
with it, to align devices along the transport connection path or paths, for
example attributes like termination level, FEC mode, bit stuffing.
Enter the relevant settings for these attributes. For information about the
options, consult the Management Data Guide for the module in question.
Step 13 The administrative state of the Tunnel is at this point Pre Post Signaling. This
indicates that the Tunnel path has not been calculated, nor has any
provisioning been signalled yet.
Select Next to continue. In response the following content is displayed in the

Create page.
Step 14 Use of explicitly specified paths is generally unnecessary, as the automated

path computation capabilities of the network element are normally sufficient to
select the optimal/desired path.
The Available Paths section displays all previously provisioned paths (see the
Provisioning and Operations Manual, section "Configuring Restoration for
Existing Tunnels") and the item NONE. NONE represents the computed path.
Do as follows, the sequence is important:
a) Enter the desired working path into the Provisioned Paths list as follows:
Available Paths list. In response it will be added to the top of the
• If an explicit path must be used, select it in the Available Paths list. In
response it will be added to top of the Provisioned Paths list.
b) If the Tunnel holds a protected transport connection, enter the desired
protection path into the Provisioned Paths list as follows:
Available Paths list. In response it will be added as the second item in
the Provisioned Paths list.
• If an explicit path must be used, select it in the Available Paths list. In
response it will be added as the second item in the Provisioned Paths
list.
Step 15 Select [Apply] to complete the provisioning of the Tunnel.
When application is complete, a message window appears.
+----------------------------------+
| |
| Entity was successfully created. |
| |
| [ OK ] |
| |
+----------------------------------+
Step 16 Select [OK] to close the informational window.

You are returned to the Tunnels WDM window.
Step 17 Check that the newly added tunnel is displayed in the list of tunnels. You can
use the search function to search for the tunnel by its name. Alternatively use
the provided controls to page up and down, or to the top or bottom of the list.
Step 18 Ensure that the endpoint service adaptation modules for this service are not
already in use.
The list of connection entities for this NE will show this. Use Control Plane >
CP-WDM > Connections WDM to display this list.
Connection entities provide a logical link between a transport connection

(described by a Tunnel) and the corresponding local equipment provisioning
operations necessary to establish that Tunnel in the network. If the required
endpoint service adaptation modules for this service transport connection are
already in use by a connection entity in this table, then stop this procedure
now.
Step 19 Open the list of Tunnels. Use Control Plane > CP-WDM > Tunnels WDM.
Step 21 Set the administrative state to In Service using the Admin State drop-down
list.
Step 22 Select [Apply] to activate the Tunnel.
Setup of the Tunnel can take a significant amount of time, up to several

minutes in the case where long paths and/or many ROADMs are present.
During the setup, the message “Tunnel setup in progress...” will appear in the
State tab window, and remain displayed until the activation is completed.
Step 23 If the requested end-to-end transport connection is not successfully
established, a message window will appear to inform of the failure. Consult the
following resources as necessary to understand what the problem is:
• The Tunnel Flt Log and Fault tabs. The Fault tab show all standing
conditions related to the Tunnel, while the Flt Log lists all conditions that
have occurred on the tunnel or on connections related to the Tunnel. This
log may be used to trace the process of setting up the Tunnel.
• The Control Plane Log Table window (Use Service Logging > Control
Plane Log Table).
• The TE Routers window (Use Control Plane > TE Information >
TE Routers). This window gives you access to an overview of all control-
plane enabled NEs. If any TE router is incorrectly configured, this can
affect the successful establishment of the requested end-to-end transport
connection. For more information see .
• The TE Links Numbered or TE Links Unnumbered window (Use
Control Plane > TE Information > TE Links WDM > TE Links
Numbered or TE Links Unnumbered). This window gives an overview of
transport links with traffic engineering capabilities. The TE links describe
the arcs in the graph representing the transport network topology as
discovered by the control plane. If any TE link is advertised incorrectly,
this can affect the successful establishment of the requested end-to-end
transport connection. For more information see “Viewing TE Link
Information” on p. 557.
Step 24 If the requested end-to-end transport connection is successfully established,
the control plane will automatically create connection entities at all network
elements along the paths associated with the originating Tunnel entity. These
connection entities provide each network element that is associated with the
end-to-end transport connection complete visibility to and correlation with that
service.
Viewing Traffic Engineering Information in an NE

Traffic engineering information is generated as a result of user configuration choices, as
described in the Provisioning and Operations Manual, section "Enabling the Control
Plane". Traffic Engineering information is critical to the overall proper operation of the
control plane. This information essentially describes the topology and resource
availability of the actual network itself, in terms which can be automatically processed by
various control plane subsystems. In particular, the automated path computation
capabilities embedded in the network element rely on this information, in order to be able
to find an optimal path through the network between the desired endpoints. As such,
having access to this information can provide considerable help and benefit to the user,
both in understanding what information is being provided to the control plane about the
network itself, and in assisting the user to diagnose any difficulties which may arise with
computing or provisioning paths.
If the user for example fails to properly describe the internal fiber mapping of the NE
during configuration, the traffic engineering information derived from the improper user
configuration will also be improper. Hence there is a direct correlation between
correctness of NE configuration as entered by the user and the ultimate ability of the
control plane subsystem to compute pathways for Tunnels through the transport network.
This section provides two methods to view what traffic engineering information is known
to a NE, as a means to identify any improper user configuration.
The following sections are provided.
“Viewing TE Router Information” on p. 556
“Viewing TE Link Information” on p. 557
Viewing TE Router Information

This procedure describes how to display the information about the TE routers that an NE
can see.
Step 1 Open the TE Routers window by using Control Plane > TE Information > TE
Routers.
In response the TE Routers window appears.
Step 2 This window displays the Node IP address for each TE router that this NE can
see. If display of the Node TID is enabled for the NE, the Node ID for each
visible TE router is also displayed.
Step 3 Use the buttons provided to navigate in the list.
Viewing TE Link Information

This procedure describes how to display the information about the TE links that an NE
can see.
Step 1 Open the TE Links window by using Control Plane > TE Information > TE
Links WDM and then TE Links Numbered or TE Links Unnumbered.
In response the TE Links window appears, either containing the numbered or
unnumbered links. The following example shows the TE Links WDM
Unnumbered window.
+---------------------------TE Links WDM Unnumbered---------------------------+
| |
| Node IP Link ID Sync Disc FEND Node IP FEND Link ID |
| +--------------------------------------------------------------------+ |
| |10.12.33.82 196611 Yes No 10.12.33.83 196609 | |
| |10.12.33.82 196612 Yes No 10.12.33.83 196610 | |
| |10.12.33.83 196609 Yes No 10.12.33.82 196611 | |
| |10.12.33.83 196610 Yes No 10.12.33.82 196612 | |
| | | |
| | | |
| | | |
| +--------------------------------------------------------------------+ |
| |
| |
| [ Cancel ] [ Top ] [ Bottom ] [ Page Up ] [Page Down] [ Refresh ] |
| |
+-----------------------------------------------------------------------------+
The following information is provided for each TE link:

• The identity of this end of the link. For an unnumbered TE link this is
defined by the Node IP address and the TE Link ID. For a numbered TE
link this is defined by the Node IP address and the TE Link IP.These
items are found in the Node IP, Link ID and Link IP columns.
• The Sync column indicates whether the TE link has been configured
completely. When both ends recognize the TE link, it is synchronized.
• The Disc column indicates whether this TE link is ignored during path
computation. For example, if the originating NE of the link is not refreshed
in the OSPF database, it is not considered reachable via OSPF and the
link is discarded. The link however persists till the time out expires.
• The identity of the far end (FEND) of the link. as defined by the Node IP
address and the TE Link ID. For an unnumbered TE link this is defined by
the FEND Node IP address and the FEND Link ID. For a numbered TE
link this is defined by the FEND Node IP address and the FEND Link IP.
These items are found in the FEND Node IP, FEND Link ID and FEND
Link IP columns.
Step 2 To view more information about a link, select the link.
In response the TE Link Unnumbered or TE Link Numbered window

appears. The following example shows the TE Link Unnumbered window.
+-------------------TE Link Unnumbered: 10.12.33.82, 196612-------------------+
| |
| Node IP Address: 10.12.33.82 |
| Node TID: NE2 |
| TE Link ID: 196612 |
| |
| Physical Link: 204000 |
| Synchronization: Yes |
| TE Link Discarded: No |
| Far End Node: 10.12.33.83 |
| Far End TE Link ID: 196610 |
| |
| |
| |
| [ Back ] [ Refresh ] [Description...] |
| |
+-----------------------------------------------------------------------------+
The following information is displayed:

• The identity of this end of the link. For an unnumbered TE link this is
defined by the Node IP address and the TE Link ID. For a numbered TE
link this is defined by the Node IP address and the TE Link IP.These items
are found in the Node IP Address, TE Link ID and TE Link IP fields.
• The Physical Link field indicates the ID of the physical link. This is useful
for interoperation with equipment from other vendors.
• The Synchronization field indicates whether the TE link has been
configured completely. When both ends recognize the TE link, it is
synchronized.
• The TE Link Discarded field indicates whether this TE link is ignored
during path computation or not. For example, if the originating NE of the
link is not refreshed in the OSPF database, it is not considered reachable
via OSPF and the link is discarded. The link however persists till the time
out expires.
• The identity of the far end (FEND) of the link. For an unnumbered TE link
this is defined by the FEND Node IP address and the FEND Link ID. For a
numbered TE link this is defined by the FEND Node IP address and the
FEND Link IP. These items are found in the Far End Node, Far End TE
Link ID and Far End TE Link fields.
Step 3 Select Description for even more details about the link, Refresh to update the
window or Back to return to the TE Links Unnumbered window.
Manually Restoring a Path

When it comes to restoring a failed path, the operator has the option to perform all
restoration operations manually without any automated restoration action taken by the
control plane. They can use existing control plane capabilities like Service Manager to
restore a failed path. If the operator chooses manual restoration, none of the paths can be
marked as being restorable. When a failure occurs along any path associated with the
Tunnel, since no paths are marked as being restorable the control plane takes no action,
and the operator is simply informed of the failure through normal event monitoring / alarm
processing capabilities provided by the management plane. The other options are auto
and guaranteed restoration. For details about automatic and guaranteed restoration see
the Provisioning and Operations Manual, section "Configuring Restoration for Existing
Tunnels".
If you choose to respond to the reported failure by initiating a manual restoration
procedure, execute the following general sequence of steps.
Step 1 Find the fault location. Utilize the alarm and fault event information delivered by
the management plane for the overall network, in order to localize where in the
network the actual fault resides.
Positive information regarding signal presence or absence available at
endpoints and active transit points is typically utilized to narrow down the
possible set of segments at which a fault may have occurred.
Step 2 Once the location of the fault has been localized, instruct the control plane to
avoid the faulted segment.
One way to repair the fault is to identify the Traffic Engineering Metric for the
affected link (thus causing subsequent path computation to disfavor the link).
Another repair method is to construct a PATH entity which explicitly routes
around the failed link. In this case the constructed PATH entity is set as a
Provisioned Path on the Tunnel entity affected by the fault.
Step 3 Once the failed path is identified, the operator initiates a modification of the
Tunnel entity affected by the fault.
This modification occurs as a Make-Before-Break transaction in the control
plane, ensuring that the new path selected by the operator is properly created
prior to removal of the failed path.
Because make-before-break semantics are used, it is entirely possible for the
newly-selected path to share zero or more links with the failed path, subject to
how the new path was computed or specified.
Troubleshooting Control Plane Issues

The following subsections describe troubleshooting tasks for the control plane. These
procedures are performed using the Craft Interface:
“Checking Status of TE Links” on p. 560
“Checking OSPF Settings” on p. 563
“Verifying Physical Connections” on p. 562
“Resolving Connection Failures Resulting from MTU Size Mismatches” on p. 566
“Tracing a Channel Through the Node” on p. 568
Checking Status of TE Links

Traffic Engineering (TE) routers and TE links represent the nodes and transport links in
the network known to have traffic engineering capabilities. Checking the status of
TE links comprise the following:
“Verifying List of TE Routers” on p. 560
“Checking Synchronization Status of TE Links” on p. 561
“Verifying Logical Interfaces” on p. 562
Verifying List of TE Routers

Check whether the list of nodes with Traffic Engineering capabilities is available at each
node.
Step 1 Select Control Plane > TE Information > TE Routers to open the
TE Routers window.
Step 2 Ensure each node in the network is specified in the TE Routers window.
If a node is missing from the TE Routers list, check the IP and OSC
connectivity to the respective node.
Note
Checking Synchronization Status of TE Links

Correctly configured TE Links are marked as "synchronized" and are hence recognized
by the control plane. Execute the following procedure to verify the synchronization status
of TE Links.
Step 1 Select Control Plane > TE Information > TE Links WDM and then TE Links
Numbered or TE Links Unnumbered.
In response the TE Links WDM Numbered or TE Links WDM Unnumbered
window appears,depending on your selection. The following example shows
the TE Links Unnumbered window.
• Numbered TE links are identified by a unique IP address within the

network.
• Unnumbered TE links have an identifier which is unique only within
Note the local node.
Step 2 The TE Links WDM (Un)Numbered window displays all the TE links

associated with this NE. Check the values of the following parameters for the
given TE Link:
• Sync - indicates whether the TE Link is configured completely and hence,
recognized by the control plane.
• Queue Discipline (Disc) - indicates whether the TE link is unreachable by
the control plane and hence, ignored during the path computation.
Verifying Logical Interfaces

Ensure that the transport layer termination points specified for each endpoint of a TE link
match, as described below:
Step 1 Log on to the source/destination node of the TE link and select Control Plane
> Logical Interfaces CP.
The Logical Interfaces window displays a list of TE Links terminating or
originating at this node.
Step 2 Choose the respective TE link to view the following parameters:
• Trans. Layer Term. Point - The transport layer termination point for this
NE.
• Far End TLTP - The transport layer termination point for the far-end NE.
Step 3 Repeat Step 1 to Step 2 for the second node associated with this TE link.
Step 4 Verify that the source transport layer termination point of one node matches the
far end transport layer termination point of the second node, and vice-versa.
Verifying Physical Connections

To properly compute pathways for the Tunnels through a network, the control plane relies
on the internal physical cable connection information entered into the
Physical Termination Point (PTP) and Physical Connections Table. PTPs represent each
point in the NE to which a physical cable or jumper is connected.
Verify the internal physical cable connection details as follows:
Step 1 Log on to the source NE of the TE link and select Service Overview > PTP &
Physical Connections Table.
The PTP & Physical Connections Table window displays the list of all fiber
connections at this NE.
+------------------- PTP & Physical Connections Table --------------------+

| |
| Shelf Slot Equipment Class |
| [All] [All ] [All ] [All ] |
| |
| From AID Eqpt To AID Eqpt Conn Class |
| +----------------------------------------------------------+ |
| |PTP-1 OL PTP-2-N EROADM 2WAY STD | |
| |PTP-2 OL PTP-1-3-C1 10TCC10G 1WAY NON-STD | |
| |PTP-1-3-C1 10TCC10G -- -- -- -- | |
| |PTP-1-3-C2 10TCC10G PTP-4-8-NE 4TCA4G 2WAY STD | |
| |PTP-1-3-N 10TCC10G PTP-2-C1 EROADM 2WAY STD | |
| |PTP-1-5-C WCA10G-C PTP-4-5-C1 5TCE10GT 2WAY STD | |
| |PTP-1-5-N WCA10G-C -- -- -- -- | |
| |PTP-1-6-N 5TCE10GT PTP-6-11-N2 4OPCM 1WAY STD | |
| |PTP-1-7-C1 OSCMPN -- -- -- -- | |
| |PTP-1-7-C2 OSCMPN PTP-1-A-C2 NCU-II 2WAY STD | |
| |PTP-1-7-C3 OSCMPN -- -- -- -- | |
| +----------------------------------------------------------+ |
| Click on From AID to view, edit, create or delete Physical Connections |
| |
| [ Cancel ] [ Top ] [ Bottom ] [ Page Up ] [Page Down] [ Refresh ] |
| |
--------------------------------------------------------------------------
Step 2 Verify the current physical connections enable the TE link to properly
transverse through this node.
Step 3 Repeat Step 1 to Step 2 for each node the TE link transverses through.
Checking OSPF Settings
To use the pathways computed by the control plane, OSPF settings at each NE must be
entered correctly when the node is provisioned. This section addresses the following
procedures to troubleshoot some commonly occurring connectivity problems:
“Verifying All Nodes are Listed” on p. 563
“Ensuring the Correct Topology” on p. 564
“Verifying OSPF Neighbors” on p. 565
Verifying All Nodes are Listed

Verify that all nodes of the OSPF domain are listed in the Target Identifier (TID) IP table,
as described in the following procedure.
Step 1 Select System Management > System IP Settings > TID IP Table.
The System IP Settings window displays the list of nodes in this
OSPF domain.
+---------------------------- System IP Settings -----------------------------+

|| 1 System IP | 2 Default Gateway | 3 Routing Table | 4 TID IP Table | |
|+---------------------------------------------------+ +------+|
|| ||
|| ||
|| TID IP ||
|| +--------------------------------------+ ||
|| |HUB1 172.18.36.1 | ||
|| |HUB2 172.18.36.6 | ||
|| |ILA1 172.18.36.2 | ||
|| |ILA2 172.18.36.3 | ||
|| |ILA3 172.18.36.4 | ||
|| |ILA4 172.18.36.5 | ||
|| |NODE71 172.18.32.71 | ||
|| |NODE73 172.18.32.73 | ||
|| |node72 172.18.32.72 | ||
|| |node86 172.18.32.86 | ||
|| +--------------------------------------+ ||
|| ||
|| ||
|| [ Cancel ] [ Top ] [ Bottom ] [ Page Up ] [Page Down] [ Refresh ] ||
|| ||
|+---------------------------------------------------------------------------+|
Step 2 Ensure all nodes in this OSPF domain are listed in the TID IP Table tab.
Step 3 If nodes in this OSPF domain are absent from the table,
• check OSPF connectivity between the affected nodes.
• ensure each node is assigned a unique System IP address or System ID.
Step 4 If nodes are still absent from the TID IP table, reboot this node.
Ensuring the Correct Topology

Verify that OSCM Topology Detection indicates the correct topology.
Step 1 Select Service Management > Shelf, then the slot occupied by the OSCM.
Step 2 Next, select MOD- x- y OSCM > Config.
The MOD- x- y, OSCM-PN window displays the current topology.
Step 3 Ensure the correct Topology and IP List are displayed.
Step 4 If an incorrect topology is indicated,
• check whether the fiber is properly connected.
• check if the received power level is too high or too low.
• check the DCN settings on nodes current connected to this NE.
Verifying OSPF Neighbors
Verify all OSPF neighbors are correctly discovered, as described in the following
procedure.
Step 1 Select System Management > System OSPF Settings > OSPF Neighbors.
The OSPF Neighbors window displays this NE's OSPF neighbors.
+------------------------------ OSPF Neighbors -------------------------------+
| |
| Interface IP Adj State Adj Role Node IP Node TID |
| +-------------------------------------------------------------------------+ |
| |172.18.32.72 2WAY OR 172.18.32.72 node72 | |
| |172.18.32.73 2WAY OR 172.18.32.73 NODE73 | |
| |172.18.32.86 2WAY OR 172.18.32.86 node86 | |
| |172.18.32.87 2WAY OR 172.18.32.87 node87 | |
| |172.18.36.1 2WAY OR 172.18.36.1 HUB1 | |
| |172.18.36.2 2WAY OR 172.18.36.2 ILA1 | |
| |172.18.36.3 2WAY OR 172.18.36.3 ILA2 | |
| |172.18.36.4 2WAY OR 172.18.36.4 ILA3 | |
| |172.18.36.5 FULL DR 172.18.36.5 ILA4 | |
| |172.18.36.6 FULL BDR 172.18.36.6 HUB2 | |
| | | |
| | | |
| | | |
| +-------------------------------------------------------------------------+ |
| |
| [ Back ] [ Refresh ] [ Top ] [ Bottom ] [ Page Up ] [Page Down] |
| |
Step 2 Refer to your DCN plan to ensure all nodes designated as this NE's
OSPF neighbors are listed in the table.
Step 3 If any OSPF neighbors are absent from this table, check the
OSPF connectivity between the corresponding nodes.
If OSPF is used by external DCNs, the Adj field should not be set to
DR or BDR.
Note
Resolving Connection Failures Resulting from MTU Size

Mismatches
All OSPF routers on the same LAN segment/PPP link must be provisioned with the same
MTU size. If the MTU size settings differ, the router will not exchange OSPF database
description packages, leading to a degradation in the overall dynamic routing function and
control plane failure.
Figure 33: Ping Response Indicating a Connection Failure
Follow this procedure to troubleshoot a connection failure to an NE, if you receive a ping
response similar to Figure 33.
Step 1 Establish a network connection to a neighbor NE on the same LAN segment.

The NE OSPF neighbors are displayed.
Step 3 Identify the Designated Router (DR) and the Backup Designated Router
(BDR). These entries are characterized by the Adj State "Full."
In the example in Figure 34, the DR is NE37 and the BDR is NE50.
Figure 34: OSPF Neighbors of the NE
Step 4 Log in to the NE identified as the BDR in Step 3 (NE50 in the above example).
The OSPF neighbors of the BDR are displayed.
Figure 35: OSPF Neighbors of the BDR
Step 6 Check the Adj State of the BDR OSPF neighbors.

• Generally, the Adj State of each BDR OSPF neighbor is "Full."
• During an OSPF database description package exchange, the Adj State
changes to "Exstart." After this process completes successfully, the Adj
State reverts to "Full."
• If the Adj State of a neighbor is "Exstart" persistently, this indicates an
MTU size mismatch.
In Figure 35, the Adj State of the NE42 is "Exstart" persistently. This implies
an MTU size mismatch between NE42 and NE50.
Step 7 Select Service Management > SHELF-1 > MOD-1-A NCU > SC-1-A-
{C|C1|C2} LANIP, depending on the NCU port used.
Step 8 Select the Config tab, then view/edit the MTU size.
Step 9 Log in to the NE that displayed the persistent "Exstart" Adj State (NE42 in this
example), and then repeat Step 7 and Step 8 to view/edit the MTU size.
Figure 36 shows the MTU size mismatch between NE42 and NE50.
Figure 36: MTU Size Comparison
Tracing a Channel Through the Node

To troubleshoot issues such as equalization failures, it is vital to trace the channel's
passage through the node to determine at which stage the failure occurs. The node
channel trace feature enables you to trace a channel's path through the node, starting
from a designated point. You may trace a channel by optical line and channel number, or
by port.
Proceed to “Tracking a Channel through a Node” on p. 586 to determine the port at which
out-of-range power levels are indicated.
Chapter 14
General Module and Management

Configuration
This chapter provides procedures for general configurations of the FSP 3000R7 modules
and NE management tools.
It contains the following sections:
“Configuring SNMP Settings” on p. 570
“Configuring In-band Management” on p. 571
“Configuring Loopbacks” on p. 575
“Configuring Clock Speeds” on p. 578
“Setting Auto Laser Shutdown” on p. 579
“Forcing and Releasing Lasers” on p. 581
“Checking for Higher-Level NTP Servers” on p. 583
“Configuring an OSCM” on p. 584
“Configuring OSPF” on p. 585
“Tracking a Channel in a Node” on p. 586
“Configuring Trace Monitoring” on p. 589
“Configuring Wavelengths” on p. 593
“Restarting Modules” on p. 595
“Exporting Network Element Logs” on p. 597
“Configuring Equipment Capabilities” on p. 598
Configuring SNMP Settings
Configuring SNMP Settings

This section describes how to provision SNMP parameters.
Requirement
Step 1 Select .
Step 2 In the Navigation Tree, select General > SNMP.
Step 3 Use the Configuration blade to:
• Enable Authentication Traps.
• Enable Extended Authentication Traps.
• Enable Secure SNMPv3 Access.
• Select the port that will be used for SNMP requests/responses (SNMP
Agent Port).
Step 4 Select the Community blade to regulate access to the network element. Here
you can specify community names and define access rights.
Step 5 Select the Trap Recipients blade to view and define trap recipients.
Configuring In-band Management

This section contains the following subsections:
“In-band Management on Channel Modules” on p. 571
“In-band Management Configuration Example” on p. 571
In-band Management on Channel Modules

This subsection provides information for the in-band management on channel modules.
The channel modules and protocols that can be used for in-band management
(Embedded Communication Channel, ECC) are listed in the Module and System
Specification, Appendix A.
ECC Information & Facts

• Can be terminated at the wavelength termination points that carry the ECC service.
• Provide point-to-point connectivity on layer 2.
• Multiple ECCs can be carried over each fiber span on different wavelengths.
• ECCs have limited bandwidths: 192, 326, 576, 1312, 5271 and 7200 kbit/s.
• A maximum of five ECCs can be terminated on each node.
• ECCs are designed mainly for feeder applications.
• Requires Hardware supporting ECC channels on link ends.
• Configuration is quite complex and requires support of routing protocols.
• The ECC information is carried via the backplane (electrical connection) between the
NCU and the channel module.
• Payload connectivity is required since the ECC data is transported in the overhead.
• For feeder application a proxy ARP (Address Resolution Protocol) functionality is
available to simplify the routing configuration.
In-band Management Configuration Example

This subsection describes an example in-band management configuration procedure,
Requirements
• Two nodes, point-to-point connection
• ECC channel available on 4TCC-PCTN-2G7+10G module
• Each node is connected to the management LAN
Overview of Configuration Steps

The following steps have to be performed:
1 Channel module ECC configuration
2 NCU configuration
There is a difference between the near-end and far-end settings.

Note
3 Disable far-end LAN IP Interface

4 Verification of connectivity
The steps are detailed in sub-tasks. Please pay attention to the additional information that
are given below.
Configuration Procedure
It is recommended to configure and verify the ECC functionality in a lab environment
before deployment in the field. To do so, connect the network interfaces of both channel
modules directly to each other (observing the maximum input power specifications) and
configure and activate the network link.
Example of Configuring the ECC

This procedure describes how to configure the ECC on the 4TCC-PCTN-2G7+10G
module.
Requirements
• The 4TCC-PCTN-2G7+10G module is provisioned.
• The network port of the 4TCC-PCTN-2G7+10G module is provisioned.
Step 1 Log on to the near-end node and select .

Step 2 In the Navigation Tree, select Shelf > 4TCC-PCTN-2G7+10G slot.
Step 3 Select the Management Channels blade and click Add.
The Add facility window opens.
Step 4 Select the GCC0 identifier, then select the facility type GCC0 from the drop
down menu.
GCC0 Special is a special customer protocol and not for general use.

The GCC0 entry is listed under Management Channels blade.
Step 6 Repeat this procedure for the far-end node.
Example of Configuring the NCU

This procedure describes how to configure the NCU.
Step 1 Log on to the near-end node, then select .

Step 2 In the Navigation Tree, select Shef 1 > NCU slot.
Step 3 Select the Management Links to Module Management Channels blade.
Step 4 To create a PPPIP facility (for example LINK-1-A-4), click Add End Point.
In response, the Add facility window appears:
Step 5 Enter the following settings:
• Set OSPF Routing to Disable (unless your network requires OSPF
routing).
• Set Proxy ARP to Enable (on the near-end node).
Step 6 Leave all other settings as default and select .

The new PPP/IP instance is listed under the Management Links to Module
Management Channels blade.
Step 7 Click Add Connection.
The DCN Connection Cross window opens.
Step 8 Enter these settings:
• Set Identifier to the newly created PPP/IP instance from the drop-down
list.
• Set Management Channel to the GCC0 entry from the drop-down list.

Expanding the "+" adjacent to the PPP/IP entry displays the DCN cross
connection.
Step 10 Select the PPP/IP entry.
The Configure Details window opens.
Step 11 Change the Admin State to Disabled, confirm with and verify with
Step 12 Change the Admin State to In Service, confirm with and verify with
.
Step 13 Repeat this procedure for the far-end node, but set Proxy ARP to Disable.
Example of Disabling the Far-End LAN IP Interface

To disable the far-end LAN IP interface, do as follows:
Step 1 Select .
Step 2 In the Navigation Tree, select Shelf 1 > NCU slot.
Step 3 Select Ethernet Ports blade > C|C1|C2|C3, depending on the NCU port used
for the Ethernet connection.
Step 4 Change the Admin State to Disabled.
Step 5 Confirm the setting with and verify by selecting .
After this action, the far-end NCU LAN interface is disabled. You will not
be able to access this node via this interface anymore.
Note
Example of Verifying Connectivity

To verify the connectivity, do as follows:
Step 1 Log on to the near-end node.

Step 2 Execute the ping command to the far-end node. You should receive an
answer from the far-end node.
Step 3 Log on to the far-end node via Serial Line.
Step 4 Execute the ping command to the near-end node. You should receive an
answer from the near-end node.
The other ECC-capable channel modules are configured in the same way.
Only the terminology for the ECC protocol changes. Refer to the Module and
System Specification for details.
For troubleshooting purposes, verify that all settings are configured as

described in this document. A frequent cause of connectivity problems
with the in-band management is an incorrect configuration of default
gateway and proxy ARP configuration. Also, it is frequently forgotten to
Note
assign an AID to the ECC channel.
Configuring Loopbacks
Loopbacks are a temporary maintenance setting. They cannot be set by editing a
parameter in the configuration database, nor can the status be retrieved as a parameter
from the configuration database because it does not belong to the database of
provisioned equipment and services.
Depending on the type of module, four different internal loopback settings can be
activated, deactivated, and monitored:
• Client interface facility loop
• Network Interface terminal loop
• Network interface facility loop
• Client interface terminal loop
For an overview of the loopback types supported by a channel module, refer to the
Module and System Specification, Appendix A.
These loopback settings allow you to isolate failed components or fiber connections and
test them separately. It is also possible to test a complete fiber link at one time.
For more details about the four internal loopback types and their characteristics, see the
System Description.
This section contains the procedure for testing a whole link, as well as the supporting
procedures for setting and releasing internal links. You can use any of the management
tools that FSP 3000R7 supports.
Loopback testing is intrusive to the optical link. Therefore, while you test
a portion of a network or only a circuit, you will be unable to pass traffic
across that link.
Note
Client or line loopback applied to 4WCE-PCN-16GFC modules may, on

rare occasions, cause bit errors in the looped traffic. In the event of bit
errors, disable the loopback.
Note
Only one loopback type (client interface facility loopback or line interface
facility loopback) may be applied to a 5WCA-PCN-16GU module at any
given time. Setting or releasing a second loopback type on the same
Note module may interrupt traffic associated with the first loopback.
The following sections are provided:

“Configuring a Client Interface Loopback” on p. 576
“Configuring a Network Interface Loopback” on p. 576
Configuring a Client Interface Loopback

This section describes how to activate or remove a terminal or facility loopback on the
client interface.
Step 1 Select .
Step 2 In the Navigation Tree, select Shelf > Module slot.
Step 3 In the Ports blade, select the client interface for which you wish to setup a
loopback (for example, CH-1-x-Cx).
Step 4 Set the Admin State to Maintenance.
Note the original setting, to be able to revert to it after the loopback setting is
activated.
Step 5 Select .
The Loopback field is accessible.
Step 6 Set Loopback to either an internal or facility loopback, or remove an already
active loopback. The options are:
• Facility - which sets a facility loopback on the interface.
• Terminal - which sets a terminal loopback on the interface.
• None - this removes an already active loopback.
Step 7 Select to activate the loopback setting.

Step 8 Set the Admin State to its original state before testing with loops.
Step 9 Select to save the setting.
Configuring a Network Interface Loopback

This section describes how to activate or remove a terminal or facility loopback on the
network interface.
If a loopback on the network interface is initiated, data traffic will be

interrupted.
Note
Requirements
The interface must not be part of a protection group. If it is, the protection group must be
removed before loopback testing has terminated.
Step 1 Select .
Step 3 Select from one of the following:

• To set a loopback on a 10TCC10GT, proceed to Step 4.
• To set a loopback on any other module, proceed to Step 8
Step 4 In the Data Channels blade, set the Admin State for each virtual channel on
the 10TCC10GT to Maintenance (for example, VCH-2-2-1) .
Note the Admin State setting, to be able to revert to the original state after the
loopback setting is activated.
Step 5 Select .
Step 6 For each payload channel on this module, change the Admin State to
Maintenance (for example, PCH-2-2-N).
Step 7 Select .
Step 8 In the Ports blade, select the network interface (for example CH-1-x-Nx) for
which you wish to set the loopback.
Step 9 Set the Admin State to Maintenance.
Step 10 Select .
The Loopback field is now accessible.
Step 11 Set Loopback to either an internal or facility loopback, or remove an already
active loopback. The options are:
• Facility - which sets a facility loopback on the interface
• Terminal - which sets a terminal loopback on the interface
• None - this removes an already active loopback.
If the interface is a member of a protection group this command will be

denied.
Note
Step 12 Select to activate the loopback setting.

Step 13 Set the Admin State to its original setting before testing with loops.
Step 14 Select to save this setting.
Configuring Clock Speeds
Configuring Clock Speeds

Clock speeds are defined when an interface is created. This section describes the
procedure for setting clock speeds.
Requirement
You must be logged on to the NE with an ADMIN privilege level account.
Step 1 Select .
Step 2 In the Navigation Tree, select Shelf > Module slot .
Step 3 In the Ports blade, select Add.
Step 4 Configure these settings in the Add facility window:
• Select an interface (this example refers to the client interface of a
WCC10G-D module).
• Set Facility Type to the desired setting.
Depending on the selected clock speed (Facility Type), additional fields are
presented. Configure them according to your network plan.
Example for 10GE LAN:
Step 5 Configure the interface settings, including the Admin State.
Step 6 Confirm the settings with .
Setting Auto Laser Shutdown

This section describes how to set auto laser shutdown (ALS) on a channel module. Refer
to the Module and System Specification, Appendix A for an overview of the channel
modules that support ALS, and an ALS switch-off.
Changing ALS may be service affecting depending on the channel

module.
Note
ALS is a method of providing eye safety for open fiber connections. When a fiber is
detected to be open, the line side transmitter initiates a pulsing behavior to reduce the
optical output power and thus provide eye safety. When the fibers are determined to be
reconnected, by the end-to-end receivers detecting the pulses, the transmitters are
enabled and the link is established again.
In certain configurations, the default and normal working condition is to have ALS
disabled. Laser safety is not affected by the disabled ALS in this case. An NE with a
ROADM, EDFA-C-D27-GCB-DM, or EDFA-C-S26-VGC-DM is an example of this.
Requirement
You must be logged on to the NE with an ADMIN privilege level account.
Step 1 Select .
Step 2 In the Navigation Tree, select Shelf > Channel Module slot.
Step 3 In the Ports blade, select the relevant client or network channel (for example,
the network channel CH-1-1-NE), where ALS needs to be set.
In response, the Configure Details window opens.
Step 4 To be able to set ALS, set the Admin State to Management. Your choice here
depends on the situation requiring the ALS change. Laser safety will not be
affected.
Step 5 Select to save your setting.

The Auto Laser Shutdown field is now accessible.
Step 6 In the Port Function blade, set Auto Laser Shutdown:
• To enable the ALS mechanism, select either Short Pulse (ALS) or Long
Pulse (SDH-ALS) from the Auto Laser Shutdown drop-down list. Use
“Long Pulse (SDH-ALS)” if your channel carries SDH/SONET traffic (e.g.
STM-16).
• To disable the ALS mechanism, select Disable. As a result, the channel
module transmitter will continue to be on.
Step 7 Select to activate your setting or Cancel to abort.

Step 8 Set the Admin State to the value used before you set Auto Laser Shutdown,
or select Auto In Service.
Step 9 Select to activate your setting.
Forcing and Releasing Lasers

This section describes how to force a channel-module laser to be permanently on and
how to release an already forced-on laser. This can be done for the client port as well as
for the network port.
CAUTION Laser Radiation Hazard!

(1) Only Service Personnel are allowed to configure a network
Hazard
laser/amplifier/switch to “Force On” mode.
Level 3B
(2) The “Forced On” mode is only permitted for testing and servicing
purposes.
(3) Setting a network laser/amplifier/switch to “Force On” mode
increases the hazard level of the device. The operating
organization is solely responsible for the safety of the end-to-end
system.
(4) Service Personnel must assure that the device is located in an
appropriate area which guarantees that the conditions for an FSP
3000R7 are potentially met up to Hazard Level 3B.
Requirements
• You must be logged on to the NE with an ADMIN privilege level account.
• To receive reliable Optical Power Received (OPR) values and valid PM records at
the network-Rx interface, a valid signal has to be applied to the client-Rx interface.
Otherwise, alarms/conditions will be reported, e.g. loss of clock, invalid or wrong
OPR values.
The following modules are affected by this requirement:
• WCA-PCN-2G5U
• WCA-PC-10G-V
• 2WCA-PCN-10G
• 4WCE-PCN-16GFC1
Other transponder modules such as WCC-PCTN-10G, 2WCA-PCN-10G, or 2TWCC-
PCN-2G7U have to be configured so that their network-Tx interface will send an error
propagation code (EPC) or alternatively is mapped to the optical transport unit (OTU).
Step 1 Select .
Step 2 In the Navigation Tree, select Shelf > Channel module slot.
Step 3 In the Ports blade, select the relevant client or network channel (for example,
CH-1-1-NW) for which the laser needs to be “forced on”.
Step 4 To be able to force a laser on, set the Admin State to Maintenance.
Step 5 Select to save your setting.

The Force Laser On checkbox is now accessible.
1Without inserted and supported SFP+ at the respective port, the network port will not
emit any light although the network laser is forced on.
Step 6 Choose the desired option:

• Select the Force Laser On checkbox to force the laser on. This
setting will override the ALS setting for the laser and should only be
used for diagnostic purposes.
• Deselect the Force Laser On to release a forced-on laser. If the ALS
mechanism is enabled, it will now switch the laser on or off
accordingly.

Step 8 Set the Admin State to the value used before you forced the laser
ON/released the forced-on laser, or select Auto In Service.
Checking for Higher-Level NTP Servers
Checking for Higher-Level NTP Servers

This section describes how to check for higher-level NTP servers. That is to ensure that
your system clocks are synchronized.
It is only possible to check for higher-level NTP servers via the Craft
Console and with root account privileges.
Note
Step 1 Select External Applications > Shell from the Craft Console main menu. In
response, a command line window is shown.
Step 2 At the Linux prompt type su - to change from ADMIN to the “root” account.
The root user account is the most powerful user account and is only
intended for support personnel.
Note
Step 3 Enter a valid root password or the default password CHGME.1.

Please use exit or Ctrl-D to return.
[ADMIN@DOKU_NE ADMIN]$ su -
Password:
[root@DOKU_NE root]#
Step 4 At the prompt type ntpq.

Step 5 At the “ntpq>” prompt type peers. If a higher-level NTP server is available, the
following screen appears:
If no higher-level NTP server is available, the NCU will ignore the NTP
server it is connected to (in the above example it is the NTP server
172.25.5.57) and the “refid” (reference ID) column is empty.
Note
Step 6 To exit this window, press CTRL+D. This will return you to the root account.
Step 7 Press CTRL+D again to access the admin prompt.
Step 8 Press CTRL+D a third time to return to the Craft Console main menu. As soon
as you are back in the Craft Console main menu, you lose root account
privileges. You automatically regain the user account privilege you were
previously logged on with (e.g. ADMIN).
Configuring an OSCM
Configuring an OSCM
This section describes how to configure an OSC module. The OSCM has very few
configurable settings. Most important for the end user is the ability to configure line
monitoring thresholds.
Requirement
Step 1 Select .
Step 2 In the Navigation Tree, select Shelf 1 > OSCM module slot.
Step 3 Expand the OSC Ports blade, then select the SC-X-X-Nx Ethernet 100FX
interface for which you wish to configure line monitoring thresholds (for
example, SC-1-3-NW).
Step 4 Under the Port Function blade, configure the following line monitoring
thresholds, as required:
• Intrusion Threshold - This value defines a threshold for intrusion
monitoring based on the normal line attenuation in dB measured on the Rx
fiber. If the line attenuation changes by this value in a certain time frame,
an alert is generated (Rx Fiber-Intrusion). The alert will clear
automatically once the line attenuation returns to its original level.
• Rx Degrade Threshold - This value defines the alarm threshold in dB of
the calculated span attenuation of the OSC optical span connected to the
near-end OSCM Rx port. The system calculates the span attenuation by
taking the absolute value differences of the OSCM receive power level on
the near-end OSC facility that is being provisioned and the far-end OSC
facility transmit power level. If the span attenuation is greater than this
value, default set at 25 dB, then an "SD-ATRCV" standing condition is
generated.
Configuring OSPF
Configuring OSPF
This section describes how to configure OSPF.
Requirement
Step 1 Select .
Step 2 In the Navigation Tree, select Management Network.
Step 3 Set the IP Address according to your network plan.
The IP address functions as the OSPF router ID.
Changes to the IP Address (OSPF router ID) will only become effective
after the NE has been restarted. Please perform a manual restart after
changing this parameter. Each NE needs to have a unique OSPF router
Note ID.
Step 4 Select .
Step 5 In the Navigation Tree, select Shelf 1 > NCU slot.
Step 6 Expand the Ethernet Ports blade, then select the corresponding SC-1-A-
{C|C1|C2} interface (for example, SC-1-A-C1).
Step 7 Provision these parameters in the designated order:
• Set OSPF Routing to Enable .
• Enter a value for the Routing Metric. This parameter translates to the
"costs". The higher this number, the more expensive a route becomes
when using this link. Changes to this parameter are effective
immediately.
• Enter the desired OSPF Area. Changes to this parameter are
effective after setting the OSPF Routing to Disable, confirming with
, changing it back to Enable, and again confirming with
If you do not establish adjacency when using OSPF with authentication,

verify that the authentication string matches on both ends of the link.
Note
Tracking a Channel in a Node

Tracking a channel through the node follows the channel path starting from a designated
end-point. In most cases, one of the channel end points must be an Optical Line (OL) and
the other is a channel module port.Tracking stops where the channel path is not
provisioned, the physical connection has not been entered or the channel termination
point on an OL or a channel module is reached.
Tracking a channel identifies the ports on modules that support the channel, starting from
the user-specified end-point to the other end-point.
Current optical layer performance monitoring (PM) values can also be displayed, where
supported. You can use the values to verify signal flow and to ensure that fibers are clean
and properly connected.
Tracking a channel can also be used to determine whether the necessary physical
connections have been entered or if a desired channel path is available.
Tracking a Channel through a Node

Channel tracking may be a single channel path for unidirectional channels or multiple
channel paths for bi-directional, drop-and-continue, or multicast channels. Channels can
be tracked starting from designated endpoints: Optical Line, External Channel or Channel
Module N port.
This procedure describes how to select a channel to trace through a node.
Step 1 Select .
Step 2 In the Navigation Tree, select either:
• Optical Lines
• External Channels
• Shelf > slot for the channel module.
Step 3 In the Main Pane,
• Right click an optical line and select Track Channel.
• Expand the Optical Channels blade, then right click an optical channel
and select Track Channel.
• Right click an external channel and select Track Channel.
• Expand the Ports blade, then right click a network port and select Track
Channel.
The Track Channel window opens, displaying the channel path. When you
select an optical line as the starting point, you must select a Channel.
Step 4 Click the Graphic tab to view a graphical representation of the channel trace.
Step 5 If desired, select the Optical Power PM checkbox to view the current optical
power levels associated with the ports/channel.
Table 97 on p. 587 addresses some fields shown in the trace.
Table 97: Track Channel
Column Name Description
ID Each number represents a different uni-directional path for the

channel.
Route Type Describes the segment:

• Fiber
• Cable
• Equipment (EQPT)
• Provisioned (PROVND)
• Backplane (BACKPL)
total/ppc total indicates the measured optical power for the interface. It
is displayed when supported.
ppc indicates the measured optical power per-channel for the
channel. It is displayed after total and /, when supported.
"OUTAGE” is displayed when performance monitoring is
supported, but the facility is not operational. For example, the
port has a Loss of Signal (LOS) alarm.
“n/a” is displayed when performance monitoring is supported
but the optical power value is not returned.
Tracking a channel can also be performed in the Monitor application.

Note
Configuring Trace Monitoring

Trace monitoring is a means to ensure connectivity within a network.
• A trace message is defined for a connection.
• The message is entered in the trace overhead of the transmitted signal.
• The message received is checked against an expected message. A mismatch
indicates the sender and receiver are not supposed to be connected, or may be
incorrectly connected.
It is recommended that the trace message used for an individual connection be globally
unique in its network layer. There must be agreement on the trace message for a
connection.
Trace monitoring is supported on SONET, SDH, and OTN interfaces.
• SONET/SDH interfaces support Section/Regenerator Section (RS) trace monitoring.
The Section/RS trace is supported according to Telecordia GR-253 or ITU G.707 and
G.783. To provision SONET/SDH traces, proceed to “Configuring SONET/SDH
Traces” on p. 589.
• OTN interfaces support trace monitoring in OTU, ODU and activated TCM layers
according to ITU G.709 and G.798. To provision OTN traces, proceed to “Configuring
OTN Traces” on p. 590.
Configuring SONET/SDH Traces

This section describes the steps for configuring SONET/SDH traces, using an example
OC-48 interface.
Step 1 Identify the following:

• The channel modules in the network at each end of the connection.
• The trace message layer.
• The trace message format (1-byte, 16-byte or 64-byte).
• The trace message for this connection (refer to your network plan).
• If the trace monitoring should report the Trace Identifier Mismatch
(TIM) alarm.
Step 2 Log on to the NE with a channel module supporting the connection and select
.
Step 4 Expand the Ports blade, then select the port carrying the connection (for
example, CH-7-2-NE).
Step 5 Select the Traces blade to display trace-related parameters.
Step 6 If relevant, set the TIM Mode to Enable-No AIS. The TIM alarm is then raised
when a trace mismatch is detected, but an AIS is not inserted.
The TIM alarm is disabled by default.
Step 7 Enter the trace message the channel module expects to receive for this
connection, as follows:
a) Select the Trace Format you identified in Step 1.
b) Set Trace to Expected (EXP).
c) Select either the ASCII or HEX message format.
d) If you selected the 16 Byte CRC-7 trace format and you wish to enter the
message according to ITU G.831, select the G.831 checkbox.
e) Enter the trace message you identified in Step 1, according to the trace
format you specified.
f) Select .
For easier provisioning, you may accept the received trace by selecting
. The system copies the received trace

into the expected trace field and will then accept the received trace as
Note valid.
Step 8 Enter the trace message the channel module will transmit for this service, as
follows:
a) Select the Trace Format you identified in Step 1.
b) Set Trace to Transmitted.
c) Select either the ASCII or HEX message format.
d) If you selected the 16 Byte CRC-7 trace format and you wish to enter the
message according to ITU G.831, select the G.831 checkbox.
e) Enter the trace message you identified in Step 1, according to the trace
format you specified.
f) Select .
Step 9 Log on to the NE with the other channel module.
Step 10 Repeat Step 3 to Step 8 to provision the expected and transmitted trace
messages.
Configuring OTN Traces
This section describes the steps for configuring OTN traces, using an example OTU2
interface.
Step 1 Identify the following:

• The channel modules in the network at each end of the connection..
• The trace message layer.
• The trace message for this connection (refer to your network plan).
• If the trace monitoring should report the Trace Identifier Mismatch
(TIM) alarm.
Step 2 Log on to the NE with a channel module supporting the connection and select
Step 4 Expand the Ports blade, then select the port carrying the connection (for
example, CH-11-1-N).
Step 5 Select the Traces blade to display trace-related parameters.
Step 6 Select the Layer of the channel to enter a trace message for (for example, the
OTU layer).
Step 7 If required, set the TIM Mode to Enable-No AIS or Enable-Generate AIS1.
• Enable-No AIS will raise a TIM alarm when a trace mismatch is detected.
• Enable-Generate AIS will raise a TIM alarm when a trace mismatch is
detected and will also insert ODU-AIS downstream of the TIM detection.
The TIM defect detected at either the ODU or OTU layer will result in
insertion of ODU-AIS for further downstream processing. In the case of a
network port detecting an ODU/OTU TIM, ODU-AIS is applied towards
the client port. The client operation will apply consequent actions
appropriate for the client facility type when ODU-AIS is received.
Note
For further details, please refer to the Configuration Management section
in the System Description.
Step 8 Enter the trace message the channel module expects to receive for this
connection, as follows:
a) Set Trace to Expected (EXP).
b) Select either the ASCII or HEX message format.
c) Select the G.709 checkbox, if you wish to enter the message according to
ITU G.709/G.798.
d) Enter the trace message you identified in Step 1 in the SAPI field.
The FSP 3000R7 does not use the DAPI or operator specific message
portions in the comparison.
e) Select .
For easier provisioning, you may accept the received trace by selecting
. The system copies the received trace

into the expected trace field and will then accept the received trace as
Note
valid.
Step 9 Enter the trace message the channel module will transmit for this service, as
follows:
a) Set Trace to Transmitted.
b) Select either the ASCII or HEX message format.
c) Select the G.709 checkbox, if you wish to enter the message according to
ITU G.709/G.798.
d) Enter the trace message you identified in Step 1 in the SAPI, DAPI, and
OPSP fields.
1The Enable-Generate AIS option is not supported on all modules or at all layers.

Currently, this option is only available on the network ports of WCC-PCTN-100GB and
10TCC-PCTN-10G+100GB modules, at the ODU and OTU layers.
e) Select .
The FSP 3000R7 does not use the DAPI or operator specific message
portions in the comparison, but if this connection is terminated in non-
ADVA Optical Networking equipment, that equipment may use them.
Note
Step 10 Log on to the NE with the other channel module.

Step 11 Repeat Step 3 to Step 9 to provision the expected and transmitted trace
messages.
Configuring Wavelengths
Some modules feature a network interface that is fully tunable from channel #D01 up to
channel #D32, including #DC1 to #DC9, in a wavelength grid of 100 GHz. Each channel
can be tuned by using the NE management tools.
This section describes how to configure a channel on a tunable network interface.
This section contains the following subsection:
“Reconfiguring Wavelengths” on p. 593
Step 1 Select .
This channel is unassigned and must now be created.
Step 3 Expand the Ports blade, then select Add.
Step 4 Select the network facility (for example, CH-12-4-N).
Step 5 Select the desired wavelength from the Channel drop-down menu.
Step 6 Provision all required parameters according to your network plan.
Step 7 Select to add this channel.
Reconfiguring Wavelengths
To reconfigure the channel, perform these steps.
Step 1 Select .
Step 3 Expand the Ports blade, then select the channel you wish to modify (for
example, CH-12-4-N).
Step 4 Change the Admin State of the network facility to Maintenance.
Step 5 Select .
The Channel field is now accessible.
Step 6 Select the new wavelength from the Channel drop-down menu.

Step 8 Change the Admin State of the network facility to In Service.
Restarting Modules
Restarting Modules
This section describes how to restart or re-initialize a module. A module may be cold-
restarted or warm-restarted.
Cold Restart
A cold restart initializes the hardware and any configured service of the corresponding
cold-started module.
A cold restart may be applied after an upgrade of the module’s firmware (including a new
FPGA release).
The initiation of a cold restart can result in the following:
• reloading and reprovisioning of the corresponding cold-restarted module
• clearing of alarms for which the condition to raise that alarm is no longer present
• traffic interruption
It is not possible to cold-restart legacy modules via management

software.
Note
Warm Restart
A warm restart initializes the firmware of a module without interrupting traffic (non-service
affecting). It may be applied after an upgrade of the module software (without a new
FPGA release).
A warm restart clears alarms for which the condition to raise that alarm is no longer
present.
Follow these steps to manually restart a module:
Step 1 Select .
Step 3 In the Main Pane, select .

The Restart window opens, displaying the restart options and details
associated with the selected restart option.
Restarting Modules
If the module does not support remotely initiated cold start, the Cold
Restart option will not be available.
Note
Step 4 If the module offers multiple restart options, select the restart type you wish to
initiate (Warm Restart or Cold Restart).
Cold restarting a module is service affecting!

Note
Step 5 Select or Cancel to abort.
Exporting Network Element Logs
Exporting Network Element Logs

The NE stores log files which can be exported to an external location for troubleshooting
purposes. The log files available on an NE depend on the NE configuration. The following
is a list of all supported log files:
• Event log
• System log
• Database Change log
• Equalization log
• Control Plane log
• Crypto log
NE logs are exported in CSV format. Opening an exported log file requires that the local
regional settings for date and time on the computer you use are the same as were used
when the CSV file was created. Otherwise, the event timestamps may be converted
incorrectly. Date and time are stored internally in the log file in the format yyyy-mm-dd
and hh:mm:ss.ss, respectively.
Follow these steps to export a log file from the NE:
Step 1 Select .
Step 2 In the Navigation Tree, expand Logs to display all available log files.
Step 3 Select the log file you wish to export.
The Main Pane displays the contents of the selected log file.
Step 4 Click Export (in the Main Pane on the upper right) to upload this log file.
Step 5 Enter relevant details in the PC dialog to save this log file to your PC or an
external file server.
Configuring Equipment Capabilities

This section describes how to provision the capability of a module to support added
features. Modules may acquire additional features after a software update, firmware
update or a hardware revision. With the option to increase the capability of a module and
thus add new features, new parameters could be made available for this module. As a
result, windows may vary because different parameters are available after increasing
capability on the module. However, no new module has to be introduced and service will
not be affected on the NE.
The following sections are covered:
“Increasing Capability” on p. 598
“Viewing Capability Level” on p. 598
Increasing Capability
This section describes how to increase capability of a module by choosing the highest
possible capability level and thus supporting all features available for the module.
Step 1 Select .
Step 3 In the Main Pane, select the row corresponding to the module's equipment
details.
Step 4 Set the Capability to the highest level possible for this module.
For more information about the feature set corresponding to each level, see the
Release Note and Compatibility Matrix from the Partner Login.
Step 5 Select to save your settings or Cancel to abort.
Viewing Capability Level

This section describes how to find more information about the capability level chosen and
the maximum possible level available for this module.
Step 1 Select .
Step 3 In the Main Pane, select the row corresponding to the module's equipment
details.
The Configure Details window opens. Note the current Capability of this
module.
Field Name Description
Capability This is a brief description of the capability level

chosen for this module. This includes information
about the feature set covered at this level.
Step 4 Select .
Step 5 In the Navigation Tree, select Inventory to display all the currently installed
modules.
Step 6 Select the corresponding module from the equipment list in the Main Pane.
The Inventory window for this module opens.
Step 7 Note the Module Capability Level and Module Capability fields.
Field Name Description
Module Capability Level This shows the maximum provisionable capability

level for this module.
Module Capability This is a brief description of the maximum

provisionable capability level. This includes
information about the feature set covered at this
level.
Chapter 15
Updating Software, Firmware, and

Database
This chapter contains instructions for updating network element (NE) application
software and firmware, and for backing up and restoring the internal database of the NE.
The procedures described in this section are demonstrated using the Network Element
Director.
“About Software and Database Files” on p. 602
“Database Restoration Guidelines for Control Plane Users” on p. 607
“Backing Up and Restoring the Database” on p. 610
“Viewing Module Firmware Versions” on p. 616
“Updating the NE Software Release” on p. 617
“Performing Other Software Update Actions” on p. 628
“Transferring Files To/From the NE” on p. 633
About Software and Database Files

This section gives background information about how NE software packages and
database files are handled on the network element. For information about software and
database updates using TL1, refer to "Software & Database Management" in the TL1
Commands and Syntax Guide.
The Software Package

The NE software is the complete software load for the NE. It is a software generic and
contains all code that runs on an NE. The NE software version number is equal to the
release number. The release number syntax is XX.YY.Z. The XX and YY represent
numbers between 1 and 99, and are increased for major and minor releases, respectively.
Z is increased for maintenance releases and can be a number from 1 to 9 or a letter from A
to Z. It starts with 1 and continues into letters in alphabetical sequence, if necessary.
Figure 37: Software Package
The NE software is a package containing these files:

• The configuration file. This file is interpreted for the correct transfer of all required
software. It is named F70XXYYZ.CON and contains the following information:
o
The names of the NE software files with their version number and size
o
The names of all firmware package (FWP) files in the FWP set and the FWP
version
o
The type of NCU that each FWP is supported by.
• The NCU software files. The NCU software is the part of the NE software that runs
on the NCU. It includes the Linux operating system and environment and the FSP
3000R7 applications. Each NCU type supports a different set of modules. To save
space and to avoid overloading the NCUs, three software files are provided. The
NCU software files are named as follows:
o
H70XXYYZ.PGM for the NCU-II/NCU-II-P
o
N70XXYYZ.PGM for the NCU-S
o
O70XXYYZ.PGM for all other NCU types
• The firmware package (FWP) set files.The FWP set contains the individual FWPs
for all modules that are supported by the NE software, except encryption modules.
Each FWP is the software that runs on a particular module type. It contains code for
all processors on the module as well as FPGA code. You may select which FWP to
activate on the individual modules. Each NCU type supports a different set of
modules. To save space and to avoid overloading the NCUs, three FWP files are
provided. The FWP set files are named as follows:
o
S70XXYYZ.PGM for the NCU-II/NCU-II-P
o
M70XXYYZ.PGM for the NCU-S
o
T70XXYYZ.PGM for all other NCU types
• The firmware package (FWP) set files for encryption modules. These files are
not included in the regular software package. These FWP files are made available
through the Customer Portal at http://www.advaoptical.com/ and they are only
retrievable for customers who have ordered encryption hardware modules. The FWP
set file is named as follows:
o
C70XXYYZ.PGM
Handling of Files
The NE software and database files are stored in the active and standby areas on the
NCU.
Figure 38: Overview of Software and Database File Handling
The NE software in the active or standby area consists of one NCU software file, the
FWP files for each module type, and the configuration file. In addition, the active or
standby area contains a database framework with default values. These files originate
from an NE software package. The database file in the active area contains the current
configuration of the running system. The standby area originates from the default factory
installation or from a restoration of a backed up database.
The active area contains the files that are currently used by the NE. The standby area is
used to prepare a change in software and/or database versions by installing the new file
versions to the standby area. The NE starts using the new versions when the contents of
the standby area are activated, which means that the standby area becomes the active
area, and the active area becomes the standby area. Thus, the previously active version
is contained in the standby area until a different file version is installed in the standby
area. The standby software files and database files can be activated individually.
The file area is an intermediate storage area located on a RAM disk (RDISK) on the NCU,
and is cleared on reboot. It is used to download software and database files from external
servers to the NE, and to upload backup database files to external servers.
Files can be downloaded and uploaded by using file transfer protocol (FTP) or secure
copy protocol (SCP). Like SSH, SCP uses secure socket layer (SSL) technology. NEs
with a first generation NCU are not capable of providing FTP or SCP server functionality,
for example, when serving the role of GNE for other NEs. Second generation NCUs can
act as an FTP or SCP servers, as they contain a stronger processor with sufficient
random-access memory (RAM). For more information about which NCUs are of first
generation or second generation, refer to “NCU Troubleshooting” on p. 509.
Database backup files can alternatively be stored in a file area on the SCU, and restored
from this area on the SCU. This requires an SCU-II, an SCU-S, or an SCU with hardware
revision 2.01 or higher.
Software and Database Compatibility

The NE software and database that will be activated on an NE must be compatible.
When a software update is performed using a valid update path, the database version is
compatible. Otherwise, the database may not support the software functionality, or vice
versa. This may affect services.
To prevent a database from making service affecting (SA) changes to the installed
modules, the NCU detects when it is inserted into a new network element, as well as
when a new Compact Flash (CF) has been inserted. It then switches to an auxiliary
database. This auxiliary database functions as a security mechanism, in which the
equipment settings are not altered by it. It will therefore not have an impact on a running
system. The auxiliary database uses the default IP address, and thus management
contact with the NE will be lost. You will have to be on site, and reconnect to the NE
using a serial connection, to restore contact. Refer to the FSP 3000R7 Provisioning and
Operations Manual for guidelines on fixing the problem.
Software Update and Switchback

During activation of a software release, the first step taken by the system is to preserve
the former software database. This is done by copying the former database to the active
area and migrating its format to the new software version. The format update is
necessary for the database to match the features of the new software version. In
addition, the first time a software release is activated, the former software database is
copied to the standby area.
If you update a protected NCU, the standby NCU will be updated automatically during the
activation of the software release on the active NCU.
Figure 39 illustrates a software update scenario. An NE operating with software release
8.1.0 is updated to software release 8.3.2. Since the user chose to keep the current
database during software activation, the previous database was migrated to the software
release 8.3.2 format. This database is labeled 8.3.2a.
Figure 39: NE Software Update, First-time Activation
You may revert to the previous software release after a software release update, if the
standby database has not changed. Figure 40 illustrates a scenario where the
NE operating with software release 8.3.2 is switched back to software release 8.1.0.
Here the user chose to use the standby database (8.1.0).
Figure 40: Switchback to Previous NE Software and Database
When switching back to the previous software, you may choose to keep the current
database (in the active area) for the new software and not touch the database in the
standby area. Figure 41 illustrates this scenario. The NE operating with software release
8.1.0 is switched back to software release 8.3.2. Since the user chose to keep the current
database, the system migrates the previous database (8.1.0) to the software release
8.3.2 format. This database is labeled 8.3.2b.
Figure 41: NE Software Activation Keeping Current Database
The databases 8.3.2a and 8.3.2b are simply instances of previously

used databases, migrated to the software release 8.3.2 format.
Note
If you attempt to download and activate an older software release, one which does not
conform to the active or standby database format, the system only allows you to reset to
the default database. This leads to the permanent loss of the database previously located
in the standby area and may affect traffic on a live system! Please consult ADVA Optical
Networking Technical Services if you are contemplating downgrading to an older
software release.
About NE Software Version and File Names

For all NE software files, the XXYYZ in the file name indicates the version of that file, and
uses the same syntax as for the release number.
The release number of the NE software package is updated when the version number of
any of the other files in the NE software package is updated. Using R9.2 as an example,
the release 9.2.1 NE software package consists of the following files: F7009021.CON,
H7009021.PGM, O7009021.PGM, S7009021.PGM, and T7009021. After one
maintenance NCU software update and two FWP set updates, the release number would
be 9.2.4.
Database Restoration Guidelines for Control Plane Users
Database Restoration Guidelines for Control

Plane Users
Control Plane users are recommended to back up databases immediately after the
tunnels are created and whenever there is a change to the tunnel.
A Control Plane user may need to restore the database for the following reasons:
“Fixing Corrupted Database on a Single NE” on p. 607
“Provisioning a Green-field Network” on p. 609
The backup and restore operations addressed in this section are

described in “Backing Up and Restoring the Database” on p. 610.
Note
Fixing Corrupted Database on a Single NE

This scenario assumes that you have identified a node with a faulty database, whereas
the databases of the neighboring nodes are in pristine condition.
Ideal Case
In the ideal case, a backed up database that exactly matches the signaling state in the
network is available. Restoring this stored database on to the NE takes care of
automatically restoring (and re-synching with the neighbors) the Control Plane state on
that NE.
Case 1: Signaling state for tunnel is present in the

network, but the restored database has no knowledge
of it
This would result in the connections for the tunnel showing up while the tunnel itself is
absent. If the data plane is intact (no traffic hit), the recommended course of action is to
abandon the connections and then adopt the tunnel.
Case 2: Restored database has a tunnel marked "in-

service", but no signaling state (connections) is
present in the network
If the data plane is intact (no traffic hit), the recommended course of action is to abandon
the tunnel and adopt it again.
Case 3: Restored database has a tunnel marked "in-

service", signaling state for the tunnel is present, but
the connections in the database do not match those in
the network
This case would result in double the number of connections for the ingress tunnel. The
recommended course of action is to abandon all the connections (including the tunnel)
and then adopt the tunnel.
The cases addressed herein assume that the faulty database is on an

isolated node and that its neighbors are intact. Consider the case where
multiple adjacent nodes (signaling neighbors) have faulty databases and
the database restoration needs to be performed for all the nodes. In this
scenario, the connections need to be abandoned at the ingress and also
Note at the node (the first "good" node) immediately succeeding the sequence
of faulty nodes. After the connections have disappeared on all the nodes,
the tunnel needs to be abandoned and adopted again.
To adopt the tunnel, refer to “Converting an Existing Service to Control

Plane Management” on p. 544".
Note
Case 4: Database was restored while tunnels were in

service
If a database restore was performed while tunnels were in service, attempts to abandon
the tunnel fail. The tunnels remain in state, "Tunnel setup in progress".
Execute the steps outlined in this recovery procedure.
Step 1 Delete all transport connections/CNX entities on the path of the service.
Generally, the deletion of a single CNX automatically removes all remaining
CNXes.
This action removes the data plane, but is not a traffic concern since the
intention for transitioning to Signalling state is to abandon the tunnel.
Note
Step 2 On the NE where the database restore was performed, remove any data plane
entities used by the tunnel, if they were not automatically removed in Step 1.
Step 3 Repeat Step 1 to Step 2 for all services you intend to tear down.
Step 4 Restart the NE, as detailed in “Restarting the NCU” on p. 517.
Provisioning a Green-field Network

This is similar to the case where the ingress has a tunnel "in-service" while the network
does not have a corresponding signaling state. The recommended course of action is to
abandon the tunnel and adopt it again.
To adopt the tunnel, refer to “Converting an Existing Service to Control

Plane Management” on p. 544".
Note
Backing Up and Restoring the Database

You can back up the active database, and later restore the database to the NCU. Backing
up the database should be done regularly, and should always be done before you update
software on the NE, as a precaution.
The backup database can be uploaded to a remote file server for storage, or it can be
stored on the SCU. Only SCU hardware revisions 2.01 or later support database backup,
while all SCU-S and SCU-II hardware revisions support database backup.
When the database is stored on the SCU and database auto restore is enabled, or when
the NE is equipped with NCU-II-P modules in a protected configuration,
NCU replacement and database recovery are simpler processes. The NCU software
release must be 9.2 or later to back up or recover the database from the SCU.
This section contains instructions for backing up and restoring the database. The
following relevant topics are addressed:
“Backing Up the Database” on p. 610
“Backing Up the Database at a Scheduled Time” on p. 611
“Restoring the Database” on p. 614
Backing Up the Database

This procedure describes how to back up the database. The backup database should be
stored remotely or on the SCU.
Requirements
• You must be logged on with an ADMIN or PROVISION privilege level account.
• The SCU in shelf 1 must be an SCU-II, an SCU-S, or an SCU with hardware revision
2.01 or higher, to save the backup database to the SCU. When the SCU version
does not support database backup, the SCU cannot be selected as a database
backup destination.
Step 1 Select .
Step 2 In the Navigation Tree, select Database > Backup.
Step 3 In the Manual Database Backup blade, select the Destination (storage
location) for the database backup:
• Select Remote Server to back up the database to an external file server.
• Select SCU if available (supported) to back up the database to the SCU.
• Select Active NCU RAM to back up the database to the RAM.
• A database back up to the SCU overwrites any existing database

stored on the SCU.
• A backup database stored in the NCU RAM is lost during an NCU
Note restart.
Step 4 When backing up the database to an external server, enter the following
additional settings:
a) Set the Transfer Protocol.
b) Select the Source IP Address:
• Default, if the management network is configured to route IP
addresses in the range of the physical IP interfaces.
• System, if the management network is configured to route IP
addresses in the range of the System IP addresses.
c) Enter the IPv4/v6 Address of the remote server.
d) Enter the User Name and Password to access the remote server.
Follow any case-sensitive rules imposed by the remote server.
e) Specify the remote server Directory Path Name, if needed.
Database backup options:

• You may include or exclude Users Information such as username,
password, and so on.
• You may encrypt the backup database, this requires a password.
• In NEs equipped with a first generation NCU or an NCU-II, a backup
to the SCU may be automatically restored by setting Database
Note Auto Restore to Restore from SCU. This may be required when
the NCU is replaced, or if the NCU database becomes corrupted.
Database Auto Restore is not applicable to NEs equipped with
redundant NCU-II-P, the database is automatically synchronized
between the NCU-II-P.
Step 5 Select .
Note the backup database file name for future reference.

Note
Backing Up the Database at a Scheduled Time

This procedure describes how to schedule automatic database backups. The backup
database may be stored on a remote sever or the SCU.
Scheduled database backups must be enabled to be performed. You may choose to
disable the scheduled backups at any time.
Requirements
• You must be logged on to the NE with an ADMIN or PROVISION privilege level
account.
2.01 or higher, to save the backup database to the SCU. When the SCU version
backup destination.
Step 1 Select .
Step 2 In the Navigation Tree, select Database > Backup.
Step 3 In the Scheduled Database Backup blade, select the Destination (storage
location) for the database backup:
• Select Remote Server to back up the database to a remote file server.
• Select SCU, if available (supported), to back up the database to the SCU.
A database back up made to the SCU overwrites any existing database

stored on the SCU.
Note
Step 4 Enter the following settings:

a) Select the interval between each backup in the Interval field.
b) Enter the date the first backup should be performed in the Backup Start
Date field.
c) Enter the time the first backup should take place in the Backup Start Time
field.
The backup is performed according to local time of the NE and the

backup start date and time.
Note
d) [Optional] Select the Add Time to File Name checkbox, to include a

timestamp in the backup database filename.
Step 5 When backing up the database to an external server, enter the following
additional settings:
Database backup options:

• You may include or exclude Users Information such as username,
password, and so on.
• You may encrypt the backup database, this requires a password.
• In NEs equipped with a first generation NCU or an NCU-II, a backup
to the SCU may be automatically restored by setting Database
Note Auto Restore to Restore from SCU. This may be required when
the NCU is replaced, or if the NCU database becomes corrupted.
Database Auto Restore is not applicable to NEs equipped with
redundant NCU-II-P, the database is automatically synchronized
between the NCU-II-P.
Step 6 Click to save the settings.

If Scheduled Backups is not selectable, please correct any remote server-
related information entered in Step 5. If the problem persists, contact your
network administrator.
Step 7 Activate the scheduled database backup by setting Scheduled Backups to
Enable.
The Next Scheduled Date field displays the date and time that the next
database backup is scheduled to be performed.
Step 8 Click to save the settings.
Viewing Files Stored on the NE

This procedure describes how to view files stored on the NCU or SCU.
Requirements
The SCU in shelf 1 must be an SCU-II, an SCU-S, or an SCU with hardware revision
2.01 or higher, to save/view the backup database on the SCU. Selection of SCU as a
database backup location is hidden when the SCU version cannot support database
backup.
Step 1 Select .
Step 2 In the Navigation Tree, select File Storage.
Step 3 In the Main Pane, select the Location of the files to view:
• Select Active NCU RAM for files saved to the NCU RAM.
• Select SCU, if available, for files saved to the SCU.
• Select Active NCU for files saved to the NCU.
• Select Active NCU/Path Results for files saved to the NCU for Tunnel
Path Analysis.
The Main Pane displays file name, size and creation date/time of the files.
Restoring the Database

This section describes how to restore a database stored on a remote server or locally.
Database restoration is typically performed after an NCU replacement or software
downgrade.
• If the backup database is stored on the SCU and the NE is equipped with a first
generation NCU or an NCU-II, you may use the “auto restore” feature.
• If the database file is stored on a remote server, the restoration process requires
downloading the file from the remote server to the NCU.
Requirements
• You must be logged on to the NE with an ADMIN or PROVISION privilege level
account.
• If the database file is encrypted, this procedure requires the encryption password to
restore the database.
2.01 or higher, to restore the backup database from the SCU. When the SCU version
backup destination.
Before restoring the database of an NE in a network that uses Control

Plane, set all tunnels to Signaling with abandon option. Otherwise, the
database restore will lead to error conditions which can only be resolved
via manual intervention, as outlined in “Case 4: Database was restored
Note
while tunnels were in service” on p. 608.
Step 1 Select .
Step 2 In the Navigation Tree, select Database > Manage.
Step 3 In the Restore Database blade, select the Source Location:
• Select Remote Server if the backup database is stored on an external
server.
• Select SCU, if available (supported), if the backup database is stored on
the SCU.
• Select Active NCU RAM, if the backup database is stored in the NCU
RAM.
Step 4 When restoring from a remote server, enter the following settings:
f) Enter the File Name of the database file.

g) If the database file is encrypted, enter the Encryption Password.
Step 5 Select .
A warning appears.
Step 6 Select to continue or Cancel to abort the database restoration.

The activation process restarts the NCU, which takes a few minutes to
complete.
After four consecutive beeps, the NCU MOD LED changes from blinking to
solid green to indicate the NCU has completed the restart and you can log in.
Viewing Module Firmware Versions
Viewing Module Firmware Versions

This section describes how to determine the firmware version a module is operating with.
Step 1 Select .
Step 2 In the Navigation Tree, select Software > Module.
The Main Pane displays the list of all modules.
• The FWP Version (Active) column displays the currently active firmware
version on the module.
• The FWP on NCU (Active) column shows the firmware version that is
available for this module in the active NCU software package.
• The Impact on Service column indicates whether activation of the
corresponding firmware package interrupts traffic.
FWP denotes the firmware package.

Note
In native1 modules:
• The FWP Version (Standby) column displays the firmware version
installed on the backup area of this module.
Note • The FWP on NCU (Standby) column shows the firmware version
that is available for this module in the NCU standby partition.
1Legacy modules were originally developed for the FSP 2000, but converted for operation
in the FSP 3000R7. Native modules were designed for the FSP 3000R7. For further
information, refer to Appendix C: Equipment Types of FSP 3000R7 Hardware
Components in the Hardware Description.
Updating the NE Software Release

This section provides an overview of the steps for updating the NCU software and
module firmware on a Network Element (NE).
Requirements
• A remote server must contain all software release files in the same directory
(location).
• The remote server must be accessible via FTP or SCP.
• The remote server must support FTP passive mode when FTP is used.
• The remote server must be reachable by the NE or management gateway NE (GNE).
• When the network uses a GNE, the software must be installed on the GNE first then
the GNE is used as the file server for the other NEs in the network.
• If any files in the NCU RAM need to be saved, upload the files to an external file
server, as described in “Uploading Files from the NCU” on p. 633.
• System log entries are overwritten when upgrading from software release 12.2 or
earlier to 12.3 or later. If the system log is needed then use export, as described in
“Exporting Network Element Logs” on p. 597.
• Refer to the Compatibility Matrix available on the Customer Portal to determine the
minimum installed software release required for this software release update.
Do not remove, reseat or restart modules during the software release

update.
Note
FWP-Mismatch alarms indicate a mismatch between the active

NCU software release and the currently active firmware package
(FWP) on a module. Do not make provisioning changes to modules with
Note FWP-Mismatch alarms.
Starting with software release 13.2.1, firmware packages may be

installed from the NCU standby area, then activated with the
NCU activation. FWP installation can be performed prior to a
Note maintenance window.
An NCU with a software release prior to 7.1.0 may have different optical
power thresholds for pluggable transceivers than later releases. Optical
power thresholds outside the updated pluggable transceiver spe-
Note cifications will be reset to default values.
After the software release update is complete on an NE equipped with

amplifiers that support automatic amplifier shutdown, under
, General > Controls in the Functionality blade

ensure the Amplifier LOS Response is set for the desired operation. If
you wish the amplifiers to remain in operation when a network fiber is
cut, set the Amplifier LOS Response to Remain On. Otherwise, set it
to Auto Off. Amplifiers which support automatic amplifier shutdown
include:
• AMP-S20H
• AMP-S20L
Note • EDFA-C-S20-GCB
• EDFA-C-S20-GCB-DM
• EDFA-C-D20-VGC
• EDFA-C-D20-VGC-DM
• EDFA-C-D20-VLGC-DM
• EDFA-S20H
• EDFA-S20L
• 2EDFA-S20-S10
Figure 42 on p. 619 shows three methods, #1, #2 and #3, for updating the software
release.
• Flow #1 has the fewest steps and works well for test labs and small nodes.
• Flow #2 allows the NCU and all modules to be updated but can require two
maintenance windows.
• Flow #3 allows transfers to the NCU and native1 modules before the maintenance
window and minimizes the loss of node visibility and firmware mismatch alarms.
1Native modules were designed for the FSP 3000R7. Legacy modules were originally
developed for the FSP 2000, but converted for operation in the FSP 3000R7. For further
information, refer to Appendix C: Equipment Types of FSP 3000R7 Hardware
Components in the Hardware Description.
Figure 42: Software Release Update Process
This section addresses the software release update methods represented by flow #1 and
flow #3 in Figure 42 on p. 619. The software release update steps include:
1 Create a database backup for the current software release, in case the software
release needs to be reverted.
2 Transfer the software release to the NCU.
3 Transfer the firmware package to native modules.
4 Activate the software release in the NCU standby area and the firmware packages in
the native modules' backup area.
5 If the node contains legacy modules, update the firmware packages on those
modules.
6 Create a database backup for the new software release in case of an NCU failure.
7 [Optional] If required for security purposes, disable the FTP client, FTP server, or
SSH server.
If you update a protected NCU, the standby NCU will be updated automatically during the
activation of the software release on the active NCU.
Back up the NCU database, as described in “Backing Up the Database” on p. 610.
To start the software release update, proceed to “Transferring Software to the NCU” on
p. 620.
Transferring Software to the NCU

This procedure describes how to transfer a software release from a file server to the
NCU.
If the software version you wish to update is listed in the Standby

Software Release blade under Node > Software > NCU, the software
is already installed and only needs to be activated.
Note
Requirements
Step 1 Select .
Step 2 In the Navigation Tree, select Software > NCU.
Step 3 In the Transfer Software to Standby Area blade, set the Source Location
of the software files to Remote Server.
Step 4 Enter or select:
a) Transfer Protocol.
b) Source IP Address:
c) IPv4/v6 Address of the remote server.
d) User Name and Password to access the remote server following any
case-sensitive rules imposed by the remote server.
e) Directory Path Name on the remote sever, if needed.
If the remote server is a GNE, set Directory Path Name to /cfdisk.

Note
f) File Name for the software configuration file (*.CON file).
Step 5 Click .
The software files are transferred to the NCU standby area. The transfer time
depends on the connection bandwidth between the NE and remote server.
When the transfer is complete, the Standby Software Release blade
displays the Software Release.
Step 6 [Optional] You may enter a Comment in the Standby Software Release
blade and confirm with .
The Standby Software Release blade displays a "WRONG PARTITION LAYOUT"

warning if the NCU-II has a wrong compact flash layout. This does not affect NE
operations such as software activation, database backup, database restore, and NCU
restart. However, module operations such as firmware installation, firmware activation,
and module restart may be affected. To resolve this, replace the NCU-II as described in
“Replacing a Malfunctioning NCU” on p. 530. Consult ADVA Optical Networking
Technical Services to temporarily resolve this issue.
If the Standby Software Release blade displays no warnings, the next step in the
software release update is to transfer firmware packages from the NCU standby area to
native modules, as described in “Transferring Firmware Packages to All Modules
(Native)” on p. 621.
Transferring Firmware Packages to All Modules (Native)

Firmware packages (FWP) are downloaded to the NCU as part of the software release,
as described in “Transferring Software to the NCU” on p. 620.
The firmware update process, which includes the installation and activation of FWP,
must be triggered by an operator. Firmware updates typically take about five minutes to
complete, however some modules may take considerably longer. To reduce downtime
during a system software release update, the FWP may be transferred to native modules
from the NCU standby area, then activated during or after the NCU software activation.
On legacy modules, the firmware must be transferred and activated after the NCU
software activation is complete.
If modules are removed or lose power during a firmware update, the

module firmware will be corrupted. Native modules revert to the FWP
installed in the backup area.
Note
Some FWP updates may be service affecting, the user interface

indicates the update effect. Take the necessary precautions for a service
interruption before starting a service affecting update or activation.
Note
FWP downgrade to an older release is supported, but is limited to

Release 9.1 or later. Downgrades are service affecting for all
FSP 3000R7 modules. However, downgrades to a FWP before Release
9.3 on FSP 3000R7 modules that were upgraded to a FWP from Release
Note
9.3 or later, are marked as not service affecting.
Only the standby module in a channel card protection configuration is

updated when a firmware update is service affecting. You must perform
a protection switch, then activate the other module. Modules in client
channel card protection configurations always accept FWP updates. The
Note FWP update is not blocked when the module is active, even when the
update is service affecting.
Some modules which support fiber detection may raise a HWANR

(Hardware Degrade) condition for up to five minutes during firmware
update.
Note
The Firmware Package (FWP) Release Status table displays the number of modules
that require firmware installation and/or activation. To access this information, select
Software > Module under :

• Modules with FWP denotes the modules that require a firmware update.
• Modules at Release denotes the modules which are already operating with the
required firmware package.
• Modules not at Release denotes the modules which are operating with a different
firmware package.
• Modules waiting for activation denotes the native modules which have the
firmware package in the standby area. These modules require firmware activation.
Requirements
• The desired software release must be installed on the NCU.
Step 1 Select .
Step 3 On the Module tab in the Main Pane, click .

The Firmware Package Transfer window opens.
Step 4 To transfer the FWP from the standby NCU area, set Transfer from NCU
Area to Standby.
Step 5 Click .
Once the transfer is complete, FWP Version (Standby) for each native
module indicates the same FWP version as shown in FWP on NCU
(Standby).
The next step in the software release update is to activate the NCU software and module
firmware packages, as described in “Activating Software” on p. 623, or only the NCU
software, as described in “Scheduling Software Activation” on p. 624.
Activating Software
This procedure describes how to activate the software release for the NCU and native
modules at the same time.
Requirements
Step 1 Select .
Step 3 Ensure the standby area contains the desired software release in the Standby
Software Release blade.
If the Software Release is incorrect, install the correct software release as
detailed in “Transferring Software to the NCU” on p. 620.
Step 4 Click in the Activate Software in Standby Area blade.

The Activation of Software in Standby Area window opens.
Step 5 Select the database to use when the standby software release is activated.
• Select Current when upgrading to a new software.
• Select Standby when updating to the previous software release in the
standby area. This option is also relevant if you switch between NCU
software versions on active and standby images and you wish to preserve
the associated database of these versions.
Use the Default-Factory option only for special cases such as updating
an NCU to be used as a spare. The default settings resulting from the
Default-Factory option depends on the release. For an overview of
default settings in this release, refer to the “Security Management”
Note
chapter in the System Description.
Step 6 Select Activate FWP on Modules to activate the firmware packages (FWP)
installed on the standby area of each native module.
Activating the FWP and the NCU software in one step ensures that FWP-
Mismatch alarms are not raised on these modules once the NCU software
activation completes.
Step 7 Click to start the activation.

The activation process takes several minutes to complete. The NCU signals
the activation is complete with four consecutive beeps and by changing the
NCU MOD LED from blinking to solid green. The NCU is then ready for log in.
Step 8 Log on to the NE.
Step 9 Verify the NCU is running the desired software release with the following
steps:
a) Select .
b) In the Navigation Tree, select Software > NCU.
c) Verify the Software Release under the Active Software Release blade.
First generation NCUs may fail the software activation process when
there is insufficient NCU memory to support the software release. The
software activation failure is indicated in the Comment field of the
Standby Software Release blade by "Database too big for this NCU
type".
To successfully update to the software release, replace the NCU with a
Note second generation NCU, such as NCU-II, or contact ADVA Optical
Networking Technical Services.
For information about how to upgrade to a second generation NCU, refer
to “Replacing a First Generation NCU with an NCU-II” on p. 537.
If the NE contains legacy modules, the next step of the software release update
is described in “Transferring and Activating Firmware on All Modules” on p. 625.
Otherwise, back up the database, as detailed in “Backing Up the Database” on p. 610.
[Optional] If required for security purposes, disable the FTP client, FTP server, or SSH
server.
Scheduling Software Activation

This procedure describes how to schedule activation of the software release on an
NCU after it has been transferred to the NCU standby area.
Scheduled NCU software activation must be enabled to be performed. You may choose
to disable the scheduled activation any time before the activation starts.
Requirements
Step 1 Select .
Step 3 Ensure the standby area contains the desired software release in the Standby
Software Release blade.
If the Software Release is not correct , install the correct software release as
described in “Transferring Software to the NCU” on p. 620.
Step 4 In the Schedule Activation of Software in Standby Area blade:
• Set Scheduled Activation to Enable.
• Enter the Activation Date for the software.
• Enter the Activate Time for the software.
Step 5 In the Database on Activate field, select the database to use when the
software release is activated.
• Select Current when upgrading to a new software.
• Select Standby when updating to the previous software release in the
standby area. This option is also relevant if you switch between NCU
software versions on active and standby areas and you wish to preserve
the associated database of these versions.
Use the Default-Factory option only for special cases such as updating
an NCU to be used as a spare. The default settings resulting from the
Default-Factory option depends on the release. For an overview of
default settings in this release, refer to the “Security Management”
Note
chapter in the System Description.
Step 6 Click to save your settings.
The next step of the software release update is to activate the firmware on the
modules, as described in “Transferring and Activating Firmware on All Modules” on
p. 625.
Transferring and Activating Firmware on All Modules

This procedure transfers and activates the FWP to all modules that are not at the same
software release as the NCU in one step.
When upgrading from software versions earlier than R13.1.1, it is recommended to
update all SCUs, as detailed in “Updating Modules of the Same Type” on p. 632, then
execute this procedure to update all remaining modules.

module firmware may be corrupted. Native modules revert to the
FWP installed in the backup area, while legacy modules require a special
Note recovery procedure.
Some FWP updates may be service affecting, the user interface

indicates the update effect. Take the necessary precautions for a service
interruption before starting a service affecting update or activation.
Note
FWP downgrade to an older release is supported, but is limited to

Release 9.1 or later. Downgrades are service affecting for all
FSP 3000R7 modules. However, downgrades to a FWP before Release
9.3 on FSP 3000R7 modules that were upgraded to a FWP from Release
Note
9.3 or later, are marked as not service affecting.
Only the standby module in a channel card protection configuration is

updated when a firmware update is service affecting. You must perform
a protection switch, then update or activate the other module. Modules in
client channel card protection configurations always accept
Note FWP updates. The FWP update is not blocked when the module is
active, even when the update is service affecting.

update.
Note
The Firmware Package (FWP) Release Status table displays the firmware status of
each installed module. Access this information under > Software >
Module and sort by one of these criteria:
• Modules with FWP
• Modules at Release
• Modules not at Release
• Modules waiting for activation
• Modules that must be updated with Transfer & Activate
Transfer & Activate transfers the firmware package then immediately

activates the firmware package in one step. Transfer & Activate works
for all modules.
Note
Requirements
• The NCU must be running the desired software release.
• Refer to the release notes to determine whether the firmware update impacts the
performance monitoring counters for the module you wish to update. If the
performance records are required to be saved, perform “Saving Performance
Monitoring History Records” on p. 652 before this procedure.
Step 1 Select .
Step 3 Select the Module tab in the Main Pane, then click .
The Firmware Package Transfer and Activate window opens.
Step 4 Select the Permitted Effect for the firmware update to the modules.
• Select NSA for non-service affecting updates.
• Select SA to allow service affecting updates at the time the firmware is
activated.
Step 5 Click .
Once the firmware installation and activation completes, FWP Version
(Active) displays the updated FWP.
If the FWP activation fails with the error message, "Firmware Activate

Failed", repeat this procedure to update the FWP of the affected
module/modules. If the FWP activation fails repeatedly, contact ADVA
Note Optical Networking Technical Services.
The next step of the software release update is to back up the database, as described in
“Backing Up the Database” on p. 610.
[Optional] If required for security purposes, disable the FTP client, FTP server, or SSH
server.
Performing Other Software Update Actions

This section addresses maintenance activities which may be required once the NE is
operating with the desired NCU software and module firmware.
These sections are addressed:
“Reverting to the Previous Software Release” on p. 628
“Updating Modules with Encryption” on p. 628
“Updating HD Module Firmware” on p. 630
“Updating a Module” on p. 631
“Updating Modules of the Same Type” on p. 632
Reverting to the Previous Software Release

You can revert to the previous software release after a software release update, if the
standby database has not changed.
If another software release has been installed or the standby database has been
changed, reverting to the previous software release may not be possible or changes can
be lost.
This procedure describes how to revert to the previous software release, using the
database saved at the time of the last software activation.
Requirements
• You must be logged on with an ADMIN privilege level account.
• The previous software release must be available in the NCU standby area.
Step 1 Activate the software as described in “Activating Software” on p. 623, select

Standby for the Database Activation.
The contents of the standby area must be the former NCU software release
and database.
Step 2 If necessary, downgrade the individual firmware packages for the relevant
modules/module types, as described in “Transferring and Activating Firmware
on All Modules” on p. 625.
Updating Modules with Encryption

Firmware updates for encryption modules are distributed separately from standard
software release. Modules with encryption are only supported in software releases 10.3
and higher.
To update encryption module firmware, execute the following procedures in the
designated order:
“Enabling Update of Modules with Encryption” on p. 629
“Updating Encryption Module Firmware” on p. 629
Enabling Update of Modules with Encryption

Requirements
• NCU with the desired software.
• Crypto Officer password
• You must be logged on with an ADMIN or CRYPTO privilege level account.
Step 1 Select .
Step 2 In the Navigation Tree, select Shelf > Encryption module .
Step 3 In the Main Pane, click the equipment row.
Step 4 In the Encryption Access blade, enter the FWP Encryption Release.
Step 5 Set FWP Encryption Update to Enable.
Step 6 Click to save your settings.

You are prompted to enter the Crypto Officer password.
Step 7 Type the Crypto Officer password in the designated field.
Step 8 Select to confirm the setting.

Repeat this procedure for all encryption modules to be updated.
Updating Encryption Module Firmware

Requirements
• Encryption firmware package for the modules to be updated.
Step 1 Select .
Step 3 Click .
The AES Module FWPs Download window opens.
Step 4 Enter these settings for the remote server:
a) Enter the IP Address of the remote server.
b) Set the Transfer Protocol.
c) Select the Source IP Address:
Step 5 Click .
The encryption firmware package is downloaded to the NE.
Step 6 Select the appropriate encryption module you wish to update.
Step 7 Ensure that the correct firmware revisions of the encryption module are
displayed:
• FWP Version (Active) displays the current module firmware revision.
• FWP on NCU (Active) displays the revision that becomes active on the
module when updated.
Step 8 Click .
Updating HD Module Firmware

Firmware updates for HD modules are distributed separately from standard software
release. HD modules are only supported in software releases 16.2 and higher.
Requirements
• Z70xxyyz.PGM file for the target release is located on the FTP server.
• Firmware package files (.PAK) for all HD module types are located on the FTP server
in a directory called “HD.”
Step 1 Select .
Step 3 Click .
The HD Modules FWPs Transfer window opens.
Step 4 Set Transfer to NCU Area to the desired setting:
• Select Active if the NCU software will not be changed.
• Select Standby if firmware packages will be activated with the NCU
software.

Step 6 Click .
The HD module firmware package is downloaded to the NE.
Step 7 Select the appropriate HD module you wish to update.
Step 8 Ensure that the correct firmware revisions of the HD module are displayed:
• FWP Version (Active) displays the current module firmware revision.
• FWP on NCU (Active) displays the revision that becomes active on the
module when updated.
Step 9 Click .
Once the firmware transfer and activation completes, FWP Version (Active)
displays the updated FWP.
Updating a Module
This procedure may be used to update the FWP on a module that does not match the
version associated with the NCU active software release.

module firmware will be corrupted. Native modules revert to the FWP
installed in the backup area, while legacy modules require a special

update.
Note
Requirements
Step 1 Select .
Step 3 Select the Module tab in the Main Pane.
Step 4 Click on the row with the desired module.
The Firmware Package Upgrade window opens.
Step 5 Click .
displays the updated FWP.
Updating Modules of the Same Type

This procedure may be applied to update the FWP on modules of the same type when the
modules do not match the version associated with NCU active software release.

module firmware may be corrupted. Native modules revert to the FWP
installed in the backup area, while legacy modules require a special

update.
Note
Requirements
Step 1 Select .
Step 3 Select the Type tab.
The Main Pane displays all the module types installed on this NE.
Step 4 Select the module type you wish to update.
The Firmware Package Upgrade window opens.
Step 5 Select the Permitted Effect for this module type.
• Select NSA, for non-service affecting updates.
• Select SA, to allow service affecting updates at the time the firmware is
activated. Services will not be affected at any other time.
Step 6 Select .
under the Module tab displays the updated FWP.
Transferring Files To/From the NE

When updating software, making a backup database or importing and exporting alarm or
external channel profiles, it is necessary to transfer files to or from the NE. Transferring
files to the NE denotes a download, transferring files from the NE denotes an upload.
This section describes how to transfer NE software, a backup database, and alarm or
external channel profiles to/from an NE.
The following topics are provided:
“Uploading Files from the NCU” on p. 633
“Downloading Files to the NCU” on p. 634
“Downloading Files from the SCU to the NCU” on p. 635
Uploading Files from the NCU

This procedure describes how to upload files from the NCU to an external server.
Do not reseat, restart, or disconnect the NCU during the file transfer.
Note
Each support data file is named after the NE name. If the NE name
contains these characters, the system replaces them with underscores
(_) in the support data file name:
Note \ / ` $ ! " ' * ? ; | > \t
Step 1 Select .
Step 3 In the Main Pane, select the Location of the file you wish to upload:
• Select Active NCU RAM for files on the NCU RAM.
• Select Active NCU for files on the NCU.
• Select Active NCU/Path Results for files on the NCU for Tunnel Path
Analysis.
Step 4 Double-click the file you wish to upload.
The Properties window opens.
Step 5 Click .
The Upload window opens.
a) Enter the IPv4/v6 Address of the remote server.
b) Specify the remote server Directory Path Name, if needed.
c) Set the Transfer Protocol.
d) Select the Source IP Address:

e) Enter the User Name and Password to access the remote server.
Step 7 Click .
Downloading Files to the NCU

This section describes how to download files from an external server to the NCU.
Do not reseat, restart, or disconnect the NCU during the file transfer.
Note
Step 1 Select .
Step 3 In the Main Pane, select the Location you wish to download the file to:
• Select Active NCU RAM for files on the NCU RAM.
• Select Active NCU for files on the NCU.
Step 4 Click .
The Download File window opens.
a) Specify the File Name.
b) Enter the IPv4/v6 Address of the remote server.
c) Specify the remote server Directory Path Name, if needed.
d) Set the Transfer Protocol.
e) Select the Source IP Address:
f) Enter the User Name and Password to access the remote server.
Step 6 Select to start the file transfer.
Step 7 If the file is not visible on the Main Pane, you may select .
Downloading Files from the SCU to the NCU

Files stored on the SCU cannot be directly uploaded to an external server. These files
must be moved to the NCU first. This section describes how to move files from the SCU
to the NCU.
Do not reseat, restart, or disconnect the NCU during the file download.
Note
Step 1 Select .
Step 3 In the Main Pane, set the Location to SCU.
The Main Pane displays name, size and creation date/time of the files stored
on the SCU.
Step 4 Double-click the file you wish to download.
The Properties window opens.
Step 5 Select .
Step 6 Set Location to Active NCU RAM.
The Main Pane displays the file.
Step 7 If the file is not visible on the Main Pane, you may select .
Chapter 16
Performance Management
This chapter contains the following sections:
“Introduction” on p. 638, which gives general information about Performance
management.
“Performance Monitoring at the Physical Layer” on p. 639, which describes the different
measurement ways of the physical layer parameters.
“Performance Monitoring at the Data Layer” on p. 642, which describes the different data
layer types.
“Performance Records” on p. 650, which describes the record types, record content and
record storage.
Introduction
Introduction
Performance management includes configuration of performance monitoring, viewing,
and reporting of performance data. This section addresses the performance counters and
records that the FSP 3000R7 supports.
The FSP 3000R7 provides monitoring of performance at module level, client interface
level, and network interface level.
The network element collects the following information:
• Physical layer measurements
• Data layer counters
The collected information is stored in records. A number of these records are stored to
provide a history.
In addition, the FSP 3000R7 provides current measurements of some physical-layer
parameters, such as transmit/receive optical power, which are not logged in records.
Hence they can only be viewed in real time.
The performance parameters measured and/or recorded may depend on the module type.
To find out the measured parameters/counters available for a specific module type,
please look up that module type in the Management Data Guide.
For more information about performance monitoring, refer to the Provisioning and
Operations Manual.
Performance Monitoring at the Physical Layer

Physical layer performance monitoring is performed at module and port level, the physical
layer includes the optical characteristics supported by the optical line monitoring
functionality. For a list of modules supporting the optical line monitoring functionality,
refer to the Module and System Specification.
The FSP 3000R7 provides physical layer measurements in two ways:
• real time measurements
• recorded measurements that provide minimum, mean, and maximum values for a
time period
Performance Monitoring has thresholds you can set so a Threshold Crossing Alert (TCA)
is generated if the measurement reaches or crosses the specified threshold. A TCA is
generated to make the operator aware of a potential change in performance. The TCA
clears when the measured value is within the threshold and hysteresis value.
• High Threshold minus hysteresis value
• Low Threshold plus hysteresis value
Some performance parameters have low and high thresholds, while others have either a
low or high threshold. Performance parameters can be user-configurable or fixed. All
thresholds have default values. Some thresholds can be set to zero to deactivate the
TCA.
In addition, FSP 3000R7 offers one error counter to monitor the entire physical layer.
Recorded Measurements
Every second the system measures and records the physical layer parameters listed in
Table 98. The parameters that are measured on a module or port depends on the module
type. The Management Data Guide provides a per module overview of which parameters
are measured for which ports.
At the end of the recording interval, the average value is calculated and stored in the
record. In addition, the lowest and highest values that were measured during the
recording interval are added to the record. The recording intervals are 15 minutes, 1 day,
and 1 week.
The average value over the recording interval is calculated by adding together all recorded
measurements and dividing by the number of seconds in the recording interval. Notice
that for parameters measured in dBm, this average, which is displayed as the “mean”
value, is not the average of the power level received within the 15 minute recording
interval. It is only the average value of the recorded power level measurements
expressed in dBm within the 15 minute period.
Table 98: Monitored Physical Layer Parameters
Physical Parameter Unit
Attenuation Rx Fiber dBm
Attenuation Tx Fiber dBm
Table 98: Monitored Physical Layer Parameters
Physical Parameter Unit
Current mA
Optical Power Rx dBm
Optical Power Tx dBm
OSC Gain dB
Back Reflection Rx dB
Pump Power dBm
OSC Power Rx dBm
Estimated Gain dB
Dispersion Compensation ps/nm
Link Attenuation dB
Real Time Measurements

The network element system measures the physical layer parameters listed in Table 99.
The parameters that are measured on a module, or port, depends on the module type. The
Management Data Guide provides a per module overview of which parameters are
measured and whether they are measured at the module or port. These parameters are
not recorded.
Table 99: Instantaneous Measurement Parameters
Physical Parameter Unit Description
Laser Bias Current mA Real time Laser Bias Current
Laser Bias Current Average mA Averaged Laser Bias Current 10

second window
Temperature °C Module or Plug Temperature
Temperature 2 °C Temperature second monitored

point
Laser Temperature °C Real time Laser Temperature
Current mA
Pump Power dBm
Pump-{1|2} Laser Temp °C
Pump-{1|2} Laser Bias Current mA
Attenuation dB
Table 99: Instantaneous Measurement Parameters
Physical Parameter Unit Description
External Loss dB Attenuation in dB from 1 stage

transmit to 2 stage receive
Hours of Operation h Accumulated total of operating

hours
Average measured BER Average measured Bit Error Rate for

the PRBS test signal
Maximum measured BER Maximum measured BER for the

PRBS test signal during monitored
time
Error free time for PRBS Sec Error free time for PRBS since last
detected error.
Elapsed Time Sec Elapsed time since PRBS test

signal start
OTDR Remaining Time Min Time remaining for OTDR

measurement completion
Max Output All PSUs dB Total power output (supplied)
Max Power All Equipment dB Total power uptake (consumption)
Physical Layer Counter

The FSP 3000R7 offers one counter for monitoring of the physical layer, depending on the
type of module. The supported performance counter is described in Table 100.
Table 100: Physical Layer Counter Descriptions
Counter name Description
Defect Seconds This counter is increased for each second in which an

error on the physical layer occurs.
Performance Monitoring at the Data Layer

Data layer performance is monitored at the interface level. The FSP 3000R7 offers
performance for monitoring of the following data layers:
• OTN (OTU, ODU, FEC)
• SDH/SONET
• Sub-aggregate layer
• GFP
• Ethernet
• Physical conversion layer
The data layers monitored for each module depends on the module type. For each data
layer a set of counters are recorded. The current values as well as historic values are
stored in records for 15-minute and 1-day periods. For the SDH/SONET or OTN layers,
you can set thresholds for each performance counter. All performance counter thresholds
have default values.
A threshold crossing alert (TCA) is generated when a data-layer performance counter
reaches or crosses a specified threshold, alerting the operator of a potential change in
performance. The TCA for a 15-minute collection period clears when the performance
counter is below the threshold for a 15-minute collection period. The TCA for a 24-hour
collection period is sent as a notification so the clear does not apply.
When an SDH, SONET or OTN layer is terminated, the module handles the overhead for
this layer as follows:
• In a port’s receive direction, the overhead bytes are read, and processed according to
the standards.
• In a port’s transmit direction, the channel module generates content and inserts this
in the overhead bytes.
When an SDH, SONET or OTN layer is not terminated, it is non-intrusively monitored.
The modules handle the overhead for this layer as follows:
• In a port’s receive direction, the overhead bytes are read, and processed according to
the standards for non-intrusive monitoring.
• In a port’s transmit direction, no processing takes place.
The following sections list the supported counters for each of the data layers.
SDH/SONET Performance
The supported set of performance counters for the Section/Regeneration Section and
Line/Multiplex Section are shown in Table 101.
Table 101: SDH/SONET Counter Descriptions
Counter Type Description
Errored Second This counter is increased for each second in which

one or more CV/BBEs, traffic disruptive defects,
connection defects, or BIP-8 violations are detected.
Severely Errored Second This counter is increased for each second in which the
number of bit parity violations is higher than a
configurable threshold, or in the case of traffic
disruptive or connection defects. The SES threshold
defaults to 30% of the transmitted frames. This
threshold applies to all relevant entities in the Network
Element.
Severely Errored Framing This counter is increased for each second with Out of
Second Frame (OOF)/Severely Errored Framing Seconds
(SEFS) or traffic disruptive defects.
Coding Violations This counter is increased for each parity

Background Block Errors violation/background block error. Given one second
for which the SES counter is increased, the parity
violations registered in this second are not counted.
Unavailable Seconds When more than 10 consecutive seconds of SES are

recorded, the unavailable second (UAS) state is
entered. The UAS counter is increased for each
second this state persists. These 10 consecutive
seconds are added to the counter. To exit the UAS
state, more than 10 consecutive seconds without
SES must be recorded. These 10 seconds are
considered available seconds
A Trace Identifier Mismatch (TIM) alarm is considered a traffic

disruption.
Note
The Management Data Guide provides a per module overview of the counters supported
for each port, as well as the maximum value that can be recorded and the record type.
OTN Performance
The FSP 3000R7 provides a set of performance counters for the OTU, ODU, and FEC
layers. The OTN counters are listed in Table 102.
Table 102: OTN and FEC Counter Descriptions
Counter Type Description
Errored Second (ES) This counter is increased for each second in which one or
more CV/BBEs, traffic disruptive defects, connection defects,
or BIP-8 violations are detected.
Severely Errored This counter is increased for each second in which the number
Second (SES) of bit parity violations is higher than a configurable threshold,
or when one or more traffic disruptive or connection defects
are detected. The SES threshold is set to 15% of the
transmitted frames. The SES threshold for each protocol
applies to the whole Network Element.
Background Block This counter is increased for each parity violation. Given one
Errors (BBE) second for which the SES counter is increased, the parity
violations registered in this second are not counted.
Unavailable Seconds When more than 10 consecutive seconds of SES are recorded
(UAS) the unavailable second (UAS) state is entered. The UAS
counter is increased for each second this state persists.
These 10 consecutive seconds are then added to the counter.
To exit the UAS state, more than 10 consecutive seconds
without SES must be recorded. These 10 seconds are
considered available seconds.
Corrected Errors This counter is increased for each error that is corrected. The
error itself results in an ES, even though it is corrected.
Uncorrected Block This counter is increased for each byte with an error that is not
Errors corrected.
Bit Error Rate This rate is computed in 15 minute and 24 hour intervals. The
rate increases with each corrected error in the given interval.
The Management Data Guide provides a per module overview of the counters supported
for each port. It also provides information about the maximum value that can be recorded
and the record type.
Physical Coding Sublayer (PCS) Performance

The FSP 3000R7 provides a set of performance counters for the physical coding sublayer
of Ethernet and Fibre Channel.
This set of counters are described in Table 103 on p. 645, however, not all modules
supporting these services support all of these counters. The Management Data Guide
gives a per module overview of the counters supported for each port, as well as the
maximum value that can be recorded and the record type.
In the column Counter Name, the counter name abbreviations that are displayed in the
management tool are shown in parentheses.
Table 103: PCS Counter Descriptions
Counter Name Description
Errored Second This counter is increased for each second in which one or
(PCS ES) more CV/DE/SEs or traffic disruptive alarms are
detected.
Disparity Errors This counter reports the number of detected 8B/10B

(PCS Disparity disparity errors (DE).
Errors)
Coding Violations This counter reports the number of detected code words
(PCS CV) violating the 8B/10B or 64B/66B coding rules, depending
on the module type.
Sync Header This counter is increased if more than 15 sync header

Errors (PCS SE) errors are detected inside a 125 µs time slot.
Coding Violations This counter reports the number of detected disparity

and Disparity errors (DE) and coding violations (CV). It is only
Errors applicable to interfaces with 8B/10B coding.
(PCS CV+DE)
Sub-aggregate Layer Performance

The 4TCA4GUS and 2TCA2G5 channel modules use a proprietary protocol on the network
port when operating in multiplexer mode. These channel modules provide a set of
performance counters for the sub-aggregate data layer at egress from de-multiplexing.
This set of counters is described in Table 104.
Table 104: Sub-aggregate Layer Counter Descriptions
Counter Name Description
Errored Second This counter is increased for each second in which one
or more CRC or traffic disruptive alarms are detected.
Severely Errored This counter is increased for each second in which the
Second number of CRC errors is higher than a fixed threshold, or
when traffic disruptive alarms are detected.1
Cyclic This counter is increased for every frame with an invalid

Redundancy CRC check sum.
Check
The Management Data Guide gives a per module overview of the counters supported for
each port, as well as the maximum value that can be recorded and the record type.
1For the 4TCA4GUS modules, this fixed threshold is 100. For the 2TCA2G5 module,
this fixed threshold is 800.
Ethernet Performance
Ethernet service counters (transmit and receive) are described in Table 105.
Table 105: Ethernet Counter Descriptions
Counter Description
name
Broadcast This counter reports the number of received broadcast

Frames Rx frames.
Bytes Rx This counter reports the number of received bytes.
CRC Errors Rx This counter reports the number of Ethernet MAC frames

with CRC errors in the receive direction.
Frames Rx This counter reports the number of successfully received

MAC Ethernet frames.
Frames Rx This counter reports the number of discarded Ethernet

Discarded MAC frames due to buffer overflow in the receive direction.
Multicast This counter reports the number of received multicast

Frames Rx frames.
Oversized This counter reports the number of received frames that are
Frames oversized.
Pause Frames This counter reports the number of received MAC Ethernet
Rx PAUSE frames.
Undersized This counter reports the number of received frames that are
Frames undersized.
Utilization Rx This counter reports the calculated utilization in percentage

(0% to 100%) for received Ethernet traffic. The current, high,
mean, and low values are displayed.
64 Byte This counter reports the number of received frames with a

Frames Rx length of 64 Bytes.
65-127 Byte This counter reports the number of received frames with a
Frames Rx length of 65-127 Bytes.
1024-1518 This counter reports the number of received frames with a

ByteFrame Rx length of 1024-1518 Bytes.
Table 105: Ethernet Counter Descriptions
Counter Description
name
1519+ Byte This counter reports the number of received frames of length
Frames Rx 1519 or more Bytes.
Broadcast This counter reports the number of transmitted broadcast

Frames Tx frames.
Bytes Tx This counter reports the number of transmitted bytes.
CRC Errors Tx This counter reports the number of Ethernet MAC frames
with CRC errors in the transmit direction.
Frames Tx This counter reports the number of transmitted Ethernet

frames.
Multicast This counter reports the number of transmitted multicast

Frames Tx frames.
Oversized This counter reports the number of transmitted frames that

Frames are oversized.
Pause Frames This counter reports the number of transmitted Ethernet

Tx Pause frames.
Undersized This counter reports the number of transmitted frames that

Frames are undersized.
Utilization Tx This counter reports the calculated utilization in percentage

(0% to 100%) for transmitted Ethernet traffic. The current
high, mean, and low values are displayed.
64 Byte This counter reports the number of transmitted frames with a

Frames Tx length of 64 Bytes.
65-127 Byte This counter reports the number of transmitted frames with a
Frames Tx length of 65-127 Bytes.
1024-1518 This counter reports the number of transmitted frames with a

Byte Frame Tx length of 1024-1518 Bytes.
1519+ Byte This counter reports the number of transmitted frames with a
Frames Tx length of 1519 or more Bytes.
GFP Frame Performance

The service counters that are supported for GFP-F frames are described in Table 106 on
p. 648. The service counters supported for GFP-T frames are described in Table 107 on
p. 648.
Table 106: Framed GFP Frame Counter Descriptions
CHEC Frames The GFP Core Header consists of a 16-bit PDU Length
Corrected Indicator (PLI) and a 16-bit HEC (cHEC) protecting the
Core Header. The cHEC corrects single bit errors and
this counter reports the number of successfully
corrected GFP Core Headers.
THEC Frames The GFP frame Type field is protected by a HEC (the
Corrected tHEC). The tHEC corrects single bit errors. This
counter reports the number of successfully corrected
Type Fields.
THEC Frames This counter reports the number of Type Fields that
Discarded were discarded due to a failed correction attempt.
Table 107: Transparent GFP Frame Counter Descriptions
CHEC Frames The GFP Core Header consists of a 16-bit PDU Length
Corrected Indicator (PLI) and a 16-bit HEC (cHEC) protecting the
Core Header. The cHEC corrects single bit errors and
this counter reports the number of successfully
corrected GFP Core Headers.
CHEC Frames This counter reports the number of Type Fields that were
Discarded discarded due to a failed correction attempt.
GFP Valid Frames This counter reports the number of received GFP frames
that were valid.
THEC Frames The GFP frame Type field is protected by a HEC (the
Corrected tHEC). The tHEC corrects single bit errors. This counter
reports the number of successfully corrected Type
Fields.
THEC Frames This counter reports the number of Type Fields that were
Discarded discarded due to a failed correction attempt.
S-Blocks This counter reports the number of discarded

Discarded Super superblocks due to errors detected in the superblock
CRC-16 error check.
EVC Frame Performance

The counters for EVC records are supported per EVC and per EVC CoS.
VLAN-based monitoring points are disabled by default and must be enabled via
management. The maximum number of simultaneously activated monitoring points is 100
per xPCA module. This includes both flow points and bridges.
Table 108: Counter Descriptions per EVC, at Receive
Counter Description Entity

name
Unicast Number of received Unicast frames per EVC at Flow point

Frames Rx Rx, counted prior to policing
Multicast Number of received Multicast/Broadcast frames Flow point

Frames Rx per EVC at Rx, counted prior to policing
Frames Number of received frames per EVC per CoS Policer

Green marked green at Rx, counted prior to policing
Frames Red Number of frames per EVC per CoS that are Policer
marked red and dropped by the policer
Bytes Green Number of received bytes per EVC per CoS Policer
marked green at Rx, counted prior to policing
Bytes Red Number of bytes per EVC per CoS that are marked Policer
red and dropped by the policer
Table 109: Counter Descriptions per EVC, at Transmit
Counter Description Entity

name
Unicast Number of transmitted Unicast frames per EVC at Flow point

Frames Tx Tx
Multicast Number of transmitted Multicast/Broadcast Flow point

Frames Tx frames per EVC at Tx
Frames Number of frames per EVC per CoS that are Bridge (queue)
Dropped dropped due to buffer overflow Tx
Bytes Number of bytes per EVC per CoS that are Bridge (queue)
Dropped dropped due to buffer overflow Tx
Performance Records
Performance Records
The FSP 3000R7 records physical-layer measurements in 15-minute, 1-day, and 1-week
intervals, and records data-layer performance and service counters in 15-minute and 1-
day intervals. 15-minute intervals start at a whole hour, a quarter past, half past or a
quarter to an hour. For example, 02:00, 02:15, 02:30 and 02:45. The 1-day intervals
always start at midnight. The 1-week intervals always start at 00:00 from Saturday to
Sunday.
When the secondary state of an entity is “Unequipped”, “Mismatch” or “Fault”,
performance recording for that entity is disabled and the content of the record so far is
discarded. This is, for example, the case when an SFP transceiver is unplugged.
For each of the record types you can do the following:
• View the content of the current record while it is being created. This is called the
Current Record.
• View the records after the recording interval has ended. A number of these records
are stored. The collection of these records is called the History Record.
• For the data-layer records only, reset the Current Record or the Current and History
Record list, if relevant.
Record Types
Current 15-Minute Record
The current 15-minute record contains the measurements or counters for the ongoing 15-
minute interval as well as the elapsed time of the ongoing interval. When the ongoing 15-
minute interval is completed, the content of this record is transferred to the historic 15-
minute record, together with a time stamp to identify it. Then the counter content is reset
and a new "current 15-minute record" is started.
History 15-Minute Record

The history 15-minute record contains the previous 15-minute records, as well as
information about the validity of each of these records. A maximum of ninety-six previous
15-minute records are stored. The ninety-seventh 15-minute record overwrites the oldest
stored record. Thus, the historic 15-minute records together represent a 24-hour history.
Current 24-Hour Record

The current 24-hour record contains the measured contents of the counter for the ongoing
24-hour interval as well as the elapsed time of the ongoing interval. When the ongoing 24-
hour interval is completed, the content of this record is transferred to the historic 24-hour
record together with a time stamp to identify it. Then the counter content is reset and a
new "current 24-hour record" is started.
History 24-Hour Record

The history 24-hour record contains the previous 24-hour records, as well as information
about the validity of each of these records. A maximum of thirty-one previous 24-hour
records are stored. The thirty-second 24-hour record will overwrite the oldest stored
record. Thus the historic 24-hour records together represent a 1-month history.
Performance Records
Current 1-Week Record

The current 1-week record contains the measured contents of the counter for the ongoing
1-week interval as well as the elapsed time of the ongoing interval. When the ongoing 1-
week interval is completed, the content of this record is transferred to the historic 1-week
record together with a times stamp to identify it. Then the counter content is reset and a
new "current 1-week record" is started.
History 1-Week Record

The history 1-week record contains the counter contents for the previous 1-week record,
as well as information about the validity of each of these records. A maximum of fifty-two
previous 1-week records are stored. The fifty-third 1-week record overwrites the oldest
stored record. Thus, the historic 1-week records together represent a 1-year history.
Record Content
Physical Layer
Each record contains the average value of the parameter over the recording interval, the
lowest and highest value measured in the interval, and an indication of the validity of the
record.
If optical performance monitoring is interrupted by an LOS or other failure in a monitoring
period, a value other than -99.0 dBm is displayed and the record is marked as invalid
(Valid = no). When the failure persists for an entire record, -99.0 dBm is displayed and the
record is marked as invalid.
Data Layer
Each record contains the count of events during the monitoring period.
If the performance monitoring is interrupted by an LOS or other failure in a monitoring
period, the record is marked as invalid (Valid = no).
Record Validity
A record is invalid in the following situations:
• When the recording period is shorter than the record interval. For example, the first
record is usually shorter than the interval unless it starts exactly at the interval start
time.
• When the administrative state has not been in “In Service” during the whole interval.
For example, setting a loopback requires the entity to be in administrative state
“Management”.
• When a threshold or measurement period has been changed during the recording
interval.
Performance Records
Record Storage
Records are located as follow:
• The 15-minute records are saved in RAM on the NCU. During a controlled shut down
of the NE (via your management system), the records are stored on the compact
flash (CF) on the NCU. Upon start up of the NE, the 15-minute records stored on the
CF are restored to the RAM. If the NE is powered off, or the NCU is extracted, these
records cannot be stored on the compact flash. The records are lost in this situation,
and a gap in the History 15-minute record will be seen.
• The 24-hour records are stored in the CF on the NCU.
• The 1-week records are stored on the CF on the NCU.
This means that if there is an uncontrolled shutdown, for example, if you re-seat the
NCU, the 15-minute records are lost. The 24-hour and 1-week records, however, are
maintained.
Saving Performance Monitoring History Records

This procedure describes how to export performance monitoring history records.
Step 1 Select .
Step 3 Select the blade corresponding to the port or data channel for which you wish
to export the history records (for example, the Network Ports blade).
Step 4 Click the History tab.
Step 5 Select 15 Minutes, Daily, or Weekly history records.
The Main Pane displays the history record for the interval you selected.
Step 6 Click Export, then follow the Windows dialog to save the records.
Step 7 Repeat this procedure for each interval, port, and module for which you wish to
save history records.
Chapter 17
Exchanging Equipment
This chapter provides instructions on exchanging optical modules, pluggable
transceivers, power supplies, dummy modules, fan units, air filter pads, front covers and
1HU shelves.
Risk of damage to fiber-optic connectors.

Do not disconnect or re-connect fiber-optic cables exposed to optical output power.
If the optical output power is greater than 13 dBm, it is recommended to always
disable the laser source before you disconnect or re-connect the optical fiber. If you
ignore this, the core of the fiber can be destroyed at high optical power levels.
Clean and inspect the fiber-optic connectors carefully before you re-connect them to
the optical ports.
Before you exchange any equipment, read and follow the safety
precautions stated in the Safety Guide. The Safety Guide contains
important information and defines the restrictions on who may carry out
different types of tasks. Failure to adhere to these guidelines could result
in personal injury or damage to equipment.
All equipment is provisioned and registered in the NE database.

Therefore all tasks involving the removal of equipment also involve
deleting the provisioned equipment from the database.
Note
After removing a plug-in module from the shelf slot, wait for at least
5 seconds before you insert it or another one again.
Note
The term plug-in module refers to all types of channel modules, optical filter modules,
management modules, optical protection switch modules, OSC modules, reconfigurable
optical layer devices, optical filter modules, optical amplifiers, dispersion compensation
modules, power supply units and fan units.
Replacing a Raman amplifier requires additional configuration steps
which do not apply to replacing other optical modules.
To replace a Raman amplifier in your system, see “Replacing a Raman
Note Amplifier” on p. 676.
After replacing an 8ROADM-C40/0/OPM module and reconnecting the
optical cables, issue an explicit equalization request on the module
network port.
For more information about user-initiated equalization requests, refer to
Note “User-Initiated Global Wavelength Power Level Equalization” in the
Chromatic Dispersion Compensation (CDC) values for 4TCC-PCTN-

10G+40G and WCC-TN-40G modules are module-dependent and must
be calibrated each time one of these modules is placed in service or
replaced. The automatic dispersion compensation routine is triggered
autonomously when these modules are replaced.
Note Note that the automatic dispersion compensation routine only searches
for the optimum CDC value within the existing network environmental
conditions present at the time that you execute the search.
Before exchanging equipment, perform these steps.
Step 1 Identify the physical location of the equipment to be exchanged.

Step 2 To exchange an optical module or pluggable transceiver, proceed as follows:
a) Use an appropriate software management tool to take the device out of
service.
b) Remove all optical cables from the module and from other equipment that
is connected to the equipment to be exchanged.
Step 3 Remove the equipment as described in one of the sections below.
Use correct procedures in handling the removed equipment as described in
“Handling Equipment” on p. 47 to avoid damage.
Step 4 To replace the equipment you removed, proceed as follows:
a) Install the replacement equipment as described in one of the sections
below.
b) Provision the equipment as described in the Provisioning and Operations
Manual.
Step 5 If you do not want to replace the removed equipment, insert a dummy module
to close the empty slot as described in “Inserting a Dummy Module” on p. 773.
The following sections are provided:

“Replacing an Optical Module” on p. 656
“Replacing an Encryption Module” on p. 668
“Replacing a Raman Amplifier” on p. 676
“Replacing Pluggable Transceivers” on p. 677
“Replacing Pluggable Transceivers in a Control Plane-based network” on p. 694
“Replacing Power Supply Units” on p. 697
“Replacing Fan Units and Fan Modules” on p. 737
“Replacing Air Filter Pads” on p. 746
“Replacing an SH1HU Shelf” on p. 752
“Replacing an SH7HU(-R), SHX9HU, or SH9HU Shelf” on p. 759
“Replacing a 40CSM/2HU Shelf” on p. 763
“Removing and Mounting Front Covers” on p. 768
“Removing and Inserting a Dummy Module” on p. 773
Replacing an Optical Module

This section describes how to remove and install optical modules.
The following subsections are covered:
“Removing an Optical Module” on p. 656
“Installing an Optical Module” on p. 660
Removing an Optical Module

This section describes the procedure of removing channel modules, optical filter
modules, optical amplifiers and protection modules. The procedure is common and
independent of the optical module types. The term “optical module“ refers to all of the
modules mentioned above.
For specific information about each optical module, refer to the Hardware Description.

CAUTION
Additional Information
Removal of NCU, SCU, OSC and channel modules does not affect the operation of the
other modules installed in the shelf. If removing an optical module permanently, the
corresponding database entity has to be deleted from the database.
Required Equipment
Before starting the procedure, ensure the following is available.
• Torx screwdriver TX10 to assist in loosening the knurled screws
• Appropriate dummy module to fill the empty slot
• Suitable grounded surface or an antistatic mat for placing the optical module
• Original shipping box including the static-protective package for saving the removed
module
• Appropriate blind plugs for inserting into the unused module receptacles
• Appropriate protective caps for covering the fiber connectors
• Tagging materials if necessary
Removal Procedure
Follow these steps to remove an optical module from a shelf slot.
To prevent ESD damage to the equipment take normal static precautions

for removing optical modules.
It is assumed that you are familiar with handling optical modules as well as fiber-optic
cables, and are aware of the precautions that should be taken to avoid damage to the
equipment. A summary of how to handle modules and fiber-optic cables is provided in
“Handling Equipment” on p. 47.
Several tasks must be completed. Some tasks are detailed in sub-tasks. Pay attention to
the safety notices and additional information that are given below.
Step 1 Read the installation plan to get information about:

• the module type that is to be removed.
• the shelf, which holds this module.
• the slot from which this module is to be removed.
Step 2 Before removing an SCU module, perform the following:
a) Set SCU Connections to "Linear".
b) Note the shelf number displayed on the shelf.
Step 3 Before replacing the spare module of a client channel card protection
configuration, ensure all client channel card protection groups on this module
are set to standby.
Step 4 Follow ESD safety guidelines. Attach the grounding wire to the ESD jack on
the shelf, next secure to your wrist.
Step 5 Find the physical location in the shelf of the module which is to be removed.
Step 6 If mounted, remove the front cover from the shelf as described in “Removing
an SH7HU, SH9HU, or SHX9HU Front Cover” on p. 768.
Step 7 Determine the physical location of the optical module to be removed within the
shelf.
Step 8 Check the operating status of the equipment and the present hazard level. If
any module in the system is operating in “Forced On” mode, this may raise the
hazard level of any network element. Do not proceed unless you have training
in laser safety.
Step 9 Identify the optical fiber pairs currently connected to the ports of the module.
For easy identification, complete the tags and attach them to the fibers.
Laser Radiation.
Invisible laser radiation may be emitted from a fiber-optic transmitter if
aperture interlocks are defeated. Never look directly at the optical
connector output beams when disconnecting the optical cables. Looking
CAUTION
directly at laser beams can cause permanent eye damage.
Raman amplifiers are high-powered devices. Always set the Network Port on a
Raman amplifier to 'Disable' before removing an optical cable. Failure to disable the
network port can result in optical connector damage.
Step 10 Remove all optical cables from the module to be removed and from other
equipment that is connected to this module. In doing so make sure not to
damage the optical cables and connectors. To remove an individual optical
cable proceed as follows:
a) Detach the connector on one end of an optical fiber and cover it with an
appropriate protective cap.
b) Detach the connector on the other end of this optical fiber and cover it with
an appropriate protective cap as well.
c) Lay the optical cable aside.
d) Insert the appropriate blind plugs into the relevant receptacles.
e) Repeat these sub-tasks for removing each optical cable.
Step 11 After taking off all relevant optical cables remove the optical module as
follows:
a) If applicable, remove the pluggable transceivers from the cages of any
channel module as described in “Removing an SFP or XFP Transceiver”
on p. 679.
b) Using your fingers or a Torx screwdriver TX10, turn the two knurled
Hot Surface!
Some channel module components such as heat sinks can become very
hot during operation. Touching a very hot component may cause skin
burns. Allow the module to cool before removing it from the shelf slot.
CAUTION
Put only cooled modules into the static-protective package.
c) Firmly pull on the screws until the module is free from the shelf and
screws.
• When removing an optical module from an SH7HU, SH9HU, or
SHX9HU shelf, slide it out vertically as shown in Figure 43 on p. 659.
• When removing an optical module from an SH1HU shelf, slide it out
horizontally as shown in Figure 44 on p. 659.

Slide the optical module out of the slot very carefully. Otherwise the components of
the PCB assembly can be damaged.
Figure 43: Removing a Channel Module from an SH7HU, SH9HU, or

SHX9HU Shelf Slot
Figure 44: Removing a Channel Module from an SH1HU Shelf Slot
Never reach into a vacant shelf slot. Contact with the adjacent optical modules or
the connectors on the backplane may damage the equipment.
Removal of an optical module is automatically detected by the

management software. Each time an optical module is removed from a
shelf slot, the internal network management system receives a trap
Note message.
d) Put the module onto a grounded surface or an antistatic mat and

immediately place it in the original static-protective package to avoid ESD
damage to the module.
lay the box aside.
Do not leave the shelf slot empty left by the removed module! To fill the empty slot
only use an appropriate dummy module. An empty shelf slot will result in an
inhomogeneous air stream and contamination of the installed optical modules and
components with dust and debris inside the shelf.
Step 12 Insert the dummy module as described in “Inserting a Dummy Module” on

p. 773.
Step 13 Repeat this procedure for each optical module to be removed from a shelf slot.
Step 14 If available, mount the front cover to the shelf as described in “Mounting an
SH7HU, SH9HU, or SHX9HU Front Cover” on p. 769.
Step 15 Detach the wrist strap from your wrist, disconnect the grounding cable from the
ESD grounding point on the shelf (if available) or the rack and lay the grounding
cable aside.
Step 16 Store the optical cables for future use.
Where necessary, return the defective module to ADVA Optical Networking for
repair. For details on returning modules, refer to the Installation and
If you have any problems that result in a deviation from the removal procedure
described above, contact ADVA Optical Networking Technical Services.
Installing an Optical Module

This section describes the procedure for adding channel modules, optical filter modules,
optical amplifiers, and protection modules. The procedure is common to all optical module
types.
For specific information about each optical module, refer to the Hardware Description.
Before connecting fiber-optic cables, install the optical module and

pluggable transceivers to the FSP 3000R7 system, as described in this
section. After physical installation, the module boots up.
Please wait about 1 minute until the boot, configuration, and initialization
Note time for protection is completed. Then fiber-optic cables can be
connected to the installed optical module and pluggable transceivers.

CAUTION
All optical modules are designed as plug-in modules that are compatible with any FSP
3000R7 shelf. Adding an optical module does not affect the operation of currently
installed modules in the shelf. There are no fixed slot positions for specific optical
modules. Each optical module can be inserted into a shelf slot without the use of any
tools.
In the majority of cases, optical modules require no additional configuration upon

replacement. Nevertheless, confirm that settings are correct, especially when adding
channel modules, by using management software to view the configuration details. If the
settings differ from your network requirements, reconfigure the module. Configuration of
optical modules is addressed in “Provisioning a Network Element” in the Provisioning and
Operations Manual.
The module inventory data stored in the EEPROM is accessible from the management
system. When auto-provisioning is enabled, the optical module will be entered into the
NE database with default parameters. See Provisioning and Operations Manual, section
"Modifying Provisioned Entities" for information about assigning equipment to the NE
database and configuring equipment.
Adding an optical module at a later time can change the optical budget. Use the FSP
Network Planner to calculate the changes or contact ADVA Optical Networking
Technical Services.
Risk of power supply failure!

Adding modules with relatively high power consumption at a later time can result in
power failure due to overload.
Pay attention that the total power consumption of a fully equipped shelf does not
exceed the specified value. Calculate the total power consumption or contact ADVA
Optical Networking Technical Services according to this before inserting the
module!
Equipment Required
Before starting the procedure, ensure the following is available:
• Optical module to be added, packaged in the shipping box. This module should be
equipped with the firmware package associated with the NE software.
• Original shipping box for storing the removed dummy module.
If the new optical module is not equipped with the firmware package
associated with the NE software, insert it into an unprovisioned slot on
the NE and update it before performing the steps outlined in this
procedure. Refer to “Updating a Module” on p. 631 for details on updating
Note
the module firmware.
Adding Procedure

for adding optical modules.
cables, and are aware of the precautions that should be taken to avoid damaging the
To add an optical module into a shelf slot, several tasks must be completed. Some tasks
are detailed in sub-tasks. Pay attention to the safety notices and additional information
given.
Step 1 Read the installation plan for information about:

• the module type that is to be added
• the shelf, which is to hold this module
• the slot, which this module is to be inserted in.
Step 3 Locate the shelf within the node where the module should be inserted into.
Step 5 Locate where the optical module is to be inserted in the shelf.
Step 6 Check the operating status of the equipment and the present hazard level. If
hazard level of any network element. Do not proceed unless you are trained in
laser safety.
Step 7 Remove the corresponding dummy module to make space for inserting the
relevant module. Proceed as described in “Removing a Dummy Module” on
p. 775.
the connectors on the backplane could result in damage to the equipment.
Step 8 Take the optical module out of the shipping box. Remove it from the static-
protective package and immediately place it onto a grounded surface or an
antistatic mat to avoid ESD damage to the module.
Step 9 Check and prepare the module as follows:
a) Make sure that the module is the correct one you want to add (type,
specifications). To quickly obtain the required information, refer to the
faceplate markings and the labels on the board cover.
b) Inspect the module visually for any damage and impurities. If necessary,
use canned, dry, oil-free compressed air to blow off any possible dust
particles.
• Carefully check the plug-in board connector of the optical module for dirt,
any deformation in the shape of the pin holes, and damage on the
outside.
• Check the contact strip or EMI shielding gasket on the faceplate edges of
the module for damage.
If the optical module is dropped on a hard surface, a contact strip or EMI
shielding gasket is loose, torn, or the module is otherwise defective, do not
install it. Return the module to ADVA Optical Networking for examination
and repair.
Step 10 Check inside the shelf that
• no foreign conductive bodies are present between pins on the backplane
connectors
• no pins on the backplane connectors are bent or broken.
If a backplane connector of the shelf is damaged in any way, do not install
the optical module.
Risk of short circuit.

If a backplane connector of a shelf has bent or broken off pins, do
not slide in the optical module into that shelf slot.
If the plug-in board connector of the optical module is damaged, do
WARNING not install this module.
Damaged connectors could cause a short circuit or malfunction.

Make sure that the EMC contact strips are not damaged before inserting the
module. Otherwise EMC compliance cannot be achieved.
Step 11 Insert the desired module into the empty slot as follows:
a) When inserting an optical module into an SH7HU, SH9HU, or SHX9HU
shelf, hold the module by both screws as shown in Figure 45 on p. 664 or
by the faceplate.
b) When inserting an optical module into an SH1HU shelf, hold the module by
both screws as shown in Figure 46 on p. 664 or by the faceplate.
c) Insert new SCUs without its shelf communication plugs.
Figure 45: Inserting a Channel Module into an SH7HU, SH9HU, or

SHX9HU Shelf Slot
Figure 46: Inserting a Channel Module into an SH1HU Shelf Slot
d) Align the upper and lower edges of the module with the upper and lower
The optical module has to be inserted vertically into an SH7HU,SH9HU,

or SHX9HU shelf and horizontally into an SH1HU shelf.

Insert the optical module into the slot very carefully. Otherwise the components of
the PCB assembly can be damaged.
e) Using moderate force, push gently until the module connectors mate

immediately. Inspect the module and the electrical connectors. If the module and
the connectors are not damaged, repeat Step 10.
Step 12 Ensure that the module is properly and completely inserted into the slot, by
confirming that:
• its faceplate is flush with the faceplates of the adjacent modules and the
shelf panels, and
• it receives power. If power is applied to the shelf, the Power LED of the
module (P) turns green as soon as the module is in contact with the
backplane.
If a 10WXC-PCN-10G module is not completely seated in an SHX9HU

shelf, bit errors may occur even if the equipment is alarm free.
Note
Insertion of an optical module is automatically detected by the

management software. Each time an optical module is inserted into a
shelf slot, the internal network management system receives a trap
Note message.
Step 13 Check the module LED indicators (P, Mod, O/E, Err) to ensure that they are
operating correctly. Refer to the module LED indicator description in this
document.
Note that the module LEDs indicate reliable information only 5 to 10

seconds after adding! After power up, wait at least 5 minutes before
observing the LEDs! The LED colors can change within this time-span!
Note
If the module does not respond, remove it from the slot. Reinsert the dummy
module into the empty slot as described in “Inserting a Dummy Module” on
p. 773.
Step 14 After inserting an SCU, compare the displayed shelf number with the value
noted in Step 2 of “Removing an Optical Module” on p. 656.
a) If the shelf numbers match, insert the shelf communication plugs.
b) If the shelf numbers differ, remove the SCU from this shelf and update its
firmware. Then re-insert it in this shelf by repeating Step 11 through Step
14.
The SCU firmware may be updated by installing it any shelf with ID 1

through 20.
Note
Step 15 When the inserted module operates properly, secure it tightly in the slot as
follows:
Step 16 For channel modules with pluggable interfaces, insert the pluggable
transceiver(s) into the module cage(s) as specified in the installation plan.
Follow the adding procedure described in “Replacing Pluggable Transceivers”
on p. 677 or Replacing Pluggable Transceivers in a Control Plane-based
network.
If any CFP cages in a 100G transponder/muxponder remain unequipped,

insert the appropriate dust plugs into the empty interface cages as soon
as possible. This ensures proper air flow within the shelf.
Note
Step 17 If you just replaced the spare module in a client channel card protection
configuration, verify it is correctly provisioned by the NCU as follows:
a) The module is displayed in your management system (for example, NED).
b) Verify that firmware package mismatch (FWP-Mismatch) alarms are not
raised against this module.
If any firmware package mismatch alarms are raised against this

module, update its firmware as described in “Updating a Module” on
p. 631 and restart it before proceeding to the next step.
Note
Step 18 Connect the module optical ports as specified in the installation plan.
Step 19 Repeat this procedure for each optical module to be added to a shelf.
cable aside.
Step 22 After replacing an SCU module, set SCU Connections to "Ring", if
this setting was used prior to the module replacement.
Step 23 Return any defective module to ADVA Optical Networking, as indicated in the
If you experience any problems that result in a deviation from this procedure,
contact ADVA Optical Networking Technical Services.
If traffic remains down following a VSM replacement, this may indicate a

rare situation in which the VSM pair has unsynchronized switch
positions. Check the active and standby lines indicated on the VSM
network ports. If the lines reported active are not facing the same
Note network path, perform a manual switch on the exchanged VSM to
recover traffic.
Replacing an Encryption Module

This section describes how to remove and install encryption modules. It contains these
subsections:
“Removing an Encryption Module” on p. 668
“Installing an Encryption Module” on p. 671
The 10TCE-PCN-16GU+AES100G-BSI module and the associated

NCU-II module contain sensitive information and, therefore have been
classified as VS-NFD (RESTRICTED) devices.
Note
Only Service Personnel who is security-cleared may replace the 10TCE-

PCN-16GU+AES100G-BSI module.
CAUTION
Removing an Encryption Module

This section describes how to remove encryption modules from a shelf. For specific
information about each encryption module type, refer to the Hardware Description.

CAUTION
Only Service Personnel who is security-cleared may remove the 10TCE-

PCN-16GU+AES100G-BSI module from the shelf.
CAUTION
Removal of encryption modules does not affect the operation of the other modules
installed in the shelf. Removing an encryption module permanently involves deleting it
from the database by using the management software.
Required Equipment
• Appropriate dummy module to fill the empty slot
• Original shipping box including the static-protective package for storing the removed
module

• Labeling materials, if necessary
Removal Procedure
Follow these steps to remove an encryption module from a shelf.
To prevent ESD damage to the equipment, exercise normal static

precautions for removing encryption modules.
It is assumed that you are familiar with handling encryption modules, as well as fiber-
optic cables, and are aware of the precautions that should be taken to avoid equipment
damage. A summary of how to handle modules and fiber-optic cables is covered in
“Handling Equipment” on p. 47. Pay attention to the safety notices and additional
information provided below.
Step 1 Refer to the installation plan for details about:

• the module type that is to be removed.
• the shelf and corresponding slot from where the module is to be removed.
the shelf, and next, secure the grounding wire to your wrist.
Step 3 Find the shelf where the module is installed.
Step 4 If the front cover is mounted, remove the front cover from the shelf, as
described in “Removing an SH7HU, SH9HU, or SHX9HU Front Cover” on
p. 768.
Step 5 Determine the physical location of the encryption module within the shelf.
hazard level of the NE. Do not proceed unless you are trained in laser safety.
Step 7 Identify the optical fiber pairs connected to the module ports. For easy
identification, attach labels to the fibers.
Laser Radiation.
Invisible laser radiation may be emitted from a fiber-optic transmitter if
aperture interlocks are defeated. Never look directly at the optical
connector output beams when disconnecting the optical cables, as this
CAUTION
can cause permanent eye damage.
Step 8 Remove all optical cables from the module and from other equipment
connected to this module, making sure not to damage the optical cables and
connectors. To remove an individual optical cable, proceed as follows:
a) Detach the connector on one end of an optical fiber and cover it with an
appropriate protective cap.
b) Detach the connector on the other end of this optical fiber and cover it with
an appropriate protective cap.
c) Lay the optical cable aside.
d) Insert the appropriate blind plugs into the relevant receptacles.
e) Repeat these tasks for removing each optical cable.
Step 9 After taking off all relevant optical cables, remove the encryption module:
a) If applicable, remove the pluggable transceivers from the module cages,
as described in “Removing an SFP or XFP Transceiver” on p. 679.
b) Using your fingers or a Torx screwdriver TX10, turn the two knurled
Hot Surface!
Some channel module components such as heat sinks can become very
hot during operation. Touching a very hot component may cause skin
burns. Allow the module to cool before removing it from the shelf slot.
CAUTION
Place only cooled modules into the static-protective package.
c) Firmly pull on the screws until the module is free from the shelf, then
screws.

Slide the encryption module out of the slot very carefully to avoid damaging the PCB
assembly components.
backplane connectors may damage the equipment.
Removal of an encryption module is automatically detected by the

management software.
Note
Passwords stored on an encryption module are automatically deleted

from the database after the module is removed from the shelf. Therefore,
the module can be stored or transported without any security
Note implications.
d) Place the module on a grounded surface or an antistatic mat and

immediately place it in the original static-protective package to avoid ESD
damage.
e) Place the static-protective package in the original shipping box.
Do not leave the vacated shelf slot empty! Fill the empty slot with an appropriate
dummy module. An empty shelf slot results in an inhomogeneous air stream and
contaminates the installed optical modules and components inside the shelf with
dust and debris.
Step 10 Insert the dummy module, as described in “Inserting a Dummy Module” on

p. 773.
Step 11 Repeat this procedure for each encryption module to be removed from a shelf.
Step 12 If available, mount the front cover to the shelf, as described in “Mounting an
Step 13 Detach the wrist strap from your wrist, and then disconnect the grounding
cable from the ESD grounding point on the shelf (if available) or the rack.
Step 14 Store the optical cables for future use.
Return any defective module to ADVA Optical Networking for repair, as
described in the Installation and Commissioning Manual.
If you encounter problems that result in a deviation from the procedure
Installing an Encryption Module

This section describes the procedure for adding encryption modules. For specific
information about each encryption module type, refer to the Hardware Description.
Before connecting fiber-optic cables, install the encryption module and

pluggable transceivers to the FSP 3000R7 system, as described in this
section. After physical installation, the module boots.
Please wait about one minute until the boot, configuration, and
initialization time for protection completes. Then fiber-optic cables can
Note
be connected to the installed encryption module and pluggable
transceivers.

CAUTION
Only Service Personnel who is security-cleared may install the 10TCE-

PCN-16GU+AES100G-BSI module to the shelf.
CAUTION
Encryption modules are plug-in modules that are compatible with any FSP 3000R7 shelf.
Adding an encryption module does not affect the operation of currently installed modules
in the shelf. There are no fixed slot positions for specific encryption modules. Encryption
modules can be inserted into a shelf slot without the use of any tools.
Encryption modules are provisioned with two independent sets of configuration
parameters:
• Optical parameters are controlled by the database on the NCU and are provisioned
automatically when the replacement module is inserted. Use management software
to confirm these settings. If the settings differ from your network requirements,
reconfigure the module, as addressed in “Provisioning a Network Element” in the
• Security parameters must be provisioned on the replacement module. This procedure

contains a step to set the Crypto-Officer and Authentication passwords. The
remaining security parameters such as session key lifetime may be provisioned
afterwords, as outlined in "Configuring Encryption Modules" in the Provisioning and
Operations Manual.
The module inventory data stored in the EEPROM is accessible from the management
system. When auto-provisioning is enabled, the encryption module is entered into the NE
database with default parameters. See Provisioning and Operations Manual, section
"Modifying Provisioned Entities," for information about assigning equipment to the NE
database and configuring equipment.
Adding an encryption module at a later time can change the optical budget. Use the FSP
Network Planner to calculate the changes or contact ADVA Optical Networking
Technical Services.
Risk of power supply failure!

Adding modules with relatively high power consumption to an already operating
node can result in power failure due to overload.
Ensure that the total power consumption of a fully equipped shelf does not exceed
the specified value. Calculate the total power consumption or contact ADVA Optical
Networking Technical Services before inserting the module!
Requirements
• The initial Crypto-Officer password of the replacement module
• Encryption module to be added, packaged in the shipping box. This module should be
equipped with the firmware package associated with the NE software.
• Suitable grounded surface or an antistatic mat for placing the encryption module
• Original shipping box for storing the removed dummy module.
Adding Procedure
To avoid ESD damage to the equipment, exercise normal static

precautions for adding encryption modules.
It is assumed that you are familiar with handling encryption modules as well as fiber-optic
cables, and are aware of the precautions that should be taken to avoid damaging the
“Handling Equipment” on p. 47. Pay attention to the safety notices and additional
information provided below.
Step 1 Refer to the installation plan for details about:

• the module type that is to be added.
• the shelf and corresponding slot that this module will be installed in.
the shelf, and then secure the grounding wire to your wrist.
Step 3 Locate the shelf within the NE where the module should be inserted.
Step 4 If the front cover is mounted, remove the front cover, as described in
“Removing an SH7HU, SH9HU, or SHX9HU Front Cover” on p. 768.
Step 5 Locate the slot where the encryption module is to be installed.
hazard level of the NE. Do not proceed unless you are trained in laser safety.
Step 7 Remove the corresponding dummy module from the slot, as described in
“Removing a Dummy Module” on p. 775.
backplane connectors can damage the equipment.
Step 8 Remove the encryption module from the shipping box. Remove the static-
protective package, and then immediately place the module on a grounded
surface or an antistatic mat, to avoid ESD damage.
Step 9 Check the module as follows:
a) The module is protected with seals and rivets. Ensure that nothing has
been damaged and that the module was not opened and/or modified.
b) Ensure that the module is the correct one you want to install (type,
specifications). Refer to the faceplate markings and the labels on the
board cover.
c) Inspect the module for any damage and impurities. If necessary, use
canned, dry, oil-free compressed air to blow off any dust particles.
• Carefully check the plug-in board connector of the optical module for dirt,
any deformation in the shape of the pin holes, or external damage.
• Check the contact strip or EMI shielding gasket on the faceplate edges of
the module for damage.
Do NOT install modules:
• That have broken seals or rivets. This could be a sign of tampering or
damage.
• That have been dropped on a hard surface.
• That have loose or torn contact strips or EMI shielding
Return these modules to ADVA Optical Networking for examination and repair.
Step 10 Check inside the shelf to ensure:
connectors
Do NOT install the module if a backplane connector of the shelf is damaged.

If a backplane connector of a shelf has bent or broken-off pins, do
not slide the encryption module into that shelf slot.
If the plug-in board connector of the encryption module is
WARNING damaged, do not install this module.

Before inserting the module, ensure that the EMC contact strips are not damaged.
Otherwise, EMC compliance cannot be achieved.
Step 11 Insert the desired module into the empty slot:

a) When inserting the module into an SH7HU, SH9HU, or SHX9HU shelf,
hold the module vertically by both screws or by the faceplate.
b) When inserting the module into an SH1HU shelf, hold the module
horizontally by both screws or by the faceplate.
c) Align the upper and lower edges of the module with the upper and lower

Insert the encryption module into the slot very carefully, to avoid damaging the PCB
assembly components.
d) Using moderate force, push gently until the module connectors mate

immediately. Inspect the module and the electrical connectors. If the module and
the connectors are not damaged, repeat Step 10.
Step 12 Ensure that the module is properly and completely inserted into the slot, by
confirming that:
• its faceplate is flush with the faceplates of the adjacent modules and the
shelf panels, and
• it receives power. If power is applied to the shelf, the Power LED of the
module (P) turns green as soon as the module establishes contact with the
backplane.
Insertion of an encryption module is automatically detected by the

Note
Step 13 Check the module LED indicators (P, Mod, O/E, Err) to ensure that they are
operating correctly. Refer to the module LED indicator description in this
document.
The module LEDs indicate reliable information only five to ten seconds
after adding! After power up, wait at least five minutes before checking
the LEDs because the LED colors can change within this time-span.
Note
If the module does not respond, remove it from the slot. Reinsert the dummy
module into the empty slot as described in “Inserting a Dummy Module” on
p. 773.
Step 14 When the inserted module operates properly, secure it tightly in the slot:
Step 15 For modules with pluggable interfaces, insert the pluggable transceiver(s) into
the module cage(s) as specified in the installation plan. Follow the adding
procedure described in “Replacing Pluggable Transceivers” on p. 677 or
Replacing Pluggable Transceivers in a Control Plane-based network.
If any CFP cages in a 100G transponder/muxponder remain unequipped,

insert the appropriate dust plugs into the empty interface cages
immediately. This ensures proper air flow within the shelf.
Note
Step 16 If the module is not equipped with the encryption firmware package associated
with the NE software, update it as outlined in “Updating Modules with
Encryption” on p. 628.
Step 17 Provision these security parameters on the module:
• Crypto-Officer password, as outlined in "Changing the Crypto-Officer
Password" in the Provisioning and Operations Manual.
• Authentication password, as outlined in "Changing the Authentication
Password" in the Provisioning and Operations Manual.
Step 18 If you just replaced the spare module in a client channel card protection
configuration, verify that it is displayed in your management system.
Step 19 Connect the module optical ports as specified in the installation plan.
Step 20 Repeat this procedure for each encryption module to be added to a shelf.
Step 21 If available, mount the front cover to the shelf, as described in “Mounting an
Step 22 Detach the wrist strap from your wrist, and disconnect the grounding cable
from the ESD grounding point on the shelf (if available) or the rack.
Return any defective module to ADVA Optical Networking, as indicated in the
If you experience any problems that result in a deviation from this procedure,
contact ADVA Optical Networking Technical Services.
Replacing a Raman Amplifier
Replacing a Raman Amplifier

The steps for removing a faulty Raman from its shelf and installing a new Raman are the
same as for other optical modules. Additionally, the Amplified Spontaneous Emission
(ASE) table must be built for the newly replaced Raman before placing it in service.
Execute the following steps to replace a Raman amplifier.
Step 1 Remove the faulty Raman amplifier, as detailed in “Removing an Optical

Module” on p. 656.
Step 2 Install the replacement Raman amplifier, as detailed in “Installing an Optical
Module” on p. 660.
Step 3 Proceed to the corresponding Raman configuration subsection under
"Configuring Optical Amplifiers" in the Provisioning and Operations Manual.
Perform the following tasks for the newly replaced Raman:
• Check Equipment
• Connect OSC and Establish a Connection
• Verify the Fiber Span is Dark
• Build the ASE Table
• Final Amplifier Check
Replacing Pluggable Transceivers

This section describes how to remove and install pluggable transceivers. Unless
otherwise specified below, the term pluggable transceivers always refers to SFP
transceivers, SFP+ transceivers, XFP transceivers and CFP transceivers.
These subsections are covered:
“General Information” on p. 677
“Safety Guidelines” on p. 678
“Removing an SFP or XFP Transceiver” on p. 679
“Installing an SFP or XFP Transceiver” on p. 682
“Removing a CFP Transceiver” on p. 686
“Installing a CFP Transceiver” on p. 689
To exchange pluggable transceivers in a Control Plane-based network,

please refer to “Replacing Pluggable Transceivers in a Control Plane-
based network” on p. 694.
Note
General Information
Pluggable transceivers are hot-pluggable and hot-swapple modules.They can easily be
inserted into or removed from the appropriate channel module interface cages without the
use of any tools, simply by using finger-pressure. It is not required to deactivate the
channel module when you remove or install a pluggable transceiver. Depending on the
transceiver manufacturer, your pluggable transceivers can use different types of latching
mechanisms to secure and detach the transceiver into or from the channel module
interface cage. Most of the pluggable transceivers - deployed by ADVA Optical
Networking - use a bale-clasp latch. CFP transceivers use two captive mounting screws
(knurled screws) on their faceplates to secure the device in the interface cage.
A transceiver check is run as soon as a pluggable transceiver is inserted into a channel
module interface cage, provided the channel module has been provisioned previously.
Only pluggable transceiver modules approved by ADVA Optical Networking pass this
check and can be used. Third-party transceiver modules are not supported by the FSP
3000R7 system. All pluggable transceiver modules approved by ADVA Optical
Networking are equipped with a Class 1 Laser device, which emits invisible radiation.
Pluggable transceivers are static-sensitive and dust-sensitive. Protect the transceiver
modules from static discharge and physical shock. Protect the optical ports of the
pluggable transceivers by inserting clean dust covers into them after the fiber optic cables
are removed. Be sure to clean the fiber-optic connectors before you reconnect them into
the optical ports of the replacement transceiver module. Do not remove and insert a
pluggable transceiver more often than necessary. Frequent installation and removal of a
pluggable transceiver can shorten its lifespan.
After removing a pluggable transceiver from the interface cage, wait for at least one
second before you reinsert it or insert another one.
For specific information about each pluggable transceiver, refer to the Hardware
Description and the Pluggable Transceiver Module Specification.
Where necessary, return a defective or damaged pluggable transceiver module to ADVA

Optical Networking for replacement. For details on returning, refer to the Installation and
Safety Guidelines
Only Service Personnel are allowed to remove and install pluggable

transceivers.
CAUTION
Each pluggable transceiver is a Class 1 laser product!

CAUTION
Risk of invisible laser radiation.

Invisible laser radiation is present when the system is open and
interlocks bypassed.
• Keep the optical port of the transceiver and the fiber-optic connecors
covered when not in use.
• Do not look into an unterminated optical fiber connector or an open
aperture of the transceiver port.
CAUTION
• Do not view directly with optical instruments.
• Make sure that the relevant laser sources are disabled, before you
inspect, clean and connect fiber optic connectors.
Looking directly at a laser beam can cause permanent eye damage.
Use of controls, adjustments, or performing procedures other than those

specified may result in hazardous radiation exposure.
CAUTION
Use only pluggable transceivers that are approved by ADVA Optical

Networking.
Use of pluggable transceivers that are not approved by ADVA Optical
Networking could result in loss of safety approval for the FSP 3000R7 or
CAUTION
system problems.
Pluggable electrical transceivers must not be directly connected to

metallic tip and ring outside-plant conductors. They have to be
used only for inside-plant conductors.
WARNING
Risk of electrostatic discharge.

To prevent damage from electrostatic discharge (ESD),
• take standard anti-static precautions when handling pluggable
transceiver modules or coming in contact with them.
• wear an ESD wrist strap or use a similar individual grounding device
when installing or removing pluggable transceivers.
The electrical connectors on the rear side of CFPs are very sensitive to
mechanical stress or ESD. Do not touch these connectors.
Be sure to disconnect all optical cables before removing or installing a pluggable

transceiver module. By ignoring this, you could damage the optical fibers, the optical
connectors, or the optical port of the transceiver module.
Dispose of obsolete pluggable transceivers according to all national laws

and regulations.
It is assumed that you are familiar with pluggable transceivers, and are aware of the
precautions that should be taken to avoid damage to the equipment. A summary of how to
handle pluggable transceivers and optical fibers is provided in “Preparation for
Troubleshooting” on p. 29 of this manual.
Removing an SFP or XFP Transceiver

See the above Safety Guidelines before removing any SFP transceiver, SFP+
transceiver, or XFP transceiver module. The following description is applicable to all
SFP, SFP+, and XFP transceiver modules provided by ADVA Optical Networking. In this
procedure, these modules are referred to as pluggable transceivers.
Equipment Required
Before starting the procedure, ensure the following equipment is available:
• Suitable grounded surface or an antistatic mat for placing the pluggable transceiver
• Appropriate dust plug to cover the empty channel module interface cage (if you want
to install a replacement transceiver module later or not at all)
• Appropriate blind plugs for inserting into the unterminated optical receptacles of the
optical module which is directly connected to this transceiver (if you want to install an
replacement transceiver module later or not at all)
• Appropriate protective caps for covering the fiber-optic connectors
• Original shipping box, including the static-protective package for saving the removed
pluggable transceiver
Removal Procedure
Several tasks must be completed. Some tasks are detailed in sub-tasks. Follow these
steps to remove a pluggable transceiver from a channel module interface cage.

• the transceiver type that is to be removed
• the channel module which holds this transceiver
• the cage (client or network port) from which this transceiver is to be
removed.
Step 2 Check the operating status of the equipment and the present hazard level.
Please keep in mind that the laser hazard level of the network element will be
influenced when any module is operating in "Forced On" mode. Do not proceed
unless you are familiar with the laser safety and you are protected accordingly.
Step 3 Attach a wrist strap to your bare wrist and fasten the grounding cable onto the
ESD grounding point on the shelf (if available) or to a bare metal surface onto
the rack.
Step 4 If mounted, remove the front cover from the shelf, as described in “Removing
Step 5 Find the physical location of the channel module which is being held the
Step 6 Identify the interface cage (port) on the module from which the pluggable
transceiver is to be removed.
If you are disconnecting the cables from the optical port of the pluggable transceiver
in the next step, do not pull on the cables in an attempt to extract the transceiver
module. It is locked in the interface cage. Pulling on the optical cables will damage
the optical connectors.
Always disconnect the optical cables before removing the pluggable transceiver
from the interface cage. Grip the housing of the fiber optic connector to plug or
unplug an optical cable. Do not pull on the fiber.
Step 7 Disconnect the optical fiber pair from the transceiver ports. Proceed as
follows:
If the connector plug does not remove easily in b and d, ensure that the
latch on the connector has been released before pulling on the
transceiver.
Note When you disconnect an optical cable from the transceiver port, the
channel module port status LED turns yellow.
a) For reattachment of the optical cables, note which connector plug is

transmit (TX) and which is receive (RX).
b) Press the release latch on the connector plug of the reception fiber, grasp
the connector housing and gently pull it from the RX transceiver port.
c) Cover the connector plug with an appropriate protective cap.

d) Press the release latch on the connector plug of the transmission fiber,
grasp the connector, and gently pull it from the TX transceiver port.
e) Cover the connector plug with an appropriate protective cap.
f) Put the optical fiber pair aside for later reattachment
If you want to install an replacement transceiver module later or not at all,

remove the fiber optic connectors on the other end of this fiber pair from
the receptacle of the connected optical module as well. Cover the fiber
optic connectors with the appropriate protective caps. Insert the
Note appropriate blind plugs into the unterminated receptacle of the
disconnected optical module.
If you have difficulty removing a bale clasp pluggable transceiver in the

next step, do not use extreme force or a tool to pull out it. Ensure that the
latch is in the correct position before continuing.
Note
Step 8 After taking off the optical cables, remove the pluggable transceiver from the
interface cage as follows:
a) If the transceiver module has a bale-clasp latch, unlock it by pulling the
bale clasp gently downwards as shown in Figure 47.
If you cannot grasp bale clasp with your index finger, use a small flat-blade
screwdriver or another long narrow instrument to unlock the bale-clasp
latch.
Figure 47: Example of an XFP Transceiver Prepared for Extracting
Note that your pluggable transceiver locking/unlocking mechanism may be

different than the model shown in Figure 47.
b) Grip the bale clasp and pull gently to draw the transceiver fully out of the
interface cage.
If the pluggable transceiver does not slide easily from the interface cage,
stop immediately. Try one of the following:
• Check whether the transceiver is really unlocked. If so, use a gentle
side-to-side rocking motion while firmly pulling the pluggable
transceiver from the cage. Be careful not to damage the interface cage
during this process.
• Move the bale-clasp toward the interface cage until it touches the
transceiver optical port again. Next, pull the bale clasp gently
downwards once more as shown in Figure 47 on p. 681, and then
grasp the bale clasp to extract the transceiver with a slight force.
When you remove the pluggable transceiver from the interface cage
the channel module port status LED turns red.
Removal of the pluggable transceiver module is automatically detected
by the management software. Each time a pluggable transceiver is
Note removed from a cage, the internal network management system
receives a trap message.
Step 9 Plug the appropriate dust cover(s) into the transceiver port.
Step 10 Place the removed pluggable transceiver in an antistatic bag, an ESD safe
box, or other protective environment.
Step 11 Insert the appropriate dust plug into the empty interface cage as shown in
Figure 48, if the replacement transceiver is not being installed.
Figure 48: Example of an XFP Dust Plug Inserted into an Empty XFP
Cage
ESD grounding point on the shelf (if available) or the rack, and lay the
grounding cable aside.
Step 13 Store the box with the removed pluggable transceiver(s) for future use in a safe
place.
Should you have any difficulty performing this procedure, contact ADVA
Optical Networking Technical Services.
Step 14 Repeat this procedure for each SFP, SFP+, or XFP transceiver to be removed.
Installing an SFP or XFP Transceiver

See the above Safety Guidelines before installing any SFP transceiver, SFP+ transceiver
or XFP transceiver module. The following description is applicable to all SFP, SFP+, and
XFP transceiver modules provided by ADVA Optical Networking. In this procedure, these
modules are referred to as pluggable transceivers.
Equipment Required
• Pluggable transceiver module to be inserted
• Suitable grounded surface or an antistatic mat for placing the pluggable transceiver
• Optical power meter (if necessary)
• Fiber optic cleaning kit including hand-held fiber scope and/or video scope
• Tagging materials (for labeling the optical fibers)
Installation Procedure
steps to remove a pluggable transceiver from a channel module interface cage.

• the transceiver type that is to be installed
• the channel module which is to hold this transceiver
• the cage where this transceiver is to be inserted in (if the channel module
has two or more interface cages).
the rack.
Step 5 Find the physical location of the channel module that is to hold the pluggable
transceiver.
Step 6 Remove the pluggable transceiver from its static-protective packaging and
immediately place it on a grounded surface or an antistatic mat.
Do not remove the optical port dust cover until directed to do so later in
this procedure.
Note
Step 7 Check and prepare the transceiver module as follows:

a) Verify that the pluggable transceiver is the correct one for your network
configuration (type, specifications). To quickly obtain the adequate
information, refer to the ADVA Optical Networking label on the top of the
transceiver module.
b) Inspect the transceiver visually for damage and impurities. If necessary,
use canned, dry, oil-free compressed air to blow off any impurities. If the
transceiver is damaged, do not install it.
c) Make sure that the optical port of the transceiver module is equipped with a
dust cover. If not, install one.
Step 8 Identify the interface cage (port) on the channel module where the replacement
transceiver will be installed.
Step 9 If installed, remove the dust plug from the corresponding interface cage of the
channel module and store it in a resealable container for future use. Figure 49
shows an example.
Figure 49: Example of a Dust Plug Covering an XFP Cage
Pluggable transceivers are keyed to prevent incorrect insertion.

Make sure that the pluggable transceiver module has the correct
orientation, either the bale clasp is oriented to the left or to the right
(depends on the channel module type).
Ensure that the bale clasp is in the lock-in position before you insert the
Note transceiver into the interface cage.
If the pluggable transceiver resists pressure, the orientation may be
wrong. Do not force the module. Pull it out of the interface cage.
Step 10 Insert the desired pluggable transceiver into the empty cage as follows:
a) If the pluggable transceiver has a bale clasp, grip the transceiver on the
narrow sides between your thumb and forefinger.
b) Remove the dust cover from the optical port.
c) Move the bale clasp toward the optical port until it touches the port (lock-in
position). Do that before inserting the transceiver.
d) Reinstall the dust cover.
e) Hold the pluggable transceiver between your thumb and forefinger and
orient it, so that the optical port is toward you, and the bale clasp is on the
right. See Figure 50 on p. 685.
For some channel modules, such as the 10TCC-PCTN-4GU(S)+10G,

align the pluggable transceiver so that the bale clasp is facing to the left.
Note
f) Align the pluggable transceiver with the cage opening, as shown in Figure
50 on p. 685, and gently insert it into the empty cage.
Figure 50: Example of an XFP Transceiver Prepared for Inserting
g) Apply light pressure to the pluggable transceiver until it snaps into place.
A click indicates that the transceiver is completely inserted and securely
seated in the cage.
If there is resistance, remove the transceiver, realign it so that the bale
clasp faces the other direction, and insert the transceiver again.
Insertion of a pluggable transceiver is automatically detected by the

management software. Each time a transceiver is inserted into a
interface cage of a channel module or network module, the internal
Note network management system receives a trap message.
Step 11 Check the corresponding channel module port LED.

If this LED is off, the inserted pluggable transceiver needs still to be assigned
using the management software (only when installed the first time).
If this LED is yellow, it indicates that the port is equipped again and the
inserted transceiver module is already assigned, but there is no traffic (only
when replacing a transceiver).
If this LED is flashing red, the inserted pluggable transceiver is the wrong type,
or it is not approved by ADVA Optical Networking, thus not accepted by the
system.
For more information about the channel module port LEDs, refer to this manual.
If the pluggable transceiver is not accepted by the system or does not respond,
remove it again from the cage. Install a new one of the correct type or reinsert
the dust plug into the empty cage.
Step 12 Connect the corresponding optical fiber pair to the transceiver ports. Proceed
as follows:
a) Identify the optical fiber pair to be connected. For easy identification, use
the tags on each fiber.
b) Remove the protective cap from the connector on the reception fiber and
store it in a clean, resealable container.
c) Inspect and clean the fiber optic connector end face before you make the
connection.
For complete information on inspecting and cleaning fiber-optic

connectors, see “Preparation for Troubleshooting” on p. 29 in this manual.
d) Remove the dust plug from the pluggable transceiver optical port and store
it in a clean resealable container.
e) Plug the cleaned connector of the reception fiber into the RX connector.
f) Remove the tag from the reception fiber.
g) Repeat b through f for connecting the transmission fiber.
Step 13 Verify that the corresponding channel module port LED is green. If so, the
replacement transceiver and the target device have an established link. The
replacement transceiver is working properly.
Step 15 Detach the wrist strap from your wrist, disconnect the earthing cable from the
ESD grounding point on the shelf (if available) or the rack and lay the earthing
cable aside.
Step 16 Store the resealable containers with the dust plugs, dust covers, and
protective caps in a safe place for future use.
Step 17 Repeat this procedure for each SFP, SFP+, or XFP transceiver to be installed.
Removing a CFP Transceiver

See the above Safety Guidelines before removing any CFP transceiver module.
Equipment Required
• Suitable grounded surface or an antistatic mat for placing the CFP transceiver
• Appropriate dust plug to protect the empty channel module interface cage (if you want
to install a replacement transceiver module later or not at all). This is especially
important for 100G transponders/muxponders.
• Appropriate blind plugs for inserting into the unterminated optical receptacles of the
optical module which is directly connected to this transceiver (if you want to install an
replacement transceiver module later or not at all)
• Appropriate protective caps for covering the fiber-optic connectors
• Original shipping box, including the static-protective package or an equivalent
container for saving the removed CFP transceiver
• Tagging materials, if necessary (for labeling the optical fibers)
Removal Procedure
steps to remove a CFP transceiver from the interface cage of a CFP-based channel
module.

• the CFP transceiver type that is to be removed
• the channel module which holds this transceiver
• the cage from which this transceiver is to be removed (if the channel
module has two interface cages)
affected when any module is operating in "Forced On" mode. Do not proceed
the rack.
Step 5 Find the physical location of the channel module which holding the CFP
transceiver to be removed.
Step 6 If appIicable, identify the interface cage (port) on the channel module from
which the CFP transceiver is to be removed.
If you are disconnecting the optical cables from the port of the pluggable transceiver
in the next step, do not pull on the cables in an attempt to extract the transceiver
module. It is locked in the interface cage. Pulling on the optical cables will damage
the optical connectors.
Always disconnect the optical cables before removing the pluggable transceiver
from the interface cage. Grip the housing of the fiber optic connector to plug or
unplug the optical cable. Do not pull on the fiber.
Step 7 Disconnect the optical fiber pair from the CFP transceiver ports. Proceed as
follows:
If the connector plug does not remove easily in b and d, ensure that the
latch on the connector has been released before pulling on the
transceiver.
When you disconnect an optical cable from the CFP transceiver RX port
Note the channel module port status LED turns yellow. For more information
about the LED indicators, refer to “Core Type Channel Modules” on p. 95.
a) For reattachment of the optical cables, note which connector plug is

transmit (TX) and which is receive (RX).
b) Press the release latch on the connector plug of the reception fiber, grasp
the connector, and gently pull it from the RX transceiver port.
c) Cover the connector plug with an appropriate protective cap.
d) Press the release latch on the connector plug of the transmission fiber,
grasp the connector, and gently pull it from the TX transceiver port.
e) Cover the connector plug with an appropriate protective cap.
f) Put the optical fiber pair aside for later reattachment.
If you want to install an replacement CFP transceiver module later or not

at all, remove the fiber optic connectors on the other end of this fiber pair
from the receptacle of the connected optical module as well. Cover the
fiber optic connectors with the appropriate protective caps. Insert the
Note appropriate blind plugs into the unterminated receptacle of the
disconnected optical module.
Step 8 Plug the dust cover(s) into the CFP transceiver ports.
Step 9 After taking off the optical fiber pair, remove the CFP transceiver from the
interface cage as follows:
a) Using your thumb and forefinger, turn the two knurled screws in a counter-
clockwise direction until they are free from the threaded holes.
b) Firmly pull on the knurled screws until the CFP transceiver module is free
from the host connector, and carefully slide it straight out of the cage,
while holding the module by both screws as shown in Figure 51.
Figure 51: Example of removing a CFP transceiver from a channel

module interface cage
When you remove the CFP transceiver from the interface cage, the
corresponding channel module port status LED turns red.
Removal of the CFP transceiver module is automatically detected by the
management software. Each time a CFP transceiver is removed from a
Note cage, the internal network management system receives a trap
message.
Step 10 Place the CFP transceiver module in an antistatic bag immediately and place it
back into the original shipping box or equivalent container.
Step 11 Insert the appropriate dust plug into the empty interface cage, as shown in
Figure 52, if a replacement transceiver is not being installed.
Figure 52: Example of a CFP dust plug inserted into an empty CFP
Cage
Upon removing a CFP from a 100G transponder/muxponder, insert the

appropriate dust plug into the empty interface cage as soon as possible.
This ensures proper air flow within the shelf.
Note
ESD grounding point on the shelf (if available) or the rack, and lay the
grounding cable aside.
Step 13 Store the shipping box with the removed CFP transceiver in a safe place for
future use.
Step 14 Repeat this procedure for each CFP transceiver module to be removed.
Installing a CFP Transceiver

See the above Safety Guidelines before installing any CFP transceiver module.
Equipment Required
• CFP transceiver module to be installed
• Suitable grounded surface or an antistatic mat for placing the CFP transceiver
• Optical power meter (if necessary)
• Fiber optic cleaning kit, including hand-held fiber scope and/or video scope
• Tagging materials (for labeling the fibers)
Installation Procedure
steps to install a CFP transceiver in the interface cage of a CFP-based channel module.

• the CFP transceiver type that is to be installed
• the channel module which is to hold this transceiver
• the cage where this transceiver is to be inserted in (if the channel module
has two interface cages)
the rack.
Step 5 Find the physical location of the channel module that is to hold the CFP
transceiver.
Step 6 Take the CFP transceiver module out of the shipping box. Remove the module
from the antistatic bag and immediately put it onto a grounded surface or an
antistatic mat.
Do not remove the optical port dust cover until directed to do so later in
this procedure.
Note
Step 7 Check and prepare the CFP transceiver module as follows:

a) Verify that the CFP transceiver is the correct one for your network
configuration (type, specifications). To quickly obtain the adequate
information, refer to the ADVA Optical Networking label on the board cover
of the transceiver module.
b) Inspect the CFP transceiver visually for damage and impurities. If
necessary, use canned, dry, oil-free compressed air to blow off any
impurities. If the CFP transceiver is damaged, do not install it.

Make sure that the EMI gasket flange is not damaged before inserting the module.
Otherwise EMC compliance cannot be achieved.
c) Make sure that the optical port of the CFP transceiver module is equipped
with a dust cover. If not, install one.
Step 8 Identify the interface cage (port) on the channel module where the replacement
CFP transceiver will be installed.
Step 9 If installed, remove the dust plug from the corresponding interface cage of the
channel module and store it in a resealable container for future use. Figure 53
shows an example.
Figure 53: Example of a CFP Dust Plug Covering a CFP Cage
Step 10 Insert the desired CFP transceiver into the empty cage as follows: NOTE:
CFP transceivers are keyed so they can only be inserted in one orientation.
a) Grasp the CFP transceiver so that the optical port is towards you, and the
label on the board cover as well as the host connector are facing to the
right.
If you install a CFP transceiver into a WCC-PCTN-100GA module, the

label on the board cover as well as the host connector must face to the
left.
Note
Figure 54: Example of Inserting a CFP Transceiver
b) Align the CFP transceiver into the empty interface cage, and carefully
slide it in until the CFP transceiver EMI gasket flange makes contact with
the bezel on the channel module faceplate. See Figure 54.
c) Press firmly on the front of the CFP transceiver with your thumbs or
fingers to fully seat it in the cage.
The CFP transceiver is completely inserted when its faceplate is flush
with the bezel on the channel module faceplate.
d) Gently tighten the two knurled screws on the CFP transceiver to secure it
in the cage.
Insertion of a CFP transceiver is automatically detected by the

management software. Each time a transceiver is inserted into a cage of
a channel module, the internal network management system receives a
Note trap message.
Step 11 Check the corresponding channel module port LED.

If this LED is off, the inserted CFP transceiver needs still to be assigned using
the management software (only when installed the first time).
If this LED is yellow, it indicates that the port is equipped again and the
inserted transceiver module is already assigned, but there is no traffic (only
when replacing a transceiver).
If this LED is off or flashing red, the inserted CFP transceiver is the wrong
type, or it is not approved by ADVA Optical Networking, thus not accepted by
the system.
For more information about the channel module port LEDs, refer to this manual.
If the CFP transceiver is not accepted by the system or does not respond,
remove it again from the cage. Install a new one of the correct type or reinsert
the dust plug into the empty cage.
Step 12 Connect the corresponding optical fiber pair to the CFP transceiver ports.
Proceed as follows:
a) Identify the optical fiber pair to be connected. For easy identification, use
the tags on each fiber.
b) Remove the protective cap from the connector on the reception fiber and
store it in a clean, resealable container.
c) Inspect and clean the fiber-optic connector end face before you make the
connection.
For complete information on inspecting and cleaning fiber-optic
connectors, see “Preparation for Troubleshooting” on p. 29 in this manual.
d) Remove the dust plug from the CFP transceiver optical port and store it in
a clean resealable container.
e) Plug the cleaned connector of the reception fiber to the RX connector.
f) Remove the tag from the reception fiber.
g) Repeat b through f for connecting the transmission fiber.
Step 13 Verify that the corresponding channel module port LED is green. If so, the
replacement transceiver and the target device have an established link. The
replacement transceiver is working properly.
ESD grounding point on the shelf (if available) or the rack, and lay the earthing
cable aside.
Step 16 Store the original shipping box of the CFP transceiver, including the static-
protective package and the resealable containers with the dust plugs, dust
covers, and the protective caps in a safe place for future use.
Step 17 Repeat this procedure for each CFP transceiver to be installed.
Replacing Pluggable Transceivers in a Control Plane-based network
Replacing Pluggable Transceivers in a Control

Plane-based network
This section describes how to remove and install pluggable transceivers in a network that
uses the Control Plane and FSP Network Manager to manage and monitor services.
Unless otherwise specified, the term pluggable transceivers always refers to SFP
transceivers, SFP+ transceivers, XFP transceivers and CFP transceivers.
These subsections are covered:
“Replacing an N Port Pluggable Transceiver with the Same Type” on p. 694
“Replacing an N Port Pluggable Transceiver with a Different Type - Method 1” on p. 695
“Replacing an N Port Pluggable Transceiver with a Different Type - Method 2” on p. 695
“Replacing a C Port Pluggable Transceiver” on p. 696
Replacing an N Port Pluggable Transceiver with the

Same Type
Use the following procedure to replace the N port pluggable transceiver with the same
type.
Requirements
Each service to/from this port is available in the NMS database.
Step 1 Via the FSP Network Manager, disable restoration for each service originating
or terminating at this port.
Step 2 Replace the pluggable transceiver as outlined in “Replacing Pluggable
Transceivers” on p. 677.
Step 3 Via the FSP Network Manager, enable restoration for each service originating
Refer to the FSP Network Manager User Manual for details on disabling
or enabling service restoration.
Note
Replacing an N Port Pluggable Transceiver with a

Different Type - Method 1
The following procedure involves deleting the associated service and its dependencies
before replacing the pluggable transceiver.
Requirements
This procedure is service-affecting since it involves deleting the service.

Note
Step 1 Delete the service using one of the following methods:

• Deactivate the tunnel.
• Delete the service via the Service Manager.
Step 2 Delete the associated Physical Termination Point (PTP) connection.
Step 3 Delete the pluggable transceiver.
Step 5 Add the pluggable transceiver to the management system.
Step 6 Provision the associated PTP connection.
Step 7 Create the service using the same method selected in Step 1 for deleting it:
• Activate the tunnel.
• Create the service via the Service Manager.
Replacing an N Port Pluggable Transceiver with a

Different Type - Method 2
The following procedure involves abandoning the tunnel before replacing the pluggable
transceiver.
Requirements
This procedure may be service-affecting if the associated pluggable

transceiver is not part of a protection group.
Note
Step 1 Abandon the tunnel.

Step 2 Delete the pluggable transceiver's dependencies (Physical Termination Point
connection, Protection, etc).
Step 3 Delete the pluggable transceiver.
Step 5 Add the pluggable transceiver to the management system.
Step 6 Provision the pluggable transceiver's dependencies (Physical Termination
Point connection, Protection, etc).
Step 7 Adopt the tunnel.
Step 8 Set the Protection Goal to None for unprotected tunnels or Required for
protected tunnels.
Replacing a C Port Pluggable Transceiver

Replace a C port pluggable transceiver as follows:
Step 1 Via the FSP Network Manager, disable restoration for each service originating
Step 2 If channel card protection is configured on this module and the pluggable
transceiver is being exchanged for a different type, delete all its dependencies
(e.g. Physical Termination Point connection to/from the client port).
Step 4 If channel card protection is configured on this module and the pluggable
transceiver was replaced with a different type, provision all its dependencies
(e.g. Physical Termination Point connection to/from the client port).
Step 5 Via the FSP Network Manager, enable restoration for each service originating
Replacing Power Supply Units

This section describes how to replace 1HU, 7HU, and 9HU power supply units (PSUs).
The replacement procedures for the different PSU types are described in the following
subsections:
General Information
Replacing a PSU/1HU-R-AC(-200) or PSU/1HU-R-DC-200
Replacing a PSU/7HU-AC, PSU/7HU-AC-HP, or PSU/7HU-AC-800
Replacing a PSU/7HU-DC, PSU/7HU-DC-HP, or PSU/7HU-DC-800
Replacing a PSU/7HU-R-DC or PSU/7HU-R-DC-HP
Replacing a PSU/9HU-DC, PSU/X9HU-DC-800, or PSU/9HU-AC
Replacing, Upgrading, or Downgrading PSUs in a Mixed PSU Configuration
Before replacing or upgrading PSUs in a protected configuration, check whether any

power consumption alarms are raised against the corresponding shelf.
• If a PWRCON-PROV alarm is present at the shelf, you may still replace or upgrade
the PSU. However, note that there are pre-provisioned/unequipped modules in the
shelf which, if installed, would require more power than the PSU can supply. Refer
to PWRCONS-PROV (PSU Limit-Provisioned) to troubleshoot this alarm.
• If a PWRCON-EQUD alarm is present at the shelf, do NOT replace or upgrade the
PSU. The modules equipped at this shelf require more power than the PSU can
supply. Refer to PWRCONS-EQUD (PSU Limit-Equipped) to troubleshoot this
alarm.
General Information
This subsection includes general information about power supply replacement in addition
to the replacement procedures described below.
Read and understand the relevant information in the FSP 3000R7

“Safety Guide” and the following instructions before you perform any
module replacement. Failure to do so could result in personal injury or
damage to the equipment.
If you encounter any problems with a power supply unit (PSU) the easiest fix is to simply
replace it with a new one of the same type and from the same manufacturer as soon as
possible. Do NOT attempt to operate a malfunctioning power supply!
After upgrades are made to the system, the installed power supplies may not provide
enough wattage to power all the components in the shelf. In this case, you need to
upgrade to PSUs with a higher wattage rating to meet the system’s power consumption
needs.
Replacing or upgrading a power supply involves removing the original

PSU and installing the new one. In this respect, the replacement
procedures described below cover the the procedures for upgrading the
Note PSUs as well.
Slots 1+2 and/or 19+20 of the SH9HU, SHX9HU, SH7HU or SH7HU-R shelves are
reserved for the PSUs. Though the PSU/7HU-AC-800 may be installed in any slot of a
SHX9HU shelf, it is recommended to install it in slot 1+2, 10+11, or 19+20. 1HU
equipment shelves with rear power access (SH1HU-R and SH1HU-R/PF) require the
power supply units to be placed through the back.
The FSP 3000R7 shelves are normally equipped with dual PSUs.
The PSUs are hot swappable, which means they can be removed and
replaced while the FSP 3000R7 system is powered on and running.
However, before you remove and replace a PSU, determine if the
Note system provides power supply redundancy or non-redundancy.
When running in power redundancy mode, you can replace or upgrade a PSU while the
system is operating. Only one PSU can be replaced at a time. The second PSU must
remain connected to the AC or DC power source. Operating in non-redundant power
mode (only one PSU is installed in the shelf) will require a complete system power off
when removing, replacing or upgrading a power supply.
Ensure that you have the replacement or upgrade unit available and
unpacked before you remove a PSU from an active shelf. Always
replace a PSU immediately to fully restore power redundancy.
Note
If a replacement PSU is not available, either leave the original power supply in the shelf or
remove it and fill the empty slots with two dummy modules (DM/5HU) until you have the
replacement unit. While a PSU is not installed, airflow through the shelf is reduced, and
the EMI emissions requirements are not met.
There is no on/off power switch on the PSUs! To disconnect the supply voltage from the
PSU you need to unplug the power cord on AC units or cut off the power with the
associated circuit breaker to the DC unit.
Always assume that a high voltage potential exists within a PSU while servicing it, even
if it is de-energized and disconnected from its power source.
Power Supply Removal Alarm

The management software constantly monitors the system modules within the shelf for
system-critical events. Removing a power supply unit from the shelf is detected and a
corresponding alarm (RMVD alarm) is generated by the management system. This alarm
is listed in the Event Log table and Fault Management table. To avoid raising an RMVD
alarm after the same PSU has been reinserted completely, comply with the following rule.
A quick sequence of removing and reinserting a PSU is not allowed.

Make sure that at least 30 seconds has elapsed between removal and
reseating the same unit.
Note
For specific information about the power supply units, refer to the Hardware Description
and Module and System Specification.
Replacing a PSU/1HU-R-AC(-200) or PSU/1HU-R-DC-

200
Only Service Personnel are allowed to replace a PSU/1HU-R-AC,

PSU/1HU-R-AC-200, or PSU/1HU-DC-200.
CAUTION
For specific information about these power supply units (PSUs), refer to the Hardware
Description.
A malfunctioning PSU/1HU-R-AC can be replaced either with a PSU of the same type or
by its successor the PSU/1HU-R-AC-200.
The term “PSU/1HU-R-AC(-200)” is henceforth used to refer to the PSU/1HU-R-AC and
PSU/1HU-R-AC-200.
The PSU/1HU-R-AC(-200) and PSU/1HU-R-DC-200 can be swapped out while the shelf
is in service. The system will keep running with its redundant power supply unit provided
that one is installed in the shelf.
Equipment Required
• No2 Phillips screwdriver to assist in loosening the knurled screws
• Suitable grounded surface or an antistatic mat for placing the power supply unit
• Replacement power supply unit packaged in the shipping box
Replacement Procedure
Follow these steps to replace the PSU/1HU-R-AC(-200) or the PSU/1HU-R-DC-200.
To prevent ESD damage to adjacent optical modules, take normal static

precautions in replacing the module.
It is assumed that you are familiar with power supplies and are aware of the electrical
safety precautions that are to be taken to avoid personal injury and damage to the
equipment.
To replace a PSU/1HU-R-AC(-200) or PSU/1HU-R-DC-200, several tasks must be
completed. Some tasks are detailed in sub-tasks. Pay attention to the safety notices and
additional information that are given below.
rack.
Step 2 Find the faulty PSU/1HU-R-AC(-200) or PSU/1HU-R-DC-200 which has to be
replaced.
Risk of electric shock.

Prior to replacing the PSU, disconnect it from its power source and
secure the circuit against re-energizing.
WARNING
Risk of Power Failure!

Do not disconnect the wrong PSU/1HU-R-AC(-200) or PSU/1HU-R-DC-200,
otherwise you risk accidentally powering down the whole shelf.
Step 3 Disconnect the faulty PSU/1HU-R-AC(-200) or PSU/1HU-R-DC-200 from the

AC or DC power source:
a) To disconnect the PSU/1HU-R-AC(-200):
• Lift the power cord locking clamp to release the device plug to
disconnect the PSU/1HU-R-AC-200.
• Remove the device plug of the AC power cord from the appliance
coupler on the unit faceplate.
b) To disconnect the PSU/1HU-R-DC-200, switch OFF the corresponding
circuit breaker in the Power Distribution Unit (PDU).
Risk of electric sparks if the circuit breaker is not switched off!

Electric sparks can melt the connector metal. Melted material is
extremely hot. Melted material may cause serious injuries.
CAUTION
After unplugging the associated AC power cord from the appliance

coupler (PSU/1HU-R-AC-(-200)), or switching off the corresponding
circuit breaker in the PDU (PSU/1HU-DC-200), the power LED turns
red. The power supply unit has to be inserted into the shelf for at least 30
Note seconds to discharge completely. The power LED turns off as soon as
the unit is removed from the backplane connector.
Step 4 To prevent inadvertent DC power restoration:

• Use adhesive tape to lock the power switch in the OFF-position.
• Place a warning on the PDU to indicate it should NOT be switched on
due to ongoing maintenance activities.
Step 5 Loosen the locking screws on each side of the power plug and remove the plug
of the DC power cord from the power input connector in the unit faceplate.
Step 6 Remove the AC or DC power supply unit from the shelf slots as follows:
Risk of residual voltage!

After unplugging the power cord wait at least 30 seconds to avoid
electric shock. After that remove the unit from the shelf.
WARNING
Hot surface!
A malfunctioning power supply unit can get very hot during operation.
Touching the hot board covers may cause skin burns. Allow the unit to
cool before removing it from the shelf slots. Put only cooled units into the
CAUTION
static-protective package.
a) Using your fingers or a No2 Phillips screwdriver, turn the two knurled
screws in counter-clockwise direction until they are loose.
b) Firmly pull on the knurled screws until the unit is free from the shelf and
carefully slide the unit straight out of the slot while holding it by the
faceplate and bottom edge.
If removing the PSU/1HU-R-AC-200 or the PSU/1HU-R-DC-200, use its
faceplate handles to firmly pull it out of the shelf slot.
c) Place the unit on a grounded surface or an antistatic mat.
Never reach into the vacant shelf slots. Contact with the adjacent optical modules
or the connectors on the backplane could result in damage to the equipment.
Removal of a power supply unit is automatically detected by the

management software. The internal management system receives a trap
message.
Note A power supply unit must not be removed from the shelf for an extended
period of time. Replace it immediately to fully restore power redundancy.
Step 7 Take the replacement unit out of the shipping box. Remove it from the static-
antistatic mat.
Step 8 Check and prepare the replacement unit as follows:
a) Make sure that the power supply unit is the correct one you want to install
(type, specifications). To quickly obtain the adequate information, refer to
the faceplate markings and the labels on the board cover.
b) Inspect the PSU/1HU-R-AC(-200) or PSU/1HU-R-DC-200 for any
damage. If necessary, use canned, dry, oil-free compressed air to blow off
any possible dust particles.
Risk of hazardous voltage!

Be aware that you may touch live contacts when the PCB cover is
damaged or missing and voltage is applied later. Never use the unit
WARNING without PCB cover and metallic enclosure!
• Ensure that the PCB cover and the metallic enclosure are mounted
properly and that they are not damaged.
• Carefully check the plug-in board connector of the PSU/1HU-R-AC(-

200) or PSU/1HU-R-DC-200 for dirt, any deformation in the shape of
the pin holes, and damage on the outside.
• Check the EMI shielding gasket on the faceplate edges of the PSU for
damage.
If the PSU/1HU-R-AC(-200) or PSU/1HU-R-DC-200 is dropped on a hard
surface, damaged in any way, or if its covers are missing, do not install the
unit. Return it to ADVA Optical Networking for examination and repair.
connectors

not slide in a module into that shelf slot.
If the plug-in board connector of a power supply unit is damaged,
WARNING do not install this unit.

Be careful not to damage the EMI shielding gasket on the faceplate edges of the
power supply when inserting the unit into the slots. Otherwise EMC compliance
cannot be achieved.
Step 10 Insert the replacement unit into the empty slots as follows:
Replace a faulty power supply unit only with a power supply unit of
the same type and from the same manufacturer! Failure to do so
could result in loss of safety approval for the system and damage to
WARNING equipment.
a) Hold the unit with both hands by the faceplate so that the markings are
upright.
b) Align the upper and lower edges of the unit with the upper and lower tracks
in the slot. If the module is in the correct position, carefully slide it into the
slots a few millimeters while guiding the upper and lower edges of the unit
in the tracks.
If the edges of the unit do not glide in the tracks, the unit cannot be
inserted correctly. In this case, stop immediately and remove the
replacement unit. Position the unit again and reinsert it.
Note
c) Using moderate force, push gently until the unit connectors mate properly
with the backplane connectors.
Risk of unit damage!

If you need a force greater than 90 Newton (20.2 lbf) to push in the unit, stop
immediately. Inspect the unit and the electrical connectors. If the unit and the
connectors are not damaged, repeat Step 10.
Step 11 Ensure that the power supply unit is properly and completely inserted into the
slots. The unit is properly and completely inserted when its faceplate is flush
with the faceplates of the adjacent modules and the shelf panels.
Insertion of a power supply unit is automatically detected by the

message.
Note
Step 12 When the unit is inserted properly and completely, secure it tightly in the slots
as follows:
a) Hold the unit in place with your left hand and simultaneously turn the two
knurled screws clockwise into the threaded holes using the thumb and
forefinger of your right hand.
Step 13 Apply voltage to the PSU/1HU-R-AC(-200) as follows:
a) Attach the device plug of the power cord to the appliance coupler on the
unit faceplate and secure the plug with the locking clamp.
b) Observe the power LED
The power LED should light up green. This indicates that power is supplied
to the replacement unit and that it is functioning properly.
Step 14 Apply voltage to the PSU/1HU-R-DC-200 as follows:
a) Push the power plug of the DC power cable straight in to the input
connector on the unit faceplate and secure it by turning the locking screws.
Do not overtighten the screws.
b) As appropriate, remove the warning previously placed on the PDU and
switch ON the corresponding circuit breaker.
c) Observe the power LED.
The power LED should light up green. This indicates that power is supplied
to the replacement unit adn that it is functioning properly.
Should you experience any problems with the unit, refer to

“Troubleshooting Power Supply Units” on p. 88. If the unit does not
respond, remove it from the slot as described above. Install another
replacement unit or reinsert the appropriate dummy module into the
Note
empty slots as described in “Inserting a Dummy Module” on p. 773.
Step 15 Place the removed power supply unit in the original static-protective package.
If you removed the PSU/1HU-R-AC-200 or PSU/1HU-R-DC-200,

disassemble the power cord locking clamp by following the substeps below
before packing away:
a) Grasp the locking clamp on the two long sides and squeeze them together
until they are free from the guide as shown in Figure 55.
Figure 55: Disassembling the Power Cord Locking Clamp
b) While squeezing the locking clamp remove it from the guide.

c) Place the power cord locking clamp in the original static-protective
package.
Step 16 Put the static-protective packages into the original shipping box and lay the
box aside.
Step 18 Detach the wrist strap from your wrist, disconnect the grounding wire from the
wire aside.
Step 19 Return the defective module to ADVA Optical Networking for repair, as
If you have any problems that result in a deviation from the insertion procedure
Replacing a PSU/7HU-AC, PSU/7HU-AC-HP, or

PSU/7HU-AC-800
Only Service Personnel are allowed to replace a PSU/7HU-AC or

PSU/7HU-AC-HP.
CAUTION
For specific information about these power supply units, refer to the Hardware
Description.
This procedure applies to PSU types PSU/7HU-AC, PSU/7HU-AC-800, and PSU/7HU-
AC-HP, henceforth referred to as “PSU/7HU-AC(-HP)”.
A malfunctioning PSU/7HU-AC(-HP) can be swapped out while the shelf is in service.

The system will keep running with its redundant power supply unit given that one is
installed in the shelf.
Required Equipment

If the shelf power consumption is 350 W to 400 W before upgrading a

PSU/7HU-AC 400 W variant to a higher power AC variant, the remaining
PSU/7HU-AC 400 W variant may raise a VOLTIN alarm when its partner
PSU/7HU-AC 400 W variant is removed or its AC connector is
unplugged. The VOLTIN alarm may be raised continuously or may toggle
Note (raise and clear repeatedly), until the higher power AC variant is inserted
and voltage is applied to it. This condition does NOT affect traffic or the
shelf/module operation.
equipment.
Step 3 Locate the PSU/7HU-AC(-HP) which needs to be replaced.
Step 4 Disconnect the faulty PSU/7HU-AC(-HP) from the mains as follows:

Do not disconnect the wrong PSU/7HU-AC(-HP), otherwise you risk accidentally
powering down the whole shelf.
a) Remove the device plug of the AC power cord from the appliance coupler
on the unit faceplate.
b) Place the AC power cord aside for later use.
If only one power supply unit is installed into the shelf, a controlled power
down is not given. Once the unit is removed it is in pending status and
voltage is no longer available via backplane. It takes at least 1 hour until
Note the unit is discharged completely.
For a controlled power down of one power supply unit, two redundant
power supplies have to be installed into the shelf. After unplugging the
associated AC power cord from the appliance coupler, the power LED
turns red. The power supply unit has to be inserted into the shelf for at
Note least 30 seconds and to discharge completely. The power LED goes off
as soon as the unit is removed from the backplane connector.
c) Remove the power supply unit from the shelf slots as follows:

After unplugging the power cord wait at least 30 seconds to avoid
electric shock. After that remove the unit from the shelf.
WARNING
Hot surface!
CAUTION
The power supply unit is relatively heavy. Support the unit with one hand
while removing it from the slots.
Note
d) Using your fingers or a Torx screwdriver TX10, turn the four knurled
screws in counter-clockwise direction until they are removed from the
threaded holes completely.
e) Firmly pull on the screws until the unit is free from the shelf and carefully
slide the unit straight out of the slots while holding it by the faceplate and
bottom edge.
f) Put the unit onto a grounded surface or an antistatic mat.

message.
antistatic mat.

b) Inspect the PSU/7HU-AC(-HP) visually for any damage. If necessary, use
particles.

• Carefully check the plug-in board connector of the PSU/7HU-AC(-HP) for
dirt, any deformation in the shape of the pin holes, and damage on the
outside.
• Check the EMI shielding gasket on the faceplate edges of the PSU/7HU-
AC(-HP) for damage.
If the PSU/7HU-AC(-HP) is dropped on a hard surface, damaged in any
way, or if its covers are missing, do not install the unit. Return it to ADVA
Optical Networking for examination and repair.
connectors

not slide in a power supply unit into that shelf slot.

cannot be achieved.
WARNING equipment.
The PSU may only be placed into slots 1+2 and 19+20.
Note
upright.
in the tracks.
Note


message.
Note
as follows:
a) Hold the unit in place with your left hand and simultaneously turn two
diagonally arranged knurled screws clockwise into the threaded holes
using the thumb and forefinger of your right hand.
b) Turn the remaining knurled screws exactly the same way into the threaded
holes as well.
c) Tighten the screws.
Step 11 Apply voltage to the power supply unit.
a) Attach the device plug of the power cord to the connector on the unit
faceplate.
b) Observe the power LED.
The power LED should light up green. This indicates that DC power is
supplied to the replacement unit and that it is functioning properly.

respond, remove it from the slots as described above. Install another
Note empty slots as described in “Inserting a Dummy Module” on p. 773 and
“Removing a Dummy Module” on p. 775.
Step 13 Put the static-protective package into the original shipping box and lay the box
aside.
wire aside.
Step 16 Return the defective module to ADVA Optical Networking, as described in the
Replacing a PSU/7HU-DC, PSU/7HU-DC-HP, or

PSU/7HU-DC-800
Only Service Personnel are allowed to replace a PSU/7HU-DC,

PSU/7HU-DC-HP, or PSU/7HU-DC-800.
CAUTION
Description.
A malfunctioning PSU/7HU-DC, PSU/7HU-DC-HP, or PSU/7HU-DC-800 can be
swapped out while the shelf is in service. The system will keep running with its redundant
power supply unit provided that one is installed in the shelf.
Equipment Required
• Flat blade screwdriver (3.5 mm x 0.5 mm) or Phillips crosstip screwdriver for
clamping and detaching the wires of the DC power cord
• TPA 25 A fuse and AWG 10 power cord when upgrading to a PSU/7HU-DC-800
Follow these steps to replace a PSU/7HU-DC, PSU/7HU-DC-HP, or PSU/7HU-DC-
800.

Upgrading to a PSU/7HU-DC-800 requires installing a 25 A fuse panel

(see Step 9 of this procedure), unless your current fuse panel supports
25 A.
Note
equipment.
the safety notices and additional information that are given below.
rack.
Step 3 Find the faulty PSU which has to be replaced.
Step 4 Disconnect the faulty PSU from the associated DC power source as follows:

Do not disconnect the wrong PSU, otherwise you risk accidentally powering down
the whole shelf.
a) Turn off the corresponding power switch of the DC power source that is
connected to the faulty PSU.
If only one PSU/7HU-DC-HP is installed into the shelf, a controlled

power down is not given. Once the unit is removed, it is in pending status
and voltage is no longer available via the backplane. It takes at least 1
Note hour until the unit is discharged completely.
For a controlled power down of one PSU/7HU-DC-HP, two redundant

power supplies have to be installed into the shelf. A controlled power
down of a PSU/7HU-DC is provided when one unit is installed. After
switch-off, the power LED turns red. The power supply unit has to be
removed from the shelf for at least 30 seconds to discharge completely.
Note
The power LED goes off as soon as the unit is removed from the
backplane connector.
b) For all PSU replacements other than an upgrade to a PSU/7HU-DC-800,

select one of the following methods to safeguard against inadvertent
power restoration:
• Remove the corresponding fuse from the fuse holder of the DC power
source. Store the fuse in a safe place.
• Save the power switch OFF-position with adhesive tape.
Risk of electric shock!

Make sure, that the power supply unit is disconnected from the DC
power source. Do not disconnect a live cable.
Risk of electric shock and short-circuits!

Before disconnecting the DC power cord, ensure that no voltage is
WARNING
applied to the power cord. Adhere to the above sub-steps.
Ignoring these instructions may result in undesired operation,
damage to the unit and personal injury.
c) When replacing a PSU/7HU-DC or PSU/7HU-DC-HP, remove the

screwed protective cover from the terminal block on the unit faceplate.
d) When replacing a PSU/7HU-DC or PSU/7HU-DC-HP, use the appropriate
screwdriver to remove the screws from the terminal block.
When replacing a PSU/7HU-DC-800, loosen the two screws on the D-
SUB.
e) Take off the wires of the DC power cord in the order positive lead (+),
negative lead (-), ground wire.
f) Place the DC power cord aside for later use.
g) When replacing a PSU/7HU-DC or PSU/7HU-DC-HP, reinsert the
terminal screws.
When replacing a PSU/7HU-DC-800, tighten the screws on the D-SUB.
h) When replacing a PSU/7HU-DC or PSU/7HU-DC-HP, place the
protective cover back onto the terminal block.
Step 5 Remove the power supply unit from the shelf slots as follows:

After switch-off wait at least 30 seconds to avoid electric shock.
After that remove the unit from the shelf.
WARNING
Hot surface!
CAUTION
Note
a) Using your fingers or a Torx screwdriver TX10, turn the four knurled
screws in counter-clockwise direction until they are removed from thread
holes completely.
b) Firmly pull on the screws (applicable to PSU/7HU-DC and PSU/7HU-DC-
HP) or the PSU handles (applicable to PSU/7HU-DC-800 only), until the
unit is free of the shelf and carefully slide the unit straight out of the slots,
while holding it by the faceplate and bottom edge.

message.
antistatic mat.
a) Refer to the faceplate markings and the labels on the board cover to
ensure this is the intended PSU (type, specifications).
b) Inspect the PSU for any damage. If necessary, use canned, dry, oil-free
compressed air to remove dust particles.

properly and are not damaged.
• Carefully check the plug-in board connector of the PSU for dirt, any
deformation in the shape of the pin holes, and outer damage.
damage.
If the PSU is dropped on a hard surface, damaged in any way, or if its
covers are missing, do not install the unit. Return it to ADVA Optical
Networking for examination and repair.
Step 8 Check inside the shelf to ensure that:
• Foreign conductive bodies are not present between pins on the backplane
connectors
• Pins on the backplane connectors are not bent or broken.


cannot be achieved.
Step 9 When upgrading to a PSU/7HU-DC-800,

a) Install a TPA 25 A fuse panel (unless your current fuse panel supports 25
A) and an AWG 10 power cord.
b) Delete the previous PSU from your management system.
Step 10 Insert the replacement PSU into the correct slot as follows:
WARNING equipment.
Note
upright.
in the slot. Once the module is in the correct position, carefully slide it into
the slots a few millimeters while guiding the upper and lower edges of the
unit in the tracks.
Note
c) Push in and fully seat the replacement PSU so that the unit is properly
connected to the backplane.

Step 11 Ensure that the replacement PSU is properly and completely inserted into the

message.
Note
as follows:
holes as well.
Step 13 Reconnect the PSU to the associated DC power source to apply voltage, as
follows:

Before connecting the DC power cord, ensure that no voltage is
applied to the power cord. Adhere to the connection procedure
below.
WARNING Ignoring these instructions may result in undesired operation,
a) When replacing a PSU/7HU-DC or PSU/7HU-DC-HP, remove the

screwed protective cover from the terminal block.
b) When replacing a PSU/7HU-DC or PSU/7HU-DC-HP, remove the screws
from the terminal block using an appropriate screwdriver and lay them
aside. Do not proceed if a terminal is damaged. Immediately replace the
whole terminal block.
When replacing a PSU/7HU-DC-800, loosen the two screws on the D-
SUB.
c) Ensure that voltage is NOT applied to the DC power cord.
d) Connect the wires of the DC power cord.
PSU/7HU-DC-800:
The D-SUB dictates the wiring sequence. Plug the cable's D-
SUB connector to the PSU D-SUB receptacle and tighten the two screws.
PSU/7HU-DC and PSU/7HU-DC-HP:

The proper wiring sequence is ground to ground, positive to positive and
negative to negative. The upper screw terminal is for the protective ground,
the middle one for the negative pole (-) and the lower terminal is used for
the positive pole (+).
When connecting a 3-core DC power cord to the terminal block, ensure the
ground wire (green-yellow) connects to the Protective ground (PE). The
color of the positive and negative wires may differ. Ensure that the positive
lead is connected to the positive (+) terminal, the negative lead to the
negative (-) terminal and the ground lead to ground.
• Attach the wires to the respective terminals by inserting the screws
into the lugs.
• Tighten the terminal screws securely.
Pay attention to polarity! If the polarity is reversed, the PSU will not operate when
the power cable is connected incorrectly.
e) When replacing a PSU/7HU-DC or PSU/7HU-DC-HP, ensure that all

wires are correctly fixed at the terminals.
f) When replacing a PSU/7HU-DC or PSU/7HU-DC-HP, place the
protective cover back onto the terminal block.
Step 14 Apply voltage to the PSU as follows:
a) For PSU replacements other than an upgrade to PSU/7HU-DC-800,
reinstall the fuse into the fuse holder of the DC power source, or take off
the adhesive tape on the power switch and turn it to the On-position,
depending on the method you selected in Step 4b.
b) Confirm that the DC power source has power. The green power indicator
should be lit.
c) Turn on the corresponding switch of the DC power source.
d) Observe the power LED.
If the unit does not respond, remove it from the slots as described above.
Install another replacement unit or reinsert the appropriate dummy
module into the empty slots as described in “Inserting a Dummy Module”
Note on p. 773.
Step 15 Place the removed PSU in the original static-protective package.

aside.
wire aside.
If you have any problems that result in a deviation from the procedure
Replacing a PSU/7HU-R-DC or PSU/7HU-R-DC-HP
Only Service Personnel are allowed to replace a PSU/7HU-R-DC or

PSU/7HU-R-DC-HP.
CAUTION
Description.
The term “PSU/7HU-R-DC(-HP)” is henceforth used to refer to the PSU/7HU-R-DC and
PSU/7HU-R-DC-HP.
The PSU/7HU-R-DC(-HP) is exclusively designed for the use in the

USA.
Note
A malfunctioning PSU/7HU-R-DC(-HP) can be swapped out while the shelf is in service.

The system will keep running with its redundant power supply unit provided that one is
installed in the shelf.
Equipment Required
Follow these steps to replace a PSU/7HU-R-DC(-HP).

equipment.
the safety notices and additional information.
rack.
Step 3 Find the faulty PSU/7HU-R-DC(-HP) which has to be replaced.
Step 4 Disconnect the faulty power supply unit from the associated DC power source
as follows:

Do not disconnect the wrong power supply unit, otherwise you risk accidentally
powering down the whole shelf.
a) Turn off the corresponding power switch of the DC power source that is
connected to the faulty PSU/7HU-R-DC(-HP).
If only one power supply unit is installed into the shelf a controlled power
down is not given. Once the unit is removed it is in pending status and
voltage is no longer available via backplane. It takes at least 1 hour until
Note the unit is discharged completely.
For a controlled power down of one power supply unit, two redundant
power supplies have to be installed into the shelf. After switch-off the
power LED turns red. The power supply unit has to be inserted in the
shelf for at least 30 seconds to discharge completely. The power LED
Note
goes off as soon as the unit is removed from the backplane connector.
b) To safeguard against inadvertent power restoration, follow either option:

• Save the power switch OFF-position with adhesive tape.


Before disconnecting the DC power cord make sure that no voltage
WARNING
is applied to the power cord. Adhere the sub-steps above.
Ignoring this instructions may result in undesired operation,
Step 5 Remove the power supply unit from the shelf slot as follows:

WARNING
Hot surface!
cool before removing it from the shelf slot. Put only cooled units into the
CAUTION
while removing it from the slot.
Note
screws in counter-clockwise direction until they are removed from
threaded holes completely.
b) Firmly pull on the screws until the unit is free of the shelf and carefully slide
the unit straight out of the slot, while holding it by the faceplate and bottom
edge.
c) Put the unit onto a grounded surface or an antistatic mat.
Never reach into vacant shelf slots. Contact with the adjacent optical modules or
the connectors on the backplane could result in damage to the equipment.

message.
Step 6 Take the replacement unit out of the shipping box.

Step 7 Remove the static-protective package and immediately place the unit onto a
grounded surface or an antistatic mat.
b) Inspect the PSU/7HU-R-DC(-HP) visually for any damage. If necessary,
particles.

• Carefully check the plug-in board connector of the PSU/7HU-R-DC(-
HP) for dirt, any deformation in the shape of the pin holes, and damage
on the outside.
• Check the EMI shielding gasket on the faceplate edges of the

PSU/7HU-R-DC(-HP) for damage.
If the PSU/7HU-R-DC(-HP) is dropped on a hard surface, damaged in any
Optical Networking for examination and repair.
connectors


cannot be achieved.
Step 10 Insert the replacement unit into the empty slot as follows:
WARNING equipment.
Note
upright.
in the tracks.
Note

slot. The unit is properly and completely inserted when its faceplate is flush

message.
Note
Step 12 When the unit is inserted properly and completely, secure it tightly in the slot
as follows:
holes as well.
Step 13 Apply voltage to the power supply unit as follows:
a) As appropriate, either reinstall the fuse into the fuse holder of the DC
power source or take off the adhesive tape on the power switch and turn it
to the On-position.
b) Confirm that the DC power source has power. The green power indicator
should be lit.
c) Turn on the corresponding switch of the DC power source.
d) Observe the power LED.
Should you experience any problems with the unit, refer to the LED
description in “PSU/7HU-R-DC” on p. 92. If the unit does not respond,
refer to remove it from the slot as described above. Install another
Note
empty slot as described in “Inserting a Dummy Module” on p. 773.
aside.
wire aside.
Replacing a PSU/9HU-DC, PSU/X9HU-DC-800, or

PSU/9HU-AC
Only Service Personnel are allowed to replace a PSU/9HU-DC, a

PSU/X9HU-DC-800, or a PSU/9HU-AC.
CAUTION
For specific information about this power supply unit, refer to the Hardware Description.
A malfunctioning PSU/9HU-DC, PSU/X9HU-DC-800, or PSU/9HU-AC can be swapped
out while the shelf is in service. The system operates with its redundant power supply
unit provided that one is installed in the shelf.
Equipment Required
Before starting the procedure, ensure the following equipment and tools are available.
• Replacement power supply unit of the same type
• Torx TX10 screwdriver to assist in loosening the knurled screws
• Original shipping boxes including the static-protective packaging for returning the
equipment
Follow these steps to replace the PSU/9HU-DC, PSU/X9HU-DC-800, or the PSU/9HU-
AC.

equipment.
Step 3 Find the faulty power supply unit that needs to be replaced.
Risk of electric shock.

Prior to replacing the PSU, disconnect it from its power source and
secure the circuit against re-energizing.
WARNING
Step 4 Disconnect the faulty power supply unit from the associated power source:

Do not disconnect the wrong power supply unit, otherwise you risk accidentally
powering down the complete shelf.
a) To disconnect the PSU/9HU-AC, remove the device plug of the AC power

cord from the appliance coupler on the unit faceplate.
b) To disconnect the PSU/9HU-DC or PSU/X9HU-DC-800, switch OFF the
corresponding circuit breaker in the Power Distribution Unit (PDU).
Risk of electric sparks if the circuit breaker is not switched off!

Electric sparks can melt the connector metal. Melted material is
extremely hot. Melted material may cause serious injuries.
CAUTION
After unplugging the associated AC power cord from the appliance

coupler (PSU/9HU-AC), or switching off the corresponding circuit
breaker in the PDU (PSU/9HU-DC or PSU/X9HU-DC-800), the PSU
power LED turns red. The power supply unit has to be inserted in the
Note shelf for at least 30 seconds to discharge completely. The power LED
turns off as soon as the unit is removed from the backplane connector.
Step 5 To prevent inadvertent DC power restoration:

• Use adhesive tape to lock the power switch in the OFF-position.
• Place a warning on the PDU to indicate it should NOT be switched on
due to ongoing maintenance activities.
Step 6 Remove the power supply unit from the shelf slots:

WARNING
Hot surface!
CAUTION
Note
a) Using your fingers or a Torx TX10 screwdriver, turn the four knurled
screws in counter-clockwise direction until they are removed from thread
holes completely.
b) Firmly pull on the screws until the unit is free of the shelf and carefully slide
the unit straight out of the slots, while holding it by the faceplate and
bottom edge.

message.
Step 7 Remove the replacement unit from the static-protective package and place it
on a grounded surface or an antistatic mat.
Step 8 Check and prepare the replacement unit:
ensure the power supply unit is the intended one (type, specifications).
b) Inspect the power supply unit for any damage. If necessary, use canned,
dry, oil-free compressed air to blow off any possible dust particles.

deformation in the shape of the pin holes, and external damage.
• Check the EMI shielding gasket on the faceplate edges of the power
supply unit for damage.
If the power supply unit is dropped on a hard surface, damaged in any
Optical Networking.
connectors


cannot be achieved.
WARNING equipment.
upright.
in the tracks.
Note
The PSU/9HU-DC or PSU/9HU-AC may only be installed in slots 1+2

and 19+20 of the SH9HU shelf.
The PSU/X9HU-DC-800 may only be installed in slots 1, 2, 19, and 20 of
Note the SHX9HU shelf.
with the backplane connector.


message.
Note
as follows:
holes as well.

respond, remove it from the slots as described above. Install another
Note
empty slots as described in “Inserting a Dummy Module” on p. 773.
Step 13 Apply voltage to the PSU/9HU-AC:

a) Attach the device plug of the power cord to the appliance coupler on the
unit faceplate.
b) Observe the power LED.
The power LED should light up green. This indicates that AC power is
Step 14 Apply voltage to the PSU/9HU-DC or PSU/X9HU-DC-800:
a) As appropriate,remove the warning previously placed on the PDU and
switch ON the corresponding circuit breaker.
b) Observe the power LED on the faceplate of the unit.
aside.
wire aside.
Step 19 Return the defective module to ADVA Optical Networking, as described in the
Replacing, Upgrading, or Downgrading PSUs in a Mixed

PSU Configuration
Only Service Personnel are allowed to replace the PSUs addressed in

this section.
CAUTION
When replacing, upgrading, or downgrading the following PSUs in an active system shelf
equipped with different PSU models/types, the system shelf/chassis may experience a
momentary power dip/loss, resulting in a possible service interruption:
Part Number Hardware Revision(s)
PSU/7HU-AC1 40700002 2.01 - 2.03
PSU/7HU-DC-HP 1040700003 2.00 - 2.02
PSU/7HU-AC-HP 1040700004 2.00
PSU/7HU-DC-800 1040700005 All revisions
PSU/7HU-AC-800 1040700006 All revisions
To circumvent this problem, follow the steps outlined in this procedure to

replace/upgrade/downgrade these PSU variants, when they are utilized in a mixed PSU
configuration2. A mixed configuration comprises of a PSU/7HU-AC with hardware
revision 2.01 through 2.03, a PSU/7HU-AC-HP with hardware revision 2.00, or a
PSU/7HU-DC-HP with hardware revision 2.00 through 2.02 used with any other PSU
version.
For all other PSU replacement/upgrade/downgrade scenarios, refer to the general
replacement procedures addressed in Replacing a PSU/7HU-AC, PSU/7HU-AC-HP, or
PSU/7HU-AC-800 or Replacing a PSU/7HU-DC, PSU/7HU-DC-HP, or PSU/7HU-DC-
800.
Requirements
• No power consumption alarms are present on this shelf. If any such alarms are
present, follow the steps outlined in PWRCONS-PROV (PSU Limit-Provisioned) or
PWRCONS-EQUD (PSU Limit-Equipped) to clear them before initiating this
procedure.
• Before downgrading a PSU, ensure that the combined current amperage readings of
the installed PSU pair does not exceed the maximum amps of the replacement PSU.
If this value is exceeded, do NOT attempt to downgrade the PSU, since the shelf
may be drawing more current than the replacement PSU can supply.
1Upgrades only.
2This procedure does not apply to the rear access variant since it cannot be powered ON
before insertion.
• Ensure the following equipment is available:

o
Torx screwdriver TX10 to assist in loosening knurled screws
o
Flat blade screwdriver (3.5 mm x 0.5 mm) or Phillips crosstip screwdriver for
clamping and detaching the wires of the DC power cord1
o
ESD-preventive wrist strap or other personal grounding device
o
Suitable grounded surface or an antistatic mat for placing the PSU on
o
Replacement PSU packaged in the shipping box
• Personnel performing this procedure are familiar with power supplies and are aware
of the electrical safety precautions to avoid personal injury and damage to the
equipment.

precautions when replacing the module.

Whenever instructed to, always ensure you disconnect the intended PSU.
Disconnecting the wrong PSU runs the risk of accidentally powering down the
whole shelf.
Step 1 Select which PSU needs to be removed first. Next, refer to Table 110 on p. 735
or to Table 111 on p. 736 to determine whether this PSU must be powered OFF
prior to removal from the shelf. “PSU Power Requirements During Insertion
and Removal” on p. 733 describes the usage of these tables.
Step 2 Attach a ESD-preventative strap to your wrist and fasten the grounding wire
onto the ESD grounding point on the shelf (if available), or to a bare metal
surface onto the rack.
Step 3 If required in Table 110 on p. 735 or Table 111 on p. 736, power OFF the PSU:
• In DC variants,
a) Turn OFF the corresponding power switch of the DC power source
connected to the PSU (with alternate power feed and PSU active).
b) To safeguard against inadvertent power restoration, select either option:
• Keep the power switch in the OFF-position with adhesive tape.
• In AC variants, remove the device plug of the AC power cord from the
appliance coupler on the unit faceplate.
Step 4 Remove or unseat the PSU from the backplane, but leave it in the slot:
screws in counter-clockwise direction until they are removed from the
thread holes completely.
b) Firmly pull on the screws until the unit is disconnected from the backplane
connectors.
1Only required when either the original or replacement PSU is a DC variant.
Step 5 If the PSU is powered ON, it may now be powered OFF:

• In DC variants,
a) Turn OFF the corresponding power switch of the DC power source
connected to the PSU (with alternate power feed and PSU active).
b) To safeguard against inadvertent power restoration, select either option:
• Keep the power switch in the OFF-position with adhesive tape.
• In AC variants, remove the device plug of the AC power cord from the
appliance coupler on the unit faceplate.
Wait for the red LED on the PSU to turn OFF, before proceeding to the
next step.
Step 6 In DC variants, remove the protective cover from the terminal block on the unit
faceplate and disconnect the wires from the PSU faceplate:

Make sure, that the PSU is disconnected from the DC power
source. Do not disconnect a live cable.

WARNING
is applied to the power cord.
Ignoring these instructions may result in undesired operation,
a) Remove the clipped protective cover from the terminal block on the unit
faceplate.
b) Using the appropriate screwdriver remove the screws from the terminal
block and take off the wires of the DC power cord in the following order:
positive lead (+), negative lead (-) and ground wire.
c) Place the DC power cord aside for later use.
d) Reinsert the terminal screws.
e) Put the protective cover back onto the terminal block.
Step 7 Delete the PSU from the slot by using NED or any other management
interface.
Step 8 Remove the PSU from the slot:

After switch-off, wait at least 30 seconds to avoid electric shock
before removing the unit from the shelf.
WARNING
Hot surface!
cool before removing it from the shelf slots. Place only cooled units into
CAUTION
the static-protective package.
Note
a) Firmly pull on the screws until the unit is free of the shelf and carefully slide
the unit straight out of the slots, while holding it by the faceplate and the
lower edge.
b) Place the unit on a grounded surface or an antistatic mat.
or the connectors on the backplane could result in equipment damage.
Removal of a PSU is automatically detected by the management

software. The internal management system receives a trap message.
A PSU must not be removed from the shelf for an extended period of
Note time. Replace it immediately to fully restore power redundancy.
Step 9 Remove the replacement PSU from the shipping box and the static-protective
package, then place it immediately on a grounded surface or an antistatic mat.
Step 10 Check and prepare the replacement PSU:
ensure this is the intended PSU (type, specifications).
b) Inspect the PSU for any damage. If necessary, use canned, dry, oil-free
compressed air to remove dust particles.

Beware that you may touch live contacts when the PCB cover is
deformation in the shape of the pin holes, and outer damage.
damage.
If the PSU is dropped on a hard surface, damaged in any way, or if its
covers are missing, do not install the unit. Return it to ADVA Optical
Networking for examination and repair.
Step 11 Check inside the shelf to ensure that:

• Foreign conductive bodies are not present between pins on the backplane
connectors
• Pins on the backplane connectors are not bent or broken.

If a backplane connector of a shelf has bent or broken pins, do not
slide a PSU into that shelf slot.
If the plug-in board connector of a PSU is damaged, do not install
WARNING this unit.

cannot be achieved.
Step 12 Insert the replacement PSU into the correct slot without fully seating it:
upright.
in the slot. Once the module is in the correct position, carefully slide it into
the slots a few millimeters while guiding the upper and lower edges of the
unit in the tracks.
Note
Step 13 If the replacement PSU is a DC variant, connect the cables as follows:

Before connecting the DC power cord make sure that no voltage is
applied to the power cord. Adhere the connection procedure
below.
WARNING Ignoring this instructions may result in undesired operation,
a) Remove the clipped protective cover from the terminal block.

b) Remove the screws from the terminal block using an appropriate
screwdriver and lay them aside.
If the terminal block is damaged, do not proceed. Immediately replace the
PSU.
c) Make sure that no voltage is impressed to the DC power cord.
d) Take the DC power cord and connect the wires to the corresponding
terminals as specified below.
Pay attention to polarity! If the polarity is reversed, the PSU will not operate when
the power cable is connected incorrectly.
The proper wiring sequence is ground to ground, positive to positive and

negative to negative. The upper screw terminal is for the protective ground, the
middle one for the negative pole (-) and the lower terminal is used for the
positive pole (+).
Connecting a 3-core DC power cord to the terminal block
Ground (green/yellow wire) Protective ground (PE)
Neutral (blue wire) negative pole (-)
Live (brown wire) positive pole (+)
Connecting a 2-core DC power cord to the terminal block
Neutral (blue wire) - 48 V negative pole (-)
Live (red wire) 0V positive pole (+)
The color of the wires may differ. In either case the positive lead must be
connected to the positive (+) terminal, the negative lead to the negative (-)
terminal and the ground lead to ground.
• Attach the wires to the respective terminals by inserting the screws
into the lugs.
• Tighten the terminal screws properly.
e) Ensure that all wires are correctly fixed at the terminals.
f) Put the protective cover back onto the terminal block.
Step 14 If the replacement PSU is an AC variant, attach the device plug of the power
cord to the connector on the unit faceplate.
Step 15 Refer to Table 110 on p. 735 or Table 111 on p. 736 to determine if this
replacement PSU must be powered ON prior to insertion into the shelf. “PSU
Power Requirements During Insertion and Removal” on p. 733 describes the
usage of these tables.
Step 16 If the replacement PSU is a DC variant and it needs to be powered ON before
insertion into the shelf, apply voltage to the unit:
a) Either reinstall the fuse into the fuse holder of the DC power source or take
off the adhesive tape on the power switch and turn it to the ON-position.
b) Confirm that the DC power source has power.
c) Turn ON the corresponding switch of the DC power source.
d) Wait 60 seconds.
The replacement PSU LED is lit red.
Step 17 If the replacement PSU is an AC variant and it needs to be powered ON before
insertion into the shelf, turn ON the corresponding switch of the AC power
source. Wait 60 seconds.
The replacement PSU LED is lit red.
Step 18 Push in and fully seat the replacement PSU so that the unit is properly
connected to the backplane. Next, secure it tightly in the slot:
holes as well.

If you require a force greater than 90 Newton (20.2 lbf) to push in the unit, stop
connectors are not damaged, repeat this step.
Step 19 If the replacement PSU was not yet powered ON, repeat Step 16/Step 17.
Step 20 If the replacement PSU LED and the shelf slot LED are not lit green, provision
the PSU.
Wait 60 seconds, then repeat this procedure for the second PSU in the
shelf to complete the upgrade/downgrade process.
PSU Power Requirements During Insertion and Removal

Generally during PSU replacement, the PSU being replaced is powered OFF prior to removal from the shelf, while the replacement PSU is powered OFF while it is inserted
into the shelf and connected to the backplane. However, the procedures addressed in “Replacing, Upgrading, or Downgrading PSUs in a Mixed PSU Configuration ” on
p. 726 vary from the "Normal" method. A mixed configuration comprises of a PSU/7HU-AC with hardware revision 2.01 through 2.03, a PSU/7HU-AC-HP with hardware
revision 2.00, or a PSU/7HU-DC-HP with hardware revision 2.00 through 2.02 used with any other PSU version.
Table 110 on p. 735 and Table 111 on p. 736 address specific PSU replacement, upgrade, and downgrade scenarios where powering the PSUs follow a different sequence.
Each PSU type is identified by the wattage level, the AC/DC type, and the hardware revision.
• The green background denotes the type of the PSU which remains in the shelf, while the blue background denotes the type and required power ON/OFF status of the
PSU being removed or inserted.
• "Powered" means that the corresponding PSU needs to be powered ON at insertion OR removal from the shelf.
• "Not Powered" means that the corresponding PSU needs to be powered OFF at insertion OR removal from the shelf.
• The PSUs in Table 110 on p. 735 and Table 111 on p. 736 have these part numbers:
Part Number
PSU/7HU-AC 40700002
PSU/7HU-DC-HP 1040700003
PSU/7HU-AC-HP 1040700004
PSU/7HU-DC-800 1040700005
PSU/7HU-AC-800 1040700006
Example
A pair of PSU/7HU-AC units with hardware revision 2.01 is being replaced with a pair of PSU/7HU-AC-HP units with hardware revision 2.01.
1 Select which PSU/7HU-AC to remove first. In this example, we will start with Slot 19/20. This is represented in Table 110 on p. 735 with blue background. The other
PSU/7HU-AC in Slot 1/2 is represented by green background. From Table 110 on p. 735, the required power state for the PSU/7HU-AC unit to be removed is "Not
Powered" (blue background). Hence power OFF the PSU, then remove it from the shelf.
2 From Table 110 on p. 735, insertion of a PSU/7HU-AC-HP into Slot 19/20 (previously occupied by the PSU/7HU-AC) requires a power state upon insertion of “Not
Powered” (blue background). Hence power OFF this PSU, then insert it into Slot 19/20.
3 From Table 111 on p. 736, removal of the remaining PSU/7HU-AC from Slot 1/2 requires a power state of “Powered” (blue background). Hence power ON this PSU,
then remove it from the shelf.
4 From Table 111 on p. 736, insertion of the last PSU/7HU-AC-HP into Slot 1/2 (previously occupied by the PSU/7HU-AC) requires a power state upon insertion of “Not
Powered” (blue background). Hence power OFF this PSU, then insert it into Slot 1/2.
Table 110: PSU Slot 19/20 Power Requirements during Replacements, Upgrades, or Downgrades
PSU in Slot 19/20 being replaced or upgraded
PSU Type PSU/7HU- PSU/7HU-AC PSU/7HU-DC-HP PSU/7HU-AC-HP PSU/7HU- PSU/7HU-

DC DC-800 AC-800
Hardware All 2.01, 2.02, >= 2.04 2.00 >= 2.01 2.00 >= 2.01 All All
Revision 2.03
PSU that PSU/7HU- All Not Powered Powered Not Powered Powered Not Powered Powered Not Powered Not Powered Not Powered
remains in DC
Slot 1/2
2.01, 2.02, Not Powered Not Not Powered Powered Not Powered Powered Not Powered Not Powered Not Powered
PSU/7HU- 2.03 Powered
AC
2.04 Not Powered Powered Not Powered Powered Not Powered Powered Not Powered Not Powered Not Powered
PSU/7HU- 2.00 Not Powered Powered Not Powered Not Not Powered Powered Not Powered Not Powered Not Powered
DC-HP Powered
2.01, 2.02 Not Powered Powered Not Powered Powered Not Powered Powered Not Powered Not Powered Not Powered
PSU/7HU- 2.00 Not Powered Powered Not Powered Powered Not Powered Not Not Powered Not Powered Not Powered
AC-HP Powered
PSU/7HU- All Not Powered Powered Not Powered Powered Not Powered Powered Not Powered Not Powered Not Powered
DC-800
AC-800
Table 111: PSU Slot 1/2 Power Requirements during Replacements, Upgrades, or Downgrades
PSU in Slot 1/2 being replaced or upgraded
PSU Type PSU/7HU- PSU/7HU-AC PSU/7HU-DC-HP PSU/7HU-AC-HP PSU/7HU- PSU/7HU-

DC DC-800 AC-800
Hardware All 2.01, 2.02, >= 2.04 2.00 >= 2.01 2.00 >= 2.01 All All
Revision 2.03
PSU that PSU/7HU- All Not Powered Powered Not Powered Powered Not Powered Powered Not Powered Not Powered Not Powered
remains in DC
Slot 19/20
2.01, 2.02,
PSU/7HU- 2.03 Not Powered Not Not Powered Powered Not Powered Powered Not Powered Not Powered Not Powered
AC Powered
PSU/7HU- 2.00 Not Powered Powered Not Powered Not Not Powered Powered Not Powered Not Powered Not Powered
DC-HP Powered
2.01, 2.02 Not Powered Powered Not Powered Powered Not Powered Powered Not Powered Not Powered Not Powered
PSU/7HU- 2.00 Not Powered Powered Not Powered Powered Not Powered Not Not Powered Not Powered Not Powered
AC-HP Powered
DC-800
AC-800
Replacing Fan Units and Fan Modules

This section describes the procedures for replacing the fan unit of an SH7HU(-R) shelf
and the fan modules of an SH9HU, SHX9HU, or SH1HU-R/PF shelf.
These sections are covered:
“Replacing a FAN/Plug-In” on p. 737
“Replacing a FAN/9HU or FAN/X9HU” on p. 739
“Replacing a FAN/1HU” on p. 742
Replacing a FAN/Plug-In
This subsection describes the procedure to replace the FAN/Plug-In (plug-in fan unit for
the SH7HU or SH7HU-R) shelf. For specific information about the fan unit, refer to the
The FAN/Plug-In is located above the module slots of the SH7HU(-R). It is a plug-in unit
with three speed controlled fans. If one or more of the three fans fail, the “fan” LED turns
yellow or red. In this case, the whole fan unit has to be replaced with a new one.
When one of the three fans is malfunctioning or has failed, this fan unit must be
replaced within 48 hours after failure. To restore system cooling, ensure that the
replacement procedure does not exceed 3 minutes!
A malfunctioning fan unit can be replaced while the shelf is in service. It is recommended
to have a spare fan module available at all times.
Figure 56 shows the front view of the SH7HU(-R) fan unit.
Figure 56: Front View of the SH7HU FAN/Plug-In
Requirements
• Replacement fan unit packaged in the shipping box
• Suitable grounded surface or an antistatic mat for placing the fan unit
Only Service Personnel are allowed to replace the FAN/Plug-In.

CAUTION
Take normal static precautions when replacing the fan unit. Failure to
follow ESD safety precautions can result in damage to the display front
panel or impair electrical circuitry.
Step 1 Take the replacement unit out of the shipping box. Remove it from the package
and place it on an appropriate surface.
a) Ensure the fan unit is an adequate replacement.
b) Inspect the unit visually for external damage and impurities. If the fan unit
is damaged, do not install it. Return the unit for repair. If necessary, use
particles.
rack.
Step 4 Remove the fan unit as follows:
a) Press down both blue levers of the defective fan unit at the same time as
shown in Figure 57.
Figure 57: Pressing Down of the Blue Levers
b) Pull the unit out of the shelf completely as shown in Figure 58.
Figure 58: Pulling Out the Unit
Step 5 Lay the unit aside.
Step 6 Insert the replacement unit as follows:

a) Hold the unit by both sides so that the faceplate markings are upright.
b) Insert the unit into the housing.
c) Press down the both blue levers (see Figure 57 on p. 738) and slide the unit
carefully to the back until both levers engage completely.

If the fan unit cannot slide in completely, stop immediately and pull it out. Inspect the
power connectors of the fan unit and the backplane (see Figure 59). If the connectors are
not damaged, reinsert the unit.
Figure 59: Front View of the SH7HU(-R) Fan Unit Removed from Housing
Step 7 Observe the “fan” status LED. When the unit is inserted properly and
completely, the “fan” status LED will light up green and the fans will start
working. This indicates that the fan unit is functioning properly. If there is an
error, the “fan” status LED will turn yellow or red.
wire aside.
Should you experience any problems with the unit, refer to “SH7HU(-R)
Fan Status LEDs” on p. 76. If the replacement unit does not work
properly, remove it again from the shelf as described above. Immediately
install another replacement unit or reinstall the defective fan unit until the
Note new one is available.
Do not operate the SH7HU(-R) shelf without having a fan unit fitted.
Step 9 Pack the removed fan unit in the original shipping box for returning.
Step 10 Return the defective fan unit to ADVA Optical Networking for repair. For details
on returning, refer to the Installation and Commissioning Manual.
Replacing a FAN/9HU or FAN/X9HU

This subsection describes the procedure to replace the FAN/9HU (plug-in fan module for
the SH9HU shelf) or the FAN/X9HU (plug-in fan module for the SHX9HU). For specific
information about these fan modules, refer to the Hardware Description.
SH9HU and SHX9HU shelves are equipped with three independent speed-controlled fan
modules, as shown in Figure 60. They are located on top of the shelf above the
CEM/9HU, as illustrated in “SH9HU and SHX9HU Shelf LEDs” on p. 81. These fan
modules are accessible from the front of the shelf.
Each fan module has one “Status” LED to indicate its operating status. The LED always
shows the failure with the highest severity. If the LED is lit yellow, red, or is off, the fan
has a failure or does not work. If a fan fails, the complete fan module must be replaced
immediately.
If a fan malfunctions or fails, this faulty fan module must be replaced by Service
Personnel within 48 hours after failure. To maintain system cooling, ensure the
corresponding fan tray slot does not remain empty for longer than 1 minute during the
replacement process!
The faulty fan module can be replaced while the shelf is in service. It is recommended to
have a spare fan module available at all times.
Figure 60 shows the front view of the three fan modules plugged in the SH9HU shelf. A
similar setup exists for fan modules in the SHX9HU shelf.
Figure 60: FAN9HU Front View
Requirements
Before starting the procedure, ensure the following equipment is available.
• Replacement fan module packaged in the shipping box
• Suitable grounded surface or an antistatic mat for placing the fan module
Only Service Personnel are allowed to replace a FAN/9HU or

FAN/X9HU.
CAUTION
Take normal static precautions when replacing the fan module. Failure to
follow ESD safety precautions can result in damage to the equipment or
impair electrical circuitry.
Step 1 Take the replacement fan out of the shipping box. Remove it from the package
and place it onto an appropriate surface.
Step 2 Check and prepare the replacement fan:
a) Ensure the fan module is an adequate replacement.
b) Inspect the fan module for external damage and impurities. If the fan
module is damaged, do not install it. Return the fan for repair. If necessary,
particles.
grounding point on the shelf (if available), or to a bare metal surface onto the
rack.
Step 4 Remove the fan unit:
a) Using your thumb and forefinger, turn the retaining screw of the relevant
defective fan module in a counter-clockwise direction until it is free from
the shelf.
b) Using the hinged handle, slowly pull the fan module out of its slot.
Before the module is pulled out all the way, use your other hand and hold
the bottom of the module to prevent it from dropping and pull it out
completely.
c) Lay the fan module aside.
Step 5 Insert the replacement fan:
a) Hold the fan by both sides so that the faceplate markings are upright.
b) Insert the fan into its slot.
c) If the fan is in the correct position, carefully slide it into the slot a few
millimeters.
d) Using moderate force, push gently until the module connectors mate

If the fan module cannot slide-in completely, stop immediately and pull it out. Inspect the
power connectors of the fan and the backplane. If the connectors are not damaged,
reinsert the fan.
e) Ensure that the module is properly and completely inserted into the slot
that is, its front side is flush with the edge of the slot.
Step 6 Observe the fan “Status” LED. When the fan is inserted properly and
completely, the fan “Status” LED will light up green and the fan will start
working. This indicates that the fan is functioning properly. If there is an error,
the fan “Status” LED will turn yellow or red.
wire aside.
Should you experience any problems with the unit, refer to “SH9HU and
SHX9HU Fan Status LEDs” on p. 82. If the replacement fan does not
work properly, remove it again from the shelf as described above.
Immediately install another replacement fan or reinstall the defective fan
Note
module until the new one is available.
Step 8 Pack the removed fan module in the original shipping box for returning.
Step 9 Return the defective fan module to ADVA Optical Networking for repair. For
details on returning, refer to the Installation and Commissioning Manual.
Replacing a FAN/1HU
This subsection describes the procedure to replace a FAN/1HU (plug-in fan module for
the SH1HU-R/PF Shelf). For specific information about this fan module, refer to the
The fan module is located on the left-hand side of the shelf. It is a plug-in module with
three speed-controlled fans. If one or more of the three fans fail, the Fan LED on the front
panel of the shelf turns yellow or red. In this case, the complete fan module has to be
replaced with a new one.
When one of the three fans is malfunctioning or has failed, this fan unit must be replaced
within 48 hours after failure to maintain redundancy and optimum cooling. To maintain
system cooling, ensure the corresponding fan module slot does not remain empty for
longer than 1 minute during the replacement process!
Removal and insertion of the fan module is automatically detected by the

management software. Each time a fan module is removed from or
inserted into the shelf slot, the internal network management system
receives a trap message.
The system emits a series of beeps during the first minute of removing
Note
the fan module. After 1 minute, the system emits a continuous audible
signal.
A malfunctioning fan module can be replaced while the shelf is in service. It is

recommended to have a spare fan module available at all times.
Requirements
• Replacement fan module packaged in the shipping box
• Suitable grounded surface or an antistatic mat for placing the fan module
Only Service Personnel are allowed to replace a FAN/1HU.

CAUTION
Take normal static precautions when replacing the fan module. Failure to
follow ESD safety precautions can result in damage to the display front
panel or impair electrical circuitry.
Step 1 Take the replacement module out of the shipping box. Remove it from the
package and place it on an appropriate surface.
a) Ensure the fan module is an adequate replacement.
b) Inspect the module visually for external damage and impurities. If the fan
module is damaged, do not install it. Return the module for repair. If
necessary, use canned, dry, oil-free compressed air to blow off any
possible dust particles.
grounding point on the shelf or to a bare metal surface onto the rack.
Step 4 Remove the display front panel:
a) Using your thumb and forefinger, turn the two captive knurled screws in a
counter-clockwise direction until they are free from the shelf. See Figure
61.
Figure 61: Screws Holding the Display Front Panel to the Shelf
b) Firmly pull on the screws until the display front panel is free from the shelf
and lay it aside. Place it on an antistatic mat.
After removing the display front panel, wait for at least 5 seconds before
you pull out the fan module. This time is taken by the fans to stop
working.
Note
c) Put your forefinger into the hole of the folded grip and gently pull the fan
module out of the shelf slot completely as shown in Figure 62 on p. 744. To
prevent dropping the module, grasp the bottom with the other hand.
Figure 62: Removing the Fan Module from the Shelf Slot
d) Lay the fan module aside.

Step 5 Insert the replacement fan module:
a) Grasp the fan module firmly on the upper and bottom sides using your
thumb and forefinger so that front side with the folded grip is facing you,
and the PCB is on the left. See also Figure 62 on p. 744.
b) If the module is in the correct position, carefully slide it into the slot a few
millimeters.
immediately and pull it out. Inspect the module and the electrical connectors. If the
module and the connectors are not damaged, reinsert the module.
The module is properly and completely inserted when its front side is flush
with the edge of the slot.
Step 6 Re-install the LED front panel back on the shelf:
a) Hold the LED front panel with your left hand in place as shown in Figure 61
on p. 743, ensuring it is aligned on all sides.
b) Turn the two attached knurled screws clockwise into the thread holes
c) Tighten the screws. Be careful not to over tighten.
If the front panel has been removed for more than 1 minute an audible
alarm is generated on the shelf so that the service technician is reminded
to re-install it. If the front panel is not re-installed after 1 minute, the fans
do not work and as a result, the operating temperature exceeds the
Note
specified limit.
Step 7 Check the Fan status LED on the front panel to ensure that the fans are
If the front panel is re-installed properly, the Fan status LED will light up green
and the fans will start working provided that the shelf is being powered. This
indicates that the fan module is functioning properly. If there is an error, the Fan
status LED will turn yellow or red.
Note that the Fan LED indicates reliable information only 5-10 seconds
after adding! After powering up the whole shelf, wait at least 5 minutes
before observing the LEDs! The LED colors can change within this time-
Note span!
Step 8 Pack the removed fan module in the original shipping box for returning.
wire aside.
Step 10 Verify that the insertion of the fan module has been detected by the
Step 11 Return the defective fan module to ADVA Optical Networking for repair. For
details on returning, refer to the Installation and Commissioning Manual.
Should you experience any problems with the module, refer to “SH1HU-
R(/PF) Fan Status LED” on p. 69. If the replacement module does not
work properly, remove it again from the shelf as described above.
Immediately install another replacement module or reinstall the defective
Note fan unit until the new one is available.
Do not operate the shelf without having a fan module inserted.
If only one fan is working, the airflow inside the shelf will be insufficient to keep the
modules cool. To avoid equipment damage and risk of fire due to component
overheating, the shelf must not be allowed to continue operation.
Replacing Air Filter Pads

This section describes how to replace an air filter pad of a PSU/1HU-R-AC-200 and of a
7HU or 9HU shelf.
The replacement procedures for the different air filter types are described in the following
subsections:
“Replacing a PSU/1HU-R-AC-200 Air Filter Pad” on p. 746
“Replacing a 7HU/9HU-Shelf Air Filter Pad” on p. 747
“Replacing the SH1HU-R/PF Shelf Air Filter Pad” on p. 749
Replacing a PSU/1HU-R-AC-200 Air Filter Pad

The air filter pad is directly located behind the air filter front cover on the PSU front panel
as shown in Figure 63. It can be replaced by the user and during system operation.
Figure 63: Front View of the Air Filter Unit
Equipment Required
• No.2 Phillips screwdriver to assist in loosening the knurled screws
• Replacement air filter pad of same type and size
Follow these steps to replace the air filter pad.
rack.
Step 2 Using your fingers or a No.2 Phillips screwdriver, turn the two knurled screws
in counter-clockwise direction until they are loose.
Step 3 Firmly pull on the screws to remove the air filter front cover.
Step 4 Lay the front cover aside.

Step 5 Use your fingers to carefully take the impure air filter pad away from the air
duct.
Figure 64: Air Filter Pad Removed from the PSU/1HU-R-AC-200
Step 6 Place a new replacement air filter pad in front of the air duct and hold it with one
finger to maintain position.
Step 7 While holding the air filter pad in position, take the air filter front cover and align
it with the threaded holes on the front panel.
Step 8 Firmly push and turn the two knurled screws clockwise into the threaded holes
Step 9 Tighten the screws.
wire aside.
Replacing a 7HU/9HU-Shelf Air Filter Pad

This section describes how to replace an air filter pad of a 7HU and 9HU shelf.
The air filter pad is located directly behind the air duct at the bottom of the shelf as shown
in Figure 65.
Figure 65: Front View of the Air Filter Unit
Equipment Required
• Replacement air filter pad
• Screwdriver (0,8 mm x max. 6 mm) to open the air filter unit
Follow these steps to replace the air filter pad.
rack.
Step 2 Slightly push both slide latches inwards at the same time and pull out the air
filter unit approximately 5 centimeters.
Step 3 Wait circa two minutes and then pull out the air filter unit completely.
Step 4 There are five small slots at the rear part of the unit as shown in Figure 66. Use
the screwdriver to carefully press open each of these slots in order to open the
air filter unit.
Figure 66: Five Slots at the rear part of the Air Filter Unit
Step 5 Remove the air filter pad from the filter unit as shown in Figure 67 on p. 749.
Figure 67: Removing an Air Filter Pad
Use only ADVA Optical Networking's original air filter pads for replacement.
Step 6 Insert a replacement air filter pad of the same type and dimensions into the air
filter unit.
Step 7 Close the filter unit by pressing both unit parts together.
Step 8 Insert the filter unit into the shelf.
Step 9 Slightly push the slide latches inwards and slide the filter unit to the back
carefully.
wire aside.
Replacing the SH1HU-R/PF Shelf Air Filter Pad

This section describes how to replace the air filter pad of the SH1HU-R/PF shelf.
The air filter unit is located in the narrow slot on the right-hand side of the shelf. The air
filter pad is accessible rightmost at the front of the shelf, as shown in Figure 68 on p. 750.
Figure 68: Front View of the SH1U-R/PF Air Filter Unit
The air filter pad can be replaced by the end-user during operation of the shelf without
shifting or even removing any optical fibers.
Equipment Required
Before starting the procedure, ensure the replacement air filter pad is available.
To replace the air filter pad, perform the following steps:
Step 1 Push the handle forward and turn it through 90° counter-clockwise to unlock
the air filter frame.
Figure 69: Air Filter Frame Unlocked
Step 2 Pull the air filter frame out of the unit completely as shown in Figure 70 on
p. 751.
Figure 70: Pulling out the Air Filter Pad
Step 3 Remove the air filter pad from the air filter frame as shown in Figure 71.
Figure 71: Removing an Air Filter Pad
Use only ADVA Optical Networking's original air filter pads for replacement.
Step 4 Insert a replacement air filter pad of the same type and dimensions into the air
filter frame as shown in Figure 71.
Step 5 Grasp the handle of the air filter frame and slide it all the way in as shown in
Figure 70.
Step 6 Push the handle forward and turn it through 90° clockwise to lock the air filter
frame.
Replacing an SH1HU Shelf

This chapter provides the procedure of replacing the following 1HU shelves:
• SH1HU-F/2DC
• SH1HU-HP/2DC
• SH1HU-HP/E-TEMP/2DC
• SH1HU-R
Only Service Personnel are allowed to replace a shelf.

CAUTION
Replacing a shelf is service affecting (SA).

Note
These shelves have to be replaced if one of their fans fail. It is recommended to have a
replacement shelf available at all times.
Before starting the procedure, ensure the following equipment and tools are available:
Equipment Required
• Replacement shelf of same type and size
• Original shipping boxes including the static-protective packages for saving the
removed modules
Tools Required
• Torx screwdriver TX10 to assist in loosening the knurled screws of the optical
modules
• An appropriate screwdriver for the shelf power supply cable depending on the shelf
type:
• SH1HU-F/2DC:
Phillips screwdriver size 2 for the terminal block screws of the shelf power
supply
• SH1HU-HP/2DC and SH1HU-HP/E-TEMP/2DC:
Screwdriver (flat-bladed 0.8 mm x 4 mm) for the captive screws of the
PHOENIX power supply plug
Only service personnel or a qualified/licensed electrician are

allowed to disconnect DC power cables.
WARNING
• Phillips head screwdriver or any other appropriate screwdriver for the rack screws
ADVA Optical Networking recommends having one person to hold the

shelf while another service person loosens the rack screws.
Note
• Wrench (7 mm or 0.276 in of size) or box spanner for the shelf grounding contacts
• An appropriate screwdriver or wrench for the rack grounding contact
Removal Procedure
Follow these steps to remove a shelf.
It is assumed that personnel performing this task know standard electrical wiring and
connection practices, are familiar with power supplies and are aware of the precautions
that are to be taken to avoid personal injury and damage to equipment.
To prevent ESD damage to the equipment take normal static precautions

for removing optical modules.
cables, and are aware of the precautions that are to be taken to avoid damage to the
Several tasks have to be completed. Some tasks are detailed in sub-tasks. Pay attention
to the safety notices and additional information that are given below.
Step 1 Create a backup file of the NCU database as described in “Backing Up the
Step 2 Turn off the user-supplied DC power source connected to the shelf power
supply by switching the associated power source circuit breaker to the OFF
position.
Step 3 To safeguard against inadvertent power restoration, follow either option:
• Save the circuit breaker OFF-position with adhesive tape.
Step 4 Attach a wrist strap to your wrist and insert the grounding wire into the ESD
jack on the right of the shelf. Refer to Figure 72 on p. 754 showing the ESD
jack.
Alternatively, you may attach the grounding wire to a bare metal surface on the
rack.
Figure 72: Example of an SH1HU Shelf Front View (SH1HU-HP/2DC)
Step 5 Remove the power cables from the shelf power supply following the
appropriate steps depending on the shelf type:
• If you replace an SH1HU-F/2DC shelf, refer to Step 6 through Step 14.
• If you replace an SH1HU-HP/2DC or an SH1HU-HP/E-TEMP/2DC shelf,
refer to Step 15 through Step 18.
• If you replace an SH1HU-R shelf, refer to Step 19 through Step 20.


WARNING
is applied to the power cord. Adhere the sub-steps above.
Ignoring this instructions may result in undesired operation,
SH1HU-F/2DC
Step 6 To remove the protective cover, use your thumb and slide the cover upwards if
possible. Otherwise, use your finger tips of the right hand and with some force,
pull the clipped cover towards you.
Step 7 Lay the cover aside for later use.
Step 8 Using the appropriate screwdriver (Phillips size 2), loosen the four screws on
the terminal block until they are free. Figure 73 illustrates the terminal block
and its screws with the transparent protective cover on top.
Figure 73: Power Supply of the SH1HU-F/2DC Shelf
Step 9 Lay the screws aside for later use.

Step 10 Take off the DC power cord wires.
Step 11 Lay the DC power cord aside for later use.
Step 12 Reinsert the terminal screws and tighten them using the appropriate
screwdriver.
Step 13 Clip the protective cover back onto the terminal block.
Step 14 Proceed with Step 23.
SH1HU-HP/2DC and SH1HU-HP/E-TEMP/2DC

Step 15 Using the appropriate screwdriver (flat-bladed 0.8 mm x 4 mm), loosen the
plug’s upper and lower captive screw until they are free. Figure 74 illustrates
the plug and its screw location.
Figure 74: Power Supply of the SH1HU-HP/2DC Shelf
Risk of electrical damage!

Always pull out the power plug by its strain relief, never by its cables.
Step 16 Pull on the strain relief to remove the plug.

Step 17 Lay the DC power cord aside for later use.
SH1HU-R
As illustrated in Figure 75, the SH1HU-R is a rear-power access shelf.
Figure 75: SH1HU-R Rear View
Step 19 Lift the power cord locking clamp to release the power cord. See Figure 76
showing the attached power cord locked by the power cord locking clamp.
Figure 76: Power Cord attached to the PSU/1HU-R-AC
Step 20 Remove the AC power cord device plug from the PSU appliance coupler on the
shelf rear side.
Step 21 Place the AC power cord aside for later use.
Step 22 Remove the PSUs from their shelf slots as follows:

Ensure that the power supply unit is fully discharged when
removed from the shelf. This is indicated by the power LED being
WARNING off.
A potential risk of injury from electric shock exists when the power supply
unit is removed from the shelf. Voltage may still be present inside the
PSU, even though the unit has no longer contact with the shelf. To avoid
the risk of electric shock, allow any residual electric charge in the unit to
dissipate. The unit has fully discharged as the power LED is off.
a) Pull on the PSU handle(s) to carefully slide the module straight out of the
slot while holding it.
b) Put the module onto a grounded surface or an antistatic mat and let it cool
down.
c) As soon as the module has cooled down, place it in the original static-
d) Lay it aside for later use.
Step 23 Remove all cables from the NCU and SCU:
c) Disconnect all Ethernet cables from the SCU and lay them aside.
Step 24 Remove the NCU and SCU from their shelf slots as follows:
Hot Surface!
removing it from the shelf slot. Put only cooled modules into the static-
CAUTION
protective package.
screws.
down.
e) Lay it aside for later use.
Step 25 To remove optical modules from the shelf, remove their optical cables first as
described from Step 10 through Step 13 in Removing an Optical Module.
Step 26 Consult another person safeguarding the shelf while loosening the rack
screws.
Only the four rack screws hold a shelf. As soon as the screws are completely free from
the rack mounting holes, the shelf has to be held to prevent it from dropping.
Step 27 Using a Phillips head or any other screwdriver appropriate, loosen the four rack
screws.
Step 28 Having the second person holding the shelf, remove the four rack screws.
Step 29 Lay the rack screws aside for later use.
Having removed the rack screws, the shelf cannot yet be removed from the rack. It is
still connected to the rack grounding contact.
Step 30 Carefully move the shelf towards you until you are able to easily reach the
shelf grounding terminals.
Step 31 Disconnect the grounding conductor assembled with a ring lug, a two-hole lug
or a Faston wire receptacle:
• If a ring lug or two-hole lug is assembled (Figure 77 on p. 758), refer to Step
32 through Step 36.
• If a Faston wire receptacle is assembled (Figure 78 on p. 758), refer to
Step 37.
Figure 77: Grounding Conductor Shown with Ring Lug and Two-hole Lug
Figure 78: Grounding Conductor with Faston Wire Receptacle
Grounding Conductor with Ring Lug or Two-hole Lug

Step 32 Using the wrench or box spanner, loosen and remove the nut(s) from the
grounding bolt(s).
Step 33 Lay the nut(s) aside for later use.
Step 34 Remove the washer(s) and the lock washer(s) and lay them aside for later use.
Step 35 Remove the grounding conductor and lay it aside for later use.
Grounding Conductor with Faston Wire Receptacle

Step 37 Pull the grounding conductor off the blade connector and lay the conductor
aside for later use.
Step 38 Completely remove the shelf from the rack and put it onto a grounded surface
or an antistatic mat and let it cool down.
Step 39 As soon as the shelf has cooled down, place it in the original static-protective
package to avoid ESD damage.
Step 40 Install the replacement shelf as described in “Installing Shelves” in the
ESD jack on the shelf or the rack and lay the grounding wire aside.
Step 42 If appropriate, return the defective shelf to ADVA Optical Networking for repair.
For details on returning shelves, refer to the “Equipment Return and Repair”
section in the Installation and Commissioning Manual.
If you have any problems that result in a deviation from the removal procedure
Replacing an SH7HU(-R), SHX9HU, or SH9HU Shelf
Replacing an SH7HU(-R), SHX9HU, or SH9HU

Shelf
This section provides instructions for replacing SH7HU, SH7HU-R, SHX9HU, and
SH9HU shelves:
Replacing a shelf is service affecting (SA).

Note
Before starting the procedure, ensure the following equipment and tools are available:
Required Equipment
• Replacement shelf of same type
• Replacement modules for any defective modules in the shelf
• Suitable grounded surface or an antistatic mat for placing the equipment
• Original shipping boxes including the static-protective packaging for returning the
equipment
• Labels to identify fibers
Required Tools
• Torx TX10 screwdriver to assist in loosening the knurled screws of the modules
• Screwdrivers for disconnecting the shelf power cable and the shelf
• Laptop computer
• Mini USB serial cable
• Fiber cleaning scope and kit
Additional Requirements
If replacing the master shelf,
• Back up the NCU database, as described in Backing Up the Database.
• Check alarms and collect the node support data files, as detailed in Generating a
Support Data File.
A summary of how to handle modules and fiber-optic cables is provided in Handling
Equipment.
Step 1 Shut off power to the shelf:

a) For DC power sources, open the circuit breaker or remove the fuse.
b) For AC power sources, unplug the power cord from the PSUs.
Step 3 Label and disconnect the fibers from the modules.
Step 4 Remove the modules and place them on an antistatic mat or in an antistatic
bag.
Step 5 Disconnect the shelf grounding cable (green-yellow) from the shelf.
Step 6 Remove the shelf.

shelf while another service person removes the rack screws.
Note
Step 7 Install the replacement shelf.

Step 8 Re-connect the shelf grounding cable (green-yellow) to the shelf.
Step 9 Install these modules in the same slots as in the previous shelf:
• PSUs
• SCU
• NCU (when replacing the master shelf)
Step 10 Connect the AC/DC power to the shelf.
Step 11 Switch on power to the shelf:
a) For DC sources, close the circuit breaker or install fuses.
b) For AC sources, plug in the power cord to the PSUs.
Step 12 Set the Shelf ID, as described in "Managing the Shelf ID" in the Installation
and Commissioning Manual.
Step 13 Install the remaining modules in the same slots as in the previous shelf.
Step 14 Clean the fibers and reconnect them to the same ports/modules as in the
previous shelf.
Step 15 The next step depends on whether the replacement shelf is a master shelf or a
main shelf:
a) When replacing a master shelf, proceed to Final Steps When Replacing a
Master Shelf.
b) When replacing a main shelf, proceed to Final Steps When Replacing a
Main Shelf.
Final Steps When Replacing a Master Shelf

Execute this procedure after replacing the master shelf, as outlined in Replacing an
SH7HU(-R), SHX9HU, or SH9HU Shelf.
Step 1 Since NCU is detected in this shelf for the first time, it starts with an auxiliary
database. Accept the auxiliary database:
a) Connect your laptop computer to the NCU using a serial connection, as
Operations Manual.
b) Log in to the NE and navigate to System Management > Software &
Database Control.
c) Press "2" to access the Database tab, then click Accept.

The NCU restarts and you will lose connection to the NE.
The NE is reachable within approximately five minutes. After three
consecutive beeps, the NCU MOD LED changes from blinking to solid
green. This indicates that the NCU has completed the restart and you can
log in.
d) Log on to the NE.
Step 2 Ensure the provisioning is correct.
Step 3 If the NE contains main shelves, re-connect fiber-optic jumpers to the SCU in
the replacement shelf.
Step 4 Set SCU ring interconnections:
a) Select one of the following:
• In NED, select , then navigate to General >

Controls.
• In Craft, navigate to System Management > System General
Settings, then select the Controls tab.
b) Toggle SCU Connections as follows: Linear > Ring > Linear, or Ring >
Linear > Ring.
Step 5 If the NE contains main shelves, ensure they are visible in the NED/Craft.
Step 6 Verify that services have been restored.
Step 7 Check for alarms.
Refer to the Alarm and Event List to resolve any alarms in the system.
Step 8 Return the defective shelf to ADVA Optical Networking. For details on
returning shelves, refer to the “Equipment Return and Repair” section in the
Final Steps When Replacing a Main Shelf

Execute this procedure after replacing the main shelf, as outlined in Replacing an SH7HU
(-R), SHX9HU, or SH9HU Shelf.
Step 1 Re-connect fiber-optic jumpers to the SCU in the replacement shelf.

Step 2 Ensure the main shelf is visible in the NED/Craft.
Step 3 If the SCU was replaced with the shelf, set SCU ring interconnections.
a) Select one of the following:
• In NED, select , then navigate to General >

Controls.
• In Craft, navigate to System Management > System General
Settings, then select the Controls tab.
b) Toggle SCU Connections as follows: Linear > Ring > Linear, or Ring >
Linear > Ring.
Step 4 Verify that services have been restored.

Step 5 Check for alarms.
Refer to the Alarm and Event List to resolve any alarms in the system.
Step 6 Return the defective shelf to ADVA Optical Networking. For details on
returning shelves, refer to the “Equipment Return and Repair” section in the
Replacing a 40CSM/2HU Shelf

This section provides the procedure of replacing a 40CSM/2HU shelf.
Unless otherwise specified below, the term 40CSM/2HU Shelf always refers to the
following shelf types:
• 40CSM/2HU-#D02-#D32 and 40CSM/2HU-#D34-#D64
• 40CSM/2HU-#19590-#19200
• 40CSM-FL/2HU-#19590-#19200
• 40CSM/2HU-#19595-#19205
• 40CSM-C80/2HU-#19590-#19200
• 40CSM-C80/2HU-#19595-#19205
• 40CSM/P-2HU-#19590-#19200-DM
Several tasks have to be completed. Some tasks are detailed in sub-tasks. Pay attention
to the safety notices and additional information that are given below.
Only Service Personnel are allowed to replace a 40CSM/2HU Shelf.

CAUTION
Replace a 40CSM/2HU Shelf only with a shelf type mentioned above.

Failure to do so could result in loss of safety approval for the system and
damage to equipment.
CAUTION
Class 1M laser radiation when open. Do not view directly with optical
instruments.
CAUTION
Risk of invisible laser radiation!

Invisible laser radiation may be emitted from the end of an unterminated
optical fiber connector or receptacle when the aperture interlocks are
defeated.
• Turn off any laser sources, before you disconnect, inspect, clean
and reconnect fiber optic cables.
CAUTION
• Never look directly into the end of an optical fiber cable or open
receptacle.
Looking directly at laser beams can cause permanent eye damage.
When performing the following procedure, wear an ESD wrist strap or

use a similar individual grounding device to prevent ESD damage to the
equipment.
Replacing a 40CSM/2HU Shelf is service affecting (SA).
Risk of damage to fiber-optic connectors.

Do not disconnect or re-connect fiber-optic cables exposed to optical output power. If the
optical output power is greater than 13dBm, it is recommended to always disable the
laser source before you disconnect or re-connect the optical fiber. If you ignore this, the
core of the fiber can be destroyed at high optical power levels.
Clean and inspect the fiber-optic connectors carefully before you re-connect them to the
optical ports.
Raman amplifiers are high-powered devices. Always set the Network Port on a Raman
amplifier to disabled before removing an optical cable. Failure to disable the network port
can result in optical connector damage.

shelf while another service person loosens/tightens the rack screws.
Note
For reattachment of the optical cables, note the current connections of

the cables to the ports on the optical modules.
Note
It is assumed that you are experienced in handling optical fibers, versed in cleaning
optical connectors, and are aware of the laser safety precautions as well as the ESD
precautions that should be taken to avoid damage to eyes and equipment.
Equipment Required
Before starting the procedure, ensure the following equipment are available:
• Replacement shelf of the same type packaged in the shipping box
• Original cardboard box with the original packaging material (styrofoam trays) for
saving the removed shelf
• Suitable grounded surface or an antistatic mat for placing the shelf
• Appropriate protective caps to cover unplugged fiber-optic connectors
• Appropriate blind plugs for inserting into the unused/unterminated optical receptacles
of the removed shelf
• Fiber-optic cleaning kit including hand-held fiber scope and/or video scope
• Optical power meter
• Torx screwdriver TX8 for removing the left and right most screws from the front panel
of the replacement shelf
• Phillips head screwdriver or any other appropriate screwdriver for the rack screws
Follow these steps to replace a 40CSM/2HU shelf.
Step 1 Read the installation or cabling plan to get information about:

• The shelf you are replacing
• The rack holding the shelf
• The position of the shelf within the rack
• The replacement shelf
Step 2 Find the location of the shelf you are replacing.
Step 3 Attach an ESD strap to your wrist and connect it to a grounding point on the
rack (if available) or to a bare metal surface on the rack.
Step 4 If mounted, remove the front cover from the shelf to be replaced. Lay the front
cover aside for reuse.
Step 5 Remove the IEEE 1394 interface cable from the interconnect port on the front
panel of the shelf. The power LED light turns off.
Step 6 Switch all laser sources off, before disconnecting the optical fibers.
Step 7 Remove all optical cables from the client and network ports of the
40CSM/2HU shelf. Do not damage the optical fibers or connectors. To remove
an individual optical fiber pair, complete these steps:
a) Identify the optical fiber pair connected to the port of the 40CSM/2HU
shelf. For easy identification, attach an identifying tag to the fiber pair.
b) Detach the connector at one end of the transmission fiber and cover it with
a protective cap.
c) Detach the connector at the other end of this fiber and cover it with a
protective cap.
d) Insert the appropriate blind plugs into the corresponding receptacles.
e) Repeat b) to d) for the reception fiber.
Step 8 Repeat Step 7 when removing each fiber pair.
Step 9 After taking off all optical fibers, remove the 40CSM/2HU shelf from the rack
as follows:
Risk of equipment damage!

Only the four rack screws hold a shelf. As soon as the screws are completely free from
the rack mounting holes, the shelf has to be held to prevent it from dropping.
a) Get an assistant to support the shelf while you loosen the rack screws.
b) Using an appropriate screwdriver, loosen the four rack screws.
c) While your assistant supports the shelf, remove the four rack screws and
lay them aside for later use.
d) Carefully move the shelf towards you and put it onto a grounded surface or
an antistatic mat.
Step 10 Remove the adaptor brackets and the fiber finger from the shelf and reinsert
the fixing screws into the thread holes.
Step 11 Repack the shelf using the original packaging material (styrofoam trays) and
place the unit box with the shelf, the adaptor brackets and the fiber finger in the
original cardboard box.
Step 12 Take the 40CSM/2HU replacement shelf out of its shipping box.
Remove it from the packaging material and put it onto a grounded surface or an
antistatic mat.
Step 13 Verify you have the proper shelf type. Check the shelf type label on the top for
identification.
Step 14 Inspect the replacement shelf visually for damage. If damaged, do not install
this shelf. Return it for repair.
Step 15 Fit the appropriate adaptor bracket pair and the fiber finger to the replacement
shelf as described in the Installation and Commissioning Manual.
Step 16 Mount the 40CSM/2HU replacement shelf in the rack as follows:
To complete this step, have a helper to hold the shelf in place while you
secure it to the bay.
Note
a) Lift the shelf into the bay and position it with the attached brackets in the
rack so that the bracket holes on each side are aligned with the rack
mounting holes.
b) Reinsert the four rack screws with the proper washers into the rack
mounting holes or the cage nuts.
c) Tighten the rack screws with an appropriate screwdriver.
Step 17 Plug the IEEE 1394 interface cable into the interconnect port on the front panel
of the shelf again.
Step 18 Check the power LED on the front panel.
The power LED should light up green. This indicates that DC power is supplied
to the replacement shelf and that it is functioning properly.
Step 19 Reconnect each fiber pair on the client and network side according to the
installation plan. Proceed as follows:
a) Select a fiber pair (according to your installation plan).
b) Make sure that the lasers are turned off before you begin the inspection.
c) Remove the protective caps and the blind plugs from the connectors, and
store them in a clean resealable container.
d) Inspect and clean the fiber-optic connectors at both ends of the fibers and
the corresponding receptacles before you make the connection.
e) Connect one end of the reception fiber to the corresponding port on the
replacement shelf and the other end to the appropriate port on the
equipment which is directly connected to this shelf.
f) Connect one end of the transmission fiber to the corresponding port on the
replacement shelf and the other end to the appropriate port on the
equipment that is connected to this shelf.
Step 20 Repeat Step 19 for each fiber pair to be connected.
Step 21 Detach the ESD strap from your wrist. Disconnect the cable from the
grounding point on the rack and lay it aside.
Step 22 Remount the 40CSM/2HU front cover to the replacement shelf.
Step 23 Turn on the lasers.
Step 24 Store unused protective caps and blind plugs in resealable containers for later
use.
Step 25 If appropriate, return the defective shelf to ADVA Optical Networking for repair.
For details on returning shelves, refer to the “Equipment Return and Repair”
section in the Installation and Commissioning Manual.
Should you have any difficulty performing this procedure, contact the ADVA Optical
Networking Technical Services.
Removing and Mounting Front Covers

This chapter describes how to remove and mount the front cover of a 7HU or 9HU shelf
and 40CSM/2HU shelf.
“Removing an SH7HU, SH9HU, or SHX9HU Front Cover” on p. 768
“Mounting an SH7HU, SH9HU, or SHX9HU Front Cover” on p. 769
“Removing the 40CSM/2HU Front Cover” on p. 770
“Mounting the 40CSM/2HU Front Cover” on p. 771
Removing an SH7HU, SH9HU, or SHX9HU Front Cover

Follow this procedure to remove the front cover of an SH7HU, SH9HU, or SHX9HU
shelf.

in mounting a front cover.
Equipment Required
An ESD-preventive wrist strap or other personal grounding device should be available
before beginning the removal procedure.
rack.
Step 2 Using your forefingers, simultaneously push in the latches on both sides of the
front cover (see Figure 79 on p. 769) and pull the cover toward you at the same
time.
Figure 79: Removing the Front Cover
Step 3 Take off the cover and lay it aside.

wire aside.
Mounting an SH7HU, SH9HU, or SHX9HU Front Cover

Follow this procedure to mount the front cover to an SH7HU, SH9HU, or SHX9HU shelf.

in mounting a front cover.
Equipment Required
An ESD-preventive wrist strap or other personal grounding device should be available
before beginning the mounting procedure.
rack.
Step 2 With both hands, hold the shorter sides of the front cover, its curvature upward.
Pay attention to the optical cables when positioning the front cover. Ensure that no
optical cables are sandwiched between the cover and the front of the shelf. Failure to do
so can result in damage to the fiber.
Step 3 Position the cover on the front of the shelf so that the latches and fixing
brackets on either side are in alignment, as shown in Figure 80.
Figure 80: Positioning the Front Cover
Step 4 Push the cover toward the shelf being careful not to pinch a fiber. Make sure
the latches snap into place.
wire aside.
Removing the 40CSM/2HU Front Cover

Follow this procedure to remove the front cover of a 40CSM/2HU shelf.
Take normal static precautions when removing the front cover. Failure to
follow ESD safety precautions can cause damage to the equipment.
Equipment and Tools Required

• relevant 40CSM/2HU shelf with mounted front cover
grounding point to a bare metal surface onto the rack.
Step 2 Take the front cover by holding it on the shorter sides and pull the cover
towards you.
Step 3 Take off the cover and lay it aside.
ESD grounding point on the rack and lay the grounding wire aside.
Mounting the 40CSM/2HU Front Cover

The 40CSM/2HU shelf will be delivered with a front cover to protect the fiber optic
connectors against external influences and prevents the fibers from being pulled out
inadvertently. If not enclosed in the shelf delivery, the front cover has to be ordered
separately.
Follow this procedure to mount the front cover to a 40CSM/2HU shelf, unless pre-
installed.
Take normal static precautions when mounting the front cover. Failure to
follow ESD safety precautions can cause damage to the equipment.
Equipment and Tools Required

• relevant 40CSM/2HU shelf
• Front cover suitable for 40CSM/2HU shelf
Following tools are also required, if no bolts are mounted to the front panel of the shelf:
• Torx screwdriver TX8 for removing the left and right most screws from the front panel
• 4 x hexagon head bolts included in the accessory box
• Hexagon wrench (wrench size of 7 mm) for tightening the bolts
grounding point to a bare metal surface onto the rack.
Step 2 Check whether your shelf is equipped with bolts on the left and right most side
of the front panel. If it is not equipped with bolts, continue with Step 3. If your
shelf is equipped with bolts go ahead with Step 4.
Step 3 If no bolts are mounted to your shelf, do as follows:
a) Using a Torx screwdriver TX8, remove the two left and right most screws
from the front panel and lay them aside.
b) Take the bolts out of the accessory box delivered with the front cover,
insert them into the holes and tighten the bolts using a wrench.
Step 4 Take the front cover by holding it on the shorter sides.
Pay attention to the optical cables when positioning the front cover. Ensure that no
optical cables are sandwiched between the cover and the front of the shelf. Failure to do
so can result in damage to the fiber.
Step 5 Position the front cover of the shelf so that the magnet pins are aligned with the
bolts as shown in Figure 81.
The magnet pins are made by strong magnets for holding the front cover.
Figure 81: Mounting a Front Cover to a 40CSM/2HU Shelf
ESD grounding point on the rack and lay the grounding wire aside.
Removing and Inserting a Dummy Module

This section describes how to remove and insert a dummy module.
“Inserting a Dummy Module” on p. 773
“Removing a Dummy Module” on p. 775
Inserting a Dummy Module

This description is common and independent of dummy module types. The term dummy
module always refers to both DM/5HU and DM/2HU5 module types. For specific
information about dummy modules, refer to the Hardware Description.

CAUTION
Equipment Required
• Appropriate dummy module packaged in the shipping box
Insertion Procedure
Follow these steps to insert a dummy module into a slot.

precautions in inserting dummy module.
It is assumed that you are familiar with optical modules, and are aware of the precautions
that should be taken to avoid damage to the equipment.
rack.
Step 2 Find the empty slot within the shelf which is to be populated with the dummy
module.
Step 3 Take the dummy module out of the shipping box and inspect it visually for
damage. If necessary, use canned, dry, oil-free compressed air to blow off any
possible dust particles.

Otherwise EMC compliance can not be achieved.
Insert the dummy module into the empty slot as follows:

a) Hold the module by both screws as shown in Figure 82 or by the faceplate.
Figure 82: Inserting a Dummy Module into a Shelf Slot
into the slot while guiding the upper and lower edges of the module in the
tracks.
c) Ensure that the module is completely inserted into the slot. The module is
properly and completely inserted when its faceplate is flush with the
faceplates of the adjacent modules and the shelf panels.
Step 4 Secure the module in place as follows:
wire aside.
Step 6 Store the empty shipping box in a safe place for future use.
Removing a Dummy Module

This description is common and independent of dummy module types. The term dummy
module always refers to both DM/5HU and DM/2HU5 module types. For specific
information about dummy modules, refer to the Hardware Description.

CAUTION
Equipment Required
• Original shipping box for storing the removed dummy module
Removal Procedure
Follow these steps to remove a dummy module from a slot.

precautions in inserting dummy module.
It is assumed that you are familiar with optical modules, and are aware of the precautions
that should be taken to avoid damage to the equipment.
rack.
Step 2 Determine the physical location of the respective dummy module within the
shelf.
Step 3 Using your fingers or a Torx screwdriver TX10, turn the two knurled screws in a
counter-clockwise direction until they are removed from threaded holes
completely.
Step 4 Firmly pull on the screws and carefully slide the module straight out of the slot,
while holding it by the screws.
Figure 83: Removing a Dummy Module from a Shelf Slot
Never reach into a vacant shelf slot. Contact with the adjacent optical modules or the
Step 5 Place the dummy module in the shipping box.

Step 6 Insert an optical module as described in “Replacing an Optical Module” on
p. 656.
wire aside.
Step 8 Store the box with the dummy module in a safe place for future use.
Chapter 18
Generating a Support Data File

This chapter contains instructions on how to generate and export a support data file
(supportdata.tgz).
The file can be generated and exported using one of these interfaces:
• NED, as detailed in “Collecting Support Data using NED” on p. 778.
• Shell, as detailed in “Collecting Support Data using Shell” on p. 779.
The file contains the following information:
• Equipment Inventory
• Module Configuration
• Linux Configuration
• Software Processes
• File System
• Logs
o
Event
o
Database (DB) Change
• Management Interfaces
• Active Network Connections
• IP Configuration
• IP Routing Data
• Performance Monitoring Data
When generation is complete, this file is stored in the Active NCU RAM and can be
exported for detailed offline troubleshooting.
Collecting Support Data using NED
Collecting Support Data using NED

This section addresses collection of support data when the NE can be accessed by
NED.
Step 1 Select .
Step 2 In the Navigation Tree, select Tools.
Step 3 In the Data for Technical Support Analysis blade, select up to 10 modules to
collect PM data for, if desired.
Step 4 In the Data for Technical Support Analysis blade, click .
Once you click , the label changes to In Progress. The data

collection process may take up to 30 minutes to complete.
Generation of the supportdata.tgz file is complete when the button is

accessible again.
Do not make any changes to the node while the data collection is in
progress.
Note

Step 6 Set Location to Active NCU RAM to view the supportdata.tgz file.
Step 7 Export the supportdata.tgz file, as described in “Uploading Files from the NCU”
on p. 633.
Note \ / ` $ ! " ' * ? ; | > \t
Collecting Support Data using Shell

When the NE is not accessible using NED, support data may be collected using Shell.
Shell is accessed through the Craft Console.
Collection of support data using Shell allows additional data to be collected, which may
be needed for the problem under investigation. These options include:
• Add binary database files: Enables collection of binary database files which are used
by ADVA Optical Networking for troubleshooting.
• Add performance monitoring data: Enables collection of the past three days'
performance monitoring values (PMs) for up to 10 modules in the NE. Contact ADVA
Optical Networking Technical Servicesto determine if this information needs to be
collected.
• Add OSPF data: Enables collection of OSPF data.
• TCP dump of ECC: Enables collection of Transmission Control Protocol (TCP) data
for all active Embedded Communication Channels (ECC) in the NE. Basic TCP
information is collected when this option is not selected.
• TCP dump simultaneously: Enables simultaneous collection of TCP information for
the active ECC. TCP information is collected sequentially for the active ECC when
this option is not selected.
Step 1 Select External Applications > Shell from the Craft Console main menu to
access the shell command line.
Step 2 Set user to ‘root’ and enter the corresponding password.
[ADMIN@NE_NAME ADMIN]$ su root
Password:
[root@NE_NAME root]#
Step 3 Start the support-data collection tool:
[root@NE_NAME root]# fsp_tool collectNcuInfo
This window allows collection of additional information. Select options as

needed for troubleshooting.
• Navigate with the arrow or TAB keys.
• Toggle option selection with the SPACEBAR.
• Select with the ENTER key.
Step 4 After the desired options are selected, select OK.
The window to configure “tcpdump” parameters is displayed:
Usually, no changes are necessary. However, if support-data collection

generates an error, increase these values.
Step 5 Select Apply.
• If option “b” was not selected in Step 4, support-data collection is started.
Proceed to Step 7.
• If option “b” was selected, the following window appears:
This window displays all active modules. However, a maximum of 10 modules

may be selected.
Step 6 Select up to 10 modules for performance monitoring data collection and select
OK.
When the command prompt returns, support-data collection is complete.

Step 7 If an error message appears,
a) Repeat Step 3 and Step 4 of this procedure.
b) In the "configure tcpdump parameters" window, increase the ‘max. time’
and ‘max. size’ values.
c) Select <Apply> and continue with Step 5.
Step 8 After the support data collection has completed, press CTRL+D twice to return
to the Craft Console main menu.
Your user account privilege is automatically restored to your log on level (e.g.
ADMIN).
Step 9 To verify the support data was collected, select System Management >
Software & Database Control, 'File Storage’ tab and ensure Location is set
to RDISK . Look for 'supportdata.tgz'.
Note \ / ` $ ! " ' * ? ; | > \t
Step 10 To export the supportdata.tgz file, select the file (highlight and press
Enter), then select [Upload].
+------------------------------ RDISK - Upload -------------------------------+
|| 1 File Storage | 2 Database | 3 NCU Update | 4 FWP Update | |
|| +----------------------------------------------------------+|
|| Protocol: [FTP] ||
|| Source IP Address: [System ] ||
|| IP Address: [192.168. 1. 1 ] ||
|| Directory Path Name: [C:/Software/ ] ||
|| File Name: NE_NAME.supportdata.tgz ||
|| ||
|| User Name: [ftpuser ] ||
|| Password: [************* ] ||
|| ||
|| [ Cancel ] [ Upload ] ||
|| ||
|+---------------------------------------------------------------------------+|
Step 11 Ensure the remote server has an FTP server configured and is running during
the file export.
Step 12 Enter the settings for the remote server:
a) Select the Protocol.
c) Enter the IP Address of the remote server.
d) Specify the Directory Path Name on the remote server, if needed.
e) Enter the User Name and Password to access the remote server.
Step 13 Select Upload.

An informational window appears when the file is successfully transferred to
the remote server. Confirm with OK.
The RDISK-Upload window displays “State: 100% Complete”.
Appendix A
Alarm and Event List

This appendix lists the standing and transient conditions which appear as alarms and
events in the FSP 3000R7. These conditions report issues and events on the system.
It contains these sections:
“Alarm and Event Nomenclature” on p. 784, which describes how conditions are indicated
in this chapter.
“Standing Conditions” on p. 785, which lists alarms remaining in existence for a period of
time and offers the probable cause with suggested corrective actions for each alarm.
“Transient Conditions” on p. 1076, which lists events reported by means of an
autonomous message and offers the probable cause with suggested corrective actions
for each event.
“Database Change Events” on p. 1131, which lists database changes reported as
autonomous messages.
Refer to the “Management” section of the System Description for information about
conditions and alarms.
Alarm and Event Nomenclature
Alarm and Event Nomenclature

Each alarm and event in this chapter is identified by two names.
• The first name is the TL1 keyword.
• The second name, specified in parentheses, is the user interface name.
For example, the standing condition “CALC-TOP (Topology Calculation)”:
l CALC-TOP = TL1 keyword
l Topology Calculation = user interface name
The TL1 keyword and user interface name may match. In this case, the
keyword and user interface name are specified in both locations (for
example, RDI (RDI)).
Note
Standing Conditions
Standing Conditions
Standing conditions are persistent events which exist for a period of time. Each standing
condition has a notification code. The notification code determines whether the condition
is an alarm or event. Alarms are reported by the network element as autonomous
messages. Events are not sent as autonomous message and must be requested. The
notification code also indicates the severity of the condition.
Table 112: Notification

Codes/Severities
Severity Definition
NR not reported
NA not alarmed
MN minor
MJ major
CR critical
Standing conditions are reported when the associated issue occurs after a specified time
delay and remain active until the issue clears and the associated time delay expires.
When the issue clears and the timer expires, an autonomous message of the same type
is reported which has “CL” or "CLEAR" to indicate that the specified condition is no longer
present.
Please refer to the section, “Alarm and Event Nomenclature” on p. 784

for details about the two names identifying each standing condition.
Note
This section does not address alarms or events marked in the MIB as
“deprecated” or “not implemented”.
Note
Standing conditions on SC ports (NCU, OSC, UTM) are reported

immediately and do not have timers to delay the reporting.
Standing conditions on other equipment may not be reported due to other
standing conditions on the equipment.
Note Please refer to the System Description for more information. The
Management Data Guide lists the alarm suppression rules defined by the
internal Fault Cause Presistency Filter (FCPF) for each module.
Standing Conditions
ACP-APS-UAV (APS Channel
Unavailable)
The corresponding SNMP name for this condition is “acpChannelUnAvail”.
Table 113: ACP-APS-UAV (Standing Condition)
AIDTYPE Default Probable Cause Suggested Corrective Action

Severity
MOD MN The APS channel is 1 Change APS channel to an

already being used. For unused channel.
example, the 2 Change protection mode to
APS channel could be unidirectional.
used by Client Channel
Card Protection
(CCCP).
Protection switching
will still be performed
but only for one
direction.
ACP-LINK (APS Channel Link Loss)

The corresponding SNMP name for this condition is “acpLinkLoss”.
Table 114: ACP-LINK (Standing Condition)

Severity
MOD MN Loss of 1 Provision the correct ACP.

communication 2 Install and provision the partner
with the module. If the ACP was deleted
provisioned APS (indicated by ACP-RMVD (APS
Channel Partner Partner Deleted)), re-provision the
(ACP). module.
3 Set protection mode to unidirectional.
4 Correct inter-shelf communication
issues.
Standing Conditions
ACP-RMVD (APS Partner Deleted)

The corresponding SNMP name for this condition is “acpPartnerDeleted”.
Table 115: ACP-RMVD (Standing Condition)
AIDTYPE Default Probable Suggested Corrective Action

Severity Cause
MOD MN The APS 1 Provision the correct ACP.

Channel 2 Install and provision the partner
Partner (ACP) module.
module has
3 If the ACP was deleted accidentally,
been deleted.
re-provision it.
4 Set the ACP to None and protection
mode to unidirectional.
ACP-UAS (APS Partner Unassigned)

The corresponding SNMP name for this condition is “acpPartnerUnassigned”.
Table 116: ACP-UAS (Standing Condition)

Severity
MOD MN No APS Channel Partner 1 Assign ACP.

(ACP) is assigned and 2 Install and provision ACP.
protection mode is
3 Set protection mode to
bidirectional.
unidirectional.
AIS-L (Line/MS-AIS)
The corresponding SNMP name for this condition is “alarmIndicationSignalLine”.
Table 117: AIS-L (Standing Condition)
AIDTYPE Default Probable Cause Suggested Corrective

Severity Action
CH NR The port is receiving This condition is informative

an Alarm Indication and requires no corrective
Signal (at Line or action. Corrective action
Multiplex Section needs to be taken in response
level). to the signal failure reported
upstream.
AIS-LP (Path-LO AIS)

The corresponding SNMP name for this condition is
“alarmIndicationSignalLowerOrderPath”.
Standing Conditions
Table 118: AIS-LP (Standing Condition)

Severity
VC3 NR The port is receiving This condition is informative and

an Alarm Indication requires no corrective action.
Signal (in the low- Corrective action needs to be
order path). taken in response to the signal
failure reported upstream.
AIS-ODU (ODU-AIS)
The corresponding SNMP name for this condition is “alarmIndicationSignalOdu”.
Table 119: AIS-ODU (Standing Condition)

Severity
CH NR The port is This condition is informative and

receiving an Alarm requires no corrective action.
Indication Signal (in Corrective action needs to be taken
the ODU layer). in response to the signal failure
reported upstream.
This condition is superseded by
AIS-OTU if the failure occurs within
the current OTU trail.
AIS-OPU (OPU-AIS)
The corresponding SNMP name for this condition is “alarmIndicationSignalOpu”.
Table 120: AIS-OPU (Standing Condition)

Severity
CH NR The port is This condition is informative and

receiving an Alarm requires no corrective action.
Indication Signal Corrective action needs to be
(in the OPU layer). taken in response to the signal
This condition typically occurs
due to a failure of the client signal
at the far-end equipment.
Standing Conditions
AIS-OTU (OTU-AIS)
The corresponding SNMP name for this condition is “alarmIndicationSignalOtu”.
Table 121: AIS-OTU (Standing Condition)

Severity
CH NR The port is receiving This condition is informative and

Signal (at the Corrective action needs to be
OTU layer). taken in response to the signal
AIS-P (Path-AIS)
“alarmIndicationSignalHigherOrderPath”.
Table 122: AIS-P (Standing Condition)
AIDTYPE Default Probable Cause Suggested

Severity Corrective Action
STS1, NA The port is receiving an Alarm This condition is

STS3C, Indication Signal (in the informative and
STS24C, transport layer). requires no corrective
STS48C, action. Corrective
VC4, action needs to be
VC4C8, taken in response to
VC4C16 the signal failure
reported upstream.
AIS-TCMA (TCM_A-AIS)
The corresponding SNMP name for this condition is “alarmIndicationSignalOduTcmA”.
Table 123: AIS-TCMA (Standing Condition)

Severity Action
CH NR The port is receiving an This condition is

Alarm Indication Signal (in informative and requires
the TCM A layer). no corrective action.
Corrective action needs
to be taken in response
to the signal failure
reported upstream.
AIS-TCMB (TCM_B-AIS)
The corresponding SNMP name for this condition is “alarmIndicationSignalOduTcmB”.
Standing Conditions
Table 124: AIS-TCMB (Standing Condition)

Severity Action

Alarm Indication Signal (in informative and requires
the TCM B layer). no corrective action.
Corrective action needs
to be taken in response
to the signal failure
reported upstream.
AIS-TCMC (TCM_C-AIS)
The corresponding SNMP name for this condition is “alarmIndicationSignalOduTcmC”.
Table 125: AIS-TCMC (Standing Condition)

Severity Action

Alarm Indication Signal (in informative and requires no
the TCM C layer). corrective action.
Corrective action needs to
be taken in response to the
signal failure reported
upstream.
AIS-VF (FEND Client Fail-AIS)

The corresponding SNMP name for this condition is “virtualChannelAis”.
Table 126: AIS-VF (Standing Condition)

Severity
CH NR The port is receiving This condition is informative and

Signal (in the client Corrective action needs to be
facility layer). taken in response to the signal
Standing Conditions
AMPANR (Amplifier-Tx Abnormal)

The corresponding SNMP name for this condition is “amplifierAbnormal”.
Table 127: AMPANR (Standing Condition)

Severity
OM MJ The amplifier output 1 Verify that the correct fibers are

power is outside the connected to the amplifiers ports.
limits consistent If needed, correct any fibering
with the provisioned issues.
gain. 2 Verify that the amplifier is
provisioned correctly based upon
the optical fiber span. If needed,
correct any provisioning errors.
3 Verify that the span length, fiber
type and loss conform to the
engineering limits and the fiber
span properties. If the span is
outside the expected engineering
limits or specifications, correct
the fiber span issues.
4 Replace the amplifier module.
AMPOUT-FAIL (Output Current Draw

High)
The corresponding SNMP name for this condition is “outputCurrentDrawHigh”.
Table 128: AMPOUT-FAIL (Standing Condition)

Severity
MOD CR • The installed 1 Replace the failed power unit.

equipment requires 2 Remove the last installed
more output current module.
than the power unit
3 Verify that the equipment in the
can support.
shelf does not exceed the
• The module is power available.
failing.
Standing Conditions
APR (Power Reduction-Auto)

The corresponding SNMP name for this condition is “automaticPowerReduction”.
Table 129: APR (Standing Condition)

Severity Action
OM MN • Fiber break. This condition is informative

• The optical output and requires no corrective
power has been action. Corrective action
reduced to comply needs to be taken in response
with laser safety to the reported signal failure.
limits.
Standing Conditions
APRLMT (Power Reduction-Limit)

“automaticPowerReductionForEyeSafety”.
Table 130: APRLMT (Standing Condition)

Severity
OM MJ • Fiber break 1 Repair network fiber break.

• Far end equipment 2 Replace failed module or plug.
failure. 3 Clean fiber connections.
• Excessive fiber loss. Launching into a span with an amplifier.
• Improper equipment At the local site:
connection or 4 Verify that the amplifier is installed,
equipment failure. provisioned and operating normally.
5 Verify that the OSCM is installed,
provisioned and operating normally.
6 Verify that the OSCM network output is
connected to the amplifier client port input.
7 Verify that the correct network fiber is
connected to the amplifier network output.
8 If needed, correct any fibering issues.
At the next site (other end of the span):
9 Verify that the amplifier is installed,
10 Verify that the OSCM is installed,
11 Verify that the OSCM network output is
connected to the amplifier client port input.
12 Correct any installation, provisioning or
fibering issues.
13 Verify that the OSC arriving at the amplifier
network port is within the specified power
range.
14 If the OSC is outside the specified range, this
indicates the span exceeds the maximum
allowable length. Address the span loss or
length issue as needed.
Standing Conditions
Table 130: APRLMT (Standing Condition)

Severity
Launching into a span with a Raman amplifer.

At the local site:
2 Verify that the Raman amplifier is installed,
3 Verify that the amplifier network output is
connected to Raman amplifier upgrade input.
4 Verify that the correct network fiber is
connected to the Raman amplifier network
output.
5 If needed, correct any fibering issues.
At the next site (other end of the span):
6 Verify that the Raman amplifier is installed,
8 Correct any installation, provisioning or
fibering issues.
9 If the signal is outside the specified range,
this indicates a problem in the span or that
the span exceeds the maximum allowable
length. Address the span loss or length issue
as needed.
APS-CONF (Protection Mismatch)

The corresponding SNMP name for this condition is “apsConfigMismatch”.
Table 131: APS-CONF (Standing Condition)

Severity
CH MJ A mismatch exists Verify the provisioned attributes

between the (APS-TYPE, TYPE, MECH, DIRN,
provisioned RVRTV) of the protection groups at
attributes of the both the near and far ends supporting
peer protection the facility reporting this condition
group entities at are set to equal values.
the near and far
ends (i.e. an APS
mode mismatch
condition has been
detected).
Standing Conditions
APS-PROT (Protection ProtocolFail)

The corresponding SNMP name for this condition is “apsProtocolFailure”.
Table 132: APS-PROT (Standing Condition)

Severity Action
CH MN • A protection switching Verify the provisioned

byte failure has been attributes (APS-TYPE,
detected (the received TYPE, MECH, DIRN,
code is either RVRTV) of the protection
inconsistent from frame groups at both the near and
to frame or contains an far ends supporting the
invalid value). facility reporting this
• A channel mismatch condition are set to equal
condition has been values.
detected (the channel
number received does
not match the channel
number transmitted).
Standing Conditions
ASELOW (Pump Shutdown (ASE

low))
The corresponding SNMP name for this condition is “aseLow”.
Table 133: ASELOW (Standing Condition)

Severity
OM: CR The level of ASE 1 Verify that the correct fiber is

RAMAN (optical background coupled to the network side input
signal, or optical port of the amplifier module, and
noise level) detected correct any cabling issues if they
in the transmission exist.
line is below the 2 Verify that the optical signal
minimum level arriving at the network port
expected by the complies with the specified power
amplifier module. level range for the module. Verify
This can be caused that the optical amplifier at the far-
by a failure, low end of the transmission span is
output power level, in-service and operating normally,
or laser safety without any active laser safety
shutdown operation condition or shutdown in effect. If
of the far-end the far-end amplifier is operating
amplifier, excessive normally and within acceptable
span length or output power levels, but the
excessive span received power is too low, this
loss. indicates a problem in the
transmission space or that the
span exceeds the maximum
allowable length. Address the
span loss or length issue as
needed. If the far-end amplifier is
not operating normally and within
specified limits, address the far-
end issues first.
3 Perform the ASE table build
process on the amplifier module
(e.g. the OPR-ASETBL-OM
command in TL1).
Standing Conditions
ASETAB-FAIL__ASELOW (ASE Table-

Fail (ASE Low))
The corresponding SNMP name for this condition is “aseTableGenFailLow”.
Table 134: ASETAB-FAIL__ASELOW (Standing Condition)

Severity
OM: MN The level of ASE 1 Verify that the correct fiber is

RAMAN (optical background coupled to the network side input
signal, or optical port of the amplifier module, and
noise level) correct any cabling issues if they
detected in the exist.
transmission line 2 Verify that the optical signal
during the ASE arriving at the network port
table build process complies with the specified
is below the power level range for the module.
minimum level Verify that the optical amplifier at
expected by the the far-end of the transmission
amplifier module. span is in-service and operating
This can be caused normally, without any active
by a failure, low laser safety condition or
output power level, shutdown in effect. If the far-end
or laser safety amplifier is operating normally
shutdown operation and within acceptable output
of the far-end power levels, but the received
amplifier, excessive power is too low, this indicates a
span length or problem in the transmission
excessive span space or that the span exceeds
loss. the maximum allowable length.
Address the span loss or length
issue as needed. If the far-end
amplifier is not operating
normally and within specified
limits, address the far-end issues
first.
process on the amplifier module
(e.g. the OPR-ASETBL-OM
command in TL1).
Standing Conditions
ASETAB-FAIL__BR (ASE Table-Fail

(BR))
“aseTableGenFailHighBackreflection”.
Table 135: ASETAB-FAIL__BR (Standing Condition)

Severity
OM: MN The level of back- 1 Verify that the correct fiber is coupled to the network
RAMAN reflection detected in the side input port of the amplifier module, and correct
transmission line exceeds any cabling issues if they exist.
the maximum allowable 2 Inspect and clean the optical fiber connector at the
level. network side receive port of the module and the
This can be caused by a corresponding connector on the fiber jumper or
damaged or dirty transmission line. If the connector on the module is
connector or a break in the damaged, replace the amplifier module. If the
fiber within the connector on the fiber line is damaged, replace the
transmission line. fiber jumper cable or the connector, as appropriate.
3 Proceeding back along the incoming network signal
fiber path, inspect each of the fiber connectors along
the path and clean or replace them as needed if they
are dirty or damaged. While disconnected, test each
optical segment to ensure it is not broken (i.e. verify
the optical continuity or the segment and that the
loss of the segment is within expected limits).
Replace any segment which is found to contain a
break or to exhibit excessive loss. Also verify that
the fiber in the segment is of the correct type, and
replace any segments containing an incorrect fiber
type.
4 Perform the ASE table build process on the amplifier
module (e.g. the OPR-ASETBL-OM command in
TL1).
Standing Conditions
ASETAB-FAIL__OSC (ASE Table-Fail

(OSC))
The corresponding SNMP name for this condition is “aseTableGenFailOscMissing”.
Table 136: ASETAB-FAIL__OSC (Standing Condition)

Severity
OM: MN The incoming network 1 Verify that the correct fiber is coupled to the
RAMAN side optical fiber does not network side input port of the amplifier module,
contain an Optical and correct any cabling issues if they exist.
Supervisory Channel 2 Verify that the optical signal arriving at the network
signal which is within the port complies with the specified power level range
required optical power for the module. Verify that the optical amplifier at
level range. the far-end of the transmission span is in-service
and operating normally, without any active laser
safety condition or shutdown in effect, that the
corresponding OSC facility is provisioned, in-
service and operating without error, and that the
OSC signal is correctly connected to the
transmission line. If the far-end amplifier and OSC
is operating normally and within acceptable output
power levels, but the received power is too low,
this indicates a problem in the transmission space
or that the span exceeds the maximum allowable
length. Address the span loss or length issue as
needed. If the far-end amplifier is not operating
normally and within specified limits, address the
far-end issues first.
3 Inspect the optical connector on the incoming
transmission fiber and the network side receive
port of the amplifier module and clean them if
needed. If the fiber connector on the cable is
damaged, replace the connector or fiber cable, as
appropriate. If the connector on the module is
damaged, replace the module.
4 Perform the ASE table build process on the
amplifier module (e.g. the OPR-ASETBL-OM
command in TL1).
Standing Conditions
ASETAB-FAIL__PILOT (ASE Table-

Fail (Pilot))
The corresponding SNMP name for this condition is “aseTableGenFailPilot”.
Table 137: ASETAB-FAIL__PILOT (Standing Condition)

Severity
OM: MN The pilot signal used 1 Verify that the correct fiber is
RAMAN to provide automatic coupled to the input port of the
connection detection module, and correct any
and verification cabling issues if they exist.
cannot be detected 2 Verify that the optical signal
and the ASE table arriving at the input port
also cannot be complies with the specified
generated. This may power level range for the
be caused by: module. Verify that the
• PILOT is missing equipment at the far-end of the
• PILOT is too high cable is in-service and
operating normally, without
• FEND BWD
any active laser safety
Raman is on but
condition or shutdown in
not in
effect. If the far-end equipment
"FWDASE-
is operating normally and
PILOT" mode.
within acceptable output power
levels, this indicates a problem
in the optical jumper cable.
Replace the optical jumper
cable with an appropriate style.
If the far-end equipment is not
operating normally and within
specified limits, address the
far-end issues first.
3 If the pilot signal is too high,
verify that the span is long
enough.
4 Verify that the FEND BWD
Raman is operating normally
using the “FWDASE-PILOT”
mode. If it does not use this
pilot mode, set it.
process.
Standing Conditions
ASETAB-FAIL__SIG (ASE Table-Fail

(Signal))
The corresponding SNMP name for this condition is “aseTableGenFailSignalinput”.
Table 138: ASETAB-FAIL__SIG (Standing Condition)

Severity
OM: MN This condition is raised if: 1 Verify that the correct fiber is coupled
RAMAN • There is an excessive level to the network side input port of the
of back-reflection from fiber amplifier, and correct any cabling
splices or fiber connectors issues.
within the first few 2 Inspect and clean the optical fiber
kilometers of the fiber connector at the network side Rx port
connected to the Raman of the module and the corresponding
amplifier. connector on the fiber jumper or
• Data channels are present transmission line. If the connector on
on the Rx fiber during the the module is damaged, replace the
ASE Table build process. amplifier module. If the connector on
No data channels can be the fiber line is damaged, replace the
present during this fiber jumper cable or the connector, as
operation. appropriate.
• There is excessive loss 3 Ensure no data channels are present

within the few kilometers of on the Rx fiber.
the fiber connected to the 4 Proceeding back along the incoming
Raman amplifier. network signal fiber path, inspect each
• The fiber type selected for of the fiber connectors along the path
the Raman amplifier does and clean or replace them as needed, if
not match the fiber actually they are dirty or damaged. While
connected. disconnected, test each optical
segment to ensure it is not broken (i.e.
verify the optical continuity of the
segment and that the loss of the
segment is within expected limits).
Replace any segment which is found
to contain a break or to exhibit
excessive loss. Also verify that the
fiber in the segment is of the correct
type, and replace any segments
containing an incorrect fiber type.
5 Perform the ASE table build operation.
6 If the condition persists, contact
ADVA Optical Networking Technical
Services.
Standing Conditions
ASETAB-NA (ASE Table-Not

Available)
The corresponding SNMP name for this condition is “aseTableNotAvailable”.
Table 139: ASETAB-NA (Standing Condition)

Severity
OM: CR The amplifier module Perform the ASE table build

RAMAN has not had the ASE process on the amplifier module
table build process (e.g. the OPR-ASETBL-OM
performed successfully. command in TL1).
ASETABUILD (ASE Table-Build)

The table below lists causes and corrective actions for the “amplified spontaneous
emissions (ASE) table build in progress” (ASETABUILD) standing condition.
The corresponding SNMP name for this condition is “aseTableGenProgress”.
Table 140: ASETABUILD (Standing Condition)

Severity
OM: NA The amplifier module This condition is informative and

RAMAN ASE table build requires no corrective action.
process is in
progress.
AUTHPW-MIS (Authentication
Required)
“encryptionPortAuthPasswdMissing”.
Table 141: AUTHPW-MIS (Standing Condition)

Severity Cause
CH MN An Cryptographic services require that both

authentication ends of a circuit be provisioned with the
key is not same secret key value (the authentication
provisioned. key).
1 Provision the same authentication key
value at both ends of the circuit.
2 Manually initiate negotiation of the
session key to activate encrypted
service.
Standing Conditions
AVLNDP-RESTRICTED (Network
Paths-Restricted)
The corresponding SNMP name for this condition is “networkPathRestricted”.
Table 142: AVLNDP-RESTRICTED (Standing Condition)

Severity
MOD NA Additional network data This condition is informative

paths cannot be and generally requires no
provisioned due to corrective action, since
fragmentation. services can still be
provisioned to use the available
network data paths.
However, if new service
provisioning is blocked, initiate
a network data path cleanup
process using NED.
BDI-ODU (ODU-BDI)
The corresponding SNMP name for this condition is “backwardDefectIndicationOdu”.
Table 143: BDI-ODU (Standing Condition)

Severity Action
CH NR The facility has received a This condition is

signal containing the backward informative and requires no
defect indication code in the corrective action.
ODU layer overhead, Corrective action will be
indicating that a failure has taken in response to the
occurred in the transmit signal failure condition
direction between this point reported along the opposite
and the far-end ODU layer direction of the path.
termination point.
Standing Conditions
BDI-OTU (OTU-BDI)
The corresponding SNMP name for this condition is “backwardDefectIndicationOtu”.
Table 144: BDI-OTU (Standing Condition)

Severity Action
CH NR The facility has received a This condition is informative

signal containing the and requires no corrective
backward defect indication action. Corrective action
code in the OTU layer will be taken in response to
overhead, indicating that a the signal failure condition
failure has occurred in the reported along the opposite
transmit direction between direction of the path.
this point and the far-end
OTU layer termination point.
BDI-TCMA (TCM_A-BDI)
“backwardDefectIndicationOduTcmA”.
Table 145: BDI-TCMA (Standing Condition)

Severity Action

signal containing the backward informative and requires
defect indication code in the no corrective action.
tandem connection monitoring Corrective action will be
overhead for the TCMi layer taken in response to the
assigned as instance “A”, signal failure condition
indicating that a failure has reported along the
occurred in the transmit opposite direction of the
direction between this point and path.
the far-end tandem connection
termination point.
Standing Conditions
BDI-TCMB (TCM_B-BDI)
“backwardDefectIndicationOduTcmB”.
Table 146: BDI-TCMB (Standing Condition)

Severity Action

signal containing the backward informative and requires no
defect indication code in the corrective action.
tandem connection monitoring Corrective action will be
overhead for the TCMi layer taken in response to the
assigned as instance “B”, signal failure condition
indicating that a failure has reported along the opposite
occurred in the transmit direction of the path.
direction between this point and
termination point.
BDI-TCMC (TCM_C-BDI)
“backwardDefectIndicationOduTcmC”.
Table 147: BDI-TCMC (Standing Condition)

Severity Action

signal containing the backward informative and no
defect indication code in the corrective action is
tandem connection monitoring needed. Corrective action
overhead for the TCMi layer will be taken in response to
assigned as instance “C”, the signal failure condition
indicating that a failure has reported along the opposite
occurred in the transmit direction of the path.
direction between this point and
termination point.
Standing Conditions
BPCOMMLOSS (Communication Loss)

The corresponding SNMP name for this condition is “communicationLoss”.
Table 148: BPCOMMLOSS (Standing Condition)

Severity
MOD MJ • The module has 1 If the condition is reported

failed. on multiple modules in the
• The ECM-x/ shelf, replace the ECM-
SCM-x has x/SCM-x.
failed. 2 Replace module.
• The backplane 3 Contact ADVA Optical
has failed. Networking Technical
Services.
The backplane may be
defective and need to be
replaced.
CALC-TOP (Topology Calculation)

“topologyDataCalculationInProgress”.
Table 149: CALC-TOP (Standing Condition)

Severity Action
TOP NA Calculation of the network No action is required. The

topology (i.e. the elements condition will clear
within the network and automatically once the
their interconnect topology determination
relationships) is in process completes.
progress.
Standing Conditions
CCM-ERR (CCM Error)

The corresponding SNMP name for this condition is “cfmCcmError”.
Table 150: CCM-ERR (Standing Condition)

Severity Action
DOWN- MN Erroneous Continuity Check This error is informative and

MEP Message (CCM) defect is no immediate action is
raised when one invalid CCM required. If the error persists,
is received. It is cleared it may indicated a degraded
when an invalid CCM is not service. If a degradation is
received for 3.5 times the service is known or
provisioned CCM suspected, review data
transmission interval of the plane reported errors along
last invalid CCM. the service path to determine
the location of the failure or
signal impairment and take
the corrective actions
indicated by the reported
data plane condition(s).
CCM-LOS (CCM Loss)

The corresponding SNMP name for this condition is “cfmCcmLost”.
Table 151: CCM-LOS (Standing Condition)

Severity
DOWN- CR This defect indicates Review data plane reported

MEP that a CCM is not errors along the service path to
received from a Remote determine the location of the
MEP for 3 consecutive failure or signal impairment and
provisioned CCM take the corrective actions
transmission intervals. indicated by the reported data
plane condition(s).
Standing Conditions
CCM-MACSTAT (CCM MAC Status)

The corresponding SNMP name for this condition is “cfmCcmMacStatus”.
Table 152: CCM-MACSTAT (Standing Condition)

Severity Action
DOWN-MEP NR This defect indicates This condition is informative in

that the Media Access nature, and no specific
Control (MAC) layer corrective action is required.
service on the port with Corrective action will be taken
which the MEP is in response to the failure
associated is condition which led to the loss
unavailable. of the MAC service on the
affected port.
CDC (CD Adjust in Progress)

The corresponding SNMP name for this condition is “dispertionTunningCondition”.
Table 153: CDC (Standing Condition)

Severity Action
CH NA The process of adjusting the No action is required. The

dynamic chromatic dispersion condition will clear
compensation element within automatically once the
the equipment supporting the adjustment process
facility is underway completes.
Standing Conditions
CHARSYNC (Loss of Char Sync)

The corresponding SNMP name for this condition is “lossOfCharSync”.
Table 154: CHARSYNC (Standing Condition)

Severity
CH CR The receiver has lost 1 Verify that the facility is

ETH character provisioned correctly.
synchronization with 2 Verify that the incoming cable is
the incoming blocks the correct cable and that the
in the received transmit and receive ports are
signal. connected to their proper
This is typically respective portions of the cable
caused either by the (i.e. that the fibers are not
incoming signal being swapped between transmit and
of a type other than receive).
that defined by the
facility, but a failure 3 Verify that the incoming fiber is
at the source of the firmly connected to the receive
signal which causes port associated with the facility
coding errors in the and that the connector is not
transmitted signal, or physically impaired by
by bit errors on the obstructions, dirt or component
line which have damage. Clean the connector or
degraded the replace the cable, plug or
incoming signal. module, as appropriate,
depending upon the cause
determined from the physical
examination.
4 Verify that a signal is present at
the cable termination and that
the signal conforms to the
required specifications (e.g.
minimum and maximum power
levels). If the signal meets the
required specifications proceed
to the next step below,
otherwise locate the source of
the signal problem upstream
5 Verify that the source of the
signal is operating correctly.
6 Replace the plug or module
supporting the facility.
Standing Conditions
CHARSYNC-FEND (FEND Loss of Char

Sync)
The corresponding SNMP name for this condition is “lossOfCharSyncFromFarEnd”.
Table 155: CHARSYNC-FEND (Standing Condition)

CH: NR The far-end has indicated that it has This condition is

{ F1062 | encountered a loss of character informative and no
F1250 } synchronization error in the signal corrective action is
transmitted from this facility. needed, since
corrective action
CH: The far-end has indicated that it has will be initiated by
{ GFPF | encountered a loss of character the failure detected
GFPT } synchronization error in the received at the far-end.
client signal being mapped at that
point, and therefore the incoming
GFP signal contains a condition
code instead of an actual client
payload.
CRY (Encryption-Disabled)
“encryptionPortEncryptionSwitchedOff”.
Table 156: CRY (Standing Condition)

Severity Cause
MOD NA The This condition is informative and no

cryptographic corrective action is needed. Cryptographic
officer has functions are typically disabled temporarily
temporarily during installation and recovery tests. If not
disabled manually re-enabled, encrypted operations
encryption will automatically resume after a period of
functions. time.
Standing Conditions
CRYINTFAIL (Internal Encryption

Fail)
The corresponding SNMP name for this condition is “internalEncryptionFail.”
Table 157: CRYINTFAIL (Standing Condition)

Severity
CH1 CR The encryption and Restart the link by cold starting the
decryption registers do modules on both ends of the link.
not match or are out of
sync. The traffic has
been dropped.
CRYOFFEN (Encryption-Bypassed)
“encryptionPortEncryptionSwitchOffEnabled”.
Table 158: CRYOFFEN (Standing Condition)

Severity
CH NA The cryptographic This condition is informative and

officer has granted requires no corrective action.
permission for Cryptographic functions are typically
disabling disabled temporarily during installation
encryption and recovery tests. If no manually re-
functions. enabled, encrypted operations will
automatically resume after a period of
time.
1This condition may be raised on 5TCE-PCN-10GU+AES10G and 5TCE-PCTN-

10GU+AES10G modules.
Standing Conditions
CRYPW-MIS (Crypto Requires

Password)
“encryptionModuleCryPasswdMissing”.
Table 159: CRYPW-MIS (Standing Condition)

Severity Cause
MOD MN A password Cryptographic services require that a

has not been Cryptographic-Officer role is assigned to
provisioned for the equipment, and that various actions are
the performed by said role.
Cryptographic- 1 Provision the password value to be
Officer role on used to authenticate a session as that
the equipment. of the Cryptographic-Officer role on the
equipment. This action will require
knowledge of the initial password
assigned during manufacturing, which
is shipped to the registered owner of
the equipment.
2 Once the Cryptographic-Officer
password has been assigned, consult
the installation and turn-up procedures
for the procedure to configure
encrypted service operation.
CRYTST (Encryption-Test)
The corresponding SNMP name for this condition is “encryptionModuleSelfTestStarted”.
Table 160: CRYTST (Standing Condition)

Severity
MOD NA A self-test of the This condition is informative and

cryptographic functions no corrective action is needed.
of the equipment has
been initiated.
Standing Conditions
CSF-OPU (OPU-Client Signal Fail)

The corresponding SNMP name for this condition is “opuClientSignalFail”.
Table 161: CSF-OPU (Standing Condition)

Severity
MOD NR The client signal This condition indicates a failure of

mapped into the the client signal at the point where the
OPU payload area OPU payload was mapped, upstream
has experienced a of the location reporting the failure.
hard failure such as This condition is informative and no
LOS, LOF, etc. corrective action is needed.
Corrective actions will be taken in
response to the reported failure of the
client signal at the upstream location
where the client signal is mapped into
the OPU payload.
CSF-VF (VF-Client Signal Fail)

The corresponding SNMP name for this condition is “vfClientSignalFail”.
Table 162: CSF-VF (Standing Condition)

Severity
CH NR The virtual facility This condition is informative and

has detected a client requires no corrective action.
signal failure at the Corrective action will be taken in
upstream site. response to the signal failure condition
reported by the client facility at the
upstream site.
Standing Conditions
DBACT_MEA (Database-Mismatch)
The corresponding SNMP name for this condition is “databaseMismatch”.
Table 163: DBACT_MEA (Standing Condition)

Severity Cause
COM MJ The system If the database was just restored and it is

database intended that the network element adopt
contains a this database as its new provisioning
signature information, then the new database should
value be accepted, which will clear this
indicating it is condition.
for a different If it was not intended that the network
network element adopt the provisioning information
element. from another system, the correct backup
copy of the database for the network
element should be downloaded and the
system restored using that database.
DBFAIL (Database-Validate Fail)

The corresponding SNMP name for this condition is “databaseFailure”.
Table 164: DBFAIL (Standing Condition)

Severity Cause
COM MJ The integrity The system database should be restored

of the system using the most recent backup copy of the
database has database for the network element.
been If this condition recurs, within a relatively
compromised. brief time interval (e.g. within one week), it
may indicate a problem with the memory
used to store the database on the network
controller unit. In this case, it is
recommended that the network controller
unit be replaced.
Standing Conditions
DBNCU_MEA (Database-NCU Type

Error)
The corresponding SNMP name for this condition is “databaseNcuMismatch”.
Table 165: DBNCU_MEA (Standing Condition)

Severity
COM MJ The database If you exchanged an NCU with an

indicates that a NCU2E, the DBNCU_MEA alarm
different grade of indicates that the NCU type is different
NCU or NCU2E than before. Accept that the restored
module is required database is used with the new NCU
in order to support type. Do as follows:
all of the 1 Select “System Management” >
provisioned “Software and Database Control” >
functions. “Database” tab.
2 Select [Accept].
After the reboot, the NCU:
o
runs the correct software
o
uses the previous database
For an NCU exchange to the new
NCU2E:
o
SC-1-A-C has changed to SC-
1-A-C1
o
SC-1-A-C2 is UAS
Standing Conditions
DBRI (Database-Copy Partial)

The corresponding SNMP name for this condition is “dbReplicationIncompleted”.
Table 166: DBRI (Standing Condition)

Severity Cause
MOD MJ1 Copying of the During a network controller module

database image replacement, this condition indicates that
from the active copying of the active database to the
network replacement module is in progress, and
controller therefore the standby module is not yet
module to the ready to provide service redundancy.
standby module
is in progress This condition is informative and no
(i.e. not yet corrective action is required, but the
completed). condition is visible and service affecting, to
ensure that automatic switching to the
standby module will not occur until it has
successfully synchronized its copy of the
database.
1For NCU-II-P modules, the default severity is MN.
Standing Conditions
DBVER_MEA (Database-Version)
The corresponding SNMP name for this condition is “databaseVersionMismatch”.
Table 167: DBVER_MEA (Standing Condition)

Severity Cause
COM MJ The database Verify that the system software generic is

employs a the correct one, and if not, reload the
schema which system software with the correct generic.
is incompatible If the system software generic is correct,
with the current this copy of the database may not be used
software (it was either saved while running a later
generic. generic which has been backed out, or it is
too many schema issues out of date to be
successfully converted to the current
schema). Download a copy of the database
saved using a compatible schema and
restore the database using that backup
copy instead.
Note: The database backup has to be
restored to the version from which it was
downloaded.
For example, the NCU has a software
version 7.1.5, then the database backup
from 7.1.5 has to be used.
Standing Conditions
DECTHRES-FAIL (Decision Threshold-

Fail)
The corresponding SNMP name for this condition is “xfpDecisionThresSetFailed”.
Table 168: DECTHRES-FAIL (Standing Condition)

Severity Cause
CH MN An attempt to This condition indicates that the system is

change the not operating according to the provisioned
optical signal decision threshold operating mode. Either
level decision the provisioned mode was set erroneously,
threshold or there may be a facility connection or
setting (e.g. to routing problem.
compensate 1 If this standing condition was raised
for the effect of when attempting to set the Decision
Raman Threshold of an
pumping) was XFP/11G/Dxxxx.xxV/SM/LC#Dxx
unsuccessful. 1061701xxx with HW revision 5.xx to
“Forward Raman”, skip the remaining
steps. Only HW revisions 2.xx and 4.xx
of the
XFP/11G/Dxxxx.xxV/SM/LC#Dxx
1061701xxx support the “Forward
Raman” setting.
2 Verify that the facility is correctly
connected (physically and via
provisioned cross-connections) to the
intended optical multiplex facility.
Correct any cabling or cross-connection
errors.
3 Verify whether the OM facility to which
the CH facility is connected employs
Raman amplification.
4 Ensure that the CH facility decision
threshold setting is correctly
provisioned. For example, when using
XFP/11G/Dxxxx.xxV/SM/LC#Dxx
1061701xxx with HW revisions 2.xx or
4.xx in a network with 2RAMAN-C15-
LL optical amplifiers and TWRS fiber,
set the Decision Threshold to “Forward
Raman.
If the above actions did not rectify the
problem, please contact your ADVA Optical
Representative for assistance.
Standing Conditions
DX-LINK (Link-Fail (Controller))

The corresponding SNMP name for this condition is “duplexLinkFailure”.
Table 169: DX-LINK (Standing Condition)

Severity Cause
MOD MJ1 The link allowing This condition indicates that the active and standby controllers
the redundant cannot communicate with each other via their dedicated status
network link. Since the modules are unable to coordinate their actions,
controllers to they will remain in their respective operating states in existence
communicate prior to the detection of this condition. While this condition exists,
with each other automatic and manual duplex switching are unavailable.
has failed. 1 Verify that both network controller modules are correctly
provisioned and equipped in the appropriate, dedicated slots
within the master shelf. Correct any provisioning or equipping
errors.
2 Remove the inactive, standby network controller module. If
this condition clears, and is replaced by an indication that the
standby unit was removed, reseat the standby module. If the
original condition recurs, replace the standby module.
NOTE: The following step(s) will result in a temporary loss of

management access to the network element. It is
recommended to perform these steps during a maintenance
window when the impact of such an interruption is minimal.
3 Remove and reseat the active network controller module. If

the original condition clears, and the system progresses to its
normal, redundant controller operating state, no further
actions are needed.
4 Ensure that the current system database was backed up.
Replace the active network controller module (Note: Do not
exchange it with the backup module. If a spare module is
unavailable, it may be replaced with the backup module,
which may in turn be replaced with a new module later, but
the originally active module should be considered failed and
discarded or submitted for repair). Install the correct software
generic and restore the system database from the backup
copy. If the original condition clears, and the system
progresses to its normal, redundant controller operating state,
no further actions are needed.
5 Replace the shelf containing the network controller modules.
Standing Conditions
EOC (Management Channel-Fail)

“embeddedOperationsChannelFailure”.
Table 170: EOC (Standing Condition)

Severity Cause
DCN MJ The received 1 Verify that the facility is provisioned

embedded correctly at both the near and far ends.
operations 2 Verify that the incoming cable is the
channel has correct cable and that the transmit and
failed. receive ports are connected to their proper
respective portions of the cable (i.e. that
the fibers are not swapped between
transmit and receive).
3 Verify that the incoming fiber is firmly
connected to the receive port associated
with the facility and that the connector is
not physically impaired by obstructions,
dirt or component damage. Clean the
connector or replace the cable, plug or
module, as appropriate, depending upon
the cause determined from the physical
examination.
4 Verify that a signal is present at the cable
termination and that the signal conforms to
the required specifications (e.g. minimum
and maximum power levels). If the signal
meets the required specifications proceed
to the next step below, otherwise locate
the source of the signal problem upstream
5 Replace the near-end plug supporting the
facility.
6 Replace the far-end plug supporting the
facility.
7 Replace the near-end module supporting
the facility.
8 Replace the far-end module supporting the
facility.
Standing Conditions
EOI (Tunnel Outage)

The corresponding SNMP name for this condition is “entityOutageIndication”.
Table 171: EOI (Standing Condition)

Severity
WDM CR A remotely located This condition indicates that a

Tunnel data plane entity failure of a data plane entity on a
has experienced a remote node is causing an outage of
failure condition the service supported by the
which has caused connection. While this condition is
an outage within informative (since corrective action
the control plane will be taken in response to the data
connection. plane failure which was already
reported), it offers a means of
identifying the data plane failure
location along the connection’s
route.
The AID values of the Remote
Alarm Table entities providing
details on the remote data plane
failures are listed in the RA-LIST
multi-valued attribute of the
connection entity. Each of the listed
entities may be retrieved to obtain
details on the location of the failure
causing the outage of the
connection.
EOL (Laser-End of Life)

The corresponding SNMP name for this condition is “laserEndOfLife”.
Table 172: EOL (Standing Condition)

Severity Action
OM MN The optical amplifier module Replace the module

has detected that one or more supporting the facility.
of the pump lasers within the
module have reached their end-
of-life point.
Standing Conditions
EPT-UAV (All Partners-Link Fail)

The corresponding SNMP name for this condition is “partnerUnavailable”.
Table 173: EPT-UAV (Standing Condition)

Severity
MOD MJ Loss of 1 Ensure the OPPM is installed and

communication properly provisioned with the correct
with all protection partner.
provisioned 2 Ensure the channel module(s)
protection associated with the protection
partners. partners are installed and provisioned
properly.
3 Verify that each protection partner is
properly provisioned. If any
protection partner was deleted (this is
indicated by ACP-RMVD (APS
Partner Deleted)), reprovision it or set
the associated protection partner on
the OPPM to None.
4 Correct any inter-shelf
communication issues.
EQLZ (Equalize-In Progress)

The corresponding SNMP name for this condition is “equalizationProgress”.
When using the control plane to manage networks, do NOT change the
alarm severity of this standing condition to Not Reported (NR).
Note
Table 174: EQLZ (Standing Condition)

Severity Corrective
Action
CH NA The optical channel is currently This condition is

undergoing a power balancing process to informative and
adjust the optical launch power to the no corrective
optimal level. action is needed.
OM The optical multiplex facility channels are

currently undergoing a power balancing
process to adjust the optical launch
powers of the active channels to their
respective optimal levels.
Standing Conditions
EQLZ-ADJUST (Equalize-Adjust)
The corresponding SNMP name for this condition is “eqlzAdjust”.
When using the control plane to manage networks, do NOT change the
alarm severity of this standing condition to Not Reported (NR).
Note
Table 175: EQLZ-ADJUST (Standing Condition)

Severity Corrective
Action
CH NA The optical channel is currently This condition is

undergoing a power balancing process to informative and
adjust the optical launch power to the no corrective
optimal level. action is needed.
OM The optical multiplex facility channels are

currently undergoing a power balancing
process to adjust the optical launch
powers of the active channels to their
respective optimal levels.
Standing Conditions
FANANR (Fan Abnormal) - one FAN is

faulty
The corresponding SNMP name for this condition is “singleFanFailure”.
Table 176: FANANR (Standing Condition)

MOD: MN A fan within the fan Replace the shelf

FAN/9HU, module assembly has assembly within 48
FAN/X9HU, failed or is hours after failure.
FCU7HU malfunctioning.
FAN/1HU1 A fan within the fan Replace the faulty fan

module assembly has module during the
failed or is next planned
malfunctioning. maintenance window.
MOD: A fan within the shelf Replace the shelf

SH1HU-F/2DC, assembly has failed assembly during the
SH1HU-R, or is malfunctioning. next planned
SH1HU-HP/2DC, maintenance window.
SH1HU-HP/E-
TEMP/2DC
1 The FAN/1HU module, installed in the SH1HU-R/PF shelf, is a hot-replaceable unit

with 3 fans. The fans cannot be replaced individually, only the complete FAN/1HU
unit (comprising the 3 fans) can be replaced.
Standing Conditions
FANFLT (Fan Fault) - more than one

FAN is faulty
The corresponding SNMP name for this condition is “multipleFanFailure”.
Table 177: FANFLT (Standing Condition)

MOD: CR The fan module Replace the faulty fan

FAN/9HU, assembly has failed modules within 48
FAN/X9HU, or is malfunctioning. hours after failure.
FCU7HU,
FAN/1HU1
MOD: The fans within the Replace the module

PSU1HU-AC, module have failed or within 48 hours after
PSU1HU-DC are malfunctioning. failure.
SHELF: The fans within the Replace the shelf

SH1HU-F/2DC, shelf assembly have assembly within 48
SH1HU-R, failed or are hours after failure.
SH1HU-HP/2DC malfunctioning.
SH1HU-HP/E-
TEMP/2DC
1 The FAN/1HU module, installed in the SH1HU-R/PF shelf, is a hot-replaceable unit

with 3 fans. The fans cannot be replaced individually, only the complete FAN/1HU
unit (comprising the 3 fans) can be replaced.
Standing Conditions
FC-ATT-HI-TX (Fiber-Loss High Tx)

The corresponding SNMP name for this condition is “fiberAttenuationHighTx”.
Table 178: FC-ATT-HI-TX (Standing Condition)

Severity
PTP NR The most probable causes Note: This condition is normally not reported, and
of this condition are: corrective actions are typically performed in
• A fiber connected to response to the FC-ATT-HI (Fiber-Loss High)
the port that is condition, which is reported by the module at the
transmitting the fiber opposite end of the fiber.
detection signal is 1 Check that all optical connectors, on both
loose. ends of the fiber, are securely attached, and
• A dirty or damaged tighten/firmly insert any loose connectors.
connector. 2 Visually inspect the fiber and verify that it is
• The fiber is of the of the appropriate fiber type, that it conforms
wrong fiber type, is to the required maximum length/attenuation
too long, has a bend limits (if it contains an in-line attenuator,
exceeding the verify that it is of the correct value), and that
minimum bend radius, the fiber is not bent, pinched or physically
or is damaged. compromised in any way. Replace any fiber
which is of the wrong type or specification,
• The near-end optical
which has been bent beyond the allowable
source power level is
minimum bend radius, or which has
below the required
operating power level.
3 Inspect the fiber connectors at each end of
the fiber and clean each connector. Verify
that the connectors are undamaged. Test the
optical fiber cable to verify that it meets
application, and that there are no internal
fiber breaks or excessive loss due to failures
that are not readily apparent from visual
inspection. Replace any damaged
component (cable or module, if the
4 Verify that the optical source for the module
is operating within expected optical signal
power limits. Replace any module found to
Standing Conditions
FC-ATT-HI (Fiber-Loss High)

The corresponding SNMP name for this condition is “fiberAttenuationHigh”.
Table 179: FC-ATT-HI (Standing Condition)

Severity
PTP MN The most probable causes of 1 Check that all optical connectors, on
this condition are: both ends of the fiber, are securely
• A fiber connected to the attached, and tighten/firmly insert any
port which is receiving loose connectors.
the fiber detect signal is 2 Visually inspect the fiber and verify that
loose. it is of the appropriate fiber type, that it
• A dirty or damaged conforms to the required maximum
connector. length/attenuation limits (if it contains an
in-line attenuator, verify that it is of the
• The fiber is of the wrong
correct value), and that the fiber is not
fiber type, is too long,
bent, pinched or physically
has a bend exceeding the
compromised in any way. Replace any
minimum bend radius, or
fiber which is of the wrong type or
is damaged
specification, which has been bent
• The far-end optical beyond the allowable minimum bend
source power level is radius, or which has sustained any
below the required physical damage.
operating power level.
3 Inspect the fiber connectors at each end
of the fiber and clean each connector.
Verify that the connectors are
undamaged. Test the optical fiber cable
to verify that it meets engineering
specifications for the application, and
that there are no internal fiber breaks or
excessive loss due to failures that are
not readily apparent from visual
inspection. Replace any damaged
component (cable or module, if the
4 Verify that the optical source for the fiber
connectivity check signals of the
modules at the far-end of the fiber is
operating within expected optical signal
power limits. Replace any module found
to operate outside the specified limits.
5 If the condition still fails to clear, replace
the module reporting the failure.
Standing Conditions
FC-COMM (Fiber-Communicate Fail)

The corresponding SNMP name for this condition is “fiberConnCommError”.
Table 180: FC-COMM (Standing Condition)

Severity Cause
PTP MN The fiber 1 Verify that the fiber detection termination

detect point entity is provisioned and in-service at
optical the far-end of the fiber, and that fiber
signal detection is enabled. Correct any
wavelength provisioning errors.
is present, 2 Verify that the module at the far-end is
but no data properly provisioned and equipped, and is
frames are operating error-free. Address any error
detected. conditions reported at the far-end module
or by the far-end fiber detection
termination point.
module supporting the facility.
FC-DATA (Fiber-Data Mismatch)

The corresponding SNMP name for this condition is “fiberConnDataFailure”.
Table 181: FC-DATA (Standing Condition)

Severity Cause
PTP MN The module 1 Verify that the fiber detection termination

is fibered to point entity at both ends of the fiber is
a different properly provisioned and fiber detection is
far-end port enabled. Correct any provisioning errors.
than the one 2 Verify that the fiber connection map
provisioned. provisioning information corresponds to the
intended fiber connection for the port.
Correct any provisioning errors.
3 Carefully trace the fiber to the far-end port
and determine to which port the fiber is
connected. Review the fiber connection
provisioning plan and adjust the fiber
connections at either or both ends, so that
they conform to the plan.
4 Replace the module at the far-end of the
fiber. If the condition still fails to clear,
replace the module supporting the facility.
Standing Conditions
FC-INVLD-TX (Fiber-Connect Invalid

Tx)
The corresponding SNMP name for this condition is “fiberConnInvalidTx”.
Table 182: FC-INVLD-TX (Standing Condition)

Severity
PTP NR The fiber Note: This condition is normally not

containing the reported. Corrective actions are typically
transmitted fiber performed in response to the FC-INVLD
detection signal is (Fiber-Connect Invalid) condition, which
connected to a is reported by the module at the opposite
port at the far-end end of the fiber.
which violates 1 Carefully trace the fiber to the far-
system end port and determine to which port
configuration the fiber is connected. Review the
rules. intended fiber connection
provisioning plan and adjust the fiber
connections at either or both ends,
so that they conform to the plan.
2 Replace the module at the far-end of
the fiber. If the condition still fails to
clear, replace the module supporting
the facility.
FC-INVLD (Fiber-Connect Invalid)

The corresponding SNMP name for this condition is “fiberConnInvalid”.
Table 183: FC-INVLD (Standing Condition)

Severity
PTP MN The fiber containing 1 Carefully trace the fiber to the far-
the received fiber end port and determine to which
detection signal is port the fiber is connected.
connected to a port Review the intended fiber
at the far-end which connection provisioning plan and
violates system adjust the fiber connections at
configuration rules. either or both ends, so that they
conform to the plan.
2 Replace the module at the far-end
of the fiber. If the condition still
fails to clear, replace the module
Standing Conditions
FC-LOS (Fiber-Loss of Signal)

The corresponding SNMP name for this condition is “fiberConnLos”.
Table 184: FC-LOS (Standing Condition)

Severity
PTP MN The far-end fiber detect 1 Verify that the fiber detection
termination point entity termination point entity at the
has been provisioned to far-end of the fiber is properly
disable the fiber detect provisioned, is in-service, and
feature, has been has the fiber detect feature
placed into a manually enabled. Correct any
out-of-service disabled provisioning errors.
state, or has 2 If the condition still fails to
experienced an clear, replace the far-end
equipment failure module.
affecting the fiber
detection signal optical
source.
FC-OPT-SF (Fiber-Tx Signal Fail)

The corresponding SNMP name for this condition is “fiberConnOptFault”.
Table 185: FC-OPT-SF (Standing Condition)

Severity Action
PTP MN The transmitted optical power Replace the module

level of the fiber detection supporting the facility.
signal is below the failure
threshold.
Standing Conditions
FC-PROT (Fiber-Protocol Fail)

The corresponding SNMP name for this condition is “fiberConnProtocolFailure”.
Table 186: FC-PROT (Standing Condition)

Severity
PTP MN The information packets If the system is undergoing a firmware update

received by the fiber procedure that has not yet completed, this
detection signaling condition may indicate that the firmware load on
mechanism are the module at one end of the fiber has been
experiencing a high rate upgraded while that of the module at the other end
of corruption/packet has not. In this case:
loss, contain an invalid 1 Verify the firmware load revision level of the
protocol version modules at both ends of the fiber and ensure
identifier value, or have that they are the version appropriate for the
inconsistent values software generic and module type. Upgrade
within various related any module found to contain an incorrect
protocol fields. firmware load revision level.
If one of the modules at either end of the fiber

recently had its firmware load modified or the
module was replaced, it is the likely cause of the
problem. In this case:
2 Verify the firmware load revision level of the
recently modified module and apply the
firmware load appropriate for the software
generic and module type. If the firmware load
is correct, verify the firmware load revision
level of the module reporting the fault and
upgrade it to one compatible with that of the
far-end module, if needed.
Standing Conditions
Table 186: FC-PROT (Standing Condition)

Severity
If neither of the preceding instances apply, the

issue may be due to an excessive number of
errors in the received protocol messages.
3 Check that all optical connectors, on both
ends of the fiber, are securely attached, and
tighten/firmly insert any loose connectors.
4 Visually inspect the fiber and verify that it is
of the appropriate fiber type, that it conforms
to the required maximum length/attenuation
limits (if it contains an in-line attenuator,
verify that it is of the correct value), and that
the fiber is not bent, pinched or physically
compromised in any way. Replace any fiber
which is of the wrong type or specification,
which has been bent beyond the allowable
minimum bend radius, or which has
5 Inspect the fiber connectors at each end of
the fiber and clean each connector. Verify
that the connectors are undamaged. Test the
optical fiber cable to verify that it meets
engineering specifications for the application,
and that there are no internal fiber breaks or
excessive loss due to failures which are not
readily apparent from visual inspection.
Replace any damaged component (cable or
module, if the connector on the module is
damaged).
6 Verify that the optical source for the fiber
connectivity check signals of the modules at
the far-end of the fiber is operating within
expected optical signal power limits. Replace
any module found to operate outside the
specified limits.
7 If the condition still fails to clear, replace the
module reporting the failure
Standing Conditions
FEND-LOS (FEND Loss of Signal)

The corresponding SNMP name for this condition is “lossOfSignalTransmitter”.
Table 187: FEND-LOS (Standing Condition)

Severity
OM NR The far-end of the This condition is informative and

optical line intended to assist in the corrective
monitoring link on the actions associated with the loss of
RSM-OLM has signal condition reported at the far-
detected a loss of end. No additional corrective actions
signal condition. are needed.
FENDIP (FEND IP Unknown)

The corresponding SNMP name for this condition is “farEndIpAddressUnknown”.
Table 188: FENDIP (Standing Condition)

Severity Action
OM MJ The IP address of the far-end Provision the FENDIP

of the APS signalling link attribute value of the OM
supporting the facilities on FFP of which the facility is a
the associated VSM has not member.
been provisioned in the
associated OM protection
group.
Standing Conditions
FENDLINK (FEND Communication

Fail)
The corresponding SNMP name for this condition is “farEndCommFailure”.
Table 189: FENDLINK (Standing Condition)

Severity Cause
CH1 MJ The 1 Verify that the facility is provisioned

communications correctly.
link signal from 2 Verify that the incoming cable is the
the far-end plug correct cable and that the transmit and
has failed. receive ports are connected to their
proper respective portions of the cable
(i.e. that the fibers are not swapped
between transmit and receive).
3 Verify that the incoming optical fiber is
firmly connected to the receive port
associated with the facility and that
the connector is not physically
impaired by obstructions, dirt or
component damage. Clean the
connector or replace the cable or plug
as appropriate, depending upon the
cause determined from the physical
examination.
4 Verify that a signal is present at the
cable termination and that the signal
conforms to the required
specifications (e.g. minimum and
maximum power levels). If the signal
meets the required specifications
proceed to the next step below,
otherwise locate the source of the
signal problem upstream and repair
the problem.
5 Replace the near-end plug supporting
the facility and verify that the
condition clears. If not, the original
plug may be re-inserted and the far-
end plug must be replaced.
1Applicable only to facilities supported by a dual ended type Optojack plug (e.g. SFP-
OD-C or SFP-OD-G).
Standing Conditions
FIM (FEND Info Mismatch)

The corresponding SNMP name for this condition is “farEndInformationMismatch”.
Table 190: FIM (Standing Condition)

Severity Cause
DCN: NA The far-end 1 Determine the intended far-end logical

{LIFTENUM logical interface location by reviewing the
LIFTEUNN interface optical line with which the reporting
LIFVTENUM entity is not entity is associated.
LIFVTEUNN} provisioned. 2 Connect to the supporting Network
Element.
3 Review the provisioning status of the
logical interface associated with that
ends termination of the optical line
whose associated logical interface
facility reported the condition.
Provision the missing logical interface
entity.
FLAT-BAT (Battery-No Charge)

The corresponding SNMP name for this condition is “batteryNoCharge.”
Table 191: FLAT-BAT (Standing Condition)

Severity
MOD MJ The module battery has Replace the module during the
discharged. The module next maintenance window.
will continue to operate,
but passwords cannot
be backed up in case of
a power outage.
Standing Conditions
FRCD (Laser-Forced On)

Note that this condition is only possible when the entity is in an OOS-MT state, which will
suppress the autonomous reporting of this condition.
The corresponding SNMP name for this condition is “facilityForcedOn”.
Table 192: FRCD (Standing Condition)

Severity Action
CH NA A manual forced override A forced override operation

operation is in effect, forcing is typically performed as a
the transmit direction to be part of service affecting
ETH NA
active in spite of a condition maintenance or testing
which would normally cause activities. This condition is
the transmitter to be disabled. informative and no
corrective action is needed.
OM: NA A manual forced override A forced override operation

RAMAN operation is in effect, forcing is typically performed as a
the amplifier to provide pump part of service affecting
power in spite of a condition maintenance or testing
which would normally cause activities. This condition is
the amplifier to be disabled. informative and no
FRCD-HALT (Forced Halt)

The corresponding SNMP name for this condition is “backupForcedToHalt”.
Table 193: FRCD-HALT (Standing Condition)

Severity
MOD MJ1 The backup (standby) A forced halt of a backup

controller of a duplex controller’s normal operation is
protection pair has typically performed as a part of
been manually forced maintenance or testing activities.
to halt its normal This condition is informative and no
operation. corrective action is needed.
Standing Conditions
FWDASEPILOT (Foward Pilot-On)

Note that this condition only occurs when the facility is in OOS Maintenance state, which
suppresses it's autonomous reporting.
The corresponding SNMP name for this condition is “fwdAseTableOnPilot”.
Table 194: FWDASEPILOT (Standing Condition)

Severity Action
OM: NA A manual forced override A forced override operation is

RAMAN operation is in effect, forcing typically performed as a part
the amplifier to provide of service-affecting
reverse direction pump maintenance or testing
power, despite a condition activities.
which would normally cause This condition is informative
the amplifier to be disabled. and requires no corrective
action.
Standing Conditions
FWDASEPILOT-FAIL (Foward Pilot-

Fail)
This condition only occurs when the facility is in OOS Maintenance state, which
suppresses its autonomous reporting.
The corresponding SNMP name for this condition is “fwdAseTableFailPilot”.
Table 195: FWDASEPILOT-FAIL (Standing Condition)

Severity
OM: MN An attempt to force A forced override operation is typically performed as a part of

RAMAN the amplifier to service-affecting maintenance or testing activities. When such
provide reverse an operation fails, execute the following corrective actions:
direction pump 1 Verify that the facility is in the correct state, allowing the
power, despite a forced override operation to be performed. If necessary,
condition which adjust the state of the entity to meet the pre-requisites for
would normally the operation and re-attempt the forced override operation.
cause the amplifier
2 Verify that the module supporting the facility and the
to be disabled, has
facility itself are provisioned, that the provisioning
failed.
corresponds to the engineering specifications of the
module and facility, that the module is equipped, and that
the module and equipment are operating without any other
error conditions reported. Correct any provisioning errors
or address any other reported conditions, and then re-
attempt the forced override operation.
3 Verify that there are no physical cabling issues in the fiber
span for which the forced override operation is attempted.
Cabling issues include incorrectly connected fibers,
broken fibers, fibers with high attenuation due to cable
bends or erroneous fiber types, or dirty or damaged
connectors. Repair any cabling issues identified within the
fiber span and then re-attempt the forced override
operation.
4 Verify that any associated Optical Supervisory Channel
facility is properly provisioned, that the supporting
modules are properly equipped and that they are correctly
interconnected to the same fiber span, and that all the
elements are operating error-free. Correct any reported
errors or cabling issues with the associated OSC and then
re-attempt the forced override operation.
Standing Conditions
FWPEN (FWP-Allow Update)

“encryptionModuleFwpUpdateEnabled”.
Table 196: FWPEN (Standing Condition)

Severity
MOD NA The module, which This condition is informative and

includes encryption indicates that the upgrade of the
functionality, has module firmware may now be
been provisioned to performed. Once the specified
allow a specific firmware upgrade has completed,
firmware upgrade to the condition will clear.
be performed.
FWPM-NSA (FWP-Mismatch(NSA))
“fwpMismatchDownloadNotServiceAffecting”.
Table 197: FWPM-NSA (Standing Condition)

MOD NA The firmware package installed on Update the module

this module differs from the version firmware to the version
supplied with the current software supplied with the
generic. Updating to this firmware current software
package will not be service- generic, as described
affecting. in “Updating the NE
Software Release” on
p. 617 and “Performing
Other Software
Update Actions” on
p. 628.
Do not attempt to make any provisioning changes to this module until the
FWPM-NSA condition is resolved.
Note
Standing Conditions
FWPM-SA (FWP-Mismatch (SA))

“fwpMismatchDownloadServiceAffecting”.
Table 198: FWPM-SA (Standing Condition)

Severity
MOD NA The firmware Update the module firmware to the

package installed version supplied with the current
on this module software generic, as described in
differs from the “Updating the NE Software Release”
version supplied on p. 617 and “Performing Other
with the current Software Update Actions” on p. 628.
software generic. Since the application of this update
Updating to this may be service-affecting, it is
firmware package recommended to perform this upgrade
will be service- during a scheduled maintenance
affecting. window reserved for the application of
such updates. When updating a
module which supports a protection
group, the updates should be applied
to each module separately, and the
module should not contain any active
protection group members when the
update is performed.
Do not attempt to make any provisioning changes to this module until the
FWPM-SA condition is resolved.
Note
Standing Conditions
GAINTILTANR (Gain/Tilt Abnormal)

The corresponding SNMP name for this condition is “gainTiltNotSettable”.
Table 199: GAINTILTANR (Standing Condition)

Severity
OM MJ It is not possible to adjust 1 Verify that the provisioned settings for the gain
either or both of the gain and/or and tilt levels are correct and that they
tilt settings on the module to correspond to the computed settings for your
the specified levels. network configuration. Correct any erroneous
The levels may be values.
unattainable in cases where 2 Verify that the optical power level at the input of
the input power to the module the amplifier module is within the required
falls outside the allowable limits. If not, determine the cause of the
range specified for the module, problem by examining the upstream fiber and
or in cases where the mid- components to identify any fiber breaks,
stage attenuation is abnormal fiber losses, excessive span lengths,
excessive. inadequate span lengths, missing or incorrect
optical attenuators/pads or equipment failures
and correct the condition which is found.
3 Verify that the connection between the first and
second amplifier stage is correctly fibered, and
that the optical power level at the input to the
second stage is within limits. If not, verify that
the output level of the first stage is within limits.
If the first stage output level is not within limits,
replace the module. If it is within limits, but the
power at the input to the second stage is not,
verify that the correct dispersion compensation
module is being used and that the fiber path
between the first and second stage is correctly
cabled. Replace any erroneous dispersion
compensation components or correct any fiber
cabling issues. If there are no cabling issues
and the dispersion element is of the correct
type, replace the dispersion module. (Note: If
the OPTLMT condition (OPTLMT (Optical
Power Tx Limit)) is raised simultaneously, the
mid-stage attenuation exceeds the allowable
limit.)
Standing Conditions
HIBER (Bit Error Rate High)

The corresponding SNMP name for this condition is “highBer”.
Table 200: HIBER (Standing Condition)

Severity
CH MJ The received 1 Verify that the near and far-end

ETH signal has a facilities are both provisioned
detected bit-error correctly and that they are of the
rate in excess of same type and have compatible
a system-defined properties.
limit. 2 Verify that the incoming cable is the
correct cable and that the transmit
and receive ports are connected to
their proper respective portions of the
cable (i.e. that the fibers are not
swapped between transmit and
receive).
3 Verify that the incoming optical fiber
is firmly connected to the receive port
connector or replace the cable, plug
or module, as appropriate, depending
upon the cause determined from the
physical examination.
the problem.
6 Verify that the plug used at the far-
end of the optical link is of the correct
type, is provisioned correctly, and is
operating within the specified limits of
optical launch power. If not, replace
the far-end plug or module supporting
the facility.
Standing Conditions
HW-ATRCV-FLT (Optical Power

Overload)
The corresponding SNMP name for this condition is “receiverOverloadProtection”.
Table 201: HW-ATRCV-FLT (Standing Condition)

Severity
DCN MN The received 1 Verify that there are no mis-

optical signal connections in the optical fiber
power level for cables supplying the receive signal
the facility is (e.g. that the output of the facility
above the has not been accidentally looped
maximum normal back to the receiver).
operating level 2 Verify that the span over which the
(the attenuation optical signal is travelling has the
from the optical minimum required optical
source to the attenuation.
receiver is
3 Verify that the plug used at the far-
abnormally low).
end of the optical link is of the
correct type, is provisioned
correctly, and is operating within the
specified limits of optical launch
power.
4 Verify that the optical pathway is not
being unintentionally optically
amplified between the source and
the receiver.
Standing Conditions
HW-INITIALIZING (Hardware
Initialization)
The corresponding SNMP name for this condition is “hwInitializing”.
Table 202: HW-INITIALIZING (Standing Condition)

Severity
MOD CR The module is This condition is generally informative

undergoing a lengthy and no corrective action is needed.
initialization process If a module remains in this condition
(lasting more than a for an excessive interval1, verify that
few seconds) and will conditions are within normal operating
automatically limits (e.g. the ambient temperature is
transition to an in- within the specified operating range,
service state when power supply is within normal range,
the process etc.) and if so, replace the module.
completes.
1Refer the Module and System Specification for the corresponding initialization
duration of this module type.
Standing Conditions
HW-OPR-HT (Optical Power Rx-

Damage)
The corresponding SNMP name for this condition is “hwOprReachedHT”.
This condition indicates that the affected equipment may already

have sustained damage due to the high optical power levels
received. Once the cause of the problem is corrected, it is
recommended to replace the module to ensure correct operation.
Table 203: HW-OPR-HT (Standing Condition)

Severity
MOD CR The received optical 1 Verify that there are no mis-

signal power level connections in the optical fiber
on one or more cables supplying the incoming
ports is above the signals.
maximum normal 2 Verify that each incoming signal
operating level (the conforms to the required
attenuation from the specifications (e.g. maximum
optical source to the power levels). If the signal meets
input port is the required specifications
abnormally low). proceed to the next step below,
signal problem upstream and
repair the problem, then proceed
to the next step below.
3 Replace the module supporting
the facility.
HWANR (Hardware Degrade)

The corresponding SNMP name for this condition is “hwDegrade”.
Table 204: HWANR (Standing Condition)

Severity
MOD MJ The module has failed, 1 If this condition is raised

but is able to maintain during firmware update of a
service under the current module that supports fiber
operating conditions. detection, wait 5 minutes
for it to clear.
HWFLT (Equipment Fault)

The corresponding SNMP name for this condition is “hwFailure”.
Standing Conditions
Table 205: HWFLT (Standing Condition)

Severity Cause
MOD1 CR The equipment 1 If the condition is raised on an FTM-x, replace the

may have failed faulty FTM-x within 48 hours.
and is unable to 2 If this alarm is raised on a PSM-x, replace the
reliably perform faulty PSM-x.
its intended
3 Verify that all PSU/PSM-x cables are properly
functions.2 3
2OSCM MJ inserted. Check the plugs for any visual damage.
OSCM 4 Verify that the external power source supplies the
OSCM-PN specified power to the PSUs.
PSCU
5 Verify that the shelf is correctly grounded.
SCU
SCU-E 6 Remove one of the two PSUs from the shelf, then
SCU-S delete it using the Craft or NED.
SCU-II o
If the condition persists, reboot the NCU.
o
If the condition persists, reinsert the PSU and
add it to the shelf using the Craft or NED. This
PSU did not cause the condition.
o
If the condition clears, this PSU caused the
HWFLT condition. Replace the PSU with
another of the same type and add it using the
Craft or NED.
Repeat this procedure for the second PSU.
NCU-II-P MN If the above actions could not rectify the problem,
please contact your ADVA Optical Networking
Technical Services Representative for assistance.
NCU-II, CR The module may 1 In NED, select Node -> General -> Defaults.
NCU-II-P, have failed and 2 In the NCU Flash Read-Write Error Automatic
NCU-S is unable to Restart blade, toggle Restart on Error.
reliably perform
3 Click Apply, then wait few minutes.
its intended
functions. 4 If the alarm persists, replace the module.
1This AIDType refers to all FSP 3000R7 modules except NCU, NCU-II, NCU-II-P,
NCU-S, NCU2E, 8-OTDR3HU, EROADM-DC, and pluggables.
2In the SH1HU-DC shelf, this condition will be raised for failures on installed modules,
but not for total or partial failures of the integrated fans. Refer to “FANANR (Fan
Abnormal) - one FAN is faulty” on p. 824.
3If the condition is raised at a PSM-x and multiple PSMs are installed and provisioned in a
redundant, load-sharing configuration, the default severity is minor (MN). If only one PSM
is installed and provisioned at this shelf, the default severity is critical (CR).
Standing Conditions
INHSWPR (Inhibit SwitchToProtect)

The corresponding SNMP name for this condition is “switchtoProtectionInhibitedL2”.
Table 206: INHSWPR (Standing Condition)

Severity
CH NA A manually initiated This condition occurs due to:

operation has been • the Inhibit Protect configuration to
performed to “yes”,
prevent the
ETH • a far-end lockout of protection
switching of traffic
request signaled from the peer
to the protection
bidirectionally switched protection
facility.
group.
OM
This condition is informative and no
INHSWWKG (Inhibit Working)

The corresponding SNMP name for this condition is “switchtoWorkingInhibitedL2”.
Table 207: INHSWWKG (Standing Condition)

Severity Cause
CH NA A manually This condition occurs due to:

initiated • the Inhibit Working configuration to
operation has “yes”,
been performed
ETH • a far-end lockout of working or forced
to prevent the
switch request1 signaled from the
switching of
peer bidirectionally switched
traffic to the
protection group.
OM working facility.
1The exact term depends upon the provisioned protection switching mechanism
used by the relevant protection group. Functionally, the request serves to inhibit the
switching of traffic to the working facility unless a higher priority failure (e.g. signal
failure on the protection facility or a lockout of protection) supersedes this request.
Standing Conditions
KEXINIT-MIS (Key Exchange-Fail

First)
“encryptionPortKeyInitExchgMissed”.
Table 208: KEXINIT-MIS (Standing Condition)

Severity Cause
CH MN The system This condition is informative and is expected

has not yet whenever a new service is being established
completed the but not yet active, or when a module is
first key reseated, replaced, or experiences a shelf
exchange with level power outage.
its peer. A session key must be negotiated in order to
(re-)establish service.
1 Ensure that the same authentication key
(shared secret) is provisioned on both
ends of the encrypted circuit.
2 Manually initiate negotiation of a new
session key.
KEXLFT-DEG (Key Exchange-Fail

Limit)
“encryptionPortMaxKeyExchgFailuresReachedIs”.
Table 209: KEXLFT-DEG (Standing Condition)

Severity
CH MJ The system has Although traffic is still operating

automatically normally, it will cease to do so once the
attempted to session key timer expires. To avoid an
negotiate a new interruption of service, a new session
session key the key must be negotiated prior to the
maximum number expiration time of the current key.
of times (3), and all 1 Ensure that the same
attempts have authentication key (shared secret)
failed. The system is provisioned on both ends of the
is still operating encrypted circuit.
with the previous
2 Manually initiate negotiation of a
key, and will
new session key.
continue to do so
until the key
expires.
Standing Conditions
KEXLFT-FAIL (Session Key-Missing)

“encryptionPortMaxKeyExchgFailuresReachedOos”.
Table 210: KEXLFT-FAIL (Standing Condition)

Severity
CH MJ The system has A new session key must be

automatically attempted negotiated in order to restore
to negotiate a new service.
session key the 1 Ensure that the same
maximum number of authentication key (shared
times (3), and all attempts secret) is provisioned on
have failed. The session both ends of the encrypted
key has also expired, and circuit.
cryptographic operation
2 Manually initiate negotiation
has ceased.
of a new session key.
KEYXCH (Key Exchange-User)

“encryptionPortKeyExchangeForced”.
Table 211: KEYXCH (Standing Condition)

Severity
CH NA The system is attempting This condition is informative and

to negotiate a new no corrective action is needed.
session key as a result of
a manual request.
Standing Conditions
LASER (Laser-Fail)
The corresponding SNMP name for this condition is “laserFailure”.
Table 212: LASER (Standing Condition)

Severity
CH CR The laser providing Wait few seconds to determine if this

the optical output condition clears automatically (for
DCN signal for the example, when tuning or powering on
facility has failed. an SFP).
ETH
This condition may Do the following if this condition
OM also be raised persists:
momentarily If the facility is supported by a plug,
2OSCM MJ during powering on replace the plug. Otherwise, replace
OSCM or tuning of an the supporting module.
OSCM-PN SFP.
LASERON-DELAY (Laser-On Delay)

The corresponding SNMP name for this condition is “laserOnDelay”.
Table 213: LASERON-DELAY (Standing Condition)
AIDTYPE Probable Cause Suggested Corrective Action
CH The interface has been This condition is informative and requires no

configured to become corrective action.
operational and is in the
process of preparing to
switch on the laser.
This condition clears
when the laser is on.
Standing Conditions
LBCLANR (Laser-Current Abnormal)

The corresponding SNMP name for this condition is “laserBiasCurrAbnormal”.
Table 214: LBCLANR (Standing Condition)

Severity
CH MN The drive current This likely means that the laser is

required to obtain the aging and is approaching its end-
desired optical signal of-life point, at which time the
output power level laser will fail resulting in a traffic
ETH
from a laser affecting condition for the facility.
associated with the Replace the plug or module
facility is abnormally supporting the facility, as
OM high given the present appropriate, during the next
operating conditions. available scheduled maintenance
window.
LCK-ODU (ODU-Locked)
The corresponding SNMP name for this condition is “lockedDefectOdu”.
Table 215: LCK-ODU (Standing Condition)

Severity Corrective
Action
CH NR The facility has received a signal containing This

the locked indication code in the ODU path condition is
overhead, indicating that the signal has been informative
manually locked out at an upstream site. and requires
This is caused by a manual action taken at an no corrective
upstream node to suspend the traffic flow. action.
Such actions are typically taken either as a
part of maintenance and diagnostics
activities when troubleshooting a network
problem or to forcibly suspend traffic due to
business decisions such as non-payment of
fees.
Standing Conditions
LCK-TCMA (TCM_A-Lock)
The corresponding SNMP name for this condition is “lockedDefectOduTcmA”.
Table 216: LCK-TCMA (Standing Condition)

Severity Corrective
Action
CH NR The facility has received a signal containing This condition

the locked indication code in the tandem is informative
connection monitoring overhead for the TCMi and requires
layer assigned as instance “A”, indicating that no corrective
the signal has been locked out due to manual action.
actions at a point upstream after that at which
that tandem connection began.
This is caused by a manual action taken at an
upstream node to suspend the traffic flow.
Such actions are typically taken either as part
of maintenance and diagnostics activities
when troubleshooting a network problem, or
to forcibly suspend traffic due to business
decisions such as non-payment of fees.
LCK-TCMB (TCM_B-Lock)
The corresponding SNMP name for this condition is “lockedDefectOduTcmB”.
Table 217: LCK-TCMB (Standing Condition)

Severity Corrective
Action
CH NR The facility has received a signal This condition

containing the locked indication code in the is informative
tandem connection monitoring overhead for and requires no
the TCMi layer assigned as instance “B”, corrective
indicating that the signal has been locked action.
out due to manual actions at a point
upstream after that at which that tandem
connection began.
This is caused by a manual action taken at
an upstream node to suspend the traffic
flow. Such actions are typically taken
either as part of maintenance and
diagnostics activities when troubleshooting
a network problem, or to forcibly suspend
traffic due to business decisions such as
non-payment of fees.
Standing Conditions
LCK-TCMC (TCM_C-Lock)
The corresponding SNMP name for this condition is “lockedDefectOduTcmC”.
Table 218: LCK-TCMC (Standing Condition)

Severity Corrective
Action
CH NR The facility has received a signal containing This condition

the locked indication code in the tandem is informative
connection monitoring overhead for the and requires
TCMi layer assigned as instance “C”, no corrective
indicating that the signal has been locked out action.
due to manual actions at a point upstream
after that at which that tandem connection
began.
This is caused by a manual action taken at
an upstream node to suspend the traffic
flow. Such actions are typically taken either
as part of maintenance and diagnostics
activities when troubleshooting a network
problem, or to forcibly suspend traffic due to
business decisions such as non-payment of
fees.
Standing Conditions
LCP (Link Control Error)

The corresponding SNMP name for this condition is “linkControlProtocolFailure”.
Table 219: LCP (Standing Condition)

Severity
DCN MJ The Link Control 1 Verify that the configuration settings

Protocol (see of the PPPIP facility are correct.
“RFC 1661” for 2 Verify that the PPPIP facility is
details) used to cross-connected to the appropriate
configure and test data transmission facility.
the end-to-end
3 Verify that the data transmission
communications
facility to which the PPPIP facility
link with the far-
is connected is configured correctly,
end PPPIP facility
that there are no active conditions
was unable to
on that facility, and that this facility
complete the
is in-service normal (“In Service”).
configuration
message 4 Verify that each successive node in
exchange with the the link up to and including the far-
far-end, or has end PPPIP facility termination point
timed out awaiting is correctly configured, operating
a response from without active conditions which
the far-end. may impact the link, and that the
facilities are all in-service (“In
Service”).
LINKDOWN (External Link Fail)

The corresponding SNMP name for this condition is “linkDown”.
Table 220: LINKDOWN (Standing Condition)

Severity
DCN: MJ No carrier is Verify that the facility’s port is

LANIP detected, or an un- physically connected to an external
modulated carrier is device of the correct type and that
detected by the the device is operating correctly.
receiver.
DCN: { An un-modulated Verify that the facility’s port is

E10-100TX carrier is detected by physically connected to the
| E100FX } the receiver. intended port and that the port at
the far-end is provisioned and
ETH operating correctly.
SH
Standing Conditions
LKDO-AIS-L (Line-Auto Shutdown

AIS)
The corresponding SNMP name for this condition is “autoShutdownSendingAisLine”.
Table 221: LKDO-AIS-L (Standing Condition)

Severity Corrective
Action
CH NR The transmitted signal has been replaced This condition is

with the Alarm Indication Signal to informative and
suppress downstream condition reports requires no
due to a locally detected or upstream corrective action.
failure.
This condition occurs either as a result of
an AIS-L signal being received at a
physical or section terminating point
which must then be relayed downstream,
or as a result of a locally detected failure
condition on the incoming signal.
LKDO-AIS-ODU (ODU-Auto Shutdown

AIS)
The corresponding SNMP name for this condition is “autoShutdownSendingAisOdu”.
Table 222: LKDO-AIS-ODU (Standing Condition)

Severity Corrective
Action
CH NR The transmitted signal has been replaced This condition

with the ODU Alarm Indication Signal (AIS) is informative
due to a locally detected or upstream failure and requires no
affecting the ODU path layer signal. corrective
This condition typically occurs as a result action.
of a failure upstream of a point where an
OTN transponder resides or where an OTN
electrical regeneration function is
performed.
Standing Conditions
LKDO-AIS-ODU-RCV (ODU-Auto
Shutdown Rx AIS)
The corresponding SNMP name for this condition is “oduAutoShutdownRxAIS”.
Table 223: LKDO-AIS-ODU-RCV (Standing Condition)

Severity Action
CH NR The receive direction signal This condition is informative

VCH has been replaced with an and requires no corrective
VCHn ODU Alarm Indication action.
Signal (AIS), due to a locally Corrective action will be taken
detected or upstream failure in response to the failure
affecting the ODU path layer condition reported locally or
signal. The replacement upstream.
signal is transmitted
towards the Rx of the cross
connection.
LKDO-AIS-ODU-TRMT (ODU-Auto
Shutdown Tx AIS)
The corresponding SNMP name for this condition is “oduAutoShutdownTxAIS”.
Table 224: LKDO-AIS-ODU-TRMT (Standing Condition)

Severity Action
CH NR The transmit direction signal This condition is informative

VCH has been replaced with an and requires no corrective
VCHn ODU Alarm Indication action.
Signal (AIS) due to a locally Corrective action will be taken
detected or upstream failure in response to the failure
affecting the ODU path layer condition reported locally or
signal. upstream.
Standing Conditions
LKDO-AIS-OPU (OPU-Auto Shutdown

AIS)
The corresponding SNMP name for this condition is “autoShutdownSendingAisOpu”.
Table 225: LKDO-AIS-OPU (Standing Condition)

Severity Action
CH NR The transmitted signal has had This condition is informative

the client payload replaced with and no corrective action is
the generic Alarm Indication needed.
Signal (AIS) due to a failure of
the client signal.
LKDO-AIS-VF (Forward Client Fail)

The corresponding SNMP name for this condition is “clientFailForwarding”.
Table 226: LKDO-AIS-VF (Standing Condition)

Severity
CH NR The client signal mapped This condition is informative

via the reporting virtual and no corrective action is
facility instance has a needed. Corrective action will
severely degraded received be taken in response to the
signal level or a failure of signal degrade or signal failure
the received signal. condition reported by the client
facility.
Standing Conditions
LKDO-ALS (Auto Shutdown (ALS))

The corresponding SNMP name for this condition is “autoShutdownAls”.
Table 227: LKDO-ALS (Standing Condition)

Severity Cause
CH NR The optical Warning: This condition may play a role in

output power ensuring that laser safety precautions are met
level of the within the network, but may not, in itself,
facility has ensure that all laser safety levels are met.
been Use extreme caution when exposing any
decreased to optical connectors and when handling optical
DCN a level fibers and treat all optical signal paths as if
sufficient to they contain unsafe optical power levels until
ensure laser confirmed otherwise by actual power
eye safety measurements.
requirements This condition occurs as a result of a failure
for the detected in the received signal direction
ETH system are which suggests a fiber cable cut may have
met. occurred, necessitating optical laser safety
measures for the outbound signal be applied.
This condition is informative and no corrective
OM action is needed.
Standing Conditions
LKDO-AMP-APS (Auto Shutdown-Tx

Safety)
The corresponding SNMP name for this condition is “autoShutdownAmpAps”.
Table 228: LKDO-AMP-APS (Standing Condition)

Severity Action
OM CR The EDFA pre-amplifier/RAMAN This condition is

and the associated OSC detected informative. Corrective
a loss of signal (e.g. due to a fiber action should be taken
cut), triggering the corresponding to clear the loss of
EDFA booster amplifier to signal at the EDFA pre-
automatically shut down for safety amplifier /RAMAN and
reasons. OSC. Upon clearing the
The following conditions must be losses (e.g. fixing the
met to enable the booster amplifier fiber cut), the EDFA
auto shutdown feature: booster amplifier will
• Span equalization (SPEC- automatically recover,
CONF) and Auto Shutdown and the LKDO-AMP-
(AMP-APS) are enabled at APS condition clears.
both far-end and near-end
nodes.
• Corresponding EDFAs (pre-
amplifiers and booster
amplifiers) at both far-end and
near-end nodes are qualified,
meaning that the EDFAs are
equipped and provisioned, and
the required fiber map (within
the node) is provisioned.
LKDO-AMP (Amplifier-Auto
Shutdown)
The corresponding SNMP name for this condition is “autoAmpShutdown”.
Table 229: LKDO-AMP (Standing Condition)

OM NR The signal was interrupted because This condition is

the optical amplifier was shut informative and
down. The action is taken because requires no corrective
the last connection to an optical action.
signal within the optical multiplex
facility has been de-provisioned or
the optical multiplex signal has
failed.
Standing Conditions
LKDO-APS (Auto Shutdown-Power)

The corresponding SNMP name for this condition is “autoPowerShutdown”.
Table 230: LKDO-APS (Standing Condition)

Severity
OM: NR The optical Warning: This condition may play a

RAMAN Raman pump role in ensuring that laser safety
power level precautions are met within the
applied to the network, but may not, in itself, ensure
facility (counter- that all laser safety levels are met.
propagating Use extreme caution when exposing
applied to the any optical connectors and when
incoming fiber handling optical fibers and treat all
connected to the optical signal paths as if they contain
amplifier module) unsafe optical power levels until
has been confirmed otherwise by actual power
decreased to a measurements.
level sufficient to This condition occurs as a result of a
ensure laser eye detected failure in the received signal
safety direction which suggests a fiber cable
requirements for cut may have occurred, necessitating
the system are optical laser safety measures for the
met. optical pump signal be applied.
LKDO-ASETAB (Auto Shutdown-ASE

Table)
The corresponding SNMP name for this condition is “aseTableBuild”.
Table 231: LKDO-ASETAB (Standing Condition)

OM: NA The process of building the ASE This condition is

RAMAN table needed by the amplifier informative and no
module is in progress. This corrective action is
process must be performed needed.
whenever a RAMAN amplifier
module is installed or replaced.
Standing Conditions
LKDO-BLK (Auto Shutdown-Block)

The corresponding SNMP name for this condition is “autoShutdownBlock”.
Table 232: LKDO-BLK (Standing Condition)

Severity Action
CH NA For signals carrying added This condition is informative

traffic, the incoming signal and requires no corrective
from the client port has failed action. Corrective action will
or the client port add path be taken in response to the
fiber has been removed, signal failure condition
broken, severely bent or reported upstream.
sustained damage to an
optical connector. For through
path signals, the incoming
signal has failed, the
incoming channel has failed
or become severely
degraded, or the pass-through
connection fiber has been
removed, broken, severely
bent or has sustained
damage to an optical
connector.
Commands triggering If there is no upstream signal

equalization requests for failure condition, perform a
channels on a given module manual equalization on the
have been entered at a rate channel. If multiple such
which exceeds the maximum channels exist on the same
allowable limit. module, wait the minimum
recommended interval (5
seconds) before submitting
subsequent requests for the
other channels.
Standing Conditions
LKDO-CSF-OPU (OPU-Auto Shutdown

(CSF))
The corresponding SNMP name for this condition is “autoShutdownOpuClientSignalFail”.
Table 233: LKDO-CSF-OPU (Standing Condition)

Severity
CH NR The transmitted signal This condition is informative and

has had the client requires no corrective action.
payload replaced with the Corrective action will be taken in
generic Client Signal Fail response to the signal failure
(CSF) due to a failure of condition reported upstream.
the client signal.
LKDO-CSF-VF (VF-Auto Shutdown

(CSF))
The corresponding SNMP name for this condition is “autoShutdownVfCSF”.
Table 234: LKDO-CSF-VF (Standing Condition)

Severity
CH NR Due to a failure in the This condition is informative

received client signal, and requires no corrective
client Signal Fail (CSF) action. Corrective action will be
frames are inserted into the taken in response to the signal
client payload of the signal failure condition reported
transmitted to the network locally.
interface.
Standing Conditions
LKDO-EPC (Auto Shutdown (EPC))

The corresponding SNMP name for this condition is “autoShutdownSendingEPC”.
Table 235: LKDO-EPC (Standing Condition)

Severity
CH NR The transmitted This condition occurs either as a result

signal contains a of a locally detected failure in the signal
conditioning upstream of the outbound facility
signal indicating termination point or due to the need to
an upstream relay a like signal received from the
failure has upstream direction.
occurred.1 This condition is informative and
requires no corrective action.
LKDO-GAIS (Auto Shutdown (G-

AIS))
The corresponding SNMP name for this condition is “autoShutdownSendingGAIS”.
Table 236: LKDO-GAIS (Standing Condition)

CH NR The transmitted signal has been This condition is

replaced with the Generic Alarm informative and
Indication Signal (G-AIS) to suppress requires no
downstream condition reports due to a corrective action.
locally detected or upstream failure.
This condition occurs either as a result
of a G-AIS signal being received at a
physical or section terminating point
which must then be relayed
downstream, or as a result of a locally
detected failure condition on the
incoming signal.
1EPC signal details vary by facility type and include SONET/SDH Alarm Indication
Signals (AIS) and similar indications defined for OTN interfaces, Gigabit Ethernet,
Fiber Channel and related signal types.
Standing Conditions
LKDO-LCK-ODU (ODU-Auto
Shutdown)
The corresponding SNMP name for this condition is “autoShutdownSendingLckOdu”.
Table 237: LKDO-LCK-ODU (Standing Condition)

Severity
CH NR The transmitted This condition occurs when a

signal contains a manual action, either a provisioning
conditioning signal change or an active operation,
indicating a locked interrupts the transmission of a
status. signal, replacing the signal payload
with a locked indication. The change
or operation is intended to block
transmission of the signal for
administrative reasons.
LKDO-OCI-ODU (ODU-Auto Shutdown

(OCI))
The corresponding SNMP name for this condition is “autoShutdownSendingOciOdu”.
Table 238: LKDO-OCI-ODU (Standing Condition)

Severity
CH NA The cross connection If the connected path is in the

of which the reporting process of being torn down, and the
facility was the “TO” reporting facility is about to be
member has been de- deleted, no prior corrective action is
provisioned. required, otherwise the erroneously
deleted connection must be re-
provisioned.
Standing Conditions
LKDO-OCI-ODU-TRMT (ODU-Auto
Shutdown (Tx))
The corresponding SNMP name for this condition is “autoShutdownSendingOciOduTx”.
Table 239: LKDO-OCI-ODU-TRMT (Standing Condition)

Severity
CH NA The cross connection, If the connected path is in the

which the reporting process of being torn down, and the
facility is a member of, reporting facility is about to be
was deleted. Data is deleted, no corrective action is
missing in the client required,
transmit direction. Otherwise, re-provision the cross
connection.
LKDO-OFF (Auto Shutdown-Forward)

“autoShutdownLaserOffDueToErrFwd”.
Table 240: LKDO-OFF (Standing Condition)

Severity Cause
CH NR The facility is Warning: This condition may play a role in

OM not transmitting ensuring that laser safety precautions are
in order to met within the network, but may not, in
propagate a itself, ensure that all laser safety levels are
signal failure met. Use extreme caution when exposing
condition which any optical connectors and when handling
has occurred optical fibers and treat all optical signal
upstream. paths as if they contain unsafe optical
power levels until confirmed otherwise by
actual power measurements.
This condition occurs either as a result of a
locally detected failure in the signal
upstream of the outbound facility
termination point or due to the need to relay
a like signal received from the upstream
direction.
This condition is informative and requires no
corrective action.
Standing Conditions
LKDO-OPT (Auto Shutdown-Tx

Power)
“autoShutdownLaserOffDueToHighTxPwr”.
Table 241: LKDO-OPT (Standing Condition)

Severity
OM CR The transmitted Warning: This condition may play a role

optical signal has in ensuring that laser safety precautions
been turned off are met within the network, but may not,
due to the in itself, ensure that all laser safety levels
detection of are met. Use extreme caution when
abnormally high exposing any optical connectors and
output power when handling optical fibers and treat all
levels. optical signal paths as if they contain
unsafe optical power levels until
confirmed otherwise by actual power
measurements.
This condition may result from either a
failure of the pump laser drive and control
circuitry of the optical amplifier module or
from an excessive optical input power on
the input port of the amplifier stage
providing the output signal.
Verify that the input power level is within
the specified system limits (see T-OPR-
HT (Optical Power Rx High) for the
relevant procedure). If the input signal is
within the specified operating range of the
amplifier module, replace the amplifier
module.
LKDO-PROTN (Laser-Standby
Shutdown)
The corresponding SNMP name for this condition is “autoShutdownStbyProtection”.
Table 242: LKDO-PROTN (Standing Condition)

Severity Action
CH NR The transmitted optical signal This condition is

has been turned off as part of informative and no
the normal operation of the corrective action is
protection switching required.
mechanism.
Standing Conditions
LKDO-TEMP (Auto Shutdown-Temp

(Tx))
“autoShutdownLaserOffDueToHighTemp”.
Table 243: LKDO-TEMP (Standing Condition)

Severity
OM CR The transmitted This condition occurs to avoid or at least

optical signal has minimize possible damage to the
been turned off amplifier module due to excessive
due to the temperatures encountered by the module.
detection of 1 Verify that the equipment operating
abnormally high environment for the shelf containing
equipment the module meets specifications and
operating that the air filter is clean and
temperature unobstructed.
levels.
2 Verify that there are no abnormal
conditions or failures of the fan units
within the shelf containing the
module.
3 Verify that the module placement and
that the surrounding equipment
contained within the same shelf
conform to the product engineering
guidelines.
Standing Conditions
LKDO-TEMPA (Auto Shutdown-

Temp)
“autoShutdownTxRxLasersDueToHighTemp”.
Table 244: LKDO-TEMPA (Standing Condition)

Severity
CH CR The transmit and This condition occurs to avoid or at

receive facilities of least minimize possible damage due to
the network excessive temperature levels
interface were encountered by the module.
turned off due to the 1 Verify that the equipment
detection of operating environment of the shelf
abnormally high containing the module meets
equipment operating specifications, and that the air
temperature levels. filter is clean and unobstructed.
2 Verify that there are no abnormal
conditions or failures of the fan
units within the shelf containing
the module.
3 Verify the module placement and
conform to the product’s
Standing Conditions
LOA (Loss of Alignment)

The corresponding SNMP name for this condition is “lossOfAlignment”.
Table 245: LOA (Standing Condition)

Severity
CH CR • Fault on one or 1 Resolve any faults on the lanes.

more lanes of 2 Verify that the optical signal path
the incoming for each lane follows the same
signal. path.
• Path 3 Verify that the optical signals
differences. meet the specifications,
especially Polarization Mode
Dispersion (PMD). Correct any
lanes that violate the
specifications.
4 Replace the plug.
5 Replace the far-end plug or
module.
Standing Conditions
LOCAL_FAULT (Local Fault)

The corresponding SNMP name for this condition is “localFault”.
Table 246: LOCAL_FAULT (Standing Condition)

Severity Cause
CH NA The received This condition may be transient in nature if

signal has the far-end device was replaced or reset. If
received a local the condition persists for an unacceptably
fault sequence long period, proceed as follows:
status 1 Verify that the near and far-end
indication at the facilities are both provisioned correctly
PHY. and that they are of the same type,
have compatible properties and that
both facilities are in service.
2 Verify that the near and far-end
supporting equipment (plugs and/or
modules) are provisioned correctly and
that they are of the correct type, have
compatible properties and are in
service. Perform corrective actions for
any conditions reported by these
entities.
3 Verify that the incoming cable is the
correct cable and that the transmit and
receive ports are connected to their
4 Replace the near-end plug or module
5 Replace the far-end plug or module
supporting the far-end facility.
LOCAL_FAULT-RX (Local Fault Rx)

The corresponding SNMP name for this condition is “localFaultRx”.
Table 247: LOCAL_FAULT-RX (Standing Condition)

Severity Cause
CH NA The upstream This condition is informative and requires

equipment no corrective action. Corrective action will
has reported a need to be taken in response to the signal
fault. failure reported upstream.
Standing Conditions
LOCAL_FAULT-TX (Local Fault Tx)

The corresponding SNMP name for this condition is “localFaultTx”.
Table 248: LOCAL_FAULT-TX (Standing Condition)

Severity Cause
CH NA The 1 Check the upstream equipment for a

upstream local fault. If needed, take corrective
equipment action in response to the signal failure
has reported reported upstream.
a local fault. 2 Replace the module or plug.
The fault is
on the
module or the
plug.
LOCLANR (Rx Laser-Abnormal)

The corresponding SNMP name for this condition is “localOscLevelAbnormal”.
Table 249: LOCLANR (Standing Condition)

Severity
CH MN The drive current, This likely means that the laser is

required to obtain the aging and is approaching its end-of-
desired optical signal life point, at which time the laser will
output power level fail resulting in a traffic affecting
from a laser used for condition for the facility.
the facility coherent Replace the plug or module
signal detection, is supporting the facility, as
abnormally high given appropriate, during the next available
the present operating scheduled maintenance window.
conditions.
Standing Conditions
LOF-GFP (GFP-Loss of Frame)

The corresponding SNMP name for this condition is “lossOfGfpFrame”.
Table 250: LOF-GFP (Standing Condition)

Severity
CH CR The equipment is unable 1 Verify that the facility is provisioned

to lock onto the Generic correctly at both the near and far-end.
Framing Protocol core 2 Verify that the incoming cable is the correct
header (which acts as cable and that the transmit and receive
the GFP framing pattern) ports are connected to their proper
in the drop direction. respective portions of the cable (i.e. that the
The most likely causes fibers are not swapped between transmit
of this condition are a and receive or that a crossover cable has
degraded network side not been used in place of a straight cable for
signal, or a failure of the electrical Ethernet connections).
GFP mapper at the
upstream aggregation 3 Verify that the incoming cable (electrical or
point. optical) is firmly connected to the receive
port associated with the facility and that the
connector is not physically impaired by
obstructions, dirt or component damage.
Clean the connector or replace the cable,
plug or module, as appropriate, depending
and maximum power levels). If the signal
meets the required specifications proceed
to the next step below, otherwise locate the
source of the signal problem upstream and
repair the problem.
facility.
facility.
facility.
8 Replace the near-end module supporting
the facility.
Standing Conditions
LOF-MUX (MUX-Loss of Frame)

The corresponding SNMP name for this condition is “lossOfFrameMux”.
Table 251: LOF-MUX (Standing Condition)

Severity
CH CR The demultiplexer 1 Verify that the facility is

is unable to lock provisioned correctly.
onto the framing 2 Verify that the incoming cable is
pattern in one or the correct cable and that the
both of the transmit and receive ports are
multiplexed signals connected to their proper
within the incoming respective portions of the cable
signal. (i.e. that the fibers are not
The most likely swapped between transmit and
causes of this receive or that a crossover cable
condition are a has not been used in place of a
degraded F2488 straight cable for electrical
signal, a failure of Ethernet connections).
the upstream
equipment 3 Verify that the incoming cable
originating the (electrical or optical) is firmly
signal, or a failure connected to the receive port
of the payload associated with the facility and
signal prior to the that the connector is not physically
aggregation point at impaired by obstructions, dirt or
the far-end. component damage. Clean the
connector or replace the cable,
plug or module, as appropriate,
examination.
the cable termination and that the
signal conforms to the required
maximum power levels). If the
signal meets the required
specifications proceed to the next
step below, otherwise locate the
source of the signal problem
Standing Conditions
LOF-OTU (OTU-Loss of Frame)

The corresponding SNMP name for this condition is “lossOfFrameOtu”.
Table 252: LOF-OTU (Standing Condition)

Severity
CH CR The receiver is 1 Verify that the facility is

unable to lock onto provisioned correctly.
the framing pattern 2 Verify that the incoming cable is
in the incoming the correct cable and that the
signal. transmit and receive ports are
This may be due to connected to their proper
a degraded signal or respective portions of the cable
failure of the (i.e. that the fibers are not
equipment swapped between transmit and
originating the receive or that a crossover cable
signal. has not been used in place of a
straight cable for electrical
Ethernet connections).
3 Verify that the incoming cable
(electrical or optical) is firmly
connected to the receive port
associated with the facility and
that the connector is not
physically impaired by
obstructions, dirt or component
damage. Clean the connector or
replace the cable, plug or module,
as appropriate, depending upon
the cause determined from the
Standing Conditions
LOF-S (Sec/RS-Loss of Frame)

The corresponding SNMP name for this condition is “lossOfFrame”.
Table 253: LOF-S (Standing Condition)

Severity
CH} CR The receiver is 1 Verify that the facility is

unable to lock onto provisioned correctly.
the framing pattern 2 Verify that the incoming cable is
in the incoming the correct cable and that the
signal. transmit and receive ports are
The most likely connected to their proper
causes of this respective portions of the cable
condition are a (i.e. that the fibers are not
degraded signal or a swapped between transmit and
failure of the receive or that a crossover cable
upstream equipment has not been used in place of a
originating the straight cable for electrical
signal. Ethernet connections).
that the connector is not physically
connector or replace the cable,
plug or module, as appropriate,
examination.
step, otherwise locate the source
of the signal problem upstream
Standing Conditions
LOFLOM-ODU (ODU-Loss of
Frame/LOM)
“lossOfFrameLossOfMultiFrameOdu”.
Table 254: LOFLOM-ODU (Standing Condition)

Severity
CH CR The receiver is unable to 1 Verify that both the near-end and far-end
lock onto the framing facilities are provisioned correctly and
pattern, and/or to verify are in-service, and that the far-end
the correct sequence in associated client facility is provisioned
the multi-frame alignment correctly and is in-service.
signal that is obtained by 2 Verify that the incoming cable is the
demultiplexing the correct cable and that the transmit and
incoming receive ports are connected to their
(network side) signal. proper respective portions of the cable
This may be due to a
degraded signal or failure
between transmit and receive or that a
of the upstream
crossover cable has not been used in
equipment that originated
place of a straight cable for electrical
the signal.
3 Verify that the incoming cable (electrical
or optical) is firmly connected to the
receive port associated with the facility
and that the connector is not physically
module, as appropriate, depending upon
examination.
conforms to the required specifications
(e.g. minimum and maximum power
levels). If the signal meets the required
specifications proceed to the next step
below, otherwise locate the source of
the signal problem upstream and repair
the problem.
5 Replace the plug or module supporting
the facility.
Standing Conditions
LOL (Loss of Lane Alignment)

The corresponding SNMP name for this condition is “lossOfLane”.
Table 255: LOL (Standing Condition)

Severity
CH MN The signals in one 1 Check the physical cabling associated with the facilities
or more lanes of the port and ensure that the correct type of cable is used, and
multi-line received that the cable is intact and that it has not been damaged or
signal are not repaired. If the cable is of the incorrect type, is damaged or
correctly aligned (in appears to have been repaired (e.g. spliced), replace the
time) relative to the cable with a new, undamaged/unrepaired cable of the
signals within the correct type.
other lanes. 2 Progressing upstream from the receiver, verify that the
optical signal paths of each lane of the channel pass
through the same multi-channel module at a given point
along the path, and that each fiber jumper cable is of the
correct type, is undamaged and unrepaired. If the lanes are
split so that different lanes traverse different fiber jumpers
at any point, ensure that each of these fiber jumpers is of
the correct type and identical length, and that each is
undamaged and unrepaired. Replace any cables found to
violate these rules, and correct any signal flow routings
which send the lanes through different multi-channel
modules at a given point along the path.
3 Verify that each optical span along the path taken by the
multi-lane channel signal conforms to the engineered
specifications for that link, especially that each link
conforms to its specified limitations for Polarization Mode
Dispersion (PMD). Correct any links that violate the span
engineering specifications.
4 Verify that each optical dispersion compensation element
along the path taken by the multi-lane channel signal
conform to the engineered requirements and correct any
which do not.
5 Replace the plug or module supporting the facility, as
appropriate.
6 Replace the far-end plug or module which is the source of
the multi-lane channel signal, as appropriate.
Standing Conditions
LOL-OTU (OTU-Loss of Lane Align)

The corresponding SNMP name for this condition is “lossOfLaneOtu”.
Table 256: LOL-OTU (Standing Condition)

Severity
CH CR The signals in one or 1 Check the physical cabling associated with the
more lanes of the facilities port and ensure that the correct type of
multi-lane received cable is used, and that the cable is intact and
signal are not has not been damaged or repaired. If the cable is
correctly aligned (in of the incorrect type, is damaged or appears to
time) relative to the have been repaired (e.g. spliced), replace the
signals within the cable with a new, undamaged/unrepaired cable
other lanes, or at of the correct type.
least one of the lanes 2 Progressing upstream from the receiver, verify
has failed. that the optical signal paths of each lane of the
channel pass through the same multi-channel
module at a given point along the path, and that
each fiber jumper cable is of the correct type, is
undamaged and unrepaired. If the lanes are split
so that different lanes traverse different fiber
jumpers at any point, ensure that each of these
fiber jumpers is of the correct type and identical
length, and that each is undamaged and
unrepaired. Replace any cables found to violate
these rules, and correct any signal flow routings
which send the lanes through different multi-
channel modules at a given point along the path.
3 Verify that each optical span along the path
taken by the multi-lane channel signal conforms
to the engineered specifications for that link,
especially that each link conforms to its
specified PMD limitations. Correct any links that
violate the span engineering specifications.
4 Verify that each optical dispersion compensation
element along the path of the multi-lane channel
signal conform to the engineered requirements
and correct any that do not.
5 Replace the plug or module supporting the
facility, as appropriate.
6 Replace the far-end plug or module that is the
source of the multi-lane channel signal, as
appropriate.
Standing Conditions
LOM-LP (Path LO-Loss Multiframe)

The corresponding SNMP name for this condition is “lossofMultiframeLowerOrderPath”.
Table 257: LOM-LP (Standing Condition)

Severity
VC3 CR The receiver is unable to verify 1 Verify that both the near-end and far-end
a correct sequence of values facilities are provisioned correctly and are in-
in the multi-frame alignment service normal (“In Service”), and that the far-
signal for the path end associated client facility is provisioned
demultiplexed from the correctly and is in-service normal (“In
incoming (network side) Service”).
signal. 2 Verify that the incoming cable is the correct
The most likely causes of this cable and that the transmit and receive ports
condition are a degraded signal are connected to their proper respective
or a failure of the upstream portions of the cable (i.e. that the fibers are not
equipment originating the swapped between transmit and receive).
signal.
3 Verify that the incoming fiber is firmly
connected to the receive port associated with
the facility and that the connector is not
physically impaired by obstructions, dirt or
component damage. Clean the connector or
replace the cable, plug or module, as
appropriate, depending upon the cause
determined from the physical examination.
termination and that the signal conforms to the
required specifications (e.g. minimum and
maximum power levels). If the signal meets
the required specifications proceed to the next
step below, otherwise locate the source of the
signal problem upstream and repair the
problem.
facility.
facility.
7 Replace the near-end module supporting the
facility.
facility.
Standing Conditions
LOM-OTU (OTU-Loss of Multiframe)

The corresponding SNMP name for this condition is “lossOfMultiFrameOtu”.
Table 258: LOM-OTU (Standing Condition)

Severity
CH CR The receiver has 1 Verify that the facility is

detected an provisioned correctly.
erroneous sequence 2 Verify that the incoming cable is
of values in the multi- the correct cable and that the
frame alignment transmit and receive ports are
signal (MFAS) connected to their proper
overhead byte in the respective portions of the cable
incoming (i.e. that the fibers are not
signal. swapped between transmit and
This may be due to a
receive or that a crossover cable
degraded signal or
has not been used in place of a
failure of the
straight cable for electrical
equipment
originating the signal.
that the connector is not
physically impaired by
Standing Conditions
LOM-P (Path-Loss of Multiframe)

The corresponding SNMP name for this condition is “lossofMultiframeHigherOrderPath”.
Table 259: LOM-P (Standing Condition)

Severity
STS1, CR The receiver is unable to 1 Verify that both the near-end and far-end
STS3C verify a correct sequence facilities are provisioned correctly and are in-
VC4 of values in the multi-frame service normal (“In Service”), and that the far-
alignment signal for the end associated client facility is provisioned
path demultiplexed from correctly and is in-service normal (“In Service”).
the incoming (network side) 2 Verify that the incoming cable is the correct
signal. cable and that the transmit and receive ports
The most likely causes of are connected to their proper respective
this condition are a portions of the cable (i.e. that the fibers are not
degraded signal or a failure swapped between transmit and receive).
of the upstream equipment
originating the signal. 3 Verify that the incoming fiber is firmly
maximum power levels). If the signal meets the
required specifications proceed to the next step
below, otherwise locate the source of the signal
facility.
6 Replace the far-end plug supporting the facility.
7 Replace the near-end module supporting the
facility.
facility.
Standing Conditions
LOOMFI-OPU (OPU-Loss of Frame

Align)
The corresponding SNMP name for this condition is “lossOfMfiOpu”.
Table 260: LOOMFI-OPU (Standing Condition)

Severity
CH CR The receiver is unable to 1 Verify both the near-end and far-end facilities are
verify a correct sequence provisioned correctly and are In Service (IS), and
of values in the multi- that the far-end associated client facility is
frame alignment signal provisioned correctly and is In Service.
for the path de- 2 Verify the incoming fiber is the intended one and
multiplexed from the that the transmit and receive fibers are connected to
incoming (network side) the proper side of the connector (the fibers are not
signal. swapped between transmit and receive).
The most likely causes
of this condition are a 3 Verify optical power is present on the receive
degraded signal or a interface and is within optical specifications (for
failure of the upstream example, minimum and maximum power levels). If
equipment originating the the optical power does not meet the required
signal. specifications, proceed to the next step. Otherwise
locate the source of the signal problem upstream
and repair the problem
4 Verify the incoming fiber is firmly connected to the
receive port associated with the facility and that the
incoming connector is clean. If necessary, replace
the fiber, plug, or module.
5 Replace the near-end plug supporting the facility.
7 Replace the near-end module supporting the facility.
8 Replace the far-end module supporting the facility.
Standing Conditions
LOP-LP (Path LO-Loss of Pointer)

The corresponding SNMP name for this condition is “lossOfPointerLowerOrderPath”.
Table 261: LOP-LP (Standing Condition)

Severity
VC3 CR The incoming 1 Verify that the received signal

pointer value is in meets the required specifications
error (i.e. a valid for stability of its timing fence and
pointer value has for ones-density. Look for
not been received abnormally high rates of pointer
for a given period of justifications as an indication that
time as defined by the timing of the signal may be
the relevant unstable.
standards). 2 Replace the near-end plug
This condition is supporting the facility.
typically caused by
either a problem 3 Replace the near-end module
with the supporting the facility.
synchronization of 4 Replace the far-end plug
the incoming signal supporting the facility.
or due to an 5 Replace the far-end module
equipment failure at supporting the facility.
the near or far-end
pointer processing
equipment.
Standing Conditions
LOP-P (Path-Loss of Pointer)

The corresponding SNMP name for this condition is “lossOfPointerHigherOrderPath”.
Table 262: LOP-P (Standing Condition)

Severity
STS1, CR The incoming pointer 1 Verify that the received signal

STS3C, value is in error (i.e. a meets the required
STS24C, valid pointer value specifications for stability of its
STS48C has not been received timing fence and for ones-
for a given period of density. Look for abnormally
VC4, time as defined by the high rates of pointer
VC4C8, relevant standards). justifications as an indication
VC4C16 This condition is that the timing of the signal
typically caused by may be unstable.
either a problem with 2 Replace the near-end plug
the synchronization supporting the facility.
of the incoming signal
or due to an 3 Replace the near-end module
equipment failure at supporting the facility.
the near or far-end 4 Replace the far-end plug
pointer processing supporting the facility.
equipment. 5 Replace the far-end module
Standing Conditions
LOS (Loss Of Signal)

The corresponding SNMP name for this condition is “lossOfSignal”.
Table 263: LOS (Standing Condition)

Severity
CH CR1 The receiver has 1 Verify that the facility is provisioned correctly.
detected a loss of the 2 Verify that the incoming cable is the correct cable and
DCN input signal.2 that the transmit and receive ports are connected to
their proper respective portions of the cable (i.e. that the
fibers are not swapped between transmit and receive or
that a crossover cable has not been used in place of a
ETH
straight cable for electrical Ethernet connections).
SH 3 Verify that the incoming cable (electrical or optical) is
firmly connected to the receive port associated with the
facility and that the connector is not physically impaired
by obstructions, dirt or component damage. Clean the
connector or replace the cable, plug or module, as
OM: The receiver for the
appropriate, depending upon the cause determined from
SWITCH signal carried by pilot
the physical examination.
laser has detected a
loss of the input 4 Verify that a signal is present at the cable termination
signal. and that the signal3 conforms to the required
specifications (e.g. minimum and maximum power
OM: The incoming optical levels). If the signal meets the required specifications
{ EDFA | signal power level has proceed to the next step below, otherwise locate the
EDFA- fallen below the source of the signal problem upstream and repair the
MID | OM minimum level able to problem.
|RAMAN} be detected by the
input monitor.
1For 2OSCM, OSCM, OSCM-PN, EROADM-DC, SCU-E, and SCU-II modules, the
default severity is MJ
2The exact definition of loss of signal varies by facility type, and may include a loss of the
carrier, an extremely high rate of bit errors or coding violations, a loss of the ability to
recovery a clock signal from the received signal or other factors
3In the case of the OM:SWITCH facilities, the signal referred to here is that of the pilot
laser, and it may be necessary to either disable the remaining channels within the line or
to use a filter or wavelength selective filter in order to perform measurements on the
received power for the pilot laser wavelength alone. In the case of the OM:RAMAN,
OM:EDFA and OM:EDFA-MID facilities, the signal is the composite power level of the
multi-wavelength signal.
Standing Conditions
LOS-P (Loss Of Input Signal)

The corresponding SNMP name for this condition is “lossOfInputSignal”.
Table 264: LOS-P (Standing Condition)

Severity Cause
CH CR Input signal 1 Verify that the optical signal power is

failure. within the receive specifications. If
needed, correct the optical path.
2 Verify that the upstream equipment is
transmitting. If needed, enable
upstream equipment.
3 Verify that the port is provisioned to
match the transmitted signal.
4 Replace the module or plug.
LOSATT (Acquiring LOS Level)

The corresponding SNMP name for this condition is “losAttProgress”.
Table 265: LOSATT (Standing Condition)

Severity Action
CH NA The optical channel is affected by This condition is

the analysis and adjustment informative in nature and
procedure conducted to determine no corrective action is
the loss of signal threshold level required.
for the channel.
Standing Conditions
LOSC (Loss of OSC)

The corresponding SNMP name for this condition is “lossOsc”.
Table 266: LOSC (Standing Condition)

Severity
OM: CR The incoming 1 Verify that the incoming cable is the

RAMAN optical signal correct cable and that the transmit
power level of the and receive ports are connected to
OSC signal has their proper respective portions of
fallen below the the cable (i.e. that the fibers are not
minimum level swapped between transmit and
able to be receive).
detected by the 2 Verify that the OSC facility
input monitor. transmitted by the far-end is
correctly configured, that it is
operating normally, and that it is
correctly connected into the
transmission fiber.
3 Verify that the incoming fiber is
or module, as appropriate,
examination.
5 Replace the module supporting the
facility.
Standing Conditions
LOSFWD-GFP (GFP-Client Loss)

The corresponding SNMP name for this condition is “gfpLossOfClientSig”.
Table 267: LOSFWD-GFP (Standing Condition)

Severity
CH NR The signal received from This condition occurs as a result

the far-end GFP facility of a locally detected failure in the
termination contains a signal at the far-end GFP facility
conditioning signal termination point.
indicating that the This condition is informative and
received client signal no corrective action is needed.
being mapped at that
point has failed.
LPBKERR (PPP/IP Loop Error)

The corresponding SNMP name for this condition is “loopbackError”.
Table 268: LPBKERR (Standing Condition)

Severity
CH MJ A communication This condition indicates a network

loop has been problem which may or may not be due
detected in the path to local issues. Starting at the node
supported by the where the facility reporting the
reporting facility. condition is located, verify that the
cabling and provisioning of each of the
elements along the path represented by
the reporting facility.
Standing Conditions
LPBKFACILITY (Loopback - Facility)

This condition is only possible when the entity is in an OOS-MT state, which will
The corresponding SNMP name for this condition is “facilityLoopback”.
Table 269: LPBKFACILITY (Standing Condition)

Severity
CH NA A facility A facility loopback operation is typically

loopback performed as a part of service affecting
operation is in maintenance or testing activities. This
effect, forcing the condition is informative and no
received signal to corrective action is needed.
ETH be echoed on the
transmit direction
in place of the
normal signal.
LPBKTERM (Loopback-Terminal)
This condition is only possible when the entity is in an OOS-MT state, which will
The corresponding SNMP name for this condition is “terminalLoopback”.
Table 270: LPBKTERM (Standing Condition)

Severity
CH NA A terminal loopback A terminal loopback operation is

operation is in effect, typically performed as a part of
forcing the received service affecting maintenance or
signal to be ignored and testing activities. This condition is
ETH replaced by the same informative and no corrective
signal which is being action is needed.
transmitted on this
facility.
Standing Conditions
LSS-OPU (OPU-Loss of Test Synch)

The corresponding SNMP name for this condition is “lossOfTestSeqSynchOpu”.
Table 271: LSS-OPU (Standing Condition)

Severity
CH NA The received signal 1 Verify that the receiving facility is

is expected to correctly set to operate in the
contain a PRBS test PRBS reception test mode. If the
sequence but the facility should not be operating in
receiver is unable to this mode, release the PRBS
synchronize to the receive test control and restore
expected pattern, or the facility to normal service.
if the bit-error ratio of 2 Verify that the far-end facility is
the received signal set to operate in PRBS test
exceeds 0.2 during signal insertion mode. If the
an integration period facility is not operating in that
of 1 second. mode, place it into this mode.
3 Examine the Performance
Monitoring counters for the
current interval and determine
whether the bit-error rate on the
received signal is excessive
relative to the expected
performance of the engineered
path. If it is excessive, it
indicates a signal quality
degradation along the path.
Proceeding upstream along the
path, verify the optical power
levels of the signal are within the
path, and correct any elements
which are outside their
engineering specifications. This
may involve performing span
equalization adjustments or
optical power setting
adjustments at various control
points along the path.
4 Replace the plug or module, as
appropriate, supporting the
facility.
appropriate, supporting the far-
end of the facility.
Standing Conditions
LTC-TCMA (TCM_A-Connection Loss)

“lossofTandemConnectionOduTcmA”.
Table 272: LTC-TCMA (Standing Condition)

Severity
CH MN The facility has received 1 Verify that the correct TCMi

a signal in which the has been assigned to this
tandem connection instance (i.e. verify the TCMA
monitoring overhead for attribute value).
the TCMi layer assigned 2 Verify that the intended
as instance “A” contains upstream facility has the same
the “No source TC” code TCMi assigned to one of its
(“000” in the STAT field, TCMA, TCMB or TCMC
bits 6 through 8 of byte 3 attributes, and that the facility
in the TCM overhead) is correctly provisioned in all
indicating that the far- other respects and is in-
end tandem connection service normal (“In Service”).
termination point has not
3 Verify that there are no errors
been provisioned.
This is caused by in cabling or cross-connection
assigning an unused at each successive upstream
TCMi to this instance. point along the trail back to the
far-end tandem connection
termination point.
Standing Conditions
LTC-TCMB (TCM_B-Connection Loss)

“lossofTandemConnectionOduTcmB”.
Table 273: LTC-TCMB (Standing Condition)

Severity
CH MN The facility has 1 Verify that the correct TCMi has

received a signal in been assigned to this instance
which the tandem (i.e. verify the TCMB attribute
connection monitoring value).
overhead for the TCMi 2 Verify that the intended
layer assigned as upstream facility has the same
instance “B” contains TCMi assigned to one of its
the “No source TC” TCMA, TCMB or TCMC
code (“000” in the attributes, and that the facility is
STAT field, bits 6 correctly provisioned in all other
through 8 of byte 3 in respects and is in-service
the TCM overhead) normal (“In Service”).
indicating that the far-
3 Verify that there are no errors in
end tandem
cabling or cross-connection at
connection
each successive upstream
termination point has
point along the trail back to the
not been provisioned.
far-end tandem connection
This is caused by
termination point.
assigning an unused
TCMi to this instance.
Standing Conditions
LTC-TCMC (TCM_C-Connection Loss)

“lossofTandemConnectionOduTcmC”.
Table 274: LTC-TCMC (Standing Condition)

Severity
CH MN The facility has 1 Verify that the correct TCMi has

received a signal in been assigned to this instance
which the tandem (i.e. verify the TCMC attribute
connection value).
monitoring overhead 2 Verify that the intended upstream
for the TCMi layer facility has the same TCMi
assigned as instance assigned to one of its TCMA,
“C” contains the “No TCMB or TCMC attributes, and
source TC” code that the facility is correctly
(“000” in the STAT provisioned in all other respects
field, bits 6 through 8 and is in-service normal (“In
of byte 3 in the TCM Service”).
overhead) indicating
3 Verify that there are no errors in
that the far-end
cabling or cross-connection at
tandem connection
each successive upstream point
termination point has
along the trail back to the far-end
not been provisioned.
This is caused by tandem connection termination
assigning an unused point.
TCMi to this
instance.
Standing Conditions
MANSW (Manual Switch)

The corresponding SNMP name for this condition is “mansw”.
Table 275: MANSW (Standing Condition)

Severity
CH NA A manual protection This condition is informative and no

switch operation corrective action is needed.
has been performed Note : This condition is reported only for
and the traffic is protection groups operating in a
switched to the revertive manner. In non-revertive
protecting member configurations, the transient conditions
of the protection MANWKSWPR (Manual
group. SwitchToProtect) and WKSWBK (Auto
SwitchToWorking) are issued for
changes in protection state due to
manual switching operations.
ETH A manual protection This condition is informative and no

switch operation corrective action is needed.
has been performed Note : This condition is reported for all
and the traffic is flow protection groups regardless of
switched to the whether or not they are operating in a
protecting member revertive manner. The transient
of the protection conditions MANWKSWPR (Manual
group. SwitchToProtect) and MANWKSWBK
(Manual SwitchToWorking) are also
issued for changes in flow protection
group protection state due to manual
switching operations, regardless of
whether the group is operating in
revertive or non-revertive mode.
MEA-ACCEPT (Plug-Incompatible)
The corresponding SNMP name for this condition is “equipmentNotAccepted”.
Table 276: MEA-ACCEPT (Standing Condition)

Severity
PL CR The physically inserted Review the provisioning

plug is of a type other attributes associated with the
than that which is plug and replace the
provisioned. unacceptable plug with one of
the required type.
Standing Conditions
MEA-ALW (Equipment-Allow
Mismatch)
The corresponding SNMP name for this condition is “equipmentMismatchAllow.”
Table 277: MEA-ALW (Standing Condition)

Severity Action
MOD MJ The equipment position Delete the module or the other

conflicts with another module which extends into the
provisioned module. slot(s) required by the module
reporting this alarm.
MEA-APPROVE (Plug-Not Approved)

The corresponding SNMP name for this condition is “equipmentNotApproved”.
Table 278: MEA-APPROVE (Standing Condition)

Severity
PL CR The physically Review the provisioning attributes

inserted plug is not associated with the plug and replace
an approved plug. the unacceptable plug with one of
the required type.
Standing Conditions
MEA-AUTOSRV (Protection Rate

Mismatch)
The corresponding SNMP name for this condition is “autoServiceMismatch."
Table 279: MEA-AUTOSRV (Standing Condition)

Severity Action
VCH MJ When protected services are 1 Wait a few minutes to

configured with adaptive determine if the alarm
facility types, the module clears automatically. If
could have different rates on the alarm persists,
the working and protection proceed to the next
paths due to one of these steps.
reasons: 2 Check the Facility Rate
• If the service (facility rate) Detected on the
is changed at the source working and protection
point of an adaptive facility paths.
type, the time taken to 3 Set the admin state of
communicate this change the protection path
over working and VCH to "Disabled,"
protection paths may then to "In Service."
differ. For the time
4 If the alarm persists,
difference, this alarm
check the far-end node,
would be raised. Once the
to ensure that the
second path is adapted,
correct client signal is
the alarm clears
sent on the protection
automatically based on
path.
the FCPF (Fault Cause
Persistency Filter)
settings.
• If the protected service
does not originate from the
same source through a
constant bridge (for
example, in video
services), one service
may have been changed
and the other not yet. This
alarm will be raised until
the second service is
changed (and the change
is communicated).
Standing Conditions
MEA-CAPABILITY (Capability
Mismatch)
The corresponding SNMP name for this condition is “capabilityLevelMismatch”.
Table 280: MEA-CAPABILITY (Standing Condition)

Severity Action
MOD MJ The capability level of the module Review the provisioned

physically inserted in the identified settings for the module
position does not meet or exceed and then replace the
the provisioned level. The incompatible module
mismatch occurs only if the correct with one matching the
module type is equipped but the provisioned attributes.
capability level of that module is
below the level provisioned.
MEA-CHANNEL (Channel Mismatch)

The corresponding SNMP name for this condition is “channelMismatch”.
Table 281: MEA-CHANNEL (Standing Condition)

Severity
ECH CR The external Review the provisioned settings for the

channel facility has facility and determine whether the
been provisioned provisioned settings match that of the
with a channel remote equipment port represented by
assignment the facility. If the provisioned values
incompatible with are correct, this suggests that the
the channel-specific remote equipment is connected to the
port to which it has wrong port, and appropriate
been connected. provisioning and cabling changes
should be made. If the provisioned
values are incorrect, change them to
the correct values, consistent with the
values supported by the remote
equipment port.
Standing Conditions
MEA (Equipment Mismatch)

The corresponding SNMP name for this condition is “mismatch”.
Table 282: MEA (Standing Condition)

Severity Action
MOD CR The module physically inserted in Review the provisioned

the identified position does not settings for the
PSU1HU- MN match the provisioned type. The module/plug and
AC mismatch may be due to the wrong replace the
PSU7HU-
module type, or the correct type incompatible
AC
with an incompatible element such module/plug with one
PSU7HU-
as an on-board laser with a matching the
DC
wavelength different than what is provisioned attributes.
PSU9HU-
provisioned.
DC
2OSCM MJ
OSCM
OSCM-
PN
PSCU
SCU
SCU-E
SCU-S
MEA-CONF (Configuration Mismatch)

This condition applies to 10WXC-PCN-10G modules only. The corresponding SNMP
name for this condition is “configurationMismatch”.
Table 283: MEA-CONF (Standing Condition)

Severity
MOD NA The module's settings 1 Using NED, delete the module.

do not match the 2 Reprovision the module.
settings in the NCU
database.
Standing Conditions
MEA-DIFFER (Plug-Provision
Mismatch)
The corresponding SNMP name for this condition is “equipmentMismatch”.
Table 284: MEA-DIFFER (Standing Condition)

PL CR The physically inserted plug exceeds Review the

the provisioned RATE or REACH provisioning
settings. Note that in this case, the attributes
plug may be able to provide signal associated with the
transport, but the specifications of the plug position and
signal may not conform to the replace the
provisioned settings (e.g. the optical unacceptable plug
power level may be too high). with one of the
required type.
MEA-FC-TX (Fiber-Connect Error Tx)

The corresponding SNMP name for this condition is “fiberConnMismatchTx”.
Table 285: MEA-FC-TX (Standing Condition)

Severity
PTP NR The port associated Note: This condition is normally not

with this fiber reported, and corrective actions are
connection has typically performed in response to the
determined that it MEA-FC (Fiber-Connect Error)
does not match the condition, which is reported by the
connections module at the opposite end of the
provisioned within fiber.
the system’s 1 Carefully trace the fiber to the far-
database. end port and determine to which
port the fiber is connected.
Review the intended fiber
connection provisioning plan and
adjust the fiber connections at
either or both ends so that they
conform to the plan, or correct the
connection provisioning if it is
found to be in error.
Standing Conditions
MEA-FC (Fiber-Connect Error)

The corresponding SNMP name for this condition is “fiberConnMismatch”.
Table 286: MEA-FC (Standing Condition)

Severity
PTP MJ The far-end port 1 Carefully trace the fiber to the far-
information does end port and determine to which
not match the port the fiber is connected.
provisioned Review the intended fiber
connections within connection provisioning plan and
the system’s adjust the fiber connections at
database, indicating either or both ends so that they
a possible fiber conform to the plan, or correct the
connection error. connection provisioning if it is
MEA-PHYS (Plug-Physical Mismatch)

“equipmentNotSupportedByPhysicalLayer”.
Table 287: MEA-PHYS (Standing Condition)

Severity Action
PL CR The physically inserted plug Review the provisioning

fails to meet one or more of attributes associated with
the provisioned physical layer the plug position and replace
properties (e.g. the plug the unacceptable plug with
cannot support the one of the required type.
provisioned signal rate or
reach, or is of the wrong
wavelength).1
1With respect to channel spacing, this condition is raised only if the channel spacing of
the inserted pluggable transceiver exceeds the respective module's provisioned channel
spacing. For example, Plug-Physical Mismatch is raised if a 100 GHz pluggable
transceiver is inserted into a channel module that requires 50 GHz channel spacing. This
condition is NOT raised if a 50 GHz or 100 GHz pluggable transceiver is inserted into a
channel module that requires 100 GHz channel spacing.
Standing Conditions
MEA-PROV (Provision Mismatch)

The corresponding SNMP name for this condition is “egptProvMismatch”.
Table 288: MEA-PROV (Standing Condition)

Severity
OM CR A provisioning error Note: The downstream modules

exists, which may connected to the facility may have
damage connected already suffered a power overload at
equipment. their optical receive ports, sufficient
An example is when to cause equipment damage. Verify
the number of that each of the affected modules is
channels within the still operating correctly once this
optical multiplex condition is resolved.
facility is within the 1 Review the provisioned inter-
allowed range for the module connections and ensure
supporting module, that the facility is connected to
but exceeds the the intended downstream
allowed limit for the modules. Correct any
configured provisioning errors.
downstream
modules. 2 Review the channels cross
connected within the facility and
correct the provisioning, so that
the number of channels are within
the system configuration limits
for the downstream modules.
MEA-RED (PSM Redundancy
Mismatch)
The corresponding SNMP name for this condition is “psmRedundancyMismatch”.
Table 289: MEA-RED (Standing Condition)

Severity
SHELF MJ The power units 1 Install power units to match

provisioned do not provisioning.
match redundancy 2 Change the shelf power unit
provisioning. redundancy provisioning to
match the installed
equipment.
Standing Conditions
MEA-SWREV (Software Mismatch)

The corresponding SNMP name for this condition is “meaSwRevision”.
Table 290: MEA-SWREV (Standing Condition)

Severity Action
MOD MJ1 The software revision of the Reload the software

backup (standby) controller generic, to get the backup
within the duplex protection module updated with the
group does not match that of desired generic.
the primary (active) controller.
MEPANR (MEP not Assigned)

The corresponding SNMP name for this condition is “mepNotPresentL2”.
Table 291: MEPANR (Standing Condition)

Severity
ELAN, NR The facility has An appropriate MEP instance must be

ELINE been configured associated with a flow configured as a
as a member of a member within a protection group if full
flow based functionality of the protection group is to
protection group, be realized. Provision the appropriate
but the MEP instance associated with the facility
associated MEP to ensure full support of all protection
has not yet been switching trigger conditions.
provisioned.
Standing Conditions
MEPVIDANR (VLAN ID Differ

MEP/Flow)
The corresponding SNMP name for this condition is “priVidNotEqualExtVidL2”.
Table 292: MEPVIDANR (Standing Condition)

Severity
DOWN- NR The Primary VLAN Review the Primary VLAN ID

MEP ID defined for the MEP value assigned to the MEP and
does not match the compare it to the SVID value of
SVID value assigned to the facility with which the MEP is
the flow with which the associated. Correct whichever
MEP has been VLAN ID value is in error.
associated.
Standing Conditions
MIDFLT (Midstage Fault)

The corresponding SNMP name for this condition is “midstageFault”.
Table 293: MIDFLT (Standing Condition)

Severity
OM CR The EDFA module 1 Verify that both the reporting facility and the associated
supporting the facility mid-stage facility are provisioned correctly.
has detected a failure 2 Verify that the optical fiber connected to the second
of the optical path stage input port is the correct cable, that it is firmly
between the output of connected to the input port and that the connector is not
the first stage and the physically impaired by obstructions, dirt or component
input to the second damage. Clean the connector or replace the cable, plug
stage. or module, as appropriate, depending upon the cause
3 Verify that the optical fiber connected to the first stage
output port is the correct cable, that it is firmly
connected to the output port and that the connector is
not physically impaired by obstructions, dirt or
component damage. Clean the connector or replace the
cable, plug or module, as appropriate, depending upon
the cause determined from the physical examination.
4 Verify that all remaining connections along the optical
pathway between the first stage output and second
stage input are firmly connected, that the connectors are
component damage. Clean the connector or replace the
cable or module, as appropriate, depending upon the
cause determined from the physical examination.
5 Verify that a signal is present at the input to the second
stage and that the signal is between the minimum and
maximum specified operating power levels. If the signal
meets the required specifications proceed to the next
step below, otherwise locate the source of the signal
problem within the mid-stage optical path and repair the
problem.
Standing Conditions
MODEMSYNC (Loss of Modem Sync)

The corresponding SNMP name for this condition is “lossOfModemSync”.
Table 294: MODEMSYNC (Standing Condition)

Severity
CH CR The incoming 1 Verify that the port is provisioned

signal is incorrect to match the transmitted signal.
or is severely 2 Verify that the received optical
degraded. signal meets specifications.
3 Clean the fiber connections.
4 Replace the module or plug.
MODFCN (Connection-Modify)
The corresponding SNMP name for this condition is “midstageFault”.
Table 295: MODFCN (Standing Condition)

Severity Action
WDM CR Signalling is underway to This condition is informative

Tunnel, modify the properties of an and no corrective action is
Ethernet established end-to-end needed.
Tunnel, tunnel.
OTN
Tunnel
Standing Conditions
MSIM-OPU (OPU-Multiplex Mismatch)

“multiplexStructureIdentifierMismatchOPU”.
Table 296: MSIM-OPU (Standing Condition)

Severity
CH CR The values in the multiplex 1 Verify that the (network side) facility
structure identifier fields within and its associated client facilities are
the OPU overhead (OPU2 provisioned correctly and are of the
Payload Structure Identifier intended type.
bytes 2 through 5) differs from 2 Verify that the facility is provisioned on
the expected values. the correct module type, and that there
The most likely causes of this are no equipment conditions active on
condition are: that module.
• Provisioning of different 3 Verify that the far-end facilities - both
unit types at each end of network and the associated client(s) -
the path. are provisioned correctly and are
• Mis-connection of the supported by the same module type as
signal between the far and the near-end facility.
near-end OPU termination 4 Verify that the incoming cable is the
points. correct cable and that the transmit and
• A failure of the far-end or receive ports are connected to their
near-end equipment. proper respective portions of the cable
• Interconnection to a far- (i.e. that the fibers are not swapped
end device which maps between transmit and receive).
the multiplexed 5 Proceeding to successive segments
ODU1/ODU2 signals upstream of the node reporting the
within the OPU2/OPU3 failure, verify that the signal is correctly
into tributaries in an order routed and that the fibers are correctly
other than tributary 1 into connected to the intended signal
position 1, tributary 2 into source.
position 2 and so on. 6 Replace the plug supporting the far-end
facility.
7 Replace the module supporting the far-
end facility.
8 Replace the plug supporting the near-
end facility.
near-end facility.
Standing Conditions
NORP (Partner-No Response)

The corresponding SNMP name for this condition is “backupNotResponding”.
Table 297: NORP (Standing Condition)

Severity
MOD MJ1 The backup 1 Verify that the provisioning and

(standby) controller equipping of both members of the
in a duplex duplex protection group is correct,
protected pair is and that the backup module is not
not responding to reporting a failure. Correct any
inter-module provisioning or equipping errors, and
communications. resolve any failure conditions
reported with respect to the backup
module.
2 Remove the inactive, standby
module. If this condition clears, and
is replaced by an indication that the
standby unit was removed, reseat
the standby module. If the original
condition recurs, replace the
standby module.
3 If the condition does not clear,
replace the shelf containing the
network controller modules.
Standing Conditions
NTPNSYNC (NTP-No Synchronization)

The corresponding SNMP name for this condition is “ntpNotInSync”.
Table 298: NTPNSYNC (Standing Condition)

Severity Cause
COM NA No NTP 1 If the system is intended to operate

(Network without synchronization of its time of day
Time clock to a remote NTP server, disable
Protocol) the synchronization of the NEs time of
servers are day clock to remote NTP servers.
reachable. 2 Verify that at least one remote NTP
server is enabled for use as a time
reference (i.e. is In-Service). Enable all
remote NTP servers which are
configured but erroneously disabled,
and/or provision and enable any missing
remote NTP servers.
3 Verify that the IP address provisioned for
each In-Service remote NTP server is
correct, and correct any erroneous
values.
4 Verify that at least one of the remote
NTP servers configured for use is alive
and able to serve requests. If a server is
temporarily unavailable due to outage or
administrative actions, correct the NTP
server issues, restart the server, and
then verify that this condition clears.
5 Verify that the network elements’ data
communications network provisioning
values are all correct and that they allow
communication to the NTP server
address (i.e. verify the systems IP
address and mask values and those of all
ports configured as part of the Data
Communication Network). Correct any
network configuration errors which may
exist.
Standing Conditions
OCI-ODU (ODU-Open Connection)

The corresponding SNMP name for this condition is “openConnectionIndicationOdu”.
Table 299: OCI-ODU (Standing Condition)

Severity Corrective
Action
CH NA The facility has received a signal Trace the path of

containing the open connection the signal
indication code in the ODU overhead, backwards
indicating that a cross-connection is through the
missing upstream. This is usually network and verify
caused by a failure to provision the client that all facilities
side facility on an upstream transponder, along the path are
by disabling such a client side facility provisioned and
through provisioning actions, by failure to are in service.
provision a client side facility or by
deleting an associated mapping facility
such as a GFPF/GFPT instance on an
upstream muxponder or by disabling
such a facility through provisioning
actions.
Standing Conditions
OCI-TCMA (TCM_A-Open Connection)

“openConnectionIndicationOduTcmA”.
Table 300: OCI-TCMA (Standing Condition)

CH NR The facility has received a signal Trace the path of

indication code in the tandem backwards through
connection monitoring overhead for the the network and
TCMi layer assigned as instance “A”, verify that all
indicating that a cross-connection is facilities along the
missing at a point upstream after that at path are
which that tandem connection began. provisioned and in
This is usually caused by a failure to an in-service
provision the client side facility on an normal (“In
upstream transponder, by disabling such Service”) state.
a client side facility through provisioning
actions, by failure to provision a client
side facility or by deleting an associated
mapping facility such as a GFPF/GFPT
instance on an upstream muxponder or
by disabling such a facility through
provisioning actions.
Standing Conditions
OCI-TCMB (TCM_B-Open Connection)

“openConnectionIndicationOduTcmB”.
Table 301: OCI-TCMB (Standing Condition)

CH NR The facility has received a signal Trace the path of the

containing the open connection signal backwards
indication code in the tandem through the network
connection monitoring overhead for the and verify that all
TCMi layer assigned as instance “B”, facilities along the
indicating that a cross-connection is path are provisioned
missing at a point upstream after that and in an in-service
at which that tandem connection normal (“In Service”)
began. state.
This is usually caused by a failure to
provision the client side facility on an
upstream transponder, by disabling
such a client side facility through
provisioning actions, by failure to
actions.
Standing Conditions
OCI-TCMC (TCM_C-Open Connection)

“openConnectionIndicationOduTcmC”.
Table 302: OCI-TCMC (Standing Condition)

CH NR The facility has received a signal Trace the path of

indication code in the tandem backwards through
connection monitoring overhead for the the network and
TCMi layer assigned as instance “C”, verify that all
indicating that a cross-connection is facilities along the
missing at a point upstream after that path are provisioned
at which that tandem connection and in an in-service
began. normal (“In Service”)
This is usually caused by a failure to state.
provision the client side facility on an
upstream transponder, by disabling
such a client side facility through
provisioning actions, by failure to
actions.
Standing Conditions
ODU-TRIB-MSIM (ODU-MSI
Mismatch)
The corresponding SNMP name for this condition is “oduTribMsiMismatch”.
Table 303: ODU-TRIB-MSIM (Standing Condition)

Severity
VCH1 CR This standing 1 Review the tributary slot and

condition occurs in tributary port provisioning on the
10TCC-PCN- VCH1 against which the alarm
2G7US+10G modules was raised. Correct any
if the received tributary provisioning errors.
slot information at a 2 If the alarm persists, review the
particular tributary port tributary slot and tributary port
does not match the provisioning on the far-end
tributary slot VCH1 for the network port
information connected to this network port.
transmitted by the Correct any provisioning errors.
corresponding far-end
If the above steps did not rectify the
port.
This alarm is only problem, please contact your ADVA
visible if two modules Optical Networking Technical
run in a link and Services Representative for
communicate on the assistance.
data layer.
Standing Conditions
OOSAINS (Auto In Service)

This condition is mutually exclusive relative to the OOSDSBLD-OFF (OOS Disabled Tx
(Off)), OOSDSBLD-RCV (OOS Disabled Rx), OOSDSBLD (OOS Disabled) and OOSMT
(Maintenance) conditions.
The corresponding SNMP names for this condition can be “bridgeOosAins”,
“cfmOosAins”, “oosAins” or “oosAinsL2”.
Table 304: OOSAINS (Standing Condition)

Severity Action
MOD NA The equipment is out-of- This condition is informative

service with an auto in- and no corrective action is
service secondary needed.
state.1
CH The facility is out-of- This condition is informative

service with an auto in- and no corrective action is
DCN service secondary needed.
ETH state.2
DOWN-MEP
OM
SH
STS1,
STS3C,
STS24C,
STS48C
VC3
VC4,
VC4C8,
VC4C16
1While in this state, the reporting of any other conditions related to this equipment will
be suppressed. This state will not permit testing or override operations to be
performed on the equipment, nor will it will allow service affecting provisioning
changes to be made.
2While in this state, the reporting of any other condition related to the facility will be
suppressed. The valid signal timer may be active, and upon expiration the facility
will automatically transition to an in-service state.
Standing Conditions
OOSDSBLD (OOS Disabled)

This condition supersedes the OOSDSBLD-OFF (OOS Disabled Tx(Off)) and OOSDSBLD-RCV conditions and
is mutually exclusive relative to the OOSMT (Maintenance) and OCI-ODU (ODU-Open Connection) conditions.
The corresponding SNMP names for this condition can be “cfmOosDisabled”, “ntpSrvOosDsbld”, “oosDisabled”,
“oosDisabledL2” or “oosDisabledSpeq”.
Table 305: OOSDSBLD (Standing Condition)

Severity
MOD, NA The equipment is This state is typically used to ensure that the
SPEQ manually out-of-service equipment is prevented from becoming active during
with a disabled some form of service affecting maintenance
secondary state, forcing procedure, or that the equipment will not be
the equipment to inhibit automatically provisioned upon unit insertion, and is
performance of its thus informative and no corrective action is needed.
normal service.1
CH The facility is manually out-of-service with a disabled secondary state, forcing

the facility to inhibit performance of its normal service.2
DCN This condition is informative and no corrective action is needed.
ETH
DOWN-
MEP
NTPSRV
OM
SH
STS1,
STS3C,
STS24C,
STS48C
VC3
VC4,
VC4C8,
VC4C16
1While in this state, the reporting of any other conditions related to this equipment is suppressed. This state
prevents the equipment from performing its provisioned functions. It will not permit testing or override
operations to be performed on the equipment, although it will allow service affecting provisioning changes to
be made.
2While in this state, the reporting of any other condition related to the facility will be suppressed. This state
prevents the facility from performing its provisioned functions. It will not permit testing or override operations
to be performed on the facility, although it will allow service affecting provisioning changes to be made.
Standing Conditions
OOSDSBLD-LCK-ODU-RCV (OOS Disabled Rx

(LCK-ODU))
The OOSDSBLD-LCK-ODU-RCV standing condition is raised when the user disables the entity, prompting it to
send the LCK maintenance signal in the receive direction.
The corresponding SNMP name for this condition is “oosDisabledLckOduRx”.
Table 306: OOSDSBLD-LCK-ODU-RCV (Standing Condition)

CH NA A user has set the administrative state of the facility This condition is
VCH to out-of-service with a disabled secondary state, informative and
VCHn forcing the facility to inhibit its normal performance.1 requires no
To condition the line, an LCK maintenance signal is corrective action.
inserted in the receive direction.
OOSDSBLD-LCK-ODU-TRMT (OOS Disabled Tx

(LCK-ODU))
The OOSDSBLD-LCK-ODU-TRMT standing condition is raised when the user disables the entity, prompting it to
send the LCK maintenance signal in the transmit direction.
The corresponding SNMP name for this condition is “oosDisabledLckOduTrmt”.
Table 307: OOSDSBLD-LCK-ODU-TRMT (Standing Condition)

CH NA A user has set the administrative state of the This condition is

VCH facility to out-of-service with a disabled secondary informative and
VCHn state, forcing the facility to inhibit its normal requires no corrective
performance.2 action.
To condition the line, an LCK maintenance signal
is inserted in the transmit direction.
to be performed on the facility, although it will allow service-affecting provisioning changes to be made.
to be performed on the facility, although it will allow service affecting provisioning changes to be made.
Standing Conditions
OOSDSBLD-OFF (OOS Disabled Tx

(Off))
This condition is mutually exclusive relative to the OOSMT (Maintenance), OOSDSBLD
(OOS Disabled) and ODU-TRIB-MSIM (ODU-MSI Mismatch) conditions.
The corresponding SNMP name for this condition is “transmitterDisabledOff”.
Table 308: OOSDSBLD-OFF (Standing Condition)

Severity Corrective
Action
CH NA The facility is manually out-of-service This condition is

with a disabled secondary state affecting informative and no
ETH the transmit direction only, forcing the corrective action
facility to inhibit performance of its is needed.
normal service in the outbound
OM
direction.1
OOSDSBLD-RCV (OOS Disabled Rx)

This condition is mutually exclusive relative to the OOSMT (Maintenance), OOSDSBLD
(OOS Disabled) and ODU-TRIB-MSIM (ODU-MSI Mismatch) conditions.
The corresponding SNMP name for this condition is “receiverDisabled”.
Table 309: OOSDSBLD-RCV (Standing Condition)

Severity Corrective
Action
CH NA The facility is manually out-of-service with This condition is

a disabled secondary state affecting the informative and
ETH receive direction only, forcing the facility no corrective
to inhibit performance of its normal service action is needed.
in the receive direction.2
1While in this state, the reporting of any other condition related to the facility with the
exception of the OOSDSBLD-RCV (OOS Disabled Rx) condition will be
suppressed. This state prevents the facility from performing its provisioned functions
in the transmit direction only - it has no effect upon the receive direction. It will not
permit testing or override operations to be performed on the facility, although it will
allow service affecting provisioning changes to be made.
2While in this state, the reporting of any other condition related to the facility with the
exception of the OOSDSBLD-OFF (OOS Disabled Tx(Off)) condition will be
suppressed. This state prevents the facility from performing its provisioned functions
in the receive direction only - it has no effect upon the transmit direction. It will not
permit testing or override operations to be performed on the facility, although it will
allow service affecting provisioning changes to be made.
Standing Conditions
OOSMGT (Management)
This condition is mutually exclusive relative to the OCI-ODU (ODU-Open Connection)
condition. The corresponding SNMP names for this condition can be
“bridgeOosManagement”, “cfmOosManagement”, “oosManagement” or
“oosManagementL2”.
Table 310: OOSMGT (Standing Condition)

Severity Cause
MOD, SPEQ NA The equipment This state is typically used to allow

was manually provisioning changes to be made to
placed out-of- attributes which will affect the services
service by a provided by the equipment and is thus
user informative and no corrective action is
command.1 needed.
CH The facility This state is typically used to allow

was manually provisioning changes to be made to
DCN: placed out-of- attributes which will affect the services
ETH service by a provided by the facility and is thus
user informative and no corrective action is
DOWN- command.2 needed.
MEP
OM
SH
STS1,
STS3C,
STS24C,
STS48C
VC3
VC4,
VC4C8,
VC4C16
be suppressed. This state does not prevent the equipment from performing its
provisioned functions, but will not permit testing and override operations to be
performed on the equipment. It will allow service affecting provisioning changes to
be made.
suppressed. This state does not prevent the facility from performing its provisioned
functions, but it will not permit testing or override operations to be performed on the
facility, although it will allow service affecting provisioning changes to be made.
Standing Conditions
OOSMT (Maintenance)
This condition supersedes the OOSDSBLD-OFF (OOS Disabled Tx(Off)) condition and is
mutually exclusive relative to the OOSDSBLD (OOS Disabled) and ODU-TRIB-MSIM
(ODU-MSI Mismatch) conditions.
The corresponding SNMP names for this condition can be
“cfmOosMaintenance”, “oosMaintenance”, “oosMaintenanceL2” or
“oosMaintenanceSpeq”.
Table 311: OOSMT (Standing Condition)

Severity
MOD, NA The equipment was manually This state is typically used to allow testing or
SPEQ placed into a maintenance override operations to be performed on the
secondary state by a user equipment and is thus informative and no corrective
command.1 action is needed.
CH The facility was manually This state is typically used to allow testing or
placed into a maintenance override operations to be performed on the facility
DCN: secondary state by a user and is thus informative and no corrective action is
ETH command.2 needed.
DOWN-
MEP
OM
SH
STS1,
STS3C,
STS24C,
STS48C
VC3
VC4,
VC4C8,
VC4C16
be suppressed. This state does not prevent the equipment from performing its
provisioned functions, but will permit testing and override operations to be
performed on the equipment which may impact the traffic carried by that equipment.
It will allow service affecting provisioning changes to be made.
suppressed. This state does not prevent the facility from performing its provisioned
functions, but it will not permit testing or override operations to be performed on the
facility, although it will allow service affecting provisioning changes to be made.
Standing Conditions
OOSPPS (OOS State Transition)

The corresponding SNMP name for this condition is “oosPrePostSig”.
Table 312: OOSPPS (Standing Condition)

Severity Action
WDM NA The tunnel properties are This state is informative and

Tunnel, defined but setup of the no corrective action is
Ethernet tunnel has not yet needed.
Tunnel, occurred.1
OTN Tunnel
OOSPPS-DOWN (OOS Tear Down)

“oosPrePostSigInTearDownProcess”.
Table 313: OOSPPS-DOWN (Standing Condition)

Severity
WDM NA The connections This state is informative and no

Tunnel, supporting the tunnel are in corrective action is needed.
Ethernet the process of being torn
Tunnel, down (the service is being
OTN terminated).2
Tunnel
1While in this state, the tunnel has not been established and no corresponding end-
to-end traffic flows will be active. This state will allow service affecting provisioning
changes to be made.
2While in this state, a previously established tunnel is being torn down and
corresponding end-to-end traffic flows will be transitioning to an inactive state. This
state will allow service affecting provisioning changes to be made.
Standing Conditions
OOSPPS-ESTFLT (OOS Setup Fail)

The corresponding SNMP name for this condition is “oosPrePostSigEstablishFailed”.
Table 314: OOSPPS-ESTFLT (Standing Condition)

Severity Cause
WDM NA The Beginning at the local node and following the

Tunnel, previously route over which the tunnel has been
Ethernet established established, review the status of the
Tunnel, tunnel is no connection entity associated with this tunnel
OTN longer in at each node to determine the supporting
Tunnel service due to equipment, facility and related entities on
a failure.1 that node which support the connection.
Review the status of each element and take
the appropriate corrective action based upon
the conditions reported by any of these
elements which are reporting failures.
OOSPPS-UP (OOS Setup In Process)

The corresponding SNMP name for this condition is “oosPrePostSigInSetUpProcess”.
Table 315: OOSPPS-UP (Standing Condition)

Severity
WDM NA The tunnel properties This state is informative and no

Tunnel are defined and setup corrective action is needed.
Ethernet of the tunnel is in
Tunnel, progress but not yet
OTN completed.2
Tunnel
1While in this state, the tunnel has been established and corresponding end-to-end
traffic flows will be active, although the service may be impacted due to the failure of
an element along the established route. This state will allow service affecting
provisioning changes to be made.
2While in this state, the tunnel has not been established and no corresponding end-
to-end traffic flows will be active. This state will allow service affecting provisioning
changes to be made.
Standing Conditions
OPM-ANR (OPM-Abnormal)
The corresponding SNMP name for this condition is “opmAbnormalCondition”.
Table 316: OPM-ANR (Standing Condition)

Severity Cause
CH NR The optical 1 Verify that the incoming cable is the

signal power correct cable and that the transmit and
has dropped to receive ports are connected to their
a level which proper respective portions of the cable
is low enough (i.e. that the fibers are not swapped
to be between transmit and receive).
considered 2 Verify that the incoming optical fiber is
degraded. firmly connected to the receive port
associated with the facility and that the
examination.
the problem.
the facility.
Standing Conditions
OPM-FLT (OPM-Fail)
The corresponding SNMP name for this condition is “faultOnOpm”.
Table 317: OPM-FLT (Standing Condition)

Severity Cause
OM MJ A failure of the 1 Verify that all cable connections on the

optical power supporting module are correct and that
monitoring the transmit and receive ports are
function of the connected to their proper respective
reporting facility portions of the cable (i.e. that the fibers
has been are not swapped between transmit and
detected. receive).
2 Verify that the optical output power
level of the reporting facility is within
specified limits, based upon the
number of active channels within the
optical multiplex facility. If not, inspect
the outgoing fiber connector and either
clean it or replace any damaged
components, as needed.
3 Verify that the sources for all received
signals cross-connected to form the
outgoing signal for the optical multiplex
facility are operating normally and are
within their relevant optical signal
specifications. If the signal meets the
required specifications proceed to the
next step below, otherwise locate the
source of the signal problem upstream
4 Verify that the incoming fibers for all
received signals cross-connected to
form the outgoing signal for the optical
multiplex facility are correct and that
each connector is firmly attached.
Inspect the connectors and fiber ends
for dirt, damage or any optical signal
path impairments and correct them as
needed.
optical multiplex facility.
Standing Conditions
OPT-FAULT (Optical Power Tx Fault)

The OPT-FAULT standing condition occurs when there is no channel output power, even
though the input power for the channel is above the LOS threshold and the channel
attenuation is set to a valid value.
The corresponding SNMP name for this condition is “outputPowerFault”.
Table 318: OPT-FAULT (Standing Condition)

Severity Action
OM CR The cross-connected channel 1 Verify that the

is below the minimum output supporting module is
power level even though the operating normally (e.g.
corresponding input signal is that it is not undergoing
within the operating range. an initialization or power
This may indicate a failure of equalization process).
the cross-connection device 2 Replace the module
within the supporting module. supporting the optical
multiplex facility.
Standing Conditions
OPT-SF (OPT Signal Fail)

The corresponding SNMP name for this condition is “optSignalFailure”.
Table 319: OPT-SF (Standing Condition)

Severity
CH CR The transmitted 1 Verify that the failed channel has a

optical signal has valid, active cross-connection
failed. provisioned. If the cross connection
has been removed of disabled,
correct the provisioned state of the
cross connection.
2 Verify that the cable associated with
the incoming signal which is cross-
connected to the reporting facility is
the correct cable and that the transmit
and receive ports are connected to
receive).
3 Verify that the incoming signals
optical fiber is firmly connected to the
receive port associated with the
facility and that the connector is not
physically impaired by obstructions,
the problem.
Standing Conditions
OPTCTRL-FHT (Optical Control-Fail

High)
The corresponding SNMP name for this condition is “thresOptPowerCtrlFailureHigh”.
Table 320: OPTCTRL-FHT (Standing Condition)

Severity Cause
CH MJ The optical This condition is caused by the received

power on the signal optical power level exceeding that
output port of which the attenuator is able to adjust to the
the attenuator desired level. The following steps may be
module has used to determine the appropriate
exceeded the corrective action:
maximum 1 Verify that the incoming cable is the
allowable level. correct cable and that the receive port
is properly connected to the intended
source.
2 Verify that the attenuator provisioning
settings are correct and adjust them as
necessary.
3 Examine the settings of the equipment
which is the source of the optical
signal received by the attenuator and if
it is possible to adjust the output power
level, decrease it to a level which is
within the optical specifications of the
attenuator receive port.
4 Add a fixed optical attenuator between
the source and the receive port to bring
the input signal within specified limits.
Standing Conditions
OPTCTRL-FLT (Optical Control-Fail

Low)
The corresponding SNMP name for this condition is “thresOptPowerCtrlFailureLow”.
Table 321: OPTCTRL-FLT (Standing Condition)

Severity Cause
CH MJ The optical This condition is caused by the received

power on the signal optical power level being below that
output port of which the attenuator is able to adjust to the
the attenuator desired level. The following steps may be
module has used to determine the appropriate corrective
fallen below action:
the minimum 1 Verify that the incoming cable is the
allowable correct cable and that the receive port is
level. properly connected to the intended
source.
2 Verify that the attenuator provisioning
settings are correct and adjust them as
necessary.
3 Verify that the incoming cable (electrical
or optical) is firmly connected to the
receive port associated with the facility
and that the connector is not physically
component damage. Clean the connector
or replace the cable, plug or module, as
examination.
4 Examine the settings of the equipment
which is the source of the optical signal
received by the attenuator and if it is
possible to adjust the output power level,
increase it to a level which is within the
optical specifications of the attenuator
receive port.
5 Verify that there are no fixed attenuators
in-line between the source and the
receive port.
6 Replace the optical cable connecting the
source to the receive port.
the source facility.
8 Replace the attenuator module.
Standing Conditions
OPTLMT (Optical Power Tx Limit)

The corresponding SNMP name for this condition is “txPowerLimited”.
Table 322: OPTLMT (Standing Condition)

Severity
OM MN The optical power on 1 Review the configuration of the

the final output port incoming and outgoing network
of the amplifier OM facilities and adjust
module has reached provisioned gain levels as needed
the maximum level to conform to the levels
prior to the amplifier determined from the optical
attaining the networks’ engineering.
provisioned amount 2 Verify that the mid-stage
of gain. attenuation and any dispersion
compensation elements used in
the mid-stage of the amplifier
conform to those determined by
the optical networks’ engineering
and adjust the elements as
needed so that they conform to
the expected values.
OSC-FIBER (OSC Fiber Entry Missing)

The corresponding SNMP name for this condition is “oscFiberMissingSpeq”.
Table 323: OSC-FIBER (Standing Condition)

Severity Action
SPEQ MJ The physical termination point Review the configuration of

connections between the OSC the fiber interconnection
module and the port which table and provision the
couples it to the optical line missing entry.
with which the entity is
associated is not provisioned in
the fiber interconnection
mapping table.
Standing Conditions
OSCOPTCTRL-FHT (OSC Control Fail

High)
The corresponding SNMP name for this condition is “oscOpticalPowerControlFailHigh”.
Table 324: OSCOPTCTRL-FHT (Standing Condition)

Severity Cause
OM MJ Attempts to 1 Verify that the incoming fiber carrying

control the OSC the optical supervisory channel
optical input signal from the associated module is
power correctly connected (i.e. that the
associated with connection is to the desired OSC
the optical signal source, rather than another
multiplex facility port). Correct any cabling errors.
have failed to 2 Verify that the OSC source module is
reduce the power correctly configured and if it employs
level to an a pluggable optical module, that the
acceptable level. correct type of pluggable module is
installed and operating normally.
3 Measure the optical power of the
OSC signal source at the input to the
module supporting the facility which
reports this condition. If the optical
power is outside the specified
operating range, either replace the
faulty source or add external optical
attenuation in-line to reduce the
power into the OSC signal port so
that it is within acceptable limits.
Standing Conditions
OSCOPTCTRL-FLT (OSC Control Fail

Low)
The corresponding SNMP name for this condition is “oscOpticalPowerControlFailHigh”.
Table 325: OSCOPTCTRL-FLT (Standing Condition)

Severity
OM MJ Attempts to control 1 Verify that the incoming fiber

the OSC optical carrying the optical supervisory
input power channel signal from the associated
associated with the module is correctly connected (i.e.
optical multiplex that the connection is to the
facility have failed desired OSC signal source, rather
to reduce the than another port). Correct any
attenuation to a cabling errors.
level where the 2 Verify that the OSC source module
power level can is correctly configured and if it
reach the employs a pluggable optical
acceptable module, that the correct type of
minimum level. pluggable module is installed and
operating normally.
3 Measure the optical power of the
OSC signal source at the input to
the module supporting the facility
which reports this condition. If the
optical power is outside the
specified operating range, either
replace the faulty source or optical
cable so that the power measured
at the OSC signal input port is
within acceptable limits.
OTDR (OTDR-In Operation)

The corresponding SNMP name for this condition is “oTDRMeasuringinProgress”.
Table 326: OTDR (Standing Condition)

RSM-OLM NA A user has triggered the OTDR This condition is

operation request. This condition informative and
clears when the OTDR operation requires no corrective
time expires. The OTDR may be action.
operated for 5, 20, 40, or 60
minutes.
Standing Conditions
PAUSE-CRYPW (Crypto User Locked

Out)
The corresponding SNMP name for this condition is “encryptionModuleCryPasswdError”.
Table 327: PAUSE-CRYPW (Standing Condition)

Severity Cause
MOD MN 3 successive This condition clears automatically after

unsuccessful ten minutes.
attempts were While this condition is informative, it may
made to indicate an attempt to breach the security
authenticate to of the cryptographic module by gaining
the equipment as access to the privileged user role.
the If the condition resulted from actions
Cryptographic which pose no threat of a security breach,
Officer role. you may disregard this condition.
Otherwise, determine the source of the
breach attempt.
PEER-AID1-RMVD (Partner 1
Deleted)
The corresponding SNMP name for this condition is “partner1Deleted”.
Table 328: PEER-AID1-RMVD (Standing Condition)

Severity Cause
MOD MN The Protection 1 Ensure that the OPPM is properly

Partner 1 provisioned with the correct Protection
previously Partner 1.
assigned to this 2 Ensure that the channel module
module has associated with Protection Partner 1 is
been deleted installed and properly provisioned.
from the NE.
3 If the Protection Partner 1 was deleted
accidentally, re-provision it. Otherwise
set the Protection Partner 1 on the
OPPM to None.
Standing Conditions
Deleted)

Severity Cause

from the NE.
OPPM to None.
Deleted)

Severity Cause

from the NE.
OPPM to None.
Standing Conditions
Deleted)

Severity Cause

from the NE.
OPPM to None.
Standing Conditions
PEER-LINK (Link Fail to Partner)

The corresponding SNMP name for this condition is “peerLink”.
Table 332: PEER-LINK (Standing Condition)

Severity
CH MJ The communication 1 Verify that the provisioned settings of both facilities within
path between the the protection group in which the reporting facility is a
transponder/ member are correct.
muxponder module 2 Verify that the protection group is provisioned correctly.
(s) supporting the
facility’s card 3 Verify that both of the modules supporting the facilities
protection group within the protection group are provisioned correctly, have
has failed. no active conditions, and are in-service normal (“In
Service”).
4 Verify that the shelf controller modules and inter-shelf
communications links between the shelves in which the
modules supporting the facilities reside are provisioned
correctly, have no active conditions, and are in-service
normal (“In Service”).
DCN The PPPIP facility 1 Verify that the configuration settings of the PPPIP facility
has detected a are correct.
failure of the 2 Verify that the PPPIP facility is cross-connected to the
communications appropriate data transmission facility.
link with its peer
3 Verify that the data transmission facility to which the
PPPIP facility at
PPPIP facility is connected is configured correctly, that
the far-end of the
there are no active conditions on that facility, and that this
communications
facility is in-service normal (“In Service”).
link.
4 Verify that each successive node in the link up to and
including the far-end PPPIP facility termination point is
correctly configured, operating without active conditions
which may impact the link, and that the facilities are all in-
service normal (“In Service”).
Standing Conditions
Table 332: PEER-LINK (Standing Condition)

Severity
OM MJ The communication 1 Verify that the provisioned settings of both facilities within
path between the the protection group in which the reporting facility is a
VSM module and member are correct.
the 2OSCM module 2 Verify that the VSM module is provisioned correctly,
supporting the operating without any active conditions and is in-service
protection protocol normal (“In Service”).
exchange used to
3 Verify that the 2OSCM module provisioned as providing
co-ordinate
the communications channel to support the protection
switching activities
switching protocol for the affected protection group
has failed.
(identified by the Partner attribute of the group) is
provisioned correctly, has no active conditions, and is in-
4 Verify that all required DCN:E100FX and DCN:E10-
100TX facilities on the 2OSCM module are provisioned
correctly, have no active conditions, and are in-service
5 Verify that each successive node in the communications
link up to and including the peer VSM module on at least
one of the 2 communications paths linking the VSM
modules is correctly provisioned, has no active conditions
and that the relevant facility and equipment entities are in-
Standing Conditions
PEER-LINK1 (Link Fail to Partner 1)

The corresponding SNMP name for this condition is “linkFailToPartner1”.
Table 333: PEER-LINK1 (Standing Condition)

Severity
MOD MN Loss of 1 Ensure that the OPPM is properly

communication provisioned with the correct
with the Protection Partner 1.
provisioned 2 Ensure that the channel module
Protection associated with Protection Partner 1
Partner 1. is installed and properly provisioned.
3 Verify that the Protection Partner 1 is
properly provisioned. If the Protection
Partner 1 was deleted (this is
indicated by the PEER-AID1-RMVD
(Partner 1 Deleted) alarm), re-
provision it or set the Protection
Partner 1 on the OPPM to None.
issues.


Severity

issues.
Standing Conditions


Severity

issues.


Severity

issues.
Standing Conditions
PILOT-HIGH (Pilot Signal High)

The corresponding SNMP name for this condition is “pilotReceiveLevelHigh”.
Table 337: PILOT-HIGH (Standing Condition)

Severity
OM MN The optical power level of the 1 Verify that the correct fiber is coupled to
counter-propagating OSC or the network side output port of the
Raman pump signal used to amplifier module, and correct any cabling
detect fiber continuity is issues if they exist. If Raman
above the maximum amplification is being used, ensure that
allowable level. the network output port is connected to
The most likely causes of the appropriate Raman amplifier module
this condition are: upgrade input port.
• Mis-connection of the 2 At the far-end of the span connected to
OSC or Raman pump the network output port, verify that the far-
module to the OM end amplifier module is operating
facilities supporting normally, that the far-end amplifier client
equipment, or the use of input port is properly connected and that
a Raman pump on a the connected OSC or Raman pump
span which is too short module is operating normally. Correct any
for Raman pumping. equipment provisioning or equipping
• Mis-connection of the issues, replace any failed equipment
signal between the far and/or correct any cabling issues which
and near-end span exist.
termination points. 3 Verify that the counter-propagating OSC
• A failure of the far-end or or Raman pump optical signal arriving at
near-end equipment. the network output port complies with the
specified power level range for the
module. If the signal is outside the
specified range, this indicates that the
span is shorter than the minimum
allowable length or that the far-end module
output power exceeds the allowable
limits. Address the span length and/or far-
end optical signal source issue(s) as
needed.
4 Replace the near-end amplifier module.
Standing Conditions
PILOT-LOS (Pilot Signal Loss)

The corresponding SNMP name for this condition is “lossOfPilotSignal”.
Table 338: PILOT-LOS (Standing Condition)

Severity
OM MN The optical power level of 1 Verify that the OSC or Raman pump module at the
the counter-propagating far-end of the span is correctly connected and
OSC or Raman pump operating normally. Correct any cabling issues
signal used to detect fiber and/or replace any failed module.
continuity has fallen below 2 Verify that the correct fiber is coupled to the network
the minimum detectable side output port of the amplifier module, and correct
level. any cabling issues if they exist.
The most likely causes of
this condition are: 3 If the network output port transmission span
employs Raman pumping, verify that the Raman
• Disconnection of the amplifier module at the far-end of the span is
far-end OSC or correctly cabled, configured and operating normally.
Raman pump signal Correct any cabling or configuration issues or
source. replace the module if it is failed.
• Mis-connection of the 4 If Raman pumping is not used, verify that the far-end
signal between the far amplifier supervisory channel input port is properly
and near-end span connected to the output of an OSC module, and that
termination points. the OSC module is operating normally. Correct any
• A failure of the far-end equipment provisioning or equipping issues, replace
or near-end any failed equipment and/or correct any cabling
equipment. issues which exist.
5 Verify that the counter-propagating OSC or Raman
pump optical signal arriving at the network output
port complies with the specified power level range
for the module. If the signal is outside the specified
range, this indicates a problem in the transmission
space or that the span exceeds the maximum
allowable length. Address the span loss or length
issue as needed.
6 Replace the near-end amplifier module.
Standing Conditions
PLM-GFP (GFP-Payload Mismatch)

The corresponding SNMP name for this condition is “payloadMismatchGfp”.
Table 339: PLM-GFP (Standing Condition)

Severity
CH CR The value identifying 1 Verify that the GFP facility and

the payload type its associated client facilities
carried within the GFP are provisioned correctly and
frame differs from the are of the intended type.
expected value. 2 Verify that the far-end facilities -
The most likely causes both GFP and the associated
of this condition are: client(s) - are provisioned
• Inconsistent correctly and are supported by
provisioning of the the same module type as the
mapping type at near-end facility.
the near and far- 3 Verify that the incoming cable is
end GFP the correct cable and that the
termination points. transmit and receive ports are
• Inconsistent client connected to their proper
signal types respective portions of the cable
provisioned at the (i.e. that the fibers are not
near and far-end swapped between transmit and
GFP termination receive).
points. 4 Proceeding to successive
• Mis-connection of segments upstream of the node
the signal between reporting the failure, verify that
the far and near- the signal is correctly routed and
end GFP that the fibers are correctly
termination points. connected to the intended signal
• A failure of the far- source.
end or near-end 5 Replace the module supporting
equipment. the near-end facility.
the far-end facility.
Standing Conditions
PLM-LP (Path LO-Payload Mismatch)

The corresponding SNMP name for this condition is “payloadMismatchLowerOrderPath”.
Table 340: PLM-LP (Standing Condition)

Severity Action
VC3 CR The received path signal carries Verify that the

an incompatible code (but not the provisioning of the path
unequipped code) in the signal and its associated client
label byte. signal type at the near
This typically means that the far- and far-end match.
end path termination point has
been assigned to carry a payload
which is of a different type than
that provisioned at the facility
reporting the condition.
Standing Conditions
PLM-OPU (OPU-Payload Mismatch)

The corresponding SNMP name for this condition is “payloadMismatchOPU”.
Table 341: PLM-OPU (Standing Condition)

Severity
CH CR The payload type of 1 Verify that the (network side)

the received signal facility and its associated client
differs from the facilities are provisioned
expected value. correctly and are of the intended
The most likely type.
causes of this 2 Verify that the facility is
condition are: provisioned on the correct
Inconsistent client
module type, and that there are
signal types
no equipment conditions active
provisioned at the
on that module.
near and far-end OPU
termination points. 3 Verify that the far-end facilities -
Provisioning of both network and the associated
different unit types at client(s) - are provisioned
each end of the path correctly and are supported by
(e.g. a 4TCC10G-x the same module type as the
type unit at one end near-end facility.
and a WCC10G-x unit 4 Verify that the incoming cable is
at the other). the correct cable and that the
Mis-connection of the transmit and receive ports are
signal between the far connected to their proper
and near-end OPU respective portions of the cable
termination points. (i.e. that the fibers are not
A failure of the far-end swapped between transmit and
or near-end receive).
equipment.
5 Proceeding to successive
segments upstream of the node
reporting the failure, verify that
the signal is correctly routed and
that the fibers are correctly
connected to the intended signal
source.
6 Replace the plug supporting the
far-end facility.
the far-end facility.
8 Replace the plug supporting the
near-end facility.
the near-end facility.
Standing Conditions
PLM-P (Path-Payload Mismatch)

The corresponding SNMP name for this condition is “payloadMismatchHigherOrderPath”.
Table 342: PLM-P (Standing Condition)

Severity Action
STS1, CR The received path signal carries an Verify that the

STS3C, incompatible code (but not the un- provisioning of the path
STS24C, equipped code) in the signal label and its associated
STS48C byte. client signal type at the
This typically means that the far- near and far-end match.
end path termination point has
VC4, been assigned to carry a payload
VC4C8, which is of a different type than
VC4C16 that provisioned at the facility
PLM-VF (Payload Mismatch)

The corresponding SNMP name for this condition is “payloadMismatch”.
Table 343: PLM-VF (Standing Condition)

CH CR The received signal for the virtual Verify that the

facility is not of the same type. provisioning of the
This typically means that the far-end virtual facility and its
virtual facility instance carries a associated client
payload which is of a different type signal type at the near
than that provisioned at the facility and far-end match.
Standing Conditions
PPLM (Prov. Payload Mismatch)

The corresponding SNMP name for this condition is “provPayloadMismatch”.
Table 344: PPLM (Standing Condition)

CH CR The received signal for the facility Verify that the

is not the same type as that provisioning of the
provisioned. facility and its
This typically means that the far- associated client signal
end facility instance carries a type at the near-end
payload that is of a different type and far-end match.
than that provisioned at the facility
Standing Conditions
PRBS-LSS (PRBS-Loss of Sync)

The corresponding SNMP name for this condition is “prbsLossOfSeqSynch”.
Table 345: PRBS-LSS (Standing Condition)

Severity
CH NA The received signal 1 Verify that the receiving facility is

is expected to correctly set to operate in the
contain a PRBS PRBS reception test mode. If the
test sequence but facility should not be operating in
the receiver is this mode, release the PRBS
unable to receive test control and restore the
synchronize to the facility to normal service.
expected pattern, 2 Verify that the far-end facility is set
or if the bit-error to operate in PRBS test signal
ratio of the received insertion mode. If the facility is not
signal exceeds 0.2 operating in that mode, place it into
during an this mode.
integration period of
3 Examine the Performance
1 second.
Monitoring counters for the current
interval and determine whether the
bit-error rate on the received signal
is excessive relative to the
expected performance of the
engineered path. If it is excessive,
it indicates a signal quality
degradation along the path.
Proceeding upstream along the
path, verify the optical power levels
of the signal are within the
path, and correct any elements
which are outside their engineering
specifications. This may involve
performing span equalization
adjustments or optical power
setting adjustments at various
control points along the path.
appropriate, supporting the facility.
appropriate, supporting the far-end
of the facility.
Standing Conditions
PRBS-RCV (PRBS-Rx Active)

The corresponding SNMP name for this condition is “prbsRcvActivated”.
Table 346: PRBS-RCV (Standing Condition)

Severity Action
CH NA The facility is set to operate in a This condition is

mode where the received signal is informative and no
expected to contain a PRBS test corrective action is
signal, which will be analyzed to needed.
produce test results.
PRBS-TRMT (PRBS-Tx Active)

The corresponding SNMP name for this condition is “prbsTrmtActivated”.
Table 347: PRBS-TRMT (Standing Condition)

CH NA The facility is set to operate in a This condition is

mode where the outgoing signal informative and no
payload is replaced by a PRBS test corrective action is
signal, which will be analyzed at the needed.
far-end receiver in order to produce
test results.
PROTNA (Partner-Not Available)

The corresponding SNMP name for this condition is “protectionNotAvailable”.
Table 348: PROTNA (Standing Condition)

Severity
MOD MN One of the modules in This condition is informative and

a duplex protection no corrective action is needed.
group was removed or Corrective action will be taken in
has failed, so no response to the conditions
equipment reported for the failed or removed
redundancy exists. module.
Standing Conditions
PSUFLT (PSU-Fail (Severe))

The corresponding SNMP name for this condition is “powerSupplyUnitFailure”.
Table 349: PSUFLT (Standing Condition)

Severity Corrective
Action
MOD MN The power supply module has failed Replace the

and is unable to reliably perform its module.
intended functions.1
PWR-BLK-FLT (Power Block Fault)

The corresponding SNMP name for this condition is “disabledChannelPowerTooHigh”.
Table 350: PWR-BLK-FLT (Standing Condition)

Severity Cause
CH MJ The optical 1 Verify that the facility is correctly

power output cross-connected to the intended
level of the signal incoming signal.
is greater than 2 Verify that the cable supporting the
the allowed incoming signal which is cross-
maximum value connected to the facility is the correct
(-25 dBm) when cable.
the optical signal
3 Verify that the incoming signal
pathway is
supposed to be
specifications (e.g. maximum power
blocked.
facility.
1Note that this condition is only able to be reported if a secondary power supply unit
is also equipped, provisioned, and operating correctly in the shelf in which the
failed unit resides.
Standing Conditions
PWRCONS-EQUD (PSU Limit-

Equipped)
The power supply capability of a single PSU can be exceeded by some combinations of
modules in a shelf. If two PSUs are installed, these module combinations can be
supported due to load sharing. However, if one of the PSUs fails, the remaining PSU
would be unable to supply sufficient power for the modules in the shelf.
“maxPowerConsEquipModulesToHigh”.
Alarms that indicate the status of the power supply itself, such as
Severe PSU Failure, do not have any influence on this condition.
Note
Table 351: PWRCONS-EQUD (Standing Condition)

Severity
SHELF MJ The total power 1 Ensure that all power supply modules are correctly
requirements of the provisioned and that the units are properly equipped
modules equipped with operational modules.
within a shelf 2 Review the equipped modules in the shelf (other than
exceed the the power supply modules) and remove any that are
capabilities of the not required.
equipped power
3 Review the provisioned modules in the shelf (other
supply modules
than the power supply modules) and correct any
within that shelf.
provisioning errors.
4 If the number of power supply modules equipped in the
shelf is less than the maximum allowed, install and
provision additional module(s).
5 If higher power output variants of the power supply
modules used are available, re-provision the power
supply modules and use the higher output variants.
6 If the preceding steps do not resolve the condition, the
shelf configuration does not conform to the product's
engineering guidelines and one or more equipped
modules must be removed and de-provisioned to bring
the configuration into conformance.
Standing Conditions
PWRCONS-PROV (PSU Limit-

Provisioned)
The power supply capability of a single PSU can be exceeded by some combinations of
modules in a shelf. If two PSUs are installed, these module combinations can be
supported due to load sharing. However, if one of the PSUs fails, the remaining PSU
would be unable to supply sufficient power for the modules in the shelf.
“maxPowerConsProvModulesToHigh”.
Alarms that indicate the status of the power supply itself, such as
Severe PSU Failure, do not have any influence on this condition.
Note
Table 352: PWRCONS-PROV (Standing Condition)

Severity
SHELF MN The total power 1 Ensure that all power supply modules are correctly
requirements of provisioned and that the units are properly equipped with
the modules operational modules.
provisioned or 2 Review the provisioned modules in the shelf (other than
equipped within a the power supply modules) and delete the provisioning
shelf exceed the information for any which are not needed.
capabilities of the
3 Correct any provisioning errors.
equipped power
supply modules 4 Review the equipped modules in the shelf (other than
within that shelf. the power supply modules) and remove any that are not
required.
5 If the number of power supply modules equipped in the
shelf is less than the maximum allowed, install and
provision additional module(s).
6 If higher power output variants of the power supply
modules used are available, re-provision the power
supply modules and use the higher output variants.
7 If the preceding steps do not resolve the condition, the
shelf configuration does not conform to the product's
engineering guidelines and one or more provisioned
modules must be modified or deleted to bring the
configuration into conformance.
Standing Conditions
PWRNOAVAIL (Insufficient Power)

The corresponding SNMP name for this condition is “insufficientPower”.
Table 353: PWRNOAVAIL (Standing Condition)

Severity
SHELF MJ The equipment 1 Verify that the power units are

consumes the provisioned and operational.
power supplied 2 Verify that the shelf power
by the power redundancy is provisioned
units. correctly.
3 If possible, install and provision
another power unit.
4 Remove and delete the last
provisioned module.
PWRPROTNA (PSU-Not Protected)

The corresponding SNMP name for this condition is “powerMissing”.
Table 354: PWRPROTNA (Standing Condition)

Severity Action
SHELF MN One of the two power Ensure that both of the power
supply modules in a master supply modules are correctly
shelf is either not yet provisioned and that both units
provisioned or is are properly equipped with
provisioned but not operational modules.
equipped.
Standing Conditions
RCVCLK (Rx Clock-Loss of Sync)

The corresponding SNMP name for this condition is “lossOfReceiverClockRecovery”.
Table 355: RCVCLK (Standing Condition)

Severity
CH CR The receiver is 1 Verify that the facility is provisioned

unable to derive a correctly.
clock reference 2 Verify that the incoming cable is the
from the input correct cable and that the transmit
signal. and receive ports are connected to
For optical signals, their proper respective portions of
this means that an the cable (i.e. that the fibers are not
optical carrier is swapped between transmit and
present to at least receive or that a crossover cable
some degree, but has not been used in place of a
that the received straight cable for electrical Ethernet
power level is too connections).
low or the bit error
rate is too high or 3 Verify that the incoming cable
the modulation rate (electrical or optical) is firmly
is too low in order connected to the receive port
for a timing associated with the facility and that
reference to be the connector is not physically
recovered from the impaired by obstructions, dirt or
signal. component damage. Clean the
examination.
Standing Conditions
RDI (RDI)
The corresponding SNMP name for this condition is “cfmRemoteDefectIndication”.
Table 356: RDI (Standing Condition)

DOWN- NR The incoming signal carries a This condition is

MEP persistent Remote Defect Indication informative and no
(RDI), indicating that the signal in the corrective action is
opposite direction has failed prior to its needed.
termination point.
RDI-L (Line/MS-Remote Defect)

The corresponding SNMP name for this condition is “remoteDefectIndicationLine”.
Table 357: RDI-L (Standing Condition)

CH NR The incoming signal carries a persistent This condition is

Remote Defect Indication (RDI, also informative and no
known as Far-End Receive Failure or corrective action is
FERF) indicating that the Line/Multiplex needed.
Section signal in the opposite direction
has failed prior to its termination point.
RDI-LP (Path LO-Remote Defect)

“remoteDefectIndicationLowerOrderPath”.
Table 358: RDI-LP (Standing Condition)

VC3 NR The incoming path carries a persistent This condition is

Remote Defect Indication (RDI, also informative and no
known as Far-End Receive Failure or corrective action is
FERF) indicating that the path signal in needed.
the opposite direction has failed prior to
its termination point.
Standing Conditions
RDI-P (Path-Remote Defect)

“remoteDefectIndicationHigherOrderPath”.
Table 359: RDI-P (Standing Condition)

STS1, NR The incoming path carries a persistent This condition is

STS3C, Remote Defect Indication (RDI, also informative and no
STS24C, known as Far-End Receive Failure or corrective action is
STS48C FERF) indicating that the path signal in needed.
the opposite direction has failed prior to
VC4, its termination point.
VC4C8,
VC4C16
REMLINK (Link-Communication Fail)

The corresponding SNMP name for this condition is “dcnCommunicationFail”.
Table 360: REMLINK (Standing Condition)

Severity Cause
SH:I2C MJ The connection 1 Verify that the port is correctly

between the provisioned and that the port should be
PSCU port and active (i.e. that it is intended to support
its supported a filter shelf).
40CSM2HU-D 2 Verify that the cable between the port
shelf is not and the filter module is connected
operating firmly at each end and that the cable is
normally. not physically damaged.
3 If more than one port on the PSCU
module is provisioned and all
provisioned ports are failed in the same
manner, replace the PSCU module.
4 If more than one port on the PSCU
module is active and the other ports in
use are operating without fault, replace
the cable.
5 Replace the 40CSM2HU-D connected
to the port reporting the failure.
Standing Conditions
RMVD (Equipment Removed)

The corresponding SNMP name for this condition is “removed”.
Table 361: RMVD (Standing Condition)

Severity Corrective
Action
MOD CR A provisioned unit does not have a Install the

module physically present. appropriate unit
PSU1HU-AC MN (shelf, module or
PSU7HU-AC
plug).
PSU7HU-
DC
PSU9HU-
DC
NCU-II-P
2OSCM MJ
OSCM
OSCM-PN
PSCU
SCU
SCU-E
SCU-S
SCU-II
NCU CR A problem establishing Restart the

NCU2E synchronization between the Network Element.
NCU-II NCU/NCU2E/NCU-II and SCU
software after an SCU card re-
insertion in SHELF-1 means that the
NCU/NCU2E control software is not
In this case, the slot LED will be lit
solid red and the Ethernet and serial
ports will function, but the PPPIP
facility terminations will not.
SCHED-NTP (NTP-Setup Required)

The corresponding SNMP name for this condition is “ntpForSchedEqlzRequired”.
Table 362: SCHED-NTP (Standing Condition)

Severity Action
COM NA The Network Time Protocol Provision at least one

server(s) and services, which NTP server and enable
are required for correct operation operation of the NTP
of scheduled equalization services.
operations, are not provisioned.
Standing Conditions
SD-ATRCV (Rx Signal Degrade)

The corresponding SNMP name for this condition is “signalDegradeOlm”.
Table 363: SD-ATRCV (Standing Condition)

Severity
DCN MN1 The calculated span 1 Verify that the facility is provisioned correctly.
attenuation of the OSC on 2 Verify that the incoming cable is the correct
the optical span connected cable and that the transmit and receive ports are
to the OSCM Rx port is connected to their proper respective portions of
greater than the defined "Rx the cable (i.e. that the fibers are not swapped
Degrade Threshold" on the between transmit and receive or that a
OSCM but is not so low as crossover cable has not been used in place of a
to cause a loss of signal straight cable for electrical Ethernet
condition. connections).
3 Verify that the incoming cable (electrical or
optical) is firmly connected to the receive port
obstructions, dirt or component damage. Clean
the connector or replace the cable, plug or
OM MJ The received signal level for module, as appropriate, depending upon the
the pilot laser has dropped cause determined from the physical
below a defined threshold examination.
(SDATRCV-HT) but is not 4 Verify that a signal is present at the cable
so low as to cause a loss of termination and that the signal conforms to the
signal condition. required specifications (e.g. minimum and
facility.
1The default severity of this condition is Minor if the associated entity was provisioned
with R12.3 or higher software version. For entities provisioned with older software
versions, this condition is raised with the severity setting that was in effect during
provisioning, even after upgrading to R12.3 or higher.
Standing Conditions
SD-L (Line/MS-Signal Degrade)

The corresponding SNMP name for this condition is “signalDegradeLine”.
Table 364: SD-L (Standing Condition)

Severity Cause
CH: MJ The received 1 Verify that the facility is provisioned

{ OC3 | signal has correctly (especially the attributes
OC12 | exceeded the quoted at left).
OC48 | bit error rate 2 Verify that the incoming cable is the
OC192 } defined by the correct cable and that the transmit and
facility’s SDHT- receive ports are connected to their
L attribute proper respective portions of the cable
value. (i.e. that the fibers are not swapped
CH: The received obstructions, dirt or component
{ STM1 | signal has damage. Clean the connector or
STM4 | exceeded the replace the cable, plug or module, as
STM16 | number of block appropriate, depending upon the cause
STM64 } errors defined determined from the physical
by the facility’s examination.
SDHT-MS
attribute value
during an
interval defined
by the facility’s
SDPER-MS
attribute value.
the problem.
the facility.
Standing Conditions
SD-LINK__VECTOR (Link-Degrade
(OSC))
This condition is superseded by SF-LINK__VECTOR. The corresponding SNMP name
for this condition is “signalDegradationonLinkVector”.
Table 365: SD-LINK__VECTOR (Standing Condition)

Severity
OM MJ The received signal 1 Verify that the DCN facility is provisioned

level on the DCN link correctly and that the correct association
carrying the APS exists between the OM FFP and the 2OSCM
signalling information for module supporting the APS signalling
this facility has dropped exchange.
below a defined 2 Verify that the incoming cable of the relevant
threshold but is not so DCN facility is the correct cable and that the
low as to cause a loss transmit and receive ports are connected to
of signal condition. their proper respective portions of the cable
(i.e. that the fibers are not swapped between
3 Verify that the incoming optical cable is firmly
the relevant DCN facility and that the
Clean the connector or replace the cable, plug
or module, as appropriate, depending upon
examination.
the required specifications (for example,
minimum and maximum power levels). Most
likely an SD-ATRCV (Rx Signal Degrade)
condition indicates the location where the
problem needs to be repaired. In rare cases,
the ATRCV-HT needs to be adjusted to a
value within the specificied range to raise the
SD-ATRCV (Rx Signal Degrade) condition.
5 If the condition persists, replace the plug or
module supporting the DCN facility.
Standing Conditions
SD-ODU (ODU-Signal Degrade)

The corresponding SNMP name for this condition is “signalDegradeOdu”.
Table 366: SD-ODU (Standing Condition)

Severity Cause
CH MJ The received 1 Verify that the facility is provisioned

signal has correctly (especially the attributes
exceeded the quoted at left).
number of block 2 Verify that the incoming cable is the
errors defined by correct cable and that the transmit and
the facility’s receive ports are connected to their
SDHT-ODU proper respective portions of the cable
attribute value (i.e. that the fibers are not swapped
during an interval between transmit and receive).
defined by the
facility’s
SDPER-ODU
attribute value.
module, as appropriate, depending
the problem.
the facility.
Standing Conditions
SD-OTU (OTU-Signal Degrade)

The corresponding SNMP name for this condition is “signalDegradeOtu”.
Table 367: SD-OTU (Standing Condition)

Severity
CH MJ The received 1 Verify that the facility is provisioned

signal has correctly (especially the attributes
exceeded the quoted at left).
number of block 2 Verify that the incoming cable is the
errors defined by correct cable and that the transmit
the facility’s and receive ports are connected to
SDHT-OTU their proper respective portions of the
attribute value cable (i.e. that the fibers are not
during an interval swapped between transmit and
defined by the receive).
facility’s SDPER-
OTU attribute
is firmly connected to the receive
value.
port associated with the facility and
the problem.
Standing Conditions
SD-PCS (PCS-Signal Degrade)

The corresponding SNMP name for this condition is “pcsSignalDegrade”.
Table 368: SD-PCS (Standing Condition)

Severity
CH MJ The number of 1 Verify that the facility is

coding errors (e.g. provisioned correctly.
8B/10B coding 2 Verify that the incoming cable is
errors, 64B/66B the correct cable and that the
coding errors) transmit and receive ports are
detected in the connected to their proper
signal has exceeded respective portions of the cable
the defined level at (i.e. that the fibers are not
which the signal swapped between transmit and
quality is deemed to receive).
reach the threshold
3 Verify that the incoming optical
for being declared
fiber is firmly connected to the
degraded.
facility and that the connector is
not physically impaired by
Standing Conditions
SD-S (Sec/RS-Signal Degrade)

The corresponding SNMP name for this condition is “signalDegradeScn”.
Table 369: SD-S (Standing Condition)

Severity
CH: MJ The received signal 1 Verify that the facility is

{ OC768 } has exceeded the provisioned correctly (especially
bit error rate the attributes quoted at left).
defined by the 2 Verify that the incoming cable is
facility’s SDHT-S the correct cable and that the
attribute value. transmit and receive ports are
connected to their proper
respective portions of the cable
(i.e. that the fibers are not
receive).
CH: The received signal not physically impaired by
{ STM256 } has exceeded the obstructions, dirt or component
number of block damage. Clean the connector or
errors defined by replace the cable, plug or module,
the facility’s as appropriate, depending upon
SDHT-RS attribute the cause determined from the
value during an physical examination.
interval defined by
the facility’s
SDPER-RS
attribute value.
Standing Conditions
SD-TCMA (TCM_A-Signal Degrade)

The corresponding SNMP name for this condition is “signalDegradeOduTcmA”.
Table 370: SD-TCMA (Standing Condition)

Severity
CH MJ The received signal 1 Verify that the facility is

has exceeded the provisioned correctly (especially
number of block the attributes quoted at left).
errors defined by 2 Verify that the incoming cable is
the facility’s SDHT- the correct cable and that the
TCMA attribute transmit and receive ports are
value during an connected to their proper
interval defined by respective portions of the cable
the facility’s (i.e. that the fibers are not
SDPER-TCMA swapped between transmit and
attribute value. receive).
as appropriate, depending upon the
cause determined from the
Standing Conditions
SD-TCMB (TCM_B-Signal Degrade)

The corresponding SNMP name for this condition is “signalDegradeOduTcmB”.
Table 371: SD-TCMB (Standing Condition)

Severity
CH MJ The received signal 1 Verify that the facility is provisioned

has exceeded the correctly (especially the attributes
number of block quoted at left).
errors defined by 2 Verify that the incoming cable is the
the facility’s correct cable and that the transmit
SDHT-TCMB and receive ports are connected to
attribute value their proper respective portions of
during an interval the cable (i.e. that the fibers are not
defined by the swapped between transmit and
facility’s SDPER- receive).
TCMB attribute
value.
is firmly connected to the receive
port associated with the facility and
examination.
cable termination and that the
Standing Conditions
SD-TCMC (TCM_C-Signal Degrade)

The corresponding SNMP name for this condition is “signalDegradeOduTcmC”.
Table 372: SD-TCMC (Standing Condition)

Severity
CH MJ The received signal 1 Verify that the facility is

has exceeded the provisioned correctly (especially
number of block the attributes quoted at left).
errors defined by the 2 Verify that the incoming cable is
facility’s SDHT- the correct cable and that the
TCMC attribute value transmit and receive ports are
during an interval connected to their proper
defined by the respective portions of the cable
facility’s SDPER- (i.e. that the fibers are not
TCMC attribute swapped between transmit and
value. receive).
Standing Conditions
SELFTEST-DEG (Test-Fault)
The corresponding SNMP name for this condition is “encryptionModuleSelfTestFail”.
Table 373: SELFTEST-DEG (Standing Condition)

MOD MJ A self-test of the cryptographic Schedule replacement

functions of the equipment has of the equipment
detected a malfunction, but the during the next
malfunction does not compromise available maintenance
the security of the encrypted interval.
service.
SELFTEST-FAIL (Test-Fail)
“encryptionModuleSelfTestFailCritical”.
Table 374: SELFTEST-FAIL (Standing Condition)

Severity Corrective
Action
MOD CR A self-test of the cryptographic functions of the Replace the

equipment has detected a serious malfunction equipment.
which means that the security of the encrypted
service has been compromised, and therefore
the service has been suspended (traffic
interrupted).
SF-CFM0 (CFM-Fail Level 0)

The corresponding SNMP name for this condition is “sfCfmLevel0L2”.
Table 375: SF-CFM0 (Standing Condition)

Severity
ELAN, NR The MEP This condition is informative and no

ELINE associated with the corrective action is required.
facility at level 0 has Corrective action will be taken in
detected a signal response to whatever condition(s)
failure condition. report the more fundamental facility or
equipment failure which leads to this
condition.
Standing Conditions


Severity

facility at level 1 has Corrective action will be taken in
detected a signal response to whatever condition(s)
failure condition. report the more fundamental facility or
equipment failure which leads to this
condition.


Severity Cause

ELINE associated with corrective action is required. Corrective
the facility at action will be taken in response to
level 2 has whatever condition(s) report the more
detected a fundamental facility or equipment failure
signal failure which leads to this condition.
condition.


Severity Cause

detected a signal fundamental facility or equipment failure
failure condition. which leads to this condition.
Standing Conditions


Severity Cause

detected a fundamental facility or equipment failure
signal failure which leads to this condition.
condition.


Severity

facility at level 5 Corrective action will be taken in
has detected a response to whatever condition(s)
signal failure report the more fundamental facility or
condition. equipment failure which leads to this
condition.


Severity Cause

detected a signal fundamental facility or equipment failure
failure condition. which leads to this condition.
Standing Conditions
SF-CFM7 (CFM Fault-Level 7)


Severity

the facility at level action will be taken in response to
7 has detected a whatever condition(s) report the more
signal failure fundamental facility or equipment failure
condition. which leads to this condition.
SF-LINK (Link-Signal Failure)

The corresponding SNMP name for this condition is “signalFailureOnLink”.
Table 383: SF-LINK (Standing Condition)

Severity Cause
CH NR The network This condition is informative and no

side signal corrective action is needed. Corrective
supporting the action will be taken in response to the signal
virtual facility failure condition reported upstream. SF-
reporting this LINK is applicable to 4TCA4G-PCN-
condition has 4GU+4G and 4TCA4G-PCN-4GUS+4G
failed. modules.
Standing Conditions
SF-LINK__VECTOR (Link-Fail (OSC))

The corresponding SNMP name for this condition is “signalFailureonLinkVector“.
Table 384: SF-LINK__VECTOR (Standing Condition)

Severity
OM Critical The received signal on the 1 Verify that the DCN facility is provisioned
DCN link carrying the APS correctly and that the correct association exists
signalling information for between the OM FFP and the 2OSCM module
this facility has a loss of supporting the APS signalling exchange.
signal condition. This 2 Verify that the incoming cable of the relevant
condition is applicable to DCN facility is the correct cable and that the
VSM modules. transmit and receive ports are connected to their
proper respective portions of the cable (i.e. that
the fibers are not swapped between transmit and
receive).
3 Verify that the incoming optical cable is firmly
connected to the receive port associated with the
relevant DCN facility and that the connector is
replace the cable, plug or module, as appropriate,
depending upon the cause determined from the
problem upstream (most likely a LOS condition on
an upstream node) and repair the problem.
5 Replace the plug or module supporting the DCN
facility.
SF-OPU (OPU-Signal Fail)

The corresponding SNMP name for this condition is “signalFailureOPU”.
Table 385: SF-OPU (Standing Condition)

Severity
CH MJ The signal mapped This condition is informative and no

into the OPU payload corrective action is needed.
area of the reporting Corrective action will be taken in
facility has failed. response to the signal failure
condition reported upstream.
Standing Conditions
SGEO-AMP (Amplifier Outage)

The corresponding SNMP name for this standing condition is “ampFailure”.
Table 386: SGEO-AMP (Standing Condition)

Severity Action
CH NR The amplifier upstream of This condition is informative

the facility has been and no corrective action is
shutdown, reducing the needed.
optical power of the facility
below the normal operating
level.
Standing Conditions
SGEO-CPORT (C Port Outage)

The corresponding SNMP name for this condition is “lossOfSignalCPort”.
Table 387: SGEO-CPORT (Standing Condition)

Severity Cause
CH NR The signal 1 Verify that the facility is correctly

arriving on the cross-connected to the intended
client port which incoming signal.
is cross 2 Verify that the incoming cable of the
connected to the relevant cross connected facility is
facility has the correct cable and that the transmit
failed. and receive ports are connected to
receive).
3 Verify that the incoming optical cable
is firmly connected to the receive port
associated with the relevant cross
connected facility and that the
connector is not physically impaired
by obstructions, dirt or component
appropriate, depending upon the
cause determined from the physical
examination.
4 Verify that the incoming signal
specifications (e.g. maximum power
facility.
Standing Conditions
SGEO-FIBER (Fiber-Connect Missing)

The corresponding SNMP name for this condition is “fiberConnectionMissing”.
Table 388: SGEO-FIBER (Standing Condition)

Severity Cause
DCN: NA A provisioned Review the provisioned fiber

{LIFTENUM| inter-port fiber connections (physical termination point
LIFTEUNN connection cross-connections) within the node
LIFVTENUM| which is reporting the condition and provision the
LIFVTEUNN} required by missing fiber cross connection.
one or more It may be beneficial to review the
provisioned autonomous output log buffer to locate
services reports of provisioning changes made
(connections) shortly before the condition was initially
is missing. raised - the log may contain a change
report which helps identify a connection
which was inappropriately deleted or
modified.
It may also be beneficial to perform a
node channel trace on each of the
connections associated with the optical
line with which the reporting logical
interface is associated, since the trace
response may help locate the missing
connection as the trace output will
prematurely cease at the point where
the cross connection is missing.
SGEO-LASER (Client Outage)

The corresponding SNMP name for this condition is “serverSignalFailTx”.
Table 389: SGEO-LASER (Standing Condition)

Severity
CH NR The client signal This condition is informative and no

being mapped via the corrective action is needed.
reporting virtual Corrective action will be taken in
facility has failed. response to the signal failure
condition reported upstream.
Standing Conditions
SGEO-NPORT (N Port Outage)

The corresponding SNMP name for this condition is “lossOfSignalNPort”.
Table 390: SGEO-NPORT (Standing Condition)

Severity
CH NR The source of the 1 Verify that the facility is

outbound signal, which correctly cross-connected to
arrived on the network the intended incoming signal.
port, experienced a 2 If the condition still fails to
failure internal to the clear, replace the module
supporting module. supporting the facility.
SGEO-RATE (Plug-Rate Not

Supported)
The corresponding SNMP name for this condition is “facilityDataRateNotSupported”.
Table 391: SGEO-RATE (Standing Condition)

Severity Action
CH CR The physically inserted plug Review the provisioning

cannot support the actual signal attributes associated
rate of the facility. with the plug position and
This situation arises when a plug replace the unacceptable
equipment is provisioned to plug with one of the
ETH support an unspecified rate and required type.
the mismatch can only be
detected once the facility type
details are known.
SGEO-SRV (OSPF Server Outage)

The corresponding SNMP name for this condition is “ospfIpServerNotAvailable”.
Table 392: SGEO-SRV (Standing Condition)

Severity
DCN: {LIFIP| NR The facility has This condition is informative and

LIFTENUM| failed due to a failure no direct corrective action is
LIFTEUNN| of the supporting needed. Corrective action should
LIFVTENUM OSPF IP server. be taken in response to the failure
LIFVTEUNN} reported by the OSPF IP server.
Standing Conditions
SGEO-UPORT (U Port Outage)

The corresponding SNMP name for this condition is “uPortFailure”.
Table 393: SGEO-UPORT (Standing Condition)

Severity
CH NR The fiber carrying 1 If the fiber was accidentally

optical passthrough disconnected, re-connect the
signals from one fiber.
EROADM-DC 2 If the fiber is damaged in any
module to another has way or if it exhibits abnormally
been removed, high optical power loss, replace
broken, is severely it.
bent or has one or
more dirty or
damaged connectors.
SPEQ-LOCKED (Span-Process
Locked)
The corresponding SNMP name for this condition is “processLockedOutSpeq”.
Table 394: SPEQ-LOCKED (Standing Condition)

Severity Action
SPEQ MJ The span equalization This condition is informative.

process is not allowed to Corrective action should be
adjust the facility, due to the taken to clear the fault(s)
following potential faults: blocking the span equalization
• ASE table is not built. process (for example,
ASETAB-NA (ASE Table-Not
• Hardware fault on the
Available), LOS (Loss Of
AMP-S20x module.
Signal), and OOSDSBLD
• No channel is present on (OOS Disabled)).
this entity (LOS).
• VOM-x-y-BRMN entity
is disabled.
Standing Conditions
SPEQ-OPT-LO (Span-Tx Power Low)

The corresponding SNMP name for this condition is “optLowSpeq”.
Table 395: SPEQ-OPT-LO (Standing Condition)

Severity Cause
SPEQ MJ The measured 1 Review the span equalization

per channel provisioning values for the power per
optical transmit channel, set point and gain calibration
power is below settings and correct any erroneous
the provisioned values.
level by 2 dBm or 2 Verify that any dispersion
more. compensating elements or optical
pads along the incoming signal path
are of the correct type and value and
replace any which do not conform to
the engineered values.
3 Progressing upstream towards the
optical source, verify the optical
power levels of the signals supplied
as input to the amplifier supporting the
entity reporting this condition. Verify
that all optical fiber cables are
correctly attached, that they are
undamaged, are not bent, and that the
fiber connectors themselves are
clean and undamaged. At each
equipment module, verify that the
optical transmit power of the signal
sent towards the entity reporting the
condition is within specifications and
adjust provisioning values found in
error as necessary, or replace any
modules which fail to meet their
required optical performance.
4 At the optical source(s), verify that
the correct optical source is in use
and that it is operating within
specifications. Replace any optical
source (module or pluggable) found to
be failed or outside its operating
specifications.
Standing Conditions
SPEQ-PPC-OOR (Span-Adopt Exceeds

PPC)
The corresponding SNMP name for this condition is “ppcOutOfRangeSpeq”.
Table 396: SPEQ-PPC-OOR (Standing Condition)

Severity
SPEQ MJ The power-per- 1 Review the span equalization

channel value provisioning values for the power
which was adopted per channel, set point and gain
during configuration calibration settings and correct any
of the span erroneous values.
equalization entity 2 Verify that any dispersion
is outside of the compensating elements or optical
allowed value pads along the incoming signal path
range. are of the correct type and value
and replace any which do not
conform to the engineered values.
3 Progressing upstream towards the
optical source, verify the optical
power levels of the signals supplied
as input to the amplifier supporting
the entity reporting this condition.
Verify that all optical fiber cables
are correctly attached, that they are
undamaged, are not bent, and that
the fiber connectors themselves are
clean and undamaged. At each
equipment module, verify that the
optical transmit power of the signal
sent towards the entity reporting the
condition is within specifications
and adjust provisioning values
found in error as necessary, or
replace any modules which fail to
meet their required optical
performance.
4 At the optical source(s), verify that
the correct optical source is in use
and that it is operating within
specifications. Replace any optical
source (module or pluggable) found
to be failed or outside its operating
specifications.
Standing Conditions
SPEQ-PPCLIMIT (Span-PPC Exceeds

Limit)
The corresponding SNMP name for this condition is “ppcLimitExceededSpeq”.
Table 397: SPEQ-PPCLIMIT (Standing Condition)

Severity
SPEQ NA The value provisioned for Review the provisioned value

the per-channel power for the per-channel power level,
level on a span exceeds the number of channels
the allowable limit supported within the band, and
determined by the the type of configuration (e.g.
properties of the Fixed OADM versus
configuration, including Reconfigurable OADM)
factors affected by the applicable to the span.
supported number of Correct any values which do
channels within the band. not conform to the network
engineering specifications.
Standing Conditions
SPEQGA-FAILED (Span-Adopt Gain

Fail)
The corresponding SNMP name for this condition is “gainAdoptFailedSpeq”.
Table 398: SPEQGA-FAILED (Standing Condition)

Severity Cause
SPEQ MJ The preceding 1 Verify that automatic span

attempt to adopt equalization has been enabled at both
the current span ends of the optical line and that all
equalization level elements have been correctly
settings has equipped and provisioned. Correct
failed because any equipping or provisioning errors or
one of the omissions and address any active
required fault conditions on any of the
conditions for equipment and facilities along the
successful optical path.
adoption has not 2 Verify that the near-end OSC
been met. equipment and facility is properly
equipped, configured, in-service,
error-free, and that it is associated
with the SPEQ entity. Also verify that
the correct fiber map entries are
provisioned to associate the OSC to
the optical line associated with the
amplifier. Correct any provisioning
errors or omissions, and replace any
failed elements.
3 Verify that the OSCs optical fiber
cables are correctly attached, that
they are undamaged, are not bent,
and that the fiber connectors
themselves are clean and
undamaged. Verify that the optical
receive power of the OSC signal is
within specifications and correct any
upstream fiber problems or far-end
OSC equipment or facility failures.
4 Once any errors and/or omissions are
corrected, disable automatic span
equalization and then re-enable it,
specifying adoption of the existing
gain equalization settings - this will re-
initiate the adoption process.
Standing Conditions
SPEQMSG-LOSS (Span-Message Loss)

The corresponding SNMP name for this condition is “messageLossSpeq”.
Table 399: SPEQMSG-LOSS (Standing Condition)

Severity
SPEQ MJ The automatic 1 Verify that automatic span

span equalization equalization has been enabled on
protocol is not the far-end of the optical line and
receiving that all elements have been
messages from correctly equipped and provisioned.
the node at the far- Correct any equipping or
end of the optical provisioning errors or omissions.
line. 2 Verify that the near-end OSC
equipment and facility is properly
equipped, configured, in-service,
error-free, and that it is associated
with the SPEQ entity. Also verify
that the correct fiber map entries are
provisioned to associate the OSC
to the optical line associated with
the amplifier. Correct any
provisioning errors or omissions,
and replace any failed elements.
3 Verify that the OSCs optical fiber
cables are correctly attached, that
they are undamaged, are not bent,
and that the fiber connectors
themselves are clean and
undamaged. Verify that the optical
receive power of the OSC signal is
within specifications and correct
any upstream fiber problems or far-
end OSC equipment or facility
failures.
Standing Conditions
SPGAIN-OOR-HI (Span-Gain Too

High)
The corresponding SNMP name for this condition is “gainTooHighSpeq”.
Table 400: SPGAIN-OOR-HI (Standing Condition)

Severity
SPEQ MJ The required gain 1 Review the span equalization provisioning

value determined by values for the power per channel, set point and
the automatic span gain calibration settings and correct any
equalization feature erroneous values. In particular, verify that the
for the associated set point and power-per-channel differential is
amplifier module is within the maximum allowable gain range of the
greater than the amplifier module in use, and adjust the values
maximum value as necessary to bring the differential within the
supported by that supported range of gain supported by the
module type. amplifier.
2 Verify that the amplifier module in use is of the
correct type as determined by the optical
network span engineering plan. Exchange the
amplifier module for one of the correct type if
the existing type is found to be in error (this will
require re-provisioning of the amplifier and its
supported entities, and will be service
affecting).
3 Verify that any dispersion compensating
elements or optical pads along the incoming
signal path are of the correct type and value and
replace any which do not conform to the
engineered values.
4 Progressing upstream towards the optical
source, verify the optical power levels of the
signals supplied as input to the amplifier
supporting the entity reporting this condition.
Verify that all optical fiber cables are correctly
attached, that they are undamaged, are not
bent, and that the fiber connectors are clean
and undamaged. At each equipment module,
verify that the optical transmit power of the
signal sent towards the entity reporting the
condition is within specifications and adjust
provisioning values found in error as necessary,
or replace any modules which fail to meet their
required optical performance.
5 At the optical source(s), verify that the correct
optical source is in use and that it is operating
within specifications. Replace any optical
source (module or pluggable) found to be failed
or outside its operating specifications.
Standing Conditions
SPGAIN-OOR-LO (Span-Gain Too

Low)
The corresponding SNMP name for this condition is “gainTooLowSpeq”.
Table 401: SPGAIN-OOR-LO (Standing Condition)

Severity
SPEQ MJ The required gain value 1 If this is a colorless configuration, check whether there
determined by the is sufficient channel power at the CCM-C96/9 client
automatic span ports. Adjust the power levels, if required.
equalization feature for 2 Review the span equalization provisioning values for
the associated the power per channel, set point and gain calibration
amplifier module is less settings and correct any erroneous values. In particular,
than the minimum verify that the set point and power-per-channel
value supported by that differential is within the minimum allowable gain range
module type. of the amplifier module in use, and adjust the values as
In a colorless necessary to bring the differential within the supported
configuration, this range of gain supported by the amplifier.
alarm may also indicate
insufficient channel 3 Verify that the amplifier module in use is of the correct
power at the CCM- type as determined by the optical network span
C96/9 client ports. engineering plan. Exchange the amplifier module for
one of the correct type if the existing type is found to be
in error (this will require re-provisioning of the amplifier
and its supported entities, and will be service affecting).
4 Verify that any dispersion compensating elements or
optical pads along the incoming signal path are of the
correct type and value and replace any which do not
conform to the engineered values.
5 Progressing upstream towards the optical source,
verify the optical power levels of the signals supplied as
input to the amplifier supporting the entity reporting this
condition. Verify that all optical fiber cables are
correctly attached. At each equipment module, verify
that the optical transmit power of the signal sent
towards the entity reporting the condition is within
specifications and adjust provisioning values found in
error as necessary, or replace any modules which
exceed their specified maximum optical output power
levels.
6 At the optical source(s), verify that the correct optical
source is in use and that it is operating within
specifications. Replace any optical source (module or
pluggable) found to be failed or outside its operating
specifications.
Standing Conditions
SQM-LP (Path LO-Loss of Sequence)

The corresponding SNMP name for this condition is “lossofSequenceLowerOrderPath”.
Table 402: SQM-LP Details and Probable Causes
AIDTYPE Default Probable Cause

Severity
VC3 CR The path is configured as a member of a virtual concatenation

bundle and the sequence indicator values have been found to
be in error. The most probable causes of this are:
• A difference in the provisioned bundle size, member
paths, or order of member paths between the near and far-
end,
• A difference in the provisioned properties of the GFP
mapping facilities between the near and far-end,
• Impairment of the received signal affecting one or more of
the paths,
• Mis-connection of cross-connected paths used to form the
virtual concatenation bundle at an intermediate cross-
connection point between the near and far-end,
• Equipment failure at the near or far-end.
Standing Conditions
Table 403: SQM-LP Suggested Corrective Action
1 Verify that the GFP facility which employs the path as a member of its virtually
concatenated bundle is correctly provisioned and is operating in-service normal (“In
Service”).
2 Verify that the far-end GFP facility instance is also correctly and consistently
provisioned relative to the near-end instance, and that it is operating in-service
3 Verify that the incoming cable is the correct cable and that the transmit and receive
ports are connected to their proper respective portions of the cable (i.e. that the
fibers are not swapped between transmit and receive).
4 Verify that the incoming optical fiber is firmly connected to the receive port
associated with the facility and that the connector is not physically impaired by
obstructions, dirt or component damage. Clean the connector or replace the cable,
plug or module, as appropriate, depending upon the cause determined from the
to the required specifications (e.g. minimum and maximum power levels). If the
signal meets the required specifications, proceed to the next step below.
Otherwise, locate the source of the signal problem upstream and repair the
problem.
6 Verify that each intermediate point through which the paths within the bundle pass
are correctly cross-connected.
7 Replace the near-end plug supporting the facility.
9 Replace the near-end module supporting the facility.
Standing Conditions
SQM-P (Path-Loss of Sequence)

The corresponding SNMP name for this condition is“lossofSequenceHigherOrderPath”.
Table 404: SQM-P (Standing Condition)

Severity
STS1, CR The path is configured as a 1 Verify that the GFP facility which employs the path
STS3C member of a virtual as a member of its virtually concatenated bundle is
concatenation bundle and correctly provisioned and is operating in-service
the sequence indicator normal (“In Service”).
values were found to be in 2 Verify that the far-end GFP facility instance is also
error. correctly and consistently provisioned relative to the
The most probable causes near-end instance, and that it is operating in-service
of this are: normal (“In Service”) state.
• A difference in the 3 Verify that the incoming cable is the correct cable
provisioned bundle and that the transmit and receive ports are
size, member paths, connected to their proper respective portions of the
or order of member cable (i.e. that the fibers are not swapped between
paths between the transmit and receive).
near and far-end,
4 Verify that the incoming optical fiber is firmly
• A difference in the connected to the receive port associated with the
provisioned properties facility and that the connector is not physically
of the GFP mapping impaired by obstructions, dirt or component
facilities between the damage. Clean the connector or replace the cable,
near and far-end, plug or module, as appropriate, depending upon the
• Impairment of the cause determined from the physical examination.
received signal 5 Verify that a signal is present at the cable
VC4 affecting one or more termination and that the signal conforms to the
of the paths, required specifications (e.g. minimum and
• Mis-connection of maximum power levels). If the signal meets the
cross-connected required specifications proceed to the next step,
paths used to form the otherwise locate the source of the signal problem
virtual concatenation upstream and repair the problem.
bundle at an 6 Verify that each intermediate point through which
intermediate cross- the paths within the bundle pass are correctly cross-
connection point connected.
between the near and
far-end, 7 Replace the near-end plug supporting the facility.
• Equipment failure at 8 Replace the far-end plug supporting the facility.

the near or far-end. 9 Replace the near-end module supporting the facility.
Standing Conditions
SSF (Server Signal Fail)

The corresponding SNMP names for this condition can be
“cfmServerSignalFailure”, “serverSignalFail” or “serverSignalFailL2”.
Table 405: SSF (Standing Condition)

Severity
DOWN-MEP, NR An upstream This condition is informative and no

ELAN, facility has failed, corrective action is needed.
ELINE, causing a loss of Corrective action will be taken in
ELINE-PPP, the server layer response to the signal failure reported
ETREE, LAG signal. upstream.
SSF-DCN (DCN-Server Signal Fail)

The corresponding SNMP name for this condition is “dcnServerSignalFailure”.
Table 406: SSF-DCN (Standing Condition)

Severity
DCN: {LIFIP| NR An upstream This condition is informative and

LIFTENUM| facility has failed, no corrective action is needed.
LIFTEUNN| causing a loss of Corrective action will be taken in
LIFVTENUM the DCN signal. response to the signal failure
LIFVTEUNN} reported upstream.
SSF-GFP (GFP-Server Signal Fail)

The corresponding SNMP name for this condition is “serverSignalFailureGfp”.
Table 407: SSF-GFP (Standing Condition)

Severity
CH: { 1GBE | NR An upstream facility This condition is informative and no

FC | 2GFC } has failed, causing a corrective action is needed.
loss of the GFP Corrective action will be taken in
CH: GFPT mapped signal. response to the signal failure
reported upstream.
Standing Conditions
SSF-ODU (ODU-Server Signal Fail)

The corresponding SNMP name for this condition is “serverSignalFailureODU”.
Table 408: SSF-ODU (Standing Condition)

Severity
CH NR An upstream facility has This condition is informative and

failed, causing a loss of no corrective action is needed.
the ODU layer signal. Corrective action will be taken in
response to the signal failure
reported upstream.
SSF-OTU (OTU Server Signal Fail)

The corresponding SNMP name for this condition is “otuServerSignalFail”.
Table 409: SSF-OTU (Standing Condition)

Severity
CH NR An upstream facility This condition is informative

has failed. requires no corrective action.
Corrective action will be taken in
reported upstream.
SSF-P (Path-Server Signal Fail)

The corresponding SNMP name for this condition is “serverSignalFailurePath”.
Table 410: SSF-P (Standing Condition)

Severity
STS24C, NR An upstream facility has This condition is informative and

STS48C failed, causing a loss of no corrective action is needed.
the path layer signal. Corrective action will be taken in
VC4C8, response to the signal failure
VC4C16 reported upstream.
Standing Conditions
SSF-RX (Server Signal Fail Rx)

The corresponding SNMP name for this condition is “serverSignalFailRx”.
Table 411: SSF-RX (Standing Condition)

Severity
CH NR An upstream facility This condition is informative and

has failed. requires no corrective action.
Corrective action will need to be
taken in response to the signal
SSF-S (Sec-Server Signal Fail)

The corresponding SNMP name for this condition is “serverSignalFailureSectionRS”.
Table 412: SSF-S (Standing Condition)

Severity
CH NR An upstream facility This condition is informative and no

has failed, causing a corrective action is needed.
loss of the path signal. Corrective action will be taken in
reported upstream.
Standing Conditions
SSF-VF (Chan-Server Signal Fail)

The corresponding SNMP name for this condition is “serverSignalFailureVf”.
Table 413: SSF-VF (Standing Condition)

Severity Cause
CH: { 1GBE | NR The multiplexed This condition is informative and no

FC | 2GFC } facility corrective action is needed. Corrective
transporting the action will be taken in response to the
virtual facility signal failure reported upstream.
payload from the
far-end has
failed.
CH: OCH The client signal 1 Verify that the fiber supplying the
carried by the incoming signal of the client port
optical channel has not been removed, broken,
has failed. severely bent or sustained damage
to an optical connector. If the cable
has accidentally been removed,
replace it. If the cable or either or
both of its connectors is damaged
or exhibits excessive loss, replace
it.
2 Determine if the source of client
signal (i.e. the transponder or
muxponder) has failed or if the
signal has been manually disabled.
If the signal is intentionally
disabled for maintenance
purposes, no further action is
needed. If the module providing the
source of the optical signal has
failed, replace it.
3 If the signal has been
automatically suppressed due to
an upstream failure, no further
corrective actions are needed - the
condition will clear once the
upstream problem has been
corrected.
Standing Conditions
SWDX-INHIBIT (Partner-Switch
Inhibit)
The corresponding SNMP name for this condition is “switchToDuplexInhibited”.
Table 414: SWDX-INHIBIT (Standing Condition)

Severity
MOD MN This condition is This condition is informative and requires

raised following a no corrective action.
user-initiated An operator may issue the command to
command to prevent a switchover, before performing
prevent switching maintenance activities on the partner
to the partner controller.
controller, in a This condition serves as a reminder for
duplex protection the operator to release the inhibit request,
group. at the appropriate time. It clears
automatically once the inhibit command
is switched off/released.
SWITCH (Switch Request Fail)

The corresponding SNMP name for this condition is “switchFailed”.
Table 415: SWITCH (Standing Condition)

Severity Action
MOD CR The module failed to complete a Replace the failed

switch or bridge operation within module.
the required time period, due to
component failure.
Standing Conditions
T-AMP-FHT (Supply-Current High)

The corresponding SNMP name for this condition is “currentTooHigh”.
Table 416: T-AMP-FHT (Standing Condition)

Severity
MOD NA The current drawn 1 Verify that the set of cards

through one or both of physically present within the
the main supply shelf (whether provisioned or
feeds to the module not) conform to the product’s
exceeds the normal engineering guidelines and
operating level for remove or re-configure the
which the power modules as necessary.
supply unit is rated. 2 Replace the power supply
module.
Standing Conditions
T-ATRCV-HT (Attenuation Rx High)

“attOnReceiverFiberHigherThanMonitor”.
Table 417: T-ATRCV-HT (Standing Condition)

Severity
DCN MN The signal level at the receiver 1 Verify that the facility is provisioned
input after allowing for the correctly and that the high attenuation
expected span loss is such threshold level is set to the intended value.
that the amount of attenuation 2 Verify that the incoming cable carrying the
on the incoming fiber has been facility is the correct cable and that the
determined to exceed the transmit and receive ports are connected to
provisioned threshold level. their proper respective portions of the cable
(i.e. that the fibers are not swapped between
3 Verify that the incoming optical fiber cable is
OM The signal level detected by obstructions, dirt or component damage.
the receiver for the optical line Clean the connector or replace the cable,
monitor signal on the RSM- plug or module, as appropriate, depending
OLM module, after allowing for upon the cause determined from the physical
the expected span loss, is examination.
such that the amount of
attenuation on the incoming
fiber has been determined to
exceed the provisioned
and maximum power levels)1. If the signal
threshold level.
meets the required specifications proceed to
the next step below, otherwise locate the
source of the signal problem upstream and
repair the problem.
facility.
1To separate the DCN signal from the traffic carrying signals optically multiplexed
together within the line side fiber, it may be necessary to employ optical filters in
addition to any external optical power measuring devices employed to perform
these measurements.
Standing Conditions
T-ATRCV-LT (Attenuation Rx Low)

“attOnReceiverFiberLowerThanMonitor”.
Table 418: T-ATRCV-LT (Standing Condition)

Severity
DCN MN The signal level at 1 Verify that the facility is provisioned

the receiver input correctly and that the low
after allowing for attenuation threshold level is set to
the expected span the intended value.
loss is such that 2 Verify that the incoming cable
the amount of carrying the facility is the correct
attenuation on the cable and that the transmit and
incoming fiber has receive ports are connected to their
been determined to proper respective portions of the
be below the cable (i.e. that the fibers are not
provisioned swapped between transmit and
threshold level. receive).
OM The signal level cable termination and that the
detected by the signal conforms to the required
receiver for the specifications (e.g. minimum and
optical line monitor maximum power levels)1. If the
signal on the RSM- signal meets the required
OLM module, after specifications proceed to the next
allowing for the step below, otherwise locate the
expected span source of the signal problem
loss, is such that upstream and repair the problem. It
the amount of may be necessary to pad the
attenuation on the optical line using a fixed or variable
incoming fiber has attenuator to bring the attenuation
been determined to within the specified minimum range
be below the required by the system.
provisioned 4 Replace the plug or module
threshold level. supporting the facility.
1In order to separate the DCN signal from the traffic carrying signals optically
multiplexed together within the line side fiber, it may be necessary to employ optical
filters in addition to any external optical power measuring devices employed to
perform these measurements.
Standing Conditions
T-ATTRMT-HT (Attenuation Tx High)

“attOnReceiverFiberLowerThanMonitor”.
Table 419: T-ATTRMT-HT (Standing Condition)

Severity
DCN NA The attenuation of 1 Verify that the threshold level is

the transmitted provisioned correctly, and that the
signal level as far-end threshold levels are
measured at the far- provisioned in a consistent manner.
end receiver 2 Assuming the near-end and far-end
exceeds the threshold levels are set to
provisioned consistent values, corrective
threshold value. actions would typically occur in
response to a SPGAIN-OOR-HI
(Span-Gain Too High) condition
OM The attenuation of reported by the far-end, in which
the transmitted case this condition is informative in
optical line nature and no additional corrective
monitoring signal actions are needed. If the system
level as measured is configured such that these
at the far-end RSM- corrective actions are normally
OLM module initiated in response to this
receiver exceeds condition instead, please follow the
the provisioned procedures described for the
threshold value. SPGAIN-OOR-HI (Span-Gain Too
High) condition, performing them at
the far-end.
Standing Conditions
T-ATTRMT-LT (Attenuation Tx Low)

“attOnTransmitterFiberLowerThanMonitor”.
Table 420: T-ATTRMT-LT (Standing Condition)

Severity
DCN NA The attenuation of the 1 Verify that the threshold level is

transmitted signal provisioned correctly, and that
level as measured at the far-end threshold levels are
the far-end receiver is provisioned in a consistent
below the provisioned manner.
threshold value. 2 Assuming the near-end and far-
end threshold levels are set to
consistent values, corrective
actions would typically occur in
response to a T-ATRCV-LT
(Attenuation Rx Low) condition
OM The attenuation of the reported by the far-end, in which
transmitted optical case this condition is informative
line monitoring signal in nature and no additional
level as measured at corrective actions are needed. If
the far-end RSM-OLM the system is configured such
module receiver is that these corrective actions are
below the provisioned normally initiated in response to
threshold value. this condition instead, please
follow the procedures described
for the T-ATRCV-LT (Attenuation
Rx Low) condition, performing
them at the far-end.
Standing Conditions
T-BBE-ODU-HT__15MIN (ODU-BBE
15M)
The corresponding SNMP name for this condition is “thres15MinExceededOduBbe”.
Table 421: T-BBE-ODU-HT__15MIN (Standing Condition)

Severity Cause
CH MN The number of This condition is informative and no

background immediate corrective action is required. If
block errors the condition persists across multiple
measured in intervals, it may indicate an imminent failure
the Optical of a more serious nature, including failure of
Data Unit either the source or receiving plug or module
(ODU) layer or a failure in one of the cables along the
exceeds the path between the source and the receiver.
provisioned
15-minute To ensure that the condition is being
threshold reported only under the correct
value. circumstances, verify that the 15-minute
threshold level is provisioned correctly.
T-BBE-OTU-HT__15MIN (OTU-BBE
15M)
The corresponding SNMP name for this condition is “thres15MinExceededOtuBbe”.
Table 422: T-BBE-OTU-HT__15MIN (Standing Condition)

Severity Cause

Transport Unit either the source or receiving plug or module
(OTU) layer or a failure in one of the cables along the
provisioned 15-
minute To ensure that the condition is being
threshold reported only under the correct
Standing Conditions
T-BBE-PCS-HT__15MIN (PCS-BBE
15M)
The corresponding SNMP name for this condition is “thres15MinExceededBbePcs”.
Table 423: T-BBE-PCS-HT__15MIN (Standing Condition)

Severity Cause

Physical Coding immediate corrective action is required. If
Sub-layer the condition persists across multiple
background intervals, it may indicate an imminent
block errors failure of a more serious nature, including
detected by the failure of either the source or receiving plug
receiver or module or a failure in one of the cables
exceeds the along the path between the source and the
provisioned 15- receiver.
minute threshold
value. To ensure that the condition is being
reported only under the correct
circumstances, verify that the 15-minute
T-BBE-TCMA-HT__15MIN (TCM_A-
BBE 15M)
“thres15MinExceededOduTcmABbe”.
Table 424: T-BBE-TCMA-HT__15MIN (Standing Condition)

Severity Cause

measured in the intervals, it may indicate an imminent
Tandem failure of a more serious nature, including
Connection failure of either the source or receiving plug
Monitoring or module or a failure in one of the cables
instance A along the path between the source and the
(TCMA) layer receiver.
exceeds the
provisioned 15- To ensure that the condition is being
minute threshold reported only under the correct
Standing Conditions
T-BBE-TCMB-HT__15MIN (TCM_B-
BBE 15M)
“thres15MinExceededOduTcmBBbe”.
Table 425: T-BBE-TCMB-HT__15MIN (Standing Condition)

Severity Cause

Connection failure of either the source or receiving
Monitoring plug or module or a failure in one of the
instance B cables along the path between the source
(TCMB) layer and the receiver.
exceeds the
T-BBE-TCMC-HT__15MIN (TCM_C-
BBE 15M)
“thres15MinExceededOduTcmCBbe”.
Table 426: T-BBE-TCMC-HT__15MIN (Standing Condition)

Severity

background block immediate corrective action is
errors measured in required. If the condition persists
the Tandem across multiple intervals, it may
Connection indicate an imminent failure of a more
Monitoring instance serious nature, including failure of
C (TCMC) layer either the source or receiving plug or
exceeds the module or a failure in one of the cables
provisioned 15- along the path between the source and
minute threshold the receiver.
value.
To ensure that the condition is being
circumstances, verify that the 15-
minute threshold level is provisioned
correctly.
Standing Conditions
T-BERCE-FEC-HT__15MIN (BER
Before FEC 15M)
The corresponding SNMP name for this condition is “thres15MinExceededFecBERCE”.
Table 427: T-BERCE-FEC-HT__15MIN (Standing Condition)

Severity
CH MN The number of bit This condition is informative and no

errors detected immediate corrective action is required. If
prior to error the condition persists across multiple
correction using intervals, it may indicate an imminent
the Forward Error failure of a more serious nature, including
Correction failure of either the source or receiving
process exceeds plug or module or a failure in one of the
the provisioned cables along the path between the source
15-minute and the receiver.
threshold value.
T-BR-HT (Back Reflection Rx High)

The corresponding SNMP name for this condition is “brPwrRxTooHigh”.
Table 428: T-BR-HT (Standing Condition)

Severity Cause
OM: CR The optical back- This condition is informative and no

RAMAN reflection power immediate corrective action is required. It
level detected may indicate a problem in the
exceeds the transmission fiber cable such as
provisioned excessive bending, stress or breakage, or
maximum contamination or damage to an optical
threshold level. connector along the transmission span.

circumstances,
verify the threshold level is provisioned
correctly.
Standing Conditions
T-BRTX-HT (Back Reflection Tx High)

The corresponding SNMP name for this condition is “backreflectionTooHigh”.
Table 429: T-BRTX-HT (Standing Condition)

Severity Cause
OM CR The optical back- This condition is informative and no

reflection power immediate corrective action is required.
level detected It may indicate a problem in the
exceeds the transmission fiber cable such as
provisioned excessive bending, stress or breakage, or
maximum contamination or damage to an optical
threshold level. connector along the transmission span.

circumstances, verify the threshold level
is provisioned correctly.
Standing Conditions
T-CD-HT (CD Compensation-High)

The corresponding SNMP name for this condition is “chromaticDispersionTooHigh”.
Table 430: T-CD-HT (Standing Condition)

Severity
CH MN The chromatic 1 Verify that the threshold level is

dispersion provisioned correctly.
compensation 2 Verify that the incoming cable is
adjustment exceeds the correct cable and that the
the provisioned transmit and receive ports are
threshold value. connected to their proper
(i.e. that the fibers are not
receive).
replace the cable or plug, as
4 Proceeding upstream, span by
span, verify that the span
engineering specifications (e.g.
levels, span attenuation/loss, fiber
type, chromatic dispersion
correction, PMD). If all spans meet
the required specifications proceed
to the next step below, otherwise
locate the source of the signal
problem upstream and repair the
problem.
facility.
Standing Conditions
T-CD-LT (CD Compensation-Low)

The corresponding SNMP name for this condition is “chromaticDispersionTooLow”.
Table 431: T-CD-LT (Standing Condition)

Severity
CH MN The chromatic 1 Verify that the threshold level is

dispersion provisioned correctly.
compensation 2 Verify that the incoming cable is
adjustment is below the correct cable and that the
the provisioned transmit and receive ports are
threshold value. connected to their proper
replace the cable or plug, as
4 Proceeding upstream, span by
span, verify that the span
engineering specifications (e.g.
levels, span attenuation/loss, fiber
type, chromatic dispersion
correction, PMD). If all spans meet
problem.
facility.
Standing Conditions
T-CDC-HT (CD Compensation-High)

The corresponding SNMP name for this condition is “dispersionCompensationTooHigh”.
Table 432: T-CDC-HT (Standing Condition)

Severity Cause
CH MN The chromatic 1 Verify that the facility is properly

dispersion configured and that it has been properly
compensation set-up. If initial set-up has not yet been
adjustment completed, perform the facility set-up
exceeds the process.
provisioned 2 Verify that the threshold level is
threshold provisioned correctly. Once the
value. threshold value is set correctly, perform
a manual chromatic dispersion
compensation adjustment operation on
the facility to reset the compensation
level.
3 Verify that the incoming cable is the
correct cable and that the transmit and
Clean the connector or replace the cable
or plug, as appropriate, depending upon
examination.
incoming signal cable termination and
that the signal conforms to the required
maximum power levels, span
attenuation/loss, fiber type, chromatic
dispersion, PMD). If the signal meets
the required specifications proceed to
the next step below, otherwise locate
the source of the signal problem
facility.
Standing Conditions
T-CDC-LT (CD Compensation-Low)

The corresponding SNMP name for this condition is “dispersionCompensationTooLow”.
Table 433: T-CDC-L (Standing Condition)

Severity
CH MN The chromatic 1 Verify that the facility is properly configured and that it
dispersion has been properly set-up. If initial set-up has not yet
compensation been completed, perform the facility set-up process.
adjustment is below the 2 Verify that the threshold level is provisioned correctly.
provisioned threshold Once the threshold value is set correctly, perform a
value. manual chromatic dispersion compensation
adjustment operation on the facility to reset the
compensation level.
3 Verify that the incoming cable is the correct cable and
that the transmit and receive ports are connected to
their proper respective portions of the cable (i.e. that
receive).
facility and that the connector is not physically
impaired by obstructions, dirt or component damage.
Clean the connector or replace the cable or plug, as
appropriate, depending upon the cause determined
from the physical examination.
5 Verify that a signal is present at the incoming signal
cable termination and that the signal conforms to the
required specifications (e.g. minimum and maximum
power levels, span attenuation/loss, fiber type,
chromatic dispersion, PMD). If the signal meets the
required specifications proceed to the next step below,
otherwise locate the source of the signal problem
Standing Conditions
T-CE-FEC-HT__15MIN (FEC-Corrected
15M)
The corresponding SNMP name for this condition is “thres15MinExceededFecCE”.
Table 434: T-CE-FEC-HT__15MIN (Standing Condition)

Severity Cause

corrected errors immediate corrective action is required. If
detected by the condition persists across multiple
Forward Error intervals, it may indicate an imminent
Correction failure of a more serious nature, including
exceeds the failure of either the source or receiving
provisioned 15- plug or module or a failure in one of the
minute threshold cables along the path between the source
value. and the receiver.

Standing Conditions
T-CFOT-HT (Carrier Offset High)

The corresponding SNMP name for this condition is “carrierFreqOffsetTooHigh”.
Table 435: T-CFOT-HT (Standing Condition)

Severity
CH MN The carrier frequency 1 Verify that the facility receive frequency (channel
offset exceeds the assignment) is properly configured, and that it
provisioned higher bound matches the assigned frequency at the far-end
threshold. (source) of the signal.
2 Verify that the threshold level is provisioned
correctly.
their proper respective portions of the cable (e.g. that
receive).
4 Verify that the signal path follows the intended routing
and that each module along the path which performs
optical filtering (including ROADMs) is of the correct
type (e.g. that they are of adequate
passband/channel width and spacing).
residual chromatic dispersion and PMD). If the signal
Standing Conditions
T-CFOT-LT (Carrier Offset Low)

The corresponding SNMP name for this condition is “carrierFreqOffsetTooLow”.
Table 436: T-CFOT-LT (Standing Condition)

Severity
CH MN The carrier frequency 1 Verify that the facility receive frequency (channel
offset exceeds the assignment) is properly configured, and that it
provisioned lower bound matches the assigned frequency at the far-end
threshold. (source) of the signal.
2 Verify that the threshold level is provisioned correctly.
their proper respective portions of the cable (e.g. that
receive).
4 Verify that the signal path follows the intended routing
and that each module along the path which performs
optical filtering (including ROADMs) is of the correct
type (e.g. that they are of adequate passband/channel
width and spacing).
Standing Conditions
T-CV-L-HT__15MIN (Line/MS-CV
15M)
The corresponding SNMP name for this condition is “thres15MinExceededSonetLineCV”.
Table 437: T-CV-L-HT__15MIN (Standing Condition)

Severity

line/multiplex immediate corrective action is required.
section layer If the condition persists across multiple
coding violations intervals, it may indicate an imminent
detected by the failure of a more serious nature, including
receiver exceeds failure of either the source or receiving
the provisioned plug or module or a failure in one of the
15-minute cables along the path between the
threshold value. source and the receiver.

T-CV-PCS-HT__15MIN (PCS-CV 15M)

“thres15MinExceededPhysConvCV”.
Table 438: T-CV-PCS-HT__15MIN (Standing Condition)

Severity

Physical Coding immediate corrective action is required.
Sub-layer coding If the condition persists across multiple
violations intervals, it may indicate an imminent
15-minute cables along the path between the
threshold value. source and the receiver.

Standing Conditions
T-CV-S-HT__15MIN (Sec/RS-CV
15M)
“thres15MinExceededSonetSectCV”.
Table 439: T-CV-S-HT__15MIN (Standing Condition)

Severity

section/regenerator immediate corrective action is
section layer required. If the condition persists
coding violations across multiple intervals, it may
detected by the indicate an imminent failure of a more
receiver exceeds serious nature, including failure of
the provisioned 15- either the source or receiving plug or
minute threshold module or a failure in one of the
value. cables along the path between the
source and the receiver.

correctly.
T-CVTX-PCS-HT__15MIN (PCS-CV Tx
15M)
“thres15MinExceededPhysConvCVTX”.
Table 440: T-CVTX-PCS-HT__15MIN (Standing Condition)

Severity

Sub-layer coding the condition persists across multiple
violations intervals, it may indicate an imminent
transmitted failure of a more serious nature, including
exceeds the failure of the source plug or module.
provisioned 15-
minute threshold To ensure that the condition is being
value. reported only under the correct
Standing Conditions
T-DE-PCS-HT__15MIN (PCS-Disparity
Error 15M)
“thres15MinExceededPhysConvDE”.
Table 441: T-DE-PCS-HT__15MIN (Standing Condition)

Severity

Physical Coding immediate corrective action is required.
Sub-layer disparity If the condition persists across multiple
errors detected by intervals, it may indicate an imminent
the receiver failure of a more serious nature,
exceeds the including failure of either the source or
provisioned 15- receiving plug or module or a failure in
minute threshold one of the cables along the path
value. between the source and the receiver.

correctly.
Standing Conditions
T-DGD-HT (Differ Group Delay High)

The corresponding SNMP name for this condition is “differentialGroupDelayTooHigh”.
Table 442: T-DGD-HT (Standing Condition)

Severity Cause
CH MN The differential This condition is informative and no

group delay immediate corrective action is required. If
across the the condition persists for a long duration, it
parallel lanes may indicate an imminent failure of a more
comprising of the serious nature, including failure of the
channel exceeds source or receiving plug or module, or a
the provisioned failure or signal routing error along the path
threshold value. between the source and the receiver.
circumstances, verify that the threshold
level is provisioned correctly.
Note: Should this condition immediately
precede a hard failure, check the signal
path upstream to the source and verify
that the signal routing is correct, that all
cables are of the correct type, equal
lengths for each of the lanes at a given
point along the path, that the cables are
undamaged and unrepaired, and that all
signals are routed through the same
modules at each point. Failure to ensure
that these factors are all correct may lead
to spurious replacement of the plugs or
modules at either end of the link, and
failure to resolve the underlying signal
integrity issues.
Standing Conditions
T-ES-FEC-HT__15MIN (FEC-ES 15M)

The corresponding SNMP name for this condition is “thres15MinExceededFecES”.
Table 443: T-ES-FEC-HT__15MIN (Standing Condition)

Severity Cause

errored seconds immediate corrective action is required. If
detected by the condition persists across multiple
Forward Error intervals, it may indicate an imminent
Correction failure of a more serious nature, including
exceeds the failure of either the source or receiving plug
provisioned 15 - or module or a failure in one of the cables
minute along the path between the source and the
threshold value. receiver.

T-ES-L-HT__15MIN (Line/MS-ES
15M)
The corresponding SNMP name for this condition is “thres15MinExceededSonetLineES”.
Table 444: T-ES-L-HT__15MIN (Standing Condition)

Severity Cause

line/multiplex immediate corrective action is required. If
section layer the condition persists across multiple
errored seconds intervals, it may indicate an imminent
receiver failure of either the source or receiving plug
exceeds the or module or a failure in one of the cables
provisioned 15- along the path between the source and the
minute threshold receiver.
value.
Standing Conditions
T-ES-ODU-HT__15MIN (ODU-ES 15M)

The corresponding SNMP name for this condition is “thres15MinExceededOduES”.
Table 445: T-ES-ODU-HT__15MIN (Standing Condition)

Severity Cause

measured in the the condition persists across multiple
Optical Data Unit intervals, it may indicate an imminent
(ODU) layer failure of a more serious nature, including
exceeds the failure of either the source or receiving
provisioned 15- plug or module or a failure in one of the
minute threshold cables along the path between the source
value. and the receiver.
To ensure that the condition is reported

only under the correct circumstances,
verify that the 15-minute threshold level is
T-ES-OTU-HT__15MIN (OTU-ES 15M)

The corresponding SNMP name for this condition is “thres15MinExceededOduES”.
Table 446: T-ES-OTU-HT__15MIN (Standing Condition)

Severity Cause

errored immediate corrective action is required. If
seconds the condition persists across multiple
Transport Unit either the source or receiving plug or module
(OTU) layer or a failure in one of the cables along the
provisioned 15-
minute To ensure that the condition is reported only
threshold under the correct circumstances, verify that
value. the 15-minute threshold level is provisioned
correctly.
Standing Conditions
T-ES-PCS-HT__15MIN (PCS-ES 15M)

“thres15MinExceededPhysConvES”.
Table 447: T-ES-PCS-HT__15MIN (Standing Condition)

Severity Cause

Sub-layer errored the condition persists across multiple
seconds intervals, it may indicate an imminent
15-minute cables along the path between the source
threshold value. and the receiver.

T-ES-S-HT__15MIN (Sec/RS-ES 15M)

“thres15MinExceededSonetSectES”.
Table 448: T-ES-S-HT__15MIN (Standing Condition)

Severity

section/regenerator immediate corrective action is required.
errored seconds intervals, it may indicate an imminent
detected by the failure of a more serious nature,
receiver exceeds including failure of either the source or
the provisioned 15- receiving plug or module or a failure in
minute threshold one of the cables along the path
value. between the source and the receiver.

correctly.
Standing Conditions
T-ES-TCMA-HT__15MIN (TCM_A-ES
15M)
The corresponding SNMP name for this condition is “thres15MinExceededOduTcmAES”.
Table 449: T-ES-TCMA-HT__15MIN (Standing Condition)

Severity Cause

Tandem intervals, it may indicate an imminent
Connection failure of a more serious nature, including
Monitoring failure of either the source or receiving
instance A plug or module or a failure in one of the
(TCMA) layer cables along the path between the source
exceeds the and the receiver.
provisioned 15-
T-ES-TCMB-HT__15MIN (TCM_B-ES
15M)
The corresponding SNMP name for this condition is “thres15MinExceededOduTcmBES”.
Table 450: T-ES-TCMB-HT__15MIN(Standing Condition)

Severity Cause

Monitoring failure of either the source or receiving plug
instance B or module or a failure in one of the cables
(TCMB) layer along the path between the source and the
exceeds the receiver.
provisioned 15-
threshold value. reported only under the correct
Standing Conditions
T-ES-TCMC-HT__15MIN (TCM_C-ES
15M)
The corresponding SNMP name for this condition is “thres15MinExceededOduTcmCES”.
Table 451: T-ES-TCMC-HT__15MIN (Standing Condition)

Severity Cause

Monitoring failure of either the source or receiving plug
instance C or module or a failure in one of the cables
(TCMC) layer along the path between the source and the
exceeds the receiver.
provisioned 15-
T-ESTX-PCS-HT__15MIN (PCS-ES Tx
15M)
“thres15MinExceededPhysConvESTX”.
Table 452: T-ESTX-PCS-HT__15MIN (Standing Condition)

Severity Cause

Sub-layer error the condition persists across multiple
seconds intervals, it may indicate an imminent
transmitted failure of a more serious nature, including
provisioned 15-
Standing Conditions
T-LATENCY-HT (Round Trip Delay 1

High)
The corresponding SNMP name for this condition is “latencyTooHigh”.
Table 453: T-LATENCY-HT (Standing Condition)

Severity
CH MN The latency 1 Review the provisioned threshold value and determine

measured for the whether it is appropriate to adjust the value beyond that of
facility exceeds the measured latency. If so, adjust the provisioned
the provisioned threshold value.
threshold level. 2 Review the provisioning of the facility, including the type of
mapping employed, the type of forward error correction
being applied to the facilities used to transport the affected
signal, and the type of module used to support the facility.
Compare the latency contributions of each element and
determine whether a change in the provisioning of one or
more of these elements is acceptable, and that the change
will provide a sufficient alteration in the latency of the signal
to meet the service requirements. If so, re-provision the
element(s).
3 Review the network routing of the circuit transporting the
facility proceeding hop by hop along the network route away
from the facility, and repeat the review described in the step
above, applying any relevant changes. Once the latency
has achieved a level which meets the service requirements,
the corrective action is completed.
4 Review the routing of the network facility used to transport
the signal and determine whether an alternative routing
exists which offers improved latency characteristics. If an
alternate routing is found which meets the latency
requirements, re-configure the service to use that
alternative routing.
5 If none of the above actions achieve an acceptable level of
latency performance, the service requirements of the signal
cannot be met within the constraints of the existing
network.
Standing Conditions
T-LATENCY-LT (Round Trip Delay 1

Low)
The corresponding SNMP name for this condition is “latencyTooLow”.
Table 454: T-LATENCY-LT (Standing Condition)

Severity
CH MN The latency measured 1 Review the provisioned threshold value and determine
for the facility is below whether it is appropriate to adjust the value beyond
the provisioned that of the measured latency. If so, adjust the
threshold level. provisioned threshold value.
2 Review the provisioning of the facility, including the
type of mapping employed, the type of forward error
correction being applied to the facilities used to
transport the affected signal, and the type of module
used to support the facility. Compare the latency
contributions of each element and determine whether
a change in the provisioning of one or more of these
elements is acceptable, and that the change will
provide a sufficient alteration in the latency of the
signal to meet the service requirements. If so, re-
provision the element(s).
3 Review the network routing of the circuit transporting
the facility proceeding hop by hop along the network
route away from the facility, and repeat the review
described in the step above, applying any relevant
changes. Once the latency has achieved a level
which meets the service requirements, the corrective
action is completed.
4 Review the routing of the network facility used to
transport the signal and determine whether an
alternative routing exists which offers improved
latency characteristics. If an alternate routing is found
which meets the latency requirements, re-configure
the service to use that alternative routing.
5 If none of the above actions achieve an acceptable
level of latency performance, the service
requirements of the signal cannot be met within the
constraints of the existing network.
Standing Conditions
T-LBCN-FHT (Laser Bias Current

High)
“laserBiasCurrentNormalizedtooHigh”.
Table 455: T-LBCN-FHT (Standing Condition)

Severity
CH MN The drive current This likely means that the laser is

required to obtain the aging and is approaching its end-of-
desired optical signal life point, at which time the laser
output power level from will fail resulting in a traffic
a laser associated with affecting condition for the facility.
the facility is abnormally Replace the plug or module
high given the present supporting the facility, as
operating conditions. appropriate, during the next
available scheduled maintenance
window.
T-LOTEMP-FHT (Rx Laser-Temp High)

The corresponding SNMP name for this condition is “localOscTemperatureTooHigh”.
Table 456: T-LOTEMP-FHT (Standing Condition)

Severity
CH MN The temperature 1 Verify that the equipment operating

of the laser environment for the shelf containing
providing the local the module meets specifications,
optical reference and that the air filter is clean and
signal for the unobstructed.
coherent receiver 2 Verify that there are no abnormal
for the facility is conditions or failures of the fan units
above the within the shelf containing the
specified module.
operating range.
3 Verify that the module placement
and that the surrounding equipment
conform to the product’s engineering
guidelines.
Standing Conditions
T-LOTEMP-FLT (Rx Laser-Temp Low)

The corresponding SNMP name for this condition is “localOscTemperatureTooLow”.
Table 457: T-LOTEMP-FLT (Standing Condition)

Severity
CH MN The temperature of 1 Verify that the equipment operating

the laser providing environment for the shelf containing
the local optical the module meets specifications,
reference signal for and that the air filter is clean and
the coherent unobstructed.
receiver for the 2 Verify that there are no abnormal
facility is below the conditions or failures of the fan
specified operating units within the shelf containing the
range. module.
Standing Conditions
T-LSRTEMP-FHT (Laser-Temperature
High)
The corresponding SNMP name for this condition is “laserTemperatureTooHigh”.
Table 458: T-LSRTEMP-FHT (Standing Condition)

Severity
CH MN The temperature of the 1 Verify that the equipment

laser providing the operating environment for the
transmit optical signal shelf containing the module
for the facility is above meets specifications, and that
the specified operating the air filter is clean and
range. unobstructed.
2 Verify that there are no
abnormal conditions or failures
of the fan units within the shelf
OM The temperature of one containing the module.
or more lasers providing 3 Verify that the module
optical pump power for placement and that the
the optical amplifier surrounding equipment
supporting the facility is contained within the same
above the specified shelf conform to the product’s
operating range. engineering guidelines.
Standing Conditions
T-LSRTEMP-FLT (Laser-Temperature
Low)
The corresponding SNMP name for this condition is “laserTemperatureTooLow”.
Table 459: T-LSRTEMP-FLT (Standing Condition)

Severity
CH MN The temperature of the 1 Verify that the equipment

laser providing the operating environment for the
transmit optical signal for shelf containing the module
the facility is below the meets specifications, and that
specified operating the air filter is clean and
range. unobstructed.
2 Verify that there are no
abnormal conditions or
failures of the fan units within
the shelf containing the
OM The temperature of one
module.
or more lasers providing
optical pump power for 3 Verify that the module
the optical amplifier placement and that the
supporting the facility is surrounding equipment
below the specified contained within the same
operating range. shelf conform to the product’s
Standing Conditions
T-LSRTEMP1-FHT (Laser1-
Temperature High)
The corresponding SNMP name for this condition is “pumpLaser1TempTooHigh”.
Table 460: T-LSRTEMP1-FHT (Standing Condition)

Severity
OM MN The temperature 1 Verify that the equipment operating

of the first-stage environment for the shelf containing
lasers providing the module meets specifications,
optical pump and that the air filter is clean and
power for the unobstructed.
optical amplifier 2 Verify that there are no abnormal
supporting the conditions or failures of the fan units
facility is above within the shelf containing the
the specified module.
operating range.
guidelines.
facility.
Standing Conditions
T-LSRTEMP1-FLT (Laser1-
Temperature Low)
The corresponding SNMP name for this condition is “pumpLaser1TempTooLow”.
Table 461: T-LSRTEMP1-FLT (Standing Condition)

Severity Cause

of the first-stage environment for the shelf containing
lasers providing the module meets specifications, and
optical pump that the air filter is clean and
power for the unobstructed.
optical amplifier 2 Verify that there are no abnormal
supporting the conditions or failures of the fan units
facility is below within the shelf containing the module.
the specified
operating range.
guidelines.
facility.
Standing Conditions
Temperature High)

Severity

of the second- environment for the shelf containing
stage lasers the module meets specifications,
providing optical and that the air filter is clean and
pump power for unobstructed.
the optical 2 Verify that there are no abnormal
amplifier conditions or failures of the fan units
supporting the within the shelf containing the
facility is above module.
the specified
operating range.
guidelines.
facility.
Temperature Low)

Severity Cause
OM MN The 1 Verify that the equipment operating

temperature of environment for the shelf containing the
the second- module meets specifications, and that
stage lasers the air filter is clean and unobstructed.
providing 2 Verify that there are no abnormal
optical pump conditions or failures of the fan units
power for the within the shelf containing the module.
optical amplifier
supporting the
facility is below
the specified
operating range.
guidelines.
facility.
Standing Conditions
Temperature High)

Severity

of the third environment for the shelf containing
instance or set of the module meets specifications, and
lasers providing that the air filter is clean and
optical pump unobstructed.
power for the 2 Verify that there are no abnormal
optical amplifier conditions or failures of the fan units
the specified
operating range.
guidelines.
facility.
Standing Conditions
Temperature Low)

Severity Cause
OM MN The 1 Verify that the equipment operating

temperature of environment for the shelf containing
the third the module meets specifications, and
instance or set that the air filter is clean and
of lasers unobstructed.
providing optical 2 Verify that there are no abnormal
pump power for conditions or failures of the fan units
the optical within the shelf containing the module.
amplifier
supporting the
facility is below
the specified
operating range.
guidelines.
facility.
Standing Conditions
Temperature High)

Severity

of the fourth environment for the shelf containing
instance or set of the module meets specifications, and
lasers providing that the air filter is clean and
optical pump unobstructed.
power for the 2 Verify that there are no abnormal
optical amplifier conditions or failures of the fan units
the specified
operating range.
guidelines.
facility.
Standing Conditions
Temperature Low)

Severity Cause

of the fourth environment for the shelf containing
instance or set the module meets specifications, and
of lasers that the air filter is clean and
providing optical unobstructed.
pump power for 2 Verify that there are no abnormal
the optical conditions or failures of the fan units
amplifier within the shelf containing the module.
supporting the
facility is below
the specified
operating range.
guidelines.
facility.
Standing Conditions
T-OPR-HT (Optical Power Rx High)

The corresponding SNMP name for this condition is “opticalInputPwrReceivedTooHigh”.
Table 468: T-OPR-HT (Standing Condition)

Severity Cause
CH MN The optical input 1 Verify that the threshold level is

power level provisioned correctly.
detected by the 2 Verify that the incoming cable carrying
receiver the facility is the correct cable and that
exceeds the the transmit and receive ports are
ETH provisioned connected to their proper respective
threshold level.1 portions of the cable (i.e. that the
fibers are not swapped between
conforms to the maximum power level
specifications. If the signal meets the
OM The composite and repair the problem. It may be
optical signal necessary to pad the optical line using
power level at a fixed or variable attenuator to bring
the input of the the attenuation within the specified
optical amplifier minimum range required by the
module exceeds system.
the provisioned 4 Replace the plug or module supporting
threshold level. the facility.
1If the condition is raised at the client ports of MP-2B4CT modules, this means that the
received optical input power level for the optical lane exceeds the provisioned threshold.
Standing Conditions
T-OPR-LT (Optical Power Rx Low)

The corresponding SNMP name for this condition is “opticalInputPwrReceivedTooLow”.
Table 469: T-OPR-LT (Standing Condition)

Severity Cause
CH MN The optical input 1 Verify that the threshold level is

power level provisioned correctly.
detected by the 2 Verify that the incoming cable carrying
receiver is the facility is the correct cable and that
below the the transmit and receive ports are
provisioned connected to their proper respective
ETH
threshold level.1 portions of the cable (i.e. that the fibers
are not swapped between transmit and
receive).
cable is firmly connected to the
facility and that the connector is not
physically impaired by obstructions,
module, as appropriate, depending
OM The composite physical examination.
optical signal
power level at
the input of the
conforms to the required minimum
optical amplifier
power level. If the signal meets the
module is below
the provisioned
threshold level.
the facility.
received optical input power level for the optical lane is less than the provisioned
threshold.
Standing Conditions
T-OPT-FHT (Optical Power Tx-High)

“opticalOutputPowerTransmittedTooHigh”.
Table 470: T-OPT-FHT (Standing Condition)

Severity
CH MN The optical launch This condition typically results from a

power of the laser failure of the laser drive circuitry.
ETH on the transmit port
of the facility Replace the plug or module supporting
exceeds the the facility.
specified maximum
launch power.
OM The composite This condition may result from either a

optical power failure of the pump laser drive and
exiting the optical control circuitry of the optical amplifier
amplifier module module or from an excessive optical
exceeds the input power on the input port of the
specified maximum amplifier stage providing the output
output power level. signal.
Verify that the input power level is
within the specified system limits (see
T-OPR-HT (Optical Power Rx High) for
the relevant procedure). If the input
signal is within the specified operating
range of the amplifier module, replace
the amplifier module.
Standing Conditions
T-OPT-FLT (Optical Power Tx Low)

“opticalOutputPowerTransmittedTooLow”.
Table 471: T-OPT-FLT (Standing Condition)

Severity
CH MN The optical launch This condition typically results from a

power of the laser failure of the laser drive circuitry or a
ETH on the transmit port failure of the laser device itself.
of the facility is
below the specified Replace the plug or module supporting
minimum launch the facility.
power.
OM The composite This condition may result from either a

optical power failure of the pump laser drive and
exiting the optical control circuitry of the optical amplifier
amplifier module is module, a failure of the pump laser
below the specified device(s), or from an optical input
minimum output power which is below the minimum
power level. specified operating level at the input of
the amplifier stage providing the output
signal.
T-OPR-LT (Optical Power Rx Low) for
the relevant procedure). If the input
range of the amplifier module, replace
the amplifier module.
Standing Conditions
T-OPT-HT (Optical Power Tx High)

“configurableOpticalOutputPowerTransmittedTooHigh”.
Table 472: T-OPT-HT (Standing Condition)

Severity
OCH MN The composite This condition may result from either

optical power exiting an excessive optical input power on
the port exceeds the the input port or a local failure of the
specified maximum attenuator or its control circuitry.
output power level.1 Verify that the input power level is
T-OPR-HT (Optical Power Rx High)
for the relevant procedure). If the input
range, replace the attenuator module.
OM 1 Verify that the optical pump power

applied to the network span by the
Raman amplifier is within the
engineered limits for that span.
Adjust the power settings as
needed to bring the power level
2 Verify that the optical signal from
the preceding module in the span
falls within the engineered limits.
3 Examine the network span and
correct all factors causing
excessive loss, such as bent or
damaged fibers, optical
attenuators with values higher
than appropriate which are placed
in-line, or loose or damaged optical
connectors.
transmitted optical input power level for the optical lane exceeds the provisioned
threshold.
Standing Conditions
T-OPT-LT (Optical Power Tx Low)

“configurableOpticalOutputPowerTransmittedTooLow”.
Table 473: T-OPT-LT (Standing Condition)

Severity
OCH MN The composite This condition may result from either

optical power exiting an optical input power which is below
the port is below the the minimum specified operating level
specified minimum or a local failure of the attenuator or its
output power level.1 control circuitry.
within the specified system limits
(see T-OPT-LT (Optical Power Tx
Low) for the relevant procedure). If the
input signal is within the specified
operating range, replace the
attenuator module.
OM 1 Verify that the optical pump

power applied to the network
span by the Raman amplifier is
within the engineered limits for
that span. Adjust the power
settings as needed to bring the
power level within the specified
limits.
2 Verify that the optical signal from
the preceding module in the span
falls within the engineered limits.
transmitted optical input power level for the optical lane is less than the provisioned
threshold.
Standing Conditions
T-OSCPWR-HT (OSC Power High)

The corresponding SNMP name for this condition is “oscPwrTooHigh”.
Table 474: T-OSCPWR-HT (Standing Condition)

Severity
OM MJ The power level of the 1 Verify that the threshold level is

OSC signal received provisioned correctly.
on the network port 2 Verify that the incoming cable
exceeds the specified carrying the facility is the correct
maximum threshold. cable and that the transmit and
receive ports are connected to
their proper respective portions
of the cable (i.e. that the fibers
are not swapped between
signal conforms to the maximum
power level specifications. If the
specifications proceed to the
next step below, otherwise
problem. It may be necessary to
pad the optical line using a fixed
or variable attenuator to bring the
attenuation within the specified
minimum range required by the
system.
the facility.
Standing Conditions
T-OSCPWR-LT (OSC Power Low)

The corresponding SNMP name for this condition is “oscPwrTooLow”.
Table 475: T-OSCPWR-LT (Standing Condition)

Severity
OM MJ The power level of 1 Verify that the threshold level is

the OSC signal provisioned correctly.
received on the 2 Verify that the incoming cable
network port is below carrying the facility is the correct
the specified cable and that the transmit and
minimum threshold. receive ports are connected to
their proper respective portions
of the cable (i.e. that the fibers
are not swapped between
signal conforms to the minimum
power level specifications. If the
signal is below the required level
problem. Upstream problems
may include failure of the module
providing the OSC signal, failure
or excessive loss of fibers within
the transmission space, or dirty
or damaged optical connectors
within the span.
the facility.
Standing Conditions
T-PUMPWR-FHT (Pump Power High)

The corresponding SNMP name for this condition is “ramanPumpPwrTooHigh”.
Table 476: T-PUMPWR-FHT (Standing Condition)

Severity
OM MN The power level of 1 Verify that the module and facility are
the optical pump provisioned correctly and that the
signal exceeds PUMPWR-CTRL attribute of the
the maximum facility is set to the correct value for
threshold. the transmission span.
carrying the facility is the correct
cable and that the transmit and
proper respective portions of the
receive).
3 Perform the ASE table build process
on the amplifier module (e.g. the
OPR-ASETBL-OM command in
TL1).
conforms to the input power level
specifications. If the signal meets
problem. The upstream problem may
be the result of excessive span
length, excessive span loss or
inadequate launch power from the
far-end.
facility.
Standing Conditions
T-PUMPWR-FLT (Pump Power Low)

The corresponding SNMP name for this condition is “ramanPumpPwrTooLow”.
Table 477: T-PUMPWR-FLT (Standing Condition)

Severity
OM MN The power level of 1 Verify that the module and facility

the optical pump are provisioned correctly and that
signal is below the the PUMPWR-CTRL attribute of the
minimum facility is set to the correct value for
threshold. the transmission span.
carrying the facility is the correct
cable and that the transmit and
proper respective portions of the
receive).
3 Perform the ASE table build process
on the amplifier module (e.g. the
OPR-ASETBL-OM command in
TL1).
conforms to the input power level
specifications. If the signal meets
problem. The upstream problem may
be an overly short span length or
excessive launch power from the
far-end.
5 The condition may signal that the
one or more of the optical pumps
within the module supporting the
facility are approaching their end of
life. Plan for a scheduled
replacement of the module during an
approaching maintenance window to
minimize the risk of service impact.
Standing Conditions
T-PWRUSED-FHT (Power
Consumption High)
The corresponding SNMP name for this condition is “powerConsumptionHigh”.
Table 478: T-PWRUSED-FHT (Standing Condition)

Severity Action
MOD MN The module is failing. Replace the module.
T-PWROUT-FHT (Output Power High)

The corresponding SNMP name for this condition is “outputPowerHigh”.
Table 479: T-PWROUT-FHT (Standing Condition)

Severity Action
MOD MN A power unit has failed. 1 Replace the failed power

The installed equipment unit.
requires more power than 2 Remove the last installed
can be provided by the module.
power units.
Standing Conditions
T-RNDTRPDLY-HT (Round Trip Delay

High)
The corresponding SNMP name for this condition is “roundTripDelayTooHigh”.
Table 480: T-RNDTRPDLY-HT (Standing Condition)

Severity
CH MN The round trip 1 Review the provisioned threshold value and determine
delay measured for whether it is appropriate to adjust the value beyond that of
the facility the measured latency. If so, adjust the provisioned
exceeds the threshold value.
provisioned 2 Review the provisioning of the facility, including the type of
threshold level. mapping employed, the type of forward error correction
being applied to the facilities used to transport the affected
signal, and the type of module used to support the facility.
Compare the latency contributions of each element and
determine whether a change in the provisioning of one or
more of these elements is acceptable, and that the change
will provide a sufficient alteration in the latency of the signal
to meet the service requirements. If so, re-provision the
element(s).
3 Review the network routing of the circuit transporting the
facility proceeding hop by hop along the network route away
from the facility, and repeat the review described in the step
above, applying any relevant changes. Once the latency
has achieved a level which meets the service requirements,
the corrective action is completed.
4 Review the routing of the network facility used to transport
the signal and determine whether an alternative routing
exists which offers improved latency characteristics. If an
alternate routing is found which meets the latency
requirements, re-configure the service to use that alternative
routing.
5 If none of the above actions achieve an acceptable level of
latency performance, the service requirements of the signal
cannot be met within the constraints of the existing network.
Standing Conditions
T-RNDTRPDLY-LT (Round Trip Delay

Low)
The corresponding SNMP name for this condition is “roundTripDelayTooLow”.
Table 481: T-RNDTRPDLY-LT (Standing Condition)

Severity
CH MN The round trip delay 1 Review the provisioned threshold value and determine
measured for the facility whether it is appropriate to adjust the value beyond
is below the provisioned that of the measured latency. If so, adjust the
threshold level. provisioned threshold value.
2 Review the provisioning of the facility, including the
type of mapping employed, the type of forward error
correction being applied to the facilities used to
transport the affected signal, and the type of module
used to support the facility. Compare the latency
contributions of each element and determine whether
a change in the provisioning of one or more of these
elements is acceptable, and that the change will
provide a sufficient alteration in the latency of the
signal to meet the service requirements. If so, re-
provision the element(s).
3 Review the network routing of the circuit transporting
the facility proceeding hop by hop along the network
route away from the facility, and repeat the review
described in the step above, applying any relevant
changes. Once the latency has achieved a level which
meets the service requirements, the corrective action
is completed.
4 Review the routing of the network facility used to
transport the signal and determine whether an
alternative routing exists which offers improved
latency characteristics. If an alternate routing is found
which meets the latency requirements, re-configure
the service to use that alternative routing.
5 If none of the above actions achieve an acceptable
level of latency performance, the service requirements
of the signal cannot be met within the constraints of
the existing network.
Standing Conditions
T-SEFS-S-HT__15MIN (Sec/RS-SEFS
15M)
“thres15MinExceededSonetSectSEFS”.
Table 482: T-SEFS-S-HT__15MIN (Standing Condition)

Severity

severely errored intervals, it may indicate an imminent
frame seconds failure of a more serious nature,
detected by the including failure of either the source or
receiver exceeds receiving plug or module or a failure in
the provisioned 15- one of the cables along the path
minute threshold between the source and the receiver.
value.
correctly.
T-SES-FEC-HT__15MIN (FEC-SES
15M)
The corresponding SNMP name for this condition is “thres15MinExceededFecSES”.
Table 483: T-SES-FEC-HT__15MIN (Standing Condition)

Severity Cause

severely errored immediate corrective action is required. If
detected by intervals, it may indicate an imminent
Forward Error failure of a more serious nature, including
Correction failure of either the source or receiving plug
minute threshold receiver.
value.
Standing Conditions
T-SES-L-HT__15MIN (Line/MS-SES
15M)
“thres15MinExceededSonetLineSES”.
Table 484: T-SES-L-HT__15MIN (Standing Condition)

Severity Cause

line/multiplex immediate corrective action is required. If
section layer the condition persists across multiple
seconds failure of a more serious nature, including
detected by the failure of either the source or receiving
receiver exceeds plug or module or a failure in one of the
the provisioned cables along the path between the source
15-minute and the receiver.
threshold value.
T-SES-ODU-HT__15MIN (ODU-SES
15M)
The corresponding SNMP name for this condition is “thres15MinExceededOduSES”.
Table 485: T-SES-ODU-HT__15MIN (Standing Condition)

Severity Cause

Optical Data failure of a more serious nature, including
Unit (ODU) failure of either the source or receiving plug
layer exceeds or module or a failure in one of the cables
the provisioned along the path between the source and the
15-minute receiver.
threshold value.
Standing Conditions
T-SES-OTU-HT__15MIN (OTU-SES
15M)
The corresponding SNMP name for this condition is “thres15MinExceededOtuSES”.
Table 486: T-SES-OTU-HT__15MIN (Standing Condition)

Severity

severely errored immediate corrective action is required.
seconds measured If the condition persists across multiple
in the Optical intervals, it may indicate an imminent
Transport Unit failure of a more serious nature,
(OTU) layer including failure of either the source or
exceeds the receiving plug or module or a failure in
provisioned 15- one of the cables along the path
value.
verify that the 15-minute threshold level
T-SES-S-HT__15MIN (Sec/RS-SES
15M)
“thres15MinExceededSonetSectSES”.
Table 487: T-SES-S-HT__15MIN (Standing Condition)

Severity

seconds detected failure of a more serious nature,
by the receiver including failure of either the source or
value.
correctly.
Standing Conditions
T-SES-TCMA-HT__15MIN (TCM_A-
SES 15M)
“thres15MinExceededOduTcmASES”.
Table 488: T-SES-TCMA-HT__15MIN (Standing Condition)

Severity

in the Tandem intervals, it may indicate an imminent
Connection failure of a more serious nature,
Monitoring instance including failure of either the source or
A (TCMA) layer receiving plug or module or a failure in
exceeds the one of the cables along the path
provisioned 15- between the source and the receiver.
minute threshold
correctly.
T-SES-TCMB-HT__15MIN (TCM_B-
SES 15M)
“thres15MinExceededOduTcmBSES”.
Table 489: T-SES-TCMB-HT__15MIN (Standing Condition)

Severity Cause

instance B cables along the path between the source
(TCMB) layer and the receiver.
exceeds the
Standing Conditions
T-SES-TCMC-HT__15MIN (TCM_C-SES
15M)
“thres15MinExceededOduTcmCSES”.
Table 490: T-SES-TCMC-HT__15MIN (Standing Condition)

Severity

Monitoring including failure of either the source or
instance C receiving plug or module or a failure in
(TCMC) layer one of the cables along the path
exceeds the between the source and the receiver.
provisioned 15-
correctly.
T-SETX-PCS-HT__15MIN (PCS-Sync
Header Tx 15M)
“thres15MinExceededPhysConvSETX”.
Table 491: T-SETX-PCS-HT__15MIN (Standing Condition)

Severity Cause

transmitted at intervals, it may indicate an imminent
the PCS layer failure of a more serious nature, including
provisioned 15-
threshold value. reported only under the correct
Standing Conditions
T-SKEW-HT (Alignment Delta High)

The corresponding SNMP name for this condition is “logicalLanesSkewTooHigh”.
Table 492: T-SKEW-HT (Standing Condition)

Severity
CH MN The timing skew Review the provisioning of the optical

between the signals facility and its end-to-end path and
in lanes of the multi- ensure that all optical lanes are routed
lane facility exceeds along the same path, and that each
the allowed span conforms to the optical signal
tolerance of the engineering specifications of the path.
receiver. Correct any provisioning or connection
errors.
Standing Conditions
T-SNR-LT (Signal Noise Ratio Low)

The corresponding SNMP name for this condition is “signalToNoiseRatioTooLow”.
Table 493: T-SNR-LT (Standing Condition)

Severity
CH MN The measured signal-to- 1 Verify that the SNR threshold level is provisioned
noise ratio of the correctly.
received signal is below 2 Review the provisioned type of forward error
the provisioned correction used by the facility and ensure that it is
minimum acceptable consistent with the signals path engineering rules.
threshold level.
meets the required specifications replace the module
5 Verify that the upstream signal path follows the
intended routing and that each module along the path
conforms to the engineering specifications of the
supported spans and that they are operating without
error or with abnormal performance levels (i.e. without
any active TCAs). Correct any items (e.g. adjust
provisioning value or replace faulty equipment) which
are operating outside their intended limits. If there are
no upstream elements operating outside of their
engineered specifications, the engineering of one or
more of the spans or of the end-to-end signal path
violates the path requirements and an alternate routing
of the path must be found which conforms to the path
requirements.
Standing Conditions
T-SUBTEMP-FHT (Temperature 2
High)
The corresponding SNMP name for this condition is “subModuleTempTooHigh”.
Table 494: T-SUBTEMP-FHT (Standing Condition)

Severity Cause
MOD MN The ambient 1 Verify that the equipment

temperature operating environment for the
surrounding the shelf containing the module
optical amplifier meets specifications, and that the
sub-assembly air filter is clean and
has exceeded unobstructed.
the normal 2 Verify that there are no abnormal
operating range. conditions or failures of the fan
units within the shelf containing
the module.
and the surrounding equipment
4 Replace the concerned module.
T-TEMP-FHT (Temperature High)

The corresponding SNMP name for this condition is “temperatureTooHigh”.
Table 495: T-TEMP-FHT (Standing Condition)

Severity Cause
PL MN The ambient 1 Verify that the equipment operating

temperature environment for the shelf containing the
surrounding the plug meets specifications, and that the
plug is above air filter is clean and unobstructed.
the maximum 2 Verify that there are no abnormal
specified conditions or failures of the fan units
operating within the shelf containing the plug.
range.
3 Verify that the module containing the
plug is provisioned and operating
correctly.
4 Replace the plug.
Standing Conditions
T-TEMP-FLT (Temperature Low)

The corresponding SNMP name for this condition is “temperatureTooLow”.
Table 496: T-TEMP-FLT (Standing Condition)

Severity Cause
PL MN The ambient 1 Verify that the equipment operating

temperature environment for the shelf containing the
surrounding the plug meets specifications, and that the
plug is below air filter is clean and unobstructed.
the minimum 2 Verify that there are no abnormal
specified conditions or failures of the fan units
operating within the shelf containing the plug.
range.
3 Verify that the module containing the
plug is provisioned and operating
correctly.
4 Replace the plug.
T-UAS-L-HT__15MIN (Line/MS-UAS
15M)
“thres15MinExceededSonetLineUAS”.
Table 497: T-UAS-L-HT__15MIN (Standing Condition)

Severity

line/multiplex immediate corrective action is
section layer required. If the condition persists
unavailable seconds across multiple intervals, it may
detected by the indicate an imminent failure of a more
receiver exceeds serious nature, including failure of
the provisioned 15- either the source or receiving plug or
minute threshold module or a failure in one of the cables
value. along the path between the source and
the receiver.

verify that the 15-minute threshold
level is provisioned correctly.
Standing Conditions
T-UAS-ODU-HT__15MIN (ODU-UAS
15M)
The corresponding SNMP name for this condition is “thres15MinExceededOduUAS”.
Table 498: T-UAS-ODU-HT__15MIN (Standing Condition)

Severity Cause

unavailable immediate corrective action is required. If
Optical Data failure of a more serious nature, including
Unit (ODU) failure of either the source or receiving plug
layer exceeds or module or a failure in one of the cables
the provisioned along the path between the source and the
15-minute receiver.
threshold value.
T-UAS-OTU-HT__15MIN (OTU-UAS
15M)
The corresponding SNMP name for this condition is “thres15MinExceededOtuUAS”.
Table 499: T-UAS-OTU-HT__15MIN (Standing Condition)

Severity

unavailable immediate corrective action is required.
in the Optical intervals, it may indicate an imminent
Transport Unit failure of a more serious nature,
(OTU) layer including failure of either the source or
value.
verify that the 15-minute threshold level
Standing Conditions
T-UAS-TCMA-HT__15MIN (TCM_A-
UAS 15M)
“thres15MinExceededOduTcmAUAS”.
Table 500: T-UAS-TCMA-HT__15MIN (Standing Condition)

Severity

instance A (TCMA) receiving plug or module or a failure in
layer exceeds the one of the cables along the path
minute threshold
correctly.
T-UAS-TCMB-HT__15MIN (TCM_B-
UAS 15M)
“thres15MinExceededOduTcmBUAS”.
Table 501: T-UAS-TCMB-HT__15MIN (Standing Condition)

Severity

instance B (TCMB) receiving plug or module or a failure in
layer exceeds the one of the cables along the path
minute threshold
correctly.
Standing Conditions
T-UAS-TCMC-HT__15MIN (TCM_C-
UAS 15M)
“thres15MinExceededOduTcmCUAS”.
Table 502: T-UAS-TCMC-HT__15MIN (Standing Condition)

Severity Cause

unavailable immediate corrective action is required. If
instance C cables along the path between the source
(TCMC) layer and the receiver.
exceeds the
T-UBE-FEC-HT__15MIN (FEC-UBE
15M)
The corresponding SNMP name for this condition is “thres15MinExceededFecUBE”.
Table 503: T-UBE-FEC-HT__15MIN (Standing Condition)

Severity Cause

uncorrectable immediate corrective action is required. If
detected by intervals, it may indicate an imminent
Forward Error failure of a more serious nature, including
Correction failure of either the source or receiving plug
minute receiver.
threshold value.
Standing Conditions
TAG-FAIL (Tag Errors High)

The corresponding SNMP name for this condition is “tagReceiveFailMaxReached.”
Table 504: TAG-FAIL (Standing Condition)

Severity
CH1 CR A tag error occurs when 1 Check the module for any
the received active or passive attacks.
authentication tag does 2 Once any security breach is
not match the resolved, reset the Tag Errors
calculated value. The counter to enable data traffic
TAG-FAIL condition is again.
raised when the tag
error limit is reached.
Consequently, traffic is
interrupted until the Tag
Errors counter is reset.
TAGLFT-DEG (Tag Error)

The corresponding SNMP name for this condition is “tagReceiveFail.”
Table 505: TAGLFT-DEG (Standing Condition)

Severity
CH1 MJ The received 1 Check the module for any active or

authentication tag passive attacks.
does not match the 2 Once any security breach is
calculated value. resolved, the Crypto Officer may
reset the Tag Errors counter, or
allow it to clear automatically when
the line is error-free.
1In 10TCE-PCN-16GU+AES100G-BSI modules only.
Standing Conditions
TAMPER (Encryption-Tamper)
The corresponding SNMP name for this condition is “encryptionModuleTamperDetected”.
Table 506: TAMPER (Standing Condition)

Severity Cause
MOD CR The equipment 1 Determine the nature of the tampering

has determined activity. If the activity is known to be
that an attempt the result of an action which poses no
was made to risk of compromising the
breach the cryptographic integrity of the
physical security equipment (e.g. reseating the module
measures within a shelf), the module may be
protecting the reset to factory defaults, re-
cryptographic commissioned and returned to
components. service.
2 If the nature of the tampering activity
is determined to have compromised
the cryptographic integrity of the
equipment, or if the nature of the
tampering activity cannot be
determined, the equipment should be
replaced with one known to be free of
tampering, and the existing equipment
should be returned for repair.
TECEOL (TEC-End of Life)

The corresponding SNMP name for this condition is “thermoElectricCoolerEndOfLife”.
Table 507: TECEOL (Standing Condition)

Severity Action
OM MN The optical amplifier module has Replace the module

detected that one or more of the supporting the facility.
pump laser thermo-electric coolers
within the module have reached
their end-of-life point.
Standing Conditions
TIFALM (Telemetry Interface)

Telemetry interface environmental conditions are unusual in that the condition name and
description are user provisioned. Some common examples of values which may be
provisioned are shown below.
The corresponding SNMP name for this condition is “alarmInputTIF”.
Table 508: Example Environmental Alarms
<tifalmtype> Meaning
AIRCOMPR Air compressor failure.
AIRCOND Air conditioning failure.
AIRDRYR Air dryer failure.
BATDSCHRG Battery discharging.
BATTERY Battery failure.
CLFAN Cooling fan failure.
CPMAJOR Centralized Power Major Environmental Alarm or Major

Equipment Failure
CPMINOR Centralized Power Minor Environmental Alarm or Minor

Equipment Failure
ENGINE Engine failure.
ENGOPRG Engine operating.
EXPLGS Explosive gas.
FIRDETR Fire detector failure.
FIRE Fire.
FLOOD Flood.
FUSE Fuse failure.
GEN Generator failure.
HIAIR High airflow.
HIHUM High humidity.
HITEMP High temperature.
HIWTR High water.
INTRUDER Intrusion detection.
LWBATVG Low battery voltage.
LWFUEL Low fuel.
Standing Conditions
LWHUM Low humidity.
LWPRES Low cable pressure.
LWTEMP Low temperature.
LWWTR Low water.
MISC Miscellaneous.
OPENDR Enclosure door open.
POWER Commercial power failure.
PWR-x <x> Volt power supply failure.
PUMP Pump failure.
RECT Rectifier failure.
RECTHI Rectifier high voltage.
RECTLO Rectifier low voltage.
SMOKE Smoke.
TOXICGAS Toxic gas.
VENTN Ventilation system failure.
AIRCOMPR Air compressor failure.
AIRCOND Air conditioning failure.
AIRDRYR Air dryer failure.
BATDSCHRG Battery discharging.
BATTERY Battery failure.
CLFAN Cooling fan failure.
CPMAJOR Centralized Power Major Environmental Alarm or Major

Equipment Failure
CPMINOR Centralized Power Minor Environmental Alarm or Minor

Equipment Failure
ENGINE Engine failure.
ENGOPRG Engine operating.
EXPLGS Explosive gas.
Standing Conditions
FIRDETR Fire detector failure.
FIRE Fire.
FLOOD Flood.
FUSE Fuse failure.
GEN Generator failure.
HIAIR High airflow.
HIHUM High humidity.
HITEMP High temperature.
HIWTR High water.
INTRUDER Intrusion detection.
LWBATVG Low battery voltage.
LWFUEL Low fuel.
LWHUM Low humidity.
LWPRES Low cable pressure.
LWTEMP Low temperature.
LWWTR Low water.
MISC Miscellaneous.
OPENDR Enclosure door open.
POWER Commercial power failure.
PWR-x <x> Volt power supply failure.
PUMP Pump failure.
RECT Rectifier failure.
RECTHI Rectifier high voltage.
RECTLO Rectifier low voltage.
SMOKE Smoke.
TOXICGAS Toxic gas.
VENTN Ventilation system failure.
Standing Conditions
Table 510: TIFALM (Standing Condition)

Severity
TIFI MJ The input contact with This condition reports a change

which the condition is in state of a contact connected
associated has changed to equipment external to the
to the active state. Network Element. The
appropriate corrective action, if
any, must be determined from
the reported condition
description and associated
practices defined by the operator
of the equipment. This condition
may be informative, in which
case no further action would be
required.
TIFO The output contact the This condition reports a change

condition is associated in state of a contact connected
with has changed to the to equipment external to the
active state. Network Element. The
appropriate corrective action, if
any, must be determined from
the reported condition
description and associated
practices defined by the operator
of the equipment. This condition
may be informative, in which
case no further action would be
required.
UTM, NR, NA
UTM-S,
CEM9HU
Standing Conditions
TIM-ODU (ODU-TIM)
The corresponding SNMP name for this condition is “traceIdentifierMismatchOdu”.
Table 511: TIM-ODU (Standing Condition)

Severity Cause
CH MN The ODU layer 1 Verify that the expected trace value

trace value at the near-end and the transmitted
received differs trace value at the expected far-end
from the ODU path termination point are the
provisioned same. If they are not, correct the
value which values so that they have the same
was expected. value.
2 Verify that the signal carrying the
trace data does not have an
abnormally high bit error rate. If it
does, troubleshoot the bit error rate
cause first.
3 Beginning with the node containing
the facility reporting the condition,
verify that all provisioned cross
connections and cable routings
upstream along the path traversed
by the facility reporting the condition
are correctly provisioned or
connected. Correct any cross
connection or cable connection
facility at the near-end.
far-end ODU path terminating
facility.
Standing Conditions
TIM-OTU (OTU-TIM)
The corresponding SNMP name for this condition is “traceIdentifierMismatchOtu”.
Table 512: TIM-OTU (Standing Condition)

Severity
CH MN The OTU layer 1 Verify that the expected trace value

trace value at the near-end and the transmitted
received differs trace value at the expected far-end
from the OTU termination point are the same.
provisioned value If they are not, correct the values so
which was that they have the same value.
expected. 2 Verify that the signal carrying the
does, troubleshoot the bit error rate
cause first.
3 Beginning with the node containing
the facility reporting the condition,
verify that all provisioned cross
connections and cable routings
upstream along the path traversed
by the facility reporting the condition
facility at the near-end.
far-end OTU terminating facility.
Standing Conditions
TIM-S (Sec/RS-TIM)
The corresponding SNMP name for this condition is “sectionTraceMismatch”.
Table 513: TIM-S (Standing Condition)

Severity
CH MN The SONET 1 Verify that the expected trace

Section/SDH value at the near-end and the
Regenerator transmitted trace value at the
Section layer expected far-end facility are the
received trace same. If they are not, correct the
value differs from values so that they have the same
that provisioned as value.
the expected 2 Verify that the signal carrying the
value. trace data does not have an
does, troubleshoot the bit error
rate cause first.
3 Beginning with the node
containing the facility reporting the
condition, verify that all
provisioned cross connections
and cable routings upstream along
the path traversed by the facility
reporting the condition are
correctly provisioned or
the facility at the near-end.
the facility at the far-end.
Standing Conditions
TIM-TCMA (TCM_A-TIM)
The corresponding SNMP name for this condition is “traceIdentifierMismatchOduTcmA”.
Table 514: TIM-TCMA (Standing Condition)

Severity
CH MN The TCM layer 1 Verify that the expected trace

assigned as instance value at the near-end and the
A has received a transmitted trace value at the
trace value which expected far-end facility
differs from that terminating the same TCM layer
provisioned as the are the same. If they are not,
expected value. correct the values so that they
have the same value.
rate cause first.
containing the facility reporting
the condition, verify that all
and cable routings upstream
along the path traversed by the
facility reporting the condition are
the facility terminating the same
TCM layer at the far-end.
Standing Conditions
TIM-TCMB (TCM_B-TIM)
The corresponding SNMP name for this condition is “traceIdentifierMismatchOduTcmB”.
Table 515: TIM-TCMB (Standing Condition)

Severity

B has received a transmitted trace value at the
rate cause first.
facility reporting the condition are
Standing Conditions
TIM-TCMC (TCM_C-TIM)
The corresponding SNMP name for this condition is “traceIdentifierMismatchOduTcmC”.
Table 516: TIM-TCMC (Standing Condition)

Severity

C has received a transmitted trace value at the
2 Verify that the signal carrying
the trace data does not have an
abnormally high bit error rate. If
it does, troubleshoot the bit error
rate cause first.
facility reporting the condition
Standing Conditions
TNL-ANR (Tunnel Abnormal)

The corresponding SNMP name for this condition is “tunnelAbnormal”.
Table 517: TNL-ANR (Standing Condition)

Severity Action
WDM Tunnel NA An abnormality exists in This condition is

the tunnel but service is informative. Corrective
not affected. The tunnel is action will be taken in
able to perform its response to specific errors
provisioned functions at a reported on the tunnel.
degraded level.
TURNUP (Initialization)
The corresponding SNMP name for this condition is “turnupCondition”.
Table 518: TURNUP (Standing Condition)

Severity
CH NA The reporting facility is No action is required. The condition

undergoing the will clear automatically once the
process needed to adjustment process completes.
determine the
necessary span
related adjustments.
Standing Conditions
TURNUP-FAIL (Initialization Fail)

The corresponding SNMP name for this condition is “turnupFailed”.
Table 519: TURNUP-FAIL (Standing Condition)

Severity
CH MJ An attempt was made to 1 Verify that the facility is provisioned correctly.

configure span related 2 Verify that the incoming cable is the correct cable
compensation settings of and that the transmit and receive ports are
the facility but the connected to their proper respective portions of the
necessary settings could cable (i.e. that the fibers are not swapped between
not be attained. transmit and receive).
3 Verify that the incoming fiber cable is firmly
impaired by obstructions, dirt or component
damage. Clean the connector or replace the cable,
plug or module, as appropriate, depending upon the
cause determined from the physical examination.
maximum power levels) and that the eye opening is
within specified limits. If the signal meets the
5 Proceeding upstream, examine each segment of
the fiber pathway to determine whether there are
dispersion compensating devices (e.g. fibers or
gratings) employed within the optical signal path.
Typical locations of such elements include the mid-
stage of dual-stage optical amplifiers or near the
end of a transmission fiber span. Verify that each
element along the path meets the compensation
requirements of the path’s optical design budget.
Replace any element which does not conform to
the engineering budget.
Standing Conditions
UNEQ-LP (Path LO-Unequipped)

The corresponding SNMP name for this condition is “unequippedLowerOrderPath”.
Table 520: UNEQ-LP (Standing Condition)

VC3 CR The received path signal carries the Provision the path and
un-equipped code in the signal label its associated client
byte. signal mapping at the
This typically means that the far-end intended far-end
path termination point has not been assignment point, or
assigned to carry a payload (i.e. that delete the unused
it is not cross-connected to a signal facility at the near-
source or that no signal is mapped end, as appropriate.
into the path).
UNEQ-P (Path-Unequipped)
The corresponding SNMP name for this condition is “unequippedHigherOrderPath”.
Table 521: UNEQ-P (Standing Condition)

STS1, STS3C, CR The received path signal Provision the path and
STS24C, carries the un-equipped code its associated client
STS48C in the signal label byte. signal mapping at the
This typically means that the intended far-end
far-end path termination point assignment point, or
has not been assigned to carry delete the unused
VC4, VC4C8, a payload (i.e. that it is not facility at the near-
VC4C16 cross-connected to a signal end, as appropriate.
source or that no signal is
mapped into the path).
Standing Conditions
VOACTRL_FAIL (Attenuator-Control
Fail)
The corresponding SNMP name for this condition is “voaControlFail”.
Table 522: VOACTRL_FAIL (Standing Condition)

Severity
CH MJ The optical power 1 Verify that the incoming cable is the

on the output port correct cable and that the receive
of the attenuator port is properly connected to the
module is unable intended source.
to be controlled. 2 Verify that the attenuator
provisioning settings are correct and
adjust them as necessary.
3 Verify that the optical signal received
is within the specified operating
limits.
VOLTANR (Voltage Out of Range)

The corresponding SNMP name for this condition is “voltageOutOfRange”.
Table 523: VOLTANR (Standing Condition)

Severity Cause
MOD MN At least one of 1 Verify that the main supply

the internal feeding the associated power
power supplies supply units is operating within
(derived from the specifications.
incoming shelf 2 Verify that the power supply
power) does not modules have not failed, and that
work within the the shelf is equipped in a manner
normal operating consistent with the engineering
range. guidelines for power consumption
given the power supply modules
used within the shelf.
3 If multiple modules/plugs within
the same shelf report this
condition, replace the associated
power supply units.
4 If only one module/plug in the
shelf reports this condition,
replace the module.
Standing Conditions
VOLTIN (Input Voltage Failure)

The corresponding SNMP name for this condition is “inputVoltageFailure”.
If the failure causing this condition results in loss of power to the main
shelf, the alarm will not be reported or logged, as the NE control function
is lost.
Note
Table 524: VOLTIN (Standing Condition)

Severity
SHELF, MN Power to the 1 Check the power distribution to

MOD power unit has the corresponding shelf, PSU, or
failed. PSM.
2 Verify that the fuse or circuit
breaker has not tripped (opened
or Off).
3 Verify that the power connections
are not loose, disconnected,
broken, reversed, or corroded.
Note: Loose or corroded
connections, cables
containing broken conductors
or vibration of the equipment
may raise and clear this
condition multiple times within
a relatively short interval.
4 Resolve any external failures
which may have caused this
condition.
5 If the condition persists, replace
the power unit.
Standing Conditions
VOLTIN-LOW (Input Voltage Low)

The corresponding SNMP name for this condition is “inputVoltageLow”.
Table 525: VOLTIN-LOW (Standing Condition)

Severity
MOD MN The power unit 1 Verify that the power cables are
input voltage is properly connected and deliver
below the required the required power.
value. 2 Verify that the power units have
not failed, and that the shelf
equipping meets the required
power consumption guidelines.
3 Replace the power unit.
VOLTIN1 (Input Voltage Fail 1/A)

The corresponding SNMP name for this condition is “inputVoltageFailurePort1”.
Table 526: VOLTIN1 (Standing Condition)

Severity Cause
SHELF, MN The power feed Check the power feeds supplied

MOD A has failed. to the shelf/module reporting the
condition, to determine the
source of the power distribution
problem prior to the equipment,
and correct any deficiencies.
Problems may include, for
example, loose, disconnected or
corroded supply line
connections, problems with the
office batteries, or tripped or
failed circuit breakers or in-line
fuses.
Standing Conditions
VOLTIN2 (Input Voltage Fail 1/B)

The corresponding SNMP name for this condition is “inputVoltageFailurePort2”.
Table 527: VOLTIN2 (Standing Condition)

Severity Cause
SHELF, MN The power Check the power feeds supplied to

MOD feed B has the shelf/module reporting the
failed. condition, to determine the source of
the power distribution problem prior
to the equipment, and correct any
deficiencies. Problems may include,
for example, loose, disconnected or
corroded supply line connections,
problems with the office batteries, or
tripped or failed circuit breakers or
in-line fuses.
VOLTOUT-FAIL (Output Voltage

Failure)
The corresponding SNMP name for this condition is “outputVoltageFailure”.
Table 528: VOLTOUT-FAIL (Standing Condition)

Severity
MOD CR The power unit Replace the power unit.

has failed.
Standing Conditions
WARM-UP (Shelf warm up)

The corresponding SNMP name for this condition is “warmUp”.
Ignore any red "1" or "2" LEDs on the FCU module while the WARM-
UP condition is raised, since the modules in slots 1 and 2 are switched
off during this phase.
Note
Table 529: WARM-UP (Standing Condition)

SHELF NA The shelf is been internally This condition is

heated to attain a temperature informative and
of 0 degree Celsius. Upon requires no corrective
completing the warm-up action.
phase, the modules in slots 1
and 2 are switched on and the
shelf starts normal operation.
The duration of the shelf
warm-up phase depends on
the environment temperature.
i.e. the lower the environment
temperature, the longer it
takes to reach an internal shelf
temperature of 0 degree
Celsius.
Standing Conditions
WTR (Wait to Restore Active)

The corresponding SNMP name for this condition is “wtrTimerRunning”.
Table 530: WTR (Standing Condition)

Severity Cause
CH NA A previous This condition is informative and no

automatic corrective action is required. Once the
protection provisioned wait-to-restore interval has
switch has elapsed since the time when the automatic
cleared and the switch cleared, the traffic will revert back
protecting to the normally active facility within the
member is still protection group.
carrying the Note : This condition is reported only for
traffic since the protection groups operating in a revertive
wait-to-restore manner. In non-revertive configurations,
time interval has the transient conditions WKSWPR (Auto
not yet elapsed. SwitchToProtect) and WKSWBK (Auto
SwitchToWorking) are issued for changes
in protection state due to automatic
switching.
Standing Conditions
XCON (CCM Cross-Connect Error)

The corresponding SNMP name for this condition is “cfmCcmXConn”.
Table 531: XCON (Standing Condition)

Severity
DOWN- NA This defect is raised 1 Review the provisioned

MEP when one cross- values of the near-end and
connected CCM is far-end maintenance end-
received. It is cleared points and correct any
when a cross- provisioning errors which
connected CCM is not are found.
received for 3.5 times 2 Review each of the
the provisioned CCM supporting data plane
transmission interval of entities along the path in
the last cross- both directions for active
connected CCM. signal loopbacks, and
A CCM is considered release any loopbacks
cross-connected if found.
MAID (48 byte entity
consisting of MD name, 3 Review each of the
MA name and MEP ID) connections of the
does not match with the supporting data plane
MAID of the receiving entities along the path in
MEP, or if MD Level is both directions for cabling
less than the receiving errors and correct any
MEP’s MD Level. errors found.
4 Review any reported data
plane errors along the
service path to determine
the location of a facility
related failure and take the
corrective actions indicated
by the reported data plane
condition(s).
5 Review any reported
supporting equipment
errors along the service
path to determine the
location of an equipment
related failure and take the
corrective actions indicated
by the reported equipment
condition(s).
Transient Conditions
Transient conditions report the occurrence of an event. Each transient condition is
reported by means of an autonomous message sent from the Network Element when the
event occurs. Such events do not exist for a defined period of time, so there is no
subsequent point in time at which the condition is deemed to clear, as is the case for
standing conditions.
As a result, there are no clear reports issued subsequent to the notification of a transient
condition. Further, transient conditions are never reported as alarms and may not have
their notification code property modified - they are always reported as transient conditions
with the severity “Not Alarmed”.
Since these conditions do not have a defined interval during which they are deemed
active, they cannot be retrieved. They may, however, be reviewed after the point in time
at which they are issued by retrieval of the corresponding entries within the autonomous
output log buffer, assuming the buffer has not been cleared or the entry over-written.
Please refer to the section “Alarm and Event Nomenclature” on p. 784 for
details about the two names identifying each transient condition.
Note
AMP-APS-DSBLD (Amp-Shutdown
Disabled)
Table 532: AMP-APS-DSBLD (Transient Condition)
SPEQ The automatic shutdown This condition is informative and

feature of the amplifier no corrective action is needed.
supporting the span has been
disabled.
AMP-APS-ENBLD (Amp-Shutdown
Enabled)
Table 533: AMP-APS-ENBLD (Transient Condition)
SPEQ The automatic shutdown This condition is informative and

feature of the amplifier no corrective action is needed.
supporting the span has been
enabled.
APACT (Alarm Profile-Activate)

Table 534: APACT (Transient Condition)
COM Alarm profile settings have been This condition is informative and
reset to factory defaults or loaded no corrective action is needed.
from a previously saved file.
APACT__FAIL (Alarm Profile-Fail Act)

Table 535: APACT__FAIL (Transient Condition)
COM An attempt to load Verify that the intended alarm profile file is loaded in
alarm profile the standby memory partition and that the file
settings from the contains settings relevant to the current software
standby memory generic running on the NE. Reattempt the updating
partition has failed. process once the correct alarm profile file is loaded
on the standby partition.
APACT__FD (Alarm Profile-Defaults)

Table 536: APACT__FD (Transient Condition)
COM Alarm profile settings This condition is informative and no

have been reset to corrective action is needed.
factory defaults.
APRSNC-END (Alarm Profile-Sync

Done)
Table 537: APRSNC-END (Transient Condition)
COM The process of applying the default This condition is informative and no
severity settings defined within the corrective action is needed.
alarm profile to entities which have
differing values has completed.
APRSNC-START (Alarm Profile-Sync

Start)
Table 538: APRSNC-START (Transient Condition)
COM The process of applying the This condition is informative and no

default severity settings defined corrective action is needed.
within the alarm profile to entities
which have differing values has
begun.
AUTHPWCHG (Authentication
Changed)
Table 539: AUTHPWCHG (Transient Condition)
CH The authentication This condition is informative and no

password value has been corrective action is needed.
changed.
BOOT__COMP (Restart-Complete)
Table 540: BOOT__COMP (Transient Condition)
MOD The module has completed a This condition is informative and requires
restart of its active image. no corrective action.
BOOT__FAIL (Restart-Fail)
Table 541: BOOT__FAIL (Transient Condition)
MOD The module failed Reattempt the module restart. If the module fails
to restart its active repeatedly, contact your vendors support
image. representative for further diagnosis and
assistance. Be prepared to provide details on the
module type and inventory related parameters,
such as the hardware revision.
BOOT__START (Restart-In Progress)

Table 542: BOOT__START (Transient Condition)
MOD The module is undergoing a This condition is informative and requires

restart of its active image. no corrective action.
CDC-FAIL (CD Compensation-Fail)

Table 543: CDC-FAIL (Transient Condition)
CH An attempt was 1 Verify that the facility is provisioned correctly.

made to adjust the 2 Verify that the incoming cable is the correct
chromatic cable and that the transmit and receive ports
dispersion are connected to their proper respective
compensation portions of the cable (i.e. that the fibers are not
setting for the swapped between transmit and receive).
reporting facility
3 Verify that the incoming fiber cable is firmly
but the needed
compensation
setting could not
be attained.
maximum power levels). If the signal meets
the required specifications proceed to the next
step below, otherwise locate the source of the
signal problem upstream and repair the
problem.
5 Proceeding upstream, examine each segment
of the fiber pathway to determine whether
there are dispersion compensating devices
(e.g. fibers or gratings) employed within the
optical signal path. Typical locations of such
elements include the mid-stage of dual-stage
optical amplifiers or near the end of a
transmission fiber span. Verify that each
element along the path meets the
compensation requirements of the path’s
optical design budget. Replace any element
which does not conform to the engineering
budget.
facility.
CLEANUP-COMPL (Path Cleanup-

Complete)
Table 544: CLEANUP-COMPL (Transient Condition)
MOD The user-initiated network This condition is informative and

path cleanup process has requires no corrective action.
completed. Previously
restricted network data paths
may be provisioned, if they
meet the hardware
requirements of the module.
COMPREADY (Precomputation Done)

Table 545: COMPREADY (Transient Condition)
AIDTYPE Probable Suggested Corrective Action

Cause
Ethernet A request to This condition is informative and no corrective action

Tunnel, OTN pre-compute is needed.
Tunnel, the route(s) Conclusion of the pre-computation process does not
WDM Tunnel necessary to guarantee that the computation was successful in
support the computing all required routes matching the specified
tunnel has constraints. Consult the status of the route
concluded. computation provided by properties of the tunnel for
which the request was made to determine the results
of the route computation.
CPY-FILE-COMPL (File Copy-

Complete)
Table 546: CPY-FILE-COMPL (Transient Condition)
SRV-UBR File upload from the NCU to a This condition is informative and
remote FTP server, or file download no corrective action is needed.
from a remote FTP server to the
NCU has completed successfully.
CPY-FILE-FAIL (File Copy-Fail)

Table 547: CPY-FILE-FAIL (Transient Condition)
SRV-UBR File upload from the NCU to a Check the information entered for the
remote FTP server, or file remote FTP server (IP address, user
download from a remote FTP ID, password).
server to the NCU has failed. Re-attempt the file copy operation
using the correct values.
CPY-FILE-PRTL (File Copy-Partial)

Table 548: CPY-FILE-PRTL (Transient Condition)
AIDTYPE Probable Cause Suggested Corrective

Action
SRV-UBR File upload from the NCU to a remote This condition is informative
FTP server, or file download from a and requires no corrective
remote FTP server to the NCU is action.
underway.
CPY-MEM-COMPL (Copy-Complete)
Table 549: CPY-MEM-COMPL (Transient Condition)
SRV-UBR File download from a This condition is informative and no

remote FTP server to the corrective action is needed.
NCU has completed
successfully.
CPY-MEM-FAIL (Copy-Fail)
Table 550: CPY-MEM-FAIL (Transient Condition)

Cause
SRV-UBR File download Review the parameters used and re-attempt the
from a remote memory copy operation using appropriately
FTP server to corrected parameters. Be sure that the specified
the NCU has source and destination memory locations are valid
failed. locations for the type of copy operation being
attempted.
CPY-MEM-PRTL (Copy-Start)
Table 551: CPY-MEM-PRTL (Transient Condition)

Action
SRV-UBR File download from a remote FTP server This condition is

to the NCU is underway and has reached informative and no
an incremental point in the transfer corrective action is
process at which the transfer progress is needed.
reported as a status update mechanism to
relay progress.
CRYAUTHFAIL (Encryption-Access
Fail)
Table 552: CRYAUTHFAIL (Transient Condition)
CH The authentication This condition is informative and no

password supplied on a corrective action is needed. Repeated
encryption related occurrences may indicate an attempt to
command was incorrect. compromise the security of the
associated facility.
CRYPWCHG (Crypto Password

Changed)
Table 553: CRYPWCHG (Transient Condition)
MOD The password for the This condition is informative and no

cryptographic officer has been corrective action is needed.
changed.
CRYRTF (Encryption-Defaults)
Table 554: CRYRTF (Transient Condition)
AIDTYPE Probable Cause Suggested

Corrective
Action
MOD The cryptographic function settings for the This condition is

module have been reset to their factory default informative and
values. All provisioned key values, passwords, no corrective
etc. are erased and reset to the factory defaults. action is needed.
DBACT (Database-Activate)
Table 555: DBACT (Transient Condition)
COM A new copy of the system database This condition is informative and
is being activated, or the system requires no corrective action.
database is being restored from a
backup copy.
DB-BKUP-REPORT (Database-Backup
Report)
Table 556: DB-BKUP-REPORT (Transient Condition)
COM A scheduled automatic This condition is informative and no

database backup corrective action is needed.
operation has completed
successfully.
DYGASP (Equipment-Dying Gasp)

Table 557: DYGASP (Transient Condition)
CH1 The far-end plug has The far-end plug must be replaced.
failed.
1Applicable only to facilities supported by a dual ended type Optojack plug (e.g. SFP-
OD-C or SFP-OD-G).
EQLZ-AUTO (Equalize-Auto)
Table 558: EQLZ-AUTO (Transient Condition)
VCH Scheduled equalization This condition is informative and requires

process adjusted the no corrective action.
channel power.
EQLZ-COMPL (Equalize-Complete)
Table 559: EQLZ-COMPL (Transient Condition)
VCH Equalization process This condition is informative and requires no

OM completed on the corrective action.
CNX- reporting facility.
WDM
EQLZ-DENY (Equalize-Denied)
Table 560: EQLZ-DENY (Transient Condition)
VCH Equalization Verify the cross connection and cross connected C

process denied port are not disabled (DSBLD).
equalization Verify the cross connected C port for the channel
request. optical power received is within the specifications.
OM Verify the reporting facility is not disabled

(DSBLD).
Verify at least one cross connection is In Service
(IS) and the cross connected C port for the channel
optical power received is within the specifications.
EQLZ-FAIL (Equalize-Fail)
Table 561: EQLZ-FAIL (Transient Condition)
VCH Equalization process 1 Verify the fibers to the cross-connected C port for the reporting
completed without facility are correct. Ensure the transmit and receive fibers are
being able to adjust connected to the proper side of the connector (the fibers are not
the channel power swapped between transmit and receive).
within the acceptable 2 Verify optical power is present on the receive interface and is
range. within optical specifications (for example, minimum and maximum
power levels). If the optical power does not meet the required
specifications, proceed to the next step. Otherwise locate the
source of the signal problem upstream and repair the problem.
3 Verify the incoming connector is clean. If necessary, replace the
fiber or module.
CNX-WDM Equalization failed on 1 Verify the connection is active and in-service and does not have
the service path. any outages. If there is an outage affecting the connection,
perform the appropriate corrective actions for the conditions
reported by the data plane elements causing the outage(s).
2 Proceeding from the ingress point to the destination, trace the path
taken by the connection through each element of each node. If any
element has an abnormal operating condition reported, address the
reported issue by following the corrective action for the reported
condition. Be sure to review the logs on the relevant nodes for
transient conditions which have been reported since the last
successful connection equalization operation in addition to any
standing conditions reported by the entities.
3 If the connection passes through any equipment which requires
equalization, verify each element has successfully completed its
own equalization procedure. If any equalization procedures of such
elements have failed, re-attempt those operations and perform any
necessary corrective actions until those equalization procedures
complete successfully.
EQLZ-NULL (Equalize-No Change)

Table 562: EQLZ-NULL (Transient Condition)

Corrective Action
VCH Equalization process examined the channel on This condition is

the reporting facility and the channel was within informative and
the optimal range. requires no
corrective action.
OM Equalization process examined the channels on
the reporting facility and the channels were within
the optimal range.
EQLZ-PASS (Equalize-Pass)
Table 563: EQLZ-PASS (Transient Condition)
VCH Equalization process adjusted This condition is informative and

the channel power on the requires no corrective action.
reporting facility within the
acceptable range.
EQLZ-RAMAN (Equalize-Adjust
Raman)
Table 564: EQLZ-RAMAN (Transient Condition)
VCH Channel power was adjusted, due This condition is informative and
to the addition of a channel on the requires no corrective action.
ingress path (network fiber) to
compensate for RAMAN tilt.
EQLZ-RESTORE (Equalize-Restore)
Table 565: EQLZ-RESTORE (Transient Condition)
VCH An autonomous channel This condition is informative and requires

equalization (not user- no corrective action.
initiated) was performed on
a channel which was at
maximum attenuation.
EQLZ-START (Equalize-Start)
Table 566: EQLZ-START (Transient Condition)
CH Equalization process This condition is informative and requires no

OM started on the corrective action.
CNX- reporting facility.
WDM
EQLZ-WAIT (Equalize-Wait(Busy))
Table 567: EQLZ-WAIT (Transient Condition)
VCH Equalization process is in- This condition is typically

OM progress on the reporting facility. informative and requires no
corrective action.
Await completion of the
equalization process already in
progress, then request another
equalization process, if needed.
EST-ABT (Connection-Setup Abort)

Table 568: EST-ABT (Transient Condition)
WDM Establishing a This condition is informative and no

Connection connection in support of corrective action is needed. Corrective
Ethernet an end-to-end tunnel action will be taken in response to the
Connection has been aborted due to failure of the tunnel establishment.
OTN problems completing
Connection the setup of the end-to-
end tunnel.
EST-COMPL (Connection-Setup Done)

Table 569: EST-COMPL (Transient Condition)
WDM A connection has been This condition is informative and no

Connection established in support of an corrective action is needed.
Ethernet end-to-end tunnel.
Connection
OTN
Connection
EST-FAIL (Connection-Setup Fail)

Table 570: EST-FAIL (Transient Condition)
WDM Establishing a Review the properties of the requested

Connection connection in connection and compare it against the local
Ethernet support of an end- provisioning status to determine which resources
Connection to-end tunnel has are in conflict, and then either alter the properties
OTN failed due to which define the connection so that the conflicts
Connection conflicts which are avoided or alter the provisioning of the
prevent the conflicting elements so that the connection is
establishment of possible when setup of the end-to-end tunnel is
the connection on re-attempted.
the node.
EST-START (Connection-Setup Start)

Table 571: EST-START (Transient Condition)
WDM Setup of a connection in This condition is informative and no

Connection support of an end-to-end corrective action is needed.
Ethernet tunnel has begun.
Connection
OTN
Connection
FENDCHG (Neighbor-Change Far End)

Table 572: FENDCHG (Transient Condition)
TOP A far-end property change This condition is informative and no

has been detected by the corrective action is needed.
neighbor discovery
protocol.
FILE-PA-COMPL (Path Analyzer File-

Done)
Table 573: FILE-PA-COMPL (Transient Condition)
WDM Connection The Path Analyzer file was This condition is informative and
successfully created. requires no corrective action.
FILE-PA-FAIL (Path Analyzer File-

Fail)
Table 574: FILE-PA-FAIL (Transient Condition)
WDM Connection The Path Analyzer file Re-attempt the service creation.

creation has failed.
FILE-PA-START (Path Analyzer File-

Start)
Table 575: FILE-PA-START (Transient Condition)
WDM Connection Creation of the Path Analyzer This condition is informative and

file has started. requires no corrective action.
FLT-TOP (Topology-Data Invalid)

Table 576: FLT-TOP (Transient Condition)
TOP The Network Ensure that all of the facilities connecting the
Element's Network Element to adjacent elements are
knowledge of the provisioned and operating correctly and that all of
network topology the required supervisory channel facilities are
has been found to provisioned and operating correctly, and then
be inaccurate or refresh the Network Elements knowledge of the
incomplete. topology by executing the Topology Detection
command on the Network Element.
FRCD-REBOOT (Forced Reboot)

Table 577: FRCD-REBOOT (Transient Condition)
MOD The backup (standby) This condition is informative and no

controller in a duplex corrective action is needed.
protection group was
forced to restart.
FRCDWKSWBK (Force Switch To

Working)
Table 578: FRCDWKSWBK (Transient Condition)

Action
CH The operator issued a protection switch This condition is

request to the working path. Since this has informative and requires no
OM the highest priority currently, traffic was corrective action.
switched to the working path.
FRCDWKSWPR (Force Switch To

Protect)
Table 579: FRCDWKSWPR (Transient Condition)

Action
CH The operator issued a protection switch This condition is informative

request to the protection path. Since this and requires no corrective
OM has the highest priority currently, traffic action.
was switched to the protection path.
FWP-UPDATE (FWP-Update
Complete)
Table 580: FWP-UPDATE (Transient Condition)

Action
MOD The firmware version on the module This condition is informative

(which supports encryption functions) and no corrective action is
has been modified as the result of a needed.
firmware upgrade or reversion.
FWPHASH-FAIL (FWP Hash Fail)

Table 581: FWPHASH-FAIL (Transient Condition)
MOD Firmware package If this condition is raised after

hash verification failed. firmware upgrade, power failure, or
after pressing the self-test button,
replace the module.
For all other cases, contact ADVA

Optical Networking Technical
Services.
FWPHASH-PASS (FWP Hash Pass)

Table 582: FWPHASH-PASS (Transient Condition)

Action
MOD Firmware package hash This condition is informative

verification was successful. and requires no corrective
action.
FWPREVCHG (FWP-Version Change)

Table 583: FWPREVCHG (Transient Condition)

Corrective Action
MOD The module (which supports encryption functions) This condition is

has been provisioned to specify a firmware informative and no
package version as one which may be installed. corrective action is
Installation of the firmware package must also be needed.
enabled before the installation may be performed.
INSTALL__COMPL (Transfer-
Complete)
Table 584: INSTALL__COMPL (Transient Condition)
MOD The firmware package This condition is informative and

was successfully requires no corrective action.
transferred to the
respective module(s).
INSTALL__FAIL (Transfer-Fail)
Table 585: INSTALL__FAIL (Transient Condition)
MOD Transfer of the firmware This condition requires no corrective

package to the action. Corrective action will be taken in
respective module(s) response to any alarms indicating the
failed. root cause of this failure.
INSTALL__START (Transfer-In
Progress)
Table 586: INSTALL__START (Transient Condition)
MOD Transfer of the firmware This condition is informative and

package to the requires no corrective action.
respective module(s) has
begun.
INTRUDE-RCV (Rx Fiber-Intrusion)

Table 587: INTRUDE-RCV (Transient Condition)
DCN The received 1 Verify that no testing is being performed upon

optical power level the fibers along the facility’s path which are
on the facility has expected to cause a change in the received
fluctuated in a signal optical power level, such as the use of
manner a device employing macro-bending of the
characteristic of an fiber to monitor the optical power at an
attempt to non- intermediate point along the cable.
intrusively tap into 2 Verify that all facilities and equipment along
the optical signal the path are correctly provisioned and are
for purposes of operating without any other active conditions
eaves-dropping on and that they are all in an in-service normal
the signals within (“In Service”) state. Confirm that the Rx Att.
the fiber. Gradient TH attribute of the facility is set to
the correct value.
3 Conduct an examination of the fiber plant at
each node along the link to verify that the
OM relevant optical fiber cables have not been
subjected to macro-bending or other physical
stresses which exceed the specified physical
limits for the fiber cable (e.g. minimum bend
radius, maximum tension).
4 Conduct a physical inspection of the inter-
node portions of the fiber plant using an
optical time-domain reflectometer (OTDR) or
similar device to locate the point of abnormal
attenuation within the fiber and repair the
damaged portion.
5 Conduct a physical inspection of the inter-
node portions of the fiber plant by on-site
visual inspection to locate the point of
abnormal attenuation.
INTRUDE-TRMT (Tx Fiber-Intrusion)

Table 588: INTRUDE-TRMT (Transient Condition)
DCN The optical power level on 1 Verify that no testing is being

the transmitted fiber performed upon the fibers along the
carrying the facility has facility’s path which are expected to
fluctuated in a manner cause a change in the far-end received
characteristic of an signal optical power level, such as the
attempt to non-intrusively use of a device employing macro-
tap into the optical signal bending of the fiber to monitor the
for purposes of eaves- optical power at an intermediate point
dropping on the signals along the cable.
within the fiber. 2 Verify that all facilities and equipment
along the path are correctly
provisioned and are operating without
any other active conditions and that
they are all in an in-service normal (“In
Service”) state. Confirm that the Rx
Att. Gradient TH attribute of the far-
end facility is set to the correct value.
3 Conduct an examination of the fiber
plant at each node along the link to
OM verify that the relevant optical fiber
cables have not been subjected to
macro-bending or other physical
stresses which exceed the specified
physical limits for the fiber cable (e.g.
minimum bend radius, maximum
tension).
4 Conduct a physical inspection of the
inter-node portions of the fiber plant
using an optical time-domain
reflectometer (OTDR) or similar
device to locate the point of abnormal
attenuation within the fiber and repair
the damaged portion.
5 Conduct a physical inspection of the
inter-node portions of the fiber plant by
on-site visual inspection to locate the
point of abnormal attenuation.
KEX-FAIL (Key Exchange-Fail)

Table 589: KEX-FAIL (Transient Condition)
CH A key exchange This condition is informative and no corrective

failed to complete action is needed.
successfully. If the key exchange fails multiple times in
succession, it may ultimately exceed the limit on
the number of successive failures and lead to the
KEXLFT-DEG and/or KEXLFT-FAIL conditions.
KEX-RESET (Key Exchange Fail

Count)
Table 590: KEX-RESET (Transient Condition)
CH The counter counting the This condition is informative and no

number of successive times corrective action is needed.
key exchange has failed to
complete successfully has
been reset.
MANWKSWBK (Manual
SwitchToWorking)
Table 591: MANWKSWBK (Transient Condition)
CH The previously active This switch occurs due to:

protection switch has • a locally issued manual switch release
ETH been manually request,
released and the
• a far-end manual switch release request
traffic is now carried
signalled from the peer bidirectionally
by the facility
switched protection group.
designated as the
working member of This condition is informative and no corrective
OM the protection group. action is needed.
MANWKSWPR (Manual
SwitchToProtect)
Table 592: MANWKSWPR (Transient Condition)

Cause
CH The traffic has This switch occurs due to:

been manually • a locally issued manual switch request,
ETH switched from
• a far-end manual switch request signalled from
the working
the peer bidirectionally switched protection
member of the
group.
protection group
to the protection
action is needed.
OM member.
MODFCN-COMPL (Connection-Modify
Done)
Table 593: MODFCN-COMPL (Transient Condition)

Connection modified in support of an corrective action is needed.
Ethernet end-to-end tunnel.
Connection
OTN
Connection
MODFCN-FAIL (Connection-Modify
Fail)
Table 594: MODFCN-FAIL (Transient Condition)
WDM Modification of a Review the connection modification request and

Connection connection which compare it against the local provisioning status to
Ethernet exists in support determine which resources are in conflict, and
Connection of an end-to-end then either alter the properties which define the
OTN tunnel has failed connection so that the conflicts are avoided or
Connection due to conflicts alter the provisioning of the conflicting elements
which prevent the so that the connection modification is possible
modification. when re-attempted.
MODFCN-START (Connection-Modify
Start)
Table 595: MODFCN-START (Transient Condition)
WDM Modification of a connection This condition is informative and no

Connection which exists in support of an corrective action is needed.
Ethernet end-to-end tunnel has
Connection begun.
OTN
Connection
NTPTEST-FAIL (NTP-Test Fail)

Table 596: NTPTEST-FAIL (Transient Condition)
NTPSRV A manually initiated This condition is informative and no corrective

test of communication action is needed. Corrective action will be
to the remote NTP taken in response to other reported conditions.
server has failed.
NTPTEST-SUCCESS (NTP-Test Pass)

Table 597: NTPTEST-SUCCESS (Transient Condition)
NTPSRV A manually initiated test of This condition is informative and no

communication to the remote corrective action is needed.
NTP server has succeeded.
REF-END (Reference-Save Done)

Table 598: REF-END (Transient Condition)
COM A manually initiated save of This condition is informative and no

optical power PM register corrective action is needed.
reference levels has completed.
REF-START (Reference-Save Start)

Table 599: REF-START (Transient Condition)
COM A manually initiated save of This condition is informative and no

optical power PM register corrective action is needed.
reference levels has begun.
RESTN-COMP (Restoration-Complete)
Table 600: RESTN-COMP (Transient Condition)

Tunnel restored via re-routing. corrective action is needed.
RESTN-FAIL (Restoration-Fail)
Table 601: RESTN-FAIL (Transient Condition)

Cause
WDM Restoration of a Review the connection provisioning to verify that the

Tunnel connection routing criteria is correct. If the criteria is correct, then
experiencing a the connection cannot be restored under the
service outage prevailing network conditions, and this condition is
has failed. informative in nature, If the criteria is incorrect, then
alter the properties of the connection so that re-
routing can succeed.
RESTN-START (Restoration-Start)
Table 602: RESTN-START (Transient Condition)

Action
WDM Restoration of a connection which exists in This condition is

Tunnel support of an end-to-end tunnel, but which informative and no
has experienced a service affecting outage, corrective action is
has begun. needed.
RESTNNUM-CHANGED (Guaranteed
Path Changed)
Table 603: RESTNNUM-CHANGED (Transient Condition)

Action
WDM In a network with a shared guaranteed This condition is informative.

Tunnel path, this event indicates a change in the For the case when the
guaranteed path number. A value of "0" guaranteed path number is
indicates the guaranteed path is used by 0, corrective action will be
another tunnel and is therefore taken in response to the
unavailable for restoring traffic, while a abnormality reported at the
value of "1" indicates the guaranteed respective working path.
path is again available for restoration.
This information is used by the Network
Management System to update the
guaranteed path number for services.
RVSN-BLKD (Reversion Blocked)

Table 604: RVSN-BLKD (Transient Condition)
WDM Reversion of traffic from the This condition is informative and

Tunnel protection connection to the requires no corrective action.
working connection is Corrective action, if needed, will be
blocked. taken in response to an active failure
condition reported along the working
connection.
RVSN-COMP (Reversion-Complete)
Table 605: RVSN-COMP (Transient Condition)
WDM Traffic has reverted to the normal This condition is informative and no
Tunnel working connection route and is corrective action is needed.
no longer utilizing the protection
route.
RVSN-FAIL (Reversion-Fail)
Table 606: RVSN-FAIL (Transient Condition)
WDM An attempt to revert This condition is informative and no corrective

Tunnel traffic back to the action is needed. Corrective action, if needed, will
normal working be taken in response to an active failure condition
connection from the reported along the normal working connection.
protection route has
failed.
RVSN-NOTREADY (Reversion-
NotReady)
Table 607: RVSN-NOTREADY (Transient Condition)
WDM The working connection is not This condition is informative and

Tunnel ready, hence traffic cannot be requires no corrective action.
reverted from the protection Corrective action, if needed, will be
connection. taken in response to an active failure
condition reported along the working
connection.
RVSN-READY (Reversion-Ready)
Table 608: RVSN-READY (Transient Condition)
WDM Traffic can be reverted from This condition is informative and

Tunnel the protection connection requires no corrective action.
back to the working
connection.
RVSN-START (Reversion-Start)
Table 609: RVSN-START (Transient Condition)
WDM Reversion of traffic from the This condition is informative and no

Tunnel protection connection back to corrective action is needed.
the normal working
connection has begun.
RVSN-UNKNOWN (Reversion
Unknown)
Table 610: RVSN-UNKNOWN (Transient Condition)
WDM Tunnel No information is This condition is informative and requires no

available on corrective action. Corrective action, if needed,
readiness to revert. will be taken in response to an active failure
The control plane is condition reported along the normal working
unable to detect connection.
failed link repair and
hence will not
provide information
on reversion state.
RVSN-WTR (Wait-to-Revert)
Table 611: RVSN-WTR (Transient Condition)

Action
WDM The failure of the working connection has This condition is informative
Tunnel been cleared, and the service has entered and no corrective action is
the wait to restore hold-off time, after needed.
which, the traffic will revert from the
protection connection back to the normal
working connection, assuming no failures
or other protection state causing changes
occur.
SF-COM (Communication Fail)

Table 612: SF-COM (Transient Condition)
OM The OPPM received 1 Refer to the alarm list to locate the

validated notification(s) signal failure condition(s) raised by the
from its protection trigger OPPM's protection trigger partner(s).
partner(s) that a signal 2 Follow the troubleshooting steps
failure condition exists in indicated in this chapter to resolve the
the network. alarm(s).
SKTIMERCHG (Session Key-Duration)

Table 613: SKTIMERCHG (Transient Condition)

Action
CH The value of the timer defining the This condition is informative

allowable lifetime of the session key and no corrective action is
has been changed. needed.
SPEQDC-DISABLED (Span-Auto
Compensate)
Table 614: SPEQDC-DISABLED (Transient Condition)
SPEQ Dynamic compensation of optical This condition is informative and

power level fluctuations on a facility no corrective action is needed.
which supports automatic span
equalization has been disabled.
SPEQDC-ENABLED (Span-Dynamic
Compensate)
Table 615: SPEQDC-ENABLED (Transient Condition)
SPEQ Dynamic compensation of optical This condition is informative

power level fluctuations on a facility and no corrective action is
which supports automatic span needed.
equalization has been enabled.
SPEQ-DENY (Span-Equalize Deny)

Table 616: SPEQ-DENY (Transient Condition)

Cause
SPEQ A request to Review the provisioning of the elements associated

perform span with the span for which the equalization attempt has
equalization been denied and correct any provisioning errors or
adjustment omissions. Ensure that all entities are in-service and
has been operating error-free and then re-attempt the span
denied. equalization request.
SPEQ-WAIT (Span-Process Busy)

Table 617: SPEQ-WAIT (Transient Condition)
SPEQ A request to perform Await the completion of the request already in

span equalization progress and review the status to determine if
adjustment has been a subsequent request is necessary, and if so,
denied since a prior submit a new request at that time.
adjustment operation
is still in progress.
SPGAIN-AUTO (Span-Auto Gain

Adjust)
Table 618: SPGAIN-AUTO (Transient Condition)

Action
SPEQ A loss of signal condition has cleared, This condition is

causing the automatic span equalization informative and no
process to re-assess the required gain corrective action is
equalization settings affecting the optical needed.
line.
SPGAIN-DYNAMIC (Span-Dynamic
GainAdjust)
Table 619: SPGAIN-DYNAMIC (Transient Condition)

Corrective Action
SPEQ The optical power level of the received signal This condition is
at the amplifier has changed by an amount informative and no
sufficient to cause the automatic span corrective action is
equalization process to re-assess the needed.
required gain equalization settings affecting
the optical line.
SPGAIN-FAIL (Span-Gain Adjust Fail)

Table 620: SPGAIN-FAIL (Transient Condition)
SPEQ An attempt to Review the provisioned values for the per-channel

perform span power level, set point, gain calibration adjustment,
equalization gain the number of channels supported within the band
adjustment has and the type of configuration (e.g. Fixed OADM
computed versus Reconfigurable OADM) applicable to the
required gain span, correct any values which do not conform to
values which are the network engineering specifications, then
outside the initiate the span equalization adjustment process.
allowable limits.
SPGAIN-MANUAL (Span-Manual Gain

Adjust)
Table 621: SPGAIN-MANUAL (Transient Condition)
SPEQ A user has manually initiated This condition is informative and no

the span equalization gain corrective action is needed.
adjustment process.
SPGAIN-NULL (Span-No Gain Adjust)

Table 622: SPGAIN-NULL (Transient Condition)

Corrective
Action
SPEQ A span equalization gain adjustment process has This condition is

completed, with the determination that all gain informative and
setting values in effect prior to that invocation are no corrective
acceptable (i.e. no changes are required to any of action is needed.
the values).
SPPPC-ADOPT (Span-Adopt PPC)

Table 623: SPPPC-ADOPT (Transient Condition)

Corrective
Action
SPEQ A span equalization gain adjustment process has This condition is

completed and has adopted the power per channel informative and
values in effect prior to the enabling of automatic no corrective
span equalization functionality on the associated action is needed.
amplifier.
SWACT (Software-Activate)
Table 624: SWACT (Transient Condition)
SRV-UBR The system software has been This condition is informative and no
activated from STBY area. corrective action is needed.
SWACT__FAIL (Software-Activate
Fail)
Table 625: SWACT__FAIL (Transient Condition)
SRV-UBR The system 1 Verify that the software load specified in

software could not the activation request is a valid load and
be activated from that all necessary files are available and
STBY area or the have a valid checksum.
software load was 2 If the system software reverted due to
not accepted within expiration of the acceptance interval and
the specified use of the new load is desired, perform the
acceptance interval. software migration operation again and
accept the load prior to the expiration of the
acceptance interval (it may be necessary
to specify a larger interval in order to have
sufficient time to accept the load).
3 If use of the existing load is acceptable, no
corrective action is required.
SWDX-COMP (Partner-Switch
Complete)
Table 626: SWDX-COMP (Transient Condition)
MOD An automatic or This condition is informative and no

manually initiated switch corrective action is needed.
between the members of
a duplex protection group
has completed
successfully.
SWDX-FAIL (Partner-Switch Fail)

Table 627: SWDX-FAIL (Transient Condition)
MOD An automatic or This condition is informative and no corrective

manually initiated action is needed.
switch between the The cause of the failure to switch may be
members of a duplex reported as a separate condition, which should
protection group be addressed according to its respective
failed to complete corrective action.
successfully.
SWDX-START (Partner-Switch Start)

Table 628: SWDX-START (Transient Condition)
MOD An automatic or This condition is informative and no corrective

manual switch was action is needed.
initiated between the
members of a duplex
protection group.
SWITCH__COMPL (Switch-Complete)
Table 629: SWITCH__COMPL (Transient Condition)
MOD Activation of the firmware This condition is informative and

package was requires no corrective action.
successfully completed
at the respective module
(s).
SWITCH__FAIL (Switch-Fail)
Table 630: SWITCH__FAIL (Transient Condition)
MOD The module did not 1 Resolve any other conditions at this
respond to the firmware module/NE which may be causing
activation request. the activation failure.
2 Re-issue the activation request.
SWITCH__REJECT (Switch-Reject)
Table 631: SWITCH__REJECT (Transient Condition)
MOD The module rejected 1 Resolve any other conditions at this

application of the new module which may be causing the
firmware load. In native activation failure.
modules, this may occur 2 Re-issue the activation request.
if the firmware package
3 If the module still rejects the
on the passive image is
activation request, force a firmware
corrupted.
upload and activation using the
Update option.
SWITCH__START (Switch-In
Progress)
Table 632: SWITCH__START (Transient Condition)
MOD Activation of the firmware This condition is informative and

package has begun at the requires no corrective action.
respective module(s).
SYSRES__RELOAD (NCU-Restart)
Table 633: SYSRES__RELOAD (Transient Condition)
SRV-UBR The network element This condition is informative and no corrective

system software action is needed.
generic has Since the restart will terminate all active login
completed a restart. sessions, users must establish new login
sessions following the normal authentication
process, to perform further operations.
T-BBE-ODU-HT__1DAY (ODU-BBE
Day)
Table 634: T-BBE-ODU-HT__1DAY (Transient Condition)
CH The number of This condition is informative and requires no

background block immediate corrective action. If the condition
errors measured in persists across multiple intervals, it may indicate
the Optical Data Unit a failure at the source or receiving plug or module,
(ODU) layer exceeds or a failure in one of the cables along the path
the provisioned 1-Day between the source and the receiver.
threshold value.
To ensure that the condition is reported only
under the correct circumstances, verify that the
1-Day threshold level is provisioned correctly.
T-BBE-OTU-HT__1DAY (OTU-BBE
Day)
Table 635: T-BBE-OTU-HT__1DAY (Transient Condition)

errors measured persists across multiple intervals, it may indicate a
in the Optical failure at the source or receiving plug or module, or a
Transport Unit failure in one of the cables along the path between
(OTU) layer the source and the receiver.
exceeds the
provisioned 1- To ensure that the condition is reported only under
Day threshold the correct circumstances, verify that the 1-Day
value. threshold level is provisioned correctly.
T-BBE-PCS-HT__1DAY (PCS-BBE
Day)
Table 636: T-BBE-PCS-HT__1DAY (Transient Condition)

Physical Coding immediate corrective action. If the condition
Sub-layer persists across multiple intervals, it may indicate a
background block failure at the source or receiving plug or module, or a
errors detected by failure in one of the cables along the path between
the receiver the source and the receiver.
exceeds the
provisioned 1-Day To ensure that the condition is reported only under
threshold value. the correct circumstances, verify that the 1-Day
T-BBE-TCMA-HT__1DAY (TCM_A-BBE
Day)
Table 637: T-BBE-TCMA-HT__1DAY (Transient Condition)

errors measured in the persists across multiple intervals, it may
Tandem Connection indicate a failure at the source or receiving plug
Monitoring instance A or module, or a failure in one of the cables along
(TCMA) layer the path between the source and the receiver.
exceeds the
provisioned 1-Day To ensure that the condition is reported only
threshold value. under the correct circumstances, verify that the
T-BBE-TCMB-HT__1DAY (TCM_B-BBE
Day)
Table 638: T-BBE-TCMB-HT__1DAY (Transient Condition)

Monitoring instance B or module, or a failure in one of the cables along
(TCMB) layer exceeds the path between the source and the receiver.
the provisioned 1-Day
threshold value. To ensure that the condition is reported only
T-BBE-TCMC-HT__1DAY (TCM__C-
BBE Day)
Table 639: T-BBE-TCMC-HT__1DAY (Transient Condition)

Monitoring instance C or module, or a failure in one of the cables along
(TCMC) layer exceeds the path between the source and the receiver.
the provisioned 1-Day
T-BERCE-FEC-HT__1DAY (BER Before

FEC Day)
Table 640: T-BERCE-FEC-HT__1DAY (Transient Condition)
CH The number of bit This condition is informative and requires no

errors detected prior immediate corrective action. If the condition
to error correction persists across multiple intervals, it may indicate
using the Forward a failure at the source or receiving plug or module,
Error Correction or a failure in one of the cables along the path
process exceeds the between the source and the receiver.
provisioned 1-Day
threshold value. To ensure that the condition is reported only under
the correct circumstances, verify that the 1-Day
T-CE-FEC-HT__1DAY (FEC-Corrected
Day)
Table 641: T-CE-FEC-HT __1DAY (Transient Condition)

corrected errors immediate corrective action. If the condition
detected by persists across multiple intervals, it may indicate a
Forward Error failure at the source or receiving plug or module, or
Correction a failure in one of the cables along the path
provisioned 1-Day
T-CV-L-HT__1DAY (Line/MS-CV Day)

Table 642: T-CV-L-HT__1DAY (Transient Condition)

line/multiplex section layer immediate corrective action. If the condition
coding violations detected persists across multiple intervals, it may
by the receiver exceeds indicate a failure at the source or receiving
the provisioned 1-Day plug or module, or a failure in one of the
threshold value. cables along the path between the source
and the receiver.

under the correct circumstances, verify that
the 1-Day threshold level is provisioned
correctly.
T-CV-PCS-HT__1DAY (PCS-CV Day)

Table 643: T-CV-PCS-HT__1DAY (Transient Condition)

Sub-layer coding persists across multiple intervals, it may indicate
violations detected a failure at the source or receiving plug or module,
by the receiver or a failure in one of the cables along the path
provisioned 1-Day
T-CV-S-HT__1DAY (Sec/RS-CV Day)

Table 644: T-CV-S-HT__1DAY (Transient Condition)

section/regenerator immediate corrective action. If the condition
section layer coding persists across multiple intervals, it may
violations detected indicate a failure at the source or receiving plug
by the receiver or module, or a failure in one of the cables along
exceeds the the path between the source and the receiver.
provisioned 1-Day
T-CVTX-PCS-HT__1DAY (PCS-CV Tx
Day)
Table 645: T-CVTX-PCS-HT__1DAY (Transient Condition)

Physical Coding Sub- immediate corrective action. If the condition
layer coding persists across multiple intervals, it may indicate
violations transmitted a failure at the source or receiving plug or
exceeds the module, or a failure in one of the cables along the
provisioned 1-Day path between the source and the receiver.
threshold value.
T-DE-PCS-HT__1DAY (PCS-Disparity
Error Day)
Table 646: T-DE-PCS-HT__1DAY (Transient Condition)

Sub-layer disparity persists across multiple intervals, it may indicate a
errors detected by failure at the source or receiving plug or module, or
the receiver a failure in one of the cables along the path
provisioned 1-Day
T-ES-FEC-HT__1DAY (FEC-ES Day)

Table 647: T-ES-FEC-HT__1DAY (Transient Condition)
CH The number of errored This condition is informative and requires no

seconds detected by immediate corrective action. If the condition
Forward Error persists across multiple intervals, it may indicate
Correction exceeds a failure at the source or receiving plug or
the provisioned 1-Day module, or a failure in one of the cables along the
threshold value. path between the source and the receiver.

T-ES-L-HT__1DAY (Line/MS-ES Day)

Table 648: T-ES-L-HT__1DAY (Transient Condition)

line/multiplex section immediate corrective action. If the condition
layer errored seconds persists across multiple intervals, it may
detected by the receiver indicate a failure at the source or receiving
exceeds the provisioned plug or module, or a failure in one of the
1-Day threshold value. cables along the path between the source
and the receiver.

correctly.
T-ES-ODU-HT__1DAY (ODU-ES Day)

Table 649: T-ES-ODU-HT__1DAY (Transient Condition)

seconds measured in immediate corrective action. If the condition
the Optical Data Unit persists across multiple intervals, it may
(ODU) layer exceeds indicate a failure at the source or receiving plug
the provisioned 1-Day or module, or a failure in one of the cables along
threshold value. the path between the source and the receiver.

T-ES-OTU-HT__1DAY (OTU-ES Day)

Table 650: T-ES-OTU-HT __1DAY (Transient Condition)

the Optical Transport persists across multiple intervals, it may
Unit (OTU) layer indicate a failure at the source or receiving plug
exceeds the provisioned or module, or a failure in one of the cables
1-Day threshold value. along the path between the source and the
receiver.

correctly.
T-ES-PCS-HT__1DAY (PCS-ES Day)

Table 651: T-ES-PCS-HT__1DAY (Transient Condition)

Sub-layer errored persists across multiple intervals, it may indicate
seconds detected by a failure at the source or receiving plug or module,
the receiver exceeds or a failure in one of the cables along the path
the provisioned 1- between the source and the receiver.
Day threshold value.
To ensure that the condition is reported only under
T-ES-S-HT__1DAY (Sec/RS-ES Day)

Table 652: T-ES-S-HT__1DAY (Transient Condition)

section layer errored persists across multiple intervals, it may indicate
seconds detected by a failure at the source or receiving plug or
the receiver exceeds module, or a failure in one of the cables along the
the provisioned 1-Day path between the source and the receiver.
threshold value.
T-ES-TCMA-HT__1DAY (TCM_A-ES
Day)
Table 653: T-ES-TCMA-HT __1DAY (Transient Condition)

the Tandem persists across multiple intervals, it may indicate
Connection a failure at the source or receiving plug or
Monitoring instance A module, or a failure in one of the cables along the
(TCMA) layer path between the source and the receiver.
exceeds the
T-ES-TCMB-HT__1DAY (TCM_B-ES
Day)
Table 654: T-ES-TCMB-HT__1DAY (Transient Condition)

the Tandem persists across multiple intervals, it may indicate
Connection a failure at the source or receiving plug or
Monitoring instance B module, or a failure in one of the cables along the
(TCMB) layer path between the source and the receiver.
exceeds the
T-ES-TCMC-HT__1DAY (TCM_C-ES
Day)
Table 655: T-ES-TCMC-HT__1DAY (Transient Condition)

the Tandem Connection persists across multiple intervals, it may
Monitoring instance C indicate a failure at the source or receiving plug
(TCMC) layer exceeds or module, or a failure in one of the cables
the provisioned 1-Day along the path between the source and the
threshold value. receiver.

correctly.
T-ESTX-PCS-HT__1DAY (PCS-ES Tx
Day)
Table 656: T-ESTX-PCS-HT__1DAY (Transient Condition)

Sub-layer errored persists across multiple intervals, it may indicate
seconds transmitted a failure at the source or receiving plug or
exceeds the module.
provisioned 1-Day
T-SEFS-S-HT__1DAY (Sec/RS-SEFS
Day)
Table 657: T-SEFS-S-HT __1DAY (Transient Condition)

section layer persists across multiple intervals, it may indicate
severely errored a failure at the source or receiving plug or module,
frame seconds or a failure in one of the cables along the path
detected by the between the source and the receiver.
receiver exceeds the
T-SES-FEC-HT__1DAY (FEC-SES Day)

Table 658: T-SES-FEC-HT__1DAY (Transient Condition)

severely errored immediate corrective action. If the condition persists
seconds detected across multiple intervals, it may indicate a failure at
by Forward Error the source or receiving plug or module, or a failure in
Correction one of the cables along the path between the source
exceeds the and the receiver.
provisioned 1-Day
T-SES-L-HT__1DAY (Line/MS-SES
Day)
Table 659: T-SES-L-HT__1DAY (Transient Condition)

layer severely errored persists across multiple intervals, it may
seconds detected by indicate a failure at the source or receiving plug
the receiver exceeds or module, or a failure in one of the cables along
the provisioned 1-Day the path between the source and the receiver.
threshold value.
T-SES-ODU-HT__1DAY (ODU-SES
Day)
Table 660: T-SES-ODU-HT__1DAY (Transient Condition)

severely errored immediate corrective action. If the condition
seconds measured persists across multiple intervals, it may indicate a
in the Optical Data failure at the source or receiving plug or module, or a
Unit (ODU) layer failure in one of the cables along the path between
exceeds the the source and the receiver.
provisioned 1-Day
T-SES-OTU-HT__1DAY (OTU-SES
Day)
Table 661: T-SES-OTU-HT __1DAY (Transient Condition)

seconds measured persists across multiple intervals, it may indicate a
in the Optical failure at the source or receiving plug or module, or a
Transport Unit failure in one of the cables along the path between
(OTU) layer the source and the receiver.
exceeds the
T-SES-S-HT__1DAY (Sec/RS-SES
Day)
Table 662: T-SES-S-HT__1DAY (Transient Condition)

section layer severely persists across multiple intervals, it may
errored seconds indicate a failure at the source or receiving plug
detected by the or module, or a failure in one of the cables along
receiver exceeds the the path between the source and the receiver.
provisioned 1-Day
T-SES-TCMA-HT__1DAY (TCM_A-SES
Day)
Table 663: T-SES-TCMA-HT__1DAY (Transient Condition)
CH The number of severely This condition is informative and requires no

errored seconds immediate corrective action. If the condition
measured in the Tandem persists across multiple intervals, it may
Connection Monitoring indicate a failure at the source or receiving
instance A (TCMA) layer plug or module, or a failure in one of the cables
exceeds the provisioned along the path between the source and the
1-Day threshold value. receiver.

correctly.
T-SES-TCMB-HT__1DAY (TCM_B-SES
Day)
Table 664: T-SES-TCMB-HT__1DAY (Transient Condition)

errored seconds measured immediate corrective action. If the condition
in the Tandem Connection persists across multiple intervals, it may
Monitoring instance B indicate a failure at the source or receiving
(TCMB) layer exceeds the plug or module, or a failure in one of the
provisioned 1-Day cables along the path between the source
threshold value. and the receiver.

correctly.
T-SES-TCMC-HT__1DAY (TCM_C-SES
Day)
Table 665: T-SES-TCMC-HT__1DAY (Transient Condition)

errored seconds immediate corrective action. If the condition
measured in the Tandem persists across multiple intervals, it may
Connection Monitoring indicate a failure at the source or receiving
instance C (TCMC) layer plug or module, or a failure in one of the
exceeds the provisioned cables along the path between the source
1-Day threshold value. and the receiver.

correctly.
T-SETX-PCS-HT__1DAY (PCS-Sync
Header Tx Day)
Table 666: T-SETX-PCS-HT__1DAY (Transient Condition)

seconds persists across multiple intervals, it may indicate a
transmitted at the failure at the source or receiving plug or module.
PCS layer exceeds
the provisioned 1- To ensure that the condition is reported only under
Day threshold the correct circumstances, verify that the 1-Day
value. threshold level is provisioned correctly.
T-UAS-L-HT__1DAY (Line/MS-UAS
Day)
Table 667: T-UAS-L-HT __1DAY (Transient Condition)

layer unavailable persists across multiple intervals, it may indicate
seconds detected by a failure at the source or receiving plug or module,
the receiver exceeds or a failure in one of the cables along the path
Day threshold value.
T-UAS-ODU-HT__1DAY (ODU-UAS
Day)
Table 668: T-UAS-ODU-HT__1DAY (Transient Condition)

unavailable seconds immediate corrective action. If the condition
measured in the Optical persists across multiple intervals, it may
Data Unit (ODU) layer indicate a failure at the source or receiving plug
exceeds the or module, or a failure in one of the cables along
provisioned 1-Day the path between the source and the receiver.
threshold value.
T-UAS-OTU-HT__1DAY (OTU-UAS
Day)
Table 669: T-UAS-OTU-HT__1DAY (Transient Condition)

measured in the persists across multiple intervals, it may indicate
Optical Transport a failure at the source or receiving plug or module,
Unit (OTU) layer or a failure in one of the cables along the path
provisioned 1-Day
T-UAS-TCMA-HT__1DAY (TCM_A-UAS
Day)
Table 670: T-UAS-TCMA-HT__1DAY (Transient Condition)

Tandem Connection a failure at the source or receiving plug or module,
Monitoring instance or a failure in one of the cables along the path
A (TCMA) layer between the source and the receiver.
exceeds the
T-UAS-TCMB-HT__1DAY (TCM_B-UAS
Day)
Table 671: T-UAS-TCMB-HT__1DAY (Transient Condition)

measured in the persists across multiple intervals, it may
Tandem Connection indicate a failure at the source or receiving
Monitoring instance B plug or module, or a failure in one of the cables
(TCMB) layer exceeds along the path between the source and the
the provisioned 1-Day receiver.
threshold value.
correctly.
T-UAS-TCMC-HT__1DAY (TCM_C-UAS
Day)
Table 672: T-UAS-TCMC-HT__1DAY (Transient Condition)

Tandem Connection a failure at the source or receiving plug or module,
Monitoring instance or a failure in one of the cables along the path
C (TCMC) layer between the source and the receiver.
exceeds the
T-UBE-FEC-HT__1DAY (FEC-UBE Day)

Table 673: T-UBE-FEC-HT__1DAY (Transient Condition)

uncorrectable block immediate corrective action. If the condition
errors detected by persists across multiple intervals, it may indicate a
Forward Error failure at the source or receiving plug or module, or
Correction exceeds a failure in one of the cables along the path
Day threshold
value. To ensure that the condition is reported only under
TAG-RESET (Tag Error Count Reset)

Table 674: TAG-RESET (Transient Condition)
CH1 The Tag Errors counter was This condition is informative and requires
reset. no corrective action.
1In 10TCE-PCN-16GU+AES100G-BSI modules only.
TIFALMRST (Telemetry-Alarm Reset)

Table 675: TIFALMRST (Transient Condition)
MOD The telemetry alarm This condition is informative and no

contacts on the module further action is required.
have been reset.
TIMECHG (Time Change)

Table 676: TIMECHG (Transient Condition)

Corrective Action
COM The local time of day clock value has been This condition is
changed in accordance with a user command. informative and no
This condition is not reported if the time of day further action is
clock is adjusted via values received when the required.
Network Time Protocol is used to synchronize
the local time of day clock to a remote NTP
server.
TNL-RESULT (Tunnel Result)

Table 677: TNL-RESULT (Transient Condition)
Ethernet A tunnel path computation or This condition is informative and no

Tunnel OTN signaling process has further action is required.
Tunnel completed.
WDM Tunnel
WKSWBK (Auto SwitchToWorking)

Table 678: WKSWBK (Transient Condition)
CH The previously This switch occurs automatically due to:

active protection 1 the expiration of a local hold-off timer in the
ETH switch has been case of a revertive protection switching
automatically configuration,
released and the
2 an automatic switch away from the protection
traffic is now
facility initiated by a locally detected condition
carried by the
arising on that facility,
facility designated
as the working 3 a far-end release request signalled from the
member of the peer bidirectionally switched protection group.
protection group. This condition is informative and no corrective
OM
action is needed.
WKSWPR (Auto SwitchToProtect)

Table 679: WKSWPR (Transient Condition)
CH The traffic has This switch occurs automatically due to:

been automatically 1 an automatic switch away from the working
ETH switched from the facility initiated by a locally detected condition
working member of arising on that facility,
the protection
2 a far-end switch request signalled from the
group to the
peer bidirectionally switched protection group.
protection member.
OM action is needed.
Database Change Events

The following conditions are exclusively reported by ADVA Optical Networking FSP
network manager systems (FSP NMS). Whenever database changes or transient events
occur on FSP 3000R7 shelves managed and monitored by FSP NMS, these conditions
are raised.
These conditions are informative and require no further actions.

Note
Condition Corresponding SNMP OID
Name Full Name Probable Cause
ATTVAL-CHG Attribute Value Change A system attribute has neAttributeValueChange

been modified.
CC-ADD Cross-Connect A cross-connection crossConnectionCreation

Created Notification entity has been created.
CC-CHG Cross-Connect Object A cross-connection crsConnObjectChange

Change Notification entity has been
modified.
CC-DEL Cross-Connect A cross-connection crossConnectionDeletion

Deleted Notification entity has been deleted
from the database.
CCL2-ADD Cross-Connection An L2 cross-connection crossConnectionCreation

Layer2 Creation entity has been created Layer2
Notification in the database.
CCL2-DEL Cross-Connection An L2 cross-connection crossConnectionDeletion

Layer2 Deletion entity has been deleted Layer2
Notification from the database.
CRS-CHG Cross-Connection An L2 cross-connection crossConnectionObject

Layer2 Change entity has been ChangeLayer2
Notification modified.
CTRANS-ADD Ctrans Creation A ctrans entity has been ctransEntityCreation

Notification created in the database.
CTRANS-CHG Ctrans Entity Object A ctrans entity was ctransEntityObjectChange

Change Notification reconfigured.
CTRANS-DEL Ctrans Deletion A ctrans entity has been ctransEntityDeletion

Notification deleted from the
database.
ENT-ADD Entity Creation An entity has been entityCreation

ENT-DEL Entity Deletion An entity has been entityDeletion

database.
ENTOBJVAL- Entity Object Value A general entity has entityObjectChange

CHG Change been modified.
An entity representing loopbackChange

the loopback has been
modified.
ENT-STAT Entity State Change A general entity entityStateChange

Notification administrative state has
been modified.
EQ-INS Equipment Inserted Equipment has been equipmentInserted

Notification physically inserted.
EQ-REM Equipment Removed Equipment has been equipmentRemoved

Notification physically removed.
FACATTVAL-CHG Facility Attribute Value A facility attribute has facilityAttributeValueChange

Change been modified.
FFP-FLOW- Ffp Flow Entity Layer2 A flow protection has ffpFlowEntityCreation

ADD Creation Notification been created in the
database.
FFP-FLOW- Ffp Flow Entity Layer2 A flow protection has ffpFlowEntityObjectChange

CHG Change Notification been modified.
FFP-FLOW- Ffp Flow Entity Layer2 A flow protection has ffpFlowEntityDeletion

DEL Deletion Notification been deleted from the
database.
FLOW-ADD Flow Creation A flow entity has been flowEntityCreation

FLOW-CHG Flow Entity Object A flow entity was flowEntityObjectChange

Change Notification reconfigured.
FLOW-DEL Flow Deletion A flow entity has been flowEntityDeletion

database.
L2ENT-STAT Layer2 Entity State An administrative state layer2EntityStateChange

Change Notification changed for an L2
entity.
LCT-NOTIF LCT Notification Local Craft Terminal lctNotification

access was detected.
A remote-connection
attempt to the network
element took place.
LCT-SUM- LCT Summary Local Craft Terminal lctSummaryNotification

NOTIF Notification access was detected
but was presented as a
summary report
because of the
frequency of LCT
accesses. A summary
of the remote-
connection attempts to
the network element
was presented.
NE-STAT Network Element State A network-element neStateChange

Change state has been
modified.
SHELF-ADD Shelf Creation A shelf entity has been chassisCreation

SHELF-DEL Shelf Deletion A shelf entity has been chassisDeletion

database.
SYSTYPE- System Type Change A network-element neSysTypeChanged

CHG Notification system type has been
modified.
TRAPS-ADD Trapsink Creation An entry has been neTrapsinkObjectCreation

Notification added to the trap-
recipient table.
TRAPS-DEL Trapsink Deletion An entry has been neTrapsinkObjectDeletion

Notification deleted from the trap-
recipient table.

FSP 3000r7

Uploaded by

Copyright:

Available Formats

FSP 3000r7

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

FSP 3000r7

Uploaded by

Copyright:

Available Formats

Fiber Service Platform 3000R7

Product Release 16.2

Preparation for Troubleshooting 29

Finding Your Problem - Follow the Light 53

Core Type Channel Modules 95

Enterprise Type Channel Modules 301

Management and Switch Modules 385

Optical Filters (Passive Modules and Shelves) 437

Optical Amplifiers 441

Dispersion Compensation Modules 507

NCU Troubleshooting 509

Control Plane Maintenance and Troubleshooting 543

General Module and Management Configuration 569

Updating Software, Firmware, and Database 601

Performance Management 637

Exchanging Equipment 653

Generating a Support Data File 777

Alarm and Event List 783

Starting with Release 13.1, the System Description and Hardware

• Module and System Specification

l SH1PCS system shelf including connectors

and presents detailed technical specifications.

Provisioning and Operating

Working with Management Tools

Purpose and Scope 16

Purpose and Scope

Please use the Network Element Director (NED) to execute the

Documentation Revision History

Product Document Document Issue Date Description

Issue B February Updated according to the content of this

Issue C May 2009 Added and corrected the section in Chapter

Product Document Document Issue Date Description

Issue B September Updated information about LEDs

9.2 80000008782 Issue A November Updated according to the content of this

Issue B April 2010 Updated LEDs of the Reconfigurable

10.1 80000011730 Issue A September Updated according to the content of this

10.2 80000014008 Issue A October Updated according to the content of this

Issue C March 2011 This issue covers fixes included in

Issue B April 2012 Content improvements in Chapter 12 and

Product Document Document Issue Date Description

11.2 80000020926 Issue A October Updated according to the content of this

Issue B January Updated per R11.2.2, including the

Issue C April 2013 Updated per R11.2.3, including the

Product Document Document Issue Date Description

12.2 80000026932 Issue A December Updated according to the content of this

Issue B January Added client channel card protection-

Product Document Document Issue Date Description

Product Document Document Issue Date Description

13.2 80000029746 Issue A September Updated according to the content of this

Issue B November Implemented these changes:

Issue B May 2015 Added Craft-based steps to provision SCU

Product Document Document Issue Date Description

15.1 80000034146 Issue A September Updated according to the content of this

Issue B October Updated troubleshooting guidelines for the

15.2 80000035929 Issue A January Updated according to the content of this

Issue B January Updated according to the content of this

Issue B August 2016 Added PSU/7HU-DC-HP revision 2.02 to

boldface font Indicates keywords and emphasized words when appearing

blue font Indicates a reference to a chapter, section, figure, table or