Alarm and Trouble Clearing Procedures

NT7E65DJ 323-1111-543
SONET Transmission Products

S/DMS TransportNode
OC-3/OC-12 NETBM
Alarm and Trouble Clearing Procedures
Standard Rel 14 February 2001
Whats inside...
Safety guidelines
Alarm reporting and surveillance
How to begin trouble clearing
Clearing equipment alarms
Clearing facility alarms
Clearing environment alarms
Interpreting circuit pack LEDs and lamps
Troubleshooting the breaker interface panel (BIP)
Clearing OPC alarms
Clearing incorrect Application Select state
Copyright 19922001 Nortel Networks, All Rights Reserved
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees
with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree
of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Nortel Networks and S/DMS TransportNode are trademarks of Nortel Networks. VT100 is a trademark of Digital Equipment
Corporation. UNIX is a trademark of X/Open Company Ltd.
Printed in Canada
iii
Contents
About this document xv
Safety guidelines 1-1

Warnings and safety precautions 1-1
Circuit packs 1-2
Static electricity 1-2
Handling, installing, or replacing circuit packs 1-2
Storing circuit packs 1-3
Transporting circuit packs 1-3
Software tapes 1-3
Software cartridges 1-4
Optical fibers 1-4
Laser radiation 1-4
Handling optical fibers 1-5
Splicing optical fibers 1-5
Repairing optical fibers 1-6
Radio-frequency emissions 1-6
Equipment location 1-6
Alarm reporting and surveillance 2-1

Alarm severity, service code, and protection and activity status 2-1
Critical 2-1
Major 2-1
Minor 2-2
Warning 2-2
Service code 2-2
Protection and activity status 2-2
Time filtering 2-2
Local alarm indications 2-2
Bay alarms 2-3
Shelf alarms 2-3
Circuit pack alarms 2-4
Cooling unit alarms 2-4
Remote alarms 2-5
Alarm reporting 2-8
Alarm hierarchies (masking relationships) 2-9
Facility alarm hierarchy 2-9
Equipment alarm hierarchy 2-12
Alarm and Trouble Clearing Procedures 323-1111-543 Rel 14 Standard Feb 2001
iv Contents
Common equipment and environmental alarm hierarchy 2-13

Automatic in service (AINS) alarm masking 2-13
Control architecture 2-16
How to begin trouble clearing 3-1

Responding to logs 3-3
List of procedures
3-1 Locating and clearing an alarm 3-4
3-2 Performing an alarm cutoff (ACO) 3-9
3-3 Clearing the alarm condition: PROC red fail LED lit 3-11
3-4 Performing a manual diagnostic test 3-13
3-5 Manually clearing OPC alarms 3-15
Clearing equipment alarms 4-1

List of equipment alarms 4-2
Reference tables: Circuit pack group identification 4-12
Eqp CE 4-19
Autoprovisioning mismatch 4-19
CNET link fail 4-20
CNET performance degraded 4-22
Critical test alarm 4-23
Major test alarm 4-23
Minor test alarm 4-23
Warning test alarm 4-23
Database not restored. Type Q APPROVE at NE 4-24
Datacomm access violation 4-33
Duplicate NE name 4-34
Duplicate NE numeric identifier 4-35
Entry to SONET clock freerun 4-36
Exerciser fail 4-37
Manual area address dropped from area 4-38
NE database backup to OPC failed 4-41
Node count limit is exceeded 4-42
PM threshold capping active 4-43
Ring reconfiguration in progress 4-44
Shelf assembly fail 4-45
Shelf id bus fail 4-46
Software trap 4-47
SONET overhead data/clock loss 4-48
Traffic upgrade in progress 4-50
User port 1 intrusion attempt 4-51
Eqp DS1 4-52
Circuit pack fail 4-52
Circuit pack mismatch 4-53
Circuit pack missing 4-54
DS1 protection unavailable, equipment OOS 4-55
Facility provisioning mismatch 4-56
S/DMS TransportNode OC-3/OC-12 NETBM Vol 5 323-1111-543 Rel 14 Standard Feb 2001
Contents v
Forced switch request 4-57

Input card fail -DoNotRemove 4-58
Output card fail -DoNotRemove 4-58
Input card mismatch 4-59
Output card mismatch 4-59
Input card missing 4-60
Output card missing 4-60
Lockout request 4-61
Manual switch request 4-62
Matchnode connection provisioning mismatch 4-63
Protection equipment unavailable 4-64
Protection path fail 4-65
Protection switch complete 4-69
Protection switch fail 4-70
Protection version mismatch 4-73
STS1 intercard fail 4-74
Eqp DS3 4-76
BNC I/O card 1 fail -DoNotRemove 4-76
BNC I/O card 1 mismatch 4-77
BNC I/O card 1 missing 4-78
DS3 protection unavailable, equipment OOS 4-82
Switcher circuit pack mismatch 4-98
Switcher circuit pack missing 4-99
Traffic problem detected 4-100
VT connection provisioning mismatch 4-103
Protection hardware incompatible 4-104
Eqp ESI 4-105
End VCO range 4-105
Equipment forced switch request 4-106
Equipment lockout request 4-107
Equipment manual switch request 4-108
Equipment protection switch complete 4-109
Equipment protection switch fail 4-111
vi Contents
Failure to lock 4-112

Intercard fail 4-113
Subunit fail 4-115
Subunit mismatch 4-116
Subunit missing 4-117
Timing generation entry to acquire 4-118
Timing generation entry to fast 4-119
Timing generation entry to freerun 4-120
Timing generation entry to holdover 4-121
Eqp Lpbk 4-122
LpbkG1 Automatic firmware download in progress 4-122
LpbkG1S Automatic firmware download in progress 4-122
Intercard cntrl: G1 to LpbkG1S 4-123
Intercard cntrl: G1S to LpbkG1 4-145
Intercard cntrl: LpbkG1 to G1 4-168
Intercard cntrl: LpbkG1S to G1S 4-179
Intercard cntrl: LpbkG1 to LpbkG1S 4-191
Intercard cntrl: LpbkG1S to LpbkG1 4-191
Intercard failure 4-202
LpbkG1 Circuit pack failed 4-204
LpbkG1S Circuit pack failed 4-204
LpbkG1 Circuit pack mismatch 4-206
LpbkG1S Circuit pack mismatch 4-206
LpbkG1 Circuit pack missing 4-207
LpbkG1S Circuit pack missing 4-207
OHB card missing 4-207
LpbkG1 firmware version mismatch 4-208
LpbkG1S firmware version mismatch 4-208
LpbkG1 firmware/software incompatible 4-209
LpbkG1S firmware/software incompatible 4-209
LpbkG1 Maps invalid or missing 4-211
LpbkG1S Maps invalid or missing 4-211
LpbkG1 protection switching byte fail 4-212
LpbkG1S protection switching byte fail 4-212
LpbkG1 STS1 intercard fail 4-213
LpbkG1S STS1 intercard fail 4-213
Ring protection suspended or unavailable 4-215
Unable to track clock reference 4-216
Eqp MIC 4-217
Alarm relay fail 4-217
E2A input fail 4-217
LED driver fail 4-217
Local craft interface port fail 4-217
Orderwire fail 4-217
Parallel telemetry relay fail 4-217
Performance monitor clock fail 4-217
Serial telemetry port fail 4-217
Time of day clock fail 4-217
Contents vii
Firmware version mismatch 4-222

Non-volatile store fail 4-223
Non-volatile store mismatch 4-224
Protection switch relay fail 4-225
Eqp OC3/OC12 4-226
Channel match fail 4-226
Circuit pack reach mismatch 4-230
Fiber connection error 4-231
Hardware/software incompatible 4-235
Laser bias current 4-238
Laser degrade 4-239
Lockout protection operation fail 4-240
Protection oscillation control activated 4-243
Protection scheme mismatch 4-246
Protection switching byte fail/Improper APS code 4-253
Receive fail 4-254
Switch mode mismatch 4-257
Transmission rate mismatch 4-258
Transmit fail 4-259
Eqp OC12 4-261
Automatic firmware download in progress 4-261
Backplane USEB inconsistent 4-262
Default K Bytes 4-263
Entry to SONET clock acquire 4-264
Entry to SONET clock holdover 4-266
Fiber loopback 4-268
Firmware corrupt 4-269
Firmware/software incompatible 4-271
Firmware trap 4-272
Hardware/software incompatible 4-273
Intercard cntrl: G1 to LpbkG1 4-275
Intercard cntrl: G1S to LpbkG1S 4-287
Intercard serial link fail 4-298
Invalid neighbor detected 4-300
Lockout protection request 4-302
Lockout working request 4-303
viii Contents
Maps invalid 4-304

NE id mismatch 4-306
Protection switch complete (remote request) 4-308
Protection switching byte/APS code inconsistent 4-309
Reference input clock fail 4-310
STS12 ring link parity error 4-311
Synchronization clock fail 4-314
System clock reference fail 4-315
Eqp OPC 4-317
OPC alarm(s) active 4-317
OPC circuit pack fail 4-318
OPC circuit pack mismatch 4-319
OPC circuit pack missing 4-320
OPC CNET loss of signal 4-321
OPC Ethernet loss of signal 4-322
OPC hardware reset 4-324
OPC OAM software fail 4-325
Eqp Proc 4-327
Both C-Bus access fail 4-327
C-Bus-A access fail 4-328
C-Bus-B access fail 4-329
Communication processor fail 4-330
Degraded communication processor 4-331
Degraded host processor 4-332
Degraded master CBIC-A 4-333
Degraded master CBIC-B 4-333
Firmware prom fail 4-334
Interprocessor comm fail 4-336
Eqp Remt 4-337
Remote critical 4-337
Remote major 4-338
Remote minor 4-339
Remote subnetwork 4-340
Eqp STS-1 only 4-341
Firmware failure 4-348
Contents ix

Protection equipment unavailable 4-353
Eqp STS1 4-362
STS1 protection unavailable, equipment OOS 4-362
Clearing facility alarms 5-1

List of facility alarms 5-2
Reference tables: Circuit pack group identification 5-7
Fac Comm 5-12
Sonet DCC link fail 5-12
Sonet DCC performance degraded 5-14
Fac DS1 5-16
Line Rx CV threshold 1, 2 5-16
Line Rx ES threshold 1, 2 5-16
Line Rx SES threshold 1, 2 5-16
Loopback 5-19
Path Rx CV threshold 1, 2 5-20
Path Rx ES threshold 1, 2 5-20
Path Rx SAS threshold 1, 2 5-20
Path Rx SES threshold 1, 2 5-20
Path Rx UAS threshold 1, 2 5-20
Rx AIS 5-23
Rx bipolar violation >10E-3 5-24
Rx loss of frame 5-26
Rx loss of signal 5-28
Rx Yellow 5-30
RTU DTAU test in progress 5-31
STS1 Rx path trace failure 5-32
STS1 Rx RFI 5-38
STS1 Rx unequipped 5-39
STS1 signal label mismatch 5-41
VT Rx AIS 5-42
VT Path Rx ALS threshold 1, 2 5-43
VT Path Rx ES threshold 1, 2 5-43
VT Rx loss of pointer 5-44
VT Rx RFI 5-45
VT Rx unequipped 5-46
Fac DS3 5-48
Frequency out of range 5-48
x Contents

Loopback 5-52
Path Rx AISS threshold 1, 2 5-53
Path Rx SEFS threshold 1, 2 5-53
Path Tx AISS threshold 1, 2 5-56
Path Tx CV threshold 1, 2 5-56
Path Tx ES threshold 1, 2 5-56
Path Tx SEFS threshold 1, 2 5-56
Path Tx SES threshold 1, 2 5-56
Path Tx UAS threshold 1, 2 5-56
Rx AIS 5-61
Rx Parity error rate>10E-6 5-68
STS1 Rx RFI 5-76
Tx AIS 5-80
Tx loss of frame 5-81
Fac ESI 5-83
Bipolar violation 5-83
Degraded clock carrier 5-84
Loss of frame 5-85
Loss of signal 5-86
Rx AIS 5-87
Tx AIS 5-88
Undefined sync status message 5-93
Fac OC3/OC12 5-94
Line RFI 5-94
Line Rx UAS threshold 1, 2 5-95
Sect Rx CV threshold 1, 2 5-95
Sect Rx ES threshold 1, 2 5-95
Sect Rx SES threshold 1, 2 5-95
Sect Rx SEFS threshold 1, 2 5-95
Loss of frame 5-105
Rx AIS 5-110
Signal degrade 5-117
Signal fail 5-123
STS1 Rx AIS 5-129
STS1 Rx loss of pointer 5-131
Contents xi
Fac OC12 5-132

Degraded timing reference 5-132
Inter-ring both feeds fail (matched nodes on rings only) 5-133
Inter-ring forced switch request 5-135
Inter-ring protection switch complete 5-136
Inter-ring lockout request 5-141
Inter-ring manual switch request 5-142
Line FE CV threshold 1, 2 5-143
Line FE ES threshold 1, 2 5-143
Line FE SES threshold 1, 2 5-143
Line FE UAS threshold 1, 2 5-143
Rx Inter-ring secondary feed fail (matched nodes on rings only) 5-145
Section Rx optical power threshold 5-147
STS1 path FE CV threshold 1, 2 5-148
STS1 path FE ES threshold 1, 2 5-148
STS1 path FE SES threshold 1, 2 5-148
STS1 path FE UAS threshold 1, 2 5-148
STS1 path Rx CV threshold 1, 2 5-150
STS1 path Rx ES threshold 1, 2 5-150
STS1 path Rx SES threshold 1, 2 5-150
STS1 path Rx UAS threshold 1, 2 5-150
STS1 Rx RFI 5-157
Timing reference interface fail 5-161
Tx loss of Inter-ring secondary feed (matched nodes on rings only) 5-162
Fac Remt 5-164
First-Alert connection down 5-164
Fac STS1 5-166
Line Rx BCV threshold 1, 2 5-166
Line Rx BES threshold 1, 2 5-166
Line Rx BSES threshold 1, 2 5-166
Loopback 5-169
Rx Line AIS 5-179
Rx RFI 5-180
STS1 Rx AIS 5-181
Reference forced switch request 5-186
Reference manual switch request 5-187
Reference switch complete 5-188
Reference switch fail 5-189
xii Contents
Clearing environment alarms 6-1

List of environment alarms 6-1
Env CE 6-3
48V battery A CE supply fail 6-3
48V battery B CE supply fail 6-3
Fan 1 fail 6-4
Fan 2 fail 6-4
Fan 3 fail 6-4
Fan 4 fail 6-4
Multiple fan fail 6-7
High bay temperature 6-9
High CE shelf temperature 6-10
Env Input 6-11
Telemetry input n 6-11
Env Remt 6-13
Remote environmental #1 6-13
Interpreting circuit pack LEDs and lamps 7-1

Breaker interface panel (NT7E56) 7-4
Cooling module (NT4K17) 7-4
DS1 VT mapper circuit pack (NT7E04) 7-5
DS3 STS mapper circuit pack (NT7E08) 7-5
External synchronization interface (ESI) unit (NT7E27) 7-6
Maintenance interface controller (MIC) circuit pack (NT4K53) 7-7
OC-3 (NT7E01) or OC-12 (NT7E02 or NT7E05) optical interface circuit pack 7-9
OC-12 ring loopback circuit pack (NT7E35) 7-10
OPC module (NT7E24) 7-11
Processor (Proc) circuit pack (NT4K52) 7-13
Protection switcher (NT4K60) 7-13
STS-1 electrical interface circuit pack (NT7E09) 7-14
STS-12 electrical interface circuit pack (NT7E33) 7-15
Troubleshooting the breaker interface panel (BIP) 8-1

BIP troubleshooting 8-7
Bay audible alarm 8-7
ACO pushbutton indicator lit 8-8
Power (white) indicator lit 8-9
On NT7E56AB/BA 8-9
On NT7E56CA 8-9
Critical (red) alarm indicator lit 8-10
Major (red) alarm indicator lit 8-11
Minor (yellow) indicator lit 8-12
Circuit breaker trip LED (red) lit 8-13
BIP troubleshooting 8-15
Troubleshooting the modem in the BIP 8-15
Contents xiii
Clearing OPC alarms 9-1

Below-baseline CP exists in the system 9-3
Datasync fail 9-5
Configuration audit fail 9-6
Connection audit fail 9-8
Lost peer OPC 9-10
NE DB missing/outdated 9-11
Removable media/Restore fail 9-13
Connection services disabled 9-17
User profile audit fail 9-18
NE ID renumbering in progress 9-19
Networkid and/or Systemid renumbering in progress 9-20
Backup: TCP/IP access violation
Primary: TCP/IP access violation 9-21
Backup: Datacomm access violation
Primary: Datacomm access violation 9-22
Backup: network port intrusion
Backup: serial port intrusion
Primary: network port intrusion
Primary: serial port intrusion 9-23
Clearing incorrect Application Select state 10-1

10-1 Trouble clearing incorrect Application Select state 10-3
xiv Contents
xv
About this document

This document consists of nine chapters.
Chapter 1 contains the safety guidelines for the OC-3/OC-12 network
element.
Chapter 2 contains information on alarm reporting and surveillance.
Chapter 3 contains information on how to begin trouble clearing.
Chapter 4 describes how to clear OC-3/OC-12 equipment alarms.
Chapter 5 describes how to clear OC-3/OC-12 facility alarms.
Chapter 6 describes how to clear OC-12 environmental alarms.
Chapter 7 provides a brief description of all the circuit pack
trouble-condition light-emitting diodes (LEDs).
Chapter 8 describes how to troubleshoot the integral modem in the BIP
panel.
Chapter 9 provides procedures on clearing OPC alarms.
Audience
This document is for the following members of the operating company:
field maintenance personnel
maintenance engineers
system lineup and test (SLAT) engineers and technicians
network administrators
NE and OPC user interfaces

The NE and OPC user interfaces are summarized in Common Procedures,
323-1111-846. If you are not familiar with the OPC or NE user interface screen
layouts, commands, and menu hierarchies, see User Interfaces Description,
323-1111-301.
xvi About this document
Circuit pack/facility states

All circuit packs and facilities can be in one of three operation states: out of
service, null, or in service. There are defined as follows:
Out of service (OOS) For a module or a facility which is in the OOS state, no
alarms are reported and both protection switching and performance
monitoring are inhibited. The OOS state is achieved through the chgstate
command and is used when maintenance action is being taken on the facility.
For example, when initiating a loopback, the facility must be placed OOS first.
Null This state is implemented using the delete command. In the null state, the
facility and circuit pack are completely removed from the system software. In
other words, the facility or circuit pack no longer exists.
In service In this state, all alarms, protection switching, and performance

monitoring are as in the normal operating state. The in-service state is initiated
with the chgstate command and is used for circuit packs and facilities which
have been tested and are ready for traffic assignment.
The following presents a summary of possible states for DS1, DS3, STS-1, or
OC-3/OC-12 facilities with respect to the state of the circuit pack on which it
resides.
Circuit pack states Possible facility states

Null NULL
OOS OOS/NULL
IS IS/OOS/NULL
Note 1: When a circuit pack is pulled out, its state does not change.
Note 2: Alarms are generated only when circuit packs are in the IS state.
Note 3: A green Active LED is turned off when a circuit pack is placed
OOS.
Note 4: A yellow LOS LED does not change state when a circuit pack is
placed OOS. The LOS LED is not updated while the circuit pack is OOS.
The following table presents a summary of system actions that are applicable
for the various states of the DS1, DS3, STS-1, and OC-3/OC-12 facilities.
About this document xvii
System actions Null OOS In-service

1. Change of state logs Y Y Y
2. Configuration data present Y Y Y
3. Card inserted N Y Y
4. Card LED operable N Y Y
5. HMI/Bay lamp alarms N N Y
6. Alarm log reports N N Y
7. Perf Mon enabled N N Y
8. Man Prot Sw enabled N N Y
9. Auto Prot Sw enabled N N Y
10. Bay audible alarms N N Y
11. E2A Telemetry alarms N N Y
References in this document

This document refers to the following documents:
About the OC-3/OC-12 NETBM Library, 323-1111-090
System Description, 323-1111-100
Circuit Pack Descriptions, 323-1111-102
Alarms and Surveillance Description, 323-1111-104
Performance Monitoring Description, 323-1111-105
Ordering Information, 323-1111-151
TL1 Interface Description, 323-1111-190
OSI Interface Description, 323-1111-191
Installation Procedures, 323-1111-201
Commissioning Procedures, 323-1111-220
System Administration Procedures, 323-1111-302
Data Administration Procedures, 323-1111-304
Provisioning and Operations Procedures, 323-1111-310
Protection Switching Procedures, 323-1111-311
Network Surveillance Procedures, 323-1111-510
Performance Monitoring Procedures, 323-1111-520
Routine Maintenance Procedures, 323-1111-546
Module Replacement Procedures, 323-1111-547
Log Report Manual, 323-1111-840
Common Procedures, 323-1111-846
Express Alarm and Trouble Clearing Procedures, 323-1051-543
xviii About this document
1-1
Safety guidelines 1-
This chapter contains safety guidelines that must be followed for personal
safety and for the proper handling and operation of equipment.
Warnings and safety precautions

To avoid injury, follow all danger warnings provided with this product, as well
as the safety procedures established by your company.
To avoid damage to equipment or service interruptions, follow all caution

warnings provided with this product, as well as the safety procedures
established by your company.
In this documentation, danger and caution notices look like the following.
DANGER
Risk of personal injury
A danger warning with this symbol indicates a risk of personal
injury.
DANGER
Risk of electrical shock
A danger warning with this symbol indicates a risk of personal
injury due to an electrical hazard.
CAUTION
Risk of interruption to service/equipment damage
A caution warning with this symbol indicates a risk of service
interruption or equipment damage.
CAUTION
Risk of damaging circuit packs
A caution warning with this symbol alerts you to use antistatic
protection to avoid damaging circuit packs.
1-2 Safety guidelines
Circuit packs
All circuit packs are subject to damage by rough handling or from electrostatic
discharge. Adhere to the following procedures to avoid damaging the circuit
packs.
Static electricity
Static electricity charges build up on your body if you walk a short distance.
This buildup is sufficient to damage a circuit pack. Therefore, always wear a
skin-contact ground strap or other suitable personal grounding device when
working on a shelf, on cables connected to a circuit pack, or on a circuit pack
itself.
Ground straps can be the expandable-wrist type where the grounding cord is
connected to the ground plug on the local craft access panel (LCAP).
FW-1674
ESD Ground
jack
Alternatively, your company may provide antistatic protection by mounting

bays on conductive floor coverings, and providing conductive shoes or heel
grounders to all personnel.
All circuit packs are shipped in antistatic bags marked with the following
symbol.
ATTENTION ATTENTION
OBSERVER DES PRECAUTIONS OBSERVE PRECAUTIONS
POUR LA MANIPULATION. FOR HANDLING
DISPOSITIFS SENSIBLES AUX ELECTROSTATIC
CHARGES STATIQUES SENSITIVE DEVICES
Handling, installing, or replacing circuit packs

When handling, installing, or replacing circuit packs, observe the following
precautions:
Wear a wrist strap or other static-grounding device before removing a
circuit pack from its package or from a shelf.
Place each circuit pack in an antistatic bag when it is not mounted in a
shelf.
Handle each circuit pack by the faceplate or stiffener.
Do not touch the solder side of the circuit pack, the pin connector, or the
components.
Do not stack circuit packs on or against each other.
Inspect all circuit packs for damage before sliding them into the shelf.
Closely inspect all pin connectors to ensure pins are undamaged.
Do not force circuit packs into their packaging material.
Protect all optical connectors of the transmit and receive optical circuit
packs by covering them with clean dust caps at all times.
Before inserting any circuit pack or OPC into a shelf, or using a portable
operations controller (OPC), allow the circuit pack or OPC to come to
room temperature.
Storing circuit packs
Spare circuit packs must be left in the original shipping container until
required. To prevent damage to circuit packs while in storage, observe
procedures that prevent the following:
accumulation of dirt or dust on the pin connectors
damage to the board or its components
board warpage (to boards stored in areas where the humidity can exceed
95 percent and the temperature can exceed 70C)
Transporting circuit packs
When transporting circuit packs, pack each circuit pack in its original antistatic
shielding bag, padding, and box. If the original material is lost, use other
suitable material to prevent damage in transit.
Software tapes
All software tapes are subject to damage by rough handling or from
electrostatic discharge. When handling or installing software tapes, observe
the following precautions:
Wear a wrist strap or other static-grounding device before removing a
software tape from its package or from an OPC.
Place each software tape in its case when it is not mounted in an OPC tape
drive.
Do not touch the bare tape in the cassette.
Inspect all tape cassettes for damage before sliding them into the OPC tape
drive.
Do not force tape cassettes into the OPC tape drive.
Before inserting any cassette tape into an OPC tape drive, allow the
cassette tape to come to room temperature.
Software cartridges
When handling or installing software cartridges, observe the following
precautions:
Wear a wrist strap or other static-grounding device before you insert or
remove a cartridge from the cartridge drive of an OPC.
Place each cartridge in its case when you remove it from the cartridge drive
of an OPC.
Ensure that the cartridge is inserted with connector facing inward and the
Nortel Networks logo facing towards the left. Do not force the cartridge
into the OPC cartridge drive.
Optical fibers
Optical fibers are either single or multiple strand. The following information
and precautions apply to all fibers.
Laser radiation
All Nortel Networks S/DMS optical products and associated optical test sets
use laser sources that emit light energy into fiber cables. This energy is within
the red (visible) and infrared (invisible) regions of the electromagnetic
spectrum.
Laser products are subject to federal regulations, state or provincial

regulations, and local practices. Regulation 21 CFR 1040 of the U.S. Bureau
of Radiological Health requires manufacturers to certify each laser product as
Class I, II, III, or IV, depending on the characteristics of the laser radiation
emitted. In terms of health and safety, Class I products present the least hazard
(none at all), while class IV products present the greatest hazard.
All Nortel Networks S/DMS transmission Caution

products comply with 21 CFR 1040, Chapter 1, Avoid direct exposure to
subchapter J as a Class I laser product, as set beam. Invisible light can blind.
forth by the U.S. Bureau of Radiological Keep all optical connectors
Health. These regulations ensure that there are capped.
no hazards to personnel from the laser transmitter when the system is in its
operating configuration. A label similar to the one above is located on all
optical interface packs, near the optical connector.
During testing and maintenance, some procedures require the handling of

optical fibers and transmitters with the dust caps removed. In these
circumstances, laser radiation within the limits of Class IIIb might be present.
This level of radiation is sufficient to cause injury to personnel and caution

must therefore be exercised to avoid exposure. This precaution applies to any
point in the system where the laser signal can be accessed (for example at the
optical connectors on the optical interface circuit packs).
Handling optical fibers

When working with optical fibers, observe the following precautions:
Wear safety glasses when installing optical fibers.
Avoid direct exposure to fiber ends or optical connector ends where the
laser signal can be accessed.
Wipe clean or wash your hands after handling optical fibers. Small bits of
glass are almost invisible and can damage your eyes.
DANGER
Risk of eye injury
If there is any suspicion of a glass chip in your eye, seek
medical attention at once.
Do not handle pieces of optical fiber with bare fingers. Use tweezers or the
sticky side of a piece of vinyl tape to pick up and discard any loose fiber
ends.
Place all optical fiber cuttings in a plastic bottle provided for that purpose.
Handle optical fibers with care. Position them in a safe and secure location
during installation.
Protect all optical fiber connectors with dust caps at all times.
Follow the manufacturers instructions when using an optical test set.
Incorrect calibration or control settings could result in hazardous levels of
radiation.
Splicing optical fibers
During the splicing of any fiber, you might be required to look at the fiber using
an eye loupe (a small magnifier). Observe the following precautions:
Before starting the splicing, power off all laser sources to the fiber or
disconnect the remote fiber end from the laser sources.
Ensure that the laser sources stay disconnected or powered off, whether the
sources are located in a central office, subscriber premises, or a remote
location.
Before starting the splicing, disconnect any optical test sets from the fiber
(whether locally or remotely connected).
Use only the optical instruments approved by your company.
Repairing optical fibers

When there is an accidental break in the fiber:
Notify both central-office and field-repair personnel.
Identify to the central-office personnel where the fibers have been
damaged.
Power off all laser sources to the fiber or disconnect the remote fiber end
from the laser sources, whether the sources are located in a central office,
subscriber premises, or a remote location.
Radio-frequency emissions
The following regulatory notice applies to all Nortel Networks SONET
transmission products.
This equipment has been tested and found to comply with the limits for a
Class A digital device pursuant to Part 15 of the Federal Communications
Commission (FCC) Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in
a commercial environment.
This equipment generates, uses, and can radiate radio-frequency energy
and, if not installed and used in accordance with the instruction manual,
may cause harmful interference to radio communications. Operating this
equipment in a residential area may cause harmful interference, in which
case users must correct the interference at their own expense.
Equipment location
To prevent access by other To be installed only in restricted access areas
than trained personnel, all (dedicated equipment rooms, equipment
equipment must be placed closets, or the like) in accordance with articles
in restricted access areas 110-16, 110-17, and 110-18 of the National
(dedicated equipment Electrical Code, ANSI/NFPA No. 70.
rooms, equipment closets, or the like) in accordance with articles 110-16,
110-17, and 110-18 of the National Electrical Code, ANSI/NFPA No. 70. The
equipment warning label above is located in the top left-hand corner of the
back cover of each shelf to remind installers of this requirement.
2-1
Alarm reporting and surveillance 2-

The OC-3 and OC-12 network elements offer an integrated alarm reporting
system structured to efficiently locate and identify the source of a problem.
There is a correlation of all alarm indications in order to present only one alarm
point for each event whenever possible. Single-ended maintenance is
provided, which means that a user can issue commands from one network
element to be executed at another network element within the system.
Note: Shelf alarm monitoring is not available during processor circuit

pack reset or software download.
For information on how to display alarms for the network elements within an
operations controller (OPC) span of control, and a summary of the OPC
network surveillance tools, see Network Surveillance Procedures,
323-1111-510.
Alarm severity, service code, and protection and activity status

The alarms are classified into four severity levels: critical (C), major (M),
minor (m), and warning (w). These indicate which level of office alarm is
raised. Each alarm point has a default severity level.
Critical and major alarms are represented with red lamps at the shelf and bay
levels, while minor alarms are represented with yellow lamps. There are no
lamps for warnings, but the warning indication appears on the user interface
screens.
Critical
Critical alarms are the most severe alarms. Unprotected optical-line failures
and unprotected service-carrying circuit pack failures are examples of critical
alarms.
Major
Major alarms correspond to failures that are not as severe as critical alarms.
Low-speed (DS3 rate or lower) tributary failures or configuration alarms such
as a missing interface circuit pack are examples of major alarms.
2-2 Alarm reporting and surveillance
Minor
Protected circuit pack failures and common equipment circuit pack failures are
examples of minor alarms.
Warning
A warning is less severe than a minor alarm. It indicates a condition to
investigate, for example, a switch-complete indication or the detection of a
maintenance signal.
Service code
Alarms of all severity levels are also assigned a service code that indicates if
the alarm is service affecting (SA) or not service affecting (NSA). For
example, an unprotected optical unit failure is reported as SA, while a
protected optical unit failure is reported as NSA.
Protection and activity status

The alarm severity and service code often differ according to whether the
equipment or facility is protectable. If a fault appears on an equipment or
facility that either carries traffic or provides timing, and the traffic or timing
does not switch automatically to the protection equipment or facility, then the
failed equipment or facility is unprotectable. In this case, the fault exists on the
active equipment or facility.
If the traffic or timing switches to the protection equipment or facility, then the
equipment or facility is protectable. In this case, the fault exists on the inactive
equipment or facility.
The protection equipment or facility is not available during protection lockout,

if not installed, is providing protection to another equipment or facility, is out
of service, or has failed.
Time filtering
The OC-3 and OC-12 network elements support time filtering of alarms, as
specified in Bellcore TR-TSY-00253. Time filtering means that an alarm
condition must be present for a predetermined amount of time before the alarm
report is generated. Also, the alarm indication has cleared a predetermined
amount of time after the alarm condition clears.
Local alarm indications

The OC-3 and OC-12 network elements provide local alarm indications to
simplify locating the source of a problem. There are bay, shelf, and unit level
alarms available at a network element. Hardware (circuit pack) or software
(shelf processor) control all local alarms.
Bay alarms
Labeled lamps on the breaker interface panel (BIP) indicate the presence of an
alarm within that bay; see Figure 2-1. Individual red lamps denote critical and
major alarms, while yellow lamps denote minor alarms.
These alarms are also available as office alarms. There are three Form-C relay
contacts for audible alarms and three Form-C relay contacts for visual alarms.
An illuminated pushbutton switch enables the alarm cutoff (ACO) for the
audible alarms only. The visual alarms cannot be cut off.
Figure 2-1
Bay alarms on the breaker interface panel (BIP)
FW-0142.1
Battery A Battery B ACO/LT

Trip A1 A2 A3 A4 B1 B2 B3 B4
Power
I I I I I I I I
Critical
O O O O O O O O
Major
Minor
Bay alarms
Shelf alarms
The shelf alarms are indicated with colored lamps on the local craft access
panel (LCAP) directly above each TBM shelf. The LCAP has individual lamps
for critical, major, and minor alarms, as well as a pushbutton ACO switch; see
Figure 2-2.
Figure 2-2
Shelf alarms on the local craft access panel (LCAP)
FW-0143 (OC)
ACO/LT Critical Major Minor ESD

Ground
Call Incoming
Cover Flap Indicator
(Open Position)
ACO/LT Critical Major Minor ESD

Ground
Circuit pack alarms

Most circuit packs include one or more light-emitting diodes (LED) on the
faceplates to indicate the source of the problem. Generally speaking, the LED
colors are defined as follows (see Chapter 7, Interpreting circuit pack LEDs
and lamps, for a description of each circuit pack.)
Red
A red LED indicates a probable circuit pack failure, a high temperature
condition on the shelf, or an exerciser failure.
Green
A green LED indicates that the circuit pack is in service, and that it should not
be removed.
Yellow
On a traffic-carrying circuit pack, yellow indicates a loss of signal. On other
circuit packs, it indicates that an active lockout or loopback is being
performed, that the exerciser is running, or that the circuit pack or shelf is
being initialized.
The circuit-pack LEDs are illustrated in Circuit Pack Descriptions,

323-1111-102.
Cooling unit alarms

Three visual alarm indicators appear on the cooling unit. A red fail indicator
(see Figure 2-3) appears on the face of each of the three fan modules. If the fan
in the cooling unit fails, the fail indicator on a fan module lights up.
Figure 2-3
Visual indicators on the cooling unit
FW-1925
Fail indicators
CU
Interface
CU Pwr
A(), B()
(see Note)
Note: A second set of cooling unit power connectors (CU Pwr A and B) for the
through-flow cooling unit (NT4K18BA) is located on the right side of the shelf.
Note: The A and B connectors of the cable organizer panel (COP) cooling
unit (NT7E7801) are located on the opposite side.
Remote alarms
The craftsperson can access the alarm information from anywhere within the
same system, using different interfaces that have connectorized ports on the
shelf side interconnect left (SIL) circuit pack.
The SIL contains ports for the following (see Figure 2-4):
a VT100 user interface
TBOS (Serial E2A) applications
parallel telemetry applications (input latches and output relays)
TL1
In addition to the ports available on each shelf, each OPC has an Ethernet port.
The Ethernet port can connect a graphical terminal (NCD X-Terminal) to the
OPC.
These interfaces are described in more detail in Alarms and Surveillance

Description, 323-1111-104. See TL1 Interface Description, 323-1111-190, for
details concerning TL1.
Figure 2-4
Surveillance interfaces
FW-1945(TBM)
X.11 Terminal
TBM Shelf Graphical
Ethernet User Interface
Operations
Controller VT100-type
OPC Terminal
CNet Port 1 or
LAN X.25 TL-1
interface
or
Printer
Processor
User Interface card Side Interconnect
Port 2 (RS-232) Left (SIL)
on LCAP OAM card connectors
Bus
X.25 TL-1
OPC interface
Maintenance Port 2
Interface
card Side Interconnect
Left (SIL)
User Interface
card connectors (Note)
(Local terminal
VT100-type)
Side Interconnect Left (SIL)
card connectors
Serial Telemetry ports

(Alarm Processing Remote)
External
Relay TBOS
Customer
Outputs (E2A)
Inputs
1 18 1 11

User Interface
Parallel Parallel Port 1 (RS-232)
Telemetry Out Telemetry In
OR
Printer
OR
Modem to Remote Terminal

User Interface
(Local Terminal
VT100-type)
Note: OPC Port 2 is not available if the NT7E24AA or NT7E24BA OPC circuit packs are used.
OPC Port 2 is available in a TBM shelf provided the OPC is equipped in slot 5.
Alarm reporting
Alarm points are divided into three classes: facility alarms, equipment alarms,
and environmental alarms (see Table 2-1).
Facility alarms relate to the signals being carried, while equipment alarms
relate to the circuit packs processing the signals. Environmental alarms
correspond to a fan failure or a high-temperature alarm, 48-V battery supply,
as well as external customer inputs (for example, an open door or a fire alarm)
or remote alarms.
The alarm reporting feature supports the correlation of multiple alarms that
indicate the same failure. All alarm indications are also screened through a
hierarchy to eliminate related alarm indications. In general, only one alarm
report is generated.
Table 2-1
Alarm classes and types
Facility alarms Equipment alarms Environment alarms
COMM CE (common equipment) (shelf) CE (common equipment)

(shelf)
DS1 DS1 Input
DS3 DS3 REMT (remote)
ESI ESI (external synchronization

interface)
OC3/OC12 Lpbk (loopback)
REMT (remote) MIC (maintenance interface

controller)
STS-1 OC3/OC12 (OC-3/OC-12)
OC12 (OC-12)
OPC
Proc (processor)
REMT (remote)
STS1 (STS-1 electrical interface)
Alarm hierarchies (masking relationships)

Alarms are screened through a hierarchy to eliminate related alarm indications.
In all hierarchies (facility alarm, equipment alarm, common equipment alarm,
and environment alarm), if a higher-level alarm point is raised, the lower-level
alarm points are masked. Examples of alarms in the various hierarchies
follows.
Figure 2-5 shows the various alarm classes. Alarms within each of the classes
can mask or be masked by other alarms of that category or other categories.
Figure 2-6 provides an overview of the masking relationship between the
categories of alarms shown in Figure 2-5.
Figure 2-5
Alarm classes
FW-0592 (TBM)
ESI timing Environmental

reference (External)
Facility Equipment
OC-12 DS1 DS3 STS-1 DS1 Common OC-12 STS-1
DS3 ESI
Facility alarm hierarchy

Figure 2-7 gives the complete hierarchy for the facility alarm class. OC-12
equipment alarms mask all OC-12 and STS-1 facility alarms. The lines in
Figure 2-5 represent a general relationship. The OC-12 equipment alarms do
not mask every alarm lower in the hierarchy. In general, circuit pack failures
mask inter-card failures.
Example of a DS1 or DS3 facility alarm
A loss of frame (LOF) is detected and the alarm point is raised. A failure in an
external piece of equipment results in DS1 or DS3 AIS being sent into the
shelf. However, the Rx AIS alarm is not reported due to the higher-level LOF
alarm.
Figure 2-6
Overview of alarm hierarchies (OC-12)
OS.0519
Equipment alarms
Circuit pack Circuit pack Section Tx

Laser fail
mismatch missing laser bias
current (LBC)
Circuit pack threshold
fail
Firmware/software Circuit pack

incompatible reach mismatch
Facility alarms
OC-12
OC-12
Rx loss of signal facility
span
performance-
alarms
monitoring
Loss of frame
thresholds
(Note 2)
STS-12
Signal fail Rx AIS
line
alarms Rx signal degrade
(Note) Line RFI
Protection switch Invalid K-bytes Protection scheme Switch mode

fail mismatch mismatch
Protection Manual switch Protection switch Forced switch Lockout

path fail request complete request request
Note 1: The STS-12 alarms apply to the STS-12 and OC-12 interface circuit packs.
FW-2439
Note 2: All OC-12 performance-monitoring alarms are independent; that is, they
do not mask each other and neither mask nor are masked by other alarms.
Figure 2-7
Facility alarm hierarchy
OS.0577
OC-3 or OC-12 Facility STS1 Facility
Optical Source STS1 Source

Rx LOS Loopback Rx LOS
LOF
Rx LOF Rx BPV
Rx AIS (line) Signal Fail Rx Line AIS

Signal Degrade
Rx RFI Rx LOP
Line RFI Rx Path AIS
Path Facility
DS3 Facility
STS1 Rx LOP DS3 Source
STS1 Rx AIS (path) Loopback

Rx LOS
Freq OOR
Path Facility or
DS3 Facility
STS1 Rx Unequipped Rx AIS (path) Rx BPV

STS1 SLM
Rx LOF
STS1 Rx PTF
STS1 Path RFI Tx LOF

Tx AIS (path)
DS1 Facility
DS1 Source
VT Rx LOP Loopback
VT Rx AIS Rx LOS
VT Rx Unequipped
Rx AIS (path) Rx BPV

VT Path RFI Rx LOF
Rx Yellow
Example of an OC-3 or OC-12 facility alarm

A line alarm indication signal (AIS) is detected on the OC-3 or OC-12 facility
and the alarm point is raised. A loss of signal (LOS) is then detected. The line
AIS alarm is cleared and the LOS alarm is asserted. When the LOS condition
is cleared, the OC-3 or OC-12 line is monitored to determine if lower-level
alarms are present (for example, loss of frame, or signal degrade).
Equipment alarm hierarchy

In general, the equipment alarm identifies the nature of the failure and the
equipment affected. Figure 2-8 indicates the hierarchy of the three common
alarms (except the processor circuit pack).
Equipment alarms mask all facility alarms except for the Protection path fail
and Switcher circuit pack missing (for DS3/STS-1 only) alarm points. A
working circuit pack reports the Protection path fail alarm point to inform the
craftsperson of protection problems.
Figure 2-8
Equipment alarm hierarchy
FW-2118
Circuit pack
missing
Circuit pack
mismatch
Circuit pack
fail
Example of a DS1 or DS3 equipment alarm

A failed DS1 VT mapper circuit pack is inserted by mistake into a slot
provisioned for a DS3 STS mapper. A Circuit pack mismatch alarm is raised;
the Circuit pack failure alarm is not raised because it is lower in the hierarchy.
Example of an OC-3 or OC-12 equipment alarm

On an OC-3 or OC-12 optical interface circuit pack, the optical laser and
photodetector fail. Two alarms are raised: an optical-laser failure alarm and an
OC-3 or OC-12 optical interface component failure alarm because the two
alarms are on the same level in the hierarchy.
Common equipment and environmental alarm hierarchy

The OPC, MIC and ESI, falling under the common equipment category, also
have three alarms and the hierarchy indicated in Figure 2-8. The processor
circuit pack is also considered a common equipment but does not have these
three alarms. The environmental alarms are all on the same level of hierarchy
and thus do not mask each other. Examples of these alarms follow.
Example of a common equipment alarm
A serial telemetry port failure is detected by the MIC and this alarm is raised.
There is then a failure on the MIC. The MIC Circuit pack fail alarm is
generated and the Serial telemetry port fail alarm disappears because it is
masked by the MIC failure alarm.
Example of an environmental alarm
An external alarm input (telemetry latch) is activated, but the alarm is not
reported because the MIC is missing. The telemetry latch alarm is raised as
soon as the MIC is inserted in the shelf. Alarm hierarchies (masking
relationships).
Automatic in service (AINS) alarm masking
The AINS feature allows customers to provision facilities and filter tributary
alarms which are raised when the facility is not immediately put into use.
The following tables indicate which facility alarms are masked by AINS.
Table 2-2
DS1 facility alarm masking
DS1 facility alarm AINS masking
Loopback no
Rx loss of signal yes
Rx bipolar violation>10E-3 yes
Rx loss of frame yes
Rx AIS yes
Rx yellow yes
VT Rx unequipped no
VT Rx loss of pointer no
VT Rx AIS no
VT Rx RFI no
STS1 Rx unequipped no
continued
Table 2-2 (continued)

STS1 Tx RFI no
STS1 Rx path trace failure no
STS1 signal label mismatch no
Table 2-3
Loopback no

Rx bipolar violation >10E-3 yes
Rx AIS yes
Frequency out of range yes
Rx parity error rate>10E-6 yes
Tx loss of frame yes
Tx AIS yes
STS1 Rx unequipped no
STS1 Rx RFI no
STS1 Rx path trace failure no
STS1 signal label mismatch no
Table 2-4
STS1 facility alarm masking
STS1 facility alarm AINS masking
Loopback no
Rx bipolar violation >10E-3 yes
Rx Line AIS yes

continued

STS1 facility alarm masking
STS1 facility alarm AINS masking
Rx RFI yes
STS1 Rx loss of pointer yes
STS1 Rx AIS yes
Table 2-5
OC3 facility alarm masking
OC3 facility alarm AINS masking

Loss of frame yes
Signal fail yes
Rx AIS yes
Line RFI yes
Signal degrade yes
STS1 Rx loss of pointer yes
STS1 Rx AIS yes
Table 2-6
Facility PM alert/alarm masking (see note)
PM alerts/alarms AINS masking
DS1 Path termination RX PM Alerts/Alarms yes
DS1 Line termination RX PM Alerts/Alarms yes
VT1.5 Path termination RX PM Alerts/Alarms no
DS3 Path termination RX PM Alerts/Alarms yes
DS3 Line termination RX PM Alerts/Alarms yes
DS3 Path termination TX PM Alerts/Alarms yes
STS1 Line termination RX PM Alerts/Alarms yes
STS3 Line termination RX PM Alerts/Alarms yes
OC3 Span termination RX PM Alerts/Alarms yes
Note: PM alarms, although masked by AINS, will be raised when AINS

completes if condition is still present.
Control architecture
All network elements within the same system are linked through the standard
SONET section, line, and path overhead (see Figure 2-9). The processor circuit
pack collects all the alarm information from the circuit packs, then converts
this information into the proper SONET overhead and makes available to the
surveillance interfaces. The processor also accepts the overhead information
from other network elements and makes it available to the local surveillance
interfaces.
Figure 2-9
Overhead layers
FW-0022
Path Line Line Path

Terminating Terminating Terminating Terminating
Equipment Equipment Equipment Equipment
Regenerator
(example: SONET
multiplexer) Terminal Tx
Rx
Section
Line
Path
(end-to-end)
(FW-0022)
3-1
How to begin trouble clearing 3-

This chapter provides information on fault-locating and clearing procedures
for the OC-3/OC-12 network element.
CAUTION
Risk of traffic loss
Ensure that the traffic has been rerouted through the protection
path before replacing any traffic-carrying circuit pack.
Refer to Chapter 1, Safety guidelines. The OC-3/OC-12

network element is a high-capacity system. Avoid interrupting
traffic or performing tasks without a valid reason.
To locate and clear a fault in an OC-3/OC-12 network element system, it is

recommended that you proceed as follows:
1 Log in to the OPC user interface and open the Alarm Monitor tool to see
one-line summaries of all active alarms in an OPC span of control.
Note: An asterisk (*) in the Time column of this tool indicates the alarm
occurred at least one day before the current date of the OPC.
2 From the active alarm list, identify the network element on which the
highest severity alarm has occurred, and determine from the Alarm
Monitors detail alarms which bay, shelf, and circuit pack is causing this
alarm.
Note 1: Some alarms on an OC-12 network can result from systems such
as OC-48, OC-192 or other vendors products. For example, for OC-48
terminals or add-drop multiplexers (ADM) nodes equipped with OC-12 or
STS-1 tributaries, you should examine the alarm status of the OC-12
network which feeds into, or is fed by, an OC-48 network.
3-2 How to begin trouble clearing
Note 2: Some alarms may not be visible either due to AINS alarm
masking, or being disabled. With AINS active, or with alarms disabled, an
alarm condition may be present, with no visible indication through alarms.
Refer to the following items for additional information:
If the AINS feature is active, it will mask a number of tributary-side
facility alarms. Refer to the section entitled Automatic in Service
(AINS) alarm masking in Chapter 2. Also refer to Procedure 2-28,
Checking the status of the automatic in-service feature for DS1, DS3,
OC3, and STS-1 facilities, in Provisioning and Operations
Procedures, 323-1111-310.
To display disabled alarms, see Procedure 2-3, Displaying disabled
alarms in Provisioning and Operations Procedures, 323-1111-310.
3 Clear the alarms one channel and one direction at a time starting with the
highest severity alarm. This might require a login to the network element
with the active alarm to execute commands locally on the network element
user interface. You might have to dispatch a person to the network element
site to perform maintenance procedures and circuit pack replacements.
Note 1: If communication through one or more user interfaces fails, the
maintenance interface controller (MIC) circuit pack might not be installed,
might require reseating, or might be faulty.
Note 2: When troubleshooting multiple faults in a ring configuration,
ensure that work is performed on only one network element at a time.
4 Refer to the detailed step-by-step procedures for clearing equipment,
facility, and environment alarms in this document.
Note: When clearing multiple alarms, you should be aware that one alarm
can mask or be masked by others.
This chapter describes the meaning of, and the possible cause of, trouble that
lights each circuit pack LED. See the chapter on LEDs for definitions of each
circuit pack LED and the lamps on the breaker interface panel (BIP).
The operations controller (OPC) provides additional tools (in the Network
Surveillance toolset) to monitor the status of the network elements in its span
of control, as follows:
The Network Browser tool is used to view the network status information
that includes alarm, protection, and performance data about all the network
elements.
The Network Alarm Summary tool is used to monitor alarms.
The Event Browser tool archives OPC logs, and OPC and network element
alarms and alerts. The Event Browser tool is aldo used to display or print
detailed information about individual events.
See Network Surveillance Procedures, 323-1111-510, for more information on

these tools used to track the network activity status.
Responding to logs
The OC-12 network element or the operations controller (OPC) generates
messages for a span of control that includes OC-12 network element. Logs
generated by the network elements can be viewed using the log utility of the
network element user interface. Logs generated by the OPC can be viewed
using the Event Browser tool on the OPC user interface.
Often, log messages require no action of maintenance personnel. However,

some logs are designed to provide supplemental information for certain alarms
or trouble conditions. Under such circumstances, it is noted in the appropriate
trouble-clearing procedure. As well, some trouble-clearing procedures request
that copies of the logs be retained for use by Nortel Networks to provide
further diagnostic support.
The OC-12 logs are listed and described in detail in the Log Report Manual,
323-1111-840. The log descriptions include detailed step-by-step procedures
for any logs that require action by maintenance personnel.
Procedure 3-1
Locating and clearing an alarm
Use this procedure to locate and clear alarms generated by the network
element.
Note 1: It is recommended that you locate and clear network element

alarms from the OPC rather than from the network element.
Note 2: Check for disabled or masked alarms. See Note 2: page 3-2.
Action
Step Action
1 Log in to the OPC, using the appropriate login method from the following
table:
If you are connected Then
directly to OPC port 1 go to step 2
to one of the network element user interface enter:
ports (1 and 2), have a network element user quit all
interface session running, and only one OPC is rlogin opc
configured
to one of the network element user interface enter:
ports (1 and 2), have a network element user quit all
interface session running, and a primary and listnodes
backup OPC are configured rlogin <nodename>
2 If you are connected directly to OPC port 1, log in to the OPC using the
netsurv userID and password (the default user password is netsurv) by
entering:
netsurv
<netsurv password>
Note 1: You can use other userIDs besides netsurv if these userIDs have
access to the Alarm Monitor tool, Event Browser tool, and NELogin Manager
tool.
Note 2: The password does not appear in the field when you type it. Do not
use capital letters unless the capitalization is part of the password, because
the system treats uppercase and lowercase letters differently.
continued
Procedure 3-1 (continued)

Step Action
3 Open the Alarm Monitor tool and observe any changes in the banner line
(changes are highlighted in the banner line). One-line alarm summaries
accompany these changes for all active alarms in an OPC span of control.
An Alarm Monitor tool displaying active alarms similar to the following
appears.
OS.0679
Alarm type and unit Severity and

(CE, DS1, DS3, COMM, STS-1, service code of
OC-3 or OC-12, REMT, the alarm
MIC, Proc, ESI, OPC)
Alarm point
Alarm Class (refer to the list of
(Fac, Eqp, or Env) OC-3/OC-12 TBM alarms)
(FW-26271)
>. Alarm Monitor Options

Critical Major minor warnng FailProt Lockout ActProt PrfAlrt
Network View . 1 2 1 . . . .
Alarms sorted by severity [*] Auto Update List

Showing: All Severities, ALL NEs, OPC
NE# NE Name Alm# Cls Sh Unit Reason Time Sev
103 - 71 Fac 1 DS3 G1 1 Rx loss of signal 12:48:42* M,SA
103 - 70 Env 1 CE Telemetry Input 1 08:38:57 m,nsa
100 - 16 Env 1 CE Telemetry Input 1 08:38:35 m,nsa
100 - 70 Eqp 1 OC12 G1 Protection switch 22:00:06* w,nsa
C 0 M 1 m 2 w 1 FailProt 0 Lckt 0 ActProt 0 PrfAlrt 0 08:39
Note: Alarms are normally shown in decreasing order of severity (Critical,

Major, minor, and warning). These alarms can be sorted and filtered
according to severity and network element. For more information on the
functionality of the Alarm Monitor, see Network Surveillance Procedures,
323-1111-510.
continued

Step Action
4 Starting with the alarm with highest severity, move to the alarm you want to
select by using the arrows keys and then select the alarm by pressing Space
(or Keypad 0).
The selected alarm appears in reverse video.
5 Display the List item menu by pressing Ctrl_L (or Keypad Enter).
The menu appears.
6 Move to the Details command, and select it by pressing Space (or Keypad 0).
A dialog with detailed alarm information similar to the following appears.
OS.0677
Alarm Details
Alm#: 180 Sev: Major

Unit: DS3 G2 Imp: SA
Address: 642 Shelf 1 Time: 12:43:25
Location: Frame ShPos Slot 4 Subslot 2 Date: 26 Feb 92
Reason: Rx loss of signal Cls: Facility
FacilityID:
[ Done Return] [ Print Details ]
This dialog provides all the information related to the selected alarm,
including the failed circuit pack, the failed network element (address), the
location of the circuit pack, the time and date of the failure, and the reason
(alarm point definition).
7 To find the appropriate trouble clearing procedures in this NTP, identify the
alarm class (Cls), alarm type (Unit), and alarm name (Reason) from the
Alarm Details screen.
In the preceding figure, the alarm class is Facility, the alarm type is DS3, and
the alarm name is Rx loss of signal.
8 Go to the list of alarms at the beginning of Chapters 4, 5, or 6 (or go to the
table of contents) and find the procedure to clear the alarm. These
procedures are listed in alphabetical order by alarm class, type, and name.
9 Turn to the page on which the alarm clearing procedure starts and follow the
step-by-step procedure to clear the alarm.
If the alarm clearing procedure Then go to

requires an NE login step 10
does not require an NE login step 13
continued

Step Action
10 To log in to a specific network element from the Alarm Details dialog, return
to the User Session Manager window by doing the following:
a. Tab to Done button, and select it by pressing Ctrl_A (or Keypad 0).
b. Display the Window menu by pressing Ctrl_L W (or Keypad 6).
c. Display the List menu by pressing Ctrl_L (or Keypad Enter).
11 Open the NE Login Manager tool and log in to the required network element.
If you do not know how to do this, see the procedure in Common Procedures,
323-1111-846.
Once you are logged in to the network element user interface a summary of
alarms and protection counts appears at the top of the display.
OS.0316
Critical Major minor warning FailProt Lockout ActProt PrfAlrt

Network View . . . . . . . .
St.Johns . . . . . . . .
S/DMS Nodes 64000.32000.44851
0 Quit Network Element Status Shelf: 1
2 SelectNE
3 Alarms NE ID Alarms Protection Prf
4 ListNEs Fac Eqp Env Fail Lckt Act Alrt
5 44851 St.Johns . . . . . . .
6 PerfMon
7 FWPUI:
8 WARNING: This computer system may be accessed only by authorized
9 users. The data and program in this system are private,
10 Protectn proprietary, confidential and protected by copyright law and
11 international treaties. Unauthorized access, use, knowledge,
12 duplication, reproduction, modification, distribution,
13 retransmission, download or disclosure of any of the data and
14 programs in this system or any portion of it may result in severe
15 Equipmnt civil and criminal penalties and will be enforced/prosecuted to
16 Facility the maximum extent possible under law. Employees or other Company
17 Admin authorized users exceeding their authorizations subject
18 Help themselves to Company initiated disciplinary proceedings.
NE 44851
Time 15:06 >
12 Log out of network element user interface and return to the User Session
Manager window.
323-1111-846.
continued

Step Action
13 After clearing the alarm, verify the status of the alarm and review the list of
historical alarms on all network elements in an OPC span of control and the
OPC event logs using the Event Browser.
From the User Session Manager window, open the Event Browser.
323-1111-846. For more information on how to use the Event Browser tool,
see Network Surveillance Procedures, 323-1111-510.
The following is an example of the Event Browser showing historical network
element alarms and OPC events.
OS.0676
FW 20363
>. Event Browser
Event sorted by time [ Update List ]

Showing: logs, alarms, alerts, all sev, and all NEs
NE # NE Name Evt# Cls Unit Reason Date Time Sv
0 OPC 292 Stat log COM501 OPC to NE 12 17 Jul 15:34:10 w
0 OPC 291 Stat log COM502 OPC to NE 12 17 Jul 15:33:40 M
0 OPC 290 Trbl log NAD351 Cannot colle 17 Jul 15:12:52 m
0 OPC 289 Comp log GEN618 Log/Alarm da 17 Jul 15:06:20 w
0 OPC 287 Comp log GEN618 Loc/Alarm da 17 Jul 14:43:32 w
0 OPC 284 Stat log COM502 OPC to NE 12 17 Jul 14:31:09 M
14 If you have completed a specific alarm clearing procedure and the alarm point
is still active, follow the product and trouble escalation support instructions in
this document.
See Network Surveillance Procedures, 323-1111-510, in conjunction with
this document for more information on specific network element user
interface commands.
end
Procedure 3-2
Performing an alarm cutoff (ACO)
Use this procedure to perform an alarm cutoff (ACO) on the selected shelf.
Note: The alarm cutoff can also be performed by pressing the ACO button
on the network elements local craft access panel (LCAP).
Requirements
Before starting this procedure, you must:
be logged on the network element user interface and be at the main menu
level
be familiar with the VT100-type network element user interface. See
Common Procedures, 323-1111-846Common Procedures, 323-1111-846.
Action
Step Action
1 Access the Shelf Equipment screen and select the shelf by entering:
equipmnt sh
The Shelf Equipment screen appears with the selected shelf.
2 Perform an alarm cutoff by entering:
aco
continued

Performing an alarm cutoff (ACO)
Step Action
A screen similar to the following appears when an alarm cutoff is performed

for a network element.
OS.0088
FW 1712 (R11)

Network View . . . . . . . .
St. Johns . . . . . . . .
Shelf Equip 1.1.63
0 Quit Shelf Equipment Shelf: 1
2
3 Location: <1234567>
4 Shelf Position: <1>
5 Inventry Shelf Type: OC12 TBM VTM RingADM
6 ListCpks Shelf Function: < >
7 LampTest Serial Number: A240404906 Exerciser: Off
8 BackupDB NE Clock Source: ESI Shelf Date: 15 Jan 95
9 Restore GMT Offset (minutes): < 0> Time Zone: GMT
10 Restart
11 Edit ACO
12 The ACO command has been received. It will be processed.
13
14
15 ACO
16 Exercise
17 AlmProv
18 Help
NE 63
Time 18:24 >
end
Procedure 3-3
Clearing the alarm condition: PROC red fail LED lit
Probable cause
The probable causes of this alarm are as follows:
faulty processor circuit pack (Proc)
Proc rebooting or initializing
faulty maintenance interface controller (MIC) circuit pack
Impact
The MIC and Proc circuit packs control the DS1/DS3/STS-1 protection
switching. If a DS1 or DS3 mapper or an STS-1 electrical interface circuit pack
fails while the red LED on the Proc is active, the live traffic does not switch to
the protection mapper. No OAM&P functions can be performed until the Proc
has rebooted or has been replaced.
Action
Step Action
1 Log in to the network element user interface at the site of the Proc failure.
Note: If you cannot log in to the network element user interface, log in to
another network element in the same span of control. Select the network
element with the Proc failure by entering:
rlogin ne <ne id>
where
<ne id> is the number of the network element with a failed Proc.
When prompted, enter the userid and password.
If you cannot log in locally or remotely, go to step 4.
2 List all alarms by typing:
alarms
Clear all alarms using the standard trouble-clearing procedures in Chapters
4, 5, and 6 of this document.
If the red fail LED remains active, go to step 3.
Note: Some alarms may not be visible either due to AINS alarm masking, or
being disabled. With AINS active, or with alarms disabled, there may be a
traffic loss with no alarms.
continued

Clearing the alarm condition: PROC red fail LED lit
Step Action
3 Restart the Proc software by entering:

equipmnt sh
restart
yes
The user interface session terminates as the software restarts.
Note: Wait 5 minutes before performing any operations through the user
interface. After 5 minutes, the user interface reflects the true condition of the
shelf. If you use the user interface before the 5 minutes have elapsed,
response times might be delayed and operations might be held pending for a
longer period of time than usual.
4
CAUTION
Avoid touching any components on the printed circuit
board. Electrostatic-sensitive devices can be damaged
by electrostatic discharge. Always ground yourself
before handling the circuit pack.
If the Proc red fail LED is still active, reseat the Proc circuit pack.
Reseating the Proc circuit pack sends a request for new software to the OPC.
The software is downloaded from the OPC over the SONET DCC channels
(remotely) or over the CNet Bus (if the primary OPC is connected to the local
shelf by CNet).
Note: While software is rebooting, network element visibility is lost and
low-speed switching is not available. Software download time varies from 3 to
30 minutes, depending on the location of the OPC.
5 If the red fail LED is still active, replace the Proc circuit pack. See Module
Replacement Procedures, 323-1111-547, for replacement instructions.
end
Procedure 3-4
Performing a manual diagnostic test
Use this procedure to manually run a diagnostic test on any of the following
circuit packs:
processor (Proc) circuit pack
maintenance interface controller (MIC) circuit pack
OC-12 VTM circuit pack
Note: Do not use this procedure on an OC-12 NWK circuit pack.
Diagnostics can be run on an in-service or out-of-service circuit pack.
Out-of-service diagnostics are more extensive than in-service diagnostics.

Results of a manual diagnostic test appear in log report EQP609.
Requirements
Before starting this procedure, you must:
be logged on the network element user interface and be at the main menu
level
familiarize yourself with the VT100-type network element user interface.
See Common Procedures, 323-1111-846Common Procedures,
323-1111-846.
Action
Step Action
1 Access the equipment screen and display the equipment status by entering:
equipmnt <equipment type> <unit>
where
<equipment type> is oc12, proc, or mic
<unit> (circuit pack group) is g1 or g2
Note: Circuit pack group is not required
for proc or mic.
The equipment screen showing the equipment status is displayed.
continued

Performing a manual diagnostic test
Step Action
2 Begin the manual diagnostic test by entering:

diagnose
The system displays the following response:
The diagnostics may take some time.
Do you want to continue?
Please confirm (Yes or No):
3 Continue with the diagnostic test by entering:
yes
Cancel the test by entering:
no
The results of the manual diagnostic test appear in log report EQP609.
4 View the log report by entering:
admin nep
logs
open eqp
end
Procedure 3-5
Manually clearing OPC alarms
Use this procedure to manually clear alarms generated by the OPC after you
have corrected the cause of the alarm but before the alarm automatically clears.
Alarms clear automatically 1 to 2 minutes after you correct the cause of the
alarm. If you clear an alarm manually without resolving the cause of the alarm,
the alarm becomes active again after any applicable hold-off period.
You can display OPC alarms using the OPC Alarm Monitor or Event Browser
tools.
Requirements
Before starting this procedure, you must log in to the OPC with access
privileges for the OPC Alarm Provisioning tool. For log-in instructions and an
overview of the OPC user interface, see Common Procedures, 323-1111-846.
Action
Step Action
1 From the User Session Manager, open the OPC Alarm Provisioning tool by
moving the cursor to the tool name and pressing Ctrl_A (or Keypad 0).
The OPC Alarm Provisioning main window appears.
OS.0680
> OPC Alarm Provisioning Utilities

Showing: OPC pointer alarm
NE for Prim. OPC NE for Back. OPC Reason Severity STA
- - OPC alarm(s) active minor OFF
Showing: all OPC alarms

Reason Severity Status(STA)
Lost peer OPC minor ON
Below-baseline CP exists in the system minor ON
Configuration audit fail minor ON
Connection audit fail minor ON
Tape backup/restore fail minor ON
Datasync fail minor ON
NE DB missing/outdated minor ON
2 Tab to the list of all OPC alarms.

3 Use the arrow keys to move to the alarm you want to clear.
continued

Manually clearing OPC alarms
Step Action
4 Display the list item menu by pressing Ctrl_L (or Keypad Enter).
The list item menu appears.
OS.0681
> OPC Alarm Provisioning Utilities
Showing: OPC pointer alarm
NE for Prim. OPC NE for Back. OPC Reason Severity STA

4286 4287 OPC alarm(s) active minor OFF
Showing: all OPC alarms

Reason Severity Status(STA)
Lost peer OPC minor ON
Below-baseline CP exists in the system
1 Change state minor ON
Configuration audit fail 1 Inhibit
minor (OFF) ON
2 Manual clear
Connection audit fail 2 Enable
minor (ON) ON
Tape backup/restore fail 3 Select minor ON
Datasync fail 4 Deselect minor ON
NE DB missing/outdated minor ON
5 help H
5 Use the arrow keys to move to the Manual clear command and select it by
pressing Space (or Keypad 0).
A confirmation dialog appears.
FW-26446
FW-
You are about to manually clear the OPC alarm.
Do you wish to continue?
[Yes Return ] [No - ]
6 Tab to the Yes button and select it by pressing Ctrl_A (or Keypad 0).
7 If you are displaying the alarm in the OPC Alarm Monitor or Event Browser
main window, refresh the screen display to show that the alarm status has
now changed.
8 Close the tool by pressing Esc ).
end
4-1
Clearing equipment alarms 4-

This chapter describes how to clear Transport Bandwidth Manager (TBM)
equipment alarms using the network element user interface.
Note 1: See Provisioning and Operations Procedures, 323-1111-310, for

procedures that include the following: provisioning alarms;
activating/deactivating (placing in /out of service) and adding/deleting
facilities and circuit packs; operating or releasing loopbacks; and
managing OC-12 rings and setting up STS connections at the OPC.
Note 2: See Protection Switching Procedures, 323-1111-311, for
procedures that include operating or releasing lockouts, and operating or
releasing forced and manual switches.
Note 3: A trouble clearing procedure might call for a circuit pack to be
replaced. For the MIC, removal of the circuit pack causes a loss of access
to the user interfaces, and the current user process is stopped.
Note 4: See Common Procedures, 323-1111-846, for procedures that
include connecting to and using the network element user interface.
Note 5: The service code provided in the impact section of the alarm
clearing procedures is the normal service code. When any alarm is
generated, the software determines if the alarm is service affecting and
under certain rare circumstances the software displays a different service
code than the one documented. Under these rare circumstances, the
software provides the correct service code and you should disregard the
documented service code.
4-2 Clearing equipment alarms
List of equipment alarms

Eqp CE (shelf) alarms
Alarm Page
Autoprovisioning mismatch 4-19
CNET link fail 4-20
CNET performance degraded 4-22
Critical test alarm 4-23
Database not restored. Type Q APPROVE at NE 4-24
Datacomm access violation 4-33
Duplicate NE name 4-34
Duplicate NE numeric identifier 4-35
Exerciser fail 4-37
Major test alarm 4-23
Manual area address dropped from area 4-38
Minor test alarm 4-23
NE database backup to OPC failed 4-41
Node count limit is exceeded 4-42
PM threshold capping active 4-43
Ring reconfiguration in progress 4-44
Shelf assembly fail 4-45
Shelf id bus fail 4-46
Software trap 4-47
SONET overhead data/clock loss 4-48
Traffic upgrade in progress 4-50
Warning test alarm 4-23
Eqp DS1 alarm
Alarm Page
Facility provisioning mismatch 4-56
Input card fail -DoNotRemove 4-58
Input card mismatch 4-59
Input card missing 4-60

Output card fail -DoNotRemove 4-58
Output card mismatch 4-59
Output card missing 4-60

Protection version mismatch 4-73
Eqp DS3 alarm
Alarm Page



Protection hardware incompatible 4-104
Eqp ESI alarms
Alarm Page
End VCO range 4-105
Equipment forced switch request 4-106
Equipment lockout request 4-107
Equipment manual switch request 4-108
Equipment protection switch complete 4-109
Equipment protection switch fail 4-111
Failure to lock 4-112
Intercard fail 4-113

Subunit fail 4-115
Subunit mismatch 4-116
Subunit missing 4-117
Timing generation entry to acquire 4-118
Timing generation entry to fast 4-119
Timing generation entry to freerun 4-120
Timing generation entry to holdover 4-121
Eqp Lpbk (loopback) alarms
Alarm Page
LpbkG1 Automatic firmware download in progress 4-122

LpbkG1S Automatic firmware download in progress
Intercard cntrl: G1 to LpbkG1S 4-123
Intercard cntrl: G1S to LpbkG1 4-145
Intercard cntrl: LpbkG1 to G1 4-168
Intercard cntrl: LpbkG1 to LpbkG1S 4-191
Intercard cntrl: LpbkG1S to G1S 4-179
Intercard cntrl: LpbkG1S to LpbkG1 4-191

LpbkG1 Circuit pack failed 4-204
LpbkG1 Circuit pack mismatch 4-206
LpbkG1 Circuit pack missing 4-207
LpbkG1 firmware version mismatch 4-208
LpbkG1 firmware/software incompatible 4-209
LpbkG1 Maps invalid or missing 4-211
LpbkG1 protection switching byte fail 4-212
LpbkG1 STS1 intercard fail 4-213
LpbkG1S Circuit pack failed 4-204
LpbkG1S Circuit pack mismatch 4-206
LpbkG1S Circuit pack missing 4-207
LpbkG1S firmware version mismatch 4-208
LpbkG1S firmware/software incompatible 4-209
LpbkG1S Maps invalid or missing 4-211
LpbkG1S protection switching byte fail 4-212
LpbkG1S STS1 intercard fail 4-213
OHB card missing 4-207
Ring protection suspended or unavailable 4-215
Eqp MIC alarms
Alarm Page
Alarm relay fail 4-217
E2A input fail 4-217
LED driver fail 4-217
Local craft interface port fail 4-217

Non-volatile store fail 4-223
Non-volatile store mismatch 4-224
Orderwire fail 4-217
Parallel telemetry relay fail 4-217
Protection switch relay fail 4-225
Serial telemetry port fail 4-217

Time of day clock fail 4-217
Eqp OC3/OC12 alarms
Alarm Page
Channel match fail 4-226
Circuit pack reach mismatch 4-230
Fiber connection error 4-231

Laser bias current 4-238
Laser degrade 4-239
Lockout protection operation fail 4-240
Protection oscillation control activated 4-243

Protection scheme mismatch 4-246

Protection switching byte fail/Improper APS code 4-253
Receive fail 4-254
Switch mode mismatch 4-257
Transmission rate mismatch 4-258
Transmit fail 4-259
Eqp OC12 alarms
Alarm Page
Default K Bytes 4-263
Entry to SONET clock acquire 4-264
Entry to SONET clock holdover 4-266
Fiber loopback 4-268
Firmware corrupt 4-269

Firmware trap 4-272
Intercard cntrl: G1 to LpbkG1 4-275
Intercard cntrl: G1S to LpbkG1S 4-287
Intercard serial link fail 4-298
Invalid neighbor detected 4-300
Lockout protection request 4-302
Lockout working request 4-303

Maps invalid 4-304
NE id mismatch 4-306
Protection switching byte/APS code inconsistent 4-309

Reference input clock fail 4-310
STS12 ring link parity error 4-311
Synchronization clock fail 4-314
System clock reference fail 4-315
Eqp OPC alarms
Alarm Page
OPC alarm(s) active 4-317
OPC circuit pack fail 4-318
OPC circuit pack mismatch 4-319
OPC circuit pack missing 4-320
OPC CNET loss of signal 4-321
OPC Ethernet loss of signal 4-322
OPC hardware reset 4-324
OPC OAM software fail 4-325
Eqp Proc alarms
Alarm Page
Both C-Bus access fail 4-327
C-Bus-A access fail 4-328
C-Bus-B access fail 4-329
Communication processor fail 4-330
Degraded communication processor 4-331
Degraded host processor 4-332
Degraded master CBIC-A 4-333
Degraded master CBIC-B 4-333
Firmware prom fail 4-334
Eqp REMT alarms
Alarm Page
Remote critical 4-337
Remote major 4-338
Remote minor 4-339
Remote subnetwork 4-340
Eqp STS1 alarms
Alarm Page

Firmware failure 4-348


Reference tables: Circuit pack group identification

Table 4-1 on page 4-13 to Table 4-5 on page 4-17 provide circuit pack group
(unit) identification as follows:
Table 4-1: Circuit pack group identification for TBM terminal shelf
Table 4-2: Circuit pack group identification for TBM linear ADM shelf
Table 4-3: Circuit pack group identification for TBM NWK ring ADM shelf
Table 4-4: Circuit pack group identification for TBM VTM ring ADM shelf
Table 4-5: Circuit pack group identification for TBM regenerator shelf
Note: When a procedure indicates that you should enter the circuit pack
group, enter a specific group such as G1, or enter all to select all circuit
pack groups of that type.
Table 4-1
Circuit pack group identification for TBM terminal shelf
Slot Circuit pack groups
OC-3 OC-3 DS1 DS3 ESI Proc MIC OPC
OC-12 tributary STS-1
STS-12
transport
1 G3 G1 P (for DS3) G1
2 G2
3 G4 G3 P (for STS-1)
4 G4
5 G1S G2
6
7 G2S
8
9 G1
10 G2
11 G5 G5 G1 G4
12 G6
13 G6 G7 G2
14 G8
15 G7 G9 G3 G5
16 G10 G6
17 G8 G11 G4
18 G12
19 P
20 See
Note
21 A
22
23 G1 (upper)
G2 (lower)
Note: The maintenance interface controller (MIC) circuit pack does not carry a circuit pack group
number.
Table 4-2
Circuit pack group identification for TBM linear ADM shelf
STS-12
transport
2 G2
4 G4
5 G1S
6
7 G2S
8
9 G1
10 G2
11 G5 G5 G1 G4
12 G6
13 G6 G7 G2
14 G8
15 G7 G9 G3 G5
16 G10 G6
17 G8 G11 G4
18 G12
19 P
20 See
Note
21 A
22
23 G1 (upper)
G2 (lower)
number.
Table 4-3
Circuit pack group identification for TBM NWK ring ADM shelf
OC-12 Loopback OC-3 DS1 DS3 ESI Proc MIC OPC
STS-12 tributary STS-1
transport
2 G2
4 G4
5 G1S
6
7 LpbkG1S
8
9 G1
10 LpbkG1
11 G5 G5 G1 G4
12 G6
13 G6 G7 G2
14 G8
15 G7 G9 G3 G5
16 G10 G6
17 G8 G11 G4
18 G12
19 P
20 See
Note
21 A
22
23 G1
(upper)
G2
(lower)
number.
Table 4-4
Circuit pack group identification for TBM VTM ring ADM shelf
transport tributary STS-1
(See Note) (See Note)
2 G2
4 G4
5 G1S G2
6
7 G2S
8
9 G1
10 G2
11 G5 G5 G1 G4
12 G6
13 G6 G7 G2
14 G8
15 G7 G9 G3 G5
16 G10 G6
17 G8 G11 G4
18 G12
19 P
20 See
Note
21 A
22
23 G1 (upper)
G2 (lower)
number.
Table 4-5
Circuit pack group identification for TBM regenerator shelf
OC-12 OPC Proc MIC

transport
1 G1
5 G1W
6
9 G1E
10
11 G4
12
13
14
15 G5
16 G6
17
18
19
20 See
Note
21 A
22
23
Figure 4-1
Installing a circuit pack in a shelf
FW-3035
(FW-3035)
Note 1: Always hold a circuit pack by its latches.
Note 2: To install a circuit pack, insert it into the tracks located in the appropriate
shelf slot. To connect the circuit pack, keep both latches open and push the circuit
pack all the way into the shelf until you feel the circuit pack engage the backplane
connector. Close both latches. To leave the circuit pack unconnected, close both
latches and push the circuit pack until the latches are flush with the shelf.
Note 3: To remove a circuit pack from a shelf, open both latches and pull the circuit
pack out of the shelf.
Eqp CE
Autoprovisioning mismatch 4
Probable cause
The circuit pack is not valid for the slot in which it has been inserted. Rules for
provisioning were not followed.
Note: See the appropriate chapters on provisioning in Provisioning and

Operations Procedures, 323-1111-310 for provisioning guidelines,
restrictions/limitations, and provisioning procedures.
Impact
This is a minor, not service-affecting (m, nsa) alarm.
Action
Step Action
1 Remove the circuit pack from the slot specified in the alarm.
2 Refer to Circuit pack groups and COMM SDCC ports in Provisioning and
Operations Procedures, 323-1111-310, for valid circuit packs and
configurations.
end
Eqp CE 40
CNET link fail 4
Probable cause
The processor circuit pack can no longer communicate through the control
network (CNet) with any other processor circuit pack or operations controller
(OPC). One of the following conditions exists:
a defective processor circuit pack
a defective or disconnected CNet cable or terminator
other defective processor circuit pack or OPC that are connected to this
processor circuit pack through CNet cables or the backplane. The alarm
will not be raised if the processor circuit pack can communicate with at
least one other Proc or OPC.
a defective or missing maintenance interface controller (MIC) circuit pack
an overloaded LAN whose physical limits have been exceeded
Note: This alarm is disabled by default.
Impact
Action
Step Action
1 Verify that there is at least one OPC and one NE, or two NEs on the CNet
LAN.
Do the following:
If Then
no other OPCs or deprovision the alarm. See the procedure for enabling
NEs are available and disabling facility alarms in Provisioning and
Operations Procedures, 323-1111-310.
other OPCs or NEs go to step 2
are available
2 Verify the intershelf CNet cables and the CNet cables connections. Ensure
that all nodes on the CNet LAN are properly terminated. Refer to Installation
Procedures, 323-1111-201, for instructions to properly install CNet cables
and terminate nodes on the CNet LAN.
continued
Eqp CE
CNET link fail (continued)
Step Action
3 Determine which other OPCs or NEs are connected to this shelf through the
CNet. Verify that none of them has failed. Replace the defective processor
circuit pack. See the procedure for replacing the processor circuit pack
(NT4K52) in Module Replacement Procedures, 323-1111-547.
4 Check and resolve the CNet error statistics and the CNet
performance-monitoring statistics for the network element according to the
procedures in System Testing Procedures, 323-1111-222.
5 If the alarm persists, contact your next level of support or your
Nortel Networks support group. See About the OC-3/OC-12 NETBM
Library, 323-1111-090.
end
Eqp CE 40
CNET performance degraded 4
Probable cause
Control network (CNet) performance is degraded because of defective LAN
cabling or connections.
Impact
This is a warning, not service-affecting (w, nsa) alarm.
Action
Step Action
1 Verify that all CNet connectors are either terminated or are connected to
another shelf with a cable. Correct any problem with the CNet cables. Refer
to Installation Procedures, 323-1111-201, for instructions to properly install
CNet cables and terminate nodes on the CNet LAN.
2 Verify and correct any hardware problems in the other processor circuit
packs or operations controllers (OPC) on the LAN such as CNet hardware
fail alarms or CNet logs.
3 Verify that the CNet engineering limits have not been exceeded. These limits
are specified in Technical Specifications, 323-1111-180.
4 Check and resolve the CNet error statistics and the CNet
performance-monitoring statistics for the network element according to the
procedures in System Testing Procedures, 323-1111-222.
5 If no problems are found, contact your next level of support or your
Library, 323-1111-090.
end
Eqp CE 40
Critical test alarm
Major test alarm
Minor test alarm
Warning test alarm 4
Probable cause
A craftsperson is testing the alarm using the CI tool FWALTSCI.
Impact
These are not service-affecting (nsa) alarms.
Note: When raised, these alarms test the critical, major, minor, or warning
alarm reporting system.
Action
Step Action
1 Clear the alarm from the CI tool FWALTSCI.

end
Eqp CE 40
Database not restored. Type Q APPROVE at NE 4
Probable cause
The network element attempted a software recovery without an available
database.
Note: This alarm cannot be inhibited.
Impact
This is a major, not service-affecting (M, nsa) alarm.
The situation of having a node attempt a software recovery without a database

available represents a serious condition. This problem requires prompt
addressing since it is potentially service affecting. The tributary protection
(DS1, DS3, STS-1, and OC-3) is not available while this condition exists.
The Approve command applies to situations in which the node has attempted
software recovery without a valid database. This means that the database was
either corrupted, or not available.
The Database not restored alarm reflects a node waiting for approval to
autoprovision all parameters to default values. Prior to the Approve,
parameters can be set to the appropriate non-default values without impacting
traffic.
The Database not restored alarm represents a serious condition and needs to be
addressed promptly, as there is a potential for service to be affected.
Low-speed (DS1 and DS3) protection is not available while this condition
exists. When this condition exists, an up-to-date database for the node may be
restored from tape to the OPC and then the node rebooted. Alternatively, all
service-affecting parameters may be re-edited and the Approve command
used.
Action
To clear the alarm, follow one of the three following procedures.
Procedure A uses the database on the backup OPC. This procedure is the
preferred procedure to follow and is safer than Procedure B if the backup to
tape or cartridge was performed long ago.
Procedure B uses a tape or cartridge backup from the OPC. The tape or
cartridge must contain the current settings for the service-affecting parameters.
continued
Eqp EC
Database not restored. Type Q APPROVE at NE (continued)
Procedure C uses the Approve command, and must be used only if procedures
A and B cannot be performed.
Note: Do not perform Procedure C on an in-service node. The Approve

command will affect traffic. Procedure C must be performed under the
direction of your Nortel Networks support group. Type Q APPROVE at the
alarmed network element to find out more about this command and if it is
applicable to your situation.
Procedure A
Ensure that the two following conditions are met before performing this
procedure:
a backup OPC must exist
a valid NE database for the NE in question must exist on the backup OPC
If these conditions are met, switch to the backup OPC and have the backup
OPC send the NE database to the NE.
Step Action
1 Log in to the OPC using a root or admin userID and open the UNIX shell tool.
If you do not know how to do this, see the procedures in Common
If you log in as Then
root the UNIX prompt opc> appears.
Go to step 2.
admin the User Session Manager appears. Select the UNIX shell
tool in the Available tools list by pressing Ctrl_A (or
Keypad 0). The UNIX prompt opc> appears.
Go to step 2.
2 At the UNIX prompt, display the activity switching screen by entering:

ows_swact
The activity switching screen appears. The left side of this screen displays the
current state of the primary and backup OPCs, indicates whether revertive
switching is turned on, whether activity switching is enabled, and whether the
backup OPC is locked in an inactive state. It also reports on the state of the
connections between the OPC, and if a data synchronization or network
upgrade is in progress. The right side of the screen lists available command
options.
continued
Eqp CE
Step Action
The following options are available:

a make the local OPC active and the peer OPC inactive
i make the local OPC inactive and the peer OPC active
p prevent users from switching activity by disabling forced switch
e enableallow users to switch activity by disabling forced switch
l put the local backup OPC into an inactive state (using release lock
or rebooting the OPC unlocks the OPC from lock inactive state
r release the local backup OPC inactive lock

c cancelcancel any active switch
d debugturn debug on
v verboseshow all messages
h helphelp menu appears and the program terminates without

forcing any active switch
q quit
FW-21789
FW-21789
OWS_SWACT OPTIONS
The local Primary OPC OPC140PP is ACTIVE a: Force local OPC Active
No Peer is commissioned i: Force local OPC Inactive
Revertive Switching is ON p: Prevent Forced Switching
Connection between OPCs is BAD e: Enable Forced Switching
Data Sync is not in progress l: Lock Backup OPC Inactive
Network Element Upgrade is not in progress r: Release Inactive Lock
Peer Backup OPC lock status unkown c: Cancel Activity Switch
Activity Switching is Enabled u: Enter Upgrade Mode
s: Exit Upgrade Mode
Debug is OFF Verbose is OFF d: Toggle debug
v: Toggle verbose
h: Help
q: Quit
<ENTER>: Refresh screen
OPCs are NOT available to switch activity. Check statuses
Enter Command>
C0 M3 m1 w0 FailProt 0 Lckt 0 ActProt 0 PrfAlrt 0 13:32
continued
Eqp CE
Step Action
Note 1: Command options can be entered as parameters of the ows_swact

command. If you do not need to look at the settings on the activity switching
screen, you can enter the ows_swact in step 2 followed by a space, hyphen,
and a, i, p, e, l, or r. (Do not enter a space between the hyphen and the
option.) For example, to make the primary OPC active and the backup OPC
inactive, type ows_swact -a .
Note 2: To enable debug, verbose, or both, using the ows_swact command,
enter d, v, or both before your selected option. Do not enter a space between
the hyphen and your selected options. For example, to enable debug and
verbose and make the primary OPC inactive and the backup OPC active, type
ows_swact -dvi .
Note 3: When using the ows_swact command, entering d, v, or both after the
a, i, p, or e options nulls the debug or verbose request. Therefore, always
ensure the d or v options are entered before the a, i, p, or e options when
using the ows_swact command.
3 Ensure that activity switching is enabled and that the backup OPC is not
locked inactive. If activity switching is disabled or the backup OPC is locked
inactive contact your next level of support to determine if you are permitted to
change these options. If you are permitted to change these options complete
the appropriate steps referenced in the following table.
If Then go to
you need to enable activity switching step 4
you need to unlock the backup OPC step 6
the settings are correct step 8
4 Enable activity switching by entering:

e
The following prompt appears.
Are you sure you want to Enable Force Activity Switching?
5 Confirm by entering:
y
The following message appears.
Enabling Force Activity Switch
ows_swact command Successful
The UNIX prompt appears. The status information on the activity switching
screen is also updated.
Go to step 2.
continued
Eqp CE
Step Action
6 Unlock the backup OPC by entering:

r
Releasing local Backup OPC from Inactive Lock will allow
it to return to its normal state.
Are you sure?
y
Releasing Backup OPC from inactive state
The UNIX prompt appears. The status information on the activity switching
Go to step 2.
8 Determine the state of the primary OPC.
If the primary OPC is Then go to
active step 9
inactive step 13
9 Force the primary OPC into an inactive state by entering:

i
Are you sure you want the local OPC INACTIVE and the peer
ACTIVE?
y
Verification Successful.
Switching OPCs Activities
The UNIX prompt appears. The backup OPC becomes active and the primary
OPC becomes inactive. The status information on the activity switching
11 Perform an NE database restore on the affected NE. If you do not know how
to do this, see the procedure on restoring a network element database in
Data Administration Procedures, 323-1111-304.
continued
Eqp CE
Step Action
12 Perform a shelf reload restart. If you do not know how to do this, see the
procedure on performing a shelf restart in Provisioning and Operations
13 Force the primary OPC into an active state by entering:
a
Are you sure you want the local OPC ACTIVE and the peer
INACTIVE?
y
Verification Successful.
Switching OPCs Activities
The UNIX prompt appears. The primary OPC becomes active and the backup
OPC becomes inactive. The status information on the activity switching
15 Perform an NE data base backup. If you do not know how to do this, see the
procedure on performing an NE data base backup in Data Administration
continued
Eqp CE
Procedure B
This procedure requires that the last backup to tape or cartridge of the OPC
(DDS) contain the current settings for the service-affecting parameters. If any
service-affecting parameters have been changed since the last tape or cartridge
was made, use Procedure C.
CAUTION
Traffic loss can occur if the backup tape or cartridge does not
contain the current settings for service-affecting parameters.
Step Action
16 Verify that no service-affecting parameters have been updated since the last
OPC Save to tape or cartridge procedure was performed. If the tape or
cartridge does not reflect the current parameters, do not complete Procedure
B; use Procedure C instead.
17 Restore the OPC from the last backup tape or cartridge. See Data
Administration Procedures, 323-1111-304, for the OPC Restore from tape or
cartridge procedures.
18 Perform a shelf reload restart. See the procedure for performing a shelf
restart in Provisioning and Operations Procedures, 323-1111-310.
Library, 323-1111-090.
continued
Eqp CE
Procedure C
This procedure uses the Approve command. This command is used to indicate
that all equipment and facility parameters have been verified as correct, and are
approved for use on the hardware. Do not issue the Approve command until all
parameters are corrected. Issuing the command before parameters are
corrected will affect service.
CAUTION
Do not perform Procedure C on an in-service node. The
Approve command will affect traffic. Contact your next level
of support or your Nortel Networks support group before
issuing the Approve command.
Step Action
20 Perform a manual edit of all service-affecting parameters. See System

Administration Procedures, 323-1111-302, for the procedures to edit
parameters.
21 Issue the Approve command.
Note: Before issuing the Approve command, you must be logged into the
network element UI at any menu level, with admin user privileges. The alarm
must be active in the system, all service-affecting parameters for low-speed
and high-speed facilities must be correct, and the clock source setting of the
network element must be properly set.
To issue the Approve command:
approve
The following warning appears on the screen:
DO NOT execute the APPROVE command on an IN SERVICE node.
THIS WILL AFFECT TRAFFIC.
Contact your next level of support before you continue.
Are you ready to continue with the APPROVE?
Please confirm (Yes or No):
To confirm the command:
yes
continued
Eqp CE
Step Action
22 The Approve command initiates a restart of the processor. If the alarm

remains following the restart, contact your next level of support or your
Library, 323-1111-090.
end
Eqp CE 40
Datacomm access violation 4
Probable cause
The network element has detected an attempt to access a data communications
node over the SONET data communications network for which the user is not
allowed access. The login attempt can be either from or to this network
element as follows:
from this network element to another network element (rlogin or selectne
commands) or an OPC (rlogin command)
to this network element from another network element (rlogin or selectne
commands) or OPC (nelogin command or OPC NE Login Manager tool)
The login attempt can be through a SONET section data communications
channel (SDCC), control network (CNet), or Ethernet connection.
Access to and from the OPC and the network elements in the span of control
is controlled through access and deny lists provisionable through the OPC
config_dcc_ac command. If the feature is enabled, access must be explicitly
allowed to OPCs and network elements in both the local and remote networks
or else login access is denied. For more information, see System
Administration Procedures, 323-1111-302.
This alarm becomes active when the network element detects the access
attempt. The alarm must be cleared manually. Only one instance of this alarm
can be active at one time. Therefore, an active alarm might indicate more than
one access violation.
Impact
Major, non-service affecting.
Enabled by default.
Action
Step Action
1 Alert the system administrator of the access attempt.

2 You must manually clear the alarm on the local network element using the
CLSDCCALM command interpreter (CI) tool. Only the admin user can use
this CI tool. Non-default users with admin-level access privileges cannot use
the tool. To clear the alarm, enter:
clrsdccalm
The alarm is cleared.
end
Eqp CE 40
Duplicate NE name 4
Probable cause
This alarm becomes active when the network element data communications
software detects another network element in the data communications network
with the same name. It becomes active when the network element detects the
condition. It clears when you rename one of the network elements.
Impact
Warning, non-service affecting.
Enabled by default.
Action
Step Action
1 To clear the alarm, rename one of the affected network elements according
to Commissioning Procedures, 323-1111-220.
end
Eqp CE 40
Duplicate NE numeric identifier 4
Probable cause
This alarm becomes active when the network element data communications
software detects another network element in the data communications network
with the same Network id, System id, and NE id.
The alarm becomes active when the network element detects the condition. It
clears when you renumber one of the network elements.
Impact
Minor, service affecting.
Enabled by default.
Action
Step Action
1 Before you attempt to clear this alarm, contact your next level of support or
Nortel Networks according to About the OC-3/OC-12 NETBM Library,
323-1111-090.
end
Eqp CE 40
Entry to SONET clock freerun 4
Probable cause
The shelf has reverted to its SONET clock despite being provisioned for
external synchronization interface (ESI) timing. There can be more than one
ESI subunit failure.
Note: This alarm is not raised on VTM systems.
Impact
Action
Step Action
1 Firmly reseat the ESI carrier. If the alarm remains, go to step 2.

2 Firmly reseat each ESI unit. If the alarm remains, go to step 3.
3 Replace the ESI units. See Module Replacement Procedures, 323-1111-547.
end
Eqp CE 40
Exerciser fail 4
Probable cause
The exerciser log records the cause of this alarm, which could be a protection
path fail.
Impact
Action
Step Action
1 The cause of the alarm is recorded in log Eqp608. Determine the cause of
the alarm by entering:
logutil
open eqp
2 Clear the problem indicated in the log. The log could indicate the following
results, which would raise the Exerciser fail alarm.
a. failed: diagnostic failed or software errors
b. aborted: exerciser run prematurely terminated by a higher priority system
activity
3 Run the exerciser again to clear the alarm.
end
Eqp CE 40
Manual area address dropped from area 4
Probable cause
This alarm is raised when a provisioned manual area address is dropped from
the computed area address set of the network. Each network element supports
a maximum of up to three manual area addresses at one time. All network
elements in the network share this information. The computed area address set
is calculated on the OPC and can be seen by each NE. The computed set is
recalculated in the following situations:
addition of a new network element to the network or adjoining networks
manual deletion or addition of an area address from any network element
As a result, the probable causes of this alarm are as follows.
Invalid area addresses have been configured into one or more intermediate
system NEs in the network.
An adjoining network operates with a different area address set. The two
area address sets have at least one area address in common. The connection
of the networks cause the combined area addresses within the routing
domain to exceed 3 unique area addresses.
This alarm can indicate a network wide error condition in the provisioning of
data communication. If an area address is dropped on a network element,
isolation of the network element and a loss of OAM&P capability on the
network element can occur.
Note: The area addresses to be used in the routing domain are decided
upon by the network planning and administration authority before any one
of the addresses is provisioned into the system. The format and value of
area addresses are not arbitrary. They follow international standards and
operation guidelines. The network operator must know the correct area
addresses to be used by the area.
In addition, the area addresses are not arbitrary. The addresses are defined
by operation policies set by the networks management and planning
authority and, sometimes, by vendors recommendations. These policies
can follow common operation standards and recommendations such as
Bellcore GR-253-CORE or the companys internal proprietary operating
policy.
continued
Eqp CE
Manual area address dropped from area (continued)
Impact
Minor alarm, non-service affecting.
Enabled by default.
Action
Step Action
Note: A solid knowledge in OSI data communication networks is necessary

in order to attempt to clear this alarm. Before attempting to clear the alarm,
you must know the correct area addresses designed for use by the network.
Please consult your network planning authority. (See the note in the Probable
cause section.)
Determine the manual area addresses needed in the network
1 To determine the manual area addresses provisioned on the network element
you must log into the network element with the alarm.
2 From the NE UI Main Menu, access the communications facility main screen
by entering:
fa comm
The Facility Menu appears.
3 Display the COMM area address screen by entering:
areaaddr
A list of up to three addresses appears. Record the list of addresses in the
manual set (Supported Area Addresses).
Determine which manual area address was dropped
4 Access the logutil CI tool by entering:
logutil
5 Select the log report type to query by entering:
open coaddr
6 Check for log COAD301. If this log exists, record the area addresses reported
in the log.
For more details on this log, see Log Report Manual, 323-1111-840. For a
description of how to access logs by the OPC Event Browser tool, refer to
chapter 1 of Log Report Manual, 323-1111-840.
continued
Eqp CE
Manual area address dropped from area (continued)
Step Action
Determine if the dropped manual area address belongs in the network

7 If Then
COAD301 contains the network area contact your next level of support or
address provisioned on the NE your Nortel Networks support group.
See About the OC-3/OC-12
NETBM Library, 323-1111-090
COAD301 does not contain the go to step 8
network area address provisioned on
the NE, for each of the area addresses
reported
Delete the manual area addresses that does not belong in the network
8 Delete the area address(es) displayed in log COAD301 by entering:
Delete <1 to 3>
where,
<1 to 3> is the first, second or third address in the list
The area address is deleted.
9 For any other NEs containing the alarm, repeat the procedure.
end
Eqp CE 40
NE database backup to OPC failed 4
Probable cause
Failure of the NE database operation to the OPC.
Impact
Action
Step Action
1 Perform a database backup to the OPC by entering:

equipment sh
backupdb
yes
2 Confirm the backup by checking the logs buffer by entering:
logutil
open FWDB
end
Eqp CE 40
Node count limit is exceeded 4
Probable cause
There is more than the allowable number of nodes in the data communications
network. The nodes include all network elements (including regenerators) and
OPCs that can communicate with one another.
The allowable node count is set by an engineering limit. For current

engineering limits, see Technical Specifications, 323-1111-180.
The alarm becomes active when the network element detects the addition of a
data communications node that exceeds the allowable node count. It clears
automatically when the number of nodes is fewer than the allowable limit.
Impact
Minor, non-service affecting.
Disabled by default.
To avoid this alarm being raised on many network elements, enable this alarm
on only one network element in the data communications network.
Action
Step Action
1 Check the allowable limit for the number of data communications nodes for
the network as specified in Technical Specifications, 323-1111-180.
2 Remove the excess number of data communications nodes from the network.
You might have to re-engineer the network so that the data communications
requirements are fully met. Follow the guidelines of Technical Specifications,
323-1111-180.
end
Eqp CE 40
PM threshold capping active 4
Probable cause
The network element has squelched some performance-monitoring alarms or
alerts through the threshold-capping feature. When the number of
performance-monitoring alarms or alerts reach a provisioned threshold, the
network element squelches any further performance-monitoring alarms or
alerts for that parameter.
The alarm becomes active when the network element caps the threshold alerts
or alarms for at least one performance-monitoring interval. The alarm clears
when there are no longer any capped threshold alerts or alarms for any interval.
Impact
Warning, non-service affecting.
Enabled by default.
Action
No action is necessary to clear this alarm. Instead, resolve the root cause of the
performance errors by following the appropriate alarm-clearing procedure in
this document for the affected performance-monitoring parameter.
end
Eqp CE 40
Ring reconfiguration in progress 4
Probable cause
The craftsperson is performing a ring reconfiguration.
Impact
Action
No action is required.
end
Eqp CE 40
Shelf assembly fail 4
Probable cause
A problem exists with the side interconnect left circuit pack on the shelf.
Impact
This is a critical, service-affecting (C, SA) alarm.
Action
Step Action
1 Check for proper seating of the side interconnect left circuit pack located in
the left most slot of the shelf.
2 If the circuit pack is properly seated in its slot, and this alarm persists, contact
your next level of support or your Nortel Networks support group. See About
the OC-3/OC-12 NETBM Library, 323-1111-090.
end
Eqp CE 40
Shelf id bus fail 4
Probable cause
A problem exists with the identification card internal to the shelf.
Impact
Action
Step Action
1 Remove the shelf cover. See Module Replacement Procedures,

323-1111-547.
2 Verify that each DS1 input or output circuit pack and each DS3 input/output
circuit pack is fully seated by firmly pushing each one of them.
Note: Do not pull out I/O circuit packs or cables as this affects corresponding
traffic.
3 Do the following:
If the alarm Then
clears you have completed the procedure
persists or reappears periodically go to step 4
4 Contact your next level of support or your Nortel Networks support group.
See About the OC-3/OC-12 NETBM Library, 323-1111-090.
end
Eqp CE 40
Software trap 4
Probable cause
A software trap has occurred on the indicated network element. It must be
cleared by Nortel Networks, using a password-protected resident tool.
Impact
Action
Note: Do not restart or reboot the system.
Step Action
1 Open the trap log buffer by entering:

admin nep
logs
open trap
2 Record all traps in the log buffer. If there is more than one, scroll through the
buffer by entering:
forward
or
back
3 Contact your Nortel Networks support group to report all information
concerning system status. See About the OC-3/OC-12 NETBM Library,
323-1111-090.
Note: Your Nortel Networks support group will capture the trap for analysis
and clear the alarm using a resident tool.
end
Eqp CE 40
SONET overhead data/clock loss 4
Probable cause
A data/clock loss has been detected on the SONET overhead. One of the
following conditions exist:
an OC-12 optical interface circuit pack is being replaced in a NWK ring
system
a faulty OC-3/OC-12 optical interface circuit pack
a faulty processor circuit pack
Impact
Action
Note: Before replacing a circuit pack, try to clear the alarm by reinstalling
the same circuit pack, ensuring the circuit pack is protected before
removing and reseating it. If the alarm persists, replace the circuit pack.
See Module Replacement Procedures, 323-1111-547.
Step Action
1 If an OC-12 optical interface circuit pack is being replaced in a NWK ring

system, this alarm should clear when the new circuit pack is in place. If this is
not the case, go to step 2.
2 One at a time, replace the OC-3/OC-12 optical interface circuit packs at the
local end, then at the far end. See Module Replacement Procedures,
323-1111-547.
If the alarm Then
clears when a circuit pack is replaced you have completed the procedure
remains after all circuit packs have go to step 3
been replaced
continued
Eqp CE
SONET overhead data/clock loss (continued)
Step Action
3 Replace the processor circuit pack at the local end then at the far end. See
Module Replacement Procedures, 323-1111-547.
If the alarm Then
clears when a circuit pack is replaced you have completed the procedure
remains after all circuit packs have go to step 4
been replaced
end
Eqp CE 40
Traffic upgrade in progress 4
Probable cause
A traffic upgrade is occurring.
Impact
Action
No action is required if a test or maintenance operation is being performed.
end
Eqp CE 40
User port 1 intrusion attempt
User port 4 intrusion attempt 4
Probable cause
More than the allowable number of unsuccessful log-in attempts have been
made from the equipment connected to the user interface port identified in the
alarm. A log-in attempt is unsuccessful if either the user identifier or password
entered is invalid.
The allowable number of unsuccessful log-in attempts ranges from 2 to 9, as

provisioned through the Centralized User Administration tool. For more
information, see System Administration Procedures, 323-1111-302.
This alarm becomes active when the network element locks out the user
interface port. It clears when the network element unlocks the port. The
network element unlocks the port automatically after a set period of time,
called the alert duration period. You can provision the alert duration period
through the Centralized User Administration tool.
Impact
Minor alarm, non-service affecting.
Enabled by default (unprovisionable).
The network element locks out the user interface port when the maximum
number of log-in attempts for that port is exceeded. No user can log in to the
network element through that port until the provisioned alert duration period
has expired. The alert duration period can be up to 3 minutes.
Action
No user action is necessary to clear the alarm. It clears automatically on the
expiry of the alert duration period. However, the system administrator might
wish to investigate to ensure that there has not been an unauthorized attempt to
breach network security.
end
Eqp DS1
Circuit pack fail 4
Probable causes
A component failure or defective circuit pack.
In rare circumstances, this alarm (when accompanied by OC12 and ESI

equipment alarms) could also be due to an incorrect Application Select state.
See chapter 10, Clearing incorrect Application Select state, for more
information.
Impact
This is a critical, service-affecting (C, SA) alarm (if not protectable).
This is a minor, not service-affecting (m, nsa) alarm (if protectable).
Note: Switch to protection initiated, with a maximum 60 ms traffic outage.
Action
Step Action
1 Replace the DS1 VT mapper circuit pack. See Module Replacement

Procedures, 323-1111-547, for replacement instructions.
end
Eqp DS1 40
Circuit pack mismatch 4
Probable cause
The circuit pack in the slot does not match the provisioned type. Rules for
The alarm also occurs when:

any facilities are provisioned for Byte Synchronous or TR-08/DLC
framing
and an NT7E04AA/BA mapper is inserted into the slot
Impact
Action
Step Action
1 For an in-service unit, replace the alarmed unit with the proper type. See
Module Replacement Procedures, 323-1111-547, for replacement
instructions.
2 If the TR08/DLC framing format, or the Then go to
Byte Synchronous provisioning, is:
required replace the mapper with an
NT7E04EA or NT7E04CA type
not required deprovision this mode/format, or
the Synchronous provisioning.
See Provisioning and Operations
Procedures, 323-1111-310 for
provisioning instructions.
end
Eqp DS1 40
Circuit pack missing 4
Probable cause
A provisioned slot does not contain a circuit pack or circuit pack is not firmly
inserted in the slot.
Impact
Note: Switch to protection is initiated, with a maximum 60 ms traffic

outage.
Action
Step Action
1 Insert a DS1 VT mapper circuit pack in the appropriate slot. See Module
end
Eqp DS1 40
DS1 protection unavailable, equipment OOS 4
Probable cause
The protection DS1 mapper is provisioned to be out of service. Therefore DS1
tributary protection is unavailable.
Impact
Enabled by default.
Action
Step Action
1 If the network element Then go to

requires DS1 protection step 2
does not require DS1 protection step 3
2 Provision the protection DS1 mapper to be in service by entering:

equipmnt ds1 p
chgstate is
3 Delete the protection DS1 mapper by entering:
equipmnt ds1 p
delete
yes
end
Eqp DS1 40
Facility provisioning mismatch 4
Probable causes
A mismatch exists between hardware and provisioned attributes if any of the
14 DS1 facilities are provisioned with attributes that are not supported by the
hardware.
This alarm is also raised for Byte Synchronous provisioning when a

NT7E04AA mapper is inserted into that slot.
Note 1: When a mapper is preprovisioned (a mapper is not installed), the

default is to a type NT7E04EA mapper, and the TR08 mode/digital loop
carrier (DLC) frame format can be set. When the NT7E04EA or
NT7E04CA mapper is inserted, no alarm is raised. However, if a
NT7E04AA mapper is installed, this alarm is raised.
Note 2: The AA and CA mappers are manufacturer discontinued but might
exist in the field.
Note 3: If an NT7E04EA or NT7E04CA mapper is subsequently replaced
with an NT7E04AA mapper, this alarm is also raised if TR08 DS1 frame
format is set.
Note 4: If DS1 TR08 frame format is required, only the NT7E04EA or
NT7E04CA mapper can be used. If the NT7E04AA mapper is installed,
the DS1 frame format cannot be set to TR08.
Impact
This is a major, service-affecting (M, SA) alarm.
Action
Step Action
1 Is the TR08 mode/digital loop carrier (DLC) frame format required on any DS1
signal passing through the alarmed mapper?
If the TR08 mode/DLC frame format is Then go to
required step 2
not required step 3
2 If the TR08 mode/DLC frame format is required, replace the mapper with an
NT7E04EA or NT7E04CA type. See Module Replacement Procedures,
323-1111-547, for replacement instructions.
3 If the TR08 mode/DLC frame format is not required, deprovision this
mode/format. See Provisioning and Operations Procedures, 323-1111-310.
end
Eqp DS1 40
Forced switch request 4
Probable cause
A forced switch command has been requested for the DS1 VT mapper circuit
pack.
Impact
Action
Note: This alarm point serves as a reminder not to leave a potentially
service-affecting condition on the system (especially when conveying live
traffic).

end
Eqp DS1 40
Input card fail -DoNotRemove
Output card fail -DoNotRemove 4
Probable cause
A component failure or defective circuit pack exists.
Impact
Action
Step Action
1 CAUTION
Loss of traffic
Do not remove input or output circuit packs without
advice from your Nortel Networks support group.
An input or output circuit pack has failed and needs replacing. Contact your
next level of support or your Nortel Networks support group. See About the
OC-3/OC-12 NETBM Library, 323-1111-090.
end
Eqp DS1 40
Input card mismatch
Output card mismatch 4
Probable cause
The provisioned circuit pack does not match the type of circuit pack in the slot.
Impact
This is a critical and service-affecting (C, SA) alarm.
Action
Step Action
1 CAUTION
Loss of traffic
Replace the circuit pack in the slot with a DS1 input or output circuit pack. See
procedures.
end
Eqp DS1 40
Input card missing
Output card missing 4
Probable cause
Either a DS1 input or output circuit pack is missing from the slot.
Impact
Action
Step Action
1 CAUTION
Loss of traffic
Insert a DS1 input or output circuit pack into the reserved slot in the top level
of the shelf. See Module Replacement Procedures, 323-1111-547, for
replacement instructions.
end
Eqp DS1 40
Lockout request 4
Probable cause
A lockout command has been issued for the DS1 VT mapper circuit pack.
Impact
Action
traffic).

end
Eqp DS1 40
Manual switch request 4
Probable cause
A manual switch command has been requested for the DS1 VT mapper circuit
pack.
Impact
Action
end
Eqp DS1 40
Matchnode connection provisioning mismatch 4
Probable cause
A matched node connection is preprovisioned on a DS1 circuit pack.
Impact
Action
Step Action
1 Delete the preprovisioned matched-node connection or deprovision the DS1

circuit pack and add an STS1 circuit pack.
Note: See chapter on provisioning matched node connections in
Provisioning and Operations Procedures, 323-1111-310 for provisioning
guidelines, restrictions/limitations, and provisioning procedures.
end
Eqp DS1 40
Protection equipment unavailable 4
Probable cause
If the DS1 protection equipment is put out of service (OOS) the system will
raise the alarm DS1 protection unavailable, equipment OOS. This alarm is
raised in order to warn the user about the unavailability of protection.
Impact
This is a minor non service affecting alarm (m, nsa).
Action
Step Action
1 Put the DS1 protection circuit pack back in service (IS) to clear the
alarm.
2 Disable the alarm from the Alarm Provisioning screen of the DS1 Protection
mapper. Refer to Provisioning and Operations procedures, 323-1111-310,
Procedure 3-6, Enabling and disabling alarms.
end
Eqp DS1 40
Protection path fail 4
Probable cause
The protection switch exerciser recorded a failure while bridging traffic to the
protection circuit pack. This indicates that a hardware failure exists on the DS1
protection path. If a DS1 working circuit pack requires protection and the
failure exists on the protection path, this alarm is raised as a major alarm since
traffic is lost. If no protection is required, the alarm is minor.
Note: The presence of a low DS1 signal level on the DS1 facility has been
known to cause this alarm. The protection unit is unable to detect the signal
when traffic is bridged to it.
This is a major, service-affecting (M, SA) alarm when protection is requested.

This is a minor, not service-affecting (m, nsa) alarm when protection is not
requested.
Action
Note 1: Removal of the maintenance interface (MIC) circuit pack causes
a loss of access to the user interface ports, and the current user process is
stopped. In particular, any UI session is stopped and has to be restarted
once the MIC circuit pack is in place.
Note 2: This alarm can be a result of different circuit packs that make up
the protection path. This procedure instructs the user to start by replacing
the circuit packs that least affect service. Once the circuit pack that causes
the alarm has been found, all previously replaced circuit packs need not be
returned to Nortel Networks for repair.
Step Action
1 Verify the state of the maintenance interface controller (MIC) circuit pack:
eq mic
If the MIC state is Then go to
OOS step 2
IS, IS trbl, or other step 3
2 Change the operating state of the MIC to IS (in service):

chgstate is
continued
Eqp DS1
Protection path fail (continued)
Step Action
3 Replace the maintenance interface controller (MIC) circuit pack. See Module
Replacement Procedures, 323-1111-547.
4 Run the DS1 exerciser:
equipmnt sh
exercise
If the alarm Then
clears you have completed the procedure. Check the scheduling
times of the exercise. Ensure that the times are set
5 minutes apart. See Protection Switching Procedures,
323-1111-311.
persists go to step 5
5 Replace the DS1 protection unit equipped in slot 19. See Module
equipmnt sh
exercise
If the alarm Then
7 Determine which DS1 ports caused the alarm.

Type the following at the NE UI prompt:
logutil
open flt
back
Type back until the Protection path fail log appears.
Note: The FLT700 log that describes this alarm also indicates in its text which
DS1 ports caused the failure. It is possible that the ports have a low DS1
signal level that caused the failure. Nortel Networks recommends that you
check the signal level of these DS1 ports to determine if this is the cause.
continued
Eqp DS1
Step Action
8 Measure the signal level of the affected DS1 ports. If the signal level appears
to be significantly lower than the normal DS1 signal level, the low signal level
is probably causing the alarm.
9 Do the following:
If the alarm Then

equipmnt sh
exercise
If the alarm Then
continued
Eqp DS1
Step Action
11 The alarm can be a result of parity errors on the STS-1 links between the
transport interface cards and the DS1 protection mapper. To determine if this
is the case, use the FLT700 logs. Type the following at the NE UI prompt:
logutil
open flt
back
Type back until all the logs that have been generated since the last
exerciser run are viewed.
If the logs Then
indicate parity errors between the transport slots go to step 12
(slots 5, 7, 9, or 10) and the DS1 protection mapper
(slot 19)
do not indicate parity errors between the transport go to step 14
slots (slots 5, 7, 9, or 10) and the DS1 protection
mapper (slot 19)
12 Replace the transport interface circuit pack indicated in the log. See Module
equipmnt sh
exercise
If the alarm Then
14 The alarm may be a result of faulty protection relays on the DS1 VT mappers
corresponding DS1 Input unit. To replace the DS1 Input unit, see Module
equipmnt sh
exercise
If the alarm Then
not cleared go to step 16
end
Eqp DS1 40
Protection switch complete 4
Probable cause
A DS1 VT mapper circuit pack is switched on the protection unit (caused by a
manual, automatic, or forced switch).
Impact
Action
Step Action
1 Determine whether the switch was automatic or manual.

protectn
dtlprot ds1
2 Do the following:
If Then
a manual operation (manual, forced the DS1 VT mapper circuit pack is
switch) was performed being tested
an automatic switch was performed investigate with the DS1 equipment
alarm screen on the network element
user interface by entering the
following commands
alarms
filter eq
3 If the cause of the switch is still unknown, check whether the facility is out of
specification.
facility ds1 <circuit pack> <port #>
where
<circuit pack> g1 to g12 or all for OC-12
g1 to g12 or all for OC-3
<port#> is 1 to 14
end
Eqp DS1 40
Protection switch fail 4
Probable cause
A DS1 VT mapper circuit pack as a result of an automatic switch, a forced
switch or a manual switch, is denied access to the protection bus.
Impact
Action
Note: Removal of the maintenance interface (MIC) circuit pack causes a
loss of access to the user interface ports, and the current user process is
once the MIC is in place.
Step Action
1 Check that there are no lockouts in effect:

equipmnt ds1 all
dtlprot
2 Is there an asterisk (*) in the Lockout column?
If an asterisk (*) Then go to
does not appear step 3
appears step 5
3 Is the operating state of the protection mapper IS?

equipmnt ds1 p
If the operating state of the protection mapper is Then go to
not IS step 4
IS step 6
continued
Eqp DS1
Protection switch fail (continued)
Step Action
4 Display the alarm screen and check for other more severe DS1 protection
equipment alarms or MIC equipment alarms.
alarms
If Then
another DS1 equipment alarm appears look up the alarm in this chapter
and proceed accordingly
an MIC equipment alarm appears look up the alarm in this chapter
no other more severe alarms appear go to step 6
5 Release the lockout:

lockout re <circuit pack>
yes
where
<circuit pack> p, g1 to g12 for OC-12
is p, g1 to g12 for OC-3
The screen displays a period (.) in the Lockout column for the corresponding
group.
eq mic
OOS step 7
IS trbl or other step 8
IS step 9

chgstate is
IS step 9
continued
Eqp DS1
Step Action
9 Run the DS1 exerciser to test the DS1 equipment

equipmnt sh
exercise
If the alarm Then
end
Eqp DS1 40
Protection version mismatch 4
Probable cause
One of the 14 in-service DS1 facilities are provisioned with attributes that are
not supported by the protection hardware. When a DS1 facility is provisioned
for TR-08 frame format and the protection DS1/VT mapper is replaced with a
NT7E04AA, this alarm would be raised.
This alarm is also raised for Byte Synchronous provisioning when a

NT7E04AA mapper is inserted into the protection slot.
Note: The AA and CA mappers are manufacture discontinued but might

exist in the field.
Impact
Action
Step Action
1 Is TR08 frame format required on any DS1 signal passing through the
alarmed mapper?
If TR08 frame format is Then go to
required step 2
not required step 3
2 If TR08 frame format is required, replace the protection mapper with an

NT7E04EA or NT7E04CA type. See Module Replacement Procedures,
3 If TR08 frame format is not required, deprovision this format. See
Provisioning and Operations Procedures, 323-1111-310, for enabling
instructions.
end
Eqp DS1 40
STS1 intercard fail 4
Probable cause
A parity error is detected at the backplane between a DS1 mapper and a
transport circuit pack (OC -3/OC-12 or Lpbk circuit pack). The cause of the
problem might be at the signal source, signal destination or on the signal path.
A hardware fault might exist on the DS1 mapper, the transport circuit pack, or
the backplane.
Impact
This is a critical, service-affecting (C, SA) alarm if the following conditions
are met: the system is in an unprotected configuration and a parity error is
detected between an active transport circuit pack and a DS1 mapper.
This is a minor, not service-affecting (m, nsa) alarm if the system is in a

protected configuration or a parity error is detected between an inactive
transport circuit pack and a DS1 mapper.
Action
Step Action
1 Display the detailed alarm information for this alarm. See the procedure for
displaying a detailed alarm report in Network Surveillance Procedures,
323-1111-510.
The signal source and signal destination are indicated by the primary slot and
secondary slot number on the detailed alarm screen.
continued
Eqp DS1
STS1 intercard fail (continued)
Step Action
A screen similar to the following is displayed.

OS.0007

Network View . 1 . . . . . .
St.John's . 1 . . . . . .
DtlAlms 1.1.63
0 Quit Detailed Alarm Reports
2 Next
3 Prev AlmRpt: 12 Raised
4 Address: DS1 G11, 50 Shelf 1 m,nsa
5 Location: Frame ShPos 1 Slot 17,9 17:32:01
6 Reason: STS1 intercard fail 13 Nov 95
7 NewAlms Prim/Sec: SNPQNA42AA Slot 17 / SNTRVNZ2AA Slot 9 Equipment
8
9 DTLALMS:
10 DtlProt
11
12
13
14 Port
15 Equipmnt
16 Facility
17
18 Help
NE 63
Time 17:35 >
2 Replace the circuit pack that occupies the primary slot number. See the
appropriate procedure in Module Replacement Procedures, 323-1111-547.
3 If the problem persists, replace the circuit pack that occupies the secondary
slot number. See the appropriate procedure in Module Replacement
Note: If the alarm clears, the circuit pack replaced is the source of the
problem. All other circuit packs replaced before this step are functioning
properly and need not be returned to Nortel Networks for repair.
4 If the problem persists, contact your next level of support or your
Library, 323-1111-090.
end
Eqp DS3
BNC I/O card 1 fail -DoNotRemove
BNC I/O card 3 fail -DoNotRemove 4
Probable cause
Impact
Action
Step Action
1 CAUTION
Do not remove BNC input/output (I/O) circuit packs
without advice from your Nortel Networks support
group.
A BNC input/output (I/O) circuit pack has failed and needs replacing. Contact
end
Eqp DS3 40
BNC I/O card 1 mismatch
BNC I/O card 3 mismatch 4
Probable cause
The circuit pack inserted into the shelf I/O slot does not match the provisioned
circuit pack type.
Impact
Action
Step Action
1 CAUTION
Do not remove BNC I/O circuit pack without advice
from your Nortel Networks support group.
Replace the circuit pack in the I/O slot with a BNC I/O circuit pack.
Note: All three I/O circuit packs must be inserted even if not all three DS3
facilities are used.
2 Ensure BNC I/O circuit packs are firmly pushed into the backplane of the
shelf.
end
Eqp DS3 40
BNC I/O card 1 missing
BNC I/O card 3 missing 4
Probable cause
A provisioned shelf I/O slot does not contain a BNC I/O circuit pack.
Impact
Action
Step Action
1 CAUTION
Do not remove another DS3 Interface unit without
Insert a BNC I/O circuit pack into the slot.

Note: All three interface circuit packs must be inserted even if not all three
DS3 facilities are used.
2 Ensure BNC I/O circuit packs are firmly pushed into the backplane of the
shelf.
end
Eqp DS3 40
Circuit pack fail 4
Probable causes

information.
Impact
Action
Step Action
1 Replace the defective unit. See Module Replacement Procedures,

end
Eqp DS3 40
Probable cause

Impact
Action
Step Action
1 For an in-service unit, replace the alarmed unit with the proper type. See
instructions.
end
Eqp DS3 40
Probable cause
One of the following conditions exists:
a provisioned slot does not contain a circuit pack

the circuit is not firmly inserted into the shelf
Impact
This is a critical and service-affecting (C, SA) alarm (if not protectable).
Action
Step Action
1 Insert a DS3 STS mapper circuit pack into the slot. See Module Replacement
end
Eqp DS3 40
DS3 protection unavailable, equipment OOS 4
Probable cause
The protection DS3 mapper is provisioned to be out of service. Therefore DS3
tributary protection is unavailable.
Impact
Enabled by default.
Action
Step Action

requires DS3 protection step 2
does not require DS3 protection step 3
2 Provision the protection DS3 mapper to be in service by entering:

equipmnt ds3 p
chgstate is
3 Delete the protection DS3 mapper by entering:
equipmnt ds3 p
delete
yes
end
Eqp DS3 40
Probable cause
A forced switch command has been requested for the DS3 STS mapper circuit
pack.
Impact
Action
traffic).

end
Eqp DS3 40
Lockout request 4
Probable cause
A lockout command has been issued for the DS3 STS mapper circuit pack.
Impact
Action
traffic).

end
Eqp DS3 40
Probable cause
A manual switch command has been requested for the DS3 STS mapper
circuit pack.
Impact
Action
end
Eqp DS3 40
Probable cause
A matched node connection is preprovisioned on a DS3 circuit pack.
Impact
Action
Step Action
1 Delete the preprovisioned match-node connection or deprovision the DS3

circuit pack and add an STS-1 circuit pack.
end
Eqp DS3 40
Probable cause
If the DS3 protection equipment is put out of service (OOS) the system will
raise the alarm DS3 protection unavailable, equipment OOS. This alarm is
Impact
Action
Step Action
1 Put the DS3 protection circuit pack back in service (IS) to clear the
alarm.
2 Disable the alarm from the Alarm Provisioning screen of the DS3 Protection
end
Eqp DS3 40
Probable cause
The protection switch exerciser failed while attempting to bridge traffic to the
protection circuit pack. A hardware failure exists on the DS3 protection path.
If a DS3 working circuit pack requires protection and a failure exists on the
protection path, this alarm is raised as a major alarm since traffic is lost. If no
protection is required, the unprotected severity is minor.
This alarm is also raised if a working DS3 mapper is reseated when one or
more of its is not in the in-service traffic (IS-traffic) state.
Note: When a DS1 out module is placed in slot 30 or a DS1 in module is

placed in slot 32, a Protection path fail alarm is raised for DS3 G1. To clear
this alarm, see the alarm and trouble clearing procedures for the Circuit
pack mismatch alarm in this chapter.
Impact
requested.
Action
Note 2: This alarm can be a result of different circuit packs which make
up the protection path. This procedure has the user start by replacing the
circuit packs that least affects service. Once the circuit pack that causes the
alarm has been found, all previously replaced circuit packs need not be
Step Action
eq mic
OOS step 2
continued
Eqp DS3
Step Action

chgstate is
equipmnt sh
exercise
If the alarm Then
5 Check the status of all the facilities of the affected DS3 mapper according to
Provisioning and Operations Procedures, 323-1111-310.
6 If Then go to
any facility has a status of IS-Trbl-Facility Fail step 7
none of the facilities has a status of IS-Trbl-Facility Fail step 10
7 Provision that facility to out of service (OOS) according to Provisioning and

equipmnt sh
exercise
If the alarm Then go to
clears step 9
persists step 10
9 Provision the facility to be in service (IS) according to Provisioning and

Operations Procedures, 323-1111-310. This procedure is complete.
10 Replace the protection switcher circuit pack. See Module Replacement
continued
Eqp DS3
Step Action

equipmnt sh
exercise
If the alarm Then
12 Replace the DS3 protection unit equipped in slot 1. See Module Replacement
equipmnt sh
exercise
If the alarm Then
14 The alarm may be a result of parity errors on the STS-1 links between the
transport interface cards and the DS3 protection mapper. To determine if this
is the case, use the FLT700 logs. Type the following at the NE UI prompt:
logutil
open flt
back
Type back until all the logs, which have been generated since the last
exerciser run, are viewed.
If the logs Then
(slots 5, 7, 9, or 10) and the DS3 protection mapper
(slot 1)
slots (slots 5, 7, 9, or 10) and the DS3 protection
mapper (slot 1)
continued
Eqp DS3
Step Action

equipmnt sh
exercise
If the alarm Then
end
Eqp DS3 40
Probable cause
A DS3 STS mapper circuit pack is switched to the standby unit (caused by a
manual, automatic or forced switch).
Impact
Action
Step Action

protectn
dtlprot ds3
2 Do the following:
If Then
a manual operation (manual or forced the DS3 STS mapper circuit pack
switch) has been performed is being tested
an automatic switch has been investigate with the DS3
performed equipment alarm screen on the
network element user interface by
entering the following commands
alarms
filter eq
specification.
facility ds3 <circuit pack> <port #>
where
<circuit pack> is g1 to g4 for OC-3
is g1 to g4 for OC-12
<port #> is 1 to 3
end
Eqp DS3 40
Probable cause
A DS3 STS mapper circuit pack is denied access to the protection bus as a
result of an automatic switch, a forced switch, or a manual switch.
Impact
Action
loss of access to the user interfaces, and the current user process is stopped.
Step Action
1 Check that there are no lockouts in effect:

equipmnt ds3 all
dtlprot
2 Is there an asterisk (*) in the Lockout column?
does not appear step 3
appears step 5
3 Is the operating state of the protection mapper IS?

equipmnt ds3 p
If the operating state of the protection mapper is Then go to
not IS step 4
IS step 6
continued
Eqp DS3
Step Action
4 Display the alarm screen and check for other more severe DS3 protection
equipment alarms or MIC equipment alarms.
alarms
If Then
another DS3 equipment alarm appears look up the alarm in this chapter
an MIC equipment alarm appears look up the alarm in this chapter
5 Release the lockout:

lockout re <circuit pack>
yes
where
<circuit pack> p, g1 to g4 for OC-3
p, g1 to g4 for OC-12
The screen displays a period (.) in the Lockout column for the corresponding
group.
eq mic
OOS step 7
IS step 10

chgstate is
IS step 10
continued
Eqp DS3
Step Action
8 Replace the MIC. See Module Replacement Procedures, 323-1111-547.

9 Verify that the alarm has cleared.
If the alarm Then
10 Replace the protection DS3 Mapper. See Module Replacement Procedures,

323-1111-547.
Do the following:
If the alarm Then

Do the following:
If the alarm Then
end
Eqp DS3 40
Probable cause
A parity error is detected at the backplane between a DS3 mapper and a
transport circuit pack (OC-3/OC-12 or Lpbk circuit pack). The cause of the
problem might be at the signal source, signal destination, or on the signal path.
A hardware fault might exist on the DS3 mapper, the transport circuit pack or
the backplane.
Impact
are met: the system is a DS3 unprotected configuration and a parity error is
detected between an active transport circuit pack and the DS3 mapper that
raised this alarm.
This is a minor, not service-affecting (m, nsa) alarm if either the system is a
DS3 protected configuration or a parity error is detected between an inactive
transport circuit pack and the DS3 mapper that raised this alarm.
Action
Step Action
323-1111-510.
continued
Eqp DS3
Step Action

OS.0008

Network View . 1 1 . . . . .
St.John's . 1 1 . . . . .
DtlAlms 1.1.63
2 Next
4 Address: DS3 G1, 13 Shelf 1 m,nsa
7 NewAlms Prim/Sec: SNPQNA52AA Slot 11 / SNTRVNB2AA Slot 9 Equipment
8
9 DTLALMS:
10 DtlProt
11
12
13
14 Port
15 Equipmnt
16 Facility
17
18 Help
NE 63
Time 17:35 >
Library, 323-1111-090.
end
Eqp DS3 40
Switcher circuit pack mismatch 4
Probable cause
The circuit pack inserted into the shelf does not match the provisioned circuit
pack type.
This alarm will be critical if a protection switch is active on another DS3

circuit pack.
Impact
This is a critical, service-affecting (C, SA) alarm (if not protectable
Action
Step Action
1 Replace the circuit pack in the slot with a protection switcher circuit pack. See
instructions.
end
Eqp DS3 40
Switcher circuit pack missing 4
Probable cause
The protection switcher circuit pack is missing.
This alarm will be critical if a protection switch is active on another DS3

circuit pack.
Impact
Action
Step Action
1 Insert a protection switcher circuit pack in the reserved slot. See Module
end
Eqp DS3 40
Traffic problem detected 4
Probable cause
The protection DS3 STS mapper is not available to provide protection. One of
the following conditions exists:
the protection mapper is already protecting another DS3 circuit pack group
the protection group is locked out
the protection DS3 STS mapper circuit pack is missing
the protection switcher circuit pack is missing
the maintenance interface controller (MIC) circuit pack is missing
the DS3 STS mapper circuit pack is faulty
Impact
This is a major, service-affecting (M, SA) alarm (if not protectable).
Action
Step Action
1 Display the DS3 protection screen. Enter:

pr
dtlprot ds3
The DS3 detailed protection screen appears.
continued
Eqp DS3
Traffic problem detected (continued)
Step Action
2 Check for an active protection event against one of the working DS3 groups.
Do this by looking for an asterisk (*) beside any of the DS3 groups, under the
headings: Forced; AutoSw; or Manual.
If Then
a Manual or Forced switch is release the protection switch
active
an AutoSwitch is active fix the problem that caused the switch to
occur, then switch back to the working
DS3 mapper
there are no active protection go to step 3
switches
3 From the same screen as in step 2, check for a lockout against the protection
DS3 mapper. Do this by looking for an asterisk (*) beside the P (protection)
group, under the Lockout column.
If the protection mapper is Then
locked out release the lockout
not locked out go to step 4
4 From the same screen as in step 2, check for a lockout against the failed DS3
mapper. Do this by looking for an asterisk (*) beside the failed mappers circuit
pack group, under the Lockout column.
If the failed mapper is Then
locked out release the lockout
not locked out go to step 5
5 Ensure that the protection DS3 STS mapper circuit pack is properly installed
in shelf slot 1, and that the Active LED is lit.
At this stage, protection is now available and this alarm should clear. Other
alarms should be raised, for instance, DS3 circuit pack fail.
If new alarms Then
do not appear go to step 6
appear clear the new alarms
continued
Eqp DS3
Step Action
6 Ensure that the MIC is properly installed, and that the Active LED is lit.
7 Determine which transport interfaces are carrying the failed traffic. For
terminal or linear systems, look under the Rx column to determine which
transport interfaces are carrying the failed traffic by entering:
For a terminal:
dtlprot <service type>
For a linear ADM:
dtlprot <service type> g1
dtlprot <service type> g1s
where
<service type> is oc3 or oc12
For a ring ADM:

dtlprot oc12
8 Manually switch traffic from this circuit pack to protection by entering:
manual switch op <unit>
yes
where
<unit> is that found in step 7
(circuit pack group)
9 Do the following:
clears step 10
persists step 11
10 If the alarm clears, replace the optical circuit pack that cleared the alarm. See
Library, 323-1111-090.
Note 1: The alarm may persist until protection is available for the DS3 card.
Note 2: A system running without DS3 protection might raise a traffic
problem detected alarm that will not clear because protection is not available.
The alarm may be deprovisioned. See Provisioning and Operations
end
Eqp DS3 40
VT connection provisioning mismatch 4
Probable cause
A VT connection is preprovisioned at a network element that is already
equipped with a DS3/STS circuit pack.
Impact
Action
Step Action
1 Note the circuit pack type and group associated with the mismatch alarm.
2 At the NE User Interface, enter the following commands:
csci
qmiscon <cptype> <cpgroup>
A list of mismatched connections is displayed.
3 Identify the mismatched connections according to the VT provisioning rules
as summarized in the Probable cause section of this alarm.
4 Delete any invalid connections using the OPC Connection Manager. See
Provisioning and Operations Procedures, 323-1111-310, for instructions.
Otherwise, replace the DS3/STS mapper with a DS1/VT mapper circuit pack.
end
Eqp DS3 40
Protection hardware incompatible 4
Probable cause
If the shelf contains at least one working NT7E08BA or later version of the
DS3 mapper, but the protection DS3 mapper is an NT7E08AA, then the
system will raise a Protection hardware incompatible alarm in order to warn
the user of possible loss of functionality.
The NT7E08AA DS3 mapper can still protect the working traffic. However the
NT7E08AA DS3 mapper does not support capabilities provided by the
NT7E08BA or later version DS3 mapper.
Note: This alarm is disabled by default.
Impact
Action
Step Action
1 Replace NT7E08AA protection mapper with an NT7E08BA mapper.

2 If DS3 framing has been disabled with the NT7E08AA mapper, refer to
323-1111-310, Procedure 2-24, Enabling/disabling DS3 framing.
3 If the related DS3 facility alarm has been deprovisioned with the NT7E08AA
mapper, refer to 323-1111-310, Procedure 2-14, Enabling and disabling
facility alarms.
end
Eqp ESI
End VCO range 4
Probable cause
The voltage controlled oscillator (VCO) on the external synchronization
interface unit is at the end of its range.
Impact
Note: The clock might be unable to track changes to the external timing
reference.
Action
Step Action
1 Verify the integrity of the ESI external timing reference signal. Verify the
frequency of active timing to ensure it is within stratum 3 requirements.
2 Replace the external synchronization interface unit. See Module
end
Eqp ESI 40
Equipment forced switch request 4
Probable cause
A forced switch was requested for the working external synchronization
interface unit.
Impact
Note: The alarm clears when the forced switch clears. If the forced switch
request is not cleared, the protection unit is not available for use by the
system in the event of a problem with the working ESI.
Action
Note: No action is required unless you want to release the forced switch
request. See the following steps.
Step Action
1 From the network element status screen, display the ESI equipment screen
by entering:
eq esi <circuit pack>
where
<circuit pack> is g1 or g2
dtlprot
2 Release the forced switch request by entering:
forced re <g1 or g2>
yes
end
Eqp ESI 40
Equipment lockout request 4
Probable cause
A lockout command has been issued for the external synchronization interface
unit circuit pack group.
Impact
Action
Note 1: No action is required if a test or maintenance operation is being
performed. This alarm point serves as a reminder not to leave a potentially
service-affecting condition on the system.
Note 2: If you want to release the lockout, see the following step.
Step Action
1 Release the lockout by entering:

pr
dtlprot esi
lockout re <g1 or g2>
yes
end
Eqp ESI 40
Equipment manual switch request 4
Probable cause
The manual protection switch command was requested for the working
external synchronization interface unit.
Impact
Action
Note 1: No action is required.
Note 2: You need not release the protection switch because the protection
scheme of the ESI is 1+1. The manual switch request raises an alarm that
clears soon after it is raised.
end
Eqp ESI 40
Equipment protection switch complete 4
Probable cause
A switch from the working external synchronization interface unit to the
protection external synchronization interface unit was successfully completed.
Impact
Action
Note: Check to see if the protection switch is the result of a manual or
forced switched request for maintenance purposes, or if the system
automatically switched service to the protection ESI.
Step Action
by entering:
where
dtlprot
The system displays a list of information about the ESI circuit pack.
If there is an asterisk (*) beside the Forced Switch or Manual Switch fields,
the protection switch was requested by a craftsperson. No further action is
required. (Manual can have an (*) flash beside it when it occurred, but will be
cleared upon completion)
If there is an asterisk (*) beside the Automatic Switch field, the protection
switch was performed automatically by the system. Go to step 3.
continued
Eqp ESI
Equipment protection switch complete (continued)
Step Action
2 Display the alarm screen and check for other more serious ESI equipment
alarms.
If other alarms Then
exist see the appropriate alarm clearing procedure
do not exist go to step 3
3 Replace the faulty external synchronization interface unit. See Module

end
Eqp ESI 40
Equipment protection switch fail 4
Probable cause
A switch from the working external synchronization interface unit to the
protection external synchronization interface unit was unsuccessful.
Impact
Action
Step Action
by entering:
where
The system displays a list of information for the ESI circuit pack.
2 Check that the ESI state is in service (IS).
If the state is IS, go to step 3.
If the state is not IS, replace the faulty external synchronization interface unit.
3 Verify that the state of the redundant unit (protection ESI) is in service. The
abbreviation beside the heading Redundant Unit State should be IS-Standby.
If the Redundant Unit State is IS-Standby, replace the external
synchronization interface unit from which the protection switch was
attempted. See Module Replacement Procedures, 323-1111-547.
If the Redundant Unit State is not IS-Standby, replace the redundant external
synchronization interface unit.
end
Eqp ESI 40
Failure to lock 4
Probable cause
The external synchronization interface unit failed to lock onto a valid reference
and should be replaced.
Impact
Action
Step Action
1 Replace the failed external synchronization interface unit. See Module

Replacement Procedures, 323-1111-547. If the alarm persists, check the
timing source.
end
Eqp ESI 40
Intercard fail 4
Probable cause
An error is detected at the backplane between an OC-3/OC-12 circuit pack and
the ESI circuit pack.
The cause of the problem might be at the signal source, signal destination or
on the signal path. This could be due to a hardware fault that exists on the
transport circuit pack, the tributary circuit pack, or the backplane. Since alarms
for this fault may not be visible refer to page 3-2 of chapter 3, How to begin
trouble clearing
Note: If the shelf clock source is not set to ESI, the alarm is always minor,
not service-affecting (m, nsa).
Impact
Action
Step Action
323-1111-510.
continued
Eqp ESI
Intercard fail (continued)
Step Action

OS.0010

Network View . 1 . . . . . .
St.John's . 1 . . . . . .
DtlAlms 1.1.63
2 Next
4 Address: OC12 G1, 50 Shelf 1 C,SA
8
9 DTLALMS:
10 DtlProt
11
12
13
14 Port
15 Equipmnt
16 Facility
17
18 Help
NE 63
Time 17:35 >
slot number.
Library, 323-1111-090.
end
Eqp ESI 40
Subunit fail 4
Probable causes
An external synchronization interface unit in the external synchronization
interface carrier has failed.
In rare circumstances, this alarm (when accompanied by OC12 equipment

alarms) could also be due to an incorrect Application Select state. See chapter
10, Clearing incorrect Application Select state, for more information.
Impact
not service-affecting (m, nsa).
Action
Step Action
1 Replace the external synchronization interface circuit pack. See Module

end
Eqp ESI 40
Subunit mismatch 4
Probable cause
The circuit pack in the slot designated for the external synchronization
interface carrier does not match the provisioned circuit pack.
Note: If an external synchronization interface carrier is equipped with the

lower external synchronization interface unit only (G2) and this carrier is
removed and replaced with another type of circuit pack, the alarm
generated will be Subunit missing instead of Subunit mismatch. If the
upper external synchronization interface unit is present on the external
synchronization interface carrier when it is removed and replaced by
another type of circuit pack, the more meaningful alarm, Subunit
mismatch, is generated.
Impact
Action
Step Action
1 Replace the external synchronization interface unit with an external

synchronization interface carrier, and one or two external synchronization
interface units. See Module Replacement Procedures, 323-1111-547.
not service-affecting.
end
Eqp ESI 40
Subunit missing 4
Probable cause
A provisioned slot in the external synchronization interface carrier does not
contain an external synchronization interface unit.
Note: If an external synchronization interface carrier is equipped with the

lower external synchronization interface unit only (G2) and this carrier is
removed and replaced with another type of circuit pack, the alarm
generated will be Subunit missing instead of Subunit mismatch. If the
upper external synchronization interface unit is present on the external
synchronization interface carrier when it is removed and replaced by
another type of circuit pack, the more meaningful alarm, Subunit
mismatch, is generated.
Impact
This a major, service-affecting (M, SA) alarm (if not protectable).
Action
Step Action
1 Install an external synchronization interface unit bearing the correct product

equipment code in the empty slot. See Module Replacement Procedures,
323-1111-547.
not service-affecting.
end
Eqp ESI 40
Timing generation entry to acquire 4
Probable causes
The external synchronization interface (ESI) is in acquisition (acquire) mode.
The ESI is synchronizing with the external timing reference. This mode is
typically present on power-up or system reset, until synchronization is
achieved.

Impact
Action
end
Eqp ESI 40
Timing generation entry to fast 4
Probable causes
The external synchronization interface (ESI) is in fast acquisition mode. The
ESI is attempting to reacquire synchronization and adjusting to changes with
the external timing reference.

Impact
Action
end
Eqp ESI 40
Timing generation entry to freerun 4
Probable causes
The external synchronization interface unit is in freerun mode. The external
synchronization interface unit is not able to lock to an external timing
reference, or the target clock mode is normally provisioned to freerun. The
voltage controlled oscillator (VCO) is set at the midpoint and is providing a
stratum 3 clock. This mode is used typically during installation of the external
synchronization interface unit.

Impact
Action
Step Action
1 Verify the integrity of the ESI external timing reference signal.

2 Verify whether the target clock mode is set on normal by entering:
where
3 If required, change the target clock mode by entering:

edittarg <clock mode>
where
<clock mode> is freerun, normal, or holdover
4 If the alarm is not cleared, place the ESI circuit pack out of service and then
back in service by entering:
chgstate oos
yes
chgstate is
end
Eqp ESI 40
Timing generation entry to holdover 4
Probable cause
The external synchronization interface unit is in holdover mode as a result of
a manual request or as the result of a loss of the reference signal. See also
Timing reference interface fail in Chapter 5, Clearing facility alarms.
(Holdover mode means the external synchronization interface unit maintains
its synchronization based on the last good reference signal.)
Note: Timing stability is maintained within 0.37 ppm in ESI holdover

mode for 24 hours. Although timing stability is guaranteed to within
4.6 ppm after this period, the ESI timing remains in holdover mode until
the reference signal is restored. Therefore, the Timing generation entry to
freerun alarm is not raised.
Impact
Action
Check to see if the holdover mode is a result of a manual request or the loss of
the reference signal.
Step Action
by entering:
where
The system displays a list of information for the ESI circuit pack.
If the information on the screen lists the target clock mode as Holdover and a
test or maintenance operation is being performed, no further action is
required.
If the information on the screen lists the target clock mode as anything other
than Holdover, go to step 2.
2 Verify the connection of the external synchronization cable and the integrity
of the external reference signal.
end
Eqp Lpbk
LpbkG1 Automatic firmware download in progress
LpbkG1S Automatic firmware download in progress 4
Probable cause
The operations controller (OPC) is downloading the current firmware load to
the affected Ring loopback circuit pack. Firmware downloads are initiated
automatically by the system when a new firmware load is available or when the
firmware on an Ring loopback circuit pack has been determined to be
corrupted.
This alarm masks the Loopback Firmware/software incompatible alarm. It

is raised when the download operation is scheduled and clears when the
operation is either complete or fails. If the operation fails, the Loopback
Firmware/software incompatible alarm is raised.
Impact
Action
No action is required. This alarm exists to inform the user that a firmware
download is in progress. It clears automatically when the firmware download
is either complete or fails.
If more than one circuit pack is to be downloaded with new firmware, the
network element schedules all of the circuit packs to be downloaded. It raises
one alarm for each circuit pack. The alarms are cleared one by one as each
download operation is completed. A firmware download to a loopback
interface circuit pack can take up to 2 minutes to complete.
However, if the download operation fails, the Loopback Firmware/software

incompatible alarm is raised. In that case, proceed to the appropriate
procedure on page 4-209 and clear the Loopback Firmware/software
incompatible alarm.
end
Eqp Lpbk 40
Intercard cntrl: G1 to LpbkG1S 4
Probable cause
The intercard control link alarms indicate failures of intercard links that
convey status and control information between the transport and protection
circuit packs.
The alarm is raised when the condition is detected and clears when the
condition clears, or when either of the two circuit packs indicated by the alarm
are removed from the shelf.
OC-12 ring loopback circuit pack LpbkG1S reports this alarm and also
displays a lit red LED. This circuit pack is the one most likely at fault. All
intercard control link failures are protected by a protection switch of the ring.
Note: The green LED on OC-12 ring loopback circuit packs is lit while
the circuit packs are in service.
Impact
Action
a loss of access to the user interfaces, and the current user process is
stopped.
Note 2: When replacing an OC-12 ring loopback circuit pack, do not
inadvertently replace it with an OC-12 optical interface circuit pack. It is
possible to fit either circuit pack in the same slot.
To clear the alarm, follow one of these three procedures:
use procedure A when the alarm is raised in an idle system
use procedure B when the alarm is raised while a protection switch is in
effect on OC-12 optical interface circuit pack G1
use procedure C when the alarm is raised while a protection switch is in
effect on OC-12 optical interface circuit pack G1S
continued
Eqp Lpbk
Intercard cntrl: G1 to LpbkG1S (continued)
Procedure A
Use this procedure when the alarm is raised in an idle system, that is, no
protection switches are in effect.
Step Action
1 Replace the OC-12 ring loopback circuit pack LpbkG1S. See Module
2 Do the following.
If the alarm Then
3 Perform a forced switch on OC-12 optical interface circuit pack G1.

pr dp oc12
forced op g1
yes
4 Replace the OC-12 optical interface circuit pack G1 as follows.
CAUTION
Loss of protection switching
When an OC-12 facility is put out of service (OOS), all
functions handled by the OC-12 optical interface
circuit packs are no longer available. Such functions
include optical protection switching and LED control.
CAUTION
If the incorrect circuit pack is removed from the shelf,
it must be immediately reinserted. The facility that was
intended to be removed must be put back in service
(IS) to avoid a prolonged service interruption.
continued
Eqp Lpbk
Step Action
a. Put the OC-12 facility out of service (OOS) by entering:

facility oc12 g1
chgstate oos
yes
b. Remove the optical patchcord, or pigtail, from the shelf fiber guides to
provide sufficient slack.
c. Gently pull out the circuit pack to the extent necessary to disconnect it
from the backplane connector.
Note 1: Care must be taken when pulling out the circuit pack to prevent
causing stress to the optical patchcord or pigtail.
Note 2: Do not extract the circuit pack from the shelf while a lamp test is
running. If a circuit pack is removed during a lamp test and then reinserted
after the test, another lamp test must be run.
continued
Eqp Lpbk
Step Action
DANGER
Risk of laser radiation
When the connector dust cap is removed, laser
radiation within the limits of Class IIIb might be
present. This level of radiation is of sufficient
magnitude to cause injury to personnel and caution
must be exercised to avoid exposure.
A label similar to the following is located on the

optical interface circuit packs near the optical
connector.
Caution
Avoid direct exposure to
beam. Invisible light can
blind. Keep all optical
connectors capped.
d. Disconnect the optical patchcord, or pigtail, from the input biconic, FC, or
ST connector on the circuit pack. Install the connector dust cap.
e. Disconnect the optical patchcord, or pigtail, from the output biconic, ST,
or FC connector on the circuit pack. Install the connector dust cap.
CAUTION
Risk of damaging equipment
Do not use excessive force when inserting circuit
packs into or removing circuit packs from the shelf.
See Figure 4-1 on page 4-18 for information on
how to remove or install circuit packs.
f. Remove the circuit pack from the shelf.
g. Install the new circuit pack in the shelf without inserting it into the
backplane connector (that is, the circuit pack must not be powered). Wait
at least 20 seconds before reinserting a removed circuit pack.
continued
Eqp Lpbk
Step Action
h. Firmly push the circuit pack all the way into its position and into the
backplane connector.
Note: After insertion, the red fail LED and the yellow LOS LED turn on
for several seconds until the circuit pack achieves full operation.
i. Measure the output power. The measured power should exceed the value
specified in the following table.
Module Requirement
NT7E02FA/FB/FC/FD 4.5 dBm (intermediate reach)

NT7E02EA/EB/EC/ED 3.0 dBm (long reach)
NT7E02JA/JB/JC/JD 3.0 dBm (extended long reach)
For additional information, see Common Procedures, 323-1111-846.

j. Reconnect the optical patchcord, or pigtail, to the output connector on the
circuit pack.
k. Reconnect the optical patchcord, or pigtail, to the input connector on the
circuit pack.
Note: Depending on the signal degrade threshold setting, the Signal
degrade alarm may not clear immediately upon reconnection of the
optical patchcord to the input connector on the circuit pack (for example,
for a signal degrade threshold setting of 10 E-9, the system can take up
to 30 minutes to declare a good path and clear the alarm).
CAUTION
Risk of losing protection switching
If the OC-12 facility is not put back in service (IS),
the optical protection switching is not enabled.
l. Put the OC-12 facility back in service (IS) by entering:

facility oc12 g1
chgstate is
continued
Eqp Lpbk
Step Action
5 Release the forced switch that was applied in step 3 by entering:

pr dp oc12
forced re g1
yes
If the alarm Then
clears you have completed the procedure. If the alarm clears, the
circuit pack replaced is the source of the problem. All other
circuit packs replaced before this step are functioning properly
and need not be returned to Nortel Networks for repair.
6 Replace the overhead bridge circuit pack. See Module Replacement

7 Do the following.
If the alarm Then
9 Do the following:
If Then
continued
Eqp Lpbk
Step Action
10 Replace the processor (Proc) circuit pack. See Module Replacement

11 Do the following:
If the alarm Then
continued
Eqp Lpbk
Procedure B
Use this procedure when the alarm is raised while a protection switch is in
effect on OC-12 optical interface circuit pack G1.
Step Action

pr dp oc12
forced op g1
yes
CAUTION
CAUTION
facility oc12 g1
chgstate oos
yes
continued
Eqp Lpbk
Step Action
running. If a circuit pack is removed during a lamp test and then
reinserted after the test, another lamp test must be run.
DANGER

connector.
Caution
connectors capped.
continued
Eqp Lpbk
Step Action
CAUTION
packs into or removing circuit packs from the
shelf. See Figure 4-1 on page 4-18 for information
on how to remove or install circuit packs.
Module Requirement

circuit pack.
circuit pack.
continued
Eqp Lpbk
Step Action
CAUTION
If the OC-12 facility is not put back in service (IS), the
optical protection switching is not enabled.
15 Put the OC-12 facility back in service (IS) by entering:

facility oc12 g1
chgstate is
pr dp oc12
forced re g1
yes
If the alarm Then
17 Force the protection circuit pack group out of service:

eq lpbk
chgstate oos force
yes
18 Replace the OC-12 ring loopback circuit pack LpbkG1S as follows.
a. Gently pull out the OC-12 ring loopback circuit pack to the extent
necessary to disconnect it from the backplane connector.
Note: Do not extract the circuit pack from the shelf while a lamp test is
running. If a circuit packs is removed during a lamp test and then
continued
Eqp Lpbk
Step Action
CAUTION
b. Remove the OC-12 ring loopback circuit pack from the shelf.
c. Install a new OC-12 ring loopback circuit pack in the shelf without
inserting it into the backplane connector (that is, the circuit pack must not
be powered). Wait at least 20 seconds before reinserting a removed
circuit pack.
Note: When replacing an OC-12 ring loopback circuit pack, do not
d. Firmly push the OC-12 ring loopback circuit pack all the way into its
position and into the backplane connector.
19 Put the protection circuit pack group back in service:
eq lpbk
chgstate is
If the alarm Then
continued
Eqp Lpbk
Step Action

eq lpbk
chgstate oos force
yes
21 Replace the overhead bridge circuit pack as follows.
a. Gently pull out the circuit pack to the extent necessary to disconnect it
CAUTION
b. Remove the circuit pack from the shelf.
c. Install the new circuit pack in the shelf without inserting it into the
d. Firmly push the circuit pack all the way into its position and into the
eq lpbk
chgstate is
If the alarm Then
continued
Eqp Lpbk
Step Action
If the alarm Then

If the alarm Then
continued
Eqp Lpbk
Procedure C
effect on OC-12 optical interface circuit pack G1S.
Step Action

eq lpbk
chgstate oos force
yes
CAUTION
circuit pack.
continued
Eqp Lpbk
Step Action

eq lpbk
chgstate is
If the alarm Then

pr dp oc12
forced op g1
yes
32 Replace OC-12 optical interface circuit pack G1 as follows.
CAUTION
CAUTION
continued
Eqp Lpbk
Step Action

facility oc12 g1
chgstate oos
yes
continued
Eqp Lpbk
Step Action
DANGER

connector.
Caution
connectors capped.
continued
Eqp Lpbk
Step Action
CAUTION
at least 20 seconds before inserting a removed circuit pack.
Module Requirement

circuit pack.
circuit pack.
continued
Eqp Lpbk
Step Action
CAUTION

facility oc12 g1
chgstate is
pr dp oc12
forced re g1
yes
If the alarm Then

eq lpbk
chgstate oos force
yes
continued
Eqp Lpbk
Step Action
CAUTION
eq lpbk
chgstate is
If the alarm Then
continued
Eqp Lpbk
Step Action
If the alarm Then
and need not be returned to Nortel Networksfor repair.

If the alarm Then
end
Eqp Lpbk 40
Intercard cntrl: G1S to LpbkG1 4
Probable cause
convey status and control information between the transport and protection
circuit packs.
are removed from the shelf.
OC-12 ring loopback circuit pack LpbkG1 reports this alarm and also displays
a lit red LED. This circuit pack is the one most likely at fault. All intercard
control link failures are protected by a protection switch of the ring.
Impact
Action
stopped.
To clear the alarm, follow one of these three procedures:
effect on OC-12 optical interface circuit pack G1S
use procedure C when the alarm is raised while a protection switch is in
effect on OC-12 optical interface circuit pack G1
continued
Eqp Lpbk
Intercard cntrl: G1S to LpbkG1 (continued)
Procedure A
protection switches are in effect.
Step Action
1 Replace the OC-12 ring loopback circuit pack LpbkG1. See Module
2 Do the following.
If that alarm Then
3 Perform a forced switch on OC-12 optical interface circuit pack G1S.

pr dp oc12
forced op g1
yes
4 Replace OC-12 optical interface circuit pack G1S as follows.
CAUTION
CAUTION
continued
Eqp Lpbk
Step Action

facility oc12 g1
chgstate oos
yes
continued
Eqp Lpbk
Step Action
DANGER

connector.
Caution
connectors capped.
CAUTION
continued
Eqp Lpbk
Step Action
Module Requirement


circuit pack.
circuit pack.
CAUTION

facility oc12 g1
chgstate is
continued
Eqp Lpbk
Step Action

pr dp oc12
forced re g1
yes
If the alarm Then

7 Do the following.
If the alarm Then
9 Do the following:
If the alarm Then

continued
Eqp Lpbk
Step Action
If the alarm Then
continued
Eqp Lpbk
Procedure B
effect on OC-12 optical interface circuit pack G1S.
Step Action

pr dp oc12
forced op g1s
yes
CAUTION
CAUTION
continued
Eqp Lpbk
Step Action
Put the OC-12 facility out of service (OOS) by entering:

facility oc12 g1s
chgstate oos
yes
a. Remove the optical patchcord, or pigtail, from the shelf fiber guides to
b. Gently pull out the circuit pack to the extent necessary to disconnect it
continued
Eqp Lpbk
Step Action
DANGER

connector.
Caution
connectors capped.
c. Disconnect the optical patchcord, or pigtail, from the input biconic, FC, or
d. Disconnect the optical patchcord, or pigtail, from the output biconic, ST,
continued
Eqp Lpbk
Step Action
CAUTION
e. Remove the circuit pack from the shelf.
f. Install the new circuit pack in the shelf without inserting it into the
g. Firmly push the circuit pack all the way into its position and into the
Note: After insertion, the red fail LED and the yellow LOS LED turn on for
several seconds until the circuit pack achieves full operation.
h. Measure the output power. The measured power should exceed the value
Module Requirement

i. Reconnect the optical patchcord, or pigtail, to the output connector on the
circuit pack.
j. Reconnect the optical patchcord, or pigtail, to the input connector on the
circuit pack.
continued
Eqp Lpbk
Step Action
CAUTION
k. Put the OC-12 facility back in service (IS) by entering:

facility oc12 g1s
chgstate is
pr dp oc12
forced re g1
yes
If the alarm Then

eq lpbk
chgstate oos force
yes
17 Replace the OC-12 ring loopback circuit pack LpbkG1 as follows.
continued
Eqp Lpbk
Step Action
CAUTION
circuit pack.
eq lpbk
chgstate is
If the alarm Then

eq lpbk
chgstate oos force
yes
continued
Eqp Lpbk
Step Action

CAUTION
eq lpbk
chgstate is
If the alarm Then
continued
Eqp Lpbk
Step Action
If the alarm Then

If the alarm Then
continued
Eqp Lpbk
Procedure C
effect on OC-12 optical interface circuit pack G1.
Step Action

eq lpbk
chgstate oos force
yes
CAUTION
circuit pack.
continued
Eqp Lpbk
Step Action

eq lpbk
chgstate is
If the alarm Then

pr dp oc12
forced op g1s
yes
CAUTION
CAUTION
continued
Eqp Lpbk
Step Action

facility oc12 g1s
chgstate oos
yes
continued
Eqp Lpbk
Step Action
DANGER

connector.
Caution
connectors capped.
continued
Eqp Lpbk
Step Action
CAUTION
Module Requirement

circuit pack.
circuit pack.
continued
Eqp Lpbk
Step Action
CAUTION

facility oc12 g1s
chgstate is
pr dp oc12
forced re g1s
yes
If the alarm Then

eq lpbk
chgstate oos force
yes
continued
Eqp Lpbk
Step Action
CAUTION
eq lpbk
chgstate is
If the alarm Then
If the alarm Then
continued
Eqp Lpbk
Step Action

If the alarm Then
end
Eqp Lpbk 40
Intercard cntrl: LpbkG1 to G1 4
Probable cause
convey status and control information between the high-speed circuit packs.
This alarm is raised when the condition is detected and clears when the
are removed from the shelf. The alarm Eqp OC12 Intercard cntrl: G1 to
LpbkG1 is also raised with this alarm.
The circuit pack that has been convicted by the system software (that is, the
one with the red fail LED active) is the one most likely at fault. All intercard
Impact
Action
To clear the alarm, follow one of these two procedures:

use procedure A when the alarm is raised in an idle system. In this instance,
the red fail LED is lit on OC-12 ring loopback circuit pack LpbkG1.
effect on OC-12 optical interface circuit pack G1. In this instance, the red
fail LED is lit on OC-12 optical interface circuit pack G1.
continued
Eqp Lpbk
Intercard cntrl: LpbkG1 to G1 (continued)
Procedure A
protection switches are in effect. In this instance, the red fail LED is lit on
OC-12 ring loopback circuit pack LpbkG1.
Step Action
2 Do the following:
If the alarm Then
3 Perform a forced switch on the OC-12 optical interface circuit pack G1.
pr dp oc12
forced op g1
yes
CAUTION
CAUTION
continued
Eqp Lpbk
Step Action

facility oc12 g1
chgstate oos
yes
DANGER

connector.
Caution
connectors capped.
continued
Eqp Lpbk
Step Action
CAUTION
Module Requirement

circuit pack.
circuit pack.
continued
Eqp Lpbk
Step Action
CAUTION

facility oc12 g1
chgstate is
pr dp oc12
forced re g1
yes
If the alarm Then
continued
Eqp Lpbk
Procedure B
effect on OC-12 optical interface circuit pack G1. In this instance, the red fail
LED is lit on OC-12 optical interface circuit pack G1.
Step Action
pr dp oc12
forced op g1
yes
CAUTION
CAUTION
continued
Eqp Lpbk
Step Action

facility oc12 g1
chgstate oos
yes
continued
Eqp Lpbk
Step Action
DANGER

connector.
Caution
connectors capped.
continued
Eqp Lpbk
Step Action
CAUTION
Module Requirement

circuit pack.
circuit pack.
continued
Eqp Lpbk
Step Action
CAUTION

facility oc12 g1
chgstate is
pr dp oc12
forced re g1
yes
If the alarm Then

eq lpbk
chgstate oos force
yes
continued
Eqp Lpbk
Step Action
CAUTION
circuit pack.
eq lpbk
chgstate is
If the alarm Then
end
Eqp Lpbk 40
Intercard cntrl: LpbkG1S to G1S 4
Probable cause
are removed from the shelf. The alarm Eqp OC12 Intercard cntrl: G1S to
LpbkG1S is also raised with this alarm.
Impact
Action

the red fail LED is lit on OC-12 ring loopback circuit pack LpbkG1S.
effect on OC-12 optical interface circuit pack G1S. In this instance, the red
fail LED is lit on OC-12 optical interface circuit pack G1S.
continued
Eqp Lpbk
Intercard cntrl: LpbkG1S to G1S (continued)
Procedure A
OC-12 ring loopback circuit pack LpbkG1S.
Step Action
2 Do the following:
If the alarm Then
3 Perform a forced switch on the OC-12 optical interface circuit pack G1S.
pr dp oc12
forced op g1s
yes
4 Replace the OC-12 optical interface circuit pack G1S as follows.
CAUTION
CAUTION
continued
Eqp Lpbk
Step Action

facility oc12 g1s
chgstate oos
yes
continued
Eqp Lpbk
Step Action
DANGER

connector.
Caution
connectors capped.
CAUTION
continued
Eqp Lpbk
Step Action
Module Requirement


circuit pack.
circuit pack.
CAUTION

facility oc12 g1s
chgstate is
continued
Eqp Lpbk
Step Action

pr dp oc12
forced re g1s
yes
If the alarm Then
continued
Eqp Lpbk
Procedure B
effect on OC-12 optical interface circuit pack G1S. In this instance, the red fail
LED is lit on OC-12 optical interface circuit pack G1S.
Step Action
pr dp oc12
forced op g1s
yes
CAUTION
CAUTION
continued
Eqp Lpbk
Step Action

facility oc12 g1s
chgstate oos
yes
a. Remove the optical patchcord, or pigtail, from the shelf fiber guides to
b. Gently pull out the circuit pack to the extent necessary to disconnect it
continued
Eqp Lpbk
Step Action
DANGER

connector.
Caution
connectors capped.
c. Disconnect the optical patchcord, or pigtail, from the input biconic, FC, or
d. Disconnect the optical patchcord, or pigtail, from the output biconic, ST,
continued
Eqp Lpbk
Step Action
CAUTION
e. Remove the circuit pack from the shelf.
Module Requirement

circuit pack.
circuit pack.
continued
Eqp Lpbk
Step Action
CAUTION

facility oc12 g1s
chgstate is
pr dp oc12
forced re g1s
yes
If the alarm Then

eq lpbk
chgstate oos force
yes
continued
Eqp Lpbk
Step Action
CAUTION
circuit pack.
eq lpbk
chgstate is
If the alarm Then
end
Eqp Lpbk 40
Intercard cntrl: LpbkG1 to LpbkG1S
Intercard cntrl: LpbkG1S to LpbkG1 4
Probable cause
These intercard control link alarms indicate failures of intercard links that
convey status and control information between transport and protection circuit
packs.
These alarms are raised when the condition is detected and clear when the
are removed from the shelf. Also, these alarms appear together.
All intercard control link failures are protected by a protection switch of the
ring.
Impact
Action
stopped.
To clear these alarms, follow one of these three procedures:
use procedure A when the alarms are raised in an idle system. In this
instance, the red fail LED is lit on both OC-12 ring loopback circuit packs
LpbkG1 and LpbkG1S.
use procedure B when the alarms are raised while a protection switch is in
fail LED is lit on OC-12 ring loopback circuit pack LpbkG1S.
continued
Eqp Lpbk
Intercard cntrl: LpbkG1S to LpbkG1 (continued)
use procedure C when the alarms are raised while a protection switch is in
fail LED is lit on OC-12 ring loopback circuit pack LpbkG1.
Procedure A
Use this procedure when the alarms are raised in an idle system, that is, no
protection switches are in effect. In this instance, the red fail LED is lit on both
OC-12 ring loopback circuit packs LpbkG1 and LpbkG1S.
Step Action
2 Do the following:
If the alarm Then
4 Do the following:
If the alarm Then

continued
Eqp Lpbk
Step Action
6 Do the following:
If the alarm Then
8 Do the following:
If the alarm Then

If the alarm Then
continued
Eqp Lpbk
Procedure B
Use this procedure when the alarms are raised while a protection switch is in
LED is lit on OC-12 ring loopback circuit pack LpbkG1S.
Step Action

eq lpbk
chgstate oos force
yes
CAUTION
circuit pack.
continued
Eqp Lpbk
Step Action

eq lpbk
chgstate is
If the alarm Then

eq lpbk
chgstate oos force
yes
CAUTION
circuit pack.
continued
Eqp Lpbk
Step Action

eq lpbk
chgstate is
If the alarm Then

eq lpbk
chgstate oos force
yes
CAUTION
continued
Eqp Lpbk
Step Action

eq lpbk
chgstate is
If the alarm Then
If the alarm Then

If the alarm Then
continued
Eqp Lpbk
Procedure C
Use this procedure when the alarms are raised while a protection switch is in
LED is lit on OC-12 ring loopback circuit pack LpbkG1.
Step Action

eq lpbk
chgstate oos force
yes
CAUTION
circuit pack.
continued
Eqp Lpbk
Step Action

eq lpbk
chgstate is
If the alarm Then

eq lpbk
chgstate oos force
yes
CAUTION
circuit pack.
continued
Eqp Lpbk
Step Action

eq lpbk
chgstate is
If the alarm Then

eq lpbk
chgstate oos force
yes
CAUTION
continued
Eqp Lpbk
Step Action

eq lpbk
chgstate is
If the alarm Then
and need not be returned to Nortel Networks for repair
If the alarm Then

If the alarm Then
end
Eqp Lpbk 40
Intercard failure 4
Probable cause
A failure between the Lpbk circuit pack and another circuit pack has occurred.
Not enough information is available to fail either circuit pack so an intercard
alarm is raised.
Impact
Action
Note: For the purpose of the trouble clearing procedure, the Lpbk circuit
pack identified in the alarm is regarded as the primary circuit pack. The
other circuit pack identified in the detailed alarm screen is regarded as the
secondary circuit pack.
Step Action
1 Display the detailed alarm screen. See the procedure for displaying a detailed
alarm report in Network Surveillance Procedures, 323-1111-510.
2 Record the primary and secondary circuit pack information.
If Then
only the primary circuit pack is inactive go to step 3
only the secondary circuit pack is inactive, go to step 6
or if both the primary and secondary circuit
packs are active or inactive
3 Replace the primary Lpbk circuit pack. See Module Replacement

4 If the alarm persists, then replace the secondary circuit pack. See Module
5 Go to step 9.
6 Replace the secondary circuit pack. See Module Replacement Procedures,
continued
Eqp Lpbk
Intercard failure
Step Action
7 If the alarm persists, then replace the primary Lpbk circuit pack. See Module
8 Go to step 9.
Library, 323-1111-090.
end
Eqp Lpbk 40
LpbkG1 Circuit pack failed
LpbkG1S Circuit pack failed 4
Probable cause
An OC-12 ring loopback circuit pack has failed and should be replaced. This
alarm point is masked by the Circuit pack missing and Circuit pack mismatch
alarm points.
The red fail LED is lit on the failed OC-12 ring loopback circuit pack.
The alarm is raised as soon as the failure is detected and clears as soon as the
circuit pack is replaced.
Impact
This is a critical, service-affecting (C, SA) alarm, (loopback active).
This is a major, not service-affecting (M, nsa) alarm, (loopback not active).
Action

use procedure B when the alarm is raised while a protection switch is active
at the faulted network element
continued
Eqp Lpbk
LpbkG1 Circuit pack failed
LpbkG1S Circuit pack failed (continued)
Procedure A
Use this procedure when the alarm is raised in an idle system.
Step Action
1 Replace the failed OC-12 ring loopback circuit pack. See Module
Procedure B
Use this procedure when the alarm is raised while a protection switch is active
at the faulted network element.
Step Action
2 Force traffic away from the failed OC-12 ring loopback circuit pack.
pr dp oc12
forced op g1 or g1s
yes
3 Replace the failed OC-12 ring loopback circuit pack. See Module
4 Release the forced switch applied in step 2.
pr dp oc12
forced re g1 or g1s
yes
end
Eqp Lpbk 40
LpbkG1 Circuit pack mismatch
LpbkG1S Circuit pack mismatch 4
Probable cause
The circuit pack inserted does not match the circuit pack type expected in this
slot, that is, an OC-12 ring loopback circuit pack. This alarm point is masked
by the Circuit pack missing alarm, and masks the Circuit pack fail alarm. The
alarm is raised as soon as the mismatch is detected and clears as soon as the
condition is corrected.

an upgrade from a linear to a ring network is in progress
an OC-12 ring loopback circuit pack is swapped
an OC-12 ring loopback circuit pack identity circuitry has failed
Note 1: Many mismatch alarms could indicate that the incorrect shelf type
has been provisioned.
Note 2: The green LED on OC-12 ring loopback circuit packs is lit while
Impact
This is a critical, service-affecting (C, SA) alarm (loopback active).
This is a major, not service-affecting (M, nsa) alarm (loopback not active).
Action
Note: When inserting the OC-12 ring loopback circuit pack into its slot,
do not inadvertently insert an OC-12 optical interface circuit pack. It is
Step Action
1 Replace the mismatched circuit pack with an OC-12 ring loopback circuit
pack. See Module Replacement Procedures, 323-1111-547.
end
Eqp Lpbk 40
LpbkG1 Circuit pack missing
LpbkG1S Circuit pack missing
OHB card missing 4
Probable cause
A provisioned slot does not contain a circuit pack. This alarm point masks the
Circuit pack mismatch and Circuit pack fail alarm points.
The alarm is raised as soon as the condition is detected and clears as soon as
the correct circuit pack is inserted into the slot.
Note 2: An EQP600 log report is not generated for the overhead bridge
circuit pack removal or insertion.
Impact
This is a critical, service-affecting (C, SA) alarm (loopback active).
This is a major, not service-affecting (M, nsa) alarm (loopback not active).
Action
Step Action
1 Insert an OC-12 ring loopback circuit pack or an OC-12 overhead bridge

circuit pack in the appropriate slot. See Module Replacement Procedures,
323-1111-547.
2 Do the following:
If the alarm Then
end
Eqp Lpbk 40
LpbkG1 firmware version mismatch
LpbkG1S firmware version mismatch 4
Probable cause
The shelf is equipped with an OC-12 ring loopback circuit pack that has a
firmware load that differs from that of its mate. The red Fail LED is lit on both
circuit packs. The alarm is raised as soon as the condition is detected and clears
as soon as compatible firmware is loaded.
Note 1: This procedure is performed using the local command input (CI)
area at the network element.
Impact
This is a major, not service-affecting (M, nsa) alarm, (loopback not active).
Action
Step Action
1 Load the firmware into the OC-12 ring loopback circuit pack by entering:
quit all
mbrfwdl
forcedld <unit>
yes
where
<unit> is lpbk g1 or lpbk g1s
2 Verify the firmware load on the OC-12 ring loopback circuit packs by entering
in the local command input (CI) area:
queryfw lpbk g1
queryfw lpbk g1s
3 If the alarm persists, replace the OC-12 ring loopback circuit packs as
described in Module Replacement Procedures, 323-1111-547.
end
Eqp Lpbk 40
LpbkG1 firmware/software incompatible
LpbkG1S firmware/software incompatible 4
Probable cause
The firmware version of the indicated OC-12 ring lbpk circuit pack is
incompatible with the NE software release.
This alarm is also raised during software upgrades when:

the automatic firmware download fails
the new software release has been loaded but the new firmware load has not
yet been downloaded. In this case, the alarm is only present until the proper
firmware release is downloaded as part of the upgrade procedure.
Note: During an upgrade, the red LEDs on both Lpbk circuit pack will be
lit.
firmware load is the same as the software version or greater.
This alarm is masked by the Lpbk Circuit pack fail alarm.
Impact
Note: If one or both firmware/software incompatible alarms are raised, the

firmware mismatch alarms will not be raised. Firmware/software
incompatible alarms mask firmware version mismatch alarms.
continued
Eqp Lpbk
LpbkG1 firmware/software incompatible
LpbkG1S firmware/software incompatible (continued)
Action
Step Action
1 Do the following:
If Then
the alarm is raised no user action is required. Complete the software
as part of a upgrade procedure. See the procedure on verifying
software upgrade and downloading the firmware load of an OC-12 ring
loopback circuit pack in Commissioning Procedures,
323-1111-220
the alarm is raised download the proper loopback firmware release. See
but is not part of a the procedure on verifying and downloading the
software upgrade firmware load of an OC-12 ring loopback circuit pack
in Commissioning Procedures, 323-1111-220
you do not know see OC-3/OC-12 network element detailed ordering
which firmware equipment codes in Ordering Information,
release is required 323-1111-151
by your system
you cannot replace the circuit pack. See the procedure for
download the replacing the OC-12 ring loopback circuit pack
circuit pack (NT7E35), Module Replacement Procedures,
323-1111-547
2 If you are unable to obtain the necessary information, contact your next level
of support or your Nortel Networks support group. See About the
end
Eqp Lpbk 40
LpbkG1 Maps invalid or missing
LpbkG1S Maps invalid or missing 4
Probable cause
This alarm reports that the automatic protection switch (APS) id numbers
exchanged by the various network elements in the ring are either missing or
are invalid.
Impact
Action
Step Action
1 Download a new map by auditing the configuration data for the ring ADM. See
If the alarm Then
2 Replace the OC-12 ring loopback circuit pack indicated in the alarm
message. See Module Replacement Procedures, 323-1111-547.
end
Eqp Lpbk 40
LpbkG1 protection switching byte fail
LpbkG1S protection switching byte fail 4
Probable cause
The OC-12 ring loopback circuit pack specified in the alarm has failed.
defective OC12 ring loopback circuit pack is replaced and is returned to
service.
Impact
Action
Step Action
1 Replace the OC-12 ring loopback circuit pack indicated in the alarm. See
end
Eqp Lpbk 40
LpbkG1 STS1 intercard fail
LpbkG1S STS1 intercard fail 4
Probable cause
A parity error is detected at the backplane at one of the following locations:
between a loopback circuit pack and the tributary circuit packs (DS1, DS3,
STS-1)
between the primary transport cards (OC-12/Lpbk) and secondary
transport circuit packs (OC-12/Lpbk)
The cause of the problem might be at the signal source, signal destination, or
on the signal path. A hardware fault might exist on the transport circuit pack,
the tributary circuit pack or the backplane.
Impact
This is a minor, not service-affecting (m, nsa) alarm, (loopback not active).
Action
Step Action
323-1111-510.
continued
Eqp Lpbk
LpbkG1 STS1 intercard fail
LpbkG1S STS1 intercard fail (continued)
Step Action

OS.0009

Network View . 1 . . . . . .
St.John's . 1 . . . . . .
DtlAlms 1.1.63
2 Next
4 Address: LPBK, 13 Shelf 1 m,nsa
6 Reason: LpbkG1S STS1 intercard fail 13 Nov 95
7 NewAlms Prim/Sec: SNPQA5M2AA Slot 7 / SNPQNA52AA Slot 11 Equipment
8
9 DTLALMS:
10 DtlProt
11
12
13
14 Port
15 Equipmnt
16 Facility
17
18 Help
NE 63
Time 17:35 >
Library, 323-1111-090.
end
Eqp Lpbk 40
Ring protection suspended or unavailable 4
Probable cause
Automatic ring protection switch cannot occur. One of the following
conditions exists:
a craftsperson has put the OC-12 ring loopback circuit pack out of service,
and is performing maintenance on it
the OC-12 ring loopback circuit pack has failed
Impact
Note: Automatic ring protection switching is prevented while the

conditions exist.
Action
Step Action
1 If the OC-12 ring loopback circuit pack has been put out of service (OOS) for
maintenance, ensure that the circuit pack is returned to in service (IS) after
maintenance operations have been completed. If no maintenance activity is
underway but the circuit pack is OOS, put it back IS.
2 If no maintenance activity is underway and the OC-12 ring loopback circuit
pack is IS, check any other alarms in an attempt to identify other problems,
and clear those alarms.
end
Eqp Lpbk 40
Unable to track clock reference 4
Probable cause
the LPBK card is no longer able to track the 51-MHZ clock

a hardware fault exists on the LPBK circuit pack
Impact
Action
Step Action
1 Replace the LPBK circuit pack. See Module Replacement Procedures,

323-1111-547.
end
Eqp MIC
Alarm relay fail
E2A input fail
LED driver fail
Local craft interface port fail
Orderwire fail
Parallel telemetry relay fail
Performance monitor clock fail
Serial telemetry port fail
Time of day clock fail 4
Probable cause
The feature that is supported by the maintenance interface controller (MIC)
circuit pack has failed due to a defective maintenance interface controller
(MIC) circuit pack.
Note 1: The MIC will generate a local craft interface port fail alarm if the
terminal or modem connected to the network element is not configured at
8 bits, no parity, 1 stop bit. Ensure that both the user interface and the
modem or terminal connected to the network element are set with the
proper baud rate.
Note 2: If the above problem occurs, adjust the settings to 8 bits, no parity,
1 stop bit then restart the MIC (wait at least 5 seconds before reinsertion).
This alarm can be cleared remotely by performing a restart reload on the
affected network element.
Impact
continued
Eqp MIC
Alarm relay fail
E2A input fail
LED driver fail
Local craft interface port fail
Orderwire fail
Parallel telemetry relay fail
Performance monitor clock fail
Time of day clock fail (continued)
Action
Step Action
end
Eqp MIC 40
Circuit pack fail 4
Probable cause
Impact
Note: Protection switching, serial telemetry, parallel telemetry, and the

user interface feature might not be available.
Action
Step Action
end
Eqp MIC 40
Probable cause
The provisioned circuit pack does not match the type of circuit pack equipped
in the slot. Rules for provisioning were not followed.

Impact
Action
Step Action
1 Insert a maintenance interface controller (MIC) circuit pack in the appropriate

slot. See Module Replacement Procedures, 323-1111-547, for replacement
instructions.
end
Eqp MIC 40
Probable cause
The maintenance interface controller (MIC) circuit pack is not equipped in the
shelf.
Impact
Note: Low-speed protection switching, serial telemetry, parallel telemetry,

and the user interface feature might not be available.
Action
Step Action
1 Insert a MIC circuit pack in the appropriate slot. See Module Replacement
end
Eqp MIC 40
Firmware version mismatch 4
Probable cause
The maintenance interface controller (MIC) circuit pack has the incorrect
firmware installed.
Impact
Action
Step Action
1 Verify the version of the MIC firmware. If the MIC firmware version is incorrect,
download the correct MIC firmware version. See the procedure in the chapter
on commissioning new network elements in Commissioning, 323-1111-220.
Then go to step 2.
2 If the alarm persists, replace the mismatched maintenance interface
controller (MIC) circuit pack. See Module Replacement Procedures,
323-1111-547.
3 If the alarm continues to persist, contact your next level of support or your
Nortel Networks support group. See About the OC3/OC12 NETBM Library,
323-1111-090.
end
Eqp MIC 40
Non-volatile store fail 4
Probable cause
An attempt to access the non-volatile storage (NVS) on the maintenance
interface controller (MIC) circuit pack failed because of a defective MIC
circuit pack.
Impact
Note: Provisioned data for the shelf and circuit packs might not be stored
or retrieved.
Action
Step Action
1 Using the network element user interface, perform a shelf backup.

equipmnt sh
backupdb
yes
2 If the problem persists, replace the maintenance interface controller (MIC)
circuit pack. See Module Replacement Procedures, 323-1111-547, for
3 Using the network element user interface, perform another shelf backup.
equipmnt sh
backupdb
yes
end
Eqp MIC 40
Non-volatile store mismatch 4
Probable cause
The provisioned configuration that is stored in the maintenance interface
controller (MIC) circuit pack non-volatile store (NVS) does not match the
provisioned configuration stored on the processor circuit pack. This might be
due to a corrupt code in the processor circuit pack or to a defective MIC circuit
pack.
Impact
Note: Provisioned data for the shelf and circuit packs cannot be stored or
retrieved.
Action
Step Action
1 Using the network element user interface, perform a shelf backup.

equipmnt sh
backupdb
yes
2 If the problem persists, replace the maintenance interface controller (MIC)
circuit pack. See Module Replacement Procedures, 323-1111-547, for
3 Using the network element user interface, perform another shelf backup.
equipmnt sh
backupdb
yes
end
Eqp MIC 40
Protection switch relay fail 4
Probable cause
If there are tributary (DS3, STS-1) mappers with missing or mismatched I/O
cards, or tributary (DS1) mappers with missing or mismatched input or output
cards, an attempt to bridge or switch traffic to the protection mapper could
have failed.
Impact
Action
Step Action
1 Check to see if there are DS1 or DS3 or STS-1 missing or mismatched circuit
pack alarms also present. If there are these alarms, handle these alarms
before handling the protection switch relay fail alarm. (Refer to the
appropriate procedure to clear the missing or mismatched circuit pack
alarms).
2 Run the exerciser to bridge all working mappers to the protection mapper.
equipmnt sh
exercise
3 If the alarm persists, refer to the procedure for clearing the MIC Alarm relay
fail alarm.
end
Eqp OC3/OC12
Channel match fail 4
Probable cause
The received channel id on the protection OC-3/OC-12 optical interface circuit
pack is not as expected.
Impact
Action
Note: To clear the alarm, perform the following step-by-step procedure at
either network element.
Step Action
1 Replace the protection OC-3/OC-12 optical circuit pack identified in the

alarm. See Module Replacement Procedures, 323-1111-547.
2 Wait 20 seconds after placing the OC-3/OC-12 facility back in service.
If the alarm Then
3 Replace the OC-3/OC-12 optical circuit pack at the far-end network element
(see Module Replacement Procedures, 323-1111-547).
4 Wait 20 seconds after placing the far-end OC-3/OC-12 facility back in service.
If the alarm Then
end
Eqp OC3/OC12 40
Circuit pack fail 4
Probable causes
A defective circuit pack or a component failure exists.
In rare circumstances, this alarm (when accompanied by ESI equipment

Impact
Note: The switch to the protection channel is initiated with a traffic outage
of 60 ms maximum.
Action
Step Action
1 Reseat the circuit pack and press it firmly into position. For information on
handling circuit packs, see Module Replacement Procedures, 323-1111-547.
2 If the alarm persists, replace the defective circuit pack. See Module
end
Eqp OC3/OC12 40
Probable cause
The provisioned circuit pack does not match the type of circuit pack in the slot.
When the circuit pack is an OC-3 optical interface, this alarm is also raised to
indicate a transmission rate mismatch.
Rules for provisioning were not followed.

Impact
Action
Step Action
1 Replace the alarmed circuit pack with the proper type. See Module
end
Eqp OC3/OC12 40
Probable cause
The provisioned slot does not contain a circuit pack. The slot has been
provisioned as in service (IS) but there is no circuit pack in the slot. If a circuit
pack is in the slot, it might be defective.
Impact
Action
Step Action
1 If there is no circuit pack in the provisioned slot insert a proper unit-type in the
slot, or reconfigure that particular slot (delete equipment). See Module
2 If there is a circuit pack in the provisioned slot, replace the circuit pack.
end
Eqp OC3/OC12 40
Circuit pack reach mismatch 4
Probable cause
The working and standby OC-3/OC-12 optical interface circuit packs installed
in the shelf do not have the same reach capabilities.
Impact
Action
Step Action
1 Check with the network planner about the proper optics reach.
Note: Both intermediate and long reach optics are available on the
OC-3/OC-12 optical interface circuit packs.
2 Replace the mismatched OC-3/OC-12 optical interface circuit packs with an
OC-3/OC-12 optical interface circuit pack bearing the correct product
equipment code. See Module Replacement Procedures, 323-1111-547.
end
Eqp OC3/OC12 40
Fiber connection error 4
Probable cause
Fiber optics are swapped.
Note: This alarm is raised only if the active optical circuit pack is the
working OC-3/OC-12.
Impact
Action
Note: The fiber connection error alarm should be disabled when
connecting a TBM shelf to a non-S/DMS TransportNode product
(mid-span meet).
Step Action
1 Tx and Rx fibers for both working and protection paths must be properly
connected to the optical circuit pack and to the fiber patch panel. To verify this,
disconnect the Tx fiber from the circuit pack at the near-end and ensure that
the far-end displays an LOS alarm on the corresponding Rx circuit pack.
Reconnect the Tx fibre and perform this test on all Tx optical units to ensure
that the fibers are not crossed.
end
Eqp OC3/OC12 40
Probable cause
The OC-3/OC-12 optical interface circuit packs have the incorrect firmware
installed.
Impact
Action
Note: If a power failure occurs while this alarm is active, the system
recovery time may be impacted.
Step Action
1 Download the correct firmware version from the OPC to the OC-12 circuit
pack by entering:
mbrfwdl
forcedld oc12vtm <unit>
yes
where
<unit> is the circuit pack group in Table 4-4, Circuit pack group
identification for TBM VTM ring ADM shelf on page 4-16
The OC-12 firmware gets transferred from the OPC to the OC-12 circuit pack.
This operation takes about 15 minutes. Wait for the message: Download to
OC12 G1 (or G2) Completed to appear before proceeding.
2 Quit out of the MBRFWDL tool by entering:
quit
3 Do the following:
If the alarm Then
persists contact your next level of support or your Nortel Networks
support group. See About the OC-3/OC-12 NETBM
Library, 323-1111-090.
end
Eqp OC3/OC12 40
Forced switch request
Probable cause
A manual or forced protection switch is requested.
Impact
This is a minor, not service-affecting (m, nsa) alarm
Action
traffic).
Note 2: If you want to release a forced or manual switch, see the following
steps.
Step Action
1 Release the forced or manual switch by entering:

protectn
dtlprot <service type> [<unit>]
where
<unit> is g1 or g2 (for primary optical interface on a
(circuit pack group) linear ADM), or g1s or g2s (for secondary
optical interface on a linear ADM)
Note: The <unit> parameter is not required
for OC-12 terminals or ring ADMs.
continued
Eqp OC3/OC12
Forced switch request
Manual switch request (continued)
Step Action
For forced:
forced re <circuit pack>
yes
where
<circuit pack> is g1 or g2 (for terminal or VTM ring ADM)
g1 or g1s (for NWK ring ADM)
g1, g2, g1s, or g2s (for linear ADM)
or
g1s, g2s, g3, g4, g5, g6, g7, g8 (for OC-3
tributaries)
For manual:
manual re <circuit pack>
yes
where
<circuit pack> is g1 or g2 (for terminal or VTM ring ADM)
or
g1s, g2s, g3, g4, g5, g6, g7, g8 (for OC-3
tributaries)
Note: Any protection switching activity (lockout, forced switch, manual
switch) will not be completed unless both working and protection optical units
are provisioned and in service (IS).
end
Eqp OC3/OC12 40
Hardware/software incompatible 4
Probable cause
An incompatible OC-3 or OC-12 optics circuit pack (does not support
SONET/SDH signaling programming) was:
provisioned for SDH signal format or
inserted as a replacement for a SONET/SDH programmed optics circuit
pack or
inserted as protection for a SONET/SDH programmed optics circuit pack.
Impact
This is a critical, service-affecting (C, SA) alarm (carrying traffic).
This is a minor, not service-affecting (m, nsa) alarm (not carrying traffic).
Action
Step Action
1 Replace the alarmed circuit pack according to Module Replacement

Procedures, 323-1111-547. See Provisioning and Operations Procedures,
323-1111-310, Procedure 2-25, Provisioning SONET/SDH mix on OC-3
tributaries for circuit packs that support SONET/SDH mix signaling mode.
2 Verify that the alarm has cleared by logging in to the network element and
entering:
alarms
You can also use the OPC Alarm Monitor tool to display the active alarms
(see Network Surveillance Procedures, 323-1111-510).
3 If the alarm is still active, clear all other alarms and contact your next level of
support. You can also contact Nortel Networks according to About the OC-12
NE Library, 323-1111-090.
end
Eqp OC3/OC12 40
Intercard failure 4
Probable cause
A failure between an OC-3/OC-12 transport optical interface circuit pack and
another circuit pack has occurred. Not enough information is available to fail
either circuit pack so an intercard alarm is raised.
Impact
This is a critical, service-affecting (C, SA) alarm, if the OC-3/OC-12 circuit
pack is active (if not protectable).
This is a minor, not service-affecting (m, nsa) alarm, if the OC-3/OC-12 circuit
pack is inactive (if protectable).
Action
Note: For the purpose of the trouble clearing procedure, the transport
circuit pack identified in the alarm is regarded as the primary circuit pack.
The secondary circuit pack identified in the detailed alarm screen can be
either another transport or a non-transport circuit pack.
Step Action
1 Display the detailed alarm screen. See the procedure for displaying a detailed
alarm report in Network Surveillance Procedures, 323-1111-510.
2 Record the primary and secondary circuit pack information.
If Then
only the primary circuit pack is inactive go to step 3
only the secondary circuit pack is inactive, go to step 6
or if both the primary and secondary circuit
packs are active or inactive
3 Replace the primary OC-3/OC-12 optical interface circuit pack. See Module
4 If the alarm persists, then replace the secondary circuit pack. See Module
5 Go to step 9.
6 Replace the secondary circuit pack. See Module Replacement Procedures,
continued
Eqp OC3/OC12
Intercard failure (continued)
Step Action
7 If the alarm persists, then replace the primary OC-3/OC-12 optical interface
circuit pack. See Module Replacement Procedures, 323-1111-547.
8 Go to step 9.
Library, 323-1111-090.
end
Eqp OC3/OC12 40
Laser bias current 4
Probable cause
The laser bias current is no longer within its specified operating range, which
is required to maintain the laser output.
Impact
Note: It is assumed that these alarm points have been provisioned as

alarms and are turned on (activated). If not, these alarm points will show
up as performance alerts.
Action
Step Action
1 If this condition persists or gets worse, replace the optical interface circuit
pack. See Module Replacement Procedures, 323-1111-547, for replacement
instructions.
2 If the alarm persists, increase the threshold value by performing the
procedure for changing the facility performance threshold value. See
Performance Monitoring Procedures, 323-1111-520.
Nortel Networks support group.
end
Eqp OC3/OC12 40
Laser degrade 4
Probable cause
The laser degrade threshold has been crossed on the OC-3/OC-12 optical
interface circuit packs.
Impact
Action
Step Action
1 Replace the affected OC-3/OC-12 optical interface circuit pack. Ensure it is

switched to protection prior to removal. See Module Replacement
end
Eqp OC3/OC12 40
Lockout protection operation fail 4
Probable cause
There has been a kbyte failure on the lockout protection operation fail.
Impact
Action
Step Action
1 CAUTION
Loss of traffic
Do not remove the circuit pack without advice from
your Nortel Networks support group.
Collect as much information as possible on the steps performed leading to

this alarm.
end
Eqp OC3/OC12 40
Lockout request 4
Probable cause
There has been a request for the type of protection switch indicated by the
alarm.
Note: Lockouts are used to prevent a protection switch from a working
circuit pack to a protection circuit pack.
Impact
Action
traffic).
Note 2: If you want to release the lockout, see the following steps.
Step Action

protectn
where
for OC-12 terminals or ring ADMs
lockout re
yes
are provisioned and in service (IS).
end
Eqp OC3/OC12 40
Probable cause
A matched node connection is preprovisioned on an OC3 circuit pack.
Note: Matchnode connections are possible only on OC-12 systems.
Impact
Action
Step Action
1 Delete the preprovisioned matched-node connection or deprovision the OC-3

circuit pack and add an STS-1 circuit pack.
end
Eqp OC3/OC12 40
Protection oscillation control activated 4
Probable cause
AutoLockout has been requested. This occurs when a protection switch from
working to protection and back to working occurs six or more times in a
one-minute period. The autolockout remains active for a one-minute period.
Impact
Action
Step Action
1 Use the EQP logs to determine the level of switching activity. If the EQP logs
show that a manual or forced switch has been initiated by the user, do not
enter any more requests from the user interface. Go to step 4.
2 List the logs and alarms to determine if a Signal Degrade or Signal Fail alarm
has occurred. If either of these alarms exists, determine the cause of the
alarm and clear it using the appropriate procedure.
3 Do the following:
If the alarm Then
end
Eqp OC3/OC12 40
Probable cause
standby circuit pack.
Impact
Action
Step Action
1 Display the OC-3/OC-12 equipment screen:

Note: In a ring system, do this at each node. In a linear system, do this at the
node that raised the alarm, and at the remote node.
eq <service type> <unit>
where
<unit> is g1s g2s, g3, g4, g5, g6, g7, or g8 (for OC-3
(circuit pack group) tributaries)
is g1 or g2 (for terminal or VTM ring ADM)
The OC-3/OC-12 screen appears.

If the state field indicates Then go to
IS Trbl step 2
IS Traffic or IS step 3
continued
Eqp OC3/OC12
Step Action
2 Replace the failed OC-12 optical interface circuit packs as indicated in

3 Run the exerciser on the shelf. See the appropriate procedure in Protection
Switching Procedures, 323-1111-311.
If the alarm Then
clears end the procedure here
Note: If the alarm clears on ring systems, verify the exerciser times at this
node and at adjacent nodes to determine whether they are scheduled at least
5 minutes apart. To change the exerciser times, see the procedure for
changing the scheduled parameters of the exerciser in Protection Switching
4 Verify the state of the maintenance circuit pack:
eq mic
The MIC equipment screen appears.
If the MIC state is Then
IS-Trbl go to step 5
IS go to step 6
5 Replace the MIC as indicated in Module Replacement Procedures,

323-1111-547. End the procedure here.
6 Replace the standby (protection) OC-3 or OC-12 optical interface circuit pack,
as indicated in Module Replacement Procedures, 323-1111-547.
Library, 323-1111-090.
end
Eqp OC3/OC12 40
Protection scheme mismatch 4
Probable cause
The provisioned protection scheme on both network elements does not agree.
Impact
Action
Step Action
1 Display the state of the optical interface circuit pack by entering:

protectn
where
<unit> is g1 or g2 (for primary optical interface on
(circuit pack group) a linear ADM), or g1s or g2s (for
secondary optical interface on a linear
ADM)
Note: The <unit> parameter is not
required for OC-12 terminals or ring ADMs
protprov
The protection scheme is displayed:
1+1 (linear ADM)
two-fiber BLSR (ring NWK or VTM)
Note: The other protection scheme (1:1) is not an option.
end
Eqp OC3/OC12 40
Probable cause
The OC-12 optical interface switched to the standby unit (automatic switch,
manual, or forced).
Impact
Action
Step Action
1 If it is a maintenance (manual or forced switch) command, no further action is

required.
2 If it is due to an automatic switch, investigate with the OC-3/OC-12 facility and
equipment alarms screens on the network element user interface:
alarms
filter eq
or
filter fa
end
Eqp OC3/OC12 40
Probable cause
The protection switch failed while attempting to bridge traffic to the standby
circuit pack.
Impact
Action
Step Action
1 Display the alarm screen and check for optical interface circuit pack failures
at both the near-end and far-end network elements.
If Then
there are OC-3/OC-12 optical look up the alarm in this chapter and
interface circuit pack failures proceed accordingly
there are no OC-3/OC-12 optical go to step 2
interface circuit pack failures
continued
Eqp OC-3/OC-12
Step Action
2 Check that there are no manual or forced switches in effect by entering:

protectn
dtlprot <type> [<unit>]
where
<type> is oc3 or oc12
<unit> is not required for transport circuit packs
(circuit pack group) on a terminal or ring ADM, and is
g1 or g2 (primary transport for a linear
ADM)
g1s or g2s (secondary transport for a
linear ADM)
g1s, g2s, g3 to g8 (OC-3 tributary for a
terminal)
g3 to g8 (OC-3 tributary on a linear or ring
ADM)
3 Is there an asterisk (*) in the Manual or Forced column?

If Then go to
yes step 4
no step 6
4 Release any manual or forced switches by entering:

If manual:
manual re <unit>
If forced:
forced re <unit>
where
<unit> is the unit against which there is an
(circuit pack group) asterisk (*) in the Manual or Forced
column
5 Has this alarm cleared?

If the alarm Then
continued
Eqp OC-3/OC-12
Step Action
6 Check that no lockouts are in effect:

protectn
where
<unit> is not required for transport circuit packs on a
(circuit pack group) terminal or ring ADM, and is
g1 or g2 (primary transport for a linear ADM)
g1s or g2s (secondary transport for a linear
ADM)
g1s, g2s, g3 to g8 (OC-3 tributary for a
terminal)
g3 to g8 (OC-3 tributary on a linear or ring
ADM)

appears in the Lockout column step 7
does not appear in the Lockout column step 9

For terminal or linear ADM:
lockout re
yes
For ring ADM:
lockout re <unit>
where
<unit> is the unit entered in step 6 or p (release
(circuit pack group) protection)
continued
Eqp OC-3/OC-12
Step Action

If the alarm Then
9 Check the state of the optical facility on the circuit pack reporting the alarm,
and its mate circuit pack, as well as the optical facility on the circuit packs at
the far end, by entering:
fa <service type> <circuit pack>
where
<circuit pack> is the unit identified in the alarm, its mate, and the
circuit packs at the far end.
10 Is the operating state IS for all facilities identified in step 9?

If the operating state is Then go to
not identified step 11
identified step 13
11 Place any out of service facility back in service by entering:

fa <service type> <circuit pack>
chgstate is
where
<circuit pack> is the unit identified in step 9 as being out of
service.

If the alarm Then
13 Replace the protection OC-3/OC-12 optical interface on the shelf reporting

the alarm. See Module Replacement Procedures, 323-1111-547.
continued
Eqp OC-3/OC-12
Step Action

15 Replace the working OC-3/OC-12 optical interface on the shelf reporting the
alarm. See Module Replacement Procedures, 323-1111-547.
If the alarm Then
17 Replace the working OC-3/OC-12 optical interface on the far-end shelf. See
If the alarm Then
19 Replace the protection OC-3/OC-12 optical interface on the far-end shelf.

If the alarm Then

Library, 323-1111-090.
end
Eqp OC3/OC12 40
Protection switching byte fail/Improper APS code 4
Probable cause
The protection switching bytes that are passed around the ring are corrupted.
In LTE, the alarm refers to Protection switching byte fail.

In BLSR, the alarm refers to Improper APS code.
Impact
Action
To clear the alarm, perform the following step-by-step procedure on the optical
circuit pack against which the alarm has been raised at either network element.
Step Action
1 Replace the local OC-12 optical circuit pack identified in the alarm. See
2 Wait 20 seconds after placing the OC-12 facility back in service.
If the alarm Then
3 If the alarm persists, replace the OC-12 optical circuit pack at each network
element in the ring until the alarm clears. See Module Replacement
4 Wait 20 seconds after placing the far-end OC-12 facility back in service.
If the alarm Then

Library, 323-1111-090.
end
Eqp OC3/OC12 40
Receive fail 4
Probable cause
The optical signal receiver has failed.
Impact
Action
Step Action
1 Replace the affected circuit pack. See Module Replacement Procedures,

end
Eqp OC3/OC12 40
Probable cause
A parity error is detected at the backplane at one of the following locations:
between an OC-3/OC-12 circuit pack and the tributary circuit packs (DS1,
DS3, STS-1)
between the primary transport circuit packs (OC-12/Lbpk) and secondary
transport circuit packs (OC-12/Lpbk)
The cause of the problem might be at the signal source, signal destination or
on the signal path. This could be due to a hardware fault that exists on the
transport circuit pack, the tributary circuit pack, or the backplane.
Impact
This is a critical, service-affecting (C, SA) alarm, if the OC-3/OC-12 circuit
pack is active.
This is a minor, not service-affecting (m, nsa) alarm, if the OC-3/OC-12 circuit
pack is inactive.
Action
Step Action
323-1111-510.
continued
Eqp OC3/OC12
Step Action

OS.0010

Network View . 1 . . . . . .
St.John's . 1 . . . . . .
DtlAlms 1.1.63
2 Next
8
9 DTLALMS:
10 DtlProt
11
12
13
14 Port
15 Equipmnt
16 Facility
17
18 Help
NE 63
Time 17:35 >
slot number.
Library, 323-1111-090.
end
Eqp OC3/OC12 40
Switch mode mismatch 4
Probable cause
The provisioned switch mode on both network elements does not agree.
Impact
Action
Step Action
1 Check the provisional switch mode attribute at the local network element:
protectn
where
for OC-12 terminals or ring ADMs.
protprov
At this point the switch mode is displayed: unidirectional or bidirectional.
2 Log in to the remote network element and repeat step 1 for the other network
element.
3 If the switch modes are different, inquire with the network planner about the
proper switch mode. Once provided with the proper switch mode type:
swmode <mode>
where
<mode> is uni (unidirectional) or bi (bidirectional)
yes
end
Eqp OC3/OC12 40
Transmission rate mismatch 4
Probable cause
Transmission rate of the optical interface circuit pack does not match that of
the network element. If the circuit pack is an OC-3 optical interface, a detected
transmission rate mismatch results in the circuit pack mismatch alarm being
raised.
Impact
Action
Step Action
1 Either replace the affected circuit pack with one of the correct transmission
rate (see Module Replacement Procedures, 323-1111-547, for replacement
instructions), or change the network element transmission rate from the OPC.
end
Eqp OC3/OC12 40
Transmit fail 4
Probable cause
The optical transmitter has failed.
Impact
Action
Step Action
1 Replace the affected circuit pack. See Module Replacement Procedures,

end
Eqp OC3/OC12 40
Note: This alarm applies to Eqp OC3 only.
Probable cause
This alarm is due to one of the following causes:
a VT1.5 add-drop connection of the OC-3 is provisioned with the VT group
and VT number mismatched with the transport STS VT group and VT
number
a VT1.5 add-drop connection of another DS1/STS-1/OC-3 port is
provisioned using the transport STS channel that is allocated for VT1.5
connections of the OC-3 port and vice versa
a VT1.5 passthrough connection is provisioned using the transport STS
channel that is allocated for VT1.5 connections of the OC-3 port and vice
versa
Impact
Action
Step Action
csci
end
Eqp OC12
Automatic firmware download in progress 4
Probable cause
The processor is downloading the current firmware load to the affected VTM
circuit pack. An automatic firmware download is initiated by:
card insertion
NE restarts
resets (for example, when the firmware is corrupt)
circuit pack provisioning
a circuit pack state change (that is, OOS to IS).
After the automatic download has been initiated, the physical download takes
place only if the firmware residing on the circuit pack does not match the
software release.
This alarm masks the OC12 Firmware/software incompatible alarm. It is

raised when the download operation is scheduled and clears when the
operation is either complete or fails. If the operation fails, the OC12
Impact
Action
download operation is completed. The time to download firmware to a VTM
circuit pack varies. To reset the card takes a minimum of 2 minutes. A
compressed firmware load takes a minimum of 7 minutes to download. An
uncompressed firmware load takes minimum of 20 minutes to download
However, if the download operation fails, the OC12 Firmware/software
procedure on page 4-271 and clear the OC12 Firmware/software
incompatible alarm.
end
Eqp OC12 40
Backplane USEB inconsistent 4
Probable cause
There is a mismatch or inconsistency among USEBN, PUSEBN, uCOUB, and
RBICOUB.
Impact
Action
Step Action
1 Put the OC-12 facility out of service (OOS) by entering:

facility oc12 <unit>
chgstate oos
yes
2 Reseat the OC-12 optical interface circuit pack firmly.
3 Put the OC-12 facility back in service (IS) by entering:
facility oc12 <unit>
chgstate is
If the alarm Then
persists, or reappears periodically go to step 4
end
Eqp OC12 40
Default K Bytes 4
Probable cause
The Automatic Protection Switching (APS) bytes transmitted with the source
node ID are equal to the destination node ID.
Impact
This is a major, service-affecting (M, nsa) alarm (if not protectable).
Action
Note: This alarm can sometimes be a secondary alarm caused by taking
the far-end facility out of service. If this is the case, ensure the facility is in
service before clearing the Default K Bytes alarm.
Step Action
1 Reprovision the circuit pack in the node transmitting the default K bytes. See
2 If the alarm persists, replace the circuit pack. See Module Replacement
end
Eqp OC12 40
Entry to SONET clock acquire 4
Probable cause
The OC-12 VTM optical interface circuit pack is in acquisition (acquire)
mode. The OC-12 is synchronizing with a timing reference. This mode is
typically present on power-up or system reset, until synchronization is
achieved.
Impact
Action
end
Eqp OC12 40
Entry to SONET clock freerun 4
Probable cause
The OC-12 VTM optical interface circuit pack is in freerun mode. The OC-12
is not able to lock to a timing reference, or the target clock mode is normally
provisioned to freerun. The voltage controlled oscillator (VCO) is not locked
to a timing reference and is running at its natural frequency.
Impact
Action
Step Action
1 Clear any other alarms against OC-12 equipment or facility according to the
appropriate alarm and trouble clearing procedures in this document.
If the alarm Then
2 Verify the integrity of the OC-12 timing reference signal.

3 Verify whether the target clock mode is set on normal by entering:
eq oc12 <circuit pack>
where
4 If required, change the target clock mode by entering:

edittarg <clock mode>
where
<clock mode> is freerun, normal, or holdover
The default target clock mode is normal.

end
Eqp OC12 40
Entry to SONET clock holdover 4
Probable cause
The VTM optical interface circuit pack is in holdover mode as a result of a
manual request to do so, or as the result of a loss of the reference signal.
(Holdover mode means the OC-12 VTM optical interface circuit pack
maintains its synchronization based on the last good reference signal.)
Note: Holdover mode is entered from Normal mode when all the timing
references have been lost. The VCXO clock holds within a certain
frequency range of the last lock-in timing reference. When the reference
returns, the OC-12 VTM optical interface circuit pack (NT7E05) enters
Acquire mode. After 24 hours in holdover mode, a log is generated
indicating that the circuit pack has been in holdover for 24 hours.
Impact
Action
Check to see if the holdover mode is a result of a manual request or the loss of
the reference signal.
Step Action
1 Clear any other alarms against OC-12 equipment or facility according to the
appropriate alarm and trouble clearing procedures in this document.
If the alarm Then
continued
Eqp OC12
Entry to SONET clock holdover (continued)
Step Action
2 From the network element status screen, display the OC12 equipment screen
by entering:
eq oc12 <unit>
where
<unit> is g1 or g2
The system displays a list of information for the OC-12 circuit pack.
If the information on the screen lists the target clock mode as Holdover and a
test or maintenance operation is being performed, no further action is
required.
If the information on the screen lists the target clock mode as anything other
than Holdover, go to step 3.
3 Verify the integrity of the timing reference signal.
end
Eqp OC12 40
Fiber loopback 4
Probable cause
A transmitter fiber has been loopbacked to the receiver on the same circuit
pack.
Impact
Action
Step Action
1 Tx and Rx fibers for both working and protection paths must be properly
connected to the optical circuit pack and to the fiber patch panel. Rearrange
the fibers so that they connect to the proper transmitter and receiver.
end
Eqp OC12 40
Firmware corrupt 4
Probable cause
A firmware load running on circuit pack G1 or G2 (slot 9 or 10) is corrupted.
Impact
Action
Step Action
1 Download the correct firmware version from the OPC to the OC-12 circuit
pack by entering:
mbrfwdl
forcedld oc12vtm <unit>
yes
where
<unit> is the circuit pack group in Table 4-4, Circuit pack
group identification for TBM VTM ring ADM shelf
on page 4-16
The OC-12 firmware gets transferred from the OPC to the OC-12 circuit pack.
This operation takes about 15 minutes. Wait for the message: Download to
OC12 G1 (or G2) Completed to appear before proceeding.
2 Quit out of the MBRFWDL tool by entering:
quit
3 Do the following:
If the alarm Then
4 Replace the circuit pack. See the procedure for replacing the OC-12 optical
interface circuit pack, Module Replacement Procedures, 323-1111-547.
continued
Eqp OC12
Firmware corrupt (continued)
Step Action
5 Do the following:
If the alarm Then
support group. See About the OC-3/OC-12 NETBM
Library, 323-1111-090.
end
Eqp OC12 40
Firmware/software incompatible 4
Probable cause
There is an older OC-12 VTM circuit pack in the shelf or the firmware load in
the circuit pack is not compatible with the network element software load.
This alarm also appears during software upgrades when the automatic
firmware download fails.
Impact
Action
Step Action
1 Do the following:
If Then
as part of a upgrade procedure. See the applicable procedure on
software upgrade verifying the firmware load of an OC-12 circuit pack in
the alarm is raised download the proper firmware release. See the
but is not part of a applicable procedure on verifying the firmware load of
software upgrade an OC-12 circuit pack in Commissioning Procedures,
323-1111-220
by your system
you cannot replace the circuit pack. See the applicable procedure
download the for replacing the OC-12 circuit pack (NT7E35), Module
circuit pack Replacement Procedures, 323-1111-547
2 Do the following:
If the alarm Then
clears the procedure is complete
end
Eqp OC12 40
Firmware trap 4
Probable cause
A trap has occurred on the firmware running on the OC-12 VTM optical
interface circuit pack (NT7E05) and is shown on the HMI port. A transport
control subsystem firmware (TCSFW) trap alarm is raised when the VTM
firmware traps.
Impact
Action
Step Action
end
Eqp OC12 40
Hardware/software incompatible 4
Probable cause
The hardware vintage of the alarmed circuit pack or its release is not
compatible with the current software release.
Impact
Enabled by default.
Action
Step Action
1 Access the OC-12 equipment screen by entering:

eq oc12 <unit>
where
<unit> is g1 or g2
(circuit pack group) (the circuit pack on which the alarm was raised)
Verify that the PEC displayed in the Circuit Packs field on the OC-12
Equipment screen is not one of NT7E05AB/AC/AD or NT7E05BB/BC/BD.
2 Do the following:
If the alarm Then
3 Download the proper firmware release. See the procedure on verifying the
firmware load of an OC-12 circuit pack in Commissioning Procedures,
323-1111-220.
If the alarm Then
4 Replace the alarmed circuit pack according to Module Replacement

Procedures, 323-1111-547. The replacement circuit pack must be compatible
with the current release.
continued
Eqp OC12
Hardware/software incompatible (continued)
Step Action
5 Verify that the alarm has cleared by logging in to the network element and
entering:
alarms
You can also use the OPC Alarm Monitor tool to display the active alarms
(see Network Surveillance Procedures, 323-1111-510).
6 If the alarm is still active, clear all other active alarms. Then contact your next
level of support or Nortel Networks according to About the OC-12 NE Library,
323-1111-090.
end
Eqp OC12 40
Intercard cntrl: G1 to LpbkG1 4
Probable cause
are removed from the shelf. The alarm Eqp Lpbk Intercard cntrl: LpbkG1 to
G1 is also raised with this alarm.
Impact
This is a major, not service-affecting (M, nsa), alarm.
Action

the red fail LED is lit on OC-12 ring loopback circuit pack LpbkG1.
fail LED is lit on OC-12 optical interface circuit pack G1.
continued
Eqp OC12
Intercard cntrl: G1 to LpbkG1 (continued)
Procedure A
OC-12 ring loopback circuit pack LpbkG1.
Step Action
2 Do the following:
If the alarm Then
pr dp oc12
forced op g1
yes
CAUTION
CAUTION
continued
Eqp OC12
Step Action

facility oc12 g1
chgstate oos
yes
continued
Eqp OC12
Step Action
DANGER

connector.
Caution
connectors capped.
CAUTION
continued
Eqp OC12
Step Action
Module Requirement


circuit pack.
circuit pack.
CAUTION

facility oc12 g1
chgstate is
continued
Eqp OC12
Step Action
5 Release the forced switch that was applied in step 3.

pr dp oc12
forced re g1
yes
If the alarm Then
continued
Eqp OC12
Procedure B
LED is lit on OC-12 optical interface circuit pack G1.
Step Action
pr dp oc12
forced op g1
yes
CAUTION
CAUTION
continued
Eqp OC12
Step Action

facility oc12 g1
chgstate oos
yes
DANGER

connector.
Caution
connectors capped.
continued
Eqp OC12
Step Action
CAUTION
See Figure 4-1 on page 4-18 for information on how
to remove or install circuit packs.
Module Requirement

circuit pack.
circuit pack.
continued
Eqp OC12
Step Action
CAUTION

facility oc12 g1
chgstate is
pr dp oc12
forced re g1
yes
If the alarm Then

eq lpbk
chgstate oos force
yes
continued
Eqp OC12
Step Action

CAUTION
circuit pack.
continued
Eqp OC12
Step Action

eq lpbk
chgstate is
If the alarm Then
end
Eqp OC12 40
Intercard cntrl: G1S to LpbkG1S 4
Probable cause
are removed from the shelf. The alarm Eqp Lpbk Intercard cntrl: LpbkG1S to
G1S is also raised with this alarm.
Impact
Action

the red fail LED is lit on OC-12 ring loopback circuit pack LpbkG1S.
fail LED is lit on OC-12 optical interface circuit pack G1S.
continued
Eqp OC12
Intercard cntrl: G1S to LpbkG1S (continued)
Procedure A
OC-12 ring loopback circuit pack LpbkG1S.
Step Action
2 Do the following:
If the alarm Then
pr dp oc12
forced op g1s
yes
a. Replace the OC-12 optical interface circuit pack G1S as follows.
CAUTION
When an OC-12 facility is put out of service
(OOS), all functions handled by the OC-12 optical
interface circuit packs are no longer available.
Such functions include optical protection
switching and LED control.
CAUTION
If the incorrect circuit pack is removed from the
shelf, it must be immediately reinserted. The
facility that was intended to be removed must be
put back in service (IS) to avoid a prolonged
service interruption.
continued
Eqp OC12
Step Action

facility oc12 g1s
chgstate oos
yes
DANGER

connector.
Caution
connectors capped.
continued
Eqp OC12
Step Action
CAUTION
Module Requirement

circuit pack.
continued
Eqp OC12
Step Action

circuit pack.
CAUTION

facility oc12 g1s
chgstate is
pr dp oc12
forced re g1s
yes
If the alarm Then
continued
Eqp OC12
Procedure B
LED is lit on OC-12 optical interface circuit pack G1S.
Step Action
pr dp oc12
forced op g1s
yes
CAUTION
CAUTION
continued
Eqp OC12
Step Action

facility oc12 g1s
chgstate oos
yes
DANGER

connector.
Caution
connectors capped.
continued
Eqp OC12
Step Action
CAUTION
Remove the circuit pack from the shelf.
Module Requirement

circuit pack.
continued
Eqp OC12
Step Action

circuit pack.
CAUTION

facility oc12 g1s
chgstate is
pr dp oc12
forced op g1s
yes
If the alarm Then

eq lpbk
chgstate oos force
yes
continued
Eqp OC12
Step Action

CAUTION
circuit pack.
continued
Eqp OC12
Step Action

eq lpbk
chgstate is
If the alarm Then
end
Eqp OC12 40
Intercard serial link fail 4
Probable cause
The serial link used by the micro-controllers equipped on the circuit packs G1
and G2 (in slots 9 and 10) has failed.
Impact
Action
Step Action
323-1111-510.
OS.0010

Network View . 1 . . . . . .
St.John's . 1 . . . . . .
DtlAlms 1.1.63
2 Next
8
9 DTLALMS:
10 DtlProt
11
12
13
14 Port
15 Equipmnt
16 Facility
17
18 Help
NE 63
Time 17:35 >
continued
Eqp OC12
Intercard serial link fail (continued)
Step Action
2 Do the following:
If the alarm is raised against Then replace
G1 in slot 9 G2 in slot 10
G2 in slot 10 G1 in slot 9
See the appropriate procedure in Module Replacement Procedures,

323-1111-547.
Library, 323-1111-090.
end
Eqp OC12 40
Invalid neighbor detected 4
Probable cause
This alarm reports discrepancies between automatic protection switch (APS)
id numbers exchanged by the various network elements in the ring and the list
of valid APS id numbers stored in each network element. This alarm is masked
by the Rx AIS alarm for OC-12 optical interface circuit packs.
Each network element in the ring is assigned an APSID number. Each network
element also contains a list of these numbers, with the numbers listed in the
order in which the network element appears relative to its own position in the
ring. Each network element therefore knows which network elements are
adjacent to it (that is, which network elements are its neighbors).
During the idle state, the network elements at each end of each fiber in the ring
continuously exchange their APSID numbers. The expected detailed alarms
screen gives the actual and expected NE IDs. If during this exchange a received
number does not match the corresponding number for that network element in
the stored list (and all other information is correct), the Invalid neighbour
alarm is raised after a 3-second hold-off period.
The number can be corrected either at the sending node or in the node list of
the receiving node. The alarm clears immediately when the detected APSID
matches the list of valid network elements.
This alarm is raised when a protection circuit pack group is out of service (oos)
(the alarm Ring protection suspended or not available is also present) and
either:
an OC-12 protection switch is initiated or is active. The alarm is either
raised at the network element where the switch is initiated or is active, or
in the case where the switch was active and a protection circuit pack group
at an intermediate network element is placed out of service, the alarm is
raised at both network elements either side of the network element with the
OOS protection circuit pack group.
the routine exerciser is run. The alarm is raised at the network element
where the exerciser is run.
When the protection circuit pack group is placed back in service, the alarm
should clear. If it persists, check that the two fiber pairs were not swapped
during installation.
continued
Eqp OC12
Invalid neighbor detected (continued)
Impact
Action
Step Action
1 Return the protection circuit pack group to in service.

If the alarm Then
2 Download valid APS ID numbers by auditing the configuration data for all ring
ADMs. See Provisioning and Operations Procedures, 323-1111-310.
If the alarm Then
3 Check that the two fiber pairs were not swapped during installation. If they
were installed incorrectly, reinstall the fiber pairs correctly, (see Installation
Procedures, 323-1111-201).
end
Eqp OC12 40
Lockout protection request 4
Probable cause
alarm.
Note: This alarm applies to ring configurations only.
Impact
Action
traffic).
Step Action

protectn
dtlprot oc12
lockout re p <circuit pack>
where
<circuit pack> is g1 or g2 (for VTM ring ADM) (see note 2)

are provisioned and in service.
end
Eqp OC12 40
Lockout working request 4
Probable cause
alarm.
Note: This alarm applies to ring configurations only.
Impact
Action
traffic).
Step Action

protectn
dtlprot oc12 <unit>
lockout re w <circuit pack>
where
<unit> is g1 or g2 (for VTM ring ADM)
(circuit pack group) g1 or g1s (for NWK ring ADM)

are provisioned and in service.
end
Eqp OC12 40
Maps invalid 4
Probable cause
The OC-12 circuit pack does not have a valid node map.
Impact
Action
Step Action
1 Audit the configuration data. See the chapter Managing OC-12 rings
inProvisioning and Operations Procedures, 323-1111-310.
If the alarm Then
2 Send the configuration data to the ring ADM. See the chapter Managing
OC-12 rings inProvisioning and Operations Procedures, 323-1111-310.
If the alarm Then
3 Verify and, if necessary, download firmware to the OC-12 VTM optical

interface circuit pack. See the Commissioning a new network element in
Commissioning Procedures, 323-1111-220.
If the alarm Then
4 Re-seat the optical interface circuit pack.

If the alarm Then
continued
Eqp OC12
Maps invalid (continued)
Step Action
5 Replace the optical interface circuit pack. See the Circuit Pack Replacement
chapter in Module Replacement Procedures, 323-1111-547.
If the alarm Then

Library, 323-1111-090.
end
Eqp OC12 40
NE id mismatch 4
Probable cause
Three consecutive and identical frames contain a source node (K2 bit 2-4) that
can be described as follows:
it does not match a neighbors node ID as defined in the destination nodes
resident ring map, or
it does not map to an entry in the ring node map
Impact
Action
Step Action
1 Audit configuration from OPC. See Provisioning and Operations Procedures,

323-1111-310.
If the alarm Then
2 Replace the OC-12 circuit pack against which the alarm has been raised or
against the source (far-end circuit pack) of the NE id mismatch. See Module
If the alarm Then
Library, 323-1111-090.
end
Eqp OC12 40
Performance monitor clock fail 4
Probable cause
The one-second clock used for performance monitoring from the MIC circuit
pack has failed. This could be caused by the failure of either the OC-12 circuit
pack or the MIC circuit pack.
Impact
Action
Step Action
1 Replace the maintenance interface controller circuit pack. See Module

If the alarm Then
2 Replace the OC-12 circuit pack. See Module Replacement Procedures,

If Then
Library, 323-1111-090.
end
Eqp OC12 40
Protection switch complete (remote request) 4
Probable cause
A protection switch is operated from the remote end (caused by a manual,
automatic, or forced switch).
Impact
Action
Step Action
1 Release the protection switch at the local end to releases the protection
switch at the remote end and drop the alarm. Refer to Protection Switching
end
Eqp OC12 40
Protection switching byte/APS code inconsistent 4
Probable cause
Over 12 successive frames, starting with the last frame containing previously
consistent APS code, no three consecutive frames contain identical APS bytes.
In LTE, the alarm refers to Protection switching byte inconsistent.
In BLSR, the alarm refers to APS code inconsistent.
Impact
Action
Step Action
1 Replace the maintenance interface controller circuit pack. See Module

If the alarm Then

If Then
Library, 323-1111-090.
end
Eqp OC12 40
Reference input clock fail 4
Probable cause
A 51 MHz reference clock from the mate OC-12 circuit pack has failed. The
faulty clock cannot be determined.
Impact
Action
Step Action

If the alarm Then
2 Replace the mate OC-12 circuit pack. See Module Replacement Procedures,
If the alarm Then
Nortel Networks support group. About the OC-3/OC-12 NETBM Library,
323-1111-090.
end
Eqp OC12 40
STS12 ring link parity error 4
Probable cause
For VTM Ring systems, a parity error has occurred on the STS-12 ring link
between the G1 and G2 circuit packs. Either the OC-12 G1 or the G2 optics
can be at fault.
This alarm causes the network element to automatically initiate a manual

switch against the OC-12 G1 optics. The manual switch is initiated against the
G1 optics regardless of whether the parity error is detected on the G1 or G2
circuit pack. The manual switch causes the system clock and drop traffic to be
selected from the OC-12 G2 optics.
The ring link (R-link) passes incoming optical traffic between OC-12 VTM
circuit packs. All 12 STS-1 signals received by one VTM circuit pack are
passed to the mate circuit pack (from OC-12 G1 to G2 or from G2 to G1).
Before the manual switch, the "STS12 ring link parity error" alarm is raised as
a critical, service-affecting alarm.
If the STS12 ring link parity error alarm is raised against OC-12 G1 optics, it
is lowered to a minor, not service-affecting alarm as the result of the manual
switch. Any affected traffic is restored. The Manual switch request alarm and
Protection switch complete warning alarm are also active.
If the STS12 ring link parity error alarm is raised against OC-12 G2 optics, the
automatic manual switch against G1 restores the traffic. However, the STS12
ring link parity error alarm remains critical, service affecting. The Manual
switch request alarm and Protection switch complete warning alarm are also
active.
The following conditions apply to this feature:

The feature is not active during a ring reconfiguration because there is a
forced switch active on the ring.
The feature is disabled while the network element is in the passthrough
state because of an active OC-12 protection switch. It automatically
enables again when the switch enters the wait-to-restore (WTR) state. This
temporary disabling of the feature prevents ring segmentation.
As with user-initiated manual switches, the automatically initiated manual
switch preempts the WTR state.
continued
Eqp OC12
STS12 ring link parity error (continued)
Step Action
Traffic is always switched to the G2 circuit pack regardless of which circuit

pack detected the fault. Any higher priority switch on the G2 circuit pack
preempts the manual switch.
CAUTION
Risk of service interruption
If the automatic manual switch is released before corrective
actions have removed the cause of the "STS12 R-link parity
error", traffic will be affected.
Impact
If the G2 optics is convicted, this is a critical, service-affecting (C, SA) alarm.
If the G1 optics is convicted, this is a minor, not service-affecting (m, nsa)
alarm.
Action
Step Action
1 Remove the OC-12 circuit pack in the G1 position. Do not follow the
replacement procedure in Module Replacement Procedures, 323-1111-547.
CAUTION
If you follow the replacement procedures, you can
cause a service interruption.
2 Insert the replacement circuit pack and wait 20 seconds for the circuit pack to
complete its initialization.
3 Check the active alarms by entering:
alarms
4 If the alarm Then
continued
Eqp OC12
STS12 ring link parity error (continued)
Step Action
5 While the G1 OC-12 circuit pack is still in the 5-minute wait-to-restore period,
perform a forced switch on the G2 OC-12 circuit pack. For protection-switch
instructions, see Protection Switching Procedures, 323-1111-311..
CAUTION
If the forced switch on the G2 circuit pack is not
operated within 5 minutes, traffic will be affected.
6 Replace the G2 OC-12 circuit pack. See Module Replacement Procedures,

Wait 20 seconds for the G2 circuit pack to complete its initialization.
7 Check the active alarms by entering:
alarms
8 If the alarm Then go to
clears step 9
persists step 10
9 Release the forced switch according to Protection Switching Procedures,

323-1111-311.
10 If the alarm continues to persist, leave the forced switch in place and contact
end
Eqp OC12 40
Synchronization clock fail 4
Probable cause
The 2-kHz synchronization clock input from the master OC-12 circuit pack
that sources the clock to the shelf has failed.
Impact
Action
Step Action

If the alarm Then
2 Replace the mate OC-12 circuit pack. See Module Replacement Procedures,
If the alarm Then
Library, 323-1111-090.
end
Eqp OC12 40
System clock reference fail 4
Probable cause
The OC-12 unit detected that it is no longer receiving a 51-MHz clock
reference. One of the following conditions exists:
the ESI unit is not transmitting a 51-MHz clock reference
the network element is VT linetimed and the circuit pack at the far end is
out of service or missing
Impact
Action
Note: Before replacing a circuit pack, try to clear the alarm by reinstalling
the same circuit pack, ensuring the circuit pack is protected before
removing and reseating it. If the alarm persists, replace the circuit pack.
Step Action
1 Change the OC-12 target clock mode to freerun. See Provisioning and
If the alarm Then
clears go to step 2
2 Switch the clock reference back to normal or the provisioned reference. End
the procedure here.
3 Replace the optical interface circuit pack. See Module Replacement
end
Eqp OC12 40
Unable to track clock reference 4
Probable causes
A hardware fault exists on the OC-12 circuit pack.
In rare circumstances, this alarm (when accompanied by ESI equipment

Impact
Action
Step Action

323-1111-547.
end
Eqp OPC
OPC alarm(s) active 4
Probable cause
This alarm indicates that the OPC associated with this pointer alarm has one
or more active alarms. The OPC can be either the primary or backup OPC, as
provisioned. This alarm becomes active at only a single designated network
element.
The pointer alarm becomes active on the designated network element when an
alarm becomes active on the OPC. It clears automatically 30 seconds after all
active alarms on the OPC are cleared or when there is an activity switch to the
peer OPC.
If the OPC and the network element with the pointer alarm lose data
communications association, the pointer alarm cannot become active or clear
until you restore the association.
Impact
Minor, non-service affecting (by default).
Disabled by default (provisionable only using the OPC Alarm Provisioning
tool).
The severity and service code of this alarm is user-provisionable (see

Provisioning and Operations Procedures, 323-1111-310).
Action
Step Action
1 Clear the root cause of the associated alarm on the OPC according to the
appropriate procedure in the chapter 9 Clearing equipment alarms.
end
Eqp OPC 40
OPC circuit pack fail 4
Probable cause
Impact
Action
Step Action
1 Replace the OPC circuit pack. See Module Replacement Procedures,

323-1111-547.
end
Eqp OPC 40
OPC circuit pack mismatch 4
Probable cause
The provisioned circuit pack does not match the type of circuit pack equipped
in the slot. Rules for provisioning were not followed.

Impact
Action
Step Action
1 Insert an OPC into the appropriate slot. See Module Replacement

Procedures, 323-1111-547. Also see the procedures for clearing a network
element and OPC trouble log in Log Report Manual, 323-1111-840.
end
Eqp OPC 40
OPC circuit pack missing 4
Probable cause
The OPC is not equipped in the shelf.
Impact
Action
Step Action
1 Insert an OPC into the appropriate slot. See Module Replacement

Procedures, 323-1111-547. Also see the procedures for clearing a network
element and OPC trouble log in Log Report Manual, 323-1111-840.
end
Eqp OPC 40
OPC CNET loss of signal 4
Probable cause
The OPC can no longer communicate through the CNet port. The possible
cause is an unsuccessful loopback test.
Impact
Action
Step Action
1 Verify the CNet cabling if any (that is, if two or more shelves are collocated at
the same site) at each connection point on each shelf.
CAUTION
The CNet LAN bus should not exceed 400 feet in
length.
When using CNet cables to connect shelves, ensure

that shelves are grounded to the same transmission
ground reference.
Two CNet connectors are located on the left side connector field of the TBM
shelves.
Note: If unused, these connectors should be terminated with NTE5072
terminators.
2 If this does not clear the alarm, replace the OPC. See Module Replacement
end
Eqp OPC 40
OPC Ethernet loss of signal 4
Probable cause
The OPC can no longer communicate through the Ethernet port.
Impact
Action
Step Action
1 Check that the X-terminal or workstation is powered on.

If the terminal or workstation is Then
not powered on turn on the power and check that the alarm
clears
powered on go to step 2
2 Check the X-terminal or workstation modem for proper connection and

operation.
If the modem is Then
not operational or is no properly connected correct the problem and check
that the alarm clears
operational go to step 3
3 Check the condition of the Ethernet cable and its connections to the OPC
module and the X-terminal or workstation.
If the Ethernet cable is Then
faulty or improperly connected correct the fault and verify that the
alarm has cleared
not faulty and is properly connected go to step 4
continued
Eqp OPC
OPC Ethernet loss of signal (continued)
Step Action
4 Verify that the Ethernet ports are properly configured for the OPC and the
X-terminal or workstation.
If the Ethernet port is Then
not configured correctly correct the configuration and verify that the
alarm has cleared.
configured correctly go to step 5
5 Replace the OPC module. See Module Replacement Procedures,

323-1111-547.
end
Eqp OPC 40
OPC hardware reset 4
Probable cause
The OPC is in the process of performing a software reset. The possible cause
is an OPC shutdown.
Impact
Action
Step Action
1 Do the following:
If the alarm Then
clears no action is required. The alarm is a status indication.
persists replace the OPC circuit pack. See Module
end
Eqp OPC 40
OPC OAM software fail 4
Probable cause
This alarm is raised when the network element processor loses communication
with the OPC on the shelf for more than seven minutes.
At one minute intervals, an network element software fail watchdog

establishes a link with the OPC and sends an ARE_YOU_OK message to the
OPC application software. The OPC application software responds with an
I_AM_OK message. If the OPC application software fails to respond, the
network element software increments a counter by one. If the counter value
reaches seven, the OPC OAM software fail alarm is raised. If the OPC
application software responds before the seventh count, the counter is reset to
zero.
The OPC application software can fail to respond for the following reasons:
an OPC failure
the OPC has been placed out of service
the OPC has been shut down
the OPC is rebooting
a software upgrade is in progress
The alarm is raised at the network element where the processor-to-OPC
communication has been lost.
Impact
continued
Eqp OPC
OPC OAM software fail (continued)
Action
Step Action
1 Verify whether a user-initiated action such as a software upgrade, placing the

OPC out of service, shutting down the OPC, or rebooting the OPC, has
occurred. If this is the case, the alarm clears at the conclusion of these
actions and when the OPC has been placed back in service. If this is not the
case, the OPC might have failed. Go to step 2.
2 Verify that the OPC has failed. This is indicated by an unsuccessful attempt
to log onto the OPC, and by the OPC red Fail LED being lit. If the OPC has
failed, and there is a backup OPC, replace the failed OPC. See Module
Replacement Procedures, 323-1111-547. If there is no backup OPC, or if the
OPC has not failed, go to step 3.
3 If the OPC has failed and there is no backup OPC, or if the alarm persists after
OPC replacement, or if there is no apparent reason for the alarm, contact
end
Eqp Proc
Both C-Bus access fail 4
Probable cause
The processor (Proc) circuit pack has lost communication with both the
communication Bus-A and the communication Bus-B.
Impact
This is a critical and service-affecting (C, SA) alarm.
Action
Step Action
1 Replace the Proc circuit pack. See Module Replacement Procedures,

323-1111-547.
end
Eqp Proc 40
C-Bus-A access fail 4
Probable cause
The processor (Proc) circuit pack has lost communication with
communication Bus-A.
Impact
Action
Step Action

323-1111-547.
end
Eqp Proc 40
C-Bus-B access fail 4
Probable cause
The processor (Proc) circuit pack has lost communication with
communication Bus-B.
Impact
Action
Step Action

323-1111-547.
end
Eqp Proc 40
Communication processor fail 4
Probable cause
The communication processor on the processor (Proc) circuit pack has failed.
Impact
Action
Step Action

323-1111-547.
end
Eqp Proc 40
Degraded communication processor 4
Probable cause
The communications processor on the processor (Proc) circuit pack is faulty.
Impact
This is a minor, service-affecting (m, nsa) alarm.
Action
Step Action

323-1111-547.
end
Eqp Proc 40
Degraded host processor 4
Probable cause
The host processor on the processor (Proc) circuit pack is faulty.
Impact
Action
Step Action

323-1111-547.
end
Eqp Proc 40
Degraded master CBIC-A
Degraded master CBIC-B 4
Probable cause
The processor circuit pack has detected an error on the master CBIC chip.
Impact
Action
Step Action
1 Remove the shelf cover. See Module Replacement Procedures,

323-1111-547.
1.1 Remove any cables connected to the user interface ports one at a time.
These ports include: User Interface Port 1, OPC Port 1, OPC Port 2 (all on
Side Interconnect Left) as well as User Interface Port 2 (on the Local Access
Craft Panel).
If the alarm Then
clears replace the cable that was just removed; you have
completed the procedure
persists continue to remove other cables and check for alarm
clearing; if all cables have been checked, go to step 2
2 Verify that each DS1 input or output circuit pack and each DS3 input/output
circuit pack is fully seated by firmly pushing each one of them.
Note: Do not pull out I/O circuit packs or cables as this affects corresponding
traffic.
3 Reseat the processor circuit pack firmly.
If the alarm Then
persists, or reappears periodically go to step 4
4 Replace the processor circuit pack. See Module Replacement Procedures,

323-1111-547.
If the alarm Then
end
Eqp Proc 40
Firmware prom fail 4
Probable cause
The programmable read only memory on the processor (Proc) circuit pack
failed.
Impact
Action
Step Action
1 Replace the processor circuit pack. See Module Replacement Procedures,

323-1111-547.
end
Eqp Proc 40
Probable cause
The processor (Proc) circuit pack has the incorrect firmware installed.
Impact
Action
Step Action
1 Replace the mismatched Proc. See Module Replacement Procedures,

323-1111-547.
end
Eqp Proc 40
Interprocessor comm fail 4
Probable cause
A communications link internal to the processor (Proc) circuit pack has failed.
Impact
Action
Step Action
Note: Do not perform a shelf restart within 5 minutes of making a

provisioning change, or within 5 minutes of replacing a circuit pack.
1 Perform a shelf reload restart. See Provisioning and Operations Procedures,
323-1111-310. If the problem persists, go to step 2.
2 Replace the Processor circuit pack. See Module Replacement Procedures,
323-1111-547.
Library, 323-1111-090.
end
Eqp Remt
Remote critical 4
Probable cause
A critical alarm condition exists on a remote node of a S/DMS TransportNode
Express system connected to the TBM through OC-3 tributaries.
Impact
Action
Step Action
1 Log onto the remote node indicated by the Alarm Details. Determine the
alarm condition and see S/DMS TransportNode Express Alarm and Trouble
Clearing Procedures, 323-1051-543.
end
Eqp Remt 40
Remote major 4
Probable cause
A major alarm condition exists on a remote node of a S/DMS TransportNode
Impact
Action
Step Action
end
Eqp Remt 40
Remote minor 4
Probable cause
A minor alarm condition exists on a remote node of a S/DMS TransportNode
Impact
Action
Step Action
end
Eqp Remt 40
Remote subnetwork 4
Probable cause
A minor alarm condition exists on a remote node of a S/DMS TransportNode
Impact
Action
Step Action
end
Eqp STS-1 only

Automatic firmware download in progress 4
Probable cause
The processor is downloading the current firmware load to the affected STS-1
interface circuit pack. An automatic firmware download is initiated by:
card insertion
NE restarts
resets (for example, when the firmware is corrupt)
circuit pack provisioning
a circuit pack state change (that is, OOS to IS).
This alarm masks the STS-1 Firmware/software incompatible alarm. It is
raised when the download operation is scheduled and clears when the
operation is either complete or fails. If the operation fails, the STS-1
Impact
Action
download operation is completed. A firmware download to an STS-1 interface
circuit pack can take up to 2 minutes to complete.
However, if the download operation fails, the STS-1 Firmware/software

procedure on page 4-349 and clear the STS-1 Firmware/software
incompatible alarm.
end
Eqp STS1 40
BNC I/O card 3 fail -DoNotRemove 4
Probable cause
Impact
This is a minor, not service-affecting, (m, nsa) alarm.
Action
Step Action
1 CAUTION
Do not remove BNC input/output (I/O) circuit packs
without advice from your Nortel Networks support
group.
A BNC input/output (I/O) circuit pack has failed and needs replacing. Contact
end
Eqp STS1 40
BNC I/O card 3 mismatch 4
Probable cause
The circuit pack inserted into the shelf I/O slot does not match the provisioned
circuit pack type.
Impact
Action
Step Action
1 CAUTION
Do not remove another BNC input/output (I/O) circuit
pack, as it will cause the loss of an STS-1 signal.
Replace the circuit pack in the I/O slot with a BNC input/output (I/O) circuit
pack.
STS-1 facilities are provisioned.
2 Ensure BNC input/output (I/O) circuit packs are firmly pushed into the
backplane of the shelf.
end
Eqp STS1 40
BNC I/O card 3 missing 4
Probable cause
A provisioned shelf I/O slot does not contain a BNC input/output (I/O) circuit
pack.
Impact
Action
Step Action
1 Insert a BNC input/output (I/O) circuit pack into the slot.

STS-1 facilities are provisioned.
2 Ensure BNC input/output (I/O) circuit packs are firmly pushed into the
backplane of the shelf.
end
Eqp STS1 40
Circuit pack fail 4
Probable cause
There is a defective circuit pack.
Impact
Action
Step Action
1 Replace the defective circuit pack. See Module Replacement Procedures,

end
Eqp STS1 40
Probable cause

Impact
Action
Step Action
1 For an in-service circuit pack, replace the alarmed circuit pack with the proper
type. See Module Replacement Procedures, 323-1111-547, for replacement
instructions.
end
Eqp STS1 40
Probable cause
A provisioned slot does not contain a circuit pack.
Impact
Action
Step Action
1 Insert an STS-1 electrical interface circuit pack into the slot. See Module
end
Eqp STS1 40
Firmware failure 4
Probable cause
A problem exists with the STS-1 electrical interface circuit pack firmware.
Impact
Action
Step Action
1 Reseat the STS-1 electrical interface circuit pack. See Module Replacement
If the alarm Then
is raised again go to step 2
2 Download firmware to the STS-1 electrical interface circuit pack. See the
procedure on verifying the firmware load of an STS-1 electrical interface
circuit pack in Commissioning Procedures, 323-1111-220.
If Then
you cannot download firmware to go to step 3
the circuit pack
the alarm is raised again go to step 3
the alarm clears you have completed the procedure
3 Replace the STS-1 electrical interface circuit pack. See Module Replacement
If the alarm Then
is raised again go to step 4
end
Eqp STS1 40
Firmware/software incompatible 4
Probable cause
The firmware on the STS-1 circuit pack is older than the baseline required by
the software.
This alarm is also raised during software upgrades when the automatic
firmware download fails.
Note: This alarm is raised during software upgrades that require updated
firmware. It can also be raised if an STS-1 circuit pack is replaced by
another which has firmware not meeting the baseline required by the
software.
Impact
Action
Step Action
1 Do the following:
If Then
as part of a upgrade procedure. See the procedure on verifying
software upgrade the firmware load of an STS-1 circuit pack in
the alarm is raised download the proper STS-1 firmware release. See the
but is not part of a procedure on verifying the firmware load of an STS-1
software upgrade circuit pack in Commissioning Procedures,
323-1111-220
by your system
you cannot replace the circuit pack. See the procedure for
download to the replacing the STS-1 circuit pack circuit pack in Module
circuit pack Replacement Procedures, 323-1111-547
2 If you are unable to obtain the necessary information, contact your next level
of support or your Nortel Networks support group. See About the
end
Eqp STS1 40
Probable cause
A forced switch command has been requested for the STS-1 electrical
interface circuit pack.
Impact
Action
traffic).

end
Eqp STS1 40
Lockout request 4
Probable cause
A lockout command has been issued for the STS-1 electrical interface circuit
pack.
Impact
Action
traffic).

end
Eqp STS1 40
Probable cause
A manual switch command has been requested for the STS-1 electrical
interface circuit pack.
Impact
Action
end
Eqp STS1 40
Protection equipment unavailable 4
Probable cause
If the STS-1 protection equipment is put out of service (OOS) the system will
raise the alarm STS-1 protection unavailable, equipment OOS. This alarm is
Impact
Action
Step Action
1 Put the STS-1 protection circuit pack back in service (IS) to clear the alarm.
2 Disable the alarm from the Alarm Provisioning screen of the STS-1 Protection
end
Eqp STS1 40
Probable cause
protection circuit pack. This indicates that a hardware failure exists on the
STS-1 protection path. If an STS-1 working circuit pack requires protection
and a failure exists on the protection path, this alarm is raised as a major alarm
since traffic is lost. If no protection is required, the unprotected severity is
minor.
Impact
requested.
Action
Note 2: This alarm can be a result of different circuit packs that make up
the protection path. This procedure has the user start by replacing the
circuit packs that least affects service. Once the circuit pack that causes the
alarm has been found, all previously replaced circuit packs need not be
Step Action
eq mic
OOS step 2

chgstate is
continued
Eqp STS1
Step Action
4 Run the STS-1 exerciser:
equipmnt sh
exercise
If the alarm is Then
cleared you have completed the procedure

equipmnt sh
exercise
7 Replace the STS-1 protection circuit pack equipped in slot 3. See Module
equipmnt sh
exercise
continued
Eqp STS1
Step Action
9 The alarm can be a result of parity errors on the STS-1 links between the
transport interface cards and the STS-1 protection circuit pack. To determine
if this is the case, use the FLT700 logs. Type the following at the NE UI prompt:
logutil
open flt
back
Type back until all the logs, which have been generated since the last
exerciser run, are viewed.
If the logs Then
(slots 5, 7, 9, or 10) and the STS-1 protection circuit
pack (slot 3)
slots (slots 5, 7, 9, or 10) and the STS-1 protection
circuit pack (slot 3)
equipmnt sh
exercise
end
Eqp STS1 40
Probable cause
An STS-1 electrical interface circuit pack is switched on the standby unit
(caused by a manual, automatic, or forced switch).
Impact
Action
Step Action

protectn
dtlprot sts1
2 Do the following:
If Then
a manual operation (manual or the STS-1 circuit pack is being tested
forced switch) has been
performed
an automatic switch has been investigate with the STS-1 equipment
performed alarm screen on the network element
user interface by entering the following
commands
alarms
filter eq
specification.
facility sts1 <unit> <port #>
where
<unit> is g1 to g4
<port #> is 1 to 3
end
Eqp STS1 40
Probable cause
An STS-1 electrical interface circuit pack as a result of an automatic switch, a
forced switch or a manual switch, is denied access to the protection bus.
Impact
Action
Step Action
1 Is the operating state of the protection circuit pack IS?

equipmnt sts1 p
If the operating state is Then go to
not IS step 2
IS step 3
2 Display the alarm screen and check for other more severe STS1 equipment
alarms or MIC equipment alarms.
alarms
If Then
another STS1 equipment alarm appears look up the alarm in this chapter
a MIC equipment alarm appears look up the alarm in this chapter
continued
Eqp STS1
Step Action
eq mic
OOS step 4
IS step 6

chgstate is
IS step 6
6 Replace the protection STS-1 electrical interface circuit pack. See Module
end
Eqp STS1 40
Probable causes
A parity error is detected at the backplane between an STS1 mapper and a
transport circuit pack (OC-3/OC-12 or Lpbk circuit pack). The cause of the
problem might be at the signal source, signal destination, or on the signal path.
This could be due to a hardware fault that exists on the STS1 mapper, the
transport circuit pack or the backplane.

information.
Impact
are met: the system is in an unprotected configuration and a parity error is
detected between an active transport circuit pack and a STS1 mapper.
This is a minor, not service-affecting (m, nsa) alarm if the system is in a

protected configuration or a parity error is detected between an inactive
transport circuit pack and an STS1 mapper.
Action
Step Action
323-1111-510.
continued
Eqp STS1
Step Action

OS.0011

Network View . 1 . . . . . .
St.John's . 1 . . . . . .
DtlAlms 1.1.63
2 Next
4 Address: STS1 G1, 13 Shelf 1 m.nsa
6 Reason: STS1 intercard fail 16 Feb 95
7 NewAlms Prim/Sec: SNIUKJ04AA Slot 11 / SNTRVNB2AA Slot 9 Equipment
8
9 DTLALMS:
10 DtlProt
11
12
13
14 Port
15 Equipmnt
16 Facility
17
18 Help
NE 63
Time 17:35 >
slot number.
Library, 323-1111-090.
end
Eqp STS1
STS1 protection unavailable, equipment OOS 4
Probable cause
The protection STS1 interface is provisioned to be out of service. Therefore
STS1 tributary protection is unavailable.
Impact
Enabled by default.
Action
requires protection for one or more STS1 interfaces step 2
does not require protection for any STS1 interfaces step 3
2 Provision the protection STS-1 interface to be in service by entering:

equipmnt sts1 p
chgstate is
3 Delete the protection STS-1 interface by entering:
equipmnt sts1 p
delete
yes
end
Eqp STS1 40
Switcher circuit pack mismatch 4
Probable cause
The circuit pack inserted into the shelf does not match the provisioned circuit
pack type.
Impact
Action
Step Action
1 Replace the circuit pack in the slot with a protection switcher circuit pack. See
instructions.
end
Eqp STS1 40
Switcher circuit pack missing 4
Probable cause
The protection switcher circuit pack is missing.
Impact
Action
Step Action
1 Insert a protection switcher circuit pack in the reserved slot. See Module
end
Eqp STS1 40
Traffic problem detected 4
Probable cause
The protection STS-1 electrical interface circuit pack is not available to
provide protection. One of the following conditions exists:
the protection STS-1 electrical interface circuit pack is already protecting
another STS-1 circuit pack group
the protection STS-1 electrical interface circuit pack is missing
the protection STS-1 electrical interface circuit pack is faulty
the protection switcher circuit pack is missing
the protection group is locked out
the maintenance interface controller (MIC) circuit pack is missing or out
of service
Impact
Action
Step Action
1 Display the STS-1 protection screen. Enter:

pr
dtlprot sts1
The STS-1 detailed protection screen appears.
continued
Eqp STS1
Step Action
2 Check for an active protection event against one of the working STS-1
groups. Do this by looking for an asterisk (*) beside any of the STS-1 groups,
under the headings: Forced or AutoSw.
If Then
a Forced switch is active release the protection switch
an AutoSwitch is active fix the problem that caused the
switch to occur, then switch back to
the working STS-1 circuit pack
there are no active protection switches go to step 3
3 From the same screen as in step 2, check for a lockout against the protection
STS-1 circuit pack. Do this by looking for an asterisk (*) beside the P
(protection) group, under the Lockout column.
If the protection mapper Then
is locked out release the lockout
is not locked out go to step 4
4 From the same screen as in step 2, check for a lockout against the failed
STS-1 circuit pack. Do this by looking for an asterisk (*) beside the failed
mappers circuit pack group, under the Lockout column.
If the failed mapper Then
is locked out release the lockout
is not locked out go to step 5
5 Ensure that the protection STS-1 electrical interface circuit pack is properly
installed in shelf slot 3, and that the Active LED is lit.
At this stage, protection is now available and this alarm should clear. Other
alarms should be raised, for instance, STS1 circuit pack fail.
If this is Then
not the case go to step 6
the case clear the new alarms
continued
Eqp STS1
Step Action
6 Ensure that the protection STS-1 electrical interface circuit pack is

provisioned and is in service.
If this is Then
not the case place the circuit pack in service
the case go to step 7
7 Ensure that the protection switcher circuit pack is properly installed in shelf
slot 2.
If this is Then
not the case correct the situation
8 Ensure that the MIC is properly installed, is in service, and that the Active LED
is lit.
If this is Then
not the case correct the situation
9 Replace the protection STS-1 electrical interface circuit pack. See Module
If the alarm Then
Note: The alarm may persist until protection is available for the STS-1 card.
end
Eqp STS1 40
Probable cause
a VT1.5 add-drop connection of the STS-1 is provisioned with the VT

group and VT number mismatched with the transport STS VT group and
VT number
a VT1.5 add-drop connection of another DS1/STS-1/OC-3 port is
provisioned using the transport STS channel that is allocated for VT1.5
connections of the STS-1 port and vice versa
a VT1.5 passthrough connection is provisioned using the transport STS
channel that is allocated for VT1.5 connections of the STS-1 port and vice
versa
Impact
Action
Step Action
csci
end
5-1
Clearing facility alarms 5-

This chapter describes how to locate and clear Transport Bandwidth Manager
(TBM) facility alarms using the network element user interface.
Note 1: See Provisioning and Operations Procedures, 323-1111-310, for

procedures that include the following: provisioning alarms;
activating/deactivating (placing in/out of service) and adding/deleting
facilities and circuit packs; and operating/releasing loopbacks; and
managing OC-12 rings and setting up STS connections at the OPC.
Note 2: See Protection Switching Procedures, 323-1111-311, for
procedures that include operating or releasing lockouts, and operating or
releasing forced and manual switches.
Note 3: A trouble clearing procedure might call for a circuit pack to be
replaced. For the maintenance interface controller (MIC) circuit pack,
removal of the circuit pack causes a loss of access to the user interfaces,
and the current user process is stopped. For the VTM interface circuit pack,
diagnostics must be run before the circuit pack is replaced.
Note 4: See Common Procedures, 323-1111-846, for procedures that
include connecting to and using the network element user interface.
Note 5: The service code provided in the impact section of the alarm
generated, the software determines if the alarm is in fact service affecting
and under certain rare circumstances the software displays a different
service code than the one documented. Under these rare circumstances, the
software provides the correct service code and you should disregard the
documented service code.
5-2 Clearing facility alarms
List of facility alarms

Fac COMM alarms
Alarm Page
Sonet DCC link fail 5-12
Sonet DCC performance degraded 5-14
Fac DS1 alarms
Alarm Page

Loopback 5-19
Path Rx SAS threshold 1, 2 5-20
Rx AIS 5-23
Rx Yellow 5-30
RTU DTAU test in progress 5-31
STS1 Rx RFI 5-38
VT Rx AIS 5-42
VT Path Rx ALS threshold 1, 2 5-43
VT Path Rx ES threshold 1, 2 5-43
Fac DS1 alarms
Alarm Page
VT Rx loss of pointer 5-44
VT Rx RFI 5-45
VT Rx unequipped 5-46
Fac DS3 alarms
Alarm Page
Frequency out of range 5-48
Loopback 5-52
Path Rx AISS threshold 1, 2 5-53
Path Rx SEFS threshold 1, 2 5-53
Path Tx AISS threshold 1, 2 5-56
Path Tx CV threshold 1, 2 5-56
Path Tx ES threshold 1, 2 5-56
Path Tx SEFS threshold 1, 2 5-56
Path Tx SES threshold 1, 2 5-56
Path Tx UAS threshold 1, 2 5-56
Rx AIS 5-61
Rx Parity error rate>10E-6 5-68
Fac DS3 alarms
Alarm Page
STS1 Rx RFI 5-76
Tx AIS 5-80
Tx loss of frame 5-81
Fac ESI alarms
Alarm Page
Bipolar violation 5-83
Degraded clock carrier 5-84
Loss of frame 5-85
Loss of signal 5-86
Rx AIS 5-87
Tx AIS 5-88
Fac OC3/OC12 alarms
Alarm Page
Line RFI 5-94
Loss of frame 5-105
Rx AIS 5-110
Sect Rx CV threshold 1, 2 5-95
Sect Rx ES threshold 1, 2 5-95
Sect Rx SES threshold 1, 2 5-95
Sect Rx SEFS threshold 1, 2 5-95
Fac OC3/OC12 alarms
Alarm Page
Signal degrade 5-117
Signal fail 5-123
STS1 Rx AIS 5-129
Fac OC12 alarms
Alarm Page
Inter-ring both feeds fail (matched nodes on rings only) 5-133
Inter-ring forced switch request 5-135
Inter-ring protection switch complete 5-136
Inter-ring lockout request 5-141
Inter-ring manual switch request 5-142
Line FE CV threshold 1, 2 5-143
Line FE ES threshold 1, 2 5-143
Line FE SES threshold 1, 2 5-143
Line FE UAS threshold 1, 2 5-143
Rx Inter-ring secondary feed fail (matched nodes on rings only) 5-145
Section Rx optical power threshold 5-147
STS1 path FE CV threshold 1, 2 5-148
STS1 path FE ES threshold 1, 2 5-148
STS1 path FE SES threshold 1, 2 5-148
STS1 path FE UAS threshold 1, 2 5-148
STS1 path Rx CV threshold 1, 2 5-150
STS1 path Rx ES threshold 1, 2 5-150
STS1 path Rx SES threshold 1, 2 5-150
STS1 path Rx UAS threshold 1, 2 5-150
STS1 Rx RFI 5-157
Fac OC12 alarms
Alarm Page
Tx loss of Inter-ring secondary feed (matched nodes on rings only) 5-162
Fac Path alarms
Note: Fac Path alarms have been moved to Fac OC12 and Fac DS1 sections.
Fac REMT alarms
Alarm Page
First-Alert connection down 5-164
Fac STS1 alarms

Alarm Page
Line Rx BCV threshold 1, 2 5-166
Line Rx BES threshold 1, 2 5-166
Line Rx BSES threshold 1, 2 5-166
Loopback 5-169
Rx Line AIS 5-179
Rx RFI 5-180
STS1 Rx AIS 5-181
Fac Tgen alarms (timing generation alarms)
Alarm Page
Reference forced switch request 5-186
Reference manual switch request 5-187
Reference switch complete 5-188
Reference switch fail 5-189
Reference tables: Circuit pack group identification

Table 5-1 on page 5-8 to Table 5-4 on page 5-11 provide circuit pack group
(unit) identification as follows:
Table 5-1: Circuit pack group identification for TBM terminal shelf
Table 5-2: Circuit pack group identification for TBM linear ADM shelf
Table 5-3: Circuit pack group identification for TBM NWK ring ADM shelf
Table 5-4: Circuit pack group identification for TBM VTM ring ADM shelf
Note: When a procedure indicates that you should enter the circuit pack
group, enter a specific group such as G1, or enter all to select all circuit
pack groups of that type.
Table 5-1
Circuit pack group identification for TBM terminal shelf
STS-12
transport
2 G2
4 G4
5 G1S G2
6
7 G2S
8
9 G1
10 G2
11 G5 G5 G1 G4
12 G6
13 G6 G7 G2
14 G8
15 G7 G9 G3 G5
16 G10 G6
17 G8 G11 G4
18 G12
19 P
20 See
Note
21 A
22
23 G1 (upper)
G2 (lower)
number.
Table 5-2
Circuit pack group identification for TBM linear ADM shelf
STS-12
transport
2 G2
4 G4
5 G1S
6
7 G2S
8
9 G1
10 G2
11 G5 G5 G1 G4
12 G6
13 G6 G7 G2
14 G8
15 G7 G9 G3 G5
16 G10 G6
17 G8 G11 G4
18 G12
19 P
20 See
Note
21 A
22
23 G1 (upper)
G2 (lower)
number.
Table 5-3
Circuit pack group identification for TBM NWK ring ADM shelf
OC-12 Loopback OC-3 DS1 DS3 ESI Pro MIC OPC
STS-12 tributary STS-1 c
transpor
t
2 G2
4 G4
5 G1S
6
7 LpbkG1S
8
9 G1
10 LpbkG1
11 G5 G5 G1 G4
12 G6
13 G6 G7 G2
14 G8
15 G7 G9 G3 G5
16 G10 G6
17 G8 G11 G4
18 G12
19 P
20 See
Not
e
21 A
22
23 G1
(upper)
G2
(lower)
number.
Table 5-4
Circuit pack group identification for TBM VTM ring ADM shelf
OC-12 OC-3 DS1 DS3 ESI Pro MIC OPC
transport tributary STS-1 c
(See Note) (See Note)
2 G2
4 G4
5 G1S G2
6
7 G2S
8
9 G1
10 G2
11 G5 G5 G1 G4
12 G6
13 G6 G7 G2
14 G8
15 G7 G9 G3 G5
16 G10 G6
17 G8 G11 G4
18 G12
19 P
20 See
Note 2
21 A
22
23 G1 (upper)
G2 (lower)
number.
Fac Comm
Sonet DCC link fail
Probable cause
The network element cannot communicate through the SONET section data
communications channel (SDCC), bytes D1D3 of the section overhead. One
of the following conditions exist:
a defective processor circuit pack (Proc)
a defective or missing maintenance interface controller (MIC) circuit pack
a defective optical interface circuit pack
lack of end-to-end continuity
a cut fiber
crossed fibers
the upstream network element has its corresponding SDCC port
provisioned to be out of service or incorrectly provisioned
Note: If this alarm is raised in a system connected to an OC-48 ADM node
(except when connected to quadrant 4 of a linear ADM), ignore it since
data communications are not supported. Disable this alarm in this
configuration to prevent it from being raised again.
Impact
Action
Step Action
1 Verify that end-to-end continuity over the optical interfaces exists.

2 Verify that both near-end and far-end network elements are similarly
configured. If one is configured for diverse routing, then the other should be
also.
3 Verify that the upstream network element has its corresponding SDCC port
in service and its parameters (such as frame size) provisioned to match the
local OC-12 SDCC port.
4 Clear any optical interface facility alarms that might exist at either end network
element.
5 If any optical interface, Proc, or MIC circuit pack has its fail LED (red) on,
replace the card. Refer to Module Replacement Procedures, 323-1111-547.
6 Verify the continuity of the OC-12 fiber lines.
continued
Fac Comm
Sonet DCC link fail (continued)
Step Action
7 If the alarm persists, contact your next level of support or your Nortel
Networks support group. See About the OC-3/OC-12 NETBM Library,
323-1111-090.
end
Fac COMM
Sonet DCC performance degraded
Probable cause
The performance of the SONET DCC channels has fallen below the expected
value. This is indicated by the occurrence of CRC errors or aborted frames.
The net result is a degraded performance of the DCC link. One of the following
conditions exist:
a defective processor circuit pack (Proc)
a defective or missing maintenance interface controller (MIC) circuit pack)
a defective optical interface circuit pack
lack of end-to-end continuity
cut or crossed fibers
Impact
Action
Step Action
1 Verify that end-to-end continuity over the optical interfaces exists.

2 Verify that both near-end and far-end network elements are similarly
configured. If one is configured for diverse routing, then the other should be
also.
3 Clear any optical interface facility alarms that might exist at either end network
element.
continued
Fac COMM
Sonet DCC performance degraded (continued)
Step Action
4 If any optical interface, Proc, or MIC circuit pack has its fail LED (red) on,
replace the card. Refer to Module Replacement Procedures, 323-1111-547.
5 Verify the continuity of the OC-12 fiber lines.
323-1111-090.
end
Fac DS1
Line Rx CV threshold 1, 2
Line Rx ES threshold 1, 2
Line Rx SES threshold 1, 2
Probable cause
a defective DS1 input cable or connector
a problem with the source of the DS1 signal
Impact
Note 1: It is assumed that these alarm points are provisioned as alarms

and are turned ON (activated). If not, these alarm points show up as
performance alerts.
Note 2: These alarms indicate that errors in excess of a provisioned level
were observed. Threshold crossing alarms automatically clear at the end of
the provisioned interval.
Action
Note: This procedure is service affecting.
Step Action
1
CAUTION
Risk of service loss
When you unplug a DS1 cable, you lose the 14 DS1s
passing through that cable.
In the top level of the shelf, locate the DS1 input circuit pack allocated to the
port reporting the bipolar violations. Examine the DS1 cable connected to its
connector. Ensure that the correct connector is used and is well secured.
continued
Fac DS1
Step Action
Do the following:
If Then
the cable is split or damaged replace it
the problem persists go to step 2
2 Unplug the DS1 cable from the DS1 input circuit pack and connect it to a DS1
receiver test set. Verify that a DS1 signal is present on that cable and that the
test set does not detect any errors.
Do the following:
If Then
no errors are detected reconnect the DS1 cable and go to step 4
errors are detected go to step 3
3 Do the following:
If Then
errors were detected at the DS1 verify the signal at the source with the
Input circuit pack (in step 2) DS1 test set
errors are detected repair the source generating the DS1
signal.
no errors are detected the DS1 cable needs to be repaired. Go
to step 7.
4
CAUTION
When you remove a DS1 input circuit pack, you lose
14 DS1s associated with that pack.
At this point, the DS1 cable and the DS1 signal source have been verified. If
errors are still occurring, then replace the DS1 Input circuit pack attributed to
this port. See Module Replacement Procedures, 323-1111-547, for
continued
Fac DS1
Step Action
5 If the problem persists, replace the DS1 circuit pack attributed to this port.
See Module Replacement Procedures, 323-1111-547, for replacement
instructions.
6 If the problem continues to persist, contact your next level of support or your
Library, 323-1111-090.
end
Fac DS1
Loopback
Probable cause
A DS1 loopback has been operated and is currently active.
Impact
Action
Step Action
1 This is a normal indication when the loopback is ON for testing purposes.

2 To clear the alarm, release the loopback by entering:
facility ds1 <unit> <port #>
where
<unit> is g1 to g12, or all
<port #> is 1 to 14, or all
loopback re
3 If you want to put the DS1 facility back in service, enter:
chgstate is
See Provisioning and Operations Procedures, 323-1111-310, for more
details.
end
Fac DS1
Path Rx CV threshold 1, 2
Path Rx ES threshold 1, 2
Path Rx SAS threshold 1, 2
Path Rx SES threshold 1, 2
Path Rx UAS threshold 1, 2
Probable cause
A DS1 Rx performance monitoring parameter threshold has been crossed. One
of the following conditions exists:
a faulty DS1 mapper circuit pack
a faulty DS1 input circuit pack
Impact
Note 1: It is assumed that these thresholds are provisioned as alarms and

are turned ON (activated). If they are not provisioned as alarms, these
alarm points show up as performance alerts.
Action
continued
Fac DS1
Path Rx UAS threshold 1, 2 (continued)
Step Action
1
CAUTION
Do the following:
If Then
Do the following:
If Then
3 Do the following:
If Then
signal
no errors are detected repair the DS1 cable. Go to step 6.
continued
Fac DS1
Step Action
4
CAUTION
errors still occur, then replace the DS1 Input circuit pack attributed to this port.
instructions.
instructions.
Library, 323-1111-090.
end
Fac DS1
Rx AIS
Probable cause
The local DS1 VT mapper circuit pack is receiving an alarm indication signal
(AIS) from the equipment at the far end of the DS1 cable.

the DS1 source at the far end of the DS1 cable is experiencing signal
problems and is sending a DS1 alarm indication signal (AIS)
there is an equipment failure at the far end of the DS1 cable
This alarm can be masked by the automatic in-service (AINS) feature.
Impact
Action
Step Action
1 Check the DS1 equipment and the DS1 facility at the DS1 source located at
the far end of the DS1 cable. Resolve any failures on the DS1 equipment or
DS1 facilities.
end
Fac DS1
Rx bipolar violation >10E-3
Probable cause
Bipolar violations have been detected on the incoming DS1 line. One of the
following conditions exists:
a faulty cable connection
a defective cable
a defective DS1 VT mapper circuit pack
a defective DS1 input circuit pack
Impact
Note: Traffic is degraded due to a previous section failure.
Action
Step Action
1
CAUTION
Do the following:
If Then
continued
Fac DS1
Rx bipolar violation >10E-3 (continued)
Step Action
Do the following:
If Then
3 Do the following:
If Then
signal
no errors are detected repair the DS1 cable. Go to step 6
4
CAUTION
errors are still occurring, then replace the DS1 Input circuit pack attributed to
instructions.
Library, 323-1111-090.
end
Fac DS1
Rx loss of frame
Probable cause
The DS1 frame cannot be detected on the incoming DS1. One of the following
conditions exists:
defective DS1 source equipment
a defective cable/connection
Impact
Action
Step Action
1
CAUTION
port reporting the loss of frame. Examine the DS1 cable connected to its
connector. Ensure you use and secure the correct connector.
Do the following:
If Then
test set does not detect loss of frame.
continued
Fac DS1
Rx loss of frame (continued)
Step Action
Do the following:
If Then
no loss of frame is detected reconnect the DS1 cable and go to step 4
a loss of frame is detected go to step 3
3 Do the following:
If Then
a loss of frame was detected at verify the signal at the source with the
the DS1 Input circuit pack (in DS1 test set
step 2)
a loss of frame is detected repair the source generating the DS1
signal
no loss of frame is detected repair the DS1 cable
Go to step 6.
4
CAUTION
loss of frame still occurs, then replace the DS1 Input circuit pack attributed to
instructions.
Library, 323-1111-090.
end
Fac DS1
Rx loss of signal
Probable cause
The DS1 VT mapper circuit pack is not detecting any DS1 input signal. One
defective DS1 source equipment
Impact
Action
Step Action
1
CAUTION
port reporting the loss of signal. Examine the DS1 cable connected to its
Do the following:
If Then
test set does not detect loss of signal.
continued
Fac DS1
Rx loss of signal (continued)
Step Action
Do the following:
If Then
no loss of signal is detected reconnect the DS1 cable and go to step 4
a loss of signal is detected go to step 3
3 Do the following:
If Then
a loss of signal was detected at verify the signal at the source with the DS1
the DS1 Input circuit pack (in test set
step 2)
a loss of signal is detected repair the source generating the DS1
signal
no loss of signal is detected repair the DS1 cable. Go to step 6.
4
CAUTION
loss of signal still occurs, then replace the DS1 Input circuit pack attributed to
instructions.
Library, 323-1111-090.
end
Fac DS1
Rx Yellow
Probable cause
A problem has been detected on the DS1 signal at the far end of the DS1 cable.
Impact
Action
Step Action
1 Check the line specification (including line coding, line build out, and framing
format) of the alarmed DS1 facility by entering:
fac ds1 <unit> <port #>
where
<unit> is g1 to g12
<port #> is 1 to 14
The line specifications should be the same as those of the far-end NE

(although LBO can be different depending on the length of the DS1 cable). If
there is any discrepancy, go to step 2.
2 Consult your network manager to get the right specifications and change
them accordingly by entering:
chgstate oos
yes
edit
<command>
where
<command> is lcoding, lbo, framefmt, alarmenc, or synchr
3 Put the facility back in service (IS) by entering:

quit
chgstate is
end
Fac DS1
RTU DTAU test in progress
Probable cause
This alarm becomes active against the DS1 facility when the remote test unit
(RTU) is active.
Impact
This is a minor, not service-affecting (w, nsa) alarm.
Action
No action is required. The alarm clears automatically when the test is
complete.
end
Fac DS1 50
STS1 Rx path trace failure 5
Probable cause
mismatched STS-1 connection
incompatible path trace
defective DS1 VT mapper circuit pack
defective OC-3/OC-12 optical interface circuit pack
network element is recovering from being powered down
Impact
Action
Step Action
1 Verify that the path trace provisioning data is correct. See the flowchart,
Figure 5-1, on page 5-37.
Do the following:
If a path trace alarm is Then
raised go to step 2
not raised you have completed the procedure
2 Do the following:
If the network element is Then
powering up wait for the network element to fully recover.
Then go to step 1.
not powering up go to step 3
continued
Fac DS1
STS1 Rx path trace failure (continued)
Step Action
3 Do the following:
If you have access to Then
the OPC UI retrieve path trace data. See the procedure on
retrieving path trace data values using the OPC
Connection Manager tool in Systems
the NE UI retrieve path trace data. See the procedure on
retrieving path trace data values using the
PTSAMPLER tool in Systems Administration
the TL1 interface retrieve path trace data. See the Retrieve Path
Trace (rtrv-pthtrc) command in TL1 Interface
Description, 323-1111-190.
Verify that the path trace values have been provisioned properly (that is, the
Tx path trace value at one end of the connection is exactly the same as the
expected Rx path trace value at the opposite end of the connection). Go to
step 4.
4 Do the following:
If path trace data is Then
provisioned properly go to step 5
not provisioned properly correct path trace provisioned data. See the
procedure in System Administration
Procedures, 323-1111-302. Go to step 1.
5 Do the following:
If the actual Rx path trace value Then
contains ? go to step 6
does not contain ? go to step 7
6 Do the following:
If an OC3 or STS-1 tributary is Then
on the STS-1 path go to step 8
not on the STS-1 path go to step 9
continued
Fac DS1
Step Action
7 Do the following:
If the actual Rx path trace Then
value
matches the expected Rx if alarm persists, contact your next level of
path trace value support or your Nortel Networks support group.
See About the OC-3/OC-12 NETBM Library,
323-1111-090.
does not match the check the connection services data and
expected Rx path trace connection. See the procedures in Provisioning
value and Operations Procedures, 323-1111-310.
Check the physical cabling on the STS path.
See the procedure in Installation Procedures,
323-1111-201.
Go to step 1.
8 The path trace format supports the 64-byte ASCII character string: the first 62
characters of the string are user provisionable and the remaining two are
reserved for line feed and carriage return characters provided by the system.
If the far end Then
complies with the path trace go to step 9
format
does not comply with the path disable path trace at both ends of the STS
trace format connection.
See the procedure in Provisioning and
You have completed the procedure.
continued
Fac DS1
Step Action
9 Do the following:
If both tributary ends are Then
the same tributary type perform the hardware isolation procedures.
Go to step 10.
If alarm persists, contact your next level of
support or your Nortel Networks support group.
not the same tributary check the connection services data and
type connection. See the procedure in Provisioning
and Operations Procedures, 323-1111-310.
Check the physical cabling on the STS path.
See the procedure in Installation Procedures,
323-1111-201.
Go to step 1
Hardware isolation procedure

10 Verify that the near-end equipment provisioning matches the provisioning of
the far-end equipment.
11 If the alarm persists, perform a protection switch on the circuit pack on which
the alarm is raised, by entering:
protectn
dtlprot ds1
manual op <unit>
yes
where
<unit> is g1 to g12 or all
12 If the alarm is cleared, replace the DS1 VT mapper circuit pack and release
the switch. See Module Replacement Procedures, 323-1111-547, for
continued
Fac DS1
Step Action
13 If the alarm persists, perform a protection switch on the corresponding circuit

pack at the other end by entering:
protectn
dtlprot ds1
manual op <unit>
where
14 If the alarm is cleared, replace the DS1 VT mapper circuit pack at the far-end
and release the switch. See Module Replacement Procedures,
15 Defective OC3/OC12 optical interface circuit pack
If the alarm persists, perform an OC-3/OC-12 transport optic protection
switch by entering:
protectn
manual op <unit>
yes
where
Note: The <unit> parameter is not required for
OC-12 terminals or ring ADMs.
<unit> is g1 or g2 (for terminal or VTM ring ADM)
(circuit pack group) is g1 or g1s (for NWK ring ADM)
is g1, g1s, g2, or g2s (for linear ADM)
16 Replace the inactive OC-3/OC-12 circuit pack and release the switch. See
instructions.
323-1111-090.
end
Figure 5-1
STS-1 Rx path trace fail alarm
FW-3004
Is a
path trace No
Exit
alarm raised?
Yes
Wait for the

network element Yes Is this network
to fully recover element powering
up?
No
Do you Retrieve path trace data. See

have access to TL1 procedure for TL1 in TL1 Interface
the OPCUI or Description, 323-1111-190.
TL1?
OPCUI
Retrieve path trace data. See procedure in
Verify that the path trace values have been provisioned

properly (that is, the Tx path trace value at one end of
the connection is exactly the same as the expected Rx
path trace value at the opposite end of the connection).
Is Correct path trace provisioned

path trace data No data. See procedure in
provisioned Provisioning and Operations
properly? Procedures, 323-1111-310.
Yes
Check the connection services
Does data and connection. See
the actual procedure in Provisioning
Does the actual Rx path trace value
No No and Operations Procedures,
Rx path trace value match the expected
contain "?" ? 323-1111-310.
Rx path trace
value?
Check the physical cabling on
Yes Yes the STS path. See procedure
in Installation Procedures,
If alarm persists, contact NT support 323-1111-201.
Is Disable path trace at both ends of

Does the STS connection. See the
there an OC-3 the far end comply
Yes No procedure on editing path trace
or STS-1 trib on the with the path trace
STS-1 path? values in Provisioning and
format? Operations Procedures,
323-1111-310. You have
No Yes completed the procedure.
Are Check the connection services data and

both trib ends No connection. See procedure in
the same trib Provisioning and Operations Procedures,
type? 323-1111-310.
Yes
Perform the hardware isolation procedure Check the physical cabling on the
STS path. See procedure in
Installation Procedures, 323-1111-201.
If alarm persists, contact NT support FW-3004
Fac DS1 50
STS1 Rx RFI 5
Probable cause
The local DS1 VT mapper circuit pack has received a Remote Failure
Indication (RFI) because a signal problem is detected on the downstream
equipment. The far-end network element transmitting the RFI has detected an
STS1 AIS or STS1 Loss of Pointer from the network element receiving the
RFI.
Impact
Action
Step Action
1 Verify the alarms at the local and far-end network elements by displaying all
active alarms at each network element by entering:
alarms
2 Clearing local and remote alarms on network elements through which the
STS connection passes should clear the STS1 Rx RFI alarm.
end
Fac DS1 50
STS1 Rx unequipped 5
Probable cause
Local DS1 VT mapper circuit pack is not receiving an STS-1 payload due to:
a connection has not been established at the OPC Connection Manager
the far-end DS1 facilities are all out-of-service (OOS)
the far-end DS1 VT mapper circuit pack is defective
Impact
Action
Step Action
1 Verify that the connection is correctly assigned to the facility for both end
points using either the OPC Connection Manager, TL1 or OSI, depending on
which method is in use.
If Then
the connection is incorrect edit the connection with the proper values
the alarm persists go to step 2
2 Obtain circuit pack group information using the Connection Manager.

3 Run the connection audit if the connection has been made. See TL1 Interface
Description, 323-1111-190, for the TL1 procedure. See OSI Specifications,
323-1111-191, for the OSI procedure.
continued
Fac DS1
STS1 Rx unequipped (continued)
Step Action
4 Verify that the far-end facility (for example, DS1, STS-1 facility) is in service
by entering:
facility <service type> <circuit pack group> <port #>
where
<service type> is ds1, sts1, or oc3
<circuit pack group> is circuit pack group obtained in step 2
<port #> is 1 to 3, or all for STS-1;
is 1 to 14, or all for DS1
The facility screen with the facility is displayed.

If State is OOS, put it in service by entering:
chgstate is
Then do the following:
If this action is Then go to
not successful step 5
successful step 6
5 Check for loopbacks set up on the far-end facility. The loopback field should
be none. If the loopback field is not none, release the loopback by entering:
loopback re
Then put the facility back in service by entering:
chgstate is
6 Do the following:
If the alarm Then
7 If the far-end circuit pack is in service and the alarm persist, replace the
far-end circuit pack. See Module Replacement Procedures, 323-1111-547,
for replacement instructions.
Note: Wait 5 seconds before inserting the new unit.
323-1111-090.
end
Fac DS1
STS1 signal label mismatch
Probable cause
The terminations at the ends of an STS1 connection between two network
elements (NE) are incompatible. For example, a DS1 on one NE is connected
to a DS3 on another NE.
Note: This alarm is raised at both ends of the connection.
Existing OCn alarms on any NE along the connection path may also cause
signal label mismatch alarms.
Impact
Action
Step Action
1 If Then
No OCn alarms exist go to step 2
Otherwise clear the OCn alarms. For information on clearing the
alarms see the appropriate alarm-clearing
procedures for:
Eqp OC3/OC12 on page 4-226
Eqp OC12 on page 4-261
Fac OC3/OC12 on page 5-94
Fac OC12 on page 5-132
If the alarm persists after attempting to clear the OCn
alarms, go to step 2.
2 From the OPC Connection Manager, verify that the intended DS1 to DS1 or
DS3 to DS3 connections are set up. The alarm was raised because these
connections are misaligned.
3 Replace either the DS3 STS mapper circuit pack or the DS1 VT mapper
circuit pack at one end of the connection, as indicated in Module
323-1111-090.
end
Fac DS1
VT Rx AIS
Probable cause
Local DS1 VT mapper circuit pack is receiving an alarm indication signal
(AIS) over the fiber optics. One of the following conditions exists:
far-end DS1 facility failure
loss of signal (LOS)
loss of pointer (LOP)
Note 1: Loss of pointer condition on a VT-managed STS-1 path is not
alarmed. The OC-12 VTM card does detect a VT LOP condition and takes
the appropriate consequent actions. That is, it generates downstream VT
AIS and it regenerates a valid downstream VT pointer. However, although
the VT LOP condition is detected, it is not alarmed. The result of this is that
the VT AIS warning, nsa alarm will be raised instead of the VT LOP Major,
sa alarm.
Note 2: This alarm can be caused by DS1 Rx LOF, Rx LOS, or Rx AIS on
the far end which may be masked by the automatic in-service (AINS)
feature.
Impact
Action
Step Action
1 In the network element user interface alarm screen, pinpoint the problem in
the upstream section by displaying all the active alarms at the remote network
element by entering:
alarms
If an LOS is detected, service the trouble at the remote end on site. Follow
the procedure for clearing Fac DS1 Rx loss of signal in this chapter.
2 If a protection switch on the far-end DS1 equipment clears the problem,
replace the DS1 equipment on the far end. See Module Replacement
end
Fac DS1 50
VT Path Rx ALS threshold 1, 2
VT Path Rx ES threshold 1, 2 5
Probable cause
A related facility DS1 VT Rx loss of pointer alarm has been raised on the
system because the VT pointer is corrupted (equivalent to losing frame). One
a defective far-end DS1 VT mapper circuit pack
a defective local DS1 VT mapper circuit pack
a defective far-end OC-3/OC-12 optical interface circuit pack
a defective local OC-3/OC-12 optical interface circuit pack
A related facility DS1 VT Rx AIS alarm has been raised on the system because
the local DS1 VT mapper circuit pack is receiving an alarm indication signal
(AIS) over the fiber optics. One of the following conditions exists:
a far-end DS1 facility failure
Impact
Action
Step Action
1 Check for other alarms on the system.

Do the following:
If Then
the VT Rx loss of pointer alarm is raised clear the alarm according to the
procedure in this NTP
the VT Rx AIS alarm is raised clear the alarm according to the
procedure in this NTP
the VT Path Rx ALS threshold 1, 2 alarm contact your next level of
and/or the VT Path Rx ES threshold 1, 2 support or your Nortel
alarms persist Networks support group
end
Fac DS1
VT Rx loss of pointer
Note: Loss of pointer condition on a VT-managed STS-1 path is not
alarmed. The OC-12 VTM card does detect a VT LOP condition and takes
the appropriate consequent actions. That is, it generates downstream VT
AIS and it regenerates a valid downstream VT pointer. However, although
the VT LOP condition is detected, it is not alarmed. The result of this is that
the VT AIS warning, nsa alarm will be raised instead of the VT LOP Major,
sa alarm.
Probable cause
The VT pointer is corrupted (equivalent to losing frame). One of the following
conditions exists:
a defective far-end DS1 VT mapper circuit pack
a defective local DS1 VT mapper circuit pack
a defective far-end OC-3/OC-12 optical interface circuit pack
a defective local OC-3/OC-12 optical interface circuit pack
Impact
Note: Switch to protection is initiated, resulting in a traffic outage of 60

ms maximum.
Action
Step Action
1 Look for an optical signal degrade or BER alarms by entering:

alarms
2 Check if a protection switch of the equipment on which the alarm was
detected clears up the problem, then replace the card. Otherwise, go to
step 3.
3 Check if a protection switch of the equipment on which the VT originates at
the far end of the fiber optic clears the problem, then replace the card. See
the appropriate procedure in Module Replacement Procedures,
323-1111-547.
end
Fac DS1
VT Rx RFI
Probable cause
A remote defect indication condition is received from the far-end node
originating the VT path signal. The remote defect indication condition is sent
because a VT AIS or VT LOP is being received on the VT path signal at the far
end.
Impact
Action
Step Action
1 Check the VT AIS or VT LOP alarms on the far-end node where the VT path
signal originates.
2 Check for an STS1 Rx RFI alarm at an upstream node through which the VT
path signal passes. If one is found, refer to the alarm-clearing procedure for
Fac Path STS1 Rx RFI.
3 Check for higher order alarms at an upstream node.
end
Fac DS1
VT Rx unequipped
Probable cause
Local DS1 VT mapper circuit pack is not receiving a VT payload because the
far-end DS1 VT facility is out of service (OOS).
Impact
Action
Step Action
1 Using the OPC Connection Manager, determine which DS1 on the near end
is connected to the far end. Determine the circuit pack group information.
2 Verify that the far-end DS1 facility is in service by entering:
fa ds1 <unit> <port #>
where
<unit> is the circuit pack group determined in step 1
<port #> is 1 to 14
If not, put it in service by entering:

chgstate is
If this action is Then
not successful go to step 3
successful go to step 4
continued
Fac DS1
VT Rx unequipped (continued)
Step Action
be none. If the loopback field is not none, then release the loopback by
entering:
loopback re
chgstate is
4 Do the following:
If the alarm Then
does not clear go to step 5
5 Replace the DS1 VT mapper circuit pack, if necessary. See Module

end
Fac DS3
Frequency out of range
Probable causes
The DS3 mapper circuit pack is receiving one of the following degraded
signals:
a bad clock reference from the active OC12 or ESI

a poorly clocked signal from the DS3 copper source
information.
Impact
Action
Step Action
1 Do the following:
If Then
ESI or OC-12 alarm exists replace the ESI or OC-12 circuit pack
(especially clock problems)
ESI and OC-12 have no check DS3 signal source for timing problems
alarms
end
Fac DS3
Probable cause
Impact
Note: It is assumed that these alarm points are provisioned as alarms and
turned ON (activated). If not, these alarm points appear as performance
alerts.
Action
were observed. Threshold crossing alarms will automatically clear at the
end of the provisioned interval.
Note 2: This procedure is service affecting.
Step Action
1 Locate the DS3 port connectors on the BNC I/O circuit pack allocated to the
port reporting the errors. Examine the DS3 cable connected to the In
connector of the concerned DS3 port. Ensure that the correct connector is
used and is well secured at the source and at the BNC I/O circuit pack. If the
cable is split or damaged, replace it. If the problem persists, go to step 2.
continued
Fac DS3
Line Rx SES threshold 1, 2 (continued)
Step Action
2
CAUTION
Ensure that the correct DS3 cable is unplugged.
Removing the wrong one will cause another DS3
signal to be lost.
Unplug the input DS3 cable from the BNC I/O circuit pack and connect it to a
DS3 receiver test set. Verify that a DS3 signal is present on the cable and that
the test set does not detect any errors.
Do the following:
If Then
3 Do the following:
If Then
errors were detected at verify the signal at the source with the DS3 test
the BNC I/O circuit pack set
(in step 2)
errors are detected repair the source generating the DS3 signal
continued
Fac DS3
Line Rx SES threshold 1, 2 (continued)
Step Action
4
CAUTION
Ensure that the proper BNC I/O circuit pack is
removed. Removing the wrong circuit pack will cause
another DS3 signal to be lost. Replacing the BNC I/O
circuit pack will also cause the loss of the DS3 signal
being sent on the Out side of the concerned port.
At this point the DS3 cable and the DS3 signal source have been verified. If
errors are still occurring, then replace the BNC I/O circuit pack associated
with this port. See Module Replacement Procedures, 323-1111-547, for
5 If the problem persists, replace the DS3 STS mapper circuit pack carrying this
facility. See Module Replacement Procedures, 323-1111-547, for
Library, 323-1111-090.
end
Fac DS3
Loopback
Probable cause
A DS3 loopback was operated and remains active.
Note: The loopback can only occur when the facility is out of service.
Impact
Note: This alarm is a normal indication when the loopback is ON for

testing purposes.
Action
Step Action

facility ds3 <unit> <port #>
where
loopback re
2 If you want to put the DS3 facility back in service, enter:
chgstate is
details.
end
Fac DS3
Path Rx AISS threshold 1, 2
Path Rx SEFS threshold 1, 2
Path Rx UAS threshold 1, 2
Probable cause
A DS3 Rx performance monitoring parameter threshold has been crossed. One
a faulty BNC I/O card
Impact
Note: These alarms indicate that errors in excess of a provisioned level

Action
Step Action
used and well secured at the source and at the BNC I/O circuit pack.
continued
Fac DS3
Step Action
Do the following:
If Then
2
CAUTION
signal to be lost.
the test set detects no errors.
Do the following:
If Then
no errors are detected then reconnect the DS3 cable and go to step 4
3 Do the following:
If Then
(in step 2)
continued
Fac DS3
Step Action
4
CAUTION
errors still occur, then replace the BNC I/O circuit pack associated with this
port. See Module Replacement Procedures, 323-1111-547, for replacement
instructions.
Library, 323-1111-090.
end
Fac DS3
Path Tx AISS threshold 1, 2
Path Tx CV threshold 1, 2
Path Tx ES threshold 1, 2
Path Tx SEFS threshold 1, 2
Path Tx SES threshold 1, 2
Path Tx UAS threshold 1, 2
Probable cause
A DS3 Tx performance monitoring parameter threshold has been crossed. One
a defective DS3 STS mapper circuit pack (local or at far end)
a defective DS3 switcher
an OC-3/OC-12 equipment or optical link failure
Impact
Note 1: It is assumed that these alarms have been provisioned (activated)

as alarms and are turned on. If not, these alarm points will show up as
performance alerts. It is also assumed that DS3 parity error correction has
been enabled.
Action
continued
Fac DS3
Path Tx UAS threshold 1, 2 (continued)
Step Action
1 Ensure that the alarm is not caused by a facility fault by checking the
OC-3/OC-12 performance monitoring facility for excessive errors by entering:
perfmon
facperf <type> <unit>
where
<unit> is the traffic carrying channel
If the present alarm is not caused by an OC-3/OC-12 facility, go to step 2.

2 From the network element user interface (UI), perform a manual switch on the
DS3 STS mapper circuit pack by entering:
protectn
dtlprot ds3
manual op <unit>
yes
where
<unit> is the alarmed circuit pack
See Protection Switching Procedures, 323-1111-311, for more details.

3 Do the following:
If Then
the problem is not go to step 4
corrected
the problem is replace the defective DS3 STS mapper circuit pack.
corrected See Module Replacement Procedures, 323-1111-547,
continued
Fac DS3
Step Action
4 Release the manual switch by entering:

protectn
dtlprot ds3
manual re <unit>
yes
where
<unit> is the one used in step 2
5 If the alarm remains active, replace the DS3 switcher circuit pack. Refer to
instructions.
6 If the alarm remains active, check the corresponding group DS3 STS mapper
circuit pack at the far-end network element. Log into the other network
element and, from the network element UI , perform a manual switch on the
DS3 STS mapper circuit pack by entering:
protectn
dtlprot ds3
manual op <unit>
yes
where
<unit> is the specific circuit pack

7 If the problem is corrected (check alarm points in Alarm Monitor), replace the
defective DS3 STS mapper circuit pack. See Module Replacement
continued
Fac DS3
Step Action

protectn
dtlprot ds3
manual re <unit>
yes
where
<unit> is the one used in step 6
9 If errors still occur, perform a manual switch of the optics on the alarmed
network element by entering:
protectn
manual op <unit>
yes
where
linear ADM), or g1s or g2s for secondary optical
interface on a linear ADM)
<unit> is the working channel group number
clears step 11
persists step 13
continued
Fac DS3
Step Action
If the circuit pack is Then go to
NT7E01 or NT7E02 step 12
NT7E05 step 13
12 If the alarm is cleared, replace the inactive OC-3/OC-12 circuit pack and
release the switch. See Module Replacement Procedures, 323-1111-547, for
13 Contact your next level of support or your Nortel Networks support group. See
About the OC-3/OC-12 NETBM Library, 323-1111-090. You have
completed the procedure.
end
Fac DS3
Rx AIS
Probable cause
The far-end network element is experiencing signal problems with the DS3
source, and is sending a DS3 alarm indication signal (AIS).
Impact
This is a warning, service-affecting (w, SA) alarm.
Action
Step Action
1 Check the DS3 equipment and the DS3 facility at the DS3 source located at
the far end of the DS3 cable. Resolve any failures on the DS3 equipment or
DS3 facilities.
end
Fac DS3
Probable cause
Bipolar violations have been detected on the incoming DS3 line. One of the
a defective coaxial connector
a defective cable
a defective DS3 source equipment
a defective BNC I/O card or DS3 STS mapper circuit pack
Impact
Note: Traffic is degraded due to a previous section failure.
Action
Step Action
used and is well secured at the source and at the BNC I/O circuit pack.
Do the following:
If Then
2
CAUTION
Ensure you unplug the correct DS3 cable . Removing
the wrong one causes another DS3 signal to be lost.
continued
Fac DS3
Step Action
Do the following:
If Then
3 Do the following:
If Then
(in step 2)
4
CAUTION
Ensure you remove the proper BNC I/O circuit pack.
Removing the wrong circuit pack cause another DS3
signal to be lost. Replacing the BNC I/O circuit pack
also causes the loss of the DS3 signal being sent on the
Out side of the concerned port.
errors still occur, then replace the BNC I/O circuit pack associated with this
port. See Module Replacement Procedures, 323-1111-547, for replacement
instructions.
Library, 323-1111-090.
end
Fac DS3
Rx loss of frame
Probable cause
The DS3 frame cannot be detected on the incoming DS3. One of the following
conditions exists:
an incorrect provisioning framing parameter
a defective DS3 source equipment
a defective BNC I/O interface circuit pack
a defective DS3 STS mapper circuit pack
a DS3 clear channel is being received when that facility is provisioned for
regular DS3 (frame on)
Impact
Action
Step Action
port reporting the loss of frame. Examine the DS3 cable connected to the In
Do the following:
If Then
2
CAUTION
signal to be lost.
continued
Fac DS3
Step Action
the test set does not detect loss of frame.
Do the following:
If Then
no loss of frame is detected reconnect the DS3 cable and go to step 4
3 Do the following:
If Then
loss of frame was detected at verify the signal at the source with the DS3
the BNC I/O circuit pack (in test set
step 2)
a loss of frame is detected repair the source generating the DS3 signal
no loss of frame is detected repair the DS3 cable. Go to step 6.
4
CAUTION
Removing the wrong circuit pack causes another DS3
loss of frame is still occurring, then replace the BNC I/O circuit pack
associated with this port. See Module Replacement Procedures,
Library, 323-1111-090.
end
Fac DS3
Rx loss of signal
Probable cause
The DS3 STS mapper circuit pack is not detecting any DS3 input signal. One
an incoming Rx DS3 line fail (loss of signal)
a defective or missing BNC I/O circuit pack
Note: If this facility terminates through the fiber (or far end NE), a DS3
facility in another OPC span of control, this alarm could be raised.
If it is the case, contact your Nortel Networks support group to clear the
alarm.
Impact
Action
Step Action
port reporting the loss of signal. Examine the DS3 cable connected to the In
Do the following:
If Then
2
CAUTION
signal to be lost.
the test set does not detect loss of signal.
continued
Fac DS3
Step Action
Do the following:
If Then
no loss of signal is detected then reconnect the DS3 cable and go to
step 4
3 Do the following:
If Then
a loss of signal was detected at verify the signal at the source with the DS3
the BNC I/O circuit pack (in test set
step 2)
a loss of signal is detected repair the source generating the DS3
signal
no loss of signal is detected repair the DS3 cable. Go to step 6.
4
CAUTION
Removing the wrong circuit pack causes another DS3
loss of signal still occurs, then replace the BNC I/O circuit pack associated
Library, 323-1111-090.
end
Fac DS3
Rx Parity error rate>10E-6
Probable cause
A DS3 STS mapper has detected parity errors coming from the DS3 input
signal. One of the following conditions exists:
a faulty BNC I/O card
Impact
Action
Step Action
Do the following:
If Then
2
CAUTION
signal to be lost.
continued
Fac DS3
Rx Parity error rate>10E-6 (continued)
Step Action
Do the following:
If Then
3 Do the following:
If Then
errors were detected at the verify the signal at the source with the DS3 test
BNC I/O circuit pack (in set
step 2)
4
CAUTION
errors are still occurring, then replace the BNC I/O circuit pack associated
Library, 323-1111-090.
end
Fac DS3
STS1 Rx path trace failure
Probable cause
a mismatched STS-1 connection
incompatible path trace
a defective DS3 STS mapper circuit pack
a defective OC-3/OC-12 optical interface circuit pack
the network element is recovering from being powered down
Impact
Action
Step Action
1 Verify that the path trace provisioning data is correct. See the flowchart in
Figure 5-2 on page 5-75.
Do the following:
If a path trace alarm is Then
raised go to step 2
not raised you have completed the procedure
2 Do the following:
If the network element is Then
powering up wait for the network element to fully recover.
Then go to step 1.
not powering up go to step 3
continued
Fac DS3
Step Action
3 Do the following:
If you have access to Then
the OPC UI retrieve path trace data. See the procedure on
retrieving path trace data values using the OPC
Connection Manager tool in Systems
the NE UI retrieve path trace data. See the procedure on
retrieving path trace data values using the
PTSAMPLER tool in Systems Administration
the TL1 interface retrieve path trace data. See the Retrieve Path
Trace (rtrv-pthtrc) command in TL1 Interface
Verify that the path trace values are provisioned correctly (the Tx path trace
value at one end of the connection is exactly the same as the expected Rx
path trace value at the opposite end of the connection). Go to step 4.
4 Do the following:
If path trace data is Then
provisioned properly go to step 5
not provisioned properly correct path trace provisioned data. See the
procedure in Provisioning and Operations
Procedures, 323-1111-310. Go to step 1.
5 Do the following:
If the actual Rx path trace value Then
contains ? go to step 6
does not contain ? go to step 7
6 Do the following:
If an OC-3 or STS-1 tributary is Then
on the STS-1 path go to step 8
not on the STS-1 path go to step 9
continued
Fac DS3
Step Action
7 Do the following:
If the actual Rx Then
path trace value
matches the if the alarm persists, contact your next level of support
expected Rx path or your Nortel Networks support group. See About the
trace value OC-3/OC-12 NETBM Library, 323-1111-090.
does not match the check the connection services data and connection.
expected Rx path See the procedures in Provisioning and Operations
trace value Procedures, 323-1111-310.
Check the physical cabling on the STS path. See the
procedure in Installation Procedures, 323-1111-201.
Go to step 1.
8 The path trace format supports the 64-byte ASCII character string: the first 62
characters of the string are user provisionable and the remaining two are
reserved for line feed and carriage return characters provided by the system.
If the far end Then
complies with the go to step 9
path trace format
does not comply disable path trace at both ends of the STS connection.
with the path trace See the procedure in Provisioning and Operations
format Procedures, 323-1111-310.
You have completed the procedure.
9 Do the following:
If both tributary Then
ends are
the same tributary perform the hardware isolation procedures.
type Go to step 10.
If alarm persists, contact your next level of support or
your Nortel Networks support group. See About the
not the same check the connection services data and connection.
tributary type See the procedure in Provisioning and Operations
Check the physical cabling on the STS path. See the
procedure in Installation Procedures, 323-1111-201.
Go to step 1.
continued
Fac DS3
Step Action
Hardware isolation procedure

10 Verify that the near-end equipment provisioning matches the provisioning of
the far-end equipment.
11 If the alarm persists, perform a protection switch on the circuit pack on which
the alarm is raised, by entering:
protectn
dtlprot ds3
manual op <unit>
yes
where
<unit> is g1 to g4
12 If the alarm is cleared, replace the DS3 STS1 mapper circuit pack and
release the switch. See Module Replacement Procedures, 323-1111-547, for
13 If the alarm persists, perform a protection switch on the corresponding circuit
pack at the other end by entering:
protectn
dtlprot ds3
manual op <unit>
where
<unit> is g1 to g4
14 If the alarm clears, replace the DS3 STS1 mapper circuit pack at the far-end
and release the switch. See Module Replacement Procedures,
continued
Fac DS3
Step Action
Defective OC3/OC12 optical interface circuit pack

15 If the alarm persists, perform an OC-3/OC-12 transport optic protection
switch by entering:
protectn
manual op <unit>
yes
where
<unit> is g1 or g2 (for primary optical interface on a linear
ADM), or g1s or g2s for secondary optical
interface on a linear ADM)
g1, g1s, g2s, or g2s (for linear ADM)
clears step 17
persists step 13
17 Do the following
If the circuit pack is Then go to
NT7E01 or NT7E02 step 18
NT7E05 step 13
18 If the alarm clears, replace the inactive OC-3/OC-12 circuit pack and release
the switch. See Module Replacement Procedures, 323-1111-547, for
About the OC-3/OC-12 NETBM Library, 323-1111-090.
end
Figure 5-2
FW-3004
Is a
path trace No
Exit
alarm raised?
Yes
Wait for the

network element Yes Is this network
to fully recover element powering
up?
No
Do you Retrieve path trace data. See

have access to TL1 procedure for TL1 in TL1 Interface
the OPCUI or Description, 323-1111-190.
TL1?
OPCUI
Retrieve path trace data. See procedure in
Verify that the path trace values have been provisioned

properly (that is, the Tx path trace value at one end of
the connection is exactly the same as the expected Rx
path trace value at the opposite end of the connection).
Is Correct path trace provisioned

path trace data No data. See procedure in
provisioned Provisioning and Operations
properly? Procedures, 323-1111-310.
Yes
Check the connection services
Does data and connection. See
the actual procedure in Provisioning
Does the actual Rx path trace value
No No and Operations Procedures,
Rx path trace value match the expected
contain "?" ? 323-1111-310.
Rx path trace
value?
Check the physical cabling on
Yes Yes the STS path. See procedure
in Installation Procedures,
If alarm persists, contact NT support 323-1111-201.
Is Disable path trace at both ends of

Does the STS connection. See the
there an OC-3 the far end comply
Yes No procedure on editing path trace
or STS-1 trib on the with the path trace
STS-1 path? values in Provisioning and
format? Operations Procedures,
323-1111-310. You have
No Yes completed the procedure.
Are Check the connection services data and

both trib ends No connection. See procedure in
the same trib Provisioning and Operations Procedures,
type? 323-1111-310.
Yes
Perform the hardware isolation procedure Check the physical cabling on the
STS path. See procedure in
Installation Procedures, 323-1111-201.
If alarm persists, contact NT support FW-3004
Fac DS3 50
STS1 Rx RFI 5
Probable cause
The local DS3 STS mapper circuit pack has received a Remote Failure
Indication (RFI) because a signal problem is detected on the downstream
equipment. The far-end network element transmitting the RFI has detected an
STS1 AIS or STS1 Loss of Pointer from the network element receiving the
RFI.
Impact
Action
Step Action
the active alarms of each network element by entering:
alarms
STS connection passes should clear the STS-1 Rx RFI alarm.
end
Fac DS3
STS1 Rx unequipped
Probable cause
Local DS3 STS mapper circuit pack is not receiving an STS-1 payload. One of
the following conditions exists:
far-end facility is out-of-service (OOS)
far-end tributary circuit pack is defective
a connection has not been established at the OPC Connection Manager
Impact
Action
Step Action
1 Verify that the connection is correctly assigned to the facility for both end
points using either the OPC Connection Manager, TL1 or OS1, depending on
which method is in use.
If the Then
connection is incorrect edit the connection with the proper
values
alarm persists go to step 2

Description, 323-1111-190, for the TL1 procedure. If the alarm persists, go to
step 4.
continued
Fac DS3
Step Action
4 Verify that the far-end facility (for example, DS3, STS-1, or OC-3) is in service
by entering:
facility <service type> <circuit pack group> <port #>
where
<service type> is ds3, sts1, or oc3
<circuit pack group> is the circuit pack group obtained in step 2
<port #> is 1 to 3, or all for DS3 and STS-1

If State is OOS, put it in service by entering:
chgstate is
If this action is Then
not successful go to step 5
successful go to step 6
be none. If the loopback field is not none, then release the loopback by
entering:
loopback re
chgstate is
6 Do the following:
If the alarm Then
7 If the far-end circuit pack is in service and the alarm persists, replace the
far-end circuit pack. See Module Replacement Procedures, 323-1111-547,
8 If the problem persists, contact your next level of support or your Nortel
323-1111-090.
end
Fac DS3
STS1 signal label mismatch
Probable cause
The terminations at the ends of an STS1 connection between two network
elements (NE) are incompatible. For example, a DS1 on one NE is connected
to a DS3 on another NE.
Note: This alarm is raised at both ends of the connection.
Existing OCn alarms on any NE along the connection path may also cause
signal label mismatch alarms.
Impact
Action
Step Action
1 If Then
No OCn alarms exist go to step 2
Otherwise clear the OCn alarms. For information on clearing
the alarms see the appropriate alarm-clearing
procedures for:
Eqp OC3/OC12 on page 4-226
Eqp OC12 on page 4-261
Fac OC3/OC12 on page 5-94
Fac OC12 on page 5-132
If the alarm persists after attempting to clear the
OCn alarms, go to step 2.
2 From the OPC Connection Manager, verify the intended DS1 to DS1 or DS3
to DS3 connections set up. The alarm was raised because these connections
are misaligned.
3 Replace either the DS3 STS mapper circuit pack or the DS1 VT mapper
circuit pack at one end of the connection, as indicated in Module
323-1111-090.
end
Fac DS3
Tx AIS
Probable cause
an AIS signal from the fiber optics side of the DS3 has been received
the AIS was passed over the fiber from the DS3 at the far end
This alarm can be caused by DS1 RX LOF, Rx LOS, or Rx AIS on the far end
which can be masked by the automatic in-service (AINS) feature.
Impact
This is a secondary alarm. The primary alarm should be cleared.
Action
Step Action
1 Verify the alarms at the local and far-end network element by displaying all
alarms
2 Clearing local and remote alarms should clear the TX AIS alarm.
end
Fac DS3
Tx loss of frame
Probable causes
an AIS signal from the fiber optics side of the DS3 has been received
a faulty DS3 signal coming from the far-end terminal
See Chapter 10, Clearing incorrect Application Select state, for more
information.
Impact
Note: This is a secondary alarm. The primary alarm should be cleared.

Action
Step Action
1 Check the DS3 facility and equipment for any failures by entering:
alarms
2 If no relevant alarm is found, check the DS3 facility and equipment at the far
end for any failures.
3 If the alarm is still not cleared, perform a DS3 protection switch at the far-end
network element by entering:
protectn
dtlprot ds3
manual op <unit>
where
<unit> is g1 to g4
4 Do the following:
If the alarm Then
clears replace the DS3 STS mapper circuit pack at the far
end. See Module Replacement Procedures,
continued
Fac DS3
Tx loss of frame (continued)
Step Action
5 Release the switch by entering:

protectn
dtlprot ds3
manual re <unit>
where
<unit> is g1 to g4
6 Perform a DS3 protection switch at the local network element by entering:

protectn
dtlprot ds3
manual op <unit>
where
<unit> is g1 to g4
7 Do the following:
If the alarm Then
clears replace the DS3 STS mapper circuit pack. See
Module Replacement Procedures, 323-1111-547, for
8 Release the switch by entering:

protectn
dtlprot ds3
manual re <unit>
where
<unit> is g1 to g4
9 Check the DS-3 equipment (multiplexers and cross-connects) that is feeding

the DS-3 signal at the far-end network element for faulty DS-3 output or an
incorrect LBO setting causing a weak signal. If faulty signals are found, take
corrective action for the equipment involved.
end
Fac ESI
Bipolar violation
Probable cause
The ESI detects bipolar violation on the timing reference input signal
(bipolar violation rate exceed 10 E-3).
Impact
Note: The identified timing reference input signal which feeds the TBM
shelf has a line condition problem. This can cause timing problems.
Action
Step Action
1 Verify the primary and secondary reference connections to the BITS and
verify the integrity of the BITS.
end
Fac ESI
Degraded clock carrier
Probable causes
The ESI cannot synchronize to the incoming timing reference input signal. If
the input reference is slowly drifting (a condition known as a static drift), the
ESI automatically detects a cumulative frequency drift of more than 5.15
ppm (best case) 20.5 ppm (worst case). If a valid secondary reference is
present, a reference protection switch is automatically performed. If no valid
secondary reference exists, the ESI enters Freerun mode.

Impact
The timing reference signal might be degraded.
Note: This alarm can also cause an Eqp ESI Timing generation entry to
freerun alarm to be generated. See Chapter 4, Clearing equipment alarms
for the appropriate procedure to clear the alarm.
Action
Step Action
1 Verify the phase and frequency stability of the external reference source. The
alarm will clear automatically when the reference frequency is within
4.5 ppm.
2 If the alarm persists, place the facility out of service (OOS) and back in
service (IS) by entering:
chgstate oos
chgstate is
3 If the problem persists, change the ESI circuit pack. Refer to Module
end
Fac ESI
Loss of frame
Probable cause
The ESI detects a loss of frame on the timing reference input signal.
Impact
Action
Step Action
1 Verify that the timing reference input frame format is equivalent to what is
expected by entering:
fa esi <timing reference>
where
<timing reference> is bitsa or bitsb
query all
2 Verify the connection of the external synchronization cable and the external
reference signal.
end
Fac ESI
Loss of signal
Probable cause
The timing reference input signal has been lost.
Impact
Action
Step Action
1 Verify and if necessary correct the connection of the external synchronization

cable and the external reference signal.
If the Then
alarm is cleared you have completed the procedure
reference signal input to the shelf is go to step 2
OK
2 Verify that the timing reference input frame format and line coding selections
are equivalent to what is expected by entering:
where
<timing is bitsa or bitsb
reference>
query
If Then go to
any parameter is not as step 3
expected
parameters are ok step 4
3 Change any incorrect parameter as described in Provisioning and Operations

If Then
the alarm is cleared you have completed the procedure
alarm is not cleared go to step 4
About the OC-3/OC-12 NETBM Library, 323-1111-090.
end
Fac ESI
Rx AIS
Probable cause
The ESI detects an AIS signal on the timing reference input signal.
The BITS that feeds the TBM shelf is sending an AIS signal. It has a problem
and might have lost both its primary and secondary reference.
Impact
Action
Step Action
1 Verify the primary and secondary reference connections to the BITS and
verify the integrity of the BITS.
end
Fac ESI
Tx AIS
Probable cause
the ESI circuit pack has lost signal reference from the optical carrier used
by the ESI to generate a DS1 timing reference output
the S1 byte synchronization status message in the OC-n line (used as a
reference for the alarmed DS1 timing reference output) is at or below a
user selectable quality level
the synchronization status message inserted into the DS1 timing reference
output is at or below a user-selectable quality level
an intercard alarm in the optical circuit pack group can cause the ESI
timing reference output to generate an AIS signal
Note: This alarm may be generated when the OCA/OCB Timing Source
provisioning is changed on the Trefsrc screen in which case the alarm will
clear 10 seconds after it is raised.
Impact
Action
Note: Verify that the relevant equipment and facilities are in service and
active. No action is required if the relevant equipment is inactive.
Step Action
1 To find which optic is relevant, query the affected timing reference output by
entering:
where
<timing is g1out or
reference> g2out
The relevant optic is the one which is used as the source for the ESI timing
reference output. Verify that the input optical signal of the OC-3/OC-12 card
is correct and that there are no active alarms for the OC-3/OC-12 facilities.
continued
Fac ESI
Tx AIS (continued)
Step Action
Do the following:
If Then
alarms are present clear them according to a procedure in this
document
no alarms are present go to step 2
2 From the network element status screen, display the relevant equipment
screen and verify that the state is IS (in service) by entering:
eq <service type> <unit>
where
The equipment screen appears.

Do the following:
If Then
the equipment is in service (IS) go to step 4
the status is standby this is normal
the equipment is not in service go to step 3
3 Change the state to in service by entering:

chgstate is
The state changes to IS.
4 Display the list of active alarms and verify that the ESI alarm is cleared by
entering:
alarms
A list of active alarms appears.
Do the following:
If the alarm Then
continued
Fac ESI
Tx AIS (continued)
Step Action
5 Display the relevant facility screen and verify that the state is IS (in service)
by entering:
fa <service type> <unit>
where
The facility screen appears.

Do the following:
If the state is Then go to
IS (in service) and the status is active step 8
not IS (in service) step 6
6 Change the state of the facility to in service by entering:

chgstate is
The state changes to IS (in service).
entering:
alarms
Do the following:
If the alarm Then
8 The problem may be that the S1 byte synchronization status message in the
OC-n line that is being used as a reference for the alarmed DS1 timing
reference output is at or below a user-selectable quality level. To view the
user-selectable quality level, enter:
where
<timing reference> is g1out or g2out
The Threshold AIS field indicates the user-selectable quality level.

continued
Fac ESI
Tx AIS (continued)
Step Action
9 Determine whether the far-end equipment connected to the OC-n line is

sending a quality level in the S1 byte that is at or below the user-selectable
quality level. If so, change the source for timing distribution or change the
user-selectable quality level for the threshold AIS value using the appropriate
procedure as follows:
Commissioning Procedures, 323-1111-220, Procedure 6-16, Changing
the ESI timing distribution source tracking and source
the AIS threshold for a timing distribution facility
entering:
alarms
Do the following:
If the alarm Then
11 There might be a synchronization status message inserted in the DS1 timing

reference output that is less than or equal to a user-selectable quality level.
Display the synchronization status messages by entering:
syncmsgci
qrymsg
12 Check to see if there is a provisioned transmit value for G1OUT or G2OUT
and whether that value is less than or equal to the threshold AIS value. If so,
change the threshold AIS value or remove the quality level inserted in the
DS1 timing reference output using the appropriate procedure as follows:
the AIS threshold for a timing distribution facility
Commissioning Procedures, 323-1111-220, Procedure 6-21,
Provisioning the clock quality level inserted into a timing signal
continued
Fac ESI
Tx AIS (continued)
Step Action
entering:
alarms
Do the following:
If the alarm Then
14 Replace the ESI circuit pack carrying the ESI facility reporting the alarm (that
is, ESI G1 for G1OUT and ESI G2 for G2OUT). See Module Replacement
entering:
alarms
If the alarm Then
support group. See About the OC-3/OC-12 NETBM Library,
323-1111-090
end
Fac ESI 50
Undefined sync status message 5
Probable cause
The network element received a synchronization status message with a value
not defined in the standard set of SONET synchronization messages or that it
does not recognize.
This alarm becomes active when the network element detects the condition. It
clears when the network element receives a SONET-defined value. For a list of
supported synchronization status messages and related information, see
Timing and Synchronization Description, 323-1111-192.
Note: The OC-12 network element uses and recognizes the

user-assignable RES (reserved) message as defined in the SONET
standards. If an NE receives this message, it does not raise the Undefined
synchronization status message alarm. The NE sends out the RES
message to other subtending TBMs only when timing for the NE has been
set to VTMlinetimed and the NE goes into holdover. When a TBM sends
the RES message, subtending OC-3 NEs that derive timing from an NE
using OC-3 synchronization status messaging (SSM) receive DUS.
Impact
Minor, non-service affecting
Action
Step Action
1 Check the BITS or upstream OC-12 network element sending the message.
Determine why it is not sending a standard synchronization value as defined
in the SONET standards. For example, the equipment might not be fully
SONET compliant.
2 Refer to the manufacturers documentation. Determine whether you can
reprovision, update, or replace the upstream equipment providing the
synchronization message so that it sends a valid value.
3 If there is no way to get the upstream equipment to send a valid message, the
alarm must remain active. You cannot deprovision this alarm.
end
Fac OC3/OC12
Line RFI
Probable cause
A Remote Failure Indication (RFI) alarm is raised when a remote defect
indication condition is received from the far-end node originating the STS1
line signal. The remote defect indication condition is sent because an STS1
LOS, STS1 LOF, or STS1 Line AIS is received on the STS1 line signal at the
far-end node.
Impact
This is a warning, not service-affecting (w, nsa) alarm (if protectable) and no
traffic is being carried.
This alarm can be caused by OC3 Line LOS or LOF on the far end which may
be masked by the automatic in-service (AINS) feature.
Action
Step Action
1 Check for STS1 LOS, STS1 LOF, or STS1 Line AIS alarms on the far-end
node where the STS1 line signal originates.
end
Fac OC3/OC12
Line Rx UAS threshold 1, 2
Sect Rx CV threshold 1, 2
Sect Rx ES threshold 1, 2
Sect Rx SES threshold 1, 2
Sect Rx SEFS threshold 1, 2
Probable cause
An OC-3/OC-12 performance monitoring parameter threshold has been
crossed. One of the following conditions exists:
a degraded fiber connection
a defective upstream optical interface circuit pack
a defective local optical interface circuit pack
If the network element is equipped with STS-12 circuit packs instead of optical
circuit packs, you can use this procedure if the following requirements are met:
a high-precision variable optical attenuator (VOA) or a mini-variable
optical attenuator is not used because the STS-12 is an electrical-interface
circuit pack
whenever the procedures refer to an optical circuit pack, replace the
reference with STS-12 circuit pack
Note: The NE commands are the same for optical and electrical circuit
packs.
Impact
Note 2: It is assumed that these thresholds have been provisioned as
alarms and are turned on (activated). If they are not provisioned as alarms,
these alarm points will show up as performance alerts.
continued
Fac OC3/OC12
Sect Rx SEFS threshold 1, 2 (continued)
Action
Step Action
1 The fiber connected to the OC-3/OC-12 optics in alarm must be removed for
checking. However, before unplugging the module, ensure that live traffic is
being received by the other OC-3/OC-12 optics.
Do the following:
If Then
the circuit in alarm is the go to step 2
working OC-3/OC-12 optical
interface circuit pack
the circuit in alarm is not the go to step 3. See Module Replacement
working OC-3/OC-12 optical Procedures, 323-1111-547, for removal and
interface circuit pack insertion of the OC-3/OC-12 optics.
Note: If this alarm is seen for unprotected OC-3 tributaries, then this
procedure cannot be performed in service since there is no OC-3 trib to
switch to.
2 Do the following:
raised at a regenerator network element go to step 4
not raised at a regenerator network element follow this step
continued
Fac OC3/OC12
Step Action
Ensure that there is no lockout by entering:

protectn
where
is g1, g2, g1s or g2s (for linear ADM)
is g3 to g8, g1s, or g2s (for OC-3 tributaries)
If a lockout is in effect, that is, next to the lockout field either a * or a *R is

present, the lockout must be removed. If * is found, enter:
lockout re
yes
For ring ADMs, enter:
lockout re w
yes
or
lockout re p
yes
If *R is found, the lockout must be deactivated at the remote end. Login to the
remote end and enter:
lockout re
yes
continued
Fac OC3/OC12
Step Action

lockout re w
yes
or
lockout re p
yes
3 Do the following:
Force the live traffic to the other OC-3/OC-12 optics by entering:

forced op <unit>
yes
where
<unit> is g1, g2, g2s, g1s, or g3 to g8
4 Unplug the fiber from the alarmed optical interface circuit pack. Clean the
fiber using the appropriate procedure for cleaning fiber optic connectors
found in Common Procedures, 323-1111-846.
continued
Fac OC3/OC12
Step Action
5 Verify that the received optical power is in the correct range using the
procedure found in Common Procedures, 323-1111-846.
Measure the received optical power using an optical power meter. The
received power should be as shown in the following table. If the received
power is not within this range, adjust the mVOA if equipped until it is.
Optical interface circuit pack Received power
minimum (dBm) maximum (dBm)
OC-3 IR (NT7E01) -28.0 -8.0
OC-3 LR (NT7E01) -34.0 -10.0
OC-12 IR (NT7E02) -24.5 -4.0
OC-12 LR (NT7E02) -32.0 -7.0
OC-12 ELR (NT7E02) -32.2 -8.0
OC-12 VTM IR (NT7E05) -28.0 0
OC-12 VTM LR (NT7E05) -29.5 0
Note: The above requirements for OC-12 VTM units are for an
Nortel-to-Nortel proprietary link. For a link meeting the Bellcore Midspan
meet specification, the following requirements apply.
OC-12 VTM IR (NT7E05) -28.0 -8.0
OC-12 VTM LR (NT7E05) -28.0 -8.0
continued
Fac OC3/OC12
Step Action
6 If the received power cannot be adjusted to be within the specification

boundaries using the mVOA, measure the received power at the origin in the
network element location (in the fiber patch panel, for example).
7 Do the following:
If the measured power at the origin is Then go to
within range step 8
not within range step 9
8 The fiber patchcord is faulty. Try another patchcord with the same
specifications. Ensure not to bend the fiber more than its bending radius of 76
mm (3 in.). Reconnect the fiber to the optical interface circuit pack.
9 Release the forced switch performed in step 3 by entering:
protectn
where
forced re (depending on where the switch was done)

yes
continued
Fac OC3/OC12
Step Action
10 Access the OC-3/OC-12 performance monitoring section parameters by

entering:
perfmon
facperf oc3 or oc12 <unit>
where
<unit> is the group number of the upstream optical
(circuit pack group) interface g1, g1s, g2, or g2s, g1e, g1w
g3 to g8
Do the following:
If the alarm Then

forced op <unit>
yes
where
continued
Fac OC3/OC12
Step Action
12 Replace the optical interface circuit pack. Refer to Module Replacement

13 Release the forced switch done previously in step 11 by entering:
protectn
where

yes
entering:
perfmon
where
g3 to g8
Do the following:
If the alarm Then
continued
Fac OC3/OC12
Step Action

forced op <unit>
yes
where
16 Replace the optical interface circuit pack at the far-end network element. See
instructions.
17 At the near-end network element, use the OC-3/OC-12 performance
monitoring statistics screen to verify if the problem has been corrected.
continued
Fac OC3/OC12
Step Action

protectn
where

yes
entering:
perfmon
where
g3 to g8
Do the following:
If the alarm Then
persists contact your next level of support or your Nortel
Networks support group. See About the OC-3/OC-12
end
Fac OC3/OC12
Loss of frame
Probable cause
An OC-3/OC-12 frame can no longer be detected on the optical fiber coming
to the equipment. One of the following conditions exists:
a signal degradation (degraded fiber or transmitter failure)
low received optical power
dirty receiver unit connector
malfunctioning mini-variable optical attenuator (mVOA)
a damaged fiber optics patchcord
a defective receiver unit
circuit pack
packs.
Impact
Note: Upon detection of the failure, a high-speed switch occurred and

caused a traffic outage of no more than 60 ms.
continued
Fac OC3/OC12
Loss of frame (continued)
Action
Step Action
1 The fiber connected to the OC-3/OC-12 optics in alarm must be removed in

order to be checked. However, before unplugging the module, ensure that live
traffic is being received by the other OC-3/OC-12 optics.
Do the following:
If Then go to
the circuit in alarm is the step 2
working OC-3/OC-12
optical interface circuit
pack
the circuit in alarm is not step 3. See Module Replacement Procedures,
the working OC-3/OC-12 323-1111-547, for removal and insertion of the
optical interface circuit OC-3/OC-12 optics.
pack
procedure cannot be performed in service since there is no OC-3 tributary to
switch to.
2 Do the following:

protectn
where
continued
Fac OC3/OC12
Step Action

lockout re
yes
lockout re w
yes
or
lockout re p
yes
lockout re
yes
lockout re w
yes
or
lockout re p
yes
3 Do the following:
not raised a t a regenerator network element follow this step

forced op <unit>
yes
where
continued
Fac OC3/OC12
Step Action
4 Unplug the fiber connected to the receive port (top) of the OC-3/OC-12 optics
in alarm which is deprived of traffic, and clean the optical connector as
outlined in Common Procedures, 323-1111-846.

OC-3 IR (NT7E01) -28.0 -8.0
OC-3 LR (NT7E01) -34.0 -10.0
OC-12 IR (NT7E02) -24.5 -4.0
OC-12 LR (NT7E02) -32.0 -7.0
OC-12 ELR (NT7E02) -32.2 -8.0
OC-12 VTM IR (NT7E05) -28.0 0
OC-12 VTM LR (NT7E05) -29.5 0
OC-12 VTM IR (NT7E05) -28.0 -8.0
OC-12 VTM LR (NT7E05) -28.0 -8.0

boundaries, measure the receiving power before the mVOA (for example, at
the fiber patch panel).
6 Do the following:
If the power before the mVOA is Then go to
low step 8
not low step 7
7 The fiber patchcord is faulty. Try another patchcord equipped with an mVOA
having the same attenuation range. Ensure not to bend the fiber more than
what the fiber manufacturer specifies (no more than 76 mm [3 in.] bending
radius). The yellow LED should then turn OFF. If the LED remains ON, go to
step 8.
continued
Fac OC3/OC12
Step Action
8 Move to the upstream site. At the new location, using a patchcord without
mVOA, measure the transmitted power. See Common Procedures,
323-1111-846.
9 Do the following:
If the transmit Then
power is
within the specified go to step 10
limits
not within the replace the OC-3/OC-12 optical interface circuit pack.
specified limits See Module Replacement Procedures, 323-1111-547,
10 If the problem persists, replace the OC-3/OC-12 optical interface circuit pack
reporting the alarm. See Module Replacement Procedures, 323-1111-547,
11 If the problem continues to persist, replace the OC-3/OC-12 optical interface
circuit pack at the far-end network element which is connected to the circuit
pack reporting the alarm. See Module Replacement Procedures,
12 Release the forced switch done previously in step 3 by typing:
protectn
yes
where

end
Fac OC3/OC12
Rx AIS
Probable cause
the OC-3 or OC-12 tributary where the alarm is present is connected to an
isolated node in a ring
Note: In this case, the cause of the alarm is likely the isolated node. Clear
the problem with the isolated node before clearing the alarm.
the OC-3/OC-12 source at the far end of the fiber is experiencing signal
problems or has failed
the facility of OC-3/OC-12 source at the far end of the fiber is out of
service (OOS)
there is a transmit failure at the far end
for ring systems: the equipment of the OC-12 source at the far end of the
fiber is out of service (OOS)
circuit pack
packs.
Impact
This is a warning, not service-affecting (w, nsa) alarm (if protectable) and no
traffic is being carried.
continued
Fac OC3/OC12
Rx AIS (continued)
Action
Step Action
1 Check the OC-3/OC-12 equipment and the OC-3/OC-12 facility at the

OC-3/OC-12 source located at the far end of the fiber. Resolve any failures
on the OC-3/OC-12 equipment or facilities. If the problem persists, go to
step 2.
2 Check whether the OC-3/OC-12 facility at the source is out of service. For
ring systems, check whether the OC-12 equipment at the source is out of
service.
end
Fac OC3/OC12
Rx loss of signal
Probable cause
A signal can no longer be detected on the optical fiber coming into the
equipment. One of the following conditions exists:
a fiber cut
a transmitter failure
insufficient received optical power
dirty receiver unit connector
a malfunctioning mini-variable optical attenuator (mVOA)
circuit pack
packs.
Impact
Upon detection of the failure, a high-speed switch occurred and caused a traffic
outage of no more than 60 ms.
continued
Fac OC3/OC12
Action
Step Action

Do the following:
If the circuit in alarm is Then go to
the working OC-3/OC-12 optical interface circuit pack step 2
not the working OC-3/OC-12 optical interface circuit pack step 3
procedure cannot be performed in service since there is no OC-3 trib to
switch to.
2 Do the following:

protectn
where
continued
Fac OC3/OC12
Step Action

For linear, enter:
lockout re
yes
lockout re w <unit>
yes
or
lockout re p <unit>
yes
For linear, enter:
lockout re
yes
lockout re w <unit>
yes
or
lockout re p <unit>
yes
3 Do the following:

forced op <unit>
yes
where
continued
Fac OC3/OC12
Step Action
4 Unplug the fiber connected to the receive port (top) of the OC-3/OC-12 optics
in alarm which is deprived of traffic, and clean the optical connector as
outlined in Common Procedures, 323-1111-846.

OC-3 IR (NT7E01) -28.0 -8.0
OC-3 LR (NT7E01) -34.0 -10.0
OC-12 IR (NT7E02) -24.5 -4.0
OC-12 LR (NT7E02) -32.0 -7.0
OC-12 ELR (NT7E02) -32.2 -8.0
OC-12 VTM IR (NT7E05) -28.0 0
OC-12 VTM LR (NT7E05) -29.5 0
OC-12 VTM IR (NT7E05) -28.0 -8.0
OC-12 VTM LR (NT7E05) -28.0 -8.0

boundaries, measure the receiving power before the mVOA (for example, at
the fiber patch panel).
6 Do the following:
If the power before the mVOA is Then go to
low step 8
not low step 7
7 The fiber patchcord is faulty. Try another patchcord equipped with an mVOA
having the same attenuation range. Ensure not to bend the fiber more than
what the fiber manufacturer specifies (no more than 76 mm [3 in.] bending
radius). The yellow LED should then turn OFF. If the LED remains ON, go to
step 8.
continued
Fac OC3/OC12
Step Action
8 Move to the upstream site. At the new location, using a patchcord without
mVOA, measure the transmitted power. See Common Procedures,
323-1111-846.
9 If the transmit power is within the specified limits, then go to step 10. If the
transmit power is not within the specified limits, replace the OC-3/OC-12
optical interface circuit pack. See Module Replacement Procedures,
10 If the problem persists, replace the OC-3/OC-12 optical interface circuit pack
reporting the alarm. See Module Replacement Procedures, 323-1111-547,
11 If the problem continues to persist, replace the OC-3/OC-12 optical interface
circuit pack at the far-end network element which is connected to the circuit
pack reporting the alarm. See Module Replacement Procedures,
protectn
yes
where
end
Fac OC3/OC12
Signal degrade
Probable cause
The optical signal coming into the equipment has degraded beyond the signal
degrade threshold (from 10-4 to 10-10). One of the following conditions exists:
a fiber cut
a dirty receiver unit connector
circuit pack
packs.
Impact
This is a minor, not service-affecting (m, nsa) alarm (if protectable)
This is a minor, service-affecting (m, sa) alarm (if not protectable).
Note: Upon detection of the failure, a high-speed switch occurred and

caused a traffic outage of no more than 60 ms.
continued
Fac OC3/OC12
Signal degrade (continued)
Action
Step Action

Do the following:
the working OC-3/OC-12 step 2
optical interface circuit pack
not the working OC-3/OC-12 step 3. See Module Replacement
optical interface circuit pack Procedures, 323-1111-547, for removal and
insertion of the OC-3/OC-12 optics.
switch to.
2 Ensure that there is no lockout by entering:
protectn
where
continued
Fac OC3/OC12
Step Action

lockout re
yes
lockout re w
yes
or
lockout re p
yes
lockout re
yes
lockout re w
yes
or
lockout re p
yes
3 Force the live traffic to the other OC-3/OC-12 optics by entering:
forced op <unit>
yes
where
continued
Fac OC3/OC12
Step Action
OC-3 IR (NT7E01) -28.0 -8.0

OC-3 LR (NT7E01) -34.0 -10.0
OC-12 IR (NT7E02) -24.5 -4.0
OC-12 LR (NT7E02) -32.0 -7.0
OC-12 ELR (NT7E02) -32.2 -8.0
OC-12 VTM IR (NT7E05) -28.0 0
OC-12 VTM LR (NT7E05) -29.5 0
Note: The above requirements for OC-12 VTM units are for an proprietary
link. For a link meeting the Bellcore Midspan meet specification, the
following requirements apply.
OC-12 VTM IR (NT7E05) -28.0 -8.0
OC-12 VTM LR (NT7E05) -28.0 -8.0

7 Do the following:
within range step 8
8 The fiber patch cord may be faulty. Try another patch cord with the same
continued
Fac OC3/OC12
Step Action

entering:
perfmon
where
(circuit pack group) interface g1, g1s, g2, or g2s, g1e, g1w, or
g3 to g8
Monitor this screen. Errors indicate that the far-end optical interface circuit
pack is faulty.
10 Check the source power levels at the transmitter.
If Then go to
source power levels at the step 11
transmitter are faulty
power levels at the Repair the fiber optic cable. See Module
transmitter are correct Replacement Procedures, 323-1111-547, for
information on repairing optical fibers.
instructions.
If Then go to
the problem has been corrected step 14
the problem has not been corrected step 13
13 Replace the near-end optical interface circuit pack. Refer to Module

Go to step 12.
continued
Fac OC3/OC12
Step Action

protectn
where

yes
end
Fac OC3/OC12
Signal fail
Probable cause
The optical signal coming into the equipment has degraded beyond the signal
fail threshold (from 10-3 to 10-5). One of the following conditions exists:
a fiber cut
a dirty receiver unit connector
a damaged fiber optics patch cord
circuit pack
packs.
Impact
Upon detection of the failure, a high-speed switch occurred and caused a traffic
outage of no more than 60 ms.
continued
Fac OC3/OC12
Signal fail (continued)
Action
Step Action

Do the following:
the working OC-3/OC-12 step 2
optical interface circuit pack
not the working OC-3/OC-12 step 3. See Module Replacement
optical interface circuit pack Procedures, 323-1111-547, for removal
and insertion of the OC-3/OC-12 optics.
switch to.
protectn
where
continued
Fac OC3/OC12
Step Action

lockout re
yes
lockout re w
yes
or
lockout re p
yes
lockout re
yes
lockout re w
yes
or
lockout re p
yes
3 Force the live traffic to the other OC-3/OC-12 optics by entering:
forced op <unit>
yes
where
continued
Fac OC3/OC12
Step Action
OC-3 IR (NT7E01) -28.0 -8.0

OC-3 LR (NT7E01) -34.0 -10.0
OC-12 IR (NT7E02) -24.5 -4.0
OC-12 LR (NT7E02) -32.0 -7.0
OC-12 ELR (NT7E02) -32.2 -8.0
OC-12 VTM IR (NT7E05) -28.0 0
OC-12 VTM LR (NT7E05) -29.5 0
OC-12 VTM IR (NT7E05) -28.0 -8.0
OC-12 VTM LR (NT7E05) -28.0 -8.0

7 Do the following:
within range step 8
8 The fiber patch cord may be faulty. Try another patch cord with the same
continued
Fac OC3/OC12
Step Action

entering:
perfmon
where
(circuit pack group) interface g1, g1s, g2, g2s, g1e, g1w, or
g3 to g8
Monitor this screen. Errors indicate that the far-end optical interface circuit
pack is faulty.
10 Check the source power levels at the transmitter.
If Then go to
source power levels at the step 11
transmitter are faulty
power levels at the Repair the fiber optic cable. See Module
transmitter are correct Replacement Procedures, 323-1111-547, for
information on repairing optical fibers.
instructions.
If Then go to
the problem has been corrected step 14
the problem has not been corrected step 13
13 Replace the near-end optical interface circuit pack. Refer to Module

continued
Fac OC3/OC12
Step Action
14 Release the forced switch done previously in step 3 by typing:

protectn
where

yes
end
Fac OC3/OC12
STS1 Rx AIS 5
Probable cause
The local equipment is receiving an STS-1 alarm indication signal from the
STS1 connection. One of the following conditions exists:
an upstream facility failure
an upstream equipment failure
Note 1: This alarm is masked by the STS1 Rx loss of pointer alarm. This
alarm masks the following alarms: STS1 Rx path trace mismatch, STS1 Rx
RFI, STS1 Rx unequipped, and STS1 signal label mismatch.
Note 2: This alarm can be caused by STS1/OC3 LOF, LOS, or AIS on the
far end which may be masked by the automatic in-service (AINS) feature.
Impact
Action
Step Action
1 On the OPC, enter the Connection Mngr, which is in the Network Admin
toolset. Look for the facility where the alarm is raised to determine the other
end point of the STS1 connection.
2 If the equipment at the far end of the STS-1 connection is an STS-1 interface
circuit pack, then if Rx loss of signal, Rx loss of frame, Rx path AIS facility
alarms are raised against it, follow the appropriate procedures in this manual
for clearing these alarms. These alarms cause the STS Rx AIS alarm.
3 Check that there are no equipment alarms raised against the equipment at
the far end of the STS-1 connection. If there are alarms raised against it, then
follow the appropriate procedures in this manual for clearing these alarms.
Verify that the state of the equipment is in service.
continued
Fac OC3/OC12
STS1 Rx AIS (continued)
Step Action
4 Using the OPC, check for any alarms on intermediate nodes through which
the STS connection passes. If equipment or facility alarms against the
primary or secondary optics on these intermediate nodes are found, then
follow the appropriate procedures for clearing them.
5 From the far end network element user interface perform a manual switch on
the far end equipment. If the alarm clears, then see Module Replacement
6 From the local network element user interface, perform a manual switch on
the DS1 or DS3 circuit pack by entering:
protectn
dtlprot <type>
manual op <unit>
yes
where
<type> is ds1 or ds3
<unit> is g1 to g12
7 If the problem clears, then see Module Replacement Procedures,

323-1111-547, for replacement instructions. If the problem does not clear,
then release the manual switch by entering:
protectn
dtlprot <type>
manual re <unit>
yes
where
<type> is ds1 or ds3
<unit> is g1 to g12
end
Fac OC3/OC12
STS1 Rx loss of pointer
Probable causes
The STS-1 pointer is corrupted (equivalent to losing frame). One of the
defective far-end DS1 VT mapper circuit pack or DS3 STS mapper circuit
pack
defective local DS1 VT mapper circuit pack or DS3 STS mapper circuit
pack
defective far-end OC-3/OC-12 optical interface circuit pack
defective local OC-3/OC-12 optical interface circuit pack
bad synchronization of the network
information.
Impact
A switch to the protection circuit pack is initiated, resulting in a traffic outage
of 60 ms maximum.
Action
Step Action

alarms
2 If the protection switch initiated by the system clears the alarm, replace the
circuit pack from which the protection switch occurred. If the alarm is not
cleared, go to step 3.
3 Check if a protection switch of the equipment which the STS-1 originates on
at the far end of the fiber optics clears the problem, then replace the card. If
the alarm is not cleared, go to step 4.
4 Verify the synchronization of the NEs between the two end points of facility.
Ensure that all NEs are synchronized with a proper source and settings.
end
Fac OC12
Degraded timing reference
Probable cause
The ESI cannot synchronize to the incoming timing reference input signal.
The accuracy of the affected timing reference is lower than the accuracy of the
internal clock. The accuracy of a reference is determined either by the
provisioned value or from the S1 byte in the SONET overhead.
Impact
Action
Step Action
1 Check provisioning. If provisioned for automatic (no P under the quality level
field), then check upstream.
2 If the provisioning is correct, contact your next level of support or your Nortel
323-1111-090.
end
Fac OC12 50
Inter-ring both feeds fail
(matched nodes on rings only) 5
Probable cause
This alarm indicates that both the primary and secondary feeds for a
matched-node connection have failed. It is raised on the primary add node (the
selector node) for the connection.
The following are the most probable causes of the alarm (see Figure 5-3 on
page 5-140):
a facility or equipment provisioning problem at the service access point
failures affecting both the primary and the secondary feeds
the primary drop node in the upstream ring is isolated and a failure is also
present on the secondary feed
there is a drop-and-continue on protection (DCP) provisioning scheme for
the connection, there is an OC-12 protection switch active, and the primary
feed has failed
The alarm is raised on a per-STS channel basis.
CAUTION
This alarm does not necessarily indicate that a problem exists
at the network element raising the alarm. The alarm can be
raised as the result of failures upstream. Therefore, only take
corrective actions based on the instructions in this procedure or
procedures associated with other currently active alarms.
Impact
Major, service affecting.
continued
Fac OC12
Inter-ring both feeds fail (matched nodes on rings only) (continued)
Action
Step Action
1 Check the alarm details for the Inter-ring both feeds fail alarm. The alarm
details include information on the tributaries the connection uses and the
STS-1 channel used for the secondary feed. Log in to the network element
and check the alarm details as follows:
alarms
dtlalms <alarm number>
where
<alarm number> is the number corresponding to the one-line
alarm report under the heading Alm. If you do not
specify an alarm number, the most severe alarm
appears.
You can also use the OPC Alarm Monitor tool to display the alarm details (see
Network Surveillance Procedures, 323-1111-510).
2 Check for other alarms indicating that the node serving as the primary drop
gateway in the upstream ring is isolated. Also check for alarms that indicate
a failure of the secondary feed. Clear any active alarms in the order of their
severity according to the procedures in this document.
3 Check for alarms indicating provisioning problems at the node serving as the
service access point. Clear any active alarms in the order of their severity
according to the procedures in this document.
4 Check the provisioning of the equipment and facilities at the service access
point according to Provisioning and Operations Procedures, 323-1111-310.
end
Fac OC12 50
Inter-ring forced switch request 5
Probable cause
Note: This alarm applies to OC-12 rings with matched-node connections.
This alarm indicates that a forced switch has been requested for a matched
node connection. The alarm is the result of a user-initiated forced-switch
request.
The alarm is raised when the forced-switch request is made and clears when
request is released.
Impact
Action
No action is necessary if a maintenance operation is being performed. This
alarm serves as a reminder to users not to leave a potentially service affecting
condition on the system (especially if running live traffic).
Step Action
1 Release the forced-switch request from the Selector Status menu in the OPC
Connection Manager tool. If you are unfamiliar with the Connection Manager,
see Provisioning and Operations Procedures, 323-1111-310.
end
Fac OC12
Inter-ring protection switch complete 5
Probable cause
Note: This alarm applies to OC-12 rings with matched-node connections.
This alarm is active when the secondary feed is selected in place of the primary
feed in a matched node configuration between two rings (that is, an Inter-ring
protection switch is active). It is raised when the selection of the secondary
feed is made and is cleared when the selection reverts to the primary feed. The
switch trigger field in the alarm details indicates the cause of the
protection-switch request (for example, a forced switch or signal fail).
Impact
Action
Step Action
1 Check the alarm details. The alarm details include information on the
tributaries the connection uses and the STS-1 channel used for the
secondary feed. Log in to the network element and check the alarm details
as follows:
alarms
dtlalms <alarm number>
where
<alarm number> is the number corresponding to the one-line
alarm report under the heading Alm. If you do not
specify an alarm number, the most severe alarm
appears.
You can also use the OPC Alarm Monitor tool to display the alarm details (see
2 Check the switch trigger field of the Alarm Details to identify the cause of the
protection switch.
continued
Fac OC12
Inter-ring protection switch complete (continued)
Step Action

OS.0857

Network View . . 1 . . . . .
St.Johns . . 1 . . . . .
DtlAlms 1.1.63
2 Next
3 Prev AlmRpt: 324 Cleared
4 Address: OC12 G1 chnl 1, 63 w,nsa
5 Shelf 1 17:32:01
6 Location: Frame ShPos 1 13 Nov 12
7 NewAlms Reason: Inter-ring protection switch complete Facility
8 SwTrig: Path AIS Trib: STS1 G1 1
9
10 DtlProt
11
12
13 DTLALMS:
14 Port
15 Equipmnt
16 Facility
17
18 Help
NE 63
Time 17:35 >
Do the following:
the result of a user-initiated no action is required.
switch (that is, a forced or It is assumed that a maintenance activity
manual switch) is under way.
the result of an automatic go to step 3
protection switch
3 Check the Trib field of the Alarm Details.

continued
Fac OC12
Step Action
Do the following:
If Then
no tributary information the tributary circuit pack serving the
exists (or the field matched-node connection is not physically
contains UNEQ) installed in the shelf, not provisioned, or not
carrying traffic
the tributary is a Circuit-pack missing alarm should be present.
provisioned to be in To determine which tributary is missing, check the
service but is physically Alarm Details.
missing
no circuit pack missing use the Connection Manager tool of the OPC or
alarm exists the CI tool Connmap on the network element to
view the Connection Details for the identified
OC-3/OC-12 circuit pack group. If you are
unfamiliar with the Connection Manager or the CI
tool Connmap, see Provisioning and Operations
Once you have identified which tributary is missing, install the appropriate
type of tributary circuit pack according to the instructions in Module
Replacement Procedures, 323-1111-547. Then go to step 4.
4 For STS-1 tributaries, check the service state of the facility serving the
connection.
If the facility is not in service, it may be the cause of the alarm at the primary
node. To put the facility back in service, enter the following command at the
network element user interface:
facility sts1 <unit> <port number>
where:
<unit> is g1 to g4
<port no.> is 1 to 3
chgstate is
information on provisioning commands.
continued
Fac OC12
Step Action
5 Check the provisioning of the connection. If the connection on the OPC and
the network element are correct, and the facility is in service, ensure that the
physical connection is correct.
6 Check for alarms relating to the facilities serving the matched-node
connection.
Do the following:
If Then
a line alarm exists this alarm must be cleared before the protection switch
such as an Rx loss can clear.
of signal (LOS) Rx LOS conditions are also indicated by a yellow LED
on the affected tributary circuit pack.
an STS-1 path the failure is in the ring supplying the signal.
alarm exists such Ensure that the facilities relating to the path are in
as a loss of pointer service at the source node. Verify that path alarms for
(LOP) or path AIS the source and intermediate rings are cleared.
7 Check for alarms relating to the tributary equipment serving the

matched-node connection. (For example, an OC-12/STS-12 circuit pack fail
or bipolar violation alarm).
Do the following:
If Then
the tributary circuit the failure is caused by either a lockout of the
pack that carries the tributary mapper circuit pack or the protection
primary feed has an mapper circuit pack is not available
unprotected failure
a lockout exists release it
the tributary mapper is replace it according to the appropriate procedure in
failed (its red LED is lit) Module Replacement Procedures, 323-1111-547
8 If the alarm is still active, contact your Nortel Networks support group by
following the instructions in About the OC-3/OC-12 NETBM Library,
323-1111-090.
end
Figure 5-3
Possible failure areas
OS.0856
Service
access
point
Source
node
Fiber 1
Ring A
(drop ring) Primary Secondary
node Probable node
Possible failure
provisioning area Possible
problem provisioning
problem
Probable failure area Probable failure area
Primary SS Secondary
node node
Ring B
(add ring)
End
node
Service
Legend: access point
(receives AIS)
= Single fiber cable with 6 working

and 6 protection timeslots
= Direction of traffic flow on working STS-1 timeslots (1 through 6)
= Direction of traffic flow on protection STS-1 timeslots (7 through 12)
AIS = Alarm indication signal
SS = Service selector
Note: For clarity, only one direction of traffic flow is shown.
Fac OC12 50
Inter-ring lockout request 5
Probable cause
This is a user initiated request to ensure that traffic remains on the primary
feed.
Impact
Action
Step Action
1 No action is required if a test or maintenance is under way. This alarm serves

as a reminder to users not to leave a potentially service-affecting condition on
the system.
2 Release the lockout request from the Selector Status menu in the OPC
Connection Manager tool. If you are unfamiliar with the Connection Manager,
see Provisioning and Operations Procedures, 323-1111-310.
end
Fac OC12 50
Inter-ring manual switch request 5
Probable cause
This is a user initiated request to manually switch the traffic to the protection
path.
Impact
Action
Step Action
1 No action is required if a test or maintenance is under way. This alarm serves

as a reminder to users not to leave a potentially service-affecting condition on
the system.
2 Release the manual switch request from the Selector Status menu in the
OPC Connection Manager tool. If you are unfamiliar with the Connection
Manager, see Provisioning and Operations Procedures, 323-1111-310.
end
Fac OC12 50
Line FE CV threshold 1, 2
Line FE ES threshold 1, 2
Line FE SES threshold 1, 2
Line FE UAS threshold 1, 2 5
Probable cause
An STS-1 path performance monitoring parameter threshold has been crossed.
Impact
Action
Note: Assume that the far-end alarm has occurred on G1 (Node B, Figure
5-4).
Step Action
1 Do the following:
If an Rx alarm Then
exists on G2 (Node A, Figure follow the procedure to clear the Fac OC12
5-4) Line Rx CV, ES, SES, UAS threshold 1, 2
on G2 (Node A, Figure 5-4) in this NTP. If
the alarm persists, go to step 2.
does not exist on G2 (Node A, go to step 2
Figure 5-4)
continued
Fac OC12
Line FE CV threshold 1, 2
Line FE ES threshold 1, 2
Line FE SES threshold 1, 2
Line FE UAS threshold 1, 2 (continued)
Step Action
2 Do the following:
If an Rx alarm Then
exists on G1 (Node B, Figure follow the procedure to clear Fac OC12
5-4) Line Rx CV, ES, SES, UAS threshold 1, 2
on G1 (Node B, Figure 5-4) in this NTP. If
the alarm persists, contact your next level
of support or your Nortel Networks support
group.
does not exist on G1 (Node B, contact your next level of support or your
Figure 5-4) Nortel Networks support group
Figure 5-4
VTM BLSR configuration (for example, in a four-node ring)
FW-3404
A B
G2 G1
G1 G2
D C
FW-3404
end
Fac OC12 50
Rx Inter-ring secondary feed fail
Probable cause
This alarm indicates that the secondary feed for a matched-node connection
has failed in the receive direction. It is raised on the primary add node (the
selector node) for the connection.
The following are the most probable causes of the alarm:

a facility or equipment provisioning problem at either the add or drop
tributary serving the secondary feed
failures affecting either the add or drop tributary serving the secondary
feed
Only one alarm can be raised per OC-12 facility, regardless of how many
matched-node connections on that node have failed.
For drop-and-continue on protection (DCP) connections, this alarm is

expected whenever there is an intra-ring OC-12 protection switch in the ring
experiencing this alarm.
Impact
Enabled by default.
Action
Step Action
1 Check whether there is also an Inter-ring both feeds fail alarm active. If so,
see Inter-ring both feeds fail (matched nodes on rings only) on page 5-133
for alarm-clearing instructions.
continued
Fac OC12
Rx Inter-ring secondary feed fail (matched nodes on rings only) (continued)
Step Action
2 Check for any other active alarms and clear them in the order of their severity
according to the alarm-clearing procedures in this document. Check
especially for the following alarms:
an OC-12 Protection switch complete alarm in either an upstream ring
on the matched-nodes path or the ring experiencing the Rx Inter-ring
secondary feed fail alarm
an STS channel fail alarm
a line AIS or path AIS alarm
equipment alarms on the primary and secondary gateway nodes
end
Fac OC12 50
Section Rx optical power threshold 5
Probable cause
a defective fiber
a fiber is in the process of failing
a dirty connector
Impact
Note: This alarm supports a condition that might affect service when it is
raised in combination with other critical alarms. Under these
circumstances, the other critical alarms will affect service. In isolation, this
alarm in not service affecting.
Action
Step Action
1 Check the power levels on optical fibers with optical power meter.
Do the following:
If the Then
power levels are correct reinsert the fiber
power levels are incorrect readjust the power levels
alarm persists go to step 2
2 Check the threshold provisioning screen.

Do the following:
If the provisioned value is Then
not appropriate reprovision the value
appropriate call your Nortel Networks representative
end
Fac OC12 50
STS1 path FE CV threshold 1, 2
STS1 path FE ES threshold 1, 2
STS1 path FE SES threshold 1, 2
STS1 path FE UAS threshold 1, 2 5
Probable cause
Note: STS-1 Path performance monitoring is supported only if the STS-1
path of VT-managed traffic is terminated on OC-12 ring ADMs.
Impact
Action
Note: Assume that the far-end alarm has occurred on G1 (Node B, Figure
5-5).
Step Action
1 Do the following:
If a Rx alarm Then
exists on G2 (Node A, Figure follow the procedure to clear the Fac OC12
5-5) STS1 path Rx CV, ES, SES, UAS
threshold 1, 2 on G2 (Node A, Figure 5-5)
in this NTP. If the alarm persists, go to
step 2.
does not exist on G2 (Node A, go to step 2
Figure 5-5)
continued
Fac OC12
STS1 path FE CV threshold 1, 2
STS1 path FE ES threshold 1, 2
STS1 path FE SES threshold 1, 2
STS1 path FE UAS threshold 1, 2 (continued)
Step Action
2 Do the following:
If a Rx alarm Then
exists on G1 (Node B, Figure 5-5) follow the procedure to clear Fac
OC12 STS1 path Rx CV, ES,
SES, UAS threshold 1, 2 on G1
(Node B, Figure 5-5) in this NTP. If
the alarm persists, contact your
next level of support or your Nortel
Networks support group.
does not exist on G1 (Node B, Figure contact your next level of support
5-5) or your Nortel Networks support
group
Figure 5-5
VTM BLSR configuration (for example, in a four-node ring)
FW-3404
A B
G2 G1
G1 G2
D C
FW-3404
end
Fac OC12
STS1 path Rx CV threshold 1, 2
STS1 path Rx ES threshold 1, 2
STS1 path Rx SES threshold 1, 2
STS1 path Rx UAS threshold 1, 2 5
Probable cause
Note: STS-1 Path performance monitoring is supported only if the STS-1
path of VT-managed traffic is terminated on OC-12 ring ADMs.
Impact
Note 2: It is assumed that these thresholds have been provisioned as
alarms and are turned on (activated). If they are not provisioned as alarms,
these alarm points will show up as performance alerts.
continued
Fac OC12
STS1 path Rx UAS threshold 1, 2 (continued)
Action
Step Action
1 The fiber connected to the OC-12 optics in alarm must be removed for
checking. However, before unplugging the module, ensure that live traffic is
being received by the other OC-12 optics.
Do the following:
If the circuit in alarm is Then
the working OC-12 optical go to step 2
interface circuit pack
not the working OC-12 go to step 3. See Module Replacement
optical interface circuit pack Procedures, 323-1111-547, for removal and
insertion of the OC-12 optics.

protectn
dtlprot <type>
where
<type> is oc12

lockout re
yes
lockout re
yes
continued
Fac OC12
Step Action
3 Force the live traffic to the other OC-12 optics by entering:

forced op <unit>
yes
where
<unit> is g1, g2, g2s, g1s
OC-12 IR (NT7E02) -24.5 -4.0
OC-12 LR (NT7E02) -32.0 -7.0
OC-12 ELR (NT7E02) -32.2 -8.0

OC-12 VTM IR (NT7E05) -28.0 0
OC-12 VTM LR (NT7E05) -29.5 0
OC-12 VTM IR (NT7E05) -28.0 -8.0
OC-12 VTM LR (NT7E05) -28.0 -8.0
continued
Fac OC12
Step Action

7 Do the following:
within range step 8
8 The fiber patchcord is faulty. Try another patchcord with the same
9 Release the forced switch performed in step 3 by entering:
protectn
dtlprot <type>
where
<type> is oc12

yes
10 Access the STS-1 Path performance monitoring section parameters by
entering:
perfmon
facperf path sts oc12 <unit> <port> [<origin>]
where
(circuit pack group) interface g1, g2
<port> is the working channel number (1 to 6)
<origin> is near or far (default is near)
continued
Fac OC12
Step Action
Do the following:
If the alarm Then

forced op <unit>
yes
where
<unit> is g1, g2
12 Replace the optical interface circuit pack. Refer to Module Replacement

protectn
dtlprot <type>
where
<type> is oc12

yes
continued
Fac OC12
Step Action

entering:
perfmon
where
Do the following:
If the alarm Then

forced op <unit>
yes
where
<unit> is g1, g2
instructions.
17 At the near-end network element, use the STS-1 Path performance
continued
Fac OC12
Step Action

protectn
dtlprot <type>
where
<type> is oc12

yes
entering:
perfmon
where
Do the following:
If the alarm Then
persists contact your next level of support or your Nortel
Networks support group. See About the OC-3/OC-12
end
Fac OC12
STS1 Rx RFI
Probable cause
The local OC-12 circuit pack has received a Remote Failure Indication (RFI)
because a signal problem is detected on the downstream equipment. The
far-end network element transmitting the RFI has detected an STS1 AIS or
STS1 Loss of Pointer from the network element receiving the RFI.
Impact
Action
Step Action
alarms
STS connection passes should clear the STS1 Rx RFI alarm.
end
Fac OC12
STS1 Rx unequipped
Probable cause
The local OC-12 circuit pack is not receiving an STS-1 payload. One of the
the far-end OC-12 facility is not in service (IS)
all the VT1.5 connections originate at the far-end NE and their facilities are
deleted
the far-end OC-12 circuit pack is defective
Impact
Action
Step Action
1 Verify that the STS connection is correctly assigned to the facility for both end
points using either the OPC Connection Manager or TL1, depending on which
method is in use. If the STS connection is incorrect, edit the connection with
the proper values.
continued
Fac OC12
Step Action
3 Verify that the VT1.5 connection has been provisioned correctly using the
OPC Connection Manager or TL1, depending on which method you are
using. If theVT1.5 connection is incorrect, edit the connection with the proper
values.
Description, 323-1111-190, for the TL1 procedure.
Do the following:
If the alarm Then
5 Verify that the far-end OC-12 facility is in service by entering:

fa oc12 <circuit pack group>
where
<circuit pack group> is the circuit pack group obtained in step 2

If the facility is not provisioned, provision it by entering:
add
If the alarm Then
continued
Fac OC12
Step Action
6 Determine if all the VT1.5 connections verified in step 3 terminate at the

far-end NE. Verify that the associated facilities are not all deleted. If they are,
provisioning one such facility will clear the alarm.
7 If the far-end STS and VT1.5 connected facilities are in service and the alarm
persists, replace the far-end OC-12 circuit pack. See Module Replacement
8 If the problem persists, contact your next level of support or your Nortel
323-1111-090.
end
Fac OC12
Timing reference interface fail
Probable cause
loss of frame (LOF)
OC-12 equipment failure
OC-12 facility out of service (OOS)
Impact
This is a major, not service-affecting (M, nsa) alarm (if unprotectable).
Action
Step Action
1 Clear any OC-12 equipment or facility alarms. See the appropriate alarm
clearing procedures in this document.
2 Verify the OC-12 facility. If the facility is out of service (OOS), place the facility
in service (IS).
323-1111-090.
end
Fac OC12 50
Tx loss of Inter-ring secondary feed
Probable cause
This alarm indicates that the secondary feed for a matched-node connection
has been lost in the transmit direction as the result of an OC-12 protection
switch. It is raised on the primary drop node (the broadcast node) for the
connection when an OC-12 protection switch occurs in the dropping ring. It is
valid only for drop-and-continue on protection (DCP) connections.
Only one alarm can be raised per OC-12 facility, regardless of how many
matched-node connections on that node have failed.
Impact
Enabled by default.
The traffic on primary feed is unaffected and there is no affect on service.

However, there is no protection available for the primary feed in the event of a
failure that affects the primary feed.
Action
Step Action
1 Check for the cause of the protection switch in the dropping ring. Clear the
cause of the protection switch according to the alarm-clearing procedures in
this document.
end
Fac OC12 50
Undefined sync status message 5
Probable cause
The network element received a synchronization status message with a value
not defined in the standard set of SONET synchronization messages or that it
does not recognize.
This alarm becomes active when the network element detects the condition. It
clears when the network element receives a SONET-defined value. For a list of
supported synchronization status messages and related information, see
Timing and Synchronization Description, 323-1111-192.
Note: The OC-12 network element uses and recognizes the

user-assignable RES (reserved) message as defined in the SONET
standards. If an NE receives this message, it does not raise the Undefined
synchronization status message alarm. The NE sends out the RES
message to other subtending TBMs only when timing for the NE has been
set to VTMlinetimed and the NE goes into holdover. When a TBM sends
the RES message, subtending OC-3 NEs that derive timing from an NE
using OC-3 synchronization status messaging (SSM) receive DUS.
Impact
Minor, non-service affecting
Action
Step Action
1 Check the BITS or upstream OC-12 network element sending the message.
Determine why it is not sending a standard synchronization value as defined
in the SONET standards. For example, the equipment might not be fully
SONET compliant.
2 Refer to the manufacturers documentation. Determine whether you can
reprovision, update, or replace the upstream equipment providing the
synchronization message so that it sends a valid value.
3 If there is no way to get the upstream equipment to send a valid message, the
alarm must remain active. You cannot deprovision this alarm.
end
Fac Remt
First-Alert connection down
Probable cause
The connection between the TBM and the S/DMS TransportNode Express has
been lost. One of the following conditions exists:
a facility SONET DCC link fail exists between the TBM and the S/DMS
TransportNode Express, which raises the SONET DCC link fail alarm
the S/DMS TransportNode Express is temporarily unavailable
an invalid address has been specified at the TBM in the First Alert
configuration while adding the OC-3 to the list of NEs monitored by the
TBM
the shelf processor at the S/DMS TransportNode Express for which the
alarm is raised has been replaced
Impact
continued
Fac Remt
First-Alert connection down (continued)
Action
Step Action
1 Do the following:
If Then
you were attempting to add see the procedure for adding an OC-3 to the list
the OC-3 to the list of NEs of NEs monitored by the TBM in S/DMS
monitored by the TBM and TransportNode Express Security and
this alarm was raised Administration, 323-1051-302.
(The wrong address information may have
been entered using the First Alert command
interpreter [ci].)
the connection between the go to step 2
TBM and S/DMS
TransportNode Express
had been working and just
went down
the shelf processor at the see the shelf processor replacement procedure
S/DMS TransportNode in S/DMS TransportNode Express Alarm and
Express for which this alarm Trouble Clearing Procedures, 323-1051-543
is raised was replaced
2 Do the following:
If Then
a Fac SDCC link fail alarm perform the appropriate alarm clearing
exists procedure in this NTP
the Express is unavailable verify the state of the Express node.
See S/DMS TransportNode Express Alarm
and Trouble Clearing Procedures,
323-1051-543 for details.
end
Fac STS1
Line Rx BCV threshold 1, 2
Line Rx BES threshold 1, 2
Line Rx BSES threshold 1, 2
Probable cause
STS-1 performance threshold has been crossed on one of the metallic
facilities. The following performance-monitoring parameters are provided:
BCV: bipolar coding violation
BES: bipolar errored seconds
BSES: bipolar severely errored seconds
CV: code violation
ES: errored second
SES: severely errored second
UAS: line unavailable seconds
a faulty STS-1 input cable or connector
a failed STS-1 interface circuit pack
a problem with the source of the STS-1 signal
Impact
Note 1: It is assumed that these alarms have been provisioned as alarms

and are turned on (activated). If not, these alarms show up as performance
alerts.
continued
Fac STS1
Line Rx UAS threshold 1, 2 (continued)
Note 3: This procedure is service affecting.

Note 4: Refer to Performance Monitoring Description, 323-1111-105, for
more information on performance-monitoring thresholds.
Action
Step Action
1 Locate the STS-1 port connectors on the BNC I/O circuit pack allocated to the
port reporting the errors. Examine the STS-1 cable connected to the In
connector of the concerned STS-1 port. Ensure that the correct connector is
Do the following:
If Then
2
CAUTION
Ensure that the correct STS-1 cable is unplugged.
Removing the wrong one will cause another STS-1
signal to be lost.
Unplug the input STS-1 cable from the BNC I/O circuit pack and connect it to
a STS-1 receiver test set. Verify that a STS-1 signal is present on the cable
and that the test set does not detect any errors.
Do the following:
If Then
no errors are detected reconnect the STS-1 cable and go to step 4
continued
Fac STS1
Line Rx UAS threshold 1, 2 (continued)
Step Action
3 If errors were detected at the BNC I/O circuit pack (in step 2) verify the signal
at the source with the STS-1 test set.
Do the following:
If errors are Then
detected repair the source generating the STS-1 signal
not detected repair the STS-1 cable. Go to step 6.
4
CAUTION
another STS-1 signal to be lost. Replacing the BNC I/O
circuit pack will also cause the loss of the STS-1 signal
At this point the STS-1 cable and the STS-1 signal source have been verified.
If errors are still occurring, then replace the BNC I/O circuit pack associated
5 If the problem persists, replace the STS-1 circuit pack carrying this facility.
instructions.
Library, 323-1111-090.
end
Fac STS1
Loopback
Probable cause
An STS-1 loopback has been operated and is currently active.
Impact
Action
Step Action
1 This is a normal indication when the loopback is ON for testing purposes. No

action is required if this is the case.
facility sts1 <unit> <port #>
loopback re
where
<unit> g1 to g4
3 If you want to put the STS-1 facility back in service, type:

chgstate is
details.
end
Fac STS1
Probable cause
Bipolar violations have been detected on the incoming STS-1 line. One of the
a faulty coaxial connector
a defective cable
defective STS-1 source equipment
a defective STS-1 interface circuit pack
a defective signal
Note: This alarm is masked by the Rx loss of signal alarm. It can also
be masked by the automatic in-service (AINS) feature.
Impact
Action
Step Action
port reporting the errors. Examine the STS-1 cable connected to the In
connector of the concerned STS-1 port. Ensure that the correct connector is
Do the following:
If Then
continued
Fac STS1
Step Action
2
CAUTION
signal to be lost.
and that the test set does not detect any errors.
Do the following:
If errors are Then
detected reconnect the STS-1 cable and go to step 4
not detected go to step 3
3 If errors were detected at the BNC I/O circuit pack (in step 2) verify the signal
at the source with the STS-1 test set.
Do the following:
If errors are Then
detected repair the source generating the STS-1 signal
not detected repair the STS-1 cable. Go to step 6.
4
CAUTION
If errors are still occurring, then replace the BNC I/O circuit pack associated
continued
Fac STS1
Step Action
instructions.
Library, 323-1111-090.
end
Fac STS1
Rx loss of frame
Probable cause
The STS-1 frame cannot be detected on the incoming STS-1. One of the
a defective cable or connection
a defective STS-1 electrical interface circuit pack
a defective BNC I/O circuit pack
a faulty signal
Impact
Action
Step Action
port reporting the loss of frame. Examine the STS-1 cable connected to the
In connector of the concerned STS-1 port. Ensure that the correct connector
is used and is well secured at the source and at the BNC I/O circuit pack.
Do the following:
If Then
continued
Fac STS1
Step Action
2
CAUTION
signal to be lost.
and that the test set does not detect a loss of frame.
Do the following:
If Then
no loss of frame is detected reconnect the STS-1 cable and go to
step 4
3 Do the following:
If Then
a loss of frame was detected verify the signal at the source with the
at the BNC I/O circuit pack (in STS-1 test set
step 2)
a loss of frame is detected repair the source generating the STS-1
signal
no loss of frame is detected repair the STS-1 cable. Go to step 6.
continued
Fac STS1
Step Action
4
CAUTION
If loss of frame is still occurring, then replace the BNC I/O circuit pack
instructions.
Library, 323-1111-090.
end
Fac STS1
Rx loss of signal
Probable cause
The STS-1 frame cannot be detected on the incoming STS-1. One of the
a defective cable or connection
a defective STS-1 electrical interface circuit pack
a defective BNC I/O circuit pack
a faulty signal
Impact
Action
Step Action
port reporting the loss of signal. Examine the STS-1 cable connected to the
In connector of the concerned STS-1 port. Ensure that the correct connector
is used and is well secured at the source and at the BNC I/O circuit pack.
Do the following:
If Then
continued
Fac STS1
Step Action
2
CAUTION
signal to be lost.
and that the test set does not detect a loss of signal.
Do the following:
If Then
no loss of signal is detected reconnect the STS-1 cable and go to step 4
3 Do the following:
If Then
a loss of signal was detected at the verify the signal at the source with the
BNC I/O circuit pack (in step 2) STS-1 test set
a loss of signal was detected repair the source generating the STS-1
signal
no loss of signal was detected repair the STS-1 cable needs to be
repaired. Go to step 6.
continued
Fac STS1
Step Action
4
CAUTION
If loss of signal is still occurring, then replace the BNC I/O circuit pack
instructions.
Library, 323-1111-090.
end
Fac STS1
Rx Line AIS
Probable cause
The external equipment is experiencing signal problems and is sending a
STS-1 alarm indication signal (AIS) to the STS 1 equipment.
Impact
Action
Step Action
1 Verify the external equipment connected to the shelf, by connecting an STS-1

test set to the output of the source.
end
Fac STS1
Rx RFI
Probable cause
A Remote Failure Indication (RFI) alarm is raised when a remote defect
indication condition is received from the far-end node originating the STS1
line signal. The remote defect indication condition is sent because an STS1
LOS, STS1 LOF, or STS1 Line AIS is received on the STS1 line signal at the
far end.
Note: This alarm can be caused by STS1 Rx LOS/Rx LOP on the far end
which may be masked by the automatic in-service (AINS) feature.
Impact
Action
Step Action
1 Check for STS1 LOS, STS1 LOF, or STS1 Line AIS on the far-end node
where the STS1 line signal originates. Clear the alarms according to the
appropriate alarm clearing procedures in this document.
323-1111-090.
end
Fac STS1
STS1 Rx AIS 5
Probable causes
The local equipment is receiving an STS-1 alarm indication signal (AIS) from
the coaxial cable (STS-1 signal source). One of the following conditions
exists:
defective local STS-1 circuit pack
defective local STS-1 BNC I/O circuit pack
loose or defective coaxial cable or connector
signal failure at the far end of the coaxial cable
This alarm, especially when accompanied by OC12 and ESI equipment
alarms, could also be due to an incorrect Application Select state. See chapter
Impact
Action
Step Action
1 Verify that the facility is in service by checking the screen by entering:

facility <sts1> <circuit pack group> <port no.>
where
<circuit pack is g1 to g4
group>
<port no.> is the port number of the alarmed facility (1 to 3)
2 From the local network element user interface, perform a manual switch on
the STS-1 electrical interface circuit pack by entering:
protectn
dtlprot sts1
manual op <circuit pack group>
yes
where
<circuit pack is g1 to g4 and is the STS-1 interface serving the
group> facility in the alarm

continued
Fac STS1
Step Action
3 If the alarm clears, replace the defective STS-1 electrical interface circuit
pack. Refer to Module Replacement Procedures, 323-1111-547, for
replacement instructions. If the problem persists, go to step 4.
protectn
dtlprot sts1
manual re <circuit pack group>
yes
where
<circuit pack is g1 to g4 as determined in step 2
group>
5 Locate the STS-1 port connectors BNC I/O circuit pack allocated to the port
reporting the STS1 Rx AIS. Examine the STS-1 cable connected to the IN
connector of the concerned STS-1 port. Make sure that the correct connector
is used and is well secured at the source and at the STS-1 BNC I/O circuit
pack. If the cable is split or damaged, replace it. If the problem persists, go to
step 6
6 Review the following before continuing the procedure.
CAUTION
Make sure that the proper STS-1 cable is removed.
Removing the wrong cable causes another STS-1
signal to be lost.
Unplug the input STS-1 cable from the STS-1 BNC I/O circuit pack and
connect it to an STS-1 receiver test set. Verify that an STS-1 signal is present
on the cable and that the test set does not detect any errors. If there are no
errors, reconnect the STS-1 cable and go to step 8. Otherwise, go to step 7.
7 If errors were detected at the STS-1 BNC I/O circuit pack (in ), verify the signal
at the source with the STS-1 test set. If there are errors, then the source
generating the STS-1 signal should be repaired. If there are no errors, go to
step 8.
continued
Fac STS1
Step Action
8 Review the following before continuing the procedure.

CAUTION
Make sure that the proper STS-1 BNC I/O circuit pack
is removed. Removing the wrong circuit pack causes
another STS-1 signal to be lost. Replacing the STS-1
BNC I/O circuit pack also causes the loss of the STS-1
signal being sent on the OUT side of the concerned
port.
At this point, the STS-1 electrical interface circuit pack, the STS-1 cable, and
the STS-1 signal source have been verified. If errors are still occurring,
replace the BNC I/O circuit pack associated with this port. Refer to Module
323-1111-090.
end
Fac STS1
STS1 Rx loss of pointer
Probable cause
This alarm is raised when an STS-1 loss of pointer is detected on the incoming
coaxial cable.
The STS-1 pointer is corrupted (equivalent to losing frame). One of the

defective far-end DS1 VT or DS3 STS mapper circuit pack
defective local or far-end STS-1 electrical interface circuit pack
defective far-end OC-3/OC-12 optical interface circuit pack
bad synchronization of the network
Impact
A switch to the protection circuit pack is initiated, resulting in a traffic outage
of 60 ms maximum.
Action
Step Action

alarms
2 Verify if a protection switch of the equipment on which the alarm was detected
clears the alarm.
If the alarm Then
clears replace the circuit pack
3 Verify if a protection switch of the equipment on which the STS-1 originates

at the far end of the coaxial cable clears the alarm.
If the alarm Then
clears replace the circuit pack
4 Verify the synchronization of the network elements at the two end points of
the STS-1 coaxial cable. Ensure that all network elements are synchronized
with a proper source and settings.
end
Fac TGen
Degraded timing reference
Probable cause
The ESI cannot synchronize to the incoming timing reference input signal.
The accuracy of the affected timing reference is lower than the accuracy of the
internal clock. The accuracy of a reference is determined either by the
provisioned value or from the S1 byte in the SONET overhead.
Impact
Action
Step Action
1 Display the provisioning reference screen and verify provisioning.

2 If the provisioning is correct, contact your next level of support or your Nortel
323-1111-090.
end
Fac TGen
Reference forced switch request
Probable cause
A forced switch has been requested for synchronization references.
Impact
Action
No action is required unless you want to release the forced switch request.
Step Action
1 From the network element status screen, display the reference protection
screen by entering:
pr
trefprot
2 Release the forced switch request by entering:
forced re <timing reference>
where
<timing is 1 to 4
reference>
yes
end
Fac TGen
Reference manual switch request
Probable cause
A manual switch has been requested for synchronization references.
Impact
Action
Note: No release is needed because of the 1+1 nature of the ESI protection
scheme. The manual switch request raises an alarm which is cleared soon
after.
end
Fac TGen
Reference switch complete
Probable cause
Synchronization timing has switched from one timing reference to another.
Impact
Action
Note: Check to determine whether the protection switch is the result of a
manual or forced switch request for maintenance purposes or whether the
system automatically switched service to the protection ESI.
Step Action
1 From the network element status screen, display the reference protection
screen by entering:
pr
trefprot
The system displays a list of information about the ESI timing reference.
If there is an asterisk (*) below the Forced or Manual fields, the protection
switch was requested by a craftsperson. No further action is required.
(Manual can have an asterisk flashing beside it when the switch is occurring,
but it is cleared upon completion.)
If there is an asterisk (*) beside the Automatic field, the protection switch was
performed automatically by the system. In this case, go to step 2.
2 Verify the integrity of the timing reference from which the system switched.
end
Fac TGen
Reference switch fail
Probable cause
A requested protection switch from one synchronization reference to another
has failed.
Impact
Action
Step Action
1 The integrity of synchronization references must be verified in order to

provide a valid reference. Follow step 2 through step 4.
2 Verify that there is no loss of signal (LOS) by checking that the cable is not
disconnected or that the signal source is not absent.
3 Ensure that proper framing has been selected on the ESI and that the BITS
source is sending proper framing for the ESI to receive. Both ends should be
checked.
4 Ensure that the wiring is not corrupted. If it is corrupted, a bipolar violation in
excess of 10-8 might arise.
end
Fac TGen
Timing reference interface fail
Probable causes
loss of frame (LOF)
a frequency deviation
alarms) could also be due to an incorrect Application Select state. See
chapter 10, Clearing incorrect Application Select state, for more
information.
Impact
This is a major, service-affecting (M, SA) alarm (if unprotectable).
This is a minor, not service-affecting (m. nsa) alarm (if protectable).
Action
Step Action
1 Verify any alarms against ESI.

2 Clear the alarms according to the appropriate alarm clearing procedures in
this document.
3 If the alarm persists, verify that the ESI facility is in service.
4 Verify that the timing reference input frame format is equivalent to what is
expected by entering:
where
<timing reference> is bitsa or bitsb
query all
If the frame format is Then go to
not as expected step 5
as expected step 6
5 Change the frame format as described in Provisioning and Operations

6 Verify the connection of the external synchronization cable and the external
reference signal.
continued
Fac TGen
Timing reference interface fail (continued)
Step Action
7 If the alarm persists, place the facility out of service (OOS) and back in
service (IS) by entering:
chgstate oos
chgstate is
323-1111-090.
end
6-1
Clearing environment alarms 6-

This chapter describes how to locate and clear Transport Bandwidth Manager
(TBM) environment alarms using the network element user interface.
Note: The service code provided in the impact section of the alarm
generated, the software determines if the alarm is in fact service affecting
and under certain rare circumstances the software displays a different
service code than the one documented. Under these rare circumstances, the
service code provided by the software is the correct service code and the
documented service code should be disregarded.
List of environment alarms

The three following tables list the environment alarms.
Env CE (shelf) alarms
Alarm Page
48V battery A CE supply fail 6-3
48V battery B CE supply fail 6-3
Fan 1 fail 6-4
Fan 2 fail 6-4
Fan 3 fail 6-4
High bay temperature 6-9
High CE shelf temperature 6-10
6-2 Clearing environment alarms
Env Input alarms

Alarm Page
Telemetry input n (see Note) 6-11
Note: Env input alarms have provisionable text. The default text is Telemetry
input n. Changed text appears if these alarms are provisioned. See System
Administration Procedures, 323-1111-302, for procedures for setting parallel
telemetry parameters.
External customer inputs (telemetry inputs)

A set of eleven external inputs is provided with return connection. To activate
the inputs, apply a connection to the input return from an isolated relay contact
or switch. These inputs correspond to external alarms only (for example,
power failure, fire alarm, flood alarm). They are not system alarms (for
example, signal degrade, protection failure, circuit pack failure). Each of these
external customer inputs can be assigned a 40-character string of text to
identify the specific alarms. The alarm class and severity are preset to a default
but can be changed (see Network Surveillance Procedures, 323-1111-510).
The following defaults apply.
Input Alarm text Severity Service

point code
1 AC power fail Minor NSA
2 Low battery Major NSA
3 Reserved for future use Minor NSA
4-11 Telemetry input n Minor NSA
Env REMT alarms

Alarm Page
Env CE
48V battery A CE supply fail
48V battery B CE supply fail
Probable cause
Either the -48V A or B power supply sourcing the shelf has failed. One of the
a tripped breaker
a failed breaker
faulty wiring
Impact
Action
Step Action
1 Verify if there is an active circuit breaker trip alarm on the breaker interface
panel (BIP). A red LED, located to the left or right of the breakers, indicates if
a breaker has been tripped. Reset the breaker that has tripped. If the breaker
had not tripped, or if after resetting the breaker the alarm persists, go to
step 2.
2 Check the breaker for correct operation. If the breaker has failed, replace it.
instructions. If the breaker has not failed, go to step 3.
3 Check the wiring and make any repairs. See Installation Procedures,
323-1111-201.
end
Env CE 60
Fan 1 fail
Fan 2 fail
Fan 3 fail
Fan 4 fail 6
Probable cause
One of the cooling modules in the cooling unit on the main bay (shelf 1 or 2)
is either missing or has failed.
The cable organizer panel (COP) cooling unit in the bottom shelf (shelf 3) is
defective. This condition applies to an enhanced three-shelf bay in which the
bottom shelf (shelf 3) is equipped with a COP cooling unit.
Impact
Note: The ambient shelf temperature may increase.
CAUTION
Clear this alarm as soon as it is raised. Failure to do so may
result in damage to the circuit packs.
Action
Step Action
1 Do the following:
If the alarm is generated by Then go to

shelf 1 or shelf 2 step 2
shelf 3 (minor alarm LED on LCAP is lit) step 8
2 Do the following:
If the red fail LED on the cooling module is Then go to

lit step 3
not lit step 4
3 Replace the defective cooling module. See Module Replacement

Procedures, 323-1111-547. If the alarm persists, go to step 5.
continued
Env CE
Fan 1 fail
Fan 2 fail
Fan 3 fail
Fan 4 fail (continued)
Step Action
Note: To determine which of the three types of fan modules needs to be

replaced, check the serial number on the network element. Cooling shelves
using fan modules NT4K17AA or NT4K17BA have a network element serial
number starting with the letter A. Cooling shelves using fan module
NT4K55AA have a network element serial number starting with letters B to Z.
4 Do the following:
If the cooling module is Then

missing insert the missing module.
If the alarm persists, go to step 7.
not missing go to step 5
5 Clean the air filters, if required. See Routine Maintenance Procedures,

323-1111-546. If the alarm persists, go to step 6.
Note: The TBM cooling unit (NT4K18BA) is not equipped with an air filter.
6 Clean the cooling unit grille, if required. See Routine Maintenance
Procedures, 323-1111-546. If the alarm persists, change the air filter. See
Routine Maintenance Procedures, 323-1111-546. If the alarm continues to
persists, go to step 7.
7 Cooling unit interface cable
a. If the cooling unit interface cable that connects the cooling unit to the
cooling unit interface connector on the side interconnect left circuit pack
(SIL) is not securely connected, reseat the cable. If the alarm persists, go
to step 7b.
b. If the cooling unit interface cable that connects the cooling unit to the
cooling unit interface connector on the SIL circuit pack is damaged,
replace the cable. If the alarm persists, go to step 10.
8 COP cooling unit interface cable
a. If the COP cooling unit interface cable that connects the COP cooling unit
to the cooling unit interface connector on the SIL circuit pack is not
secure, reseat the cable. If the alarm persists, go to step 8b.
b. If the COP cooling unit interface cable that connects the COP cooling unit
to the cooling unit interface connector on the SIL circuit pack is damaged,
9 Replace the COP cooling unit. See Module Replacement Procedures,
continued
Env CE
Fan 1 fail
Fan 2 fail
Fan 3 fail
Fan 4 fail (continued)
Step Action
Library, 323-1111-090.
end
Env CE 60
Multiple fan fail 6
Probable cause
Two or more of the cooling modules in the cooling unit on the main bay (shelf
1 or 2) are either missing or have failed.
The cable organizer panel (COP) cooling unit in the bottom shelf (shelf 3) is
defective. This condition applies to an enhanced three-shelf bay in which the
bottom shelf (shelf 3) is equipped with a COP cooling unit.
Impact
Note: The ambient shelf temperature may increase.
CAUTION
Clear this alarm as soon as it is raised. Failure to do so may
result in damage to the circuit packs.
Action
Step Action
1 Do the following:
If an alarm is generated by Then go to

shelf 1 or shelf 2 step 2
shelf 3 (minor alarm LED on LCAP is lit) step 8
2 Do the following:
If the red fail LED on the cooling module is Then go to

lit step 3
not lit step 4
3 Replace the defective cooling module. See Module Replacement

Procedures, 323-1111-547. If the alarm persists, go to step 5.
continued
Env CE
Multiple fan fail (continued)
Step Action
4 Do the following:
If the cooling module is Then

missing insert the missing module.
If the alarm persists, go to step 7.
not missing go to step 5
5 Clean the air filters, if required. See Routine Maintenance Procedures,

Note: The TBM cooling unit (NT4K18BA) is not equipped with an air filter.
6 Clean the cooling unit grille, if required. See Routine Maintenance
Procedures, 323-1111-546. If the alarm persists, change the air filter. See
Routine Maintenance Procedures, 323-1111-546. If the alarm continues to
persists, go to step 7.
7 Cooling unit interface cable
a. If the cooling unit interface cable that connects the cooling unit to the
cooling unit interface connector on the side interconnect left circuit pack
(SIL) is not securely connected, reseat the cable. If the alarm persists, go
to step 7b.
b. If the cooling unit interface cable that connects the cooling unit to the
cooling unit interface connector on the SIL circuit pack is damaged,
8 COP cooling unit interface cable
a. If the COP cooling unit interface cable that connects the COP cooling unit
to the cooling unit interface connector on the SIL circuit pack is not
secure, reseat the cable. If the alarm persists, go to step 8b.
b. If the COP cooling unit interface cable that connects the COP cooling unit
to the cooling unit interface connector on the SIL circuit pack is damaged,
9 Replace the COP cooling unit. See Module Replacement Procedures,
Library, 323-1111-090.
end
Env CE 60
High bay temperature 6
Probable cause
The fan units are reporting high shelf temperature at the main bay. The
temperature detectors indicate a temperature over 65C (149F). One of the
no power to the cooling unit
a defective fan module
clogged air filters
obstructed entry or exit grille
an excessively high room temperature
Note: This alarm is also reported locally on the MIC faceplate alarm LED
labelled CU.
Impact
This is a critical, not service-affecting (C, nsa) alarm.
Action
Step Action
1 Verify that there is power to the cooling unit.

2 Verify if there is a fan fail alarm. If so, clear it according to the Env CE fan fail
(Fan 1 fail, Fan 2 fail, Fan 3 fail, Fan 4 fail, Multiple fan fail) alarm clearing
procedure in this chapter.
3 If the alarm persists, change the air filter located at the bottom of the bay by
following the instructions in Routine Maintenance Procedures, 323-1111-546.
4 Ensure the entry grille openings at the bottom of the bay are clear of
obstructions.
5 Clean the cooling unit grille, as required. See Routine Maintenance
Procedures, 323-1111-546, for cleaning instructions.
6 Ensure the ambient temperature remains below (65C [149F]).
7 You might be having problems with certain circuit packs generating too much
heat. If so, contact your next level of support or your Nortel Networks support
group. See About the OC-3/OC-12 NETBM Library, 323-1111-090.
end
Env CE 60
High CE shelf temperature 6
Probable cause
The maintenance interface controller (MIC) circuit pack temperature sensor is
reporting a high air temperature in the common equipment shelf. The
temperature detectors indicate a temperature over 70C (158F) has been
reported and has not yet dropped below 65C (149F). One of the following
conditions exists:
no power to the cooling unit
a defective fan module
clogged air filters
an excessively high room temperature
an obstructed grille on the fan module
Note: This alarm is currently reported only locally on the MIC circuit pack
faceplate alarm LED labelled TEMP.
Impact
This is a critical, not service-affecting (C, nsa) alarm.
Action
Step Action
1 Verify that there is power to the cooling unit.

2 Verify if there is a fan fail alarm. If so, clear it according to the Env CE fan fail
(Fan 1 fail, Fan 2 fail, Fan 3 fail, Fan 4 fail, Multiple fan fail) alarm clearing
procedure in this chapter.
3 Change the air filter located directly above the cooling unit, if required. See
the procedure for changing an air filter in Routine Maintenance Procedures,
323-1111-546.
Note: The TransportNode (TN) cooling unit (NT4K18BA ) is not equipped
with an air filter.
4 Ensure the ambient temperature remains below (65C [149F]).
5 Ensure the grille openings to the fan module are clear of obstructions.
6 You might be having problems with certain circuit packs generating too much
heat. If so, contact your next level of support or your Nortel Networks support
group. See About the OC-3/OC-12 NETBM Library, 323-1111-090.
end
Env Input
Telemetry input n 6
Probable cause
One of 11 provisionable external parallel telemetry inputs has been activated
by a condition that meets the user-provisioned criteria for an alarm, that is, any
external alarm such as a door open, power failure, fire, or other alarms. For
information on the parallel telemetry features see Alarms and Surveillance
Impact
The severity of the 11 telemetry alarms is provisionable. The impact varies
according to the provisioned value.
Action
Because the 11 telemetry inputs are user-provisionable, there is no single
procedure to clear this alarm. The procedure varies depending on the
provisioning of each input. Use the following procedure to obtain more details
on this alarm.
Step Action
1 Check with your system administrator to determine how the alarm was
provisioned, for example, door open, high temperature, or a generator
problem.
2 Clear the active condition (for example, close the door) using the appropriate
procedures.
3 From any screen, display the alarm screen by entering:
alarms
4 Display the detailed alarm screen for the telemetry input alarm:
dtlalms <alarm #>
where
<alarm #> is the number of the telemetry alarm that appears under the
heading Alm on the alarm screen
5 Display the telemetry input alarm parameters by entering:
port
The screen displays the details of the telemetry alarm.
6 Proceed according to the severity and details of the alarm.
continued
Env Input
Telemetry input n (continued)
Step Action
7 If the alarm persists and you have checked all the external wiring and
contacts, replace the MIC circuit pack. See Module Replacement
end
Env Remt
Remote environmental #1 6
Probable cause
An environmental alarm condition exists on a remote S/DMS TransportNode
Express node connected to the TBM through OC-3 tributaries.
Impact
Action
Step Action
1 Log in to the remote node indicated by the Alarm Details. Determine the
end
Env Remt 60
Probable cause
Impact
Action
Step Action
end
Env Remt 60
Probable cause
Impact
Action
Step Action
end
Env Remt 60
Probable cause
An environmental alarm condition exists on a remote node of a S/DMS
TransportNode Express system connected to the TBM through OC-3
tributaries.
Impact
Action
Step Action
end
7-1
Interpreting circuit pack LEDs and

lamps 7-
This chapter provides information on the probable cause and meaning of each
circuit pack trouble-condition LED. See Chapter 4, Clearing equipment
alarms, for procedures on how to clear alarms related to circuit packs.
An active green LED indicates that the circuit pack is in service and should not
be removed. Under certain conditions, both the red fail and green active LEDs
light up on the same circuit pack. This condition can indicate a failure on the
circuit pack.
In some cases, such as the case of intercard failures in a ring (communications

failures between the G1 and G2/G1S OC-12/STS-12 interface circuit packs or
between a OC-12/STS-12 interface circuit pack and a ring loopback circuit
pack) both the green and red LEDs that are lit might either indicate a failure of
the circuit pack with the red LED or of the circuit pack with which it is
communicating.
When both green and red LEDs are lit on a circuit pack, check for alarms and
troubleshoot accordingly.
Shelf lamps and circuit pack LEDs can be tested by performing a shelf lamp
test as described in Provisioning and Operations Procedures, 323-1111-310.
This test lights all the lamps and LEDs for 30 seconds. If at any time during
system operation all the shelf lamps light and stay lit, this can indicate the
failure of the shelf processor or maintenance interface controller (MIC) circuit
pack.
You can find procedures for clearing equipment, facility, and environment
alarms, in this document.
7-2 Interpreting circuit pack LEDs and lamps
Table 7-1
Summary of circuit pack LEDs and lamps
Circuit pack Label Color Controlled by Information
Breaker interface panel (BIP) Power White Hardware page 7-4

(NT7E56)
Critical Red Hardware/software
Major Red Hardware/software
Minor Yellow Hardware
Circuit breaker trip Red Hardware
Cooling module Fail Red Hardware page 7-4

(NT4K17)
DS1 VT mapper circuit pack Fail Red Software page 7-5
(NT7E04)
Active Green Software
DS3 STS mapper circuit pack Fail Red Software page 7-5
(NT7E08)
LOS 1, LOS 2, or LOS3 Yellow Hardware
Protection switcher circuit Fail Red Software page 7-13

pack
(NT4K60)
External synchronization Fail Red Hardware/software page 7-6

interface (ESI) unit
(NT7E27) Active Green Software
Maintenance interface Fail Red Hardware/software page 7-7

controller (MIC) circuit pack
(NT4K53) LoopBk Yellow Software
CU Fail Yellow Software
Temp Red Software
TestFail Red Software
TestRun Yellow Software
LckOut Yellow Software
Init Yellow Software

continued-

Summary of circuit pack LEDs and lamps
Circuit pack Label Color Controlled by Information

Optical Interface circuit pack Fail Red Software page 7-9
OC-3 (NT7E01)
OC-12 (NT7E02) LOS Yellow Hardware
OC-12 (NT7E05) Active Green Hardware/software
OC-12 ring loopback circuit Fail Red Hardware/software page 7-10

pack
(NT7E35) Active Green Hardware/software
OPC module E LAN Fail Yellow Software page 7-11

(NT7E24)
CNet Fail Yellow Software
Fail Red Hardware/software
Tape drive hardware Amber Hardware/software

status (see Note)
Tape drive activity Green Hardware/software

status (see Note)
Cartridge drive activity Green Hardware/software

status (see Note) Red
Processor (Proc) circuit pack Fail Red Software page 7-13

(NT4K52)
STS-1 electrical interface Fail Red Software page 7-14

circuit pack
(NT7E09) Active Green Software
LOS 1, LOS 2, or LOS Yellow Hardware

3
STS-12 electrical interface Fail Red Software page 7-15

circuit pack
(NT7E33) LOS Yellow Hardware
Active Green Hardware
Note: This identification is not labelled on the unit.
Breaker interface panel (NT7E56)

Power lamp (white)
Indicates 48 V power source is available on the breaker interface panel (BIP).
Critical lamp (red)

Indicates a critical alarm on one of the shelves in the bay.
Major lamp (red)

Indicates a major alarm on one of the shelves in the bay.
Minor lamp (yellow)

Indicates a minor alarm on one of the shelves in the bay.
The minor alarm lamp also lights up if any of the BIP lamps have failed. To
test the lamps, press the ACO/LT (green) button. All the lamps on the BIP
should light up. Replace those that do not.
Circuit breaker trip LED (red)

Indicates if one or more of the BIP breakers have tripped. To reset the breaker,
remove the BIP cover and push down the open breaker. A description of the
function of each of these breakers can be found in System Description,
323-1111-100.
Cooling module (NT4K17)

Fail LED (red)
Probable cause
The fan has failed.
Impact
The remaining functioning fans compensate for the failed fan. However, the
fan must be replaced as soon as possible. If all the fans fail, the circuit packs
in the shelf can overheat and be damaged.
DS1 VT mapper circuit pack (NT7E04)

Fail LED (red)
Probable cause
Faulty circuit pack.
Impact
If the failure occurs on the active DS1 VT mapper circuit pack, the incoming
and outgoing DS1 signals are rerouted to the protection DS1 VT mapper
provided that:
the protection DS1 VT mapper circuit pack was provisioned in the network
element
the DS1 VT mapper circuit pack in the protection slot is not already in use
by another circuit pack of equal or higher priority
During rerouting, only the affected DS1 traffic is hit for a period not exceeding
60 ms.
Note: If a protection DS1 VT mapper circuit pack is not available on the

network element, the DS1 traffic might be lost.
DS3 STS mapper circuit pack (NT7E08)

Fail LED (red)
Probable cause
A circuit pack component has failed.
Impact
If the failure occurs on the active DS3 STS mapper circuit pack, the incoming
and outgoing DS3 signals are rerouted to the protection DS3 STS mapper
provided that:
the protection DS3 STS mapper circuit pack is provisioned in the network
element
the DS3 STS mapper circuit pack in the protection slot is not already in use
by another circuit pack of equal or higher priority
During rerouting, only the affected DS3 traffic is hit for a period not exceeding
60 ms.
Note 1: If a protection DS3 STS mapper circuit pack is not available on

the network element, the DS3 traffic might be lost.
Note 2: If the shelf contains at least one NT7E08BA mapper, then it is

required that the protection mapper be an NT7E08BA mapper in order to
prevent loss of enhanced functionality.
If both the Fail and Active LEDs are lit on a mapper, use the network element
user interface to access the DS3 Protection Detail screen to check whether the
mapper is protected. If it is protected, replace the circuit pack. If it is not
protected, operate a manual switch on the suspect mapper, replace the mapper,
then release the manual switch.
LOS LED (yellow)

Probable cause
The following are the probable causes of a yellow LOS LED on a DS3 STS
mapper:
faulty DS3 cable
faulty BNC I/O circuit pack
faulty DS3 source
Impact
The DS3 signal being added to the fiber is lost.
Note: In the event that both working and protection optical interfaces on a
shelf fail, the signal bridge between the working and protection DS3
mappers is dropped. This results in the activation of all three LOS LEDs
on the protection mapper.
External synchronization interface (ESI) unit (NT7E27)

Fail LED (red)
Probable cause
Some circuit pack component failed.
Impact
If in duplex mode, synchronization is provided through the other ESI unit (G1
or G2).
If in simplex mode or both ESI units fail, the optics are put into freerun. This
causes a traffic hit. When this occurs, either replace the ESI unit or units
immediately, or remove the functional ESI unit at the other end from the shelf.
Maintenance interface controller (MIC) circuit pack (NT4K53)

Fail LED (red)
Probable cause
The following are the probable causes of a red Fail LED on the MIC circuit
pack:
the nonvolatile RAM on the MIC circuit pack contains configuration
information different from the configuration information retained by the
Proc circuit pack
a faulty MIC circuit pack
a faulty Proc circuit pack
Proc circuit pack rebooting or initializing
Impact
The tributary protection switching is controlled by the MIC circuit pack and
by the Proc circuit pack (NT4K52). If a DS1, DS3, or STS-1 circuit pack fails
while the red LED on the MIC circuit pack is ON, the live traffic cannot switch
to the protection circuit pack. Furthermore, no OAM&P functions can be
carried out until you replace the MIC circuit pack.
LoopBk LED (yellow)

Probable cause
This LED informs you that a DS3, DS1, or STS-1 loopback is active on at least
one of the DS1, DS3, or STS-1 ports.
Impact
This LED lights up only if a loopback is intentionally activated. See
CU fail LED (red)

This LED is currently not used.
Temp LED (red)

Probable cause
The network element is operating outside the specified temperature range (that
is, an increase in the ambient temperature), or one or more fans have failed. If
the problem is persistent, the temperature sensor on the MIC circuit pack may
have failed.
Impact
An increase in the shelf temperature will cause the fans to run at a higher speed
to try to maintain the shelf temperature within the specified range. If the shelf
temperature is outside the specified range, some of the network element circuit
packs may fail. This can result in the loss of OC-3/OC-12, DS1, DS3, or STS-1
services.
If a fan has failed, the remaining functioning fans will compensate for the
failed fan. The fan must be replaced as soon as possible. If all the fans fail, the
circuit packs may overheat and be damaged.
If the temperature sensor on the MIC circuit pack fails, the fans will run at a
higher speed but this will not affect the normal operation of the network
element.
TestFail LED (red)

Probable cause
The protection switching exerciser detected a failure. The failure can be caused
by a missing protection DS3 STS mapper (NT7E08), DS1 VT mapper
(NT7E04), or STS-1 electrical interface (NT7E09), by a faulty protection
switcher (NT4K60), or by failure of the switching mechanism in an
OC-3/OC-12 optical interface.
Impact
If a DS3 STS-1 mapper, DS1 VT mapper, or STS-1 electrical interface fails,
the switching of the traffic to the protection DS3 STS-1 mapper, DS1 VT
mapper, or STS-1 electrical interface might fail. If an OC-3/OC-12 optical
interface fails, or an optical line fails, traffic switching to the standby optical
interface might fail. Check the EQP logs to determine which component of the
exerciser failed.
TestRun LED (yellow)

Probable cause
This LED lights up when the protection switching exerciser is running and is
extinguished at the end of the exercise.
Impact
None.
LckOut LED (yellow)

Probable cause
This LED lights up when the protection on one of the circuit packs is locked
out.
Impact
Under normal operating conditions, no lockout should be present on any of the
circuit packs (DS3, STS, or DS1 VT mappers; STS-1 electrical interface; or
OC-3, OC-12, or STS-12 interfaces).
Init LED (yellow)

Probable cause
This LED lights up when the processor circuit pack reloads software.
Impact
None of the OAM&P functions (including the tributary protection switching)
can be done on the network element while this lamp is lit.
Note: The transport protection switching is not affected.
OC-3 (NT7E01) or OC-12 (NT7E02 or NT7E05) optical interface circuit

pack
Fail LED (red)
Probable cause
The following are the probable causes of a red Fail LED on an optical interface
circuit pack:
the laser failed or a circuit pack component failed
parity errors were detected on the buses between tributary circuit packs and
the OC-12 optical circuit pack
Impact
Upon detection of the failure, a high-speed switch occurs.
LOS LED (yellow)

Probable cause
The following are the probable causes of a yellow LOS LED on an optical
interface circuit pack:
no optical signal is present at the optical interface (for example, due to a
fiber cut or transmitter failure
a low received optical power
a dirty connector of the optical interface
a malfunctioning the mini-variable optical attenuator (mVOA)
a damaged the fiber optics patchcord
Impact
Upon detection of the failure, a high-speed switch occurs and causes a traffic
hit of no more than 60 ms.
Note: When this interface circuit pack is installed in a protected transport

configuration, if the facility of one of the circuit packs that comprise the
protection pair is placed out of service, the LOS LED on both circuit packs
is disabled, and cannot indicate a loss of signal if one occurs. However, the
facility Rx loss of signal alarm would still be raised.
OC-12 ring loopback circuit pack (NT7E35)

Fail LED (red)
Probable cause
An active red LED generally indicates an intercard control link failure or a
faulty circuit pack.
Impact
A faulty OC-12 ring loopback circuit pack must be taken out of service before
its removal, at which time both the red and green LEDs are turned off.
Active LED (green)

An active green LED indicates that the circuit pack is in service and should not
be removed.
Impact
A green LED on indicates only that the circuit pack is in service: it does not
indicate that the circuit pack is without fault. A faulty OC-12 ring loopback
circuit pack must be taken out of service before removing it.
OPC module (NT7E24)

E LAN fail LED (yellow)
Probable cause
A problem with the Ethernet LAN such as a loose connection, a faulty cable,
or a device powered off can cause this LED to illuminate. Faults with the
Ethernet LAN are only detected when the OPC is attempting to use the
connection.
If the Ethernet LAN is not being used and has been provisioned, this LED
lights up. See System Administration Procedures, 323-1111-302, to
deprovision the Ethernet LAN.
Impact
None, if the Ethernet is not in use. If the Ethernet LAN is in use and this lamp
is lit, the OPC can not communicate with the other elements connected to the
same Ethernet LAN.
CNet fail LED (yellow)

Probable cause
A component that ensures the communication over the CNet has failed.
Impact
If the subnetwork is provisioned with a backup OPC, the backup OPC
becomes active. If no backup OPC is available, the network element to OPC
communication is lost. If any of the network elements reboot, no software load
can be sent.
Active LED (green)

Probable cause
The OPC is functioning properly. This LED should be illuminated on both the
primary and the backup OPC. If this LED is not illuminated:
the power supply to the OPC module failed
the OPC is not properly inserted
the OPC is booting
Impact
The unit should not be removed when this LED is lit. This LED indicates that
the OPC is functioning.
Fail LED (red)

Probable cause
The following are the probable causes of a red Fail LED on the OPC:
the OPC failed
this LED can also light up in the event of a transient software problem
Impact
When this LED lights up, a reboot of the OPC module is triggered. In the case
of a transient software problem, the unit should be operational after the reboot,
and the LED should extinguish after a few minutes.
If the problem is a hardware failure, the LED remains illuminated. If the

network is provisioned with a backup OPC, the backup OPC becomes active.
Otherwise, the network element-to-OPC communication is lost. If any of the
network elements reboot, no software load can be sent.
Tape drive hardware status LED (amber)

Probable cause
The following are the probable causes of a amber Tape drive hardware status
LED on the OPC:
LED extinguished: no tape activity.
LED illuminated: tape drive is reading or writing a tape without problems.
LED flashing rapidly: hardware within tape drive has failed.
Note: The LED is only visible when the tape door is open.
Tape drive activity status LED (green)

Probable cause
The following are the probable causes of a green Tape drive activity status
LED on the OPC:
LED extinguished: No tape activity; no tape in drive.
LED illuminated: A tape is inserted in the drive.
LED flashing slowly (in sync with Amber LED): The drive is attempting
to play a prerecorded audio tape instead of the data tape.
LED flashing slowly: A tape is in the drive and the number of transient
errors exceeded the predefined error threshold. This is a warning indication
that tape reading and writing capability is deteriorating.
LED flashing rapidly: The drive cannot read/write a tape. This indicates the
current operation failed.
Cartridge drive status LED

Probable cause
LED extinguished: No cartridge in the cartridge drive.
LED illuminated green: A cartridge is in the cartridge drive.
LED illuminated red: Indicates the cartridge is in use
Processor (Proc) circuit pack (NT4K52)

Fail LED (red)
Probable cause
The following are the probable causes of a red Fail LED on the Proc circuit
pack:
a faulty processor circuit pack
Proc circuit pack rebooting or initializing
a faulty maintenance interface controller (MIC) circuit pack
an unsuccessful software download
Impact
The low-speed protection switching is controlled by both the maintenance
interface circuit pack and by the processor circuit pack. If a DS1, DS3, or
STS-1 circuit pack fails while the red LED on the processor circuit pack is ON,
the live traffic cannot switch to the protection mapper. No OAM&P functions
(serial telemetry, user interface features, DS1/DS3/STS-1 protection
switching) can be carried out until the processor is restarted, rebooted, or
replaced.
Protection switcher (NT4K60)

Fail LED (red)
Probable cause
A faulty circuit pack.
Impact
If the Fail LED on this circuit pack is ON and a DS3 STS mapper circuit pack
fails, the affected DS3 traffic might not be rerouted to the protection DS3 STS
mapper circuit pack and some of that traffic might be lost.
STS-1 electrical interface circuit pack (NT7E09)

Fail LED (red)
Probable cause
Some circuit pack component has failed.
Impact
If the failure occurs on the active STS-1 electrical interface circuit pack, the
incoming and outgoing STS-1 signals are rerouted to the protection STS-1
electrical interface circuit pack provided that:
the protection STS-1 electrical interface circuit pack was provisioned in
the network element
the STS-1 electrical interface circuit pack in the protection slot is not
already in use by another circuit pack of equal or higher priority
During rerouting, only the affected STS-1 traffic is hit for a period not
exceeding 60 ms.
Note: If a protection STS-1 electrical interface circuit pack is not available

on the network element, the STS-1 traffic might be lost.
If both the Fail and Active LEDs are lit on an STS-1 electrical interface circuit
pack, use the network element user interface to access the STS-1 Protection
Detail screen to check whether the interface is protected. If it is, replace the
circuit pack. If it is not protected, operate a manual switch on the suspect
interface, replace the interface, then release the manual switch.
LOS LEDs (yellow)

Probable cause
The following are the probable causes of a red Fail LED on an STS-1 electrical
interface circuit pack:
a faulty STS-1 cable
a faulty BNC I/O circuit pack
a faulty STS-1 source
Impact
The STS-1 signal being added on the fiber is lost.
Note: In the event that both working and protection optical interfaces on a
shelf fail, the signal bridge between the working and protection STS-1
electrical interface circuit packs is dropped. This results in the actuation of
all three LOS LEDs on the protection mapper.
STS-12 electrical interface circuit pack (NT7E33)

Fail LED (red)
Probable cause
The following are the probable causes of a red Fail LED on an STS-12
electrical interface circuit pack:
a circuit pack component failed
parity errors have been detected on the bus between a tributary circuit pack
and an STS-12 circuit pack
Impact
Upon detection of the failure, a high-speed switch occurs.
LOS LED (yellow)

Probable cause
The following are the probable causes of a yellow LOS LED on an STS-12
electrical interface circuit pack:
no signal is present at the interface (for example, due to a coaxial cable cut
or transmitter failure
low received power
a dirty connector of the interface
a damaged coax cable
Impact
Upon detection of the failure, a high-speed switch occurs and causes a traffic
hit of no more than 60 ms.
Note: When this interface circuit pack is installed in a protected transport

configuration, if the facility of one of the circuit packs which make up the
protection pair is placed out of service, the LOS LED on both circuit packs
is disabled, and cannot indicate a loss of signal if one occurs. However, the
facility Rx loss of signal alarm would remain raised.
8-1
Troubleshooting the breaker interface

panel (BIP) 8-
The BIP is mounted at the top of an OC-12 bay. See Figure 8-1 for the internal
layout and Figure 8-3 for a functional block diagram. The BIP provides
48 V dc power to all equipment on a bay.
The BIP power distribution block is connected to two 48 V dc battery power

and battery return (RET) pairs (labeled A and B) from two local battery
stations. The two ground returns (RETA and RETB) are isolated from the bay
ground. On the NT7E56AB/BA BIP, a battery filter is provided between the
power distribution block and the main breakers on the panel, and is protected
by the battery filter breaker. On the NT7E56CA BIP, the battery filter is on the
logic card and is protected by BIPA and BIPB fuses.
The battery feeds are monitored separately by the internal BIP circuitry and if
one should fail or drop below 38 V dc, a minor alarm is raised on the BIP.
Each of the power supplies feeds a separate set of four 15-A circuit breakers
which in turn feed the shelves mounted in the bay. The TBM shelf is a single
unit. A BIP has sufficient breakers to provide an A-side and a B-side feed to
three TBM shelves and one cooling unit. The same TBM shelf is used for
terminal, ADM, and regenerator applications.
If one or more breakers trip, the circuit breaker trip lamp is lit on the BIP and
a minor alarm is raised. If both breakers trip, a critical alarm is raised.
Because all bays do not have a full complement of shelves, the shelf alarms are
provisionable using the DIP switches on the right cover of the BIP. See Figure
8-4 to see how these switches are set. If you set up a TBM shelf on the bay, it
must have one A power feed and one B power feed. It has one BIP alarm
connector.
8-2 Troubleshooting the breaker interface panel (BIP)
The office alarms wire-wrap board is located on the right-side hinged cover
and provides relay contacts for both visible and audible alarms, as well as the
alarm cut-off (ACO) pushbutton. On the NT7E56AB/BA BIP, four auxiliary
2-A breakers are also provided behind this cover. These are connected directly
to the battery terminals. Each is fed by way of a diode to both the A- and B-side
batteries. On the NT7E56CA BIP, there are four GMT fuses provided in the
center of the unit. BIPA and OEMA/MDU fuses are connected directly to
Battery A. BIPB and OEMB fuses are connected directly to Battery B.
These breakers on the NT7E56AB/BA BIP are used to feed (from left to right)
the following:
BIP control circuits
not used
modem, if required
indicator lamps
These breakers on the NT7E56CA BIP are used to feed (from top to bottom)
the following:
BIPA - BIP control circuits and Battery Filter A
BIPB - BIP control circuits and Battery Filter B
OEMA/MDU - customer OEM equipment
OEMB - customer OEM equipment
The BIP can be equipped with an optional plug-in modem (2400 baud
maximum) to connect any of the network element shelves on the bay to a
remote terminal.
The front panel of the BIP is equipped with the following lamps for bay alarm
and status indications:
bay critical alarm (red)
bay major alarm (red)
bay minor alarm (yellow)
circuit breaker trip alarm (red)
BIP power lamp (white)
ACO lamp (green)
The following sections in this chapter provide troubleshooting instructions for
these lamps and other indications on the BIP. It also includes a procedure for
troubleshooting the BIP modem.
Figure 8-1
Breaker interface panelinternal view of components, NT7E56AB/BA
FW-0147
To office battery Power terminal

distribution blocks
Battery filter breaker
Circuit breaker (not available
trip LED (red) on NT7E56AA)
A- Modem
A+
(optional)
B-
B+
Circuit breakers
Configuration
DIP switches
BIP, maintenance
terminal, modem,
and lamp circuit
breakers
To shelf
ACO/lamp test power terminal
pushbutton blocks
Power (white)
critical (red) Lamps
major (red)
minor (yellow)
Figure 8-2
Breaker interface panel, NT7E56CA
FW-0147(CA)
Rear "battery connections"

Left hinged
panel removes
to expose "battery
connections"
Modem pack
Teladapt connector
Breakers A1-A4
Breakers B1-B4
BIPA
Modem connector (9 pin)
BIPB Shelf alarms connector
GMT fuses
OEMA Modem fuse Lamps (LEDs)
Power (white)
Critical (red)
OEMB ACO/lamp Major (red)
test pushbutton Minor (yellow)
Logic pack
C.O. alarms wirewrap panel
mounting screws
Circuit-breaker "TRIP" LED (red)
DIP switch SW1
Figure 8-3
BIP functional block diagram
FW-0423(CA)
NT7E56AB/BA
Power distribution block 4
4 Power to
2 Battery Auxilliary 4 all shelves
Battery A feeds A and B
filter circuit circuit 4
2
Battery B feeds breakers breakers 2
Breaker Not used
2
Power to MODEM
1 8 2 2
Alarm Block
ACO Detection Lamps

25 Alarm signals
Drive to the office
Alarm signals 25
Controller and audible and
from shelves PUPS
25 relays visible alarm
NT7E56CA
Battery A Power distribution block

2 4
Front feeds 4
2 A and B circuit breakers Power to
Rear feeds 4 all shelves
Battery B "GMT" style fuses 4
2 2
Front feeds BIPA BIPB OEMA OEM
OEMA/MDU
2 /MDU 15
Rear feeds 2
OEMB
A B
Alarm Block
Alarm signals to the
Battery Logic Drive and office audible and
9 filters and ACO relays visible alarm
Alarm signals 9 25
from shelves 9 Optional MODEM output
Controller Alarm MODEM
lamps teledapt
Fuse
MODEM input
from shelf
Legend:
2 9
= 2-wire cable =9-wire cable
4 25
= 4-wire cable = 25-wire cable
8
=8-wire cable
Figure 8-4
Equipment provisioning switches
FW-2290(CA)
SW1
0 1
Shelf unequipped 2 Shelf equipped
Audible critical alarm 4 Audible critical alarm

ENABLED DISABLED
SW2
0 1
MODEM unequipped 1 MODEM equipped
Not used 2 Not used
Note 1: DIP switches are shown in the equipped mode.
Note 2: On the NT7E56CA BIP, the modem is equipped automatically

upon connection, and therefore SW2 is not required.
Switch 1
Section Setting
1 If shelf position #1 is equipped, set to 1, otherwise set to 0.

4 If audible critical alarm is to be transmitted to central office, set to 0, otherwise

set to 1.
Switch 2
Section Setting
1 If modem is equipped, set to 1.
2 Not used.
Note: The printed circuit board marking matrix provides a legend to determine the setting of these switches.
BIP troubleshooting
Bay audible alarm
Probable cause
The bay audible alarm is raised under the following conditions:
a minor, major or critical alarm has been generated by one of the shelves
or by the BIP circuitry itself
a critical alarm is raised on any shelf in the bay, and the shelf DIP switch
is set to the shelf equipped state, see Figure 8-4
a shelf alarm interconnect cable is removed from the BIP connector,
(connector J1, J2, or J3) when the DIP switch is set to the shelf equipped
state
loss of power to the BIP
the office alarm relays fail
Impact
In all cases, log in to the OPC or the shelves in the bay and determine the cause
of the alarm.
If no alarm is active on any shelf, the alarm is due to a disconnected

interconnect cable, or DIP switches in the wrong state or an alarm has been
generated by the BIP due to circuit breaker trip, blown fuse, low battery
voltage or BIP circuit failure.
If the problem is a failure of the office alarm relays, replace the printed circuit
board (located behind the right door of the BIP) that controls all the BIP
functions.
If you are replacing a lamp or if there is a lamp failure, a minor alarm is raised
that generates the audible alarm. On the NT7E56CA, the lamps are LEDs
which can only be replaced by replacing the entire DISPLAY CARD
NT7E5662.
end
BIP troubleshooting
ACO pushbutton indicator lit
Probable cause
An alarm is present on the bay, but the ACO (alarm cut-off) button was pressed
to silence the bay audible alarm. The ACO lamp lights up until all alarms that
were present at the time the button was pressed are reset. In the event of a new
alarm on the bay, the audible alarm restarts and the ACO lamp extinguishes.
If the ACO pushbutton is pressed when the ACO light is extinguished, the
pushbutton lamp lights up in conjunction with all other lamps on the BIP as
part of the lamptest feature.
Impact
In all cases, if you do not know why the lamp is lit, log in to the OPC or the
shelves in the bay and determine the cause of the alarm or alarms.
See the Bay audible alarm section in this chapter for troubleshooting.
end
BIP troubleshooting
Power (white) indicator lit
Probable cause
Both lamps lit is the normal condition. When this indicator is lit, at least one
-48 Vdc power source is available on the BIP. If this indicator is not lit, it
indicates one of the following:
both lamps failed
both battery feeds to the bay failed
both BIPA and BIPB fuses blown on NT7E56CA
Impact
On NT7E56AB/BA
If any other lamp on the bay is lit when both power lamps are extinguished,
then both power indicator lamps failed. (All lamps on the bay have the same
power supply as these lamps.) Obtain some new lamps and replace them as
soon as possible. It is safe to replace the lamps without isolating power supply
to the bay.
If you press the ACO pushbutton and no lamps light on the BIP, both battery
feeds have failed. There could be a major traffic failure in the network.
Tell your system administrator immediately, and determine the cause of the
battery failure. Restore power as quickly as possible.
On NT7E56CA
If any other lamp on the bay is lit when both rows of power LEDs are
extinguished, then either both rows of LEDs have a failed LED, or both BIPA
and BIPB fuses are blown. Check fuses and replace if blown. If fuses were
functional, replace DISPLAY CARD NT7E5662.
If you press the ACO pushbutton and no lamps light on the BIP, then either one
of the circuit packs NT7E5662 or NT7E5664 has failed, or both battery feeds
have failed.
There could be a major traffic failure in the network.
If there is a battery failure, contact your system administrator immediately and

restore power as quickly as possible.
end
BIP troubleshooting
Critical (red) alarm indicator lit
Probable cause
The bay critical lamp is lit under the following conditions:
a critical alarm is raised on any shelf in the bay
both breakers related to one shelf position are tripped or incorrectly
positioned
failure of the office alarm relays
the ACO lamp test pushbutton is pressed on the BIP
an electrostatic discharge (ESD) to the BIP has caused a false critical alarm
latch up
Impact
In all cases, log in to the OPC and determine the cause of the alarm by
examining the alarm history for the shelves in this bay.
If the problem is a failure of the office alarm relays, replace the printed circuit
board (located behind the right door of the BIP) that controls all the BIP
functions.
If no problems are shown by the OPC controlling this bay, then the alarm is
due to tripped or incorrectly optioned BIP breakers or an excessive ESD to the
NT7E56CA BIP.
If the BIP breakers are correctly optioned, and not tripped, follow this
procedure to clear a false critical alarm latch up on the NT7E56CA BIP.
Action
Step Action
1 Disable the office alarms by positioning the options dip switch S1-4 in the right
(disabled) position.
2 Remove both BIPA and BIPB fuses from behind the right door. This will not
affect power to the shelves, but it will disconnect the battery filters.
3 Wait one minute, then reinsert the two fuses. A minor alarm will continue for
five seconds.
4 Position switch S1-4 in the left (enabled) position. The critical lamp will be
extinguished.
5 Close the right door and replace the BIP cover.
end
BIP troubleshooting
Major (red) alarm indicator lit
Probable cause
The bay major alarm indicator is lit under the following conditions:
a major alarm is raised on any shelf in the bay, and the shelf DIP switch is
set to the shelf equipped state. See Figure 8-4.
a shelf alarm interconnect cable is removed from the BIP connector,
(connector J1, J2, or J3) when the DIP switch is set to the shelf equipped
state
the maintenance interface controller (MIC) circuit pack or processor (Proc)
circuit pack is removed from any shelf on the bay
Impact
In all cases, log in to the OPC and determine the cause of the alarm by
examining the alarm history for the shelves in this bay.
end
BIP troubleshooting
Minor (yellow) indicator lit
Probable cause
The bay minor alarm indicator is lit under the following conditions:
a minor alarm is raised on any shelf in the bay
any one breaker to a shelf is tripped, see Circuit breaker trip LED (red) lit
any of the BIP lamps or LEDs are burned out
the modem breaker or fuse trips, and the DIP switch is set to the equipped
state
the Battery Filter breaker is tripped
one of BIPA, OEMA/MDU, OEMB, or modem fuses is blown
Impact
Press the ACO pushbutton. All the lamps on the BIP should light. If any do not
light, obtain some new lamps and replace them as soon as possible. It is safe
to replace the lamps without isolating power supply to the bay.
On the NT7E56CA BIP, the LEDs can only be replaced by replacing the
DISPLAY CARD NT7E5662. It is safe to replace this card while BIPA and
BIPB fuses are removed.
If the indicator remains lit, log in to the OPC and determine the cause of the
alarm by examining the alarm history for the shelves in this bay.
end
BIP troubleshooting
Circuit breaker trip LED (red) lit
Probable cause
One or more of the BIP (15 A or 2A) breakers tripped, or a fuse is blown, or
the breaker labelled Breaker Filter is in the off position (see Figure 8-1 on
page 8-3 for the position of this breaker).
Impact
Check that all breakers on the panel are in the correct state.
On the NT7E56CA BIP, check that GMT fuses are not blown.
Normally, the shelves in the bay are connected from left to right on each set of
breakers. That is, shelf 1 is connected to breaker A1 and B1, FANS shelf to
breakers A2 and B2, shelf 2 to breakers A3 and B3, and shelf 3 to breakers A4
and B4.
Ensure breakers are optioned properly for their normal operation state.
On the NT7E56AB/BA BIP, the Battery Filter Breaker should be in the On
position.
If any 15-A breaker is tripped, press the On or 1 side of the rocker switch until
you hear the breaker click. If the breaker immediately retrips, do not reset it
there is a permanent short circuit in the BIP or on the shelf that is being fed
from that breaker.
On the NT7E56AB/BA BIP, if a 2-A breaker is tripped, press down the plunger
to reset the breaker. This is found on the right-side behind cover of the BIP.
On the NT7E56CA BIP, check that GMT fuses (four in the center of the BIP
plus the additional modem), and replace if one is blown.
In general, the breakers do not trip unless there has been a major physical
interference with the shelf. This might be caused by any of the following:
a major earthquake
Note: Bays are tested for zone 4 protection; but, if they are installed
incorrectly, a short can occur in the power feed circuits
a bay is hit with vehicle or other bay-moving equipment

a craftsperson maintaining the shelf or BIP inadvertently short-circuits the
power feeds to the shelf
a battery feed has been disrupted resulting in the tripping of the Battery
Filter Breaker
continued
BIP troubleshooting
Circuit breaker trip LED (red) lit (continued)
a large power transient or filter failure has tripped the Battery Filter
Breaker on the NT7E56AB/BA BIP
a large power transient or filter failure has blown fuse BIPA or BIPB on the
NT7E56CA BIP
a new circuit pack with a damaged backplane connector or other major
fault is inserted into the shelf
CAUTION
Risk of interruption to service
Do not reinsert a circuit pack into shelf when that circuit pack is
suspected of causing a shelf breaker trip.
If you are installing or replacing a circuit pack and one or more of the shelf
breakers trips, remove the card from the shelf and examine the backplane
connector for damage. If no damage is evident, restore the breakers to their
normal state. Check system for any remaining alarms. Do not insert the circuit
pack again until it has been checked on a non-traffic carrying system.
end
BIP troubleshooting
Troubleshooting the modem in the BIP 8
Action
Step Action
1 Verify the type of line used on the modem.
If the line used on the modem is Then

a call-waiting line replace it with a regular telephone line.
Go to step 2
not a call-waiting line go to step 2
2 Verify that the VT100-compatible terminal did not lock up.
If the terminal screen is Then

locked enter one of the following commands:
)
<break> hx
quit all
logout
Go to step 3.
not locked go to step 3
To verify the BIP modem setting (not required on NT7E56CA BIP)
3 Remove the BIP front cover. Verify that DIP switch 1 of SW2 is set to the
equipped position (for example, to the right, as shown in Figure 8-4 on
page 8-6). If it is not, then set it to the right position.
4 Verify that the modem circuit breaker is set to the closed (ON) position, by
pushing it down (see Figure 8-5 on page 8-19). If it is not, then press it down.
To verify the user interface port setting
5 Log in to the network element to which the BIP modem is connected.
6 Ensure that the user interface port to which the modem is connected is
properly set (2400 baud, 8 bits, 1 stop bit, in service).
continued
BIP troubleshooting
Troubleshooting the modem in the BIP (continued)
Step Action
To verify the power to the NT7E90AA modem as used in the

NT7E56AB/BA BIP
7 At the front of the BIP panel, trip the modem circuit breaker to the open (OFF)
position by pulling it up (see Figure 8-5 on page 8-19).
8 Open the BIP right cover and remove the power connection (4-pin molex)
from the modem (see Figure 8-5 on page 8-19).
9 Set the modem breaker to the closed (ON) position (see Figure 8-5 on
page 8-19) by pressing it down.
10 Verify that there is -48 V (-40 to -60 Vdc) present from the molex cable
(NT7E9030) by checking the voltage across terminal leads 1 and 2. The
terminal markings are indicated at the rear of the molex connector. If -48 V is
not present, then verify that power is available to the shelf.
11 If -48 V is present, set the modem circuit breaker to open (OFF) and
reconnect the molex cable to the power connector on the modem.
12 Set the modem breaker to the closed position (see Figure 8-5 on page 8-19)
by pressing it down.
To verify the power to the NT7E90BA modem as used in the
NT7E56CA BIP
13 Check the modem fuse located in the faceplate of the logic card (behind the
right door) and replace the fuse if it is blown.
To verify the telephone wire
14 Disconnect the telephone line at the Teladapt (RJ-11C) connector on the
modem (see Figure 8-5 on page 8-19).
15 Connect the telephone line to a telephone or to another modem to verify that
the telephone line is operating correctly. If the telephone or the modem does
not operate, then replace the telephone line, or check the connections.
16 If the telephone line is operating properly, then reconnect the telephone line
at the Teladapt (RJ-11C) connector on the modem.
To verify the BIP modem cable
17 At the modem, remove the BIP modem cable (NT7E44DD/DE/DF, 9-pin
connector) from the modem (see Figure 8-5 on page 8-19).
18 Connect this cable to a VT100-compatible terminal (with a null-modem
adapter) or to another modem to verify the cable operates correctly. If the
VT100, the 9-pin to 25-pin adaptor, or the modem does not operate correctly,
then replace the NT7E44DD/DE/DF cable.
19 If the cable is operating correctly, then reconnect the BIP modem cable to the
user interface connector on the modem.
continued
BIP troubleshooting
Step Action
To verify the user interface port 1 connection

20 At the side of the shelf, verify that the NT7E44DD/DE/DF cable connects to
the user interface port 1 (9-pin) connector. Ensure that the connector is
correctly secured to the shelf connector.
To verify the modem auto-answer ringing register
21 Dial the BIP modem.
22 If there is no answer after five rings, disconnect the BIP modem cable (DB9
connector) from the modem.
23 Connect a 9-pin to 25-pin straight cable between the modem and a
VT100-compatible terminal. Use the VT100-compatible terminal to view the
status of the modem.
24 Enter the following to view the status of the SO register (which sets the default
value for how many rings occur before answering a ringing line):
AT
The screen displays OK
ATS0?
Terminal response: 000 or 001 or 002 or...
The default value should be 001 to answer on the first ring. (If it has been set
to 000, then the BIP modem would never answer back.)
25 Set the S0 register to 1 by entering:
ATS0=001
26 Ensure the correct data is entered by entering:
ATSO
If the screen displays 001, then the modem answers on the first ring.
27 Set the modem to quiet by typing:
atqi
Set the modem to turn off local command echo by typing:
ate0
28 Disconnect the 9-pin to 25-pin cable and reconnect the BIP modem cable to
the DB9 connector on the modem.
continued
BIP troubleshooting
Step Action
29 Dial the BIP modem.

30 While the modem is in use, check the type of line used. If the telephone line
has call-waiting enabled, either change the line to a non call-waiting type of
line or disable the call-waiting feature.
31 If the modem still does not operate after following step 1 to step 29, replace
the BIP modem (as outlined in Module Replacement Procedures,
323-1111-547).
32 The maintenance interface controller (MIC) circuit pack might also be
defective (the user port drivers are located in the MIC circuit pack). If the
modem still does not operate, replace the MIC circuit pack. See Module
continued
BIP troubleshooting
Step Action
Figure 8-5
Connect the 9-pin user interface connector to the modem mounted inside the BIP
FW-1826 (TBM-CA)
Normally
SW1 closed
position
Configuration Normally
DIP switches open Power connector Teladapt Female 9-pin
position (4-pin Molex) user interface
SW2
B
2 AIP
mp Ma
Te int
2 Arm Mod
mp 2 A em Molex cable (NT7E9030)
mp La
Lamp, Modem, Maintenance 2 Amp prewired to right
mp
Terminal, and BIP hand-side door PCB
circuit breakers
Modem card
BIP cover
Locking screw
Telephone
wire
BIP modem cable
NT7E56AB/BA NT7E44DD (posn 1) or
FW-1826 (tbm) NT7E44DE (posn 2) or
NT7E44DF (posn 3)
To shelf user
interface port 1
connection
NT7E56CA
Modem fuse
User Interface
Teladapt
end
9-1
Clearing OPC alarms 9-

This chapter provides alarm-clearing procedures for the alarms on the
operations controller (OPC) when used with OC-12 network elements. The
OPC, not the network element, raises the alarms.
The OPC user interface identifies these alarms as equipment alarms (for
example, in the Event Browser and Alarm Monitor tools). The alarms do not
appear on the network element user interface, except as part of the total alarm
count in the network banner line.
There is a pointer alarm you can provision to appear on a single network

element for a given OPC. Typically, you provision the alarm to appear on the
network element in which the OPC is installed. For information on the pointer
alarm, see OPC alarm(s) active alarm information in Chapter 4. The pointer
alarm becomes active whenever there is one or more alarms active on the OPC.
Note: Do not confuse the alarms the OPC raises with the circuit pack
alarms the network element raises against the OPC hardware. The OPC
circuit pack alarms are common equipment (CE) alarms (see Chapter 4,
Clearing Equipment alarms).
You can manually clear all OPC alarm according to Chapter 3 procedure,
Manually clearing OPC alarms. Nortel Networks recommends that you
manually clear the alarm only if you have corrected the root cause of the alarm.
To clear an alarm, look up the alarm in the following table, go to the referenced
page, and perform the procedure. The table lists the alarms in alphabetical
order by alarm label as they appear in the OPC user interface.
9-2 Clearing OPC alarms
Alarm Page
Below-baseline CP exists in the system 9-3
Datasync fail 9-5
Configuration audit fail 9-6
Connection audit fail 9-8
Lost peer OPC 9-10
NE DB missing/outdated 9-11
Removable media/Restore fail 9-13
Connection services disabled 9-17
User profile audit fail 9-18
NE ID renumbering in progress 9-19
Networkid and/or Systemid renumbering in progress 9-20
Backup: TCP/IP access violation Primary: TCP/IP access violation 9-21
Backup: Datacomm access violation Primary: Datacomm access 9-22

violation
Backup: network port intrusion Backup: serial port intrusion Primary: 9-23
network port intrusion Primary: serial port intrusion
Eqp 90
Below-baseline CP exists in the system 9
Probable cause
A circuit pack on a network element in the span of control is below the
hardware baseline for this software release. The alarm can also indicate that the
circuit pack is not in the network element inventory.
The alarm becomes active after a hold-off period of 1 to 2 minutes. If you have
replaced the affected circuit pack with a circuit pack above the baseline, it
clears automatically 1 to 2 minutes after you run the Hardware Baseline audit.
The alarm clears only on the OPC on which you ran the hardware baseline. If
the alarm became active on one OPC and the hardware baseline audit later
passed on the peer OPC after an activity switch, the alarm will become active
again on the original OPC if the original OPC becomes active again. In this
case, manually clear the alarm on the original OPC
Impact
Enabled by default.
Action
Step Action
1 Log in to the network element and check the equipment inventory by entering:
equipmnt sh
inventry
2 Check the Equipment ID field on the Shelf Inventory screen for the Common
Language Equipment Identifier (CLEI) code.
If the field displays Then go to

only question marks (????????) step 3
a CLEI code step 8
3 The circuit pack responsible for this alarm is not in the inventory. Verify that
the circuit pack is compatible with the current release according to the current
hardware baseline. To display the hardware baseline, see Software
Administration Procedures, 323-1111-303. You can get the latest hardware
baseline information from the Nortel Networks fax-on-demand service as
described in the technical assistance chapter of About the OC-2/OC-12
NE Library, 323-1111-090.
continued
Eqp
Below-baseline CP exists in the system (continued)
Step Action
If the circuit pack Then go to

is compatible with the hardware baseline step 4
is not compatible with the hardware baseline step 6
4 Add the circuit pack to the network element inventory according to
Commissioning Procedures, 323-1111-220.
5 Go to step 11
6 Replace the circuit pack with a circuit pack that meets the hardware baseline.
7 Go to step 11
8 Use the OPC Hardware Baseline tool to display the results of the baseline
check (see Software Administration Procedures, 323-1111-303).
9 Take note of the circuit packs that are below the baseline for the release and
the network elements in which they are equipped.
10 Go to the site of each network element with a circuit pack below the baseline
for the release. Replace each circuit pack that is below the baseline with a
circuit pack above the baseline.
11 Run the hardware baseline audit manually. For instructions, see Software
12 Use the OPC Alarm Monitor tool to display the active alarms (see Network
Surveillance Procedures, 323-1111-510). Make sure the Below-baseline CP
exists in the system alarm clears. The alarm clears 1 to 2 minutes after the
audit completes successfully.
You can also use the OPC Event Browser tool to display the logs for
information about the audit. An SDA622 log indicates the audit ran
successfully on all network elements in the span of control. An SDA344 log
indicates that the audit failed to run and provides the reason why it failed. An
SDA345 log indicates that the audit failed, but the OPC could not determine
reason for the failure.
For instructions on how to use the Event Browser, see Network Surveillance
Procedures, 323-1111-510. For more information on the logs, see Log Report
Manual, 323-1111-840.
13 If the alarm is still active, repeat this procedure until you have replaced all
below-baseline circuit packs and the alarm is no longer active.
end
Eqp 90
Datasync fail 9
Probable cause
A synchronization attempt (database backup) from the primary to the backup
OPC has failed. The backup attempt can have been either a manual or
scheduled operation.
The alarm becomes active after a hold-off period of 1 to 2 minutes. It clears

automatically 1 to 2 minutes after a successful database backup.
Impact
Enabled by default.
Action
Step Action
1 Use the Commissioning Manager to attempt a database backup from the

primary OPC to the backup OPC. For instructions, see Data Administration
Surveillance Procedures, 323-1111-510). Make sure the Datasync Fail
alarm clears. The alarm clears 1 to 2 minutes after the data synchronization
completes successfully.
information about the data synchronization. An STBY612 log indicates that
the data synchronization was successful. Other STBY logs indicate problems
with the data synchronization or other conditions that affect the
synchronization. An SDA331 log is displayed for failed data synchronization
attempts during network upgrades.
Manual, 323-1111-840.
3 If trying the operation again does not clear the problem, contact your next
level of support or Nortel Networks according to About the OC-12 NE Library,
323-1111-090.
end
Eqp 90
Configuration audit fail 9
Probable cause
A configuration audit of a ring has detected a discrepancy between the OPC
and one or more network elements in the span of control. The audit could have
been either a manual audit or a scheduled audit.

automatically 1 to 2 minutes after a successful configuration audit.
Impact
Enabled by default.
Action
Step Action
1 Check the site records to determine the intended configuration data for the
affected ring.
2 Open the Configuration Manager tool on the OPC (see Provisioning and
Operations Procedures, 323-1111-310).
3 Compare the ring configuration records with the data in the Configuration
Manager.
If the Configuration Manager data Then go to

is correct step 4
is incorrect step 7
4 If the Configuration Manager tool has the correct data, perform a
configuration audit. For instructions, see Provisioning and Operations
A list of all the network elements having discrepancies with the OPC data
appears.
5 When a prompt asks you to correct the discrepancies, select Yes.
6 Go to step 9.
7 If the Configuration Manager tool has incorrect data, correct the data in the
tool.
continued
Eqp
Configuration audit fail (continued)
Step Action
8 When the OPC configuration data is correct, select the command Save and
send configuration data. This command sends the corrected configuration
data to the network elements. For detailed instructions, see Provisioning and
9 Perform another configuration audit.
Surveillance Procedures, 323-1111-510). Make sure the Configuration audit
fail alarm clears. The alarm clears 1 to 2 minutes after the audit completes
successfully.
information about the audit. An NAD308 log is present for each audit.
Manual, 323-1111-840.
11 If the alarm is still active, repeat this procedure until you have audited all the
ring configurations for the span of control and the alarm is no longer active. If
the alarm remains active and you are satisfied that the configuration
information in the OPC is correct, there might be a data communications
problem between the OPC and the affected network elements. Check for data
communications alarms. Clear them according to Chapter 5, Clearing facility
alarms.
end
Eqp 90
Connection audit fail 9
Probable cause
A connection audit has detected a discrepancy between the OPC and one or
more network elements in the span of control. The audit could have been either
a manual audit or a scheduled audit.

automatically 1 to 2 minutes after you resolve the provisioning conflict and run
a successful connection audit.
Impact
Enabled by default.
Action
Step Action
1 Check the site records to determine the intended connection data.

2 Open the OPC Connection Manager tool and perform a connection audit
according to Provisioning and Operations Procedures, 323-1111-310.
A list of all the connections for which mismatches between the OPC and
network element data appears.
3 Resolve the mismatches by either editing the connections or deleting them,
as appropriate, according to the intended provisioning. For detailed
instructions, see Provisioning and Operations Procedures, 323-1111-310.
CAUTION
If you overwriting the network element data, you can
cause a loss of traffic. Be sure that the existing network
element connection data is inaccurate before you
overwrite it.
4 Perform a manual connection audit from the OPC using the Connection
Manager tool.
Surveillance Procedures, 323-1111-510). Make sure the Connection audit
fail alarm clears. The alarm clears 1 to 2 minutes after the audit completes
successfully.
continued
Eqp
Connection audit fail (continued)
Step Action
information about the audit. An NAD324 log indicates any problems found
with a scheduled audit. An NAD325 log indicates any problems found when
you manually audit or correct connection data.
Manual, 323-1111-840.
6 If the alarm is still active, repeat this procedure. If you are satisfied that the
connection information in the OPC is correct, there might be a data
communications problem between the OPC and the affected network
elements. Check for data communications alarms. Clear them according to
Chapter 5, Clearing facility alarms.
end
Eqp 90
Lost peer OPC 9
Probable cause
Data communications association between this OPC and its peer has failed. If
this OPC is the primary OPC, the peer is the backup OPC. If this OPC is the
backup OPC, the peer is the primary OPC. For example, the fiber between the
OPCs has been cut or damaged.

automatically 1 to 2 minutes after communications is reestablished.
Impact
Enabled by default.
There might be a segmentation of the data communications network. Such a

segmentation means the primary OPC controls part of the span of control. The
backup OPC controls the remainder of the span of control. You must repeat any
provisioning changes you make on the backup OPC in such circumstances on
the primary OPC. Otherwise, you lose the changes as the result of the next
primary to backup OPC data synchronization.
Action
Step Action
Surveillance Procedures, 323-1111-510).
2 Correct the active alarms according to the appropriate procedures in this
document.
3 When you have cleared all other alarms, make sure the Lost peer OPC
alarm clears. The alarm clears 1 to 2 minutes after the OPCs can again
communicate.
end
Eqp 90
NE DB missing/outdated 9
Probable cause
A network element database backup is either missing or out of date (more than
24 hours old).

automatically 1 to 2 minutes after all the network element databases are
present and up to date.
Impact
Enabled by default.
CAUTION
A missing or out of date database backup can result in the
network element autoprovisioning in the case of a reboot. Such
an autoprovisioning can result in a loss of service.
Action
Step Action
1 Use the OPC Backup/Restore Manager tool to check the database backups
for each of the network elements. Each network element is supposed to have
two backups, one identified as current and the other as backup1. The date
associated with both should be within 24 hours of the present time.
2 When you have identified the missing or out of date backup, log in to the
affected network element. Manually perform a database backup by entering:
equipmnt sh
backupdb
y
3 Verify that the backup was successful by checking for a FWDB400 Database
Backup Successful log by entering:
admin nep (see Note 1)
logs
open fwdb
back all (optional; see Note 2)
continued
Eqp
NE DB missing/outdated (continued)
Step Action
Note 1: If you prefer, you can use the logutil command interpreter (CI) tool
instead of the admin nep and logs commands. You can use the tool from the
command input area or in the command interpreter (CI) level of the user
interface. For more on the logs utility, see Chapter 1 of User Interfaces
Note 2: The back all command displays all the logs of the requested type
currently stored in the logs buffer. Use the back command (without the all
parameter) to step back through the logs one by one.
Note 3: Refer to Log Report Manual, 323-1111-840, for a description of the
FWDB400 log and to Network Surveillance Procedures, 323-1111-510, for a
description of how to access logs through the OPC Event Browser tool.
Surveillance Procedures, 323-1111-510). Make sure the NE DB
missing/outdated alarm clears. The alarm clears 1 to 2 minutes after all the
databases are present and up to date.
5 If the alarm does not clear, repeat step 1 to step 4. If the alarm remains active
after the second attempt, contact your next level of support or Nortel
Networks according to About the OC-12 NE Library, 323-1111-090.
end
Eqp 90
Removable media/Restore fail 9
Probable cause
An attempt to back up to tape or cartridge, restore a backup from tape or
cartridge, or to display the tape or cartridge contents has failed. Some
problems that can affect tape or cartridge backup and restore operations are as
follows:
There is no tape or cartridge drive in the version of the OPC on which the
attempt was made.
There is no tape or cartridge in the tape or cartridge drive.
The tape or cartridge drive is already in use.
The contents on the tape or cartridge are unrecognized by the OPC.
The tape was ejected.
The tape is write protected.
The data on the tape or cartridge is corrupted.
The data on the tape or cartridge is not for the correct software release.
The tape or cartridge backup is for a different TransportNode product.
The database backup between the primary and backup OPCs failed after a
restore from tape or cartridge.
A software problem exists on the OPC or the disk space on the OPC is full.
automatically 1 to 2 minutes after a successful backup to tape or cartridge or
restore from tape or cartridge (depending on which operation failed).
Impact
Enabled by default.
Action
Step Action
1 Make sure the OPC on which you are attempting the operation is equipped
with a tape or cartridge drive.
continued
Eqp
Removable media/Restore fail (continued)
Step Action
2 Verify that the tape or cartridge is not damaged and that it contains the
backup for the correct OPC and software release. Never store tape or
cartridges in the sun, near a heat source, or near a magnetic source such as
a power converter. If the OPC can detect that the tape or cartridge is
damaged, the message bad tape appears as a response to the attempt to
perform the backup.
3 If you are backing up to tape, make sure the tape is not write-protected. You
can remove the write protection by closing the tab on the tape. If the
write-protection is in place, the message unable to write to tape appears as
a response to the attempt to perform the backup.
Note: The cartridge is not provided with a write protect capability.
4 Reattempt the data backup or restore operation two more times. After each
attempt, use the OPC Alarm Monitor tool to display the active alarms (see
If the message couldnt be accessed appears as a response to the attempt
to perform the backup, the failure is most likely the result of a transient
condition.
If the message disk full appears, the OPC disk is full. You cannot perform
the backup or restore operation until disk space is available. In this case, go
to step 12.
5 If you have corrected the cause of the problem or if the problem was only
transient, the Tape backup/Restore fail alarm clears 1 to 2 minutes after the
operation completes successfully.
You can use the OPC Event Browser tool to display the logs for information
about the operation.
continued
Eqp
Step Action
Manual, 323-1111-840. The following logs are applicable:
SDA320 indicates that the backup to tape or cartridge from the OPC disk
has failed (for either a manual or scheduled operation).
SDA321 indicates that the restore from tape or cartridge to the OPC disk
has failed.
SDA322 indicates that the data transfer between the primary and backup
OPCs has failed following a data restore from tape or cartridge operation.
SDA349 indicates the software load is only partially on the OPC because
the previous transfer from tape or cartridge was not successful.
SDA350 indicates a failure in the backup to tape or cartridge because of
a transient error or the OPC disk is full.
SDA351 indicates a failure in the restore from the tape or cartridge to the
OPC disk because of a transient error, the OPC disk is full, or the tape or
cartridge is defective.
SDA620 indicates the completion of a save-to-tape or cartridge
operation.
SDA621 indicates the completion of a restore-from-tape or cartridge
operation.
SDA650 indicates that the transfer of files from the OPC to tape or
cartridge was performed successfully.
SDA651 indicates that the transfer of files from tape or cartridge to the
OPC was performed successfully.
SDA720 indicates the start of a save-to-tape or cartridge operation.
SDA721 indicates the start of a restore-from-tape or cartridge operation.
6 If the same error occurs each time you attempt the operation, remove the tape
or cartridge and reattempt the same procedure with another tape or cartridge.
In the case of a restore operation, use the most recent backup.
7 If the alarm is still active after using another backup tape or cartridge, shut
down the OPC according to Common Procedures, 323-1111-846.
continued
Eqp
Step Action
8 Try the operation again after the OPC reboots.

9 If the alarm remains active, the tape or cartridge drive might be damaged.
Replace the OPC according to Module Replacement Procedures,
323-1111-547.
10 Check the active alarms using the Alarm Monitor tool.
11 If the alarm is still active, the original OPC is not at fault. Reinstall the original
OPC according to Module Replacement Procedures, 323-1111-547.
12 Clear all other active alarms, then contact your next level of support or Nortel
Networks according to About the OC-12 NE Library, 323-1111-090. Report
the cause of the problem as indicated in any relevant log reports.
end
Eqp 90
Connection services disabled 9
Probable cause
This alarm is raised after the command /iws/obm/cs_state off is invoked from
a UNIX shell. The command /iws/obm/cs_state off is used during SLAT to
disable connection services functionality. Disabling connection services
prevents all interfaces from provisioning, deleting, or editing cross-connects,
and also prevents the discovery audit from running and transferring any
fictitious cross-connects from the NE to the OPC.
Impact
Enabled by default.
Action
Step Action
1 Enable connection services by using the command

/iws/obm/cs_state on
end
Eqp 90
User profile audit fail 9
Probable cause
This alarm indicates that a user profile audit attempted by the OPC
CentralizedUser Administration tool has failed.
The alarm becomes active when the failure is detected. It clears when the audit
runs successfully.
Impact
Enabled by default.
Action
Step Action
1 Use the Centralized User Administration tool to manually run a user profile
data audit. For instructions, see System Administration Procedures,
323-1111-302.
information about the audit. An SEC606 log indicates the audit ran
successfully on all network elements in the span of control. An SEC306 log
indicates that the audit failed to run and identifies the network elements that
were not audited.
Manual, 323-1111-840.
2 If the audit does not run successfully, troubleshoot the data communications
links between the OPC and the affected network elements.
end
Eqp 90
NE ID renumbering in progress 9
Probable cause
This alarm indicates that an in-service renumbering of the network element is
in progress. The network element number is also called the network element
identifier (NE ID).
It is recommended that only the user doing the network element renumbering
be logged in to the network element or OPC while this alarm is active. No other
user is to make any maintenance or provisioning changes until the
renumbering procedure is complete.
The alarm becomes active when the renumbering procedure begins. The alarm
clears automatically when the procedure is complete.
Impact
Warning, non-service affecting (by default).
Enabled by default.
There is a loss of communications association between the network element

and the operations controller (OPC) during the renumbering procedure. The
data communications exerciser cannot run during the procedure. The result of
an attempt to run the data communications exerciser is an Exerciser fail
alarm on the affected network element.
The network element number for existing active alarms and logs take the new
network element number as a consequence of the in-service renumbering
procedure. Cleared alarms are not affected.
Action
No user action is necessary, except to complete the In-service NE ID
renumbering procedure according to System Expansion Procedures II,
323-1111-225.
end
Eqp 90
Networkid and/or Systemid renumbering in progress9
Probable cause
This alarm indicates that an in-service renumbering of the network identifier
or system identifier is in progress.
It is recommended that only the user doing the renumbering be logged in to the
network element or OPC while this alarm is active. No other user is to make
any maintenance or provisioning changes until the renumbering procedure is
complete.
The alarm becomes active when the renumbering begins. The alarm clears
automatically when the renumbering is complete.
Impact
Enabled by default.
There is a brief loss of communications association between the network

element and the operations controller (OPC) during the renumbering. The
association is automatically restored when the OPC and network elements
update their respective databases with the new network identifier or system
identifier.
Action
No user action is necessary.
end
Eqp 90
Backup: TCP/IP access violation
Primary: TCP/IP access violation 9
Probable cause
The access control software has denied a user on the primary or backup OPC
access to the TCP/IP network.
The alarm becomes active when the access denial occurs. You must clear the
alarm manually after you investigate the potential security violation.
Impact
Enabled by default.
Action
Step Action
1 Investigate the potential attempt to violate security by checking the security

(SEC) logs using the OPC Event Browser. For instructions, see Network
Surveillance Procedures, 323-1111-510.
2 Clear the alarm manually using the OPC Alarm Provisioning tool. For
instructions, see Chapter 3, How to begin trouble clearing.
end
Eqp 90
Backup: Datacomm access violation
Primary: Datacomm access violation 9
Probable cause
The OPC has detected an attempt to access a data communications node over
the SONET data communications network for which the user is not allowed
access. The login attempt can be either from or to this OPC as follows:
from this OPC to a network element (nelogin command or NE Login
Manager) or another OPC (remote OPC login from a graphical terminal)
to this OPC from a network element (rlogin command) or another OPC
(remote OPC login from a graphical terminal)
Access to and from the OPC and the network elements in the span of control
is controlled through access and deny lists provisionable through the OPC
config_dcc_ac command. If the feature is enabled, access must be explicitly
allowed to OPCs and network elements in both the local and remote networks
or else login access is denied. For more information, see System
These alarms become active when the OPC detects the access attempt. The
alarms must be cleared manually. Only one instance of either alarm can be
active at one time. Therefore, an active alarm might indicate more than one
access violation.
Impact
Enabled by default.
Action
Step Action
1 Alert the system administrator of the access attempt.

2 You must manually clear the alarm using the OPC Alarm Provisioning tool.
For instructions, see Chapter 3, How to begin trouble clearing.
end
Eqp 90
Primary: serial port intrusion 9
Probable cause
There was more than the allowable number of unsuccessful login attempts to
the OPC. A login attempt is unsuccessful if either the user identifier or
password entered is invalid.
The alarm indicates whether the unsuccessful login attempt relates to the
primary or backup OPC. The active OPC raises the alarm. For example, if the
primary OPC is active and the backup OPC detects an intrusion attempt, the
alarm becomes active on the primary OPC.
Only one instance of each of these alarms can be active at a time, even if there
are multiple active intrusion attempts for a given OPC.
The Backup: serial port intrusion and Primary: serial port intrusion alarms
relate to login attempts from local equipment connected to the following
physical ports:
port B on the OC-48 terminal shelf

ports B or 3 on the OC-48 regenerator/optical amplifier shelf
The Backup: network port intrusion and Primary: network port intrusion
alarms relate to remote login attempts over network connections to the OPC.
Users can access the OPC remotely from a network element or over the
following interface ports:
port B (mapped to user interface port B on the OC-48 terminal shelf)

ports B, 2, and 3 (mapped to user interface ports B, Esp 2, and Esp 1 on the
OC-48 regenerator/optical amplifier shelf, respectively)
the Ethernet port on the OPC faceplate
For detailed connection information and the types of connection that support
network intrusion attempt handling, see System Administration Procedures,
323-1111-302.
continued
Eqp
Primary: serial port intrusion (continued)
The alarm becomes active when the OPC detects a provisioned number of
invalid login attempts from the same network address. The allowable number
of unsuccessful login attempts ranges from 2 to 9, as provisioned through the
Centralized User Administration tool. For more information, see System
The alarm clears automatically after a set period of time, called the alert
duration period. You can provision the alert duration period through the
Centralized User Administration tool. The alarm also clears in the following
circumstances:
If the OPC reboots, the alarm clears when the OPC is active again.
If there is an activity switch away from then back to the OPC, the alarm
clears when the OPC is again the active OPC.
If there is a loss of data communications association with the inactive OPC
when an intrusion attempt alarm is active on that OPC, the alarm clears
when association is restored.
In the case of an OPC shutdown, the intrusion alarms clear when the OPC
becomes active again.
Impact
Enabled by default (cannot be deprovisioned).
For local connections, the OPC locks out the physical port when the maximum
number of login attempts is exceeded. No user can log in to the network
element through that port until the provisioned alert duration period expires.
For network connections, there is no lock. There is only an alarm to indicate

that an intrusion attempt condition exists. The user can log in again
immediately during the intrusion attempt condition, but the alarm remains
active for the remainder of the alert duration period.
The alert duration period can be up to 999 seconds.
Action
No user action is necessary to clear the alarm. However, the system
administrator might wish to investigate to ensure that there has not been an
unauthorized attempt to breach network security.
continued
Eqp
Primary: serial port intrusion (continued)
You can clear an intrusion attempt condition according to System

end
10-1
Clearing incorrect Application Select

state 10-
This chapter provides an alarm-clearing procedure for the alarms that are
possibly raised by an incorrect Application Select state.
In rare circumstances, Application Select may fall into an incorrect state as a

result of ESI carrier failure and cause timing deviation of system clock. In such
a case, the following ESI and OC12 alarms will be activated.
ESI One of the following alarms will be raised for each
subunit:
- Subunit fail
- Timing generation entry to (fast, acquire or freerun)
Other possible alarms:
- BITS Degraded clock carrier
- BITS Timing reference interface fail
OC12 One of the following alarms will be raised:
- Unable to track clock reference
- Circuit pack fail
In addition, the following alarms may be activated in response to the incorrect

Application Select state.
If shelf is equipped with Then the following alarms may be raised.
OC3 trib STS1 Rx loss of pointer (Fac OC-3/OC12)
DS3 Frequency out of range (Fac DS3)
Tx loss of frame (Fac DS3)
Circuit pack fail (Eqp DS3)
STS1 STS1 intercard fail (Eqp STS1)
DS1 Circuit pack fail (Eqp DS1)
10-2 Clearing incorrect Application Select state
Only if you meet these conditions, perform Procedure 10-1 to:

determine if the incorrect Application Select state is the cause
clear the incorrect Application state condition
Otherwise, continue to execute the usual alarm clearing procedure.
Clearing incorrect Application Select state 10-3
Procedure 10-1
Trouble clearing incorrect Application Select state
Use this procedure to determine if there is an incorrect Application Select state,
and to clear it if the Application Select state is incorrect.
Step Action
1 Replace the ESI carrier circuit pack.

2
If the alarms Then the problem:
disappear is due to the incorrect Application Select state.
remain is not due to the incorrect Application Select state.
Return to your normal troubleshooting procedure.
end
10-4 Clearing incorrect Application Select state
SONET Transmission Products
S/DMS TransportNode
OC-3/OC-12 NETBM
Alarm and Trouble Clearing Procedures
Copyright 19922001 Nortel Networks, All Rights Reserved
The information contained herein is the property of

Nortel Networks and is strictly confidential. Except as expressly
authorized in writing by Nortel Networks, the holder shall keep all
information contained herein confidential, shall disclose it only to
its employees with a need to know, and shall protect it, in whole
or in part, from disclosure and dissemination to third parties with
the same degree of care it uses to protect its own confidential
information, but with no less than reasonable care. Except as
expressly authorized in writing by Nortel Networks, the holder is
granted no rights to use the information contained herein.
Nortel Networks and S/DMS TransportNode are trademarks of

Nortel Networks. VT100 is a trademark of Digital Equipment
Corporation. UNIX is a trademark of X/Open Company Ltd.
323-1111-543
Rel 14 Standard
February 2001
Printed in Canada

Alarm and Trouble Clearing Procedures

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alarm and Trouble Clearing Procedures

Uploaded by

Copyright:

Available Formats

NT7E65DJ 323-1111-543

SONET Transmission Products

Safety guidelines 1-1

Alarm reporting and surveillance 2-1

Common equipment and environmental alarm hierarchy 2-13

How to begin trouble clearing 3-1

Clearing equipment alarms 4-1

Forced switch request 4-57

Failure to lock 4-112

Firmware version mismatch 4-222

Maps invalid 4-304

Firmware/software incompatible 4-349

Clearing facility alarms 5-1

Line Rx ES threshold 1, 2 5-49

Fac OC12 5-132

Clearing environment alarms 6-1

Interpreting circuit pack LEDs and lamps 7-1

Troubleshooting the breaker interface panel (BIP) 8-1

Clearing OPC alarms 9-1

Clearing incorrect Application Select state 10-1

About this document

NE and OPC user interfaces

Circuit pack/facility states

In service In this state, all alarms, protection switching, and performance

Circuit pack states Possible facility states

System actions Null OOS In-service

References in this document

Warnings and safety precautions

To avoid damage to equipment or service interruptions, follow all caution

Alternatively, your company may provide antistatic protection by mounting

Handling, installing, or replacing circuit packs

Laser products are subject to federal regulations, state or provincial

All Nortel Networks S/DMS transmission Caution

During testing and maintenance, some procedures require the handling of

This level of radiation is sufficient to cause injury to personnel and caution

Handling optical fibers

Repairing optical fibers

Alarm reporting and surveillance 2-

Note: Shelf alarm monitoring is not available during processor circuit

Alarm severity, service code, and protection and activity status

Protection and activity status

The protection equipment or facility is not available during protection lockout,

Local alarm indications

Battery A Battery B ACO/LT

ACO/LT Critical Major Minor ESD

ACO/LT Critical Major Minor ESD

Circuit pack alarms

The circuit-pack LEDs are illustrated in Circuit Pack Descriptions,

Cooling unit alarms

These interfaces are described in more detail in Alarms and Surveillance

Serial Telemetry ports

Modem to Remote Terminal

Facility alarms Equipment alarms Environment alarms

COMM CE (common equipment) (shelf) CE (common equipment)

DS1 DS1 Input

DS3 DS3 REMT (remote)

ESI ESI (external synchronization

OC3/OC12 Lpbk (loopback)

REMT (remote) MIC (maintenance interface

STS-1 OC3/OC12 (OC-3/OC-12)

STS1 (STS-1 electrical interface)

Alarm hierarchies (masking relationships)

ESI timing Environmental

OC-12 DS1 DS3 STS-1 DS1 Common OC-12 STS-1