LambdaUnite MultiService Switch (MSS)...Linear protection switching alarms Overview..... 3-128 Clearing Far End Signal Fail ..... 3-129 Clearing primary section Mismatch ..... 3-132

LambdaUnite® MultiService Switch(MSS)Release 6.2Alarm Messages and Trouble Clearing Guide

365-374-186CC109600163

Issue 1December 2005

Lucent Technologies - ProprietaryThis document contains proprietary information of Lucent Technologies and

is not to be disclosed or used except in accordance with applicable agreements.

Copyright © 2005 Lucent TechnologiesUnpublished and Not for Publication

All Rights Reserved

See notice on first page

This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced,distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicableagreements, contracts or licensing, without the express written consent of Lucent Technologies and the business management owner of thematerial.

Trademarks

All trademarks and service marks specified herein are owned by their respective companies.

Notice

Every effort has been made to ensure that the information in this document was complete and accurate at the time of printing. However,information is subject to change.

Declaration of Conformity

The Declaration of Conformity (DoC) for this product can be found in the MultiService Switch (MSS) Applications and Planning Guide in thechapter “Quality and reliability”, or at: http://www.lucent.de/ecl.

Ordering information

The order number of this document is 365-374-186 (Issue 1).

Technical support

Please contact your Lucent Technologies Local Customer Support Team (LCS) for technical questions about the information in this document.

Information product support

To comment on this information product online, go to http://www.lucent-info.com/comments or email your comments to [email protected].

See notice on first page

Lucent Technologies - ProprietarySee notice on first page

Contents

About this information product

Purpose .............................................................................................................................................................................................................. xixxix

Reason for reissue ...................................................................................................................................................................................... xixxix

Safety information ..................................................................................................................................................................................... xixxix

Intended audience ....................................................................................................................................................................................... xixxix

How to use this information product ............................................................................................................................................. xixxix

Conventions used ........................................................................................................................................................................................ xxixxi

Related documentation .......................................................................................................................................................................... xxiixxii

Related training ......................................................................................................................................................................................... xxivxxiv

Documented feature set ....................................................................................................................................................................... xxivxxiv

Intended use ................................................................................................................................................................................................ xxivxxiv

Optical safety ............................................................................................................................................................................................. xxivxxiv

Technical Documentation .................................................................................................................................................................. xxviixxvii

How to order ............................................................................................................................................................................................. xxviixxvii

How to comment .................................................................................................................................................................................. xxviiixxviii

1 Safety

Overview ......................................................................................................................................................................................................... 1-11-1

General notes on safety

Overview ......................................................................................................................................................................................................... 1-31-3

Structure of hazard statements ........................................................................................................................................................... 1-41-4

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


iii

Basic safety aspects .................................................................................................................................................................................. 1-71-7

Specific safety areas

Overview ....................................................................................................................................................................................................... 1-101-10

Laser safety ................................................................................................................................................................................................. 1-111-11

Optical circuit pack specifications ................................................................................................................................................ 1-141-14

Laser product classification ............................................................................................................................................................... 1-161-16

Electrostatic discharge .......................................................................................................................................................................... 1-201-20

Safety requirements in specific deployment phases

Overview ....................................................................................................................................................................................................... 1-221-22

Transportation ............................................................................................................................................................................................ 1-231-23

Storage ........................................................................................................................................................................................................... 1-251-25

Installation .................................................................................................................................................................................................... 1-271-27

Taking into operation ............................................................................................................................................................................ 1-291-29

Operation and maintenance ............................................................................................................................................................... 1-321-32

Taking out of operation ....................................................................................................................................................................... 1-371-37

2 Alarm messages

Overview ......................................................................................................................................................................................................... 2-12-1

DCN alarms

Overview ....................................................................................................................................................................................................... 2-102-10

Address List Overflow ......................................................................................................................................................................... 2-112-11

ASTN Neighbor Not Available ....................................................................................................................................................... 2-122-12

DCC MS/Line failure ........................................................................................................................................................................... 2-132-13

DCC RS/Section failure ...................................................................................................................................................................... 2-142-14

DCN Provisioning Not Valid ........................................................................................................................................................... 2-152-15

Partitioned Area Repair ....................................................................................................................................................................... 2-162-16

Protocol Version Mismatch ............................................................................................................................................................... 2-182-18

Contents

.................................................................................................................................................................................................................................

iv Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

DS3 alarms

Overview ....................................................................................................................................................................................................... 2-212-21

Degraded DS3 Line signal ................................................................................................................................................................ 2-222-22

DS3 AIS ........................................................................................................................................................................................................ 2-232-23

DS3 AIS egress ......................................................................................................................................................................................... 2-242-24

DS3 Application Mismatch in ......................................................................................................................................................... 2-252-25

DS3 IDLE in .............................................................................................................................................................................................. 2-262-26

DS3 LOF egress ....................................................................................................................................................................................... 2-272-27

DS3 Loss of Frame ................................................................................................................................................................................ 2-282-28

DS3 Loss of Signal ................................................................................................................................................................................ 2-292-29

DS3 RAI egress ........................................................................................................................................................................................ 2-302-30

DS3 RAI in ................................................................................................................................................................................................. 2-322-32

Environmental alarms

Overview ....................................................................................................................................................................................................... 2-342-34

Miscellaneous Discrete Input # (#=1 8) ............................................................................................................................... 2-352-35

Equipment alarms

Overview ....................................................................................................................................................................................................... 2-372-37

Abnormal condition ............................................................................................................................................................................... 2-392-39

Backplane Read Failure ....................................................................................................................................................................... 2-412-41

CICTL Comm Failure .......................................................................................................................................................................... 2-422-42

CICTL Failure ........................................................................................................................................................................................... 2-432-43

CICTL not Present .................................................................................................................................................................................. 2-442-44

CICTL Powered Down ........................................................................................................................................................................ 2-452-45

Circuit Pack Comm Failure .............................................................................................................................................................. 2-462-46

Circuit Pack Failure ............................................................................................................................................................................... 2-472-47

Circuit Pack not Present ...................................................................................................................................................................... 2-482-48

Circuit Pack Type Mismatch ............................................................................................................................................................ 2-502-50

Contents

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


v

Comm Channel Failure ........................................................................................................................................................................ 2-512-51

CTL Comm Failure ................................................................................................................................................................................ 2-522-52

Duplex Control not Present ............................................................................................................................................................... 2-532-53

ECI Comm Failure ................................................................................................................................................................................. 2-552-55

ECI Mismatch Failure .......................................................................................................................................................................... 2-562-56

ECI not Present ......................................................................................................................................................................................... 2-572-57

Fan Failure ................................................................................................................................................................................................... 2-582-58

Fan Unit Comm Failure ...................................................................................................................................................................... 2-592-59

Fan Unit Failure ....................................................................................................................................................................................... 2-602-60

Fan Unit not Present .............................................................................................................................................................................. 2-612-61

Fan Voltage Feed A Failure .............................................................................................................................................................. 2-622-62

Fan Voltage Feed B Failure .............................................................................................................................................................. 2-632-63

IDE Flash Card Access Fail ............................................................................................................................................................. 2-642-64

NVM Shortage .......................................................................................................................................................................................... 2-652-65

ONI Failure on protecting CTL ..................................................................................................................................................... 2-662-66

ONI Failure on working CTL ......................................................................................................................................................... 2-682-68

Optical Module Fail ............................................................................................................................................................................... 2-702-70

Optical Module not Present .............................................................................................................................................................. 2-722-72

Optical Module not supported ......................................................................................................................................................... 2-732-73

Optical Module Type Mismatch ..................................................................................................................................................... 2-742-74

Power Interface not Present .............................................................................................................................................................. 2-752-75

Power Interface Read Failure ........................................................................................................................................................ 2-762-76

System Power Failure ........................................................................................................................................................................... 2-782-78

TI Mismatch ............................................................................................................................................................................................... 2-792-79

TI not Present ............................................................................................................................................................................................ 2-802-80

TXI Failure ................................................................................................................................................................................................ 2-812-81

Unit Cooling Degraded ...................................................................................................................................................................... 2-832-83

Contents

.................................................................................................................................................................................................................................

vi Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

Unit Temperature too High .............................................................................................................................................................. 2-842-84

User Panel Comm Failure .................................................................................................................................................................. 2-862-86

User Panel not Present ......................................................................................................................................................................... 2-872-87

Ethernet alarms

Overview ....................................................................................................................................................................................................... 2-882-88

GFP Loss of Frame ................................................................................................................................................................................ 2-892-89

LAN Auto Negotiation Mismatch ................................................................................................................................................. 2-902-90

Loss of Alignment .................................................................................................................................................................................. 2-922-92

LAN Loss of Signal .............................................................................................................................................................................. 2-942-94

max number of VLAN instances reached ................................................................................................................................ 2-952-95

Partial Transport Capacity Loss ..................................................................................................................................................... 2-972-97

Server Signal Fail (VCGSSF) ......................................................................................................................................................... 2-982-98

Sink End Failure of Protocol ........................................................................................................................................................... 2-992-99

Source End Failure of Protocol ................................................................................................................................................... 2-1002-100

Total Transport Capacity Loss ...................................................................................................................................................... 2-1012-101

Linear protection switching alarms

Overview .................................................................................................................................................................................................... 2-1022-102

Far End Signal Fail ............................................................................................................................................................................. 2-1032-103

primary section Mismatch ............................................................................................................................................................... 2-1052-105

Prot. Arch. Mismatch ......................................................................................................................................................................... 2-1072-107

Prot. Arch. Mode Mismatch ........................................................................................................................................................... 2-1082-108

Prot. Arch. Operation Mismatch .................................................................................................................................................. 2-1102-110

Prot. Switch Byte Inappropriate .................................................................................................................................................. 2-1122-112

Prot. Switch Byte Unacceptable .................................................................................................................................................. 2-1142-114

Switch Channel Mismatch .............................................................................................................................................................. 2-1162-116

Contents

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


vii

Path-related transmission alarms

Overview .................................................................................................................................................................................................... 2-1172-117

Alarm Indication Signal (AIS-P) ................................................................................................................................................ 2-1192-119

Degraded Signal (DEG-P) ............................................................................................................................................................... 2-1202-120

Degraded Signal (THPDEG) ......................................................................................................................................................... 2-1212-121

Excessive Bit Error Ratio (EXC-P) .......................................................................................................................................... 2-1222-122

Excessive Bit Error Ratio (THPEXC) ..................................................................................................................................... 2-1242-124

Loss of Multiframe .............................................................................................................................................................................. 2-1262-126

Loss of Pointer (LOP-P) .................................................................................................................................................................. 2-1282-128

Loss of Pointer (THPLOP) ............................................................................................................................................................. 2-1292-129

Path Switch Denial .............................................................................................................................................................................. 2-1312-131

Payload Defect Indication ............................................................................................................................................................... 2-1322-132

Payload Mismatch ................................................................................................................................................................................ 2-1342-134

Remote Defect Indication (RFI-P) ............................................................................................................................................. 2-1352-135

Remote Defect Indication (THPRDI) ...................................................................................................................................... 2-1372-137

Sequence Number Mismatch ......................................................................................................................................................... 2-1382-138

Server Signal Fail (SSF-P) ............................................................................................................................................................. 2-1402-140

Server Signal Fail (THPSSF) ........................................................................................................................................................ 2-1412-141

Signal Rate Mismatch ........................................................................................................................................................................ 2-1422-142

Trace Identifier Mismatch (TIM-P) ........................................................................................................................................... 2-1442-144

Trace Identifier Mismatch (THPTIM) ..................................................................................................................................... 2-1452-145

Unequipped (UNEQ-P) ..................................................................................................................................................................... 2-1472-147

Unequipped (THPUNEQ) ............................................................................................................................................................... 2-1492-149

Port-related transmission alarms

Overview .................................................................................................................................................................................................... 2-1512-151

Alarm Indication Signal (AIS-L) ................................................................................................................................................ 2-1522-152

Backw Defect Transparent Ch ...................................................................................................................................................... 2-1542-154

Contents

.................................................................................................................................................................................................................................

viii Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

Degraded Signal (MSDEG) ............................................................................................................................................................ 2-1552-155

Excessive Bit Error Ratio (MSEXC) ....................................................................................................................................... 2-1572-157

LOF Transparent Ch ........................................................................................................................................................................... 2-1592-159

Loss of Frame ......................................................................................................................................................................................... 2-1602-160

Loss of Frame transp ch egress ................................................................................................................................................... 2-1622-162

Loss of Multiframe Transparent Ch .......................................................................................................................................... 2-1632-163

Loss of Signal ......................................................................................................................................................................................... 2-1642-164

OCh Loss of Frame ............................................................................................................................................................................. 2-1662-166

Payload Mismatch Transparent Ch ............................................................................................................................................ 2-1672-167

Post DCM Signal Loss ...................................................................................................................................................................... 2-1682-168

Pre DCM Signal Loss ........................................................................................................................................................................ 2-1702-170

Remote Defect Indication (RFI-L) ............................................................................................................................................. 2-1722-172

Server Signal Fail (MSSSF) .......................................................................................................................................................... 2-1732-173

Server Signal Fail Transparent Ch ............................................................................................................................................. 2-1742-174

Trace Identifier Mismatch (RSTIM) ......................................................................................................................................... 2-1752-175

Trace Identifier Mismatch egress (TIM-T-EGR) .............................................................................................................. 2-1762-176

WTU3 Loss of Frame ........................................................................................................................................................................ 2-1772-177

Ring protection switching alarms

Overview .................................................................................................................................................................................................... 2-1782-178

Default K-bytes ...................................................................................................................................................................................... 2-1792-179

Duplicate Ring Node .......................................................................................................................................................................... 2-1812-181

Extra Traffic Preempted .................................................................................................................................................................... 2-1832-183

Improper APS Codes .......................................................................................................................................................................... 2-1842-184

Inconsistent APS Codes .................................................................................................................................................................... 2-1862-186

Inconsistent Ring Protection Mode ........................................................................................................................................... 2-1882-188

Local Squelch Map Conflict .......................................................................................................................................................... 2-1892-189

Node ID Mismatch .............................................................................................................................................................................. 2-1912-191

Contents

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


ix

Open Ring ................................................................................................................................................................................................. 2-1922-192

Ring Discovery in Progress ............................................................................................................................................................ 2-1932-193

Ring Incomplete .................................................................................................................................................................................... 2-1952-195

Ring Protection Switch Suspended ............................................................................................................................................ 2-1972-197

Traffic Squelched .................................................................................................................................................................................. 2-1982-198

Unknown Ring Type ........................................................................................................................................................................... 2-2022-202

Synchronisation alarms

Overview .................................................................................................................................................................................................... 2-2032-203

Circuit Pack Clock Failure ............................................................................................................................................................. 2-2042-204

Loss of Synchronisation ................................................................................................................................................................... 2-2052-205

NE Clock Failure .................................................................................................................................................................................. 2-2062-206

Protection Clock Input Fail ............................................................................................................................................................ 2-2072-207

T4 quality unsufficient ...................................................................................................................................................................... 2-2082-208

Timing Reference Failure ................................................................................................................................................................ 2-2092-209

Worker Clock Input Fail .................................................................................................................................................................. 2-2102-210

Additional alarm-related information

Overview .................................................................................................................................................................................................... 2-2112-211

BLSR/MS-SPRing management information ...................................................................................................................... 2-2122-212

Automatic discovery of the ring topology ............................................................................................................................ 2-2152-215

Automatic node ID allocation ....................................................................................................................................................... 2-2192-219

Automatic discovery of the ring type ...................................................................................................................................... 2-2202-220

3 Trouble clearing

Overview ......................................................................................................................................................................................................... 3-13-1

DCN alarms

Overview ......................................................................................................................................................................................................... 3-53-5

Clearing DCC MS/Line failure ......................................................................................................................................................... 3-63-6

Contents

.................................................................................................................................................................................................................................

x Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

Clearing Partitioned Area Repair .................................................................................................................................................... 3-83-8

Clearing Protocol Version Mismatch ............................................................................................................................................. 3-93-9

Clearing DCC RS/Section failure .................................................................................................................................................. 3-113-11

DS3 alarms

Overview ....................................................................................................................................................................................................... 3-133-13

Clearing DS3 AIS ................................................................................................................................................................................... 3-143-14

Clearing DS3 AIS egress .................................................................................................................................................................... 3-153-15

Clearing DS3 Application Mismatch in .................................................................................................................................... 3-163-16

Clearing DS3 LOF egress .................................................................................................................................................................. 3-173-17

Clearing DS3 Loss of Frame ........................................................................................................................................................... 3-193-19

Clearing DS3 RAI egress ................................................................................................................................................................... 3-203-20

Clearing DS3 RAI in ............................................................................................................................................................................ 3-213-21

Equipment alarms

Overview ....................................................................................................................................................................................................... 3-223-22

Clearing CICTL Comm Failure ...................................................................................................................................................... 3-243-24

Clearing CICTL Failure ...................................................................................................................................................................... 3-283-28

Clearing CICTL not Present ............................................................................................................................................................. 3-293-29

Clearing Circuit Pack Comm Failure ......................................................................................................................................... 3-303-30

Clearing Circuit Pack not Present ................................................................................................................................................. 3-463-46

Clearing Circuit Pack Type Mismatch ....................................................................................................................................... 3-473-47

Clearing Circuit Pack Failure ........................................................................................................................................................ 3-493-49

Clearing Comm Channel Failure ................................................................................................................................................. 3-503-50

Clearing CTL Comm Failure ......................................................................................................................................................... 3-583-58

Clearing Duplex Control not Present .......................................................................................................................................... 3-603-60

Clearing ECI Comm Failure ............................................................................................................................................................ 3-613-61

Clearing ECI Mismatch Failure ..................................................................................................................................................... 3-653-65

Clearing ECI not Present .................................................................................................................................................................... 3-683-68

Contents

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


xi

Clearing Fan Failure ............................................................................................................................................................................ 3-693-69

Clearing Fan Unit Comm Failure ................................................................................................................................................. 3-723-72

Clearing Fan Unit Failure .................................................................................................................................................................. 3-763-76

Clearing Fan Unit not Present ......................................................................................................................................................... 3-803-80

Clearing Fan Voltage Feed A/B Failure .................................................................................................................................. 3-823-82

Clearing IDE Flash Card Access Fail ......................................................................................................................................... 3-873-87

Clearing NVM Shortage ..................................................................................................................................................................... 3-893-89

Clearing ONI Failure on protecting CTL ................................................................................................................................. 3-903-90

Clearing ONI Failure on working CTL ..................................................................................................................................... 3-933-93

Clearing Optical Module Fail .......................................................................................................................................................... 3-963-96

Clearing Optical Module not Present ......................................................................................................................................... 3-973-97

Clearing Optical Module not supported .................................................................................................................................... 3-983-98

Clearing Optical Module Type Mismatch ................................................................................................................................ 3-993-99

Clearing Power Interface not Present ...................................................................................................................................... 3-1003-100

Clearing Power Interface Read Failure ................................................................................................................................... 3-1013-101

Clearing System Power Failure ................................................................................................................................................... 3-1023-102

Clearing TI not Present ..................................................................................................................................................................... 3-1053-105

Clearing TXI Failure .......................................................................................................................................................................... 3-1063-106

Clearing Unit Cooling Degraded ................................................................................................................................................ 3-1093-109

Clearing Unit Temperature too High ........................................................................................................................................ 3-1123-112

Clearing User Panel Comm Failure .......................................................................................................................................... 3-1153-115

Clearing User Panel not Present .................................................................................................................................................. 3-1193-119

Ethernet alarms

Overview .................................................................................................................................................................................................... 3-1203-120

Clearing Loss of Alignment ........................................................................................................................................................... 3-1213-121

Clearing max number of VLAN instances reached ........................................................................................................ 3-1223-122

Clearing Partial Transport Capacity Loss .............................................................................................................................. 3-1233-123

Contents

.................................................................................................................................................................................................................................

xii Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

Clearing Server Signal Fail (VCGSSF) .................................................................................................................................. 3-1243-124

Clearing Sink End Failure of Protocol .................................................................................................................................... 3-1253-125

Clearing Source End Failure of Protocol ............................................................................................................................... 3-1263-126

Clearing Total Transport Capacity Loss ................................................................................................................................. 3-1273-127


Overview .................................................................................................................................................................................................... 3-1283-128

Clearing Far End Signal Fail ........................................................................................................................................................ 3-1293-129

Clearing primary section Mismatch .......................................................................................................................................... 3-1323-132

Clearing Prot. Arch. Mismatch .................................................................................................................................................... 3-1343-134

Clearing Prot. Arch. Mode Mismatch ...................................................................................................................................... 3-1353-135

Clearing Prot. Arch. Operation Mismatch ............................................................................................................................. 3-1363-136

Clearing Prot. Switch Byte Inappropriate ............................................................................................................................. 3-1373-137

Clearing Prot. Switch Byte Unacceptable ............................................................................................................................. 3-1383-138

Clearing Switch Channel Mismatch ......................................................................................................................................... 3-1423-142


Overview .................................................................................................................................................................................................... 3-1433-143

Clearing Alarm Indication Signal (AIS-P) ............................................................................................................................ 3-1443-144

Clearing Path Switch Denial ......................................................................................................................................................... 3-1453-145

Clearing Remote Defect Indication (RFI-P) ........................................................................................................................ 3-1463-146

Clearing Remote Defect Indication (THPRDI) .................................................................................................................. 3-1473-147

Clearing Server Signal Fail (SSF-P) ......................................................................................................................................... 3-1483-148

Clearing Server Signal Fail (THPSSF) ................................................................................................................................... 3-1493-149

Clearing Trace Identifier Mismatch (THPTIM) ................................................................................................................ 3-1503-150

Clearing Trace Identifier Mismatch (TIM-P) ...................................................................................................................... 3-1513-151

Clearing Unequipped (THPUNEQ) ........................................................................................................................................... 3-1523-152

Clearing Unequipped (UNEQ-P) ................................................................................................................................................ 3-1533-153

Contents

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


xiii

Port-related transmision alarms

Overview .................................................................................................................................................................................................... 3-1543-154

Clearing Alarm Indication Signal (AIS-L) ........................................................................................................................... 3-1553-155

Clearing Excessive Bit Error Ratio ........................................................................................................................................... 3-1563-156

Clearing Loss of Frame .................................................................................................................................................................... 3-1633-163

Clearing Loss of Frame transp ch egress .............................................................................................................................. 3-1663-166

Clearing Loss of Signal .................................................................................................................................................................... 3-1673-167

Clearing OCh Loss of Frame ........................................................................................................................................................ 3-1743-174

Clearing Post DCM Signal Loss ................................................................................................................................................. 3-1753-175

Clearing Pre DCM Signal Loss ................................................................................................................................................... 3-1763-176

Clearing Remote Defect Indication (RFI-L) ........................................................................................................................ 3-1773-177

Clearing Server Signal Fail (MSSSF) ...................................................................................................................................... 3-1783-178

Clearing Server Signal Fail Transparent Ch ........................................................................................................................ 3-1793-179

Clearing Trace Identifier Mismatch (RSTIM) .................................................................................................................... 3-1803-180

Clearing Trace Identifier Mismatch egress (TIM-T-EGR) .......................................................................................... 3-1813-181

Clearing WTU3 Loss of Frame ................................................................................................................................................... 3-1833-183


Overview .................................................................................................................................................................................................... 3-1843-184

Clearing Default K-bytes ................................................................................................................................................................. 3-1853-185

Clearing Duplicate Ring Node ..................................................................................................................................................... 3-1903-190

Clearing Extra Traffic Preempted ............................................................................................................................................... 3-1923-192

Clearing Improper APS Codes ..................................................................................................................................................... 3-1933-193

Clearing Inconsistent APS Codes ............................................................................................................................................... 3-1973-197

Clearing Inconsistent Ring Protection Mode ....................................................................................................................... 3-2023-202

Clearing Local Squelch Map Conflict ..................................................................................................................................... 3-2033-203

Clearing Ring Discovery in Progress ..................................................................................................................................... 3-2053-205

Clearing Ring Protection Switch Suspended ..................................................................................................................... 3-2073-207

Contents

.................................................................................................................................................................................................................................

xiv Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

Synchronisation

Overview .................................................................................................................................................................................................... 3-2103-210

Clearing Circuit Pack Clock Failure ......................................................................................................................................... 3-2113-211

Clearing Loss of Synchronisation .............................................................................................................................................. 3-2133-213

Clearing NE Clock Failure ............................................................................................................................................................. 3-2143-214

Clearing Protection Clock Input Fail ....................................................................................................................................... 3-2153-215

Clearing T4 quality unsufficient .................................................................................................................................................. 3-2173-217

Clearing Timing Reference Failure ........................................................................................................................................... 3-2193-219

Clearing Worker Clock Input Fail .............................................................................................................................................. 3-2223-222

4 Supporting procedures

Overview ......................................................................................................................................................................................................... 4-14-1

Retrieving the WaveStar® CIT NE Alarm List ....................................................................................................................... 4-34-3

The WaveStar® CIT NE Alarm List ............................................................................................................................................... 4-54-5

Retrieving the WaveStar® CIT NE Alarm Log ....................................................................................................................... 4-94-9

Identifying SDH tributaries in alarm messages .................................................................................................................... 4-104-10

Replacing the fan unit .......................................................................................................................................................................... 4-164-16

Replacing the air filter ......................................................................................................................................................................... 4-184-18

Cleaning optical fiber connectors .................................................................................................................................................. 4-214-21

Cleaning optical fiber couplings .................................................................................................................................................... 4-234-23

Performing cross-connection loopbacks .................................................................................................................................... 4-254-25

Releasing a cross-connection loopback ..................................................................................................................................... 4-284-28

Performing facility loopbacks .......................................................................................................................................................... 4-304-30

Releasing a facility loopback ........................................................................................................................................................... 4-334-33

Performing optical fiber loopbacks manually ........................................................................................................................ 4-354-35

Optical circuit pack parameters ...................................................................................................................................................... 4-374-37

Retrieving a list of currently active loopbacks ..................................................................................................................... 4-404-40

Restoring a database to a network element ............................................................................................................................ 4-434-43

Contents

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


xv

Replacing a CompactFlash® card ................................................................................................................................................. 4-484-48

Removing a circuit pack from the system ............................................................................................................................... 4-534-53

Replacing a circuit pack by a circuit pack of the same type ....................................................................................... 4-554-55

Exchanging a circuit pack without deprovisioning ............................................................................................................ 4-574-57

Replacing a circuit pack by a circuit pack of a different type ................................................................................... 4-604-60

Replacing the Controller (CTL) ..................................................................................................................................................... 4-624-62

Replacing a defective optical fiber ............................................................................................................................................... 4-644-64

Configuration rules ................................................................................................................................................................................. 4-664-66

Initiating a circuit pack reset ............................................................................................................................................................ 4-764-76

Initiating a system reset ....................................................................................................................................................................... 4-804-80

Cross-connection loopbacks .............................................................................................................................................................. 4-814-81

Facility loopbacks ................................................................................................................................................................................... 4-844-84

SDH/SONET tributary numbering ................................................................................................................................................ 4-874-87

TXI bus line numbering scheme ................................................................................................................................................. 4-1114-111

5 Exceptional situations not reflected by alarm messages

Overview ......................................................................................................................................................................................................... 5-15-1

Solving (and avoiding) Controller recovery problems ........................................................................................................ 5-25-2

System autonomously entered the maintenance condition ............................................................................................... 5-85-8

A Maintenance services and technical support

Overview ........................................................................................................................................................................................................ A-1A-1

Maintenance services .............................................................................................................................................................................. A-2A-2

Technical support ...................................................................................................................................................................................... A-3A-3

B A comparison of LambdaUnite® MSS and WaveStar® TDM 10G (STM-64) alarms

Overview ........................................................................................................................................................................................................ B-1B-1

Tabular overview of LambdaUnite® MSS and WaveStar® TDM 10G (STM-64) alarms ........................... B-2B-2

Glossary

Contents

.................................................................................................................................................................................................................................

xvi Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

Index

Contents

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


xvii


Purpose

This Alarm Messages and Trouble Clearing Guide (AMTCG) provides information onthe alarm messages which can be generated by the LambdaUnite® MSS networkelements. Furthermore, it provides procedures for routine maintenance, troubleshooting,diagnostics, and component replacement.

Reason for reissue

This is the first issue of the LambdaUnite® MSS Alarm Messages and TroubleClearing Guide for the LambdaUnite® MSS Release 6.2.

Safety information

This information product contains hazard statements for your safety. Hazard statementsare given at points where safety consequences to personnel, equipment, and operationmay exist. Failure to follow these statements may result in serious consequences.

Intended audience

The intended audience of this Alarm Messages and Trouble Clearing Guide primarilyconsists of people who are responsible for the maintenance of network elements andfor the supervision of transmission operation.

Training of personnel

Working on the complex equipments and systems described in this Alarm Messagesand Trouble Clearing Guide requires special training of the personnel. For moreinformation, please also read chapter 1 (“Safety”).

How to use this information product

Each chapter of this manual treats a specific aspect of the system and can be regardedas an independent description. This ensures that the reader can inform himselfaccording to his special needs. This also means that the manual provides moreinformation than needed by many of the readers. Before you start reading the manual,

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005,


xix

it is therefore necessary to assess which aspects or chapters will cover the individualarea of interest.

The following table briefly describes the type of information found in each chapter.

Preface About thisinformationproduct

This chapter

• describes the guide’s purpose, intended audience,and organization

• lists related documentation

• explains how to comment on this document

1 Safety This chapter contains a series of very importantsafety instructions concerning the handling ofLambdaUnite® MSS network elements.

2 Alarm messages This chapter contains descriptions of the alarmswhich can be generated by the LambdaUnite® MSSnetwork elements.

3 Trouble clearing This chapter describes the measures to be taken forlocalising and clearing faults on the LambdaUnite®

MSS network elements. It is based on the networkelement alarms that can be generated.

4 Supportingprocedures

This chapter covers tasks that are often used duringtrouble clearing and related information.

5 Exceptionalsituations

This chapter contains information about exceptionalsituations that may occur during the operation of aLambdaUnite® MSS network element, and which arenot reflected by alarm messages.

A Maintenanceservices andtechnical support

This appendix provides information about themaintenance services and the technical supportavailable for the LambdaUnite® MSS networkelements.

B Comparison of

alarmsThis appendix contains an overview table forcomparing similar LambdaUnite® MSS andWaveStar® TDM 10G (STM-64) alarm messages.

GL Glossary Defines telecommunication terms and expandscommon telecommunication abbreviations andacronyms

IN Index Lists specific subjects and their corresponding pagenumbers


.................................................................................................................................................................................................................................

xx Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

,

Conventions used

The following conventions are used throughout this Alarm Messages and TroubleClearing Guide:

Numbering

The chapters of this document are numbered consecutively. The page numberingrestarts at “1” in each chapter. To facilitate identifying pages in different chapters, thepage numbers are prefixed with the chapter number. For example, page 2-3 is the thirdpage in chapter 2.

Cross references

Cross reference conventions are identical with those used for numbering, i.e. the firstnumber in a reference to a particular page refers to the corresponding chapter.

Keyword blocks

This document contains so-called keyword blocks to facilitate the location of specifictext passages. The keyword blocks are placed to the left of the main text and indicatethe contents of a paragraph or group of paragraphs.

Typographical conventions

Special typographical conventions apply to elements of the graphical user interface(GUI), filenames and system path information, keyboard entries, alarm messages etc.

• Elements of the graphical user interface (GUI)These are examples of text that appears on a graphical user interface (GUI), suchas menu options, window titles or pushbuttons:

– Provision, Delete, Apply, Close, OK (pushbuttons)

– Provision Timing/Sync (window title)

– View Equipment Details (menu option)

– Administration → Security → User Provisioning (path for invoking awindow)

• Filenames and system path informationThese are examples of filenames and system path information:

– setup.exe

– C:\Program Files\Lucent Technologies

• Keyboard entriesThese are examples of keyboard entries:

– F1, Esc X, Alt-F, Ctrl-D, Ctrl-Alt-Del (simple keyboard entries)A hyphen between two keys means that both keys have to be pressedsimultaneously. Otherwise, a single key has to be pressed, or several keys haveto be pressed in sequence.

– copy abc xyz (command)


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005,


xxi

A complete command has to be entered.

• Alarms and error messagesThese are examples of alarms and error messages:

– Loss of Signal

– Circuit Pack Failure

– Ring Incomplete

Abbreviations

Abbreviations used in this document can be found in the “Glossary” unless it can beassumed that the reader is familiar with the abbreviation.

Related documentation

This section briefly describes the documents that are included in the LambdaUnite®

MSS documentation set.

• Installation Guide (IG)The LambdaUnite® MultiService Switch (MSS) Installation Guide is a step-by-stepguide to system installation and setup. It also includes information needed forpre-installation site planning and post-installation acceptance testing.

• Applications and Planning Guide (APG)The LambdaUnite® MultiService Switch (MSS) Applications and Planning Guide isfor use by network planners, analysts and managers. It is also for use by the LucentAccount Team. It presents a detailed overview of the system, describes itsapplications, gives planning requirements, engineering rules, ordering information,and technical specifications.

• User Operations Guide (UOG)The LambdaUnite® MultiService Switch (MSS) User Operations Guide providesstep-by-step information for use in daily system operations. The UOG demonstrateshow to perform system provisioning, operations, and administrative tasks by use ofthe WaveStar® CIT.

• Alarm Messages and Trouble Clearing Guide (AMTCG)The LambdaUnite® MultiService Switch (MSS) Alarm Messages and TroubleClearing Guide gives detailed information on each possible network element alarmmessage. Furthermore, the AMTCG provides procedures for routine maintenance,troubleshooting, diagnostics, and component replacement.

• Operations System Engineering Guide (OSEG)The LambdaUnite® MultiService Switch (MSS) Operations System EngineeringGuide serves as a reference for all TL1 commands which can be used to operatethe network element. The OSEG also gives an introduction to the concept of theTL1 commands, and an instruction how to use them.


.................................................................................................................................................................................................................................

xxii Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

,

The following table lists the documents included in the LambdaUnite® MSSdocumentation set, and related engineering drawings.

Document title Document code(UL-format)

LambdaUnite® MSS 6.2 Applications and PlanningGuide

109600155

(365-374-182)

LambdaUnite® MSS 6.2 User Operations Guide 109600171

(365-374-185)

LambdaUnite® MSS 6.2 Alarm Messages and TroubleClearing Guide

109600163

(365-374-186)

LambdaUnite® MSS 6.2 Installation Guide 109600197

(365-374-187)

LambdaUnite® MSS 6.2 Operations System EngineeringGuide (TL1 Reference Manual)

109600189

(365-374-188)

Navis® Optical EMS Provisioning Guide forLambdaUnite® MSS 6.2

109600379

(365-374-189)

LambdaUnite® MSS Safety Guide 109510909

(365-374-159)

CD-ROM Documentation LambdaUnite® MSS 6.2 (allLambdaUnite® MSS 6.2 guides on a CD-ROM)

109600205

(365-374-190)

TransLAN® Ethernet SDH Transport SolutionApplications and Planning Guide

109457192

(365-377-000)

LambdaUnite® MSS 6.2 Software Release Description This document is deliveredwith the NE software.

LambdaUnite® MSS Engineering and OrderingInformation

Drawing

ED8C948-10

LambdaUnite® MSS Interconnect and Circuit Information Drawing

ED8C948-20

These documents and drawings can be ordered at or downloaded from the CustomerInformation Center (CIC) at http://www.cic.lucent.com/, or via your Local CustomerSupport.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005,


xxiii

Related training

For detailed information about the training courses that are related to theLambdaUnite® MultiService Switch (MSS) please refer to the LambdaUnite® MSSApplications and Planning Guide, chapter 8 Product support - Training courses.

Documented feature set

This manual describes LambdaUnite® MSS Release 6.2. For technical reasons somefeatures have been documented that will not be available until later software versions.For precise information about the availability of features, please consult the SoftwareRelease Description. This provides details of the status at the time of software delivery.

Intended use

This equipment shall be used only in accordance with intended use, correspondinginstallation and maintenance statements as specified in this documentation. Any otheruse or modification is prohibited.

Optical safety

IEC Customer Laser Safety Guidelines

Lucent Technologies declares that this product is compliant with all essential safetyrequirements as stated in IEC 60825-Part 1 and 2 “Safety of laser products” and“Safety of optical fibre telecommunication systems”. Futhermore Lucent Technologiesdeclares that the warning statements on labels on this equipment are in accordancewith the specified laser radiation class.

Optical Safety Declaration (if laser modules used)

Lucent Technologies declares that this product is compliant with all essential safetyrequirements as stated in IEC 60825-Part 1 and 2 “Safety of Laser Products” and“Safety of Optical Fiber Telecommunication Systems”. Furthermore LucentTechnologies declares that the warning statements on labels on this equipment are inaccordance with the specified laser radiation class.

Optical Fiber Communications

This equipment contains an Optical Fiber Communications semiconductor laser/LEDtransmitter. The following Laser Safety Guidelines are provided for this product.

General Laser Information

Optical fiber telecommunication systems, their associated test sets, and similaroperating systems use semiconductor laser transmitters that emit infrared (IR) light atwavelengths between approximately 800 nanometers (nm) and 1600 nm. The emittedlight is above the red end of the visible spectrum, which is normally not visible to thehuman eye. Although radiant en at near-IR wavelengths is officially designatedinvisible, some people can see the shorter wavelength energy even at power levels


.................................................................................................................................................................................................................................

xxiv Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

,

several orders of magnitude below any that have been shown to cause injury to theeye.

Conventional lasers can produce an intense beam of monochromatic light. The term“monochromaticity” means a single wavelength output of pure color that may bevisible or invisible to the eye. A conventional laser produces a small-size beam oflight, and because the beam size is small the power density (also called irradiance) isvery high. Consequently, lasers and laser products are subject to federal and applicablestate regulations, as well as international standards, for their safe operation.

A conventional laser beam expands very little over distance, or is said to be very wellcollimated. Thus, conventional laser irradiance remains relatively constant overdistance. However, lasers used in lightwave systems have a large beam divergence,typically 10 to 20 degrees. Here, irradiance obeys the inverse square law (doubling thedistance reduces the irradiance by a factor of 4) and rapidly decreases over distance.

Lasers and Eye Damage

The optical energy emitted by laser and high-radiance LEDs in the 400-1400 nm rangemay cause eye damage if absorbed by the retina. When a beam of light enters the eye,the eye magnifies and focuses the energy on the retina magnifying the irradiance. Theirradiance of the energy that reaches the retina is approximately 105, or 100,000 timesmore than at the cornea and, if sufficiently intense, may cause a retinal burn.

The damage mechanism at the wavelengths used in an optical fiber telecommunicationsis thermal in origin, i.e., damage caused by heating. Therefore, a specific amount ofenergy is required for a definite time to heat an area of retinal tissue. Damage to theretina occurs only when one looks at the light long enough that the product of theretinal irradiance and the viewing time exceeds the damage threshold. Optical energiesabove 1400 nm cause corneal and skin burns, but do not affect the retina. Thethresholds for injury at wavelengths greater than 1400 nm are significantly higher thanfor wavelengths in the retinal hazard region.

Classification of Lasers

Manufacturers of lasers and laser products in the U.S. are regulated by the Food andDrug Administration’s Center for Devices and Radiological Health (FDA/CDRH) under21 CFR 1040. These regulations require manufacturers to certify each laser or laserproduct as belonging to one of four major Classes: I, II, lla, IlIa, lllb, or IV. TheInternational Electro-technical Commission is an international standards body thatwrites laser safety standards under IEC-60825. Classification schemes are similar withClasses divided into Classes 1, 1M, 2, 2M, 3R, 3B, and 4. Lasers are classifiedaccording to the accessible emission limits and their potential for causing injury.Optical fiber telecommunication systems are generally classified as Class I/1 because,under normal operating conditions, all energized laser transmitting circuit packs areterminated on optical fibers which enclose the laser energy with the fiber sheathforming a protective housing. Also, a protective housing/access panel is typically


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005,


xxv

installed in front of the laser circuit pack shelves The circuit packs themselves,however, may be FDA/CDRH Class I, IIIb, or IV or IEC Class 1, 1M, 3R, 3B, or 4.

Laser Safety Precautions for Optical Fiber Telecommunication Systems

In its normal operating mode, an optical fiber telecommunication system is totallyenclosed and presents no risk of eye injury. It is a Class I/1 system under the FDA andIEC classifications.

The fiber optic cables that interconnect various components of an optical fibertelecommunication system can disconnect or break, and may expose people to laseremissions. Also, certain measures and maintenance procedures may expose thetechnician to emission from the semiconductor laser during installation and servicing.Unlike more familiar laser devices such as solid-state and gas lasers, the emissionpattern of a semiconductor laser results in a highly divergent beam. In a divergentbeam, the irradiance (power density) decreases rapidly with distance. The greater thedistance, the less energy will enter the eye, and the less potential risk for eye injury.Inadvertently viewing an un-terminated fiber or damaged fiber with the unaided eye atdistances greater than 5 to 6 inches normally will not cause eye injury, provided thepower in the fiber is less than a few milliwatts at the near IR wavelengths and a fewtens of milliwatts at the far IR wavelengths. However, damage may occur if an opticalinstrument such as a microscope, magnifying glass, or eye loupe is used to stare at theenergized fiber end.

CAUTION

Laser hazard

Use of controls, adjustments, and procedures other than those specified herein mayresult in hazardous laser radiation exposure.

xx

Laser Safety Precautions for Enclosed Systems

Under normal operating conditions, optical fiber telecommunication systems arecompletely enclosed; nonetheless, the following precautions shall be observed:

1. Because of the potential for eye damage, technicians should not stare into opticalconnectors or broken fibers

2. Under no circumstance shall laser/fiber optic operations be performed by atechnician before satisfactorily completing an approved training course

3. Since viewing laser emissions directly in excess of Class I/1 limits with an opticalinstrument such as an eye loupe greatly increases the risk of eye damage,appropriate labels must appear in plain view, in close proximity to the optical porton the protective housing/access panel of the terminal equipment.


.................................................................................................................................................................................................................................

xxvi Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

,

Laser Safety Precautions for Unenclosed Systems

During service, maintenance, or restoration, an optical fiber telecommunication systemis considered unenclosed. Under these conditions, follow these practices:

1. Only authorized, trained personnel shall be permitted to do service, maintenanceand restoration. Avoid exposing the eye to emissions from un-terminated, energizedoptical connectors at close distances. Laser modules associated with the opticalports of laser circuit packs are typically recessed, which limits the exposuredistance. Optical port shutters, Automatic Power Reduction (APR), andAutomatic Power Shut Down (APSD) are engineering controls that are also used tolimit emissions. However, technicians removing or replacing laser circuit packsshould not stare or look directly into the optical port with optical instruments ormagnifying lenses. (Normal eye wear or indirect viewing instruments such asFind-R-Scopes are not considered magnifying lenses or optical instruments.)

2. Only authorized, trained personnel shall use optical test equipment duringinstallation or servicing since this equipment contains semiconductor lasers (Someexamples of optical test equipment are Optical Time Domain Reflectometers(OTDR’s), Hand-Held Loss Test Sets.)

3. Under no circumstances shall any personnel scan a fiber with an optical test setwithout verifying that all laser sources on the fiber are turned off

4. All unauthorized personnel shall be excluded from the immediate area of theoptical fiber telecommunication systems during installation and service.

Consult ANSI Z136.2, American National Standard for Safe Use of Lasers in the U.S.;or, outside the U.S., IEC-60825, Part 2 for guidance on the safe use of optical fiberoptic communication in the workplace.

For the optical specifications please refer to the chapter “Technical specifications” inthe LambdaUnite® MultiService Switch (MSS) Applications and Planning Guide.

Technical Documentation

The technical documentation as required by the Conformity Assessment procedure iskept at Lucent Technologies location which is responsible for this product. For moreinformation please contact your local Lucent Technologies representative.

How to order

This information product can be ordered with the order number 365-374-186 at theCustomer Information Center (CIC), see http://www.cic.lucent.com/.

An overview of the ordering process and the latest software & licences information isgiven in the LambdaUnite® MultiService Switch (MSS) Applications and PlanningGuide.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005,


xxvii

How to comment

To comment on this information product, go to the Online Comment Form(http://www.lucent-info.com/comments/enus/) or email your comments to theComments Hotline ([email protected]).

As customer satisfaction is extremely important to Lucent Technologies, every attemptis made to encourage feedback from customers about our information products. Thankyou for your feedback.


.................................................................................................................................................................................................................................

xxviii Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

,

http://www.lucent-info.com/comments/enus/

http://www.lucent-info.com/comments/enus/

1 1Safety

Overview.................................................................................................................................................................................................................................

Purpose

The aim of this chapter on safety is to provide users of LambdaUnite® MSS systemswith the relevant information and safety guidelines to safeguard against personal injury.Furthermore, this chapter may be useful to prevent material damage to the equipment.

The present chapter on safety must be read by the responsible technical personnelbefore carrying out relevant work on the system. The valid version of this documentmust always be kept close to the equipment.

Potential sources of danger

The LambdaUnite® MSS equipment has been developed in line with the presentstate-of-the-art and fulfils the current national and international safety requirements. Itis provided with a high degree of operational safety resulting from many years ofdevelopment experience and continuous stringent quality checks in our company.

The equipment is safe in normal operation. There are, however, some potential sourcesof danger that cannot be completely eliminated. In particular, these arise during the:

• opening of housings or equipment covers,

• manipulation of any kind within the equipment, even if it has been disconnectedfrom the power supply,

• disconnection of optical or electrical connections,

through possible contact with the following:

• live parts,

• laser light,

• hot surfaces, or

• sharp edges

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-1

Contents

General notes on safety 1-3

Structure of hazard statements 1-4

Basic safety aspects 1-7

Specific safety areas 1-10

Laser safety 1-11

Optical circuit pack specifications 1-14

Laser product classification 1-16

Electrostatic discharge 1-20

Safety requirements in specific deployment phases 1-22

Transportation 1-23

Storage 1-25

Installation 1-27

Taking into operation 1-29

Operation and maintenance 1-32

Taking out of operation 1-37

Safety Overview

.................................................................................................................................................................................................................................

1-2 Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

General notes on safety

Overview.................................................................................................................................................................................................................................

Purpose

This section provides general information on the structure of safety instructions andsummarizes general safety requirements.

Contents

Structure of hazard statements 1-4

Basic safety aspects 1-7

Safety

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-3

Structure of hazard statements.................................................................................................................................................................................................................................

Overview

Hazard statements describe the safety risks relevant while performing tasks on LucentTechnologies products during deployment and/or use. Failure to avoid the hazards mayhave serious consequences.

General structure

Hazard statements include the following structural elements:

Item Structure element Purpose

1 Personal injury symbol Indicates the potential for personal injury(optional)

2 Hazard type symbol Indicates hazard type (optional)

3 Signal word Indicates the severity of the hazard

4 Hazard type Describes the source of the risk of damage orinjury

5 Damage statement Consequences if protective measures fail

6 Avoidance message Protective measures to take to avoid the hazard

7 Identifier The reference ID of the hazard statement(optional)

Safety

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Signal words

The signal words identify the hazard severity levels as follows:

Signal word Meaning

DANGER Indicates an imminently hazardous situation (high risk) which, ifnot avoided, will result in death or serious injury.

WARNING Indicates a potentially hazardous situation (medium risk) which,if not avoided, could result in death or serious injury.

CAUTION When used with the personal injury symbol:

Indicates a potentially hazardous situation (low risk) which, ifnot avoided, may result in personal injury.

When used without the personal injury symbol:

Indicates a potentially hazardous situation (low risk) which, ifnot avoided, may result in property damage, such as serviceinterruption or damage to equipment or other materials.

General structure

All safety instructions include a warning symbol and a signal word that classify thedanger, and a text block that contains descriptions of the type and cause of the danger,the consequences of ignoring the safety instruction and the measures that can be takento minimize the danger.

Example:

WARNING

Arcing on removing or inserting a live power supply plug.

Arcing can cause burns to the hands and damage to the eyes.

Before removing or inserting the power supply plug at the Power Interface (PI/-),ensure that the line circuit breaker on the Power Interface is in the “OFF” position.

Danger classification

There are three classes of safety instructions: “DANGER”, “WARNING” and“CAUTION”. Which class is relevant depends on the consequences of ignoring thesafety instruction:

DANGER Serious injury is definite or likely.

Safety Structure of hazard statements

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-5

WARNING Serious injury is possible.

CAUTION Minor injury is definite, likely or possible, or material damage to theproduct or in the product environment is definite or likely.

Warning symbols

These warning symbols are defined for safety instructions:

Legend:

1 General warning of danger

2 Electric shock

3 Hazard of laser radiation

4 Magnetic hazard

5 Electromagnetic radiation

6 Components sensitive to electrostatic discharge (ESD)

7 Radioactivity

8 Hazard caused by batteries

9 Hot surface

10 Heavy load

11 Unhealthy, irritating substance

12 Hazard of falling

1

11 12

2 3 4 5 6

7 8 9 10

Safety Structure of hazard statements

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Basic safety aspects.................................................................................................................................................................................................................................

General safety requirements

In order to keep the technically unavoidable residual risk to a minimum, it isimperative to observe the following rules:

• Transport, storage and operation of the system must be under the permissibleconditions only.See accompanying documentation and information on the system.

• Installation, configuration and disassembly must be carried out only by expertpersonnel and with reference to the respective documentation.Due to the complexity of the system, the personnel requires special training.

• The system must be operated by expert and authorized users only.The user must operate the system only after having read and understood thischapter on safety and the parts of the documentation relevant to operation. Forcomplex systems, additional training is recommended. Any obligatory training foroperating and service personnel must be carried out and documented.

• The system must not be operated unless it is in perfect working order.Any faults and errors that might affect safety must be reported immediately by theuser to a person in responsibility.

• The system must be operated only with the connections and under theenvironmental conditions as described in the documentation.

• Any conversions or changes to the system or parts of the system (including thesoftware) must be carried out by qualified Lucent Technologies personnel or byexpert personnel authorized by Lucent Technologies.All changes carried out by other persons lead to a complete exemption fromliability.No components/spare parts must be used other than those recommended by themanufacturer and those listed in the procurement documents.

• The removal or disabling of safety facilities, the clearing of faults and errors, andthe maintenance of the equipment must be carried out by specially qualifiedpersonnel only.The respective parts of the documentation must be strictly observed. Thedocumentation must also be consulted during the selection of measuring and testequipment.

• Calibrations, special tests after repairs and regular safety checks must be carriedout, documented and archived.

• Non-system software is used at one’s own risk. The use/installation of non-systemsoftware can adversely affect the normal functioning of the system.

• Only use tested and virus-free data carriers (floppy disks, streamer tapes, ).

Safety

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-7

Summary of important safety instructions

Especially observe the following safety instructions, they are of particular importancefor LambdaUnite® MSS systems:

• This equipment is to be installed only in Restricted Access Areas in business andcustomer premises.Applications in accordance with Articles 110-16, 110-17 and 110-18 of the NationalElectrical Code, ANSI/NFPA No. 70. Other installations exempt from theenforcement of the National Electrical Code may be engineered according to theaccepted practices of the local telecommunications utility.

• This product should only be operated from the type of power source indicated onthe marking label.

• This equipment must be provided with a readily accessible disconnect device aspart of the building installation.

• Disconnect up to four (4) power supply connections when removing power fromthe system.

• Installation must include an independent frame ground drop to the building ground.Refer to the LambdaUnite® MSS Installation Guide.

• For information on proper mounting instructions, consult the LambdaUnite® MSSInstallation Guide.

• Install only equipment identified in the LambdaUnite® MSS Installation Guideprovided with this product. Use of other equipment may result in improperconnection of circuitry leading to fire or injury to persons.

• To reduce the risk of electrical shock, do not disassemble this product. Installationand service should be performed by trained personnel only. Opening or removingcovers and/or circuit boards may expose you to dangerous voltages or other risks.Incorrect re-assembly can cause electrical shock when the unit is subsequentlyused.

• Slots and openings in this product are provided for ventilation. To protect theproduct from overheating, these openings must not be blocked or covered. Thisproduct should not be placed in a built-in installation unless proper ventilation isprovided.

• Never push objects of any kind into this product through slots as they may touchdangerous voltage points or short-out parts that could result in a risk of fire orelectrical shock. Never spill liquids of any kind on the product.

Safety Basic safety aspects

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

• CAUTION: This equipment is designed to permit the connection of the groundedconductor of the DC supply circuit to the grounding conductor at the equipment.

1. This equipment shall be connected directly to the DC supply system groundingelectrode conductor or to a bonding jumper from a grounding terminal bar orbus to which the DC supply system grounding electrode conductor is connected.

2. This equipment shall be located in the same immediate area (such as, adjacentcabinets) as any other equipment that has a connection between the groundedconductor of the same DC supply circuit and the grounding conductor, and alsothe point of grounding of the DC system. The DC system shall not be groundedelsewhere.

3. The DC supply source is to be located within the same premises as thisequipment.

4. There shall be no switching or disconnection devices in the grounded circuitconductor between the DC source and the point of connection of the groundingelectrode conductor.

CAUTION

Laser hazard

LambdaUnite® MSS systems contain optical circuit packs that can emit laser radiationassessed as IEC Hazard Level 3A.

Therefore, LambdaUnite® MSS systems may only be installed in restricted accesslocations! Restricted access locations are controlled environments where there is noready access to the general public, but only to authorized persons who have receivedadequate training in laser safety.

Safety Basic safety aspects

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-9

Specific safety areas

Overview.................................................................................................................................................................................................................................

Purpose

The aspects of “laser safety” and “handling of components sensitive to electrostaticdischarge (ESD)” are of vital importance for the LambdaUnite® MSS equipment.Therefore, the key safety instructions for these subjects are summarized in thefollowing.

Contents

Laser safety 1-11

Optical circuit pack specifications 1-14

Laser product classification 1-16

Electrostatic discharge 1-20

Safety

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Laser safety.................................................................................................................................................................................................................................

System design

The LambdaUnite® MSS system complies with the Food and Drug Administration’sCenter for Devices and Radiological Health (FDA/CDRH) regulations FDA/CDRH 21CFR 1040.10 and 1040.11 as a Class I and with IEC 60825-1 as a Class 1 OpticalFiber Telecommunication laser product.

The system has been designed to ensure that the operating personnel is not endangeredby laser radiation during normal system operation. The safety measures specified in theFDA/CDRH regulations and the international standards IEC 60825 and DIN/EN 60825respectively are met. Please also refer to “Laser product classification” (p. 1-16).

These laser warning labels (not to scale) are affixed on the LambdaUnite® MSSequipment. They refer to the system as a whole in normal operation.

Release 1.0, Release 2.0

Safety

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-11

Release 2.1 onwards

Potential sources of danger

Beware of the following potential sources of danger which will remain despite allsafety measures taken:

• Laser radiation can cause damage to the skin and eyes.

• Laser radiation from optical transmission systems is in a wavelength range that isinvisible to the human eye.

Laser classes

The maximum output power of laser radiation depends on the type of laser diode used.The international standards IEC 60825 and DIN/EN 60825 respectively as well as theFDA/CDRH regulations define the maximum output power of laser radiation for eachlaser class in accordance with the wavelength.

Safety Laser safety

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

The classification scheme is based on the ability of the laser emission or the reflectedlaser emission to cause injury to the eye or skin during normal operating conditions.

Please also refer to “Laser product classification” (p. 1-16).

Laser safety instructions

Observe the following instructions to avoid exposing yourself and others to risk:

• Read the relevant descriptions in the manuals before taking equipment intooperation or carrying out any installation and maintenance work on the optical portunits, and follow the instructions. Ignoring the instructions may result in hazardouslaser radiation exposure.

• Do not view directly into the laser beam with optical instruments such as a fibermicroscope, because viewing of laser emission in excess of Class 1 limitssignificantly increases the risk of eye damage.

• Never look into the end of an exposed fiber or an open connector as long as theoptical source is still switched on.

• Ensure that the optical source is switched off before disconnecting optical fiberconnectors.

• In the event of doubt, check that the optical source is switched off by measuringwith an optical power meter.

CAUTION

Laser hazard

Use of controls, adjustments and procedures other than those specified herein mayresult in hazardous laser radiation exposure.

Safety Laser safety

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-13

Optical circuit pack specifications.................................................................................................................................................................................................................................

Specifications

The following table contains the specifications of the LambdaUnite® MSS opticalcircuit packs. Please refer to the LambdaUnite® MSS Applications and Planning Guidefor more detailed technical specifications.

Circuit pack Wavelength[nm]

Fiber type1

(core/claddingdiameter [µm])

Maximum outputpower[mW / dBm]

Laser class2

(IEC / FDA)

155 Mbit/s

OP155M/1.3IR16 (KFA18) 1310 SM (9/125) 0.15 / -8 1 / I

OM155/1.3LR1 (OM155A183) 1310 SM (9/125) 1 / 0 1 / I

OM155/1.3IR1 (OM155A184) 1310 SM (9/125) 0.15 / -8 1 / I

622 Mbit/s

OP622/1.3IR16 (KFA17) 1310 SM (9/125) 0.15 / -8 1 / I

OM622/1.3LR1 (OM622A181) 1310 SM (9/125) 1.6 / +2 1 / I

OM622/1.3IR1 (OM622A182) 1310 SM (9/125) 0.15 / -8 1 / I

2.5 Gbit/s

OP2G5/1.3IOR4 (KFA12) 1310 SM (9/125) 0.5 / −3 1 / I

OP2G5/1.3LR4 (KFA203) 1310 SM (9/125) 1.6 / +2 1 / I

OP2G5/1.5LR4 (KFA204) 1550 SM (9/125) 1.6 / +2 1 / I

OP2G5-1...32PWDM (KFA20) withOM2G5/921PWDM ... 959PWDM(OM2G5A921 ... OM2G5A959)

1560.61

1530.33SM (9/125) 1 / 0 1 / I

OM2G5/1.3SR1 (OM2G5A12) 1550 SM (9/125) 0.5 / −3 1 / I

OM2G5/1.3LR1 (OM2G5A203) 1310 SM (9/125) 1.6 / +2 1 / I

OM2G5/1.5LR1 (OM2G5A204) 1550 SM (9/125) 1.6 / +2 1 / I

10 Gbit/s

OP10/1.3IOR1 (KFA7) 1310 SM (9/125) 0.8 / –1 1 / I

OP10/1.5IR1 (KFA14) 1550 SM (9/125) 1.6 / +2 1 / I

OP10/1.5LR1 (KFA6)3 1550 SM (9/125) 20 / +13 1M / IIIb

OP10/0180/800G (KFA9, KFA81 159) 1530.72

1562.23SM (9/125) 0.41 / -3.8 1 / I

OP10/116/PWDM (KFA11, KFA6175) 1530.33 ...1560.61

SM (9/125) 1.6 / +2 1 / I

OP10/9285XT8650XT(KFA210 KFA482)

1554.537 ...1607.466

SM (9/125) 0.63 / -2 1 / I

OM10/1.3IOR1 (OM10G7) 1310 SM (9/125) 0.8 / –1 1 / I

Safety

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Circuit pack Wavelength[nm]

Fiber type1

(core/claddingdiameter [µm])

Maximum outputpower[mW / dBm]

Laser class2

(IEC / FDA)

OM10/1.5IR1 (OM10G14) 1550 SM (9/125) 1.6 / +2 1 / I

OM10/1.5LR1 (OM10G6) 1550 SM (9/125) 2.5 / +4 1 / I

40 Gbit/s

OP40/1.3IOR1 (KFA202) 1311 SM (9/125) 5 / +7 1M / IIIb

OP40/1.5LR1O (KFA3) 1555.75 SM (9/125) 20 / +13 1M / IIIb

OP40/9280XT 8650XT (KFA290 353) 1554.940

1607.466SM (9/125) 0.5 / -3 1 / I

Gigabit Ethernet

GE1/SX4 (KFA13) 850 MM (50/125) 0.4 / −4 1 / I

GE1/LX4 (KFA532) 1310 SM (9/125) 0.5 / -3 1 / I

Notes:

1. SM: Single-mode fiber, MM: multi-mode fiber.

2. It is the class of the circuit pack, not that of the telecommunications system as a whole, that is specified.

3. The OP10/1.5LR1 circuit packs delivered with the LambdaUnite® MSS releases 1.0 or 2.0 are classifiedas Class 3A laser products in accordance with the IEC classification (cf. “Laser product classification”(p. 1-16)).

Connector types

All optical circuit packs are equipped with LC-type connectors.

Safety Optical circuit pack specifications

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-15

Laser product classification.................................................................................................................................................................................................................................

Standards compliance

The LambdaUnite® MSS product complies with the applicable IEC standards and theFood and Drug Administration’s Center for Devices and Radiological Health(FDA/CDRH) regulations.

FDA/CDRH regulations

Laser products are classified in accordance with the FDA/CDRH - 21 CFR 1010 and1040. The classification scheme is based on the ability of the laser emission to causeinjury to the eye or skin during normal operating conditions.

In the United States, lasers and laser systems in the infrared wavelength range (greaterthan 700 nm) are assigned to one of the following classes (please refer to“FDA/CDRH laser classification” (p. 1-17)):

• Class I,

• Class IIIb or

• Class IV.

Laser classification is dependent upon operating wavelength, output power and fibermode field diameter (core diameter).

IEC requirements

The International Electro-Technical Commission (IEC) establishes standards for theelectrical and electronic industries. The IEC 60825 standard has been established forthe worldwide safety of laser products.

According to the IEC classification, lasers and laser systems in the infrared wavelengthrange (greater than 700 nm) are assigned to one of the following classes (please referto “IEC laser classification” (p. 1-17)):

• Class 1,

• Class 1M,

• Class 3R,

• Class 3B or

• Class 4.

There are some major differences between the FDA/CDRH regulations and the IECrequirements:

1. The Accessible Emission Limits (AEL) are different.

2. Class 3A applies to all wavelengths.

Safety

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

3. Class 3B requires strict engineering controls.

4. Classification is under single fault conditions.

FDA/CDRH laser classification

The following table provides an overview of laser classes for wavelengths of 1310 nmand 1550 nm in accordance with the FDA/CDRH regulations.

Laser class Wavelength Max. output power of laser radiation

I 1310 nm 1.53 mW +1.85 dBm

1550 nm 8.52 mW +9.3 dBm

IIIb 1310 nm 500 mW +27 dBm

1550 nm 500 mW +27 dBm

IV 1310 nm > 500 mW > +27 dBm

1550 nm > 500 mW > +27 dBm

Explanatory note: In the United States, lasers and laser systems are assigned to one ofthe following classes: Roman numerals I, IIa, II, IIIa, IIIb, and IV. Classes I, IIIb andIV apply to lasers of all wavelengths. Classes IIa, II and IIIa apply only to those lasersoperating within the visible wavelength range (400-700 nm). Lucent Technologies laserproducts typically operate in the infrared wavelength range (greater than 700 nm) and,therefore, are primarily in the Class I or Class IIIb classifications.

IEC laser classification

The following table provides an overview of laser classes for wavelengths of 1310 nmand 1550 nm in accordance with the IEC 60825-1 Ed. 1.2 (2001) standard. The precisepower limits depend on the mode field diameter and the numerical aperture (NA) ofthe laser source.


1 1310 nm 15.6 mW +11.93 dBm

1550 nm 10 mW +10 dBm

1M 1310 nm 50.84 mW +17.06 dBm

1550 nm 121.20 mW +20.84 dBm

3R 1310 nm 86 mW +18.92 dBm

1550 nm –1

Safety Laser product classification

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-17


3B 1310 nm 500 mW +27 dBm

1550 nm 500 mW +27 dBm

4 1310 nm > 500 mW > +27 dBm

1550 nm > 500 mW > +27 dBm

Notes:

1. Class 3R only exists if the maximum power is within five times the Accessible EmissionLimit (AEL) of Class 1.

In earlier editions of the IEC 60825 standard the following laser classes andcorresponding power limits were defined for wavelengths of 1310 nm and 1550 nm.


1 1310 nm 8.85 mW +9.5 dBm

1550 nm 10 mW +10 dBm

3A 1310 nm 24 mW +13.8 dBm

1550 nm 50 mW +17 dBm

3B 1310 nm 500 mW +27 dBm

1550 nm 500 mW +27 dBm

4 1310 nm > 500 mW > +27 dBm

1550 nm > 500 mW > +27 dBm

Notes:

1. Corresponding laser warning labels can still be found on equipment manufactured beforepublication of the IEC 60825-1 Ed. 1.2 (2001) standard.

Hazard level assignment

“Hazard level” refers to the potential hazard from laser emission at any location in anend-to-end optical fiber communication system that may be accessible during serviceor in the event of a failure. The assignment of hazard level uses the AELs for theclasses.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Hazard levels for optical transmission equipment are assigned in either of the followingtwo ways:

• the actual output power from the connector or fiber cut.

• if automatic power reduction is used, the output power at the connector or fiber cutat one second after automatic power reduction takes place, provided that maximumoutput and restart conditions are met.

Classification of optical telecommunication equipment

Optical telecommunication equipment is generally classified as IEC Class 1 orFDA/CDRH Class I, because under normal operating conditions the transmitter portsterminate on optical fiber connectors. These are covered by a front panel to ensureprotection against emissions from any energized, unterminated transmitter.

The circuit packs themselves, however, may be IEC Class 1 or 1M or FDA/CDRHClass I or Class IIIb.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-19

Electrostatic discharge.................................................................................................................................................................................................................................

Introduction

Electrostatic discharge (ESD), caused by touching with the hand for example, candestroy semiconductor components. The correct operation of the complete system isthen no longer assured.

Industry experience has shown that all semiconductor components can be damaged bystatic electricity that builds up on work surfaces and personnel. The electrostaticdischarge can also affect the components indirectly via contacts or conductor tracks.The electrostatic charges are produced by various charging effects of movement andcontact with other objects. Dry air allows greater static charges to accumulate. Higherpotentials are measured in areas with low relative humidity, but potentials high enoughto cause damage can occur anywhere.

The barred-hand symbol

Circuit packs containing components that are especially sensitive to electrostaticdischarge are identified by warning labels bearing the barred-hand symbol.

ESD instructions

Observe the following ESD instructions to avoid damage to electrostatic-sensitivecomponents:

• Wear working garment made of 100% cotton to avoid electrostatic charging.

• Touch the circuit packs at the edges or the insertion and removal facilities only.

• Ensure that the rack is grounded.

• Wear conductively connected wrist straps and connect them to the rack ESPbonding point.

• Work in an area which is protected against electrostatic discharge. Use conductingfloor and bench mats which are conductively connected to the rack ESP bondingpoint.

• Conductively connect all test equipment and trolleys to the rack ESP bonding point.

Safety

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

• Store and ship circuit packs and components in their shipping packing. Circuitpacks and components must be packed and unpacked only at workplaces suitablyprotected against build-up of charge.

• Whenever possible, maintain the relative humidity of air above 20%.

Safety Electrostatic discharge

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-21

Safety requirements in specific deployment phases

Overview.................................................................................................................................................................................................................................

Purpose

To enable rapid orientation, safety instructions are given on the following pages, whichare assigned to various stages in the life cycle of the LambdaUnite® MSS equipment(“deployment phases”).

Deployment phases

The instructions are arranged according to the following deployment phases:

• “Transportation” (p. 1-23)

• “Storage” (p. 1-25)

• “Installation” (p. 1-27)

• “Taking into operation” (p. 1-29)

• “Operation and maintenance” (p. 1-32)

• “Taking out of operation” (p. 1-37)

Contents

Transportation 1-23

Storage 1-25

Installation 1-27

Taking into operation 1-29

Operation and maintenance 1-32

Taking out of operation 1-37

Safety

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Transportation.................................................................................................................................................................................................................................

Weight

WARNING

Risk of injury due to unsecured shelf.

A fully-equipped shelf weighs more than 30 kg and can cause considerable injuries if itis knocked over or dropped. This can also cause serious damage to the shelf.

Use a sturdy vehicle for transportation and secure the shelf against dropping. At leasttwo persons are required for lifting the shelf.

Packaging

CAUTION

Adverse effect on operation due to incorrect packaging.

Dampness and soiling can cause corrosion or tracking paths. This can causemalfunctioning of the system components. Shocks can cause damage.

Protect the system components against dampness, soiling and shocks. Use the originalantistatic packaging if possible.

Climatic conditions

CAUTION

Damage to system components under extreme environmental conditions.

Extreme environmental conditions can damage system components and causemalfunctioning.

Ensure that the climatic limits for transportation and storage of LambdaUnite® MSSequipment are complied with during transportation; please refer to “Climatic limits fortransportation and storage” (p. 1-24).

Safety

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-23

Climatic limits for transportation and storage

These are the climatic limits for transportation and storage of LambdaUnite® MSSsystems:

Temperature range -40 °C to +70 °C

(exceptional: up to +85 °C)

Humidity range relative humidity: 10% to 100%

absolute humidity: 0.5 g/m3 to 29 g/m3

The following climatogram visualizes these climatic limits:

Legend:

1 Air temperature in degrees Celsius [°C] or degrees Fahrenheit [°F]

2 Relative humidity [%]

3 Absolute humidity [g/m3]. The dashed curves specify a constantabsolute humidity of 0.5 g/m3 or 29 g/m3, respectively.

4 Permissible range for transportation and storage of LambdaUnite®

MSS systems.

5 Exceptional conditions, permissible for a short duration only.

0

60

30

10

70

40

20

90

80

50

-10

-40

-30

-20

-50

29

0.5

1

3

0 10 20 30 7040 8050 9060 100

2

4

5

Safety Transportation

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Storage.................................................................................................................................................................................................................................

Weight

WARNING



Use only a stable base for storage and secure the shelf against dropping. At least twopersons are required for lifting the shelf.

Electrostatic discharge (ESD)

CAUTION

ESD hazard

Electronic components can be destroyed by electrostatic discharge.

Circuit packs must therefore always be kept in antistatic covers. Use the originalantistatic packaging if possible. Always observe the ESD instructions (cf. “Electrostaticdischarge” (p. 1-20)).

Packaging

CAUTION

Adverse effect on operation due to incorrect packaging.

Dampness and soiling can cause corrosion or tracking paths. This can causemalfunctioning of the system components. Shocks can cause damage.

Protect the system components against dampness, soiling and shocks. Use the originalantistatic packaging if possible.

Safety

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-25

Climatic conditions

CAUTION



Ensure that the climatic limits for transportation and storage of LambdaUnite® MSSequipment are complied with during storage; please refer to “Climatic limits fortransportation and storage” (p. 1-24).

Safety Storage

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Installation.................................................................................................................................................................................................................................

Weight

WARNING



At least two persons are required for lifting the shelf.

Laser warning labels

WARNING

Laser hazard

Warning labels on the system and especially on the optical components warn of thedangers of invisible laser radiation. Removed, concealed or illegible labels can lead toincorrect action and thus cause serious injuries to the eyes of operating staff.

Ensure that the laser warning labels are not removed or concealed and always clearlylegible.


CAUTION

ESD hazard


Hold circuit packs only at the edges or on the insertion and removal facilities. Alwaysobserve the ESD instructions (cf. “Electrostatic discharge” (p. 1-20)).

Safety

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-27

Overheating

CAUTION

Risk of fire due to overheating.

Inadequate heat dissipation can cause heat accumulation or even a fire in the networkelement.

You must therefore ensure that

• the fan unit is installed,

• the individual fans are not obstructed,

• the minimum separation is maintained between two shelves in a rack (follow theinstallation instructions given in the LambdaUnite® MSS Installation Guide).

Detector diodes

CAUTION

Destruction of the detector diodes caused by too high an input power.

Connecting the output and input of optical circuit packs with a transmit power inexcess of -3 dBm over short distances will cause the destruction of the detector diodes,as the input power is then too high.

Use an optical attenuator pad of approx. 10 to 20 dB when establishing connectionsover short distances for test purposes.

The following label is affixed on the LambdaUnite® MSS subrack:

Receiver sensitivities

You can find the receiver sensitivities in the LambdaUnite® MSS Applications andPlanning Guide (Technical specifications).

Safety Installation

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Taking into operation.................................................................................................................................................................................................................................

Invisible laser radiation

DANGER

Laser hazard

LambdaUnite® MSS systems operate with invisible laser radiation. Laser radiation cancause considerable injuries to the eyes.

Never look into the end of an exposed fiber or into an open optical connector as longas the optical source is switched on. Always observe the laser warning instructions (cf.“Laser safety” (p. 1-11)).

Arcing

DANGER

Power Interface PI/-: Arcing on removing or inserting a live powersupply plug.



DANGER

Power Interface PI/100: Arcing on removing or connecting livepower supply cable lugs.


Before removing or connecting the power supply cable lugs at the Power Interface(PI/100), ensure that the line circuit breaker on the Power Interface is in the “OFF”position.

Safety

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-29

DANGER

Power Interface PI/100NOCB: Arcing on removing or connectinglive power supply cable lugs.


Before removing or connecting the power supply cable lugs at the Power Interface(PI/100NOCB), ensure that the power supply line is switched off at the upstreamcircuit breaker in the BDFB (Battery Distribution and Fuse Bay) or PDP (PowerDistribution Panel).

Supply voltage

CAUTION

Destruction of components due to a supply voltage of incorrect polarity ortoo high.

LambdaUnite® MSS equipment operates at a nominal voltage of -48 V or -60 V. Thepermissible tolerance range is -40.5 V to -72 V.

Ensure that the supply voltage has the correct range and polarity before connecting thevoltage.

Fusing

CAUTION

Risk of fire in the event of a short-circuit.

A short-circuit can cause a fire in the network element.

Protect all supply lines with line circuit breakers matched to the load of the shelfequipment. Note the relevant guide values in the LambdaUnite® MSS InstallationGuide.

Safety Taking into operation

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Condensation

CAUTION

Condensation causes malfunctioning

Condensation can occur in the network element during transport, especially on movingfrom outside to closed rooms; this can cause malfunctioning of the circuit packs.

Ensure that circuit packs and shelves have reached room temperature and are drybefore taking them into operation.

Safety Taking into operation

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-31

Operation and maintenance.................................................................................................................................................................................................................................


DANGER

Laser hazard



Arcing

DANGER




DANGER




Safety

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

DANGER




Laser warning labels

WARNING

Laser hazard

Warning labels on the system and especially on the optical components warn of thedangers of invisible laser radiation. Removed, concealed or illegible labels can lead toincorrect action and thus cause serious injuries to the eyes of operating staff.

Ensure that the laser warning labels are not removed or concealed and always clearlylegible.


CAUTION

ESD hazard



Safety Operation and maintenance

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-33

Overheating

CAUTION

Risk of fire due to overheating.

Inadequate heat dissipation can cause heat accumulation or even a fire in the networkelement.

You must therefore ensure that

• the fan unit is installed,

• the individual fans are not obstructed,

• the minimum separation is maintained between two shelves in a rack (follow theinstallation instructions given in the LambdaUnite® MSS Installation Guide).

Detector diodes

CAUTION

Destruction of the detector diodes caused by too high an input power.

Connecting the output and input of optical circuit packs with a transmit power inexcess of -3 dBm over short distances will cause the destruction of the detector diodes,as the input power is then too high.

Use an optical attenuator pad of approx. 10 to 20 dB when establishing connectionsover short distances for test purposes.

The following label is affixed on the LambdaUnite® MSS subrack:

Receiver sensitivities

You can find the receiver sensitivities in the LambdaUnite® MSS Applications andPlanning Guide (Technical specifications).


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Short-circuit

CAUTION

Destruction of circuit packs in the event of a short-circuit.

A short-circuit in the network element can cause destruction of electronic componentsand thus malfunctioning of the complete system.

You must therefore not handle objects such as a screwdriver in the circuit pack area ofthe shelf.

Test voltage

CAUTION

Destruction of components due to test voltage of incorrect polarity or toohigh.

The use of test voltages above 6 V DC for measurements on circuit packs can causedestruction of components and thus malfunctioning of the complete system.

Ensure that the test voltage does not exceed 6 V DC and that the test equipment isconnected with the correct polarity.

Climatic conditions

CAUTION



Ensure that the “Climatic limits for the operation of LambdaUnite® MSS equipment”(p. 1-35) are complied with during operation.

Climatic limits for the operation of LambdaUnite® MSS equipment

These are the climatic limits for the operation of LambdaUnite® MSS systems:

Temperature range +5 °C to +40 °C

(exceptional: –5 °C to +50 °C)

Humidity range relative humidity: 5% to 85% (exceptional: 90%),

absolute humidity: 0 to 24 g water per kg dry air


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-35

The following climatogram visualizes these climatic limits:

Legend:

1 Air temperature in degrees Celsius [°C] or degrees Fahrenheit [°F]

2 Relative humidity [%]

3 Absolute humidity [g water/kg dry air]. The dashed curve specifies aconstant absolute humidity of 24 g water per kg dry air.

4 Permissible range for the operation of LambdaUnite® MSS systems.

5 Exceptional conditions, permissible for a short duration only.

0

60

30

10

70

40

20

50

-10

0 10 20 30 7040 8050 9060 100

1

2

24

3

4

5


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Taking out of operation.................................................................................................................................................................................................................................


DANGER

Laser hazard



Arcing

DANGER




DANGER




Safety

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


1-37

DANGER




Weight

WARNING



At least two persons are required for lifting the shelf.


CAUTION

ESD hazard



Disposal

The equipment in the LambdaUnite® MSS system series must be disposed of at theend of its lifetime. Please contact us in this case and we will arrange for proper andenvironment-friendly disposal of your equipment (most parts of the system can berecycled).

Safety Taking out of operation

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

2 2Alarm messages

Overview.................................................................................................................................................................................................................................

Purpose

The present chapter contains information about the alarm messages that can bereported by LambdaUnite® MultiService Switch (MSS) network elements.

Introduction

This chapter on network element (NE) alarm messages is divided thematically into thefollowing sections:

• “DCN alarms” (p. 2-10)

• “DS3 alarms” (p. 2-21)

• “Environmental alarms” (p. 2-34)

• “Equipment alarms” (p. 2-37)

• “Ethernet alarms” (p. 2-88)

• “Linear protection switching alarms” (p. 2-102)

• “Path-related transmission alarms” (p. 2-117)

• “Port-related transmission alarms” (p. 2-151)

• “Ring protection switching alarms” (p. 2-178)

• “Synchronisation alarms” (p. 2-203)

• “Additional alarm-related information” (p. 2-211)

The alarm descriptions are alphabetically ordered within each section according to thealarm text displayed in the Description column of the WaveStar® CIT NE Alarm List.

The information provided for each alarm includes the meaning of the alarm, thealarm’s short designation (alarm identifier, mnemonic), the alarm category, the type ofalarm severity assignment profile (ASAP) the alarm belongs to, the alarm’s defaultseverity etc.

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-1

Local indications via the red fault LED on the circuit pack faceplate, additionalalarm-related information, consequent actions, and how protection switching isinfluenced by the corresponding alarm, are described, if appropriate.

Furthermore, a reference to the corresponding trouble clearing procedure is provided.

Defects and alarms

Please note that there is a difference between defects and alarms which is described indetail in the LambdaUnite® MSS User Operations Guide in the “Alarm managementconcepts” chapter.

General alarm information

Each NE alarm description contains a brief tabular overview of the main alarmcharacteristics:

Alarm identifier “LOS”, “LOF” or “DUPL-RNG” for example

ASAP type “System Timing” for example

Alarm category “Equipment” for example

Effect-on-service “Not service-affecting (NSA)” for example

Alarm severity (defaultsetting)

“Critical” for example

Alarm source “Circuit pack” or “STS-12C” for example.

In the following, the general meaning of these characteristics will be desribed in moredetail.

Alarm identifier

The “Alarm identifier” entry in the alarm overview table gives the alarm’s abbreviateddesignation as displayed in the Probable Cause column of the WaveStar® CIT NEAlarm List.

Alphabetical index

Please refer to the alphabetical index provided with this information product to findinformation concerning alarms of which you only know the alarm short designation.

Alarm category

The “Alarm category” entry in the alarm overview table indicates the functional area towhich the relevant alarm belongs.

Alarm messages Overview

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

The NE alarms are assigned to the following alarm categories:

• CommunicationThis alarm category comprises alarms related to the management communication(DCN, SCN), synchronisation and transmission. Therefore, the “Communication”alarm category is subdivided into:

– Communication (DCN)

– Communication (SCN)

– Communication (Synchronisation)

– Communication (Transport)

• EnvironmentThis alarm category is used for environmental alarms, detected by means ofMiscellaneous Discrete Inputs (MDIs).

• EquipmentThis alarm category is used for hardware- and configuration-related alarms andalarms concerning the internal communication.

• Processing errorThis alarm category is used for alarms related to problems or failures of the controlsystem software, due to overload situations for example.

ASAP type

The “ASAP type” entry in the alarm overview table indicates the type of alarmseverity assignment profile (ASAP) to which the corresponding alarm belongs.

Please refer to the LambdaUnite® MSS User Operations Guide for information aboutthe available ASAP types.

Effect-on-service

To reflect the service state, an effect-on-service attribute is assigned to each alarm asfar as possible.

Possible values of the effect-on-service attribute are:

• Service-affecting (SA),

• Not service-affecting (NSA).

The effect-on-service attribute indicates if transmission on a path may be affected (SA)or not (NSA).

Please note that the effect-on-service attribute is assessed solely from a local point ofview. Network aspects outside the network element are not taken into consideration.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-3

Default alarm severity

The “Alarm severity (default setting)” entry in the alarm overview table indicates thefactory settings of the corresponding alarm’s severity.

Alarm severities can be assigned by means of alarm severity assignment profiles(ASAPs). The default alarm severity is the alarm severity as originally specified in theASAPs named “DEFAULT”.

Please refer to the LambdaUnite® MSS User Operations Guide for information aboutalarm severities, the available ASAP types, and how alarm severities can be assigned.

Alarm source

The “Alarm source” entry in the alarm overview table specifies the alarm originationpoint, i.e. the system component where the alarm has been detected or the affectedsignal level in case of transmission alarms.

Local indications

Local indications are indications via the circuit pack faceplate LEDs, especially via thered fault LED.

Please note that the local indications via the red fault LED on the circuit packfaceplate is controlled by defects, not alarms.

Important! The signalling of alarms by means of the user panel LEDs or the officealarm interfaces is not taken into consideration in this Alarm Messages and TroubleClearing Guide because the signalling of alarms by means of the user panel LEDsor the office alarm interfaces depends on the actual value of the alarm severityassigned.

Related information

Please refer to the LambdaUnite® MSS User Operations Guide for further information.

Consequent actions

Consequent actions mean the autonomous insertion of maintenance signals as theconsequence of a detected defect.

Please note that the insertion of consequent actions, for example insertion of an AlarmIndication Signal (AIS) or a Remote Defect Indication (RDI), is controlled by defects,not alarms.

Contents

DCN alarms 2-10


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Address List Overflow 2-11

ASTN Neighbor Not Available 2-12

DCC MS/Line failure 2-13

DCC RS/Section failure 2-14

DCN Provisioning Not Valid 2-15

Partitioned Area Repair 2-16

Protocol Version Mismatch 2-18

DS3 alarms 2-21

Degraded DS3 Line signal 2-22

DS3 AIS 2-23

DS3 AIS egress 2-24

DS3 Application Mismatch in 2-25

DS3 IDLE in 2-26

DS3 LOF egress 2-27

DS3 Loss of Frame 2-28

DS3 Loss of Signal 2-29

DS3 RAI egress 2-30

DS3 RAI in 2-32

Environmental alarms 2-34

Miscellaneous Discrete Input # (#=1 8) 2-35

Equipment alarms 2-37

Abnormal condition 2-39

Backplane Read Failure 2-41

CICTL Comm Failure 2-42

CICTL Failure 2-43

CICTL not Present 2-44

CICTL Powered Down 2-45

Circuit Pack Comm Failure 2-46

Circuit Pack Failure 2-47

Circuit Pack not Present 2-48

Circuit Pack Type Mismatch 2-50

Comm Channel Failure 2-51


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-5

CTL Comm Failure 2-52

Duplex Control not Present 2-53

ECI Comm Failure 2-55

ECI Mismatch Failure 2-56

ECI not Present 2-57

Fan Failure 2-58

Fan Unit Comm Failure 2-59

Fan Unit Failure 2-60

Fan Unit not Present 2-61

Fan Voltage Feed A Failure 2-62

Fan Voltage Feed B Failure 2-63

IDE Flash Card Access Fail 2-64

NVM Shortage 2-65

ONI Failure on protecting CTL 2-66

ONI Failure on working CTL 2-68

Optical Module Fail 2-70

Optical Module not Present 2-72

Optical Module not supported 2-73

Optical Module Type Mismatch 2-74

Power Interface not Present 2-75

Power Interface Read Failure 2-76

System Power Failure 2-78

TI Mismatch 2-79

TI not Present 2-80

TXI Failure 2-81

Unit Cooling Degraded 2-83

Unit Temperature too High 2-84

User Panel Comm Failure 2-86

User Panel not Present 2-87

Ethernet alarms 2-88

GFP Loss of Frame 2-89

LAN Auto Negotiation Mismatch 2-90


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Loss of Alignment 2-92

LAN Loss of Signal 2-94

max number of VLAN instances reached 2-95

Partial Transport Capacity Loss 2-97

Server Signal Fail (VCGSSF) 2-98

Sink End Failure of Protocol 2-99

Source End Failure of Protocol 2-100

Total Transport Capacity Loss 2-101

Linear protection switching alarms 2-102

Far End Signal Fail 2-103

primary section Mismatch 2-105

Prot. Arch. Mismatch 2-107

Prot. Arch. Mode Mismatch 2-108

Prot. Arch. Operation Mismatch 2-110

Prot. Switch Byte Inappropriate 2-112

Prot. Switch Byte Unacceptable 2-114

Switch Channel Mismatch 2-116

Path-related transmission alarms 2-117

Alarm Indication Signal (AIS-P) 2-119

Degraded Signal (DEG-P) 2-120

Degraded Signal (THPDEG) 2-121

Excessive Bit Error Ratio (EXC-P) 2-122

Excessive Bit Error Ratio (THPEXC) 2-124

Loss of Multiframe 2-126

Loss of Pointer (LOP-P) 2-128

Loss of Pointer (THPLOP) 2-129

Path Switch Denial 2-131

Payload Defect Indication 2-132

Payload Mismatch 2-134

Remote Defect Indication (RFI-P) 2-135

Remote Defect Indication (THPRDI) 2-137

Sequence Number Mismatch 2-138


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-7

Server Signal Fail (SSF-P) 2-140

Server Signal Fail (THPSSF) 2-141

Signal Rate Mismatch 2-142

Trace Identifier Mismatch (TIM-P) 2-144

Trace Identifier Mismatch (THPTIM) 2-145

Unequipped (UNEQ-P) 2-147

Unequipped (THPUNEQ) 2-149

Port-related transmission alarms 2-151

Alarm Indication Signal (AIS-L) 2-152

Backw Defect Transparent Ch 2-154

Degraded Signal (MSDEG) 2-155

Excessive Bit Error Ratio (MSEXC) 2-157

LOF Transparent Ch 2-159

Loss of Frame 2-160

Loss of Frame transp ch egress 2-162

Loss of Multiframe Transparent Ch 2-163

Loss of Signal 2-164

OCh Loss of Frame 2-166

Payload Mismatch Transparent Ch 2-167

Post DCM Signal Loss 2-168

Pre DCM Signal Loss 2-170

Remote Defect Indication (RFI-L) 2-172

Server Signal Fail (MSSSF) 2-173

Server Signal Fail Transparent Ch 2-174

Trace Identifier Mismatch (RSTIM) 2-175

Trace Identifier Mismatch egress (TIM-T-EGR) 2-176

WTU3 Loss of Frame 2-177

Ring protection switching alarms 2-178

Default K-bytes 2-179

Duplicate Ring Node 2-181

Extra Traffic Preempted 2-183

Improper APS Codes 2-184


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Inconsistent APS Codes 2-186

Inconsistent Ring Protection Mode 2-188

Local Squelch Map Conflict 2-189

Node ID Mismatch 2-191

Open Ring 2-192

Ring Discovery in Progress 2-193

Ring Incomplete 2-195

Ring Protection Switch Suspended 2-197

Traffic Squelched 2-198

Unknown Ring Type 2-202

Synchronisation alarms 2-203

Circuit Pack Clock Failure 2-204

Loss of Synchronisation 2-205

NE Clock Failure 2-206

Protection Clock Input Fail 2-207

T4 quality unsufficient 2-208

Timing Reference Failure 2-209

Worker Clock Input Fail 2-210

Additional alarm-related information 2-211

BLSR/MS-SPRing management information 2-212

Automatic discovery of the ring topology 2-215

Automatic node ID allocation 2-219

Automatic discovery of the ring type 2-220


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-9

DCN alarms

Overview.................................................................................................................................................................................................................................

Purpose

In the following, alarm descriptions are given for the alarms related to the DataCommunication Network (DCN), that can be reported by the LambdaUnite® MSSnetwork elements.

The DCN includes the Management Communication Network (MCN) and theSignalling Communication Network (SCN):

• The MCN is the network for the exchange of management information between themanagers and the managed NE’s. For historical reasons, the term “DCN” is oftenused synonymously to the term “MCN”.

• The SCN is the network that the Optical Network Navigation System (ONNS) usesfor the exchange of its control messages between the NE’s.

Related information

For MCN and SCN related information, please refer to the LambdaUnite® MSS UserOperations Guide.

Contents

Address List Overflow 2-11

ASTN Neighbor Not Available 2-12

DCC MS/Line failure 2-13

DCC RS/Section failure 2-14

DCN Provisioning Not Valid 2-15

Partitioned Area Repair 2-16

Protocol Version Mismatch 2-18

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Address List Overflow.................................................................................................................................................................................................................................

Meaning of the alarm

One or more computed area addresses have been dropped, because the maximumcapacity of the computed area address list is exceeded.

Brief alarm overview

The following tabular overview summarizes important information concerning theAddress List Overflow alarm:

Alarm identifier ADDROV

ASAP type Data Communications Network

Alarm category Communication (DCN)

Effect-on-service Not service-affecting (NSA)


Major

Alarm source DCN

Related information

Please refer to “General alarm information” (p. 2-2) for a description of the meaning ofthe entries in this brief alarm overview.

Local indications

There are no specific local indications.

Related information

Please also refer to the LambdaUnite® MSS User Operations Guide.

Trouble clearing

For technical support please refer to Appendix A, “Maintenance services and technicalsupport”.

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-11

ASTN Neighbor Not Available.................................................................................................................................................................................................................................


The SCN communication channel to the ONNS neighbor node indicated in the alarmmessage is not available. The IP address of the affected ONNS neighbor node isincluded in the alarm message.


The following tabular overview summarizes important information concerning the ASTN

Neighbor Not Available alarm:

Alarm identifier ASTNNBRNAV


Alarm category Communication (SCN)



Major

Alarm source SCN

Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

DCC MS/Line failure.................................................................................................................................................................................................................................


No connection could be established on an enabled DCC link provisioned for theAcknowledged Information Transfer Service (AITS).


The following tabular overview summarizes important information concerning the DCC

MS/Line failure alarm:

Alarm identifier DCCMSF

ASAP type SDH/SONET ports

Alarm category Communication (Transport)



SA – (not applicable)

NSA Major

Alarm source DCC

Notes:

1. The effect-on-service attribute of the DCC MS/Line failure alarm is always notservice-affecting (NSA). Nevertheless, the SA alarm severity is listed for the sake ofcompleteness because the alarm is part of the “SDH/SONET ports” ASAP which isservice-dependent.

Related information


Local indications

The red fault LED on the faceplate of the circuit pack where the respective port residesis flashing.

Related information


Trouble clearing

Please refer to “Clearing DCC MS/Line failure” (p. 3-6).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-13

DCC RS/Section failure.................................................................................................................................................................................................................................


No connection could be established on an enabled RS/Section DCC link provisionedfor the Acknowledged Information Transfer Service (AITS).


The following tabular overview summarizes important information concerning the DCC

RS/Section failure alarm:

Alarm identifier DCCRSF






NSA Major

Alarm source DCC

Notes:

1. The effect-on-service attribute of the DCC RS/Section failure alarm is always notservice-affecting (NSA). Nevertheless, the SA alarm severity is listed for the sake ofcompleteness because the alarm is part of the “SDH/SONET ports” ASAP which isservice-dependent.

Related information


Local indications


Related information


Trouble clearing

Please refer to “Clearing DCC RS/Section failure” (p. 3-11).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

DCN Provisioning Not Valid.................................................................................................................................................................................................................................

Not supported!

Although the DCN Provisioning Not Valid alarm is part of the “Data CommunicationsNetwork” ASAP, it has no relevance for the present LambdaUnite® MSS releasebecause the detection of the alarm is currently not supported. The alarm is prepared forfuture applications.

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-15

Partitioned Area Repair.................................................................................................................................................................................................................................


A partition repair path (“partition repair tunnel”) has been established in order to repaira partitioned area using connections via nodes outside the area.

The Partitioned Area Repair alarm is reported by the end nodes of a partitionrepair tunnel.

Important! Do not start a software upgrade of network elements or a softwaredownload, while a partition repair is active in the destination area.


The following tabular overview summarizes important information concerning thePartitioned Area Repair alarm:

Alarm identifier PARARREP





Minor

Alarm source DCN

Related information


Local indications


Partition repair

Partition repair provides a way to enhance the robustness of the DCN by providing thecapability to repair intra-area routing using connections via nodes outside the area. Thisis done by creating a path through the level-2 subdomain outside the area, between twolevel-2 nodes (which must be provisioned to be partition repair capable level-2 nodes),belonging to distinct partitions of the same IS-IS area. Level-1 IS-IS/CLNP PDU’s areencapsulated and transferred over that path. This is also referred to as tunnelling.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Related information


Trouble clearing

Important! When a Partitioned Area Repair alarm is present, it should becleared soon, so that the network does not suffer from degraded networkperformance or robustness.

Please refer to “Clearing Partitioned Area Repair ” (p. 3-8).

Alarm messages Partitioned Area Repair

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-17

Protocol Version Mismatch.................................................................................................................................................................................................................................


The automatic exchange of link ID information between two adjacent end nodes of anenabled DCC link (RS/Section DCC or MS/Line DCC) is not possible because theversion numbers of their link ID protocols or the protocol types or version numbers oftheir network address protocols are incompatible.

Whether an RS/Section DCC or an MS/Line DCC is affected, can be seen from thealarm identifier.


The following tabular overview summarizes important information concerning theProtocol Version Mismatch alarm:

Alarm identifier LIDRSM if an RS/Section DCC is affected,

LIDMSM if an MS/Line DCC is affected.






NSA Major

Alarm source Optical interface port

Notes:

1. The effect-on-service attribute of the Protocol Version Mismatch alarm is alwaysnot service-affecting (NSA). Nevertheless, the SA alarm severity is listed for the sake ofcompleteness because the alarm is part of the “SDH/SONET ports” ASAP which isservice-dependent.

Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Effect on protection switching

BLSR/MS-SPRing ring interworking, and thus ring protection switching is not possiblebetween the concerning network elements.

Automatic exchange of link ID information

LambdaUnite® MSS network elements autonomously exchange link identification (linkID) information via the so-called “link ID protocol” between two adjacent end nodesof enabled DCC links.

The link ID information is discovered upon initial link start-up and upon dynamicchanges to the link ID information. The network elements determine bidirectionalconnectivity with their neighbours via the LAPD datalink service and determine thelink ID information of the neighbour via a message exchange over that LAPD datalinkservice. The link ID information is used as an additional means to automatically andunambiguously discover the BLSR/MS-SPRing topology (please also refer to“Automatic discovery of the ring topology” (p. 2-215)).

The link ID information includes:

• Link ID protocol version numberThe version number specifies which version of the link ID protocol is running atthe end node. For LambdaUnite® MSS network elements only the version number“2” is supported.

• NE nameThe NE name, also referred to as the NE’s target identifier (TID), is analphanumeric string of up to 20 characters, used to uniquely identify a networkelement within the network.

• Port informationThe access identifier (AID) of the port where the DCC link is terminated.

• Network addressThe node’s NSAP address.The NSAP information is transported in the so-called “Network address protocol”which is nested in the link ID protocol. The NSAP address is used to set up an OSIassociation between adjacent ring nodes to support the distribution ofBLSR/MS-SPRing related information for the automatic discovery of ring topology,for the automatic allocation of the node IDs and for the distribution of crossconnection information in the ring.The network address information includes:

– Protocol type“OSI” for LambdaUnite® MSS network elements.

– Network address protocol version number, indicating the supported OSIpresentation context.“1” or “3” for LambdaUnite® MSS network elements.

Alarm messages Protocol Version Mismatch

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-19

– Length of the NSAP address

– Value of the NSAP address

Trouble clearing

Please refer to “Clearing Protocol Version Mismatch” (p. 3-9).

Alarm messages Protocol Version Mismatch

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

DS3 alarms

Overview.................................................................................................................................................................................................................................

Purpose

In the following, alarm descriptions are given for the alarms related to the transmissionof DS3 signals, that can be reported by the LambdaUnite® MSS network elements.

Contents

Degraded DS3 Line signal 2-22

DS3 AIS 2-23

DS3 AIS egress 2-24

DS3 Application Mismatch in 2-25

DS3 IDLE in 2-26

DS3 LOF egress 2-27

DS3 Loss of Frame 2-28

DS3 Loss of Signal 2-29

DS3 RAI egress 2-30

DS3 RAI in 2-32

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-21

Degraded DS3 Line signal.................................................................................................................................................................................................................................


The bit error ratio (BER) in the DS3 line has exceeded the provisioned SignalDegrade (BER) Threshold. The quality of the transmission signal is degraded.


The following tabular overview summarizes important information concerning theDegraded DS3 Line signal alarm:

Alarm identifier DS3LineDEG

ASAP type DS3 asynchronous ports


Effect-on-service Service-affecting (SA)


Major

Alarm source DS3 port

Related information


Local indications

The red fault LED on the faceplate of the EP51 port unit is flashing.

Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

DS3 AIS.................................................................................................................................................................................................................................


The DS3 path contains AIS.

The alarm is detected in the ingress direction (EP51 → XC).


The following tabular overview summarizes important information concerning the DS3

AIS alarm:

Alarm identifier DS3AIS





Major

Alarm source DS3 path

Related information


Local indications


Trouble clearing

Please refer to “Clearing DS3 AIS” (p. 3-14).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-23

DS3 AIS egress.................................................................................................................................................................................................................................


The DS3 path contains AIS.

The alarm is detected in the egress direction (XC → EP51).



AIS egress alarm:

Alarm identifier DS3AIS-EGR





Not reported


Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

DS3 Application Mismatch in.................................................................................................................................................................................................................................


The DS3 port is provisioned for the DS3 C-bit parity format, but actually a signal withthe DS3 M23 format is received.



Application Mismatch in alarm:

Alarm identifier DS3AIC





Major


Related information


Local indications


Trouble clearing

Please refer to “Clearing DS3 Application Mismatch in” (p. 3-16).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-25

DS3 IDLE in.................................................................................................................................................................................................................................


The respective DS3 signal is not in use, i.e. not cross-connected in the upstreamequipment.



IDLE in alarm:

Alarm identifier DS3IDLE





Major


Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

DS3 LOF egress.................................................................................................................................................................................................................................


Frame alignment to the DS3 signal is not possible.

The alarm is detected in the egress direction (XC → EP51), and is only applicablewhen the C-bit parity application or M23 application is provisioned.



LOF egress alarm:

Alarm identifier DS3LOF-EGR





Not reported


Related information


Local indications


Trouble clearing

Please refer to “Clearing DS3 LOF egress” (p. 3-17).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-27

DS3 Loss of Frame.................................................................................................................................................................................................................................


Frame alignment to the DS3 signal is not possible.

The alarm is detected in the ingress direction (EP51 → XC), and is only applicablewhen the C-bit parity application or M23 application is provisioned.



Loss of Frame alarm:

Alarm identifier DS3LOF





Major


Related information


Local indications


Trouble clearing

Please refer to “Clearing DS3 Loss of Frame” (p. 3-19).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

DS3 Loss of Signal.................................................................................................................................................................................................................................


The received DS3 signal contains too many consecutive zeros, or the signal level is toolow.



Loss of Signal alarm:

Alarm identifier DS3LOS





Major

Alarm source DS3 port

Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-29

DS3 RAI egress.................................................................................................................................................................................................................................


The Remote Alarm Indication (RAI) codeword contained in the Far End Alarm &Control (FEAC) channel indicates a far-end alarm.

The DS3 RAI egress alarm is detected in the egress direction (XC → EP51), and thecause of alarm can probably be found in the upstream DS3 path terminatingequipment.

C-bit parity application

For the C-bit parity application, a DS3 RAI egress alarm indicates one of thefollowing far-end alarms as signalled via the FEAC channel (cf. “Remote AlarmIndication (RAI) codeword” (p. 2-31)):

• A service-affecting DS3 equipment failure

• DS3 loss of signal

• DS3 loss of frame

• DS3 AIS received

M23 application

For the M23 application, a DS3 RAI egress alarm indicates one of the followingfar-end alarms as signalled via the FEAC channel (cf. “Remote Alarm Indication (RAI)codeword” (p. 2-31)):

• A DS3 severely errored frame (SEF)




RAI egress alarm:

Alarm identifier DS3RAI-EGR





Not reported


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Related information


Local indications


Remote Alarm Indication (RAI) codeword

The Far End Alarm & Control (FEAC) channel is realized by means of a repeating16-bit RAI codeword in the C3 byte of the M-subframe 1 (cf. ANSI T1.107):

Alarm / Status condition RAI codeword

Service-affecting DS3 equipment failure 00110010 11111111

DS3 LOS 00011100 11111111

DS3 Out-Of-Frame 00000000 11111111

DS3 AIS Received 00101100 11111111

DS3 IDLE Received 00110100 11111111

Not service-affecting DS3 equipment failure 00011110 11111111

Common equipment failure 00111010 11111111

Multiple DS1 LOS1 00101010 11111111

Service-affecting DS1 equipment failure1 00001010 11111111

Single DS1 LOS1 00111100 11111111

Not service-affecting DS1 equipment failure1 00000110 11111111

No alarm or status condition 11111111 11111111

Notes:

1. These codes are not assigned for unchannelized applications

Trouble clearing

Please refer to “Clearing DS3 RAI egress” (p. 3-20).

Alarm messages DS3 RAI egress

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-31

DS3 RAI in.................................................................................................................................................................................................................................


The Remote Alarm Indication (RAI) codeword contained in the Far End Alarm &Control (FEAC) channel indicates a far-end alarm.

The DS3 RAI in alarm is detected in the ingress direction (EP51 → XC), and thecause of alarm can probably be found in the Digital Distribution Frame (DDF) in thelocal office.

C-bit parity application

For the C-bit parity application, a DS3 RAI in alarm indicates one of the followingfar-end alarms as signalled via the FEAC channel (cf. “Remote Alarm Indication (RAI)codeword” (p. 2-31)):

• A service-affecting DS3 equipment failure

• DS3 loss of signal

• DS3 loss of frame


M23 application

For the M23 application, a DS3 RAI in alarm indicates one of the following far-endalarms as signalled via the FEAC channel (cf. “Remote Alarm Indication (RAI)codeword” (p. 2-31)):

• A DS3 severely errored frame (SEF)




RAI in alarm:

Alarm identifier DS3RAI





Major


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Related information


Local indications


Trouble clearing

Please refer to “Clearing DS3 RAI in” (p. 3-21).

Alarm messages DS3 RAI in

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-33

Environmental alarms

Overview.................................................................................................................................................................................................................................

Purpose

LambdaUnite® MSS systems feature a set of eight Miscellaneous Discrete Inputs foruser-defined applications. A Miscellaneous Discrete Input can be connected to monitora temperature probe or a fire alarm device for example. Miscellaneous Discrete Inputscan thus be used to trigger the reporting of application-specific environmental alarms.

Contents

Miscellaneous Discrete Input # (#=1 8) 2-35

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Miscellaneous Discrete Input # (#=1 8).................................................................................................................................................................................................................................


An environmental alarm condition has been detected by an external sensor connectedto the corresponding Miscellaneous Discrete Input.

Alarm message text

As the meaning of an environmental alarm depends on the specific application, thealarm message (Environment message) to be displayed in the WaveStar® CIT NEAlarm List is configurable. The default alarm messages are Miscellaneous Discrete

Input 1, Miscellaneous Discrete Input 2 Miscellaneous Discrete Input 8.



The following tabular overview summarizes important information concerning theMiscellaneous Discrete Input alarms:

Alarm identifier MISC_1, MISC_2, , MISC_8

ASAP type Environmental (Miscellaneous Discrete)

Alarm category Environment

Effect-on-service – (not applicable)


Not reported

(configurable individually for each of the eightenvironmental alarms)

Alarm source Miscellaneous Discrete Input 1, Miscellaneous DiscreteInput 2, Miscellaneous Discrete Input 8

Notes:

1. In the WaveStar® CIT NE Alarm List, “MISC” is displayed as the probable cause (alarmidentifier) of an environmental alarm. The information, which Miscellaneous DiscreteInput (MDI) has a pending alarm can be derived from the AID parameter (for example“misc_in4”), and of course from the configurable alarm message.

2. Environmental alarms have no effect-on-service attribute assigned because the actual useof the MDIs cannot be foreseen.

Related information


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-35

Local indications


Trouble clearing

The measures to be taken to locate and clear environmental alarms depend on thespecific application of the respective Miscellaneous Discrete Input.

Alarm messages Miscellaneous Discrete Input # (#=1 8)

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Equipment alarms

Overview.................................................................................................................................................................................................................................

Purpose

In the following, alarm descriptions are given for the equipment alarms that can bereported by the LambdaUnite® MSS network elements.

Contents

Abnormal condition 2-39

Backplane Read Failure 2-41

CICTL Comm Failure 2-42

CICTL Failure 2-43

CICTL not Present 2-44

CICTL Powered Down 2-45

Circuit Pack Comm Failure 2-46

Circuit Pack Failure 2-47

Circuit Pack not Present 2-48

Circuit Pack Type Mismatch 2-50

Comm Channel Failure 2-51

CTL Comm Failure 2-52

Duplex Control not Present 2-53

ECI Comm Failure 2-55

ECI Mismatch Failure 2-56

ECI not Present 2-57

Fan Failure 2-58

Fan Unit Comm Failure 2-59

Fan Unit Failure 2-60

Fan Unit not Present 2-61

Fan Voltage Feed A Failure 2-62

Fan Voltage Feed B Failure 2-63

IDE Flash Card Access Fail 2-64

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-37

NVM Shortage 2-65

ONI Failure on protecting CTL 2-66

ONI Failure on working CTL 2-68

Optical Module Fail 2-70

Optical Module not Present 2-72

Optical Module not supported 2-73

Optical Module Type Mismatch 2-74

Power Interface not Present 2-75

Power Interface Read Failure 2-76

System Power Failure 2-78

TI Mismatch 2-79

TI not Present 2-80

TXI Failure 2-81

Unit Cooling Degraded 2-83

Unit Temperature too High 2-84

User Panel Comm Failure 2-86

User Panel not Present 2-87


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Abnormal condition.................................................................................................................................................................................................................................


The control system has detected manually initiated maintenance activity that couldaffect service or potentially mask the reporting of service-affecting failures.

Abnormal conditions

These types of abnormal conditions exist:

• A forced switch is active (protection group)

• A lockout of protection is active (protection group)Please note that a lockout of protection of a 1+1 MSP optimized protection groupdoes not lead to an abnormal condition indication.

• The system operates in holdover mode (timing reference)

• The system operates in free-running mode (timing reference)

• A facility loopback is active (port)

• A cross-connection loopback is active (tributary)

• A test access session is active (tributary)

• The system operates in maintenance mode (system)


The following tabular overview summarizes important information concerning theAbnormal condition alarm:

Alarm identifier ABN

ASAP type Equipment unprotected

Alarm category Equipment

Effect-on-service – (not applicable)


Not alarmed

Alarm source System, protection group, timing reference, port, ortributary (depending on the type of abnormal condition)

Notes:

1. Abnormal conditions are events, and therefore have no effect-on-service attributeassigned.

2. The severity of an Abnormal condition alarm is not provisionable, it is always “Notalarmed”. Abnormal conditions are reported as events, and thus are signalled by means ofthe event status display of the WaveStar® CIT.

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-39

Related information


Local indications

The yellow “ABN” LED on the user panel is lit.

Trouble clearing

The Abnormal condition indication is to be understood as an information rather thanas an alarm, and it will be cleared automatically as soon as the abnormal condition isno longer existing.

Alarm messages Abnormal condition

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Backplane Read Failure.................................................................................................................................................................................................................................


The backplane EEPROM cannot be accessed by the Controller (CTL). Reading from orwriting to the EEPROM is not possible. This means that the EEPROM is either not ornot correctly partitioned, does not hold data, or that the hardware is defective.

The backplane EEPROM contains factory and application specific data and theelectronic type label.


The following tabular overview summarizes important information concerning theBackplane Read Failure alarm:

Alarm identifier BPEF





Major

Alarm source Shelf

Related information


Local indications


Trouble clearing

Please contact your Lucent Technologies Local Customer Support (LCS) team or theLucent Technologies Service Hotline.

Please refer to Appendix A, “Maintenance services and technical support”.

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-41

CICTL Comm Failure.................................................................................................................................................................................................................................


The CICTL Comm Failure alarm may have the following causes:

• The inventory EEPROM on the CI-CTL (Connection Interface of the Controller)cannot be accessed by the Controller (CTL).Reading from or writing to the EEPROM is not possible. This means that theEEPROM is either not or not correctly partitioned, does not hold data, or that thehardware is defective.

• The MDI/MDO status cannot be retrieved by the Controller (CTL).MDI/MDO status means whether an MDI or MDO port is on or off.

The internal communication between the CI-CTL (Connection Interface of theController) and the Controller (CTL) is disturbed.


The following tabular overview summarizes important information concerning theCICTL Comm Failure alarm:

Alarm identifier CICOMF





Minor

Alarm source CI-CTL

Related information


Local indications


Trouble clearing

Please refer to “Clearing CICTL Comm Failure” (p. 3-24).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

CICTL Failure.................................................................................................................................................................................................................................


The CI-CTL (connection interface of the Controller) has failed.

The CICTL Failure alarm may be caused by a power failure on the CI-CTL or afailure of the CI-CTL local clock.


The following tabular overview summarizes important information concerning theCICTL Failure alarm:

Alarm identifier CIF





Minor

Alarm source Slot

Related information


Local indications


Trouble clearing

Please refer to “Clearing CICTL Failure” (p. 3-28).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-43

CICTL not Present.................................................................................................................................................................................................................................


The CI-CTL (Connection Interface of the Controller) cannot be detected by theController (CTL). Either there is no CI-CTL plugged in slot 51 on the rear side of theshelf, or the CTL is defective.


The following tabular overview summarizes important information concerning theCICTL not Present alarm:

Alarm identifier CIMISS





Minor

Alarm source Slot

Related information


Local indications


Trouble clearing

Please refer to “Clearing CICTL not Present” (p. 3-29).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

CICTL Powered Down.................................................................................................................................................................................................................................


The power supply for the CI-CTL (connection interface of the Controller) has beenswitched off by the Controller (CTL).


The following tabular overview summarizes important information concerning theCICTL Powered Down alarm:

Alarm identifier CIPWRDWN





Minor

Alarm source Slot

Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-45

Circuit Pack Comm Failure.................................................................................................................................................................................................................................


A protocol failure occurred in the internal data communication between a port unit, thecross-connect and timing unit (XC), and the Controller (CTL).


The following tabular overview summarizes important information concerning theCircuit Pack Comm Failure alarm:

Alarm identifier CPCOMF





Minor

Alarm source Circuit pack

Related information


Local indications


Trouble clearing

Please refer to “Clearing Circuit Pack Comm Failure” (p. 3-30).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Circuit Pack Failure.................................................................................................................................................................................................................................


One of the following failure conditions exists on the circuit pack for which the alarmis reported:

• An error occurred during the initialization of the circuit pack.

• There is a hardware error on the circuit pack.

• One of the local circuit pack voltages is out of range.

In the case of a cross-connect and timing unit (XC160, XC320), the Circuit Pack

Failure alarm may also indicate a failure of the system timing function.


The following tabular overview summarizes important information concerning theCircuit Pack Failure alarm:

Alarm identifier CPFAIL

ASAP type Equipment with Protection State Dependence


Effect-on-service Service-affecting (SA) if transmission on a path ispotentially affected. Not service-affecting (NSA)otherwise.


Depending on the effect-on-service:

SA Critical

NSA Minor


Related information


Local indications

The red fault LED on the faceplate of the respective circuit pack is constantly lit.

Trouble clearing

Please refer to “Clearing Circuit Pack Failure ” (p. 3-49).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-47

Circuit Pack not Present.................................................................................................................................................................................................................................


Although previously provisioned, no circuit pack can be detected by the Controller(CTL) in the slot for which the Circuit Pack not Present alarm is reported. Eitherthere is no circuit pack installed in the corresponding slot, the function controller onthe affected circuit pack is defective, or the CTL is defective.


The following tabular overview summarizes important information concerning theCircuit Pack not Present alarm:

Alarm identifier REPLUNITMISS






SA Critical

NSA Minor

Alarm source Slot

Related information


Local indications

Local indications via the red fault LED of the missing circuit pack are of course notpossible.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

However, please be aware of the following special situations that may occur:

• In the case of a missing cross-connect and timing unit, the red fault LEDs on allcircuit packs will be flashing because of a Worker Clock Input Fail orProtection Clock Input Fail defect being present. However there will be nocorresponding alarm, because the Worker Clock Input Fail or ProtectionClock Input Fail alarm will be suppressed due to the existence of the CircuitPack not Present alarm of the cross-connect and timing unit. Either a CircuitPack not Present alarm (for the cross-connect and timing unit) or no alarm at allwill be reported depending on whether the missing cross-connect and timing unitremains provisioned or is deprovisioned.

• In the case of a missing port unit (OP variants or GE1 circuit pack), the red faultLEDs on the cross-connect and timing units will be flashing due to the detectedTXI Failure condition but no TXI Failure alarm will be reported because it ismasked by the Circuit Pack not Present alarm (for the missing port unit).

Missing Controller

In the case of a missing Controller (CTL), no Circuit Pack not Present alarm willbe reported because no autonomous alarm notification can be generated. However, thered Critical (CR) alarm LEDs on the user panel and on the rack alarm facility will belit.

Trouble clearing

Please refer to “Clearing Circuit Pack not Present” (p. 3-46).

Alarm messages Circuit Pack not Present

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-49

Circuit Pack Type Mismatch.................................................................................................................................................................................................................................


There is an unexpected circuit pack present in the slot for which the Circuit Pack

Type Mismatch alarm is reported.

The Circuit Pack Type Mismatch alarm may have one of the folowing causes:

1. Although the circuit pack is in principle permitted for that slot, a different type ofcircuit pack had previously been provisioned.

2. The current shelf equipage is not permitted. The configuration rules which resultfrom the provisioned maximum switching capacity of the system are violated.Please also refer to “Configuration rules” (p. 4-66).


The following tabular overview summarizes important information concerning theCircuit Pack Type Mismatch alarm:

Alarm identifier PRCDRERR






SA Major

NSA Minor

Alarm source Slot

Related information


Local indications


Trouble clearing

Please refer to “Clearing Circuit Pack Type Mismatch” (p. 3-47).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Comm Channel Failure.................................................................................................................................................................................................................................


A protocol failure occurred in the internal data communication between one or twocross-connect and timing units and the active Controller (CTL).


The following tabular overview summarizes important information concerning the Comm

Channel Failure alarm:

Alarm identifier SYSCOMF





Major


Related information


Local indications

The red fault LED on the faceplate of the respective circuit pack is flashing.

Trouble clearing

Please refer to “Clearing Comm Channel Failure ” (p. 3-50).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-51

CTL Comm Failure.................................................................................................................................................................................................................................


The CTL Comm Failure alarm may have different causes:

• The inventory data of the Controller (CTL) cannot be accessed, or

• one of the internal selftests failed, or

• the ONI communication between the DCC controller function and the systemcontroller function (both are realized on the CTL) is disturbed.


The following tabular overview summarizes important information concerning the CTL

Comm Failure alarm:

Alarm identifier CTLCOMF





Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing CTL Comm Failure ” (p. 3-58).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Duplex Control not Present.................................................................................................................................................................................................................................


The active Controller cannot be protected by a standby Controller because

• there is no second Controller installed, or

• the hardware versions of the two Controllers do not match.

A typical cause of a Duplex Control not Present alarm is a duplex controlconfiguration where the active Controller is a CTL/2, and the standby Controller is aCTL/-. As the CTL/2 supports an extended functionality in comparison with the CTL/-,a CTL/2 may protect a CTL but not vice versa.

Related information

Please also refer to the equipment provisioning concepts described in theLambdaUnite® MSS User Operations Guide.


The following tabular overview summarizes important information concerning theDuplex Control not Present alarm:

Alarm identifier DCTLUNAVAIL






NSA Not reported

Alarm source System

Notes:

1. The effect-on-service attribute of the Duplex Control not Present alarm is alwaysnot service-affecting (NSA). Nevertheless, the SA alarm severity is listed for the sake ofcompleteness because the alarm is part of the “Equipment with Protection StateDependence” ASAP which is service-dependent.

Related information


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-53

Local indications


Trouble clearing

Please refer to “Clearing Duplex Control not Present” (p. 3-60).

Alarm messages Duplex Control not Present

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

ECI Comm Failure.................................................................................................................................................................................................................................


The ECI Comm Failure alarm may have different causes:

• The internal communication between the corresponding Electrical ConnectorInterface (ECI) and the Controller (CTL) is disturbed, or

• two EP155 circuit packs are present in the slots assosciated to the ECI, and thecontent of their EPROMs is inconsistent.


The following tabular overview summarizes important information concerning the ECI

Comm Failure alarm:

Alarm identifier ECICOMF





Minor

Alarm source ECI slot

Related information


Local indications


Trouble clearing

Please refer to “Clearing ECI Comm Failure” (p. 3-61).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-55

ECI Mismatch Failure.................................................................................................................................................................................................................................


The type of Electrical Connector Interface (ECI) used is not suitable for the currentconfiguration.

Related information

Please also refer to the equipment provisioning concepts described in theLambdaUnite® MSS User Operations Guide.



Mismatch Failure alarm:

Alarm identifier ECIMISMA





Critical


Related information


Local indications


Trouble clearing

Please refer to “Clearing ECI Mismatch Failure” (p. 3-65).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

ECI not Present.................................................................................................................................................................................................................................


The corresponding Electrical Connector Interface (ECI) is missing.



not Present alarm:

Alarm identifier ECIMISS





Critical


Related information


Local indications


Trouble clearing

Please refer to “Clearing ECI not Present” (p. 3-68).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-57

Fan Failure.................................................................................................................................................................................................................................


One or more fans have failed.


The following tabular overview summarizes important information concerning the Fan

Failure alarm:

Alarm identifier FANF





Major

Alarm source Fan unit

Related information


Local indications

The red fault LED on the faceplate of the fan unit is constantly lit.

Trouble clearing

Please refer to “Clearing Fan Failure ” (p. 3-69).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Fan Unit Comm Failure.................................................................................................................................................................................................................................


A failure occurred in the internal communication between the fan unit, the CI-CTL(Connection Interface of the Controller) and the Controller (CTL), or no fan unit isinstalled .



Unit Comm Failure alarm:

Alarm identifier FANUNITCOMF





Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Fan Unit Comm Failure” (p. 3-72).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-59

Fan Unit Failure.................................................................................................................................................................................................................................


The fan unit has no power supply.



Unit Failure alarm:

Alarm identifier FANUNITF





Critical


Related information


Local indications

Both LEDs on the fan unit faceplate are off.

Trouble clearing

Please refer to “Clearing Fan Unit Failure” (p. 3-76).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Fan Unit not Present.................................................................................................................................................................................................................................


The fan unit is not installed in the shelf.



Unit not Present alarm:

Alarm identifier FANUNITMISS





Critical

Alarm source Shelf

Related information


Local indications


Trouble clearing

Important! A Fan Unit not Present alarm should be cleared as soon as possible.

Please refer to “Clearing Fan Unit not Present” (p. 3-80).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-61

Fan Voltage Feed A Failure.................................................................................................................................................................................................................................


There is no voltage supply at the “Power Input A” of the fan unit, or the voltage is toolow.



Voltage Feed A Failure alarm:

Alarm identifier FEEDAF





Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Fan Voltage Feed A/B Failure ” (p. 3-82).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Fan Voltage Feed B Failure.................................................................................................................................................................................................................................


There is no voltage supply at the “Power Input B” of the fan unit, or the voltage is toolow.



Voltage Feed B Failure alarm:

Alarm identifier FEEDBF





Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Fan Voltage Feed A/B Failure ” (p. 3-82).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-63

IDE Flash Card Access Fail.................................................................................................................................................................................................................................


Reading or writing from/to the system’s non-volatile memory (NVM,CompactFlash®card with IDE interface) is not possible.


The following tabular overview summarizes important information concerning the IDE

Flash Card Access Fail alarm:

Alarm identifier BKUPMEMP







NSA Major

Alarm source Controller (CTL)

Notes:

1. The effect-on-service attribute of the IDE Flash Card Access Fail alarm is alwaysnot service-affecting (NSA). Nevertheless, the SA alarm severity is listed for the sake ofcompleteness because the alarm is part of the “Equipment with Protection StateDependence” ASAP which is service-dependent.

Related information


Local indications

The red fault LED on the faceplate of the Controller (CTL) is constantly lit.

Trouble clearing

Important! Refer to the following trouble clearing procedure even if the IDE

Flash Card Access Fail alarm was reported only for a short period of time, andhas cleared in the meantime.

Please refer to “Clearing IDE Flash Card Access Fail” (p. 3-87).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

NVM Shortage.................................................................................................................................................................................................................................


The capacity of the system’s non-volatile memory (NVM, CompactFlash® card withIDE interface) is nearly exhausted.

The required size of the CompactFlash® card depends on the Controller used:

CTL/- 256 MByte

CTL/2 512 MByte

CTL/3T or CTL/3S 1 GByte


The following tabular overview summarizes important information concerning the NVM

Shortage alarm:

Alarm identifier BKUPMEMO


Alarm category Equipment (Processing error)



Minor

Alarm source Controller (CTL)

Related information


Local indications

The red fault LED on the faceplate of the Controller (CTL) is constantly lit.

Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-65

ONI Failure on protecting CTL.................................................................................................................................................................................................................................


The internal communication between circuit packs via their Operations NetworkInterface (ONI) failed. This may have an impact on the overhead informationcommunicated between circuit packs.

The actual alarm text displayed in the WaveStar® CIT NE Alarm List is: “circuitpack name/circuit pack qualifier,ONI Failure on protecting CTL”. Thealarm has been detected by the standby Controller (protecting CTL), and is reported forthe circuit pack indicated in the alarm message (“circuit pack name/circuit packqualifier”).


The following tabular overview summarizes important information concerning the ONI

Failure on protecting CTL alarm:

Alarm identifier ONIFP







NSA Minor


Notes:

1. The effect-on-service attribute of the ONI Failure on protecting CTL alarm isalways not service-affecting (NSA). Nevertheless, the SA alarm severity is listed for thesake of completeness because the alarm is part of the “Equipment with Protection StateDependence” ASAP which is service-dependent.

Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing

Please refer to “Clearing ONI Failure on protecting CTL” (p. 3-90).

Alarm messages ONI Failure on protecting CTL

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-67

ONI Failure on working CTL.................................................................................................................................................................................................................................


The internal communication between circuit packs via their Operations NetworkInterface (ONI) failed. This may have an impact on the overhead informationcommunicated between circuit packs.

The actual alarm text displayed in the WaveStar® CIT NE Alarm List is: “circuitpack name/circuit pack qualifier,ONI Failure on working CTL”. Thealarm has been detected by the active Controller (working CTL), and is reported forthe circuit pack indicated in the alarm message (“circuit pack name/circuit packqualifier”).


The following tabular overview summarizes important information concerning the ONI

Failure on working CTL alarm:

Alarm identifier ONIFW







NSA Minor


Notes:

1. The effect-on-service attribute of the ONI Failure on working CTL alarm is alwaysnot service-affecting (NSA). Nevertheless, the SA alarm severity is listed for the sake ofcompleteness because the alarm is part of the “Equipment with Protection StateDependence” ASAP which is service-dependent.

Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing

Please refer to “Clearing ONI Failure on working CTL” (p. 3-93).

Alarm messages ONI Failure on working CTL

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-69

Optical Module Fail.................................................................................................................................................................................................................................


The optical module is defective.

This may have one of the following reasons:

• The laser is defective.

• The EEPROM of the optical module cannot be accessed.

Hot plug-in of an optical module

Additionally, an Optical Module Fail alarm is likely to be reported temporarilywhen a pluggable optical module with a cooled laser transmitter (e.g. an opticalmodule of type OM10G6 or OM10G14) is inserted into a parent board duringoperation (″hot plug-in″). Initially, the transmitter is on the wrong temperature level,and thus not operating under its nominal conditions. While the transmitter needs sometime to reach its nominal operating temperature, all other functions of the board arefully operational. The Optical Module Fail alarm will disappear after 60 seconds atthe latest when the laser transmitter has reached its nominal operating temperature.


The following tabular overview summarizes important information concerning theOptical Module Fail alarm:

Alarm identifier OMFAIL






SA Critical

NSA Minor

Alarm source OM socket

Related information


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Local indications

The red port LED associated to the pluggable optical interface is constantly lit.

Trouble clearing

Please refer to “Clearing Optical Module Fail” (p. 3-96).

Alarm messages Optical Module Fail

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-71

Optical Module not Present.................................................................................................................................................................................................................................


Although previously provisioned, there is no optical module installed in thecorresponding OM socket.


The following tabular overview summarizes important information concerning theOptical Module not Present alarm:

Alarm identifier OMMISS






SA Critical

NSA Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Optical Module not Present” (p. 3-97).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Optical Module not supported.................................................................................................................................................................................................................................


The optical interface module in the respective OM socket is not suitable for the use ina LambdaUnite® MSS system.

Important! Only for the LambdaUnite® MSS certified SFPs, Lucent Technologiescan guarantee the full functionality and warranty.


The following tabular overview summarizes important information concerning theOptical Module not supported alarm:

Alarm identifier OMUNSUP






SA Critical

NSA Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Optical Module not supported” (p. 3-98).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-73

Optical Module Type Mismatch.................................................................................................................................................................................................................................


The currently installed optical interface module does not match the provisioned opticalmodule type, or it is not suitable for the parent board (the latter applies in case ofautoprovisioning).


The following tabular overview summarizes important information concerning theOptical Module Type Mismatch alarm:

Alarm identifier OMMISMA






SA Critical

NSA Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Optical Module Type Mismatch” (p. 3-99).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Power Interface not Present.................................................................................................................................................................................................................................


The Power Interface (PI) is not installed.


The following tabular overview summarizes important information concerning thePower Interface not Present alarm:

Alarm identifier PIMISS



Effect-on-service Not service-affecting (NSA); see the table note.



SA Major

NSA Minor

Alarm source Power Interface (PI A, PI B)

Notes:

1. A Power Interface not Present alarm condition is classified service-affecting (SA)if no PI is installed. However, please be aware that such a situation can never be alarmedbecause in that case the system would have no power supply. The alarm can only bereported as not service-affecting (NSA).

Related information


Local indications


Trouble clearing

Please refer to “Clearing Power Interface not Present” (p. 3-100).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-75

Power Interface Read Failure.................................................................................................................................................................................................................................


The inventory EEPROM on the affected Power Interface (PI A or PI B) cannot beaccessed by the Controller (CTL).

Reading from or writing to the EEPROM is not possible. This means that theEEPROM is either not or not correctly partitioned, does not hold data, or that thehardware is defective.

Please note that the presence and the absence (after trouble clearing) of the Power

Interface Read Failure alarm can only be detected if the inventory EEPROM isaccessed (for example by manually retrieving the equipment parameters of a PowerInterface).


The following tabular overview summarizes important information concerning thePower Interface Read Failure alarm:

Alarm identifier PIEF







NSA Minor


Notes:

1. The effect-on-service attribute of the Power Interface Read Failure alarm isalways not service-affecting (NSA). Nevertheless, the SA alarm severity is listed for thesake of completeness because the alarm is part of the “Equipment with Protection StateDependence” ASAP which is service-dependent.

Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing

Please refer to “Clearing Power Interface Read Failure” (p. 3-101).

Alarm messages Power Interface Read Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-77

System Power Failure.................................................................................................................................................................................................................................


The supply voltage of one of the two input power feeders has dropped below 39 V DC(–39.0 ± 1.0 V DC). The second supply voltage is within the nominal range.

Which system power feeder is affected can be seen from the Power Interface AID(“1-1-pia” or “1-1-pib”) indicated in the AID column of the WaveStar® CIT NE AlarmList, or from the green “PWR ON” LED on the respective Power Interface PI A or PIB (cf. “Local indications”).


The following tabular overview summarizes important information concerning theSystem Power Failure alarm:

Alarm identifier POWF



Effect-on-service Not service-affecting (NSA); see the table note.



SA Major

NSA Minor


Notes:

1. A System Power Failure is service-affecting (SA) if the supply voltages of bothpower feeders have dropped below the nominal range. However, please be aware thatsuch a situation can never be alarmed because in that case the system would have nopower supply. The alarm can only be reported as not service-affecting (NSA).

Related information


Trouble clearing

Please refer to “Clearing System Power Failure” (p. 3-102).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

TI Mismatch.................................................................................................................................................................................................................................


A second Timing Interface (TI) has been inserted into the system, and the type of thissecond TI does not match the type of the already plugged-in TI.


The following tabular overview summarizes important information concerning the TI

Mismatch alarm:

Alarm identifier TIMM





Minor

Alarm source Timing Interface

Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-79

TI not Present.................................................................................................................................................................................................................................


The respective Timing Interface (TI) is not installed.


The following tabular overview summarizes important information concerning the TI

not Present alarm:

Alarm identifier TIMISS





Minor

Alarm source Timing Interface (TI)

Related information


Local indications


Trouble clearing

Please refer to “Clearing TI not Present” (p. 3-105).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

TXI Failure.................................................................................................................................................................................................................................


Frame alignment has been lost for the TXI bus line “n” as indicated by the alarmidentifier.

The TXI Failure alarm is reported by the circuit pack receiving a signal on thecorresponding TXI bus line.

Please also refer to “TXI bus line numbering scheme” (p. 4-111).


The following tabular overview summarizes important information concerning the TXI

Failure alarm:

Alarm identifier TXInF (where “n” is a number representing the affectedTXI bus line)






SA Critical

NSA Minor


Notes:

1. The maximum of n depends on the card type. The alarm identifier will be reported as:TXI1F, TXI2F, TXI3F ...

Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-81

Trouble clearing

Please refer to “Clearing TXI Failure” (p. 3-106).

Alarm messages TXI Failure

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Unit Cooling Degraded.................................................................................................................................................................................................................................


The operating temperature of the circuit pack reporting the alarm has exceeded apredefined limit.


The following tabular overview summarizes important information concerning the Unit

Cooling Degraded alarm:

Alarm identifier CPDEGR





Minor


Related information


Local indications


Trouble clearing

Important! A Unit Cooling Degraded alarm is the predecessor of a more severealarm condition (Unit Temperature too High). Therefore, it is recommended toimmediately react on a Unit Cooling Degraded alarm in order to prevent a moresevere situation.

Please refer to “Clearing Unit Cooling Degraded” (p. 3-109).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-83

Unit Temperature too High.................................................................................................................................................................................................................................


The operating temperature of the circuit pack reporting the alarm has exceeded themaximum permitted value.


The following tabular overview summarizes important information concerning the Unit

Temperature too High alarm:

Alarm identifier CPTEMP






SA Major

NSA Minor


Notes:

1. Please note that for unprotected and MS-layer protected applications the UnitTemperature too High alarm will always be reported “not service-affecting” (NSA)and “Minor”. The service state calculation will never lead to “service-affecting” (SA) and“Major”. In a 1+1 equipment protection application, the service state calculation is donecorrectly.

Related information


Local indications



Unit Temperature too High is a trigger for equipment protection switching.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing

Please refer to “Clearing Unit Temperature too High” (p. 3-112).

Alarm messages Unit Temperature too High

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-85

User Panel Comm Failure.................................................................................................................................................................................................................................


A failure occurred in the internal communication between the user panel and theController (CTL).


The following tabular overview summarizes important information concerning the User

Panel Comm Failure alarm:

Alarm identifier UPCOMF





Minor

Alarm source User panel

Related information


Trouble clearing

Please refer to “Clearing User Panel Comm Failure” (p. 3-115).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

User Panel not Present.................................................................................................................................................................................................................................


The user panel is not installed.


The following tabular overview summarizes important information concerning the User

Panel not Present alarm:

Alarm identifier UPMISS





Minor

Alarm source Shelf

Related information


Local indications


Trouble clearing

Please refer to “Clearing User Panel not Present” (p. 3-119).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-87

Ethernet alarms

Overview.................................................................................................................................................................................................................................

Purpose

In the following, alarm descriptions are given for the alarms related to theLambdaUnite® MSS Gigabit Ethernet functionality.

Contents

GFP Loss of Frame 2-89

LAN Auto Negotiation Mismatch 2-90

Loss of Alignment 2-92

LAN Loss of Signal 2-94

max number of VLAN instances reached 2-95

Partial Transport Capacity Loss 2-97

Server Signal Fail (VCGSSF) 2-98

Sink End Failure of Protocol 2-99

Source End Failure of Protocol 2-100

Total Transport Capacity Loss 2-101

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

GFP Loss of Frame.................................................................................................................................................................................................................................


The GFP delineation algorithm failed to recover the framestart of a GFP frame.


The following tabular overview summarizes important information concerning the GFP


Alarm identifier GFPLOF

ASAP type Ethernet





SA Critical

NSA Minor

Alarm source Virtual Concatenated Group (VCG)

Related information


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-89

LAN Auto Negotiation Mismatch.................................................................................................................................................................................................................................


The priority resolution mechanism precluded operation between the two end nodes ofan Ethernet link because there is no common mode of operation. For example, one endnode is configured to operate in full duplex mode whereas the other end node isconfigured to operate in half duplex mode.


The following tabular overview summarizes important information concerning the LAN

Auto Negotiation Mismatch alarm:

Alarm identifier LANANM

ASAP type Ethernet





SA Minor

NSA Not alarmed

Alarm source Gigabit Ethernet port

Related information


Local indications

The red fault LED on the faceplate of the Gigabit Ethernet port unit is flashing.

Auto negotiation

Auto negotiation means that both end nodes of an Ethernet link exchange informationamong each other concerning their possible modes of operation. If a common mode ofoperation exists then the mode with the highest priority acc. to the priority resolutionmechanism will be selected.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing


Alarm messages LAN Auto Negotiation Mismatch

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-91

Loss of Alignment.................................................................................................................................................................................................................................


The virtually concatenated payload cannot be aligned to a common multiframe startbecause the delay difference between the VC-4s/STS-1s in the Virtual ConcatenatedGroup (VCG) exceeds the range that can be compensated by buffering.

The received data is corrupted.


The following tabular overview summarizes important information concerning the Loss

of Alignment alarm:

Alarm identifier VCGLOA

ASAP type Ethernet





SA Critical

NSA Minor


Related information


Local indications


Payload realignment

The different VC-4s/STS-1s of a Virtual Concatenated Group (VCG) in general havedifferent transit times when transmitted over the network. These differences have to becompensated in a realignment process by buffering the “fastest” and all subsequentVC-4s/STS-1s until the “slowest” VC-4/STS-1 has arrived. The sequence number andthe multiframe information are used to realign the virtually concatenated payload

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

provided that no Sequence Number Mismatch or Loss of Multiframe alarm ispresent.

Compensation of delay is only possible in a relatively small region called the“correction range”. For LambdaUnite® MSS systems, the correction range is 32 ms.

As soon as the delay difference between the fastest and the slowest VC-4/STS-1 islarger than the correction range, realignment is no longer possible and a Loss of

Alignment alarm will be reported. Such a delay difference can only be caused bytributaries routed over extremely different paths (different in length, and/or concerningthe number of network elements in the path).

Trouble clearing

Please refer to “Clearing Loss of Alignment” (p. 3-121).

Alarm messages Loss of Alignment

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-93

LAN Loss of Signal.................................................................................................................................................................................................................................


The receiver of the corresponding Gigabit Ethernet port has detected no optical inputsignal for more than one second or is not able to synchronize to the incoming signal.


The following tabular overview summarizes important information concerning the LAN

Loss of Signal alarm:

Alarm identifier LANLOS

ASAP type Ethernet





SA Critical

NSA Minor

Alarm source Gigabit Ethernet port

Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

max number of VLAN instances reached.................................................................................................................................................................................................................................


The GARP VLAN Registration Protocol (GVRP) is enabled, and the maximum numberof VLAN instances per virtual switch has been exceeded.

Max. number of VLANs per virtual switch

Up to 247 VLAN instances (VLANs) can exist per virtual switch when the GARPVLAN Registration Protocol (GVRP) is enabled in the IEEE 802.1D compliantmultipoint MAC bridge mode of the Gigabit Ethernet port unit.


The following tabular overview summarizes important information concerning the max

number of VLAN instances reached alarm:

Alarm identifier MACVLANOVFW

ASAP type Ethernet





NSA Minor

Alarm source Virtual switch

Notes:

1. The effect-on-service attribute of the max number of VLAN instances reachedalarm is always not service-affecting (NSA). Nevertheless, the SA alarm severity is listedfor the sake of completeness because the alarm is part of the “Ethernet” ASAP which isservice-dependent.

2. One virtual switch is available per Gigabit Ethernet card. Therefore, the alarm is alwaysreported for the first LAN port (Ethernet port) of the Gigabit Ethernet port unit.

Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-95

Trouble clearing

Please refer to “Clearing max number of VLAN instances reached” (p. 3-122).

Alarm messages max number of VLAN instances reached

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Partial Transport Capacity Loss.................................................................................................................................................................................................................................


The transport capacity of the Virtual Concatenated Group (VCG) is partiallyunavailable.

This alarm will only be reported when LCAS is enabled.


The following tabular overview summarizes important information concerning thePartial Transport Capacity Loss alarm:

Alarm identifier VCGLOPC

ASAP type Ethernet





SA Major

NSA Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Partial Transport Capacity Loss” (p. 3-123).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-97

Server Signal Fail (VCGSSF).................................................................................................................................................................................................................................


The entire payload signal transported in the affected Virtual Concatenated Group(VCG) has been replaced by AIS (all-ones signal) due to a failure that occurred in thisNE or in the upstream direction.


The following tabular overview summarizes important information concerning theServer Signal Fail alarm:

Alarm identifier VCGSSF

ASAP type Ethernet





SA Not reported

NSA Not reported


Related information


Local indications


Trouble clearing

Please refer to “Clearing Server Signal Fail (VCGSSF)” (p. 3-124).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Sink End Failure of Protocol.................................................................................................................................................................................................................................


A protocol failure occurred in the receive direction in the Link Capacity AdjustmentScheme (LCAS) protocol.


The following tabular overview summarizes important information concerning the Sink

End Failure of Protocol alarm:

Alarm identifier VCGFOPR

ASAP type Ethernet





SA Major

NSA Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Sink End Failure of Protocol” (p. 3-125).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-99

Source End Failure of Protocol.................................................................................................................................................................................................................................


A protocol failure occurred in the transmit direction in the Link Capacity AdjustmentScheme (LCAS) protocol.


The following tabular overview summarizes important information concerning theSource End Failure of Protocol alarm:

Alarm identifier VCGFOPT

ASAP type Ethernet





SA Major

NSA Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Source End Failure of Protocol” (p. 3-126).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Total Transport Capacity Loss.................................................................................................................................................................................................................................


The transport capacity of the Virtual Concatenated Group (VCG) is completelyunavailable.

This alarm will only be reported when LCAS is enabled.


The following tabular overview summarizes important information concerning theTotal Transport Capacity Loss alarm:

Alarm identifier VCGLOTC

ASAP type Ethernet





SA Critical

NSA Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Total Transport Capacity Loss” (p. 3-127).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-101


Overview.................................................................................................................................................................................................................................

Purpose

In the following, alarm descriptions are given for the alarms related to linear protectionswitching that can be reported by the LambdaUnite® MSS network elements.

Linear protection switching includes:

SDH Multiplex Section Protection (MSP)

SONET Linear Automatic Protection Switching (Linear APS), Line protection

Contents

Far End Signal Fail 2-103

primary section Mismatch 2-105

Prot. Arch. Mismatch 2-107

Prot. Arch. Mode Mismatch 2-108

Prot. Arch. Operation Mismatch 2-110

Prot. Switch Byte Inappropriate 2-112

Prot. Switch Byte Unacceptable 2-114

Switch Channel Mismatch 2-116

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Far End Signal Fail.................................................................................................................................................................................................................................


The APS bytes (K1/K2 bytes in the SDH Multiplex Section Overhead (MSOH) orSONET Line Overhead (LOH) respectively) received from the far end indicate thatthere is a signal fail (SF) condition on the protection line at the far-end receive side.


The following tabular overview summarizes important information concerning the Far

End Signal Fail alarm:

Alarm identifier FESF

ASAP type Automatic Protection Switch




Major

Alarm source SDH: MSP (group)

SONET: Line protection (group)

Related information


Local indications


working

protectionX

Alarm-reportingNE

FESFSF condition

detected

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-103


A protection switch to the protection channels is temporarily not possible.

Trouble clearing

Please refer to “Clearing Far End Signal Fail” (p. 3-129).

Alarm messages Far End Signal Fail

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

primary section Mismatch.................................................................................................................................................................................................................................


The primary section indication in the received K2 byte (K2 [1-4]) does not match theexpected value. This means that the section naming did not change synchronized atboth the near end and the far end of the Multiplex Section.


The following tabular overview summarizes important information concerning theprimary section Mismatch alarm:

Alarm identifier PRIM





Major

Alarm source MSP group

This alarm applies to the optimized 1+1 MSP protocol(in the SDH mode only).

Related information


Local indications


Optimized 1+1 MSP protocol

The optimized bidirectional 1+1 MSP protection uses working sections 1 and 2 insteadof fixed working and protection sections for realizing a high-speed 1+1 non-revertiveprotection switching. On both head-ends the outgoing signals are permanently bridgedto the working sections 1 and 2 so that the same payload is transmitted identically tothe tail-end equipment.

Section naming

In the absence of a switch request the section carrying traffic is the primary section,whereas the other section is the secondary section. All switch requests are for a switch

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-105

from the primary section to the secondary section. Once a switch request clearsnormally, traffic is maintained on the section to which it was switched by making thatsection the primary section.

The bits 1 to 4 of the K2 byte (K2 [1-4]) are used to signal the primary section:

K2 [1-4] Meaning

0001 The working section 1 is the primary section

0010 The working section 2 is the primary section

When the traffic is selected from the secondary section due to a signal fail (SF) orsignal degrade (SD) condition on the primary section, and whenever an SF or SDcondition on the primary section clears and no other condition is pending, then theWait-to-Rename (WtR) timer is started.

After the Wait-to-Rename timer has expired, the secondary section becomes theprimary section (by section renaming), and the primary section becomes the secondarysection. The transmitted K1 and K2 bytes are updated accordingly.

Trouble clearing

Please refer to “Clearing primary section Mismatch” (p. 3-132).

Alarm messages primary section Mismatch

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Prot. Arch. Mismatch.................................................................................................................................................................................................................................


The protection architectures at both end nodes of the optical line do not match.

For example, for the alarm-reporting network element a 1+1 architecture might beprovisioned while for the network element at the far end of the optical line a 1:1architecture is provisioned.


The following tabular overview summarizes important information concerning theProt. Arch. Mismatch (protection architecture mismatch) alarm:

Alarm identifier PAMARCH





Major



Related information


Local indications


Protection architecture

The protection architecture of the Multiplex Section Protection (MSP, SDH) or LineProtection (SONET) respectively is indicated in bit 5 of the K2 byte (K2 [5]):

• K2 [5] = 0 → 1+1 architecture

• K2 [5] = 1 → 1:1 architecture

Trouble clearing

Please refer to “Clearing Prot. Arch. Mismatch” (p. 3-134).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-107

Prot. Arch. Mode Mismatch.................................................................................................................................................................................................................................


The linear protection switching mode of operation provisioned for both end nodes ofthe optical line do not match.


The following tabular overview summarizes important information concerning theProt. Arch. Mode Mismatch (protection architecture mode mismatch) alarm:

Alarm identifier PAMMODE





Major



Related information


Local indications


Modes of operation

These modes of operation exist for linear protection switching:

• Non-revertive modeIn non-revertive switching, an active and stand-by line exist on the network. Whena protection switch occurs, the standby line is selected to support traffic, therebybecoming the active line. The original active line then becomes the stand-by line.This status remains in effect even when the fault clears. That is, there is noautomatic switch back to the original status.

• Revertive modeWhen the condition that caused the protection switching has cleared, service“reverts” to the working line after a configurable wait-to-restore time (WRT).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing

Please refer to “Clearing Prot. Arch. Mode Mismatch” (p. 3-135).

Alarm messages Prot. Arch. Mode Mismatch

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-109

Prot. Arch. Operation Mismatch.................................................................................................................................................................................................................................


The provisioning for unidirectional or bidirectional operation is inconsistent at the nearend and the far end of the optical line.

The far-end information is exchanged by means of bits 6 to 8 of the K2 byte (K2[6-8]) in the APS protocol.

Note

The Prot. Arch. Operation Mismatch alarm is not defined for SDH, because it isnot supported by the SDH APS protocol.


The following tabular overview summarizes important information concerning theProt. Arch. Operation Mismatch alarm:

Alarm identifier PAMOPER





Major

Alarm source SONET: Line protection (group)

Related information


Local indications


Unidirectional or bidirectional operation

Each linear protection switching group can be configured to operate in one of thefollowing two ways (if supported by the protection architecture):

• Unidirectional operationBoth end nodes operate independently from each other.

• Bidirectional operationBoth end nodes operate in a synchronized manner, controlled by the APS protocol.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005


In case of an 1+1 architecture, the NE provisioned for bidirectional operation will beswitched to unidirectional operation.

Trouble clearing

Please refer to “Clearing Prot. Arch. Operation Mismatch” (p. 3-136).

Alarm messages Prot. Arch. Operation Mismatch

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-111

Prot. Switch Byte Inappropriate.................................................................................................................................................................................................................................


An inappropriate APS code and/or invalid channel number has been received in theAPS bytes.

No Prot. Switch Byte Inappropriate alarm will be reported when a Signal Fail(SF) condition exists on the protection line (or on the secondary section in case of 1+1MSP optimized), and an existing Prot. Switch Byte Inappropriate alarm will besuppressed during an SF condition on the protection line (or on the secondary sectionin case of 1+1 MSP optimized).

Please also refer to “Protection Switching Byte (PSB) defect” (p. 2-114).

Inappropriate APS codes

The APS bytes (K1/K2 bytes in the SDH Multiplex Section Overhead (MSOH) orSONET Line Overhead respectively) are monitored for inappropriate APS codes.

An appropriate APS code is defined as a request with equal or higher priority than thelocal request (currently pending switching request), or a reverse request for any localrequest except “No Request”. Otherwise, the APS codes are considered inappropriate.

An APS code irrelevant for the specific switching operation (for example a “ReverseRequest” while no switching request is pending) is also considered inappropriate.


The following tabular overview summarizes important information concerning theProt. Switch Byte Inappropriate alarm:

Alarm identifier PSBINAPPR





Major

Alarm source SDH: MSP (group) in bidirectional operation

SONET: Line protection (group) in bidirectionaloperation

Related information


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Local indications



In bidirectional operation, the Prot. Switch Byte Inappropriate alarm results intothe release of the selector. Furthermore, it may result into a “Failure of Protocol” state.

Trouble clearing

Please refer to “Clearing Prot. Switch Byte Inappropriate” (p. 3-137).

Alarm messages Prot. Switch Byte Inappropriate

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-113

Prot. Switch Byte Unacceptable.................................................................................................................................................................................................................................


An unused APS code, or an “Exercise” request (which is not supported byLambdaUnite® MSS systems) has been received, or the values of the APS bytes(K1/K2 bytes in the SDH Multiplex Section Overhead (MSOH) or SONET LineOverhead respectively) are not stable, i.e. change too frequently (cf. “Inconsistent APSCodes” (p. 2-186)).

Unused codes

The request codes “1001”, “0111”, “0101”, “0100”, and “0011” in K1[1-4] are unused.In case of 1+1 MSP optimized, also the codes “1111”, “1101”, “1011”, “1000”, and“0001” in K1[1-4] are unused.

Protection Switching Byte (PSB) defect

The LambdaUnite® MSS classification of linear protection switching alarms isprimarily based on the Telcordia® GR-253 recommendation. However, the ProtectionSwitching Byte (PSB) defect acc. to Telcordia® GR-253 is split up into two differentdefects for LambdaUnite® MSS systems: Prot. Switch Byte Inappropriate andProt. Switch Byte Unacceptable.

The Prot. Switch Byte Inappropriate defect results in a consequent action whilethe Prot. Switch Byte Unacceptable defect does not (cf. “Effect on protectionswitching”).


The following tabular overview summarizes important information concerning theProt. Switch Byte Unacceptable alarm:

Alarm identifier PSBUNACC





Major



Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Related information


Local indications


Effect on protection switching (consequent action)

The Prot. Switch Byte Unacceptable defect does not result into a consequentaction.

Trouble clearing

Please refer to “Clearing Prot. Switch Byte Unacceptable” (p. 3-138).

Alarm messages Prot. Switch Byte Unacceptable

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-115

Switch Channel Mismatch.................................................................................................................................................................................................................................


There is a mismatch of the channel numbers coded in bits 5 to 8 of the K1 byte(K1[5-8], transmit direction) and bits 1 to 4 of the K2 byte (K2[1-4], receivedirection), i.e. the two NEs concerned use different channels for MSP/APS.

Note

The Switch Channel Mismatch alarm is defined for any mode of operation other than1+1 unidirectional.


The following tabular overview summarizes important information concerning theSwitch Channel Mismatch alarm:

Alarm identifier SCM





Major



Related information


Local indications


Trouble clearing

Please refer to “Clearing Switch Channel Mismatch” (p. 3-142).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005


Overview.................................................................................................................................................................................................................................

Purpose

In the following, alarm descriptions are given for the path-related transmission alarmsthat can be reported by the LambdaUnite® MSS network elements.

“Path-related transmission alarms” includes alarms pertaining to the following ASAPtypes:

• Path MSA/NIM related

• Path Termination

• Sub-Network Connection Protection and Unidirectional Path Switched Ring

Contents

Alarm Indication Signal (AIS-P) 2-119

Degraded Signal (DEG-P) 2-120

Degraded Signal (THPDEG) 2-121

Excessive Bit Error Ratio (EXC-P) 2-122

Excessive Bit Error Ratio (THPEXC) 2-124

Loss of Multiframe 2-126

Loss of Pointer (LOP-P) 2-128

Loss of Pointer (THPLOP) 2-129

Path Switch Denial 2-131

Payload Defect Indication 2-132

Payload Mismatch 2-134

Remote Defect Indication (RFI-P) 2-135

Remote Defect Indication (THPRDI) 2-137

Sequence Number Mismatch 2-138

Server Signal Fail (SSF-P) 2-140

Server Signal Fail (THPSSF) 2-141

Signal Rate Mismatch 2-142

Trace Identifier Mismatch (TIM-P) 2-144

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-117

Trace Identifier Mismatch (THPTIM) 2-145

Unequipped (UNEQ-P) 2-147

Unequipped (THPUNEQ) 2-149


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Alarm Indication Signal (AIS-P).................................................................................................................................................................................................................................


The Alarm Indication Signal (AIS) has been detected in the receive signal of the path.The signal cannot be used.


The following tabular overview summarizes important information concerning theAlarm Indication Signal alarm:

Alarm identifier AIS-P

ASAP type Path MSA/NIM related





SA Not reported

NSA Not reported

Alarm source Non-intrusively monitored path

Related information


Local indications


Consequent actions

AIS (all-ones signal) on path level is inserted in the downstream direction.


The alarm is a trigger for UPSR and SNCP (SNC/N, but not SNC/I) automatic pathprotection switching.

Trouble clearing

Please refer to “Clearing Alarm Indication Signal (AIS-P)” (p. 3-144).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-119

Degraded Signal (DEG-P).................................................................................................................................................................................................................................


The bit error ratio (BER) in the path has exceeded the provisioned HP DegradedThreshold. The quality of the transmission signal is degraded.

The alarm is detected at a non-intrusive monitoring (NIM) point.


The following tabular overview summarizes important information concerning theDegraded Signal alarm:

Alarm identifier DEG-P






SA Major

NSA Minor


Related information


Local indications



The alarm is a trigger for SNCP (SNC/N, but neither SNC/I nor UPSR) automatic pathprotection switching.

Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Degraded Signal (THPDEG).................................................................................................................................................................................................................................


The bit error ratio (BER) in the path has exceeded the provisioned HP DegradedThreshold. The quality of the transmission signal is degraded.

The alarm is detected at the path termination.



Alarm identifier THPDEG

ASAP type Path Termination





SA Major

NSA Minor

Alarm source Path termination

Related information


Local indications




Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-121

Excessive Bit Error Ratio (EXC-P).................................................................................................................................................................................................................................


The bit error ratio (BER) in the path, calculated using the B3 byte of the PathOverhead (POH), has exceeded the provisioned HP DEXC Threshold.

The HP DEXC Threshold can be set in terms of integer powers of ten between 10–3

and 10–5. The default setting is 10–3.



The following tabular overview summarizes important information concerning theExcessive Bit Error Ratio alarm:

Alarm identifier EXC-P






SA Critical

NSA Minor


Related information


Local indications




Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing


Alarm messages Excessive Bit Error Ratio (EXC-P)

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-123

Excessive Bit Error Ratio (THPEXC).................................................................................................................................................................................................................................


The bit error ratio (BER) in the path, calculated using the B3 byte of the PathOverhead (POH), has exceeded the provisioned HP DEXC Threshold.

The HP DEXC Threshold can be set in terms of integer powers of ten between 10–3

and 10–5. The default setting is 10–3.




Alarm identifier THPEXC






SA Critical

NSA Minor


Related information


Local indications


Consequent actions

AIS (all-ones signal) on path level is inserted in the downstream direction.

RDI (Remote Defect Indication) on path level is inserted in the upstream direction.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



Trouble clearing


Alarm messages Excessive Bit Error Ratio (THPEXC)

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-125

Loss of Multiframe.................................................................................................................................................................................................................................


No multiframe sequence can be derived from the received H4 byte of the VC-4 PathOverhead.

Loss of Multiframe is applicable for VC-4s substructured into lower order tributaries(TU-12 substructure), or VC-4s in a Virtual Concatenated Group (VCG).

Important! In order to guarantee a proper Loss of Multiframe supervision forSDH signals with a mixed lower order tributary substructure (TU-12 and TU-3),the first TUG-3 of the VC-4 must have a TU-12 substructure. The substructure ofthe second and third TUG-3 may be either TU-12 or TU-3.



of Multiframe alarm:

Alarm identifier VCLOM






SA Critical

NSA Minor

Alarm source VC-4 path termination

Related information


Local indications


Consequent actions

AIS (all-ones signal in the affected VC-4s) is inserted in the downstream direction.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Virtual concatenation multiframe indicators

The consecutive frames of the VC-4s in a Virtual Concatenated Group (VCG) areorganized into a multiframe consisting of 4096 frames by writing a 12-bit multiframeindicator into the H4 byte of the VC-4 Path Overhead (VC-4-POH). The individual bitsof the 12-bit multiframe indicator are distributed to several frames to accomplish thetransmission of a 12-bit multiframe indicator by using a single byte. Therefore, a 12-bitmultiframe indicator consists of two parts, a multiframe 1 (MF1) and a multiframe 2(MF2).

Multiframe 1 (MF1) The four least significant bits of the 12-bit multiframeindicator are transmitted each frame in bits 5 to 8 of the H4byte forming a multiframe 1 (MF1) which consists of 16frames. Per MF1, the inserted bits are incremented insuccessive frames from “0000” to “1111”. An MF1 is 2 mslong as the basic frame length is 125 µs.

Multiframe 2 (MF2) The eigth most significant bits of the 12-bit multiframeindicator are transmitted only once per MF1, in bits 1 to 4 ofthe H4 byte, four bits in the first frame of MF1 and four bitsin the second frame. These bits form a multiframe 2 (MF2)consisting of 256 MF1s (4096 frames). Per MF2, the insertedbits are incremented in successive MF1s from “00000000” to“11111111”. An MF2 is 512 ms long.

Furthermore, bits 1 to 4 of the H4 byte are used to transmit sequence numbersassociated with the VC-4s (in the last two frames of each MF1) and the Link CapacityAdjustment Scheme (LCAS) protocol, thus providing a means to clearly identify theordering of the transmitted VC-4s, and, at the receiver, to compensate possible delaydifferences between the individual VC-4s of the Virtual Concatenated Group.


The alarm is a trigger for UPSR and SNCP (SNC/N and SNC/I) automatic pathprotection switching.

Trouble clearing


Alarm messages Loss of Multiframe

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-127

Loss of Pointer (LOP-P).................................................................................................................................................................................................................................


The expected signal structure cannot be found in the receive signal.




of Pointer alarm:

Alarm identifier LOP-P






SA Critical

NSA Minor


Related information


Local indications




Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Loss of Pointer (THPLOP).................................................................................................................................................................................................................................


The expected signal structure cannot be found in the receive signal.

The received pointers do not represent a valid concatenation structure. Either thepointer value or the concatenation indication is invalid.

The Loss of Pointer (THPLOP) alarm is specific to SONET ports configured foradaptive-rate tributary operation (“pipe mode”).




of Pointer alarm:

Alarm identifier THPLOP






SA Critical

NSA Minor


Related information


Local indications


Consequent actions

AIS (all-ones signal) is inserted in the downstream direction for each of the tributariesfor which the Loss of Pointer (THPLOP) is detected.

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-129



Trouble clearing


Alarm messages Loss of Pointer (THPLOP)

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Path Switch Denial.................................................................................................................................................................................................................................


Although a switching criterion for automatic path protection switching has beendetected (for example Alarm Indication Signal (AIS-P), Loss of Pointer (LOP-P)or Unequipped (UNEQ-P)), the protection switch has not been performed eitherbecause a path protection switch request of a higher or equal priority is active, or thereis an invalid signal (for example a signal fail (SF) condition) on the protection path.

For example, a Path Switch Denial alarm will be reported if AIS-P is detected onthe working path, and a “Forced Switch to Working” command was previouslyinitiated for the path.


The following tabular overview summarizes important information concerning the Path

Switch Denial alarm:

Alarm identifier FAILTOSW

ASAP type Sub-Network Connection Protection and UnidirectionalPath Switched Ring




Not alarmed

Alarm source Path protection group

Related information


Local indications


Trouble clearing

Please refer to “Clearing Path Switch Denial” (p. 3-145).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-131

Payload Defect Indication.................................................................................................................................................................................................................................


The Payload Defect Indication alarm indicates the number of defects in thepayload.

Please notice that the detection of this alarm is supported for both SONET and SDHsignals, although not requested by the standards for SDH signals.


The following tabular overview summarizes important information concerning thePayload Defect Indication alarm:

Alarm identifier PDI-P






SA Major

NSA Minor


Related information


Local indications



The alarm is a trigger for UPSR (not SNCP!) automatic path protection switching ifcorrespondingly provisioned. The PDI-P Switching Enable parameter determines if thePayload Defect Indication shall contribute to automatic path protection switchingor not.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing


Alarm messages Payload Defect Indication

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-133

Payload Mismatch.................................................................................................................................................................................................................................


The received (and accepted) trail signal label (TSL) differs from the expected TSL andhas a value other than ″equipped - not specified″.

A TSL is accepted after the reception of five consecutive C2 bytes with identicalvalues.


The following tabular overview summarizes important information concerning thePayload Mismatch alarm:

Alarm identifier THPPLM






SA Critical

NSA Minor

Alarm source Payload signal

Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Remote Defect Indication (RFI-P).................................................................................................................................................................................................................................


The receive signal contains RDI.

This means that the network element at the far-end path termination (in thedownstream direction) has detected a defect in the incoming signal and has insertedRDI into the outgoing signal as a consequent action.



The following tabular overview summarizes important information concerning theRemote Defect Indication alarm:

Alarm identifier RFI-P






SA Not reported

NSA Not reported


Notes:

1. In SONET standards, a distinction is made between the RDI defect and the resultingfailure, which is RFI (Remote Failure Indication). Therefore, RFI is used in the alarmidentifier.

Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-135

Trouble clearing

Please refer to “Clearing Remote Defect Indication (RFI-P)” (p. 3-146).

Alarm messages Remote Defect Indication (RFI-P)

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Remote Defect Indication (THPRDI).................................................................................................................................................................................................................................



This means that the network element at the far-end path termination has detected adefect in the incoming signal and has inserted RDI into the outgoing signal as aconsequent action.




Alarm identifier THPRDI






SA Not reported

NSA Not reported


Related information


Local indications


Trouble clearing

Please refer to “Clearing Remote Defect Indication (THPRDI)” (p. 3-147).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-137

Sequence Number Mismatch.................................................................................................................................................................................................................................


The accepted and the expected sequence number of at least one tributary (VC-4 orSTS-1) in a Virtual Concatenated Group (VCG) does not match.


The following tabular overview summarizes important information concerning theSequence Number Mismatch alarm:

Alarm identifier VCSQM






SA Critical

NSA Minor


Related information


Local indications


Sequence numbers

Sequence numbers are used to signal to the receive end in which order the individualtributaries of the Virtual Concatenated Group (VCG) are filled with payload data andto check that ordering of the tributaries inside the VCG has not been altered duringtransport.

Each tributary inside a VCG carries a sequence number in the last two frames ofmultiframe 1 (MF1). A received sequence number is considered an “accepted”sequence number, if it is identical in three consecutive MF1s. The accepted sequence

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

numbers can be useful when corrective actions are necessary, for example to findmisconnections in other network elements.

Sequence numbers are not evaluated when the Link Capacity Adjustment Scheme(LCAS) protocol is active.

Trouble clearing


Alarm messages Sequence Number Mismatch

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-139

Server Signal Fail (SSF-P).................................................................................................................................................................................................................................


The payload signal has been replaced by AIS (all-ones signal) due to a failure thatoccurred in the upstream direction.




Alarm identifier SSF-P






SA Not reported

NSA Not reported


Related information


Local indications


Trouble clearing

Please refer to “Clearing Server Signal Fail (SSF-P)” (p. 3-148).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Server Signal Fail (THPSSF).................................................................................................................................................................................................................................


The payload signal has been replaced by AIS (all-ones signal) due to a failure thatoccurred in the upstream direction.




Alarm identifier THPSSF






SA Not reported

NSA Not reported


Related information


Local indications


Trouble clearing

Please refer to “Clearing Server Signal Fail (THPSSF)” (p. 3-149).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-141

Signal Rate Mismatch.................................................................................................................................................................................................................................


The Signal Rate Mismatch alarm is reported whenever one of the following twosituations occur:

• The constituent signal rate for a certain set of tributaries is larger than the rate of across connection configured for these tributaries.

• There is a mismatch between the received and the expected signal structure in aport working in adaptive-rate tributary mode but which tries to approximate thefixed-rate mode. In this case, the Signal Rate Mismatch alarm is reported insteadof the Loss of Pointer alarm that a normal fixed-rate port would have issued.


The following tabular overview summarizes important information concerning theSignal Rate Mismatch alarm:

Alarm identifier SRM-P






SA Major

NSA Minor


Related information


Local indications




Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing


Alarm messages Signal Rate Mismatch

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-143

Trace Identifier Mismatch (TIM-P).................................................................................................................................................................................................................................


The received path trace identifier in the J1 byte of the VC-n or STS-m Path Overhead(POH) does not match the expected path trace identifier.



The following tabular overview summarizes important information concerning theTrace Identifier Mismatch alarm:

Alarm identifier TIM-P






SA Critical

NSA Minor


Related information


Local indications




Trouble clearing

Please refer to “Clearing Trace Identifier Mismatch (TIM-P)” (p. 3-151).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trace Identifier Mismatch (THPTIM).................................................................................................................................................................................................................................


The received path trace identifier in the J1 byte of the VC-4 or STS-1 Path Overhead(POH) does not match the expected path trace identifier provisioned for thecorresponding path termination.




Alarm identifier THPTIM






SA Critical

NSA Minor


Related information


Local indications


Related information


Consequent actions

AIS (all-ones signal) is inserted in the downstream direction.

HP-RDI is inserted in the upstream (opposite) direction.

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-145



Trouble clearing

Please refer to “Clearing Trace Identifier Mismatch (THPTIM)” (p. 3-150).

Alarm messages Trace Identifier Mismatch (THPTIM)

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Unequipped (UNEQ-P).................................................................................................................................................................................................................................


The corresponding tributary channel in the receive signal is not in use. Possibly, thecross-connections are not consistently defined at both sides of a line (e. g. at the localand remote station).



The following tabular overview summarizes important information concerning theUnequipped alarm:

Alarm identifier UNEQ-P






SA Critical

NSA Minor


Related information


Local indications


Consequent actions

As the alarm is detected at a non-intrusive monitoring (NIM) point, no consequentactions are inserted.



Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-147

Trouble clearing

Please refer to “Clearing Unequipped (UNEQ-P)” (p. 3-153).

Alarm messages Unequipped (UNEQ-P)

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Unequipped (THPUNEQ).................................................................................................................................................................................................................................


The corresponding tributary channel in the receive signal is not in use. Possibly, thecross-connections are not consistently defined at both ends of the path (e. g. at thelocal and remote station).



The following tabular overview summarizes important information concerning theUnequipped alarm:

Alarm identifier THPUNEQ






SA Critical

NSA Minor


Related information


Local indications


Consequent actions


HP-RDI is inserted in the upstream (opposite) direction.

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-149



Trouble clearing

Please refer to “Clearing Unequipped (THPUNEQ)” (p. 3-152).

Alarm messages Unequipped (THPUNEQ)

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Port-related transmission alarms

Overview.................................................................................................................................................................................................................................

Purpose

In the following, alarm descriptions are given for the port-related transmission alarmsthat can be reported by the LambdaUnite® MSS network elements.

Contents

Alarm Indication Signal (AIS-L) 2-152

Backw Defect Transparent Ch 2-154

Degraded Signal (MSDEG) 2-155

Excessive Bit Error Ratio (MSEXC) 2-157

LOF Transparent Ch 2-159

Loss of Frame 2-160

Loss of Frame transp ch egress 2-162

Loss of Multiframe Transparent Ch 2-163

Loss of Signal 2-164

OCh Loss of Frame 2-166

Payload Mismatch Transparent Ch 2-167

Post DCM Signal Loss 2-168

Pre DCM Signal Loss 2-170

Remote Defect Indication (RFI-L) 2-172

Server Signal Fail (MSSSF) 2-173

Server Signal Fail Transparent Ch 2-174

Trace Identifier Mismatch (RSTIM) 2-175

Trace Identifier Mismatch egress (TIM-T-EGR) 2-176

WTU3 Loss of Frame 2-177

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-151

Alarm Indication Signal (AIS-L).................................................................................................................................................................................................................................


The receive signal contains MS-AIS or Line AIS respectively.

MS-AIS or Line AIS respectively is an indication that Loss of Signal or Loss of

Frame has been detected in the upstream equipment.


The following tabular overview summarizes important information concerning theAlarm Indication Signal alarm:

Alarm identifier AIS-L






SA Critical

NSA Minor

Alarm source SDH/SONET interface port

Related information


Local indications


Consequent actions


RDI is inserted in the upstream (opposite) direction.


The alarm is a trigger for BLSR/MS-SPRing protection switching.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing

Please refer to “Clearing Alarm Indication Signal (AIS-L)” (p. 3-155).

Alarm messages Alarm Indication Signal (AIS-L)

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-153

Backw Defect Transparent Ch.................................................................................................................................................................................................................................


The receive signal contains the Backward Defect Indication (BDI).

BDI is an indication that a signal fail (SF) condition has been detected in thedownstream equipment.


The following tabular overview summarizes important information concerning theBackw Defect Transparent Ch alarm:

Alarm identifier ODUBDIT

ASAP type Fully Transparent Service




Major

Alarm source OPT2G5 port

Notes:

1. The fully transparent service is unprotected. Therefore, the related alarms are alwaysservice-affecting (SA).

Related information


Local indications

The red fault LED on the faceplate of the respective OPT2G5 port unit is flashing.

Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Degraded Signal (MSDEG).................................................................................................................................................................................................................................


The quality of the transmission signal is degraded.

The alarm is initiated if the bit error ratio (BER) in the Multiplex Section (MS) orLine respectively, calculated using the B2 bytes of the MS or Line Overhead (MSOH,LOH), exceeds the provisioned Degraded Signal BER Threshold.

The Degraded Signal BER Threshold can be set in terms of integer powers of tenbetween 10-3 and 10-9. The default setting is 10-6.



Alarm identifier MSDEG






SA Major

NSA Minor

Alarm source SDH/SONET interface port:

• Optical SDH interface port (STM-1, STM-4,STM-16, STM-64, and STM-256)

• Electrical STM-1 port (STM-1E)

• Optical SONET interface port (OC-3, OC-12,OC-48, OC-192, and OC-768)

• Fully transparent port (STM-16T, OC-48T)

Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-155



Trouble clearing

A Degraded Signal condition is less critical than an Excessive Bit Error Ratio.However, in principle you can take the same measures as for “Clearing Excessive BitError Ratio” (p. 3-156), taking into account the required measurement times todetermine the bit error ratio.

Required measurement times for BER

Especially if the threshold for the detection of a signal degrade is set to 10-7, 10-8 or10-9, relatively long measurement times are needed to determine the bit error ratio.

Threshold Max. duration of measurement acc. to ITU-T Rec. G.783

10-5 approx. 1 s

10-6 approx. 10 s

10-7 approx. 100 s

10-8 approx. 1000 s (=16 min 40 s)

10-9 approx. 10000 s (= 2 h 46 min 40 s)

Alarm messages Degraded Signal (MSDEG)

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Excessive Bit Error Ratio (MSEXC).................................................................................................................................................................................................................................


The bit error ratio (BER) in the Multiplex Section (MS) or Line respectively is veryhigh and the signal received at an electrical or optical SDH/SONET interface istherefore subject to considerable interference.

An Excessive Bit Error Ratio alarm is initiated if the BER in the MultiplexSection (MS) or Line respectively, calculated using the B2 bytes of the MS or LineOverhead (MSOH, LOH), exceeds the provisioned Excessive BER Threshold.

The Excessive BER Threshold can be set in terms of integer powers of ten between10–3 and 10–5. The default setting is 10–3.

Important! The alarm is not defined in Burst mode but only in Poisson mode.



Alarm identifier MSEXC






SA Critical

NSA Minor






Related information


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-157

Local indications




Trouble clearing

Please refer to “Clearing Excessive Bit Error Ratio” (p. 3-156).

Alarm messages Excessive Bit Error Ratio (MSEXC)

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

LOF Transparent Ch.................................................................................................................................................................................................................................


The position of the ODU1 frame alignment bytes (OA1/OA2 bytes) cannot be detectedcorrectly in the receive signal, frame alignment is not possible.


The following tabular overview summarizes important information concerning the LOF

Transparent Ch alarm:

Alarm identifier ODULOFT





Critical

Alarm source OPT2G5

Notes:


Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-159

Loss of Frame.................................................................................................................................................................................................................................


The position of the frame alignment bytes (A1/A2 bytes) cannot be detected correctlyin the receive signal, frame alignment is not possible.



of Frame alarm:

Alarm identifier LOF






SA Critical

NSA Minor

Alarm source SDH/SONET optical interface port

Related information


Local indications


Possible causes

A Loss of Frame alarm may have the following causes:

• The receive signal does not match the port rate (due to a misconnected fiber forexample). For example, an OC-12 signal is received at an OC-48/STM-16 port.

• The Section Overhead (SOH) of the SDH or SONET receive signal is not correctlystructured (due to a failure of the transmit circuit pack at the far end).

• At the far end, the Optical Channel (OCh) is enabled while it is disabled at the portfor which the alarm is reported.

• The receiver at the circuit pack reporting the alarm is defective.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Consequent actions



Important! Please note, that on an OP10, the AIS insertion time may varybetween 0 and 60 ms after clearing the Loss of Frame condition.


Loss of Frame is a trigger for line protection switching (MSP, linear APS) and ringprotection switching (MS-SPRing, BLSR).

Trouble clearing

Please refer to “Clearing Loss of Frame” (p. 3-163).

Alarm messages Loss of Frame

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-161

Loss of Frame transp ch egress.................................................................................................................................................................................................................................


Frame alignment cannot be achieved in the egress direction of a fully transparent path,i.e. the position of the frame alignment bytes (A1/A2 bytes) cannot be detectedcorrectly in the reconstructed SDH/SONET client signal.



of Frame transp ch egress alarm:

Alarm identifier LOF-T-EGR





Critical


Notes:


Related information


Local indications

The red fault LED on the faceplate of the OPT2G5 port unit is flashing.

Trouble clearing

Please refer to “Clearing Loss of Frame transp ch egress” (p. 3-166).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Loss of Multiframe Transparent Ch.................................................................................................................................................................................................................................


No multiframe sequence can be derived from the received multiframe alignment signal(MFAS) of the OTU1/ODU1 overhead.



of Multiframe Transparent Ch alarm:

Alarm identifier ODULOMT





Critical

Alarm source OPT2G5

Notes:


Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-163

Loss of Signal.................................................................................................................................................................................................................................


The input power at the corresponding port is too low. Frame alignment andsynchronisation to the receive signal is not possible.

When gradually decreasing the optical input power below the receiver sensitivity limit,it might happen that first a Loss of Frame will be reported and at an even lower levela Loss of Signal.

For passive WDM and DWDM interfaces, in incidental cases when the actual receiversensitivity is better than required, it may happen that when gradually increasing theattenuation, a Loss of Signal alarm is reported while no Degraded Signal

(MSDEG) and/or Excessive Bit Error Ratio (MSEXC) alarm is reported first. Thisadditionally depends on the actual threshold setting for MSDEG (10–9

10–5) andMSEXC (10–5

10–3).



of Signal alarm:

Alarm identifier LOS






SA Critical

NSA Minor






Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Related information


Possible causes

A Loss of Signal alarm may have the following causes:

• Cable break along the route,

• Connector is not terminated or features impurities,

• Defective optical receiver,

• Defective optical transmitter at the far end,

• Inputs and outputs are mixed up.

Local indications


The red port LED associated to the pluggable optical interface is flashing if the alarmis reported by a pluggable optical interface.

Consequent actions




A Loss of Signal defect is a trigger for line protection switching (MSP, linear APS)and ring protection switching (MS-SPRing, BLSR).

Trouble clearing

Please refer to “Clearing Loss of Signal” (p. 3-167).

Alarm messages Loss of Signal

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-165

OCh Loss of Frame.................................................................................................................................................................................................................................


The position of the frame alignment bytes (OA1/OA2 bytes) cannot be detectedcorrectly in the receive signal.


The following tabular overview summarizes important information concerning the OCh


Alarm identifier OCHLOF






SA Critical

NSA Minor

Alarm source 10-Gbit/s SDH/SONET optical interface port

Related information


Local indications


Trouble clearing

Please refer to “Clearing OCh Loss of Frame” (p. 3-174).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Payload Mismatch Transparent Ch.................................................................................................................................................................................................................................


The payload signal transported over the transparent channel is unexpectedly not anasynchronously mapped 2.5-Gbit/s signal of constant bit rate (CBR2G5 signal).


The following tabular overview summarizes important information concerning thePayload Mismatch Transparent Ch alarm:

Alarm identifier ODUPLMT





Critical


Notes:


Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-167

Post DCM Signal Loss.................................................................................................................................................................................................................................


There is no input signal at the input port of the optical booster amplifier (OBA IN) ofan OP40 port unit for long reach applications, or the signal level is too low.

As the OP40 port unit for long reach applications is operated using an opticalpre-amplifier (OPA) and an optical booster amplifier (OBA) in combination withdispersion compensation modules (DCM), three different Loss of Signal alarms aredefined, please refer to the following diagram:

Legend:

1 Post DCM Signal Loss

2 Loss of Signal

3 Pre DCM Signal Loss


The following tabular overview summarizes important information concerning the Post

DCM Signal Loss alarm:

Alarm identifier POSTDCMLOS

OBA OUT

OBA IN

OP40DCM

OUT

TX OUT IN

OPA OUT

OPA IN

DCM

OUTRX IN

IN

(Post DCM)

(Pre DCM)

OBA

OPA

1

2

3

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005






SA Critical

NSA Minor

Alarm source OP40 optical interface port (OP40 for long reachapplications, with OPA and OBA)

Related information


Local indications


Trouble clearing

Please refer to “Clearing Post DCM Signal Loss” (p. 3-175).

Alarm messages Post DCM Signal Loss

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-169

Pre DCM Signal Loss.................................................................................................................................................................................................................................


There is no input signal at the optical input port (RX IN) of an OP40 port unit for longreach applications, or the signal level is too low.

As the OP40 port unit for long reach applications makes use of an optical pre-amplifier(OPA) and an optical booster amplifier (OBA) in combination with dispersioncompensation modules (DCM), three different alarms are defined that are related toLoss of Signal conditions, please refer to the following diagram:

Legend:

1 Post DCM Signal Loss

2 Loss of Signal

3 Pre DCM Signal Loss


The following tabular overview summarizes important information concerning the Pre

DCM Signal Loss alarm:

Alarm identifier PREDCMLOS

OBA OUT

OBA IN

OP40DCM

OUT

TX OUT IN

OPA OUT

OPA IN

DCM

OUTRX IN

IN

(Post DCM)

(Pre DCM)

OBA

OPA

1

2

3

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005






SA Critical

NSA Minor

Alarm source OP40 optical interface port (OP40 for long reachapplications, with OPA and OBA)

Related information


Local indications


Trouble clearing

Please refer to “Clearing Pre DCM Signal Loss” (p. 3-176).

Alarm messages Pre DCM Signal Loss

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-171

Remote Defect Indication (RFI-L).................................................................................................................................................................................................................................



The network element at the far end of the Multiplex Section or Line respectively (inthe downstream direction) has detected an error in the incoming signal and, as aconsequent action, has inserted RDI (“110” in bits 6, 7 and 8 of the K2 byte) into theoutgoing signal in the upstream direction.



Alarm identifier RFI-L






SA Not reported

NSA Not reported


Notes:

1. In SONET standards, a distinction is made between the RDI defect and the resultingfailure, which is RFI (Remote Failure Indication). Therefore, RFI is used in the alarmidentifier.

Related information


Local indications


Trouble clearing

Please refer to “Clearing Remote Defect Indication (RFI-L)” (p. 3-177).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Server Signal Fail (MSSSF).................................................................................................................................................................................................................................


The receive signal contains AIS (all-ones signal) due to a signal failure that occurred inthe upstream direction.



Alarm identifier MSSSF






SA Not reported

NSA Not reported


Related information


Local indications


Trouble clearing

Please refer to “Clearing Server Signal Fail (MSSSF)” (p. 3-178).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-173

Server Signal Fail Transparent Ch.................................................................................................................................................................................................................................


The entire payload signal transported in the affected Optical Data Unit (ODU) has beenreplaced by AIS (all-ones signal) due to a failure that occurred in the upstreamdirection.


The following tabular overview summarizes important information concerning theServer Signal Fail Transparent Ch alarm:

Alarm identifier ODUSSFT





Not reported

Alarm source OPT2G5

Notes:


Related information


Local indications


Trouble clearing

Please refer to “Clearing Server Signal Fail Transparent Ch” (p. 3-179).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trace Identifier Mismatch (RSTIM).................................................................................................................................................................................................................................


The received section trace identifier in the J0 byte of the STM-n or OC-m SectionOverhead (SOH) does not match the expected section trace identifier.



Alarm identifier RSTIM






SA Critical

NSA Minor


Related information


Local indications


Consequent actions



Trouble clearing

Please refer to “Clearing Trace Identifier Mismatch (RSTIM)” (p. 3-180).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-175

Trace Identifier Mismatch egress (TIM-T-EGR).................................................................................................................................................................................................................................


The section trace identifier in the J0 byte of the STM-n or OC-m Section Overhead(SOH) does not match the expected value in the reconstructed SDH/SONET clientsignal in the egress direction of a fully transparent path.


The following tabular overview summarizes important information concerning theTrace Identifier Mismatch egress alarm:

Alarm identifier TIM-T-EGR





SA Critical

NSA – (not applicable)

Alarm source OPT2G5

Notes:


Related information


Local indications

The red fault LED on the faceplate of the OPT2G5 port unit is flashing.

Trouble clearing

Please refer to “Clearing Trace Identifier Mismatch egress (TIM-T-EGR)” (p. 3-181).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

WTU3 Loss of Frame.................................................................................................................................................................................................................................


The position of the frame alignment bytes (OA1/OA2 bytes) cannot be detectedcorrectly in the receive signal.


The following tabular overview summarizes important information concerning the WTU3


Alarm identifier WTU3LOF






SA Critical

NSA Minor

Alarm source 40-Gbit/s SDH/SONET optical interface port

Related information


Local indications


Trouble clearing

Please refer to “Clearing WTU3 Loss of Frame” (p. 3-183).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-177


Overview.................................................................................................................................................................................................................................

Purpose

In the following, alarm descriptions are given for the alarms related to ring protectionswitching that can be reported by the LambdaUnite® MSS network elements.

Contents

Default K-bytes 2-179

Duplicate Ring Node 2-181

Extra Traffic Preempted 2-183

Improper APS Codes 2-184

Inconsistent APS Codes 2-186

Inconsistent Ring Protection Mode 2-188

Local Squelch Map Conflict 2-189

Node ID Mismatch 2-191

Open Ring 2-192

Ring Discovery in Progress 2-193

Ring Incomplete 2-195

Ring Protection Switch Suspended 2-197

Traffic Squelched 2-198

Unknown Ring Type 2-202

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Default K-bytes.................................................................................................................................................................................................................................


The source node and destination node identifiers in the received APS bytes (K1 andK2 bytes) have equal values.

Furthermore, the Default K-bytes alarm will be reported if the worker and protectionport in a 4-fiber BLSR/MS-SPRing configuration are interchanged.

Default K1/K2 bytes

The K1/K2 bytes in the SDH Multiplex Section Overhead (MSOH) or SONET LineOverhead (LOH) respectively are used to transport the BLSR/MS-SPRing automaticprotection switching (APS) protocol.

Default K1/K2 bytes with identical source node and destination node identifiers areinserted when a ring node is not in a position to properly signal the BLSR/MS-SPRingprotection switching protocol, and therefore cannot properly execute BLSR/MS-SPRingprotection switching.


The following tabular overview summarizes important information concerning theDefault K-bytes alarm:

Alarm identifier DKB

ASAP type MS-SPRing and Bilateral Switched Ring ProtectionSwitch




Major

Alarm source BLSR/MS-SPRing protection group

Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-179


BLSR/MS-SPRing protection switching is not possible.

Trouble clearing

Please refer to “Clearing Default K-bytes” (p. 3-185).

Alarm messages Default K-bytes

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Duplicate Ring Node.................................................................................................................................................................................................................................


The Duplicate Ring Node alarm is reported by all the nodes of a ring if one of thefollowing erroneous BLSR/MS-SPRing configurations has been detected:

• There are more than 16 nodes on the ring.

• There are multiple ring nodes from the same LambdaUnite® MSS NE on the ring.

• There are multiple network elements with the same NE name (TID) on the ring.


The following tabular overview summarizes important information concerning theDuplicate Ring Node alarm:

Alarm identifier DUPL-RNG





Major


Related information


Local indications



Ring protection switching is suspended (disabled) as long as a Duplicate Ring Node

alarm is present.

Related information

Please also refer to “Automatic node ID allocation” (p. 2-219).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-181

Trouble clearing

Please refer to “Clearing Duplicate Ring Node” (p. 3-190).

Trouble clearing


Alarm messages Duplicate Ring Node

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Extra Traffic Preempted.................................................................................................................................................................................................................................


Any extra traffic in the ring has been preempted (replaced by AIS) due to a ringprotection switch.

The Extra Traffic Preempted “alarm” is to be understood as an information ratherthan as an alarm.

Extra traffic

When the protection channels are not being used to restore working channels, they canbe used to carry additional working traffic. This additional traffic, referred to as “extratraffic”, has lower priority than the traffic on the working channels. In the event of aring protection switch, the traffic on the working channels will access the protectionchannels causing any extra traffic to be preempted, or removed, from the protectionchannels. When the failure that caused the protection switch has been cleared, the extratraffic will be restored.


The following tabular overview summarizes important information concerning theExtra Traffic Preempted alarm:

Alarm identifier ET-PREEMPT





Not alarmed


Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-183

Improper APS Codes.................................................................................................................................................................................................................................


An Improper APS Codes alarm is reported

• if an expected request code in K1[1-4] is not received within a predefined timelimit of two seconds, or

• if invalid K1/K2 bytes are received:

– APS bytes with an unused channel status code in K2[6-8],

– APS bytes with an invalid request code in K1[1-4].


The following tabular overview summarizes important information concerning theImproper APS Codes alarm:

Alarm identifier IMAPS





Major


Related information


Local indications



An existing ring protection switch will be released when the Improper APS Codes

alarm condition is received on the long path.

Meaning of “short path” and “long path”

In a typical 2-fiber BLSR/MS-SPRing configuration the working traffic will usually berouted the short way around the ring (“short path”) as long as no ring protectionswitching conditions are present. After a ring protection switch due to a failure on the

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

short path the traffic will be routed in the opposite direction, the long way around thering (“long path”).

Trouble clearing

Please refer to “Clearing Improper APS Codes” (p. 3-193).

Alarm messages Improper APS Codes

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-185

Inconsistent APS Codes.................................................................................................................................................................................................................................


The values of the APS bytes (K1/K2 bytes in the SDH Multiplex Section Overhead(MSOH) or SONET Line Overhead respectively) are not stable, i.e. change toofrequently.

In the twelve frames starting with the last frame containing previously consistent APSbytes, there are not three consecutive frames containing identical K1 and K2 bytes.


The following tabular overview summarizes important information concerning theInconsistent APS Codes alarm:

Alarm identifier APSC





Major


Related information


Local indications



An existing ring protection switch will be released when the Inconsistent APS

Codes alarm condition is received on the long path.

Meaning of “short path” and “long path”

In a typical 2-fiber BLSR/MS-SPRing configuration the working traffic will usually berouted the short way around the ring (“short path”) as long as no ring protectionswitching conditions are present. After a ring protection switch due to a failure on the

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

short path the traffic will be routed in the opposite direction, the long way around thering (“long path”).

Trouble clearing

Please refer to “Clearing Inconsistent APS Codes” (p. 3-197).

Alarm messages Inconsistent APS Codes

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-187

Inconsistent Ring Protection Mode.................................................................................................................................................................................................................................


The ring protection mode (Ring Loopback, Shortened Path) is not consistentlyprovisioned for all nodes on the ring.

The Inconsistent Ring Protection Mode alarm is only applicable to 4-fiberMS-SPRing configurations.


The following tabular overview summarizes important information concerning theInconsistent Ring Protection Mode alarm:

Alarm identifier RNG-IRPM





Major

Alarm source 4-fiber MS-SPRing protection group

Related information


Local indications



Ring protection switching is suspended (disabled) as long as an Inconsistent Ring

Protection Mode alarm is present. 4-fiber MS-SPRing protection switching is notpossible.

Trouble clearing

Please refer to “Clearing Inconsistent Ring Protection Mode” (p. 3-202).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Local Squelch Map Conflict.................................................................................................................................................................................................................................


The ring node’s local squelch map contains invalid values for the source and/ordestination nodes of a ring circuit.

When a bidirectional (2-way) BLSR/MS-SPRing add, drop or through cross-connectionhas been established with an unknown NE name (TID) for the source node (A-node)and/or destination node (Z-node), then the Local Squelch Map Conflict alarm isreported.


The following tabular overview summarizes important information concerning theLocal Squelch Map Conflict alarm:

Alarm identifier SQMAP-CONFL





Minor

Alarm source 2-fiber or 4-fiber BLSR/MS-SPRing protection group

Related information


Local indications


Related information

Please also refer to the LambdaUnite® MSS User Operations Guide for a generaldescription of BLSR/MS-SPRing protection switching.

Ring circuits

A ring circuit is a provisioned path within a ring which can be carrying service orextra traffic.

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-189

A ring circuit enters a ring at one or more “source” nodes, continues on the same or ona different tributary within the ring, and is dropped from the ring at one or more“destination” nodes.

Local squelch map

Each NE internally maintains a local view of the source and destination nodes of thering circuits and the local cross connection information in its local squelch map.

The local squelch map is used by a ring node adjacent to a failed link or failed node todetermine which tributary channels between itself and the adjacent node can beprotected and which need to be squelched via the insertion of AIS.

Trouble clearing

Please refer to “Clearing Local Squelch Map Conflict” (p. 3-203).

Alarm messages Local Squelch Map Conflict

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Node ID Mismatch.................................................................................................................................................................................................................................


The node IDs in the received APS bytes (K1/K2 bytes in the SDH Multiplex SectionOverhead (MSOH) or SONET Line Overhead (LOH) respectively are inconsistent withthe ring topology data stored in the node’s ring map.

A Node ID Mismatch condition causes a ring topology discovery.


The following tabular overview summarizes important information concerning the Node

ID Mismatch alarm:

Alarm identifier NID-CONFL





Major


Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-191

Open Ring.................................................................................................................................................................................................................................


During a ring topology discovery, an open ring configuration has been detected.


The following tabular overview summarizes important information concerning the Open

Ring alarm:

Alarm identifier RNG-OPEN





Major


Related information


Local indications


Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Ring Discovery in Progress.................................................................................................................................................................................................................................


A ring topology discovery is currently in progress.

The Ring Discovery in Progress “alarm” is a temporary indication, it is to beunderstood as an information rather than as an alarm.


The following tabular overview summarizes important information concerning the Ring

Discovery in Progress alarm:

Alarm identifier RNG-DSCVY





Not alarmed


Related information


Local indications


Ring topology discovery

Please refer to “Automatic discovery of the ring topology” (p. 2-215).


BLSR/MS-SPRing protection switching is temporarily not possible.

Trouble clearing

In the normal case there are no specific trouble clearing measures required for theRing Discovery in Progress alarm, the alarm will be cleared as soon as the ringtopology discovery has finished.

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-193

If the alarm persists for longer than approximately ten minutes, please refer to“Clearing Ring Discovery in Progress ” (p. 3-205).

Alarm messages Ring Discovery in Progress

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Ring Incomplete.................................................................................................................................................................................................................................


A Ring Incomplete alarm is reported if no correct ring topology can be discovered, orif the ring discovery algorithm times out.

Incomplete ring discovery in fibre cut scenario

If a 2-fiber BLSR/MS-SPRing node is in a ring switching state due to a fiber cut and aring map re-discovery is triggered, it might not complete. In this case the alarm Ring

Incomplete is raised. The critical scenario is that the ring map re-discovery istriggered by a DCF (Data Communication Controller Function) or CTL (SystemController) reboot/power on. Nevertheless protection switching is not suspended in thiscase. The problem does not apply for a ring map re-discovery triggered by apass-through node.

Try to avoid DCF and CTL reboots if there is a Signal Fail (SF) condition for the ringnodes of the affected NE.



Incomplete alarm:

Alarm identifier RNG-INC





Major


Related information


Local indications


Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-195

Related information

Please also refer to “Automatic discovery of the ring topology” (p. 2-215).

Trouble clearing


Alarm messages Ring Incomplete

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Ring Protection Switch Suspended.................................................................................................................................................................................................................................


MS-SPRing protection switching is suspended. No further MS-SPRing protectionswitching requests will be processed.

Protection switching is suspended by a ring node if the node’s ring map is invalid orthe node does not yet have a node ID. This alarm is typically reported when a newnode is added to a ring and does not have a ring map, or if the ring map is invalid.

The Ring Protection Switch Suspended alarm will be cleared as soon as the ringnode has a valid node ID and ring map.



Protection Switch Suspended alarm:

Alarm identifier RNG-PSS





Major


Related information


Local indications


Trouble clearing

Please refer to “Clearing Ring Protection Switch Suspended ” (p. 3-207).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-197

Traffic Squelched.................................................................................................................................................................................................................................


The Traffic Squelched alarm is reported by a ring node for each channel on whichthe traffic has been squelched.


The following tabular overview summarizes important information concerning theTraffic Squelched alarm:

Alarm identifier TS





Major


Related information


Local indications


Related information

Please refer to the LambdaUnite® MSS User Operations Guide for a generaldescription of BLSR/MS-SPRing protection switching.

Misconnected traffic

Because the protection channels are shared amongst each span of the ring and maycarry extra traffic, each channel is subject to use by multiple services. With no extratraffic on the ring, under certain multiple point failures, such as those that cause theisolation of nodes, services may contend for access to the same protection channel.With extra traffic on the ring, even under single point failures, service on the workingchannels may contend for access to the same protection channel. These cases yield thepotential for misconnected traffic. Therefore, a mechanism to prevent trafficmisconnection is provided.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Prevention of traffic misconnection

A potential traffic misconnection is determined by identifying the nodes that will act asthe switching nodes for a protection switching bridge request and how the nodes areinterconnected (by means of the ring map), and by examining the traffic that will beaffected by the switch.

Traffic squelching

Squelching means replacing a potentially misconnected signal by an all-ones signal(Alarm Indication Signal, AIS). In the case of a LambdaUnite® MSS system, the trafficthat cannot be protected will be squelched by replacing the payload signal with AIS(all-ones signal).

Specifically, the traffic that is sourced or dropped at the nodes isolated from the ringby a failure is squelched. In addition, extra traffic circuits that have their sourceremoved due to preemption are squelched.

Alarm messages Traffic Squelched

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-199

The following figure provides an example of the squelching functional principle:

1. In a ring consisting of five nodes (A, B, C, D, E), a bidirectional Signal Fail (SF)condition, a “Loss of Signal” for example, occurs between the nodes E and D. ThisSF condition is protected by a ring protection switch.

2. Afterwards, a second bidirectional SF condition occurs between the nodes B and C.

The following squelching occurs:

• Node BAny traffic is squelched that

– was being transmitted towards node C with C or D as the destination node,

– was being received from node C with C or D as the source node.

• Node CAny traffic is squelched that

– was being transmitted towards node B with A, B or E as the destination node,

– was being received from node B with A, B or E as the source node.

• Node D

Working channels

Protection channels

E

A B

C

D

X

X

X

X

1

2


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Any traffic is squelched that

– was being transmitted towards node E with A, B or E as the destination node,

– was being received from node E with A, B or E as the source node.

• Node EAny traffic is squelched that

– was being transmitted towards node D with C or D as the destination node,

– was being received from node D with C or D as the source node.

Trouble clearing



.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-201

Unknown Ring Type.................................................................................................................................................................................................................................


During an automatic discovery of the ring type, the ring type could not be determined.


The following tabular overview summarizes important information concerning theUnknown Ring Type alarm:

Alarm identifier RNG-URT





Not alarmed


Related information


Local indications


Related information

Please refer to “Automatic discovery of the ring type” (p. 2-220).


BLSR/MS-SPRing protection switching is not possible.

Trouble clearing


Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Synchronisation alarms

Overview.................................................................................................................................................................................................................................

Purpose

In the following, alarm descriptions are given for the alarms related to the networkelement synchronisation that can be reported by the LambdaUnite® MSS networkelements.

Contents

Circuit Pack Clock Failure 2-204

Loss of Synchronisation 2-205

NE Clock Failure 2-206

Protection Clock Input Fail 2-207

T4 quality unsufficient 2-208

Timing Reference Failure 2-209

Worker Clock Input Fail 2-210

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-203

Circuit Pack Clock Failure.................................................................................................................................................................................................................................


The circuit pack reporting the alarm is either unable to process the internal systemclock signals or is not receiving any clock signals from the system timing function.

Please note that if the Circuit Pack Clock Failure condition is present for allcircuit packs of the network element, an NE Clock Failure alarm (cf. “NE ClockFailure” (p. 2-206)) will be reported for the complete system instead of a separateCircuit Pack Clock Failure alarm for each circuit pack.

Note

In the case of an XC circuit pack, a Circuit Pack Clock Failure condition causes aCircuit Pack Failure alarm.


The following tabular overview summarizes important information concerning theCircuit Pack Clock Failure alarm:

Alarm identifier EQPT






SA Critical

NSA Minor


Related information


Local indications


Trouble clearing

Please refer to “Clearing Circuit Pack Clock Failure” (p. 3-211).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Loss of Synchronisation.................................................................................................................................................................................................................................


The internal system clock generator is not synchronised externally because all assignedtiming references have failed. Therefore, the internal timing generator hasautonomously entered the holdover mode.



of Synchronisation alarm:

Alarm identifier SYNCLOSS

ASAP type System Timing

Alarm category Communication (Synchronisation)

Effect-on-service – (no effect-on-service classification possible)


Major

Alarm source System

Notes:

1. The alarm may be service-affecting (SA) or not service-affecting (NSA). However, theeffect-on-service is not predictable.

Related information


Local indications


Related information

Please also refer to the LambdaUnite® MSS User Operations Guide for informationabout timing provisioning.

Trouble clearing

Please refer to “Clearing Loss of Synchronisation” (p. 3-213).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-205

NE Clock Failure.................................................................................................................................................................................................................................


A Circuit Pack Clock Failure condition is present for all circuit packs of thenetwork element.

Note

In the case of an XC circuit pack, a Circuit Pack Clock Failure condition causes aCircuit Pack Failure alarm.


The following tabular overview summarizes important information concerning the NE

Clock Failure alarm:

Alarm identifier SYNCCLK





Critical

Alarm source System

Related information


Local indications

The red fault LED on the faceplate of the cross-connect and timing unit(s) isconstantly lit.

Trouble clearing

Please refer to “Clearing NE Clock Failure” (p. 3-214).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Protection Clock Input Fail.................................................................................................................................................................................................................................


There is either no clock signal available at the protection timing reference input of therespective circuit pack, or the available clock signal is not suitable for synchronisation.


The following tabular overview summarizes important information concerning theProtection Clock Input Fail alarm:

Alarm identifier CSDPF





Minor


Related information


Local indications


Clock and synchronisation distribution

The clock and synchronisation distribution function (CSD function, located on eachcircuit pack) is supplied with a working and a protection timing reference from thesystem timing function (located on the working or protection cross-connect and timingunit, respectively). In addition, an internal oscillator is available on each circuit packwhich serves as the timing reference when both timing references from the systemtiming function are unavailable or not suitable for synchronisation.

Trouble clearing

Please refer to “Clearing Protection Clock Input Fail” (p. 3-215).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-207

T4 quality unsufficient.................................................................................................................................................................................................................................


The quality of the relevant timing reference for the external timing output (T4 timingoutput) is insufficient. As a consequence the external timing output has been switchedoff (“squelched”).


The following tabular overview summarizes important information concerning the T4

quality unsufficient alarm:

Alarm identifier SYNCT4OUT





Major

Alarm source External timing output

Notes:


Related information


Local indications


Trouble clearing

Please refer to “Clearing T4 quality unsufficient” (p. 3-217).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Timing Reference Failure.................................................................................................................................................................................................................................


There is no clock source connected to an external or line timing input that is assignedas a timing reference, or the signal connected is not suitable for synchronisation.


The following tabular overview summarizes important information concerning theTiming Reference Failure alarm:

Alarm identifier SYNCRF





Major

Alarm source External or line timing reference

Notes:


Related information


Local indications


Trouble clearing

Please refer to “Clearing Timing Reference Failure” (p. 3-219).

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-209

Worker Clock Input Fail.................................................................................................................................................................................................................................


There is either no clock signal available at the working timing reference input of therespective circuit pack, or the available clock signal is not suitable for synchronisation.


The following tabular overview summarizes important information concerning theWorker Clock Input Fail alarm:

Alarm identifier CSDWF





Minor


Related information


Local indications


Clock and synchronisation distribution

The clock and synchronisation distribution function (CSD function, located on eachcircuit pack) receives a working and a protection timing reference from the systemtiming function (located on the working or protection cross-connect and timing unit,respectively). In addition, an internal oscillator is available on each circuit pack whichserves as the timing reference when both timing references from the system timingfunction are unavailable or not suitable for synchronisation.

Trouble clearing

Please refer to “Clearing Worker Clock Input Fail” (p. 3-222).

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Additional alarm-related information

Overview.................................................................................................................................................................................................................................

Purpose

This chapter provides additional information for network element alarms that might beuseful to understand the meaning of alarms and to locate their origin.

Contents

BLSR/MS-SPRing management information 2-212

Automatic discovery of the ring topology 2-215

Automatic node ID allocation 2-219

Automatic discovery of the ring type 2-220

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-211

BLSR/MS-SPRing management information.................................................................................................................................................................................................................................

Terms and definitions

Please refer to the LambdaUnite® MSS User Operations Guide for a generaldescription of BLSR/MS-SPRing protection switching.

Ring node

A BLSR/MS-SPRing consists of at least two and at most 16 nodes (cf. “Maximumnumber of ring nodes” (p. 2-219)).

Each ring node is characterized by the NE name (TID), the protection group AID, theEast (E) and West (W) interface port information, the node ID, and the associated ringID.

Multiple ring nodes from the same NE on the same ring are not allowed. If such asituation occurs a Duplicate Ring Node alarm will be generated.

NE name (TID)

The NE name, also referred to as the NE’s target identifier (TID), is an alphanumericstring of up to 20 characters, used to uniquely identify a network element within thenetwork.

Protection group AID

The protection group AID is the port AID associated with a port protection group. It isunique within an NE and used to distinguish the different port protection groups. Eachring node in a network is uniquely identified by the NE name (TID) in connection withthe protection group AID.

East/West interface ports

The east (E) and west (W) interface port information is required to determine thedirectionality of a link within a ring circuit.

Node ID

Each node within a ring is automatically allocated a node identifier (node ID) which isused to uniquely identify a ring node within a ring. The node ID value may range from0 to 15. Please refer to “Automatic node ID allocation” (p. 2-219) for further details.

Ring ID

To uniquely identify rings within a network, each ring can be assigned a ring identifier(ring ID, an alphanumeric string of up to 15 characters) when a port protection groupis configured for a ring node. All ring nodes in the same ring have the same ring ID.

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Link ID

To support ring protection switching and the display of ring configuration informationon graphical user interfaces, each ring node maintains the following information foreach link to a neighbouring ring node:

• the local NE name (TID), port ID and the east (E) and west (W) interface portinformation of the local end of the link,

• the ring neighbour’s NE name (TID), port ID and the east (E) and west (W)interface port information of the remote end of the link.

The link ID information is required to discover a given ring topology. The link IDinformation is discovered upon initial link startup and is modified dynamically whenchanges to the link ID information occur (for example, when the name of aneighbouring NE is changed, or a node is added to or removed from a ring). After thelinks are discovered, the sequence of links around the ring is determined. Thisinformation is used to assign node IDs to each node of the ring and to create a ringmap. Please also refer to “Automatic discovery of the ring topology” (p. 2-215).

Link map

The link map contains a list of link IDs, starting with the local node’s east link andordered by their sequence in the ring.

Ring map

Each NE internally maintains a ring map in its non-volatile memory (NVM). The ringmap serves to identify the relative position of all nodes within a ring.

The ring map contains the ring ID assigned to the ring and a list of all ring nodes,identified by their node IDs and ordered by their sequence of occurrence in the ring.Because the list does not necessarily start with the local node, the ring map alsocontains the node ID of the local node, and because the ring protection switchingsignalling requires node IDs instead of TIDs, the ring map additionally contains amapping of TIDs to node IDs.

Please also refer to “Automatic discovery of the ring topology” (p. 2-215).

Ring circuits

A ring circuit is a provisioned path within a ring which can be carrying service orextra traffic.

A ring circuit enters a ring at one or more “source” nodes, continues on the same or ona different tributary within the ring, and is dropped from the ring at one or more“destination” nodes.

Local squelch map

Each NE internally maintains a local view of the source and destination nodes of thering circuits and the local cross connection information in its local squelch map.

Alarm messages BLSR/MS-SPRing management information

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-213

The local squelch map is used by a ring node adjacent to a failed link or failed node todetermine which tributary channels between itself and the adjacent node can beprotected and which need to be squelched via the insertion of AU-AIS.

Alarm messages BLSR/MS-SPRing management information

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Automatic discovery of the ring topology.................................................................................................................................................................................................................................

Introduction

As a prerequisite for BLSR/MS-SPRing protection switching the topology of the ringmust be known at each ring node. LambdaUnite® MSS network elements have aproprietary algorithm implemented to discover the ring topology automatically.

Closed ring

A closed ring consists of network elements which are all equipped and cabled withoptical interface circuit packs for both the east (E) and west (W) directions.

Example of a closed ring:

Open ring

An open ring is a linear configuration of network elements where the two end nodesare equipped and/or cabled with optical interface circuit packs for only one direction.

Example of an open ring:

NE2

NE3

NE4

E

W

E

W

E W

E

W

E

W

NE1

NE5

NE2

NE3

NE4

E

W

E

W

E W

E

W

E

W

NE1

NE5

NE2

NE3

NE4

E

W

E

W

E W

E

W

E

W

NE1

NE5

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-215

In a 2-fiber BLSR/MS-SPRing, an open ring configuration will automatically bedetected by the LambdaUnite® MSS network elements, and an Open Ring alarm willbe reported in that case.

Ring topology data

Each ring node inserts or appends the following ring topology data (ring data) to amessage which it sends or forwards over a DCN association to its neighbour on thering:

• Its own NSAP address and TID.The system identifier in the NSAP address is also used for automatic allocation ofthe node ID (cf. “Automatic node ID allocation” (p. 2-219)).

• The interface port identification and the east/west (E/W) directionality informationof the link to its neighbour.

This way, at each ring node sufficient information is available to form a ring maprepresenting the ring topology.

Trigger for the topology discovery

The discovery of the ring topology is initiated by a ring node when the ring node isfirst created by the provisioning of an BLSR/MS-SPRing port protection group, orwhen the DCC controller on the Controller (CTL) is re-initialized.

Discovery of a closed ring topology

The ring topology data (ring data) “circles” once around the ring until the node thatinitiated the ring topology discovery again receives a corresponding message. The

Alarm messages Automatic discovery of the ring topology

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

following figure shows the ring topology discovery for a ring of five nodes as anexample.

NE2

NE3

NE4

NE5

Step 1

E

W

E

W

E W

E

W

E

W

Ring data (1)

Ringdata (1)

NE1 NE2

NE3

NE4

NE5

Step 2

E

W

E

W

E W

E

W

E

W Ringdata (1,2)

Ringdata (1,5)

NE1 NE2

NE3

NE4

NE5

Step 3

E

W

E

W

E W

E

W

E

W

Ringdata (1,2,3)

Ringdata (1,5,4)

NE1 NE2

NE3

NE4

NE5

Step 5

E

W

E

W

E W

E

W

E

W

Ring(1,2,3,4,5)

data

Ring(1,5,4,3,2)

data

NE1


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-217

Related alarms

These alarms are related to the ring topology discovery:

• Ring Discovery in Progress

• Ring Incomplete

• Open Ring


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Automatic node ID allocation.................................................................................................................................................................................................................................

Node identifier (node ID)

Each node within a ring is automatically allocated a node identifier (node ID). Thenode ID is a 4-bit address used in the BLSR/MS-SPRing protection switching protocolto uniquely identify a ring node within a ring.

Principle of node ID allocation

All nodes of a ring are ordered according to their system identifier, the IEEE 802.3MAC address in the “SYSTEM” field of the NSAP address. For this purpose, the ringnodes distribute their system identifier values over the ring to every other node on thering.

The ring node with the lowest system identifier value is allocated a node ID of “0”.The remaining node IDs are allocated in ascending order in accordance with the valueof their system identifier. The following table shows an example for a ring of fivenodes.

NE name (TID) System Identifier (in hexadecimal representa-tion)

Node ID

NE3 00 00 00 01 20 40 0

NE1 00 00 00 45 A3 21 1

NE4 00 00 00 80 0B 54 2

NE5 00 00 03 76 D0 88 3

NE2 00 00 09 9C 99 32 4

Re-allocation of node IDs

Node IDs may change in value, they will be re-allocated when:

• a node is added to the ring,

• a node is deleted from the ring, or

• the Controller (CTL) is re-initialized.

Maximum number of ring nodes

As the node ID is a 4-bit address, its value may vary from 0 to 15, thus the maximumnumber of nodes in a ring is restricted to 16.

Alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-219

Automatic discovery of the ring type.................................................................................................................................................................................................................................

Introduction

In parallel to the discovery of the ring topology (cf “Automatic discovery of the ringtopology” (p. 2-215)), a discovery of the ring type takes place. This means that thetype of network elements involved in the ring is evaluated. The discovery of the ringtype also includes the evaluation of the signal level (port type) and the ring protectionmode used.

Ring type discovery

LambdaUnite® MSS network elements have a proprietary algorithm implemented toautomatically discover the ring type of other nodes in the ring. The discovery of thering type is required to determine the compatibility of the nodes in the ring and toderive information specific to ring interworking.

The information exchanged during the discovery of the ring type includes:

• NE typeNE types that are “known” to LambdaUnite® MSS network elements are:

– FT-2000 OC-48 Lightwave System – Add/Drop Ring Terminal,

– WaveStar® ADM 16/1,

– WaveStar® BandWidth Manager,

– WaveStar® TDM 2.5G (OC-48 2F),

– WaveStar® TDM 10G (OC-192 2F),

– WaveStar® TDM 10G (OC-192 4F),

– WaveStar® TDM 10G (STM-64),

– Metropolis® ADM (Universal shelf),

– Metropolis® ADM (Compact shelf),

– LambdaUnite® MultiService Switch (MSS).

• Port typePossible port types are STM-16, STM-64, STM-256, OC-48, OC-192, or OC-768.

• Ring protection modePossible BLSR/MS-SPRing ring protection modes are “ring loopback” or“shortened path” (transoceanic protocol).

Ring types

Based on the information exchanged during the discovery of the ring type, thefollowing ring types can be determined by a LambdaUnite® MSS ring node:

• Lucent Technologies SONET ring

– NE type

Alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

WaveStar® BandWidth Manager, WaveStar® TDM 2.5G (OC-48 2F),WaveStar® TDM 10G (OC-192 2F) or LambdaUnite® MSS.

– Port typeOC-48, OC-192, or OC-768.

– Ring protection modeBLSR – “ring loopback”

• Lucent Technologies SDH ring

– NE typeWaveStar® BandWidth Manager, WaveStar® TDM 10G (STM-64), Metropolis®

DMX Access Multiplexer or LambdaUnite® MSS.

– Port typeSTM-16, STM-64, or STM-256.

– Ring protection modeMS-SPRing – “ring loopback” or “shortened path” (transoceanic protocol).

• Unknown ring typeA ring is considered to be of an unknown ring type if the combinations of NE type,port type and ring protection mode are not in one of the above categories, or if theinformation for discovering the ring type is not available after a predefined timeinterval (timeout).

Alarm messages Automatic discovery of the ring type

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


2-221

3 3Trouble clearing

Overview.................................................................................................................................................................................................................................

Purpose

The present chapter provides step-by-step procedures to locate and clear networkelement alarms.

Technical support


Contents

DCN alarms 3-5

Clearing DCC MS/Line failure 3-6

Clearing Partitioned Area Repair 3-8

Clearing Protocol Version Mismatch 3-9

Clearing DCC RS/Section failure 3-11

DS3 alarms 3-13

Clearing DS3 AIS 3-14

Clearing DS3 AIS egress 3-15

Clearing DS3 Application Mismatch in 3-16

Clearing DS3 LOF egress 3-17

Clearing DS3 Loss of Frame 3-19

Clearing DS3 RAI egress 3-20

Clearing DS3 RAI in 3-21

Equipment alarms 3-22

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-1

Clearing CICTL Comm Failure 3-24

Clearing CICTL Failure 3-28

Clearing CICTL not Present 3-29

Clearing Circuit Pack Comm Failure 3-30

Clearing Circuit Pack not Present 3-46

Clearing Circuit Pack Type Mismatch 3-47

Clearing Circuit Pack Failure 3-49

Clearing Comm Channel Failure 3-50

Clearing CTL Comm Failure 3-58

Clearing Duplex Control not Present 3-60

Clearing ECI Comm Failure 3-61

Clearing ECI Mismatch Failure 3-65

Clearing ECI not Present 3-68

Clearing Fan Failure 3-69

Clearing Fan Unit Comm Failure 3-72

Clearing Fan Unit Failure 3-76

Clearing Fan Unit not Present 3-80

Clearing Fan Voltage Feed A/B Failure 3-82

Clearing IDE Flash Card Access Fail 3-87

Clearing NVM Shortage 3-89

Clearing ONI Failure on protecting CTL 3-90

Clearing ONI Failure on working CTL 3-93

Clearing Optical Module Fail 3-96

Clearing Optical Module not Present 3-97

Clearing Optical Module not supported 3-98

Clearing Optical Module Type Mismatch 3-99

Clearing Power Interface not Present 3-100

Clearing Power Interface Read Failure 3-101

Clearing System Power Failure 3-102

Clearing TI not Present 3-105

Clearing TXI Failure 3-106

Clearing Unit Cooling Degraded 3-109

Trouble clearing Overview

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Unit Temperature too High 3-112

Clearing User Panel Comm Failure 3-115

Clearing User Panel not Present 3-119

Ethernet alarms 3-120

Clearing Loss of Alignment 3-121

Clearing max number of VLAN instances reached 3-122

Clearing Partial Transport Capacity Loss 3-123

Clearing Server Signal Fail (VCGSSF) 3-124

Clearing Sink End Failure of Protocol 3-125

Clearing Source End Failure of Protocol 3-126

Clearing Total Transport Capacity Loss 3-127

Linear protection switching alarms 3-128

Clearing Far End Signal Fail 3-129

Clearing primary section Mismatch 3-132

Clearing Prot. Arch. Mismatch 3-134

Clearing Prot. Arch. Mode Mismatch 3-135

Clearing Prot. Arch. Operation Mismatch 3-136

Clearing Prot. Switch Byte Inappropriate 3-137

Clearing Prot. Switch Byte Unacceptable 3-138

Clearing Switch Channel Mismatch 3-142

Path-related transmission alarms 3-143

Clearing Alarm Indication Signal (AIS-P) 3-144

Clearing Path Switch Denial 3-145

Clearing Remote Defect Indication (RFI-P) 3-146

Clearing Remote Defect Indication (THPRDI) 3-147

Clearing Server Signal Fail (SSF-P) 3-148

Clearing Server Signal Fail (THPSSF) 3-149

Clearing Trace Identifier Mismatch (THPTIM) 3-150

Clearing Trace Identifier Mismatch (TIM-P) 3-151

Clearing Unequipped (THPUNEQ) 3-152

Clearing Unequipped (UNEQ-P) 3-153

Port-related transmision alarms 3-154


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-3

Clearing Alarm Indication Signal (AIS-L) 3-155

Clearing Excessive Bit Error Ratio 3-156

Clearing Loss of Frame 3-163

Clearing Loss of Frame transp ch egress 3-166

Clearing Loss of Signal 3-167

Clearing OCh Loss of Frame 3-174

Clearing Post DCM Signal Loss 3-175

Clearing Pre DCM Signal Loss 3-176

Clearing Remote Defect Indication (RFI-L) 3-177

Clearing Server Signal Fail (MSSSF) 3-178

Clearing Server Signal Fail Transparent Ch 3-179

Clearing Trace Identifier Mismatch (RSTIM) 3-180

Clearing Trace Identifier Mismatch egress (TIM-T-EGR) 3-181

Clearing WTU3 Loss of Frame 3-183

Ring protection switching alarms 3-184

Clearing Default K-bytes 3-185

Clearing Duplicate Ring Node 3-190

Clearing Extra Traffic Preempted 3-192

Clearing Improper APS Codes 3-193

Clearing Inconsistent APS Codes 3-197

Clearing Inconsistent Ring Protection Mode 3-202

Clearing Local Squelch Map Conflict 3-203

Clearing Ring Discovery in Progress 3-205

Clearing Ring Protection Switch Suspended 3-207

Synchronisation 3-210

Clearing Circuit Pack Clock Failure 3-211

Clearing Loss of Synchronisation 3-213

Clearing NE Clock Failure 3-214

Clearing Protection Clock Input Fail 3-215

Clearing T4 quality unsufficient 3-217

Clearing Timing Reference Failure 3-219

Clearing Worker Clock Input Fail 3-222


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

DCN alarms

Overview.................................................................................................................................................................................................................................

Purpose

This section contains trouble clearing procedures for DCN alarms.

Contents

Clearing DCC MS/Line failure 3-6

Clearing Partitioned Area Repair 3-8

Clearing Protocol Version Mismatch 3-9

Clearing DCC RS/Section failure 3-11

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-5

Clearing DCC MS/Line failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an DCC MS/Line failure alarm.

Related information

Please also refer to

• the corresponding alarm description → “DCC MS/Line failure” (p. 2-13)

• the LambdaUnite® MultiService Switch (MSS) User Operations Guide.

Before you begin

You or a service technician must be on-site at the NE to clear an DCC MS/Line

failure alarm.

Prior to performing the following trouble clearing procedure, you must:

• have a valid user login and password for the WaveStar® CIT, and

• have established a WaveStar® CIT connection to the alarm-reporting NE.

Required equipment

Make sure that the following equipment is available:

• WaveStar® CIT

Trouble clearing procedure

Proceed as follows to clear an DCC MS/Line failure alarm:

.................................................................................................................................................................................................

1 Make sure that the MS/Line DCC is enabled at both ends of the DCC link.

.................................................................................................................................................................................................

2 At the WaveStar® CIT, refresh the NE Alarm List, and check if the alarm has cleared.

If then

the alarm has cleared Stop! You have completed this procedure.

the alarm persists proceed with the next step.

.................................................................................................................................................................................................

3 Make sure that the LAPD mode is set to AITS at both ends of the DCC link.

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

5 Make sure that the LAPD role (USER-SIDE, NETWORK-SIDE) is set to differentvalues at both ends of the DCC link.

.................................................................................................................................................................................................


If then


the alarm persists please refer to Appendix A, “Maintenance servicesand technical support”.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing DCC MS/Line failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-7

Clearing Partitioned Area Repair.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Partitioned Area Repair alarm.

Related information

Please also refer to the corresponding alarm description → “Partitioned Area Repair”(p. 2-16).

Before you begin

Required equipment

The following equipment is required to complete this procedure:

• WaveStar® CIT to check the alarm state of the network.


Proceed as follows to clear a Partitioned Area Repair alarm:

.................................................................................................................................................................................................

1 Locate and clear the failure in the network that caused the partition repair.

Partitioning of an area The following situations may lead to the partitioning of anarea:

• The design of the DCN is not correct (the DCN has not a ring or meshedstructure within the area for example). The LambdaUnite® MSS UserOperations Guide contains rules and guidelines for the DCN design.

• The provisioning of the DCN is not correct (a DCC may be unintentionallydisabled for example).

• A node failure or fiber cut. Such failures would result in a DCC failure alarm(DCC RS/Section failure or DCC MS/Line failure) to be reported, possiblyin connection with Loss of Signal or Loss of Frame for example.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Protocol Version Mismatch.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Protocol Version Mismatch alarm.

Related information

Please also refer to the corresponding alarm description:

• “Protocol Version Mismatch” (p. 2-18)

Before you begin




Required privilege

You must have at least a privilege code of S4.

Required equipment

The following equipment is required:

• WaveStar® CIT


Proceed as follows to clear a Protocol Version Mismatch alarm:

.................................................................................................................................................................................................

1 Perform a software download at the neighboring NE to adjust the supported protocolversions at both NEs.

Please refer to the LambdaUnite® MSS User Operations Guide for information how toperform a software download for upgrade purposes.

.................................................................................................................................................................................................


If then



Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-9

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Protocol Version Mismatch

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing DCC RS/Section failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an DCC RS/Section failure alarm.

Related information


• the corresponding alarm description → “DCC RS/Section failure” (p. 2-14)


Before you begin

You or a service technician must be on-site at the NE to clear an DCC RS/Section

failure alarm.




Required equipment


• WaveStar® CIT


Proceed as follows to clear an DCC RS/Section failure alarm:

.................................................................................................................................................................................................

1 Make sure that the RS-DCC (Section DCC) is enabled at both ends of the DCC link.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

3 Make sure that the LAPD mode is set to AITS at both ends of the DCC link.

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-11

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

5 Make sure that the LAPD role (USER-SIDE, NETWORK-SIDE) is set to differentvalues at both ends of the DCC link.

.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing DCC RS/Section failure

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

DS3 alarms

Overview.................................................................................................................................................................................................................................

Purpose

This section contains trouble clearing procedures for DS3 alarms.

Contents

Clearing DS3 AIS 3-14

Clearing DS3 AIS egress 3-15

Clearing DS3 Application Mismatch in 3-16

Clearing DS3 LOF egress 3-17

Clearing DS3 Loss of Frame 3-19

Clearing DS3 RAI egress 3-20

Clearing DS3 RAI in 3-21

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-13

Clearing DS3 AIS.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a DS3 AIS alarm.

Related information

Please also refer to the corresponding alarm description → “DS3 AIS” (p. 2-23).

Instructions

Proceed as follows to clear a DS3 AIS alarm:

.................................................................................................................................................................................................

1 Analyze the alarm state of the upstream DS3 equipment and take appropriate measures.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing DS3 AIS egress.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a DS3 AIS egress alarm.

Related information

Please also refer to the corresponding alarm description → “DS3 AIS egress” (p. 2-24).

Instructions

Proceed as follows to clear a DS3 AIS egress alarm:

.................................................................................................................................................................................................

1 Refer to the following figure for reference:

.................................................................................................................................................................................................

2 If then

a Server Signal Fail alarm isreported for the associatedSDH/SONET port unit (detectedat a non-intrusive monitoring(NIM) point)

analyze the alarm state of the network elements inthe upstream direction of the STS-1 path, and takeappropriate measures.

alarms are reported for the STS-1path termination function (PTF),for example Payload Mismatch(THPPLM), or Unequipped(THPUNEQ).

clear these alarms first.

E N D O F S T E P S........................................................................................................................................................................................................................

DS3 STS-1PTF

NIM

EP51XC

Port unit

L/P

L/P

DS3 Line

DS3 path

STS-1 path

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-15

Clearing DS3 Application Mismatch in.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a DS3 Application Mismatch in alarm.

Related information

Please also refer to the corresponding alarm description → “DS3 Application Mismatchin” (p. 2-25).

Instructions

Proceed as follows to clear a DS3 Application Mismatch in alarm:

.................................................................................................................................................................................................

1 If then

the M23 format is the desiredDS3 signal format

change the provisioning accordingly.

the current provisioning (C-bitparity format) is correct

make sure to provide a DS3 C-bit parity formattedsignal.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing DS3 LOF egress.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a DS3 LOF egress alarm.

Related information

Please also refer to the corresponding alarm description → “DS3 LOF egress”(p. 2-27).

Instructions

Proceed as follows to clear a DS3 LOF egress alarm:

.................................................................................................................................................................................................

1 If then

the DS3 unframed format is thedesired DS3 signal format


the current provisioning iscorrect

make sure to provide a DS3 signal according to thecurrent provisioning (C-bit parity format, or DS3M23 format).

.................................................................................................................................................................................................


.................................................................................................................................................................................................

3 Check if alarms are reported for the STS-1 path termination function (PTF), forexample Degraded Signal (THPDEG), or Excessive Bit Error Ratio (THPEXC),and clear these alarms first.

DS3 STS-1PTF

NIM

EP51XC

Port unit

L/P

L/P

DS3 Line

DS3 path

STS-1 path

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-17

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

5 Check if alarms are reported for the associated SDH/SONET port unit (detected at anon-intrusive monitoring (NIM) point), for example Server Signal Fail (SSF-P),and clear these alarms first.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

7 Check the correct structure of the DS3 frame in the egress direction by performing across-connection loopback for the associated STS-1 tributary.

.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing DS3 LOF egress

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing DS3 Loss of Frame.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a DS3 Loss of Frame alarm.

Related information

Please also refer to the corresponding alarm description → “DS3 Loss of Frame”(p. 2-28).

Instructions

Proceed as follows to clear a DS3 Loss of Frame alarm:

.................................................................................................................................................................................................

1 If then

the DS3 unframed format is thedesired DS3 signal format


the current provisioning iscorrect

make sure to provide a DS3 signal according to thecurrent provisioning (C-bit parity format, or DS3M23 format).

.................................................................................................................................................................................................

2 Check the correct functioning of the EP51 port unit by performing a DS3 far-sidefacility loopback.

.................................................................................................................................................................................................


If then


the alarm persists analyze the alarm state of the upstream DS3 pathterminating equipment and take appropriatemeasures.

In the upstream direction means towards thefar-end DS3 path termination in the direction overthe DS3 path.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-19

Clearing DS3 RAI egress.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a DS3 RAI egress alarm.

Related information

Please also refer to the corresponding alarm description → “DS3 RAI egress” (p. 2-30).

Instructions

Proceed as follows to clear a DS3 RAI egress alarm:

.................................................................................................................................................................................................

1 Analyze the alarm state of the upstream DS3 path terminating equipment and takeappropriate measures.

In the upstream direction means towards the far-end DS3 path termination in thedirection over the STS-1 path.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing DS3 RAI in.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a DS3 RAI in alarm.

Related information

Please also refer to the corresponding alarm description → “DS3 RAI in” (p. 2-32).

Instructions

Proceed as follows to clear a DS3 RAI in alarm:

.................................................................................................................................................................................................

1 Analyze the alarm state of the upstream DS3 path terminating equipment and takeappropriate measures.

In the upstream direction means towards the far-end DS3 path termination in thedirection over the DS3 path.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-21

Equipment alarms

Overview.................................................................................................................................................................................................................................

Purpose

This section contains trouble clearing procedures for equipment alarms.

Contents

Clearing CICTL Comm Failure 3-24

Clearing CICTL Failure 3-28

Clearing CICTL not Present 3-29

Clearing Circuit Pack Comm Failure 3-30

Clearing Circuit Pack not Present 3-46

Clearing Circuit Pack Type Mismatch 3-47

Clearing Circuit Pack Failure 3-49

Clearing Comm Channel Failure 3-50

Clearing CTL Comm Failure 3-58

Clearing Duplex Control not Present 3-60

Clearing ECI Comm Failure 3-61

Clearing ECI Mismatch Failure 3-65

Clearing ECI not Present 3-68

Clearing Fan Failure 3-69

Clearing Fan Unit Comm Failure 3-72

Clearing Fan Unit Failure 3-76

Clearing Fan Unit not Present 3-80

Clearing Fan Voltage Feed A/B Failure 3-82

Clearing IDE Flash Card Access Fail 3-87

Clearing NVM Shortage 3-89

Clearing ONI Failure on protecting CTL 3-90

Clearing ONI Failure on working CTL 3-93

Clearing Optical Module Fail 3-96

Clearing Optical Module not Present 3-97

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Optical Module not supported 3-98

Clearing Optical Module Type Mismatch 3-99

Clearing Power Interface not Present 3-100

Clearing Power Interface Read Failure 3-101

Clearing System Power Failure 3-102

Clearing TI not Present 3-105

Clearing TXI Failure 3-106

Clearing Unit Cooling Degraded 3-109

Clearing Unit Temperature too High 3-112

Clearing User Panel Comm Failure 3-115

Clearing User Panel not Present 3-119


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-23

Clearing CICTL Comm Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a CICTL Comm Failure alarm.

Related information

Please also refer to the corresponding alarm description → “CICTL Comm Failure”(p. 2-42).

Before you begin

You or a service technician must be on-site at the NE to clear a CICTL Comm Failure

alarm.




Required equipment


• WaveStar® CIT

• A replacement CI-CTL (Connection Interface of the Controller)


Proceed as follows to clear a CICTL Comm Failure alarm:

.................................................................................................................................................................................................

1 At the CI-CTL and at the fan unit, check the connectors of the fan unit control cable.

If then

both connectors are connectedproperly

continue with Step 4.

any of the connectors (at theCI-CTL or at the fan unit) is notproperly connected

continue with the next step.

.................................................................................................................................................................................................

2 Complete these steps to connect the respective connector(s) properly:

1. Slightly pull out the Controller (CTL).

2. Connect the connector(s) properly.

3. Re-insert the CTL, and wait for the system to re-initialize.

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Important! Pulling-out and re-inserting the CTL affects

• MS/Line performance monitoring, and

• Automatic Protection Switching (APS) on MS/Line level

Automatic Protection Switching (APS) on MS/Line level includes (depending onthe interface standard):

• SDH: Multiplex Section Protection (MSP) and MS-SPRing

• SONET: Line Protection and BLSR

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

4 Slightly pull out the Controller (CTL).

.................................................................................................................................................................................................

5 Replace the fan unit control cable, and connect the new cable properly at the CI-CTLand at the fan unit.

.................................................................................................................................................................................................

6 Re-insert the CTL, and wait for the system to re-initialize.







.................................................................................................................................................................................................


If then



Trouble clearing Clearing CICTL Comm Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-25

.................................................................................................................................................................................................


.................................................................................................................................................................................................

9 Disconnect the fan unit control cable at the CI-CTL.

.................................................................................................................................................................................................

10 Replace the CI-CTL.

.................................................................................................................................................................................................

11 Connect the fan unit control cable at the CI-CTL.

.................................................................................................................................................................................................








.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................

15 Replace the fan unit.

Reference: Please refer to:

• “Replacing the fan unit” (p. 4-16)

.................................................................................................................................................................................................



.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005







.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-27

Clearing CICTL Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a CICTL Failure alarm.

Related information

Please also refer to the corresponding alarm description → “CICTL Failure” (p. 2-43).

Before you begin

You or a service technician must be on-site at the NE to clear a CICTL Failure alarm.

Perform the following trouble clearing procedure from the rear side of the shelf.


Proceed as follows to clear a Power Interface not Present alarm:

.................................................................................................................................................................................................


E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing CICTL not Present.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a CICTL not Present alarm.

Related information

Please also refer to the corresponding alarm description → “CICTL not Present”(p. 2-44).

Before you begin

You or a service technician must be on-site at the NE to clear a CICTL not Present

alarm.

Required equipment


• A replacement Controller (CTL)


Proceed as follows to clear a CICTL not Present alarm:

.................................................................................................................................................................................................

1 Check if the CI-CTL (Connection Interface of the Controller) is plugged in slot 51 onthe rear side of the shelf.

If then

the CI-CTL is plugged replace the CTL.

Reference:

Please refer to:

• “Replacing the Controller (CTL)” (p. 4-62)

the CI-CTL is not plugged insert the CI-CTL.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-29

Clearing Circuit Pack Comm Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Circuit Pack Comm Failure alarm.

Related information

Please also refer to the corresponding alarm description → “Circuit Pack CommFailure” (p. 2-46).

Before you begin

You or a service technician should be on-site at the NE to clear a Circuit Pack Comm

Failure alarm.




Required equipment


• WaveStar® CIT

• Eventually, a replacement circuit pack may be required.This may be either a Controller (CTL/-, CTL/2), a port unit (OP, EP, or GE1), orone or two cross-connect and timing units (XC160, XC320, XC640).

Distinction between simplex control and duplex control mode

The appropriate trouble clearing procedure depends on the network element’s controlsystem configuration, i.e. whether CTL equipment protection is provisioned (duplexcontrol mode) or not (simplex control mode). Depending on the control mode, pleaserefer to:

• “Trouble clearing procedure in simplex control mode” (p. 3-31)

• “Trouble clearing procedure in duplex control mode” (p. 3-36)

Important! Please read the appropriate trouble clearing procedure completelybefore you begin.

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Trouble clearing procedure in simplex control mode

Proceed as follows to clear a Circuit Pack Comm Failure alarm:

.................................................................................................................................................................................................

1If the Controller (CTL) isinstalled in

then

the worker slot (slot 11) continue with Step 4.

the protection slot (slot 31) if the circuit pack reporting the alarm has just beeninstalled for the first time, continue with the nextstep. Otherwise, continue with Step 4.

.................................................................................................................................................................................................

2 Remove the Controller from the protection slot, and insert it into the worker slot.

Reference: For information on how to replace the Controller (CTL) whilepreserving the present NE database, please refer to “Replacing the Controller(CTL)” (p. 4-62).

.................................................................................................................................................................................................


If then



Trouble clearing Clearing Circuit Pack Comm Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-31

.................................................................................................................................................................................................


Legend:

CTL The Controller.

Port unit, activeXC, standby XC

The circuit pack reporting the Circuit Pack Comm Failure alarm.This may be either a port unit (OP, EP, or GE1) or the active orstandby cross-connect and timing unit (XC160, XC320, XC640).

.................................................................................................................................................................................................

5 Take a note which cross-connect and timing unit (XC) is currently the active unit, andwhich is standby.

.................................................................................................................................................................................................

6 Perform a full reset of the CTL.

Important! A full reset, in contrast to a controller reset, of the CTL affects


• Automatic Protection Switching (APS) on MS/Line level.





• “Initiating a circuit pack reset” (p. 4-76)

CTL

Port unit active XC standby XC

Internalbus system


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

8 Depending on the circuit pack reporting the alarm:

If then

the alarm is reported by theactive XC


the alarm is reported by thestandby XC


the alarm is reported by a portunit


.................................................................................................................................................................................................

9 Perform a manual protection switch to the standby XC (Manual to Protection if theactive XC is the XC in the worker slot (slot 9), Manual to Working otherwise).

Result: The previously standby XC becomes the active XC, and the previouslyactive XC becomes standby.

.................................................................................................................................................................................................

10 Replace the XC reporting the alarm.

.................................................................................................................................................................................................


If then


the alarm persists continue with Step 24.

.................................................................................................................................................................................................

12 Perform a full reset of the standby XC.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-33



.................................................................................................................................................................................................



.................................................................................................................................................................................................


Independent from whether the alarm has cleared or not, continue with the next step.

.................................................................................................................................................................................................

15 Perform a full reset of the standby XC (this is not the same XC as in Step 12!).



.................................................................................................................................................................................................

16 Perform a manual equipment protection switch to the standby XC (Manual toProtection if the active XC is the XC in the worker slot (slot 9), Manual to Workingotherwise).


.................................................................................................................................................................................................


If then

the alarm has cleared in Step 14,and is still cleared

Stop! You have completed this procedure.

the alarm had cleared in Step 14,and now is reported again

replace the XC which initially was the active unit(cf. Step 5).


the alarm continued to persist inStep 14, and now has cleared

replace the XC which initially was the standby unit(cf. Step 5).


the alarm continued to persist inStep 14, and still persists



.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

18 Perform a controller reset of the port unit reporting the alarm.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

20 Important! A full reset of a port unit is traffic affecting!

Perform a full reset of the port unit reporting the alarm.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

22 Replace the port unit reporting the alarm.

.................................................................................................................................................................................................


If then




.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-35

.................................................................................................................................................................................................

24 Replace the Controller (CTL).



.................................................................................................................................................................................................


If then



Trouble clearing procedure in duplex control mode

Proceed as follows to clear a Circuit Pack Comm Failure alarm:

.................................................................................................................................................................................................


Legend:

CTL #1 The active Controller at the time when the alarm is being reported.

CTL #2 The standby Controller at the time when the alarm is being reported.

CTL #1 CTL #2

Port unit active XC standby XC

Internalbus system


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

E N D O F S T E P S.................................................................................................................................................................................................

Port unit, activeXC, standby XC

The circuit pack reporting the Circuit Pack Comm Failure alarm.This may be either a port unit (OP, EP, or GE1) or the active orstandby cross-connect and timing unit (XC160, XC320, XC640).

.................................................................................................................................................................................................

2 Take a note which cross-connect and timing unit (XC) is currently the active unit, andwhich is standby.

.................................................................................................................................................................................................

3 Perform a manual equipment protection switch to the CTL #2 (Manual to Protectionif CTL #1 is the Controller in the worker slot (slot 11), Manual to Workingotherwise).

.................................................................................................................................................................................................


If then

the alarm has cleared continue with the next step.


.................................................................................................................................................................................................

5 Perform a manual equipment protection switch back to the CTL #1.

.................................................................................................................................................................................................

6 At the WaveStar® CIT, refresh the NE Alarm List, and check if the alarm is stillcleared.

If then

the alarm is not reported again Stop! You have completed this procedure.

the alarm is reported again perform a manual equipment protection switch tothe CTL #2, and replace the CTL #1.


Reference:

Please refer to:


.................................................................................................................................................................................................

7 Perform a controller reset of the CTL #2.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-37

Important! It is important that the controller reset be performed as soon aspossible after the manual protection switch to avoid a (now unintended) automaticCTL protection switch. No automatic protection switch will be performed as longas the synchronisation process of the CTL #2 has not yet completed.



.................................................................................................................................................................................................

8 Verify that CTL #2 is still the active Controller (no automatic CTL protection switchoccurred).

If then

CTL #2 is still the activeController


CTL #1 is the active Controller(an automatic CTL protectionswitch occurred due to thecontroller reset of the CTL #2)

Perform a manual equipment protection switch tothe CTL #2, and then repeat Step 7 and Step 8.

.................................................................................................................................................................................................


If then

the alarm has cleared replace the CTL #1.


Reference:

Please refer to:


the alarm persists continue with the next step.

.................................................................................................................................................................................................

10 Perform a full reset of the CTL #2.

Important! It is important that the full reset be performed as soon as possible afterthe manual protection switch to avoid a (now unintended) automatic CTLprotection switch. No automatic protection switch will be performed as long as thesynchronisation process of the CTL #2 has not yet completed.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



.................................................................................................................................................................................................


If then





.................................................................................................................................................................................................


If then



Reference:

Please refer to:



.................................................................................................................................................................................................

13 Perform a manual equipment protection switch to the CTL #1 (Manual to Protectionif CTL #2 is the Controller in the worker slot (slot 11), Manual to Workingotherwise).


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-39

.................................................................................................................................................................................................


If then



The fact that the Circuit Pack Comm Failurealarm is not reported by the now active CTL #1 isan indication that CTL #2 is defective.

Reference:

Please refer to:



.................................................................................................................................................................................................

15 Perform a controller reset of the CTL #1.

Important! It is important that the controller reset be performed as soon aspossible after the manual protection switch to avoid a (now unintended) automaticCTL protection switch. No automatic protection switch will be performed as longas the synchronisation process of the CTL #1 has not yet completed.



.................................................................................................................................................................................................


If then






.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



Reference:

Please refer to:



.................................................................................................................................................................................................

18 Perform a full reset of the CTL #1.

Important! It is important that the full reset be performed as soon as possible afterthe manual protection switch to avoid a (now unintended) automatic CTLprotection switch. No automatic protection switch will be performed as long as thesynchronisation process of the CTL #1 has not yet completed.



.................................................................................................................................................................................................


If then






.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-41

.................................................................................................................................................................................................


If then



Reference:

Please refer to:



.................................................................................................................................................................................................

21 Depending on the circuit pack reporting the alarm:

If then





the alarm is reported by a portunit


.................................................................................................................................................................................................



.................................................................................................................................................................................................

23 Replace the XC reporting the alarm.

.................................................................................................................................................................................................


If then




.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................




.................................................................................................................................................................................................



.................................................................................................................................................................................................


Independent from whether the alarm has cleared or not, continue with the next step.

.................................................................................................................................................................................................

28 Perform a full reset of the standby XC (this is not the same XC as in Step 25!).



.................................................................................................................................................................................................



.................................................................................................................................................................................................


If then

the alarm has cleared in Step 27,and is still cleared


the alarm had cleared in Step 27,and now is reported again

replace the XC which initially was the active unit(cf. Step 2).


the alarm continued to persist inStep 27, and now has cleared

replace the XC which initially was the standby unit(cf. Step 2).



.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-43

If then

the alarm continued to persist inStep 27, and still persists


.................................................................................................................................................................................................

31 Perform a controller reset of the port unit reporting the alarm.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

33 Important! A full reset of a port unit is traffic affecting!

Perform a full reset of the port unit reporting the alarm.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

35 Replace the port unit reporting the alarm.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

37 Replace one of the two CTLs, and make the newly inserted CTL the active Controller.



.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-45

Clearing Circuit Pack not Present.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Circuit Pack not Present alarm.

Related information

Please also refer to the corresponding alarm description → “Circuit Pack not Present”(p. 2-48).

Before you begin

You or a service technician must be on-site at the NE to clear a Circuit Pack not

Present alarm.

Required equipment


• A replacement circuit pack of the correct type


Proceed as follows to clear a Circuit Pack not Present alarm:

.................................................................................................................................................................................................

1 Check if a circuit pack is plugged in the slot for which the Circuit Pack not

Present alarm is reported.

If then

a circuit pack is plugged replace the CTL.

Reference:

Please refer to:


no circuit pack is plugged insert a circuit pack of the correct type (acc. to theactual provisioning).

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Circuit Pack Type Mismatch.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Circuit Pack Type Mismatch alarm.

Related information

Please also refer to the corresponding alarm description → “Circuit Pack TypeMismatch” (p. 2-50).

Before you begin

You or a service technician must be on-site at the NE to clear a Circuit Pack Type

Mismatch alarm.




Required equipment


• WaveStar® CIT

• A replacement circuit pack of the correct type


Proceed as follows to clear a Circuit Pack Type Mismatch alarm:

.................................................................................................................................................................................................

1 If you have inserted a circuit pack in the lower row of the shelf in an LXCconfiguration with XC160 cross-connect and timing unit(s), then remove this circuitpack (please also refer to “Configuration rules” (p. 4-66)).

Otherwise, continue with the next step.

.................................................................................................................................................................................................

2 Check if the latches of the circuit pack are closed.

If then

the latches are closed continue with the next step.

the latches are not closed close the latches, and then continue with the nextstep.

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-47

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

4 Verify that the provisioning for the slot, for which the Circuit Pack Type Mismatch

alarm is reported, is according to your needs.

If then

the provisioning is correct replace the affected circuit pack.

The circuit pack EEPROM seems to be defective.

the provisioning is not correct correct the provisioning.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Circuit Pack Type Mismatch

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Circuit Pack Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Circuit Pack Failure alarm.

Related information

Please also refer to the corresponding alarm description → “Circuit Pack Failure”(p. 2-47).

Before you begin

You or a service technician should be on-site at the NE to clear a Circuit Pack

Failure alarm.




Required equipment


• WaveStar® CIT

• A replacement circuit pack of the same type


Proceed as follows to clear a Circuit Pack Failure alarm:

.................................................................................................................................................................................................

1 Replace the faulty circuit pack with a circuit pack of the same type.


• “Replacing a circuit pack by a circuit pack of the same type” (p. 4-55)

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-49

Clearing Comm Channel Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Comm Channel Failure alarm.

Related information

Please also refer to the corresponding alarm description → “Comm Channel Failure”(p. 2-51).

Before you begin

You or a service technician must be on-site at the NE to clear a Comm Channel

Failure alarm.




Required equipment


• WaveStar® CIT


• A replacement cross-connect and timing unit (XC160, XC320, XC640)

Instructions

Proceed as follows to clear a Comm Channel Failure alarm:

If then

the alarm is reported for one ortwo cross-connect and timingunits (XCs)

please refer to “Trouble clearing procedure whenalarm is reported by an XC” (p. 3-50).

the alarm is reported for one ormore port units

please refer to “Trouble clearing procedure whenalarm is reported by a port unit” (p. 3-55).

Trouble clearing procedure when alarm is reported by an XC

Important! Please be aware that the terms “worker” and “protection” are used todescribe the static role within a protection, whereas the terms “active” and“standby” are used to describe the current (dynamic) role in a protection. Theactive or standby unit always means the circuit pack which is currently the activeor standby unit in an equipment protection.

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Proceed as follows:

.................................................................................................................................................................................................

1 Depending on whether the alarm is reported by one or two cross-connect and timingunits (XCs):

If the alarm is reported by then

one XC continue with the next step.

two XCs at the same time continue with Step 11.

.................................................................................................................................................................................................

2 If then




perform a manual equipment protection switch tothe standby XC (Manual to Protection if the activeXC is the XC in the worker slot (slot 9), Manual toWorking otherwise).

Result: The alarm reporting XC becomes thestandby unit.

.................................................................................................................................................................................................




.................................................................................................................................................................................................


If then



Trouble clearing Clearing Comm Channel Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-51

.................................................................................................................................................................................................

5 If then

one CTL is installed (no CTLequipment protection, simplexcontrol)


two CTLs are installed (CTLequipment protection, duplexcontrol)


.................................................................................................................................................................................................

6 Perform a full reset of the CTL.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

8 Replace the standby XC.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

10 Replace the CTL.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then


at least one XC still reports thisalarm

continue (restart) with Step 2.

.................................................................................................................................................................................................

12 Perform a manual equipment protection switch to the standby CTL (Manual toProtection if the active Controller is the CTL in the worker slot (slot 11), Manual toWorking otherwise).

Result: The previously standby CTL becomes the active CTL, and the previouslyactive CTL becomes standby.

.................................................................................................................................................................................................


If then


the alarm persists replace the standby XC, and then continue withStep 11.

.................................................................................................................................................................................................

14 Perform a full reset of the standby CTL.







Result: A CTL equipment protection switch occurs.




.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-53

.................................................................................................................................................................................................

15 Clear the existing manual equipment protection switch.

.................................................................................................................................................................................................



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................



.................................................................................................................................................................................................

20 Replace the standby CTL.

Result: The alarm should have cleared now, and you have completed thisprocedure.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

E N D O F S T E P S.................................................................................................................................................................................................

Trouble clearing procedure when alarm is reported by a port unit

Proceed as follows:

.................................................................................................................................................................................................



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

3 Re-assign the line timing references, i.e. make sure that no port of the alarm-reportingport unit is assigned as a line timing reference.

.................................................................................................................................................................................................


.................................................................................................................................................................................................



.................................................................................................................................................................................................


If then




.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-55

.................................................................................................................................................................................................

7 Re-assign the line timing references, i.e. re-establish the initial timing configuration(assign a port of the alarm-reporting port unit as a line timing reference.

.................................................................................................................................................................................................

8 Perform a full reset of the port unit reporting the alarm.



.................................................................................................................................................................................................


If then


the alarm persists replace the port unit reporting the alarm.

Result: The alarm should have cleared now, andyou have completed this procedure.

.................................................................................................................................................................................................


.................................................................................................................................................................................................



.................................................................................................................................................................................................




.................................................................................................................................................................................................


.................................................................................................................................................................................................



.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005


.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................



.................................................................................................................................................................................................

18 Replace the standby XC.

Result: The alarm should have cleared now, and you have completed thisprocedure.

E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-57

Clearing CTL Comm Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a CTL Comm Failure alarm.

Related information

Please also refer to the corresponding alarm description → “CTL Comm Failure”(p. 2-52).

Before you begin

You or a service technician should be on-site at the NE to clear a CTL Comm Failure

alarm.




Required equipment


• WaveStar® CIT



Proceed as follows to clear a CTL Comm Failure alarm:

.................................................................................................................................................................................................

1 Perform a controller reset of the CTL.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

3 Perform a full reset of the CTL, and wait for the system to re-initialize.

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005









.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

5 Replace the CTL.



.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing CTL Comm Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-59

Clearing Duplex Control not Present.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Duplex Control not Present alarm.

Related information

Please also refer to the corresponding alarm description → “Duplex Control notPresent” (p. 2-53).

Before you begin

You or a service technician must be on-site at the NE to clear a Duplex Control not

Present alarm.

Required equipment

The following equipment might be required:

• A second Controller (either CTL/- or CTL/2)


Proceed as follows to clear a Duplex Control not Present alarm:

.................................................................................................................................................................................................

1 If you want to operate the system in simplex control mode, then set the severity of theDuplex Control not Present alarm to “Not reported”. Otherwise continue with thenext step.

.................................................................................................................................................................................................

2 Make sure that two Controllers are installed, and that the hardware versions of the twoControllers match (for example 2 × CTL/-, or 2 × CTL/2).

The CTL equipment protection group will be created automatically and the Duplex

Control not Present alarm be cleared as soon as a suitable second Controller isinstalled.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing ECI Comm Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an ECI Comm Failure alarm.

Related information

Please also refer to the corresponding alarm description → “ECI Comm Failure”(p. 2-55).

Before you begin

You or a service technician should be on-site at the NE to clear an ECI Comm Failure

alarm.

Required equipment


• WaveStar® CIT

• Eventually, a replacement EP51 or EP155 port unit


Proceed as follows to clear a ECI Comm Failure alarm:

.................................................................................................................................................................................................

1 Perform a controller reset of the standby EP51 or EP155.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

3 Perform a full reset of the standby EP51 or EP155.



Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-61

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

5 Perform a manual protection switch to the standby EP51 or EP155.

.................................................................................................................................................................................................

6 Perform a controller reset of the standby EP51 or EP155.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

8 Perform a full reset of the standby EP51 or EP155.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


Trouble clearing Clearing ECI Comm Failure

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................










.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

14 Replace the ECI reporting the alarm by an ECI of the same type.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-63

.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing ECI Mismatch Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a ECI Mismatch Failure alarm.

Related information

Please also refer to the corresponding alarm description → “ECI Mismatch Failure”(p. 2-56).

Before you begin

You or a service technician must be on-site at the NE to clear a ECI Mismatch

Failure alarm.

Required equipment

The following equipment may be eventually required:

• Either an ECI/155MP8 or ECI/155ME8 Electrical Connector Interface (ECI).The type of ECI needed (ECI/155MP8 or ECI/155ME8) depends on the desiredconfiguration (protected or unprotected STM-1E transmission functionality).Please also refer to the LambdaUnite® MultiService Switch (MSS) User OperationsGuide.

• WaveStar® CIT


Proceed as follows to clear a ECI Mismatch Failure alarm:

.................................................................................................................................................................................................

1 Depending on the type of ECI installed in the ECI slot, for which the alarm is beingreported:

If then

an ECI/155ME8 is installed continue with the next step.

an ECI/155MP8 is installed continue with Step 3.

an ECI51/MP72 is installed continue with Step 4.

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-65

.................................................................................................................................................................................................

2 If then

an STM-1E equipment protectiongroup exists involving the ECIand two EP155 port units in thecorresponding universal slot pair

replace the ECI/155ME8 by an ECI/155MP8.

The ECI/155ME8 is not suitable for STM-1Eequipment protection.

an STM-1E equipment protectiongroup exists (ECI/155MP8 with2 × EP155), and you haveinstalled the ECI/155ME8 inorder to convert a protectedconfiguration into an unprotectedconfiguration with two EP155s(ECI/155ME8 with 2 × EP155)

delete the STM-1E equipment protection group.

EP51 port units are installed inthe corresponding universal slots

replace the ECI/155ME8 by an ECI51/MP72.

.................................................................................................................................................................................................

3 If then

you just have installed twoEP155 port units and theECI/155MP8 in order toconfigure an STM-1E equipmentprotection

create the corresponding STM-1E equipmentprotection group.

you just have deleted theSTM-1E equipment protectiongroup involving the ECI/155MP8

replace the ECI/155MP8 by an ECI/155ME8, ordeprovision one of the associated EP155 port units.

The ECI/155MP8 is not suitable for an unprotectedconfiguration with two EP155 port units.

EP51 port units are installed inthe corresponding universal slots

replace the ECI/155ME8 by an ECI51/MP72.

.................................................................................................................................................................................................

4 If then

you just have installed twoEP155 port units in thecorresponding universal slots inorder to configure an STM-1Eequipment protection

replace the ECI51/MP72 by an ECI/155MP8, andcreate the STM-1E equipment protection group.

Trouble clearing Clearing ECI Mismatch Failure

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If then

you just have installed one ortwo EP155 port units in thecorresponding universal slots inorder to realize unprotectedSTM-1E transmission

replace the ECI51/MP72 by an ECI/155ME8.

there are EP155 port unitsinstalled in the correspondinguniversal slots, although youwant to realize a DS3 protectedor unprotected configuration

install EP51 port units instead (observing therelevant configuration rules).

Related information

The type of ECI needed depends on the desired configuration:

ECI/155ME8 Unprotected STM-1E transmission functionality

ECI/155MP8 Protected STM-1E transmission functionality

ECI51/MP72 DS3 transmission functionality (protected or unprotected)

Please also refer to the equipment provisioning concepts described in theLambdaUnite® MultiService Switch (MSS) User Operations Guide.

Trouble clearing Clearing ECI Mismatch Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-67

E N D O F S T E P S.................................................................................................................................................................................................

Clearing ECI not Present.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a ECI not Present alarm.

Related information

Please also refer to the corresponding alarm description → “ECI not Present” (p. 2-57).

Before you begin

You or a service technician must be on-site at the NE to clear a ECI not Present

alarm.

Required equipment


• Either an ECI/155MP8 or ECI/155ME8 Electrical Connector Interface (ECI).The type of ECI needed (ECI/155MP8 or ECI/155ME8) depends on the desiredconfiguration (protected or unprotected STM-1E transmission functionality).Please also refer to the LambdaUnite® MultiService Switch (MSS) User OperationsGuide.


Proceed as follows to clear a ECI not Present alarm:

.................................................................................................................................................................................................

1 Install a suitable Electrical Connector Interface (ECI).

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Fan Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Fan Failure alarm.

Related information

Please also refer to the corresponding alarm description → “Fan Failure” (p. 2-58).

Fan speed

The information that a fan has failed is derived from the fan speed. If the fan speeddrops below a certain value, then the fan is likely to be faulty.

Opening angle of the non-return valves

In normal operation the fan speed may vary between 2000 and 4400 RPM (rotationsper minute) in steps of 400 RPM. An operational fan produces an airflow which opensthe non-return valves. The opening angle of the non-return valves depends on theamount of airflow passing through. Thus, the opening angle of the non-return valvescan be used to make a rough estimate of the fan speed.

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-69

To give you a clue, the following figure shows the non-return valves at three differentfan speeds.

Legend:

1 2000 RPM, opening angle approx. 16o



Before you begin

You or a service technician must be on-site at the NE to clear a Fan Failure alarm.

➀

➁

➂

Trouble clearing Clearing Fan Failure

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Required equipment


• A fully functional fan unit


Proceed as follows to clear a Fan Failure alarm:

.................................................................................................................................................................................................




.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................




E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Fan Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-71

Clearing Fan Unit Comm Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Fan Unit Comm Failure alarm.

Related information

Please also refer to the corresponding alarm description → “Fan Unit Comm Failure”(p. 2-59).

Before you begin

You or a service technician must be on-site at the NE to clear a Fan Unit Comm

Failure alarm.




Required equipment


• WaveStar® CIT

• A replacement fan unit control cable



Proceed as follows to clear a Fan Unit Comm Failure alarm:

.................................................................................................................................................................................................


If then





Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................











.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................








Trouble clearing Clearing Fan Unit Comm Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-73

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................








.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................



.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................




.................................................................................................................................................................................................








.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-75

Clearing Fan Unit Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Fan Unit Failure alarm.

Related information

Please also refer to the corresponding alarm description → “Fan Unit Failure” (p. 2-60).

Before you begin

You or a service technician must be on-site at the NE to clear a Fan Unit Failure

alarm.





Required equipment


• WaveStar® CIT


• Two replacement fan unit power cables

• Two replacement Power Interfaces


CAUTION

Destruction of components by electrostatic discharge.

A network element which is operated without a functional fan unit for more than twominutes may fail due to overheating.

Therefore, do not operate a network element without a functional fan unit.

Proceed as follows to clear a Fan Unit Failure alarm:

.................................................................................................................................................................................................




Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

3 During the following steps, refresh and check the alarm list in regular intervals. If aUnit Temperature too High alarm should be reported, refer to “Unit Temperaturetoo High in combination with Fan Unit Failure” (p. 3-79) .

.................................................................................................................................................................................................

4 Are both the fan unit power connectors (“Power Input A/B”) and the correspondingPower Interface (PI) connectors “(FAN output”) connected properly?

If then

yes continue with Step 6.

no connect the connectors properly, and then continuewith the next step.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

6 Successively replace both fan unit power cables.

.................................................................................................................................................................................................


If then



Trouble clearing Clearing Fan Unit Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-77

.................................................................................................................................................................................................

8 Replace PI A.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

10 Replace PI B.

.................................................................................................................................................................................................


If then




.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

E N D O F S T E P S.................................................................................................................................................................................................

Unit Temperature too High in combination with Fan Unit Failure

If a Unit Temperature too High alarm is reported while a Fan Unit Failure alarmis present, then it is up to your discretion how to proceed. You may take one of thefollowing actions:

Possible action Consequences

You may switch off the NE toprevent circuit packs frombeing seriously damaged due tooverheating.

All traffic managed by the respective NE will beinterrupted.

However, it might be an option to wait a while (atleast ten minutes) to let the circuit packs cool off,switch on the NE again, and then proceed with thetrouble clearing procedure.

Important: Before switching off the NE, follow theinstructions given in Step 1 of the procedure“Replacing the Controller (CTL)” (p. 4-62) toremove the Controller (CTL) from its slot.

You may remove the affectedcircuit pack from the system toprevent it from being seriouslydamaged due to overheating.

The traffic managed by the respective circuit packwill be interrupted. The circuit pack can bere-inserted after the Fan Unit Failure alarm iscleared.

You might ignore the UnitTemperature too High alarm.

There is a high risk of seriously damaging circuitpacks due to overheating.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-79

Clearing Fan Unit not Present.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Fan Unit not Present alarm.

Related information

Please also refer to the corresponding alarm description → “Fan Unit not Present”(p. 2-61).

Before you begin

You or a service technician must be on-site at the NE to clear a Fan Unit not

Present alarm.





Required equipment


• WaveStar® CIT



CAUTION

A network element may fail without proper cooling.

A network element which is operated without a fan unit for more than two minutes mayfail due to overheating.

Therefore, do not operate a network element without a fan unit.

Proceed as follows to clear a Fan Unit not Present alarm:

.................................................................................................................................................................................................

1 Install the fan unit. Proceed as described in the following steps.

.................................................................................................................................................................................................

2 If required, loosen the screws (1) of the fan unit drawer (with your fingers).

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Refer to the following figure for clarification and further reference:

.................................................................................................................................................................................................

3 Slide the fan unit drawer from its position by using the handles (2).

.................................................................................................................................................................................................

4 Place the fan unit into the fan unit drawer, and slide the fan unit drawer back into theshelf.

.................................................................................................................................................................................................

5 Connect the power and alarm connectors of the fan unit.

.................................................................................................................................................................................................

6 With your fingers, fasten the screws of the fan unit drawer.

E N D O F S T E P S........................................................................................................................................................................................................................

(1)

(2)

(1)

Trouble clearing Clearing Fan Unit not Present

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-81

Clearing Fan Voltage Feed A/B Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Fan Voltage Feed A Failure or Fan Voltage Feed B

Failure alarm.

Related information

Please also refer to the corresponding alarm description:

• → “Fan Voltage Feed A Failure” (p. 2-62)

• → “Fan Voltage Feed B Failure” (p. 2-63)

Before you begin

You or a service technician must be on-site at the NE to clear a Fan Voltage Feed A

Failure alarm.




The following trouble clearing procedure is based on the assumption that the “FANoutput” of the Power Interfaces (PI A, PI B) and the fan unit power inputs (“PowerInput A”, “Power Input B”) are interconnected as follows:

• “FAN output” of the PI A → Fan unit “Power Input A”

• “FAN output” of the PI B → Fan unit “Power Input B”


Required equipment


• WaveStar® CIT

• A replacement fan unit power cable

• A replacement Power Interface (PI)

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005


Proceed as follows to clear a Fan Voltage Feed A Failure or Fan Voltage Feed B

Failure alarm:

.................................................................................................................................................................................................

1 The measures to be taken depend on the type of Power Interface used:

If then

the PI/- variant is used continue with the next step.

the PI/100 variant is used continue with Step 4.

.................................................................................................................................................................................................

2 At the WaveStar® CIT, check the NE Alarm List.

If then

a System Power Failure alarmis reported at the same time


no System Power Failurealarm is reported

continue with the next step

.................................................................................................................................................................................................

3 Make sure that the circuit breaker on the affected Power Interface is in the ON position(“I”), and then continue with Step 6.

Trouble clearing Clearing Fan Voltage Feed A/B Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-83

Circuit breaker on the Power Interfaces:

.................................................................................................................................................................................................

4 At the WaveStar® CIT, check the NE Alarm List.

If then

a System Power Failure alarmis reported at the same time

clear this alarm first (cf. “Clearing System PowerFailure” (p. 3-102)), and then continue with Step 6.

no System Power Failurealarm is reported


.................................................................................................................................................................................................

5 Measure the actual supply voltage at the affected system power feeder of the exchangebattery.

If then

the voltage is within the normalrange (≥ 38.0 V DC, negativepolarity)

replace the Power Interface reporting the SystemPower Failure alarm.

the voltage is out of range repair the exchange battery.

0

0

I

I


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

6 At the WaveStar® CIT, check the NE Alarm List, and check if the alarm (Fan Voltage

Feed A Failure or Fan Voltage Feed B Failure) has cleared.

If then



.................................................................................................................................................................................................

7 Is a fan unit power cable installed between the corresponding fan unit power input(“Power Input A”, “Power Input B”) and the “FAN output” of the associated PowerInterface (PI A, PI B)?

If then


no install a fan unit power cable between the fan unitpower input and the “FAN output” of theassociated Power Interface, and then continue withthe next step.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

9 Are the connectors of the power cable connected properly at both the fan unit powerinput and the “FAN output” of the associated Power Interface?

If then


no connect the connectors properly, and then continuewith the next step.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-85

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

11 Replace the fan unit power cable between the corresponding fan unit power input(“Power Input A”, “Power Input B”) and the “FAN output” of the associated PowerInterface (PI A, PI B).

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

13 Replace the associated Power Interface (PI A, PI B).

.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing IDE Flash Card Access Fail.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an IDE Flash Card Access Fail alarm.

Related information


• the corresponding alarm description → “IDE Flash Card Access Fail” (p. 2-64)

• “Configuration rules” (p. 4-66)

Before you begin

You or a service technician must be on-site at the NE to clear an IDE Flash Card

Access Fail alarm.

Required equipment


• A CompactFlash® card of the following size:

– 256 MB when one or two Controllers of type CTL/- are used.

– 512 MB when one or two Controllers of type CTL/2 are used.


Proceed as follows to clear an IDE Flash Card Access Fail alarm:

.................................................................................................................................................................................................

1 Perform a database backup.

Even if the database backup should fail, continue with the next step.

.................................................................................................................................................................................................

2 Important! Make sure to use a CompactFlash® card of the correct size.

Replace the CompactFlash® card currently in use.

Reference: “Replacing a CompactFlash® card” (p. 4-48)

.................................................................................................................................................................................................

3 If then

one CTL is installed (no CTLequipment protection, simplexcontrol)

restore the most recent database.

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-87

If then

two CTLs are installed (CTLequipment protection, duplexcontrol)

the data stored on the newly insertedCompactFlash® card will automatically besynchronized to the data stored on theCompactFlash® card of the active Controller.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing IDE Flash Card Access Fail

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing NVM Shortage.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an NVM Shortage alarm.

Related information

Please also refer to the corresponding alarm description → “NVM Shortage” (p. 2-65).

Before you begin

You or a service technician must be on-site at the NE to clear an NVM Shortage alarm.

Required equipment


• One or two CompactFlash® cards of the following size:

– 256 MByte when one or two Controllers of type CTL/- are used.

– 512 MByte when one or two Controllers of type CTL/2 are used.

– 1 GByte when one or two Controllers of type CTL/3T or CTL/3S are used.


Proceed as follows to clear an NVM Shortage alarm:

.................................................................................................................................................................................................

1 Make sure to use CompactFlash® card(s) of the correct size.

If necessary, replace the CompactFlash® card(s) currently in use.


E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-89

Clearing ONI Failure on protecting CTL.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an ONI Failure on protecting CTL alarm.

Related information

Please also refer to the corresponding alarm description → “ONI Failure on protectingCTL” (p. 2-66).

Before you begin

You or a service technician should be on-site at the NE to clear an ONI Failure on

protecting CTL alarm.




Required equipment


• WaveStar® CIT

• A replacement circuit pack for the circuit pack reporting the alarm



Proceed as follows to clear an ONI Failure on protecting CTL alarm:

.................................................................................................................................................................................................

1 Verify that the latches of the circuit pack for which the alarm is reported are closed.

If then

the latches are properly closed continue with Step 3.

the latches are not properlyclosed

close the latches (the circuit pack performs a fullreset), wait for the circuit pack to re-initialize, andthen continue with the next step.

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

3 Perform a controller reset of the standby Controller.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

5 Perform a full reset of the standby Controller.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

7 Replace the circuit pack for which the alarm is reported.

Trouble clearing Clearing ONI Failure on protecting CTL

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-91

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

9 Replace the standby Controller.



.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing ONI Failure on protecting CTL

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing ONI Failure on working CTL.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an ONI Failure on working CTL alarm.

Related information

Please also refer to the corresponding alarm description → “ONI Failure on workingCTL” (p. 2-68).

Before you begin

You or a service technician should be on-site at the NE to clear an ONI Failure on

working CTL alarm.




Required equipment


• WaveStar® CIT




Proceed as follows to clear an ONI Failure on working CTL alarm:

.................................................................................................................................................................................................

1 Verify that the latches of the circuit pack for which the alarm is reported are closed.

If then

the latches are properly closed continue with Step 3.

the latches are not properlyclosed

close the latches (the circuit pack performs a fullreset), wait for the circuit pack to re-initialize, andthen continue with the next step.

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-93

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

3 Perform a controller reset of the standby Controller.



.................................................................................................................................................................................................

4 Perform a manual protection switch to the just reset Controller.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

6 Perform a full reset of the standby Controller.



.................................................................................................................................................................................................

7 Perform a manual protection switch to the just reset Controller.

.................................................................................................................................................................................................


If then



Trouble clearing Clearing ONI Failure on working CTL

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

9 Replace the circuit pack for which the alarm is reported.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

11 Replace the standby Controller.



.................................................................................................................................................................................................

12 Perform a manual protection switch to the newly inserted Controller.

.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing ONI Failure on working CTL

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-95

Clearing Optical Module Fail.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Optical Module Fail alarm.

Related information

Please also refer to the corresponding alarm description → “Optical Module Fail”(p. 2-70).

Before you begin

You or a service technician must be on-site at the NE to clear a Optical Module Fail

alarm.


Proceed as follows to clear a Optical Module Fail alarm:

.................................................................................................................................................................................................

1 Wait approx. one minute.

.................................................................................................................................................................................................


If then


the alarm persists Replace the optical module.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Optical Module not Present.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Optical Module not Present alarm.

Related information

Please also refer to the corresponding alarm description → “Optical Module notPresent” (p. 2-72).


Proceed as follows to clear a Optical Module not Present alarm:

.................................................................................................................................................................................................

1 Depending on your needs:

If then

you want to keep on using anoptical module acc. to the currentprovisioning

install an optical module corresponding to theprovisioning.

you do not want to use an opticalmodule in the corresponding OMsocket any longer

deprovision the optical module.

you want to change the type ofprovisioned optical module of anOM socket

follow the procedure “Changing the provisionedoptical module of an OM socket” given in theLambdaUnite® MultiService Switch (MSS) UserOperations Guide.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-97

Clearing Optical Module not supported.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Optical Module not supported alarm.

Related information

Please also refer to the corresponding alarm description → “Optical Module notsupported” (p. 2-73).

Before you begin

You or a service technician must be on-site at the NE to clear a Optical Module not

supported alarm.


Proceed as follows to clear a Optical Module not supported alarm:

.................................................................................................................................................................................................

1 Install a LambdaUnite® MSS certified SFP.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Optical Module Type Mismatch.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Optical Module Type Mismatch alarm.

Related information

Please also refer to the corresponding alarm description → “Optical Module TypeMismatch” (p. 2-74).


Proceed as follows to clear a Optical Module Type Mismatch alarm:

.................................................................................................................................................................................................

1 If you just have installed the optical module for autoprovisioning purposes, then verifyif the optical module is permitted for the use with this type of parent board.

Otherwise, continue with the next step.

.................................................................................................................................................................................................

2 Depending on your needs:

If then

you want to keep on using anoptical module acc. to the currentprovisioning

install an optical module corresponding to theprovisioning.

you want to change the type ofprovisioned optical module of anOM socket

follow the procedure “Changing the provisionedoptical module of an OM socket” given in theLambdaUnite® MultiService Switch (MSS) UserOperations Guide.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-99

Clearing Power Interface not Present.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Power Interface not Present alarm.

Related information


• the corresponding alarm description → “Power Interface not Present” (p. 2-75)


Before you begin

You or a service technician must be on-site at the NE to clear a Power Interface not

Present alarm.



Proceed as follows to clear a Power Interface not Present alarm:

.................................................................................................................................................................................................

1 Install the missing Power Interface (PI).

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Power Interface Read Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Power Interface Read Failure alarm.

Related information


• the corresponding alarm description → “ Power Interface Read Failure ” (p. 2-76)


Before you begin

You or a service technician must be on-site at the NE to clear a Power Interface

Read Failure alarm.


Required equipment


• WaveStar® CIT


Proceed as follows to clear a Power Interface Read Failure alarm:

.................................................................................................................................................................................................

1 Replace the Power Interface (PI).

.................................................................................................................................................................................................

2 Retrieve the equipment parameters of that Power Interface (by using the RTRV-EQPTTL1 command, or by retrieving the equipment details using the WaveStar® CITgraphical user interface) to make sure that the Power Interface Read Failure alarmhas cleared.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-101

Clearing System Power Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a System Power Failure alarm.

Related information

Please also refer to the corresponding alarm description → “System Power Failure”(p. 2-78).

Before you begin

You or a service technician must be on-site at the NE to clear a System Power

Failure alarm.




The following trouble clearing procedure is based on the assumption that the “FANoutput” of the Power Interfaces (PI A, PI B) and the fan unit power inputs (“PowerInput A”, “Power Input B”) are interconnected as follows:

• “FAN output” of the PI A → Fan unit “Power Input A”

• “FAN output” of the PI B → Fan unit “Power Input B”

Required equipment


• WaveStar® CIT

• A volt meter

• A replacement Power Interface (PI)


Proceed as follows to clear a System Power Failure alarm:

.................................................................................................................................................................................................

1 Make sure that the circuit breaker on the affected Power Interface is in position “I”.

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Circuit breaker on the Power Interfaces:

.................................................................................................................................................................................................

2 At the WaveStar® CIT, refresh the NE Alarm List, and check if the System Power

Failure alarm has cleared.

If then


the System Power Failurealarm persists


.................................................................................................................................................................................................

3 Measure the actual supply voltage at the affected system power feeder of the exchangebattery.

If then

the voltage is within the nominalrange (≥ 38.0 V DC, negativepolarity)

replace the Power Interface reporting the SystemPower Failure alarm.

the voltage is out of range repair the exchange battery.

0

0

I

I

Trouble clearing Clearing System Power Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-103

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing System Power Failure

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing TI not Present.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a TI not Present alarm.

Related information

Please also refer to the corresponding alarm description → “TI not Present” (p. 2-80).

Before you begin

You or a service technician must be on-site at the NE to clear a TI not Present

alarm.

Required equipment

Make sure that you have a Timing Interface (TI) available.


Proceed as follows to clear a TI not Present alarm:

.................................................................................................................................................................................................

1 Install the Timing Interface.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-105

Clearing TXI Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a TXI Failure alarm.

Related information

Please also refer to the corresponding alarm description → “TXI Failure ” (p. 2-81).

Before you begin

You or a service technician must be on-site at the NE to clear a TXI Failure alarm.




Required equipment


• WaveStar® CIT


Proceed as follows to clear a TXI Failure alarm:

.................................................................................................................................................................................................

1If then

the cross-connect and timing unit(XC) in the protection slot (slot10) and one or more port unitshave been installed(autoprovisioned) immediatelybefore the alarm was reported

proceed as follows:

1. Deprovision the protection XC.

2. Insert (Autoprovision) the protection XC again,and wait a few seconds before inserting anyassociated port units, and insert the port unitsone after the other.

Important! After inserting the protectionXC, always wait a few seconds beforeinserting any associated port units, andinsert the port units one after the other!

When the protection XC and port units areinserted concurrently, then it may happenthat the TXI configuration on the protectionXC is not completely correct, which mayresult in TXI Failure alarms.

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If then

the system configuration has notbeen changed


.................................................................................................................................................................................................

2 Identify the affected TXI bus line.

The affected TXI bus line can be seen from the alarm identifier (Probable cause).When the Probable cause is TXI2F for example, then the TXI bus line number 2is affected.

.................................................................................................................................................................................................

3 From the alarm message displayed in the WaveStar® CIT NE Alarm List, identify thecircuit pack reporting the alarm.

.................................................................................................................................................................................................

4 Use the TXI bus line numbering scheme (see “TXI bus line numbering scheme”(p. 4-111)) to identify the sender of the TXI signal on the affected TXI bus line.

Result: You have identified a port unit and a cross-connect and timing unit, one ofthem being the sender of the TXI signal on the affected TXI bus line, and the otherbeing the alarm-reporting circuit pack.

.................................................................................................................................................................................................

5 In case you have identified

a port unit proceed with the next step

an XC proceed with Step 8.

.................................................................................................................................................................................................

6 Replace the port unit identified in Step 4, i.e. the sender of the TXI signal on theaffected TXI bus line.

.................................................................................................................................................................................................


If then




Trouble clearing Clearing TXI Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-107

.................................................................................................................................................................................................

8 If the XC identified in Step 4 then

is currently the active unit in the1+1 XC equipment protection

perform a manual equipment protection switch tothe second XC, and then continue with the nextstep.

is currently the standby unit inthe 1+1 XC equipment protection


.................................................................................................................................................................................................

9 Replace the XC identified in Step 4.

.................................................................................................................................................................................................


If then




E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing TXI Failure

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Unit Cooling Degraded.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Unit Cooling Degraded alarm.

Related information

Please also refer to the corresponding alarm description → “Unit Cooling Degraded ”(p. 2-83).

Before you begin

You or a service technician should be on-site at the NE to clear a Unit Cooling

Degraded alarm.

Required equipment


• A replacement air filter


Proceed as follows to clear a Unit Cooling Degraded alarm:

.................................................................................................................................................................................................

1 Check the NE Alarm List.

If then

any of the following alarms ispresent at the same time:

Fan Failure,

Fan Unit Failure,

Unit Temperature too High.


Reference:

Please refer to the corresponding trouble clearingprocedure:

• “Clearing Fan Failure ” (p. 3-69)

• “Clearing Fan Unit Failure” (p. 3-76)

• “Clearing Unit Temperature too High”(p. 3-112)

none of these alarms is present continue with the next step.

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-109

.................................................................................................................................................................................................

2 Check the shelf equipage (front and rear side).

If then

there are empty slots which arenot covered by blank faceplates

cover all empty slots by blank faceplates

all empty slots are covered byblank faceplates


.................................................................................................................................................................................................

3 Ensure that a sufficient air flow through the shelf is garantueed.

If then

the air inlet (air filter) or outlet(fan unit) are obstructed

provide for adequate air supply and circulation byremoving the obstructing objects.

the air inlet or outlet are notobstructed by any objects

possibly, the air filter is clogged. Replace the airfilter.

Reference:

Please refer to:

• “Replacing the air filter” (p. 4-18)

.................................................................................................................................................................................................

4 Wait a few minutes.

.................................................................................................................................................................................................


If then


the alarm persists check if the ambient temperature is extremly high(please refer to the climatic conditions for theoperation of LambdaUnite® MSS network elementsgiven in the safety guide). If the ambienttemperature is extremly high, then provide coolingat least in the direct vicinity of the neworkelement.

Trouble clearing Clearing Unit Cooling Degraded

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Unit Cooling Degraded

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-111

Clearing Unit Temperature too High.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Unit Temperature too High alarm.

Related information

Please also refer to the corresponding alarm description → “Unit Cooling Degraded ”(p. 2-83).

Before you begin

You or a service technician should be on-site at the NE to clear a Unit Temperature

too High alarm.


Proceed as follows to clear a Unit Temperature too High alarm:

.................................................................................................................................................................................................

1 Check the NE Alarm List.

If then

any of the following alarms ispresent at the same time:

Fan Failure,

Fan Unit Failure.


Important! It is critical to clear these fanunit alarms quickly. If this is not possibleplease consider the case differentiationconcerning a persistent Unit Temperaturetoo High alarm given subsequent to thistrouble clearing procedure.

Reference:

Please refer to the corresponding trouble clearingprocedure:

• “Clearing Fan Failure ” (p. 3-69)

• “Clearing Fan Unit Failure” (p. 3-76)

none of these alarms is present consider the case differentiation concerning apersistent Unit Temperature too High alarmgiven subsequent to this trouble clearing procedure.Then continue with the next step.

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

2 Check the shelf equipage (front and rear side).

If then

there are empty slots which arenot covered by blank faceplates

cover all empty slots by blank faceplates

all empty slots are covered byblank faceplates


.................................................................................................................................................................................................

3 Check if the air inlet or outlet are obstructed.

If then

the air inlet or outlet areobstructed

provide for adequate air supply.

the air inlet or outlet are notobstructed

check if the ambient temperature is extremly high(please refer to the climatic conditions for theoperation of LambdaUnite® MSS network elementsgiven in the safety guide). If the ambienttemperature is extremly high, then provide coolingat least in the direct vicinity of the neworkelement.

Trouble clearing Clearing Unit Temperature too High

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-113

E N D O F S T E P S.................................................................................................................................................................................................

Persistent “Unit Temperature too High” alarm

If a Unit Temperature too High alarm persists for a longer period (more than twominutes), then it is up to your discretion how to proceed. You may take one of thefollowing actions:

Possible action Consequences

You may switch off the NE toprevent circuit packs frombeing seriously damaged due tooverheating.

All traffic managed by the respective NE will beinterrupted.

However, it might be an option to wait a while (atleast ten minutes) to let the circuit packs cool off,switch on the NE again, and then proceed with thetrouble clearing procedure.

Important: Before switching off the NE, follow theinstructions given in Step 1 of the procedure“Replacing the Controller (CTL)” (p. 4-62) toremove the Controller (CTL) from its slot.

You may remove the affectedcircuit pack from the system toprevent it from being seriouslydamaged due to overheating.

The traffic managed by the respective circuit packwill be interrupted. The circuit pack can bere-inserted after the Unit Temperature too Highalarm has cleared.

You might ignore the UnitTemperature too High alarm.

There is a high risk of seriously damaging circuitpacks due to overheating.

Trouble clearing Clearing Unit Temperature too High

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing User Panel Comm Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a User Panel Comm Failure alarm.

Related information

Please also refer to the corresponding alarm description → “User Panel Comm Failure”(p. 2-86).

Before you begin

You or a service technician must be on-site at the NE to clear a User Panel Comm

Failure alarm.




Required equipment


• WaveStar® CIT

• A replacement user panel



Proceed as follows to clear a User Panel Comm Failure alarm:

.................................................................................................................................................................................................


If then





Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-115

.................................................................................................................................................................................................











.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................








Trouble clearing Clearing User Panel Comm Failure

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

8 Replace the user panel.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................









.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-117

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................




.................................................................................................................................................................................................








.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing User Panel not Present.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a User Panel not Present alarm.

Related information

Please also refer to the corresponding alarm description → “User Panel not Present”(p. 2-87).

Before you begin

You or a service technician must be on-site at the NE to clear a User Panel not

Present alarm.

Required equipment

Make sure that you have a user panel available.


Proceed as follows to clear a User Panel not Present alarm:

.................................................................................................................................................................................................

1 Install the user panel.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-119

Ethernet alarms

Overview.................................................................................................................................................................................................................................

Purpose

This section contains trouble clearing procedures for Ethernet alarms.

Contents

Clearing Loss of Alignment 3-121

Clearing max number of VLAN instances reached 3-122

Clearing Partial Transport Capacity Loss 3-123

Clearing Server Signal Fail (VCGSSF) 3-124

Clearing Sink End Failure of Protocol 3-125

Clearing Source End Failure of Protocol 3-126

Clearing Total Transport Capacity Loss 3-127

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Loss of Alignment.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Loss of Alignment alarm.

Related information

Please also refer to:

• the corresponding alarm description → “Loss of Alignment” (p. 2-92)


Before you begin

You or a service technician should be on-site at the NE to clear a Loss of Alignment

alarm.




Required equipment


• WaveStar® CIT

• Possibly, an additional Gigabit Ethernet circuit pack is required.


Proceed as follows to clear a Loss of Alignment alarm:

.................................................................................................................................................................................................

1 Check the cross-connections of all VC-4s/STS-1s of the Virtual Concatenated Group(VCG).

Make sure that the individual tributaries of the VCG are not routed over extremelydifferent paths. “Different” means different in length, and/or different concerning thenumber of network elements in the path (as each cross-connection causes a particulartransit delay).

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-121

Clearing max number of VLAN instances reached.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a max number of VLAN instances reached alarm.

Related information

Please also refer to:

• the corresponding alarm description → “max number of VLAN instances reached”(p. 2-95)


Before you begin

You or a service technician should be on-site at the NE to clear a max number of

VLAN instances reached alarm.




Required equipment


• WaveStar® CIT

• Possibly, an additional Gigabit Ethernet circuit pack is required.


Proceed as follows to clear a max number of VLAN instances reached alarm:

.................................................................................................................................................................................................

1 If possible, reduce the number of VLAN connections by deleting dispensible VLANtags from the static VLAN lists of all nodes participating in the Virtual LAN.

Otherwise (if there are no dispensible VLAN tags), consider installing an additionalGigabit Ethernet circuit pack in the network element reporting the alarm.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Partial Transport Capacity Loss.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Partial Transport Capacity Loss alarm.

Related information

Please also refer to the corresponding alarm description → “Partial Transport CapacityLoss” (p. 2-97).

Before you begin




Required equipment


• WaveStar® CIT


Proceed as follows to clear a Partial Transport Capacity Loss alarm:

.................................................................................................................................................................................................

1 Identify the affected members of the VCG by means of the alarms that are reported forthese tributaries (THPDEG, THPTIM or THPUNEQ for example), and clear thesealarms.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-123

Clearing Server Signal Fail (VCGSSF).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Server Signal Fail (VCGSSF) alarm.

Related information

Please also refer to the corresponding alarm description → “Server Signal Fail(VCGSSF)” (p. 2-98).

Instructions

Proceed as follows to clear a Server Signal Fail (VCGSSF) alarm:

.................................................................................................................................................................................................

1 Analyze the alarm state of the upstream equipment and take appropriate measures.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Sink End Failure of Protocol.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Sink End Failure of Protocol alarm.

Related information

Please also refer to the corresponding alarm description → “Sink End Failure ofProtocol” (p. 2-99).

Before you begin




Required equipment


• WaveStar® CIT


Proceed as follows to clear a Sink End Failure of Protocol alarm:

.................................................................................................................................................................................................

1 Make sure that the used equipment can interwork.

.................................................................................................................................................................................................

2 Check the provisioning of the LCAS source side, and correct if necessary.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-125

Clearing Source End Failure of Protocol.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Source End Failure of Protocol alarm.

Related information

Please also refer to the corresponding alarm description → “Source End Failure ofProtocol” (p. 2-100).

Before you begin




Required equipment


• WaveStar® CIT


Proceed as follows to clear a Source End Failure of Protocol alarm:

.................................................................................................................................................................................................

1 Make sure that the used equipment can interwork.

.................................................................................................................................................................................................

2 Check the provisioning of the LCAS sink side, and correct if necessary.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Total Transport Capacity Loss.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Total Transport Capacity Loss alarm.

Related information

Please also refer to the corresponding alarm description → “Total Transport CapacityLoss” (p. 2-101).

Before you begin




Required equipment


• WaveStar® CIT


Proceed as follows to clear a Total Transport Capacity Loss alarm:

.................................................................................................................................................................................................

1 If then

higher order transmission alarms(such as “Loss of signal” or“Loss of frame” for example) arereported at the same time


no higher order transmissionalarms are reported at the sametime

repair the individual members (tributaries) of theVCG.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-127


Overview.................................................................................................................................................................................................................................

Purpose

This section contains trouble clearing procedures for linear protection switching alarms.

Contents

Clearing Far End Signal Fail 3-129

Clearing primary section Mismatch 3-132

Clearing Prot. Arch. Mismatch 3-134

Clearing Prot. Arch. Mode Mismatch 3-135

Clearing Prot. Arch. Operation Mismatch 3-136

Clearing Prot. Switch Byte Inappropriate 3-137

Clearing Prot. Switch Byte Unacceptable 3-138

Clearing Switch Channel Mismatch 3-142

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Far End Signal Fail.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Far End Signal Fail alarm.

Related information

Please also refer to the corresponding alarm description → “Far End Signal Fail”(p. 2-103).

Before you begin



• have established a WaveStar® CIT connection to both the alarm-reporting and thecorresponding far-end NE.

Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to clear a Far End Signal Fail (FESF) alarm:

.................................................................................................................................................................................................

1 Identify the port unit and the input port associated to the protection line at the far end(NE A).

working

protectionX

Alarm-reportingNE

FESFSF condition

detected

NE BNE A

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-129

.................................................................................................................................................................................................

2 If then

transmission alarms are reportedfor the port identified in theprevious step

clear these alarms first, and then continue withStep 8.

no transmission alarms arereported for that port


.................................................................................................................................................................................................

3 Perform a controller reset of the port unit associated to the protection line at NE A.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

5 Perform a full reset of the port unit associated to the protection line at NE A.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

7 Replace the port unit associated to the protection line at NE A.

Trouble clearing Clearing Far End Signal Fail

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Far End Signal Fail

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-131

Clearing primary section Mismatch.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a primary section Mismatch alarm.

Related information

Please also refer to the corresponding alarm description → “primary section Mismatch”(p. 2-105).

Before you begin




Required privilege code

You should have at least a privilege code of M4 to perform the following troubleclearing procedure.

Required equipment


• WaveStar® CIT


Proceed as follows to clear a primary section Mismatch alarm:

.................................................................................................................................................................................................

1 Are other alarms reported at the same time, especially transmission alarms (signal fail(SF) or signal degrade (SD) conditions), which might have caused a protection switch?

If then

YES clear these alarms first.

Please refer to the corresponding trouble clearingprocedure.

NO continue with the next step.

.................................................................................................................................................................................................

2 Perform a clear protection switch command to both ends of the 1+1 optimized MSPprotection group.

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

4 Release the 1+1 optimized MSP protection groups at both ends.

.................................................................................................................................................................................................

5 Re-establish the 1+1 optimized MSP protection groups at both ends.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

7 Perform a controller reset of the active CTL.



.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing primary section Mismatch

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-133

Clearing Prot. Arch. Mismatch.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Prot. Arch. Mismatch alarm.

Related information

Please also refer to the corresponding alarm description → “Prot. Arch. Mismatch”(p. 2-107).

Before you begin




Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to clear a Prot. Arch. Mismatch alarm:

.................................................................................................................................................................................................

1 Define the protection architecture consistently at both ends of the protection line.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Prot. Arch. Mode Mismatch.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Prot. Arch. Mode Mismatch alarm.

Related information

Please also refer to the corresponding alarm description → “Prot. Arch. ModeMismatch” (p. 2-108).

Before you begin




Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to clear a Prot. Arch. Mode Mismatch alarm:

.................................................................................................................................................................................................

1 Provision the protection group consistently for the revertive or non-revertive switchingmode at both ends of the protection line.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-135

Clearing Prot. Arch. Operation Mismatch.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Prot. Arch. Operation Mismatch alarm.

Related information

Please also refer to the corresponding alarm description → “Prot. Arch. OperationMismatch” (p. 2-110).

Before you begin




Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to clear a Prot. Arch. Operation Mismatch alarm:

.................................................................................................................................................................................................

1 Provision the protection group consistently for unidirectional or bidirectional operationat both ends of the protection line.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Prot. Switch Byte Inappropriate.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Prot. Switch Byte Inappropriate alarm.

Related information

Please also refer to the corresponding alarm description → “Prot. Switch ByteInappropriate” (p. 2-112).

Instructions

Proceed as follows to clear a Prot. Switch Byte Inappropriate alarm:

.................................................................................................................................................................................................

1 If then

you have completed the cablingbetween the two nodes involvedin the 1+1 APS/MSP scheme, andjust have created the protectiongroup at the local node, i.e.currently only one end isconfigured.

continue with the provisioning, i.e. create theprotection group also at the remote node.

.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-137

Clearing Prot. Switch Byte Unacceptable.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Prot. Switch Byte Unacceptable alarm.

Related information

Please also refer to the corresponding alarm description → “Prot. Switch ByteUnacceptable” (p. 2-114).

Before you begin

You or a service technician should be on-site at the near-end NE and at the far-end NEto clear a Loss of Frame alarm.




Required equipment


• WaveStar® CIT.

Instructions

Proceed as follows to clear a Prot. Switch Byte Unacceptable alarm:

.................................................................................................................................................................................................

1 If then

the far-end NE is sending an“Exercise” request

terminate (clear) the “Exercise” request at thefar-end NE.

LambdaUnite® MSS systems do not support“Exercise” requests.

.................................................................................................................................................................................................


If then



Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

3 At the local (alarm-reporting) NE, perform a manual protection switch to the standbyXC (Manual to Protection if the active XC is the XC in the worker slot (slot 9),Manual to Working otherwise).


.................................................................................................................................................................................................


If then

the alarm now has cleared At the local NE, replace the XC which now is thestandby unit.

The clearing of the alarm as a consequence of theprotection switch indicates that the previouslyactive XC is defective.


Reference: “Replacing a circuit pack by a circuitpack of the same type” (p. 4-55)


.................................................................................................................................................................................................

5 At the far-end NE, perform a manual protection switch to the standby XC (Manual toProtection if the active XC is the XC in the worker slot (slot 9), Manual to Workingotherwise).

Trouble clearing Clearing Prot. Switch Byte Unacceptable

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-139

Result: At the far-end NE, the previously standby XC becomes the active XC, andthe previously active XC becomes standby.

.................................................................................................................................................................................................


If then

the alarm now has cleared At the far-end NE, replace the XC which now isthe standby unit.


The clearing of the alarm as a consequence of theprotection switch indicates that the previouslyactive XC is defective.



.................................................................................................................................................................................................

7 At the local NE, perform a full reset of the port unit associated to the protection line.



.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

9 At the far-end NE, perform a full reset of the port unit associated to the protection line.




.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

11 At the local NE, replace the port unit associated to the protection line.

Reference: “Replacing a circuit pack by a circuit pack of the same type” (p. 4-55)

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

13 At the far-end NE, replace the port unit associated to the protection line.


.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-141

Clearing Switch Channel Mismatch.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Switch Channel Mismatch alarm.

Related information

Please also refer to the corresponding alarm description → “Switch ChannelMismatch” (p. 2-116).

Before you begin




Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to clear a Switch Channel Mismatch alarm:

.................................................................................................................................................................................................

1 Define the protection settings consistently at both ends of the protection line.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005


Overview.................................................................................................................................................................................................................................

Purpose

This section contains trouble clearing procedures for path-related transmission alarms.

Contents

Clearing Alarm Indication Signal (AIS-P) 3-144

Clearing Path Switch Denial 3-145

Clearing Remote Defect Indication (RFI-P) 3-146

Clearing Remote Defect Indication (THPRDI) 3-147

Clearing Server Signal Fail (SSF-P) 3-148

Clearing Server Signal Fail (THPSSF) 3-149

Clearing Trace Identifier Mismatch (THPTIM) 3-150

Clearing Trace Identifier Mismatch (TIM-P) 3-151

Clearing Unequipped (THPUNEQ) 3-152

Clearing Unequipped (UNEQ-P) 3-153

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-143

Clearing Alarm Indication Signal (AIS-P).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Alarm Indication Signal (AIS-P) alarm.

Related information

Please also refer to the corresponding alarm description → “Alarm Indication Signal(AIS-P)” (p. 2-119).

Instructions

Proceed as follows to clear an Alarm Indication Signal (AIS-P) alarm:

.................................................................................................................................................................................................

1 Analyze the alarm state of the network elements in the upstream direction of the path,and take appropriate measures.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Path Switch Denial.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Path Switch Denial alarm.

Related information

Please also refer to the corresponding alarm description → “Path Switch Denial”(p. 2-131).

Instructions

Proceed as follows to clear an Path Switch Denial alarm:

.................................................................................................................................................................................................

1 If transmission alarms are reported for the protection line, then clear these alarms first.

Otherwise continue with the next step.

.................................................................................................................................................................................................

2 If a switch request with an equal or higher priority is active, then clear this switchrequest, or accept, that protection switching is currently not possible..

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-145

Clearing Remote Defect Indication (RFI-P).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Remote Defect Indication (RFI-P) alarm.

Related information

Please also refer to the corresponding alarm description → “Remote Defect Indication(RFI-P)” (p. 2-135).

Instructions

Proceed as follows to clear an Remote Defect Indication (RFI-P) alarm:

.................................................................................................................................................................................................

1 Analyze the alarm state of the network elements in the downstream direction of thepath and take appropriate measures.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Remote Defect Indication (THPRDI).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Remote Defect Indication (THPRDI) alarm.

Related information

Please also refer to the corresponding alarm description → “Remote Defect Indication(THPRDI)” (p. 2-137).

Instructions

Proceed as follows to clear a Remote Defect Indication (THPRDI) alarm:

.................................................................................................................................................................................................

1 Analyze the alarm state of the network element at the far-end path termination and takeappropriate measures.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-147

Clearing Server Signal Fail (SSF-P).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Server Signal Fail (SSF-P) alarm.

Related information

Please also refer to the corresponding alarm description → “Server Signal Fail(SSF-P)” (p. 2-140).

Instructions

Proceed as follows to clear a Server Signal Fail (SSF-P) alarm:

.................................................................................................................................................................................................


E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Server Signal Fail (THPSSF).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Server Signal Fail (THPSSF) alarm.

Related information

Please also refer to the corresponding alarm description → “Server Signal Fail(SSF-P)” (p. 2-140).

Instructions

Proceed as follows to clear a Server Signal Fail (THPSSF) alarm:

.................................................................................................................................................................................................


E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-149

Clearing Trace Identifier Mismatch (THPTIM).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Trace Identifier Mismatch (THPTIM) alarm.

Related information

Please also refer to the corresponding alarm description → “Trace Identifier Mismatch(THPTIM)” (p. 2-145).

Before you begin




Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to clear a Trace Identifier Mismatch (THPTIM) alarm:

.................................................................................................................................................................................................

1 Verify that the cross-connections for the path are set up correctly.

.................................................................................................................................................................................................

2 Match the path trace identifier to be sent (at the start of the path) to the expected pathtrace identifier (at the network element reporting the alarm).

You can use the WaveStar® CIT to poll the received path trace identifier and to setthe path trace identifier to be sent and the expected path trace identifier.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Trace Identifier Mismatch (TIM-P).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Trace Identifier Mismatch (TIM-P) alarm.

Related information

Please also refer to the corresponding alarm description → “Trace Identifier Mismatch(TIM-P)” (p. 2-144).

Before you begin




Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to clear a Trace Identifier Mismatch (TIM-P) alarm:

.................................................................................................................................................................................................

1 Verify that the cross-connections for the path are set up correctly.

.................................................................................................................................................................................................

2 Match the path trace identifier to be sent (at the start of the path) to the expected pathtrace identifier (at the network element reporting the alarm).

You can use the WaveStar® CIT to poll the received path trace identifier and to setthe path trace identifier to be sent and the expected path trace identifier.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-151

Clearing Unequipped (THPUNEQ).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Unequipped (THPUNEQ) alarm.

Related information

Please also refer to the corresponding alarm description → “Unequipped (THPUNEQ)”(p. 2-149).

Instructions

Proceed as follows to clear an Unequipped (THPUNEQ) alarm:

.................................................................................................................................................................................................

1 Define the cross-connections consistently.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Unequipped (UNEQ-P).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Unequipped (UNEQ-P) alarm.

Related information

Please also refer to the corresponding alarm description → “Unequipped (UNEQ-P)”(p. 2-147).

Instructions

Proceed as follows to clear an Unequipped (UNEQ-P) alarm:

.................................................................................................................................................................................................

1 Define the cross-connections consistently.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-153

Port-related transmision alarms

Overview.................................................................................................................................................................................................................................

Purpose

This section contains trouble clearing procedures for port-related transmision alarms.

Contents

Clearing Alarm Indication Signal (AIS-L) 3-155

Clearing Excessive Bit Error Ratio 3-156

Clearing Loss of Frame 3-163

Clearing Loss of Frame transp ch egress 3-166

Clearing Loss of Signal 3-167

Clearing OCh Loss of Frame 3-174

Clearing Post DCM Signal Loss 3-175

Clearing Pre DCM Signal Loss 3-176

Clearing Remote Defect Indication (RFI-L) 3-177

Clearing Server Signal Fail (MSSSF) 3-178

Clearing Server Signal Fail Transparent Ch 3-179

Clearing Trace Identifier Mismatch (RSTIM) 3-180

Clearing Trace Identifier Mismatch egress (TIM-T-EGR) 3-181

Clearing WTU3 Loss of Frame 3-183

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Alarm Indication Signal (AIS-L).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Alarm Indication Signal (AIS-L) alarm.

Related information

Please also refer to the corresponding alarm description → “Alarm Indication Signal(AIS-L)” (p. 2-152).

Instructions

Proceed as follows to clear an Alarm Indication Signal (AIS-L) alarm:

.................................................................................................................................................................................................


E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-155

Clearing Excessive Bit Error Ratio.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Excessive Bit Error Ratio alarm.

Related information

Please also refer to the corresponding alarm description → “Excessive Bit Error Ratio(MSEXC)” (p. 2-157).

Before you begin

You or a service technician must be on-site at the NE to clear an Excessive Bit

Error Ratio alarm.




Required equipment

Which equipment is actually required depends on the type of alarm-reporting interfaceport (optical or electrical):

• Optical SDH/SONET interface port

– WaveStar® CIT

– The required equipment to clean optical fiber connectors (see “Cleaning opticalfiber connectors” (p. 4-21))

– An optical power meter

– A network analyzer, if available.

• Electrical STM-1 interface port

– WaveStar® CIT


– A suitable coaxial cable for performing STM-1e loops (the STM-1e interface isa 75 Ω coaxial connector; 1.6/5.6 male)

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Instructions

Proceed as follows to clear an Excessive Bit Error Ratio alarm:

.................................................................................................................................................................................................

1 Has the alarm been reported for an optical or an electrical SDH/SONET interface?

If the alarm has been reportedfor an ...

then ...

optical SDH/SONET interface continue with the next step.

electrical STM-1 interface continue with Step 16.

.................................................................................................................................................................................................

2 DANGER

Laser hazard



Clean the optical fiber connectors and connect properly again.

Reference: “Cleaning optical fiber connectors” (p. 4-21)

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

4 Check the optical receive power using an optical power meter.

Trouble clearing Clearing Excessive Bit Error Ratio

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-157

Reference: Please refer to the LambdaUnite® MSS Applications and PlanningGuide for a specification of the power budgets of the optical interfaces.

.................................................................................................................................................................................................

5 Is the optical receive power (measured with the optical power meter) within thepermissible range?

If ... then ...

Yes Continue with Step 8.

No Continue with the next step.

.................................................................................................................................................................................................

6 Clean the optical connectors of the associated transmit port unit at the far-end NE andconnect properly again.

Reference: “Cleaning optical fiber connectors” (p. 4-21)

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

8 Check the optical transmit power at the far-end NE using an optical power meter.

Please refer to the LambdaUnite® MSS Applications and Planning Guide for aspecification of the power budgets of the optical interfaces.

.................................................................................................................................................................................................

9 Is the optical transmit power at the far-end NE (measured with the optical powermeter) within the permissible range?

If ... then ...

Yes there exists a fault on the transmission path (forinstance defective cabling).


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If ... then ...

No replace the associated transmit unit at the far-endNE.


.................................................................................................................................................................................................

10 Is a network analyzer available for checking the received signal?

If ... then ...

Yes continue with the next step.

No continue with Step 13.

.................................................................................................................................................................................................

11 Using the network analyzer, check if the signal rate of the received signal matches thesignal rate of the port reporting the alarm.

If ... then ...


No assign a suitable transmit unit at the far-end NE.

.................................................................................................................................................................................................

12 Is the Section Overhead (SOH, SDH) or Line Overhead (LOH, SONET) respectivelystructured correctly?

If ... then ...

Yes replace the port unit reporting the alarm.


No the SOH/LOH is not correctly formed at thefar-end NE. Replace the associated transmit portunit at the far-end NE.



.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-159

.................................................................................................................................................................................................

13 Important! When setting up loops, an optical attenuator pad of approx. 10 to 20dB must be used for long-haul optical transmit units.

At the local NE, loop the optical output to the optical input.

.................................................................................................................................................................................................

14 Is the alarm still present?

If ... then ...

Yes replace the port unit reporting the alarm, andre-establish the normal system setup.


No continue with the next step.

.................................................................................................................................................................................................

15 Has the associated transmit unit at the far-end of the Multiplex Section or Linerespectively the same signal rate as the receiving port unit at the local NE?

If ... then ...

Yes the SOH/LOH is not correctly formed at thefar-end NE. Replace the associated transmit unitat the far-end NE.


No assign a suitable transmit plug-in unit at thefar-end NE.

.................................................................................................................................................................................................

16 At the Electrical Connector Interface (ECI/155MP8 or ECI/155ME8), loop the signaloutput to the signal input using a suitable coaxial cable.

.................................................................................................................................................................................................

17 Is the alarm still present?

If ... Then ...

Yes re-establish the normal loop state, and continuewith Step 20.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If ... Then ...

No re-establish the normal loop state and continuewith the next step.

.................................................................................................................................................................................................

18 Check the receive signal using a network analyzer.

.................................................................................................................................................................................................

19 The bit error ratio and the attenuation are they within the permissible range?

If ... then ...


No either the SOH is not correctly formed at the farend, or there exists a fault in the cabling (e.g.wrong coaxial cable).

Clear these external faults.

.................................................................................................................................................................................................

20 Replace the associated Electrical Connector Interface (ECI/155MP8 or ECI/155ME8).

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

22 Replace the port unit reporting the alarm, and re-establish the normal system setup.


.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-161

If then


E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Loss of Frame.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Loss of Frame alarm.

Related information

Please also refer to the corresponding alarm description → “Loss of Frame” (p. 2-160).

Before you begin

You or a service technician should be on-site at the near-end NE and at the far-end NEto clear a Loss of Frame alarm.




Required equipment


• WaveStar® CIT for monitoring both the local (alarm-reporting) NE as well as thefar-end NE.

• A network analyzer, if available.

Instructions

.................................................................................................................................................................................................

1 Is the Optical Channel enabled at the far end?

If then

Yes disable the Optical Channel at the far-end NE.


.................................................................................................................................................................................................


If then



Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-163

.................................................................................................................................................................................................

3 Is a network analyzer available for checking the receive signal?

If then



.................................................................................................................................................................................................

4 Using the network analyzer, check if the signal rate of the received signal matches thesignal rate of the port reporting the alarm.

.................................................................................................................................................................................................

5 Does the signal rate of the received signal match the signal rate of the port reportingthe alarm?

If then


No assign the signal structure correctly at the far-endNE.

.................................................................................................................................................................................................

6 Is the Section Overhead (SOH) of the received signal structured correctly?

If then

Yes replace the receiver circuit pack reporting thealarm.


No replace the associated transmitter circuit pack atthe far-end NE.


The SOH is not correctly formed at the far-end NE.

.................................................................................................................................................................................................

7 At the alarm-reporting port, loop the optical output to the optical input.

Trouble clearing Clearing Loss of Frame

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Reference: “Performing optical fiber loopbacks manually” (p. 4-35)

.................................................................................................................................................................................................


If then


the alarm persists replace the receiver circuit pack reporting thealarm.


.................................................................................................................................................................................................

9 Does the port rate of the transmit port (at the far-end NE) match the port rate of thealarm-reporting receive port?

If then

Yes replace the associated transmitter circuit pack atthe far-end NE.

The SOH is not correctly formed at the far-end NE.

No assign a suitable transmitter circuit pack at thefar-end NE.

.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Loss of Frame

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-165

Clearing Loss of Frame transp ch egress.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Loss of Frame transp ch egress alarm.

Related information

Please also refer to the corresponding alarm description → “Loss of Frame transp chegress” (p. 2-162).

Before you begin




Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to clear a Loss of Frame transp ch egress alarm:

.................................................................................................................................................................................................

1 Check the complete transparent path for the presence of transmission alarms, and if soclear these alarms first.

.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Loss of Signal.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Loss of Signal alarm.

Related information

Please also refer to the corresponding alarm description → “Loss of Signal” (p. 2-164).

Before you begin

You or a service technician must be on-site at the local (alarm-reporting) NE and at thefar-end NE to clear a Loss of Signal alarm.




Required equipment

Which equipment is actually required depends on the type of alarm-reporting interfaceport (optical or electrical):


• Optical SDH/SONET interface port

– The required equipment to clean optical fiber connectors (see “Cleaning opticalfiber connectors” (p. 4-21))

– Optionally, an optical power meter

– A suitable optical fiber for performing manual loopbacks (see “Performingoptical fiber loopbacks manually” (p. 4-35))

• Electrical STM-1 interface port


– A suitable coaxial cable for performing STM-1e loops (the STM-1e interface isa 75 Ω coaxial connector; 1.6/5.6 male)

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-167

Clearing “Loss of Signal” at an optical SDH/SONET port

DANGER

Laser hazard



Proceed as follows to clear a Loss of Signal alarm at an optical SDH/SONET port:

.................................................................................................................................................................................................

1 How to proceed depends on which method you prefer for localizing the cause of thealarm:

If then

you prefer measuring theincoming signal level using anoptical power meter


you prefer performing manualloopbacks


.................................................................................................................................................................................................

2 At the local NE, disconnect the fiber from the optical input of the alarm-reporting port,and measure the optical input power.

If then

the input power is within thepermissible range (higher thanthe minimum receiver sensitivity,and lower than the maximumoverload)

the receiver of the alarm-reporting port unit isdefective. Replace the port unit reporting the alarm.


Reference: For the technical specifications of theoptical port units, please refer to theLambdaUnite® MultiService Switch (MSS)Applications and Planning Guide.“Replacing acircuit pack by a circuit pack of the same type”(p. 4-55)

Trouble clearing Clearing Loss of Signal

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If then

the input power is too low (i.e.lower than the minimum receiversensitivity)

re-connect the fiber, and continue with the nextstep.

.................................................................................................................................................................................................

3 At the far-end NE, disconnect the fiber from the optical output of the transmitting portunit, and measure the optical output power transmitted at that port.

If then

the output power is within thepermissible range


the output power is too low the transmitting port unit at the far end isdefective. Replace the transmitting port unit.



.................................................................................................................................................................................................

4 Check for proper and correct fiber connections.

If then

the fibers are not properlyconnected, or inputs and outputsare mixed up

connect the fibers properly/correctly.


the fibers are properly connected,and inputs and outputs are notmixed up

the Loss of Signal alarm indicates a cable breakalong the route. Localize and repair the cablebreak.


.................................................................................................................................................................................................

5 At the local NE, loop the optical output of the alarm-reporting port to its correspondingoptical input.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-169


.................................................................................................................................................................................................


If then


the alarm persists the receiver of the alarm-reporting port unit isdefective. Replace the port unit reporting the alarm.



.................................................................................................................................................................................................

7 At the far-end NE, loop the optical output of the transmitting port unit to itscorresponding optical input.


.................................................................................................................................................................................................

8 Retrieve the WaveStar® CIT NE Alarm List at the far-end NE.

If then

Loss of Signal is now reportedfor the respective port at the farend

the transmitting port unit at the far end isdefective. Replace the transmitting port unit.



no Loss of Signal is reportedfor the respective port at the farend


.................................................................................................................................................................................................

9 Check for proper and correct fiber connections.

If then

the fibers are not properlyconnected, or inputs and outputsare mixed up

connect the fibers properly/correctly.



.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If then

the fibers are properly connected,and inputs and outputs are notmixed up

the Loss of Signal alarm indicates a cable breakalong the route. Localize and repair the cablebreak.


Clearing “Loss of Signal” at an electrical STM-1 port

Proceed as follows to clear a Loss of Signal alarm at an electrical STM-1 (STM-1E)port:

.................................................................................................................................................................................................

1 At the Electrical Connector Interface (ECI/155MP8 or ECI/155ME8), are the affectedSTM-1E ports connected properly?

If then


No connect the ports properly.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

3 Is a network analyzer available for checking the receive signal?

If then




.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-171

E N D O F S T E P S.................................................................................................................................................................................................

.................................................................................................................................................................................................

4 Check the receive signal using the network analyzer. Is the alarm also detected withthe network analyzer?

If then

Yes there is an external fault, either in the cabling, orthe transmitter at the far end is defective.


.................................................................................................................................................................................................

5 At the Electrical Connector Interface (ECI/155MP8 or ECI/155ME8), loop the signaloutput to the signal input using a suitable coaxial cable.

.................................................................................................................................................................................................


If then

the alarm has cleared there is an external fault, either in the cabling, orthe transmitter at the far end is defective.


.................................................................................................................................................................................................

7 Replace the associated Electrical Connector Interface (ECI/155MP8 or ECI/155ME8).

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

9 Replace the port unit reporting the alarm, and re-establish the normal system setup.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005


.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-173

Clearing OCh Loss of Frame.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an OCh Loss of Frame alarm.

Related information

Please also refer to the corresponding alarm description → “OCh Loss of Frame”(p. 2-166).

Before you begin




Required equipment



Instructions

Proceed as follows to clear an OCh Loss of Frame alarm:

.................................................................................................................................................................................................

1 Make sure that a 10-Gbit/s port is assigned at the far end (assignment by cabling), andthat the Optical Channel is enabled at both ends.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Post DCM Signal Loss.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Post DCM Signal Loss alarm.

Related information

Please also refer to the corresponding alarm description → “Post DCM Signal Loss”(p. 2-168).

Instructions

Proceed as follows to clear a Post DCM Signal Loss alarm:

.................................................................................................................................................................................................

1 Check the cabling (fibers and connectors) between the optical output port of the OP40(TX OUT) and the dispersion compensation module (Post DCM) as well as betweenthe Post DCM and the input port of the optical booster amplifier (OBA IN).

Make sure that all connectors are connected properly.

If required, clean the optical fibers and connectors (see “Cleaning optical fiberconnectors” (p. 4-21)).

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-175

Clearing Pre DCM Signal Loss.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Pre DCM Signal Loss alarm.

Related information

Please also refer to the corresponding alarm description → “Pre DCM Signal Loss”(p. 2-170).

Instructions

Proceed as follows to clear a Pre DCM Signal Loss alarm:

.................................................................................................................................................................................................

1 Check the cabling (fibers and connectors) between the output of the opticalpre-amplifier (OPA OUT) and the dispersion compensation module (Pre DCM) as wellas between the Pre DCM and the optical input port of the OP40 (RX IN).

Make sure that all connectors are connected properly.

If required, clean the optical fibers and connectors (see “Cleaning optical fiberconnectors” (p. 4-21)).

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Remote Defect Indication (RFI-L).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Remote Defect Indication (RFI-L) alarm.

Related information

Please also refer to the corresponding alarm description → “Remote Defect Indication(RFI-L)” (p. 2-172).

Instructions

Proceed as follows to clear an Remote Defect Indication (RFI-L) alarm:

.................................................................................................................................................................................................

1 Analyze the alarm state at the far end of the Multiplex Section or Line respectively,and take appropriate measures.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-177

Clearing Server Signal Fail (MSSSF).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Server Signal Fail (MSSSF) alarm.

Related information

Please also refer to the corresponding alarm description → “Server Signal Fail(MSSSF)” (p. 2-173).

Instructions

Proceed as follows to clear an Server Signal Fail (MSSSF) alarm:

.................................................................................................................................................................................................


E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Server Signal Fail Transparent Ch.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Server Signal Fail Transparent Ch alarm.

Related information

Please also refer to the corresponding alarm description → “Server Signal FailTransparent Ch” (p. 2-174).

Instructions

Proceed as follows to clear an Server Signal Fail Transparent Ch alarm:

.................................................................................................................................................................................................


E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-179

Clearing Trace Identifier Mismatch (RSTIM).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Trace Identifier Mismatch (RSTIM) alarm.

Related information

Please also refer to the corresponding alarm description → “Trace Identifier Mismatch(RSTIM)” (p. 2-175).

Before you begin




Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to clear a Trace Identifier Mismatch (RSTIM) alarm:

.................................................................................................................................................................................................

1 Match the section trace identifier to be sent (at the start of the Regenerator Section(RS) or Section respectively) to the expected section trace identifier (at the networkelement reporting the alarm).

You can use the WaveStar® CIT to poll the received section trace identifier and toset the section trace identifier to be sent and the expected section trace identifier.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Trace Identifier Mismatch egress (TIM-T-EGR).................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Trace Identifier Mismatch egress (TIM-T-EGR)alarm.

Related information

Please also refer to the corresponding alarm description → “Trace Identifier Mismatchegress (TIM-T-EGR)” (p. 2-176).

Before you begin




Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to clear a Trace Identifier Mismatch egress (TIM-T-EGR)alarm:

.................................................................................................................................................................................................

1 Check the complete transparent path for the presence of transmission alarms, and if soclear these alarms first.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

3 Along the complete transparent path, make sure that all cross-connections are correctlyconfigured, and verify the correct cabling.

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-181

.................................................................................................................................................................................................


If then

the cross-connections and thecabling are as desired

proceed with Step 6.

the cross-connections and thecabling are not as desired

correct the cross-connections and/or the cabling,and then proceed with the next step.

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

6 Match the section trace identifier to be sent (at the start of the Regenerator Section(RS) or Section respectively) to the expected section trace identifier (at the networkelement reporting the alarm).

You can use the WaveStar® CIT to poll the received section trace identifier and toset the section trace identifier to be sent and the expected section trace identifier.

Technical support

If you need further technical support, please refer to Appendix A, “Maintenanceservices and technical support”.

Trouble clearing Clearing Trace Identifier Mismatch egress (TIM-T-EGR)

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

E N D O F S T E P S.................................................................................................................................................................................................

Clearing WTU3 Loss of Frame.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an WTU3 Loss of Frame alarm.

Related information

Please also refer to the corresponding alarm description → “WTU3 Loss of Frame”(p. 2-177).

Before you begin




Required equipment



Instructions

Proceed as follows to clear an WTU3 Loss of Frame alarm:

.................................................................................................................................................................................................

1 Make sure that a 40-Gbit/s port is assigned at the far end (assignment by cabling), andthat the Optical Channel is enabled at both ends.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-183


Overview.................................................................................................................................................................................................................................

Purpose

This section contains trouble clearing procedures for ring protection switching alarms.

Contents

Clearing Default K-bytes 3-185

Clearing Duplicate Ring Node 3-190

Clearing Extra Traffic Preempted 3-192

Clearing Improper APS Codes 3-193

Clearing Inconsistent APS Codes 3-197

Clearing Inconsistent Ring Protection Mode 3-202

Clearing Local Squelch Map Conflict 3-203

Clearing Ring Discovery in Progress 3-205

Clearing Ring Protection Switch Suspended 3-207

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Default K-bytes.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Default K-bytes alarm.

Related information

Please also refer to the corresponding alarm description → “Default K-bytes”(p. 2-179).

Before you begin

You or a service technician must be on-site at the NE to clear a Default K-bytes

alarm.




Required equipment


• WaveStar® CIT


Proceed as follows to clear a Default K-bytes alarm:

.................................................................................................................................................................................................

1 At the WaveStar® CIT, open the alarm list.

.................................................................................................................................................................................................

2 Determine the port AID for which the alarm is reported from the AID column of theWaveStar® CIT NE Alarm List.

.................................................................................................................................................................................................

3 Are other alarms, related to BLSR/MS-SPRing protection switching (for example Ring

Incomplete, Ring Discovery in Progress (persistently) or Ring Protection

Switch Suspended), reported at the same time for the same port?

If then

other BLSR/MS-SPRing alarmsare reported at the same time

clear these alarms first (please refer to thecorresponding trouble clearing procedure), and thencontinue with the next step.

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-185

If then

no other BLSR/MS-SPRingalarms are reported


.................................................................................................................................................................................................

4 Refresh the alarm list display by pressing the Refresh button of the NE Alarm Listwindow. Check the alarm list.

If then



.................................................................................................................................................................................................

5 Are other transmission alarms (SD/SF conditions) reported at the same time for thesame port?

If then

other transmission alarms arereported at the same time


no other transmission alarms arereported

continue with Step 7

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

7 Determine the AIDs of the two network elements involved.

Trouble clearing Clearing Default K-bytes

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Refer to the following figure for clarification and further reference. The Default

K-bytes alarm is reported on node A, port q.

.................................................................................................................................................................................................

8 Perform a Forced Switch (FS-R) at the transmitter (node B, port p).

.................................................................................................................................................................................................

9 Check the switch status of the network elements.

If then

the Forced Switch has beenexecuted correctly

remove and re-insert the transmitter circuit pack(node B, port p), and then continue with the nextstep.

the Forced Switch has not beenexecuted correctly

clear the Forced Switch and abort the procedure.

.................................................................................................................................................................................................

10 Wait until the green “ACTIVE” LED on the faceplate of the circuit pack is constantlylit.

.................................................................................................................................................................................................


If then

the alarm has cleared continue with Step 18.


.................................................................................................................................................................................................

12 Replace the transmitter circuit pack (node B, port p) with a circuit pack of the sametype.



A B

q p


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-187

.................................................................................................................................................................................................


.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

15 Replace the alarm-reporting circuit pack (node A, port q) with a circuit pack of thesame type.



.................................................................................................................................................................................................


.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

18 Clear the Forced Switch at the transmitter (node B, port p).

.................................................................................................................................................................................................

19 Check the switch status of the network elements, and determine if the Forced Switchhas been cleared.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

20 If you need further support, please refer to Appendix A, “Maintenance services andtechnical support”.

E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-189

Clearing Duplicate Ring Node.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Duplicate Ring Node alarm.

Related information

Please also refer to the corresponding alarm description → “Duplicate Ring Node”(p. 2-181).

Before you begin

Prior to performing the following trouble clearing procedure, make sure that you have:

• management access via WaveStar® CIT to all ring nodes within the affected ring,and

• at least privilege codes of M4 and P1.

Required equipment


• WaveStar® CIT


Proceed as follows to clear a Duplicate Ring Node alarm:

.................................................................................................................................................................................................

1 Using the WaveStar® CIT, retrieve the ring map (textual or graphical representation).

.................................................................................................................................................................................................

2 Verify if there are more than 16 nodes on the ring.

If then

there are more than 16 nodes onthe ring

reduce the number of ring nodes, and continue withthe next step.

Reference: The maximum number of nodes in aring is restricted to 16 (cf. “Automatic node IDallocation” (p. 2-219)).

the number of ring nodes is equalto or less than 16


Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

4 Verify if there are duplicate NE names (target identifiers, TIDs) on the ring.

If then

there are duplicate NE names rename the corresponding NEs so that all NEnames are unique. Then continue with the nextstep.

there are no duplicate NE names please refer to Appendix A, “Maintenance servicesand technical support”.

.................................................................................................................................................................................................

5 Disable and re-enable the automatic ring discovery for all nodes reporting a Duplicate

Ring Node alarm.

Result: This will trigger a ringmap re-discovery to clear the alarms and to resumeprotection switching.

.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Duplicate Ring Node

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-191

Clearing Extra Traffic Preempted.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Extra Traffic Preempted alarm.

Related information

Please also refer to the corresponding alarm description → “Extra Traffic Preempted”(p. 2-183).

Before you begin

Prior to performing the following trouble clearing procedure, make sure that you havemanagement access via WaveStar® CIT to all ring nodes within the affected ring.

Required equipment


• WaveStar® CIT


Proceed as follows to clear an Extra Traffic Preempted alarm:

.................................................................................................................................................................................................

1 Using the WaveStar® CIT, locate and clear the failure that caused the ring protectionswitch.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Improper APS Codes.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Improper APS Codes alarm.

Related information

Please also refer to the corresponding alarm description → “Improper APS Codes”(p. 2-184).

Before you begin

You or a service technician must be on-site at the NE to clear an Improper APS Codes

alarm.




Required equipment


• WaveStar® CIT


Proceed as follows to clear an Improper APS Codes alarm:

.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................

3 Are other transmission transmission alarms (SD/SF conditions) reported at the sametime for the same port?

If then

Yes Clear these alarms first (please refer to thecorresponding trouble clearing procedure), and thencontinue with the next step.


Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-193

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

5 Check the switch status of the network elements. Are there any switch requests in thenetwork?

If then

there are other switch requests abort the procedure.

there are no other switch requests continue with the next step.

.................................................................................................................................................................................................


Refer to the following figure for clarification and further reference. The Improper

APS Codes alarm is reported on node A, port q.

.................................................................................................................................................................................................


.................................................................................................................................................................................................


If then



A B

q p

Trouble clearing Clearing Improper APS Codes

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................




.................................................................................................................................................................................................


.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................





.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-195

.................................................................................................................................................................................................


.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................


E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Inconsistent APS Codes.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Inconsistent APS Codes alarm.

Related information

Please also refer to the corresponding alarm description → “Inconsistent APS Codes”(p. 2-186).

Before you begin

You or a service technician must be on-site at the NE to clear an Inconsistent APS

Codes alarm.




Required equipment


• WaveStar® CIT


Proceed as follows to clear an Inconsistent APS Codes alarm:

.................................................................................................................................................................................................


.................................................................................................................................................................................................


.................................................................................................................................................................................................

3 Are other alarms, related to BLSR/MS-SPRing protection switching, reported at thesame time for the same port?

If then



Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-197

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................

5 Are other transmission transmission alarms (SD/SF conditions) reported at the sametime for the same port?

If then


No continue with Step 7

.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


Trouble clearing Clearing Inconsistent APS Codes

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Refer to the following figure for clarification and further reference. TheInconsistent APS Codes alarm is reported on node A, port q.

.................................................................................................................................................................................................


.................................................................................................................................................................................................


If then





.................................................................................................................................................................................................


.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................




A B

q p


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-199

.................................................................................................................................................................................................


.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................




.................................................................................................................................................................................................


.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


.................................................................................................................................................................................................



.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................


E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-201

Clearing Inconsistent Ring Protection Mode.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear an Inconsistent Ring Protection Mode alarm.

Related information

Please also refer to the corresponding alarm description → “Inconsistent RingProtection Mode” (p. 2-188).

Before you begin

Prior to performing the following trouble clearing procedure, make sure that you have:

• management access via WaveStar® CIT to all ring nodes pertaining to the affected4-fiber MS-SPRing protection group, and

• at least privilege codes of M4 and P1.

Required equipment


• WaveStar® CIT


Proceed as follows to clear an Inconsistent Ring Protection Mode alarm:

.................................................................................................................................................................................................

1 Define the ring protection mode consistently to either Ring Loopback or ShortenedPath for all nodes on the ring.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Local Squelch Map Conflict.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Local Squelch Map Conflict alarm.

Related information

Please also refer to the corresponding alarm description → “Local Squelch MapConflict” (p. 2-189).

Before you begin




Required equipment


• WaveStar® CIT


Proceed as follows to clear a Local Squelch Map Conflict alarm:

.................................................................................................................................................................................................

1 Make sure that the A-node/Z-node configuration (source/destination node information)is consistently defined for the affected BLSR/MS-SPRing protection group. TheA-node/Z-node configuration can be corrected by modifying the involvedcross-connections using the WaveStar® CIT.

Important! When you are modifying a 2-way cross-connection, then only one leg(direction) of the cross-connection can be modified at a time. Therefore,successively correct the A-node/Z-node configuration for both legs of the 2-waycross-connection.

Example: If, for example, the source and/or destination node names contain quotes,then delete these quotes.

Reference: Please also refer to the LambdaUnite® MultiService Switch (MSS) UserOperations Guide:

• Modifying a cross-connection

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-203

.................................................................................................................................................................................................


If then


the alarm persists perform a controller reset of the CTL.

Reference:

Please refer to:


E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Local Squelch Map Conflict

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Ring Discovery in Progress.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a persistent Ring Discovery in Progress alarm.“Persistent” means that the alarm is present for longer than approximately ten minutes.

Related information

Please also refer to the corresponding alarm description → “Ring Discovery inProgress” (p. 2-193).

Before you begin




Required equipment


• WaveStar® CIT


Proceed as follows to clear a persistent Ring Discovery in Progress alarm:

.................................................................................................................................................................................................




.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................


Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-205









.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Ring Discovery in Progress

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Ring Protection Switch Suspended.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Ring Protection Switch Suspended alarm.

Related information

Please also refer to the corresponding alarm description → “Ring Protection SwitchSuspended” (p. 2-197).

Before you begin




Required equipment


• WaveStar® CIT


Proceed as follows to clear a Ring Protection Switch Suspended alarm:

.................................................................................................................................................................................................

1 At the WaveStar® CIT, open the NE Alarm List, and check if other alarms, related toBLSR/MS-SPRing protection switching (for example Ring Incomplete orInconsistent Ring Protection Mode), are being reported at the same time for thesame port.

If then

other BLSR/MS-SPRing alarmsare reported


no other BLSR/MS-SPRingalarms are reported


.................................................................................................................................................................................................


If then


Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-207

If then


.................................................................................................................................................................................................




.................................................................................................................................................................................................


If then



.................................................................................................................................................................................................










.................................................................................................................................................................................................


If then



Trouble clearing Clearing Ring Protection Switch Suspended

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Ring Protection Switch Suspended

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-209

Synchronisation

Overview.................................................................................................................................................................................................................................

Purpose

This section contains trouble clearing procedures for synchronisation alarms.

Contents

Clearing Circuit Pack Clock Failure 3-211

Clearing Loss of Synchronisation 3-213

Clearing NE Clock Failure 3-214

Clearing Protection Clock Input Fail 3-215

Clearing T4 quality unsufficient 3-217

Clearing Timing Reference Failure 3-219

Clearing Worker Clock Input Fail 3-222

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Circuit Pack Clock Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Circuit Pack Clock Failure alarm.

Related information

Please also refer to the corresponding alarm description → “Circuit Pack ClockFailure” (p. 2-204).

Before you begin

You or a service technician must be on-site at the NE to clear a Circuit Pack Clock

Failure alarm.




Required equipment


• WaveStar® CIT


• A replacement cross-connect and timing unit


Proceed as follows to clear a Circuit Pack Clock Failure alarm:

.................................................................................................................................................................................................

1 Depending on whether one or more circuit packs report the alarm:

If then

the alarm is reported by only onecircuit pack

replace the circuit pack reporting the alarm.

Reference:

Please refer to:

• “Replacing a circuit pack by a circuit pack ofthe same type” (p. 4-55)

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-211

If then

the alarm is reported by severalcircuit packs

replace the cross-connect and timing unit (replacingthe standby circuit pack is sufficient).

Reference:

Please refer to:


.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Circuit Pack Clock Failure

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Loss of Synchronisation.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Loss of Synchronisation alarm.

Related information

Please also refer to the corresponding alarm description → “Loss of Synchronisation”(p. 2-205).

Before you begin

You or a service technician must be on-site at the NE to clear a Loss of

Synchronisation alarm.




Required equipment


• WaveStar® CIT

• An oscilloscope or frequency analyzer

• An STM analyzer

Related information

Please also refer to the LambdaUnite® MultiService Switch (MSS) User OperationsGuide.


Proceed as follows to clear a Loss of Synchronisation alarm:

.................................................................................................................................................................................................

1 Verify the quality of all assigned timing references starting with the timing referencewith the highest priority.


• “Checking external timing references” (p. 3-220)to check the quality of an external timing reference.

• “Checking line timing references” (p. 3-221)to check the quality of a line timing reference.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-213

Clearing NE Clock Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a NE Clock Failure alarm.

Related information

Please also refer to the corresponding alarm description → “NE Clock Failure”(p. 2-206).

Before you begin

You or a service technician must be on-site at the NE to clear a NE Clock Failure

alarm.




Required equipment


• WaveStar® CIT



Proceed as follows to clear a NE Clock Failure alarm:

.................................................................................................................................................................................................

1 Replace the cross-connect and timing unit (replacing the standby circuit pack issufficient).

Important! To clear the alarm, it is sufficient to replace the standby circuit pack.However, both cross-connect and timing units are defective.



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Protection Clock Input Fail.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Protection Clock Input Fail alarm.

Related information

Please also refer to the corresponding alarm description → “Protection Clock InputFail” (p. 2-207).

Before you begin

You or a service technician must be on-site at the NE to clear a Protection Clock

Input Fail alarm.




Required equipment


• WaveStar® CIT




Proceed as follows to clear a Protection Clock Input Fail alarm:

.................................................................................................................................................................................................


If then



Reference:

Please refer to:


Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-215

If then


replace the cross-connect and timing unit in theprotection slot (slot 10, cf. “Configuration rules”(p. 4-66)).

Reference:

Please refer to:


.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Protection Clock Input Fail

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing T4 quality unsufficient.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a T4 quality unsufficient alarm.

Related information

Please also refer to the corresponding alarm description → “T4 quality unsufficient”(p. 2-208).

Before you begin

You or a service technician must be on-site at the NE to clear a T4 quality

unsufficient alarm.




Required equipment


• WaveStar® CIT


• A SONET/SDH Network Tester

Related information

Please also refer to the LambdaUnite® MultiService Switch (MSS)User OperationsGuide for information about timing provisioning.


Proceed as follows to clear a T4 quality unsufficient alarm:

.................................................................................................................................................................................................

1 Verify if other alarms are reported at the same time for the circuit pack that suppliesthe timing reference for the external timing output, for example Circuit Pack

Failure, Loss of Signal, Loss of Frame, Alarm Indication Signal (AIS-L),Excessive Bit Error Ratio (MSEXC) or Degraded Signal (MSDEG).

If then

any of these alarms is reported atthe same time


Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-217

If then

none of these alarms is reportedat the same time


.................................................................................................................................................................................................

2 Now you have the following options to choose from:

1. Select a different timing reference (Provisioned Derived Output Timing SourceSelection) from which the external timing signal shall be derived.

2. Decrease the provisioned quality acceptance level for the external timing output(Acceptance Quality Level for Output Threshold AIS).

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing T4 quality unsufficient

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Clearing Timing Reference Failure.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Timing Reference Failure alarm.

Related information

Please also refer to the corresponding alarm description → “Timing Reference Failure”(p. 2-209).

Nominal values of external timing input signals

The following table provides an overview of the possible external timing input signalsand their characteristics.

External timinginput signal

Frequency or bit rate Signal level Encoding

2 MHz 2048 kHz (± 20 ppm) 1.0 to 1.9 V (120 Ω balancedmode)

0.75 to 0.9 V (75 Ω unbalancedmode)

–

2 Mbit/s (framedor unframed)

2048 kbit/s (± 20 ppm) compliant with ITU-T Rec. G.703(10/98), Telcordia GR-1244, orTelcordia GR-499, respectively

HDB3

DS1 (SF or ESF) 1544 kbit/s (± 20 ppm) B8ZS

Before you begin

You or a service technician must be on-site at the NE to clear a Timing Reference

Failure alarm.




Required equipment


• WaveStar® CIT


• A SONET/SDH Network Tester

Related information

Please also refer to the LambdaUnite® MultiService Switch (MSS)User OperationsGuide.

Trouble clearing

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-219


Proceed as follows:

.................................................................................................................................................................................................

1 Verify the quality of the timing reference concerned.


• “Checking external timing references” (p. 3-220)to check the quality of an external timing reference.

• “Checking line timing references” (p. 3-221)to check the quality of a line timing reference.

Checking external timing references

Perform the following procedure to verify the quality of a timing reference connectedto an external timing input port.

.................................................................................................................................................................................................

1 Disconnect the clock source from the respective external timing input port.

.................................................................................................................................................................................................

2 Measure the supplied clock signal by using an oscilloscope or frequency analyzer, andcompare the measurement results with the desired values given under “Nominal valuesof external timing input signals” (p. 3-219).

.................................................................................................................................................................................................

3 If then

the measurement results complywith the desired values

replace the Timing Interface (TI) associated to theexternal timing input under test.

the measurement results deviatefrom the desired values

repair or replace the station clock supply.

Trouble clearing Clearing Timing Reference Failure

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

E N D O F S T E P S.................................................................................................................................................................................................

E N D O F S T E P S.................................................................................................................................................................................................

Checking line timing references

Perform the following procedure to verify the quality of a timing reference connectedto a line timing input port.

.................................................................................................................................................................................................

1 Verify if other alarms are reported at the same time for the corresponding line timinginput port or the associated circuit pack, for example Circuit Pack Failure, Lossof Signal, Loss of Frame, Alarm Indication Signal (AIS-L), Excessive Bit

Error Ratio (MSEXC) or Degraded Signal (MSDEG).

If then

any of these alarms is reported atthe same time


none of these alarms is reportedat the same time


.................................................................................................................................................................................................

2 Verify the quality of the clock signal, indicated by means of the Synchronization StatusMessage (SSM) in bits 1 to 4 of the S1 byte (S1 [1-4]), by using a SONET/SDHnetwork analyzer.

If then

the quality of the clock signal isbetter than or equal to SEC (forSDH signals) or ST3 (forSONET signals)

replace the receive unit

Reference:

Please refer to:


the quality of the clock signal isless than SEC (for SDH signals)or ST3 (for SONET signals)

check the far-end equipment.

The transmit unit might be defective, or the timingprovisioning might be incorrect.

E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Timing Reference Failure

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-221

Clearing Worker Clock Input Fail.................................................................................................................................................................................................................................

Purpose

Use this procedure to clear a Worker Clock Input Fail alarm.

Related information

Please also refer to the corresponding alarm description → “Worker Clock Input Fail”(p. 2-210).

Before you begin

You or a service technician must be on-site at the NE to clear a Worker Clock Input

Fail alarm.




Required equipment


• WaveStar® CIT


• A replacement cross-connect and timing unit


Proceed as follows to clear a Protection Clock Input Fail alarm:

.................................................................................................................................................................................................


If then



Reference:

Please refer to:


Trouble clearing

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If then


replace the cross-connect and timing unit in theworker slot (slot 9, cf. “Configuration rules”(p. 4-66)).

Reference:

Please refer to:


.................................................................................................................................................................................................


If then



E N D O F S T E P S........................................................................................................................................................................................................................

Trouble clearing Clearing Worker Clock Input Fail

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


3-223

4 4Supporting procedures

Overview.................................................................................................................................................................................................................................

Purpose

This chapter covers tasks that are often used during trouble clearing and additionalrelated information. Instead of describing a trouble clearing task to its fullest extent,the repetitive part is included here in this chapter.

Contents

Retrieving the WaveStar® CIT NE Alarm List 4-3

The WaveStar® CIT NE Alarm List 4-5

Retrieving the WaveStar® CIT NE Alarm Log 4-9

Identifying SDH tributaries in alarm messages 4-10

Replacing the fan unit 4-16

Replacing the air filter 4-18

Cleaning optical fiber connectors 4-21

Cleaning optical fiber couplings 4-23

Performing cross-connection loopbacks 4-25

Releasing a cross-connection loopback 4-28

Performing facility loopbacks 4-30

Releasing a facility loopback 4-33

Performing optical fiber loopbacks manually 4-35

Optical circuit pack parameters 4-37

Retrieving a list of currently active loopbacks 4-40

Restoring a database to a network element 4-43

Replacing a CompactFlash® card 4-48

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-1

Removing a circuit pack from the system 4-53

Replacing a circuit pack by a circuit pack of the same type 4-55

Exchanging a circuit pack without deprovisioning 4-57

Replacing a circuit pack by a circuit pack of a different type 4-60

Replacing the Controller (CTL) 4-62

Replacing a defective optical fiber 4-64

Configuration rules 4-66

Initiating a circuit pack reset 4-76

Initiating a system reset 4-80

Cross-connection loopbacks 4-81

Facility loopbacks 4-84

SDH/SONET tributary numbering 4-87

TXI bus line numbering scheme 4-111

Supporting procedures Overview

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Retrieving the WaveStar® CIT NE Alarm List.................................................................................................................................................................................................................................

Purpose

Use this procedure to retrieve detailled information about the current alarm status of aLambdaUnite® MSS NE by using the WaveStar® CIT.

Related information

For information about the WaveStar® CIT alarm list, please refer to

• “The WaveStar® CIT NE Alarm List” (p. 4-5).

Before you begin

Prior to performing this task, you must:

• have a valid user login and password,

• be connected to the corresponding NE, and

• have proper access privileges to perform this task.

Required privilege

You must have at least a privilege code of M1 to retrieve the WaveStar® CITNE Alarm List.

Required equipment

The following equipment is required to perform this task:

• WaveStar® CIT

Instructions

Proceed as follows to retrieve the WaveStar® CIT NE Alarm List:

.................................................................................................................................................................................................

1 From the WaveStar® CIT, invoke the NE Alarm List by either:

• pressing the Alarm List button in the upper right area of the System View window,or

• selecting Fault → NE Alarm List in the System View main menu, or

• selecting Reports → NE Alarm List in the System View main menu.

Supporting procedures

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-3

Result: The NE Alarm List window will be opened.

The NE Alarm List reflects the current alarm status at the time when it is invoked.

.................................................................................................................................................................................................

2 To make sure that the NE Alarm List reflects the current alarm status, click

• the Refresh button in the NE Alarm List window or

• again the Alarm List button

as soon as you observe changes in the alarm status display in the lower left corner ofthe System View window, or whenever you are unsure whether the alarm list is stillsynchronized to the current alarm status.

.................................................................................................................................................................................................

3 The following options are avaialable:

If then

you want to store the currentlydisplayed alarm list as a standardtext file (ASCII format)

click the Save As button and specify a filenameand a destination.

you want to print out thecurrently displayed alarm list

click the Print button and specify a printer.

you want to dismiss the window click the Close button.

you want to update the alarm list click the Refresh button or again the Alarm Listbutton (cf. Step 2).

you want to get online helpinformation

click the Help button.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Retrieving the WaveStar® CIT NE Alarm List

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

The WaveStar® CIT NE Alarm List.................................................................................................................................................................................................................................

The “NE Alarm List” window

The WaveStar® CIT provides a list of current alarms, the NE Alarm List, to retrievedetailed information about the current alarm status of a LambdaUnite® MSS networkelement (NE).

Structure of the “NE Alarm List”

The following table explains the structure of the WaveStar® CIT NE Alarm List.

Column Meaning

Alarm Level This column indicates the alarm severity.

Possible values are:

• Critical/Major/Minor (CR/MJ/MN), or

• Prompt/Deferred/Info (PR/DF/INF).

PR/DF/INF is the default setting for LambdaUnite® MSS systems.

AID This column indicates the alarm issue point, i.e. the access identifier (AID) ofthe component for which an alarm is being reported (“exttmg1”,“1-1-#-#-ctlw-nvm” or “1-1-#-#-12-v4” for example).

Please note that a special display format is being used for SDH tributary AIDs,please refer to “Identifying SDH tributaries in alarm messages” (p. 4-10).

Date

Time

These two columns indicate the date and time of occurrence, i.e. the date andtime the alarm was reported by the NE.

The date and time format depends on the country in which the WaveStar® CITis being used.

Effect on Service This column indicates whether the corresponding alarm is service affecting ornot. Possible values are:

• service affecting (SA),

• not service affecting (NSA),

• not applicable (-).

Probable Cause This column indicates the alarm short designation. A more detailed descriptionof the alarm’s probable cause can be found in the Description column.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-5

Column Meaning

Signal LevelAffected

This column indicates the affected signal level for communication alarms orthe type of alarm otherwise. Possible values are:

• COMCommonAlarms that apply to the system as a whole, processing errors for example.

• ENVEnvironmental (Miscellaneous Discrete Inputs)

• EQPTEquipment

• OC-3, OC-12,OC-48, OC-192, OC-768Optical transport signals (SONET): OC-3 (155 Mbit/s), OC-12(622 Mbit/s), OC-48 (2.5 Gbit/s), OC-192 (10 Gbit/s) or OC-768(40 Gbit/s)

• OUTTOutput timing

• STM-1, STM-4, STM-16, STM-64, STM-256Optical transport signals (SDH): STM-1 (155 Mbit/s), STM-4 (622 Mbit/s),STM-16 (2.5 Gbit/s), STM-64 (10 Gbit/s), or STM-256 (40 Gbit/s)

• STM-1ESTM-1 electrical (155 Mbit/s)

• STM-16T, OC-48T2.5 Gbit/s fully transparent service

• STS-1, STS-3C, STS-12C, STS-48C, STS-192CPayload signals (SONET): STS-1, STS-3c, STS-12c, STS-48c or STS-192c

• SYSTSystem timing

• T3DS3 signal

• VC-3, VC-4, VC-4-4C, VC-4-16C, VC-4-64CPayload signals (SDH): VC-3, VC-4, VC-4-4C, VC-4-16C or VC-4-64C

• 1GE1-Gbit/s Ethernet

• VCGVirtual Concatenation Group (VCG) tributary

Supporting procedures The WaveStar® CIT NE Alarm List

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Column Meaning

Alarm Type This column indicates the alarm category. The alarm category indicates thefunctional area to which an alarm belongs.

The NE alarms are assigned to the following alarm categories:

• Communication

This alarm category comprises DCN, synchronisation and transmissionalarms. Therefore, the “Communication” alarm category is further dividedinto:– Communication (DCN)– Communication (Synchronisation)– Communication (Transport)

• EnvironmentThis alarm category is used for environmental alarms, detected by means ofMiscellaneous Discrete Inputs (MDIs).

• EquipmentThis alarm category is used for hardware- and configuration-related alarmsand alarms concerning the internal communication.

• Processing errorThis alarm category is used for alarms related to problems or failures of thecontrol system software, due to overload situations for example.

Description This column describes the alarm’s probable cause in more detail.

Notes:

1. The sequence of alarm list columns in this table reflects the ordering of the columns (from left to right)in the default alarm list display.

2. The ordering of the columns in the alarm list display can be modified by clicking on the column header,holding down the mouse button, and dragging the column to the desired position.

3. The column width can be resized by selecting the small outside margin of a column with the mouse,holding down the mouse button, and adjusting the column’s width.

Buttons and actions

The NE Alarm List window provides the following pushbuttons:

1. Save AsUse this button to store the currently displayed alarm list as a standard text filewhich may then be used for editing and further processing.

2. PrintUse this button to print out the currently displayed alarm list.

3. CloseUse this button to close the window.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-7

4. RefreshClicking the Refresh button causes the WaveStar® CIT to retrieve the alarminformation from the NE again to update the alarm list.Notice that there is a difference between the Refresh button and the UpdateAlarms button beside the Alarm List button. The Update Alarms button can onlybe used to manually refresh the alarm status display, not the alarm list.

5. HelpUse this button to get online help information specific to the NE Alarm Listwindow.

Alarm signaling after a CTL protection switch

After a CTL protection switch, all currently present alarms are redetected and reportedagain. As a consequence the alarm signaling is as follows:

• All currently present alarms, including those that were previously acknowledged bymeans of the ACO button on the user panel, will be signaled again by the userpanel LEDs and the office alarm interfaces.

• In the NE Alarm List, the same alarms are listed as before the CTL protectionswitch. They are, however, marked with a new timestamp.

• In the NE Alarm Log, alarms may appear twice, but with different timestamps,without a clear notification between the two log entries.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Retrieving the WaveStar® CIT NE Alarm Log.................................................................................................................................................................................................................................

Purpose

Use this procedure to retrieve alarm history information by using the WaveStar® CIT.

The WaveStar® CIT “NE Alarm Log”

The WaveStar® CIT NE Alarm Log window provides a detailled alarm history foreach LambdaUnite® MSS NE. The most recent alarms, up to 1024 alarms ordered bytheir date and time of occurrence, are stored in the NE alarm log. The informationcontained is presented in an identical fashion as in the NE alarm list; please refer to“The WaveStar® CIT NE Alarm List” (p. 4-5).

Before you begin





Required privilege

You must have at least a privilege code of M1 to retrieve the NE Alarm Log.

Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to retrieve the NE Alarm Log:

.................................................................................................................................................................................................

1 From the WaveStar® CIT, invoke the NE Alarm Log by either:

• selecting Fault → NE Alarm Log... in the System View main menu, or

• selecting Reports → NE Alarm Log... in the System View main menu.

Result: The NE Alarm Log window will be opened.

E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-9

Identifying SDH tributaries in alarm messages.................................................................................................................................................................................................................................

Purpose

Use this procedure to uniquely identify SDH tributaries in case of tributary alarmsreported in the WaveStar® CIT NE Alarm List or NE Alarm Log.

Representation of SDH tributaries in alarm messages

When tributary alarms are reported, the alarm messages in the WaveStar® CIT NEAlarm List or NE Alarm Log contain the signal level affected, but not the port type.Therefore, a five-digit representation is used for SDH tributary AIDs to facilitate thecorrect identification of SDH tributaries. Please also refer to “SONET and SDHtributary numbering format” (p. 4-12).

Each of the five digits represents a particular VC-N level:

The possible values of the individual digits are as follows:

Digit Value Meaning

10 no VC-3

1, 2 or 3 the first, second or third VC-3 within an STM-1 frame.

20 no VC-4

1, 2, 3 or 4 the first, second, third or fourth VC-4 within thecorresponding STM-4 frame.

* An asterisk represents either a “1” or a fill characterwhich can be ignored (if the second digit is notrequired, in the case of an STM-1 interface port forexample).

45 3 2 1

1/3 STM-1

STM-1STM-N bandwithequivalentSTM-4

VC-4-6

4CVC-4

-16C

VC-4-4

CVC-4

VC-3

STM-16

STM-64


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Digit Value Meaning

30 no VC-4-4C

1, 2, 3 or 4 the first, second, third or fourth VC-4-4C within thecorresponding STM-16 frame.

* An asterisk represents either a “1” or a fill characterwhich can be ignored (if the third digit is not required,in the case of an STM-1 or STM-4 interface port forexample).

40 no VC-4-16C


* An asterisk represents either a “1” or a fill characterwhich can be ignored (if the fourth digit is notrequired, in the case of an STM-1, STM-4 or STM-16interface port for example).

50 no VC-4-64C


* An asterisk represents either a “1” or a fill characterwhich can be ignored (if the fifth digit is not required,in the case of an STM-1, STM-4, STM-16 or STM-64interface port for example).

Required number of digits

Depending on the STM level of an SDH port, a different number of digits is requiredto uniquely identify the tributaries contained.

STM-256 interface port All five digits are required.

STM-64 interface port Four digits are required.

STM-16 interface port or 1-Gbit/sEthernet port

Three digits are required.

STM-4 interface port Two digits are required.

STM-1 interface port Only the last digit is required.

Supporting procedures Identifying SDH tributaries in alarm messages

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-11

Examples

These are examples of the WaveStar® CIT numbering format of SDH tributaries inalarm messages:

1-3-u-#-06-1-**20 This is an STM-16 port (three digits are required): Theasterisk at position 3 represents a “1”, the asterisk at position4 can be ignored. Therefore, the AID indicates a VC-4 in thesecond STM-1 of the first STM-4 within the STM-16 frame.

1-3-u-#-04-1-***3 This is an STM-16 port (three digits are required): Theasterisks at positions 2 and 3 represent a “1”, the asterisk atposition 4 can be ignored. Therefore, the AID indicates thethird VC-3 in the first STM-1 of the first STM-4 within theSTM-16 frame.

SONET and SDH tributary numbering format

A special numbering format is used for SDH tributaries (VC-3, VC-4, VC-4-4C,VC-4-16C and VC-4-64C) whereas the SONET tributary numbering format isrelatively straight-forward:

Interface port rate Tributary rate Tributary AID

SONET format SDH format

OC-3/STM-1 STS-3c/VC-4 1 0

STS-1/VC-3 1, 2, 3 1, 2, 3

OC-12/STM-4 STS-12c/VC-4-4C 1 00

STS-3c/VC-4 1, 4, 7, 10 10, 20, 30, 40

STS-1/VC-3 1, 2, 3, 4, , 12 11, 12, 13,

21, 22, 23,

31, 32, 33,

41, 42, 43


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



OC-48/STM-16 STS-48c/VC-4-16C 1 000

STS-12c/VC-4-4C 1, 13, 25, 37 100, 200, 300, 400

STS-3c/VC-4 1, 4, 7, 10, , 46 110, 120, 130, 140,

210, 220, ,

, 430, 440

STS-1/VC-3 1, 2, 3, 4, , 48 111, 112, 113,

121, 122, 123,

,

441, 442, 443

OC-192/STM-64 STS-192c/VC-4-64C 1 0000

STS-48c/VC-4-16C 1, 49, 97, 145 1000, 2000, 3000,4000

STS-12c/VC-4-4C 1, 13, 25, 37, , 181 1100, 1200, 1300,1400,

2100, 2200, ,

, 4300, 4400

STS-3c/VC-4 1, 4, 7, 10, , 190 1110, 1120, 1130,1140,

1210, 1220, ,

, 4430, 4440

STS-1/VC-3 1, 2, 3, 4, , 192 1111, 1112, 1113,

1121, 1122, 1123,

,

4441, 4442, 4443


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-13



OC-768/STM-2561 STS-768c/VC-4-256C 1 00000

STS-192c/VC-4-64C 1, 193, 385, 577 10000, 20000, 30000,40000

STS-48c/VC-4-16C 1, 49, 97, 145, , 721 11000, 12000, 13000,14000,

21000, 22000, ,

, 43000, 44000

STS-12c/VC-4-4C 1, 13, 25, 37, , 757 11100, 11200, 11300,11400,

12100, 12200, ,

, 44300, 44400

STS-3c/VC-4 1, 4, 7, 10, , 766 11110, 11120, 11130,11140,

11210, 11220, ,

, 44430, 44440

STS-1/VC-3 1, 2, 3, 4, , 768 11111, 11112, 11113,

11121, 11122, 11123,

,

44441, 44442, 44443

1 Gbit/s (Ethernet) STS-3c/VC-4 1, 4, 7, 10, 13, 16, 19 110, 120, 130, 140,

210, 220, 230

STS-1/VC-3 1, 2, 3, 4, , 24 111, 112, 113,

121, 122, 123,

,

241, 242, 243

Notes:

1. STM-256 and OC-768 ports are not supported in LambdaUnite® MSS Release 1.0


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

How to identify SDH tributaries in alarm messages

Proceed as follows to identify the correct tributary from the SDH tributary AIDrepresentation in the WaveStar® CIT NE Alarm List or NE Alarm Log:

.................................................................................................................................................................................................

1 Determine the port type by means of the slot information in the AID and by usingoffice records or the WaveStar® CIT System View window for example.

.................................................................................................................................................................................................

2 Depending on the port unit type, determine the number of required digits in thetributary AID representation (cf. “Required number of digits” (p. 4-11)).

All required digits with an asterisk represent “1”, all other digits with an asterisk canbe ignored.

Please also refer to “SONET and SDH tributary numbering format” (p. 4-12).

E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-15

Replacing the fan unit.................................................................................................................................................................................................................................

Purpose

Use this procedure to replace the fan unit only when instructed to do so as part of atrouble-clearing procedure.

Before you begin

Perform the following procedure from the rear side of the shelf.

Required equipment

The following equipment is required to perform this procedure:

• A replacement fan unit.

Instructions

CAUTION

A network element may fail without proper cooling.

Leaving the fan unit out of operation for more than two minutes may cause therespective network element to fail.

Never remove the fan unit unless you already have a replacement fan unit in hand andimmediately perform the replacement, as instructed in this procedure.

Proceed as follows to replace the fan unit.

.................................................................................................................................................................................................

1 At the rear side of the shelf, locate the replacement fan unit within easy reach.

.................................................................................................................................................................................................

2 With your fingers, loosen the screws (1) of the fan unit drawer.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Refer to the following figure for clarification and further reference.

.................................................................................................................................................................................................

3 Disconnect the power supply cables and the fan unit control cable.

.................................................................................................................................................................................................

4 Slide the fan unit drawer from its position by using the handles (2).

.................................................................................................................................................................................................

5 Take the fan unit from the fan unit drawer.

.................................................................................................................................................................................................

6 Place the replacement fan unit into the fan unit drawer, and slide the fan unit drawerback into the shelf.

.................................................................................................................................................................................................

7 Re-connect the power supply cables and the fan unit control cable.

.................................................................................................................................................................................................

8 With your fingers, fasten the screws (1) of the fan unit drawer.

E N D O F S T E P S........................................................................................................................................................................................................................

(1)

(2)

(1)

Supporting procedures Replacing the fan unit

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-17

Replacing the air filter.................................................................................................................................................................................................................................

When to use

Use this procedure:

• Every 3 months, as a part of routine fan maintenance.

• When instructed to do so as a part of a trouble-clearing task.

Air filter position

The following figure illustrates the postion of the air filter (1) in the NE rack:

12


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Air filter types

Two air filter types can be used

• Filter washable — DC1002025

• Filter disposable — DC1002027

Before you begin


• A replacement air filter (either a new or a cleaned air filter)

Instructions

Complete the following steps to replace the air filter.

.................................................................................................................................................................................................

1 Rotate the (one) locking/pull tab (in the middle of the filter) to a horizontal position.

.................................................................................................................................................................................................

2 Remove the air filter by grasping the locking/pull tab and pulling the air filter out ofthe subrack.

.................................................................................................................................................................................................

3 Insert the replacement air filter into the shelf so that the locking/pull tab is positionedat the rear of the subrack.

.................................................................................................................................................................................................

4 Rotate the locking/pull tab until the air filter is locked in place.

.................................................................................................................................................................................................

5 Discard or clean the dirty air filter.

There are four easy ways recommended to clean Universal’s Windowpane,Quadrafoam and Uni-Foam Air Filters:

1. Cleaning using a vacuum cleanerA few passes of a vacuum cleaner will remove accumulated dust and dirt inseconds.

2. Cleaning using compressed airPoint compressed air nozzle in opposite direction of operating air flow (blowfrom exhaust side toward intake side).

Supporting procedures Replacing the air filter

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-19

3. Cleaning using cold waterUnder normal conditions the foam media used in Universal’s Windowpane,Quadrafoam and Uni-Foam filters require no oily adhesives. Collected dirt iswashed away quickly and easily using just a standard hose nozzle with plainwater.

4. Cleaning using warm, soapy waterWhere stubborn air-borne dirt is present, the filter may be dipped in a solutionof warm water and mild detergent. Then simply rinse in clear water, let standuntil completely dry and free of moisture, and return to service.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Replacing the air filter

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Cleaning optical fiber connectors.................................................................................................................................................................................................................................

Before you begin

Make sure that the required equipment listed below is available before you begincleaning the optical fiber connectors.

Required equipment


• Isopropanol,

• Smooth tissues,

• Purified compressed air (optional),

• Microscope with a magnification x 200,

• Coupling cleaner (e.g. a cotton bud or cotton-wool swab),

• Tape dispenser.

Instructions

DANGER

Laser hazard


Never look into the end of an exposed fiber or into an open optical connector as longas the optical source is switched on. Always observe the laser warning instructionsgiven in the safety guide.

CAUTION

Injury to eyes caused by invisible laser radiation.

Optical fiber cables will break if the bending radius is too small.

To avoid cable break ensure that the bending radius of optical fiber cables is not lessthan 30 mm.

Proceed as follows to clean the optical fiber connectors:

.................................................................................................................................................................................................

1 Wipe off the connector face lengthwise (not with a circular motion!) using a smoothtissue (moistened with isopropanol).


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-21

.................................................................................................................................................................................................

2 Wipe off the connector face lengthwise (not with a circular motion!) using a dry andsmooth tissue.

.................................................................................................................................................................................................

3 Let the connector face air-dry (the isopropanol must evaporate completely!).

As an option, purified compressed air can also be used for drying.

.................................................................................................................................................................................................

4 If necessary, the connector face can additionally be dabbed on the tape dispenser.

.................................................................................................................................................................................................

5 Check the connector face for cleanliness using the microscope.

Do not connect the optical connectors without having checked them for impuritiesunder the microscope!

.................................................................................................................................................................................................

6 If the connector impurities were not removed completely during the first cleaningprocedure, repeat the preceding steps until the result is satisfactory.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Cleaning optical fiber connectors

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Cleaning optical fiber couplings.................................................................................................................................................................................................................................

Before you begin

Make sure that the required equipment listed below is available before you begincleaning the optical fiber couplings.

Required equipment


• Isopropanol,

• Coupling cleaner (e.g. a cotton bud or cotton-wool swab),

Instructions

DANGER

Laser hazard



CAUTION

Injury to eyes caused by invisible laser radiation.

Optical fiber cables will break if the bending radius is too small.

To avoid cable break ensure that the bending radius of optical fiber cables is not lessthan 30 mm.

Proceed as follows to clean the optical fiber connectors:

.................................................................................................................................................................................................

1 Soak the coupling cleaner in isopropanol and move it back and forth in the couplingseveral times.

.................................................................................................................................................................................................

2 Let the optical fiber coupling air-dry (the isopropanol must evaporate completely!).

Important! Lightguide build-outs (LBOs) may be damaged when compressed air isused for drying. Therefore, do not use compressed air for drying LBOs.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-23

.................................................................................................................................................................................................

3 Check the optical fiber coupling for residual impurities by holding it to the light.

The geometry of the coupling does not allow it to be checked under the microscope.

.................................................................................................................................................................................................

4 If necessary, repeat the preceding steps until the result is satisfactory.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Cleaning optical fiber couplings

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Performing cross-connection loopbacks.................................................................................................................................................................................................................................

Purpose

Use this procedure to operate cross-connection loopbacks.

Related information

Please also refer to “Cross-connection loopbacks” (p. 4-81).

Before you begin





Observe the rules for performing a cross-connection loopback (see “Cross-connectionloopbacks” (p. 4-81)).

Required privilege

You must have at least privilege codes of S1 and P2 and M3 to perform or releasecross-connection loopbacks.

Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to operate a cross-connection loopback:

.................................................................................................................................................................................................

1 Select Fault → Analysis → Cross-Connect Loopback from the WaveStar® CITSystem View main menu.

Result: The Crossconnect Loopback equipment selection window opens.

.................................................................................................................................................................................................

2 Select the desired tributary from the Crossconnect Loopback equipment selectionwindow, and click Select.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-25

Result: The crossConnect Loopback window opens. The AID of the selectedtributary and the type of the respective port are displayed in the Tributary AID andPort Type/Rate fields.

.................................................................................................................................................................................................

3 By means of the display-only fields in the upper region of the window (Tributary AID,Port Type/Rate), verify that you selected the desired tributary.

.................................................................................................................................................................................................

4 Select the signal rate of the cross-connection loopback to be operated by means of theLoopback Rate drop-down list box.

Additional information Depending on the selected tributary, the selection choicesfor the loopback rate will automatically be restricted to suitable rates.

.................................................................................................................................................................................................

5 Whether you are going to perform a “normal” or a forced cross-connection loopbackdepends on the Cross Connect Status (display only filed below the Loopback Ratedrop-down list box):

If then

the Cross Connect Status is No there is currently no cross-connection for theselected tributary. You are going to perform a“normal” cross-connection loopback.

the Cross Connect Status is Yes there is currently a cross-connection for theselected tributary. You are going to perform aforced cross-connection loopback.

.................................................................................................................................................................................................

6 Verify that the Cross Connect Loopback Status is No Loopback (there is currentlyno cross-connection loopback active for the selected tributary).

.................................................................................................................................................................................................

7 Click Operate to perform the cross-connection loopback (“normal” or forcedcross-connection loopback; cf. Step 5).

.................................................................................................................................................................................................

8 Important! Operating a cross-connection loopback, especially a forcedcross-connection loopback, may be service affecting!

Supporting procedures Performing cross-connection loopbacks

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If you want to proceed, confirm your selection by clicking Yes in the confirmationwindow that opens.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Performing cross-connection loopbacks

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-27

Releasing a cross-connection loopback.................................................................................................................................................................................................................................

Purpose

Use this procedure to dismantle (release) a cross-connection loopback.

Related information

Please also refer to “Cross-connection loopbacks” (p. 4-81).

Before you begin





Required privilege

You must have at least privilege codes of S1 and P2 and M3 to perform or releasecross-connection loopbacks.

Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to release a cross-connection loopback:

.................................................................................................................................................................................................

1 Select Fault → Analysis → Cross-Connect Loopback from the WaveStar® CITSystem View main menu.

Result: The Crossconnect Loopback equipment selection window opens.

.................................................................................................................................................................................................

2 Select the desired tributary from the Crossconnect Loopback equipment selectionwindow, and click Select.

Result: The crossConnect Loopback window opens. The AID of the selectedtributary and the type of the respective port are displayed in the Tributary AID andPort Type/Rate fields.

.................................................................................................................................................................................................

3 By means of the display-only fields in the upper region of the window (Tributary AID,Port Type/Rate), verify that you selected the desired tributary.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

4 Select the signal rate of the cross-connection loopback to be released by means of theLoopback Rate drop-down list box.

Additional information Depending on the selected tributary, the selection choicesfor the loopback rate will automatically be restricted to suitable rates.

.................................................................................................................................................................................................

5 Verify that you selected the correct tributary, and that the Cross Connect LoopbackStatus is Loopback Running.

.................................................................................................................................................................................................

6 Click Release, if you want to dismantle the cross-connection loopback on therespective tributary, and confirm your selection by clicking Yes in the confirmationwindow that opens.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Releasing a cross-connection loopback

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-29

Performing facility loopbacks.................................................................................................................................................................................................................................

Purpose

Use this procedure to operate near-side or far-side facility loopbacks.

Related information

Please also refer to “Facility loopbacks” (p. 4-84).

Before you begin





Required privilege

You must have at least privilege codes of S1 and P1 and M3 to perform or releasefacility loopbacks.

Required equipment


• WaveStar® CIT

Instructions

Important! If you want to switch a facility loopback on a port involved in aLine/MS protection scheme (Line protection, MSP), it is highly recommended toput the corresponding protection group in the lockout or forced switch state beforeswitching the facility loopback to avoid an unintended protection switch or failureof protocol (FOP) events.

Proceed as follows to operate a near-side or far-side facility loopback:

.................................................................................................................................................................................................

1 Make sure that the port on which you want to operate a facility loopback is notassigned/locked as timing reference, and that no DCC is enabled for that port.

.................................................................................................................................................................................................

2 By using the WaveStar® CIT, set the port into the out-of-service state proceedingaccording to one of the following options:

• Option 1

1. Select Configuration → Provision from the System View main menu,

2. choose the port on which you want to operate a facility loopback from theequipment selection window, and


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

3. click Provision.

4. In the Provision Parameters for Protection Group or Equipment window, setthe Service Condition to Out Of Service.

• Option 2

1. In the System View, right-click on the alarm LED of the port on which youwant to operate a facility loopback.

2. In the pop-up menu that opens, select the Provision Port # menu item (“#”represents the port number).

3. In the Provision Port window, set the Service Condition to Out Of Service.

.................................................................................................................................................................................................

3 Proceed according to one of the following options to invoke the Facility Loopbackwindow from the WaveStar® CIT:

• Option 1

1. Select Fault → Analysis → Facility Loopback from the System View mainmenu,

2. choose the port on which you want to operate a facility loopback from theequipment selection window that will be opened, and

3. click Select.

• Option 2

1. In the System View, right-click on the alarm LED of the port on which youwant to operate a facility loopback.

2. In the pop-up menu that opens, select the Facility Loopback menu item.

.................................................................................................................................................................................................

4 By means of the read-only fields in the upper region of the window (Port AID, PortType/Rate, Facility Loopback Status), verify that you selected the desired port, andthat no loopback is currently active.

.................................................................................................................................................................................................

5 Select the type of facility loopback to be operated by means of the Facility LoopbackType checkboxes:

• Nearside Facility or

• Farside Facility.

.................................................................................................................................................................................................

6 Click the button in the lower left-hand-side corner of the window which may belabelled either Operate or Force.

The button will be labelled Operate if the corresponding port is an optical port, isprotected and not active, and if the switch request state is “Lockout of protection”.Otherwise it will be labelled Force.

Supporting procedures Performing facility loopbacks

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-31

.................................................................................................................................................................................................

7 Important! Operating a facility loopback may be service affecting!

If you want to proceed, confirm your selection by clicking Yes in the confirmationwindow that will be opened.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Performing facility loopbacks

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Releasing a facility loopback.................................................................................................................................................................................................................................

Purpose

Use this procedure to dismantle (release) a near-side or far-side facility loopback.

Before you begin





Required privilege

You must have at least privilege codes of S1 and P1 and M3 to perform or releasefacility loopbacks.

Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to dismantle a facility loopback:

.................................................................................................................................................................................................

1 Proceed according to one of the following options to invoke the Facility Loopbackwindow from the WaveStar® CIT:

• Option 1

– Select Fault → Analysis → Facility Loopback from the System View mainmenu,

– choose the port on which you want to dismantle a facility loopback from theequipment selection window that will be opened, and

– click Select.

• Option 2

– In the shelf display, right-click on the alarm LED of the port on which youwant to dismantle a facility loopback.

– In the pop-up menu that opens, select the Facility Loopback menu item.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-33

Result: The Facility Loopback window will be opened. The read-only fields in theupper region of the window (Port AID, Port Type/Rate, Facility LoopbackStatus) indicate the selected port and whether a facility loopback is currentlyactive. In the Facility Loopback Type field, the type of facility loopback currentlybeing active is shown.

.................................................................................................................................................................................................

2 Click the Release button if you want to dismantle the indicated type of facilityloopback on the respective port.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Releasing a facility loopback

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Performing optical fiber loopbacks manually.................................................................................................................................................................................................................................

Purpose

Front access to the optical connectors on the optical circuit pack faceplates allowsmanual optical loopbacks. These loopbacks are performed by connecting an opticaloutput port to the corresponding optical input port.

Manual loopbacks are similar in function to far-side facility loopbacks. The advantageof a manual loopback is that the entire signal path is tested including the physicalinterface.

Before you begin

Important! If a fiber loop is made between an input and an output on the sameGigabit Ethernet port or between Gigabit Ethernet ports on the same circuit packthere is a chance that all Gigabit Ethernet transmission over the loop is blocked.The chance of occurrence depends on the length of the fiber. It is recommended touse a fiber of approximately 3 meters or 6-7 meters.

Make sure that the required equipment listed below is available before you begin.

Required equipment


• Clean protection caps to cover the fiber endfaces of the optical interfaces,

• Suitable optical fiber (“loopback cable”), see LambdaUnite® MSS InstallationGuide,

• Suitable optical attenuator (see “Optical circuit pack parameters” (p. 4-37)).

Instructions

DANGER

Laser hazard



Important! The normal traffic will be interrupted during a manual loopback.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-35

Proceed as follows to manually perform a loopback on an optical port unit:

.................................................................................................................................................................................................

1 Determine the required optical attenuation depending on the selected optical circuitpack type (please refer to “Optical circuit pack parameters” (p. 4-37)).

.................................................................................................................................................................................................

2 At the circuit pack faceplate, remove the optical connections from both the opticalinput and output and cover the fiber endfaces with protection caps.

Make a record of these disconnections so they can be re-established after the loopback.

.................................................................................................................................................................................................

3 Mount the optical attenuator at the optical input and cover it with a protection cap.

.................................................................................................................................................................................................

4 Equip the loopback cable with optical connectors.

.................................................................................................................................................................................................

5 Clean all optical fiber endfaces, connectors and couplings (please refer to “Cleaningoptical fiber connectors” (p. 4-21) and “Cleaning optical fiber couplings” (p. 4-23)).

.................................................................................................................................................................................................

6 Connect one end of the loopback cable to the port unit input.

.................................................................................................................................................................................................

7 Connect the other end of the loopback cable to the port unit output.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Performing optical fiber loopbacks manually

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Optical circuit pack parameters.................................................................................................................................................................................................................................

Optical parameters and recommended attenuation

The following tables provide an overview of the transmitter output power ranges andthe permitted receiver input power ranges (receiver sensitivity) for the different opticalcircuit packs as well as a recommendation for the optical attenuation that should beused when performing manual loopbacks.

40-Gbit/s circuit packs

These are the relevant optical parameters of the 40-Gbit/s circuit packs:

App. Code Functional name Transmitter output powerrange [dBm]

Receiver input powerrange [dBm]

Recommendedattenuation [dB]

KFA3 OP40/1.5LR1O +10 +13 −14 +2 15

KFA202 OP40/1.3IOR1 +5 +7 −2 +4 5

KFA290

KFA353OP40/9280XT ...OP40/8650XT

−5 –3 −10.5 −0.5 3

10-Gbit/s circuit packs and modules

These are the relevant optical parameters of the 10-Gbit/s circuit packs and modules:




KFA7 OP10/1.3IOR1 −6 −1 −11 −1 3

KFA14 OP10/1.5IR1 −1 +2 −14 −1 5

KFA6 OP10/1.5LR1 +10 +13 −16 −1 20

KFA9, KFA81

KFA159OP10/0180/800G –6.2 –3.8 −20 −13 12

KFA11, KFA61

KFA75OP10/116/PWDM –1 +2 −21 −8 15

KFA210 KFA482 OP10/9285XT

OP10/8650XTapprox. –2 −13 −3 7

OM10G7 OM10/1.3IOR1 −6 −1 −11 −1 3

OM10G14 OM10/1.5IR1 −1 +2 −14 −1 5

OM10G6 OM10/1.5LR1 0 +4 −27 −7 15 - 20

2.5-Gbit/s circuit packs and modules

These are the relevant optical parameters of the 2.5-Gbit/s circuit packs and modules:


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-37

App. Code Functional name Transmitter outputpower range [dBm]



KFA12 OP2G5/1.3IOR4 −10 –3 −18 −3 3

OM2G5A12 OM2G5/1.3SR1

KFA203 OP2G5/1.3LR4 −2 +2 −27 −8 15

OM2G5A203 OM2G5/1.3LR1

KFA204 OP2G5/1.5LR4 −2 +2 −28 −8 15

OM2G5A204 OM2G5/1.5LR1

KFA20 withOM2G5A921 ...OM2G5A959

OP2G5-1...32PWDM withOM2G5/921PWDM ...OM2G5/959PWDM

−3 0 −28 −8 10 - 15

622-Mbit/s circuit packs and modules

These are the relevant optical parameters of the 622-Mbit/s circuit packs and modules:




KFA17 OP622/1.3IR16 −15 −8 −28 −8 7

OM622A182 OM622/1.3IR1

OM622A181 OM622/1.3LR1 −3 +2 −28 −8 15 - 20

155-Mbit/s circuit packs and modules

These are the relevant optical parameters of the optical 155-Mbit/s circuit packs andmodules:

App. Code Functional name Transmitter outputpower range [dBm]



KFA18 OP155M/1.3IR16 −15 −8 −28 −8 7

OM155A184 OM155/1.3IR1

OM155A183 OM155/1.3LR1 −5 0 −28 −8 15

Gigabit Ethernet circuit packs

These are the relevant optical parameters of the Gigabit Ethernet circuit packs:

App. Code Functionalname

Transmitter output powerrange [dBm]



KFA13 GE1/SX4 –9.5 −4 –17 −12.5 7 - 8

KFA532 GE1/LX4 –11.5 –3 –19 −3 5

Supporting procedures Optical circuit pack parameters

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Related information

For related information, please refer to:

• LambdaUnite® MSS Installation Guide (Ordering codes and specifications,fiber-optic cables, attenuators),

• LambdaUnite® MSS Applications and Planning Guide (Technical specifications).

Supporting procedures Optical circuit pack parameters

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-39

Retrieving a list of currently active loopbacks.................................................................................................................................................................................................................................

Purpose

Use this procedure to retrieve an overview of currently active loopbacks in the system.

Before you begin





Required privilege

You must have at least privilege codes of S1 and P1 and M1 to release across-connection loopback.

Required equipment


• WaveStar® CIT

Instructions

Proceed as follows to retrieve an overview of currently active loopbacks:

.................................................................................................................................................................................................

1 Select View → Loopback from the WaveStar® CIT System View main menu.

Result: The View Loopback List equipment selection window opens.

.................................................................................................................................................................................................

2 You can retrieve an overview of all active loopbacks (of any type) in the completeshelf, or on a certain circuit pack or port, or an overview of active cross-connectionloopbacks of a particular rate in the complete shelf, or on a certain circuit pack, port ortributary:

If then

you want a list of all activeloopbacks (of any type) in thecomplete shelf

select Shelf 1 (DUR) from the equipment selectionwindow, and continue with Step 3.

you want a list of all activeloopbacks (of any type) on acertain circuit pack

select the desired circuit pack from the equipmentselection window, and continue with Step 3.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If then

you want a list of all activeloopbacks (of any type) on acertain port

select the desired port from the equipment selectionwindow, and continue with Step 3.

you want a list of all activecross-connection loopbacks of aparticular rate in the completeshelf

select Shelf 1 (DUR) from the equipment selectionwindow, and continue with Step 4.

you want a list of all activecross-connection loopbacks of aparticular rate on a certain circuitpack

select the desired circuit pack from the equipmentselection window, and continue with Step 4.

you want a list of all activecross-connection loopbacks of aparticular rate on a certain port

select the desired port the equipment selectionwindow, and continue with Step 4.

you want to see whether across-connection loopback iscurrently active on a certaintributary

select the desired tributary from the equipmentselection window, and continue with Step 4.

.................................................................................................................................................................................................

3 Select ALL from the Port Type/Rate Selection drop-down list box in the PortType/Rate Selection window that opens. Continue with Step 5.

.................................................................................................................................................................................................

4 Select the desired tributary rate from the Port Type/Rate Selection drop-down list boxin the Port Type/Rate Selection window that opens. Continue with the next step.

.................................................................................................................................................................................................

5 Click OK in the Port Type/Rate Selection window.

Supporting procedures Retrieving a list of currently active loopbacks

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-41

Result: The View Loopback window opens (the AID of the selected systemcomponent is also indicated in the window title). The currently active loopbacks(Nearside Facility, Farside Facility, Cross Connect) on the selected systemcomponent are displayed in a tabular form.

Additional information Several View Loopback windows may be open at thesame time.

.................................................................................................................................................................................................

6 As an option, you can store or print the currently displayed list of active loopbacks:

If then

you want to store the list as astandard text file (ASCII format)

click the Save As button and specify a filenameand a destination.

you want to print out the list click the Print button and specify a printer.

.................................................................................................................................................................................................

7 Click Close to dismiss the window.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Retrieving a list of currently active loopbacks

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Restoring a database to a network element.................................................................................................................................................................................................................................

Purpose

Use this procedure to restore a previously saved database to a network element.

Safety precautions

To assure both personal safety and the proper functioning of the LambdaUnite® MSSsystem, it is imperative to review and understand these warnings and precautions priorto performing this task.

CAUTION

ESD hazard

Handling circuit packs or working on a LambdaUnite® MSS system can causeelectrostatic discharge damage to sensitive components.

Use a static ground wrist strap whenever handling circuit packs or working on aLambdaUnite® MSS system.

Important! If provisioning changes were made after the last backup files werecreated, use the appropriate WaveStar® CIT commands to manually apply therecent provisioning changes to the just-restored database.

Do not remove or reset the standby (inactive) CTL while a software download ordatabase restoration is in progress. Otherwise, the software download or databaserestoration will be aborted.

Before you begin

Before you begin this task:

• Obtain the work instructions for this task and note the database to be restored andthe location of the most recent backup files.

• Verify that a WaveStar® CIT is connected and logged in to the LambdaUnite® MSSnetwork element (NE) where the database is to be restored.

Required equipment


• WaveStar® CIT

• For connecting the WaveStar® CIT to the system via LAN connections using a hub,the following hubs are recommeded:

– Hewlett Packard:


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-43

J3128A / Advanced Stack Hub-8E

– Allied Telesyn:MR820TR3024SLMR815TMR415T

Instructions

Complete the following steps to manually restore a database to a network element:

.................................................................................................................................................................................................

1 From the System View main menu, enter the maintenance condition via Fault →Enter/Exit Maintenance Condition... → Enter Maintenance Condition...

.................................................................................................................................................................................................

2 Confirm the resulting system message by clicking OK.

.................................................................................................................................................................................................

3 Select Configuration → Software → Remote Restore... from the System View mainmenu.

Result: The Restore Database window will be opened.

.................................................................................................................................................................................................

4 Proceed as follows:

If then

you want to restore the databasedirectly from the PC where theWaveStar® CIT is installed,

select CIT in the Restore From/Via drop down listbox.

Result: A file selection screen appears showing thatthe database will back up to a specified folderunder C:\Program Files\Lucent Technologies\Wavestar CIT\ The directory of the file selectionscreen is automatically pre-populated.

Reference: Proceed with Step 5.

the connection to the NE isthrough a TCP/IP gateway,

select FTTD in the Restore From/Via drop down listbox.

Reference: Proceed with Step 6.

.................................................................................................................................................................................................

5 Select “CIT” in the Look in field and double click successively on C:, Program Files,Lucent Technologies, Wavestar CIT, and backups.

Supporting procedures Restoring a database to a network element

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Proceed with Step 8.

.................................................................................................................................................................................................

6 Select the FTTD tab and specify the TID, presentation selector (Psel), session selector(Ssel), transport selector (Tsel) and the NSAP Address for the FTTD information.

.................................................................................................................................................................................................

7 Select the FTP tab and specify the Server (IP address or server name), portinformation (optional), User name (optional) and password (optional) for the FTPinformation.

Proceed with Step 8.

.................................................................................................................................................................................................

8 Important! Be careful to select the correct backup files to restore to the NE.

Specify the path to the folder where the backup files reside.

Important! The NE does not restore a backup file properly if the release numberof the backup file is not the same as the release number of the running SW.

Restoring a backup file with a different release number Restoring a backup filewith a different release number is quite dangereous for the consistency of thedatabase and the configuration of the system and should therefore only beperformed in emergency cases by trained personel.

To restore a backup file with a different release number as the running softwareyou have to perform the following:

• open the file named db (in the WaveStar® CIT) in the directory where thebackuped information (list of files) are stored, using a text editor

• in this file change the release number of the backup file to the release numberof the running SW.

.................................................................................................................................................................................................

9 Verify your settings and correct if necessary. Then click Restore.

.................................................................................................................................................................................................

10 Confirm the resulting system message by clicking YES.

Important! TCP/IP connections are aborted automatically after 60 minutes ofinactivity (an ″inactive TCP connection″ is a TCP connection over which no TL1messages are transmitted in either direction).

To avoid this behaviour during the current action, perform an action like clickingon the Update Alarms button in the system view which causes TL1 messages(RTRV-ALM-ALL, RTRV-ALM-ENV) to be sent to the NE.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-45

Result: The NE Data Restore in Progress window appears. When the databaserestore is complete, the system will perform a reset. As a consequence, themanagement association between the WaveStar® CIT and the NE will be lost. Afterthe system reset has finished, you can re-establish the management association byagain connecting the WaveStar® CIT to the NE.

If the current action has been interrupted wait approximately 10 minutes. After 10minutes the NE has recovered from the last action and a newdownload/restore/backup can be executed.

.................................................................................................................................................................................................

11 Connect to the NE again.

Result: The NE comes up in maintenance mode if during startup a database with anot matching serial number is detected. However, if the original database (with amatching serial number) is restored, the NE does not come up in maintenancemode.

If the database does not match to the NE (if, for example, the database of adifferent NE was restored) the system will come up in maintenance mode againafter the restoration.

Now it is up to your discretion

1. to accept this database by leaving the maintence mode, or

2. to restore the correct database.

.................................................................................................................................................................................................

12If then

the NE comes up in maintenancemode,


the NE does not come up inmaintenance mode,


.................................................................................................................................................................................................

13If then

you want to accept the database, continue with the next step.

you do not want to accept thedatabase,

restore a different database by performing thisprocedure for that database.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

14 From the System View main menu, select Fault → Enter/Exit MaintenanceCondition... → Exit Maintenance Condition...

.................................................................................................................................................................................................

15 Confirm the resulting system message by clicking OK.

The LambdaUnite® MSS NE will now perform a system reset. As a consequence,the management association between the WaveStar® CIT and the NE will be lost.After the system reset has finished, you can re-establish the managementassociation by again connecting the WaveStar® CIT to the NE.

E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-47

Replacing a CompactFlash® card.................................................................................................................................................................................................................................

Purpose

Use this procedure to replace the system’s non-volatile memory (NVM,CompactFlash® card with IDE interface) only when instructed to do so as part of atrouble clearing procedure or as part of a periodic activity.

CompactFlash® card

The Controller (CTL) maintains system configuration data and system software on anexchangeable CompactFlash® card; it resides in a CompactFlash® drive integrated inthe CTL circuit pack.

The CompactFlash® card resides in a CompactFlash® drive integrated in the CTLcircuit pack.

Regular database backups

To make sure that the NE database (NE software and configuration data) available forrestoration after the exchange of a CompactFlash® card best represents the most recent


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

NE configuration, it is strongly recommended to backup the NE database in regularintervals, and especially after major configuration changes.

Please refer to the LambdaUnite® MSS User Operations Guide for further informationabout database backup.

Before you begin

Verify that a database back-up with the desired configuration is available.

You or a service technician need to be on-site at the NE to replace CompactFlash®

cards.

Make sure the required equipment listed below is available and within easy reach.

Required equipment


• New, empty Lucent Technologies -provided CompactFlash® card(s):of the correct capacity:

– 256 MB for traditional applications with CTL/- (without ONNS)

– 512 MB for traditional and ONNS applications with CTL/2

– 1 GB for traditional applications with CTL/3T, or traditional and ONNSapplications with CTL/3S.

in the minimum quantity:

– one in case of simplex CTL configuration

– two in case of duplex CTL configuration.

• A PC featuring:

– a CompactFlash® drive. Alternatively, a PCMCIA drive in conjunction with aCompactFlash® adapter (for example a SanDisk® CompactFlash Adapter) maybe used.

– the desired WaveStar® CIT version with the desired NE SW generic installed.

• A PC with the desired WaveStar® CIT version installed (for the simplex CTL casealso the OSI drivers must be installed), with:

– LAN connectivity to the NE in that you want to replace the CompactFlash®

card

– the previously taken database back-up stored (for the simplex CTL case only).

Instructions

.................................................................................................................................................................................................

1 Insert the new, empty Lucent Technologies -provided CompactFlash® card into therespective drive of the PC.

Supporting procedures Replacing a CompactFlash® card

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-49

.................................................................................................................................................................................................

2 Open the WaveStar® CIT, and in the network view (main window) selectAdministration→ Prepare PCMCIA Disks from the top menu.

Result: The Prepare PCMCIA Disks window opens.

.................................................................................................................................................................................................

3 In the Available Generics section select the desired NE type from the list.

Result: The Directory Select window opens.

.................................................................................................................................................................................................

4 In the Selection List section select the SW generic from the list, and confirm yourchoice by clicking in the Copy button.

Result: The Directory Select window closes.

.................................................................................................................................................................................................

5 Back in the Prepare PCMCIA Disks window, move to the Destination PCMCIA Disksection; select the drive letter of the CompactFlash® drive where you inserted the new,empty card.

Result: The Copy Generic button at the bottom of the Prepare PCMCIA Diskswindow is now accessible.

.................................................................................................................................................................................................

6 Start the copy process by clicking on the Copy Generic button at the bottom of thePrepare PCMCIA Disks window.

Note: The copy process usually takes about one minute, depending on the PCperformance.

.................................................................................................................................................................................................

7 When the copy process is finished, shown by the activity indicator of theCompactFlash® drive, unmount the CompactFlash® card (“slot power off”).

.................................................................................................................................................................................................

8 Eject the CompactFlash® card from the PC drive.

.................................................................................................................................................................................................

9 At the NE: unseat the CTL where the CompactFlash® card to be replaced resides, andextract the CTL from its slot.

Note: In case of duplex CTL configuration, unseat the stand-by CTL.

.................................................................................................................................................................................................

10 Eject the “old” CompactFlash® card from the CTL CompactFlash® drive.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

11 Insert the new CompactFlash® card into the CTL CompactFlash® drive.

.................................................................................................................................................................................................

12 In case of simplex CTL configuration proceed with step 16.

In case of duplex CTL configuration proceed with step 13

.................................................................................................................................................................................................

13 Re-insert and re-seat the CTL.

Result: The stand-by CTL performs a synchronization, copying the database fromthe active CTL, which typically takes about 20 minutes, depending on the workload of the CTL. At the end of the synchronization both LEDs of the stand-by CTLare off.

.................................................................................................................................................................................................

14 After the synchronization process of the stand-by CTL is finished (both LEDs of thestand-by CTL are off), do the following:

From the PC with LAN connection to the NE, start the WaveStar® CIT and log-in tothe NE, as described in the LambdaUnite® MSS User Operations Guide, chapter“WaveStar® CIT Tutorial”, and

then switch the 1+1 CTL protection manually, as described in the LambdaUnite® MSSUser Operations Guide, chapter “Equipment provisioning”.

Result: The stand-by CTL becomes the active one, and vice versa.

.................................................................................................................................................................................................

15 If only one CTL unit is processed sofar

proceed with step 1

If both CTL units are processed stop. You have reached the end of steps.

Result: The system is in normal operation with the previously active database, andthe previously active CTL.

.................................................................................................................................................................................................

16 Re-insert and re-seat the CTL.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-51

Result: The CTL performs a boot; this can typically take 20 minutes. At the end,when the green LED of the CTL is permanently on, the system is in maintenancecondition, accessible with the default TID “LUCENT-UNITE-NE”.

.................................................................................................................................................................................................

17 Using the PC with LAN connection to the NE, start the WaveStar® CIT and log-in tothe NE (default TID “LUCENT-UNITE-NE”, default superusers and passwords, defaultarea address and default data communications settings, as described in theLambdaUnite® MSS User Operations Guide, chapter “WaveStar® CIT Tutorial”), and

perform a Restore operation, as described in the LambdaUnite® MSS User OperationsGuide, chapter “Database backup”.

Result: Immediately after the download-database process the CTL performs are-boot; this can take up to 45 minutes, depending on the LAN connectivity and thedatabase size. At the end of the boot process, when the green LED of the CTL ispermanently on, the system is in normal operation with the previously downloadeddatabase.

E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Removing a circuit pack from the system.................................................................................................................................................................................................................................

Purpose

Use this procedure to permanently remove a circuit pack from its slot.

Before you begin

You or a service technician need to be on-site at the NE to replace a circuit pack.


Required equipment


• A replacement circuit pack.

• Blank faceplates to cover unequipped slots.

• WaveStar® CIT.

Instructions

CAUTION

ESD hazard



Proceed as follows to permanently remove a circuit pack from the shelf:

.................................................................................................................................................................................................

1 Using the WaveStar® CIT, release all cross-connections, facility loopbacks, timingreference assignments etc. which have previously been provisioned for the circuit packto be removed.

Reference: Please refer to “Deprovisioning a circuit pack” (p. 4-54).

.................................................................................................................................................................................................

2 Remove the circuit pack from its slot.

.................................................................................................................................................................................................

3 Cover the now unequipped slot(s) with a blank faceplate (cf. “Configuration rules”(p. 4-66)).


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-53

Circuit packs occupying more than one slot require the corresponding number ofblank faceplates to cover the unequipped slots.

.................................................................................................................................................................................................

4 Deprovision the circuit pack by using the WaveStar® CIT.

Deprovisioning a circuit pack

These preconditions have to be fulfilled for the indicated circuit pack before it can bedeprovisioned:

• Cross-connect and timing units (XC160, XC320, XC640):

– The corresponding slot is not equipped, and

– there exists no port protection group, and

– there exists no cross-connection.

• OP port unit:


– no port of the provisioned OP port unit is a member of a port protectiongroup, and

– no port of the provisioned OP port unit has DCC links enabled, and

– no port of the provisioned OP port unit is assigned as a timing reference, and

– no port of the provisioned OP port unit is involved in an orderwire connection,and

– no port of the provisioned OP port unit is involved in a cross-connection orfacility loopback, and

– no tributary of the provisioned OP port unit is involved in a cross-connectionor in a path protection.

• GE1 port unit:


– no port of the provisioned GE1 port unit is involved in a cross-connection, and

– no port of the provisioned GE1 port unit is involved in a facility loopback.

• Lower order cross-connect unit (LOXC):


– the LOXC is not involved in an equipment protection group, and

– no lower order cross-connection exists on the LOXC.

Supporting procedures Removing a circuit pack from the system

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

E N D O F S T E P S.................................................................................................................................................................................................

Replacing a circuit pack by a circuit pack of the same type.................................................................................................................................................................................................................................

Purpose

Use the following procedure, for example during a trouble clearing procedure, toreplace a circuit pack by a circuit pack of the same type.

These two situations can be distinguished:

• Replacing a circuit pack by another circuit pack of exactly the same type, i.e. by acircuit pack with the same functional name and functional qualifier.Example: Replacing an OP10/1.5IR1 (KFA14) by another OP10/1.5IR1 (KFA14).

• Replacing a circuit pack by another variant of the same circuit pack type, i.e. by acircuit pack with the same functional name but different functional qualifier, whilepreserving configuration settings, such as cross-connections and protection groupsfor example.Example: Replacing an OP10/1.5IR1 (KFA14) by an OP10/1.5LR1 (KFA6).

Note that there is a specific procedure for replacing the Controller (CTL), please referto “Replacing the Controller (CTL)” (p. 4-62).

Before you begin



Required equipment


• A replacement circuit pack of the same type.

Instructions

CAUTION

ESD hazard




.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-55

Proceed as follows to replace a circuit pack by a circuit pack of the same type:

.................................................................................................................................................................................................

1 If you want to replace a circuitpack by

then

another circuit pack of exactlythe same type

proceed with the next step.

another variant of the samecircuit pack type

please refer to “Exchanging a circuit pack withoutdeprovisioning” (p. 4-57).

.................................................................................................................................................................................................


.................................................................................................................................................................................................

3 Within ten minutes (cf. “Configuration rules” (p. 4-66)), insert the replacement circuitpack.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Replacing a circuit pack by a circuit pack of the sametype

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Exchanging a circuit pack without deprovisioning.................................................................................................................................................................................................................................

Purpose

Use this procedure to replace an already provisioned circuit pack by another variant ofthe same circuit pack type without first having to deprovision the currently provisionedcircuit pack.

A typical application of this procedure is the exchange of port units with the samefunctional name, but different wavelengths and/or reaches. These port unit variants canbe exchanged while configured cross-connections and protection groups are preserved.

Related information

For related information, see:

• “Reprovisioning (Exchangeability)” (p. 4-58)

Before you begin

Please observe the rules and preconditions with respect to the exchangeability of circuitpacks (cf. “Reprovisioning (Exchangeability)” (p. 4-58)).

Required privilege code

You must have at least privilege codes of P3 and M1 to exchange a circuit pack.

Required equipment


• WaveStar® CIT

Instructions

CAUTION


Deletion of provisioned equipment will remove all parameter settings. Removing ormodifying a working circuit pack will interrupt service!

In order to prevent service interruptions, you should verify that the respective circuitpack is out of service.

Proceed as follows to exchange a circuit pack:

.................................................................................................................................................................................................

1 Physically remove the currently provisioned circuit pack and insert the new circuitpack, or leave the slot empty.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-57

Result: In the WaveStar® CIT shelf display, the circuit pack is displayed withdiagonal grey lines to show that the slot is still assigned to this circuit pack.

.................................................................................................................................................................................................

2 Choose one of the following options:

1. From the WaveStar® CIT System View main menu, select Configuration →Exchange Circuit Pack

2. In the WaveStar® CIT System View shelf display, right-click on the slot of thecircuit pack you removed in Step 1, and select Exchange Circuit Pack in thepop-up menu that opens.

Result: If you have chosen option 1, then the Exchange Circuit Pack windowopens with the Equip selection tab on the left-hand side, the right-hand side of thewindow is empty. Proceed with the next step.

If you have chosen option 2, then the Exchange Circuit Pack window opens.Proceed with Step 4.

.................................................................................................................................................................................................

3 From the Equip selection tab, select the circuit pack you removed in Step 1.

Result: The Exchange Circuit Pack window opens. A list with the acceptable newcircuit packs is displayed.

.................................................................................................................................................................................................

4 Select the desired circuit pack type from the list of acceptable circuit packs.

.................................................................................................................................................................................................

5 If not yet done, physically insert the new circuit pack.

Result: The new circuit pack will be autoprovisioned (with the configurationparameters of the old circuit pack).

Reprovisioning (Exchangeability)

Reprovisioning is often also referred to as “exchangeability”. It means replacing analready provisioned circuit pack (referred to as the “old” circuit pack in the following)by another variant of the same circuit pack type (referred to as the “new” circuit packin the following) without first having to deprovision the old circuit pack.

Supporting procedures Exchanging a circuit pack without deprovisioning

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

E N D O F S T E P S.................................................................................................................................................................................................

Exchangeability of optical port units (including Gigabit Ethernet)

To exchange different variants of optical port units (including Gigabit Ethernet), all ofthe following preconditions must be fulfilled at the same time:

• The system must not be in maintenance condition.

• The respective slot must be empty, or the new port unit must already be installed.

• The new port unit has the same transmission capacity as the old port unit.

• The new port unit supports the same number of ports as the old port unit.

• The new port unit supports the same port configuration concerning FEC as it iscurrently provisioned for the old port unit.

Exchangeability of cross-connect and timing units

To exchange different variants of cross-connect and timing units, all of the followingpreconditions must be fulfilled at the same time:

• The system must not be in maintenance condition.

• The respective slot must be empty, or the new cross-connect and timing unit mustalready be installed.

• The new cross-connect and timing unit has the same switching capacity as the oldcross-connect and timing unit.

Reprovisioning in maintenance mode

Reprovisioning is not possible in the maintenance mode.

Supporting procedures Exchanging a circuit pack without deprovisioning

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-59

Replacing a circuit pack by a circuit pack of a different type.................................................................................................................................................................................................................................

Purpose

Use this procedure, for example during a reconfiguration of a shelf, to replace a circuitpack by a circuit pack of a different type.

Before you begin



Required equipment


• A replacement circuit pack.

• Blank faceplates to cover unequipped slots.

• WaveStar® CIT.

Instructions

CAUTION

ESD hazard



Proceed as follows to replace a circuit pack by a circuit pack of a different type:

.................................................................................................................................................................................................

1 Using the WaveStar® CIT, release all cross-connections, facility loopbacks, timingreference assignments etc. which have previously been provisioned for the circuit packto be removed.

Reference: Please refer to “Deprovisioning a circuit pack” (p. 4-54).

.................................................................................................................................................................................................


.................................................................................................................................................................................................

3 Cover the now unequipped slot(s) temporarily with a blank faceplate (cf.“Configuration rules” (p. 4-66)).


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Circuit packs occupying more than one slot require the corresponding number ofblank faceplates to cover the unequipped slots.

.................................................................................................................................................................................................

4 Deprovision the circuit pack by using the WaveStar® CIT.

.................................................................................................................................................................................................

5 You may now either preprovision the circuit pack to be inserted using the WaveStar®

CIT and then proceed with the next step, or you may directly proceed with the nextstep.

.................................................................................................................................................................................................

6 Remove the previously inserted blank faceplates.

The number of blank faceplates to be removed depends on the required number ofslots for the circuit pack to be inserted. Do not leave unequipped slots uncoveredfor more than ten minutes (cf. “Configuration rules” (p. 4-66)).

.................................................................................................................................................................................................

7 Insert the new circuit pack.

If you did not preprovision the circuit pack (cf. Step 5), then it will now beautoprovisioned.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Replacing a circuit pack by a circuit pack of a differenttype

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-61

Replacing the Controller (CTL).................................................................................................................................................................................................................................

Purpose

Use this procedure to replace the Controller (CTL) while preserving the present NEdatabase (NE software and configuration data).

Before you begin

Make sure the required equipment listed below is available and within easy reachbefore you begin.

Required equipment


• A replacement CTL circuit pack.

Instructions

.................................................................................................................................................................................................

1 Important! In order to avoid damage to the NE database stored on theCompactFlash® card, it is of great importance to follow a special procedure forremoving the Controller (CTL) from its slot.

Proceed as follows:

1. Open the latches of the CTL to be replaced. Do not remove the CTL from its slot atthat time.The green “ACTIVE” LED on the faceplate of the CTL starts flashing.

2. Wait until the green “ACTIVE” LED has stopped flashing (about five seconds).

3. Remove the CTL from its slot.

.................................................................................................................................................................................................

2 Eject the CompactFlash® card from the CompactFlash® drive of the CTL circuit packto be replaced.

.................................................................................................................................................................................................

3 Insert the CompactFlash® card into the CompactFlash® drive of the CTL circuit packto be inserted.

.................................................................................................................................................................................................

4 Insert the new CTL circuit pack into its designated slot and close the latches.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Result: The serial number stored in the backplane EEPROM will now be comparedwith the serial number stored on the CompactFlash® card. If the serial numbersmatch, the CTL circuit pack will perform a reset (full reset).

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Replacing the Controller (CTL)

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-63

Replacing a defective optical fiber.................................................................................................................................................................................................................................

Purpose

Use this procedure to replace a defective optical fiber.

Before you begin

You or a service technician need to be on-site at the NE to replace a defective opticalfiber.


Required equipment


• A replacement fiber.

• An edge cutter.

Instructions

.................................................................................................................................................................................................

1 Disconnect the defective optical fiber from the circuit pack port.

.................................................................................................................................................................................................

2 Cut off the optical fiber connector.

.................................................................................................................................................................................................

3 CAUTION


Cutting the wrong fiber will be traffic affecting!

Make sure to cut the defective fiber only.

Cut the defective optical fiber at the subrack entrance.

.................................................................................................................................................................................................

4 Remove the fiber.

.................................................................................................................................................................................................

5 Route the new fiber on top of the existing fiber bundles.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

6 Connect the new fiber to the circuit pack port.

E N D O F S T E P S........................................................................................................................................................................................................................

Supporting procedures Replacing a defective optical fiber

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-65

Configuration rules.................................................................................................................................................................................................................................

Supported LXC configurations

These LXC configurations are supported:

• “LXC with a max. switching capacity of 160 Gbit/s” (p. 4-71)



• “LXC supporting ONNS applications” (p. 4-75)

All these configurations can be realized by using a dual unit row (DUR) shelf.

DUR shelf

A DUR shelf can be equipped from the front as well as from the rear side.

As a general rule, a DUR shelf is designed such that optical interfaces can be accessedfrom the front while electrical interfaces can be accessed from the rear side.

Available slots on the front side

The following illustration shows the available circuit pack slots on the front side of aDUR shelf.

A DUR shelf provides the following circuit pack slots on the front side:

• 2 dedicated slots for CTL (slots 11 and 31, “W” = worker, “P” = protection).

• 2 dedicated slots for XC cross-connect and timing units (slots 9 and 10, “W” =worker, “P” = protection).

21

1 9

40

3122

2 1210 19

393223

3 13

3324

4 14

3425

5 15

3526

6 16

3627

7 17

3728

8 18

38

User panel

front view

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

CT

L (P

) sl

ot

Uni

vers

al s

lot

CT

L (W

) sl

ot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

XC

(W

) sl

ot

XC

(P

) sl

ot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

11


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

• 32 “universal slots” for port units (slots 1-8, 12-19, 21-28, and 32-39).

• 1 dedicated slot for the user panel (slot 40).

Slots Slot equipage

18

1219

2128

3239

Universal slots1 Universal slots can be used for any mix of port units:2

• Electrical DS3 (45 Mbit/s, plesiochronous) or EC-1 (51 Mbit/s, synchronous)port units (EP51)3

For the EP51 port units, there are dedicated slots for the electrical connectioninterfaces (ECI) on the rear side of the shelf.

• Electrical 155-Mbit/s (STM-1E) port units (EP155)3

For the EP155 port units, there are dedicated slots for the electrical connectioninterfaces (ECI) on the rear side of the shelf.

• Optical 155-Mbit/s port units (OP155)

• 622-Mbit/s port units (OP622)

• 2.5-Gbit/s port units (OP2G5)

• 10-Gbit/s port units (OP10)

• 40-Gbit/s port units (OP40)An OP40 port unit occupies four universal slots.

• 1-Gigabit Ethernet interface (GE1)

• 10-Gigabit Ethernet WANPHY interface (realised on an OP10 port unit)

Lower order cross-connect units (LOXC):

The slots 4, 17, 18, 19, 37, and 39 can be used for lower order cross-connect unitsof type LOXC/1, depending on the maximum switching capacity of the system.

For more detailed information, please refer to:

• “LXC with a max. switching capacity of 160 Gbit/s” (p. 4-71),

• “LXC with a max. switching capacity of 320 Gbit/s” (p. 4-72), and

• “LXC with a max. switching capacity of 640 Gbit/s” (p. 4-74), respectively.

9 XC (W) slot Cross-connect and timing unit (XC) – worker (W).4

This XC is paired with the XC in the protection slot in a 1+1 non-revertiveprotection mode configuration. Furthermore, the XC contains the timing generatorfunction for the NE.

10 XC (P) slot Cross-connect and timing unit (XC) – protection (P).4

This XC is paired with the XC in the worker slot in a 1+1 non-revertive protectionmode configuration. Furthermore, the XC contains the timing generator function forthe NE.

11 CTL (W) slot Controller (CTL) – worker (W).4

Controller including the non-volatile memory (NVM, CompactFlash® card). Afterinitial system startup (power on), this Controller takes on the active role.

31 CTL (P) slot Controller (CTL) – protection (P).4

Optionally, a second Controller can be equipped for CTL equipment protection(duplex control). After initial system startup (power on), this Controller takes on thestandby role.

40 User panel

The slots 20, 29, and 30 do not exist.

Supporting procedures Configuration rules

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-67

Notes:

1. Slots for port units are called “universal slots”. The transmission capacity of a port unit in a universal slotcan be up to 20 Gbit/s per slot.

2. Each port unit occupies one universal slot, if not stated otherwise.

3. The electrical port units (EP) can only be used in the universal slots in the upper row of the shelf (slots18, and 1219), and in a DUR shelf of type DUR/2.

4. The terms “worker” and “protection” are used to describe the static role within a protection, whereas theterms “active” and “standby” are used to describe the current (dynamic) role. Please also refer to theLambdaUnite® MSS User Operations Guide.

Available slots on the rear side

The following illustration shows the available slots on the rear side of a DUR shelf.

A DUR shelf provides the following slots on the rear side:

• 1 dedicated slot for the connection interface of the Controller (CI-CTL).

• 2 dedicated slots for timing interfaces (TI A and TI B).

• 2 dedicated slots for power interfaces (PI A and PI B).

• 8 dedicated slots for electrical connection interfaces (ECI).

• 1 dedicated slot for the fan unit.

Slots Slot equipage

41 – (reserved for future applications)


69

80

56 45

65

4151

67

435254

72 6163

70

747678

CI-CTL

ECIslot

TI (A)

Fan unit

Air filter

rear view

PI (A)

TI (B)

PI (B)

ECIslot

ECIslot

ECIslot

ECIslot

ECIslot

ECIslot

ECIslot

PI/-

PI/100

PI/-

PI/100


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Slots Slot equipage

45 Power interface (PI A)

The PI/100 variant of the power interface requires a wider slot than the PI/-variant.

51 Connection interface of the Controller (CI-CTL)



56 Power interface (PI B)

The PI/100 variant of the power interface requires a wider slot than the PI/-variant.

6167 Electrical connection interfaces (ECI).

Grouping of the slots

• when EP51 is used: 61 and 65, or 63; the respective ECI is 4 slots wide;

• when EP155 is used: 61, 63, 65, 67 the respective ECI is 2 slots wide.

69 Timing interface (TI A)

70 Timing interface (TI B)

7278 Electrical connection interfaces (ECI).

Grouping of the slots

• when EP51 is used: 72 and 76, or 74; the respective ECI is 4 slots wide;

• when EP155 is used:72, 74, 76, 78; the respective ECI is 2 slots wide.

80 Fan unit

General configuration rules and guidelines

Observe the following general rules and guidelines with regard to the shelfconfiguration. Take all these rules and guidelines into consideration as the ordering inthe list does not necessarily reflect the order of importance.

1. Use the configurator tool to verify if a certain subrack equipage is permitted.For example: Do not install a GE1 port unit in the lower row of the subrack belowan OP10 port unit in the upper row. This applies to all supported OP10 versionsexcept the OP10/1.3IOR1.

2. Never operate a LambdaUnite® MSS system without a fan unit for more than two(2) minutes to avoid overheating of the system.Leaving the fan unit out of operation for more than two minutes may cause therespective network element to fail.

3. Do not operate a network element without a CI-CTL, as the initialization/re-initialization of the CTL may fail when no CI-CTL is present.

4. Do not insert circuit packs simultaneously. When several circuit packs have to beinserted, they should be inserted one after the other, with intervals of at least onesecond.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-69

5. Cover unequipped slots and OM sockets with blank faceplates or dummy modulesto guarantee proper cooling, airflow and EMC behavior. Do not leave unequippedslots uncovered for more than ten (10) minutes to avoid overheating of the system.Disregarding this warning could cause the system to fail and voids warranty.The cooling of the LambdaUnite® MSS system relies on sufficient airflow.Uncovered slots prevent an adequate cooling because LambdaUnite® MSS systemsmake use of the stack effect.

6. To avoid damaging the blank faceplates, make sure that the maximum upward anddownward displacement of the latches does not exceed 5 mm.

7. In order to avoid damage to the NE database stored on the CompactFlash® card, itis of great importance to follow a special procedure for removing the Controller(CTL) from its slot. Proceed as follows:

a. Open the latches of the CTL to be replaced. Do not immediately remove theCTL from its slot at that time.The green activity LED on the faceplate of the CTL starts flashing.

b. Wait until the green activity LED has stopped flashing (about five seconds).

c. Remove the CTL from its slot.

Specific configuration rules and guidelines

Specific configuration rules and guidelines apply depending on the maximum switchingcapacity of a LambdaUnite® MSS system and on the desired application.

Therefore, please refer to:




• “LXC supporting ONNS applications” (p. 4-75)

Maximum switching capacity

A LambdaUnite® MSS system can be configured for different values of the maximumcross-connect capacity (Maximum Switch Capacity):

LXC160 The maximum switch capacity of the system is 160 Gbit/s(3072 × 3072 VC-3/STS-1; 1024 × 1024 VC4).

This is the default value after a new NE installation with Release4.0 (or higher) NE software and an empty database.


This is the default value after an upgrade from a previous NEsoftware release to Release 4.0 (or higher) NE software.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005


Important! The maximum switch capacity is independent of the type ofcross-connect and timing unit used. However, the shelf equipage concerning thecross-connect and timing units depends on the maximum switch capacity.

LXC with a max. switching capacity of 160 Gbit/s

These rules and guidelines apply when the Maximum Switch Capacity of the systemis set to LXC160:

1. The maximum switching capacity of the system is 160 Gbit/s (3072 × 3072VC-3/STS-1; 1024 × 1024 VC4).

2. Each type of cross-connect and timing unit (XC160, XC320, XC640) can beprovisioned in slot 9 and slot 10. However, the maximum switching capacity thatcan be used is 160 Gbit/s, and the slot equipage rules as described above applyindependent of which cross-connect and timing unit is used.

3. Port units can only be used in the upper row of the DUR shelf, i.e. in the universalslots 21 28 and 32 39.When a port unit is installed in any of the remaining universal slots, then the greenactivity LED of that port unit will be flashing, and a Circuit Pack TypeMismatch alarm will be reported. An attempt to preprovision a port unit for any ofthese slots will be denied.Cover all unequipped slots with blank faceplates (see “General configuration rulesand guidelines” (p. 4-69)).

4. Port units with a transmission capacity of 20 Gbit/s (for example anOP2G5D/PAR8 parent board, equipped with 8 optical modules) can only be used inthe universal slots 22, 24, 26, 28, 33, 35, 37, and 39. The slot left to a slot wheresuch a port unit is installed has to remain unequipped, i.e. cannot be used for otherapplications. Please also refer to the diagram subsequent to this list.

5. Lower order cross-connect units of type LOXC/1 can be used in the universal slots37 (worker slot) and 39 (protection slot). The slot left to an LOXC/1 has to remainunequipped, i.e. cannot be used for other applications.Please also refer to the LambdaUnite® MSS User Operations Guide.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-71

6. XC160 cross-connect and timing units support ONNS applications (cf. “LXCsupporting ONNS applications” (p. 4-75)).

7. It is recommended to use two XC160 cross-connect and timing units. Thus, boththe cross-connnect as well as the timing function are automatically 1+1 equipmentprotected. However, an LXC configuration with a single, but unprotected XC160cross-connect and timing unit is also possible.




2. Only XC320 or XC640 cross-connect and timing units can be provisioned in slot 9and slot 10. However, the maximum switching capacity that can be used is 320Gbit/s, and the slot equipage rules as described above apply independent of whetheran XC320 or XC640 is used.When an XC160 cross-connect and timing unit is installed in slot 9 or slot 10,then the green activity LED of that XC160 will be flashing, and a Circuit PackType Mismatch alarm will be reported.

1

40

2 12 193 134 145 156 167 178 18

User panel

front view

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

CT

L (W

) sl

ot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

21 3223 3425 3627 38

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

22

Uni

vers

al s

lot

XC

(W

) sl

ot

XC

(P

) sl

ot

24

Uni

vers

al s

lot

26

Uni

vers

al s

lot

28

Uni

vers

al s

lot

33

Uni

vers

al s

lot

35

Uni

vers

al s

lot

37

Uni

vers

al s

lot

39

Uni

vers

al s

lot

9 10 11

31

CT

L (P

) sl

ot


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

3. Port units can be used in all universal slots.However, port units with a transmission capacity of 20 Gbit/s (for example anOP2G5D/PAR8 parent board, equipped with 8 optical modules) can only be used inthe universal slots 2, 4, 6, 8, 13, 15, 17, 19, 22, 24, 26, 28, 33, 35, 37, and 39. Theslot left to a slot where a 20-Gbit/s port unit is installed has to remain unequipped,i.e. cannot be used for other applications. Please also refer to the diagramsubsequent to this list.Cover all unequipped slots with blank faceplates (see “General configuration rulesand guidelines” (p. 4-69)).

4. Lower order cross-connect units of type LOXC/1 can be used in the universal slots4, 17, 19, 37, and 39.The slots 4, 17 and 37 are worker slots. The slots 19 and 39 are protection slots. Ifthe worker LOXC/1 is installed either in slot 4 or in slot 17, then the protectionLOXC/1 must be installed in slot 19. If the worker LOXC/1 is installed in slot 37,then the protection LOXC/1 must be installed in slot 39. The slot left to anLOXC/1 has to remain unequipped, i.e. cannot be used for other applications.Please note that at most one LOXC equipment protection group may exist, i.e. atmost one worker slot can be used in combination with one protection slot (pleasealso refer to the LambdaUnite® MSS User Operations Guide).

5. Only the XC320/B variant of the XC320 cross-connect and timing units supportsONNS applications (cf. “LXC supporting ONNS applications” (p. 4-75)).


21

40

12

3223 25 27

User panel

front view

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

CT

L (P

) sl

ot

Uni

vers

al s

lot

CT

L (W

) sl

ot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

XC

(W

) sl

ot

XC

(P

) sl

ot

Uni

vers

al s

lot

Uni

vers

al s

lot

22

Uni

vers

al s

lot

24

Uni

vers

al s

lot

26

Uni

vers

al s

lot

28

Uni

vers

al s

lot

1 2 3 5 6 7 8 13 14 15 16 18

33 34 35 36 38

Uni

vers

al s

lot

37

Uni

vers

al s

lot

17

Uni

vers

al s

lot

39

Uni

vers

al s

lot

199 10 11

31

Uni

vers

al s

lot

4


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-73




2. Only XC640 cross-connect and timing units can be provisioned in slot 9 andslot 10.When any cross-connect and timing unit other than an XC640 is installed in slot 9or slot 10, then the green activity LED of that cross-connect and timing unit willbe flashing, and a Circuit Pack Type Mismatch alarm will be reported.

3. Port units can be used in all universal slots, and all universal slots can be used.

4. Lower order cross-connect units of type LOXC/1 can be used in the universal slots4, 17, 18, 19, 37, and 39. The slots 4, 17, 18 and 37 are worker slots. The slots 19and 39 are protection slots. If the worker LOXC/1 is installed in slot 4, 17, or 18,then the protection LOXC/1 must be installed in slot 19. If the worker LOXC/1 isinstalled in slot 37, then the protection LOXC/1 must be installed in slot 39.Please note that at most one LOXC equipment protection group may exist, i.e. atmost one worker slot can be used in combination with one protection slot (pleasePlease also refer to the LambdaUnite® MSS User Operations Guide).

5. XC640 cross-connect and timing units support ONNS applications (cf. “LXCsupporting ONNS applications” (p. 4-75)).


21

1 9

40

3122

2 1210

3223

3 13

3324

14

3425

5 15

3526

6 16

3627

7

28

8

User panel

front view

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

CT

L (P

) sl

ot

Uni

vers

al s

lot

CT

L (W

) sl

ot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

Uni

vers

al s

lot

XC

(W

) sl

ot

XC

(P

) sl

ot

Uni

vers

al s

lot

Uni

vers

al s

lot

11 1917

Uni

vers

al s

lot

Uni

vers

al s

lot

3937

Uni

vers

al s

lot

Uni

vers

al s

lot

38

Uni

vers

al s

lot

18

Uni

vers

al s

lot

4

Uni

vers

al s

lot


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

LXC supporting ONNS applications

A special shelf equipage is required for ONNS applications.

Observe these rules and guidelines with regard to an LXC configuration supportingONNS applications:

1. Only Controllers of type CTL/2 (with a 512-MByte CompactFlash® card) orCTL/3S (with a 1-GByte CompactFlash® card) and cross-connect and timing unitsof type XC160, XC320/B, or XC640 are suitable for ONNS applications.It is recommended to use two suitable Controllers (duplex control) and two suitablecross-connect and timing units (XCs). Thus, both the Controllers as well as thecross-connect and timing units are automatically 1+1 equipment protected.

2. All available port units except for OP40, EP51 and OPT2G5 can be used forONNS applications.

3. Lower order cross-connections are not supported by ONNS.

In addition, the permissible shelf equipage depends on the maximum switch capacity,cf.





.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-75

Initiating a circuit pack reset.................................................................................................................................................................................................................................

Purpose

Use this procedure to reset a circuit pack.

A circuit pack reset is only possible for circuit packs with an integrated controller(function controller). Circuit packs with function controller are also called“subsystems”.

Types of reset

These types of reset can be distinguished:

• Controller resetA controller reset is a partial shutdown of a subsystem, which does not affect thebasic transmission service provided by the subsystem as a whole. Only thesubsystem’s controller part, hardware and software, is shut down.

• Full resetA full reset is a shutdown of a whole subsystem with basic transmission serviceaffected. A full reset affects both the subsystem controller and the controlledhardware.Please note, that a full reset of the Controller (CTL), in contrast to a controllerreset of the CTL, affects

– MS/Line performance monitoring, and

– Automatic Protection Switching (APS) on MS/Line level (SDH: MultiplexSection Protection (MSP) and MS-SPRing; SONET: Line Protection and BLSR)

LED indications

When performing a reset, the indications via the circuit pack faceplate LEDs will be asfollows, depending on the type of reset:

Full reset For a few seconds, the red fault LED is on, and the green activityLED is off.

Then the green activity LED is flashing until the circuit packrecovery has finished.

Controller reset For a few seconds, the green activity LED is off.

Then the green activity LED is flashing until the circuit packrecovery has finished.

Before you begin

Please read the instructions first.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If you want to initiate a controller reset for a particular circuit pack, or if you are noton site at the network element, make sure that you have the required privileges, andthat the required equipment is available.

Required privilege

You must have at least privilege codes of S4 and M4.

Required equipment


• WaveStar® CIT

Instructions

.................................................................................................................................................................................................

1 Depending on the type of reset, proceed as follows:

If you want to initiate a then

Full reset proceed with Step 2.

Controller reset proceed with Step 4.

.................................................................................................................................................................................................

2 There are two possible ways to initiate a full reset of a circuit pack, depending onwhether you are on site at the network element or not:

If you are then

on site at the NE proceed with the next step.

not on site at the NE proceed with Step 4.

.................................................................................................................................................................................................

3 Important! A full reset of a circuit pack may be service affecting!

Supporting procedures Initiating a circuit pack reset

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-77

If you want to proceed, follow these instructions depending on the type of circuit packto be reset:

If you want to reset then

the CTL proceed as follows in order to avoid damage to theNE database stored on the CompactFlash® card:

1. Open at least one of the latches of the CTL tobe reset.

The green “ACTIVE” LED on the faceplate ofthe CTL starts flashing.

2. Wait until the “ACTIVE” LED has stoppedflashing (about five seconds).

3. Close the latches of the CTL.

Result: The Controller performs a recovery. Asa consequence, the management associationbetween the WaveStar® CIT and the NE will belost. After the recovery has finished, you canre-establish the management association byagain connecting the WaveStar® CIT to the NE.

a circuit pack other than the CTL open and close the latches of the correspondingcircuit pack.

Result: The corresponding circuit pack will performa full reset.

.................................................................................................................................................................................................

4 By means of the WaveStar® CIT, establish a management association to the respectiveNE.

.................................................................................................................................................................................................

5 From the WaveStar® CIT System View main menu, select Fault → Reset →Slot/Circuit Pack

Result: The Reset Slot window is opened.

.................................................................................................................................................................................................

6 Specify the slot where the corresponding circuit pack resides by selecting the slot fromthe equipment selection tree on the left-hand side of the Reset Slot window.Alternatively, you may also enter the slot AID directly into the Enter AID field.

.................................................................................................................................................................................................

7 Click Select.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

8 Specify the type of reset (Full or Controller) by means of the Reset Type checkboxeson the right-hand side of the Reset Slot window.

.................................................................................................................................................................................................

9 Click Apply.

.................................................................................................................................................................................................

10 Important! A full reset of a circuit pack may be service affecting!

If you want to proceed, confirm your selection by clicking Yes in the confirmationwindow.

In the case of a controller reset of the active Controller, the managementassociation between the WaveStar® CIT and the NE will be lost. After the CTLrecovery has finished, you can re-establish the management association by againconnecting the WaveStar® CIT to the NE.

E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-79

Initiating a system reset.................................................................................................................................................................................................................................

Purpose

You may initiate a system reset to bring the entire system in a defined state if yoususpect it to be in a faulty state. As a result the entire system will be re-initialized.

Before you begin

Make sure that you have the required privileges, and that the required equipment isavailable.

Required privilege

You must have at least privilege codes of S4 and M4.

Required equipment


• WaveStar® CIT

Instructions

.................................................................................................................................................................................................

1 By means of the WaveStar® CIT, establish a management association to the respectiveNE.

.................................................................................................................................................................................................

2 From the WaveStar® CIT System View main menu, select Fault → Reset →System

.................................................................................................................................................................................................

3 Important! A system reset may be service affecting!

If you want to proceed, confirm your selection by clicking Yes in the confirmationwindow.

The LambdaUnite® MSS NE will now perform a system reset. As a consequence,the management association between the WaveStar® CIT and the NE will be lost.After the system reset has finished, you can re-establish the managementassociation by again connecting the WaveStar® CIT to the NE.

E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Cross-connection loopbacks.................................................................................................................................................................................................................................

Cross-connection loopbacks can be used to analyze tributary signals.

Functional principle

A cross-connection loopback can be regarded as a unidirectional cross-connection froman input to its related output. There are no bidirectional cross-connection loopbacks.

The following schematical diagram depicts the functional principle of cross-connectionloopbacks.

The selected input tributary is looped back (cross-connected) in the XC320 switch unitto the output of the same tributary.

Important! For cross connection loopbacks it is possible to specify a tributary rateof a different standard than the port interface standard, for example an SDH rate ona SONET port. In the resulting notifications or responses the rate is determined bythe interface standard of the port, and then differs from the rate specified for thecross-connection loopback. Therefore, it is recommended not to use an SDHtributary rate on a SONET port, and vice versa.

Port Unit Port UnitSwitch XC320

O/E

E/O

E/O

O/E

(AIS)


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-81

Dependence on the tributary operation mode

Cross-connection loopbacks can be switched on tributaries on ports configured forfixed-rate tributary operation, and on tributaries on ports configured for adaptive-ratetributary operation:

• For tributaries on ports configured for fixed-rate tributary operation,cross-connection loopbacks are only possible if the rate of the cross-connectionloopback is compatible to the rates defined for the corresponding input and outputtributaries. Compatible means, that, for example, a VC-4 cross-connection loopbackcan be switched on a VC-4 tributary or on an STS-3c tributary and vive versa.

• For tributaries on ports configured for adaptive-rate tributary operation,cross-connection loopbacks are only possible if the rate of the cross-connectionloopback is supported by the corresponding port, and if the tributary boundary iscompatible with the requested loopback rate. Compatible means, that, for example,for a VC-4 or STS-3c cross-connection loopback, the corresponding tributary muststart at a position where also a VC-4 or STS-3c tributary would start (tributarypositions 1, 4, 7, 10 for STS-3c tributaries, or the corresponding timeslots forVC-4 tributaries, cf. “SDH/SONET tributary numbering” (p. 4-87)).

This implies, that the rates of the corresponding input and output tributaries must beconfigured to the same value.

Normal cross-connection loopbacks

A normal cross-connection loopback on a port configured for fixed-rate tributaryoperation is only possible, if there are no existing cross-connections for thecorresponding tributary.

A normal cross-connection loopback on a port configured for adaptive-rate tributaryoperation is only possible, if there are no existing cross-connections for thecorresponding tributary, and if the tributary, for which the loopback is requested, doesnot overlap with any existing cross-connection.

Forced cross-connection loopbacks

By means of a forced cross-connection loopback on a port configured for fixed-ratetributary operation, it is possible to perform a cross-connection loopback even if thereis an existing cross-connection for the corresponding tributary. Existingcross-connections are preempted when a forced cross-connection loopback isperformed. Preempted means that AIS is inserted in the downstream direction, and thesignal in the upstream direction (in the case of a bidirectional cross-connection) isterminated.

Preempting existing cross-connections by means of a forced cross-connection loopbackon a port configured for adaptive-rate tributary operation is only possible, if the rate ofthe existing cross-connection and the rate of the requested cross-connection loopbackare equal. This implies in particular, that forced cross-connection loopbacks are not

Supporting procedures Cross-connection loopbacks

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

possible for tributary rates smaller than the rate of the existing adaptive-ratecross-connection itself.

When the cross-connection loopback is released, any previously existingcross-connections are automatically restored.

Important! It is not possible to switch a cross-connection on a tributary while across-connection loopback is active on this tributary.

Cross-connection loopbacks on path-protected cross-connections

Performing a forced cross-connection loopback on the working or protection leg of apath-protected cross-connection leads to a Signal Fail (SF) condition on thecorresponding leg of the path-protected cross-connection. An SF condition on theworking leg causes a protection switch. An SF condition on the protection leg preventsa protection switch from the working to the protection leg.

“ABN” LED

The yellow “ABN” LED on the LambdaUnite® MSS user panel is lit as long as across-connection loopback is active.

Supporting procedures Cross-connection loopbacks

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-83

Facility loopbacks.................................................................................................................................................................................................................................

Facility loopbacks are loopbacks switched on whole ports. They make it possible toverify the correct system operation and may facilitate troubleshooting of problems.

There are two types of facility loopbacks:

• Near-side facility loopbacksThe signal on the input port is looped to the corresponding output port withtranspassing as few NE components as possible.Near-side facility loopbacks can be switched on all out-of-service optical interfaceports.

• Far-side facility loopbacksThe transmission signal to the output port in the NE is looped back to thecorresponding input port with passing through as many equipment components aspossible.Far-side facility loopbacks can be switched on all out-of-service optical interfaceports as well as on 1-Gbit/s Ethernet ports.

Near-side facility loopbacks

Near-side facility loopbacks can be used to test the correct cabling between twonetwork elements including the involved interface ports.


The following schematical diagram depicts the functional principle of near-side facilityloopbacks.

The incoming signal at the input port is, after optical-to-electrical conversion, entirelylooped back to the output port.


O/E

O/E

E/O

E/O


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Near-side facility loopbacks are characterized as follows:

• Near-side facility loopbacks are transparent, the signal transmitted in thedownstream direction is not changed.

• The signal transmitted in the original (downstream) direction is different from thesignal looped back. Particular Section/RS and Line/MS Overhead bytes, such asthose used for frame alignment (A1, A2) or bit error monitoring (B1, B2) forexample, are not looped back but processed. The Path Overhead (POH) and thepayload signal, however, are looped back unchanged.

• The incoming signal in the upstream direction is terminated during the loopback.

Far-side facility loopbacks

Far-side facility loopbacks can be used to test signal paths through a network element.


The following schematical diagram depicts the functional principle of far-side facilityloopbacks.

Far-side facility loopbacks are characterized as follows:

• Far-side facility loopbacks are non-transparent, the signal transmitted in the original(downstream) direction is different from the signal looped back. Line AIS (SONET)or MS-AIS (SDH) respectively is inserted into the outgoing signal in thedownstream direction during the loopback.

• The signal is not changed before it is looped back.

• The incoming signal in the upstream direction is terminated during the loopback.

Important! No AIS insertion for OP2G5, OP622, OP155.

The AIS insertion as characterized above does not take place for OP2G5, OP622,OP155 packs. For these units the signal is transparently passed through.


O/E

O/E

AIS

E/O

E/O

Supporting procedures Facility loopbacks

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-85

Configuration Rules

Consider the following configuration rules to perform facility loopbacks:

• Before a (near-side or far-side) facility loopback can be performed, thecorresponding port must be set out-of-service.

• When a (near-side or far-side) facility loopback is active, no line timing referencescan be assigned.

• When a line timing reference is assigned, no facility loopbacks can be performed.

• After an upgrade of the NE software (Release 2.1 → Release 3.0) perform a fullreset of all installed OP155 circuit packs. Otherwise, it may happen that near-sidefacility loopbacks are only possible on ports 1 and 9 of the OP155 circuit packs.

Related information

Please refer to:

• “Performing facility loopbacks” (p. 4-30)

• “Releasing a facility loopback” (p. 4-33)

Supporting procedures Facility loopbacks

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

SDH/SONET tributary numbering.................................................................................................................................................................................................................................

In this section, the SDH and SONET tributary numbering scheme will be described indetail.

A special numbering format is used for SDH tributaries whereas the SONET tributarynumbering format is relatively straight-forward. Moreover, the tributary numberingdepends on the port rate, and therefore the subsequent description is structured inaccordance with the LambdaUnite® MSS SDH/SONET port rates.

OC-3/STM-1 port

The following figure shows the possible substructuring of an OC-3/STM-1 signal andthe associated SDH and SONET tributary numbering schemes.

OC-12/STM-4 port

The following figure shows the possible substructuring of an OC-12/STM-4 signal andthe associated SDH and SONET tributary numbering schemes.

10

133122111 1

SONET SDH

VC-3STS-1STS-3c/

VC-4

110

120

130

140

143121421114110 10133913281317 7123612251214 4113311221111 1 1 100

SONET SDH

VC-3STS-1 VC-4STS-3cSTS-12c/VC-4-4C


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-87

OC-48/STM-16 port

The following figure shows the possible substructuring of an OC-48/STM-16 signaland the associated SDH and SONET tributary numbering schemes.

SONET SDHVC-3STS-3c STS-12c

STS-48c/

VC-4VC-4-4CVC-4-16CSTS-1123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748

1

4

7

10

13

16

19

22

25

28

31

34

37

40

43

46

1

13

25

37

1 110

120

130

140

210

220

230

240

310

320

330

340

410

420

430

440

111112113121122123131132133141142143211212213221222223231232233241242243311312313321322323331332333341342343411412413421422423431432433441442443

100

200

300

400

000

Supporting procedures SDH/SONET tributary numbering

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

OC-192/STM-64 port


SONET SDHVC-3STS-3c STS-12c STS-48c

STS-192c/VC-4VC-4-4CVC-4-64C VC-4-16CSTS-1

123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748

1

4

7

10

13

16

19

22

25

28

31

34

37

40

43

46

1

13

25

37

1 1 1110

1120

1130

1140

1210

1220

1230

1240

1310

1320

1330

1340

1410

1420

1430

1440

111111121113112111221123113111321133114111421143121112121213122112221223123112321233124112421243131113121313132113221323133113321333134113421343141114121413142114221423143114321433144114421443

1100

1200

1300

1400

10000000


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-89

SONET(continued) SDHVC-3STS-3c STS-12c STS-48c


495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596

49

52

55

58

61

64

67

70

73

76

79

82

85

88

91

94

49

61

73

85

49 2110

2120

2130

2140

2210

2220

2230

2240

2310

2320

2330

2340

2410

2420

2430

2440

211121122113212121222123213121322133214121422143221122122213222122222223223122322233224122422243231123122313232123222323233123322333234123422343241124122413242124222423243124322433244124422443

2100

2200

2300

2400

2000


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



979899

100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144

97

100

103

106

109

112

115

118

121

124

127

130

133

136

139

142

97

109

121

133

97 3110

3120

3130

3140

3210

3220

3230

3240

3310

3320

3330

3340

3410

3420

3430

3440

311131123113312131223123313131323133314131423143321132123213322132223222323132323233324132423243331133123313332133223323333133323333334133423343341134123413342134223423343134323433344134423443

3100

3200

3300

3400

3000


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-91



145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192

145

148

151

154

157

160

163

166

169

172

175

178

181

184

187

190

145

157

169

181

145 4110

4120

4130

4140

4210

4220

4230

4240

4310

4320

4330

4340

4410

4420

4430

4440

411141124113412141224123413141324133414141424143421142124213422142224222423142324233424142424243431143124313432143224323433143324333434143424343441144124413442144224423443144324433444144424443

4100

4200

4300

4400

4000


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

OC-768/STM-256 port




123456789

101112131415161718192021222324252627282930313233343536373839404142434445464748

1

4

7

10

13

16

19

22

25

28

31

34

37

40

43

46

1

13

25

37

1 1 11110

11120

11130

11140

11210

11220

11230

11240

11310

11320

11330

11340

11410

11420

11430

11440

111111111211113111211112211123111311113211133111411114211143112111121211213112211122211223112311123211233112411124211243113111131211313113211132211323113311133211333113411134211343114111141211413114211142211423114311143211433114411144211443

11100

11200

11300

11400

1100010000


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-93



495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596

49

52

55

58

61

64

67

70

73

76

79

82

85

88

91

94

49

61

73

85

49 12110

12120

12130

12140

12210

12220

12230

12240

12310

12320

12330

12340

12410

12420

12430

12440

121111211212113121211212212123121311213212133121411214212143122111221212213122211222212223122311223212233122411224212243123111231212313123211232212323123311233212333123411234212343124111241212413124211242212423124311243212433124411244212443

12100

12200

12300

12400

12000


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



979899

100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144

97

100

103

106

109

112

115

118

121

124

127

130

133

136

139

142

97

109

121

133

97 13110

13120

13130

13140

13210

13220

13230

13240

13310

13320

13330

13340

13410

13420

13430

13440

131111311213113131211312213123131311313213133131411314213143132111321213213132211322213222132311323213233132411324213243133111331213313133211332213323133311333213333133411334213343134111341213413134211342213423134311343213433134411344213443

13100

13200

13300

13400

13000


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-95



145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192

145

148

151

154

157

160

163

166

169

172

175

178

181

184

187

190

145

157

169

181

145 14110

14120

14130

14140

14210

14220

14230

14240

14310

14320

14330

14340

14410

14420

14430

14440

141111411214113141211412214123141311413214133141411414214143142111421214213142211422214222142311423214233142411424214243143111431214313143211432214323143311433214333143411434214343144111441214413144211442214423144311443214433144411444214443

14100

14200

14300

14400

14000


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240

193

196

199

202

205

208

211

214

217

220

223

226

229

232

235

238

193

205

217

229

193 193 21110

21120

21130

21140

21210

21220

21230

21240

21310

21320

21330

21340

21410

21420

21430

21440

211112111221113211212112221123211312113221133211412114221143212112121221213212212122221223212312123221233212412124221243213112131221313213212132221323213312133221333213412134221343214112141221413214212142221423214312143221433214412144221443

21100

21200

21300

21400

2100020000

(continued)


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-97



241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288

241

244

247

250

253

256

259

262

265

268

271

274

277

280

283

286

241

253

265

277

241 22110

22120

22130

22140

22210

22220

22230

22240

22310

22320

22330

22340

22410

22420

22430

22440

221112211222113221212212222123221312213222133221412214222143222112221222213222212222222223222312223222233222412224222243223112231222313223212232222323223312233222333223412234222343224112241222413224212242222423224312243222433224412244222443

22100

22200

22300

22400

22000


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



289290291292293294295296297298299300301302303304305306

310

320321322323324325326327328329330331332333334335336

307308309

311312313314315316317318319

289

292

301

331

334

295

298

304

307

310

313

316

319

322

325

328

289

301

313

325

289 23110

23120

23130

23140

23210

23220

23230

23240

23310

23320

23330

23340

23410

23420

23430

23440

231112311223113231212312223123231312313223133231412314223143232112321223213232212322223223232312323223233232412324223243233112331223313233212332223323233312333223333233412334223343234112341223413234212342223423234312343223433234412344223443

23100

23200

23300

23400

23000


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-99



337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384

337

340

343

346

349

352

355

358

361

364

367

370

373

376

379

382

337

349

361

373

337 24110

24120

24130

24140

24210

24220

24230

24240

24310

24320

24330

24340

24410

24420

24430

24440

241112411224113241212412224123241312413224133241412414224143242112421224213242212422224222242312423224233242412424224243243112431224313243212432224323243312433224333243412434224343244112441224413244212442224423244312443224433244412444224443

24100

24200

24300

24400

24000


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432

385

388

391

394

397

400

403

406

409

412

415

418

421

424

427

430

385

397

409

421

385 385 31110

31120

31130

31140

31210

31220

31230

31240

31310

31320

31330

31340

31410

31420

31430

31440

311113111231113311213112231123311313113231133311413114231143312113121231213312213122231223312313123231233312413124231243313113131231313313213132231323313313133231333313413134231343314113141231413314213142231423314313143231433314413144231443

31100

31200

31300

31400

3100030000

(continued)


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-101



433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480

433

436

439

442

445

448

451

454

457

460

463

466

469

472

475

478

433

445

457

469

433 32110

32120

32130

32140

32210

32220

32230

32240

32310

32320

32330

32340

32410

32420

32430

32440

321113211232113321213212232123321313213232133321413214232143322113221232213322213222232223322313223232233322413224232243323113231232313323213232232323323313233232333323413234232343324113241232413324213242232423324313243232433324413244232443

32100

32200

32300

32400

32000


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



481482483484485486487488489490491492493494495496497498

502

512513514515516517518519520521522523524525526527528

499500501

503504505506507508509510511

481

484

493

523

526

487

490

496

499

502

505

508

511

514

517

520

481

493

505

517

481 33110

33120

33130

33140

33210

33220

33230

33240

33310

33320

33330

33340

33410

33420

33430

33440

331113311233113331213312233123331313313233133331413314233143332113321233213332213322233223333313323233333332413324233243333113331233313333213332233323333313333233333333413334233343334113341233413334213342233423334313343233433334413344233443

33100

33200

33300

33400

33000


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-103



529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576

529

532

535

538

541

544

547

550

553

556

559

562

565

568

571

574

529

541

553

565

529 34110

34120

34130

34140

34210

34220

34230

34240

34310

34320

34330

34340

34410

34420

34430

34440

341113411234113341213412234123341313413234133341413414234143342113421234213342213422234222342313423234233342413424234243343113431234313343213432234323343313433234333343413434234343344113441234413344213442234423344313443234433344413444234443

34100

34200

34300

34400

34000


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



577578579

581582583584585586587588589

591592593594595596597598599

601602603604605606607608609

611612613614615616617618619

621622623624

580

590

600

610

620

577

580

583

586

589

592

595

598

601

604

607

610

613

616

619

622

577

589

601

613

577 577 41110

41120

41130

41140

41210

41220

41230

41240

41310

41320

41330

41340

41410

41420

41430

41440

411114111241113411214112241123411314113241133411414114241143412114121241213412214122241223412314123241233412414124241243413114131241313413214132241323413314133241333413414134241343414114141241413414214142241423414314143241433414414144241443

41100

41200

41300

41400

4100040000

(continued)


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-105



625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672

625

628

631

634

637

640

643

646

649

652

655

658

661

664

667

670

625

637

649

661

625 42110

42120

42130

42140

42210

42220

42230

42240

42310

42320

42330

42340

42410

42420

42430

42440

421114211242113421214212242123421314213242133421414214242143422114221242213422214222242223422314223242233422414224242243423114231242313423214232242323423314233242333423414234242343424114241242413424214242242423424314243242433424414244242443

42100

42200

42300

42400

42000


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005



673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720

673

676

679

682

685

688

691

694

697

700

703

706

709

712

715

718

673

685

697

709

673 43110

43120

43130

43140

43210

43220

43230

43240

43310

43320

43330

43340

43410

43420

43430

43440

431114311243113431214312243123431314313243133431414314243143432114321243213432214322243223432314323243233432414324243243433114331243313433214332243323433314333243333433414334243343434114341243413434214342243423434314343243433434414344243443

43

43200

43300

43400

10043000


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-107



721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768

721

724

727

730

733

736

739

742

745

748

751

754

757

760

763

766

721

733

745

757

721 44110

44120

44130

44140

44210

44220

44230

44240

44310

44320

44330

44340

44410

44420

44430

44440

441114411244113441214412244123441314413244133441414414244143442114421244213442214422244222442314423244233442414424244243443114431244313443214432244323443314433244333443414434244343444114441244413444214442244423444314443244433444414444244443

44100

44200

44300

44400

44000


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

VCG port

The following figure shows the possible substructuring of a VCG port signal and theassociated SDH and SONET tributary numbering schemes.

SONET SDHVC-4STS-1

123456789

101112131415161718192021

110

120

130

140

210

220

230


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-109


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

TXI bus line numbering scheme.................................................................................................................................................................................................................................

Introduction

The TXI bus interconnects port units and cross-connect and timing units (XCs) for thepurpose of NE-internal distribution of transport signals. Each TXI bus line provides atransmission capacity of 2.5 Gbit/s.

Concerning the TXI bus line numbering, a distinction has to be made between differenttypes of circuit packs:

• Single-slot port units (port units other than OP40)

• Multi-slot port units (OP40 port units, occupying 4 universal slots)

• Cross-connect and timing units (XCs, in the worker and protection slots)

Single-slot port units

In the receive direction (from the view point of a single-slot port unit), the associationbetween the XCs and the port units in the universal slots of a LambdaUnite® MSSshelf is as follows (the TXI bus line numbering is independent from the slot numberwhere the port unit is installed):

XC (Worker)

TXInF TXInF

TXInF

Port unit

XC (Protection)

TXI bus


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-111

The alarm-reporting circuit pack (receiver) is a single-slot port unit in a universal slot.The associated sender is the XC in the worker or protection slot as shown below (depending on the TXI busline indicated in the alarm message, and the port unit type).

TXI bus line Cross-connect and timing unit

1 XC in the worker slot (slot 9)

2

3

4

5

6

7

8

9 XC in the protection slot (slot 10)

10

11

12

13

14

15

16

If, for example, a TXI Failure alarm (TXI9F) is reported by a single-slot port unit,then the TXI signal originates from the XC in the protection slot.

Multi-slot port units

In the receive direction (from the view point of an OP40), the association between theXCs and the OP40s in the universal slots of a LambdaUnite® MSS shelf is as follows

Supporting procedures TXI bus line numbering scheme

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

(the TXI bus line numbering is independent from the slot quadruple where the OP40 isinstalled):

The alarm-reporting circuit pack (receiver) is an OP40 port unit.The associated sender is the XC in the worker or protection slot as shown below (depending on the TXI busline indicated in the alarm message).

TXI bus line Cross-connect and timing unit TXI bus line

1 XC in the worker slot 17

2 18

3 19

4 20

5 21

6 22

7 23

8 24

9 XC in the protection slot 25

10 26

11 27

12 28

13 29

14 30

15 31

16 32

If, for example, a TXI Failure alarm (TXI19F) is reported by an OP40 port unit, thenthe TXI signal originates from the XC in the worker slot.

Cross-connect and timing units

In the receive direction (from the view point of an XC160 or XC320 cross-connect andtiming unit), the association between the port units in the universal slots of aLambdaUnite® MSS shelf and the XCs is as indicated in the following tables (there isno difference in the TXI bus line numbering between the XC in the worker andprotection slots).

Single-slot port units, LambdaUnite® MSS releases prior to Release 4.0

The following table is valid for single-slot port units, and LambdaUnite® MSS releasesprior to Release 4.0:


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-113


The alarm-reporting circuit pack (receiver) is the XC in the worker or protection slot.The associated sender is a single-slot port unit in the universal slot as shown below (depending on the TXI bus line indicatedin the alarm message).

TXI bus line Universal slot TXI bus line Universal slot TXI bus line Universal slot TXI bus line Universal slot

1 1 33 12 65 21 97 32

2 34 66 98

3 35 67 99

4 36 68 100

5 2 37 13 69 22 101 33

6 38 70 102

7 39 71 103

8 40 72 104

9 3 41 14 73 23 105 34

10 42 74 106

11 43 75 107

12 44 76 108

13 4 45 15 77 24 109 35

14 46 78 110

15 47 79 111

16 48 80 112

17 5 49 16 81 25 113 36

18 50 82 114

19 51 83 115

20 52 84 116

21 6 53 17 85 26 117 37

22 54 86 118

23 55 87 119

24 56 88 120

25 7 57 18 89 27 121 38

26 58 90 122

27 59 91 123

28 60 92 124


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005


The alarm-reporting circuit pack (receiver) is the XC in the worker or protection slot.The associated sender is a single-slot port unit in the universal slot as shown below (depending on the TXI bus line indicatedin the alarm message).


29 8 61 19 93 28 125 39

30 62 94 126

31 63 95 127

32 64 96 128

OP40 port units, LambdaUnite® MSS releases prior to Release 4.0

The following table is valid for OP40 port units, and LambdaUnite® MSS releasesprior to Release 4.0:


The alarm-reporting circuit pack (receiver) is the XC in the worker or protection slot.The associated sender is an OP40 port unit in the universal slots as shown below (depending on the TXI bus line indicated inthe alarm message).

TXI bus line Universalslots




1 1 - 4 33 12 - 15 65 21 - 24 97 32 - 35

2 34 66 98

3 35 67 99

4 36 68 100

5 37 69 101

6 38 70 102

7 39 71 103

8 40 72 104

9 41 73 105

10 42 74 106

11 43 75 107

12 44 76 108

13 45 77 109

14 46 78 110

15 47 79 111

16 48 80 112


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-115


The alarm-reporting circuit pack (receiver) is the XC in the worker or protection slot.The associated sender is an OP40 port unit in the universal slots as shown below (depending on the TXI bus line indicated inthe alarm message).





17 5 - 8 49 16 - 19 81 25 - 28 113 36 - 39

18 50 82 114

19 51 83 115

20 52 84 116

21 53 85 117

22 54 86 118

23 55 87 119

24 56 88 120

25 57 89 121

26 58 90 122

27 59 91 123

28 60 92 124

29 61 93 125

30 62 94 126

31 63 95 127

32 64 96 128

LambdaUnite® MSS Release 4.0 and onwards

The following table is valid for LambdaUnite® MSS Release 4.0 and onwards:


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005


The alarm-reporting circuit pack (receiver) is the XC in the worker or protection slot.The associated sender is a port unit in the universal slot(s) as shown below (depending on the TXI bus line indicated in thealarm message).


11, 2 1 651, 2 12 1291, 2 21 1931, 2 32

21, 2 661, 2 1301, 2 1941, 2

31, 2 671, 2 1311, 2 1951, 2

41, 2 681, 2 1321, 2 1961, 2

51 691 133 197

61 701 134 198

71 711 135 199

81 721 136 200

91 2 731 13 137 22 201 33

101 741 138 202

111 751 139 203

121 761 140 204

131 771 141 205

141 781 142 206

151 791 143 207

161 801 144 208

171, 2 3 811, 2 14 1451, 2 23 2091, 2 34

181, 2 821, 2 1461, 2 2101, 2

191, 2 831, 2 1471, 2 2111, 2

201, 2 841, 2 1481, 2 2121, 2

211 851 149 213

221 861 150 214

231 871 151 215

241 881 152 216


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-117




251 4 891 15 153 24 217 35

261 901 154 218

271 911 155 219

281 921 156 220

291 931 157 221

301 941 158 222

311 951 159 223

321 961 160 224

331, 2 5 971, 2 16 1611, 2 25 2251, 2 36

341, 2 981, 2 1621, 2 2261, 2

351, 2 991, 2 1631, 2 2271, 2

361, 2 1001, 2 1641, 2 2281, 2

371 1011 165 229

381 1021 166 230

391 1031 167 231

401 1041 168 232

411 6 1051 17 169 26 233 37

421 1061 170 234

431 1071 171 235

441 1081 172 236

451 1091 173 237

461 1101 174 238

471 1111 175 239

481 1121 176 240


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005




491, 2 7 1131, 2 18 1771, 2 27 2411, 2 38

501, 2 1141, 2 1781, 2 2421, 2

511, 2 1151, 2 1791, 2 2431, 2

521, 2 1161, 2 1801, 2 2441, 2

531 1171 181 245

541 1181 182 246

551 1191 183 247

561 1201 184 248

571 8 1211 19 185 28 249 39

581 1221 186 250

591 1231 187 251

601 1241 188 252

611 1251 189 253

621 1261 190 254

631 1271 191 255

641 1281 192 256

Notes:

1. These TXI bus lines are not applicable to the XC160 cross-connect and timing unit (as port units canonly be equipped in the upper row of the DUR shelf in a configuration with XC160, i.e. in the universalslots 21 28 and 32 39).

2. These TXI bus lines are not applicable to the XC320 cross-connect and timing unit.

If, for example, a TXI Failure alarm (TXI181F) is reported by an XC, then the TXIsignal originates from the port unit installed in slot 27 (this can be a single-slot portunit, or an OP40 installed in slots 25, 26, 27 and 28).


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


4-119

5 5Exceptional situations notreflected by alarm messages

Overview.................................................................................................................................................................................................................................

Purpose

This chapter contains information about exceptional situations that may occur duringthe operation of a LambdaUnite® MSS network element, and which are not reflectedby alarm messages.

Contents

Solving (and avoiding) Controller recovery problems 5-2

System autonomously entered the maintenance condition 5-8

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


5-1

Solving (and avoiding) Controller recovery problems.................................................................................................................................................................................................................................

Purpose

Use these procedures to solve Controller (CTL) recovery problems, and to proactivelyavoid such problems. CTL recovery problems means that a CTL fails to recover(reboot).

Possible reasons

CTL recovery problems may be caused by a corrupted and thus unreadableCompactFlash® card. A CompactFlash® card may be damaged when its power supplyis interrupted while it is accessed for a read or write operation.

These situations can be distinguished in which CTL recovery problems may occur:

1. When a CTL is re-inserted which was not adequately removed from its slot(without following the → “Recommended procedure for removing a CTL from itsslot” (p. 5-5)).

2. When the power supply is restored after a System Power Failure. TheCompactFlash® card may have been damaged when the system power was lost.

3. When a network element is taken into operation again which was previously takenout of operation without following the → “Recommended deinstallation procedure”(p. 5-6).

Solving CTL recovery problems

.................................................................................................................................................................................................

1 If then

the problem has occurred after aSystem Power Failure

carry out Step 2 to Step 7.

the problem has occurred duringa re-installation

proceed with Step 8.

Assumptions

The following assumptions are made in that case:

• No circuit packs are equipped, i.e. the shelf isempty, when the power is switched on.

• Subsequently a CTL is installed in the workerslot (CTL-W, with an existing NE configurationdatabase stored on its CompactFlash® card).

• The CTL-W does not recover.

This installation sequence complies to theprocedure for the first installation as described inthe LambdaUnite® MSS Installation Guide.

Exceptional situations not reflected by alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

2 If then

there is only one CTL equipped(simplex control)

replace the currently used CompactFlash® card.

Reference: “Replacing a CompactFlash® card”(p. 4-48)

there are two CTLs equipped(duplex control), and one of themfailed to recover

1. remove the CTL that failed to recover from itsslot,

2. insert a new, vendor-formatted CompactFlash®

card into the CompactFlash® drive, and

3. re-insert the CTL.

there are two CTLs equipped(duplex control), and both failedto recover

proceed with the next step.

.................................................................................................................................................................................................

3 Replace the currently used CompactFlash® card for one of the two CTLs by followingthe procedure for replacing a defective CompactFlash® card.


.................................................................................................................................................................................................

4 Wait for the just inserted CTL to recover.

.................................................................................................................................................................................................

5 Remove the second CTL from its slot.

.................................................................................................................................................................................................

6 Insert a new, vendor-formatted CompactFlash® card into the CompactFlash® drive ofthe second CTL.

.................................................................................................................................................................................................

7 Re-insert the second CTL.

Result: The NE configuration database will be synchronized between the twoCTLs.

.................................................................................................................................................................................................

8 Remove the CTL-W from its slot.

Exceptional situations not reflected by alarm messages Solving (and avoiding) Controller recovery problems

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


5-3

.................................................................................................................................................................................................

9 If then

a protection CTL (duplex CTL,CTL-P) is available (depends onthe previous NE configuration)

insert the CTL-P into the protection slot, andproceed with the next step.

no protection CTL (duplex CTL,CTL-P) is available

replace the currently used CompactFlash® card forthe CTL-W by following the procedure forreplacing a defective CompactFlash® card.


.................................................................................................................................................................................................

10 If then

the just inserted CTL-P recoverssuccessfully

1. install all the remaining circuit packs,

2. insert a new, vendor-formatted CompactFlash®

card into the CompactFlash® drive of theCTL-W, and

3. re-insert the CTL-W.


the just inserted CTL-P does notrecover

replace the currently used CompactFlash® card forthe CTL-W by following the procedure forreplacing a defective CompactFlash® card.


.................................................................................................................................................................................................

11 Wait for the CTL-W to recover.

.................................................................................................................................................................................................

12 Install all the remaining circuit packs.

.................................................................................................................................................................................................

13 Install the CTL-P.

.................................................................................................................................................................................................

14 If then

the CTL-P recovers successfully Stop! You have completed this procedure.


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

If then

the CTL-P does not recover 1. insert a new, vendor-formatted CompactFlash®

card into the CompactFlash® drive of theCTL-P, and

2. re-insert the CTL-P.

.................................................................................................................................................................................................

15 Wait for the CTL-W to recover.


Recommended procedure for removing a CTL from its slot

CAUTION

ESD hazard


Hold circuit packs only at the edges or on the insertion and removal facilities. Circuitpacks must always be kept in antistatic covers. Use the original antistatic packaging ifpossible. Always observe the ESD instructions (cf. “Electrostatic discharge” (p. 1-20)).

In order to avoid damaging the CompactFlash® card, proceed as follows to remove aCTL from its slot:

.................................................................................................................................................................................................

1 Open the latches of the CTL to be removed.

Important! Do not remove the CTL from its slot at that time!

Result: The green “ACTIVE” LED on the faceplate of the CTL starts flashing.

.................................................................................................................................................................................................

2 Wait until the green “ACTIVE” LED has stopped flashing (about five seconds).

.................................................................................................................................................................................................

3 Remove the CTL from its slot.

Important! Use the original antistatic packaging for storage and transport, ifpossible.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


5-5

E N D O F S T E P S.................................................................................................................................................................................................

E N D O F S T E P S.................................................................................................................................................................................................

Recommended deinstallation procedure

CAUTION

ESD hazard


Hold circuit packs only at the edges or on the insertion and removal facilities. Circuitpacks must always be kept in antistatic covers. Use the original antistatic packaging ifpossible. Always observe the ESD instructions (cf. “Electrostatic discharge” (p. 1-20)).

Proceed as follows to take a network element (NE) out of operation:

.................................................................................................................................................................................................

1 If two CTLs are equipped (duplex control), then open the latches of the standby CTL.Otherwise, proceed with Step 4.

Important! Do not remove the standby CTL from its slot at that time!

Result: The green “ACTIVE” LED on the faceplate of the standby CTL startsflashing.

.................................................................................................................................................................................................


.................................................................................................................................................................................................

3 If then

you want to temporarily switchoff the NE (while maintainingthe configuration)

slightly pull out the standby CTL (approx. 2 cm),so that there is no connection to the backplane.

you want to completely deinstallthe NE (for example, to move itto another location, and re-installit)

remove the standby CTL from its slot. Use theoriginal antistatic packaging for storage andtransport, if possible.

.................................................................................................................................................................................................

4 Open the latches of the active CTL.

Important! Do not remove the active CTL from its slot at that time!

Result: The green “ACTIVE” LED on the faceplate of the active CTL startsflashing.

.................................................................................................................................................................................................



.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................

6 If then

you want to temporarily switchoff the NE (while maintainingthe configuration)

slightly pull out the active CTL (approx. 2 cm), sothat there is no connection to the backplane.

you want to completely deinstallthe NE (for example, to move itto another location, and re-installit)

remove the active CTL from its slot. Use theoriginal antistatic packaging for storage andtransport, if possible.

.................................................................................................................................................................................................

7 Switch off the NE power supply by means of the circuit breakers on both PowerInterfaces (position 0 = OFF).

.................................................................................................................................................................................................

8 Remove all other circuit packs from the shelf. Use the original antistatic packaging forstorage and transport, if possible.

E N D O F S T E P S........................................................................................................................................................................................................................


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


5-7

System autonomously entered the maintenance condition.................................................................................................................................................................................................................................

Maintenance condition

The maintenance condition (or “maintenance mode”) is an exceptional mode ofoperation characterized as follows:

• The system behaves as if the Controller was not present (transmission services arenot affected).

• The internal communication between the Controller and the function controllers oncircuit packs is disabled.

• A software download from the Controller to the function controllers on circuitpacks is not possible.

• Only those autonomous state change events (i.e. also notifications) that do notchange the active configuration database (NVM) are allowed.

• Only a limited set of operations is allowed:

– Changing the NE name (only possible in maintenance mode).

– Setting the NE’s date and time.

– Changing the default value for the NE’s synchronization mode (only possible inmaintenance mode).

– Changing the default value for the optical interface standard.

– Changing the default value for the tributary operation mode.

– Setting an IP address, both for IP access on LAN, and for the SCN (onlypossible in maintenance mode).

– Setting the IP default router address and LAN port (only possible inmaintenance mode).

– Setting the T-TD raw mode and length value port.

– Setting the LAN status (general, OSI, IP), designated router, osinode, and TLSSof LANs.

– Performing a database download.

– Retrieving data from the active configuration database (NVM).

– Leaving (terminating) the maintenance mode (only possible in maintenancemode).

• Write access to the active configuration database (NVM) is restricted to those datarelated to the limited set of operations that are allowed in maintenance mode.

The maintenance mode can either be entered manually to perform operations that areonly possible in maintenance mode, such as changing the NE name (TID) for example,or autonomously by the system when an exceptional situation occurred.

Exceptional situations not reflected by alarm messages

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Reasons for autonomously entering the maintenance mode

The following description lists the possible reasons why a LambdaUnite® MSS systemautonomously enters the maintenance mode, and gives recommendations how toresolve the “problem”:

1. An empty database is detected during startupPerform a database restore using the most recent database backup.

2. A new database is detected during startupPerform a database restore using the most recent database backup, or leave themaintenance mode (see “Leaving the maintenance mode” (p. 5-10)) if you areabsolutely sure that the current system configuration and the configuration databaseon the NVM are compatible.

Empty database

An empty database is detected during startup

Perform a database restore using the most recent database backup.

New database

A new database is detected during startup

Perform a database restore using the most recent database backup, or leave themaintenance mode (see “Leaving the maintenance mode” (p. 5-10)) if you areabsolutely sure that the current system configuration and the configuration database onthe NVM are compatible.

Unsuitable Controller variant

A Controller of type CTL/- is present, and during startup it is detected that theCross-Connect Application is set to ONNS.

The CTL/- Controller variant does not support ONNS applications. For ONNSapplications the CTL/2 Controller variant is mandatory.

Either adapt the system equipage to meet the requirements for using ONNS, orprovision the system according to the current equipage.

Unsuitable optical interface module

An optical interface module has been detected which is not qualified for the use withina LambdaUnite® MSS system.

Make sure that all optical interface modules used are qualified for the use withinLambdaUnite® MSS systems. Only the recommended versions of optical interfacemodules are guaranteed to meet the LambdaUnite® MSS system requirements (withregard to the EMC/ESD performance or transmission characteristics for example).

Please refer to the LambdaUnite® MSS Applications and Planning Guide and theLambdaUnite® MSS User Operations Guide for information on the recommendedversions of optical interface modules.

Exceptional situations not reflected by alarm messages System autonomously entered the maintenance condition

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


5-9

Leaving the maintenance mode

You can terminate (leave) the maintenance mode by selecting Fault → Enter/ExitMaintenance Condition... → Exit Maintenance Condition... from the WaveStar® CITSystem View main menu.

Important! Do not leave the maintenance mode unless you are absolutely sure thatthe current system configuration and the configuration database on the NVM arecompatible.

Exceptional situations not reflected by alarm messages System autonomously entered the maintenance condition

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Appendix A: Maintenance servicesand technical support

Overview.................................................................................................................................................................................................................................

Purpose

This appendix provides information about the maintenance services and the technicalsupport available for the LambdaUnite® MultiService Switch (MSS).

Contents

Maintenance services A-2

Technical support A-3

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


A-1

Maintenance services.................................................................................................................................................................................................................................

This section describes the maintenance services available to support LambdaUnite®

MSS.

Description

Maintenance Services is composed of three primary services to support yourmaintenance needs. The services are

• Remote Technical Support Service (RTS)

• On-site Technical Support Service (OTS)

• Repair and Exchange Services (RES)

Remote Technical Support Service (RTS)

RTS provides telephone and web-based access to remote engineers and tools forproduct information, network diagnostics, and trouble resolution and restoration for allLucent products.

On-site Technical Support (OTS)

OTS provide network trouble resolution and restoration, at the customer’s location, forall Lucent products and selected OEM equipment.

Repair and Exchange Services (RES)

RES provides advanced exchange or return for repair services for defective hardware,eliminating the need for you to purchase and maintain a costly spares inventory.

Contact

For maintenance service contact information please refer to “Technical support”(p. A-3).

Maintenance services and technical support

.................................................................................................................................................................................................................................

A-2 Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

Technical support.................................................................................................................................................................................................................................

This section describes the technical support available for LambdaUnite® MSS.

Services

LambdaUnite® MSS is complemented by a full range of services available to supportplanning, maintaining, and operating your system. Applications testing, networkintegration, and upgrade/conversion support is also available.

Technical support groups

Technical support is available through

• Local/Regional Customer Support (LCS/RCS)

• Technical Support Service (TSS).

Contacting your LCS/RCS

LCS/RCS personnel troubleshoot field problems 24 hours a day over the phone and onsite (if necessary) based on Lucent Technologies Service Contracts:

for north and south America(NAR and CALA)

Customer Technical Assistance Management(CTAM):

• +1 866 Lucent8 (prompt#1)

• +1 630 224 4672 (from outside the UnitedStates)

for Europe, Africa, Asia and thepacific region (EMEA andAPAC)

International Customer Management Centre (ICMC):

• +353 1 692 4579 (toll number)

• 00 800 00Lucent (toll free number in mostEMEA countries)

For technical assistance, call your Local/Regional Customer Support Team. If therequest cannot be solved by LCS/RCS, it will be escalated to the central TechnicalSupport Service (TSS) teams in Merrimack Valley, USA or Nuremberg, Germany.

Technical Support Service

Lucent Technologies Technical Support Service (TSS) organization is committed toproviding customers with quality product support services. Each segment of the TSSorganization regards the customer as its highest priority and understands yourobligations to maintain quality services for your customers.

Maintenance services and technical support

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


A-3

The TSS team maintains direct contact with Lucent Technologies manufacturing, BellLaboratories development, and other organizations to assure fast resolution of allassistance requests.

Technical support platform

A global online trouble tracking system is used by all support teams to track customerassistance requests. The system communicates details about product bulletins,troubleshooting procedures, and other critical information to customers. All details of arequest are entered into this database until closure. For online access to your troubletickets via the web please contact your local support team.

Reference

For additional information about technical support, please contact your LucentTechnologies Customer Team.

Maintenance services and technical support Technical support

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Product support levels

The following figure shows the levels of product support for Lucent Technologiesproducts.


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


A-5


.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Appendix B: A comparison ofLambdaUnite® MSS and WaveStar®

TDM 10G (STM-64) alarms

Overview.................................................................................................................................................................................................................................

Purpose

This appendix contains an overview table for comparing similar LambdaUnite® MSSand WaveStar® TDM 10G (STM-64) alarm messages.

Contents

Tabular overview of LambdaUnite® MSS and WaveStar® TDM 10G(STM-64) alarms

B-2

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


B-1

Tabular overview of LambdaUnite® MSS and WaveStar® TDM10G (STM-64) alarms.................................................................................................................................................................................................................................

Overview table

The following table gives an overview of LambdaUnite® MSS and WaveStar® TDM10G (STM-64) alarm messages. It provides a means to compare similar alarmmessages which may have differnt probable causes and/or alarm descriptions.

A comparison of LambdaUnite® MSS and WaveStar®


.................................................................................................................................................................................................................................

B-2 Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

AS

AP

Typ

eL

amb

daU

nit

e®

MS

SW

aveS

tar®

TD

M10

G(S

TM

-64)

AS

AP

Par

amet

erC

on

dit

ion

Typ

e(p

rob

able

cau

se)

Ala

rmD

escr

ipti

on

AS

AP

Par

amet

erC

on

dit

ion

Typ

e(p

rob

able

cau

se)

Ala

rmD

escr

ipti

on

PO

RT

“ai

dtyp

e”

ison

eof

OC

3,O

C12

,O

C48

,O

C19

2,O

C76

8,S

TM

1E,

ST

M1,

ST

M4,

ST

M16

,S

TM

64,

ST

M25

6“

rr”

ison

eof

ST

M1,

ST

M1E

,S

TM

4,S

TM

16,

ST

M64

sa_o

chlo

f,ns

a_oc

hlof

OC

HL

OF

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

po

rt,

OC

hL

oss

ofF

ram

e

––

–

sa_o

chpf

di,

nsa_

ochp

fdi

OC

HP

FD

IC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,F

orw

ard

Def

ect

Indi

cati

on

––

–

sa_o

chpt

im,

nsa_

ochp

tim

OC

HP

TIM

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

po

rt,

Tra

ceId

enti

fier

Mis

mat

ch

––

–

sa_o

chpp

lm,

nsa_

ochp

plm

OC

HP

PL

MC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,P

aylo

adM

ism

atch

––

–

sa_p

redc

mlo

s,ns

a_pr

edcm

los

PR

ED

CM

LO

SC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,P

reD

CM

Sig

nal

Los

s

––

–

sa_p

ostd

cmlo

s,ns

a_po

stdc

mlo

sP

OS

TD

CM

LO

SC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,P

ost

DC

MS

igna

lL

oss

––

–

sa_l

os,

nsa_

los

LO

SC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,L

oss

ofS

igna

l

sa_s

tmf_

los,

nsa_

stm

f_lo

sS

TM

LO

SC

omm

unic

atio

ns,

rr

port

,S

TM

Los

sof

Sig

nal

sa_l

of,

nsa_

lof

LO

FC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,L

oss

ofF

ram

e

sa_r

df_l

of,

nsa_

rsf_

lof

ST

ML

OF

Com

mun

icat

ions

,r

rpo

rt,

ST

ML

oss

ofF

ram

e

sa_r

stim

,ns

a_rs

tim

RS

TIM

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

po

rt,

Tra

ceId

enti

fier

Mis

mat

ch

sa_r

sf_t

im,

nsa_

rsf_

tim

RS

TIM

Com

mun

icat

ions

,r

rpo

rt,

RS

ect

Tra

ceId

enti

fier

Mis

mat

ch

sa_m

sexc

,ns

a_m

sexc

MS

EX

CC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,E

xces

sive

Bit

Err

orR

atio

sa_m

sf_e

xc,

nsa_

msf

_exc

MS

EX

CC

omm

unic

atio

ns,

rr

port

,M

Sec

tE

xces

sive

Err

or


TDM 10G (STM-64) alarmsTabular overview of LambdaUnite® MSS and WaveStar®


.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


B-3

AS

AP

Typ

eL

amb

daU

nit

e®

MS

SW

aveS

tar®

TD

M10

G(S

TM

-64)

AS

AP

Par

amet

erC

on

dit

ion

Typ

e(p

rob

able

cau

se)

Ala

rmD

escr

ipti

on

AS

AP

Par

amet

erC

on

dit

ion

Typ

e(p

rob

able

cau

se)

Ala

rmD

escr

ipti

on




.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

sa_m

sdeg

,ns

a_m

sdeg

MS

DE

GC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,D

egra

ded

Sig

nal

sa_m

sf_d

eg,

nsa_

msf

_deg

MS

DE

GC

omm

unic

atio

ns,

rr

port

,M

Sec

tS

igna

lD

egra

de

sa_a

isl,

nsa_

aisl

AIS

-LC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,A

larm

Indi

cati

onS

igna

l

sa_m

sf_a

is,

nsa_

msf

_ais

MS

AIS

Com

mun

icat

ions

,r

rpo

rt,

MS

ect

Ala

rmIn

dica

tion

Sig

nal

sa_m

sssf

,ns

a_m

sssf

MS

SS

FC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,S

erve

rS

igna

lF

ail

sa_m

sf_s

sf,

nsa_

msf

_ssf

MS

SS

FC

omm

unic

atio

ns,

rr

port

,M

Sec

tS

erve

rS

igna

lF

ailu

re

sa_m

spss

f,ns

a_m

spss

fM

SP

SS

FC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,P

rot.

Ser

ver

Sig

nal

Fai

l

––

–

sa_r

fil,

nsa_

rfil

RF

I-L

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

po

rt,

Rem

ote

Def

ect

Indi

cati

on

sa_m

sf_r

di,

nsa_

msf

_rdi

MS

RD

IC

omm

unic

atio

ns,

rr

port

,M

Sec

tR

emot

eF

ailu

reIn

dica

tion

nsa_

dccr

sfD

CC

RS

FC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,D

CC

RS

/Sec

tion

fail

ure

sa_d

ccrs

,ns

a_dc

crs

DC

CR

SF

Com

mun

icat

ions

,r

rpo

rt,

DC

CR

Sec

tF

ailu

re

nsa_

lidr

smL

IDR

SM

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

po

rt,

Pro

toco

lV

ersi

onM

ism

atch

sa_l

idrs

mm

,ns

a_li

drsm

mL

IDR

SM

Com

mun

icat

ions

,r

rpo

rt,

Lin

kID

RS

ect

Mis

mat

ch

nsa_

dccm

sfD

CC

MS

FC

omm

unic

atio

n-T

rans

port

,a

idty

pe

port

,D

CC

MS

/Lin

efa

ilur

e

sa_d

ccm

s,ns

a_dc

cms

DC

CM

SF

Com

mun

icat

ions

,r

rpo

rt,

DC

CM

Sec

tF

ailu

re

nsa_

lidm

smL

IDM

SM

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

po

rt,

Pro

toco

lV

ersi

onM

ism

atch

sa_l

idm

smm

,ns

a_li

dmsm

mL

IDM

SM

Com

mun

icat

ions

,r

rpo

rt,

Lin

kID

MS

ect

Mis

mat

ch

PAT

Ha

idty

pe

ison

eof

ST

S1,

ST

S3C

,S

TS

12C

,S

TS

48C

,S

TS

192C

,V

C3,

VC

4,V

C44

C,

VC

416C

,V

C46

4Cr

ris

one

ofV

C3,

VC

4,V

C44

C,

VC

416C

sa_a

is,

nsa_

ais

AIS

-PC

omm

unic

atio

n-T

rans

port

,a

idty

pe

path

,A

larm

Indi

cati

onS

igna

l

sa_a

uf_a

is,

nsa_

auf_

ais

AU

AIS

Com

mun

icat

ions

,r

rC

S,

AU

Ala

rmIn

dica

tion

Sig

nal

sa_l

op,

nsa_

lop

LO

P-P

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

pa

th,

Los

sof

Poi

nter

sa_a

uf_l

op,

nsa_

auf_

lop

AU

LO

PC

omm

unic

atio

nsr

rC

S,

AU

Los

sof

Poi

nter




.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


B-5

sa_s

rm,

nsa_

srm

SR

M-P

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

pa

th,

Sig

nal

Rat

eM

ism

atch

sa_a

uf_s

rm,

nsa_

auf_

srm

AU

SR

MC

omm

unic

atio

ns,

rr

CS

,A

US

igna

lR

ate

Mis

mat

ch




.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

sa_u

neq,

nsa_

uneq

UN

EQ

-PC

omm

unic

atio

n-T

rans

port

,a

idty

pe

path

,U

nequ

ippe

d

sa_h

pf_u

neq,

nsa_

hpf_

uneq

HP

UN

EQ

Com

mun

icat

ions

,r

rC

S,

HP

Une

quip

sa_t

im,

nsa_

tim

TIM

-PC

omm

unic

atio

n-T

rans

port

,a

idty

pe

path

,T

race

Iden

tifi

erM

ism

atch

sa_h

pf_t

im,

nsa_

hpf_

tim

HP

TIM

Com

mun

icat

ions

,r

rC

S,

HP

Tra

ceId

enti

fier

Mis

mat

ch

sa_e

xc,

nsa_

exc

EX

C-P

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

pa

th,

Exc

essi

veB

itE

rror

Rat

io

sa_h

pf_e

xc,

nsa_

hpf_

exc

HP

EX

CC

omm

unic

atio

ns,

rr

CS

,H

PE

xces

sive

Err

or

sa_d

eg,

nsa_

deg

DE

G-P

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

pa

th,

Deg

rade

dS

igna

l

sa_h

pf_d

eg,

nsa_

hpf_

deg

HP

DE

GC

omm

unic

atio

ns,

rr

CS

,H

PS

igna

lD

egra

de

sa_s

sf,

nsa_

ssf

SS

F-P

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

pa

th,

Ser

ver

Sig

nal

Fai

l

sa_r

fi,

nsa_

rfi

RF

I-P

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

pa

th,

Rem

ote

Def

ect

Indi

cati

on

sa_h

pf_r

di,

nsa_

hpf_

rdi

HP

RD

IC

omm

unic

atio

ns,

rr

CS

,H

PR

emot

eD

efec

tIn

dica

tion

sa_p

di,

nsa_

pdi

PD

I-P

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

pa

th,

Pay

load

Def

ect

Indi

cati

on

––

–

PAT

HT

ER

M(P

ath

term

inat

ion)

aid

type

is

one

ofS

TS

1,V

C4

rr

ison

eof

VC

3,V

C4

sa_t

hpss

f,ns

a_th

pssf

TH

PS

SF

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

C

S,

Ser

ver

Sig

nal

Fai

l

hpf_

ssf

HP

SS

FC

omm

unic

atio

ns,

rr

CS

,H

PS

erve

rS

igna

lF

ailu

re

sa_t

hplo

p,ns

a_th

plop

TH

PL

OP

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

C

S,

Los

sof

Poi

nter

hpf_

lop

HP

LO

PC

omm

unic

atio

ns,

rr

CS

,H

PL

oss

ofP

oint

er

sa_t

hpun

eq,

nsa_

thpu

neq

TH

PU

NE

QC

omm

unic

atio

n-T

rans

port

,a

idty

pe

CS

,U

nequ

ippe

dhp

f_un

eqH

PU

NE

QC

omm

unic

atio

ns,

rr

CS

,H

PU

nequ

ip

sa_t

hpti

m,

nsa_

thpt

imT

HP

TIM

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

C

S,

Tra

ceId

enti

fier

Mis

mat

ch

hpf_

tim

HP

TIM

Com

mun

icat

ions

,r

rC

S,

HP

Tra

ceId

enti

fier

Mis

mat

ch

sa_t

hpex

c,ns

a_th

pexc

TH

PE

XC

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

C

S,

Exc

essi

veB

itE

rror

Rat

io

––

–




.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


B-7

sa_t

hpde

g,ns

a_th

pdeg

TH

PD

EG

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

C

S,

Deg

rade

dS

igna

l

hpf_

deg

HP

DE

GC

omm

unic

atio

ns,

rr

CS

,H

PS

igna

lD

egra

de




.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

sa_t

hprd

i,ns

a_th

prdi

TH

PR

DI

Com

mun

icat

ion-

Tra

nspo

rt,

aid

type

C

S,

Rem

ote

Def

ect

Indi

cati

on

hpf_

rdi

HP

RD

IC

omm

unic

atio

ns,

rr

CS

,H

PR

emot

eD

efec

tIn

dica

tion

sa_t

hppl

m,

nsa_

thpp

lmT

HP

PL

MC

omm

unic

atio

n-T

rans

port

,a

idty

pe

CS

,P

aylo

adM

ism

atch

hpf_

plm

HP

PL

MC

omm

unic

atio

ns,

rr

CS

,H

PP

aylo

adL

abel

Mis

mat

ch

sa_v

clom

,ns

a_vc

lom

VC

LO

MC

omm

unic

atio

n-T

rans

port

,a

idty

pe

CS

,L

oss

ofM

ulti

fram

e

hpf_

lom

LO

MC

omm

unic

atio

ns,

rr

CS

,L

oss

ofM

ulti

fram

e

sa_v

csqm

,ns

a_vc

sqm

VC

SQ

MC

omm

unic

atio

n-T

rans

port

,a

idty

pe

CS

,S

eque

nce

Num

ber

Mis

mat

ch

hpf_

sqm

SQ

MC

omm

unic

atio

ns,

rr

CS

,S

eque

nce

Num

ber

Mis

mat

ch

EN

ET

(Eth

erne

t)

sa_v

cg_l

oa,

nsa_

vcg_

loa

VC

GL

OA

Com

mun

icat

ion-

Tra

nspo

rt,

VC

G,

Los

sof

Ali

gnm

ent

sa_l

oa,

nsa_

loa

LO

AC

omm

unic

atio

ns,

VC

G,

Los

sof

Ali

gnm

ent

sa_v

cg_l

opc,

nsa_

vcg_

lopc

VC

GL

OP

CC

omm

unic

atio

n-T

rans

port

,V

CG

,P

arti

alT

rans

port

Cap

acit

yL

oss

sa_l

opc,

nsa_

lopc

CL

OP

CC

omm

unic

atio

ns,

VC

G,

Los

sof

Par

tial

Cap

acit

y

sa_v

cg_l

otc,

nsa_

vcg_

lotc

VC

GL

OT

CC

omm

unic

atio

n-T

rans

port

,V

CG

,T

otal

Tra

nspo

rtC

apac

ity

Los

s

sa_l

otc,

nsa_

lotc

CL

OT

CC

omm

unic

atio

ns,

VC

G,

Los

sof

Tot

alC

apac

ity

sa_v

cg_f

opt,

nsa_

vcg_

fopt

VC

GF

OP

TC

omm

unic

atio

n-T

rans

port

,V

CG

,S

ourc

eE

ndF

ailu

reof

Pro

toco

l

sa_f

opt,

nsa_

fopt

CF

OP

TC

omm

unic

atio

ns,

VC

G,

Fai

lure

ofP

roto

col

Tx

sa_v

cg_f

opr,

nsa_

vcg_

fopr

VC

GF

OP

RC

omm

unic

atio

n-T

rans

port

,V

CG

,S

ink

End

Fai

lure

ofP

roto

col

sa_f

opr,

nsa_

fopr

CF

OP

RC

omm

unic

atio

ns,

VC

G,

Fai

lure

ofP

roto

col

Rx

sa_v

cg_s

sf,

nsa_

vcg_

ssf

VC

GS

SF

Com

mun

icat

ion-

Tra

nspo

rt,

VC

G,

Ser

ver

Sig

nal

Fai

lsa

_vcg

sf,

nsa_

vcgs

fV

CG

SF

Com

mun

icat

ions

,V

CG

,V

CG

Sig

nal

Fai

l

sa_g

fp_l

of,

nsa_

gfp_

lof

GF

PL

OF

Com

mun

icat

ion-

Tra

nspo

rt,

VC

G,

GF

PL

oss

ofF

ram

esa

_gfp

lof,

nsa_

gfpl

ofG

FP

LO

FC

omm

unic

atio

ns,

VC

G,

Los

sof

Fra

me

Del

inea

tion

sa_l

an_l

os,

nsa_

lan_

los

LA

NL

OS

Com

mun

icat

ion-

Tra

nspo

rt,

1GE

,L

AN

Los

sof

Sig

nal

sa_l

anlo

s,ns

a_la

nlos

LO

SC

omm

unic

atio

ns,

Ene

tpo

rt,

Los

sof

Sig

nal




.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


B-9

sa_l

an_a

nm,

nsa_

lan_

anm

LA

NA

NM

Com

mun

icat

ion-

Tra

nspo

rt,

1GE

,L

AN

Aut

oN

egot

iati

onM

ism

atch

sa_l

anan

m,

nsa_

lana

nmA

NM

Com

mun

icat

ions

,E

net

port

,A

uto

Neg

otia

tion

Mis

mat

ch




.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

sa_v

lan_

max

no,

nsa_

vlan

_m

axno

MA

CvL

AN

OV

FW

max

num

ber

ofV

LA

Nin

stan

ces

reac

hed

––

–

SNC

P_U

PSR

psin

hP

SI

Com

mun

icat

ion-

Tra

nspo

rt,

Pat

hpr

otgr

oup,

Pat

hS

wit

chIn

hibi

t

psin

hP

SI

Com

mun

icat

ions

,P

ath

prot

grp,

Pat

hS

wit

chIn

hibi

ted

psfa

ilFA

ILT

OS

WC

omm

unic

atio

n-T

rans

port

,P

ath

prot

grou

p,P

ath

Sw

itch

Den

ial

psfa

ilFA

ILT

OS

WC

omm

unic

atio

ns,

Pat

hpr

otgr

p,P

ath

Sw

itch

Fai

lure

MSS

PR

ING

-BL

SR

inap

sA

PS

CC

omm

unic

atio

n-T

rans

port

,M

SS

PR

ING

-BL

SR

prot

grou

p,In

cons

iste

ntA

PS

Cod

es

blsr

inap

sA

PS

CC

omm

unic

atio

ns,

BL

SR

/MS

-SP

Rin

gpr

otgr

p,In

cons

iste

ntA

PS

Cod

es

imap

sIM

AP

SC

omm

unic

atio

n-T

rans

port

,M

SS

PR

ING

-BL

SR

prot

grou

p,Im

prop

erA

PS

Cod

es

blsr

imap

sA

PS

PR

OV

Com

mun

icat

ions

,B

LS

R/M

S-S

PR

ing

prot

grp,

Impr

oper

AP

SC

odes

nid_

conf

lN

ID-C

ON

FL

Com

mun

icat

ion-

Tra

nspo

rt,

MS

SP

RIN

G-B

LS

Rpr

otgr

oup,

Nod

eID

Mis

mat

ch

nidm

NID

-CO

NF

LC

omm

unic

atio

ns,

BL

SR

/MS

-SP

Rin

gpr

otgr

p,N

ode

IDM

ism

atch

dkb

DK

BC

omm

unic

atio

n-T

rans

port

,M

SS

PR

ING

-BL

SR

prot

grou

p,D

efau

ltK

-byt

es

blsr

dkb

BL

SR

-DK

BC

omm

unic

atio

ns,

BL

SR

/MS

-SP

Rin

gpr

otgr

p,D

efau

ltK

-byt

es

rng_

pss

RN

G-P

SS

Com

mun

icat

ion-

Tra

nspo

rt,

MS

SP

RIN

G-B

LS

Rpr

otgr

oup,

Rin

gP

rote

ctio

nS

wit

chS

uspe

nded

rpss

OV

RD

SW

Com

mun

icat

ions

,B

LS

R/M

S-S

PR

ing

prot

grp,

Rin

gP

rot

Sw

itch

ing

Sus

pend

ed

tsT

SC

omm

unic

atio

n-T

rans

port

,M

SS

PR

ING

-BL

SR

prot

grou

p,T

raff

icS

quel

ched

blsr

tsR

NG

-SQ

UE

LC

HC

omm

unic

atio

ns,

rr

port

,T

raff

icS

quel

ched

dupl

_rng

DU

PL

-RN

GC

omm

unic

atio

n-T

rans

port

,M

SS

PR

ING

-BL

SR

prot

grou

p,D

upli

cate

Rin

gN

ode

dprn

DU

PL

-RN

GC

omm

unic

atio

ns,

BL

SR

/MS

-SP

Rin

gpr

otgr

p,D

upli

cate

Rin

gN

ode




.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


B-11

ropn

RN

G-O

PE

NC

omm

unic

atio

n-T

rans

port

,M

SS

PR

ING

-BL

SR

prot

grou

p,O

pen

Rin

g

ropn

RN

G-O

PE

NC

omm

unic

atio

ns,

BL

SR

/MS

-SP

Rin

gpr

otgr

p,R

ing

Ope

n




.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

sqm

ap_c

onfl

SQ

MA

P-C

ON

FL

Com

mun

icat

ion-

Tra

nspo

rt,

MS

SP

RIN

G-B

LS

Rpr

otgr

oup,

Loc

alS

quel

chM

apC

onfl

ict

rsm

cS

QM

AP

-CO

NF

LC

omm

unic

atio

ns,

BL

SR

/MS

-SP

Rin

gpr

otgr

p,L

ocal

Squ

elch

Map

Con

flic

t

rng_

inc

RN

G-I

NC

Com

mun

icat

ion-

Tra

nspo

rt,

MS

SP

RIN

G-B

LS

Rpr

otgr

oup,

Rin

gIn

com

plet

e

rinc

RN

G-I

NC

Com

mun

icat

ions

,B

LS

R/M

S-S

PR

ing

prot

grp,

Rin

gIn

com

plet

e

rng_

urt

RN

G-U

RT

Com

mun

icat

ion-

Tra

nspo

rt,

MS

SP

RIN

G-B

LS

Rpr

otgr

oup,

Unk

now

nR

ing

Typ

e

urt

RN

G-U

RT

Com

mun

icat

ions

,B

LS

R/M

S-S

PR

ing

prot

grp,

Unk

now

nR

ing

Typ

e

rng_

irpm

RN

G-I

RP

MC

omm

unic

atio

n-T

rans

port

,M

SS

PR

ING

-BL

SR

prot

grou

p,In

cons

iste

ntR

ing

Pro

tect

ion

Mod

e

irpm

RN

G-I

RP

MC

omm

unic

atio

ns,

BL

SR

/MS

-SP

Rin

gpr

otgr

p,In

cons

iste

ntR

ing

Pro

tM

ode

rng_

dscv

yR

NG

-DS

CV

YC

omm

unic

atio

n-T

rans

port

,M

SS

PR

ING

-BL

SR

prot

grou

p,R

ing

Dis

cove

ryin

Pro

gres

s

rdip

RN

G-D

SC

VY

Com

mun

icat

ions

,B

LS

R/M

S-S

PR

ing

prot

grp,

Rin

gD

isco

very

inP

rogr

ess

et_p

reem

ptE

T-P

RE

EM

PT

Com

mun

icat

ion-

Tra

nspo

rt,

MS

SP

RIN

G-B

LS

Rpr

otgr

oup,

Ext

raT

raff

icP

reem

pted

etp

RN

G-P

RE

EM

PT

Com

mun

icat

ions

,B

LS

R/M

S-S

PR

ing

prot

grp,

Ext

raT

raff

icP

reem

pted




.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


B-13



.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Glossary

.................................................................................................................................................................................................................................

Symbols

µMicrons

µmMicrometer

.................................................................................................................................................................................................................................

Numerics

0x1 Line Operation0x1 means unprotected operation. The connection between network elements has onebidirectional line (no protection line).

1+1 Line ProtectionA protection architecture in which the transmitting equipment transmits a valid signal onboth the working and protection lines. The receiving equipment monitors both lines.Based on performance criteria and OS control, the receiving equipment chooses one lineas the active line and designates the other as the standby line.

1xN Equipment Protection1xN protection pertains to N number of circuit pack/port units protected by one circuitpack or port unit. When a protection switch occurs, the working signals are routed fromthe failed pack to the protection pack. When the fault clears, the signals revert to theworking port unit.

12NC (12-digit Numerical Code)Used to uniquely identify an item or product. The first ten digits uniquely identify anitem. The eleventh digit is used to specify the particular variant of an item. The twelfthdigit is used for the revision issue. Items with the first eleven digits the same, arefunctionally equal and may be exchanged.

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-1

.................................................................................................................................................................................................................................

A ABNAbnormal (condition)

ABS (Absent)Used to indicate that a given circuit pack is not installed.

ACAlternating Current

Accessible Emission Limits (AEL)The maximum accessible emission level permitted within a particular laser class (directlyat the aperture).

Acknowledged Information Transfer Service (AITS)The confirmed mode of operation of the LAPD protocol.

ACO (Alarm Cut-Off)A button on the user panel used to silence audible alarms.

ACT (Active)Used to indicate that a circuit pack or module is in-service and currently providingservice functions.

Adaptive-rate tributary operation of a port (Pipe mode)Mode of operation of a port in which tributaries are not explicitely provisioned for theexpected signal rates. The signal rates are automatically identified.

ADM (Add/Drop Multiplexer)The term for a synchronous network element capable of combining signals of differentrates and having those signals added to or dropped from the stream.

AEL→ “Accessible Emission Limits” (p. GL-2)

AgentPerforms operations on managed objects and issues events on behalf of these managedobjects. All SDH managed objects will support at least an agent. Control of distantagents is possible via local “Managers”.

AGNEAlarm Gateway Network Element

AID (Access Identifier)A technical specification for explicitly naming entities (both physical and logical) of anNE using a grammar comprised of ASCII text, keywords, and grammar rules.

AIS (Alarm Indication Signal)

Glossary

.................................................................................................................................................................................................................................

GL-2 Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

A code transmitted downstream in a digital network that indicates that an upstreamfailure has been detected and alarmed if the upstream alarm has not been suppressed.

AITS→ “Acknowledged Information Transfer Service” (p. GL-2)

AlarmVisible or audible signal indicating that an equipment failure or significantevent/condition has occurred.

Alarm CorrelationThe search for a directly-reported alarm that can account for a given symptomaticcondition.

Alarm SeverityAn attribute defining the priority of the alarm message. The way alarms are processeddepends on the severity.

Alarm SuppressionSelective removal of alarm messages from being forwarded to the GUI or to networkmanagement layer OSs.

Alarm ThrottlingA feature that automatically or manually suppresses autonomous messages that are notpriority alarms.

AligningIndicating the head of a virtual container by means of a pointer, for example, creating anAdministrative Unit (AU) or a Tributary Unit (TU).

AMI (Alternate Mark Inversion)A line code that employs a ternary signal to convert binary digits, in which successivebinary ones are represented by signal elements that are normally of alternative positiveand negative polarity but equal in amplitude and in which binary zeros are representedby signal elements that have zero amplitude.

AnomalyA difference between the actual and desired operation of a function.

ANSIAmerican National Standards Institute

APDAvalanche Photo Diode

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-3

APSAutomatic Protection Switching

ASCII (American Standard Code for Information Interchange)A standard 7-bit code that represents letters, numbers, punctuation marks, and specialcharacters in the interchange of data among computing and communications equipment.

ASN.1Abstract Syntax Notation 1

AssemblyGathering together of payload data with overhead and pointer information (an indicationof the direction of the signal).

AssociationA logical connection between manager and agent through which management informationcan be exchanged.

AsynchronousThe essential characteristic of time-scales or signals such that their correspondingsignificant instants do not necessarily occur at the same average rate.

ATM (Asynchronous Transfer Mode)A high-speed transmission technology characterized by high bandwidth and low delay. Itutilizes a packet switching and multiplexing technique which allocates bandwidth ondemand.

AttributeAlarm indication level: critical, major, minor, or no alarm.

AU (Administrative Unit)Carrier for TUs.

AU PTR (Administrative Unit Pointer)Indicates the phase alignment of the VC-N with respect to the STM-N frame. Thepointer position is fixed with respect to the STM-N frame.

AUGAdministrative Unit Group

AUTO (Automatic)One possible state of a port or slot. When a port is in the AUTO state and a good signalis detected, the port automatically enters the IS (in-service) state. When a slot is in theAUTO state and a circuit pack is detected, the slot automatically enters the EQ(equipped) state.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

AutolockAction taken by the system in the event of circuit pack failure/trouble. System switchesto protection and prevents a return to the working circuit pack even if the trouble clears.Multiple protection switches on a circuit pack during a short period of time cause thesystem to autolock the pack.

Autonomous MessageA message transmitted from the controlled Network Element to a management systemwhich was not a response to a command originating from the management system.

.................................................................................................................................................................................................................................

B B3ZS (Bipolar with Three-Zero Substitution)A line code in which bipolar violations are deliberately inserted if user data contain astring of three or more consecutive zeros to ensure a sufficient number of transitions tomaintain system synchronization when the user data stream does not contain a sufficientnumber of transitions.B3ZS is typically used to encode data at 44.736 Mbit/s (T3).HDB3 and B3ZS are different names for the same encoding. HDB3 is typically used toencode data at 2.048 Mbit/s (E1), 8.448 Mbit/s (E2) and 34.368 Mbit/s (E3).

BandwidthThe difference in Hz between the highest and lowest frequencies in a transmissionchannel. The data rate that can be carried by a given communications circuit.

Baud RateTransmission rate of data (bits per second) on a network link.

BCSRBidirectional Circuit-Switched Ring

BCSR_restPABCSR enhanced with restoration of non-affected protection access (extra traffic).

BDIBackward Defect Indication

BER (Bit Error Rate )The ratio of error bits received to the total number of bits transmitted.

Bidirectional LineA transmission path consisting of two fibers that handle traffic in both the transmit andreceive directions.

Bidirectional RingA ring in which both directions of traffic between any two nodes travel through the samenetwork elements (although in opposite directions).

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-5

Bidirectional SwitchProtection switching performed in both the transmit and receive directions.

BIP-N (Bit Interleaved Parity-N)A method of error monitoring over a specified number of bits (BIP-3 or BIP-8).

BitThe smallest unit of information in a computer, with a value of either 0 or 1.

Bit Error Rate ThresholdThe point at which an alarm is issued for bit errors.

BLD OUT LGBuild-Out Lightguide

BLSRBidirectional Line-Switched Ring

Bridge Cross-ConnectionThe setting up of a cross-connection leg with the same input tributary as that of anexisting cross-connection leg. Thus, forming a 1:2 bridge from an input tributary to twooutput tributaries.

Broadband CommunicationsVoice, data, and/or video communications at greater than 2 Mb/s rates.

Broadband Service TransportSTM-1 concatenation transport over the LambdaUnite® MSS for ATM applications.

ByteRefers to a group of eight consecutive binary digits.

.................................................................................................................................................................................................................................

C CContainer

CC (Clear Channel)A digital circuit where no framing or control bits are required, thus making the fullbandwidth available for communications.

CC (Cross-Connection)Path-level connections between input and output tributaries or specific ports within asingle NE. Cross-connections are made in a consistent way even though there arevarious types of ports and various types of port protection. Cross-Connections arereconfigurable interconnections between tributaries of transmission interfaces.

Cell RelayFixed length cells. For example, ATM with 53 octets.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

CEPTConférence Européenne des Administrations des Postes et des Télécommunications

CFRCode of Federal Regulations

ChannelA sub-unit of transmission capacity within a defined higher level of transmissioncapacity.

CircuitA set of transmission channels through one or more network elements that providestransmission of signals between two points, to support a single communications path.

CIT or WaveStar® CIT (Craft Interface Terminal)The user interface terminal used by craft personnel to communicate with a networkelement.

CLClear

CLEICommon Language Equipment Identifier

ClientComputer in a computer network that generally offers a user interface to a server.

CLLICommon Language Location Identifier

Closed Ring NetworkA network formed of a ring-shaped configuration of network elements. Each networkelement connects to two others, one on each side.

CM (Configuration Management)Subsystem that configures the network and processes messages from the network.

CMICoded Mark Inversion

CMIPCommon Management Information Protocol. OSI standard protocol for OAM&Pinformation exchange.

CMISECommon Management Information Service Element

CO (Central Office)A building where common carriers terminate customer circuits.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-7

Co-ResidentA hardware configuration where two applications can be active at the same timeindependently on the same hardware and software platform without interfering with eachothers functioning.

CollocatedSystem elements that are located in the same location.

Command GroupAn administrator-defined group that defines commands to which a user has access.

ConcatenationA procedure whereby multiple virtual containers are associated one with each otherresulting in a combined capacity that can be used as a single container across which bitsequence integrity is maintained.

Core diameter (Mode field diameter)The diameter of the fiber core which is the center of the optical fiber. The transmittedlight is propagated through the core.

CorrelationA process where related hard failure alarms are identified.

CPCircuit Pack

CPECustomer Premises Equipment

CR (Critical (alarm) )Alarm that indicates a severe, service-affecting condition.

CRCCyclical Redundancy Check

Cross-Connect MapConnection map for an SDH Network Element; contains information about how signalsare connected between high speed time slots and low speed tributaries.

CrosstalkAn unwanted signal introduced into one transmission line from another.

CSDClock and synchronisation distribution function

CSMA/CDCarrier Sense Multiple Access with Collision Detection

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

CTIPCustomer Training and Information Products

CTLController

CTSCustomer Technical Support within Lucent Technologies

.................................................................................................................................................................................................................................

D DACS/DCSDigital Access Cross-Connect System

DataA collection of system parameters and their associated values.

Database AdministratorA user who administers the database of the application.

dBDecibels

DCDirect Current

DCC (Data Communications Channel)The embedded overhead communications channel in the synchronous line, used forend-to-end communications and maintenance. The DCC carries alarm, control, and statusinformation between network elements in a synchronous network.

DCE (Data Communications Equipment )The equipment that provides signal conversion and coding between the data terminatingequipment (DTE) and the line. The DCE may be separate equipment or an integral partof the DTE or of intermediate equipment. A DCE may perform other functions usuallyperformed at the network end of the line.

DCFData Communications Function

DCNData Communications Network

DDFDigital Distribution Frame

DefaultAn operation or value that the system or application assumes, unless a user makes anexplicit choice.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-9

Default ProvisioningThe parameter values that are preprogrammed as shipped from the factory.

DefectA limited interruption of the ability of an item to perform a required function. It may ormay not lead to maintenance action depending on the results of additional analysis.

DemultiplexingA process applied to a multiplexed signal for recovering signals combined within it andfor restoring the distinct individual channels of these signals.

DEMUX (Demultiplexer)A device that splits a combined signal into individual signals at the receiver end oftransmission.

DeprovisioningThe inverse order of provisioning. To manually remove/delete a parameter that has (orparameters that have) previously been provisioned.

Digital LinkA transmission span such as a point-to-point 2 Mb/s, 34 Mb/s, 140 Mb/s, VC12, VC3 orVC4 link between controlled network elements. The channels within a digital link areinsignificant.

Digital MultiplexerEquipment that combines by time-division multiplexing several digital signals into asingle composite digital signal.

Digital SectionA transmission span such as an STM-N signal. A digital section may contain multipledigital channels.

DisassemblySplitting up a signal into its constituents as payload data and overhead (an indication ofthe direction of a signal).

DispersionTime-broadening of a transmitted light pulse.

Dispersion Shifted Optical Fiber1330/1550 nm minimum dispersion wavelength.

DivergenceWhen there is unequal amplification of incoming wavelengths, the result is a powerdivergence between wavelengths.

DNI (Dual Node Ring Interworking)A topology in which two rings are interconnected at two nodes on each ring and operate

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

so that inter-ring traffic is not lost in the event of a node or link failure at aninterconnecting point.

DopingThe addition of impurities to a substance in order to attain desired properties.

DownstreamAt or towards the destination of the considered transmission stream, for example,looking in the same direction of transmission.

DPLLDigital Phase Locked Loop

DRAMDynamic Random Access Memory

Drop and ContinueA circuit configuration that provides redundant signal appearances at the outputs of twonetwork elements in a ring. Can be used for Dual Node Ring Interworking (DNI) and forvideo distribution applications.

Drop-Down MenuA menu that is displayed from a menu bar.

DS3Digital Signal - Level 3 (44.736 Mbit/s)

DS3 lineA DS3 line is, acc. to the ANSI T1.231 standard, a a physical transport vehicle thatprovides the means of moving digital information between two points at the nominal rateof 44.736 Mbit/s. A DS3 line is characterized by bipolar 3-zero substitution (B3ZS)coding and transmission on a metallic medium. A DS3 line is normally an intra-officetransport vehicle used to connect DS3 facilities and equipment.Details of DS3 line and path formats can be found in the ANSI T1.102, T1.404, andT1.107 standards.

DS3 pathA DS3 path is, acc. to the ANSI T1.231 standard, a a framed digital signal between twopoints at a nominal rate of 44.736 Mbit/s. A DS3 path is independent of the physicaltransport system(s) over which it is carried. The basic DS3 frame format is called theM-Frame format, described in ANSI T1.107.Details of DS3 line and path formats can be found in the ANSI T1.102, T1.404, andT1.107 standards.

DSNE (Directory Service Network Element)A designated Network Element that is responsible for administering a database that mapsNetwork Elements names (node names) to addresses (node Id). There can be one DSNEper (sub)network.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-11

DTE (Data Terminating Equipment)The equipment that originates data for transmission and accepts transmitted data.

DTMFDual Tone Multifrequency

DUSDo not Use for Synchronization

DWDM (Dense Wavelength Division Multiplexing)Transmitting two or more signals of different wavelengths simultaneously over a singlefiber.

.................................................................................................................................................................................................................................

E EBER (Excessive Bit Error Ratio)The calculated average bit error ratio over a data stream.

ECCEmbedded Control Channel

EEPROMElectrically Erasable Programmable Read-Only Memory

EIA (Electronic Industries Association)A trade association of the electronic industry that establishes electrical and functionalstandards.

EMEvent Management

EMC (Electromagnetic Compatibility)A measure of equipment tolerance to external electromagnetic fields.

EMI (Electromagnetic Interference)High-energy, electrically induced magnetic fields that cause data corruption in cablespassing through the fields.

EMP (Equipment Management Protocol)The Equipment Management Protocol (EMP) is used for basic equipment managementpurposes, such as equipage supervision, reset and recovery control and softwaredownload.

EMSElement Management System

EntityA specific piece of hardware (usually a circuit pack, slot, or module) that has beenassigned a name recognized by the system.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Entity IdentifierThe name used by the system to refer to a circuit pack, memory device, orcommunications link.

EoS (Ethernet over SDH)Generic name for the mapping of MAC frames (Ethernet frames) into SDH standard orvirtually concatenated VC-n. It involves encapsulation, framing, scrambling, mappingand management of VC-n-Xv.

EPROMErasable Programmable Read-Only Memory

EQ (Equipped)Status of a circuit pack or interface module that is in the system database and physicallyin the frame, but not yet provisioned.

ES (Errored Seconds)A performance monitoring parameter. ES “type A” is a second with exactly one error;ES “type B” is a second with more than one and less than the number of errors in aseverely errored second for the given signal. ES by itself means the sum of the type Aand type B ESs.

ESDElectrostatic Discharge

ESPElectrostatic Protection

EstablishA user initiated command, at the WaveStar® CIT, to create an entity and its associatedattributes in the absence of certain hardware.

ETSIEuropean Telecommunications Standards Institute

EventA significant change. Events in controlled Network Elements include signal failures,equipment failures, signals exceeding thresholds, and protection switch activity. When anevent occurs in a controlled Network Element, the controlled Network Element willgenerate an alarm or status message and send it to the management system.

Event DrivenA required characteristic of network element software system: NEs are reactive systems,primarily viewed as systems that wait for and then handle events. Events are providedby the external interface packages, the hardware resource packages, and also by thesoftware itself.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-13

Externally TimedAn operating condition of a clock in which it is locked to an external reference and isusing time constants that are altered to quickly bring the local oscillator’s frequency intoapproximate agreement with the synchronization reference frequency.

Extra trafficUnprotected traffic that is carried over protection channels when their capacity is notused for the protection of working traffic.

.................................................................................................................................................................................................................................

F FaultTerm used when a circuit pack has a hard (not temporary) fault and cannot perform itsnormal function.

Fault ManagementCollecting, processing, and forwarding of autonomous messages from network elements.

FCCFederal Communications Commission

FDA/CDRHThe Food and Drug Administration′s Center for Devices and Radiological Health.

FDDI (Fiber Distributed Data Interface)Fiber interface that connects computers and distributes data among them.

FE (Far End )Any other network element in a maintenance subnetwork other than the one the user isat or working on. Also called remote.

FEACFar-End Alarm & Control

FEBE (Far-End Block Error)An indication returned to the transmitting node that an errored block has been detectedat the receiving node. A block is a specified grouping of bits.

FEPROM (Flash EPROM)A technology that combines the nonvolatility of EPROM with the in-circuitreprogrammability of EEPROM (electrically-erasable PROM).

FERF (Far-End Receive Failure)An indication returned to a transmitting Network Element that the receiving NetworkElement has detected an incoming section failure. Also known as RDI.

FIT (Failures in Time)Circuit pack failure rates per 109 hours as calculated using the method described inReliability Prediction Procedure for Electronic Equipment, BellCore Method I, Issue 5,

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

September 1995.

Fixed-rate tributary operation of a portMode of operation of a port in which tributaries are provisioned for the expected signalrates. This provisioning information is used for crossconnection rate validation and foralarm handling (for example “Loss of Pointer”).

Folded RingsFolded (collapsed) rings are rings without fiber diversity. The terminology derives fromthe image of folding a ring into a linear segment.

ForcedTerm used when a circuit pack (either working or protection) has been locked into aservice-providing state by user command.

FR (Frame Relay)A form of packet switching that relies on high-quality phone lines to minimize errors. Itis very good at handling high-speed, bursty data over wide area networks. The framesare variable lengths and error checking is done at the end points.

FrameThe smallest block of digital data being transmitted.

FrameworkAn assembly of equipment units capable of housing shelves, such as a bay framework.

Free RunningAn operating condition of a clock in which its local oscillator is not locked to aninternal synchronization reference and is using no storage techniques to sustain itsaccuracy.

.................................................................................................................................................................................................................................

G GBGigabytes

Gbit/sGigabits per second

GHzGigahertz

Global Wait to Restore TimeCorresponds to the time to wait before switching back to the timing reference. It occursafter a timing link failure has cleared. This time applies for all timing sources in asystem hence the name global. This can be between 0 and 60 minutes, in increments ofone minute.

GNE (Gateway Network Element)

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-15

A network element that passes information between other network elements andmanagement systems through a data communication network.

.................................................................................................................................................................................................................................

H Hard FailureAn unrecoverable nonsymptomatic (primary) failure that causes signal impairment orinterferes with critical network functions, such as DCC operation.

HDB3 (High Density Bipolar 3 Code)Line code for 2 Mb/s transmission systems.

HDLC (High Level Data Link Control)OSI reference model datalink layer protocol.

HMIHuman Machine Interface

HML (Human Machine Language)A standard language developed by the ITU for describing the interaction betweenhumans and dumb terminals.

HOHigh Order

HoldoverAn operating condition of a clock in which its local oscillator is not locked to anexternal reference but is using storage techniques to maintain its accuracy with respectto the last known frequency comparison with a synchronization reference.

Hot StandbyA circuit pack ready for fast, automatic placement into operation to replace an activecircuit pack. It has the same signal as the service going through it, so that choice is allthat is required.

HPA (Higher Order Path Adaptation)Function that adapts a lower order Virtual Container to a higher order Virtual Containerby processing the Tributary Unit pointer which indicates the phase of the lower orderVirtual Container Path Overhead relative to the higher order Virtual Container PathOverhead and assembling/disassembling the complete higher order Virtual Container.

HPC (Higher Order Path Connection)Function that provides for flexible assignment of higher order Virtual Containers withinan STM-N signal.

HPT (Higher Order Path Termination)Function that terminates a higher order path by generating and adding the appropriateVirtual Container Path Overhead to the relevant container at the path source andremoving the Virtual Container Path Overhead and reading it at the path sink.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

HSHigh Speed

HWHardware

HzHertz

.................................................................................................................................................................................................................................

I I/OInput/Output

IAO LANIntraoffice Local Area Network

IDIdentifier

IDE→ “Integrated Device (or Drive) Electronics ” (p. GL-17)

IECInternational Electro-Technical Commission

IEEEInstitute of Electrical and Electronics Engineers

IMFInfant Mortality Factor

InsertTo physically insert a circuit pack into a slot, thus causing a system initiated restoral ofan entity into service and/or creation of an entity and associated attributes.

Integrated Device (or Drive) Electronics (IDE)A hard-drive interface which has all of its controller electronics integrated into the driveitself.

Interface CapacityThe total number of STM-1 equivalents (bidirectional) tributaries in all transmissioninterfaces with which a given transmission interface shelf can be equipped at one time.The interface capacity varies with equipage.

Intermediate System (IS)A system which routes/relays management information. An SDH Network Element maybe a combined intermediate and end system.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-17

IPCInter Processor Communications

IS (In-Service)A memory administrative state for ports. IS refers to a port that is fully monitored andalarmed.

IS-IS RoutingThe Network Elements in a management network, route packets (data) between eachother using an IS-IS level protocol. The size of a network running IS-IS Level 1 islimited, and therefore certain mechanisms are employed to facilitate the management oflarger networks.For STATIC ROUTING, the capability exists for disabling the protocol over the LANconnections, effectively causing the management network to be partitioned into separateIS-IS Level 1 areas. In order for the network management system to communicate with aspecific Network Element in one of these areas, the network management system mustidentify through which so-called Gateway Network Element this specific NetworkElement is connected to the LAN. All packets to this specific Network Element arerouted directly to the Gateway Network Element by the network management system,before being re-routed (if necessary) within the Level 1 area.For DYNAMIC ROUTING an IS-IS Level 2 routing protocol is used allowing a numberof Level 1 areas to interwork. The Network Elements which connect an IS-IS area toanother area are set to run the IS-IS Level 2 protocol within the Network Element andon the connection between other Network Elements. Packets can now be routed betweenIS-IS areas and the network management system does not have to identify the GatewayNetwork Elements.

ISDNIntegrated Services Digital Network

ITMIntegrated Transport Management

ITM-NMIntegrated Transport Management Network Module

ITUInternational Telecommunications Union

ITU-TInternational Telecommunications Union — Telecommunication standardization sector.Formerly known as CCITT: Comité Consultatif International Télégrafique &Téléphonique; International Telegraph and Telephone Consultative Committee.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

.................................................................................................................................................................................................................................

J JitterShort term variations of amplitude and frequency components of a digital signal fromtheir ideal position in time.

.................................................................................................................................................................................................................................

K Kbit/sKilobits per second

.................................................................................................................................................................................................................................

L LAN (Local Area Network)A communications network that covers a limited geographic area, is privately owned anduser administered, is mostly used for internal transfer of information within a business,is normally contained within a single building or adjacent group of buildings, andtransmits data at a very rapid speed.

LAPD (Link Access Procedure in the D channel)Protocol used on the data link layer (OSI layer two) according to the ITU-T Rec. Q.921.

LBCLaser Bias Current

LBFCLaser Backface Currents

LBO (Lightguide Build-Out )An attenuating (signal-reducing) element used to keep an optical output signal strengthwithin desired limits.

LCAS (Link Capacity Adjustment Scheme)The Link Capacity Adjustment Scheme is a protocol that allows to dynamically changethe number of payload carrying VC-n’s in a Virtual Concatenation Group (VCG). Undermanagement control a VC-n can in-service be added to or deleted from a VCG.Furthermore, VC-n’s for which a Trail Signal Fail (TSF) condition is present can beremoved autonomously from the VCG and added to the group again as soon as the TSFcondition is no longer present.

LCNLocal Communications Network

LEDLight-Emitting Diode

LHLong Haul

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-19

LineA transmission medium, together with the associated equipment, required to provide themeans of transporting information between two consecutive network elements. Onenetwork element originates the line signal; the other terminates it.

Line ProtectionThe optical interfaces can be protected by line protection. Line protection switchingprotects against failures of line facilities, including the interfaces at both ends of a line,the optical fibers, and any equipment between the two ends. Line protection includesprotection of equipment failures.

Line TimingRefers to a network element that derives its timing from an incoming STM-N signal.

LinkThe mapping between in-ports and out-ports. It specifies how components are connectedto one another.

Lockout of ProtectionThe WaveStar® CIT command that prevents the system from switching traffic to theprotection line from a working line. If the protection line is active when a “Lockout ofProtection” is entered – this command causes the working line to be selected. Theprotection line is then locked from any Automatic, Manual, or Forced protectionswitches.

Lockout StateThe Lockout State shall be defined for each working or protection circuit pack. The twopermitted states are: None – meaning no lockout is set for the circuit pack, set meaningthe circuit pack has been locked out. The values (None & Set) shall be takenindependently for each working or protection circuit pack.

LOFLoss of Frame

LOHLine Overhead

LOMLoss of Multiframe

Loop TimingA special case of line timing. It applies to network elements that have only oneOC-N/STM-N interface. For example, terminating nodes in a linear network are looptimed.

LoopbackType of diagnostic test used to compare an original transmitted signal with the resultingreceived signal. A loopback is established when the received optical or electrical external

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

transmission signal is sent from a port or tributary input directly back toward the output.

LOPLoss of Pointer

LOSLoss of Signal

Loss BudgetLoss (in dB) of optical power due to the span transmission medium (includes fiber lossand splice losses).

LPA (Lower order Path Adaptation)Function that adapts a PDH signal to a synchronous network by mapping the signal intoor de-mapping the signal out of a synchronous container.

LPC (Lower Order Path Connection )Function that provides for flexible assignment of lower order VCs in a higher order VC.

LPT (Lower Order Path Termination)Function that terminates a lower order path by generating and adding the appropriate VCPOH to the relevant container at the path source and removing the VC POH and readingit at the path sink.

LSLow Speed

LSP

1. Link State Protocol

2. Label-switched path

LTELine Terminating Equipment

.................................................................................................................................................................................................................................

M MACMedia Access Control

MAFManagement Application Function

Maintenance ConditionAn equipment state in which some normal service functions are suspended, eitherbecause of a problem or to perform special functions (copy memory) that can not beperformed while normal service is being provided.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-21

Management ConnectionIdentifies the type of routing used (STATIC or DYNAMIC), and if STATIC is selectedallows the gateway network element to be identified.

ManagerCapable of issuing network management operations and receiving events. The managercommunicates with the agent in the controlled network element.

Manual Switch StateA protection group shall enter the Manual Switch State upon the initiation and successfulcompletion of the Manual Switch command. The protection group leaves the ManualSwitch state by means of the Clear or Forced Switch commands. While in the ManualSwitch state the system may switch the active unit automatically if required forprotection switching.

MappingThe logical association of one set of values, such as addresses on one network, withquantities or values of another set, such as devices or addresses on another network.

MBMegabytes

Mbit/sMegabits per second

MCF (Message Communications Function)Function that provides facilities for the transport and routing of TelecommunicationsManagement Network messages to and from the Network Manager.

MD (Mediation Device)Allows for exchange of management information between Operations System andNetwork Elements.

MDIMiscellaneous Discrete Input

MDOMiscellaneous Discrete Output

MEC (Manufacturer Executable Code)Network Element system software in binary format that after being downloaded to oneof the stores can be executed by the system controller of the network element.

MEMMemory

MFASMultiframe Alignment Signal

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Mid-Span MeetThe capability to interface between two lightwave network elements of different vendors.This applies to high-speed optical interfaces.

Miscellaneous Discrete InterfaceAllows an operations system to control and monitor equipment collocated within a set ofinput and output contact closures.

MJ (Major (alarm))Indicates a service-affecting failure, main or unit controller failure, or power supplyfailure.

MMIMan-Machine Interface

MMLHuman-Machine Language

MN (Minor (alarm))Indicates a non-service-affecting failure of equipment or facility.

MOManaged Object

Mode field diameter (Core diameter)

MPLSMulti Protocol Label Switching

MSMultiplex Section

msMillisecond

MS-SPRING (Multiplex Section Shared Protection Ring)A protection method used in Add-Drop Multiplexer Network Elements.

MSOHMultiplex Section Overhead

MSP (Multiplex Section Protection)Provides capability for switching a signal from a working to a protection section.

MST (Multiplex Section Termination)Function that generates the Multiplexer Section OverHead in the transmit direction andterminates the part of the Multiplexer Section overhead that is acceptable in the receivedirection.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-23

MTBF (Mean Time Between Failures)The expected time between failures, usually expressed in hours.

MTBMAMean Time Between Maintenance Activities

MTIEMaximum Time Interval Error

MTPIMultiplexer Timing Physical Interface

MTS (Multiplexer Timing Source)Function that provides timing reference to the relevant component parts of the multiplexequipment and represents the SDH Network Element clock.

MTTRMean Time To Repair

MultiplexerA device (circuit pack) that combines two or more transmission signals into a combinedsignal on a shared medium.

MultiplexingA procedure by which multiple lower order path layer signals are adapted into a higherorder path, or the multiple higher order path layer signals are adapted into a multiplexsection.

.................................................................................................................................................................................................................................

N NANot Applicable

NE (Network Element)A node in a telecommunication network that supports network transport services and isdirectly manageable by a management system.

NEBSNetwork Equipment-Building System

nmNanometer (10–9 meters)

NMON (Not Monitored )A provisioning state for equipment that is not monitored or alarmed.

NMSNetwork Management System

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

No Request StateThis is the routine-operation quiet state in which no external command activities areoccurring.

NodeA network element in a ring or, more generally, in any type of network. In a networkelement supporting interfaces to more than one ring, node refers to an interface that is ina particular ring. Node is also defined as all equipment that is controlled by one systemcontroller. A node is not always directly manageable by a management system.

Non-Revertive SwitchingIn non-revertive switching, an active and stand-by line exist on the network. When aprotection switch occurs, the standby line is selected to support traffic, thereby becomingthe active line. The original active line then becomes the stand-by line. This statusremains in effect even when the fault clears. That is, there is no automatic switch backto the original status.

Non-SynchronousThe essential characteristic of time-scales or signals such that their correspondingsignificant instants do not necessarily occur at the same average rate.

NPINull Pointer Indication

NPPA (Non-Preemptible Protection Access)Non-preemptible protection access increases the available span capacity for traffic whichdoes not require protection by a ring, but which cannot be preempted.

NRZNonreturn to Zero

NSANot service-affecting

NSAP Address (Network Service Access Point Address)Network Service Access Point Address (used in the OSI network layer 3). Anautomatically assigned number that uniquely identifies a Network Element for thepurposes of routing DCC messages.

NVM (Non-Volatile Memory )Memory that retains its stored data after power has been removed. An example of NVMwould be a hard disk.

.................................................................................................................................................................................................................................

O O&MOperation and Maintenance

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-25

OAOptical amplifier

OAM&POperations, Administration, Maintenance, and Provisioning

OBAOptical booster amplifier

OC, OC-nOptical Carrier

OC-12Optical Carrier, Level 12 Signal (622.08 Mbit/s)

OC-192Optical Carrier, Level 192 (9953.28 Mb/s) (10 Gbit/s)

OC-3Optical Carrier, Level 3 Signal (155 Mbit/s)

OC-48Optical Carrier, Level 48 (2488.32 Mb/s) (2.5 Gbit/s)

ODUk (Optical Channel Data Unit – k)According to the ITU-T Rec. G.709/Y.1331 (03/2003), the ODUk is an informationstructure consisting of the information payload (OPUk, Optical Channel Payload Unit)and ODUk related overhead.

ODUk capacities are defined for k = 1, 2, or 3 where k indicates the bit rate of theclient signal:

1. 2.5 Gbit/s

2. 10 Gbit/s

3. 40 Gbit/s

OI (Operations Interworking)The capability to access, operate, provision, and administer remote systems through craftinterface access from any site in a SDH network or from a centralized operationssystem.

OLSOptical Line System

ONI (Operations Network Interface)The Operations Network Interface is used to transport management information betweencircuit packs.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

OOFOut-of-Frame

OOS (Out-of-Service)The circuit pack is not providing its normal service function (removed from either theworking or protection state) either because of a system problem or because the pack hasbeen removed from service.

OPAOptical pre-amplifier

Open Ring NetworkA network formed of a linear chain-shaped configuration of network elements. Eachnetwork element connects to two others, one on each side, except for two networkelements at the ends which are connected on only one side. A closed ring can be formedby adding a connection between the two end nodes.

Operations InterfaceAny interface providing you with information on the system behaviour or control. Theseinclude the equipment LEDs, user panel, WaveStar® CIT, office alarms, and all telemetryinterfaces.

OperatorA user of the system with operator-level user privileges.

Optical Line SignalA multiplexed optical signal containing multiple wavelengths or channels.

OPUk (Optical Channel Payload Unit – k)According to the ITU-T Rec. G.709/Y.1331 (03/2003), the OPUk is the informationstructure used to adapt client information for the transport over an optical channel. Itcomprises client information together with any overhead needed to perform rateadaptation between the client signal rate and the OPUk payload rate and other OPUkoverhead supporting the client signal transport. This overhead is adaptation specific.

OPUk capacities are defined for k = 1, 2, or 3 where k indicates the bit rate of theclient signal:

1. 2.5 Gbit/s

2. 10 Gbit/s

3. 40 Gbit/s

Original Value ProvisioningPreprogramming of a system’s original values at the factory. These values can beoverridden using local or remote provisioning.

OS (Operations System)A central computer-based system used to provide operations, administration, and

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-27

maintenance functions.

OSI (Open Systems Interconnection )Referring to the OSI reference model, a logical structure for network operationsstandardized by the International Standards Organization (ISO).

OTNOptical Transport Network

OTUk (Optical Channel Transport Unit – k)According to the ITU-T Rec. G.709/Y.1331 (03/2003), the OTUk is the informationstructure used for the transport of an ODUk over one or more optical channelconnections. It consists of the optical channel data unit and OTUk related overhead(FEC and overhead for management of an optical channel connection). It is characterizedby its frame structure, bit rate, and bandwidth.

OTUk capacities are defined for k = 1, 2, or 3 where k indicates the bit rate of theclient signal:

1. 2.5 Gbit/s

2. 10 Gbit/s

3. 40 Gbit/s

OutageA disruption of service that lasts for more than 1 second.

OW (Orderwire)A dedicated voice-grade line for communications between maintenance and repairpersonnel.

.................................................................................................................................................................................................................................

P ParameterA variable that is given a value for a specified application. A constant, variable, orexpression that is used to pass values between components.

Parity CheckTests whether the number of ones (or zeros) in an array of binary bits is odd or even;used to determine that the received signal is the same as the transmitted signal.

Pass-ThroughPaths that are cross-connected directly across an intermediate node in a network.

PathA logical connection between the point at which a standard frame format for the signalat the given rate is assembled, and the point at which the standard frame format for thesignal is disassembled.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Path Terminating EquipmentNetwork elements in which the path overhead is terminated.

PCBPrinted Circuit Board

PCMPulse Code Modulation

PCMCIAPersonal Computer Memory Card International Association

PDHPlesiochronous Digital Hierarchy

PIPhysical Interface

Pipe mode (Adaptive-rate tributary operation of a port)Mode of operation of a port in which tributaries are not explicitely provisioned for theexpected signal rates. The signal rates are automatically identified.

PlatformA family of equipment and software configurations designed to support a particularapplication.

Plesiochronous NetworkA network that contains multiple subnetworks, each internally synchronous and alloperating at the same nominal frequency, but whose timing may be slightly different atany particular instant.

PM (Performance Monitoring)Measures the quality of service and identifies degrading or marginally operating systems(before an alarm would be generated).

PMD (Polarization Mode Dispersion)Output pulse broadening due to random coupling of the two polarization modes in anoptical fiber.

POH (Path Overhead)Informational bytes assigned to, and transported with the payload until the payload isdemultiplexed. It provides for integrity of communication between the point of assemblyof a virtual container and its point of disassembly.

PointerAn indicator whose value defines the frame offset of a virtual container with respect tothe frame reference of the transport entity on which it is supported.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-29

POPPoint of Presence

Port (also called Line)The physical interface, consisting of both an input and output, where an electrical oroptical transmission interface is connected to the system and may be used to carry trafficbetween network elements. The words “port” and “line” may often be usedsynonymously. “Port” emphasizes the physical interface, and “line” emphasizes theinterconnection. Either may be used to identify the signal being carried.

Port State ProvisioningA feature that allows a user to suppress alarm reporting and performance monitoringduring provisioning by supporting multiple states (automatic, in-service, and notmonitored) for low-speed ports.

POTSPlain Old Telephone Service

PPPointer Processing

PRC (Primary Reference Clock)The main timing clock reference in SDH equipment.

PreprovisioningThe process by which the user specifies parameter values for an entity in advance ofsome of the equipment being present. These parameters are maintained only in NVM.These modifications are initiated locally or remotely by either a CIT or an OS.Preprovisioning provides for the decoupling of manual intervention tasks (for example,install circuit packs) from those tasks associated with configuring the node to provideservices (for example, specifying the entities to be cross-connected).

PRIPrimary

Proactive MaintenanceRefers to the process of detecting degrading conditions not severe enough to initiateprotection switching or alarming, but indicative of an impending signal fail or signaldegrade defect.

Protection AccessTo provision traffic to be carried by protection tributaries when the port tributaries arenot being used to carry the protected working traffic.

Protection Group ConfigurationThe members of a group and their roles, for example, working protection, line number,etc.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Protection PathOne of two signals entering a path selector used for path protection switching or dualring interworking. The other is the working path. The designations working andprotection are provisioned by the user, whereas the terms active path and standby pathindicate the current protection state.

Protection StateWhen the working unit is currently considered active by the system and that it iscarrying traffic. The “active unit state” specifically refers to the receive direction ofoperation — since protection switching is unidirectional.

PROTN (Protection)Extra capacity (channels, circuit packs) in transmission equipment that is not intended tobe used for service, but rather to serve as backup against equipment failures.

PROV (Provisioned)Indicating that a circuit pack is ready to perform its intended function. A provisionedcircuit pack can be active (ACT), in-service (IS), standby (STBY), provisionedout-of-service (POS), or out-of-service (OOS).

PRS (Primary Reference Source)According to the Telcordia GR-1244-CORE and ANSI T1.101 standards, a PrimaryReference Source provides the basic reference signal for the timing or synchronization ofother clocks within a network. The long term accuracy of the timing signal is maintainedat 1×10-11 or better with verification to coordinated universal time (UTC). ForLambdaUnite® MSS systems, PRS is synonymous with Stratum-1 (ST-1).

PSDNPublic Switched Data Network

PSTNPublic Switched Telephone Network

PTEPath Terminating Equipment

PWRPower

PWR ONPower On

.................................................................................................................................................................................................................................

Q Q-LANThin Ethernet LAN which connects the manager to Gateway Network Elements so thatmanagement information between Network Elements and management systems can beexchanged.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-31

QL (Quality Level)The quality of the timing signal(s) provided to clock a Network Element. The level isprovided by the Synchronization Status Marker which can accompany the timing signal.If the System and Output Timing Quality Level mode is “Enabled”, and if the signalselected for the Station Clock Output has a quality level below the Acceptance QualityLevel, the Network Element “squelches” the Station Clock Output Signal, which meansthat no signal is forwarded at all.

Possible levels are:

• PRC (Primary Reference Clock)

• SSU_T (Synchronization Supply Unit - Transit)

• SSU_L (Synchronization Supply Unit - Local)

• SEC (SDH Equipment Clock)

• DUS (Do not Use for Synchronization)

QOSQuality of Service

.................................................................................................................................................................................................................................

R RAMRandom Access Memory

RDI (Remote Defect Indication)An indication returned to a transmitting terminal that the receiving terminal has detectedan incoming section failure. [Previously called far-end-receive failure (FERF).]

Reactive MaintenanceRefers to detecting defects/failures and clearing them.

Receive-DirectionThe direction towards the Network Element.

RegenerationThe process of reconstructing a digital signal to eliminate the effects of noise anddistortion.

Regenerator LoopLoop in a Network Element between the Station Clock Output(s) and one or both StationClock Inputs, which can be used to dejitterize the selected timing reference in networkapplications.

Regenerator Section Termination (RST)Function that generates the Regenerator Section Overhead (RSOH) in the transmitdirection and terminates the RSOH in the receive direction.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

ReliabilityThe ability of a software system performing its required functions under statedconditions for a stated period of time. The probability for an equipment to fulfill itsfunction. Some of the ways in which reliability is measured are: MTBF (Mean TimeBetween Failures) expressed in hours; Availability = (MTBF)/(MTBF+MTTR)(%) [whereMTTR = mean time to restore]; outage in minutes per year; failures per hour; percentageof failures per 1,000 hours.

Remote Network ElementAny Network Element that is connected to the referenced Network Element througheither an electrical or optical link. It may be the adjacent node on a ring, or N nodesaway from the reference. It also may be at the same physical location but is usually atanother (remote) site.

Restore TimerCounts down the time (in minutes) during which the switch waits to let the worker linerecover before switching back to it. This option can be set to prevent the protectionswitch continually switching if a line has a continual transient fault. This field is grayedout if the mode is non-revertive.

RevertiveA protection switching mode in which, after a protection switch occurs, the equipmentreturns to the nominal configuration (that is, the working equipment is active, and theprotection equipment is standby) after any failure conditions that caused a protectionswitch to occur, clear, or after any external switch commands are reset. (See“Non-Revertive”.)

Revertive SwitchingIn revertive switching, there is a working and protection high-speed line, circuit pack,etc. When a protection switch occurs, the protection line, circuit pack, etc. is selected.When the fault clears, service “reverts” to the working line.

RingA configuration of nodes comprised of network elements connected in a circular fashion.Under normal conditions, each node is interconnected with its neighbor and includescapacity for transmission in either direction between adjacent nodes. Path switched ringsuse a head-end bridge and tail-end switch. Line switched rings actively reroute trafficover the protection capacity.

RouteA series of contiguous digital sections.

RouterAn interface between two networks. While routers are like bridges, they workdifferently. Routers provide more functionality than bridges. For example, they can findthe best route between any two networks, even if there are several different networks inbetween. Routers also provide network management capabilities such as load balancing,

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-33

partitioning of the network, and trouble-shooting.

RSOHRegenerator Section OverHead; part of SOH

RSTRegenerator Section Termination

RTRemote Terminal

RTRVRetrieve

RZ (Return to Zero)A code form having two information states (termed zero and one) and having a thirdstate or an at-rest condition to which the signal returns during each period.

.................................................................................................................................................................................................................................

S SAService-affecting

SASection Adaptation

SCNSignalling Communication Network

SDSignal Degrade

SDH (Synchronous Digital Hierarchy)A hierarchical set of digital transport structures, standardized for the transport of suitableadapted payloads over transmission networks.

SDSStandard Directory Service based on ANSI recommendation T1.245

SECSecondary

SECSDH Equipment Clock

SectionThe portion of a transmission facility, including terminating points, between a terminalnetwork element and a line-terminating network element, or two line-terminatingnetwork elements.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Section AdaptationFunction that processes the AU-pointer to indicate the phase of the VC-3/4 POH relativeto the STM-N SOH and assembles/disassembles the complete STM-N frame.

Self-HealingA network’s ability to automatically recover from the failure of one or more of itscomponents.

SEMF (Synchronous Equipment Management Function)Function that converts performance data and implementation specific hardware alarmsinto object-oriented messages for transmission over the DCC and/or Q-interface. It alsoconverts object-oriented messages related to other management functions for passingacross the S reference points.

ServerComputer in a computer network that performs dedicated main tasks which generallyrequire sufficient performance.

ServiceThe operational mode of a physical entity that indicates that the entity is providingservice. This designation will change with each switch action.

SES (Severely Errored Seconds)This performance monitoring parameter is a second in which a signal failure occurs, ormore than a preset amount of coding violations (dependent on the type of signal) occurs.

SHShort Haul

Single-Ended OperationsProvides operations support from a single location to remote Network Elements in thesame SDH subnetwork. With this capability you can perform operations, administration,maintenance, and provisioning on a centralized basis. The remote Network Elements canbe those that are specified for the current release.

Site AddressThe unique address for a Network Element.

SlotA physical position in a shelf designed for holding a circuit pack and connecting it tothe backplane. This term is also used loosely to refer to the collection of ports ortributaries connected to a physical circuit pack placed in a slot.

SM (Single-Mode Fiber)A low-loss, long-span optical fiber typically operating at either 1310 nm, 1550 nm, orboth.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-35

SMNSDH Management Network

SNC/ISubNetwork Connection (protection) / Inherent monitoring

SNC/NSubNetwork Connection (protection) / Non-Intrusive Monitoring

SNR (Signal-to-Noise Ratio)The relative strength of signal compared to noise.

Software BackupThe process of saving an image of the current network element’s databases, which arecontained in its NVM, to a remote location. The remote location could be theWaveStar™ CIT or an OS.

Software DownloadThe process of transferring a generic (full or partial) or provisioned database from aremote entity to the target network element’s memory. The remote entity may be theWaveStar™ CIT or an OS. The download procedure uses bulk transfer to move anuninterpreted binary file into the network element.

Software IDNumber that provides the software version information for the system.

SOH (Section Overhead)Capacity added to either an AU-4 or assembly of AU-3s to create an STM-1. Containsalways STM-1 framing and optionally maintenance and operational functions. SOH canbe subdivided in MSOH (multiplex section overhead) and RSOH (regenerator sectionoverhead).

SONET (Synchronous Optical Network)The North American standard for the rates and formats that defines optical signals andtheir constituents.

SpanAn uninterrupted bidirectional fiber section between two network elements.

Span GrowthA type of growth in which one wavelength is added to all lines before the nextwavelength is added.

SPESynchronous Payload Envelope

SPISDH Physical Interface

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Squelch MapThis map contains information for each cross-connection in a ring and indicates thesource and destination nodes for the low-speed circuit that is part of thecross-connection. This information is used to prevent traffic misconnection in rings withisolated nodes or segments.

SSMSynchronization Status Message

SSU_LSynchronization Supply Unit — Local Node

SSU_TSynchronization Supply Unit — Transit Node

Standby PathOne of two signals entering a constituent path selector, the standby path is the path notcurrently being selected.

StateThe state of a circuit pack indicates whether it is defective or normal (ready for normaluse).

Station Clock InputAn external clock may be connected to a Station Clock Input.

StatusThe indication of a short-term change in the system.

STBY (Standby)The circuit pack is in service but is not providing service functions. It is ready to beused to replace a similar circuit pack either by protection or by duplex switching.

STMSynchronous Transport Module (SDH)

STM-N (Synchronous Transport Module, Level N)A building block information structure that supports SDH section layer connections,where N represents a multiple of 155.52 Mb/s. Normally N=1, 4, 16, or 64.

STSSynchronous Transport Signal (SONET)

SubnetworkA group of interconnected/interrelated Network Elements. The most common connotationis a synchronous network in which the Network Elements have data communicationschannel (DCC) connectivity.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-37

SupervisorA user of the application with supervisor user privileges.

SuppressionA process where service-affecting alarms that have been identified as an “effect” are notdisplayed to a user.

SYNCSynchronizer

Synchronization MessagingSynchronization messaging is used to communicate the quality of network timing,internal timing status, and timing states throughout a subnetwork.

SynchronousThe essential characteristic of time scales or signals such that their correspondingsignificant instances occur at precisely the same average rate, generally traceable to asingle Stratum-1 source.

Synchronous NetworkThe synchronization of transmission systems with synchronous payloads to a master(network) clock that can be traced to a reference clock.

Synchronous PayloadPayloads that can be derived from a network transmission signal by removing integralnumbers of bits from every frame. Therefore, no variable bit-stuffing rate adjustmentsare required to fit the payload in the transmission signal.

SYSCTLSystem Controller circuit pack

System AdministratorA user of the computer system on which the system’s OS software application can beinstalled.

.................................................................................................................................................................................................................................

T TARPTID Address Resolution Protocol

TCA (Threshold-Crossing Alert)A message sent from a network element indicating that a certain performance monitoringparameter has exceeded a specified threshold.

TDM (Time Division Multiplexing)A technique for transmitting a number of separate data, voice, and/or video signalssimultaneously over one communications medium by interleaving a portion of eachsignal one after another.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Through (or Continue) Cross-ConnectionA cross-connection within a ring, where the input and output tributaries have the sametributary number but are in lines opposite each other.

Through TimingRefers to a network element that derives its transmit timing in the east direction from areceived line signal in the east direction and its transmit timing in the west directionfrom a received line signal in the west direction.

THzTerrahertz (1012 Hz)

TID (Target Identifier)A provisionable parameter that is used to identify a particular Network Element within anetwork. It is a character string of up 20 characters where the characters are letters,digits, or hyphens (-).

TL1 (Transaction Language One)A machine-to-machine communications language that is a subset of ITU’shuman-machine language.

TMNTelecommunications Management Network

TRTechnical Requirement

Transmit-DirectionThe direction outwards from the Network Element.

TributaryA signal of a specific rate (2 Mb/s, 34 Mb/s, 140 Mb/s, VC12, VC3, VC4, STM-1 orSTM-4) that may be added to or dropped from a line signal.

TributaryA path-level unit of bandwidth within a port, or the constituent signal(s) being carried inthis unit of bandwidth, for example, an STM-1 tributary within an STM-N port.

Tributary Unit PointerIndicates the phase alignment of the VC with respect to the TU in which it resides. Thepointer position is fixed with respect to the TU frame.

True Wave™ Optical FiberLucent Technologies’ fiber generally called non-zero dispersion-shift fiber, with acontrolled amount of chromatic dispersion designed for amplified systems in the1550/1310 nm range.

TSA (Time Slot Assignment)

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-39

A capability that allows any tributary in a ring to be cross-connected to any tributary inany lower-rate, non-ring interface or to the same-numbered tributary in the opposite sideof the ring.

TSI (Time Slot Interchange)The ability of the user to assign cross-connections between any tributaries of any lineswithin a Network Element. Three types of TSI can be defined: Hairpin TSI, InterringTSI (between rings), and Intraring TSI (within rings).

TSOTechnical Support Organization

TTPTrail Termination Point

TU (Tributary Unit)An information structure which provides adaptation between the lower order path layerand the higher path layer. Consists of a VC-n plus a tributary unit pointer TU PTR.

TUGTributary Unit Group

Two-Way Point-to-Point Cross-ConnectionA two-legged interconnection, that supports two-way transmission, between two and onlytwo tributaries.

Two-Way RollThe operation which moves a two-way cross-connection between tributary i and tributaryj to a two-way cross-connection between the same tributary i and a new tributary k witha single user command.

.................................................................................................................................................................................................................................

U UAS (Unavailable Seconds )In performance monitoring, the count of seconds in which a signal is declared failed orin which 10 consecutively severely errored seconds (SES) occurred, until the time when10 consecutive non-SES occur.

Unacknowledged Information Transfer Service (UITS)The unconfirmed mode of operation of the LAPD protocol.

UNEQPath Unequipped

UpstreamAt or towards the source of the considered transmission stream, for example, looking inthe opposite direction of transmission.

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

User PrivilegePermissions a user must perform on the computer system on which the system softwareruns.

UTC (Universal Coordinated Time)A time-zone independent indication of an event. The local time can be calculated fromthe Universal Coordinated Time.

.................................................................................................................................................................................................................................

V VVolts

VACVolts Alternating Current

ValueA number, text string, or other menu selection associated with a parameter.

VariableAn item of data named by an identifier. Each variable has a type, such as int or Object,and a scope.

VC-n (Virtual Container of n-th order)Container of n-th order with path overhead.

VC-n-Xv (A group of X virtually concatenated VC-n’s)A group of X individual Virtual Containers of n-th order that form a VirtualConcatenated Group (VCG). The X in VC-n-Xv always denotes the actual number ofVC-n’s that are transported in the VCG which may vary when the Link CapacityAdjustment Scheme (LCAS) is active.

VCG (Virtual Concatenated Group)A group of Virtual Containers that are virtually concatenated to offer larger payloadbandwidth.

VDCVolts Direct Current

VFVoice frequency

VirtualRefers to artificial objects created by a computer to help the system control sharedresources.

Virtual CircuitA logical connection through a data communication (for example, X.25) network.

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-41

Voice Frequency (VF) CircuitA 64 kilobit per second digitized signal.

Volatile MemoryType of memory that is lost if electrical power is interrupted.

.................................................................................................................................................................................................................................

W WADWavelength Add/Drop

WAN (Wide Area Network )A communication network that uses common-carrier provided lines and covers anextended geographical area.

WanderLong term variations of amplitude frequency components (below 10 Hz) of a digitalsignal from their ideal position in time possibly resulting in buffer problems at areceiver.

Wavelength InterchangeThe ability to change the wavelength associated with an STM-N signal into anotherwavelength.

WaveStar® OLS 40G/80G/400GWaveStar® Optical Line System 40G/80G/400G

WDCSWideband Digital Cross-Connect System

WDM (Wavelength Division Multiplexing)A means of increasing the information-carrying capacity of an optical fiber bysimultaneously transmitting signals at different wavelengths.

Wideband CommunicationsVoice, data, and/or video communication at digital rates from 64 kb/s to 2 Mb/s.

WorkingLabel attached to a physical entity. In case of revertive switching the working line orunit is the entity that is carrying service under normal operation. In case of nonrevertiveswitching the label has no particular meaning.

Working StateThe working unit is currently considered active by the system and that it is carryingtraffic.

WRT (Wait to Restore Time)Corresponds to the time to wait before switching back after a failure has cleared, in arevertive protection scheme. This can be between 0 and 15 minutes, in increments of one

Glossary

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

minute.

WSWork Station

WTR (Wait to Restore)Applies to revertive switching operation. The protection group enters the WTR statewhen all Equipment Fail (EF) conditions are cleared, but the system has not yet revertedback to its working line. The protection group remains in the WTR state until theWait-to-Restore timer completes the WTR time interval.

WTU3 (WaveWrapper™ Transport Unit 3)The WTU3 corresponds to the Optical Channel Transport Unit (OTU3) in the ITU-TRec. G.709.

.................................................................................................................................................................................................................................

X X.25An ITU standard defining the connection between a terminal and a publicpacket-switched network

X.25 Interface/ProtocolThe ITU packet-switched interface standard for terminal access that specifies threeprotocol layers: physical, link, and packet for connection to a packet-switched datanetwork.

XCCross-connect and timing unit

.................................................................................................................................................................................................................................

Z Zero Code SuppressionA technique used to reduce the number of consecutive zeros in a line-coded signal(B3ZS, B8ZS).

Glossary

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


GL-43

Index

Numerics

2-fiber BLSR/MS-SPRing,2-215

4-fiber BLSR/MS-SPRing,2-215

.............................................................

A A1/A2 bytes, 2-160

ABNSee: Abnormal condition

ABN LED, 4-83

Abnormal condition, 2-39

Acknowledged InformationTransfer Service (AITS), 2-13,2-14

Adaptive-rate tributaryoperation, 2-129

Address List Overflow, 2-11

ADDROVSee: Address List OverflowSee: ASTN Neighbor Not

Available

Affect-on-service attribute, 2-2

Air filter, 4-18

AIS-LSee: Alarm Indication

Signal

AIS-PSee: Alarm Indication

Signal

Alarm category, 2-2, 4-7

Alarm descriptions, 2-1

Alarm history, 4-9, 4-9

Alarm Indication Signal

AIS-L, 2-152, 3-155

AIS-P, 2-119, 3-144

Alarm level, 4-5

Alarm list, 4-3

Alarm log, 4-9

Alarm severity (default setting),2-3

Alarm severity assignmentprofile (ASAP), 2-3

Alarm short designation, 2-2

Alarm source, 2-4

Alarm status display, 4-3, 4-8

Alarm typeSee: Alarm category

Alarm identifier, 2-2

Antistatic covers, 1-25

Appropriate APS code, 2-112

APS bytes, 2-103, 2-112,2-114, 2-186, 2-191

APS codes, 2-112

APS protocol, 2-179

APSCSee: Inconsistent APS Codes

ASAPSee: Alarm severity

assignment profile

ASTN Neighbor Not Available,2-12

Automatic node ID allocation,2-219

Automatic protection switchingprotocol, 2-179

.............................................................

B B1 byte, 4-84

B2 byte, 4-84

B2 bytes, 2-157

B3 byte, 2-122, 2-124

Backplane EEPROM, 2-41

Backplane Read Failure, 2-41

Backw Defect Transparent Ch

ODUBDIT, 2-154

Barred-hand symbol, 1-20

Battery Distribution and FuseBay (BDFB), 1-29, 1-32, 1-37

BDFBSee: Battery Distribution

and Fuse Bay

Bending radius, 4-21, 4-23

Bit error monitoring, 4-84

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


IN-1

Bit error ratio

Required measurementtimes, 2-156

BKUPMEMOSee: NVM Shortage

BKUPMEMPSee: IDE Flash Card Access

Fail

BLSR/MS-SPRing protectionswitching, 2-179, 2-215

BPEFSee: Backplane Read Failure

.............................................................

C C-bit parity application, 2-25

C2 byte, 2-134

Chapter descriptions, xix

CICOMFSee: CICTL Comm Failure

CICTL Comm Failure, 2-42,3-24

CICTL Failure, 2-43, 3-28

CICTL not Present, 2-44, 3-29

CICTL Powered Down, 2-45

CIFSee: CICTL FailureSee: CICTL Powered Down

CIMISSSee: CICTL not Present

Circuit Pack Clock Failure,2-204, 2-206, 3-211

Circuit Pack Comm Failure,2-46, 3-30

Circuit pack faceplate LEDs,2-4

Circuit Pack Failure, 2-47, 3-49

Circuit Pack not Present, 2-48,3-46

Circuit pack reset, 4-76

Circuit Pack Type Mismatch,2-50, 3-47

Clear channel, 2-25

Climatic conditions, 1-26

Clock and synchronisationdistribution, 2-207, 2-210

Closed ring, 2-215

Comm Channel Failure, 2-51,3-50

CompactFlash® card, 2-64,2-65, 4-48, 4-75, 4-75, 5-2

Connector types, 1-15

Consequent actions, 2-4

Controller recovery, 5-2

Controller reset, 4-76

Conventions, xx

Cooling, 4-70

Correction range, 2-92

CPCOMFSee: Circuit Pack Comm

Failure

CPDEGRSee: Unit Cooling Degraded

CPFAILSee: Circuit Pack Failure

CPTEMPSee: Unit Temperature too

High

Cross-connection loopback,2-39, 4-25, 4-28, 4-40, 4-81

CSD function, 2-207, 2-210

CSDPFSee: Protection Clock Input

Fail

CSDWFSee: Worker Clock Input

Fail

CTL Comm Failure, 2-52, 3-58

CTL recovery, 5-2

CTLCOMFSee: CTL Comm Failure

Customer comment form, xxvii

.............................................................

D Danger classification, 1-5

Data Communication Network(DCN), 2-10

Database backup, 4-48

DCC MS/Line failure, 2-13,3-6

DCC RS/Section failure, 2-14,3-11

DCCMSFSee: DCC MS/Line failure

DCCRSFSee: DCC RS/Section

failure

DCN Provisioning Not Valid,2-15

DCTLUNAVAILSee: Duplex Control not

Present

Default alarm severity, 2-3

Default K-bytes, 2-179, 3-185

DEG-PSee: Degraded Signal

Degraded DS3 Line signal

DS3LineDEG, 2-22

Degraded Signal

DEG-P, 2-120

MSDEG, 2-155

THPDEG, 2-121

Delineation, 2-89

Discovery of the ring type,2-220

DKBSee: Default K-bytes

Index

.................................................................................................................................................................................................................................

IN-2 Lucent Technologies - ProprietarySee notice on first page

365-374-186Issue 1, December 2005

Document conventions, xx

Documentation set, xxii

DS3 AIS, 3-14

DS3AIS, 2-23

DS3 AIS egress, 3-15

DS3AIS-EGR, 2-24

DS3 Application Mismatch in,3-16

DS3AIC, 2-25

DS3 C-bit parity format, 2-25

DS3 formats, 2-25

DS3 IDLE in

DS3IDLE, 2-26

DS3 LOF egress, 3-17

DS3LOF-EGR, 2-27

DS3 Loss of Frame, 3-19

DS3LOF, 2-28

DS3 Loss of Signal

DS3LOS, 2-29

DS3 RAI egress, 3-20

DS3RAI-EGR, 2-30

DS3 RAI in, 3-21

DS3RAI, 2-32

DS3AICSee: DS3 Application

Mismatch in

DS3AISSee: DS3 AIS

DS3AIS-EGRSee: DS3 AIS egress

DS3IDLESee: DS3 IDLE in

DS3LineDEGSee: Degraded DS3 Line

signal

DS3LOFSee: DS3 Loss of Frame

DS3LOF-EGRSee: DS3 LOF egress

DS3LOSSee: DS3 Loss of Signal

DS3RAISee: DS3 RAI in

DS3RAI-EGRSee: DS3 RAI egress

DUPL-RNGSee: Duplicate Ring Node

Duplex Control not Present,2-53, 3-60

Duplicate Ring Node, 2-181,3-190

DUR shelf, 4-66

.............................................................

E East/West interface ports, 2-212

ECI Comm Failure, 2-55, 3-61

ECI Mismatch Failure, 2-56,3-65

ECI not Present, 2-57, 3-68

ECICOMFSee: ECI Comm Failure

ECIMISMASee: ECI Mismatch Failure

ECIMISSSee: ECI not Present

Effect-on-service attribute, 2-3

Electrical interfaces, 4-66

Electronic type label, 2-41

Electrostatic discharge, 1-20,1-25, 1-27, 1-33, 1-38

Electrostatic protection, 1-20

Environment message, 2-35

Environmental alarms, 2-34

EQPTSee: Circuit Pack Clock

Failure

ESDSee: Electrostatic discharge

ESPSee: Electrostatic protection

ESP bonding point, 1-20

ET-PREEMPTSee: Extra Traffic

Preempted

Event status display, 2-39

EXC-PSee: Excessive Bit Error

Ratio

Excessive Bit Error Ratio,3-156

EXC-P, 2-122

MSEXC, 2-157

THPEXC, 2-124

Exchangability of circuit packs,4-57

Exchangeability, 4-58

External timing output, 2-208,3-217

External timing reference,3-213, 3-219, 3-220

Extra traffic, 2-198

Extra Traffic Preempted, 2-183,3-192

.............................................................

F Facility loopback, 2-39, 4-30,4-33, 4-84

Status, 4-33

FAILTOSWSee: Path Switch Denial

Fan Failure, 2-58, 3-69

Fan speed, 3-69

Fan Unit Comm Failure, 2-59,3-72

Fan Unit Failure, 2-60, 3-76

Index

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


IN-3

Fan Unit not Present, 2-61,3-80

Fan Voltage Feed A Failure,2-62, 3-82, 3-102

Fan Voltage Feed B Failure,2-63, 3-82, 3-102

FANFSee: Fan Failure

FANUNITCOMFSee: Fan Unit Comm

Failure

FANUNITFSee: Fan Unit Failure

FANUNITMISSSee: Fan Unit not Present

Far End Signal Fail, 2-103,3-129

Far-side facility loopback, 4-30,4-33, 4-40, 4-85

FDA/CDRH laser classification,1-12, 1-17

FDA/CDRH Regulations, 1-16

FEEDAFSee: Fan Voltage Feed A

Failure

FEEDBFSee: Fan Voltage Feed B

Failure

FESFSee: Far End Signal Fail

File Transfer TranslationDevice (FTTD), 4-44

Forced cross-connectionloopback, 4-82

Forced switch, 2-39

Frame alignment bytes, 2-160,4-84

Free-running mode, 2-39

FTTDSee: File Transfer

Translation Device

Full reset, 4-76

.............................................................

G GARP VLAN RegistrationProtocol (GVRP), 2-95

General alarm information, 2-2

GFP Loss of Frame, 2-89

GFPLOFSee: GFP Loss of Frame

.............................................................

H H4 byte, 2-126

Hazard level, 1-18

History alarms, 4-9

Holdover mode, 2-39

.............................................................

I IDE Flash Card Access Fail,2-64, 3-87

IEC laser classification, 1-12,1-17

IEC Requirements, 1-16

IEEE 802.3 MAC address,2-181, 2-219

IMAPSSee: Improper APS Codes

Improper APS Codes, 2-184,3-193

Inappropriate APS code, 2-112

Inconsistent APS Codes, 2-186,3-197

Inconsistent Ring ProtectionMode, 2-188, 3-202

Insertion and removal facilities,1-20

Invisible laser radiation, 1-29,1-32, 1-37, 4-21, 4-23, 4-35

.............................................................

J J0 byte, 2-175

J1 byte, 2-144, 2-145

.............................................................

K K1 byte, 2-116

K1/K2 bytes, 2-103, 2-112,2-114, 2-179, 2-184, 2-186,2-191

K2 byte, 2-105, 2-107, 2-110,2-110, 2-116, 2-172

.............................................................

L LAN Auto NegotiationMismatch, 2-90

LAN Loss of Signal, 2-94

LANANMSee: LAN Auto Negotiation

Mismatch

LANLOSSee: LAN Loss of Signal

LAPD mode, 3-6, 3-11

LAPD role, 3-6, 3-11

Laser classes, 1-12

Laser safety instructions, 1-13

Laser warning labels, 1-27,1-33

LCASSee: Link Capacity

Adjustment Scheme

LCS/RCS, A-3

LIDMSMSee: Protocol Version

Mismatch

LIDRSMSee: Protocol Version

Mismatch

Lightguide build-outs, 4-23

Line Protection, 2-107

Index

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Line timing reference, 3-213,3-219, 3-221

Link Capacity AdjustmentScheme, 2-126, 2-138

Link ID information, 2-19

Link ID protocol, 2-19

List of current alarms, 4-3, 4-5

List of history alarms, 4-9

Local Cross-Connect (LXC),4-66

Local indications, 2-4

Local squelch map, 2-189

Local Squelch Map Conflict,2-189, 3-203

Local/Regional CustomerSupport. See LCS/RCS., A-3

Lockout of protection, 2-39

LOFSee: Loss of Frame

LOF Transparent Ch

ODULOFT, 2-159

LOF-T-EGRSee: Loss of Frame transp

ch egress

Long path, 2-184, 2-186

Loopback

Cross-connection loopback,4-25, 4-28, 4-40, 4-81

Facility loopback, 4-30,4-33, 4-84

Far-side facility loopback,4-30, 4-33, 4-40, 4-85

Manual loopback, 4-35

Near-side facility loopback,4-30, 4-33, 4-40, 4-84

LOP-PSee: Loss of Pointer

LOSSee: Loss of Signal

Loss of Alignment, 2-92, 3-121

Loss of Frame, 2-160, 3-163

Loss of Frame transp ch egress

LOF-T-EGR, 2-162, 3-166

Loss of Multiframe, 2-92,2-126

Loss of Multiframe TransparentCh

ODULOMT, 2-163

Loss of Pointer, 2-128

THPLOP, 2-129

Loss of Signal, 2-164, 3-167

Loss of Synchronisation, 2-205,3-213

LXC

Local Cross-Connect, 4-66

.............................................................

M MACVLANOVFWSee: max number of VLAN

instances reached

Maintenance condition, 4-44,5-8

Maintenance mode, 2-39

maintenance service, A-2

Management CommunicationNetwork (MCN), 2-10

Manual loopback, 4-35

max number of VLANinstances reached, 2-95, 3-122

Maximum switch capacity, 4-70

MF1See: Multiframe 1

MF2See: Multiframe 2

Miscellaneous Discrete Input,2-35

MISC_1 MISC_8See: Miscellaneous Discrete

Input

MS-SPRing port protectiongroup, 2-216

MSDEGSee: Degraded Signal

MSEXCSee: Excessive Bit Error

Ratio

MSPSee: Multiplex Section

Protection

MSSSFSee: Server Signal Fail

Multiframe 1, 2-126

Multiframe 2, 2-126

Multiframe indicator, 2-126

Multiplex Section Protection(MSP), 2-107

.............................................................

N NE alarm list, 4-3

NE alarm log, 4-9

NE Clock Failure, 2-204,2-206, 3-214

NE database, 4-48

NE name, 2-181

Near-side facility loopback,4-30, 4-33, 4-40, 4-84

Network address protocol, 2-19

NID-CONFLSee: Node ID Mismatch

Node ID, 2-191, 2-219

Automatic node IDallocation, 2-219

Node ID Mismatch, 2-191

Index

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


IN-5

Nominal voltage, 1-30

Non-volatile memory, 2-64,2-65

Non-volatile memory (NVM),4-48, 4-53

NSAP address, 2-19, 2-181,2-216, 2-219

NVMSee: Non-volatile memory

NVM Shortage, 2-65, 3-89

.............................................................

O OA1/OA2 bytes, 2-166, 2-177

OChSee: Optical Channel

OCh Loss of Frame, 2-166

OCHLOF, 3-174

OCHLOFSee: OCh Loss of Frame

ODUBDITSee: Backw Defect

Transparent Ch

ODULOFTSee: LOF Transparent Ch

ODULOMTSee: Loss of Multiframe

Transparent Ch

ODUPLMTSee: Payload Mismatch

Transparent Ch

ODUSSFTSee: Server Signal Fail

Transparent Ch

Office alarm interfaces, 2-4

OMFAILSee: Optical Module Fail

OMMISMASee: Optical Module Type

Mismatch

OMMISSSee: Optical Module not

Present

OMUNSUPSee: Optical Module not

supported

ONI Failure on protecting CTL,2-66, 3-90

ONI Failure on working CTL,2-68, 3-93

ONIFPSee: ONI Failure on

protecting CTL

ONIFWSee: ONI Failure on

working CTL

Open Ring, 2-192, 2-215, 2-217

Optical Channel (OCh), 2-160

Optical circuit packspecifications, 1-14

Optical interfaces, 4-66

Optical Module Fail, 2-70, 3-96

Optical Module not Present,2-72, 3-97

Optical Module not supported,2-73, 3-98

Optical Module TypeMismatch, 2-74, 3-99

Optical port unit parameters,4-37

.............................................................

P Packaging, 1-25

PAMARCHSee: Prot. Arch. Mismatch

PAMMODESee: Prot. Arch. Mode

Mismatch

PAMOPERSee: Prot. Arch. Operation

Mismatch

PARARREPSee: Partitioned Area Repair

Partial Transport Capacity Loss,2-97, 3-123

Partition repair tunnel, 2-16

Partitioned Area Repair, 2-16,3-8

Path Switch Denial, 2-131

FAILTOSW, 3-145

Path trace identifier, 2-144,2-145

Payload Defect Indication,2-132

Payload Mismatch, 2-134

Payload Mismatch TransparentCh

ODUPLMT, 2-167

Payload realignment, 2-92

PDI-PSee: Payload Defect

Indication

PDPSee: Power Distribution

Panel

PIEFSee: Power Interface Read

Failure

PIMISSSee: Power Interface not

Present

Pipe mode, 2-129

Post DCM Signal Loss, 2-168,3-175

POSTDCMLOSSee: Post DCM Signal Loss

Power Distribution Panel(PDP), 1-29, 1-32, 1-37

Power Interface not Present,2-75, 3-100

Index

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

Power Interface Read Failure,2-76, 3-101

POWFSee: System Power Failure

PRCDRERRSee: Circuit Pack Type

Mismatch

Pre DCM Signal Loss, 3-176

PREDCMLOS, 2-170

PREDCMLOSSee: Pre DCM Signal Loss

Preemption, 2-198

PRIMSee: primary section

Mismatch

primary section Mismatch,2-105, 3-132

Probable cause, 2-2

Prot. Arch. Mismatch, 2-107,3-134

Prot. Arch. Mode Mismatch,2-108, 3-135

Prot. Arch. OperationMismatch, 2-110, 3-136

Prot. Switch ByteInappropriate, 2-112, 3-137

Prot. Switch ByteUnacceptable, 2-114, 3-138

Protection architecture, 2-107

Protection Clock Input Fail,2-207, 3-215

Protection timing reference,2-207, 2-207, 2-210

Protocol Version Mismatch,2-18, 3-9

PROVINVALSee: DCN Provisioning Not

Valid

PSBINAPPRSee: Prot. Switch Byte

Inappropriate

PSBUNACCSee: Prot. Switch Byte

Unacceptable

.............................................................

R Realignment process, 2-92

Refresh button, 4-7

Remote Defect Indication

RFI-L, 2-172, 3-177

RFI-P, 2-135, 3-146

THPRDI, 2-137, 3-147

REPLUNITMISSSee: Circuit Pack not

Present

Reprovisioning, 4-58

Reset, 4-76, 4-80

RFI-LSee: Remote Defect

Indication

RFI-PSee: Remote Defect

Indication

Ring circuits, 2-189

Ring Discovery in Progress,2-193, 2-217, 3-205

Ring Incomplete, 2-195, 2-217

Ring map, 2-216

Ring protection mode, 2-220

Ring Protection SwitchSuspended, 2-197, 3-207

Ring topology, 2-193, 2-215

Ring type discovery, 2-220

RNG-DSCVYSee: Ring Discovery in

Progress

RNG-INCSee: Ring Incomplete

RNG-IRPMSee: Inconsistent Ring

Protection Mode

RNG-OPENSee: Open Ring

RNG-PSSSee: Ring Protection Switch

Suspended

RNG-URTSee: Unknown Ring Type

RSTIMSee: Trace Identifier

Mismatch

.............................................................

S S1 byte, 3-221

Safety of laser products, 1-16,1-16

SCMSee: Switch Channel

Mismatch

SDH tributary AIDs, 4-10

SDH tributary numberingformat, 4-12

SDH/SONET tributarynumbering, 4-87

Section trace identifier, 2-175

Sequence number, 2-126, 2-138

Sequence Number Mismatch,2-92, 2-138

Server Signal Fail

MSSSF, 2-173, 3-178

SSF-P, 2-140, 3-148

THPSSF, 2-141, 3-149

VCGSSF, 2-98, 3-124

Server Signal Fail TransparentCh, 3-179

ODUSSFT, 2-174

Index

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


IN-7

Short path, 2-184, 2-186

Signal Rate Mismatch, 2-142

Signalling CommunicationNetwork (SCN), 2-10

Sink End Failure of Protocol,2-99, 3-125

SONET tributary numberingformat, 4-12

Source End Failure of Protocol,2-100, 3-126

SQMAP-CONFLSee: Local Squelch Map

Conflict

Squelching, 2-198

SRM-PSee: Signal Rate Mismatch

SSF-PSee: Server Signal Fail

SSMSee: Synchronization Status

Message

Standards Compliance, 1-16

Switch Channel Mismatch,2-116, 3-142

SYNCCLKSee: NE Clock Failure

Synchronization Status Message(SSM), 3-221

SYNCLOSSSee: Loss of

Synchronisation

SYNCRFSee: Timing Reference

Failure

SYNCT4OUTSee: T4 quality unsufficient

SYSCOMFSee: Comm Channel Failure

System identifier, 2-181, 2-216,2-219

System Power Failure, 2-78,3-83, 3-102

.............................................................

T T4 quality unsufficient, 2-208,3-217

T4 timing output, 2-208

TCP/IP gateway, 4-44

technical support; support

technical, A-3

Test access session, 2-39

THPDEGSee: Degraded Signal

THPEXCSee: Excessive Bit Error

Ratio

THPLOPSee: Loss of Pointer

THPPLMSee: Payload Mismatch

THPRDISee: Remote Defect

Indication

THPSSFSee: Server Signal Fail

THPTIMSee: Trace Identifier

Mismatch

THPUNEQSee: Unequipped

TI Mismatch, 2-79

TI not Present, 2-80, 3-105

TIM-PSee: Trace Identifier

Mismatch

TIM-T-EGRSee: Trace Identifier

Mismatch egress

Timing reference

External timing output,3-217

External timing reference,3-213, 3-219, 3-220

Line timing reference,3-213, 3-219, 3-221

Timing Reference Failure,2-209, 3-219

TIMISSSee: TI not Present

TIMMSee: TI Mismatch

Total Transport Capacity Loss,2-101, 3-127

Trace Identifier Mismatch

RSTIM, 2-175, 3-180

THPTIM, 2-145, 3-150

TIM-P, 2-144, 3-151

Trace Identifier Mismatchegress

TIM-T-EGR, 2-176, 3-181

Traffic Squelched, 2-198

Traffic squelching, 2-198

Trail signal label (TSL), 2-134

Transmission capacity per slot,4-111

Tributary numbering, 4-87

OC-12/STM-4 port, 4-87

OC-192/STM-64, 4-88

OC-3/STM-1 port, 4-87

OC-48/STM-16 port, 4-87

OC-768/STM-256 port, 4-92

VCG port, 4-108

Tributary numbering format,4-12

Tributary operation mode, 4-81

Index

.................................................................................................................................................................................................................................


365-374-186Issue 1, December 2005

TSSee: Traffic Squelched

TSLSee: Trail signal label

TSS

Technical Support Service,A-3

TXI bus, 4-111

TXI Failure, 2-81, 3-106

TXInFSee: TXI Failure

.............................................................

U UNEQ-PSee: Unequipped

Unequipped, 2-147

THPUNEQ, 2-149, 3-152

UNEQ-P, 3-153

Unit Cooling Degraded, 2-83,3-109

Unit Temperature too High,2-84, 3-112

Universal slot, 4-67

Unknown Ring Type, 2-202

Unknown ring type, 2-220

UPCOMFSee: User Panel Comm

Failure

Update Alarms button, 4-7

Updating the alarm list, 4-7

UPMISSSee: User Panel not Present

User Panel Comm Failure,2-86, 3-115

User panel LEDs, 2-4

User Panel not Present, 2-87,3-119

.............................................................

V VCGSee: Virtual Concatenated

Group

VCGFOPRSee: Sink End Failure of

Protocol

VCGFOPTSee: Source End Failure of

Protocol

VCGLOASee: Loss of Alignment

VCGLOPCSee: Partial Transport

Capacity Loss

VCGLOTCSee: Total Transport

Capacity Loss

VCGSSFSee: Server Signal Fail

VCLOMSee: Loss of Multiframe

VCSQMSee: Sequence Number

Mismatch

Virtual Concatenated Group(VCG), 2-98, 2-138

Virtual switch, 2-95

VLAN connections, 2-95

.............................................................

W WaveStar® CIT NE Alarm List,4-3, 4-5

WaveStar® CIT NE Alarm Log,4-9

Worker Clock Input Fail,2-210, 3-222

Working timing reference,2-207, 2-210, 2-210

WTU3 Loss of Frame, 2-177

WTU3LOF, 3-183

WTU3LOFSee: WTU3 Loss of Frame

Index

.................................................................................................................................................................................................................................365-374-186Issue 1, December 2005


IN-9

LambdaUnite MultiService Switch (MSS)...Linear protection switching alarms Overview..... 3-128 Clearing Far End Signal Fail ..... 3-129 Clearing primary section Mismatch ..... 3-132

Documents