Nortel Common Photonic Layer

Fault Management - Alarm Clearing and

Module Replacement
Standard Release 3.2 Issue 1 June 2008

What’s inside...
Trouble clearing strategies
Fault monitoring and diagnostics
Alarm clearing
Module and component replacement
Restart procedures
Recovering from a fiber cut on Stretched Spans
Appendix A: Events and logs

ATTENTION
Clicking on a PDF hyperlink takes you to the appropriate page. If necessary,
scroll up or down the page to see the beginning of the referenced section.

www.nortel.com

323-1661-543 NTT840BE
Nortel Common Photonic Layer
Release 3.2
Publication: Fault Management - Alarm Clearing and Module Replacement
Document Status: Standard
Document Release Date: June 2008

Copyright  2004-2008, Nortel Networks

All Rights Reserved

This document is protected by copyright laws and international treaties. All information, copyrights and
any other intellectual property rights contained in this document are the property of Nortel Networks.
Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the
information contained herein and this document shall not be published, copied, produced or reproduced,
modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or
media.

This information is provided “as is”, and Nortel Networks does not make or provide any warranty of any
kind, expressed or implied, including any implied warranties of merchantability, non-infringement of third
party intellectual property rights, and fitness for a particular purpose.

Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

Printed in Canada
 iii

Contents 0

New in this release vii

New features vii
Other changes viii

Introduction ix
Trouble clearing strategies 1-1
Alarm clearing strategy overview 1-1
Alarm reporting 1-3
Identifying the alarmed entity 1-9
Visual indicator strategy 1-10
Shelf - network element level visual indicators (GMD, UOSC, and DOSC) 1-10
Module visual indicators (all modules) 1-11
Alarm severities 1-14
Alarm clearing priorities 1-15
Alarm hierarchies and masking 1-16

Fault monitoring and diagnostics 2-1

Monitoring network element status from the Craft Interface 2-1
Active Alarms 2-2
Number of alarms and events that can be stored in history 2-3
List of procedures
2-1 Displaying active alarms 2-6
2-2 Displaying active disabled alarms 2-8
2-3 Displaying the alarm history for a network element 2-10
2-4 Displaying the event history for a network element 2-12
2-5 Performing a lamp test from the Craft interface 2-14
2-6 Clearing audible alarms from the Craft interface 2-15
2-7 Clearing audible alarms and performing lamp tests on the GMD, UOSC, or
DOSC manually 2-16
2-8 Displaying and clearing DOC and SOC logs 2-18
2-9 Locating a reflective event 2-20
2-10 Performing fiber work on a Common Photonic Layer system 2-25

Alarm clearing 3-1

List of procedures
3-1 Adjacency Far End Not Discovered (538) 3-6

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
iv Contents

3-2 Adjacency Mismatch (539) 3-9

3-3 Adjacency Provisioning Error (707) 3-12
3-4 All Provisioned RADIUS servers Unavailable (582) 3-16
3-5 Automatic Power Reduction Active (542) 3-19
3-6 Automatic Shutoff (590, 942) 3-22
3-7 Automatic Shutoff Disabled (943, 1035) 3-24
3-8 Autoprovisioning Mismatch (60) 3-27
3-9 Channel Controller: Failure Detected (709) 3-29
3-10 Channel Controller: Unexpected Loss Detected (877) 3-33
3-11 Circuit Pack Failed (581) 3-38
3-12 Circuit Pack Mismatch (580) 3-40
3-13 Circuit Pack Missing (579) 3-44
3-14 Circuit Pack Unknown (58) 3-47
3-15 Circuit Pack Upgrade Failed (124) 3-49
3-16 COLAN 1 Port Failure (546) 3-51
3-17 Cross-connection Mismatch (863) 3-53
3-18 Database Integrity Fail (8) 3-55
3-19 Database Not Recovered (561) 3-56
3-20 Database Restore in Progress (143) 3-59
3-21 Database Save and Restore Failed (144) 3-60
3-22 DHCP Client Address Rejected (544) 3-62
3-23 Disk 75 percent Full (374) 3-63
3-24 Disk Full (146) 3-64
3-25 DOC Action: Channel Add in Progress (875) 3-65
3-26 DOC Action: Channel Delete in Progress (876) 3-66
3-27 DOC Action: Fault Detected (873) 3-67
3-28 DOC Action Failed: Add (576) 3-71
3-29 DOC Action Failed: Delete (577) 3-74
3-30 DOC Action Failed: Monitor (549) 3-77
3-31 DOC Action Failed: Optimize (550) 3-81
3-32 DOC Consecutive Re-Opt Threshold Crossed (874) 3-85
3-33 DOC Domain Not Optimized (551) 3-88
3-34 DOC Invalid Photonic Domain (552) 3-90
3-35 Duplicate IP Address (545) 3-94
3-36 Duplicate Primary Shelf (714) 3-96
3-37 Duplicate Site ID (871) 3-98
3-38 Duplicate Shelf Detected(70) 3-101
3-39 Fan Failed (592) 3-103
3-40 Fan Missing (593) 3-105
3-41 Fiber Type Manual Provisioning Required (907) 3-107
3-42 Flash Banks Mismatch (222) 3-108
3-43 Gauge Threshold Crossing Alert Summary (724, 725, 726) 3-110
3-44 Group Input Loss Of Signal (712) 3-117
3-45 Group Output Loss Of Signal (713) 3-120
3-46 Group Loss of Signal (710, 832) 3-122
3-47 High Temperature (596) 3-125
3-48 ILAN 1 Port Failure (547) 3-127
3-49 ILAN 2 Port Failure (548) 3-129
3-50 Incoming Network Access Violation (268) 3-131
3-51 Incomplete Software Lineup (92) 3-132

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Contents v

3-52 Input Loss Of Signal (557) 3-134

3-53 Internal Mgmt Comms Suspected (438) 3-137
3-54 Intrusion Attempt (267) 3-139
3-55 Invalid Site Topology (872) 3-141
3-56 Loss Of Signal (553, 560) 3-143
3-57 Member Shelf Unknown (719) 3-146
3-58 Member Shelf Unreachable (717) 3-149
3-59 Optical Line Fail (610, 541) 3-152
3-60 OSC Link Failed (555) 3-155
3-61 OSC Loss Of Signal (556) 3-157
3-62 OSC Signal Degrade (711) 3-160
3-63 OSPF Area Exceeded (543) 3-163
3-64 Output Loss Of Signal (572) 3-164
3-65 Packet Rate Limit Exceeded (591) 3-167
3-66 Power Failure - A (594) 3-169
3-67 Power Failure - B (595) 3-171
3-68 Primary RADIUS Server Unavailable (583) 3-173
3-69 Primary Shelf Unreachable (716) 3-176
3-70 Provisioning Incompatible (82) 3-179
3-71 Raman Failed To Turn On (944) 3-181
3-72 Save Release In Progress (867) 3-182
3-73 Secondary RADIUS Server Unavailable (584) 3-183
3-74 Shelf Data Error (571) 3-186
3-75 Shelf Data Missing (570) 3-189
3-76 Shutoff Threshold Crossed (540) 3-190
3-77 Shutoff Threshold Crossed (940) 3-192
3-78 Software Auto-Upgrade Failed (440) 3-194
3-79 Software Auto-Upgrade in Progress (439) 3-195
3-80 Software Configuration Unknown (138) 3-197
3-81 Software Delivery Incomplete (453) 3-199
3-82 Software Delivery In Progress (454) 3-200
3-83 Software Mismatch (75) 3-201
3-84 Software Upgrade Failed (71) 3-203
3-85 Software Upgrade in Progress (74) 3-204
3-86 TOD Server Not Provisioned (575) 3-205
3-87 Transport Data Recovery Failed (76) 3-207
3-88 Unable to Synchronize TOD (336) 3-208
3-89 Wavelength Measurement Error (879) 3-210
3-90 Wavelength Measurement Warning (878) 3-212
3-91 WAYSIDE 1 Port Failure (573) 3-214
3-92 WAYSIDE 2 Port Failure (574) 3-216

Module and component replacement 4-1

List of procedures
4-1 Replacing the amplifier module 4-4
4-2 Replacing the CMDA module 4-9
4-3 Replacing the CMD44 module with the equivalent CMD44 4-14
4-4 Replacing the CMD4 module with the equivalent CMD4 4-19
4-5 Replacing the CMD4 module with the SCMD4 module 4-24

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
vi Contents

4-6 Replacing the CMD4 module with the SCMD8 module 4-29
4-7 Replacing an Open SCMD8 module with a Filtered SCMD8 module 4-35
4-8 Replacing an MLA module with an MLA2 module or an MLA2 module with an
MLA module 4-40
4-9 Replacing the DOSC module 4-47
4-10 Replacing the GMD module 4-58
4-11 Replacing the OPM module 4-69
4-12 Replacing the SCMDx module 4-73
4-13 Replacing the UOSC module 4-78
4-14 Replacing the WSS module 4-89
4-15 Replacing a DSCM contained within a Fiber Manager 4-94
4-16 Replacing the DRA module with the equivalent DRA 4-99
4-17 DOC settings when replacing equipment subtending to the Common Photonic
Layer network element 4-104
4-18 Replacing the fan assembly in an amplifier 4-105
4-19 Replacing the fan assembly in a UOSC, GMD, or DOSC 4-108
4-20 Replacing air filters 4-110
4-21 Replacing a patch panel for attenuator fix pads 4-112

Restart procedures 5-1

List of procedures
5-1 Performing a module warm restart 5-3
5-2 Performing a module cold restart 5-5
5-3 Restarting on the UOSC, GMD, or DOSC using the reset button 5-7
5-4 Performing a power cycle 5-8

Recovering from a fiber cut on Stretched Spans 6-1

List of procedures
6-1 Recovering from a fiber cut on a Stretched Span (no Raman amplification)
6-2
6-2 Recovering from a fiber cut on a Stretched Span with Raman amplification
6-5

Appendix A: Events and logs 7-1

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 323-1661-543
vii

New in this release 0

The following sections describe what is new in the Common Photonic Layer
Fault Management - Alarm Clearing and Module Replacement for Release
3.2:
• New features
• Other changes

New features
The following are feature changes in Release 3.2 that affect this NTP:
• CMD44 50 GHz—The Channel Mux/Demux 44 (CMD44) 50 GHz (Red
and Blue) are new hardware modules that provide wavelength add/drop
granularity for up to 44 50 GHz channels on a per module basis. The
modules allow from one to 88 channels to be added/dropped/passed
through at each node.
• CMDA—The Channel Mux/Demux Amplifier (CMDA) is a new hardware
module that provides amplification in the demux path and
multiplexes/demultiplexes signals to/from the CMD44 (50 GHz and
100 GHz) modules to support 88 channels.
• Extended Raman support—In Release 3.2, Distributed Raman Amplifiers
(DRA) can operate in two shutoff modes, local (as per Release 3.1) and
managed. The managed mode uses different Automatic Line Shut Off
(ALSO) conditions to shut off amplifiers and DRAs and extends the span
loss.
Ultra long reach applications require alternative OSC routing and manual
channel turn-up/recovery procedures.

• Interior SLA control—Before Release 3.2, SLAs were allowed between the
Pre-amp and WSS at ROADMs and between the Pre-amp and GMD at
GOADMs, but these interior SLAs were used in a set-and-forget mode (no
DOC control). Release 3.2 includes enhancements that allow the interior
SLAs to be controlled by DOC.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
viii New in this release

• Differential provisioning—Differential provisioning allows traffic with

different transmission characteristics to be grouped together and
controlled with a different peak power target. Differential provisioning
allows groups (or classes) of channels to be prioritized to achieve a
different relative OSNR to other channels.
• Fiber pinch detection—A new fiber pinch detection feature is introduced
that detects fiber pinch conditions at various places in the Common
Photonic Layer network and raises the “DOC Action: Fault Detected”
alarm.

Other changes
The following other changes were made to the Common Photonic Layer Fault
Management - Alarm Clearing and Module Replacement for Release 3.2:
• The procedures to replace GMD, DOSC, and UOSC modules have been
updated.
• Procedures have been added to recover from a fiber cut on Stretched
Spans (with or without Raman amplification).

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 323-1661-543
ix

Introduction 0

This document contains information on how to troubleshoot and clear alarms

for a Nortel Common Photonic Layer system.
Navigation
• “Trouble clearing strategies”
• “Fault monitoring and diagnostics”
• “Alarm clearing”
• “Module and component replacement”
• “Restart procedures”
• “Appendix A: Events and logs”

Sorting tables in Craft and Site Manager

In addition to supporting sorting table rows in ascending or descending
alphanumerical order, some of the tables in the Craft interface and Site
Manager support the sorting of table rows by up to three columns (sort within
a sorted list).

Rows are sorted alphanumerically, with the following exception of items in the
Date and Time columns, which are sorted by date and then time.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
x Introduction

Where applicable, the Sort Table dialog box is opened by right-clicking on a

header in the table. The Sort Table dialog box has the following fields and
buttons.

Field/Button Description

Sort by Select the parameter (column) and the sort order for the first
(primary) sort parameter.

Then by (first Select the parameter (column) and the sort order for the
instance) second sort parameter. If these fields are disabled, you
cannot sort by two columns.

Then by (second Select the parameter (column) and the sort order for the third
instance) sort parameter. If these fields are disabled, you cannot sort
by three columns.

OK Click this button to sort the table and to close the dialog box.

Apply Click this button to sort the table rows and keep the dialog
box open.

Cancel Click this button to close the dialog box without sorting the
table rows.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 323-1661-543
1-1

Trouble clearing strategies 1-

In this chapter, CMD44 refers to both CMD44 100 GHz and CMD44 50 GHz,
unless otherwise specified.

Common Photonic Layer hardware and software perform automatic fault

detection and identification. When faults are detected, the network element
issues autonomous alarms, activates office alarms, and displays alarms
through light-emitting diodes (LED).

The trouble clearing strategy is based on the assumptions that:

• No external problem causes the alarm, such as power fluctuation.
• The network element is initially provisioned correctly and works until the
time of the alarm.

Alarm clearing strategy overview

The following steps make up the strategy for fault and alarm clearing:
1 Detect the fault.
— see “Alarm reporting” on page 1-3
2 Identify the entity and network element that raised the alarm.
— see “Identifying the alarmed entity” on page 1-9
3 Check for illuminated Fail indicator LEDs on the modules.
— see “Module visual indicators (all modules)” on page 1-11
4 Perform the module replacement procedure if a Fail LED is illuminated.
— see Chapter 4, Module and component replacement
5 Retrieve alarm messages through the Craft interface if no Fail LEDs are
illuminated.
— see Chapter 2, Fault monitoring and diagnostics
6 Identify alarm severity and priority.
— see “Alarm severities” on page 1-14 and “Alarm clearing priorities” on
page 1-15

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
1-2 Trouble clearing strategies

7 Perform trouble-clearing procedures.

— see Chapter 3, Alarm clearing
8 Repeat the process until all alarms are addressed or cleared.
This fault clearing strategy is illustrated as a flowchart in Figure 1-1.

Figure 1-1
Fault clearing strategy
CPL0095t

Alarm
detected

Yes Press ACO

Audible ?
button
No

Replace Yes
module Module failed

No

Local login

Retrieve
alarms

ID faults
&
severity

Complete alarm
clearing
procedures

Alarm
detected Yes

No

End

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Trouble clearing strategies 1-3

Alarm reporting
Common Photonic Layer network elements report alarms through:
• alarm LEDs on the modules
• alarm messages retrieved through the Craft interface or TL1 messages
• office alarms (optional)

Shelf level alarm correlation

Shelf level correlation (SLC) allows for optical alarm suppression within a shelf
based on the fiber interconnections. Alarm suppression reduces the number
of sympathetic loss of signal alarms resulting from the same root cause and it
facilitates the isolation of the fault.

Suppression of loss of signal alarms occurs for all downstream facilities that
contain the same number or fewer number of channels than the facility at
which the fault is first detected in the system. For example, a failure at a line
level suppresses alarms for all downstream GMD, WSS, OPM, and
CMD/SCMD facilities where possible. However, a failure at a SCMD/CMD and
GMD interconnect only suppresses downstream alarms for facilities that
contain the same number of channels as where the fault was detected. After
other channels have been muxed into the line, the alarm suppression stops.
See Figure 1-2, Figure 1-3, Figure 1-4, and Figure 1-5 for examples of SLC at
various site types.

The alarm masking or suppression occurs within 2.5 seconds of the fault
being detected, no alarm toggling is seen.

Secondary states which indicate facility failures are not affected by SLC
masking. A facility on which a masked fault exists will still report its secondary
state as FAF, for example.

SLC is also responsible for suppression of sympathetic alarming during an

automatic line shutoff (ALSO) condition. The faults used in ALSO declaration
(which is indicated by the Optical Line Fail and the Automatic Shutoff
conditions) are masked by SLC so that one alarm is raised for one failure.

With SLC you can end up with an alarm-free NE. This state occurs when the
root alarm is masked by AINS mode or by the facility being OOS, which masks
all of the downstream alarms. The Circuit Pack Fail alarm and alarms that
have been disabled through alarm provisioning can also make an NE appear
alarm-free, when in fact it is not. See Figure 1-6 for the alarm masking layers.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
1-4 Trouble clearing strategies

Figure 1-2
Shelf level alarm correlation at a TOADM site
CPL0330p

Optical Line Fail

alarm is raised
UOSC UOSC

OSC OSC

Amplifier box Loss of Signal alarm Amplifier box

is suppressed
DSCM DSCM
(optional) (optional)

SCMD4 SCMD4

M M
u u
x x

D D
e e
m m
u u
x x Input
Loss of Signal
alarm is raised
Loss of Signal alarm M
u
M
u
is suppressed x x

D D
e e
m m
u u
x x

M M
u u
x x

D D
e e
m m
u u
x x

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Trouble clearing strategies 1-5

Figure 1-3
Shelf level alarm correlation at a ROADM site
CPL0331p

Loss of Signal alarm

is suppressed Loss of Signal
alarm is raised
uni OSC uni OSC

Optical Line Fail OPM

OSC OSC
alarm is raised

WSS WSS
MLA/MLA2 MLA/MLA2
Out 2 1 In
Switch 1
Switch 1 In 1 2 Out
11 Common Common 12
In Out 4 3 In Out
Switch 2 In 3 4 Out
Switch 2

Out 6 5 In
Switch 3 In 5 Switch 3
6 Out

Out 8 7 In
Switch 4
Switch 4 In 7 8 Out
12 Common Common 11
Out 10 9 In In
Out
Switch 5 In 9 10 Out Switch 5

SCMD4 SCMD4

D
M
u
e
m
Loss of Signal
x u
x alarm is raised

D
e M
m u
u x
x

SCMD8 SCMD8

FT 16GHz
Mux Demux

16GHz FT
Demux Mux

Loss of Signal alarm

is suppressed

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
1-6 Trouble clearing strategies

Figure 1-4
Shelf level alarm correlation at a GMD based OADM site
CPL0470p

Optical Line Fail

(Input Loss of Signal)
(Shutoff Threshold Crossed)
(Output Loss of Signal)
GMD (Type 2) GMD (Type 2)
(Loss of Loss of
Signal) Signal

Amplifier Amplifier box

Loss of
A OSC Signal OSC A

Cut
B B

SCMD8 SCMD8

FT 16GHz
Mux Demux

Group 1 Group 1
16GHz FT
Demux Mux

SCMD8 SCMD8
(Loss of
Signal) Loss of
FT 16GHz
Mux Demux
Signal
Group 2 Group 2
16GHz FT
Demux Mux

SCMD8 SCMD8
(Loss of Cut
Signal) FT
Mux
16GHz
Demux

Group 3 Group 3
16GHz FT
Demux Mux

(Loss of
Signal)

Legend
Alarm raised
(Alarm masked)

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Trouble clearing strategies 1-7

Figure 1-5
Shelf level alarm correlation at a line amp site
CPL0469p

(Loss of
Signal)

Optical Line Fail DOSC

(Input Loss of Signal)
(Shutoff Threshold Crossed) OSC OSC
(Output Loss of Signal) (Loss of
Signal)
SLA SLA

Cut
A

Legend
Alarm raised
(Alarm masked)

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
1-8 Trouble clearing strategies

Figure 1-6
Alarm masking layers
CPL0466p

Alarm provisioning
(enabled or disabled)

Equipment Facility AINS &

Primary State Primary State

Shelf Level Correlation

Fault reporting diagnostics (SNMP/IPC)

Subtending Card/Module

is masked by

Simple Network Management Protocol (SNMP)

Common Photonic Layer supports simple network management protocol
(SNMP) traps for all Common Photonic Layer alarms. For more information on
SNMP supported functionality and procedures, see Planning Guide,
NTT840FE, and Configuration, 323-1661-310.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Trouble clearing strategies 1-9

Identifying the alarmed entity

When an alarm is generated and displayed in the Craft interface, the alarmed
entity is identified in the Unit field. Table 1-1 provides information on how to
interpret the information provided in the Unit field.

Table 1-1
Alarmed entity formats

Alarm class Format(s) Values (see Note 4)

(see Note 1 to Note 3)
Adjacency Facility (ADJ) ADJ-shelf-slot-port ADJ-[1...20]-[1...3,5...13]-[3...10]
Amplifier Facility (AMP) AMP-shelf-slot-port AMP-[1...20]-[1...3,5...13]-[6,8]
Common to Shelf (COM) GMD-shelf-slot GMD-[1...20]-4
DOSC-shelf-slot DOSC-[1...20]-4
UOSC-shelf-slot UOSC-[1...20]-4
SLOT-shelf SLOT-[1...20]-[1...13]
COLAN-shelf-port COLAN-[1...20]-1
ILAN-shelf-port ILAN-[1...20]-[1,2]
WAYSIDE-shelf-port WSC-[1...20]-[1,2]
Domain Optical Control DOC-shelf-slot DOC-[1...20]-4
(DOC)
Environmental (ENV) ENV-shelf-port ENV-[1...36]-[1,2]
Equipment (EQPT) GMD-shelf-slot GMD-[1...20]-4
DOSC-shelf-slot DOSC-[1...20]-4
UOSC-shelf-slot UOSC-[1...20]-4
LIM-shelf-slot LIM-[1...20]-[1...3,5...13]
CMD4-shelf-slot CMD4-[1...20]-[1...3,5...13]
CMD8-shelf-slot CMD8-[1...20]-[1...3,5...13]
OPM-shelf-slot OPM-[1...20]-1
WSS-shelf-slot WSS-[1...20]-3
UNKNOWN-shelf-slot UNKNOWN-[1...20]-[1...3,5...13]
CMDA-shelf-slot CMDA-[1...20]-[1...3,5...13]
DRA-shelf-slot DRA-[1...20]-[1...3,5...13]
OPTMon Facility OPTMON-shelf-slot-port OPTMON-[1...20]-[1...13]-[2...5,7,9,23]
(OPTMON) OPTMON-[1...20]-[1...3,5...13]-[6,8]
OSC Facility (OSC) OSC-shelf-slot-port OSC-[1...20]-4-[1,2,21]
RAMAN Facility RAMAN-shelf-slot-port RAMAN-[1...20]-[1...3,5...13]-[4]

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
1-10 Trouble clearing strategies

Table 1-1 (continued)

Alarmed entity formats
Alarm class Format(s) Values (see Note 4)
(see Note 1 to Note 3)
Security (SECU) GMD-shelf-slot GMD-[1...20]-4
DOSC-shelf-slot DOSC-[1...20]-4
UOSC-shelf-slot UOSC-[1...20]-4
VOA Facility (VOA) VOA-shelf-slot-port VOA-[1...20]-[1...3,5...13]-[1,3,5,7,9,11,13,15,17]
VOA-[1...20]-[1...3,5...13]-[6,8]
Note 1: There are 13 provisionable slots in a Channel Access network element and 12 provisionable
slots in a Line Amplifier. In a Channel Access network element the Group Mux/Demux (GMD) is always
located in slot 4. In a Line Amplifier the Dual Optical Service Channel (DOSC) is always located in
slot 4. In a Thin OADM or a Reconfigurable OADM network element, the Uni Optical Service Channel
(UOSC) is always located in slot 4.
Note 2: Typically, Channel Mux/Demux (CMD4/SCMDx) modules are located in slots 5 to 13,
amplifiers are located in slots 1, 2 and 3, the OPM is located in slot 1, and the WSS is located in slot 3.
Note 3: Typically, the shelf values restart at 1 for each site. For example, a 3-way branch site would
have NEs with shelf values of 1, 2, and 3.
Note 4: In the Values column, an entry like [1...20] indicates that the shelf value is any number from
1 to 20.

Visual indicator strategy

Shelf - network element level visual indicators (GMD, UOSC, and DOSC)
The GMD, UOSC, and DOSC include a number of LEDs to provide alarm
indications for the entire network element. Table 1-2 summarizes these
alarms.

Table 1-2
GMD, UOSC, and DOSC network element alarm LED behavior

LED name or Shape Color Function

Description

Critical Rectangle Red ON when a network element level Critical alarm is active.
Typically, this is for a module fail alarm on a module
subtending from the GMD, UOSC, or DOSC.

Major Rectangle Red ON when a network element level Major alarm is active.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Trouble clearing strategies 1-11

Table 1-2 (continued)

GMD, UOSC, and DOSC network element alarm LED behavior

LED name or Shape Color Function

Description

Minor Rectangle Yellow ON when a network element level Minor alarm is active.

ACO/Lamp Test Circle Clear ON or active when the ACO push button is in the active
or engaged position. This LED is cleared or OFF when
either the ACO push button is disengaged or the GMD,
UOSC, or DOSC re-writes the ACO push button position
to the disengaged inactive state.

LED on the RJ-45 Rectangle Green ON when there is an active Ethernet connection.
connectors, If there is an active physical connection to the Craft port
present on all and the Craft LAN port is deleted (DLT-LAN), the RJ-45
Ethernet ports (for LED for the Craft Ethernet Port remains lit (green).
example, Craft,
COLAN, ILAN)

Module visual indicators (all modules)

Each module includes LEDs to identify its status and operating condition.
These LEDs are described in Table 1-3.

Table 1-3
Module LED overview

LED name Shape Color Visible through Function

the door

Fault Triangle Red Yes ON when module fails; ON temporarily while

See Note 2 module powers up.

Active Rectangle Green Yes ON while module is operating normally; flashes

See Note 2 while the module is initializing or rebooting
(after soft and hard resets).

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
1-12 Trouble clearing strategies

Table 1-3 (continued)

Module LED overview

LED name Shape Color Visible through Function

the door

Fan Fail Fan shape Red Yes ON when either one or more fans have failed
See Note 1 (that is, rotor has stopped) or the fan
point-of-use power supply (PUPS) has failed.
This indicator is visible with the door closed to
assist in fault location and facilitates the rapid
replacement of the fan assembly.

LOS (master) Circle Yellow Yes This LED is active based on the OR’ing of all
facility LOS indications for that module, as
described in Table 1-4.

Note 1: The Fan Fail LED is on the GMD, UOSC, DOSC, SLA, MLA, MLA2, LIM, and CMDA.
Note 2: A powered-up CMD or SCMD that is not connected by Ethernet to the UOSC or GMD
auto-restarts every 10 minutes. This behavior is normal and expected. While the CMD or SCMD is not
connected, the red LED active and the green LED will flash every 10 minutes indicating the restart. After
the Ethernet connection between the CMD/SCMD and the GMD/UOSC is established, the auto-restarts
will stop.

Table 1-4 presents the loss of signal (LOS) LEDs and their functionality on a
per-module basis. These LEDs can be seen when the front cover of the
module is opened.

Table 1-4
LOS LED overview (per module)

Module Port Name (LOS # and port #) Comment

GMD Grp1 In (1), Grp2 In (3), Grp3 In (5), Grp4 In ON when the provisioned LOS threshold
(7), Grp5 In (9), Grp6 In (11), Grp7 In (13), has been exceeded at the corresponding
Grp8 In (15), Grp9 In (17) group input to Group Mux

Common In (22) ON when the provisioned LOS threshold

has been exceeded at the common input
to Group Demux

OSC1 In (21) ON when the OSC_1 is not present

CMD4 Ch1 In (3), Ch2 In (5), Ch3 In (7), Ch4 In (9) ON when the provisioned LOS threshold
has been exceeded at the corresponding
channel input to Channel Mux

Common In (1) ON when the provisioned LOS threshold

has been exceeded at the corresponding
input to Channel Demux

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Trouble clearing strategies 1-13

Table 1-4 (continued)

LOS LED overview (per module)

Module Port Name (LOS # and port #) Comment

SCMD4 Ch1 In (3), Ch2 In (5), Ch3 In (7), Ch4 In (9) ON when the provisioned LOS threshold
has been exceeded at the corresponding
channel input to Channel Mux

Common In (1) ON when the provisioned LOS threshold

has been exceeded at the corresponding
input to Channel Demux

SCMD8 Ch1 In (3), Ch2 In (5), Ch3 In (7), ON when the provisioned LOS threshold
Ch4 In (9), Ch5 In (11), Ch6 In (13), has been exceeded at the corresponding
Ch7 In (15), Ch8 In (17) channel input to Channel Mux

Common In (1) ON when the provisioned LOS threshold

has been exceeded at the corresponding
input to Channel Demux

Upgd In (19) ON when the provisioned LOS threshold

has been exceeded at the corresponding
input to the group level Upgrade In port

CMDA Common In (5) ON when the provisioned LOS threshold

Common Out (6) has been exceeded at the corresponding
input to channel Mux or Demux

DOSC OSC1 In (1) ON when the OSC_1 input is not present

OSC2 In (2) ON when the OSC_2 input is not present

UOSC OSC1 In (1) ON when the OSC_1 input is not present

SLA, MLA, OSC A Out (4) ON when the provisioned LOS threshold
MLA2, LIM has been exceeded on the OSC_A Out
port 4.

Line B (6), Line A (8) ON when the provisioned Input LOS

threshold has been exceeded at the
amplifier input.

DRA LINE-A In (4) ON when Raman is in Local mode and the

OSC power on LINE-A input has
exceeded the provisioned LOS threshold

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
1-14 Trouble clearing strategies

Table 1-4 (continued)

LOS LED overview (per module)

Module Port Name (LOS # and port #) Comment

WSS Switch1 In (1), Switch2 In (3), Switch3 In (5), ON when the provisioned LOS threshold
Switch4 In (7), Switch5 In (9) has been exceeded at the corresponding
input to the Switch.

Common In (11) ON when the provisioned LOS threshold

has been exceeded at the corresponding
input from the amplifier.

OPM Mon1 In (1), Mon2 In (2), ON when the provisioned LOS threshold
Mon3 In (3), Mon4 In (4) has been exceeded at the input from the
amplifier.

Lamp tests
Lamp tests provide important diagnostic information. This test allows users to
test the LEDs on Common Photonic Layer modules to ensure that the LEDs
are functioning. Lamp tests can be initiated from the Craft interface, using TL1
(OPR-LAMP-TEST) or directly from the shelf. When the lamp test is
performed, the LEDs must light up. After 30 seconds, the LEDs are restored
to the original state.

One lamp test can be performed at a time. When the lamp test is initiated from
the Craft interface, the test can be performed on all the LEDs in the shelf or
on a single module. When initiated using the ACO/Lamp test button on the
GMD, UOSC, or DOSC, the lamp test is performed on all the LEDs on the
network element.
For information on initiating a lamp test from the Craft interface, see
“Performing a lamp test from the Craft interface” on page 2-14.

For information on initiating a lamp test from the equipment, see “Clearing
audible alarms and performing lamp tests on the GMD, UOSC, or DOSC
manually” on page 2-16.

Alarm severities
Alarm reports always contain a notification code that identifies the alarm
severity, or the code CL to indicate that the fault has been cleared.

The default levels of severity for Common Photonic Layer alarms are major
(M) and minor (m). Users can provision alarms to have a critical (C) severity.

Critical alarms (C)

Critical alarms are the most severe. Critical alarms always indicate a
service-affecting fault.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Trouble clearing strategies 1-15

Major alarms (M)

Major alarms can be service-affecting or non-service-affecting.

Minor alarms (m)

Minor alarms are less severe and are non-service-affecting.

Cleared alarm notification (CL)

The cleared alarm notification code indicates that the fault no longer exists.

Attention: After taking corrective action, wait at least 10 seconds to verify

that an alarm has cleared.

Alarm severity provisioning

Alarm severity provisioning allows you to change the severity that is used
when reporting alarms. Changes in alarm severities are also reflected in the
LEDs of the GMD, DOSC, and UOSC modules. The severity of each alarm
instance is set using the alarm provisioning profiles. Users have the choice
between three predefined alarm severities: minor, major and critical.

Changing the alarm severity affects both existing alarms and any alarm raised
thereafter. When alarm severity is changed for an existing alarm, the alarm
clears and is re-raised with the appropriate new severity. Changing the alarm
status (enabled or disabled) in a profile does not affect alarm severity. The
alarm notification code (SA and NSA) is also not affected by alarm severity
provisioning. Alarm severity changes are effective on the current shelf only.

Alarm profiles are initialized with the default severities, which are defined in
Chapter 3, “Alarm clearing” for each alarm. The severities defined in the
read-only profiles are not editable.

Alarm clearing priorities

Clear alarms in order of severity:
1 critical, service-affecting (SA) alarm
2 major, service-affecting (SA) alarm
3 major, non-service-affecting (NSA) alarm
4 minor, service-affecting (SA) alarm
5 minor, non-service-affecting (NSA) alarm

Attention: One fault can cause more than one alarm. Clear the alarm with
the highest severity, and some other alarms often clear.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
1-16 Trouble clearing strategies

Alarm hierarchies and masking

More than one alarm condition can apply to an entity. Figure 1-7 shows
equipment and facility alarm masking and Figure 1-8 shows optical signal
alarm masking.

The masking shown in Figure 1-7 and Figure 1-8 applies to one specific entity
at a time and is based on default alarm provisioning severities.

The procedures in Chapter 3 of this document are structured to address

possible masked alarms, so, it is important to perform the procedural steps in
the order shown. Performing the steps in order minimizes unnecessary
impacts to traffic and equipment replacements.

When an alarm is masked it is not listed as an alarm in the Active Alarm

window of the Craft interface. Other conditions that can prevent the listing of
an alarm in the Active alarm window include:
• the auto-in-service (AINS) state of a facility, where alarms are not
generated on a facility during the AINS period
• the primary state of an alarm, where alarms are not generated on
out-of-service maintenance (OOS-MA) entities
• The alarm has been disabled.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Trouble clearing strategies 1-17

Figure 1-7
Equipment and facility alarm masking
CPL0618

Slot not
provisioned

All facility alarms

(VOA, OPTmon,
OSC, COLAN, Provisioning
ILAN, WAYSIDE, Incompatible
Circuit Pack Autoprovisioning
AMP, RAMAN) Unknown Mismatch

Circuit Pack
Circuit Pack Circuit Pack Upgrade Circuit Pack
Failed Mismatch Failed Missing

High Fan
Temperature Missing

Power Power Fan

Failure A Failure B Failed

Legend

A B Alarm A is masked by B

Alarm B is masked by A

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
1-18 Trouble clearing strategies

Figure 1-8
Optical signal alarm masking
cpl0093p

Optical Line
Failed

Automatic
Shutoff

Shutoff Threshold Automatic Power OSC Loss

Crossed Reduction Active of Signal

Input Loss Output Loss OSC Signal

of Signal of Signal OSC Link Fail Degrade

Legend

Alarm B is masked by A

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 323-1661-543
2-1

Fault monitoring and diagnostics 2-

This chapter contains fault monitoring and diagnostic procedures.

Monitoring network element status from the Craft Interface

The status bar of the Craft Interface has four sections:
• Communication status field—displays the status of the communication link
to the network element. When communication is lost, the field turns blue
and displays a white question mark.
• Alarm indicator—displays the number of alarms and alarm severity for the
network element.
• Silence button—clears the color from the alarm indicator fields, so the
centers of the fields appear white.
• Command status field—displays the status of the last action performed,
and maintains a list of up to 200 previous actions that you can scroll
through.

The status bar sections are shown in Figure 2-1.

Figure 2-1
Status bar of the Main Common Photonic Layer Craft window

Alarm indicator Silence Command status

Communication buttton
status

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-2 Fault monitoring and diagnostics

The alarm indicator uses a color-coded system to display alarm counts. A

number appears next to each letter to represent the number of alarms of each
type. The letters/color representing alarm severity are shown in Table 2-1. The
colors are also used when displaying alarms in the various alarm applications.

Table 2-1
Alarm status and description

Alarm status Color Description

--C Red the number of critical alarms

--M Red the number of major alarms

--m Orange the number of minor alarms

--w Yellow the number of warning alarms

For information on monitoring network element status using the alarm banner
in Site Manager, see Site Manager Planning and Installation Guide,
323-1661-195.

Silencing alarms
You can use the status bar to silence the counts for all alarms, or for alarms of
a specific severity. Silencing alarm counts clears the color from the alarm
indicator fields, so they appear white. When an alarm is raised after you have
silenced the alarms, the indicator fields once again display the colors
associated with the alarm severity. In this way, silencing alarm counts enables
you to see the changes in alarm counts more clearly.

To silence the alarm count for a specific severity, click on the alarm indicator
field for that severity. To silence all alarm counts, click on the Silence button.

When you silence an alarm count, the center of the alarm indicator field clears
of color. If alarms are present when you silence the alarm count, the border of
the alarm indicator field remains the color of the associated alarm severity, as
shown in Figure 2-2. If no alarms are present when you silence the alarm
count, a colored border is not shown.

Figure 2-2
Status bar with silenced alarm counts

Active Alarms
When the Craft interface is launched for a commissioned network element, the
Active Alarms screen is displayed. You can use the Active Alarms screen to
look at alarm information for the shelf and for general troubleshooting.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-3

Active Alarms is also available under the Faults menu of the Craft.

In Site Manager, the Consolidated Alarms application under the Tools menu
provides alarm information on all network elements you are logged into, or
selected network elements you are logged into.

Number of alarms and events that can be stored in history

There are two logs types on the NE: AO and AO-BROADCAST. AO logs
include Alarm logs, Environmental Alarm Logs, and some Event logs
(Transient Conditions, Standing Conditions, Clears of Standing Conditions).
AO-BROADCAST logs contain other Event logs like Database Changes and
TL1 Command History.

There is a maximum of 5000 AO logs per shelf, which are the most recent
5000 irrespective of type. There is a maximum of 600 AO-BROADCAST logs
per shelf.

The Alarm History in the Craft interface displays the Alarm and Environmental
Alarm logs from the AO buffer. So while there is a maximum of 5000 AO logs
per shelf, in practice, there will be fewer in Alarm History as some of the AO
logs will be Event Logs that are not displayed in the Alarm History window.

The Event History in the Craft interface displays the Event logs from both AO
and AO-BROADCAST. So while there is a theoretical maximum of 5600 per
shelf, in practice there will be fewer displayed as most will be Alarm and
Environmental Alarm logs that are not displayed in the Event History.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-4 Fault monitoring and diagnostics

Procedure list
Table 2-2 lists the procedures in this chapter.

Table 2-2
Fault monitoring and diagnostic procedures
Procedure Page Comments

Fault monitoring

2-1 Displaying active alarms 2-6 This procedure describes how to retrieve, sort,
refresh, print, copy and save the active alarms list.

2-2 Displaying active disabled alarms 2-8 This procedure describes how to retrieve, print, copy
and save a list of active alarms that are raised
against disabled alarm points.

2-3 Displaying the alarm history for a 2-10 This procedure describes how to retrieve, sort, and
network element refresh, print, copy and save the alarm history list.

2-4 Displaying the event history for a 2-12 This procedure describes how to retrieve, sort, and
network element refresh, print, copy and save the event history list.

Diagnostics

2-5 Performing a lamp test from the Craft 2-14 This procedure describes how to perform the lamp
interface test from the Craft interface.

2-6 Clearing audible alarms from the 2-15 This procedure describes how to clear audible
Craft interface alarms using the Craft interface.

2-7 Clearing audible alarms and 2-16 This procedure describes how to clear audible
performing lamp tests on the GMD, alarms and perform lamp tests on hardware.
UOSC, or DOSC manually

2-8 Displaying and clearing DOC and 2-18 This procedure describes how to display DOC and
SOC logs SOC logs for troubleshooting DOC alarms.

2-9 Locating a reflective event 2-20 This procedure describes how to isolate a reflective
event at a site.

2-10 Performing fiber work on a Common 2-25 This procedure describes the measurements that
Photonic Layer system should be taken and adjusted when performing fiber
work on a Common Photonic Layer network element.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-5

Procedures 2-1 to 2-4 describe how to display alarms and events in the Craft
interface. Figure 2-3 summarizes these procedures.

Figure 2-3
Fault monitoring procedures summarized
CPL0110t

X = either Display in Craft

- Active Alarms Faults -> X
- Active Disabled Alarms
- Alarm History
or
- Event History

Display <X> details

"Click anywhere in the row that
contains .... "

Sort <X>
"Click on a column header to
sort the alarms by ... "

No Filter by severity ?
Y = either
- Active Alarms
- Active Disabled Alarms
Yes or
- Alarm History
Filter <Y>
"Hide alarms of a specific
severity from the <Y> list ... "

Refresh
"Click the refresh button ..."

end

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-6 Fault monitoring and diagnostics

Procedure 2-1
Displaying active alarms
Use this procedure to:
• retrieve the active alarms list
• display alarm details
• sort active alarms
• filter active alarms
• update or refresh the active alarms list
• print, copy or save the alarm table

The Active Alarm window in the Craft interface displays Critical, Major, and
minor alarm events for that network element that are enabled.

You can also view active alarms using the Consolidated Alarms application in
Site Manager, which can display the active alarms from all network elements
you are logged into or from selected network elements you are logged into.

Prerequisites
Log into the Craft interface. To log into the network, see Configuration,
323-1661-310.

Procedure steps
Step Action

Displaying active alarms

1 Select Faults->Active Alarms.
The Active Alarms window opens and displays the active alarms according to
your last filter settings and the alarm points that are not disabled.
You can also view active alarms by selecting Tools->Consolidated Alarms in
Site Manager. The Consolidated Alarms application can display the active
alarms from all logged in network elements or for selected logged in network
elements. Use the radio buttons in the Show area to select either all network
elements or selected network elements. If using the Show network elements
option, you can use the Advanced button to open an Advanced Alarm
Resource Filtering dialog box and select individual network elements.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-7

Procedure 2-1 (continued)

Displaying active alarms

Step Action

Displaying alarm details

2 Click anywhere in the row that contains the alarm that you want to see in
detail.
The details area at the bottom of the Active Alarms window displays the
details of the alarm.
You can view the details of only one alarm at a time.
Sorting active alarms
3 Click on a column header to sort the alarms by that column, in ascending
order.
4 Click again on the same column header to sort the alarms in descending
order.
Filtering active alarms
5 Hide alarms of a specific severity from the Active Alarm List by clearing a
severity check box (Critical, Major, minor).
By default, the Active Alarms window displays active alarms of all severities.
6 Display alarms filtered from the list, by selecting the appropriate severity
check box again.
The Active Alarms window updates.
Refreshing the active alarms list
7 To refresh the active alarms, do one of the following:
• Select the Auto refresh check box to update the alarm list automatically.
• Clear the Auto Refresh check box to disable the auto refresh and enable
the Refresh button. Click on the Refresh button.
Saving, copying or printing alarms
8 Use the File menu in the Craft interface to print and save the alarms table.
9 Use the Edit menu in the Craft interface to copy the alarm table to another
application such as Microsoft Excel or a text editor.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-8 Fault monitoring and diagnostics

Procedure 2-2
Displaying active disabled alarms
Use this procedure:
• to retrieve a list of active alarms that are raised against disabled alarm
points
• retrieve detailed information about an alarm
• sort the alarms in this list
• filter the active disabled alarms
• refresh the Active Disabled Alarms window manually
• print, copy or save the alarm table

The Active Disable Alarm window in the Craft interface displays Critical, Major,
and minor alarm events for that network element that are disabled. For
information on how to enable alarm points, see Configuration, 323-1661-310.

Prerequisites
Log into the Craft interface. To log into the network, see Configuration,
323-1661-310.

Procedure steps
Step Action

Display active disabled alarms

1 Select Faults->Active Disabled Alarms.
The Active Disabled Alarms window opens and displays the active disabled
alarms according to your last filter settings and the alarm points that are
disabled.
Display alarm details
2 Click anywhere in the row that contains the alarm that you want to see in
detail.
The details area at the bottom of the Disabled Active Alarms window displays
the details of the alarm.
You can view the details of only one alarm at a time.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-9

Procedure 2-2 (continued)

Displaying active disabled alarms

Step Action

Sort active disabled alarms

3 Click on a column header to sort the alarms by that column, in ascending
order.
4 Click again on the same column header to sort the alarms in descending
order.
Filter active disabled alarms
5 Hide alarms of a specific severity from the Disabled Active Alarm List by
clearing a severity check box (Critical, Major, minor, clear).
By default, the Active Disabled Alarms window displays disabled active
alarms of all severities.
6 Display alarms filtered from the list, by selecting the appropriate severity
check box again.
The Active Disabled Alarms window updates.
Refresh the active disabled alarms list
7 Click on the Refresh button.
The Last Refresh field displays the date (yyyy-mm-dd) and time (hh:mm:ss)
of the most recent update of the Active Disabled Alarms window.
Save, copy or print alarms
8 Use the File menu in the Craft interface to print and save the alarms table.
9 Use the Edit menu in the Craft interface to copy the alarm table to another
application such as Microsoft Excel or a text editor.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-10 Fault monitoring and diagnostics

Procedure 2-3
Displaying the alarm history for a network element
Use this procedure to:
• retrieve the alarm history list
• display alarm details
• sort alarms in the list
• filter alarms in the list
• set the maximum number of alarm entries to display
• refresh the alarms list manually
• print, copy, or save the alarm table

The Alarm History window displays Critical, Major, minor, warning, and
cleared alarm events for that network element. Both enabled and disabled
alarm points are retrieved.

Colors indicate the severity of the alarm and display in the Severity column:
Critical alarms (red), Major (red), minor (orange), warning (yellow), clear (no
color)

Upgrade events are not displayed in the Alarm History window.

Prerequisites
Log into the Craft interface. To log into the network, see Configuration,
323-1661-310.

Procedure steps
Step Action

Display alarm history list

1 Select Faults->Alarm History.
The Alarm History window opens and displays the alarms according to your
last filter settings.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-11

Procedure 2-3 (continued)

Displaying the alarm history for a network element

Step Action

Display alarm details

2 Click anywhere in the row that contains the alarm that you want to see in
detail.
The details area at the bottom of the Alarm History window displays the
details of the alarm.
You can view the details of only one alarm at a time.
Sort alarms
3 Click on a column header to sort the alarms by that column, in ascending
order.
4 Click again on the same column header to sort the alarms in descending
order.
Filter alarms
5 Hide alarms of a specific severity from the Alarm History list by clearing the
appropriate severity check box (Critical, Major, minor, clear).
By default, the Alarm History window displays alarms of all severities.
6 Display alarms filtered from the list, by selecting the appropriate severity
check box again.
The Alarm History window updates.
Set the maximum number of alarm entries to display
7 Use the Maximum entries to display drop-down selector to specify the
maximum number of entries that are displayed.
The default is 500. Other possible values are 1000, 2000, 3000, 4000, ALL.
Refresh the alarm history list
8 To refresh the alarm history, do one of the following:
• Select the Auto refresh check box to update the alarm list automatically.
• Clear the Auto Refresh check box to disable the auto refresh and enable
the Refresh button. Click on the Refresh button.
The Last Refresh field displays the date (yyyy-mm-dd) and time (hh:mm:ss)
of the most recent update of the Alarm History window.
Save, copy or print alarms
9 Use the File menu in the Craft interface to print and save the alarms table.
10 Use the Edit menu in the Craft interface to copy the alarm table to another
application such as Microsoft Excel or a text editor.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-12 Fault monitoring and diagnostics

Procedure 2-4
Displaying the event history for a network element
Use this procedure to:
• retrieve the event history list
• display event details
• sort events
• refresh the event list manually
• print, copy, or save the alarm table

The Event History window displays all non-alarm events that have occurred
for that network element. For a listing of events, see Appendix A: Events and
logs in this document.

Attention: If you are logged in with a level 2 or 3 user privilege code (UPC),
a warning appears stating that the UPC level is not high enough to access
all event logs. All event logs are retrieved for UPC 4 and 5.

Prerequisites
Log into the Craft interface. To log into the network, see Configuration,
323-1661-310.

Procedure steps
Step Action

Display event history list

1 Select Faults->Event History.
The Event History window opens and displays all events.
Display event details
2 Click anywhere in the row that contains the event that you want to see in
detail.
The details area at the bottom of the Event History window displays the
details of the event.
You can view the details of only one event at a time.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-13

Procedure 2-4 (continued)

Displaying the event history for a network element

Step Action

Sort events
3 Click on a column header to sort the events by that column, in ascending
order.
4 Click again on the same column header to sort the events in descending
order.
Refresh the event list
5 Click on the Refresh button.
The Last Refresh field displays the date (yyyy-mm-dd) and time (hh:mm:ss)
of the most recent update of the Event History window.
Save, copy or print events
6 Use the File menu in the Craft interface to print and save the event table.
7 Use the Edit menu in the Craft interface to copy the event table to another
application such as Microsoft Excel or a text editor.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-14 Fault monitoring and diagnostics

Procedure 2-5
Performing a lamp test from the Craft interface
Use this procedure to perform the lamp test from the Craft interface.

Prerequisites
• Use an account with a level 2, 3, 4, or 5 user privilege code (UPC).
• Log into the Craft interface. To log into the network, see Configuration,
323-1661-310.
• You must be at the site to view the results of the test.

Procedure steps
Step Action

1 Select Faults->Lamp Test.

2 Select the slot containing the module that you want to perform the lamp test
on or select ALL to perform the lamp test on the entire shelf.
3 Click on the OK button.
All LEDs on the selected modules light up. After 30 seconds the LEDs are
restored to the original state.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-15

Procedure 2-6
Clearing audible alarms from the Craft interface
Use this procedure to clear audible alarms using the Craft interface.

When the alarm cut-off (ACO) operation is requested on a network element,

audible alarm indications are halted without changing other alarm indications.
The result of this Craft operation is identical to manually pressing the ACO
button on the GMD, UOSC, or DOSC.

Prerequisites
• Use an account with a level 4 or 5 user privilege code (UPC).
• Log into the Craft Interface to perform this procedure. To log into the
network, see Configuration, 323-1661-310.

Procedure steps
Step Action

1 Select Faults->Alarm Cut-Off.

The Alarm Cut-Off confirmation dialog appears.
2 Click Yes to confirm silencing the audible alarm indicators for all
unacknowledged alarms.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-16 Fault monitoring and diagnostics

Procedure 2-7
Clearing audible alarms and performing lamp tests on
the GMD, UOSC, or DOSC manually
Use this procedure to clear audible alarms and perform lamp tests on network
elements. Each network element has relay contacts that allow you to connect
to both visual and audible alarms.

Attention: When you clear an audible alarm, the alarmed LEDs and faults
are not cleared.

Procedure steps
Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage.

Connect the wrist strap to the electrostatic discharge (ESD) jack on the shelf
or module.
2 If you want to Then complete
clear audible alarms using the ACO button on the GMD, step 3 and step 4
UOSC, or DOSC
perform a lamp test using the ACO button on the GMD, step 5 and step 6
UOSC, or DOSC

Clear audible alarms using the ACO button on the GMD, UOSC, or DOSC
3 Locate the network element with the audible alarm.
4 Press the ACO/Lamp test button on the GMD, UOSC, or DOSC once to reset
the audible alarm relays for the network element.
The ACO LED on the GMD, UOSC, or DOSC is lit.
You have completed this procedure.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-17

Procedure 2-7 (continued)

Clearing audible alarms and performing lamp tests on the GMD, UOSC, or DOSC manually

Step Action

Perform a lamp test using the ACO button on the GMD, UOSC, or DOSC
5 Locate the required network element.
6 Press the ACO/Lamp test button on the GMD, UOSC, or DOSC:
• once if there are no audible alarms
• twice, keeping it pressed the second time until all the LEDs turn on, if
there are audible alarms. The first press clears the audible alarms.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-18 Fault monitoring and diagnostics

Procedure 2-8
Displaying and clearing DOC and SOC logs
Use this procedure to retrieve and clear the:
• Domain Optical Controller (DOC) Topology log
• Domain Optical Controller Command log
• Section Optical Control (SOC) Topology Log
• Section Optical Control Command Log

Use these logs to save and print topology information and to trouble shoot the
following DOC alarms:
• DOC Action Failed: Monitor (549)
• DOC Action Failed: Optimize (550)
• DOC Action Failed: Add (576)
• DOC Action Failed: Delete (577)
• DOC Invalid Photonic Domain (552)

Prerequisites
Log into the Craft interface. To log into the network, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Select Facilities->Domain Optical Controller (DOC)

Attention: If this is not a DOC site, a message is displayed stating that this
is not a DOC site and that only ‘Show Logs’ is available on this shelf. Click the
OK button.

The Domain Optical Controller (DOC) window is displayed.

Display DOC logs
2 Click the Show Logs button.
The DOC log file appears in a separate window.
You can save and copy the log file. You can also perform case sensitive text
searched on the log.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-19

Procedure 2-8 (continued)

Displaying and clearing DOC and SOC logs

Step Action

Clear DOC logs

3 If you want to clear the DOC logs from the shelf, click the “Clear DOC Logs”
button on the top menu of the DOC logs window.
A confirmation dialog box displays asking you if you want to delete the DOC
logs at that shelf location.
4 Click OK to delete the DOC logs at that shelf location.
5 Click the Close button (X) to close this window.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-20 Fault monitoring and diagnostics

Procedure 2-9
Locating a reflective event
Use this procedure to locate connector losses or a reflective event at a:
• line amplifier site
• channel access site

In this procedure you will attempt to isolate the connector losses by starting at
the connector that is farthest from the alarmed amplifier and then working
back towards the alarmed amplifier. See Figure 2-4 on page 2-23 for an
example of an alarmed amplifier at a line amplifier site. See Figure 2-5 on
page 2-24 for an example of an alarmed amplifier at a channel access site.

One of the more difficult reflections to locate are those on an amplifier

transmitting into a GMD. You can have instances where the cause of the
reflection is an unterminated connector on the demux ports of the GMD and
other instances where the reflection is caused by unterminated connectors on
the CMD demux ports.

Attention: This procedure involves wrapping optical fiber around a mandrel

to create optical power attenuations. Winding the fiber too tightly will damage
optical fibers and the optical power attenuations can generate additional
alarms on the system.

CAUTION
Risk of laser radiation exposure
If the fiber downstream of the MLA2 Line A output connector
becomes disconnected accidentally while the Amp Auto
Shutoff Disabled feature is active, the radiation at the exposed
fiber can be at hazard level 1M (IEC 60825-2). In this situation,
you must take all safety precautions appropriate to hazard level
1M (IEC 60825-2).

If the fiber upstream of the DRA Line A input connector

becomes disconnected accidentally while the Auto Shutoff
Disabled feature is active, the radiation at the exposed fiber
can be at hazard level 3B (IEC 60825-2). In this situation, you
must take all safety precautions appropriate to hazard level 3B
(IEC 60825-2).

The ORL based APR safety mechanism remains active.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-21

Procedure 2-9 (continued)

Locating a reflective event

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface to perform this procedure. To log into the
network, see Configuration, 323-1661-310.
• Have a network diagram that identifies all connection points at the site of
the alarmed module that can be cleaned.
Procedure steps
Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage.

Connect the wrist strap to the ESD jack on the shelf or module
2 Review the network diagram, and locate the connector that is farthest from
the alarmed amplifier within the site.
3 Wind the optical fiber patch cord attached to the connector (which is farthest
from the alarmed amplifier) four turns around a 15-mm mandrel.
This step checks for high reflection (low return loss) by causing attenuation of
the optical power in the direction back towards the amplifier output.
You can use a screwdriver handle or other similar sized cylinder in place of a
mandrel.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-22 Fault monitoring and diagnostics

Procedure 2-9 (continued)

Locating a reflective event

4 Verify if the alarm clears and select your next step.

If the alarm Then
does not clear and there are more the reflective event is closer to the
optical fiber patch cords before the alarmed amplifier. Locate the next
alarmed amplifier farthest connector from the
alarmed amplifier and go to
step 5.
does not clear and there are no more return to step in the procedure
optical fiber patch cords before the that you were working on
alarmed amplifier at this site (you are
now at the output of the alarmed
amplifier)
clears go to step 6

5 Wind the optical fiber four turns around a 15-mm mandrel (you can use a
screwdriver handle), and return to step 4.
6
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to circuit packs
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical
amplifier is out of service (OOS), then disconnect or
reconnect the fiber.

Place the alarmed optical amplifier out of service (OOS). For information on
how to put the amplifier OOS, see Configuration, 323-1661-310.
7 Clean and then reconnect the output fibers and connectors at the amplifier.
For instructions on inspecting and cleaning optical fiber, see SLAT and
Channel Procedures, 323-1661-221.
8 Place the amplifier back in-service (IS). For information on how to put the
amplifier IS, see Configuration, 323-1661-310.
9 If the alarm Then
clears you have completed this
procedure
does not clear contact your next level of support
or your Nortel support group

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-23

Figure 2-4
Locating connector losses at a Common Phonic Layer Line Amplifier site (with DSCM)
CPL0104p
Automatic Power Reduction Active (APR) alarm

Amplifier Amplifier

DSCM
Patch panel #1

Patch panel #2

Patch panel #3

Patch panel #4
B A
Out In

3 3
DSCM
A 1 B
2 In Out

Legend
Indicates the reflection point (actual problem point in this example).

1 Perform mandrel test on optical fiber patch cord at 1 . In this

example, the APR alarm is not cleared, because the
optical power attenuation is occurring after the reflection point ( ).

2 Backtrack in direction towards alarmed amplifier port. Perform mandrel

test on optical fiber patch cord 2 . In this example the alarm clears
because attenuated optical power is reflected.

3 Clean connectors at 3 on both sides of of the DSCM. Ensure amplifier

is OOS before cleaning connectors.

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

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-24 Fault monitoring and diagnostics

Figure 2-5
Locating connector losses at a Common Phonic Layer Channel Access site
CPL0103t
Automatic Power Reduction Active (APR) alarm

Amplifier
Group Mux/Demux

Line B In Line B In 3 3

Patchpanel #1

Patchpanel #2

Not accessible
B 2 1

Line B Out Line B Out

A

Legend
Indicates the reflection point (actual problem point in this example).

1 Perform mandrel test on optical fiber patch cord at 1 . In this

example, the APR alarm is not cleared, because the
optical power attenuation is occurring after the reflection point ( ).

2 Backtrack in the direction towards the alarmed amplifier port. Perform

mandrel test on optical fiber patch cord 2 . In this example the alarm
clears because attenuated optical power is reflected.

3 Clean connectors at 3 on both sides of patch panel #1. Ensure amplifier

is OOS before cleaning connectors.

Note: If alarm does not clear, problem is likely with patch panel.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-25

Procedure 2-10
Performing fiber work on a Common Photonic Layer
system
Use this procedure to record existing power levels and amplifier gain settings
before performing fiber maintenance/repair and to readjust these parameters
if the fiber maintenance/repair causes power levels to change.

CAUTION
Risk of damage to downstream amplifier
You must complete this procedure on an amplifier that is
downstream of the location where the fiber cut or maintenance
activity will be performed. Not performing this procedure can
result in power levels at the amplifier that are high enough to
damage the module.

CAUTION
Risk of laser radiation exposure
If the fiber downstream of the MLA2 Line A output connector
becomes disconnected accidentally while the Amp Auto
Shutoff Disabled feature is active, the radiation at the exposed
fiber can be at hazard level 1M (IEC 60825-2). In this situation,
you must take all safety precautions appropriate to hazard level
1M (IEC 60825-2).

If the fiber upstream of the DRA Line A input connector

becomes disconnected accidentally while the Auto Shutoff
Disabled feature is active, the radiation at the exposed fiber
can be at hazard level 3B (IEC 60825-2). In this situation, you
must take all safety precautions appropriate to hazard level 3B
(IEC 60825-2).

The ORL based APR safety mechanism remains active.

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface to perform this procedure. To log into the
network, see Configuration, 323-1661-310.
• Have a network diagram that identifies all connection points at the site of
the alarmed module that can be cleaned.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-26 Fault monitoring and diagnostics

Procedure 2-10 (continued)

Performing fiber work on a Common Photonic Layer system

Procedure steps
Step Action

1 Log into the NE containing the amplifier that is downstream of the location
where the fiber cut or maintenance activity will be performed.
2 Select Facility->AMP.
3 Record the Gain.
4 Select Facility -> OSC.
5 Record the OSC Span Loss.
6 Select Performance->Performance Monitoring->New.
7 Retrieve the PMs parameters for the AMP.
8 Record the current (Untimed) Input Power (OPIN).
9 If a DRA module is used on the link, retrieve the PM parameters for the DRA.
Record the current (Untimed) Input Power (OPIN) and OSC Power
(OPROSC).
10 Log into the DOC NE that controls this amplifier and change the DOC
Automation mode to No Automation. See Configuration, 323-1661-310, for
information on setting DOC parameters.
11 Place amplifier downstream of fiber cut/maintenance out-of-service (OOS).
See Configuration, 323-1661-310, for information on placing an amplifier
(facility) OOS.
If a DRA is used on the link, place the DRA modules downstream of fiber
cut/maintenance out-of-service (OOS). See Configuration, 323-1661-310, for
information on placing a RAMAN facility OOS.
12 Perform maintenance/repair fiber according to the safety requirements of
your company and the safety requirements described in Documentation
Roadmap, 323-1661-090.
13 If a DRA is used on the link, place the DRA modules downstream of fiber
cut/maintenance in-service (IS). See Configuration, 323-1661-310, for
information on placing a RAMAN facility IS.
If the DRA is part of a stretched span, see Procedure 6-2, “Recovering from
a fiber cut on a Stretched Span with Raman amplification” on page 6-5, for
information on recovering from the ALSO condition.
14 Log into the NE containing the amplifier that is downstream of the location
where the fiber cut or maintenance activity was performed.
15 Select Facility->AMP.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Fault monitoring and diagnostics 2-27

Procedure 2-10 (continued)

Performing fiber work on a Common Photonic Layer system

Step Action

16 Record the Gain.

17 Select Facility -> OSC.
18 Record the OSC Span Loss.
19 Select Performance->Performance Monitoring->New.
20 Retrieve the PMs parameters for the AMP.
21 Record the current (Untimed) Input Power (OPIN).
22 Retrieve the PM parameters for the DRA.
23 Record the current (Untimed) Input Power (OPIN) and OSC Power
(OPROSC).
24 Compare the current OSC Span Loss recorded in step 18 to the OSC Span
Loss recorded in step 5.
25 Compare current (Untimed) Input Power (OPIN) recorded in step 21 to the
Input Power (OPIN) recorded in step 8 (or you can also use the 1-day Input
Power (OPIN)).
26 If a DRA module is used on the link, compare current (untimed) Input Power
(OPIN) and OSC Power (OPROSC) recorded in step 23 to the powers
recorded in step 9. (Alternatively, you can use the 1-day Input Power [OPIN]
and OSC Power [OPROSC].
27 If OSC span loss has Then
increased by more than 3 dB (or check the fiber splice and fiber
the amplifier or DRA Input Power connections. It is likely that the splice is
[OPIN] or OSC Power poor or there is a dirty connection.
[OPROSC] has decreased by Correct the problem and go to step 28.
more than 3 dB)
decreased by more than 3 dB (or perform steps 1 to 4 to adjust the
the amplifier or DRA Input Power downstream OOS amplifier gain
[OPIN] or OSC Power downwards by the difference in OSC
[OPROSC] has increased by Span Loss. (For example, if the OSC
more than 3 dB) Span Loss has decreased by 4 dB and
the old amplifier gain was 18 dB, the new
amplifier gain will be 18 dB-4 dB=14 dB.)
1 Select Facility -> Amp.
2 Select the amplifier to edit (the one that is
OOS).
3 Click the Edit button.
4 Edit the Target Gain to the new value and
click OK.
5 Go to step 28.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
2-28 Fault monitoring and diagnostics

Procedure 2-10 (continued)

Performing fiber work on a Common Photonic Layer system

Step Action

28 Put the amp downstream of the fiber repair in-service (IS). See Configuration,
323-1661-310, for information on placing an amplifier (facility) IS.
29 Log into the DOC NE that controls this amplifier and change the DOC
Automation mode to Auto Re-Optimization as Necessary or click the
Re-optimize button. See Configuration, 323-1661-310, for information on
setting DOC parameters.
30 Wait for DOC to perform optimization. This may take up to 5 minutes to begin.
31 After optimization is complete, return the DOC Automation mode to the
original setting (mode prior to procedure beginning).
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
323-1661-543
3-1

Alarm clearing 3-

The Common Photonic Layer (CPL) alarm clearing procedures are listed in
this chapter in alphabetical order. Use these alarm clearing procedures to
clear the appropriate alarms that are raised on CPL.

The number next to the alarm name in the clearing procedures is the unique
identifier for that alarm. The unique identifier is not part of the alarm name and
therefore does not appear next to the alarm in the Craft or TL1. However, the
number does appear in one of the fields for that alarm in the CPL TL1 and
Craft.

The User Privilege Codes (UPC) that are indicated in the alarm clearing
procedures are defined in the chapter on user account and security
administration, in Configuration, 323-1661-310.

In this chapter, “CMD44” refers to both CMD44 100 GHz and CMD44 50 GHz,
unless otherwise specified.

Table 3-1 lists the CPL alarm clearing procedures in this chapter.

Table 3-1
CPL alarm clearing procedures

Alarm Procedure Page

Adjacency Far End Not Discovered (538) 3-1 3-6

Adjacency Mismatch (539) 3-2 3-9

Adjacency Provisioning Error (707) 3-3 3-12

All Provisioned RADIUS servers Unavailable (582) 3-4 3-16

Automatic Power Reduction Active (542) 3-5 3-19

Automatic Shutoff (590, 942) 3-6 3-22

Automatic Shutoff Disabled (943, 1035) 3-7 3-24

Autoprovisioning Mismatch (60) 3-8 3-27

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-2 Alarm clearing

Table 3-1 (continued)

CPL alarm clearing procedures

Alarm Procedure Page

Channel Controller: Failure Detected (709) 3-9 3-29

Channel Controller: Unexpected Loss Detected (877) 3-10 3-33

Circuit Pack Failed (581) 3-11 3-38

Circuit Pack Mismatch (580) 3-12 3-40

Circuit Pack Missing (579) 3-13 3-44

Circuit Pack Unknown (58) 3-14 3-47

Circuit Pack Upgrade Failed (124) 3-15 3-49

COLAN 1 Port Failure (546) 3-16 3-51

Cross-connection Mismatch (863) 3-17 3-53

Database Integrity Fail (8) 3-18 3-55

Database Not Recovered (561) 3-19 3-56

Database Restore in Progress (143) 3-20 3-59

Database Save and Restore Failed (144) 3-21 3-60

DHCP Client Address Rejected (544) 3-22 3-62

Disk 75 percent Full (374) 3-23 3-63

Disk Full (146) 3-24 3-64

DOC Action: Channel Add in Progress (875) 3-25 3-64

DOC Action: Channel Delete in Progress (876) 3-26 3-66

DOC Action: Fault Detected (873) 3-27 3-67

DOC Action Failed: Add (576) 3-28 3-71

DOC Action Failed: Delete (577) 3-29 3-74

DOC Action Failed: Monitor (549) 3-30 3-77

DOC Action Failed: Optimize (550) 3-31 3-81

DOC Consecutive Re-Opt Threshold Crossed (874) 3-32 3-85

DOC Domain Not Optimized (551) 3-33 3-88

DOC Invalid Photonic Domain (552) 3-34 3-90

Duplicate IP Address (545) 3-35 3-94

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-3

Table 3-1 (continued)

CPL alarm clearing procedures

Alarm Procedure Page

Duplicate Primary Shelf (714) 3-36 3-96

Duplicate Site ID (871) 3-37 3-98

Duplicate Shelf Detected(70) 3-38 3-101

Fan Failed (592) 3-39 3-103

Fan Missing (593) 3-40 3-105

Fiber Type Manual Provisioning Required (907) 3-41 3-107

Flash Banks Mismatch (222) 3-42 3-108

Gauge Threshold Crossing Alert Summary (724, 725, 726) 3-43 3-110

Group Input Loss Of Signal (712) 3-44 3-117

Group Output Loss Of Signal (713) 3-45 3-120

Group Loss of Signal (710, 832) 3-46 3-122

High Temperature (596) 3-47 3-125

ILAN 1 Port Failure (547) 3-48 3-127

ILAN 2 Port Failure (548) 3-49 3-129

Incoming Network Access Violation (268) 3-50 3-131

Incomplete Software Lineup (92) 3-51 3-132

Input Loss Of Signal (557) 3-52 3-134

Internal Mgmt Comms Suspected (438) 3-53 3-137

Intrusion Attempt (267) 3-54 3-139

Invalid Site Topology (872) 3-55 3-141

Loss Of Signal (553, 560) 3-56 3-143

Member Shelf Unknown (719) 3-57 3-146

Member Shelf Unreachable (717) 3-58 3-149

Optical Line Fail (610, 541) 3-59 3-152

OSC Link Failed (555) 3-60 3-155

OSC Loss Of Signal (556) 3-61 3-157

OSC Signal Degrade (711) 3-62 3-160

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-4 Alarm clearing

Table 3-1 (continued)

CPL alarm clearing procedures

Alarm Procedure Page

OSPF Area Exceeded (543) 3-63 3-163

Output Loss Of Signal (572) 3-64 3-164

Packet Rate Limit Exceeded (591) 3-65 3-167

Power Failure - A (594) 3-66 3-169

Power Failure - B (595) 3-67 3-171

Primary RADIUS Server Unavailable (583) 3-68 3-173

Primary Shelf Unreachable (716) 3-69 3-176

Provisioning Incompatible (82) 3-70 3-179

Raman Failed To Turn On (944) 3-71 3-181

Save Release In Progress (867) 3-72 3-182

Secondary RADIUS Server Unavailable (584) 3-73 3-183

Shelf Data Error (571) 3-74 3-186

Shelf Data Missing (570) 3-75 3-189

Shutoff Threshold Crossed (540) 3-76 3-190

Shutoff Threshold Crossed (940) 3-77 3-192

Software Auto-Upgrade Failed (440) 3-78 3-194

Software Auto-Upgrade in Progress (439) 3-79 3-195

Software Configuration Unknown (138) 3-80 3-197

Software Delivery Incomplete (453) 3-81 3-199

Software Delivery In Progress (454) 3-82 3-200

Software Mismatch (75) 3-83 3-201

Software Upgrade Failed (71) 3-84 3-203

Software Upgrade in Progress (74) 3-85 3-204

TOD Server Not Provisioned (575) 3-86 3-205

Transport Data Recovery Failed (76) 3-87 3-207

Unable to Synchronize TOD (336) 3-88 3-208

Wavelength Measurement Error (879) 3-89 3-212

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-5

Table 3-1 (continued)

CPL alarm clearing procedures

Alarm Procedure Page

Wavelength Measurement Warning (878) 3-90 3-212

WAYSIDE 1 Port Failure (573) 3-91 3-214

WAYSIDE 2 Port Failure (574) 3-92 3-216

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-6 Alarm clearing

Procedure 3-1
Adjacency Far End Not Discovered (538)
Use this procedure to clear the Adjacency Far End Not Discovered (538)
alarm.

This alarm is raised for a line adjacency.

Probable cause
This alarm is raised when the Expected Far End (Line) Address of an
adjacency has been manually provisioned, but this same adjacency cannot be
automatically discovered. Possible reasons why this far end adjacency is not
being discovered include:
• The two adjacency end points have not been fibered.
• The two adjacency end points have been fibered but some other problem
exists with the fiber or connection.
• There is a Comms provisioning error where the OSPF Circuit on OSC is
incorrectly provisioned or not provisioned at one or both ends of the
alarmed span.
• The OSC-1 Amp Slot (or OSC2 for DOSC) provisioning in the Shelf is
different than the actual provisioning (location) of the amplifier.
• An upstream UOSC, DOSC, or GMD has undergone a restart operation.
The alarm will clear after the restart has completed.

In the case of a line adjacency, the discovered provisioned far end address is
the Common Photonic Layer Line Amplifier at the other end of the fiber span.
See Figure 3-1 on page 3-8 for example line adjacency far end addresses.

Impact
minor, NSA (Not service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-7

Procedure 3-1 (continued)

Adjacency Far End Not Discovered (538)

Procedure steps
Step Action

1 Verify and correct the adjacency provisioning information as required. See

the adjacency provisioning chapter in Configuration, 323-1661-310, for
details on how to retrieve and edit adjacencies.
If the alarm did not clear, go to step 2.
2 If this adjacency Then
is fibered, but a fiber break, reflective go to step 3
event, or disconnect is suspected
was provisioned for future use and disable this alarm so that it no longer
you do not want this alarm to be appears in the active alarms list. See
displayed in the active alarm list the fault provisioning section in
Configuration, 323-1661-310.
was provisioned for future use and no action is required. You have
you want this alarm to be displayed in completed this procedure.
the active alarms list for informational
purposes
requires fibering fiber the adjacency end points. See
Installation, 323-1661-201.

3 Clear any alarms that indicate a fiber break or disconnect.

Attention: Alarms that indicate a fiber break or disconnect include:

Automatic Power Reduction Active (542), Automatic Shutoff (590, 942), Input
Loss Of Signal (557), Loss Of Signal (553, 560), Group Input Loss Of Signal
(712), Group Loss of Signal (710, 832), Optical Line Fail (610, 541).

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-8 Alarm clearing

Figure 3-1
Examples of line adjacency far end address
CPL0101t
Site F Site G
MLA MLA
slot 1 slot 2

8 In 5 Out

5 Out 8 In

Legend
Line adjacency ADJ-1-1-5
far end address SiteG-1-2-8
Line adjacency ADJ-1-2-5
far end address SiteF-1-1-8
shelf slot port

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-9

Procedure 3-2
Adjacency Mismatch (539)
Use this procedure to clear the Adjacency Mismatch (539) alarm.

This alarm is raised for a line adjacency or spur [(s)CMD-(s)CMD]

adjacencies.

Probable cause
The following conditions raise this alarm:
• When the Expected Far End Address of an adjacency has been manually
provisioned, and the manually provisioned information does not match the
discovered (Actual Far End Address) address.
• If the provisioned information is correct, mis-fibering can be the cause of
this alarm.
• When the Expected Far End Address of a Tx or Rx Adjacency is another
Common Photonic Layer Network Element that is located at a different site
than the Network Element raising the alarm.

The Adjacency Mismatch alarm is expected on network elements adjacent to

NEs undergoing a TID consolidated reconfiguration. These alarms should
clear after the inter-shelf adjacencies are updated with the NE Name.

In the case of a line adjacency, the discovered provisioned far end address is
the Common Photonic Layer Line Amplifier at the other end of the fiber span.
See Figure 3-2 for examples of line adjacency far end addresses.

Impact
minor, NSA (Not service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Know the correct far end address for the alarmed adjacency.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-10 Alarm clearing

Procedure 3-2 (continued)

Adjacency Mismatch (539)

Procedure steps

Step Action

1 Select Facilities->Adjacency
All of the created adjacencies are listed.
2 Select the alarmed adjacency from the adjacency window. For line
adjacencies, go to step 4.
3 Verify what is the correct far end address using the network planning diagram.
4 If the Actual Far End Address is Then
correct go to step 5
incorrect if a line adjacency, verify that the
line side fiber is correctly
connected according to the
installation documentation. If it is
correctly connected, go to step 18.

5 If the Actual Far End Address Then go to

does not match the Expected End Address step 6
matches the Expected Far End Address step 18

6 Click the Edit button.

7 Use the pull down menus and text fields to edit the Expected Far End Address
and Expected Far End Address Format.
8 Click the OK button.
If the alarm does not clear, go to step 9. Otherwise, you have completed this
procedure.
9 .If a Then go to
Tx\Rx adjacency step 10
Line adjacency step 18

10 For the NE raising the alarm, select Configuration->Node Information->Shelf

Note the listed Site Identifier (ID).
11 For the NE listed in the Expected Far End Address field, select
Configuration->Node Information->Shelf
Note the listed Site ID.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-11

Procedure 3-2 (continued)

Adjacency Mismatch (539)

Step Action

12 If the NEs are at the same physical site, and the Site IDs are Then go to
different step 13
same step 18

13 Verify the correct Site ID for the site.

14 In the NE with the incorrect Site ID, select Configuration->Node
Information->Shelf
15 Select the shelf to change in the Shelf window. Click Edit.
The Edit Shelf window opens.
16 In the Edit Shelf window, change the Site Identifier in the Site ID field.
17 Click OK.
18 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—
Figure 3-2
Examples of line adjacency far end address
CPL0101t

Site F Site G
MLA MLA
slot 1 slot 2

8 In 5 Out

5 Out 8 In

Legend
Line adjacency ADJ-1-1-5
far end address SiteG-1-2-8
Line adjacency ADJ-1-2-5
far end address SiteF-1-1-8
shelf slot port

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-12 Alarm clearing

Procedure 3-3
Adjacency Provisioning Error (707)
Use this procedure to clear the Adjacency Provisioning Error (707) alarm.

Attention: If unpaired channels are to be used, you must provision

inter-shelf adjacencies in both directions. For unpaired Spur channels, you
must provision Tx and Rx adjacencies in both directions.

Probable cause
This alarm is raised when the inter-shelf provisioning is missing and there is
a channel with an optical cross-connect or inter-domain passthrough over that
adjacency or over the paired adjacency in the opposite direction.

The following conditions raise this alarm:

• A passthrough channel is provisioned but the far-end address does not
match the discovered shelf.
• An optical cross-connect or spur connection is provisioned but the far-end
address does not match a shelf at the same site and in a different domain.
• The adjacency type does not match the shelf function (for example, WSS
on a ROADM, GMD on a GOADM, CMD or LIM on a TOADM, TX or RX
for a spur).
• A passthrough channel is provisioned at a TOADM or GOADM, but a CMD
for that same group is provisioned. In a TOADM configuration, the
adjacency corresponding to the CMD channel OUT port for that
wavelength is alarmed. In a GOADM configuration, the adjacency
corresponding to the GMD group OUT port for that group is alarmed.
• A skip channel originating from a CMD44/ROADM is provisioned as
passthrough at a TOADM or GOADM. This channel cannot be optically
passed through the node. For more information on unavailable skip
channels, refer to the table (unavailable 50 GHz channels - TOADMs and
GMDs/GOADMs) in the introduction chapter of the Planning Guide,
NTT840FE.
• If no passthrough adjacency is provisioned on a ROADM, the alarm is
raised against all candidate passthrough ports. The alarm is cleared
against all candidate passthrough ports when a passthrough adjacency is
provisioned.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-13

Procedure 3-3 (continued)

Adjacency Provisioning Error (707)

Impact
minor, NSA (Not service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Have the engineering documentation package (EDP) for shelf details.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps

Step Action

1 If this is a Then go to
ROADM site step 2
TOADM site step 5
GMD-based OADM site step 10
CMD spur connection step 15

2 Verify if the WSS-to-WSS adjacency is provisioned and correct. In particular,

confirm that the provisioned far end address is correct. Select
Facilities->Adjacency.
3 If the WSS-to-WSS adjacency Then go to
has not been manually provisioned or has an error step 4
is provisioned and correct step 18

4 Create or edit the WSS-to-WSS adjacency. See Configuration,

323-1661-310.
Then go to step 18.
5 Verify that the CMD-to-CMD adjacencies at the end of SCMD Cascading
Order are provisioned and correct.
In particular, for inter-shelf adjacencies, confirm that the Upgrade OUT and
Upgrade IN adjacencies for the cascading CMD are provisioned correctly.
Verify that the provisioned far end address is correct. Select
Facilities->Adjacency.
For intra-shelf adjacencies, confirm that the cascading SCMD order is
provisioned correctly. Select the Configuration->SCMD Cascading Order.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-14 Alarm clearing

Procedure 3-3 (continued)

Adjacency Provisioning Error (707)

Step Action

6 If the CMD-to-CMD adjacency at the end of the SCO Then go to

has an error step 7
is provisioned and correct step 18

7 Edit the CMD-to-CMD adjacency. See Configuration, 323-1661-310.

8 Verify that CMDs are not provisioned for the same groups that are intended
to pass through the site. If this occurs, the system will have to be
re-engineered to use a channel that does not drop at this site. See your
EDP/IDP.
9 Verify that a skip channel is not provisioned to pass through this node. If it is,
de-provision the illegal channel and/or re-engineer the network.
Then go to step 18.
10 Verify that the GMD-to-GMD adjacency provisioning for all groups carrying
passthrough traffic is correct. In particular confirm that the provisioned far end
address is correct. Select Facilities->Adjacency.
11 If the GMD-to-GMD adjacency Then go to
has not been manually provisioned or has an error step 12
is provisioned and correct step 18

12 Create or edit the GMD-to-GMD adjacency. See Configuration,

323-1661-310.
13 Verify that CMDs are not provisioned for the same groups that are intended
to pass through the site. If this occurs, the system will have to be
re-engineered to use a channel that does not drop at this site. See your
EDP/IDP.
14 Verify that a skip channel is not provisioned to pass through this node. If it is,
de-provision the illegal channel and/or re-engineer the network.
Then go to step 18.
15 Verify that the CMD-to-CMD adjacency provisioning is correct, the
provisioned far end address is correct, and that the far-end CMD is in a
different OSID. Select Facilities->Adjacency.
16 If the CMD-to-CMD adjacency Then go to
has not been manually provisioned or has an error step 17
is provisioned and correct step 18

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-15

Procedure 3-3 (continued)

Adjacency Provisioning Error (707)

Step Action

17 Create or edit the CMD-to-CMD adjacency. See Configuration,

323-1661-310.
18 If the alarm does not clear, contact Nortel technical support or your next level
of support.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-16 Alarm clearing

Procedure 3-4
All Provisioned RADIUS servers Unavailable (582)
Use this procedure to clear the All Provisioned RADIUS servers Unavailable
(582) alarm. This alarm is raised on a Uni Optical Service Channel (UOSC),
Dual Optical Service Channel (DOSC) or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the remote authentication requests to both the
primary and secondary RADIUS servers expires after a user-provisionable
timeout and no response is received from a RADIUS server. Possible reasons
why the RADIUS server is unavailable include:
• The shared secret provisioned for Centralized Security Authentication
(CSA) on the network element does not match the RADIUS server shared
secret.
• The wrong RADIUS server IP addresses or ports are provisioned on the
network element.
• The network element IP address is not provisioned on the RADIUS server
as a RADIUS client.
• A COLAN or OSC comms problem exists.
• The network delay exceeds the provisioned timeout value.
• UDP packet loss or other network problems prevent communication.

Disabling CSA clears this alarm. An alternate security authentication method

is used for log in and authentication if CSA is disabled or if the RADIUS
servers are unavailable. For more information on user account and security
administration, see Configuration, 323-1661-310.

Impact
Major, NSA (Not service-affecting)

Prerequisites
• Have an account with a level 4 or higher user privilege code (UPC).
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• Know the shared secret.
• Know the IP address of the RADIUS servers.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-17

Procedure 3-4 (continued)

All Provisioned RADIUS servers Unavailable (582)

Procedure steps
Step Action

1 Verify if any of the following alarms are active, and clear them using the
procedures in this document:
• COLAN 1 Port Failure (546)
• ILAN 1 Port Failure (547)
• ILAN 2 Port Failure (548)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)

If the alarm remains active, go to step 2.

2 Select Security->Centralized Security Administration.
3 Select the Primary or Secondary server from the list.
4 Click on the Edit Server button.
5 Verify the IP addresses of the RADIUS Servers are correct and re-enter if
required.
6 Verify the port number in the Port Number field is correct and re-enter if
required.
The port number is the UDP port number of the RADIUS server.
7 Increase the timeout value in the Timeout Value field.
The timeout value is the amount of time (in seconds) that is allowed for
communication to occur between the controller and RADIUS server. The
timeout value can range between 1 and 30 seconds.
8 Click OK if any changes were made in step 5 to step 7.
If the alarm remains active, go to step 9.
9 Return to the Centralized Security Administration window.
10 Click the Set NE Shared Secret button.
11 Enter the shared secret in the Shared Secret field.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-18 Alarm clearing

Procedure 3-4 (continued)

All Provisioned RADIUS servers Unavailable (582)

Step Action

12 Re-enter the shared secret in the Shared Secret (confirmed) field.

13 Click OK.
14 Repeat step 3 to step 13 on the other RADIUS Server.
15 If the alarm does not clear, contact your network administrator to verify that
the IP address of the network element has been added to the RADIUS server
and to correct any networking issues.
Use your RADIUS server documentation to troubleshoot possible RADIUS
server issues.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-19

Procedure 3-5
Automatic Power Reduction Active (542)
Use this procedure to clear the Automatic Power Reduction Active (542)
alarm. This alarm is raised on an amplifier.

Probable cause
This alarm is raised to notify users that the optical return loss (ORL) drops
below a fixed threshold. See Configuration, 323-1661-310, for information on
displaying optical facility details.

Low optical return loss indicates high reflection at the amplifier output, which
can be due to:
• dirty optical connectors
• improper optical cable mating
• a disconnected optical fiber at the amplifier output
• an optical fiber cut
• a degraded optical fiber
• a disconnected or missing termination
• misprovisioning of an amplifier resulting in excessive power being injected
into the mid-stage DSCM or fiber-plant

Attention: When the optical return loss (ORL) falls below the threshold, the
system reduces the amplifier output power level to minimize the danger of
personal eye injury.

Impact
Major, SA (service-affecting)

Prerequisites
• Observe all safety requirements. See Documentation Roadmap,
323-1661-090.
• Have the engineering documentation package (EDP).
• Have a fiber cleaning kit.
• Have a replacement module.
• Log into the Craft interface. See Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-20 Alarm clearing

Procedure 3-5 (continued)

Automatic Power Reduction Active (542)

Procedure steps
Step Action

1 If this alarm Then

was raised as a result of a no action is required. You can disable this
maintenance activity or during alarm if you do not want it to appear in the
SLAT and it is expected active alarm list. See Configuration,
323-1661-310.
is not expected go to step 2

2 Check the alarmed amplifier power level defined in your EDP against the
provisioned AMP settings in the Craft interface. See Configuration,
323-1661-310, for information on displaying optical facility details.
3 Edit power levels as required. See Configuration, 323-1661-310, for
information on editing the attributes of an optical facility.
If the alarm remains active, go to step 4.
4 If Then go to
the alarmed amplifier is a pre-amplifier step 5
otherwise step 8

5 Ensure that all LC/SC connectors are correctly mated on each module (for
example, CMD, SCMD, GMD, DSCM, DRA) located after the amplifier output.
Verify this on both ends of the connector mating receptacles.
If the alarm remains active, go to step 6.
6 Ensure that the termination plugs are present and are mated correctly on
unused ports. Termination plugs must be present on the SCMD Upgrade Out
port and GMD Group Out ports.
If the alarm remains active, go to step 7.
7 Ensure that the CMD and/or SCMD patch cord connections to the Channel In
and Channel Out ports are not reversed. If a subtending equipment
transmitter is connected to the Channel Out port by mistake, the alarm will be
raised.
If the alarm remains active, go to step 8.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-21

Procedure 3-5 (continued)

Automatic Power Reduction Active (542)

Step Action

8
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure that the optical
amplifier is out of service (OOS), then disconnect or
reconnect the fiber.

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Place the alarmed optical amplifier out of service (OOS). For information on
how to put the amplifier OOS, see Configuration, 323-1661-310.
9 Clean and then reconnect the output fibers and connectors at the amplifier.
For instructions on inspecting and cleaning optical fiber, see SLAT and
Channel Procedures, 323-1661-221.
10 Place the amplifier back in-service (IS). For information on how to put the
amplifier IS, see Configuration, 323-1661-310.
11 If the alarm remains active, you may have to clean a specific connector or
connectors that may not be immediately connected to the alarmed amplifier
output. For information on isolating connector losses, refer to Procedure 2-9,
Locating a reflective event.
12 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-22 Alarm clearing

Procedure 3-6
Automatic Shutoff (590, 942)
Use this procedure to clear the Automatic Shutoff (590, 942) alarm. This alarm
is masked by the Optical Line Fail (610, 541) alarm and the Circuit Pack
Missing (579) alarm.

This alarm is raised on amplifiers.

Probable cause
For amplifiers contained within the SLA, MLA, MLA2, or DRA, this alarm is
raised when the Automatic Laser Shut Off (ALSO) feature is activated.

The ALSO feature is a safety laser shutdown mechanism. Amplifier power

levels are turned down or turned off when a fiber break or intermediate
connector disconnect occurs between two neighboring sites where optical
radiation is being fed into both ends of the optical fiber and generating a
hazard on both ends of a fiber cut. For more information on this feature, see
the Planning Guide, NTT840FE.

Activation of the ALSO feature is an immediate consequence of an Optical

Line Fail (610, 541) condition detected at the alarmed site or adjacent site. In
cases where the Optical Line Fail (610, 541) occurs on a Stretched Span,
manual intervention may be required to recover from the condition after the
physical line fault has been repaired. For more information, see Chapter 6 for
the procedures on recovering from a fiber cut on Stretched Spans, with and
without Raman amplification, as applicable to your configuration.

For amplifiers contained within the SCMD8 or CMDA, this alarm is raised
when the Forced Shutoff parameter is set to the Enabled state. This alarm is
expected during SLAT and on a SCMD8 or CMDA that does not have any
channels controlled by DOC. The Forced Shutoff parameter is controlled by
DOC. Do not edit the Forced Shutoff parameter after SLAT.

When an amplifier pack is in Auto Shutoff Disabled mode, the Raman/Amp

Auto Shutoff Disabled alarm is raised. If the Ethernet cable is removed while
the pack is in Auto Shutoff Disabled mode, the Raman/Amp Auto Shutoff
Disabled alarm clears and the Circuit Pack Missing alarm is raised. This
indicates that the communication to the Raman/Amp pack has been
interrupted. The ALSO feature will not function in this state. Refer to the Circuit
Pack Missing (579) alarm clearing procedure to clear this condition.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-23

Procedure 3-6 (continued)

Automatic Shutoff (590, 942)

Impact
Major, SA (service-affecting)

Procedure steps
Step Action

1 If the alarm is raised against the Then go to

SLA, MLA, MLA2, or DRA step 2
SCMD8 amplifier or CMDA step 3

Alarm is raised against the SLA, MLA, MLA2, or DRA

2 Complete Procedure 3-59, Optical Line Fail (610, 541) on page 3-152.
This alarm is cleared when the condition that activated the ALSO feature is
cleared. If the alarm does not clear, contact your next level of support or your
Nortel support group.
Alarm is raised against the SCMD8 amplifier or CMDA
3 Log into the DOC network element that controls this amplifier.
4 Select Facilities->Domain Optical Controller (DOC).
5 Click on the Change Setting button.
6 Ensure that the Automation Mode is set to Auto Re-Optimize As Necessary.
7 Click on the OK button.
8 Allow DOC to run.

Attention: When DOC is in the Auto Re-Optimize As Necessary mode, the

next optimization occurs within five minutes.

9 Return to DOC to the original Automation Mode.

10 If the alarm does not clear, contact your next level of support or your Nortel
support group. If no channels are provisioned in DOC to drop to the SCMD8
or CMDA that is raising the alarm, you can put the amplifier facility on the
modules in the AINS state. See Configuration, 323-1661-310, for information
on placing facilities in AINS.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-24 Alarm clearing

Procedure 3-7
Automatic Shutoff Disabled (943, 1035)
Use this procedure to clear the Automatic Shutoff Disabled alarm.

The Automatic Shutoff Disabled (943) alarm is raised against RAMAN

facilities. The Automatic Shutoff Disabled (1035) is raised against AMP
facilities.

Probable cause
This alarm is raised when the RAMAN facility is placed in Automatic Shutoff
Disabled mode for a period of time that is specified by the Automatic Shutoff
Disabled timer. The RAMAN facility is put in Shutoff Disabled mode for
maintenance (for example, replacing an OSC module on an upstream network
element).

CAUTION
Risk of laser radiation exposure
During this procedure the fiber plant does not have to be
disrupted and the system remains a Class 1(IEC)/Class I
(FDA) product.

If the fiber upstream of the DRA Line A input connector

becomes disconnected accidentally while the Auto Shutoff
Disable feature is active, the radiation at the exposed fiber can
be at hazard level 3B (IEC 60825-2). In this situation, you must
take all safety precautions appropriate to hazard level 3B (IEC
60825-2).

The ORL based APR safety mechanism remains active.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-25

Procedure 3-7 (continued)

Automatic Shutoff Disabled (943, 1035)

This alarm is raised on AMP facilities when the Shutoff Threshold is

provisioned to be -60 dB for the AMP facility. The AMP facility is put in Shutoff
Disabled mode when the user is adding the first optical channel to a Stretched
Span (see the procedure in SLAT and Channel Procedures, 323-1661-221).

CAUTION
Risk of laser radiation exposure
During this procedure the fiber plant does not have to be
disrupted and the system remains a Class 1(IEC)/Class I
(FDA) product.

If the fiber downstream of the MLA2 Line A output connector

becomes disconnected accidentally while the Amp Auto
Shutoff Disabled feature is active, the radiation at the exposed
fiber can be at hazard level 1M (IEC 60825-2). In this situation,
you must take all safety precautions appropriate to hazard level
1M (IEC 60825-2).

The ORL based APR safety mechanism remains active.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC).
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.

Procedure steps
Step Action

1 Make sure that the maintenance work has been completed.

2 If the alarm is raised against Then go to
a RAMAN facility step 3
an AMP facility step 4

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-26 Alarm clearing

Procedure 3-7 (continued)

Automatic Shutoff Disabled (943, 1035)

Step Action

For RAMAN facilities

3 Immediately after the maintenance work has been completed, enable Auto
Shutoff:
• Select Facilities -> RAMAN.
• Click the Enable Auto Shutoff button to cancel the Shutoff Disabled.

This action also stops the timer and clears the alarm. (Note that this alarm
also clears when the RAMAN facility comes out of Shutoff Disabled mode
because the time specified by the Automatic Shutoff Disabled Time
parameter ends.)
Go to step 5.
For AMP facilities
4 This alarm clears when the Shutoff Threshold is provisioned to be above
-60 dB. For details on provisioning the Shutoff Threshold, see Configuration,
323-1661-310.
5 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-27

Procedure 3-8
Autoprovisioning Mismatch (60)
Use this procedure to clear the Autoprovisioning Mismatch (60) alarm. This
alarm is masked by the Circuit Pack Missing (579) alarm.

This alarm is raised on the following modules:

• 4 Channel Mux/Demux (CMD4)
• Serial 4 Channel Mux/Demux (SCMD4)
• Serial 8 Channel Mux/Demux (SCMD8)
• Channel Mux/Demux Amplifier (CMDA)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Optical Power Monitor (OPM)
• Wavelength Selective Switch (WSS)
• Distributed Raman Amplifier (DRA)

Probable cause
This alarm is raised when:
• An OPM module is inserted into a shelf that has an OPM as shared
equipment (in shared equipment list).
• Two modules with the same product engineering code (PEC) are
connected to the same Group Mux/Demux (GMD) or Uni Optical Service
Channel (UOSC). Examples include:
— A second CMD module of the same group as a currently provisioned
CMD module is inserted into a shelf.
— An OPM is inserted into an unprovisioned slot on a shelf that already
has an OPM provisioned in another slot.
— A WSS is inserted into an unprovisioned slot on a UOSC shelf that
already has a WSS provisioned in another slot.
• A module is installed in an unprovisioned slot that does not support that
module type. For example, a WSS is connected to a DOSC.
• You have provisioned your cascading order against the AMP, and a WSS
is connected to the GMD/UOSC and it autoprovisions. In this case the
system assumes that this is a TOADM site, so a WSS module is not
supported.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-28 Alarm clearing

Procedure 3-8 (continued)

Autoprovisioning Mismatch (60)

• CDM4/8 autoprovisioning is blocked because shared wavelengths are

already provisioned and in-service on a CMD44.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Have the engineering documentation package (EDP) for shelf details.
• Have a replacement module.

Procedure steps

Step Action

1 Select Configuration->Inventory.
2 Verify the information in the Inventory window against your EDP.
3
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage.

Connect the wrist strap to the ESD jack on the shelf or module.
4 Remove and replace the wrongly installed module, see the procedures in
chapter “Module and component replacement” on page 4-1. If the alarm
clears, you have completed this procedure. If the alarm is still active, go to
step 5.
5 Determine what is the shelf function (ROADM, TOADM) from the EDP.

Attention: A ROADM must have a WSS.

6 If the shelf function is Then

ROADM remove the cascading group provisioning from the
LIM module, and proceed with provisioning the
cascade order on the WSS module. See
Configuration, 323-1661-310.
TOADM remove the WSS from the shelf

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-29

Procedure 3-9
Channel Controller: Failure Detected (709)
Use this procedure to clear the Channel Controller: Failure Detected (709)
alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC) or Group

Mux/Demux (GMD).

Probable cause
This alarm is raised when the WSS controller (a GMD or UOSC) is unable to
function correctly. Conditions that can cause this alarm include:
• The WSS circuit pack has failed.
• There is a loss of signal on one of the channels carried by the WSS.
• The OPM circuit pack has failed.
• The OPM is not provisioned against LIM, SLA, MLA or MLA2 monitor ports
(there is an adjacency provisioning error).
• The OPM data is invalid (provisioning error).
• The fibers to the OPM monitor ports are crossed.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• Use an account with a level 3 or higher user privilege code (UPC).
• Have the engineering documentation package (EDP)/international
engineering apckage (IDP) that contains shelf details.
• Have a replacement module if required.
• Have a fiber cleaning kit.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-30 Alarm clearing

Procedure 3-9 (continued)

Channel Controller: Failure Detected (709)

Procedure steps
Step Action

Check for and clear the Circuit Pack Failed alarm

1 Check for the Circuit Pack Failed (581) alarm on the WSS or OPM and clear
it using the procedure in this document. If the alarm remains active, go to
step 2.
Check for adjacency alarms
2 Check for and clear any of the following alarms: Adjacency Mismatch (539),
Adjacency Far End Not Discovered (538) or Shelf Data Error (571). If the
alarm remains active, go to step 3.
Check for and clear other alarms in the system
3 Verify and clear any of the following alarms on all of the network elements
before clearing the Channel Controller: Failure Detected alarm:
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Group Input Loss Of Signal (712)
• Group Output Loss Of Signal (713)
• Group Loss of Signal (710, 832)
• Input Loss Of Signal (557)
• Loss Of Signal (553, 560)
• Optical Line Fail (610, 541)
• Output Loss Of Signal (572)
• Shutoff Threshold Crossed (540)
• Channel Controller: Unexpected Loss Detected (877)

If the alarm remains active, go to step 4.

Check the adjacency provisioning between the LIM, SLA, MLA, or MLA2 to OPM
4 Select Facilities->Adjacency.
5 View the LIM (LIM, SLA, MLA, MLA2) adjacency to ensure that the Expected
Far End Address field has the correct OPM module port listed.
6 If the Expected Far End Address field and Adjacency type are empty or have
incorrect values, select the LIM monitor port AID and click the Edit button to
set the correct Expected Far End Address and Adjacency Type (LIM). If the
alarm remains active, go to step 7.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-31

Procedure 3-9 (continued)

Channel Controller: Failure Detected (709)

Step Action

Check the derived OPM to LIM, SLA, MLA, MLA2 adjacency

7 View the OPM adjacency to ensure that the Expected Far End Address field
has the correct LIM module port listed.
8 If the Expected Far End Address field and Adjacency type are empty or have
incorrect values, select the OPM monitor port AID and click the Edit button to
set the correct Expected Far End Address and Adjacency Type (OPM).

Attention: If an OPM is shared between two shelves then (up to) four
different amp ports must each be configured (and fibered) correctly to share
the four OPM ports.

If the alarm remains active, go to step 9.

Check the shelf-to-shelf association
9 Select Configuration->Node Information->Shelf.
10 Check the Associated Shelf List and the Discovered Associated Shelf fields.
The Associated Shelf List field should list the adjacent shelf TID, and the
Discovered Associated Shelf TID should be the same as the Associated Shelf
List.
11 If the Then
Associated Shelf List shows the click the Edit button, and correct the
incorrect adjacent shelf TID Associated Shelf List field
Discovered Associated Shelf is not the check the inter-shelf
same as the Associated Shelf List communications

12 Repeat step 10 and step 11 on each adjacent shelf. If the alarm remains
active, go to step 13.
Check LIM to OPM fibering
13 Verify that all LIM (LIM, SLA, MLA, MLA2) to OPM fibers are connected to the
correct ports and that the fiber has been cleaned. For instructions on
inspecting and cleaning optical fiber, see SLAT and Channel Procedures,
323-1661-221. If the alarm remains active, go to step 14.
Perform restarts
14 Perform warm restarts on the OPM module and the WSS modules. See
Chapter 5, Restart procedures. If the alarm remains active, go to step 15.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-32 Alarm clearing

Procedure 3-9 (continued)

Channel Controller: Failure Detected (709)

Step Action

15 Perform warm restarts on the GMD or UOSC modules. See Chapter 5,

Restart procedures. If the alarm remains active, go to step 16.
16 Perform cold restarts on the OPM module and the WSS modules. See
Chapter 5, Restart procedures.
17 Perform cold restarts on the GMD or UOSC modules. See Chapter 5, Restart
procedures. If the alarm remains active, contact your next level of support or
your Nortel support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-33

Procedure 3-10
Channel Controller: Unexpected Loss Detected (877)
Use this procedure to clear the Channel Controller: Unexpected Loss
Detected (877) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC) or Group

Mux/Demux (GMD).

Probable cause
This alarm is raised when the WSS controller (a GMD or UOSC) is unable to
function correctly. Conditions that can cause this alarm include:
• The difference between the expected loss and the measured loss is higher
than 6 dB.
• The WSS circuit pack has failed.
• There is a loss of signal on one of the channels carried by the WSS.
• The OPM circuit pack has failed.
• The OPM is not provisioned against LIM, SLA, MLA or MLA2 monitor ports
(there is an adjacency provisioning error).
• The OPM data is invalid (provisioning error).
• The fibers to the OPM monitor ports are crossed.
• The transmitter power at the CMD44 ingress port is not within +/- 3 dBm
of the provisioned Max/Typical Launch Power for that Tx Adjacency. The
alarm is raised on managed channels that have this unexpected power
level, or on inactive channels that are being manually pre-checked with
this unexpected power level. This condition only applies to the CMD44
circuit pack.

Impact
minor, NSA (non-service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-34 Alarm clearing

Procedure 3-10 (continued)

Channel Controller: Unexpected Loss Detected (877)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• Use an account with a level 4 or higher user privilege code (UPC).
• Have the engineering documentation package (EDP) that contains shelf
details.
• Confirm if you require a replacement module.
• Have a fiber cleaning kit.

Procedure steps
Step Action

Check for and clear the Circuit Pack Failed alarm

1 Check for the Circuit Pack Failed (581) alarm on the WSS or OPM and clear
it using the procedure in this document.
If the alarm remains active, go to step 2.
Check for adjacency alarms
2 Check for and clear any of the following alarms: Adjacency Mismatch (539),
Adjacency Far End Not Discovered (538) or Shelf Data Error (571).
If the alarm remains active, go to step 3.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-35

Procedure 3-10 (continued)

Channel Controller: Unexpected Loss Detected (877)

Step Action

3 Verify and clear any of the following alarms on all of the network elements:
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Group Input Loss Of Signal (712)
• Group Output Loss Of Signal (713)
• Group Loss of Signal (710, 832)
• Input Loss Of Signal (557)
• Loss Of Signal (553, 560)
• Optical Line Fail (610, 541)
• Output Loss Of Signal (572)
• Shutoff Threshold Crossed (540)

If the alarm remains active, go to step 4.

Check the adjacency provisioning between the LIM, SLA, MLA, or MLA2 to OPM
4 Select Facilities->Adjacency.
5 View the LIM (LIM, SLA, MLA, MLA2) adjacency to ensure that the Expected
Far End Address field has the correct OPM module port listed.
6 If the Expected Far End Address field and Adjacency type are empty or have
incorrect values, select the LIM monitor port AID and click the Edit button to
set the correct Expected Far End Address and Adjacency Type (LIM).
If the alarm remains active, go to step 7.
Check the derived OPM to LIM, SLA, MLA, MLA2 adjacency
7 View the OPM adjacency to ensure that the Expected Far End Address field
has the correct LIM module port listed.
8 If the Expected Far End Address field and Adjacency type are empty or have
incorrect values, select the OPM monitor port AID and click the Edit button to
set the correct Expected Far End Address and Adjacency Type (OPM).

Attention: If an OPM is shared between two shelves then (up to) four
different amp ports have to each be configured (and fibered) correctly to
share the four OPM ports.

If the alarm remains active, go to step 9.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-36 Alarm clearing

Procedure 3-10 (continued)

Channel Controller: Unexpected Loss Detected (877)

Step Action

Check the shelf-to-shelf association

9 Select Configuration->Node Information->Shelf.
10 Check the Associated Shelf List and the Discovered Associated Shelf fields.
The Associated Shelf List field should list the adjacent shelf TID, and the
Discovered Associated Shelf TID should be the same as the Associated Shelf
List.
11 If the Then
Associated Shelf List shows the click the Edit button, and correct the
incorrect adjacent shelf TID Associated Shelf List field
Discovered Associated Shelf is not the check the inter-shelf comms
same as the Associated Shelf List

12 Repeat step 10 and step 11 on each adjacent shelf.

If the alarm remains active, go to step 13.
Check LIM to OPM fibering
13 Verify that all LIM (LIM, SLA, MLA, MLA2) to OPM fibers are connected to the
correct ports and that the fiber has been cleaned. For instructions on
inspecting and cleaning optical fiber, see SLAT and Channel Procedures,
323-1661-221.
If the alarm remains active, go to step 14.
Check the DOC screen
14 Select Facilities–>Domain Optical Controller (DOC)
The DOC screen opens.
15 From the DOC screen, check for channels that have a channel condition of
“Pre-Check Fail” or “Fault Detected”. If these channel conditions are the
cause of this alarm, the DOC Action: Fault Detected (873) alarm is raised.
16 If any channels have the condition of “Pre-Check Fail” or “Fault Detected”,
check for the DOC Action: Fault Detected (873) alarm (Select Faults–>Active
Alarms).
17 Click the Show Logs button to check the DOC logs and determine which
channel has the unexpected ingress power.
If the alarm remains active, go to step 19.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-37

Procedure 3-10 (continued)

Channel Controller: Unexpected Loss Detected (877)

Step Action

Perform restarts
18 Perform warm restarts on the OPM module and the WSS modules. See
Chapter 5, Restart procedures. If the alarm remains active, go to step 19.
19 Perform warm restarts on the GMD or UOSC modules. See Chapter 5,
Restart procedures. If the alarm remains active, go to step 20.
20 Perform cold restarts on the OPM module and the WSS modules. See
Chapter 5, Restart procedures.
21 Perform cold restarts on the GMD or UOSC modules. See Chapter 5, Restart
procedures. If the alarm does not clear, contact your next level of support or
your Nortel support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-38 Alarm clearing

Procedure 3-11
Circuit Pack Failed (581)
Use this procedure to clear the Circuit Pack Failed (581) alarm. This alarm
masks the associated facility alarms and is masked by the Circuit Pack
Mismatch (580) alarm.

This alarm is raised on the following modules:

• 4 Channel Mux/Demux (CMD4)
• Serial 4 Channel Mux/Demux (SCMD4)
• Serial 8 Channel Mux/Demux (SCMD8)
• Channel Mux/Demux Amplifier (CMDA)
• Dual Optical Service Channel (DOSC)
• Group Mux/Demux (GMD)
• Uni Optical Service Channel (UOSC)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Optical Power Monitor (OPM)
• Wavelength Selective Switch (WSS)
• Distributed Raman Amplifier (DRA)

Probable cause
This alarm is raised when a slot is provisioned and the valid module in the slot
has failed.

Attention: Both the alarm and LED alarm indicators can report the failure
at the same time. The status LED comes on (red indicates a failure) after a
module is inserted until it is completely booted. The module is not failed in
this case. This LED should clear one minute after insertion.

Impact
Major, SA (service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-39

Procedure 3-11 (continued)

Circuit Pack Failed (581)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Have a replacement module.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.

Procedure steps
Step Action

1 Identify the module raising the alarm. See “Identifying the alarmed entity” on
page 1-9.
2
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage.

Connect the wrist strap to the ESD jack on the shelf or module.
3 Replace the module. See the module replacement procedures in Chapter 4.
4 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-40 Alarm clearing

Procedure 3-12
Circuit Pack Mismatch (580)
Use this procedure to clear the Circuit Pack Mismatch (580) alarm. This alarm
is masked by the Circuit Pack Missing (579) alarm and the Circuit Pack
Upgrade Failed (124) alarm. This alarm masks the Circuit Pack Failed (581)
alarm.

This alarm is raised on the following modules:

• 4 Channel Mux/Demux (CMD4)
• Serial 4 Channel Mux/Demux (SCMD4)
• Serial 8 Channel Mux/Demux (SCMD8)
• Channel Mux/Demux Amplifier (CMDA)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Dual Optical Service Channel (DOSC)
• Group Mux/Demux (GMD)
• Uni Optical Service Channel (UOSC)
• Optical Power Monitor (OPM)
• Wavelength Selective Switch (WSS)
• Distributed Raman Amplifier (DRA)

Probable cause
This alarm is raised under the following conditions:
• A slot is provisioned for a module type and there is a module present in
the slot that is not the expected type.
• There is a problem with the module that prevents proper identification.
• The Ethernet cable for a subtending circuit pack was disconnected and
reconnected in less than five seconds (A 10-second wait time is required
before reconnecting.).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-41

Procedure 3-12 (continued)

Circuit Pack Mismatch (580)

Table 3-2 specifies slots where modules are supported in a Common Photonic
Layer shelf.

Table 3-2
Module positions in a Common Photonic Layer shelf
Module Slot number (see Note 1)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
GMD, DOSC, UOSC (see √
Note 2)
CMD4, CMD44, SCMD4, √ √ √ √ √ √ √ √ √ √ √ √
SCMD8 (see Note 3)
CMD44 (see Note 4) √ √
CMDA (see Note 5) √
DRA (see Note 6) √
LIM, SLA, MLA, MLA2 (see √ √ √ √ √ √ √ √ √ √ √ √
Note 3 and Note 7)
OPM (see Note 8) √
WSS (see Note 9) √
Note 1: There are 13 provisionable slots in a Channel Access network element and 12 provisionable
slots in a Line Amplifier.
Note 2: GMD, UOSC, and DOSC is always located in slot 4.
Note 3: Typically, CMD modules are located in slots 5 to 13 and amplifiers are located in slots 1 and
2. This reduces the risk of fibering errors.
Note 4: CMD44 are allowed only in slot 14 and 15.
Note 5: The CMDA can be located in any slot of the Common Photonic Layer shelf. However, it is
recommended to provision the CMDA in slot 5 or the first next available slot.
Note 6: The DRA can be located in any slot of the Common Photonic Layer shelf. However, it is
recommended to provision the DRA in slot 5 or the first next higher available slot.
Note 7: In a ROADM shelf, the LIM, SLA, MLA, and MLA2 modules are only supported in slots 1 and 2.
Note 8: The OPM module is usually located in slot 1 unless an interior SLA is provisioned in slot 1. In
this case, it is recommended to provision the OPM module in slot 13 or the next lower available slot.
Note 9: WSS modules are always located in slot 3.

Impact
Major, SA (service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-42 Alarm clearing

Procedure 3-12 (continued)

Circuit Pack Mismatch (580)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• If required, have a replacement module.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.

Step Action

1 Identify the module raising the alarm. See “Identifying the alarmed entity” on
page 1-9.
2 Verify if the DHCP Client Address Rejected (544) alarm is active, and clear it
using the procedure in this document.
If the alarm remains active, go to step 3.
3 Select Configuration->Equipment.
4 Click the alarmed module and verify if the provisioning information is correct.
5 If Then
the wrong module was provisioned delete and create the equipment with
for the slot the correct provisioning information.
See Configuration, 323-1661-310.
the correct module was go to step 6
provisioned for the slot

6 Compare the slot assignments in the Equipment window of the Craft interface
with the actual modules in the shelf to identify the incorrect or failed module.
7
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Remove the module currently located in the alarmed slot. See module
replacement procedures in Chapter 4.

Attention: Perform steps related to removing the module only.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-43

Procedure 3-12 (continued)

Circuit Pack Mismatch (580)

Step Action

8 Replace the module with the expected type. See module replacement
procedures in Chapter 4.

Attention: Perform steps related to installing the module only.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-44 Alarm clearing

Procedure 3-13
Circuit Pack Missing (579)
Use this procedure to clear the Circuit Pack Missing (579) alarm. This alarm
is masked by the following alarms: Autoprovisioning Mismatch (60), Circuit
Pack Unknown (58), and Provisioning Incompatible (82).

This alarm is raised on the following modules:

• 4 Channel Mux/Demux (CMD4)
• Serial 4 Channel Mux/Demux (SCMD4)
• Serial 8 Channel Mux/Demux (SCMD8)
• Channel Mux/Demux Amplifier (CMDA)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Optical Power Monitor (OPM)
• Wavelength Selective Switch (WSS)
• Distributed Raman Amplifier (DRA)

Probable cause
This alarm is raised when a slot is provisioned and the following occurs:
• The Ethernet harness cable between the UOSC, GMD or DOSC and the
alarmed module is missing, disconnected or faulty.
• There is no module or no Ethernet harness connected.
• A module fault makes the module undetectable.
• The LAN port is not enabled.

Impact
Major, SA (service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• If required, have a replacement module and an Ethernet harness.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-45

Procedure 3-13 (continued)

Circuit Pack Missing (579)

Procedure steps
Step Action

1 Identify the module raising the alarm. See “Identifying the alarmed entity” on
page 1-9.
2 If the alarm is raised against an amplifier (SLA, MLA, MLA2) or Raman
Amplifier (DRA) do not disconnect any fibers on the system, as Automatic
Laser Shut-Off may not operate correctly until the alarm is cleared.
CAUTION
Risk of laser radiation exposure
During this procedure the fiber plant does not have to
be disrupted and the system remains a Class
1(IEC)/Class I (FDA) product.

If the fiber upstream of the DRA Line A input connector

becomes disconnected accidentally while the Auto
Shutoff Disable feature is active, the radiation at the
exposed fiber can be at hazard level 3B (IEC 60825-2).
In this situation, you must take all safety precautions
appropriate to hazard level 3B (IEC 60825-2).

If the fiber downstream of the MLA2 Line A output

connector becomes disconnected accidentally while
the Amp Auto Shutoff Disabled feature is active, the
radiation at the exposed fiber can be at hazard level 1M
(IEC 60825-2). In this situation, you must take all safety
precautions appropriate to hazard level 1M (IEC
60825-2).
The ORL based APR safety mechanism remains
active.

3 Select Configuration->Comms Setting Management->Interfaces->LAN.

4 Verify that the LAN port of the alarmed slot is provisioned. Provision the slot
LAN Port if it is not displayed in the LAN Ports list. See Configuration,
323-1661-310, for more information.
If the alarm remains active, go to step 5.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-46 Alarm clearing

Procedure 3-13 (continued)

Circuit Pack Missing (579)

Step Action

5
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

If Then
the module is missing insert the correct module in the slot and
connect the Ethernet harness. See
Installation, 323-1661-201.
the correct module is present connect or reconnect the Ethernet
but the Ethernet harness is harness, and correct any other issues
missing, disconnected or faulty related to this cable.
the correct module and restart the module. See Chapter 5.
Ethernet harness are present
and connected

If the alarm remains active, go to step 6.

6 Perform a restart of the GMD, UOSC, or DOSC; see Chapter 5.
7 If the alarm did not clear after the restart, the module has failed. Replace the
module. See module replacement procedures in Chapter 4.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-47

Procedure 3-14
Circuit Pack Unknown (58)
Use this procedure to clear the Circuit Pack Unknown (58) alarm. This alarm
is masked by the Circuit Pack Missing (579) alarm.

Probable cause
This alarm is raised when a module is inserted into a slot and the inventory
information cannot be read from the module because of a software or
hardware problem.

It can also be raised if the module PEC is not supported in this software
release. See the ordering section of the Planning Guide, NTT840FE.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• If required, have a replacement module.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.

Procedure steps
Step Action

1 Identify the module raising the alarm. See “Identifying the alarmed entity” on
page 1-9.
2 Verify if the DHCP Client Address Rejected (544) alarm is active, and clear it
using the procedure in this document.
If the Circuit Pack Unknown (58) alarm remains active, go to step 3.
3 Select Configuration->Equipment.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-48 Alarm clearing

Procedure 3-14 (continued)

Circuit Pack Unknown (58)

Step Action

4 Compare the slot assignments in the Equipment window of the Craft interface
with the actual modules in the shelf to identify the unknown, incorrect or failed
module.
5 If Then
the shelf is equipped with the correct perform a power cycle on the
module but it is newly inserted module; see Procedure 5-4,
Performing a power cycle.
this is not a newly inserted module go to step 6

6
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage.

Connect the wrist strap to the ESD jack on the shelf or module.
If Then
the slot contains the wrong module remove and insert a module of the
correct type into the slot. See Chapter 4.
the correct module is in the slot power cycle the module. See
Procedure 5-4, Performing a power
cycle.

If the alarm remains active, go to step 7.

7 If the alarm did not clear after the power cycle, the module has failed. Replace
the module. See module replacement procedures in Chapter 4.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-49

Procedure 3-15
Circuit Pack Upgrade Failed (124)
Use this procedure to clear the Circuit Pack Upgrade Failed (124) alarm.

This alarm is raised on the following modules:

• 4 Channel Mux/Demux (CMD4)
• Serial 4 Channel Mux/Demux (SCMD4)
• Serial 8 Channel Mux/Demux (SCMD8)
• Channel Mux/Demux Amplifier (CMDA)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Optical Power Monitor (OPM)
• Wavelength Selective Switch (WSS)
• Distributed Raman Amplifier (DRA)

Probable cause
This alarm is raised against a module when the upgrade process fails for that
module for one of the following reasons:
• the Ethernet cable is disconnected during the upgrade
• the module is damaged

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• Use an account with a level 3 or higher user privilege code (UPC).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-50 Alarm clearing

Procedure 3-15 (continued)

Circuit Pack Upgrade Failed (124)

Procedure steps
Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Check the Ethernet cable connections on the alarmed module.

2 If Then
there is a disconnected Ethernet correct the problem, and go to step 3
cable or other connection problem
between the UOSC, GMD or DOSC
and the alarmed module
there are no Ethernet cable and go to step 4
connection problems

3 After the Ethernet connections have been repaired, the upgrade for the
alarmed module will be automatically started (the Software Auto-Upgrade in
Progress (439) alarm should be raised). Wait for the automatic upgrade to
complete. If the upgrade fails again and the Circuit Pack Upgrade Failed (124)
alarm is active, then go to step 6.
4 On the GMD, UOSC or DOSC that the alarmed module is connected to,
delete the LAN port of the alarmed module and then re-add it using the
following steps from the Craft:
• Select Configuration->Comms Setting Management->Interfaces->LAN
• Select the LAN port of the alarmed module (for example, SLOT-1-6) and
then click the Delete button.
• To re-add the LAN port, click the Add button.
• Select the LAN Port Type to be Slot Port, select the Port number (for
example, slot 6), select the Configured Mode and click the Ok button.
An automatic upgrade of the alarmed module is triggered and the Software
Auto-Upgrade in Progress (439) alarm is raised.
5 Wait for the automatic upgrade to complete. If the upgrade fails again and the
Circuit Pack Upgrade Failed (124) alarm is active, then go to step 6.
6 Replace the module. See module replacement procedures in Chapter 4.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-51

Procedure 3-16
COLAN 1 Port Failure (546)
Use this procedure to clear the COLAN 1 Port Failure (546) alarm. This alarm
is masked by the Circuit Pack Failed (581) alarm.

Probable cause
This alarm is raised when central office local area network port 1 (COLAN) on
the UOSC, GMD, and DOSC does not receive any Ethernet packets. This
occurs if there is a bad Ethernet connection or the COLAN port fails.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• Have data communication network (DCN) information for your network.
• Use an account with a level 3 or higher user privilege code (UPC).

Procedure steps
Step Action

1 Check the DCN information to determine if the COLAN 1 port should be

enabled.
If the COLAN should be Then go to
enabled step 3
disabled step 2

2 Delete the alarmed COLAN port. See Configuration, 323-1661-310, for

information on deleting a COLAN 1 port.

Attention: By deleting the COLAN port, you lose any established

connections to the Craft or any other connection that uses this port.

You have completed this procedure.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-52 Alarm clearing

Procedure 3-16 (continued)

COLAN 1 Port Failure (546)

Step Action

3 Check that the COLAN configuration at both ends of the Ethernet link are the
same. See Configuration, 323-1661-310 for information on how to view
COLAN port information.
4 If the configuration is different, edit the configuration as required. See
Configuration, 323-1661-310 for information on how to edit COLAN port
information.
If the alarm remains active, go to step 5.
5 Ensure that the appropriate cable is correctly connected to the alarmed
COLAN port. See Installation, 323-1661-201, for cabling procedures.
6 If the alarm does not clear, contact your next level of support to verify any
network issues or LAN equipment issues.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-53

Procedure 3-17
Cross-connection Mismatch (863)
Use this procedure to clear the Cross-connection Mismatch (863) alarm.

Probable cause
This alarm is raised when an optical cross-connection recorded in the Optical
Bandwidth Manager (OBM) database mismatched with the existing
configuration in the Shelf Wavelength Topology (SWT) database.

Impact
Major, SA (service-affecting)

Prerequisites
CAUTION
Risk of service interruption
Deleting a channel from the Domain Optical Controller (DOC)
can interrupt traffic.

• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• Use an account with a level 3 or higher user privilege code (UPC).

Procedure steps
Step Action

1 From the Craft, select the TID consolidated NE from the navigation tree. Then
select Visualization->Network Graphics Viewer.
The Network Graphics Viewer window opens.
2 In the Network Graphics Viewer, locate the Cross Connection table (right
window). Check the MISMATCH column and note the wavelength and the
direction of the connection.
3 If you can, switch traffic away from the link with the mismatch.
4 From the Craft, select Facilities->Domain Optical Controller (DOC).
The DOC window opens.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-54 Alarm clearing

Procedure 3-17 (continued)

Cross-connection Mismatch (863)

Step Action

5
CAUTION
Risk of service interruption
Deleting a channel from the Domain Optical Controller
(DOC) can interrupt traffic.

From the DOC window, select the channel that had the mismatch in the
Network Graphics Viewer. Click the Delete button (bottom of the window) to
remove the channel from the DOC.
6 After the channel is deleted in DOC, the alarm should clear immediately. You
must wait 15 minutes for the next Optical Bandwidth Manager (OBM) audit to
run before you re-add the channel.
If the alarm has Then complete
not cleared step 7
cleared step 10

7 If the alarm has not cleared after 15 minutes, go to the inventory screen and
restart (WARM) the primary shelf SP (VSC). See “Performing a module warm
restart” on page 5-3 for more information.
8 Wait for the restart to complete, then log back into the Craft and check for the
Cross-connection Mismatch alarm again (select Faults->Active Alarms).
If the alarm has Then complete
not cleared step 9
cleared step 10

9 If the alarm does not clear, contact your next level of support. You have
completed this procedure.
10 Wait 15 minutes for the next Optical Bandwidth Manager (OBM) audit to run.
Then, go to the DOC window (select Facilities->Domain Optical Controller
(DOC)), select the channel and click the Add button (bottom of the window).
The channel is added back to DOC.
11 Switch traffic back to the link.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-55

Procedure 3-18
Database Integrity Fail (8)
Use this procedure to clear the Database Integrity Fail (8) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised after a UOSC, GDM, or DOSC restart because of one of
the following conditions:
• The database was not recovered after the restart.
• The UOSC, GMD, or DOSC was unable to send the database file to the
subtending module.

Impact
Major, NSA (non-service-affecting)

Procedure steps
Step Action

1 Contact your next level of support or your Nortel support group.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-56 Alarm clearing

Procedure 3-19
Database Not Recovered (561)
Use this procedure to clear the Database Not Recovered (561) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC) or Group Mux/Demux (GMD).

Probable cause
This alarm is raised after a UOSC, GMD, or DOSC restart when the system
cannot determine which database is the correct one to recover from.

Impact
Major, SA (service-affecting)

Prerequisites
• Use TL1 commands.
• Be at the alarmed site.

CAUTION
Service affecting
This caution only applies to VSC (UOSC, DOSC, or GMD)
replacement procedures. It does not apply to VSC stand-alone
being commissioned.

Do not perform the steps to clear the Database Not Recovered

alarm if any of the following alarms exist on the system:
Software Delivery Incomplete (453), Software Configuration
Unknown (138), and Flash Banks Mismatch (222). If you detect
any of these conditions, along with the Database Not
Recovered (561) alarm, remove the subtending cards and
upgrade the VSC to the correct release before resuming the
procedure. Refer to the SLAT and Channel Upgrade
Procedures, 323-1661-221.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-57

Procedure 3-19 (continued)

Database Not Recovered (561)

Procedure steps
Step Action

1 Connect a PC to the Craft Ethernet port of the GMD, DOSC, or UOSC using
a cross-over Ethernet cable.
2 Open a DOS Command prompt on the craft PC and enter the following
command to establish a DHCP session:
ipconfig/release
ipconfig/renew
Note the default gateway address provided by the shelf.

Attention: It can take up to three minutes for the Ethernet link to establish.

3 Launch a Web browser, type the IP address of the default gateway noted in
step 2.
4 Log into the Craft. If the first screen presented after login is not the “Restore
Local Database” screen, then from the Craft menu go to
Configuration->Backup and Restore->Restore Local Database.
5 If this option is Then
not visible go to step 6 and use TL1
visible highlight the slot-shelf-module from which to restore
your local database. Click the Restore Local button.
Then click the Commit button. Go to step 11.

6 Telnet to the default gateway address provided by the UOSC, GMD, or DOSC.
For example, telnet 10.0.0.1 and establish a telnet session.
7 Activate a user session with:
ACT-USER:[<tid>]:<uid>:<ctag>::<pid>:[DOMAIN=<domain>];
8 Determine what slots contain databases using:
RTRV-LOCALDB:[<tid>]::<ctag>;
9 Use the following command to select the database to recover from:
RST-LOCALDB:[tid]:[aid]:ctag;
10 Use the following command to commit the files which have been restored:
CMMT-PROV:[<tid>]::<ctag>;
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-58 Alarm clearing

Procedure 3-19 (continued)

Database Not Recovered (561)

Step Action

11 Wait for the modules to restart.

12 Restart both DOC site GMDs to ensure that the channel topology is rebuilt
after the database recovery. For restart procedures, see Chapter 5.
13 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-59

Procedure 3-20
Database Restore in Progress (143)
Use this procedure to clear the Database Restore in Progress (143) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the UOSC, DOSC, or GMD detects that the module
is restoring its provisioning files from a remote source.

Canceling the restore operation clears this alarm.

Impact
minor, NSA (non-service-affecting)

Prerequisites
To perform this procedure, you must log into the Craft interface. To log into the
network element, see Configuration, 323-1661-310.

Procedure steps

Step Action

1 Wait until the database successfully restores the provisioning data.

Attention: If you want to abort the database restore, click the Cancel button
in the Backup and Restore window. Canceling stops the action and cleans up
any backup files left in invalid states.

2 If the alarm does not clear after the restore is complete, contact your next
level of support or your Nortel support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-60 Alarm clearing

Procedure 3-21
Database Save and Restore Failed (144)
Use this procedure to clear the Database Save and Restore Failed (144)
alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the UOSC, DOSC, or GMD detects that a save or
restore operation fails.

This alarm clears automatically when another save or restore operation is

attempted. The alarm remains clear if the backup or restore action is
successful, but returns if the operation is unsuccessful again.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• Use an account with a level 3 or higher user privilege code (UPC).

Procedure steps

Step Action

1 Select Configuration->Backup and Restore.

2 Check the information in the status display window to check the events that
led to the failure.
3 Verify that the URL information was entered correctly. See Configuration,
323-1661-310, for information on setting the URL.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-61

Procedure 3-21 (continued)

Database Save and Restore Failed (144)

Step Action

4 Click the Cancel button in the Backup and Restore window.

Canceling cleans up any backup files left in invalid states.

Attention: When restoring the databases at a TID consolidated node, the

primary shelf must be restored before restoring the member shelves.

5 Retry the backup/restore operation.

This alarm clears if you try to backup or restore the provisioning data again
and remains cleared if the backup or restore action is successful.
6 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-62 Alarm clearing

Procedure 3-22
DHCP Client Address Rejected (544)
Use this procedure to clear the DHCP Client Address Rejected (544) alarm.

Probable cause
This alarm is raised when the subtending module (CMD4, SCMD4, SCMD8,
LIM, SLA, MLA, MLA2, WSS, and OPM) rejects the dynamically assigned IP
address by the GMD, DOSC, or UOSC using Dynamic Host Configuration
Protocol (DHCP).

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• Have the engineering documentation package (EDP) for subtending
module details.
• Have DCN information for your network.
• Use an account with a level 3 or higher user privilege code (UPC).

Procedure steps
Step Action

1 Verify the equipment provisioning of the alarmed subtending module against

the EDP (see Configuration, 323-1661-310). Complete provisioning changes
as required.
2 Check and correct any cabling issues.
If the alarm remains active, go to step 3.
3 Perform a restart on the alarmed subtending module. See Chapter 5, Restart
procedures.

Attention: A power cycle is likely required. See Procedure 5-4, Performing

a power cycle.

4 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-63

Procedure 3-23
Disk 75 percent Full (374)
Use this procedure to clear the Disk 75 percent Full (374) alarm. This alarm
is masked by the Disk Full (146) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the disk is 75% full on the UOSC, DOSC or GMD.

This alarm clears when the disk space drops below 75% or when the UOSC
is restarted, and the space is less than 75%.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 No action is required unless more disk space is required. If more disk space
is required, go to step 2.
2 Select Configuration->Release Management.
3 Check the space remaining, which is indicated in the Space available field.
4 Click on a release load that you no longer require on the disk.
5 Click the Delete button.
6 Click Yes to confirm the Delete.
7 Check the available file system space that is now available.
8 Repeat step 4 to step 7 if more space is required.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-64 Alarm clearing

Procedure 3-24
Disk Full (146)
Use this procedure to clear the Disk Full (146) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the disk is full on the UOSC, DOSC, or GMD. This
alarm indicates that there is less than 512 Kbytes of available file system
space remaining.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.

Procedure steps
Step Action

1 Select Configuration->Release Management.

2 Check the space remaining, which is indicated in the Space available field.
3 Click on a release load that you no longer require on the disk.
4 Click the Delete button.
5 Click Yes to confirm the delete.
6 Check the available file system space that is now available.
7 Repeat step 3 to step 6 if more space is required.

Attention: This alarm clears when there is at least 5% of the disk space
available.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-65

Procedure 3-25
DOC Action: Channel Add in Progress (875)
Use this procedure to clear the DOC Action: Channel Add in Progress (875)
alarm.

This procedure applies to the Domain Optical Controller (DOC).

Probable cause
This alarm provides a warning to users who want to perform system
maintenance or provisioning.

This alarm is raised by the DOC as soon as the Add command enters the
EXECUTING state. This alarm is only active at the DOC site where the Add
command is executing.
Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.

Procedure steps
Step Action

1 Wait for the DOC Add to complete (successfully, unsucessfully, or with the
manual command STOP) and the DOC clears the alarm.
2 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-66 Alarm clearing

Procedure 3-26
DOC Action: Channel Delete in Progress (876)
Use this procedure to clear the DOC Action: Channel Delete in Progress (876)
alarm.

This procedure applies to the Domain Optical Controller (DOC).

Probable cause
This alarm provides a warning to users who want to perform system
maintenance or provisioning.

This alarm is raised by the DOC as soon as the Delete or Forced Delete
command enters the EXECUTING state.

The EXECUTING state begins after the “Add: Waiting” state.

This alarm is only active at the DOC site where the Delete or Forced Delete
command is executing.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Wait for DOC Delete to complete (successfully, unsucessfully, or by the

manual command STOP) and the DOC clears the alarm.
2 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-67

Procedure 3-27
DOC Action: Fault Detected (873)
Use this procedure to clear the DOC Action: Fault Detected (873) alarm.

This procedure applies to the Domain Optical Controller (DOC).

Attention: This alarm appears only on the affected DOC network element.

Probable cause
This alarm is raised during DOC Pre-Check or DOC Automatic Fault Detection
when DOC detects a fault or the action is not completed. The conditions that
can cause this failure include:
• Maintenance activities (such as, module replacement, module restart,
fiber cut) occurred while DOC auto monitoring was running.
• A module within the DOC photonic domain was replaced or restarted.
• an internal communications issue (for example ILAN is not cabled)
• an optical disconnect (such as a fiber cut) within the DOC span of control
• fiber pinch detected when the optical power differs from the baseline value
by more than the threshold provisioned by the ED-ADJ-FIBER command

Attention: This alarm is cleared if the DOC automation mode is changed to

No Automation. However, the underlying problem is not fixed. See
Configuration, 323-1661-310, for details on how to change the automation
mode.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC).
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-68 Alarm clearing

Procedure 3-27 (continued)

DOC Action: Fault Detected (873)

Procedure steps
Step Action

1 If maintenance activities (such as, module replacement, module restart, fiber

cut) occurred during the Fault Detected operation, then the DOC Action: Fault
Detected alarm will be active. Ensure that the maintenance activities have
completed.
2 Verify if the DOC Invalid Photonic Domain (552) alarm is active and clear it
using the procedure in this document.
3 Verify and clear any of the following alarms on all of the network elements that
are active within the DOC span of control:
• Adjacency Far End Not Discovered (538)
• Adjacency Provisioning Error (707)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Circuit Pack Failed (581)
• Circuit Pack Mismatch (580)
• Circuit Pack Missing (579)
• Circuit Pack Unknown (58)
• Gauge Threshold Crossing Alert Summary (724, 725, 726)
• Optical Line Fail (610, 541)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Shutoff Threshold Crossed (540)
• Channel Controller: Unexpected Loss Detected (877)

Attention: If the Optical Line Fail (610, 541) alarm is active, clear this alarm
first.

4 Clear all other active alarms on the network elements within the DOC span of
control. For optimal DOC operation, the system must be alarm free.
5 Use the Domain Optical Control Logs to assist in troubleshooting this DOC
alarm. First view the DOC logs from the DOC NE. The DOC NE logs can
indicate that another NE reported an error. If this is the case, then you must
view the DOC logs at the other NE. For information on retrieving DOC logs,
see Procedure 2-8, Displaying and clearing DOC and SOC logs.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-69

Procedure 3-27 (continued)

DOC Action: Fault Detected (873)

Step Action

6 Select your next step.

If Then go to
the alarm is raised after completing a software upgrade step 7
otherwise step 8

7 If the alarm is raised after completing a software upgrade and the DOC logs
indicate that a fiber degradation has been detected, verify that the optical
power at the fiber degradation point is within the expected range. A fiber
degradation will be indicated in the logs with a message as follows:
YYYY-MM-DD HH:MM:SS TID:Facility-shelf-slot-port,
BaselineLoss:X.XX, currentLoss:Y.YY, Exceed
DeltaThreshold:Z.ZZ
YYYY-MM-DD HH:MM:SS Fiber Degradation Fault Detected.
Check for loss after TID:Facility-shelf-slot-port

If the optical power at the point indicated Then

by the DOC logs
is within the expected range, reset the TCA baseline (see the
procedure on resetting the
baseline in Performance
Monitoring, 323-1661-520)
is not within the expected range repair the fiber indicated by the
DOC logs. After the repair is
complete, reset the TCA baseline
(see the procedure on resetting
the baseline in Performance
Monitoring, 323-1661-520).

If the alarm does not clear, go to step 8.

8 Verify and correct the following provisioned data using your EDP/IDP:
— Tx and Rx adjacency parameters (Type, and power parameters).
— Line adjacency parameter (Fiber Type)
— AMP optical facility parameters (MODE, Target Peak Power, Target
Power, Target Gain)
See Configuration, 323-1661-310, for information on how to display and edit
adjacency and optical facility parameters.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-70 Alarm clearing

Procedure 3-27 (continued)

DOC Action: Fault Detected (873)

Step Action

9 Run DOC fault detection again (either Pre-Check or regular fault detection).
10 If the alarm does not clear, contact your next level of support or your Nortel
support group.

Attention: This alarm is cleared if the Clear Alarm button is clicked in the
DOC window of the Craft interface; however, the underlying problem is not
cleared.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-71

Procedure 3-28
DOC Action Failed: Add (576)
Use this procedure to clear the DOC Action Failed: Add (576) alarm.

This procedure applies to the Domain Optical Controller (DOC).

Attention: This alarm appears only on the affected DOC network element.

Probable cause
This alarm is raised when a channel add operation is requested and fails.
Conditions that can cause this failure include:
• maintenance activities (for example, module replacement, module restart,
fiber cut) occurred during the channel add operation
• an internal communications issue (for example ILAN is not cabled)
• an optical disconnect (such as a fiber break) within the DOC span of
control
• a provisioning error on the Rx or Tx adjacency
• an associated adjacency, VOA or AMP facility is deleted
Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have the engineering documentation package (EDP) for provisioning
details.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-72 Alarm clearing

Procedure 3-28 (continued)

DOC Action Failed: Add (576)

Procedure steps
Step Action

1 If maintenance activities (such as, module replacement, module restart, fiber

cut) occurred during the channel add operation, then the DOC Action Failed:
Add alarm will be active. Ensure that the maintenance activities have
completed and then go to step 6.
2 Verify if the DOC Invalid Photonic Domain (552) alarm is active and clear it
using the procedure in this document.
3 Verify and clear any of the following alarms on all of the network elements that
are active within the DOC span of control:
• Adjacency Far End Not Discovered (538)
• Adjacency Provisioning Error (707)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Circuit Pack Failed (581)
• Circuit Pack Mismatch (580)
• Circuit Pack Missing (579)
• Circuit Pack Unknown (58)
• Gauge Threshold Crossing Alert Summary (724, 725, 726)
• Optical Line Fail (610, 541)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Shutoff Threshold Crossed (540)

Attention: If the Optical Line Fail (610, 541) alarm is active, clear this alarm
first.

4 Clear all other active alarms on the network elements within the DOC span of
control. For optimal DOC operation, the system must be alarm free.
5 Use the Domain Optical Control Logs to assist in troubleshooting this DOC
alarm. First view the DOC logs from the DOC NE. The DOC NE logs can
indicate that another NE reported an error, if this is the case, then you need
to view the DOC logs at the other NE. For information on retrieving DOC logs,
see Procedure 2-8, Displaying and clearing DOC and SOC logs.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-73

Procedure 3-28 (continued)

DOC Action Failed: Add (576)

Step Action

6 Delete the channels that were unsuccessfully added under DOC control. See
optical topology and optical control procedures in Configuration,
323-1661-310, for information on how to provision channels.
If the delete operation fails, try a force delete operation (service affecting
action). See optical topology and optical control procedures in Configuration,
323-1661-310, for information on how to provision channels.

Attention: You must successfully delete the channels that were

unsuccessfully added under DOC control before re-attempting to add them.

7 Verify and correct the following provisioned data using your EDP:
— Tx and Rx adjacency parameters (Type, and power parameters).
— Line adjacency parameter (Fiber Type)
— AMP optical facility parameters (MODE, Target Peak Power, Target
Power, Target Gain)
See Configuration, 323-1661-310, for information on how to display and edit
adjacency and optical facility parameters.
8 Re-attempt to add the channels.
9 If the alarm Then
clears you have completed this procedure
does not clear continue with step 10

10 Contact your next level of support or your Nortel support group, if the alarm
does not clear.

Attention: This alarm is cleared if the Clear Alarm button is clicked in the
DOC window of the Craft interface, however, the underlying problem is not
cleared.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-74 Alarm clearing

Procedure 3-29
DOC Action Failed: Delete (577)
Use this procedure to clear the DOC Action Failed: Delete (577) alarm.

This procedure applies to the Domain Optical Controller (DOC).

Attention: This alarm appears only on the affected DOC network element.

Probable cause
This alarm is raised when a channel delete operation is requested and fails.
Conditions that can cause this failure include:
• Maintenance activities (such as, module replacement, module restart,
fiber cut) occurred during the channel delete operation.
• An internal communications issue (for example ILAN is not cabled).
• An optical disconnect (such as a fiber break) within the DOC span of
control.
• A provisioning error on the Rx or Tx adjacency.
• An associated adjacency, VOA or AMP facility is deleted or out of service
(OOS).
• The DOC Action: Channel Delete was stopped before the deletion was
completed.
Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have the engineering documentation package (EDP) that contains
provisioning details.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-75

Procedure 3-29 (continued)

DOC Action Failed: Delete (577)

Procedure steps
Step Action

1 If maintenance activities (such as, module replacement, module restart, fiber

cut) occurred during the channel delete operation, then the DOC Action
Failed: Delete alarm will be active. Ensure that the maintenance activities
have completed and then go to step 2.
2 Verify if the DOC Invalid Photonic Domain (552) alarm is active and clear it
using the procedure in this document.
3 Verify and clear any of the following alarms on all of the network elements that
are active within the DOC span of control:
• Adjacency Far End Not Discovered (538)
• Adjacency Provisioning Error (707)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Circuit Pack Failed (581)
• Circuit Pack Mismatch (580)
• Circuit Pack Missing (579)
• Circuit Pack Unknown (58)
• Gauge Threshold Crossing Alert Summary (724, 725, 726)
• Optical Line Fail (610, 541)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Shutoff Threshold Crossed (540)

Attention: If the Optical Line Fail (610, 541) alarm is active, clear this alarm
first.

4 Clear all other active alarms on the network elements within the DOC span of
control. For optimal DOC operation, the system must be alarm free.
5 Use the Domain Optical Control Logs to assist in troubleshooting this DOC
alarm. First view the DOC logs from the DOC NE. The DOC NE logs can
indicate that another NE reported an error, if this is the case, then you need
to view the DOC logs at the other NE. For information on retrieving DOC logs,
see Procedure 2-8, Displaying and clearing DOC and SOC logs.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-76 Alarm clearing

Procedure 3-29 (continued)

DOC Action Failed: Delete (577)

Step Action

6 Verify and correct the following provisioned data using your EDP:
— Tx and Rx adjacency parameters (Type, and power parameters).
— Line adjacency parameter (Fiber Type)
— AMP optical facility parameters (MODE, Target Peak Power, Target
Power, Target Gain)
See Configuration, 323-1661-310, for information on how to display and edit
adjacency and optical facility parameters.
7 If the Condition field displays Then
a condition other than Partially Deleted step 8
Partially Deleted step 11

8 Select the Clear Alarm button in the DOC window.

Attention: This clears the DOC Action Failed: Delete alarm, however the
underlying problem is not cleared.

9 Select the Re-Optimize button and wait until the optimization is completed.
10 If the optimization Then go to
fails Procedure 3-31, DOC Action Failed:
Optimize (550)
succeeds step 11

11 Re-attempt the delete operation. See optical topology and optical control
procedures in Configuration, 323-1661-310, for information on how to
provision channels.

Attention: Any channels that were in the Delete queue are returned to their
previous state if the delete fails. These channels need to be re-selected for
deletion.

12 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-77

Procedure 3-30
DOC Action Failed: Monitor (549)
Use this procedure to clear the DOC Action Failed: Monitor (549) alarm.

This procedure applies to the Domain Optical Controller (DOC).

Attention: This alarm appears only on the affected DOC network element.

Probable cause
This alarm is raised when the DOC is in the Auto Monitor automation mode
and is unable to monitor and thus unable to determine if the Photonic Domain
is optimal. Conditions that can cause this failure include:
• maintenance activities (such as, module replacement, module restart,
fiber cut) occurred while DOC auto monitoring was running
• a module within the DOC photonic domain was replaced or restarted
• an internal communications issue (for example ILAN is not cabled)
• an optical disconnect (such as a fiber break) within the DOC span of
control

Attention: This alarm is cleared if the DOC automation mode is changed to

No Automation, however the underlying problem is not fixed. See
Configuration, 323-1661-310 for details on how to change the automation
mode.

Attention: When this alarm is raised, it indicates that DOC could not
determine the systems optimization state, so DOC keeps the current
optimization state. If this alarm was caused by a comms issue, the
optimization state is most likely indicated correctly in DOC. If this alarm is
caused by fault in the system such as a fiber cut, DOC may display that the
system is optimized, but in fact it is not. After the fault is fixed, the system
returns to its optimal state.

Impact
minor, NSA (non-service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-78 Alarm clearing

Procedure 3-30 (continued)

DOC Action Failed: Monitor (549)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps

Step Action

1 If maintenance activities (for example, module replacement, module restart,

or fiber cut) occurred while DOC automatic monitoring was running, then the
DOC Action Failed: Monitor alarm will be active. If this is the case and the
maintenance activities have been completed, the alarm should clear
autonomously during the next DOC auto monitor run. DOC Auto Monitor runs
5 minutes after the last DOC Auto Monitor operation has completed.
2 Continue with the next step, if the alarm remains active.
3 Verify if the DOC Invalid Photonic Domain (552) alarm is active and clear it
using the procedure in this document.

Attention: Once the DOC Invalid Photonic Domain (552) clears, the DOC
Action Failed: Monitor alarm should clear autonomously during the next DOC
auto monitor run. DOC Auto Monitor runs 5 minutes after the last DOC Auto
Monitor operation has completed.

4 Continue with the next step, if the alarm remains active.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-79

Procedure 3-30 (continued)

DOC Action Failed: Monitor (549)

Step Action

5 Verify and clear any of the following alarms on all of the network elements that
are active within the DOC span of control:
• Adjacency Far End Not Discovered (538)
• Adjacency Provisioning Error (707)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Gauge Threshold Crossing Alert Summary (724, 725, 726)
• Optical Line Fail (610, 541)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Shutoff Threshold Crossed (540)
• Circuit Pack Failed (581)
• Circuit Pack Mismatch (580)
• Circuit Pack Missing (579)
• Circuit Pack Unknown (58)

Attention: If the Optical Line Fail (610, 541) alarm is active, clear this alarm
first.

Once the above alarms have been cleared, the DOC Action: Fault Detected
alarm should clear autonomously during the next DOC auto monitor run.
DOC Auto Monitor runs 5 minutes after the last DOC Auto Monitor operation
has completed.
6 Continue with the next step, if the alarm remains active.
7 Clear all other active alarms on the network elements within the DOC span of
control.
For optimal DOC operation, the system must be alarm free. Once the other
alarms have been cleared, the DOC Action Failed: Monitor alarm should clear
autonomously during the next DOC auto monitor run. DOC Auto Monitor runs
5 minutes after the last DOC Auto Monitor operation has completed.
8 Continue with the next step, if the alarm remains active.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-80 Alarm clearing

Procedure 3-30 (continued)

DOC Action Failed: Monitor (549)

Step Action

9 Use the Domain Optical Control Logs to assist in troubleshooting this DOC
alarm. First view the DOC logs from the DOC NE. The DOC NE logs can
indicate that another NE reported an error, if this is the case, then you need
to view the DOC logs at the other NE. For information on retrieving DOC logs,
see Procedure 2-8, Displaying and clearing DOC and SOC logs.
After the conditions that caused the failure have been cleared, the DOC
Action Failed: Monitor alarm should clear autonomously during the next DOC
auto monitor run. DOC Auto Monitor runs 5 minutes after the last DOC Auto
Monitor operation has completed.
10 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-81

Procedure 3-31
DOC Action Failed: Optimize (550)
Use this procedure to clear the DOC Action Failed: Optimize (550) alarm.

This alarm is raised on the Domain Optical Controller (DOC).

Attention: This alarm appears only on the affected DOC network element.

Probable cause
This alarm is raised when the DOC is in the Auto Re-Optimize automation
mode and is unable to perform an optimization. The conditions that can cause
this failure include:
• maintenance activities (for example, module replacement, module restart,
or fiber cut) occurred while DOC auto monitoring was running
• an internal communications issue (for example, ILAN is not cabled)
• an optical disconnect (for example, a fiber break) within the DOC span of
control

Attention: This alarm is cleared if the DOC automation mode is changed to

No Automation, however the underlying problem is not fixed. See
Configuration, 323-1661-310 for details on how to change the automation
mode.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-82 Alarm clearing

Procedure 3-31 (continued)

DOC Action Failed: Optimize (550)

Procedure steps
Step Action

1 If maintenance activities (for example, module replacement, module restart,

or fiber cut) occurred while DOC auto re-optimize as necessary was running,
then the DOC Action Failed: Optimize alarm will be active. If this is the case
and the maintenance activities have been completed, the alarm should clear
autonomously during the next DOC auto re-optimize as necessary run.
2 Continue with the next step, if the alarm remains active.
3 Verify if the DOC Invalid Photonic Domain (552) alarm is active and clear it
using the procedure in this document.

Attention: Once the DOC Invalid Photonic Domain (552) clears, the DOC
Action Failed: Optimize alarm should clear autonomously during the next
DOC auto re-optimize as necessary run.

4 Continue with the next step, if the alarm remains active.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-83

Procedure 3-31 (continued)

DOC Action Failed: Optimize (550)

Step Action

5 Verify and clear any of the following alarms on all of the network elements that
are active within the DOC span of control:
• Adjacency Far End Not Discovered (538)
• Adjacency Provisioning Error (707)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Channel Controller: Unexpected Loss Detected (877)
• Circuit Pack Failed (581)
• Circuit Pack Mismatch (580)
• Circuit Pack Missing (579)
• Circuit Pack Unknown (58)
• Gauge Threshold Crossing Alert Summary (724, 725, 726)
• Optical Line Fail (610, 541)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Shutoff Threshold Crossed (540)

Attention: If the Optical Line Fail (610, 541) alarm is active, clear this alarm
first.

Once all of the alarms have been cleared, the DOC Action Failed: Optimize
alarm should clear autonomously during the next DOC auto re-optimize as
necessary run.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-84 Alarm clearing

Procedure 3-31 (continued)

DOC Action Failed: Optimize (550)

Step Action

6 Continue with the next step, if the alarm remains active.

7 Clear all other active alarms on the network elements within the DOC span of
control. For optimal DOC operation, the system must be alarm free. Once the
other alarms have been cleared, the DOC Action Failed: Optimize alarm
should clear autonomously during the next DOC auto re-optimize as
necessary run.
8 Continue with the next step, if the alarm remains active.
9 Use the Domain Optical Control Logs to assist in troubleshooting this DOC
alarm. First view the DOC logs from the DOC NE. The DOC NE logs can
indicate that another NE reported an error, if this is the case, then you need
to view the DOC logs at the other NE. For information on retrieving DOC logs,
see Procedure 2-8, Displaying and clearing DOC and SOC logs.
Once the conditions that caused the failure have been cleared, the DOC
Action Failed: Optimize alarm should clear autonomously during the next
DOC auto re-optimize as necessary run.
10 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-85

Procedure 3-32
DOC Consecutive Re-Opt Threshold Crossed (874)
Use this procedure to clear the DOC Consecutive Re-Opt Threshold Crossed
(874) alarm.

This procedure applies to the Domain Optical Controller (DOC).

Attention: This alarm appears only on the affected DOC network element.

Probable cause
This alarm is raised when DOC performs 10 re-optimizations in a row, with no
separation by successful auto-monitoring cycles (that is, when DOC
completes an optimization and the next monitoring cycle detects another
re-optimization is required). There are continuous power fluctuations (>
1.0 dB) that DOC needs to compensate for every five minutes for 10 times.
Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have the engineering documentation package (EDP) that contains
provisioning details.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-86 Alarm clearing

Procedure 3-32 (continued)

DOC Consecutive Re-Opt Threshold Crossed (874)

Procedure steps
Step Action

1 If the alarm occurs during maintenance activities (module replacement,

module restart, fiber cut), complete the activities and wait five minutes to see
if the alarm clears. Continue with the next step, if the alarm remains active.
2 Verify if the DOC Invalid Photonic Domain (552) alarm is active and clear it
using the procedure in this document.
Once the DOC Invalid Photonic Domain (552) clears, the DOC Consecutive
Re-Opt Threshold Crossed alarm should clear autonomously during the next
DOC auto re-optimize as necessary run.
Continue with the next step, if the alarm remains active.
3 Check and clear any of the following alarms on all of the network elements
that are active within the DOC span of control (Faults->Active Alarms):
• Adjacency Far End Not Discovered (538)
• Adjacency Provisioning Error (707)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Circuit Pack Failed (581)
• Circuit Pack Mismatch (580)
• Circuit Pack Missing (579)
• Circuit Pack Unknown (58)
• Gauge Threshold Crossing Alert Summary (724, 725, 726)
• Optical Line Fail (610, 541)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Shutoff Threshold Crossed (540)

Attention: If the Optical Line Fail (610, 541) alarm is active, clear this alarm
first.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-87

Procedure 3-32 (continued)

DOC Consecutive Re-Opt Threshold Crossed (874)

Step Action

Once all of the alarms have been cleared, the DOC Consecutive Re-Opt
Threshold Crossed alarm should clear autonomously during the next DOC
auto re-optimize as necessary run.
Use any Gauge Threshold Crossing Alert Summary alarms to help determine
the exact cause of the power fluctuation. Fix the cause of the power
fluctuation and let the system re-optimize. The alarm should clear.
Continue with the next step, if the alarm remains active.
4 Clear all other active alarms on the network elements within the DOC span of
control. For optimal DOC operation, the system must be alarm free.
Once the other alarms have been cleared, the DOC Consecutive Re-Opt
Threshold Crossed alarm should clear autonomously during the next DOC
auto re-optimize as necessary run.
Continue with the next step, if the alarm remains active.
5 Use the Domain Optical Control Logs to help you determine which section is
reporting not-optimal and for what reason. First view the DOC logs from the
DOC NE. The DOC NE logs can indicate that another NE reported an error,
if this is the case, then you need to view the DOC logs at the other NE.
For example, the Domain Optical Control Command Log may show a
message like: “<date, time><NE-X>SOC was not optimal”, and the
corresponding Section Optical Control Command Log might show a message
like “<date, time> Not Optimal Status was reported for peak channel power”.
For information on retrieving DOC logs, see Procedure 2-8, Displaying and
clearing DOC and SOC logs.
6 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-88 Alarm clearing

Procedure 3-33
DOC Domain Not Optimized (551)
Use this procedure to clear the DOC Domain Not Optimized (551) alarm.

This procedure applies to the Domain Optical Controller (DOC).

Attention: This alarm appears only on the affected DOC network element.

Probable cause
This alarm is raised when the system is not optimal. The conditions that can
cause this alarm include:
• A channel addition or deletion has failed.
• The automation modes; Auto Monitor and Auto Re-Optimize As
Necessary, has determined that the system is not optimal.
Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have the engineering documentation package (EDP) that contains
adjacency details.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-89

Procedure 3-33 (continued)

DOC Domain Not Optimized (551)

Procedure steps
Step Action

1 If Then
none of the following alarms are active: go to step 2
DOC Action Failed: Monitor (549)
DOC Action Failed: Optimize (550)
DOC Action Failed: Add (576)
DOC Action Failed: Delete (577)
the DOC Action Failed: Monitor (549) is complete Procedure 3-30, DOC
active Action Failed: Monitor (549)
the DOC Action Failed: Optimize (550) complete Procedure 3-31, DOC
is active Action Failed: Optimize (550)
the DOC Action Failed: Add (576) is complete Procedure 3-28, DOC
active Action Failed: Add (576)
the DOC Action Failed: Delete (577) is complete Procedure 3-29, DOC
active Action Failed: Delete (577)

2 Wait for the re-optimization or auto-monitor to complete, or select the

Re-Optimize button to trigger an immediate re-optimization.
3 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-90 Alarm clearing

Procedure 3-34
DOC Invalid Photonic Domain (552)
Use this procedure to clear the DOC Invalid Photonic Domain (552) alarm.

This procedure applies to the Domain Optical Controller (DOC).

Attention: This alarm appears only on the affected DOC network element.

Attention: This alarm is active during system lineup and test (SLAT).

Probable cause
This alarm is raised when the DOC cannot retrieve a valid Network Topology.
Conditions that can cause this alarm include:
• an internal communications issue (for example ILAN is not cabled)
• an optical disconnect (such as a fiber break) within the DOC span of
control
• there is an incorrectly provisioned shelf parameter
• an upstream UOSC, DOSC or GMD has undergone a restart operation.
The alarm clears once the restart has completed.
• there are more than two DOC network elements provisioned within the
optical system
• if a channel has been optimized in the system and an upstream Tx on the
same channel has been provisioned. (To prevent this alarm from being
raised, enter the second Rx Adjacency for the reused wavelength before
provisioning the second Tx Adjacency.)

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Have the engineering documentation package (EDP) that contains shelf
details.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-91

Procedure 3-34 (continued)

DOC Invalid Photonic Domain (552)

Procedure steps
Step Action

1 If the system Then

is being SLATed no action is required, alarm clears after SLAT
is already SLATed continue with the next step

2 Verify that both DOC site network elements are commissioned and
connected to the network.
3 Verify that the shelf parameters are correctly provisioned.

Attention: Select Configuration->Node Information->Shelf to view shelf

details.

4 If a channel has been optimized in the system and an upstream Tx on the

same channel has been provisioned, remove the Tx adjacency or add an Rx
to terminate the wavelength correctly. The DOC clears the alarm after the
topology rebuilds. For more information, see the adjacency provisioning
chapter in Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-92 Alarm clearing

Procedure 3-34 (continued)

DOC Invalid Photonic Domain (552)

Step Action

5 Verify if any of the following alarms, which indicate an internal

communications or equipment problem, are active within the DOC span of
control, and clear them using the procedures in this document:
• Circuit Pack Failed (581)
• Circuit Pack Mismatch (580)
• Circuit Pack Missing (579)
• Circuit Pack Unknown (58)
• Circuit Pack Upgrade Failed (124)
• Duplicate IP Address (545)
• Duplicate Shelf Detected(70)
• Database Integrity Fail (8)
• Database Not Recovered (561)
• Database Restore in Progress (143)
• Database Save and Restore Failed (144)
• DHCP Client Address Rejected (544)
• ILAN 1 Port Failure (547)
• ILAN 2 Port Failure (548)
• OSPF Area Exceeded (543)
• Packet Rate Limit Exceeded (591)
• Shelf Data Error (571)
• Shelf Data Missing (570)
• Circuit Pack Upgrade Failed (124)
• Software Auto-Upgrade in Progress (439)
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-93

Procedure 3-34 (continued)

DOC Invalid Photonic Domain (552)

Step Action

6 Wait at least 15 minutes and verify that the alarm cleared. Continue with the
next step, if the alarm remains active.
7 Verify if any of the following alarms, which indicate an optical disconnect, are
active within the DOC span of control, and clear them using the procedures
in this document:
• Adjacency Far End Not Discovered (538)
• Adjacency Provisioning Error (707)
• Adjacency Mismatch (539)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Optical Line Fail (610, 541)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)

Attention: If the Optical Line Fail (610, 541) alarm is active, clear this alarm
first.

8 Wait at least 15 minutes and verify that the alarm cleared. Continue with the
next step, if the alarm remains active.
9 Clear all other active alarms on the network elements within the DOC span of
control.

Attention: For optimal DOC operation, the system must be alarm free.

Use the Domain Optical Control Logs to assist in troubleshooting this DOC
alarm. First view the DOC logs from the DOC NE. The DOC NE logs can
indicate that another NE reported an error, if this is the case, then you need
to view the DOC logs at the other NE. For information on retrieving DOC logs,
see Procedure 2-8, Displaying and clearing DOC and SOC logs.
10 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-94 Alarm clearing

Procedure 3-35
Duplicate IP Address (545)
Use this procedure to clear the Duplicate IP Address (545) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised under the following conditions:
• The UOSC, GMD or DOSC detects another network element with the
same internet protocol (IP) address. The alarm occurs at the same time at
all network elements that share the same IP. Each UOSC, GMD, or DOSC
detects the condition.
• A gratuitous address resolution protocol (ARP) message or an AR
application detects that the network element (NE) IP address is being
used by another connected device.
• During provisioning of a Redundant ARP GNE configuration, a Duplicate
IP Address alarm is raised. Provisioning of a Redundant ARP
configuration (particularly if single shelf IP is being used) requires the
COLAN IP of both GNEs to be entered in the Proxy list of both GNEs. A
GNE attempts to become master for all IPs in its Proxy list and upon
becoming master sends a gratuitous arp for that IP. When provisioning of
one of the GNEs is completed (and before completion of provisioning its
partner GNE), the GNE can become master and send a gratuitous arp for
its proposed partner GNE's COLAN IP. The intended partner GNE raises
the Duplicate IP Address alarm. Once provisioning of the partner GNE is
completed, the partner GNE takes over as master for its own COLAN IP.
A GNE is always the preferred master for its own COLAN IP and the
Duplicate IP Address alarm clears.
Impact
minor, NSA (non-service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-95

Procedure 3-35 (continued)

Duplicate IP Address (545)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC) on the
nodes with a duplicate IP.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have a network plan or other documents that allow you to determine the
correct IPs.

Procedure steps

Step Action

1 Identify the network elements raising this alarm.

2 Determine from network plans or other documents which network element
has the correct IP.
3 Log in to the network element with the duplicate IP.

Attention: If a remote login is not possible, log in locally using the RS-232
serial modem port. If the serial port is used, the Craft is not available.

4 Select Configuration->Comms Setting Management->Interfaces->IP.

The IP window opens, and the current IP address is displayed.
5 Click the row identified as COLAN-#-1.
The Attribute/Values Details table appears.
6
CAUTION
Risk of loss of functionality
Ensure every network element has an unique IP. If you
are changing the IP of a network element, ensure that
the new IP is correct.

Click the Edit button.

7 Enter the unique IP address in the IP Address field.
8 Click the Ok button.
9 Ensure no other Duplicate IP Address alarms exist. If there are other
Duplicate IP Address alarms, repeat this procedure.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-96 Alarm clearing

Procedure 3-36
Duplicate Primary Shelf (714)
Use this procedure to clear the Duplicate Primary Shelf (714) alarm.

This alarm is generated at the shelf level.

Probable cause
This alarm is raised if more than one primary shelf is activated within a
consolidated TID. This alarm is raised on all the primary shelves within the
consolidated TID.

Attention: A Primary shelf will not auto-provision new member shelves

while a duplicate primary shelf exists on the same network.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have the engineering documentation package (EDP) that contains shelf
details.

Procedure steps

Step Action

1 Identify the shelves raising this alarm.

2 Determine from network plans or other documents which shelf should be the
Primary shelf.
3 Log into the network element that is enabled as a primary shelf, but should
not be.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-97

Procedure 3-36 (continued)

Duplicate Primary Shelf (714)

Step Action

4 Select Configuration->Node Information->Shelf.

The Shelf window opens.
5 Select the shelf.
The Attribute/Values Details table appears.
6 Click the Edit button.
7 Select Disable for the Primary field.
8 Click Yes.

Attention: This action triggers a restart of the shelf.

9 Log back in after the shelf has restarted and verify that the alarm has cleared
against the shelf.

Attention: The first time a user logs into the TID consolidated shelf, the shelf
that was just edited will not have all the Craft menu items available. Log out
and log back in to restore access to all the menu items.

10 Ensure no other Duplicate Primary Shelf alarms exist. If there are other
Duplicate IP Address alarms, repeat this procedure.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-98 Alarm clearing

Procedure 3-37
Duplicate Site ID (871)
Use this procedure to clear the Duplicate Site ID (871) alarm.

This alarm is raised on a shelf.

Probable cause
This alarm is raised when both the Site Identifier and the Shelf ID of two or
more shelves are the same. The alarm occurs at the same time at all network
elements that share the same Site ID and Shelf ID. Each UOSC, GMD, or
DOSC detects the condition.

Attention: After a restart, this alarm can be masked for 20 minutes.

Attention: You can edit the Site ID, however changing the Shelf ID, requires
decommissioning and recommissioning of the network element.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC) on the
nodes with this alarm.
• Have a network plan or other documents that allow you to determine the
correct Site ID and Shelf ID.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-99

Procedure 3-37 (continued)

Duplicate Site ID (871)

Procedure steps
Step Action

1 Identify the network elements raising this alarm.

2
CAUTION
Risk of loss of functionality
Traffic and data communications will be lost
Decommissioning a shelf results in a loss of all traffic
and data communications associated with the shelf that
is being decommissioned.

If Then
the Site ID is incorrectly go to step 3
provisioned
the Shelf ID is incorrectly Decommission the shelf and re-add it, see
provisioned SLAT and Channel Procedures, 323-1661-221
Take note of all the provisioning information
required to recommission the shelf.

Attention: It is easier to perform a change in Site ID. A change in Shelf ID

requires decommissioning the shelf.

3 Determine from network plans or other documents which network element

has the correct Site ID.
To view the current Site ID, select Configuration->Node Information->Shelf
4 Log in to the network element with the duplicate Site ID.
5 Select Configuration->Node Information->Shelf.
6
CAUTION
Risk of loss of functionality
Ensure every network element has an unique set of
both the Site ID and Shelf ID. If you are changing the
Site ID of a network element, ensure that the new Site
ID is unique.

Highlight the shelf. Click the Edit button. Edit the Site ID to be something
unique from all other shelves in the network.
7 Click the OK button.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-100 Alarm clearing

Procedure 3-37 (continued)

Duplicate Site ID (871)

Step Action

8 Log back into the shelf and verify that the alarm has cleared.
9 Ensure no other Duplicate Site ID alarms exist. If there are other Duplicate
Site ID alarms, repeat this procedure.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-101

Procedure 3-38
Duplicate Shelf Detected(70)
Use this procedure to clear the Duplicate Shelf Detected (70) alarm.

This alarm is generated at the shelf level.

Probable cause
This alarm is raised on a shelf that has detected another shelf in the network
with the same TID (also referred to as the Site Name) and Shelf ID (SHELF-#).

An OADM/ROADM/TOADM site consists of two Channel shelves each with a

GMD or UOSC. The GMD or UOSC of each shelf represents a direction. A
Shelf ID with a value of Shelf-1 represents the west-facing direction and
Shelf-2 represents the east-facing direction. For a Line Amplifier network
element, the Shelf ID value is always Shelf-1.

Attention: Using Shelf-1 and Shelf-2 as described is recommended,

however, other values can be used.

Impact
major, NSA (non-service-affecting)

Prerequisites
• Ensure that you are the only active user logged into the network element.
For information on viewing active users, see Configuration, 323-1661-310.
If the network element is managed by OMEA, unmanage the node before
performing this procedure (refer to the OMEA NTP library for details).
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have the engineering documentation package (EDP) that contains shelf
details.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-102 Alarm clearing

Procedure 3-38 (continued)

Duplicate Shelf Detected(70)

Procedure steps

Step Action

1 Identify the shelves raising this alarm.

2 Determine from network plans or other documents which shelf has
provisioned information that is incorrect. Take note of the IP address of the
shelf with the valid provisioning.
Select Configuration->Shelf Level View to view shelf details.
3
CAUTION
Risk of loss of functionality
Traffic and data communications will be lost
Decommissioning a shelf results in a loss of all traffic
and data communications associated with the shelf that
is being decommissioned.

CAUTION
Risk of loss of functionality
Make sure that you have the correct duplicate. A
software configuration restart is required to correctly
recover, removing network visibility of the member
node for the duration of the restart.

If Then
the TID is incorrectly change the TID, see “Displaying and changing
provisioned the NE Name (target identifier (TID))” in
Configuration, 323-1661-310
the Shelf ID is incorrectly Decommission the shelf and re-add it, see
provisioned SLAT and Channel Procedures, 323-1661-221
Take note of all the provisioning information
required to recommission the shelf.

4 If the network element was previously managed by OMEA, enrol the network
element again in OMEA so that it is managed again (see OMEA NTP library
for details).
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-103

Procedure 3-39
Fan Failed (592)
Use this procedure to clear the Fan Failed (592) alarm. This alarm is masked
by the Fan Missing (593), Circuit Pack Mismatch (580), and Circuit Pack
Missing (579) alarms.

This alarm is raised on the following modules:

• Channel Mux/Demux Amplifier (CMDA)
• Dual Optical Service Channel (DOSC)
• Uni Optical Service Channel (UOSC)
• Group Mux/Demux (GMD)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Distributed Raman Amplifier (DRA)

Probable cause
This alarm is raised when the fan unit is:
• missing
• equipped but has failed

Impact
Major, SA (service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• If required, have a replacement fan module.
• Have a flathead screwdriver.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-104 Alarm clearing

Procedure 3-39 (continued)

Fan Failed (592)

Procedure steps
Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

2 Open the module front cover by turning the screws counterclockwise.

3 Check the air filter to ensure there is no blockage, and replace it if required.
See Procedure 4-20, Replacing air filters.
4 Check the fan assembly. See figures in Procedure 4-18, Replacing the fan
assembly in an amplifier and Procedure 4-19, Replacing the fan assembly in
a UOSC, GMD, or DOSC.
5 If the fan assembly Then go to
is missing step 9
has failed step 6

6 Verify that the fan assembly is seated correctly.

7 Make any necessary adjustments.
8 If the alarm Then go to
cleared step 10
did not clear step 9

9 Install the missing fan assembly or replace the failed fan assembly. See
Procedure 4-18, Replacing the fan assembly in an amplifier or
Procedure 4-19, Replacing the fan assembly in a UOSC, GMD, or DOSC.
10 Close the front cover of the module by turning the screws clockwise.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-105

Procedure 3-40
Fan Missing (593)
Use this procedure to clear the Fan Missing (593) alarm. This alarm masks
the Fan Failed (592) alarm and is masked by the Circuit Pack Mismatch (580)
alarm.

This alarm is raised on the following modules:

• Channel Mux/Demux Amplifier (CMDA)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Distributed Raman Amplifier (DRA)

Attention: This alarm is not raised on the GMD, UOSC, or DOSC. When the
fan module is removed on these modules, the Fan Failed (592) alarm is
raised.

Probable cause
This alarm is raised when the fan unit in the CMDA, LIM, SLA, MLA, MLA2, or
DRA is missing.

The Fan Fail LED is lit (red) when this alarm is raised.

Impact
Major, SA (service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• If required, have a replacement fan module.
• Have a flathead screwdriver.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-106 Alarm clearing

Procedure 3-40 (continued)

Fan Missing (593)

Procedure steps

Step Action

1 Install the missing fan assembly. See Procedure 4-18, Replacing the fan
assembly in an amplifier.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-107

Procedure 3-41
Fiber Type Manual Provisioning Required (907)
Use this procedure to clear the Fiber Type Manual Provisioning Required
(907) alarm.

This alarm is raised on a line adjacency.

Probable cause
This alarm is raised for a line adjacency when the fibertype for the line
adjacency is set to UNKNOWN (not provisioned) putting the line adjacency
OOS.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps

Step Action

1 Change the fiber type of a line adjacency to a value other than UNKNOWN
using the procedure on editing adjacencies in Configuration, 323-1661-310.
2 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-108 Alarm clearing

Procedure 3-42
Flash Banks Mismatch (222)
Use this procedure to clear the Flash Banks Mismatch (222) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when an upgrade is interrupted. When an upgrade is
interrupted, different loads can be present on the UOSC, GMD, or DOSC.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Retrieve and note all active alarms (enabled and disabled) on the system.
See Procedure 2-1, Displaying active alarms and Procedure 2-2, Displaying
active disabled alarms.
2 Identify the module raising the alarm. See “Identifying the alarmed entity” on
page 1-9.
3 Select Configuration->Release Management.
4 Verify the current load release on the UOSC, DOSC, or GMD.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-109

Procedure 3-42 (continued)

Flash Banks Mismatch (222)

Step Action

5 If Then
the current active upgrade the UOSC, GMD or DOSC to the current
network element release active network element release.
is not the required Note 1: Contact Nortel for upgrade support
release before upgrading the UOSC, GMD, or DOSC.
Note 2: If the UOSC, GMD, or DOSC does not
contain the required release, you must transfer a
software load from a local or remote server into
the UOSCs, GMDs, or DOSCs local file system,
before upgrading. See release and upgrade
management procedures in Configuration,
323-1661-310.
the release running on upgrade all of the NE subtending modules to the
the UOSC, GMD, or UOSC, GMD, or DOSC release.
DOSC is the required Note: Contact Nortel for upgrade support before
release upgrading the NE subtending modules.

6 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-110 Alarm clearing

Procedure 3-43
Gauge Threshold Crossing Alert Summary (724, 725,
726)
Use this procedure to clear the Gauge Threshold Crossing Alert Summary
(724, 725, 726) alarm. This alarm is masked by the Circuit Pack Failed (581)
alarm.

This alarm is a summary alarm for each facility. The alarm is raised if one or
more of the physical gauge power values crosses its provisioned PM
threshold.

This alarm is masked by the Loss Of Signal (553, 560) alarm.

This procedure applies to the VOA, OPTMON, AMP, and RAMAN facilities.

Probable cause
This alarm is raised when one of the following physical gauge power values
has crossed a provisioned PM threshold:
— optical power received (OPR)
— optical power transmitted (OPT)
— optical power input (OPIN)
— optical power output (OPOUT)
— optical return loss (ORL)
— group gain (GRPGAIN)
— group optical power output (GRPOPOUT)
— group optical power input (GRPOPIN)
— group optical power transmitted (GRPOPT)
— OSC optical power input to a DRA (OPROSC)

Attention: PM thresholds are defined by PM Profiles and base lined values,

base lining of physical gauge power values is normally done by DOC.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-111

Procedure 3-43 (continued)

Gauge Threshold Crossing Alert Summary (724, 725, 726)

The typical cause for this alarm is reduced power levels on the port reporting
the alarm. Conditions that can result in reduced power levels at a port include:
• a faulty or incorrectly provisioned transmitter module
• a faulty or incorrectly provisioned receive module
• an optical signal degradation due to a bent optical fiber or a dirty optical
connector
• a wrong dispersion slope compensating module (DSCM) type for the link
• improper optical cable mating
• a disconnected optical fiber at the amplifier output
• an optical fiber cut
• a disconnected or missing termination
• misprovisioning of an amplifier resulting in excessive power being injected
into the mid-stage DSCM or fiber-plant
• a power value that is reported out of range (OOR) and is outside the
threshold range of the current baseline
• anytime a baseline has been set as out of range (OOR) regardless of the
current power

Use this alarm to resolve the causes of the threshold crossings before a
service-affecting problem occurs.

This alarm clears automatically when all gauge readings fall within their
threshold boundaries.

Attention: This alarm can be cleared manually from the Craft PM screen as
follows. Bear in mind that manually clearing this alarm does not resolve the
underlying cause of the alarm.
—Select the facility and the module associated with the alarm.
—Click the Reset button.
—Confirm the module, and select the Baseline check box.

Impact
minor, NSA (non-service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-112 Alarm clearing

Procedure 3-43 (continued)

Gauge Threshold Crossing Alert Summary (724, 725, 726)

Prerequisites
• Have an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have the engineering documentation package (EDP) for shelf details.
• Have a fiber cleaning kit.
• May require a replacement module or fiber patch cord.

Procedure steps
Step Action

1 If this alarm Then

was raised as a result of a no action is required. You can disable this
maintenance activity or during alarm if you do not want it to appear in the
SLAT and it is expected active alarm list (see Configuration,
323-1661-310).
is not expected go to step 2

2 Select Performance->PM Profiles.

3 Verify that the PM threshold values for the facility is correctly provisioned,
adjust the value if required. For information on how to set PM thresholds, see
Performance Monitoring, 323-1661-520.
If the alarm remains active, go to step 4.
4 Verify that the optical power is within range. See Performance Monitoring,
323-1661-520.
5 If both the minimum and maximum values are outside of range, you can
enable the automatic in-service (AINS) feature for the facility until a valid
signal is present. For AINS provisioning, see Configuration, 323-1661-310.
If the alarm remains active, go to step 6.
6 Using the Alarm details for the Gauge Threshold Crossing Alert Summary
alarm, note the Unit and Class the alarm is raised against.
7 Select Performance->Performance Monitoring->New.
8 Use the pull-down menus to select the Facility Type, Shelf, Slot and Port
based on the information noted in step 6 and then click on the Retrieve
button.
9 In the list, note the facility that has an Untimed value that has crossed the
threshold value.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-113

Procedure 3-43 (continued)

Gauge Threshold Crossing Alert Summary (724, 725, 726)

Step Action

10 If Then go to
the facility parameter that has crossed the step 11
threshold is ORL (optical return loss)
otherwise step 22

11 If Then go to
the alarm is raised against a pre-amplifier step 12
otherwise step 15

12 Ensure that all LC/SC connectors are correctly mated on each module (for
example, CMD, SCMD, GMD, DSCM) located after the amplifier output. Verify
this on both ends of the connector mating receptacles.
If the alarm remains active, go to step 13.
13 Ensure that the termination plugs are present and are mated correctly on
unused ports. Termination plugs must be present on the SCMD Upgrade Out
port and GMD Group Out ports.
If the alarm remains active, go to step 14.
14 Ensure that the CMD and/or SCMD patch cord connections to the Channel In
and Channel Out ports are not reversed. If a subtending equipment
transmitter is connected to the Channel Out port by mistake, then the alarm
will be raised.
If the alarm remains active, go to step 15.
15 Check the alarmed amplifier power level defined in your EDP against the
provisioned AMP settings in the Craft interface. See Configuration,
323-1661-310 for information on displaying optical facility details.
16 Edit power levels as required. See Configuration, 323-1661-310, for
information on editing the attributes of an optical facility.
If the alarm remains active, go to step 17.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-114 Alarm clearing

Procedure 3-43 (continued)

Gauge Threshold Crossing Alert Summary (724, 725, 726)

Step Action

17
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure that the optical
amplifier is out of service (OOS), then disconnect or
reconnect the fiber.

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Place the alarmed optical amplifier out of service (OOS). For information on
how to put the amplifier OOS, see Configuration, 323-1661-310.
18 Clean and then reconnect the output fibers and connectors at the amplifier.
For instructions on inspecting and cleaning optical fiber, see SLAT and
Channel Procedures, 323-1661-221.
19 Place the amplifier back in-service (IS). For information on how to put the
amplifier IS, see Configuration, 323-1661-310.
20 If the alarm remains active, you may have to clean a specific connector or
connectors that may not be immediately connected to the alarmed amplifier
output. For information on isolating connector losses, perform Procedure 2-9,
Locating a reflective event.
21 If the alarm does not clear, contact your next level of support or your Nortel
support group.
You have completed this procedure.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-115

Procedure 3-43 (continued)

Gauge Threshold Crossing Alert Summary (724, 725, 726)

Step Action

22 Verify and clear any of the following alarms on all of the network elements
before clearing the Gauge Threshold Crossing Alert Summary alarm:
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Group Input Loss Of Signal (712)
• Group Output Loss Of Signal (713)
• Group Loss of Signal (710, 832)
• Input Loss Of Signal (557)
• Loss Of Signal (553, 560)
• Optical Line Fail (610, 541)
• Output Loss Of Signal (572)
• OSC Loss Of Signal (556)
• Shutoff Threshold Crossed (540)

If the alarm remains active, go to step 23.

23 Determine if there are other Gauge Threshold Crossing Alert Summary
alarms raised in the network and begin by troubleshooting the most upstream
Gauge Threshold Crossing Alert Summary alarm. To troubleshoot the most
upstream Gauge Threshold Crossing Alert Summary alarm, verify the optical
patch cord connected to the port reporting the alarm.

Attention: Make sure that the optical patch cord is connected at both ends
and that no problems exist with the optical patch cord. (Clean the connectors.
For instructions on inspecting and cleaning optical fiber, see SLAT and
Channel Procedures, 323-1661-221.)

24 If the alarm is reported against the OPOUT parameter of CMD or SCMD

Channel In VOA facility, make sure that the transmitting subtending
equipment is functioning correctly and transmitting a valid signal.
25 If the alarm is reported against the GRPOPOUT parameter of a SCMD4
Common In VOA facility or the OPR parameter of a SCMD8 Common In
OPTMON facility, it may be a problem at the head end site where the SCMDs
are interconnected using the upgrade ports. Check the patch cords used at
the upgrade ports.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-116 Alarm clearing

Procedure 3-43 (continued)

Gauge Threshold Crossing Alert Summary (724, 725, 726)

Step Action

26 If the alarm is reported against Then verify

the OPIN parameter of a CMDA the connection between the CMD44
Common Out (port 6) and the CMDA
the OPR parameter of a CMDA the connection between the WSS
Common In (port 5) and the CMDA
the OPIN parameter of a LIM amplifier the outside fiber plant
Line A In (port 8) facility (or the OPR
parameter of a LIM OPTMON Line A
In [port 8] facility) and the OPR
parameter of a LIM OSC A Out (port 4)
facility
the OPROSC parameter of a DRA that the OSC of the far-end network
element is functioning correctly and
transmitting a valid signal

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-117

Procedure 3-44
Group Input Loss Of Signal (712)
Use this procedure to clear the Group Input Loss Of Signal (712) alarm. This
alarm is masked by the Circuit Pack Failed (581) alarm.

This alarm is raised on an amplifier facility.

Probable cause
This alarm is raised when an LOS condition is detected at the input of an
SCMD8 (Common In), which occurs when the total input optical power to the
amplifier has fallen below the provisioned LOS threshold level.

The conditions that can cause the input power level to fall below the threshold
level include:
• a disconnected fiber
• a dirty optical fiber connector at the receiver or adjacent transmitter
• a defective fiber optic patch cord
• a defective module
• an incorrect provisioned value
• a reflective event (indicated by Automatic Power Reduction Active (542))
at an upstream booster amplifier or pre-amplifier (DSCM)

The Group Input Loss Of Signal (712) can remain active after the fault is
cleared and the original power level is restored. This behavior occurs because
the power level is lower than the user provisioned LOS threshold plus the
hysteresis value. The hysteresis value is not user provisionable and is set at
3 dB.

Impact
Major, SA (service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-118 Alarm clearing

Procedure 3-44 (continued)

Group Input Loss Of Signal (712)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Have a fiber cleaning kit.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• Have the LOS threshold level for this amplifier.
• Use an account with a level 3 or higher user privilege code (UPC).
• Have a network and site diagram.
Procedure steps

Step Action

1 Verify and clear any of the following alarms on all of the network elements
before clearing this Loss of Signal alarm:
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Input Loss Of Signal (557)
• Optical Line Fail (610, 541)
• Output Loss Of Signal (572)
• Shutoff Threshold Crossed (540)

2 Continue with the next step, if the alarm remains active.

3 Select Facilities->AMP.
4 Verify that the amplifier (AMP) values are correctly provisioned, adjust the
value(s) if required. For information on how to edit amplifier values, see
Configuration, 323-1661-310.
5 Continue with the next step, if the alarm remains active.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-119

Procedure 3-44 (continued)

Group Input Loss Of Signal (712)

Step Action

6 Clear any upstream (either local to the network element reporting the alarm
or other upstream remote network element) related alarms that could be
causing this alarm such as Circuit Pack Failed (581), Circuit Pack Missing
(579), Loss Of Signal (553, 560).

Attention: It may be a problem at the head end site or at the site reporting
the alarm if the SCMD4s are interconnected using the upgrade ports. Check
the patch cords used at the upgrade ports.

Attention: If there are no upstream alarms then verify the optical patch cord
connected to the port reporting the alarm. Make sure that the optical patch
cord is connected at both ends and that there is no problem with the optical
patch cord (clean the connectors, for instructions on inspecting and cleaning
optical fiber, see SLAT and Channel Procedures, 323-1661-221).

7 Continue with the next step, if the alarm remains active.

8 Select Facility->AMP and then select the amp reporting the alarm. Edit the
Input LOS Threshold for the facility reporting the alarm to be 5 dB less than
the current Input LOS Threshold. For example, if the Input LOS Threshold is
-31 dBm, change the Input LOS Threshold to be -36 dBm.
9 Wait at least 1 minute for the LOS alarm to clear.
10 Change the Input LOS Threshold back to the original value.
11 Continue with the next step, if the alarm remains active.
12 Restart the module supporting the alarmed AMP facility. See Chapter 5,
Restart procedures.
13 If the alarm remains active, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-120 Alarm clearing

Procedure 3-45
Group Output Loss Of Signal (713)
Use this procedure to clear the Group Output Loss Of Signal (713) alarm. This
alarm is masked by the Circuit Pack Failed alarm.

This alarm is raised on an amplifier facility.

Probable cause
This alarm is raised when the total output optical power from the amplifier
within the SCMD8 has fallen below the provisioned optical power out
threshold level.

The conditions that can cause the output power level to fall below the
threshold level include:
• a disconnected fiber
• a dirty optical fiber connector
• a defective fiber optic patch cord
• a defective module
• incorrect provisioning data

The Group Output Loss Of Signal (713) can remain active after the fault is
cleared and the original power level is restored. This is because the power
level is lower than the user provisioned LOS threshold plus the hysteresis
value. The hysteresis value is not user provisionable and is set at 3 dB.

Impact
Major, SA (service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have the LOS threshold level value for this amplifier.
• Use an account with a level 3 or higher user privilege code (UPC).
• Have a fiber cleaning kit.
• Have a network and site diagram.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-121

Procedure 3-45 (continued)

Group Output Loss Of Signal (713)

Procedure steps
Step Action

1 Select Facilities->AMP.
2 Verify that the amplifier (AMP) values are correctly provisioned, adjust the
value(s) if required. For information on how to edit amplifier values, see
Configuration, 323-1661-310.
3 Continue with the next step, if the alarm remains active.
4 Check for upstream alarms. Clear active alarms using the procedures in this
document.
5 Continue with the next step, if the alarm remains active.
6 Select Facility->AMP and then select the amp reporting the alarm. Edit the
Output LOS Threshold for the facility reporting the alarm to be 5 dB less than
the current Output LOS Threshold. For example, if the Output LOS Threshold
is -8, change the Output LOS Threshold to be -13.
7 Wait at least 1 minute for the LOS alarm to clear.
8 Change the Output LOS Threshold back to the original value.
9 Continue with the next step, if the alarm remains active.
10 Replace the alarmed SCMD8. See Procedure 4-12, Replacing the SCMDx
module.
11 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-122 Alarm clearing

Procedure 3-46
Group Loss of Signal (710, 832)
Use this procedure to clear the Group Loss of Signal (710, 832) alarm. This
alarm is masked by the Circuit Pack Failed alarm.

This procedure applies to:

• the variable optical attenuator (VOA) facility at the SCMD4 Common In
demux path
• the OPTMON facility at the SCMD4 or CMD44 Channel MUX output port
Probable cause
The alarm is raised when a loss of signal is detected at the:
• VOA facility at the Common In demux path
• OPTMON facility at the SCMD4 Channel MUX output port

The conditions that can cause this alarm include:

• a disconnected, or defective fiber optic patch cord
• a dirty optical fiber connector
• a defective module
• a provisioning error
• a reflective event (indicated by Automatic Power Reduction Active (542))
at an upstream booster amplifier or pre-amplifier (DSCM)

The Group Loss of Signal (710, 832) can remain active after the fault is
cleared and the original power level is restored. This is because the power
level is lower than the user provisioned LOS threshold plus the hysteresis
value. The hysteresis value is not user provisionable and is set at 3 dB.

Impact
Major, SA (service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-123

Procedure 3-46 (continued)

Group Loss of Signal (710, 832)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Have a fiber cleaning kit.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• If required, have a replacement module.
• Have a network and site diagram.
Procedure steps

Step Action

1 If the alarm is raised against the Then go to

VOA facility step 3
OPTMON facility step 2

2 Verify the optical patch cord between the subtending equipment and the
SCMD4 or CMD44 channel input port.
• Make sure that the patch cord is connected at both ends and that there
is no problem with the optical patch cord. (Clean the connectors. For
instructions on inspecting and cleaning optical fiber, see SLAT and
Channel Procedures, 323-1661-221.)
• Make sure that the transmitting subtending equipment is functioning
correctly and transmitting a valid signa.l
If the alarm does not clear, then go to step 4.
3 Verify and clear any of the following alarms on all of the network elements
before clearing this Loss of Signal alarm:
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Input Loss Of Signal (557)
• Optical Line Fail (610, 541)
• Output Loss Of Signal (572)
• Shutoff Threshold Crossed (540)
4 Select Facilities->VOA or OPTMON.
5 Verify that values are correctly provisioned, adjust the value(s) if required. For
information on how to edit facility values, see Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-124 Alarm clearing

Procedure 3-46 (continued)

Group Loss of Signal (710, 832)

Step Action

6 Continue with the next step, if the alarm remains active.

7 Clear any upstream (either local to the network element reporting the alarm
or other upstream remote network element) related alarms that could be
causing this alarm such as Circuit Pack Failed (581), Circuit Pack Missing
(579), Loss Of Signal (553, 560).

Attention: It may be a problem at the head end site or at the site reporting
the alarm if the SCMD4s are interconnected using the upgrade ports. Check
the patch cords used at the upgrade ports.

Attention: If there are no upstream alarms then verify the optical patch cord
connected to the port reporting the alarm. Make sure that the optical patch
cord is connected at both ends and that there is no problem with the optical
patch cord (clean the connectors, for instructions on inspecting and cleaning
optical fiber, see SLAT and Channel Procedures, 323-1661-221).

8 Continue with the next step, if the alarm remains active.

9 Select Facility->VOA or OPTMON and then select the facility reporting the
alarm. Edit the LOS Threshold for the facility reporting the alarm to be 5 dB
less than the current LOS Threshold. For example, if the LOS Threshold is
-26, change the LOS Threshold to be -31.
10 Wait at least 1 minute for the LOS alarm to clear.
11 Change the LOS Threshold back to the original value.
12 Continue with the next step, if the alarm remains active.
13 Restart the module supporting the alarmed VOA, or OPTMON facility. See
Chapter 5, Restart procedures.
14 If the alarm remains active, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-125

Procedure 3-47
High Temperature (596)
Use this procedure to clear the High Temperature (596) alarm. This alarm is
masked by the Circuit Pack Mismatch (580) alarm.

This alarm is raised on the following modules:

• 4 Channel Mux/Demux (CMD4)
• Serial 4 Channel Mux/Demux (SCMD4)
• Serial 8 Channel Mux/Demux (SCMD8)
• Channel Mux/Demux Amplifier (CMDA)
• Dual Optical Service Channel (DOSC)
• Group Mux/Demux (GMD)
• Uni Optical Service Channel (UOSC)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Optical Power Monitor (OPM)
• Wavelength Selective Switch (WSS)
• Distributed Raman Amplifier (DRA)

Probable cause
This alarm is raised when the nominal temperature of the module is too high.

This alarm is caused by one of the following conditions:

• The central office temperature is too high.
• The cooling unit (fan assembly) is not functioning correctly on the module.
• There is a problem with the module.

Impact
Major, SA (service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-126 Alarm clearing

Procedure 3-47 (continued)

High Temperature (596)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Have access to replacement modules.
• Have a flathead screwdriver.

Procedure steps
Step Action

1 Make sure that the central office temperature does not exceed the operating
temperature requirements of the equipment. See Planning Guide,
NTT840FE, for operating environment specifications.
2 If the office temperature is Then
within the operating temperature go to step 3
not within the operating temperature correct the office temperature

3
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

4 Inspect the grill of the fan assembly of that module. Remove any debris or
vacuum any dust.
5 If the alarm is raised against a GMD, UOSC, or DOSC check the air filter to
ensure there is no blockage and replace it if required. See Procedure 4-20,
Replacing air filters.
If the alarm remains active, go to step 6.
6 Replace the fan assembly in the module. See Procedure 4-19, Replacing the
fan assembly in a UOSC, GMD, or DOSC or Procedure 4-18, Replacing the
fan assembly in an amplifier.
If the alarm remains active, go to step 7.
7 Replace the alarmed module. See Chapter 4, Module and component
replacement.
8 Now that the original alarmed module is removed from the shelf, remove the
replacement fan assembly that you installed in step 6, and replace it with the
original fan assembly. It is unlikely that the fan assembly was the problem.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-127

Procedure 3-48
ILAN 1 Port Failure (547)
Use this procedure to clear the ILAN 1 Port Failure (547) alarm. This alarm is
masked by the Circuit Pack Failed alarm.

Probable cause
This alarm is raised when the interconnect local area network (ILAN) port 1
on the GMD, UOSC, or DOSC does not receive any Ethernet packets. This
occurs if there is a bad Ethernet connection or the ILAN 1 port fails.

This alarm is also raised if the adjacent equipment connected to the ILAN port
has undergone a restart operation. The alarm clears once the restart has
completed.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have DCN information for your network.
• Use an account with a level 3 or higher user privilege code (UPC).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-128 Alarm clearing

Procedure 3-48 (continued)

ILAN 1 Port Failure (547)

Procedure steps
Step Action

1 Check the DCN information to determine if the ILAN 1 port should be

enabled.
If the ILAN should be Then go to
enabled step 3
disabled step 2

2 Delete the alarmed ILAN port. See Configuration, 323-1661-310, for

information on deleting an ILAN 1 port. You have completed this procedure.

Attention: By deleting the ILAN port, you lose any established connections
that use this port.

3 Check that the ILAN configuration at both ends of the Ethernet link are the
same. See Configuration, 323-1661-310, for information on how to view ILAN
port information.
4 If the configuration is different, edit the configuration as required. See
Configuration, 323-1661-310, for information on how to edit ILAN port
information.
5 Continue with the next step, if the alarm remains active.
6 Ensure that the appropriate cable is correctly connected to the alarmed
ILAN-1 port. See Installation, 323-1661-201, for cabling procedures.
7 Continue with the next step, if the alarm remains active.
8 The cable connected to the ILAN port may be defective. Replace the cable.
9 If the alarm does not clear, contact your next level of support to verify any
network issues or LAN equipment issues.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-129

Procedure 3-49
ILAN 2 Port Failure (548)
Use this procedure to clear the ILAN 2 Port Failure (548) alarm. This alarm is
masked by the Circuit Pack Failed alarm.

Probable cause
This alarm is raised when the interconnect local area network (ILAN) port 2
on the GMD, UOSC, or DOSC does not receive any Ethernet packets. This
occurs if there is a bad Ethernet connection or the ILAN 2 port fails.

This alarm is also raised if the adjacent equipment connected to the ILAN port
has undergone a restart operation. The alarm clears once the restart has
completed.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have DCN information for your network.
• Use an account with a level 3 or higher user privilege code (UPC).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-130 Alarm clearing

Procedure 3-49 (continued)

ILAN 2 Port Failure (548)

Procedure steps
Step Action

1 Check the DCN information to determine if the ILAN 2 port should be

enabled.
If the ILAN should be Then go to
enabled step 3
disabled step 2

2 Delete the alarmed ILAN port. See Configuration, 323-1661-310, for

information on deleting an ILAN 2 port. You have completed this procedure.

Attention: By deleting the ILAN port, you lose any established connections
that use this port.

3 Check that the ILAN configuration at both ends of the Ethernet link are the
same. See Configuration, 323-1661-310, for information on how to view ILAN
port information.
4 If the configuration is different, edit the configuration as required. See
Configuration, 323-1661-310, for information on how to edit ILAN port
information.
5 Continue with the next step, if the alarm remains active.
6 Ensure that the appropriate cable is correctly connected to the alarmed
ILAN-2 port. See Installation, 323-1661-201, for cabling procedures.
7 Continue with the next step, if the alarm remains active.
8 The cable connected to the ILAN port may be defective. Replace the cable.
9 If the alarm does not clear, contact your next level of support to verify any
network issues or LAN equipment issues.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-131

Procedure 3-50
Incoming Network Access Violation (268)
Use this procedure to clear the Incoming Network Access Violation (268)
alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC) or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when a connection request is received from a denied
address.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Be the designated Security Authority (with at least a user privilege code
(UPC) level 4).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Follow your company policy for network access violations.

2 Select Faults -> Clear Security Alarms.
3 Click Yes to proceed with clearing the security alarms.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-132 Alarm clearing

Procedure 3-51
Incomplete Software Lineup (92)
Use this procedure to clear the Incomplete Software Lineup (92) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when a software load file is missing or a software upgrade
or module replacement procedure was not completed correctly.

Attention: If this alarm is raised during an upgrade activity, make sure that
you follow the appropriate procedure for the upgrade. If the alarm remains
active after correctly following the appropriate procedure, contact your next
level of support or your Nortel support group.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Have an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Select Configuration->Release Management.

2 Verify the current load release on the UOSC, DOSC, or GMD.
3 Retrieve all active alarms (enabled and disabled) on the system, see
Procedure 2-1, Displaying active alarms and Procedure 2-2, Displaying
active disabled alarms. Record the current state of the system.
4 If both the Software Configuration Unknown and Incomplete Software Lineup
alarms are active, but no Software Mismatch alarm is active, a software
upgrade or module replacement procedure might not have been followed
correctly. In this case, complete the upgrade or replacement according to the
appropriate NTP procedure.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-133

Procedure 3-51 (continued)

Incomplete Software Lineup (92)

Step Action

5 If the alarm remains active, perform a software load transfer. See

Configuration, 323-1661-310.
6 Wait for the load transfer to complete. Contact your next level of support or
your Nortel support group for assistance if necessary.
7 Perform a UOSC, DOSC, or GMD warm restart. See Procedure 5-1,
Performing a module warm restart.
8 Retrieve all alarms to ensure that the system is restored to its original state.
If any alarm not recorded in step 3 is displayed, refer to the appropriate alarm
clearing procedure in this chapter.
9 If the Incomplete Software Lineup alarm does not clear, contact your next
level of support or your Nortel support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-134 Alarm clearing

Procedure 3-52
Input Loss Of Signal (557)
Use this procedure to clear the Input Loss Of Signal (557) alarm. This alarm
is masked by the Shutoff Threshold Crossed alarm. On Raman facilities, this
alarm is masked in Managed mode.

This procedure applies to amplifier facilities.

Probable cause
This alarm is raised when the total input optical power to the amplifier has
fallen below the provisioned LOS threshold level.

The conditions that can cause the input power level to fall below the threshold
level include:
• a disconnected fiber
• a dirty optical fiber connector at the receiver or adjacent transmitter
• a failure of the transmitting laser at the adjacent Tx
• a defective fiber optic patch cord
• a defective module
• an incorrect provisioned value
• a reflective event (indicated by Automatic Power Reduction Active (542))
at an upstream booster amplifier or pre-amplifier (DSCM)

The Input Loss Of Signal (557) can remain active after the fault is cleared and
the original power level is restored. This is because the power level is lower
than the user provisioned LOS threshold plus the hysteresis value. The
hysteresis value is not user provisionable and is set at 3 dB.

Impact
Major, SA (service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Have a fiber cleaning kit.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-135

Procedure 3-52 (continued)

Input Loss Of Signal (557)

• Have the LOS threshold level for this amplifier.

• Use an account with a level 3 or higher user privilege code (UPC).
• Have a network and site diagram.

Procedure steps

Step Action

1 Verify if the Optical Line Fail (610, 541) alarm is active, and clear it using the
procedure in this document. If the alarm remains active, go to step 2.
2 Verify if Automatic Power Reduction Active (542) is active at the upstream
booster amplifier or pre-amplifier that is providing output power to the
alarmed amplifier. Clear it using the procedure in this document.
If the alarm remains active, go to step 3.
3 Continue to check for the Automatic Power Reduction Active (542) alarm
further upstream and clear it using the procedure in this document.
4 Check for Input Loss Of Signal (557) alarms at Amps further upstream and
repeat step 1 to step 3. If the alarm remains active, go to step 5.
5 Select Facilities->AMP.
6 Verify that the amplifier (AMP) values are correctly provisioned, adjust the
value(s) if required. For information on how to edit amplifier values, see
Configuration, 323-1661-310.
If the alarm remains active, go to step 7.
7
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure that the optical
amplifier is out of service (OOS).

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-136 Alarm clearing

Procedure 3-52 (continued)

Input Loss Of Signal (557)

Step Action

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

8 Place the alarmed amplifier out of service (OOS). See Configuration,

323-1661-310, for information on placing equipment OOS.
9 Clean the connector of the alarmed amplifier receiver.
10 Place the amplifier back in-service (IS). See Configuration, 323-1661-310, for
information on placing equipment IS. If the alarm remains active, go to
step 11.
11 Check for upstream alarms. Clear active alarms using the procedures in this
document. If the alarm remains active, go to step 12.
12 Select Facility->AMP and then select the amp reporting the alarm. Edit the
Input LOS Threshold for the facility reporting the alarm to be 5 dB less than
the current Input LOS Threshold. For example, if the Input LOS Threshold is
-31 dBm, change the Input LOS Threshold to be -36 dBm.
13 Wait at least 1 minute for the LOS alarm to clear.
14 Change the Input LOS Threshold back to the original value. If the alarm
remains active, go to step 15.
15 Replace the alarmed amplifier. See the following procedures:
• for SLA, LIM, MLA and MLA2 modules: Procedure 4-1, Replacing the
amplifier module
• for CMDA: Procedure 4-2, Replacing the CMDA module
• for SCMDx: Procedure 4-12, Replacing the SCMDx module
• for DRA modules: Procedure 4-16, Replacing the DRA module with the
equivalent DRA

16 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-137

Procedure 3-53
Internal Mgmt Comms Suspected (438)
Use this procedure to clear the Internal Mgmt Comms Suspected (438) alarm.

This alarm is raised on the following modules:

• 4 Channel Mux/Demux (CMD4)
• Serial 4 Channel Mux/Demux (SCMD4)
• Serial 8 Channel Mux/Demux (SCMD8)
• Channel Mux/Demux Amplifier (CMDA)
• Dual Optical Service Channel (DOSC)
• Group Mux/Demux (GMD)
• Uni Optical Service Channel (UOSC)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Optical Power Monitor (OPM)
• Wavelength Selective Switch (WSS)
• Distributed Raman Amplifier (DRA)

This alarm has a hold-off time of four minutes and hold on time of 30 seconds.

Probable cause
This alarm is raised when there is a communication channel failure between
a subtending module and the GMD, DOSC, or UOSC. The alarm indicates
which subtending module is having the communication failure.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Use an account with a level 3 or higher user privilege code (UPC).
• If required, have a replacement module.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-138 Alarm clearing

Procedure 3-53 (continued)

Internal Mgmt Comms Suspected (438)

Procedure steps
Step Action

1 Identify the module raising the alarm. See “Identifying the alarmed entity” on
page 1-9.
2
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Check the Ethernet cable connections on the alarmed modules.

3 If Then
there is a disconnected Ethernet correct the problem, and check if the
cable or other comms connection alarm cleared.
problem between the UOSC, GMD, Go to step 4.
or DOSC and alarmed module
there are no Ethernet cable and Go to step 5.
connection problems

4 Continue with the next step, if the alarm remains active.

5 Power cycle the module, see Chapter 5.
6 Continue with the next step, if the alarm remains active.
7 If the alarm did not clear after performing a power cycle, replace the module
See module replacement procedures in Chapter 4.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-139

Procedure 3-54
Intrusion Attempt (267)
Use this procedure to clear the Intrusion Attempt (267) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
The network element provides intrusion detection by maintaining a count of
the number of consecutive failed login attempts against the user’s originating
address (IP address). This alarm is raised when the number of consecutive
failed login attempts exceeds the provisioned number of allowed login
attempts. This can be the result of an unauthorized person trying to guess
userIDs and passwords to gain access to the network element, or an operator
incorrectly entering a userID or password repeatedly.

If the alarm is raised frequently and unnecessarily, adjust the maximum

number of login attempts. See Configuration, 323-1661-310, for information
on setting default security attributes for a network element.

The Intrusion Attempt alarm clears when one of the following events occurs:
• The provisioned lockout period expires for the last intrusion attempt on the
network element.
• All outstanding detected intrusions are cleared by receiving successful
logins from each of the suspected IP addresses.
• An administrator manually clears the Intrusion Attempt alarm. Note that
the failed login counter does not reset and the alarm will not raise again
until the provisioned lockout period expires.
• A restart of UOSC, GMD, or DOSC.

Attention: The lockout period is provisionable by an administrator.

Impact
Major, NSA (non-service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-140 Alarm clearing

Procedure 3-54 (continued)

Intrusion Attempt (267)

Prerequisites
• Be the designated Security Authority (with at least user privilege code
(UPC) level 4).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Follow your company policy for network access violations.

2 Select Faults -> Clear Security Alarms.
3 Click Yes to proceed with clearing the security alarms.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-141

Procedure 3-55
Invalid Site Topology (872)
Use this procedure to clear the Invalid Site Topology (872) alarm.

This alarm is raised on the shelf.

Probable cause
This alarm is raised if there are more than two NEs at the same site in the
same Optical System Identifier (OSID).

Attention: This alarm may be raised if there is a duplicate site provisioned

within an OSID.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Be the designated Security Authority with user privilege code (UPC) 4.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Identify the network elements raising this alarm.

2 Determine from network plans or other documents which network element
has the correct Site ID and OSID.
3 Login to the network element with the duplicate Site ID and OSID.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-142 Alarm clearing

Procedure 3-55 (continued)

Invalid Site Topology (872)

Step Action

4 Select Configuration->Node Information->Shelf

The Shelf window opens.
5
CAUTION
Risk of loss of functionality
Ensure every network element has an unique
Site ID/TID. If you are changing the Site ID/TID of a
network element, ensure that the new Site ID/TID is
unique.

6 View the Site ID and OSID from the Craft: select Configuration->Node
Information->Shelf. Highlight the shelf to display the shelf details in the
Details window. Click the Edit button on the Shelf window
7 Enter the correct OSID in the Optical System ID field.
8 Click the OK button.
The network element restarts automatically, and you are logged out.
9 Ensure that no other Invalid Site Topology alarms exist. If there are other
Invalid Site Topology alarms, repeat this procedure.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-143

Procedure 3-56
Loss Of Signal (553, 560)
Use this procedure to clear the Loss Of Signal (553, 560) alarm. This alarm is
masked by the Circuit Pack Failed (581) alarm.

This procedure applies to variable optical attenuator (VOA) facilities or

OPTMON facilities.

Probable cause
This alarm is raised when:
• a module with a VOA facility is not detecting an input signal
• a module with a OPTMON facility is not detecting an input signal
• optical power transmitted or optical power received have fallen below the
provisioned LOS threshold level

The conditions that can cause this alarm include:

• a disconnected, or defective fiber optic patch cord
• a dirty optical fiber connector
• a defective module
• the transmitting subtending equipment is defective
• a provisioning error
• a reflective event (indicated by Automatic Power Reduction Active (542))
at an upstream booster amplifier or pre-amplifier (DSCM)

The Loss Of Signal (553, 560) can remain active after the fault is cleared and
the original power level is restored. This is because the power level is lower
than the user provisioned LOS threshold plus the hysteresis value. The
hysteresis value is not user provisionable and is set at 3 dB.

Impact
Major, SA (service-affecting)

When a Loss Of Signal alarm is active, a pre-check can result in an Inactive:

LOS condition, rather than a Pass or Fail. For more information on the
pre-check function, see Configuration, 323-1661-310.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-144 Alarm clearing

Procedure 3-56 (continued)

Loss Of Signal (553, 560)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Have a fiber cleaning kit.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• If required, have a replacement module.
• Have a network and site diagram.

Procedure steps
Step Action

1 Verify and clear any of the following alarms on all of the network elements
before clearing the Loss of Signal alarm:
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Input Loss Of Signal (557)
• Optical Line Fail (610, 541)
• Output Loss Of Signal (572)
• Shutoff Threshold Crossed (540)

2 Select Facilities->VOA or OPTMON.

3 Verify that values are correctly provisioned, adjust the value(s) if required. For
information on how to edit facility values, see Configuration, 323-1661-310.
4 Continue with the next step, if the alarm remains active.
5 If the alarm is raised against Then go to
a CMD channel input port (VOA facility 3,5,7,9,11,13,15,17), or step 6
a CMD4 common output port (OPTMON facility 2), or a CMD44
channel input port (1...87)
any other port step 8

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-145

Procedure 3-56 (continued)

Loss Of Signal (553, 560)

Step Action

6 Verify the optical patch cord between the subtending equipment and the CMD
channel input port:
• Make sure it is connected at both ends and that there is no problem with
the optical patch cord (clean the connectors; for instructions on
inspecting and cleaning optical fiber, see SLAT and Channel Procedures,
323-1661-221).
• Make sure that the transmitting subtending equipment is functioning
correctly and transmitting a valid signal.

7 If the alarm is not cleared on Then go to

a CMD channel input port (VOA facility 3,5,7,9,11,13,15,17), step 12
or a CMD4 common output port (OPTMON facility 2)
a CMD44 channel input port (1...87) step 13

8 Clear any upstream (either local to the network element reporting the alarm
or other upstream remote network element) related alarms that can be
causing this alarm, such as Circuit Pack Failed (581), Circuit Pack Missing
(579), Loss Of Signal (553, 560).

Attention: If there are no upstream alarms, verify the optical patch cord
connected to the port reporting the alarm. Make sure that the optical patch
cord is connected at both ends and that there is no problem with the optical
patch cord (clean the connectors; for instructions on inspecting and cleaning
optical fiber, see SLAT and Channel Procedures, 323-1661-221).

If the alarm does not clear, go to step 9.

9 Select Facility->VOA or OPTMON and then select the facility reporting the
alarm. Edit the LOS Threshold for the facility reporting the alarm to be 5 dB
less than the current LOS Threshold. For example, if the LOS Threshold is
-26 dBm, change the LOS Threshold to be -31 dBm.
10 Wait at least 1 minute for the LOS alarm to clear.
11 Change the LOS threshold back to the original value. If the alarm does not
clear, go to step 12.
12 Restart the module supporting the alarmed facility. See Chapter 5, Restart
procedures.
13 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-146 Alarm clearing

Procedure 3-57
Member Shelf Unknown (719)
Use this procedure to clear the Member Shelf Unknown (719) alarm.

This alarm is raised on the shelf.

Probable cause
This alarm is raised under the following conditions:
• The TID (NE name) was changed on the Primary with more than one user
login session open on a member shelf.
• A Member shelf is provisioned with a shelf type that is unsupported by the
TID Primary shelf.
• If a Member is provisioned manually on the Primary, the Member Shelf
Unknown alarm will be raised until either communications is established
between the Primary and its Member, or a 5 minute hold off has expired.
This will also occur after each Primary Restart.
• A duplicate Primary shelf exists. The alarm is raised on the Primary shelf
which attempted to communicate with a Member shelf which is already
associated with another Primary shelf.
Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC).
• Have a network plan or other documents that allow you to determine the
valid Primary.
• Have the IP address of all shelves within the consolidated TID.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Clear any Duplicate Primary Shelf alarms present, see Procedure 3-36,
Duplicate Primary Shelf (714).
2 Login to the Primary shelf. For the Craft commands, see Configuration,
323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-147

Procedure 3-57 (continued)

Member Shelf Unknown (719)

Step Action

3 Select the TID-consolidated shelf from the Navigation tree and then select
Configuration->Node Information->Member shelves. Retrieve the Member
table of the consolidated TID-consolidated shelf.
4 Determine if the provisioned Member IP, software version, shelf type, or
Member names are synchronized and/or supported by the current TID
Primary shelf.
If the provisioned Member shelf has Then go to
an incorrect IP Address provisioned in the step 5
Member Shelves screen
a software version that is unsupported by the TID step 7
Primary shelf
a shelf type that is unsupported by the TID step 8
Primary shelf
a different SID/TID from the TID Primary shelf step 9

5 Either get the IP address from the network plan, or login to the Member shelf
directly (you may need Challenge Response, see Configuration,
323-1661-310, for login procedures) and check the shelf IP Address of this
Member shelf (select Configuration->Comms Setting
Management->Interfaces->IP and note the SHELF-x IP Address).
6 Return to the Member Shelves screen in the Consolidated TID network
element and select the member shelf with the “Member Shelf Unknown”
alarm.
Click the Edit button, change the IP address to the one noted in step 5, and
then click the OK button.
Go to step 10.
7
CAUTION
Risk of loss of functionality
Failure to sync the software release can cause the
software system not to recognize or interpret
commands correctly, which can affect management or
communications to that member shelf.

Upgrade the appropriate shelf (Member or Primary) to a software version

supported by the Primary shelf. See Configuration, 323-1661-310.
Go to step 10.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-148 Alarm clearing

Procedure 3-57 (continued)

Member Shelf Unknown (719)

Step Action

8 If the shelf type is unsupported, remove it from the Consolidated TID and see
your network plan for appropriate provisioning. Also, log into the Member
shelf directly (may need Challenge Response, see Configuration,
323-1661-310 for login procedures) and confirm that in Configuration->Node
Information->Self screen that the TID consolidation details are correct.
9 Confirm that the Member has the same SID/TID as its Primary. If not, edit the
NE Name on the member shelf to be the same as the Primary. See the
procedure on displaying and changing the NE Name (target identifier (TID) in
Configuration, 323-1661-310.

10 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-149

Procedure 3-58
Member Shelf Unreachable (717)
Use this procedure to clear the Member Shelf Unreachable (717) alarm.

This alarm is raised on the shelf.

Probable cause
This alarm is raised when IP communications capability between a Member
shelf and its Primary shelf are unavailable.

This alarm is expected during initial commissioning operations. This alarm is

raised after five minutes.

TID Consolidation auto-associates when a Primary shelf establishes

communications with a Member shelf of the same Site ID, and unique
Shelf-ID. Isolated provisioning of TID Consolidation members from their
Primary shelf will populate all parameters once COMMs association is
established. This will prevent Unreachable alarms due to pre-provisioning of
the Primary. Alternatively, the member shelf can be put out of service and
deleted from the Primary shelf to clear the alarm.

Attention: If a Member shelf is provisioned manually on the Primary shelf,

the Member Shelf Unknown alarm will be raised until either communications
is established between Primary and its Member, or a five minute hold off has
expired. This will occur after each Primary Restart.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Have a network plan or other documents that allow you to determine the
valid Primary in a Consolidated TID node.
• Have a valid primary shelf in a consolidated TID node.
• Have the IP address of all shelves within the consolidated TID.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-150 Alarm clearing

Procedure 3-58 (continued)

Member Shelf Unreachable (717)

Procedure steps
Step Action

1 Log into the Primary shelf. For the Craft commands, see Configuration,
323-1661-310.
2 Retrieve the Member table of the Primary shelf to identify which nodes are
affected. Go to the Craft menu, select Configuration->Node
Information->Member shelves.
3 From the results of the query in step 2, determine which shelves are
exhibiting the alarm.
If Then
all shelves within the the issue is with the Primary shelf. Go to
Consolidated TID display the step 4
same fault
only one shelf within the go to step 5
Consolidated TID displays the
fault.

4 Refer to the network plan to verify that all communications required for TID
Consolidation operation are provisioned correctly:
• Check for any ILAN alarms matching your intended ILAN configuration
between Primary and Member. If alarms exist, perform ILAN alarm
clearing procedures in this book.
• Confirm that the ILAN connection between the Primary and its Member
is provisioned and correctly physically connected. See the ILAN
provisioning procedures in Configuration, 323-1661-310.
• Confirm that an OSPF circuit is provisioned for all ILANs involved in the
Consolidated TID to the default router. See the OSPF Circuit provisioning
in Configuration, 323-1661-310 and your network plan.
• Confirm that MAC filtering settings are correct and that the Primary shelf
can ping the Shelf IP of the Member shelf with the alarm. See
Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-151

Procedure 3-58 (continued)

Member Shelf Unreachable (717)

Step Action

• Confirm with your engineering documentation that Site ID, Shelf-ID and
IP addresses are provisioned according to your engineering diagram.
— If the Site ID is incorrect according to your diagram, please edit to the
Consolidated Site ID using procedure “Edit shelf information” in
Configuration, 323-1661-310.
— If IP addresses do not match what is intended, use the procedure
“Edit communications settings” in Configuration, 323-1661-310.
— If the Shelf-ID is not provisioned according to the diagram, and the
network LAN cannot be altered to accommodate this provisioning
mismatch, a system re configuration of that shelf will be required to
correctly set the Shelf-ID, Contact Nortel technical support.
5 Attempt to log directly into the Member shelf displaying the fault and perform
the procedure to clear the Primary Shelf Unreachable (716). See
Configuration, 323-1661-310.
6 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-152 Alarm clearing

Procedure 3-59
Optical Line Fail (610, 541)
Use this procedure to clear the Optical Line Fail (610, 541) alarm. This alarm
masks the Automatic Shutoff (590, 942) alarm.

This procedure applies to the OPTMON and AMP facilities.

DANGER
Risk of radiation exposure
If light is used to test the broken fiber (with a light source or an
optical time domain reflectometer [OTDR]), certain automatic
laser shutoff (ALSO) and loss of signal (LOS) alarms can clear.
When the shelf detects light, the alarms clear and the amplifier
facility is powered up. This is an expected behavior because a
shelf cannot distinguish between a light source from an optical
test set or a light source from a shelf.

Make sure that the adjacent optical amplifiers are out of

service (OOS) when performing fiber repairs.

Probable cause
This alarm is normally raised when there is a fiber break or an intermediate
connector disconnect between neighboring sites, or DRA and LIM modules.

Impact
Major, SA (service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• If required, have a replacement module or fiber patch cord.
• Have a fiber cleaning kit.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-153

Procedure 3-59 (continued)

Optical Line Fail (610, 541)

Procedure steps
Step Action

1
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure that the optical
amplifier is out of service (OOS), then disconnect or
reconnect the fiber.

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

If the site reporting the alarm has an MLA or MLA2 module, put the booster
amplifier in the OOS state. If the neighboring site also has an MLA or MLA2,
put its booster amplifier in the OOS state. If the site reporting the alarm has
a DRA, put the RAMAN facilities at both ends of the link in the OOS state. For
information on how to put the booster amplifier and the RAMAN facilities
OOS, see Configuration, 323-1661-310.
2 Take the appropriate action to repair the fiber break or intermediate connector
disconnect between the site reporting the alarm and the neighboring site.
3 Reconnect, replace or repair the fiber.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-154 Alarm clearing

Procedure 3-59 (continued)

Optical Line Fail (610, 541)

Step Action

4 Select your next step.

If the affected fiber span Then go to
is on a Stretched Span without Raman Procedure 6-1, Recovering from
amplification a fiber cut on a Stretched Span
(no Raman amplification) on
page 6-2
is on a Stretched Span with Procedure 6-2, Recovering from
Raman amplification a fiber cut on a Stretched Span
with Raman amplification on
page 6-5
is not on a Stretched Span step 5

5 Place the amplifiers back in-service (IS). For information on how to put the
amplifier IS, see Configuration, 323-1661-310.
6 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-155

Procedure 3-60
OSC Link Failed (555)
Use this procedure to clear the OSC Link Failed (555) alarm. This alarm is
masked by the OSC Loss of Signal alarm.

This procedure applies to OSC facilities.

Probable cause
This alarm is raised when the OSC facility with OSC Link Failed (555) alarm
cannot establish communications with the OSC facility at the remote end of
the link.

The conditions that can cause this alarm include:

• a defective OSC fiber linking the OSC facilities
• a miss-connected or crossed fiber
• a defective connector on the far-end transmit module
• a remote module failure
• a disabled (out of service [OOS]) OSC link on the remote system
• an upstream UOSC, DOSC or GMD has undergone a restart operation.
The alarm clears once the restart has completed.
Impact
Major, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have a fiber cleaning kit.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-156 Alarm clearing

Procedure 3-60 (continued)

OSC Link Failed (555)

Procedure steps
Step Action

1 Verify that the OSC facility at the remote end is functioning correctly. Perform
the necessary actions to clear alarms on the remote end such as the OSC
Loss Of Signal (556) alarm.
2 Continue with the next step, if the alarm remains active.
3
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Verify the fiber on the alarmed OSC facility.

• Check if the fibers are connected.
• Check if the fibers are dirty. If so, clean them. For instructions on
inspecting and cleaning optical fiber, see, SLAT and Channel
Procedures, 323-1661-221.
• Check the fibers and ensure they are not crossed, looped back, or
mis-connected.
4 Continue with the next step, if the alarm remains active.
5 Perform a warm restart on the alarmed module. See Procedure 5-1,
Performing a module warm restart.
6 Continue with the next step, if the alarm remains active.
7 Power cycle the alarmed module. See Procedure 5-4, Performing a power
cycle.
8 Continue with the next step, if the alarm remains active.
9 Replace the alarmed module, see “Module and component replacement” on
page 4-1.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-157

Procedure 3-61
OSC Loss Of Signal (556)
Use this procedure to clear the OSC Loss Of Signal (556) alarm. This alarm
masks the OSC Link Fail and OSC Signal Degrade alarms. It is masked by the
Circuit Pack Failed alarm.

This procedure applies to OSC facilities.

Probable cause
This alarm is raised when the optical signal for this Optical Service Channel
(OSC) facility falls below a fixed threshold. One or more of the following
conditions can raise this alarm:
• a defective or dirty fiber linking the OSC ports
• a miss-connected or unconnected fiber at the alarmed OSC port
• a disabled (out of service, [OOS]) OSC link on the remote network
element
• a powered down remote network element
Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• If required, have a replacement module or fiber patch cord.
• Have a fiber cleaning kit.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-158 Alarm clearing

Procedure 3-61 (continued)

OSC Loss Of Signal (556)

Procedure steps
Step Action

1 Log into the network element at the remote end of the alarmed OSC link.
Ensure that the OSC facility is not out of service. See Configuration,
323-1661-310, for information on how to display facility details.
If Then
the remote network element has been the OSC Loss of Signal alarm is a
powered down result of this condition and will clear
when this condition no longer exists.
the remote network element has not continue with step 2
been powered down

2
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Verify the fiber on the alarmed OSC facility.

• Check if the fibers are connected?
• Check if the fibers are dirty. If so, clean them. For instructions on
inspecting and cleaning optical fiber, see, SLAT and Channel
Procedures, 323-1661-221.
• Check the fibers and ensure they are not crossed, looped back, or
mis-connected.
These need to be verified at the NE raising the alarm and at the upstream NE.
At the alarmed NE, this is the fiber that connects the OSC OUT port (port 4)
of the LIM, SLA, MLA/MLA2 to the UOSC, DOSC, or GMD. At the upstream
NE, this is the fiber that connects the OSC IN port (port 3) of the LIM, SLA,
MLA/MLA2 to the UOSC, DOSC, or GMD.
3 Continue with the next step, if the alarm remains active.
4 Perform a warm restart on the alarmed module. See Procedure 5-1,
Performing a module warm restart.
5 Continue with the next step, if the alarm remains active.
6 Power cycle the alarmed module. See Procedure 5-4, Performing a power
cycle.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-159

Procedure 3-61 (continued)

OSC Loss Of Signal (556)

Step Action

7 Continue with the next step, if the alarm remains active.

8 Replace the alarmed module, see “Module and component replacement” on
page 4-1.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-160 Alarm clearing

Procedure 3-62
OSC Signal Degrade (711)
Use this procedure to clear the OSC Signal Degrade (711) alarm. This alarm
is masked by the OSC Loss of Signal alarm.

This procedure applies to OSC facilities for the GMD, UOSC, or DOSC.

Probable cause
This alarm is raised when OSC bit error rate (BER) crosses the provisioned
threshold and clears when the BER falls below the provisioned threshold by
10 times. For example, if the provisioned BER is 10-6, the average BER has
to drop below 10-7 in order to clear the alarm.

Conditions that can cause the OSC channel BER to exceed the provisioned
threshold include:
• the OSC channel crossed a very long span
• dirty fiber connection

Attention: The OSC signal degrade threshold should lie within the range of
10-4 to 10-10. The default is 10-6.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• If required, have a replacement module or fiber patch cord.
• Have a fiber cleaning kit.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-161

Procedure 3-62 (continued)

OSC Signal Degrade (711)

Procedure steps
Step Action

1 If you want to clear this alarm by Then go to

provisioning a higher OSC Signal Degrade Threshold value step 2
checking and cleaning the dirty fiber step 7

Provision a higher OSC Signal Degrade Threshold value

2 Select Facilities->OSC.
3 Select the OSC facility.
4 Click on the Edit button.
5 Increase the Signal Degrade Threshold value.
The range is 4 (10 -4) to 10 (10 -10).
6 If the alarm does not clear, and the threshold is set at 4 (10 -4), then continue
with step 7.
Clean the dirty fiber
7
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Verify the fiber on the alarmed OSC facility.

• Check if the fibers are connected.
• Check if the fibers are dirty. If so, clean them. For instructions on
inspecting and cleaning optical fiber, see, SLAT and Channel
Procedures, 323-1661-221.
• Check the fibers and ensure they are not crossed, looped back, or
mis-connected.

Attention: These need to be verified at the NE raising the alarm and at the
upstream NE. At the alarmed NE, this is the fiber that connects the OSC OUT
port (port 4) of the LIM, SLA, MLA/MLA2 to the UOSC, DOSC, or GMD. At
the upstream NE, this is the fiber that connects the OSC IN port (port 3) of
the LIM, SLA, MLA/MLA2 to the UOSC, DOSC, or GMD.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-162 Alarm clearing

Procedure 3-62 (continued)

OSC Signal Degrade (711)

Step Action

8 Continue with the next step, if the alarm remains active.

9 Perform a warm restart on the alarmed module. See Procedure 5-1,
Performing a module warm restart.
10 Continue with the next step, if the alarm remains active.
11 Power cycle the alarmed module. See Procedure 5-4, Performing a power
cycle.
12 Continue with the next step, if the alarm remains active.
13 Replace the alarmed module, see “Module and component replacement” on
page 4-1.
14 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-163

Procedure 3-63
OSPF Area Exceeded (543)
Use this procedure to clear the OSPF Area Exceeded (543) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the number of open shortest path first (OSPF)
nodes in an area exceeds 150.

Impact
minor, NSA (non-service-affecting)

Procedure steps
Step Action

1 This alarm indicates a network problem. Contact your network planning

group.

Attention: After the root cause is fixed, it will take up to an hour for this alarm
to clear.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-164 Alarm clearing

Procedure 3-64
Output Loss Of Signal (572)
Use this procedure to clear the Output Loss Of Signal (572) alarm. This alarm
is masked by the Automatic Power Reduction Active (542) and Shutoff
Threshold Crossed alarms.

This procedure applies to amplifier facilities.

Probable cause
This alarm is raised when the total output optical power from the amplifier has
fallen below the provisioned optical power out threshold level.

The conditions that can cause the output power level to fall below the
threshold level include:
• a disconnected fiber
• a dirty optical fiber connector
• a defective fiber optic patch cord
• a defective module
• incorrect provisioning data
• a reflective event (indicated by Automatic Power Reduction Active (542))
at an upstream booster amplifier or pre-amplifier (DSCM)

The Group Output Loss Of Signal (713) can remain active after the fault is
cleared and the original power level is restored because the power level is
lower than the user provisioned LOS threshold plus the hysteresis value. The
hysteresis value is not user provisionable and is set at 3 dB.

Impact
Major, SA (service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-165

Procedure 3-64 (continued)

Output Loss Of Signal (572)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
• Use an account with a level 3 or higher user privilege code (UPC).
• Have a fiber cleaning kit.
• Have the LOS threshold level for this amplifier.
• Have a network and site diagram.

Procedure steps
Step Action

1 Verify if Automatic Power Reduction Active (542) is active at the upstream

booster amplifier or pre-amplifier that is providing output power to the
alarmed amplifier. Clear it using the procedure in this document.
If the alarm remains active, go to step 2.
2 Continue to check for the Automatic Power Reduction Active (542) alarm
further upstream and clear it using the procedures in this document.
If the alarm remains active, go to step 3.
3 Select Facilities->AMP.
4 Verify that the amplifier (AMP) values are correctly provisioned, adjust the
value(s) if required. For information on how to edit amplifier values, see
Configuration, 323-1661-310.
If the alarm remains active, go to step 5.
5 Check for upstream alarms. Clear active alarms using the procedures in this
document. If the alarm remains active, go to step 6.
6 Select Facility->AMP and then select the amp reporting the alarm. Edit the
Output LOS Threshold for the facility reporting the alarm to be 5 dB less than
the current Output LOS Threshold. For example, if the Output LOS Threshold
is -8, change the Output LOS Threshold to be -13.
7 Wait at least 1 minute for the LOS alarm to clear.
8 Change the Output LOS Threshold back to the original value. If the alarm
remains active, go to step 9.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-166 Alarm clearing

Procedure 3-64 (continued)

Output Loss Of Signal (572)

Step Action

9 Replace the alarmed amplifier. See the following procedures:

• for SLA, LIM, MLA and MLA2 modules: Procedure 4-1, Replacing the
amplifier module
• for CMDA: Procedure 4-2, Replacing the amplifier module
• for SCMDx: Procedure 4-12, Replacing the OPM module

10 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-167

Procedure 3-65
Packet Rate Limit Exceeded (591)
Use this procedure to clear the Packet Rate Limit Exceeded (591) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the aggregate number of packets per time period
received by the UOSC, GMD, or DOSC crosses a pre-determined threshold.
Conditions that can trigger this alarm include:
• network issues such as broadcast storms
• internal faults such as a babbling module

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 If this is Then
a network issue no action is required. The network element
communications software clears this alarm automatically
when it stops detecting that the packet rate limit was
exceeded.
an internal fault go to step 2

2 Select Configuration->Comms Setting Management->Interfaces->IP.

3 Verify that the COLAN Subnet Mask is correctly set according to the values
supplied by the LAN administrator.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-168 Alarm clearing

Procedure 3-65 (continued)

Packet Rate Limit Exceeded (591)

Step Action

4 Verify that the COLAN Host Only Mode is set corrected.

Attention: For single or dual GNE configurations it should be set to OFF. For
DCN configurations where all network elements are connected to the COLAN
it should be set to ON.

5 Contact your next level of support or your Nortel support group if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-169

Procedure 3-66
Power Failure - A (594)
Use this procedure to clear the Power Failure - A (594) alarm. This alarm is
masked by the Circuit Pack Mismatch alarm.

This alarm is raised on the following modules:

• 4 Channel Mux/Demux (CMD4)
• Serial 4 Channel Mux/Demux (SCMD4)
• Serial 8 Channel Mux/Demux (SCMD8)
• Channel Mux/Demux Amplifier (CMDA)
• Dual Optical Service Channel (DOSC)
• Uni Optical Service Channel (UOSC)
• Group Mux/Demux (GMD)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Optical Power Monitor (OPM)
• Wavelength Selective Switch (WSS)
• Distributed Raman Amplifier (DRA)

Probable cause
This alarm is raised when the module detects that low or no voltage exists on
the A DC Power feed connection on the module.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Have a standard multimeter.
• Have replacement modules and replacement power cables as required.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-170 Alarm clearing

Procedure 3-66 (continued)

Power Failure - A (594)

Procedure steps
Step Action

1
DANGER
Risk of electric shock
Exercise caution when verifying power connections.
Otherwise, you risk an electric shock.

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Check if the breaker is in the ON (l) position.

2 Use a voltmeter to measure the voltage available at the A power input
connectors on the BIP or Fuse panel.
3 If Then
the input is low (for example -40 V) either insufficient power is coming from
and if the breaker is good the distribution frame or the bay power
supply is faulty. Use your company
procedures to clear the problem.
the input is OK go to step 4

4
DANGER
Risk of electric shock
Ensure the power feeds to the module at the breaker
panel are off before performing power related
maintenance activities.

Check the power cabling and power connectors between the BIP or Fuse
panel and the alarmed module. Adjust power connectors and replace the
power cable as required.
5 If the alarm remains active, replace the alarmed module. See Chapter 4.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-171

Procedure 3-67
Power Failure - B (595)
Use this procedure to clear the Power Failure - B (595) alarm. This alarm is
masked by the Circuit Pack Mismatch alarm.

This alarm is raised on the following modules:

• 4 Channel Mux/Demux (CMD4)
• Serial 4 Channel Mux/Demux (SCMD4)
• Serial 8 Channel Mux/Demux (SCMD8)
• Channel Mux/Demux Amplifier (CMDA)
• Dual Optical Service Channel (DOSC)
• Uni Optical Service Channel (UOSC)
• Group Mux/Demux (GMD)
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA/MLA2)
• Optical Power Monitor (OPM)
• Wavelength Selective Switch (WSS)
• Distributed Raman Amplifier (DRA)

Probable cause
This alarm is raised when the module detects that low or no voltage exists on
the B DC Power feed connection on the module.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Have a standard multimeter.
• If required, have replacement modules and replacement power cables.
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-172 Alarm clearing

Procedure 3-67 (continued)

Power Failure - B (595)

Procedure steps
Step Action

1
DANGER
Risk of electric shock
Exercise caution when verifying power connections.
Otherwise, you risk an electric shock.

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Check if the breaker is in the ON (l) position.

2 Use a voltmeter to measure the voltage available at the B power input
connectors on the BIP or Fuse panel.
3 If Then
the input is low (for example -40 V) either insufficient power is coming from
and if the breaker is good the distribution frame or the bay power
supply is faulty. Use your company
procedures to clear the problem.
the input is OK go to step 4

4
DANGER
Risk of electric shock
Ensure the power feeds to the module at the breaker
panel are off before performing power related
maintenance activities.

Check the power cabling and power connectors between the BIP or Fuse
panel and the alarmed module. Adjust power connectors and replace the
power cable as required.
5 If the alarm remains active, replace the alarmed module. See Chapter 4.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-173

Procedure 3-68
Primary RADIUS Server Unavailable (583)
Use this procedure to clear the Primary RADIUS Server Unavailable (583)
alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the remote authentication requests to the primary
RADIUS server expires after a user-provisionable timeout and no response is
received from a RADIUS server. Possible reasons why the RADIUS server is
unavailable include:
• the shared secret provisioned for Centralized Security Authentication
(CSA) on the network element does not match the RADIUS server shared
secret
• wrong RADIUS server IP address or port provisioned on the network
element
• the network element IP address is not provisioned on the RADIUS server
as a RADIUS client
• a COLAN or OSC comms problem exists
• the network delay exceeds the provisioned timeout value
• a UDP packet loss or other network problem prevents communication

Attention: Disabling CSA clears this alarm. An alternate security

authentication method is used for login and authentication if CSA is disabled
or if the RADIUS servers are unavailable. For information on security
administration, see Configuration, 323-1661-310.

Impact
minor, NSA (non-service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-174 Alarm clearing

Procedure 3-68 (continued)

Primary RADIUS Server Unavailable (583)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC).
• Have the shared secret.
• Have the IP address of the RADIUS server.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Select Security->Centralized Security Administration.

2 Select the Primary server from the list.
3 Click on the Edit Server button.
4 Verify the IP address of the Primary RADIUS Server is correct and re-enter it
if required.
5 Verify the port number in the Port Number field is correct and re-enter it if
required.
The port number is the UDP port number of the RADIUS server.
6 Increase the time out value in the Timeout Value field.
The Timeout value is the amount of time (in seconds) that is allowed for
communication to occur between the controller and the RADIUS server. The
timeout value can range between 1 and 30 seconds.
7 Click the OK button if any changes were made.
8 Continue with the next step, if the alarm remains active.
9 Return to the Centralized Security Administration window.
10 Click the Set NE Shared Secret button.
11 Enter the shared secret in the Shared Secret field.
12 Re-enter the shared secret in the Shared Secret (confirmed) field.
13 Click the OK button.
14 Continue with the next step, if the alarm remains active.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-175

Procedure 3-68 (continued)

Primary RADIUS Server Unavailable (583)

Step Action

15 If the alarm does not clear, contact your network administrator to verify that
the IP address of the network element has been added to the RADIUS server
and to correct any networking issues.

Attention: Use your RADIUS server documentation to troubleshoot possible

RADIUS server issues.

16 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-176 Alarm clearing

Procedure 3-69
Primary Shelf Unreachable (716)
Use this procedure to clear the Primary Shelf Unreachable (716) alarm.

This alarm is raised at the shelf level.

Probable cause
This alarm is raised when IP connectivity between a Member shelf and its
Primary shelf is unavailable.

Attention: This alarm is expected during initial commissioning operations.

Attention: TID Consolidation auto-associates when a Primary shelf

establishes communications with a Member shelf of the same Site ID, and
unique Shelf-ID. Isolated Provisioning of TID Consolidation members from
their Primary shelf will populate all parameters once COMMs association is
established. This will prevent Unreachable alarms due to pre-provisioning of
the Primary. Alternatively, the member shelf can be put out of service and
deleted from the Primary shelf to clear the alarm.

Attention: If a Member shelf is provisioned manually on the Primary shelf,

the Member Shelf Unknown alarm will be raised until either communications
is established between Primary and its Member, or a 5 minute hold off has
expired. This will also occur after each Primary Restart.

Impact
Major, NSA (non-service-affecting)
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-177

Procedure 3-69 (continued)

Primary Shelf Unreachable (716)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Have a network plan or other documents that allow you to determine the
valid primary shelf in a consolidated TID node.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
Procedure steps
Step Action

1 Locate and attempt to log into the TIDC Primary shelf associated with this
Member shelf. For the Craft commands, see Configuration, 323-1661-310.
2 If the Primary shelf login is successful, select the TID-consolidated shelf from
the Navigation tree. Then, select Configuration->Node Information->Member
shelves.
3 Identify which shelf is causing the alarm. If only this member has the Member
Shelf Unreachable alarm raised against it from the Primary, continue with
step 4. If you have already attempted to clear the Member Shelf Unreachable
alarm and this condition still exists, continue with step 6.
4 Log in locally to the shelf displaying the fault. See Configuration,
323-1661-310, for login details.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-178 Alarm clearing

Procedure 3-69 (continued)

Primary Shelf Unreachable (716)

Step Action

5 Refer to the network plan to verify that all communications required for TID
Consolidation operation are provisioned correctly:
• Check for any ILAN alarms matching your intended ILAN configuration
between Primary and Member. If alarms exist, perform ILAN alarm
clearing procedures in this book.
• Confirm that the ILAN connection between the Primary and its Member
is provisioned and correctly physically connected. See the ILAN
provisioning procedures in Configuration, 323-1661-310.
• Confirm that an OSPF circuit is provisioned for all ILANs involved in the
Consolidated TID to the default router. See the OSPF Circuit provisioning
in Configuration, 323-1661-310, and your network plan.
• Confirm with your engineering documentation that Site ID, Shelf-ID and
IP addresses are provisioned according to your engineering diagram.
— If the Site ID is incorrect according to your diagram, please edit to the
Consolidated Site ID using procedure “Edit shelf information” in
Configuration, 323-1661-310.
— If IP addresses do not match what is intended, use the procedure
“Edit communications settings” in Configuration, 323-1661-310.
— If the Shelf-ID is not provisioned according to the diagram, and the
network LAN cannot be altered to accommodate this provisioning
mismatch, a system re-configuration of that shelf will be required to
correctly set the Shelf-ID, contact Nortel technical support.
6 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-179

Procedure 3-70
Provisioning Incompatible (82)
Use this procedure to clear the Provisioning Incompatible (82) alarm. This
alarm is masked by the Circuit Pack Missing alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the physical configuration of the shelf does not
match the provisioned fixed configuration type.

This alarm is also raised on a CHAL or CHALWSS Fixed Configuration if a

CMD of the unexpected group is inserted in a slot pre-reserved for another
CMD group. See the Planning Guide, NTT840FE, for the expected CMD
groups and slots for large fixed configurations.

Attention: This alarm is not raised when the no fixed configuration

(NOFIXC) value is selected for the Fixed Config Type parameter.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC).
• Have the configuration information for the shelf. The supported
configuration types include:
— No Fix Configuration Type - NOFIXC
— Channel Access (Large w/WSS 72 lambda ready) - CHALWSS
— Channel Access (Small w/WSS 326 lambda ready) - CHASWSS
— Channel Access (Large - 36-72 lambda ready) - CHAL
— Channel Access (Small - 16-32 lambda ready) - CHAS
— Line Amplifier NE with optional DSCMs - AMP
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-180 Alarm clearing

Procedure 3-70 (continued)

Provisioning Incompatible (82)

Attention: For equipping rules for each configuration type, see Planning
Guide, NTT840FE.

• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Select Configuration->Node Information->Shelf.

All shelves within a network element are listed.
2 Click the alarmed shelf.
Additional information for that shelf is displayed including the Fixed Config
Type.
3 If Then
the correct Fixed Config Type is there is an equipping error within the shelf,
displayed in the Craft interface remove and replace modules as required.
See Planning Guide, NTT840FE, or your
engineering documentation package
(EDP) for details.
the incorrect Fixed Config Type Click the Edit button, select the correct
is displayed in the Craft configuration type from the Fixed Config
interface Type pull down menu, and click the Ok
button.
Note: NOFIXC is the only configuration
that can be selected. NOFIXC clears this
alarm. To change the shelf to a
configuration other than NOFIXC, you
must decommission the network element.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-181

Procedure 3-71
Raman Failed To Turn On (944)
Use this procedure to clear the Raman Failed To Turn On (944) alarm. This
alarm is masked by the Shutoff Threshold Crossed (540, 940) alarm and the
Automatic Shutoff (590, 942) alarm.

This alarm is raised on a Distributed Raman Amplifier (DRA) module in Local

mode only.

Probable cause
This alarm is raised when the Raman Facility power is above the Turn On
Threshold, but it is still below OSC Shutoff threshold. This condition can occur
after a Shutoff mode when the Raman facility power does not increase enough
to exceed the OSC Shutoff threshold within a certain time. The Raman facility
then goes to Shutoff mode and raises this alarm.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC).
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
Procedure steps
Step Action

1 Check for unexpected alarms from the Craft (Faults—>Active Alarms) and
clear them where possible using the alarm clearing procedures in this
chapter.
2 Check from the Craft (Facilities—>RAMAN) that the correct RAMAN OSC
Shutoff threshold has been provisioned for the fiber type and C/L
Splitter/Couplers (if any are used).
3 Ensure there is no OSC span loss or additional loss.
4 Manually toggle the DRA state from IS to OOS and then back to IS.
5 If the alarm does not clear, repeat step 1 to step 4 and then go to step 6.
6 If the alarm does not clear, contact your next level of support or your Nortel
support group.
—end—.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-182 Alarm clearing

Procedure 3-72
Save Release In Progress (867)
Use this procedure to clear the Save Release In Progress (867) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC) or Group Mux/Demux (GMD).

This alarm clears when the save either completes or fails.

Probable cause
This alarm is raised while a save release operation is in progress.

Attention: No alarm is raised if the save release operation fails. Only an AO

broadcast message indicates the save release operation failed.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Wait for the save of the software release to complete.

See the Configuration, 323-1661-310, for more information on saving a
release.
2 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-183

Procedure 3-73
Secondary RADIUS Server Unavailable (584)
Use this procedure to clear the Secondary RADIUS Server Unavailable (584)
alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the remote authentication requests to the
secondary RADIUS server expires after a user-provisionable timeout and no
response is received from a RADIUS server. Possible reasons why the
RADIUS server is unavailable include:
• The shared secret provisioned for Centralized Security Authentication
(CSA) on the network element does not match the RADIUS server shared
secret.
• Wrong RADIUS server IP address or port provisioned on the network
element.
• The network element IP address is not provisioned on the RADIUS server
as a RADIUS client.
• A COLAN or OSC comms problem exists.
• The network delay exceeds the provisioned timeout value.
• UDP packet loss or other network problem prevents communication.

Attention: Disabling CSA clears this alarm. An alternate security

authentication method is used for log in and authentication if CSA is disabled
or if the RADIUS servers are unavailable. For information on security
administration, see Configuration, 323-1661-310.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-184 Alarm clearing

Procedure 3-73 (continued)

Secondary RADIUS Server Unavailable (584)

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or higher user privilege code (UPC).
• Have the shared secret.
• Have the IP address of the RADIUS server.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps

Step Action

1 Select Security->Centralized Security Administration.

2 Select the Secondary server from the list.
3 Click on the Edit Server button.
4 Verify the IP address of the Secondary RADIUS Server is correct and re-enter
it if required.
5 Verify the port number in the Port Number field is correct and re-enter it if
required.
The port number is the UDP port number of the RADIUS server.
6 Increase the time out value in the Timeout Value field.
The Timeout value is the amount of time (in seconds) that is allowed for
communication to occur between the controller and the RADIUS server. The
timeout value can range between 1 and 30 seconds.
7 Click the OK button if any changes were made.
8 Continue with the next step, if the alarm remains active.
9 Return to the Centralized Security Administration window.
10 Click the Set NE Shared Secret button.
11 Enter the shared secret in the Shared Secret field.
12 Re-enter the shared secret in the Shared Secret (confirmed) field.
13 Click the OK button.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-185

Procedure 3-73 (continued)

Secondary RADIUS Server Unavailable (584)

Step Action

14 Continue with the next step, if the alarm remains active.

15 If the alarm does not clear, contact your network administrator to verify that
the IP address of the network element has been added to the RADIUS server
and to correct any networking issues.

Attention: Use your RADIUS server documentation to troubleshoot possible

RADIUS server issues.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-186 Alarm clearing

Procedure 3-74
Shelf Data Error (571)
Use this procedure to clear the Shelf Data Error (571) alarm.

This alarm is raised at the shelf level.

Probable cause
This alarm is raised under the following conditions:
1 Two or more GMD/UOSC modules are connected through ILAN and one
of the following SLAT rules has not been met:
— Site ID must be the same on the GMD/UOSC modules.
— Shelf ID must be different on the GMD/UOSC modules.
— The fixed configuration must be the same on the GMD/UOSC
modules.
— OSC1 Tx Path IDs must be different on GMD/UOSC modules that
have the same OSID (in the same optical domain).
— OSC Mode must be the same on the GMD/UOSC modules.
— The provisioned associated shelf information must match the
discovered shelf information.
2 A GMD/UOSC or DOSC are connected together through OSC and one of
the following SLAT rules has not been met:
— OSID must be the same on both modules. OSID is case sensitive.
— Tx path ID for one module must be the same as the Rx path ID of the
other module.
— Site ID must be different on both modules.
3 A passthrough channel is provisioned on a TOADM but the last element in
the Serial Cascade Order (SCO) is a regular (non-serial) CMD4.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-187

Procedure 3-74 (continued)

Shelf Data Error (571)

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or 5 user privilege code (UPC).
• Have the engineering documentation package (EDP) for shelf details.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 If this is Then go to
a ROADM site step 2
not a ROADM site step 9

2 Verify if the WSS to WSS adjacency is provisioned and correct. Select

Facilities->Adjacency.
3 If the WSS to WSS adjacency Then go to
has not been manually provisioned or has an error step 4
is provisioned and correct step 9

4 Create or edit the WSS to WSS adjacency. See Configuration, 323-1661-310.

5 Continue with the next step, if the alarm remains active.
6 Verify that the GMD to GMD adjacency is provisioned and corrected for any
passthrough bands in an OADM configuration. Select Facilities -> Adjacency.
7 If the GMD to GMD adjacency Then go to
has not been manually provisioned or has an error step 8
is provisioned and correct step 9

8 Create or edit the GMD to GMD adjacency. See Configuration,

323-1661-310.
9 Select Configuration->Node Information->Shelf.
All shelves within a network element are listed.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-188 Alarm clearing

Procedure 3-74 (continued)

Shelf Data Error (571)

Step Action

10 Click the alarmed shelf.

Additional information for that shelf is displayed.
11 Verify the shelf details against the EDP/IDP.
12 Repeat step 9 to step 11, verify the information on the other alarmed shelf.
13 Correct any wrongly provisioned information. For details on network element
commissioning and provisioning, see SLAT and Channel Procedures,
323-1661-221, and Configuration, 323-1661-310.

Attention: Not all information entered during the SLAT stage can be edited.
In some cases the NE must be recommissioned to clear this alarm.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-189

Procedure 3-75
Shelf Data Missing (570)
Use this procedure to clear the Shelf Data Missing (570) alarm.

This alarm is raised at the shelf level.

Probable cause
This alarm is raised when a shelf is physically detected but the shelf
configuration attributes have not yet been commissioned.

Attention: This alarm is expected during initial commissioning operations.

Attention: When the shelf configuration attributes have not yet been
commissioned, most other actions (Equipment and Facility provisioning) are
blocked (Status, Requested Command Inhibited).

Impact
Major, NSA (non-service-affecting)

Procedure steps
Step Action

1 This alarm clears when the commissioning of the shelf has been completed
successfully. Complete the commissioning procedures according to SLAT
and Channel Procedures, 323-1661-221.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-190 Alarm clearing

Procedure 3-76
Shutoff Threshold Crossed (540)
Use this procedure to clear the Shutoff Threshold Crossed (540) alarm. This
alarm masks the Input Loss Of Signal (557) alarm and is masked by the
Automatic Shutoff (590, 942) alarm.

This alarm is raised on an amplifier within the SLA, MLA, MLA2, SCMD8, or
CMDA.

Attention: If a Shutoff Threshold Crossed alarm is raised on an amplifier in

a DRA module, use the Shutoff Threshold Crossed (940) alarm clearing
procedure to clear the alarm.

Probable cause
This alarm is raised when the power level at the amplifier drops below the
shutoff threshold.

Attention: When the shutoff threshold is crossed on an SLA, MLA or MLA2

module, the Automatic Laser Shut Off (ALSO) feature is activated. The
ALSO feature is a safety laser shutdown mechanism. Amplifier power levels
are turned down or turned off when a fiber break or intermediate connector
disconnect occurs between two neighboring sites where optical radiation is
being fed into both ends of the optical fiber and generating a hazard on both
ends of a fiber break.

Impact
Major, SA (service-affecting)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-191

Procedure 3-76 (continued)

Shutoff Threshold Crossed (540)

Procedure steps
Step Action

1 If this alarm is Then

raised on a
SLA, MLA, MLA2 perform Procedure 3-59, Optical Line Fail (610, 541)
SCMD8, CMDA perform Procedure 3-44, Group Input Loss Of Signal
(712)

This alarm is cleared and amplifier(s) are turned up when the condition that
activated the ALSO feature is cleared.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-192 Alarm clearing

Procedure 3-77
Shutoff Threshold Crossed (940)
Use this procedure to clear the Shutoff Threshold Crossed (940) alarm. This
alarm masks the Input Loss Of Signal (557) alarm and is masked by the
Automatic Shutoff (590, 942) alarm.

This alarm is raised on DRA modules in Local mode that are in Automatic
Shutoff Disabled mode at the same time. The DRA was put into Raman Auto
Shutoff Disabled mode for maintenance. The upstream OSC fiber was
disconnected and then reconnected while the DRA was in Auto Shutoff
Disabled mode, activating the Shutoff Threshold Crossed alarm and the
Automatic Shutoff Disabled (943, 1035) alarm.

Attention: If a Shutoff Threshold Crossed alarm is raised on an amplifier in

an SLA, MLA, MLA2, SCMD8, use the Shutoff Threshold Crossed (540)
alarm clearing procedure to clear the alarm.

Probable cause
This alarm is raised on DRA modules in Local mode that are in Automatic
Shutoff Disabled mode at the same time. In other conditions, this alarm is
masked by the Automatic Shutoff (590, 942) alarm.

Impact
Major, SA (service-affecting)

Procedure steps
Step Action

1 If Then
you want to leave the DRA in no action is required. You have completed
Automatic Shutoff Disabled this procedure.
mode
otherwise go to step 2

2 Clean all fibers in the OSC path. For instructions on cleaning fibers, see SLAT
and Channel Procedures, 323-1661-221.
When the extra loss is removed, the Shutoff Threshold Crossed (STC) alarm
will disappear.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-193

Procedure 3-77 (continued)

Shutoff Threshold Crossed (940)

Step Action

3 If the alarm does not clear, then the extra loss was not caused by a
maintenance activity. Contact your next level of support, or Nortel technical
support.

Attention: The STC alarm can be cleared by a warm restart, but the next
RAMAN ramp-up (IS-OOS-IS transition, fixing the fiber cut) will cause the
Raman Failed To Turn On (944) alarm to be raised because the OSC power
level is below the Shutoff Clear Threshold.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-194 Alarm clearing

Procedure 3-78
Software Auto-Upgrade Failed (440)
Use this procedure to clear the Software Auto-Upgrade Failed (440) alarm.

This alarm applies to all cards with the exception of the GMD, UOSC, and
DOSC.
Probable cause
This alarm is raised when a failure occurs during an automatic upgrade of a
module. Automatic upgrades may occur during module replacements.

Impact
minor, NSA (non-service-affecting)

Procedure steps
Step Action

1 Contact your next level of support or your Nortel support group.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-195

Procedure 3-79
Software Auto-Upgrade in Progress (439)
Use this procedure to clear the Software Auto-Upgrade in Progress (439)
alarm.

This alarm is raised on the following modules:

• 4 Channel Mux/Demux (CMD4)
• Serial 4 Channel Mux/Demux (SCMD4)
• Serial 8 Channel Mux/Demux (SCMD8)
• Channel Mux/Demux Amplifier (CMDA)
• Dual Optical Service Channel (DOSC)
• Uni Optical Service Channel (UOSC)
• Group Mux/Demux (GMD)
• Line Interface Module (LIM)
• Optical Power Monitor (OPM)
• Wavelength Selective Switch (WSS)
• Distributed Raman Amplifier (DRA)

Attention: It can take up to 20 minutes for this alarm to clear.

Probable cause
This alarm is raised if a newly inserted module is being
auto-upgraded/downgraded to the active software release of the network
element.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-196 Alarm clearing

Procedure 3-79 (continued)

Software Auto-Upgrade in Progress (439)

Procedure steps
Step Action

1 Wait for the auto-upgrade/downgrade of the module to complete.

2 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-197

Procedure 3-80
Software Configuration Unknown (138)
Use this procedure to clear the Software Configuration Unknown (138) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC) or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the UOSC, GMD or DOSC software fails to install
the software release information.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft interface. To log into the network element, see
Configuration, 323-1661-310.
Procedure steps
Step Action

1 Retrieve all active alarms (enabled and disabled) on the system, see
Procedure 2-1, Displaying active alarms and Procedure 2-2, Displaying
active disabled alarms.
2 If Then
a Software Mismatch (75) and an perform the alarm clearing procedure
Incomplete Software Lineup (92) for the Incomplete Software Lineup
alarm are also both active (92).
If the Software Configuration Unknown
alarm does not clear, go to step 3.
a Software Mismatch (75) and an go to step 3
Incomplete Software Lineup (92)
alarm are not both active

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-198 Alarm clearing

Procedure 3-80 (continued)

Software Configuration Unknown (138)

Step Action

3 If a software upgrade or module replacement procedure is performed

incorrectly, both the Software Configuration Unknown and Incomplete
Software Lineup alarms can be active, but the Software Mismatch alarm
might not be raised. In this case, complete the upgrade or replacement
according to the appropriate NTP procedure.
4 If the alarm remains active, contact your next level of support or your Nortel
support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-199

Procedure 3-81
Software Delivery Incomplete (453)
Use this procedure to clear the Software Delivery Incomplete (453) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC) or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when a transfer of a new software release to the UOSC,
GMD or DOSC has failed.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Select Configuration->Release Management.

2 Click the Cancel button in the Release Management window.
Canceling stops the action and cleans up any files left in invalid states.
3 This alarm can also clear if you try to deliver the software release again. Try
to establish and resolve the cause of the initial failure then retry the delivery.
See the release management procedures in Configuration, 323-1661-310.

Attention: Wait for the load transfer to complete. Contact your next level of
support or your Nortel support group for assistance if necessary.

4 Perform a UOSC, DOSC or GMD warm restart. See Procedure 5-1,

Performing a module warm restart.
5 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-200 Alarm clearing

Procedure 3-82
Software Delivery In Progress (454)
Use this procedure to clear the Software Delivery In Progress (454) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC) or Group Mux/Demux (GMD).

Probable cause
This alarm is raised if a new release is being transferred to the UOSC, GMD
or DOSC.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps

Step Action

1 Wait for the transfer of the software release to complete.

2 If you want to abort the transfer, click the Cancel button in the Release
Management window.
Canceling stops the action and cleans up any files left in invalid states.
3 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-201

Procedure 3-83
Software Mismatch (75)
Use this procedure to clear the Software Mismatch (75) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

CAUTION
Risk of traffic loss
Do not perform module replacements while this alarm is active.
Provisioning information will be lost and traffic can be affected.

Probable cause
This alarm is raised under the following conditions:
• If a UOSC, GMD, or DOSC is inserted in the shelf and the UOSC, GMD,
or DOSC is running a different software release than the active release on
the network element.
• After a GMD/DOSC/UOSC restart occurs and one or more of the
subtending modules does not have the proper release. This alarm and the
Software Auto-Upgrade in Progress (439) alarm are raised until the
subtending modules have been brought up to the proper release.

Attention: When this alarm is active, do not make any provisioning

changes.

Impact
Major, SA (service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-202 Alarm clearing

Procedure 3-83 (continued)

Software Mismatch (75)

Procedure steps
Step Action

1 Select Configuration->Release Management.

2 Verify the current load release on the UOSC, DOSC, or GMD.
3 If Then
the current active upgrade the UOSC, GMD, or DOSC to the current
network element release active network element release.
is not the required Note 1: Contact Nortel for upgrade support
release before upgrading the UOSC, GMD, or DOSC.
Note 2: If the UOSC, GMD, or DOSC does not
contain the required release, you must transfer a
software load from a local or remote server into
the UOSCs, GMDs, or DOSCs local file system,
before upgrading. See release and upgrade
management procedures in Configuration,
323-1661-310.
the release running on upgrade all of the NE subtending modules to the
the UOSC, GMD, or UOSC, GMD, or DOSC release.
DOSC is the required Note: Contact Nortel for upgrade support before
release
upgrading the NE subtending modules.
the UOSC, GMD, or replace the UOSC, GMD, or DOSC with one
DOSC has been running the correct software release. See
inserted in the wrong Chapter 4, Module and component replacement.
shelf

4 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-203

Procedure 3-84
Software Upgrade Failed (71)
Use this procedure to clear the Software Upgrade Failed (71) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when a failure occurs during a manual upgrade of
modules.

Impact
minor, NSA (non-service-affecting)

Procedure steps
Step Action

1 Contact your next level of support or your Nortel support group.

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-204 Alarm clearing

Procedure 3-85
Software Upgrade in Progress (74)
Use this procedure to clear the Software Upgrade in Progress (74) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised while a software upgrade is in progress. The alarm clears
after the upgrade is complete.

Attention: This alarm is for information only. Do not perform any actions
other than the upgrade activity while it is active. The alarm clears after the
upgrade is complete.

Impact
minor, NSA (non-service-affecting)

Procedure steps
Step Action

1 If the alarm does not clear after the upgrade is complete, contact your next
level of support or your Nortel support group.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-205

Procedure 3-86
TOD Server Not Provisioned (575)
Use this procedure to clear the TOD Server Not Provisioned (575) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when the shelf is provisioned to retrieve its date and time
from a Network Time Protocol (NTP) server but the NTP server attributes have
not yet been provisioned.

Attention: If the Common Photonic Layer network element is managed by

the Optical Manager Element Adapter (OMEA), use the IP address of the
primary OMEA platform as the IP address of the first NTP server. If a backup
OMEA platform is deployed, use the IP address of this platform for the
second NTP server. Leave the third, fourth, and fifth NTP server
unprovisioned.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Confirm that date and time will be retrieved from an NTP server.
• Know the IP addresses of the NTP servers and have access to these
servers.
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-206 Alarm clearing

Procedure 3-86 (continued)

TOD Server Not Provisioned (575)

Procedure steps
Step Action

1 Select Configuration->Node Information->Time Of Day.

The Time of Day window opens.
2 If date and time should be Then
set manually change the Time Of Day Mode to INACTIVE
and click on the Apply button.
You have completed this procedure.
retrieved from an NTP server Complete the procedure on setting the date
and time using an NTP server, see
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-207

Procedure 3-87
Transport Data Recovery Failed (76)
Use this procedure to clear the Transport Data Recovery Failed (76) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC) or Group Mux/Demux (GMD).

Probable cause
This alarm is raised when data is not recovered after a UOSC, GMD, or DOSC
replacement. Data cannot be recovered correctly if one or more of the
transport modules are running a higher software release than the UOSC,
GMD, or DOSC.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 3 or higher user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.

Procedure steps
Step Action

1 Select the action you must take:

If Then
the alarm occurs refer to the respective replacement procedure to clear
during a DOSC, the alarm (Procedure 4-9, Replacing the DOSC
GMD, or UOSC module, Procedure 4-10, Replacing the GMD module,
replacement or Procedure 4-13, Replacing the UOSC module)
otherwise contact Nortel technical support, or your next level of
support

—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-208 Alarm clearing

Procedure 3-88
Unable to Synchronize TOD (336)
Use this procedure to clear the Unable to Synchronize TOD (336) alarm.

This alarm is raised on a Uni Optical Service Channel (UOSC), Dual Optical
Service Channel (DOSC), or Group Mux/Demux (GMD).

Probable cause
This alarm is raised under the following conditions:
• When the network element attempts to reference its internal clock to a
provisioned Network Time Protocol (NTP) server, and this attempt is
unsuccessful.

Attention: If the Common Photonic Layer network element is managed by

the Optical Manager Element Adapter (OMEA), use the IP address of the
primary OMEA platform as the IP address of the first NTP server. If a backup
OMEA platform is deployed, use the IP address of this platform for the
second NTP server. Leave the third, fourth, and fifth NTP servers
unprovisioned.

• A TID Consolidation Primary is unable to synchronize with its member

shelf after an IP address change.
Impact
Major, NSA (non-service-affecting)

Prerequisites
• Use an account with a level 4 or 5 user privilege code (UPC).
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Know the time zones of the NTP servers and the Common Photonic Layer
network element.
• Know the IP addresses of the NTP servers and have access to these
servers.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-209

Procedure 3-88 (continued)

Unable to Synchronize TOD (336)

Procedure steps
Step Action

1 Select Configuration->Node Information->Time Of Day.

2 Verify and correct Time Of Day (TOD) parameter information in the Time OF
Day window.

Attention: Increase the polling interval if your NTP server(s) are overworked
or if precision is not an issue.

3 Click the Apply button if any changes were made in step 2.

4 Click the Synchronize button to perform a manual Time Of Day
synchronization.
5 If the alarm does not clear, contact your network administrator to verify the IP
address of the NTP server, to correct any networking issues, and to ensure
that the Simple Network Timing Protocol (SNTP) daemon is running correctly
on the remote server.
6 Perform warm restarts on the Primary shelf. See Chapter 5, Restart
procedures.
7 If the alarm does not clear, contact Nortel technical support, or your next level
of support.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-210 Alarm clearing

Procedure 3-89
Wavelength Measurement Error (879)
Use this procedure to clear the Wavelength Measurement Error (879) alarm.
This alarm can be masked by the OPM Circuit Pack Failed alarm.

This alarm is raised on the OPTMON facilities.

Attention: If this alarm is raised against more than one wavelength, the
Circuit Pack Failed (581) will be triggered against the OPM circuit pack that
contains the OPTMON facilities at fault. The Circuit Pack Failed alarm will
mask the Wavelength Measurement Error alarms.

Probable cause
This alarm is raised by the OPM Drift Controller if it detects a channel drifting
away from the ITU grid by more than 25 GHz from the start point of monitoring.

Impact
Major, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Use an account with a level 4 or higher user privilege code (UPC).
• Have the engineering documentation package (EDP) that contains shelf
details.
• Have access to the appropriate module replacement documentation for
the transmitters in the network.

Procedure steps

Step Action

1 Identify the OPM module raising the alarm. See “Identifying the alarmed
entity” on page 1-9.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-211

Procedure 3-89 (continued)

Wavelength Measurement Error (879)

Step Action

2 Check if the Circuit Pack Failed (581) alarm is active against that module
(Faults->Active Alarms).
If the Circuit Pack Failed (581) alarm is Then go to
active step 5
not active step 3

3 Use the Domain Optical Controller screen and the DOC Optical Control
Command Logs to help you determine which wavelength(s) the problem is
reported against. For information on retrieving DOC logs, see Procedure 2-8,
Displaying and clearing DOC and SOC logs.
In the DOC screen the Channel Condition field will show “Optimized Fault
Detected” against any channel with a problem.
In the DOC Logs, under the Optical Control Command Log section, the
following error message will appear against the channel: “Wavelengths
measurement error”.

Attention: If there is an OPM Circuit Pack Failure alarm masking the

Wavelength Measurement Error alarm, the following message will appear
against the channel(s): “OPM failure detected. Wavelengths measurement
error”.

4 Replace the transmitter circuit pack(s) that this alarm is raised against. Follow
the appropriate module replacement documentation for the transmitter
source. Wait for the transmitter(s) to initialize.
If the alarm Then
clears you have completed this procedure
does not go to step 5

5 Replace the OPM circuit pack. See the module replacement procedure in
chapter “Module and component replacement” on page 4-1.
If the alarm Then
clears you have completed this procedure
does not clear Contact your next level of support.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-212 Alarm clearing

Procedure 3-90
Wavelength Measurement Warning (878)
Use this procedure to clear the Wavelength Measurement Warning (878)
alarm. This alarm is masked by the OPM Circuit Pack Failed alarm.

This alarm is raised on an OPTMON facility.

Attention: If this alarm is raised against more than one wavelength, the
Circuit Pack Failed (581) will be triggered against the OPM circuit pack that
contains the OPTMON facilities at fault. The Circuit Pack Failed alarm will
mask the Wavelength Measurement Warning alarms.

Probable cause
This alarm is raised by the OPM Drift Controller if it detects a provisioned
channel drifting away from the ITU grid by more than 20 GHz but less 25 GHz
from the start point of monitoring.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Use an account with a level 4 or higher user privilege code (UPC).
• Have the engineering documentation package (EDP) that contains shelf
details.
• Have access to the appropriate module replacement documentation for
the transmitters in the network.

Procedure steps

Step Action

1 Identify the OPM module raising the alarm. See “Identifying the alarmed
entity” on page 1-9.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-213

Procedure 3-90 (continued)

Wavelength Measurement Warning (878)

Step Action

2 Check if the Circuit Pack Failed (581) alarm is active against that OPM
module (Faults->Active Alarms).
If the Circuit Pack Failed (581) alarm is Then go to
active step 5
not active step 3

3 Use the Domain Optical Controller screen and the DOC Optical Control
Command Logs to help you determine which wavelength(s) the problem is
reported against. For information on retrieving DOC logs, see Procedure 2-8,
Displaying and clearing DOC and SOC logs.
In the DOC screen the Channel Condition field will show “Optimized Fault
Detected” against any channel with a problem.
In the DOC Logs, under the Optical Control Command Log section, the
following error message will appear against the channel: “OPM measurement
warning for wavelength 15xx.xx 15xx.xx.

Attention: If there is an OPM Circuit Pack Failure alarm masking the

Wavelength Measurement Warning alarm, the following message will appear
against the channel(s): “OPM failure detected. Wavelengths measurement
warning”.

4 Replace the transmitter circuit pack(s) that this alarm is raised against. Follow
the appropriate module replacement documentation for the transmitter
source. Wait for the transmitter(s) to initialize.
If the alarm Then
clears you have completed this procedure
does not go to step 5

5 Replace the OPM circuit pack. See the module replacement procedure in
chapter “Module and component replacement” on page 4-1.
If the alarm Then
clears you have completed this procedure
does not clear Contact your next level of support.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-214 Alarm clearing

Procedure 3-91
WAYSIDE 1 Port Failure (573)
Use this procedure to clear the WAYSIDE 1 Port Failure (573) alarm. This
alarm is masked by the Circuit Pack Failed alarm.

This alarm is raised against WSC-1 port on the UOSC, GMD or DOSC.

Probable cause
This alarm is raised when this wayside port cannot connect to another
wayside port.

Wayside traffic enters the system through one wayside port and exits the
system through another wayside port.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have DCN information for your network.
• Use an account with a level 3 or higher user privilege code (UPC).

Procedure steps
Step Action

1 Check the DCN information to determine if the WSC-1 port should be

enabled.
If the WSC-1 should be Then go to
enabled step 3
disabled step 2
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-215

Procedure 3-91 (continued)

WAYSIDE 1 Port Failure (573)

Step Action

2 Delete the alarmed WSC-1 port. See Configuration, 323-1661-310, for

information on deleting a WSC-1 port. You have completed this procedure.

Attention: By deleting the WSC-1 port, you lose any established

connections that use this port.

3 Check that the WSC-1 configuration at both ends of the Ethernet link are the
same. See Configuration, 323-1661-310, for information on how to view
WSC-1 port information.
4 If the configuration is different, edit the configuration as required. See
Configuration, 323-1661-310, for information on how to edit WSC-1 port
information.
5 Continue with the next step, if the alarm remains active.
6 Ensure that the appropriate cable is correctly connected to the alarmed
WSC-1 port. See Installation, 323-1661-201, for cabling procedures.
7 Continue with the next step, if the alarm remains active.
8 The cable connected to the WSC port may be defective. Replace the cable.
9 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-216 Alarm clearing

Procedure 3-92
WAYSIDE 2 Port Failure (574)
Use this procedure to clear the WAYSIDE 2 Port Failure (574) alarm. This
alarm is masked by the Circuit Pack Failed alarm.

This alarm is raised against WSC-2 port on the DOSC.

Probable cause
This alarm is raised when this wayside port cannot connect to another
wayside port.

Wayside traffic enters the system through one wayside port and exits the
system through another wayside port.

Impact
minor, NSA (non-service-affecting)

Prerequisites
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Log into the Craft. To log into the network element, see Configuration,
323-1661-310.
• Have DCN information for your network.
• Use an account with a level 3 or higher user privilege code (UPC).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Alarm clearing 3-217

Procedure 3-92 (continued)

WAYSIDE 2 Port Failure (574)

Procedure steps
Step Action

1 Check the DCN information to determine if the WSC-2 port should be

enabled.
If the WSC-2 should be Then go to
enabled step 3
disabled step 2

2 Delete the alarmed WSC-2 port. See Configuration, 323-1661-310, for

information on deleting a WSC-2 port. You have completed this procedure.

Attention: By deleting the WSC-2 port, you lose any established

connections that use this port.

3 Check that the WSC-2 configuration at both ends of the Ethernet link are the
same. See Configuration, 323-1661-310, for information on how to view
WSC-2 port information.
4 If the configuration is different, edit the configuration as required. See
Configuration, 323-1661-310, for information on how to edit WSC-2 port
information.
5 Continue with the next step, if the alarm remains active.
6 Ensure that the appropriate cable is correctly connected to the alarmed
WSC-2 port. See Installation, 323-1661-201, for cabling procedures.
7 Continue with the next step, if the alarm remains active.
8 The cable connected to the WSC port may be defective. Replace the cable.
9 Contact your next level of support or your Nortel support group, if the alarm
does not clear.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
3-218 Alarm clearing

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 323-1661-543
4-1

Module and component replacement 4-

This chapter contains module and component replacement procedures for the
Common Photonic Layer (CPL).

In this chapter, CMD44 refers to both CMD44 100 GHz and CMD44 50 GHz,
unless otherwise specified.

See Table 4-1 for a list of procedures in this chapter.

Table 4-1
Module and component replacement procedures

Procedure Page Comments

Module replacement procedures

4-1 Replacing the amplifier module 4-4 This procedure describes how to replace the
following module types: Single Line Amplifier
(SLA), Line Interface Module (LIM), Mid-stage
Line Amplifier (MLA and MLA2).

4-2 Replacing the CMDA module 4-9 This procedure describes how to replace the
CMDA module.

4-3 Replacing the CMD44 module with the 4-14 This procedure describes how to replace a 44
equivalent CMD44 Channel Mux/Demux (CMD44) module with
another CMD44 with the same PEC.

4-4 Replacing the CMD4 module with the 4-19 This procedure describes how to replace a 4
equivalent CMD4 Channel Mux/Demux (CMD4) module with
another CMD4 with the same PEC.

4-5 Replacing the CMD4 module with the 4-24 This procedure describes how to replace a 4
SCMD4 module Channel Mux/Demux (CMD4) module with a
Serial 4 Channel Mux/Demux (SCMD4) module.

4-6 Replacing the CMD4 module with the 4-29 This procedure describes how to replace the 4
SCMD8 module Channel Mux/Demux (CMD4) module with a
Serial 8 Channel Mux/Demux (SCMD8) module.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-2 Module and component replacement

Table 4-1 (continued)

Module and component replacement procedures

Procedure Page Comments

4-7 Replacing an Open SCMD8 module with a 4-35 This procedure describes how to replace the
Filtered SCMD8 module Open Serial 8 Channel Mux/Demux (Open
SCMD8) module with a Filtered Serial 8
Channel Mux/Demux (Filtered SCMD8) module.

4-8 Replacing an MLA module with an MLA2 4-40 This procedure describes how to replace a
module or an MLA2 module with an MLA Mid-stage Line Amplifier (MLA) with an MLA2
module module. Or, how to replace an MLA2 with an
MLA module.

4-9 Replacing the DOSC module 4-47 This procedure describes how to replace a Dual
Optical Service Channel (DOSC) module.

4-10 Replacing the GMD module 4-58 This procedure describes how to replace the
Group Mux/Demux (GMD) module.

4-11 Replacing the OPM module 4-69 This procedure describes how to replace the
Optical Power Monitor (OPM) module.

4-12 Replacing the SCMDx module 4-73 This procedure describes how to replace a
Serial Channel Mux/Demux (SCMDx) module.

4-13 Replacing the UOSC module 4-78 This procedure describes how to replace a Uni
Optical Service Channel (UOSC) module.

4-14 Replacing the WSS module 4-89 This procedure describes how to replace a
Wavelength Selective Switch (WSS) module.

4-15 Replacing a DSCM contained within a 4-94 This procedure describes how to replace the
Fiber Manager dispersion slope compensating module
(DSCM).

4-16 Replacing the DRA module with the 4-99 This procedure describes how to replace a DRA
equivalent DRA (Distributed Raman Amplifier) module with
another DRA with the same PEC.

4-17 DOC settings when replacing equipment 4-104 This procedure describes the DOC settings
subtending to the Common Photonic Layer when replacing equipment subtending to the
network element Common Photonic Layer network element.

Component replacement procedures

4-18 Replacing the fan assembly in an 4-105 This procedure describes how to replace the
amplifier 4-unit fan assembly in an amplifier.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-3

Table 4-1 (continued)

Module and component replacement procedures

Procedure Page Comments

4-19 Replacing the fan assembly in a UOSC, 4-108 This procedure describes how to replace the fan
GMD, or DOSC assembly in the Uni Optical Service Channel
(UOSC), Group Mux/Demux (GMD) module and
the Dual Optical Service Channel (DOSC)
module.

4-20 Replacing air filters 4-110 This procedure describes how to replace the air
filter in the Uni Optical Service Channel (UOSC),
Group Mux/Demux (GMD) module and the Dual
Optical Service Channel (DOSC) module.

4-21 Replacing a patch panel for attenuator fix 4-112 This procedure describes how to replace the
pads patch panel for attenuator fix pads used with the
CMD44 module.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-4 Module and component replacement

Procedure 4-1
Replacing the amplifier module
Use this procedures to replace the following module types:
• Single Line Amplifier (SLA)
• Line Interface Module (LIM)
• Mid-stage Line Amplifier (MLA and MLA2)

CAUTION
Service affecting procedure
Amplifier module replacement is service affecting. Ensure you
have exhausted all other troubleshooting options before
performing this procedure and if possible, re-route the traffic to
minimize the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC a loss of provisioning data may occur. Do
not remove any subtending modules during a
GMD/DOSC/UOSC replacement.

Attention: You can perform this procedure while DOC is set to Auto
Re-optimize As Necessary. However, DOC will raise the DOC Action Failed:
Monitor (549) or DOC Action Failed: Optimize (550) alarm at the DOC
network element. These alarms occur because DOC detects changes in the
system topology. To ensure correct operation, DOC only attempts
equalization when the system topology is stable and determined to be
accurate. To avoid the alarm generation, set DOC OOS before the procedure
is started. See Configuration, 323-1661-310, for information on changing
DOC settings. Ensure you return DOC to the original settings after this
procedure is completed.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-5

Procedure 4-1 (continued)

Replacing the amplifier module

Attention: No action is required to recover the software or data

configuration unless a problem recovery scenario occurs. Alarms are raised
identifying specific problems.

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have the correct replacement module (the replacement product
engineering code (PEC) is the same as the current PEC).
• Have a 10-mm socket.
• Have a torque wrench.

Procedure steps
Step Action

Remove the module

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2 Set all Domain Optical Controllers (DOC) within this domain OOS. See
Configuration, 323-1661-310.

Attention: Other DOC domains will not be able to optimize or add/delete

channels when DOC is put OOS in this domain.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-6 Module and component replacement

Procedure 4-1 (continued)

Replacing the amplifier module

Step Action

3 Verify the current alarm conditions on the network element. Depending on the
configuration of the node where this procedure is to be performed the
following alarms can appear throughout the network during this procedure:
• Adjacency Far End Not Discovered (538)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Circuit Pack Missing (579)
• DOC Invalid Photonic Domain (552)
• Loss Of Signal (553, 560)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Power Failure - A (594)
• Power Failure - B (595)
• Shutoff Threshold Crossed (540)

4 Verify that the replacement product engineering code (PEC) is the same as
the current PEC.
5 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
6
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical
amplifier is out of service (OOS).

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-7

Procedure 4-1 (continued)

Replacing the amplifier module

Step Action

Remove from service the amplifier facilities (SLA, MLA, MLA2) connected to
the module you are replacing. See Configuration, 323-1661-310, for
information on removing optical facilities from service.
7 Turn off the power feeds to the amplifier at the breaker panel.
8 Apply labels to both ends of all cables and optical fiber patch cords. Apply
labels to the breaker interface panel or fuse panel. See Installation,
323-1661-201, for information on labeling cable and optical fibers.
9
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections; otherwise, you risk an electric shock.
Ensure the power feeds to the amplifier at the breaker
panel are off (0).

Ensure the power feeds to the amplifier at the breaker panel are off (0) and
disconnect the A and B power connectors on the amplifier.
10 Unscrew the two 3/8-in. nuts and lock washers over the ground pins (located
on the left side of the module).
11 Disconnect the Ethernet and RS-232 cables from the amplifier.
12 Disconnect all optical connectors (Line A, Line B, OSC A, OSC B, Mon 1 and
Mon 2) on the amplifier.
13 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
14 Pull out and hold the amplifier spring plunger and remove the existing
amplifier from the frame.
Install the module
15 Install the replacement amplifier into the frame.
16 Secure the two 3/8-in. nuts and lock washers over the ground pins.
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque two 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-8 Module and component replacement

Procedure 4-1 (continued)

Replacing the amplifier module

Step Action

17 Reconnect all Ethernet and RS-232 cables disconnected in step 11 to the

amplifier.
18 Clean all fiber connectors disconnected from the Mon, OSC, and Line ports
in step 12 and reconnect them to the appropriate ports on the amplifier. For
instructions on inspecting and cleaning optical fiber, see SLAT and Channel
Procedures, 323-1661-221.
19
DANGER
Risk of electric shock
Exercise caution when connecting power connections;
otherwise, you risk an electric shock. Ensure the power
feeds to the amplifier at the breaker panel are off.

Ensure the power feeds to the amplifier at the breaker panel are off and
connect the A and B power connectors disconnected in step 9 to the amplifier.
20 At the breaker panel turn on the power feeds to the amplifier.
21 Wait for the amplifier to start. The active LED should be green.
22 Restore the amplifier facilities (SLA, MLA,MLA2) connected to the new
amplifier back in-service (IS). See Configuration, 323-1661-310, for
information on restoring facilities to service.
23 Check the active alarms (Faults->Active Alarms).
24 If the Software Auto-Upgrade in Progress (439) alarm is active, wait until the
alarm clears before continuing.

Attention: It can take up to 20 minutes for this alarm to clear.

25 If the Circuit Pack Upgrade Failed (124) is active, clear this alarm using the
procedures in this NTP.
26 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact Nortel.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)

27 Undo any traffic switches performed in step 5.

28 Put both of the Domain Optical Controllers back in-service; a re-optimization
is recommended. See Configuration, 323-1661-310.
29 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-9

Procedure 4-2
Replacing the CMDA module
Use this procedure to replace the Channel Mux/Demux Amplifier (CMDA)
module.

CAUTION
Service affecting procedure
Amplifier module replacement is service affecting. Ensure you
have exhausted all other troubleshooting options before
performing this procedure and if possible, reroute the traffic to
minimize the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC a loss of provisioning data may occur. Do
not remove any subtending modules during a
GMD/DOSC/UOSC replacement.

Attention: You can perform this procedure while DOC is set to Auto
Re-optimize As Necessary. However, DOC will raise the DOC Action Failed:
Monitor (549) or DOC Action Failed: Optimize (550) alarm at the DOC
network element. These alarms occur because DOC detects changes in the
system topology. To ensure correct operation, DOC only attempts
equalization when the system topology is stable and determined to be
accurate. To avoid the alarm generation, set DOC to OOS before the
procedure is started. See Configuration, 323-1661-310, for information on
changing DOC settings. Ensure you return DOC to the original settings after
this procedure is completed.

Attention: No action is required to recover the software or data

configuration unless a problem recovery scenario occurs. Alarms are raised
identifying specific problems.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-10 Module and component replacement

Procedure 4-2 (continued)

Replacing the CMDA module

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have the correct replacement module (the replacement product
engineering code [PEC] is the same as the current PEC).
• Have a 10-mm socket.
• Have a torque wrench.

Procedure steps
Step Action

Remove the module

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2 Set all Domain Optical Controllers (DOC) within this domain OOS. See
Configuration, 323-1661-310.

Attention: Other DOC domains will not be able to optimize or add/delete

channels when DOC is put OOS in this domain.

3 Verify the current alarm conditions on the network element. Depending on the
configuration of the node where this procedure is to be performed, the
following alarms can appear throughout the network during this procedure:
• Adjacency Far End Not Discovered (538)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Circuit Pack Missing (579)
• DOC Invalid Photonic Domain (552)
• Loss Of Signal (553, 560)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Power Failure - A (594)
• Power Failure - B (595)
• Shutoff Threshold Crossed (540)

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-11

Procedure 4-2 (continued)

Replacing the CMDA module

Step Action

4 Verify that the replacement product engineering code (PEC) is the same as
the current PEC.
5 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
6
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical
amplifier is out of service (OOS).

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Remove from service the OPTMON and AMP facilities connected to the
module you are replacing. See Configuration, 323-1661-310, for information
on removing optical facilities from service.
7 Turn off the power feeds to the CMDA at the breaker panel.
8 Apply labels to both ends of all cables and optical fiber patch cords. Apply
labels to the breaker interface panel or fuse panel. See Installation,
323-1661-201, for information on labeling cable and optical fibers.
9
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections; otherwise, you risk an electric shock.
Ensure the power feeds to the amplifier at the breaker
panel are off (0).

Ensure the power feeds to the CMDA at the breaker panel are off (0) and
disconnect the A and B power connectors on the amplifier.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-12 Module and component replacement

Procedure 4-2 (continued)

Replacing the CMDA module

Step Action

10 Unscrew the two 3/8-in. nuts and lock washers over the ground pins (located
on the left side of the module).
11 Disconnect the Ethernet and RS-232 cables from the amplifier.
12 Disconnect all optical connectors on the CMDA.
13 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
14 Pull out and hold the CMDA spring plunger and remove the existing CMDA
from the frame.
Install the module
15 Install the replacement CMDA into the frame.
16 Secure the two 3/8-in. nuts and lock washers over the ground pins.
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque two 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

17 Reconnect all Ethernet and RS-232 cables disconnected in step 11 to the
amplifier.
18 Clean all fiber connectors disconnected from the ports in step 12 and
reconnect them to the appropriate ports on the CMDA. For instructions on
inspecting and cleaning optical fiber, see SLAT and Channel Procedures,
323-1661-221.
19
DANGER
Risk of electric shock
Exercise caution when connecting power connections;
otherwise, you risk an electric shock. Ensure the power
feeds to the amplifier at the breaker panel are off.

Ensure the power feeds to the amplifier at the breaker panel are off and
connect the A and B power connectors disconnected in step 9 to the CMDA.
20 At the breaker panel turn on the power feeds to the CMDA.
21 Wait for the amplifier to start. Verify that the active LED is green.
22 Restore the OPTMON and AMP facilities connected to the new CMDA back
in-service (IS). See Configuration, 323-1661-310, for information on restoring
facilities to service.
23 Check the active alarms (Faults->Active Alarms).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-13

Procedure 4-2 (continued)

Replacing the CMDA module

Step Action

24 If the Software Auto-Upgrade in Progress (439) alarm is active, wait until the
alarm clears before continuing.

Attention: It can take up to 20 minutes for this alarm to clear.

25 If the Circuit Pack Upgrade Failed (124) is active, clear this alarm using the
procedures in this NTP.
26 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact Nortel.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)

27 Undo any traffic switches performed in step 5.

28 Put both of the Domain Optical Controllers back in-service; a re-optimization
is recommended. See Configuration, 323-1661-310.
29 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-14 Module and component replacement

Procedure 4-3
Replacing the CMD44 module with the equivalent
CMD44
Use this procedure to replace the 44 Channel Mux/Demux (CMD44) module
with the equivalent CMD44 (50 GHz with 50 GHz, 100 GHz with 100 GHz,
Blue with Blue, Red with Red).

CAUTION
Service affecting procedure
CMD44 module replacement is service affecting. Ensure you
have exhausted all other troubleshooting options before
performing this procedure and, if possible, reroute the traffic to
minimize the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC a loss of provisioning data may occur. Do
not remove any subtending modules during a
GMD/DOSC/UOSC replacement.

Attention: You can perform this procedure while DOC is set to Auto
Re-optimize As Necessary. However, DOC will raise the DOC Action Failed:
Monitor (549) or DOC Action Failed: Optimize (550) alarm at the DOC
network element. These alarms occur because DOC detects changes in the
system topology. To ensure correct operation, DOC only attempts
equalization when the system topology is stable and determined to be
accurate. To avoid the alarm generation, set DOC to OOS before the
procedure is started. See Configuration, 323-1661-310, for information on
changing DOC settings. Ensure you return DOC to the original settings after
this procedure is completed.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-15

Procedure 4-3 (continued)

Replacing the CMD44 module with the equivalent CMD44

The CMD44 is shipped with

• mounting brackets pre-installed in the 5-inch setback position for
installation into a 19-inch frame
• standard Common Photonic Layer grounding bracket
• two-hole ground lug
• screws for mounting into a 19-inch frame
• twenty 90-degree boot clips (see the procedure on installing a 90-degree
bootclip to a patch cord boot [for CMD44 only], in Installation,
323-1601-201, before routing fiber to a CMD44)

Attention: You must configure mounting brackets on a CMD44 module for

a 19-inch frame or a PTE2000 frame in a 6-inch setback position, for a
23-inch frame in a 5-inch or 6-inch setback position, or for an ETSI frame.
You then install the CDM44 module into the required frame.

The CMD44 module is shipped with mounting brackets pre-installed in the

5-inch setback position for a 19-inch frame or a PTE2000 frame (if the
PTE2000 frame is pre-installed with either a 22U adapter kit [NTT899BA/BF]
or a 6U adapter kit [NTT899BB]). The 22U or 6U adapter kits convert the
aperture of the PTE2000 frame to 19-inch EIA standard mounting centers.
For installation details, see Installation, 323-1661-201.

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have the correct replacement module (the replacement product
engineering code [PEC] is the same as the current PEC).
• Unpack and inspect the CMD44 module.
• Be familiar with the manufacturer’s torque specifications for the 19-inch,
23-inch, or ETSI frame, as required.
• Have a 3/8-in. wrench.
• Have a 10-mm socket.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-16 Module and component replacement

Procedure 4-3 (continued)

Replacing the CMD44 module with the equivalent CMD44

Procedure steps

Step Action

Remove the module

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2 Set all Domain Optical Controllers (DOC) within this domain OOS. See
Configuration, 323-1661-310.

Attention: Other DOC domains will not be able to optimize or add/delete

channels when DOC is put OOS in this domain.

3 Check the active alarms on the network element (Faults->Active Alarms).

Depending on the configuration of the node where this procedure is to be
performed, the Adjacency Far End Not Discovered (538) alarm can appear
throughout the network during this procedure.
4 Verify that the replacement product engineering code (PEC) is the same as
the current PEC.
5 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
6
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. See Installation, 323-1661-201, for information on labeling cable
and optical fibers.
7 Unscrew the two 3/8-in nuts and lock washers over the ground pins (located
on the side of the module).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-17

Procedure 4-3 (continued)

Replacing the CMD44 module with the equivalent CMD44

Step Action

8
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

Disconnect all optical connectors on the CMD44.

9 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
10 Remove the existing CMD4 by removing the mounting screws from the frame.
Install the module
11 If you are installing a CMD44 module into a Then go to
19-inch frame or PTE2000 frame (pre-installed with step 12
a 22U or 6U adapter kit)
23-inch or ETSI frame step 13

12 Go to the procedure on installing a CMD44 into a frame, in Installation,

Part 2 of 2, 323-1661-201. Complete all the steps for installing a CMD44 into
a 19-inch frame or PTE2000 frame. Then, go to step 14.
13 Go to the procedure on installing a CMD44 into a frame, in Installation,
Part 2 of 2, 323-1661-201. Complete all the steps for installing a CMD44 into
a 23-inch frame or an ETSI frame. Then, go to step 14.
14 Secure the two 3/8-in. nuts and lock washers over the ground pins.
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque the 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

15 Clean all fiber connectors disconnected from the ports in step 8 and
reconnect them to the appropriate ports on the CMD44. For instructions on
inspecting and cleaning optical fiber, see SLAT and Channel Procedures,
323-1661-221.
16 If necessary, adjust the 90-degree bootclips to the boot of each patch cord
installed on the CMD44.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-18 Module and component replacement

Procedure 4-3 (continued)

Replacing the CMD44 module with the equivalent CMD44

Step Action

17 Check the active alarms (Faults->Active Alarms) for alarms that can occur:
• Loss Of Signal (553, 560)
• DOC Action: Fault Detected (873)
• DOC Action Failed: Monitor (549)
• Channel Controller: Unexpected Loss Detected (877)

18 Undo any traffic switches preformed in step 5.

19 Put both of the Domain Optical Controllers back in-service; a re-optimization
is recommended. See Configuration, 323-1661-310.
20 Update the user label with the current shelf number. See Configuration,
323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-19

Procedure 4-4
Replacing the CMD4 module with the equivalent
CMD4
Use this procedure to replace the 4 Channel Mux/Demux (CMD4) module with
another CMD4 with the same PEC.

CAUTION
Service affecting procedure
CMD4 module replacement is service affecting. Ensure you
have exhausted all other troubleshooting options before
performing this procedure and if possible, reroute the traffic to
minimize the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC a loss of provisioning data may occur. Do
not remove any subtending modules during a
GMD/DOSC/UOSC replacement.

Attention: You can perform this procedure while DOC is set to Auto
Re-optimize As Necessary. However, DOC will raise the DOC Action Failed:
Monitor (549) or DOC Action Failed: Optimize (550) alarm at the DOC
network element. These alarms occur because DOC detects changes in the
system topology. To ensure correct operation, DOC only attempts
equalization when the system topology is stable and determined to be
accurate. To avoid the alarm generation, set DOC to OOS before the
procedure is started. See Configuration, 323-1661-310, for information on
changing DOC settings. Ensure you return DOC to the original settings after
this procedure is completed.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-20 Module and component replacement

Procedure 4-4 (continued)

Replacing the CMD4 module with the equivalent CMD4

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Be logged into the Craft interface. See Configuration, 323-1661-310.
• Have the correct replacement module (the replacement product
engineering code (PEC) is the same as the current PEC).
• Have a 10-mm socket.
• Have a torque wrench.
Procedure steps

Step Action

Remove the module

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2 Set all Domain Optical Controllers (DOC) within this domain OOS. See
Configuration, 323-1661-310.

Attention: Other DOC domains will not be able to optimize or add/delete

channels when DOC is put OOS in this domain.

3 Check the active alarms on the network element (Faults->Active Alarms).

Depending on the configuration of the node where this procedure is to be
performed, the following alarms can appear throughout the network during
this procedure:
• Adjacency Far End Not Discovered (538)
• Circuit Pack Missing (579)
• Loss Of Signal (553, 560)
• Power Failure - A (594)
• Power Failure - B (595)
4 Verify that the replacement product engineering code (PEC) is the same as
the current PEC.
5 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-21

Procedure 4-4 (continued)

Replacing the CMD4 module with the equivalent CMD4

Step Action

6
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Turn off the power feeds to the CMD4 at the breaker panel.
7 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Ensure labels are applied to the breaker interface panel or fuse
panel. See Installation, 323-1661-201, for information on labeling cable and
optical fibers.
8
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections; otherwise, you risk an electric shock.
Ensure the power feeds to the CMD4 at the breaker
panel are off (0).

Ensure the power feeds to the CMD4 at the breaker panel are off (0) and
disconnect the A and B power connectors on the CMD4.
9 Unscrew the two 3/8-in nuts and lock washers over the ground pins (located
on the left side of the module).
10 Disconnect the Ethernet and RS-232 cables from the CMD4.
11
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

Disconnect all optical connectors (Ch 1... Ch 4 and Common) on the CMD4.
12 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
13 Pull out and hold the CMD4 spring plunger and remove the existing CMD4
from the frame.
Install the module
14 Install the replacement CMD4 into the frame.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-22 Module and component replacement

Procedure 4-4 (continued)

Replacing the CMD4 module with the equivalent CMD4

Step Action

15 Secure the two 3/8-in. nuts and lock washers over the ground pins.
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque the 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

16 Reconnect all Ethernet cables, disconnected in step 10, to the CMD4.
17 Clean all fiber connectors disconnected from the Channel and common ports
in step 11 and reconnect them to the appropriate ports on the CMD4. For
instructions on inspecting and cleaning optical fiber, see SLAT and Channel
Procedures, 323-1661-221.
18
DANGER
Risk of electric shock
Exercise caution when connecting power connections;
otherwise, you risk an electric shock. Ensure the power
feeds to the CMD4 at the breaker panel are off (0).

Ensure the power feeds to the CMD4 at the breaker panel are off (0) and
connect the A and B power connectors disconnected in step 11 to the CMD4.
19 At the breaker panel, turn on the power feeds to the CMD4.
20 Wait for the CMD4 to start.
21 Check the active alarms (Faults->Active Alarms).
22 If the Software Auto-Upgrade in Progress (439) is active, wait until the alarm
clears before continuing.

Attention: It can take up to 20 minutes for this alarm to clear.

23 If the Circuit Pack Upgrade Failed (124) is active, clear this alarm using the
procedure in this document.
24 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact your next level of support or your Nortel support
group.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-23

Procedure 4-4 (continued)

Replacing the CMD4 module with the equivalent CMD4

Step Action

25 Undo any traffic switches performed in step 5.

26 Put both of the Domain Optical Controllers back in-service, a re-optimization
is recommended. See Configuration, 323-1661-310.
27 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-24 Module and component replacement

Procedure 4-5
Replacing the CMD4 module with the SCMD4 module
Use this procedure to replace the 4 Channel Mux/Demux (CMD4) module with
a serial 4 Channel Mux/Demux (SCMD4) module (in both directions).

CAUTION
Service affecting procedure
CMD4 to SCMD4 module replacement is service affecting.
Ensure that you have exhausted all other troubleshooting
options before performing this procedure and if possible,
reroute the traffic to minimize the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC a loss of provisioning data may occur. Do
not remove subtending modules during a GMD/DOSC/UOSC
replacement.

Attention: If you are replacing a CMD4 with a SCMD4 and the SCMD4
wavelength is a 100 GHz spacing wavelength, then you can replace the
CMD4 with an SCMD4 at either or both ends of the traffic path (that is, define
Tx/Rx adjacencies using an SCMD4 at one end, and use a CMD4 at the
other end, or use SCMD4s at both ends of the traffic path). If you are
replacing a CMD4 with a SCMD4 and the SCMD4 wavelength is a 50 GHz
spacing wavelength, then this procedure must be completed at both the
ingress and egress network elements. See the Planning Guide, NTT840FE,
for information related to 100 GHz and 50 GHz sources on the same link.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-25

Procedure 4-5 (continued)

Replacing the CMD4 module with the SCMD4 module

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Be logged into the Craft interface. See Configuration, 323-1661-310.
• Have the correct SCMD4 replacement module (you must have a
replacement SCMD4 module with a wavelength group that corresponds to
the wavelength group of the CMD4 module being replaced).
• Have a 10-mm socket.
• Have a torque wrench.
Procedure steps

Step Action

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2 Verify the current alarm conditions on the network element. Depending on the
configuration of the node where this procedure is to be performed the
following alarms can appear throughout the network during this procedure:
• Adjacency Far End Not Discovered (538)
• Automatic Shutoff (590, 942)
• DOC Domain Not Optimized (551)
• Gauge Threshold Crossing Alert Summary (724, 725, 726)
• Loss Of Signal (553, 560)
• Power Failure - A (594)
• Power Failure - B (595)
3 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
4 In direction 1, the DOC Automation Mode must be set to “No Auto
monitoring”. See Configuration, 323-1661-310, for information on changing
DOC settings.
5 In direction 2, the DOC Automation Mode must be set to “No Auto
monitoring”. See Configuration, 323-1661-310, for information on changing
DOC settings.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-26 Module and component replacement

Procedure 4-5 (continued)

Replacing the CMD4 module with the SCMD4 module

Step Action

Remove the CMD4

6
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Turn off the power feeds to the CMD4 at the breaker panel.
7 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Ensure labels are applied to the breaker interface panel or fuse
panel. See Installation, 323-1661-201, for information on labeling cable and
optical fibers.
8
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections; otherwise, you risk an electric shock.
Ensure the power feeds to the CMD4 at the breaker
panel are off (0).

Ensure the power feeds to the CMD4 at the breaker panel are off (0) and
disconnect the A and B power connectors on the CMD4.
9 Unscrew the two 3/8-in nuts and lock washers over the ground pins (located
on the left side of the module).
10 Disconnect the Ethernet and RS-232 cables from the CMD4.
11
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

Disconnect all optical connectors (Ch 1... Ch 4 and Common) on the CMD4.
12 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
13 Pull out and hold the CMD4 spring plunger and remove the existing CMD4
from the frame.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-27

Procedure 4-5 (continued)

Replacing the CMD4 module with the SCMD4 module

Step Action

Install the SCMD4

14
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Install the replacement SCMD4 into the frame.

15 Secure the two 3/8-in. nuts and lock washers over the ground pins.
16
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque the 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

17 Connect all Ethernet cables, disconnected in step 10, to the SCMD4.
18 Clean all fiber connectors disconnected from the channel, and common ports
in step 11 and connect them to the appropriate ports on the SCMD4. For
instructions on inspecting and cleaning optical fiber, see SLAT and Channel
Procedures, 323-1661-221.
19
DANGER
Risk of electric shock
Exercise caution when connecting power connections;
otherwise, you risk an electric shock. Ensure the power
feeds to the SCMD4 at the breaker panel are off (0).

Ensure the power feeds to the SCMD4 at the breaker panel are off (0) and
connect the A and B power connectors disconnected in step 8 to the SCMD4.
20 At the breaker panel, turn on the power feeds to the SCMD4.
21 Wait for the SCMD4 to start.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-28 Module and component replacement

Procedure 4-5 (continued)

Replacing the CMD4 module with the SCMD4 module

Step Action

22 In the equipment list, edit the PEC from a CMD4 Grp X to a SCMD4 Grp X:
• Highlight the CMD4 in the Equipment screen.
• Select the Edit button.
• Edit the Card Type field to sCDM4.
• Edit the Card Variant field to SCMD4 Group x. (Use the appropriate
group. For example, change NTT810BB for a group 2 CMD4 to
NTT810CB for a group 2 SCMD4.) See Configuration, 323-1661-310, for
details.
23 Check the active alarms (Faults->Active Alarms).
24 If the Software Auto-Upgrade in Progress (439) alarm is active, wait until the
alarm clears before continuing.

Attention: It can take up to 20 minutes for this alarm to clear.

25 If the Circuit Pack Upgrade Failed (124) is active, clear this alarm using the
procedure in this document.
26 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact your next level of support or your Nortel support
group.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)
27 Return the DOC automation mode back to what it was set to at the beginning
of the procedure. Make sure that DOC is optimal in both directions. Select the
Re-Optimize button in the DOC screen. See Configuration, 323-1661-310,
for information on changing DOC settings.
28 Undo any traffic switches performed in step 3.
29 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-29

Procedure 4-6
Replacing the CMD4 module with the SCMD8 module
Use this procedure to replace the 4 Channel Mux/Demux (CMD4) module with
a serial 8 Channel Mux/Demux (SCMD8) module (in both directions).

CAUTION
Service affecting procedure
CMD4 to a SCMD8 module replacement is service affecting.
Ensure you have exhausted all other troubleshooting options
before performing this procedure and if possible, reroute the
traffic to minimize the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC a loss of provisioning data may occur. Do
not remove subtending modules during a GMD/DOSC/UOSC
replacement.

Attention: If you are replacing a CMD4 with a SCMD8 and the SCMD8
wavelength to be used is one of the 100 GHz spacing wavelengths, then the
CMD4 can be replaced with an SCMD8 at either or both ends of the traffic
path (that is, Tx/Rx adjacencies can be defined using an SCMD8 at one end,
and using a CMD4 at the other end, or using SCMD8s at both ends of the
traffic path). If you are replacing a CMD4 with a SCMD8 and the SCMD8
wavelength to be used is one of the 50 GHz spacing wavelengths, then this
procedure must be completed at both the ingress and egress network
elements. See the Planning Guide, NTT840FE, for information related to
100 GHz and 50 GHz sources on the same link.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-30 Module and component replacement

Procedure 4-6 (continued)

Replacing the CMD4 module with the SCMD8 module

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Be logged into the Craft. See Configuration, 323-1661-310.
• Have the correct SCMD8 replacement module (you must have a
replacement SCMD8 module with a wavelength group that corresponds to
the wavelength group of the CMD4 module being replaced).
• Have a 10-mm socket.
• Have a torque wrench.
Procedure steps

Step Action

Deprovision the CMD4 module

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2 Verify the current alarm conditions on the network element. Depending on the
configuration of the node where this procedure is to be performed the
following alarms can appear throughout the network during this procedure:
• Adjacency Far End Not Discovered (538)
• Automatic Shutoff (590, 942)
• DOC Domain Not Optimized (551)
• Gauge Threshold Crossing Alert Summary (724, 725, 726)
• Loss Of Signal (553, 560)
• Power Failure - A (594)
• Power Failure - B (595)
3 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-31

Procedure 4-6 (continued)

Replacing the CMD4 module with the SCMD8 module

Step Action

4 In direction 1, use DOC to perform a non-service affecting manual delete of

all ingress and egress wavelengths on the CMD4 that is being replaced. See
SLAT and Channel procedures, 323-1661-221.

Attention: The DOC Automation Mode must be set to No Automation in

order to perform the manual delete procedure. See Configuration,
323-1661-310, for information on changing DOC settings.

5 In direction 2, use DOC to perform a non-service affecting manual delete of

all ingress and egress wavelengths on the CMD4 that is being replaced. See
SLAT and Channel Procedures, 323-1661-221.

Attention: The DOC Automation Mode must be set to No Automation in

order to perform the manual delete procedure. See Configuration,
323-1661-310, for information on changing DOC settings.

6 Remove all the VOA and OPTMON facilities from service on the CMD4s
being replaced. See Configuration, 323-1661-310, for details on how to
remove an optical facility from service.
7 Delete all the VOA and OPTMON facilities from service on the CMD4s being
replaced. See Configuration, 323-1661-310, for details on how to delete an
optical facility.
8 In the Facility->Adjacencies screen, select the transmitters and receivers
attached to the CMD4 being replaced and set their Transmitter type to
Unknown. See Configuration, 323-1661-310, for adjacency provisioning
details.
9 Delete the transmitter and receiver facilities attached to the CMD4 being
replaced. See Configuration, 323-1661-310, for details on how to delete the
transmitter and receiver facilities.
10 Delete the ADJ-TX and RX facilities on the CMD4s being replaced. See
Configuration, 323-1661-310, for details on how to delete the ADJ-TX and RX
facilities.
11 Remove the CMD4s being replaced from service. See Configuration,
323-1661-310, for details on how to remove equipment from service.
12 Delete the CMD4s being replaced. See Configuration, 323-1661-310, for
details on how to delete equipment.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-32 Module and component replacement

Procedure 4-6 (continued)

Replacing the CMD4 module with the SCMD8 module

Step Action

Remove the CMD4

13
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Turn off the power feeds to the CMD4 at the breaker panel.
14 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Ensure labels are applied to the breaker interface panel or fuse
panel. See Installation, 323-1661-201, for information on labeling cable and
optical fibers.

15
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections; otherwise, you risk an electric shock.
Ensure the power feeds to the CMD4 at the breaker
panel are off (0).

Ensure the power feeds to the CMD4 at the breaker panel are off (0) and
disconnect the A and B power connectors on the CMD4.
16 Unscrew the two 3/8-in nuts and lock washers over the ground pins (located
on the left side of the module).
17 Disconnect the Ethernet and RS-232 cables from the CMD4.
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

18 Disconnect all optical connectors (Ch 1... Ch 4 and Common) on the CMD4.
19 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
20 Pull out and hold the CMD4 spring plunger and remove the existing CMD4
from the frame.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-33

Procedure 4-6 (continued)

Replacing the CMD4 module with the SCMD8 module

Step Action

Install the SCMD8

21
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Install the replacement SCMD8 into the frame.

22 Secure the two 3/8-in. nuts and lock washers over the ground pins.
23
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque the 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

24 Connect all Ethernet cables, disconnected in step 17, to the SCMD8.
25 Clean all fiber connectors disconnected from the channel, and common ports
in step 18 and connect them to the appropriate ports on the SCMD8. For
instructions on inspecting and cleaning optical fiber, see SLAT and Channel
Procedures, 323-1661-221.
26
DANGER
Risk of electric shock
Exercise caution when connecting power connections;
otherwise, you risk an electric shock. Ensure the power
feeds to the SCMD8 at the breaker panel are off (0).

Ensure the power feeds to the SCMD8 at the breaker panel are off (0) and
connect the A and B power connectors disconnected in step 15 to the
SCMD8.
27 At the breaker panel, turn on the power feeds to the SCMD8.
28 Wait for the SCMD8 to start.
29 Check the active alarms (Faults->Active Alarms).
30 If the Software Auto-Upgrade in Progress (439) alarm is active, wait until the
alarm clears before continuing.
31 If the Circuit Pack Upgrade Failed (124) is active, clear this alarm using the
procedure in this document.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-34 Module and component replacement

Procedure 4-6 (continued)

Replacing the CMD4 module with the SCMD8 module

Step Action

32 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact your next level of support or your Nortel support
group.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)
33 Edit the Tx and Rx adjacencies for the channels attached to the new SCMD8.
See Configuration, 323-1661-310, for information on editing adjacencies.
34 Ensure the Shelf Wavelength Topology populates for both directions. See
Configuration, 323-1661-310, for details on how to display shelf wavelength
topology.
35 In direction 1, use DOC to perform a non-service affecting add of all ingress
and egress wavelengths on the new SCMD8. See SLAT and Channel
Procedures, 323-1661-221.
36 In direction 2, use DOC to perform a non-service affecting add of all ingress
and egress wavelengths on the new SCMD8. See SLAT and Channel
Procedures, 323-1661-221.
37 Make sure that the DOC condition for each wavelength in both directions is
Optimal. To re-optimize the system, select the Re-optimize button in the
DOC screen. DOC will re-optimize the system automatically as required. See
Configuration, 323-1661-310, for information on changing DOC settings.
38 Undo any traffic switches performed in step 3.
39 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-35

Procedure 4-7
Replacing an Open SCMD8 module with a Filtered
SCMD8 module
Use this procedure to replace an Open Serial 8 Channel Mux/Demux module
with a Filtered Serial 8 Channel Mux/Demux module (in both directions).

CAUTION
Service affecting procedure
Open SCMD8 module to Filtered SCMD8 module replacement
is service affecting. Ensure that you have exhausted all other
troubleshooting options before performing this procedure and
if possible, reroute the traffic to minimize the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC, a loss of provisioning data can occur. Do
not remove subtending modules during a GMD/DOSC/UOSC
replacement.

Attention: If you are replacing an Open SCMD8 module with a Filtered

SCMD8 module and the Filtered SCMD8 wavelength is a 100 GHz spacing
wavelength, then you can replace the Open SCMD8 module with a Filtered
SCMD8 module at either or both ends of the traffic path (that is, define Tx/Rx
adjacencies using a Filtered SCMD8 module at one end, and use an Open
SCMD8 module at the other end, or use Filtered SCMD8 modules at both
ends of the traffic path). If you are replacing an Open SCMD8 module with a
Filtered SCMD8 module and the Filtered SCMD8 wavelength is a 50 GHz
spacing wavelength, then this procedure must be completed at both the
ingress and egress network elements. See the Planning Guide, NTT840FE,
for information related to 100 GHz and 50 GHz sources on the same link.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-36 Module and component replacement

Procedure 4-7 (continued)

Replacing an Open SCMD8 module with a Filtered SCMD8 module

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have the correct Filtered SCMD8 replacement module (you must have a
replacement Filtered SCMD8 module with a wavelength group that
corresponds to the wavelength group of the Open SCMD8 module being
replaced).
• Have a 10-mm socket.
• Have a torque wrench.
Procedure steps

Step Action

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2 Verify the current alarm conditions on the network element. Depending on the
configuration of the node where this procedure is to be performed the
following alarms can appear throughout the network during this procedure:
• Adjacency Far End Not Discovered (538)
• Automatic Shutoff (590, 942)
• DOC Domain Not Optimized (551)
• Gauge Threshold Crossing Alert Summary (724, 725, 726)
• Loss Of Signal (553, 560)
• Power Failure - A (594)
• Power Failure - B (595)
3 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
4 In direction 1, the DOC Automation Mode must be set to “No Auto
monitoring”. See Configuration, 323-1661-310, for information on changing
DOC settings.
5 In direction 2, the DOC Automation Mode must be set to “No Auto
monitoring”. See Configuration, 323-1661-310, for information on changing
DOC settings.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-37

Procedure 4-7 (continued)

Replacing an Open SCMD8 module with a Filtered SCMD8 module

Step Action

Remove the Open SCMD8 module

6
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Turn off the power feeds to the Open SCMD8 module at the breaker panel.
7 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Ensure labels are applied to the breaker interface panel or fuse
panel. See Installation, Part 2 of 2, 323-1661-201, for information on labeling
cable and optical fibers.
8
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections; otherwise, you risk an electric shock.
Ensure the power feeds to the Open SCMD8 module at
the breaker panel are off (0).

Ensure the power feeds to the Open SCMD8 module at the breaker panel are
off (0) and disconnect the A and B power connectors on the Open SCMD8
module.
9 Unscrew the two 3/8-in nuts and lock washers over the ground pins (located
on the left side of the module).
10 Disconnect the Ethernet and RS-232 cables from the Open SCMD8 module.
11
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

Disconnect all optical connectors (Ch 1... Ch 4 and Common) on the Open
SCMD8 module.
12 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
13 Pull out and hold the Open SCMD8 module spring plunger and remove the
existing Open SCMD8 module from the frame.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-38 Module and component replacement

Procedure 4-7 (continued)

Replacing an Open SCMD8 module with a Filtered SCMD8 module

Step Action

Install the Filtered SCMD8 module

14
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Install the replacement Filtered SCMD8 module into the frame.

15 Secure the two 3/8-in. nuts and lock washers over the ground pins.
16
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque the 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

17 Connect all Ethernet cables, disconnected in step 10, to the Filtered SCMD8
module.
18 Clean all fiber connectors disconnected from the channel, and common ports
in step 11 and connect them to the appropriate ports on the Filtered SCMD8
module. For instructions on inspecting and cleaning optical fiber, see SLAT
and Channel Procedures, 323-1661-221.
19
DANGER
Risk of electric shock
Exercise caution when connecting power connections;
otherwise, you risk an electric shock. Ensure the power
feeds to the Filtered SCMD8 at the breaker panel are
off (0).

Ensure the power feeds to the Filtered SCMD8 module at the breaker panel
are off (0) and connect the A and B power connectors disconnected in step 8
to the Filtered SCMD8 module.
20 At the breaker panel, turn on the power feeds to the Filtered SCMD8 module.
21 Wait for the Filtered SCMD8 module to start.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-39

Procedure 4-7 (continued)

Replacing an Open SCMD8 module with a Filtered SCMD8 module

Step Action

22 From the Craft, in the equipment list (Configuration–>Equipment), edit the

PEC from an SCMD8 Gr x Open to a SCMD8 Gr x Filtered:
• Highlight the Open SCMD8 in the Equipment screen.
• Select the Edit button.
• Edit the Card Type field to Filtered SCDM8 (SCDM8 Gr x Filtered).
• Edit the Card Variant field to Filtered SCMD8 Group x (Use the
appropriate group). See Configuration, 323-1661-310, for details.
23 Check the active alarms (Faults->Active Alarms).
24 If the Software Auto-Upgrade in Progress (439) alarm is active, wait until the
alarm clears before continuing.

Attention: It can take up to 20 minutes for this alarm to clear.

25 If the Circuit Pack Upgrade Failed (124) is active, clear this alarm using the
procedure in this document.
26 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact your next level of support or your Nortel support
group.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)
27 Return the DOC automation mode back to what it was set to at the beginning
of the procedure. Make sure that DOC is optimal in both directions. Select the
Re-Optimize button in the DOC screen. See Configuration, 323-1661-310,
for information on changing DOC settings.
28 Undo any traffic switches performed in step 3.
29 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-40 Module and component replacement

Procedure 4-8
Replacing an MLA module with an MLA2 module or an
MLA2 module with an MLA module
Use this procedure to replace the following modules:
• an MLA module with an MLA2 module
• an MLA2 module with an MLA module

Attention: An MLA module can replace an MLA2 module only in some

applications since the MLA2 module provides more gain than an MLA
module. You can use the Optical Modeler to verify if you can use an MLA
module in place of an MLA2 module.

CAUTION
Service affecting procedure
Amplifier module replacement is service affecting. Ensure that
you have completed all other troubleshooting options before
performing this procedure and, if possible, re-route the traffic to
minimize the traffic loss.

CAUTION
Loss of provisioning data
If a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC, a loss of provisioning data can occur. Do
not remove any subtending modules during a
GMD/DOSC/UOSC replacement.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-41

Procedure 4-8 (continued)

Replacing an MLA module with an MLA2 module or an MLA2 module with an MLA module

Attention: You can perform this procedure while DOC is set to Auto
Re-optimize As Necessary. However, DOC will raise the DOC Action Failed:
Monitor (549) or DOC Action Failed: Optimize (550) alarm at the DOC
network element. These alarms occur because DOC detects changes in the
system topology. To ensure correct operation, DOC only attempts
equalization when the system topology is stable and determined to be
accurate. To avoid the alarm generation, set DOC OOS before the procedure
is started. See Configuration, 323-1661-310, for information on changing
DOC settings. Ensure that you return DOC to the original settings after this
procedure is completed.

No action is required to recover the software or data configuration unless a

problem recovery scenario occurs. Alarms are raised identifying specific
problems.

When replacing an MLA module with an MLA2 module or an MLA2 module

with an MLA module, you must change the AMP facility Input LOS threshold,
Output LOS threshold, and Shutoff Threshold on the replacement MLA/MLA2
module to match the AMP facility threshold values on the MLA/MLA2 module
that you are replacing.

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have the correct replacement module.
• Have a 10-mm socket.
• Have a torque wrench.

Procedure steps
Step Action

Remove the module

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-42 Module and component replacement

Procedure 4-8 (continued)

Replacing an MLA module with an MLA2 module or an MLA2 module with an MLA module

Step Action

2 Verify the current alarm conditions on the network element. Depending on the
configuration of the node where this procedure is to be performed the
following alarms can appear throughout the network during this procedure:
• Adjacency Far End Not Discovered (538)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Circuit Pack Missing (579)
• DOC Invalid Photonic Domain (552)
• Loss Of Signal (553, 560)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Power Failure - A (594)
• Power Failure - B (595)
• Shutoff Threshold Crossed (540)

3 Go to the Craft and record the AMP facility Input LOS threshold, Output LOS
threshold, and Shutoff Threshold for the MLA/MLA2 module that you are
replacing (Facilities->AMP). Change these AMP facility threshold values from
the Craft to match the AMP facility threshold values for the replacement
MLA/MLA2 module. See Configuration, 323-1661-310, for instructions on
changing these threshold values.
4 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-43

Procedure 4-8 (continued)

Replacing an MLA module with an MLA2 module or an MLA2 module with an MLA module

Step Action

5
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical am-
plifier is out of service (OOS).

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Remove from service the amplifier facilities (AMP, OPTMON) for the module
being replaced. See Configuration, 323-1661-310, for information on
removing optical facilities from service.
6 Remove the amplifier equipment from service. See Configuration,
323-1661-310, for information on removing equipment from service.
7 Edit the Card Variant to match that of the replacement amplifier. In the
Configuration->Equipment screen, select the amplifier begin replaced. Select
the Edit button and edit the Card Variant to match that of the replacement
module.
8 Turn off the power feeds to the amplifier at the breaker panel.
9 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Ensure labels are applied to the breaker interface panel or fuse
panel. See Installation, Part 2 of 2, 323-1661-201, for information on labeling
cable and optical fibers.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-44 Module and component replacement

Procedure 4-8 (continued)

Replacing an MLA module with an MLA2 module or an MLA2 module with an MLA module

Step Action

10
DANGER
Risk of electric shock
Exercise caution when disconnecting power connec-
tions; otherwise, you risk an electric shock. Ensure the
power feeds to the amplifier at the breaker panel are off
(0).

Ensure the power feeds to the amplifier at the breaker panel are off (0) and
disconnect the A and B power connectors on the amplifier.
11 Unscrew the two 3/8-in. nuts and lock washers over the ground pins (located
on the left side of the module).
12 Disconnect the Ethernet and RS-232 cables from the amplifier.
13 Disconnect all optical connectors (Line A, Line B, OSC A, OSC B, Mon 1 and
Mon 2) on the amplifier.
14 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
15 Pull out and hold the amplifier spring plunger and remove the existing
amplifier from the frame.
Install the module
16 Install the replacement amplifier into the frame.
17 Secure the two 3/8-in. nuts and lock washers over the ground pins.
18
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque two 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

19 Reconnect all Ethernet and RS-232 cables disconnected in step 12 to the
amplifier.
20 Clean all fiber connectors disconnected from the Mon, OSC, and Line ports
in step 13 and reconnect them to the appropriate ports on the amplifier. For
instructions on inspecting and cleaning optical fiber, see SLAT and Channel
Procedures, 323-1661-221.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-45

Procedure 4-8 (continued)

Replacing an MLA module with an MLA2 module or an MLA2 module with an MLA module

Step Action

21
DANGER
Risk of electric shock
Exercise caution when connecting power connections;
otherwise, you risk an electric shock. Ensure the power
feeds to the amplifier at the breaker panel are off.

Ensure the power feeds to the amplifier at the breaker panel are off and
connect the A and B power connectors disconnected in step 11 to the
amplifier.
22 At the breaker panel turn on the power feeds to the amplifier.
23 Wait for the amplifier to start. The active LED should be green.
24 Restore the amplifier equipment back in-service (IS). See Configuration,
323-1661-310, for information on restoring equipment to service.
25 Restore the amplifier facilities (AMP, OPTMON) back in-service (IS). See
Configuration, 323-1661-310, for information on restoring facilities to service.
26 When the product engineering code (PEC) is changed, the software
automatically changes the amplifier facility thresholds to the default values of
the new PEC.
Thresholds Default MLA Default MLA2
values (dBm) values (dBm)

Shutoff Threshold (port 8) -35 -39

Input LOS Threshold (port 8) -32 -36

Output LOS Threshold (port 8) -10 -9

Shutoff Threshold (port 6) -35 -39

Input LOS Threshold (port 6) -22 -36

Output LOS Threshold (port 6) -6 -9

If you want to set the thresholds to values different than the default, see the
chapter on optical facility provisioning in Configuration, 323-1661-310, for the
procedure on how to edit an optical facility. Note that you cannot use the Craft
interface to change the Shutoff Threshold value; you must use TL1.
27 Check the active alarms (Faults->Active Alarms).
28 If the Software Auto-Upgrade in Progress (439) alarm is active, wait until the
alarm clears before continuing.
29 If the Circuit Pack Upgrade Failed (124) is active, clear this alarm using the
procedures in this document.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-46 Module and component replacement

Procedure 4-8 (continued)

Replacing an MLA module with an MLA2 module or an MLA2 module with an MLA module

Step Action

30 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact Nortel technical support.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)

31 Undo any traffic switches performed in step 4.

32 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-47

Procedure 4-9
Replacing the DOSC module
Use this procedure to replace the Dual Optical Service Channel (DOSC)
module.

Attention: If both a DOSC and a subtending module must be replaced,

contact Nortel technical support.

This procedure covers the following scenarios:

• the active release on the replacement DOSC is the same as the
committed release on the network element and the upgrade state is
inactive
• the active release on the replacement DOSC is the same as the
committed release on the network element and the upgrade state is not
inactive
• the active release on the replacement DOSC is higher than the committed
release on the network element and the upgrade state is inactive and you
have more than one subtending module
• the active release on the replacement DOSC is higher than the committed
release on the network element and the upgrade state is inactive and you
have only one subtending module
• the active release on the replacement DOSC is lower than the committed
release on the network element

Attention: This procedure is simplified and traffic is restored faster if the

replacement DOSC module has the same software release as the rest of the
network element. If you can, Nortel recommends that you
upgrade/downgrade the DOSC module to the same software release as the
rest of the network element before performing this procedure. See SLAT and
Channel Procedures, 323-1661-221, for upgrade and downgrade
procedures during module replacement. If you do not upgrade before
performing this procedure, you will be prompted to upgrade during this
procedure. See the chapter on release and upgrade management in
Configuration, 323-1661-310.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-48 Module and component replacement

Procedure 4-9 (continued)

Replacing the DOSC module

Prerequisites
• Ensure that you have the correct replacement module. You must replace
a DOSC with another DOSC, and not with a UOSC or a GMD.
• Have a PC available.
• You may require access to a CD with a previous CPL release. You
determine which release when you power up the replacement DOSC.
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Make sure you wear an antistatic wrist strap to protect the equipment from
static damage. Connect the wrist strap to the ESD jack on the shelf or the
module. Use an Ethernet cross-over cable to connect your PC to the Craft
port.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have a 10-mm socket.
• Have a torque wrench.

Procedure steps
Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage.

Connect the wrist strap to the ESD jack on the shelf or module.
2 Set all Domain Optical Controllers (DOC) within this domain out of service
(OOS). See Configuration, 323-1661-310.

Attention: Other DOC domains will not be able to optimize or add/delete

channels when DOC is put OOS in this domain.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-49

Procedure 4-9 (continued)

Replacing the DOSC module

Step Action

3
CAUTION
Risk of laser radiation exposure
During this procedure the fiber plant does not have to
be disrupted and the system remains a Class
1(IEC)/Class I (FDA) product.

If the fiber upstream of the DRA Line A input connector

becomes disconnected accidentally while the Raman
Auto Shutoff Disabled feature is active, the radiation at
the exposed fiber can be at hazard level 3B (IEC
60825-2). In this situation, you must take all safety
precautions appropriate to hazard level 3B (IEC
60825-2).

The ORL based APR safety mechanism remains

active.

If the link has DRA modules in one or both directions and the traffic is
unprotected, ensure that the RAMAN facilities in both directions are in Auto
Shutoff Disabled mode. Place both the local and the remote RAMAN facilities
on each span into Auto Shutoff Disabled mode. See Configuration,
323-1661-310, for information about disabling Auto-Shutoff on a RAMAN
facility.

Attention: The RAMAN facility will come out of Auto Shutoff Disabled mode
if there is a restart on the DRA module, or if the RAMAN facility primary state
changes. If communication with the DOSC requiring replacement is not
available and the link has DRA modules, traffic may be lost for the duration of
this procedure.

4 If communication with the DOSC requiring replacement is Then go to

possible step 5
not possible step 8
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-50 Module and component replacement

Procedure 4-9 (continued)

Replacing the DOSC module

Step Action

5 In the Craft interface, check the active alarms (Faults->Active Alarms).

Depending on the configuration of the node where you perform this
procedure, the following alarms can appear throughout the network during
this procedure.

Attention: No alarm clearing is required at this point.

• Adjacency Far End Not Discovered (538)

• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Automatic Shutoff Disabled (943, 1035)
• Circuit Pack Missing (579)
• DOC Invalid Photonic Domain (552)
• ILAN 1 Port Failure (547)
• ILAN 2 Port Failure (548)
• Loss Of Signal (553, 560)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Power Failure - A (594)
• Power Failure - B (595)

6 In the Craft interface:

a. Perform a remote database save (you can save to a local PC). See the
procedures in the chapter on provisioning data backup and restore, in
Configuration, 323-1661-310.
b. Query the software release currently running on the DOSC module. See
the chapter on release and upgrade management, in Configuration,
323-1661-310.
c. Query the upgrade state. The upgrade state must be inactive. If it is
another state, wait for the upgrade to complete before continuing with this
procedure. See the chapter on release and upgrade management, in
Configuration, 323-1661-310.
7 Log out of the Craft. See the Site Manager chapter in Configuration,
323-1661-310.
8 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Apply labels before you disconnect the cables. Ensure labels are
applied to the breaker interface panel or fuse panel. See Installation,
Part 2 of 2, 323-1661-201, for information on labeling cable and optical fibers.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-51

Procedure 4-9 (continued)

Replacing the DOSC module

Step Action

9
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections to prevent electric shock.

Ensure the power feeds to the DOSC at the breaker panel are off (0) and
disconnect the A and B power connectors on the DOSC.
Removing the replacement module
10 Unscrew the two 3/8-in. nuts and lock washers over the ground pins (located
on the left side of the module).
11
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical
amplifier is out of service (OOS).

Disconnect all electrical cables (Ethernet, Alarm/Telemetry, Modem) and all

optical patch cords from the DOSC. Put protective caps on the ends of the
patch cords to protect them from contamination and damage.
12 Pull out and hold the DOSC spring plunger and remove the existing DOSC
from the frame.
Installing the replacement module
13 Install the replacement DOSC into its slot in the frame.
14 Secure the two 3/8-inch nuts and lock washers over the ground pins.
15
CAUTION
Risk of damage to equipment
Use a torque wrench to prevent damage to the
equipment.

Secure the two 3/8-inch nuts to a value of 60 in.lbf (6.8 Nm).

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-52 Module and component replacement

Procedure 4-9 (continued)

Replacing the DOSC module

Step Action

16 Reconnect to the subtending modules the Ethernet cables you disconnected

in step 11.
17
DANGER
Risk of electric shock
Exercise caution when connecting power connections
to prevent electric shock.

Ensure the power feeds to the DOSC at the breaker panel are off and connect
to the DOSC the A and B power connectors disconnected in step 9.
18 Reconnect the rest of the electrical cables (Alarm/Telemetry, Modem) and
optical patch cords disconnected in step 11. Make sure that you clean all fiber
connectors before reconnecting. For instructions on cleaning optical fibers,
see SLAT and Channel Upgrade Procedures, 323-1661-221.

Attention: Ensure that all the cables to the subtending modules are
reconnected, otherwise there is a risk that the modules will lose their
provisioning information.

19
DANGER
Risk of electric shock
Exercise caution when connecting power connections
to prevent electric shock.

Turn on the power feeds to the DOSC at the breaker panel. Wait 10 minutes
for the DOSC to start.
20 Determine the number of subtending modules.
If there is Then go to
only one subtending module step 21
more than one subtending module step 27

21 Launch a new web browser and log into the Craft with the default ADMIN level
username and password.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-53

Procedure 4-9 (continued)

Replacing the DOSC module

Step Action

22 Select your next step.

If Then go to
the Craft opens in the Restore Local Database tab of step 23
the Backup and Restore application
otherwise step 28

23 Because only two modules are available (the DOSC and one subtending
module) the system is not able to automatically recover a database. The Craft
interface opens in the Restore Local Database tab of the Backup and Restore
application and lists the slots with valid databases. Select the subtending
module slot from the list and click the Restore Local button.
When the restore is complete, the Commit button will be active.
24 Click the Commit button.
A dialog window opens asking to confirm the Commit.
25 Click the Yes button.
The NE restarts, which results in loss of communication with the Craft
interface.
26 Wait 10 minutes for the DOSC to restart.
27 Launch a new web browser and log into the Craft; you may have to use the
default or provisioned ADMIN level password.
28 In the Craft, check the active alarms (Faults->Active Alarms). Shortly after the
fiber connections are completed and the DOSC restarts, OSC related alarms
at this site and at the adjacent sites clear.

Attention: If there is more than one subtending module, the Database Not
Recovered alarm should not be active.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-54 Module and component replacement

Procedure 4-9 (continued)

Replacing the DOSC module

Step Action

29 Select your next step.

If the following alarms are raised Then go to
Transport Data Recovery Failed (TDRF) or Flash Bank step 30
Mismatch and Shelf Data Missing

Database Not Recovered (DNR), but no TDRF alarm step 32

Any of: step 36

Incomplete Software Lineup
Software Configuration Unknown
Software Mismatch
Circuit Pack Upgrade Failed
Software Upgrade Failed, but no TDRF or DNR alarm

Software Upgrade in Progress contact your next

level of support

otherwise step 39

30 If the Transport Data Recovery Failed or Flash Bank Mismatch and Shelf
Data Missing alarms are raised:
a. Open a telnet session on the CPL NE and log into the TL1 interface using
the following command. The default ADMIN level username and
password are required to log into the TL1 session.
ACT-USER::<ADMIN Level User>:<CTAG>::<ADMIN Level
password>:;
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-55

Procedure 4-9 (continued)

Replacing the DOSC module

Step Action

b. Determine the application load running on the DOSC using the following
command:
RTRV-SW-VER::SLOT-1-4:<CTAG>;
The output will be in the following format:
<AID>:<swIssue>
The first line of the output indicates the committed software release for
the NE. The remaining lines indicate the software release running on the
DOSC.
For example:
SHELF-1:REL0321P.JD
DOSC-1-4:311842,RAM,APPL,ALIGNED
DOSC-1-4:311842,RAM,BOOT,ALIGNED
DOSC-1-4:311842,BANK0,APPL,ALIGNED
DOSC-1-4:311842,BANK0,BOOT,ALIGNED
DOSC-1-4:311842,BANK1,APPL,ALIGNED
DOSC-1-4:311842,BANK1,BOOT,ALIGNED
Cross-reference the <swIssue> for the line “RAM,APPL” with the
following table.
011587 REL0201P.LE

311836 REL0300P.GD

311842 REL0301P.HF

311986 REL0302P.AE

311982 REL0310P.FP

c. Log out using the following command and close the telnet session:
CANC-USER::<ADMIN Level User>:<CTAG>;
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-56 Module and component replacement

Procedure 4-9 (continued)

Replacing the DOSC module

Step Action

d. Select your next step.

If the software version in substep b is Then
lower than the current release go to step 31
equal to or higher than the current release, contact your next level of
or not in the table support

31 Upgrade the DOSC by performing the procedure in SLAT and Channel

Procedures, 323-1661-221.

Attention: If you perform the upgrade within a TIDc shelf, make sure that the
shelf where the upgrade is occurring is the only one selected in the Craft
Navigation tree. If necessary, expand the TID in the Navigation tree to see the
specific shelf that you must select.

After the upgrade is complete, go to step 39.

32 If the Database Not Recovered (DNR) alarm is raised, but the TDRF alarm is
not, select the database to recover from (Configuration->Backup and
Restore->Restore Local Database tab):
a. Select the subtending module from which to restore the database.
b. Click on the Restore Local button.

33 Click on the Commit button to commit the files that have been restored.
The NE restarts, which results in loss of communication with the Craft
interface.
34 Wait for the DOSC to restart.
The DOSC restarts automatically, which can take up to 10 minutes.
35 Launch a new web browser and log into the Craft; use the previously
provisioned ADMIN level username and password.
36 Open Configuration->Release Management and determine the software
release running on the DOSC:
If the Active software release is Then go to
higher than the Committed release step 37
lower than the Committed release step 38
same as the Committed release step 39

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-57

Procedure 4-9 (continued)

Replacing the DOSC module

Step Action

37 Downgrade the DOSC by performing the procedure in SLAT and Channel

Procedures, 323-1661-221.

Attention: If you perform the downgrade within a TIDc shelf, make sure that
the shelf where the downgrade is occurring is the only one selected in the
Craft Navigation tree. If necessary, expand the TID in the Navigation tree to
see the specific shelf that you must select.

After the downgrade is complete, go to step 39.

38 Upgrade the DOSC by performing the procedure in SLAT and Channel
Procedures, 323-1661-221.

Attention: If you perform the upgrade within a TIDc shelf, make sure that the
shelf where the upgrade is occurring is the only one selected in the Craft
Navigation tree. If necessary, expand the TID in the Navigation tree to see the
specific shelf that you must select.

After the upgrade is complete, go to step 39.

39 Clear any alarms on the system using the appropriate procedure in
Chapter 3, “Alarm clearing” on page 3-1.
40 If the link has DRA modules in one or both directions, clear the Auto Shutoff
Disabled mode set in step 3 on both the local and the remote RAMAN
facilities on each span. See Configuration, 323-1661-310, for information on
enabling Auto-Shutoff on a RAMAN facility.

41 Put both of the Domain Optical Controllers back in-service. A re-optimization

is recommended. See Configuration, 323-1661-310.
42 Perform a BER test or verify performance monitoring data on the service layer
to ensure traffic is error-free. See SLAT and Channel Procedures,
323-1661-221, for more information.
43 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-58 Module and component replacement

Procedure 4-10
Replacing the GMD module
Use this procedure to replace the Group Mux/Demux (GMD) module.

Attention: If both a GMD and a subtending module must be replaced,

contact Nortel technical support.

CAUTION
Service-affecting procedure
GMD replacement is service-affecting. Ensure you have
exhausted all other troubleshooting options before performing
this procedure and if possible, reroute the traffic to minimize
the traffic loss.

This procedure covers the following scenarios:

• the active release on the replacement GMD is the same as the committed
release on the network element and the upgrade state is inactive
• the active release on the replacement GMD is the same as the committed
release on the network element and the upgrade state is not inactive
• the active release on the replacement GMD is higher than the committed
release on the network element and the upgrade state is inactive and you
have more than one subtending module
• the active release on the replacement GMD is higher than the committed
release on the network element and the upgrade state is inactive and you
have only one subtending module
• the active release on the replacement GMD is lower than the committed
release on the network element
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-59

Procedure 4-10 (continued)

Replacing the GMD module

Attention: This procedure is simplified and traffic is restored faster if the

replacement GMD module has the same software release as the rest of the
network element. If you can, Nortel recommends that you
upgrade/downgrade the GMD module to the same software release as the
rest of the network element before performing this procedure. See SLAT and
Channel Procedures, 323-1661-221, for upgrade and downgrade
procedures. If you do not upgrade before performing this procedure, you will
be prompted to upgrade during this procedure. See the chapter on release
and upgrade management in Configuration, 323-1661-310.

Prerequisites
• Ensure that you have the correct replacement module. You must replace
a GMD with another GMD, and not with a UOSC or a DOSC.
• Have a PC available.
• You may require access to a CD with a previous CPL release. You
determine which release when you power up the replacement GMD.
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Make sure you wear an antistatic wrist strap to protect the equipment from
static damage. Connect the wrist strap to the ESD jack on the shelf or the
module. Use an Ethernet cross-over cable to connect your PC to the Craft
port.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have a 10-mm socket.
• Have a torque wrench.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-60 Module and component replacement

Procedure 4-10 (continued)

Replacing the GMD module

Procedure steps
Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage.

Connect the wrist strap to the ESD jack on the shelf or module.
2 Set all Domain Optical Controllers (DOC) within this domain out of service
(OOS). See Configuration, 323-1661-310.

Attention: Other DOC domains will not be able to optimize or add/delete

channels when DOC is put OOS in this domain.

3 Switch traffic away from this node by performing a protection switch at the
service layer (non-Common Photonic Layer equipment) to prevent traffic loss.
4 If communication with the GMD requiring replacement is Then go to
possible step 5
not possible step 10
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-61

Procedure 4-10 (continued)

Replacing the GMD module

Step Action

5 In the Craft interface, check the active alarms (Faults->Active Alarms).

Depending on the configuration of the node where you perform this
procedure, the following alarms can appear throughout the network during
this procedure.

Attention: No alarm clearing is required at this point.

• Adjacency Far End Not Discovered (538)

• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Automatic Shutoff Disabled (943, 1035)
• Circuit Pack Missing (579)
• DOC Invalid Photonic Domain (552)
• ILAN 1 Port Failure (547)
• ILAN 2 Port Failure (548)
• Loss Of Signal (553, 560)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Power Failure - A (594)
• Power Failure - B (595)

6 In the Craft interface:

a. Perform a remote database save (you can save to a local PC). See the
procedures in the chapter on provisioning data backup and restore, in
Configuration, 323-1661-310.
b. Query the software release currently running on the GMD module. See
the chapter on release and upgrade management, in Configuration,
323-1661-310.
c. Query the upgrade state. The upgrade state must be inactive. If it is
another state, wait for the upgrade to complete before continuing with this
procedure. See the chapter on release and upgrade management, in
Configuration, 323-1661-310.
7 Place all amplifier facilities on this NE OOS. See Configuration,
323-1661-310, for information on placing amplifier facilities OOS.
8 If the link has DRA modules in one or both directions, place both the local and
the remote RAMAN facilities on this DRA link OOS. See Configuration,
323-1661-310, for information on placing RAMAN facilities OOS.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-62 Module and component replacement

Procedure 4-10 (continued)

Replacing the GMD module

Step Action

9 Log out of the Craft. See the Site Manager chapter in Configuration,
323-1661-310. Then, go to step 11.
10 If the link has DRA modules in one or both directions and communication is
not possible with the GMD you are replacing, place the remote RAMAN
facilities OOS. See Configuration, 323-1661-310, for information on placing
RAMAN facilities OOS.
11
CAUTION
Risk of laser radiation exposure
During this procedure the fiber plant does not have to
be disrupted and the system remains a Class
1(IEC)/Class I (FDA) product.

If the fiber upstream of the DRA Line A input connector

becomes disconnected accidentally while the Raman
Auto Shutoff Disabled feature is active, the radiation at
the exposed fiber can be at hazard level 3B (IEC
60825-2). In this situation, you must take all safety
precautions appropriate to hazard level 3B (IEC
60825-2).

The ORL based APR safety mechanism remains

active.

Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Apply labels before you disconnect the cables. Ensure labels are
applied to the breaker interface panel or fuse panel. See Installation,
Part 2 of 2, 323-1661-201, for information on labeling cable and optical fibers.
12
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections to prevent electric shock.

Ensure the power feeds to the GMD at the breaker panel are off (0) and
disconnect the A and B power connectors on the GMD.
Removing the replacement module
13 Unscrew the two 3/8-in. nuts and lock washers over the ground pins (located
on the left side of the module).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-63

Procedure 4-10 (continued)

Replacing the GMD module

Step Action

14
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical
amplifier is out of service (OOS).

Disconnect all electrical cables (Ethernet, Alarm/Telemetry, Modem) and all

optical patch cords from the GMD. Put protective caps on the ends of the
patch cords to protect them from contamination and damage.
15 Pull out and hold the GMD spring plunger and remove the existing GMD from
the frame.
Installing the replacement module
16 Install the replacement GMD into its slot in the frame.
17 Secure the two 3/8-inch nuts and lock washers over the ground pins.
18
CAUTION
Risk of damage to equipment
Use a torque wrench to prevent damage to the
equipment.

Secure the two 3/8-inch nuts to a value of 60 in.lbf (6.8 Nm).

19 Reconnect to the subtending modules the Ethernet cables you disconnected
in step 14.
20
DANGER
Risk of electric shock
Exercise caution when connecting power connections
to prevent electric shock.

Ensure the power feeds to the GMD at the breaker panel are off and connect
to the DOSC the A and B power connectors disconnected in step 12.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-64 Module and component replacement

Procedure 4-10 (continued)

Replacing the GMD module

Step Action

21 Reconnect the rest of the electrical cables (Alarm/Telemetry, Modem) and

optical patch cords disconnected in step 14. Make sure that you clean all fiber
connectors before reconnecting. For instructions on cleaning optical fibers,
see SLAT and Channel Upgrade Procedures, 323-1661-221.

Attention: Ensure that all the cables to the subtending modules are
reconnected, otherwise there is a risk that the modules will lose their
provisioning information.

22
DANGER
Risk of electric shock
Exercise caution when connecting power connections
to prevent electric shock.

Turn on the power feeds to the GMD at the breaker panel. Wait 10 minutes for
the GMD to start.
23 Determine the number of subtending modules.
If there is Then go to
only one subtending module step 24
more than one subtending module step 30

24 Launch a new web browser and log into the Craft with the default ADMIN level
username and password.
25 Select your next step.
If Then go to
the Craft opens in the Restore Local Database tab of step 26
the Backup and Restore application
otherwise step 31

26 Because only two modules are available (the GMD and one subtending
module) the system is not able to automatically recover a database. The Craft
interface opens in the Restore Local Database tab of the Backup and Restore
application and lists the slots with valid databases. Select the subtending
module slot from the list and click the Restore Local button.
When the restore is complete, the Commit button will be active.
27 Click the Commit button.
A dialog window opens asking to confirm the Commit.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-65

Procedure 4-10 (continued)

Replacing the GMD module

Step Action

28 Click the Yes button.

The NE restarts, which results in loss of communication with the Craft
interface.
29 Wait 10 minutes for the GMD to restart.
30 Launch a new web browser and log into the Craft; you may have to use the
default or provisioned ADMIN level password..
31 In the Craft, check the active alarms (Faults->Active Alarms). Shortly after the
fiber connections are completed and the GMD restarts, OSC related alarms
at this site and at the adjacent sites clear.

Attention: If there is more than one subtending module, the Database Not
Recovered alarm should not be active.

32 Select your next step.

If the following alarms are raised Then go to
Transport Data Recovery Failed (TDRF) or Flash Bank step 33
Mismatch and Shelf Data Missing

Database Not Recovered (DNR), but no TDRF alarm step 35

Any of: step 39

Incomplete Software Lineup
Software Configuration Unknown
Software Mismatch
Circuit Pack Upgrade Failed
Software Upgrade Failed, but no TDRF or DNR alarm

Software Upgrade in Progress contact your next

level of support

otherwise step 42

33 If the Transport Data Recovery Failed or Flash Bank Mismatch and Shelf
Data Missing alarms are raised:
a. Open a telnet session on the CPL NE and log into the TL1 interface using
the following command. The default ADMIN level username and
password are required to log into the TL1 session.
ACT-USER::<ADMIN Level User>:<CTAG>::<ADMIN Level
password>:;
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-66 Module and component replacement

Procedure 4-10 (continued)

Replacing the GMD module

Step Action

b. Determine the application load running on the GMD using the following
command:
RTRV-SW-VER::SLOT-1-4:<CTAG>;
The output will be in the following format:
<AID>:<swIssue>
The first line of the output indicates the committed software release for
the NE. The remaining lines indicate the software release running on the
GMD.
For example:
SHELF-1:REL0321P.JD
GMD-1-4:311842,RAM,APPL,ALIGNED
GMD-1-4:311842,RAM,BOOT,ALIGNED
GMD-1-4:311842,BANK0,APPL,ALIGNED
GMD-1-4:311842,BANK0,BOOT,ALIGNED
GMD-1-4:311842,BANK1,APPL,ALIGNED
GMD-1-4:311842,BANK1,BOOT,ALIGNED
Cross-reference the <swIssue> for the line “RAM,APPL” with the
following table.
011587 REL0201P.LE

311836 REL0300P.GD

311842 REL0301P.HF

311986 REL0302P.AE

311982 REL0310P.FP

c. Log out using the following command and close the telnet session:
CANC-USER::<ADMIN Level User>:<CTAG>;
d. Select your next step.
If the software version in substep b is Then
lower than the current release go to step 34
equal to or higher than the current release, contact your next level of
or not in the table support
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-67

Procedure 4-10 (continued)

Replacing the GMD module

Step Action

34 Upgrade the GMD by performing the procedure in SLAT and Channel

Procedures, 323-1661-221. If you perform the upgrade within a TIDc shelf,
make sure that the shelf where the upgrade is occurring is the only one
selected in the Craft Navigation tree. If necessary, expand the TID in the
Navigation tree to see the specific shelf that you must select.
After the upgrade is complete, go to step 42.
35 If the Database Not Recovered (DNR) alarm is raised, but the TDRF alarm is
not, select the database to recover from (Configuration->Backup and
Restore->Restore Local Database tab):
a. Select the subtending module from which to restore the database.
b. Click on the Restore Local button.

36 Click on the Commit button to commit the files that have been restored.
The NE restarts, which results in loss of communication with the Craft
interface.
37 Wait for the GMD to restart.
The GMD restarts automatically, which can take up to 10 minutes.
38 Launch a new web browser and log into the Craft; use the previously
provisioned ADMIN level username and password.
39 Open Configuration->Release Management and determine the software
release running on the GMD:
If the Active software release is Then go to
higher than the Committed release step 40
lower than the Committed release step 41
same as the Committed release step 42

40 Downgrade the GMD by performing the procedure in SLAT and Channel

Procedures, 323-1661-221.

Attention: If you perform the downgrade within a TIDc shelf, make sure that
the shelf where the downgrade is occurring is the only one selected in the
Craft Navigation tree. If necessary, expand the TID in the Navigation tree to
see the specific shelf that you must select.

After the downgrade is complete, go to step 42.

41 Upgrade the GMD by performing the procedure in SLAT and Channel
Procedures, 323-1661-221.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-68 Module and component replacement

Procedure 4-10 (continued)

Replacing the GMD module

Step Action

Attention: If you perform the upgrade within a TIDc shelf, make sure that the
shelf where the upgrade is occurring is the only one selected in the Craft
Navigation tree. If necessary, expand the TID in the Navigation tree to see the
specific shelf that you must select.

After the upgrade is complete, go to step 42.

42 .If the Circuit Pack Mismatch (580) alarm is Then go to
active step 43
not active step 50

Attention: The alarm appears when GMD Type 1 is replaced with GMD Type
2 or GMD Type 2 is replaced with GMD Type 1.

43 Remove the facilities (OPTMON, VOA, OSC) from service against the GMD
(slot 4). See Configuration, 323-1661-310, for information on placing a facility
OOS.
44 Remove the GMD equipment from service. See Configuration,
323-1661-310, for information on placing equipment OOS.
45 Edit the Card Type parameter for the new GMD module. The PEC will
automatically be updated. See Configuration, 323-1661-310, for information
on editing equipment properties.
46 Restore the new GMD equipment to service. See Configuration,
323-1661-310, for information on how to place equipment IS.
47 Restore the facilities (OSC, VOA, OPTMON) to service on the GMD. See
Configuration, 323-1661-310, for information on how to place facilities IS.
48 Return all amplifiers previously placed OOS to IS. See Configuration,
323-1661-310, for information on placing amplifier facilities IS.
49 If the link has DRA modules in one or both directions, place both the local and
the remote RAMAN facilities IS. See Configuration, 323-1661-310, for
information on placing RAMAN facilities IS.
50 Clear any alarms on the system using the appropriate procedure in
Chapter 3, “Alarm clearing” on page 3-1.
51 Put both of the Domain Optical Controllers back in-service. A re-optimization
is recommended. See Configuration, 323-1661-310.
52 Perform a BER test or verify performance monitoring data on the service layer
to ensure traffic is running clean. See SLAT and Channel Procedures,
323-1661-221, for more information.
53 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-69

Procedure 4-11
Replacing the OPM module
Use this procedures to replace the Optical Power Monitor (OPM) module.
CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC, a loss of provisioning data may occur. Do
not remove any subtending modules during a
GMD/DOSC/UOSC replacement.

Attention: You can perform this procedure while DOC is set to Auto
Re-optimize As Necessary. However, DOC will raise the DOC Action Failed:
Monitor (549) or DOC Action Failed: Optimize (550) alarm at the DOC
network element. These alarms occur because DOC detects changes in the
system topology. To ensure correct operation, DOC only attempts
equalization when the system topology is stable and determined to be
accurate. To avoid the alarm generation, set DOC to OOS before the
procedure is started. See Configuration, 323-1661-310, for information on
changing DOC settings. Ensure you return DOC to the original settings after
this procedure is completed.

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Be logged into the Craft interface. See Configuration, 323-1661-310.
• Have the correct replacement module (the replacement product
engineering code (PEC) is the same as the current PEC).
• Have a 10-mm socket.
• Have a torque wrench.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-70 Module and component replacement

Procedure 4-11 (continued)

Replacing the OPM module

Procedure steps
Step Action

Remove the module

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Verify that the replacement product engineering code (PEC) is the same as
the current PEC.
3 Verify the current alarm conditions on the network element. Depending on the
configuration of the node where this procedure is to be performed, the
following alarms can appear throughout the network during this procedure:
• Adjacency Far End Not Discovered (538)
• DOC Invalid Photonic Domain (552)
• Circuit Pack Missing (579)
• Channel Controller: Failure Detected (709)
• Loss Of Signal (553, 560)
• Power Failure - A (594)
• Power Failure - B (595)

4 Select your next step.

If Then go to
the OPM is to be removed (not to step 5 to delete the OPM adjacencies and
be replaced) and is shared delete the OPM facilities and equipment.
across different OSIDs (for Note: For detailed procedures on deleting
example, T-branch) adjacencies, removing from service and
deleting facilities and equipment, see
Configuration, 323-1661-310.
otherwise step 10

5 Delete the OPM adjacencies on the local and the remote shelves that share
the OPM.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-71

Procedure 4-11 (continued)

Replacing the OPM module

Step Action

6 Set all OPM facilities out-of-service (OOS).

7 Delete all OPM facilities.
8 Remove the OPM equipment from service.
9 Delete the OPM equipment.
10 Turn off the power feeds to the OPM at the breaker panel.
11 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Ensure labels are applied to the breaker interface panel or fuse
panel. See Installation, 323-1661-201, for information on labeling cable and
optical fibers.
12
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections to prevent an electric shock.

Ensure the power feeds to the OPM at the breaker panel are off (0) and
disconnect the A and B power connectors on the OPM.
13 Unscrew the two 3/8-in. nuts and lock washers over the ground pins (located
on the left side of the module).
14 Disconnect the Ethernet and RS-232 cables from the OPM.
15
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

Disconnect all optical connectors (Mon) on the OPM.

16 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
17 Pull out and hold the OPM spring plunger and remove the existing OPM from
the frame. If the OPM is not to be replaced, you have completed this
procedure.
Install the module
18 Install the replacement OPM into the frame.
19 Secure the two 3/8-in. nuts and lock washers over the ground pins.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-72 Module and component replacement

Procedure 4-11 (continued)

Replacing the OPM module

Step Action

20
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque two 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

21 Reconnect all Ethernet and RS-232 cables disconnected in step 14 to the
OPM.
22 Clean all fiber connectors disconnected from the Mon ports in step 15 and
reconnect them to the appropriate ports on the OPM. For instructions on
inspecting and cleaning optical fiber, see SLAT and Channel Procedures,
323-1661-221.
23
DANGER
Risk of electric shock
Exercise caution when connecting power connections;
otherwise, you risk an electric shock. Ensure the power
feeds to the OPM at the breaker panel are off.

Ensure the power feeds to the OPM at the breaker panel are off and connect
the A and B power connectors disconnected in step 12 to the OPM.
24 At the breaker panel turn on the power feeds to the OPM.
25 Wait for the OPM to start.
26 Check the active alarms (Faults->Active Alarms).
27 If the Software Auto-Upgrade in Progress (439) alarm is active, wait until the
alarm clears before continuing.

Attention: It can take up to 20 minutes for this alarm to clear.

28 If the Circuit Pack Upgrade Failed (124) alarm is active, clear these alarm
using the procedures in this document.
29 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact your next level of support or your Nortel support
group.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)
30 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-73

Procedure 4-12
Replacing the SCMDx module
Use this procedure to replace the Serial 4 Channel Mux/Demux (SCMD4)
module or Serial 8 Channel Mux/Demux (SCMD8) module.

CAUTION
Service affecting procedure
SCMDx module replacement is service affecting. Ensure you
have exhausted all other troubleshooting options before
performing this procedure and if possible, reroute the traffic to
minimize the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC, a loss of provisioning data may occur. Do
not remove any subtending modules during a
GMD/DOSC/UOSC replacement.

Attention: You can perform this procedure while DOC is set to Auto
Re-optimize As Necessary. However, DOC will raise the DOC Action Failed:
Monitor (549) or DOC Action Failed: Optimize (550) alarm at the DOC
network element. These alarms occur because DOC detects changes in the
system topology. To ensure correct operation, DOC only attempts
equalization when the system topology is stable and determined to be
accurate. To avoid the alarm generation, set DOC to OOS before the
procedure is started. See Configuration, 323-1661-310, for information on
changing DOC settings. Ensure you return DOC to the original settings after
this procedure is completed.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-74 Module and component replacement

Procedure 4-12 (continued)

Replacing the SCMDx module

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have the correct replacement module (the replacement product
engineering code (PEC) is the same as the current PEC).
• Have a 10-mm socket and have a torque wrench.
Procedure steps
Step Action

Remove the module

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2 Verify the current alarm conditions on the network element. Depending on the
configuration of the node where this procedure is to be performed, the
following alarms can appear throughout the network during this procedure:
• Adjacency Far End Not Discovered (538)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Circuit Pack Missing (579)
• Loss Of Signal (553, 560)
• Power Failure - A (594)
• Power Failure - B (595)
• Shutoff Threshold Crossed (540)
3 Verify that the replacement product engineering code (PEC) is the same as
the current PEC.
4 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-75

Procedure 4-12 (continued)

Replacing the SCMDx module

Step Action

5
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Turn off the power feeds to the SCMDx at the breaker panel.
6 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Ensure labels are applied to the breaker interface panel or fuse
panel. See Installation, 323-1661-201, for information on labeling cable and
optical fibers.
7
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections; otherwise, you risk an electric shock.
Ensure the power feeds to the SCMDx at the breaker
panel are off (0).

Ensure the power feeds to the SCMDx at the breaker panel are off (0) and
disconnect the A and B power connectors on the SCMDx.
8 Unscrew the two 3/8-in nuts and lock washers over the ground pins (located
on the left side of the module).
9 Disconnect the Ethernet and RS-232 cables from the SCMDx.
10
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical
amplifier is out of service (OOS).

Disconnect all optical connectors (Ch #, Updg and Common) on the SCMDx.
11 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-76 Module and component replacement

Procedure 4-12 (continued)

Replacing the SCMDx module

Step Action

12 Pull out and hold the SCMDx spring plunger and remove the existing SCMDx
from the frame.
Install the module
13 Install the replacement SCMDx into the frame.
14 Secure the two 3/8-in. nuts and lock washers over the ground pins
15 .
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque the 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

16 Reconnect all Ethernet cables, disconnected in step 9, to the SCMDx.
17 Clean all fiber connectors disconnected from the channel, upgrade and
common ports in step 10 and reconnect them to the appropriate ports on the
SCMDx. For instructions on inspecting and cleaning optical fiber, see SLAT
and Channel Procedures, 323-1661-221.
18
DANGER
Risk of electric shock
Exercise caution when connecting power connections;
otherwise, you risk an electric shock. Ensure the power
feeds to the SCMDx at the breaker panel are off (0).

Ensure the power feeds to the SCMDx at the breaker panel are off (0) and
connect the A and B power connectors disconnected in step 7 to the SCMDx.
19 At the breaker panel, turn on the power feeds to the SCMDx.
20 Wait for the SCMDx to start.
21 Check the active alarms (Faults->Active Alarms).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-77

Procedure 4-12 (continued)

Replacing the SCMDx module

Step Action

22 If the Software Auto-Upgrade in Progress (439) is active, wait until this alarm
clears before continuing.

Attention: It can take up to 20 minutes for this alarm to clear.

23 If the Circuit Pack Upgrade Failed (124) is active, clear this alarm using the
procedure in this document.
24 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact your next level of support or your Nortel support
group.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)
25 Undo any traffic switches performed in step 4.
26 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-78 Module and component replacement

Procedure 4-13
Replacing the UOSC module
Use this procedure to replace the Uni Optical Service Channel (UOSC)
module.

Attention: If both a UOSC and a subtending module must be replaced,

contact Nortel technical support.

This procedure covers the following scenarios:

• the active release on the replacement UOSC is the same as the
committed release on the network element and the upgrade state is
inactive
• the active release on the replacement UOSC is the same as the
committed release on the network element and the upgrade state is not
inactive
• the active release on the replacement UOSC is higher than the committed
release on the network element and the upgrade state is inactive and you
have more than one subtending module
• the active release on the replacement UOSC is higher than the committed
release on the network element and the upgrade state is inactive and you
have only one subtending module
• the active release on the replacement UOSC is lower than the committed
release on the network element

Attention: This procedure is simplified and traffic is restored faster if the

replacement UOSC module has the same software release as the rest of the
network element. If you can, Nortel recommends that you
upgrade/downgrade the UOSC module to the same software release as the
rest of the network element before performing this procedure. See SLAT and
Channel Procedures, 323-1661-221, for upgrade/downgrade procedures. If
you do not upgrade before performing this procedure, you will be prompted
to upgrade during this procedure. See the chapter on release and upgrade
management in Configuration, 323-1661-310.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-79

Procedure 4-13 (continued)

Replacing the UOSC module

Prerequisites
• Ensure that you have the correct replacement module. You must replace
a UOSC with another UOSC, and not with a DOSC or a GMD.
• Have a PC available.
• You may require access to a CD with a previous CPL release. You
determine which release when you power up the replacement UOSC.
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Make sure you wear an antistatic wrist strap to protect the equipment from
static damage. Connect the wrist strap to the ESD jack on the shelf or the
module. Use an Ethernet cross-over cable to connect your PC to the Craft
port.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have a 10-mm socket.
• Have a torque wrench.

Procedure steps
Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage.

Connect the wrist strap to the ESD jack on the shelf or module.
2 Set all Domain Optical Controllers (DOC) within this domain out of service
(OOS). See Configuration, 323-1661-310.

Attention: Other DOC domains will not be able to optimize or add/delete

channels when DOC is put OOS in this domain.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-80 Module and component replacement

Procedure 4-13 (continued)

Replacing the UOSC module

Step Action

3
CAUTION
Risk of laser radiation exposure
During this procedure the fiber plant does not have to
be disrupted and the system remains a Class
1(IEC)/Class I (FDA) product.

If the fiber upstream of the DRA Line A input connector

becomes disconnected accidentally while the Raman
Auto Shutoff Disabled feature is active, the radiation at
the exposed fiber can be at hazard level 3B (IEC
60825-2). In this situation, you must take all safety
precautions appropriate to hazard level 3B (IEC
60825-2).

The ORL based APR safety mechanism remains

active.

If the link has DRA modules in one or both directions and the traffic is
unprotected, ensure that the RAMAN facilities in both directions are in Auto
Shutoff Disabled mode. Place both the local and the remote RAMAN facilities
on each span into Auto Shutoff Disabled mode. See Configuration,
323-1661-310, for information about disabling Auto-Shutoff on a RAMAN
facility.

Attention: The RAMAN facility will come out of Auto Shutoff Disabled mode
if there is a restart on the DRA module, or if the RAMAN facility primary state
changes. If communication with the UOSC requiring replacement is not
available and the link has DRA modules, traffic may be lost for the duration of
this procedure.

4 If communication with the UOSC requiring replacement is Then go to

possible step 5
not possible step 8
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-81

Procedure 4-13 (continued)

Replacing the UOSC module

Step Action

5 In the Craft interface, check the active alarms (Faults->Active Alarms).

Depending on the configuration of the node where you perform this
procedure, the following alarms can appear throughout the network during
this procedure.

Attention: No alarm clearing is required at this point.

• Adjacency Far End Not Discovered (538)

• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Automatic Shutoff Disabled (943, 1035)
• Circuit Pack Missing (579)
• DOC Invalid Photonic Domain (552)
• ILAN 1 Port Failure (547)
• ILAN 2 Port Failure (548)
• Loss Of Signal (553, 560)
• OSC Link Failed (555)
• OSC Loss Of Signal (556)
• Power Failure - A (594)
• Power Failure - B (595)

6 In the Craft interface:

a. Perform a remote database save (you can save to a local PC). See the
procedures in the chapter on provisioning data backup and restore, in
Configuration, 323-1661-310.
b. Query the software release currently running on the UOSC module. See
the chapter on release and upgrade management, in Configuration,
323-1661-310.
c. Query the upgrade state. The upgrade state must be inactive. If it is
another state, wait for the upgrade to complete before continuing with this
procedure. See the chapter on release and upgrade management in
Configuration, 323-1661-310.
7 Log out of the Craft. See the Site Manager chapter in Configuration,
323-1661-310.
8 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Apply labels before you disconnect the cables. Ensure labels are
applied to the breaker interface panel or fuse panel. See Installation,
Part 2 of 2, 323-1661-201, for information on labeling cable and optical fibers.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-82 Module and component replacement

Procedure 4-13 (continued)

Replacing the UOSC module

Step Action

9
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections to prevent electric shock.

Ensure the power feeds to the UOSC at the breaker panel are off (0) and
disconnect the A and B power connectors on the UOSC.
Removing the replacement module
10 Unscrew the two 3/8-in. nuts and lock washers over the ground pins (located
on the left side of the module).
11
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical
amplifier is out of service (OOS).

Disconnect all electrical cables (Ethernet, Alarm/Telemetry, Modem) and all

optical patch cords from the UOSC. Put protective caps on the ends of the
patch cords to protect them from contamination and damage.
12 Pull out and hold the UOSC spring plunger and remove the existing UOSC
from the frame.
Installing the replacement module
13 Install the replacement UOSC into its slot in the frame.
14 Secure the two 3/8-inch nuts and lock washers over the ground pins.
15
CAUTION
Risk of damage to equipment
Use a torque wrench to prevent damage to the
equipment.

Secure the two 3/8-inch nuts to a value of 60 in.lbf (6.8 Nm).

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-83

Procedure 4-13 (continued)

Replacing the UOSC module

Step Action

16 Reconnect to the subtending modules the Ethernet cables you disconnected

in step 11.
17
DANGER
Risk of electric shock
Exercise caution when connecting power connections
to prevent electric shock.

Ensure the power feeds to the UOSC at the breaker panel are off and connect
to the UOSC the A and B power connectors disconnected in step 9.
18 Reconnect the rest of the electrical cables (Alarm/Telemetry, Modem) and
optical patch cords disconnected in step 11. Make sure that you clean all fiber
connectors before reconnecting. For instructions on cleaning optical fibers,
see SLAT and Channel Upgrade Procedures, 323-1661-221.

Attention: Ensure that all the cables to the subtending modules are
reconnected, otherwise there is a risk that the modules will lose their
provisioning information.

19
DANGER
Risk of electric shock
Exercise caution when connecting power connections
to prevent electric shock.

Turn on the power feeds to the UOSC at the breaker panel. Wait 10 minutes
for the UOSC to start.
20 Determine the number of subtending modules:
If there is Then go to
only one subtending module step 21
more than one subtending module step 27

21 Launch a new web browser and log into the Craft with the default ADMIN level
username and password.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-84 Module and component replacement

Procedure 4-13 (continued)

Replacing the UOSC module

Step Action

22 Select your next step.

If Then go to
the Craft opens in the Restore Local Database tab of step 23
the Backup and Restore application
otherwise step 28

23 Because only two modules are available (the UOSC and one subtending
module) the system is not able to automatically recover a database. The Craft
interface opens in the Restore Local Database tab of the Backup and Restore
application and lists the slots with valid databases. Select the subtending
module slot from the list and click the Restore Local button.
When the restore is complete, the Commit button will be active.
24 Click the Commit button.
A dialog window opens asking to confirm the Commit.
25 Click the Yes button.
The NE restarts, which results in loss of communication with the Craft
interface.
26 Wait 10 minutes for the UOSC to restart.
27 Launch a new web browser and log into the Craft; you may have to use the
default or provisioned ADMIN level password.
28 In the Craft, check the active alarms (Faults->Active Alarms). Shortly after the
fiber connections are completed and the UOSC restarts, OSC related alarms
at this site and at the adjacent sites clear.

Attention: If there is more than one subtending module, the Database Not
Recovered alarm should not be active.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-85

Procedure 4-13 (continued)

Replacing the UOSC module

Step Action

29 Select your next step.

If the following alarms are raised Then go to
Transport Data Recovery Failed (TDRF) or Flash Bank step 30
Mismatch and Shelf Data Missing

Database Not Recovered (DNR), but no TDRF alarm step 32

Any of: step 36

Incomplete Software Lineup
Software Configuration Unknown
Software Mismatch
Circuit Pack Upgrade Failed
Software Upgrade Failed, but no TDRF or DNR alarm

Software Upgrade in Progress contact your next

level of support

otherwise step 39

30 If the Transport Data Recovery Failed or Flash Bank Mismatch and Shelf
Data Missing alarms are raised:
a. Open a telnet session on the CPL NE and log into the TL1 interface using
the following command. The default ADMIN level username and
password are required to log into the TL1 session.
ACT-USER::<ADMIN Level User>:<CTAG>::<ADMIN Level
password>:;
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-86 Module and component replacement

Procedure 4-13 (continued)

Replacing the UOSC module

Step Action

b. Determine the application load running on the UOSC using the following
command:
RTRV-SW-VER::SLOT-1-4:<CTAG>;
The output will be in the following format:
<AID>:<swIssue>
The first line of the output indicates the committed software release for
the NE. The remaining lines indicate the software release running on the
UOSC.
For example:
SHELF-1:REL0321P.JD
UOSC-1-4:311842,RAM,APPL,ALIGNED
UOSC-1-4:311842,RAM,BOOT,ALIGNED
UOSC-1-4:311842,BANK0,APPL,ALIGNED
UOSC-1-4:311842,BANK0,BOOT,ALIGNED
UOSC-1-4:311842,BANK1,APPL,ALIGNED
UOSC-1-4:311842,BANK1,BOOT,ALIGNED
Cross-reference the <swIssue> for the line “RAM,APPL” with the
following table.
011587 REL0201P.LE

311836 REL0300P.GD

311842 REL0301P.HF

311986 REL0302P.AE

311982 REL0310P.FP

c. Log out using the following command and close the telnet session:
CANC-USER::<ADMIN Level User>:<CTAG>;
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-87

Procedure 4-13 (continued)

Replacing the UOSC module

Step Action

d. Select your next step.

If the software version in substep b is Then
lower than the current release go to step 31
equal to or higher than the current release, contact your next level of
or not in the table support

31 Upgrade the UOSC by performing the procedure in SLAT and Channel

Procedures, 323-1661-221.

Attention: If you perform the upgrade within a TIDc shelf, make sure that the
shelf where the upgrade is occurring is the only one selected in the Craft
Navigation tree. If necessary, expand the TID in the Navigation tree to see the
specific shelf that you must select.

After the upgrade is complete, go to step 39.

32 If the Database Not Recovered (DNR) alarm is raised, but the TDRF alarm is
not, select the database to recover from (Configuration->Backup and
Restore->Restore Local Database tab):
a. Select the subtending module from which to restore the database.
b. Click on the Restore Local button.

33 Click on the Commit button to commit the files that have been restored.
The NE restarts, which results in loss of communication with the Craft
interface.
34 Wait for the UOSC to restart.
The UOSC restarts automatically and it can take up to 10 minutes.
35 Launch a new web browser and log into the Craft; use the previously
provisioned ADMIN level username and password.
36 Open Configuration->Release Management and determine the software
release running on the UOSC:
If the Active software release is Then go to
higher than the Committed release step 37
lower than the Committed release step 38
same as the Committed release step 39

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-88 Module and component replacement

Procedure 4-13 (continued)

Replacing the UOSC module

Step Action

37 Downgrade the UOSC by performing the procedure in SLAT and Channel

Procedures, 323-1661-221.

Attention: If you perform the downgrade within a TIDc shelf, make sure that
the shelf where the downgrade is occurring is the only one selected in the
Craft Navigation tree. If necessary, expand the TID in the Navigation tree to
see the specific shelf that you must select.

After the downgrade is complete, go to step 39.

38 Upgrade the UOSC by performing the procedure in SLAT and Channel
Procedures, 323-1661-221.

Attention: If you perform the upgrade within a TIDc shelf, make sure that the
shelf where the upgrade is occurring is the only one selected in the Craft
Navigation tree. If necessary, expand the TID in the Navigation tree to see the
specific shelf that you must select.

After the upgrade is complete, go to step 39.

39 Clear any alarms on the system using the appropriate procedure in
Chapter 3, “Alarm clearing” on page 3-1.
40 If the link has DRA modules in one or both directions, clear the Auto Shutoff
Disabled mode set in step 3 on both the local and the remote RAMAN
facilities on each span. See Configuration, 323-1661-310, for information on
enabling Auto-Shutoff on a RAMAN facility.

41 Put both of the Domain Optical Controllers back in-service. A re-optimization

is recommended. See Configuration, 323-1661-310.
42 Perform a BER test or verify performance monitoring data on the service layer
to ensure traffic is running clean. See SLAT and Channel Procedures,
323-1661-221, for more information.
43 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-89

Procedure 4-14
Replacing the WSS module
Use this procedures to replace the Wavelength Selective Switch (WSS)
module.

CAUTION
Service affecting procedure
WSS module replacement is service affecting. Ensure you
have exhausted all other troubleshooting options before
performing this procedure and if possible, re-route the traffic to
minimize the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC a loss of provisioning data may occur. Do
not remove any subtending modules during a
GMD/DOSC/UOSC replacement.

Attention: You can perform this procedure while DOC is set to Auto
Re-optimize As Necessary. However, DOC will raise the DOC Action Failed:
Monitor (549) or DOC Action Failed: Optimize (550) alarm at the DOC
network element. These alarms occur because DOC detects changes in the
system topology. To ensure correct operation, DOC only attempts
equalization when the system topology is stable and determined to be
accurate. To avoid the alarm generation, set DOC to OOS before the
procedure is started. See Configuration, 323-1661-310, for information on
changing DOC settings. Ensure you return DOC to the original settings after
this procedure is completed.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-90 Module and component replacement

Procedure 4-14 (continued)

Replacing the WSS module

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have the correct replacement module (the replacement product
engineering code (PEC) is the same as the current PEC).
• Have a 10-mm socket.
• Have a torque wrench.

Procedure steps
Step Action

Remove the module

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2 Verify the current alarm conditions on the network element. Depending on the
configuration of the node where this procedure is to be performed the
following alarms can appear throughout the network during this procedure:
• Adjacency Far End Not Discovered (538)
• Automatic Power Reduction Active (542)
• Automatic Shutoff (590, 942)
• Circuit Pack Missing (579)
• Channel Controller: Failure Detected (709)
• Loss Of Signal (553, 560)
• Power Failure - A (594)
• Power Failure - B (595)
• Shutoff Threshold Crossed (540)

3 Verify that the replacement product engineering code (PEC) is the same as
the current PEC.
4 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-91

Procedure 4-14 (continued)

Replacing the WSS module

Step Action

5
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical
amplifier is out of service (OOS).

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Remove the amplifier facilities (SLA, MLA, MLA2) connected to the module
being replaced from service. See Configuration, 323-1661-310, for
information on removing optical facilities from service.
6 Turn off the power feeds to the WSS at the breaker panel.
7 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Ensure labels are applied to the breaker interface panel or fuse
panel. See Installation, 323-1661-201, for information on labeling cable and
optical fibers.
8
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections to prevent an electric shock.

Ensure the power feeds to the WSS at the breaker panel are off (0) and
disconnect the A and B power connectors on the WSS.
9 Unscrew the two 3/8-in. nuts and lock washers over the ground pins (located
on the left side of the module).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-92 Module and component replacement

Procedure 4-14 (continued)

Replacing the WSS module

Step Action

10 Disconnect the Ethernet and RS-232 cables from the WSS.

11 Disconnect all optical connectors (Switch and Common) on the WSS.
12 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
13 Pull out and hold the WSS spring plunger and remove the existing WSS from
the frame.
Install the module
14 Install the replacement WSS into the frame.
15 Secure the two 3/8-in. nuts and lock washers over the ground pins.
16
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque two 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

17 Reconnect all Ethernet and RS-232 cables disconnected in step 10 to the
WSS.
18 Clean all fiber connectors disconnected from the Switch and Common ports
in step 11 and reconnect them to the appropriate ports on the WSS. For
instructions on inspecting and cleaning optical fiber, see SLAT and Channel
Procedures, 323-1661-221.
19
DANGER
Risk of electric shock
Exercise caution when connecting power connections
to prevent an electric shock.

Ensure the power feeds to the WSS at the breaker panel are off and connect
the A and B power connectors disconnected in step 8 to the amplifier.
20 At the breaker panel turn on the power feeds to the WSS.
21 Wait for the WSS to start.
22 Restore the amplifier facilities connected to the new WSS back in-service
(IS). See Configuration, 323-1661-310, for information on restoring facilities
to service.
23 Check the active alarms (Faults->Active Alarms).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-93

Procedure 4-14 (continued)

Replacing the WSS module

Step Action

24 If the Software Auto-Upgrade in Progress (439) alarm is active, wait until the
alarm clears before continuing.

Attention: It can take up to 15 minutes for this alarm to clear.

25 If the Circuit Pack Upgrade Failed (124) is active, clear this alarm using the
procedure in this document.
26 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact Nortel.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)

27 Undo any traffic switches performed in step 4.

28 Update the user label with the current shelf and slot number (see
Configuration, 323-1661-310).
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-94 Module and component replacement

Procedure 4-15
Replacing a DSCM contained within a Fiber Manager
Use this procedure to replace a Dispersion Slope Compensating Module
(DSCM) contained within a Fiber Manager.

CAUTION
Service affecting procedure
DSCM replacement is service affecting. Ensure you have
exhausted all other troubleshooting options before performing
this procedure and if possible, reroute the traffic to minimize
the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC a loss of provisioning data may occur. Do
not remove any subtending modules during a
GMD/DOSC/UOSC replacement.

Attention: You can perform this procedure while DOC is set to Auto
Re-optimize As Necessary. However, DOC will raise the DOC Action Failed:
Monitor (549) or DOC Action Failed: Optimize (550) alarm at the DOC
network element. These alarms occur because DOC detects changes in the
system topology. To ensure correct operation, DOC only attempts
equalization when the system topology is stable and determined to be
accurate. To avoid the alarm generation, set DOC to OOS before the
procedure is started. See Configuration, 323-1661-310, for information on
changing DOC settings. Ensure you return DOC to the original settings after
this procedure is completed.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-95

Procedure 4-15 (continued)

Replacing a DSCM contained within a Fiber Manager

Step Action

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have a nut driver, 5/16 in.
• Have the correct replacement module. You must have a replacement
module of the same PEC as the defective module being replaced.

Attention: For the product engineering codes for the DSCMs, see Planning
Guide, NTT840FE.

Procedure steps
Step Action

1 Retrieve and note all active alarms (enabled and disabled) on the system, see
Procedure 2-1, Displaying active alarms and Procedure 2-2, Displaying
active disabled alarms.
2 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment).
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-96 Module and component replacement

Procedure 4-15 (continued)

Replacing a DSCM contained within a Fiber Manager

Step Action

3
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

CAUTION
Risk of damage to modules
Never disconnect an optical fiber that is connected to
an active or powered up optical amplifier. To disconnect
or reconnect an optical fiber, make sure the optical
amplifier is out of service (OOS).

CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Remove the amplifier facilities (SLA, MLA, MLA2) connected to the DSCM
being replaced from service. See Configuration, 323-1661-310, for
information on removing optical facilities from service.
4 Press and hold the locking tabs on the sides of the Fiber Manager, and pull
the drawer toward you until it is fully extended.
5 Locate the locking clip, if available, at the back left corner of the Fiber
Manager. Lock the Fiber Manager open by rotating the locking clip
counter-clockwise until it rests on the edge of the drawer.
6 Ensure that labels are applied to both ends of all optical fiber patch cords. See
Installation, 323-1661-201, for information on labeling cable and optical
fibers.
7 Disconnect all the fibers connected to the IN and OUT ports of the DSCM that
you are replacing.
8 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
9 Remove the four nuts that fasten the DSCM to the drop-in-plate assembly.

Attention: The nuts are located at the front and back of the drop-in-plate
assembly. Make sure you keep the nuts to install the replacement module.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-97

Procedure 4-15 (continued)

Replacing a DSCM contained within a Fiber Manager

Step Action

10 Use the handle on the DSCM to lift and remove it from the Fiber Manager, see
Figure 4-1.
11 Remove the replacement DSCM from its packaging, and ensure that its PEC
matches with the PEC of the DSCM that was removed in the previous step. If
it does not match, ensure that the correct DSCM is about to be installed.
12 Use the DSCM handle to position the DSCM.
13 Fasten the DSCM to the drop-in-plate assembly using the four nuts that you
removed in step 9.
14 Re-route the fiber patch cords to the DSCM.
15 Clean all fiber connectors disconnected from the IN and OUT ports in step 7
and reconnect them to the appropriate ports on the DSCM. For instructions
on inspecting and cleaning optical fiber, see SLAT and Channel Procedures,
323-1661-221.
16 Locate the locking clip, if available, at the back left corner of the Fiber
Manager.
17 Unlock the Fiber Manager by rotating the locking clip clockwise to the original
upright position.
18 Close the Fiber Manager by pressing and holding the locking tabs on the
sides of the tray while you slide the drawer into the rack.

Attention: Be careful not to pinch any fibers, and to allow proper fiber slack.

19 Restore the amplifier facilities connected to the new DSCM back in-service
(IS). See Configuration, 323-1661-310, for information on restoring facilities
to service.
20 Make sure the only active alarms on the system match those noted in step 1.
If there are additional alarms, contact your next level of support or Nortel.
21 Undo any traffic switches performed in step 2.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-98 Module and component replacement

Figure 4-1
DSCM
CPL0167t.jpg

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-99

Procedure 4-16
Replacing the DRA module with the equivalent DRA
Use this procedure to replace the Distributed Raman Amplifier (DRA) module
with another DRA with the same PEC.

CAUTION
Service affecting procedure
DRA module replacement is service affecting. Ensure you
have exhausted all other troubleshooting options before
performing this procedure and if possible, reroute the traffic to
minimize the traffic loss.

CAUTION
Loss of provisioning data
If both a GMD/DOSC/UOSC and a subtending module must be
replaced, first replace the GMD/DOSC/UOSC and then
replace the subtending module.

If a subtending module is replaced at the same time as a

GMD/UOSC/DOSC, a loss of provisioning data can occur. Do
not remove any subtending modules during a
GMD/DOSC/UOSC replacement.

Attention: You can perform this procedure while DOC is set to Auto
Re-optimize As Necessary. However, DOC will raise the DOC Action Failed:
Monitor (549) or DOC Action Failed: Optimize (550) alarm at the DOC
network element. These alarms occur because DOC detects changes in the
system topology. To ensure correct operation, DOC only attempts
equalization when the system topology is stable and determined to be
accurate. To avoid the alarm generation, set DOC to OOS before the
procedure is started. See Configuration, 323-1661-310, for information on
changing DOC settings. Ensure you return DOC to the original settings after
this procedure is completed.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-100 Module and component replacement

Procedure 4-16 (continued)

Replacing the DRA module with the equivalent DRA

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Log into the Craft interface. See Configuration, 323-1661-310.
• Have the correct replacement module (the replacement product
engineering code [PEC] is the same as the current PEC).
• Have a 10-mm socket.
• Have a torque wrench.

Procedure steps

Step Action

Remove the module

1 Check the date and time of the last backup and check to see if a data backup
is required. See Configuration, 323-1661-310, for details on how to view the
current backup state and how to save provisioning data.
2 Set all Domain Optical Controllers (DOC) within this domain OOS. See
Configuration, 323-1661-310.

Attention: Other DOC domains will not be able to optimize or add/delete

channels when DOC is put OOS in this domain.

3 Ensure that the RAMAN facilities at both ends of the optical span are not in
the Shutoff Disabled state.
4 Check the active alarms on the network element (Faults->Active Alarms).
Depending on the configuration of the node where this procedure is to be
performed, the following alarms can appear throughout the network during
this procedure:
• Adjacency Far End Not Discovered (538)
• Circuit Pack Missing (579)
• Loss Of Signal (553, 560)
• Power Failure - A (594)
• Power Failure - B (595)

5 Verify that the replacement product engineering code (PEC) is the same as
the current PEC.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-101

Procedure 4-16 (continued)

Replacing the DRA module with the equivalent DRA

Step Action

6 Switch traffic away from this optical link by performing a protection switch at
the service layer (non-Common Photonic Layer equipment) to prevent traffic
loss.
7 Remove the RAMAN facilities from service. See Configuration,
323-1661-310, for information on removing optical facilities from service.
8
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Turn off the power feeds to the DRA at the breaker panel.
9 Ensure that labels are applied to both ends of all cables and optical fiber
patch cords. Ensure labels are applied to the breaker interface panel or fuse
panel. See Installation, 323-1661-201, for information on labeling cable and
optical fibers.
10
DANGER
Risk of electric shock
Exercise caution when disconnecting power
connections; otherwise, you risk an electric shock.
Ensure the power feeds to the DRA at the breaker
panel are off (0).

Ensure the power feeds to the DRA at the breaker panel are off (0) and
disconnect the A and B power connectors on the DRA.
11 Unscrew the two 3/8-in nuts and lock washers over the ground pins (located
on the left side of the module).
12 Disconnect the Ethernet and RS-232 cables from the DRA
13 .
DANGER
Risk of laser radiation exposure
Do not look directly into the optical beam. Invisible light
can severely damage your eyes.

Disconnect all optical connectors on the DRA.

14 Put protective caps on the ends of the patch cords to protect them from
contamination and damage.
15 Pull out and hold the DRA spring plunger and remove the existing DRA from
the frame.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-102 Module and component replacement

Procedure 4-16 (continued)

Replacing the DRA module with the equivalent DRA

Step Action

Install the module

16 Install the replacement DRA into the frame.
17 Secure the two 3/8-in. nuts and lock washers over the ground pins
18 .
CAUTION
Risk of damage to equipment
Use a torque wrench. Otherwise, you risk damaging
the equipment.

Torque the 3/8-in. nuts to a value of 60 in.lbf (6.8 N·m).

19 Reconnect all Ethernet cables, disconnected in step 12, to the DRA.
20 Clean all fiber connectors disconnected from the Channel and common ports
in step 13 and reconnect them to the appropriate ports on the DRA. For
instructions on inspecting and cleaning optical fiber, see SLAT and Channel
Procedures, 323-1661-221.
21
DANGER
Risk of electric shock
Exercise caution when connecting power connections;
otherwise, you risk an electric shock. Ensure the power
feeds to the DRA at the breaker panel are off (0).

Ensure the power feeds to the DRA at the breaker panel are off (0) and
connect the A and B power connectors disconnected in step 10 to the DRA.
22 At the breaker panel, turn on the power feeds to the DRA.
23 Wait for the DRA to start. Check that the active LED is green.
24 Restore the RAMAN facilities back in-service (IS). See Configuration,
323-1661-310, for information on restoring facilities to service.
25 Check the active alarms (Faults->Active Alarms).
26 If the Software Auto-Upgrade in Progress (439) is active, wait until the alarm
clears before continuing.

Attention: It can take up to 20 minutes for this alarm to clear.

27 If the Circuit Pack Upgrade Failed (124) is active, clear this alarm using the
procedure in this document.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-103

Procedure 4-16 (continued)

Replacing the DRA module with the equivalent DRA

Step Action

28 If RAMAN facility alarms are active, clear them using the procedures in this
document:
• Automatic Shutoff Disabled (943, 1035)
• Raman Failed To Turn On (944)

29 If any of the following alarms are active, a problem provisioning the module
has been detected. Contact your next level of support or your Nortel support
group.
• Autoprovisioning Mismatch (60)
• Database Integrity Fail (8)

30 Undo any traffic switches performed in step 6.

31 Put both of the Domain Optical Controllers back in-service, a re-optimization
is recommended. See Configuration, 323-1661-310.
32 Update the user label with the current shelf and slot number. See
Configuration, 323-1661-310.
33 If the DRA replacement occurred on a Stretched Span, perform
Procedure 6-2, “Recovering from a fiber cut on a Stretched Span with Raman
amplification” on page 6-5 to get the link back up after the replacement.
Otherwise, you have completed this procedure.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-104 Module and component replacement

Procedure 4-17
DOC settings when replacing equipment subtending
to the Common Photonic Layer network element
Use this procedure to set DOC values when replacing equipment subtending
to the Common Photonic Layer network element.

Prerequisites
• Observe all safety requirements in Documentation Roadmap,
323-1661-090.
• Have access to the product documentation listed in this procedure.
• Log into the Craft interface. See Configuration, 323-1661-310.

Procedure steps

Step Action

Before subtending equipment is removed

1 Ensure that no channel adds or channel deletes are in progress. See
Configuration, 323-1661-310.
2 Ensure that the following DOC values are set before the subtending
equipment is removed from the Common Photonic Layer network element:
• Auto Add Channels is set to Disabled
• Auto Delete Channels is set to Disabled
• Automation Mode is set to No Auto Monitoring
• Auto Delete on Channel LOS is Disabled.

See Configuration, 323-1661-310, for instructions on setting DOC values.

Replace the subtending equipment
3 Replace the subtending equipment following the procedures in the third-party
product documentation.
After the subtending equipment is replaced
4 Ensure that the DOC values set in step 2 are returned to their original values.
See Configuration, 323-1661-310, for instructions on setting DOC values.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-105

Procedure 4-18
Replacing the fan assembly in an amplifier
Use this procedure to replace the 4-unit fan assembly in an amplifier.

For information on fan assemblies and product engineering codes (PEC), see
Planning Guide, NTT840FE.

Attention: The entire fan assembly must be replaced even if only one fan
within the assembly fails.

Prerequisites
CAUTION
Risk of service interruption
In the SLA, and MLA modules, fan assemblies are used in
thermal management. Replace the fan assembly within three
minutes after its removal, to avoid temperature related issues.

• Observe all safety requirements in Documentation Roadmap,

323-1661-090.
• Have the correct replacement 4-unit fan assembly. You must have a
replacement fan assembly of the same PEC as the defective fan assembly
being replaced.
• Have a slotted screwdriver.

Procedure steps

Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

2 Using a slotted screwdriver, open the module front cover by turning the
screws counterclockwise.
3 Remove the new fan assembly from its packaging.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-106 Module and component replacement

Procedure 4-18 (continued)

Replacing the fan assembly in an amplifier

Step Action

4 Loosen the screw on the front of the fan assembly. See Figure 4-2.
5 Pull the fan assembly toward you to remove it from the module.
See Figure 4-2 and Figure 4-3.

Attention: The Fan Failed and the Fan Missing alarm are raised, these
alarms clear when the new fan assembly is installed. Also, the Fan Fail LED
is lit (red).

6 Slide the new fan assembly into the module.

7 Tighten the screw on the front of the fan assembly to secure it to the module.
8 Close the module front cover.
—end—
Figure 4-2
Loosen the screw and start removing the fan assembly
CPL0105t.jpg

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-107

Figure 4-3
Slide the fan assembly out
CPL0106t.jpg

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-108 Module and component replacement

Procedure 4-19
Replacing the fan assembly in a UOSC, GMD, or DOSC
Use this procedure to replace the fan assembly in the Uni Optical Service
Channel (UOSC), Group Mux/Demux (GMD) module, and the Dual Optical
Service Channel (DOSC) module.

For information on replacement units and product engineering codes (PEC),

see Planning Guide, NTT840FE.

Attention: The entire fan assembly must be replaced even if only one fan
within the assembly fails.

Prerequisites
CAUTION
Risk of service interruption
In the GMD and DOSC modules, fan assemblies are used in
thermal management. Replace the fan assembly within three
minutes after its removal, to avoid temperature related issues.

• Observe all safety requirements in Documentation Roadmap,

323-1661-090.
• Have the correct replacement 5-unit fan assembly. You must have a
replacement fan assembly of the same PEC as the defective fan assembly
being replaced.
• Have a slotted screwdriver.

Procedure steps

Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

2 Using a slotted screwdriver, open the module front cover by turning the
screws counterclockwise.
3 Remove the new fan assembly from its packaging.
4 Loosen the screw on the front of the fan assembly. See Figure 4-4.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-109

Procedure 4-19 (continued)

Replacing the fan assembly in a UOSC, GMD, or DOSC

Step Action

5 Pull the fan assembly toward you to remove it from the module.
See Figure 4-5.

Attention: The Fan Failed and the Fan Missing alarm are raised. These
alarms clear when the new fan assembly is installed. Also, the Fan Fail LED
is lit, red.

6 Slide the new fan assembly into the module.

7 Tighten the screw on the front of the fan assembly to secure it to the module.
8 Close the module front cover.
—end—
Figure 4-4
Loosen the screw
CPL0107t.jpg

Figure 4-5
Slide the fan assembly out
CPL0108t.jpg

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-110 Module and component replacement

Procedure 4-20
Replacing air filters
Use this procedure to replace a 2U height air filter (NTT899HA), or a reduced
height air filter (NTT899HC) in the Uni Optical Service Channel (UOSC),
Group Mux/Demux (GMD) module and the Dual Optical Service Channel
(DOSC) module.

For information on replacement units and product engineering codes (PEC),

see Planning Guide, NTT840FE.

Prerequisites
CAUTION
Risk of service interruption
Field-replaceable air filters are used to eliminate dust and
other contaminants and prevent them from affecting the
electronic and optical components of modules. Replace the air
filter for each applicable UOSC, GMD, and DOSC every
9 months for North American systems and every 12 months for
ETSI systems.

• Observe all safety requirements in Documentation Roadmap,

323-1661-090.
• Have a replacement air filter. Ensure that you have the correct
replacement filter type. There are two filter types:
— The NTT899HA is a 2U height air filter (Figure 4-6).
— The NTT899HC is a reduced height air filter (Figure 4-7).
• Have a slotted screwdriver.

Procedure steps
Step Action

1 Identify if the GMD, DOSC, or UOSC requires a 2U height air filter

(NTT899HA) or reduced height air filter (NTT899HC). Ensure that you have
the correct filter.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Module and component replacement 4-111

Procedure 4-20 (continued)

Removing the air filter (example shows a NTT899HA-2U height air filter)

Step Action

2
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

Using a slotted screwdriver, open the module front cover by turning the
screws counterclockwise.
3 Move the Ethernet and power cables out of the path of the filter if they are in
the way. See Figure 4-6.
4 Grasp the tab on the front of the air filter to the left side of the UOSC, GMD,
or DOSC module and pull the filter toward you until it is free. See Figure 4-6.
5 Discard the old air filter.
6 Move the Ethernet and power cables out of the path of the filter if they are in
the way.
7 With the tab in front of you and at the top, slide the replacement filter into the
guides to the left of the UOSC, GMD, or DOSC module. See Figure 4-6.
8 Adjust the cables (only necessary for the 2U height air filter).
9 Close the module cover.
—end—
Figure 4-6
Removing the air filter (example shows a NTT899HA-2U height air filter)
CPL0109t.jpg

Figure 4-7
Inserting the air filter (example shows a NTT899HC- reduced height air filter)
CPL0385t.jpg

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
4-112 Module and component replacement

Procedure 4-21
Replacing a patch panel for attenuator fix pads
Use this procedure to replace a patch panel for attenuator fix pads for a 44
Channel Mux/Demux (CMD44) only.

For information on replacement units and product engineering codes (PEC),

see Planning Guide, NTT840FE.

The Optical Metro 5100/5200 20-position SC Patch Panel (NT0H43CBE6) is

recommended for this application. You must use LC-to-SC patch cords
between the CMD44 and the Optical Metro 5100/5200 20-position SC Patch
Panel (NT0H43CBE6).

Requirements
• Ensure that you have the engineering documentation package (EDP) or
equivalent site/network engineering plans.
• Ensure that you have LC-SC patch cords and SC attenuator pads.
• For information on installing a patch panel, see the procedure on
configuring and installing a patch panel for attenuator fix pads (for CMD44)
in Common Photonic Layer Installation, Part 2 of 2, 323-1661-201.
• For information on routing fiber for the patch panel, see the procedure on
routing fiber to a patch panel to prepare to apply attenuator fix pads
(CMD44 systems only).

Procedure steps
Step Action

1 Follow the procedure on replacing a patch panel, in Optical Metro

5100/5200 Maintenance and Replacement Procedures,
323-1701-546.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
323-1661-543
5-1

Restart procedures 5-

This chapter contains procedures for restarting modules, see Table 5-2 for a
list of procedures.

The power cycle and cold restart procedures are service affecting. For this
reason it is recommended that the other restart procedures be attempted in
the order suggested in Table 5-1.

Attention: Your location (remote or local), the communication situation, and

the module type determine the available restart options.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
5-2 Restart procedures

Table 5-1
Suggested order for performing restarts

Order Procedure Service Location Module

affecting

1 5-1 Performing a module warm restart no remote GMD, DOSC,

or local UOSC, MLA,
MLA2, SLA, LIM,
CMDx, SCMDx,
WSS, OPM, DRA,
CMDA

2 5-3 Restarting on the UOSC, GMD, or DOSC using no local only GMD, UOSC,
the reset button DOSC

3 5-2 Performing a module cold restart yes remote GMD, DOSC,

or local UOSC, MLA,
MLA2, SLA, LIM,
CMDx, SCMDx,
WSS, OPM. DRA,
CMDA

4 5-4 Performing a power cycle yes local only GMD, DOSC,

UOSC, MLA,
MLA2, SLA, LIM,
CMDx, SCMDx,
WSS, OPM, DRA,
CMDA

Table 5-2
Restart procedures
Procedure Page Comments

5-1 Performing a module warm restart 5-3 This procedure describes how to perform a warm
restart on a module using TL1 commands and Craft
Interface.

5-2 Performing a module cold restart 5-5 This procedure describes how to perform a cold
restart using TL1 commands and Craft Interface.

5-3 Restarting on the UOSC, GMD, or 5-7 This procedure describes how to perform a warm
DOSC using the reset button restart on the Uni Optical Service Channel (UOSC),
Group Mux/Demux (GMD) module, and the Dual
Optical Service Channel (DOSC) module using the
reset button.

5-4 Performing a power cycle 5-8 This procedure describes how to perform a power
cycle on a module.

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Restart procedures 5-3

Procedure 5-1
Performing a module warm restart
Use this procedure to instruct a network element to initialize one of its
modules.

Attention: Warm restarts are not service affecting.

This procedure describes how to perform a warm restart using either TL1
commands or the Craft Interface.

Prerequisites
Use an account with a level 3 or higher user privilege code (UPC).

Procedure steps
Step Action

1 If you are performing a warm restart using Then complete

Craft Interface step 2 to step 5
TL1 commands step 6 to step 8

Warm restart using the Craft Interface

2 Select Configuration->Inventory.
All the slots within a shelf are listed.
3 Select the module that requires the restart from the list.
4 Click on the Init Warm button.
5 Click Yes to begin the restart.
Warm restart using TL1 commands
6 Establish a TL1 session on the shelf containing the alarmed module. From a
DOS or UNIX prompt, telnet to the IP address of the Common Photonic Layer
shelf containing the alarmed module. For example, enter:
telnet 10.110.10.110

Attention: If telnet access is not possible, log in locally by connecting the

craft PC to the Modem port of the UOSC, GMD, or DOSC using a serial cable
and establish a VT-100 session.

—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
5-4 Restart procedures

Procedure 5-1 (continued)

Performing a module warm restart

Step Action

7 Activate a user session with:

ACT-USER:[<tid>]:<uid>:<ctag>::<pid>:[DOMAIN=<domain>];
8 Use the following command to initiate the warm restart:
INIT-WARM:[<tid>]:<aid>:<ctag>;
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Restart procedures 5-5

Procedure 5-2
Performing a module cold restart
Use this procedure to instruct a network element to initialize one of its
modules.

This procedure describes how to perform a cold restart using either TL1
commands or the Craft Interface.

CAUTION
Service affecting procedure
A cold restart affects traffic. Perform this procedure as your last
restart option.

Prerequisites
Use an account with a level 3 or higher user privilege code (UPC).

Procedure steps
Step Action

1 If possible, switch traffic away from the network element containing the
module you must reset by performing a protection switch at the service layer
(non-Common Photonic Layer equipment) to prevent traffic loss.
2 If you are performing a cold restart using Then complete
Craft Interface step 3 to step 9
TL1 commands step 10 to step 14

Cold restart using the Craft Interface

3 Select Configuration->Inventory.
All the slots within a shelf are listed.
4 Select the module that requires the restart from the list.
5 Click on the Init Cold button.
6 Click Yes to begin the restart
7 Wait for the module to restart.
8 Reset the date and time if required, see Configuration, 323-1661-310, for
procedures on setting the date and time.
9 Undo any traffic rerouting invoked in step 1.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
5-6 Restart procedures

Procedure 5-2 (continued)

Performing a module cold restart

Step Action

Cold restart using TL1 commands

10 Establish a TL1 session on the shelf containing the alarmed module. From a
DOS or UNIX prompt, telnet to the IP address of the Common Photonic Layer
shelf containing the alarmed module. For example enter:
telnet 10.110.10.110

Attention: If telnet access is not possible, then login locally by connecting

the craft PC to the Modem port of the UOSC, GMD, or DOSC using a serial
cable and establish a VT-100 session.

ACT-USER:[<tid>]:<uid>:<ctag>::<pid>:[DOMAIN=<domain>];
11 Use the following command to initiate the cold restart:
INIT-COLD:[<tid>]:<aid>:<ctag>;
12 Wait for the module to restart.
13 Reset the date and time if required, see Configuration, 323-1661-310, for
procedures on setting the date and time.
14 Undo any traffic rerouting performed in step 1.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Restart procedures 5-7

Procedure 5-3
Restarting on the UOSC, GMD, or DOSC using the
reset button
Use this procedure to perform a warm restart on a the Uni Optical Service
Channel (UOSC), Group Mux/Demux (GMD), and the Dual Optical Service
Channel (DOSC) modules using the reset button.

Attention: Warm restarts are not service affecting.

Prerequisites
• Be at the site.
• Observe all safety requirements described in Documentation Roadmap,
323-1661-090.
• Have a flathead screwdriver.
• Have a thin rigid wire, such as a paper clip to insert into the Reset button
hole.

Procedure steps

Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

2 Open the module front cover by turning the screws counterclockwise.

3 Locate the Reset button.
4 Use a thin rigid wire, such as a paper clip to insert into the Reset button hole.
The Active (green) LED blinks during the restart.
5 Wait for the module to restart.
6 Close the module front cover.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
5-8 Restart procedures

Procedure 5-4
Performing a power cycle
Use this procedure to power cycle a module.

When a power cycle occurs on the network element, the network element date
and time can reset to the default values in some cases. See Configuration,
323-1661-310 for procedures on setting the date and time.

CAUTION
Service affecting procedure
A power cycle affects traffic. Perform this procedure as your
last restart option.

Procedure steps
Step Action

1
CAUTION
Risk of damage to modules
Wear an antistatic wrist strap to protect the equipment
from static damage. Connect the wrist strap to the ESD
jack on the shelf or module.

2 If possible, switch traffic away from the network element containing the
module you need to power cycle by performing a protection switch at the
service layer (non-Common Photonic Layer equipment) to prevent traffic loss.
3 If the link contains a DRA in Managed mode and you are performing a
UOSC/DOSC/GMD power cycle, then:
• Set the Shutoff Disabled timer on the DRAs at either end of the link to a
value that will exceed the duration of time the UOSC/GMD/DOSC will be
powered off.
• Put the DRAs at either end of the link in Shutoff Disabled.
• Perform the power cycle.
• After the UOSC/GMD/DOSC recovers for power cycle, put the DRAs at
either end of the link in Shutoff enabled.

4 Turn off the power feeds to the alarmed module at the breaker panel or pull
the fuse or disconnect the power connectors on the faceplate of the module.
5 Wait at least five seconds.
6 Turn on the power feeds to the alarmed module at the breaker panel, or
restore the fuse or power connectors.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Restart procedures 5-9

Procedure 5-4 (continued)

Performing a power cycle

Step Action

7 Wait for the module to restart. The active LED should be green.
8 Undo any traffic rerouting performed in step 2.
9 Reset the date and time if required; see Configuration, 323-1661-310, for
procedures on setting the date and time.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
5-10 Restart procedures

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 323-1661-543
6-1

Recovering from a fiber cut on Stretched

Spans 6-

This chapter describes how to recover from a fiber cut on Stretched Spans
with or without Raman amplification.

Navigation
• Procedure 6-1, Recovering from a fiber cut on a Stretched Span (no
Raman amplification)
• Procedure 6-2, Recovering from a fiber cut on a Stretched Span with
Raman amplification

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
6-2 Recovering from a fiber cut on Stretched Spans

Procedure 6-1
Recovering from a fiber cut on a Stretched Span (no
Raman amplification)
Use this procedure to manage traffic on a Stretched Span configuration in
systems that do not contain Raman amplification, specifically to recover the
traffic after a fiber cut has been repaired on a span exceeding the OSC
budget. On such applications, the CPL data communication traffic that is
normally carried by the OSC is carried over an external link, such as
OME6500 GCC0 or an OM5000 MOTR channel.

Figure 6-1 illustrates a configuration example.

CAUTION
Risk of laser radiation exposure
During this procedure the fiber plant does not have to be
disrupted and the system remains a Class 1(IEC)/Class I
(FDA) product.

If the fiber downstream of the MLA2 Line A output connector

becomes disconnected accidentally while the Amp Auto
Shutoff Disabled feature is active, the radiation at the exposed
fiber can be at hazard level 1M (IEC 60825-2). In this situation,
you must take all safety precautions appropriate to hazard level
1M (IEC 60825-2).

The ORL based APR safety mechanism remains active.

Prerequisites
• The installation of CPL and terminal (OME6500/OM5000) equipment is
complete.
• The CPL and the terminal (OME6500/OM5000) equipment is fibered.
• Network element and nodal commissioning is complete.
• The post amplifiers on each side of the Stretched Span are in Automatic
Shutoff because of a fiber cut.
• The fiber cut is repaired—use the procedure on performing fiber work on
a Common Photonic Layer system in Fault Management - Alarm Clearing
and Module Replacement, 323-1661-543.
• Communications are available to the CPL network elements on either side
of the Stretched Span.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Recovering from a fiber cut on Stretched Spans 6-3

Procedure 6-1 (continued)

Recovering from a fiber cut on a Stretched Span (no Raman amplification)

• Resources are deployed on each side of the Stretched Span, where the
CPL data communications are bridged over to the terminal
(OME6500/OM5000) shelves.
• Resources can communicate to coordinate their actions.

• The site EDPs (engineering design packages)/IDPs (international

engineering packages) and the CPL and the terminal
(OME6500/OM5000) NTPs are available.

Figure 6-1
Recovering from a fiber cut on a Stretched Span (no Raman amplification)—example is using
OME6500 terminal equipment
CPL0622

Stretched Span

GOADM/ GOADM/
••• TOADM/ TOADM/ • • •
ROADM ROADM

ILAN ILAN
DOSC DOSC

OME6500 OME6500
BB Fiber cut BB

Note: For clarity, only amplifiers and Virtual Shelf Controllers are shown.

Procedure steps
Step Action

Temporarily overriding ALSO automatic shutoff on Line A amplifiers

1 Log into the CPL shelves on each side of the Stretched Span and record the
current provisioned shutoff threshold on pre-amplifier facilities facing the
Stretched Span. Disable ALSO on the Stretched Span as follows:
a. Open a telnet session on each CPL shelf facing the Stretched Span and
log into the TL1 interface using the following command:
ACT-USER::<ADMIN Level User>:<CTAG>::<ADMIN Level
password>:;
b. Note the current shutoff threshold (SHUTTHRES) for the Line A (port 8)
amplifier launching into the Stretched Span using the following
command:
RTRV-AMP::AMP-<shelf>-<slot>-8:<CTAG>;
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
6-4 Recovering from a fiber cut on Stretched Spans

Procedure 6-1 (continued)

Recovering from a fiber cut on a Stretched Span (no Raman amplification)

Step Action

c. Set the Line A (port 8) post amplifier shutoff threshold to -60 dB

(temporary shutoff disable, which overrides the Automatic Shutoff
condition) by entering:
ED-AMP::AMP-<shelf>-<slot>-8:<CTAG>:::SHUTTHRES=-60:;
d. Log out using the following command:
CANC-USER::<ADMIN Level User>:<CTAG>;
2 When the post-amplifiers on each side of the Stretched Span have come out
of Automatic Shutoff mode, use the Performance Monitoring application to
measure the span loss after the repair. Make sure the span loss is within
specifications; if not, take the appropriate actions.
3 Allow the system a few minutes to provide complete visibility of the domain
from both sides of the Stretched Span. To verify data communication
continuity, log into the CPL and into the shelves on the other side of the
Stretched Span.
4 After the link has been restored in both directions, perform the following
substeps to take the Line A AMP facilities out of Auto Shutoff Disabled mode
to re-enable normal response to ALSO automatic shutoff requests to Line A
amplifiers on the Stretched Span.
a. Open a telnet session on each CPL shelf facing the Stretched Span and
log into the TL1 interface using the following command:
ACT-USER::<ADMIN Level User>:<CTAG>::<ADMIN Level
password>:;
b. Set the Line B (port 8) amplifier shutoff threshold back to their initial
values (recorded in step 1b) by entering:
ED-AMP::AMP-<shelf>-<slot>-8:<CTAG>:::SHUTTHRES=<init
ial value>:;
For normal operation of Stretched Span applications with valid optical
safety feature operation, the Shutoff Thresholds for the Line A AMP
facilities must be provisioned to -40 dBm, which is below their defaults
(MLA Line A default is -35 dBm; MLA2 Line A default is -39 dBm). Do not
provision this threshold below -40 dBm. All optical safety testing and
accreditation is suspect if this threshold is provisioned below -40 dBm.
c. Log out using the following command:
CANC-USER::<ADMIN Level User>:<CTAG>;
5 If the DOC Automation Mode is not set to Auto Re-optimize As Necessary,
click on the Re-Optimize button in the DOC facility screen.
6 If you were sent to this procedure from another procedure, return to the next
step in the procedure that sent you here. Otherwise, you have completed this
procedure.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Recovering from a fiber cut on Stretched Spans 6-5

Procedure 6-2
Recovering from a fiber cut on a Stretched Span with
Raman amplification
Use this procedure to manage traffic on a Stretched Span configuration in
systems that contain Raman amplification in Managed mode only, specifically
to recover the traffic after a fiber cut has been repaired on a span exceeding
the OSC budget. On such applications, the CPL data communication traffic
that is normally carried by the OSC is carried over an external link such as
OME6500 GCC0 or an OM5000 MOTR channel.

Figure 6-2 illustrates a configuration example.

CAUTION
Risk of laser radiation exposure
During this procedure the fiber plant does not have to be
disrupted and the system remains a Class 1(IEC)/Class I
(FDA) product.

If the fiber upstream of the DRA Line A input connector

becomes disconnected accidentally while the Auto Shutoff
Disable feature is active, the radiation at the exposed fiber can
be at hazard level 3B (IEC 60825-2). In this situation, you must
take all safety precautions appropriate to hazard level 3B (IEC
60825-2).

The ORL based APR safety mechanism remains active.

Prerequisites
• The Installation of CPL and terminal (OME6500/OM5000) equipment is
complete.
• The CPL and terminal (OME6500/OM5000) equipment is fibered.
• Network element and nodal commissioning is complete.
• The Raman and post amplifiers on each side of the Stretched Span are in
Automatic Shutoff because of a fiber cut.
• The fiber cut is repaired—use the procedure on performing fiber work on
a Common Photonic Layer system in Fault Management - Alarm Clearing
and Module Replacement, 323-1661-543.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
6-6 Recovering from a fiber cut on Stretched Spans

Procedure 6-2 (continued)

Recovering from a fiber cut on a Stretched Span with Raman amplification

• Communications are available to the CPL network elements on either side

of the Stretched Span.
• Resources are deployed on each side of the Stretched Span, where the
CPL data communications are bridged over to the terminal
(OME6500/OM5000) shelves.
• Resources can communicate to coordinate their actions.
• The site EDPs (engineering design packages)/IDPs (international
engineering packages) and the CPL and the terminal
(OME6500/OM5000) NTPs are available.

Figure 6-2
Recovering from a fiber cut on a Stretched Span with Raman amplification—example is using
OME6500 terminal equipment
CPL0619

Stretched Span

GOADM/ GOADM/
••• TOADM/ DRA DRA TOADM/ • • •
ROADM ROADM

ILAN ILAN
DOSC DOSC

OME6500 OME6500
BB Fiber cut BB

Note: For clarity, only amplifiers and Virtual Shelf Controllers are shown.

Procedure steps
Step Action

Disabling ALSO
1 Disable ALSO on the Stretched Span as follows:
a. From the Raman facility screen, set the Auto Shutoff Disabled Time to a
value of 30 minutes and select the Disable Auto Shutoff button to place
the DRA in Auto Shutoff Disabled mode.
b. Repeat for the CPL NE at the other end of the Stretched Span.
2 Allow the system a few minutes to provide complete visibility of the domain
from both sides of the Stretched Span. To verify data communication
continuity, log into the CPL shelves on the other side of the Stretched Span.
—continued—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Recovering from a fiber cut on Stretched Spans 6-7

Procedure 6-2 (continued)

Recovering from a fiber cut on a Stretched Span with Raman amplification

Step Action

3 After the link has been restored in both directions, cancel the DRA
Auto Shutoff Disabled mode timer by selecting the Enable Auto Shutoff
button in the Raman facility screen.
4 If the DOC Automation Mode is not set to Auto Re-optimize As Necessary,
click on the Re-Optimize button in the DOC facility screen.
5 If you were sent to this procedure from another procedure, return to the next
step in the procedure that sent you here. Otherwise, you have completed this
procedure.
—end—

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
6-8 Recovering from a fiber cut on Stretched Spans

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
323-1661-543
7-1

Appendix A: Events and logs 7-

Events do not require a specific action. Events report the activity status on the
network elements and logs are used to isolate and troubleshoot alarmed
conditions.

The following event types are supported:

• database changes
• logs
• transient conditions

Table 7-1 lists supported events.

Attention: Users with a level 4 or higher user privilege code (UPC), can view
provisioning database change logs that are not listed in Table 7-1.

Table 7-1
Events

Event

Cancel S/R Completed

Cancel S/R Failed

Cancel S/R Failed:Save/Restore not in progress

Check S/R Completed

Check S/R Failed

Check S/R Failed: Blocked by another application

This event indicates that an operation on the node is preventing the S/R operation
from proceeding. The prevention can be the result of an upgrade, load installation,
or restart. This event also occurs for an S/R attempt on an uncommissioned shelf.

Check S/R Failed: Blocked by presence of alarms

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
7-2 Appendix A: Events and logs

Table 7-1 (continued)

Events

Event

Check S/R Failed: Could not connect to destination

Check S/R Failed: FTP access denied

Check S/R Failed: Invalid destination

This event indicates that a file access violation has occurred, the file names were
too long for the operating system, or that the local files you attempted to FTP do not
exist.

Database Commit Failed

Database Commit Failed: Blocked by another application

This event indicates that an operation on the node is preventing the S/R operation
from proceeding. The prevention can be the result of an upgrade, load installation,
or restart. This event also occurs for an S/R attempt on an uncommissioned shelf.

Database Commit Failed: Blocked by presence of alarms

Database Commit Failed: Restored backup is corrupt

Database Commit: Restart in progress

Database Restore Completed

Database Restore Failed

Database Restore Failed: Backup not from this node

Database Restore Failed: Blocked by another application

This event indicates that an operation on the node is preventing the S/R operation
from proceeding. The prevention can be the result of an upgrade, load installation,
or restart. This event also occurs for an S/R attempt on an uncommissioned shelf.

Database Restore Failed: Blocked by presence of alarms

Database Restore Failed: Could not connect to source

Database Restore Failed: Failure transferring file

Database Restore Failed: FTP access denied

Database Restore Failed: Interrupted by card restart

Database Restore Failed: Invalid source

This event indicates that a file access violation has occurred, the file names were
too long for the operating system, or that the local files you attempted to FTP do not
exist.

Database Restore Failed: Mismatched Software Releases

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Appendix A: Events and logs 7-3

Table 7-1 (continued)

Events

Event

Database Restore Failed: Restored backup is corrupt

Database Save Completed

Database Save Failed

Database Save Failed: Blocked by another application

This event indicates that an operation on the node is preventing the S/R operation
from proceeding. The prevention can be the result of an upgrade, load installation,
or restart. This event also occurs for an S/R attempt on an uncommissioned shelf.

Database Save Failed: Blocked by presence of alarms

Database Save Failed: Blocked by remote application

This event cannot be raised.

Database Save Failed: Could not connect to destination

Database Save Failed: Failure transferring file

Database Save Failed: FTP access denied

Database Save Failed: Interrupted by card restart

Database Save Failed: Invalid destination

This event indicates that a file access violation has occurred, the file names were
too long for the operating system, or that the local files you attempted to FTP do not
exist.

Database Save in Progress

Database Validate Failed

Database Validate Failed: Restored backup is corrupt

Equipment Physical PEC and Provisioned PEC mismatch

Load Installation: Cancel Passed

Load Installation: Check Failed

This event indicates that a CHK-INSTALL or CHK-UPGRD operation has failed.
Verify the TL1 parameters and ensure that they are correct.

Load Installation: Check Passed

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
7-4 Appendix A: Events and logs

Table 7-1 (continued)

Events

Event

Load Installation: Commit Failed

This event indicates that an error (most likely a flash read or write error) occurred
during the commit attempt of a software load operation. Try the load operation again.
If it fails a second time, contact your next level of support or your Nortel support
group.

Load Installation: Commit Passed

Load Installation: Committing New Release

Load Installation: Invoke Failed

This event indicates that an error (most likely a flash read or write error) occurred
during the commit attempt of a software load operation. Try the load operation again.
If it fails a second time, contact your next level of support or your Nortel support
group.

Load Installation: Invoke Passed

Load Installation: Load Failed

This event indicates that an error (most likely a flash read or write error) occurred
while installing a software load. Try the load operation again. If it fails a second time,
contact your next level of support or your Nortel support group.

Load Installation: Load Passed

Load Installation: Programming Load to FLASH

Load Installation: Running from incorrect FLASH bank

Load Installation: Unable to Access Release Files

This event indicates that the required release files could not be located at the
location provided or that access restrictions are preventing the specified user
account from accessing the files.

Load Installation: Unable to Program Load to FLASH

This event indicates that an error occurred when copying a software load to a flash
bank. Try the load operation again. If it fails a second time, contact your next level
of support or your Nortel support group.

Password has expired. Change it now

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
 Appendix A: Events and logs 7-5

Table 7-1 (continued)

Events

Event

Password has expired. Contact your Admin.

Password will expire in 1 day

Password will expire in 2 days
Password will expire in 3 days
Password will expire in 4 days
Password will expire in 5 days
Password will expire in 6 days
Password will expire in 7 days
Password will expire in 8 days
Password will expire in 9 days
Password will expire in 10 days
Password will expire in 11 days
Password will expire in 12 days
Password will expire in 13 days
Password will expire in 14 days

Your password will expire today

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
7-6 Appendix A: Events and logs

Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module Replacement
323-1661-543 Issue 1 Standard
Release 3.2 June 2008
Copyright  2004-2008, Nortel Networks
Nortel Common Photonic Layer

Fault Management - Alarm Clearing and Module

Replacement
Copyright  2004-2008, Nortel Networks
All Rights Reserved
This document is protected by copyright laws and international treaties. All information, copyrights and any other
intellectual property rights contained in this document are the property of Nortel Networks. Except as expressly
authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein
and this document shall not be published, copied, produced or reproduced, modified, translated, compiled,
distributed, displayed or transmitted, in whole or part, in any form or media.

This information is provided “as is”, and Nortel Networks does not make or provide any warranty of any kind,
expressed or implied, including any implied warranties of merchantability, non-infringement of third party
intellectual property rights, and fitness for a particular purpose.

Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

Printed in Canada

Release 3.2
Publication: Fault Management - Alarm Clearing and Module Replacement
Document Status: Standard
Document Issue: Issue 1
Document Release Date: June 2008

To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback.

www.nortel.com