Tellabs 5500 FP11.1 Trouble Shooting Manual PDF

®
Troubleshooting Manual
76.5500/29
®
Tellabs 5500 Digital Cross-Connect
®
Tellabs 5500S Digital Cross-Connect
Revision R, 7/07
Copyright © 2007 Tellabs. All rights reserved.
FCC Notification Federal Communications Commission (FCC) Rules require that you be notified of
Statement the following:
This equipment has been tested and found to comply with the limits for a Class A
digital device, pursuant to part 15 of the 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.
Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his
own expense.
Changes or modifications not expressly approved by Tellabs Operations, Inc., in
writing can void the user’s authority to operate the equipment.
Industry Canada Industry Canada interference-causing equipment regulations require that you be
Notification Statement notified of the following:
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du
Canada.
Copyright Statement This Tellabs manual is owned by Tellabs or its licensors and protected by U.S. and
international copyright laws, conventions, and treaties. Your right to use this manual
is subject to limitations and restrictions imposed by applicable licenses and
copyright laws. Unauthorized reproduction, modification, distribution, display or
other use of this manual may result in criminal and civil penalties.
Trademark Notice The following trademarks and service marks are owned by Tellabs Operations, Inc.,
®
or its affiliates in the United States and/or other countries: CABLESPAN ,
® ® ® ™ ®
CEC-128 , DXX , , DYNAMIC SIGNAL TRANSFER , EC DUO ,
® ® ™
ENHANCED AUDIO PLUS , EXPRESS/PATH , FOCUS , INTELLIGENT
™ ® ® ® ®
SERVICE EDGE , MARTIS , , MARTISDXX , ,
SM ™ ™ ®
METROCARE , METROVANTAGE , METROWATCH , NETREACH ,
® ®
NETWISE , SCULPTURED SOUND , TECHNOLOGY THAT TRANSFORMS
™ ® ® ®
THE WAY THE WORLD COMMUNICATES , , TELLABS , ,
™
TELLABS PROPARTNER , TELLABS. THE FUTURE OF YOUR BUSINESS.
™ ®
STARTING NOW , TEL/MOR , THE WORLD COMMUNICATES THROUGH
™ ® ® ®
TELLABS , TITAN , VERITY , YOUR NETWORKING PARTNER
Any other company or product names may be trademarks of their respective

companies.
Contact Information In an effort to improve the quality of this document, please notify Tellabs Technical
Assistance at 1.800.443.5555 in North America or 1.630.798.7070 outside North
America if any anomalous conditions are observed.
Troubleshooting Manual Contents
Contents Page
Section 1 Introduction 29-1
Reason for Issue .............................................................................................. 29-3
Tellabs Technical Assistance ........................................................................... 29-3
Conventions Used in This Manual ................................................................... 29-4
Performing Numbered Steps ..................................................................... 29-4
Command and System Response Conventions ........................................ 29-6
TL1 Command Language .......................................................................... 29-7
Abbreviations ............................................................................................. 29-8
Fiber Optic Safety .......................................................................................... 29-10
Laser........................................................................................................ 29-10
Safety Precautions................................................................................... 29-10
Optical Fiber Handling ............................................................................. 29-11
Removing Modules ........................................................................................ 29-13
Module Removal...................................................................................... 29-14
High Density Module Removal ................................................................ 29-15
MIM96E Module Removal ....................................................................... 29-16
OPM3 Removal ....................................................................................... 29-19
OPM3X8 Removal ................................................................................... 29-20
OPM12 Removal ..................................................................................... 29-23
OPM12X4 Removal ................................................................................. 29-25
OPM48 Removal ..................................................................................... 29-28
CAM Removal.......................................................................................... 29-31
CCPMA Removal..................................................................................... 29-33
Consolidated Core Switch Shelf Module Removal......................................... 29-36
CCSM and CGCM Removal .................................................................... 29-36
NIM and PAM Removal ........................................................................... 29-37
LAN Switch Module (LSM) Removal .............................................................. 29-40
Synchronization Cables ................................................................................. 29-42
Standard Core Switch Synchronization Timing Cables ........................... 29-42
AC Shelves Revision J and Later...................................................... 29-43
Hybrid Consolidated Core Switch Synchronization Timing Cables ......... 29-45
Consolidated Core Switch with DS1 Support Synchronization Timing
Cables......................................................................................... 29-48
Consolidated Core Switch without DS1 Support Synchronization Timing
Cables......................................................................................... 29-51
Section 2 Troubleshooting the Administrative Complex 29-53

Hardware Requirements ................................................................................ 29-54
Status of the LEDs on a Faulted Module ....................................................... 29-54
System Pre-Checks ....................................................................................... 29-64
Determining the Meaning of Alarm Messages ............................................... 29-73
Administrative Complex (AC) Alarm Messages....................................... 29-74
Alarm Interface Module (AIM) Alarm Messages ...................................... 29-75
System Communication Module 1 (SCM-1) Alarm Messages................. 29-77
System Communication Module 2 (SCM-2) Alarm Messages................. 29-78
Hard Disk Drive (HDD) Alarm Messages................................................. 29-79
Administrative Processor Module (APM) Alarm Messages ..................... 29-80
Synchronization Interface Module (SIM) Alarm Messages...................... 29-82
LAN Switch Module (LSM) Alarm Messages........................................... 29-85
LAN Interface Panel (LIP) Alarm Messages ............................................ 29-86
Administrative Complex Power Supply (ACPS) Alarm Messages........... 29-87
76.5500/29, Rev R 7/07 Page 29-i

Contents Troubleshooting Manual
Contents Page
Primary Memory (PRI) Alarm Messages ................................................. 29-88
Secondary Memory (SEC) Alarm Messages ........................................... 29-89
Removable Storage Drive (RSD) Alarm Messages................................. 29-90
Removable Media (REMV) Alarm Messages .......................................... 29-91
Operation Channel (CHAN) Alarm Messages ......................................... 29-92
Operation LINK Alarm Messages ............................................................ 29-94
Control LAN Related Descriptions (LAN-1) ............................................. 29-94
CO Local Area Network (LAN) (LAN-2) Alarm Messages ....................... 29-95
Transmission Control Protocol/Internet Protocol (TCP/IP) Alarm
Messages ................................................................................... 29-96
Timing Reference (REF) Alarm Messages .............................................. 29-97
Network Element (NE) Alarm Messages ............................................... 29-100
Alarm Interface Module (AIM) ...................................................................... 29-102
System Communication Modules (SCM-1 and SCM-2) ............................... 29-110
Data Storage Module (DSM) ........................................................................ 29-117
Restoral Using CRTE-EQPT::HDD........................................................ 29-123
Completion ...................................................................................... 29-126
Administrative Processor Module (APM) or System Processor Module
(SPM) .............................................................................................. 29-131
Troubleshooting an APM UEQ Alarm .................................................... 29-141
Synchronization Interface Module (SIM) ...................................................... 29-146
LAN Switch Module ...................................................................................... 29-171
LAN Interface Panel ..................................................................................... 29-180
Remove Faulted LIP or LIP Cable................................................... 29-184
AC-x Is STBY or OOS, SIM-x Is MSTR........................................... 29-185
Editing SIM-x to OOS ...................................................................... 29-187
Turning Breakers Off ....................................................................... 29-189
Determining AC Shelf Revision ....................................................... 29-190
AC Shelf Rev B Through I ............................................................... 29-191
AC Shelf Rev J or Later .................................................................. 29-191
Removing LIP Cables ..................................................................... 29-191
Replacing LIP ........................................................................................ 29-193
Removing Cables AC Shelf Rev B Through I.................................. 29-193
Removing Cables AC Shelf Rev J and Later .................................. 29-194
Removing the LIP............................................................................ 29-195
Install Replacement LIP .................................................................. 29-195
Administrative Complex Power Supply Module (ACPS) .............................. 29-204
Primary Memory (PRI) ................................................................................. 29-210
Secondary Memory (SEC) ........................................................................... 29-214
Single Removable Media (SRM) .................................................................. 29-218
Link (LINK) or Channel (CHAN) ................................................................... 29-225
Local Area Network (LAN-1) ........................................................................ 29-230
Troubleshooting Control LAN in System with Hybrid or CCS Switch
Core .......................................................................................... 29-238
Timing Reference (REF) .............................................................................. 29-242
Page 29-ii 7/07 76.5500/29, Rev R

Contents Page
Section 3 Troubleshooting the Network Complex 29-245
Hardware Requirements .............................................................................. 29-246
Status of the LEDs on a Faulted Module ..................................................... 29-246
Troubleshooting the Network Complex ........................................................ 29-255
System Pre-Checks ............................................................................... 29-256
Determining the Meaning of Alarm Messages ............................................. 29-266
Network Complex (NC) Alarm Messages .............................................. 29-267
Network Group Controller Module (NGC) Alarm Messages .................. 29-268
Network Timing Distribution Module (NTDM) Alarm Messages ............ 29-269
Center Stage Module (CSM) Alarm Messages...................................... 29-271
CSM Adapter Module (CAM) Alarm Messages ..................................... 29-273
End Stage Module (ESM) Alarm Messages .......................................... 29-276
Center Stage Shelf Power Supply Module (CSSPS) Alarm Messages . 29-280
End Stage Shelf Power Supply Module (ESSPS) Alarm Messages...... 29-281
Network Group Controller Module (NGC) .................................................... 29-282
Network Timing Distribution Module (NTDM)............................................... 29-292
Center Stage Module (CSM) ........................................................................ 29-307
CSM Adapter Module (CAM) ....................................................................... 29-318
Verifying SDF48 Cables on CAM .......................................................... 29-328
Troubleshooting SDF48 Loss of Signal Alarms on CAM................. 29-329
Troubleshooting SDF48 Mismatch Alarms on CAM........................ 29-331
End Stage Module (ESM) ............................................................................ 29-332
Verifying Proper Light Levels on a Non-High Density Port Shelf........... 29-340
Verifying Proper Light Levels on a High-Density Port Shelf .................. 29-345
Center Stage Shelf Power Supply Module (CSSPS) ................................... 29-353
End Stage Shelf Power Supply Module (ESSPS) ........................................ 29-358
Section 4 Troubleshooting Consolidated Core Switch Shelf

Equipment 29-363
Troubleshooting the Consolidated Core Switch Shelf .................................. 29-371
System Pre-Checks ............................................................................... 29-372
Consolidated Core Switch (CCS) Shelf Alarm Messages ..................... 29-382
Consolidated Core Switch Module (CCSM) Alarm Messages............... 29-383
Port Aggregation Module (PAM) Alarm Messages ................................ 29-385
Network Interface Module (NIM) Alarm Messages ................................ 29-388
Consolidated Group Controller Module (CGCM) Alarm Messages ....... 29-392
Consolidated Core Switch Module (CCSM) ................................................. 29-394
Port Aggregation Module (PAM) .................................................................. 29-405
Checking PAM to TSI96P High-Density SDF Fiber Cable Integrity ............. 29-413
Laser ............................................................................................... 29-413
Safety Precautions .......................................................................... 29-413
Optical Fiber Handling..................................................................... 29-414
Checking TSI96P Receive Fibers ................................................... 29-415
Checking PAM Transmit Power Levels ........................................... 29-422
Checking PAM Receive Fibers........................................................ 29-423
Checking TSI96P Transmit Power Levels....................................... 29-429
Finalizing Procedure ....................................................................... 29-430
Network Interface Module (NIM) .................................................................. 29-434
76.5500/29, Rev R 7/07 Page 29-iii

Contents Page
Verifying SDF48 Cables on NIM............................................................ 29-442
Troubleshooting SDF48 Loss of Signal Alarms on NIM .................. 29-442
Troubleshooting SDF48 Mismatch Alarms on NIM ......................... 29-445
Consolidated Group Controller Module (CGCM) ......................................... 29-450
Troubleshooting CGCM LAN Cables..................................................... 29-463
Checking LTIP to LIP Cables................................................................. 29-464
Checking CGC to CGC Cables.............................................................. 29-467
Verifying CGC LAN Cabling................................................................... 29-468
Section 5 Troubleshooting System Common Equipment 29-473

System Pre-Checks ..................................................................................... 29-479
Port Group Controller Module (PGC) Alarm Messages......................... 29-481
Time Slot Interchange Module (TSI) Alarm Messages .......................... 29-484
Line Interface Module (LIM) Alarm Messages ....................................... 29-492
Port Shelf Power Supply Module (PPS) Alarm Messages..................... 29-493
Port Group Controller Module (PGC) ........................................................... 29-494
Time Slot Interchange Module (TSI) ............................................................ 29-506
Checking High-Density SDF Fiber Cable Integrity ....................................... 29-520
Laser ............................................................................................... 29-520
Safety Precautions .......................................................................... 29-520
Optical Fiber Handling..................................................................... 29-521
Checking High-Density SDF Fiber Cable Integrity for TSI96................. 29-522
Checking TSI Receive Fibers.......................................................... 29-522
Checking ESM Transmit Power Levels ........................................... 29-529
Checking ESM Receive Fibers........................................................ 29-531
Checking TSI Transmit Power Levels ............................................. 29-537
Checking High-Density SDF Fiber Cable Integrity for TSI96P .............. 29-538
Checking TSI96P Receive Fibers ................................................... 29-539
Checking PAM Transmit Power Levels ........................................... 29-546
Checking PAM Receive Fibers........................................................ 29-547
Checking TSI96P Transmit Power Levels....................................... 29-553
Line Interface Module (LIM) ......................................................................... 29-559
Port Shelf Power Supply Module (PPS) ....................................................... 29-568
Section 6 Troubleshooting the Port Shelves 29-575

Hardware Requirements........................................................................ 29-576
OPM3X8 Port Module LEDs............................................................ 29-587
Fan Tray Module LEDs ................................................................... 29-607
Port Complex (PC) Alarm Messages..................................................... 29-609
DS1 and Double-Density DS1 Port Module Alarm Messages ............... 29-611
DS3 Port Module Alarm Messages........................................................ 29-615
Electrical Port Module (EPM) Alarm Messages..................................... 29-620
STS-1 Port Module Alarm Messages .................................................... 29-624
Page 29-iv 7/07 76.5500/29, Rev R

Contents Page
DS1 and Double-Density DS1 Redundant Port Module Alarm
Messages ................................................................................. 29-629
DS3 Redundant Port Module Alarm Messages ..................................... 29-633
Redundant Electrical Port Module (REPM) Alarm Messages................ 29-638
STS-1 Redundant Port Module Alarm Messages.................................. 29-642
Optical Port Module Alarm Messages ................................................... 29-647
CCPMA Alarm Messages ...................................................................... 29-651
RCCPMA Alarm Messages ................................................................... 29-655
Mapping Module (MM) Alarm Messages ............................................... 29-659
Redundant Mapping Module (RMM) Alarm Messages.......................... 29-664
Mapping Interface Module (MIM) Alarm Messages ............................... 29-669
Pluggable Transceiver (PT) Alarm Messages ....................................... 29-673
Fan Tray Module and Air Filter Alarm Messages .................................. 29-675
Electrical Port Modules (DS1, DD DS1, DS3, STS-1, or EPM).................... 29-676
Redundant Electrical Port Modules (DS1, DD DS1, DS3, STS-1, REPM)... 29-694
Optical Port Modules (OPM3, OPM3X8, OPM12, OPM12X4, OPM48)....... 29-705
Working OPM3, OPM3X8, OPM12, OPM12X4, or OPM48................... 29-706
Protect OPM3, OPM3X8, OPM12, OPM12X4, or OPM48 .................... 29-739
CCPMA ........................................................................................................ 29-770
RCCPMA...................................................................................................... 29-784
Mapping Modules (MM) ............................................................................... 29-794
Redundant Mapping Modules (RMM) .......................................................... 29-807
Mapping Interface Module (MIM) ................................................................. 29-815
4xGbE Port Module (MIM96E) ..................................................................... 29-824
Pluggable Transceiver (PT) ......................................................................... 29-835
Fan Tray Module .......................................................................................... 29-843
Section 7 Troubleshooting the Facilities 29-851

System Pre-Checks ..................................................................................... 29-852
DS1 Di-Group Termination (T1 DGR) Alarm Messages........................ 29-855
DS1 Constituent (T1 CST) Termination Alarm Messages ..................... 29-857
DS1 Internal Termination (DS1 TRMINT) Alarm Messages .................. 29-860
DS2 Termination (T2) Alarm Messages ................................................ 29-862
DS3 Di-Group Termination (T3 DGR) Alarm Messages........................ 29-863
DS3 Constituent (T3 CST) Termination Alarm Messages ..................... 29-866
DS3 Internal Termination (T3 TRMINT) Alarm Messages..................... 29-867
Electrical Carrier 1 (EC1) Termination Alarm Messages ....................... 29-869
STS-1 Termination Alarm Messages..................................................... 29-871
Virtual Tributary 1 Termination (VT1) Alarm Messages......................... 29-874
Optical Carrier 3, 12, or 48 (OC3, OC12, or OC48) Termination Alarm
Messages ................................................................................. 29-878
STS3C Termination Alarm Messages ................................................... 29-884
DS1 VT1 Constituent (VT1 CST) Alarm Messages ............................... 29-887
T1 Internal (T1INT) Termination Alarm Messages ................................ 29-889
Ethernet (ETH) Termination Alarm Messages....................................... 29-890
Ethernet Management (ETHMNG) Termination Alarm Messages ........ 29-891
Link Aggregation Group (LAG) Alarm Messages .................................. 29-892
Point to Point Protocol (PPP) Alarm Messages..................................... 29-892
Point to Point Protocol Group (PPPG) Alarm Messages ....................... 29-893
Virtual Concatenation Group (VCG) Alarm Messages .......................... 29-894
76.5500/29, Rev R 7/07 Page 29-v

Contents Page
DS1 Di-Group, Constituent, or Internal Termination (T1 DGR, CST, or
TRMINT) ......................................................................................... 29-897
DS2 Termination (T2)................................................................................... 29-901
DS3 Di-Group Termination (T3 DGR) .......................................................... 29-903
DS3 Constituent Termination (T3 CST) ....................................................... 29-906
DS3 Internal Termination (DS3 TRMINT) .................................................... 29-913
Electrical Carrier 1 Termination (EC1) ......................................................... 29-915
STS-1 Termination ....................................................................................... 29-919
Virtual Tributary 1 Termination (VT1) ........................................................... 29-925
Optical Carrier 3-Working Termination (OC3-W) ......................................... 29-931
Optical Carrier 3-Protect Termination (OC3-P) ............................................ 29-936
Optical Carrier 12-Working Termination (OC12-W) ..................................... 29-940
Optical Carrier 12-Protect Termination (OC12-P) ........................................ 29-945
Optical Carrier 48-Working Termination (OC48-W) ..................................... 29-949
Optical Carrier 48-Protect Termination (OC48-P) ........................................ 29-954
STS3C Termination...................................................................................... 29-958
DS1 VT1 Constituent (VT CST) ................................................................... 29-965
T1 Internal (T1INT) Termination................................................................... 29-971
STS1-Working Termination (STS1-W) ......................................................... 29-974
STS1-Protect Termination (STS1-P)............................................................ 29-979
VT1-Working Termination (VT1-W).............................................................. 29-984
VT1-Protect Termination (VT1-P) ................................................................ 29-988
STS3C-Working Termination (STS3C-W).................................................... 29-991
STS3C-Protect Termination (STS3C-P) ...................................................... 29-997
Virtual Concatenation Group (VCG)........................................................... 29-1002
Ethernet (ETH) Termination ....................................................................... 29-1006
Ethernet Management (ETHMNG) Termination......................................... 29-1010
Link Aggregation Group (LAG)................................................................... 29-1014
Point-to-Point Protocol (PPP) Termination................................................. 29-1017
Point-to-Point Protocol Group (PPPG) ....................................................... 29-1020
Verifying EPS to MSA Connectivity ..................................................... 29-1023
Troubleshooting Internal Path Integrity Errors (DS1 CST, DS1 DGR, VT1, or
VPG Termination) ......................................................................... 29-1027
Section 8 Troubleshooting VQE and DS0 Grooming

Functionality 29-1033
Troubleshooting VQE Functionality............................................................ 29-1033
Troubleshooting DS0 Functionality ............................................................ 29-1045
Troubleshooting Relational Port Alarming ........................................... 29-1049
Page 29-vi 7/07 76.5500/29, Rev R

Contents Page
Section 9 Isolating Port Group Controller LAN Trouble 29-1059
High Density Port Shelf LAN ...................................................................... 29-1059
Low Density Port Shelf LAN ....................................................................... 29-1066
Performing Preliminary System Checks..................................................... 29-1067
Verifying the Status of the Network and Timing................................... 29-1073
Port Group Controller Failures ................................................................... 29-1076
Single Faulted Port Group Controller................................................... 29-1076
Multiple Faulted Port Group Controllers and Faulted SCM ................. 29-1076
Multiple Faulted Port Group Controllers .............................................. 29-1077
Troubleshooting Port Group Controller LAN Failures ................................ 29-1078
Performing Final System Checks ............................................................... 29-1084
Checking the Status of the System...................................................... 29-1085
Section 10 Clearing Residual Alarms 29-1089

Requirements............................................................................................. 29-1089
System Pre-Checks ................................................................................... 29-1090
Placing the System in Utility Mode............................................................. 29-1095
Clearing Residual Alarms........................................................................... 29-1098
Finalizing Procedure .................................................................................. 29-1100
Section 11 Checking the Power to a Shelf 29-1105

Checking the Power to a LDPS, NC Shelf, or AC Shelf ............................. 29-1106
Checking the Power to an HDPS or a CCSS ............................................. 29-1116
Section 12 Restoring the System 29-1123

System Requirements ................................................................................ 29-1124
Restoring a System Using UM............................................................. 29-1124
Restoring a System Using the CPY-MEM Command.......................... 29-1124
Restoring a System from an SRM ....................................................... 29-1124
Restoring a System from a Remote Server ......................................... 29-1125
Getting Started ........................................................................................... 29-1125
Restoring a System Using Utility Mode (UM) ............................................. 29-1126
Entering UM......................................................................................... 29-1127
Restoring Software on AC-A................................................................ 29-1128
Restoring Software on AC-A from an SRM ......................................... 29-1129
Restoring Software on AC-B from an SRM ......................................... 29-1135
Restoring Software on AC-A from a Remote Server ........................... 29-1144
Restoring Software on AC-B from a Remote Server ........................... 29-1151
Restoring a System Using the CPY-MEM Command ................................ 29-1164
Performing Preliminary System Checks..................................................... 29-1165
Restoring a System from an SRM.............................................................. 29-1167
Restoring a System from a Remote Server ............................................... 29-1170
Completing Restoration.............................................................................. 29-1173
76.5500/29, Rev R 7/07 Page 29-vii

Contents Page
Section 13 TL1 Conditions 29-1177
Fault Hierarchy for Ethernet SST=SENA Conditions ................................. 29-1177
Condition Type Definitions ......................................................................... 29-1177
Network Element Condition Descriptions and Condition Types ................. 29-1178
Network Element Related Condition Descriptions (NE)....................... 29-1178
Administrative Complex Condition Descriptions and Types....................... 29-1178
Administrative Complex Related Condition Descriptions (AC) ............ 29-1178
AC Power Supply Related Condition Descriptions (ACPS) ................. 29-1179
APM Related Condition Descriptions................................................... 29-1179
AIM Related Condition Descriptions .................................................... 29-1179
Hard Disk Related Condition Descriptions (DSM) ............................... 29-1180
Removable Storage Drive Related Condition Descriptions (DSM)...... 29-1180
Removable Media Related Condition Descriptions (REM) .................. 29-1181
Primary Memory Related Condition Descriptions (PRI)....................... 29-1181
Secondary Memory Related Condition Descriptions (SEC) ................ 29-1181
Operation Link Related Condition Descriptions (LINK)........................ 29-1182
Operation Channel Related Condition Descriptions (CHAN)............... 29-1182
SCM-1 Related Descriptions ............................................................... 29-1182
SCM-2 Related Descriptions ............................................................... 29-1183
Central Office (CO) LAN Related Descriptions (LAN-2) ...................... 29-1183
Control LAN Related Descriptions (LAN-1) ......................................... 29-1183
TCPIP Related Descriptions ................................................................ 29-1183
Reference (REF) Related Condition Descriptions ............................... 29-1184
Synchronization Interface Module (SIM) Related Condition
Descriptions ............................................................................ 29-1184
LAN Switch Module (LSM) Related Condition Descriptions ................ 29-1185
LAN Interface Panel (LIP) Related Condition Descriptions ................. 29-1186
Switch Network Complex Condition Descriptions and Types .................... 29-1186
Network Complex Related Condition Descriptions (NC) ..................... 29-1186
Network Group Controller Related Condition Descriptions (NGC) ...... 29-1186
Center Stage Module Related Condition Descriptions (CSM) ............. 29-1187
Center Stage PS Related Condition Descriptions (CSSPS)................ 29-1187
End Stage Module Related Condition Descriptions (ESM).................. 29-1188
End Stage PS Related Condition Descriptions (ESSPS) ................... 29-1189
Network Timing Distributor Related Condition Descriptions (NTDM) .. 29-1189
CSM Adapter Module (CAM) Related Condition Descriptions............. 29-1190
Consolidated Core Switch (CCS) Complex Condition Descriptions and
Types ............................................................................................ 29-1191
Consolidated Core Switch (CCS) Shelf Related Condition
Descriptions ............................................................................ 29-1191
Port Aggregation Module (PAM) Related Condition Descriptions ....... 29-1191
Network Interface Module (NIM) Related Condition Descriptions ....... 29-1192
CCS Group Controller (CGC) Related Condition Descriptions............ 29-1193
Consolidate Core Switch Module (CCSM) Related Condition
Descriptions ............................................................................ 29-1194
Port Complex Condition Descriptions and Types....................................... 29-1195
Port Complex Shelf Related Condition Descriptions (PGCx) .............. 29-1195
Port Group Controller (PGCx) Related Condition Descriptions ........... 29-1196
Port Power Supply (PPS) Related Condition Descriptions .................. 29-1197
DS1 Constituent Term Related Condition Descriptions (DS1 CST) .... 29-1197
DS1 Di-Group Term Related Condition Descriptions (DS1 DGR) ....... 29-1198
DS1 VTCST Term Related Condition Descriptions (DS1 VTCST) ...... 29-1199
DS1 TRMINT Termination Related Condition Descriptions................. 29-1199
Page 29-viii 7/07 76.5500/29, Rev R

Contents Page
DS2 Termination Related Condition Descriptions ............................... 29-1200
DS3 Di-Group Termination Related Condition Descriptions................ 29-1200
DS3 CST Termination Related Condition Descriptions ....................... 29-1201
DS3 TRMINT Termination Related Condition Descriptions................. 29-1202
EC1 Termination Related Condition Descriptions ............................... 29-1203
OCn Termination Related Condition Descriptions ............................... 29-1203
STS3C Termination Related Condition Descriptions........................... 29-1205
STS1 Termination Related Condition Descriptions ............................. 29-1206
VT1 Termination Related Condition Descriptions................................ 29-1207
ETH Termination Related Condition Descriptions ............................... 29-1209
ETHMNG Termination Related Condition Descriptions....................... 29-1209
LAG Related Condition Descriptions ................................................... 29-1209
PPP Termination Related Condition Descriptions ............................... 29-1210
PPPG Related Condition Descriptions ................................................ 29-1210
VCG Related Condition Descriptions................................................... 29-1210
DS1 Port Module Related Condition Descriptions (DS1 PM) ............. 29-1211
DS1 Redundant Port Module (RPM) Related Condition Descriptions . 29-1212
DS3 Port Module Related Condition Descriptions ............................... 29-1213
DS3 Redundant Port Module (RPM) Related Condition Descriptions . 29-1214
STS1E Port Module (PM) Related Condition Descriptions.................. 29-1215
STS1E Redundant (RPM) Port Module Related Condition
Descriptions ............................................................................ 29-1216
Electrical Port Module (EPM) Related Condition Descriptions (EC1
and T3 Combo)....................................................................... 29-1218
Redundant Electrical Port Module (EPM) Related Condition Descriptions
(EC1 and T3 Combo).............................................................. 29-1219
OPMn Related Condition Descriptions ................................................ 29-1220
CCPM Related Condition Descriptions................................................ 29-1221
RCCPM Related Condition Descriptions ............................................. 29-1223
MIM Related Condition Descriptions ................................................... 29-1224
MM Related Condition Descriptions .................................................... 29-1225
RMM Related Condition Descriptions.................................................. 29-1227
Line Interface Module (LIMx) Related Condition Descriptions............. 29-1228
Time Slot Interchange (TSIx) Related Condition Descriptions ............ 29-1229
FPG (OCN Protection Switching) Related Switching Event
Descriptions ............................................................................ 29-1231
CPG (OCN Protection Switching) Related Switching Event
Descriptions ............................................................................ 29-1232
PPG (OCN Protection Switching) Related Switching Event
Descriptions ............................................................................ 29-1234
VPG (OCN Protection Switching) Related Switching Event
Descriptions ............................................................................ 29-1235
Performance Monitoring Related Threshold Crossing Alerts............... 29-1237
Common Condition Descriptions and Types .............................................. 29-1238
FAN Module Related Condition Descriptions ...................................... 29-1238
Air Filter Entity Related Condition Descriptions (FILTER) ................... 29-1238
PT (Pluggable Transceiver) Module Related Condition Descriptions.. 29-1238
Index 29-1241
76.5500/29, Rev R 7/07 Page 29-ix

USER NOTES
TELLABS DOCUMENTATION
Troubleshooting Manual 1. Introduction
1. Introduction
1.01 The Tellabs 5500/5500S Troubleshooting Manual, 76.5500/29, contains

procedures for troubleshooting modules, equipment, and facilities in alarm on a
Tellabs® 5500 digital cross-connect and a Tellabs® 5500S digital cross-connect.
1.02 Troubleshoot alarmed modules, equipment, and facilities by determining
the meaning of alarm messages received. Use the status of the LEDs on the
faulted module as a reference when troubleshooting.
1.03 The information and procedures for troubleshooting the problem occurring
on modules, equipment, and facilities are provided in each separate
troubleshooting section. For procedures to replace faulted equipment or shelves in
the Tellabs 5500/5500S system, refer to Tellabs 5500/5500S Replacement
Procedures, 76.5500/55.
1.04 When troubleshooting the Tellabs 5500/5500S system, always check for
any pertinent Product Performance Notices (PPNs). There may be an issue that
has already been identified that will shorten the time required to troubleshoot the
Tellabs 5500/5500S system.
1.05 FP9.0 introduced two high density port shelves: the High Density-96
Universal Port Shelf (HD-96U) and the High Density-96 Optical Port Shelf
(HD-96O). FP10.0.x introduced three new high density port shelves: the Ethernet
Port Shelf (EPS), the Voice Quality Enhancement Port Shelf (VQEPS), and the
Narrow Band Port Shelf (NBPS).
1.06 FP11.0 introduces the Consolidated Core Switch Shelf (CCSS), which is a
switch-port combination shelf.
1.07 FP11.0.1 introduces the new Circuit Cell Packet Shelf (CCPS), which
contains the 81.5599A Circuit Cell Packet Module (Abis/ATM) (CCPMA).
Note: The High Density Optical Port Shelf, 81.0550H-OPTIC, and the High
Density Universal Port Shelf, 81.0550H-UNIV, support Ethernet,
Narrowband, and VQE functionality.
1.08 Throughout this manual, the pre-FP9.0 port shelves are referred to as the
Low Density Port Shelves (LDPSs), and the HD-96O, HD-96U, EPS, VQEPS,
NBPS, and CCPS are referred to as the High Density Port Shelves (HDPSs).
76.5500/29, Rev R 7/07 Page 29-1

1. Introduction Troubleshooting Manual
1.09 The Tellabs 5500 system recognizes the following HDPS types:
Table 1.1 HDPS Types

Shelf Name Shelf Type
HD-96O UNIV96
HD-96U UNIV96
EPS UETH
VQEPS UVQE
NBPS UNB
CCPS UCC
1.10 If an alarm is being received for a module and the location of that module
is not certain, the OPR-EQPT-LED command can be used to locate the module.
The module locator application allows you to flash the red fault LED on a specific
port or network module to help locate it. When using the OPR-EQPT-LED
command, the supporting Network Group Controller (NGC) or Port Group
Controller (PGC) must be in-service, normal (IS-NR). The module itself must be
equipped. For more information on executing this command, go to Tellabs
5500/5500S Maintenance Manual, 76.5500/24.
1.11 When entering the commands listed in this manual, refer to Tellabs
5500/5500S Command Reference Manual, 76.5500/13, for proper TL1 command
syntax, proper system responses, and an interpretation of error messages. If a
DENY message appears in response to a command, verify the syntax of the
command in Tellabs 5500/5500S Command Reference Manual, 76.5500/13, then
execute it again. If the DENY response still appears, follow your company's
prescribed procedures for obtaining technical assistance or call Tellabs Technical
Assistance at 1.800.443.5555 (North America) or 1.630.798.7070 (outside North
America).
1.12 Throughout this procedure, you will be asked to verify the condition of
various modules. If the modules do not have the same state as those described in
the text, or if a fault LED lights on any module after it has been placed in-service,
the problem must be corrected before continuing. If necessary, follow your
company's prescribed procedures for obtaining technical assistance or call Tellabs
Technical Assistance at 1.800.443.5555 (North America) or 1.630.798.7070
(outside North America).
1.13 Personnel who perform these procedures must have adequate security
clearance in order to perform these commands. They must also have basic
knowledge of the Tellabs 5500/5500S system to follow the procedures.
®
Note: The TITAN 5500 digital cross-connect system has been renamed the
® ®
Tellabs 5500 digital cross-connect and Tellabs 5500S digital
cross-connect. This is a change in the name only. You may see references
® ®
to both the TITAN 5500/S digital cross-connect system and the Tellabs
®
5500 digital cross-connect and Tellabs 5500S digital cross-connect
when doing business with Tellabs. For more information, please visit
http://www.tellabs.com/products.
Page 29-2 7/07 76.5500/29, Rev R

Reason for Issue

1.14 This manual is issued at Revision R to include functionality for Tellabs
5500 system FP11.1.
Tellabs Technical Assistance
Note: If a specific system response or hardware indication does not

appear, stop the procedure. If you cannot resolve a problem, follow your
company's prescribed procedures for obtaining technical assistance or call
Tellabs Technical Assistance at 1.800.443.5555 (North America) or
1.630.798.7070 (outside North America).
1.15 Prepare the following information before calling Tellabs:

• site name and contact
• software version
• size of system
• how much traffic is on the system
76.5500/29, Rev R 7/07 Page 29-3

Conventions Used in This Manual

1.16 Table 1.2 describes the conventions and admonishments used in this
manual.
Table 1.2 Highlights of Syntax Conventions Used in this Manual
Convention Description
Courier font In this document, all TL1 commands and the system responses are shown in Courier.
Note: Provides the user with supplemental information or details.
Caution: Alerts the user to the possibility of service interruption such as a loss of traffic.
Danger: Alerts the user to the possibility of personal injury.
Warning: Alerts the user to the possibility of equipment damage.
Performing Numbered Steps

1.17 Perform all numbered steps in the procedure unless specifically instructed
to skip to another step or procedure.
1.18 The numbered steps in a procedure are usually prefaced with a numbered
paragraph that describes the type of procedure that is to be performed. The
substeps of a numbered step may require you to make a choice before proceeding.
The substeps of a numbered step reflect the number of their parent step. Refer to
Figure 1.1, page 29-5.
Page 29-4 7/07 76.5500/29, Rev R

Figure 1.1 Example of Optional Substeps to a Numbered Step

Numbered paragraphs
describe the type of
procedure that is to 1.19 Review the state of the NCs.
be performed.
Numbered steps
ask the user to __ 1. Verify that the NCs are in-service, normal (IS-NR) by entering the following
perform a function command:
or verify a system RTRV-EQPT::NC-A&&-B:ctag:
response.
System response:
M ctag COMPLD
"NC-A::SIZE=5376,EFSIZE=4608,ESMSIZE=0,MAP=CMM,ALMPF=99
:PST=IS-NR”
"NC-B::SIZE=5376,EFSIZE=4608,ESMSIZE=0,MAP=CMM,ALMPF=99
Substeps indicate :PST=IS-NR”
that the user has a
choice as to what __ 1.1 If the NCs are in-service, normal (IS-NR), go to step 2, page
step will be 39.12.
performed next
depending on the __ 1.2 If the NCs are not in-service, normal (IS-NR), follow your
system response company's prescribed procedures for obtaining technical
received in the assistance or call Tellabs Technical Assistance at
previous step. 1.800.443.5555 (North America) or 1.630.798.7070 (outside
1.20 Sometimes all the substeps of a numbered step must be performed. The
user has no choices. Refer to Figure 1.2.
Figure 1.2 Example of a Step Broken Down Into Substeps

__ 1. Remove the spare DSM by performing the following steps:
__ 1.1 Remove the spare DSM from the AC-B shelf.
Mandatory substeps to a
numbered step. __ 1.2 Label the spare DSM with the FP load and date.
__ 1.3 Place it in an antistatic bag and set it aside.
1.21 Place a check mark on the line beside each step number in a procedure
as you complete it. Then, if a procedure must be interrupted, the place to resume
is clearly indicated. Refer to Figure 1.3, page 29-6.
76.5500/29, Rev R 7/07 Page 29-5

Figure 1.3 Example of a Step With Checkmark Line and Response
__ 1. Place links 1 and link 5 in-service (IS):

After completing a step, ED-LINK::LINK-x:ctag:::IS;
check it off or write down
the time of completion. Where: x = link number.
Command to be entered.
System response:
M ctag COMPLD
Command and System Response Conventions

1.22 In this document, all commands and system responses (ED-EQPT,
COMPLD, etc.) or citations from them are shown in Courier font. Any parts of
commands (or system responses) shown in all UPPERCASE letters are to be
entered (or appear) exactly as shown. Any variables (ctag, time, date, xxxx
[address], etc.) in either commands or responses are shown in lowercase.
1.23 The responses included in this document are typical system responses
similar to what actually displays. Any command with a variable is followed by a
“where” line that explains what must be entered at that point. Any specific
information for a response is noted in these instructions.
1.24 The system responses show sample SDF numbers that may not match
those in your system. The sample SDF numbers show a realistic range of numbers
for each type of module or entity specified in the command. Replace the variables
in the “where” statements with the information specific to your system and
requirements, including SDF numbers where applicable.
Table 1.3 Conventions Used in System Responses to Commands

Element Explanation of System Response Element
ctag Correlation tag. Identifies the user who entered the command. Usually the user’s initials.
user_id User’s login name/identifier.
system_id Site ID of the system.
yymmdd Date: year, month, day. Example: 961120 (November 20, 1996)
hh-mn-ss Time: hour-minute-second (24-hour clock) Example: 18-59-29
hh-mn hour-minute (24-hour clock) Example: 18-59
Rx Revision level of the hardware module, where x = A-ZZ.
Sn=n Serial number, where n=n represents the serial number of the hardware module.
COMPLD M ctag COMPLD = Completed. Command has been accepted by system. The system
may display “COMPLD” before the command is fully processed.
RTRV Retrieval of ranges of equipment returns M ctag RTRV instead of M ctag COMPLD.
IP In progress. If system cannot respond within two seconds of the command entry, then the
“IP” response repeats every 90 seconds until the command is completed.
DENY The input command was denied. An error code displays on the following line indicating
the reason for denial—usually a mistake in command syntax.
Page 29-6 7/07 76.5500/29, Rev R

Table 1.3 Conventions Used in System Responses to Commands (Continued)

Element Explanation of System Response Element
PRTL Partial. Action requested by a ranged command has been partially completed.
ALMPF=nn Alarm Profile number, where nn = 0, 1 - 20, or 99, where 0 and 99 are defaults and 1 - 20
are user-defined values.
SIZE=pppp Size of the system, where pppp = the number of ports from 128 in a Tellabs 5500S
system to 5376 in a fully expanded Tellabs 5500 system. Initial zeroes are not returned in
TL1: SIZE=256 (not 0256).
TMG=[MSTR/SLV] Square brackets “[ ]” are not part of the command syntax and do not display on the
screen.
They enclose all acceptable values for a given command or response parameter. In this
example, master and slave are the possible values for TMG (timing).
TL1 Command Language

1.25 This manual assumes that the user has some familiarity with the TL1
Command Language used by the Tellabs 5500/5500S systems. Tellabs
5500/5500S Command Reference Manual, 76.5500/13, provides a thorough
introduction to the command syntax, system responses, and error codes for
individual commands.
1.26 Take a moment to review these features of TL1 commands:
• TL1 commands are not case sensitive. The system does not
distinguish between capital and lowercase letters. (Utility mode
passwords are not part of TL1—they are case sensitive.)
• A semicolon (;), not the Enter or RETURN key, always is the final
character that executes the command.
• The semicolon (;) also serves as a prompt. It appears at the end of the
command and indicates the system is ready for the next command.
• M ctag COMPLD is the normal system response to a correctly entered

command. The “M ctag COMPLD” does not always appear at the end
of the system response. It may appear in the midst of the response
displayed on the screen or printed.
• M ctag RTRV is the normal response to a RTRV command that

retrieves a range of equipment addresses.
• The system displays the “Header” line (system ID, date, and time
stamp) with the COMPLD/RTRV line.
1.27 Some TL1 commands produce responses that are too long to fit on one
screen. Before starting this procedure, create a log file or attach a printer to the
system to capture all commands and responses. Use the log file or paper copy for
reference while performing this procedure.
76.5500/29, Rev R 7/07 Page 29-7

Abbreviations
1.28 Table 1.4 lists abbreviations used in this manual
Table 1.4 Abbreviations Used in this Manual

Abbreviation Definition
AC Administrative Complex
AC-[A/B] AC copy A or B
ACT Active
ANR Abnormal
AS Assigned
CCPMA Circuit Cell Packet Module (Abis/ATM))

CCPS Circuit Cell Packet Shelf
CCSM Consolidated Core Switch Module
CCSS Consolidated Core Switch Shelf

CCS Shelf Consolidated Core Switch Shelf
CGCM Consolidated Group Controller Module
CPG STS-3c Path Protection Group
CST Constituent
DGR Digroup
EPS Ethernet Port Shelf
ETH Ethernet termination
EQ Equipped
FPG Facility Protection Group
HD-96O High Density Port Shelf Optical (shelf populated with OPMs
only)
HD-96U High Density Port Shelf Universal (shelf populated with a mix
of OPMs and EPMs)
HDPS High Density Port Shelf

IS In-service
LAG Link Aggregation Group
LAPS Linear Automatic Protection Switching
LDPS Low Density Port Shelf
LED Light Emitting Diode
NBPS Narrow Band Port Shelf

NC Network Complex
Page 29-8 7/07 76.5500/29, Rev R

Table 1.4 Abbreviations Used in this Manual (Continued)

Abbreviation Definition
NE Network Element
NGC Network Group Controller (module)

NIM Network Interface Module
NR Normal
OCN Optical Carrier level N
OD Optical disk
OOS Out-of-service
PAM Port Aggregation Module
PGC Port Group Controller
PPG STS-1 Path Protection Group
PPP Point-to-Point Protocol
PPPG Point-to-Point Protocol Group
PRI Primary Memory
REMV Removable media = optical disk or flash card
SDF System Data Format: Tellabs proprietary digital signal used

internally to Tellabs 5500. Equals a DS3 plus overhead.
SEC Secondary Memory
STBY Standby
STS Synchronous Transport Signal
UPSR Unidirectional Path Switched Rings
VPG VT1 Path Protection Group
VQE Voice Quality Enhancement
VQEPS VQE Port Shelf
VT Virtual Tributary
UEQ Unequipped
UAS Unassigned
76.5500/29, Rev R 7/07 Page 29-9

Fiber Optic Safety

1.29 Read the following information about fiber optic safety before installing and
operating the Tellabs 5500/5500S system:
• Laser
• Safety Precautions
• Optical Fiber Handling, page 29-11
Laser
1.30 The Tellabs 5500/5500S system and associated optical test sets use
semiconductor laser sources that emit light energy into fiber or lightguide cables.
The lasers emit lightwaves within the infrared (invisible) wavelengths.
1.31 The level of laser radiation emitted from the transmitters of this product are
not considered to be hazardous; however, the level of radiation that may be emitted
from a disconnected optical facility receive cable may be harmful to the eye. As a
general practice, do not look into the end of optical disconnects.
1.32 Laser products are subject to international, federal, state, and local
regulations. The Tellabs 5500 system complies with USA Code of Federal
Regulations (CFR), Title 21, Subchapter J, Part 1040.10, Performance Standards
for Light-Emitting Products, as a class 1 laser product.
Safety Precautions
1.33 Only qualified technicians who are knowledgeable and trained in optical
safety hazards can operate, maintain, install, and service the Tellabs 5500 system.
1.34 Optical radiation originates from the optical connectors, or in the case of
cable rupture, the optical fiber ends.
DANGER:
When inspecting optical fibers or connectors, always use protected optical
viewing aids. For example, fiber scopes and magnifying glasses must be
equipped with protective filters. Use laser safety glasses that are equipped to
protect against all possible wavelength ranges emitting from the equipment.
DANGER:
The power level of the visible and invisible laser radiation emitted from an
unconnected facility fiber optical cable is not under Tellabs’ control and may be
dangerous. Therefore, to ensure safety, assume that it is dangerous to your
eyesight. As a general practice, NEVER LOOK INTO ANY OPEN OPTICAL
PORT OR END OF A DISCONNECTED OPTICAL CABLE.
Page 29-10 7/07 76.5500/29, Rev R

DANGER:
Do not examine fiber optic cables when there is a light source present. Before
examining fiber optic cables with unfiltered magnifying lenses or microscopes,
perform the following actions to prevent accidental exposure to optical radiation:
• perform the necessary steps to disable the laser source of the fiber
to be examined
• disconnect the optical path from all relevant optical modules
Turning off a laser source in the Tellabs 5500 system disrupts traffic.
1.35 The optical sources for the Tellabs 5500/5500S system include the
following semiconductor lasers. The laser classification is the USA Center for
Devices and Radiological Health (CDRH) title 21, Code of Federal Regulations
(CFR) Chapter 1, Subchapter J, Parts 1040.1.
• 850 nm semiconductor LED
• 1310 nm semiconductor laser (class 1)
Optical Fiber Handling

1.36 Optical fibers can break into small glass fragments during handling. These
small bits of glass are almost invisible and can cause physical injury.
DANGER:
Fiber glass fragments can enter the skin and be very difficult to detect and
remove. Do not handle exposed optical fiber with bare hands or touch it to your
body. If there is any suspicion of glass fiber chips in your eye, seek medical
attention at once.
1.37 To perform procedures other than those specified in the Tellabs

5500/5500S documents can result in hazardous radiation exposure.
76.5500/29, Rev R 7/07 Page 29-11

1.38 Follow these precautions to prevent physical injury when handling optical
fiber:
1. Avoid looking directly at the fiber connectors.
2. If it is required to look at the connectors, perform one of the following

actions to prevent any hazard:
a. Remove the optical modules or ensure the optical modules are not
powered at both the shelf near end and shelf at the fiber path far
end.
b. Wear protective glasses that block all possible wavelength ranges
emitting from the equipment.
3. Wear laser safety glasses when installing optical fibers.
4. Wash your hands after handling optical fibers.
5. Handle optical fibers with extreme care during installation and position
the optical fibers in a safe and secure location.
6. Protect unterminated optical fiber connectors with dust caps at all

times.
7. Perform the necessary steps to disable the laser source, unplug

optical modules, and disconnect optical paths when using magnifying
lenses or microscopes.
Page 29-12 7/07 76.5500/29, Rev R

Removing Modules
1.39 Refer to the following procedures to remove a module, depending on the
module type:
• To remove a DS1 PM, DD DS1 PM, DS3 PM, or MM go to Module
Removal, page 29-14.
• To remove an EPM, MM24, MM24E, MM24V, MM24VE, MM24NB, or

MIM96, go to High Density Module Removal, page 29-15.
• To remove a MIM96E, go to MIM96E Module Removal, page 29-16.
• To remove an OPM3, go to OPM3 Removal, page 29-19.
• To remove an OPM3X8, go to OPM3X8 Removal, page 29-20.
• To remove an OPM12X4, go to OPM12X4 Removal, page 29-25.
• To remove a CCPMA, go to CCPMA Removal, page 29-33.
• To remove a Consolidated Core Switch Shelf module, go to

Consolidated Core Switch Shelf Module Removal, page 29-36.
• To remove a CSM Adapter Module, go to CAM Removal, page 29-31.
• To remove a LAN Switch Module, go to LAN Switch Module (LSM)

Removal, page 29-40.
76.5500/29, Rev R 7/07 Page 29-13

Module Removal
1.40 To remove a faulted DS1 PM, DD DS1 PM, DS3 PM, or MM perform the
following steps.
__ 1. Locate the faulted module on the port shelf.
__ 2. Release the locks on the module by performing the following two
operations at the same time.
__ 2.1 On the top lock, while pushing down on the safety clip,
lift up on the ejector clip with sufficient force to unlock
the module.
__ 2.2 On the bottom lock, while lifting up on the safety clip,

push down on the ejector clip with sufficient force to
unlock the module. Refer to Figure 1.4.
__ 3. Slowly slide the module out of the shelf.

__ 4. Place the module in an anti-static bag and put it in a safe place.
Figure 1.4 Module Removal Method
Page 29-14 7/07 76.5500/29, Rev R

High Density Module Removal

1.41 To remove a faulted EPM, MM24E, MM24V, MM24VE, MM24NB, or
MIM96, perform the following steps.
__ 1. Locate the module on the port shelf.
__ 2. Identify the ejectors and locking clips at the top and bottom of the
module front panel. Refer to Figure 1.5.
Figure 1.5 Ejector and Locking Clip Positions
ejector ejector
locking clip locking clip
in locked in unlocked
position position ejector in
open
position
__ 3. Using both hands, perform the following two operations at the same
time. Refer to Figure 1.6, page 29-15.
- With the thumb and index finger of one hand, pull the top locking
clip forward against ejector until the clip is in the unlocked position,
then pull the ejector up to the open position.
- With the thumb and index finger of the other hand, pull the bottom
locking clip forward against ejector until the clip is in the unlocked
position, then pull the ejector down to the open position.
__ 4. Use the ejectors to slowly pull the module out of the slot.
76.5500/29, Rev R 7/07 Page 29-15

MIM96E Module Removal

1.42 To remove a faulted MIM96E, perform the following steps.
__ 2. Disconnect the Ethernet management cable from the Ethernet
management port (RJ45 connector). Refer to Figure 1.7, page 29-17.
__ 3. Disconnect the transmit and receive facility fibers from the four
pluggable transceivers (PTs) on the MIM96E.
__ 4. If necessary, remove the four PTs from the MIM96E and place them in
anti-static bags.
Page 29-16 7/07 76.5500/29, Rev R

Figure 1.7 MIM96E Ethernet Management Cable and Facility Fiber Locations
81.5597E
MIM96E
REV. A
power
active
fault
active
data
mng
mng
fac
Pt -4
Pt -3
Pt -2
Pt -1
Flt Fac
management port
RJ45
GbE facility port 4

pluggable transceiver
GbE facility port 3

GbE facility port 2

GbE facility port 1

76.5500/29, Rev R 7/07 Page 29-17

ejector ejector
open
position
time. Refer to Figure 1.9.
Page 29-18 7/07 76.5500/29, Rev R

OPM3 Removal
1.43 To remove a faulted OPM3, perform the following steps.
__ 2. On the bottom lock, while lifting up on the safety clip, push down on
the ejector clip with sufficient force to unlock the module. Refer to
Figure 1.10.
DANGER:
Disconnected optical connectors may emit invisible optical radiation that may
cause injury. Avoid direct eye exposure to the beam. Do not stare into the beam.
Do not view beam with optical instruments.
__ 3. Slowly slide the module out of the shelf until it reaches the module
stop.
__ 4. Disconnect the transmit and receive connector couplers from the
module. Refer to Figure 1.11, page 29-20.
__ 5. Slide the module past the module stop by pushing in on the retaining
clip long enough to pull the module past the module stop, then release
the retaining clip once the module has passed the module stop. Refer
to Figure 1.11, page 29-20.
76.5500/29, Rev R 7/07 Page 29-19

Figure 1.11 OPM3 Side View
fiber cable guide
OC-3 RECEIVE
connector coupler
OC-3 TRANSMIT
connector coupler
module stop
(Press to Release Module)
Press to
Release
cable attachment position
OPM3X8 Removal
1.44 To remove a faulted OPM3X8 perform the following steps.
__ 2. Remove the eight connectors on the front of the OPM3X8, slide the
optical facility fibers from the OPM3X8, and attach fiber dust protectors
to the ends of the optical facility fibers. Refer to Figure 1.12,
page 29-21.
DANGER:
Looking into the end of an optical cable or connector can cause eye damage.
Do not look into the end of an optical cable or connector, either directly or
through an optical instrument.
The power level of the invisible laser radiation emitted from an unconnected
optical facility receive cable is not under Tellabs’ control and may be dangerous.
Therefore, to ensure safety, assume that it is dangerous to your eyesight.
Page 29-20 7/07 76.5500/29, Rev R

Figure 1.12 OPM3X8 Facility Fiber Locations
81.5592A/B
OPM3X8
REV. A
12/02
CAUTION
DISCONNECT FIBER
OPTIC CABLES
BEFORE FULLY
REMOVING MODULE
FAC/ALM
8
7
6
5
4
3
2
1
power
active
fault
XMT - 8
RCV - 8
XMT - 7
RCV - 7
XMT - 6
RCV - 6
XMT - 5
facility fiber connections
RCV - 5
XMT - 4
RCV - 4
XMT - 3
RCV - 3
XMT - 2
RCV - 2
XMT - 1
RCV - 1
module front panel. Refer to Figure 1.13, page 29-22.
76.5500/29, Rev R 7/07 Page 29-21

ejector ejector
open
position
clip forward against the ejector until the clip is in the unlocked
position; then pull the ejector up to the open position.
locking clip forward against the ejector until the clip is in the
unlocked position; then pull the ejector down to the open position.
__ 5. Grasp the ends of both levers and slowly pull the module toward you
and out of the port shelf.
Page 29-22 7/07 76.5500/29, Rev R

OPM12 Removal
1.45 To remove a faulted OPM12, perform the following steps:
__ 2. Release the locks on the module ejectors by performing the following
two operations at the same time.
- On the top lock, while pushing down on the safety clip, lift up on
the ejector clip with sufficient force to unlock the module.
- On the bottom lock, while lifting up on the safety clip, push down
on the ejector clip with sufficient force to unlock the module. Refer
to Figure 1.15.
DANGER:
__ 3. Slowly slide the module out of the shelf until it reaches the module
stop.
__ 4. Disconnect the transmit and receive connector couplers from the
module. Refer to Figure 1.16, page 29-24.
76.5500/29, Rev R 7/07 Page 29-23

__ 5. Slide the module past the module stop by pushing in on the retaining
clip long enough to pull the module past the module stop, then release
the retaining clip once the module has passed the module stop. Refer
to Figure 1.16.
Figure 1.16 OPM12 Side View
fiber cable guide
OC-12 RECEIVE
connector coupler
OC-12 TRANSMIT
connector coupler
module stop
(Press to Release Module)
Press to
Release
cable attachment position
Page 29-24 7/07 76.5500/29, Rev R

OPM12X4 Removal
1.46 To remove a faulted OPM12X4, perform the following steps.
__ 2. Depending on the type of connector used on the module (FC, SC, or
ST), perform one of the following substeps. Refer to Figure 1.17,
page 29-26.
__ 2.1 For an FC or ST connector, unscrew the connector,
slide the optical facility fiber from the OPM12X4, and
attach a fiber dust protector to the end of the optical
facility fiber. Repeat for all optical facility fibers on the
OPM12X4.
__ 2.2 For an SC connector, pull back the connector, slide the

optical facility fiber from the OPM12X4, and attach a
fiber dust protector to the end of the optical facility fiber.
Repeat for all optical facility fibers on the OPM12X4.
DANGER:
76.5500/29, Rev R 7/07 Page 29-25

Figure 1.17 OPM12X4 Facility Fiber Locations
81.5593A/B
OPM12X4
REV. A
12/02
FAC/ALM
POWER
ACTIVE
FAULT
CAUTION:
Disconnect fiber
cables
XMT - 4
RCV - 4
XMT - 3
RCV - 3
XTM - 2
RCV - 2
XMT - 1
RCV - 1
CLEI BAR CODE
Page 29-26 7/07 76.5500/29, Rev R

ejector ejector
open
position
76.5500/29, Rev R 7/07 Page 29-27

OPM48 Removal
1.47 To remove a faulted OPM48, perform the following steps.
__ 2. Disconnect the transmit and receive facility fibers from the pluggable
transceivers (PT) of the OPM48. Refer to Figure 1.20, page 29-29.
__ 3. If necessary, remove the PT from the OPM48 and place it in an
anti-static bag.
DANGER:
Page 29-28 7/07 76.5500/29, Rev R

Figure 1.20 OPM48 Facility Fiber Locations
81.5594B
OPM48
REV. A
8/06
Pt-1
Flt Fac
power
active
fault
Caution:
Disconnect fiber cables
before fully removing
modules
CLEI BAR CODE
76.5500/29, Rev R 7/07 Page 29-29

ejector ejector
open
position
Page 29-30 7/07 76.5500/29, Rev R

CAM Removal
1.48 To remove a faulted CSM Adapter Module (CAM), perform the following
steps.
__ 2. Disconnect the transmit and receive facility fibers from the CAM. Refer
to Figure 1.23.
Figure 1.23 CAM Facility Fiber Locations
CAM
81.55108
facility fiber cables
active
fault
Rcv-2
Rcv-1
SDF
static
sensitive
76.5500/29, Rev R 7/07 Page 29-31

ejector ejector
open
position
Page 29-32 7/07 76.5500/29, Rev R

CCPMA Removal
1.49 To remove a faulted CCPMA, perform the following steps:
__ 2. Remove the Ethernet cable from the MNG connector on the module
front panel. Refer to Figure 1.26, page 29-34.
76.5500/29, Rev R 7/07 Page 29-33

Figure 1.26 CCPMA MNG Fiber Location
CCPMA
81.5599A
REV. A
power
active
fault
MNG
link
activity
Ethernet connector
Page 29-34 7/07 76.5500/29, Rev R

ejector ejector
open
position
1.50 Place the module in an anti-static bag and put it in a safe place.
76.5500/29, Rev R 7/07 Page 29-35

Consolidated Core Switch Shelf Module Removal

1.51 Follow the procedures in this section to remove a module from a
Consolidated Core Switch Shelf.
CCSM and CGCM Removal
Caution:
In order to maintain proper air flow, insert a filler module into any unused slots in
the CCS shelf.
1.52 To remove a faulted Consolidated Core Switch Module (CCSM) or

Consolidated Core Group Controller Module (CGCM), perform the following steps.
ejector ejector
open
position
time. Refer to Figure 1.30, page 29-37.
Page 29-36 7/07 76.5500/29, Rev R

NIM and PAM Removal
Caution:
the CCS shelf.
1.53 To remove a faulted Network Interface Module (NIM) or Port Aggregation

Module (PAM), perform the following steps.
__ 2. Disconnect the transmit and receive facility fibers from the eight
pluggable transceivers (PTs) on the NIM or PAM. Refer to Figure 1.31,
page 29-38.
DANGER:
76.5500/29, Rev R 7/07 Page 29-37

Figure 1.31 NIM and PAM Facility Fiber Locations
Pt-8
Pt-7
Pt-6
Pt-5
Pt-4
Pt-3
Pt-2
Pt-1
Flt SDF
ejector ejector
open
position
Page 29-38 7/07 76.5500/29, Rev R

1.54 Place the module in an anti-static bag and put it in a safe place.
76.5500/29, Rev R 7/07 Page 29-39

LAN Switch Module (LSM) Removal

1.55 To remove a faulted LAN Switch Module (LSM), perform the following
steps.
__ 1. Disconnect the LSM to APM LAN jumper cable from the RJ45 con-
nector on the front panel. Refer to Figure 1.34, page 29-40.
Figure 1.34 LSM to APM LAN Jumper Location
LSM
81.55103
LIP fault
in service
active
fault
LAN jumper cable
static
sensitive
Page 29-40 7/07 76.5500/29, Rev R

__ 2. Perform the following two operations at the same time. Refer to

Figure 1.35.
- With the thumb and index finger of one hand, squeeze the lever
and locking hook of the top ejector together, until the module
unlocks at the top.
- With the thumb and index finger of the other hand, squeeze the
lever and locking hook of the bottom ejector together, until the
module unlocks at the bottom.
__ 3. Grasp the ends of both levers and slowly pull the module out of the
slot.
76.5500/29, Rev R 7/07 Page 29-41

Synchronization Cables
1.56 Refer to the following sections for information about the synchronization
cables used in Standard Core Switch, Hybrid Core Switch, and Consolidated Core
Switch configurations.
Standard Core Switch Synchronization Timing Cables

1.57 The cables required depend on the AC backplane connectors. For AC
shelves revision B through I use the following cable types:
• For Rev B through I backplanes, in 256 or 1024 systems, use four
Shielded Data Link (SDL) to NTDM cables. The cables are Tellabs
part number 50.156xx or 50.158xx (where xx is the length in feet).
• For Rev B through I backplanes in a 1536, 2048, or 3072 system, refer

to Table 1.5.
Table 1.5 SYNC Cables for AC Shelves Rev B through I in a

1536, 2048, or 3072 System
Administrative Network
Complex Complex Color Coding Part Number
SYNC A NC-A
J37 SYNC A red label 50.2190
J3
SYNC A NC-B
J36 SYNC A white label 50.2191
J3
SYNC B NC-A
J37 SYNC B yellow label 50.2192
J4
SYNC B NC-B
J36 SYNC B black label 50.2193
J4
Page 29-42 7/07 76.5500/29, Rev R

AC Shelves Revision J and 1.58 For AC shelves revision J and later, use the following cable types:
Later
• For Rev J or Later backplanes in a 128, 256, or 1024 system, use at
least four SYNC cables. Refer to Table 1.6.
Table 1.6 SDL to Twinax SYNC Cables for AC Shelves Rev J or Later in a 128, 256, or 1024 System
Shelf Cable Length Part Labels
AC-A AC-A J37 to 8 feet 50.21201
NC-A J3
10 feet 50.21202
red
20 feet 50.21203
SYNC CABLE SYNC CABLE
30 feet 50.21204 NETWORK COPY A ADMIN COPY A
J3 (SIM A) J37
40 feet 50.21205
50 feet 50.21206
AC-A J36 to 8 feet 50.21207
NC-B J3
10 feet 50.21208
white
20 feet 50.21209
30 feet 50.21210 NETWORK COPY B ADMIN COPY A
J3 (SIM A) J36
40 feet 50.21211
50 feet 50.21212
AC-B AC-B J37 to 8 feet 50.21213
NC-A J4
10 feet 50.21214
yellow
20 feet 50.21215
30 feet 50.21216 NETWORK COPY A ADMIN COPY B
J4 (SIM B) J37
40 feet 50.21217
50 feet 50.21218
AC-B J36 to 8 feet 50.21219
NC-B J4
10 feet 50.21220
black
20 feet 50.21221
30 feet 50.21222 NETWORK COPY B ADMIN COPY B
J4 (SIM B) J36
40 feet 50.21223
50 feet 50.21224
76.5500/29, Rev R 7/07 Page 29-43

• For Rev J or Later backplanes in a 1536, 2048 or 3072 system, use at

least four SYNC cables. Refer to Table 1.7 for available 100-foot
cables.
Table 1.7 SYNC Cables for AC Shelves Rev J or Later in a 1536,

2048, or 3072 System with a Standard Core Switch
AC-A NC-A
SYNC A SYNC A red label 50.2196
J37 J3
AC-A NC-B
SYNC A SYNC A white label 50.2197
J36 J3
AC-B NC-A
SYNC B SYNC B yellow label 50.2198
J37 J4
AC-B NC-B
SYNC B SYNC B black label 50.2199
J36 J4
Page 29-44 7/07 76.5500/29, Rev R

Hybrid Consolidated Core Switch Synchronization Timing Cables
Table 1.8 SDL to Twinax SYNC Cables for AC Shelves Rev J or Later to NC Shelves
AC
Shelf Part
Copy Cable Length Number Labels

NC-A J3
10 feet 50.21202
red
20 feet 50.21203
J3 (SIM A) J37
40 feet 50.21205
50 feet 50.21206
AC-A J36 to 8 feet 50.21207
NC-B J3
10 feet 50.21208
white
20 feet 50.21209
J3 (SIM A) J36
40 feet 50.21211
50 feet 50.21212
NC-A J4
10 feet 50.21214
yellow
20 feet 50.21215
J4 (SIM B) J37
40 feet 50.21217
50 feet 50.21218
AC-B J36 to 8 feet 50.21219
NC-B J4
10 feet 50.21220
black
20 feet 50.21221
J4 (SIM B) J36
40 feet 50.21223
50 feet 50.21224
76.5500/29, Rev R 7/07 Page 29-45

Table 1.9 SDL to Twinax SYNC Cables for NC to LTIP Connections

NC-A NC-A J1 to 50 feet 50.21230
to LTIP-1 J2
LTIP-1 SYNC CABLE SYNC CABLE
NC COPY A LTIP COPY 1 (A)
J1 J2
NC-A J2 to 50 feet 50.21236

LTIP-1 J1
J2 J1
NC-B NC-B J1 to 50 feet 50.21243

to LTIP-2 J2
NC COPY B LTIP COPY 2 (B)
J1 J2
NC-B J2 to 50 feet 50.21249

LTIP-2 J1
J2 J1
Table 1.10 Twinax to Twinax SYNC Cables for AC Shelves Rev

J or Later
AC-A NC-A
J37 J3
AC-A NC-B
J36 J3
AC-B NC-A
J37 J4
AC-B NC-B
J36 J4
Page 29-46 7/07 76.5500/29, Rev R

Table 1.11 Twinax to Twinax Sync Cables for the AC Shelves Rev
J or Later to the LTIPs in a 256 or 1024 Size System
Shelf Cable Length Part Number
AC-A to AC-A J35 to 50 feet 150.2506

LTIP-1 LTIP-1 J3
red
AC-A to AC-A J34 to 150.2517

LTIP-2 LTIP-2 J3
white
AC-B to AC-B J35 to 150.2528

LTIP-1 LTIP-1 J4
yellow
AC-B to AC-B J34 to 150.2539

LTIP-2 LTIP-2 J4
black
J or Later to the LTIPs in a 1536, 2048, or 3072 Size System

LTIP-1 LTIP-1 J3
red
AC-A to AC-A J34 to 150.2522

LTIP-2 LTIP-2 J3
white
AC-B to AC-B J35 to 150.2533

LTIP-1 LTIP-1 J4
yellow
AC-B to AC-B J34 to 150.2544

LTIP-2 LTIP-2 J4
black
76.5500/29, Rev R 7/07 Page 29-47

Consolidated Core Switch with DS1 Support Synchronization Timing Cables
Table 1.13 SDL to Twinax SYNC Cables for AC Shelves Rev J or Later to NC Shelves
AC
Shelf Part

NC-A J3
10 feet 50.21202
red
20 feet 50.21203
J3 (SIM A) J37
40 feet 50.21205
50 feet 50.21206
AC-A J36 to 8 feet 50.21207
NC-B J3
10 feet 50.21208
white
20 feet 50.21209
J3 (SIM A) J36
40 feet 50.21211
50 feet 50.21212
NC-A J4
10 feet 50.21214
yellow
20 feet 50.21215
J4 (SIM B) J37
40 feet 50.21217
50 feet 50.21218
AC-B J36 to 8 feet 50.21219
NC-B J4
10 feet 50.21220
black
20 feet 50.21221
J4 (SIM B) J36
40 feet 50.21223
50 feet 50.21224
Page 29-48 7/07 76.5500/29, Rev R


to LTIP-1 J2
J1 J2
NC-A J2 to 50 feet 50.21236

LTIP-1 J1
J2 J1

to LTIP-2 J2
J1 J2
NC-B J2 to 50 feet 50.21249

LTIP-2 J1
J2 J1

LTIP-1 LTIP-1 J3
red
AC-A to AC-A J34 to 150.2517

LTIP-2 LTIP-2 J3
white
AC-B to AC-B J35 to 150.2528

LTIP-1 LTIP-1 J4
yellow
AC-B to AC-B J34 to 150.2539

LTIP-2 LTIP-2 J4
black
76.5500/29, Rev R 7/07 Page 29-49


LTIP-1 LTIP-1 J3
red
AC-A to AC-A J34 to 150.2522

LTIP-2 LTIP-2 J3
white
AC-B to AC-B J35 to 150.2533

LTIP-1 LTIP-1 J4
yellow
AC-B to AC-B J34 to 150.2544

LTIP-2 LTIP-2 J4
black
Table 1.17 Twinax to Twinax SYNC Cables for NC to LTIP Connections

NC-A NC-A J1 to 100 feet 150.2555
to LTIP-1 J2
LTIP-1 NC-A1 LTIP-1A
NC COPY A LTIP COPY 1(A)
J1 J2
NC-A J2 to 100 feet 150.2566

LTIP-1 J1
NC-A1 LTIP-1A
NC COPY A LTIP COPY 1(A)
J2 J1
NC-B NC-B J1 to 100 feet 150.2577

to LTIP-2 J2
LTIP-2 NC-B2 LTIP-2B
NC COPY B LTIP COPY 2(B)
J1 J2
NC-B J2 to 100 feet 150.2588

LTIP-2 J1
NC-B2 LTIP-2B
NC COPY B LTIP COPY 2(B)
J2 J1
Page 29-50 7/07 76.5500/29, Rev R

Consolidated Core Switch without DS1 Support Synchronization Timing Cables

LTIP-1 LTIP-1 J3
red
AC-A to AC-A J34 to 150.2517

LTIP-2 LTIP-2 J3
white
AC-B to AC-B J35 to 150.2528

LTIP-1 LTIP-1 J4
yellow
AC-B to AC-B J34 to 150.2539

LTIP-2 LTIP-2 J4
black

LTIP-1 LTIP-1 J3
red
AC-A to AC-A J34 to 150.2522

LTIP-2 LTIP-2 J3
white
AC-B to AC-B J35 to 150.2533

LTIP-1 LTIP-1 J4
yellow
AC-B to AC-B J34 to 150.2544

LTIP-2 LTIP-2 J4
black
76.5500/29, Rev R 7/07 Page 29-51

USER NOTES
Page 29-52 7/07 76.5500/29, Rev R

Troubleshooting Manual 2. Troubleshooting the Administrative Complex
2. Troubleshooting the Administrative Complex
2.01 This section contains procedures to troubleshoot the problem occurring on

the following faulted modules or equipment:
• Administrative Complex Power Supply Module (ACPS)
• System Processor Module (SPM)
• Synchronous Interface Module (SIM)

• Timing Reference (REF)
• Alarm Indicator Module (AIM)
• System Communications Module (SCM-1 and SCM-2)
• LAN Switch Module (LSM)

• Local Area Network (LAN)
• Primary Memory (PRI)
• Secondary Memory (SEC)
• Single Removable Media (SRM)
• Link (LINK) or Channel (CHAN)
2.02 When troubleshooting the Administrative Complex (AC), always check for
AC.
2.03 The SPM replaces the Administrative Processor Module (APM). The SPM
must be 128M.
Note: Beginning with FP11.0 in the Tellabs 5500 system, the 5501B/C System
Processor Module (SPM) no longer functions as the Communications
Processor Module (CPM) in slot 3 of the AC shelf. The 81.55103 LAN
Switch Module (LSM) now functions as the CPM. The LSM provides the
LAN interfaces for the Consolidated Core Switch (CCS), CO LAN to
communicate with the SPM in the APM slot, and TCP/IP functions for the
system.
2.04 Use the status of the LEDs on the faulted module as a reference in
troubleshooting the Administrative Complex. Refer to Status of the LEDs on a
Faulted Module, page 29-54.
command, the supporting network group controller (NGC) or port group controller
(PGC) must be in-service, normal (IS-NR). The module itself must be equipped.
For more information on executing this command, go to Tellabs 5500/5500S
Maintenance Manual, 76.5500/24.
76.5500/29, Rev R 7/07 Page 29-53

2. Troubleshooting the Administrative Complex Troubleshooting Manual
Note: In a Tellabs 5500 system with a Consolidated Core Switch Shelf, the
backplane of the administrative complex must be Rev. J or higher.
2.06 On-site personnel are required to successfully complete this procedure.
Warning:
Electrostatic discharge (ESD) may damage sensitive electronic components
resulting in a traffic-affecting condition. Ensure that plug-in modules are stored
in static preventive material. Do not touch any components on the modules.
Handle modules by the edges or front panel. Always wear a properly grounded
wrist strap when handling, removing, or inserting a module and when touching
the equipment shelves or cables. ESD protective flooring, used with proper ESD
footwear, may be used as an alternative to a wrist strap. ESD wrist straps and
footwear should be checked daily to verify performance.
Hardware Requirements
2.07 A spare module may be required to perform this procedure. Therefore, it is
advised to obtain a spare module before starting this procedure. Refer to Tellabs
5500/5500S Software Release Document, 76.5500/16, to verify the correct
revision level of the module needed, depending on feature package and what shelf
type you are troubleshooting.
Status of the LEDs on a Faulted Module

2.08 Figures 2.1, page 29-55, through Figure 2.6, page 29-61, are for
reference only. Use these figures as an aid in troubleshooting the alarmed
Administrative Complex.
2.09 To troubleshoot the faulted module or equipment, go to Determining the
Meaning of Alarm Messages, page 29-73.
Page 29-54 7/07 76.5500/29, Rev R

Administrative Complex Figure 2.1 Administrative Complex Power Supply Module LEDs
Power Supply Module LEDs
PSAC
power
Table 2.1 Status of Administrative Complex Power Supply Module LEDs
Status of
LEDs Meaning Notes
Power ON Normal state; the module is operational.
Power OFF - Failed or faulted module.

- No power, not in slot, breaker OFF, bent pin(s) on
backplane connector.
76.5500/29, Rev R 7/07 Page 29-55

Administrative Processor Figure 2.2 Administrative Processor Module LEDs

Module LEDs
WARNING:
Follow replacement procedure for
this module prior to removal.
SPM
81.5501C
128 MEG
APM
CPM
in service
active
fault
static
sensitive
Table 2.2 Status of SPM (APM Functionality) Module LEDs
Status of
LEDs Meaning Notes
APM ON, Normal state for APM on the active AC.

in service ON,
active ON
fault OFF
Page 29-56 7/07 76.5500/29, Rev R

Table 2.2 Status of SPM (APM Functionality) Module LEDs (Continued)
APM ON, Normal state for APM on the standby AC.

in service ON,
active OFF
fault OFF
APM flashing, Normal state for APM when system in Utility Mode.
in service OFF,
active OFF
fault OFF
APM ON, Normal state when the AC for the same copy as the APM If unable to determine why the AC is in OOS state, you
in service OFF, is OOS. may want to investigate this.
active OFF
fault OFF
APM ON, Module is running its diagnostic test. Temporary state. Both APM and fault LEDs are ON during LINK mode
in service OFF, while processor is looking for active processor.
active OFF Temporary state.
fault ON
APM OFF, - Module is in the process of initializing its software. Fault LED blinks ten times, then OFF when module
in service OFF, Temporary state. resets. Continues to reset until clears and displays one
active OFF - If module is faulty or failed, fault LED blinks ten times. of four normal states above. Temporary state.
fault ON
All LEDs OFF No power to module, not in slot, breaker OFF. Refer to Section 11, Checking the Power to a Shelf,
page 29-1105.
76.5500/29, Rev R 7/07 Page 29-57

Alarm Interface Module LEDs Figure 2.3 Alarm Interface Module LEDs
AIM
active
fault
Table 2.3 Status of Alarm Indicator Module LEDs
Status of
LEDs Meaning Notes
Active ON, Normal state when AC is active, but not standby (STBY)
fault OFF or out-of-service (OOS).
All ON - If APM is faulted, this state remains until APM clears its Usually a temporary state that occurs during module or
fault and downloads data to AIM to clear its fault. system initialization.
- In self-diagnostic mode.
Active OFF, - Faulted or failed module.

fault ON - Bent pin(s) on the backplane connector.
Both OFF - This is normal state when the administrative complex is When the AC is not active (IS-NR-ACT), this is normal
either in-service, standby (IS-STBY) or out-of-service, state.
standby (OOS-STBY).
- No power to module, not in slot, breaker OFF, bent pin(s) Refer to Section 11, Checking the Power to a Shelf,
on the backplane connector. page 29-1105.
Page 29-58 7/07 76.5500/29, Rev R

System Communication Figure 2.4 System Communication Module 1 and 2 LEDs

Module LEDs
SCM
active
fault
Table 2.4 Status of System Communication 1 and 2 Module LEDs
Status of
LEDs Meaning Notes
Active ON, Normal, active state.

fault OFF
Both ON - If SPM (functioning as APM) is faulted, wait until APM The SCM performs the following sequence:
clears its fault before receiving download. 1. download, 2. self-diagnostics, 3. SCM downloads to
- Faulted or failed module. PGCs and NGCs. Usually a temporary state that occurs
- Active module has no STBY module. during module or system initialization.

fault ON - Bent pin(s) on the backplane connector.
Both OFF No power to module, not in slot, breaker OFF, bent pin(s) Refer to Section 11, Checking the Power to a Shelf,
on the backplane connector. page 29-1105.
76.5500/29, Rev R 7/07 Page 29-59

Synchronous Interface Figure 2.5 5507B Synchronous Interface Module Fault LEDs
Module LEDs
Master Slave
SIM SIM
SIM SIM
ref A facility ref A facility

alarms alarms
ref B ref B
ref A ref A
ref B ref B
selected selected
references references
holdover holdover
free run free run
Master Master module

module
status
status
in service in service
fault fault
5507B Synchronization Interface

Module (SIM) in normal state for both
MSTR and SLV state with selected
reference A
Page 29-60 7/07 76.5500/29, Rev R

Figure 2.6 5507A Synchronous Interface Module LEDs
SIM
ref B
fault
ref A
active
fault
5507A Synchronous Interface

Module (SIM) in normal state
(Power LED is ON)
Table 2.5 Status of Synchronous Interface Module LEDs
LED Status of
Groups LEDs Meaning Notes
One red facility External reference fails, either ref A or ref B.

Facility Alarms alarm ON
Both red facility Normal state with no facility alarms.

alarms OFF
76.5500/29, Rev R 7/07 Page 29-61

Table 2.5 Status of Synchronous Interface Module LEDs (Continued)
LED Status of
Selected Both green 1. If MSTR LED is ON and this is MSTR SIM, this
References references OFF, is a faulted or failed module.
both yellow 2. If MSTR LED is OFF and this is SLV SIM, this
references OFF is normal state.
One green Normal state for selected references:

reference ON, either ref A or ref B is ON, both yellow LEDs are
both yellow OFF.
references OFF
Both green The timing generator is operating in frequency Holdover mode is the condition of a clock that
references OFF, holdover mode. lost its previously connected external
holdover reference reference source. Neither external reference
ON is available.
Follow your company’s prescribed procedures

for obtaining technical assistance or call
Tellabs Technical Assistance at
1.800.443.5555 (North America) or
Both green The timing generator is operating with the Free run is the condition of a clock for a
references OFF, on-board 10Mhz oscillator as the timing source. system that is configured to use the internal
free run reference There is no synchronization to an external timing timing source.
ON source.
Follow your company’s prescribed procedures
Module Status Master ON Indicates that this SIM is acting as Master for A system has two SIMs: one SIM Master LED
timing synchronization is ON, the other SIM Master LED is OFF. This
is the normal state.
Master OFF Indicates that the other SIM is acting as Master
for timing synchronization. This SIM is SLV
In service ON, a) Faulted or failed module Both LEDs are ON during initialization
fault ON b) Bent pin(s) on backplane connector
In service ON, a) Normal, active state 5507A and 5507B SIM: The active/in-service
fault OFF LED for the MSTR SIM is ON constantly.
5507A only: SLV SIM active LED flashes ON

every 1.5 seconds.
In service OFF, a) The module is OOS-ANR

fault ON b) Faulted or failed module
c) Bent pin(s) on backplane connector
In service OFF, 1. If SIM was edited OOS, this is normal state. Refer to Section 11, Checking the Power to a
fault OFF Verify with RTRV-TMG command to check Shelf, page 29-1105.
PST=OOS-NR
2. If SIM is IS-NR, this indicates no power, not in
slot, breaker OFF, bent pin(s) on backplane
connector
Page 29-62 7/07 76.5500/29, Rev R

LAN Switch Module LEDs Figure 2.7 LAN Switch Module LEDs
LSM
LIP fault
in service
active
fault
Table 2.6 Status of LSM LEDs

Status of
LEDs Meaning Notes
in service and active LEDs on Module is functioning normally. No fault on LIP.
LIP fault and fault LEDs off
in service and active on LSM is in standby mode.
in service and active LEDs on Module is functioning normally. Fault on LIP.

LIP fault on
in service and active LEDs on a) Faulted or failed module Both LEDs are ON during initialization
fault LED on b) Bent pin(s) on backplane connector
c) Disconnected or broken cable
in service and active LEDs off a) The module is OOS-ANR

fault ON b) Faulted or failed module
c) Bent pin(s) on backplane connector
All LEDs OFF No power to module, not in slot, breaker OFF. Refer to Section 11, Checking the Power to a
Shelf, page 29-1105.
76.5500/29, Rev R 7/07 Page 29-63

System Pre-Checks
2.10 Perform the following system pre-checks.
__ 1. Using either link 1 or link 5, log on to the system by entering the
following command:
ACT-USER::uid:ctag::pid;
Where: uid = User identity.

ctag = Correlation tag.
pid = Password.
System response:
system_id yy-mm-dd hh:mn:ss
M ctag COMPLD
/* NOTICE: This is a private computer system. */
/* Unauthorized access or use may lead to
prosecution. */
Where: yy = Current year.

mm = Month, 1 - 12.
dd = Day, 1 - 31.
hh = Hour of 24-hour clock, 0 - 23.
mn = Minute, 0 - 59.
ss = Seconds, 0 - 59.
__ 2. Verify that your login has been assigned the proper user privilege code
(UPC) to perform these procedures by entering the following
command:
RTRV-SECU-USER::uid:ctag;
System response:
M ctag COMPLD
Followed by lines of data similar to the following sample:

"BOB:,UPC=A8::CHAN=N-2,PAGE=0,PCNT=0,PARTNAME=ALLFAC,MINPWLIFE=24,MAXSES=6"
__ 2.1 Verify that your login is a UPC of an A8 or greater.
__ 2.2 If your UPC is not an A8 or higher, contact your system

administrator to have your UPC changed.
Page 29-64 7/07 76.5500/29, Rev R

__ 3. Put the system in local restoration mode by entering the following

command:
STA-LOCL-RST:::ctag;
Where: ctag = Correlation tag.

System response when CPC is off:
M ctag COMPLD
System response when CPC is on:

WARNING: All other user sessions and scheduled reports will be terminated.
Do you want to Execute this Command: (Y or N)
__ 3.1 Press Y for Yes to execute this command.
M ctag COMPLD
__ 4. Retrieve the local restoration mode by entering the following

command:
RTRV-LOCL-RST:::ctag;
System response:
M ctag COMPLD

":ALW:UPGRADE=NO"
__ 4.1 Verify from the system response that the system is in local
restoration mode (ALW).
__ 5. Retrieve the status of both ACs by entering the following command:

RTRV-EQPT::AC-A&&-B:ctag;
System response:
M ctag RTRV

"AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=IS-NR-ACT"
"APM-A::HWV=81.5501C RG,ALMPF=99,SN=TD3630071,DT=051230,RAM=128MB:PST=NR"
"LSM-A::HWV=81.55103 R09,ALMPF=99,SN=UV0694866,DT=060310,MACADDR2=
0001AF1681B5:PST=NR"
"SCM-1-A::HWV=81.5506A RQ,ALMPF=99,SN=UZ0240754,DT=060124:PST=NR"
"SCM-2-A::HWV=81.5506B RG,ALMPF=99,SN=OI0454509,DT=000603:PST=NR"
"HDD-A::HWV=\"MAXTOR ATLAS10K5_73WLS JNZH\",ALMPF=99:PST=NR"
"RSD-A::HWV=\"ADTRON SDDS N18012 DUAL 2b02\",TYPE=NON-OPTICAL,ALMPF=99:PST=NR"
"PRI-A::,ALMPF=99:PST=NR"
"SEC-A::,ALMPF=99:PST=ANR"
"REMV-A::,ALMPF=99:PST=ANR-EQ"
"AIM-A::HWV=81.5504 RJ,ALMPF=99,SN=OI0619944,DT=000724:PST=NR"
"ACPS-1-A::HWV=8X.5534,ALMPF=99:PST=NR"
"SIM-A::HWV=81.5507A RG,ALMPF=99,TMG=MSTR,SN=MI0536631,DT=980718:PST=IS-NR"
"LIP-A::HWV=81.55130 RP,ALMPF=99:PST=NR"
76.5500/29, Rev R 7/07 Page 29-65

"AC-B::SWV=5500FP11.0A507,ALMPF=99:PST=IS-ANR-STBY"
"APM-B::HWV=81.5501C RG,ALMPF=99,SN=OD466288701234,DT=000617,RAM=128MB:PST=NR"
"LSM-B::,ALMPF=99:PST=UEQ"
"SCM-1-B::HWV=81.5506A RQ,ALMPF=99,SN=UZ0240068,DT=060124:PST=NR"
"SCM-2-B::HWV=81.5506B RH,ALMPF=99,SN=QI4353833,DT=021224:PST=NR"
"HDD-B::HWV=\"MAXTOR ATLAS10K5_73WLS JNZH\",ALMPF=99:PST=NR"
"RSD-B::HWV=\"ADTRON SDDS N18012 DUAL 2b02\",TYPE=NON-OPTICAL,ALMPF=99:PST=NR"
"PRI-B::,ALMPF=99:PST=ANR"
"SEC-B::,ALMPF=99:PST=ANR"
"REMV-B::,ALMPF=99:PST=ANR-EQ"
"AIM-B::HWV=81.5504 RJ,ALMPF=99,SN=OI0619448,DT=000724:PST=NR"
"ACPS-1-B::HWV=8X.5534,ALMPF=99:PST=NR"
"SIM-B::HWV=81.5507A RG,ALMPF=99,TMG=SLV,SN=OI1283575,DT=001026:PST=IS-NR"
"LIP-B::,ALMPF=99:PST=ANR-UEQ"
__ 5.1 Verify from the system response that the present state of
the non-alarmed AC is in-service, normal, active
(IS-NR-ACT).
__ 6. Retrieve the state of the network timing related entities in the system
by entering the following command:
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
Note: The system output will vary depending on the system configuration.
"NE-TITAN5500::TMG=SYNC,SYNCMODE=NORM"
"NC-A::SIZE=5376,ESMSIZE=3072,INHSTATUS=ALLOWED,PREFNET=YES:PST=IS-NR"
"NC-B::SIZE=5376,ESMSIZE=3072,INHSTATUS=ALLOWED,PREFNET=NO:PST=IS-NR"
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
"REF-A::SSM=NA:PST=IS-NR-ACT"
"REF-B::SSM=NA:PST=IS-NR-STBY"
"SIM-A::TMG=MSTR,SYNCMODE=NORM:PST=IS-NR"
"SIM-B::TMG=SLV,SYNCMODE=NA:PST=IS-NR"
"NTDM-A::TMG=SIM-A:PST=NR"
"NTDM-B::TMG=SIM-A:PST=NR"
"CGC-SH1-10::PST=IS-NR"
"CCSM-SH1-9::TMG=SIM-A:PST=NR"
"CCSM-SH1-12::TMG=NONE:PST=NR"
Page 29-66 7/07 76.5500/29, Rev R

both SIMs is in-service, normal (IS-NR).
__ 6.1.1 If the system response verifies that the

present state of either SIM is not
in-service, normal (IS-NR), resolve the
issue by proceeding to Synchronization
Interface Module (SIM), page 29-146.
__ 6.2 Record the MASTER/SLAVE relationship (TMG=MSTR

and TMG=SLV). The active LED on the MASTER SIM is
on constantly. Only one SIM is Master, the other is Slave:
SIM in Copy A or B TMG = MSTR TMG = SLV
SIM-A
SIM-B
__ 6.3 Record the SIM copy A or B that is assigned to the

NTDMs and/or CCSMs (TMG=SIM-A/B). Both NTDMs
and CCSMs must list the same MASTER SIM.
NTDM TMG = SIM-A TMG = SIM-B
NTDM-A
NTDM-B
CCSM-SH1-9
CCSM-SH2-9
__ 6.4 Verify that both NTDMs and CCSMs are listening to the
same MASTER SIM. Refer to step 6.3.
__ 6.5 If the NTDMs and CCSMs are not listening to the MSTR
SIM, proceed to Troubleshooting the Network Complex,
page 29-245, to troubleshoot the problem.
__ 6.6 If the SIM in the alarmed AC contains TMG=SLV,

continue to step 9, page 29-69.
__ 6.7 If the SIM in the alarmed AC contains TMG=MSTR,

Note: Follow internal policy for SIM copy switching.
76.5500/29, Rev R 7/07 Page 29-67

__ 7. Switch duplex equipment to switch master/slave timing of the SIMs by

entering the following command:
SW-DX-EQPT::SIM-x:ctag;
Where: x = Either A or B, whichever SIM is MSTR.

M ctag COMPLD
System response: when CPC is on:

WARNING: Redundancy status may be altered - potential loss of service.

M ctag COMPLD
__ 7.2 Wait 1 minute before proceeding.
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
Page 29-68 7/07 76.5500/29, Rev R

__ 8.1 Verify from the system response that SIM-A and SIM-B
have now switched timing (TMG=MSTR/SLV).
__ 8.2 Verify from the system response that NTDM-A and

NTDM-B are listening to the master SIM.
__ 8.3 Verify from the system response that the CCSM-SH1-9

and CCSM-SH2-9 are listening to the master SIM.
__ 8.4 Verify from the system response that one REF is

in-service, normal, standby (IS-NR-STBY) and the other
is in-service, normal, active (IS-NR-ACT).
Note: For 5507B SIMs, the master LED should be lit on the SIM that is master.
For 5507A SIMs, the active LED should be lit on the SIM that is master.
Verify that the LED activity on the SIMs corresponds with the system
response. If there is a discrepancy between the system response and the
LED activity, follow your company's prescribed procedures for obtaining
technical assistance or call Tellabs Technical Assistance at
1.800.443.5555 (North America) or 1.630.798.7070 (outside North
America).
__ 9. Are continuous TSI messages reporting "card removed" and/or

"module inserted" being displayed?
__ 9.1 If yes, go to Troubleshooting the Network Complex,
page 29-245, to troubleshoot the problem.
__ 9.2 If no, go to the next step.
System response:
M ctag COMPLD

"AC-A::SWV=5500FPX.Y.Z.R [LITE], ALMPF=99:PST=IS-NR-ACT"
{Additional system output messages appear ...}
"AC-B::SWV=5500FPX.Y.Z.R [LITE], ALMPF=99:PST=IS-ANR-STBY"
__ 10.1 If the present state of the alarmed AC is in-service,

abnormal (IS-ANR), go to step 11, page 29-70.
__ 10.2 If the present state of the alarmed AC is out-of-service,

abnormal (OOS-ANR), go to step 12, page 29-70.
76.5500/29, Rev R 7/07 Page 29-69

__ 11. Retrieve all alarm conditions by entering the following command:

RTRV-ALM-ALL:::ctag;
System response when no alarm conditions exist:

M ctag COMPLD
System response when alarm conditions do exist:

M ctag COMPLD

\"Disk synch lost on active AC - Relational files error\"
\"Disk synch lost on active AC - Log processing error\"
__ 11.1 If the system generates a DISK SYNC alarm or the

following TCP/IP alarm, follow your company’s prescribed
procedures for obtaining technical assistance or call
Tellabs Technical Assistance at 1.800.443.5555 (North
America) or 1.630.798.7070 (outside North America).
\"PM Data HSO client connection lost\"
__ 11.2 For all other alarm messages, go to Determining the

Meaning of Alarm Messages, page 29-73, to troubleshoot
the problem.
__ 12. Retrieve the present state of the failed administrative complex by

RTRV-EQPT::AC-x:ctag;
Where: x = Either A or B, whichever AC is in alarm.
System response:
M ctag COMPLD

"AC-B::SWV=5500FPX.Y.Z.R [LITE],ALMPF=99:PST=OOS-ANR"
"APM-B::HWV=81.5501C RG,ALMPF=99,SN=OD466288701234,DT=000617,RAM=128MB:PST=ANR"
"LSM-B::HWV=81.55103 R12,ALMPF=99,SN=UV1170222,DT=051230,
MACADDR2=0001AF1681B5:PST=ANR"
Page 29-70 7/07 76.5500/29, Rev R

__ 12.1 Verify from the system response that no modules are

abnormal (ANR) or out-of-service (OOS).
__ 12.1.1 If any modules are abnormal (ANR), go

to step 11, page 29-70, to troubleshoot
the problem.
__ 12.1.2 If all the modules are in-service, normal

(IS-NR) or normal (NR), go to step 13,
page 29-71.
__ 13. Retrieve the status of the primary memory by entering the following
command:
RTRV-MEMSTAT-MEM::PRI:ctag;
System response:
M ctag COMPLD

":PRI-B,PGM:040915,08-08,FULL,5500FPX.Y.Z,,VALID,ACTIVE,SYNC"
":PRI-B,DATA:040915,08-08,FULL,5500FPX.Y.Z,PLS1024,VALID,ACTIVE,OUT-OF-SYNC"
":PRI-A,PGM:040916,11-39,FULL,5500FPX.Y.Z,,VALID,STANDBY,SYNC"
":PRI-A,DATA:040916,11-39,FULL,5500FPX.Y.Z,PLS1024,VALID,STANDBY,OUT-OF-SYNC"
__ 13.1 If the primary memory program and data bundles are

VALID, go to step 14.
__ 13.2 If the primary memory program or data bundles are not

VALID, go to Single Removable Media (SRM),
page 29-218.
__ 14. Retrieve the status of the secondary memory by entering the following
command:
RTRV-MEMSTAT-MEM::SEC:ctag;
System response:
M ctag COMPLD

":SEC-B,PGM:040916,13-44,FULL,5500FPX.Y.Z,,VALID,ACTIVE"
":SEC-B,DATA:040916,13-44,FULL,5500FPX.Y.Z,PLS1024,VALID,ACTIVE"
":SEC-A,PGM:040916,13-44,FULL,5500FPX.Y.Z,,VALID,STANDBY"
":SEC-A,DATA:040916,13-44,FULL,5500FPX.Y.Z,PLS1024,VALID,STANDBY"
__ 14.1 If the secondary memory program and data bundles are

VALID, go to step 15, page 29-72.
__ 14.2 If the secondary memory program or data bundles are not

VALID, go to Secondary Memory (SEC), page 29-214.
76.5500/29, Rev R 7/07 Page 29-71

__ 15. Retrieve the status of the removable memory by entering the following
command:
RTRV-MEMSTAT-MEM::REMV:ctag;
System response:
M ctag COMPLD

":REMV-B,PGM:040831,10-42,FULL,5500FPX.Y.Z,,VALID,ACTIVE"
":REMV-B,DATA:040831,10-42,FULL,5500FPX.Y.Z,,PLS1024,VALID,ACTIVE"
":REMV-B,UPGRADE:040707,14-21,FULL,5500FPX.Y.Z,,VALID,ACTIVE"
":REMV-A,PGM:040915,15-26,FULL,5500FPX.Y.Z,,VALID,STANDBY"
":REMV-A,DATA:040915,15-26,FULL,5500FPX.Y.Z,PLS1024,,VALID,STANDBY"
":REMV-A,UPGRADE:040707,14-21,FULL,5500FPX.Y.Z,,VALID,STANDBY"
__ 15.1 If the removable memory program and data bundles are

VALID, follow your company's prescribed procedures for
obtaining technical assistance or call Tellabs Technical
Assistance at 1.800.443.5555 (North America) or
__ 15.2 If the removable memory program or data bundles are not

VALID, go to Single Removable Media (SRM),
page 29-218.
End of Procedure
Page 29-72 7/07 76.5500/29, Rev R

Determining the Meaning of Alarm Messages

2.11 Administrative Complex alarm messages are listed in the Table 2.8,
page 29-75, through Table 2.25, page 29-96. Each table lists the alarm messages
for a certain module type or entity, the description of that alarm message, a
probable cause for the alarm, and then directs you to the appropriate
troubleshooting procedure.
Note: For the associated condition type of an alarm message, refer to TL1
Conditions, page 29-1177.
2.12 The alarms listed in Table 2.8, page 29-75, through Table 2.25,
page 29-96, are listed in the order recommended for troubleshooting. If multiple
alarms are listed in the alarm output, troubleshoot the alarms in the order they are
listed in the tables. For example, if an AIM alarm and a LINK alarm are both listed,
troubleshoot the AIM alarm first; then troubleshoot the LINK alarm.
2.13 Choose the correct table for the alarmed module type or entity:
• For the Administrative Complex, go to Table 2.7, page 29-74.
• For an Alarm Interface Module, go to Table 2.8, page 29-75.
• For a System Communication Module 1, go to Table 2.9, page 29-77.

• For a System Communication Module 2, go to Table 2.10, page 29-78.
• For the Administrative Processor Module, go to Table 2.12,

page 29-80.
• For a Synchronous Interface Module, go to Table 2.13, page 29-82.
• For a LAN Switch Module, go to Table 2.14, page 29-85.
• For a LAN Interface Panel, go to Table 2.15, page 29-86.
• For an Administrative Complex Power Supply, go to Table 2.16,

page 29-87.
• For the Primary Memory, go to Table 2.17, page 29-88.
• For the Secondary Memory, go to Table 2.18, page 29-89.
• For the Removable Media, go to Table 2.20, page 29-91.

• For the Channel, go to Table 2.21, page 29-93.
• For the LINK, go to Table 2.22, page 29-94.
• For the Local Area Network (LAN), go to Table 2.24, page 29-95.
• For the Timing Reference, go to Table 2.26, page 29-97.
• For the Network Element, go to Table 2.27, page 29-100.
• For the Removable Storage Drive, go to Table 2.19, page 29-90.

• For the Hard Disk Drive, go to Table 2.11, page 29-79.
• For the Transmission Control Protocol/Internet Protocol (TCP/IP), go

to Table 2.25, page 29-96.
76.5500/29, Rev R 7/07 Page 29-73

Administrative Complex (AC) Alarm Messages

2.14 In order to troubleshoot the alarm message(s) received for the
Administrative Complex, use the following table. The first column of the table lists
the possible alarm messages that can be generated for an AC. The second column
lists a description of the alarm message. The third column gives a probable cause
for the alarm.
Table 2.7 Administrative Complex Alarm Messages

Condition Probable Cause(s)—For
Type Alarm Message Description Reference Only
PROTNA Administrative Complex failed One of the elements in the AC has Defective module in the administrative
(ANR) - Not available for protection faulted. The alarm clears when all AC complex.
elements have returned to a normal
state. This alarm message may be
accompanied by another alarm
message related to a specific module.
Go to the alarm message table for the
specific module in alarm to troubleshoot
the problem.
PRONTNA Administrative Complex OOS - Not The AC has been edited The AC has been edited to an
available for protection out-of-service. The alarm clears when out-of-service state.
the AC is edited back to an in-service
state. Go to step 21, page 29-138.
INT Entity failure reported to the Admin. System has detected condition An AC entity (module or disk) is in alarm
Complex declared against AC entity. This is a or the APM in the standby AC has been
secondary alarm marking the AC detected as removed.
transition to an ANR state.
Go to Administrative Processor Module
(APM) or System Processor Module
(SPM), page 29-131.
If the APM troubleshooting procedures

do not resolve the problem and there is
another alarm message related to a
specific module, go to the alarm
message table for the specific module in
alarm to troubleshoot the problem.
INT Failed to complete active processor System is unable to execute a Switch away failed because the standby
initialization sequence manual AC copy switch. AC failed to detect all AIM cables or
because there are AIP cables missing.
Go to Alarm Interface Module (AIM),
page 29-102.
INT Unable to deselect because standby The standby side AC cannot become A significant ANR condition exists on the
processor not available active. STBY side admin complex, preventing a
copy switch. Go to Administrative
Processor Module (APM) or System
Processor Module (SPM), page 29-131.
INT Unable to deselect due to possible The standby side AC cannot become Either the AIM cable is disconnected or
AIM fault active. faulty, or the AIM is faulty. Go to Alarm
Interface Module (AIM), page 29-102.
CONTCOM Degraded internal comm: Rev J AC This alarm occurs when the system is Replace the existing shelf with a Rev J
backplane not verified configured for 4608 SDFs in a or later AC shelf. (Refer to Tellabs 5500
Consolidated Core Switch, and the Replacement Procedures, 76.5500/55.)
AC backplane is less than Rev J.
Page 29-74 7/07 76.5500/29, Rev R

Alarm Interface Module (AIM) Alarm Messages

2.15 In order to troubleshoot the alarm message(s) received for a faulted Alarm
Interface Module, use the following table. The first column of the table lists the
possible alarm messages that can be generated for an AIM. The second column
for the alarm.
Table 2.8 Alarm Interface Module Alarm Messages

INT AIM initialization failure Inserted AIM has failed initialization. - The AIM module is defective.
- The AIM-cable audit has failed.
- There is a communications failure.

page 29-102.
INT AIM removed The AIM module is detected as being - AIM has been removed from the system.
absent from the system. - AIM audits unable to detect the presence
of the AIM.
- Communications failed between the APM
and the AIM.

page 29-102.
INT Both AIM cables are absent Both the AIP cable and the Both cables are disconnected from the
interprocessor LAN cables are active AC. Go to Alarm Interface Module
reported as being disconnected. (AIM), page 29-102.
INT One AIM cable is absent Either the AIP cable or the One of the cables is disconnected from the
interprocessor LAN cables are active AC. Go to Alarm Interface Module
reported as being disconnected. (AIM), page 29-102.
INT EEPROM failure Either a failure to read the EEPROM Corrupted EEPROM data. Go to Alarm
information or a failure to store this Interface Module (AIM), page 29-102.
information to the database has
occurred.
INT Module not compatible with Module is not supported by the Module revision level is either lower or
existing software software version currently operating higher than the levels supported by the
on the system. current software version. Go to Alarm
REVLVL Module revision level does not The revision level of the module does This module is not supported by this
meet revision level requirements not match the set of valid revision version of the software. Go to Alarm
levels maintained in the system Interface Module (AIM), page 29-102.
database. Use RTRV-REVTBL
command to view the system
database of valid module revision
levels. Refer to Tellabs 5500/5500S
Command Reference Manual,
76.5500/13.
INT No AIP cable AIP cable is detected as being absent AIP cable is either disconnected, cut, or
from the system. damaged. Go to Alarm Interface Module
(AIM), page 29-102.
INT No reset is detected on the AIM After a reset, AIM did not detect a A second reset occurred before AIM was
second reset. fully initialized. Go to Alarm Interface
Module (AIM), page 29-102.
76.5500/29, Rev R 7/07 Page 29-75

Table 2.8 Alarm Interface Module Alarm Messages (Continued)

INT Selection circuit test failed Selection circuit(s) for determining the Failure of one or both of the selection
active AIM failed. circuits on the active AIM. Go to Alarm
INT De-selection test failed The de-selection test failed. Internal diagnostic tests have failed. Go to
Alarm Interface Module (AIM),
page 29-102.
INT Watchdog timing circuitry failure The watchdog timer has elapsed or Failure of the watchdog timer circuitry on
failed. This alarm is typically posted the AIM is the most likely failure (bad
against the AIM on the standby AC. module). Failure of software to begin the
watchdog process may also cause this
alarm. Go to Alarm Interface Module
(AIM), page 29-102.
INT Failed diagnostics The AIM has failed one of its internal Failed one or more internal diagnostic
diagnostics either on power-up or the tests. Failed or faulted module. Go to
TL1 DGN command. Alarm Interface Module (AIM),
page 29-102.
Page 29-76 7/07 76.5500/29, Rev R

System Communication Module 1 (SCM-1) Alarm Messages

2.16 In order to troubleshoot the alarm message(s) received for a faulted
System Communication Module 1, use the following table. The first column of the
table lists the possible alarm messages that can be generated for a SCM-1. The
second column lists a description of the alarm message. The third column gives a
probable cause for the alarm.
Table 2.9 System Communication Module 1 Alarm Messages

INT EEPROM failure Either a failure to read the EEPROM Corrupted EEPROM data. Go to
information or a failure to store this System Communication Modules
information to the database has (SCM-1 and SCM-2), page 29-110.
occurred.
INT Module not compatible with Module is not compatible with the Module revision level is either lower or
existing software software version running on the system. higher than the levels supported by the
current software version. Go to System
Communication Modules (SCM-1 and
SCM-2), page 29-110.
meet revision level requirements not match the set of valid revision levels version of the software. Go to System
maintained in the system database. Use Communication Modules (SCM-1 and
RTRV-REVTBL command to view the SCM-2), page 29-110.
system database of valid module
revision levels. Refer to the Tellabs
5500/5500S Command Reference
Manual, 76.5500/13.
INT No reset detected on the SCM After a reset, the SCM did not detect a A second reset has occurred before the
second reset. SCM was fully initialized. Go to System
SCM-2), page 29-110.
INT System Communication Module The SCM has failed module diagnostics. The SCM has failed. Go to System
card failure Communication Modules (SCM-1 and
SCM-2), page 29-110.
INT System Communication Module There was a memory failure on the The module memory is faulty. Go to
Memory Failure SCM. System Communication Modules
(SCM-1 and SCM-2), page 29-110.
INT System Communication Module The system cannot detect the presence SCM is either removed from the system
removed of an SCM module. or the SCM audits are unable to detect
the presence of the SCM. Go to System
SCM-2), page 29-110.
INT Failed diagnostics The SCM-1 has failed one of its internal Failed one or more internal diagnostic
TL1 DGN command. System Communication Modules
INT LAN Controller x fails loopback test A LAN controller has failed the loopback The module has failed internal LAN
(where x = 0 - 9) test. tests. Go to System Communication
Modules (SCM-1 and SCM-2),
page 29-110.
INT LAN Controller x fails transmit and A LAN controller has failed the transmit The module has failed internal LAN
dump test (where x = 0 - 9) and dump test. tests. Go to System Communication
Modules (SCM-1 and SCM-2),
page 29-110.
76.5500/29, Rev R 7/07 Page 29-77

System Communication Module 2 (SCM-2) Alarm Messages

System Communication Module 2, use the following table. The first column of the
table lists the possible alarm messages that can be generated for a SCM-2. The
Table 2.10 System Communication Module 2 Alarm Messages

INT EEPROM failure The AP was not able to successfully Corrupted EEPROM data, or EEPROM
access the information in the EEPROM information was not read successfully.
of the SCM-2. Go to System Communication Modules
REVLVL Module revision level does not The revision level of the module does not This module is not supported by this
meet revision level requirements match the set of valid revision levels version of the software. Go to System
maintained in the system database. Use Communication Modules (SCM-1 and
RTRV-REVTBL command to view the SCM-2), page 29-110.
revision levels. Refer to Tellabs
Manual, 76.5500/13.
INT No reset detected on the SCM-2 The SCM-2 did not detect a reset. A second reset has occurred before the
SCM-2 was fully initialized. Go to System
SCM-2), page 29-110.
INT System Communication Module The SCM-2 configuration failed. One or more of the following has
failure occurred:
- The SCM-2 has been removed from the
system.
- The SCM-2 audits cannot detect the
presence of the SCM-2.
Go to System Communication Modules

INT System Communication Module The active AC is not detecting the One or more of the following has
removed presence of the SCM-2. occurred:
- The SCM-2 is not seated in its slot.
- AC audit has failed to receive the proper
response from the SCM-2.
Go to System Communication Modules

INT Module not compatible with The module contains the wrong software Run an equipment audit. Verify that the
existing software or the wrong revision level. feature package supports SCM-2. Go to
System Communication Modules (SCM-1
and SCM-2), page 29-110.
INT Failed diagnostic The SCM-2 has failed one of its internal Failed one or more internal diagnostic
TL1 DGN command. System Communication Modules (SCM-1
and SCM-2), page 29-110.
Page 29-78 7/07 76.5500/29, Rev R

Hard Disk Drive (HDD) Alarm Messages

2.18 In order to troubleshoot the alarm message(s) received for a faulted Hard
Disk Drive, use the following table. The first column of the table lists the possible
alarm messages that can be generated for an HDD. The second column lists a
description of the alarm message. The third column gives a probable cause for the
alarm.
Table 2.11 Hard Disk Drive Alarm Messages

INT Disk has failed self test The DSM hard disk drive (HDD) has The inactive AC was unable to
failed, but its removable storage drive complete initialization for one of the
(RSD) may still be good. following reasons:
- During INIT-SYS-Phase 0, a condition
exists on the hard disk drive (HDD).
- The hard disk drive (HDD) failed to
mount any of the partitions.
Go to Data Storage Module (DSM),

page 29-117.
INT Disk removed The system has failed to detect the hard The boot source is not coming from the
disk drive (HDD). hard disk drive (HDD). The primary
PGM bundle is invalid. Go to Data
Storage Module (DSM), page 29-117.
INT Hard Disk Access Failed Read-write access to the hard disk drive There is a problem with the hard disk
(HDD) failed. drive. Follow your company's
prescribed procedures for obtaining
technical assistance or call Tellabs
Technical Assistance at
1.630.798.7070 (outside North
America).
INT Inactive AC has different program During init process monitoring the Software versions of the two ACs do not
version than active AC active AC has polled the inactive AC to match. Go to Data Storage Module
compare software versions and they do (DSM), page 29-117.
not match. The inactive AC has been
marked ANR, unless a Phase II is in
progress. If a Phase II is in progress,
the problems will be flagged and an
autofallback will occur.
INT Failed diagnostics The HDD has failed one of its internal Failed one or more internal diagnostic
TL1 DGN command. Data Storage Module (DSM),
page 29-117.
76.5500/29, Rev R 7/07 Page 29-79

Administrative Processor Module (APM) Alarm Messages

Administrative Processor Module (APM), use the following table. The first column
of the table lists the possible alarm messages that can be generated for an APM.
The second column lists a description of the alarm message. The third column
gives a probable cause for the alarm.
Table 2.12 Administrative Processor Module Alarm Messages

INT APM removed APM in the standby AC detected as APM has either been removed from the
being either removed or absent from system or APM audits are unable to detect
the shelf. the presence of the APM. Go to
Administrative Processor Module (APM)
or System Processor Module (SPM),
page 29-131.
INT The LAN cable is not present The Inter-AC LAN cable is either The inter-AC LAN cable is either cut or
absent or not connected. defective. The inter-AC LAN cable is not
connected to both AC backplanes. Go to
page 29-131.
INT The STBY AC has been The standby APM has been found to The standby AC was commanded to go
commanded into Utility Mode be in the Utility Mode. into Utility Mode. Go to Administrative
INT The LAN has failed The Inter-AC LAN is absent, not The inter-AC LAN cable is either cut or
connected, or defective. defective. The inter-AC LAN cable is not
connected to both AC backplanes. Go to
page 29-131.
INT APM Compatibility mismatch Active and Standby APM do not Must install compatible APMs in both
match. active and standby APM slots. Go to
page 29-131.
INT Failed diagnostic The APM has failed one of its Failed one or more internal diagnostic
internal diagnostics either on tests. Failed or faulted module. Go to
power-up or the TL1 DGN command. Administrative Processor Module (APM)
page 29-131.
INT The initialization for the APM The active AC has detected the One or more of the following has occurred:
failed Administrative Processor Module - Initialization of APM is in progress.
(APM), after it was flagged as - APM has been physically inserted into
“removed from the system.” backplane.
Go to Administrative Processor Module

(APM) or System Processor Module
(SPM), page 29-131.
INT APM EEPROM Failure Either a failure to read the EEPROM Internal module failure. Go to
information or a failure to store this Administrative Processor Module (APM)
information to the database has or System Processor Module (SPM),
occurred. page 29-131.
Page 29-80 7/07 76.5500/29, Rev R

Table 2.12 Administrative Processor Module Alarm Messages (Continued)

INT The reset for the APM has not After a reset, the APM did not detect A second reset occurred before the APM
cleared a second reset. was fully initialized. Go to Administrative
CONTCOM AC backplane APM-LSM LAN LAN connection between the APM Broken or disconnected Ethernet cable
failure detected and LSM on the backplane of the AC between J72 and J71 connectors on AC
has failed. backplane.
Verify connection is secure. If necessary,

replace cable.
CONTCOM AC front panel APM-LSM LAN LAN connection between the APM Broken or disconnected Ethernet cable
failure detected and LSM on the front panel of the between APM front panel and LSM front
modules has failed. panel.
Verify connection is secure. If necessary,

replace cable.
meet revision level requirements not match the set of valid revision version of the software. Go to
levels maintained in the system Administrative Processor Module (APM)
database. Use RTRV-REVTBL or System Processor Module (SPM),
command to view the system page 29-131.
76.5500/13.
76.5500/29, Rev R 7/07 Page 29-81

Synchronization Interface Module (SIM) Alarm Messages

Synchronization Interface Module, use the following table. The first column of the
table lists the possible alarm messages that can be generated for a SIM. The
Table 2.13 Synchronization Interface Module Alarm Messages

INT Signal to all timing elements lost When operating in synchronous mode, One or more of the following has
(possible cables missing) the NTDM receives its clock signal from occurred:
a reference signal provided by the - Possible problem with cable connecting
master SIM. In this case, both NTDMs the SIM and the NTDM.
are not properly receiving the external - Improper or lack of EMI shielding on the
synchronous reference signal being sent AC backplane.
directly from the SIM. - Improper grounding of AC backplane
cabling when EMI shielding is provided.
- SIM module has faulted.
- AC backplane connector problem.
Go to Synchronization Interface Module

(SIM), page 29-146.
PAINTGRT Signal to NTDM-A lost (possible When operating in synchronous mode, One or more of the following has
cable missing) the NTDM receives its clock signal from occurred:
master SIM. In this case, NTDM-A is not the SIM and the NTDM.
properly receiving the external - Improper or lack of EMI shielding on the

(SIM), page 29-146.
PAINTGRT Signal to NTDM-B lost (possible When operating in synchronous mode, One or more of the following has
cable missing) the NTDM receives its clock signal from occurred:
master SIM. In this case, NTDM-B is not the SIM and the NTDM.
properly receiving the external - Improper or lack of EMI shielding on the

(SIM), page 29-146.
Page 29-82 7/07 76.5500/29, Rev R

Table 2.13 Synchronization Interface Module Alarm Messages (Continued)

PAINTGRT Signal to CCSM on SH1 lost When operating in synchronous mode, One or more of the following has
(possible cable missing) the NTDM receives its clock signal from occurred:
master SIM. In this case, the CCSM on the SIM and the LTIP.
shelf 1 is not properly receiving the - Possible problem with the cable
external synchronous reference signal connecting the LTIP and the CCS shelf.
being sent directly from the SIM. - Improper or lack of EMI shielding on the
AC backplane.
- Improper grounding of AC backplane

(SIM), page 29-146.
PAINTGRT Signal to CCSM on SH2 lost When operating in synchronous mode, One or more of the following has
(possible cable missing) the NTDM receives its clock signal from occurred:
master SIM. In this case, the CCSM on the SIM and the LTIP.
shelf 2 is not properly receiving the - Possible problem with cable connecting
external synchronous reference signal the LTIP and the CCS shelf.
being sent directly from the SIM. - Improper or lack of EMI shielding on the
AC backplane.
- Improper grounding of AC backplane

(SIM), page 29-146.
INT Download failed SIM audit has determined that either the The SIM has faulted. Go to
SIM is still requesting a download or the Synchronization Interface Module (SIM),
initial download is still in progress. page 29-146.
INT EEPROM failure detected Either a failure to read the EEPROM Internal module failure. Go to
information or a failure to store this Synchronization Interface Module (SIM),
information to the database has page 29-146.
occurred.
INT Internal error detected An internal error has been reported by -SIM has failed to complete diagnostics
the SIM module. on initialization.
- The NTDMs or CCSMs cannot lock to
the frequency or multiframe of the SIMs.

(SIM), page 29-146.
INT Internal failure detected An internal failure has been reported by One or more of the following has
the SIM as the result of either an audit or occurred:
autonomous fault handling. - The reporting SIM has failed.
- The other SIM has failed.
- The active APM has failed.
- The VME bus on the AC backplane has
failed.

(SIM), page 29-146.
76.5500/29, Rev R 7/07 Page 29-83


INT Module diagnostics failed Module diagnostics for the SIM module An internal fault exists on the SIM
have failed. This message displayed module. Go to Synchronization Interface
only when a DGN-EQPT command for Module (SIM), page 29-146.
the SIM module is issued.
INT Module is incompatible with Module is not compatible with the Module revision level is either lower or
existing software software version running on the system. higher than the levels supported by the
current software version. Go to
Synchronization Interface Module (SIM),
page 29-146.
INT Module removed AC detected the absence of a SIM from One or more of the following has
its slot on the AC shelf. occurred:
• SIM module is missing from the
shelf.
• SIM module is not seated properly.
• SIM module has failed.
• Active SCM module has failed.
• APM module on the same AC has
failed.
• AIM module on the same AC has
failed.
• VME bus on the AC backplane has
failed.
• J40 cable on the AC backplane has
failed or been removed.

(SIM), page 29-146.
meet revision level requirements not match the set of valid revision levels version of the software. Go to
maintained in the system database. Use Synchronization Interface Module (SIM),
RTRV-REVTBL command to view the page 29-146.
Manual, 76.5500/13.
MEA SIM on a 2048 or larger system A 2048 or 3072 SDF system requires a You inserted a 5507 or 5507A SIM into a
must be 81.5507B or later 5507B SIM or later. 2048 or 3072 system. Replace it with a
5507B SIM or later revision. Go to
Synchronization Interface Module (SIM),
page 29-146.
PROTNA SIM failed (ANR) - not available This alarm message displays when a The SIM is transitioning its state via a
for protection user is configuring a SIM using TL1 TL1 command. Go to Synchronization
commands. As a result, one of the Interface Module (SIM), page 29-146.
following has occurred:
- SIM is being taken out-of-service
(OOS) when the other SIM is in-service
(IS) and the current state of the SIM
being placed OOS is IS.
- SIM is transitioned to IS when the
requested SIM is currently OOS and
other SIM is also OOS.
SWTOREFA Primary external timing reference The SIMs are getting their timing from REF-B is receiving LOS or its frequency
has switched to REF-A REF-A instead of REF-B. is outside of the SONET specification. Go
to Timing Reference (REF), page 29-242.
Page 29-84 7/07 76.5500/29, Rev R


SWTOREFB Primary external timing reference The SIMs are getting their timing from REF-A is receiving LOS or its frequency
has switched to REF-B REF-B instead of REF-A. is outside of the SONET specification. Go
to Timing Reference (REF), page 29-242.
CONTCOM Internal loss of communications The SIM and APM-A are not Communication between the modules
between SIM and APM-A communicating. has failed. Go to Synchronization
CONTCOM Internal loss of communications The SIM and APM-B are not Communication between the modules
between SIM and APM-B communicating. has failed. Go to Synchronization
MODINSRT Module inserted The module was removed, but is now in Module has been inserted in its slot on
its slot on the shelf. the shelf. No recovery necessary.
LAN Switch Module (LSM) Alarm Messages

2.21 In order to troubleshoot the alarm message(s) received for a faulted LAN
Switch Module, use the following table. The first column of the table lists the
possible alarm messages that can be generated for an LSM. The second column
for the alarm.
Table 2.14 LAN Switch Module Alarm Messages

INT Module removed AC detected the absence of the LSM One or more of the following has occurred:
from its slot on the AC shelf. LSM is missing from the shelf.
LSM is not seated properly.
LSM has failed.
Go to LAN Switch Module, page 29-171.
INT Internal failure or APM-LSM The Ethernet cable between the APM Make sure cable is securely connected. If
LAN cable disconnected and LSM is broken or disconnected. necessary, replace cable.
meet revision level not match the set of valid revision levels version of the software. Go to LAN Switch
requirements maintained in the system database. Use Module, page 29-171.
RTRV-REVTBL command to view the
Manual, 76.5500/13.
CONTCOM CO LAN cable failure detected Failure detected at the CO LAN port of Verify CO LAN cable is securely
the LIP. connected at LIP.
Go to LAN Interface Panel, page 29-180.
CONTCOM LSM to LSM LAN Comm Lost at LAN communication lost between the Verify cable is securely connected at
XCOPY port (missing cable?) LSMs on each copy of the AC, possibly XCOPY port of LIP.
due to missing cable at the XCOPY port.
76.5500/29, Rev R 7/07 Page 29-85

Table 2.14 LAN Switch Module Alarm Messages (Continued)

CONTCOM LSM to CGC LAN Comm Lost LAN communication lost between the Verify cable is securely connected at
at LAN-1 port (missing cable?) LSM to the CGC, possibly due to LAN-1 port of both copies of the LIP.
missing cable at the LAN-1 port.
Go to Local Area Network (LAN-1),
page 29-230
MAN LAN Interface Panel (LIP) A cable has been incorrectly connected A cable has been plugged into the wrong
miscabled on port <xxxx> to a port on the LIP. connector on the LIP.
where <xxxx> = LAN-1 through
LAN-8|SIM-A|SIM-B|XCOPY| Go to LAN Switch Module, page 29-171.
COLAN which corresponds to
the labels of the ports on LAN
Interface Panel (LIP)
MODINSRT Module Inserted The module was removed, but is now in Module has been inserted in its slot on the
its slot on the shelf. shelf. No recovery necessary.
LAN Interface Panel (LIP) Alarm Messages

2.22 In order to troubleshoot the alarm message(s) received for a LIP, use the
following table. The first column of the table lists the possible alarm messages that
can be generated for an LIP. The second column lists a description of the alarm
message. The third column gives a probable cause for the alarm.
Table 2.15 LAN Interface Panel (LIP) Alarm Messages

INT Module removed or LSM to LIP LIP has been removed, or the LSM to Reconnect LSM to LIP cable.
cable disconnected LIP cable has been disconnected.
Replace LIP.
meet revision level requirements not match the set of valid revision levels version of the software. Go to LAN
maintained in the system database. Use Interface Panel, page 29-180.
RTRV-REVTBL command to view the
Manual, 76.5500/13.
MODINSRT Module Inserted The module was removed, but is now in Module has been inserted in its slot on the
Page 29-86 7/07 76.5500/29, Rev R

Administrative Complex Power Supply (ACPS) Alarm Messages

2.23 In order to troubleshoot the alarm message(s) received for a faulted ACPS,
use the following table. The first column of the table lists the possible alarm
messages that can be generated for an ACPS.The second column lists a
alarm.
Table 2.16 Administrative Complex Power Supply (ACPS) Alarm Messages

INT Power supply module failed Diagnostic tests on the power supply Either the module has failed, the
have detected an internal error on the system is unable to communicate with
module. the module, or the breaker switch
serving the module is turned off. Go to
Administrative Complex Power Supply
Module (ACPS), page 29-204.
INT Administrative shelf power supply The ACPS module is detected as being Either the module has been removed
removed absent from the system. or there is a communications failure
between the APM and the ACPS. Go to
Administrative Complex Power Supply
INT Power supply inserted The power supply module was Power supply module has been
removed, but is now in its slot on the inserted in its slot on the shelf. Go to
shelf. Administrative Complex Power Supply
PROTNA Power supply failed (ANR) - not There is an abnormal condition with the There is a problem with the power
available for protection power supply and the abnormal side supply and/or power supply module.
has lost power redundancy. Go to Administrative Complex Power
Supply Module (ACPS), page 29-204.
76.5500/29, Rev R 7/07 Page 29-87

Primary Memory (PRI) Alarm Messages

2.24 In order to troubleshoot the alarm message(s) received for the Primary
Memory, use the following table. The first column of the table lists the possible
alarm messages that can be generated for the PRI. The second column lists a
alarm.
Table 2.17 Primary Memory Alarm Messages

NVMEMP CMCI Database inconsistencies The connection memory map in the There is a potential problem with the hard
detected database is not consistent with the drive in the DSM, or possible wrong
hardware registers for the ESM, CSM, hardware connection map for a module in
CAM, CCSM, and/or TSI. This problem is the network. Go to Data Storage Module
detected by the Connection (DSM), page 29-117.
Memory/Content Integrity (CMCI) Audit.
NVMEMP DBSI Database inconsistencies The database integrity is corrupted. This Follow your company's prescribed
detected problem is detected by the Database procedures for obtaining technical
Structural Integrity (DBSI) Audit. assistance or call Tellabs Technical
Assistance at 1.800.443.5555 (North
America) or 1.630.798.7070 (outside
North America).
DISKSYNC Disk synch lost on active AC - The content of the standby disk does not There is a failure in disk synchronization
Relational files error match the active disk. This problem is between the standby disk and the active
detected by the Database disk. Go to Primary Memory (PRI),
Synchronization - Administrative page 29-210.
Complex (DBSAC) audit.
DISKSYNC Disk synch lost on active AC - The content of the standby AC disk does There is a failure in disk synchronization
Log processing error not match the active disk. Something has between the standby disk and the active
occurred to interrupt disk disk. Go to Primary Memory (PRI),
synchronization. page 29-210.
NVMEMP Internal software error A copy memory command has been Undetermined failure of access to primary
executed and an unknown failure memory. Go to Primary Memory (PRI),
condition has occurred from the page 29-210.
secondary memory.
Page 29-88 7/07 76.5500/29, Rev R

Secondary Memory (SEC) Alarm Messages

2.25 In order to troubleshoot the alarm message(s) received for the Secondary
Memory, use the following table. The first column of the table lists the possible
alarm messages that can be generated for a SEC. The second column lists a
alarm.
Table 2.18 Secondary Memory Alarm Messages
NVMEMS CMCI Database inconsistencies The connection memory map in the There is a potential problem with the
detected database is not consistent with the hard drive in the DSM.
hardware registers for the ESM, CSM,
CAM, CCSM, and/or TSI. This problem Go to Data Storage Module (DSM),
is detected by the Connection page 29-117.
Memory/Content Integrity (CMCI) Audit.
NVMEMS Copy attempt denied to avoid A copy memory command has been Source and destination memories
bundles with different versions attempted, but the source and contain different version levels for the
destination bundles contain different bundle being copied.
version levels.
Go to Secondary Memory (SEC),
page 29-214.
NVMEMS Copy failure to secondary memory, A copy memory command to the Either the copy memory command
bundle = ALL secondary memory has failed for both has terminated or a CRC comparison
the data and program bundles. has failed.

page 29-214.
bundle = DATA secondary has failed for the data bundle. has terminated or a CRC comparison
has failed.

page 29-214.
bundle = PGM secondary memory has failed for the has terminated or a CRC comparison
program bundle. has failed.

page 29-214.
NVMEMS DBSI Database inconsistencies The database integrity is corrupted. This There is a problem with the hard disk
detected problem is detected by the Database drive in the DSM.
Structural Integrity (DBSI) Audit.
Go to Data Storage Module (DSM),
page 29-117.
NVMEMS Internal software error A copy memory command has been Undetermined failure of access to
executed and an unknown failure secondary memory.
condition has occurred from the
secondary memory. Go to Secondary Memory (SEC),
page 29-214.
NVMEMS Secondary memory data and Both the data and the program bundles The validity flags have not been set
program bundles are invalid in secondary memory are not in a valid for the data and program bundles or
condition. last copy operation did not complete
properly.

page 29-214.
76.5500/29, Rev R 7/07 Page 29-89

Table 2.18 Secondary Memory Alarm Messages (Continued)

NVMEMS Secondary memory data bundle is Data bundle in secondary memory is not The validity flag has not been set for
invalid in a valid condition. the data bundle or the last copy
operation did not complete properly.

page 29-214.
NVMEMS Secondary memory program bundle Program bundle in secondary memory is The validity flag has not been set for
is invalid not in a valid condition. the program bundle or last copy
operation did not complete properly.

page 29-214.
NVMEMS SID mismatch The system detects that SID in The secondary memory contains a
secondary memory is different from SID different SID from the one in system
in the memory to which it is writing. memory.

page 29-214.
Removable Storage Drive (RSD) Alarm Messages

Removable Storage Drive, use the following table. The first column of the table lists
the possible alarm messages that can be generated for an RSD. The second
column lists a description of the alarm message. The third column gives a probable
cause for the alarm.
Table 2.19 Removable Storage Drive Alarm Messages

INT Removable Storage Drive has The RSD has failed self-diagnostics. The RSD has failed. Go to Data Storage
failed self-test Module (DSM), page 29-117.
INT Removable Storage Drive The RSD of the DSM appears to have Either the DSM has been removed, or the
removed been removed from the system. RSD has failed. Go to Data Storage
Module (DSM), page 29-117.
MEA Removable Storage Drive types There was a mismatch detected One RSD has optical media, and the other
are not identical between RSDs. RSD has flash media. Go to Single
Removable Media (SRM), page 29-218.
Page 29-90 7/07 76.5500/29, Rev R

Removable Media (REMV) Alarm Messages

2.27 In order to troubleshoot the alarm message(s) received for the Removable
Media, use the following table. The first column of the table lists the possible alarm
messages that can be generated for a REMV. The second column lists a
alarm.
Table 2.20 Removable Media Alarm Messages

BKUPMEMR Copy attempt denied to avoid Copy memory command has been Source and destination memories contain
bundles with different versions attempted where the source and different version levels for the bundle
destination bundles contain being copied. Go to Single Removable
different version levels. Media (SRM), page 29-218.
BKUPMEMR Copy failure to removable media, Copy memory command to the Either the copy memory command has
bundle = ALL removable media has failed for terminated or a CRC comparison has
both the data and program failed. Go to Single Removable Media
bundles. (SRM), page 29-218.
bundle = DATA removable media has failed for terminated or a CRC comparison has
the data bundle. failed. Go to Single Removable Media
(SRM), page 29-218.
bundle = PGM removable media has failed for terminated or a CRC comparison has
the program bundle. failed. Go to Single Removable Media
(SRM), page 29-218.
BKUPMEMR Internal software error Copy memory command is Access to removable media failed or DSM
executed and either an unknown failed. Go to Single Removable Media
failure condition from removable (SRM), page 29-218.
media or an unmount failure of the
removable media has occurred.
BKUPMEMR Removable media data and Both the data and program One of the following reasons:
program bundles are invalid bundles on the removable media - The validity flags have not been set for
are not in a valid condition. the data and program bundles.
- The last copy operation did not complete
properly.
- The removable media data and program
bundles do not exist.
Go to Single Removable Media (SRM),

page 29-218.
BKUPMEMR Removable media data bundle is Data bundle on removable media One of the following reasons:
invalid is not in a valid condition. - The validity flag has not been set for the
data bundle.
properly.
- The removable media data bundles do
not exist.

page 29-218.
76.5500/29, Rev R 7/07 Page 29-91

Table 2.20 Removable Media Alarm Messages (Continued)

BKUPMEMR Removable media program bundle Program bundle on the removable One of the following reasons:
is invalid media is not in a valid condition. - The validity flag has not been set for the
program bundle.
properly.
- The removable media program bundle
does not exist.

page 29-218.
BKUPMEMR Removable media not high-level System has detected absence of The drive or removable media are
formatted a high-level format on the damaged or cannot be mounted. Go to
removable media. Single Removable Media (SRM),
page 29-218.
BKUPMEMR Removable media not present System has detected that the The drive has either faulted or been
flash disk is absent. removed from the system. Go to Single
Removable Media (SRM), page 29-218.
BKUPMEMR SID mismatch System attempted to write Removable media contains a different SID
removable media information to from the one in system memory. Go to
memory, detected different SID Single Removable Media (SRM),
versions, and declared an alarm. page 29-218.
BKUPMEMR Removable media is a self booting The SRM in the Removable An upgrade disk has been inserted into
SRM Storage Drive is self-bootable. the data storage module (DSM). Go to
Single Removable Media (SRM),
page 29-218.
BKUPMEMR Removable media has insufficient Removable media does not have Refer to Tellabs 5500 Software Release
storage capacity enough storage space to serve as Document, 76.5500/16, for the proper
a backup media. revision of the media.
BKUPMEMR Removable media cannot be used The removable media is an SRM, This message serves as notification that a
for system backup and cannot be used for a system media cannot be used for a backup.
backup.
If a backup is being attempted, obtain a
different media.

page 29-218.
Operation Channel (CHAN) Alarm Messages

2.28 In order to troubleshoot the alarm message(s) received for a channel, use
the following table. The first column of the table lists the possible alarm messages
that can be generated for a CHAN. The second column lists a description of the
alarm message. The third column gives a probable cause for the alarm.
Page 29-92 7/07 76.5500/29, Rev R

Table 2.21 Operation Channel Alarm Messages

OSLINK Channel Transmission Error Buffer for transmitting data out of the - The operations channel has been shut
Causing Buffer Overflow operations channel has received too off via flow control for too long.
much data to store and has been - The speed of the operations channel is
flushed. too slow to handle the amount of
information flowing out from the system.
This would be for a message log port
(MLP).
Go to Link (LINK) or Channel (CHAN),

page 29-225.
SENA Lost Operation Channel Active AC is not detecting anything One or more of the following has
Communication attached to the alarmed operations occurred:
link. As a result, communicating via - A reset of the associated AC is in
that link is impossible. progress.
- No terminal device such as a printer,
terminal, or modem is attached to the link.
- The terminal device attached to the link
is not powered up.
- There is a defective cable between link
and terminal device.

page 29-225.
INTRUSION Maximum number of invalid login The maximum number of invalid The user has exceeded the allowable
attempts exceeded attempts for entering the ACT-USER number of invalid ACT-USER or
or INTRPT-SYS commands have INTRPT-SYS attempts on this channel.
been exceeded on this channel. Also, if a channel was locked before it
went abnormal, it may still be locked when
it comes back up, and this alarm is
reposted. Go to Link (LINK) or Channel
(CHAN), page 29-225.
76.5500/29, Rev R 7/07 Page 29-93

Operation LINK Alarm Messages

2.29 In order to troubleshoot the alarm message(s) received for a LINK, use the
can be generated for a LINK. The second column lists a description of the alarm
Table 2.22 Operation LINK Alarm Messages
OSLINK Lost Operation Link Active AC is not detecting anything One or more of the following has occurred:
Communication being attached to the alarmed - A reset of the associated AC is in
operations link. As a result, progress.
communications via that link is not - No terminal device such as a printer,
possible. terminal, or modem is attached to the link.
-Terminal device attached to link is not
powered up.
- Defective cable between link and
terminal device.

page 29-225.
Control LAN Related Descriptions (LAN-1)

2.30 In order to troubleshoot the alarm message(s) received for a Control Local
Area Network, use the following table. The first column of the table lists the
possible alarm messages that can be generated for a LAN. The second column
for the alarm.
Table 2.23 Control Local Area Network Alarm Messages
PROTNA Failure on internal LAN - part of path The redundancy of the LAN-1 There is a disconnected or broken cable
not available for protection connections between the two in the control LAN path.
administrative complex copies and the
two switch network copies has failed Go to Local Area Network (LAN-1),
due to a broken cable in the path. page 29-230.
Page 29-94 7/07 76.5500/29, Rev R

CO Local Area Network (LAN) (LAN-2) Alarm Messages

2.31 In order to troubleshoot the alarm message(s) received for a Central Office
Local Area Network, use the following table. The first column of the table lists the
possible alarm messages that can be generated for a LAN. The second column
for the alarm.
Table 2.24 Local Area Network Alarm Messages
SENA Supporting Entity Not Available This message displays when the active The system has detected a problem with
AC cannot communicate with the the active LSM and LIP and it no longer
specified LSM and LIP. has the ability to communicate over the
CO LAN.
Most likely cause is disconnected CO LAN

cable.
Other possible causes:

- The AC associated with the specified
LSM and LIP is in the process of resetting.
- LSM has been physically unseated from
the backplane, or LIP has been removed.
- AC audit has failed to receive the proper
response from the LSM.
- LSM is resetting or reinitializing.
Go to LAN Switch Module, page 29-171,

and LAN Interface Panel, page 29-180.
OSLINK CO LAN communications failure The Central Office LAN has failed. The CO LAN cable has been
disconnected from the CO LAN Ethernet
port of the LIP.
76.5500/29, Rev R 7/07 Page 29-95

Transmission Control Protocol/Internet Protocol (TCP/IP) Alarm Messages

2.32 In order to troubleshoot the alarm message(s) received for the
Transmission Control Protocol/Internet Protocol, use the following table. The first
column of the table lists the possible alarm messages that can be generated for the
TCP/IP. The second column lists a description of the alarm message. The third
column gives a probable cause for the alarm.
Table 2.25 Transmission Control Protocol/Internet Protocol Alarm Messages

PROGFLT PM Data HSO client connection This message displays due to One or more of the following has occurred:
lost abnormal loss of the connection to the - Client-Tellabs 5500/5500S system
central office computer client program, connection has been broken.
over the TCP/IP socket interface. - Client software program has been
terminated.
- Cabling problem between Client-Network
or Network-Tellabs 5500/5500S system.

page 29-225.
SENA Supporting Entity Not Available The active AC is not detecting that the One or more of the following has occurred:
active LSM is not in a normal state in - Reset of the LSM is in progress.
the system. - LSM has been physically unseated from
This message displays when the the backplane.
active AC cannot communicate with - AC audit has failed to receive the proper
the specified LSM. response from the LSM.
- Specified LSM has been removed from the
system.
Go to LAN Switch Module, page 29-171.
Page 29-96 7/07 76.5500/29, Rev R

Timing Reference (REF) Alarm Messages

2.33 In order to troubleshoot the alarm message(s) received for the Timing
Reference, use the following table. The first column of the table lists the possible
alarm messages that can be generated for a REF. The second column lists a
alarm.
Table 2.26 Timing Reference Alarm Messages

SSM Change at the received An autonomous message that is The incoming DS1 synchronization
Synchronization Status Message generated against the REF indicating clock quality level has changed. Go to
detected that a change has been detected in the Timing Reference (REF), page 29-242.
synchronous status message of the
received timing reference (DS1 datalink).
SENA Neither SIM is available Message refers to both SIM modules. Both SIM modules are unable to
Both SIMs are either OOS or ANR or provide synchronization to the system.
OOS-ANR. System switches NTDMs to Both SIM modules are OOS or ANR.
an INT/SLV asynchronous timing mode. Go to Synchronization Interface
Module (SIM), page 29-146.
PROTNA Reference not available for This message refers to a timing The timing reference is being
protection reference (REF). The following state transitioned to/from a state of
transitions will cause this error message: in-service (IS) or
- REF has transitioned from an out-of-service (OOS). Go to Timing
out-of-service, unassigned state to an Reference (REF), page 29-242.
out-of-service, assigned (OOS-AS) state.
The other reference is in-service.
- REF has transitioned from an in-service
(IS) state to out-of-service (OOS) state.
The other reference remains in-service
(IS).
- REF is transitioning from an
out-of-service, assigned (OOS-AS) state
to an in-service (IS) condition. The error
message is actually issued against the
other REF whose condition remains as
out-of-service, assigned (OOS-AS). This
alarm message will not be annunciated
against a reference in the out-of-service,
unassigned (OOS-UAS) state.
SYNC SIM-A and SIM-B are unable to Both SIMs have lost synchronization with The external synchronization reference
synchronize to the reference the external synchronization reference source is not providing an adequate
source. signal. The SIM or the cable from the
synchronization reference source has
faulted. Go to Timing Reference (REF),
page 29-242.
SYNC SIM-A is unable to synchronize to SIM has lost synchronization with the The external synchronization reference
the reference external synchronization reference source is not providing an adequate
page 29-242
SYNC SIM-B is unable to synchronize to SIM has lost synchronization with the The external synchronization reference
the reference external synchronization reference source is not providing an adequate
page 29-242.
76.5500/29, Rev R 7/07 Page 29-97

Table 2.26 Timing Reference Alarm Messages (Continued)

AIS SIM-A and SIM-B have detected Both SIM modules have detected an AIS The external synchronization reference
DS1 AIS on the reference blue alarm condition from the external source is not providing an adequate
synchronization reference source. signal. Also possible, but less likely: the
SIM modules have faulted. Go to
Timing Reference (REF), page 29-242.
AIS SIM-A has detected DS1 AIS on SIM module has detected an AIS blue The external synchronization reference
the reference alarm condition from the external source is not providing an adequate
synchronization reference source. signal. SIM module has faulted. Go to
AIS SIM-B has detected DS1 AIS on SIM module has detected an AIS blue The external synchronization reference
the reference alarm condition from the external source is not providing an adequate
synchronization reference source. signal. SIM module has faulted. Go to
LOF SIM-A and SIM-B have detected SIM-A and SIM-B have detected that the One of the following is the likely
Loss of Frame on the reference clock reference is in a loss of frame problem:
condition. - Provisioned and actual frame formats
do not match. For example, the timing
source is using ESF but the Tellabs
5500 system is provisioned for SF.
- The external timing reference has
failed.
- Both SIM modules are faulty
(unlikely).
Go to Timing Reference (REF),

page 29-242.
LOS SIM-A and SIM-B have detected Both SIM modules have detected a loss The external synchronization reference
Loss of Signal on the reference of signal from the external source is not providing an adequate
synchronization reference source. signal. Either the cable from the
reference source is disconnected from
the SIM modules, or the SIM modules
are faulted.

page 29-242.
LOF SIM-A has detected Loss of Frame SIM-A has detected that the clock One of the following is the likely
on the reference reference is in a loss of frame condition. problem:
- Provisioned and actual frame formats
failed.
- SIM-A has failed.

page 29-242.
Page 29-98 7/07 76.5500/29, Rev R

Table 2.26 Timing Reference Alarm Messages (Continued)

LOF SIM-B has detected Loss of Frame SIM-B has detected that the clock One of the following is the likely
on the reference reference is in a loss of frame condition. problem:
- Provisioned and actual frame formats
failed.
- SIM-B has failed.

page 29-242.
LOS SIM-A has detected Loss of Signal SIM module has detected a loss of signal The external synchronization reference
on the reference from the external synchronization source is not providing an adequate
reference source. signal. Either the cable from the
the SIM module, or the SIM module is
faulted.

page 29-242.
LOS SIM-B has detected Loss of Signal SIM module has detected a loss of signal The external synchronization reference
on the reference from the external synchronization source is not providing an adequate
reference source. signal. Either the cable from the
the SIM module, or the SIM module is
faulted.

page 29-242.
76.5500/29, Rev R 7/07 Page 29-99

Network Element (NE) Alarm Messages

2.34 In order to troubleshoot the alarm message(s) received for the Network
Element, use the following table. The first column of the table lists the possible
alarm messages that can be generated for an NE. The second column lists a
alarm.
Table 2.27 Network Element Alarm Messages

ACOACT ACO activated via push button The Alarm Cutoff (ACO) mechanism The ACO button on the Alarm Interface
has been activated by the ACO Panel was pushed and activated.
push button on the Alarm Interface
Panel. The purpose of this This alarm message may be accompanied
mechanism is to cut off audible by another alarm message related to a
alarms and all alarm panel lamps specific module. Go to the alarm message
that are currently lit. table for the specific module in alarm to
troubleshoot the problem.
MAN Intra-system control LAN x cabling The GC connections on an There are unbalanced copy A and B
has unbalanced GC connections intra-system control LAN cabling are connections on the LAN run.
(where x = 1 to 8) unbalanced.
page 29-230.
MAN Intra-system control LAN x has An intra-system control LAN has There are more than the recommended
exceeded the node limit (where x = exceeded the node limit. number of nodes on the LAN.
1 to 8)
page 29-230.
FRNGSYNC System timing has transitioned from System timing is no longer in Both SIMs are either OOS or ANR.
Synchronous to Asynchronous synchronous mode, but is now in System timing is generated by the
timing asynchronous mode. NTDMs.

(SIM), page 29-146.
SYNC The system has detected a timing Slave (SLV) SIM cannot lock to the There is a problem with one or more of the
mismatch between SIM-A and Master (MSTR) SIM. There is a following:
SIM-B problem with one of the SIMs that - Faulty cable or improperly connected
causes either of the following cable.
problems: - Lack of EMI shielding.
- The SLV SIM is unable to track a - Faulty Master (MSTR) SIM module.
good signal from the MSTR SIM. - Faulty AC backplane connectors.
- The MSTR SIM is transmitting a
signal that is bad and the SLV SIM Go to Synchronization Interface Module
is unable to track it. (SIM), page 29-146.
FRNGSYNC The system is currently in the SIM has reported that it is running in The cause may be one of the following:
free-run synchronization mode free-run mode instead of using a - External timing reference has gone bad
synchronous timing reference. or is missing.
- Synchronization mode of the SIM has
been set to free-running (FRNG) by
means of the ED-EQPT-NE command.
- Both SIMs have failed.

(SIM), page 29-146.
Page 29-100 7/07 76.5500/29, Rev R

Table 2.27 Network Element Alarm Messages (Continued)

HLDOVR The system is currently in the SIM has reported that it is running in The cause may be one of the following:
SYNC holdover synchronization mode holdover mode instead of using a - External timing reference has gone bad
synchronous timing reference. or is missing.
- Synchronization mode of the SIM has
been set to holdover (HLDOVR) by means
of ED-EQPT-NE command.

(SIM), page 29-146.
NTWKSIZE The two networks are mismatched One network copy has gone through Because the size of only one network at a
in network size a network size change, making it time can be changed, this message
different from the other copy. normally appears during a system
expansion after the first network copy has
gone through its size change and before
the second one can do so. If the problem
persists after the second network copy
has gone through its size change, refer to
the Tellabs 5500/5500S Expansion
Manuals for the system core size you are
troubleshooting.
MEA The networks have mismatched Can happen if the NTWKSIZE Because the size of only one network at a
connection memory maps parameter is set different for each time can be changed, this message
NE. normally appears during a system
expansion after the first network copy has
gone through its size change and before
the second one can do so. If the problem
persists after the second network copy
has gone through its size change, refer to
the Tellabs 5500/5500S Expansion
Manuals for the system core size you are
troubleshooting.
TRGTSWVER CCPM NPU software version needs Off-normal condition indicates that Refer to appropriate documentation to
upgrade the CCPMA NPU software version upgrade CCPMA Network Processor Unit
needs to be upgraded when the API (NPU) software.
version number in the CCPMA NPU
software is less than the API version
number of the Tellabs CCPMA
version.
76.5500/29, Rev R 7/07 Page 29-101

Alarm Interface Module (AIM)

2.35 In this section, you will troubleshoot the alarmed Alarm Interface Module
(AIM). You should have completed System Pre-Checks, page 29-64, and been
directed to this section from an alarm message table.
2.36 A spare AIM may be required in order to perform this procedure. Refer to
Tellabs 5500/5500S Software Release Document, 76.5500/16, to verify the correct
__ 1. Edit the alarmed AC out-of-service (OOS) by entering the following
command:
ED-EQPT::AC-x:ctag::::OOS;
Where: x = Either A or B, whichever AC copy is in alarm.

M ctag COMPLD

WARNING: Execution of this command may result in a loss of system redundancy.
M ctag COMPLD
__ 2. Does the system response generate an AIM alarm CLR message for
the alarmed AC?
__ 2.1 If no, follow your company's prescribed procedures for
__ 2.2 If yes, go to step 3.
__ 3. Does the system response generate the following alarm message:

"AIM-A:MN,INT,NSA,08-28,15-07-00,NEND:\"No AIP cable\":,ISLTD"
__ 3.1 If yes, check the cabling from the AIP panel to P2-9 on the
back of the AC. Refer to Figure 2.8, page 29-103. Then
go to step 4, page 29-104.
__ 3.2 If no, go to step 4, page 29-104.
Page 29-102 7/07 76.5500/29, Rev R

Figure 2.8 Cabling from AIP to the AC
AC-A AC-B
P2-9 J10 J12 J2-3

P2-9
EC1 connects to P2-9 J10 J12 J2-3
AC-B, P2-9 (part

number 80.2402
GND
for black, round GND
J11 J13 -48VA

cable)
J11 J13 -48VA
A
B
1
8 6 4 2
5540 AIP
EC4 connects to AC-A, P2-9 (part rear view
number 180.0537 for black, round cable)
76.5500/29, Rev R 7/07 Page 29-103

__ 4. Retrieve the present state of the alarmed AC by entering the following

command:
System response:
M ctag COMPLD

"AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=OOS-ANR"
"AIM-A::HWV=\"81.5504 RE\",ALMPF=1,SN=FL0133435,DT=911216:PST=ANR-EQ"
__ 4.1 If the system response verifies that the alarmed AC is

out-of-service, abnormal (OOS-ANR), go to step 5.
__ 4.2 For all other system responses, follow your company's

prescribed procedures for obtaining technical assistance
or call Tellabs Technical Assistance at 1.800.443.5555
(North America) or 1.630.798.7070 (outside North
America).
__ 5. What is the system response for the alarmed AIM?

__ 5.1 If the system response for the alarmed AIM is abnormal,
unequipped, (ANR-UEQ), go to step 6.
__ 5.2 If the system response for the alarmed AIM is abnormal,

equipped (ANR-EQ), go to step 7.
__ 6. Visually verify that the alarmed AIM is present in the slot.

__ 6.1 If there is a module present in the slot, go to step 7.
__ 6.2 If there is not a module present in the slot, go to step 12,

page 29-106.
__ 7. Diagnose the problem on the alarmed AIM by entering the following

command:
DGN-EQPT::AIM-x:ctag::PH=1,ITER=5;
System response:
M ctag COMPLD
Followed by lines of data similar to the following output:

"AIM-A:PASS-3"
/* Number of iterations that passed */
"AIM-A:FAIL-2,,,0020"
/* Number of iterations that failed */
Page 29-104 7/07 76.5500/29, Rev R

__ 7.1 If the system response shows 0 failed iterations, go to

step 8.
__ 7.2 If the system response shows 1 or more failed iterations,

go to step 11.

command:
System response:
M ctag COMPLD

"AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=OOS-NR"
"AIM-A::HWV=\"81.5504 RE\",ALMPF=1,SN=FL0133435,DT=911216:PST=IS-NR"
__ 8.1 If the system response verifies that the present state of

the AIM is normal (NR), go to step 18, page 29-107.
__ 8.2 For all other system responses, continue to next step.
__ 9. Reseat the module.

__ 10. Diagnose the problem on the alarmed AIM by entering the following
command:
DGN-EQPT::AIM-x:ctag::PH=1,ITER=1;
Where: x = either A or B, whichever AC copy is in alarm.
System response:
M ctag COMPLD

"AIM-A:PASS-1"
"AIM-A:FAIL-0,,,0020"
__ 10.1 If the system response for the AIM shows 0 failed

iterations, return to step 8, page 29-105.
__ 10.2 If the system response for the AIM shows 1 or more failed
iterations, go to step 11.
__ 11. Remove the module.
76.5500/29, Rev R 7/07 Page 29-105

__ 12. Verify that there is no backplane damage by completing the following

steps:
__ 12.1 Obtain sufficient lighting for viewing pins on the
backplane.
__ 12.2 Are all pins extending straight outward from the

backplane?
__ 12.2.1 If backplane damage is suspected, follow

your company's prescribed procedures
__ 12.2.2 If backplane damage is not suspected,

go to step 13.
__ 13. Refer to Tellabs 5500/5500S Software Release Document,

76.5500/16, to verify the correct revision level of the module needed,
depending on feature package and what shelf type you are
troubleshooting.
Note: Module front panel active LED lights within five minutes during normal
system behavior.
__ 14. Insert the new module.
Note: The alarmed AC will reset.
__ 15. Reset the local AC by entering the following command:

INIT-SYS::AC-x:ctag::0;
Where: x = Either A or B, whichever AC copy is standby

(STBY).
System response:
STOPPING DBMS ACCESSES
Standby AC Reset in 30 Seconds...
M ctag COMPLD
Page 29-106 7/07 76.5500/29, Rev R

__ 16. If necessary, log back on to the system by entering the following

command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */
__ 17. Retrieve the present state of OOS AC by entering the following

command:
RTRV-EQPT::AC-x::ctag;
Where: x = Either A or B, whichever AC is out-of-service

(OOS).
System response:
M ctag COMPLD

“AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=OOS-NR”
__ 17.1 If the system response verifies that the standby AC is

out-of-service, normal (OOS-NR), go to step 18.
__ 17.2 If the system response verifies that the standby AC is

out-of-service, abnormal (OOS-ANR), return to step 11,
page 29-70.
__ 18. Edit the OOS AC in-service (IS) by entering the following command:
ED-EQPT::AC-x:ctag::::IS;
Where: x = Either A or B, whichever AC is out-of-service

(OOS).
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-107

__ 19. Does the system response generate the following sync messages
within 40 minutes?
/* Inactive Database Synchronized */
"PRI-A:CL,DISKSYNC,NSA,07-16,14-05-42,NEND:\"CLR - Disk Synchronization with active

AC disk has been lost - Log file processing failure\""
/* Message Log Files Synchronization is complete */
__ 19.1 If yes, go to step 20, page 29-108.


command:
System response when restoration mode is inhibited:

M ctag COMPLD
":INH"
System response when restoration mode is allowed:

M ctag COMPLD
":ALW:UPGRADE=NO"
__ 20.1 If the system response verifies that the system is not in

local restoration mode (INH), go to step 21.
__ 20.2 If the system response verifies that the system is in local

restoration mode (ALW), go to step 22.


M ctag COMPLD

M ctag COMPLD

"AIM-A,EQPT:CL,INT,NSA,02-01,14-52-20,NEND:\" Failed diagnostic \":,ISLTD"
__ 21.1 Does the system response list another alarm message?
__ 21.1.1 If no, go to step 22.
__ 21.1.2 If yes, go to the appropriate section of

this manual to troubleshoot that alarm
message.
Page 29-108 7/07 76.5500/29, Rev R

__ 22. Exit local restoration mode by entering the following command:

EXIT-LOCL-RST:::ctag;
System response:
M ctag COMPLD
__ 23. Retrieve local restoration mode by entering the following command:

System response:
M ctag COMPLD
":INH"
__ 23.1 Verify from the system response that the system is no

longer in local restoration mode (INH).
__ 24. Log off the system by entering the following command:

CANC-USER::uid:ctag;

End of Procedure
76.5500/29, Rev R 7/07 Page 29-109

System Communication Modules (SCM-1 and SCM-2)

2.37 In this section, you will troubleshoot the alarmed System Communication
Modules (SCM-1 and SCM-2). You should have completed System Pre-Checks,
page 29-64, and been directed to this section from an alarm message table.
2.38 A SCM may be required in order to perform this procedure. Refer to
2.39 A Utility Mode (UM) password may be required to perform this procedure
if you are using Data Storage Modules (DSMs).
command:
System response:
M ctag COMPLD

"AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=IS-NR-STBY"
__ 1.1 If the present state of the alarmed AC is out-of-service

(OOS), go to step 5, page 29-111.
__ 1.2 If the present state of the alarmed AC is in-service (IS), go

to step 2.

command:

M ctag COMPLD

M ctag COMPLD
Page 29-110 7/07 76.5500/29, Rev R

__ 3. Does the system response generate an AC alarm CLR message and

a SCM alarm CLR message for the alarmed AC?

command:
System response:
M ctag COMPLD

"SCM-1-A::HWV=\"81.5506A RA\",ALMPF=99,SN=EL0092669,DT=950810:PST=ANR-EQ"

the alarmed AC is out-of-service, abnormal (OOS-ANR),
go to step 5.

America).
__ 5. What is the system response for the present state of the alarmed
SCM?
the alarmed SCM is abnormal, equipped (ANR-EQ), go to
step 7, page 29-112.

the alarmed SCM is abnormal, unequipped (ANR-UEQ),
go to step 6.
__ 6. Visually verify that the alarmed SCM is present in the slot.

__ 6.1 If there is no module present in the slot, go to step 12,
page 29-113.
__ 6.2 If there is a module present in the slot, go to step 15,

page 29-114.
76.5500/29, Rev R 7/07 Page 29-111

__ 7. Diagnose the problem on the alarmed SCM by entering the following

command:
DGN-EQPT::SCM-x-y:ctag::PH=1,ITER=5;
Where: x = 1 or 2.
y = Either A or B, whichever AC copy is in alarm.
System response:
M ctag COMPLD

"SCM-1-A:PASS-3"
"SCM-1-A:FAIL-2,,,0002"
__ 7.1 If the system response for the SCM shows 1 or more

failed iterations, go to step 9, page 29-113.
__ 7.2 If the system response for the SCM shows 0 failed

iterations, go to step 8.

command:
System response:
M ctag COMPLD

"SCM-1-A::HWV=\"81.5506A RA\",ALMPF=99,SN=EL0092669,DT=950810:PST=NR"

the SCM is normal (NR), go to step 18, page 29-115.
__ 8.2 For all other system responses, go to step 9,

page 29-113.
Page 29-112 7/07 76.5500/29, Rev R

Warning:
Handle modules by the edges or face plate. Always wear a properly grounded

__ 10. Diagnose the problem on the alarmed SCM by entering the following
command:
DGN-EQPT::SCM-x-y:ctag::PH=1,ITER=1;
Where: x = 1 or 2.
y = Either A or B, whichever AC copy is in alarm.
System response:
M ctag COMPLD

"SCM-1-A:PASS-1"
"SCM-1-A:FAIL-0"
__ 10.1 If the system response for the SCM shows 1 or more

failed iterations, go to step 11.
__ 10.2 If the system response for the SCM shows 0 failed

iterations, return to step 8, page 29-112.

__ 11.1 Place the module in an anti-static bag and put it in a safe
place.

steps:
backplane.
__ 12.2 If slot backplane contains a fiber shroud, verify that the

fiber shroud does not contain physical damage.

backplane?
76.5500/29, Rev R 7/07 Page 29-113



go to step 13.

troubleshooting.
Note: The alarmed AC will reset.

Where: x = Either A or B, whichever AC copy is standby

(STBY).
System response:
STOPPING DBMS ACCESSES
Standby AC Reset in 30 Seconds...
M ctag COMPLD
__ 16. If necessary, log back on to the system by entering the following

command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */
Page 29-114 7/07 76.5500/29, Rev R

__ 17. Retrieve the present state of out-of-service (OOS) AC by entering the

following command:
Where: x = Either A or B, whichever AC copy is out-of-service

(OOS).
System response:
M ctag COMPLD

“AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=OOS-NR”

the alarmed AC is out-of-service, normal (OOS-NR), go to
step 18, page 29-115.
__ 17.2 For all other system responses, return to step 11,

page 29-70.
__ 18. Edit the alarmed AC in-service (IS) by entering the following

command:
System response:
M ctag COMPLD
__ 19. Does the system response generate both of the following sync
messages within 40 minutes?


76.5500/29, Rev R 7/07 Page 29-115

command:
System response:
M ctag COMPLD


the alarmed AC is in-service, normal, standby
(IS-NR-STBY), go to step 21, page 29-116.

America).


M ctag COMPLD

M ctag COMPLD

"SCM-1-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Failed diagnostic\":,ISLTD"
__ 21.1.1 If no, go to step 22.

message.
__ 22. Log off the system:


End of Procedure
Page 29-116 7/07 76.5500/29, Rev R

Data Storage Module (DSM)

2.40 In this section, you will troubleshoot the alarmed Data Storage Module
(DSM). You should have completed System Pre-Checks, page 29-64, and been
2.41 A spare DSM module and DSM disk may be required in order to perform
this procedure. Refer to Tellabs 5500/5500S Software Release Document,
76.5500/16, to verify the correct revision level of the module needed, depending on
feature package and what shelf type you are troubleshooting.
2.42 A Utility Mode (UM) password may be required to perform this procedure.
__ 1. Retrieve the state of the system security features:
RTRV-SECU-SYS:::ctag;
System response:
M ctag COMPLD

":ACINT=10,TMOUT=9,ABTMOUT=150,MXINV=6,UMLINK=x,
BANNER=CONF"
Where: x = Link number. For AC-A, 1, 2, or 3;

for AC-B, 5, 6, or 7.
command:

M ctag COMPLD

M ctag COMPLD
__ 3. Does the system response generate an AC alarm CLR message and

a DSM alarm CLR message for the alarmed AC?
76.5500/29, Rev R 7/07 Page 29-117

__ 4. Retrieve the present state of the alarmed AC:

System response:
M ctag COMPLD


the alarmed AC is out-of-service, abnormal (OOS-ANR),
go to step 5.

America).
__ 5. Visually verify that the alarmed DSM is present in the slot.


page 29-120.
__ 6. Diagnose the problem on the alarmed DSM by entering the following

command:
DGN-EQPT::DSM-x:ctag::PH=1,ITER=5;
System response:
M ctag COMPLD

"DSM-A:PASS-3"
"DSM-A:FAIL-2,,,0020"

wait for the following output. Then go to step 8,
page 29-119.
"DBMS INACT - sync task waiting for message from ACTIVE AP"

Page 29-118 7/07 76.5500/29, Rev R


command:
System response:
M ctag COMPLD


the HDD is normal (NR) and the alarmed AC is
out-of-service, normal (OOS-NR), go to Completion,
page 29-126.

the HDD is normal (NR), and the alarmed AC is
out-of-service, abnormal (OOS-ANR), go to step 16,
page 29-120.

Where: x = Either A or B, whichever AC copy is in standby.
System response:
M ctag COMPLD
__ 10. Diagnose the problem on the alarmed DSM by entering the following
command:
DGN-EQPT::DSM-x:ctag::PH=1,ITER=1;
System response:
M ctag COMPLD

"DSM-A:PASS-1"
"DSM-A:FAIL-0,,,0020"
__ 10.1 If the system response for the DSM shows 0 failed

iterations, return to step 7.
__ 10.2 If the system response for the DSM shows any failed
iterations, go to step 11, page 29-120.
76.5500/29, Rev R 7/07 Page 29-119

__ 11. Remove the SRM from the DSM, if present.
Warning:

place.

steps:
backplane.

backplane?


go to step 14.

troubleshooting.
EXIT-LOCL-RST::::ctag;
System response:
M ctag COMPLD
Page 29-120 7/07 76.5500/29, Rev R

__ 17. Verify that the system is no longer in local restoration mode by

System response:
M ctag COMPLD

":INH"



__ 19. Insert the SRM.
__ 20. Choose one of the following options:
__ 20.1 If AC-A is in alarm, move the terminal to link 5.
__ 20.2 If AC-B is in alarm, move the terminal to link 1.
__ 21. Log back onto the system by entering the following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
76.5500/29, Rev R 7/07 Page 29-121


command:
System response when restoration mode is inhibited:

M ctag COMPLD
":INH"
System response when restoration mode is allowed:

M ctag COMPLD
":ALW:UPGRADE=NO"
__ 22.1 If the system response verifies that the system is not in

local restoration mode (INH), go to step 23.
__ 22.2 If the system response verifies that the system is in local

restoration mode (ALW), go to Restoral Using
CRTE-EQPT::HDD, page 29-123.
__ 23. Start the local restoration mode by entering the following command:
Note: Entering this command will cancel all system uid (user identifier) variable
definitions.

M ctag COMPLD

M ctag COMPLD
__ 24. Verify that the system is in local restoration mode by entering the
following command:
System response:
M ctag COMPLD

":ALW:UPGRADE=NO"
__ 24.1 Verify from the system response that the system is in local
restoration mode (ALW). Go to Restoral Using
CRTE-EQPT::HDD, page 29-123.
Page 29-122 7/07 76.5500/29, Rev R

Restoral Using CRTE-EQPT::HDD

__ 1. Retrieve your user privilege code by entering the following command:
Where: uid = User ID.
System response:
M ctag COMPLD

__ 1.1 Record your user privilege code (UPC): _____________
__ 2. Retrieve the COPC assigned to the CRTE-EQPT command by

RTRV-SECU-CMD::CRTE-EQPT:ctag;
System response:
M ctag COMPLD

"CRTE-EQPT::COPC=Z9"
__ 2.1 Record the CRTE-EQPT command COPC: ___________
__ 2.2 If the CRTE-EQPT command COPC has the same or

lower numerical and alpha character as your UPC, go to
__ 2.3 If the CRTE-EQPT command COPC does not have the

same or lower numerical and alpha characters as your
UPC, continue to the next step.
__ 3. Edit the CRTE-EQPT command to match your UPC listed in

substep 1.1 by entering the following command:
ED-SECU-CMD::CRTE-EQPT:ctag::COPC=xx;
Where: xx = Value of the UPC listed in substep 1.1.
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-123

__ 4. Retrieve the COPC assigned to the CRTE-EQPT command by

System response:
M ctag COMPLD

"CRTE-EQPT::COPC=A8"
__ 4.1 Verify that the COPC matches the UPC listed in substep
1.1, page 29-123.
__ 5. Create the new DSM by entering the following command:

CRTE-EQPT::HDD-x:ctag;
Where: x = Either A or B, whichever AC is standby (STBY).

System response:
M ctag COMPLD

/* HDD-X:Formatting volume A ...*/
/* HDD-X:Formatting volume B ...*/
/* HDD-X:Formatting volume C ...*/
/* HDD-X:Formatting volume D ...*/
/* HDD-X:Format and partition entire disk complete*/
/* HDD-X:Copying bootloader to disk...*/
/* HDD-X:Copying bootloader to disk complete...*/
/* HDD-X:Copying of DSM replacement files
in progress*/
/* HDD-X:Copying of DSM replacement files complete*/
/* HDD-X:Updating SID...*/
/* HDD-X:Updating SID complete*/
COMPLD


System response:
M ctag COMPLD
__ 6.1 Wait for the following output before continuing with this
procedure:
"DBMS INACT - Sync task waiting for message from ACTIVE AP"
Page 29-124 7/07 76.5500/29, Rev R

__ 7. Log on to the system by entering the following command:


pid = Password.
System response:
M ctag COMPLD
prosecution. */
__ 8. Place the system in local restoration mode by entering the following

command:
System response:
M ctag COMPLD
__ 9. Retrieve the present state of standby AC by entering the following

command:

System response:
M ctag COMPLD

__ 9.1 If the system response verifies that the present states of

HDD-A and RSD-A are normal (NR) or the alarmed AC is
out-of-service, normal (OOS-NR), go to step 10,
page 29-126.

HDD-A and RSD-A are not normal (NR), follow your
company's prescribed procedures for obtaining technical
assistance or call Tellabs Technical Assistance at
1.800.443.5555 (North America) or 1.630.798.7070
__ 9.3 If the system response verifies that the alarmed AC is

out-of-service, abnormal (OOS-ANR), return to step 1,
page 29-64.
76.5500/29, Rev R 7/07 Page 29-125

Completion __ 10. Edit the alarmed AC in-service (IS) by entering the following
command:
System response:
M ctag COMPLD
__ 11. Does the system response generate the following sync messages
within 40 minutes?


command:
System response:
M ctag COMPLD

primary memory (PRI) is normal (NR).


America).
Page 29-126 7/07 76.5500/29, Rev R

__ 13. Create a backup copy to secondary memory by entering the following

command:
CPY-MEM::FROMMEM=PRI,TOMEM=SEC:ctag::ALL;
System response:
M ctag COMPLD
Note: The system copies memory within 10 minutes.
__ 14. Does the system response generate the following SEC alarm CLR
message within 10 minutes?
"SEC-A:CL,NVMEMS,NSA,09-02,10-52-07,NEND:\"CLR - Secondary memory data and program
bundles are invalid\""

__ 15. Retrieve the state of the secondary memory by entering the following
command:
System response:
M ctag COMPLD

“:SEC-A,PGM:yymmdd,hh-mn,FULL,5500FPX.Y.Z,,VALID,ACTIVE”
“:SEC-A,DATA:yymmdd,hh-mn,FULL,5500FPX.Y.Z,system_id,VALID,ACTIVE”
“:SEC-B,PGM:yymmdd,hh-mn,FULL,5500FPX.Y.Z,,VALID,STANDBY”
“:SEC-B,DATA:yymmdd,hh-mn,FULL,5500FPX.Y.Z,system_id,VALID,STANDBY”
__ 15.1 Are the system responses for secondary program (PGM)

and data (DATA) VALID?
__ 15.1.1 If yes, go to step 16.
__ 15.1.2 If no, go to Secondary Memory (SEC),

page 29-214.

System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-127


command:
System response:
M ctag COMPLD
":INH"

__ 18. Was the communication device cable moved during this procedure?


__ 20. Connect and secure the communication device cable to the original
location. Then go to step 21.

pid = Password.
System response:
M ctag COMPLD
prosecution. */
Page 29-128 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

"DSM-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Failed diagnostic\":,ISLTD"
__ 22.1.1 If no, go to step 23.

message.

__ 23.1 If the COPC was not changed in step 3, page 29-123, go
to step 24, page 29-130.
__ 23.2 If the COPC was changed in step 3, page 29-123,

continue to substep 23.3.
__ 23.3 Refer to substep 2.1, page 29-123, and note the COPC
value that was set before beginning this procedure. Then
change the COPC back to its original value by entering
the following command:
ED-SECU-CMD::CRTE-EQPT:ctag::COPC=xx;
Where: xx = Value recorded in substep 2.1, page 29-123.
System response:
M ctag COMPLD
__ 23.4 Retrieve the COPC assigned to the CRTE-EQPT

command to verify it was changed back to its original
value by entering the following command:
System response:
M ctag COMPLD

"CRTE-EQPT::COPC=A8"
__ 23.4.1 Verify that the COPC is set to its original

value listed in substep 2.1, page 29-123.
Then continue to the next step.
76.5500/29, Rev R 7/07 Page 29-129



End of Procedure
Page 29-130 7/07 76.5500/29, Rev R

Administrative Processor Module (APM) or System Processor Module (SPM)

2.43 In this section, you will troubleshoot the alarmed Administrative Processor
Module (APM) or the System Processor Module (SPM). You should have
completed System Pre-Checks, page 29-64, and been directed to this section from
an alarm message table.
2.44 A System Processor Module (SPM) and needle-nosed pliers may be
required in order to perform this procedure. Refer to Tellabs 5500/5500S Software
Release Document, 76.5500/16, to verify the correct revision level of the module
needed, depending on feature package and what shelf type you are
troubleshooting.
Caution:
Performing the following step may cause a system traffic interruption. Follow
internal policy for AC shelf module insertion.
Note: On-site personnel may be required to successfully complete this

procedure.

command:
System response:
M ctag COMPLD
OR
M CTAG DENY

SROF
"AC-A"
/* Requested Operation Failed */
__ 1.1 Did the command deny with a failure code of SROF?
__ 1.1.1 If no, continue to step 2, page 29-132.
__ 1.1.2 If yes, go to step 7, page 29-133.
76.5500/29, Rev R 7/07 Page 29-131


command:
System response:
M ctag COMPLD


the alarmed AC is out-of-service (OOS), go to step 3.

America).
__ 3. Does the system response generate an AC alarm CLR message for

the alarmed AC?

__ 4. Diagnose the problem on the alarmed APM by entering the following

command:
DGN-EQPT::APM-x:ctag::PH=1;
System response:
M ctag COMPLD
Note: The alarmed APM will reboot. Wait for the following output.

"APM-A:PASS-1"
OR
M ctag COMPLD
"APM-A:FAIL-1,,,dgn_code"
Where:
dgn_code = Refer to Tellabs 5500 Command Reference
Manual, 76.5500/13, for diagnostic codes.
Page 29-132 7/07 76.5500/29, Rev R

__ 4.1 If the system response for the APM shows fail, go to step
7, page 29-133.
__ 4.2 If the system response for the APM shows pass, go to


command:
System response:
M ctag COMPLD

"APM-A::HWV=\"81.5501C RD\",ALMPF=1,SN=EL00061798,DT=000106,RAM=128MB:PST=NR"

the APM is normal (NR), go to step 21, page 29-138.
Warning:
Warning:
Mishandling of modules may damage module components. Follow internal
policy for equipment handling.
__ 6. Verify power LEDs are lit on ACPS-1-x and ACPS-2-x.

__ 6.1 If the power LEDs are lit, continue to the next step.
__ 6.2 If the power LEDs are not lit, go to Section 11, Checking
the Power to a Shelf, page 29-1105.
__ 7. Reseat the APM.
76.5500/29, Rev R 7/07 Page 29-133

Note: The alarmed APM will reboot.

command:
System response:
M ctag COMPLD

__ 8.1 Verify the state of the alarmed AC.
__ 8.1.1 If the alarmed AC is OOS-NR or

OOS-ANR, go to step 11, page 29-135.
__ 8.1.2 If the alarmed AC is IS-NR, go to step 20,

page 29-138.
__ 8.1.3 For all other system responses, go to


command:
System response:
M ctag COMPLD
command:
System response:
M ctag COMPLD

__ 10.1 Verify that the alarmed AC is out-of-service (OOS).
Page 29-134 7/07 76.5500/29, Rev R

__ 11. Diagnose the problem on the alarmed APM by entering the following
command:
DGN-EQPT::APM-x:ctag::PH=1;
System response:
M ctag COMPLD
Note: The alarmed APM will reboot. Wait for the following output.

M ctag COMPLD
"APM-A:PASS-1"
or
M ctag COMPLD
"APM-A:FAIL-1,,,dgn_code"
Where:
__ 11.1 If the system response for the APM shows fail or

command denied, go to step 12.
__ 11.2 If the system response for the APM shows pass, go to

step 20, page 29-138.

steps:
backplane.

backplane?


go to step 14.

troubleshooting.
76.5500/29, Rev R 7/07 Page 29-135

__ 15. Visually verify that the jumper settings for the replacement APM match
the jumper settings for the APM that was removed in step 12,
page 29-135. Refer to Figure 2.9, page 29-137.
__ 15.1 If the jumper settings match, place the removed module
in an anti static bag and put it in a safe place. Go to step
16, page 29-137.
__ 15.2 If the jumper settings do not match, reset settings on the

new APM to match the settings on the removed APM.
Needle-nosed pliers may be needed. For additional
information, see substep 15.3 and substep 15.4. After
settings are reset, continue to substep 15.5, page 29-136.
__ 15.3 To set the strapping on the APM for an X.25

communication device, use jumpers J8, J9, and J10 to set
the modes TERE, TIRI, and TIRE. These options affect
link 4 (AC-A) and link 8 (AC-B) only.
__ 15.4 Place the jumper plugs of J8, J9, and J10 over the
adjacent pair of pins as required for interfacing to the
particular external equipment being used. Use the
following chart as a guide:
• Transmit External, Receive External (TERE, default configuration)

Application: Interface to modem link, to packet switching network
J8: Place jumper over pins 2 and 3.
• Transmit Internal, Receive External (TIRE)

Application: Interface to Tellabs 33X packet switch network
J10: Place jumper in storage (only on pin 1).
• Transmit Internal, Receive Internal (TIRI)

Application: Supply transmit and receive clock when unavailable from
external equipment
J10: Place jumper in storage (only on pin 1)
__ 15.5 Place the removed module in an anti-static bag and put it

in a safe place. Then continue to step 16, page 29-137.
Page 29-136 7/07 76.5500/29, Rev R

Figure 2.9 Jumper Settings on the SPM
TERE
J8 1 2 3 1 2 3 J9
configuration to receive
1 transmit Tx clock and
2 receive Rx clock
J10
TIRI
J8 1 2 3 1 2 3 J9
configuration to supply
2 supply Rx clock
J10
TIRE
J8 1 2 3 1 2 3 J9
configuration to supply
2 receive Rx clock
J10
Note 1: The alarmed APM will reboot.
Note 2: Module front panel active LEDs light within five minutes during normal
system behavior.
__ 17. Does the system response generate a LINK alarm CLR message
within 10 minutes?

__ 18. Are any Fault LEDs lit on the alarmed Administrative Complex (AC)?
__ 18.1 If yes, follow your company's prescribed procedures for
76.5500/29, Rev R 7/07 Page 29-137

command:

procedure.
System response:
M ctag COMPLD


the alarmed APM is normal (NR), go to step 20.

America).
__ 20. What is the present state of the alarmed AC?

the alarmed AC is out-of-service, normal (OOS-NR), go to
step 21.


America).
__ 21. Edit the alarmed AC in-service (IS) by entering the following

command:
System response:
M ctag COMPLD
Page 29-138 7/07 76.5500/29, Rev R

__ 22. Does the system response generate the following SYNC messages
within 40 minutes?
\* Inactive Database Synchronized *\


command:
System response:
M ctag COMPLD



America).
76.5500/29, Rev R 7/07 Page 29-139



M ctag COMPLD

M ctag COMPLD

"APM-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Failed diagnostic\":,ISLTD"
__ 24.1.1 If no, go to step 25.

message.
__ 25. Exit the local restoration mode by entering the following command:
System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD
":INH"



End of Procedure
Page 29-140 7/07 76.5500/29, Rev R

Troubleshooting an APM UEQ Alarm

2.45 Perform the following steps to troubleshoot the APM when an APM UEQ
alarm is present.
__ 1. Start a capture file on both admin links, if possible. If you cannot
monitor both admin links, connect to the admin link of the AC on which
you are working.
__ 2. Remove cables from J11, J12, J13, and telnet links from the rear of the
AC. Leave only ASYNC links connected to J10 on the admin link port
(1 or 5) for visibility.
__ 3. Remove the CO LAN cable from the connector on the LIP.
Note: An AC with an unequipped (UEQ) APM will transition to an in-service,

abnormal, standby (IS-ANR-STBY) state. An AC copy switch takes place
if the abnormal (ANR) AC was in an active (ACT) state at the time of the
failure. The other AC should be in an in-service, normal, active
(IS-NR-ACT) state.
__ 4. Unseat the APM that is in the unequipped (UEQ) state on the standby
AC.
__ 5. Unseat the remaining modules on the standby AC, except the SIM and
power supplies.
Caution:
Unseating the SIM and power supplies could be traffic affecting.
__ 6. Verify that there are no bent pins on any of the modules removed from
the standby AC.
steps:
backplane.


backplane?


76.5500/29, Rev R 7/07 Page 29-141

Caution:
Do not remove or unseat the J40 cable. If a cable seating problem is suspected,
follow your company's prescribed procedures for obtaining technical assistance
or call Tellabs Technical Assistance at 1.800.443.5555 (North America) or
__ 8. Inspect the J40 IPC cable on the backplane for proper seating. Correct
any problems before continuing with this procedure.
__ 9. Inspect the AIP ribbon cable that runs between the AIP and the P2-9
port on the AC backplane for proper seating per Tellabs 5500/5500S
Installation Manual, 76.5500/7.
__ 10. Inspect the LIP cable that runs from the LIP to the J2-3 port on the
backplane for proper seating per Tellabs 5500/5500S TCP/IP
Activation and DCC Deactivation Manual, 76.5500/46.
__ 11. Label all LAN cables at the AC side and remove them.
Note: Removing the LAN cables will ensure that the port shelves and network
shelves will not take a download should a problem occur during this
procedure.
__ 12. Reseat the DSM on the standby AC.

__ 13. Once LED activity on the reseated DSM stops, reseat the SCM-1,
SCM-2, AIM, and APM on the standby AC from right to left. Leave the
LSM unseated.
__ 14. Did the system receive a LINK 1 alarm CLR message?
__ 14.2 If no, enter Utility Mode (UM) in order to reload system

files from either the active AC (Replace data storage
module) or from the removable media (Copy a bundle
from removable) to eliminate possible data corruption on
the standby AC. Refer to Section 12, Restoring the
System, page 29-1123, for procedures.
Note: The SRM must be present and visible to the DSM in order to access UM.
Monitor the active AC from the admin port (J10) on the active AC at this
time, if possible.
Page 29-142 7/07 76.5500/29, Rev R

command:

procedure.
System response:
M ctag COMPLD


(IS-NR-STBY), go to step 16.

America).
__ 16. Does the system response generate the following SYNC messages
within 40 minutes?
\* Inactive Database Synchronized *\


command:
System response:
M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-143


(IS-NR-STBY), go to step 18.

America).
__ 18. Replace the LAN cables that you removed in step 11, page 29-142.
__ 19. Replace J11, J12, J13, and the telnet cables that you removed in step
2, page 29-141.
__ 20. Replace the LSM and LIP, if equipped.

M ctag COMPLD

M ctag COMPLD

"APM-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Failed diagnostic\":,ISLTD"
__ 21.1.1 If no, go to step 22.

message.
System response:
M ctag COMPLD
Page 29-144 7/07 76.5500/29, Rev R


command:
System response:
M ctag COMPLD
":INH"



End of Procedure
76.5500/29, Rev R 7/07 Page 29-145

Synchronization Interface Module (SIM)

2.46 In this section, you will troubleshoot the alarmed Synchronization Interface
Module (SIM). You should have completed System Pre-Checks, page 29-64, and
been directed to this section from an alarm message table.
2.47 A spare SIM may be required in order to perform this procedure. Refer to
revision level of the module needed.
__ 1. Retrieve the system timing to verify the inhibit status and the preferred
network status by entering the following command:
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
__ 1.1 If either NC-A or NC-B have a status of

INHSTATUS=INHIBITED, follow your company's
America) for further analysis.
__ 1.2 Verify that one NC copy equals PREFNET=YES and one

NC copy equals PREFNET=NO. If both copies PREFNET
parameters are the same, follow your company's
Page 29-146 7/07 76.5500/29, Rev R

__ 2. Verify that no modules are improperly inhibited from either copy of the
network and that they are listening to the preferred copy data byte, by
entering both of the following commands:
RTRV-BBBC-INH:::ctag;
RTRV-BBBC-INH:::ctag::DUALINH;
__ 2.1 System response has two possible outputs, which are

the same for either command.
System response:
M ctag COMPLD

Modules are properly inhibited:
M ctag RTRV
/* The preferred network copy is currently set to NC-A */
or
Modules are improperly inhibited:
M ctag RTRV
"MM24-0385:ADATA=INH-LOCAL,BDATA=OK-FORCED,ACLK=INH-LOCAL,BCLK=OK-FORCED"
"RMM24-0385:ADATA=INH-LOCAL,BDATA=OK-FORCED,ACLK=INH-LOCAL,BCLK=OK-FORCED"
"MIM96-0385-A:ADATA=INH-LOCAL,BDATA=OK-FORCED,ACLK=INH-LOCAL,BCLK=OK-FORCED"
"MIM96-0385-B:ADATA=INH-LOCAL,BDATA=OK-FORCED,ACLK=INH-LOCAL,BCLK=OK-FORCED"
/* The preferred network copy is currently set to NC-A*/
Note: If the system response indicates INH-PENDING, this means that the data
in the network complex was locally inhibited and is now in a wait period
before switching back to the preferred copy. Depending on the
troubleshooting procedure being performed, it may be necessary to wait
up to 20 minutes for the INH status to finalize.
__ 2.2 If the system response verifies that no modules are

improperly inhibited (INH-xxxx), continue to step 3,
page 29-148.
76.5500/29, Rev R 7/07 Page 29-147

__ 2.3 If the system response verifies that modules are

improperly inhibited (INH-xxxx), enter the RTRV-BBBC
command again, specifying the particular module that is
improperly inhibited:
RTRV-BBBC-INH:[tid]:aid:ctag;
Where: aid = Address of the module that is improperly inhibited.

Example:
RTRV-BBBC-INH::OPM12X4-W0125:ctag;

"OPM12X4-W-0125:ADATA=INH-MIMA,BDATA=OK-FORCED-MIMB,ACLK=INH-MIMA,
BCLK=OK-FORCED-MIMB"
/* If a partial line is displayed, it indicates either an error retrieving data or

unassigned port */
__ 2.4 Perform the appropriate troubleshooting steps before

continuing with this procedure.
Caution:
Do not disconnect the SYNC timing cables from the AC backplane or loss of
timing may result.


M ctag COMPLD

M ctag COMPLD

"SIM-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal error detected \":,ISLTD"
Page 29-148 7/07 76.5500/29, Rev R

__ 3.1 Are any of the following alarm posted against the Tellabs
5500/5500S system?
"SIM-A:MN,PAINTGRT,NSA,08-28,14-22-24,NEND:\"Signal to NTDM-A lost (possible cable

missing)\":,ISLTD"
"SIM-A:MN,PAINTGRT,NSA,08-28,14-22-24,NEND:\"Signal to NTDM-B lost (possible cable

missing)\":,ISLTD"
"SIM-A:MN,PAINTGRT,NSA,08-28,14-22-24,NEND:\"Signal to CCSM on SH1 lost (possible

cable missing)\":,ISLTD"
"SIM-A:MN,PAINTGRT,NSA,08-28,14-22-24,NEND:\"Signal to CCSM on SH2 lost (possible

cable missing)\":,ISLTD"
__ 4. If the Tellabs 5500 system has an Standard switch core, go to step 5,

page 29-149.
If the Tellabs 5500 system has a Hybrid switch core, go to step 6,
page 29-154.
If the Tellabs 5500 system has a CCS switch core, go to step 7,
page 29-161.
__ 5. Perform the following steps to verify that the SYNC timing cables in an
Standard switch core are connected properly. Refer to Table 2.28,
page 29-150, through Table 2.30, page 29-151, for the information
necessary to complete this task. Depending on your circumstances,
choose from the following options to verify the cabling:
- Go hand over hand from one connector to the other.
- Check the labels for matching numbers.
- Verify the color coding.
The sync timing cables are attached to the backplane of both
Administrative Complex A (AC-A) and Administrative Complex B
(AC-B) and then to the backplane of the Center Stage Shelf Copy A
(CSS-A) and the Center Stage Shelf Copy B (CSS-B). Refer to Figure
2.10, page 29-153, and Figure 2.11, page 29-154.
__ 5.1 Verify that one end of the SYNC timing cable is connected
to the J4 connector on the backplane of the CSS-A and
one end of the cable is connected to the J37 connector on
the backplane of AC-B.
to the J4 connector on the backplane of the CSS-B and
the backplane of AC-A.
76.5500/29, Rev R 7/07 Page 29-149

to the J3 connector on the backplane of the CSS-B one
end of the cable is connected to the J36 connector on the
backplane of AC-A.
__ 5.5 If any of the SYNC timing cables are incorrectly cabled,

correct the cabling problem and go to step 24,
page 29-169.
__ 5.6 If the SYNC timing cables are correctly cabled, follow your
1.800.443.5555 (North America) or 1.630.798.7070
Note: For a 1024 or smaller system, these SYNC cables are available in 8-foot,
10-foot, 20-foot, 30-foot, 40-foot, and 50-foot lengths. For a 1536, 2048, or
3072 size system, all cables are 100 feet. In any system, all four SYNC
cables must be the same length to prevent timing skew.
Table 2.28 SYNC Cables for AC Shelves Rev B through I in a 1536, 2048, or 3072 (Standard Core Switch)
Network
Administrative Complex Complex Color Coding Part Number
SYNC A NC-A
J37 SYNC A Red label 50.2190
J3
SYNC A NC-B
J36 SYNC A White label 50.2191
J3
SYNC B NC-A
J37 SYNC B Yellow label 50.2192
J4
SYNC B NC-B
J36 SYNC B Black label 50.2193
J4
Page 29-150 7/07 76.5500/29, Rev R

Table 2.29 SYNC Cables for AC Shelves Rev J or Later in a 1536, 2048, or 3072 System (Standard Core Switch)
Network
Administrative Complex Complex Color Coding Part Number
SYNC A NC-A
J37 SYNC A Red label 50.2196
J3
SYNC A NC-B
J36 SYNC A White label 50.2197
J3
SYNC B NC-A
J37 SYNC B Yellow label 50.2198
J4
SYNC B NC-B
J36 SYNC B Black label 50.2199
J4
NC-A J3
10 feet 50.21202
red
20 feet 50.21203
J3 (SIM A) J37
40 feet 50.21205
50 feet 50.21206
AC-A J36 to 8 feet 50.21207
NC-B J3
10 feet 50.21208
white
20 feet 50.21209
J3 (SIM A) J36
40 feet 50.21211
50 feet 50.21212
76.5500/29, Rev R 7/07 Page 29-151

NC-A J4
10 feet 50.21214
yellow
20 feet 50.21215
J4 (SIM B) J37
40 feet 50.21217
50 feet 50.21218
AC-B J36 to 8 feet 50.21219
NC-B J4
10 feet 50.21220
black
20 feet 50.21221 SYNC CABLE SYNC CABLE
J4 (SIM B) J36
40 feet 50.21223
50 feet 50.21224
Page 29-152 7/07 76.5500/29, Rev R

Figure 2.10 SIM to NTDM SYNC Cabling for 0550B Center Stage Shelf (Standard Switch Core)
AC-B CSS-B
GND
J40 P12 P11 P10 P9 P8 P7 P6
-48VB
J2
J1
J4 J3
J11
J5
T
J12
P2-9 J10 J12 J2-3 T
J6
P13
P14
T J36 P3
GND P15
GND
T J37
J11 J13 -48VA
-48VA
#2 - J36 AC-B to J4 CSS-B
#1 - J37 AC-B to J4 CSS-A

CABLE PROVIDES
EXTERNAL
REFERENCE
CROSS-COPY LINK
AC-A CSS-A
GND
J40 P12 P11 P10 P9 P8 P7 P6
-48VB
J2
J1
J4 J3
J11
J5
T
J12
T
J6
P2-9 J10 J12 J2-3
P13
P14
J36 P3
GND P15
GND
J37
J11 J13 -48VA -48VA
#2 - J36 AC-A to J3 CSS-B
#1 - J37 AC-A to J3 CSS-A
76.5500/29, Rev R 7/07 Page 29-153

Figure 2.11 SIM to NTDM SYNC Cabling for 0550G Center Stage Shelf (Standard Switch Core)
AC-B CSS-B
J40
J3 J4
P2-9 J10 J12 J2-3
T J36
GND
T J37 J11 J13 -48VA
#1 - J36 AC-B to J4 CSS-B
AC cross-copy #2 - J37 AC-B to J4 CSS-A

link cable
AC-A CSS-A
J40
J3 J4
P2-9 J10 J12 J2-3
J36
GND
J37
J11 J13 -48VA
#1 - J36 AC-A to J3 CSS-B
#2 - J37 AC-A to J3 CSS-A
__ 6. Perform the following steps to verify that the SYNC timing cables in a
hybrid switch core are connected properly. Refer to Table 2.31,
necessary to complete this task. Depending on your circumstances,
choose from the following options to verify the cabling:
Page 29-154 7/07 76.5500/29, Rev R


(AC-B), to the backplane of the Center Stage Shelf Copy A (CSS-A)
and the Center Stage Shelf Copy B (CSS-B), and to the LAN Timing
Interface Panel Copy A (LTIP-A), and to LAN Timing Interface Panel
Copy B (LTIP-B). Refer to Figure 2.12, page 29-159, and Figure 2.13,
page 29-160.
to the J3 connector on the LTIP-1 and one end is
connected to the J35 connector on the backplane of
AC-A.
AC-B.
AC-A.
AC-B.

page 29-169.
1.800.443.5555 (North America) or 1.630.798.7070
76.5500/29, Rev R 7/07 Page 29-155

Table 2.31 SDL to Twinax SYNC Cables for AC Shelves Rev J or Later to 128, 256, 1024 Standard Core Switch
AC
Shelf Part
NC-A J3
10 feet 50.21202
red
20 feet 50.21203
J3 (SIM A) J37
40 feet 50.21205
50 feet 50.21206
AC-A J36 to 8 feet 50.21207
NC-B J3
10 feet 50.21208
white
J3 (SIM A) J36
40 feet 50.21211
50 feet 50.21212
NC-A J4
10 feet 50.21214
yellow
J4 (SIM B) J37
40 feet 50.21217
50 feet 50.21218
AC-B J36 to 8 feet 50.21219
NC-B J4
10 feet 50.21220
black
J4 (SIM B) J36
40 feet 50.21223
50 feet 50.21224
Page 29-156 7/07 76.5500/29, Rev R


to LTIP-1 J2
J1 J2
NC-A J2 to 50 feet 50.21236

LTIP-1 J1
J2 J1

to LTIP-2 J2
J1 J2
NC-B J2 to 50 feet 50.21249

LTIP-2 J1
J2 J1
Table 2.33 Twinax to Twinax SYNC Cables for AC Shelves Rev

J or Later in a 1536, 2048, or 3072 Standard Core Switch
AC-A NC-A
J37 J3
AC-A NC-B
J36 J3
AC-B NC-A
J37 J4
AC-B NC-B
J36 J4
76.5500/29, Rev R 7/07 Page 29-157


LTIP-1 LTIP-1 J3
red
AC-A to AC-A J34 to 150.2517

LTIP-2 LTIP-2 J3
white
AC-B to AC-B J35 to 150.2528

LTIP-1 LTIP-1 J4
yellow
AC-B to AC-B J34 to 150.2539

LTIP-2 LTIP-2 J4
black

LTIP-1 LTIP-1 J3
red
AC-A to AC-A J34 to 150.2522

LTIP-2 LTIP-2 J3
white
AC-B to AC-B J35 to 150.2533

LTIP-1 LTIP-1 J4
yellow
AC-B to AC-B J34 to 150.2544

LTIP-2 LTIP-2 J4
black
Page 29-158 7/07 76.5500/29, Rev R

Figure 2.12 256 or 1024 SIM to NTDM SYNC Cabling Diagram Using 0550B CSS Shelf
Center Stage Switch Shelf

AC-B NC Copy B
GND
Ret B
J40 J43
P12 P11 P10 P9 P8 P7 P6
-48VB
J62
J2
J1
-48B J4 J3
J59
J65
J11
J66 T
J5
P2-9 J10 J12 J2-3
J12
J67 T
J6
J68 J14
J69 J34 T J23 J22 J15 (B)
(A) (B) (A)
J70 P13
J25 J24 J16
J35 T J17 (B)
J56 (A) (B) (A)
Ret A P14
J41 J27 J26 J18
J57 J36 T Net B (B) J19 (B) P3
J53 (A)
(A) P15
J42 J29 J28 J61 GND
J37 T J20
J58 Net A (A) (B) J21 (B)
(A) J11 J13
-48A -48VA
SCM-1 (LAN) SCM-2 (LAN) J72 J71
J36 AC-B to J4 CSS1-B
J37 AC-B to J4 CSS1-A

part number 50.0332
cable provides external
reference cross-copy link from
AC-A J40 to AC-B J40
AC-A NC Copy A
GND
Ret B
J40 J43 P12 P11 P10 P9 P8 P7 P6
-48VB
J62
J2
J1
-48B J4 J3
J59
J65
J11
J66 T
J5
P2-9 J10 J12 J2-3
J12
T
J6
J67
J68 J14
J69 J34 T J23 J22 J15 (B)
(A) (B) (A)
J70 P13
J25 J24 J16
J35 T J17 (B)
J56 (A) (B) (A) P14
Ret A
J41 J27 J26 J18 P3
J57 J36 T Net B (A) (B) J19 (B)
J53 (A) P15
J42 J29 J28 J61 GND
J37 T J20
J58 Net A (A) (B) J21 (B)
(A) J11 J13
-48A -48VA
J36 AC-A to J3 CSS1-B
J37 AC-A to J3 CSS1-A

J35 AC-A to J3 LTIP-1
LTIP 1 LTIP 2
P4 P4
J7 J8 J9 J10 J3 J4 J2 J1 J11 J12 J13 J14 J7 J8 J9 J10 J3 J4 J2 J1 J11 J12 J13 J14
OUT IN AUX B AUX A LAN B LAN A OUT IN AUX B AUX A LAN B LAN A
LAN B LAN A AUX B AUX A LAN B LAN A AUX B AUX A
SYNC A SYNC B EXT REF LEGACY NTD SYNC A SYNC B EXT REF LEGACY NTD

J35 AC-B to J4 LTIP-1
76.5500/29, Rev R 7/07 Page 29-159

Figure 2.13 1536, 2048, 3072, or 4608 SIM to NTDM SYNC Cabling Diagram Using 0550G CSS Shelf

AC-B NC Copy B
Ret B
J40 J43
J62 J3 J4
-48B
J59
J65
J66
P2-9 J10 J12 J2-3

J67
J68 J14
J69 J34 T J23 J22 J15 (B)
(A) (B) (A)
J70
J25 J24 J16
J35 T J17 (B)
J56 (A) (B) (A)
Ret A
J41 J27 J26 J18
J57 J36 T Net B (A) (B) J19 (B)
J53 (A)
J42 J29 J28 J61
J37 T J20
J58 T Net A (A) (B) J21 (B)
(A) J11 J13
-48A
J36 AC-B to J4 CSS1-B

J37 AC-B to J4 CSS1-A
part number 50.0332
reference cross-copy link from Center Stage Switch Shelf
AC-A J40 to AC-B J40 AC-A NC Copy A
Ret B
J40 J43
J3 J4
J62
-48B
J59
J65
J66
P2-9 J10 J12 J2-3

J67
J68 J14
J69 J34 T J23 J22 J15 (B)
(A) (B) (A)
J70
J25 J24 J16
J35 T J17 (B)
J56 (A) (B) (A)
Ret A
J41 J27 J26 J18
J57 J36 T Net B (A) (B) J19 (B)
J53 (A)
J42 J29 J28 J61
J37 T J20
J58 Net A (A) (B) J21 (B)
(A) J11 J13
-48A
J36 AC-A to J3 CSS1-B
J37 AC-A to J3 CSS1-A

LTIP 1 LTIP 2
P4 P4

Page 29-160 7/07 76.5500/29, Rev R

__ 7. Perform the following steps to verify that the SYNC timing cables in a
CCS switch core are connected properly.
For a CCS switch core with DS1 Support, refer to Table 2.31,
necessary to complete this task.
For a CCS switch core without DS1 support, refer to Table 2.34,
page 29-158, and Table 2.35, page 29-158, for the information
necessary to complete this task.
Depending on your circumstances, choose from the following options
to verify the cabling:
(AC-B), to the LAN Timing Interface Panel Copy A (LTIP-A), and to
LAN Timing Interface Panel Copy B (LTIP-B). Refer to Figure 2.14,
page 29-162, and Figure 2.15, page 29-163.
to the J4 connector on LTIP-1 and one end of the cable is
AC-B.
AC-A.
AC-B.
AC-A.

page 29-169.
1.800.443.5555 (North America) or 1.630.798.7070
76.5500/29, Rev R 7/07 Page 29-161

Figure 2.14 4608 SIM to LTIP SYNC Cabling Diagram Using CCS Switch Core in a Stacked Configuration
AC-B
Ret B
J40 J43
J62
-48B
J59
J65
J66
P2-9 J10 J12 J2-3

J67
J68 J14
J69 J34 T J23 J22 J15 (B)
(A) (B) (A)
J70
J25 J24 J16
J35 T J17 (B)
J56 (A) (B) (A)
Ret A
J41 J27 J26 J18
J57 J36 T Net B (A) (B) J19 (B)
J53 (A)
J42 J29 J28 J61
J37 T J20
J58 T Net A (A) (B) J21 (B)
(A) J11 J13
-48A
part number 50.0332

reference cross-copy link from
AC-A J40 to AC-B J40 AC-A
Ret B
J40 J43
J62
-48B
J59
J65
J66
P2-9 J10 J12 J2-3

J67
J68 J14
J69 J34 T J23 J22 J15 (B)
(A) (B) (A)
J70
J25 J24 J16
J35 T J17 (B)
J56 (A) (B) (A)
Ret A
J41 J27 J26 J18
J57 J36 T Net B (A) (B) J19 (B)
J53 (A)
J42 J29 J28 J61
J37 T J20
J58 Net A (A) (B) J21 (B)
(A) J11 J13
-48A

LTIP 1 LTIP 2
P4 P4

Page 29-162 7/07 76.5500/29, Rev R

Figure 2.15 4608 SYNC Cabling Diagram with Consolidated Core Switch (No DS1 Support)
cable part number 50.0332
provides external reference
cross-copy link from AC-A J40
to AC-B J40
AC-A AC-B
J40 J43 J40 J43
Ret B Ret B
J62 J62
-48B -48B
J59
J59
J65
J65
J66
J66
P2-9 J10 J12 J2-3 P2-9 J10 J12 J2-3

J67 J67
J68 J23 J22 J15 J14 J68
J69 J34 T J23 J22 J15 J14
(A) (B) (A) (B) J69 J34 T (A) (B)
J70 (A) (B)
J70
J25 J24 J17 J16 J25 J24 J17 J16
J35 T (A) (B) (A) (B) J35 T
J56 J56 (A) (B) (A) (B)
Ret A Ret A
J36 T J41 J27 J26 J19 J18 J41 J27 J26 J19 J18
Net B (A) (B) J36 T
J57 J53 (A) (B) J57 Net B (A) (B) (A) (B)
J53
J42 J29 J28 J21 J20 J61 J61
J37 T J37 T J42 J29 J28 J21 J20
J58 Net A (A) (B) (A) (B) J58 Net A (A) (B) (A) (B)
J11 J13 J11 J13
-48A -48A
SCM-1 (LAN) SCM-2 (LAN) J72 J71 SCM-1 (LAN) SCM-2 (LAN) J72 J71

J35 AC-A to J3 LTIP-1 J35 AC-B to J4 LTIP-1
P4 P4
J7 J8 J9 J10 J2 J1 J11 J12 J13 J14 J7 J8 J9 J10 J2 J1 J11 J12 J13 J14
J4 P2 J36 J37 J53 OUT IN J4 P2 J36 J37 J53 OUT IN
LAN B LAN A AUX B AUX A J3 P1 AUX B AUX A LAN B LAN A LAN B LAN A AUX B AUX A J3 P1 AUX B AUX A LAN B LAN A
LTIP-1 LTIP-2
76.5500/29, Rev R 7/07 Page 29-163

Caution:
The following command may cause a temporary system traffic interruption.
Follow internal policy for SIM copy switching.
__ 8. Edit the alarmed SIM out-of-service (OOS) by entering the following

command:
ED-EQPT::SIM-x:ctag::::OOS;
Note: During normal system behavior, module front panel in-service LEDs turn
off.

M ctag COMPLD

M ctag COMPLD
__ 9. Does editing the SIM out-of-service (OOS) cause a system traffic

interruption?
Note: Follow internal policy for measuring system traffic flow.
__ 9.1 If no, go to step 10.
__ 9.2 If yes, follow your company's prescribed procedures for

__ 10. Does the system response generate a SIM alarm CLR message for
the alarmed SIM?

Page 29-164 7/07 76.5500/29, Rev R

command:
System response:
M ctag COMPLD

"SIM-A::HWV=81.5507A RB,ALMPF=99,TMG=MSTR,SN=IL2345481,DT=960311:
PST=OOS-ANR-EQ-AS"

the alarmed SIM is out-of-service, abnormal, equipped
(OOS-ANR-EQ), go to step 13, page 29-166.

the alarmed SIM is out-of-service, abnormal, unequipped
(OOS-ANR-UEQ), go to step 12.
Warning:
__ 12. Visually verify that the alarmed SIM is present in the slot.
page 29-166.

page 29-167.
76.5500/29, Rev R 7/07 Page 29-165

__ 13. Diagnose the problem on the alarmed SIM by entering the following
command:
Note: Module front panel LEDs light for approximately one minute during normal
system behavior.
DGN-EQPT::SIM-x:ctag::,ITER=5;
System response:
M ctag COMPLD

"SIM-A:PASS-2"
"SIM-A:FAIL-3,,,dgn_code"
Where:
go to step 15.

step 14.
command:
System response:
M ctag COMPLD

"SIM-A::HWV=81.5507A RB,ALMPF=99,TMG=MSTR,SN=IL2345481,DT=960311:PST=OOS-NR"

the SIM is out-of-service, normal (OOS-NR), go to step
22, page 29-168.
Page 29-166 7/07 76.5500/29, Rev R


steps:
backplane.


backplane?


go to step 17.

troubleshooting.
__ 19. After a two minute module initialization, what is the front panel LED
status of the module?
__ 19.1 If the LEDs remain lit, go to step 20.
__ 19.2 If the LEDs turn off, go to step 21, page 29-168.
__ 20. Diagnose the problem on the alarmed SIM by entering the following
command:
Note: Module front panel LEDs light for approximately one minute during normal
system behavior.
DGN-EQPT::SIM-x:ctag::,ITER=5;
System response:
M ctag COMPLD

"SIM-A:PASS-5"
"SIM-A:FAIL-0"
76.5500/29, Rev R 7/07 Page 29-167


follow your company's prescribed procedures for

step 21.
command:
System response:
M ctag COMPLD

"AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=IS-ACT"
"SIM-A::HWV=81.5507A RB,ALMPF=99,TMG=MSTR,SN=IL2345481,DT=960311:PST=OOS-NR"
__ 21.1 If the present state of the SIM is out-of-service, normal

(OOS-NR), go to step 22.
__ 21.2 If the present state of the SIM is out-of-service, abnormal

(OOS-ANR), return to step 11, page 29-70.
__ 22. Edit the alarmed SIM in-service (IS) by entering the following
command:
ED-EQPT::SIM-x:ctag::::IS;
System response:
M ctag COMPLD
__ 23. Does the system response generate a SIM PROTNA alarm CLR
message for the alarmed SIM?

Page 29-168 7/07 76.5500/29, Rev R

command:
System response:
M ctag COMPLD

"AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=IS-ACT"
"SIM-A::HWV=81.5507A RB,ALMPF=99,TMG=SLV,SN=IL2345481,DT=960311:PST=IS-NR"

the SIM is in-service, normal (IS-NR), go to step 25.

America).
__ 25. What is the system response for the timing of the alarmed SIM?
__ 25.1 If the system response for the timing of the alarmed SIM
is configured for slave (TMG=SLV), go to step 26.

America).


M ctag COMPLD

M ctag COMPLD

__ 26.1.1 If no, go to step 27.

message.
76.5500/29, Rev R 7/07 Page 29-169

System response:
M ctag COMPLD
__ 28. Verify that local restoration mode has been exited by entering the
following command:
System response:
M ctag COMPLD
":INH"



End of Procedure
Page 29-170 7/07 76.5500/29, Rev R

LAN Switch Module

2.48 In this section, you will troubleshoot the alarmed LAN Switch Module
(LSM). You should have completed System Pre-Checks, page 29-64, and been
2.49 A spare LSM may be required in order to perform this procedure. Refer to
Caution:
Editing the active (ACT) AC to an out-of-service (OOS) state causes the system
to temporarily lose communication.
__ 1. Retrieve all alarm conditions on the equipment by entering the

following command:
RTRV-ALM-EQPT:::ctag;

M ctag COMPLD

M ctag COMPLD

"APM-A:MN,CONTCOM,NSA,07-10,09-31-42,NEND:\"AC backplane APM-LSM LAN failure
detected\":,ISLTD"
"LSM-A:MN,INT,NSA,07-10,09-31-43,NEND:\"Internal failure or APM-LSM LAN cable

disconnected\":,ISLTD"
"APM-A:MN,CONTCOM,NSA,07-10,09-35-37,NEND:\"AC front panel APM-LSM LAN failure

detected\":,ISLTD"
"LSM-A:MN,INT,NSA,07-10,09-35-37,NEND:\"Internal failure or APM-LSM LAN cable

disconnected\":,ISLTD
"LSM-A:MN,CONTCOM,NSA,07-10,09-38-44,NEND:\"LSM to LSM LAN Comm Lost at XCOPY port

(missing cable?)\":,ISLTD";
"LAN-0001:MN,PROTNA,NSA,07-10,09-38-44,NEND:\"Failure on internal LAN - part of path

not available for protection\":,ISLTD";
"LSM-B:MN,CONTCOM,NSA,07-10,09-38-44,NEND:\"LSM to LSM LAN Comm Lost at XCOPY port

(missing cable?)\":,ISLTD";
"LSM-B:MN,CONTCOM,NSA,06-15,10-30-18,NEND:\"CO LAN cable failure detected\":,ISLTD"
"LSM-A:MAN,SC,06-15,08-55-36,NEND:\"LAN Interface Panel (LIP) miscabled on port

LAN-1\":,ISLTD"
76.5500/29, Rev R 7/07 Page 29-171

__ 1.1 If the following messages are retrieved, verify that the

LAN cable between J71 and J72, on the backplane on the
AC shelf, is secure.
AC backplane APM-LSM LAN failure detected
Internal failure or APM-LSM LAN cable disconnected
__ 1.2 If the following messages are retrieved, verify that the

LAN cable between APM and LSM on front panel of both
modules is secure.
AC front panel APM-LSM LAN failure detected
Internal failure or APM-LSM LAN cable disconnected
__ 1.3 If the following messages are retrieved, verify the LAN

cable connected to the X-COPY port of LIP-A and LIP-B
is secure. Go to Troubleshooting Control LAN in System
with Hybrid or CCS Switch Core, page 29-238.
LSM to LSM LAN Comm Lost at XCOPY port (missing

cable?)
Failure on internal LAN - part of path not available

for protection
__ 1.4 If the following message is retrieved, follow local

procedures for troubleshooting CO LAN.
CO LAN cable failure detected
__ 1.5 If the following message is retrieved, suspect that the

cable is plugged into the wrong connector on the LIP or
LTIP. Go to Checking LTIP to LIP Cables, page 29-464.
LAN Interface Panel (LIP) miscabled on port {LAN-2|LAN-3|LAN-4|LAN-5|LAN-6|

LAN-7|LAN-8|SIM-A|SIM-B|XCOPY|COLAN}
__ 1.6 If a different message is retrieved, or if verifying the LIP

and LSM cables does not clear the alarm, go to step 2,
page 29-173.
Page 29-172 7/07 76.5500/29, Rev R

__ 2. Retrieve the present state of both ACs, and the state of the LSMs, by
entering the following command.
M ctag RTRV

"AC-A::SWV=5500FPX.Y.Z.R [LITE], ALMPF=99:PST=IS-NR-ACT"
"APM-A::HWV=\"81.5501CRD\",ALMPF=99,SN=EL00061798,DT=000106,RAM=128MB:PST=NR"
"LSM-A::HWV=\"81.55103 RA\",ALMPF=99,SN=EL00052316,DT=060106,MACADDR2=AE12DC79CA44
:PST=NR"
"SCM-2-A::HWV=\"81.5506B RA\",ALMPF=99,SN=EL0092670,DT=950810:PST=NR"
"SEC-A::,ALMPF=99:PST=NR"
"REMV-A::,ALMPF=99:PST=NR"
"AIM-A::HWV=\"81.5504 RE\",ALMPF=99,SN=FL0133435,DT=911216:PST=NR"
"ACPS-1-A::HWV=81.5534,ALMPF=99:PST=NR"
"SIM-A::HWV=81.5507A RA,ALMPF=99,TMG=SLV,SN=IL2488248,DT=941207:PST=IS-NR"
"LIP-A::HWV=\"81.55130 RA\",ALMPF=99:PST=NR"
"AC-B::SWV=5500FPX.Y.Z.R [LITE], ALMPF=99:PST=IS-NR-STBY"

"APM-B::HWV=\"81.5501B RD\",ALMPF=99,SN=EL00061798,DT=000106,RAM=32MB:PST=ANR"
"LSM-B::HWV=\"81.55103 RA\",ALMPF=99,SN=EL00052354,DT=060106,MACADDR2=
AE12DC79CD54:PST=ANR-EQ"
"SCM-1-B::HWV=\"81.5506A RA\",ALMPF=99,SN=EL0092669,DT=950810:PST=NR"
"SCM-2-B::HWV=\"81.5506B RA\",ALMPF=99,SN=EL0092670,DT=950810:PST=NR"
"PRI-B::,ALMPF=99:PST=NR"
"SEC-B::,ALMPF=99:PST=NR"
"REMV-B::,ALMPF=99:PST=NR"
"AIM-B::HWV=\"81.5504 RE\",ALMPF=99,SN=FL0133435,DT=911216:PST=NR"
"ACPS-1-B::HWV=81.5534,ALMPF=99:PST=NR"
"ACPS-2-B::HWV=81.5534,ALMPF=99:PST=NR"
"SIM-B::HWV=81.5507ARA,ALMPF=99,TMG=SLV,SN=IL2488248,DT=941207:PST=IS-NR"
"LIP-B::HWV=\"81.55130 RA\",ALMPF=99:PST=NR"
__ 2.1 If the LSM and LIP are unequipped (UEQ), go to LAN

Interface Panel, page 29-180.
__ 2.2 If the LSM is abnormal (ANR), verify the LAN cabling

connections at the following points before continuing with
the troubleshooting procedure.
• between the front panels of the LSM and the APM

• between J71 and J72 on the backplane of the AC
• between the X-COPY connector on LIP-A and LIP-B
__ 2.3 If both LSMs are unequipped (UEQ) troubleshoot the
LSM on the active AC first.
76.5500/29, Rev R 7/07 Page 29-173

__ 3. Edit the AC supporting the alarmed LSM out-of-service (OOS) by


M ctag COMPLD

M ctag COMPLD

command:

procedure.
System response:
M ctag COMPLD

"AC-B::SWV=5500FPX.Y.Z,ALMPF=99:PST=OOS-NR"
"LSM-B::HWV=\"81.55103 RA\",ALMPF=99,SN=EL00052354,DT=060106,MACADDR2=00B0C7051CDF:
PST=ANR-EQ"
__ 4.1 If the system response for the present state of the

alarmed AC is out-of-service, go to step 5.

America).
__ 5. What is the present state of the alarmed LSM?

alarmed LSM is abnormal, unequipped (ANR-UEQ), go to
step 6.

alarmed LSM is abnormal, equipped (ANR-EQ), go to
step 7.
__ 5.3 For all other system responses, go to step 21,

page 29-178.
Page 29-174 7/07 76.5500/29, Rev R

__ 6. Visually verify that the alarmed LSM is present in the slot.

page 29-176.

page 29-177.
__ 7. Diagnose the problem on the alarmed LSM by entering the following

command:
DGN-EQPT::LSM-x:ctag;
System response if no failures are detected:

M ctag COMPLD

"LSM-A:PASS-1"
"LSM-A:FAIL-0"
System response if failures are detected:

M ctag COMPLD

"LSM-A:PASS-0"
"LSM-A:FAIL-1,,,xxxx"
Where: xxxx = Diagnostic failure code for LSM in hexadecimal

value (0-F).
0001 - EEPROM diagnostic failure
0002 - LAN Controller diagnostic failure
0003 - MAC address diagnostic failure
0004 - Chip Select diagnostic failure
0005 - Rear cable interconnect failure
0006 - Front cable interconnect failure.
__ 7.1 If the system response for the LSM shows pass, go to

__ 7.2 If the system response for the LSM shows fail, go to step
9, page 29-176.
76.5500/29, Rev R 7/07 Page 29-175

__ 8. Retrieve the present state of the AC supporting the alarmed LSM by

System response:
M ctag COMPLD

PST=ANR-EQ"

the LSM is normal (NR), go to step 22, page 29-178.
Warning:
__ 9. Disconnect the Ethernet cable from the front panel connector of the
LSM.
__ 11. Reconnect the Ethernet cable to the front panel connector.
__ 12. Wait three minutes for module initialization to complete.
__ 12.1 If the Fault LED remains lit, go to step 13, page 29-177.
__ 12.2 If the Fault LED goes out, go to step 21, page 29-178.
Page 29-176 7/07 76.5500/29, Rev R

__ 13. Diagnose the problem on the alarmed LSM by entering the following
command:
DGN-EQPT::LSM-x:ctag::PH=1;
System response:
M ctag COMPLD

"LSM-A:PASS-1"
Or
"LSM-A:FAIL-1,,,xxxx"
Where: xxxx = Diagnostic failure code for LSM in hexadecimal

value (0-F).
0001 - EEPROM diagnostic failure
0002 - LAN Controller diagnostic failure
0003 - MAC address diagnostic failure
0004 - Chip Select diagnostic failure
0005 - Rear cable interconnect failure
0006 - Front cable interconnect failure.
__ 13.1 If the system response for the LSM shows fail, go to
step 15.
__ 13.2 If the system response for the LSM shows pass, go to

step 21, page 29-178.
__ 14. Disconnect the Ethernet cable from the front panel connector of the
LSM.
steps:
backplane.

backplane?


go to step 17.

troubleshooting.
76.5500/29, Rev R 7/07 Page 29-177


__ 19. Reconnect the Ethernet cable to the front panel connector.
__ 20. After a three minute module initialization, determine the status of the
module LEDs?
__ 20.1 If the Fault LED remains lit, follow your company's
America).
__ 20.2 If the Fault LED turns off, go to step 21.
command:
System response:
M ctag COMPLD

PST=NR"

the alarmed LSM is normal (NR), and the alarmed AC is

America).
__ 22. Edit the AC in-service (IS) by entering the following command:

Where: x = Either A or B, whichever AC copy is out-of-service

(OOS).
System response:
M ctag COMPLD


Page 29-178 7/07 76.5500/29, Rev R

Note: Sync messages are displayed by the system within 40 minutes (5 to 15

minutes average) during normal system behavior.
__ 23. Retrieve the present state of the ACs by entering the following
command:
RTRV-EQPT::AC-A&&-B::ctag;
System response:
M ctag COMPLD

"AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=IS-NR-[ACT/STBY]"
"AC-B::SWV=5500FPX.Y.Z,ALMPF=99:PST=IS-NR-[ACT/STBY]"

both AC-A and AC-B is in-service, normal (IS-NR), go to
step 24.

America).


M ctag COMPLD

M ctag COMPLD

"LSM-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Failed diagnostic\":,ISLTD"
__ 24.1.1 If no, go to step 25.

message.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-179

LAN Interface Panel

2.50 In this section, you will troubleshoot the alarmed LAN Interface Panel
(LIP). You should have completed System Pre-Checks, page 29-64, and been
2.51 A spare LIP may be required in order to perform this procedure. Refer to

M ctag COMPLD

M ctag COMPLD

"LSM-A:MN,CONTCOM,NSA,06-15,15-51-02,NEND:\"LSM to LSM LAN Comm Lost at XCOPY port
(missing cable?)\":,ISLTD"

not available for protection\":,ISLTD"
"CGC-SH2-10:MN,CONTCOM,NSA,06-15,15-51-05,NEND:\"CGC to LSM LAN Comm Lost at LAN A

port (missing cable?)\":,ISLTD"
"LIP-B:MN,INT,NSA,06-15,15-51-06,NEND:\"Module removed or LSM to LIP cable

disconnected\":,ISLTD"
"APM-A:MN,CONTCOM,NSA,07-10,09-35-37,NEND:\"AC front panel APM-LSM LAN failure

detected\":,ISLTD"
"APM-A:MN,CONTCOM,NSA,07-10,09-31-42,NEND:\"AC backplane APM-LSM LAN failure

detected\":,ISLTD"
__ 1.1 If the system response lists the following alarm message,

check the cabling between LIP-A and LIP-B and replace
if necessary. Go to troubleshooting Troubleshooting
Control LAN in System with Hybrid or CCS Switch Core,
page 29-238.
"LSM to LSM LAN Comm Lost at XCOPY port (missing cable?)\"
Page 29-180 7/07 76.5500/29, Rev R


check the short jumper cable between the LSM and APM
on the front of the Administrative complex and replace if
necessary.
"AC front panel APM-LSM LAN failure detected\"

check the short jumper cable between J71 and J72 on the
backplane of the Administrative complex and replace if
necessary.
"AC backplane APM-LSM LAN failure detected\"
__ 1.4 If the system response lists another alarm message, refer

to the appropriate section to troubleshoot.

System response:
M ctag RTRV

"AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=IS-ANR-STBY"
"APM-A::HWV=81.5501CRG,ALMPF=99,SN=UD1390021,DT=060523,RAM=128MB:PST=NR"
"LSM-A::,ALMPF=99:PST=UEQ"
"SCM-1-A::HWV=81.5506A RO,ALMPF=99,SN=OI1299876,DT=001031:PST=NR"
"SCM-2-A::HWV=81.5506B RH,ALMPF=99,SN=UZ0240471,DT=060125:PST=NR"
"SIM-A::HWV=81.5507B RA,ALMPF=99,TMG=MSTR,SN=OI1290740,DT=001103:PST=IS-NR"
"LIP-A::,ALMPF=99:PST=ANR-UEQ"
"AC-B::SWV=5500FP11.0A801,ALMPF=99:PST=IS-NR-ACT"
"APM-B::HWV=81.5501C RG,ALMPF=99,SN=UD1390015,DT=060524,RAM=128MB:PST=NR"
"LSM-B::HWV=81.55103 R12,ALMPF=99,SN=UV1170211,DT=060515,
MACADDR2=0001AF160E7A:PST=NR"
"SCM-2-B::HWV=81.5506B RH,ALMPF=99,SN=UZ0240422,DT=060125:PST=NR"
76.5500/29, Rev R 7/07 Page 29-181

"SIM-B::HWV=81.5507B RA,ALMPF=99,TMG=SLV,SN=OI1290732,DT=001103:PST=IS-NR"
"LIP-B::HWV=81.55130 RA,ALMPF=99:PST=NR"
__ 2.1 Verify from the system response that one AC is

IS-NR-ACT and the other AC is IS-ANR-STBY. If the ACs
are not in-service, take the appropriate troubleshooting
steps before continuing.
__ 2.2 Verify the status of the LSM on the AC supporting the

faulted LIP. If the LIP is unequipped (UNEQ), the LSM will
also be unequipped. Troubleshoot the LIP first. Go to
step 3.
__ 2.3 If both ACs show an unequipped (UNEQ) LIP and LSM,

troubleshoot the LIP on the standby AC first. Go to step 3.
__ 3. Edit the AC that is supporting the alarmed LIP out-of-service (OOS) by

Where: x = Either A or B.

M ctag COMPLD

M ctag COMPLD
Page 29-182 7/07 76.5500/29, Rev R

__ 4. Retrieve the status of the ACs by entering the following command.

System response:
M ctag RTRV

"AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=OOS-STBY"
"LSM-A::HWV=81.55103 RA,ALMPF=99,SN=UV0694866,DT=060310,
MACADDR2=0001AF160E7A:PST=NR"
"LIP-A::HWV=81.55130 RA,ALMPF=99:PST=ANR-UNEQ"
"AC-B::SWV=5500FP11.0A507,ALMPF=99:PST=IS-NR-ACT"
"LSM-B::HWV=81.55103 RA,ALMPF=99,SN=UV0694866,DT=060310,
MACADDR2=0001AF161A7C:PST=NR"
"LIP-A::HWV=81.55130 RA,ALMPF=99:PST=NR"
__ 4.1 Verify that the AC that is supporting the alarmed LIP is

OOS.
__ 5. Verify that the LSM to LIP cable is securely connected. Refer to Figure
2.19, page 29-194.
__ 5.1 If the cable is not securely connected, tighten the cable
connection and proceed to step 6, page 29-183.
__ 5.2 If the LSM to LIP cable (part number 180.0401) is

securely connected (from connector J2-3 on the AC
backplace to the LSM connector on the LIP), proceed to
paragraph 2.52, page 29-184.
__ 6. Determine if a clear message similar to the following appears.

"LIP-B:CL,INT,NSA,06-15,15-53-57,NEND:\"CLR - Module removed or LSM to LIP cable
disconnected\""
__ 6.1 If the fault does not clear, proceed to paragraph 2.52,

page 29-184.
__ 6.2 If the fault clears, proceed to step 38, page 29-201.
76.5500/29, Rev R 7/07 Page 29-183

Remove Faulted LIP or LIP 2.52 Follow the procedure below to replace the faulted LIP. The AC is powered
Cable down before replacing the faulted LIP. The next step determines which AC copy is
standby (STBY).
Note 1: If any command does not complete correctly (DENY appears, or the
system response is other than what it should be), refer to that
command’s section in the Tellabs 5500/5500S Command Reference
Manual, 76.5500/13, and its Error Conditions section for additional
information. The most common error messages are IISP, IDRG, and
IBMS, which indicate a syntax problem. Correct the problem and
proceed to the next step.
If unsure how to resolve the problem, please contact Tellabs Technical

Assistance Center at 1.800.443.5555, or follow your company
procedures for obtaining technical assistance.
Note 2: During this procedure, certain messages may appear on the terminal
connected to the operations link being used, depending on whether this
link was optioned with System Integrity Report Messages (SIRPT)
activated via the ED-CHAN command. These messages are a normal
part of the procedure and should be ignored.
__ 7. Retrieve the state of both ACs by entering the following command:

System response:
M ctag RTRV

"SIM-A::HWV=82.5507A R07,ALMPF=99,TMG=SLV,SN=LI5766507,DT=971222:PST=IS-NR"
"AC-B::SWV=5500FPX.Y.Z,ALMPF=99:PST=IS-NR-ACT"
"SIM-B::HWV=82.5507A R07,ALMPF=99,TMG=MSTR,SN=LI5767868,DT=971222:PST=IS-NR"
__ 7.1 Verify from the response that one AC is IS-NR-ACT and

the other is OOS-ANR-STBY. On the checklist below,
record which AC has which state.
__ 7.2 The response should also show that one SIM is

TMG=SLV and the other is TMG=MSTR. Record these
also, based on your system response:
_____ AC is IS-NR-ACT
_____ AC is OOS-ANR-STBY
_____ TMG=SLV
_____ TMG=MSTR
Page 29-184 7/07 76.5500/29, Rev R

__ 8. Based on information about the SIM retrieved in the previous step,

select one of the following options:
__ 8.1 If the SIM in the AC copy that is OOS is TMG=MSTR, go
to step 9, page 29-185 to change the SIM in the OOS AC
copy from TMG=MSTR to TMG=SLV.
__ 8.2 If the SIM in the AC copy that is OOS is TMG=SLV, go to

step 12, page 29-187 to power down the STBY AC.
AC-x Is STBY or OOS, SIM-x __ 9. If the SIM in the OOS AC copy is TMG=MSTR, switch the SIM from
Is MSTR MSTR to SLV by entering the following command:
SW-DX-EQPT::SIM-y:ctag;
Where: y = SIM that is MSTR, in AC-A or AC-B.

System response when CPC is turned off:
M ctag COMPLD
System response when CPC is turned on:

WARNING: Redundancy status may be altered - potential loss of traffic.
Do you want to Execute this command? (Y or N)
M ctag COMPLD
__ 9.2 Wait at least one minute before proceeding.
__ 10. Retrieve the status of the SIM by entering the following command:
RTRV-EQPT::AC-y:ctag;
Where: y = AC copy that is OOS.
System response:
M ctag COMPLD

"AC-B::SWV=5500FPX.Y.Z,ALMPF=99:PST=IS-NR-STBY"
"SIM-B::HWV=82.5507A R07,ALMPF=99,TMG=SLV,SN=LI5767868,DT=971222:PST=IS-NR"
__ 10.1 Verify from the system response that the timing of the SIM
in the OOS AC is now slave (TMG=SLV).
76.5500/29, Rev R 7/07 Page 29-185

__ 11. Retrieve the system timing:

RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
__ 11.1 Verify from the system response that the SIM which was
master (MSTR) is now slave (TMG=SLV). Record the
MASTER/SLAVE relationship (TMG=MSTR and
TMG=SLV). The active LED on the MASTER SIM is on
constantly. Only one SIM is Master, the other is Slave:
SIM in Copy A or B TMG = MSTR TMG = SLV
SIM-A
SIM-B

NTDM-A
NTDM-B
CCSM-SH1-9
CCSM-SH2-9
Page 29-186 7/07 76.5500/29, Rev R

__ 11.3 Verify that both NTDMs and CCSMs are listening to the
same MASTER SIM. Refer to step 11.2, page 29-186.
Note: If the system response shows any response other than the NTDM timing
“TMG = SIM-x” where “x” equals the Master SIM, contact Tellabs
Customer Services or your next level of technical support.
Editing SIM-x to OOS __ 12. Edit OOS the 5507A/B Synchronization Interface Module (SIM) in the
OOS AC by entering the following command:
ED-EQPT::SIM-x:ctag::::OOS;
Where: x = A or B, the OOS AC.

System response when CPC is turned off:
M ctag COMPLD
System response when CPC is turned on:

WARNING: Execution of this command may result in a loss of traffic/service.
Do you want to Execute this command? (Y or N)
M ctag COMPLD
__ 13. Retrieve the current state of both ACs by entering the following
command:
System response:
M ctag RTRV

"SIM-A::HWV=82.5507AR07,ALMPF=99,TMG=MSTR,SN=LI5766507,DT=971222:PST=IS-NR"
"AC-B::SWV=5500FPX.Y.Z,ALMPF=99:PST=OOS-ANR"
"SIM-B::HWV=82.5507AR07,ALMPF=99,TMG=SLV,SN=LI5767868,DT=971222:PST=OOS-NR"
__ 13.1 Verify from the response that the OOS AC SIM is OOS
and its TMG is SLV.
_____ AC to be cabled is OOS-NR or OOS-ANR

_____ SIM=OOS-NR
_____ TMG=SLV
__ 13.2 Verify from the response that the other AC is now

IS-NR-ACT and its TMG=MSTR.
_____ AC=IS-NR-ACT
_____ TMG=MSTR
_____ SIM=IS-NR
76.5500/29, Rev R 7/07 Page 29-187

Caution:
The OOS AC must have its TMG=SLV; if it is not, DO NOT PROCEED. Call
Tellabs Customer Service at 1.800.443.5555.
Communications with the system via the links on the STBY AC Shelf is lost until
the shelf is powered again. Disregard any LINK alarms during this procedure.
Electrostatic Discharge (ESD) may damage system components. Wear a static

protection wriststrap, or practice your prescribed precautions for ESD before
performing any of these steps that involve touching modules or the system itself.
Be sure there is no single removable media (SRM) activity on the 5502D Data
Storage Modules (DSMs) at this time. The SRM access LEDs of the DSMs
should be off, indicating they are idle.
__ 14. Retrive which link you are currently logged into.

System response:
M ctag COMPLD

Where: N = Link number (1 or 5).
__ 14.1 If you are currently logged into link 5, and the state of
AC-A is IS-NR-ACT, go to step 17. Otherwise, go to
step 15.
__ 14.2 If you are currently logged into link 1, and the state of
AC-B is IS-NR-ACT, go to step 17. Otherwise, go to
step 15.
__ 15. Log off of link 1 or link 5 by entering the following command:


Page 29-188 7/07 76.5500/29, Rev R

__ 16. Using one of the following links, log onto the system by entering the
following command.
- log onto link 1 if the state of AC-A from step 13, page 29-187,
IS-NR-ACT
- log onto link 5 if the state of AC-B from step 13, page 29-187, is
IS-NR-ACT

pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
Turning Breakers Off __ 17. Choose one of the following steps, depending on the size of the
system.
__ 17.1 If the OOS AC Shelf is AC-A on a 256, 1024, 1536, 2048,
or 3072 system, shut off breakers A1 and B1 on the
Tellabs 5550 breaker and alarm panel at the top of the
administrative complex frame.
__ 17.2 If the system is a Tellabs 5500S (128) and the OOS AC

shelf is AC-A, shut off breakers A2 and B2.
__ 17.3 If the OOS AC Shelf is AC-B on a 128, 256, 1024, 1536,

2048, or 3072 system, shut off breakers A4 and B4 on the
__ 17.4 If the AC shelf is configured for a Consolidated Core

Switch (CCS) or Hybrid Core Switch (HCS) in a
side-by-side configuration, shut off breaker 3 for AC-A or
AC-B.
2.53 Continue with step 18, page 29-190.
76.5500/29, Rev R 7/07 Page 29-189

Determining AC Shelf __ 18. Remove the transparent plastic (Lexan) rear panels, if installed, from
Revision the upper Administrative Shelf (AC-B) and from the lower
Administrative Shelf (AC-A).
__ 19. The two AC shelf scenarios are Rev B through I and Rev J or later. The
AC shelf version can be identified by the product revision sticker,
which is located on the upper left-hand corner on the front of the shelf.
Refer to Figure 2.16. Choose one of the following options.
__ 19.1 If the AC shelf is Rev B through I, continue with AC Shelf
Rev B Through I, page 29-191.
__ 19.2 If the AC shelf is Rev J or later, proceed to AC Shelf Rev

J or Later, page 29-191.
Note: For FP11.0.1 or later, the 5506A SCM or the 5506B SCM may be inserted
into the SCM1 or SCM2 slot in the Administrative Complex Shelf of the
Tellabs 5500/5500S system. For Tellabs 5500/5500S systems running
FP11.0, only the 5506B SCM may be inserted into the SCM2 slot.
Figure 2.16 Fully Populated AC Shelf Showing Revision Label Placement
PSAC 1 AUX2 2 CPM 3 APM 4 AIM 5 SCM2 6 SCM1 7 DSM 8 SIM 9 PSAC 10
PSAC
81.5534
81.0550A LSM
81.55103
SPM
81.5501C
AIM
81.5504
SCM
81.5506A/B*
SCM
81.5506A/B
DSM
81.5502D
SIM
81.5507B
Rev. J PCMCIA reference

alarms
HARD
APM DRIVE ref A
ACTIVITY
CPM ref B
selected
reference
ref A
power
power
ref B
holdover
free run
module
status
LIP fault
in-service
active
master
in-service active
in-service
fault fault active active active
fault
fault fault fault

static
81.5534
PSAC
sensitive
REMOVABLE
STORAGE DRIVE
slot PSAC 1 AUX2 2 CPM 3 APM 4 AIM 5 SCM2 6 SCM1 7 DSM 8 SIM 9 PSAC 10
assignments 1 2 3 4 5 6 7 8 9 10
* The 5506A may be inserted into the SCM2 slot only in Tellabs 5500/5500S systems running FP11.0.1 or later.
Otherwise, the 5506B must be used.
Page 29-190 7/07 76.5500/29, Rev R

AC Shelf Rev B Through I __ 20. For 81.0550A Rev B through I Administrative Complex Shelf
backplane, use a voltage measuring device to measure the voltage in
the power leads. The present voltage should be less than 10Vdc. If the
voltage from any checkpoint is more than 10Vdc, DO NOT CONTINUE
with this procedure. Resolve the problem before continuing with this
procedure.
- Check voltage between J60, Ret A power lead (black) and J61,
-48A power lead (red), located on the lower right-hand corner of
the AC backplane.
- Check voltage between J62, Ret B power lead (black) and J63,
-48B power lead (red), located on the upper left-hand corner of the
AC backplane.
__ 20.1 Continue with step 21.
AC Shelf Rev J or Later __ 21. For a 81.0550A Rev J or later Administrative Complex Shelf
backplane, use a voltage measuring device to measure the voltage in
the power leads. The present voltage should be less than 10Vdc. If the
voltage from any checkpoint is more than 10Vdc, DO NOT CONTINUE
with this procedure. Resolve the problem before continuing with this
procedure.
- Check voltage between J61, Ret A power lead (black) and J61,
-48A power lead (red), located in the lower right-hand corner of the
AC backplane.
- Check voltage between J62, Ret B power lead (black) and J62,
-48B power lead (red), located in the upper left-hand corner of the
AC backplane.
__ 21.1 If only replacing the LIP cable, go to step 23,
page 29-193, for a rev B through I AC backplane. Go to or
step 24, page 29-194 for a rev J or later AC backplane.
__ 21.2 If replacing the entire LIP, continue to step 22,

page 29-191.
Removing LIP Cables __ 22. Before removing the LIPs installed on AC-A and AC-B the cross-copy
cable must be removed. Remove the following cables from the faulted
LIP. Refer to Figure 2.17, page 192.
__ 22.1 Remove the cross-copy cable from the LIP XCOPY
connector on faulted LIP.
__ 22.2 Remove the LAN 1 (for use with the Consolidated Core
Switch Shelf) cable from the LAN-1 connector from the
faulted LIP.
__ 22.3 Remove the CO LAN cable from the CO-LAN connector

on the faulted LIP.
__ 22.4 Remove the LSM cable (part number 180.0401).
76.5500/29, Rev R 7/07 Page 29-191

Figure 2.17 LIP Connectors
RS232
DEBUG
LIP
STATUS
LIP cross-copy Ethernet CO LAN
CO LAN
(XCOPY)
XCOPY
connector
23
connector
1
SIM-A
SIM-B
14
15
LAN-8
LAN-7
18
22
LAN-6
used on Consolidated
LAN-5
17
21
Core Switch Network
(CCS)
LAN-3
LAN-4
16
20
LAN-1
LAN-2
19
0
LSM connector
LSM
Cable 180.0401
AIP
reserved for future use
__ 22.5 Continue with Replacing LIP, page 29-193.
Page 29-192 7/07 76.5500/29, Rev R

Replacing LIP
Warning:
When working on the rear of the AC rack to remove the LIP, be careful not
to disturb the cables already in place. Take particular care not to disturb the
5507A/B Synchronous Interface Modules (SIMs) output cables, which are
located on the lower left of the AC backplane. Disconnecting or dislodging these
cables can disrupt the entire system.
Removing Cables AC Shelf __ 23. On the OOS AC, perform the following substeps to remove cable
Rev B Through I 180.0401 which is connected to LSM connector on the LIP and J2-3
on the backplane of the AC. Refer to Figure 2.18.
__ 23.1 On the LIP, loosen the two screws on the side of the
cable.
__ 23.2 Remove the cable from the standoff screws on the

administrative bracket using the captive nut.
__ 23.3 Remove the 180.0401 cable from the LSM Connector on

the LIP.
__ 23.4 Continue with step 25, page 29-195.
Figure 2.18 Location of Bracket Assembly on AC Shelf Backplane Rev B Through I
captive screw
administrative shelf
bracket assembly
cable
LIP 80.55130
J2-3
captive screw captive nut(s)
76.5500/29, Rev R 7/07 Page 29-193

Removing Cables AC Shelf __ 24. On the OOS AC, remove cable 180.0401, which is connected to the
Rev J and Later LSM connector of the LIP and J2-3 on the backplane of the AC.
Remove the cable from the standoff screws on the backplane using
the captive nuts. Refer to Figure 2.19, page 29-194.
Figure 2.19 Example Rear of AC Rack Showing the 55130 LIPs Installed on an Unpowered System
cable 180.0401 connected to the J2-3

(96 pin) DIN connector on the upper
AC (AC-B)
LAN Interface Panel (LIP), 80.55130
LSM connector
LAN jumper cable (J71/J72),

150.1189
cable 180.040 connected to the J2-3

(96 pin) DIN connector on the lower
AC (AC-A)
LAN Interface Panel (LIP),

80.55130
LSM connector
transparent plastic (Lexan)
rear panel (shaded area)
LAN jumper cable (J71/J72),
150.1189
Page 29-194 7/07 76.5500/29, Rev R

Removing the LIP __ 25. If only replacing the LIP cable, go to step 30, page 29-195.
__ 26. Remove the LIP.
Install Replacement LIP __ 27. Mount the replacement LIP assembly over the open holes in the rack
on the right side of the backplane.
__ 27.1 For an AC shelf located in the top position of the rack,
install the LIP in screw holes numbered 67 and 79,
counting up from the base of the rack.
__ 27.2 For an AC shelf located in the bottom position of the rack,

install the LIP in screw holes numbered 23 and 35,
counting up from the base of the rack.
Note: If necessary, the plastic edge guard on the rack may need to be trimmed
for a flush LIP installation. A ring cutter may be used for a clean cut.
__ 28. Insert the screws into the holes on top and bottom of the panel.
__ 29. Tighten the screws in the holes on top and bottom of the panel. Refer
to Figure 2.20.
Figure 2.20 Tightening the LIP Screws to the Rack
__ 30. Connect one end of cable 180.0401 to the LSM connector on the LIP.
Refer to Figure 2.17, page 29-192 for a diagram of the LIP.
76.5500/29, Rev R 7/07 Page 29-195

__ 31. Connect the other end to the J2-3 connector on the AC backplane.
Refer to Figure 2.19, page 29-194 for an example LIP cable installed
on the backplane. Refer to Figure 2.24, page 29-198 for the location
of the (96 pin) DIN connector on the backplane of the new AC-A.
__ 31.1 Loosen the hex nuts on the side of the cable. This will
allow for adjustment of the cable so it mates properly with
the connector.
__ 31.2 Tighten the hex nuts after the cable is fully seated. Refer
__ 31.3 Tighten the captive screws on the top and bottom of the
connector to fit securely to the backplane.
Figure 2.21 LIP Installed on Rack with Cable Connected to J2-3 Connector on AC Backplane
cable 180.0401
connected to the
J2-3 connector on
the AC backplane
LAN Interface
Panel (LIP),
80.55130
LSM
connector
__ 32. Install the cross copy cable into the XCOPY connector in the LIP. This
cable connects the two LIPs from AC-A to AC-B. Refer to Figure 2.17,
page 29-192 for a diagram of the LIP and connector locations.
__ 33. Install the CO LAN cable into the CO LAN connector in the LIP.
__ 34. Install the LIP LAN-1 cable from the LIP on AC-A to the J14 LAN A
connector on the LTIP. Refer to Figure 2.22, page 29-197 for an
example LIP with cables connected. Refer to Figure 2.23,
page 29-197, for an illustration of the LTIP connectors.
Page 29-196 7/07 76.5500/29, Rev R

Figure 2.22 LIP with Cables Installed
Figure 2.23 5580 LTIP Connectors
to J1 connector on center switch shelf

LTIP-2 = to LAN-1 connector on LIP-B

LTIP-1 = to LAN-1 connector on LIP-A
to P31 connector on CCS shelf
LTIP-1 = to J35 on AC-A
LTIP-1 = to J35 on AC-B

LTIP-1 and LTIP-2 =

LTIP-1 and LTIP-2 =
LTIP-1 and LTIP-2 =
P4
T
R
GND
J7 J8 J9 J10 J3 P3 J4 P4 J36 J37 J53 J2 J1 J11 J12 J13 J14
LAN B LAN A AUX B AUX A OUT1 OUT2 BITS OUT IN AUX B AUX A LAN B LAN A
CGCM SlOT 11 SYNC A SYNC B EXT.REF. LEGACY NTD CGCM SlOT 10
76.5500/29, Rev R 7/07 Page 29-197

Figure 2.24 View of AC Shelf Backplane Rev J and Later
Ret B
J62
J40 J43
-48B
J59 LIP cable
J65 connector
J66
J2-3
P2-9 J10 J12 J2-3
J67
J68 J14
J69 J34 T J23 J22 J15 (B)
(A) (B) (A)
J70
J25 J24 J16
J35 T J17 (B)
J56 (A) (B) (A)
T
S Ret A
J41 J27 J26 J18
J57
R J36 T Net B (B) J19 (B)
(A)
J53 (A)
J42 J29 J28 J61
J37 T J20
J58 Net A (A) (B) J21 (A)
(A) J11 J13
-48A
jumper cable connectors

for cable part number
150.1189
Page 29-198 7/07 76.5500/29, Rev R

Figure 2.25 Rear of AC Shelves Revision J and Later with the 55130 LIPs
cable 180.0401 connected

to the J2-3 connector
AC-B AC-A
A RET
B RET
FRAME
-48A
A RET
-48B
B RET
FRAME ALARM NO NO
-48A
-48B
ALARM NO NO 4 4 4 4 CONTACTS C C
4 4 4 4 CONTACTS C C Caution NC NC
Caution 3 3 3 3
3 3 3 3 NC NC 48 Volts
48 Volts 2 2 2 2 IN 4 IN 4
2 2 2 2 IN 4 IN 4 1 1 1 1 RET 4 RET 4
1 1 1 1 RET 4 RET 4
IN 3 IN 3
IN 3 IN 3 B Ret B Feeds B Ret B Feeds SHELF RET 3 RET 3
B Ret B Feeds B Ret B Feeds SHELF RET 3 RET 3 ALARM
ALARM
GND
GND
Ret B J43
Ret B J43 J40
J40 J40 J43
J40 J43 -48VB
-48VB
J62
J62
-48VA J59
-48VA J59
J65 J59
J65 J59 J66 J65
J66 J65
J66
J66
J10 J12
J10 J12 P2-9 P2-9 J10 J12 P2-3
J2-3
P2-9 P2-9 J10 J12 P2-3
J2-3
J67
J30
J31
J23
J22
J15
J14
J67
J30
J31
J23
J22
J15
J14
J68 J14
J68 J14 J23 J22 J15
J23 J22 J15 J56 J69 J34 T (B) (B)
(B)
(B)
J56 J69 J34 T (B) (B)
(B) (B)
(B) J70
J32
J33
J25
J24
J17
J16
J70
J32
J33
J25
J24
J17
J16
J25 J24 J16

J25 J24 J16 J53 J35 T J17 (A)
(A)
J53 J35 T J17 (A) J56 J57 (A) (A) (A)
J56 J57 (A) (A) (A) Ret A
J34
J35
J41
J27
J26
J19
J18
Ret A J41 J27 J26 J18
J34
J35
J41
J27
J26
J19
J18
J41 J27 J26 J18 J57 J36 T Net B (B) J19 (B)
(B) GND
J57 J36 T J19 (B) GND J53 (B)
J53 Net B (B) (B) J58 (B)
J58 (B)
J61
J61 J42 J29 J28 J20
J36
J37
J42
J29
J28
J21
J20
J42 J29 J28 J20 J58 J37 T Net A (A) (A) J21
J36
J37
J42
J29
J28
J21
J20
J58 J37 T Net A (A) (A) J21 (A)

(A)
(A)
J11 J13
(A)
(A) J11 J13 -48VA
-48VA J11 J13 -48VA
J11 J13 -48VA SCM-1 (LAN) SCM-2 (LAN) J72 J71
LAN Interface LAN Interface

-48 48V 48V -48
Panel (LIP), Panel (LIP),
RET RET
A A B B
TB1 64 64
80.55130 80.55130
EC1 1 EC2 EC3 1 EC4
8 7 6 5 4 3 2 1
76.5500/29, Rev R 7/07 Page 29-199

__ 35. Choose one of the following steps, depending on the size of the
system.
__ 35.1 If the AC Shelf is AC-A on a 256, 1024, 1536, 2048, or
3072 system, turn on breakers A1 and B1 on the Tellabs
5550 breaker and alarm panel at the top of the
__ 35.2 If the system is a Tellabs 5500S (128) and the OOS AC

shelf is AC-A, turn on breakers A2 and B2.
__ 35.3 If the AC Shelf is AC-B on a 128, 256, 1024, 1536, 2048,

or 3072 system, turn on breakers A4 and B4 on the
__ 35.4 If the AC shelf is configured for a Consolidated Core

Switch (CCS) or Hybrid Core Switch (HCS) in a
side-by-side configuration, turn on breaker 3 for AC-A or
AC-B.
__ 36. Retrieve the status of the AC supporting the faulted LIP, and verify the
AC and the SIM are OOS-NR by entering the following command:
Where: x = A or B.
System response:
M CTAG COMPLD

"LSM-B::HWV=81.55103 R12,ALMPF=99,SN=UV1170211,DT=060515,MACADDR2=0001AF170E5C:
PST=NR"
"SIM-B::HWV=81.5507B RA,ALMPF=99,TMG=SLV,SN=OI1290732,DT=001103:PST=OOS-NR"
__ 36.1 Verify that the AC is out-of-service normal (OOS-NR).
__ 36.2 Verify that the SIM is out-of-service normal (OOS-NR).
__ 36.3 Verify that the LIP is normal (NR).
Page 29-200 7/07 76.5500/29, Rev R

__ 37. Edit the SIM in-service by entering the following command:

ED-EQPT::SIM-x:ctag::::IS;
Where: x = A or B.
System response:
M CTAG COMPLD

"SIM-B:CL,PROTNA,NSA,07-10,10-51-34,NEND:\"CLR - SIM OOS - not available for
protection\""
__ 38. Retrieve the status of the ACs, and verify the SIM on the AC
supporting the previously faulted LIP is in-service (IS).
System response:
M CTAG COMPLD

"LSM-A::HWV=81.55103 RA,ALMPF=99,SN=UV0694866,DT=060310,MACADDR2=0001AF1681B5:
PST=NR"
"LSM-B::HWV=81.55103 R12,ALMPF=99,SN=UV1170211,DT=060515,MACADDR2=0001AF170E5C:
PST=NR"
"SIM-B::HWV=81.5507B RA,ALMPF=99,TMG=SLV,SN=OI1290732,DT=001103:PST=IS-NR"
76.5500/29, Rev R 7/07 Page 29-201

__ 39. Verify that the state of the SIM is IS-NR, and that timing is SLV.
__ 40. Verify that the state of one AC is IS-NR-ACT, and the other AC is
OOS-NR.
__ 41. Edit the AC supporting the previously faulted LIP in-service by entering
Where: x = A or B.
System response:
M CTAG COMPLD

""AC-B:CL,PROTNA,NSA,07-10,10-52-01,NEND:\"CLR - Admin. Complex OOS - Not available
for protection\""
/* Starting Inactive Database Synchronization */
System response:
M ctag RTRV

"LSM-A::HWV=81.55103 RA,ALMPF=99,SN=UV0694866,DT=060310,MACADDR2=0001AF1681B5:
PST=NR"
"AC-B::SWV=5500FP11.0A507,ALMPF=99:PST=IS-NR-STBY"
"LSM-B::HWV=81.55103 RA,ALMPF=99,SN=UV0694866,DT=060310,MACADDR2=
0001AF1621B2:PST=NR"
Page 29-202 7/07 76.5500/29, Rev R


IS-NR-ACT an the other is IS-NR-STBY.
__ 42.2 Verify from the system response that the LIP and LSM are
NR.


M ctag COMPLD

M ctag COMPLD

"LSM-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Failed diagnostic\":,ISLTD"
__ 43.1.1 If no, go to step 25.

message.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-203

Administrative Complex Power Supply Module (ACPS)

2.54 In this section, you will troubleshoot the alarmed Administrative Complex
Power Supply Module (ACPS). You should have completed System Pre-Checks,
2.55 A spare ACPS may be required in order to perform this procedure. Refer
to Tellabs 5500/5500S Software Release Document, 76.5500/16, to verify the
correct revision level of the module needed, depending on feature package and
what shelf type you are troubleshooting.
__ 1. Retrieve the present state of the alarmed Administrative Complex (AC)
System response:
M ctag COMPLD

"ACPS-2-A::HWV=81.5534,ALMPF=99:PST=ANR-EQ"

the alarmed ACPS is abnormal, unequipped (ANR-UEQ),
go to step 2.

the alarmed ACPS is abnormal, equipped (ANR-EQ), go
__ 2. Visually verify that a module is present in the slot for the alarmed
ACPS.
__ 2.1 If there is no module present in the slot for the alarmed
ACPS, go to step 3, page 29-205.
__ 2.2 If there is a module present in the slot for the alarmed

ACPS, go to step 4, page 29-205.
Warning:
Page 29-204 7/07 76.5500/29, Rev R

Note: The AC shelves number bottom up with shelf number 1 at the bottom of
the rack and shelf number 4 at the top of the rack. Breakers A1 and B1 are
for shelf number 1, Breakers A2 and B2 are for shelf number 2, and so on.
Caution:
When turning OFF the breaker panel switch for an alarmed ACPS, only turn off
the breaker panel switch for that module, either A or B, and not both breakers to
the shelf. Turning off both breakers to the shelf will cause loss of power to that
shelf, which in turn will cause an interruption in service.
__ 3. Depending on if the breaker panel switch for the shelf with the alarmed
ACPS is either OFF or ON, perform one of the following. Refer to
Tables 2.36 through 2.38.
__ 3.1 If the breaker panel switch for the alarmed ACPS is OFF,
__ 3.2 If the breaker panel switch for the alarmed ACPS is ON,
flip it down to the OFF position. Then go to step 9,
page 29-207.
ACPS is either OFF or ON, perform one of the following. Refer to
Table 2.36.
__ 4.1 If the breaker panel switch for the alarmed ACPS is ON,
page 29-206.
__ 4.2 If the breaker panel switch for the alarmed ACPS is OFF,
flip it up to the ON position. Then go to step 6,
page 29-206.
Table 2.36 Standard Core Switch (SCS) Breaker Assignments

(82.0550H B/FAP)
AC Breaker Number Shelf Type
1 AC-A
2 N/A
3 AIP
4 AC-B
76.5500/29, Rev R 7/07 Page 29-205

Table 2.37 Hybrid Core Switch (HCS) Breaker Assignments

(82.0550H1 B/FAP)
1 Consolidated Core Shelf
2 Standard Core Shelf
3 AC-A and AC-B
Table 2.38 Consolidated Core Switch (CCS) Breaker Assignments

(82.0550H1 B/FAP)
1 Consolidated Core Shelf
2 Not Applicable
3 AC-A and AC-B
__ 5. Remove the alarmed ACPS.

place. Then go to step 9, page 29-207.
__ 6. After a five second module initialization, what is the front LED status
of the ACPS?
__ 6.1 If the power LED remains lit, does the system generate an
ACPS alarm CLR (clear) message?
__ 6.1.1 If no, go to step 7.
Caution:
__ 7. Flip the breaker panel switch for the alarmed ACPS to the OFF
position (flip switch down).
__ 8. Remove the alarmed ACPS.
place.
Page 29-206 7/07 76.5500/29, Rev R


steps:
backplane.

backplane?


go to step 10.

troubleshooting.
__ 11. Insert the module.
Note: After inserting the module, the module front panel LEDs light for
approximately two minutes during normal system behavior.

__ 12.1 If the breaker is off, flip the breaker panel switch for the
alarmed ACPS to the ON position (flip switch up), and go
to step 13.
__ 12.2 If the breaker is on, go to step 14.
__ 13. After a five second module initialization, what is the front LED status
of the ACPS?
__ 13.1 If the power LED remains lit, does the system generate an
ACPS alarm CLR (clear) message?
__ 13.1.1 If no, go to step 14.
__ 14. Flip the breaker panel switch for the alarmed ACPS to the OFF
position (flip switch down). Then go to Section 11, Checking the Power
to a Shelf, page 29-1105.
76.5500/29, Rev R 7/07 Page 29-207

__ 15. Retrieve the present state of the alarmed Administrative Complex (AC)
Where: x = EIther A or B, whichever AC is in alarm.
System response:
M ctag COMPLD

__ 15.1 Does the system response verify that the present state of
the alarmed ACPS is normal (NR)?
__ 15.1.1 If no, follow your company's prescribed

procedures for obtaining technical
assistance or call Tellabs Technical
North America).


M ctag COMPLD

M ctag COMPLD


message.
__ 16.1.2 If no, go to step 17.
System response:
M ctag COMPLD
Page 29-208 7/07 76.5500/29, Rev R


command:
System response:
M ctag COMPLD
":INH"



End of Procedure
76.5500/29, Rev R 7/07 Page 29-209

Primary Memory (PRI)

2.56 In this section, you will troubleshoot the primary memory partition on the
harddrive of the Data Storage Module. You should have completed System
Pre-Checks, page 29-64, and been directed to this section from an alarm message
table.
command:
System response:
M ctag COMPLD

":PRI-A,PGM:010104,09-42,FULL,5500FPX.Y.Z,,INVALID,ACTIVE,SYNC"
":PRI-A,DATA:010104,09-42,FULL,5500FPX.Y.Z,SOFTWARE1,INVALID,ACTIVE,SYNC"
__ 1.1 If the system response verifies that a primary memory is

INVALID and you want to sync primary memory, go to
step 2.
__ 1.2 If the system response verifies that the primary memory is

INVALID and you do not want to sync primary memory
information, follow your company's prescribed
__ 2. Edit the alarmed primary memory out-of-service (OOS) by entering the

following command:
Where: x = Either A or B, whichever primary memory copy is

in alarm.
System response:
M ctag COMPLD
__ 3. Retrieve the state of the primary memory by entering the following

command:
System response:
M ctag COMPLD

the alarmed primary memory is abnormal (ANR) and the
other Primary Memory is normal (NR).
Page 29-210 7/07 76.5500/29, Rev R

__ 4. Edit the alarmed primary memory by entering the following command:

ED-EQPT::AC-x:ctag:::DBSYNC=YES:IS;
Where: x = Either A or B, whichever primary memory copy is

in alarm.
System response:
M ctag COMPLD

/* Starting Inactive Database*/
/* Log File Synchronized */
__ 4.1 Before continuing with this procedure, verify that the

above messages were received. It can take up to 45
minutes for AC-A and AC-B to synchronize.

command:
System response:
M ctag COMPLD

":PRI-B,PGM:040915,08-08,FULL,5500FPX.Y.Z,,VALID,ACTIVE,SYNC"
":PRI-B,DATA:040915,08-08,FULL,5500FPX.Y.Z,PLS1024,VALID,ACTIVE,SYNC"
":PRI-A,PGM:040915,14-40,FULL,5500FPX.Y.Z,,VALID,STANDBY,SYNC"
":PRI-A,DATA:040915,14-40,FULL,5500FPX.Y.Z,PLS1024,VALID,STANDBY,SYNC"

both the PGM and DATA bundles for the primary memory
are VALID, go to step 6, page 29-212.

both the PGM and DATA bundles for the primary memory
are not VALID, follow your company's prescribed
76.5500/29, Rev R 7/07 Page 29-211

__ 6. Retrieve the state of the ACs by entering the following command:

System response:
M ctag COMPLD


both PRI-A and PRI-B are normal (NR), go to step 10,
page 29-213.

both PRI-A and PRI-B are abnormal (ANR), go to step 7.
__ 7. Edit the channel that you are on by entering the following command:
ED-CHAN:::ctag::AUD=ON;
System response:
M ctag COMPLD
__ 8. Retrieve the channel by entering the following command:

RTRV-CHAN:::ctag;
System response:
M ctag COMPLD

"CHAN-1-1:CRALM=ON,MJALM=ON,MNALM=ON,NAEVT=ON,CONDSCHED=ON,REPTSCHED=ON,PMSCHED=ON,
SYSMSG=ON,SIRPT=OFF,DBCHG=ON,AUD=ON:MLP=ON:PST=NR"
__ 8.1 Verify from the system response that the audit parameter
equals ON (AUD=ON).
__ 9. Run the audit data report by entering the following command:

AUD-DATA::PRI:ctag;
Note: The audit data report is used to help troubleshoot the problem on the
primary memory.
System response:
M ctag COMPLD

"PRI-A,DBSI,2"
"PRI-A,CMCI,3"
"PRI-B,DBSI,0"
"PRI-B,CMCI,0"
Page 29-212 7/07 76.5500/29, Rev R

__ 9.1 After the report is finished running, follow your company's

America).


M ctag COMPLD

M ctag COMPLD


message.
__ 10.1.2 If no, go to step 11.
System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD
":INH"



End of Procedure
76.5500/29, Rev R 7/07 Page 29-213

Secondary Memory (SEC)

2.57 In this section, you will troubleshoot the secondary memory partition on the
hard drive of the Data Storage Module. You should have completed System
Pre-Checks, page 29-64, and been directed to this section from an alarm message
table.
command:
System response:
M ctag COMPLD

":SEC-A,PGM:010104,09-42,FULL,5500FPX.Y.Z,,INVALID,ACTIVE"
":SEC-A,DATA:010104,09-42,FULL,5500FPX.Y.Z,SOFTWARE1,INVALID,ACTIVE"
__ 1.1 If the system response verifies that the secondary

memory is INVALID and you want to copy over existing
secondary memory information, go to step 2.
__ 1.2 If the system response verifies that the secondary

memory is INVALID and you do not want to copy over
existing secondary memory information, follow your
1.800.443.5555 (North America) or 1.630.798.7070
__ 2. Copy the primary memory onto the secondary memory by entering the
following command:
CPY-MEM::FROMMEM=PRI,TOMEM=SEC:ctag::ALL:FRCD;
System response:
M ctag COMPLD
Note 1: During copying, the DSM disk activity LEDs occasionally flash to
indicate disk activity.
Note 2: This command may take from 10 to 20 minutes to complete.
Note 3: The system may or may not generate a SEC alarm CLR (clear) message
within 10 minutes after executing this command.
Page 29-214 7/07 76.5500/29, Rev R


command:
System response:
M ctag COMPLD

":SEC-A,PGM:010104,09-42,FULL,5500FPX.Y.Z,,VALID,ACTIVE"
":SEC-A,DATA:010104,09-42,FULL,5500FPX.Y.Z,SOFTWARE1,VALID,ACTIVE"

both the PGM and DATA for the secondary memory are
VALID, go to step 4.

both the PGM and DATA for the secondary memory are
not VALID, follow your company's prescribed procedures
for obtaining technical assistance or call Tellabs
Technical Assistance at 1.800.443.5555 (North America)
or 1.630.798.7070 (outside North America).

System response:
M ctag COMPLD


both SEC-A and SEC-B are normal (NR), go to step 8,
page 29-216.

both SEC-A and SEC-B are abnormal (ANR), go to
step 5.
__ 5. Edit the channel that you are on by entering the following command:
ED-CHAN:::ctag::AUD=ON;
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-215

__ 6. Retrieve the channel by entering the following command:

RTRV-CHAN:::ctag;
System response:
M ctag COMPLD

"CHAN-1-1:CRALM=ON,MJALM=ON,MNALM=ON,NAEVT=ON,CONDSCHED=ON,REPTSCHED=ON,PMSCHED=ON,
SYSMSG=ON,SIRPT=OFF,DBCHG=ON,AUD=ON:MLP=ON:PST=NR"
__ 6.1 Verify from the system response that the audit parameter
equals ON (AUD=ON).
__ 7. Run the audit data report by entering the following command:

AUD-DATA::SEC:ctag;
Note: The audit data report is used to help troubleshoot the problem on the
secondary memory.
System response:
M ctag COMPLD

"SEC-A,DBSI,2"
"SEC-A,CMCI,3"
"SEC-B,DBSI,0"
"SEC-B,CMCI,0"
__ 7.1 After the report is finished running, follow your company's

America).


M ctag COMPLD

M ctag COMPLD

Page 29-216 7/07 76.5500/29, Rev R


message.

System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD
":INH"



End of Procedure
76.5500/29, Rev R 7/07 Page 29-217

Single Removable Media (SRM)

2.58 In this section, you will troubleshoot the alarmed Single Removable Media
(SRM). You should have completed System Pre-Checks, page 29-64, and been
2.59 The term Single Removable Media (SRM) refers to the flash memory card.
The term Removable Storage Drive (RSD) refers to PCMCIA drive on the Data
Storage Module (DSM).
2.60 A spare SRM may be required in order to perform this procedure.

M ctag COMPLD

M ctag COMPLD

"REMV-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Removable media not present \":,ISLTD"
__ 1.1 Does the system response generate any of the following

alarm messages? (For a complete list of alarm messages
related to single removable media, refer to TL1
\* SID mismatch \*
\* Removable media data bundle is invalid \*
\* Removable media program bundle is invalid \*
\* Removable media data and program bundles are invalid \*
\* Removable media has insufficient storage capacity\"*
__ 2. Does the system response generate the following alarm message?

\* Removable media cannot be used for system backup\"*
__ 2.1 If you are performing a system backup when this

message was received, go to step 11, page 29-220.
__ 2.2 If you are performing another procedure, such as an

upgrade, when this message was received, no fault
exists. The message serves as a notification that the
removable media cannot be used for system backup.
Page 29-218 7/07 76.5500/29, Rev R

__ 3. Visually verify that the alarmed SRM is present in the alarmed DSM.
__ 3.1 If the SRM is present, go to step 4.
__ 3.2 If the SRM is not present, go to step 8, page 29-219.
Warning:
__ 4. Remove the SRM from the RSD by performing the following steps:
__ 4.1 Push the DSM front panel SRM ejector button located to
the right of the RSD.
__ 4.2 Completely remove the SRM from the DSM.
__ 5. Reinsert the SRM by performing the following steps:

__ 5.1 Hold the SRM and position it as shown on the RSD front
panel.
__ 5.2 Insert the SRM into the RSD front panel disk drive slot
until resistance is met.
__ 6. Does the RSD front panel disk access LED turn off after 10 seconds?
__ 6.2 If no, remove the SRM and go to step 8.
Note: Remove the SRM from the immediate area so that it is not installed again.
__ 7. Does the system response generate a REMV alarm CLR message for
the alarmed SRM?

__ 8. Follow internal policy to determine the correct version of SRM to be

inserted into the RSD of the alarmed DSM.
76.5500/29, Rev R 7/07 Page 29-219

__ 9. Insert the new SRM by performing the following steps:

__ 9.1 Hold the SRM and position it as shown on the RSD front
panel.
__ 9.2 Insert the SRM into the RSD front panel disk drive slot
until resistance is met.
the alarmed SRM?
System response:
M ctag COMPLD

"REMV-A,EQPT:CLR,02-01,14-52-20,NEND:\" CLR - Removable media not present \"

__ 11. Retrieve the status of the removable memory bundles by entering the
following command:
System response:
M ctag COMPLD
":REMV-B,DATA:040915,15-26,FULL,5500FPX.Y.Z,PLS1024,VALID,ACTIVE"
/* REMV-A:Patch Distribution Media: FPx.y.z patch load number xx */
__ 11.1 If the removable media shows patch distribution media,

this media cannot be used for backups. Return to step 9,
page 29-220, and insert a valid disk that is not a patch
distribution media.
__ 12. Are you allowed to record over system memory information on the
SRM?
Note: This SRM contains information that does not match current system
information. Follow internal policy for recording over SRM information.
Page 29-220 7/07 76.5500/29, Rev R

__ 13. Copy data from PRI memory to SEC memory by entering the following
command:
CPY-MEM::FROMMEM=PRI,TOMEM=SEC:ctag::aaaa;
Where: aaaa = Type of data bundle you want to back up:

DATA (to specify system data)
PGM (to specify program software)
PATCH (to specify patch load data)
ALL (to specify PGM and DATA).
Example:
CPY-MEM::FROMMEM=PRI,TOMEM=SEC:dm::ALL;
System response:
TELLABS 03-06-09 14:17:01
M ctag COMPLD
Note 1: Memory copying lasts approximately 15 minutes.
Note 2: Module front panel LEDs light on the alarmed RSD during normal
system behavior.
command:
RTRV-MEMSTAT-MEM::SEC:ctag::aaaa;
Where: aaaa = Type of data bundle you backed up in step 13.
System response:
M ctag COMPLD

":SEC-B,PGM:030609,14-17,FULL,5500FPX.Y.Z,,VALID,ACTIVE"
":SEC-B,DATA:030609,14-17,FULL,5500FPX.Y.Z, TELLABS,VALID,ACTIVE"
":SEC-A,PGM:030609,14-19,FULL,5500FPX.Y.Z,,VALID,STANDBY"
":SEC-A,DATA:030609,14-19,FULL,5500FPX.Y.Z,TELLABS,VALID,STANDBY"
__ 14.1 Verify from the system response that the PGM and DATA
bundles are valid (VALID).
__ 14.2 Verify the date and time stamp of the PGM and DATA
bundles correspond to the header date and time stamp
listed above the M ctag COMPLD response from step 13.
__ 14.3 Verify from the system response that the system ID

matches the header ID listed above the M ctag COMPLD
response from step 13.
Note: The flash memory card does not have write-protection.
76.5500/29, Rev R 7/07 Page 29-221

__ 15. Verify that SRMs are present in the DSMs. If there are no SRMs, insert
them now.
Note: The following command takes 30 to 60 minutes to complete. A COMPLD

system response will appear once the copy process is complete.
__ 16. Copy data from SEC memory to REMV by entering the following
command:
CPY-MEM::FROMMEM=SEC,TODEV=REMV:ctag::aaaa;
Where: aaaa = Type of data bundle you want to back up:

DATA (to specify system data)
PGM (to specify program software)
PATCH (to specify patch load data)
ALL (to specify PGM and DATA).
Example:
CPY-MEM::FROMMEM=SEC,TODEV=REMV:dm::ALL;
System response:
TELLABS 03-06-06 15:16:01
M ctag COMPLD
__ 17. Retrieve the status of the REMV memory by entering the following
command:
RTRV-MEMSTAT-MEM::REMV:ctag::aaaa;
Where: aaaa = Type of data bundle you backed up in step 16.
System response:
M ctag COMPLD

":REMV-B,DATA:030606,15-16,FULL,5500FPX.Y.Z,TELLABS,VALID,ACTIVE"
":REMV-A,PGM:030606,15-27,FULL,5500FPX.Y.Z,,VALID,STANDBY"
":REMV-A,DATA:030606,15-27,FULL,5500FPX.Y.Z,TELLABS,VALID,STANDBY"
":REMV-A,UPGRADE:030602,18-12,FULL,5500FPX.Y.Z,,VALID,STANDBY"
__ 17.1 Verify from the system response that the PGM and DATA
bundles are valid (VALID).
__ 17.2 Verify the date and time stamp of the PGM and DATA
bundles correspond to the header date and time stamp
listed above the M ctag COMPLD response from step 16,
page 29-222.
Page 29-222 7/07 76.5500/29, Rev R

__ 17.3 Verify from the system response that the system ID

matches the header ID listed above the M ctag COMPLD
response from step 16, page 29-222.
the alarmed SRM?

__ 19. Retrieve the state of the SRM by entering the following command:
System response:
M ctag COMPLD

":REMV-A,PGM:010104,09-42,FULL,5500FPX.Y.Z,,VALID,ACTIVE"
":REMV-A,DATA:001227,14-32,FULL,5500FPX.Y.Z,SOFTWARE1,VALID,ACTIVE"
__ 19.1 Is the system response for the REMV program (PGM)

VALID?

North America).
__ 20. Is the system response for the REMV data (DATA) VALID within one
minute?

76.5500/29, Rev R 7/07 Page 29-223



M ctag COMPLD

M ctag COMPLD

"REMV-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Removable media not present \":,ISLTD"
__ 21.1.1 If no, go to step 22.

message.
System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD
":INH"



End of Procedure
Page 29-224 7/07 76.5500/29, Rev R

Link (LINK) or Channel (CHAN)

2.61 In this section, you will troubleshoot the alarmed Link (LINK) or the
alarmed channel (CHAN). You should have completed System Pre-Checks,
2.62 Follow internal policy for synchronous link troubleshooting if operating over
an X.25 link.
__ 1.1 If you received a LINK-N alarm similar to the following
example, go to step 7, page 29-227, to verify the
configuration of the TCP/IP and LAN. Refer to Tellabs
5500/5500S TCP/IP Activation and DCC Deactivation
Manual, 76.5500/46, for more detailed information on
how to configure the TCP/IP.
"LINK-5:MN,OSLINK,NSA,06-04,14-09-46,NEND:\"Lost Operation Link Communication\":

,ISLTD"
__ 1.2 If you did not receive a LINK-N alarm, go to step 2.
__ 2. Depending on whether or not the alarmed link is connected to an

external device, choose one of the following options:
__ 2.1 If the alarmed link is connected to an external device,
verify that the external device is working properly.
__ 2.1.1 If the external device is working properly,

go to substep 2.2, page 29-226.
__ 2.1.2 If the external device is connected to J11

or J12 serving links 2, 3, 6, or 7,
disconnect the device and insert the
loopback device (Tellabs part number
50.0730). The loopback device causes
pin 20 (DTR) to go to a positive voltage.
See the following note for an explanation
of the asynchronous links.
Note 1: Backplane connections are as follows: J10 for links 1 and 5, J11 for links
2 and 6, J12 for links 3 and 7, J13 for links 4 and 8.
Note 2: The asynchronous links are configured for RS-232-C. Links 2, 3, 6, and
7 use pin 20 for DTR (Data Terminal Ready) because they were
originally intended to be used with a modern connection. They also
provide automatic logout when users disconnect the serial cable. Links
1 and 5 were intended for use with a local terminal where the user logs
out of each session. Links 1 and 5 do not provide automatic logout when
the serial cable is removed, because they do not use pin 20 for DTR
interface control. If pin 20 for DTR is not high, the system will declare the
following alarm:
"LINK-7:MN,OSLINK,NSA,09-16,14-59-26,NEND:\"Lost Operation Link

Communication\":,ISLTD"
76.5500/29, Rev R 7/07 Page 29-225

__ 2.2 If the alarmed link is not connected to an external device

for J11 or J12, verify that the loopback plug for the async
link (Tellabs part number 50.0730) is plugged into the
alarmed link.
Note: For J10 and J13, the link does not have to be plugged into a loopback plug
for the async link (part number 50.0730). The link can be left empty.
__ 3. Did the alarm message clear?

__ 3.1 If yes, the problem with the link is external to the Tellabs
5500/5500S system.
__ 3.2 If no, continue to step 4.
__ 4. Retrieve the present state of the alarmed link by entering the following
command:
RTRV-LINK::LINK-x:ctag;
Where: x = Alarmed link.
System response:
M ctag RTRV

"LINK-2::BAUD=1200,PAR=EVEN,BPC=7,FC=H`11-H'13,ALMPF=5:PST=OOS-NR"

the alarmed link is out-of-service (OOS), go to step 5.

the alarmed link is in-service (IS), go to step 13,
page 29-229.
__ 5. Edit the alarmed link in-service (IS) by entering the following

command:
ED-LINK::LINK-x:ctag:::IS;
Where: x = Alarmed link.
System response:
M ctag COMPLD
__ 5.1 Does the system response generate a LINK alarm CLR

message for the alarmed link?
__ 5.1.1 If no, go to step 6, page 29-227.
Page 29-226 7/07 76.5500/29, Rev R


command:
Where: x = Either A or B, whichever AC is in alarm.
System response:
M ctag COMPLD

"AC-A::SWV=5500FPX.Y.Z,ALMPF=99:PST=IS"

the alarmed AC is in-service, abnormal (IS-ANR), return

the alarmed AC is in-service, normal (IS-NR), go to step
13, page 29-229.
__ 7. Retrieve the state of the TCP/IP by entering the following command:

RTRV-TCPIP::TCPIP:ctag;
System response:
M ctag COMPLD

"TCPIP:IPADDR=172.23.169.184:ALMPF=99,HOST=PLSLAB-H,MASK=255.255.255.0,
GWDFLT=172.23.169.254,TELNET=ALW,FTP=INH,HTTP=INH,IT=INH,SSHAUTH=ALL,CSTATE=CONNECT,
KEYSTRENGTH=1024,TMR1=10,TMR2=60,CONMON=ON,KEYHOSTFP=\"00:db:23:67:ba:62:c9:f5:91:b4
:e9:92:ba:a4:d5:7b\":PST=OOS-NR"

the TCP/IP is out-of-service (OOS), go to step 8.

the TCP/IP is in-service (IS), go to step 10, page 29-228.
__ 8. Edit the TCP/IP in-service (IS) by entering the following command:

ED-TCPIP::TCPIP:ctag::::IS;
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-227

__ 9. Retrieve the present state of the TCP/IP by entering the following

command:
RTRV-TCPIP::TCPIP:ctag;
System response:
M ctag COMPLD

"TCPIP:IPADDR=172.23.169.184:ALMPF=99,HOST=PLSLAB-H,MASK=255.255.255.0,
GWDFLT=172.23.169.254,TELNET=ALW,FTP=INH,HTTP=INH,IT=INH,SSHAUTH=ALL,CSTATE=CONNECT,
KEYSTRENGTH=1024,TMR1=10,TMR2=60,CONMON=ON,KEYHOSTFP=\"00:db:23:67:ba:62:c9:f5:91:b4
:e9:92:ba:a4:d5:7b\":PST=IS-NR"
__ 9.1 Verify from the system response that the TCP/IP is

in-service, normal (IS-NR). Then go to step 10.
__ 10. Retrieve the state of the LAN by entering the following command:
RTRV-LAN::LAN-2:ctag;
System response:
M ctag COMPLD

"LAN-0002::LANTYPE=STD,ALMPF=99:PST=OOS-NR"

the LAN is out-of-service (OOS), go to step 11.

the LAN is in-service (IS), go to step 13, page 29-229.
__ 11. Edit the LAN in-service (IS) by entering the following command:
ED-LAN::LAN-2:ctag::::IS;
System response:
M ctag COMPLD
__ 12. Retrieve the present state of the LAN by entering the following
command:
RTRV-LAN::LAN-2:ctag;
System response:
M ctag COMPLD

"LAN-0002::LANTYPE=STD,ALMPF=99:PST=IS-NR"
__ 12.1 Verify from the system response that the LAN is

in-service, normal (IS-NR). Then go to step 13,
page 29-229.
Page 29-228 7/07 76.5500/29, Rev R

System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD
":INH"



End of Procedure
76.5500/29, Rev R 7/07 Page 29-229

Local Area Network (LAN-1)

2.63 In this section, you will troubleshoot the alarmed Local Area Network
(LAN). You should have completed System Pre-Checks, page 29-64, and been
__ 1. If you are troubleshooting a Standard switch core, go to step 2,
page 29-230.
If you are troubleshooting a Consolidated or Hybrid Core, go to step 8,
page 29-238.

M ctag COMPLD

M ctag COMPLD

"NE-TITAN5500:MAN,SC,07-17,10-33-02,NEND;\"Intra-system control LAN 3 has exceeded
the node limit\"\":ISLTD"
__ 2.1 Does the system generate any of the following alarm

messages?
"NE-TITAN5500:MAN,SC,07-17,10-33-02,NEND;\"Intra-system control LAN x has exceeded

the node limit\"\":ISLTD"
Where: x = GC LAN (1 - 8).
"NE-TITAN5500:MAN,SC,07-17,10-33-02,NEND;\"GC LAN Miscabled - AC-A on ESS-xxxx-y LAN

B\"\":ISLTD"
"NE-TITAN5500:MAN,SC,07-17,10-33-02,NEND;\"GC LAN Miscabled - AC-B on ESS-xxxx-y LAN

A\"\":ISLTD"
"NE-TITAN5500:MAN,SC,07-17,10-33-02,NEND;\"GC LAN Miscabled - AC-A on ESS-xxxx-y LAN

B\"\":ISLTD"
"NE-TITAN5500:MAN,SC,07-17,10-33-02,NEND;\"GC LAN Miscabled - AC-B on ESS-xxxx-y LAN

A\"\":ISLTD"
Where: xxxx = Lead SDF of the shelf.

y = Network Copy (A or B).
__ 2.1.1 If yes, go to paragraph 2.64,

page 29-231.
__ 2.1.2 If no, continue to the next step.
Page 29-230 7/07 76.5500/29, Rev R

__ 3. Does the system generate the following alarm message?

"NE-TITAN5500:MAN,SC,07-17,10-33-02,NEND;\"Intra-system control LAN x cabling has
unbalanced GC connections\":ISLTD"
Where: x = GC LAN (1 - 8).

2.64 The Intra-system control LAN x has exceeded the node limit alarm is
generated when the maximum number of nodes on a particular LAN run has been
exceeded. The following are the parameters that must be followed:
• In a complete high density LAN run, up to 10 shelves maximum are
permitted. The high density port shelves (HDPS) each count as 4
shelves, for a maximum of 40 shelves possible per LAN run.
• In a complete low density port shelf (LDPS) LAN run, up to 40 low

density shelves are permitted.
• In a combination of low and high density shelves on a single LAN run,

up to 5 HDPS and up to 20 LDPS are used. (HDPSs count as four
shelves and LDPSs count as one shelf.) The following list provides
rules for acceptable maximum per LAN run configurations:
- The maximum of 5 HDPS can be altered provided the number of

LDPS on the LAN run decreases by 4 shelves for every HDPS
added to the LAN run (for example, 6 HDPS and 16 LDPS).
- A LAN run containing HDPS and LDPS may not contain more than
20 LDPS, regardless of the number of HDPS on the LAN run.
__ 4. Retrieve the number of shelves on the LAN runs by entering the
following command:
RTRV-CONFIG::GCLAN-xxxx:ctag;
Where: xxxx = GC LAN being retrieved (1 - 8).
System response:
M ctag COMPLD

"GCLAN-1:NODECOUNT=1,SDFS=0"
"GCLAN-1:NGC-A"
"GCLAN-2:PGC1-0001-A,PGC1-0005-A,PGC1-0009-A,PGC1-0013-A"
"GCLAN-2:PGC1-0001-B,PGC1-0005-B,PGC1-0009-B,PGC1-0013-B,NGC-B"
"GCLAN-3:PGC1D-0017-A,PGC1D-0025-A,PGC3-0033-A,PGCO12-0049-A"
76.5500/29, Rev R 7/07 Page 29-231

"GCLAN-3:PGC1D-0017-B,PGC1D-0025-B,PGC3-0033-B,PGCO12-0049-B"
"GCLAN-4:PGC3-0097-A,PGC3-0113-A,PGCO3-0129-A,PGCO3-0141-A
"GCLAN-4:PGC3-0097-B,PGC3-0113-B,PGCO3-0129-B,PGCO3-0141-B"
"GCLAN-5:PGCO3-0193-A,PGCO3-0205-A,PGCO3-0217-A,PGCO3-0229-A"
"GCLAN-5:PGCO3-0193-B,PGCO3-0205-B,PGCO3-0217-B,PGCO3-0229-B"
"GCLAN-6:PGCO12-0241-A,PGCO12-0253-A,PGCO12-0265-A,PGCO12-0277-A"
"GCLAN-6:PGCO12-0241-B,PGCO12-0253-B,PGCO12-0265-B,PGCO12-0277-B"
"GCLAN-7:PGCU-0709-A,PGCU-0805-A,PGCU-0901-A,PGCU-0997-A"
"GCLAN-7:PGCU-0709-B,PGCU-0805-B,PGCU-0901-B,PGCU-0997-B"
"GCLAN-8:PGCU-1093-A,PGCU-1189-A"
"GCLAN-8:PGCU-1093-B,PGCU-1189-B"
"\* GC LAN configuration is for PGCs connected to Active AC only *\"
__ 5. Determine the LAN run in alarm based on the output from step 4,
page 29-231. If the LAN run exceeds 40 nodes, follow your company's
prescribed procedures to reconfigure the LAN runs until the node limit
is below 40 nodes. Continue to step 7, page 29-238, when completed.
__ 6. Starting in FP9.0.X, the GC LAN connectors on the rear of the
Administrative Complex have changed. Refer to Figure 2.26,
page 29-233, for the LAN configuration prior to FP9.0.X. Refer to
Figure 2.27, page 29-233, for the LAN configuration for FP9.0.X and
later. The system will issue the Intra-system control LAN x cabling has
unbalanced GC connections alarm if the LAN cabling does not
conform to the new LAN layout per Figure 2.27, page 29-233. Per
office records, verify that the LAN runs are correctly installed. Refer to
Figure 2.26, page 29-233, through Figure 2.31, page 29-237.
Page 29-232 7/07 76.5500/29, Rev R

Figure 2.26 LAN Configuration Before FP9.0.X
Figure 2.27 LAN Configuration After FP9.0.X
76.5500/29, Rev R 7/07 Page 29-233

Figure 2.28 DS1, DS3, and STS-1E Daisy Chain LAN Run
To bottom shelf of the next bay
A
AC-B B
J8 A A J4 A
AC-B LAN A
J7 B B J3 B
AC-B LAN B J6 A A J2
J5 B B J1
J8 A A J4
J28 (B)
J29 (A) J7 B B J3
J6 A A J2
AC-A J5 B B J1
J8 A A J4
J7 B B J3
J6 A A J2
J5 B B J1
J29 (A) J8 A A J4
J28 (B)
J7 B B J3
J6 A A J2
AC-A LAN B J5 B B J1
port shelf backplane (rear view)
AC-A LAN A Copy B | Copy A
Page 29-234 7/07 76.5500/29, Rev R

Figure 2.29 DDS1 Port Shelf LAN Run, Daisy Chain Formation
A
AC-B B
J2 A A J2 A
AC-B LAN A
J2 B B J2 B
J2 B B J3
J2 A A J2
J28 (B)
J29 (A) J2 B B J2
J2 A A J2
AC-A J2 B B J3
J2 A A J2
J2 B B J2
J2 A A J2
J2 B B J3
J29 (A) J2 A A J2
J28 (B)
J2 B B J2
J2 A A J2
76.5500/29, Rev R 7/07 Page 29-235

Figure 2.30 OC-3 or OC-12 Port Shelf LAN Run, Daisy Chain Formation
A
AC-B B
J5 A A J1 A
AC-B LAN A
J6 B B J1 B
J8 B B J2
J5 A A J1
J28 (B)
J29 (A) J6 B B J1
J7 A A J1
AC-A J8 B B J2
J5 A A J1
J6 B B J1
J7 A A J1
J8 B B J2
J29 (A) J5 A A J1
J28 (B)
J6 B B J1
J7 A A J1
Page 29-236 7/07 76.5500/29, Rev R

Figure 2.31 High Density Port Shelf (HDPS) LAN Run
AC-B NC-B ESS Key:

OUT IN terminator =
shorting plug =
Retrofit Bar
GC LAN Jumper Cable
J29 (1A) J28 (1B)
AC-B LAN B
AC-B LAN A TSI96-A
AC-A NC-A ESS

OUT IN
TSI96-B
(front view)
J29 (1A) J28 (1B)
AC-A LAN B
AC-A LAN A
76.5500/29, Rev R 7/07 Page 29-237



M ctag COMPLD

M ctag COMPLD

"SCM-1-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Failed diagnositc\":,ISLTD"

message.
Troubleshooting Control LAN in System with Hybrid or CCS Switch Core

2.65 Perform the steps in this section to troubleshoot the control LAN in a
system that contains a CCS core.
RTRV-COND-ALL:::ctag;

M ctag COMPLD

M ctag COMPLD

"LSM-B:MN,CONTCOM,NSA,06-20,10-09-20,NEND:\"LSM to CGC LAN Comm Lost at LAN-1 port
(missing cable?)\":,ISLTD"

not available for protection\":,ISLTD"
"CGC-SH2-10:MN,CONTCOM,NSA,06-20,10-09-22,NEND:\"CGC to LSM LAN Comm Lost at LAN A

port (missing cable?)\":,ISLTD"
Page 29-238 7/07 76.5500/29, Rev R

__ 8.1 Determine if the PROTNA alarm, "Failure on internal LAN

- part of path not available for protection" is generated.
__ 8.1.1 If the PRONTNA alarm on the LAN is not

generated, refer to the appropriate
section of the Troubleshooting manual to
troubleshoot the message received.
__ 8.1.2 If the PROTNA alarm is generated, note

the CONTCOM alarms that are
generated, and the affected entities.
__ 9. Using the AIDs of the entities affected by the CONTCOM alarms,

check that the LAN cable between the two entities is securely
connected.
Refer to Figure 2.32 for the control LAN cabling in a system with a
hybrid or CCS switch core.
Figure 2.32 Control LAN Cabling with Hybrid and CCS Switch Core
AC-A AC-B
X COPY CO LAN X COPY CO LAN
LSM LIP-A LIP-B LSM

A LAN-1 LAN-1 B
J14 J14
LTIP-1 LTIP-2
LAN-A LAN-A
CGC-SH1 in CCS-A CGC-SH2 in CCS-B
P24 P26 P24 P26
2.66 Important: If the P24 and P26 connectors on the CCS shelf are suspected
as faulty, follow your company’s prescribed procedures for obtaining technical
assistance or call Tellabs Technical Assistance at 1.800.443.5555 (North America)
or 1.630.798.7070 (outside North America).
76.5500/29, Rev R 7/07 Page 29-239



M ctag COMPLD

M ctag COMPLD

"LSM-B:CL,CONTCOM,NSA,06-20,10-10-21,NEND:\"CLR - LSM to CGC LAN Comm Lost at LAN-1
port (missing cable?)\""
"CGC-SH2-10:CL,CONTCOM,NSA,06-20,10-10-23,NEND:\"CLR - CGC to LSM LAN Comm Lost at LAN

A port (missing cable?)\""
"LAN-0001:CL,PROTNA,NSA,06-20,10-10-23,NEND:\"CLR - Failure on internal LAN - part of

path not available for protection\""
__ 10.0.1 Determine if Clear messages are

generated for the LAN PRONTNA alarm,
and the corresponding CONTCOM
alarms.
__ 10.0.2 If the alarm messages do not clear, go to

step 11.
__ 10.0.3 If the alarm messages clear, go to

step 12.
__ 11. Replace the LAN cable.


M ctag COMPLD

M ctag COMPLD

"LSM-B:CL,CONTCOM,NSA,06-20,10-10-21,NEND:\"CLR - LSM to CGC LAN Comm Lost at LAN-1
port (missing cable?)\""

"LAN-0001:CL,PROTNA,NSA,06-20,10-10-23,NEND:\"CLR - Failure on internal LAN - part of

path not available for protection\""
Page 29-240 7/07 76.5500/29, Rev R

__ 12.0.1 Determine if Clear messages are

generated for the LAN PRONTNA alarm,
and the corresponding CONTCOM
alarms.
__ 12.0.2 If the alarm messages clear, go to step

13, page 29-241.
__ 12.0.3 If you are troubleshooting a \"CGC to

LSM LAN Comm Lost at LAN A port
(missing cable?)\" message, and the
alarm does not clear, go to LAN Switch
Module, page 29-171.
__ 12.0.4 If other alarm messages do not clear,

follow your company’s prescribed
North America).
__ 13. Log off the system:

End of Procedure
76.5500/29, Rev R 7/07 Page 29-241

Timing Reference (REF)

2.67 In this section, you will troubleshoot the alarmed Timing Reference (REF).
You should have completed System Pre-Checks, page 29-64, and been directed
to this section from an alarm message table.

M ctag COMPLD

M ctag COMPLD

"REF-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Neither SIM is available \":,ISLTD"
__ 1.1 Does the system generate a loss of timing input?
System response when external reference is lost:

"REF-A,REF:MN,LOS,NSA,07-16,09-00-08,NEND:\"SIM-A and SIM-B have detected Loss of
Signal on the reference\":,ISLTD"
__ 1.1.1 If yes, go to substep 1.2.
__ 1.2 Verify that the external device is working properly.
__ 1.2.1 If the external device is not working

properly, follow internal policy to correct
the problem.
__ 2. Using a DS1 test set, verify the DS1 timing signal on J53 on the
backplane of the AC.
__ 2.1 If there is an external problem with the timing reference,
resolve the problem. Then go to step 7, page 29-244.
__ 2.2 If there is not an external problem with the timing

reference, continue to step 3, page 29-243.
Page 29-242 7/07 76.5500/29, Rev R

__ 3. Retrieve the present state of the alarmed REF by entering the

following command:
RTRV-REF::REF-x:ctag;
Where: x = Either A or B, whichever REF is in alarm.
System response:
M ctag RTRV

"REF-A::ALM=INH,ALMPF=4,LINECDE=AMI,FMT=ESF,SSM=STRATUM1:PST=OOS-NR"

the alarmed REF is out-of-service, normal (OOS-NR), go

the alarmed REF is out-of-service, abnormal (OOS-ANR),
and the external device is working properly, follow your
1.800.443.5555 (North America) or 1.630.798.7070
__ 3.2.1 If the external device is not working

properly, follow your company's
prescribed procedures to correct the
problem. Then repeat step 3,
page 29-243.

America).
__ 4. Edit the alarmed REF in-service (IS) by entering the following

command:
ED-REF::REF-x:ctag::::IS;
Where: x = Either A or B, whichever REF is in alarm.
System response:
M ctag COMPLD
__ 5. Does the system response generate the following REF PROTNA

alarm message?
\*"REF-A:CL,PROTNA,NSA,09-15,14-12-23,NEND:\"CLR - Reference not available for
protection\"" \*

76.5500/29, Rev R 7/07 Page 29-243

__ 6. Retrieve the present state of the alarmed REF by entering the

following command:
RTRV-REF::REF-x:ctag;
Where: x = EIther A or B, whichever REF is in alarm.
System response:
M ctag RTRV

"REF-A::ALM=INH,ALMPF=4,LINECDE=AMI,FMT=ESF,SSM=STRATUM1:PST=IS-NR-STBY"

the alarmed REF is in-service, normal, standby

America).


M ctag COMPLD

M ctag COMPLD

"REF-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Neither SIM is available \":,ISLTD"

message.



End of Procedure
Page 29-244 7/07 76.5500/29, Rev R

Troubleshooting Manual 3. Troubleshooting the Network Complex
3. Troubleshooting the Network Complex
3.01 This section contains procedure to troubleshoot a problem occurring on

the following faulted modules:
• Center Stage Shelf Power Supply Module (CSSPS)
• End Stage Shelf Power Supply Module (ESSPS)
• Network Group Controller Module (NGC)

• Network Timing Distribution Module (NTDM)
• End Stage Module (ESM)
• Center Stage Module (CSM)
• CSM Adapter Module (CAM)

3.02 When troubleshooting the Network Complex (NC), always check for any
pertinent Product Performance Notices (PPNs). There may be an issue that has
already been identified that will shorten the time required to troubleshoot the NC.
troubleshooting the Network Complex. Refer to Status of the LEDs on a Faulted
Module, page 29-246.
is not certain, the OPR-EQPT-LED command can be used to locate the
module.The module locator application allows you to flash the red fault LED on a
specific port or network module to help locate it. When using the OPR-EQPT-LED
(PGC) must be in-service normal (IS-NR). The module itself must be equipped. For
more information on executing this command, go to Tellabs 5500/5500S
Note: In a Tellabs 5500 system with a hybrid core switch, the ESMs must be Rev.
S or higher.
Warning:
76.5500/29, Rev R 7/07 Page 29-245

3. Troubleshooting the Network Complex Troubleshooting Manual
advised to obtain a spare module before starting. Refer to Tellabs 5500/5500S
Software Release Document, 76.5500/16, to verify the correct revision level of the
module needed, depending on feature package and what shelf type you are
troubleshooting.

3.07 Figures 3.1 through Figure 3.5, page 29-254, are for reference only. Use
these figures as an aid in troubleshooting the alarmed Network Complex.
3.08 To troubleshoot a faulted module, go to System Pre-Checks,
page 29-256.
Network Group Controller Figure 3.1 Network Group Controller Module LEDs
Module LEDs
GCM
GCM
active
fault
Page 29-246 7/07 76.5500/29, Rev R

Table 3.1 Status of Network Group Controller Module LEDs
Status of
LEDs Meaning Notes

Fault OFF
All ON - Both the Active and Fault LEDs flash on and off regularly - Active, slow flash = requesting download from main
when requesting a download from the Administrative processor.
Complex. - The NGC role is to download information from the
- Module is in self-diagnostic mode. database to all of the modules on its shelf. Other
modules may have Fault LEDs ON until the NGC is
seated and it downloads the information to the
modules.
Usually a temporary state that occurs during module

or system initialization.

Fault ON - Bent pin(s) on backplane connector.
Both OFF - Module is out-of-service (OOS). When NGC is out-of-service (OOS), it does not affect
- Bent pin(s) on backplane connector. the other network modules it serves.
- No power, out of slot, breaker OFF.
Usually a temporary state.
76.5500/29, Rev R 7/07 Page 29-247

Network Timing Distribution Figure 3.2 Network Timing Distribution Module LEDs
Module LEDs
NTDM
reference
alarms
SIM A
SIM B
other
NTDM
selected
reference
SIM A
SIM B
other
NTDM
module
status
master
active
fault
Network Timing Distribution Module (NTDM) in

normal state (active LED is ON) with selected
reference from SIM-A
Table 3.2 Status of Network Timing Distribution Module LEDs
LED Status of
All reference Normal, available state.

alarms OFF
SIM-A or SIM-B - SIM or SIMs faulty, failed or removed. The indicated reference is not a valid timing
alarms ON. Other - Faulty or disconnected cabling between SIMs source.
Reference NTDM alarm OFF. and NTDMs.
Alarms
SIM reference - Other NTDM faulty, failed or removed. The reference from the other NTDM is not
alarms OFF. Other - Faulty or disconnected cabling between available or invalid.
NTDM reference NTDMs.
alarm ON.
Page 29-248 7/07 76.5500/29, Rev R

Table 3.2 Status of Network Timing Distribution Module LEDs (Continued)
LED Status of
Selected SIM-A or SIM-B Indicates which SIM module is used as the In synchronous mode, only one LED is ON from
Reference selected reference timing reference. Normal, available state. among the possible selected references.
ON
Other NTDM Timing source is from the other NTDM or CCSM. Verify the other NTDM or CCSM timing source
reference ON by using RTRV-TMG command or by looking at
its LEDs1.
All selected No selected references. Verify the Master LED is ON. See Module Status
references OFF below*.
Module All selected This NTDM is providing internal timing with no Timing is not synchronized to external timing
Status references OFF. selected reference. Troubleshoot problem; DO source.
1
Master ON. NOT REMOVE this module.
Master OFF NTDM is using a selected reference. This is normal, available state, unless there is no
power to the modules when all LEDs are OFF.
Reference alarms Normal, available state.

OFF, SIM-A or
SIM-B selected
reference ON,
Master OFF,
Active ON, and
Fault OFF.
Both Active and - In self-diagnostic mode. The Active LED is ON when the NC is in-service,
Fault ON. - Until receives download and receives timing. or during power-up.
NTDM is among last components in the NC to
power-up.
- EEPROM or internal failure.
- Cable between NTDMs is faulty or removed.
Active OFF, Fault - The associated NC is OOS and this NTDM is in If the network status is out-of-service (OOS), the
ON. alarm. Refer to Table 3.9, page 29-269. NTDM is still active and provides timing.
- Faulted or failed module.
- Bent pin(s) on backplane connector.
Both Active and - The associated NC is OOS and this NTDM is - If the network status is OOS, the NTDM is still
Fault OFF. not in alarm. active and provides timing.
- No power to module, not in slot, breaker OFF, - If the NTDM is removed, the
bent pin(s) on backplane connector. RTRV-COND-EQPT command shows “card
Note: This module cannot be edited OOS. removed” for NTDM, ESM and CSM.
1. In synchronous mode with external timing, selected reference LED for either SIM-A or SIM-B is ON, or NTDM-x shows Other
NTDM selected reference LED ON and NTDM-y shows selected ref. SIM-x; RTRV-TMG command verifies NTDM-y
TMG=SIM-x/y. If problem exists with external timing, NTDMs fall back to asynchronous, internal timing mode, where NTDM-x
shows the Other NTDM LED and NTDM-y shows its master LED; using RTRV-TMG, NTDM-y TMG=INT. Refer to Table 3.3,
page 29-250.
76.5500/29, Rev R 7/07 Page 29-249

Table 3.3 Verifying the System Timing Mode

If NTDM-x Shows these If NTDM-y Shows these
Conditions Conditions System Timing Mode =
1. No reference alarms 1. No reference alarms. Sync
2. Selected ref. =SIM-A or SIM-B LED ON 2. Selected reference =same as NTDM-x.
3. RTRV-TMG=SIM-A or SIM-B 3. RTRV-TMG=SIM-A or SIM-B.
1. SIM-A/B reference alarm(s) 1. No reference alarms. Sync

2. Other NTDM selected ref LED ON 2. Selected reference =SIM-A or SIM-B LED
3. RTRV-TMG=SLV ON.
3. RTRV-TMG=SIM-A or SIM-B.
1. Reference alarms ON 1. Reference alarms ON. Fallback Async

2. Selected ref.=Other NTDM LED ON 2. Selected reference =Master LED ON.
3. RTV-TMG=SLV 3. RTRV-TMG=INT.
Page 29-250 7/07 76.5500/29, Rev R

Center Stage Module LEDs Figure 3.3 Center Stage Module LEDs
CSM CSM
active
active
fault fault
5508 5508A
Table 3.4 Status of Center Stage Module LEDs
Status of
LEDs Meaning Notes
Active ON, Normal, active state. Cannot edit the CSM to be out-of-service (OOS).
Fault OFF
All ON - When system is first powered on. Check the Network Group Controller (NGC).
- Module is abnormal-unequipped (ANR-UEQ).
- If all CSMs on a shelf show both LEDs are ON, possible Usually a temporary state that occurs during module
faulted NTDM or defective NTDM clock cable to the CSS or system initialization.
shelf.
Active OFF, - Faulty or failed module. Also check the NGC for the shelf that carries the CSM
Fault ON - Bad, loose microcoax between ESM and CSM. module that is in alarm.
- Blown fuse.
Both OFF - No power to module, not in slot, breaker OFF, bent pin(s)
on backplane connector.
- NC associated with the CSM in alarm is OOS.
76.5500/29, Rev R 7/07 Page 29-251

CSM Adapter Module LEDs Figure 3.4 CAM LEDs
CAM
81.55108
XMT -2 RCV -2
XMT -1 RCV -1
active
fault
rcv-2
rcv-1
static
sensitive
Page 29-252 7/07 76.5500/29, Rev R

Table 3.5 Status of CSM Adapter Module LEDs

Status of LEDs Meaning Notes
active Green indicates the
module is active and
functioning normally
fault • Red indicates a Fault LED lights while

blown fuse, loss of module is undergoing
voltage condition, or diagnostics.
loss of clock.
• Flashing indicates
software
initialization.
• It is off if no fault
exists.
RCV-1 • Green indicates that • Amber RCV-1 LED
the SDF48 receive could be caused by
port #1 is loss of frame, loss of
functioning multiframe, or
normally. incorrect link ID.
• Amber indicates a • Red RCV-1 LED
fault on the SDF48 could be caused by
receive port #1. loss of signal.
• Red indicates a fault
on the SDF48
receive port #1.
RCV-2 • Green indicates that • Amber RCV-2 LED
the SDF48 receive could be caused by
port #2 is loss of frame, loss of
functioning multiframe, or
normally. incorrect link ID.
• Amber indicates a • Red RCV-2 LED
fault on the SDF48 could be caused by
receive port #2. loss of signal.
• Red indicates a fault
on the SDF48
receive port #2.
76.5500/29, Rev R 7/07 Page 29-253

End Stage Module LEDs Figure 3.5 End Stage Module LEDs
ESM
active
fault
Table 3.6 Status of End Stage Module LEDs
Status of
LEDs Meaning Notes

Fault OFF
All ON - If ESM is in abnormal (ANR) state. For example, a problem If it is a microcoax problem, an autonomous message
with communication between the CSM and ESM, such as indicates which ESM, CSM, CAM, and line number
microcoax/wiring problem. have the problem.
- Before receiving download.
- If all CSMs on a shelf show both LEDs are ON, possible Usually a temporary state that occurs during module
faulted NTDM or defective NTDM clock cable to the CSS or system initialization.
shelf.
Active OFF, - Abnormal (ANR) module did not download. Also check the GCM for the shelf that carries the ESM
Fault ON - Faulted or failed module. Module is out-of-service, module that is in alarm.
abnormal (OOS-ANR).
- Microcoax has a severe fault.
Both OFF - Out-of-service (OOS). When the ESM is removed, the TSI that it serves
- No power to module, not in slot, breaker OFF, bent pin(s) normally shows the Fault LED ON and “ESM card
on backplane connector. removed” error message
Page 29-254 7/07 76.5500/29, Rev R

Troubleshooting the Network Complex

3.09 There are many reasons why the NC can become abnormal. By executing
the RTRV-COND-EQPT::NC command, you can get a better idea of where to
begin to solve the problem.
3.10 A list of conditions that may cause an abnormal state in the NC is provided
to assist you in isolating the cause, troubleshooting the problem, and clearing it
from the system:
• ESM, NIM, or PAM becomes OOS-NR by using an edit command.
• ESM becomes OOS-ANR-UEQ from a previously IS-NR state by

editing it OOS and removing it.
• ESM becomes IS-ANR-EQ by detecting an internal fault, or if the
corresponding ESM is unequipped.
• ESM becomes UEQ from a previously equipped state.
• CSM or CAM becomes ANR-EQ by detecting an internal fault.
• CSM or CAM becomes UEQ from a previously equipped state.
• Single NC power supply is turned off at the Breaker/Frame Alarm

Panel.
• Single NC power supply is removed.
• NC power supply is determined as ANR by internal software audits.
• NGC or CGC becomes OOS by using an edit command from an IS-NR

state.
• NGC or CGC becomes ANR by detecting an internal fault.
• NGC or CGC is removed.
• NTDM or CCSM becomes ANR, or is removed.
• TSI becomes ANR by detecting an internal fault.
• TSI becomes OOS from the IS-NR state.
• TSI becomes OOS-ANR-UEQ and does not have the same state as
its redundant TSI on the same port shelf.
• PTx is removed or faulted.
• Port shelf was degrown incorrectly. Proper procedures, described in

Tellabs 5500/5500S Provisioning Manual, 76.5500/23, were not
correctly followed.
76.5500/29, Rev R 7/07 Page 29-255

System Pre-Checks
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */
command:
System response:
M ctag COMPLD

__ 2.1 Verify that your login is a UPC of an A8 or higher.

Page 29-256 7/07 76.5500/29, Rev R

__ 3. Retrieve the present state of both NCs by entering the following

command:
RTRV-EQPT::NC-A&&-B:ctag;
System response:
M ctag COMPLD

Standard Core Switch:
"NC-A::SIZE=256,EFSIZE=256,ESMSIZE=256,MAP=CMM,ALMPF=99:PST=IS-ANR"
"NC-B::SIZE=256,EFSIZE=256,ESMSIZE=256,MAP=CMM,ALMPF=99:PST=IS-ANR"
Hybrid Core Switch:

Consolidated Core Switch:

__ 3.1 If the system response for both NC-A and NC-B is

in-service, abnormal (IS-ANR), go to step 4,
page 29-258.
__ 3.2 If the system response verifies that one NC copy, either

A or B, is in-service, abnormal (IS-ANR), go to step 8,
page 29-262.
__ 3.3 If the system response verifies that one or both NCs are
page 29-289.
76.5500/29, Rev R 7/07 Page 29-257

__ 4. Retrieve all current alarms and status conditions for the NCs by
RTRV-COND-EQPT::NC-A&&-B:ctag;
System response when no alarms or status conditions exist:

M ctag COMPLD
System response when alarms or status conditions do exist:

M ctag COMPLD
"ESM-0993-A,EQPT:NR,INT,NSA,02-18,13-39-06,NEND,,,\"ESM card removed\""
"TSI31-0065-A,:,,,,,,,,\"TSI is OOS\""
"ESM-0001-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal signal degradation

detected at ESM line 10 from CSM\":,ISLTD"
Note: If there is a condition posted against more than one module, remember to
troubleshoot the least traffic affecting module first, such as a TSI before an
ESM. Troubleshoot the port shelf first, then the network complex, and then
the administrative complex.
__ 4.1 If you are troubleshooting a Tellabs 5500/5500S system

with high density port shelves (HDPSs) and the system
response shows any of the following alarm messages,
the SDF cabling length from one TSI96 to its network
copy has exceeded the acceptable range. Follow your
company's prescribed procedures for obtaining
technical assistance or call Tellabs Technical
Note: The difference between the maximum length among all SDF cables from
one TSI96 to its network copy and the minimum length among all SDF
cables from the other TSI96 to its network copy cannot exceed 100 feet.
The difference between the maximum and minimum lengths of all SDF
cables from one TSI96 to its network copy cannot exceed 50 feet. If either
of these cable length limitations is exceeded, one of the following alarms
will be generated.
\"Excessive length differential between SDF cable(s) to TSI A and SDF cable(s) to
TSI B\"
\"Excessive length differential between SDF cables to TSI Copy A\"
\"Excessive length differential between SDF cables to TSI Copy B\"
Page 29-258 7/07 76.5500/29, Rev R

__ 4.2 Does the system response display alarm messages for

the Center Switch Shelf Power Supply Module (CSSPS)
associated with the alarmed NC?
__ 4.2.1 If no, go to substep 4.3.

the End Switch Shelf Power Supply Module (ESSPS)
__ 4.3.1 If yes, go to End Stage Shelf Power

Supply Module (ESSPS), page 29-358.
__ 5. Check the power supply modules (PS-NP) on the primary Center

Switch Shelf Copy A (CSS-A) and the primary Center Switch Shelf
Copy B (CSS-B).
Note: The primary CSS contains the Network Timing Distribution Module
(NTDM) and Network Group Controller Module (NGC). There is one
primary CSS on both the NC-A and NC-B racks.
__ 5.1 If the green Power LEDs are lit on all four power supply
modules for both the primary NC-A and NC-B, go to
__ 5.2 If the green Power LEDs are not lit on all four power
supply modules for both the primary NC-A and NC-B, go
to Center Stage Shelf Power Supply Module (CSSPS),
page 29-353.
76.5500/29, Rev R 7/07 Page 29-259

Caution:
If both NCs are abnormal and the trouble is not isolated to a failed power supply,
1.630.798.7070 (outside North America). Failure to do so may result in a traffic
interruption.
__ 6. Physically check the LAN cables to both NGCs, on the primary NC-A
shelf and on the primary NC-B shelf:
__ 6.1 Verify that connectors J5 and J6 on the CSS-A
backplane and connectors J5 and J6 on the CSS-B
backplane are securely connected.
__ 6.1.1 If there are any loose LAN cables,

securely attach them to the backplane, or
replace any defective cables as
necessary.
__ 6.2 Does the NC alarm message clear?
__ 6.2.1 If yes, return to step 3, page 29-257.
Page 29-260 7/07 76.5500/29, Rev R

RTRV-TMG:::ctag;
System response:
M ctag RTRV
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

prescribed procedures for obtaining technical
1.800.443.5555 (North America) or 1.630.798.7070
(outside North America) for further analysis.
__ 7.2 Verify that one NC copy equals PREFNET=YES and

one NC copy equals PREFNET=NO. If both copies
PREFNET parameters are the same, follow your
1.630.798.7070 (outside North America) for further
analysis.
76.5500/29, Rev R 7/07 Page 29-261

Warning:
network and that they are listening to the preferred copy data byte by

System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV

improperly inhibited, continue to step 9, page 29-264.
Page 29-262 7/07 76.5500/29, Rev R


improperly inhibited, enter the RTRV-BBBC command
again, specifying the particular module that is

Example:
RTRV-BBBC-INH::PM1D-0001-01:ctag;
System response:
M ctag COMPLD

"PM1D-0001-01:PORTID=0001-01,PORTTYPE=T1,ADATA=OK-SELECTED,BDATA=OKNOTSELECTED,
ACLK=OK-SELECTED,BCLK=OK-NOTSELECTED"
"PM1D-0001-01:PORTID=0001-03,PORTTYPE=T1,ADATA=INH-LOCAL,BDATA=OK-FORCED,ACLK=INHLOC
AL,
BCLK=OK-FORCED"
"PM1D-0001-01:PORTID=0001-06,PORTTYPE=T1"
/* If a partial line is displayed, it indicates an error retrieving data */

76.5500/29, Rev R 7/07 Page 29-263

__ 9. Retrieve the master/slave status of the SIMs by entering the following

command:
RTRV-TMG:::ctag;
System response:
M ctag RTRV
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
__ 9.1 Record the master/slave relationship (TMG=MSTR and

TMG=SLV). The active LED on the master SIM is on
constantly. Only one SIM is master, the other is slave:
SIM TMG = MSTR TMG = SLV
SIM-A
SIM-B

NTDM-A
NTDM-B
CCSM-SH1-9
CCSM-SH2-9
Page 29-264 7/07 76.5500/29, Rev R

__ 9.3 Verify that the non-alarmed NTDM and CCSM is

listening to the master SIM. See substep 9.1,
page 29-264.
__ 9.3.1 If the non-alarmed NTDM and CCSM is

listening to the master SIM, continue to
step 10.
__ 9.3.2 If not, follow your company's prescribed

North America).
__ 10. Retrieve all current alarms by entering the following command:


M ctag COMPLD

M ctag COMPLD

"ESM-0129-A,EQPT:MJ,INT,NSA,01-29,04-26-12,NEND,,,\"ESM card removed\""
__ 10.1 Go to Determining the Meaning of Alarm Messages,

page 29-266, to troubleshoot the faulted module listed
in the alarm message(s) received.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-265


3.12 Network Complex alarm messages are listed in the Table 3.7,
page 29-267, through Table 3.10, page 29-271. Each table lists the alarm
messages for a certain module type or entity, the description of that alarm
message, a probable cause for the alarm, and then directs you to the appropriate
3.13 Choose the correct table for the module type that is faulted:
• For the Network Complex, go to Table 3.7, page 29-267.
• For the NGC go to Table 3.8, page 29-268.

• For the NTDM go to Table 3.9, page 29-269.
• For the CSM, go to Table 3.10, page 29-271.
• For the CAM, go to Table 3.11, page 29-273.
• For the ESM, go to Table 3.12, page 29-276.
• For the CSSPS, go to Table 3.13, page 29-280.
• For the ESSPS, go to Table 3.14, page 29-281.
Page 29-266 7/07 76.5500/29, Rev R

Network Complex (NC) Alarm Messages

3.14 In order to troubleshoot the alarm message(s) received for the Network
Complex, use the following table. The first column of the table lists the possible
alarm messages that can be generated for an NC. The second column lists a
alarm.
Table 3.7 Network Complex Alarm Messages

MAN GC LAN Miscabled - AC-A on <ess_aid> AC-A is connected to the The LAN cables are improperly wired. Go
LAN B, where <ess_aid> is ESS-xxxx-y, NC-A ESS retrofit bar LAN B. to Local Area Network (LAN-1),
xxxx is the lead SDF of the shelf, and y is A page 29-230, to troubleshoot the LAN.
or B to indicate Copy
MAN GC LAN Miscabled - AC-B on <ess_aid> AC-B is connected to the The LAN cables are improperly wired. Go
LAN A, where <ess_aid> is ESS-xxxx-y, NC-A ESS retrofit bar LAN A. to Local Area Network (LAN-1),
xxxx is the lead SDF of the shelf, and y is A page 29-230, to troubleshoot the LAN.
or B to indicate Copy
PROTNA Network Complex failed (ANR) - not One of the elements in the NC Defective module in the network complex.
available for protection has faulted. It clears when all
NC elements have returned to This alarm message may be
a normal state. accompanied by another alarm message
related to a specific module. Go to the
alarm message table for the specific
module in alarm to troubleshoot the
problem.
PROTNA Network Complex OOS - not available for A command was entered that The NC has been edited by command to
protection put the NC into an an out-of-service state.
out-of-service state.The alarm
clears when the command to Go to step 19, page 29-289.
put the NC back in service is
entered.
PWR Possible LAN or power failure: NGCs or Both NCs and NGCs are Possible causes:
CGCs ANR abnormal due to possible LAN - LAN cables to both NGCs are
or power failure. disconnected or faulty.
- Both power supplies on the shelf with
the NGCs are faulty.
Go to one of the following:

- Local Area Network (LAN-1),
page 29-230, to troubleshoot the LAN
- Network Group Controller Module
(NGC), page 29-282, to troubleshoot the
NGC
- Consolidated Group Controller Module
(CGCM), page 29-450, to troubleshoot
the CGC
- End Stage Shelf Power Supply Module
(ESSPS), page 29-358, to troubleshoot
the power supplies.
76.5500/29, Rev R 7/07 Page 29-267

Network Group Controller Module (NGC) Alarm Messages

3.15 In order to troubleshoot the alarm message(s) received for a faulted NGC,
messages that can be generated for an NGC. The second column lists a
alarm.
Table 3.8 Network Group Controller Module (NGC) Alarm Messages

INT EEPROM failure Either a failure to read the EEPROM Internal module failure.
information or a failure to store this
information to the database has Go to Network Group Controller Module
occurred. (NGC), page 29-282.
INT Failed diagnostics The NGC has failed one of its internal Failed one or more internal diagnostic
diagnostics either on power-up or the tests. Failed or faulted module.
TL1 DGN command.
Go to Network Group Controller Module
(NGC), page 29-282.
INT Module not compatible with The NGC is not supported by the Module revision level is either lower or
existing software software version currently operating on higher than the levels supported by the
the system. current software version.

(NGC), page 29-282.
INT NGC card removed The active AC has detected the Either the NGC is missing from the NC
absence of the NGC or shelf or there is a problem with the LAN
communications with it have failed. cable or connectors.

(NGC), page 29-282.
meet revision level requirements not match the set of valid revision version of the software.
levels maintained in the system
database. Use RTRV-REVTBL Go to Network Group Controller Module
command to view the system database (NGC), page 29-282.
of valid module revision levels. Refer to
Tellabs 5500/5500S Command
Reference Manual, 76.5500/13.
Page 29-268 7/07 76.5500/29, Rev R

Network Timing Distribution Module (NTDM) Alarm Messages

NTDM, use the following table. The first column of the table lists the possible alarm
messages that can be generated for an NTDM. The second column lists a
alarm.
Table 3.9 Network Timing Distribution Module Alarm Messages

INT EEPROM failure A failure to read the EEPROM Internal module failure.
information to the database has Go to Network Timing Distribution Module
occurred. (NTDM), page 29-292.
INT Failure to initialize NTD While in its internal initialization at power During power-up, the NTDM failed its
up, the NTDM is in failure mode. internal initialization or diagnostics check.
Go to Network Timing Distribution Module

(NTDM), page 29-292.
INT Internal failure detected Reporting NTDM is detecting one of One of the following is the likely cause:
several possible errors, but cannot - Download requested while NTDM is in
isolate the problem. normal (NR) state.
- NTDM cannot communicate with its GC.

INT Module not compatible with Reporting module is not supported by Module revision level is either lower or
existing software the software version currently operating higher than the levels supported by the
on the system. current software version. Go to Network
Timing Distribution Module (NTDM),
page 29-292.
INT NTD loses multi-frame alignment The NTDM has detected a loss of lock One of the following has occurred:
to other NTD or CCSM to the multi-frame alignment signal - A momentary disruption in the timing
imbedded in the NTD or the CCSM. signal from the NTDM or CCSM
- Defective NTDM module
- Defective CCSM

to SIM-A to the multi-frame alignment signal - A momentary disruption in the timing
imbedded in the SIM-A output clock signal from the SIM
signal. - Defective NTDM module
- Defective SIM

to SIM-B to the multi-frame alignment signal - A momentary disruption in the timing
imbedded in the SIM-B output clock signal from the SIM
signal. - Defective NTDM module
- Defective SIM

76.5500/29, Rev R 7/07 Page 29-269

Table 3.9 Network Timing Distribution Module Alarm Messages (Continued)

INT NTD loses frequency lock to The slave NTDM has lost frequency lock Either the NTDM cable is defective or it is
other NTD or CCSM (no clock) with the master NTDM, or the CCSM. disconnected from the NTDM between the
network bays.

INT NTD loses frequency lock to The NTDM is not longer detecting a One of the following has occurred:
SIM-A (no clock) frequency signal from SIM-A. - A momentary disruption in the timing
signal from the SIM
- Defective SIM

INT NTD loses frequency lock to The NTDM is not longer detecting a One of the following has occurred:
SIM-B (no clock) frequency signal from SIM-B. - A momentary disruption in the timing
signal from the SIM
- Defective SIM

INT NTD card removed The NGC has detected that the NTDM is One of the following has occurred:
missing from the system. - The NTDM is removed from the shelf.
- The PCP Bus has failed between the
NGC and NTDM modules.
- The NTDM is not properly seated within
the equipment shelf.

MODINSRT Module inserted The module was removed, but is now in Module has been inserted in its slot on the
PAINTGRT Faulty timing signal from other The timing signal from one NTDM to the The cable is missing.
NTDM (possible cable missing) other NTDM is faulty, possibly due to a
missing cable. Go to Network Timing Distribution Module
meet revision level requirements not match the set of valid revision levels version of the software.
maintained in the system database. Use
RTRV-REVTBL command to view the Go to Network Timing Distribution Module
system database of valid module (NTDM), page 29-292.
Manual, 76.5500/13.
Page 29-270 7/07 76.5500/29, Rev R

Center Stage Module (CSM) Alarm Messages

3.17 In order to troubleshoot the alarm message(s) received for a faulted CSM,
messages that can be generated for an CSM. The second column lists a
alarm.
Table 3.10 Center Stage Module Alarm Messages

INT Connection Memory failure Failure to write/read connection Defective CSM module.
memory through the reporting CSM.
Go to Center Stage Module (CSM),
page 29-307.
INT CSM card removed Active NGC has detected the absence Either the CSM is absent or the NTDM
of the CSM or has lost has been removed, causing a
communications with it. reinitialization of the CSM and other
modules.

page 29-307.
INT CSM connection memory The CMCI (Connection Management Change to software database not
inconsistent with database Content Integrity) audit has detected a propagated to the CSM connection
difference between the CSM memory.
connection memory and the database.
page 29-307.
INT EEPROM failure Either a failure to read chip Internal module failure.
information to the database has Go to Center Stage Module (CSM),
INT Failed diagnostics The CSM has failed one of its internal Failed one or more internal diagnostic
diagnostics, which is generated by the tests. Failed or faulted module.
TL1 DGN command.
page 29-307.
INT Input SDF failed at CSM line x from ICOMM audit between Stage 4 ESMs Most probable cause is incorrect cabling
ESM (suspect cable)\" where x is in and Stage 3 CSMs has failed. The between the CSM and the ESM.
the range 0-95 CSM line number indicates the cable However, problems with the ESM or
where the ICOMM failure actually CSM module (bad ICOMM data) could
occurred. ICOMM test is intended to also cause this message to be displayed.
verify correct CSM to ESM cabling.
page 29-307.
INT Module not compatible with existing The CSM is not supported by the Module revision level is either lower or
software software version currently operating higher than the levels supported by the
on the system. current software version.

page 29-307.
76.5500/29, Rev R 7/07 Page 29-271

Table 3.10 Center Stage Module Alarm Messages (Continued)

INT Stage three tubby loss of frame on The stage three switch element has Do not attempt to troubleshoot this alarm
SDF 0 through 31 detected a loss of frame. message. Follow your company's
Technical Assistance at 1.800.443.5555
(North America) or 1.630.798.7070
INT Stage three tubby parity error on The stage three switch element has Do not attempt to troubleshoot this alarm
SDF 0 through 31 detected a parity error. message. Follow your company's
INT Stage three tubby yellow alarm on The stage three switch element has Do not attempt to troubleshoot this alarm
SDF 0 through 31 detected a yellow alarm. message. Follow your company's
MODINSRT Module Inserted The module was removed, but is now Module has been inserted in its slot on
in its slot on the shelf. the shelf. No recovery necessary.
REVLVL CSM (81.5508) in a network size A system configured with a network In a system with a network size of 1024
1024 system must be Rev I or size of 1024 (SDFs) requires the use (SDFs), a CSM with a revision level prior
greater of a CSM Revision I or greater. to Rev. I has been inserted into the CSM
slot on the shelf.

page 29-307.
REVLVL Module revision level does not meet The revision level of the module does This module is not supported by this
revision level requirements not match the set of valid revision version of the software.
database. Use RTRV-REVTBL Go to Center Stage Module (CSM),
76.550/13.
SENA Supported Entity (NTDM) Not The active NC is not detecting that the The system has detected a problem with
Available active NTDM is in a normal state in the the active NTDM.
system. Possible causes:
This message displays when the - The NC associated with the specified
active NC cannot communicate with NTDM is in the process of resetting.
the specified NTDM. - NTDM has been physically unseated
from the backplane.
- NTDM is resetting or reinitializing.
Go to Network Timing Distribution

Module (NTDM), page 29-292.
Page 29-272 7/07 76.5500/29, Rev R

CSM Adapter Module (CAM) Alarm Messages

3.18 In order to troubleshoot the alarm message(s) received for a faulted CAM,
messages that can be generated for an CAM. The second column lists a
alarm.
Table 3.11 CSM Adapter (CAM) Alarm Messages

INT Failed diagnostics The CAM has failed one of its internal Failed one or more internal diagnostic
TL1 DGN command.
Go to CSM Adapter Module (CAM),
page 29-318.
INT Input SDF failed at CAM line x ICOMM audit between CAMs and ESMs Most probable cause is incorrect cabling
from ESM (suspect cable) where x has failed. The CAM line number between the CAM and the ESM.
is in the range 0 - 95 indicates the cable where the ICOMM However, problems with the ESM or
failure actually occurred. ICOMM test is CAM module (bad ICOMM data) could
intended to verify correct CAM to ESM also cause this message to be displayed.
cabling. Go to CSM Adapter Module (CAM),
page 29-318.
INT Internal Failure Detected Reporting CAM is detecting one of One of the following is the likely cause:
several possible errors, but cannot - Download requested while CAM is in
- CAM cannot communicate with its GC.

page 29-318.
INT Module removed Active GC has detected the absence of Module has been removed from its slot,
a CAM. or it has not responded to
communications from the CGC, or its
EEPROMs are corrupt or incompatible
with the current software version.

page 29-318.
INT SDF48 Loss of Frame detected at The CAM has detected an LOF on the One or more of the following has
fiber X, where X is the fiber SDF48 cable. occurred:
number. - CAM is losing framing.
- Output stage on NIM is not maintaining
framing.
- Fiber optic cable or connectors are
damaged.

page 29-318, to troubleshoot the CAM,
or to Network Interface Module (NIM),
page 29-434, to troubleshoot the NIM.
76.5500/29, Rev R 7/07 Page 29-273

Table 3.11 CSM Adapter (CAM) Alarm Messages (Continued)

INT SDF48 Loss of Multi-Frame The CAM has detected two consecutive Either the quality of the signal received
alignment detected at fiber X, H4 values that do not agree with any from the NIM is poor, or the CAM has
where X is the fiber number. part of the multiframe sequence, and it failed.
has declared a loss of multiframe
(LOMF) defect. Verify SIM cable lengths are correct.
(Refer to Synchronization Interface
Module (SIM), page 29-146.)

page 29-318.
INT SDF48 Loss of Signal detected at A Loss of Signal has been declared at a Disconnected or broken cable. Go to
fiber X, where X is the fiber port on the CAM. CSM Adapter Module (CAM),
number. page 29-318, to troubleshoot the SDF
fiber.
INT SDF48 mismatch detected at fiber An SDF48 cable is connected to the Either the SDF48 cables for port 1 and
X, where X is the mismatched fiber wrong port. port 2, or Copy A and Copy B, are
(X = 1 or 2). reversed.

page 29-318, to troubleshoot the SDF
fiber.
INT SDF48 Parity Error detected at SDF parity errors were detected at the Either the CAM or NIM is faulty.
fiber X, where X is the fiber port.
number. Go to CSM Adapter Module (CAM),
or go to Network Interface Module (NIM),
INT SDF48 Yellow Frame at fiber X. The CAM has declared a Yellow Frame Either the CAM or NIM is faulty.
where X is the fiber number. on a fiber that is connected to the NIM.
INT SDF48 Yellow Multi-Frame at fiber The PAM has declared a Yellow Either the CAM or NIM is faulty.
X, where X is the fiber number. Multi-Frame on a fiber that is connected
tot he TSI. Go to CSM Adapter Module (CAM),
MODINSRT Module Inserted The module was removed, but is now in Module has been inserted in its slot on
RTFV-REVTBL command to view the Go to CSM Adapter Module (CAM),
system database of valid module page 29-318.
Manual, 76.550/13.
Page 29-274 7/07 76.5500/29, Rev R

Table 3.11 CSM Adapter (CAM) Alarm Messages (Continued)

SENA Supporting Entity Not Available The active NC is detecting that either the The system has detected a problem with
active NIM, active CCSM, or active the active NTDM, CCSM, or NIM.
NTDM, are in abnormal states. Possible causes:
- The NC associated with the specified
This message displays when the active NTDM, CCSM, or NIM is in the process
CAM cannot communicate with the of resetting.
NTDM, CCSM, or NIM. - NTDM, CCSM, or NIM has been
physically unseated from the backplane.
- NTDM, CCSM, or NIM is resetting or
reinitializing.
Go to Network Timing Distribution

Module (NTDM), page 29-292, to
troubleshoot the NTDM.
Go to Consolidated Core Switch Module

(CCSM), page 29-394, to troubleshoot
the CCSM.
Go to Network Interface Module (NIM),

76.5500/29, Rev R 7/07 Page 29-275

End Stage Module (ESM) Alarm Messages

3.19 In order to troubleshoot the alarm message(s) received for a faulted ESM,
messages that can be generated for an ESM. The second column lists a
alarm.
Table 3.12 End Stage Module Alarm Messages

CONTCOM Loss of GC LAN communication LAN A cable has been disconnected at Verify that ESS bus bar is terminated
from ESM to PGC on LAN A the ESM. properly, and that all cables are properly
connected.
Verify that the cable between the ESS

bus bar and the ESMU dongle connector
is secure.
For more information, refer to Tellabs

5500 Installation, 76.5500/7.
CONTCOM Loss of GC LAN communication LAN B cable has been disconnected at Verify that ESS bus bar is terminated
from ESM to PGC on LAN B the ESM. properly, and that all cables are properly
connected.
Verify that the cable between the ESS

bus bar and the ESMU dongle connector
is secure.
For more information, refer to Tellabs

5500 Installation, 76.5500/7.
INT Connection Memory Failure Failure to write/read connection Defective ESM.

memory through the reporting ESM.
Go to End Stage Module (ESM),
page 29-332.
INT EEPROM failure Either a failure to read the EEPROM Internal module failure.
information to the database has Go to End Stage Module (ESM),
INT ESM card removed Active NGC has detected the absence - Most probable cause is removing this
of an ESM module. module.
- ESM is reinserted before it has been
reinitialized.
- The NGC loses communications with
the ESM.
- The NTDM is reinserted and ESM is
already present during system
initialization of the network complex.
In these last two cases it is part of

initialization sequences and does not
affect the system.

page 29-332.
Page 29-276 7/07 76.5500/29, Rev R

Table 3.12 End Stage Module Alarm Messages (Continued)

INT ESM connection memory The CMCI (Connection Management During an NCI audit, it was found that
inconsistent with database Content Integrity) audit has detected a one or more of the tubby chips on the
difference between the ESM connection ESM does not match the database.
memory and the database.
page 29-332
INT Failed diagnostics The ESM has failed one of its internal Failed one or more internal diagnostic
TL1 DGN command.
page 29-332.
INT Failure to initialize ESM The system does not recognize the Either cable faults exist or the ESM has
ESM. failed.

page 29-332.
INT Incoming SDF failure from TSI There is an incoming SDF failure from There is an SDF cable fault.
(possible cable fault) the TSI, possibly due to a cable fault.
Go to Time Slot Interchange Module
(TSI), page 29-506, to troubleshoot the
TSI.
INT Input SDF failed on ESM line x ICOMM audit between CAMs and Most probable cause is incorrect cabling
from CAM (suspect cable), where ESMs has failed. The ESM line number between the CAM and the ESM.
x is in the range 0 to 35 indicates the cable where the ICOMM However, problems with the ESM or CAM
failure actually occurred. ICOMM test is module (bad ICOMM data) could also
intended to verify correct CAM to ESM cause this message to be displayed.
cabling.
page 29-332.
INT Input SDF failed on ESM line x ICOMM audit between Stage 3 CSMs Most probable cause is incorrect cabling
from CSM (suspect cable) [where and Stage 4 ESMs has failed. The ESM between the CSM and the ESM.
x = 0-35] line number indicates the cable where However, problems with the ESM or CSM
the ICOMM failure actually occurred. module (bad ICOMM data) could also
ICOMM test is intended to verify correct cause this message to be displayed.
CSM to ESM cabling.
page 29-332.
INT Internal signal degradation at ESM The NC runs periodic audits on each One or more of the following has
line x from CAM, where x is in the piece of equipment. Reported CAM has occurred:
range 0 to 35 detected a parity error from the ESM. - Microcoax between ESM and CAM is
bad or not connected.
- Internal fault in corresponding CAM.
- Internal fault in corresponding ESM.

page 29-332.
INT Internal signal degradation at ESM The NC runs periodic audits on each One or more of the following has
line x from CSM (where x = 00-35) piece of equipment. Reported CSM has occurred:
detected a parity error from the ESM. - Microcoax between ESM and CSM is
- Internal fault in corresponding CSM.

page 29-332.
76.5500/29, Rev R 7/07 Page 29-277


INT Internal signal degradation at CAM The NC runs periodic audits on each One or more of the following has
line x from ESM, where x is in the piece of equipment. Reported CAM has occurred:
range 0 to 95 detected a parity error from the ESM. - Microcoax between ESM and CAM is

page 29-332.
INT Internal signal degradation at CSM The NC runs periodic audits on each One or more of the following has
line x from ESM (where x = 00-95) piece of equipment. Reported CSM has occurred:
detected a parity error from the ESM. - Microcoax between ESM and CSM is

page 29-332.
INT Internal signal failure at CAM line x The NC runs periodic audits on each One or more of the following has
from ESM, where x is in the range piece of equipment. Reported CAM has occurred:
0 to 95 detected LOF from the ESM. - Microcoax between ESM and CAM is

page 29-332.
INT Internal signal failure at CSM line x The NC runs periodic audits on each One or more of the following has
from ESM (where x = 0-95) piece of equipment. Reported CSM has occurred:
detected LOF from the ESM. - Microcoax between ESM and CSM is

page 29-332.
INT Internal signal failure detected at The NC runs periodic audits on each One or more of the following has
ESM line x from CAM, where x is piece of equipment. Reported ESM has occurred:
in the range 0 to 35 detected LOF from CAM. - Microcoax between ESM and CAM is

page 29-332.
INT Internal signal failure detected at The NC runs periodic audits on each One or more of the following has
ESM line x from CSM (where x = piece of equipment. Reported ESM has occurred:
00-35) detected LOF from the CSM. - Microcoax between ESM and CSM is

page 29-332.
Page 29-278 7/07 76.5500/29, Rev R


INT Loss of clock on ESM The ESM is experiencing a loss of The ESM has lost its clocking signal.
clock.
page 29-332.
INT Module not compatible with The ESM is not supported by the Module revision level is either lower or

page 29-332.
INT Stage two tubby loss of frame on The stage two switch element has Do not attempt to troubleshoot this alarm
SDF 0 to 31 detected a loss of frame. message. Follow your company's
INT Stage two tubby parity error on The stage two switch element has Do not attempt to troubleshoot this alarm
SDF 0 to 31 detected a parity error. message. Follow your company's
INT Stage two tubby yellow alarm on The stage two switch element has Do not attempt to troubleshoot this alarm
SDF 0 to 31 detected a yellow alarm. message. Follow your company's
INT Stage four tubby loss of frame on The stage four switch element has Do not attempt to troubleshoot this alarm
SDF 0 to 35 detected a loss of frame. message. Follow your company's
INT Stage four tubby parity error on The stage four switch element has Do not attempt to troubleshoot this alarm
SDF 0 to 35 detected a parity error. message. Follow your company's
INT Stage four tubby yellow alarm on The stage four switch element has Do not attempt to troubleshoot this alarm
SDF 0 to 35 detected a yellow alarm. message. Follow your company's
76.5500/29, Rev R 7/07 Page 29-279


MEA Inserted card inconsistent with The ESM type is not consistent with the The ESM is the wrong type for the PGC
supported PGC shelf supported PGC shelf. shelf.

page 29-332.
MODINSRT Module inserted The module was removed, but is now in Module has been inserted in its slot on
maintained in the system database.
Use RTRV-REVTBL command to view Go to End Stage Module (ESM),
the system database of valid module page 29-332.
Manual, 76.5500/13.
SENA Supporting Entity Not Available Slot is either unequipped or the module If the NTDM or CCSM is in-service and
is faulted. transitions to ANR-UEQ, and the ESM is
equipped prior to the NTDM transitioning
to ANR-UEQ.

page 29-332.
Center Stage Shelf Power Supply Module (CSSPS) Alarm Messages

CSSPS, use the following table. The first column of the table lists the possible
alarm messages that can be generated for an CSSPS. The second column lists a
alarm.
Table 3.13 Center Stage Shelf Power Supply Module (CSSPS) Alarm Messages
INT Power supply module failed NGC has detected a failure on one of Power supply module has an internal
the CSSPS modules. failure.
Go to Center Stage Shelf Power

Supply Module (CSSPS), page 29-353.
INT Power supply module removed NGC has detected the absence of one Power supply module has been
of the CSSPS modules. removed from the shelf.

PROTNA Power supply failed (ANR) - not There is an abnormal condition with There is a problem with the power
available for protection the power supply and the abnormal supply and/or power supply module.
side has lost power redundancy.
Page 29-280 7/07 76.5500/29, Rev R

End Stage Shelf Power Supply Module (ESSPS) Alarm Messages

ESSPS, use the following table. The first column of the table lists the possible
alarm messages that can be generated for an ESSPS. The second column lists a
alarm.
Table 3.14 End Stage Shelf Power Supply Module (ESSPS) Alarm Messages
INT Power supply module failed Power supply audit indicates that a Power supply module has an internal
power supply has failed on the ESM failure. This could be because of
shelf. It does not indicate which power external loading conditions present on
supply (A or B) has failed on the ESM the other shelf or on the other power
shelf. supply module.
Go to End Stage Shelf Power Supply

Module (ESSPS), page 29-358.
INT Power supply module removed A power supply module has been Power supply module has been
removed. removed from either side of the ESM
shelf.

PROTNA Power supply failed (ANR) - not There is an abnormal condition with There is a problem with the power
available for protection the power supply and the abnormal supply and/or power supply module.
side has lost power redundancy.
76.5500/29, Rev R 7/07 Page 29-281

Network Group Controller Module (NGC)

3.22 In this section, you will troubleshoot the alarmed Network Group Controller
Module (NGC). You should have completed System Pre-Checks, page 29-256,
and been directed to this section from an alarm message table.
3.23 A spare NGC may be required in order to perform this procedure. Refer to
Caution:
Performing the following step may cause a temporary interruption of traffic.
Follow internal policy for Network Complex (NC) copy switching.
Note: The active LEDs of all the modules, except the power supply module
(PSNP), on the abnormal (ANR) NC will turn off during normal system
behavior.
Caution:
Failure to resolve internal path integrity errors in the redundant NC copy prior to
an NC copy switch may result in service interruption.
__ 1. Retrieve all internal path integrity errors by entering the following

command:
RTRV-COND-ALL:::ctag::PAINTGRT;
System response when no internal path integrity errors exist:

M ctag COMPLD
System response when internal path integrity errors do exist:

M ctag COMPLD

"VT1-0615-1-3,VT1:MN,PAINTGRT,NSA,04-30,11-18-33,NEND,,,\"TVT parity error detected
on network copy x\""
Where: x = Network Complex copy (A or B).
__ 1.1 If the system response generates a TVT parity error, go

to Troubleshooting Internal Path Integrity Errors (DS1
CST, DS1 DGR, VT1, or VPG Termination),
page 29-1027, in Section 7 to resolve the problem
before continuing with this procedure.
__ 1.2 If the system response does not generate a TVT parity

error, continue to the next step.
Page 29-282 7/07 76.5500/29, Rev R

Caution:
The following action may cause temporary system traffic interruption. Follow
internal polity for NC copy switching.
__ 2. Edit the NC supporting the alarmed NGC out-of-service (OOS) by

ED-EQPT::NC-x:ctag::::OOS;
Where: x = Alarmed NC (A or B).
System response:
M ctag COMPLD

"NC-B:MN,PROTNA,NSA,08-28,13-27-49,NEND:\"Network Complex OOS - not available for
protection\":,ISLTD"
__ 3. Choose one of the following:

__ 3.1 If editing the alarmed NC out-of-service caused traffic
interruption, and the system does not recover from the
traffic interruption, go to step 4, page 29-283.
__ 3.2 If editing the alarmed NC out-of-service does not cause

__ 3.3 If the system response results in Requested Operation

Failed (SROF), go to step 6, page 29-284.
__ 4. Edit the NC supporting the alarmed NGC in-service (IS) by entering

ED-EQPT::NC-x:ctag:::MODE=FRCD:IS;
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-283

__ 5. Retrieve the present state of the NC supporting the alarmed NGC by

RTRV-EQPT::NC-x:ctag;
System response:
M ctag COMPLD

"NC-A::SIZE=256,EFSIZE=256,ESMSIZE=256,MAP=CMM,ALMPF=99:PST=OOS-ANR"
Hybrid Core Switch:


__ 5.1 If the system response verifies that the alarmed NC is


1.800.443.5555 (North America) or 1.630.798.7070
__ 6. Visually verify that the alarmed NGC module is present in the slot.
__ 6.1 There is a module present in the slot. go to step 7.

page 29-286.
__ 7. Edit the NGC associated with the alarmed NC out-of-service (OOS) by

ED-EQPT::NGC-y:ctag:::MODE=FRCD:OOS;
Where: y = Alarmed NC (A or B).
System response:
M ctag COMPLD
__ 7.1 If the system response results in Requested Operation

Failed (SROF), go to step 11, page 29-286.
Page 29-284 7/07 76.5500/29, Rev R

__ 8. Diagnose the problem on the alarmed NGC by entering the following

command:
Note 1: The NGC must be out-of-service (OOS) and it must be equipped (EQ) in
order to perform diagnostics on it.
Note 2: Module front panel LEDs light for approximately 10 seconds. This is
normal behavior.
DGN-EQPT::NGC-x:ctag;
System response:
M ctag COMPLD

"NGC-A:PASS-1"
"NGC-A:FAIL-0"
__ 8.1 If the system response shows 0 passed iterations and 1

failed iteration, go to step 9.
__ 8.2 If the system response shows 1 passed iteration and 0

76.5500/29, Rev R 7/07 Page 29-285

__ 10. Diagnose the problem on the alarmed NGC by entering the following
command:
Note 1: The NGC must be out-of-service (OOS) and it must be equipped (EQ) in
order to perform diagnostics on it.
normal behavior.
DGN-EQPT::NGC-x:ctag;
System response:
M ctag COMPLD

"NGC-A:PASS-1"
"NGC-A:FAIL-0"


failed iterations, return to step 16, page 29-287.
__ 11. Remove the alarmed NGC, place the module in an anti-static bag, and
put it in a safe place.
steps:
backplane.


backplane?


Page 29-286 7/07 76.5500/29, Rev R


troubleshooting.
approximately three minutes during normal system behavior.
__ 15. After a three minute module download, what is the front panel LED
__ 15.1 If the LEDs remain lit, follow your company's prescribed
__ 15.2 If the LEDs turn off, does the system response generate
an NGC alarm CLR (clear) message for the alarmed
NC?

North America).
__ 16. Retrieve the present state of the alarmed or previously alarmed NC by

Where: x = NC copy that is alarmed or was previously

alarmed (A or B).
System response:
M ctag COMPLD

"NC-A::SIZE=256,EFSIZE=256,ESMSIZE=256,MAP=CMM,ALMPF=99:PST=OOO-NR"
"NGC-A::HWV=81.5512B RH,ALMPF=99,SN=OI0686441,DT=000810:PST=IS-NR"
Hybrid Core Switch:

"NC-A::SIZE=5376,EFSIZE=4480,ESMSIZE=256,MAP=CMM,ALMPF=99:PST=OOS-NR"
"NGC-A::HWV=81.5512B RJ,ALMPF=99,SN=TZ1900605,DT=060129:PST=IS-NR"

"CGC-SH1-10::HWV=81.55112 RA,SN=TN2200009,DT=050808:PST=IS-NR"
76.5500/29, Rev R 7/07 Page 29-287


the NGC associated with the alarmed NC is
page 29-288.

the NGC associated with the alarmed NC is in-service,
normal (IS-NR), what is the present state of the NC?
__ 16.2.1 If the NC is out-of-service, normal

(OOS-NR), go to step 19, page 29-289.
__ 16.2.2 If the NC is abnormal, go to step 3,

page 29-257.
__ 17. Edit the NGC associated with the alarmed NC in-service (IS) by
ED-EQPT::NGC-y:ctag::::IS;
Where: y = NC copy that is alarmed or was previously

alarmed (A or B).
System response:
M ctag COMPLD
__ 18. After a five minute download, retrieve the present state of the alarmed
or previously alarmed NC by entering the following command:
Where: x = NC copy that is alarmed or was previously

alarmed (A or B).
System response:
M ctag COMPLD

"ESM-0001-A::HWV=81.5509 RAF,ALMPF=99,SN=OT0395615,DT=000809:PST=OOS-NR"
Hybrid Core Switch:

"ESM-0001-A::HWV=81.5509 RZ,ALMPF=99,SN=LI0039164,DT=970207:PST=OOS-NR"

"CCSM-SH1-9::HWV=81.55110 RA,TMG=SLV,ALMPF=99,SN=UV0582836,DT=060319:PST=OOS-NR"
"CCSM-SH1-12::HWV=81.55110 RA,TMG=NONE,ALMPF=99,SN=UV0796546,DT=060418:PST=OOO-NR"
Page 29-288 7/07 76.5500/29, Rev R


the NGC associated with the alarmed NC is not
in-service, normal (IS-NR), follow your company's
1.800.443.5555 (North America) or 1.630.798.7070

the NGC associated with the alarmed NC is in-service,
normal (IS-NR), go to substep 18.3, page 29-289.
__ 18.3 Depending on the present state of the alarmed or

previously alarmed NC, choose one of the following:

present state of the alarmed or previously
alarmed NC is in-service, normal
(IS-NR), go to step 21, page 29-290.

alarmed NC is out-of-service, normal

alarmed NC is anything other than the
responses listed above, go to step 3,
page 29-257.
__ 19. Edit the alarmed NC in-service (IS) by entering the following

command:
ED-EQPT::NC-x:ctag::::IS;
System response:
M ctag COMPLD
Note: Module front panel active LED lights within five seconds. This is normal
system behavior.
76.5500/29, Rev R 7/07 Page 29-289

__ 20. Retrieve the present state of the alarmed NC by entering the following
command:
System response:
M ctag COMPLD

"NC-A::SIZE=256,EFSIZE=256,ESMSIZE=256,MAP=CMM,ALMPF=99:PST=IS-NR"
Hybrid Core Switch:


__ 20.1 If the system response for the alarmed NC is not

in-service, normal (IS-NR), go to step 3, page 29-257.



M ctag COMPLD

M ctag COMPLD


message.
__ 21.1.2 If no, go to step 22.
Page 29-290 7/07 76.5500/29, Rev R



End of Procedure
76.5500/29, Rev R 7/07 Page 29-291

Network Timing Distribution Module (NTDM)

3.24 In this section, you will troubleshoot the alarmed Network Timing
Distribution Module (NTDM). You should have completed System Pre-Checks,
3.25 A spare NTDM may be required in order to perform this procedure. Refer
__ 1. Is the SIM-A or SIM-B fault LED on the NTDM lit?
__ 1.1 If yes, go to Synchronization Interface Module (SIM),
page 29-146, to troubleshoot the SIM.
__ 1.2 If no, continue to the next step.
__ 2. If the other NTDM fault light is on, retrieve alarms and conditions by
System response:
M ctag COMPLD

"NTDM-B,EQPT:MN,PAINTGRT,NSA,07-22,09-28-05,NEND,,,\"Faulty timing signal to other
NTDM (possible cable missing)\""
__ 2.1 If the system response generates the message listed

above, go to step 23, page 29-301.
__ 2.2 If the system response does not list the above

message, continue to the next step.
Page 29-292 7/07 76.5500/29, Rev R

__ 3. Retrieve the state of the network timing by entering the following

command:
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
__ 3.1 Verify from the system response that the SIM is

configured for Master on the non-alarmed NC.
__ 4. Switch the master SIM to time off the non-alarmed NC by entering the
following command:
SW-DX-EQPT::SIM-A:ctag;
System response:
M ctag COMPLD

"ACT=SIM-A,STBY=SIM-B"
76.5500/29, Rev R 7/07 Page 29-293

__ 5. Retrieve the state of the network timing by entering the following

command:
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
"SIM-A::TMG=SLV,SYNCMODE=NORM:PST=IS-NR"
"SIM-B::TMG=MSTR,SYNCMODE=NA:PST=IS-NR"
__ 5.1 Verify from the system response that the SIM is now
configured for Master on the non-alarmed NC.
Note: If the location of a module is not certain, the OPR-EQPT-LED command

can be used to locate the module. For more information on executing this
command, go to the Module Location and LED Testing section of Tellabs
Caution:
Failure to resolve internal path integrity errors in the redundant Network
Complex copy prior to a Network Copy switch may result in service interruption.
Page 29-294 7/07 76.5500/29, Rev R


command:

M ctag COMPLD

M ctag COMPLD



Caution:
__ 7. Edit the alarmed NC out-of-service (OOS) by entering the following

command:
System response:
M ctag COMPLD


traffic interruption, go to step 9.

76.5500/29, Rev R 7/07 Page 29-295


command:
System response:
M ctag COMPLD
command:
System response:
M ctag COMPLD

"NC-A::SIZE=256,ALMPF=99:PST=OOS-ANR"

Hybrid Core Switch:



1.800.443.5555 (North America) or 1.630.798.7070
__ 11. Visually verify that the alarmed NTDM is present in the slot.
__ 11.1 If there is an NTDM present in the slot, go to step 12,
page 29-297.
__ 11.2 If there is no NTDM present in the slot, go to step 15,

page 29-298.
Page 29-296 7/07 76.5500/29, Rev R

__ 12. Diagnose the problem on the alarmed NTDM by entering the following
command:
Note 1: The associated NC must be out-of-service (OOS) and it must be

equipped (EQ) in order to perform diagnostics on it.
normal behavior.
DGN-EQPT::NTDM-x:ctag;
System response:
M ctag COMPLD

"NTDM-A:PASS-1"
"NTDM-A:FAIL-0"


Warning:
__ 13. Remove the module, place the module in an anti-static bag, and put it
in a safe place.
76.5500/29, Rev R 7/07 Page 29-297

__ 14. Did removing the module cause a system traffic interruption?
__ 14.2 If yes, did the system recover from the traffic

interruption?
Note: Follow internal policy for determining system traffic recovery.

North America).

steps:
backplane.

backplane?


go to step 16.

troubleshooting.
Note 1: The system generates NC entity alarm CLR messages during certain
instances of troubleshooting.
Note 2: Module front panel LEDs light for approximately five minutes during
normal system behavior.
Page 29-298 7/07 76.5500/29, Rev R

__ 18. After a five minute module download, what is the front panel LED
__ 18.1 If the fault LED turns off, go to step 19.
__ 18.2 If the fault LED remains lit, follow your company's

1.800.443.5555 (North America) or 1.630.798.7070
__ 19. Does the system response generate an NTDM alarm CLR message
for the alarmed NC?
command:
System response:
M ctag COMPLD

Hybrid Core Switch:

__ 20.1 If the system response for the alarmed NC is

__ 20.2 If the system response for the alarmed NC is in-service,

normal (IS-NR), go to step 23, page 29-301.

1.800.443.5555 (North America) or 1.630.798.7070
76.5500/29, Rev R 7/07 Page 29-299


command:
Note: The module front panel active LEDs light on each module of the alarmed
NC during normal system behavior.
System response:
M ctag COMPLD
__ 21.1 Does the system response generate an NC PROTNA

OOS CLR message for the alarmed NC?

North America).
command:
System response:
M ctag COMPLD

Hybrid Core Switch:



page 29-257, for additional troubleshooting.
Page 29-300 7/07 76.5500/29, Rev R

Caution:
Use caution when handling the SYNC timing cables. Disconnecting the cable
from its connector may result in loss of timing to the system.
__ 23. Perform the following steps to verify proper Network Timing

Distribution (NTD) clock cable connections.
For a system with an ESM switch core, go to step 24, page 29-301.
For a system with a Hybrid or CCS switch core, go to step 25,
page 29-304.
__ 24. ESM Switch Core: The NTD clock cables are attached to the
backplane of Center Stage Shelf Copy A (CSS-A) and Center Stage
Shelf Copy B (CSS-B). Refer to Figure 3.6 through Figure 3.8,
page 29-303.
__ 24.1 Verify that the J1 connector on the back of CSS-A is
connected to the J2 connector of CSS-B.
__ 24.2 Verify that the J2 connector on the back of CSS-A is

connected to the J1 connector of CSS-B.
__ 24.3 Did the alarm message clear?
__ 24.3.2 If no, replace the cable, or follow your

company's prescribed procedures for
obtaining technical assistance or call
76.5500/29, Rev R 7/07 Page 29-301

Figure 3.6 NTDM to NTDM Cabling Diagram for a 256 or 1024 System
Center Stage Switch Shelf Center Stage Switch Shelf
Copy A Copy B
J2 J1 J2 J1
GND GND
P12 P11 P10 P9 P8 P7 P6 P12 P11 P10 P9 P8 P7 P6

-48VB -48VB
J2
J1
J2
J1
J11
J11
J5
J5
T T
J12
J12
T T
J6
J6
P13 P13
P14 P14
P3 P3
P15 P15
GND GND
-48VA -48VA
Figure 3.7 NTDM to NTDM Cabling Diagram for a 1536, 2048, or 3072 System
Center Stage Switch Shelf Center Stage Switch Shelf

Copy A Copy B
J2 J1 J2 J1
Page 29-302 7/07 76.5500/29, Rev R

Figure 3.8 NTDM to NTDM 550G CSS Shelf Cabling Diagram for a 1536, 2048, or 3072 Size System
Control Control
CSS1-A CSS1-B
rear view rear view
NTD NTD NTD NTD

OUT IN OUT IN
J2 J1 J2 J1
Cross-timing cable
Part Number 50.2195
Cross-timing cable Part

Number 50.2194
SYN SYN SYN NTD NTD NGC NTD LAN A LAN A LAN B LAN B
Y4
BLK 0
BA
J10 J9 J3 J4 J13 J2 J1 WHT 0 J15 J16 J5 J11 J6 J12 J8 J7

-48 RET -48 RET
B B TIMING J14 - A A
CSS NTDM Connectors
76.5500/29, Rev R 7/07 Page 29-303

__ 25. Hybrid Switch Core: The NTD clock cables are attached to the LAN
Timing Interface Panel. Refer to Figure 3.9, page 29-305.
__ 25.1 Verify that the NTD OUT (J2) connector on the back of
the CSS-A is connected to the IN (J1) connector on
LTIP 1.
__ 25.2 Verify that the NTD IN (J1) connector on the back of the
CSS-A is connected to the OUT (J2) connector on LTIP
1.
the CSS-B is connected to the IN (J1) connector on
LTIP 2.
CSS-B is connected to the OUT (J2) connector on LTIP
2.

Page 29-304 7/07 76.5500/29, Rev R

Figure 3.9 NTD Connections on LAN Timing Interface Panel (Systems with Hybrid Core Switch)
AC-A AC-B
SYNC Out SYNC Out
J34 J34
SYNC Out SYNC Out
J35 J35
SYNC Out SYNC Out SYNC Out SYNC Out
J36 J37 J36 J37
SYNC A (J3) SYNC B (J4) SYNC A (J3) SYNC B (J4)
CSS-A CSS-B
NTD OUT (J2) NTD IN (J1) NTD OUT (J2) NTD IN (J1)
SYNC A (J3)
J2 J1 J2 J1
Out In Out In
SYNC B (J4)
LTIP-1 SYNC B (J4) SYNC A (J3) LTIP-2
76.5500/29, Rev R 7/07 Page 29-305



M ctag COMPLD

M ctag COMPLD

"NTDM-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal signal degradation
detected at ESM line 10 from CSM\":,ISLTD"
__ 26.1.1 If no, go to step 27.

message.


End of Procedure
Page 29-306 7/07 76.5500/29, Rev R

Center Stage Module (CSM)

3.26 In this section, you will troubleshoot the alarmed Center Stage Module
(CSM). You should have completed System Pre-Checks, page 29-256, and been
3.27 A spare CSM may be required in order to perform this procedure. Refer to
__ 1. Retrieve all current alarm conditions by entering the following
command:

M ctag COMPLD

M ctag COMPLD

"CSM-21-A:MN,INT,NSA,03-08,01-09-17,NEND:\"Input SDF failed on CSM line 22 from ESM
(suspect cable)\",ESM-0321-A:,NIMAN"
"ESM-0321-A:MN,INT,NSA,03-08,01-09-17,NEND:\"Input SDF failed on ESM line 22 from CSM

(suspect cable)\",CSM-21-A:,NIMAN"
__ 2. Did the alarm condition indicate "Input SDF failed on CSM line x from
ESM (suspect cable)"?
__ 3. Did the alarm condition indicate either a "Internal signal degradation"

or "Internal signal failure"?
__ 3.2 If yes, are there other alarm conditions posted against

the CSM?

North America).
76.5500/29, Rev R 7/07 Page 29-307

RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

1.800.443.5555 (North America) or 1.630.798.7070

analysis.
Page 29-308 7/07 76.5500/29, Rev R

__ 5. Verify that no port modules are improperly inhibited from either copy
of the network and that they are listening to the preferred copy data
byte by entering both of the following commands:

System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV

76.5500/29, Rev R 7/07 Page 29-309



Example:
System response:
M ctag COMPLD

AL,
BCLK=OK-FORCED"

Page 29-310 7/07 76.5500/29, Rev R

Caution:

command:

M ctag COMPLD

M ctag COMPLD



Caution:

command:
System response:
M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-311




command:
System response:
M ctag COMPLD
command:
System response:
M ctag COMPLD



1.800.443.5555 (North America) or 1.630.798.7070
__ 11. Visually verify that the alarmed CSM is present in the slot.
page 29-313.

page 29-315.
Page 29-312 7/07 76.5500/29, Rev R

__ 12. Diagnose the problem on the alarmed CSM by entering the following
command:
normal behavior.
Note 2: The NGC must be in-service, normal (IS-NR), the CSM must be
equipped (EQ), and the associated network must be out-of-service
(OOS) in order to perform diagnostics on it. The PMs are not listening to
the associated network.
DGN-EQPT::CSM-xx-y:ctag;
Example:
DGN-EQPT::CSM-1-B:ctag;
Where: xxxx = 1 - 36.

y = Alarmed NC (A or B).
System response:
M ctag COMPLD

"CSM-1-B:PASS-1"
"CSM-1-B:FAIL-0"

failed iteration, on-site personnel are required. Go to
step 13.

76.5500/29, Rev R 7/07 Page 29-313

__ 14. Diagnose the problem on the alarmed CSM by entering the following
command:
normal behavior.
DGN-EQPT::CSM-xx-y:ctag;
Example:
DGN-EQPT::CSM-1-B:ctag;
Where: xxxx = 1 - 36.

System response:
M ctag COMPLD

"CSM-1-B:PASS-1"
"CSM-1-B:FAIL-0"

step 15.

__ 15. Remove the CSM, place the module in an anti-static bag, and put it in
a safe place.
Page 29-314 7/07 76.5500/29, Rev R


steps:
backplane.

backplane?


go to step 17.

troubleshooting.
Note 1: The system generates CSM alarm CLR messages during certain
Note 2: The system generates NC CLR PROTNA ANR alarm messages during
certain instances of troubleshooting.
__ 19. After a one minute module download, what is the front panel LED
__ 19.2 If the LEDs turn off, go to step 20.

Where: x = NC copy that is alarmed or was previously in

alarm (A or B).
System response:
M ctag COMPLD

"CSM-01-A::HWV=81.5508 RO,ALMPF=99,SN=OI0830361,DT=000811:PST=NR"
76.5500/29, Rev R 7/07 Page 29-315


the CSM associated with the alarmed NC is abnormal
(ANR), follow your company's prescribed procedures
Technical Assistance at 1.800.443.5555 (North

the CSM associated with the alarmed NC is normal
(NR), what is the present state of the NC?
__ 20.2.1 If the NC is out-of-service normal

__ 20.2.2 If the NC is abnormal go to step 3,

page 29-257.

command:
System response:
M ctag COMPLD
system behavior.
command:
System response:
M ctag COMPLD



Page 29-316 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD


__ 23.1.1 If you are troubleshooting an "Input SDF

failed on CSM line x from ESM (suspect
cable) message," and the alarm does not
clear, or, if the same alarm appears on
the connected ESM, go to End Stage
Module (ESM), page 29-332, to
troubleshoot the ESM.
Note: If troubleshooting the connected module does not clear the "Input SDF
failed on CSM line x" or the "Input SDF failed on ESM line x" alarm
message, follow your company's prescribed procedures for obtaining
__ 23.1.2 For all other alarm messages, go to the

appropriate section of this manual to
troubleshoot that alarm message.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-317

CSM Adapter Module (CAM)

3.28 In this section, you will troubleshoot the alarmed CSM Adapter Module
(CAM). You should have completed System Pre-Checks, page 29-256, and been
3.29 A spare CAM may be required in order to perform this procedure. Refer to
__ 1. Retrieve all alarms and conditions by entering the following command:

M ctag RTRV

M ctag RTRV

"NC-A,EQPT:MN,PROTNA,NSA,08-02,09-19-15,NEND,,,\"Network Complex failed (ANR)- not
available for protection\""
"NIM-SH1-1,EQPT:MN,INT,NSA,08-02,09-19-15,NEND,,,\"SDF48 Loss of Signal detected at
fiber 6\""
"NIM-SH1-1,EQPT:MN,INT,NSA,08-02,09-22-26,NEND,,,\"SDF48 Yellow Frame detected at
fiber 4\""
"NIM-SH1-1,EQPT:MN,INT,NSA,08-02,09-27-32,NEND,,,\"SDF48 mismatch detected at fiber
6\""
"CAM-01-A,EQPT:NR,SENA,NSA,08-02,09-19-19,NEND,,,\"Supporting Entity Not
Avai lable\""
"CAM-02-A,EQPT:MN,INT,NSA,08-02,09-22-14,NEND,,,\"SDF48 Loss of Signal detected at
fiber 2\""
Available\""
Available\""
__ 1.1 If the alarm condition indicates an "SDF48 Loss of

Multiframe" alarm, troubleshoot the timing cables. Refer
to Network Timing Distribution Module (NTDM),
page 29-292, Synchronization Interface Module (SIM),
page 29-146, and Consolidated Core Switch Module
(CCSM), page 29-394.
__ 1.2 If the alarm condition indicates either an "SDF48

mismatch" or "SDF48 Loss of Signal" or "SDF 48 yellow
frame detected," go to paragraph 3.30, page 29-328.
Page 29-318 7/07 76.5500/29, Rev R

__ 1.3 If the system response lists a "Supporting Entity Not

Available Alarm," troubleshoot the NIM or NTDM. Refer
to Network Interface Module (NIM), page 29-434, or
Network Timing Distribution Module (NTDM),
page 29-292.
__ 1.4 If the alarm condition indicates another type of SDF48

alarm, or any other type of alarm, go to step 2.
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

1.800.443.5555 (North America) or 1.630.798.7070

analysis.
76.5500/29, Rev R 7/07 Page 29-319

byte by entering the both of the following commands:

System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV

Page 29-320 7/07 76.5500/29, Rev R



Example:
System response:
M ctag COMPLD

AL,
BCLK=OK-FORCED"

76.5500/29, Rev R 7/07 Page 29-321

Caution:

command:

M ctag COMPLD

M ctag COMPLD



Caution:

command:
System response:
M ctag COMPLD

Page 29-322 7/07 76.5500/29, Rev R




command:
System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD



1.800.443.5555 (North America) or 1.630.798.7070
__ 9. Visually verify that the alarmed CAM is present in the slot.

page 29-324.

page 29-325.
76.5500/29, Rev R 7/07 Page 29-323

__ 10. Diagnose the problem on the alarmed CAM by entering the following
command:
normal behavior.
Note 2: The NGC must be in-service, normal (IS-NR), the CAM must be
DGN-EQPT::CAM-xx-y:ctag;
Example:
DGN-EQPT::CAM-2-B:ctag;
Where: xx = 1 to 36.
System response:
M ctag COMPLD

"CAM-02-B:PASS-1"
"CAM-02-B:FAIL-0"

step 11.

Page 29-324 7/07 76.5500/29, Rev R

__ 12. Diagnose the problem on the alarmed CAM by entering the following
command:
normal behavior.
Note 2: The NGC must be in-service, normal (IS-NR), the CAM must be
DGN-EQPT::CAM-xx-y:ctag;
Example:
DGN-EQPT::CAM-2-B:ctag;
Where: xx = 1 - 36.
System response:
M ctag COMPLD

"CAM-02-B:PASS-1"
"CAM-02-B:FAIL-0"

step 13.

__ 13. Disconnect the SDF48 cables from the front of the CAM. Remove the
CAM, place the module in an anti-static bag, and put it in a safe place.
steps:
backplane.

backplane?


go to step 17.
76.5500/29, Rev R 7/07 Page 29-325


troubleshooting.
__ 16. Insert the module. Reconnect the SDF48 cables.
Note 1: The system generates CAM alarm CLR messages during certain


alarm (A or B).
System response:
M ctag COMPLD

"CAM-01-A::HWV=81.5508 RO,ALMPF=99,SN=OI0830361,DT=000811:PST=NR"

the CAM is abnormal (ANR), follow your company's
1.800.443.5555 (North America) or 1.630.798.7070

the CAM is normal (NR), what is the present state of the
NC?


page 29-257.
Page 29-326 7/07 76.5500/29, Rev R


command:
System response:
M ctag COMPLD
system behavior.
command:
System response:
M ctag COMPLD





M ctag COMPLD

M ctag COMPLD


message.
76.5500/29, Rev R 7/07 Page 29-327



Verifying SDF48 Cables on CAM

3.30 Follow the steps in this section verify proper SDF48 cabling on the CAM.

M ctag COMPLD

M ctag COMPLD

"NIM-SH2-1:MN,INT,NSA,01-01,00-48-02,NEND:\"SDF48 Loss of Signal detected at
fiber 4\",CAM-02-B:,NIMAN"

fiber 4\""
"CAM-03-B:MN,INT,NSA,01-01,00-48-03,NEND:\"SDF48 Loss of Signal detected at fiber

2\",NIM-SH2-1:,NIMAN"
"NC-B:MN,PROTNA,NSA,01-01,00-48-03,NEND:\"Network Complex failed (ANR) - not

available for protection\":,ISLTD"
"CAM-02-B:MAN,SC,01-01,00-48-49,NEND:\"SDF48 mismatch detected at fiber


__ 1.1 If the system response indicates an "SDF48 Loss of

Signal," or "SDF48 Yellow Frame" go to step 2,
page 29-329.
__ 1.2 If the system response indicates an "SDF48 mismatch

detected at fiber X," go to step 18, page 29-331.
Page 29-328 7/07 76.5500/29, Rev R

Troubleshooting SDF48 Loss __ 2. Based on the system response from step 1, locate the CAM and fiber
of Signal Alarms on CAM that is alarmed.
__ 3. Verify that the connections are secure, and that the fiber is not
damaged or broken.

M ctag COMPLD

M ctag COMPLD

"CAM-02-B:CL,INT,NSA,01-01,00-48-38,NEND:\"CLR - SDF48 Loss of Signal detected at
fiber 2\""

fiber 2\""
"NC-B:CL,PROTNA,NSA,01-01,00-53-39,NEND:\"CLR - Network Complex failed (ANR) -

not available for protection\""
__ 4.1 If a clear (CL) message is generated for the alarm, the

procedure is complete.
__ 4.2 If the alarm does not clear go to step 5, page 29-329.
__ 5. Remove the duplex connector from the CAM that is in alarm.

__ 6. Using the proper adapter on a fiber optic meter, attach the cable
marked "receive" to the fiber optic meter.
__ 7. Set the fiber optic meter to 850 nm, and verify the reading is within the
acceptance range. Refer to Table 3.15.
Table 3.15 Acceptable CAM Optical Parameters

Direction Parameter Short Reach
Transmit power, maximum -2.5 dBm

(dBm)
power, minimum -9 dBm

(dBm)
Receive power, maximum -15 dBm

(dBm)
__ 8. If the power levels are within range, go to step 9, page 29-329.

If the power levels are not within range, go to step 11, page 29-330.
__ 9. Clean the duplex connector and connect it to the CAM.
76.5500/29, Rev R 7/07 Page 29-329


__ 10.1 If the CAM fault clears within three minutes, go to step
20, page 29-331.
__ 10.2 If the CAM fault does not clear within three minutes,
repeat step 5, page 29-329 through 8 to check the
transmit cables for the CAM.
__ 10.2.1 If all the transmit fiber levels meet

requirements, go to step 13,
page 29-325, to replace the CAM.
__ 11. Locate the NIM in the CCS shelf, to which the opposite end of the
SDF48 cable is connected. (The NIM is listed in the secondary AID in
the system response from step 1, page 29-328.)
__ 12. Remove the duplex connector from the NIM.
__ 13. Using the proper adapter on a fiber optic meter, attach a short fiber
jumper cable to the duplex connector marked "transmit" on the NIM.
__ 14. Verify the reading is within an acceptable range. Refer to Table 3.16.
Table 3.16 Acceptable NIM Optical Parameters


(dBm)

(dBm)

(dBm)
__ 15. If the reading is within an acceptable range, go to step 16,

page 29-330.
If the reading is not within an acceptable range, go to Network
Interface Module (NIM), page 29-434, to troubleshoot the NIM.
__ 16. Using the proper fiber optic cleaning procedures, clean the NIM duplex
connector and the SDF48 cable.
20, page 29-331.
__ 17.2 If the CAM fault does not clear, replace the SDF48
cable. After three minutes, if the CAM fault still does not
clear, go to Network Interface Module (NIM),
Page 29-330 7/07 76.5500/29, Rev R

Troubleshooting SDF48 __ 18. Based on the system response from step 1, page 29-328, locate the
Mismatch Alarms on CAM CAM that is alarmed and the AID of the module where the SDF48
cable is connected.
Example:

"NIM-SH2-1:MAN,SC,01-01,00-48-21,NEND:\"SDF48 mismatch detected at fiber

__ 19. Correct the SDF48 fiber cabling between the two modules.

M ctag COMPLD

M ctag COMPLD

"CAM-02-B:MAN,CL,01-01,00-53-01,NEND:\"CLR - SDF48 mismatch detected at fiber
2\""
"NIM-SH2-1:MAN,CL,01-01,00-53-01,NEND:\"CLR - SDF48 mismatch detected at fiber

4\""


__ 20.2 If the alarm does not clear go to step 2, page 29-319,

and complete the procedure for troubleshooting the
CAM.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-331

End Stage Module (ESM)

3.31 In this section, you will troubleshoot the alarmed End Stage Module (ESM).
3.32 A spare ESM may be required in order to perform this procedure. Refer to
__ 1. Retrieve all current alarm conditions by entering the following
command:

M ctag COMPLD

M ctag COMPLD

"ESM-0129-A,EQPT:MJ,INT,NSA,01-29,04-26-12,NEND,,,\"Incoming SDF failure from TSI
(possible cable fault)\""
"CSM-21-A:MN,INT,NSA,03-08,01-09-17,NEND:\"Input SDF failed on CSM line 22 from ESM

(suspect cable)\",ESM-0321-A:,NIMAN"

__ 2. Did the alarm condition indicate "Input SDF failed on ESM line x from
CSM (suspect cable)"?
__ 3. Did the alarm condition indicate either an "Internal signal degradation"

or "Internal signal failure"?
__ 3.2 If yes, are there other alarm conditions posted against

the ESM?

North America).
__ 3.2.2 If yes, go to substep 3.3, page 29-333.
Page 29-332 7/07 76.5500/29, Rev R

__ 3.3 If there are alarm conditions posted against the faulted

ESM, does the alarm message reference the CSM or
CAM?
__ 3.3.1 If yes, go to Center Stage Module (CSM),

page 29-307, to troubleshoot the proper
CSM in an attempt to clear the ESM
alarm.
__ 3.3.2 If yes, go to CSM Adapter Module (CAM),

page 29-318, to troubleshoot the proper
CAM in an attempt to clear the ESM
alarm.
__ 3.3.3 If no, proceed to step 4, page 29-333.
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

1.800.443.5555 (North America) or 1.630.798.7070
76.5500/29, Rev R 7/07 Page 29-333


analysis.
Caution:
behavior.
byte by entering both of the following commands:

System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV
Page 29-334 7/07 76.5500/29, Rev R




Example:
System response:
M ctag COMPLD

AL,
BCLK=OK-FORCED"

76.5500/29, Rev R 7/07 Page 29-335

behavior.
Caution:

command:

M ctag COMPLD

M ctag COMPLD


page 29-1027, 7 to resolve the problem before

Page 29-336 7/07 76.5500/29, Rev R

Caution:

command:
System response:
M ctag COMPLD


__ 8.2 If editing the alarmed NC out-of-service did not cause


command:
System response:
M ctag COMPLD
command:
System response:
M ctag COMPLD

Hybrid Core Switch:

76.5500/29, Rev R 7/07 Page 29-337



1.800.443.5555 (North America) or 1.630.798.7070
__ 11. Visually verify that the alarmed ESM (or the ESM associated with the
alarmed TSI) is present in the slot.

page 29-340.
__ 12. Edit the ESM associated with the alarmed NC out-of-service (OOS) by
ED-EQPT::ESM-xxxx-y:ctag::::OOS;
Where: xxxx = SDF number of the module.

Example:
ED-EQPT::ESM-33-A:ctag::::OOS;
System response:
M ctag COMPLD
__ 13. Diagnose the problem on the alarmed ESM by entering the following
command:
Note 1: The module front panel fault LED may remain lit. This is normal behavior.
DGN-EQPT::ESM-xxxx-y:ctag;
Where: xxxx = SDF of the module.

Example:
DGN-EQPT::ESM-33-A:ctag;
System response:
M ctag COMPLD

"ESM-33-A:PASS-1"
"ESM-33-A:FAIL-0"
Page 29-338 7/07 76.5500/29, Rev R


step 14.


__ 15. Diagnose the problem on the alarmed ESM by entering the following
command:
Note 1: The module front panel fault LED may remain lit. This is normal behavior.
Note 2: The NGC must be in-service, normal (IS-NR), the ESM must be
DGN-EQPT::ESM-xxxx-y:ctag;
Example:
DGN-EQPT::ESM-33-A:ctag;

System response:
M ctag COMPLD

"ESM-33-A:PASS-1"
"ESM-33-A:FAIL-0"

step 16.

__ 16. Remove the ESM, place the module in an anti-static bag, and put it in
a safe place.
__ 17. Is the shelf equipped with an ESM (Tellabs part number 81.5509) for
a non-high density port shelf?
76.5500/29, Rev R 7/07 Page 29-339

__ 18. Is the shelf equipped with an ESMU (Tellabs part number 81.5509A)
for a high density port shelf?

Verifying Proper Light Levels on a Non-High Density Port Shelf

__ 1. Verify that the proper fiber shroud lights turn on in the slot for the
removed ESM. Refer to Figure 3.10, page 29-341, through Figure
3.13, page 29-344.
__ 1.1 If the proper fiber shroud lights do turn on, go to step 6,
page 29-347.
__ 1.2 If the proper fiber shroud lights do not turn on, has the
TSI been replaced?
__ 1.2.1 If yes, the fiber cable will need to be

replaced. Follow your company's
Warning:
When inserting an ESM, verify that you are using the correct version of the
module. Inserting the 5509A ESMU in a slot that contains a fiber interface for the
5509 ESM may cause equipment damage.
__ 1.2.2 If no, reseat the ESM and proceed to

Time Slot Interchange Module (TSI),
page 29-506.
Page 29-340 7/07 76.5500/29, Rev R

Figure 3.10 Fiber Shroud Lights for the DS1 TSI
P
I
N
S
Slot Backplane
Fiber Shroud Lights

for ESM
Fiber Shroud
= Lights Are On Under Normal

Operating Conditions
76.5500/29, Rev R 7/07 Page 29-341

Figure 3.11 Fiber Shroud Lights for the Double-Density DS1 TSI
P
I
N
S
slot backplane
fiber shroud lights

for ESM
fiber shroud
= lights are on under normal

operating conditions
Page 29-342 7/07 76.5500/29, Rev R

Figure 3.12 Fiber Shroud Lights for the DS3 and STS1 TSI
P
I
N
S
slot backplane
fiber shroud lights for

ESM
fiber shroud

76.5500/29, Rev R 7/07 Page 29-343

Figure 3.13 Fiber Shroud Lights for the OC-3 or OC-12 TSI
P
I
N
S
slot backplane

ESM
fiber shroud
= lights are on under

normal conditions
Caution:
Do not look directly into the fibers on a high-density port shelf. These lasers are
Class 1 lasers and can cause damage to your eyes.
Page 29-344 7/07 76.5500/29, Rev R

Verifying Proper Light Levels on a High-Density Port Shelf

__ 1. On the back of the ESS, remove the duplex connector attached to slot
A of the first ESMU.
__ 2. Using the proper adapter on the Fiber Optic Meter, attach the cable
marked “receive” to the Fiber Optic Meter. Refer to Figure 3.14,
page 29-346, for the fiber optic adapter location.
__ 3. Set the Fiber Optic Meter for 1310 nm and verify the reading is within
acceptable range. Refer to Table 3.17, page 29-345.
__ 4. If the power is not within range, clean and/or replace the cable before
continuing.
__ 5. Repeat steps 1 through 4 until all 6 fiber optic receive cables have
been verified.
__ 5.1 When all six fiber optic receive cables have been
verified, continue to step 6, page 29-347.
Table 3.17 Acceptable ESMU and TSI96/P Optical Parameters

Short/Intermediate
Direction Parameter Reach Long Reach
Transmit power, maximum -3 n/a

(dBm)
power, minimum -11 n/a

(dBm)
Receive power, maximum -3 n/a

(dBm)
(dBm)
76.5500/29, Rev R 7/07 Page 29-345

Figure 3.14 ESMU Fiber Optic Adapter Location
ESMU fiber optic adapter
slot B
slot A
Page 29-346 7/07 76.5500/29, Rev R


steps:
backplane.


backplane?


go to step 7.

troubleshooting.
Warning:
When inserting an ESM, verify that you are using the correct version of the
module. Inserting the 5509A ESMU in a slot that contains a fiber interface for the
5509 ESM may cause equipment damage.
Note 1: After inserting the module, the module front panel fault LED may remain
lit. This is normal system behavior.
Note 2: The system generates TSI alarm CLR messages during certain
Note 3: The system generates ESM alarm CLR messages during certain
76.5500/29, Rev R 7/07 Page 29-347


Where: x = NC copy that is alarmed or was previously in alarm

(A or B).
System response:
M ctag COMPLD

"NTDM-A::HWV=83.5524A RE,TMG=SIM-A,ALMPF=99,SN=UZ0405251,DT=060210:PST=NR"
"CSSPS-1-A::HWV=8X.5535,ALMPF=99:PST=NR"
"ESM-0001-A::HWV=81.5509 RAF,ALMPF=99,SN=OT0395615,DT=000809:PST=OOS-NR"
"ESM-0033-A::HWV=81.5509 RAF,ALMPF=99,SN=OT0399329,DT=000810:PST=IS-NR"
"ESM-0161-A::HWV=81.5509A RD,ALMPF=99,SN=TZ0080338,DT=050114:PST=IS-NR"
"ESM-0193-A::HWV=81.5509A RD,ALMPF=99,SN=TZ0071168,DT=050214:PST=IS-NR"
"ESM-0225-A::HWV=81.5509A RD,ALMPF=99,SN=UZ0795481,DT=060324:PST=IS-NR"
"ESSPS-01-A::HWV=8X.5535,ALMPF=99:PST=NR"
Hybrid Core Switch:

"NTDM-A::HWV=83.5524A RE,TMG=SIM-B,ALMPF=99,SN=UZ0405257,DT=060210:PST=NR"
"CAM-01-A::HWV=81.55108 RA,ALMPF=99,SN=UV1149976,DT=030208:PST=NR"
"ESM-0001-A::HWV=81.5509 RZ,ALMPF=99,SN=LI0039164,DT=970207:PST=OOS-NR"
"ESM-0033-A::HWV=81.5509 RS,ALMPF=99,SN=GL0251454,DT=930112:PST=IS-NR"
"ESM-0065-A::HWV=81.5509 RY,ALMPF=99,SN=HL1537298,DT=981118:PST=IS-NR"
"ESM-0097-A::HWV=81.5509 RU,ALMPF=99,SN=JL5011854,DT=951017:PST=IS-NR"
Page 29-348 7/07 76.5500/29, Rev R

"CCS-SH1::ALMPF=99:PST=NR"
"CGC-SH1-10::HWV=81.55112 RA,SN=UV0166613,DT=051115:PST=IS-NR"
"CCSM-SH1-9::HWV=81.55110 RA,TMG=SIM-B,ALMPF=99,SN=UV0796550,DT=060418:PST=NR"
"CCSM-SH1-12::HWV=81.55110 RA,TMG=NONE,ALMPF=99,SN=UV0796540,DT=060417:PST=NR"
"NIM-SH1-1::HWV=81.55105 RA,SN=UV0755612,DT=060407,ALMPF=99:PST=IS-NR"
"PAM-SH1-2::HWV=81.55109 RA,SN=UV0755600,DT=060309,ALMPF=99,START=SDF-385,
END=SDF-769:PST=IS-NR"
"PTX-SH1-2-1:TYPE=SDF48:HWV=81.SDF48SR1131S RA,SN=P920FU1,DT=060109,ALMPF=99,
CLEI=T3C5CCDAAA,PTVENDOR=FINISAR CORP.,PTVENDORPN=FTRJ1321P1BTL:PST=IS-NR"
"PTX-SH1-2-2:TYPE=SDF48:HWV=81.SDF48SR1131S RA,SN=P920FPM,DT=060109,ALMPF=99,
CLEI=T3C5CCDAAA,PTVENDOR=FINISAR CORP.,PTVENDORPN=FTRJ1321P1BTL:PST=IS-NR"
"PTX-SH1-2-3:::PST=OOS-ANR-UEQ-UAS"

the ESM associated with the alarmed NC is

the ESM associated with the alarmed NC is in-service,
normal (IS-NR), what is the present state of the NC?


page 29-257.
__ 11. Edit the alarmed ESM in-service (IS) by entering the following
command:
ED-EQPT::ESM-xxxx-y:ctag::::IS;
Example:
ED-EQPT::ESM-33-A:ctag::::IS;
Note 1: System generates NC PROTNA ANR alarm CLR messages during

Note 2: The module front panel LEDs light for approximately five seconds during
Where: xxxx = First SDF on the module.

System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-349



alarm (A or B).
System response:
M ctag COMPLD

Hybrid Core Switch:

"ESM-0001-A::HWV=81.5509 RZ,ALMPF=99,SN=LI0039164,DT=970207:PST=IS-NR"

the ESM associated with the alarmed NC is not
in-service, normal (IS-NR), follow your company's
1.800.443.5555 (North America) or 1.630.798.7070

the ESM associated with the alarmed NC is in-service,
normal (IS-NR), go to substep 12.3.




page 29-257.
Page 29-350 7/07 76.5500/29, Rev R


command:
System response:
M ctag COMPLD
system behavior.
command:
System response:
M ctag COMPLD

Hybrid Core Switch:



76.5500/29, Rev R 7/07 Page 29-351



M ctag COMPLD

M ctag COMPLD

"CSM-21-A:MN,INT,NSA,03-08,01-09-17,NEND:\"Input SDF failed on ESM line 22 from CSM

(suspect cable)\",:ESM-0321-A,NIMAN"
__ 15.1.1 If you are troubleshooting an "Input SDF

failed on ESM line x from CSM (suspect
cable) message," and the alarm does not
clear, or, if the same alarm appears on
the connected CSM, go to Center Stage
Module (CSM), page 29-307, to
troubleshoot the CSM.
Note: If troubleshooting the connected module does not clear the "Input SDF
failed on CSM line x" or the "Input SDF failed on ESM line x" alarm
message, follow your company's prescribed procedures for obtaining
__ 15.1.2 For all other alarm message, go to the

appropriate section of this manual to
__ 15.1.3 If no, go to step 16.


End of Procedure
Page 29-352 7/07 76.5500/29, Rev R

Center Stage Shelf Power Supply Module (CSSPS)

3.33 In this section, you will troubleshoot the alarmed Center Stage Shelf Power
Supply Module (CSSPS). You should have completed System Pre-Checks,
3.34 A spare CSSPS may be required in order to perform this procedure. Refer
command:
System response:
M ctag COMPLD

"CSSPS-2-A::HWV=8X.5535,ALMPF=99:PST=ANR-EQ"
"NC-B::SIZE=256,EFSIZE=256,ESMSIZE=256,MAP=CMM,ALMPF=99:PST=IS-NR"
"CSSPS-1-B::HWV=8X.5535,ALMPF=99:PST=NR"
"CSSPS-2-B::HWV=8X.5535,ALMPF=99:PST=ANR-EQ"
Hybrid Core Switch:

"CSSPS-2-B::HWV=8X.5535,ALMPF=99:PST=ANR-EQ"
__ 1.1 Does the system response verify that the present state
of the non-alarmed CSSPS on the shelf is normal (NR)?
__ 1.1.1 If no, go to Section 11, Checking the

Power to a Shelf, page 29-1105.

the alarmed CSSPS is abnormal, unequipped
(ANR-UEQ), go to step 2, page 29-354.

the alarmed CSSPS is abnormal, equipped (ANR-EQ),
76.5500/29, Rev R 7/07 Page 29-353


CSSPS.
CSSPS, step 3

CSSPS, perform the following:
__ 2.2.1 Verify the breaker panel switch for the

alarmed CSSPS is OFF. Refer to
Table 3.18.
__ 2.2.2 Go to step 7, page 29-355.
Table 3.18 Breaker Locations

NC Breaker NC Shelf
A1 and B1 1
A2 and B2 2
A3 and B3 3
A4 and B4 4
Caution:
When turning OFF the breaker panel switch for an alarmed CSSPS, only turn off
CSSPS is either OFF or ON, perform one of the following:
__ 3.1 If the breaker panel switch for the alarmed CSSPS is
OFF, flip it up to the ON position. Refer to Table 3.18,
page 29-354. Go to step 4, page 29-355.
__ 3.2 If the breaker panel switch for the alarmed CSSPS is

ON, flip it down to the OFF position. Refer to Table 3.18,
page 29-354. Go to step 6, page 29-355.
Page 29-354 7/07 76.5500/29, Rev R

__ 4. After a 30 second module download, does the system generate an

CSSPS alarm CLR (clear) message?
Note: The NC shelves number bottom up with shelf number 1 at the bottom of
Caution:
When turning OFF the breaker panel switch for an alarmed CSSPS, only turn off
__ 5. Flip the breaker panel switch for the alarmed CSSPS to the OFF
position (flip switch down). Refer to Table 3.18, page 29-354.
__ 6. Remove the alarmed CSSPS, place the module in an anti-static bag,
and put it in a safe place.
steps:
backplane.


backplane?


go to step 8.

troubleshooting.
__ 10. Flip the breaker panel switch for the alarmed CSSPS to the ON
position (flip switch up). Refer to Table 3.18, page 29-354.
76.5500/29, Rev R 7/07 Page 29-355

__ 11. After a 30 second module initialization, does the system generate a

CSSPS alarm CLR (clear) message?
__ 11.1 If no, go to Section 11, Checking the Power to a Shelf,
page 29-1105.
command:
System response:
M ctag COMPLD

Hybrid Core Switch:

of the alarmed CSSPS is normal (NR)?

North America).
Page 29-356 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD


message.
__ 13.1.2 If no, go to step 14.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-357

End Stage Shelf Power Supply Module (ESSPS)

3.35 In this section, you will troubleshoot the alarmed End Stage Shelf Power
Supply Module (ESSPS). You should have completed System Pre-Checks,
3.36 A spare ESSPS may be required in order to perform this procedure. Refer
command:
System response:
M ctag COMPLD

"ESSPS-02-A::HWV=8X.5535,ALMPF=99:PST=ANR-EQ"
"ESSPS-01-B::HWV=8X.5535,ALMPF=99:PST=NR"
"ESSPS-02-B::HWV=8X.5535,ALMPF=99:PST=ANR-EQ"
Hybrid Core Switch:

of the non-alarmed ESSPS on the shelf is normal (NR)?
__ 1.1.1 If no, go to Section 11, Checking the

Power to a Shelf, page 29-1105.

the alarmed ESSPS is abnormal, unequipped
(ANR-UEQ), go to step 2, page 29-359.

the alarmed ESSPS is abnormal, equipped (ANR-EQ),
Page 29-358 7/07 76.5500/29, Rev R


ESSPS.
ESSPS, go to step 3.

ESSPS, perform the following:
__ 2.2.1 Verify the breaker panel switch for the

alarmed ESSPS is OFF.
__ 2.2.2 Go to step 7, page 29-360.
Caution:
When turning OFF the breaker panel switch for an alarmed ESSPS, only turn off
ESSPS is either OFF or ON, perform one of the following:
__ 3.1 If the breaker panel switch for the alarmed ESSPS is
OFF, flip it up to the ON position. Go to step 4.
__ 3.2 If the breaker panel switch for the alarmed ESSPS is

ON, flip it down to the OFF position. Go to step 6,
page 29-360.
__ 4. After a 30 second module initialization, does the system generate an

ESSPS alarm CLR (clear) message?
76.5500/29, Rev R 7/07 Page 29-359

Caution:
When turning OFF the breaker panel switch for an alarmed ESSPS, only turn off
__ 5. Flip the breaker panel switch for the alarmed ESSPS to the OFF
position (flip switch down).
__ 6. Remove the alarmed ESSPS, place the module in an anti-static bag,
steps:
backplane.


backplane?


go to step 8.

troubleshooting.
__ 10. Flip the breaker panel switch for the alarmed ESSPS to the ON
position (flip switch up).
__ 11. After a 30 second module initialization, does the system generate a
ESSPS alarm CLR (clear) message?
__ 11.1 If no, go to Section 11, Checking the Power to a Shelf,
page 29-1105.
Page 29-360 7/07 76.5500/29, Rev R

command:
System response:
M ctag COMPLD

Hybrid Core Switch:

of the alarmed ESSPS is normal (NR)?

North America).


M ctag COMPLD

M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-361


message.


End of Procedure
Page 29-362 7/07 76.5500/29, Rev R

Troubleshooting Manual 4. Troubleshooting Consolidated Core Switch Shelf Equipment
4. Troubleshooting Consolidated Core Switch Shelf Equipment
4.01 This section contains procedures to troubleshoot a problem occurring on

the following faulted equipment and modules:
• Consolidated Core Switch Shelf
• Port Aggregation Module (PAM)
• Network Interface Module (NIM)

• Consolidated Core Switch Module (CCSM)
• Consolidated Core Group Controller Module (CGCM)
4.02 When troubleshooting the system common equipment, always check for
system common equipment.
troubleshooting the system common equipment. Refer to Status of the LEDs on a
Warning:
Caution:
the CCS shelf.
76.5500/29, Rev R 7/07 Page 29-363

4. Troubleshooting Consolidated Core Switch Shelf Equipment Troubleshooting Manual

4.07 Figures 4.1 and Figure 4.3, page 29-368, are for reference only. Use
these figures as an aid in troubleshooting the alarmed system common equipment.
4.08 To troubleshoot a faulted module, go to Determining the Meaning of Alarm
Messages, page 29-381.
Port Aggregation Module Figure 4.1 Port Aggregation Module (PAM)

LEDs
PAM
81.55109
Pt-6
Pt-5
Pt-4
Pt-3
Pt-2
Pt-1
Flt SD
Page 29-364 7/07 76.5500/29, Rev R

Table 4.1 Port Aggregation Module LEDs

LED Status Description
power green Both feeds are functional.
amber One feed is dysfunctional or has a

blown fuse.
off The module is not functional.

active green The module is active.
off The module is inactive.
fault red A module failure has occurred.
off No fault exists.
Flt PTs red The module is initializing or one of the

1-8 following problems has occurred: the
pluggable transceiver (PT) is
unequipped, the wrong type of PT is
installed, or a PT failure has occurred.
off The PT is not provisioned.
SDF PTs green The SDF48 between the PAM and the
1-8 TSI96P is operating normally.
amber An SDF48 cable is incorrectly

connected.
red The module is initializing, or an SDF48

alarm has occurred.
off The PT is not connected.
76.5500/29, Rev R 7/07 Page 29-365

Network Interface Module Figure 4.2 Network Interface Module LEDs

LEDs
NIM
81.55105
Pt-
Pt-7
Pt-6
Pt-5
Pt-4
Pt-3
Pt-2
Pt-1
Flt SD
Page 29-366 7/07 76.5500/29, Rev R

Table 4.2 Network Interface Module LEDs

power green Both feeds are functional.
amber One feed is dysfunctional or has a

blown fuse.
off The module is not functional.
fault red A module failure has occurred.
off No fault exists.
Flt PTs red The module is initializing or one of the

1-8 following problems has occurred: the
pluggable transceiver (PT) is
unequipped, the wrong PT is installed,
or a PT failure has occurred.
off The PTs are not provisioned.
SDF PTs green The SDF between the CAM and NIM is
1-8 operating normally.
amber The SDF48 cable has been incorrectly
connected.
red The module is initializing, or an SDF48

alarm has occurred.
off The PT is not provisioned.
76.5500/29, Rev R 7/07 Page 29-367

Consolidated Core Switch Figure 4.3 Consolidated Core Switch Module LEDs
Module LEDs
CCSM
81.55110
power
active
fault
SIM A
SIM B
other
CCSM
NTDM
master
Page 29-368 7/07 76.5500/29, Rev R

Table 4.3 Consolidated Core Switch Module LEDs

power green The module is powered.
amber The module is operative but a fuse has

failed.
fault green A module failure has occurred.
red No fault exists.
SIM A green SIM-A is being used as a timing

reference.
red The timing reference from SIM-A is

unavailable.
off The timing reference from SIM-A is

available.
SIM B green SIM-B is being used as a timing

reference.
red The timing reference from SIM-B is

unavailable.
off The timing reference from SIM-B is

available.
other green The other CCSM copy is being used as a
CCSM timing reference.
red The timing reference from the other

CCSM copy is unavailable.
off The timing reference from the other

CCSM copy is available.
NTDM red Communication between the CCSM and

the NTDM is unavailable.
off Communication between the CCSM and

the NTDM is available.
master green The CCSM is in free run mode.
off The CCSM is not in free run mode.
76.5500/29, Rev R 7/07 Page 29-369

Consolidated Core Group Figure 4.4 Consolidated Core Group Controller Module
Controller Module
CGCM
power
active
fault
Table 4.4 Status of Consolidated Core Group Controller Module

Power ON, Normal, active state.
Active ON,
Fault OFF
All ON a) Fault LED flashes ON/OFF regularly when 1. Active, slow flash = requesting download from main
requesting a download from the Administrative processor.
Complex. 2. CGC downloads information from the database to all
b) Module is in self-diagnostic mode. of the modules on its shelf. The fault LEDs for other
modules may be ON until the CGC is seated and
downloads the information to the modules
Usually a temporary state that occurs during module or

system initialization.
Power ON, a) Faulted or failed module. Fault LED flashes periodically:

Active OFF, b) Bent pin(s) on backplane connector. Active, fast flash = in error state (for example, incorrect
Fault ON cabling from LTIP LAN-A connection to LIP LAN-1
connection).
Power ON, a) Module is in standby (STBY) mode. When CGC is out-of-service (OOS), it will not affect
Active OFF, b) Module is out-of-service (OOS). See Note. other network modules it serves.
Both OFF c) Bent pin(s) on backplane connector.
d) No power, out of slot, breaker OFF. Usually a temporary state.
Power OFF, a) No power, out of slot, breaker OFF. When CGC is out-of-service (OOS), it will not affect
Active OFF, other network modules it serves.
Both OFF
Usually a temporary state.
Page 29-370 7/07 76.5500/29, Rev R

Troubleshooting the Consolidated Core Switch Shelf

4.09 There are many reasons why the NC can become abnormal. By executing
the RTRV-COND-EQPT::NC command, you can get a better idea of where to
begin to solve the problem.
4.10 A list of conditions that may cause an abnormal state in the NC is provided
to assist you in isolating the cause, troubleshooting the problem, and clearing it
from the system:
• ESM, NIM, or PAM becomes OOS-NR by using an edit command.
• ESM becomes OOS-ANR-UEQ from a previously IS-NR state by

editing it OOS and removing it.
• ESM becomes IS-ANR-EQ by detecting an internal fault, or if the
corresponding ESM is unequipped.
• ESM becomes UEQ from a previously equipped state.
• CSM or CAM becomes ANR-EQ by detecting an internal fault.
• CSM or CAM becomes UEQ from a previously equipped state.
• Single NC power supply is turned off at the Breaker/Frame Alarm

Panel.
• Single NC power supply is removed.
• NC power supply is determined as ANR by internal software audits.
• NGC or CGC becomes OOS by using an edit command from an IS-NR

state.
• NGC or CGC becomes ANR by detecting an internal fault.
• NGC or CGC is removed.
• NTDM or CCSM becomes ANR, or is removed.
• TSI becomes ANR by detecting an internal fault.
• TSI becomes OOS from the IS-NR state.
• TSI becomes OOS-ANR-UEQ and does not have the same state as
its redundant TSI on the same port shelf.
• PTx is removed or faulted.
• Port shelf was degrown incorrectly. Proper procedures, described in

Tellabs 5500/5500S Provisioning Manual, 76.5500/23, were not
correctly followed.
76.5500/29, Rev R 7/07 Page 29-371

System Pre-Checks
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */
command:
System response:
M ctag COMPLD


Page 29-372 7/07 76.5500/29, Rev R


command:
System response:
M ctag COMPLD

Hybrid Core Switch:

__ 3.1 If the system response for both NC-A and NC-B is

in-service, abnormal (IS-ANR), go to step 4.
__ 3.2 If the system response verifies that one NC copy, either

A or B, is in-service, abnormal (IS-ANR), go to step 9,
page 29-376.
__ 3.3 If the system response verifies that one or both NCs are
out-of-service, normal (OOS-NR), go to Consolidated
Group Controller Module (CGCM), page 29-450.
__ 4. Retrieve all current alarms and status conditions for the NCs by
RTRV-COND-EQPT::NC-A&&-B:ctag;
System response when no alarms or status conditions exist:

M ctag COMPLD
System response when alarms or status conditions do exist:

M ctag COMPLD
"ESM-993-A,EQPT:NR,INT,NSA,02-18,13-39-06,NEND,,,\"ESM card removed\""
"TSI96-0065-A,:,,,,,,,,\"TSI is OOS\""
Note: If there is a condition posted against more than one module, remember to
troubleshoot the least traffic affecting module first, such as a TSI before an
ESM. Troubleshoot the port shelf first, then the network complex, and then
76.5500/29, Rev R 7/07 Page 29-373

__ 4.1 If you are troubleshooting a Tellabs 5500/5500S system

with high density port shelves (HDPSs), and the system
response shows any of the following alarm messages,
the SDF cabling length from one TSI96 to its network
copy has exceeded the acceptable range. Follow your
Note: The difference between the maximum length among all SDF cables from
one TSI96 to its network copy and the minimum length among all SDF
cables from the other TSI96 to its network copy cannot exceed 100 feet.
The difference between the maximum and minimum lengths of all SDF
cables from one TSI96 to its network copy cannot exceed 50 feet. If either
of these cable length limitations is exceeded, one of the following alarms
will be generated.
\"Excessive length differential between SDF cable(s) to TSI A and SDF cable(s) to
TSI B\"
\"Excessive length differential between SDF cables to TSI Copy A\"

the Center Switch Shelf Power Supply Module (CSSPS)
__ 4.2.1 If yes, go to Center Stage Shelf Power


the End Switch Shelf Power Supply Module (ESSPS)
__ 4.3.1 If yes, go to End Stage Shelf Power

Supply Module (ESSPS), page 29-358.

the Consolidated Group Controller Module (CGCM)
__ 4.4.1 If yes, go to Consolidated Group

Controller Module (CGCM), page 29-450
__ 4.4.2 If no, go to substep 4.5, page 29-375.
Page 29-374 7/07 76.5500/29, Rev R


both NC-A and NC-B?
__ 4.5.1 If alarm messages are posted for both

NC-A and NC-B, go to step 5,
page 29-375.
__ 4.5.2 If alarm messages are posted for either

NC-A or NC-B, go to step 10,
page 29-377.
__ 5. For a system with a Hybrid Core Switch configuration, go to step 6,

page 29-375.
For a system with a Consolidated Core Switch configuration, go to
Caution:
If both NCs are abnormal and the trouble is not isolated to a failed power supply,
1.630.798.7070 (outside North America). Failure to do so may result in a traffic
interruption.
__ 6. Physically check the LAN cables to both NGCs and/or LTIPs, on the
primary NC-A shelf and on the primary NC-B shelf:
__ 6.1 Verify that connectors J5 and J6 on the CSS-A
backplane and connectors J5 and J6 on the CSS-B
backplane are securely connected.
__ 7. Verify that the LAN-A connector on the LTIPs are connected to the
LAN-1 connector on the LIPs.
__ 7.1 If there are any loose LAN cables, securely attach them
to the backplane, or replace any defective cables as
necessary.
__ 8. Does the NC alarm message clear?

__ 8.2 If yes, return to step 3, page 29-373.
76.5500/29, Rev R 7/07 Page 29-375

RTRV-TMG:::ctag;
System response:
M ctag RTRV
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

1.800.443.5555 (North America) or 1.630.798.7070

analysis.
Page 29-376 7/07 76.5500/29, Rev R

Warning:

System response:
M ctag COMPLD

Modules are not improperly inhibited:
M ctag RTRV
or
M ctag RTRV

76.5500/29, Rev R 7/07 Page 29-377



Example:
System response:
M ctag COMPLD

AL,
BCLK=OK-FORCED"

Page 29-378 7/07 76.5500/29, Rev R

__ 11. Retrieve the master/slave status of the SIMs by entering the following
command:
RTRV-TMG:::ctag;
System response:
M ctag RTRV
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

SIM-A
SIM-B

NTDM-A
NTDM-B
CCSM-SH1-9
CCSM-SH2-9
76.5500/29, Rev R 7/07 Page 29-379

__ 11.3 Verify that the non-alarmed NTDM and/or CCSM is

listening to the master SIM. See substep 11.1,
page 29-379.
__ 11.3.1 If the non-alarmed NTDM and CCSM is

listening to the master SIM, continue to
step 12.

North America).


M ctag COMPLD

M ctag COMPLD

"ESM-0129-A,EQPT:MJ,INT,NSA,01-29,04-26-12,NEND,,,\"ESM card removed\""
"PTX-SH1-18-2,EQPT:MN,INT,NSA,07-02,09-25-31,NEND:\"SDF48 Loss of Signal detected at

fiber\",TSI96-4993-A:,NIMAN"
"PTX-SH1-18-2:MN,INT,NSA,07-03,15-57-25,NEND:\"SDF48 Yellow Frame detected at

fiber\",TSI96-4993-A:,NIMAN"
"TSI96-0161-A:MN,INT,NSA,07-03,15-39-57,NEND:\"Internal signal failure detected at

TSI from ESM\",ESM-0225-A:,NIMAN"
__ 12.1 If you recieve an "SDF48 Loss of Signal detected at

fiber message", go to one of the following:
• Checking High-Density SDF Fiber Cable Integrity for TSI96,

page 29-522
• Checking High-Density SDF Fiber Cable Integrity for TSI96P,

page 29-538
__ 12.2 For all other alarm messages, go to Determining the

Meaning of Alarm Messages, page 29-381, to
troubleshoot the faulted module listed in the alarm
message(s) received.
Page 29-380 7/07 76.5500/29, Rev R


4.12 System common equipment alarm messages are listed in the Table 4.5,
• For a Consolidated Core Switch Shelf, go to Table 4.5, page 29-382.
• For a Consolidated Core Switch Module, go to Table 4.6,

page 29-383.
• For a Port Aggregation Module, go to Table 4.7, page 29-385.
• For a Network Interface Module, go to Table 4.8, page 29-388.
• For a Consolidated Group Controller Module, go to Table 4.9,

page 29-392
76.5500/29, Rev R 7/07 Page 29-381

Consolidated Core Switch (CCS) Shelf Alarm Messages

4.14 In order to troubleshoot the alarm message(s) received for a faulted CCS
shelf, use the following table. The first column of the table lists the possible alarm
messages that can be generated for a CCS shelf. The second column lists a
alarm.
Table 4.5 Consolidated Core Switch Shelf Alarm Messages

FANPWR Loss of power or processor The fan tray has experienced a loss of - Loss of power; circuit breakers off or
failure on fan tray power or a processor failure. blown (B/FAP or F/FAP).
- Faulty or failed fan tray module.
Go to Fan Tray Module, page 29-843.
FEED Loss of power feed A to shelf There is no power on feed A to the CCS Power has been turned off, or feeds have
shelf. been disconnected.
Go to Checking the Power to a Shelf,

page 29-1105.
FEED Loss of power feed B to shelf There is no power on feed B to the CCS Power has been turned off, or feeds have
shelf. been disconnected.

page 29-1105.
INT Missing module - potential air A module is missing from the CCS shelf. In order to maintain proper air flow, insert
flow problem a filler module into any unused slots in
the CCS shelf.
MAN Active module(s) are being used An active module has been inserted into There is a module with active circuitry
as filler module(s) a slot designated for a filler module. being used as a filler. Replace the active
module with the proper filler module for
that slot.
MAN Cable from Plug P31 to LTIP not The SDF48 cable bundle that connects Follow your company's prescribed
detected (for CCS Shelf to LTIP the CCS shelf to the LTIP is procedures for obtaining technical
cable) disconnected or broken. assistance or call Tellabs Technical
North America).
MAN SDF48 Cable Bundle from An SDF48 cable bundle that connects Follow your company's prescribed
<plug# for eqpt_aid> to <plug# the two copies of the CCS shelf is procedures for obtaining technical
for aiddet> not detected, where disconnected or broken. assistance or call Tellabs Technical
<plug# for eqpt_aid> and <plug# Assistance at 1.800.443.5555 (North
for aiddet> are in the range America) or 1.630.798.7070 (outside
P23...P28. See REPTÂLM for North America).
<eqpt_aid> and <aiddet>
definition.
Page 29-382 7/07 76.5500/29, Rev R

Consolidated Core Switch Module (CCSM) Alarm Messages

CCSM, use the following table. The first column of the table lists the possible alarm
messages that can be generated for a CCSM. The second column lists a
alarm.
Table 4.6 Consolidated Core Switch Module Alarm Messages

FEED Loss of power feed A to module There is no power on feed A to the Power has been turned off, or feeds
CCSM. have been disconnected.

page 29-1105.
FEED Loss of power feed B to module There is no power on feed B to the Power has been turned off, or feeds
CCSM. have been disconnected.

page 29-1105.
INT EEPROM Failure A failure to read the EEPROM Reporting CCSM has failed: it has
information or a failure to store this corrupted EEPROM data.
occurred. Go to Consolidated Core Switch Module
INT Failed diagnostics The CCSM has failed one of its internal Failed one or more internal diagnostic
TL1 DGN command.
INT Internal failure detected Reporting CCSM is detecting one of One of the following is the likely cause:
several possible errors, but cannot - Download requested while CCSM is in
- CCSM cannot communicate with its
CGC.
- CCSM experiencing internal transmit or
receive error.

INT Internal SDF48 LOF between Loss of frame has been detected At least one CCSM in the shelf is faulty.
CCSMs on shelf between the two CCSMs in the shelf Go to Consolidated Core Switch Module
INT Internal SDF48 LOF on CCSM Loss of frame has been detected on the The CCSM is faulty.
CCSM.
INT Internal SDF48 LOMF between Loss of multi-frame has been detected At least one CCSM in the shelf is faulty.
CCSMs on shelf between the two CCSMs in the shelf
INT Internal SDF48 LOMF on CCSM Loss of multi-frame has been detected The CCSM is faulty.
on the CCSM.
76.5500/29, Rev R 7/07 Page 29-383

Table 4.6 Consolidated Core Switch Module Alarm Messages (Continued)

INT Internal SDF48 Parity Error SDF48 parity errors were detected At least one CCSM in the shelf is faulty.
between CCSMs on shelf between the two CCSMs on the shelf.
INT Internal SDF48 Parity Error on SDF48 parity errors were detected on The CCSM is faulty.
CCSM the specified CCSM.
INT Module not compatible with The CGC is not supported by the Module revision level is either lower or

INT Module removed Active CCG has detected the absence Module has been removed from its slot,
of a CCSM. or it has not responded to

PAINTGRT Faulty timing signal to NTDM The CCSM cannot receive timing from Verify that the LTIP cables are correctly
(possible cable missing) the NTDM—possibly due to a missing connected.
cable.
Go to step 18, page 29-402.
PAINTGRT Faulty timing signal to other The CCSM cannot receive timing from Follow your company’s prescribed
CCSM (possible cable missing) the other CCSM—possibly due to a procedures for obtaining technical
missing cable. assistance or call Tellabs Technical
North America).
Use RTRV-REVTBL command to view Go to Consolidated Core Switch Module
the system database of valid module (CCSM), page 29-394.
Manual, 76.5500/13.
SENA Supporting Entity Not Available The active AC is detecting that the The system has detected a problem with
supporting module is not in a normal the supporting module. Possible causes:
state. - The module supporting the CCSM is in
the process of resetting.
- Supporting module has been physically
unseated from the backplane.
- There is a problem with the supporting
module.

Page 29-384 7/07 76.5500/29, Rev R

Port Aggregation Module (PAM) Alarm Messages

4.16 In order to troubleshoot the alarm message(s) received for a faulted PAM,
messages that can be generated for a PAM. The second column lists a description
of the alarm message. The third column gives a probable cause for the alarm.
Table 4.7 Port Aggregation Module Alarm Messages

CONTCOM Loss of LAN communication from There is no LAN communication from The communications channel between
PAM to TSI 1 PAM to TSI 1. PAM and TSI 1 is broken.
Go to Port Aggregation Module (PAM),

page 29-405.

page 29-405.
PAM to TSI 3 PAM to TSI 3 PAM and TSI 3 is broken.

page 29-405.

page 29-405.
FEED Loss of power feed A to module There is no power on feed A to the CCS Power has been turned off, or feeds
shelf. have been disconnected.

page 29-1105.
FEED Loss of power feed B to module There is no power on feed B to the CCS Power has been turned off, or feeds

page 29-1105.
INT EEPROM Failure A failure to read the EEPROM Reporting PAM has failed: it has
occurred. Go to Port Aggregation Module (PAM),
page 29-405.
INT Failed diagnostics The PAM has failed one of its internal Failed one or more internal diagnostic
TL1 DGN command.
page 29-405.
76.5500/29, Rev R 7/07 Page 29-385

Table 4.7 Port Aggregation Module Alarm Messages (Continued)

INT Internal failure detected Reporting PAM is detecting one of One of the following is the likely cause:
several possible errors, but cannot - Download requested while PAM is in
- PAM cannot communicate with its
CGC.
- PAM experiencing internal transmit or
receive error.

page 29-405.
INT Internal SDF48 LOF from CCSM LOF has been detected from the PAM to Either the PAM or CCSM is faulty.
to PAM CCSM.
page 29-405.
INT Internal SDF48 LOMF from LOF has been detected from the PAM to Either the PAM or CCSM is faulty.
CCSM to PAM CCSM.
page 29-405.
INT Internal SDF48 LOF from PAM to LOF has been detected from the PAM to Either the PAM or CCSM is faulty.
CCSM CCSM.
page 29-405.
INT Internal SDF48 LOMF from PAM LOMF has been detected from the PAM Either the PAM or CCSM is faulty.
to CCSM to CCSM.
page 29-405.
INT Internal SDF48 parity error from SDF48 parity errors were detected from Either PAM or CCSM is faulty.
CCSM to PAM the CCSM to PAM.
page 29-405.
INT Internal SDF48 parity error from SDF48 parity errors were detected from Either PAM or CCSM is faulty.
PAM to CCSM the PAM to the CCSM.
page 29-405.
INT Module not compatible with The PAM is not supported by the Module revision level is either lower or

page 29-405.
INT Module removed Active CGC has detected the absence of Module has been removed from its slot,
a PAM. or it has not responded to

page 29-405.
Page 29-386 7/07 76.5500/29, Rev R

Table 4.7 Port Aggregation Module Alarm Messages (Continued)

RTRV-REVTBL command to view the Go to Port Aggregation Module (PAM),
system database of valid module page 29-405.
Manual, 76.5500/13.
supporting module is not in a normal the supporting module. Possible causes:
state. - The module supporting the PAM is in
module.

page 29-405.
76.5500/29, Rev R 7/07 Page 29-387

Network Interface Module (NIM) Alarm Messages

4.17 In order to troubleshoot the alarm message(s) received for a faulted NIM,
messages that can be generated for a NIM. The second column lists a description
of the alarm message, and the third column gives a probable cause for the alarm.
Table 4.8 Network Interface Module (NIM) Alarm Messages

FEED Loss of power feed A to module There is no power on feed A to the CCS Power has been turned off, or feeds

page 29-1105.
FEED Loss of power feed B to module There is no power on feed B to the CCS Power has been turned off, or feeds

page 29-1105.
INT Cable or Internal failure - PT at port Either the SDF48 cable or the PT is There is a problem with the SDF48
X, where X is the port number. defected. cable, such as a dirty or broken cable, or
there is an internal failure with the PT.
Go to Pluggable Transceiver (PT),

page 29-835.
INT EEPROM Failure A failure to read the EEPROM Reporting NIM has failed: it has
occurred. Go to Network Interface Module (NIM),
page 29-434.
INT Failed diagnostics The NIM has failed one of its internal Failed one or more internal diagnostic
TL1 DGN command.
page 29-434.
INT Internal failure detected Reporting NIM is detecting one of One of the following is the likely cause:
several possible errors, but cannot - Download requested while NIM is in
- NIM cannot communicate with its
CGC.
- NIM experiencing internal transmit or
receive error.

page 29-434.
INT Internal failure detected - PT at port The Pluggable Transceiver in port X is Replace the PT.
X, where X is the port number. faulted.
Refer to Pluggable Transceiver (PT),
page 29-835.
Page 29-388 7/07 76.5500/29, Rev R

Table 4.8 Network Interface Module (NIM) Alarm Messages (Continued)

INT Internal SDF48 LOF from CCSM to LOF has been detected from the CCSM Either the CCSM or NIM is faulty.
NIM to the NIM.
the CCSM.

INT Internal SDF48 LOF from NIM to LOF has been detected from the NIM to Either the CCSM or NIM is faulty.
CCSM the CCSM.
the CCSM.

INT Internal SDF48 LOMF from CCSM Loss of Multi-frame has been detected Either the CCSM or NIM is faulty.
to NIM from the CCSM to the NIM.
the CCSM.

INT Internal SDF48 LOMF from NIM to Loss of Multi-frame has been detected Either the CCSM or NIM is faulty.
CCSM from the NIM to the CCSM.
the CCSM.

INT Internal SDF48 Parity Error from SDF48 parity errors were detected from Either CCSM or NIM is faulty.
CCSM to NIM the CCSM to the NIM.
the CCSM.

INT Internal SDF48 Parity Error from SDF48 parity errors were detected from Either CCSM or NIM is faulty.
NIM to CCSM the NIM to the CCSM.
the CCSM.

INT Module not compatible with The CGC is not supported by the Module revision level is either lower or

page 29-434.
76.5500/29, Rev R 7/07 Page 29-389


INT Module removed Active CGC has detected the absence Module has been removed from its slot,
of a port module. or it has not responded to

page 29-434.
INT PT Module inconsistent with The PT inserted in the port is not Verify the correct version of the PT.
assigned type - PT at port X, where designed to be used with the NIM. Refer to Tellabs 5500/5500S Software
X is the port number. Release Document, 76.5500/16.
Replace the PT.

page 29-835.
INT PT Module removed - PT at port X, PT at port X of the NIM has been Reseat or replace the PT.
where X is the port number. removed.
page 29-835.
INT SDF48 Loss of Frame detected at The NIM has detected an LOF on the One or more of the following has
fiber X, where X is the fiber specified SDF48 cable. occurred:
number. - NIM is losing framing.
damaged.

INT SDF48 Loss of Multi-Frame The NIM has detected two consecutive Either the quality of the signal received
detected at fiber X, where X is the H4 values that do not agree with any from the CAM is poor, or the NIM has
fiber number. part of the multiframe sequence, and it failed.
has declared a loss of multiframe
(LOMF) defect. Go to Network Interface Module (NIM),
page 29-434.
INT SDF48 Loss of Signal detected at A Loss of Signal has been declared at a Disconnected or broken cable.
fiber X, where X is the fiber port on the NIM.
number. Go to Network Interface Module (NIM),
fiber.
INT SDF48 mismatch detected at fiber An SDF48 cable is connected to the Either the SDF48 cables for port 1
X, where X is the mismatched fiber wrong port. through port 8, or Copy A and Copy B,
(X = 1 to 8). are reversed.

page 29-434.
INT SDF48 Parity Error detected at SDF parity errors were detected at the Either the NIM or CAM is faulty.
fiber X, where X is the fiber port.
number. Go to CSM Adapter Module (CAM),
page 29-318, to troubleshoot the CAM.

Page 29-390 7/07 76.5500/29, Rev R


INT SDF48 Yellow Frame at fiber X, The NIM has declared a Yellow Frame Either the NIM or CAM is faulty.
where X is the fiber number. on a fiber that is connected to the
specified port. Go to CSM Adapter Module (CAM),

INT SDF48 Yellow Multi-Frame at fiber The NIM has declared a Yellow The NIM is faulty.
X, where X is the fiber number. Multi-Frame on the fiber that is
connected to the specified port. Go to Network Interface Module (NIM),
Use RTRV-REVTBL command to view Go to Network Interface Module (NIM),
Manual, 76.5500/13.
REVLVL Module rev level does not meet The revision of the NIM is incompatible Refer to Tellabs 5500 Software Release
minimum due to PT port X, where with the PT in the module. Document, 76.5500/16, for the correct
X is the port number. version of the NIM.

page 29-434.
supporting module is not in a normal the supporting module. Possible
state. causes:
- The module supporting the NIM is in
- Supporting module has been
physically unseated from the backplane.
module.

page 29-434.
76.5500/29, Rev R 7/07 Page 29-391

Consolidated Group Controller Module (CGCM) Alarm Messages

CGCM, use the following table. The first column of the table lists the possible alarm
messages that can be generated for an CGCM.The second column lists a
alarm.
Table 4.9 Consolidated Group Controller Module (CGC) Alarm Messages

CONTCOM CGC to CGC LAN Comm Lost There is no LAN communication One or more of the following has occurred:
between SH1 and SH2 between the CGCM on SH1 and the • CGCM is resetting (usually a transient
CGCM on SH2. condition)
• CGCM is not properly seated.
• Broken, loose, or disconnected
micro-coax cable between CCS1 and
CCS2.
Go to Consolidated Group Controller
Module (CGCM), page 29-450.
CONTCOM CGC to LSM LAN Comm Lost at There is no LAN communication One or more of the following has occurred:
LAN A port (missing cable?) between the CGCM and the LSM at • LSM is not properly seated.
LAN port A.
• Loose or disconnected LAN cable
between LTIP LAN A port and LIP
LAN 1 port.
Go to Troubleshooting Control LAN in

System with Hybrid or CCS Switch Core,
page 29-238.
CONTCOM Loss of LAN communication from There is no LAN communication One or more of the following has occurred
CGC to PAM-x (where x is in the between the CGCM and a PAM in a • CGC and PAMx lost communication.
range of 1-8, and 13, 14, 17, 18) specified slot.
• PAM is possibly resetting (usually a
transient condition).
• PAM is not properly seated.
Perform procedures in Consolidated
Group Controller Module (CGCM),
page 29-450, and Port Aggregation
Module (PAM), page 29-405.
If alarm does not clear, follow your

FEED Loss of power feed A to module There is no power on feed A to the Power has been turned off, or feeds have
CGCM. been disconnected.

page 29-1105.
FEED Loss of power feed B to module There is no power on feed B to the Power has been turned off, or feeds have
CGCM. been disconnected.

page 29-1105.
Page 29-392 7/07 76.5500/29, Rev R

Table 4.9 Consolidated Group Controller Module (CGC) Alarm Messages (Continued)
INT EEPROM failure When the CGCM initializes, it polls Either the EEPROM data is corrupt or
the AP to determine whether or not it hardware has failed.
should initialize as the active or
standby CGCM. As part of this Go to Consolidated Group Controller
process, the EEPROM of the CGCMs Module (CGCM), page 29-450.
are read and validated for size,
checksum and parity. This alarm is
generated if the software fails to read
the EEPROMs or if a failure occurs
during the validation of the
EEPROMs.
INT Failed diagnostics The CGCM has failed one of its Failed one or more internal diagnostic
internal diagnostics either on tests. Failed or faulted module.
power-up or by TL1 DGN command.
INT Module not compatible with Reporting module is not supported by Module revision level is either lower or
existing software the software version currently higher than the levels supported by the
operating on the system. current software version.

INT Module Removed The AC has detected the absence of One or more of the following has occurred:
the CGCM module. - CGCM module is defective.
- CGCM module has been removed from
its slot.
- IPC link to CGCM module has failed.
- Backplane pin damage in the CGCM slot.

MAN LAN and Timing Interface Panel A cable on the LTIP has been A cable has been connected to the wrong
(LTIP) miscabled on port <xx>, connected to the wrong connector. connector.
where <xx> = J1 - J4 | J11-J14
which corresponds to the labels on Go to Consolidated Group Controller
the LAN and Timing Interface Module (CGCM), page 29-450.
Panel (LTIP)
database. Use RTRV-REVTBL Go to Consolidated Group Controller
command to view the system Module (CGCM), page 29-450.
76.5500/13.
76.5500/29, Rev R 7/07 Page 29-393

Consolidated Core Switch Module (CCSM)

4.19 In this section, you will troubleshoot the alarmed Consolidate Core Switch
Module (CCSM). You should have completed System Pre-Checks, page 29-372,
and been directed to this section from an alarm message table.
4.20 A spare CCSM may be required in order to perform this procedure. Refer
Caution:
the CCS shelf.
__ 1. Is the SIM-A or SIM-B fault LED on the CCSM lit?

__ 1.1 If yes, go to Synchronization Interface Module (SIM),
page 29-146, to troubleshoot the SIM.
__ 1.3 Retrieve all alarms and conditions by entering the

following command:
RTRV-COND-EQPT:::ctag;
System response:
M ctag COMPLD

Internal failure detected
__ 1.4 If the following alarm message is received, go to

Checking the Power to a Shelf, page 29-1105.
Loss of power feed A to module
Loss of power feed B to module
__ 1.5 If the following alarm message is received, go to step

18, page 29-402.
Faulty timing signal to NTDM (possible cable

missing)
Page 29-394 7/07 76.5500/29, Rev R

__ 1.6 If the following alarm messages are received, follow

your company's prescribed procedures for obtaining
Signal to CCSM on SH1 lost (possible cable missing)
Signal to CCSM on SH2 lost (possible cable missing)
SDF48 Cable Bundle from <plug# for eqpt_aid> to

<plug# for aiddet> not detected, where <plug# for
eqpt_aid> and <plug# for aiddet> are in the range
P23..P28.
Faulty timing signal to other CCSM (possible cable

missing)
__ 1.7 If any other type of alarm message is received, go to

Caution:

command:

M ctag COMPLD

M ctag COMPLD


page 29-1027, to resolve the problem before continuing
with this procedure.

76.5500/29, Rev R 7/07 Page 29-395

Caution:

command:
System response:
M ctag COMPLD




command:
System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD

Hybrid Core Switch:

Page 29-396 7/07 76.5500/29, Rev R



1.800.443.5555 (North America) or 1.630.798.7070
__ 7. Visually verify that the alarmed CCSM is present in the slot.

__ 7.1 If there is a CCSM present in the slot, go to step 8,
page 29-397.
__ 7.2 If there is no CCSM present in the slot, go to step 11,

page 29-399.
__ 8. Diagnose the problem on the alarmed CCSM by entering the following

command:
Note 1: The associated NC must be out-of-service (OOS) and it must be

equipped (EQ) in order to perform diagnostics on it.
normal behavior.
DGN-EQPT::CCSM-SHx-y:ctag;
Example:
DGN-EQPT::CCSM-SH1-12:ctag;
Where: x = Shelf identifier (1 or 2).

y = Slot number (9 or 12).
System response when the diagnostic routine is successful:

M ctag COMPLD

"CCSM-SH1-12:PASS-1"
"CCSM-SH1-12:FAIL-0"
76.5500/29, Rev R 7/07 Page 29-397

System response when the diagnostic routine detects a failure:

M ctag COMPLD

"CCSM-SH1-12:PASS-0"
"CCSM-SH1-12:FAIL-1,,,dgn_code"
/* SIM-A reference not detected */
Note: The warning references could include any or all

of these:
- /* SIM-A reference not detected */
- /* SIM-B reference not detected */
- /* Other CCSM reference not detected */
Where:

Warning:
__ 9. Remove the module, place the module in an anti-static bag, and put it
in a safe place.
Page 29-398 7/07 76.5500/29, Rev R

__ 10. Did removing the module cause a system traffic interruption?
__ 10.2 If yes, did the system recover from the traffic

interruption?
Note: Follow internal policy for determining system traffic recovery.

North America).

steps:
backplane.

backplane?


go to step 12.

troubleshooting.
Note 1: The system generates NC entity alarm CLR messages during certain
Note 2: Module front panel LEDs light for approximately five minutes during
76.5500/29, Rev R 7/07 Page 29-399

__ 14. After a five minute module download, what is the front panel LED
__ 14.2 If the fault LED remains lit, follow your company's

1.800.443.5555 (North America) or 1.630.798.7070
command:
System response:
M ctag COMPLD

Hybrid Core Switch:

__ 15.1 If the system response for the alarmed NC is



1.800.443.5555 (North America) or 1.630.798.7070

command:
Note: The module front panel active LEDs light on each module of the alarmed
NC during normal system behavior.
System response:
M ctag COMPLD
Page 29-400 7/07 76.5500/29, Rev R

__ 16.1 Does the system response generate an NC PROTNA

OOS CLR message for the alarmed NC?

North America).
command:
System response:
M ctag COMPLD

Hybrid Core Switch:


__ 17.2 For all other system response, return to step 2,

page 29-395, for additional troubleshooting.
76.5500/29, Rev R 7/07 Page 29-401

Caution:
Use caution when handling the SYNC timing cables. Disconnecting the cable
from its connector may result in loss of timing to the system.
__ 18. The NTD clock cables are attached to the LAN Timing Interface Panel.
Refer to Figure 4.5, page 29-403.
the CSS-A is connected to the IN (J1) connector on
LTIP 1.
CSS-A is connected to the OUT (J2) connector on LTIP
1.
the CSS-B is connected to the IN (J1) connector on
LTIP 2.
CSS-B is connected to the OUT (J2) connector on LTIP
2.

Page 29-402 7/07 76.5500/29, Rev R

Figure 4.5 Clock Connections on LAN Timing Interface Panel (Systems with Hybrid Core Switch)
AC-A AC-B
SYNC Out SYNC Out
J34 J34
SYNC Out SYNC Out
J35 J35
SYNC Out SYNC Out SYNC Out SYNC Out
J36 J37 J36 J37
SYNC A (J3) SYNC B (J4) SYNC A (J3) SYNC B (J4)
CSS-A CSS-B
NTD OUT (J2) NTD IN (J1) NTD OUT (J2) NTD IN (J1)
SYNC A (J3)
J2 J1 J2 J1
Out In Out In
SYNC B (J4)
LTIP-1 SYNC B (J4) SYNC A (J3) LTIP-2
76.5500/29, Rev R 7/07 Page 29-403



M ctag COMPLD

M ctag COMPLD

"NTDM-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal signal degradation detected
at ESM line 10 from CSM\":,ISLTD"
__ 19.1.1 If no, go to step 20.

message.


End of Procedure
Page 29-404 7/07 76.5500/29, Rev R

Port Aggregation Module (PAM)

4.21 In this section, you will troubleshoot the alarmed Port Aggregation Module
(PAM). You should have completed System Pre-Checks, page 29-372, and been
4.22 A spare PAM may be required in order to perform this procedure. Refer to

M ctag COMPLD

M ctag COMPLD

"PAM-SH1-13,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Failed diagnostic \":,ISLTD"

Checking the Power to a Shelf, page 29-1105.
Loss of power feed A to module
Loss of power feed B to module
__ 1.2 For all other system responses, proceed to step 2,

page 29-405.
Caution:
the CCS shelf.
__ 2. Retrieve the present state of the NCs by entering the following

command:
System response:
M ctag RTRV
76.5500/29, Rev R 7/07 Page 29-405

Hybrid Core Switch:

END=SDF-769:PST=IS-ANR"

END=SDF-2689:PST=OOS-ANR"
__ 3. Based on the alarm condition of the NCs, proceed accordingly.

__ 3.1 If both NCs are in-service, abnormal (IS-ANR), go to
__ 3.2 If only the NC associated with the alarmed PAM is

page 29-406.
Note: The active LEDs of all the modules on the abnormal (ANR) CCS shelf will
turn off during normal system behavior.
Caution:

command:

M ctag COMPLD

M ctag COMPLD

Page 29-406 7/07 76.5500/29, Rev R



Caution:

command:
Where: x = A or B, whichever NC copy is in alarm.
System response:
M ctag COMPLD

__ 5.1 Choose one of the following:
__ 5.1.1 If editing the alarmed NC out-of-service

caused traffic interruption, and the
system does not recover from the traffic
interruption, go to step 6.
__ 5.1.2 If editing the alarmed NC out-of-service

does not cause traffic interruption, go to

command:
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-407


command:
System response:
M ctag COMPLD

Hybrid Core Switch:
"NC-x::SIZE=5376,EFSIZE=4480,ESMSIZE=256,MAP=CMM,ALMPF=99:PST=OOS-ANR"


page 29-408.

1.800.443.5555 (North America) or 1.630.798.7070
__ 8. Retrieve the present state of the PAMs by entering the following

command:
RTRV-EQPT::PAM-SHx-y&&-y:ctag;
Where: x = Shelf number (1 or 2).

y = Slot number of the PAM in the range (1 - 8, 13, 14,
17, and 18).
System response:
M ctag COMPLD

"PAM-SH1-13::HWV=81.55109RA,ALMPF=99,SN=PA0210372,DT=050507,START=SDF-3073,END=SDF-3
456:PST=IS-NR"
456:PST=OOS-NR"
456:PST=IS-NR"
__ 8.1 Repeat step 8 for the PAM in the other switch network.
Page 29-408 7/07 76.5500/29, Rev R


the non-alarmed PAMs are in-service, normal (IS-NR),
choose one of the following options:

alarmed PAM is out-of-service, normal
__ 8.2.2 If the alarmed PAM is out-of-service

abnormal (OOS-ANR), go to step 2,
page 29-405.

alarmed PAM is in-service abnormal
(IS-ANR), go to step 11, page 29-410.

a non-alarmed PAM is not in-service, normal (IS-NR),
__ 9. Edit the alarmed PAM in-service (IS) by entering the following

command:
ED-EQPT::PAM-SHx-y:ctag::::IS;
Example:
ED-EQPT::PAM-SH1-8:ctag::::IS;

17, and 18).
System response:
M ctag COMPLD
__ 10. Retrieve the present state of the alarmed PAM by entering the
following command:
RTRV-EQPT::PAM-SHx-y:ctag;
Example:
RTRV-EQPT::PAM-SH1-8:ctag;

17, and 18).
System response:
M ctag COMPLD

56:PST=IS-NR"
76.5500/29, Rev R 7/07 Page 29-409


the alarmed PAM is anything except in-service, normal

the alarmed PAM is in-service, normal (IS-NR), go to
step 71, page 29-431.
__ 11. Edit the alarmed PAM out-of-service (OOS) by entering the following
command:
ED-EQPT::PAM-SHx-y:ctag:::MODE=FRCD:OOS;
Example:
ED-EQPT::PAM-SH1-8:ctag:::MODE=FRCD:OOS;

17, and 18).
M ctag COMPLD

System response:
M ctag COMPLD

following command:
Example:

17, and 18).
System response:
M ctag COMPLD

56:PST=OOS-NR"
Page 29-410 7/07 76.5500/29, Rev R

__ 12.1 Verify that the alarmed PAM is out-of-service (OOS).
__ 13. Visually verify that the alarmed PAM is present in the slot.
page 29-411.

page 29-429.
__ 14. Diagnose the problem on the alarmed PAM by entering the following
command:
Note: Module front panel LEDs light for approximately 10 seconds. This is
normal behavior.
DGN-EQPT::PAM-SHx-y:ctag::,ITER=3;
Example:
DGN-EQPT::PAM-SH1-8:ctag::,ITER=3;

17, and 18).
System response:
M ctag COMPLD

"PAM-SH1-8:PASS-3"
"PAM-SH1-8:FAIL-0"
__ 14.1 If the system response shows any failed iterations, go to

step 15.

76.5500/29, Rev R 7/07 Page 29-411

__ 16. Diagnose the problem on the alarmed PAM by entering the following
command:
normal behavior.
DGN-EQPT::PAM-SHx-y:ctag;
Example:
DGN-EQPT::PAM-SH1-8:ctag;

17, and 18).
System response:
M ctag COMPLD

"PAM-SH1-8:PASS-1"
"PAM-SH1-8:FAIL-0"

failed iteration, go to step 17, page 29-412.


__ 17.1 If you are troubleshooting a loss of LAN communication
message similar to the following examples, go to
Checking PAM to TSI96P High-Density SDF Fiber
Cable Integrity, page 29-413.
Loss of LAN communication from PAM to TSI 1
Loss of LAN communication from PAM to TSI 3
__ 17.2 If you are troubleshooting another type of error

message, continue to step 18, page 29-412.
__ 18. Remove the alarmed PAM. Disconnect the intra-system fibers from
the front of the PAM before removing the module from the shelf. Go to
step 65, page 29-429.
Page 29-412 7/07 76.5500/29, Rev R

Checking PAM to TSI96P High-Density SDF Fiber Cable Integrity

4.23 Use an optical light source and an optical power meter to verify that light
passes from one end of the cable to the other through both fibers.
Laser 4.24 The Tellabs 5500/5500S and associated optical test sets use
semiconductor laser sources that emit light energy into fiber or lightguide cables.
The lasers emit lightwaves within the infrared (invisible) wavelengths.
regulations. The Tellabs 5500 complies with USA Code of Federal Regulations
(CFR), Title 21, Subchapter J, Part 1040.10, Performance Standards for
Light-Emitting Products, as a class 1 laser product.
Safety Precautions 4.27 Only qualified technicians who are knowledgeable and trained in optical
safety hazards can operate, maintain, install, and service the 5500.
DANGER:
viewing aids. For example, fiber scopes and magnifying glasses must be
DANGER:
DANGER:
to be examined
76.5500/29, Rev R 7/07 Page 29-413

4.29 The optical sources for the Tellabs 5500 system include the following
semiconductor lasers. The laser classification is the USA Center for Devices and
Radiological Health (CDRH) title 21, Code of Federal Regulations (CFR) Chapter
1, Subchapter J, Parts 1040.1.
Optical Fiber Handling 4.30 Optical fibers can break into small glass fragments during handling. These
DANGER:
attention at once.
4.31 To perform procedures other than those specified in the Tellabs

5500/5500S documents can result in hazardous radiation exposure.
fiber:

end.


times.

Page 29-414 7/07 76.5500/29, Rev R

Checking TSI96P Receive __ 19. Retrieve the system timing to verify the inhibit status and the preferred
Fibers network status by entering the following command:
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

1.800.443.5555 (North America) or 1.630.798.7070

one NC copy equals PREFNET=NO. Then, proceed to
step 20, page 29-416.
If both copies PREFNET parameters are the same,

analysis.
76.5500/29, Rev R 7/07 Page 29-415

__ 20. Determine if any modules are inhibited from the network that is
in-service, normal (IS-NR) by entering both of the following
commands:

System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV
__ 20.2 If you are troubleshooting a PAM connected to TSI96-B,

verify that ADATA=OK and ACLK=OK. If you are
troubleshooting a PAM connected to TSI96-A, verify
that BDATA=OK and BCLK=OK. If any modules are
inhibited from the network, refer to Troubleshooting the
Network Complex, page 29-245, or Troubleshooting
Consolidated Core Switch Shelf Equipment,
page 29-363.
Page 29-416 7/07 76.5500/29, Rev R

__ 21. Retrieve the state of the TSI96Ps by entering the following command:
RTRV-EQPT::TSI96-xxxx-A&&-B:ctag;
Example:
RTRV-EQPT::TSI96-161-A&&-B:ctag;
Where: xxxx = SDF number for the TSI96 being retrieved.
System response:
M ctag COMPLD

"TSI96-161-A::HWV=81.55196 RPD,SN=RI1490012,DT=030613,ALMPF=99:PST=IS-ANR-EQ"
"TSI96-161-B::HWV=81.55196,SN=RI1490009,DT=030612,ALMPF=99:PST=IS-NR"
__ 21.1 If the target PAM is connected to an in-service,

abnormal TSI96P, go to step 22, page 29-417.
__ 21.2 If the target PAM is connected to an out-of-service

TSI96, go to step 24, page 29-418.
__ 22. Edit the TSI96P connected to the PAM out-of-service by entering the
following command:
ED-EQPT::TSI96-xxxx-y:ctag::::OOS;
Example:
ED-EQPT::TSI96-161-A:ctag::::OOS;
Where: xxxx = SDF number for the TSI96 being edited.

y = TSI96 copy (A or B).
System response:
M ctag COMPLD

"TSI96-161-A:CL,INT,NSA,08-27,14-53-58,NEND:\"CLR - Loss of LAN communications from
PAM to TSI\""
__ 23. Retrieve the state of the TSI96P by entering the following command:
RTRV-EQPT::TSI96-xxxx-y:ctag;
Example:
RTRV-EQPT::TSI96-161-y:ctag;

System response:
M ctag COMPLD

"TSI96-0161-A::HWV=81.55196 RPD,SN=RI1490012,DT=030613,ALMPF=99:PST=OOS-ANR-EQ"
76.5500/29, Rev R 7/07 Page 29-417

__ 23.1 Verify from the system response that the TSI96P is

out-of-service (OOS).
Caution:
command:

M ctag COMPLD

M ctag COMPLD



__ 25. Retrieve the state of the NC by entering the following command:

System response:
M ctag COMPLD

Hybrid Core Switch:
"NC-B::SIZE=5376,EFSIZE=4480,ESMSIZE=256,MAP=CMM,ALMPF=99:PST=OOS-ANR"

__ 25.1 If the NC supporting the alarmed TSI is in-service (IS),

__ 25.2 If the NC supporting the alarmed TSI in out-of-service

Page 29-418 7/07 76.5500/29, Rev R

__ 26. Edit the NC out-of-service by entering the following command:

System response:
M ctag COMPLD


System response:
M ctag RTRV
Followed by lines of data similar to the following samples:

Hybrid Core Switch:

__ 27.1 Verify from the system response that the NC is

__ 28. Remove the dual LC connector from the TSI96P. Refer to Figure 4.6,
page 29-420.
76.5500/29, Rev R 7/07 Page 29-419

Figure 4.6 55196 TSI96P Front Panel
81.55196
TSI96P
POWER
ACTIVE
FAULT
PT-2
PT-1
FLT SDF
XMT - 2
RCV - 2
XMT - 1 Intra-system fiber connectors

RCV - 1
Note: The fiber connected to XMT - 1 and RCV -1 should be from the lowest SDF
PAM for a given CCSS.
__ 29. Clean the receive connector and secure it to the optical power meter.
__ 30. Set the optical power meter to 1310 nm.
__ 31. Verify the optical power reading meets requirements. Refer to Table
4.10, page 29-421.
Page 29-420 7/07 76.5500/29, Rev R

__ 31.1 If the requirements are acceptable, go to step 32.
__ 31.2 If the requirements are out of range, remove the receive

LC connector from the optical power meter and
reconnect the dual LC fiber cable to the proper port on
the TSI module. Go to step 35, page 29-422.
Table 4.10 Acceptable PAM/TSI96 Optical Parameters

Short/Intermediate

(dBm)
power, minimum -9.5 n/a

(dBm)

(dBm)
(dBm)
__ 32. Remove the receive LC connector from the optical power meter.
__ 33. Clean the dual LC connector and connect it to the proper port on the
TSI96P module.
__ 34.1 If the PAM fault clears within three minutes, go to step
69, page 29-430.
__ 34.2 If the PAM fault does not clear within three minutes,
repeat step 28, page 29-419 through 32 to check the
receive cables for the two ports on the TSI96P module.
__ 34.2.1 If all the receive fiber levels meet

requirements, go to Time Slot
Interchange Module (TSI), page 29-506,
to replace the TSI96P.
Note: If the PAM module has already been replaced, the receive power levels
are in range, and the fault does not clear, follow your company's
prescribed procedures for obtaining technical assistance or call Tellabs
Technical Assistance at 1.800.443.5555 (North America) or
76.5500/29, Rev R 7/07 Page 29-421

Checking PAM Transmit __ 35. Remove the dual LC connector from the front of the PAM for the SDF
Power Levels fiber in question. Refer to Figure 4.7.
Figure 4.7 PAM LC Fiber Optic Connection
__ 36. Using a short LC patch cable, connect the power meter to the transmit
port on the PAM for the opposite end of the failed fiber.
__ 38. Verify the transmit optical power reading meets requirements. Refer to
Table 4.10, page 29-421.
__ 38.2 If the requirements are out of range, remove the optical

power meter from the PAM transmit port and replace
the PTx. Refer to Pluggable Transceiver (PT),
page 29-835.
__ 39. Remove the LC connector from the transmit port on the PAM.
__ 40. Clean and connect the dual LC connector to the proper port on the
front of the PAM.
69, page 29-430.
replace the fiber cable. Refer to Tellabs 5500/5500S
Page 29-422 7/07 76.5500/29, Rev R

Checking PAM Receive __ 42. Retrieve the system timing to verify the inhibit status and the preferred
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

1.800.443.5555 (North America) or 1.630.798.7070

analysis.
76.5500/29, Rev R 7/07 Page 29-423

commands:

System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV
__ 43.2 If you are troubleshooting a PAM connected to TSI96-B,

verify that ADATA=OK and ACLK=OK. If you are
troubleshooting a PAM connected to TSI96-A, verify
that BDATA=OK and BCLK=OK. If any modules are
inhibited from the network, refer to Troubleshooting the
Network Complex, page 29-245, or Troubleshooting
Consolidated Core Switch Shelf Equipment,
page 29-363.
Page 29-424 7/07 76.5500/29, Rev R

Example:
RTRV-EQPT::TSI96-161-A&&-B:ctag;
Where: xxxx = SDF number for the TSI96P being retrieved.
System response:
M ctag COMPLD

__ 44.1 If the TSI96P is in-service (IS), go to step 45,

page 29-425.
__ 44.2 If the TSI96P is out-of-service (OOS), go to step 47,

page 29-426.
__ 45. Edit the TSI96P out-of-service by entering the following command:

Example:
ED-EQPT::TSI96-161-A:ctag::::OOS;

System response:
M ctag COMPLD

"TSI96-161-A:CL,INT,NSA,08-27,14-53-58,NEND:\"CLR - Internal signal failure detected
at ESM from TSI\""
__ 46. Retrieve the state of the TSI96P by entering the following command:
Example:
RTRV-EQPT::TSI96-161-A:ctag;

System response:
M ctag COMPLD


76.5500/29, Rev R 7/07 Page 29-425

Caution:
command:

M ctag COMPLD

M ctag COMPLD




System response:
M ctag COMPLD

Hybrid Core Switch:

__ 48.1 If the NC supporting the alarmed PAM is in-service (IS),

__ 48.2 If the NC supporting the alarmed PAM in out-of-service

Page 29-426 7/07 76.5500/29, Rev R

Caution:

System response:
M ctag COMPLD


System response:
M ctag COMPLD

Hybrid Core Switch:


__ 51. Remove the fiber optic LC connector from the front of the PAM. Refer
__ 54. Verify the optical power reading meets requirements. Refer to Table
4.11, page 29-428.
__ 54.1 If the requirements are acceptable, go to step 55,
page 29-428.

connector from the optical power meter and reconnect
the dual LC fiber cable to the proper port on the front of
the PAM. Go to step 58, page 29-429.
76.5500/29, Rev R 7/07 Page 29-427

Table 4.11 Acceptable PAM/TSI96P Optical Parameters

Short/Intermediate
(dBm)

(dBm)

(dBm)
(dBm)
front of the PAM.
69, page 29-430.
repeat steps 51, page 29-427 through 56, page 29-428
to check the receive cables for all eight ports on the
PAM.

requirements, replace the PTx on the
PAM. Refer to Pluggable Transceiver
(PT), page 29-835.
Note: If the PAM PTx has already been replaced, the receive power levels are in
range, and the fault does not clear, follow your company's prescribed
procedures for obtaining technical assistance or call Tellabs Technical
Assistance at 1.800.443.5555 (North America) or 1.630.798.7070 (outside
North America).
Page 29-428 7/07 76.5500/29, Rev R

Checking TSI96P Transmit __ 58. Remove the dual LC connector from the TSI96P module. Refer to
Power Levels Figure 4.6, page 29-420.
__ 59. Using a short jumper cable, connect the power meter to the transmit
port on the TSI96P module for the opposite end of the failed fiber.
Table 4.11, page 29-428.

power meter from the TSI96P module transmit port, and
replace the TSI96P. Go to Time Slot Interchange
Module (TSI), page 29-506.
__ 62. Remove the LC connector from the transmit port on the TSI96P.
front of the TSI96P.
__ 64.1 If the PAM fault clears after the fibers are reinserted, go
__ 64.2 If the PAM fault does not clear, replace the fiber cable.
Refer to Tellabs 5500/5500S Installation Manual,
76.5500/7.

steps:
backplane.

backplane?


go to step 66.

troubleshooting.
76.5500/29, Rev R 7/07 Page 29-429

following command:
Example:

17, and 18).
System response:
M ctag COMPLD

56:PST=OOS-NR"

the alarmed PAM is out-of-service, normal (OOS-NR),
go to step 69.

the alarmed PAM is in-service, normal (IS-NR), go to
step 71, page 29-431.

the alarmed PAM is out-of-service, abnormal, equipped

the alarmed PAM is in-service, abnormal, equipped
(IS-ANR-EQ), go to step 17, page 29-412.

the alarmed PAM is anything other than what is listed
above, follow your company's prescribed procedures
Finalizing Procedure __ 69. Edit the alarmed PAM in-service (IS) by entering the following
command:
ED-EQPT::PAM-SHx-y:ctag:::MODE=FRCD:IS;
Example:
ED-EQPT::PAM-SH1-8:ctag:::MODE=FRCD:IS;

17, and 18).
System response:
M ctag COMPLD
Page 29-430 7/07 76.5500/29, Rev R

__ 69.1 If the system does not generate a PAM alarm message,

__ 69.2 If the system generates a PAM alarm message, go to

step 17, page 29-412.
following command:
Example:

17, and 18).
System response:
M ctag COMPLD

56:PST=IS-NR"
__ 70.1 Verify from the system response that the PAM is

in-service, normal (IS-NR).
__ 71. Retrieve the present state of NC supporting the target PAM by

Where: x = A or B, whichever NC copy is alarmed or was

previously alarmed.
System response:
M ctag COMPLD

Hybrid Core Switch:



76.5500/29, Rev R 7/07 Page 29-431



page 29-373.

command:
System response:
M ctag COMPLD
system behavior.
command:
System response:
M ctag COMPLD

Hybrid Core Switch:


in-service, normal (IS-NR), go to step 74.

Page 29-432 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

__ 74.1 If the system response lists an internal SDF48 error

message similar to the following examples, go to
Consolidated Core Switch Module (CCSM),
page 29-394.
"PAM-SH1-13,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal SDF48 LOF from PAM to

CCSM \":,ISLTD"
"PAM-SH1-14,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal SDF48 LOMF from CCSM to

PAM \":,ISLTD"
"PAM-SH1-13,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal SDF48 parity error from

CCSM to PAM \":,ISLTD"
"PAM-SH1-14,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal SDF48 SDF48 parity error

from PAM to CCSM \":,ISLTD"
__ 74.2 For all other alarm messages, go to the appropriate

section of this manual to troubleshoot that alarm
message.
__ 74.3 If no new alarm messages were listed in the system

response, go to step 75.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-433

Network Interface Module (NIM)

4.33 In this section, you will troubleshoot the alarmed Network Interface Module
(NIM). You should have completed System Pre-Checks, page 29-372, and been
4.34 A spare NIM may be required in order to perform this procedure. Refer to
Caution:
the CCS shelf.


M ctag COMPLD

M ctag COMPLD

"NIM-SH2-1:MN,INT,NSA,01-01,00-48-02,NEND:\"SDF48 Loss of Signal detected at fiber
4\",CAM-02-B:,NIMAN"

fiber 4\""
"NIM-SH2-1,EQPT:MN,REVLVL,NSA,06-04,06-59-47,NEND,,,\"Module revision level does not

meet revision level requirements\""


__ 1.1 If the system response indicates one of the following, an

"SDF48 Loss of Signal " or "SDF48 Yellow Frame" go to
Verifying SDF48 Cables on NIM, page 29-442.
- SDF48 Loss of Signal detected at fiber x

- SDF48 Yellow Frame detected at fiber x
- SDF48 mismatch detected at fiber X
__ 1.2 For all other alarm messages, proceed to step 2,
page 29-435.
Page 29-434 7/07 76.5500/29, Rev R

__ 2. Retrieve the present state of the NIM by entering the following

command:
RTRV-EQPT::NIM-SHx-y:ctag;
Example:
RTRV-EQPT::NIM-SH1-1:ctag;

y = Slot number of the NIM in the range (1 - 8).
System response:
M ctag COMPLD

"NIM-SH1-1::HWV=81.55105 RA,ALMPF=99,SN=NI0210372,DT=910507:PST=OOS-NR"
__ 2.1 If the system response verifies that the alarmed NIM is

page 29-435.
__ 2.2 If the system response verifies that the alarmed NIM is

abnormal (ANR), go to step 12, page 29-439.
__ 3. Edit the alarmed NIM in-service (IS) by entering the following

command:
ED-EQPT::NIM-SHx-y:ctag::::IS;
Example:
ED-EQPT::NIM-SH1-1:ctag::::IS;

System response:
M ctag COMPLD
__ 4. Retrieve the present state of the alarmed NIM by entering the following
command:
Example:

System response:
M ctag COMPLD

"NIM-SH1-1::HWV=81.55105 RA,ALMPF=99,SN=NI0210372,DT=910507:PST=IS-NR"
76.5500/29, Rev R 7/07 Page 29-435


the alarmed NIM is in-service, normal (IS-NR), go to
step 31, page 29-449.

the alarmed NIM is not in-service, normal (IS-NR), go to

command:
System response:
M ctag RTRV

Hybrid Core Switch:
"NIM-SH1-01::HWV=81.55105 RA,ALMPF=99,SN=NI0210372,DT=910507:PST=IS-ANR"

"NIM-SH2-01::HWV=81.55105 RA,ALMPF=99,SN=NI0210372,DT=910507:PST=OOS-ANR"
__ 6. Based on the alarm condition of the NCs supporting the alarmed NIM,
proceed accordingly.
Troubleshooting the Network Complex, page 29-245.
__ 6.2 If only the NC associated with the alarmed NIM is

page 29-437.
Note: The active LEDs of all the modules on the abnormal (ANR) CCS shelf will
turn off during normal system behavior.
Page 29-436 7/07 76.5500/29, Rev R

Caution:

command:

M ctag COMPLD

M ctag COMPLD



Caution:
__ 8. Edit the NC supporting the alarmed NIM out-of-service (OOS) by

entering the following commands:
System response:
M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-437




command:
System response:
M ctag COMPLD
command:
System response:
M ctag COMPLD

Hybrid Core Switch:


page 29-439.

1.800.443.5555 (North America) or 1.630.798.7070
Page 29-438 7/07 76.5500/29, Rev R

__ 12. Edit the alarmed NIM out-of-service (OOS) by entering the following
command:
ED-EQPT::NIM-SHx-y:ctag::::OOS;
Example:
ED-EQPT::NIM-SH1-1:ctag::::OOS;

M ctag COMPLD

System response:
M ctag COMPLD

command:
Example:

System response:
M ctag COMPLD

__ 13.1 Verify that the alarmed NIM is out-of-service (OOS).
__ 14. Visually verify that the alarmed NIM is present in the slot.
page 29-440.

page 29-445.
76.5500/29, Rev R 7/07 Page 29-439

__ 15. Diagnose the problem on the alarmed NIM by entering the following
command:
normal behavior.
DGN-EQPT::NIM-SHx-y:ctag::,ITER=3;
Example:
DGN-EQPT::NIM-SH1-1:ctag::,ITER=3;

System response:
M ctag COMPLD

"NIM-SH1-1:PASS-3"
"NIM-SH1-1:FAIL-0"
/* The following is PT information */

PORT1:TYPE=SDF48:HWV=81.SDF48SR1851M_RA,SN=P8B07F7,DT=050906,CLEI=T3C5CCDAAA,
PTVENDOR=FINISAR CORP.,PTVENDORPN=FTRJ1321P1BTL
PORT8:TYPE=SDF48:HWV=81.SDF48SR1851M_RB,SN=P8B07FC,DT=050906,CLEI=T3C5CCDAAA,
;

step 16, page 29-440.


__ 17. After the three minute module download has completed, determine the
front panel LED status of the module.
__ 17.2 If the Fault LED turns off, go to step 25, page 29-446.
Page 29-440 7/07 76.5500/29, Rev R

__ 18. Diagnose the problem on the alarmed NIM by entering the following
command:
normal behavior.
DGN-EQPT::NIM-SHx-y:ctag;
Example:
DGN-EQPT::NIM-SH1-1:ctag;

System response:
M ctag COMPLD

"NIM-SH1-1:PASS-1"
"NIM-SH1-1:FAIL-0"

PORT8:TYPE=SDF48:HWV=81.SDF48SR1851M_RB,SN=P8B07FC,DT=050906,CLEI=T3C5CCDAAA,
;


__ 19. Remove the alarmed NIM. Disconnect the intra-system fibers from the
front of the NIM before removing the module from the shelf. Go to step
21, page 29-445.
76.5500/29, Rev R 7/07 Page 29-441

Verifying SDF48 Cables on NIM

4.35 Follow the steps in this section verify proper SDF48 cabling on the NIM.

M ctag COMPLD

M ctag COMPLD

"NIM-SH2-1:MN,INT,NSA,01-01,00-48-02,NEND:\"SDF48 Loss of Signal detected at
fiber 4\",CAM-02-B:,NIMAN"

fiber 4\""


__ 1.1 If the system response indicates an "SDF48 Loss of

Signal " or "SDF48 Yellow Frame" go to step 2,
page 29-442.
__ 1.2 If the system response indicates an "SDF48 mismatch

detected at fiber X," go to step 18, page 29-445.
Troubleshooting SDF48 Loss __ 2. Based on the system response from step 1, locate the NIM and fiber
of Signal Alarms on NIM that is alarmed.
__ 3. Verify that the connections are secure, and that the fiber is not
damaged or broken. If the fiber is damaged or broken, replace the
cable.
Page 29-442 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

fiber 2\""

fiber 2\""


__ 4.2 If the alarm does not clear go to step 5, page 29-443.
__ 5. Remove the duplex connector from the NIM that is in alarm.

__ 6. Using the proper adapter on a fiber optic meter, attach a short fiber
jumper cable to the receive side of the duplex connector.
__ 7. Set the fiber optic meter to 850 nm and verify the reading is within an
acceptable range. Refer to Table 4.12.
Table 4.12 Acceptable NIM Optical Parameters

(dBm)

(dBm)

(dBm)

If the reading are not within range, go to step 11, page 29-444.
__ 9. Using the proper fiber optic cleaning procedures, clean the duplex
connector and connect it to the NIM.
76.5500/29, Rev R 7/07 Page 29-443


__ 10.1 If the NIM fault clears within three minutes, go to step
20, page 29-445.
__ 10.2 If the NIM fault does not clear, repeat step 5,

page 29-443, through 8, page 29-443 to check the
transmit cables for the NIM.
__ 10.2.1 If all the transmit fiber levels meet

page 29-438, to replace the NIM.
__ 11. Locate the CAM in the CCS shelf, to which the opposite end of the
SDF48 cable is connected. (The CAM is listed in the secondary AID in
the system response from step 1, page 29-442.)
__ 12. Remove the duplex connector from the CAM.
__ 13. Using a short jumper cable, connect a fiber optic meter to the transmit
port on the CAM.
__ 14. Set the fiber optic meter to 850 nm, and verify the reading is within the
acceptance range. Refer to Table 4.13, page 29-444.
Table 4.13 Acceptable CAM Optical Parameters


(dBm)

(dBm)

(dBm)
__ 15.1 If the power levels are not within range, go to CSM
Adapter Module (CAM), page 29-318.
__ 16. Using proper fiber optic cleaning procedures, clean CAM duplex
connector and the SDF48 cable. Connect the SDF48 cable to the
CAM.
20, page 29-445.
__ 17.2 If the CAM fault does not clear, replace the SDF48
cable. After three minutes, if the CAM fault still does not
clear, go to CSM Adapter Module (CAM), page 29-318.
Page 29-444 7/07 76.5500/29, Rev R

Troubleshooting SDF48 __ 18. Based on the system response from step 1, page 29-442, locate the
Mismatch Alarms on NIM NIM that is alarmed and the AID of the CAM where the SDF48 cable
is connected.
Example:

"NIM-SH2-1:MAN,SC,01-01,00-48-21,NEND:\"SDF48 mismatch detected at fiber

__ 19. Correct the SDF48 fiber cabling between the two modules.

M ctag COMPLD

M ctag COMPLD

"CAM-02-B:MAN,CL,01-01,00-53-01,NEND:\"CLR - SDF48 mismatch detected at fiber 2\""
"NIM-SH2-1:MAN,CL,01-01,00-53-01,NEND:\"CLR - SDF48 mismatch detected at fiber 4\""
"NC-B:CL,PROTNA,NSA,01-01,00-53-39,NEND:\"CLR - Network Complex failed (ANR) - not

available for protection\""

__ 20.2 If the alarm does not clear go to step 2, page 29-435,

and complete the procedure for troubleshooting the
NIM.

steps:
backplane.

backplane?


go to step 66.
76.5500/29, Rev R 7/07 Page 29-445


troubleshooting.
__ 23. Insert the module and reconnect the intra-system fiber cables.
command:
Example:

System response:
M ctag COMPLD


the alarmed NIM is out-of-service, normal (OOS-NR),

the alarmed NIM is in-service, normal (IS-NR), go to
step 28, page 29-447.

the alarmed NIM is out-of-service, abnormal, equipped

the alarmed NIM is in-service, abnormal, equipped
(IS-ANR-EQ), go to step 1, page 29-442.

the alarmed NIM is anything other than what is listed
Page 29-446 7/07 76.5500/29, Rev R

Finalizing Procedure __ 26. Edit the alarmed NIM in-service (IS) by entering the following
command:
ED-EQPT::NIM-SHx-y:ctag:::MODE=FRCD:IS;
Example:
ED-EQPT::NIM-SH1-1:ctag:::MODE=FRCD:IS;

System response:
M ctag COMPLD
__ 26.1 If the system generates a NIM alarm message, go to

__ 26.2 If the system does not generate a NIM alarm message,

command:
Example:

System response:
M ctag COMPLD

"NIM-SH1-1::HWV=81.55105 RA,ALMPF=99,SN=NI0210372,DT=910507:PST=IS-NR"
__ 27.1 Verify from the system response that the NIM is

__ 28. Retrieve the present state of NC supporting the target NIM by entering

previously alarmed.
System response:
M ctag COMPLD

Hybrid Core Switch:

76.5500/29, Rev R 7/07 Page 29-447





page 29-373.

command:
System response:
M ctag COMPLD
system behavior.
command:
System response:
M ctag COMPLD

Hybrid Core Switch:



Page 29-448 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD


message.
__ 31.1.2 If no, go to step 32.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-449

Consolidated Group Controller Module (CGCM)

4.36 In this section, you will troubleshoot the faulted Consolidated Group
Controller (CGCM). You should have completed System Pre-Checks,
4.37 A spare CGC may be required in order to perform this procedure. Refer to

M ctag COMPLD

M ctag COMPLD

"CGC-SH2-10,EQPT:NR,MAN,NSA,05-08,06-07-12,NEND,,,\"CGC to CGC LAN Comm Lost between
SH1 and SH2\"
"CGC-SH1-10:MAN,SC,06-15,09-43-07,NEND:\"LAN and Timing Interface Panel (LTIP)

miscabled on port J13\":,ISLTD"
__ 1.1 If the system response lists the following alarm

message, go to Port Aggregation Module (PAM),
page 29-405.
Loss of LAN communication from CGC to PAM-x

message, go to Checking LTIP to LIP Cables,
page 29-464.
LAN and Timing Interface Panel (LTIP) miscabled on port {J1|J2|J3|J4|J11|J12|J13|J14}
__ 1.3 If the system response lists another CGC alarm

message, go to step 2, page 29-451.
Page 29-450 7/07 76.5500/29, Rev R

__ 2. Retrieve the present state of both NCs, and the present state of both
CGCs, by entering the following command:
System response:
M ctag RTRV
Followed by lines of data containing output similar to the following samples:
Hybrid Core Switch:

"CGC-SH1-10::HWV=81.55112 RA,SN=UV0166613,DT=051115:PST=IS-NR"
"CGC-SH2-10::HWV=81.55112 RA,SN=TN2200010,DT=080508:PST=IS-NR-ACT"

"CGC-SH2-10::HWV=81.55112 RA,SN=TV2904922,DT=051017:PST=IS-NR-ACT"
__ 2.1 Determine if the CGC that is alarmed is in NC-A or

NC-B.

the non-alarmed NC is out-of-service, normal

the non-alarmed NC is in-service, normal (IS-NR), go to

the non-alarmed NC is anything other than what is listed
76.5500/29, Rev R 7/07 Page 29-451

__ 3. Edit the non-alarmed NC in-service (IS) by entering the following

command:
Where: x = Network Copy identifier (A or B).
Note: Module front panel LEDs light for approximately five seconds during
System response:
M ctag COMPLD
__ 4. Retrieve the present state of the non-alarmed NC:

Where: x = Shelf identifier (A or B).
System response:
M ctag RTRV
Hybrid Core Switch:



the non-alarmed NC is in-service, normal (IS-NR), go to

present state of the non-alarmed NC is
not in-service, normal (IS-NR), follow
Page 29-452 7/07 76.5500/29, Rev R

Caution:

command:

M ctag COMPLD

M ctag COMPLD



Caution:
__ 6. Edit the NC supporting the alarmed CGCM out-of-service (OOS) by

entering one of the following commands:
System response:
M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-453




command:
System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD

Hybrid Core Switch:


page 29-455.

1.800.443.5555 (North America) or 1.630.798.7070
Page 29-454 7/07 76.5500/29, Rev R

__ 10. Retrieve the present state of the alarmed CGC by entering the
following command:
RTRV-EQPT::CGC-SHx-10:ctag;
System response:
M ctag COMPLD

"CGC-SH1-10::HWV=81.55112 RA,,SN=EL00092000,DT=050925:PST=IS-ANR-EQ"
__ 10.1 If the present state of the alarmed CGC is in-service,

abnormal, equipped (IS-ANR-EQ), go to step 6,
page 29-453.

abnormal, unequipped (IS-ANR-UEQ), go to step 6,
page 29-453.
__ 10.3 If the present state of the alarmed CGC is

out-of-service, abnormal, unequipped
(OOS-ANR-UEQ), go to step 14, page 29-456.

out-of-service, abnormal, equipped (OOS-ANR-EQ), go

out-of-service, normal (OOS-NR) go to step 29,
page 29-460.

normal, (IS-NR) go to step 31, page 29-461.
__ 10.7 If the system response is anything other than what is

listed above, follow your company's prescribed
__ 11. Edit the alarmed CGC out-of-service (OOS) by entering the following
command:
ED-EQPT::CGC-SHx-10:ctag::::OOS;
Note: Module front panel LEDs light for approximately two minutes during normal
system behavior.
System response when command prompt confirmation (CPC) is off:

M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-455

M ctag COMPLD
__ 12. Does the system generate an alarm CLR (clear) message for the
alarmed CGC? Refer to the following example:

following command:
System response:
M ctag COMPLD

"CGC-SH1-10::HWV=81.55112 RA,,SN=EL00092000,DT=050925:PST=OOS-ANR-EQ"

out-of-service, abnormal, unequipped, assigned
(OOS-ANR-UEQ) go to step 14.

out-of-service, abnormal, equipped, assigned
(OOS-ANR-EQ) go to step 19, page 29-457.

page 29-460.

__ 14. Visually verify that a module is present in the slot.

page 29-457.

page 29-458.
Page 29-456 7/07 76.5500/29, Rev R


steps:
backplane.

backplane?

__ 15.3 If backplane damage is not suspected, go to step 16,

page 29-457.

troubleshooting.
__ 19. Diagnose the problem on the alarmed CGC by entering the following
command:
Note 1: The CGC must be out-of-service (OOS) and it must be equipped (EQ) in
order to perform diagnostics on it. However, if the CGC is unequipped
(UEQ), follow your company's prescribed procedures for obtaining
America).
normal behavior.
DGN-EQPT::CGC-SHx-10:ctag;
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-457


"CGC-SH1-10:PASS-1"
"CGC-SH1-10:FAIL-0"
__ 19.1 If the system response shows 0 passed iterations, go to

step 20.
__ 19.2 If the system response shows 1 passed iteration, go to

step 28, page 29-459.
Note: The LEDs on the front panel of the module flash during the download.
__ 22. Diagnose the problem on the alarmed CGC by entering the following
command:
Note 1: The CGC must be out-of-service (OOS) and it must be equipped (EQ) in
order to perform diagnostics on it. However, if the CGC is unequipped
America).
normal behavior.
DGN-EQPT::CGC-SHx-10:ctag;
System response:
M ctag COMPLD

"CGC-SH1-10:PASS-1"
"CGC-SH1-10:FAIL-0"

step 23.

step 28, page 29-459.
Page 29-458 7/07 76.5500/29, Rev R

__ 23. Remove the alarmed CGC.

place.

steps:
backplane.
__ 24.2 Verify that all pins extending straight outward from the
backplane.
__ 24.2.1 If there is any backplane damage, follow


go to step 25.

troubleshooting.
__ 27. After a three minute module download has completed, determine the
__ 27.1 If the Fault LED turns off, go to step 28.
__ 27.2 If the Fault LED remains lit, follow your company's

1.800.443.5555 (North America) or 1.630.798.7070
following command:
System response:
M ctag COMPLD

"CGC-SH1-10::HWV=81.55112 RA,,SN=EL00092000,DT=050925:PST=OOS-NR"
76.5500/29, Rev R 7/07 Page 29-459


the alarmed CGC is out-of-service, normal (OOS-NR),
go to step 29.

the alarmed CGC is not out-of-service, normal
(OOS-NR), choose one of the following options:
__ 28.2.1 If you have not reseated the module, go

__ 28.2.2 If you have already reseated the module,

__ 28.2.3 If the alarm message that was received in

step 1, page 29-450, indicates possible
faulty cabling, proceed to step 29,
page 29-460.
__ 28.2.4 If the alarm message does not indicate

faulty cabling, follow your company's
Note: Refer to Table 4.9, page 29-392 for Consolidated Group Controller alarm
messages.
__ 29. Edit the alarmed CGC in-service (IS) by entering the following
command:
ED-EQPT::CGC-SHx-10:ctag::::IS;
System response:
M ctag COMPLD
following command:
System response:
M ctag COMPLD

"CGC-SH1-10::HWV=81.55112 RA,,SN=EL00092000,DT=050925:PST=IS-NR"
Page 29-460 7/07 76.5500/29, Rev R


the alarmed CGC is in-service, normal (IS-NR), go to
step 31, page 29-461.
__ 30.2 If the system response verifies that the CGC is

in-service, normal (IS-NR), and the alarm message
from step 1, page 29-450 indicates faulty cabling,
proceed to step 31, page 29-461.

the alarmed CGC is not in-service, normal (IS-NR),
command:
System response:
M ctag RTRV
Hybrid Core Switch:


"NC-A::SIZE=5376,EFSIZE=4608,ESMSIZE=0,MAP=CMM,ALMPF=99:PST=IS-NR
__ 31.1 If the present state is OOS, proceed to step 32,

page 29-461.
__ 31.2 If the present state is IS-NR, proceed to step 34,

page 29-462.
__ 32. Edit the alarmed NC in-service by entering the following command.

Where: x = Network Copy identifier (A or B).
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-461

command:
System response:
M ctag RTRV
Hybrid Core Switch:


__ 33.1 Verify that the present state of the alarmed NC is IS-NR.


M ctag COMPLD

M ctag COMPLD

__ 34.1.1 If the alarm message indicates possible

faulty cabling, proceed to go to
Troubleshooting CGCM LAN Cables,
page 29-463, to troubleshoot the LAN.
Note: Refer to Table 4.9, page 29-392 for Consolidated Group Controller alarm
messages.
__ 34.1.2 If the system response lists a different

alarm message, go to the appropriate
section of this manual to troubleshoot
that alarm message.
__ 34.1.3 If the system response does not list any

alarm messages, go to step 35,
page 29-463.
Page 29-462 7/07 76.5500/29, Rev R



End of Procedure
Troubleshooting CGCM LAN Cables

__ 1. Choose one of the following options, based on the alarm message you
received.
Checking LTIP to LIP Cables, page 29-464.
CGC to LSM LAN Comm Lost at LAN A port (missing

cable?)
LAN and Timing Interface Panel (LTIP) miscabled on

port J14
LAN Interface Panel (LIP) miscabled on port LAN-1

Checking CGC to CGC Cables, page 29-467.
CGC to CGC LAN Comm Lost between SH1 and SH2
__ 1.3 If CONTCOM type alarm messages are received, and

other troubleshooting measures have not been able to
resolve the alarm, refer to Verifying CGC LAN Cabling,
page 29-468 to verify that the LAN cables are correctly
connected.
76.5500/29, Rev R 7/07 Page 29-463

Checking LTIP to LIP Cables

4.38 Perform the steps in this section to verify the cabling between the LTIP and
the LIP:

M ctag COMPLD

M ctag COMPLD

"CGC-SH2-10:MN,MAN,NSA,06-20,10-09-20,NEND:\"LAN and Timing Interface Panel (LTIP)
miscabled on port J14\":,ISLTD"
"LSM-B:MN,MAN,SC,06-20,10-09-20,NEND:\"LAN Interface Panel (LIP) miscabled on port

LAN-1\":,ISLTD"
__ 1.1 If the following messages are retrieved, suspect that the

LAN cables are plugged into the wrong connectors on the
LTIP or the LIP. Proceed to step 2.
LAN and Timing Interface Panel (LTIP) miscabled on

port J14
LAN Interface Panel (LIP) miscabled on port LAN-1
__ 1.2 If the following message is retrieved, proceed to step 4,

page 29-465.
CGC to LSM LAN Comm Lost at LAN A port (missing

cable?)
__ 2. Verify that the LAN cable is plugged into the LAN-1 connector on the
LIP, and the J14 connector on the LTIP. Refer to Figure 4.8,
page 29-465 and Figure 4.9, page 29-466.
__ 3. Go to step 7, page 29-467.
Page 29-464 7/07 76.5500/29, Rev R

Figure 4.8 5580 LTIP Connectors

LTIP-2 = to LAN-1 connector on LIP-B

LTIP-1 = to LAN-1 connector on LIP-A
to P31 connector on CCS shelf

LTIP-1 and LTIP-2 =

LTIP-1 and LTIP-2 =
LTIP-1 and LTIP-2 =
P4
T
R
GND
J7 J8 J9 J10 J3 P3 J4 P4 J36 J37 J53 J2 J1 J11 J12 J13 J14
LAN B LAN A AUX B AUX A OUT1 OUT2 BITS OUT IN AUX B AUX A LAN B LAN A
CGCM SlOT 11 SYNC A SYNC B EXT.REF. LEGACY NTD CGCM SlOT 10
__ 4. Examine the Ethernet cable between LAN 1 connector on the LIP, and
the LAN A connector on the LTIP. Verify that the Ethernet cable is not
visibly damaged.
__ 4.1 If the cable is not visibly damaged, proceed to step 5.
__ 4.2 If the cable is damaged, replace it and proceed to step

7, page 29-467.
__ 5. Verify that the LAN A connection on the LAN Timing Interface Panel
(LTIP) is secure. Refer to Figure 4.8.
__ 6. Verify that the LAN 1 connection on the LIP is secure. Refer to Figure
4.9, page 29-466.
76.5500/29, Rev R 7/07 Page 29-465

Figure 4.9 LIP Connectors
DEBUG
STATU S
LIP
CO LAN SIM-B
XCOPY
23
1
SIM-A LAN-7 LAN-5 LAN-3 LAN-1
14
15
LAN-8 LAN-6 LAN-4 LAN-2

18
22
17
21
16
20
19
0
A IP LSM
Page 29-466 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

__ 7.1 If the alarm has not cleared, replace the Ethernet cable.
Repeat step 7.
__ 7.2 If the alarm has cleared, go to Verifying CGC LAN

Cabling, page 29-468.
Checking CGC to CGC Cables

4.39 Perform the steps in this section to troubleshoot CGC to CGC alarm
messages.

M ctag COMPLD

M ctag COMPLD

"CGC-SH1-10,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"
\"CGC to CGC LAN Comm Lost between SH1 and SH2\"
76.5500/29, Rev R 7/07 Page 29-467

__ 2. If the following alarm messages are received, go to step 3,

page 29-468.
\"SDF48 Cable Bundle from <plug# P24> to <plug# P26> not detected\"
If other alarm messages are received, refer to the appropriate section

of the Troubleshooting Manual to troubleshoot the alarm.
__ 3. Important: If the P24 and P26 connectors on the CCS shelf are
suspected as faulty, follow your company’s prescribed procedures for
obtaining technical assistance or call Tellabs Technical Assistance at
America).
Verifying CGC LAN Cabling

4.40 CONTCOM alarms are raised for any LAN disconnect that occurs on the
LSM/LIP and the CGC. If the LAN cables from the LSM/LIP to the CGC are
misconnected—for example, if the LSM-A LAN is connected to CGC-SH2,
unexpected alarm messages will be generated. Also, if the LSM-A is faulted, alarm
messages will be generated on CGC-SH1 and LSM-B. Refer to Figure 4.10,
page 29-468.
Figure 4.10 LSM/LIP to CGC LAN Cabling
AC-A AC-B
X COPY CO LAN X COPY CO LAN
LSM LIP-A LIP-B LSM

A LAN-1 LAN-1 B
J14 J14
LTIP-1 LTIP-2
LAN-A LAN-A
CGC-SH1 in CCS-A CGC-SH2 in CCS-B
P24 P26 P24 P26
Key
= LAN cable
Page 29-468 7/07 76.5500/29, Rev R

4.41 If unexpected CONTCOM alarms are generated on the system, follow the
steps below to verify the LAN cabling.
__ 1. Disconnect the LAN cable from the LAN-1 jack on LIP-A.

M ctag COMPLD

M ctag COMPLD

"LSM-B,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,CONTCOM"
\"LSM to LSM LAN Comm Lost at XCOPY port (missing cable?)\"
"CGC-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,CONTCOM"

\"CGC to LSM LAN cable failure detected\"
__ 2.1 Note the "CONTCOM" messages that are generated,

and the affected modules and entities.
If the LAN cables are correctly connected, failures will

be detected at LSM-A and CGC-SH1-10.
If any of the LAN cables are misconnected, failures will
be detected at LSM-A and CGC-SH2-10.
__ 3. Reconnect the LAN cable to the LAN-1 jack on LIP-A.
__ 4. Disconnect the LAN cable from the LAN-1 jack on LIP-B.

M ctag COMPLD

M ctag COMPLD

"LSM-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,CONTCOM"
"CGC-B,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,CONTCOM"



be detected at LSM-B and CGC-SH2-10.
If any of the LAN cables are misconnected, failures will
be detected at LSM-B and CGC-SH1-10.
76.5500/29, Rev R 7/07 Page 29-469

__ 6. Reconnect the LAN cable to the LAN-1 jack on LIP-B.

__ 7. Disconnect the LAN cable from XCOPY port on LIP-A.

M ctag COMPLD

M ctag COMPLD

"LSM-A,EQPT:MJ,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,CONTCOM"
"LSM-B,EQPT:MJ,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,CONTCOM"

"CGC-A,EQPT:MJ,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,CONTCOM"



be detected at LSM-A and LSM-B.
If any of the LAN cables are misconnected, a failure will
be detected at either LSM-A or LSM-B.
__ 9. Reconnect the LAN cable at XCOPY port on LIP-A.

M ctag COMPLD

M ctag COMPLD


message.
__ 10.2 If troubleshooting reveals misconnected LAN cables,

refer to Tellabs 5500 Installation, 76.5500/7, for the
procedure to reconnect the LAN.
Page 29-470 7/07 76.5500/29, Rev R

__ 10.3 If troubleshooting reveals that the LAN cables are

correctly connected, but there is an outstanding alarm
message that cannot be resolved, follow your
End of Procedure
76.5500/29, Rev R 7/07 Page 29-471

USER NOTES
Page 29-472 7/07 76.5500/29, Rev R

Troubleshooting Manual 5. Troubleshooting System Common Equipment
5. Troubleshooting System Common Equipment
5.01 This section contains procedures to troubleshoot a problem occurring on

• Port Power Supply Module (PPS)
• Port Group Controller Module (PGC)
• Time Slot Interchange Module (TSI)

• Time Slot Interchange Module 96P (TSI96P)
• Line Interface Module (LIM)
5.02 When troubleshooting the system common equipment, always check for
system common equipment.
troubleshooting the system common equipment. Refer to Status of the LEDs on a
command, the supporting network group controller (NGC), port group controller
(PGC), or consolidated group controller (CGC) must be in-service normal (IS-NR).
The module itself must be equipped. For more information on executing this
command, go to Tellabs 5500/5500S Maintenance Manual, 76.5500/24.
Warning:
76.5500/29, Rev R 7/07 Page 29-473

5. Troubleshooting System Common Equipment Troubleshooting Manual

5.07 Figures 5.1 through 5.2, page 29-476, are for reference only. Use these
figures as an aid in troubleshooting the alarmed system common equipment.
Port Group Controller Module Figure 5.1 Port Group Controller Module (PGCx)
PGC
active
fault
Page 29-474 7/07 76.5500/29, Rev R

Table 5.1 Status of Port Group Controller Module LEDs

Fault OFF
All ON a) Fault LED flashes ON/OFF regularly when requesting a 1. Active, slow flash = requesting download from
download from the Administrative Complex. main processor.
b) Module is in self-diagnostic mode. 2. PGC downloads information from the database to
all of the modules on its shelf. The fault LEDs for
other modules may be ON until the PGC is seated
and downloads the information to the modules.
Usually a temporary state that occurs during module

or system initialization.
Active OFF, a) Faulted or failed module. Fault LED flashes periodically:

Fault ON b) Bent pin(s) on backplane connector. Active, fast flash = in error state (for example,
incorrect fiber cabling to TSI).
Both OFF a) Module is in standby (STBY) mode. When PGC is out-of-service (OOS), it will not affect
b) Module is out-of-service (OOS). See Note. other network modules it serves.
c) Bent pin(s) on backplane connector.
d) No power, out of slot, breaker OFF. Usually a temporary state.
76.5500/29, Rev R 7/07 Page 29-475

Time Slot Interchange

Module LEDs
Figure 5.2 Time Slot Interchange Module LEDs

5596 55196
5516, 5516DD,5519, 5519A, and 5546
TSI96 TSI96P
TSI
power
active
power
fault
PT-2
active
PT-1
FLT SDF
fault
XMT - 6
RCV - 6
XMT - 5
RCV - 5
XMT - 4
RCV - 4
XMT - 2
XMT - 3
RCV - 2
RCV - 3
XMT - 1
XMT - 2
active RCV - 2
RCV - 1
fault XMT - 1
RCV - 1
Time Slot Interchange Module Time Slot Interchange Module (TSI96) Time Slot Interchange Module (TSI96P)
(TSI) in normal state (active LED is ON) in normal state (power and active LEDs in normal state (power and active LEDs
are ON) are ON)
Page 29-476 7/07 76.5500/29, Rev R

Table 5.2 Status of Time Slot Interchange Module LEDs (5516, 5516DD, 5519, 5519A, and 5546)
Status of
LEDs Meaning Notes
Active ON, Normal, active state. Active LEDs are always ON for both TSIs, when in a
Fault OFF normal, active state.
All ON - RTRV-EQPT = IS-ANR. The test for fault LED flashes ON for self-diagnostics.
- If it loses timing from NC. For example, if the NC is
out-of-service (OOS), both TSI LEDs light. Usually a temporary state that occurs during module or
- At power-up. system initialization.
Active OFF, - When the TSI is OOS-ANR-EQ.

Fault ON - Faulted or failed module.
Both OFF - Out-of-service (OOS). - When the TSI status is out-of-service (OOS), this
- No power, not in slot, breaker OFF, bent pin(s) on causes the network to become abnormal (ANR). A
backplane connector. condition alarm may appear, “network unavailable for
protection.”
- When the module or shelf hasn’t been edited into
service or “grown,” an out-of-service, normal
(OOS-NR) status may appear.
Table 5.3 Status of Time Slot Interchange Module LEDs (TSI96)
Status of
LEDs Meaning Notes
Power ON, Normal, active state. Power and Active LEDs are always ON for both TSIs
Active ON, when in a normal, active state.
Fault OFF
All ON - RTRV-EQPT = IS-ANR. The test for fault LED flashes ON for self-diagnostics.
- If it loses timing from NC. For example, if the NC is
out-of-service (OOS), both TSI LEDs light. Usually a temporary state that occurs during module
- At power-up. or system initialization.
Power ON, - When the TSI is OOS-ANR-EQ.

Power, Active, and - Out-of-service (OOS). - When the TSI status is out-of-service (OOS), this
Fault OFF - No power, not in slot, breaker OFF, bent pin(s) on causes the network to become abnormal (ANR). A
backplane connector. condition alarm may appear, “network unavailable for
protection.”
- When the module or shelf hasn’t been edited into
service or “grown,” an out-of-service-normal
76.5500/29, Rev R 7/07 Page 29-477

Table 5.4 Status of Time Slot Interchange Module 96P LEDs (TSI96P)
Power ON, Normal, active state. Power and Active LEDs are always ON for both
Active ON, TSIs when in a normal, active state.
Fault OFF
All ON - RTRV-EQPT = IS-ANR. The test for fault LED flashes ON for
- If it loses timing from CCSS. For example, if the self-diagnostics.
CCSS is out-of-service (OOS), all TSI LEDs light.
- At power-up. Usually a temporary state that occurs during
module or system initialization.
Power ON, - When the TSI is OOS-ANR-EQ.

Power, Active, and Fault OFF - Out-of-service (OOS). - When the TSI status is out-of-service (OOS),
- No power, not in slot, breaker OFF, bent pin(s) on this causes the network to become abnormal
backplane connector. (ANR). A condition alarm may appear, “network
unavailable for protection.”
- When the module or shelf hasn’t been edited
into service or “grown,” an out-of-service-normal
PT-x The Pluggable Transceiver is functioning normally

FLT OFF and the SDF is functioning normally.
SDF Green
PT-x - The PT has been unseated from its slot.

FLT Red
SDF Red
PT-x - The SDF cable has been pulled from the port.
FLT Off - The transmit and receive fibers of the SDF cable
SDF Red are possibly flipped.
- "SDF loss of signal on receive fibers" alarm
message has been generated
PT-x - Module is resetting. Usually a temporary state.

FLT Off - System is initializing.
SDF Amber - "Link ID mismatch" alarm has been generated. Persistent SDF amber condition may indicate
incorrect TSI96P to PAM cabling.
Page 29-478 7/07 76.5500/29, Rev R

System Pre-Checks
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
command:
System response:
M ctag COMPLD

__ 2.1 Verify that your login is a UPC of an A8 or greater.

76.5500/29, Rev R 7/07 Page 29-479



M ctag COMPLD

M ctag COMPLD

"PPS-0035-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"

page 29-480, to troubleshoot the faulted module listed
in the alarm message(s) received.

• for a PGC, go to Table 5.5, page 29-481
• for a TSI, go to Table 5.6, page 29-484
• for a LIM, go to Table 5.7, page 29-492
• for a PPS, go to Table 5.8, page 29-493
Page 29-480 7/07 76.5500/29, Rev R

Port Group Controller Module (PGC) Alarm Messages

5.12 In order to troubleshoot the alarm message(s) received for a faulted PGC,
messages that can be generated for an PGC.The second column lists a description
Table 5.5 Port Group Controller Module (PGC) Alarm Messages

TSI-A to GC TSI-A to the GC. TSI-A and the PGC is broken.
Go to Port Group Controller Module

(PGC), page 29-494.
TSI-B to GC TSI-B to the GC. TSI-B and the PGC is broken.

(PGC), page 29-494.
PGC. have been disconnected.

(PGC), page 29-494.
PGC. have been disconnected.

(PGC), page 29-494.
INT EEPROM failure When the PGC initializes, it polls the Either the EEPROM data is corrupt or
AP to determine whether or not it hardware has failed.
should initialize as the active or
standby PGC. As part of this process, Go to Port Group Controller Module
the EEPROM of the PGCs are read (PGC), page 29-494.
and validated for size, checksum and
parity. This alarm is generated if the
software fails to read the EEPROMs or
if a failure occurs during the validation
of the EEPROMs.
INT Failed diagnostics The PGC has failed one of its internal Failed one or more internal diagnostic
diagnostics either on power-up or by tests. Failed or faulted module.
TL1 DGN command.
(PGC), page 29-494.
INT GC executable load image checksum The GC cannot verify the load image There is a problem with the download
verification fail checksum. of the PGC.

(PGC), page 29-494.
INT Lost LAN communication with GC There is no LAN communication to the The PGC is faulty.
GC.
(PGC), page 29-494.
76.5500/29, Rev R 7/07 Page 29-481

Table 5.5 Port Group Controller Module (PGC) Alarm Messages (Continued)
INT Module not compatible with existing Reporting module is not supported by Module revision level is either lower or
software the software version currently higher than the levels supported by the
operating on the system. current software version.

(PGC), page 29-494.
INT PGC Removed The AC has detected the absence of One or more of the following has
the PGC module. occurred:
- PGC module is defective.
- PGC module has been removed from
its slot.
- IPC link to PGC module has failed.
- Backplane pin damage in the PGC
slot.

(PGC), page 29-494.
MAN GC LAN Miscabled - AC-A on PGC-A AC-A is connected to PGC-A LAN B. The LAN cables are improperly wired.
LAN B
MAN GC LAN Miscabled - AC-B on PGC-A AC-B is connected to PGC-A LAN A. The LAN cables are improperly wired.
LAN A
MAN GC LAN Miscabled - AC-A on PGC-B AC-A is connected to PGC-B LAN B. The LAN cables are improperly wired.
LAN B
MAN GC LAN Miscabled - AC-B on PGC-B AC-B is connected to PGC-B LAN A. The LAN cables are improperly wired.
LAN A
MEA GC type and/or SDF inconsistent with The GC type and/or the SDF is There is a GC type mismatch.
assignment inconsistent with its assignment.
(PGC), page 29-494.
MEA GC type inconsistent with assignment The GC type is inconsistent with its There is a GC type mismatch.
assignment.
(PGC), page 29-494.
PROTNA PGC failed (ANR) - not available for Redundancy for the mate PGC has The PGC has been removed from its
protection been lost because the PGC is in an slot.
abnormal (ANR) state.
The PGC has failed.

(PGC), page 29-494
PROTNA PGC OOS - not available for Redundancy for the mate PGC has The PGC has been commanded out of
protection been lost because the PGC is in an service using the ED-EQPT command
out-of-service (OOS) state. (a transition from IS-NR-ACT/STBY to
OOS-NR).

(PGC), page 29-494.
Page 29-482 7/07 76.5500/29, Rev R

Table 5.5 Port Group Controller Module (PGC) Alarm Messages (Continued)
database. Use RTRV-REVTBL Go to Port Group Controller Module
command to view the system (PGC), page 29-494.
76.5500/13.
REVLVL PGC (81.5512A) on an OC3/OC12 An 81.5512A PGC module has been If the PGC module is 81.5512A and it is
shelf must be Rev G or greater inserted on an OC3/OC12 shelf, but inserted on an OC3/OC12 shelf, the
the revision level of the module is not revision level of the module must be
Rev G or greater. Rev. G or greater.

(PGC), page 29-494.
76.5500/29, Rev R 7/07 Page 29-483

Time Slot Interchange Module (TSI) Alarm Messages

5.13 In order to troubleshoot the alarm message(s) received for a faulted TSI,
messages that can be generated for an TSI. The second column lists a description
Table 5.6 Time Slot Interchange Module Alarm Messages

CONTCOM Loss of LAN communication from There is no LAN communication The communications channel between the
GC-A to TSI from GC-A to the TSI. PGC and the TSI is broken.
Go to Time Slot Interchange Module (TSI),

page 29-506, to troubleshoot the TSI, or
go to Port Group Controller Module (PGC),
page 29-494, to troubleshoot the PGC.
CONTCOM Loss of LAN communication from There is no LAN communication The communications channel between the
GC-B to TSI from GC-B to the TSI. PGC and the TSI is broken.

TSI. been disconnected.

page 29-506.
TSI. been disconnected.

page 29-506.
INT Cable or Internal failure - PT at port Either the SDF48 cable or the PT is There is a problem with the SDF48 cable,
X where X is the port number. defected. such as a dirty or broken cable, or there is
an internal failure with the PT.

page 29-506, or go to Pluggable
Transceiver (PT), page 29-835.
INT Card Removed The PGC has either detected the Either the TSI is missing from the port shelf
absence of the TSI or or it is not properly seated within the port
communications with it have failed. shelf.
NOTE: Continuous "Card Removed"
messages with "Module Inserted"
messages for specific revision level TSIs
indicates a loss of SDF clocking possibly
resulting from a bad NTDM or ESM.

page 29-506.
Page 29-484 7/07 76.5500/29, Rev R

Table 5.6 Time Slot Interchange Module Alarm Messages (Continued)

INT Connection memory failed to The Connection Management Mismatches were detected on the TSI for
compare with database Content Integrity (CMCI) audit audited network side. A most likely cause
detected mismatches in the is that a change to the software database
database for the TSI that was was not correctly propagated to the TSI
audited. hardware.

page 29-506.
INT Connection Memory failure There is a failure in reading or Defective TSI module.
writing a connection through the TSI.
page 29-506.
INT EEPROM Failure The PGC has failed to read and Defective TSI module.
verify the EEPROMs on the
addressed TSI. The EEPROMs on Go to Time Slot Interchange Module (TSI),
the TSI are read upon initialization of page 29-506.
the PGC and upon TSI insertion.
INT Failed diagnostics The TSI has failed one of its internal One or more of the following has occurred:
diagnostics either on power up or by - Failed EEPROM test.
entering a TL1 diagnostic command. - Failed TSI framing test.
- Failed TSI device connection memory
test.
- Failed restore of connection memory test.
For a TSI96P, one or more of the following

has occurred:
- Failed PIMDAG FPGA check
- Faulty input to TSI96P at SFP48 fiber
optic cables
- Internal Loss of Frame
- Internal parity error

page 29-506.
INT Incoming SDF failure from ESM The ICOMM audit of the path from a Defective TSI or ESM module. The fiber
(possible cable fault) Stage 4 ESM to the reporting Stage optic cable between the TSI and ESM
5 TSI has detected a failure. modules may be disconnected or faulty.

page 29-506, to troubleshoot the TSI, or to
End Stage Module (ESM), page 29-332, to
INT Internal Error The PGC has detected invalid One or more of the following has occurred:
communication responses from one - TSI has faulted.
or more devices on the TSI but no - PGC has faulted.
isolation is possible because of the - PCP bus on the shelf backplane has
state or absence of the standby GC. faulted.

76.5500/29, Rev R 7/07 Page 29-485


INT Internal Failure Circuitry internal to the TSI has One or more of the following has occurred:
failed. - A memory write or verify failure within the
connection management area.
- Audit of connection memory has detected
a failure.
- Y bit errors have been detected on the
Xmit side of the QMUX device.
- LOF occurred on the RCV side of the TSI
device.
- LOF has occurred on Xmit side of the TSI
device.
- LOF occurred on the Xmit side of the
QMUX device

page 29-506.
INT Internal failure detected - PT at port The Pluggable Transceiver in port X Go to Pluggable Transceiver (PT),
X where X is the port number. is faulted. page 29-835.
INT Internal SDF Loss Of Frame An LOF has been detected at the If the condition is received intermittently,
detected in receive direction SDF level in the receive path the TSI96P may be experiencing
between the QMUX chip and the TSI temporary framing problems.
chip. These chips are located on the
TSI11 module. The fault exists in the If the condition is constant, the TSI96P
port module to TSI direction. may be defective.

page 29-506.
INT Internal SDF Loss Of Frame An LOF has been detected at the If the condition is received intermittently,
detected in transmit direction SDF level in the transmit path the TSI96P may be experiencing
between the TSI chip and the QMUX temporary framing problems.
chip. These chips are located on the
TSI11 module. The fault exists in the If the condition is constant, the TSI96P
TSI to port module direction. may be defective.

page 29-506.
INT Internal SDF parity error detected at Constant parity error at the SDF Faulty TSI module.
QMUX from TSI level has been detected at the
QMUX chip from the TSI chip. Go to Time Slot Interchange Module (TSI),
page 29-506.
INT Internal SDF parity error detected at Constant parity error at the SDF Faulty TSI module.
TSI from QMUX level has been detected at the TSI
chip from the QMUX chip. Go to Time Slot Interchange Module (TSI),
page 29-506.
INT Internal signal degradation detected Parity errors have been detected in One or more of the following has occurred:
at ESM from TSI the receive path at the ESM coming - TSI is generating incorrect parity.
from the TSI (Stage 1 to Stage 2) - Input stage on the ESM is not detecting
module. correct parity from the TSI module.
- Excessive data errors in transmission
path between TSI and ESM—damaged
fiber optic cable.

Page 29-486 7/07 76.5500/29, Rev R


INT Internal signal degradation detected A constant rate of parity errors at the One or more of the following has occurred:
at TSI from ESM SDF level has been detected in the - ESM is generating incorrect parity.
transmit path at the TSI coming from - Input stage on the TSI is not detecting
the ESM (Stage 4 to Stage 5) correct parity from the ESM module.
module. - Excessive data errors in transmission
path between TSI and ESM—damaged
fiber optic cable.

INT Internal signal failure detected at A Loss of Frame (LOF) has been One or more of the following has occurred:
ESM from TSI detected at the SDF level in the - TSI module is losing frame.
receive path at the ESM coming - Input stage on ESM is not maintaining
from the TSI. framing.
damaged.

INT Internal signal failure detected at A Loss of Frame (LOF) has been One or more of the following has occurred:
TSI from ESM detected at the SDF level in the - TSI is losing framing.
receive path at the TSI module - Output stage on ESM is not maintaining
coming from the ESM module. framing.
damaged.

INT Internal TVT parity error detected at Constant parity error at the TVT Faulty TSI module.
TSI from QMUX level has been detected at the
QMUX chip from the TSI chip. Go to Time Slot Interchange Module (TSI),
page 29-506.
INT Loss of clock detected at both MIMs TSI detected SDF LOC at the MIMs. The TSI has lost its clock. Depending on
from TSI the configuration of the system, check the
NTDM, ESM, CCSM, and PAM. Go to one
of the following:
• Network Timing Distribution Module
(NTDM), page 29-292
• End Stage Module (ESM),
page 29-332
• Consolidated Core Switch Module
(CCSM), page 29-394
• Port Aggregation Module (PAM),
page 29-405
76.5500/29, Rev R 7/07 Page 29-487


INT Loss of SDF clock, TSI cannot A Loss of Frame (LOF) from the One or more of the following has occurred:
frame PAM PTx has been detected by the - Fiber optic cable is disconnected.
TSI module. - Fiber optic cable is damaged.
- ESM or TSI has failed.
- TSI is recovering from a Loss of Clock
due to framing problems.

INT Module not compatible with existing There is an incompatibility between Module either failed internal software
software the system software and the compatibility check or contains wrong
on-board memory (EEPROM) of a EEPROM version.
particular module. An additional
output to this error will indicate the Go to Time Slot Interchange Module (TSI),
particular module that failed. page 29-506.
INT Parity error (Constant) detected at Constant parity errors are being - Faulty TSI module.
input from ports received from port modules. - Fiber optic cable is damaged.

page 29-506.
INT PT Module inconsistent with The PT inserted in the port is not Go to Pluggable Transceiver (PT),
assigned type - PT at port X where designed to be used with the TSI. page 29-835, to insert the correct type of
X is the port number. PT.
INT PT Module removed - PT at port X The TSI detected that the PT Reseat the PT module at the affected port
where X is the port number. module is not in its slot. in the TSI module.

page 29-835.
INT QTVT parity error detected at Constant DS1 Quad TVT parity Either the port module(s) or TSI is
QMUX from ports errors have been detected at the defective.
QMUX from the ports.
go to Section 6, Troubleshooting the Port
Shelves, page 29-575, to troubleshoot the
port module(s).
INT SDF Loss of Clock detected at the SDF LOC was detected at the port Either the TSI or network is faulty.
port modules modules.
go to Section 3, Troubleshooting the
Network Complex, page 29-245, to
troubleshoot the network.
INT SDF Loss Of Frame detected at A TSI has detected an SDF Loss of Problem possible exists between the MM
input from ports Frame (LOF) coming from more and the TSI.
than one port module.
page 29-506, or Mapping Modules (MM),
page 29-794.
Page 29-488 7/07 76.5500/29, Rev R


INT SDF Loss of Frame detected at the SDF LOF was detected at the port Either the TSI or network is faulty.
port modules modules.
INT SDF Parity Errors detected at the SDF parity errors were detected at Either the TSI or network is faulty, or the
port modules the port modules. SDF cable is damaged.

INT SDF48 Loss of Frame detected at The TSI has detected an LOF on the One or more of the following has occurred:
fiber X where X is the fiber number. SDF48 cable. - TSI is losing framing.
- Output stage on PAM is not maintaining
framing.
damaged.

Port Aggregation Module (PAM),
page 29-405, to troubleshoot the PAM.
INT SDF48 Loss of Multi-Frame This termination has detected two One or more of the following has occurred:
detected at fiber X where X is the consecutive H4 values that do not - TSI is losing framing.
fiber number. agree with any part of the multiframe - Output stage on PAM is not maintaining
sequence, and it has declared a loss framing.
of multiframe (LOMF) defect. - Fiber optic cable or connectors are
damaged.

INT SDF48 Loss of Signal detected at A Loss of Signal has been declared Disconnected or broken cable at the TSI.
fiber X where X is the fiber number at a port on the TSI.
fiber.
INT SDF48 mismatch detected at fiber X An SDF48 cable is connected to the Either the SDF48 cables for port 1 and port
where X is the mismatched fiber (X wrong port. (The secondary AID of 2, or Copy A and Copy B, are reversed.
= 1 or 2). the alarm message lists the module
to which the cable is connected.)
INT SDF48 Parity Error detected at fiber SDF parity errors were detected at One or both of the following has occurred:
X where X is the fiber number the port. - The TSI is faulted.
- The PAM is faulted.

76.5500/29, Rev R 7/07 Page 29-489


INT SDF48 Yellow Frame at fiber X The PTx has declared a Yellow One or both of the following has occurred:
where X is the fiber number Frame on a fiber that is connected to - The TSI is faulted.
the TSI. - The PAM is faulted.

INT SDF48 Yellow Multi-Frame The PTx has declared a Yellow One or both of the following has occurred:
detected at fiber X where X is the Multi-Frame on a fiber that is - The TSI is faulted.
fiber number connected to the TSI. - The PAM is faulted.

INT Signature verification failure on A cross-connect was entered and The network entity flagged in the alarm
writing a connection the one-byte signature test pattern message is experiencing communication
was sent over the path. Signature difficulties over the specified path.
pattern has not been reproduced
correctly throughout the path. Go to Time Slot Interchange Module (TSI),
page 29-506.
INT TVT Parity Errors detected at the TVT parity errors were detected at Either the TSI or network is faulty.
port modules the port modules.
INT Y bit errors at XIN of 1/1 Qmux, TSI The TSI chip has detected errors in Either the TSI or Qmux chip on the TSI
cannot frame the “Y” bit from an SDF originating module is defective.
from the QMUX device: the QMUX
device cannot establish framing with Go to Time Slot Interchange Module (TSI),
the network. page 29-506.
INT Yellow alarm from ESS to TSI The TSI1 or TSI1D has declared a One or more of the following has occurred:
yellow alarm on the link from the - TSI is losing framing.
ESS. - Output stage on the ESS is not
maintaining framing.

page 29-506.
MEA Inconsistent with currently defined The TSI is inconsistent with the There is a database type mismatch on the
type currently defined type. TSI.

page 29-506.
MODINSRT Module inserted The module was removed, but is Module has been inserted in its slot on the
now in its slot on the shelf. shelf. No recovery necessary.
REVLVL Module rev level does not meet The revision of the TSI is Refer to Tellabs 5500 Software Release
minimum due to PT port X where X incompatible with the PT in the Document, 76.5500/16, for the correct
is the port number module. version of the TSI.
Replace the TSI.
Refer to Tellabs 5500 Maintenance,

76.5500/24.
Page 29-490 7/07 76.5500/29, Rev R


REVLVL Module revision level does not meet The revision level of the module This module is not supported by this
revision level requirements does not match the set of valid version of the software.
revision levels maintained in the
system database. Use Go to Time Slot Interchange Module (TSI),
RTRV-REVTBL command to view page 29-506.
the system database of valid module
Manual, 76.5500/13.
connected module is not in a normal the connected module. Possible causes:
state. - The module supporting the TSI is in the
process of resetting.
module.

page 29-506.
76.5500/29, Rev R 7/07 Page 29-491

Line Interface Module (LIM) Alarm Messages

5.14 In order to troubleshoot the alarm message(s) received for a faulted LIM,
messages that can be generated for a LIM.The second column lists a description
Table 5.7 Line Interface Module (LIM) Alarm Messages

INT LIM Removed Active PGC is unable to detect the Either the LIM has been physically
presence of the LIM. removed or it has faulted such that the
PGC unable to detect its presence.
Go to Line Interface Module (LIM),

page 29-559.
MEA Set LBO switch position to LONG This alarm message appears when The LBO has been physically switched to
the LBO switch on the back of a 3/1 Short on a LIM card operating on an
LIM card is not set to Long when STS-1E shelf.
operating on an STS-1E shelf.
page 29-559.
MEA Switch position inconsistent with This alarm message appears when Either the LBO has been physically
T3 database attribute EQLZ the LBO switch on the back of a 3/1 switched on the LIM card without changing
LIM card is not consistent with the the value in the database via the ED-T3
database’s EQLZ value for that card. command or the EQLZ parameter on an
The EQLZ parameter is specified in ENT-T3 or ED-T3 command has been
the ENT-T3 or ED-T3 commands. changed without setting the switch on the
LIM to the correct position.

page 29-559.
Page 29-492 7/07 76.5500/29, Rev R

Port Shelf Power Supply Module (PPS) Alarm Messages

5.15 In order to troubleshoot the alarm message(s) received for a faulted PPS,
messages that can be generated for an PPS. The second column lists a description
Table 5.8 Port Shelf Power Supply Module (PPS) Alarm Messages
INT Module removed A power supply module has been Power supply module has been
removed from the system. removed.
Go to Port Shelf Power Supply Module

(PPS), page 29-568.
INT Power supply module failed Diagnostic tests run on the power Faulty power supply or a loss of power
supply upon power up or insertion have due to the power switch on the
detected an internal error in the Breaker/Frame Alarm panel in the OFF
module. position.

(PPS), page 29-568.
PROTNA Power supply failed (ANR) - not There is an abnormal condition with the There is a problem with the power
available for protection power supply and the abnormal side supply and/or power supply module.
has lost power redundancy.
(PPS), page 29-568.
76.5500/29, Rev R 7/07 Page 29-493

Port Group Controller Module (PGC)

5.16 In this section, you will troubleshoot the faulted Port Group Controller
(PGC). You should have completed System Pre-Checks, page 29-479, and been
5.17 A spare PGC may be required in order to perform this procedure. Refer to

M ctag COMPLD

M ctag COMPLD

"PGC3-0241-A,EQPT:NR,MAN,NSA,05-08,06-07-12,NEND,,,\"GC LAN Miscabled - AC-x on PGC-x

LAN x\"

message: “Loss of shelf communication and traffic due
to power failure,” go to step 2.

message: "GC LAN Miscabled - AC-x on PGC-x LAN x"
(where x equals A or B), go to Section 2,
Troubleshooting the Administrative Complex,

message: “Loss of LAN communications on a PGCU,”
go to Time Slot Interchange Module (TSI), page 29-506.
__ 1.4 If the system response lists another PGC alarm

__ 2. Perform the following steps:

__ 2.1 If the breaker panel switch of the Port Shelf A side for
the alarmed PGC is OFF, flip it up to the ON position.
__ 2.2 If the breaker panel switch of the Port Shelf B side for
the alarmed PGC is OFF, flip it up to the ON position.
Page 29-494 7/07 76.5500/29, Rev R

__ 2.3 If you are troubleshooting an HDPS shelf, verify that the

power LEDs on all modules are green.
__ 2.3.2 If the LEDs are off or amber, go to

Section 11, Checking the Power to a
Shelf, page 29-1105.
__ 3. Verify that the module front panel power LED lights for both PPS-A
and PPS-B.
__ 3.1 If both LEDs do not light, go to Port Shelf Power Supply
Module (PPS), page 29-568.
__ 3.2 If both LEDs do light, go to step 4.
__ 4. Retrieve the state of the non-alarmed PGCs by entering the following

command:
RTRV-EQPT::PGCee-xxxx-z:ctag;
Where: ee = Shelf type being retrieved (1 for DS1 port shelf, 1D

for double-density DS1 port shelf, 3 for DS3 port
shelf, E for STS1E port shelf, O3 for OC-3 port
shelf, O12 for OC-12 port shelf, U for High Density
port shelf).
xxxx = First SDF on the port equipment shelf being
retrieved.
z = Non-alarmed PGC (A or B).
System response:
M ctag COMPLD

"PGC1-0009-B:TYPE=11:HWV=81.5512A RB,SN=KI6479242,DT=961023:PST=OOS-NR"

the nonalarmed PGC is out-of-service, normal

the nonalarmed PGC is in-service, normal, active
(IS-NR-ACT), go to step 7, page 29-497.

the nonalarmed PGC is anything other than what is
76.5500/29, Rev R 7/07 Page 29-495

__ 5. Edit the non-alarmed PGC in-service (IS) by entering the following

command:
ED-EQPT::PGCee-xxxx-z:ctag::::IS;

port shelf).
retrieved.
System response:
M ctag COMPLD
__ 6. Retrieve the present state of the non-alarmed PGC:


port shelf).
retrieved.
System response:
M ctag COMPLD

"PGC1-0009-A:TYPE=11:HWV=81.5512A RAP1,SN=HL1604851,DT=930721:PST=IS-NR-ACT"
"PGC1-0009-B:TYPE=11:HWV=81.5512B RB,SN=KI6479242,DT=961023:PST=IS-NR-STBY"

the nonalarmed PGC is in-service, normal, active

present state of the nonalarmed PGC is
not in-service, normal, active
(IS-NR-ACT), follow your company's
Page 29-496 7/07 76.5500/29, Rev R

__ 7. Retrieve the present state of the alarmed PGC by entering the

following command:

port shelf).
retrieved.
z = PGC in alarm (A or B).
System response:
M ctag COMPLD

__ 7.1 If the present state of the alarmed PGC is in-service,

abnormal, equipped (IS-ANR-EQ), go to step 8,
page 29-498.

page 29-498.
__ 7.3 If the present state of the alarmed PGC is

__ 7.4 If the present state of the alarmed PGCe is


out-of-service, normal (OOS-NR) go to step 24,
page 29-504.

normal, standby (IS-NR-STBY) go to step 26,
page 29-505.

76.5500/29, Rev R 7/07 Page 29-497

__ 8. Edit the alarmed PGC out-of-service (OOS) by entering the following

command:
ED-EQPT::PGCee-xxxx-z:ctag::::OOS;

port shelf).
retrieved.
Note: Module front panel LEDs light for approximately two minutes during normal
system behavior.
System response when command prompt confirmation (CPC) is off:

M ctag COMPLD

M ctag COMPLD
__ 9. Does the system generate an alarm CLR (clear) message for the
alarmed PGC?
Page 29-498 7/07 76.5500/29, Rev R

following command:

port shelf).
retrieved.
System response:
M ctag COMPLD

"PGC1-0009-A:TYPE=11:HWV=81.5512A RAP1,SN=HL1604851,DT=930721:PST=OOS-ANR-EQ"
"PGC1-0009-B:TYPE=11:HWV=81.5512B RB,SN=KI6479242,DT=961023:PST=OOS-ANR-UEQ"

(OOS-ANR-UEQ) go to step 11.

(OOS-ANR-EQ) go to step 16, page 29-501.

page 29-504.


page 29-501.

page 29-500.
76.5500/29, Rev R 7/07 Page 29-499


steps:
backplane.


backplane?


go to the next step.

troubleshooting.
__ 15. After a three minute module download, what is the front panel LED
__ 15.1 If the LEDs remain lit, go to step 16, page 29-501.
Page 29-500 7/07 76.5500/29, Rev R

__ 16. Diagnose the problem on the alarmed PGC by entering the following
command:
Note 1: The PGC must be out-of-service (OOS) and it must be equipped (EQ) in
order to perform diagnostics on it. However, if the PGC is unequipped
America).
normal behavior.
DGN-EQPT::PGCee-xxxx-z:ctag;

port shelf).
xxxx = First SDF on the port shelf being diagnosed.
z = Alarmed PGC (A or B).
System response:
M ctag COMPLD

"PGC1-1-A:PASS-1"
"PGC1-1-A:FAIL-0"

step 17.

step 23, page 29-503.
76.5500/29, Rev R 7/07 Page 29-501

__ 18. Diagnose the problem on the alarmed PGC by entering the following
command:
Note 1: The PGC must be out-of-service (OOS) and it must be equipped (EQ) in
order to perform diagnostics on it. However, if the PGC is unequipped
America).
normal behavior.
DGN-EQPT::PGCee-xxxx-z:ctag;

port shelf).
xxxx = First SDF on the port shelf being diagnosed.
System response:
M ctag COMPLD

"PGC1-1-A:PASS-1"
"PGC1-1-A:FAIL-0"

step 19.

step 23, page 29-503.
__ 19. Remove the alarmed PGC.

place.

steps:
backplane.

backplane?
Page 29-502 7/07 76.5500/29, Rev R



go to step 21.

troubleshooting.
following command:

port shelf).
xxxx = First SDF on the port shelf being retrieved.
System response:
M ctag COMPLD

"PGC1-0009-A:TYPE=11:HWV=81.5512A RAP1,SN=HL1604851,DT=930721:PST=OOS-NR"
"PGC1-0009-B:TYPE=11:HWV=81.5512B RB,SN=KI6479242,DT=961023:PST=IS-NR-ACT"

the alarmed PGC is not out-of-service, normal
(OOS-NR), choose one of the following options:
__ 23.1.1 If you have not reseated the module, go

__ 23.1.2 If you have already reseated the module,

follow your company's prescribed
North America).
76.5500/29, Rev R 7/07 Page 29-503


the alarmed PGC is out-of-service, normal (OOS-NR),
go to step 24.
__ 24. Edit the alarmed PGC in-service (IS) by entering the following
command:
ED-EQPT::PGCee-xxxx-z:ctag::::IS;

port shelf).
System response:
M ctag COMPLD
following command:

port shelf).
System response:
M ctag COMPLD


the alarmed PGC is not in-service, normal, standby
(IS-NR-STBY), follow your company's prescribed

the alarmed PGC is in-service, normal, standby
Page 29-504 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD


message, for example, Troubleshooting
the Network Complex.
__ 26.1.2 If no, go to step 27.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-505

Time Slot Interchange Module (TSI)

5.18 In this section, you will troubleshoot the alarmed Time Slot Interchange
Module (TSI). You should have completed System Pre-Checks, page 29-479, and
5.19 A spare TSI may be required in order to perform this procedure. Refer to
__ 1. Retrieve the present state of the TSIs by the following command:
RTRV-EQPT::TSIff-xxxx-A&&-B:ctag;
Where: ff = Shelf type being retrieved (11 for DS1 port shelf,
1D for double-density DS1 port shelf, 31 for DS3
port shelf, 31 for STS1E port shelf, O for OC-3 port
shelf, O for OC-12 port shelf, 96 for Universal port
shelf).
System response:
M ctag COMPLD

"TSI11-0001-A:TYPE=11:HWV=81.5516RA,SN=ELXXXXXXXX,DT=900825,ALMPF=6:PST=IS-NR"
"TSI11-0001-B:TYPE=11:HWV=81.5516RA,SN=ELXXXXXXXX,DT=900825,ALMPF=6:PST=OOS-NR"

the non-alarmed TSI is in-service, normal (IS-NR),

alarmed TSI is out-of-service, normal

alarmed TSI is abnormal (ANR), go to

the non-alarmed TSI is not in-service, normal (IS-NR),
Page 29-506 7/07 76.5500/29, Rev R

__ 2. Edit the alarmed TSI in-service (IS) by entering the following

command:
ED-EQPT::TSIff-xxxx-z:ctag::::IS;
shelf).
xxxx = First SDF on the port shelf.
z = A or B, whichever TSI copy is in alarm.
System response:
M ctag COMPLD
__ 3. Retrieve the present state of the alarmed TSI by entering the following
command:
RTRV-EQPT::TSIff-xxxx-y:ctag;
shelf).
y = A or B, whichever TSI copy is in alarm.
System response:
M ctag COMPLD

"TSI11-0001-B:TYPE=11:HWV=81.5516 RA, SN=ELXXXXXXXX,DT=900825,ALMPF=6:PST=IS-NR"

the alarmed TSI is in-service, normal (IS-NR), go to step
100, page 29-556.

the alarmed TSI is not in-service, normal (IS-NR), go to
76.5500/29, Rev R 7/07 Page 29-507

__ 4. Edit the alarmed TSI out-of-service (OOS) by entering the following

command:
ED-EQPT::TSIff-xxxx-z:ctag::::OOS;
shelf).
M ctag COMPLD

M ctag COMPLD

command:
RTRV-EQPT::TSIff-xxxx-z:ctag;
shelf).
System response:
M ctag COMPLD

"TSI1D-0001-B::HWV=81.5516DD RA,SN=EL02103731,DT=910507,ALMPF=99:PST=OOS-NR"
__ 5.1 Verify that the alarmed TSI is out-of-service (OOS).
Page 29-508 7/07 76.5500/29, Rev R


command:
System response:
M ctag RTRV

Hybrid Core Switch:


__ 7. Based on the alarm condition of the NCs, proceed accordingly.

Section 3, Troubleshooting the Network Complex,
page 29-245.
__ 7.2 If only the NC associated with the alarmed TSI is

page 29-510.
behavior.
76.5500/29, Rev R 7/07 Page 29-509

Caution:

command:

M ctag COMPLD

M ctag COMPLD



Caution:
Page 29-510 7/07 76.5500/29, Rev R

__ 9. Edit either the alarmed NC or CCSS out-of-service (OOS) by entering

one of the following commands:
__ 9.1 Edit the alarmed NC OOS by entering the following
command:
System response:
M ctag COMPLD




command:
System response:
M ctag COMPLD
__ 11.1 Follow your company's prescribed procedures for

76.5500/29, Rev R 7/07 Page 29-511

command:
System response:
M ctag COMPLD

Hybrid Core Switch:



page 29-512.

1.800.443.5555 (North America) or 1.630.798.7070
__ 13. Visually verify that the alarmed TSI module is present in the slot.
page 29-513.

page 29-553.
Page 29-512 7/07 76.5500/29, Rev R

__ 14. Diagnose the problem on the alarmed TSI by entering the following
command:
Note 1: In order to perform diagnostics on the TSI module, the supporting PGC
must be in-service, normal, the associated network (NC) must be
out-of-service, the PM(s) must not be listening to associated network,
and the TSI must be equipped.
normal behavior.
DGN-EQPT::TSIff-xxxx-z:ctag::,ITER=3;
shelf).
System response:
M ctag COMPLD

"TSI11-0121-A:PASS-2"
"TSI11-0121-A:FAIL-1,,,dgn_code"

PORT1:TYPE=SDF48:HWV=81.SDF48SR1131S_RA,SN=P8B07F7,DT=050906,CLEI=T3C5CCDAAA,
PORT2:TYPE=SDF48:HWV=81.SDF48SR1131S_RA,SN=P8B07F5,DT=050906,CLEI=T3C5CCDAAA,PTV
ENDOR=FINISAR CORP.,PTVENDORPN=FTRJ1321P1BTL
;
Where:
step 15.

76.5500/29, Rev R 7/07 Page 29-513

__ 16. Diagnose the problem on the alarmed TSI by entering the following
command:
Note 1: In order to perform diagnostics on the TSI module, the supporting PGC
must be in-service, normal, the associated network (NC) must be
out-of-service, the PM(s) must not be listening to associated network,
and the TSI must be equipped.
normal behavior.
DGN-EQPT::TSIff-xxxx-z:ctag;
shelf).
System response:
M ctag COMPLD

"TSI11-0121-A:PASS-0"
"TSI11-0121-A:FAIL-1,,,dgn_code"

PORT1:TYPE=SDF48:HWV=81.SDF48SR1131S_RA,SN=P8B07F7,DT=050906,CLEI=T3C5CCDAAA,
PORT2:TYPE=SDF48:HWV=81.SDF48SR1131S_RA,SN=P8B07F5,DT=050906,CLEI=T3C5CCDAAA,PTVENDO
R=FINISAR CORP.,PTVENDORPN=FTRJ1321P1BTL
;
Where:

Page 29-514 7/07 76.5500/29, Rev R


__ 17.1 If you are troubleshooting a TSI96, go to Checking
High-Density SDF Fiber Cable Integrity, page 29-520.
__ 17.2 If you are troubleshooting a TSI96P, go to Checking

High-Density SDF Fiber Cable Integrity for TSI96P,
page 29-538.
__ 17.3 If you are troubleshooting a TSI other than a TSI96

module, continue to step 20, page 29-515.
__ 18. Remove the alarmed TSI.

__ 18.1 If you are removing a TSI96, disconnect the
intra-system fibers from the front of the TSI96 before
removing the module from the shelf. Go to step 94,
page 29-553.
__ 18.2 If you are removing a TSI96P, disconnect the two

intra-system fiber cables from the front of the TSI96P
before removing the module from the shelf. Go to step
94, page 29-553.
__ 20. Verify that the proper fiber shroud lights turn on in the slot for the
alarmed TSI. Refer to Figure 5.3, page 29-516, through Figure 5.6,
page 29-519.
__ 20.1 If the proper fiber shrouds are lit, go to step 94,
page 29-553.
__ 20.2 If the proper fiber shrouds are not lit, has the ESM been
replaced?
__ 20.2.1 If yes, the fiber cable will need to be

replaced. Follow your company's
__ 20.2.2 If no, reseat the TSI and proceed to End

Stage Module (ESM), page 29-332.
76.5500/29, Rev R 7/07 Page 29-515

Figure 5.3 Fiber Shroud Lights for the DS1 TSI
P
I
N
S
slot backplane
fiber shroud lights

for TSI11
fiber shroud

Page 29-516 7/07 76.5500/29, Rev R

Figure 5.4 Fiber Shroud Lights for the Double-Density DS1 TSI
P
I
N
S
slot backplane
fiber shroud
Lights for TSI1D
fiber shroud

76.5500/29, Rev R 7/07 Page 29-517

Figure 5.5 Fiber Shroud Lights for the DS3 and STS1 TSI
P
I
N
S
slot backplane

TSI31
fiber shroud

Page 29-518 7/07 76.5500/29, Rev R

Figure 5.6 Fiber Shroud Lights for the OC-3 or OC-12 TSI
P
I
N
S
slot backplane

TSIO
fiber shroud
= lights are on under

normal conditions
76.5500/29, Rev R 7/07 Page 29-519

Checking High-Density SDF Fiber Cable Integrity

5.20 Use an optical light source and an optical power meter to verify that light
passes from one end of the cable to the other through both fibers.
Laser 5.21 The 5500/5500S and associated optical test sets use semiconductor laser
sources that emit light energy into fiber or lightguide cables. The lasers emit
lightwaves within the infrared (invisible) wavelengths.
regulations. The 5500 complies with USA Code of Federal Regulations (CFR), Title
21, Subchapter J, Part 1040.10, Performance Standards for Light-Emitting
Products, as a class 1 laser product.
Safety Precautions 5.24 Only qualified technicians who are knowledgeable and trained in optical
safety hazards can operate, maintain, install, and service the 5500.
DANGER:
viewing aids. For example, fiberscopes and magnifying glasses must be
DANGER:
DANGER:
to be examined
Page 29-520 7/07 76.5500/29, Rev R

5.26 The optical sources for the 5500 include the following semiconductor
lasers. The laser classification is the USA Center for Devices and Radiological
Health (CDRH) title 21, Code of Federal Regulations (CFR) Chapter 1, Subchapter
J, Parts 1040.1.
Optical Fiber Handling 5.27 Optical fibers can break into small glass fragments during handling. These
DANGER:
attention at once.
5.28 To perform procedures other than those specified in the 5500/5500S

documents can result in hazardous radiation exposure.
fiber:

end.


times.

76.5500/29, Rev R 7/07 Page 29-521

5.30 If you are troubleshooting high-density SDF fiber cables for a TSI96,
proceed to Checking High-Density SDF Fiber Cable Integrity for TSI96,
page 29-522.
5.31 If you are troubleshooting high-density SDF fiber cables for a TSI96P,
proceed to Checking High-Density SDF Fiber Cable Integrity for TSI96P,
page 29-538.
Checking High-Density SDF Fiber Cable Integrity for TSI96

__ 1. Choose one of the following options, based on the alarm message you
received.
__ 1.1 If the following alarm message is received, go to step 2,
page 29-522.

TSI from ESM\",ESM-0161-A:,NIMAN"
__ 1.2 If the following alarm message is received, go to step

25, page 29-531.

ESM from TSI\",ESM-0193-A:,NIMAN"
Checking TSI Receive Fibers __ 2. Retrieve the system timing to verify the inhibit status and the preferred
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
Page 29-522 7/07 76.5500/29, Rev R


1.800.443.5555 (North America) or 1.630.798.7070


analysis.
commands:

System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV
76.5500/29, Rev R 7/07 Page 29-523

__ 3.2 If you are troubleshooting TSI96-B, verify that

ADATA=OK and ACLK=OK. If you are troubleshooting
TSI96-A, verify that BDATA=OK and BCLK=OK. If any
modules are inhibited from the network, refer to
Troubleshooting the Network Complex, page 29-245, or
Troubleshooting Consolidated Core Switch Shelf
Equipment, page 29-363.
__ 4. Retrieve the state of the TSI96s by entering the following command:

System response:
M ctag COMPLD

__ 4.1 Determine which TSI96 is abnormal (ANR).
__ 4.2 If the abnormal TSI is in-service (IS), proceed to step 5,

page 29-524. If the abnormal TSI is out-of-service
__ 5. Edit the abnormal TSI96 out-of-service by entering the following

command:

System response:
M ctag COMPLD

at TSI from ESM\""
__ 6. Retrieve the state of the abnormal TSI96 by entering the following

command:

System response:
M ctag COMPLD

__ 6.1 Verify from the system response that the TSI96 is

Page 29-524 7/07 76.5500/29, Rev R

Caution:

command:

M ctag COMPLD

M ctag COMPLD




System response:
M ctag COMPLD

"NC-B::SIZE=256,EFSIZE=256,ESMSIZE=256,MAP=CMM,ALMPF=99:PST=OOS-NR"
Hybrid Core Switch:



__ 8.2 If the NC supporting the alarmed TSI is out-of-service

76.5500/29, Rev R 7/07 Page 29-525


System response:
M ctag COMPLD


System response:
M ctag COMPLD

Hybrid Core Switch:



__ 11. Remove the dual LC connector from the TSI96. Refer to Figure 5.7,
page 29-527.
Page 29-526 7/07 76.5500/29, Rev R

Figure 5.7 TSI Front Panel
81.5596
TSI96
POWER
ACTIVE
FAULT
XMT - 6
RCV - 6
XMT - 5
RCV - 5
XMT - 4
RCV - 4
intra-system fiber connectors
XMT - 3
RCV - 3
XMT - 2
RCV - 2
XMT - 1
RCV - 1
Note: The fiber connected to XMT - 1 and RCV -1 should be from the lowest sdf
ESMU in the trio of ESMUs for a given HDPS.
76.5500/29, Rev R 7/07 Page 29-527

__ 14. Verify the optical power reading meets requirements. Refer to

Table 5.9.

Table 5.9 Acceptable ESMU/TSI96 Optical Parameters

Short/Intermediate

(dBm)

(dBm)

(dBm)
(dBm)
TSI96 module.
__ 17.1 If the TSI fault clears within three minutes, go to step 98,
page 29-555.
__ 17.2 If the TSI fault does not clear within three minutes,
repeat steps 11 through 16 to check the receive cables
for all six ports on the TSI96 module.

page 29-515, to replace the TSI96
module.
Note: If the TSI96 module has already been replaced, the receive power levels
Page 29-528 7/07 76.5500/29, Rev R

Checking ESM Transmit __ 18. From the back of the ESMU in the Network Complex, remove the dual
Power Levels LC connector from the back of the ESMU. Refer to Figure 5.8.
Figure 5.8 ESMU Fiber Optic Adapter Location
ESMU fiber optic adapter
slot B
slot A
port on the ESMU for the opposite end of the failed fiber. Refer to
Table 5.10.
Table 5.10 ESMU Port Assignments

ESMU 3 ESMU 2 ESMU1
B Slot Port 6 Port 4 Port 2

A Slot Port 5 Port 3 Port 1
76.5500/29, Rev R 7/07 Page 29-529

Table 5.9, page 29-528.

power meter from the ESM transmit port and replace
the ESM.
__ 21.2.1 If the fault clears after replacing the ESM,

__ 21.2.2 If the fault does not clear, follow your

company’s prescribed procedures for
__ 22. Remove the LC connector from the ESM transmit port.

back of the ESMU.
page 29-555.
Page 29-530 7/07 76.5500/29, Rev R

Checking ESM Receive __ 25. Retrieve the system timing to verify the inhibit status and the preferred
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

1.800.443.5555 (North America) or 1.630.798.7070

analysis.
76.5500/29, Rev R 7/07 Page 29-531

commands:

System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV

Page 29-532 7/07 76.5500/29, Rev R

__ 27. Retrieve the state of the TSI96s by entering the following command:
System response:
M ctag COMPLD

__ 27.2 If the abnormal TSI96 is in-service (IS), go to step 28,

page 29-533.
__ 27.3 If the abnormal TSI is out-of-service (OOS), go to step

30, page 29-534.
__ 28. Edit the abnormal TSI96 out-of-service by entering the following

command:

System response:
M ctag COMPLD

at ESM from TSI\""
__ 29. Retrieve the state of the abnormal TSI96 by entering the following
command:

System response:
M ctag COMPLD

__ 29.1 Verify from the system response that the TSI96 is

76.5500/29, Rev R 7/07 Page 29-533

Caution:
command:

M ctag COMPLD

M ctag COMPLD



Page 29-534 7/07 76.5500/29, Rev R

Caution:

System response:
M ctag COMPLD

Hybrid Core Switch:





System response:
M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-535


System response:
M ctag COMPLD

Hybrid Core Switch:



__ 34. Remove the fiber optic adapter from the back of the ESMU. Refer to
Table 5.11.
page 29-536.

the dual LC fiber cable to the proper port on the back of
the ESMU. Go to step 41, page 29-537.
Table 5.11 Acceptable ESMU/TSI96 Optical Parameters

Short/Intermediate

(dBm)
(dBm)

(dBm)

(dBm)
Page 29-536 7/07 76.5500/29, Rev R

back of the ESMU.
page 29-555.
for all six ports on the ESMU.

requirements, replace the ESMU
following the module replacement
procedures in Tellabs 5500/5500S
Note: If the ESMU has already been replaced, the receive power levels are in
North America).
Checking TSI Transmit __ 41. Remove the dual LC connector from the TSI96 module. Refer to
__ 42. Connect the power meter to the transmit port on the TSI96 module for
the opposite end of the failed fiber. Refer to Table 5.12.
Table 5.12 ESMU Port Assignments

ESMU 3 ESMU 2 ESMU1
B Slot Port 6 Port 4 Port 2

A Slot Port 5 Port 3 Port 1

Table 5.11, page 29-536.

power meter from the TSI96 transmit port and replace
the TSI96. Go to step 18, page 29-515.
__ 45. Remove the LC connector from the TSI96 transmit port.

back of the TSI96 module.
76.5500/29, Rev R 7/07 Page 29-537


__ 47.1 If the TSI fault clears after the fibers are reinserted, go
__ 47.2 If the TSI fault does not clear, replace the fiber cable.
76.5500/7.
Checking High-Density SDF Fiber Cable Integrity for TSI96P

5.32 Perform the procedures in this section if one of the following alarm
messages is received.
• Loss of LAN communications from PAM to TSI
• Cable or Internal failure - PT at port X
• SDF48 Loss of Frame detected at fiber X
• SDF48 Loss of Multi-Frame alignment detected at fiber X
• SDF48 Parity Error detected at fiber X

• SDF48 Loss of Signal detected at fiber X
• SDF48 Yellow Frame at fiber X
• SDF48 Yellow Multi-Frame at fiber X
Page 29-538 7/07 76.5500/29, Rev R

Checking TSI96P Receive __ 48. Retrieve the system timing to verify the inhibit status and the preferred
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

1.800.443.5555 (North America) or 1.630.798.7070


analysis.
76.5500/29, Rev R 7/07 Page 29-539

commands:

System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV

Page 29-540 7/07 76.5500/29, Rev R

System response:
M ctag COMPLD

__ 50.2 If the abnormal TSI96 is in-service (IS), go to step 51,

page 29-541.
__ 50.3 If the abnormal TSI96 is out-of-service (OOS), go to

step 53, page 29-542.
__ 51. Edit the abnormal TSI96P out-of-service by entering the following

command:

System response:
M ctag COMPLD

"TSI96-0161-A:CL,INT,NSA,08-27,14-53-58,NEND:\"CLR - Loss of LAN communications from
PAM to TSI\""
__ 52. Retrieve the state of the abnormal TSI96P by entering the following
command:

System response:
M ctag COMPLD


76.5500/29, Rev R 7/07 Page 29-541

Caution:
command:

M ctag COMPLD

M ctag COMPLD




System response:
M ctag COMPLD

Hybrid Core Switch:




Page 29-542 7/07 76.5500/29, Rev R


System response:
M ctag COMPLD


System response:
M ctag RTRV
Followed by lines of data similar to the following samples:

Hybrid Core Switch:



__ 57. Remove the dual LC connector from the TSI96P. Refer to Figure 5.9,
page 29-544.
76.5500/29, Rev R 7/07 Page 29-543

Figure 5.9 55196 TSI96P Front Panel
81.55196
TSI96P
POWER
ACTIVE
FAULT
PT-2
PT-1
FLT SDF
XMT - 2
RCV - 2
XMT - 1 intra-system fiber connectors

RCV - 1
Note: The fiber connected to XMT - 1 and RCV -1 should be from the lowest SDF
PAM for a given CCSS.
Page 29-544 7/07 76.5500/29, Rev R


Table 5.13.

Table 5.13 Acceptable PAM/TSI96 Optical Parameters

Short/Intermediate

(dBm)

(dBm)

(dBm)
(dBm)
TSI96P module.
page 29-555.
for the two ports on the TSI96P module.

page 29-515, to replace the TSI96P
module.
Note: If the TSI96P module has already been replaced, the receive power levels
76.5500/29, Rev R 7/07 Page 29-545

Checking PAM Transmit __ 64. Remove the dual LC connector from the front of the PAM for the SDF
Power Levels fiber in question. Refer to Figure 5.10.
Figure 5.10 PAM LC Fiber Optic Connection
port on the PAM for the opposite end of the failed fiber.
Table 5.13, page 29-545.

power meter from the PAM transmit port and replace
the PTx. Refer to Pluggable Transceiver (PT),
page 29-835.
__ 68. Remove the LC connector from the transmit port on the PAM.
front of the PAM.
page 29-555.
Page 29-546 7/07 76.5500/29, Rev R

Checking PAM Receive __ 71. Retrieve the system timing to verify the inhibit status and the preferred
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

1.800.443.5555 (North America) or 1.630.798.7070

analysis.
76.5500/29, Rev R 7/07 Page 29-547

commands:

System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV

Page 29-548 7/07 76.5500/29, Rev R

Where: xxxx = SDF number for the TSI96P being retrieved.
System response:
M ctag COMPLD

__ 73.1 Determine which TSI96P is abnormal (ANR).
__ 73.2 If the abnormal TSI96P is in-service (IS), go to step 74,

page 29-549.
__ 73.3 If the abnormal TSI96P is out-of-service (OOS), go to

step 76, page 29-550.
__ 74. Edit the abnormal TSI96P out-of-service by entering the following

command:

System response:
M ctag COMPLD

at ESM from TSI\""
__ 75. Retrieve the state of the abnormal TSI96P by entering the following
command:

System response:
M ctag COMPLD


76.5500/29, Rev R 7/07 Page 29-549

Caution:
command:

M ctag COMPLD

M ctag COMPLD




System response:
M ctag COMPLD

Hybrid Core Switch:




Page 29-550 7/07 76.5500/29, Rev R

Caution:

System response:
M ctag COMPLD


System response:
M ctag COMPLD

Hybrid Core Switch:



__ 80. Remove the fiber optic LC connector from the front of the PAM. Refer
76.5500/29, Rev R 7/07 Page 29-551


Table 5.14.
page 29-552.

the dual LC fiber cable to the proper port on the front of
the PAM. Go to step 87, page 29-553.
Table 5.14 Acceptable PAM/TSI96P Optical Parameters

Short/Intermediate

(dBm)

(dBm)

(dBm)

(dBm)
front of the PAM.
page 29-555.
repeat steps 80, page 29-551 through 85, page 29-552
to check the receive cables for all eight ports on the
PAM.

requirements, replace the PTx on the
PAM. Refer to Pluggable Transceiver
(PT), page 29-835.
Note: If the PAM PTx has already been replaced, the receive power levels are in
North America).
Page 29-552 7/07 76.5500/29, Rev R

Checking TSI96P Transmit __ 87. Remove the dual LC connector from the TSI96P module. Refer to
__ 88. Connect the power meter to the transmit port on the TSI96P module
for the opposite end of the failed fiber.
Table 5.14, page 29-552.

power meter from the TSI96P module transmit port, and
replace the TSI96P. Go to step 18, page 29-515.
__ 91. Remove the LC connector from the transmit port on the TSI96P.
front of the TSI96P.
__ 93.1 If the TSI fault clears after the fibers are reinserted, go
__ 93.2 If the TSI fault does not clear, replace the fiber cable.
76.5500/7.

steps:
backplane.


backplane?


go to step 95.

troubleshooting.
76.5500/29, Rev R 7/07 Page 29-553

__ 96. Insert the module. Perform one of the steps below.

__ 96.1 If you are inserting a TSI96P, replace the two
intra-system fiber cables on the front of the TSI96P.
Note 1: After inserting the module, the module front panel LEDs light for
Note 2: System generates TSI alarm CLR messages during certain instances of
troubleshooting.
Note 3: System generates NC PROTNA ANR alarm CLR messages during

command:
Where: ff = Shelf type being retrieved (96 for High Density port
shelf)
y = A or B, whichever TSI is in alarm.
System response:
M ctag COMPLD

"TSI11-0001-B:TYPE=11:HWV=81.5516 RA, SN=ELXXXXXXXX,DT=900825,ALMPF=6:PST=OOS-NR"

the alarmed TSI is out-of-service, normal (OOS-NR), go
to step 98.

the alarmed TSI is in-service, normal (IS-NR), go to step
100, page 29-556.

the alarmed TSI is out-of-service, abnormal, equipped

the alarmed TSI96 is in-service, abnormal, equipped
(IS-ANR-EQ), go to End Stage Module (ESM),
page 29-332.
If the system response verifies that the present state of

the alarmed TSI96P is in-service, abnormal, equipped
(IS-ANR-EQ), go to Port Aggregation Module (PAM),
page 29-405.
Page 29-554 7/07 76.5500/29, Rev R


the alarmed TSI is anything other than what is listed
Finalizing Procedure __ 98. Edit the alarmed TSI in-service (IS) by entering the following
command:
ED-EQPT::TSIff-xxxx-z:ctag:::MODE=FRCD:IS;
shelf).
z = A or B, whichever TSI is in alarm.
System response:
M ctag COMPLD
__ 98.1 If the system does not generate a TSI alarm message,

__ 98.2 If the system generates a TSI alarm message, follow

command:
shelf).
y = A or B, whichever TSI is in alarm.
System response:
M ctag COMPLD

"TSI11-0001-B:TYPE=11:HWV=81.5516 RA, SN=ELXXXXXXXX,DT=900825,ALMPF=6:PST=IS-NR"
__ 99.1 Verify from the system response that the TSI is

76.5500/29, Rev R 7/07 Page 29-555



previously alarmed.
System response:
M ctag COMPLD

Hybrid Core Switch:





page 29-257.

command:
System response:
M ctag COMPLD
Page 29-556 7/07 76.5500/29, Rev R

system behavior.
command:
System response:
M ctag COMPLD

Hybrid Core Switch:





M ctag COMPLD

M ctag COMPLD


message.
76.5500/29, Rev R 7/07 Page 29-557



End of Procedure
Page 29-558 7/07 76.5500/29, Rev R

Line Interface Module (LIM)

5.33 In this section, you will troubleshoot the alarmed DS1 Line Interface
Module 1 (LIM1), the alarmed Double-density DS1 Line Interface Module 1
(LIM1D), and the alarmed DS3 or STS1 Line Interface Module 3 (LIM3). You
should have completed System Pre-Checks, page 29-479, and been directed to
this section from an alarm message table.
5.34 A spare LIM may be required in order to perform this procedure. Refer to
__ 1. Is the system experiencing a service-affecting problem?
__ 2. Is the port module associated with the alarmed LIM working properly?
__ 2.1 For a DS1 or Double-density DS1 PM, enter one of the
following commands:
RTRV-EQPT::PM1-xxxx-yy:ctag;
RTRV-EQPT::PM1D-xxxx-yy:ctag;
Where: xxxx = SDF number of the quadrant being retrieved.

yy = First DS1 serviced by the faulted PM.
.
__ 2.2 For a DS3 PM or STS-1 PM, enter one of the following
commands:
RTRV-EQPT::PM3-xxxx:ctag;
RTRV-EQPT::PME-xxxx:ctag;
Where: xxxx = SDF number of the faulted module.
System response:
M ctag COMPLD

"PM1-0009-5:TYPE=11:HWV=81.5514 RB,SN=FL0005886,DT=910627,ALMPF=99,PRTN=ALW,
PRTN_PORT=NONE,PRTN_TYPE=NULL:PST=IS-NR-ACT"
__ 2.2.1 If the present state of the port module is

normal (NR), go to step 3, page 29-560.
__ 2.2.2 If the present state of the port module is

abnormal (ANR), go to step 4,
page 29-560.
76.5500/29, Rev R 7/07 Page 29-559

__ 3. Retrieve the redundant port module associated with the alarmed LIM
to verify that it is working properly by entering the following command:
RTRV-EQPT::eeeee-xxxx:ctag;
Where: eeeee = Module type being retrieved (RPM1 for DS1 port
module, RPM1D for double-density DS1 port
module, RPM3 for DS3 port module, RPME for
STS1E port module).
xxxx = SDF number protected by the RPM.
System response:
M ctag COMPLD

"RPM1-0009:TYPE=11:HWV=81.5514 RB,SN=FL0005886,DT=910627,ALMPF=99,PRTN=ALW,
PRTN_PORT=PM1-0009-5,PRTN_TYPE=AUTO:PST=IS-NR-ACT"
__ 3.1 If abnormal (ANR), go to DS1 and Double-Density DS1

Port Module Alarm Messages, page 29-611.
__ 3.2 If in-service, normal, active (IS-NR-ACT) or in-service,

normal, standby (IS-NR-STBY), go to step 4,
page 29-560.
__ 4. Retrieve alarms to determine if there is a LIM alarm message by


M ctag COMPLD

M ctag COMPLD

"LIMx-0033,NEND:\" LIM Removed\":,ISLTD"
"LIMx-0033,NEND:\" Set LBO switch position to LONG\":,ISLTD"
"LIMx-0033,NEND:\" Switch position inconsistent with database attribute

EQLZ\":,ISLTD"
Where: x = LIM type (either 1, 1D, or 3).
__ 4.1 For a LIM1 or a LIM1D, go to step 5, page 29-561.
Page 29-560 7/07 76.5500/29, Rev R

__ 4.2 For a LIM3, choose one of the following options:
__ 4.2.1 If you received the \”LIM Removed\”

message, go to step 5.
__ 4.2.2 If you received the \”Set LBO switch

position to LONG\” message, go to step
7, page 29-564.
__ 4.2.3 If you received the \”Switch position

inconsistent with database attribute
EQLZ\” message, go to step 7,
page 29-564.
__ 5. Verify that the LIM is attached correctly and fully seated to its
associated port module. Refer to Figure 5.11, page 29-561, through
Figure 5.11 Locations of LIM1s on a DS1 Port Shelf (Rear View)

SLOT 37 36 35 34 33 32 31 30 29 28 27 26 25 24
ASSIGNMENTS
L L L L L L L L L L L L L L
I I I I I I I I I I I I I I
M M M M M M M M M M M M M M
1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
(PSNP)
(PSNP)
(TSI11)
M M M M M M M M M M M M M M (TSI11)
(GCM)
(GCM)
1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
L
SLOT I
M
ASSIGNMENTS 18 17 16 15 14 13 12 11 10 9 8 7 6 5 1
76.5500/29, Rev R 7/07 Page 29-561

Figure 5.12 DS1 Shelf Backplane SDF Numbering for LIM1s (Rear View)
RCV DS1 RCV DS1

17-22 P67 13-16 P66 7-12 P65
23-28 P68 1-6 P64

GND
P56 A IN A IN
P55 J8 J4
-48VB B IN B IN
J7 J3
A OUT A OUT
J6 J2
J9 J10
B OUT B OUT
J5 P28 P27 P26 P25 P24 P23 P22 P21 P20 P19 P18 P17 P16 P15 J1
P14 P13 P12 P11 P0 P9 P8 P7 P6 P5 P4 P3 P2 P1
P51 COPY B COPY A
GND
P54
P52 P50 P53
-48VA
23-28 P63 1-6 P59
17-22 P62 13-16 P61 7-12 P60

XMT DS1 XMT DS1
Call out is an example of

25
17
13
21 22
1
the numbering per
quadrant using the first
26
18
14
10
SDF quadrant
27
23
19
15
11
3
28
20
16
12
24
Figure 5.13 Locations of LIM1Ds on a DD-DS1 Port Shelf (Rear View)
slot assignments 37 36 35 34 33 32 31 30 29 28 27 26 25 24
5516DD TSI1D
5516DD TSI1D
5512A/B GCM
5512A/B GCM
5535 PSNP
5535 PSNP
slot assignments 18 17 16 15 14 13 12 11 10 9 8 7 6 5
LIM1D
Page 29-562 7/07 76.5500/29, Rev R

Figure 5.14 DD-DS1 Shelf Backplane SDF Numbering for LIM1Ds (Rear View)
J19 J20 J16 J15
J23 J27
J24 J28
J25 J29
J17 J18 J14 J13
J26 J30
J11 J12 J8 J7
P43 P44
P45 P46
J9 J10 J6 J5
28 24 20 16 12 8 4
SDF
27 23 19 15 11 7 3
even
26 22 18 14 10 6 2
25 21 17 13 9 5 1
Call out is an example of
the numbering per 28 24 20 16 12 8 4
quadrant using the first
SDF
SDF quadrant
27 23 19 15 11 7 3 odd
26 22 18 14 10 6 2
25 21 17 13 9 5 1
Figure 5.15 Locations of LIM3s on a DS3 Port Shelf (Rear View)

(TSI31/A)
(PSNP)
(PSNP)
(GCM)
(TSI31/A)
(GCM)
L L L L L L L L L L L L L L L L L L
I I I I I I I I I I I I I I I I I I
M M M M M M M M M M M M M M M M M M
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
SLOT
ASSIGNMENTS 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
76.5500/29, Rev R 7/07 Page 29-563



M ctag COMPLD

M ctag COMPLD


EQLZ\":,ISLTD"
__ 6.1 If there are no alarm conditions posted against the

faulted LIM, go to step 16, page 29-566.

LIM, replace the LIM and repeat this step.
__ 7. For a LIM3, choose one of the following options:

__ 7.1 If working on a DS3 facility, go to step 8, page 29-564.
__ 7.2 If working on a STS1 facility, go to step 14,

page 29-566.
__ 8. Retrieve the state of the T3 terminations by entering the following

command:
RTRV-T3::xxx:ctag;
Where: xxx = SDF of the T3 termination.
System response:
M ctag RTRV

"0049::OOSCDE=AIS,FMT=M23,EQLZ=1,GOS=99,ALM=ALW,ALMPF=1,XBIT=YELLOW,,AISTYPE=SS,
BERTYPE=BPV,PARITY=PATH,MAP=ASYNC,IDLECDE=IDLE,AISGEN=NAS:PST=IS-ANR"
Page 29-564 7/07 76.5500/29, Rev R

__ 8.1 Record the value of the EQLZ parameter:

____________
Table 5.15 Equalization (LBO) Setting Versus Cable Length

Cable Type Set Switch to Short (1) Set Switch to Long (2)
Lucent 728B 0 to 225 feet 226 to 450 feet
Lucent 734A 0 to 225 feet 226 to 450 feet
Lucent 734D 0 to 225 feet 226 to 450 feet
Lucent 735 0 to 125 feet 126 to 250 feet
Lucent 735A 0 to 115 feet 116 to 230 feet
Montrose 1288 0 to 109 feet 110 to 218 feet
KS19224L2 0 to 72 feet 73 to 144 feet
__ 9. Determine the actual length of the coax cable from the alarmed LIM to
the DSX or other network equipment.
__ 10. Compare the EQLZ parameter cable length to the actual cable length.
__ 10.1 If the EQLZ parameter cable length matches the actual
cable length, go to step 11.
__ 10.2 If the EQLZ parameter cable length does not match the
actual cable length, go to step 12, page 29-565.
__ 11. Locate the LBO switch on the back of the alarmed LIM and set the LBO
switch to the correct setting for the actual cable length.
__ 11.1 If EQLZ equals 1, set the LBO switch to SHORT.
__ 11.2 If EQLZ equals 2, set the LBO switch to LONG.
__ 11.3 Once the LBO switch is set, go to step 15, page 29-566.
__ 12. Edit the T3 termination so that the EQLZ parameter cable length
matches the actual cable length by entering the following command:
ED-T3::xxxx:ctag:::EQLZ=n,mode=FRCD;
Note: If prompted “Do you want to execute this command (Y or N),” press Y for
Yes.
Where: xxx = SDF of the T3 termination.

n = Correct EQLZ setting (1 or 2). See Table 5.15,
page 29-565.
76.5500/29, Rev R 7/07 Page 29-565

__ 13. Retrieve the state of the T3 terminations by entering the following

command:
RTRV-T3::xxxx:ctag;
Where: xxxx = SDF of the T3 termination.
System response:
M ctag RTRV

"0049::OOSCDE=AIS,FMT=M23,EQLZ=1,GOS=99,ALM=ALW,ALMPF=1,XBIT=YELLOW,,AISTYPE=SS,BERT
YPE=BPV,PARITY=PATH,MAP=ASYNC,IDLECDE=IDLE,AISGEN=NAS:PST=IS-ANR"
__ 13.1 Verify that the EQLZ is now set for the appropriate
length, and go to step 14.
__ 14. Locate the LBO switch on the back of the alarmed LIM and verify that
the switch is set to LONG.
__ 14.1 Once the LBO switch is set, go to step 15, page 29-566.


M ctag COMPLD

M ctag COMPLD


EQLZ\":,ISLTD"

faulted LIM3, go to step 16.

LIM3, make a note of the system response and follow
internal policy to have LIM replaced.
__ 16. Does the system response list another alarm message?

__ 16.2 If yes, go to the appropriate section of this manual to

Page 29-566 7/07 76.5500/29, Rev R



End of Procedure
76.5500/29, Rev R 7/07 Page 29-567

Port Shelf Power Supply Module (PPS)

5.35 In this section, you will troubleshoot the alarmed Port Shelf Power Supply
Module (PPS). You should have completed System Pre-Checks, page 29-479, and
5.36 A spare PPS may be required in order to perform this procedure. Refer to
__ 1. Retrieve the state of the PGCs for the shelf where the faulted PPS
module is located by entering the following command:
RTRV-EQPT::PGCee-xxxx:ctag;

shelf, O12 for OC-12 port shelf).
retrieved.
System response:
M ctag COMPLD

"PPS-0001-A::HWV=8X.5535,ALMPF=1:PST=NR"
"PPS-0001-B::,ALMPF=1:PST=ANR-UEQ"

the non-alarmed PPS is normal (NR), and the front
panel power LED is lit, choose one of the following:

present state of the alarmed PPS is
abnormal, equipped (ANR-EQ), go to

present state of the alarmed PPS is
abnormal, unequipped (ANR-UEQ), go to

__ 2. Visually verify that a module is present in the slot for the alarmed PPS.
PPS, go to step 4, page 29-570.

PPS, go to step 3.
Page 29-568 7/07 76.5500/29, Rev R

Warning:
Caution:
When turning OFF the breaker panel switch for an alarmed PPS, only turn off the
breaker panel switch for that module, either A or B, and not both breakers to the
shelf. Turning off both breakers to the shelf will cause loss of power to that shelf,
which in turn will cause an interruption in service.
PPS is either OFF or ON, perform one of the following:
__ 3.1 If the breaker panel switch for the alarmed PPS is OFF,
__ 3.2 If the breaker panel switch for the alarmed PPS is ON,
page 29-571.
76.5500/29, Rev R 7/07 Page 29-569

PPS is either OFF or ON, perform one of the following:
__ 4.1 If the breaker panel switch for the alarmed PPS is OFF,
flip it up to the ON position. Then go to step 6.
__ 4.2 If the breaker panel switch for the alarmed PPS is ON,
flip it down to the OFF position. Then go to step 5.
__ 5. Remove the alarmed PPS.

place. Then go to step 9, page 29-571.
__ 6. After a 30 second module initialization, what is the front panel LED

status of the PPS?
__ 6.1 If the LEDs remain lit, does the system generate a PPS
alarm CLR (clear) message?
Caution:
__ 7. Flip the breaker panel switch for the alarmed PPS to the OFF position
(flip switch down).
__ 8. Remove the alarmed PPS.
place.
Page 29-570 7/07 76.5500/29, Rev R


steps:
backplane.


backplane?


go to step 10.

troubleshooting.
Note 1: After inserting the module, the module front panel LEDs light for
Note 2: The AC shelves number bottom up with shelf number 1 at the bottom of
the rack and shelf number 4 at the top of the rack. Breakers A1 and B1
are for shelf number 1, Breakers A2 and B2 are for shelf number 2, and
so on.
__ 12. Flip the breaker panel switch for the alarmed PPS to the ON position
(flip switch up).
__ 13. After module initialization (which may take up to 30 seconds), what is
the front panel LED status of the PPS?
__ 13.1 If the LEDs remain lit, does the system generate a PPS
alarm CLR (clear) message?
__ 13.1.1 If no, go to step 14, page 29-572
76.5500/29, Rev R 7/07 Page 29-571

__ 14. Flip the breaker panel switch for the alarmed PPS to the OFF position
(flip switch down).
__ 14.1 Go to Replacing Parts in a Breaker/Frame Alarm Panel
(B/FAP), located in Tellabs 5500/5500S Replacement
Procedures, 76.5500/55.
__ 15. Retrieve the state of the PGCs for the shelf where the faulted PPS
module is located by entering the following command:

shelf, O12 for OC-12 port shelf).
retrieved.
System response:
M ctag COMPLD

"PPS-0001-A::HWV=8X.5535,ALMPF=1:PST=NR"
"PPS-0001-B::HWV=8X.5535,ALMPF=1:PST=NR"
of the alarmed PPS is normal (NR)?

North America).
Page 29-572 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD


message.
__ 16.1.2 If no, go to step 17.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-573

USER NOTES
Page 29-574 7/07 76.5500/29, Rev R

Troubleshooting Manual 6. Troubleshooting the Port Shelves
6. Troubleshooting the Port Shelves
6.01 This section contains procedures to troubleshoot the problem occurring on

• DS1 Port Module (PM)
• Double-Density DS1 PM
• DS3 PM
• Electrical Port Module (EPMX24)
• STS-1 PM
• Optical PMs (OC-3 PM, OC-12 PM, OPM3X8 PM, OPM12X4 PM,
High Density OPM48 PM)
• Redundant Port Module (RPM)
• Redundant Electrical Port Module (REPM)
• Mapping Modules (MM)
• Redundant Mapping Modules (RMM)
• Mapping Interface Module (MIM)
• Circuit Cell Packet Module (Abis/ATM) (CCPMA)
• Pluggable Transceiver (PT)
• Fan Tray Module
6.02 When troubleshooting the modules on the port shelves, always check for
port shelves.
troubleshooting the modules on the port shelves. Refer to Status of the LEDs on a
is not certain, the OPR-EQPT-LED command can be used to locate the
module.The module locator application allows you to flash the red fault LED on a
specific port or network module to help locate it. When using the OPR-EQPT-LED
6.05 The OPR-EQPT-LED command cannot be used to locate a faulted fan tray
module.
76.5500/29, Rev R 7/07 Page 29-575

6. Troubleshooting the Port Shelves Troubleshooting Manual
6.07 Follow this precaution when using the system:
Warning:
6.09 Also, more than one type of related spare module can be used within some
types of port shelves. For example, 81.5514 and 81.5514A type port modules can
be used within the same Protection Group in a standard DS1 Port Shelf. For
example, if both 81.5514 and 81.5514A DS1 Port Modules are within any of the
four Protection Groups in a DS1 shelf, an 81.5514A must be in the RPM slot in that
Protection Group. The 5514 does not have all functions of the 5514A, so a 5514
cannot be used as the RPM in a Protection Group in which both 5514s and 5514As
are present. Refer to Table 6.1, page 29-576 to verify the correct type of port
module needed to replace the faulted module.
6.10 Use of proper port modules as RPMs applies only to port modules with
alternate types: the DS1, DS3, STS-1E, and Mapping Modules. Double Density
DS1, OC-3, and OC-12 port modules currently have no alternate types, so they
may always back each other up.
Table 6.1 General Port Module Type Protection Table

RPM Type Can Support the Following Port Module Type(s) in a Protection Group
81.5514 81.5514
81.5514A 81.5514 81.5514A

81.5517 81.5517
81.5517A 81.5517 81.5517A
81.5517B 81.5517B
82.5517A 81.5517 81.5517A 81.5517B 82.5517A
81.5598 81.5598
1
81.5520 81.5520
1
82.5520 81.5520 82.5520 82.5520FE
Page 29-576 7/07 76.5500/29, Rev R

Table 6.1 General Port Module Type Protection Table (Continued)

RPM Type Can Support the Following Port Module Type(s) in a Protection Group
1
82.5520FE 81.5520 82.5520 82.5520FE
1
81.5520T 81.5520 82.5520 82.5520FE 815520T
81.5544 81.5544 81.5545
81.5544A 81.5544 81.5544A 81.5544B 81.5544T 81.5545

81.5545A 81.5545B 81.5545T
81.5544B 81.5544B 81.5545B

81.5544T 81.5544 81.5544B 81.5544T 81.5545
81.5545B 81.5545T
81.5545 81.5544 81.5545
81.5545A 81.5544 81.5544A 81.5544B 81.5544T 81.5545

81.5545A 81.5545B 81.5545T
81.5545B 81.5544B 81.5545B

81.5545T 81.5544 81.5544B 81.5544T 81.5545
81.5545B 81.5545T
81.5592A/B 81.5592A/B
81.5593A/B 81.5593A/B
81.5594B 81.5594B
81.5595A 81.5595A
81.5595E 81.5595E
81.5595V 81.5595V
81.5595VE 81.5595VE
81.5596NB 81.5596NB
81.5597E 81.5597E
81.5599A 81.5599A
1. If different types of STS-1E port modules are mixed within the same Protection Group, use an 82.5520, 82.5520FE,
or an 81.5520T as the redundant port module if either Enhanced PDI is running or PDI is in OFF mode. If Regular PDI
is running, use any of the following as the redundant port module: 81.5520, 82.5520, 82.5520FE, or 81.5520T. However
the General Port Module Type Protection Table must still be followed. Refer to the RTRV-EQPT::NE command in
Tellabs 5500/5500S Command Reference Manual, 76.5500/13, for more information.
76.5500/29, Rev R 7/07 Page 29-577


6.11 Figures 6.1 through Figure 6.26, page 29-607, are for reference only. Use
these figures as an aid in troubleshooting the alarmed modules on the port shelves.
DS1 Port Module LEDs Figure 6.1 DS1 Port Module LEDs
PM11
red 1
red 2
red 3
red 4
active
fault
Port Module 1 (PM1) in normal state

(active LED is ON)
Page 29-578 7/07 76.5500/29, Rev R

Double-Density DS1 Port Figure 6.2 Double-Density DS1 Port Module LEDs
Module LEDs
PM1D
red upper
3
red lower
3
active
fault
Double-density Port Module 1 (PM1D) in normal

state (active LED is ON)
76.5500/29, Rev R 7/07 Page 29-579

DS3 Port Module LEDs Figure 6.3 DS3 Port Module LEDs
PM31
red
active
fault
Port Module 3 (PM3) in normal state

(active LED is ON)
Page 29-580 7/07 76.5500/29, Rev R

EPMX24
Electrical Port Module LEDs Figure 6.4 Electrical Port Module LEDs
power
active
fault
Electrical Port Module (EPMX24) in

normal state (active LED and Power
LED are ON)
76.5500/29, Rev R 7/07 Page 29-581

STS-1E Port Module LEDs Figure 6.5 STS-1E Port Module LEDs
PME
red
active
fault
STS-1E Port Module (PME) in normal

state (active LED is ON)
Table 6.2 Status of Port Module LEDs
Status of
LEDs Meaning Notes
All ON a) Not downloading data to this module from GCM. Usually a temporary state that occurs during module
b) There is power to shelf, but it is not provisioned. or system initialization.
c) At power up—module is running
self-diagnostics. A red signal LED ON means there is a loss of signal
(LOS) for each signal. This also registers a “Red
Alarm” message.
Red LED is ON, Module is in normal state, but there may be no signal input to Alarmed PM (red ON, active ON) - if all PM lights
Active ON, the module (there is a red alarm message on the incoming OFF, RPM shows both red and active LEDs ON.
Fault OFF signal).
Red LED is ON, The following conditions are in effect: This condition depends on whether the switch to
Active OFF, The module switched to redundant module. See Note. RPM was manual or auto/forced. With a switch to
Fault OFF The red LED indicates that there may be no signal input to RPM, the PM lights are OFF and RPM LEDs take on
the module (red alarm). the status that the PM had.
Page 29-582 7/07 76.5500/29, Rev R

Table 6.2 Status of Port Module LEDs (Continued)
Red LED is ON, a) Faulted or failed module. 1) Both the active and fault LEDs light when the
Active OFF, b) Incoming signal has a problem and module thinks it failed, module is downloading information. The fault LED is
Fault ON so it switches to protection/RPM. See Notes 1 and 2. OFF when it is finished downloading.
c) Redundant module in use or abnormal (ANR). 2) This state also occurs if the module was unable to
d) Bent pin(s) on backplane connector. switch to the RPM because the RPM is already
carrying traffic.
All OFF a) Out-of-service (OOS).

b) No power, out of slot, breaker off, bent pin(s) on backplane
connector.
c) If the RPM is on STBY, all LEDs OFF.
d) PM switched to Protection (PST=IS-NR-STBY).
Red LED is OFF a) Faulted or failed module.

Active ON, b) Bent pin(s) on backplane connector.
Fault ON
Red LED is OFF Normal, in-service, active state (IS).

Active ON,
Fault OFF
Red LED is OFF a) Faulted or failed module.

Active OFF, b) While downloading information.
Fault ON c) Bent pin(s) on backplane connector.
76.5500/29, Rev R 7/07 Page 29-583

OC-3 Port Module LEDs Figure 6.6 OC-3 Port Module LEDs
OC3
red
active
fault
OC-3 Optical Port Module 3 (OPM3) in

normal state (active LED is ON)
OC-12 Port Module LEDs Figure 6.7 OC-12 Port Module LEDs
OPM12
red
active
fault
OC-12 Optical Port Module (OPM12) in

normal state (active LED is ON)
Page 29-584 7/07 76.5500/29, Rev R

Table 6.3 Status of OC-3 and OC-12 Port Module LEDs

All ON a) Downloading (fault light flashes occasionally). Usually a temporary state that occurs during module
b) Waiting to receive download (OOS problem with or system initialization.
another PGCO or TSIO module).
Red LED is ON, Module is in-service, normal (IS-NR) and also either: Clean connectors and check signal.
Active ON, a) Loss of signal.
Fault OFF b) Optical connectors are not clean.
Red LED is ON, The following conditions are in effect: Clean connectors and check signal.
Active OFF, Module is out-of-service (OOS).
Fault OFF Problem with the signal.
Red LED is ON, The following conditions are in effect:

Active OFF, - Module is out-of-service, abnormal (OOS-ANR).
Fault ON - Failed or faulted module.
- Loss of signal.
All OFF a) Module is out-of-service (OOS).

b) No power, out of slot, breaker OFF, bent pin(s) on
Red LED is OFF a) Faulted or failed module (module is IS-ANR).

Fault ON
Red LED is OFF Normal, active state.

Active ON,
Fault OFF
Red LED is OFF a) Faulted or failed module is OOS-ANR, but signal is still
Active OFF, OK.
Fault ON b) Bent pin(s) on backplane connector.
76.5500/29, Rev R 7/07 Page 29-585

OPM12X4 Port Module LEDs Figure 6.8 OPM12X4 Port Module LEDs
OPM12X4
FAC/ALM
4
3
2
1
power
active
fault
Table 6.4 Status of OPM12X4 Port Module LEDs

All ON a) Downloading (fault light flashes occasionally). Usually a temporary state that occurs during module or
b) Waiting to receive download (OOS problem with system initialization.
another PGCU or TSI96 module)
Power LED is ON, Module is in-service, normal (IS-NR) and also either: Clean connectors and check signal.
Power LED is ON, The following conditions are in effect: Clean connectors and check signal.
Power LED is ON, The following conditions are in effect:

- Loss of signal.

Page 29-586 7/07 76.5500/29, Rev R

OPM3X8 Port Module LEDs Figure 6.9 OPM3X8 Port Module LEDs
OPM3X8
FAC/ALM
8
7
6
5
4
3
2
1
power
active
fault
OC-3X8 Optical Port Module (OPM3X8) in

normal state (active LED and power LED are
ON)
Table 6.5 Status of OPM3X8 Port Module LEDs

All ON a) Downloading (fault light flashes occasionally). Usually a temporary state that occurs during module
b) Waiting to receive download (OOS problem with or system initialization.
another PGCU or TSI96 module)
Power LED is ON, Module is in-service, normal (IS-NR) and also either: Clean connectors and check signal.
Power LED is ON, The following conditions are in effect: Clean connectors and check signal.

- Loss of signal.

76.5500/29, Rev R 7/07 Page 29-587

5594B High Density OPM48 Figure 6.10 High Density OPM48 Port Module LEDs
Module LEDs
81.5594B
OPM48
Pt-1
Flt Fac
power
active
fault
Caution:
Disconnect fiber cables
before fully removing
modules
CLEI BAR CODE
Page 29-588 7/07 76.5500/29, Rev R

Table 6.6 High Density OPM48 Port Module LEDs

power green Indicates the module is powered.
amber Indicates the module is operative, but a

fuse or feed has failed.
off Indicates the module has no power.
active green Indicates the module is active.
off Indicates the module is inactive.
fault off Indicates no fault exists.
red Indicates a module failure has occurred,

the module is booting up, or the module is
running a self-test.
Flt off No fault exists on the PT
red Indicates a faulty PT, or the wrong type of

PT has been inserted in module.
Fac off The facility is not active.
green The facility is active.
red Indicates a facility failure has occurred

(Loss of Signal or Loss of Frame).
76.5500/29, Rev R 7/07 Page 29-589

CCPMA LEDs Figure 6.11 CCPMA LEDs
CCPMA
81.5599A
REV. A
power
active
fault
MNG
link
activity
Page 29-590 7/07 76.5500/29, Rev R

Table 6.7 Status of Circuit Cell Packet Module (CCPMA) LEDs
Power ON, Normal, active state

Active ON,
Fault OFF
All ON The module is downloading information or waiting to Usually a temporary state that occurs during module
download. or system initialization.
Power ON, The following conditions are in effect:

Active OFF, a) Faulted or failed module.
Fault ON Module is also out-of-service (OOS) or standby (STBY).
b) Another possible cause is bent pin(s) on backplane
connector.
Power OFF, No power, not in slot, breakers OFF, bent pin(s) on

Active OFF, backplane connector.
Fault OFF
Management Port Link is established in the management port.

Link Green
Management Port Link is not established in the management port.

Link Red
Management Port Management port is active.

Activity Green
76.5500/29, Rev R 7/07 Page 29-591

Mapping Module LEDs Figure 6.12 Mapping Module (MM3) LEDs
MM3x
active
fault
Mapping Module (MM3x) in normal state (active

LED is ON)
Table 6.8 Status of Mapping Module (MM3) LEDs
Active ON, Normal, active state

Fault OFF
Active OFF, The following conditions are in effect:

Fault ON a) Faulted or failed module.
Module is also out-of-service (OOS) or standby (STBY).
connector.
Both OFF a) The MM3x is out-of-service (OOS).

b) No power, not in slot, breakers OFF, bent pin(s) on
Page 29-592 7/07 76.5500/29, Rev R

Mapping Module LEDs Figure 6.13 Mapping Module (MM24A) LEDs
MM24
power
active
fault
Mapping Module (MM24) in normal state (active

LED and power LED are ON)
Table 6.9 Status of Universal Mapping Module (MM24) LEDs

Fault OFF

connector.
Both OFF a) The MM24A is out-of-service (OOS).

76.5500/29, Rev R 7/07 Page 29-593

Ethernet Mapping Module Figure 6.14 Ethernet Mapping Module (MM24E) LEDs
LEDs
MM24E
power
active
fault
Ethernet Mapping Module (MM24E) in normal state (active

Table 6.10 Status of Universal Mapping Module (MM24E) LEDs

Fault OFF

connector.
Both OFF a) The MM24E is out-of-service (OOS).

Page 29-594 7/07 76.5500/29, Rev R

VQE Mapping Module LEDs Figure 6.15 VQE Mapping Module (MM24V) LEDs
MM24V
power
active
fault
VQE Mapping Module (MM24V) in normal state (active

Table 6.11 Status of VQE Mapping Module (MM24V) LEDs

Fault OFF

connector.
Both OFF a) The MM24V is out-of-service (OOS).

76.5500/29, Rev R 7/07 Page 29-595

VQE Extended Mapping Figure 6.16 VQE Extended Mapping Module (MM24VE) LEDs
Module LEDs
MM24VE
power
active
fault
VQE Extended Mapping Module (MM24VE) in normal state

(active LED and power LED are ON)
Table 6.12 Status of VQE Extended Mapping Module (MM24VE) LEDs

Fault OFF

connector.
Both OFF a) The MM24VE is out-of-service (OOS).

Page 29-596 7/07 76.5500/29, Rev R

Narrowband Mapping Figure 6.17 Narrowband Mapping Module (MM24NB) LEDs

Module LEDs
MM24NB
power
active
fault
Narrowband Mapping Module (MM24NB) in normal state

(active LED and power LED are ON)
Table 6.13 Status of Narrowband Mapping Module (MM24NB) LEDs

Fault OFF

connector.
Both OFF a) The MM24NB is out-of-service (OOS).

76.5500/29, Rev R 7/07 Page 29-597

Redundant Mapping Module Figure 6.18 Redundant Mapping Module Fault LEDs
LEDs
MM3x
active
fault
Redundant Mapping Module (RMM3) in its

normal state (both LEDs are OFF when acting
as the STBY module)
Table 6.14 Status of Redundant Mapping Module LEDs
Active ON, In active mode (IS-NR-ACT) when protecting a defective Check the status of the MM3x which it is protecting.
Fault OFF MM3x.
Active OFF, a) The following conditions are in effect:

Fault ON Faulted or failed module.
connector.
Both OFF Normal, standby state

a) The RMM3x is either out-of-service, normal (OOS-NR)
or in-service, normal, standby (IS-NR-STBY).
Page 29-598 7/07 76.5500/29, Rev R

Redundant Mapping Module Figure 6.19 Redundant Mapping Module (RMM24A) LEDs
LEDs
MM24A
power
active
fault
Redundant Mapping Module (RMM24A) in its

normal state (the active and fault LEDs are
OFF and the power LED is ON when acting
as the STBY module)
Table 6.15 Status of Redundant Mapping Module (RMM24A) Fault LEDs

Fault OFF MM24x.

connector.

a) The RMM24A is either out-of-service, normal
(OOS-NR) or in-service, normal, standby (IS-NR-STBY).
76.5500/29, Rev R 7/07 Page 29-599

Redundant Ethernet Mapping Figure 6.20 Redundant Ethernet Mapping Module (RMM24E) LEDs
Module LEDs
MM24E
power
active
fault
Redundant Ethernet Mapping Module

(RMM24E) in its normal state (the active and
fault LEDs are OFF and the power LED is ON
when acting as the STBY module)
Table 6.16 Status of Redundant Ethernet Mapping Module (RMM24E) Fault LEDs

Fault OFF MM24x.

connector.

a) The RMM24E is either out-of-service, normal
Page 29-600 7/07 76.5500/29, Rev R

Redundant VQE Mapping Figure 6.21 Redundant VQE Mapping Module (RMM24V) LEDs
Module LEDs
MM24V
power
active
fault
Redundant VQE Mapping Module (RMM24V)

in its normal state (the active and fault LEDs
are OFF and the power LED is ON when
acting as the STBY module)
Table 6.17 Status of Redundant VQE Mapping Module (RMM24V) Fault LEDs

Fault OFF MM24x.

connector.

a) The RMM24V is either out-of-service, normal
76.5500/29, Rev R 7/07 Page 29-601

Redundant VQE Extended Figure 6.22 Redundant VQE Extended Mapping Module (RMM24VE) LEDs
Mapping Module LEDs
MM24VE
power
active
fault
Redundant VQE Extended Mapping Module

(RMM24V) in its normal state (the active and
fault LEDs are OFF and the power LED is ON
when acting as the STBY module)
Table 6.18 Status of Redundant VQE Extended Mapping Module (RMM24VE) Fault LEDs

Fault OFF MM24x.

connector.

a) The RMM24VE is either out-of-service, normal
Page 29-602 7/07 76.5500/29, Rev R

Redundant Narrowband Figure 6.23 Redundant Narrowband Mapping Module (RMM24NB) LEDs
Mapping Module LEDs
MM24NB
power
active
fault
Redundant Narrowband Mapping Module

(RMM24NB) in its normal state (the active
and fault LEDs are OFF and the power LED is
ON when acting as the STBY module)
Table 6.19 Status of Redundant Narrowband Mapping Module (RMM24NB) Fault LEDs

Fault OFF MM24x.

connector.

a) The RMM24NB is either out-of-service, normal
76.5500/29, Rev R 7/07 Page 29-603

MIM96 LEDs Figure 6.24 Mapping Interface Module (MIM96) LEDs
MIM96
power
active
fault
Mapping Interface Module (MIM96) in

normal state (active LED and power LED
are ON)
Table 6.20 Mapping Interface Module (MIM96) LEDs

Status of
LEDs Meaning Notes
All ON a) Not downloading data to this module from GCM. Usually a temporary state that occurs during module or
b) There is power to shelf, but it is not provisioned. system initialization.
c) At power up—module is running self-diagnostics.
Power LED is ON, Module is in normal state.

Active ON,
Fault OFF

Active OFF, The module switched to standby MIM.
Fault OFF
Power LED is ON, a) Faulted or failed module. 1) Both the active and fault LEDs light when the module is
Active OFF, b) Incoming signal has a problem and module thinks downloading information. The fault LED is OFF when it is
Fault ON it failed, so it switches to standby MIM. finished downloading.
c) Standby module in use or abnormal (ANR). 2) This state also occurs if the module was unable to switch
d) Bent pin(s) on backplane connector. to the standby MIM because the standby MIM is already
carrying traffic.
Page 29-604 7/07 76.5500/29, Rev R

Table 6.20 Mapping Interface Module (MIM96) LEDs (Continued)

All OFF a) Out-of-service (OOS).
b) No power, out of slot, breaker off, bent pin(s) on
c) If the standby MIM is on STBY, all LEDs OFF.
d) MIM switched to Protection (PST=IS-NR-STBY).
Power LED is OFF a) Faulted or failed module.

Fault ON
76.5500/29, Rev R 7/07 Page 29-605

MIM96E LEDs Figure 6.25 Mapping Interface Module (MIM96E) LEDs
81.5597E
MIM96E
REV. A
power
active
fault
active
data
mng
mng
fac
Pt -4
Pt -3
Pt -2
Pt -1
Flt Fac
management port
RJ45
GbE facility port 4

GbE facility port 3

GbE facility port 2

GbE facility port 1

Page 29-606 7/07 76.5500/29, Rev R

Table 6.21 Mapping Interface Module (MIM96E) Fault LEDs

Status of
LEDs Meaning Notes
All ON a) Not downloading data to this module from GCM. Usually a temporary state that occurs during module or
b) There is power to shelf, but it is not provisioned. system initialization.
c) At power up—module is running self-diagnostics.
Power LED is ON, Module is in normal state.

Active ON,
Fault OFF
Power LED is ON, Module is out-of-service (OOS).

Active OFF,
Fault OFF
Power LED is ON, a) Faulted or failed module. 1) Both the active and fault LEDs light when the module is
Active OFF, b) Incoming signal has a problem. downloading information. The fault LED is OFF when it is
Fault ON c) Bent pin(s) on backplane connector. finished downloading.
Power LED is OFF a) Faulted or failed module.

Fault ON
Mng fac Red The link is down. (LOS on management port)
Pt 1 - 4 FAC Red The link is down. (LOS on facility GbE port)
Pt 1 - 4 FLT Red The pluggable transceiver is faulty. Indicates a faulty PT, or the wrong type of PT has been
inserted in module.
Fan Tray Module LEDs Figure 6.26 Fan Tray Module LEDs
power
fault
Table 6.22 Status of Fan Tray Module LEDs

Status of LEDs Meaning
Power ON, Normal, active state
Fault OFF
Both ON (flashing) Filter is missing.
Power OFF, The following conditions are in effect:

b) Another possible cause is bent pin(s) on backplane connector.
Both OFF No power, not in slot, breakers OFF.
76.5500/29, Rev R 7/07 Page 29-607


• For the Port Complex, go to Table 6.23, page 29-609.
• For the DS1 and DD DS1 port modules, go to Table 6.24,

page 29-611.
• For the DS3 port module, go to Table 6.25, page 29-615.
• For the EPM, go to Table 6.26, page 29-620.
• For the STS-1 port module, go to Table 6.27, page 29-624.
• For the redundant DS1 and DD DS1 port modules, go to Table 6.28,
page 29-629.
• For the redundant DS3 port module, go to Table 6.29, page 29-633.
• For the redundant EPM, go to Table 6.30, page 29-638.
• For the redundant STS-1 port module, go to Table 6.31, page 29-642.
• For the optical port modules (OC-3, OC-12, OPM3X8, OPM12X4, and
OPM48), go to Table 6.32, page 29-647.
• For the CCPMA, go to Table 6.33, page 29-651
• For the RCCPMA, go to Table 6.34, page 29-655
• For the MM, go to Table 6.35, page 29-659.
• For the redundant MM, go to Table 6.36, page 29-664.
• For the MIM, go to Table 6.37, page 29-669.
• For the Pluggable Transceiver (PT), go to Table 6.38, page 29-673.
• For the fan tray module, go to Table 6.39, page 29-675.
Page 29-608 7/07 76.5500/29, Rev R

Port Complex (PC) Alarm Messages

6.15 In order to troubleshoot the alarm message(s) received for the Port
Complex, use the following table. The first column of the table lists the possible
alarm messages that can be generated for the Port Complex. The second column
for the alarm.
Table 6.23 Port Complex Alarm Messages

CONTRDUP Protection switching unavailable - Loss of communication for a particular A PGC has transitioned to ANR and its
Loss of Communication PGC shelf. mate is not IS-NR-ACT.

(PGC), page 29-494, to troubleshoot the
PGC.
FANPWR Loss of power or processor failure on The fan tray has experienced a loss of - Loss of power; circuit breakers off or
fan tray power or a processor failure. blown (B/FAP or F/FAP).
- Faulty or failed fan tray module.
FEED Loss of power feed A to port shelf There is no power on feed A to the Power has been turned off, or feeds

page 29-1105.
FEED Loss of power feed B to port shelf There is no power on feed B to the Power has been turned off, or feeds

page 29-1105.
INT Missing module - potential air flow There is an empty slot on the port There is an open slot on the shelf.
problem shelf, which could result in an air flow
problem. Insert a filler module into the empty slot.
MAN Active module(s) are being used as An active module has been inserted There is a module with active circuitry
filler module(s) into a slot designated for a filler being used as a filler. Replace the active
module. module with the proper filler module for
that slot.
MAN Excessive length differential between The maximum length for SDF cables The delta between TSI-A cables and
SDF cable(s) to TSI A and SDF between TSI-A and/or TSI-B has been TSI-B cables has exceeded the
cable(s) to TSI B exceeded. maximum value.

TSI.
MAN Excessive length differential between The maximum length for SDF cables The delta between TSI-A cables has
SDF cables to TSI Copy A between TSI-A has been exceeded. exceeded the maximum value.

TSI.
76.5500/29, Rev R 7/07 Page 29-609

Table 6.23 Port Complex Alarm Messages (Continued)

MAN Excessive length differential between The maximum length for SDF cables The delta between TSI-B cables has
SDF cables to TSI Copy B between TSI-B has been exceeded. exceeded the maximum value.

TSI.
PWR Probable loss of shelf power failure When a port shelf is powered down by - Loss of power; circuit breakers off or
turning off both circuit breakers that blown (B/FAP or F/FAP).
supply power to the shelf. - Faulty or failed power supply module.

page 29-1105.

(PPS), page 29-568
SWVER Multiple CCPM NPU software Multiple versions of the CCPMA NPU This condition can occur after a partially
versions present software are present in the port shelf. successful targeted software upgrade.
Repeat the STA-TRGTSW-UPDATE
command or perform a system restore
to the previous program and database.
Page 29-610 7/07 76.5500/29, Rev R

DS1 and Double-Density DS1 Port Module Alarm Messages

6.16 In order to troubleshoot the alarm message(s) received for a faulted DS1
or Double-Density DS1 PM, use the following table. The first column of the table
lists the possible alarm messages that can be generated for a DS1 or
Double-Density DS1 PM. The second column lists a description of the alarm
Table 6.24 DS1 and Double-Density DS1 Port Module Alarm Messages
INHSWPR The switch to protection for the The INHSWPR condition is posted The condition is posted when an
entity is inhibited against an assigned port module when IHN-SWTOPROTN-EQPT::PM command
its protection switching capability has is executed on an entity and will be
been inhibited. cleared when the corresponding
ALW-SWTOPROTN-EQPT::PM
command is executed.
Go to Electrical Port Modules (DS1, DD

DS1, DS3, STS-1, or EPM), page 29-676.
INT DS1 Parity Error in Network Copy Reporting module has detected a One of these three has occurred:
A detected at PM mismatch between the parity of the - Bad port module incorrectly calculated
incoming signal from network copy A the parity.
and that of the outgoing port module. - Bad TSI.
- Bad fiber cable between ESM and TSI
modules.

DS1, DS3, STS-1, or EPM), page 29-676,
to troubleshoot the DS1 or DD DS1 port
modules.

page 29-332, to troubleshoot the ESM.

page 29-506, to troubleshoot the TSI.
INT DS1 Parity Error in Network Copy Reporting module has detected a One of these three has occurred:
B detected at PM mismatch between the parity of the - Bad port module incorrectly calculated
incoming signal from network copy B the parity.
modules.

to troubleshoot the DS1 or DD DS1 port
modules.


INT EEPROM Failure A failure to read the EEPROM Reporting port module has failed: it has
occurred. Go to Electrical Port Modules (DS1, DD
76.5500/29, Rev R 7/07 Page 29-611

Table 6.24 DS1 and Double-Density DS1 Port Module Alarm Messages (Continued)
INT Failed download Reporting port module requested The PGC did not provide the download
download 255 times without success because the port module was UEQ and
and could not be initialized. therefore incompatible. If the port module
was previously NR, it has probably failed,
and the PGC will fault it.

INT Failed module diagnostics Port module has failed self-diagnostics. Port module has failed.

INT Failed reprogram of network During an audit the GC has determined Either the port module or the GC has
status that the actual status of one of its port failed.
modules does not match what the GC
sees. Its attempt to reprogram the port Go to Electrical Port Modules (DS1, DD
module has failed. DS1, DS3, STS-1, or EPM), page 29-676.
INT Internal error An internal error has occurred because Port has experienced Rcv, Xmt, or Gbl
of a failure of a port module, but PGC errors, but there is no way to isolate or
cannot isolate or confirm the failure. confirm this. A port module has not
properly responded to UART
communication with the GC, but this
cannot be isolated.

INT Internal failure Reporting port module is reporting one One of the following is the likely cause:
of several possible errors. The RPM - Download is being requested while port
has checked the same incoming signal module is in normal (NR) state.
but is not able to confirm these errors. - Port module is experiencing internal
The RPM has switched to protected transmit or receive error.
mode. - Port module cannot communicate with its
GC.

INT Internal failure - audit response is The module did not pass internal audits. Failed or faulted module.
invalid The port module responds, but the
response indicates boot fault or Go to Electrical Port Modules (DS1, DD
unexpected activity (initializing, DS1, DS3, STS-1, or EPM), page 29-676.
download request, test in progress, or
halted).
INT Internal failure - global error - The module detected a global isolation Failed or faulted module.
isolation not available error.
INT Internal failure - global signal The module detected a global signal Failed or faulted module.
processing error processing error.
INT Internal failure - hardware logic The module has a hardware logic fault. Failed or faulted module.
fault
Page 29-612 7/07 76.5500/29, Rev R

INT Internal failure - loss of The module detected a loss of Failed or faulted module.
communication with module communication.
INT Internal failure - receive error - The module is detecting an error Failed or faulted module.
Ckt. Type DS1, Ckt No. = <xx> received from the DS1 signal.
(where xx = 0 to 3 or 0 to 7) (Ckt. No. = circuit number) Go to Electrical Port Modules (DS1, DD
INT Internal failure - transmit error - The module is detecting an error when Failed or faulted module.
Ckt. Type DS1, Ckt No. = <xx> transmitting to the DS1 signal.
(where xx = 0 to 3 or 0 to 7) (Ckt. No. = circuit number) Go to Electrical Port Modules (DS1, DD
INT Internal failure - unexpected The module experienced an Failed or faulted module.
download request unexpected request for download.
INT Internal signal degradation at TSI TSI Qmux device has detected constant If this alarm is declared against only one
from port module TVT (Tellabs virtual tributary) parity port module, then that module has
errors from a port module. At least one probably failed. If the alarm is declared
of the TVTs is experiencing parity against several port modules, the TSIs on
errors. that shelf are suspect.

to troubleshoot the port module, or go to
INT Module not compatible with This port module is not supported by the Module revision level is either lower or
existing software current software load. higher than the levels supported by the
current software version.

INT Network Copy Synchronization While trying to synchronize the network, The synchronization errors from the NC
Error Threshold Crossed the system had too many have exceeded the threshold.
synchronization errors.
INT Port Module Removed Active PGC has detected the absence Port module has been removed from its
of a port module. slot, or it has not responded to
communications from the PGC, or its
EEPROMS are corrupt or incompatible

INT System clock error in Network Reporting port module has detected a If a single port module reports this, it is
Copy A system clock error in network copy A. likely faulty. If several report this, then
either the stage 5 TSI or one of the
network elements is at fault.

76.5500/29, Rev R 7/07 Page 29-613

Copy B system clock error in network copy B. likely faulty. If several report this, then

MEA Inconsistent with currently The type of the reporting module differs Either the wrong module has been
assigned type from that assigned to this slot by the inserted or the wrong type assigned to that
ENT-EQPT command. slot.

MEA Inconsistent with type of During a reset of the shelf of the The type of the reporting module in this
associated RPM reporting module, a mismatched RPM protection group does not match that of its
was detected. assigned RPM.

RTRV-REVTBL command to view the Go to Electrical Port Modules (DS1, DD
system database of valid module DS1, DS3, STS-1, or EPM), page 29-676.
Manual, 76.5500/13.
Page 29-614 7/07 76.5500/29, Rev R

DS3 Port Module Alarm Messages

PM, use the following table. The first column of the table lists the possible alarm
messages that can be generated for a DS3 PM. The second column lists a
alarm.
Table 6.25 DS3 Port Module Alarm Messages


INT DS3 Parity Error in Network Reporting module has detected a One of these three has occurred:
Copy A detected at PM mismatch between the parity of the - Bad port module incorrectly calculated
incoming signal from Network Copy A the parity.
modules.

to troubleshoot the port module.


Copy B detected at PM mismatch between the parity of the - Bad port module incorrectly calculated
incoming signal from Network Copy B the parity.
modules.



INT EEPROM Failure A failure either to read the EEPROM Reporting port module has failed:
information or to store this information EEPROM data corrupted.
to the database has occurred.
76.5500/29, Rev R 7/07 Page 29-615

Table 6.25 DS3 Port Module Alarm Messages (Continued)

download 255 times without success because the port module was UEQ and
and could not be initialized therefore incompatible. If the port module

INT Failed module diagnostics Port module or redundant port module Port module has failed.
has failed self-diagnostics.
sees. Its attempt to reprogram the port Go to Electrical Port Modules (DS1, DD
module has failed. DS1, DS3, STS-1, or EPM), page 29-676.
INT Internal Error An internal error has occurred because Port has experienced Rcv, Xmt, or Gbl
cannot be isolated.

INT Internal Failure Reporting port module is reporting one One of the following is the likely cause:
of several possible errors. The RPM - Download is being requested while the
has checked the same incoming signal port module is in normal (NR) state.
but is not able to confirm these errors. - Port module (PM) cannot communicate
The RPM has switched to protected with its GC.
mode. - PM experiencing internal transmit or
receive error.

INT Internal failure - audit response is The module did not pass internal Failed or faulted module.
invalid audits. The port module responds, but
the response indicates boot fault or Go to Electrical Port Modules (DS1, DD
unexpected activity (initializing, DS1, DS3, STS-1, or EPM), page 29-676.
halted).
fault
Page 29-616 7/07 76.5500/29, Rev R


Ckt. Type DS1, Ckt. No. = xx received from the DS1 signal. (Ckt. No.
(where xx = 0 to 27) = circuit number) Go to Electrical Port Modules (DS1, DD
Ckt. Type DS1, Ckt. No. = xx transmitting to the DS1 signal. (Ckt. No.
Ckt. Type DS2, Ckt. No. = xx received from the DS2 signal. (Ckt. No.
Ckt. Type DS2, Ckt. No. = xx transmitting to the DS2 signal. (Ckt. No.
Ckt. Type DS3 received from the DS3 signal.
Ckt. Type DS3 transmitting to the DS3 signal.
INT Internal signal degradation at TSI The TSI Qmux device has detected If this alarm is declared against only one
from port module constant SDF and/or PYLD (payload) port module, then that module has
parity errors from a port module. probably failed. If the alarm is declared
against several port modules, the TSIs on
that shelf are suspect.

INT Internal signal failure at TSI from The TSI has detected a loss of frame Either the port module identified or the TSI
port module from a specific reporting module. has failed.

76.5500/29, Rev R 7/07 Page 29-617


INT Module not compatible with This port module is not supported by Module revision level is either lower or
existing software the current software load. higher than the levels supported by the
current software version. Refer to the
current version of Tellabs 5500/5500S
Software Release Document, 76.5500/16,
for the software version currently installed.

INT Network Copy Synchronization While trying to synchronize the The synchronization errors from the NC
Error Threshold Crossed network, the system had too many have exceeded the threshold.

INT SDF out of frame in Network Addressed port module is seeing Because this alarm is given only if a single
Copy A loss-of-frame errors on Network Copy port module is reporting Loss of Frame
A. (LOF), the module is presumed faulty.

INT SDF out of frame in Network Addressed port module is seeing Because this alarm is given only if a single
Copy B loss-of-frame errors on Network Copy port module is reporting Loss of Frame
B. (LOF), the module is presumed faulty.

INT SDF parity error in Network Copy Addressed port module is seeing SDF Because this alarm is given only if a single
A Side parity errors on Network Copy A. port module reports SDF parity errors,
module is presumed faulty.

INT SDF parity error in Network Copy Addressed port module is seeing SDF Because this alarm is given only if a single
B Side parity errors on Network Copy B. port module reports SDF parity errors,
module is presumed faulty.

Copy A system clock error in Network Copy A. likely faulty. If several report this, then

Page 29-618 7/07 76.5500/29, Rev R


Copy B system clock error in Network Copy B. likely faulty. If several report this, then

assigned type from that assigned to this slot by the inserted or the wrong type was assigned
ENT-EQPT command. to that slot.

MEA Inconsistent with type of During a reset of the shelf of the The type of the reporting module in this
associated RPM reporting module, a mismatched RPM protection group does not match that of its
was detected. assigned RPM.

MEA Inserted card type incompatible Reporting port module is incompatible The shelf was not configured for this type
with shelf type with the shelf into which it has been of module.
inserted, such as putting a 3/1 port
module into a shelf of STS-1 modules. Go to Electrical Port Modules (DS1, DD
MODINSRT Module inserted The module was removed but is now in Module has been inserted in its slot on the
database. Use RTRV-REVTBL Go to Electrical Port Modules (DS1, DD
command to view the system database DS1, DS3, STS-1, or EPM), page 29-676.
of valid module revision levels. Refer to
76.5500/29, Rev R 7/07 Page 29-619

Electrical Port Module (EPM) Alarm Messages

6.18 In order to troubleshoot the alarm message(s) received for a faulted EPM,
messages that can be generated for an EPM. The second column lists a
alarm.
Table 6.26 Electrical Port Module Alarm Messages

FEED Loss of power feed A to module There is no power on feed A to the EPM. Power has been turned off, or feeds have
been disconnected.

FEED Loss of power feed B to module There is no power on feed B to the EPM. Power has been turned off, or feeds have
been disconnected.

entity is inhibited against an assigned port module when its IHN-SWTOPROTN-EQPT::PM command
protection switching capability has been is executed on an entity and will be
inhibited. cleared when the corresponding

INT An Attention Line Hardware The EPM has detected an attention line There are hardware problems with the
Error was Detected error. module or the attention line.

INT EEPROM failure A failure either to read the EEPROM The EEPROM data on the port module
information or to store this information to has been corrupted.
the database has occurred.
download 255 times without success and because the port module was UEQ and
could not be initialized. therefore incompatible. If the port module

INT Failed module diagnostics Port module or redundant port module Port module has failed.
has failed self-diagnostics.
INT Failed to detect BNC backplane The EPM does not detect a connection to Either the port module or the BNC
the BNC backplane. backplane is faulty.

Page 29-620 7/07 76.5500/29, Rev R

Table 6.26 Electrical Port Module Alarm Messages (Continued)

INT Failure to reprogram EPM Communications between the GC and The EPM was removed from the shelf
during Best Clock and Data the EPM failed during Best Clock and during the Best Clock audit. There is a
audit Data audit. hardware fault in the GC to EPM UART
communications bus.

INT Internal error An internal error has occurred because of Port has experienced Rcv, Xmt, or Gbl
a failure of a port module, but PGC errors, but there is no way to isolate or
communication with the PGC, but this
cannot be isolated.

INT Internal failure Reporting port module (PM) is detecting One of the following is the likely cause:
one of several possible errors, but cannot - Download requested while PM is in
- Port module (PM) cannot communicate
with its PGC.
- PM experiencing internal transmit or
receive error.

DS1, DS3, STS-1, or EPM), page 29-676
INT Internal failure - audit response The module did not pass internal audits. Failed or faulted module.
is invalid The port module responds, but the
response indicates boot fault or Go to Electrical Port Modules (DS1, DD
unexpected activity (initializing, download DS1, DS3, STS-1, or EPM), page 29-676.
request, test in progress, or halted).
fault
INT Internal failure - unexpected The module experienced an unexpected Failed or faulted module.
download request request for download.
INT LOF detected at both MIMs LOFs have been detected at both MIMs The EPM has failed internally.
from EPM from the EPM.
76.5500/29, Rev R 7/07 Page 29-621


INT LOF detected from MIM LOF has been detected from the MIM. Either the port module or MIM is faulty.

INT MIM detected LOF from EPM The MIM detected LOF from the EPM. The EPM has failed internally.

INT MIM detected Parity Errors The MIM detected parity errors from the Either the EPM or MIM has failed.
from EPM EPM.
current software version. For current
module revision levels, refer to Tellabs
5500/5500S Software Release Document,
76.5500/16 for the software version
currently installed on your system.

INT Parity errors detected from MIM The MIM has detected parity errors. Either the port module or MIM is faulty.

INT Parity errors detected at both Both MIMs have detected parity errors The EPM has failed internally.
MIMs from EPM from the EPM.
INT Port module removed Active PGC has detected the absence of Port module has been removed from its
the reporting port module. slot, or it has not responded to

INT System clock error from MIM A system clock error from the MIM has Either the port module or MIM is faulty.
been detected.
MEA Inconsistent with type of During a reset of the shelf of the reporting The type of the reporting module in this
associated REPM module, a mismatched REPM was protection group does not match that of its
detected. assigned REPM.

Page 29-622 7/07 76.5500/29, Rev R


meet revision level match the set of valid revision levels version of the software.
requirements maintained in the system database. Use
RTRV-REVTBL command to view the Go to Electrical Port Modules (DS1, DD
system database of valid module revision DS1, DS3, STS-1, or EPM), page 29-676.
76.5500/13.
76.5500/29, Rev R 7/07 Page 29-623

STS-1 Port Module Alarm Messages

6.19 In order to troubleshoot the alarm message(s) received for a faulted STS-1
PM, use the following table. The first column of the table lists the possible alarm
messages that can be generated for a STS-1 PM. The second column lists a
alarm.
Table 6.27 STS-1 Port Module Alarm Messages


INT Download failed Reporting STS-1E requested The PGC did not provide the download
download 255 times without success because the STS-1E was UEQ and
and could not be initialized. therefore incompatible. If the STS-1E was
previously NR, it has probably failed, and
the PGC will fault it.

INT EC1 Parity Error in Network Copy Reporting port module has detected a - Port module is bad and has incorrectly
A detected at PM parity error in the incoming signal from calculated the parity.
Network Copy A. - The TSI is bad.
- The fiber cable between the ESM and
the TSI is bad.



B detected at PM parity error in the incoming signal from calculated the parity.
Network Copy B. - The TSI is bad.
the TSI is bad.


Page 29-624 7/07 76.5500/29, Rev R

Table 6.27 STS-1 Port Module Alarm Messages (Continued)

INT EEPROM failure detected A failure either to read the EEPROM The EEPROM data on the port module
information or to store this information has been corrupted.
INT Failed reprogram of network status During an audit the PGC has Either the port module or the PGC has
determined that the network status of failed.
one of its port modules does not match
what it sees. The PGC has attempted Go to Electrical Port Modules (DS1, DD
but failed to reprogram the port DS1, DS3, STS-1, or EPM), page 29-676.
module.
INT Internal error detected An internal error has occurred Port has experienced Rcv, Xmt, or Gbl
because of a failure of a port module, errors, but there is no way to isolate or
but PGC cannot isolate or confirm the confirm this. A port module has not
failure. properly responded to UART
communication with the PGC, but this
cannot be isolated.

INT Internal failure detected Reporting port module (PM) is One of the following is the likely cause:
detecting one of several possible - Download requested while PM is in
errors, but cannot isolate the problem. normal (NR) state.
with its PGC.
receive error.

INT Internal signal failure at TSI from The TSI has detected a loss of frame There is either a faulty port module or a
port module from a specific port module. faulty TSI.

INT Module diagnostics failed Diagnostics are performed either when Port module has failed or is faulty.
a port module is inserted in its shelf
slot, or manually with the DGN-EQPT Go to Electrical Port Modules (DS1, DD
command. This alarm is generated DS1, DS3, STS-1, or EPM), page 29-676.
when one or more of the
self-diagnostic tests fail.
INT Module is incompatible with This port module is not supported by Module revision level is either lower or
current software version. For current
module revision levels, refer to Tellabs
5500/5500S Software Release Document,
76.5500/16 for the software version
currently installed on your system.

76.5500/29, Rev R 7/07 Page 29-625


INT Module removed Active PGC has detected the absence Port module has been removed from its
of the reporting port module. slot, or it has not responded to

INT Payload parity error The TSI has detected payload parity Either the port module or the TSI has
errors and isolated them to the failed.
reporting PME.
INT SDF out of frame in Network Copy Addressed port module is seeing SDF Faulty port module.
A loss-of-frame errors on Network Copy
A. Go to Electrical Port Modules (DS1, DD
INT SDF out of frame in Network Copy Addressed port module is seeing SDF Faulty port module.
B loss-of-frame errors on Network Copy
B. Go to Electrical Port Modules (DS1, DD
INT SDF parity error The TSI has detected SDF parity Faulty port module or faulty TSI.
errors and has isolated to the reporting
PME. Go to Electrical Port Modules (DS1, DD
INT SDF parity error in Network Copy Addressed port module is seeing SDF Faulty port module.
A Side parity errors on Network Copy A.
B Side parity errors on Network Copy B.
INT System clock error in Network Reporting port module has detected a If a single PM reports this, it is likely faulty.
Copy A system clock error in Network Copy A. If several report this, then either the stage
5 TSI or one of the network elements is at
fault.

Page 29-626 7/07 76.5500/29, Rev R


INT System clock error in Network Reporting port module has detected a If a single PM reports this, it is likely faulty.
Copy B system clock error in Network Copy B. If several report this, then either the stage
fault.

inserted, such as putting an 3/1 port
module into a shelf of PMEs. Go to Electrical Port Modules (DS1, DD
MEA Module is inconsistent with Either the module or the revision level Module revision level is either lower or
existing software of the module is not supported by the higher than the levels supported by the
feature package currently running on current software version.
the system.
MEA Module is inconsistent with the The type of the reporting module Either the wrong module has been
currently assigned type differs from that assigned to this slot inserted or the wrong type assigned to that
by the ENT-EQPT command. slot. Refer to the ED-EQPT::PM or
ED-EQPT::RPM commands in Tellabs
Manual, 76.5500/13.

MEA Module is inconsistent with type of During a reset of the shelf containing The PM type of the reporting module in
associated RPM the reporting module, a redundant port this protection group does not match that
module detected a mismatch between of its assigned RPM. Refer to the
the RPM type and the PM types in its ED-EQPT::RPM command in Tellabs
protection group. 5500/5500S Command Reference
Manual, 76.5500/13 for a list of compatible
RPM types for each PM type.
Caution:
The Tellabs stated position is that the
RPME must match the highest revision
level among the PMEs in its protection
group, or traffic loss may occur.
Note: If different types of STS-1E port

modules are mixed within the same
protection group, use an 82.5520 or an
82.5520FE as the redundant port module
if either Enhanced PDI is running or PDI is
in OFF mode. If Regular PDI is running,
use any of the following as the redundant
port module: 81.5520, 82.5520, or
82.5520FE. Refer to the RTRV-EQPT::NE
command in Tellabs 5500/5500S
76.5500/13.

76.5500/29, Rev R 7/07 Page 29-627


MODINSRT Module inserted The module was removed, but is now Module has been inserted in its slot on the
in its slot on the shelf. shelf. No recovery necessary.
meet revision level requirements not match the set of valid revision version of the software. Go to Electrical
levels maintained in the system Port Modules (DS1, DD DS1, DS3, STS-1,
database. Use RTRV-REVTBL or EPM), page 29-676.
command to view the system
76.5500/13.
Page 29-628 7/07 76.5500/29, Rev R

DS1 and Double-Density DS1 Redundant Port Module Alarm Messages

or Double-Density DS1 RPM, use the following table. The first column of the table
lists the possible alarm messages that can be generated for a DS1 or
Double-Density DS1 RPM. The second column lists a description of the alarm
message, and the third column gives a probable cause for the alarm.
Table 6.28 DS1 or Double-Density DS1 Redundant Port Module Alarm Messages
Copy A detected at RPM mismatch between the parity of the - Bad port module incorrectly calculated
incoming signal from network copy A and the parity.
that of the outgoing port module. - Bad TSI.
modules.
Go to Redundant Electrical Port Modules

(DS1, DD DS1, DS3, STS-1, REPM),
page 29-694, to troubleshoot the port
module.


Copy B detected at RPM mismatch between the parity of the - Bad port module incorrectly calculated
incoming signal from network copy B and the parity.
that of the outgoing port module. - Bad TSI.
modules.

module.


INT EEPROM Failure A failure either to read the EEPROM Reporting port module failed due to
information or to store it to the database corrupted EEPROM data.
has occurred.
page 29-694.
download 255 times without success and because the port module was UEQ and
could not be initialized. therefore incompatible. If the port module

page 29-694.
76.5500/29, Rev R 7/07 Page 29-629

Table 6.28 DS1 or Double-Density DS1 Redundant Port Module Alarm Messages (Continued)
INT Failed module diagnostics Port module has failed self-diagnostics. Port module has failed.

page 29-694.
sees. Its attempt to reprogram it failed. Go to Redundant Electrical Port Modules
page 29-694.
INT Internal error An internal error has occurred because of Port has experienced Rcv, Xmt, or Gbl
a failure of a port module, but PGC cannot errors, but there is no way to isolate or
isolate or confirm the failure. confirm this. A port module has not
cannot be isolated.

page 29-694.
INT Internal failure Reporting redundant port module has One of the following is the likely cause:
detected one of several possible internal - Download is being requested while port
errors. module is in normal (NR) state.
with its GC.
receive error.

page 29-694.
INT Internal failure - module The module failed its internal sanity check. DS1 or DD DS1 was not actually removed
sanity check failed but is faulty.

page 29-694.
INT Internal signal degradation at The TSI Qmux device has detected If this alarm is declared against only one
TSI from port module constant TVT (Tellabs virtual tributary) redundant port module, then that module
parity errors from a protecting redundant has probably failed. If the alarm is
port module. declared against several port modules, the
TSIs on that shelf are suspect.

page 29-694.

page 29-694.
Page 29-630 7/07 76.5500/29, Rev R

INT Network Copy While trying to synchronize the network, The synchronization errors from the NC
Synchronization Error the system had too many synchronization have exceeded the threshold.
Threshold Crossed errors.
page 29-694.
INT Port Module Removed Active PGC has detected the absence of a Redundant port module has been
port module. removed from its slot, or it has not
responded to communications from the
PGC, or its EEPROMS are corrupt or
incompatible with the current software
version.

page 29-694.
INT System clock error in Network Reporting redundant port module has If a single RPM reports this, it is likely
Copy A detected a system clock error in Network faulty. If several report this, then either the
Copy A. stage 5 TSI or one of the network
elements is at fault.

module.

Copy B detected a system clock error in Network faulty. If several report this, then either the
Copy B. stage 5 TSI or one of the network

module.

MEA Inconsistent with currently The type of the reporting module differs Either the wrong module was inserted or
assigned type from that assigned to this slot by the the wrong type was assigned to that slot.
ENT-EQPT command.
page 29-694.
MODINSRT Module Inserted The module was removed but is now in its Module has been inserted in its slot on the
slot on the shelf. shelf. No recovery necessary.
PROTNA RPM carrying FORCED Redundancy for the specified protection The SW-TOWKG-EQPT command has
switched traffic - not available group is unavailable because the RPM been used to force traffic to this RPM.
for protection has been forced to carry traffic.
page 29-694.
76.5500/29, Rev R 7/07 Page 29-631

PROTNA RPM failed (ANR) - not Redundancy is unavailable for specified One of the following is the likely cause:
available for protection protection group because RPM is in an - RPM has been entered while still in the
abnormal (ANR) state. ANR state.
- The RPM has been removed.
- A fault in the RPM has been detected by
either the port module firmware or by the
GC software.

page 29-694.
PROTNA RPM inhibited - not available Redundancy for protection group is The INH-SWTOPROTN-EQPT command
for protection unavailable because PRTN parameter on has been used to inhibit protection by this
the RPM is INH. RPM.

page 29-694.
PROTNA RPM OOS - not available for Redundancy for the protection group is Either the RPM has been “entered” while
protection unavailable because the RPM is still in the out-of-service state, or it has
out-of-service. been forced OOS by the ED-EQPT
command.

page 29-694.
REVLVL Module revision level does The revision level of the module does not This module is not supported by this
not meet revision level match the set of valid revision levels version of the software.
RTRV-REVTBL command to view the Go to Redundant Electrical Port Modules
system database of valid module revision (DS1, DD DS1, DS3, STS-1, REPM),
levels. Refer to Tellabs 5500/5500S page 29-694.
76.5500/13.
Page 29-632 7/07 76.5500/29, Rev R

DS3 Redundant Port Module Alarm Messages

RPM, use the following table. The first column of the table lists the possible alarm
messages that can be generated for a DS3 RPM. The second column lists a
description of the alarm message, and the third column gives a probable cause for
the alarm.
Table 6.29 DS3 Redundant Port Module Alarm Messages

INT DS3 Parity Error in Network Copy A Reporting redundant module has One of these three has occurred:
detected at RPM detected a mismatch between the - Bad port module incorrectly calculated
parity of the incoming DS3 signal the parity.
from network copy A and that of the - Bad TSI.
outgoing port module. - Bad fiber cable between ESM and TSI
modules.

module.


INT DS3 Parity Error in Network Copy B Reporting redundant module has One of these three has occurred:
detected at RPM detected a mismatch between the - Bad port module incorrectly calculated
parity of the incoming DS3 signal the parity.
from network copy B and that of the - Bad TSI.
outgoing port module. - Bad fiber cable between ESM and TSI
modules.

module.

INT EEPROM Failure Either a failure to read the EEPROM Reporting port module has failed:
information or a failure to store this EEPROM data corrupted.
occurred. Go to Redundant Electrical Port Modules
page 29-694.
INT Failed download Reporting redundant port module The PGC did not provide the download
requested download 255 times because the RPM was UEQ and therefore
without success and could not be incompatible. If the RPM was previously
initialized. NR, it has probably failed, and the PGC
will fault it.

page 29-694.
76.5500/29, Rev R 7/07 Page 29-633

Table 6.29 DS3 Redundant Port Module Alarm Messages (Continued)

INT Failed module diagnostics Redundant port module has failed Port module has failed.
self-diagnostics.
page 29-694.
INT Failed reprogram of network status During an audit, GC has determined Either the port module or the GC has
that actual status of one of its port failed.
modules does not match what the
GC sees. Its attempt to reprogram Go to Redundant Electrical Port Modules
RPM3 has failed. (DS1, DD DS1, DS3, STS-1, REPM),
page 29-694.
INT Internal Error An internal error has occurred Port has experienced Rcv, Xmt, or Gbl
because of a failure of a port errors, but there is no way to isolate or
module, but PGC cannot isolate or confirm this. A port module has not
confirm the failure. properly responded to UART
cannot be isolated.

page 29-694.
INT Internal Failure Reporting redundant port module is One of the following is the likely cause:
detecting one of several possible - Download is being requested while port
errors, but cannot isolate the module is in normal (NR) state.
problem. - Port module (PM) cannot communicate
with its GC.
receive error.

page 29-694.
INT Internal failure - module sanity check The module failed its internal sanity RPM was not actually removed, but is
failed check. faulty.

page 29-694.
INT Internal signal degradation at TSI The TSI Qmux device has detected If this alarm is declared against only one
from port module constant SDF and/or PYLD port module, then that module has
(payload) parity errors from a probably failed. If the alarm is declared
protecting redundant port module. against several port modules, the TSIs on
that shelf are suspect.

module, or go to Time Slot Interchange
Module (TSI), page 29-506, to
troubleshoot the TSI.
Page 29-634 7/07 76.5500/29, Rev R



module, or go Time Slot Interchange
INT Module not compatible with existing Redundant port module is not Module revision level is either lower or
software supported by the current software higher than the levels supported by the
load. current software version.

page 29-694.
INT Network Copy Synchronization Error While trying to synchronize the The synchronization errors from the NC
Threshold Crossed network, the system had too many have exceeded the threshold.
page 29-694.
INT Port Module Removed Active PGC has detected the Port module has been removed from its
absence of a port module. slot, or it has not responded to

page 29-694.
INT SDF out of frame in Network Copy A Addressed port module is seeing Because this alarm is given only if a single
loss-of-frame errors on Network port module is reporting LOFs, the module
Copy A. is presumed faulty.

page 29-694.
INT SDF out of frame in Network Copy B Addressed port module is seeing Because this alarm is given only if a single
loss-of-frame errors on Network port module is reporting LOFs, the module
Copy B. is presumed faulty.

page 29-694.
INT SDF parity error in Network Copy A Addressed port module is seeing Because this alarm is given only if a single
Side SDF parity errors on Network Copy port module is reporting SDF parity errors,
A. the module is presumed faulty.

page 29-694.
76.5500/29, Rev R 7/07 Page 29-635


INT SDF parity error in Network Copy B Addressed port module is seeing Because this alarm is given only if a single
Side SDF parity errors on Network Copy port module is reporting SDF parity errors,
B. the module is presumed faulty.

page 29-694.
INT System clock error in Network Copy Reporting port module has detected If a single port module reports this, it is
A a system clock error in Network likely faulty. If several report this, then
Copy A. either the stage 5 TSI or one of the

INT System clock error in Network Copy Reporting port module has detected If a single port module reports this, it is
B a system clock error in Network likely faulty. If several report this, then
Copy B. either the stage 5 TSI or one of the

MEA Inconsistent with currently assigned The type of the reporting module Either the wrong module has been
type differs from that assigned to this slot inserted or the wrong type assigned to that
by the slot.
ENT-EQPT command.
page 29-694.
MEA Inserted card type incompatible with Reporting port module is The shelf was not configured for this type
shelf type incompatible with the shelf into of module.
which it has been inserted, such as
putting a 3/1 port module into a shelf Go to Redundant Electrical Port Modules
of STS-1E modules. (DS1, DD DS1, DS3, STS-1, REPM),
page 29-694.
MODINSRT Module Inserted The module was removed but is now Module has been inserted in its slot on the
PROTNA RPM carrying FORCED switched Redundancy for the specified SW-TOPROTN-EQPT command has
traffic - not available for protection protection group is unavailable been used to force traffic to this RPM.
because the RPM has been forced
to carry traffic. Go to Redundant Electrical Port Modules
page 29-694.
Page 29-636 7/07 76.5500/29, Rev R


PROTNA RPM failed (ANR) - not available for Redundancy for the specified One of the following is the likely cause:
protection protection group is unavailable - The RPM has been entered while still in
because the RPM is in an abnormal the ANR state.
(ANR) state. - The RPM has been removed.
GC software.

page 29-694.
PROTNA RPM inhibited - not available for Redundancy for the protection group The INH-SWTOPROTN-EQPT command
protection is unavailable because the PRTN has been used to inhibit protection by this
parameter on the RPM has been set RPM.
to INH.
page 29-694.
PROTNA RPM OOS - not available for Redundancy for the protection group Either the RPM has been “entered” while
protection is unavailable because the RPM is still in the out-of-service state, or it has
command.

page 29-694.
system database. Use Go to Redundant Electrical Port Modules
RTRV-REVTBL command to view (DS1, DD DS1, DS3, STS-1, REPM),
Manual, 76.5500/13.
76.5500/29, Rev R 7/07 Page 29-637

Redundant Electrical Port Module (REPM) Alarm Messages

REPM, use the following table. The first column of the table lists the possible alarm
messages that can be generated for a REPM, the second column lists a description
Table 6.30 Redundant Electrical Port Module Alarm Messages

REPM. been disconnected.

page 29-1105.
REPM. been disconnected.

page 29-1105.
INT EEPROM failure A failure either to read the EEPROM The EEPROM data on the EPM or REPM
information or to store it to the has been corrupted.
database has occurred.
page 29-694.
INT Failed download Reporting REPM requested download The PGC did not provide the download
255 times without success and could because the REPM was UEQ and
not be initialized. therefore incompatible. If the REPM was

page 29-694.
INT Failed module diagnostics The REPM has failed self-diagnostics. The REPM has failed.

page 29-694.
INT Failed to detect BNC backplane The REPM does not detect a Either the port module or the BNC
connection to the BNC backplane. backplane is faulty.

page 29-694.
INT Failure to reprogram REPM Communications between the GC and The REPM was removed from the shelf
during Best Clock and Data audit the REPM failed during Best Clock and during the Best Clock audit. There is a
Data audit. hardware fault in the GC to REPM UART
communications bus.

page 29-694.
Page 29-638 7/07 76.5500/29, Rev R

Table 6.30 Redundant Electrical Port Module Alarm Messages (Continued)

INT Internal Error An internal error has occurred because Port has experienced Rcv, Xmt, or Gbl
cannot be isolated.

page 29-694.
INT Internal Failure Reporting port module is reporting one One of the following is the likely cause:
of several possible errors. The REPM - Download is being requested while port
but is not able to confirm these errors. - Port module cannot communicate with its
The REPM has switched to protected GC.
mode. - Port module is experiencing internal
transmit or receive error.

page 29-694.
INT Internal failure - audit response is The module did not pass internal Failed or faulted module.
invalid audits. The port module responds, but
the response indicates boot fault or Go to Redundant Electrical Port Modules
unexpected activity (initializing, (DS1, DD DS1, DS3, STS-1, REPM),
download request, test in progress, or page 29-694.
halted).
page 29-694.
page 29-694.
fault
page 29-694.
page 29-694.
page 29-694.
76.5500/29, Rev R 7/07 Page 29-639



page 29-694.
INT LOF detected at both MIMs from Both MIMs have detected LOFs from The REPM has failed internally.
REPM the REPM.
page 29-694.
INT MIM detected LOF from REPM The MIM detected LOF from the The REPM has failed internally.
REPM.
page 29-694.
INT MIM detected Parity Errors from The MIM detected parity errors from Either the REPM or MIM has failed.
REPM the REPM.
page 29-694.
INT Module not compatible with This port module is not supported by Module revision level is either lower or

page 29-694.
INT Parity errors detected from MIM Parity errors have been detected from Either the REPM or MIM has failed.
the MIM.
page 29-694.
INT Parity errors detected at both Both MIMs have detected parity errors The REPM has failed internally.
MIMs from REPM from the REPM.
page 29-694.

page 29-694.
been detected.
page 29-694.
MODINSRT Module inserted The module was removed, but is now Module has been inserted in its slot on the
Page 29-640 7/07 76.5500/29, Rev R


command.

page 29-694.
PROTNA RPM failed (ANR) - not available Redundancy for the specified One of the following is the likely cause:
for protection protection group is unavailable - The RPM has been entered while still in
GC software.

page 29-694.
PROTNA RPM inhibited - not available for Redundancy for the protection group is The INH-SWTOPROTN-EQPT command
protection unavailable because the PRTN has been used to inhibit protection by this
parameter on the RPM has been set to RPM.
Inhibit (INH).
page 29-694.
PROTNA RPM carrying FORCED switched Redundancy for the specified The SW-TOPROTN-EQPT command has
because the RPM has been forced to
carry traffic. Go to Redundant Electrical Port Modules
page 29-694.
database. Use RTRV-REVTBL Go to Redundant Electrical Port Modules
command to view the system database (DS1, DD DS1, DS3, STS-1, REPM),
of valid module revision levels. Refer to page 29-694.
76.5500/29, Rev R 7/07 Page 29-641

STS-1 Redundant Port Module Alarm Messages

6.23 In order to troubleshoot the alarm message(s) received for a faulted STS-1
RPM, use the following table. The first column of the table lists the possible alarm
messages that can be generated for a STS-1 RPM. The second column lists a
the alarm.
Table 6.31 STS-1 Redundant Port Module Alarm Messages

INT Download failed Reporting redundant STS-1E The PGC did not provide the download
requested download 255 times without because the redundant STS-1E was UEQ
success and could not be initialized. and therefore incompatible. If the
redundant STS-1E was previously NR, it
has probably failed, and the PGC will fault
it.

page 29-694.
A detected at RPM parity error in the incoming signal from calculated the parity.
Network Copy A. - The TSI is bad.
the TSI is bad.

module.


TSI.
B detected at RPM parity error in the incoming signal from calculated the parity.
Network Copy B. - The TSI is bad.
the TSI is bad.

module.


TSI.
Page 29-642 7/07 76.5500/29, Rev R

Table 6.31 STS-1 Redundant Port Module Alarm Messages (Continued)

INT EEPROM failure detected A failure either to read the EEPROM The EEPROM data on the redundant port
information or to store this information module has been corrupted.
page 29-694.
INT Failed reprogram of network status During an audit the GC has Either the port module or the GC has
determined that the network status of failed.
one of its port modules does not match
what it sees. The GC has attempted Go to Redundant Electrical Port Modules
but failed to reprogram the port (DS1, DD DS1, DS3, STS-1, REPM),
module. page 29-694.
INT Internal error detected An internal error has occurred because Port has experienced Rcv, Xmt, or Gbl
cannot be isolated.

page 29-694.
INT Internal failure detected Reporting redundant port module is One of the following is the likely cause:
detecting one of several possible - Download is being requested while the
errors, but cannot isolate the problem. redundant port module is in normal (NR)
state
with its GC.
receive error.

page 29-694.

module. Go to Time Slot Interchange
INT Module diagnostics failed Port module has failed Port module has failed.
self-diagnostics.
page 29-694.
INT Module is incompatible with This port module is not supported by Module revision level is either lower or

page 29-694.
76.5500/29, Rev R 7/07 Page 29-643


INT Module removed Active PGC has detected the absence Port module has been removed from its
of the reporting port module. slot, or it has not responded to

page 29-694.
page 29-694.
INT SDF out of frame in Network Copy Addressed port module is seeing Faulty port module.
A loss-of-frame errors on network copy
A. Go to Redundant Electrical Port Modules
page 29-694.
INT SDF out of frame in Network Copy Addressed port module is seeing Faulty port module.
B loss-of-frame errors on network copy
B. Go to Redundant Electrical Port Modules
page 29-694.
INT SDF parity error The TSI has detected SDF parity Faulty port module or faulty TSI.
errors and has isolated to the reporting
RPME. Go to Redundant Electrical Port Modules
A Side parity errors on network copy A.
page 29-694.
B Side parity errors on network copy B.
page 29-694.
Copy A detected a system clock error in faulty. If several report this, then either
network copy A. the stage 5 TSI or one of the network

Page 29-644 7/07 76.5500/29, Rev R


Copy B detected a system clock error in faulty. If several report this, then either
network copy B. the stage 5 TSI or one of the network

INT Payload parity error The TSI has detected payload parity Either the redundant port module or the
errors and isolated them to the TSI has failed.
reporting RPME.
MEA Inserted card type is incompatible Reporting port module is incompatible The shelf was not configured for this type
inserted, such as putting an 3/1 port
module into a shelf of PMEs. Go to Redundant Electrical Port Modules
page 29-694.
MEA Module is inconsistent with the The type of the reporting module Either the wrong module has been
currently assigned type differs from that assigned to this slot by inserted or the wrong type assigned to
the ENT-EQPT command. that slot.

page 29-694.
MODINSRT Module Inserted The module was removed but is now in Module has been inserted in its slot on
PROTNA RPM carrying FORCED switched Redundancy for the specified The SW-TOPROTN-EQPT command has
because the RPM has been forced to
carry traffic. Go to Redundant Electrical Port Modules
page 29-694.
PROTNA RPM failed (ANR) - not available Redundancy for the specified One of the following is the likely cause:
for protection protection group is unavailable - The RPM has been entered while still in
GC software.

page 29-694.
76.5500/29, Rev R 7/07 Page 29-645


PROTNA RPM inhibited - not available for Redundancy for the protection group is The INH-SWTOPROTN-EQPT command
protection unavailable because the PRTN has been used to inhibit protection by this
parameter on the RPM has been set to RPM.
Inhibit (INH).
page 29-694.
command.

page 29-694.
database. Use RTRV-REVTBL Go to Redundant Electrical Port Modules
command to view the system database (DS1, DD DS1, DS3, STS-1, REPM),
of valid module revision levels. Refer page 29-694, to troubleshoot the port
to Tellabs 5500/5500S Command module.
Page 29-646 7/07 76.5500/29, Rev R

Optical Port Module Alarm Messages

6.24 In order to troubleshoot the alarm message(s) received for a faulted OC-3,
OPM3X8, OC-12, OPM12X4, or OPM48 port module use the following table. The
first column of the table lists the possible alarm messages that can be generated
for an optical port module. The second column lists a description of the alarm
message, and the third column gives a probable cause for the alarm.
Table 6.32 Optical Port Module Alarm Messages

OPM. been disconnected.
Go to Optical Port Modules (OPM3,

OPM3X8, OPM12, OPM12X4, OPM48),
page 29-705.
OPM. been disconnected.

page 29-705.
INT An Attention Line Hardware Error The OPM has detected an attention There are hardware problems with the
was Detected line error. module or the attention line.

page 29-705.
INT Cable or Internal failure - PT at Either the OC48 cable or the PT is There is a problem with the SDF48 cable,
port X, where X is the port defected. such as a dirty or broken cable, or there is
number. an internal failure with the PT.

page 29-835.
INT Connection Memory Download There is a failure downloading the Defective OC-3 and OC-12.
Failure OC-3 and OC-12 connection memory.
page 29-705.
INT Download failed Reporting OPM requested download The PGC did not provide the download
255 times without success and could because the OPM was UEQ and
not be initialized. therefore incompatible. If the OPM was

page 29-705.
INT EEPROM failure detected A failure either to read the EEPROM The EEPROM data on the OPM3 or
information or to store it to the OPM12 module (working or protect) has
database has occurred. been corrupted.

page 29-705.
76.5500/29, Rev R 7/07 Page 29-647

Table 6.32 Optical Port Module Alarm Messages (Continued)

INT Failure to reprogram OPM during Communications between the GC and The OPM was removed from the shelf
Best Clock and Data audit the OPM failed during Best Clock and during the Best Clock audit. There is a
Data audit. hardware fault in the GC to OPM UART
communications bus.

page 29-705.
INT Indeterminable inter-module An Inter-Module Signaling Impairment Not determinable.

signal is impaired (IMSI) condition is an indication of
communication errors between the Go to Optical Port Modules (OPM3,
OPM and MIM devices. This message OPM3X8, OPM12, OPM12X4, OPM48),
indicates that the OPM, or possibly the page 29-705.
MIM has been determined as faulty.
IMSI faults are seen between the OPM Go to Mapping Interface Module (MIM),
and MIM on the universal shelves. page 29-815.
INT Internal error detected The GC state machine generates an Port module has not properly responded
internal error when the GC cannot to UART communication with the GC and
properly communicate with the the problem cannot be isolated. Port has
MM/RMM. experienced an OPM to OPM interface
problem.

page 29-705.
INT Internal failure detected Reporting port module is reporting one One of the following is the likely cause:
of several possible errors. The RMM - Download is being requested while port
but is not able to confirm these errors. - Port module (OPM) cannot
The RMM has switched to protected communicate with its GC.
mode. - PM experiencing internal transmit or
receive error.

page 29-705.
INT Internal failure detected - PT at The Pluggable Transceiver in the There is a problem with the PT.
port X, where X is the port OPM48 is faulted.
number. Go to Pluggable Transceiver (PT),
page 29-835.
INT LOF detected at both MIMs from LOFs have been detected at both MIMs The OPMN has failed internally.
OPMN from the OPMN.
page 29-705.

page 29-705.
INT MIM detected LOF from OPMN The MIM detected LOF from the The OPMN has failed internally.
OPMN.
page 29-705.
Page 29-648 7/07 76.5500/29, Rev R


INT MIM detected Parity Errors from The MIM detected parity errors from Either the OPMN or MIM has failed.
OPMN the OPMN.
page 29-705.
INT Module diagnostics failed Port module has failed self-diagnostics. The optical port module has failed.

page 29-705.
INT Module is incompatible with This optical port module is not Module revision level is either lower or
existing software supported by the current software load. higher than the levels supported by the

page 29-705.
INT Module removed Active PGC has detected the absence The OPMN has been removed from its
of the reporting optical port module. slot, or it has not responded to

page 29-705.
INT Parity errors detected at both Both MIMs have detected parity errors The OPMN has failed internally.
MIMs from OPMN from the OPMN.
page 29-705.
INT Parity errors detected from MIM Parity errors have been detected from Either the port module or MIM is faulty.
the MIM.
page 29-705.
INT PT Module removed - PT at port The OPM48 has detected that the PT Reseat the PT module at the affected port
X, where X is the port number. module is not in its slot. in the OPM48.
INT PT Module inconsistent with The PT inserted in the port is not Verify the correct version of the PT. Refer
assigned type - PT at port X, designed to be used with the OPM48. to Tellabs 5500/5500S Software Release
where X is the port number. Document, 76.5500/16.

page 29-835.
been detected.
page 29-705.
76.5500/29, Rev R 7/07 Page 29-649


assigned type from that assigned to this slot by the inserted or the wrong type assigned to
ENT-EQPT command. that slot.

page 29-705.
MODINSRT Module Inserted The module was removed but is now in Module has been inserted in its slot on the
database. Use RTRV-REVTBL Go to Optical Port Modules (OPM3,
command to view the system database OPM3X8, OPM12, OPM12X4, OPM48),
of valid module revision levels. Refer to page 29-705.
REVLVL Module rev level does not meet The revision of the OPM48 is Refer to Tellabs 5500 Software Release
minimum due to PT port X, where incompatible with the PT in the module. Document, 76.5500/16, for the correct
X is the port number. version of the OPM48.

page 29-705.
Page 29-650 7/07 76.5500/29, Rev R

CCPMA Alarm Messages

CCPMA, use the following table. The first column of the table lists the possible
alarm messages that can be generated for a CCPMA. The second column lists a
the alarm.
Table 6.33 CCPMA Alarm Messages

CC1CNFG Configuration Mismatch of A termination is a member of a group Incorrectly provisioned terminations on the
terminations detected in first CC or connection on the NPU side of the Tellabs or NPU side of the CCPMA.
Block CCPMA within the first CC Block, but
is not provisioned on the Tellabs side
of the CCPMA.
CC1ERROR Error in the first CC Block - Critical At least one critical alarm has been A condition exists on the NPU side of the
CR declared on the NPU side of the first CCPMA.
CC Block within the CCPMA.
Go to the NPU user interface to see the
details of the condition type.
CC1ERROR Error in the first CC Block - Major At least one major alarm has been A condition exists on the NPU side of the
MJ declared on the NPU side of the first CCPMA.
CC1ERROR Error in the first CC Block - Minor At least one minor alarm has been A condition exists on the NPU side of the
MN declared on the NPU side of the first CCPMA.
CC2CNFG Configuration Mismatch of A termination is a member of a group Incorrectly provisioned terminations on the
terminations detected in second CC or connection on the NPU side of the Tellabs or NPU side of the CCPMA.
Block CCPMA within the second CC Block,
but is not provisioned on the Tellabs
side of the CCPMA.
CC2ERROR Error in the second CC Block - At least one critical alarm has been A condition exists on the NPU side of the
CR Critical declared on the NPU side of the CCPMA.
second CC Block within the CCPMA.
CC2ERROR Error in the second CC Block - At least one major alarm has been A condition exists on the NPU side of the
MJ Major declared on the NPU side of the CCPMA.
CC2ERROR Error in the second CC Block - At least one minor alarm has been A condition exists on the NPU side of the
MN Minor declared on the NPU side of the CCPMA.
CCPMA. been disconnected.
Go to CCPMA, page 29-770.
76.5500/29, Rev R 7/07 Page 29-651

Table 6.33 CCPMA Alarm Messages (Continued)

CCPMA. been disconnected.
entity is inhibited against an assigned CCPMA when IHN-SWTOPROTN-EQPT::PM command
INT An Attention Line Hardware Error The CCPMA has detected an There are hardware problems with the
was Detected attention line error. module or the attention line.
INT CC block failure The CCPMA detected a hardware Failed or faulted CCPMA.
problem with one of the CC blocks
within the module. Go to CCPMA, page 29-770.
INT EEPROM failure A failure either to read the EEPROM The EEPROM data on the CCPMA
information or to store it to the (working or protect) has been corrupted.
INT Failed download Reporting CCPMA requested The PGC did not provide the download
download 255 times without success because the CCPMA was UEQ and
and could not be initialized. therefore incompatible. If the CCPMA was
INT Failed module diagnostics CCPMA has failed self-diagnostics. The CCPMA has failed.
INT Internal Error The GC state machine generates an CCPMA has not properly responded to
internal error when the GC cannot UART communication with the GC and the
properly communicate with the problem cannot be isolated. Port has
MM/RMM. experienced an CCPMA to CCPMA
interface problem.
INT Internal Failure Reporting CCPMA is reporting one of One of the following is the likely cause:
several possible errors. The RMM - Download is being requested while port
has checked the same incoming module is in normal (NR) state.
signal but is not able to confirm these - CCPMA cannot communicate with its
errors. The RMM has switched to GC.
protected mode. - CCPMA experiencing internal transmit or
receive error.
INT Internal failure - audit response is The CCPMA did not pass internal Failed or faulted CCPMA.
invalid audits. The port module responds,
but the response indicates boot fault Go to CCPMA, page 29-770.
or unexpected activity (initializing,
download request, test in progress,
or halted).
Page 29-652 7/07 76.5500/29, Rev R


INT Internal failure - loss of The CCPMA detected a loss of Failed or faulted CCPMA.
INT LOF detected at both MIMs from LOFs have been detected at both The CCPMA has failed internally.
CCPM MIMs from the CCPMA.
INT LOF detected from MIM LOF has been detected from the Either the CCPMA or MIM is faulty.
MIM.
INT MIM detected Parity Errors from The MIM detected parity errors from Either the CCPMA or MIM has failed.
CCPM the CCPMA.
INT MIM detected LOF from CCPM The MIM detected LOF from the The CCPMA has failed internally.
CCPMA.
INT Module not compatible with existing This CCPMA is not supported by the Module revision level is either lower or
software current software load. higher than the levels supported by the
INT Parity errors detected at both MIMs Both MIMs have detected parity The CCPMA has failed internally.
from CCPM errors from the CCPMA.
INT Parity errors detected from MIM Parity errors have been detected Either the CCPMA or MIM is faulty.
from the MIM.
INT Port Module Removed Active PGC has detected the The CCPMA has been removed from its
absence of the reporting CCPMA. slot, or it has not responded to
INT Signal Fail detected at MM and There is a signal failure between the Either the CCPMA or mapping module has
RMM from CCPM mapping module and the CCPMA. failed. Depending on the corresponding
messages received, go to one of the
following:
• CCPMA, page 29-770
• Mapping Modules (MM), page 29-794
• Redundant Mapping Modules (RMM),
page 29-807
MODINSRT Module Inserted The CCPMA was removed but is now CCPMA has been inserted in its slot on
PROTDEG Protection Switching Degraded - This message will be seen when the The probable cause is a bad
Extra Switch Time Possible NPU dynamic data held on the communication path between the CCPMA
CCPMA and RCCPMA is out of sync. and RCCPMA modules.
The NPU dynamic data on the
RCCPMA must exactly match the Go to CCPMA, page 29-770.
NPU dynamic data on the CCPMA,
this allows one module to quickly
substitute for another.
76.5500/29, Rev R 7/07 Page 29-653


REVLVL Module revision level does not meet The revision level of the CCPMA This CCPMA is not supported by this
system database. Use Go to CCPMA, page 29-770.
RTRV-REVTBL command to view
the system database of valid CCPMA
Manual, 76.5500/13.
Page 29-654 7/07 76.5500/29, Rev R

RCCPMA Alarm Messages

RCCPMA, use the following table. The first column of the table lists the possible
alarm messages that can be generated for a RCCPMA. The second column lists a
the alarm.
Table 6.34 RCCPMA Alarm Messages

CC1CNFG Configuration Mismatch of A termination is a member of a group Incorrectly provisioned terminations on
terminations detected in first CC or connection on the NPU side of the the Tellabs or NPU side of the RCCPMA.
Block CCPMA within the first CC Block, but
is not provisioned on the Tellabs side
of the CCPMA.
CC1ERROR Error in the first CC Block - Critical At least one critical alarm has been A condition exists on the NPU side of the
CR declared on the NPU side of the first CCPMA.
CC1ERROR Error in the first CC Block - Major At least one major alarm has been A condition exists on the NPU side of the
MJ declared on the NPU side of the first CCPMA.
CC1ERROR Error in the first CC Block - Minor At least one minor alarm has been A condition exists on the NPU side of the
MN declared on the NPU side of the first CCPMA.
CC2CNFG Configuration Mismatch of A termination is a member of a group Incorrectly provisioned terminations on

terminations detected in second or connection on the NPU side of the the Tellabs or NPU side of the RCCPMA.
CC Block CCPMA within the second CC Block,
but is not provisioned on the Tellabs
side of the CCPMA.
CC2ERROR Error in the second CC Block - At least one critical alarm has been A condition exists on the NPU side of the
CR Critical declared on the NPU side of the CCPMA.
CC2ERROR Error in the second CC Block - At least one minor alarm has been A condition exists on the NPU side of the
MN Minor declared on the NPU side of the CCPMA.
CC2ERROR Error in the second CC Block - At least one major alarm has been A condition exists on the NPU side of the
MJ Major declared on the NPU side of the CCPMA.
RCCPMA. have been disconnected.
Go to RCCPMA, page 29-784.
76.5500/29, Rev R 7/07 Page 29-655

Table 6.34 RCCPMA Alarm Messages (Continued)

RCCPMA. have been disconnected.
entity is inhibited against an assigned RCCPMA when IHN-SWTOPROTN-EQPT::PM
its protection switching capability has command is executed on an entity and
been inhibited. will be cleared when the corresponding
INT An Attention Line Hardware Error The RCCPMA has detected an There are hardware problems with the
was Detected attention line error. RCCPMA or the attention line.
INT CC block failure The RCCPMA detected a hardware Failed or faulted RCCPMA.
problem with one of the CC blocks
within the RCCPMA. Go to RCCPMA, page 29-784.
INT EEPROM failure A failure either to read the EEPROM The EEPROM data on the RCCPMA has
information or to store it to the been corrupted.
INT Failed download Reporting RCCPMA requested The PGC did not provide the download
download 255 times without success because the RCCPMA was UEQ and
and could not be initialized. therefore incompatible. If the RCCPMA
INT Failed module diagnostics RCCPMA has failed self-diagnostics. The RCCPMA has failed.
INT Internal Error The GC state machine generates an RCCPMA has not properly responded to
internal error when the GC cannot UART communication with the GC and
properly communicate with the the problem cannot be isolated. Port has
MM/RMM. experienced an RCCPMA to RCCPMA
interface problem.
INT Internal Failure Reporting RCCPMA is reporting one of One of the following is the likely cause:
several possible errors. The RMM has - Download is being requested while
checked the same incoming signal but RCCPMA is in normal (NR) state.
is not able to confirm these errors. The - RCCPMA cannot communicate with its
RMM has switched to protected mode. GC.
- RCCPMA experiencing internal
transmit or receive error.
INT Internal failure - audit response is The RCCPMA did not pass internal Failed or faulted RCCPMA.
invalid audits. The RCCPMA responds, but
the response indicates boot fault or Go to RCCPMA, page 29-784.
unexpected activity (initializing,
halted).
Page 29-656 7/07 76.5500/29, Rev R


INT Internal failure - loss of The RCCPMA detected a loss of Failed or faulted RCCPMA.
INT LOF detected at both MIMs from LOFs have been detected at both The RCCPMA has failed internally.
RCCPM MIMs from the RCCPMA.
INT LOF detected from MIM LOF has been detected from the MIM. Either the RCCPMA or MIM is faulty.
INT MIM detected LOF from RCCPM The MIM detected LOF from the The RCCPMA has failed internally.
RCCPMA.
INT MIM detected Parity Errors from The MIM detected parity errors from Either the RCCPMA or MIM has failed.
RCCPM the RCCPMA.
INT Module not compatible with existing This RCCPMA is not supported by the RCCPMA revision level is either lower or
INT Parity errors detected at both MIMs Both MIMs have detected parity errors The RCCPMA has failed internally.
from RCCPM from the RCCPMA.
INT Parity errors detected from MIM Parity errors have been detected from Either the RCCPMA or MIM is faulty.
the MIM.
INT Port Module Removed Active PGC has detected the absence The RCCPMA has been removed from
of the reporting RCCPMA. its slot, or it has not responded to
INT Signal Fail detected at MM and There is a signal failure between the Either the RCCPMA or mapping module
RMM from RCCPM mapping module and the RCCPMA. has failed. Depending on the
corresponding messages received, go to
one of the following:
• RCCPMA, page 29-784
• Mapping Modules (MM),
page 29-794
• Redundant Mapping Modules
(RMM), page 29-807
ISOAUTOS Traffic was switch away from the Traffic was switched from the Faulted RCCPMA.
W RCCPM to run isolation RCCPMA to an available CCPMA in
order to isolate a fault detected on Go to RCCPMA, page 29-784.
another module.
MODINSRT Module Inserted The RCCPMA was removed but is now RCCPMA has been inserted in its slot on
76.5500/29, Rev R 7/07 Page 29-657


PROTDEG Protection Switching Degraded - This message will be seen when the The probable cause is a bad
Extra Switch Time Possible NPU dynamic data held on the communication path between the
CCPMA and RCCPMA is out of sync. CCPMA and RCCPMA modules.
The NPU dynamic data on the
RCCPMA must exactly match the NPU Go to RCCPMA, page 29-784.
dynamic data on the CCPMA, this
allows one module to quickly substitute
for another.
PROTNA RCCPM carrying FORCED Redundancy for the specified The SW-TOWKG-EQPT command has
switched traffic - not available for protection group is unavailable been used to force traffic to this
protection because the RCCPMA has been RCCPMA.
forced to carry traffic.
PROTNA RCCPM failed (ANR) - not Redundancy for the specified One of the following is the likely cause:
available for protection protection group is unavailable - RCCPMA has been entered while still
because the RMM3 is in an abnormal in the ANR state.
(ANR) state. - RCCPMA has been removed.
- A fault in the RCCPMA has been
detected by either the RCCPMA
firmware or by the GC software.
PROTNA RCCPM inhibited - not available for Redundancy for protection group is The INH-SWTOPROTN-EQPT
protection unavailable because PRTN parameter command has been used to inhibit
on the RPM is INH. protection by this RPM.
PROTNA RCCPM OOS - not available for Redundancy for the protection group is Either the RCCPMA has been entered
protection unavailable because the RMM is out of while still in the out-of-service state, or it
service. has been forced OOS by the ED-EQPT
command.
REVLVL Module revision level does not The revision level of the RCCPMA This RCCPMA is not supported by this
meet revision level requirements does not match the set of valid revision version of the software.
database. Use RTRV-REVTBL Go to RCCPMA, page 29-784.
command to view the system database
of valid RCCPMA revision levels.
Refer to Tellabs 5500/5500S
76.5500/13.
Page 29-658 7/07 76.5500/29, Rev R

Mapping Module (MM) Alarm Messages

6.27 In order to troubleshoot the alarm message(s) received for a faulted MM,
messages that can be generated for a MM. The second column lists a description
of the alarm messages, and the third column gives a probable cause for the alarm.
Table 6.35 Mapping Module Alarm Messages

MM. been disconnected.
Go to Mapping Modules (MM),

page 29-794.
MM. been disconnected.

page 29-794.
INT An Attention Line Hardware Error The MM has detected an attention There are hardware problems with the

page 29-794.
INT Card removed Active PGC has detected the The MM has been removed from its slot,
absence of the reporting MM. or it has not responded to communications
from the PGC, or its EEPROMS are
corrupt or incompatible with the current
software version.

page 29-794.
INT Connection Memory download There is a failure downloading the Defective MM.
failure MM connection memory.
page 29-794.
INT EEPROM failure Either a failure to read the EEPROM The EEPROM data on the MM module
information or a failure to store this has been corrupted.
occurred. Go to Mapping Modules (MM),
page 29-794.
INT Failed download Reporting MM requested download The PGC did not provide the download
255 times without success and could because the MM was UEQ and therefore
not be initialized. incompatible. If the MM was previously
NR, it has probably failed, and the PGC
will fault it.

page 29-794.
INT Failed module diagnostics The MM has failed self-diagnostics. The MM has failed.

page 29-794.
76.5500/29, Rev R 7/07 Page 29-659

Table 6.35 Mapping Module Alarm Messages (Continued)

INT Failed port framing to TSI Port framing to the TSI failed. The SDF framing mechanism on the MM
was unsuccessful.

page 29-794.
INT Failure to reprogram Communications between the GC The MM3 or MM24 was removed from the
MM<x>/RMM<x> network status and the MM3 or MM24 failed during shelf during the BBBC (Best Byte Best
during BBBC audit (where x = 3 or BBBC audit. Clock) audit. There is a hardware fault in
24) the GC to RMM3 or RMM24 UART
communications bus.

page 29-794.
INT Internal error An internal error has occurred Port module has not properly responded
because of a failure of a port module, to UART communication with the GC and
but PGC cannot isolate or confirm the problem cannot be isolated.
the failure.
page 29-794.
INT Internal failure Reporting triple mapping module - Download is being requested while the
(MM) has detected one of several port module is in a normal (NR) state.
possible errors. - Port module cannot communicate with its
GC.
- The MM module is experiencing an
STS1 or VT1 internal transmit or receive
error.
- The MM is experiencing an
unambiguous or global hardware fault.
- The MM is experiencing an UCOK fault,
an indication of possible processor failure.

page 29-794.
INT Internal signal degradation detected The TSIO or TSI96 device has If this alarm is declared against only one
at TSI from MM<x> (where x = 3 or detected constant TVT (Tellabs protecting redundant port module, then
24) virtual tributary) parity errors from a that module has probably failed. If the
protecting redundant port module. alarm is declared against several RMMs,
the TSIOs or TSI96s on that shelf are
suspect.

page 29-794, to troubleshoot the MM, or
go to Time Slot Interchange Module (TSI),
INT Internal signal failure detected at TSI The TSI has detected a loss of frame Either the port module identified or the TSI
from port module from a specific reporting module. has failed.

page 29-794, to troubleshoot the mapping
INT Link Failure detected at both MIMs A link failure from the MM has been Faulty MM.
from MM detected by both MIMs.
page 29-794.
Page 29-660 7/07 76.5500/29, Rev R


INT Link Failure detected from MIM A link failure from the MIM has been Faulty MIM.
detected.
Go to Mapping Interface Module (MIM),
page 29-815.
INT LOF detected from MIM LOF has been detected from the Either the port module or MIM is faulty.
MIM.
page 29-794.
INT LOF detected at both MIMs from MM LOFs have been detected at both The MM has failed internally.
MIMs from the MM.
page 29-794.
INT MIM detected Link Failure from MM A link failure from the MM has been Faulty MM.
detected by a MIM.
page 29-794.
INT MIM detected LOF from MM The MIM detected LOF from the MM. The MM has failed internally.

page 29-794.
INT MIM detected Parity Errors from MM The MIM detected parity errors from Either the MM or MIM has failed.
the MM.
page 29-794.
INT Module not compatible with existing This port module is not supported by Module revision level is either lower or
software the current software load. higher than the levels supported by the

page 29-794.
INT MM connection memory inconsistent The MM connection memory is Mismatches were detected on the MM for
with database inconsistent with the database. audited network side. A most likely cause
is that a change to the software database
was not correctly propagated to the MM
hardware.

page 29-794.
INT Network Copy Synchronization Error While trying to synchronize the The synchronization errors from the NC
Threshold Crossed network, the system had too many have exceeded the threshold.
page 29-794.
INT Parity errors detected at both MIMs Both MIMs have detected parity The MM has failed internally.
from MM errors from the MM.
page 29-794.
INT Parity errors detected from MIM Parity errors have been detected Either the port module or MIM is faulty.
from the MIM.
page 29-794.
76.5500/29, Rev R 7/07 Page 29-661


INT Parity error in Network Copy A Reporting module has detected a - Port module is bad and has incorrectly
detected at MM<x> (where x = 3 or parity error in the incoming signal calculated the parity.
24) from network copy A. - The TSIO is bad.
the TSIO is bad.

INT Parity error in Network Copy B Reporting module has detected a - Port module is bad and has incorrectly
detected at MM<x> (where x = 3 or parity error in the incoming signal calculated the parity.
24) from Network copy B. - The TSIO is bad.
the TSIO is bad.

INT SDF out of frame in Network Copy A Addressed port module is seeing Faulty port module.
SDF loss-of-frame errors on network
copy A. Go to Mapping Modules (MM),
page 29-794.
INT SDF out of frame in Network Copy B Addressed port module is seeing Faulty port module.
SDF loss-of-frame errors on network
copy B. Go to Mapping Modules (MM),
page 29-794.
INT SDF parity error in Network Copy A Addressed port module is seeing Faulty port module.
Side SDF parity errors on network copy A.
page 29-794.
INT SDF parity error in Network copy B Addressed port module is seeing Faulty port module.
Side SDF parity errors on network copy B.
page 29-794.
INT System clock error in Network Copy Reporting port module has detected If a single MM reports this, it is likely
A a system clock error in network copy faulty. If several report this, then either the
A. stage 5 TSI or one of the network

INT System clock error in Network Copy Reporting port module has detected If a single MM reports this, it is likely
B a system clock error in network copy faulty. If several report this, then either the
B. stage 5 TSI or one of the network

Page 29-662 7/07 76.5500/29, Rev R


INT System clock error from MIM A system clock error from the MIM Either the port module or MIM is faulty.
has been detected.
page 29-794.
MEA Inserted card type incompatible with Reporting port module is The shelf was not configured for this type
shelf type incompatible with the shelf into which of module.
it has been inserted, such as putting
an STS-1E port module into a shelf Go to Mapping Modules (MM),
of OC3 or OC12s. page 29-794.
MEA Module is inconsistent with currently The type of the reporting module Either the wrong module has been
assigned type differs from that assigned to this slot inserted or the wrong type assigned to
by the ENT-EQPT command. that slot.

page 29-794.
MEA Module is inconsistent with type of During a reset of the shelf containing The PM type of the reporting module in
associated RMM<x> (where x = 3 or the reporting module, a redundant this protection group does not match that
24) mapping module detected a of its assigned RMM. Refer to the
mismatch between the RMM type ED-EQPT::RMM command in Tellabs
and the PM types in its protection 5500/5500S Command Reference
group. Manual, 76.5500/13 for a list of compatible
RMM types for each PM type.
Caution:
The Tellabs stated position is that the
RMM must match the highest revision
level among the PMs in its protection
group, or traffic loss may occur.

page 29-794.
MODINSRT Module Inserted The module was removed, but is Module has been inserted in its slot on the
now in its slot on the shelf. shelf. No recovery necessary.
system database. Use Go to Mapping Modules (MM),
RTRV-REVTBL command to view page 29-794.
the system database of valid module
Manual, 76.5500/13.
76.5500/29, Rev R 7/07 Page 29-663

Redundant Mapping Module (RMM) Alarm Messages

6.28 In order to troubleshoot the alarm message(s) received for a faulted RMM,
messages that can be generated for a RMM. The second column lists a description
of the alarm messages, and the third column gives a probable cause for the alarm.
Table 6.36 Redundant Mapping Module Alarm Messages

RMM. been disconnected.
Go to Redundant Mapping Modules

(RMM), page 29-807.
RMM. been disconnected.

(RMM), page 29-807.
INT Card removed Active PGC has detected the absence The MM has been removed from its slot,
of the reporting MM. or it has not responded to communications
from the PGC, or its EEPROMS are
corrupt or incompatible with the current
software version.

(RMM), page 29-807.
INT Connection Memory download There is a failure downloading the RMM Defective RMM.
failure connection memory.
(RMM), page 29-807.
INT EEPROM failure Either a failure to read the EEPROM The EEPROM data on the MM has been
information or a failure to store this corrupted.
occurred. Go to Redundant Mapping Modules
(RMM), page 29-807.
INT Failed download Reporting MM requested download 255 The PGC did not provide the download
times without success and could not be because the MM was UEQ and therefore
initialized. incompatible. If the MM was previously
NR, it has probably failed, and the PGC
will fault it.

(RMM), page 29-807.
INT Failed module diagnostics The MM has failed self-diagnostics. The MM has failed.

(RMM), page 29-807.
INT Failure to reprogram Communications between the GC and The MM was removed from the shelf
MM3/RMM3 network status the MM failed during BBBC audit. during the BBBC (Best Byte Best Clock)
during BBBC audit audit. There is a hardware fault in the GC
to RMM UART communications bus.

(RMM), page 29-807.
Page 29-664 7/07 76.5500/29, Rev R

Table 6.36 Redundant Mapping Module Alarm Messages (Continued)

INT Internal error An internal error has occurred because Port module has not properly responded
of a failure of a port module, but PGC to UART communication with the GC and
cannot isolate or confirm the failure. the problem cannot be isolated.

(RMM), page 29-807.
INT Internal failure Reporting triple mapping module (MM) - Download is being requested while the
has detected one of several possible port module is in a normal (NR) state.
errors. - Port module cannot communicate with its
GC.
- The MM module is experiencing an STS1
or VT1 internal transmit or receive error.
- The MM is experiencing an unambiguous
or global hardware fault.
- The MM is experiencing an UCOK fault,
an indication of possible processor failure.

(RMM), page 29-807.
INT Internal signal degradation The TSIO device has detected constant If this alarm is declared against only one
detected at TSI from port module TVT (Tellabs virtual tributary) parity protecting redundant port module, then
errors from a protecting redundant port that module has probably failed. If the
module. alarm is declared against several RMMs,
the TSIOs on that shelf are suspect.

(RMM), page 29-807, to troubleshoot the
RMM, or go to Time Slot Interchange
Module (TSI), page 29-506 to troubleshoot
the TSI.
INT Link Failure detected at both A link failure from the RMM has been Faulty RMM.
MIMs from RMM detected by both MIMs.
(RMM), page 29-807.
INT LOF detected at both MIMs from LOFs have been detected at both MIMs The RMM has failed internally.
RMM from the RMM.
(RMM), page 29-807.

(RMM), page 29-807.
INT MM connection memory The RMM connection memory is Mismatches were detected on the RMM
inconsistent with database inconsistent with the database. for audited network side. A most likely
cause is that a change to the software
database was not correctly propagated to
the RMM hardware.

(RMM), page 29-807.
INT MIM detected Link Failure from A link failure from the MIM has been Faulty RMM.
RMM detected.
(RMM), page 29-807.
76.5500/29, Rev R 7/07 Page 29-665


INT MIM detected LOF from RMM The MIM detected LOF from the RMM. The RMM has failed internally.

(RMM), page 29-807.
INT MIM detected Parity Errors from The MIM detected parity errors from the Either the RMM or MIM has failed.
RMM RMM.
(RMM), page 29-807.

(RMM), page 29-807.
INT Network Copy Synchronization While trying to synchronize the network, The synchronization errors from the NC
Error Threshold Crossed the system had too many have exceeded the threshold.
(RMM), page 29-807.
INT Parity Errors detected at both Both MIMs have detected parity errors The RMM has failed internally.
MIMs from RMM from the RMM.
(RMM), page 29-807.
INT Parity errors detected from MIM Parity errors have been detected from Either the port module or MIM is faulty.
the MIM.
(RMM), page 29-807.
INT Parity error in Network Copy A Reporting module has detected a parity Port module is bad and has incorrectly
detected at MM3 error in the incoming signal from calculated the parity. The TSIO is bad.
network copy A. The fiber cable between the ESM and the
TSIO is bad.

INT Parity error in Network Copy B Reporting module has detected a parity Port module is bad and has incorrectly
detected at MM3 error in the incoming signal from calculated the parity. The TSIO is bad.
Network copy B. The fiber cable between the ESM and the
TSIO is bad.

INT SDF out of frame in Network Addressed port module is seeing SDF Faulty port module.
Copy A loss-of-frame errors on network copy A.
(RMM), page 29-807.
INT SDF out of frame in Network Addressed port module is seeing SDF Faulty port module.
Copy B loss-of-frame errors on network copy B.
(RMM), page 29-807.
Page 29-666 7/07 76.5500/29, Rev R


INT SDF parity error in Network Addressed port module is seeing SDF Faulty port module.
Copy A Side parity errors on network copy A.
(RMM), page 29-807.
INT SDF parity error in Network copy Addressed port module is seeing SDF Faulty port module.
B Side parity errors on network copy B.
(RMM), page 29-807.
been detected.
(RMM), page 29-807.
INT System clock error in Network Reporting port module has detected a If a single MM reports this, it is likely faulty.
Copy A system clock error in network copy A. If several report this, then either the stage
fault.

INT System clock error in Network Reporting port module has detected a If a single MM reports this, it is likely faulty.
Copy B system clock error in network copy B. If several report this, then either the stage
fault.

ISOAUTOS Traffic was switched away from Traffic was switched from the RMM to Faulted MM.
W the RMM to run isolation an available MM in order to isolate a
fault detected on another module. Go to Mapping Modules (MM),
page 29-794.
inserted, such as putting an STS-1E
port module into a shelf of OC3 or Go to Redundant Mapping Modules
OC12s. (RMM), page 29-807.
MEA Module inconsistent with The type of the reporting module differs Either the wrong module has been
currently assigned type from that assigned to this slot by the inserted or the wrong type assigned to that

(RMM), page 29-807.
MODINSRT Module Inserted The module was removed but is now in Module has been inserted in its slot on the
76.5500/29, Rev R 7/07 Page 29-667


RTRV-REVTBL command to view the Go to Redundant Mapping Modules
system database of valid module (RMM), page 29-807.
Manual, 76.5500/13.
PROTNA RMM Active in FRCD mode - not Redundancy for the specified protection SW-TOPROTN-EQPT command has
available for protection group is unavailable because the RMM3 been used to force traffic to this RMM. An
has been forced to carry traffic. MM3 with IS terminations was forced
OOS, and has forced the RMM to carry
traffic.

(RMM), page 29-807.
PROTNA RMM failed (ANR) - not available Redundancy for the specified protection One of the following is the likely cause:
for protection group is unavailable because the RMM3 - RMM has been entered while still in the
is in an abnormal (ANR) state. ANR state.
- RMM has been removed.
- A fault in the RMM has been detected by
GC software.

(RMM), page 29-807.
PROTNA RMM OOS - not available for Redundancy for the protection group is Either the RMM has been entered while
protection unavailable because the RMM is out of still in the out-of-service state, or it has
service. been forced OOS by the ED-EQPT
command.

(RMM), page 29-807.
Page 29-668 7/07 76.5500/29, Rev R

Mapping Interface Module (MIM) Alarm Messages

6.29 In order to troubleshoot the alarm message(s) received for a faulted MIM,
messages that can be generated for a MIM. The second column lists a description
Table 6.37 Mapping Interface Module Alarm Messages

MIM. been disconnected.

page 29-1105.
MIM. been disconnected.

page 29-1105.
INT An Attention Line Hardware Error The MIM has detected an attention There are hardware problems with the

page 29-815.
INT Card Removed Active PGC has detected the absence The MIM has been removed from its slot,
of the reporting MIM. or it has not responded to

page 29-815.
INT Connection Memory download There is a failure downloading the Defective MIM.
failure MIM connection memory.
page 29-815.
INT EEPROM failure The EEPROM chip contains One or more of the following has
information about the module. When a occurred:
new module is inserted, the PGCU - The MIM has failed.
reads the EEPROMS to load the data - The EEPROM data is corrupt.
into the database. If the PGCU has
failed to read the EEPROM data or Go to Mapping Interface Module (MIM),
has failed to validate the data, then page 29-815.
this failure will be detected.
INT Failed module diagnostics Module has failed self-diagnostics. The module has failed.

page 29-815.
INT Failure to reprogram MIM during Communications between the GC and The MIM was removed from the shelf
Best Clock audit the MIM failed during Best Clock audit. during the Best Clock audit. There is a
hardware fault in the GC to MIM UART
communications bus.

page 29-815.
76.5500/29, Rev R 7/07 Page 29-669

Table 6.37 Mapping Interface Module Alarm Messages (Continued)

INT Internal failure Reporting module is detecting one of One of the following is the likely cause:
several possible errors, but cannot - Download requested while module is in
- MIM cannot communicate with its PGC.
- MIM experiencing internal transmit or
receive error.

page 29-815.
INT Link Failure detected at both A link failure from both the MM and Faulty MM, RMM, or MIM.
MM/RMM from MIM RMM has been detected.
page 29-794, to troubleshoot the MM or
RMM, or go to Mapping Interface Module
(MIM), page 29-815, to troubleshoot the
MIM.
INT LOF detected at both EPM/REPM LOF has been detected at both The MIM has failed internally.
from MIM REPM/EPM from the MIM.
page 29-815.
INT LOF detected at both MM/RMM LOF has been detected at both The MIM has failed internally.
from MIM MM/RMM from the MIM.
page 29-815.
INT LOF detected at both OPMs from LOF has been detected at both OPMs The MIM has failed internally.
MIM from the MIM.
page 29-815.
INT Loss of clock detected at MIM from MIM has detected a loss of clock from The TSI has lost its clock. Depending on
TSI-A TSI-A. the configuration of the system, check
the TSI, NTDM, ESM, CCSM, and PAM.
(NTDM), page 29-292
page 29-332
(CCSM), page 29-394
page 29-405
• Time Slot Interchange Module (TSI),
page 29-506
Page 29-670 7/07 76.5500/29, Rev R


INT Loss of clock detected at MIM from MIM has detected a loss of clock from The TSI has lost its clock. Depending on
TSI-B TSI-B. the configuration of the system, check
the TSI, NTDM, ESM, CCSM, and PAM.
(NTDM), page 29-292
page 29-332
(CCSM), page 29-394
page 29-405
• Time Slot Interchange Module (TSI),
page 29-506
INT MIM connection memory The MIM connection memory is Mismatches were detected on the MIM
inconsistent with database inconsistent with the database. for audited network side. A most likely
cause is that a change to the software
database was not correctly propagated to
the MIM hardware.

page 29-815.
INT Module not compatible with existing This module is not supported by the Module revision level is either lower or

page 29-815.
INT Parity Errors detected at both Parity errors have been detected at The MIM has failed internally.
EPM/REPM from MIM both EPM/REPM from the MIM.
page 29-815.
INT Parity Errors detected at both Parity errors have been detected at The MIM has failed internally.
MM/RMM from MIM both MM/RMM from the MIM.
page 29-815.
INT Parity Errors detected at both OPMs Parity errors have been detected at The MIM has failed internally.
from MIM both OPMs from the MIM.
page 29-815.
INT System clock error in Network Copy Reporting module has detected a If a single module reports this, it is likely
A system clock error in network copy A. faulty. If several modules report this, then

page 29-815, to troubleshoot the MIM, or
go to Time Slot Interchange Module
TSI.
76.5500/29, Rev R 7/07 Page 29-671


INT System clock error in Network Copy Reporting module has detected a If a single module reports this, it is likely
B system clock error in network copy B. faulty. If several modules report this, then

page 29-815, to troubleshoot the MIM, or
go to Time Slot Interchange Module
TSI.
PROTNA MIM OOS - not available for Redundancy for the mate MIM has The MIM has been commanded
protection been lost because the MIM is in an out-of-service using the ED-EQPT
out-of-service (OOS) state. command. That is a transition from
IS-NR-ACT to OOS-NR.

page 29-815.
PROTNA MIM failed (ANR) - not available for Redundancy for the mate MIM has One or more of the following has
protection been lost because the MIM is in an occurred:
abnormal (ANR) state. - The MIM has been removed from its
slot.
- The MIM has failed.

page 29-815.
MEA Module is inconsistent with currently The type of the reporting module Either the wrong module has been
assigned type differs from that assigned to this slot inserted or the wrong type assigned to
by the ENT-EQPT command. that slot.

page 29-815.
MODINSRT Module Inserted The module was removed but is now Module has been inserted in its slot on
database. Use RTRV-REVTBL Go to Mapping Interface Module (MIM),
76.5500/13.
Page 29-672 7/07 76.5500/29, Rev R

Pluggable Transceiver (PT) Alarm Messages

pluggable transceiver (PT), use the following table. The first column of the table
lists the possible alarm messages that can be generated for a MIM. The second
column lists a description of the alarm message. The third column gives a probable
cause for the alarm.
Table 6.38 Pluggable Transceiver Alarm Messages

INT EEPROM failure detected The EEPROM chip contains information One or more of the following has occurred:
about the module. When a new module is - The PT has failed.
inserted, the PGCO reads the EEPROM - The EEPROM data is corrupt.
to load the data into the database. If the
PGCO has failed to either read the Go to Pluggable Transceiver (PT),
EEPROM data or has failed to validate page 29-835.
the data then this failure will be detected.
INT Internal failure detected The PT module has an internal failure Internal failure of module hardware.
detected.
page 29-835.
INT Internal transmitter failure The PT module has an internal Internal transmitter failure of module
detected transmitter failure detected. hardware.

page 29-835.
INT Module is incompatible with The PT module is not supported by the Need to check the compatibility between
existing software feature package software currently modules and Feature Package software at
operating on the system. installation. Refer to Tellabs 5500/5500S
Software Release Document, 76.5500/16
for the system’s minimum revision levels
of modules supported by the current
Feature Package.

page 29-835.
INT Module removed Active PGC has detected the absence of A PT module has been removed from its
a PT module. slot, or it has not responded to

page 29-835.
INT SDF48 Loss of Frame detected The PT has detected an LOF on the One or more of the following has occurred:
at fiber SDF48 cable. - Module supporting the PT is losing
framing.
damaged.

page 29-835, to troubleshoot the PT.
76.5500/29, Rev R 7/07 Page 29-673

Table 6.38 Pluggable Transceiver Alarm Messages (Continued)

INT SDF48 Loss of Multi-Frame The PT has detected two consecutive H4 Either the quality of the signal received
detected at fiber values that do not agree with any part of from the connected module is poor, or the
the multiframe sequence, and it has PT has failed.
declared a loss of multiframe (LOMF)
defect. Go to Pluggable Transceiver (PT),
page 29-835.
INT SDF48 Loss of Signal detected A Loss of Signal has been declared at the Disconnected or broken cable.
at fiber fiber of the PT.
page 29-835.
INT SDF48 mismatch detected at An SDF48 cable is connected to the An SDF48 cable has been connected to
fiber wrong port. the wrong port.
INT SDF48 Parity Error detected at SDF parity errors were detected at the Either the module supporting the PT, or
fiber fiber of the PT. the connected module, is faulty.

Go to the appropriate section to

troubleshoot the supporting module or the
connected module.
INT SDF48 Yellow Frame detected The PT has declared a Yellow Frame on Either the PT, the connected module, or
at fiber its fiber. the supporting module is faulty.


connected module.
INT SDF48 Yellow Multi-Frame The PT has declared a Yellow Either the module supporting the PT, or
detected at fiber Multi-Frame on its fiber. the connected module, is faulty.


connected module.
assigned type from that assigned to this slot by the inserted or the wrong type assigned to that

page 29-835.
MODINSRT Module inserted The module was removed but is now in Module has been inserted in its slot on the
meet revision level match the set of valid revision levels version of the software.
RTRV-REVTBL command to view the Go to Pluggable Transceiver (PT),
system database of valid module revision page 29-835.
76.5500/13.
Page 29-674 7/07 76.5500/29, Rev R

Fan Tray Module and Air Filter Alarm Messages

6.31 In order to troubleshoot the alarm message(s) received for a faulted fan
tray module, use the following table. The first column of the table lists the possible
alarm messages that can be generated for a fan tray module. The second column
lists a description of the alarm messages. The third column gives a probable cause
for the alarm.
Table 6.39 Fan Tray Module Alarm Messages

FAN Fan module has more than one There are multiple internal failures There are multiple fan failure on the
internal failure on the fan module module.
FAN Fan module has single internal There is a single internal failure on There is one fan failure on the module.
failure the fan module.
FAN Fan module removed Active PGC has detected the Port module has been removed from its
absence of a fan module. slot, or it has not responded to
fan tray module. been disconnected.
fan tray module. been disconnected.
FLTREMV Air filter removed The air filter has been removed Refer to Tellabs 5500 Maintenance,
from the fan tray. 76.5500/24, to replace the fan filter.
MAR Air filter routine maintenance The air filter requires routine The air filter time period has expired and
required maintenance. the air filter needs to be replaced.
system database. Use Go to Fan Tray Module, page 29-843.
RTRV-REVTBL command to view
the system database of valid
module revision levels. Refer to
76.5500/29, Rev R 7/07 Page 29-675

Electrical Port Modules (DS1, DD DS1, DS3, STS-1, or EPM)

6.32 In this section, you will troubleshoot the alarmed DS1 port module (PM),
DD DS1 PM, DS3 PM, STS-1 PM, or EPM.
6.33 A spare module may be required in order to perform this procedure. Refer
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
command:
System response:
M ctag COMPLD

__ 2.1 Verify that your login is a UPC of A8 or higher.
__ 2.2 If your UPC is not A8 or higher, contact your system

Page 29-676 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

__ 3.1 If there are no alarm conditions posted against the port

module, follow your company's prescribed procedures
__ 3.2 If there are alarm conditions posted against the port

module, go to step 4.
__ 4. Retrieve the status of the redundant port module (RPM) associated

with the faulted port module by entering the following command:
RTRV-EQPT::eeeeeee-xxxx:ctag;
Where: eeeeeee = Module type (RPM1 for DS1 port module, RPM1D
for double-density DS1 port module, RPM3 for
DS3 port module, REPMX24 for electrical port
module, RPME for STS-1E port module).
System response:
M ctag COMPLD

"RPM3-0193:TYPE=331A:HWV=82.5517A RI,SN=MI0372133,DT=980523,ALMPF=99,
PRTN=ALW,PRTN_PORT=PM3-0193,PRTN_TYPE=AUTO:PST=IS-NR-ACT"
__ 4.1 If the system response verifies that the module is

in-service, normal, active (IS-NR-ACT), go to step 6,
page 29-678.

in-service, normal, standby (IS-NR-STBY), go to step 5,
page 29-678.

abnormal (ANR), go to step 1, page 29-694.
76.5500/29, Rev R 7/07 Page 29-677

__ 5. Switch the faulted port module to protection by entering the following

command:
following commands:
SW-TOPROTN-EQPT::PM1-xxxx-yy:ctag;
SW-TOPROTN-EQPT::PM1D-xxxx-yy:ctag;
Where: xxxx = SDF number of the module or quadrant.

yy = First DS1 serviced by the PM.
__ 5.2 For a DS3 PM, STS-1 PM, or EPM, enter one of the
following commands:
SW-TOPROTN-EQPT::PM3-xxxx:ctag;
SW-TOPROTN-EQPT::PME-xxxx:ctag;
SW-TOPROTN-EQPT::EPMX24-xxxx:ctag;
System response:
M ctag COMPLD
__ 6. From the system response retrieved in step 4, page 29-677, verify the
following:
__ 6.1 If the system response for the RPM verifies that the
PRTN_PORT equals the SDF number of the faulted
port modules, go to step 7, page 29-679.
PRTN_PORT is not the SDF number of the faulted port
module, then another port module has previously failed
and has already switched to protection. Verify traffic
exists on that port module.
__ 6.2.1 If traffic exists on the port module,

troubleshoot that port module first, then
return to step 1, page 29-676.
Page 29-678 7/07 76.5500/29, Rev R

__ 6.2.2 If traffic does not exist on the port

module, enter the following command to
free up the protection module:
INH-SWTOPROTN-EQPT::eeeeeee-xxxx:ctag;
Where: eeeeeee = Module type(RPM1 for DS1 port module, RPM1D

System response:
M ctag COMPLD

"PM3-0194:INHSWPR,SC,01-02,15-29-54,NEND:\"The switch to protection for the entity is
inhibited\":,ISLTD"
__ 6.2.3 Return to step 4, page 29-677.
Note: Troubleshoot the single port module address listed in the PRTN_PORT
parameter system response throughout the entire procedure or until
directed otherwise.
__ 7. Retrieve the status of the faulted module by entering one of the

following commands depending on what module type is faulted:
__ 7.1 For a faulted DS1 or Double-density DS1 PM, enter one
of the following commands:

.
__ 7.2 For a faulted DS3 PM, STS-1 PM, or EPM, enter one of
the following commands:
RTRV-EQPT::EPMX24-xxxx:ctag;

"PM1-0017-01:TYPE=11:HWV=81.5514 RB,SN=EL0210372,DT=910507,ALMPF=99,PRTN=ALW,
PMPI=PASSIVE:PST=OOS-NR"
__ 7.3 If the present state of the faulted port module is

in-service, abnormal, equipped, standby
(IS-ANR-EQ-STBY), go to step 8, page 29-680.
76.5500/29, Rev R 7/07 Page 29-679


in-service, abnormal, unequipped (IS-ANR-UEQ), go to

(OOS-ANR-UEQ-AS), go to step 10, page 29-682.

(OOS-ANR-EQ-AS), go to step 20, page 29-685.

page 29-688.

in-service, normal, standby (IS-NR-STBY), go to step
26, page 29-690.

page 29-692.

__ 8. Edit the faulted module out-of-service (OOS) by entering one of the

__ 8.1 For a faulted DS1 or Double-density DS1 PM, enter one
ED-EQPT::PM1-xxxx-yy:ctag::::OOS;
ED-EQPT::PM1D-xxxx-yy:ctag::::OOS;
Where: xxxx = SDF number of the quadrant being edited.

Page 29-680 7/07 76.5500/29, Rev R

ED-EQPT::PM3-xxxx:ctag::::OOS;
ED-EQPT::PME-xxxx:ctag::::OOS;
ED-EQPT::EPMX24-xxxx:ctag::::OOS;

M ctag COMPLD

__ 8.2.1 Press Y for Yes to execute this

command.
M ctag COMPLD
__ 9. Retrieve the status of the faulted module by entering one of the

__ 9.1 For a faulted DS1 or Double-Density DS1 PM, enter one

RTRV-EQPT::EMPX24-xxxx:ctag;
System response:
M ctag COMPLD

PMPI=PASSIVE:PST=OOS-ANR-EQ-AS"
76.5500/29, Rev R 7/07 Page 29-681



(OOS-ANR-UEQ-AS), go to step 10.


page 29-685.

page 29-683.
__ 11. Remove the faulted module.

place.

steps:
backplane.


backplane?


perform one of the following steps:
__ 12.3.3 If the removed module is not to be

reinserted and a new module is to be
used, go to step 13, page 29-683.
__ 12.3.4 If the removed module is going to be

reinserted, go to step 14, page 29-683.
Page 29-682 7/07 76.5500/29, Rev R

__ 13. Determine which module type is to be inserted into the empty slot by
referring to Table 6.1, page 29-576.
__ 13.1 Refer to Tellabs 5500/5500S Software Release
Document, 76.5500/16, to verify the correct revision
level of the module needed, depending on feature
package and what shelf type you are troubleshooting.
__ 13.2 Choose one of the following options:
__ 13.2.1 If the module type is not the same as the

module removed in step 11,
page 29-682, or the slot is not
provisioned for the proper module type,
__ 13.2.2 If the module type is the same as the

page 29-682, go to step 16,
page 29-684.
__ 14. Check the module that is to be reinserted for physical damage by

verifying the following:
__ 14.1 Do the module backplane connectors appear to contain
any physical damage?
__ 14.2 Are any structural or mechanical pieces on the module

loose or missing?
__ 14.3 Are any module LEDs loose or missing?
__ 14.4 If the module contains heat sinks, are any of the heat
sinks loose or misaligned?
__ 14.5 If the answer is yes to any of the above questions, the

module is damaged and you will need to replace it.
Return to step 13, page 29-683.
__ 14.6 If the answer is no to all of the above questions, go to

step 16.
__ 15. Delete the module type provisioned in the slot by entering one of the
following commands, depending on the module type:
__ 15.1 For a DS1 or Double-Density DS1 PM, enter one of the
following commands:
DLT-EQPT::PM1-xxxx-yy:ctag;
DLT-EQPT::PM1D-xxxx-yy:ctag;

yy = First DS1 serviced by the PM.
76.5500/29, Rev R 7/07 Page 29-683

__ 15.2 For a DS3 PM, an STS-1 PM, or an EPM, enter one of

DLT-EQPT::PM3-xxxx:ctag;
DLT-EQPT::PME-xxxx:ctag;
DLT-EQPT::EPMX24-xxxx:ctag;
System response:
M ctag COMPLD
Note: If this is a HDPS and the module type provisioned is an OPM12X4, refer
to Tellabs 5500/5500S Provisioning Manual, 76.5500/23.
__ 17. After a two minute module download, what is the front panel LED
Note: After entering the following command, the module front panel LEDs light
for approximately 10 seconds. This is normal behavior.
__ 18. Retrieve the status of the port module by entering the following
command:
RTRV-EQPT::PM1D-xxxx:ctag;
System response:
M ctag COMPLD

"PM1D-0001-01:TYPE=11DD:HWV=81.5514DD,SN=LI0012970,DT=970123, ALMPF=99,PRTN=ALW,
PMPI=PASSIVE:PST=IS-NR-STBY"
Page 29-684 7/07 76.5500/29, Rev R

__ 18.1 If the present state of the port module is in-service (IS),

__ 18.2 If the present state of the port module is out-of-service

__ 19. Edit the port module out-of-service (OOS) by entering one of the
following commands depending on the module type:
following commands:
ED-EQPT::PM1-xxxx-yy:ctag::::OOS;
ED-EQPT::PM1D-xxxx-yy:ctag::::OOS;
Where: xxxx = SDF of the quadrant being diagnosed.

yy = Module being diagnosed (1, 5, 9, 13, 17, 21, or
25).
following commands:
ED-EQPT::PM3-yyyy:ctag::::OOS;
ED-EQPT::PME-yyyy:ctag::::OOS;
ED-EQPT::EPMX24-yyyy:ctag::::OOS;
Where: yyyy = SDF of the faulted module.
System response:
M ctag COMPLD

"RPM1D-0001:MN,PROTNA,NSA,10-20,10-57-31,NEND:\"RPM carrying FORCED switched traffic
- not available for protection\":,ISLTD"
__ 20. Diagnose the problem on the port module by entering one of the
following commands:
DGN-EQPT::PM1-xxxx-yy:ctag::,ITER=3;
DGN-EQPT::PM1D-xxxx-yy:ctag::ITER=3;

25).
76.5500/29, Rev R 7/07 Page 29-685

following commands:
DGN-EQPT::PM3-yyyy:ctag::,ITER=3;
DGN-EQPT::PME-yyyy:ctag::,ITER=3;
DGN-EQPT::EPMX24-yyyy:ctag::,ITER=3;
Where: yyyy = SDF of the faulted module.
System response:
M ctag COMPLD

"PM1-0009:PASS-3"
"PM1-0009:FAIL-0"
__ 20.3 If this is the first module replaced, and the system

response shows any failed iterations, go to step 21.
__ 20.4 If this is the second module replaced, and the system

response still shows any failed iterations, follow your

__ 20.6 If the system response says “Parameter is inconsistent

with the type of module,” go to step 11, page 29-682.

__ 22. Diagnose the problem on the port module by entering one of the
following commands:
DGN-EQPT::PM1-xxxx-yy:ctag;
DGN-EQPT::PM1D-xxxx-yy:ctag;

25).
Page 29-686 7/07 76.5500/29, Rev R

following commands:
DGN-EQPT::PM3-xxxx:ctag;
DGN-EQPT::PME-xxxx:ctag;
DGN-EQPT::EPMX24-xxxx:ctag;
Where: xxxx = SDF of the faulted module.
System response:
M ctag COMPLD

"PM1-0009:PASS-1"
"PM1-0009:FAIL-0"

failed iteration, return to step 11, page 29-682.

__ 23. Retrieve the status of the new module by entering one of the following
commands depending on the module type:
following commands:

yy = First DS1 serviced by the new PM.
76.5500/29, Rev R 7/07 Page 29-687

__ 23.2 For a DS3 PM, an STS-1 PM, or an EPM, enter one of

Where: xxxx = SDF number of the new module.
System response:
M ctag COMPLD

PMPI=PASSIVE:PST=OOS-NR"
__ 23.3 If system response for the new port module is

__ 23.4 If system response for the new port module is anything

other than out-of-service, normal (OOS-NR), follow your
__ 24. Edit the new module in-service (IS) by entering one of the following
following commands:
ED-EQPT::PM1-xxxx-yy:ctag::::IS;
ED-EQPT::PM1D-xxxx-yy:ctag::::IS;

following commands:
ED-EQPT::PM3-xxxx:ctag::::IS;
ED-EQPT::PME-xxxx:ctag::::IS;
ED-EQPT::EPMX24-xxxx:ctag::::IS;
System response:
M ctag COMPLD
Page 29-688 7/07 76.5500/29, Rev R

following commands:

.
following commands:
System response:
M ctag COMPLD

PMPI=PASSIVE:PST=IS-NR-STBY"
__ 25.3 If the system response for the port module is in-service,

page 29-690.

normal, active (IS-NR-ACT), go to step 30,
page 29-692.

normal (IS-NR) and PRTN=INH, enter one of the
following commands:
ALW-SWTOPROTN-EQPT::PM1-xxxx-yy:ctag;
ALW-SWTOPROTN-EQPT::PM1D-xxxx-yy:ctag;
ALW-SWTOPROTN-EQPT::PM3-xxxx:ctag;
ALW-SWTOPROTN-EQPT::PME-xxxx:ctag;
ALW-SWTOPROTN-EQPT::EPMX24-xxxx:ctag;

yy = First DS1 serviced by the port module.
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-689

__ 26. Retrieve the status of the RPM associated with the faulted port module
by entering one of the following commands:
System response:
M ctag COMPLD

"RPM1-0017:TYPE=11:HWV=81.5514,SN=EL0210350,DT=910507,ALMPF=99,PRTN=ALW,PRTN_PORT=
NONE,PRTN_TYPE=NULL:PST=IS-NR-STBY"

page 29-692.

page 29-690.
Caution:
Performing the following step may cause port module traffic interruption. Follow
internal policy for redundancy switching.
Note: After entering the following command, the active LED on the RPM turns off
while the active LED on the PM lights.
__ 27. Perform a protection switch on the new module by entering one of the
following commands:
SW-TOWKG-EQPT::PM1-xxxx-yy:ctag;
SW-TOWKG-EQPT::PM1D-xxxx-yy:ctag;

Page 29-690 7/07 76.5500/29, Rev R

following commands:
SW-TOWKG-EQPT::PM3-xxxx:ctag;
SW-TOWKG-EQPT::PME-xxxx:ctag;
SW-TOWKG-EQPT::EPMX24-xxxx:ctag;
System response:
M ctag COMPLD
following commands:

following commands:
System response:
M ctag COMPLD

PMPI=PASSIVE:PST=IS-NR-ACT"

page 29-692.
__ 28.4 If the system response for the port module is not

in-service, normal, active (IS-NR-ACT), follow your
76.5500/29, Rev R 7/07 Page 29-691

__ 29. Retrieve the status of the RPM associated with the new port module
System response:
M ctag COMPLD

"RPM1-0017:TYPE=11:HWV=81.5514,SN=EL0210350,DT=910507,ALMPF=99,PRTN=ALW,PRTN_PORT=
NONE,PRTN_TYPE=NULL:PST=IS-NR-ACT"
__ 29.1 If the system response for the RPM is in-service,

normal, active (IS-NR-ACT) and the PRTN_PORT
equals the SDF number of the faulted port module, go
PRTN_PORT does not equal the SDF number of the
faulted port module, then another port module has
previously failed and has already switched to protection.
Return to step 1, page 29-676, to troubleshoot the
problem.

page 29-692.


M ctag COMPLD

M ctag COMPLD


message.
__ 30.1.2 If no, go to step 31.
Page 29-692 7/07 76.5500/29, Rev R



End of Procedure
76.5500/29, Rev R 7/07 Page 29-693

Redundant Electrical Port Modules (DS1, DD DS1, DS3, STS-1, REPM)

6.34 In this section, you will troubleshoot the alarmed redundant DS1 port
module (PM), DD DS1 PM, DS3 PM, STS-1 PM, or REPM.
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
command:
System response:
M ctag COMPLD


Page 29-694 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

"RPME-0035,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"

redundant port module, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070
__ 3.2 If there are alarm conditions posted against the

redundant port module, go to step 4.
__ 4. Retrieve the status of the RPM by entering the following command:

xxxx = SDF number assigned to the RPM.
System response:
M ctag COMPLD

PRTN_PORT=PM1-0009-5,PRTN_TYPE=AUTO:PST=IS-NR-ACT"
__ 4.1 If the present state of the RPM is in-service, abnormal,

equipped, standby (IS-ANR-EQ-STBY), go to step 5,
page 29-696.
__ 4.2 If the present state of the RPM is in-service, abnormal,

unequipped (IS-ANR-UEQ), go to step 5, page 29-696.
__ 4.3 If the present state of the RPM is out-of-service,

abnormal, unequipped, assigned

abnormal, equipped, assigned (OOS-ANR-EQ-AS), go
__ 4.5 If the present state of the RPM is out-of-service, normal

76.5500/29, Rev R 7/07 Page 29-695

__ 4.6 If the present state of the RPM is in-service, normal,

standby (IS-NR-STBY), go to step 19, page 29-701.
__ 4.7 If the present state of the RPM is in-service, normal,

active (IS-NR-ACT), go to step 19, page 29-701.

__ 5. Edit the RPM out-of-service (OOS) by entering the following

command:
ED-EQPT::eeeeeee-xxxx:ctag::::OOS;
M ctag COMPLD

M ctag COMPLD

System response:
M ctag COMPLD

PRTN_PORT=PM1-0009-5,PRTN_TYPE=AUTO:PST=OOS-ANR-EQ-AS"


Page 29-696 7/07 76.5500/29, Rev R


__ 7. Visually verify that there is an RPM present in the slot.

__ 7.1 If there is an RPM in the slot, go to step 8, page 29-697.
__ 7.2 If there is no RPM in the slot, go to step 10,

page 29-697.
Warning:
__ 8. Remove the RPM.

place.

steps:
backplane.

backplane?


continue to the next step.
76.5500/29, Rev R 7/07 Page 29-697

__ 10.2.1 If the module type is not the same type as

the module removed in step 8, or if the
slot is not provisioned for the proper
module type, follow your company's
__ 10.2.2 If the module type is the same type as the

module removed in step 8, go to step 11,
page 29-698.

__ 11.1 Does the module backplane connectors appear to
contain any physical damage?

loose or missing?

Return to step 10.

step 12.
status of the RPM?
Page 29-698 7/07 76.5500/29, Rev R

__ 14. Diagnose the problem on the RPM by entering the following

command:
DGN-EQPT::eeeeeee-xxxx:ctag::,ITER=3;
System response:
M ctag COMPLD

"RPM1-0009:PASS-3"
"RPM1-0009:FAIL-0"
__ 14.1 If this is the first redundant port module replaced, and

the system response shows any failed iterations, go to
step 15.
__ 14.2 If this is the second redundant port module replaced,

and the system response still shows any failed
iterations, follow your company's prescribed procedures

76.5500/29, Rev R 7/07 Page 29-699


command:
DGN-EQPT::eeeeeee-xxxx:ctag::,ITER=1;
System response:
M ctag COMPLD

"RPM1-0009:PASS-1"
"RPM1-0009:FAIL-0"


System response:
M ctag COMPLD

"RPM1-0017:TYPE=11:HWV=81.5514,SN=EL0210350,DT=910507,ALMPF=99,PRTN=ALW,
PRTN_PORT=NONE,PRTN_TYPE=NULL:PST=OOS-NR"
__ 17.1 If the system response for the RPM is out-of-service,

normal (OOS-NR), go to step 18, page 29-701.
__ 17.2 If the system response for the RPM is in-service, normal

(IS-NR), go to substep 19.1, page 29-701.
__ 17.3 If the system response for the RPM is abnormal (ANR),

Page 29-700 7/07 76.5500/29, Rev R

__ 18. Edit the RPM in-service (IS) by entering the following command:
ED-EQPT::eeeeeee-xxxx:ctag::::IS;
System response:
M ctag COMPLD
Note: System generates termination SENA alarm CLR messages during certain
System response:
M ctag COMPLD

"RPM1-0017:TYPE=11:HWV=81.5514,SN=EL0210350,DT=910507,ALMPF=99,PRTN=INH,
PRTN_PORT=NONE,PRTN_TYPE=NULL:PST=IS-NR-STBY"
__ 19.1 If the system response for the redundant port module is

in-service, normal, standby (IS-NR-STBY) and the
PRTN=INH, go to step 20, page 29-702.

in-service, normal, standby (IS-NR-STBY) and
PRTN=ALW, go to step 24, page 29-704.
__ 19.3 If the system response is anything other than the

system responses listed above, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070
76.5500/29, Rev R 7/07 Page 29-701

__ 20. Release the inhibit on the RPM by entering the following command:
Note: After entering the following command, the system generates termination
SENA alarm CLR messages during certain instances of troubleshooting.
ALW-SWTOPROTN-EQPT::eeeeeee-xxxx:ctag;
System response:
M ctag COMPLD
System response:
M ctag COMPLD

"RPM1-0009-5:TYPE=11:HWV=81.5514 RB,SN=FL0005886,DT=910627,ALMPF=99,PRTN=ALW,
PRTN_PORT=NONE,PRTN_TYPE=ALW:PST=IS-NR-STBY"

normal, standby (IS-NR-STBY) and PRTN=ALW, go to
step 24, page 29-704.

normal, active (IS-NR-ACT) and PRTN=ALW, go to
step 22, page 29-703.
__ 21.3 If the system response for the PRTN is anything other

than ALW, follow your company's prescribed
__ 21.4 If the system response for the present state is anything

other than in-service, normal, standby (IS-NR-STBY) or
page 29-695.
Page 29-702 7/07 76.5500/29, Rev R

__ 22. Perform a protection switch by entering the following commands

depending on the moduel type:
SW-TOWKG-EQPT::PM1-xxxx-yy:ctag;
SW-TOWKG-EQPT::PM1D-xxxx-yy:ctag;
SW-TOWKG-EQPT::PM3-xxxx:ctag;
SW-TOWKG-EQPT::PME-xxxx:ctag;
SW-TOWKG-EQPT::EPMX24-xxxx:ctag;
Where: xxxx = SDF number listed in the output from step 21,
page 29-702.
yy = First DS1 serviced by the port module.
System response:
M ctag COMLD
__ 23. Retrieve the status of the redundant port module by entering the
following command:
RTRV-EQPT::RPM1-eeeeeee-xxxx:ctag;
RTRV-EQPT::RPM1D-eeeeeee-xxxx:ctag;
RTRV-EQPT::RPM3-xxxx:ctag;
RTRV-EQPT::RPME-xxxx:ctag;
RTRV-EQPT::REPMX24-xxxx:ctag;
System response:
M ctag COMPLD

"RPM3-0193:TYPE=331A:HWV=82.5517A RI,SN=MI0372133,DT=980523,ALMPF=99,PRTN=ALW,
PRTN_PORT=NONE,PRTN_TYPE=NULL:PST=IS-NR-STBY"

24, page 29-704

normal, active (IS-NR-ACT), another port module has
failed and switched to protection. Go to step 1,
page 29-676.
76.5500/29, Rev R 7/07 Page 29-703



M ctag COMPLD

M ctag COMPLD


message.
__ 24.1.2 If no, go to step 25.


End of Procedure
Page 29-704 7/07 76.5500/29, Rev R

Optical Port Modules (OPM3, OPM3X8, OPM12, OPM12X4, OPM48)

6.36 In this section, you will troubleshoot the alarmed optical port modules
(OPM3, OPM3X8, OPM12, OPM12X4, OPM48).
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
command:
System response:
M ctag COMPLD


76.5500/29, Rev R 7/07 Page 29-705

__ 3. Depending on if the faulted OPM is located in the Working slot or the

Protect slot on the shelf, choose one of the following:
__ 3.1 If the OPM is located in the Working slot, go to Working
OPM3, OPM3X8, OPM12, OPM12X4, or OPM48,
page 29-706.
__ 3.2 If the OPM is located in the Protect slot, go to Protect

page 29-739.
Working OPM3, OPM3X8, OPM12, OPM12X4, or OPM48


M ctag COMPLD

M ctag COMPLD

"OC3-W-0001,OC3:CR,LOS,SA,01-01,00-00-00,NEND:\" Loss of Signal \":,ISLTD"
"OC3-P-0225,OC3:MN,APSB,NSA,12-31,23-59-59,NEND:\" Automatic Protection Switching

Byte Failure \":,ISLTD"

faulted port module, follow your company's prescribed

__ 2. Retrieve the status of the redundant mapping module (RMM) by

RTRV-EQPT::RMM-xxxx:ctag;
RTRV-EQPT::RMM24-xxxx:ctag;
Where: xxxx = First SDF on the port equipment shelf.
System response:
M ctag COMPLD

"RMM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5070516,DT=960516,ALMPF=99:PST=IS-NR-STBY"
Page 29-706 7/07 76.5500/29, Rev R


in-service, normal, active (IS-NR-ACT), go to
Redundant Mapping Modules (RMM), page 29-807.

in-service, normal, standby (IS-NR-STBY), go to step 3.
__ 3. Retrieve the status of the protect OPM associated with the faulted port
module by entering the following command:
RTRV-EQPT::OPMeeee-P-xxxx:ctag;
Where: eeee = Module type (3, 3X8, 12, 12X4, or 48).

xxxx = SDF number of the faulted module.
System response:
M ctag COMPLD

"OPM3-P-0193:TYPE=SHORT:HWV=81.5542A RA,SN=JL2679341,DT=950803,ALMPF=99,CONN=FC,
FREQ=1310:PST=IS-NR"
__ 3.1 If the present state of the protect OPM is out-of-service,

normal (OOS-NR), go to step 4.
__ 3.2 If the present state of the protect OPM is in-service,

normal (IS-NR), go to step 5.
__ 3.3 If the present state of the protect OPM is anything other

than the two responses listed above, go to Protect
page 29-739.
__ 4. Edit the protect OPM associated with the faulted port module
in-service (IS) by entering the following command:
ED-EQPT::OPMeeee-P-xxxx:ctag::::IS;

System response:
M ctag COMPLD

__ 5.1 If you are troubleshooting an OPM48, go to step 6,
page 29-708
__ 5.2 If you are troubleshooting an OPM12 module or an

OPM12X4, go to step 10, page 29-710.
__ 5.3 If you are troubleshooting an OPM3 module or an

76.5500/29, Rev R 7/07 Page 29-707

__ 6. Retrieve the present state of the FPGs associated with the faulted
OPM48 by entering the following command:
RTRV-FPG-OC48::FPG48-xxxx:ctag;
Where: xxxx = The first SDF serving the HDPS if editing the
OPM48 in slot 2, or the first SDF serving the
HDPS plus 48 if editing the OPM48 in slot 15.
System response:
M ctag COMPLD

If OC protection is configured ON:
"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=SFONPROT,K
1=11000000,K2=00000100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=ON,PARTNAME=UASPART
:PST=AS"
"OC48-W-0645::PMAID=OPM48-W-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN
,SSMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"
"OC48-P-0645::PMAID=OPM48-P-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=SF,SSM=UNKNOWN,S
SMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-STBY"
If OC protection is configured OFF:

"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=NOREQ,K1=1
1000000,K2=00000100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=OFF,PARTNAME=UASPART
:PST=AS"
"OC48-W-0645::PMAID=OPM48-W-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=SF,SSM=UNKNOWN,S
__ 6.1 If the system response for the protect OC is in-service,

normal, standby (IS-ANR-STBY), go to step 7,
page 29-708.

normal, active (IS-NR-ACT), go to substep 14.2,
page 29-712.
__ 6.3 If OC protection (OCPROT) is configured OFF, go to

__ 7. Switch the OC to protect by entering the following command:

OPR-PROTNSW-OC48::OC48-W-xxxx:ctag::MAN;
Where: xxxx = SDF number of the OC48.
System response:
M ctag COMPLD

"FPG48-0645:MANTOPROT,TC,,,NEND:\"Manual switch to PROT OCn occurred, Count=1\""
Page 29-708 7/07 76.5500/29, Rev R

OPM by entering the following command:
System response:
M ctag COMPLD

"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=MANTO
PROT,K1=11000000,K2=00000100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=ON,PARTNAME=UASPART
:PST=AS"

:PST=AS"
SMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"
__ 8.1 If the system response shows PROT=MANTOPROT,

__ 8.2 If the system response shows anything other than

PROT=MANTOPROT, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070
__ 9. Release the protection switch by entering the following command:

RLS-PROTNSW-OC48::OC48-W-xxxx:ctag;
System response:
M ctag COMPLD
__ 9.1 Go to step 38, page 29-723.
76.5500/29, Rev R 7/07 Page 29-709

RTRV-FPG-OC12::FPG12-xxxx&&-yyyy:ctag;
Where: xxxx = First SDF number for the HDPS.

yyyy = First SDF plus 83, or the last SDF being retrieved.

"FPG12-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=SFONWKG,
K1=11000001,K2=00010100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=ON,PARTNAME=UASPART:PST=AS"
"OC12-W-1732::PMAID=OPM12X4-W-1732,ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=NA,SSMEVE
NT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"
"OC12-P-1732::PMAID=OPM12X4-P-1732,ALM=ALW,CMDLPBKREQ=NONE,STATUS=SF,SSM=UNKNOWN,SSM
EVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-STBY"

"FPG12-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300, PROT=NOREQ,
K1=11000001,K2=00010100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=OFF,PARTNAME=UASPART:PST=AS"
"OC12-W-1732::PMAID=OPM12X4-W-1732,ALM=ALW,CMDLPBKREQ=NONE,STATUS=SF,SSM=NA,
SSMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"

normal, standby (IS-ANR-STBY), go to step 11,
page 29-710.

page 29-712.

System response:
M ctag COMPLD

Page 29-710 7/07 76.5500/29, Rev R

System response:
M ctag COMPLD

"FPG12-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=MANTOPROT,
NT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"
EVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"

__ 12.1 If the system response shows PROT=MANTOPROT,


PROT=MANTOPROT, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070

System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-711


System response:
M ctag COMPLD

"FPG12-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=MANTOPROT,
EVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"


normal, standby (IS-NR-STBY), repeat steps 11
through 14 for each OC where the protect OC is
in-service, normal, standby (IS-NR-STBY).
__ 14.2 If the system response for the OC is in-service, normal,

active (IS-NR-ACT), choose one of the following
options:
__ 14.2.1 If the type equals UPSR (TYPE=UPSR),

__ 14.2.2 If the type equals APS (TYPE=APS), go

Page 29-712 7/07 76.5500/29, Rev R

Where: xxxx = SDF number.
System response:
M ctag COMPLD

"FPG3-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=SFONWKG,K1=1100
0001,K2=00010100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=ON,PARTNAME=UASPART:PST=AS"
"OC3-W-1732::PMAID=OPM3-W-1732,ALM=ALW,CMDLPBKREQ=NONE,STATUS=SF,SSM=NA,SSMEVENT=OFF
,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"
"OC3-P-1732::PMAID=OPM3-P-1732,ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN,SSMEV
ENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"

"FPG3-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=NOREQ,K1=110000
01,K2=00010100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=OFF,PARTNAME=UASPART:PST=AS"

page 29-715.

normal, standby (IS-NR-STBY), go to step 16.

System response:
M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-713


System response:
M ctag COMPLD

"FPG3-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=MANTOPROT,K1=11
,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"
ENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"

__ 17.1 If the system response shows MANTOPROT, continue

to the next step.

MANTOPROT, follow your company's prescribed

System response:
M ctag COMPLD
Page 29-714 7/07 76.5500/29, Rev R


System response:
M ctag COMPLD

"FPG3-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=MANTOPROT,K1=11


normal, standby (IS-NR-STBY), repeat step 15,
page 29-713, through step 19, page 29-715, for each
OC where the protect OC is in-service, normal, standby
(IS-NR-STBY).

normal, active (IS-NR-ACT), choose one of the
following options:


76.5500/29, Rev R 7/07 Page 29-715

__ 20. Retrieve the state of the CPG for the faulted module by entering the
following command:
RTRV-CPG::CPG-xxxx:ctag;
System response:
M ctag COMPLD

"CPG-0465::NODETYPE=PASSTHRU,GOS=99,ALMPF=99,PREFRD=WORKING,RVRTV=NO,WTR=300,
PROT=NA,STS3CMAP=INTACT:PST=AS"
"STS3C-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=UEQ,STATUS=GOOD:PST=IS-NR-STBY"
"STS3C-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=UEQ,STATUS=GOOD:PST=IS-NR-ACT"
__ 20.1 Does the following system response appear for the

CPG?
"CPG-0913::PARTNAME=UASPART:PST=UAS"
__ 20.1.1 If no, go to step 21.
__ 21. Depending on the state of the STS3C terminations retrieved in

step 20, perform one of the following:
__ 21.1 If the present state of one STS3C is in-service, normal,
active (IS-NR-ACT) and the other STS3C is in-service,
__ 21.2 If the present state of both STS3Cs is in-service,

page 29-718.
__ 21.3 If the present state is anything other than what is listed

above, perform one of the following:
__ 21.3.1 If the STS3C in question is the working

STS3C, go to STS3C-Working
Termination (STS3C-W), page 29-991.
__ 21.3.2 If the STS3C in question is the protect

STS3C, go to STS3C-Protect
Termination (STS3C-P), page 29-997
__ 22. Does the system response from step 20 verify that the working STS3C
is in-service, normal, standby (IS-NR-STBY)?
__ 23. Repeat steps 20 through 22 for the remaining CPG terminations

assigned to the faulted module.
Page 29-716 7/07 76.5500/29, Rev R

Caution:
This action may cause port module traffic interruption. Follow internal policy for
redundancy switching.
Note: After entering the following command, the active LED on the working OPM
turns off while the active LED on the protect OPM lights.
__ 24. Perform a protection switch on the faulted module, forcing it to

standby, by entering the following command:
OPR-PROTNSW-STS3C::STS3C-W-xxxx:ctag::MAN;

M ctag COMPLD

M ctag COMPLD
following command:
System response:
M ctag COMPLD

"STS3C-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=UEQ,STATUS=SF:PST=IS-NR-STBY"
"STS3C-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=UEQ,STATUS=SF:PST=IS-NR-ACT"
__ 25.1 If the system response for the working STS3C is now

in-service, normal, standby (IS-NR-STBY) go to step
23, page 29-716.
76.5500/29, Rev R 7/07 Page 29-717

__ 25.2 If the system response for the working STS3C is not

in-service, normal, standby (IS-NR-STBY) perform one
of the following:


Termination (STS3C-P), page 29-997.
__ 26. Retrieve the state of the VPG for the faulted module by entering the
following command:
RTRV-VPG::VPG-xxxx-1&&-28:ctag;
System response:
M ctag COMPLD

"VPG-0001-1-1::NODETYPE=PASSTHRU,GOS=99,ALMPF=99,PREFRD=WORKING,RVRTV=NO,
WTR=300,PROT=NA,VTMAP=INTACT,FLTPR=DISABLED, FLTRC=NONE,PARTNAME=UASPART:PST=AS"
"VT1-W-0001-1-1::PMAID=OPM12-W-0001,ALM=ALW,PSL=NA,PSLT=NA,STATUS=SF,PASUSP=DLY,PATM
=00-03-30,PATM_REMAIN=00-00-10,PARTNAME=UASPART:PST=IS-NR-STBY"
"VT1-P-0001-1-1::PMAID=OPM12-P-0001,ALM=ALW,PSL=NA,PSLT=NA,STATUS=SF,PASUSP=DLY,PATM
=00-03-30,PATM_REMAIN=00-00-10,PARTNAME=UASPART:PST=IS-NR-ACT"

VPG?
"VPG-0913-1-1::PARTNAME=UASPART:PST=UAS"
__ 26.1.2 If no, go to the next step.
__ 27. Depending on the state of the VT1 terminations retrieved in step 26,
page 29-718, perform one of the following:
__ 27.1 If the present state of one VT1 is in-service, normal,
active (IS-NR-ACT) and the other VT1 is in-service,
__ 27.2 If the present state of both VT1s are in-service, normal,


__ 27.3.1 If the VT1 in question is the working VT1,

go to VT1-Working Termination (VT1-W),
page 29-984.
Page 29-718 7/07 76.5500/29, Rev R

__ 27.3.2 If the VT1 in question is the protect VT1,

go to VT1-Protect Termination (VT1-P),
page 29-988.
__ 28. Does the system response from step 26, page 29-718, verify that the
working VT1 is in-service, normal, standby (IS-NR-STBY)?
__ 29. Repeat steps 26 through 28 for the remaining VPG terminations

Caution:
__ 30. Perform a protection switch on the faulted module forcing it to standby

OPR-PROTNSW-VT1::VT1-W-xxxx:ctag::MAN;

M ctag COMPLD

M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-719

following command:
RTRV-VPG::VPG-xxxx:ctag;
System response:
M ctag COMPLD

WTR=300,PROT=NA,VTMAP=INTACT,FLTPR=DISABLED,FLTRC=NONE,PARTNAME=UASPART:PST=AS"
=00-03-30,PATM_REMAIN=00-00-10,PARTNAME=UASPART:PST=OOS-NR"
__ 31.1 If the system response for the working VT1 is now

in-service, normal, standby (IS-NR-STBY), return to
step 29, page 29-719.
__ 31.2 If the system response for the working VT1 is not

of the following:

page 29-984.

page 29-988.
__ 32. Retrieve the state of the PPG for the faulted module by entering the
following command:
RTRV-PPG::PPG-xxxx&&-yyyy:ctag;

yyyy = Last SDF number assigned to the faulted module.
System response:
M ctag COMPLD

"PPG-0465::NODETYPE=NA,GOS=99,ALMPF=99,PREFRD=NA,RVRTV=NA,WTR=NA,PROT=NA,
STSMAP=VTFLOAT,FLTPR=DISABLED:PST=AS"
"STS1-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=NA,PSLT=UEQ,STATUS=GOOD:PST=IS-NR-ACT"
"STS1-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=NA,PSLT=UEQ,STATUS=GOOD:PST=IS-NR-ACT"
Page 29-720 7/07 76.5500/29, Rev R


PPG?
"PPG-0913::PARTNAME=UASPART:PST=UAS"
__ 32.1.1 If yes, go to step step 38, page 29-723.
__ 32.1.2 If no, go to the next step.
__ 33. Depending on the state of the STS1 terminations retrieved in step 32,
__ 33.1 If the present state of one STS1 is in-service, normal,
active (IS-NR-ACT), and the other STS1 is in-service,
__ 33.2 If the present state of both STS1s is in-service, normal,


__ 33.3.1 If the STS1 in question is the working

STS1, go to STS1-Working Termination
(STS1-W), page 29-974.
__ 33.3.2 If the STS1 in question is the protect

STS1, go to STS1-Protect Termination
(STS1-P), page 29-979.
working STS1 is in-service, normal, standby (IS-NR-STBY)?
__ 35. Repeat steps 32 through 34 for the remaining PPG terminations

Caution:
76.5500/29, Rev R 7/07 Page 29-721


OPR-PROTNSW-STS1::STS1-W-xxxx:ctag::MAN;
System response:
M ctag COMPLD
following command:
RTRV-PPG::PPG-xxxx:ctag;
System response:
M ctag COMPLD

"STS1-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=NA,PSLT=UEQ,STATUS=GOOD:
PST=IS-NR-STBY"
"STS1-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=NA,PSLT=UEQ,STATUS=GOOD:
PST=IS-NR-ACT"
__ 37.1 If the system response for the working STS1 is now

35, page 29-721.
__ 37.2 If the system response for the working STS1 is not

in-service, normal, standby (IS-NR-STBY), perform one
of the following:

(STS1-W), page 29-974.

(STS1-P), page 29-979.
Page 29-722 7/07 76.5500/29, Rev R

__ 38. Retrieve the status of the faulted OPM by entering the following
command:
RTRV-EQPT::OPMeeee-W-xxxx:ctag;

System response:
M ctag COMPLD

"OPM3-W-0193:TYPE=SHORT:HWV=81.5542A RA,SN=JL2679341,DT=950803,ALMPF=99,CONN=FC,

in-service, abnormal, equipped (IS-ANR-EQ), go to
step 39.

step 39.

out-of-service, abnormal, unequipped,


page 29-727.


__ 39. Edit the faulted OPM out-of-service (OOS) by entering the following
command:
ED-EQPT::OPMeeee-W-xxxx:ctag::::OOS;

System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-723

command:

System response:
M ctag COMPLD

FREQ=1310:PST=OOS-ANR-EQ"
__ 40.1 If the system response for the faulted OPM is

__ 40.2 If the system response for the working OPM is




page 29-725.

place.
DANGER:
__ 42.2 Label and remove the fiber optic cables attached to the
module. Place dust covers on all fiber optic cables
previously removed.
Page 29-724 7/07 76.5500/29, Rev R


steps:
backplane.


backplane?


__ 43.3.3 If the removed port module is to be

reinserted, go to step 46, page 29-726.
__ 43.3.4 If the removed port module is not to be

used, go to step 44.

troubleshooting.
__ 45.1 If the module type is not the same type as the module
removed in step 42, page 29-724, or if the slot is not
provisioned for the proper module type, refer to Tellabs
5500/5500S Provisioning Manual, 76.5500/23.
__ 45.2 If the module type is the same type as the module

removed in step 42, page 29-724, go to step 46,
page 29-726.
Note: Use of proper port modules as RPMs applies only to port modules with
alternate types: the DS1, DS3, STS-1E, and mapping modules. Double
Density DS1, OC-3, OC-12, and OC-48 Port Modules currently have no
alternate types, so they may back each other up only.
76.5500/29, Rev R 7/07 Page 29-725



loose or missing?

module is damaged and you will need to replace it. Go

step 47.
__ 47. If the fiber cables on the module contain optical connector dust covers,
remove the dust covers from the fiber cables.
__ 48. If necessary, insert the facility fiber cables into the front of the module.
__ 51. Retrieve the status of the working OPM by entering the following
command:

System response:
M ctag COMPLD

FREQ=1310:PST=OOS-NR"
__ 51.1 If the present state of the working OPM is

page 29-727.
__ 51.2 If the present state of the working OPM is not

page 29-727.
Page 29-726 7/07 76.5500/29, Rev R

__ 52. Edit the working OPM in-service (IS) by entering the following
command:
ED-EQPT::OPMeeee-W-xxxx:ctag::::IS;

System response:
M ctag COMPLD
__ 53. Retrieve the status of the working OPM by entering the following
command:

System response:
M ctag COMPLD

__ 53.1 If the present state of the working OPM is in-service,

__ 53.2 If the present state of the working OPM is not

__ 54. Diagnose the problem on the working port module by entering the
following command:
DGN-EQPT::OPMeeee-W-xxxx:ctag::,ITER=3;

System response:
M ctag COMPLD

"OPM12-W-5:PASS-3"
"OPM12-W-5:FAIL-0"
76.5500/29, Rev R 7/07 Page 29-727


step 55.


__ 56. Diagnose the problem on the working port module by entering the
following command:
DGN-EQPT::OPMeeee-W-xxxx:ctag;

System response:
M ctag COMPLD

"OPM12-W-5:PASS-1"
"OPM12-W-5:FAIL-0"



__ 57.1 If you are troubleshooting an OPM48, go to step 58,
page 29-729.
__ 57.2 If you are troubleshooting an OPM12 or OPM12X4, go

__ 57.3 If you are troubleshooting an OPM3 or OPM3X8, go to

step 68, page 29-735.
Page 29-728 7/07 76.5500/29, Rev R

System response:
M ctag COMPLD

000,K2=00000100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=ON,PARTNAME=UASPART
:PST=AS"
"OC48-W-0645::PMAID=OPM48-W-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN,SSM
"OC48-P-0645::PMAID=OPM48-P-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN,SSM

__ 58.1 If the system response shows the working OC is

PROT=DNR, go to step 59, page 29-730.

in-service, normal, active (IS-NR-ACT) and the
PROT=MANTOWKG, go to step 61, page 29-731

PROT=WTR, wait for the following message to appear.
Then go to step 62, page 29-731.
"FPG48-0645:RTW,TC,,,NEND:\"Revert to working OCn switch occurred, Count=1\""

PROT=NOREQ, go to step 73, page 29-738.

PROT=SFONWKG, go to Optical Carrier 48-Working
Termination (OC48-W), page 29-949.
76.5500/29, Rev R 7/07 Page 29-729

__ 59. Switch the service from protect to working by entering the following
command:
OPR-PROTNSW-OC48::OC48-P-xxxx:ctag::MAN;
System response:
M ctag COMPLD

"FPG48-0645:MANTOWKG,TC,,,NEND:\"Manual switch to WKG OCn occurred, Count=1\""
System response:
M ctag COMPLD

"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=MANTOWKG,K1=11
"OC48-P-0645::PMAID=OPM48-P-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN,SSM

__ 60.1 If the system response shows that

PROT=MANTOWKG, continue to the step 61,
page 29-731.

PROT=MANTOWKG, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070
Page 29-730 7/07 76.5500/29, Rev R


System response:
M ctag COMPLD
System response:
M ctag COMPLD

:PST=AS"
"OC48-P-0645::PMAID=OPM48-P-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN
,SSMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"

:PST=AS"
76.5500/29, Rev R 7/07 Page 29-731

__ 62.1 If the system response for the working OC is in-service,

normal, active (IS-NR-ACT) and PROT=NOREQ, go to
step 73, page 29-738.
__ 62.2 If the system response for the working OC is not


System response:
M ctag COMPLD

"FPG12-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=MANTOWKG,



PROT=MANTOWKG, go to step 66, page 29-734

Page 29-732 7/07 76.5500/29, Rev R



PROT=SFONWKG, go to Optical Carrier 12-Working
command:
System response:
M ctag COMPLD

Where: xxxx = First SDF number for the port shelf.

yyyy = First SDF plus 83, or the last SDF being retrieved
(OPM12X4 only).
System response:
M ctag COMPLD


76.5500/29, Rev R 7/07 Page 29-733

__ 65.1 If the system response shows that

PROT=MANTOWKG, continue to the step 66,
page 29-734.

1.800.443.5555 (North America) or 1.630.798.7070

RLS-PROTNSW-OC12::OC12-P-xxxx:ctag;
Where: xxxx = First SDF for the port module.
System response:
M ctag COMPLD

(OPM12X4 only).
System response:
M ctag COMPLD


"FPG12-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=NOREQ,

Page 29-734 7/07 76.5500/29, Rev R


step 73, page 29-738.


(OPM3X8 only).
System response:
M ctag COMPLD




PROT=MANTOWKG, go to step 71, page 29-737.

76.5500/29, Rev R 7/07 Page 29-735



normal, standby (IS-NR-STBY) and the PROT =
SFONWKG, go to Optical Carrier 3-Protect Termination
(OC3-P), page 29-936.
command:
System response:
M ctag COMPLD


(OPM3X8 only).
System response:
M ctag COMPLD

"FPG3-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=MANTOWKG,K1=110

Page 29-736 7/07 76.5500/29, Rev R

__ 70.1 If the system response show the PROT=MANTOWKG,


1.800.443.5555 (North America) or 1.630.798.7070

System response:
M ctag COMPLD

(OPM3X8 only).
System response:
M ctag COMPLD


76.5500/29, Rev R 7/07 Page 29-737


step 73.

in-service, normal, active (IS-NR-ACT) and PROT does
not equal NOREQ, follow your company's prescribed


M ctag COMPLD

M ctag COMPLD


message.


End of Procedure
Page 29-738 7/07 76.5500/29, Rev R

Protect OPM3, OPM3X8, OPM12, OPM12X4, or OPM48


M ctag COMPLD

M ctag COMPLD

"OC3-W-0001,OC3:CR,LOS,SA,01-01,00-00-00,NEND:\" Loss of Signal \":,ISLTD"
"OC3-P-0225,OC3:MN,APSB,NSA,12-31,23-59-59,NEND:\" Automatic Protection Switching

Byte Failure \":,ISLTD"

faulted port module, follow your company's prescribed


System response:
M ctag COMPLD

"RMM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5070516,DT=960516,ALMPF=99:
PST=IS-NR-STBY"

in-service, normal, active (IS-NR-ACT), go to
Redundant Mapping Modules (RMM), page 29-807.

page 29-740.
76.5500/29, Rev R 7/07 Page 29-739

__ 3. Retrieve the status of the working OPM associated with the faulted
port module by entering the following command:

System response:
M ctag COMPLD

__ 3.1 If the present state of the working OPM is

__ 3.2 If the present state of the working OPM is in-service,

__ 3.3 If the present state of the working OPM is anything other

than the two responses listed above, go to step 1,
page 29-705.
__ 4. Edit the working OPM associated with the faulted port module

System response:
M ctag COMPLD

__ 5.1 If you are troubleshooting an OPM48, go to step 6.
__ 5.2 If you are troubleshooting an OPM12 module or

__ 5.3 If you are troubleshooting an OPM3 module or

Page 29-740 7/07 76.5500/29, Rev R

System response:
M ctag COMPLD

:PST=AS"
"OC48-W-0645::PMAID=OPM3X8-W-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=SF,SSM=UNKNOWN,
"OC48-P-0645::PMAID=OPM3X8-P-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=SF,SSM=UNKNOWN,
SSMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-STBY"

page 29-743.

normal, standby (IS-NR-STBY), go to the next step.

command:
System response:
M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-741

System response:
M ctag COMPLD

"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=MANTOWKG,K
:PST=AS"
SSMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"
__ 8.1 If the system response shows that the

PROT=MANTOWKG, go to the next step.

1.800.443.5555 (North America) or 1.630.798.7070

System response:
M ctag COMPLD
Page 29-742 7/07 76.5500/29, Rev R

System response:
M ctag COMPLD

:PST=AS"
__ 10.1 Go to step 40, page 29-755.
__ 11. For each OC where the system response for the working OC is
in-service, normal, standby (IS-NR-STBY), repeat steps 7,
page 29-741, through 10.

(OPM12X4 only).
System response:
M ctag COMPLD


page 29-745.

76.5500/29, Rev R 7/07 Page 29-743

command:
System response:
M ctag COMPLD


(OPM12X4 only).
System response:
M ctag COMPLD

__ 14.1 If the system response shows that the

PROT=MANTOWKG, go to the next step.

1.800.443.5555 (North America) or 1.630.798.7070

System response:
M ctag COMPLD
Page 29-744 7/07 76.5500/29, Rev R


(OPM12X4 only).
System response:
M ctag COMPLD

__ 16.1 For each OC where the system response for the

working OC is in-service, normal, standby
(IS-NR-STBY), repeat steps 13, page 29-744,
through 16.

following:
__ 16.2.1 If the type equals UPSR (TYPE=UPSR)

__ 16.2.2 If the type equals APS (TYPE=APS) go


(OPM3X8 only).
System response:
M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-745


page 29-747.

command:
System response:
M ctag COMPLD


(OPM3X8 only).
System response:
M ctag COMPLD

"FPG3-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=MANTOWKG,K1=110
__ 19.1 If the system response shows PROT=MANTOWKG, go

to the next step.

1.800.443.5555 (North America) or 1.630.798.7070
Page 29-746 7/07 76.5500/29, Rev R


System response:
M ctag COMPLD

(OPM3X8 only).
System response:
M ctag COMPLD


normal, standby (IS-NR-STBY), repeat steps 17
through 21 for each OC where the working OC is
in-service, normal, standby (IS-NR-STBY).

following:


76.5500/29, Rev R 7/07 Page 29-747

following command:
System response:
M ctag COMPLD

"STS3C-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=UEQ,STATUS=SF:PST=IS-NR-STBY"
"STS3C-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=UEQ,STATUS=SF:PST=IS-NR-ACT"

CPG?
"CPG-0913::PARTNAME=UASPART:PST=UAS"
__ 22.1.1 If no, go to step 23.
__ 23. Depending on the state of the STS3C terminations retrieved in step 22

perform one of the following:?
__ 23.1 If the present state of one STS3C is in-service, normal,
active (IS-NR-ACT) and the other STS3C is in-service,
__ 23.2 If the present state of both STS3Cs is in-service,

page 29-750.



__ 24. Does the system response from step 22 verify that the protect STS3C
is in-service, normal, standby (IS-NR-STBY)?
Page 29-748 7/07 76.5500/29, Rev R

__ 25. Repeat steps 22 through 24 for the remaining CPG terminations

Caution:
Note: After entering the following command, the active LED on the protect OPM
turns off while the active LED on the working OPM lights.

OPR-PROTNSW-STS3C::STS3C-W-xxxx:ctag::MAN;
System response:
M ctag COMPLD
following command:
System response:
M ctag COMPLD

"STS3C-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=UEQ,STATUS=SF:PST=IS-NR-ACT"
"STS3C-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=UEQ,STATUS=SF:PST=IS-NR-STBY"
76.5500/29, Rev R 7/07 Page 29-749

__ 27.1 If the system response for the protect STS3C is now

25, page 29-749.
__ 27.2 If the system response for the working STS3C is not

of the following:


following command:
RTRV-VPG::VPG-xxxx-1&&-28:ctag;
System response:
M ctag COMPLD

=00-03-30,PATM_REMAIN=00-00-10,PARTNAME=UASPART:PST=IS-NR-ACT"

VPG?
"VPG-0913-1-1::PARTNAME=UASPART:PST=UAS"
__ 28.1.2 If no, go to step 29.
__ 29. Depending on the state of the VT1 terminations retrieved in step 28,
perform one of the following:
__ 29.1 If the present state of one VT1 is in-service, normal,
active (IS-NR-ACT) and the other VT1 is in-service,
page 29-748.
__ 29.2 If the present state of both VT1s is in-service, normal,

Page 29-750 7/07 76.5500/29, Rev R

__ 29.3 If the preset state is anything other than what is listed


page 29-984.

page 29-988.
__ 30. Does the system response from step 28 verify that the working VT1 is
in-service, normal, standby (IS-NR-STBY)?
__ 31. Repeat step 26, page 29-749, through 30 for the remaining VPG
terminations assigned to the faulted module.
Caution:

OPR-PROTNSW-VT1::VT1-W-xxxx:ctag::MAN;
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-751

following command:
RTRV-VPG::VPG-xxxx:ctag;
System response:
M ctag COMPLD

WTR=300,PROT=NA,VTMAP=INTACT,FLTPR=DISABLED,FLTRC=NONEE,PARTNAME=UASPART:PST=AS"
__ 33.1 If the system response for the protect VT1 is now

in-service, normal, standby (IS-NR-STBY) go to step
31, page 29-751.
__ 33.2 If the system response for the protect VT1 is not

of the following:

page 29-984.

page 29-988.
following command:
RTRV-PPG::PPG-xxxx&&yyyy:ctag;

yyyy = Last SDF number assigned to the faulted module.
System response:
M ctag COMPLD

"STS1-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=NA,PSLT=UEQ,STATUS=GOOD:PST=IS-NR-ACT"
"STS1-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=NA,PSLT=UEQ,STATUS=GOOD:PST=IS-NR-ACT"
Page 29-752 7/07 76.5500/29, Rev R


PPG?
"PPG-0913::PARTNAME=UASPART:PST=UAS"
__ 34.1.1 If yes, go to step step 40, page 29-755.
__ 34.1.2 If no, go to step 35.
__ 35. Depending on the state of the STS1 terminations retrieved in step 34,
__ 35.1 If the present state of one STS1 is in-service, normal,
active (IS-NR-ACT), and the other STS1 is in-service,
__ 35.2 If the present state of both STS1s is in-service, normal,



(STS1-W), page 29-974.

(STS1-P), page 29-979.
working STS1 is in-service, normal, standby (IS-NR-STBY)?
__ 37. Repeat steps 34 through 36 for the remaining PPG terminations

76.5500/29, Rev R 7/07 Page 29-753

Caution:

OPR-PROTNSW-STS1::STS1-W-xxxx:ctag::MAN;

M ctag COMPLD

M ctag COMPLD
following command:
System response:
M ctag COMPLD

"STS1-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=NA,PSLT=UEQ,STATUS=GOOD:
PST=IS-NR-STBY"
"STS1-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=NA,PSLT=UEQ,STATUS=GOOD:
PST=IS-NR-ACT"
Page 29-754 7/07 76.5500/29, Rev R

__ 39.1 If the system response for the protect STS1 is now

37, page 29-753.
__ 39.2 If the system response for the protect STS1 is not

in-service, normal, standby (IS-NR-STBY), perform one
of the following:

(STS1-W), page 29-974.

(STS1-P), page 29-979.
command:
Where: eeee = Module type (3, 3X8, 12, or 12X4).

System response:
M ctag COMPLD


in-service, abnormal, equipped (IS-ANR-EQ), go to step
41, page 29-756.

step 41, page 29-756.

out-of-service, abnormal, unequipped,


page 29-759.
76.5500/29, Rev R 7/07 Page 29-755



__ 41. Edit the faulted OPM out-of-service (OOS) by entering the following
command:
ED-EQPT::OPMeeee-W-xxxx:ctag::::OOS:

System response:
M ctag COMPLD
command:

System response:
M ctag COMPLD

ENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=OOS-ANR-EQ"
__ 42.1 If the system response for the faulted OPM is

__ 42.2 If the system response for the working OPM is


page 29-760.
__ 43.2 If there is no module present in the slot, go to substep

45.2.4, page 29-757.

place.
Page 29-756 7/07 76.5500/29, Rev R


steps:
backplane.

backplane?


__ 45.2.3 If the removed port module is to be

reinserted, go to step 46.
__ 45.2.4 If the removed port module is not to be



loose or missing?

to step 47.

step 51, page 29-758.

troubleshooting.
76.5500/29, Rev R 7/07 Page 29-757


__ 48.1 If the module type is not the same type as the module
removed in step 44, page 29-756, or if the slot is not
provisioned for the proper module type, refer to Tellabs
__ 48.2 If the module type is the same type as the module

removed in step 44, page 29-756, go to step 49.
Density DS1, OC-3, and OC-12 Port Modules currently have no alternate
types, so they may always back each other up.
__ 49. If the fiber cables on the module contain optical connector dust covers,
remove them from the fiber cables.
DANGER:
__ 50. If necessary, insert the facility fiber cables into the front of the module.
Page 29-758 7/07 76.5500/29, Rev R

__ 53. Retrieve the status of the protect OPM by entering the following
command:

System response:
M ctag COMPLD

FREQ=1310:PST=OOS-NR"
__ 53.1 If the present state of the protect OPM is out-of-service,

__ 53.2 If the present state of the protect OPM is not

page 29-760.
__ 54. Edit the protect OPM in-service (IS) by entering the following
command:

System response:
M ctag COMPLD
__ 55. Retrieve the status of the protect OPM by entering the following
command:

System response:
M ctag COMPLD

__ 55.1 If the present state of the protect OPM is in-service,

__ 55.2 If the present state of the protect OPM is not in-service,

76.5500/29, Rev R 7/07 Page 29-759

__ 56. Diagnose the problem on the protect port module by entering the
following command:
DGN-EQPT::OPMeeee-P-xxxx:ctag::,ITER=3;

System response:
M ctag COMPLD

"OPM12-P-5:PASS-3"
"OPM12-P-5:FAIL-0"

step 57.


__ 58. Diagnose the problem on the protect port module by entering the
following command:
DGN-EQPT::OPMeeee-P-xxxx:ctag;

System response:
M ctag COMPLD

"OPM12-P-5:PASS-1"
"OPM12-P-5:FAIL-0"


Page 29-760 7/07 76.5500/29, Rev R


__ 59.1 If you are troubleshooting an OPM48, go to step 60.
__ 59.2 If you are troubleshooting an OC-12 module or

OPM12X4, go to step 65.
__ 59.3 If you are troubleshooting an OC-3 module or OPM3X8,

System response:
M ctag COMPLD

:PST=AS"

normal, active (IS-NR-ACT) and PROT=DNR, go to
step 61, page 29-762.

normal, active (IS-NR-ACT) and PROT=WTR, wait for
the following message to appear. Then go to step 64,
page 29-763.

abnormal, standby (IS-ANR-STBY), and
PROT=SFONPROT, go to Optical Carrier 48-Protect
Termination (OC48-P), page 29-954.
76.5500/29, Rev R 7/07 Page 29-761

command:
System response:
M ctag COMPLD

System response:
M ctag COMPLD

"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=MANTOWKG,K
:PST=AS"

normal, active (IS-NR-ACT) and PROT=MANTOWKG,
go to step 63.

PROT=MANTOWKG, follow your company’s
1.800.443.555 (North America) or 1.630.798.7070


System response:
M ctag COMPLD
Page 29-762 7/07 76.5500/29, Rev R

System response:
M ctag COMPLD

:PST=AS"

page 29-769.

in-service, normal, active (IS-NR-ACT), go to Working
page 29-706.
OPM12X4 by entering the following command:

System response:
M ctag COMPLD

"FPG12-0065:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=NA,PROT=DNR,
K1=00010001,K2=00010100,SWEVNT=OFF,SSMTYPEOC=ANSI:PST=AS"
"OC12-W-0065::ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=NA,SSMEVENT=OFF,SSMUSER=SYS:
PST=IS-NR-STBY"
"OC12-P-0065::ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=DNU,SSMEVENT=OFF,SSMUSER=SYS:
PST=IS-NR-ACT"
"FPG12-0077:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=NA,PROT=NOREQ,
PST=IS-NR-STBY"
PST=IS-NR-ACT"
76.5500/29, Rev R 7/07 Page 29-763

PST=IS-NR-STBY"
PST=IS-NR-ACT"
PST=IS-NR-STBY"
PST=IS-NR-ACT"

step 66, page 29-764.

page 29-766.

command:
System response:
M ctag COMPLD

Page 29-764 7/07 76.5500/29, Rev R


(OPM12X4 only).
System response:
M ctag COMPLD

"FPG12-0769:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI, RVRTV=NO,WTR=300,PROT=MANTOWKG,
K1=10000000,K2=00000100,SWEVNT=NA,SSMTYPEOC=ANSI,PARTNAME=UASPART:PST=AS"
"OC12-W-0769::ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD, SSM=UNKNOWN,SSMUSER=SYS,
PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"
"OC12-P-0769::ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD, SSM=UNKNOWN,SSMEVENT=OFF,
SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"

normal, active (IS-NR-ACT) and PROT=MANTOWKG,

PROT=MANTOWKG, follow your company’s
1.800.443.555 (North America) or 1.630.798.7070

System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-765


(OPM12X4 only).
System response:
M ctag COMPLD

"OC12-W-0769::ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD, SSM=UNKNOWN,SSMEVENT=OFF,
SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"
"OC12-P-0769::ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD, SSM=UNKNOWN,SSMEVENT=OFF,
SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"

page 29-769.

page 29-706.

(OPM3X8 only).
System response:
M ctag COMPLD

"FPG3-0113:TYPE=APS:GOS=3,ALMPF=6,PSDIRN=NA,RVRTV=YES,WTR=300,PROT=DNR,K1=00000000,
K2=00001100,SWEVNT=OFF,SSMTYPEOC=ANSI,PARTNAME=UASPART:PST=AS"
"OC3-W-0113::PMAID=OPM3-W-0017,ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=STRATUM3,
SSMEVENT=OFF,SSMUSER=SYS,PASUSP=DLY,PATM=00-00-40,PATM_REMAIN=00-00-10,PARTNAME=UASP
ART:PST=IS-NR-STBY"
"OC3-P-0113::PMAID=OPM3-P-0017,ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=STRATUM3,
SSMEVENT=OFF,SSMUSER=SYS,PASUSP=DLY,PATM=00-00-40,PATM_REMAIN=00-00-10,
PARTNAME=UASPART:PST=IS-NR-ACT"
Page 29-766 7/07 76.5500/29, Rev R


step 71, page 29-767.

page 29-768.

command:
System response:
M ctag COMPLD


(OPM3X8 only).
System response:
M ctag COMPLD

"FPG3-0769:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI, RVRTV=NO,WTR=300,PROT=MANTOWKG,
"OC3-W-0769::ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD, SSM=UNKNSSMUSER=SYS,PASUSP=OFF,
PARTNAME=UASPART:PST=IS-NR-ACT"
"OC3-P-0769::ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD,
SSM=UNKNOWN,SSMEVENT=OFF,SSMUSER=SYS,
PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"
76.5500/29, Rev R 7/07 Page 29-767

__ 72.1 If the system response shows PROT=MANTOWKG, go

to the next step.

1.800.443.5555 (North America) or 1.630.798.7070

System response:
M ctag COMPLD

(OPM3X8 only).
System response:
M ctag COMPLD

"OC3-W-0769::ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN,SSMEVENT=OFF,SSMUSER=
SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"
"OC3-P-0769::ALM=INH,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN,SSMEVENT=OFF,SSMUSER=
SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"

normal, active (IS-NR-ACT), go to step 75.

page 29-706.
Page 29-768 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD


message.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-769

CCPMA
6.38 In this section, you will troubleshoot the alarmed CCPMA.
6.39 A spare CCPMA may be required in order to perform this procedure. Refer
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
command:
System response:
M ctag COMPLD


Page 29-770 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

"CCPM-0035,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"
\"Parity errors detected from MIM\"
__ 3.1 If there are no alarm conditions posted against the port

module, follow your company's prescribed procedures

__ 4. Retrieve the status of the RCCPMA by entering the following

command:
RTRV-EQPT::RCCPM-aaaa:ctag;
Where: aaaa = The first SDF serving the CCPS.
System response:
M ctag COMPLD

"RCCPM-0097:TYPE=CCA:HWV=81.5599A,SN=CB0110990,DT=060507,ALMPF=99,PRTN=ALW,
SWVCC=CCFPx.y.z:PST=IS-NR-STBY"
__ 4.1 If the system response verifies that the RCCPMA is

page 29-772.

page 29-773.

abnormal (ANR), go to RCCPMA, page 29-784.
76.5500/29, Rev R 7/07 Page 29-771

Caution:
This step assumes the working port module is IS-NR-STBY condition and the
redundant module is IS-NR-ACT condition. If not, they must be brought to these
states before executing this command. Failure to do so may result in loss of
traffic. Refer to the Tellabs 5500/5500S Troubleshooting Manual, 76.5500/29, to
correct this condition.
__ 5. Retrieve the protection status of the CCPMAs in the shelf by entering

RTRV-EQPT::CCPM-aaaa&&-aaaa:ctag;
Where:
aaaa&&-aaaa = Range of CCPMAs, beginning with the first SDF
serving the CCPS + 12n where n = {0 - 6}.
System response:
M ctag COMPLD

"CCPM-0073:TYPE=CCA:HWV=81.5599A,SN=CB0110990,DT=060507,ALMPF=99,PRTN=ALW,
SWVCC=CCFPx.y.z,CCBLOCK1=<cc_block_aid>,CCBLOCK2=<cc_block_aid>,OPMODE=<opmode>:
PST=IS-NR-STBY"
SWVCC=CCFPx.y.z,CCBLOCK1=<cc_block_aid>,CCBLOCK2=<cc_block_aid>,OPMODE=<opmode>:
PST=IS-NR-STBY"
__ 5.1 If any CCPMAs are inhibited from protection switching

(PRTN=INH), go to substep 5.2.
If the CCPMAs are not inhibited from protection switch

(PRTN-ALW), go to step 6.
__ 5.2 Allow protection switching on the CCPMAs by entering
the following command.
ALW-SWTOPROTN-EQPT::CCPM-aaaa&&-aaaa:ctag;
Where:
serving the CCPS + 12n where n = (0 - 6).
System response:
M ctag COMPLD
Page 29-772 7/07 76.5500/29, Rev R

__ 6. From the system response retrieved in step 4, page 29-771, verify the
following:
__ 6.1 If the system response for the RCCPMA verifies that the
PRTN_PORT equals the SDF number of the faulted
CCPMA, go to step 7, page 29-773.
PRTN_PORT is not the SDF number of the faulted
CCPMA, then another CCPMA has previously failed
and has already switched to protection.
__ 6.2.1 Troubleshoot the CCPMA with the same

SDF number as the PRTN_PORT
parameter. Go to step 7, page 29-773.
Note: Troubleshoot the single port module address listed in the PRTN_PORT
parameter system response of step 4, page 29-771 throughout the entire
procedure or until directed otherwise.
__ 7. If the system response verifies that the CCPMA(s) are out-of-service,

abnormal (OOS-ANR), diagnose the problem by entering the following
command:
DGN-EQPT::CCPM-aaaa:ctag;
Where: aaaa = The lead_shelf_sdf (slot 2).

The lead_shelf_sdf plus 12 (slot 3).
Enter CCPM-aaaa&&-aaaa format to specify a
range of CCPMAs.
System response:
M ctag COMPLD

"CCPM-25:PASS-1"
"CCPM-25:FAIL-0"
__ 7.1 If the system response indicates a failure, correct the

problem before continuing with the next step. Refer to
Tellabs 5500 Command Reference Manual,
76.5500/13, for information about diagnostic codes.
76.5500/29, Rev R 7/07 Page 29-773

__ 8. Retrieve the protection status of the CCPMAs in the shelf by entering

RTRV-EQPT::CCPM-aaaa&&-aaaa:ctag;
Where:
serving the CCPS + 12n where n = {0 - 6}.
System response:
M ctag COMPLD

SWVCC=CCFPx.y.z,CCBLOCK1=<cc_block_aid>,CCBLOCK2=<cc_block_aid>,OPMODE=<opmode>]:PST
=IS-NR-STBY"
=IS-NR-STBY"
__ 8.1 If any CCPMAs are inhibited from protection switching

(PRTN=INH), go to substep 8.2.
If the CCPMAs are not inhibited from protection switch

(PRTN-ALW), go to substep 8.3.
__ 8.2 Allow protection switching on the CCPMAs by entering
the following command.
ALW-SWTOPROTN-EQPT::CCPM-aaaa&&-aaaa:ctag;
Where:
serving the CCPS + 12n where n = (0 - 6).
System response:
M ctag COMPLD
__ 8.3 Switch traffic carried by the CCPMA to the RCCPMA by

SW-TOPROT-EQPT::CCPM-aaaa:ctag;
Where: aaaa = The first SDF serving the CCPS + 12n where n =
(0 - 6).
System response:
M ctag COMPLD
Page 29-774 7/07 76.5500/29, Rev R

__ 8.4 Go to step 7, page 29-773.
If the status of the faulted CCPMA is still

IS-ANR-EQ-ACT or OOS-ANR-EQ-UAS, follow your
__ 9. Edit the faulted CCPMA out-of-service (OOS) by entering the following
command:
ED-EQPT::CCPM-aaaa:ctag::::OOS;
(0 - 6).

M ctag COMPLD

M ctag COMPLD
__ 10. Retrieve the status of the faulted CCPMA by entering the following
command:
RTRV-EQPT::CCPM-aaaa:ctag;
{0 - 6}.
System response:
M ctag COMPLD

=OOS-ANR-EQ-AS"
__ 10.1 If the present state of the faulted CCPMA is

__ 10.2 If the present state of the faulted CCPMA is


76.5500/29, Rev R 7/07 Page 29-775


page 29-776.

page 29-776.

place.

steps:
backplane.

backplane?


__ 13.2.3 If the removed module is not to be

__ 13.2.4 If the removed module is to be reinserted,

__ 14. Locate a replacement module. Ensure that the replacement CCPMA

is the same type as the faulted CCPMA being replaced.

loose or missing?
Page 29-776 7/07 76.5500/29, Rev R



step 16, page 29-777.
approximately five minutes during normal system behavior.
__ 17. Wait ten minutes for the module to download, then examine the front
panel LEDs of the module
__ 17.1 If the Power, Active, and Fault LEDs remain lit, go to
step 18.
__ 17.2 If the Active and Fault LEDs turn off, go to step 25,
page 29-780.
__ 18. Retrieve the status of the port module by entering the following
command:
(0 - 6).
System response:
M ctag COMPLD

PMPI=PASSIVE:SWVCC=CCFPx.y.z,CCBLOCK1=<cc_block_aid>,CCBLOCK2=<cc_block_aid>,OPMODE=<
opmode>]:PST=IS-NR-STBY"
__ 18.1 If the present state of the port module is in-service,

abnormal (IS-ANR), go to step 19.
__ 18.2 If the present state of the port module is out-of-service,

__ 18.3 If the present state of the CCPMA is out-of-service,

__ 18.4 If the present state of the CCPMA is in-service, normal,

76.5500/29, Rev R 7/07 Page 29-777

__ 19. Edit the port module out-of-service (OOS) by entering the following
command:
ED-EQPT::CCPM-aaaa:ctag::::OOS;
{0 - 6}.

M ctag COMPLD

M ctag COMPLD
__ 20. Diagnose the problem on the port module by entering the following
command:
DGN-EQPT::CCPM-aaaa:ctag::,ITER=3;
(0 - 6).
System response:
M ctag COMPLD

"CCPM-0009:PASS-3"
"CCPM-0009:FAIL-0"
__ 20.1 If this is the first module replaced, and the system

response shows any failed iterations, go to step 21.
__ 20.2 If this is the second module replaced, and the system

response still shows any failed iterations, follow your

__ 20.4 If the system response says “Parameter is inconsistent

with the type of module,” go to step 12, page 29-776.
Note: Allow up to 10 minutes for the module to download.
Page 29-778 7/07 76.5500/29, Rev R

__ 22. Diagnose the problem on the port module by entering the following
command:
DGN-EQPT::CCPM-aaaa:ctag::,ITER=1;
(0 - 6).
System response:
M ctag COMPLD

"CCPM-0009:PASS-1"
"CCPM-0009:FAIL-0"


__ 23. Retrieve the status of the new module by entering the following
command:
(0 - 6).
System response:
M ctag COMPLD

PMPI=PASSIVE:SWVCC=CCFPx.y.z,CCBLOCK1=<cc_block_aid>,CCBLOCK2=<cc_block_aid>,OPMODE=<
opmode>]:PST=OOS-NR"
__ 23.1 If system response for the new port module is

__ 23.2 If system response for the new port module is anything

other than out-of-service, normal (OOS-NR), follow your
76.5500/29, Rev R 7/07 Page 29-779

__ 24. Edit the new module in-service (IS) by entering the following
command:
ED-EQPT::CCPM-aaaa:ctag::::IS;
(0 - 6).
System response:
M ctag COMPLD
(0 - 6).
System response:
M ctag COMPLD

PMPI=PASSIVE:SWVCC=CCFPx.y.z,CCBLOCK1=<cc_block_aid>,CCBLOCK2=<cc_block_aid>,OPMODE=
<opmode>]:PST=IS-NR-STBY"
;

page 29-781.

page 29-783.

normal (IS-NR) and PRTN=INH, enter the following
commands:
ALW-SWTOPROTN-EQPT::RCCPM-aaaa:ctag;
(0 - 6).
System response:
M ctag COMPLD
Page 29-780 7/07 76.5500/29, Rev R

__ 26. Retrieve the status of the RCCPMA associated with the faulted port
module by entering one of the following commands:
(0 - 6).
System response:
M ctag COMPLD

PRTN_PORT=NONE,PRTN_TYPE=AUTO,SWVCC=CCFPx.y.z:PST=IS-NR-STBY"

page 29-781.

page 29-783.
Caution:
Note: After entering the following command, the active LED on the RCCPMA
turns off while the active LED on the CCPMA lights.
__ 27. Perform a protection switch on the new module by entering the

following command:
SW-TOWKG-EQPT::CCPM-aaaa:ctag;
(0 - 60).
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-781

command:
(0 - 6).
System response:
M ctag COMPLD

PMPI=PASSIVE:SWVCC=CCFPx.y.z,CCBLOCK1=<cc_block_aid>,CCBLOCK2=<cc_block_aid>,OPMODE=
<opmode>:PST=IS-NR-ACT"
;

page 29-782.
__ 28.2 If the system response for the port module is not

__ 29. Retrieve the status of the RCCPMA associated with the new port
module by entering the following command:
(0 - 6).
System response:
M ctag COMPLD

__ 29.1 If the system response for the RCCPMA is in-service,

normal, active (IS-NR-ACT) and the PRTN_PORT
equals the SDF number of the faulted port module, go
PRTN_PORT does not equal the SDF number of the
faulted port module, then another port module has
previously failed and has already switched to protection.
Return to step 1, page 29-770, to troubleshoot the
problem.

page 29-783.
Page 29-782 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

"CCPM-0035,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"
\"System Clock error from MIM\"

message.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-783

RCCPMA
6.40 In this section, you will troubleshoot the alarmed redundant CCPMA.
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
command:
System response:
M ctag COMPLD


Page 29-784 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

"RCCPM-0097,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"

redundant port module, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070
__ 3.2 If there are alarm conditions posted against the

redundant port module, go to step 4.

command:
{0 - 6}.
System response:
M ctag RTRV

;
__ 4.1 If the present state of the RCCPMA is in-service,

abnormal, equipped, standby (IS-ANR-EQ-STBY), go

page 29-786.
__ 4.3 If the present state of the RCCPMA is out-of-service,


abnormal, equipped, unassigned
(OOS-ANR-EQ-UAS), go to step 8, page 29-788.
76.5500/29, Rev R 7/07 Page 29-785




page 29-791.

page 29-791.

abnormal, equipped, active (IS-ANR-EQ-ACT), go to
step 22, page 29-792.

__ 5. Edit the RPM out-of-service (OOS) by entering the following

command:
ED-EQPT::RCCPM-aaaa:ctag::::OOS;
{0 - 6}.

M ctag COMPLD

M ctag COMPLD
Page 29-786 7/07 76.5500/29, Rev R


command:
{0 - 6}.
System response:
M ctag RTRV

PRTN_PORT=NONE,PRTN_TYPE=AUTO,SWVCC=CCFPx.y.z:PST=OOS-ANR-EQ-AS"
;



__ 7. Visually verify that there is an RCCPMA present in the slot.

__ 7.1 If there is an RCCPMA in the slot, go to step 8,
page 29-788.
__ 7.2 If there is no RCCPMA in the slot, go to step 10,

page 29-788.
Warning:
76.5500/29, Rev R 7/07 Page 29-787

__ 8. Remove the RCCPMA.

place.

steps:
backplane.

backplane?



the module removed in step 8,
page 29-788, or if the slot is not
North America).

module removed in step 8, page 29-788,


loose or missing?
Page 29-788 7/07 76.5500/29, Rev R



step 12, page 29-789.
__ 13. Wait ten minutes for the module download, then examine the front
panel LEDs of the RCCPMA?
__ 13.1 If the Power, Active, and Fault LEDs remain lit, go to
step 14, page 29-789.
__ 13.2 If the Active and Fault LEDs turn off, go to step 17,
page 29-790.

command:
DGN-EQPT::RCCPM-aaaa:ctag::,ITER=3;
(0 - 6).
System response:
M ctag COMPLD

"RPM1-0097:PASS-3"
"RPM1-0097:FAIL-0"
__ 14.1 If this is the first redundant port module replaced, and

the system response shows any failed iterations, go to
step 15.
__ 14.2 If this is the second redundant port module replaced,

and the system response still shows any failed
iterations, follow your company's prescribed procedures
76.5500/29, Rev R 7/07 Page 29-789


Note: Wait up to 10 minutes for the module to download.
__ 16. Diagnose the problem on the RCCPMA by entering the following

command:
DGN-EQPT::RCCPM-aaa:ctag::,ITER=1;
(0 - 6).
System response:
M ctag COMPLD

"RCCPM1-0009:PASS-1"
"RCCPM1-0009:FAIL-0"



command:
(0 - 6).
System response:
M ctag RTRV

PRTN_PORT=NONE,PRTN_TYPE=AUTO,SWVCC=CCFPx.y.z:PST=OOS-NR"
;
__ 17.1 If the system response for the RCCPMA is


normal (IS-NR), go to substep 19.1, page 29-791.
__ 17.3 If the system response for the RCCPMA is abnormal

(ANR), go to step 4, page 29-785.
Page 29-790 7/07 76.5500/29, Rev R

__ 18. Edit the RCCPMA in-service (IS) by entering the following command:
ED-EQPT::RCCPM-aaaa:ctag::::IS;
{0 - 6}.
System response:
M ctag COMPLD
Note: System generates termination SENA alarm CLR messages during certain
{0 - 6}.
System response:
M ctag RTRV

SWVCC=CCFPx.y.z:PST=IS-NR-STBY"
;

normal, standby (IS-NR-STBY) and the PRTN=INH, go

step 24, page 29-793.
__ 19.3 If the system response is anything other than the

system responses listed above, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070
__ 20. Release the inhibit on the RCCPMA by entering the following

command:
ALW-SWTOPROTN-EQPT::CCPM-aaaa:ctag;
{0 - 6}.
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-791


command:
(0 - 6).
System response:
M ctag RTRV

"RCCPM-0097:TYPE=CCA:HWV=81.5599A,SN=CB0110990,DT=060507,ALMPF=99,PRTN=ALW,SWVCC=CCP
MFPx.y:PST=IS-NR-STBY"

normal, active (IS-NR-ACT) and PRTN=ALW, go to
step 22, page 29-703.

step 24, page 29-704.
__ 21.3 If the system response for the PRTN is anything other

than ALW, follow your company's prescribed
__ 21.4 If the system response for the present state is anything

other than in-service, normal, standby (IS-NR-STBY) or
page 29-695.
__ 22. Perform a protection switch by entering the following commands

depending on the module type:
SW-TOWKG-EQPT::CCPM-aaaa:ctag;
{0 - 6}.
System response:
M ctag COMLD
Page 29-792 7/07 76.5500/29, Rev R

__ 23. Retrieve the status of the redundant port module by entering the
following command:
{0 - 6}.
System response:
M ctag RTRV

;

24, page 29-793

normal, active (IS-NR-ACT), another port module has
failed and switched to protection. Go to step 1,
page 29-784.


M ctag COMPLD

M ctag COMPLD

"RCCPM-0097,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"
\"System Clock error from MIM\"

message.
__ 24.1.2 If no, go to step 25.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-793

Mapping Modules (MM)

6.42 In this section, you will troubleshoot the alarmed Mapping Module (MM).
6.43 A spare MM may be required in order to perform this procedure. Refer to
following command:

pid = Password.
System response:
M ctag COMPLD

prosecution. */
command:
System response:
M ctag COMPLD


Page 29-794 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

"MM-0035,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"

faulted mapping module (MM), follow your company's
1.800.443.5555 (North America) or 1.630.798.7070

MM, go to step 4.

System response:
M ctag COMPLD

PRTN MM=MM-0193,PRTN TYPE=AUTO:PST=IS-NR-ACT"
__ 4.1 If the present state of the RMM is in-service, normal,



listed above, go to Redundant Mapping Modules
(RMM), page 29-807.
76.5500/29, Rev R 7/07 Page 29-795

__ 5. Perform a protection switch on the faulted MM by entering one of the

following commands:
SW-TOPROTN-EQPT::MM-xxxx:ctag;
SW-TOPROTN-EQPT::MM24-xxxx:ctag;
Where: xxxx = SDF number of the faulted MM.
System response:
M ctag COMPLD
__ 6. Retrieve the status of the RMM by entering one of the following

commands:
System response:
M ctag COMPLD

__ 7. From the system response retrieved in step 4, page 29-795, or step 6,

verify the following:
__ 7.1 If the system response for the RMM verifies that the
protection MM equals the SDF number of the faulted
MM, go to step 8, page 29-797.
__ 7.2 If the system response for the RMM verifies that the
protection MM does not equal the SDF number of the
faulted MM, go to step 1, page 29-794, to troubleshoot
the MM that has switched to protection.
Page 29-796 7/07 76.5500/29, Rev R

__ 8. Retrieve the status of the faulted MM by entering one of the following

commands:
RTRV-EQPT::MM-xxxx:ctag;
RTRV-EQPT::MM24-xxxx:ctag;
System response:
M ctag COMPLD

"MM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5016233,DT=960508,ALMPF=99:PST=IS-NR-STBY"
__ 8.1 If the present state of the MM is in-service, abnormal,

page 29-798.
__ 8.2 If the present state of the MM is in-service, abnormal,

__ 8.3 If the present state of the MM is out-of-service,

abnormal, unequipped, assigned (OOS-ANR-UEQ-AS)
__ 8.4 If the present state of the MM is out-of-service,

abnormal, equipped, assigned (OOS-ANR-EQ-AS) go
__ 8.5 If the present state of the MM is out-of-service, normal

(OOS-NR) go to step 23, page 29-802.
__ 8.6 If the present state of the MM is in-service, normal,

standby (IS-NR-STBY) go to step 25, page 29-803.
__ 8.7 If the present state of the MM is in-service, normal,

active (IS-NR-ACT) go to step 28, page 29-805.

76.5500/29, Rev R 7/07 Page 29-797

Note: After entering the following command, the active LED on the RMM lights
while the active LED on the MM turns off.
__ 9. Edit the MM out-of-service (OOS) by entering one of the following

commands:
ED-EQPT::MM-xxxx:ctag::::OOS;
ED-EQPT::MM24-xxxx:ctag::::OOS;

M ctag COMPLD

M ctag COMPLD
commands:
System response:
M ctag COMPLD

"MM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5016233,DT=960508,ALMPF=99:PST=OOS-ANR-EQ-AS"
__ 10.1 If the system response for the MM is out-of-service,


abnormal, un equipped, assigned

__ 11. Visually verify that there is an MM present in the slot.

__ 11.1 If there is no MM in the slot, go to step 13, page 29-799.
__ 11.2 If there is an MM in the slot, go to step 20, page 29-801.
Page 29-798 7/07 76.5500/29, Rev R

__ 12. Remove the MM.

place.

steps:
backplane.


backplane?


__ 13.3.3 If the removed MM is not to be reinserted,

and a new module is to be used, go to
step 14, page 29-799.
__ 13.3.4 If the removed MM is to be reinserted, go


the module removed in step 12,
page 29-799, or if the slot is not
go to step 16.

page 29-799, go to step 17.
76.5500/29, Rev R 7/07 Page 29-799



loose or missing?

to step 14.

step 17.
__ 16. Delete the module type provisioned in the slot by entering the following
command:
DLT-EQPT::MM-xxxx:ctag;
DLT-EQPT::MM24-xxxx:ctag;
System response:
M ctag COMPLD
__ 17. Insert the MM.
Page 29-800 7/07 76.5500/29, Rev R

commands:
System response:
M ctag COMPLD

"MM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5016233,DT=960508,ALMPF=99:PST=OOS-NR"

__ 19.2 If the system response for the MM is not out-of-service,

__ 20. Diagnose the problem on the faulted MM by entering one of the

following commands:
DGN-EQPT::MM-xxxx:ctag::,ITER=3;
DGN-EQPT::MM24-xxxx:ctag::,ITER=3;
System response:
M ctag COMPLD

"MM-0981:PASS-3"
"MM-0981:FAIL-0"
__ 20.1 If the system response generates the following alarm


failed iterations, return to step 19.

step 21, page 29-801.
/* Parameter is inconsistent with the type of the physical equipment */
76.5500/29, Rev R 7/07 Page 29-801

__ 22. Diagnose the problem on the faulted MM by entering one of the

following commands:
DGN-EQPT::MM-xxxx:ctag;
DGN-EQPT::MM24-xxxx:ctag;
System response:
M ctag COMPLD

"MM-0981:PASS-1"
"MM-0981:FAIL-0"


__ 23. Edit the faulted MM in-service (IS) by entering one of the following
commands:
ED-EQPT::MM-xxxx:ctag::::IS;
ED-EQPT::MM24-xxxx:ctag::::IS;
System response:
M ctag COMPLD
Page 29-802 7/07 76.5500/29, Rev R

commands:
System response:
M ctag COMPLD

"MM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5016233,DT=960508,ALMPF=99:PST=IS-NR-STBY"

listed above, go to step 3, page 29-795.
__ 24.2 If the system response for the MM is in-service, normal,

standby (IS-NR-STBY), go to step 25.
__ 24.3 If the system response for the MM is in-service, normal,

commands:
System response:
M ctag COMPLD

"RMM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5070516,DT=960516,ALMPF=99:PRTN MM=MM-0193,
PRTN TYPE=RECV:PST=IS-NR-ACT"
Caution:
Note: After entering the following command, the active LED on the RMM turns
off while the active LED on the MM lights.
76.5500/29, Rev R 7/07 Page 29-803

__ 26. Perform a protection switch on the faulted MM by entering one of the

following commands:
SW-TOWKG-EQPT::MM-xxxx:ctag;
SW-TOWKG-EQPT::MM24-xxxx:ctag;
Where: xxxx = SDF number of the faulted MM from the

PROTN-MM field in step 25, page 29-803.
System response:
M ctag COMPLD
commands:
System response:
M ctag COMPLD

"MM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5016233,DT=960508,ALMPF=99:PST=IS-NR-ACT"
__ 27.1 If the system response verifies that the MM is in-service,

page 29-803.

page 29-805.
Page 29-804 7/07 76.5500/29, Rev R

command:
System response:
M ctag COMPLD

PRTN MM=MM-0193,PRTN TYPE=RECV:PST=IS-NR-ACT"
__ 28.1 If the system responses verifies that the RMM is

page 29-794, to troubleshoot the MM that switched to
protection.
__ 28.2 If the system responses verifies that the RMM is

in-service, normal, standby (IS-NR-STBY), go to
step 29.



M ctag COMPLD

M ctag COMPLD

"RMM-0035,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"

message.
76.5500/29, Rev R 7/07 Page 29-805



End of Procedure
Page 29-806 7/07 76.5500/29, Rev R

Redundant Mapping Modules (RMM)

6.44 In this section, you will troubleshoot the alarmed redundant Mapping
Module (RMM).
6.45 A spare RMM may be required in order to perform this procedure. Refer to
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */
command:
System response:
M ctag COMPLD


76.5500/29, Rev R 7/07 Page 29-807



M ctag COMPLD

M ctag COMPLD


faulted RMM, follow your company's prescribed

RMM, go to step 4.

commands:
System response:
M ctag COMPLD

__ 4.1 If the present state of the RMM is in-service, abnormal,

page 29-809.
__ 4.2 If the present state of the RMM is in-service, abnormal,

__ 4.3 If the present state of the RMM is out-of-service,

abnormal, unequipped, assigned (OOS-ANR-UEQ-AS)
__ 4.4 If the present state of the RMM is out-of-service,

abnormal, equipped, assigned (OOS-ANR-EQ-AS) go
__ 4.5 If the present state of the RMM is out-of-service, normal

(OOS-NR) go to step 18, page 29-813.

standby (IS-NR-STBY) go to step 20, page 29-814.
Page 29-808 7/07 76.5500/29, Rev R


active (IS-NR-ACT) go to Mapping Modules (MM),
page 29-794.

__ 5. Edit the RMM out-of-service (OOS) by entering one of the following

commands:
ED-EQPT::RMM-xxxx:ctag::::OOS;
ED-EQPT::RMM24-xxxx:ctag::::OOS;

M ctag COMPLD

M ctag COMPLD
__ 6. Retrieve the status of the faulted RMM by entering one of the following
commands:
System response:
M ctag COMPLD

__ 6.1 If the system response for the RMM is out-of-service,



76.5500/29, Rev R 7/07 Page 29-809

__ 7. Visually verify that there is a RMM present in the slot.

__ 7.1 If there is a RMM in the slot, go to step 8.
__ 7.2 If there is no RMM in the slot, go to step 9.
__ 8. Remove the RMM and place it in an anti-static bag.

steps:
backplane.


backplane?


Density DS1, EPM, OC-3, and OC-12, and OPM48 port modules currently
have no alternate types, so they may always back each other up.
Page 29-810 7/07 76.5500/29, Rev R



loose or missing?


step 12.
__ 12. Insert the RMM.
__ 14. Retrieve the status of the faulted module by entering the following
command:
Where: xxxx = SDF of the faulted module.
System response:
M ctag COMPLD

"RMM-0769:TYPE=MM3A:HWV=81.5544A RA,SN=LI0508518,DT=970915, ALMPF=99:PST=OOS-NR"

__ 14.2 If the system response for the RMM is in-service,

76.5500/29, Rev R 7/07 Page 29-811

__ 15. Diagnose the problem on the faulted RMM by entering one of the
following commands:
DGN-EQPT::RMM-xxxx:ctag::,ITER=3;
DGN-EQPT::RMM24-xxxx:ctag::,ITER=3;
System response:
M ctag COMPLD

"RMM-0981:PASS-3"
"RMM-0981:FAIL-0"


step 16.
__ 16. Reseat the RMM.

__ 17. Diagnose the problem on the faulted RMM by entering one of the
following commands:
DGN-EQPT::RMM-xxxx:ctag;
DGN-EQPT::RMM24-xxxx:ctag;
System response:
M ctag COMPLD

"RMM-0981:PASS-1"
"RMM-0981:FAIL-0"


Page 29-812 7/07 76.5500/29, Rev R

__ 18. Edit the RMM in-service (IS) by entering one of the following
commands:
ED-EQPT::RMM-xxxx:ctag::::IS;
ED-EQPT::RMM24-xxxx:ctag::::IS;
System response:
M ctag COMPLD
__ 19. Retrieve the status of the faulted RMM by entering one of the following
commands:
System response:
M ctag COMPLD


normal, active (IS-NR-ACT), go to Mapping Modules
(MM), page 29-794.

page 29-814.
__ 19.3 If the system response for the RMM is anything other

than what is listed above, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070
76.5500/29, Rev R 7/07 Page 29-813

__ 20. Retrieve all alarm conditions:


M ctag COMPLD

M ctag COMPLD


message.
__ 20.1.2 If no, go to step 21.


End of Procedure
Page 29-814 7/07 76.5500/29, Rev R

Mapping Interface Module (MIM)

6.46 In this section, you will troubleshoot the alarmed Mapping Interface
Module (MIM).
6.47 A spare MIM may be required in order to perform this procedure. Refer to
__ 1.1 If you are troubleshooting a MIM96E, go to 4xGbE Port
Module (MIM96E), page 29-824.
__ 1.2 If you are troubleshooting a MIM96, continue with this

procedure.

following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */
command:
System response:
M ctag COMPLD


76.5500/29, Rev R 7/07 Page 29-815



M ctag COMPLD

M ctag COMPLD

"MIM96-65-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"
"MIM96-67-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Link Failure Detected at both

MM/RMM from MIM\":,ISLTD"

faulted MIM, follow your company's prescribed
__ 4.2 If the system response verifies that a "Link Failure

Detected at both MM/RMM from MIM" condition is
posted against the MM24E, go to Mapping Modules
(MM), page 29-794.
__ 4.3 If any other alarm condition is posted against the faulted

MIM, go to step 5.
__ 5. Retrieve the status of the MIMs by entering the following command:

RTRV-EQPT::MIM96-xxxx-A&&-B:ctag;
Where: xxxx = First SDF on the port shelf.
System response:
M ctag COMPLD

"MIM96-1793-A::TYPE=MIM96,HWV=81.5597RC,SN=RI1550621,DT=030613,ALMPF=99:
PST=IS-NR-STBY"
"MIM96-1793-B::TYPE=MIM96,HWV=81.5597RC,SN=RI1550653,DT=030612,ALMPF=99:
PST=IS-NR-ACT"
__ 5.1 If the non-alarmed MIM is in-service, normal, standby

__ 5.2 If the non-alarmed MIM is in-service, normal, active

Page 29-816 7/07 76.5500/29, Rev R

__ 6. Switch the status of the non-faulted MIM to in-service, normal, active

(IS-NR-ACT) by entering the following command:
SW-DX-EQPT::MIM96-xxxx-y:ctag;

y = Non-alarmed MIM (A or B).
System response:
M ctag COMPLD

"ACT=MIM96-0513-B,STBY=MIM96-0513-A"
__ 7. Retrieve the status of the faulted MIM by entering the following

command:
RTRV-EQPT::MIM96-xxxx-y:ctag;

y = Faulted MIM (A or B).
System response:
M ctag COMPLD

"MIM96-65-A::HWV=81.5597 RC,SN=LI5706360,DT=971120,ALMPF=99:PST=IS-NR-STBY"
__ 7.1 If the present state of the MIM is in-service, abnormal,

standby (IS-ANR-STBY), go to step 8, page 29-818.
__ 7.2 If the present state of the MIM is in-service, abnormal,

unequipped (IS-ANR-UEQ), go to step 10,
page 29-818.
__ 7.3 If the present state of the MIM is out-of-service,

abnormal, unequipped (OOS-ANR-UEQ), go to step 10,
page 29-818.
__ 7.4 If the present state of the MIM is out-of-service,

abnormal, equipped (OOS-ANR-EQ), go to step 18,
page 29-821.
__ 7.5 If the present state of the MIM is out-of-service, normal

__ 7.6 If the present state of the MIM is in-service, normal,

__ 7.7 If the present state of the MIM is in-service, normal,


76.5500/29, Rev R 7/07 Page 29-817

__ 8. Edit the faulted MIM out-of-service (OOS) by entering the following

command:
ED-EQPT::MIM96-xxxx-y:ctag::::OOS;

System response:
M ctag COMPLD

command:

System response:
M ctag COMPLD

"MIM96-65-A::HWV=81.5597 RC,SN=LI5706360,DT=971120,ALMPF=99:PST=OOS-ANR-EQ"
__ 9.1 If the system response for the MIM is out-of-service,

abnormal, unequipped (OOS-ANR-UEQ), go to
step 10.

abnormal, equipped (OOS-ANR-EQ), go to step 18,
page 29-821.

__ 10. Visually verify that there is a MIM present in the slot.

__ 10.1 If there is a MIM in the slot, go to step 11.
__ 10.2 If there is no MIM in the slot, go to step 14, page 29-819.
__ 11. Remove the MIM from the shelf, place the module in an anti-static bag,
Page 29-818 7/07 76.5500/29, Rev R

__ 13. Check the module that is to be inserted for physical damage by


loose or missing?
__ 13.4.1 If the answer is yes to any of the above

questions, the module is damaged and
you will need to replace it with a new
MIM. Go to step 14.
__ 13.4.2 If the answer is no to all of the above

questions, the module can be reinserted.
Go to step 14.

steps:
backplane.


backplane?


76.5500/29, Rev R 7/07 Page 29-819

Warning:
__ 15. Insert the MIM.
command:

System response:
M ctag COMPLD

"MIM96-65-A::HWV=81.5597 RC,SN=LI5706360,DT=971120,ALMPF=99:PST=OOS-NR"
__ 17.1 If the system response for the MIM is anything other

than out-of-service, normal (OOS-NR), go to step 4,
page 29-816.

Page 29-820 7/07 76.5500/29, Rev R

__ 18. Diagnose the problem on the faulted MIM by entering the following
command:
DGN-EQPT::MIM96-xxxx-y::,ITER=3;
Where: xxxx = SDF number of the faulted MIM.

System response:
M ctag COMPLD

"MIM96-0129-A:PASS-3"
/* Number of iterations that passed. */
"MIM96-0129-A:FAIL-0"
/* Number of iterations that failed. */

step 19.


__ 20. Diagnose the problem on the faulted MIM by entering the following
command:
DGN-EQPT::MIM96-xxxx-y;

System response:
M ctag COMPLD

"MIM96-0129-A:PASS-1"
"MIM96-0129-A:FAIL-0"


76.5500/29, Rev R 7/07 Page 29-821

__ 21. Edit the faulted MIM in-service (IS) by entering the following
command:
ED-EQPT::MIM96-xxxx-y:ctag::::IS;

System response:
M ctag COMPLD
command:

System response:
M ctag COMPLD
Sample output for the MIM96:

__ 22.1 If the system response for the MIM is in-service, normal,

standby (IS-NR-STBY), go to step 23.
__ 22.2 If the system response is in-service, normal, active

__ 23. Perform a protection switch on the faulted MIM by entering the

following command:
SW-DX-EQPT::MIM96-xxxx-y:ctag;

System response:
M ctag COMPLD
command:

System response:
M ctag COMPLD

"MIM96-65-A::HWV=81.5597 RC,SN=LI5706360,DT=971120,ALMPF=99:PST=IS-NR-ACT"
Page 29-822 7/07 76.5500/29, Rev R

__ 24.1 If the system response verifies that the MIM is

in-service, normal, active (IS-NR-ACT), go to step 25.

__ 25. Retrieve the status of the non-faulted MIM by entering the following
command:

y = Non-faulted MIM (A or B).
System response:
M ctag COMPLD
Sample response for a MIM96:

__ 25.1 If the system response verifies that the non-faulted MIM

is in-service, normal, standby (IS-NR-STBY), go to step
26, page 29-823.



M ctag COMPLD

M ctag COMPLD


message.
__ 26.1.2 If no, go to step 27.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-823

4xGbE Port Module (MIM96E)

6.48 In this section, you will troubleshoot the alarmed 4xGbE Port Module
(MIM96E).
6.49 A spare MIM may be required in order to perform this procedure. Refer to
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */
command:
System response:
M ctag COMPLD


Page 29-824 7/07 76.5500/29, Rev R



M ctag COMPLD

M ctag COMPLD

"MIM96-67-A,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Link Failure Detected at both

MM/RMM from MIM\":,ISLTD"

faulted MIM, follow your company's prescribed
__ 3.2 If the system response verifies that a "Link Failure

Detected at both MM/RMM from MIM" condition is
posted against the MM24E, go to Mapping Modules
(MM), page 29-794.
__ 3.3 If any other alarm condition is posted against the faulted

MIM96E, go to step 4.
__ 4. Retrieve the status of the MIMs by entering the following command:

System response:
M ctag COMPLD

"MIM96-0001-A:TYPE=MIM96EX4:HWV=81.5597ERA,SN=EL02103741,DT=910507,ALMPF=99,AGG=YES,
MNG=YES:PST=IS-NR"
"MIM96-0001-B:TYPE=MIM96EX4:HWV=81.5597ERA,SN=EL02103751,DT=910507,ALMPF=99,AGG=NO,
MNG=NO:PST=IS-NR"
__ 4.1 If the EPS is not running in unprotected mode and is

populated with two MIM96Es, go to step 5,
page 29-826.
__ 4.2 If the EPS is running in unprotected mode and only one

MIM96E is populated, go to step 9, page 29-827.
76.5500/29, Rev R 7/07 Page 29-825

__ 5. Retrieve the status of the PTs for the non-faulted MIM96E by entering
RTRV-EQPT::PT-xxxx-yy-1&&-4:ctag;

yy = Slot number (10 - 11).
System response:
M ctag COMPLD
Followed by lines of data similar to the following format:

"PT-513-11-1:TYPE=1000SX:HWV=partnumberRev,SN=EL0210372,DT=050107,ALMPF=99,
CLEI=SNCLPV42AA,PTVENDOR=VENDORNAME,PTVENDORPN=VENDOR_PARTNUMBER:PST=IS-NR"
__ 5.1 Verify that the present state of the PTs is in-service,

normal (IS-NR).
__ 6. Repeat step 5 for the PTs of the faulted MIM96E.

__ 7. Edit the PTs out-of-service (OOS) by entering the following command:
ED-EQPT::PT-xxxx-yy-1&&-4:ctag:::MODE=FRCD:OOS;

System response:
M ctag COMPLD
Note: Errors may occur during this protection switch -- this is normal. However,
if the signal is completely lost during the procedure, a problem exists and
it must be corrected. If necessary, follow your company’s prescribed
North America).
Page 29-826 7/07 76.5500/29, Rev R

__ 8. Retrieve the status of the PTs for the faulted MIM96E by entering the
following command:

System response:
M ctag COMPLD

CLEI=SNCLPV42AA,PTVENDOR=VENDORNAME,PTVENDORPN=VENDOR_PARTNUMBER:PST=OOS-NR"
__ 8.1 Verify that the present state of the PTs is out-of-service,

normal (OOS-NR).
Caution:
Editing the MIM96E out-of-service (OOS) when the EPS is running in unpro-
tected mode will result in a traffic loss until the MIM96E is returned to an
in-service (IS) state.
__ 9. Edit the faulted MIM out-of-service (OOS) by entering the following

command:
ED-EQPT::MIM96-xxxx-y:ctag::::OOS;

y = Faulted MIM96E (A or B).
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-827

__ 10. Retrieve the status of the MIM96Es by entering the following

command:
System response:
M ctag COMPLD
Sample output for an unprotected MIM96E:

"MIM96-513-A:TYPE=MIM96EX4:HWV=81.5597ERA,SN=EL02103741,DT=910507,ALMPF=99,AGG=NO,
MNG=YES:PST=OOS-ANR"
"MIM96-513-B:::PST=OOS-ANR-UEQ-UAS"
Sample output for a protected MIM96E:

"MIM96-513-B:TYPE=MIM96EX4:HWV=81.5597ERA,SN=EL02103751,DT=910507,ALMPF=99,AGG=YES,
MNG=NO:PST=IS-NR"
__ 10.1 If the present state of the faulted MIM96E is in-service,

__ 10.2 If the present state of the faulted MIM96E is in-service,

page 29-829.
__ 10.3 If the present state of the faulted MIM96E is



page 29-832.

listed above, follow your company’s prescribed
Page 29-828 7/07 76.5500/29, Rev R


__ 11. Visually verify that there is a MIM96E present in the slot.

__ 11.1 If there is a MIM96E in the slot, go to step 12.
__ 11.2 If there is no MIM96E in the slot, go to step 13.
__ 12. Perform the following substeps to remove the MIM96E:

__ 12.1 Disconnect the Ethernet management cable from the
Ethernet management port (RJ45 connector).
__ 12.2 Disconnect the transmit and receive facility fibers from

the four pluggable transceivers (PTs).
__ 12.3 If necessary, remove the four PTs from the MIM96E and
place them in anti-static bags.

place.


loose or missing?
__ 14.4.1 If the answer is yes to any of the above

questions, the module is damaged and
you will need to replace it with a new
MIM96E. Go to step 15, page 29-830.
__ 14.4.2 If the answer is no to all of the above

questions, the module can be reinserted.
76.5500/29, Rev R 7/07 Page 29-829


steps:
backplane.


backplane?


go to step 16.
Warning:
__ 16. Insert the MIM96E.

__ 16.1 Reconnect the Ethernet management cable.
__ 16.2 If required, reinsert the four PTs from the failed

MIM96E.
__ 16.3 Reconnect the PT facility fibers.
Page 29-830 7/07 76.5500/29, Rev R


command:
System response:
M ctag COMPLD


"MIM96-513-B:TYPE=MIM96EX4:HWV=81.5597ERA,SN=EL02103751,DT=910507,ALMPF=99,AGG=YES,
MNG=NO:PST=IS-NR"
__ 18.1 If the system response for the MIM96Es is

page 29-832.
__ 18.2 If the system response for the MIM96Es is anything

other than out-of-service, normal (OOS-NR), go to step
3, page 29-825.
__ 19. Diagnose the problem on the faulted MIM96E by entering the following
command:
DGN-EQPT::MIM96-xxxx-y::,ITER=3;

System response:
M ctag COMPLD

"MIM96-0129-A:PASS-3"
"MIM96-0129-A:FAIL-0"


step 20, page 29-832.
76.5500/29, Rev R 7/07 Page 29-831


__ 21. Diagnose the problem on the faulted MIM96E by entering the following
command:
DGN-EQPT::MIM96-xxxx-y;

System response:
M ctag COMPLD

"MIM96-0129-A:PASS-1"
"MIM96-0129-A:FAIL-0"


__ 22. Edit the faulted MIM96E in-service (IS) by entering the following
command:
ED-EQPT::MIM96-xxxx-y:ctag::::IS;

System response:
M ctag COMPLD
__ 23. Retrieve the status of the faulted MIM96E by entering the following
command:

System response:
M ctag COMPLD
MNG=YES:PST=IS-NR"
__ 23.1 Verify from the system response that the MIM96E is

Page 29-832 7/07 76.5500/29, Rev R

__ 24. Edit the PTs in-service (IS) by entering the following command:
ED-EQPT::PT-xxxx-yy-1&&-4:ctag::::IS;

System response:
M ctag COMPLD
__ 25. Retrieve the status of the PTs for the faulted MIM96E by entering the
following command:

System response:
M ctag COMPLD

__ 25.1 Verify that the present state of the PTs is in-service,

normal (IS-NR).
76.5500/29, Rev R 7/07 Page 29-833


command:
System response:
M ctag COMPLD

MNG=YES:PST=IS-NR"

MNG=YES:PST=IS-NR"
"MIM96-513-B:TYPE=MIM96EX4:HWV=81.5597ERA,SN=EL02103751,DT=910507,ALMPF=99,AGG=NO,
MNG=NO:PST=IS-NR"

__ 26.2 If the system response verifies that the faulted MIM96E

is now in-service, normal (IS-NR), go to step 27.


M ctag COMPLD

M ctag COMPLD


message.
__ 27.1.2 If no, go to step 28.


End of Procedure
Page 29-834 7/07 76.5500/29, Rev R

Pluggable Transceiver (PT)

6.50 In this section, you will troubleshoot the alarmed Pluggable Transceiver
(PT).
6.51 A spare PT may be required in order to perform this procedure. Refer to
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */
command:
System response:
M ctag COMPLD


76.5500/29, Rev R 7/07 Page 29-835



M ctag COMPLD

M ctag COMPLD

"PT-362-10-2,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure
detected\":,ISLTD"
__ 3.1 If there are no alarm conditions posted against the PTs,


PTs, go to step 4.
__ 4. Retrieve the status of the faulted PT by entering one of the following

commands:
For PTs that support the SDF based addressing:
RTRV-EQPT::PT-xxxx-yy-z:ctag;

z = Port number (1 - 4).
For PTs that support shelf-based addressing:

RTRV-EQPT::PTX-SHx-y-z:ctag;

y = Slot number in the range (1 - 8, 13, 14, 17, 18).
z = Port number within the supporting module in the
range of (1 - 8).
System response:
M ctag COMPLD

CLEI=SNCLPV42AA,PTVENDOR=VENDORNAME,PTVENDORPN=VENDOR_PARTNUMBER:PST=IS-ANR,
SST=SENA"
__ 4.1 If the present state of the PT is in-service, abnormal

__ 4.2 If the present state of the PT is in-service, abnormal,

Page 29-836 7/07 76.5500/29, Rev R

__ 4.3 If the present state of the PT is out-of-service,

__ 4.4 If the present state of the PT is out-of-service,

__ 4.5 If the present state of the PT is out-of-service, normal

__ 4.6 If the present state of the PT is in-service, normal

__ 4.7 If the system response from step 4, page 29-836 shows

SST=SENA, there is a problem with the supporting
entity for the PT. Go to the appropriate section to
troubleshoot the supporting entity (MIM, NIM, PAM,
OPM48, CAM, TSI96P).

__ 5. Edit the faulted PT out-of-service (OOS) by entering the following

command:
ED-EQPT::PT-xxxx-yy-z:ctag:::MODE=FRCD:OOS;


ED-EQPT::PTX-SHx-y-z:ctag:::MODE=FRCD:OOS;

range of (1 - 8).
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-837

__ 6. Retrieve the status of the faulted PT by entering the following

command:



range of (1 - 8).
System response:
M ctag COMPLD

__ 6.1 If the system response for the PT is out-of-service,

to step 7.

__ 7. Visually verify that there is a PT present in the slot.

__ 7.1 If there is a PT in the slot, go to step 8.
__ 7.2 If there is no PT in the slot, go to step 11, page 29-839.
__ 8. If necessary, remove the SDF cable connected to the PT.

__ 9. Remove the PT.
__ 9.1 Place the PT in an anti-static bag and put it in a safe
place.
__ 10. Determine which PT type is to be inserted into the empty slot.

level of the PT needed, depending on feature package
and what shelf type you are troubleshooting.
Page 29-838 7/07 76.5500/29, Rev R

Warning:
__ 11. Insert the PT.

__ 12. If necessary, reconnect the SDF cable connected to the PT.
__ 13. Wait six seconds. What is the fault LED status on the supporting
module for the PT you just inserted?
__ 13.1 If the fault LED remain lit, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070

command:



range of (1 - 8).
System response:
M ctag COMPLD

76.5500/29, Rev R 7/07 Page 29-839


__ 14.2 If the system response for the PT is abnormal (ANR),

there may be a problem with the supporting module. Go
to the appropriate section to troubleshoot the supporting
module.

page 29-836.
__ 15. Edit the faulted PT in-service (IS) by entering the following command:
ED-EQPT::PT-xxxx-yy-z:ctag::::IS;


ED-EQPT::PTX-SHx-y-z:ctag::::IS;

range of (1 - 8).
System response:
M ctag COMPLD
Page 29-840 7/07 76.5500/29, Rev R


command:



range of (1 - 8).
System response:
M ctag COMPLD

__ 16.1 If the system response for the PT is in-service, normal

(IS-NR), go to step 17.

listed above, return to step 3, page 29-836.


M ctag COMPLD

M ctag COMPLD


message.
76.5500/29, Rev R 7/07 Page 29-841



End of Procedure
Page 29-842 7/07 76.5500/29, Rev R

Fan Tray Module

6.52 In this section, you will troubleshoot the alarmed fan tray module for a port
shelf or Consolidated Core Switch Shelf.
Warning:
Verify that you have a spare fan tray module with you before you remove the
faulted fan tray module. The replacement fan tray module must be inserted into
the fan tray within one minute of removing the defective fan tray module. If you
wait longer than one minute to replace the fan tray module, the shelf may
overheat.
6.53 A spare fan tray module may be required in order to perform this
procedure. Refer to Tellabs 5500/5500S Software Release Document,
76.5500/16, to verify the correct revision level of the module needed, depending on
feature package and what shelf type you are troubleshooting.
following command:

pid = Password.
System response:
M ctag COMPLD

prosecution. */
command:
System response:
M ctag COMPLD


76.5500/29, Rev R 7/07 Page 29-843



M ctag COMPLD

M ctag COMPLD

"FAN-0001-A,EQPT:MJ,FAN,SA,01-03,23-59-59,NEND:\"Fan module has single internal
failure\":,ISLTD"
"FILTER-0161,EQPT:MN,MAR,NSA,07-28,15-03-48,NEND:\"Air filter routine maintenance

required\":,ISLTD"

faulted fan tray module or filter, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070

fan tray module or filter, go to step 4, page 29-844.
__ 4. Retrieve the shelf by entering one of the following commands:
For a Universal Port Shelf:

RTRV-EQPT::PGCU-xxxx:ctag;
For a Consolidated Core Switch Shelf:

RTRV-EQPT::CGC-SHx-10:ctag:
Where: x = Shelf indentifier (1 or 2).
System response:
M ctag COMPLD

"FAN-65-A::HWV=81.55040 RA,ALMPF=99:PST=ANR-EQ"
"FAN-65-B::HWV=81.55040 RA,ALMPF=99:PST=NR"
"FILTER-65::FILTEREXP=011130,ALMPF=99:PST=NR"
__ 4.1 If the present state of the faulted fan tray module is

abnormal, unequipped (ANR-UEQ), or abnormal,
equipped (ANR-EQ), go to step 5.
__ 4.2 If the present state of the faulted fan tray module is

normal (NR), this procedure is complete.
Page 29-844 7/07 76.5500/29, Rev R

__ 4.3 If the present state of the filter is anything other than

normal (NR), go to step 10, page 29-846.

Warning:
Verify that you have a spare fan tray module with you before you remove the
faulted fan tray module. The replacement fan tray module must be inserted into
the fan tray within one minute of removing the defective fan tray module. If you
wait longer than one minute to replace the fan tray module, the shelf may
overheat.
__ 5. Refer to Replacing a Faulted Fan Tray Module, located in Tellabs

5500/5500S Replacement Procedures, 76.5500/55, for the
appropriate procedure to replace the fan tray module.
__ 6. After a two minute module download, what is the power LED status of
the module?
__ 6.1 If the power LED is amber, only one power feed is
active. Go to step 7.
__ 6.2 If the power LED is green and the fault LED is off, go to
step 11, page 29-849.
__ 6.3 If the power LED is green and the fault LED is on, follow
__ 7. Verify that the circuit breaker or fuse at the B/FAP or F/FAP is

functioning normally.
__ 8. Is a GMT fuse blown? Refer to Figure 6.27, page 29-846 for GMT fuse
locations.
__ 8.1 If a fuse is not blown, go to step 9, page 29-846.
__ 8.2 If a fuse is blown, replace the fuse. Then go to step 11,

page 29-849.
76.5500/29, Rev R 7/07 Page 29-845

Figure 6.27 GMT Fuse Locations on the B/FAP and F/FAP
Power Distribution Unit Side A Power Distribution Unit Side B
GMT fuses GMT fuses
__ 9. Is the power feed missing?
Note: The power feed connects the B/FAP or F/FAP to the fan tray.
__ 9.1 If the power feed is missing, replace the power feed.

__ 10. Is the fan filter missing? Refer to Figure 6.28, page 29-848, for a High
Density Port Shelf. Refer to Figure 6.29, page 29-849, for a
Consolidated Core Switch Shelf.
__ 10.1 If the fan filter is missing, perform the following substeps
replace the fan filter:
__ 10.1.1 Loosen the thumbscrew on the fan door

and open the door.
__ 10.1.2 Use the handle to pull the filter out until

the fault LEDs on the fans blink red and
the fans stop.
__ 10.1.3 Once the fans have stopped, remove the

filter completely and replace it within one
minute.
Page 29-846 7/07 76.5500/29, Rev R

Warning:
The fans will stop momentarily to allow the filter to be replaced. After one minute
the fans will resume at high speed to avoid overheating. If the filter is not
replaced before the fans resume, debris may be blown into the modules,
possibly causing damage to the modules.
__ 10.1.4 When the filter is replaced, the fault LEDs

on the fans will stop blinking and the fans
will start.
__ 10.1.5 Close the fan door and tighten the

thumbscrew.
__ 10.1.6 Go to step 11, page 29-849.
__ 10.2 If the fan filter is not missing, is the following alarm

message being generated:
"FILTER-0161,EQPT:MN,MAR,NSA,07-28,15-03-48,NEND:\"Air filter routine maintenance

required\":,ISLTD"
__ 10.2.1 If yes, the fan filter needs to be replaced

with a new fan filter. Go to substep 10.1,
page 29-846.

North America).
76.5500/29, Rev R 7/07 Page 29-847

Figure 6.28
Page 29-848
flow
a closed
required to
maintain air
shelf door is
fan tray door

1
20
GCU- Copy A DPMU- Copy A
2
Universal Slot (Port Modules Only)
fan tray chassis

6. Troubleshooting the Port Shelves
3
4
5
6
MM24 #1
7
warmer air leaves from rear of air baffle
MM24 #2
HDPS with Fan Tray Assembly
8
RMM24
9
TSI96 - Copy A
MIM96 - Copy A
10
MIM96 - Copy B
11
TSI96 - Copy B
12
MM24 #3
13
7/07
MM24 #4
14
15

16

17
18

21
GCU- Copy B
19
DPMU- Copy B
shelf
air baffle
air flow drawn in

fan tray filter
for next shelf
2 fan tray modules

air intake baffle
high density port
76.5500/29, Rev R
Figure 6.29 55C80/55C80-HA Fan Tray Assembly
warmer air leaves from rear of air baffle
air baffle
auxiliary filler
auxiliary filler
NIN/PAM/filler
NIN/PAM/filler
NIN/PAM/filler
NIN/PAM/filler
NIN/PAM/filler
NIN/PAM/filler
NIN/PAM/filler
NIN/PAM/filler
PAM/filler
PAM/filler
PAM/filler
PAM/filler
CCSM 1
CCSM 2
21 22
filler
filler
filler
fillet
a closed
shelf door CCS shelf
CGC filler
is required
CGC
to maintain
air flow
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
fan tray filter
fan tray chassis
2 fan modules
fan tray door air flow drawn in
__ 11. Retrieve the shelf by entering one of the following commands:

For a Universal Port Shelf:
For a Consolidated Core Switch Shelf:

RTRV-EQPT::CGC-SHx-10:ctag:
Where: x = Shelf indentifier (1 or 2).
System response:
M ctag COMPLD

"FAN-65-A::HWV=81.55040 RA,ALMPF=99:PST=NR"
"FAN-65-B::HWV=81.55040 RA,ALMPF=99:PST=NR"
76.5500/29, Rev R 7/07 Page 29-849

__ 11.1 If the present state of the faulted fan tray module is now
normal (NR), this procedure is complete.

End of Procedure
Page 29-850 7/07 76.5500/29, Rev R

Troubleshooting Manual 7. Troubleshooting the Facilities
7. Troubleshooting the Facilities
7.01 This section contains procedure to troubleshoot a problem occurring on

the facilities.
7.02 When troubleshooting the facilities, always check for any pertinent Product
Performance Notices (PPNs). There may be an issue that has already been
identified that will shorten the time required to troubleshoot the facilities.
7.03 The DUALNCX = ON/OFF parameter is configurable via the
ED-EQPT::NE command. When DUALNCX is set to ON, the Tellabs 5500/5500S
system will deny a cross-connect if the cross-connect could not be implemented
successfully in both network copies. When DUALNCX is set to OFF (the system
default), the Tellabs 5500/5500S system will complete the cross-connect
command even if the cross-connect could not be implemented successfully in both
network copies.
7.04 If you are troubleshooting the facilities because you received an M ctag
DENY message while attempting to enter a cross-connect, the port modules and
facilities are in-service, normal (IS-NR), and the DUALNCX parameter is set to ON,
you may have a problem with the TSI, ESM, or CSM. Go to Section 3,
Troubleshooting the Network Complex, page 29-245.
Warning:
76.5500/29, Rev R 7/07 Page 29-851

7. Troubleshooting the Facilities Troubleshooting Manual
System Pre-Checks
following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */
__ 2. Verify that your login has the proper user privilege code (UPC) to
perform these procedures by entering the following command:
System response:
M ctag COMPLD




M ctag COMPLD

M ctag COMPLD

T1-1-1,T1:CR,SENA,SA,01-31,23-59-59,NEND,,,\"Line Interface Module Not Available"\"

page 29-853, to troubleshoot the faulted facility listed in
the alarm message(s) received.
End of Procedure
Page 29-852 7/07 76.5500/29, Rev R


7.07 Facility alarm messages are listed in the Table 7.1, page 29-855, through
Table 7.13, page 29-887. Each table lists the alarm messages for the facility, the
description of that alarm message, a probable cause for the alarm, and then directs
you to the appropriate troubleshooting procedure.
7.08 Choose the correct table for the facility that is faulted:
• For DS1 Di-Group Termination (T1 DGR) alarm messages, refer to
Table 7.1, page 29-855.
• For DS1 Constituent Termination (T1 CST) alarm messages, refer to

Table 7.2, page 29-857.
• For DS1 Internal Termination (T1 TRMINT) alarm messages, refer to

Table 7.3, page 29-860.
• For DS2 Termination (T2) alarm messages, refer to Table 7.4,
page 29-862.
• For DS3 Di-Group Termination (T3 DGR) alarm messages, refer to

Table 7.5, page 29-863.
• For DS3 Constituent Termination (T3 CST) alarm messages, refer to

Table 7.6, page 29-866.
• For DS3 Internal Termination (DS3 TRMINT) alarm messages, refer

to Table 7.7, page 29-867.
• For Electrical Carrier 1 Termination (EC1) alarm messages, refer to

Table 7.8, page 29-869.
• For STS-1 Termination (STS1) alarm messages, refer to Table 7.9,

page 29-871.
• For Virtual Tributary 1 Termination (VT1) alarm messages, refer to

Table 7.10, page 29-874.
• For Optical Carrier n Termination (OC3, OC12, or OC48) alarm

messages, refer to Table 7.11, page 29-878.
• For STS3C Termination (STS3C) alarm messages, refer to Table

7.12, page 29-884.
• For DS1 VT1 Constituent Termination (T1 VTCST) alarm messages,

refer to Table 7.13, page 29-887.
• For T1 Internal Termination (T1INT) alarm messages, refer to Table

7.14, page 29-889.
• For Ethernet Termination (ETH) alarm messages, refer to Table 7.15,

page 29-890.
• For Ethernet Management Termination (ETHMNG) alarm messages,
refer to Table 7.16, page 29-891.
76.5500/29, Rev R 7/07 Page 29-853

• For Link Aggregation Group (LAG) alarm messages, refer to Table

7.17, page 29-892.
• For Point-to-Point Protocol (PPP) alarm messages, refer to Table

7.18, page 29-892.
• For Point-to-Point Protocol Group (PPPG) alarm messages, refer to

Table 7.19, page 29-893.
• For Virtual Concatenation Group (VCG) alarm messages, refer to
Table 7.20, page 29-894.
Page 29-854 7/07 76.5500/29, Rev R

DS1 Di-Group Termination (T1 DGR) Alarm Messages

7.09 To verify the meaning of the alarm message(s) received for a T1 DGR
facility, use the following table. The first column of the table lists the possible alarm
messages that can be generated for a T1 DGR facility. The second column lists a
alarm.
Table 7.1 T1 DGR Termination Alarm Messages

ACTLPBK Active Loopback - Command When a near-end internal loopback is A near-end internal loopback is
Requested NEND Internal activated on a DS1 digroup via the activated.
operate-loopback command, a Refer to Tellabs 5500/5500S Command
retrieve-condition TL1 command posts Reference Manual, 76.5500/13, for
the appropriate ACTLPBK condition code RLS-LPBK-T1 command.
against the termination.
Then go to DS1 Di-Group, Constituent,
or Internal Termination (T1 DGR, CST,
or TRMINT), page 29-897.
ACTLPBK Active Loopback - Command When a near-end line loopback is A near-end line loopback is activated.
Requested NEND Line activated on a DS1 digroup via the Refer to Tellabs 5500/5500S Command
operate-loopback command, a Reference Manual, 76.5500/13, for
retrieve-condition TL1 command posts RLS-LPBK-T1 command.
the appropriate ACTLPBK condition code
against the termination. Then go to DS1 Di-Group, Constituent,
AIS AIS alarm This DS1 has detected a continuous The far end is transmitting all ones to
stream of all ones condition on the indicate that it is no longer receiving a
receive path. signal. A problem has occurred on the
transmitting side. AIS is activated only
when a signal failure (interruption) has
been detected.
Go to DS1 Di-Group, Constituent, or

Internal Termination (T1 DGR, CST, or
TRMINT), page 29-897.
DATALINK ESF framing datalink failure Failed to detect one or more incoming Far end equipment is not sending data
detected DS1 Data Link messages. link messages.

FELOS Fault Escalation Loss of Signal The fault escalation feature for the T1 Verify that the fault escalation feature
detected has been configured, and a defect that has been correctly configured for the T1,
has been specified in this parameter has as well as for the terminations to which
been detected. the T1 is cross-connected. In Tellabs
5500 Command Reference, 76.5500/13,
refer to the RTRV-T1, RTRV-T3,
RTRV-VT1, and RTRV-STS1
commands to verify the FLTRC
parameter. Refer to the ED-T1, ED-T3,
ED-VT1, and ED-STS1 commands to
edit the FLTRC parameter.
76.5500/29, Rev R 7/07 Page 29-855

Table 7.1 T1 DGR Termination Alarm Messages (Continued)

INHALM Alarm Monitoring has been Alarm Monitoring has been inhibited by TL1 commands were used to inhibit the
inhibited (via command) setting ALM=INH, using ED-T1 or alarm monitoring function. Refer to
ENT-T1 commands. Tellabs 5500/5500S Command
Reference Manual, 76.5500/13, to allow
alarms using the ED-T1 command.

INHALM Performance and Alarm Performance and Alarm Monitoring TL1 commands were used to configure
Monitoring Suspension mode Suspension (PASUP) mode was set to the PASUP mode, causing the Inhibit
TRIG/DLY by using a TL1 command. Alarm (INHALM) condition posted
against the termination. Refer to Tellabs
Manual, 76.5500/13, to disable PASUSP
mode using the ED-T1 command.

ISD Idle signal has been detected on The termination is detected idle signal. This indicates a far end idle signal. Go to
termination DS1 Di-Group, Constituent, or Internal
Termination (T1 DGR, CST, or
PAINT TVT parity error detected on An internal path integrity error has been A connected network complex entity has
network copy x, where x equals detected on NC-A or NC-B. failed.
A or B
RED Red alarm A Loss of Frame or Loss of Signal Receive path of this DS1 has been
condition lasting 2.5 +/-.5 seconds has interrupted or severely impaired. Go to
occurred. DS1 Di-Group, Constituent, or Internal
SENA Line Interface Module Not The LIM supporting this digroup is not Either the supporting LIM has been
Available available. removed from its backplane slot or it has
failed.

SENA Port Module and Redundant Port This displays for each digroup of a PM The redundant port module was either
Module Not Available that has faulted without receiving already protecting a failed termination or
protection. Typically occurs when an it was unavailable.
RPM is protecting a group containing a
PM with an uncleared fault. A second Go to DS1 Di-Group, Constituent, or
faulted PM will not be protected and its Internal Termination (T1 DGR, CST, or
associated digroups will declare SENA TRMINT), page 29-897.
alarms. The RPM is also unavailable for
backing up if it is out-of-service (OOS) or
if it is inhibited from protection, such as in
PRTN=INH.
Page 29-856 7/07 76.5500/29, Rev R


T-BERH Line BER high threshold crossed The bit error rate high threshold register The most probable cause for BPVs is
for a DS1 digroup has exceeded the line noise from the facility.
setting defined by the grade of service
(GOS) table. A DS1 BER is calculated Go to DS1 Di-Group, Constituent, or
based on bipolar violations (BPVs). Internal Termination (T1 DGR, CST, or
T-BERL Line BER low threshold crossed The bit error rate low threshold register The most probable cause for BPVs is
for a DS1 digroup has exceeded the line noise from the facility.
setting defined by the grade of service
(GOS) table. A DS1 BER is calculated Go to DS1 Di-Group, Constituent, or
based on bipolar violations (BPVs). Internal Termination (T1 DGR, CST, or
YEL Yellow alarm Yellow alarm signal has been detected The node or equipment upstream of the
by this DS1. In SuperFrame, yellow far end has gone into red alarm;
alarm is indicated by setting bit 2 to 0 on therefore, the far end of this DS1 is
all 24 channels. In Extended transmitting a yellow alarm to indicate it
SuperFrame (ESF) this condition is has lost the signal.
signaled by a repeated pattern of eight
zeros and eight ones. Go to DS1 Di-Group, Constituent, or
DS1 Constituent (T1 CST) Termination Alarm Messages

7.10 To verify the meaning of the alarm message(s) received for a T1 CST
messages that can be generated for a T1 CST facility. The second column lists a
alarm.
Table 7.2 T1 CST Termination Alarm Messages

ACTLPBK Active Loopback - Command When a far end line loopback is A far-end line loopback is activated.
Requested FEND Line activated on a DS1 constituent via the Refer to Tellabs 5500/5500S Command
retrieve-condition TL1 command will RLS-LPBK-T1 command.
post the appropriate ACTLPBK
condition code against the termination. Then go to DS1 Di-Group, Constituent,
or Internal Termination (T1 DGR, CST, or
Requested NEND Line activated on a DS1 constituent via the Refer to Tellabs 5500/5500S Command
retrieve-condition TL1 command posts RLS-LPBK-T1 command.
the appropriate ACTLPBK condition
code against the termination. Then go to DS1 Di-Group, Constituent,
76.5500/29, Rev R 7/07 Page 29-857

Table 7.2 T1 CST Termination Alarm Messages (Continued)

ACTLPBK Active Loopback - Remotely When a near-end remote line loopback A near-end remote line loopback is
Requested NEND Line is activated on a DS1 constituent via activated. Refer to Tellabs 5500/5500S
the operate-loopback command, a Command Reference Manual,
retrieve-condition TL1 command posts 76.5500/13, for RLS-LPBK-T1
the appropriate ACTLPBK condition command.
code against the termination.
AIS AIS alarm This DS1 has detected a continuous The far-end is transmitting all ones to
stream of all ones (1s) condition on the indicate that it is no longer receiving a
receive path. signal. A problem has occurred on the
transmitting side. AIS is activated only
when a signal failure (interruption) has
been detected.

DATALINK ESF framing datalink failure The system failed to detect one or The far end equipment is not sending
detected more incoming DS1 Data Link data link messages.
messages.

INHALM Performance and Alarm Monitoring Performance and Alarm Monitoring TL1 commands were used to configure
Suspension mode Suspension (PASUP) mode was set to the PASUP mode, causing the Inhibit

ISD Idle signal has been detected on The termination is detected idle signal. This indicates a far end idle signal.
termination
PAINTGRT TVT parity error detected on An internal path integrity error has A connected network complex entity has
network copy x, where x equals A been detected on NC-A or NC-B. failed.
or B
Page 29-858 7/07 76.5500/29, Rev R


RED Red alarm A loss of frame or loss of signal Receive path of this DS1 has been
condition lasting 2.5 +/-.5 seconds has interrupted or severely impaired.
occurred.
SENA Port Module and Redundant Port This is displayed for each constituent The redundant port module was either
Module Not Available of a PM that has faulted without already protecting a failed termination or
receiving protection. Typically occurs was unavailable.
when an RPM is protecting a group
containing a PM with an uncleared Go to DS1 Di-Group, Constituent, or
fault. A second faulted PM is not Internal Termination (T1 DGR, CST, or
protected and its associated TRMINT), page 29-897.
constituent will declare SENA alarms.
The RPM is also unavailable for
backing up if it is out-of-service (OOS)
or if it is inhibited from protection, such
as the code PRTN=INH.
SENA Supporting T2 not available This alarm is generated when the T2 Associated T2 is either out-of-service
associated with the reporting T1 (OOS) or it has an abnormal condition.
constituent is not in-service, normal
(IS-NR). Go to DS1 Di-Group, Constituent, or
by this DS1. In SuperFrame (SF), far end has gone into red alarm;
yellow alarm is indicated by setting bit therefore, the far end of this DS1 is
2 to zero on all 24 channels. In transmitting a yellow alarm to indicate it
Extended SuperFrame (ESF) this has lost the signal.
condition is signaled by a repeated
pattern of eight zeros and eight ones. Go to DS1 Di-Group, Constituent, or
76.5500/29, Rev R 7/07 Page 29-859

DS1 Internal Termination (DS1 TRMINT) Alarm Messages

7.11 To verify the meaning of the alarm message(s) received for a DS1 internal
termination, use the following table. The first column of the table lists the possible
alarm messages that can be generated for a DS1 TRMINT. The second column
for the alarm.
Table 7.3 DS1 Internal Termination Alarm Messages

ACTLBPK Active Loopback - Command The user has attempted to configure a A loopback is already in place on the
Requested NEND CC near-end CC block loopback on a CCPMA.
CCPMA termination, but a loopback
already exists on this termination. If necessary, refer to Tellabs 5500
Provisioning, 76.5500/23, to disable the
existing loopback and create a new
one.
Requested NEND Internal activated on a DS1 via the activated.
operate-loopback command, a
retrieve-condition TL1 command posts Refer to Tellabs 5500/5500S Command
the appropriate ACTLPBK condition Reference Manual, 76.5500/13, for
code against the termination. RLS-LPBK-T1 command. Then go to
DS1 Di-Group, Constituent, or Internal
AIS AIS alarm This DS1 has detected an all-ones The far-end is transmitting all ones to
condition on the receive path. indicate that it is no longer receiving a
signal.

inhibited (via command) setting ALM=INH, using ED-T1 or alarm monitoring function.
ENT-T1 commands.
ISD Idle signal has been detected on The termination is detecting idle signal. This indicates a far-end idle signal.
the termination
NOCCPORT Termination is not being used A termination has been provisioned on The termination is incompletely
within CC Blocks the CCPMA, but not on the NPU-side of provisioned. Refer to NPU
the CCPMA. documentation to provision the
termination.
RED Red alarm A loss of frame condition lasting 2.5 +/- Receive path of this DS1 has been
0.5 seconds has occurred. interrupted or severely impaired.

Page 29-860 7/07 76.5500/29, Rev R

Table 7.3 DS1 Internal Termination Alarm Messages (Continued)

SENA Port Module and Redundant Port This alarm displays for each DS1 that The redundant port module was either
Module Not Available has faulted without receiving protection. already protecting a failed termination
Typically this occurs when an RPM is or it was unavailable.
protecting a group containing a PM with
an uncleared fault. A second faulted PM Go to DS1 Di-Group, Constituent, or
will not be protected and its associated Internal Termination (T1 DGR, CST, or
in-service DS1s will declare SENA TRMINT), page 29-897.
backing up if it is OOS or if it is inhibited
from protection, such as in PRTN=INH.
SENA Supporting MM24/RMM24 not This alarm is generated when the MM24 Associated MM24 or RMM24 is either
available or RMM24 associated with the reporting out-of-service (OOS) or it has an
DS1 TRMINT is not in-service, normal abnormal condition.
(IS-NR).
page 29-794.
SENA Supporting MIM96 Not Available This alarm is generated when the Associated MIM96 is either
MIM96 associated with the reporting out-of-service (OOS) or it has an
DS1 TRMINT is not in-service, normal abnormal condition.
(IS-NR).
page 29-815.
SENACC Supporting Entity Not Available The T1 termination to which the T1 There is a problem with the T1
from Cross-connected Side TRMINT is cross-connected has termination that the T1 TRMINT is
experienced a fault condition. cross-connected to.

T-BERH-P Path BER high threshold crossed The bit error rate for the path layer of Degradation of STS1-W/P path
the STS1-W/P has exceeded the transmission performance. Go to DS1
service threshold level (BERHP) set in Di-Group, Constituent, or Internal
the grade of service table. Termination (T1 DGR, CST, or
by this DS1. In SuperFrame (SF), yellow far end has gone into red alarm;
alarm is indicated by setting bit 2 to zero therefore, the far end of this DS1 is
on all 24 channels. In Extended transmitting a yellow alarm to indicate it
SuperFrame (ESF) this condition is has lost the signal. Go to DS1
signaled by a repeated pattern of eight Di-Group, Constituent, or Internal
zeros and eight ones. Termination (T1 DGR, CST, or
76.5500/29, Rev R 7/07 Page 29-861

DS2 Termination (T2) Alarm Messages

7.12 To verify the meaning of the alarm message(s) received for a T2 facility,
messages that can be generated for a T2 facility. The second column lists a
alarm.
Table 7.4 T2 Termination Alarm Messages

ACTLPBK Active Loopback - Command When that a far-end line loopback is A far-end line loopback has been
Requested FEND Line activated on a DS2 via the activated. Refer to Tellabs 5500/5500S
operate-loopback command, a Command Reference Manual,
RTRV-COND-T2 command posts the 76.5500/13, for RLS-LPBK-T2
appropriate ACTLPBK condition code command.
Then go to DS2 Termination (T2),
page 29-901.
ACTLPBK Active Loopback - Command When that a near-end line loopback is A near-end line loopback has been
Requested NEND Line activated on a DS2 constituent via the activated. Refer to Tellabs 5500/5500S
page 29-901.
ACTLPBK Active Loopback - Remotely When that a near-end remote line A near-end remote line loopback has
Requested NEND Line loopback is activated on a DS2 via the been activated. Refer to Tellabs
operate-loopback command, a 5500/5500S Command Reference
RTRV-COND-T2 command posts the Manual, 76.5500/13, for RLS-LPBK-T2
page 29-901.
AIS AIS alarm This DS2 has detected an all-ones The far-end is transmitting all ones to
condition on the receive path. indicate that it is no longer receiving a
signal.
Go to DS2 Termination (T2),

page 29-901.

page 29-901.

page 29-901.
Page 29-862 7/07 76.5500/29, Rev R

Table 7.4 T2 Termination Alarm Messages (Continued)

RED Red alarm A loss of frame condition lasting 2.5 Receive path of this DS2 has been
+/-.5 seconds has occurred. interrupted or severely impaired.

page 29-901.
SENA Supporting T3 not available This alarm is generated when the T3 Associated T3 is either OOS or it has an
associated with the reporting T2 is not abnormal condition causing it to be
IS-NR. IS-ANR.

page 29-901.
YEL Yellow alarm Yellow alarm signal has been detected The immediate upstream equipment
by this DS2. This alarm is declared detected a loss of signal or loss of frame
when the x bit is set to zero. Alarm and it responded by transmitting the
condition is lifted when the x bit is set yellow alarm signal.
back to 1.
page 29-901.
DS3 Di-Group Termination (T3 DGR) Alarm Messages

7.13 To verify the meaning of the alarm message(s) received for a T3 DGR
messages that can be generated for a T3 DGR facility. The second column lists a
alarm.
Table 7.5 T3 DGR Termination Alarm Messages

ACTLPBK Active Loopback - Command When a near-end internal loopback is A near-end internal loopback has been
Requested NEND Internal activated on a DS3 via the activated. Refer to Tellabs 5500/5500S
appropriate ACTLPBK condition code command. Then go to DS3 Di-Group
against the termination. Termination (T3 DGR), page 29-903.
ACTLPBK Active Loopback - Command When a near-end line loopback is A near-end line loopback has been
Requested NEND Line activated on a DS3 via the activated. Refer to Tellabs 5500/5500S
appropriate ACTLPBK condition code command. Then go to DS3 Di-Group
against the termination. Termination (T3 DGR), page 29-903.
AIC AIC alarm This DS3 port module has detected an Mismatch in framing configurations
application identification channel error. between near and far ends. They must
agree on M23 or C-bit parity. Go to DS3
Di-Group Termination (T3 DGR),
page 29-903.
AIS AIS alarm This DS3 has detected an all ones Far-end is setting the information bits to
condition on the receive path. alternating ones and 0s to indicate that it
is no longer receiving a signal. Go to
DS3 Di-Group Termination (T3 DGR),
page 29-903
76.5500/29, Rev R 7/07 Page 29-863


FEAIS Fault Escalation - transmitting AIS A failure in the DS3 payload is being There is a failure within the DS3
escalated to AIS. payload, and fault escalation is
provisioned for this T3. Also, the fault
received attribute is provisioned for the
cross-connected termination. Go to DS3
page 29-903.
FELOS Fault Escalation - transmitting LOS A failure in the DS3 payload is being There is a failure within the DS3
escalated to LOS. payload, and fault escalation is
provisioned for this T3. Also, the fault
received attribute is provisioned for the
cross-connected termination. Go to DS3
page 29-903.
inhibited (via command) setting ALM=INH, using ED-T3 or alarm monitoring function. Go to DS3
ENT-T3 commands. Di-Group Termination (T3 DGR),
page 29-903.
mode using the ED-T3 command. Then
go to DS3 Di-Group Termination (T3
DGR), page 29-903.
INHALM The termination has alarm Craft has inhibited alarm reporting on The alarming enabled (ALM) attribute for
annuciation inhibited that particular termination. This will that particular termination has been
force an abnormal termination to provisioned to inhibited (ALM=INH). This
transition to normal and replace all forces the system to Not Report any
alarms against that termination with this alarms (both existing and new) against
single INHALM condition. that termination. Refer to Tellabs
Manual, 76.5500/13, to allow alarms
using the ED-T3 command. Then go to
DS3 Di-Group Termination (T3 DGR),
page 29-903.
ISD Idle signal has been detected on The termination is detecting idle signal. This indicates a far-end idle signal. Go to
termination DS3 Di-Group Termination (T3 DGR),
page 29-903.
RED Red alarm A loss of signal or loss of frame Receive path from another node of this
condition lasting 2.5 +/-.5 seconds has DS3 has been interrupted or severely
occurred. impaired. Go to DS3 Di-Group
Termination (T3 DGR), page 29-903.
SENA Line Interface Module Not The LIM supporting this DS3 is not Either the supporting LIM has been
Available available. removed from its backplane slot or it has
failed. Go to DS3 Di-Group Termination
(T3 DGR), page 29-903.
Page 29-864 7/07 76.5500/29, Rev R


SENA Neither MM nor RMM is IS-NR The supporting MMs and RMMs are no The supporting MMs and RMMs are
longer IS-NR. OOS or ANR.
Go to DS3 Di-Group Termination (T3

DGR), page 29-903, to troubleshoot the
facility, or go to Section 6,
Troubleshooting the Port Shelves,
RMM.
SENA Neither supporting MIM is IS-NR The supporting MIMs are no longer The supporting MIMs are OOS or ANR.
IS-NR.
Go to DS3 Di-Group Termination (T3
DGR), page 29-903, to troubleshoot the
page 29-575, to troubleshoot the MIM.
SENA Port Module and Redundant Port This alarm displays for each DS3 that The redundant port module was either
Module Not Available has faulted without receiving protection. already protecting a failed termination or
Typically this occurs when an RPM is it was unavailable. Go to DS3 Di-Group
protecting a group containing a PM with Termination (T3 DGR), page 29-903.
an uncleared fault. A second faulted
PM will not be protected and its
associated
in-service DS3s will declare SENA
backing up if it is OOS or if it is inhibited
from protection, such as in PRTN=INH.
T-BERH Line BER high threshold crossed Bit error rate register for this DS3 has Line noise on the facility. Go to DS3
exceeded the high threshold set by the Di-Group Termination (T3 DGR),
grade of service table. Bit error rate is page 29-903.
based on either the number of bipolar
violations (BPVs), framing errors, or
parity errors.
T-BERL Line BER low threshold crossed Bit error rate register for this DS3 has Line noise on the facility. Go to DS3
exceeded the low threshold set by the Di-Group Termination (T3 DGR),
based on either the number of bipolar
violations (BPVs), framing errors, or
parity errors.
YEL Yellow alarm This alarm is declared when a detection The node or equipment upstream of the
of five consecutive X1 + X2 bits set to far end has gone into red alarm;
00 are received. These are repeated for therefore, the far end of this DS3 is
the duration of the failure condition. transmitting a yellow alarm to indicate it
This alarm is lifted when five has lost the signal. Go to DS3 Di-Group
consecutive X1 + X2 bits set to 11 are Termination (T3 DGR), page 29-903.
received. Processing of DS3 yellow
alarms is craft configurable.
76.5500/29, Rev R 7/07 Page 29-865

DS3 Constituent (T3 CST) Termination Alarm Messages

7.14 To verify the meaning of the alarm message(s) received for a T3 CST
messages that can be generated for a T3 CST facility. The second column lists a
alarm.
Table 7.6 T3 CST Termination Alarm Messages

AIC AIC alarm Application Identification Channel Incoming signal on a DS3 provisioned
alarm on a DS3 Constituent for C-Bit Parity is of type M13 or
termination. vice-versa.
Go to DS3 Constituent Termination (T3

CST), page 29-906.
AIS AIS alarm Alarm Indication Signal. The remote end is sending an all-1s
pattern for this DS3.

CST), page 29-906.
INHALM Alarm Monitoring has been inhibited Alarm Monitoring has been inhibited by TL1 commands were used to inhibit the
(via command) setting ALM=INH, using ED-EQPT or alarm monitoring function.
ENT-EQPT commands.
CST), page 29-906.

CST), page 29-906.
INHALM The termination has alarm Craft has inhibited Alarm reporting on The alarming enabled (ALM) attribute
annunciation inhibited that particular termination. This will for that particular termination has been
force an Abnormal termination to provisioned to inhibited (ALM=INH).
transition to Normal and replace all This forces the system to Not Report
alarms against that termination with any alarms (both existing and new)
this single INHALM condition. against that termination. Refer to
alarms using the ED-DS3 command.
Then go to DS3 Constituent Termination

(T3 CST), page 29-906.
ISD Idle signal has been detected on The DS3 signal is idle, or 1100 pattern The far-end is sending idle signal. A
termination is detected. 1100 pattern occurs over contiguous
M-frames.

CST), page 29-906.
RED Red alarm A red alarm has been detected The incoming signal is out of frame, or a
loss of signal is detected.

CST), page 29-906.
Page 29-866 7/07 76.5500/29, Rev R


SENA Neither supporting STS1 is The supporting STS1-W and STS1-P The supporting STS1-W and STS1-P or
IS-NR-ACT are no longer IS-NR. their supporting entities are OOS or
ANR.

CST), page 29-906.
SENA Supporting STS1 is not IS-NR The supporting STS-1 is no longer The supporting STS-1 or one of its
IS-NR. supporting entities is OOS or ANR.

CST), page 29-906.
YEL Yellow alarm A yellow alarm has been detected The remote end is sending a yellow
alarm.

CST), page 29-906.
DS3 Internal Termination (T3 TRMINT) Alarm Messages

7.15 To verify the meaning of the alarm message(s) received for a T3 TRMINT
messages that can be generated for a T3 TRMINT facility. The second column lists
a description of the alarm message. The third column gives a probable cause for
the alarm.
Table 7.7 T3 TRMINT Alarm Messages

ACTLPBK Active Loopback - Command When a near-end internal loopback is A near-end internal loopback is activated.
Requested NEND Internal activated on a T3 TRMINT via the Refer to Tellabs 5500/5500S Command
retrieve-condition TL1 command RLS-LPBK-T3 command. Then go to DS3
posts the appropriate ACTLPBK Internal Termination (DS3 TRMINT),
condition code against the page 29-913.
termination.
ACTLPBK Active Loopback - Command The user has attempted to configure a A loopback is already in place on the
Requested NEND CC near-end CC block loopback on a CCPMA.
CCPMA termination, but a loopback If necessary, refer to Tellabs 5500
already exists on this termination. Provisioning, 76.5500/23, to disable the
existing loopback and create a new one.
AIC AIC alarm Application Identification Channel Incoming signal on a DS3 provisioned for
alarm on a DS3 Constituent C-Bit Parity is of type M13 or vice-versa. Go
termination. to DS3 Internal Termination (DS3 TRMINT),
page 29-913.
AIS AIS alarm Alarm Indication Signal. The remote end is sending an all-1s pattern
for this DS3. Go to DS3 Internal
Termination (DS3 TRMINT), page 29-913.
INHALM Alarm Monitoring has been Alarm Monitoring has been inhibited TL1 commands were used to inhibit the
inhibited (via command) by setting ALM=INH, using ED-T3 or alarm monitoring function. Go to DS3
ENT-T3 commands. Internal Termination (DS3 TRMINT),
page 29-913.
76.5500/29, Rev R 7/07 Page 29-867

Table 7.7 T3 TRMINT Alarm Messages (Continued)

ISD Idle signal has been detected on The DS3 signal is idle, or 1100 The far-end is sending idle signal. A 1100
termination pattern is detected. pattern occurs over contiguous M-frames.
Go to DS3 Internal Termination (DS3
NOCCPORT Termination is not being used A termination has been provisioned The termination is incompletely provisioned.
within CC Blocks on the CCPMA, but not on the Refer to NPU documentation to provision
NPU-side of the CCPMA. the termination.
PTM Payload Type Mismatch The payload type is different from the The far end equipment may not be
expected payload type. configured to send a CFP payload over the
T3 TRMINT.
RADCOMM Remote Access Device A ping attempt from the shelf through There is a problem with the T3 TRMINT, or
Communication Lost the VCG to a Remote Access Device with the Remote Access Device.
fails.
TRMINT), page 29-913, to troubleshoot the
T3 TRMINT.
To troubleshoot the Remote Access Device,

America) or 1.630.798.7070 (outside North
America).
RED Red alarm A red alarm has been detected The incoming signal is out of frame, or a
loss of signal is detected. Go to DS3
Internal Termination (DS3 TRMINT),
page 29-913.
SENA Port Module and Redundant Port This alarm is displayed for each T3 Port module associated with this T3
Module Not Available termination for which neither the termination is either not present in the slot,
supporting port module or its has been set to inhibit protection by the
associated redundant port module is RPM, or has failed; and its associated
available. redundant port module has been removed,
has failed, or has been inhibited from
protecting the port module. Go to DS3
Internal Termination (DS3 TRMINT),
page 29-913.
SENA Supporting MM24/RMM24 not This alarm is generated when the Associated MM24 or RMM24 is either
available MM24 or RMM24 associated with the out-of-service (OOS) or it has an abnormal
reporting T3 TRMINT is not condition.
page 29-794.
SENA Supporting MIM96 Not Available This alarm is generated when the Associated MIM96 is either out-of-service
MIM96 associated with the reporting (OOS) or it has an abnormal condition.
T3 TRMINT is not in-service, normal
(IS-NR). Go to Mapping Interface Module (MIM),
page 29-815.
SENACC Supporting Entity Not Available The T3 termination to which the T3 There is a problem with the T3 termination
from Cross-connected Side TRMINT is cross-connected has that the T3 TRMINT is cross-connected to.
experienced a fault condition.
Page 29-868 7/07 76.5500/29, Rev R

Table 7.7 T3 TRMINT Alarm Messages (Continued)

YEL Yellow alarm A yellow alarm has been detected The remote end is sending a yellow alarm.
Electrical Carrier 1 (EC1) Termination Alarm Messages

7.16 To verify the meaning of the alarm message(s) received for an EC1 facility,
messages that can be generated for an EC1 facility. The second column lists a
alarm.
Table 7.8 EC1 Termination Alarm Messages

ACTLPBK Active Loopback - Command Anytime that a near-end internal A near-end internal loopback has been
Requested NEND Internal loopback is activated on a EC1 via the activated. Refer to Tellabs 5500/5500S
RTRV-COND-EC1 command will post 76.5500/13, for RLS-LPBK-EC1
the appropriate ACTLPBK condition command. Then go to Electrical Carrier
code against the termination. 1 Termination (EC1), page 29-915.
ACTLPBK Active Loopback - Command Anytime that a near-end line loopback is A near-end line loopback has been
Requested NEND Line activated on a EC1 via the activated. Refer to Tellabs 5500/5500S
RTRV-COND-EC1 command will post 76.5500/13, for RLS-LPBK-EC1
the appropriate ACTLPBK condition command. Then go to Electrical Carrier
code against the termination. 1 Termination (EC1), page 29-915.
inhibited (via command) setting ALM=INH, using ED-EC1 or alarm monitoring function. Refer to
ENT-EC1 commands. Tellabs 5500/5500S Command
alarms using the ED-EC1 command.
Then go to Electrical Carrier 1
Termination (EC1), page 29-915.
Monitoring Suspension Mode Suspension (PASUP) mode was set to the PASUP mode, causing the Inhibit
mode using the ED-EC1 command.
Then go to Electrical Carrier 1
LOF EC1 Loss of Frame detected A Loss of Frame condition lasting 2.5 Receive path from another node has
+/-.5 seconds has occurred. been blocked or severely impaired. Go
to Electrical Carrier 1 Termination (EC1),
page 29-915.
LOS EC1 Loss of Signal detected This EC1 is detecting all zeros. The signal transmitted from the far end
has been blocked or dropped. Go to
Electrical Carrier 1 Termination (EC1),
page 29-915.
76.5500/29, Rev R 7/07 Page 29-869

Table 7.8 EC1 Termination Alarm Messages (Continued)

RFI EC1 Remote Failure Indication The system generates this alarm when There is either a faulty facility or a faulty
detected bit 8 is set to 1 in byte V5 in five PM.
consecutive VT superframes. It indicates
an unspecified type of failure at the far Go to Electrical Carrier 1 Termination
end. (EC1), page 29-915, to troubleshoot the
page 29-575, to troubleshoot the PM.
SENA Line Interface Module not The LIM supporting this EC1 is not Either the supporting LIM has been
available available. removed from its backplane slot or it has
failed. Go to Electrical Carrier 1
SENA Port Module and Redundant Port This alarm is displayed for each EC1 Port module associated with this EC1
Module not available termination for which neither the termination is either not present in the
supporting port module or its associated slot, has been set to inhibit protection by
redundant port module is available. the RPM, or has failed; and its
associated redundant port module has
been removed, has failed, or has been
inhibited from protecting the port
module. Go to Electrical Carrier 1
SSM Change at the received An autonomous message that is The incoming EC1 synchronization clock
Synchronization Status Message generated against the EC1 indicating quality level has changed. Go to
detected that a change has been detected in the Electrical Carrier 1 Termination (EC1),
received EC1 synchronous status page 29-915.
message.
T-BERH Line BER high threshold crossed Bit error rate register for this EC1 has Line noise on the facility. Go to Electrical
exceeded the high threshold set by the Carrier 1 Termination (EC1),
grade of service table. Bit error rate is page 29-915
based on the number of BPVs
(bipolar violations).
T-BEHRL Line BER low threshold crossed Bit error rate register for this EC1 has Line noise on the facility. Go to Electrical
exceeded the low threshold set by the Carrier 1 Termination (EC1),
based on the number of BPVs
(bipolar violations).
Page 29-870 7/07 76.5500/29, Rev R

STS-1 Termination Alarm Messages

7.17 To verify the meaning of the alarm message(s) received for an STS-1
facility provisioned for either APS or UPSR, use the following table. The first
column of the table lists the possible alarm messages that can be generated for an
STS-1 facility. The second column lists a description of the alarm message. The
third column gives a probable cause for the alarm.
Table 7.9 STS-1 Termination Alarm Messages

Requested NEND Internal activated on an STS-1 via the activated. Refer to Tellabs 5500/5500S
retrieve-condition TL1 command posts 76.5500/13, for RLS-LPBK-STS1
the appropriate ACTLPBK condition command. Then go to STS-1
code against the termination. Termination, page 29-919.
Requested NEND Line activated on an STS-1 via the Refer to Tellabs 5500/5500S Command
retrieve-condition TL1 command posts RLS-LPBK-STS1 command. Then go to
the appropriate ACTLPBK condition STS-1 Termination, page 29-919.
code against the termination.
AIS STS1 Path AIS detected The line terminating equipment (LTE) All ones signal is being received by this
is sending STS Path AIS to alert this STS-1 from the upstream equipment.
STS-1 that a failure has been There is either a loss of signal, loss of
detected. This causes maintenance frame, facility failure, or equipment
actions to start, such as propagating failure upstream. Go to STS-1
the AIS. Termination, page 29-919.
(via command) setting ALM=INH, using ED-STS1 or alarm monitoring function. Refer to
ENT-STS1 commands. Tellabs 5500/5500S Command
alarms using the ED-STS1 command.
Then go to STS-1 Termination,
page 29-919.
Manual, 76.5500/13, to disable
PASUSP mode using the ED-STS1
command. Then go to STS-1
Termination, page 29-919.
FEAIS Fault Escalation - transmitting AIS A failure in the STS-1 payload is being There is a failure within the STS-1
escalated to AIS. payload and fault escalation is
provisioned for this STS-1. Also, the
fault received attribute is provisioned for
the cross-connected termination. Go to
STS-1 Termination, page 29-919.
LOM Loss of Multiframe on VCG The STS-1, which is a part of a VCG, The quality of the signal received from
has experienced a loss of multiframe. the far end is poor. Go to STS-1
76.5500/29, Rev R 7/07 Page 29-871

Table 7.9 STS-1 Termination Alarm Messages (Continued)

LOMF STS1 Loss of Multiframe alignment This termination has detected two Either the quality of the signal received
detected consecutive H4 values that do not from the far end is poor, or the STS1E
agree with any part of the multiframe card has failed. Go to STS-1
sequence, and it has declared a loss of Termination, page 29-919.
multiframe (LOMF) defect.
LOP STS1 Loss of Pointer detected This termination has failed to detect a Either the facility from the far end is
valid STS payload pointer from the experiencing problems or the PME has
pointer overhead within eight failed. Go to STS-1 Termination,
consecutive frames, or it has detected page 29-919.
eight consecutive new data frames
(NDFs).
MND LCAS member not Deskewable In a VCG with multiple STS1 or VT1 This particular STS1/VT1 is
members, one of the members is experiencing a longer end-to-end delay,
experiencing excessive differential relative to the other STS1/VT1 LCAS
delay relative to the other members in members. This delay can possibly be
the VCG. Therefore, the STS1 or VT1 caused by the fact that the physical path
is disabled from the VCG (in other of the STS1/VT1 is longer or shorter,
words, it is not allowed to participate in relative to the other STS1/VT1 LCAS
the VCG). members.
This alarm only occurs in a VCG when Go to STS-1 Termination, page 29-919.
LCAS is enabled.
MISCON Crossconnection is inconsistent with The PPG is involved in a Either a cross-connection has been
node type of protection group cross-connection and configured with established on a PPG Pass-through
a node type of Pass-through. This node, or the node type has been edited
condition indicates a mismatch of to Pass-through on a cross-connected
configuration (MISCON) for the entity. PPG entity. Go to STS-1 Termination,
This alarm is posted only against the page 29-919.
STS1-Working.
PDIP STS1 Path Payload Defect The STS- C2 byte contains a payload Another element within the network has
Indication detected defect indication (values E1 to FC). detected a failure within the STS-1
payload. Go to STS-1 Termination,
page 29-919.
PLM STS1 Payload Label Mismatch The STS-1 overhead byte C2 was There is a non-zero value in the C2
detected detected as a Payload Label overhead byte that does not match what
Mismatch. is expected. Go to STS-1 Termination,
page 29-919.
PROTNA Forced Switch to Protection This alarm appears after entering a An OPR-PROTNSW-STS1 command
command to force traffic to Protection. was used to force a switch from the
The Protection side is forced to carry STS1-W to the STS1-P path. Go to step
traffic without redundancy on the 1, page 29-919.
Working side. A PROTNA message
also appears from the OCN.
PROTNA Forced Switch to Working A protection switch to the STS1-W An OPR-PROTNSW-STS1 command
(working) has occurred. was used to force a switch from the
STS1-P to the STS1-W path. Go to step
1, page 29-919.
PROTNA Lockout of Protection If the STS1-P (protection) was active, An OPR-PROTNSW-STS1 command
a protection switch to the STS1-W was used to lockout the STS1-P path.
(working) has occurred. Go to STS-1 Termination, page 29-919.
PROTNA Lockout of Working If the STS1-W (working) was active, a An OPR-PROTNSW-STS1 command
protection switch to the STS1-P was used to lockout the STS1-W path.
(protect) has occurred. Go to STS-1 Termination, page 29-919.
Page 29-872 7/07 76.5500/29, Rev R


PROTNA STS1-P is ANR This is a PROTNA condition posted The Path STS1-Protect (PSTS1-P) is
against the path STS1-Protect abnormal (ANR). Go to STS-1
termination. Termination, page 29-919.
PROTNA STS1-P is OOS This is a PROTNA condition posted The Path STS1-Protect (STS1-P) Is
against the path STS1-Protect out-of-service (OOS). Go to STS-1
PROTNA STS1-W is ANR This is a PROTNA condition posted The Path STS1-Working (PSTS1-W) is
against the path STS1-Working abnormal (ANR). Go to STS-1
PROTNA STS1-W is OOS This is a PROTNA condition posted The Path STS1-Working (PSTS1-W) is
against the path STS1-Working out-of-service (OOS). Go to STS-1
RFI STS1 Remote Failure Indication This termination has detected an STS Either the quality of the signal received
detected path RDI defect, which is indicated by from the far end is poor, or there is a
setting bit 5 of byte G1 to 1 for ten faulty PM.
consecutive frames.
Go to STS-1 Termination, page 29-919,
to troubleshoot the facility, or go to
Section 6, Troubleshooting the Port
Shelves, page 29-575, to troubleshoot
the PM.
SENA Neither supporting entity (OC) is The supporting OCs are no longer The supporting OCs are OOS, ANR, or
IS-NR-ACT IS-NR-ACT. STBY. Go to STS-1 Termination,
page 29-919.
SENA Neither supporting MIM is IS-NR The supporting MIMs are no longer The supporting MIMs are OOS or ANR.
IS-NR.
Go to STS-1 Termination, page 29-919,
the MIM.
SENA Supporting EC1 not available This alarm is generated when the EC1 Associated EC1 is either OOS or it has
associated with the reporting STS-1 is an abnormal condition causing it to be
not IS-NR. IS-ANR. Go to Electrical Carrier 1
SENA Supporting entity (MM<x>) not Alarm is generated against an The supporting MMs and RMMs are
available (where <x> = 3 or 24) assigned STS-1 when the PM OOS or ANR.
associated with the reporting STS-1 is
not IS-NR. Go to STS-1 Termination, page 29-919,
the MMs or RMMs.
SENA Supporting entity (OC) is not OCN-W and OCN-P are no longer The OCNs or the supporting equipment
IS-NR-ACT IS-NR. is/are OOS or ANR. Go to STS-1
SENACC Supporting Entity Not Available from The termination to which the STS-1 There is a problem with the termination
Cross-connected Side TRMINT is cross-connected has that the STS-1 TRMINT is
experienced a fault condition. cross-connected to. Go to STS-1
76.5500/29, Rev R 7/07 Page 29-873


SQM Sequence Mismatch Sequence Mismatch (SQM) The This alarm is only reported when LCAS
received sequence number does not is disabled.
match the expected sequence There is a fault on the STS-1 termination
number. Failure occurs when the SQM or VCG.
defect is present for the alarm Go to STS-1 Termination, page 29-919,
integration period. or Virtual Concatenation Group (VCG),
page 29-1002.
T-BERH-P Path BER high threshold crossed The bit error rate for the path layer of Degradation of STS1-W/P path
the STS1-W/P has exceeded the transmission performance. Go to STS-1
service threshold level (BERHP) set in Termination, page 29-919.
the grade of service table.
T-BERL-P Path BER low threshold crossed The bit error rate for the path layer of Degradation of STS1-W/P path
the STS1-W/P has exceeded the transmission performance. Go to STS-1
maintenance threshold level (BERLP) Termination, page 29-919.
set in the grade of service table.
UNEQ STS1 Path UNEQ detected STS-1 overhead byte C2 detected an A zero value in the C2 overhead byte.
Unequipped (UEQ) condition. Go to STS-1 Termination, page 29-919.
Virtual Tributary 1 Termination (VT1) Alarm Messages

7.18 To verify the meaning of the alarm message(s) received for a VT1 facility
provisioned for either APS or UPSR, use the following table. The first column of the
table lists the possible alarm messages that can be generated for a VT1 facility.
The second column lists a description of the alarm message. The third column
gives a probable cause for the alarm.
Table 7.10 VT1 Termination Alarm Messages

Condition Alarm Message for both Probable Cause(s)—For
Type APS and UPSR Description Reference Only
Requested NEND Internal activated on a VT1 via the activated. Refer to Tellabs 5500/5500S
retrieve-condition TL1 command posts 76.5500/13, for RLS-LPBK-VT1
the appropriate ACTLPBK condition command. Then go to Virtual Tributary 1
code against the termination. Termination (VT1), page 29-925.
Requested NEND Line activated on a VT1 via the Refer to Tellabs 5500/5500S Command
retrieve-condition TL1 command posts RLS-LPBK-VT1 command. Then go to
the appropriate ACTLPBK condition Virtual Tributary 1 Termination (VT1),
code against the termination. page 29-925.
AIS VT1 Path AIS detected This VT1 has detected an all ones code All ones signal is being received by this
lasting 2.5 +/-0.5 seconds with no VT1 from the upstream equipment.
framing. There is either a loss of signal, loss of
frame, facility failure, or equipment
failure upstream. Go to Virtual Tributary
1 Termination (VT1), page 29-925.
Page 29-874 7/07 76.5500/29, Rev R

Table 7.10 VT1 Termination Alarm Messages (Continued)

FEAIS Fault Escalation - transmitting AIS A failure within the VT1 payload is being There is a failure within the VT1 payload
escalated to AIS. and fault escalation is provisioned for
this VT1. Also, the fault received attribute
is provisioned for the cross-connected
termination. Go to Virtual Tributary 1
Termination (VT1), page 29-925.
inhibited (via command) setting ALM=INH, using ED-VT1 or alarm monitoring function. Refer to
ENT-VT1 commands. Tellabs 5500/5500S Command
alarms using the ED-VT1 command.
Then go to Virtual Tributary 1
mode using the ED-VT1 command. Then
go to Virtual Tributary 1 Termination
(VT1), page 29-925.
LOM Loss of Multiframe on VCG The VT-1, which is a part of a VCG, has The quality of the signal received from
experienced a loss of multiframe. the far end is poor. Go to Virtual
Tributary 1 Termination (VT1),
page 29-925.
LOP VT1 Loss of Pointer detected This termination has failed to detect a Either the facility from the far end is
valid VT superframe pointer from the experiencing problems or the port
pointer overhead within eight module has failed. Go to Virtual Tributary
consecutive frames, or it has detected 1 Termination (VT1), page 29-925.
eight consecutive new data frames
(NDFs).
MISCON Crossconnection is inconsistent The VPG is involved in a Either a cross-connection has been
with node type of protection group cross-connection and configured with a established on a VPG Pass-Through
node type of Pass-Through. This node, or the node type has been edited
condition indicates a mismatch of to Pass-Through on a cross-connected
configuration (MISCON) for the entity. VPG entity. Go to Virtual Tributary 1
This alarm is posted only against the Termination (VT1), page 29-925.
VT1-Working.
MND LCAS member not Deskewable In a VCG with multiple STS1 or VT1 This particular STS1/VT1 is experiencing
members, one of the members is a longer end-to-end delay, relative to the
experiencing excessive differential delay other STS1/VT1 LCAS members. This
relative to the other members in the delay can possibly be caused by the fact
VCG. Therefore, the STS1 or VT1 is that the physical path of the STS1/VT1 is
disabled from the VCG (in other words, longer or shorter, relative to the other
it is not allowed to participate in the STS1/VT1 LCAS members.
VCG).
Go to Virtual Tributary 1 Termination
This alarm only occurs in a VCG when (VT1), page 29-925.
LCAS is enabled.
PAINTGRT TVT parity error detected on An internal path integrity error has been A connected network complex entity has
network copy x, where x equals A detected on NC-A or NC-B. failed. Go to Virtual Tributary 1
or B Termination (VT1), page 29-925.
76.5500/29, Rev R 7/07 Page 29-875


PDIV VT1 Path Payload Defect The port module has detected a Path Check the network equipment which is
Indication detected Payload Defect Indicator signal on the attached to the associated port module.
VT1. Another element within the network has
detected a failure within the VT1
payload. Go to Virtual Tributary 1
PLM VT1 Payload Label Mismatch The VT1 overhead byte V5 was There is a non-zero value in the V5
detected detected as a Payload Label Mismatch. overhead byte does not match what is
expected. Go to Virtual Tributary 1
PLM VT1 Path Signal Label Mismatch The port module has detected a path The received path signal label does not
detected signal label mismatch on the VT-1. match what it is expected. Go to Virtual
Tributary 1 Termination (VT1),
page 29-925.
PROTNA Forced Switch to Protection This alarm appears after entering a An OPR-PROTNSW-VT1 command was
command to force traffic to Protection. used to force a switch from the VT1-W to
The Protection side is forced to carry the VT1-P path. Go to Virtual Tributary 1
traffic without redundancy on the Termination (VT1), page 29-925.
Working side. A PROTNA message also
appears from the OCN.
PROTNA Forced Switch to Working This alarm appears after entering a An OPR-PROTNSW-VT1 command was
command to force traffic to Working. used to force a switch from the VT1-P to
The Working side is forced to carry the VT1-W path. Go to Virtual Tributary 1
traffic without redundancy on the Termination (VT1), page 29-925.
Protection side. A PROTNA message
also appears from the OCN.
PROTNA Lockout of Protection If the VT1-P (protection) was active, a An OPR-PROTNSW-VT1 command was
protection switch to the VT1-W used to lockout the VT1-P path. Go to
(Working) may have occurred. Virtual Tributary 1 Termination (VT1),
page 29-925.
PROTNA Lockout of Working If the VT1-W (working) was active, a An OPR-PROTNSW-VT1 command was
protection switch to the VT1-P used to lockout the VT1-W path. Go to
(Protection) may have occurred. Virtual Tributary 1 Termination (VT1),
page 29-925.
PROTNA VT1-P is ANR This is a PROTNA condition posted The Path VT1-Protect (VT1-P) is
against the Path VT1-Protect Abnormal (ANR). Go to Virtual Tributary
termination. 1 Termination (VT1), page 29-925.
PROTNA VT1-P is OOS This is a PROTNA condition posted The Path VT1-Protect (VT1-P) Is
against the Path VT1-Protect out-of-service (OOS). Go to Virtual
termination. Tributary 1 Termination (VT1),
page 29-925.
PROTNA VT1-W is ANR This is a PROTNA condition posted The Path VT1-Working (VT1-W) is
against the Path VT1-Working Abnormal (ANR). Go to Virtual Tributary
termination. 1 Termination (VT1), page 29-925.
PROTNA VT1-W is OOS This is a PROTNA condition posted The Path VT1-Working (VT1-W) Is
against the Path VT1-Working out-of-service (OOS). Go to Virtual
termination. Tributary 1 Termination (VT1),
page 29-925.
RFI VT1 Remote Failure Indication Alarm indicates an unknown type of Either the quality of the signal received
detected far-end failure. It is indicated by setting from the far end is poor, or there is a
bit 8 of byte V5 to 1 for five contiguous faulty port module. Go to Virtual
VT superframes. Tributary 1 Termination (VT1),
page 29-925.
Page 29-876 7/07 76.5500/29, Rev R


SENACC Supporting Entity Not Available The termination to which the VT1 There is a problem with the termination
from Cross-connected Side TRMINT is cross-connected has that the VT1 TRMINT is cross-connected
experienced a fault condition. to.
Go to Virtual Tributary 1 Termination

(VT1), page 29-925.
SENA Supporting MM24/RMM24 Not This alarm is generated when the MM24 Associated MM24 or RMM24 is either
Available or RMM24 associated with the reporting out-of-service (OOS) or it has an
VT1 is not in-service, normal (IS-NR). abnormal condition.

page 29-794.
SENA Supporting STS1 not available The supporting STS-1 or both The supporting STS-1(s) is/are OOS or
supporting STS1-W and STS1-P are not ANR. Go to Virtual Tributary 1
IS-NR. Termination (VT1), page 29-925.
SQM Sequence Mismatch The received sequence number does This alarm is only reported when LCAS
not match the expected sequence is disabled.
number. Failure occurs when the SQM There is a fault on the VT-1 termination
defect is present for the alarm or VCG.
integration period. Go to Virtual Tributary 1 Termination
(VT1), page 29-925, or Virtual
Concatenation Group (VCG),
page 29-1002.
T-BERH-V Path BER high threshold crossed The Bit Error Rate for the path layer of Degradation of VT1-W/P path
the VT1-W/P has exceeded the service transmission performance. Go to Virtual
threshold level (BERHV) set in the Tributary 1 Termination (VT1),
Grade of Service table. page 29-925.
T-BERL-V Path BER low threshold crossed The Bit Error Rate for the path layer of Degradation of VT1-W/P path
the VT1W/P has exceeded the transmission performance. Go to Virtual
maintenance threshold level (BERLV) Tributary 1 Termination (VT1),
set in the Grade of Service table. page 29-925.
UNEQ VT1 Path UNEQ detected VT1 overhead byte C2 detected an A zero value in the C2 overhead byte.
Unequipped (UEQ) condition. Go to Virtual Tributary 1 Termination
(VT1), page 29-925.
76.5500/29, Rev R 7/07 Page 29-877

Optical Carrier 3, 12, or 48 (OC3, OC12, or OC48) Termination Alarm Messages

7.19 To verify the meaning of the alarm message(s) received for an OC3,
OC12, or OC48 facility, use the following table. The first column of the table lists
the possible alarm messages that can be generated for an OCn facility. The
Table 7.11 OCn Termination Alarm Messages

ACTLPBK Facility Loopback is applied A “facility loopback message” has been A loopback has been applied to this
received. termination. Refer to Tellabs 5500/5500S
76.5500/13, for RLS-LPBK-OCn
command. Then go to one of the following:
• Optical Carrier 3-Working
Termination (OC3-W), page 29-931
AIS Line Alarm Indication Signal Line terminating equipment upstream Loss of signal, loss of frame, an open
has trouble and is sending an all-ones circuit, or failure of an OPMn port module.
signal (OCN AIS) to alert downstream Go to one of the following:
equipment that a failure has occurred. • Optical Carrier 3-Working
• Troubleshooting the Port Shelves,
page 29-575, to troubleshoot the
OPM.
APSB Automatic Protection Switching Inconsistent or invalid Automatic Inconsistent or invalid Automatic
Byte Failure Protection Switching (APS) bytes are Protection Switching (APS) bytes are
being received on STS #1 of the being received. Go to one of the following:
protection OCN. This occurs only in • Optical Carrier 3-Working
FPGs configured for bidirectional Termination (OC3-W), page 29-931
operation.
APSB-FE Far End Automatic Protection Signal failure code on channel 0000 is Protection channel is bad. Go to one of the
Switching Byte Failure being received. The system has following:
automatically switched to the working • Optical Carrier 3-Working
channel and has declared a Protection Termination (OC3-W), page 29-931
Switching Byte Failure (PSBF) for the
bidirectional FPG in question.
Page 29-878 7/07 76.5500/29, Rev R

Table 7.11 OCn Termination Alarm Messages (Continued)

APSCM Channel Mismatch Failure One end of a bidirectional linearly Bits 1 to 4 of the received K2 byte do not
protected system has requested a equal bits 5 to 8 of the transmitted K1 byte
protection switch, but the other end has for at least 50 milliseconds. Go to one of
failed to comply. the following:
APSMM Mode Mismatch Failure This alarm occurs when the FPG is in Verify the switching type configured on the
linear APS mode. The near end and far FPG. Go to one of the following:
end are configured for different types of • Optical Carrier 3-Working
switching (unidirectional or Termination (OC3-W), page 29-931
bidirectional).
INHALM The termination has alarm Craft has inhibited Alarm reporting on The alarming enabled (ALM) attribute for
annunciation inhibited. that particular termination. This will that particular termination has been
force an Abnormal termination to provisioned to inhibited (ALM=INH). This
transition to Normal and replace all forces the system to Not Report any
alarms against that termination with this alarms (both existing and new) against
single INHALM condition. that termination. Refer to Tellabs
Manual, 76.5500/13, to allow alarms using
the ED-OCn command. Go to one of the
following:
LOF Loss of Frame A Loss of Frame condition lasting 2.5 Receive path from another node has been
+/-.5 seconds has occurred. blocked or severely impaired. Go to one of
the following:
LOS Loss of Signal An all-zeros pattern is being received, Either a loss of frame, out of frame, an
indicating a loss-of-signal condition open circuit, or failure of a port module has
(LOS). resulted in a loss of the receive path. Go to
one of the following:
76.5500/29, Rev R 7/07 Page 29-879


PROTNA Forced Switch to Protection The “protection not available” failure Protection state of the supporting FPG is
exists against the working OCN of an Forced Switch of working to protection.
FPG due to a forced line protection Refer to Tellabs 5500/5500S Command
switch from the working OCN to the Reference Manual, 76.5500/13, for
protection OCN. RLS-PROTNSW-OCn command. Then go
to one of the following:
PROTNA Forced Switch to Working The “protection not available” failure Protection state of the supporting FPG is
exists against the protection OCN of an Forced Switch of protection to working.
FPG due to a forced line protection Refer to Tellabs 5500/5500S Command
switch from the protection OCN to the Reference Manual, 76.5500/13, for
working OCN. RLS-PROTNSW-OCn command. Then go
PROTNA Lockout of Protection A “protection not available” failure has Protection state of the supporting FPG is
occurred because the protection OCN set to “Lockout of Protection.” Refer to
has been configured to lockout Tellabs 5500/5500S Command Reference
protection switching for the FPG in Manual, 76.5500/13, for
question. RLS-PROTNSW-OCn command. Then go
PRONTA OCN-P is ANR A “protection not available” failure has The state of the protection OCN is ANR.
occurred because protection OCN for Go to one of the following:
FPG in question is ANR. • Optical Carrier 3-Working
PROTNA OCN-P is OOS A “protection not available” failure has The state of the protection OCN is OOS.
occurred because protection OCN for Go to one of the following:
FPG in question is OOS. • Optical Carrier 3-Working
Page 29-880 7/07 76.5500/29, Rev R


PRONTA OCN-W is ANR A “protection not available” failure has The state of the associated working OCN
occurred. The protection OCN for the is ANR. Go to one of the following:
FPG in question is associated to a • Optical Carrier 3-Working
working OCN that is ANR. Termination (OC3-W), page 29-931
PROTNA OCN-W is OOS A “protection not available” failure has The state of the associated working OCN
occurred. The protection OCN for the is OOS. Go to one of the following:
FPG in question is associated to a • Optical Carrier 3-Working
working OCN that is OOS. Termination (OC3-W), page 29-931
PROTNA OPM-P is ANR A “protection not available” failure The state of the associated protection
exists against the protection OCN for OPMN is ANR. Go to one of the following:
the FPG in question because the • Optical Carrier 3-Working
protection OPMN is ANR. Termination (OC3-W), page 29-931
PROTNA OPM-P is OOS A “protection not available” failure The state of the associated working
exists against the protection OCN for OPMN is OOS. Go to one of the following:
protection OPMN is OOS. Termination (OC3-W), page 29-931
PROTNA OPM-W is ANR A “protection not available” failure The state of the associated protection
exists against the protection OCN for OPMN is ANR. Go to one of the following:
protection OPMN is ANR. Termination (OC3-W), page 29-931
PROTNA OPM-W is OOS A “protection not available” failure The state of the associated working
exists against the protection OCN for OPMN is OOS. Go to one of the following:
protection OPMN is OOS. Termination (OC3-W), page 29-931
76.5500/29, Rev R 7/07 Page 29-881


PROTNA Signal Degrade on Protection Degraded signal on the protect OC. Transmission problem on fiber tracing
back to upstream NE. Go to one of the
following:
PROTNA Signal Degrade on Working Degraded signal on the protect OC Transmission problem on fiber tracing
following:
PROTNA Signal Failure on Protection Loss of signal on the working OC. Transmission problem on fiber tracing
following:
PROTNA Signal Failure on Working Loss of signal on the working OC. Transmission problem on fiber tracing
following:
RFI Line Remote Failure Indication An OCN line RDI defect has persisted Either there are facility problems at the far
for more than the predefined system end, or there is a faulty OPMN module. Go
alarm integration period. to one of the following:

• Troubleshooting the Port Shelves,
OPM.
Page 29-882 7/07 76.5500/29, Rev R


SENA Supporting Entity (OPMN) Not Alarm is generated against an assigned The OPMN is either OOS or it has an
Available OCN when the OPMN associated with abnormal condition (ANR). Go to one of
the reporting OCN is not IS-NR. the following:
SSM Change at the received An autonomous message that is The incoming OCx synchronization clock
Synchronization Status Message generated against the OCx indicating quality level has changed. Go to one of the
detected that a change has been detected in the following:
received OCx synchronous status • Optical Carrier 3-Working
message. Termination (OC3-W), page 29-931
T-BERH Line BER high threshold crossed Bit error rate register for this OCn has Line noise on the facility. Go to one of the
exceeded the high threshold set by the following:
Grade of Service table. Bit error rate is • Optical Carrier 3-Working
based on the number of BPVs (Bipolar Termination (OC3-W), page 29-931
Violations).
T-BERL Line BER low threshold crossed Bit error rate register for this OCn has Line noise on the facility. Go to one of the
exceeded the low threshold set by following:
Grade of Service table. Bit error rate is • Optical Carrier 3-Working
based on the number of BPVs (Bipolar Termination (OC3-W), page 29-931
Violations).
76.5500/29, Rev R 7/07 Page 29-883

STS3C Termination Alarm Messages

7.20 To verify the meaning of the alarm message(s) received for an STS3C
facility provisioned for either APS or UPSR, use the following table. The first
column of the table lists the possible alarm messages that can be generated for an
STS3C facility. The second column lists a description of the alarm message. The
third column gives a probable cause for the alarm.
Table 7.12 STS3C Termination Alarm Messages

Type Alarm Messages Description Reference Only
ACTLPBK Active Loopback - Command When a near-end internal loopback is A near-end internal loopback is activated.
Requested NEND Internal activated on an STS3C via the Refer to Tellabs 5500/5500S Command
retrieve-condition TL1 command RLS-PROTNSW-STS3C command. Then
posts the appropriate ACTLPBK go to STS3C Termination, page 29-958.
condition code against the
termination.
Requested NEND Line activated on an STS3C via the Refer to Tellabs 5500/5500S Command
retrieve-condition TL1 command RLS-PROTNSW-STS3C command. Then
posts the appropriate ACTLPBK go to STS3C Termination, page 29-958.
condition code against the
termination.
AIS STS3C Path AIS detected Alarm indication signal. The remote end is sending an all ones
pattern for this STS3C. Go to STS3C
INHALM Alarm Monitoring has been Alarm Monitoring has been inhibited TL1 commands were used to inhibit the
inhibited (via command) by setting ALM=INH, using alarm monitoring function. Refer to Tellabs
ED-STS3C or ENT-STS3C 5500/5500S Command Reference
commands. Manual, 76.5500/13, to allow alarms using
the ED-STS3C command. Then go to
STS3C Termination, page 29-958.
Suspension mode Suspension (PASUP) mode was set the PASUP mode, causing the Inhibit
to TRIG/DLY by using a TL1 Alarm (INHALM) condition posted against
command. the termination. Go to STS3C
LOP STS3C Loss of Pointer detected An LOP alarm has been detected. The pattern pointer has been lost in the
transmission signal of this STS3C. Go to
MISCON Crossconnection is inconsistent Alarm occurs if a protection group Occurs on optical shelves configured for
with node type of protection group (PPG, CPG, or VPG) has been edited UPSR mode.
for PASSTHRU mode, and a cross Verify the configuration of the protection
connection to it is already established. group. Go to STS3C Termination,
page 29-958.
PLM STS3C Payload Label Mismatch STS3C overhead byte C2 detected as A non-zero value in the C2 overhead byte
detected a Payload Label Mismatch. does not match what is expected. Go to
Page 29-884 7/07 76.5500/29, Rev R

Table 7.12 STS3C Termination Alarm Messages (Continued)

PROTNA Forced Switch to Protection This alarm appears after entering a An OPR-PROTNSW-STS3C command
command to force traffic to Protection. was used to force a switch from the
The Protection side is forced to carry STS3C-W to the STS3C-P path. Refer to
traffic without redundancy on the Tellabs 5500/5500S Command Reference
Working side. A PROTNA message Manual, 76.5500/13, for
also appears from the OCN. RLS-PROTNSW-STS3C command. Then
go to STS3C Termination, page 29-958.
PROTNA Forced Switch to Working This alarm appears after entering a An OPR-PROTNSW-STS3C command
command to force traffic to Working. was used to force a switch from the
The Working side is forced to carry STS3C-P to the STS3C-W path. Refer to
traffic without redundancy on the Tellabs 5500/5500S Command Reference
Protection side. A PROTNA message Manual, 76.5500/13, for
also appears from the OCN. RLS-PROTNSW-STS3C command. Then
PROTNA Lockout of Protection If the STS3C-P (protection) was An OPR-PROTNSW-STS3C command

active, a protection switch to the was used to lockout the STS3C-P path.
STS3C-W (working) has occurred. Refer to Tellabs 5500/5500S Command
Reference Manual, 76.5500/13, for
RLS-PROTNSW-STS3C command. Then
PROTNA Lockout of Working If the STS3C-W (working) was active, An OPR-PROTNSW-STS3C command
a protection switch to the STS3C-P was used to lockout the STS3C-W path.
(protect) has occurred. Refer to Tellabs 5500/5500S Command
Reference Manual, 76.5500/13, for
RLS-PROTNSW-STS3C command. Then
PROTNA STS3C-P is ANR This is a PROTNA condition posted The Path STS3C-Protect (STS3C-P) is
against the Path STS3C-Protect Abnormal (ANR). Go to STS3C
PROTNA STS3C-W is ANR This is a PROTNA condition posted The Path STS3C-Working (PTS3C-W) is
against the Path STS3C-Working abnormal (ANR). Go to STS3C
PROTNA STS3C-P is OOS This is a PROTNA condition posted The Path STS3C-Protect (STS3C-P) Is
against the Path STS3C-Protect out-of-service (OOS). Go to STS3C
PROTNA STS3C-W is OOS This is a PROTNA condition posted The Path STS3C-Working (STS3C-W) is
against the Path STS3C-Working out-of-service (OOS). Go to STS3C
RFI STS3C Remote Failure Indication The STS Path RDI Indicator bit in the The received signal from the far end has a
detected G1 path overhead byte is set if the Remote Defect Indication (RDI-P) bit set in
system detects a ‘1’ in bit 5 of byte G1 the STS Path Overhead. Go to STS3C
for five contiguous frames. This RDI Termination, page 29-958.
defect causes a Remote Failure
Indication (RFI) alarm to be declared
against that STS3C termination.
SENA Neither supporting MIM is IS-NR The supporting MIMs are no longer The supporting MIM is OOS or ANR.
IS-NR.
Go to STS3C Termination, page 29-958,
to troubleshoot the facility, or go to Section
6, Troubleshooting the Port Shelves,
page 29-575, to troubleshoot the MIM.
76.5500/29, Rev R 7/07 Page 29-885

Table 7.12 STS3C Termination Alarm Messages (Continued)

SENA Neither supporting OCN is The supporting OCN-W and OCN-P The supporting OCN-W and OCN-P or
IS-NR-ACT are no longer IS-NR. their supporting equipment is OOS or
ANR. Go to STS3C Termination,
page 29-958.
SENA Supporting MM or RMM is not The supporting MM or RMM is no The supporting MM or RMM is OOS or
IS-NR longer IS-NR. ANR.
Go to STS3C Termination, page 29-958,

to troubleshoot the facility, or go to Section
6, Troubleshooting the Port Shelves,
RMM.
SENA Supporting OCN is not IS-NR-ACT The supporting OCN is no longer The supporting OCN or its supporting
IS-NR. equipment is OOS or ANR. Go to STS3C
T-BERH Line BER high threshold crossed The bit error rate for the line layer of Degradation of STS3C-W/P path
the STS3C-W/P has exceeded the transmission performance. Go to STS3C
service threshold level (BERHP) set in Termination, page 29-958.
the grade of service table.
T-BERL Line BER low threshold crossed The Bit Error Rate for the line layer of Degradation of STS3C-W/P path
the STS3C-W/P has exceeded the transmission performance. Go to STS3C
maintenance threshold level (BERLP) Termination, page 29-958.
set in the Grade of Service table.
UNEQ STS3C Path UNEQ detected STS3C overhead byte C2 detected an A zero value in the C2 overhead byte. Go
Unequipped (UEQ) condition. to STS3C Termination, page 29-958.
Page 29-886 7/07 76.5500/29, Rev R

DS1 VT1 Constituent (VT1 CST) Alarm Messages

7.21 To verify the meaning of the alarm message(s) received for a VT1 CST,
messages that can be generated for a VT1 CST. The second column lists a
alarm.
Table 7.13 VT1 CST Alarm Messages

AIS AIS alarm Alarm Indication Signal. The remote end is sending an "all-1s"
pattern for this DS1.
Go to DS1 VT1 Constituent (VT CST),

page 29-965.
DATALINK ESF framing datalink failure Failed to detect one or more incoming Far-end equipment is not sending data
detected DS1 Data Link messages. link messages.

page 29-965.
inhibited (via command) setting ALM=INH, using ED-T1 or alarm monitoring function.
ENT-T1 commands.
page 29-965.

page 29-965.
ISD Idle signal has been detected on The DS1 signal is idle or all zeros. The far-end is sending all zeros in the
termination DS1 channel. The DS1 is either OOS or
not connected on the far-end equipment.

page 29-965.
RED Red alarm A red alarm has been detected. The incoming signal is out of frame, or a
loss of signal is detected.

page 29-965.
SENA Neither supporting VT1 is The supporting VT1-W and The supporting VT1-W and VT1-P or
IS-NR-ACT VT1-P are no longer IS-NR. their supporting entities are OOS or
ANR.

page 29-965.
SENA Supporting VT1 is not IS-NR The supporting VT1 is no longer The supporting VT1 or one of its
IS-NR. supporting entities is OOS or ANR.

page 29-965.
76.5500/29, Rev R 7/07 Page 29-887

Table 7.13 VT1 CST Alarm Messages

SENACC Supporting Entity Not Available The termination to which the VT1 CST There is a problem with the termination
from Cross-connected Side is cross-connected has experienced a that the VT1 CST is cross-connected to.
fault condition.
page 29-965.
YEL Yellow alarm A yellow alarm has been detected. The remote end is sending a yellow
alarm.

page 29-965.
Page 29-888 7/07 76.5500/29, Rev R

T1 Internal (T1INT) Termination Alarm Messages

7.22 To verify the meaning of the alarm message(s) received for a T1INT
messages that can be generated for a T1INT facility. The second column lists a
alarm.
Table 7.14 T1INT Termination Alarm Messages

AIS AIS alarm Alarm Indication Signal. The remote end is sending an "all-1s"
pattern for this DS1. Go to T1 Internal
(T1INT) Termination, page 29-971.
ISD Idle signal has been detected on The DS1 signal is idle or all zeros. The far-end is sending all zeros in the DS1
termination channel. The DS1 is either OOS or not
connected on the far-end equipment. Go
to T1 Internal (T1INT) Termination,
page 29-971.
RED Red alarm A red alarm has been detected. The incoming signal is out of frame, or a
loss of signal is detected. Go to T1 Internal
(T1INT) Termination, page 29-971.
SENA Neither supporting VT1 is The supporting VT1-W and The supporting VT1-W and VT1-P or their
IS-NR-ACT VT1-P are no longer IS-NR. supporting entities are OOS or ANR. Go to
T1 Internal (T1INT) Termination,
page 29-971.
SENA Supporting VT1 is not IS-NR The supporting VT1 is no longer The supporting VT1 or one of its
IS-NR. supporting entities is OOS or ANR. Go to
T1 Internal (T1INT) Termination,
page 29-971.
76.5500/29, Rev R 7/07 Page 29-889

Ethernet (ETH) Termination Alarm Messages

7.23 To verify the meaning of the alarm message(s) received for an Ethernet
messages that can be generated for an Ethernet facility. The second column lists
a description of the alarm message. The third column gives a probable cause for
the alarm.
Table 7.15 Ethernet (ETH) Termination Alarm Messages

ANEGFAIL AutoNegotiation Failure Autonegotiation protocol fails to The Tellabs 5500 system failed to
negotiate the Ethernet rate and mode successfully negotiate the Ethernet
between an ETH on the NE and its rate or mode with its peer Ethernet
peer Ethernet interface, and the interface.
default rate and mode setting result in
an 802.3 link status of OK. Go to Ethernet (ETH) Termination,
page 29-1006.
INHALM Alarm Monitoring has been Alarm Monitoring has been inhibited TL1 commands were used to inhibit
inhibited (via command) by setting ALM=INH, using ED-ETH the alarm monitoring function. Refer to
or ENT-ETH commands. Tellabs 5500/5500S Command
Reference Manual, 76.5500/13, to
allow alarms using the ED-ETH
command.
Then go to Ethernet (ETH)

LINKDN Link Down No signal is detected at the physical There is a problem with the
layer. end-to-end connection.
Go to Ethernet (ETH) Termination,

page 29-1006.
Page 29-890 7/07 76.5500/29, Rev R

Ethernet Management (ETHMNG) Termination Alarm Messages

7.24 To verify the meaning of the alarm message(s) received for an Ethernet
management facility, use the following table. The first column of the table lists the
possible alarm messages that can be generated for an Ethernet management
facility. The second column lists a description of the alarm message. The third
column gives a probable cause for the alarm.
Table 7.16 Ethernet Management (ETHMNG) Termination Alarm Messages

ANEGFAIL AutoNegotiation Failure Autonegotiation protocol fails to The Tellabs 5500 system failed to
negotiate the Ethernet rate and mode successfully negotiate the Ethernet rate or
between an ETHMNG on the NE and mode with its peer Ethernet interface.
its peer Ethernet interface, and the
default rate and mode setting result in Go to Ethernet Management (ETHMNG)
an 802.3 link status of OK. Termination, page 29-1010.
INHALM Alarm Monitoring has been inhibited Alarm Monitoring has been inhibited TL1 commands were used to inhibit the
(via command) by setting ALM=INH, using alarm monitoring function. Refer to Tellabs
ED-ETHMNG or ENT-ETHMNG 5500/5500S Command Reference
commands. Manual, 76.5500/13, to allow alarms using
the ED-ETHMNG command.
Then go to Ethernet Management

(ETHMNG) Termination, page 29-1010.
LINKDN Link Down No signal is detected at the physical There is a problem with the end-to-end
layer. connection. Go to Ethernet Management
(ETHMNG) Termination, page 29-1010.
76.5500/29, Rev R 7/07 Page 29-891

Link Aggregation Group (LAG) Alarm Messages

7.25 To verify the meaning of the alarm message(s) received for an LAG, use
that can be generated for an LAG. The second column lists a description of the
Table 7.17 LAG Alarm Messages

inhibited (via command) setting ALM=INH, using ED-LAG or alarm monitoring function. Refer to Tellabs
ENT-LAG commands. 5500/5500S Command Reference
the ED-LAG command.
Then go to Link Aggregation Group (LAG),

page 29-1014.
TLC Total Loss of Capacity All members of the LAG are abnormal There is a problem with the ETH
(ANR). terminations in the LAG. Go to Link
Aggregation Group (LAG), page 29-1014.
Point to Point Protocol (PPP) Alarm Messages

7.26 To verify the meaning of the alarm message(s) received for a PPP, use the
can be generated for a PPP. The second column lists a description of the alarm
Table 7.18 PPP Alarm Messages

inhibited (via command) setting ALM=INH, using ED-PPP or alarm monitoring function. Refer to Tellabs
ENT-PPP commands. 5500/5500S Command Reference
the ED-PPP command.
Then go to Point-to-Point Protocol (PPP)

LINKDN Link Down PPP is down at the physical layer. - The PPP fails to negotiate the link control
protocol (LCP) during the link
establishment phase.
- The PPP link is a member of a PPPG
that is enabled for multi-link and fails the
multi-link protocol (ML-PPP) negotiation.
- The PPP enters the DOWN phase
without a proper termination packet
exchange.
- The echo reply is not received in
response to an echo request after a
request time-out.
Go to Point-to-Point Protocol (PPP)

Page 29-892 7/07 76.5500/29, Rev R

Point to Point Protocol Group (PPPG) Alarm Messages

7.27 To verify the meaning of the alarm message(s) received for a PPPG, use
that can be generated for a PPPG. The second column lists a description of the
Table 7.19 PPPG Alarm Messages

BCPDWN Bridge Control Protocol Down The Bridge Control Protocol (BCP) is The BCP has failed negotiation during
down. the network-layer protocol phase of PPP
link negotiation.
Go to Point-to-Point Protocol Group

(PPPG), page 29-1020.
INHALM Alarm Monitoring has been inhibited Alarm Monitoring has been inhibited TL1 commands were used to inhibit the
(via command) by setting ALM=INH, using alarm monitoring function. Refer to
ED-PPPG or ENT-PPPG commands. Tellabs 5500/5500S Command
alarms using the ED-PPPG command.
Then go to Point-to-Point Protocol Group

(PPPG), page 29-1020.
PLC Partial Loss of Capacity Some members of the PPPG are There is a problem with the PPP
abnormal (ANR.) terminations. Go to Point-to-Point
Protocol (PPP) Termination,
page 29-1017.
RADCOMM Remote Access Device A ping attempt from the shelf through There is a problem with a PPP
Communication Lost the PPPG to a Remote Access termination within the PPPG or with the
Device fails. Remote Access Device.
Go to Point-to-Point Protocol Group

(PPPG), page 29-1020, to troubleshoot
the PPPG.
To troubleshoot the Remote Access

Device, follow your company's prescribed
North America).
TLC Total Loss of Capacity All members of the PPPG are There is a problem with the PPP
abnormal (ANR). terminations. Go to Point-to-Point
Protocol (PPP) Termination,
page 29-1017.
76.5500/29, Rev R 7/07 Page 29-893

Virtual Concatenation Group (VCG) Alarm Messages

7.28 To verify the meaning of the alarm message(s) received for a VCG, use
that can be generated for a VCG. The second column lists a description of the
Table 7.20 VCG Alarm Messages

FOP Failure of LCAS Protocol - RX Duplicate sequence numbers are Can occur if multiple LCAS groups at
direction received from the far end, or there may the far end are cross connected to a
be CRC errors received on the LCAS single VCG, or if there are high bit error
channel. rates between the VCG and the far end.
Go to Virtual Concatenation Group

(VCG), page 29-1002, to troubleshoot
the VCG.
FOP Failure of LCAS Protocol - TX The far end has sent an inappropriate Far end may be misconfigured, or the
direction value for the MST (member status) in receive and transmit directions may be
response to an IDLE or DNU state. connected to different VCGs.

the VCG.
(via command) setting ALM=INH, using ED-VCG or alarm monitoring function. Refer to
ENT-VCG commands. Tellabs 5500/5500S Command
Reference Manual, 76.5500/13, to
allow alarms using the ED-VCG
command.
Then go to Virtual Concatenation

Group (VCG), page 29-1002.
LFD Loss of Frame Delineation The VCG cannot frame to the CFP Possible high bit error rates on the
frame contained in the VCAT group. facilities, or a misconfiguration of
equipment at the far end.

the VCG.
LOA Loss of Alignment: member ANR or At least one link is faulty at the VCAT This alarm occurs when LCAS has not
not in CRS level. been configured on the VCG.
Check for alarms at associated VT1s or

STS1s, and verify that all
cross-connections are set up properly.

• VT1-Working Termination
(VT1-W), page 29-984
• STS1-Working Termination
(STS1-W), page 29-974
• Virtual Concatenation Group
(VCG), page 29-1002
Page 29-894 7/07 76.5500/29, Rev R

Table 7.20 VCG Alarm Messages (Continued)

PLC Partial Loss of Capacity in the RX The partial loss of capacity receive This alarm only occurs when LCAS has
direction threshold, which is set using the been configured on the VCG.
ED-VCG command, has been crossed. Verify that the VCG parameters are
This threshold allows alarming a VCAT correctly set using the RTRV-VCG and
group when it has less than full ED-VCG commands.
capacity, for example. If fewer links Go to Virtual Concatenation Group
than the number of links specified in (VCG), page 29-1002, to troubleshoot
the PLCR parameter are good, this the VCG.
alarm is raised.
PLC Partial Loss of Capacity in the TX The partial loss of capacity transmit This alarm only occurs when LCAS has
direction threshold, which is set using the been configured on the VCG. The
ED-VCG command, has been crossed. failure is most likely at the far end, and
This threshold allows alarming a VCAT may be indicated by an RDI condition at
group when it has less than full the near end.
capacity, for example. If fewer links
than the number of links specified in Verify that the VCG parameters are
the PLCT parameter are good, this correctly set using the RTRV-VCG and
alarm is raised. ED-VCG commands.
the VCG.
PTM Payload Type Mismatch The payload type is different from the The far end equipment may not be
expected payload type. configured to send a CFP payload over
the VCG.
RADCOMM Remote Access Device A ping attempt from the shelf through There is a problem with a termination
Communication Lost the VCG to a Remote Access Device within the VCG or with the Remote
fails. Access Device.

the VCG.
To troubleshoot the Remote Access

Device, follow your company's
Technical Assistance at
1.630.798.7070 (outside North
America).
TLC Total Loss of Capacity: member In a VCG with multiple STS1s or VT1s, This alarm only occurs when LCAS has
ANR or not in CRS one of the STS1/VT1 members is ANR not been configured on the VCG.
or is not cross-connected. Since LCAS
has been disabled, the entire VCG Go to Virtual Concatenation Group
group is not functional. (VCG), page 29-1002, to troubleshoot
the VCG.
TLC Total Loss of Capacity in RX dir: The total loss of capacity receive This alarm only occurs when LCAS has
member ANR or not in CRS threshold, which is set using the been configured on the VCG.
ED-VCG command, has been crossed. Verify that the VCG parameters are
correctly set using the RTRV-VCG and
ED-VCG commands.

the VCG.
76.5500/29, Rev R 7/07 Page 29-895

Table 7.20 VCG Alarm Messages (Continued)

TLC Total Loss of Capacity in TX dir: The total loss of capacity transmit This alarm only occurs when LCAS has
member ANR or not in CRS threshold, which is set using the been configured on the VCG. The
ED-VCG command, has been crossed. failure is most likely at the far end, and
may be indicated by an RDI condition at
the near end.
Verify that the VCG parameters are
correctly set using the RTRV-VCG and
ED-VCG commands.
the VCG.
Page 29-896 7/07 76.5500/29, Rev R

DS1 Di-Group, Constituent, or Internal Termination (T1 DGR, CST, or

TRMINT)
7.29 In this section, you will troubleshoot the T1 termination in alarm. You
Caution:
The external equipment that is utilizing the T1s for DS0 grooming or VQE traffic
must be timed from the same clock reference source as the Tellabs 5500
system. Failure to meet this requirement could result in slips.
__ 1. Retrieve all T1 conditions by entering the following command:

RTRV-COND-T1:::ctag;
System response when no conditions exist:

M ctag COMPLD
System response when conditions do exist:

M ctag COMPLD

"0001-01,T1:CR,SENA,SA,01-31,23-59-59,NEND,,,\"Line Interface Module Not Available\""
"0003-02,T1:CR,SENA,SA,01-31,23-59-59,NEND,,,\"Port Module and Redundant Port Module

Not Available\""
"0003-02,T1:MN,SENA,NSA,01-31,23-59-59,NEND,,,\"TVT parity error detected on network

copy x"\"
"0003-02,T1:MN,SENACC,SA,01-31,23-59-59,NEND,,,\"Supporting Entity Not Available from

Cross-connected Side"\"
__ 1.1 If the system response verifies that a "Port Module and

Redundant Port Module Not Available" condition is
posted against the T1, go to Section 6, Troubleshooting
the Port Shelves, page 29-575, to troubleshoot the port
module.
__ 1.2 If the system response verifies that a "Line Interface

Module Not Available" condition is posted against the
T1, go to Section 5, Troubleshooting System Common
Equipment, page 29-473, to troubleshoot the LIM.
__ 1.3 If the system response verifies that a "TVT parity error

detected on network copy x" (where x equals A or B)
condition is posted against the T1, go to
Troubleshooting Internal Path Integrity Errors (DS1
page 29-1027.
76.5500/29, Rev R 7/07 Page 29-897

__ 1.4 If the system response verifies that a "Supporting Entity

Not Available from Cross-connected Side" condition is
posted against the T1, the problem is with the
termination that is cross-connected to the T1 TRMINT.
__ 1.5 For all other conditions, go to step 2.
__ 2. Retrieve the present state of the T1 by entering the following

command:
RTRV-T1::xxxx-yy:ctag;

yy = T1 in alarm.
System response:
M ctag COMPLD

"0001-26:CST:PMAID=PM3-0001,TACC=0,IDLECDE=AIS,OOSCDE=QRSS,FMT=ESF,GOS=1,ALM=INH,
ALMPF=4,RXLPBKREQ=NENDLINE,LPRSP=YES,CMDLPBKREQ=NENDLINE,FENDPMTYPE=ANSI403,
DS1ADDR=45,CSUADDR=Z,TMG=INT,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART:PST=OOS-NR"
__ 2.1 If the present state of the T1 termination is

out-of-service, normal (OOS-NR) or out-of-service,
abnormal (OOS-ANR), verify there is a valid incoming
signal and that all the parameters are set correctly.
__ 2.1.1 If parameters are incorrectly set, go to

Tellabs 5500/5500S Provisioning
Manual, 76.5500/23.
__ 2.1.2 If parameters are correctly set, continue

to step 3.
__ 2.2 If the present state of the termination is in-service,

__ 3. Edit the T1 in-service (IS) by entering the following command:

ED-T1::xxxx-yy:ctag::zzz::IS;
Where: xxxx = SDF number of the quadrant being grown.

yy = T1 in alarm.
zzz = T1 type (CST for a T1 constituent, DGR for a T1
digroup, or TRMINT for an internal termination).
Example:
ED-T1::255-1:ctag::DGR::IS;
System response (when CPC is off):

M ctag COMPLD
System response (when CPC is on):

Page 29-898 7/07 76.5500/29, Rev R

Note: If you are accessing the system on a network channel (for example,
TCP/IP), press Y and a semicolon (;) to respond to the CPC warning.
__ 4. Retrieve the T1 by entering the following command:

Where: xxxx = SDF number of the quadrant.

yy = T1 in alarm.
System response:
M ctag COMPLD

"0001-01:DGR:PMAID=PM1-0255-01,TACC=0,IDLECDE=AIS,OOSCDE=AIS,LINECDE=B8ZS,
FMT=ESF,EQLZ=1,GOS=99,ALM=ALW,ALMPF=99,FENDPMTYPE=ANSI403,DS1ADDR=C,CSUADDR=B,
TMG=THRU,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR"
__ 4.1 If the termination is in-service, normal (IS-NR), this

__ 4.2 If the termination is in-service, abnormal (IS-ANR) and

the alarmed T1 is a T1 constituent (T1 CST), is the T1
CST provisioned for VQE functionality?
__ 4.2.2 If no, go to go to DS2 Termination (T2),

page 29-901.

the alarmed T1 is a T1 digroup (T1 DGR), follow
company procedures to verify there is a valid incoming
signal and that all the parameters are set correctly.

Manual, 76.5500/23.
__ 4.3.2 If parameters are correctly set, go to

Shelves, page 29-575.

the alarmed T1 is a T1 internal termination (T1
TRMINT), go to step 6, page 29-900.
76.5500/29, Rev R 7/07 Page 29-899

__ 5. Retrieve the VQE attributes of the T1 by entering the following

command:
RTRV-VQE-T1::xxxx-yy:ctag;

yy = T1 number (1 - 28).
System response:
M ctag COMPLD

"0021-08::CHANF=ACT,DS0CHAN=18,CHANF=BYPASS,DS0CHAN=14&15&16&20,CHANCM=CAS,CASD=AND,
IDLED=AND,IDLECS=7F,IDLECR=7F"
__ 5.1 Is the T1 in VQE bypass mode (CHANF=BYPASS)?
__ 5.1.1 If yes, refer to Tellabs 5500/5500S VQE

Operations Manual, 76.5500/56, to take
the T1 out of bypass mode.
__ 5.1.2 If no, continue to substep 5.2.
__ 5.2 Verify there is a valid incoming signal and that all the
parameters are set correctly.

Tellabs 5500/5500S VQE Operations
Manual, 76.5500/56.
__ 6. Retrieve the T1 cross-connect by entering the following command:

RTRV-CRS-T1::xxxx-yy:ctag;

yy = T1 in alarm.
System response:
M ctag COMPLD

"0209-08,0010-22:CCT=2WAY,ALTMAP=NO,CCSTATE=IDLE,TAP=000::,SST=RDLD"
__ 6.1 Note the termination that the T1 TRMINT is

cross-connected to.

__ 7.1 If the T1 TRMINT is cross-connected to a T1 DGR or T1
CST, return to step 1, page 29-897, to troubleshoot the
T1 DGR or T1 CST.
__ 7.2 If the T1 TRMINT is cross-connected to a VT1, go to

Virtual Tributary 1 Termination (VT1), page 29-925, to
troubleshoot the VT1.
End of Procedure
Page 29-900 7/07 76.5500/29, Rev R

DS2 Termination (T2)

7.30 In this section, you will troubleshoot the T2 termination in alarm. You
__ 1. Retrieve the condition of all the T2s by entering the following
command:

M ctag COMPLD

M ctag COMPLD

"T2-1-1,T2:CR,SENA,SA,01-31,23-59-59,NEND,,,\"Supporting T3 Not Available"\"
"T2-3-2,T2:CR,SENA,SA,01-31,23-59-59,NEND,,,\"Port Module and Redundant Port Module
Not Available"\"

the Port Shelves, page 29-575.
__ 1.2 If the system response verifies that a "Supporting T3

Not Available" condition is posted against the T2, go to
__ 1.3 If the system response verifies a condition posted

against the T2 other than the two listed above, go to
step 2.

RTRV-T2::xxxx-y:ctag;

y = T2 in alarm.
System response:
M ctag COMPLD

"0033-2::ALM=INH,ALMPF=4,LPRSP=yes,PASUSP=OFF,PARTNAME=UASPART,MAP=T1:PST=OOS-NR"
__ 2.1 If the present state of the T2 termination is

__ 2.2 If the present state of the T2 termination is in-service,

__ 2.3 If the present state of the T2 termination is in-service,

76.5500/29, Rev R 7/07 Page 29-901

__ 3. Edit the T2 termination in-service (IS) by entering the following

command:
ED-T2::xxxx-y:ctag::::IS;

y = T2 in alarm.
System response:
M ctag COMPLD

RTRV-T2::xxxx-y:ctag;

y = T2 in alarm.
System response:
M ctag COMPLD

"0033-2::ALM=INH,ALMPF=4,LPRSP=yes,PASUSP=OFF,PARTNAME=UASPART,MAP=T1:PST=IS-NR"
__ 4.1 Verify from the system response that the T2 termination

is in-service, normal (IS-NR).
__ 4.2 If the termination is not in-service, normal (IS-NR), go to

the next step.
__ 5. Retrieve the T3 associated with the T2 in alarm by entering the

following command:
RTRV-T3::xxxx:ctag;
Where: xxxx =T3 associated with T2 in alarm.
System response:
M ctag COMPLD

"0633:TYPE=DGR:OOSCDE=AIS,FMT=M23,EQLZ=1,GOS=99,ALM=INH,ALMPF=99,XBIT=YELLOW,,
AISTYPE=SST,BERTYPE=PARER,PARITY=PATH,MAP=ASYNC,IDLECDE=IDLE,AISGEN=NAS,
FLTPR=DISABLED,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR"
__ 5.1 If the system response verifies that the T3 associated

with the alarmed T2 is a T3 Di-Group (T3 DGR), go to
DS3 Di-Group Termination (T3 DGR), page 29-903.
__ 5.2 If the system response verifies that the T3 associated

with the alarmed T2 is a T3 Constituent (T3 CST), go to
DS3 Constituent Termination (T3 CST), page 29-906.
End of Procedure
Page 29-902 7/07 76.5500/29, Rev R

DS3 Di-Group Termination (T3 DGR)

7.31 In this section, you will troubleshoot the T3 DGR termination in alarm. You
command:

M ctag COMPLD

M ctag COMPLD

"1,T3:CR,SENA,SA,01-31,23-59-59,NEND,,,\"Line Interface Module Not Available"\"
"16,T3:CR,SENA,SA,01-31,23-59-59,NEND,,,\"Port Module and Redundant Port Module Not

Available"\"


T3, go to Line Interface Module (LIM), page 29-559.
__ 1.3 For all other conditions, go to step 2, page 29-904.
76.5500/29, Rev R 7/07 Page 29-903

__ 2. Retrieve the T3 in alarm by entering the following command:

RTRV-T3::xxxx:ctag;
Where: xxxx = T3 in alarm.
System response:
M ctag COMPLD

FLTPR=DISABLED,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART:PST=OOS-NR"
__ 2.1 If the present state of the termination is out-of-service,

normal (OOS-NR) or out-of-service, abnormal
(OOS-ANR), verify that all parameters are set correctly.

Manual, 76.5500/23.

step 3.

abnormal (IS-ANR), follow company procedure to verify
valid incoming signal and that all parameters are set
correctly.

Manual, 76.5500/23.

step 3.
__ 3. Edit the T3 termination to place the facility in-service (IS) by entering

ED-T3::xxxx&&yyyy:ctag::DGR:dgr_parameters:IS;
Where: xxxx = First SDF serving the port module.

yyyy = First SDF on the port equipment shelf plus 15 or
the last SDF being edited.
dgr_parameters = Enter any other necessary parameters at this time
using Tellabs 5500/5500S Provisioning Manual,
76.5500/23. Refer to Tellabs 5500/5500S
Command Reference Manual, 76.5500/13.
Example:
ED-T3::633:ctag::DGR:ALM=INH,MAP=ASYNC,EQLZ=1:IS;
System response:
M ctag COMPLD
Page 29-904 7/07 76.5500/29, Rev R

__ 4. Retrieve the T3 DGR by entering the following command:

RTRV-T3::xxxx&&yyyy:ctag;

yyyy = First SDF on the port equipment shelf plus 15, or
the last SDF being retrieved.
Example:
RTRV-T3::633:ctag;
System response:
M ctag COMPLD

FLTPR=DISABLED,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR"
__ 4.1 Verify from the system response that the termination is

__ 4.2 If the termination is not in-service, normal (IS-NR), go to

Section 6, Troubleshooting the Port Shelves,
page 29-575, to troubleshoot the port module.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-905

DS3 Constituent Termination (T3 CST)

7.32 In this section, you will troubleshoot the T3 CST termination in alarm. You
command:

M ctag COMPLD

M ctag COMPLD


Available"\"


__ 1.3 If the system response lists an alarm condition other

than those listed above, continue to the next step.
Page 29-906 7/07 76.5500/29, Rev R


RTRV-T3::xxxx:ctag;
Where: xxxx = T3 in alarm.
System response:
M ctag COMPLD

"0633:TYPE=CST:OOSCDE=AIS,FMT=M23,EQLZ=1,GOS=99,ALM=INH,ALMPF=99,XBIT=YELLOW,,
AISTYPE=SST,BERTYPE=PARER,PARITY=PATH,MAP=ASYNC,IDLECDE=IDLE,AISGEN=NAS,FLTPR=
DISABLED,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART:PST=OOS-NR"

(OOS-ANR), verify there is a valid incoming signal and
that all parameters are set correctly.
__ 2.1.1 If parameters are incorrectly set, refer to

Manual, 76.5500/23.

step 3.

__ 3. Edit the T3 termination to change any other parameters as necessary,

and place the facility in-service (IS) by entering the following
command:
ED-T3::xxxx&&yyyy:ctag::CST:cst_parameters:IS;

yyyy = First SDF on the port shelf plus 15, or the last SDF
being edited.
cst_parameters = Enter any other necessary parameters at this time
76.5500/23. Refer to Tellabs 5500/5500S
Command Reference Manual, 76.5500/13.
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-907


RTRV-T3::xxxx&&yyyy:ctag;

yyyy = First SDF on the port shelf plus 15, or the last SDF
being retrieved.
System response:
M ctag COMPLD

"0633:TYPE=CST:OOSCDE=AIS,FMT=M23,EQLZ=1,GOS=99,ALM=INH,ALMPF=99,XBIT=YELLOW,,
AISTYPE=SST,BERTYPE=PARER,PARITY=PATH,MAP=ASYNC,IDLECDE=IDLE,AISGEN=NAS,FLTPR=
DISABLED,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR"
__ 4.1 If the system response verifies the present state of the

termination is in-service, normal (IS-NR), go to step 5.

__ 5. Verify the T1 cross-connects are configured by entering the following

command:
RTRV-CRS-T1::xxxx-1&&-28:ctag;
Where: xxxx = First SDF of the constituent T3 in alarm.

System response when cross-connects are configured:
M ctag COMPLD

"0785-01,0193-01:CCT=2WAY,ALTMAP=NO,CCSTATE=IDLE,TAP=0"
System response when cross-connects are not configured:

M ctag COMPLD
__ 5.1 If cross-connects are configured, go to step 12,

page 29-912.
__ 5.2 If cross-connects are not configured, follow company

procedures to determine if company records show the
provisioning status of the T3. Refer to Tellabs
5500/5500S Provisioning Manual, 76.5500/23, to
provision the T3; then go to step 6, page 29-909.
Page 29-908 7/07 76.5500/29, Rev R


command:

M ctag COMPLD

M ctag COMPLD


Available"\"
"0801,T3:NR,SENA,SA,03-09,12-49-13,NEND,,,\"Supporting STS1 is not IS-NR\""
__ 6.1 If the system response shows alarms or conditions for

an OC or STS-1, go to step 7.
__ 6.2 If the system response shows CTAG COMPLD, go to

step 12, page 29-912.
__ 7. Determine which OC/STS-1 is associated with the constituent T3 by

RTRV-CONFIG::SDF-xxxx:ctag;
Where: xxxx = SDF in alarm.
System response:
M ctag COMPLD

"OC3:AID=PGCO3-0369,START=SDF-0369,END=SDF-0380"
__ 7.1 Based on the AID in the system response, does the T3

CST ride on an OC shelf?
__ 7.1.2 If no, go to STS-1 Termination,

page 29-919.
76.5500/29, Rev R 7/07 Page 29-909

__ 8. Retrieve the present state of the FPG associated with the alarmed T3
RTRV-FPG-OCee::FPGee-xxxx:ctag;
Where: ee = Module type (3, 12, or 48).

xxxx = SDF number of the OC associated with the
alarmed T3.
System response:
M ctag COMPLD

"FPG3-0465:TYPE=APS:GOS=3,ALMPF=6,PSDIRN=NA,RVRTV=YES,WTR=300,PROT=NOREQ,
K1=00000000,K2=00001100,SWEVNT=OFF,SSMTYPEOC=ANSI,PARTNAME=UASPART:PST=AS"
__ 8.1 If the system response verifies that the TYPE=APS, go

to step 9.
__ 8.2 If the system response verifies that the TYPE=UPSR,

__ 9. Retrieve the STS-1 associated with the T3 constituent by entering the

following command:
RTRV-STS1::STS1-xxxx:ctag;
System response:
M ctag COMPLD

"STS1-0801::PMAID=OPM3-W-0801,TACC=0,GOS=99,ALM=ALW,ALMPF=99, STSMAP=M13,
PSL=ASYNC,PSLT=UEQ,FLTPR=DISABLED,PASUSP=OFF,PARTNAME=UASPART:PST=OOS-NR"

(OOS-ANR), go to STS-1 Termination, page 29-919.

Page 29-910 7/07 76.5500/29, Rev R

__ 10. Retrieve the state of the PPG associated with the alarmed T3 by
Where: xxxx = SDF number of the PPG associated with the

alarmed T3.
System response:
M ctag COMPLD

"PPG-0465::NODETYPE=PASSTHRU,GOS=99,ALMPF=99,PREFRD=WORKING,RVRTV=NO,WTR=300,
PROT=NA,STSMAP=INTACT,FLTPR=DISABLED,PARTNAME=UASPART:PST=AS"
"STS1-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=UEQ,PSLT=UEQ,STATUS=GOOD,PASUSP=OFF,
PARTNAME=UASPART:PST=IS-NR"
"STS1-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=UEQ,PSLT=UEQ,STATUS=GOOD,PASUSP=OFF,

both the STS-1 working and protect are in-service,

the STS-1 working and protect are not in-service,
normal (IS-NR), choose one of the following:

present state of the STS-1 working
and/or protect is out-of-service, normal
(OOS-NR), verify that all parameters are
set correctly. If parameters are
incorrectly set, go to Tellabs 5500/5500S
Provisioning Manual, 76.5500/23;
otherwise go to step 11, page 29-912.
__ 10.2.2 If the system response for the STS1-W is

in-service, abnormal (IS-ANR), go
to STS1-Working Termination
(STS1-W), step 1, page 29-974.
__ 10.2.3 If the system response for the STS1-P is

in-service, abnormal (IS-ANR), go
to STS1-Protect Termination (STS1-P),
76.5500/29, Rev R 7/07 Page 29-911

__ 11. Edit the STS1-W and/or the STS1-P in-service (IS) by entering the
following command:
ED-STS1::STS1-y-xxxx:ctag::::IS;
Where: xxxx = SDF number of the STS1 associated with the

alarmed T3.
y = Module state (W for working or P for protect).
System response:
M ctag COMPLD
__ 11.1 Return to step 10, page 29-911, to retrieve the present

state of the PPG.
__ 12. Retrieve all conditions by entering the following command:


M ctag COMPLD

M ctag COMPLD

__ 12.1 Does the system response list another condition?

this manual to troubleshoot that
condition.
__ 12.1.2 If no, follow company procedure to verify

valid incoming signal and that all
parameters are set correctly. If
parameters are incorrectly set, go to
Manual, 76.5500/23.
__ 12.1.3 If the termination is still not in-service,

normal (IS-NR), follow your company's
End of Procedure
Page 29-912 7/07 76.5500/29, Rev R

DS3 Internal Termination (DS3 TRMINT)

7.33 In this section, you will troubleshoot the DS3 internal termination in alarm.
__ 1. Retrieve the condition of all the T3 terminations by entering the
following command:

M ctag COMPLD

M ctag COMPLD

"1,T3:MN,SENACC,SA,01-31,23-59-59,NEND,,,\"Supporting Entity Not Available from
Cross-connected Side"\"
__ 1.1 If the system response verifies that a "Supporting Entity

Not Available from Cross-connected Side" condition is
posted against the T3, the problem is with the
termination to which the T3 TRMINT is
cross-connected. Continue to the next step.
__ 1.2 If the system response lists an alarm condition other

than those listed above, go to that section to
troubleshoot the problem.
__ 2. Retrieve the T3 cross-connect by entering the following command:

RTRV-CRS-T3::xxxx:ctag;
System response:
M ctag COMPLD

"0208,0010:CCT=2WAY,ALTMAP=NO,CCSTATE=IDLE,TAP=000::,SST=RDLN"
__ 2.1 Note the termination that the T3 TRMINT is

cross-connected to.
76.5500/29, Rev R 7/07 Page 29-913


__ 3.1 If the T3 TRMINT is cross-connected to a T3 DGR, go
to DS3 Di-Group Termination (T3 DGR), page 29-903.
__ 3.2 If the T3 TRMINT is cross-connected to a T3 CST, go to

DS3 Constituent Termination (T3 CST), page 29-906.
__ 3.3 If the T3 TRMINT, supported by an EPS, is

cross-connected to an asynchronous STS-1, go to
STS-1 Termination, page 29-919, to troubleshoot the
STS-1.
End of Procedure
Page 29-914 7/07 76.5500/29, Rev R

Electrical Carrier 1 Termination (EC1)

7.34 In this section, you will troubleshoot the EC1 termination in alarm. You
__ 1. Retrieve all EC1 conditions by entering the following command:
RTRV-COND-EC1:::ctag;

M ctag COMPLD

M ctag COMPLD

"EC1-0017,EC1:NR,SENA,SA,03-18,12-27-34,NEND,,,\"Port Module and Redundant Port
Module not available\""
"EC1-0145,EC1:CR,LOS,SA,11-22,10-35-23,NEND,,,\"EC1 Loss of Signal detected\""
"EC1-0018,EC1:NR,SENA,NSA,12-05,15-35-43,NEND,,,\"Line Interface Module not

available\""
"EC1-0017,EC1:NA,INHALM,NSA,12-04,09-46-29,NEND,,,\"Alarm Monitoring has been

inhibited (via command)\""
__ 1.1 If the system response verifies a \"Line Interface Module

not available\" condition against the EC1, go to Line
Interface Module (LIM), page 29-559.
__ 1.2 If the system response verifies an \"Alarm Monitoring

has been inhibited (via command)\" condition against
the EC1, follow company procedures to determine if
company records show the provisioning status of the
EC1. Refer to Tellabs 5500/5500S Provisioning
Manual, 76.5500/23, to provision the EC1 carrier; then
__ 1.3 Does the system response list alarm conditions for a

port module (PM)?
__ 1.3.1 If yes, proceed to Section 6,

page 29-575, and troubleshoot the
appropriate module.
76.5500/29, Rev R 7/07 Page 29-915

__ 2. Retrieve the present state of the EC1 by entering the following

command:
RTRV-EC1::EC1-xxxx&&-yyyy:ctag;
Where: xxxx = First SDF serving the port equipment shelf.

System response:
M ctag COMPLD
Followed by lines of data similar to the following sample (partial

response):
"EC1-0056::GOS=99,ALM=ALW,ALMPF=99,,EQLZ=,PASUSP=OFF,PARTNAME=UASPART:PST=OOS-NR"

(OOS-ANR), go to step 3, page 29-917.

correctly.

Manual, 76.5500/23. Then go to step 4,
page 29-918.

Page 29-916 7/07 76.5500/29, Rev R

__ 3. Verify that the EQLZ parameter is set correctly and place the facility
Note: Refer to Tellabs 5500/5500S Command Reference Manual, 76.5500/13,

for EC1 parameter options. If parameters are set incorrectly, use Tellabs
5500/5500S Provisioning Manual, 76.5500/23, to change any other
parameters as necessary.
ED-EC1::EC1-xxxx&&-yyyy:ctag:::EQLZ=z,ec1_parameters:IS;

the last SDF being edited.
z = Attenuation that is applied at this termination,
measured in cable length (1 to specify from 0 - 255
feet, 2 to specify from 255-450 feet). The system
default is 1.
ec1_parameters = Enter any other necessary parameters at this time
76.5500/23.
Example:
ED-EC1::EC1-56:ctag:::GOS=99,ALM=INH,ALMPF=99,,EQLZ=2:IS;
System response (when CPC is off):

M ctag COMPLD
System response (when CPC is on):

76.5500/29, Rev R 7/07 Page 29-917

__ 4. Retrieve the EC1 by entering the following command:

RTRV-EC1::EC1-xxxx&&-yyyy:ctag;

Example:
RTRV-EC1::EC1-56:ctag;
System response:
M ctag COMPLD

"EC1-0056::GOS=99,ALM=INH,ALMPF=99,,EQLZ=2,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR"
__ 4.1 Verify from the system response that EQLZ is set

correctly. Refer to Tellabs 5500/5500S Provisioning
Manual, 76.5500/23, for EC1 parameter options.
__ 4.2 Verify from the system response that any other

necessary parameters are set correctly.

__ 4.4 If the termination is not in-service, normal (IS-NR),

follow company procedures to verify there is a valid
incoming signal and that all parameters are set
Manual, 76.5500/23.
End of Procedure
Page 29-918 7/07 76.5500/29, Rev R

STS-1 Termination
7.35 In this section, you will troubleshoot the STS-1 termination in alarm. You
__ 1. Retrieve all STS-1 conditions by entering the following command:
RTRV-COND-STS1:::ctag;

M ctag COMPLD

M ctag COMPLD

"STS1-0018,STS1:NR,SENA,NSA,12-05,15-56-44,NEND,,,\"Supporting EC1 not available"\"
__ 1.1 If the system response lists \"Supporting EC1 not

available\", refer to Electrical Carrier 1 Termination
(EC1), page 29-915.
__ 1.2 If the system response lists \"LCAS Member not

Deskewable\", trace the path of the alarmed STS1 and
compare the path to the paths of the other STS1/VT1
members in the VCG. The alarm may be caused by one
of the STS1/VT1 members experiencing an excessive
differential delay, relative to the remaining members of
the VCG. For example, the alarmed STS1/VT1 may
travel through an additional piece of equipment before
reaching the Tellabs 5500 system, which adds the
delay.
Follow your company's prescribed procedures for

port module (PM)?

appropriate module.
__ 2. Retrieve the present state of the STS-1 by entering the following

command:
RTRV-STS1::STS1-xxxx:ctag:::DETAILS=YES;
Where: xxxx = SDF of the alarmed STS-1.
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-919


"STS1-0049::PMAID=PME-0049,TACC=0,GOS=1,ALM=INH,ALMPF=4,STSMAP=VTFLOAT,PSL=VTFLOAT,
PSLT=VTFLOAT,FLTPR=DISABLED,PASUSP=OFF,PARTNAME=UASPART,APPL=VQE/NB:PST=OOS-NR"

(OOS-ANR), verify there is a valid incoming signal and
that all the parameters are set correctly.
__ 2.1.1 If parameters are set incorrectly, go to

Manual, 76.5500/23.
__ 2.1.2 If parameters are set correctly, go to step

3, page 29-920.

abnormal (IS-ANR), go to substep 4.2.
__ 3. Edit the STS-1 in-service (IS) by entering the following command:

ED-STS1::STS1-xxxx:ctag::::IS;
Where: xxxx = SDF of the STS-1 in alarm.
System response:
M ctag COMPLD

command:
Where: xxxx = SDF number of the alarmed STS-1.
System response:
M ctag COMPLD

PSLT=VTFLOAT,FLTPR=DISABLED,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR"
__ 4.1 If the system response shows the STS-1 termination is

in-service, normal (IS-NR), this procedure is complete.
__ 4.2 If the system response is not in-service, normal (IS-NR),

__ 4.2.1 If the system response shows

PMAID=OPM48-W, go to step 5.

PMAID=OPM12-W, go to step 7.

PMAID=OPM3-W, go to step 9,
page 29-923.
Page 29-920 7/07 76.5500/29, Rev R


PMAID=PME or EPMX24, go to step 11,
page 29-924.
__ 5. Retrieve the present state of the working OPM48 associated with the
alarmed STS-1 by entering the following command:
RTRV-EQPT::OPM48-W-xxxx:ctag;
Where: xxxx = SDF number of the OPM48 associated with the

alarmed STS-1.
System response:
M ctag COMPLD

"OPM48-W-0065:TYPE=SHORT:HWV=81.5594B RB,SN=JL5081447,DT=960103,ALMPF=99,CONN=FC,
WLENGTH=1310:PST=IS-NR"
__ 5.1 If the system response verifies that the OPM48-W is

__ 5.2 If the system response verifies that the OPM48-W is not

in-service, normal (IS-NR), go to Section 6,
Troubleshooting the Port Shelves, page 29-575.
__ 6. Retrieve the present state of the protect OPM48 associated with the
RTRV-EQPT::OPM48-P-xxxx:ctag;
Where: xxxx = SDF number of the OPM48 associated with the

alarmed STS-1.
System response:
M ctag COMPLD

OPM48-P-0065:TYPE=SHORT:HWV=81.5594B RB,SN=JL5081447,DT=960103,ALMPF=99,CONN=FC,
__ 6.1 If the system response verifies that the OPM48-P is not

Troubleshooting the Port Shelves, page 29-575, step 1,
page 29-705.
__ 6.2 If the system response verifies that the OPM48W and

OPM48-P are in-service, normal (IS-NR), go to Optical
Carrier 48-Working Termination (OC48-W),
page 29-949.
76.5500/29, Rev R 7/07 Page 29-921

Where: eeee = Module type (12 or 12X4).

xxxx = SDF number of the OPM12 associated with the
alarmed STS-1.
System response:
M ctag COMPLD

"OPM12-W-0205:TYPE=SHORT:HWV=81.5543A RC,SN=KL5028937,DT=960222,ALMPF=99,CONN=FC,



alarmed STS-1.
System response:
M ctag COMPLD

"OPM12-P-0205:TYPE=SHORT:HWV=81.5543A RC,SN=KL5028937,DT=960222,ALMPF=99,CONN=FC,
__ 8.1 If the system response verifies that the OPM12-P is not

page 29-705.
__ 8.2 If the system response verifies that the OPM12-W and

Carrier 12-Working Termination (OC12-W),
page 29-940.
Page 29-922 7/07 76.5500/29, Rev R

__ 9. Retrieve the present state of the OPM3-W associated with the alarmed
STS-1 by entering the following command:
RTRV-EQPT::OPMeee-W-xxxx:ctag;
Where: eee = Module type (3 or 3X8).

alarmed STS-1.
System response:
M ctag COMPLD



RTRV-EQPT::OPMeee-P-xxxx:ctag;

alarmed STS-1.
System response:
M ctag COMPLD

__ 10.1 If the system response verifies that the OPM3-P not

page 29-705.
__ 10.2 If the system response verifies that the OPM3-W and

Carrier 3-Working Termination (OC3-W), page 29-931.
76.5500/29, Rev R 7/07 Page 29-923

__ 11. Retrieve the present state of the PM associated with the alarmed
STS-1 by entering one of the following commands:
Where: xxxx = SDF number of the PM associated with the

alarmed STS-1
System response:
M ctag COMPLD

"PME-0161:TYPE=STS1E:HWV=81.5520 RA,SN=IL2146940,DT=940601,ALMPF=99,PRTN=ALW,
PMPI=PASSIVE:PST=IS-NR-ACT"
__ 11.1 If the system response verifies that the PME or

EPMX24 is in-service, normal (IS-NR), go to Electrical
Carrier 1 Termination (EC1), page 29-915.
__ 11.2 If the system response verifies that the PME or

EPMX24 is in-service, abnormal (IS-ANR), go to
page 29-575.
End of Procedure
Page 29-924 7/07 76.5500/29, Rev R

Virtual Tributary 1 Termination (VT1)

7.36 In this section, you will troubleshoot the VT1 termination in alarm. You
Caution:
The external equipment that is utilizing the VT1s for DS0 grooming or VQE traffic
must be timed from the same clock reference source as the Tellabs 5500
system. Failure to meet this requirement could result in slips.
__ 1. Retrieve all VT1 conditions by entering the following command:

RTRV-COND-VT1:::ctag;

M ctag COMPLD

M ctag COMPLD

"VT1-0001-1-1,VT1:NR,SENA,NSA,01-31,23-59-59,NEND,,,\"Supporting STS1 Not
Available"\"
"VT1-0001-2-1,VT1:,SENA,NSA,01-31,23-59-59,NEND,,,\"TVT parity error detected on

network copy x"\"
__ 1.1 If the system response lists \"LCAS Member not

Deskewable\", trace the path of the alarmed VT1 and
compare the path to the paths of the other STS1/VT1
members in the VCG. The alarm may be caused by one
of the STS1/VT1 members experiencing an excessive
differential delay, relative to the remaining members of
the VCG. For example, the alarmed STS1/VT1 may
travel through an additional piece of equipment before
reaching the Tellabs 5500 system, which adds the
delay.

76.5500/29, Rev R 7/07 Page 29-925


port module (PM)?

appropriate module.
__ 1.3 Does the system response list a "TVT parity error

condition against the VT1?
__ 1.3.1 If yes, go to Troubleshooting Internal

Path Integrity Errors (DS1 CST, DS1
DGR, VT1, or VPG Termination),
page 29-1027.
__ 2. Retrieve the VT1 in alarm by entering the following command:

RTRV-VT1::VT1-xxxx-y-z:ctag:::DETAILS=YES;

y = VT group number (1 - 7).
z = VT number (1 - 4).
System response:
M ctag COMPLD

"VT1-0093-2-3::PMAID=PME-93,TACC=0,GOS=99,ALM=ALW,ALMPF=99,VTMAP=ASYNC,PSL=NA,
PSLT=NA,FLTPR=DISABLED,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART,APPL=VQE/NB:PST=OOS-NR
"

(OOS-ANR), verify that all parameters are set correctly.
__ 2.1.1 If parameters are set incorrectly, go to

Manual, 76.5500/23.
__ 2.1.2 If parameters are set correctly, go to step

3, page 29-926.
__ 3. Edit the VT1 termination in-service (IS) by entering the following

command:
ED-VT1::VT1-xxxx-y-z:ctag::::IS;

System response:
M ctag COMPLD
Page 29-926 7/07 76.5500/29, Rev R

__ 4. Retrieve the VT1 by entering the following command:

RTRV-VT1::VT1-xxxx-y-z:ctag;

System response:
M ctag COMPLD

"VT1-0093-2-3::PMAID=PME-93,TACC=0,GOS=99,ALM=ALW,ALMPF=99,VTMAP=ASYNC,PSL=NA,
PSLT=NA,FLTPR=DISABLED,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART,APPL=VQE/NB:PST=IS-NR"
__ 4.1 If the system response shows that the termination is

in-service, normal (IS-NR), the procedure is complete.

__ 5. Verify the VT1 cross-connects are configured by entering the following

command:
RTRV-CRS-VT1::VT1-xxxx-1&&-28:ctag;
Where: xxxx = SDF of the VT1 in alarm.
System response:
M ctag COMPLD
System response when cross-connects are configured:

"VT1-0369-1-1,VT1-0372-1-1:CCT=2WAY,ALTMAP=NO,CCSTATE=IDLE,TAP=0"
System response when cross-connects are not configured:

M CTAG COMPLD
__ 5.1 If cross-connects are configured, go to step 7,

page 29-929.
__ 5.2 If cross-connects are not configured, follow company

provisioning status of the VT1. Refer to Tellabs
provision the VT1; then go to step 6, page 29-928.
76.5500/29, Rev R 7/07 Page 29-927



System response:
M ctag COMPLD

"VT1-0093-2-3::PMAID=PME-93,TACC=0,GOS=99,ALM=ALW,ALMPF=99,VTMAP=ASYNC,PSL=NA,PSLT=N
A,FLTPR=DISABLED,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART,APPL=VQE/NB:PST=IS-NR"

normal (IS-NR), verify that all parameters are set
correctly.
__ 6.1.1 If parameters are set incorrectly, refer to

Manual, 76.5500/23.
__ 6.1.2 If parameters are set correctly, the

__ 6.2 If the present state of the termination is abnormal

(ANR), continue to the next step.
Page 29-928 7/07 76.5500/29, Rev R

__ 7. Retrieve the present state of the STS-1 associated with the VT1 by
System response:
M ctag COMPLD


(OOS-ANR), go to step 8.

abnormal (IS-ANR), go to substep 9.2, page 29-930.
__ 8. Edit the STS-1 in-service (IS) by entering the following command:

ED-STS1::STS1-xxxx:ctag::::IS;
Where: xxxx = SDF of the STS-1 in alarm.
System response:
M CTAG COMPLD

command:
System response:
M ctag COMPLD

__ 9.1 If the system response verifies that the termination is

76.5500/29, Rev R 7/07 Page 29-929


choose one of the following:

PMAID=OPM48-W, go to Optical Carrier
48-Working Termination (OC48-W),
page 29-949.

page 29-940.

page 29-931.

PMAID=PME or EPMX24, go to STS-1


System response:
M ctag COMPLD

"VT1-0093-2-3::PMAID=PME-93,TACC=0,GOS=99,ALM=ALW,ALMPF=99,VTMAP=ASYNC,
PSL=NA,PSLT=NA,FLTPR=DISABLED,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR"
__ 10.1 Verify that the termination is in-service, normal (IS-NR).
__ 10.2 If the present state of the termination is abnormal

(ANR), follow your company's prescribed procedures
End of Procedure
Page 29-930 7/07 76.5500/29, Rev R

Optical Carrier 3-Working Termination (OC3-W)

7.37 In this section, you will troubleshoot the OC-3 working termination in alarm.
RTRV-COND-OC3:::ctag;

M ctag COMPLD

M ctag COMPLD

"OC3-W-1732,OC3:MN,PROTNA,NSA,08-04,14-41-02,NEND,,,\"OCN-W is ANR\""
"OC3-W-1732,OC3:MN,LOS,NSA,08-04,14-41-02,NEND,,,\"Loss of Signal\""
"OC3-W-1732,OC3:NR,SENA,SA,08-04,15-30-10,NEND,,,\"Supporting Entity (OPMN) Not

Available\""
__ 1.1 Does the system response list alarm conditions for an

optical port module (OPM)?
__ 1.1.1 If yes, go to Section 6, Troubleshooting

the Port Shelves, page 29-575, to
troubleshoot the OPM.
76.5500/29, Rev R 7/07 Page 29-931

__ 2. Retrieve the present state of the working and protect OC-3 by entering
System response:
M ctag COMPLD


,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT""
__ 2.1 If the system response verifies that the working OC-3 is

abnormal (OOS-ANR), go to step 3.

page 29-933.

__ 3. Edit the working OC-3 in-service by entering the following command:

ED-OC3::OC3-W-xxxx:ctag::::IS;
System response:
M ctag COMPLD
Page 29-932 7/07 76.5500/29, Rev R

System response:
M ctag COMPLD



__ 4.2 If the working OC-3 is in-service, abnormal (IS-ANR),

go to step 5.
alarmed working OC-3 by entering the following command:

xxxx = SDF number of the working OPM3 associated with
the alarmed working OC-3.
System response:
M ctag COMPLD

__ 5.1 If the system response verifies that the working OPM3

is out-of-service, normal (OOS-NR), go to step 6,
page 29-934.

is in-service, abnormal (IS-ANR), go to Section 6,
76.5500/29, Rev R 7/07 Page 29-933


is in-service, normal (IS-NR), follow company
procedure to verify a valid incoming signal on the
working OC-3 and to verify that all parameters are set
correctly. If parameters are incorrectly set, go to Tellabs
__ 6. Edit the working OPM3 in-service (IS) by entering the following

command:
ED-EQPT::OPMeee-W-xxxx:ctag::::IS;

the alarmed OC3.
System response:
M ctag COMPLD
__ 7. Retrieve the present state of thew working OPM3 associated with the
alarmed OC3 by entering the following command:

the alarmed OC3.
System response:
M ctag COMPLD

"OPM3-W-0193:TYPE=SHORT:HWV=81.5542ARA,SN=JL2679341,DT=950803,ALMPF=99,
CONN=FC,FREQ=1310:PST=IS-NR"
__ 7.1 If the system response verifies the working OPM3 is

in-service, abnormal (IS-ANR), go to Section 6,
__ 7.2 If the system response verifies the working OPM3 is

Page 29-934 7/07 76.5500/29, Rev R

System response:
M ctag COMPLD


__ 8.1 Verify from the system response that the working OC-3
__ 8.2 If the system response verifies that the protect OC-3 is

out-of-service (OOS), go to Optical Carrier 3-Protect
End of Procedure
76.5500/29, Rev R 7/07 Page 29-935

Optical Carrier 3-Protect Termination (OC3-P)

7.38 In this section, you will troubleshoot the OC-3 protect termination in alarm.

M ctag COMPLD

M ctag COMPLD

"OC3-P-1732,OC3:MN,PROTNA,NSA,08-04,14-41-02,NEND,,,\"OCN-P is ANR\""
"OC3-P-1732,OC3:MN,LOS,NSA,08-04,14-41-02,NEND,,,\"Loss of Signal\""
"OC3-P-1732,OC3:NR,SENA,SA,08-04,15-30-10,NEND,,,\"Supporting Entity (OPMN) Not

Available\""


System response:
M ctag COMPLD

"FPG3-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,
PROT=SFONWKG,K1=11000001,K2=00010100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=ON,
PARTNAME=UASPART:PST=AS"
,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-STBY"
"OC3-P-1732::PMAID=OPM3-P-1732,ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN,
Page 29-936 7/07 76.5500/29, Rev R

__ 2.1 If the system response verifies the protect OC-3 is

__ 2.2 If the system response verifies the protect OC-3 is

page 29-938.
__ 3. Edit the protect OC-3 in-service by entering the following command:

ED-OC3::OC3-P-xxxx:ctag::::IS;
System response:
M ctag COMPLD
System response:
M ctag COMPLD

"FPG3-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300, PROT=SFONWKG,
__ 4.1 If the protect OC-3 is in-service, abnormal (IS-ANR), go


76.5500/29, Rev R 7/07 Page 29-937

alarmed protect OC-3 by entering the following command:

xxxx = SDF number of the protect OPM3 associated with
the alarmed protect OC-3.
System response:
M ctag COMPLD

"OPM3-P-1732:TYPE=SHORT:HWV=81.5542AF,SN=MI0504585,DT=981007,ALMPF=99,CONN=SC,
__ 5.1 If the system response verifies that the protect OPM3 is



in-service, normal (IS-NR), follow company procedure
to verify a valid incoming signal on the protect OC-3 and
to verify that all parameters are set correctly. If
parameters are incorrectly set, go to Tellabs
__ 6. Edit the protect OPM3 in-service (IS) by entering the following

command:
ED-EQPT::OPMeee-P-xxxx::::IS;

System response:
M ctag COMPLD
Page 29-938 7/07 76.5500/29, Rev R


System response:
M ctag COMPLD

"OPM3-P-1732:TYPE=SHORT:HWV=81.5542AF,SN=MI0504585,DT=981007,ALMPF=99,
CONN=SC,WLENGTH=1310:PST=IS-NR"


System response:
M ctag COMPLD

PROT=SFONWKG,K1=11000001,K2=00010100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=ON,
PARTNAME=UASPART:PST=AS"
"OC3-P-1732::PMAID=OPM3-P-1732,ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN,
__ 8.1 Verify from the system response that the protect OC-3
__ 8.2 If the system response verifies the working OC-3 is

out-of-service (OOS), go to Optical Carrier 3-Working
End of Procedure
76.5500/29, Rev R 7/07 Page 29-939


7.39 In this section, you will troubleshoot the OC-12 working termination in
alarm. You should have completed System Pre-Checks, page 29-852, and been

M ctag COMPLD

M ctag COMPLD


Available\""


__ 2. Retrieve the present state of the working and protect OC-12 by

System response:
M ctag COMPLD

"OC12-W-1732::PMAID=OPM12X4-W-1732,ALM=ALW,CMDLPBKREQ=NONE,STATUS=SF,SSM=NA,SSMEVENT
=OFF,SSMUSER=SYS,
PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-STBY"
"OC12-P-1732::PMAID=OPM12X4-P-1732,ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=UNKNOWN,S
Page 29-940 7/07 76.5500/29, Rev R


SSMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-ACT"
__ 2.1 If the system response verifies that the working OC-12

is in-service, abnormal (IS-ANR), go to step 5,
page 29-942.

is out-of-service, normal (OOS-NR or out-of-service,
abnormal (OOS-ANR)), go to step 3, page 29-941.

System response:
M ctag COMPLD

System response:
M ctag COMPLD

=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"

76.5500/29, Rev R 7/07 Page 29-941



is in-service, normal (IS-NR), go to step 8, page 29-943.

xxxx = SDF number of the working OPM12 associated
with the alarmed working OC-12.
System response:
M ctag COMPLD

"OPM12-W-1732:TYPE=SHORT:HWV=81.5542AF,SN=MI0504585,DT=981007,ALMPF=99,CONN=SC,
WLENGTH=1310:PST=OOS-NR"

is out-of-service, normal (OOS-NR), go to step 6.



command:

with the alarmed OC12.
System response:
M ctag COMPLD
Page 29-942 7/07 76.5500/29, Rev R


with the alarmed OC12.
System response:
M ctag COMPLD

"OPM12-P-1732:TYPE=SHORT:HWV=81.5542AF,SN=MI0504585,DT=981007,ALMPF=99,
CONN=SC,WLENGTH=1310:PST=IS-NR"


is in-service, normal (IS-NR), go to step 8.

System response:
M ctag COMPLD

=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"

76.5500/29, Rev R 7/07 Page 29-943


is in-service, normal (IS-NR), this procedure is
complete.

End of Procedure
Page 29-944 7/07 76.5500/29, Rev R


7.40 In this section, you will troubleshoot the OC-12 protect termination in

M ctag COMPLD

M ctag COMPLD


Available\""



System response:
M ctag COMPLD

"FPG12-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=SFONPROT,
=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"
76.5500/29, Rev R 7/07 Page 29-945



page 29-942.

System response:
M ctag COMPLD

System response:
M ctag COMPLD

"FPG12-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300, PROT=SFONPROT,
=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-ACT"
__ 4.1 If the protect OC-12 is in-service, abnormal (IS-ANR),


Page 29-946 7/07 76.5500/29, Rev R


xxxx = SDF number of the protect OPM12 associated
with the alarmed protect OC-12.
System response:
M ctag COMPLD

__ 5.1 If the system response verifies that the protect OPM12



protect OC-12 and to verify that all parameters are set

command:

with the alarmed protect OC12.
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-947


with the alarmed protect OC12.
System response:
M ctag COMPLD




System response:
M ctag COMPLD

PROT=NOREQ,K1=11000001,K2=00010100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=ON,PARTNAME=
UASPART:PST=AS"
"OC12-P-1732::PMAID=OPM12X4-P-1732,ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,
SSM=UNKNOWN,SSMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"


is out-of-service (OOS), go to Optical Carrier
12-Working Termination (OC12-W), page 29-940.
End of Procedure
Page 29-948 7/07 76.5500/29, Rev R


7.41 In this section, you will troubleshoot the OC-48 working termination in

M ctag COMPLD

M ctag COMPLD


Available\""



System response:
M ctag COMPLD

"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=SFONWKG,K1
=11000000,K2=00000100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=ON,PARTNAME=UASPART
:PST=AS"
76.5500/29, Rev R 7/07 Page 29-949


:PST=AS"
SMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-ACT"

is in-service, abnormal (IS-ANR), go to step 5,
page 29-951.

is out-of-service, normal (OOS-NR) or out-of-service,

System response:
M ctag COMPLD

System response:
M ctag COMPLD

"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=SFONWKG,K1
=11000000,K2=00000100,SWEVNT=NA,SSMTYPEOC=ANSI,OCPROT=ON,PARTNAME=UASPART
:PST=AS"
Page 29-950 7/07 76.5500/29, Rev R


:PST=AS"


is in-service, normal (IS-NR), go to step 8, page 29-952.
M ctag COMPLD





command:
ED-EQPT::OPM48-W-xxxx:ctag::::IS;
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-951

M ctag COMPLD




System response:
M ctag COMPLD

"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=DNR,K1=110
:PST=AS"
SMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"

:PST=AS"
Page 29-952 7/07 76.5500/29, Rev R


is in-service, normal (IS-NR), this procedure is
complete.

End of Procedure
76.5500/29, Rev R 7/07 Page 29-953


7.42 In this section, you will troubleshoot the OC-48 protect termination in

M ctag COMPLD

M ctag COMPLD


Available\""



System response:
M ctag COMPLD

"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=SFONPROT,
"OC48-W-0645::PMAID=OPM48-W-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=SF,SSM=UNKNOWN,
"OC48-P-0645::PMAID=OPM48-P-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=SF,SSM=UNKNOWN,
SSMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-STBY"
Page 29-954 7/07 76.5500/29, Rev R



page 29-956.

System response:
M ctag COMPLD

System response:
M ctag COMPLD

:PST=AS"
SMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR-STBY"
__ 4.1 If the protect OC-48 is in-service, abnormal (IS-ANR),


76.5500/29, Rev R 7/07 Page 29-955

System response:
M ctag COMPLD

"OPM48-P-0065:TYPE=SHORT:HWV=81.5594B RB,SN=JL5081447,DT=960103,ALMPF=99,CONN=FC,
WLENGTH=1310:PST=IS-ANR"



protect OC-48 and to verify that all parameters are set

command:
ED-EQPT::OPM48-P-xxxx:ctag::::IS;
System response:
M ctag COMPLD
Page 29-956 7/07 76.5500/29, Rev R

System response:
M ctag COMPLD

"OPM48-P-0065:TYPE=SHORT:HWV=81.5594B RB,SN=JL5081447,DT=960103,ALMPF=99,CONN=FC,



System response:
M ctag COMPLD

"FPG48-0645:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NA,WTR=300,PROT=SFONPROT,
"OC48-W-0645::PMAID=OPM48-W-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=SF,SSM=UNKNOWN,
"OC48-P-0645::PMAID=OPM48-P-0645,ALM=INH,CMDLPBKREQ=NONE,STATUS=SF,SSM=UNKNOWN,


is out-of-service (OOS), go to Optical Carrier
End of Procedure
76.5500/29, Rev R 7/07 Page 29-957

STS3C Termination
7.43 In this section, you will troubleshoot the STS3C termination in alarm. You
__ 1. Retrieve all STS3Cs conditions by entering the following command:
RTRV-COND-STS3C:::ctag;

M ctag COMPLD

M ctag COMPLD

"STS3C-0801,STS3C:NR,SENA,SA,03-10,09-24-22,NEND,,,\"Neither supporting OCN is
IS-NR-ACT\""
"STS3C-0145,STS3C:NR,SENA,SA,11-22,10-35-23,NEND,,,\"Supporting OCN not available\""
"STS3C-0159,STS3C:NR,SENA,SA,11-15,17-18-45,NEND,,,\"Supporting MM or RMM is not

IS-NR\""
__ 1.1 If the system response verifies that a "Neither

supporting OCN is IS-NR-ACT" condition is posted
against the STS3C, go to step 2, page 29-959.
__ 1.2 If the system response verifies that a "Supporting MM or

RMM is not IS-NR" condition is posted against the
STS3C, go to step 3, page 29-960.
__ 1.3 If the system response verifies that a "STS3C Remote

Failure Indication Detected" condition is posted against
the STS3C, there is an external problem upstream of
the Tellabs 5500/5500S. Follow internal policy.

against the STS3C other than the three listed above, go
Page 29-958 7/07 76.5500/29, Rev R

__ 2. Retrieve the present state of the FPG associated with the alarmed
STS3C by entering the following command:

alarmed STS3C.
System response:
M ctag COMPLD

"FPG12-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=SFONPROT,
=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-ACT"

SSMEVENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-ACT"
__ 2.1 If the system response verifies that the OC3-W is

not in-service, normal (IS-NR), go to Optical Carrier
__ 2.2 If the system response verifies that the OC3-P is not

in-service, normal (IS-NR), go to Optical Carrier
3-Protect Termination (OC3-P), page 29-936.
__ 2.3 If the system response verifies that the OC12-W is not


__ 2.5 If the system response verifies that the OC48-W is not

76.5500/29, Rev R 7/07 Page 29-959


__ 2.7 If the system response verifies a present state of the

working and protect OC-3 or OC-12 is in-service,
__ 3. Retrieve the present state of the Mapping Module (MM) associated

with the alarmed STS3C by entering one of the following commands:
Where: xxxx = SDF number of the MM associated with the

alarmed STS3C.
System response:
M ctag COMPLD

"MM-0205:TYPE=MM3:HWV=81.5544 RA,SN=JL2680187,DT=950719,ALMPF=99:PST=IS-NR-ACT"

abnormal (IS-ANR) or abnormal, unequipped
(ANR-UEQ), go to Section 6, Troubleshooting the Port
Shelves, page 29-575, to troubleshoot the faulted MM.
__ 3.2 If the system response verifies that the MM is


__ 4. Edit the MM in-service (IS) by entering one of the following commands:

ED-EQPT::MM-xxxx:ctag:::MODE=FRCD:IS:
ED-EQPT::MM24-xxxx:ctag:::MODE=FRCD:IS:
Where: xxxx = SDF number of the MM.
System response:
M ctag COMPLD
Page 29-960 7/07 76.5500/29, Rev R

__ 5. Retrieve the present state of the MM associated with the alarmed

STS3C by entering one of the following commands:

alarmed STS3C.
System response:
M ctag COMPLD

"MM-0205:TYPE=MM3:HWV=81.5544 RA,SN=JL2680187,DT=950719,ALMPF=99:PST=IS-NR-ACT"

abnormal (IS-ANR), go to Section 6, Troubleshooting
the Port Shelves, page 29-575, to troubleshoot the
faulted MM.
__ 5.2 If the system response verifies that he MM is in-service,

normal (IS-NR), go to step 6.
__ 6. Retrieve the present state of the Redundant Mapping Module (RMM)

associated with the alarmed STS3C by entering one of the following
commands:
Where: xxxx = SDF number of the RMM associated with the

alarmed STS3C.
System response:
M ctag COMPLD

"RMM-0205:TYPE=MM3:HWV=81.5544 RA,SN=JL2680187,DT=950719,ALMPF=99:PST=IS-NR-ACT"
__ 6.1 If the system response verifies that the RMM is

in-service, abnormal (IS-ANR) or abnormal,
unequipped (ANR-UEQ), go to Section 6,
Troubleshooting the Port Shelves, page 29-575, to
troubleshoot the faulted RMM.


76.5500/29, Rev R 7/07 Page 29-961

__ 7. Edit the RMM in-service (IS) by entering one of the following

commands:
ED-EQPT::RMM-xxxx:ctag:::MODE=FRCD:IS:
ED-EQPT::RMM24-xxxx:ctag:::MODE=FRCD:IS:
Where: xxxx = SDF number of the RMM.
System response:
M ctag COMPLD
__ 8. Retrieve the present state of the Redundant Mapping Module (RMM)

associated with the alarmed STS3C by entering one of the following
commands:
Where: xxxx = SDF number of the RMM associated with the

alarmed STS3C.
System response:
M ctag COMPLD

"RMM-0205:TYPE=MM3:HWV=81.5544 RA,SN=JL2680187,DT=950719,ALMPF=99:PST=IS-NR-ACT"


Page 29-962 7/07 76.5500/29, Rev R

__ 9. Retrieve the state of the alarmed STS3C by entering the following

command:
RTRV-STS3C::STS3C-xxxx:ctag;
System response:
M ctag COMPLD

"STS3C-0001::PMAID=OPM3-W-0001,TACC=0,GOS=1,ALM=INH,ALMPF=4,STS3CMAP=INTACT,
PSL=INTACT,PASUSP=OFF,PARTNAME=UASPART:PST=OOS-NR"


abnormal (IS-ANR), follow company procedures to
verify a valid incoming signal on the OC and verify that
all parameters are set correctly. If parameters are
incorrectly set, go to Tellabs 5500/5500S Provisioning
Manual, 76.5500/23.
__ 10. Edit the STS3C in-service by entering the following command:

ED-STS3C::STS3C-xxxx:ctag::::IS;
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-963

__ 11. Retrieve the state of the alarmed STS3C by entering the following
command:
RTRV-STS3C::STS3C-xxxx:ctag;
System response:
M ctag COMPLD

"STS3C-0001::PMAID=OPM3-W-0001,TACC=0,GOS=1,ALM=INH,ALMPF=4,STS3CMAP=INTACT,
PSL=INTACT,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR"
__ 11.1 If the system response verifies that the termination is


End of Procedure
Page 29-964 7/07 76.5500/29, Rev R

DS1 VT1 Constituent (VT CST)

7.44 In this section, you will troubleshoot the DS1 VT1 CST termination in

M ctag COMPLD

M ctag COMPLD

"T1-1-1,T1:CR,SENA,SA,01-31,23-59-59,NEND,,,\"Line Interface Module Not Available"\"
"T1-3-2,T1:CR,SENA,SA,01-31,23-59-59,NEND,,,\"Port Module and Redundant Port Module

Not Available"\"
"T1-1-4,T1:MN,SENA,NSA,01-31,23-59-59,NEND,,,\"TVT parity error detected on network

copy x"\"

Redundant Port Module Not Available"\ condition is
the Port Shelves, page 29-575, to troubleshoot the port
module.

Module Not Available"\ condition is posted against the

condition is posted against the T1, go to
page 29-1027.
__ 1.4 For all other alarm conditions, go to the next step.
76.5500/29, Rev R 7/07 Page 29-965


RTRV-T1::xxxx-yy-z:ctag;
Where: xxxx = SDF of the alarmed T1. (1 - network size range

(for example, 1024)).
yy = Port number of the T1. (1 - 7).
z = (1 - 4).
System response:
M ctag COMPLD

"0801-1-1:VTCST:PMAID=OPM3-W-0801,FMT=SF,GOS=99,ALM=ALW,ALMPF=99,
FENDPMTYPE=ANSI403,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR"
__ 2.1 Note the PMAID for use in the following step.
__ 2.2 If the T1 is supported by an EPMX24 or PME, go to

step 4.
__ 3. Using the PMAID from the system output of step 2, retrieve the
present state of the FPG associated with the alarmed T1 by entering

alarmed T1.
System response:
M ctag COMPLD

__ 3.1 If the system response verifies that the TYPE=APS, go

to step 4.
__ 3.2 If the system response verifies that the TYPE=UPSR,

Page 29-966 7/07 76.5500/29, Rev R

__ 4. Retrieve the present state of the VT1 associated with the alarmed T1
Where: xxxx = SDF number of the OPM associated with the

alarmed T1 (VTCST).
System response:
M ctag COMPLD

"VT1-0801-1-1::OPM3-W-0801::TACC=0,GOS=99,ALM=INH,ALMPF=6,VTMAP=ASYNC,PSL=UEQ,
PSLT=UEQ,FLTPR=DISABLED,FLTRC=NONE:PST=IS-NR"
__ 4.1 If the system response verifies that the VT1 is



in-service, abnormal (IS-ANR) or out-of-service,
abnormal (OOS-ANR), go to Virtual Tributary 1
__ 5. Edit the VT1associated with the alarmed T1 in-service (IS) by entering

ED-VT1::VT1-xxxx-y-z:ctag;

alarmed T1 (VTCST).
System response:
M ctag COMPLD
__ 6. Retrieve the present state of the VT1 associated with the alarmed T1

alarmed T1 (VTCST).
System response:
M ctag COMPLD

"VT1-0801-1-1::OPM3-W-0801::TACC=0,GOS=99,ALM=INH,ALMPF=6,VTMAP=ASYNC,PSL=UEQ,PSLT=U
EQ,FLTPR=DISABLED,FLTRC=NONE:PST=IS-NR"
76.5500/29, Rev R 7/07 Page 29-967



__ 7. Retrieve the VPG associated with the alarmed VT by entering the

following command:
RTRV-VPG::VPG-xxxx-y-z&&-a:ctag;

alarmed T1 (VTCST).
yy = VT group.
z = VT number.
System response:
M ctag COMPLD

__ 7.1 If the system response verifies that the VT1-W and/or

VT1-P is out-of-service, normal (OOS-NR), go to step 8,
page 29-969.
__ 7.2 If the system response verifies that either the VT1-W or

VT1-P is in-service, normal (IS-NR), go to step 10,
page 29-970.
__ 7.3 If the system response verifies that the VT1-W is

abnormal (OOS-ANR), go to VT1-Working Termination
(VT1-W), step 1, page 29-984.
__ 7.4 If the system response verifies that the VT1-P is

abnormal (OOS-ANR), go to VT1-Protect Termination
(VT1-P), step 1, page 29-988.
Page 29-968 7/07 76.5500/29, Rev R

__ 8. Edit the VT1 associated with the alarmed T1 in-service (IS) by entering
ED-VT1::VT1-W-xxxx-yy-z:ctag::::IS;

alarmed T1 (VTCST).
yy = VT group.
z = VT number.
System response:
M ctag COMPLD
__ 9. Retrieve the VPG associated with the alarmed VT by entering the

following command:
RTRV-VPG::VPG-xxxx-y-z&&-a:ctag;

alarmed T1 (VTCST).
yy = VT group.
z = VT number.
System response:
M ctag COMPLD

__ 9.1 If the system response verifies that either the VT1-W or

VT1-P is in-service, normal (IS-NR), go to step 10,
page 29-970.
__ 9.2 If the system response verifies that the VT1-W is

abnormal (OOS-ANR), go to VT1-Working Termination
(VT1-W), step 1, page 29-984.
__ 9.3 If the system response verifies that the VT1-P is

abnormal (OOS-ANR), go to VT1-Protect Termination
(VT1-P), step 1, page 29-988.
76.5500/29, Rev R 7/07 Page 29-969

__ 10. Retrieve the alarmed T1 by entering the following command:

Where: xxxx = SDF number of the alarmed T1.

yy = Port number of the T1.
System response:
M ctag COMPLD

"0001-26:CST:PMAID=PM3-0001,TACC=0,IDLECDE=AIS,OOSCDE=QRSS,FMT=ESF,GOS=1,
ALM=INH,ALMPF=4,RXLPBKREQ=NENDLINE,LPRSP=YES,CMDLPBKREQ=NENDLINE,FENDPMTYPE=ANSI403,
DS1ADDR=45,CSUADDR=Z,TMG=INT,FLTRC=NONE,PASUSP=OFF,PARTNAME=UASPART:PST=IS-NR"

End of Procedure
Page 29-970 7/07 76.5500/29, Rev R

T1 Internal (T1INT) Termination

7.45 In this section, you will troubleshoot the T1INT termination in alarm. You

M ctag COMPLD

M ctag COMPLD

"T1INT-0801-01-01,T1:MJ,RED,SA,05-09,20-47-23,NEND:\"Red alarm\":,ISLTD"
__ 2. Retrieve the T1INT in alarm by entering the following command:

RTRV-T1::T1INT-xxxx-y-z:ctag;
Where: xxxx = (1 - network size range (for example, 1024)).

y = (1 - 7).
z = (1 - 4).
System response:
M ctag COMPLD

"T1INT-801-1-1:VTCST:PMAID=MM24-801,FMT=SF,GOS=99,ALM=ALW,ALMPF=99,
FENDPMTYPE=ANSI403,PASUSP=OFF[,RPA={SRC|DEST|2WAY|OFF},[RPAAID=801-1-1]],
PARTNAME=UASPART:PST=IS-ANR"
__ 2.1 Verify the state of the T1INT. If the termination is OOS,

__ 3. Retrieve the present state of the VT1 associated with the alarmed
T1INT by entering the following command:

alarmed T1 (VTCST).
System response:
M ctag COMPLD

"VT1-0801-1-1::OPM3-W-0801::TACC=0,GOS=99,ALM=INH,ALMPF=6,VTMAP=ASYNC,PSL=UEQ,PSLT=U
EQ,FLTPR=DISABLED,FLTRC=NONE:PST=IS-NR"
76.5500/29, Rev R 7/07 Page 29-971




__ 4. Edit the VT1associated with the alarmed T1INT in-service (IS) by

ED-VT1::VT1-xxxx-y-z:ctag::::IS;
Where: xxxx = SDF number of the module associated with the

alarmed T1INT.
System response:
M ctag COMPLD
__ 5. Retrieve the present state of the VT1 associated with the alarmed
T1INT by entering the following command:
Where: xxxx = SDF number of the module associated with the

alarmed T1INT.
System response:
M ctag COMPLD

"VT1-0801-1-1::OPM3-W-0801::TACC=0,GOS=99,ALM=INH,ALMPF=6,VTMAP=ASYNC,PSL=UEQ,
PSLT=UEQ,FLTPR=DISABLED,FLTRC=NONE:PST=IS-NR"


Page 29-972 7/07 76.5500/29, Rev R

__ 6. Retrieve the alarmed T1 by entering the following command:


y = (1 - 7).
z = (1 - 4).
System response:
M ctag COMPLD

FENDPMTYPE=ANSI403,PASUSP=OFF[,RPA={SRC|DEST|2WAY|OFF},[RPAAID=802-1-1]],

End of Procedure
76.5500/29, Rev R 7/07 Page 29-973

STS1-Working Termination (STS1-W)

7.46 In this section, you will troubleshoot the STS-1 working termination in
__ 1. Retrieve all working STS-1 conditions by entering the following
command:

M ctag COMPLD

M ctag COMPLD

"STS1-W-0369,STS1:NR,SENA,SA,03-11,08-46-10,NEND,,,\"Supporting entity (OC) is not
IS-NR-ACT\""
"STS1-W-0055,STS1:CR,SENA,SA,01-31,23-59-59,NEND,,,\"The supporting MM or RMM is not

IS-NR-ACT"\"
__ 1.1 If the system response verifies that a "Cross-connection

is inconsistent with node type of protection group"
condition is posted against the STS1-W, go to step 2,
page 29-975.
__ 1.2 If the system response verifies that a "Supporting entity

(OC) is not IS-NR-ACT" condition is posted against the
STS1-W, go to step 3, page 29-975.

RMM is not IS-NR-ACT" condition is posted against the
__ 1.4 If the system response verifies that a "STS-1 Remote

the STS1-W, there is an external problem upstream of
the Tellabs 5500/5500S system. Follow internal policy.

against the STS1-W other than the four conditions listed
Page 29-974 7/07 76.5500/29, Rev R

__ 2. Retrieve the present state of the PPG associated with the alarmed
STS1-W by entering the following command:

alarmed STS1-W.
System response:
M ctag COMPLD

"STS1-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=UEQ,PSLT=UEQ,STATUS=SF,PASUSP=OFF,
PARTNAME=UASPART:PST=OOS-NR"
"STS1-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=UEQ,PSLT=UEQ,STATUS=SF,PASUSP=OFF,
__ 2.1 If the system response verifies that the nodetype equals

passthru (NODETYPE=PASSTHRU), the nodetype
needs to be reconfigured because an STS-1
termination that is cross-connected to another
termination cannot be configured for
NODETYPE=PASSTHRU. Go to Tellabs 5500/5500S
Provisioning Manual, 76.5500/23, and reconfigure the
nodetype.
__ 2.2 If the system response verifies that the nodetype does

not equal passthru (NODETYPE=PASSTHRU),
Where: ee = Module type (3, 12).

xxxx = SDF number of the FPG associated with the
alarmed STS1-W.
System response:
M ctag COMPLD

"OC3-W-0465::ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=STRATUM3,SSMEVENT=OFF,
SSMUSER=SYS,PARTNAME=UASPART:PST=IS-ANR-ACT"
"OC3-P-0465::ALM=ALW,CMDLPBKREQ=NONE,STATUS=GOOD,SSM=STRATUM3,SSMEVENT=OFF,
SSMUSER=SYS,PARTNAME=UASPART:PST=IS-NR-STBY"
76.5500/29, Rev R 7/07 Page 29-975


the OC is in-service, abnormal, active (IS-ANR-ACT),
go to one of the following, depending on which OC is
associated with the alarmed STS1-W:
Optical Carrier 3-Working Termination (OC3-W),

page 29-931
page 29-940
the OC is in-service, normal, active (IS-NR-ACT), follow


alarmed STS1-W.
System response:
M ctag COMPLD

"MM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5016233,DT=960508,ALMPF=99:PST=IS-ANR-ACT"



__ 5. Edit the MM in-service (IS) by entering one of the following commands:

ED-EQPT::MM-xxxx:ctag:::MODE=FRCD:IS;

alarmed STS1-W.
System response:
M ctag COMPLD
Page 29-976 7/07 76.5500/29, Rev R


STS1-W by entering one of the following commands:

alarmed STS1-W.
System response:
M ctag COMPLD


faulted MM.

__ 7. Retrieve the present state of the RMM by entering the following

command:
System response:
M ctag COMPLD

"RMM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5070516,DT=960516,ALMPF=99:PST=IS-ANR-STBY"



__ 8. Edit the RMM in-service (IS) by entering the following command:

ED-EQPT::RMM-xxxx:ctag:::MODE=FRCD:IS;
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-977


command:
System response:
M ctag COMPLD



__ 10. Retrieve all working STS-1 conditions by entering the following

command:

M ctag COMPLD

M ctag COMPLD

"STS1-W-0369,STS1:NR,SENA,SA,03-11,08-46-10,NEND,,,\"Supporting entity (OC) is not
IS-NR-ACT\""
__ 10.1 Verify no conditions exist against the STS1-W

termination.
End of Procedure
Page 29-978 7/07 76.5500/29, Rev R

STS1-Protect Termination (STS1-P)

7.47 In this section, you will troubleshoot the STS-1 protect termination in alarm.
__ 1. Retrieve all protect STS-1 conditions by entering the following
command:

M ctag COMPLD

M ctag COMPLD

"STS1-P-0369,STS1:NR,SENA,SA,03-11,08-46-10,NEND,,,\"Supporting entity (OC) is not
IS-NR-ACT\""
"STS1-P-0055,STS1:CR,SENA,SA,01-31,23-59-59,NEND,,,\"The supporting MM or RMM is not

IS-NR-ACT"\"
__ 1.1 If the system response verifies that a "Supporting entity

(OC) is not IS-NR-ACT" condition is posted against the
STS1-P, go to step 2, page 29-980.

STS1-P, go to step 3, page 29-981.
__ 1.3 If the system response verifies that a "STS-1 Remote

the STS1-P, there is an external problem upstream of

against the STS1-P other than the three conditions
76.5500/29, Rev R 7/07 Page 29-979

STS1-P by entering the following command:

alarmed STS1-P.
System response:
M ctag COMPLD

"FPG3-1732:TYPE=APS:GOS=99,ALMPF=99,PSDIRN=UNI,RVRTV=NO,WTR=300,PROT=SFONPROT,K1=110

the OC is in-service, normal, active (IS-NR-ACT), go to
one of the following, depending on which OC is
associated with the alarmed STS1-P.
Optical Carrier 3-Protect Termination (OC3-P),

page 29-936
page 29-945
the OC is in-service, abnormal (IS-ANR) or abnormal,
unequipped (ANR-UEQ), follow your company's
1.800.443.5555 (North America) or 1.630.798.7070
Page 29-980 7/07 76.5500/29, Rev R



alarmed STS1-P.
System response:
M ctag COMPLD


faulted MM.


__ 4. Edit the MM in-service (IS) by entering the following command:

System response:
M ctag COMPLD


alarmed STS1-P.
System response:
M ctag COMPLD


faulted MM.

76.5500/29, Rev R 7/07 Page 29-981


command:
System response:
M ctag COMPLD



abnormal (IS-ANR), go to step 7.


System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD



Page 29-982 7/07 76.5500/29, Rev R

__ 9. Retrieve all protect STS-1 conditions by entering the following

command:

M ctag COMPLD

M ctag COMPLD

"STS1-P-0369,STS1:NR,SENA,SA,03-11,08-46-10,NEND,,,\"Supporting entity (OC) is not
IS-NR-ACT\""
__ 9.1 Verify no conditions exist against the STS1-P

termination.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-983

VT1-Working Termination (VT1-W)

7.48 In this section, you will troubleshoot the VT1 working termination in alarm.
__ 1. Retrieve all working VT1 conditions by entering the following
command:

M ctag COMPLD

M ctag COMPLD

"VT1-W-0001-1-1,VT1:NR,SENA,NSA,01-31,23-59-59,NEND,,,\"Supporting STS1 Not
Available"\"
"VT1-W-0001-1-1,VT1:MN,SENA,NSA,01-31,23-59-59,NEND,,,\"TVT parity error detected on

network copy x"\"

condition is posted against the STS1-W, go to step 2,
page 29-985.
__ 1.2 If the system response verifies that a "Supporting STS-1

is not available" condition is posted against the
__ 1.3 If the system response verifies that a "VT1 Remote

Failure Indication Detected " condition is posted against

condition is posted against the VT1, go to
page 29-1027.

against the VT1-W other than the four listed above,
Page 29-984 7/07 76.5500/29, Rev R

__ 2. Retrieve the present state of the VPG associated with the alarmed
VT1-W by entering the following command:
RTRV-VPG::VPG-xxxx-y-z:ctag;
Where: xxxx = SDF number of the alarmed VT1.

y = VT group.
z = VT1 number.
System response:
M ctag COMPLD


needs to be reconfigured because a VT1 termination
that is cross-connected to another termination cannot
be configured for NODETYPE=PASSTHRU. Go to
Tellabs 5500/5500S Provisioning Manual, 76.5500/23,
and reconfigure the nodetype.

not equal passthru (NODETYPE=PASSTHRU), go to
76.5500/29, Rev R 7/07 Page 29-985


alarmed VT1-W.
System response:
M ctag COMPLD

__ 3.1 If the system response verifies that the STS1-W is

in-service, abnormal (IS-ANR), go to STS1-Working
Termination (STS1-W), page 29-974.

abnormal (OOS-ANR), continue to the next step.
__ 4. Edit the working STS-1 in-service (IS) by entering the following

command:
ED-STS1::STS1-W-xxxx:ctag::::IS;
Where: xxxx = SDF number of the working STS-1.
System response:
M ctag COMPLD
Page 29-986 7/07 76.5500/29, Rev R


alarmed VT1-W.
System response:
M ctag COMPLD



in-service, abnormal (IS-ANR), go to STS1-Working
Termination (STS1-W), page 29-974.
__ 6. Retrieve all working VT1 conditions by entering the following

command:

M ctag COMPLD

M ctag COMPLD

"VT1-W-0001-1-1,VT1:NR,SENA,NSA,01-31,23-59-59,NEND,,,\"Supporting STS1 Not
Available"\"
__ 6.1 Verify no conditions exist against the VT1-W

termination.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-987

VT1-Protect Termination (VT1-P)

7.49 In this section, you will troubleshoot the VT1 protect termination in alarm.
__ 1. Retrieve all VT1 conditions by entering the following command:

M ctag COMPLD

M ctag COMPLD

"VT1-P-0001-1-1,VT1:NR,SENA,NSA,01-31,23-59-59,NEND,,,\"Supporting STS1 Not
Available"\"
"VT1-P-0001-1-1,VT1:MN,SENA,NSA,01-31,23-59-59,NEND,,,\"TVT parity error detected on

network copy x"\"
Where: x = Network Complex Copy (A or B).
__ 1.1 If the system response verifies that a "Supporting STS-1

is not available" condition is posted against the STS1-P,
__ 1.2 If the system response verifies that a "VT1 Remote

Failure Indication Detected " condition is posted against

condition is posted against the VT1, go to
page 29-1027.

against the VT1-P other than the three listed above,
Page 29-988 7/07 76.5500/29, Rev R

VT1-P by entering the following command:

alarmed VT1-P.
System response:
M ctag COMPLD

__ 2.1 If the system response verifies that the STS1-P is

in-service, abnormal (IS-ANR), go to STS1-Protect
Termination (STS1-P), page 29-979.

abnormal (OOS-ANR), continue to the next step.
__ 3. Edit the protect STS-1 in-service (IS) by entering the following

command:
ED-STS1::STS1-P-xxxx:ctag::::IS;
Where: xxxx = SDF number of the protect STS-1.
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-989

VT1-P by entering the following command:

alarmed VT1-P.
System response:
M ctag COMPLD



in-service, abnormal (IS-ANR), go to STS1-Protect
Termination (STS1-P), page 29-979.
__ 5. Retrieve all protect VT1 conditions by entering the following command:


M ctag COMPLD

M ctag COMPLD

"VT1-P-0001-1-1,VT1:NR,SENA,NSA,01-31,23-59-59,NEND,,,\"Supporting STS1 Not
Available"\"
__ 5.1 Verify no conditions exist against the VT1-P

termination.
End of Procedure
Page 29-990 7/07 76.5500/29, Rev R

STS3C-Working Termination (STS3C-W)

7.50 In this section, you will troubleshoot the STS3C working termination in
__ 1. Retrieve all working STS3C conditions by entering the following
command:

M ctag COMPLD

M ctag COMPLD

"STS3C-W-0145,STS3C:NR,SENA,SA,11-22,10-35-23,NEND,,,\"Supporting OCN is not
IS-NR-ACT\""
"STS3C-W-0158,STS3C:NR,SENA,SA,11-14,12-44-52,NEND,,,\"Supporting MM or RMM is not

IS-NR-ACT\""

condition is posted against the STS3C-W, go to step 2,
page 29-992.
__ 1.2 If the system response verifies that a "The supporting

OCN is not IS-NR-ACT" condition is posted against the
STS3C-W, go to step 3, page 29-993.

STS3C-W, go to step 4, page 29-994.

the STS3C-W, there is an external problem upstream of

against the STS3C-W other than the conditions listed
76.5500/29, Rev R 7/07 Page 29-991

__ 2. Retrieve the present state of the CPG associated with the alarmed
STS3C-W by entering the following command:
Where: xxxx = SDF number of the CPG associated with the

alarmed STS3C-W.
System response:
M ctag COMPLD

PROT=SFONWKG,STS3CMAP=INTACT,PARTNAME=UASPART:PST=AS"
"STS3C-W-0465::PMAID=OPM3-W-0465,ALM=ALW,PSL=UEQ,STATUS=SF,PASUSP=OFF,
"STS3C-P-0465::PMAID=OPM3-P-0465,ALM=ALW,PSL=UEQ,STATUS=SF,PASUSP=OFF,

needs to be reconfigured because an STS3C
termination that is cross-connected to another
termination cannot be configured for
NODETYPE=PASSTHRU. Go to Tellabs 5500/5500S
Provisioning Manual, 76.5500/23, and reconfigure the
nodetype.

not equal passthru (NODETYPE=PASSTHRU), go to
Page 29-992 7/07 76.5500/29, Rev R


alarmed STS3C-W.
System response:
M ctag COMPLD

,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-ACT"

the OC is in-service, abnormal, active (IS-ANR-ACT),
go to one of the following, depending on which OC is
associated with the alarmed STS3C-W:

page 29-931
page 29-940
the OC is in-service, normal, active (IS-NR-ACT), follow
76.5500/29, Rev R 7/07 Page 29-993



alarmed STS3C-W.
System response:
M ctag COMPLD

"MM-0193:TYPE=MM3:HWV=81.5544 RE,SN=KL5016233,DT=960508,ALMPF=99:PST=IS-ANR"




System response:
M ctag COMPLD


alarmed STS3C-W.
System response:
M ctag COMPLD


faulted MM.

Page 29-994 7/07 76.5500/29, Rev R


command:
System response:
M ctag COMPLD





System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD



76.5500/29, Rev R 7/07 Page 29-995

__ 10. Retrieve all working STS3C conditions by entering the following

command:

M ctag COMPLD

M ctag COMPLD

"STS3C-0145,STS3C:NR,SENA,SA,11-22,10-35-23,NEND,,,\"Supporting OCN is not
IS-NR-ACT\""
__ 10.1 Verify no conditions exist against the STS3C-W

termination.
End of Procedure
Page 29-996 7/07 76.5500/29, Rev R

STS3C-Protect Termination (STS3C-P)

7.51 In this section, you will troubleshoot the STS3C protect termination in
__ 1. Retrieve all protect STS3C conditions by entering the following
command:

M ctag COMPLD

M ctag COMPLD

"STS3C-P-0145,STS3C:NR,SENA,SA,11-22,10-35-23,NEND,,,\"Supporting OCN is not
IS-NR-ACT\""
"STS3C-P-0158,STS3C:NR,SENA,SA,11-14,12-44-52,NEND,,,\"Supporting MM or RMM is not

IS-NR-ACT\""
__ 1.1 If the system response verifies that a "The supporting

OCN is not IS-NR-ACT" condition is posted against the
STS3C-P, go to step 2, page 29-998.

STS3C-P, go to step 3, page 29-999.

the STS3C-P, there is an external problem upstream of

against the STS3C-P other than the three conditions
76.5500/29, Rev R 7/07 Page 29-997

STS3C-P by entering the following command:

alarmed STS3C-P.
System response:
M ctag COMPLD

ENT=OFF,SSMUSER=SYS,PASUSP=OFF,PARTNAME=UASPART:PST=IS-ANR-ACT"

the OC is in-service, normal, active (IS-NR-ACT), go to
one of the following, depending on which OC is
associated with the alarmed STS3C-P:

page 29-936
page 29-945
the OC is in-service, abnormal (IS-ANR) or abnormal,
unequipped (ANR-UEQ), follow your company's
1.800.443.5555 (North America) or 1.630.798.7070
Page 29-998 7/07 76.5500/29, Rev R


STS3C-P by entering one of the following commands:

alarmed STS3C-P.
System response:
M ctag COMPLD


faulted MM.



System response:
M ctag COMPLD

STS3C-P by entering one of the following commands:

alarmed STS3C-P.
System response:
M ctag COMPLD


faulted MM.

76.5500/29, Rev R 7/07 Page 29-999

__ 6. Retrieve the present state of the RMM by entering one of the following
commands:
System response:
M ctag COMPLD





System response:
M ctag COMPLD
__ 8. Retrieve the present state of the RMM by entering one of the following
commands:
System response:
M ctag COMPLD

PST=IS-ANR-STBY"


Page 29-1000 7/07 76.5500/29, Rev R

__ 9. Retrieve all protect STS3C conditions by entering the following

command:

M ctag COMPLD

M ctag COMPLD

"STS3C-0145,STS3C:NR,SENA,SA,11-22,10-35-23,NEND,,,\"Supporting OCN is not
IS-NR-ACT\""
__ 9.1 Verify no conditions exist against the STS3C-P

termination.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-1001

Virtual Concatenation Group (VCG)

7.52 In this section, you will troubleshoot the virtual concatenation group in
__ 1. Retrieve all conditions against the VCG by entering the following
command:
RTRV-COND-VCG:::ctag;
M ctag COMPLD

"VCG-265-1,VCG:CR,LOA,SA,01-31,23-59-59,,,,\"Loss of Alignment: member ANR or not in
CRS\""
__ 1.1 If the system response lists one of the following

conditions against the VCG, go to step 2,
page 29-1003.
Failure of LCAS Protocol - RX direction
Failure of LCAS Protocol - Tx direction
Loss of Alignment: member ANR or not in CRS
Loss of Frame Delineation

conditions against the VCG, there is a problem with the
VT1 termination or STS-1 associated with the VCG.
Partial Loss of Capacity in the RX direction
Partial Loss of Capacity in the TX direction
Total Loss of Capacity in RX dir: member ANR or not

in CRS
Total Loss of Capacity in TX dir: member ANR or not

in CRS
Total Loss of Capacity: member ANR or not in CRS
Payload Type Mismatch

STS-1 Termination, page 29-919
Virtual Tributary 1 Termination (VT1), page 29-925
Page 29-1002 7/07 76.5500/29, Rev R


conditions, troubleshoot the connected equipment.
Remote Access Device Communication Lost


M ctag COMPLD

M ctag COMPLD

"MM-0035,EQPT:MN,INT,NSA,02-01,14-52-20,NEND:\" Internal failure\":,ISLTD"
__ 2.1 Does the system response list alarm conditions for the
MM?
__ 2.1.1 If there is an alarm condition against the

MM, go to Section 6, Troubleshooting the
Port Shelves, page 29-575, to
troubleshoot the MM.
__ 2.1.2 If there are no alarm conditions against

the MM, go to step 3, page 29-1003.
__ 3. Retrieve the VCG in alarm, and its members, by entering the following
command:
RTRV-VCG::VCG-xxxx-yyy:ctag;
Where: xxxx = Lead SDF number for the shelf.

yyy = Group number (101 - 600).
System response:
M ctag COMPLD

"VCG-0065-101:STS1:PMAID=MM24-0065,ALM=INH,ALMPF=4,MAP=ETHGFP,LCAS=ON,PLCR=1,PLCT=1,
HOTMR=ON,HOTIME=100, WTRTMR=ON, WTRTIME=300,MBRPROV=2,ADIPADDR=121.23.134.24,
ADMACADDR=6F-00-34-7C-00-21:PST=IS-ANR,SST=SENA"
"STS1-0065-01:::CCT=2WAY,ACTMBRRX=YES,ACTMBRTX=YES,RXSEQNUM=01,TXSEQNUM=01,
PST=IS-ANR"
PST=IS-ANR"
__ 3.1 If the primary state of the VCG is out-of-service, normal

(OOS-NR) or out-of-service, abnormal (OOS-ANR), go
76.5500/29, Rev R 7/07 Page 29-1003

__ 3.2 Determine if the SST (secondary state) of the VCG is

SENA.
__ 3.2.1 If the SST is not SENA, go to step 3.3,

page 29-1004.
__ 3.2.2 If the SST= SENA, there is a problem

with the supporting entity (VT-1 or
STS-1) for the VCG (Refer to Table 13.1,
page 29-1177.) Go to STS-1
Termination, page 29-919, to
troubleshoot the supporting STS-1. Go to
Virtual Tributary 1 Termination (VT1),
supporting VT-1.
__ 3.3 If any of the members of the VCG are abnormal (ANR),

go to STS1-Working Termination (STS1-W),
page 29-974, to troubleshoot the supporting STS-1. Go
to VT1-Working Termination (VT1-W), page 29-984, to
troubleshoot the supporting VT-1.
__ 3.4 If the primary state of the VCG is in-service, abnormal

__ 4. Verify that the VCG parameters are set correctly and edit the VCG
in-service (IS) using the following command. Then, go to step 6,
page 29-1005.
ED-VCG::VCG-xxxx-aaa:ctag:::vcg_parameters:IS;
Where: xxxx = Lead SDF number of the shelf.

aaa = Group number in the range (101 - 600).
VCG_parameters = VCG parameters. Refer to Tellabs 5500/5500S
Provisioning Manual, 76.5500/23, for a list of
parameter options.
System response:
M ctag COMPLD
__ 5. Verify that the VCG parameters are set correctly and edit the
parameters, if necessary, using the following command.
ED-VCG::VCG-xxxx-aaa:ctag:::vcg_parameters;
Where: xxxx = Lead SDF number of the shelf.

aaa = Group number in the range (101 - 600).
VCG_parameters = VCG parameters. Refer to Tellabs 5500/5500S
parameter options.
System response:
M ctag COMPLD
Page 29-1004 7/07 76.5500/29, Rev R

__ 6. Retrieve the VCG in alarm by entering the following command:

RTRV-VCG::VCG-xxxx-yyy:ctag;

System response:
M ctag COMPLD

"VCG-0065-101:STS1:PMAID=MM24-0065,ALM=INH,ALMPF=4,MAP=ETHGFP,LCAS=ON,PLCR=1,PLCT=1,
HOTMR=ON,HOTIME=100, WTRTMR=ON, WTRTIME=300,MBRPROV=2,ADIPADDR=121.23.134.24,
ADMACADDR=6F-00-34-7C-00-21:PST=IS-NR"
PST=IS-NR"
PST=IS-NR"
__ 6.1 If the present state of the VCG is in-service, normal

__ 6.2 If the present state of the VCG is not in-service, normal

(IS-NR), follow company procedures to verify that all
parameters are set correctly. Refer to Tellabs


M ctag COMPLD

M ctag COMPLD


message.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-1005

Ethernet (ETH) Termination

7.53 In this section, you will troubleshoot the Ethernet termination in alarm. You
__ 1. Retrieve all conditions against the Ethernet (ETH) termination by
RTRV-COND-ETH:::ctag;
System response:
M ctag COMPLD

"ETH-1-10-1,ETH:CR,LINKDN,SA,11-22,10-35-23,NEND,,,\"Link Down\""
"ETH-1-10-2,ETH:CR,ANEGFAIL,SA,11-22,10-35-23,NEND,,,\"AutoNegotiation Failure\""
__ 1.1 If the system response verifies that a "Link Down"

condition is posted against the ETH termination, there is
no signal detected at the physical layer. Go to Section
6, Troubleshooting the Port Shelves, page 29-575, to
troubleshoot the MIM96E or pluggable transceivers
(PTs).
__ 1.2 If the system response verifies that a "AutoNegotiation

Failure" condition is posted against the ETH
termination, the Ethernet rate and mode of the Tellabs
5500 system and its peer Ethernet interface are not
negotiating. Follow your company's prescribed

MIM96E or pluggable transceiver (PT)?

appropriate module.
Page 29-1006 7/07 76.5500/29, Rev R

__ 2. Retrieve the state of the ETH termination by entering the following

command:
RTRV-ETH::ETH-xxxx-ss-pp:ctag;

ss = MIM slot number (10 - 11).
pp = PT port number (1 - 4).
System response:
M ctag COMPLD

"ETH-362-10-1::ALM=ALW,ALMPF=4,MACADDR=08002002904C,ETHMODE=FDPLX,ETHRATE=1000,
FLOWCTRLRX=NO,FLOWCTRLTX=NO,FLOWCTRLAD=SPAUSE,AUTONEG=ON,AUTONEGSTAT=CMPLT,
AUTONEGRMTSGL=YES,GRPAID=LAG-362-1:PST=OOS-ANR,SST=SENA"
__ 2.1 If the system response shows SST=SENA, there is a

problem with the supporting entity (PT) for the ETH
termination. (Refer to Table 13.1, page 29-1177.) Go to
Pluggable Transceiver (PT), page 29-835, to
troubleshoot the supporting entity.
__ 2.2 If the present state of the ETH termination is

__ 2.3 If the present state of the ETH termination is in-service,

correctly.

page 29-1008.

76.5500/29, Rev R 7/07 Page 29-1007

__ 3. Verify that the ETH parameters are set correctly and place the
termination in-service (IS) by entering the following command:
Note: Refer to Tellabs 5500/5500S Provisioning Manual, 76.5500/23, for ETH

parameter options. If parameters are set incorrectly, use Tellabs
ED-ETH::ETH-xxxx-ss-pp:ctag:::eth_parameters:IS;

eth_parameters = Ethernet parameters. Refer to Tellabs
5500/5500S Provisioning Manual, 76.5500/23, for
a list of parameter options.
System response:
M ctag COMPLD
__ 4. Retrieve the state of the ETH termination by entering the following

command:
RTRV-ETH::ETH-xxxx-ss-pp:ctag;

System response:
M ctag COMPLD

"ETH-362-10-1::ALM=ALW,ALMPF=4,MACADDR=08002002904C,ETHMODE=FDPLX,ETHRATE=1000,
FLOWCTRLRX=NO,FLOWCTRLTX=NO,FLOWCTRLAD=SPAUSE,AUTONEG=ON,AUTONEGSTAT=CMPLT,
AUTONEGRMTSGL=YES,GRPAID=LAG-362-1:PST=IS-NR"
__ 4.1 Verify from the system response that the parameters

are set correctly. Refer to Tellabs 5500/5500S
Provisioning Manual, 76.5500/23, for parameter
options.

__ 4.2.1 If the termination is in-service, normal

__ 4.2.2 If the termination is not in-service, normal

(IS-NR), follow company procedures to
verify there is a valid incoming signal and
Provisioning Manual, 76.5500/23.
Page 29-1008 7/07 76.5500/29, Rev R


RTRV-COND-ETH:::ctag;
System response:
M ctag COMPLD

"ETH-1-10-1,ETH:CR,LINKDN,SA,11-22,10-35-23,NEND,,,\"Link Down\""
"ETH-1-10-2,ETH:CR,ANEGFAIL,SA,11-22,10-35-23,NEND,,,\"AutoNegotiation Failure\""
__ 5.1 Verify there are no conditions posted against the ETH

termination.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-1009

Ethernet Management (ETHMNG) Termination

7.54 In this section, you will troubleshoot the Ethernet management termination
in alarm. You should have completed System Pre-Checks, page 29-852, and been
__ 1. Retrieve all conditions against the Ethernet management (ETHMNG)
termination by entering the following command:
RTRV-COND-ETHMNG:::ctag;
System response:
M ctag COMPLD

"ETHMNG-1-10-1,ETHMNG:CR,LINKDN,SA,11-22,10-35-23,NEND,,,\"Link Down\""
"ETHMNG-1-10-2,ETHMNG:CR,ANEGFAIL,SA,11-22,10-35-23,NEND,,,\"AutoNegotiation
Failure\""

condition is posted against the ETHMNG termination,
there is no signal detected at the physical layer. Go to
page 29-575, to troubleshoot the MIM96E or pluggable
transceivers (PTs).
__ 1.2 If the system response verifies that a "AutoNegotiation

Failure" condition is posted against the ETHMNG
termination, the Ethernet rate and mode of the Tellabs
5500 system and its peer Ethernet interface are not
negotiating. Follow your company's prescribed

MIM96E or pluggable transceiver (PT)?

appropriate module.
Page 29-1010 7/07 76.5500/29, Rev R

__ 2. Retrieve the state of the ETHMNG termination by entering the

following command:
RTRV-ETHMNG::ETHMNG-xxxx-ss-1:ctag;

System response:
M ctag COMPLD

"ETHMNG-362-10-1::ALM=ALW,ALMPF=4,MACADDR=08-00-20-02-90-4C,ETHMODE=FDPLX,
ETHRATE=100,
FLOWCTRLRX=YES,FLOWCTRLTX=YES,FLOWCTRLAD=SPAUSE,AUTONEG=ON,AUTONEGSTAT=CMPLT,
AUTONEGRMTSGL=YES:PST=OOS-ANR,SST=SENA"

problem with the supporting entity (MIM) for the
ETHMNG termination. (Refer to Table 13.1,
page 29-1177). Go to Mapping Interface Module (MIM),
page 29-815, to troubleshoot the supporting entity.
__ 2.2 If the present state of the ETHMNG termination is

__ 2.3 If the present state of the ETHMNG termination is

in-service, abnormal (IS-ANR), follow company
procedure to verify valid incoming signal and that all

page 29-1012.

76.5500/29, Rev R 7/07 Page 29-1011

__ 3. Verify that the ETHMNG parameters are set correctly and place the
termination in-service (IS) by entering the following command:
Note: Refer to Tellabs 5500/5500S Provisioning Manual, 76.5500/23, for

ETHMNG parameter options. If parameters are set incorrectly, use Tellabs
ED-ETHMNG::ETHMNG-xxxx-ss-1:ctag:::eth_parameters:IS;

ethmng_parameters = Ethernet management parameters. Refer to
Tellabs 5500/5500S Provisioning Manual,
76.5500/23, for a list of parameter options.
System response:
M ctag COMPLD
__ 4. Retrieve the state of the ETHMNG termination by entering the

following command:
RTRV-ETHMNG::ETHMNG-xxxx-ss-1:ctag;

System response:
M ctag COMPLD

"ETHMNG-362-10-1::ALM=ALW,ALMPF=4,MACADDR=08-00-20-02-90-4C,ETHMODE=FDPLX,
ETHRATE=100,
FLOWCTRLRX=YES,FLOWCTRLTX=YES,FLOWCTRLAD=SPAUSE,AUTONEG=ON,AUTONEGSTAT=CMPLT,
AUTONEGRMTSGL=YES:PST=IS-NR"

are set correctly. Refer to Tellabs 5500/5500S
Provisioning Manual, 76.5500/23, for parameter
options.

__ 4.2.1 If the termination is in-service, normal

__ 4.2.2 If the termination is not in-service, normal

(IS-NR), follow company procedures to
verify there is a valid incoming signal and
Provisioning Manual, 76.5500/23.
Page 29-1012 7/07 76.5500/29, Rev R


RTRV-COND-ETHMNG:::ctag;
System response:
M ctag COMPLD

"ETHMNG-1-10-1,ETHMNG:CR,LINKDN,SA,11-22,10-35-23,NEND,,,\"Link Down\""
"ETHMNG-1-10-2,ETHMNG:CR,ANEGFAIL,SA,11-22,10-35-23,NEND,,,\"AutoNegotiation
Failure\""
__ 5.1 Verify there are no conditions posted against the

ETHMNG termination.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-1013

Link Aggregation Group (LAG)

7.55 In this section, you will troubleshoot the link aggregation group in alarm.
__ 1. Retrieve all conditions against the Link Aggregation Group (LAG) by
RTRV-COND-LAG:::ctag;
System response:
M ctag COMPLD

"LAG-1-1,LAG:MJ,TLC,SA,01-31,23-59-59,,,,\"Total Loss of Capacity\""
__ 1.1 If the system response verifies that a "Total Loss of

Capacity" condition is posted against the LAG, go to
step 2, page 29-1015.
MIM96E or an Ethernet (ETH) termination?

troubleshoot the MIM96E, or go to
Ethernet (ETH) Termination,
page 29-1006, to troubleshoot the ETH
termination.
Page 29-1014 7/07 76.5500/29, Rev R

__ 2. Retrieve the LAG in alarm by entering the following command:

RTRV-LAG::LAG-xxxx-aa:ctag;

aa = Group number (1 - 4).
System response:
M ctag COMPLD

"LAG-362-2:LAGTYPE=AGG:MACADDR=08-02-10-99-03-22,AGGRATE=2000,ETHRATE=1000000,
SUBSCRT=100,SUBLIMIT=1000000,CIRSUM=640,EIRSUM=2000,ALMPF=4,ALM=ALW:PST=IS-ANR,
SST-SENA"
"ETH-362-10-1:::PST=IS-NR"
"ETH-362-11-1:::PST=IS-NR"

problem with the supporting entity (ETH) for the LAG
termination. (Refer to Table 13.1, page 29-1177.) Go to
Ethernet (ETH) Termination, page 29-1006, to
troubleshoot the supporting entity.
__ 2.2 If the present states of the ETH terminations are

abnormal (ANR), the problem is with the ETH
terminations. Go to Ethernet (ETH) Termination,
page 29-1006.
__ 2.3 If the present states of the ETH terminations are

in-service, normal (IS-NR), what is the present state of
the LAG?
__ 2.3.1 If the present state of the LAG is

in-service, normal (IS-NR), go to step 5,
page 29-1016.

out-of-service, normal (OOS-NR) or
out-of-service, abnormal (OOS-ANR), go

in-service, abnormal (IS-ANR), follow
company procedure to verify valid
incoming signal and that all parameters
are set correctly. If parameters are
Provisioning Manual, 76.5500/23. Then
Note: Refer to Tellabs 5500/5500S Provisioning Manual, 76.5500/23, for LAG

76.5500/29, Rev R 7/07 Page 29-1015

__ 3. Verify that the LAG parameters are set correctly and edit the LAG
ED-LAG::LAG-xxxx-aa:ctag::::IS;

lag_parameters = LAG parameters. Refer to Tellabs 5500/5500S
parameter options.
System response:
M ctag COMPLD
__ 4. Retrieve the LAG in alarm by entering the following command:

RTRV-LAG::LAG-xxxx-aa:ctag;

System response:
M ctag COMPLD

"LAG-362-2:LAGTYPE=AGG:MACADDR=08-02-10-99-03-22,AGGRATE=2000,ETHRATE=1000000,
SUBSCRT=100,SUBLIMIT=1000000,CIRSUM=640,EIRSUM=2000,ALMPF=4,ALM=ALW:PST=IS-NR"
"ETH-362-10-1:::PST=IS-NR"
"ETH-362-11-1:::PST=IS-NR"
__ 4.1 If the present state of the LAG is in-service, normal

__ 4.2 If the present state of the LAG is not in-service, normal

(IS-NR), follow company procedures to verify there is a
Manual, 76.5500/23
__ 5. Retrieve all conditions against the Link Aggregation Group (LAG) by

RTRV-COND-LAG:::ctag;
System response:
M ctag COMPLD

"LAG-1-1,LAG:MJ,TLC,SA,01-31,23-59-59,,,,\"Total Loss of Capacity\""
__ 5.1 Verify that there are no alarm conditions listed against

the LAG.
End of Procedure
Page 29-1016 7/07 76.5500/29, Rev R

Point-to-Point Protocol (PPP) Termination

7.56 In this section, you will troubleshoot the point-to-point protocol termination
in alarm. You should have completed System Pre-Checks, page 29-852, and been
__ 1. Retrieve all conditions against the PPP termination by entering the
following command:
RTRV-COND-PPP:::ctag;
System response:
M ctag COMPLD

"PPP-0013-1,PPP:MN,LINKDN,NSA,01-31,23-59-59,NEND,,,\"Link Down\""

condition is posted against the PPP, there is no signal
detected at the physical layer. Go to Section 6,
troubleshoot the MM24E.
MM24E, T1 TRMINT termination, or PPPG?

MM24E, go to Section 6, Troubleshooting

T1 TRMINT, go to DS1 Di-Group,
Constituent, or Internal Termination (T1
DGR, CST, or TRMINT), page 29-897, to
troubleshoot the T1 internal termination.

PPPG, go to Point-to-Point Protocol
Group (PPPG), page 29-1020, to
troubleshoot the PPPG.

the MM24E, T1 TRMINT, or PPPG, go to
step 2, page 29-1018.
76.5500/29, Rev R 7/07 Page 29-1017

__ 2. Retrieve the PPP in alarm by entering the following command:

RTRV-PPP::PPP-xxxx-yy:ctag:::all;

yy = T1 termination (1 - 28).
System response:
M ctag COMPLD

"PPP-0065-01::PMAID=MM24-0065,CONFIG=INDVL,PPPGAID=PPPG-0065-101,
LCPSTATE=OPENED,ALM=ALW,ALMPF=99,MRUTC=1522,MRUT_NEG=1522,MRURC=1522,MRUR_NEG=1522,
LQRTC=OFF,LQRT_NEG=OFF,LQRTCINT=0,LQRTINT_NEG=0,LQRRC=OFF,LQRR_NEG=OFF,LQRRCINT=0,
LQRRINT_NEG=0,MAGNUMC=ON,MAGNUM_NEG=ON,FCSTC=16,FCST_NEG=16,FCSRC=16,FCSR_NEG=16,
RTIMER=3000,MAXTERM=2,MAXCNFG=10,MAXFAIL=5:PST=OOS-ANR,SST=SENA"

problem with the supporting entity (T1 TRMINT) for the
PPP termination. (Refer to Table 13.1, page 29-1177.)
Go to DS1 Di-Group, Constituent, or Internal
Termination (T1 DGR, CST, or TRMINT), page 29-897,
to troubleshoot the supporting entity.
__ 2.2 If the present state of the PPP is in-service, normal

__ 2.3 If the present state of the PPP is out-of-service, normal

(OOS-NR) or out-of-service, abnormal (OOS-ANR), go
__ 2.4 If the present state of the PPP is in-service, abnormal

(IS-ANR), follow company procedures to verify that all
parameters are set correctly. If parameters are
incorrectly set, go to Tellabs 5500/5500S Provisioning
Manual, 76.5500/23. Then go to step 4, page 29-1019.
Note: Refer to Tellabs 5500/5500S Provisioning Manual, 76.5500/23, for PPP

Page 29-1018 7/07 76.5500/29, Rev R

__ 3. Verify that the PPP parameters are set correctly and edit the PPP
ED-PPP::PPP-xxxx-yy:ctag::::IS;

ppp_parameters = PPP parameters. Refer to Tellabs 5500/5500S
parameter options.
System response:
M ctag COMPLD
__ 4. Retrieve the PPP in alarm by entering the following command:

RTRV-PPP::PPP-xxxx-yy:ctag:::all;

System response:
M ctag COMPLD

"PPP-0065-01::PMAID=MM24-0065,CONFIG=INDVL,PPPGAID=PPPG-0065-101,
LCPSTATE=OPENED,ALM=ALW,ALMPF=99,MRUTC=1522,MRUT_NEG=1522,MRURC=1522,MRUR_NEG=1522,
LQRTC=OFF,LQRT_NEG=OFF,LQRTCINT=0,LQRTINT_NEG=0,LQRRC=OFF,LQRR_NEG=OFF,LQRRCINT=0,
LQRRINT_NEG=0,MAGNUMC=ON,MAGNUM_NEG=ON,FCSTC=16,FCST_NEG=16,FCSRC=16,FCSR_NEG=16,
RTIMER=3000,MAXTERM=2,MAXCNFG=10,MAXFAIL=5:PST=IS-NR"
__ 4.1 If the present state of the PPP is in-service, normal

__ 4.2 If the present state of the PPP is not in-service, normal

5500/5500S Provisioning Manual, 76.5500/23
__ 5. Retrieve all conditions against the PPP termination by entering the

following command:
RTRV-COND-PPP:::ctag;
System response:
M ctag COMPLD

"PPP-0013-1,PPP:MN,LINKDN,NSA,01-31,23-59-59,NEND,,,\"Link Down\""

the PPP.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-1019

Point-to-Point Protocol Group (PPPG)

7.57 In this section, you will troubleshoot the point-to-point protocol group in
__ 1. Retrieve all conditions against the PPPG by entering the following
command:
RTRV-COND-PPPG:::ctag;
M ctag COMPLD

"PPPG-0013-101,PPPG:MN,BCPDWN,NSA,01-31,23-59-59,NEND,,,\"Bridge Control Protocol
Down\""
"PPPG-0014-101,PPPG:MN,RADCOMM,NSA,01-31,23-59-59,NEND,,,\"Remote Access Device

Communication Lost\""
"PPPG-0015-101,PPPG:MN,TLC,NSA,01-31,23-59-59,NEND,,,\"Total Loss of Capacity\""
__ 1.1 If the system response verifies that a "Bridge Control

Protocol Down" condition is posted against the PPPG,
__ 1.2 If the system response lists only a "Remote Access

Device Communication Lost" condition posted against
the PPPG, the Ethernet port shelf and remote access
device cannot communicate. Go to Verifying EPS to
MSA Connectivity, page 29-1023.
__ 1.3 If the system response verifies that a "Remote Access

Device Communication Lost" and "Total Loss of
Capacity" condition is posted against the PPPG, there
is a problem with the PPP termination associated with
the PPPG. Go to Point-to-Point Protocol (PPP)
MM24E or PPP?

MM24E, go to Section 6, Troubleshooting

PPP, go to Point-to-Point Protocol (PPP)
troubleshoot the PPP.

the MM24E or PPP, go to step 2,
page 29-1021.
Page 29-1020 7/07 76.5500/29, Rev R

__ 2. Retrieve the PPPG in alarm by entering the following command:

RTRV-PPPG::PPPG-xxxx-yyy:ctag;

System response:
M ctag COMPLD

"PPPG-0065-101::PMAID=MM24-0065,BCPSTATE=OPENED,ALM=INH,ALMPF=99,MAP=ETH,ML=ON,
MRRUTC=1552,MRRUT_NEG=1552,MRRURC=1552,MRRUR_NEG=1552,SSNTC=YES,SSNT_NEG=YES,
SSNRC=YES,
SSNR_NEG=YES,ADIPADDR=121.23.241.32,ADMACADDR=6F-00-AC-10-00-13:PST=IS-ANR,SST=SENA"
"PPP-0065-01::PST=IS-NR"
__ 2.1 If the system response for the PPPG shows

SST=SENA, there is a problem with the supporting
entity (PPP) for the PPPG termination. (Refer to Table
13.1, page 29-1177.) Go to Point-to-Point Protocol
(PPP) Termination, page 29-1017, to troubleshoot the
supporting entity.
__ 2.2 If the present states of the PPP termiantions are

abnormal (ANR), the problem is with the ETH
terminations. Go to Point-to-Point Protocol (PPP)
__ 2.3 If the present states of the PPP terminations are

in-service, normal (IS-NR), what is the present state of
the PPPG?
__ 2.3.1 If the present state of the PPPG is

in-service, normal (IS-NR), go to step 5,
page 29-1023.

out-of-service, normal (OOS-NR) or
out-of-service, abnormal (OOS-ANR), go

in-service, abnormal (IS-ANR), follow
company procedure to verify a valid
incoming signal and that all parameters
are set correctly. If parameters are
Provisioning Manual, 76.5500/23. Then
76.5500/29, Rev R 7/07 Page 29-1021

Note: Refer to Tellabs 5500/5500S Provisioning Manual, 76.5500/23, for LAG

__ 3. Verify that the PPPG parameters are set correctly and edit the PPPG
ED-PPPG::PPPG-xxxx-yyy:ctag:::pppg_parameters:IS;
Where:xxxx = Lead SDF number for the shelf.

pppg_parameters = PPPG parameters. Refer to Tellabs 5500/5500S
parameter options.
System response:
M ctag COMPLD
__ 4. Retrieve the PPPG in alarm by entering the following command:

RTRV-PPPG::PPPG-xxxx-yyy:ctag;

System response:
M ctag COMPLD

"PPPG-0065-101::PMAID=MM24-0065,BCPSTATE=OPENED,ALM=INH,ALMPF=99,MAP=ETH,ML=ON,
MRRUTC=1552,MRRUT_NEG=1552,MRRURC=1552,MRRUR_NEG=1552,SSNTC=YES,SSNT_NEG=YES,
SSNRC=YES,
SSNR_NEG=YES,ADIPADDR=121.23.241.32,ADMACADDR=6F-00-AC-10-00-13:PST=IS-NR"
__ 4.1 If the present state of the PPPG is in-service, normal

__ 4.2 If the present state of the PPPG is not in-service, normal

Page 29-1022 7/07 76.5500/29, Rev R

__ 5. Retrieve all conditions against the PPPG by entering the following

command:
RTRV-COND-PPPG:::ctag;
System response:
M ctag COMPLD

"PPPG-0013-101,PPPG:MN,BCPDWN,NSA,01-31,23-59-59,NEND,,,\"Bridge Control Protocol
Down\""

the PPPG.
Verifying EPS to MSA Connectivity

7.58 Verify connectivity between the Ethernet Port Shelf (EPS) and the Tellabs
8815 Multi-Service Access Node (MSA) by following the steps in this section.
__ 1. Retrieve the ETHINT to be used between the EPS and the MSA by
RTRV-ETHINT::ETHINT-xxxx-aaa&&aaa:ctag;
Where: xxxx = SDF number on the EPS.

aaa = Group number (101 - 600).
Example:
RTRV-ETHINT::ETHINT-609-122:ctag;
System response:
M ctag COMPLD

"ETHINT-609-122::ETHRATE=1536,SUBSCRT=100,POL=OFF,BWLIM=256,ABS=9728,
SUBLIMIT=1536,CIRSUM=0,EIRSUM=0,MNGVID=4094:PST=IS-NR"
Note: The MNGVID on the ETHINT must match the MNGVID on the Tellabs
8815 MSA. The Tellabs 8815 MSA's MNGVID defaults to 4094; therefore,
Tellabs recommends that the ETHINT's MNGVID be set to 4094.
__ 1.1 Confirm that the ETHINT's MNGVID matches the

Tellabs 8815 MSA.
__ 1.2 If ETHINT does not match the Tellabs 8815 MSA, go to

__ 1.3 If the ETHINT does match the Tellabs 8815 MSA, go to

76.5500/29, Rev R 7/07 Page 29-1023

__ 2. Edit the ETHINT termination to change the MNGVID to match the

Tellabs 8815 MSA by entering the following command:
ED-ETHINT::ETHINT-xxxx-aaa&&aaa:ctag:::MNGVID=4094;

Example:
ED-ETHINT::ETHINT-609-122:ctag:::MNGVID=4094;
System response:
M ctag COMPLD
__ 3. Retrieve the ETHINT termination by entering the following command:


Example:
System response:
M ctag COMPLD

"ETHINT-609-122::ETHRATE=1536,SUBSCRT=100,POL=DROP,BWLIM=256,ABS=9728,
__ 3.1 Verify from the system response that the MNGVID

matches the Tellabs 8815 MSA. Then, go to step 8,
page 29-1026.
__ 4. Edit the ETHINT termination to change the MNGVID to NONE by

ED-ETHINT::ETHINT-xxxx-aaa&&aaa:ctag:::MNGVID=NONE;

System response:
M ctag COMPLD
Page 29-1024 7/07 76.5500/29, Rev R



Example:
System response:
M ctag COMPLD

SUBLIMIT=1536,CIRSUM=0,EIRSUM=0,MNGVID=NONE:PST=IS-NR"
__ 5.1 Verify from the system response that the

MNGVID=NONE.
__ 5.2 Wait 5 Minutes for the MAC Address to clear out of

memory.
__ 6. Edit the ETHINT termination to change the MNGVID to match the

Tellabs 8815 MSA by entering the following command:
ED-ETHINT::ETHINT-xxxx-aaa&&aaa:ctag:::MNGVID=4094;

Example:
ED-ETHINT::ETHINT-609-122:ctag:::MNGVID=4094;
System response:
M ctag COMPLD


Example:
System response:
M ctag COMPLD

__ 7.1 Verify from the system response that the MNGVID

matches the Tellabs 8815 MSA.
76.5500/29, Rev R 7/07 Page 29-1025

__ 8. At a DOS prompt from a computer on the customer network, ping the

PPPG IP address (as configured on the Tellabs 8815 MSA) to confirm
connectivity:
Example:
ping 172.23.158.3

Reply from 172.23.158.3: bytes=32 time=15ms TTL=64
Ping statistics for 172.23.158.3:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 15ms, Average = 7ms
__ 8.1 If the ping is unsuccessful, perform the following steps:
__ 8.1.1 Confirm that the correct IP address was

entered.
__ 8.1.2 Return to step 1, page 29-1023, and

confirm that all steps were completed
properly.
__ 8.1.3 Follow your company's prescribed

assistance or contact Tellabs Technical
North America).
Page 29-1026 7/07 76.5500/29, Rev R

Troubleshooting Internal Path Integrity Errors (DS1 CST, DS1 DGR, VT1, or
VPG Termination)
7.59 In this section, troubleshoot an internal path integrity error received against
a DS1 CST, DS1 DGR, VT1, or VPG termination.
command:

M ctag COMPLD

M ctag COMPLD

__ 1.1 If internal path integrity errors are posted against both

Network Complexes, follow your company's prescribed
__ 1.2 If internal path integrity errors are posted against only

one Network Complex, choose one of the following
options:
__ 1.2.1 If the internal path integrity error is posted

against a T1 DGR or T1 CST, go to step
2, page 29-1028.
__ 1.2.2 If the internal path integrity error is posted

against a VT1 or VPG, go to step 3,
page 29-1028.
76.5500/29, Rev R 7/07 Page 29-1027

__ 2. Retrieve the path of the T1 that is posting an internal path integrity

error by entering the following command:
RTRV-PATH-T1::xxxx-yy:ctag;

yy = T1 being retrieved (1 - 28).
System response:
M ctag COMPLD

"0005-01,0007-04:TSI11-0005-A,ESM-0001-A,CSM-0001-A,ESM-0001-A,TSI11-0009-A:CCT=1WAY
,CCSTATE=IDLE"
"0005-01,0007-04:TSI11-0005-B,ESM-0001-B,CSM-0001-B,ESM-0001-B,TSI11-0009-B:CCT=1WAY
,CCSTATE=IDLE"
Note: In a system with a Hybrid Core Switch, the system response to step 2 may
list CAMs.
__ 2.1 Note the locations of the modules in the path of the T1

termination that is posting the internal path integrity
error. Continue to step 4.
__ 3. Retrieve the path of the VT1 or VPG that is posting an internal path
integrity error by entering one of the following commands:
RTRV-PATH-VT1::VT1-xxxx-y-z:ctag;
RTRV-PATH-VPG::VPG-xxxx-y-z:ctag;
Where: xxxx = SDF number being retrieved.

y = VT group (1 - 7).
System response:
M ctag COMPLD

"VT1-0005-01-01,VT1-0007-04-01:TSI11-0005-A,ESM-0001-A,CSM-0001-A,ESM-0001-A,
TSI11-0009-A:CCT=1WAY,CCSTATE=IDLE"
"VT1-0005-01-01,VT1-0007-04-01:TSI11-0005-B,ESM-0001-B,CSM-0001-B,ESM-0001-B,
TSI11-0009-B:CCT=1WAY,CCSTATE=IDLE"
__ 3.1 Note the locations of the modules in the path of the VT1
or VPG termination that is posting the internal path
integrity error. Continue to step 4, page 29-1029.
Page 29-1028 7/07 76.5500/29, Rev R

__ 4. Remove the TSI module that is the first stage of the five stage network.
__ 4.1 If you are removing a TSI96/P, disconnect the
intra-system fibers from the front of the TSI96/P before
removing the module from the shelf.

place.

troubleshooting.
__ 7. Wait approximately two minutes for the internal path integrity error
condition to clear.
__ 7.1 If the internal path integrity error condition clears, go to
step 20, page 29-1031.
__ 7.2 If the internal path integrity error condition does not

clear, continue to the next step.
__ 8. Remove the ESM that is the second stage of the five stage network.
place.

troubleshooting.
condition to clear.
step 20, page 29-1031.

76.5500/29, Rev R 7/07 Page 29-1029

__ 12. Remove the CSM or CAM that is the third stage of the five stage
network.
__ 12.1 If you are removing a CAM, disconnect the fibers from
the front panel of the module.

place.

troubleshooting.
condition to clear.
step 20, page 29-1031.

__ 16. Remove the ESM that is the fourth stage of the five stage network.
place.

troubleshooting.
condition to clear.
step 20, page 29-1031.

clear, follow your company's prescribed procedures for
Page 29-1030 7/07 76.5500/29, Rev R

command:

M ctag COMPLD

M ctag COMPLD

__ 20.1 Verify that no internal path integrity errors are being

posted.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-1031

USER NOTES
Page 29-1032 7/07 76.5500/29, Rev R

Troubleshooting Manual 8. Troubleshooting VQE and DS0 Grooming Functionality
8. Troubleshooting VQE and DS0 Grooming Functionality
8.01 In this section, troubleshoot Voice Quality Enhancement (VQE) and DS0
grooming (NB) functionality.
command:
RTRV-STS1::STS1-xxxx:ctag:::DETAILS=YES;
Where: xxxx = SDF of the STS-1.
System response:
M ctag COMPLD

PSLT=VTFLOAT,FLTPR=DISABLED,PASUSP=OFF,PARTNAME=UASPART,APPL=VQE/NB:PST=OOS-NR"
__ 1.1 Does the system response show that the STS-1 is

capable of supporting VQE or DS0 grooming
functionality (APPL=VQE or APPL=NB)?
__ 1.1.1 If APPL=VQE, go to Troubleshooting

VQE Functionality.
__ 1.1.2 If APPL=NB, go to Troubleshooting DS0

Functionality, page 29-1045.
Troubleshooting VQE Functionality

__ 1. Retrieve the present state of all entities on the port shelf by entering
Where: xxxx = First SDF number on the port shelf.
System response:
M ctag COMPLD

"PGCU-0513:TYPE=UVQE:ALMPF=99,VQECONFIG=INLINE/LOOP,VQEAPPL=WIRELESS,VQEEPT=255:
PST=NR"
"PGCU-0513-A:TYPE=UVQE:HWV=81.5591 RF,SN=LI0462863,DT=000105:PST=IS-NR-ACT"
"PGCU-0513-B:TYPE=UVQE:HWV=81.5591 RG,SN=LI5718448,DT=971124:PST=IS-NR-STBY"
"MM24-0065:TYPE=MM24VE:HWV=81.5595VE RA,SN=LI5717878,DT=051027,ALMPF=99,
VQEBYPASS=OFF:PST=IS-NR-ACT"
76.5500/29, Rev R 7/07 Page 29-1033

8. Troubleshooting VQE and DS0 Grooming Functionality Troubleshooting Manual
__ 1.1 Verify that the port shelf type is configured for VQE
(TYPE=UVQE).
__ 1.1.2 If no, refer to Tellabs 5500/5500S VQE

Operations Manual, 76.5500/56, to
correct the shelf type setting.
__ 1.2 Verify that the port shelf is configured for the correct
VQE configuration of inline or loop
(VQECONFIG=INLINE/LOOP).
__ 1.2.1 If the port shelf is configured for the

correct VQE configuration, go to
substep 1.3.
__ 1.2.2 If the port shelf is not configured for the

correct VQE configuration, go to Tellabs
5500/5500S VQE Operations Manual,
76.5500/56, to resolve the issue.
__ 1.3 For an MM24V module, verify that the VQE application

is set correctly to wireless or wireline
(VQEAPPL=WIRELESS/WIRELINE).
__ 1.3.1 If the VQEAPPL is set correctly, continue

to substep 1.4.
__ 1.3.2 If the VQEAPPL is not set correctly, refer

to Tellabs VQE Operations Manual,
76.5500/56.
Note: An MM24VE module can only be configured as wireless.
__ 1.4 Are you receiving a DENY message while attempting to

enter an STS-1?
__ 1.4.2 If yes, verify from the system response

that the end path type setting
(VQEEPT=128/255) is supported by the
MM type (TYPE=MM24V/MM24VE).
Note: For an MM24V, the supported end path type setting is 128 ms.
For an MM24VE, the supported end path type settings are 128 ms and
255 ms.
The type setting controls how many SDFs can perform VQE functions and
what the maximum end path option can be set for at the STS-1 level, not
the actual end path delay configuration.
Page 29-1034 7/07 76.5500/29, Rev R

__ 2. Verify that the STS is supported by the module type and that the
cross-connect you are attempting to enter adheres to the SDF
mapping configuration for the VQEPS. For more information on SDF
mapping for the VQEPS, refer to Tellabs 5500/5500S VQE Operations
Manual, 76.5500/56.
Refer to the following figures for graphical representations of the inline
and loop around configurations:
- Figure 8.1 shows an inline configuration with MM24V modules.
- Figure 8.2, page 29-1036, shows an inline configuration with
MM24VE modules
- Figure 8.3, page 29-1036, shows a loop around configuration with
MM24V modules.
- Figure 8.4, page 29-1037, shows a loop around configuration with
MM24VE modules.
- Figure 8.5, page 29-1038, shows an in-line configuration with
OPM12X4 and MM24VE modules.
- Figure 8.6, page 29-1039, shows a loop-around configuration with
OPM12X4 and MM24VE modules.
Figure 8.1 In-Line Configuration SDF Management with the MM24V
76.5500/29, Rev R 7/07 Page 29-1035

Figure 8.2 In-Line Configuration SDF Management with the MM24VE
Figure 8.3 Loop-Around Configuration SDF Management with the MM24V
Page 29-1036 7/07 76.5500/29, Rev R

Figure 8.4 Loop-Around Configuration SDF Management with the MM24VE
76.5500/29, Rev R 7/07 Page 29-1037

Figure 8.5 VQE In-Line Mapping - Extended 255 ms Endpath with OPM12x4
SDF 1 - 3 SDF 1 - 3
Not Available (4-6) Not Available (4-6)
SDF 31 - 33
SDF 7 - 12
Not Available (34-36)
SDF 61 - 63 SDF 13 - 18

SDF 19 - 24
EPMx24/ SDF 91 - 93
OPM3x8 MM24VE-1
SDF 25 - 30
SDF 31 - 33
SDF 7 - 12 Not Available (34-36)
SDF 13 - 18 SDF 37 - 42
SDF 19 - 24
EPMx24/ SDF 43 - 48
OPM3x8
(non-VQE) SDF 25 - 30 MM24VE-25
SDF 49 - 54
SDF 37 - 42
SDF 55 - 60
SDF 43 - 48 SDF 61 - 63

SDF 49 - 54
SDF 67 - 72
OPM12x4 SDF 55 - 60
(non-VQE) MM24VE-25
SDF 67 - 72
SDF 73 - 78
SDF 73 - 78
SDF 79 - 84
SDF 79 - 84
SDF 85 - 90
SDF 85 - 90
SDF 91 - 93
MM24VE-73
MIM96
Note: Non-VQE SDFs are mapped

to the last two protection groups.
Page 29-1038 7/07 76.5500/29, Rev R

Figure 8.6 VQE Loop-Around Mapping - Extended 255 ms Endpath with OPM12x4
SDF 1 - 3
Not Available (4-6)
SDF 7 - 9
SDF 13 - 18
Filler
SDF 19 - 24
MM24VE-1
SDF 25 - 30
SDF 31 - 36
SDF 37 - 39
Filler
SDF 43 - 45
MM24VE-25
SDF 13- 18
SDF 49 - 51
SDF 19- 24
SDF 25 - 30 SDF 55 - 57
SDF 31 - 36 Not Available (58-60)
OPM12x4 SDF 61 - 66 SDF 61 - 66

(non-VQE)
SDF 67 - 72
SDF 67 - 72
SDF 73 - 78 MM24VE-49
SDF 79 - 84
SDF 73 - 78
SDF 79 - 84
SDF 85 - 87
SDF 91 - 93
MM24VE-73
MIM96
Note: Non-VQE SDFs are mapped

to the last two protection groups.
76.5500/29, Rev R 7/07 Page 29-1039


command:
Where: xxxx = SDF number of the alarmed STS-1.
System response:
M ctag COMPLD

__ 3.1 Verify that the present state is in-service, normal

(IS-NR).
__ 3.2 Verify that STSMAP=VTFLOAT.
__ 3.2.2 If no, refer to Tellabs 5500/5500S VQE

Operations Manual, 76.5500/56, to
configure the STS-1 for VTFLOAT.
__ 4. Determine whether the MM24V or MM24VE is in bypass mode by

Where: xxxx = Lead SDF of the MM24V/MM24VE.
System response:
M ctag COMPLD

"MM24-0001:TYPE=MM24V:HWV=81.5595V,SN=PE12345678,DT=050825,ALMPF=99,VQEBYPASS=ON:
PST=IS-NR-ACT"
__ 4.1 If VQE bypass is on (VQEBYPASS=ON), go to Tellabs

VQE Operations Manual, 76.5500/56, to turn off VQE
bypass.
__ 4.2 If VQE bypass is off (VQEBYPASS=OFF), go to step 5.
Page 29-1040 7/07 76.5500/29, Rev R

__ 5. Are the STS-1s that are configured for VQE performing echo
cancellation properly?
__ 5.1 If yes, this procedure is complete.
__ 5.2 If no, retrieve the VQE settings for the STS-1 by

RTRV-VQE-STS1::STS1-xxxx:ctag;
Where: xxxx = SDF number serving the STS-1.
System response:
M ctag COMPLD

"STS1-0646::HEC=ON,SDST=ON,NLP=ON,EPDS=128,ERL=0,ADTMF=OFF,DTD=G165,DTDR=HOLDV,
STD=C6,RTAC=25,RTLC=18,RTNR=OFF,STLC=18,STAG=OFF,RDST=DST,RBTD=ON,STAC=25,STACD=360"
__ 5.3 For hybrid echo, verify from the system response that
hybrid echo cancellation is enabled (HEC=ON).
__ 5.3.1 If HEC=ON, verify from the system

response that the end path delay setting
is set appropriately (EPDS=64/128 or
EPDE=64/128/192/255).
Note: If the shelf is populated with MM24Vs, the supported end path delay
settings (EPDS) for the STS-1 are 64 ms and 128 ms.
If the shelf is populated with MM24VEs, the supported end path delay
settings (EPDE) for the STS-1 are 64 ms, 128 ms, 192 ms, and 255 ms.
__ 5.3.2 If HEC=OFF, enable hybrid echo

cancellation by entering the following
command:
ED-VQE-STS1::STS1-xxxx:ctag:::HEC=ON;
Where: xxxx = SDF number serving the STS-1.
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-1041

__ 5.4 For acoustic echo, verify from the system response that
acoustic echo cancellation is enabled (RTAC=25/35).
__ 5.4.1 If RTAC=25/35, go to step 5.5.
__ 5.4.2 If RTAC=OFF, enable acoustic echo

cancellation by entering the following
command:
ED-VQE-STS1::STS1-xxxx:ctag:::RTAC=rcv_acoustic;
Where: xxxx = The SDF number serving the STS-1.

rcv_acoustic = Enter 25 to specify processing acoustic echo
return loss of at least 25 dB.
Enter 35 to specify processing acoustic echo
System response:
M ctag COMPLD
__ 5.5 If you are troubleshooting VQE for wireless

applications, proceed to step 5.6. Otherwise, proceed to
step 6, page 29-1043.
__ 5.6 For acoustic echo in the send path in wireless

applications, verify from the system response send-side
TAC is enabled (STAC=25/35).
__ 5.6.1 If STAC=25/35, go to step 5.7.
__ 5.6.2 If STAC=OFF, enable send-side TAC by

ED-VQE-STS1::STS1-xxxx:ctag:::STAC=send_acoustic;

send_acoustic = Enter 25 to specify processing acoustic echo
Enter 35 to specify processing acoustic echo
System response:
M ctag COMPLD
Page 29-1042 7/07 76.5500/29, Rev R

__ 5.7 For acoustic echo delay in the send path in wireless

applications, verify from the system response that
send-side TAC delay is enabled (STACD=360/420).
__ 5.7.1 If STACD=360/420, go to step 6.
__ 5.7.2 If STACD=OFF, enable send-side TAC

delay by entering the following
command:
ED-VQE-STS1::STS1-xxxx:ctag:::STACD=send_acoustic_d
elay;

send_acoustic_delay = 360 identifies 180ms to 360ms delay.
420 identifies 180ms to 420ms delay.
System response:
M ctag COMPLD
__ 6. Verify the following:

__ 6.1 Verify that the correct STS-1s are cross-connected.
__ 6.2 Verify that line and drop are not reversed. To determine
whether the line and drop addresses are correct, go to
step 7.
__ 6.3 Verify that the correct STS-1/T1/DS0 is being

monitored.
__ 6.4 If you have verified the issues listed above and trouble
persists, go to step 8, page 29-1044.
__ 7. Retrieve the VQE cross-connects by entering the following command:

RTRV-CRS-VQE:::ctag;
Sample system response when cross-connects are configured:

M ctag COMPLD

"DROP=0209-7,LINE=0101-02:CCT=2WAY,ALTMAP=NO,CCSTATE=IDLE:APPL=VQE"
"DROP=0209-11,LINE=0101-03:CCT=2WAY,ALTMAP=NO,CCSTATE=IDLE,TAP=220:APPL=VQE:,
SST=RDLD"
Sample system response when cross-connects are not configured:

M ctag COMPLD
__ 7.1 Verify from the system response that line and drop
76.5500/29, Rev R 7/07 Page 29-1043

__ 7.2 Are the cross-connects configured correctly?
__ 7.2.2 If no, follow company procedures to

determine if company records show the
provisioning status of the STS-1. Refer to
Tellabs 5500/5500S VQE Operations
Manual, 76.5500/56, to provision the
STS-1; then go to step 8.
__ 8. Determine whether echo cancellation is being bypassed at the

channel level by entering the following command:
RTRV-VQE-T1::xxxx-yy:ctag;
Where: xxxx = SDF number serving the T1.

yy = T1 termination number (1 - 28).
System response:
M ctag COMPLD

"0646-1-2::CHANF=NR,CHANCM=IT,CASD=AND,IDLED=AND,IDLECS=XF,IDLECR=XF"
__ 8.1 If the system response shows CHANF=NR, the echo

cancellation is not being bypassed. Go to step 9.
__ 8.2 If the system response shows CHANF=BYPASS, the

echo cancellation is being bypassed. Go to Tellabs
VQE Operations Manual, 76.5500/56, to turn off VQE
bypass.
__ 9. Verify that echo cancellation is not being bypassed at the signal level.
Echo cancellation can be bypassed at the signal level due to the
following events:
- signal alarm
- tone detection
- signaling/idle code
__ 10. If you have completed all VQE troubleshooting procedures and trouble
persists, follow your company's prescribed procedures for obtaining
America).
End of Procedure
Page 29-1044 7/07 76.5500/29, Rev R

Troubleshooting DS0 Functionality

__ 1. Retrieve the present state of all entities on the port shelf by entering
System response:
M ctag COMPLD

"PGCU-0513:TYPE=UNB:ALMPF=99,DS0CONFIG=INLINE/LOOP:PST=NR"
"PGCU-0513-A:TYPE=UNB:HWV=81.5591 RF,SN=LI0462863,DT=000105:PST=IS-NR-ACT"
"PGCU-0513-B:TYPE=UNB:HWV=81.5591 RG,SN=LI5718448,DT=971124:PST=IS-NR-STBY"
__ 1.1 Verify that the port shelf type is configured for DS0
grooming (TYPE=UNB).
__ 1.1.2 If no, refer to Tellabs 5500/5500S

Provisioning Manual, 76.5500/23, to
correct the shelf type setting.
__ 1.2 Verify that the port shelf is configured for the correct
DS0 grooming configuration of inline or loop around
(DS0CONFIG=INLINE/LOOP).
__ 1.2.1 If the port shelf is configured for the

correct DS0 grooming configuration, go
to step 2.
__ 1.2.2 If the port shelf is not configured for the

correct DS0 grooming configuration, go
to Tellabs 5500/5500S Provisioning
Manual, 76.5500/23.
__ 2. Are you receiving a DENY message while attempting to enter a

cross-connect on the NBPS?
__ 3. Verify that the cross-connect you are attempting to enter adheres to

the SDF mapping configuration for the NBPS. For more information on
SDF mapping for the NBPS, refer to Tellabs 5500/5500S Provisioning
Manual, 76.5500/23.
Refer to Figure 8.7, page 29-1046, for a graphical representation of
the inline configuration and to Figure 8.8, page 29-1046, for a
graphical representation of the loop around configuration.
76.5500/29, Rev R 7/07 Page 29-1045

Figure 8.7 In-Line Configuration SDF Management for NBPS
Figure 8.8 Loop-Around Configuration SDF Management for NBPS
Page 29-1046 7/07 76.5500/29, Rev R

__ 4. If the NBS is configured for in-line, go to step 5. If the NBS is

configured for loop-around, go to step 6.
__ 5. Retrieve alarms for the DS0 midpoint terminations (T1INT) by entering
Note: T1INT terminations are implicitly created when the supporting T1 CST is
created.
RTRV-ALM-T1::T1INT-xxxx-y-z&&-z:ctag:
Where: xxxx = Is in the 1 - network_size range (e.g., 1024).

y = Is in the 1 - 7 range.
z = Is in the 1 - 4 range.
M ctag COMPLD

M ctag COMPLD

"T1INT-513-1-1,T1:MJ,RED,SA,05-09,20-47-23,NEND:\"AIS Alarm\":,AIS"
__ 5.1 Does the system response list alarms for the T1INT
terminations?
__ 5.1.1 If yes, go to T1 Internal (T1INT)

troubleshoot the T1INT terminations.
__ 6. Retrieve alarms for the T1 VTCST by entering the following command:

RTRV-ALM-T1::xxxx-yy-z:ctag;
Where: xxxx = SDF of the alarmed T1. (1 - network size range

(for example, 1024)).
yy = Port number of the T1. (1 - 7).
z = (1 - 4).
M ctag COMPLD

M ctag COMPLD

M ctag COMPLD
"0001-01,T1:MJ,RED,SA,05-09,20-47-23,NEND:\"Supporting Entity Not Available from
Cross-connected Side\":,SENA"
;
76.5500/29, Rev R 7/07 Page 29-1047

__ 7. Verify the DS0 cross-connects are configured by entering the following

command:
RTRV-CRS-DS0::{ds0_aid_from|ds0_aid_to}:ctag;
Where:
ds0_aid_from = Specifies the DS0:
Enter DS0-xxxx-y-z-ww for DS0 on the port side,
where xxxx, is the lead SDF number.
y (1 thru 7) is the VT1 group, z (1 thru 4) is the VT1
number.
ww (1 thru 24) is the DS0 channel.
Enter DS0INT-xxxx-y-z-ww for DS0 on the
network side, where xxxx, is the lead SDF
number.
y (1 thru 7) is the VT1 group.
z (1 thru 4) is the VT1 number, and ww (1 thru 24)
is the DS0 channel.
Enter DS0|DS0INT-xxxx-y-z-ww&&-ww format to
specify a range.
ds0_aid_to = Specifies the DS0:
Enter DS0-xxxx-y-z-ww for DS0 on the port side,
where xxxx, is the lead SDF number.
y (1 thru 7) is the VT1 group, z (1 thru 4) is the VT1
number.
ww (1 thru 24) is the DS0 channel.
Enter DS0INT-xxxx-y-z-ww for DS0 on the
network side, where xxxx, is the lead SDF
number.
y (1 thru 7) is the VT1 group.
z (1 thru 4) is the VT1 number, and ww (1 thru 24)
is the DS0 channel.
Enter DS0|DS0INT-xxxx-y-z-ww&&-ww format to
specify a range.
System response:
M ctag COMPLD

"FROM=DS0INT-0209-07-03-04,T0=DS0INT-0201-02-04-01:CCSTATE=XC,DS0TC=TRSP,DS0TW=FF"
"FROM=DS0INT-0201-01-01-08,TO=DS0-0203-03-02-06:CCSTATE=XC,DS0TC=0011-0011,DS0TW=7F
::,SST=RDLD"
__ 7.1 If cross-connects are configured, follow company

provisioning status of the STS-1. Refer to Tellabs
provision the STS-1.
__ 7.2 If cross-connects are not configured, refer to Tellabs

5500 Narrowband Operations, 76.5500/59, to provision
the cross-connections.
Page 29-1048 7/07 76.5500/29, Rev R

__ 8. If you have completed all DS0 grooming troubleshooting procedures

and trouble persists, follow your company's prescribed procedures for
obtaining technical assistance or call Tellabs Technical Assistance at
America).
Troubleshooting Relational Port Alarming
Note: The relational port alarming feature is available in the Tellabs 5500 system
FP11.0.1.
8.02 Relational Port Alarming is a feature that logically associates two

terminations such that when one termination goes into alarm, the other associated
(related) termination automatically transmits AIS. The Tellabs 5500 system
supports relational port alarming for T1 VTCST and T1INT terminations for which
the DS1 path is terminated on the iDS0 shelf.
8.03 Figure 8.9, page 29-1050, shows an example of relational port alarming
using the loop-around configuration with a narrowband port shelf. Figure 8.10,
page 29-1050, shows an example of relational port alarming using the in-line
configuration. The termination detecting the alarm is the source termination. The
related termination is the destination termination. When the source termination
detects local alarms (for example, LOF and LOS), the related destination
termination automatically transmits unframed AIS.
8.04 Use the ED-T1::::::VTCST command to configure relational port alarming.
For information about configuring relational port alarming, refer to Tellabs 5500
Narrowband Operations, 76.5500/59.
8.05 The configuration information for each port configured for relational port
alarming can be retrieved using the RTRV-T1 command.
76.5500/29, Rev R 7/07 Page 29-1049

Figure 8.9 Example of Relational Port Alarming in iDS0 Shelf with Loop-Around Configuration
legacy T1 T1 legacy
port T1 T1 port
shelf switch fabric shelf
T1 VTCST T1 VTCST 807-5-1 (RPAAID)

801-01-01 designated as related port and
configured as SRC; is automatically configured as
detects local alarms DEST; transmits unidirectional
unframed AIS
iDS0 port shelf
Figure 8.10 Example of Relational Port Alarming in iDS0 Shelf with In-Line Configuration
legacy T1
port
shelf T1 switch fabric
T1 INT-513-1-1 (RPAAID) designated as

related port and is automatically configured as
2WAY; transmits unidirectional unframed AIS
and detects local alarms
iDS0 port shelf
T1 VTCST 514-1-1 configured as 2WAY;

detects local alarms and transmits
unidirectional unframed AIS
T1 T1
customer
traffic
Page 29-1050 7/07 76.5500/29, Rev R

8.06 If relational port alarming has been configured, but a failure is suspected
and the remote equipment is not detecting AIS, follow the steps below.
__ 1. Retrieve the configuration of the DS0 port shelf by entering the
following command:
System response:
M ctag COMPLD

"PGCU-0513:TYPE=UNB:ALMPF=99,DS0CONFIG=INLINE/LOOP:PST=NR"
"PGCU-0513-A:TYPE=UNB:HWV=81.5591 RF,SN=LI0462863,DT=000105:PST=IS-NR-ACT"
"PGCU-0513-B:TYPE=UNB:HWV=81.5591 RG,SN=LI5718448,DT=971124:PST=IS-NR-STBY"
__ 1.1 If the port shelf is configured for LOOP, go to step 2.
__ 1.2 If the port shelf is configured for INLINE, go to step 4,

page 29-1055.
Note: Refer to Figure 8.9, page 29-1050, for an example of relational port
alarming in an iDS0 shelf with a loop-around configuration.
__ 2. Retrieve the T1VTCST by entering the following command:

RTRV-T1::xxxx-y-z:ctag;

y = (1 - 7).
z = (1 - 4).
Example:
RTRV-T1::801-01-01:ctag
System response:
M ctag COMPLD

"0801-1-1:VTCST:PMAID=MM24-0801,FMT=SF,GOS=99,ALM=ALW,ALMPF=99,
FENDPMTYPE=ANSI403,PASUSP=OFF[,RPA=rpa_config,[RPAAID=0807-5-1]],PARTNAME=UASPART:
PST=IS-ANR"
76.5500/29, Rev R 7/07 Page 29-1051

Where:
rpa_config = Specifies the configuration of relational port
alarming for a termination.
SRC specifies that the termination is the source
for unidirectional relational port alarming. The
source detects local alarms.
DEST specifies that the termination is the
destination for unidirectional relational port
alarming. The destination transmits AIS.
2WAY specifies that the termination can both
detect local alarms and transmit AIS.
OFF specifies that relational port alarming is
disabled on the termination.
The system default is OFF.
RPAAID = Specifies the AID of the related termination used
for relational port alarming. The behavior of the
RPAAID is automatically configured based on the
configuration of RPA. Refer to Table 8.1.
Table 8.1 RPA and RPAAID Relationship

If RPA is configured as: RPAAID is automatically configured as:
SRC (detects local alarms) DEST (transmits AIS)
DEST (transmits AIS) SRC (detects local alarms)
2WAY (detects local alarms and 2WAY (detects local alarms and transmits AIS)
transmits AIS)
OFF (no RPA) OFF (no RPA)
__ 2.1 Note the AID of the related termination (RPAAID).
__ 2.2 If the RPA=SRC or RPA=DEST, go to step 3,

page 29-1053.
__ 2.3 If RPA=OFF, refer to Tellabs 5500 Narrowband

Operations, 76.5500/59, for the procedure to configure
relational port alarming.
__ 2.4 If RPA=2WAY, verify that the correct RPAAID has been

used for relational port alarming.
__ 2.4.1 If necessary, refer to Tellabs 5500

Narrowband Operations, 76.5500/59, to
reconfigure relational port alarming using
the correct RPAAID.
__ 2.4.2 If the correct RPAAID was used, follow

Page 29-1052 7/07 76.5500/29, Rev R

__ 3. Retrieve the related T1VTCST (refer to step 2.1, page 29-1052) by


y = (1 - 7).
z = (1 - 4).
Example:
RTRV-T1::807-5-1:ctag
System response:
M ctag COMPLD

"0807-5-1:VTCST:PMAID=MM24-0807,FMT=SF,GOS=99,ALM=ALW,ALMPF=99,
FENDPMTYPE=ANSI403,PASUSP=OFF[,RPA=rpa_config,[RPAAID=0801-1-1]],PARTNAME=UASPART:
PST=IS-ANR"
Where:


transmits AIS)
76.5500/29, Rev R 7/07 Page 29-1053

__ 3.1 Verify that the correct AID appears for the related
termination (RPAAID). If the incorrect AID appears,
refer to Tellabs 5500 Narrowband Operations,
76.5500/59, to reconfigure relational port alarming
using the correct AID.
__ 3.2 If the RPA=SRC, the termination will be the source for

unidirectional relational port alarming. The RPAAID will
automatically be configured as DEST. Refer to
Table 8.2. If the RPAAID has not been configured to
transmit AIS in the correct direction, refer to Tellabs
5500 Narrowband Operations, 76.5500/59.
__ 3.3 If the RPA=DEST, the termination will be the destination

for unidirectional relational port alarming. The RPAAID
will automatically be configured as SRC. Refer to
transmit AIS is the correct direction, refer to Tellabs
__ 3.4 If RPA=OFF refer to Tellabs 5500 Narrowband



the correct RPAAID.
__ 3.5.2 If the correct RPAAID was used, and the

AIS is not detected on the remote
equipment, follow your company's
Page 29-1054 7/07 76.5500/29, Rev R

Note: Refer to Figure 8.10, page 29-1050, for an example of relational port
alarming in an iDS0 shelf with a in-line configuration.
__ 4. Retrieve the T1VTCST by entering the following command:


y = (1 - 7).
z = (1 - 4).
Example:
RTRV-T1::513-01-01:ctag
System response:
M ctag COMPLD

"0514-1-1:VTCST:PMAID=OPM3-W-0514,FMT=SF,GOS=99,ALM=ALW,ALMPF=99,
FENDPMTYPE=ANSI403,PASUSP=OFF[,RPA=rpa_config,[RPAAID=TIINT-0513-1-1]],
Where:


transmits AIS)
76.5500/29, Rev R 7/07 Page 29-1055

__ 4.1 Note the AID of the related termination (RPAAID).
__ 4.2 If the RPA=SRC or RPA=DEST, go to step 5.



the correct RPAAID.
__ 4.4.2 If the correct RPAAID was used, follow

__ 5. Retrieve the related T1INT (refer to step 4.1, page 29-1056) by


y = (1 - 7).
z = (1 - 4).
Example:
RTRV-T1::T1INT-513-1-1:ctag
System response:
M ctag COMPLD

FENDPMTYPE=ANSI403,PASUSP=OFF[,RPA=rpa_config,[RPAAID=514-1-1]],PARTNAME=UASPART
:PST=IS-ANR"
Page 29-1056 7/07 76.5500/29, Rev R

Where:

transmits AIS)
__ 5.1 Verify that the correct AID appears for the related
termination (RPAAID). If the incorrect AID appears,
refer to Tellabs 5500 Narrowband Operations,
76.5500/59, to reconfigure relational port alarming
using the correct AID.
__ 5.2 If the RPA=SRC, the termination will be the source for

unidirectional relational port alarming. The RPAAID will
automatically be configured as DEST. Refer to
transmit AIS in the correct direction, refer to Tellabs
__ 5.3 If the RPA=DEST, the termination will be the destination

for unidirectional relational port alarming. The RPAAID
will automatically be configured as SRC. Refer to
transmit AIS is the correct direction, refer to Tellabs

76.5500/29, Rev R 7/07 Page 29-1057



the correct RPAAID.
__ 5.5.2 If the correct RPAAID was used, and the

AIS is not detected on the remote
equipment, follow your company's
End of Procedure
Page 29-1058 7/07 76.5500/29, Rev R

Troubleshooting Manual 9. Isolating Port Group Controller LAN Trouble
9. Isolating Port Group Controller LAN Trouble
9.01 This procedure describes how to isolate and troubleshoot port group
controller failures due to a LAN problem.
Note: This section applies to Tellabs 5500 systems with port shelves subtended
to the Standard Core Switch portion of the network complex.
For systems with a Hybrid Core Switch or a Consolidated Core Switch,

refer to Port Aggregation Module (PAM), page 29-405, or Time Slot
Interchange Module (TSI), page 29-506, to troubleshoot the SDF48
cables.
To troubleshoot the Control LAN for a Network Complex shelf, go to Local

Area Network (LAN-1), page 29-230.
To troubleshoot the control LAN in a system with a Hybrid or Consolidated

Core Switch, go to Troubleshooting Control LAN in System with Hybrid or
CCS Switch Core, page 29-238.
9.02 Prior to the start of this procedure, obtain a chart or diagram detailing the
LAN configuration (or “LAN runs”) of the affected Tellabs 5500/5500S system. On
each shelf, the A-side group controller is on a different LAN run than the B-side
group controller. If multiple group controllers fail, it is important to identify the
affected LAN runs.
9.03 Refer to Tellabs 5500/5500S Installation Manual, 76.5500/7, for a detailed
description of LAN configuration guidelines.
High Density Port Shelf LAN

9.04 High density port shelves require LAN connections between the
administrative complexes and the network complexes; however, LAN cables do
not connect directly from the administrative complexes to the high density port
shelf. LAN communication is embedded within the HD SDF fiber optic link between
the End Switch Module-Universal (81.5509A ESMUs) and 5596 Time Slot
Interchange 96 Modules (TSI96 modules).
Note: In a system with a Consolidated Core Switch Shelf, LAN communication is

embedded within the SDF48 fiber optic link between the 55196 Time Slot
Interchange 96P Modules (TSI96P) and the 55109 Port Aggregation
Module (PAM). To troubleshoot the SDF48 fibers between the PAMs and
the TSI96P, go to Checking PAM to TSI96P High-Density SDF Fiber Cable
Integrity, page 29-413.
76.5500/29, Rev R 7/07 Page 29-1059

9. Isolating Port Group Controller LAN Trouble Troubleshooting Manual
9.05 LAN cables connect from the administrative complexes to a GC LAN

retrofit bar, which is attached to the rear of a designated End Stage Shelf (ESS). A
jumper cable connects the GC LAN retrofit bar to the rear of the first ESMU
dedicated to a HDPS.
9.06 Each HDPS requires three ESMUs and one GC LAN jumper cable per
copy. The GC LAN jumper cable connects from the GC LAN retrofit bar to the first
(lowest SDF number) of three ESMUs per copy. The second and third ESMUs in
the shelf do not carry LAN traffic directly to the applicable TSI96.
9.07 Tellabs provides four fiber cable types for the HDPS application:
• The standard red ESM-A cable, Tellabs part number 155.0059-xxx, is
available in lengths from 5 to 600 meters (where xxx equals the length
in meters).
• The standard blue ESM-B cable, Tellabs part number 155.0060-xxx,

is available in lengths from 5 to 600 meters (where xxx equals the
length in meters).
• The heavy duty red ESM-A cable, Tellabs part number 155.0061-xxx,
length in meters).
• The heavy duty blue ESM-B cable, Tellabs part number 155.0062-xxx,
length in meters).
Note: Customers may use their own fiber cables from the NC to the HDPS. Refer
to Tellabs 5500/5500S Installation, 76.5500/7, for specifications.
9.08 The Tellabs part number for the required GC LAN jumper cable is
150.0346.
9.09 Tellabs strongly recommends dedicating a LAN run (for example, J14 and
J15) for connecting high density port shelves. If no high density port shelf will be
installed, Tellabs recommends that a LAN run be saved for future connectivity.
9.10 If a situation arises where high density and low density port shelves need
to be mixed on a single LAN run, refer to the following notes and Table 9.1 for LAN
rules.
Note 1: When mixing LDPS and HDPS in a single LAN run, the shelf types can
be situated in any order, provided the rules in Table 9.1, page 29-1061
are followed.
Note 2: Within a given LAN run, each high density port shelf counts as four
shelves and each low density shelf counts as one shelf.
Page 29-1060 7/07 76.5500/29, Rev R

Table 9.1 LAN Rules

Maximum LAN
GCM LDPS HDPS LAN cable type run distance
1
81.5512A 32 0 50.17xxx (white) 600 feet
2 3 1
81.5512A 20 5 50.17xxx (white) 600 feet
81.5512A/B 32 0 50.15xxx (gray) 300 feet1

2 3 1
81.5512A/B 20 5 50.15xxx (gray) 300 feet
1
81.5512B 40 0 50.17xxx (white) 700 feet
81.5512B 202 53 50.17xxx (white) 700 feet1
81.5591 0 10 155.0059-xxx (red), 2000 feet4

155.0060-xxx (blue),
155.0061-xxx (red),
155.0062-xxx (blue)
1. Maximum LAN run distance applies only to the low density port shelves.
2. A LAN run containing HDPS and LDPS may not contain more than 20 LDPS regardless of
the number of HDPS on the LAN run.
3. The maximum of 5 HDPS can be altered provided the number of LDPS on the LAN run
decreases by four shelves for every HDPS added to the LAN run (for example, 6 HDPS
and 16 LDPS).
4. This is the maximum distance for the fiber cable from the network ESMU to the TSI96 in
the HDPS.
9.11 Tellabs requires adherence to the following high density LAN cable rules:
• each ESS containing an ESMU must be dedicated to one LAN run
(only the first ESMU receives LAN communication via the HD SDF
fiber cables)
• three ESMUs per high density port shelf (the ESMUs may span ESSs)
• first ESMU dedicated to a given HDPS is counted on LAN run
• 10 high density port shelves maximum per LAN run
9.12 If no LAN runs are available to support high density port shelves, refer to
Tellabs 5500/5500S Port Shelf Expansion Manual, 76.5500/39, for instructions to
mix high density and low density port shelves on a single LAN run.
9.13 Figure 9.1, page 7-1062, shows a basic example of the AC to NC LAN and
NC to HD SDF fiber connections.
9.14 Figure 9.2, page 29-1063, shows a basic example of a LDPS - HDPS
mixed LAN run with the HDPS connected directly to the ACs.
9.15 Figure 9.3, page 29-1064, shows a basic example of a LDPS - HDPS
mixed LAN run with the LDPS connected directly to the ACs.
9.16 Figure 9.4, page 29-1065, shows an example of the AC to NC LAN and NC
to HD SDF fiber connections with daisy-chained GC retrofit bars.
Note: All shelves in these figures are from a rear view except the HDPS, which
is from a front view.
76.5500/29, Rev R 7/07 Page 29-1061

Figure 9.1 High Density Port Shelf LAN Run: AC to NC to a High Density Port Shelf
AC-B NC-B ESS Key:

OUT IN terminator =
retrofit bar shorting plug =
GC LAN jumper cable
J29 (1A) J28 (1B)
AC-B LAN B
TSI96-A
AC-B LAN A
AC-A NC-A ESS

OUT IN
TSI96-B
J29 (1A) J28 (1B)
AC-A LAN B
AC-A LAN A
Note: While three ESMUs are connected via HD SDF fiber cables to a given
HDPS, only the first ESMU sends LAN traffic directly to the first two
connectors on the TSI 96. This communication path is shown in Figure 9.1.
Page 29-1062 7/07 76.5500/29, Rev R

Figure 9.2
AC-B NC-B ESS A

OUT IN
B
76.5500/29, Rev R
J8 A A J4 A
J7 B B J3 B
J6 A A J2
J5 B B J1
J29 (1A) J28 (1B) J8 A A J4

J7 B B J3
AC-B LAN B
J6 A A J2
TSI96-A J5 B B J1
J8 A A J4
Mixed LAN Run: AC to HDPS to LDPS
AC-B LAN A J7 B B J3
J6 A A J2
7/07
J5 B B J1
AC-A NC-A ESS
OUT IN J8 A A J4
J7 B B J3
TSI96-B
J6 A A J2
J5 B B J1
Copy B | Copy A
J29 (1A) J28 (1B)
AC-A LAN B
AC-A LAN A
Page 29-1063
76.5500/29, Rev R
AC-B
NC-B ESS
OUT IN
J8 A A J4
J7 B B J3
J6 A A J2
J5 B B J1
J29 (1A) J28 (1B)
J8 A A J4
J7 B B J3
7/07
J6 A A J2
AC-B LAN B J5 B B J1 TSI96-A
Mixed LAN Run: AC to LDPS to HDPS
J8 A A J4
J7 B B J3
AC-B LAN A
J6 A A J2
J5 B B J1 NC-A ESS
AC-A OUT IN
J8 A A J4
J7 B B J3 TSI96-B
J6 A A J2
J5 B B J1
Copy B | Copy A
J29 (1A) J28 (1B)
Page 29-1064
Figure 9.3
AC-A LAN B
AC-A LAN A
Figure 9.4 HDPS LAN with Daisy-Chained GC Retrofit Bars (Rear View)
NC-B ESS
AC-B
OUT IN OUT IN
J29 (1A) J28 (1B)
AC-B LAN B
GC LAN jumper cable
AC-B LAN A
NC-A ESS
AC-A
OUT IN OUT IN
J29 (1A) J28 (1B)
AC-A LAN B
AC-A LAN A
Key:
terminator =
shorting plug =
76.5500/29, Rev R 7/07 Page 29-1065

Low Density Port Shelf LAN

9.17 All low density port shelves (LDPS) require LAN connections directly
between the administrative complexes and the port complexes.
9.18 There are two types of basic LAN cable:
• The standard gray cable, Tellabs part number 50.15xxx, is available in
lengths from 3 to 300 feet (where xxx equals the length in feet).
• The white low-loss cable, Tellabs part number 50.17xxx, is available

in lengths from 3 to 600 feet.
Note 1: The white cable, Tellabs part number 50.17xxx, is used for new
installations only.
Note 2: The gray cable, Tellabs part number 50.15xxx, is used for NTDMs cross
copy.
9.19 Tellabs requires adherence to the following 50.17xxx and 50.15xxx LAN
cable rules:
• 50.15xxx cables cannot be longer than 300 feet.
• 50.17xxx cables cannot be longer than 600 feet.
• The 50.17xxx and 50.15xxx cables cannot be mixed within the same
LAN run.
• Use the same type of cables on LAN A run and LAN B run.
• Network LAN connected to J41 must be the same cable type as the
LAN run connected to J26 and J27. For example, if J26 and J27 are
white cable LANs, then J41 cables must also be white.
• Network LAN connected to J42 must be the same cable type as the
LAN run connected to J28 and J29. For example, if J28 and J29 are
white cable LANs, then J42 cables must also be white.
• LAN cables connected to J41 and J42 do not have to be the same
type. For example, white cables can be connected to J41 at the same
time that gray cables are connected to J42.
Page 29-1066 7/07 76.5500/29, Rev R

Performing Preliminary System Checks

9.20 In this section, verify that certain user profile parameters are set correctly
in order to perform this procedure.
__ 1. Log into the system by entering the following command:

pid = Password.
System response:
M ctag COMPLD

prosecution. */
Note: When a user changes their user profile settings by executing the
SET-PROFILE-USER command, the original channel profile settings
configured for a link when executing the SET-PROFILE-CHAN command
will not be affected. Once the user completes the procedure and logs off
the system, the channel profile settings revert back to the original settings.
__ 2. Retrieve the current user profile parameters by entering the following

command:
RTRV-PROFILE-USER::uid:ctag;
Where: uid = User identity or upgrade user ID.
System response:
M ctag COMPLD

“uid:CRALM=ON,MJALM=ON,MNALM=ON,NAEVT=ON,CONDSCHED=ON,REPTSCHED=OFF,PMSCHED=ON,
SYSMSG=ON,SIRPT=ON,DBCHG=ON,AUD=ON,ABSNUM=ON:MLP=OFF”
__ 2.1 If CRALM, MJALM, MNALM, SYSMSG, AUD, and

SIRPT are set to ON, and MLP is set to OFF, go to step
7, page 29-1069.
__ 2.2 If CRALM, MJALM, MNALM, SYSMSG, AUD, and/or

SIRPT are not set to ON and MLP is not set to OFF, go
to step 3 to change the parameters.
__ 3. Set the user profile parameters by entering the following command:

SET-PROFILE-USER::uid:ctag::SIRPT=ON,MJALM=ON,MNALM=ON,SYSMSG=ON,CRALM=ON,
AUD=ON:MLP=OFF;
System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-1067

__ 4. Retrieve the user profile parameters by entering the following

command:
System response:
M ctag COMPLD

"uid::CRALM=ON,MJALM=ON,MNALM=ON,NAEVT=ON,CONDSCHED=ON,REPTSCHED=ON,PMSCHED=ON,
SYSMSG=ON,SIRPT=ON,DBCHG=ON,AUD=ON,ABSNUM=ON:MLP=OFF"
__ 4.1 Verify from the system response that CRALM, MJALM,

MNALM, SYSMSG, AUD, and SIRPT are set to ON,
and MLP is set to OFF.
Note: Changes to the user profile table will not take effect until the next time the
user logs on.



pid = Password.
System response:
M ctag COMPLD
Page 29-1068 7/07 76.5500/29, Rev R

__ 7. Retrieve the master/slave status of the ACs and the SIMs by entering
Note: Press Ctrl+o to start and stop the screen scroll.
System response:
M ctag RTRV

"LSM-A::HWV=81.55103 R09,ALMPF=99,SN=UV0694866,DT=060310,MACADDR2=0001AF1681B5:
PST=NR"
76.5500/29, Rev R 7/07 Page 29-1069

__ 7.1 Record the master/slave relationship. Only one SIM is

MSTR, the other is SLV:
SIM in Copy A or B TMG=MSTR TMG=SLV
SIM-A
SIM-B

in-service, normal, active (IS-NR-ACT) and the other
AC is in-service, normal, standby (IS-NR-STBY).
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
__ 8.1 Verify from the system response that the both NCs are

Page 29-1070 7/07 76.5500/29, Rev R


SIM-A
SIM-B


NTDM-A
NTDM-B
CCSM-SH1-9
CCSM-SH2-9
__ 8.5 Verify from the system response that both NTDMs and
CCSMs are listening to the master SIM. Refer to
step 8.4.
__ 9. Retrieve the alarm and condition states by entering the following

command:
System response:
M ctag COMPLD
__ 9.1 Before continuing these procedures, record any INT

conditions indicating equipment failures that are present
in the system at this time. These conditions must be
corrected. If necessary, follow your company's
1.800.443.5555 (North America) or 1.630.798.7070
(outside North America) for further analysis to verify that
there are no alarms and conditions that indicate that you
must not continue with this procedure.
__ 9.2 If there are no alarms or conditions indicating that you

must not continue with this procedure, continue to the
next step.
76.5500/29, Rev R 7/07 Page 29-1071

__ 10. Verify that the redundant port modules and redundant mapping
modules are in-service, normal, standby (IS-NR-STBY) by entering
RTRV-EQPT::RMACT:ctag;

System response when RPMs and RMMs are not active:
M ctag COMPLD
System response when RPMs or RMMs are active:

M ctag COMPLD

"RPM1-0001::PRTN_TYPE=RECV,PRTN_PORT=PM1-0001-05:RM_PST=IS-NR-ACT,
PORT_PST=IS-NR-STBY"
"RPM3-0017::PRTN_TYPE=FRCD,PRTN_PORT=PM3-0019:RM_PST=IS-NR-ACT,PORT_PST=OOS-NR"
"RMM-0065::PRTN_TYPE=MAN,PRTN_MM=MM-0065:RM_PST=IS-NR-ACT,MM_PST=IS-NR-STBY"
__ 10.1 If the system responds with the M ctag COMPLD

message only, no RPMs or RMMs are active. Continue
to the next section.
__ 10.2 If the system responds with the M ctag COMPLD

message followed by output listing active RPMs or
RMMs, resolve the problem causing this state before
continuing with this procedure. Refer to Section 6,
Caution:
Do not continue with this procedure if any RPMs or RMMs are active (ACT). Your
actions may result in a loss of traffic. Resolve the problem that is causing the
abnormal state before continuing with this procedure.
Page 29-1072 7/07 76.5500/29, Rev R

Verifying the Status of the Network and Timing

9.21 Verify the status of the port module network clock.
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

1.800.443.5555 (North America) or 1.630.798.7070

analysis.
76.5500/29, Rev R 7/07 Page 29-1073


System response:
M ctag COMPLD

M ctag RTRV
or
M ctag RTRV

improperly inhibited (BYTEINH=NONE), continue to
step 3, page 29-1076.
Page 29-1074 7/07 76.5500/29, Rev R


improperly inhibited (BYTEINH=INH), enter the
RTRV-BBBC command again, specifying the particular
module that is improperly inhibited:

Example:

"PM1D-0001-01:PORTID=0001-01,PORTTYPE=T1,CAUSE=NONE,BYTEINH=NONE,CLCKINH=NONE,
SELECT=NCA"
"PM1D-0001-01:PORTID=0001-02,PORTTYPE=T1:PST=UAS"
"PM1D-0001-01:PORTID=0001-03,PORTTYPE=T1,CAUSE=LOCAL,BYTEINH=INH-BYTEA,CLCKINH=
INH-CLKA,SELECT=FRC-NCB"
SELECT=NCA"
SELECT=NCA"
SELECT=NCA"
SELECT=NCA"
/* If a partial line is displayed, it indicates either an error retrieving data or

unassigned port */
__ 2.4 Refer to Section 3, Troubleshooting the Network

Complex, page 29-245, to resolve any network issues
76.5500/29, Rev R 7/07 Page 29-1075

__ 3. Retrieve all alarms and equipment conditions by entering the following

command:
RTRV-ALM-EQPT:::ctag;
(Optional) RTRV-ALM-ALL:::ctag;
__ 3.1 Record all conditions indicating “protection not

available” (PROTNA alarms) for all port modules.
Port Group Controller Failures

9.22 Isolate the cause of the faulted group controller module(s).
Single Faulted Port Group Controller

__ 1. If a single group controller has faulted, refer to the Port Group
Controller Module (PGC) Alarm Messages, page 29-481, to address
the faulted module.
__ 1.1 If the group controller clears the fault condition after
following the steps, proceed to Performing Final System
Checks, page 29-1084.
Multiple Faulted Port Group Controllers and Faulted SCM

__ 1. If a system communication module (SCM) has faulted, refer to the
System Communication Modules (SCM-1 and SCM-2), page 29-110,
to address the faulted SCM.
__ 1.1 If the group controllers clear the fault condition after
following the steps for the faulted SCM, proceed to
Performing Final System Checks, page 29-1084.
Page 29-1076 7/07 76.5500/29, Rev R

Multiple Faulted Port Group Controllers

__ 1. If multiple group controller modules have faulted, perform an
administrative complex copy switch by entering the following
command:
SW-DX-EQPT::AC-A:ctag;
System response:
M ctag COMPLD
Note: It may take up to twenty minutes for group controllers to clear.
__ 1.1 If group controller modules remain in a fault condition,

proceed to Troubleshooting Port Group Controller LAN
Failures, page 29-1078.
__ 1.2 If the fault conditions against the group controller

modules clear, go to step 2, page 29-1077.
Note: If performing the first administrative complex copy switch clears the faulted
group controllers, the problem may still reside in the LAN runs of the
previously active administrative complex. The second copy switch verifies
the condition of the LAN runs on the previously active administrative
complex.
__ 2. If the faulted group controllers clear, perform another administrative

complex copy switch by entering the following command:
SW-DX-EQPT::AC-A:ctag;
System response:
M ctag COMPLD
__ 2.1 If all the group controllers remain normal, proceed to

Performing Final System Checks, page 29-1084.
__ 2.2 If group controller modules fault again or remain in fault,

proceed to Troubleshooting Port Group Controller LAN
Failures, page 29-1078.
76.5500/29, Rev R 7/07 Page 29-1077

Troubleshooting Port Group Controller LAN Failures

9.23 As a reference, refer to Figure 9.5 through Figure 9.8, page 29-1081, for
typical LAN cable configurations.
Figure 9.5 DS1, DS3, and STS-1E Daisy Chain LAN Run
A
AC-B B
J8 A A J4 A
AC-B LAN A
J7 B B J3 B
J5 B B J1
J27 (B)
J8 A A J4
J29 (A)
J7 B B J3
J6 A A J2
AC-A J5 B B J1
J8 A A J4
J7 B B J3
J6 A A J2
J5 B B J1
J27 (B) J8 A A J4
J29 (A) B J3
J7 B
J6 A A J2
AC-A LAN A
Note: Some LAN runs may be run from top to bottom (that is, the connection to
the administrative complexes are at the top of the rack instead of the
bottom).
Page 29-1078 7/07 76.5500/29, Rev R

Figure 9.6 DD DS1 Port Shelf LAN Run, Daisy Chain Formation
A
AC-B
B
AC-B LAN A J23 A

J27
J24 J28 B
AC-B LAN B J25 J29

J26 J30
J27 (B)
J23 J27
J29 (A)
J24 J28
J25 J29
AC-A J26 J30
J23 J27
J24 J28
J25 J29
J26 J30
J27 (B) J23 J27

J29 (A) J24 J28
J25 J29
AC-A LAN B
J26 J30
AC-A LAN A
Note: Some LAN runs may be run from top to bottom (that is, the connection to
the administrative complexes are at the top of the rack instead of the
bottom).
76.5500/29, Rev R 7/07 Page 29-1079

Figure 9.7 OC-3 or OC-12 Port Shelf LAN Run, Daisy Chain Formation

A
AC-B B
AC-B LAN A J5 A A J17 A
J6 B B J18 B

J8 B B J20
J27 (B)
J5 A A J17
J29 (A)
J6 B B J18
J7 A A J19
AC-A J8 B B J20
J5 A A J17
J6 B B J18
J7 A A J19
J8 B B J20
J27 (B) J5 A A J17

J29 (A) J6 B B J18
J7 A A J19
AC-A LAN A
Page 29-1080 7/07 76.5500/29, Rev R

Figure 9.8 High Density Port Shelf LAN Run

Key:
AC-B NC-B ESS terminator =
OUT IN shorting plug =
Retrofit Bar
GC LAN Jumper Cable
J29 (1A) J28 (1B)
AC-B LAN B
AC-B LAN A TSI96-A
AC-A NC-A ESS

OUT IN
TSI96-B
(front view)
J29 (1A) J28 (1B)
AC-A LAN B
AC-A LAN A
Note 1: Some LAN runs may be run from top to bottom (i.e. the connection to the
administrative complexes are at the top of the rack instead of the
bottom).
Note 2: If you cannot resolve the problem, follow your company's prescribed
Assistance at 1.800.443.5555 (North America) or 1.630.798.7070
76.5500/29, Rev R 7/07 Page 29-1081

9.24 While troubleshooting LAN problems, use the following list as a guide:
• The system communication module (SCM) may have an internal
failure.
a. Prior to troubleshooting the LAN, replace the SCM equipped in the

Tellabs 5500/5500S system with a spare SCM.
• The terminators in the LAN run may be missing, improperly connected,

or damaged.
a. Verify that all terminators are properly connected at the ends of the
LAN runs.
b. If all terminators are properly connected, replace terminators with

spares.
• LAN cables may be damaged, transposed, connected to the wrong

connectors, not seated properly in the correct connectors, or may be
improperly terminated.
a. Follow the diagrams in this section as well as any site-specific

diagrams to determine if shelves are properly cabled.
b. Proceed “hand-over-hand” from shelf to shelf to verify all cables

are connected to the correct connectors on the rear of the shelves.
Pay particular attention to the LAN connections between the last
working PGC and the first faulted PGC of the LAN run.
c. Determine which entities are connected to which GC LAN runs

located on the active AC by entering the following command:
RTRV-CONFIG::GCLAN-xxxx:ctag;
Where: xxxx = GC LAN being retrieved (1 - 8).
System response:
M ctag COMPLD

"GCLAN-1:PGC1D-0049-A,PGC3-0513-A,PGCO3-0641-A,PGCO12-0653-A,NGC-A"
"GCLAN-1:PGC1D-0049-B,PGC3-0513-B,PGCO3-0641-B,PGCO12-0653-B"
"\* GC LAN configuration is for PGCs connected to Active AC only *\"
• A faulted group controller on a LAN run may need to be reseated.
a. Unseat all faulted group controller modules.
b. Insert the group controllers modules one at a time. Wait for each
module to download before moving on to the next one.
Page 29-1082 7/07 76.5500/29, Rev R

• Refer to PPN 99036A
a. In the field, 81.0550J, 81.0550K, and 81.0550JK optical port

shelves have been found to have one bent contact on the J7 LAN
connection. The J7 LAN connection is located on the rear of the
shelf, left side facing the back. The J7 connection enables the
shelf’s Group Controller (GC) module B copy to communicate with
the Administrative Complex (AC) A copy. The J7 connection is
made up of four contacts, and the second contact from the top is
the one that has been found to be slightly bent. This problem has
typically been encountered when first turning up an optical port
shelf.
• Refer to PPN 00082A.

a. Tellabs has determined that revision F and F1 of the 81.5512A
Group Controller (GC) module may not download when used with
21 or more revision D 81.5512A GCs on the same LAN. Revision
D GCs can cause LAN loading, which may prevent the revision F
and later GCs from downloading correctly. If a system contains 21
or more revision D GCs on the same LAN, Tellabs recommends
upgrading these GCs. Systems with fewer than 21 revision D GCs
on the same LAN are not affected.
b. Tellabs recommends moving revision F and above GCs closer on

the LAN to the Administrative Complex, allowing the GCs to
correctly download. Tellabs also recommends upgrading all
revision D GCs on LAN runs with more than 21 GCs (shelves).
Refer to Tellabs 5500/5500S Software Release Document,
76.5500/16, for information regarding module revisions.
• If your LAN run contains a high density port shelf, the retrofit bar and/or
GC LAN jumper cable located at the backplane of the end stage shelf
(ESS) may be damaged or improperly connected, or the ESMU may
be faulted.
Note: On the high density port shelf, only the first ESMU communicates LAN
information to the TSI96s.
a. Troubleshoot the ESMU. Refer to Section 3, Troubleshooting the

Network Complex, page 29-245.
b. Verify that the GC LAN jumper cable is properly connected. Refer

- If the GC LAN jumper cable is not properly connected, reconnect

the cable.
- If the GC LAN jumper cable is properly connected, replace the GC
LAN jumper cable.
76.5500/29, Rev R 7/07 Page 29-1083

c. Verify that the shorting plugs on the ESS backplane are properly
connected.
- If the shorting plugs are not properly connected, reconnect the

shorting plugs.
- If the shorting plugs are properly connected, replace the shorting
plugs.
d. If replacing the GC LAN jumper cables or shorting plugs does not
resolve the problem, replace the retrofit bar.
Performing Final System Checks

9.25 Verify that the system is normal and in-service.
__ 1. Verify that the system is free of hardware alarms and equipment
conditions by entering the following commands:
System response:
M ctag COMPLD
Note: Before continuing these procedures, verify that performing these two steps
did not cause any additional alarms and conditions to display. If you see
additional alarms or conditions, follow your company's prescribed
North America) for further analysis.
__ 1.1 If there are no additional alarms or conditions, continue

to the next step.

Page 29-1084 7/07 76.5500/29, Rev R

Checking the Status of the System

9.26 Perform the following procedure to recheck the state of the system.
System response:
M ctag COMPLD

"LSM-A::HWV=81.55103 R09,ALMPF=99,SN=UV0694866,DT=060310,
MACADDR2=0001AF1681B5:PST=NR"
76.5500/29, Rev R 7/07 Page 29-1085

__ 1.1 Record the master/slave relationship. Only one SIM is

MSTR, the other is SLV:
SIM in Copy A or B TMG=MSTR TMG=SLV
SIM-A
SIM-B
RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
have now switched timing (TMG=MSTR/SLV).

Page 29-1086 7/07 76.5500/29, Rev R


SIM-A
SIM-B


NTDM-A
NTDM-B
CCSM-SH1-9
CCSM-SH2-9
__ 2.6 Verify from the system response that both NTDMs and
CCSMs are listening to the master SIM. Refer to
step 2.5.


End of Procedure
76.5500/29, Rev R 7/07 Page 29-1087

USER NOTES
Page 29-1088 7/07 76.5500/29, Rev R

Troubleshooting Manual 10. Clearing Residual Alarms
10. Clearing Residual Alarms
10.01 This section describes the process to clear residual alarms by reinstalling
the ALARM.DAT file through utility mode.
10.02 When an alarm is posted against an entity and the abnormal condition is
corrected, the alarm against the entity should clear.
10.03 In certain circumstances, an alarm posted against an entity fails to clear
once the abnormal condition is corrected. One example is when a shelf is
improperly degrown. When this occurs, the alarms need to be manually deleted
from the database by following this procedure.
10.04 After a retrieve command is entered for alarms in the system, the system
may go into a IP loop. In this case, the ALARM.DAT file must be reinstalled using
this procedure.
Requirements
10.05 The following stipulations are required to perform these procedures:
• Access to the first link (J10) on the active administrative complex.
• Site personnel with a general knowledge of the Tellabs 5500/5500S

system.
• A flash memory card must be inserted in the DSM of the active side of
• No flash memory card can be in the DSM of the standby administrative

complex.
Note: Throughout this procedure, various steps ask to verify the condition of
equipment and terminations. Should the entity not have the same state as
the one described in the text, correct the problem before continuing. If
necessary, follow your company's prescribed procedures for obtaining
America).
76.5500/29, Rev R 7/07 Page 29-1089

10. Clearing Residual Alarms Troubleshooting Manual
System Pre-Checks
10.06 If necessary, notify network surveillance centers at the beginning of this
procedure.
__ 1. Log on to link 1 by entering the following command:

pid = Password.
__ 2. Retrieve the current user profile parameters by entering the following
command:
Where: uid = User id or upgrade user ID.
System response:
M ctag COMPLD

“uid:CRALM=ON,MJALM=ON,MNALM=ON,NAEVT=ON,CONDSCHED=ON,REPTSCHED=OFF,PMSCHED=ON,
SYSMSG=ON,SIRPT=ON,DBCHG=ON,AUD=ON,ABSNUM=ON:MLP=OFF”
__ 2.1 Record the current channel profile parameter values of

CRALM, MJALM, MNALM, SYSMSG, SIRPT, AUD,
and MLP. Use these values to restore the original
channel profile configuration after the procedure is
completed.
Table 10.1 User Profile Parameters

Required
Channel 5 Parameter On Off Settings
Critical Alarm (CRALM) ON
Major Alarm (MJALM) ON
Minor Alarm (MNALM) ON
System Message (SYSMSG) ON
System Integrity Reports (SIRPT) ON
Audit (AUD) ON
Message Log Ports (MLP) OFF
__ 2.2 If CRALM, MJALM, MNALM, SYSMSG, AUD, and

SIRPT are set to ON, and MLP is set to OFF, go to step
7, page 29-1092.
__ 2.3 If CRALM, MJALM, MNALM, SYSMSG, AUD, and/or

SIRPT are not set to ON and MLP is not set to OFF, go
to step 3 to change the parameters.
Page 29-1090 7/07 76.5500/29, Rev R

__ 3. Set the user profile parameters by entering the following command:

SET-PROFILE-USER::uid:ctag::SIRPT=ON,MJALM=ON,MNALM=ON,SYSMSG=ON,CRALM=ON,
AUD=ON:MLP=OFF;
Where: uid = User id.
System response:
M ctag COMPLD
__ 4. Retrieve the user profile parameters by entering the following

command:
System response:
M ctag COMPLD

"uid::CRALM=ON,MJALM=ON,MNALM=ON,NAEVT=ON,CONDSCHED=ON,REPTSCHED=ON,PMSCHED=ON,
__ 4.1 Verify from the system response that CRALM, MJALM,

MNALM, SYSMSG, AUD, and SIRPT are set to ON,
and MLP is set to OFF.
Note: Changes to the user profile table will not take effect until the next time the
user logs on.



pid = Password.
System response:
M ctag COMPLD

prosecution. */
76.5500/29, Rev R 7/07 Page 29-1091

System response:
M ctag COMPLD

“AC-A::SWV-5500FPX.Y.Z,ALMPF=99:PST=IS-NR-ACT”
“SIM-A::HWV=81.5507A RA,ALMPF=1,TMG=MSTR,SN=IL2488248,DT=941207:PST=IS-NR”
“AC-B::SWV-5500FPx.y.z,ALMPF=99:PST=IS-NR-STBY”
“SIM-B::HWV=81.5507A RA,ALMPF=1,TMG=SLV,SN=IL2488248,DT=941207:PST=IS-NR”

__ 8. Retrieve timing by entering the following command:

RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
"NTDM-A::TMG=SIM-B:PST=NR"
"NTDM-B::TMG=SIM-B:PST=NR"
"CCSM-SH1-9::TMG=SIM-B:PST=NR"
Page 29-1092 7/07 76.5500/29, Rev R


SIM-A
SIM-B


NTDM-A
NTDM-B
CCSM-SH1-9
CCSM-SH2-9
__ 8.4 Verify that the NTDMs/CCSMs are listening to the

master SIM. See substep 8.2, page 29-1093.
__ 8.4.1 If the NTDMs/CCSMs are listening to the

master SIM, continue to step 9.

North America).
__ 9. Remove the flash disk from the DSM in the standby AC.
__ 10. If AC-A is active, verify the terminal is plugged into link 1. If AC-B is
active, verify the terminal is plugged into link 5.
__ 10.1 If the terminal is not plugged into the correct link, go to
step 11.
__ 10.2 If the terminal is plugged into the correct link, go to step

12, page 29-1094.
76.5500/29, Rev R 7/07 Page 29-1093

__ 11. Perform the following steps to move the terminal:

__ 11.1 Logout from the system by entering the following
command:

__ 11.2 Move the terminal to the correct link.
__ 11.3 Log into the system by entering the following command:

pid = Password.
System response:
M ctag COMPLD
__ 12. Enter local restoration by entering the following command:

Note: When a user changes their user profile settings by executing the
SET-PROFILE-USER command, the original channel profile settings
configured for a link when executing the SET-PROFILE-CHAN command
will not be affected. Once the user completes the procedure and logs off
the system, the channel profile settings revert back to the original settings.
System response:
M ctag COMPLD
following command:
System response:
M ctag COMPLD

":ALW:UPGRADE=NO"
__ 13.1 Verify from the system response that the system is in

local restoration mode (ALW).
Page 29-1094 7/07 76.5500/29, Rev R

Placing the System in Utility Mode

10.07 Place the system into utility mode by performing the following steps.
System response:
M ctag COMPLD

"AC-A::SWV=5500FPx.y.z,ALMPF=99:PST=IS-NR-ACT"
"SIM-A::HWV=81.5507ARA,ALMPF=1,TMG=SLV,SN=IL2488248,DT=941207:PST=IS-NR"
"AC-B::SWV=5500FPx.y.z,ALMPF=99:PST=IS-NR-STBY"
"SIM-B::HWV=81.5507ARA,ALMPF=1,TMG=MSTR,SN=IL2488248,DT=941207:PST=IS-NR"
__ 1.1 Verify that the MSTR/SLV states of the SIMs changed.
__ 1.2 Verify that the IS-NR-STBY AC shows that SIM=MSTR.

RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"
76.5500/29, Rev R 7/07 Page 29-1095


SIM-A
SIM-B

NTDM-A
NTDM-B
CCSM-SH1-9
CCSM-SH2-9
__ 2.4 Verify that the NTDMs/CCSMs are listening to the

master SIM. See substep 2.2, page 29-1096.
__ 2.4.1 If the NTDMs/CCSMs are listening to the

master SIM, continue to step 3.

North America).
__ 3. Enter the following command to swap the data from SEC memory to
PRI memory by entering the following command:
INIT-SYS:::ctag::2;
System response:
M ctag COMPLD
Note 1: The AC will now reset. The reset will take approximately five minutes.
Note 2: In the following step, do not pull the APM until hard disk activity has
ceased. Wait for the APM Fault LED to light.
__ 4. Unseat the APM in the in-service, normal, active (IS-NR-ACT) AC.

__ 5. Unseat the APM in the in-service, normal, standby (IS-NR-STBY) AC.
Page 29-1096 7/07 76.5500/29, Rev R

__ 6. Unseat the AIM in the in-service, normal, active (IS-NR-ACT) AC.

__ 7. Reseat the APM in the in-service, normal, active (IS-NR-ACT) AC.
Wait for the AC to reset approximately three times and enter utility
mode.
__ 8. Reinsert the AIM.
__ 9. Enter the appropriate utility mode password at the UM> prompt.
__ 10. Press RETURN to enter the main menu of utility mode. The following
screen appears.
Figure 10.1 UM Main Menu
Boot Directory: TITANx

Boot Loader Version Program Version, Validity Flag
ACT: 5500FPx.y.z PRI: 5500FPx.y.z VALID
INACT:5500FPx.y.z DATE: hh:mn mm-dd-yyyy
REMV: 5500FPx.y.z SEC: 5500FPx.y.z
DATE: hh:mn mm-dd-yyyy
REMV: 5500FPx.y.z
header DATE: hh:mn mm-dd-yyyy
Database Version, Validity Flag SID of Data Bundle

PRI: 5500FPx.y.z VALID PRI:x...x
SEC: 5500FPx.y.z
terminal DATE: hh:mn mm-dd-yyyy VALID SEC:x...x
screen REMV: 5500FPx.y.z
DATE: hh:mn mm-dd-yyyy VALID REMV:x...x
1 Update header display

2 Reset local ac
3 UM Advanced I Menu
menus 4 UM Advanced II Menu
5 Retrieve patch load information
6 Logout
Enter selection (by number): 4
76.5500/29, Rev R 7/07 Page 29-1097

Clearing Residual Alarms

__ 1. From the UM Main Menu shown above, enter 4 for “UM Advanced II
Menu” and press RETURN.
Figure 10.2 UM Advanced II Menu
1 Swap pri and sec on local ac 9 Expand a 5500S (Tellabs only)

2 Copy bootloader to disk 10 Set date and time
11 Prepare DSM for FPx.y.z Upgrade
3 Copy a bundle from removable 12 Return to previous menu
4 Reset hard disk ID 13 Logout
5 Format and partition disk
6 Clear residual alarms
7 Clear off normal conditions
8 Exit local restoration
__ 2. Enter 6 for “Clear residual alarms” and press RETURN.

Clear residual alarms
Please make sure the removable media is inserted.

Press RETURN to continue.
__ 3. Make sure the SRM is inserted and press RETURN.

Proceed with clear residual alarms? (Y/N) y
__ 4. Press “y” when prompted with the question “Proceed with clear
residual alarms.”
clearing residual alarms ...
clear residual alarms complete
__ 5. Press RETURN to go back to the menu.
Figure 10.3 UM Advanced II Menu

1 Swap pri and sec on local ac 9 Expand a 5500S (Tellabs only)
2 Copy bootloader to disk 10 Set date and time
11 Prepare DSM for FPx.y.z Upgrade
3 Copy a bundle from removable 12 Return to previous menu
4 Reset hard disk ID 13 Logout
5 Format and partition disk
6 Clear residual alarms
7 Clear off normal conditions
8 Exit local restoration
__ 6. Enter 11 to “Return to previous menu” and press RETURN.
Page 29-1098 7/07 76.5500/29, Rev R

Figure 10.4 UM Main Menu

ACT: 5500FPx.y.z PRI: 5500FPx.y.z VALID
INACT:5500FPx.y.z DATE: hh:mn mm-dd-yyyy
REMV: 5500FPx.y.z SEC: 5500FPx.y.z
REMV: 5500FPx.y.z
header DATE: hh:mn mm-dd-yyyy

PRI: 5500FPx.y.z VALID PRI:x...x
SEC: 5500FPx.y.z
terminal DATE: hh:mn mm-dd-yyyy VALID SEC:x...x
screen REMV: 5500FPx.y.z
2 Reset local ac
menus 4 UM Advanced II Menu
6 Logout
Enter selection (by number): 2
__ 7. Enter 2 to “Reset local ac” and press RETURN.

Reset local ac
__ 8. Make sure SRM is inserted in the active AC and press RETURN.

Proceed with reset of local AC? (Y/N) Y
__ 9. Press “y” to reset local AC.

resetting AC ...
The local AC will reset immediately.
__ 10. Insert the APM into the inactive AC.
76.5500/29, Rev R 7/07 Page 29-1099

__ 11. Before proceeding, wait for the following messages to appear,

indicating that the standby AC hard disk is synchronized to the active
AC hard disk:
The following message can appear in any order, before, between, or
after the disk messages below.
/* Message Log Files Synchronization is complete*/
The two following messages must appear in the order shown.

/* Starting Inactive Database Synchronization *//*
Inactive Database Synchronized */
__ 12. Wait for the active and standby administration complexes to fully reset
and all the links to clear.
Finalizing Procedure
__ 1. Log on to link 1 of the active AC by entering the following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */

System response:
M ctag COMPLD

"AC-A::SWV=5500FPx.y.z, ALMPF=99:PST=IS-NR-ACT"
"AC-B::SWV=5500FPx.y.z, ALMPF=99:PST=IS-NR-STBY"
__ 2.1 Verify from the system response that the standby AC is

out-of-service, normal (OOS-NR) and the active AC
in-service, normal, active (IS-NR-ACT).
Page 29-1100 7/07 76.5500/29, Rev R

__ 3. Edit the standby AC in-service (IS) by entering the following command:

Where: x = AC that is OOS-NR.
System response:
M ctag COMPLD
__ 3.1 Wait for the messages stating that the inactive log files
and the inactive disk are synchronized before
proceeding to the next step.

System response:
M ctag COMPLD

"AC-A::SWV=5500FPx.y.z, ALMPF=99:PST=IS-NR-ACT"
"AC-B::SWV=5500FPx.y.z, ALMPF=99:PST=IS-NR-STBY"
__ 4.1 Verify that the active and standby ACs are in-service,
normal (IS-NR).
__ 5. Insert the SRM in the standby AC.

__ 6. Perform an AC copy switch to clear all visual alarms and reinstate all
valid alarms by entering the following command:
SW-DX-EQPT::AC-x:ctag;
Where: x = AC that is IS-NR-ACT (A or B).
System response:
M ctag COMPLD
Note: Both ACs will reset.
__ 7. Log back on to link 1 of the active AC by entering the following

command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */
76.5500/29, Rev R 7/07 Page 29-1101

__ 8. Retrieve the ACs by entering the following command:

System response:
M ctag COMPLD

"AC-A::SWV=5500FPx.y.z, ALMPF=99:PST=IS-NR-STBY"
"AC-B::SWV=5500FPx.y.z, ALMPF=99:PST=IS-NR-ACT"

are in-service, normal (IS-NR).
__ 9. Retrieve system condition states and verify that the residual alarms
have cleared by entering the following commands:
System response:
M ctag COMPLD
Note: If the residual alarms do not clear, follow your company's prescribed
North America).
__ 9.1 Correct any abnormal conditions before proceeding to

the next step.
Page 29-1102 7/07 76.5500/29, Rev R


RTRV-TMG:::ctag;
System response:
M ctag COMPLD
"NGC-A:::PST=IS-NR"
"NGC-B:::PST=IS-NR"

command:
System response:
M ctag COMPLD
":INH"
__ 11.1 If the system response shows that the system is not in

local restoration mode (INH), go to step 16,
page 29-1104.
__ 11.2 If the system response show that the system is in local

restoration mode (ALW), go to step 12, page 29-1103.
__ 12. Exit local restoration by entering the following command:

System response:
M ctag COMPLD
76.5500/29, Rev R 7/07 Page 29-1103


command:
System response:
M ctag COMPLD
":INH"

__ 14. Restore the user profile parameters to match the settings shown in
Table 10.1, page 29-1090.
SET-PROFILE-USER::uid:ctag::CRALM=[ON/OFF],MJALM=[ON/OFF],MNALM=[ON/OFF],
SYSMSG=[ON/OFF],SIRPT=[ON/OFF],AUD=[ON/OFF]:MLP=[ON/OFF];
Where: uid = User identification.
System response:
M ctag COMPLD
__ 15. Retrieve the user profile parameters:

RTRV-PROFILE-USER:::ctag;
System response:
M ctag COMPLD

"user:CRALM=ON,MJALM=ON,MNALM=ON,NAEVT=ON,CONDSCHED=ON,REPTSCHED=OFF,PMSCHED=ON,

were set back to the original state. Refer to Table 10.1,
page 29-1090.
__ 16. Cancel the user session by entering the following command:


__ 17. Inform network surveillance centers of the completion of this
maintenance procedure.
End of Procedure
Page 29-1104 7/07 76.5500/29, Rev R

Troubleshooting Manual 11. Checking the Power to a Shelf
11. Checking the Power to a Shelf
11.01 In this section, you will measure the voltages from the office Battery
Distribution Fuse Bay (BDFB) to the Breaker Frame/Alarm Panel (B/FAP) or Fuse
Frame/Alarm Panel (F/FAP) to verify that the Tellabs 5500/5500S digital
cross-connect is receiving outside power. You will also measure the voltages
between the feed and return connectors on the backplane of the B/FAP or F/FAP
and the input power connectors on the faulted shelf to verify that the shelf is
receiving power.
11.02 This procedure must be performed by qualified personnel only.
Warning:

__ 1.1 If you are checking power to a low density port shelf
(LDPS), go to Checking the Power to a LDPS, NC Shelf,
or AC Shelf, page 29-1106.
__ 1.2 If you are checking power to a high density port shelf

(HDPS) or a Consolidated Core Switch (CCS) shelf, go
to Checking the Power to an HDPS or a CCSS,
page 29-1116.
76.5500/29, Rev R 7/07 Page 29-1105

11. Checking the Power to a Shelf Troubleshooting Manual
Checking the Power to a LDPS, NC Shelf, or AC Shelf

__ 1. Verify that the power supply module (PPS) is seated securely in its
slot.
__ 2. Verify that the module tabs are in the lock position.
DANGER:
Hazardous Voltages: -48V to the system. Contact with the electrical current can
cause physical injury.
__ 3. Using a voltage meter, measure the voltages from the office BDFB to
the B/FAP. Refer to Figure 11.1, page 29-1107, and Figure 11.2,
page 29-1108.
__ 4. Verify that the voltage is in the acceptable range of -42Vdc to -56Vdc.
__ 5. Depending on the voltages obtained by the voltage meter, perform one
of the following steps:
__ 5.1 If the voltages are within the acceptable range, go to
step 6, page 29-1112.
__ 5.2 If the voltages read 0, the problem is with the BDFB.

Follow internal policy for checking and maintaining the
BDFB.
Page 29-1106 7/07 76.5500/29, Rev R

Figure 11.1 Rear of a Typical Rack Showing the Locations for Testing Power Distribution on AC Shelf
Feed/Return power from B/FAP to shelves. Refer to Figure
Breaker/Frame Alarm
Panel (B/FAP)
B RET
A RET
-48A
-48B
FRAME
ALARM NO NO
4 4 Caution 4 4 CONTACTS C C
3 3 3 3 NC NC
48 Volts
2 2 2 2 IN 4 IN 4
1 1 1 1 RET 4 RET 4
IN 3 IN 3
B Ret B Feeds B Ret B Feeds SHELFRET 3 RET 3
ALARM
GND Power from office BDFB to

J43
Input power from feed and -48VB

J40
B/FAP. Refer to Figure 11.2,
return to shelves, Copy B J59
J65
J66
page 29-1108.
side. Refer to Figure 11.5, P2-9 J10 J12 P2-3
J30
J31
J23
J22
J15
J14
page 29-1111. J56
J32
J33
J25
J24
J17
J16
J53
J57
J34
J35
J41
J27
J26
J19
J18
GND
J58
Input power from feed and
J36
J37
J42
J29
J28
J21
J20
J11 J13 -48VA
return to shelves, Copy A

side. Refer to Figure 11.5,
-4848V48V-48
RET RET
A A BB
page 29-1111.
TB1 64 64
EC1 1 EC2 EC3 1 EC4
8 7 6 5 4 3 2 1
TS2 TS1
J1 J1
-48 -48
COMM COMM
ALARM 1 ALARM 1
P8 P7 P6 P5 P4 P3 P2 P1 ALARM 2 ALARM 2 P8 P7 P6 P5 P4 P3 P2 P1
CHASSIS CHASSIS
GND GND
16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
DTE DTE
GND
J43
J40
-48VB
J59
J65
J66
P2-9 J10 J12 P2-3

J30
J31
J23
J22
J15
J14
J56
J32
J33
J25
J24
J17
J16
J53
J57
J34
J35
J41
J27
J26
J19
J18
GND
J58
J36
J37
J42
J29
J28
J21
J20
J11 J13 -48VA
76.5500/29, Rev R 7/07 Page 29-1107

Figure 11.2 Testing Power Input from the Office BDFB to the B/FAP
Power input from office BDFB

to B/FAP - red and black
Measure - 48V for

each pair of wires, Measure - 48V for
red and black each pair of wires, red
and black
Red
Red Black Black
CAUTION:
48 Volts
Measure - 48V for

Red Black Black Red each pair of wires,
Measure - 48V for red and black
each pair of wires, red
and black
Power input into the B/FAP - red and black
Note: The wires running from the office BDFB to the B/FAP are not always red
and black. They can be grey as well. However, industry standard calls for
red and black wires.
Page 29-1108 7/07 76.5500/29, Rev R

Figure 11.3 Locations for Testing Output Power from the Right Rear Side of the Feed/Return to the Shelves
Power to shelves
Power from
Breaker/Frame Red Black
Alarm Panel
4 4
3 3
2 2
1 1
A Feeds A Ret
Measure red at -48V, black as ground.

Repeat for both sides of rack. Refer to Figure
11.1, page 29-1107.
76.5500/29, Rev R 7/07 Page 29-1109

Figure 11.4 Locations for Testing Output Power from the Left Rear Side of the Feed/Return to the Shelves
Power to shelves
Power from
Black Red
Breaker/Frame
Alarm Panel
4 4
3 3
2 2
1 1
B Ret B Feeds
Measure red at -48V, black as ground.

Repeat for both sides of rack. Refer to Figure
11.1, page 29-1107.
Page 29-1110 7/07 76.5500/29, Rev R

Figure 11.5 Shelf Power Test Points (Administrative Complex Shelves and End Stage Shelf)
Shelf power test points with EMI shielding. Remove

two screws and pry off black plastic covers (using a
non-conductive device) to expose lug nuts and
screws.
Copy A Copy B
Ret A Ret B
Black
AMP
Measure - 48V Wires from B/FAP
between two
points on rear of
shelf
Red
AMP
Copy A Copy B
- 48A - 48B
76.5500/29, Rev R 7/07 Page 29-1111

Figure 11.6 Shelf Power Test Points (Center Stage Shelf)
Shelf power test points with EMI shielding. Remove

two screws and pry off black plastic covers (using a
non-conductive device) to expose lug nuts and
screws.
Wires from B/FAP
Red Black
Feed A Feed A
AMP
AMP -48 Vdc RETURN
Feed B Feed B
- 48 Vdc RETURN
Measure - 48V
between two
points on rear of
shelf
__ 6. Using a voltage meter, measure the voltage at the faulted shelf. Refer
to Figure 11.5, page 29-1111, and Figure 11.6.
__ 7. Verify that the voltage is in the acceptable range of -42Vdc to -56Vdc
for either PPS-A or PPS-B.
__ 8. Is the shelf voltage in the acceptable range?
Page 29-1112 7/07 76.5500/29, Rev R



pid = Password.
System response:
M ctag COMPLD
prosecution. */
__ 10. Retrieve the state of the shelf by entering the following commands
based on the type of shelf you are troubleshooting:
__ 10.1 For a port shelf, enter the following command:
Where: ee = Shelf type being grown (1 for DS1 port shelf, 1D

shelf, E for STS-1E port shelf, O3 for OC-3 port
shelf, O12, for OC-12 port shelf).
System response:
M ctag COMPLD

"PGC1D-0217:TYPE=11DD:ALMPF=99:PST=AS"
"PGC1D-0217-A:TYPE=11DD:HWV=81.5512B RA,SN=KL5069830,DT=960528:PST=IS-NR-ACT"
"PGC1D-0217-B:TYPE=11DD:HWV=81.5512B RA,SN=KL5069827,DT=960528:PST=IS-NR-STBY”
"PPS-0217-A::HWV=8X.5535,ALMPF=1:PST=NR”
"PPS-0217-B::HWV=8X.5535,ALMPF=1:PST=NR"
__ 10.1.1 If the present state of the power supply is

abnormal (ANR), follow your company's

normal (NR), the procedure is complete.
76.5500/29, Rev R 7/07 Page 29-1113

__ 10.2 For a network shelf, enter the following command:

M ctag COMPLD

M ctag COMPLD
"CCS-SH1,EQPT:MJ,FEED,NSA,08-09,09-16-49,NEND:\"Loss of power feed A to shelf

\":,ISLTD"
__ 10.2.1 If the system response lists a "Loss of

power feed A to shelf" message, go to
step 11.
__ 10.3 For an administrative complex shelf, enter the following

command:
System response:
M ctag COMPLD

"AC-B::SWV=5500FP10.0.X,ALMPF=99:PST=IS-NR-STBY"

abnormal (ANR), follow your company's

normal (NR), the procedure is complete.
Page 29-1114 7/07 76.5500/29, Rev R

DANGER:
__ 11. Verify that the circuit breaker switch for the faulted shelf is in the ON
position.
__ 11.1 If the circuit breaker is in the ON position, go to step 13.
__ 11.2 If the circuit breaker is in the OFF position, go to

step 12.
__ 12. Supply power to the faulted shelf by turning ON the appropriate

breakers on the B/FAP. Then go to step 6, page 29-1112.
__ 13. Turn off the circuit breaker to the affected shelf.
__ 14. Tighten the terminals on each end of the connecting wire.
__ 15. Turn on the circuit breaker to the affected shelf.
__ 16. Using a voltage meter, measure the voltage at the faulted shelf. Refer
to Figure 11.5, page 29-1111, and Figure 11.6, page 29-1112.
__ 17. Verify that the voltage is in the acceptable range of -42Vdc to -56Vdc
for either PPS-A or PPS-B.
__ 17.1 If the voltages are within the acceptable range, the
__ 17.2 If the voltages are not within the acceptable range, there
is potentially a problem with the circuit breaker switch
for the faulted shelf. Go to Replacing Parts in a
Breaker/Frame Alarm Panel (B/FAP), located in Tellabs
5500/5500S Replacement Procedures, 76.5500/55.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-1115

Checking the Power to an HDPS or a CCSS

11.03 Verify that the high density port shelf or consolidated core switch shelf is
receiving power by performing the following steps.
DANGER:
__ 1. To determine if power is supplied to the B/FAP or F/FAP from the

BDFB, check the status of the feed LEDs on the Breaker/Frame Alarm
Module (B/FAM) or Fuse/Frame Alarm Module (F/FAM). Refer to
Figure 11.7, page 29-1116, and Figure 11.8, page 29-1117.
__ 1.1 If the feed LED is off, go to step 2, page 29-1117.
__ 1.2 If the feed LED is green, go to step 5, page 29-1119.
__ 1.3 If the feed LED is red, go to step 9, page 29-1120.
Figure 11.7 B/FAM Front Panel LEDs
Frame Alarm
8X.5550H
Feed 3A Feed 3B
Feed 2A Feed 2B
Feed 1A Feed 1B
B/FAM
Shelf 3/Fan 3
Shelf 2/Fan 2
Shelf 1/Fan 1
CLEI Label W Date Revision
Page 29-1116 7/07 76.5500/29, Rev R

Figure 11.8 F/FAM Front Panel LEDs

82.5550HF
Frame Alarm
Feed 3A Feed 3B
Feed 2A Feed 2B
Feed 1A Feed 1B
FFAP
Shelf 3/ Fan 3
Shelf 2/ Fan 2
Shelf 1/ Fan 1
CLEI LABEL
W DATE REV
__ 2. Using a voltage meter, measure the voltages from the office BDFB to
the B/FAP or F/FAP.
Refer to Figure 11.9, page 29-1118, for an 82.5550H.
Refer to Figure 11.10, page 29-1118, for an 82.5550HF.
__ 3. Verify that the voltage is in the acceptable range of -42 Vdc to -56 Vdc.
__ 4. Depending on the voltages obtained by the voltage meter, perform one
of the following steps:
__ 4.1 If the voltages are within the acceptable range, go to
step 5, page 29-1119.
__ 4.2 If power is OFF and voltages read 0, the problem is with

the BDFB. Follow internal policy for checking and
maintaining the BDFB.
76.5500/29, Rev R 7/07 Page 29-1117

Figure 11.9 82.5550H Silkscreen Door and B/FAP Chassis

inside of B/FAP cover
Alarm Module -48V “B” Feeds Return

Return -48V “A” Feeds Frame The power sources for this
Alarm equipment must be protected
with a UL listed 60 A (maximum)
Feed 3A Feed 3B current limiting fuse or breaker.
Feed 2A Feed 2B 1B 2B 3B 1B 2B 3B
1A 2A 3A 1A 2A 3A Feed 1A Feed 1B CAUTION:
BFAM “for continued protection
NC 1 NC 2
Shelf 3 against risk of fire, replace (Torque to 40-in-lbs.) COM 2 CO
COM 1 CO only with same type and
NO 1 (Torque to 40-in-lbs.) Shelf 2 (1/4-20 Thd Size) NO 2
-48V -RTN (1/4-20 Thd Size) Shelf 1 rating of fuse” -RTN -48V
EQUIP Fan 3 3 Fan EQUIP
Shelf 3 Each equipment shelf is powered 3 ALARM Shelf 3
ALARM Tray 2 3 (5A) (5A) 2 Tray Fan 3
REF Fan 3 Fan from two -48VDC power sources Fan REF
1 1
EQUIP 2 RTN RTN RTN Tray 2 (5A) CAUTION Use caution when servicing or Tray 2 (5A)
RTN RTN RTN 2 EQUIP Shelf 2
Shelf 2 Failure (BLK) (BLK) (BLK) 1 (5A) 48 Volts disconnecting. 1 (5A) (BLK) (BLK) (BLK) Failure ALARM
ALARM 1 1 Fan 2
REF Fan 2 -48V -48V -48V 2 (5A) 2 (5A) -48V REF
Circuit Breakers “A” side Failure -48V -48V
EQUIP (RED) (RED) (RED) Failure 1 (5A)
Circuit Breakers “B” side
1 (5A) (RED) (RED) (RED) EQUIP
Shelf 1 Shelf 1 Shelf 2 Shelf 3 Shelf 1 Shelf 2 Shelf 3 ALARM Shelf 1
ALARM Shelf 1 Shelf 2 Shelf 3 Fan 1
REF Fan 1 (30A) (30A) (30A) Shelf 1 Shelf 2 Shelf 3 REF
(30A) (30A) (30A)
B/FAM
front of B/FAP (with cover lifted up)
Figure 11.10 5550HF F/FAP Chassis and Cover

inside of F/FAP cover
Alarm Module -48V “B” Feeds Return

Return -48V “A” Feeds Frame The power sources for this
equipment must be protected
CAUTION
Alarm
with a UL listed 60 A (maximum) CAUTION
current limiting fuse or breaker. 48 Volts DC
48 Volts DC Feed 3A Feed 3B
Feed 2A Feed 2B 1B 2B 3B 1B 2B 3B
1A 2A 3A 1A 2A 3A Feed 1A Feed 1B Each equipment shelf is powered
FFAP from two -48VDC power sources
NC 1 Use caution when servicing or NC 2
COM 1 CO Shelf 3 disconnecting. (Torque to 40-in-lbs.) COM 2 CO
NO 1 (Torque to 40-in-lbs.) Shelf 2 (1/4-20 Thd Size) NO 2
-48V -RTN (1/4-20 Thd Size) Shelf 1 -RTN -48V
EQP 3 CAUTION: 3 EQP
ALM Shelf 3 Fan 2 Fan 3 (5A) CAUTION: For continued protection against Fan 3 (5A) 2 Fan ALM Shelf 3
For continued protection against
REF 1 RTN RTN RTN risk of fire, replace only with same risk of fire, replace only with same 1 REF
Fan 2 (5A) type and rating of GMT fuse. Fan 2 (5A)
EQP 2 (BLK) (BLK) (BLK) type and rating of GMT fuse. RTN RTN RTN 2 EQP
Spare Fan 1 (5A) Fan 1 (5A) (BLK) Spare
ALM Shelf 2 1 -48V -48V -48V Protection Device “A” Side (BLK) (BLK) 1 ALM Shelf 2
Protection Device “B” Side
REF (RED) (RED) (RED) 2 (5A) 2 (5A) -48V -48V -48V REF
EQP 7.5 AMPS Spare
1 (5A) Shelf 1 Shelf 2 Shelf 3 Shelf 1 Shelf 2 Shelf 3 Spare
(5A) (RED) (RED) (RED) 7.5 AMPS EQP
Use only UL Listed 50A 1
ALM Shelf 1 MAX OUTPUT Shelf 3 Shelf 2 Shelf 1 Use only UL Listed 50A
Max current limiting fuses
MAX OUTPUT ALM Shelf 1
REF Max current limiting fuses Shelf 1 Shelf 2 Shelf 3 REF
F/FAM
front of F/FAP (with cover lifted up)
Page 29-1118 7/07 76.5500/29, Rev R

Figure 11.11 Shelf Power Test Points (Right Side)

Wires from B/FAP
Black
Red
Ret A -48V A
Figure 11.12 Shelf Power Test Points (Left Side)

Wires from B/FAP
Red
Black
-48V B Ret B
__ 5. Using a voltage meter, measure the voltage of the faulted port shelf.
Refer to Figure 11.11 and Figure 11.12.
__ 7. Is the shelf voltage in the acceptable range?
76.5500/29, Rev R 7/07 Page 29-1119

__ 8. Check the status of the LEDs on the front of each module on the
faulted port shelf.
__ 8.1 If any fault LEDs on the HDPS are lit red, refer to the
troubleshooting procedure for the faulted module, follow
technical assistance, or call Tellabs Technical
__ 8.2 If the status of the LEDs on the port modules is green,

the procedure is complete.
__ 8.3 If the power LEDs on all the modules in the shelf are lit
amber, follow your company's prescribed procedures
DANGER:
__ 9. Verify that the circuit breaker switch for the faulted shelf is in the ON
position. Refer to Figure 11.9, page 29-1118, for an 82.5550H.
__ 9.1 If the circuit breaker is in the ON position, go to step 11.
__ 9.2 If the circuit breaker is in the OFF position, go to

step 10.
__ 10. Supply power to the faulted shelf by turning ON the appropriate

breakers on the B/FAP. Then go to step 5, page 29-1119.
__ 11. Turn off the circuit breaker to the affected shelf. Or, remove the
appropriate fuse for the affected shelf.
__ 12. Tighten the terminals on each end of the connecting wire.
__ 13. Turn on the circuit breaker to the affected shelf. Or, insert the
appropriate fuse for the affected shelf.
__ 14. Using a voltage meter, measure the voltage of the faulted port shelf.
Refer to Figure 11.11, page 29-1119.
__ 15.1 If the voltages are within the acceptable range, the
__ 15.2 If the voltages are not within the acceptable range, there
is potentially a problem with the circuit breaker switch,
or fuse, for the faulted shelf. Go to step 16,
page 29-1121.
Page 29-1120 7/07 76.5500/29, Rev R

__ 16. Check the status of the feed LED on the Breaker/Frame Alarm Module
(B/FAM), or the Fuse/Frame Alarm Module (F/FAM). Refer to Figure
__ 16.1 If the feed LED is green there is a potential problem with
the wiring from the B/FAP or F/FAP to the shelf. Follow
__ 16.2 If the feed LED is red, and the breaker is in the ON

position, or the fuse is inserted, then the circuit breaker
or fuse is faulted. Go to Tellabs 5500/5500S
Replacement Procedures, 76.5500/55, to replace the
faulted circuit breaker or fuse.
End of Procedure
76.5500/29, Rev R 7/07 Page 29-1121

USER NOTES
Page 29-1122 7/07 76.5500/29, Rev R

Troubleshooting Manual 12. Restoring the System
12. Restoring the System
12.01 Two different mediums are available for restoring the Tellabs 5500/5500S
system data (DATA) and program software (PGM) bundles. These two mediums
are a remote server or a single removable media (SRM).
12.02 System restoration can also be performed using two different methods.
The first method of restoration can be performed using the CPY-MEM command.
The second method uses the Utility Mode (UM) when both AC-A and AC-B are
abnormal.
12.03 There are two different types of bundles that are needed to run a Tellabs
5500/5500S system. The two bundle types are system data (DATA) and program
software (PGM). System data consists of data such as the cross-connection
mapping information of a system. Program software is the current feature package
(FP) running on the system, plus any patches.
Note: Throughout this manual, the word “data” is used to refer to both system
data (DATA) and program software data (PGM). The acronym DATA is
used only in reference to system data, and the acronym PGM is used only
in reference to program software data.
12.04 In order to restore the system from either a remote server or an SRM using
UM, you must have two backup SRMs in order to bring the system into UM. If
restoring a system from a remote server, the backup SRMs only need the feature
package (PGM bundles) the system is currently running. The actual restoration of
the system will be done from the remote server; therefore, it is not necessary to
have the most current DATA and PGM bundles. However, if restoring the system
from an SRM, you must have two backup SRMs containing the most current DATA
and PGM bundles since the restoration of the system will be done from the SRMs.
Warning:
76.5500/29, Rev R 7/07 Page 29-1123

12. Restoring the System Troubleshooting Manual
System Requirements
12.06 Depending on if you are restoring the system using UM or the CPY-MEM
command, there are different system requirements that must be met in order to
perform this procedure. These requirements are listed under the following sub
headings for each method: UM or CPY-MEM command; and the medium type, a
remote server or an SRM.
__ 1. From the sub headings listed below, choose the appropriate method
(UM or the CPY-MEM command) and medium type (a remote server
or an SRM) that you are going to use for the restoration procedure, and
verify that the requirements are met before beginning this procedure.
__ 2. You must have a login privilege of A8 or greater. If you do not have a
login privilege of A8 or higher, contact your system administrator.
Restoring a System Using UM

12.07 The following requirements are necessary to restore a system using UM:
__ 1. Two terminals or personal computers (PCs) with terminal emulation
connected to link 1 on AC-A and link 5 on AC-B.
__ 1.1 Terminals must be configured for:
- 9600 baud
- 8 bits
- no parity
- 1 stop-bit
Note: If only one terminal is available, the terminal has to be reconnected to the
appropriate link for each switch from AC-A to AC-B.
Restoring a System Using the CPY-MEM Command

12.08 One operational SPM on either AC-A or AC-B is required to restore a
system using the CPY-MEM command.
Restoring a System from an SRM

12.09 Two backup SRMs with a copy of the most current DATA and PGM
bundles are required to restore a system from an SRM. These SRMs are needed
for both bringing the system into UM and restoration of the system. That is why it
is necessary for the SRMs to contain the most current DATA and PGM bundles.
Note: If only one SRM is available, the SRM has to be switched from AC-A to
AC-B.
Page 29-1124 7/07 76.5500/29, Rev R

Restoring a System from a Remote Server

12.10 The following requirements are necessary to restore a system from a
remote server:
• There are three major parameters you need to know to restore a
system from a remote server. These parameters are the server name,
your user ID used to login to the server, and the password ID
associated with your user ID. If the remote server is configured to
transfer files via SFTP, the password ID may be omitted if the Tellabs
5500 system’s public key is installed on the remote server. For more
information about installing the public key on a remote server, refer to
Tellabs 5500 System Administration Manual, 76.5500/9.
• Two backup SRMs containing the feature package (PGM bundles) the
system is currently running are required. These SRMs are needed
only to bring the system into UM; therefore, it is not necessary for the
SRMs to contain the most current DATA and PGM bundles, since the
restoration of the system will be performed from the remote server.
Getting Started
12.11 System restoration can be performed using the CPY-MEM command or
using UM when your system does not have an operational SPM on either AC-A or
AC-B.
__ 1. Depending on if you are going to restore a system using UM or the
CPY-MEM command, choose one of the following:
__ 1.1 To restore a system using UM, go to Restoring a
System Using Utility Mode (UM), page 29-1126.
__ 1.2 To restore a system using the CPY-MEM command, go

to Restoring a System Using the CPY-MEM Command,
page 29-1164.
76.5500/29, Rev R 7/07 Page 29-1125

Restoring a System Using Utility Mode (UM)

12.12 This section provides the necessary steps for restoring the Tellabs
5500/5500S DATA and PGM bundles using UM. This procedure is used when the
APM in both AC-A and AC-B is abnormal.
Note: If at any time during this procedure the intended system response does not
appear, or if alarms or conditions are received, follow your company's
Caution:
Failure to follow these steps precisely may result in traffic loss.
12.13 Two different mediums are available to use in this restoration procedure.
These two mediums are a remote server or an SRM. Once in UM, the system will
prompt you to choose between restoring the system from an SRM or a remote
server.
__ 1. Depending on if you are restoring the system from an SRM or a remote
server, choose one of the following:
__ 1.1 If you are restoring the system from an SRM, verify that
you have two backup SRMs with a copy of the most
current DATA and PGM bundles stored on them. If not,
obtain them before continuing with this procedure.
__ 1.2 If only one SRM is available, the SRM has to be

switched from AC-A to AC-B, or from AC-B to AC-A.
__ 1.3 If you are restoring the system from a remote server,

verify that you have two backup SRMs containing the
feature package (PGM bundles) the system is currently
running. If not, obtain them before continuing with this
procedure.

__ 2.1 If there are SRMs present in the Data Storage Modules
(DSMs), go to step 3.
__ 2.2 If there are no SRMs present in the DSMs, go to step 4.
__ 3. Remove the SRMs from both DSMs.

__ 4. Insert the backup SRMs into the DSMs.
__ 4.1 Before proceeding, wait until the green LED on the
Removable Storage Drive (RSD) turns off for a 5502D
DSM.
Page 29-1126 7/07 76.5500/29, Rev R

Entering UM
Caution:
Do not pull any modules or enter commands when the hard drive activity LED is
lit. If the DSM is interrupted while copying or formatting, the contents on the hard
disk drive could be corrupted or improperly formatted.
__ 1. Check the hard drive activity LED on DSM-B. If this LED is flashing,
wait until it stops before proceeding.
__ 1.1 Unseat the SPM in the APM slot in AC-B to disconnect
it from the backplane.
__ 1.2 Unseat the AIM in AC-B so that it is disconnected from

the backplane.
__ 2. Check the hard drive activity LED on DSM-A. If this LED is flashing,
wait until it stops before proceeding.
__ 2.1 Unseat the SPM in the APM slot in AC-A to disconnect
it from the backplane.
__ 2.2 Unseat the AIM in AC-A to disconnect it from the

backplane.
Note: After performing the following step, the system can take 5 to 15 minutes to
respond with a UM prompt.
__ 3. Reseat the SPM slot of AC-B.

__ 3.1 Verify that the system responds with the UM prompt on
link 5 before proceeding to the next step.
UM>
Note: After performing the following step, the system can take 5 to 15 minutes to
respond with a UM prompt.
__ 4. Reseat the SPM in the APM slot in AC-A.

__ 4.1 Verify that the system responds with the UM prompt on
link 1 before proceeding to the next step.
UM>
76.5500/29, Rev R 7/07 Page 29-1127

Restoring Software on AC-A

__ 1. Enter the appropriate utility mode password at the UM prompt.
System response:
__ 1.1 Press <RETURN>.
__ 1.2 The system displays the Utility Mode Main Menu. Refer
to Figure 12.1.
Note: Until the hard disk drive is formatted and partitioned, disregard the FP
information in PRI and SEC for Program and Database version.
Figure 12.1 Sample UM Main Menu
Boot Directory: TITANX

ACT: 5500FPX.Y.Z PRI: 5500FPx.y.z VALID
DATE: 15:21 02-07-2001
INACT: SEC:
REMV: 5500FPx.y.z REMV

PRI: 5500FPx.y.z VALID PRI: TELLABS
DATE: 15:21 02-07-2001
SEC: SEC:
REMV: REMV:

2 Reset local ac
4 UM Advanced II Menu
6 Logout
Enter selection (by number):
__ 2. Enter 3 to select the UM Advanced I Menu.

__ 2.2 The system displays the UM Advanced I Menu. Refer to

Figure 12.2, page 29-1129.
Page 29-1128 7/07 76.5500/29, Rev R

Figure 12.2 Sample UM Advanced I Menu
1 Change SID on pri, sec, or remv

2 Change UM password
3 View Utility Mode log
4 System installation
5 Replace data storage module (DSM)
6 Emergency Recovery Options
7 Return to previous menu
8 Logout
__ 3. Enter 6 to select the Emergency Recovery Options Menu.

__ 3.2 The system displays the Emergency Recovery Options

Menu. Refer to Figure 12.3.
__ 4. Depending on if you are restoring the system using an SRM or a

remote server, choose one of the following:
__ 4.1 If you are restoring the system from an SRM, go to
Restoring Software on AC-A from an SRM,
page 29-1129.
__ 4.2 If you are restoring the system from a remote server,

go to Restoring Software on AC-A from a Remote
Server, page 29-1144.
Restoring Software on AC-A from an SRM

12.14 Perform the following steps to restore the system using data from an SRM.
Figure 12.3 Sample UM Emergency Recovery Options Menu.
1 Recovery from removable media

2 Recovery from remote server
4 Logout
__ 1. Enter 1 to recover from removable media.

System response:
Recover from removable media
Forced mode copy? (Y/N)
76.5500/29, Rev R 7/07 Page 29-1129

__ 2. Enter N to not recover from forced mode.

System response:
__ 3. Verify that the SRM is present.

System response:
Proceed with copying Emergency Archive recovery files to PRI? (Y/N)
Note: The following command takes about 10 minutes to complete.
__ 4. Enter Y to start the restoration process.

System response:
Formatting volume A ...
Formatting volume B ...
Formatting volume C ...
Formatting volume D ...
format and partition entire disk complete
copying bootloader to disk ...
copy bootloader to disk complete
Copying of Emergency Archive recovery files in progress .....
copying archive program bundle ...
copy archive program bundle complete
copying archive data bundle ...
copy archive data bundle complete
Copying of Emergency Archive recovery files complete.
__ 5. Press <RETURN>.
Menu. Refer to Figure 12.4, page 29-1131.
Page 29-1130 7/07 76.5500/29, Rev R


4 Logout
__ 6. Enter 3 to return to previous menu.


Figure 12.5.

8 Logout
__ 7. Enter 1 to Change SID on pri, sec, or remv.

System response:
Enter new System ID:
__ 8. Enter current system ID.

System response:
Select Primary, Secondary, or Removable Memory
(P/S/R):
__ 9. Enter P for Primary.

System response:
Proceed with change SID [system_id] to PRI? (Y/N)
76.5500/29, Rev R 7/07 Page 29-1131

__ 10. Enter Y to change the system ID on PRI memory.

System response:
changing System ID ...
WARNING: You have just changed the SID from the VIRGIN SID in the PRIMARY memory of
this disk. The database present may be VIRGIN,and if it came ACTIVE on a LIVE traffic
system,ALL TRAFFIC WILL BE LOST.Please be sure that the other Admin Complex is ACTIVE
before resetting this Admin Complex.
change System ID complete
System response:
Retrieving version information from removable device...

8 Logout

__ 12.1 Verify that the boot loader version in active memory is
the correct feature package.
__ 12.2 Verify that the program version in primary memory is the

correct feature package.
__ 12.3 Verify that the database version in primary memory is

__ 12.4 If the boot loader version in ACT memory is not the

correct feature package or the program version in PRI
memory is not the correct feature package, follow your
Page 29-1132 7/07 76.5500/29, Rev R


__ 13.2 The system displays the UM Main Menu. Refer to

Figure 12.7, page 29-1133.
__ 14. Reseat the AIM into the slot in AC-A.

ACT: 5500SFPx.y.z PRI: 5500SFPx.y.z VALID
INACT:5500SFPx.y.z DATE: hh:mn mm-dd-yyyy
REMV: 5500SFPx.y.z SEC: 5500SFPx.y.z
REMV: 5500SFPx.y.z

PRI: 5500SFPx.y.z VALID PRI:x...x
SEC: 5500SFPx.y.z
DATE: hh:mn mm-dd-yyyy VALID SEC:x...x
REMV: 5500SFPx.y.z
2 Reset local ac
6 Logout
__ 15. Enter 2 to reset local AC.

System response:
Reset local ac
Please make sure that the removable media is inserted.

System response:
Proceed with reset of local AC? (Y/N)
Note: This process takes 10 to 20 minutes.
76.5500/29, Rev R 7/07 Page 29-1133

__ 17. Enter Y to reset local AC.

System response:
resetting AC...
S 0 REPT SYS /* Bootloader initialization in progress */
S 0 REPT SYS /* AC loading from [A/C]:\TITAN[X/Y] */
S 0 REPT SYS /* Base Load = 1100 Active Patch Load = 000 */
S 0 REPT SYS /* AC loading complete */
/*AC initialization to inactive status has begun*/
/*AC initialization to inactive status has completed successfully*/
“LINK-1:CL,OSLINK,NSA,15:21 02-07-2001,NEND:\”CLR “Lost Operation Link

Communication.\”;
__ 17.2 Verify that a system response similar to the one listed

above was received before continuing with this
procedure.


pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
Page 29-1134 7/07 76.5500/29, Rev R

__ 19. Retrieve the present state of AC-A by entering the following command:
RTRV-EQPT::AC-A::ctag;
System response:
M ctag COMPLD

“AC-A::SWV=5500FPx.y.z,ALMPF=99:PST=IS-NR-ACT”
__ 19.1 Verify from the system response that AC-A is

Restoring Software on AC-B from an SRM

__ 1. If only one terminal is available, reconnect the terminal to link 5 on
AC-B.
Note: While Utility Mode is accessed, the LED on the SPM (APM functionality)
for AC-B will be flashing.
__ 2. Enter the appropriate utility mode password at the UM prompt.
System response:
__ 2.1 Press <RETURN>
to Figure 12.8.
76.5500/29, Rev R 7/07 Page 29-1135


REMV: 5500SFPx.y.z

SEC: 5500SFPx.y.z
REMV: 5500SFPx.y.z
2 Reset local ac
6 Logout


Figure 12.9, page 29-1137.
Page 29-1136 7/07 76.5500/29, Rev R


8 Logout
__ 4. Enter 6 to select the Emergency Recovery Options menu.



4 Logout
__ 5. Enter 1 for Recovery from removable media.

System response:
Recover from removable media

System response:

System response:
Proceed with copying Emergency Archive recovery files to PRI? (Y/N)
76.5500/29, Rev R 7/07 Page 29-1137


System response:
Copying of Emergency Archive recovery files in progress .....
copying archive program bundle ...
copy archive program bundle complete
copying archive data bundle ...
copy archive data bundle complete
Copying of Emergency Archive recovery files complete.

4 Logout


Figure 12.12, page 29-1139.
Page 29-1138 7/07 76.5500/29, Rev R


8 Logout

System response:

System response:
Select Primary, Secondary, or Removable Memory (P/S/R):

System response:
Proceed with change SID to [system_id] on PRI? (Y/N)

System response:
System response:
76.5500/29, Rev R 7/07 Page 29-1139


8 Logout




correct feature package, or the program version in PRI


Figure 12.14, page 29-1141.
__ 18. Reseat AIM into the slot in AC-B.
Page 29-1140 7/07 76.5500/29, Rev R


REMV: 5500SFPx.y.z

SEC: 5500SFPx.y.z
REMV: 5500SFPx.y.z
2 Reset local ac
6 Logout

System response:
Reset local AC

System response:
76.5500/29, Rev R 7/07 Page 29-1141


System response:
resetting AC...
“LINK-5:CL,OSLINK,NSA,15:21 02-07-2001,NEND:\”CLR “Lost Operation Link

Communication.\”;

procedure.
__ 22. Log back on to the system by entering the following command:


pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
Page 29-1142 7/07 76.5500/29, Rev R

command:
RTRV-EQPT::AC-A&&B:ctag;
System response:
M ctag COMPLD

“AC-B::SWV=5500FFPx.y.z,ALMPF=99:PST=IS-NR-STBY”

__ 23.2 If the AC is not in-service, normal, active (IS-NR-ACT),

go to Section 2, Troubleshooting the Administrative
Complex, page 29-53, to resolve the problem before
command:
System response:
M ctag COMPLD

Hybrid Core Switch:


__ 24.1 Verify from the system response that both NCs are
76.5500/29, Rev R 7/07 Page 29-1143

__ 25. Retrieve the status of the Primary (PRI) memory by entering the
following command:
System response:
“:PRI-A,PGM:961118,18-25,FULL,FULL,5500FPx.y.z,,VALID,ACTIVE,SYNC”
“:PRI-A,DATA:961118,18-25,FULL,FULL,5500FPx.y.z,TELLABS,VALID,ACTIVE,SYNC”
“:PRI-B,PGM:961118,18-25,FULL,FULL,5500FPx.y.z,,VALID,STANDBY,SYNC”
“:PRI-B,DATA:961118,18-25,FULL,FULL,5500FPx.y.z,TELLABS,VALID,STANDBY,SYNC”
__ 25.1 Verify from the system response that the PGM and
DATA bundles for both PRI-A and PRI-B are at the
DATA bundles for both PRI-A and PRI-B are valid
(VALID).
DATA bundles for both PRI-A and PRI-B are
synchronous (SYNC).
__ 25.4 Verify from the system response that PRI-A PGM and
DATA bundles are active (ACTIVE).
__ 25.5 Verify from the system response that PRI-B PGM and
DATA bundles are standby (STANDBY).
__ 26. Proceed to Completing Restoration, page 29-1173.
Restoring Software on AC-A from a Remote Server

12.15 Perform the following steps to restore the system using UM from a remote
server.

4 Logout
Page 29-1144 7/07 76.5500/29, Rev R

__ 1. Enter 2 to recover from remote server.

System response:
Recover from remote server

System response:
Please insert LSM and wait until initialzed to proceed.
__ 3. Verify that the LAN Switch Module (LSM) is equipped.

__ 3.1 Verify that the LSM Active and In-service LEDs are
green.
System response:
Proceed with copying Emergency remote recovery files to PRI? (Y/N)
Note: The following command takes about 10 minutes to complete. As the

system response scrolls down the screen, you will be prompted to answer
various questions. Follow the steps listed in between the system response
display in order to complete the restoration procedure.

System response:
Select Source of Program Files: REMV or remote Server (R/S):
__ 5. Enter S to restore from a remote server.

Enter Local NE IP Address:
76.5500/29, Rev R 7/07 Page 29-1145

__ 6. Enter local NE IP address.

Enter Local NE Subnet Mask (Optional):
__ 7. This is optional, enter local NE Subnet Mask or skip to substep 7.1.

Enter Local NE Gateway Address (Optional):
__ 8. This is optional, enter local NE Gateway Address or skip to

substep 8.1.
Enter Remote Server IP Address:
__ 9. Enter remote server IP address.

Enter Remote Server Username:
__ 10. Enter remote server user name.

Enter Remote Server Password:
__ 11. Enter remote server password.

Enter Port Number (21):
__ 12. Enter port number.

Enter Working Directory Name (TELLABS/T5500):
__ 13. Enter working directory name.

Enter System ID:
__ 14. Enter system ID.

Enter the Software Version (Ex. FPx.y.z):
Page 29-1146 7/07 76.5500/29, Rev R

__ 15. Enter the software version.

Copying Emergency Program Recovery files in progress .....
Copying Emergency Program Recovery files SUCCESSFUL
Copying Emergency Data Recovery files in progress .....
Copying Emergency Data Recovery files SUCCESSFUL
Copying of Emergency Remote recovery files SUCCESSFUL

Figure 12.16 Sample UM Emergency Recovery Options Menu

4 Logout


Figure 12.17, page 29-1147.

8 Logout

System response:
76.5500/29, Rev R 7/07 Page 29-1147


System response:

System response:
Proceed with change to SID [system_id] on PRI? (Y/N)

System response:
System response:

8 Logout



Page 29-1148 7/07 76.5500/29, Rev R




Figure 12.19, page 29-1149.
__ 25. Reseat the AIM into the slot in AC-A.

REMV: 5500SFPx.y.z

SEC: 5500SFPx.y.z
REMV: 5500SFPx.y.z

2 Reset local ac
6 Logout

System response:
Reset local ac
76.5500/29, Rev R 7/07 Page 29-1149


System response:

System response:
M ctag COMPLD

resetting AC...
“LINK-1:CL,OSLINK,NSA,15:21 02-07-2001,NEND: \”CLR “Lost Operation Link

Communication.\”;

procedure.
Page 29-1150 7/07 76.5500/29, Rev R



pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
__ 30. Retrieve the present state of AC-A by entering the following command:
RTRV-EQPT::AC-A::ctag;
System response:
M ctag COMPLD

__ 30.1 Verify from the system response that AC-A is

Restoring Software on AC-B from a Remote Server

__ 1. If only one terminal is available, reconnect the terminal to link 5 on
AC-B.
__ 2. Enter the password on link 5.
System response:
__ 2.1 Press <RETURN>
to Figure 12.20.
76.5500/29, Rev R 7/07 Page 29-1151


REMV: 5500SFPx.y.z

SEC: 5500SFPx.y.z
REMV: 5500SFPx.y.z
2 Reset local ac
6 Logout


Figure 12.21.

8 Logout
__ 4. Enter 6 to select the Emergency Recovery Options Menu.


Menu. Refer to Figure 12.22, page 29-1153.
Page 29-1152 7/07 76.5500/29, Rev R


4 Logout
__ 5. Enter 2 to recover from remote server.

System response:
Recover from a remote server

System response:
Please insert LSM and wait until initialzed to proceed.
__ 7. Verify that the LAN Switch Module (LSM) is equipped.

__ 7.1 Verify that the LSM Active and In-service LEDs are
green.
System response:
Proceed with copying Emergency remote recovery files to PRI? (Y/N)
76.5500/29, Rev R 7/07 Page 29-1153

Note: The following command takes about 10 minutes to complete. As the

system response scrolls down the screen, you will be prompted to answer
various questions. Follow the steps listed in between the system response
display in order to complete the restoration procedure.

Select Source of Program Files: REMV or remote Server (R/S):
__ 9. Enter S to restore from a remote server.

Enter Local NE IP Address:
__ 10. Enter local NE IP address.

Enter Local NE Subnet Mask (Optional):
__ 11. (Optional) Enter local NE Subnet Mask or skip to substep 11.1.

Enter Local NE Gateway Address (Optional):
__ 12. (Optional) Enter local NE Gateway Address or skip to substep 12.1.

Enter Remote Server IP Address:
__ 13. Enter remote server IP address.

Enter Remote Server Username:
__ 14. Enter remote server user name.

Enter Remote Server Password:
Page 29-1154 7/07 76.5500/29, Rev R

__ 15. Enter remote server password.

Enter Port Number (21):
__ 16. Enter port number.

Enter Working Directory Name (TELLABS/T5500):
__ 17. Enter working directory name.

Enter System ID:
__ 18. Enter system ID.

Enter the Software Version (Ex. FPx.y.z):
__ 19. Enter the software version.

Copying Emergency Program Recovery files in progress .....
Copying Emergency Program Recovery files SUCCESSFUL
Copying Emergency Data Recovery files in progress .....
Copying Emergency Data Recovery files SUCCESSFUL
Copying of Emergency Remote recovery files SUCCESSFUL


4 Logout


Figure 12.24, page 29-1156.
76.5500/29, Rev R 7/07 Page 29-1155


8 Logout
__ 22. Enter 1 to change the system ID.

System response:

System response:

System response:
Proceed with change to SID [system_id] on PRI? (Y/N)

System response:
System response:
Page 29-1156 7/07 76.5500/29, Rev R


8 Logout






Figure 12.26.
__ 29. Reseat the AIM into the slot in AC-B.
76.5500/29, Rev R 7/07 Page 29-1157


REMV: 5500SFPx.y.z

SEC: 5500SFPx.y.z
REMV: 5500SFPx.y.z
2 Reset local ac
6 Logout

System response:
Reset local ac

System response:
Page 29-1158 7/07 76.5500/29, Rev R


Sample system response:

resetting AC...
“LINK-5:CL,OSLINK,NSA,15:21 02-07-2001,NEND: \”CLR “Lost Operation Link

Communication.\”;

procedure.


pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
76.5500/29, Rev R 7/07 Page 29-1159

command:
System response:
M ctag COMPLD

“AC-B::SWV=5500FFPx.y.z,ALMPF=99:PST=IS-NR-STBY”

command:
System response:
M ctag COMPLD

Hybrid Core Switch:


Page 29-1160 7/07 76.5500/29, Rev R

__ 36. Retrieve the status of the PRI memory by entering the following
command:
System response:
M ctag COMPLD

(VALID).
synchronous (SYNC).
__ 37. Copy the current DATA and PGM bundles from PRI memory to SEC
memory by entering the following command:
CPY-MEM::FROMMEM=PRI,TOMEM=SEC:ctag::ALL;
System response:
M ctag COMPLD

SEC-B: CL,NUMEMS,NSA,15:21 02-07-2001,NEND:
/*CLR-Secondary memory data and program bundles are invalid/””
76.5500/29, Rev R 7/07 Page 29-1161

__ 38. Retrieve the status of the SEC memory by entering the following
command:
System response:
M ctag COMPLD

“:SEC-A,PGM:961120,18-25,FULL,5500FPx.y.z,,VALID,ACTIVE”
“:SEC-A,DATA:961120,18-25,FULL,5500FPx.y.z,TELLABS,VALID,ACTIVE”
“:SEC-B,PGM:961120,18-25,FULL,5500FPx.y.z,,VALID,STANDBY”
“:SEC-B,DATA:961120,18-25,FULL,5500FPx.y.z,TELLABS,VALID,STANDBY”
DATA bundles for both SEC-A and SEC-B are at the
DATA bundles for both SEC-A and SEC-B are valid
(VALID).
__ 38.3 Verify from the system response that SEC-A PGM and
__ 38.4 Verify from the system response that SEC-B PGM and
__ 39. Copy the current DATA and PGM bundles from SEC memory to a
remote server by entering the following command:
CPY-MEM::FROMMEM=SEC,TOSVR=aaaa:ctag::ALL,bbbb,cccc;
Where: aaaa = Name of the server.

bbbb = Your user ID needed to login to the remote server.
cccc = Your password ID associated with the user ID.
Example:
CPY-MEM::FROMMEM=SEC,TOSVR=NYSERVER:dm::ALL,"mmousel","BlueMoon9";
Sample system response:

TELLABS 01-01-23 14:46:01
M ctag COMPLD
Page 29-1162 7/07 76.5500/29, Rev R

__ 40. Retrieve the remote server by entering the following command:

RTRV-MEMSTAT-MEM::SERVER:ctag::ALL,aaaa,"bbbb","cccc";
Where: aaaa = Name of the server.

bbbb = Your user ID need to login to the remote server.
cccc = Your password ID associated with the user ID.
System response:
M ctag COMPLD

“SERVERX,PGM:000713,02-15,FULL,5500FPx.y.z,,VALID”
“SERVERX,DATA:000713,02-15,FULL,5500FPx.y.z,TELLABS,VALID”
__ 40.1 Verify that both the PGM and DATA bundles are Valid
(VALID).
__ 40.2 Verify the date and time stamp of the system response
corresponds to the header date and time stamp listed
above the M ctag COMPLD response from step 39,
page 29-1162.
__ 40.3 Verify the system ID corresponds with the system ID

listed above the M ctag COMPLD response from step
39, page 29-1162.
__ 40.4 If the INVALID still appears, discontinue this procedure

and follow your company's prescribed procedures for
End of Procedure
76.5500/29, Rev R 7/07 Page 29-1163

Restoring a System Using the CPY-MEM Command

12.16 This section provides the necessary steps for restoring the Tellabs
5500/5500S DATA and PGM bundles using the CPY-MEM command. This method
is used if there is an operational SPM, acting as an APM, which is in the present
state of in-service, normal, active (IS-NR-ACT).
12.17 Two different mediums are available to use in this restoration procedure.
These two mediums are a remote server or an SRM.
12.18 There are three major parameters you need to know to restore a system
from a remote server. These parameters are the server name, your user ID used
to login to the server, and the password ID associated with your user ID. If the
remote server is configured to transfer files via SFTP, the password ID may be
omitted if the Tellabs 5500 system’s public key is installed on the remote server.
For more information about installing the public key on a remote server, refer to
Tellabs 5500 System Administration Manual, 76.5500/9.
12.19 When restoring the system from a remote server, it is necessary to first
copy the data from the remote server to intermediate memory (IMED); then copy
the data from IMED to secondary memory (SEC); then use the INIT-SYS command
to swap the data from SEC memory to Primary (PRI) memory.
12.20 When restoring the system from an SRM, it is necessary to first copy the
data from REMV memory to SEC memory; then use the INIT-SYS command to
swap the data from SEC memory to PRI memory.
12.21 When restoring the system, there are two different types of data bundles
that you need to restore. The two data bundle types are PGM for program software
and DATA for system data. Specifying the “ALL” parameter when executing the
CPY-MEM command ensures that both the DATA and PGM bundles are restored
to the system. The system default is “ALL.”
Caution:
Failure to follow these steps precisely may result in traffic loss.
Warning:
Page 29-1164 7/07 76.5500/29, Rev R

Performing Preliminary System Checks

12.23 In this section, perform the following steps to ensure the system is in the
proper state to perform the procedure.
Note: If at any time during this procedure the intended system response does not
appear, or if alarms or conditions are received, follow your company's

following command:

pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
hh = Hour, 0 - 23.
__ 2. Retrieve your user profile to verify that your login has been assigned
the proper user privilege code (UPC) to perform these procedures by

System response:
M ctag COMPLD

__ 2.1 Verify that your login has a UPC of A8 or higher.

76.5500/29, Rev R 7/07 Page 29-1165

__ 3. Activity from remote terminals could disrupt recovery procedures.

Notify other personnel using the Tellabs 5500/5500S system that they
are being logged off.
__ 4. Put the system in local restoration mode, using the appropriate link, by

M ctag COMPLD

WARNING: All other user sessions and scheduled reports will be terminated.
M ctag COMPLD

following command:
System response:
M ctag COMPLD

":ALW:UPGRADE=NO"
__ 5.1 Verify from the system response that the system is in

local restoration mode (ALW).
__ 6. Depending on if you are going to restore a system from an SRM or a

remote server, choose one of the following:
__ 6.1 To restore a system from an SRM, go to Restoring a
System from an SRM, page 29-1167.
__ 6.2 To restore a system from a remote server, go to

Restoring a System from a Remote Server,
page 29-1170.
Page 29-1166 7/07 76.5500/29, Rev R

Restoring a System from an SRM

12.24 In this section, you will perform the procedure to restore a system from an
SRM.
12.25 When restoring a system from an SRM, it is necessary to first copy the
data from the REMV memory to SEC memory. Then use the INIT-SYS command
to swap the data from SEC memory to PRI memory.
__ 1.1 If there are SRMs present in the Data Storage Modules
(DSMs), go to step 2.
__ 1.2 If there are no SRMs present in the DSMs, go to step 3.
__ 2. Remove the SRMs from both DSMs.

__ 3. Insert the back up SRMs containing the desired data to be restored
into the DSMs.
__ 3.1 Before proceeding, wait until the green LED on the
Removable Storage Drive (RSD) turns on for a 5502D
DSM.
__ 4. Retrieve the status of the REMV memory by entering the following

command:
System response:
M ctag COMPLD

“:REMV-A,PGM:961120,18-25,FULL,5500FPx.y.z,,VALID,ACTIVE”
“:REMV-A,FP:961120,18-25,FULL,5500FPx.y.z,,VALID,ACTIVE”
“:REMV-A,DATA:961120,18-25,FULL,5500FPx.y.z,TELLABS,VALID,ACTIVE”
“:REMV-B,PGM:961120,18-25,FULL,5500FPx.y.z,,VALID,STANDBY”
“:REMV-B,FP:961120,18-25,FULL,5500FPx.y.z,,VALID,STANDBY”
“:REMV-B,DATA:961120,18-25,FULL,5500FPx.y.z,TELLABS,VALID,STANDBY”
DATA bundles for both REMV-A and REMV-B are at the
__ 4.2 Verify from the system response that the system ID is

correct.
76.5500/29, Rev R 7/07 Page 29-1167

__ 5. Copy data from REMV memory to SEC memory by entering the

following command:
CPY-MEM::FROMDEV=REMV,TOMEM=SEC:ctag::ALL;
System response:
M ctag COMPLD

command
System response:
M ctag COMPLD
Followed by lines of data similar to the following example:

(VALID).
__ 6.3 Verify from the system response that PGM and DATA
bundles for the active SEC are VALID.
bundles for the standby SEC are VALID.
INIT-SYS:::ctag::2;
System response:
M ctag COMPLD
Note: The AC will now reset. The reset will take approximately five minutes.
Page 29-1168 7/07 76.5500/29, Rev R



pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
command:
System response:
M ctag COMPLD

(VALID).
synchronous (SYNC).
76.5500/29, Rev R 7/07 Page 29-1169

Restoring a System from a Remote Server

12.26 In this section, you will perform the procedure to restore a system from a
remote server.
12.27 When restoring a system from a remote server, it is necessary to first copy
the data from the remote server to Intermediate memory (IMED); then copy the
data from IMED to Secondary memory (SEC); then use the INIT-SYS command to
swap the data from SEC memory to Primary (PRI) memory.
12.28 There are three major parameters you need to know to restore a system
from a remote server. These are the server name, your user ID used to login to the
server, and the password ID associated with your user ID. If the remote server is
configured to transfer files via SFTP, the password ID may be omitted if the Tellabs
5500 system’s public key is installed on the remote server. For more information
about installing the public key on a remote server, refer to Tellabs 5500 System
Administration Manual, 76.5500/9.
__ 1. Copy data from the remote server to IMED by entering the following
command:
CPY-MEM::FROMSVR=aaaa,TOMEM=IMED:ctag::ALL,"bbbb","cccc";
Where: aaaa = Name of the remote server.

bbbb = Your user ID to login to the remote server.
cccc = Your password ID associated with user ID.
System response:
M ctag COMPLD
__ 2. Retrieve the status of the IMED memory by entering the following

command:
RTRV-MEMSTAT-MEM::IMED:ctag;
System response:
M ctag COMPLD

":IMED-A,PGM:010531,12-14,FULL,5500FFPx.y.z,,VALID,ACTIVE"
":IMED-A,DATA:010531,12-18,FULL,5500FPx.y.z,TELLABS,VALID,ACTIVE"
"IMED-A:ERCDE=SDNC,PRMTR=AID&MEMUSG,MEMUSG=UPGRADE"
/* Requested memory bundle not found */
"IMED-B:ERCDE=SDNC,PRMTR=AID&MEMUSG,MEMUSG=PGM"
"IMED-B:ERCDE=SDNC,PRMTR=AID&MEMUSG,MEMUSG=DATA"
"IMED-B:ERCDE=SDNC,PRMTR=AID&MEMUSG,MEMUSG=UPGRADE"
DATA bundles for the active AC has the correct feature
package.
DATA bundles for the active AC are valid (VALID).
__ 2.3 Verify from the system response that the active AC

PGM and DATA bundles are active (ACTIVE).
Page 29-1170 7/07 76.5500/29, Rev R

__ 3. Copy data from the IMED to SEC memory by entering the following
command:
CPY-MEM::FROMMEM=IMED,TOMEM=SEC:ctag::ALL;
System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD
Followed by lines of data similar to the following example, if copied to

both ACs:
(VALID).
__ 4.3 Verify from the system response that active AC PGM

and DATA bundles are active (ACTIVE).
__ 4.4 Verify from the system response that standby AC PGM

and DATA bundles are standby (STANDBY).
INIT-SYS:::ctag::2;
System response:
M ctag COMPLD
Note: The AC will now reset. The reset will take approximately five minutes.
76.5500/29, Rev R 7/07 Page 29-1171



pid = Password.
System response:
M ctag COMPLD
prosecution. */

mm = Month, 1 - 12.
dd = Day, 1 - 31.
hh = Hour, 0 - 23.
command:
System response:
M ctag COMPLD

(VALID).
synchronous (SYNC).
Page 29-1172 7/07 76.5500/29, Rev R

Completing Restoration
__ 1. Retrieve the integrity and content of the data stored in the PRI memory
AUD-DATA::PRI:ctag;
System response:
"PRI-A,DBSI,0"
"PRI-A,CMCI,0"
"PRI-B,DBSI,0"
"PRI-B,DBSAC,0"
__ 1.1 Verify from the system response that the number of

errors is 0. If it is not, follow your company's prescribed
__ 2. Copy data from PRI memory to SEC memory by entering the following
command:
CPY-MEM::FROMDEV=PRI,TOMEM=SEC:ctag::ALL;
System response:
M ctag COMPLD

command:
System response:
M ctag COMPLD
Followed by lines of data similar to the following example:

(VALID).
bundles for one AC copy are active (ACTIVE).
bundles for one AC copy are standby (STANDBY).
76.5500/29, Rev R 7/07 Page 29-1173

__ 4. Retrieve the present state of both ACs by entering the following

command:
System response:
M ctag COMPLD

"AC-A::SWV=5500FPx.y.z,ALMPF=99:PST=IS-NR-ACT"
"AC-B::SWV=5500FPx.y.z,ALMPF=99:PST=IS-NR-STBY"


command:
System response:
M ctag COMPLD

Hybrid Core Switch:


Page 29-1174 7/07 76.5500/29, Rev R


System response:
M ctag COMPLD
":INH"
__ 6.1 If the system response shows that you are in local

restoration mode (ALW), go to step 7.
__ 6.2 If the system response shows that you are not in local
restoration mode (INH), go to step 9, page 29-1175.

System response:
M ctag COMPLD

System response:
M ctag COMPLD
":INH"

End of Procedure
76.5500/29, Rev R 7/07 Page 29-1175

USER NOTES
Page 29-1176 7/07 76.5500/29, Rev R

Troubleshooting Manual 13. TL1 Conditions
13. TL1 Conditions
13.01 In the REPTÂLM, and the REPTÊVT autonomous TL1 messages the
fields condition type (referred to as condtype) and condition description (referred to
as conddescr) define for the user the condition which caused the alarm. Alarms are
triggered by messages from Facility Monitoring (FM) and System Integrity (SI). The
condtype and conddescr printed in the REPTÊVT will depend upon the condition
code embedded in the message from SI or FM. The purpose of this appendix is to
define the values of the condtype and conddescr fields.
13.02 The conddescr field is limited to 58 characters.
Fault Hierarchy for Ethernet SST=SENA Conditions

13.03 If a SST=SENA (secondary state = supporting entity not available)
condition is posted against an Ethernet entity (ETH, ETHINT, ETHMNG, LAG,
PPP, PPPG, or PT) when executing the applicable RTRV commands, there is a
problem with the supporting entity for the Ethernet entity being retrieved.
13.04 Use Table 13.1 to determine the supporting entity causing the condition.
Then go to the troubleshooting procedure for the supporting entity to troubleshoot
the problem.
Table 13.1 Fault Hierarchy for SENA Condition

SST=SENA on... Supporting Entity is...
ETHINT PPPG, VCG, or T3 TRMINT
(whichever is parent)
PPPG PPP
PPP T1 TRMINT
LAG ETH
ETH PT
PT MIM
ETHMNG MIM
Condition Type Definitions

13.05 This section gives a brief description and in some cases a reference for
each of the condition types referenced in this section.
condtype = MEA means Mismatch of Equipment and Attributes (TA 199, Issue 3)
76.5500/29, Rev R 7/07 Page 29-1177

13. TL1 Conditions Troubleshooting Manual
Network Element Condition Descriptions and Condition Types

13.06 In the subsections that follow the possible condition types and condition
descriptions are defined for the Network Element (NE).
Network Element Related Condition Descriptions (NE)

Condition Type: ACOACT
\"ACO activated via push button\"
Condition Type: MAN

\"Intra-system control LAN x cabling has unbalanced GC connections\" where x = 1 to 8
\"Intra-system control LAN x has exceeded the node limit\" where x = 1 to 8
Condition Type: NTWKSIZE

\"The two networks are mismatched in network size\"
Condition Type: MEA

\"The networks have mismatched connection memory maps\"
Condition Type: HLDOVRSYNC

\"The system is currently in the holdover synchronization mode\"
Condition Type: FRNGSYNC

\"System timing has transitioned from Synchronous to Asynchronous timing\" <MR 28473>
\"The system is currently in the free-run synchronization mode\"
Condition Type: SYNC

\"The system has detected a timing mismatch between SIM-A and SIM-B\"
Condition Type: TRGTSWVER

\"CCPM NPU software version needs upgrade\"
Administrative Complex Condition Descriptions and Types
Administrative Complex Related Condition Descriptions (AC)

Condition Type: INT
\"Unable to deselect because standby processor not available\"
\"Unable to deselect due to possible AIM fault\"
\"Failed to complete active processor initialization sequence\"
\"Entity failure reported to the Admin. Complex\"
Condition Type: PROTNA

\"Administrative Complex failed (ANR) - Not available for protection\"
Page 29-1178 7/07 76.5500/29, Rev R

\"Administrative Complex OOS - Not available for protection\"
Condition Type: CONTCOM

\"Degraded internal comm: Rev J AC backplane not verified\"
AC Power Supply Related Condition Descriptions (ACPS)

Condition Type: INT
\"Power supply module failed\"
\"Administrative shelf power supply removed\"
\"Power supply inserted\"

\"Power supply failed (ANR) - not available for protection\"
APM Related Condition Descriptions

Condition Type: INT
\"The LAN has failed\"
\"The LAN cable is not present\"
\"The reset for the APM has not cleared\"
\"The initialization for the APM failed\"
\"APM removed\"
\"The STBY AC has been commanded into Utility Mode\"
\"Failed diagnostic\"
\"APM Compatibility mismatch\"
\"APM EEPROM Failure\"

\"AC backplane APM-LSM LAN failure detected\"
\"AC front panel APM-LSM LAN failure detected\"
Condition Type: REVLVL

\"Module revision level does not meet revision level requirements\"
AIM Related Condition Descriptions

Condition Type: INT
\"Both AIM cables are absent\"
\"One AIM cable is absent\"
76.5500/29, Rev R 7/07 Page 29-1179

\"No reset is detected on the AIM\"
\"AIM initialization failure\"
\"AIM removed\"
\"No AIP cable\"
\"De-selection test failed\"
\"Selection circuit test failed\"
\"Module not compatible with existing software\"
\"EEPROM failure\"
\"Watchdog timing circuitry failure\"

Hard Disk Related Condition Descriptions (DSM)

Condition Type: INT
\"Disk has failed self test\"
\"Disk removed\"
\"Inactive AC has different program version than active AC\"
\"Hard Disk Access Failed\"
Removable Storage Drive Related Condition Descriptions (DSM)

Condition Type: INT
\"Removable Storage Drive has failed self-test\"
\"Removable Storage Drive removed\"
Condition Type: MEA

\"Removable Storage Drive types are not identical\"
Page 29-1180 7/07 76.5500/29, Rev R

Removable Media Related Condition Descriptions (REM)

Condition Type: BKUPMEMR
\"Removable media not present\"
\"Removable media not high-level formatted\"
\"SID mismatch\"
\"Copy failure to removable media, bundle=PGM\"
\"Copy failure to removable media, bundle=DATA\"
\"Copy failure to removable media, bundle=ALL\"
\"Removable media data bundle is invalid\"
\"Removable media program bundle is invalid\"
\"Removable media data and program bundles are invalid\"
\"Internal software error\"
\"Copy attempt denied to avoid bundles with different versions\"
\"Removable media is a self booting SRM\"
\"Removable media has insufficient storage capacity\"
\"Removable media cannot be used for system backup\"
Primary Memory Related Condition Descriptions (PRI)

Condition Type: DISKSYNC
\"Disk synch lost on active AC - Relational files error\"
\"Disk synch lost on active AC - Log processing error\"
Condition Type: NVMEMP

\"CMCI Database inconsistencies detected.\"
\"DBSI Database inconsistencies detected.\"
Secondary Memory Related Condition Descriptions (SEC)

Condition Type: NVMEMS
\"SID mismatch\"
\"Copy failure to secondary memory, bundle=PGM\"
\"Copy failure to secondary memory, bundle=DATA\"
76.5500/29, Rev R 7/07 Page 29-1181

\"Copy failure to secondary memory, bundle=ALL\"
\"CMCI Database inconsistencies detected.\"
\"DBSI Database inconsistencies detected.\"
\"Secondary memory data bundle is invalid\"
\"Secondary memory program bundle is invalid\"
\"Secondary memory data and program bundles are invalid\"
\"Copy attempt denied to avoid bundles with different versions\"
Operation Link Related Condition Descriptions (LINK)

Condition Type: OSLINK
\"Lost Operation Link Communication\"
Operation Channel Related Condition Descriptions (CHAN)

Condition Type: INTRUSION
\"Maximum number of invalid login attempts exceeded\"

\"Channel Transmission Error Causing Buffer Overflow\"
Condition Type: SENA

\"Lost Operation Channel Communication\"
SCM-1 Related Descriptions

Condition Type: INT
\"LAN Controller x fails loopback test\" where x is in the range 0-9
\"LAN Controller x fails transmit and dump test\" where x is in the range 0-9
\"System Communication Module Memory Failure\"
\"No reset detected on the SCM\"
\"System Communication Module removed\"
\"System Communication Module card failure\"
\"EEPROM failure\"
Page 29-1182 7/07 76.5500/29, Rev R


\"Module revison level does not meet revision level requirements\"
SCM-2 Related Descriptions

Condition Type: INT
\"No reset detected on the SCM-2\"
\"System Communication Module removed\"
\"System Communication Module failure\"
\"EEPROM failure\"

\"Module revison level does not meet revision level requirements\"
Central Office (CO) LAN Related Descriptions (LAN-2)

\"Supporting Entity Not Available\"

\"CO LAN communications failure\"
Control LAN Related Descriptions (LAN-1)

\"Failure on internal LAN - part of path not available for protection"\
TCPIP Related Descriptions

Condition Type: PROGFLT

\"PM Data HSO client connection lost\"
76.5500/29, Rev R 7/07 Page 29-1183

Reference (REF) Related Condition Descriptions

Condition Type: LOF
\"SIM-A has detected Loss of Frame on the reference\"
\"SIM-B has detected Loss of Frame on the reference\"
\"SIM-A and SIM-B have detected Loss of Frame on the reference\"
Condition Type: LOS

\"SIM-A has detected Loss of Signal on the reference\"
\"SIM-B has detected Loss of Signal on the reference\"
\"SIM-A and SIM-B have detected Loss of Signal on the reference\"
Condition Type: AIS

\"SIM-A has detected DS1 AIS on the reference\"
\"SIM-B has detected DS1 AIS on the reference\"
\"SIM-A and SIM-B have detected DS1 AIS on the reference\"
Condition Type: SYNC

\"SIM-A is unable to synchronize to the reference\"
\"SIM-B is unable to synchronize to the reference\"
\"SIM-A and SIM-B are unable to synchronize to the reference\"

\"Neither SIM is available\"
Condition Type: SSM

\"Change at the received Synchronization Status Message detected\"

\"Reference not available for protection\"
Synchronization Interface Module (SIM) Related Condition Descriptions

Condition Type: INT
\"Module diagnostics failed\"
\"Module removed\"
\"Internal failure detected\"
\"Internal error detected\"
\"Signal to all timing elements lost (possible cables missing)\"
\"Module is incompatible with existing software\"
\"EEPROM failure detected\"
Page 29-1184 7/07 76.5500/29, Rev R

\"Download failed\"
Condition Type PAINTGRT

\"Signal to NTDM-A lost (possible cable missing)\"
\"Signal to NTDM-B lost (possible cable missing\"
\"Signal to CCSM on SH1 lost (possible cable missing)\"
\"Signal to CCSM on SH2 lost (possible cable missing)\"

\"SIM failed (ANR) - not available for protection\"
Condition Type: SWTOREFA

\"Primary external timing reference has switched to REF-A\"
Condition Type: SWTOREFB

\"Primary external timing reference has switched to REF-B\"

Condition Type: MODINSRT

\"Module Inserted\"
Condition Type: MEA

\"SIM on a 2048 or larger system must be 81.5507B or later\"

\"Internal loss of communications between SIM and APM-A\"
\"Internal loss of communications between SIM and APM-B\"
LAN Switch Module (LSM) Related Condition Descriptions

Condition Type: INT
\"Module removed\"
\"Internal failure or APM-LSM LAN cable disconnected\"


\"CO LAN cable failure detected\"
\"LSM to CGC LAN Comm Lost at LAN-1 port (missing cable?)\"
76.5500/29, Rev R 7/07 Page 29-1185

Condition Type: MAN

\"LAN Interface Panel (LIP) miscabled on port <xxxx>\", where <xxxx>= LAN-1 through
LAN-8|SIM-A|SIM-B|XCOPY|COLAN which corresponds to the labels of the ports on LAN
Interface Panel (LIP)

\"Module Inserted\"
LAN Interface Panel (LIP) Related Condition Descriptions

Condition Type: INT
\"Module removed or LSM to LIP cable disconnected\"


\"Module Inserted\"
Switch Network Complex Condition Descriptions and Types
Network Complex Related Condition Descriptions (NC)

Condition Type: MAN
\"GC LAN Miscabled - AC-A on <ess_aid> LAN B\" where <ess_aid> is ESS-xxxx-y, xxxx
is the lead sdf of the shelf and y is A or B to indicate Copy
\"GC LAN Miscabled - AC-B on <ess_aid> LAN A\" where <ess_aid> is ESS-xxxx-y, xxxx
is the lead sdf of the shelf and y is A or B to indicate Copy

\"Network Complex failed (ANR) - not available for protection\"
\"Network Complex OOS - not available for protection\"
Condition Type: PWR

\"Possible LAN or power failure: NGCs or CGCs ANR\"
Network Group Controller Related Condition Descriptions (NGC)

Condition Type: INT
\"NGC card removed\"
\"EEPROM failure\"
Page 29-1186 7/07 76.5500/29, Rev R

\"Failed diagnostics\"

Center Stage Module Related Condition Descriptions (CSM)

Condition Type: INT
\"CSM card removed\"
\"stage three tubby loss of frame on SDF 0 through 31\"
\"stage three tubby parity error on SDF 0 through 31\"
\"stage three tubby yellow alarm on SDF 0 through 31\"
\"Input SDF failed at CSM line x from ESM (suspect cable)\" where x is in the range
0-95
\"EEPROM failure\"
\"Connection Memory failure\"
\"Failed diagnostics\" [cond-1906]
\"CSM connection memory inconsistent with database\"

\"CSM (81.5508) in a network size 1024 system must be Rev I or greater\"

\"Supporting Entity (NTDM) Not Available\"

\"Module Inserted\"
Center Stage PS Related Condition Descriptions (CSSPS)

Condition Type: INT
\"Power supply module removed\"

76.5500/29, Rev R 7/07 Page 29-1187

End Stage Module Related Condition Descriptions (ESM)

Condition Type: INT
\"ESM card removed\"
\"EEPROM failure\"
\"Stage two tubby loss of frame on SDF 0 to 31\"
\"Stage two tubby parity error on SDF 0 to 31\"
\"Stage two tubby yellow alarm on SDF 0 to 31\"
\"Internal signal failure detected at ESM line x from CSM\" where x is in the range 0
to 35
\"Internal signal failure detected at ESM line x from CAM\" where x is in the range 0
to 35
\"Internal signal degradation at ESM line x from CSM\" where x is in the range 0 to
35
\"Internal signal degradation at ESM line x from CAM\" where x is in the range 0 to
35
\"Stage four tubby loss of frame on SDF 0 to 35\"
\"Stage four tubby parity error on SDF 0 to 35\"
\"Stage four tubby yellow alarm on SDF 0 to 35\"
\"Incoming SDF failure from TSI (possible cable fault)\"
\"Input SDF failed on ESM line x from CSM (suspect cable)\" where x is in the range 0
to 35
\"Input SDF failed on ESM line x from CAM (suspect cable)\" where x is in the range 0
to 35
\"Internal signal failure at CSM line x from ESM\" where x is in the range 0 to 95
\"Internal signal failure at CAM line x from ESM\" where x is in the range 0 to 95
\"Internal signal degradation at CSM line x from ESM\" where x is in the range 0 to
95
\"Internal signal degradation at CAM line x from ESM\" where x is in the range 0 to
95
\"Failure to initialize ESM\"
\"Connection Memory failure\"
\"ESM connection memory inconsistent with database\"
\"Loss of clock on ESM\"
Page 29-1188 7/07 76.5500/29, Rev R

Condition Type: MEA

\"Inserted card inconsistent with supported PGC shelf\"


\"Module Inserted\"
\"Supporting Entity Not Available\" Condition Type: CONTCOM

\"Loss of GC LAN communication from ESM to PGC on LAN A\"
\"Loss of GC LAN communication from ESM to PGC on LAN B\"
End Stage PS Related Condition Descriptions (ESSPS)

Condition Type: INT
\"Power supply module removed\"

Network Timing Distributor Related Condition Descriptions (NTDM)

Condition Type PAINTGRT
\"Faulty timing signal to other NTDM (possible cable missing)\"
Condition Type: INT

\"NTD card removed\"
\"EEPROM failure\"
\"Failure to initialize NTD\"
\"NTD loses multi-frame alignment to SIM-A\"
\"NTD loses multi-frame alignment to SIM-B\"
\"NTD loses multi-frame alignment to other NTD or CCSM\"
\"NTD loses frequency lock to SIM-A (no clock)\"
\"NTD loses frequency lock to SIM-B (no clock)\"
\"NTD loses frequency lock to other NTD or CCSM (no clock)\"
76.5500/29, Rev R 7/07 Page 29-1189



\"Module Inserted\"
CSM Adapter Module (CAM) Related Condition Descriptions

Condition Type: INT
\"Module removed\"
\"SDF48 Loss of Frame detected at fiber X\" where X is the fiber number.
\"SDF48 Loss of Multi-Frame detected at fiber X\" where X is the fiber number.
\"SDF48 Parity Error detected at fiber X\" where X is the fiber number.
\"SDF48 Loss of Signal detected at fiber X\" where X is the fiber number.
\"SDF48 Yellow Frame detected at fiber X\" where X is the fiber number.
\"SDF48 Yellow Multi-Frame detected at fiber X\" where X is the fiber number.
\"SDF48 mismatch detected at fiber X \" where X is the mismatched fiber (X = 1 or 2).
\"Input SDF failed at CAM line x from ESM (suspect cable)\" where x is in the range
0-95



\"Module Inserted\"
Page 29-1190 7/07 76.5500/29, Rev R

Consolidated Core Switch (CCS) Complex Condition Descriptions and

Types
Consolidated Core Switch (CCS) Shelf Related Condition Descriptions

Condition Type: FANPWR
\"Loss of power or processor failure on fan tray\"
Condition Type: FEED

\"Loss of power feed A to shelf\"
\"Loss of power feed B to shelf\"
Condition Type: MAN

\"Active module(s) are being used as filler module(s)\"
\"SDF48 Cable Bundle from <plug# for eqpt_aid> to <plug# for aiddet> not detected\"
where <plug# for eqpt_aid> and <plug# for aiddet> are in the range P23..P28. See
REPTÂLM for <eqpt_aid> and <aiddet> definition.
\"Cable from Plug P31 to LTIP not detected\" (for CCS Shelf to LTIP cable)
Condition Type: INT

\"Missing module - potential air flow problem\"
Port Aggregation Module (PAM) Related Condition Descriptions

\"Loss of power feed A to module\"
\"Loss of power feed B to module\"
Condition Type: INT

\"Module removed\"
\"EEPROM Failure\"
\"Internal SDF48 LOF from CCSM to PAM\"
\"Internal SDF48 LOMF from CCSM to PAM\"
\"Internal SDF48 Parity Error from CCSM to PAM\"
\"Internal SDF48 LOF from PAM to CCSM\"
\"Internal SDF48 LOMF from PAM to CCSM\"
\"Internal SDF48 Parity Error from PAM to CCSM\"
76.5500/29, Rev R 7/07 Page 29-1191



\"Loss of LAN communication from PAM to TSI 1\"


\"Module Inserted\"
Network Interface Module (NIM) Related Condition Descriptions

Condition Type: INT

\"Module removed\"
\"EEPROM Failure\"
\"Internal failure detected - PT at port X\" where X is the port number. (use for
all unambiguous PT failures in a NIM.)
\"Cable or Internal failure - PT at port X\" where X is the port number. (use for all
ambiguous PT failures in a NIM.)
\"PT Module removed - PT at port X\" where X is the port number.
\"PT Module inconsistent with assigned type - PT at port X\" where X is the port number.
Page 29-1192 7/07 76.5500/29, Rev R

\"SDF48 mismatch detected at fiber X \" where X is the mismatched fiber (X = 1 to 8).
\"Internal SDF48 LOF from CCSM to NIM\"
\"Internal SDF48 LOMF from CCSM to NIM\"
\"Internal SDF48 Parity Error from CCSM to NIM\"
\"Internal SDF48 LOF from NIM to CCSM\"
\"Internal SDF48 LOMF from NIM to CCSM\"
\"Internal SDF48 Parity Error from NIM to CCSM\"

\"Module rev level does not meet minimum due to PT port X\" where X is the port number.


\"Module Inserted\"
CCS Group Controller (CGC) Related Condition Descriptions

Condition Type: INT

\"Module removed\"
\"EEPROM Failure\"


\"CGC to LSM LAN Comm Lost at LAN A port (missing cable?)\"
\"Loss of LAN communication from CGC to PAM-x\" where x is in the range of 1-8, and
13, 14, 17, 18.
76.5500/29, Rev R 7/07 Page 29-1193

Condition Type: MAN

\"LAN and Timing Interface Panel (LTIP) miscabled on port <xx>\", where <xx> = J1-J4
|J11-14 which corresponds to the labels on the LAN and Timing Interface Panel (LTIP)
Consolidate Core Switch Module (CCSM) Related Condition Descriptions

Condition Type: INT

\"Module removed\"
\"EEPROM Failure\"
\"Internal SDF48 LOF between CCSMs on shelf\"
\"Internal SDF48 LOMF between CCSMs on shelf\"
\"Internal SDF48 Parity Error between CCSMs on shelf\"
\"Internal SDF48 LOF on CCSM\"
\"Internal SDF48 LOMF on CCSM\"
\"Internal SDF48 Parity Error on CCSM\"

Condition Type: PAINTGRT

\"Faulty timing signal to other CCSM (possible cable missing)\"
\"Faulty timing signal to NTDM (possible cable missing)\"

\"Module Inserted\"

Page 29-1194 7/07 76.5500/29, Rev R

Port Complex Condition Descriptions and Types

descriptions are defined for the Port Complex (PC) modules.
Port Complex Shelf Related Condition Descriptions (PGCx)

Condition Type: CONTRDUP
\"Protection switching unavailable - Loss of communication\"
Condition Type: FANPWR

\"Loss of power or processor failure on fan tray\"

\"Loss of power feed A to port shelf\"
\"Loss of power feed B to port shelf\"
Condition Type: INT

\"Missing module - potential air flow problem\"
Condition Type: MAN

\"Active module(s) are being used as filler module(s)\"
\"Excessive length differential between SDF cable(s) to TSI A and SDF cable(s) to TSI
B\" \"Excessive length differential between SDF cables to TSI Copy A\"
Condition Type: PWR

\"Probable loss of shelf power failure\"
Condition Type: SWVER

\"Multiple CCPM NPU software versions present\"
76.5500/29, Rev R 7/07 Page 29-1195

Port Group Controller (PGCx) Related Condition Descriptions

\"Loss of LAN communication from TSI-A to GC\"
\"Loss of LAN communication from TSI-B to GC\"

Condition Type: INT

\"PGC Removed\"
\"GC executable load image checksum verification fail\"
\"EEPROM failure\"
\"Lost LAN communication with GC\"
Condition Type: MAN

\"GC LAN Miscabled - AC-A on PGC-A LAN B\"
\"GC LAN Miscabled - AC-B on PGC-A LAN A\"
\"GC LAN Miscabled - AC-A on PGC-B LAN B\"
\"GC LAN Miscabled - AC-B on PGC-B LAN A\"
Condition Type: MEA

\"GC type and/or SDF inconsistent with assignment\"
\"GC type inconsistent with assignment\"

\"PGC OOS - not available for protection\"
\"PGC failed (ANR) - not available for protection\"

\"PGC (81.5512A) on an OC3/OC12 shelf must be Rev G or greater\"
Page 29-1196 7/07 76.5500/29, Rev R

Port Power Supply (PPS) Related Condition Descriptions

Condition Type: INT
\"Module removed\"

DS1 Constituent Term Related Condition Descriptions (DS1 CST)

Condition Type: ACTLPBK
\"Active Loopback - Command Requested NEND Line\"
\"Active Loopback - Command Requested FEND Line\"
\"Active Loopback - Remotely Requested NEND Line\"
Condition Type: AIS

\"AIS alarm\"
Condition Type: DATALINK

\"ESF framing datalink failure detected\"
Condition Type: INHALM

\"Alarm Monitoring has been inhibited (via command)\"
\"Performance and Alarm Monitoring Suspension mode\"

\"TVT parity error detected on network copy <copy>\", where <copy> = A or B.
Condition Type: RED

\"Red alarm\"

\"Port Module and Redundant Port Module Not Available\"
\"Supporting T2 not available\"
Condition Type: ISD

\"Idle signal has been detected on termination\"
Condition Type: YEL

\"Yellow alarm\"
76.5500/29, Rev R 7/07 Page 29-1197

DS1 Di-Group Term Related Condition Descriptions (DS1 DGR)

Condition Type: RED
\"Red alarm\"
Condition Type: AIS

\"AIS alarm\"
Condition Type: YEL

\"Yellow alarm\"
Condition Type: ISD

\"Idle signal has been detected on the termination\"

\"Line Interface Module Not Available\"


\"Active Loopback - Command Requested NEND Internal\"

Condition Type: FELOS

\"Fault Escalation Loss of Signal detected\"

Condition Type: T-BERH

\"Line BER high threshold crossed\"
Condition Type: T-BERL

\"Line BER low threshold crossed\"
Page 29-1198 7/07 76.5500/29, Rev R

DS1 VTCST Term Related Condition Descriptions (DS1 VTCST)

Condition Type: AIS
\"AIS alarm\"


Condition Type: RED

\"Red alarm\"

\"Supporting VT1 is not IS-NR\"
\"Neither supporting VT1 is IS-NR-ACT\"
Condition Type: SENACC

\"Supporting Entity Not Available from Cross-connected Side\"
Condition Type: YEL

\"Yellow alarm\"
Condition Type: ISD

DS1 TRMINT Termination Related Condition Descriptions

\"Supporting MM24/RMM24 not available\"
\"Supporting MIM96 Not Available\"

Condition Type: RED

\"Red alarm\"
Condition Type: AIS

\"AIS alarm\"
Condition Type: YEL

\"Yellow alarm\"
Condition Type: ISD

76.5500/29, Rev R 7/07 Page 29-1199

Condition Type: T-BERH-P

\"Path BER high threshold crossed\"

\"Active Loopback - Command Requested NEND CC\"

Condition Type: NOCCPORT

\"Termination is not being used within CC Blocks\"
DS2 Termination Related Condition Descriptions

\"Active Loopback - Command Requested FEND Line\"
\"Active Loopback - Remotely Requested NEND Line\"
Condition Type: AIS

\"AIS alarm\"

Condition Type: RED

\"Red alarm\"

\"Supporting T3 Not Available\"
Condition Type: YEL

\"Yellow alarm\"
DS3 Di-Group Termination Related Condition Descriptions

Condition Type: AIC

\"AIC alarm\"
Page 29-1200 7/07 76.5500/29, Rev R

Condition Type: AIS

\"AIS alarm\"

\"The termination has alarm annunciation inhibited\"
Condition Type: ISD

Condition Type: RED

\"Red alarm\"

\"Line Interface Module Not Available\"
\"Neither supporting MIM is IS-NR\"
\"Neither MM nor RMM is IS-NR\"


Condition Type: YEL

\"Yellow alarm\"
Condition Type: FEAIS

\"Fault Escalation - Transmitting AIS\"
Condition Type: FELOS

\"Fault Escalation - Transmitting LOS\"
DS3 CST Termination Related Condition Descriptions

Condition Type: AIC
\"AIC alarm\"
Condition Type: AIS

\"AIS alarm\"

76.5500/29, Rev R 7/07 Page 29-1201

Condition Type: ISD

Condition Type: RED

\"Red alarm\"

\"Supporting STS1 is not IS-NR\"
\"Neither supporting STS1 is IS-NR-ACT\"
Condition Type: YEL

\"Yellow alarm\"
DS3 TRMINT Termination Related Condition Descriptions

\"Supporting MM24/RMM24 not available\"
\"Supporting MIM96 Not Available\"

Condition Type: RED

\"Red alarm\"
Condition Type: AIC

\"AIC alarm\"
Condition Type: AIS

\"AIS alarm\"
Condition Type: YEL

\"Yellow alarm\"
Condition Type: ISD


\"Active Loopback - Command Requested NEND CC\"

Condition Type: NOCCPORT

\"Termination is not being used within CC Blocks\"
Page 29-1202 7/07 76.5500/29, Rev R

Condition Type: RADCOMM

\"Remote Access Device Communication Lost\"
Condition Type: PTM

\"Payload Type Mismatch\"
EC1 Termination Related Condition Descriptions

Condition Type: LOF

\"EC1 Loss of Frame detected\"
Condition Type: LOS

\"EC1 Loss of Signal detected\"
Condition Type: RFI

\"EC1 Remote failure indication detected\"


\"Port Module and Redundant Port Module not available\"
\"Line Interface Module not available\"
Condition Type: SSM



OCn Termination Related Condition Descriptions

\"Facility Loopback is applied\"
Condition Type: AIS

\"Line Alarm Indication Signal\"
Condition Type: APSB

\"Automatic Protection Switching Byte Failure\"
76.5500/29, Rev R 7/07 Page 29-1203

Condition Type: APSB-FE

\"Far End Automatic Protection Switching Byte Failure\"
Condition Type: APSCM

\"Channel Mismatch Failure\"
Condition Type: APSMM

\"Mode Mismatch Failure\"
Condition Type: LOF

\"Loss of Frame\"
Condition Type: LOS

\"Loss of Signal\"

\"Lockout of Protection\"
\"Forced Switch to Protection\"
\"Forced Switch to Working\"
\"OPM-P is OOS\"
\"OPM-W is OOS\"
\"OPM-P is ANR\"
\"OPM-W is ANR\"
\"OCN-P is OOS\"
\"OCN-W is OOS\"
\"OCN-P is ANR\"
\"OCN-W is ANR\"
\"Signal Failure on Protection\"
\"Signal Failure on Working\"
\"Signal Degrade on Protection\"
\"Signal Degrade on Working\"
Condition Type: RFI

\"Line Remote Failure Indication\"

\"Supporting Entity (OPMN) Not Available\"
Condition Type: SSM


Page 29-1204 7/07 76.5500/29, Rev R



STS3C Termination Related Condition Descriptions

Condition Type: AIS

\"STS3C Path AIS detected\"

Condition Type: LOP

\"STS3C Loss of Pointer detected\"
Condition Type: MISCON

\"Crossconnection is inconsistent with node type of protection group\"
Condition Type: PLM

\"STS3C Payload Label Mismatch detected\"

\"Lockout of Working\"
\"STS3C-P is OOS\"
\"STS3C-W is OOS\"
\"STS3C-P is ANR\"
\"STS3C-W is ANR\"
Condition Type: RFI

\"STS3C Remote Failure Indication detected\"

\"Neither supporting OCN is IS-NR-ACT\"
\"Supporting OCN is not IS-NR-ACT\"
76.5500/29, Rev R 7/07 Page 29-1205

\"Supporting MM or RMM is not IS-NR\"

Condition Type: T-BERL-P

Condition Type: UNEQ

\"STS3C Path UNEQ detected\"
STS1 Termination Related Condition Descriptions

Condition Type: LOP
\"STS1 Loss of Pointer detected\"
Condition Type: LOMF

\"STS1 Loss of Multiframe alignment detected\"
Condition Type: AIS

\"STS1 Path AIS detected\"


Condition Type: PLM

\"STS1 Payload Label Mismatch detected\"
Condition Type: RFI

\"STS1 Remote Failure Indication detected\"

\"STS1 Path UNEQ detected\"

\"Supporting EC1 not available\"
\"Supporting entity (OC) is not IS-NR-ACT\"
\"Neither supporting entity (OC) is IS-NR-ACT\"
\"Supporting entity (MM<x>) not available\", where <x> is 3 or 24
Page 29-1206 7/07 76.5500/29, Rev R



\"STS1-P is OOS\"
\"STS1-W is OOS\"
\"STS1-P is ANR\"
\"STS1-W is ANR\"
Condition Type: PDIP

\"STS1 Path Payload Defect Indication detected\"

\"Fault Escalation - transmitting AIS\"


Condition Type: T-BERL-P

\"Path BER low threshold crossed\"
Condition Type: LOM

\"Loss of Multiframe on VCG\"
Condition Type: SQM

\"Sequence Mismatch\"
Condition Type: MND

\"LCAS member not Deskewable\"
VT1 Termination Related Condition Descriptions

Condition Type: LOP
\"VT1 Loss of Pointer detected\"

76.5500/29, Rev R 7/07 Page 29-1207

Condition Type: AIS

\"VT1 Path AIS detected\"
Condtition Type: PAINTGRT

Condition Type: PLM

\"VT1 Payload Label Mismatch detected\"
\"VT1 Path Signal Label Mismatch detected\"
Condition Type: RFI

\"VT1 Remote Failure Indication detected\"

\"VT1 Path UNEQ detected\"


\"Supporting STS1 not available\"
\"Supporting MM24/RMM24 Not Available\"


\"Forced Switch to Working\" ]
\"VT1-P is OOS\"
\"VT1-W is OOS\"
\"VT1-P is ANR\"
\"VT1-W is ANR\"
Condition Type: PDIV

\"VT1 Path Payload Defect Indication detected\"

\"Fault Escalation - transmitting AIS\"

Page 29-1208 7/07 76.5500/29, Rev R

-Condition Type: T-BERH-V

Condition Type: T-BERL-V

\"Path BER low threshold crossed\"
Condition Type: LOM

\"Loss of Multiframe on VCG\"
Condition Type: SQM

\"Sequence Mismatch\"
Condition Type: MND

\"LCAS member not Deskewable\"
ETH Termination Related Condition Descriptions

Condition Type: LINKDN
\"Link Down\"
Condition Type: ANEGFAIL

\"AutoNegotiation Failure\"

ETHMNG Termination Related Condition Descriptions

\"Link Down\"
Condition Type: ANEGFAIL

\"AutoNegotiation Failure\"

LAG Related Condition Descriptions

Condition Type: TLC
\"Total Loss of Capacity\"

76.5500/29, Rev R 7/07 Page 29-1209

PPP Termination Related Condition Descriptions

\"Link Down\"

PPPG Related Condition Descriptions

Condition Type: BCPDWN
\"Bridge Control Protocol Down\"
Condition Type: PLC

\"Partial Loss of Capacity\"
Condition Type: TLC

\"Total Loss of Capacity\"


VCG Related Condition Descriptions

Condition Type: FOP
\"Failure of LCAS Protocol - RX direction\"
\"Failure of LCAS Protocol - TX direction\"
Condition Type: LFD

\"Loss of Frame Delineation\"
Condition Type: LOA

\"Loss of Alignment: member ANR or not in CRS\"
Condition Type: PLC

\"Partial Loss of Capacity in the RX direction \"
\"Partial Loss of Capacity in the TX direction \"
Condition Type: PTM

\"Payload Type Mismatch\"

Page 29-1210 7/07 76.5500/29, Rev R

Condition Type: TLC

\"Total Loss of Capacity: member ANR or not in CRS\"
\"Total Loss of Capacity in RX dir: member ANR or not in CRS\"
\"Total Loss of Capacity in TX dir: member ANR or not in CRS\"

DS1 Port Module Related Condition Descriptions (DS1 PM)

Condition Type: INHSWPR
\"The switch to protection for the entity is inhibited\"
Condition Type: INT

\"Internal signal degradation at TSI from port module\"
\"System clock error in Network Copy A\"
\"System clock error in Network Copy B\"
\"Network Copy Synchronization Error Threshold Crossed\"
\"DS1 Parity Error in Network Copy A detected at PM\"
\"DS1 Parity Error in Network Copy B detected at PM\"
\"Failed module diagnostics\"
\"Failed download\"
\"Internal failure\"
\"Internal error\"
\"Port Module Removed\"
\"EEPROM failure\"
\"Failed reprogram of network status\"
\"Internal failure - transmit error - Ckt. Type DS1, Ckt. No. xx\" (where xx is in the
range {0...3} or {0...7})
\"Internal failure - receive error - Ckt. Type DS1, Ckt. No. xx\" (where xx is in the
range {0...3} or {0...7})
\"Internal failure - global signal processing error\"
\"Internal failure - global error - isolation not available\"
\"Internal failure - hardware logic fault\"
\"Internal failure - loss of communication with module\"
76.5500/29, Rev R 7/07 Page 29-1211

\"Internal failure - audit response is invalid\"
\"Internal failure - unexpected download request\"
Condition Type: MEA

\"Inconsistent with currently assigned type\"
\"Inconsistent with type of associated RPM\"


\"Module Inserted\"
DS1 Redundant Port Module (RPM) Related Condition Descriptions

Condition Type: INT
\"DS1 Parity Error in Network Copy A detected at RPM\"
\"DS1 Parity Error in Network Copy B detected at RPM\"
\"Failed download\"
\"Internal failure\"
\"Internal error\"
\"EEPROM failure\"
\"Internal failure - module sanity check failed\"
Condition Type: MEA


\"RPM OOS - not available for protection\"
\"RPM failed (ANR) - not available for protection\"
Page 29-1212 7/07 76.5500/29, Rev R

\"RPM inhibited - not available for protection\"
\"RPM carrying FORCED switched traffic - not available for protection\"


\"Module Inserted\"
DS3 Port Module Related Condition Descriptions

\"The switch to protection for the entity is inhibited\"
Condition Type: INT

\"Internal signal failure at TSI from port module\"
\"SDF parity error in Network Copy A Side\"
\"SDF parity error in Network Copy B Side\"
\"SDF out of frame in Network Copy A\"
\"SDF out of frame in Network Copy B\"
\"DS3 Parity Error in Network Copy A detected at PM\"
\"DS3 Parity Error in Network Copy B detected at PM\"
\"Failed download\"
\"EEPROM failure\"
\"Internal Failure\"
\"Internal Error\"
\"Internal failure - transmit error - Ckt. Type DS1, Ckt. No. = xx\" (where xx is in
the range {0...27})
\"Internal failure - receive error - Ckt. Type DS1, Ckt. No. = xx\" (where xx is in
the range {0...27})
76.5500/29, Rev R 7/07 Page 29-1213

\"Internal failure - transmit error - Ckt. Type DS2, Ckt. No. = xx\" (where xx is in
the range {0...6})
\"Internal failure - receive error - Ckt. Type DS2, Ckt. No. = xx\" (where xx is in
the range {0...6})
\"Internal failure - transmit error - Ckt. Type DS3\"
\"Internal failure - receive error - Ckt. Type DS3\"
Condition Type: MEA

\"Inconsistent with type of associated RPM\"
\"Inserted card type incompatible with shelf type\"


\"Module Inserted\"
DS3 Redundant Port Module (RPM) Related Condition Descriptions

Condition Type: INT
\"DS3 Parity Error in Network Copy A detected at RPM\"
\"DS3 Parity Error in Network Copy B detected at RPM\"
Page 29-1214 7/07 76.5500/29, Rev R

\"Failed download\"
\"Internal Error\"
\"Internal failure - module sanity check failed\"
\"EEPROM failure\"
Condition Type: MEA




\"Module Inserted\"
STS1E Port Module (PM) Related Condition Descriptions

\"The switch to protection for the entity is inhibited \"
Condition Type: INT

\"System clock error in Network Copy B\" \"SDF parity error in Network Copy A Side\"
76.5500/29, Rev R 7/07 Page 29-1215

\"SDF parity error\"
\"Payload parity error\"
\"EC1 Parity Error in Network Copy A detected at PM\"
\"EC1 Parity Error in Network Copy B detected at PM\"
\"Download failed\"
\"Module removed\"
Condition Type: MEA

\"Module is inconsistent with currently assigned type\"
\"Module is inconsistent with type of associated RPM\"
\"Module is inconsistent with existing software\"


\"Module Inserted\"
STS1E Redundant (RPM) Port Module Related Condition Descriptions

Condition Type: INT
Page 29-1216 7/07 76.5500/29, Rev R

\"EC1 Parity Error in Network Copy A detected at RPM\"
\"EC1 Parity Error in Network Copy B detected at RPM\"
\"Download failed\"
\"Module removed\"
\"SDF parity error\"
\"Payload parity error\"
Condition Type: MEA

\"Module is inconsistent with the currently assigned type\"
\"Inserted card type is incompatible with shelf type\"



\"Module Inserted\"
76.5500/29, Rev R 7/07 Page 29-1217

Electrical Port Module (EPM) Related Condition Descriptions (EC1 and T3 Combo)
Condition Type: INT

\"System clock error from MIM\"
\"Parity errors detected at both MIMs from EPM\"
\"MIM detected Parity Errors from EPM\"
\"LOF detected from MIM\"
\"LOF detected at both MIMs from EPM\"
\"MIM detected LOF from EPM\"
\"Failed download\"
\"EEPROM failure\"
\"Internal Error\"
\"Failed to detect BNC backplane\" [cond-3881]
\"Failure to reprogram EPM during Best Clock and Data audit\"
\"An Attention Line Hardware Error was Detected\"
Condition Type: MEA

\"Inconsistent with type of associated REPM\"

Page 29-1218 7/07 76.5500/29, Rev R



\"Module Inserted\"
Redundant Electrical Port Module (EPM) Related Condition Descriptions (EC1 and T3
Combo)
Condition Type: INT

\"Parity errors detected at both MIMs from REPM\"
\"MIM detected Parity Errors from REPM\"
\"LOF detected at both MIMs from REPM\"
\"MIM detected LOF from REPM\"
\"Failed download\"
\"EEPROM failure\"
\"Internal Error\"
\"Failed to detect BNC backplane\"
76.5500/29, Rev R 7/07 Page 29-1219

\"Failure to reprogram REPM during Best Clock and Data audit\"


\"Module Inserted\"

OPMn Related Condition Descriptions

Condition Type: INT

\"Download failed\"
\"Connection Memory download failure\"
\"Module removed\"
\"Indeterminable inter-module signal is impaired\"
\"Parity errors detected at both MIMs from OPMN\"
\"MIM detected Parity Errors from OPMN\"
\"LOF detected at both MIMs from OPMN\"
\"MIM detected LOF from OPMN\"
Page 29-1220 7/07 76.5500/29, Rev R

\"Failure to reprogram OPM during Best Clock and Data audit\"
all unambiguous PT failures in an OPM.)
ambiguous PT failures in an OPM.)
Condition Type: MEA



\"Module Inserted\"
CCPM Related Condition Descriptions

Condition Type: INT
\"Parity errors detected at both MIMs from CCPM\"
\"MIM detected Parity Errors from CCPM\"
\"LOF detected at both MIMs from CCPM\"
\"MIM detected LOF from CCPM\"
\"Signal Fail detected at MM and RMM from CCPM\"
\"Failed download\"
\"EEPROM failure\"
\"Internal Error\"
76.5500/29, Rev R 7/07 Page 29-1221

\"CC block failure\"




\"Module Inserted\"
Condition Type: CC1ERRORMN

\"Error in the first CC Block - Minor\"

\"Error in the second CC Block - Minor\"
Condition Type: CC1ERRORMJ

\"Error in the first CC Block - Major\"

\"Error in the second CC Block - Major\"
Condition Type: CC1ERRORCR

\"Error in the first CC Block - Critical\"

\"Error in the second CC Block - Critical\"
Condition Type: CC1CNFG

\"Configuration Mismatch of terminations detected in first CC Block\"

\"Configuration Mismatch of terminations detected in second CC Block\"
Condition Type: PROTDEG

\"Protection Switching Degraded - Extra Switch Time Possible\"
Page 29-1222 7/07 76.5500/29, Rev R

RCCPM Related Condition Descriptions

Condition Type: INT
\"Parity errors detected at both MIMs from RCCPM\"
\"MIM detected Parity Errors from RCCPM\"
\"LOF detected at both MIMs from RCCPM\"
\"MIM detected LOF from RCCPM\"
\"Signal Fail detected at MM and RMM from RCCPM\"
\"Failed download\"
\"EEPROM failure\"
\"Internal Error\"
\"CC block failure\"




\"Module Inserted\"
Condition Type: ISOAUTOSW

\"Traffic was switched away from the RCCPM to run isolation\"

\"Error in the first CC Block - Minor\"
76.5500/29, Rev R 7/07 Page 29-1223


\"Error in the second CC Block - Minor\"

\"Error in the first CC Block - Major\"

\"Error in the second CC Block - Major\"

\"Error in the first CC Block - Critical\"

\"Error in the second CC Block - Critical\"

\"Configuration Mismatch of terminations detected in first CC Block\" <MR54125>

\"Configuration Mismatch of terminations detected in second CC Block\" <MR54125>

\"RCCPM OOS - not available for protection\"
\"RCCPM failed (ANR) - not available for protection\"
\"RCCPM inhibited - not available for protection\"
\"RCCPM carrying FORCED switched traffic - not available for protection\"
Condition Type: PROTDEG

\"Protection Switching Degraded - Extra Switch Time Possible\"
MIM Related Condition Descriptions

Condition Type: INT

\"MIM connection memory inconsistent with database\"
Page 29-1224 7/07 76.5500/29, Rev R

\"LOF detected at both EPM/REPM from MIM\" \"Parity Errors detected at both EPM/REPM
from MIM\"
\"LOF detected at both OPMs from MIM\"
\"Parity Errors detected at both OPMs from MIM\"
\"LOF detected at both MM/RMM from MIM\"
\"Parity Errors detected at both MM/RMM from MIM\"
\"EEPROM failure\"
\"Card Removed\"
\"Failure to reprogram MIM during Best Clock audit\"
\"Link Failure detected at both MM/RMM from MIM\"
\"Loss of clock detected at MIM from TSI-A\"
\"Loss of clock detected at MIM from TSI-B\"
Condition Type:MEA

\"Module Inserted\"

\"MIM OOS - not available for protection\"
\"MIM failed (ANR) - not available for protection\"

MM Related Condition Descriptions

Condition Type: INT

\"Internal signal degradation detected at TSI from MM<x>\" where x = 3 or 24
\"Internal signal failure detected at TSI from port module\"
76.5500/29, Rev R 7/07 Page 29-1225

\"Failed port framing to TSI\"
\"Failed download\"
\"Internal Error\"
\"Card Removed\"
\"EEPROM failure\"
\"Failure to reprogram MM<x>/RMM<x> network status during BBBC audit\" where x = 3 or

24
\"Parity Error in Network Copy A detected at MM<x>\" where x = 3 or 24
\"Parity Error in Network Copy B detected at MM<x>\" where x = 3 or 24
\"Parity Errors detected from MIM\"
\"Parity Errors detected at both MIMs from MM\"
\"MIM detected Parity Errors from MM\"
\"LOF detected at both MIMs from MM\"
\"MIM detected LOF from MM\"
\"MIM detected Link Failure from MM\"
\"Link Failure detected at both MIMs from MM\"
\"Link Failure detected from MIM\"
\"MM connection memory inconsistent with database\"
Condition Type: MEA

Page 29-1226 7/07 76.5500/29, Rev R

\"Module is inconsistent with type of associated RMM<x>\" where x = 3 or 24


\"Module Inserted\"
RMM Related Condition Descriptions

FEED
Condition Type: INT

\"SDF parity error in Network Copy B Side\" [
\"Failed download\"
\"Internal Error\"
\"Card Removed\"
\"EEPROM failure\"
\"Failure to reprogram MM3/RMM3 network status during BBC audit\"
\"Parity Error in Network Copy A detected at MM3\"
\"Parity Error in Network Copy B detected at MM3\"
\"Parity Errors detected from MIM\"
76.5500/29, Rev R 7/07 Page 29-1227

\"Parity Errors detected at both MIMs from RMM\"
\"MIM detected Parity Errors from RMM\"
\"LOF detected at both MIMs from RMM\"
\"MIM detected LOF from RMM\"
\"MIM detected Link Failure from RMM\"
\"Link Failure detected at both MIMs from RMM\"
\"MM connection memory inconsistent with database\"
Condition Type: MEA


\"RMM OOS - not available for protection\"
\"RMM failed (ANR) - not available for protection\"
\"RMM ACTive in FRCD mode - not available for protection\"


\"Module Inserted\"
Condition Type: ISOAUTOSW

\"Traffic was switched away from the RMM to run isolation\"
Line Interface Module (LIMx) Related Condition Descriptions

Condition Type: INT
\"LIM Removed\"
Condition Type: MEA

\"Switch position inconsistent with T3 database attribute EQLZ\"
\"Set LBO switch to LONG\"
Page 29-1228 7/07 76.5500/29, Rev R

Time Slot Interchange (TSIx) Related Condition Descriptions

\"Loss of LAN communications from GC-A to TSI\"
\"Loss of LAN communications from GC-B to TSI\"

Condition Type: INT

\"SDF Loss Of Frame detected at input from ports\"
\"Internal SDF Loss Of Frame detected in receive direction\"
\"Internal SDF Loss Of Frame detected in transmit direction\"
\"Yellow Alarm from ESS to TSI\"
\"Parity error (Constant) detected at input from ports\"
\"Connection memory failed to compare with database\"
\"Incoming SDF failure from ESM (possible cable fault)\"
\"Internal Error\"
\"Card Removed\"
\"Y bit errors at XIN of 1/1 Qmux, TSI cannot frame\"
\"Loss of SDF clock, TSI cannot frame\"
\"EEPROM failure\"
\"Signature verification failure on writing a connection\"
\"Connection memory failure\"
\"Internal signal failure detected at ESM from TSI\"
\"Internal signal degradation detected at ESM from TSI\"
\"Internal signal failure detected at TSI from ESM\"
\"Internal signal degradation detected at TSI from ESM\"
\"QTVT parity error detected at QMUX from ports\"
\"Internal SDF parity error detected at TSI from QMUX\"
\"Internal TVT parity error detected at TSI from QMUX\"
76.5500/29, Rev R 7/07 Page 29-1229

\"Internal SDF parity error detected at QMUX from TSI\"
\"SDF Loss of Clock detected at the port modules\"
\"SDF Loss of Frame detected at the port modules\"
\"SDF Parity Errors detected at the port modules\"
\"TVT Parity Errors detected at the port modules\"
\"Loss of clock detected at both MIMs from TSI\"
all unambiguous PT failures in a TSI.)
ambiguous PT failures in a TSI.)
\"SDF48 mismatch detected at fiber X\" where X is the mismatched fiber (X = 1 or 2).
Condition Type: MEA

\"Inconsistent with currently defined type\"



\"Module Inserted\"
Page 29-1230 7/07 76.5500/29, Rev R

FPG (OCN Protection Switching) Related Switching Event Descriptions

13.08 The following conditions (and their associated output text strings) cause
switching events to occur. They are not conditions that are posted against the FPG.
The ps_event_count is the number of protection switches that have occurred
during the current audit cycle.
Condition Type: LOSONWKG (loss of signal on working)

\"Protection switch occurred due to LOS on WKG OCn, Count=<ps_event_count\>\"
Condition Type: LOSONPROT (loss of signal on protection)

\"Protection switch occurred due to LOS on PROT OCn, Count=<ps_event_count\>\"
Condition Type: LOFONWKG (loss of framing on working)

\"Protection switch occurred due to LOF on WKG OCn, Count=<ps_event_count\>\"
Condition Type: LOFONPROT (loss of framing on protection)

\"Protection switch occurred due to LOF on PROT OCn, Count=<ps_event_count\>\"
Condition Type: AISONWKG (line AIS on working)

\"Protection switch occurred due to AIS-L on WKG OCn, Count=<ps_event_count\>\"
Condition Type: AISONPROT (line AIS on protection)

\"Protection switch occurred due to AIS-L on PROT OCn, Count=<ps_event_count\>\"
Condition Type: SFONWKG (signal failure on working)

\"Protection switch occurred due to SF on WKG OCn, Count=<ps_event_count\>\"
Condition Type: SFONPROT (signal failure on protection)

\"Protection switch occurred due to SF on PROT OCn, Count=<ps_event_count\>\"
Condition Type: SDONWKG (signal degrade on working)

\"Protection switch occurred due to SD on WKG OCn, Count=<ps_event_count\>\"
Condition Type: SDONPROT (signal degrade on protection)

\"Protection switch occurred due to SD on PROT OCn, Count=<ps_event_count\>\"
Condition Type: ANRWKG (OPM failure (ANR) on working)

\"ANR OPM caused a protection switch to PROT, Count=<ps_event_count\>\"
Condition Type: ANRPROT (OPM failure (ANR) on protection)

\"ANR OPM caused a protection switch to WKG, Count=<ps_event_count\>\"
Condition Type: OOSWKG (working OPM or OCN taken OOS)

\"OOS OPM caused a protection switch to PROT, Count=<ps_event_count\>\"
\"OOS OCN caused a protection switch to PROT, Count=<ps_event_count\>\"
Condition Type: OOSPROT (protection OPM or OCN taken OOS)

\"OOS OPM caused a protection switch to WKG, Count=<ps_event_count\>\"
\"OOS OCN caused a protection switch to WKG, Count=<ps_event_count\>\"
Condition Type: UEQWKG (working OPM is unequipped)

\"UNEQPT OPM caused a protection switch to PROT, Count=<ps_event_count\>\"
76.5500/29, Rev R 7/07 Page 29-1231

Condition Type: MANTOWKG (manual switch to working)

\"Manual switch to WKG OCn occurred, Count=<ps_event_count\>\"
Condition Type: MANTOPROT (manual switch to protection)

\"Manual switch to PROT OCn occurred, Count=<ps_event_count\>\"
Condition Type: FSTOWKG (force switch to working)

\"Forced switch to WKG OCn occurred, Count=<ps_event_count\>\"
Condition Type: FSTOPROT (force switch to protection)

\"Forced switch to PROT OCn occurred, Count=<ps_event_count\>\"
Condition Type: LOCKOUT (lockout of protection)

\"Switch caused by lockout of protection OCn, Count=<ps_event_count\>\"
Condition Type: APSREQ (APS channel switch request)

\"APS channel switch request occurred, Count=<ps_event_count\>\"
Condition Type: APSFAIL (APS byte failure)

\"APS byte failure occured, Count=<ps_event_count\>\"
Condition Type: RTW (revert to working)

\"Revert to WKG OCn switch occurred, Count=<ps_event_count\>\"
CPG (OCN Protection Switching) Related Switching Event Descriptions

switching events to occur. They are not conditions that are posted against the
CPG. The ps_event_count is the number of protection switches that have occurred

\"Protection switch occurred due to SD on WKG, Count=<ps_event_count\>\"

\"Protection switch occurred due to SD on PROT, Count=<ps_event_count\>\"

\"Protection switch occurred due to SF on WKG, Count=<ps_event_count\>\"
\"Protection switch occurred due to an MM equipment switch, Count=1\" <MR60371 >

\"Protection switch occurred due to SF on PROT, Count=<ps_event_count\>\"
\"Protection switch occurred due to an MM equipment switch, Count=1\"
Condition Type: AISONWKG (path AIS on working)

\"Protection switch occurred due to AIS defect on WKG, Count=<ps_event_count\>\"
Condition Type: AISONPROT (path AIS on protection)

\"Protection switch occurred due to AIS defect on PROT, Count=<ps_event_count\>\"
Page 29-1232 7/07 76.5500/29, Rev R

Condition Type: LOPONWKG (loss of pointer on working)

\"Protection switch occurred due to LOP defect on WKG, Count=<ps_event_count\>\"
Condition Type: LOPONPROT (loss of pointer on protection)

\"Protection switch occurred due to LOP defect on PROT, Count=<ps_event_count\>\"
Condition Type: UNEQONWKG (signal degrade on working)

\"UNEQ on WKG caused a protection switch to PROT, Count=<ps_event_count\>\"
Condition Type: UNEQONPROT (signal degrade on protection)

\"UNEQ on PROT caused a protection switch to WKG, Count=<ps_event_count\>\"
Condition Type: SENAONWKG (SENA on working)

\"Protection switch occurred due to SENA on WKG, Count=<ps_event_count\>\"
Condition Type: SENAONPROT (SENA on protection)

\"Protection switch occurred due to SENA on PROT, Count=<ps_event_count\>\"
Condition Type: OOSWKG (working OPM is unequipped)

\"OOS circuit on WKG caused a protection switch to PROT, Count=<ps_event_count\>\"
Condition Type: OOSPROT (protection OPM is unequipped)

\"OOS circuit on PROT caused a protection switch to WKG, Count=<ps_event_count\>\"

\"Manual switch to WKG occurred, Count=<ps_event_count\>\"

\"Manual switch to PROT occurred, Count=<ps_event_count\>\"

\"Forced switch to WKG occurred, Count=<ps_event_count\>\"

\"Forced switch to PROT occurred, Count=<ps_event_count\>\"
Condition Type: LOCKWKG (lockout of working)

\"Protection switch occurred due to lockout of WKG, Count=<ps_event_count\>\"
Condition Type: LOCKPROT (lockout of protection)

\"Protection switch occurred due to lockout of PROT, Count=<ps_event_count\>\"

\"Revert to working switch occurred, Count=<ps_event_count\>\"
Condition Type: RTP (revert to protection)

\"Revert to protection switch occurred, Count=<ps_event_count\>\"
76.5500/29, Rev R 7/07 Page 29-1233

PPG (OCN Protection Switching) Related Switching Event Descriptions

switching events to occur. They are not conditions that are posted against the PPG.









\"UNEQ on WKG caused a protection switch to PROT, Count=<ps_event_count\>\" ]






Page 29-1234 7/07 76.5500/29, Rev R








Condition Type: PLMONWKG (PLM on working)

\"Protection switch occurred due to PLM Defect on WKG, Count=<ps_event_count>\"
Condition Type: PLMONPROT (PLM on protection)

\"Protection switch occurred due to PLM Defect on PROT, Count=<ps_event_count>\"
Condition Type: PDIONWKG (PDI on working)

\"Protection switch occurred due to PDI Defect on WKG, Count=<ps_event_count>\"
Condition Type: PDIONPROT (PDI on protection)

\"Protection switch occurred due to PDI Defect on PROT, Count=<ps_event_count>\"
VPG (OCN Protection Switching) Related Switching Event Descriptions

switching events to occur. They are not conditions that are posted against the VPG.




76.5500/29, Rev R 7/07 Page 29-1235






\"UNEQ on WKG caused a protection switch to PROT, Count=<ps_event_count\>\"













Page 29-1236 7/07 76.5500/29, Rev R

Condition Type: PLMONWKG (PLM on working)

\"Protection switch occurred due to PLM Defect on WKG, Count=<ps_event_count>\"
Condition Type: PLMONPROT (PLM on protection)

\"Protection switch occurred due to PLM Defect on PROT, Count=<ps_event_count>\"
Condition Type: PDIONWKG (PDI on working)

\"Protection switch occurred due to PDI Defect on WKG, Count=<ps_event_count>\"
Condition Type: PDIONPROT (PDI on protection)

\"Protection switch occurred due to PDI Defect on PROT, Count=<ps_event_count>\"
Performance Monitoring Related Threshold Crossing Alerts

13.12 This section applies across terminations. Threshold Crossing Alerts
(TCAs) are transient conditions (TCs), i.e. they are conditions that do not require
clearing.
Condition Type: T-CVV

\"Path CV threshold exceeded\"
Condition Type: T-ESV

\"Path ES threshold exceeded\"
Condition Type: T-SESV

\"Path SES threshold exceeded\"
Condition Type: T-FCV

\"Path FC threshold exceeded\"
Condition Type: T-PPSCV

\"Path PPSC threshold exceeded\"
Condition Type: T-PPSDV

\"Path PPSD threshold exceeded\"
Condition Type: T-UASV

\"Path UAS threshold exceeded\"
76.5500/29, Rev R 7/07 Page 29-1237

Common Condition Descriptions and Types

descriptions are defined for entities, e.g. fans and filters, that are common across
complexes and also have common condtion types and descriptions.
FAN Module Related Condition Descriptions

Condition Type: FAN
\"Fan module removed\"
\"Fan module has single internal failure\"
\"Fan module has more than one internal failure\"


Air Filter Entity Related Condition Descriptions (FILTER)

Condition Type: FLTREMV
\"Air filter removed\"
Condition Type: MAR

\"Air filter routine maintenance required\"
PT (Pluggable Transceiver) Module Related Condition Descriptions

Condition Type: INT
\"Internal transmitter failure detected\"
\"Module removed\"
\"SDF48 Loss of Frame detected at fiber\"
\"SDF48 Loss of Multi-Frame detected at fiber\"
\"SDF48 Parity Error detected at fiber\"
Page 29-1238 7/07 76.5500/29, Rev R

\"SDF48 Loss of Signal detected at fiber\"
\"SDF48 Yellow Frame detected at fiber\"
\"SDF48 Yellow Multi-Frame detected at fiber\"
\"SDF48 mismatch detected at fiber\"
Condition Type: MEA



\"Module Inserted\"
76.5500/29, Rev R 7/07 Page 29-1239

USER NOTES
Page 29-1240 7/07 76.5500/29, Rev R

Troubleshooting Manual Index
Index
Numerics LAN-2 29-95

LIM 29-492
4xGbE Port Module 29-824
LINK 29-94
LIP 29-86
A LSM 29-85
abbreviations 29-8 MIM 29-669
AC alarm messages 29-74 MM 29-659
ACPS NC 29-267
alarm messages 29-87 NE 29-100
LEDs 29-55 NGC 29-268
AC shelf revision NIM 29-388
determining 29-190 NTDM 29-269
Administrative Complex Power Supply Module 29-204 OC termination 29-878
administrative complex power supply See ACPS OPM 29-647, 29-651, 29-655
administrative complex SeeAC PAM 29-385
Administrative Processor Module 29-131 PC 29-609
Administrative Shelf Bracket Assembly 29-193 PGC 29-392, 29-481
admonishments 29-4 PPP 29-892
AIM PPPG 29-893
alarm messages 29-75 PPS 29-493
LEDs 29-58 PRI 29-88
AIP to AC cabling 29-103 RCCPMA 29-655
ALARM.DAT file 29-1089 REF 29-97
alarm interface module See AIM REMV 29-91
Alarm Interface Panel REPM 29-638
ACO button 29-100 RMM 29-664
alarm messages RSD 29-90
AC 29-74 SCM 29-77, 29-78
ACPS 29-87 SEC 29-89
AIM 29-75 SIM 29-82
APM 29-80 STS-1 PM 29-624
CCPMA 29-651 STS-1 RPM 29-642
CCSM 29-383 STS-1 termination 29-871
CCS shelf 29-382 STS3C 29-884
CHAN 29-92 T1 CST 29-857
CSM 29-271, 29-273 T1 DGR 29-855
CSSPS 29-280 T1 TRMINT 29-860
DD DS1 29-611 T2 29-862
DS1 and DD DS1 RPM 29-629 T3 CST 29-866, 29-867
DS1 PM 29-611 T3 DGR 29-863
DS3 PM 29-615 TCP/IP 29-96
DS3 RPM 29-633 TSI 29-484
EC1 29-869 VT1 29-874
EPM 29-620 VT1 CST 29-887, 29-889
ESM 29-276 APM 29-131
ESSPS 29-281 alarm messages 29-80
ETH 29-890 jumper settings 29-136
ETH MNG 29-891 LEDs 29-56
fan tray module 29-675 APM UEQ alarm 29-141
HDD 29-79 asynchronous links 29-225
LAG 29-892
LAN-1 29-94
76.5500/29, Rev R 7/07 Page 29-1241

Index Troubleshooting Manual
B consolidated group controller module See GCM

CONTCOM alarms 29-468
B/FAM front panel 29-1116
control LAN cabling 29-239
B/FAP 29-1105
control LAN in CCS core 29-238
B/FAP breaker assignments
courier font usage 29-4
consolidated core switch 29-206
CSM 29-307
hybrid core switch 29-206
alarm messages 29-271, 29-273
standard core switch 29-205
LEDs 29-251
backing up data 29-1123, 29-1164
CSM Adapter Module 29-245, 29-318
battery distribution fuse bay 29-1105
LEDs 29-252
BDFB 29-1105
CSSPS alarm messages 29-280
Breaker Frame/Alarm Panel 29-1105
breakers
turning off 29-189 D
danger statements, explanation of use 29-4
C Data Storage Module 29-117
primary memory partition 29-210
cables
secondary memory partition 29-214
CGC to CGC 29-467
DD DS1 PM
LTIP to LIP 29-464
alarm messages 29-611
cabling
LEDs 29-579
AIP to AC 29-103
double-density DS1 port module See DD DS1 PM
CGC LAN 29-468
DS1 and DD DS1 RPM alarm messages 29-629
LSM/LIP to CGC LAN 29-468
DS1 PM
CAM 29-245, 29-318
facility fiber locations 29-31
LEDs 29-578
optical parameters 29-329, 29-444
DS1 port module See DS1 PM
SDF48 cabling 29-328
DS1 VT1 CST termination 29-965
SDF48 mismatch alarms 29-331
DS3 PM
cautions, explanation of use 29-4
CCPMA 29-770
LEDs 29-580
DS3 port module See DS3 PM
MNG fiber location 29-34
DS3 RPM alarm messages 29-633
CCSM 29-363, 29-394
DSM 29-117
LEDs 29-368
DUALNCX parameter 29-851
CCSM alarm messages 29-383
CCSS 29-363
CCS shelf 29-363 E
alarm messages 29-382 EC1 29-915
CCS switch core EC1 alarm messages 29-869
stacked configuration 29-162 electric port module See EPM
SYNC timing cables 29-161 EMI 29-82
Center Stage Module 29-307 EMI shielding 29-82
Center Stage Shelf Power Supply Module 29-353 End Stage Module 29-332
center stage shelf power supply module See CSSPS end stage module See ESM
CGC LAN cabling 29-468 End Stage Shelf Power Supply Module 29-358
CGCM 29-450 EPM
troubleshooting LAN cables 29-463 alarm messages 29-620
CGC to CGC cables 29-467 LEDs 29-581
CHAN 29-225 EPS to MSA connectivity 29-1023
alarm messages 29-92 EQLZ 29-565
channel See CHAN equalization (LBO) setting versus cable length 29-565
Circuit Cell Packet Module Abis/ATM 29-770 ESM
class 1 laser 29-10, 29-413, 29-520 alarm messages 29-276
consolidated core switch module 29-36, 29-363, 29-394 LEDs 29-254
consolidated core switch shelf 29-363 receive fibers 29-531
Consolidated Group Controller Module 29-450 ESMU
Page 29-1242 7/07 76.5500/29, Rev R

fiber optic adapters 29-346, 29-529 High Density Port Shelf

port assignments 29-529, 29-537 LAN 29-1059
ESMU/TSI96/P optical parameters 29-345 high density port shelf types 29-2
ESMU/TSI96 optical parameters 29-528, 29-536 hybrid switch core
ESSPS 29-358 SYNC timing cables 29-154
ETH alarm messages 29-890 I
ethernet management See ETH MNG
iDS0 29-1045
Ethernet Management termination 29-1010
internal path integrity error 29-1027
Ethernet Port Shelf to Multi-Service Access Node
iVQE 29-1033
connectivity 29-1023
ethernet See ETH
Ethernet termination 29-1006 J
ETH MNG alarm messages 29-891 J40 cable 29-142
ETHMNG termination 29-1010 jumper settings
ETH termination 29-1006 APM 29-136
SPM 29-137
F
F/FAM front panel 29-1117 L
F/FAP 29-846, 29-1105 LAG 29-1014
failures alarm messages 29-892
group controller 29-1076 LAN
LAN 29-1078 failures 29-1078
fan tray assembly High Density Port Shelf 29-1059
of HDPS 29-848 rules 29-1060
fan tray module 29-843 LAN-1 29-230
alarm messages 29-675 alarm messages 29-94
LEDs 29-607 LAN-2
fiber handling 29-11, 29-414, 29-521 alarm messages 29-95
fiber optic safety 29-10 LAN Interface Panel (LIP) 29-180
fiber shroud lights installing 29-193
for DD DS1 TSI 29-342, 29-517 LAN run example
for DS1 TSI 29-341, 29-516 DD DS1 29-1079
for DS3 and STS1 TSI 29-343, 29-518 DS1, DS3, and STS-1 29-1078
for OC-3 and OC-12 TSI 29-344, 29-519 HDPS 29-1081
flash memory card 29-218 OC-3 or OC-12 29-1080
clearing residual alarms 29-1089 LAN Switch Module 29-53
fuse frame/alarm panel 29-1105 LEDs 29-63
laser
G class 1 29-10, 29-413, 29-520
laser radiation safety precautions 29-10, 29-413, 29-
GMT fuse 29-846
520
group controller failures 29-1076
LDPS LAN 29-1066
multiple faults 29-1076, 29-1077
cable types 29-1066
SCM fault 29-1076
LEDs
single fault 29-1076
ACPS 29-55
AIM 29-58
H APM 29-56
handling fiber 29-11, 29-414, 29-521 CCPMA 29-590
HDD alarm messages 29-79 CSM 29-251
HDPS LAN DD DS1 PM 29-579
cables 29-1060 DS1 PM 29-578
description 29-1059 DS3 PM 29-580
example 29-1062 EPM 29-581
example with daisy chain 29-1065 ESM 29-254
rules 29-1060 fan tray module 29-607
76.5500/29, Rev R 7/07 Page 29-1243

MIM96 29-604 facility fiber location 29-17

MIM96E 29-606 mixed LAN run example 29-1063, 29-1064
MM24A 29-593 MM 29-794
MM24E 29-594 alarm messages 29-659
MM24NB 29-597 LEDs 29-592, 29-593, 29-594, 29-595, 29-596, 29-
MM24V 29-595, 29-596 597
MM3 29-592 MM24V 29-1035
NGC 29-246 in-line configuration SDF management 29-1035
NTDM 29-248 loop-around configuration SDF management 29-
OPM12 29-584 1036
OPM12X4 29-586 MM24VE
OPM3 29-584 in-line configuration SDF management 29-1036
OPM3X8 29-587 loop-around configuration SDF management 29-
PGC 29-474 1037
RMM24 29-599
RMM24E 29-600 N
RMM24NB 29-603
narrowband port shelf
RMM24V 29-601, 29-602
DS0 functionality 29-1045
RMM3 29-598
in-line configuration SDF management 29-1046
SCM 29-59
loop-around configuration SDF management 29-
SIM 29-60, 29-61 1046
STS-1 PM 29-582 relational port alarming 29-1049
light levels 29-340, 29-345 NC alarm messages 29-267
LIM 29-559 NC shelf numbering 29-355
alarm messages 29-492 NE alarm messages 29-100
Line Interface Module 29-559 network group controller module See NGC
line interface module See LIM network interface module 29-363, 29-434
LINK 29-225 removal 29-37
alarm messages 29-94 Network Timing Distribution Module 29-292
link aggregation group 29-1014 NGC
LIP alarm messages 29-268
alarm messages 29-86 LEDs 29-246
LIP connectors 29-192 NIM 29-363, 29-434
LIP X-COPY port 29-172 alarm messages 29-388
local area network See LAN LEDs 29-366
low density port shelf See LDPS optical parameters 29-330, 29-443
LSM 29-53 SDF48 cables 29-442
alarm messages 29-85 notes, textual, explanation of use 29-4
LAN Switch Module 29-171 NTD clock cables
LSM/LIP to CGC LAN cabling 29-468 hybrid switch core 29-304
LSM to APM LAN jumper cable 29-40 NTD connections on LTIP 29-305
LTIP NTDM 29-292
clock connections 29-403 alarm messages 29-269
connectors 29-197, 29-465 LEDs 29-248
LTIP to LIP cables 29-464 NTDM to NTDM cabling 29-302, 29-303
M O
Mapping Interface Module 29-815
OC-12 port module See OPM
Mapping Module 29-794
OC-3 port module See OPM
Message Log Port (MLP)
OC termination alarm messages 29-878
settings 29-1090
OPM12 LEDs 29-584
MIM 29-815
OPM12X4
LEDs 29-604, 29-606
OPM12X4 LEDs 29-586
MIM96E 29-824
OPM3 LEDs 29-584
Ethernet management cable location 29-17
Page 29-1244 7/07 76.5500/29, Rev R

OPM3X8 LEDs 29-587 R

OPM48
RCCPMA 29-784
OPM alarm messages 29-647, 29-651, 29-655
recovering the system 29-1123, 29-1164
optical fiber cable safety 29-10
redundant CCPMA 29-784
handling 29-11, 29-414, 29-521
redundant electrical port module See REPM
laser radiation 29-10, 29-413, 29-520
redundant Mapping Module 29-807
optical parameters
redundant port module See RPM
ESMU/TSI96 29-528, 29-536
REF 29-242
PAM/TSI96 29-545
PAM/TSI96P 29-421
relational port alarming 29-971, 29-1049
optical radiation 29-10, 29-413, 29-520
destination 29-1049
in-line configuration 29-1050, 29-1055
P loop-around configuration 29-1050, 29-1051
PAM 29-363, 29-405 source 29-1049
alarm messages 29-385 REMV alarm messages 29-91
receive fibers 29-547 REPM alarm messages 29-638
transmit power levels 29-546 resetting local AC 29-1141
PAM/TSI96 optical parameters 29-421, 29-545 RMM 29-807
PAM/TSI96P optical parameters 29-428 alarm messages 29-664
PAM LC fiber optic connectors 29-422 LEDs 29-598, 29-599, 29-600, 29-601, 29-602, 29-
PAM LEDs 29-364 603
PAM to TSI96P cabling 29-413 RPM
path integrity error 29-1027 DS1 and DD DS1 alarm messages 29-629
PC alarm messages 29-609 DS3 alarm messages 29-633
PGC STS-1 alarm messages 29-642
alarm messages 29-392, 29-481 RSD alarm messages 29-90
LEDs 29-474 rules, LAN 29-1060
Pluggable Transceiver 29-835
point-to-point protocol group 29-1020 S
point to point protocol group See PPPG
safety
point to point protocol See PPP
handling optical fiber cable 29-11, 29-414, 29-521
point-to-point protocol termination 29-1017
laser radiation 29-10, 29-413, 29-520
port aggregation module 29-363, 29-405
SCM
removal 29-37
alarm messages 29-77, 29-78
port group controller
LEDs 29-59
LAN problem 29-1059
SDF48 cabling
port group controller module See PGC
CAM 29-328
port module protection types 29-576
SDF48 mismatch alarms
port power supply module See PPS
CAM 29-331
Port Shelf Power Supply Module 29-568
SDF fiber cable integrity 29-413, 29-520
PPN 29-575
SDL cables 29-42
PPP alarm messages 29-892
SEC alarm messages 29-89
PPPG 29-1020
secondary memory partition
PPPG alarm messages 29-893
Data Storage Module 29-214
PPP termination 29-1017
secondary memory See SEC
PPS alarm messages 29-493
settings
PRI 29-210
Message Log Ports (MLP) 29-1090
System Integrity Reports (SIRPT) 29-1090
Primary Memory 29-210
shelf power test points 29-1119
product performance notice 29-245, 29-575
shielded data link cables 29-42
PT 29-835
SIM 29-146
LEDs 29-60, 29-61
Single Removable Memory 29-218
76.5500/29, Rev R 7/07 Page 29-1245

SPM 29-131 TSI96

jumper settings 29-137 SDF fiber cable integrity 29-522
SRM 29-218 TSI96P
STS-1 SDF fiber cable integrity 29-538
RPM alarm messages 29-642
termination alarm messages 29-871 U
STS-1 PM
USA Code for Federal Regulations (CFR) 29-10, 29-
413, 29-520
LEDs 29-582
utility mode menus
STS-1 port module See STS-1 PM
advanced I menu 29-1129, 29-1131, 29-1132, 29-
STS-1 termination 29-919
1137, 29-1139, 29-1140, 29-1147, 29-1148,
STS3C alarm messages 29-884
29-1152, 29-1156, 29-1157
synchronization cables 29-42
emergency recovery options menu 29-1129, 29-
Synchronization Interface Module 29-146
1131, 29-1137, 29-1138, 29-1144, 29-1147,
synchronization timing cables
29-1153, 29-1155
consolidated core switch with DS1 support 29-48
main menu 29-1128, 29-1133, 29-1136, 29-1141,
consolidated core switch without DS1 support 29-
29-1149, 29-1152, 29-1158
51
hybrid consolidated core switch 29-45
standard core switch 29-42 V
synchronous interface module See SIM VCG 29-1002
SYNC timing cables virtual concatenation group 29-1002
CCS switch core 29-161 voice quality enhancement 29-1033
hybrid switch core 29-154 VQE
system communications module See SCM acoustic echo delay 29-1043
System Integrity Reports (SIRPT) in-line mapping 29-1038
settings 29-1090 loop-around mapping 29-1039
System Processor Module 29-131 MM24V 29-1035
system recovery 29-1165 VQE grooming 29-1033
VQEPS 29-1035
T VT1
T1
CST alarm messages 29-887, 29-889
CST alarm messages 29-857
VT1 termination 29-925
DGR alarm messages 29-855
TRMINT alarm messages 29-860
T1INT 29-889 W
T1INT termination 29-971 warning statements, explanation of use 29-4
T2 alarm messages 29-862
T3 X
CST alarm messages 29-866, 29-867 X-COPY port LIP 29-172, 29-192
DGR alarm messages 29-863
TCP/IP 29-225
TERE 29-136
Time Slot Interchange Module 29-506
time slot interchange module 96P See TSI
time slot interchange module See TSI
Timing Reference 29-242
TIRE 29-136
TIRI 29-136
TL1 command explanation 29-7
transmit external, receive external 29-136
transmit internal, receive external 29-136
transmit internal, receive internal 29-136
TSI 29-506
Page 29-1246 7/07 76.5500/29, Rev R

USER NOTES
USER NOTES

Tellabs 5500 FP11.1 Trouble Shooting Manual PDF

Uploaded by

Copyright:

Available Formats

You might also like

Tellabs 5500 FP11.1 Trouble Shooting Manual PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tellabs 5500 FP11.1 Trouble Shooting Manual PDF

Uploaded by

Copyright:

Available Formats

®

Any other company or product names may be trademarks of their respective

Section 2 Troubleshooting the Administrative Complex 29-53

76.5500/29, Rev R 7/07 Page 29-i

Page 29-ii 7/07 76.5500/29, Rev R

Section 4 Troubleshooting Consolidated Core Switch Shelf

76.5500/29, Rev R 7/07 Page 29-iii

Section 5 Troubleshooting System Common Equipment 29-473

Section 6 Troubleshooting the Port Shelves 29-575

Page 29-iv 7/07 76.5500/29, Rev R

Section 7 Troubleshooting the Facilities 29-851

76.5500/29, Rev R 7/07 Page 29-v

Section 8 Troubleshooting VQE and DS0 Grooming

Page 29-vi 7/07 76.5500/29, Rev R

Section 10 Clearing Residual Alarms 29-1089

Section 11 Checking the Power to a Shelf 29-1105

Section 12 Restoring the System 29-1123

76.5500/29, Rev R 7/07 Page 29-vii

Page 29-viii 7/07 76.5500/29, Rev R

76.5500/29, Rev R 7/07 Page 29-ix

1.01 The Tellabs 5500/5500S Troubleshooting Manual, 76.5500/29, contains

76.5500/29, Rev R 7/07 Page 29-1

Table 1.1 HDPS Types

Page 29-2 7/07 76.5500/29, Rev R

Reason for Issue

Tellabs Technical Assistance

Note: If a specific system response or hardware indication does not

1.15 Prepare the following information before calling Tellabs:

• how much traffic is on the system

76.5500/29, Rev R 7/07 Page 29-3

Conventions Used in This Manual

Table 1.2 Highlights of Syntax Conventions Used in this Manual

Note: Provides the user with supplemental information or details.

Danger: Alerts the user to the possibility of personal injury.

Warning: Alerts the user to the possibility of equipment damage.

Performing Numbered Steps

Page 29-4 7/07 76.5500/29, Rev R

Figure 1.1 Example of Optional Substeps to a Numbered Step

Figure 1.2 Example of a Step Broken Down Into Substeps

__ 1.3 Place it in an antistatic bag and set it aside.

76.5500/29, Rev R 7/07 Page 29-5

Figure 1.3 Example of a Step With Checkmark Line and Response

__ 1. Place links 1 and link 5 in-service (IS):

Command and System Response Conventions

Table 1.3 Conventions Used in System Responses to Commands

Page 29-6 7/07 76.5500/29, Rev R

Table 1.3 Conventions Used in System Responses to Commands (Continued)

TL1 Command Language

• M ctag COMPLD is the normal system response to a correctly entered

• M ctag RTRV is the normal response to a RTRV command that

76.5500/29, Rev R 7/07 Page 29-7

Table 1.4 Abbreviations Used in this Manual

CCPMA Circuit Cell Packet Module (Abis/ATM))

CCSM Consolidated Core Switch Module

CCSS Consolidated Core Switch Shelf

CGCM Consolidated Group Controller Module

CPG STS-3c Path Protection Group

EPS Ethernet Port Shelf