Troubleshooting_Manual[1].pdf

(1)

Troubleshooting Manual (TSMN)

A42022-L5961-L081-03-7619

(2)

2 A42022-L5961-L081-03-7619

Issue: 3 Issue date: August 2008

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

f Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system. The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

(3)

A42022-L5961-L081-03-7619

Issue: 3 Issue date: August 2008

3

Statements of compliance

FCC statement

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Shielded cables must be used with this unit to ensure compliance with the Class A FCC limits.

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equip-ment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

CE statement

The CE conformity declaration for the product is fulfilled when the system is built and cabled in line with the information given in the manual and the documentation specified within it, such as installation instructions, cable lists or the like. Where necessary project-specific documentation should be taken into consideration. Deviations from the specifications or independent modifications to the layout, such as use of cable types with lower screening values for example, can lead to violation of the CE protection requirements. In such cases the conformity declaration is invalidated. The responsibility for any prob-lems which subsequently arise rests with the party responsible for deviating from the installation spec-ifications.

(4)

4 A42022-L5961-L081-03-7619

(5)

A42022-L5961-L081-03-7619 Issue: 3 Issue date: August 2008

5

3.1.6 APSBUF . . . 52 3.1.7 APSBUR . . . 53 3.1.8 APSM . . . 53 3.1.9 BTBM . . . 54 3.1.10 CALIBRATION_FAIL . . . 54 3.1.11 CALIBRATION_FAILL . . . 55 3.1.12 CALIBRATION_FAILT1 . . . 55 3.1.13 CALIBRATION_FAILT2 . . . 56 3.1.14 CALIBRATION_FAILT3 . . . 56 3.1.15 CALIBRATION_FAILT4 . . . 57 3.1.16 CANFAIL. . . 57 3.1.17 CDL. . . 58

(6)

6 A42022-L5961-L081-03-7619 Issue: 3 Issue date: August 2008

3.1.18 CFAIL . . . 60

3.1.18.1 CFAIL raised by OSCT slot . . . 61

3.1.18.2 CFAIL raised by SMU slot . . . 61

3.1.18.3 CFAIL raised by OCR10T-LH or TEX-LH slot . . . 61

3.1.18.4 CFAIL raised by 40G card slots . . . 62

3.1.18.5 CFAIL raised by FSU slot in MCU-Shelf . . . 63

3.1.18.6 CFAIL raised by other slot types . . . 63

3.1.19 CFF . . . 64 3.1.20 CHCNTMISM . . . 64 3.1.21 CLOSSHDS . . . 66 3.1.22 CLOSSOTS . . . 66 3.1.23 CMISM . . . 67 3.1.24 CMISS . . . 69 3.1.25 CONCABF . . . 70 3.1.26 CP . . . 70

3.1.26.1 Special procedure “A” for CP alarm raised by PUMP card . . . 71

3.1.26.2 Special procedure “B” for CP alarm raised by PUMP card . . . 71

3.1.27 CPHDS . . . 72

3.1.28 CPOTS. . . 73

3.1.29 CTP . . . 74

3.1.30 CTRLCABLP . . . 74

3.1.31 CUPGVIOL1 . . . 75

3.1.31.1 Channel Upgrade Rules. . . 76

3.1.32 DSPP . . . 77 3.1.33 ETHSWFAIL . . . 77 3.1.34 FAN_MAJOR . . . 78 3.1.35 FAN_MINOR . . . 78 3.1.36 FBSIG_ABSENT . . . 79 3.1.37 FBSIG_DEGRADED . . . 79 3.1.38 FIFOFLOWP . . . 80 3.1.39 FN11F . . . 81 3.1.40 FN12F . . . 82 3.1.41 FN21F . . . 83 3.1.42 FN22F . . . 84 3.1.43 FN31F . . . 85 3.1.44 FN32F . . . 86 3.1.45 FN1CF . . . 87 3.1.46 FN2CF . . . 87 3.1.47 FN3CF . . . 88 3.1.48 FN1M . . . 89 3.1.49 FN2M . . . 89 3.1.50 FN3M . . . 89 3.1.51 FNLOW . . . 90 3.1.52 FNLOWM . . . 91 3.1.53 FNUPP . . . 91 3.1.54 FNUPPM . . . 92 3.1.55 FREQNOTSUP . . . 93

(7)

7

3.1.55.1 FREQNOTSUP raised by an OTS-4520 (TDCM) card . . . 93

3.1.55.2 FREQNOTSUP raised by an OTS-4xxx V3 card . . . 94

3.1.56 GNELOS . . . 95

3.1.57 GTMMP. . . 99

3.1.58 GTP. . . 99

3.1.58.1 Hints for multiple GTP alarms . . . 101

3.1.59 HDS_APSMISS . . . 102 3.1.60 HDSRECOVERMODE . . . 102 3.1.61 ICP . . . 103 3.1.62 ILOL . . . 103 3.1.63 ILOL1 . . . 104 3.1.64 ILOL2 . . . 105 3.1.65 ILOL3 . . . 106 3.1.66 IOPL . . . 107 3.1.67 ISLP . . . 107 3.1.68 LNREFCLOCKP . . . 110 3.1.69 LOCNELOS . . . 110 3.1.70 LOSADD . . . 111 3.1.71 LOSIn1 . . . 112 3.1.72 LOSIn2 . . . 114 3.1.73 LOSIn3 . . . 114 3.1.74 LOSIn4 . . . 115 3.1.75 LSBFAIL . . . 116 3.1.76 LSS . . . 116 3.1.77 MEASF . . . 117 3.1.78 MFNF . . . 118 3.1.79 MIBF . . . 120 3.1.80 MIBF . . . 121 3.1.81 MIBM. . . 121 3.1.82 MIBS256 . . . 122 3.1.83 MTX_APSMISS . . . 123 3.1.84 MWBMP . . . 123 3.1.85 NLDC1 . . . 124 3.1.86 NLDC2 . . . 125 3.1.87 NOSYNCMSTR . . . 126 3.1.88 NOTIMMSTR . . . 127 3.1.89 NQO . . . 127 3.1.90 NTPSVACCFAIL. . . 128 3.1.91 NVCDBMIG. . . 128 3.1.92 OBLOS . . . 129 3.1.93 OBTF . . . 134 3.1.94 OLOL . . . 134 3.1.95 OPLOS . . . 135 3.1.96 OPTF . . . 137 3.1.97 OSAMP . . . 137 3.1.98 OSAPF . . . 138 3.1.99 OSCTD1 . . . 138

(8)

3.1.100 OSCTD2 . . . 139 3.1.101 OTS_APSMISS . . . 139 3.1.102 PbusF. . . 140 3.1.103 PCBF . . . 140 3.1.104 PDIFF. . . 141 3.1.105 PQMLOS . . . 141 3.1.106 PQMMP . . . 142 3.1.107 PREEMPF . . . 143

3.1.107.1Last Action message: Adjustable VOA range exceeded . . . 144

3.1.107.2Last Action message: Precondition violation . . . 145

3.1.108 PU1TD, PU2TD, PU3TD, PU4TD, and PU5TD . . . 146

3.1.109 PU1TF, PU2TF, PU3TF, PU4TF, and PU5TF . . . 147

3.1.110 PWCTLSUSP. . . 148 3.1.111 PWR1, PWR2, PWR3, and PWR4. . . 148 3.1.112 PWR12, PWR34, PWR13, and PWR24. . . 149 3.1.113 PWREQFAIL . . . 150 3.1.114 REGEN_PAIR_UNAVAIL. . . 150 3.1.115 REMNELOS . . . 151 3.1.116 SABF . . . 151 3.1.117 SAMISS . . . 152 3.1.118 SBL . . . 152 3.1.119 SC_DISK_SPACE . . . 157

3.1.120 SFPMISM1, SFPMISM2, SFPMISM3, and SFPMISM4. . . 157

3.1.121 SFPMISS1, SFPMISS2, SFPMISS3, and SFPMISS4 . . . 158

3.1.122 SFPMISS1, SFPMISS2, SFPMISS3, and SFPMISS4 . . . 158

3.1.123 SFPUNQ1, SFPUNQ2, SFPUNQ3, and SFPUNQ4 . . . 158

3.1.124 SHLFADRCH . . . 159 3.1.125 SLH . . . 160 3.1.126 SLL. . . 161 3.1.127 SPFAIL. . . 162 3.1.128 SRCP . . . 163 3.1.129 STORAGEFAIL . . . 163 3.1.130 SUBSMISMHDS . . . 164 3.1.131 SWDWNLD_OCU40FAIL. . . 164 3.1.132 SWP . . . 165 3.1.133 SWP1, SWP2, SWP3, and SWP4 . . . 165 3.1.134 SYNCPROG . . . 166 3.1.135 T3LOS . . . 167 3.1.136 TargetP . . . 167 3.1.137 TempHi . . . 168 3.1.138 TempHiC . . . 168 3.1.139 TempP . . . 169 3.1.140 TempPVOA . . . 170

3.1.141 TempP1, TempP2, TempP3, and TempP4 . . . 170

3.1.142 TempRegRun. . . 171

3.1.143 TimP. . . 171

(9)

9 3.1.145 TSCh2TD . . . 172 3.1.146 TSCh3TD . . . 172 3.1.147 TSCh4TD . . . 173 3.1.148 TSCh1TF . . . 173 3.1.149 TSCh2TF . . . 173 3.1.150 TSCh3TF . . . 174 3.1.151 TSCh4TF . . . 175 3.1.152 TSCh1TEMP. . . 175 3.1.153 TSCh2TEMP. . . 175 3.1.154 TSCh3TEMP. . . 176 3.1.155 TSCh4TEMP. . . 177 3.1.156 TWOSYNCMSTR . . . 177 3.1.157 TWOTIMMSTR . . . 178 3.1.158 ULEDF . . . 179 3.1.159 VOAP . . . 179 3.1.160 VOAP# . . . 180 3.1.161 VOLT. . . 181 3.1.162 VOLTL. . . 181

3.1.163 VOLTT1, VOLTT2, VOLTT3, and VOLTT4. . . 182

3.1.164 WSSMP . . . 182

3.1.165 XFP_MISM1 . . . 183

3.1.166 XFP_MISS1, XFP_MISS2, XFP_MISS3, and XFP_MISS4 . . . 184

3.1.167 XFP_QUAL1, XFP_QUAL2, XFP_QUAL3, and XFP_QUAL4 . . . 184

3.2 Communication Alarms. . . 185 3.2.1 BDI . . . 185 3.2.2 DMISM . . . 187 3.2.3 EOCI . . . 187 3.2.4 ETHNLNF . . . 189 3.2.5 EXC. . . 189 3.2.6 EXM . . . 190 3.2.7 FMISM . . . 190 3.2.8 GCCP . . . 191 3.2.9 HIPWRECD . . . 191 3.2.10 HIPWRECF. . . 192 3.2.11 LCK . . . 192 3.2.12 LFD . . . 193 3.2.13 LOC. . . 194

3.2.14 LOF (OSCT cards) . . . 196

3.2.15 LOF (OCU cards) . . . 196

3.2.15.1 Case A: OTU Connection Termination Point LOF . . . 198

3.2.15.2 Case B: Client to Line LOF . . . 199

3.2.15.3 Case C: Line to Client LOF . . . 200

3.2.16 LOFLOM . . . 200

3.2.17 LOM . . . 202

3.2.18 LOS (OLI, OM20, and OSCT cards) . . . 202

3.2.19 LOS (OCU cards) . . . 203

(10)

3.2.19.2 Line In LOS . . . 205 3.2.20 LTC . . . 206 3.2.21 MSIM . . . 207 3.2.22 OCI. . . 207 3.2.23 OPR . . . 208 3.2.24 OSCVIM . . . 209 3.2.25 PDHD . . . 210 3.2.26 PDLD . . . 211 3.2.27 PDF (Rx) . . . 212 3.2.28 PDF (Tx) . . . 213 3.2.29 PHF . . . 213 3.2.30 PHF (Rx) . . . 214 3.2.31 PHF (Tx) . . . 216 3.2.32 PLF . . . 217 3.2.33 PLF (Rx). . . 218 3.2.34 PLF (Tx) . . . 219 3.2.35 PHF (OPA) . . . 220

3.2.35.1 Special Procedure for OPAPC connected to a Pre-amplifier OLI . . . 221

3.2.36 PLF (OPA) . . . 222

3.2.37 PLM . . . 223

3.2.38 RETHNLNF . . . 223

3.2.39 SD (OLI and OSCT cards) . . . 224

3.2.40 SD (OCU cards) . . . 224

3.2.41 SSF . . . 225

3.2.42 SYNCFail . . . 227

3.2.43 TD (OLI cards) . . . 227

3.2.44 TD (OCU cards) . . . 228

3.2.45 TF (OLI and ODAxx cards) . . . 229

3.2.46 TF (OCU cards) . . . 230

3.2.47 TIM (OSCT cards) . . . 231

3.2.48 TIM (OCU cards) . . . 232

3.2.49 UPM . . . 233

3.3 Processing Error Alarms . . . 234

3.3.1 SCP . . . 234 3.4 Environmental Alarms . . . 235 3.4.1 EXT . . . 235 3.4.2 TIFACT . . . 236 3.5 Security Alarms . . . 237 3.5.1 EXCLOGIN . . . 237 3.5.2 PWEXP . . . 237 3.5.3 PWEXPSON . . . 238 3.6 Subsystem Alarms . . . 238 3.6.1 SMISS . . . 238 3.6.2 SFAIL . . . 241

4 Card Replacement Instructions . . . 242

4.1 CAX card . . . 243

(11)

11

4.3 FSU. . . 244

4.4 MCU card . . . 245

4.5 MIB circuit board . . . 246

4.6 NEAP Circuit Board . . . 246

4.7 OCR10 and TEX cards . . . 247

4.8 ODA20, ODA20 cards. . . 247

4.9 OLI cards (except Add-OLI and Drop-OLI) . . . 248

4.10 Add-OLI cards (used in ADU or ADX: Shelf 2, Slot 013) . . . 248

4.11 Drop-OLI cards (used in ADU or ADX: Shelf 2, Slots 007 and 010) . . . . 249

4.12 OM10, OM20 cards. . . 249

4.13 OMDFC, OMDFIC, OMDIFC cards (at OTTU) . . . 250

4.14 OMDFC or OMDFIC cards (at OADM100U) . . . 250

4.15 OMDIFC cards (at OADM100N) . . . 251

4.16 OMDFC card (when used for sub-band compensation) . . . 251

4.17 OPAPC card . . . 252

4.18 OSCTUT, OSCTUI cards . . . 252

4.19 PUMP cards . . . 253 4.20 PQMC card . . . 253 4.21 RPUMPC card . . . 254 4.22 SMU card . . . 255 4.23 TSC card. . . 255 4.24 UDCM . . . 256 4.25 UDCM Tray . . . 257 4.26 VOA2 card . . . 258 4.27 WBAN card . . . 259 4.28 WBAU card . . . 259 4.29 WBN card . . . 260 4.30 WSSC card . . . 261 4.31 SFP and XFP modules . . . 261

4.32 OTS-4400, OTS-40xx cards . . . 262

4.33 OTS-4520 card . . . 263

4.34 OTS-4540 card . . . 264

4.35 OTS-4700 Controller card. . . 265

4.36 OTS-4000 Air Filter . . . 267

4.37 MTS Shelf . . . 268

4.38 OCU Shelf. . . 269

4.39 CCEP card . . . 270

4.40 CCMP card . . . 270

4.40.1 CCMP replacement due to CP alarm . . . 270

4.40.2 CCMP replacement due to MIBF alarm . . . 270

4.40.3 CCMP replacement due to Loss of Communication . . . 271

4.41 Compact Flash Replacement . . . 272

4.42 CCSP card . . . 274

4.43 HDS Transponder cards . . . 274

4.44 HDS Shelf Air Filter. . . 274

(12)

5 Cold Start and Warm Start . . . 277

5.1 Differences between Warm and Cold Start . . . 277

5.2 Impact of Warm and Cold Start . . . 277

5.3 Use of Warm and Cold Start for troubleshooting . . . 278

5.4 Time required for software download to cards . . . 280

5.5 Fault LED behavior . . . 281

6 Link Control Troubleshooting . . . 282

6.1 Potential Symptoms . . . 282

7 Last Action and Load Result Messages. . . 287

7.1 List of Last Action Messages . . . 287

7.2 List of Load Result Messages . . . 294

8 Performance Monitoring and TCAs . . . 297

8.1 OCU transponder card Performance Parameters . . . 297

8.2 OTS-4000 transponder cards Performance Parameters . . . 298

8.3 HDS transponder card Performance Parameters . . . 300

8.4 Monitored parameter definitions. . . 301

9 MIB, MCU, and SAB replacement . . . 303

9.1 MIB circuit board replacement procedures . . . 303

9.1.1 Determine location of MCU raising the MIBF alarm. . . 304

9.1.1.1 MCU-MTS, MCU-OCU, MCU-OCU40, and MCU-OCU73 location . . . 306

9.1.1.2 MCU-CNE, MCU-TL1GNE, and MCU-Q3GNE location . . . 306

9.1.2 Determine location of the failed MIB . . . 307

9.1.3 Remove failed MIB. . . 311

9.1.4 Install new MIB. . . 313

9.2 MCU replacement procedures . . . 314

9.2.1 MCU replacement if MIBS256 is used . . . 314

9.2.2 MCU replacement if MIBS32 or MIBS32-2 is used . . . 315

9.2.2.1 MCU-CNE and Stand-alone MCU replacement (for MIBS32/MIBS32-2) . 317 9.2.2.2 Sub-agent MCU replacement (for MIBS32/MIBS32-2) . . . 318

9.3 SAB replacement procedures . . . 319

10 Packing equipment for return . . . 320

10.1 Definitions . . . 320

10.2 Requirements for packing and packaging . . . 320

10.3 Container requirements . . . 320

10.4 Labeling requirements . . . 320

11 Abbreviations . . . 322

(13)

13

List of Figures

Figure 1 Air Filter replacement in a 10G shelf . . . 31

Figure 2 APRM in an OTT that uses OMDFIC + OMDFC . . . 35

Figure 3 APRM in an OTT that uses OMDFIC + OMD2IC. . . 36

Figure 4 APRM in an OADM100U . . . 38

Figure 5 APRM in an OADM100N with CDAN and WBN . . . 40

Figure 6 APRM in an OADM100N with CDN and WBAN . . . 42

Figure 7 Diagram for APRM troubleshooting in OADM100N with CDN and WBAN . . . 43

Figure 8 Isolating the APRM-causing fault in an OADM100N (1 of 2) . . . 44

Figure 9 Isolating the APRM-causing fault in an OADM100N (2 of 2) . . . 45

Figure 10 Diagram for CDL alarm . . . 59

Figure 11 Identify the nearest upstream card . . . 62

Figure 12 MTS shelf Lower Fan Unit . . . 90

Figure 13 MTS shelf Upper Fan Unit . . . 92

Figure 14 GNELOS alarm causes . . . 97

Figure 15 “Connection Loss to GNE” alarm causes. . . 98

Figure 16 Arrangement of OPAPCs in a network . . . 100

Figure 17 Determining which OPAPC to Warm Start. . . 100

Figure 18 Multiple GTP alarm diagram . . . 101

Figure 19 OLI card interstage devices . . . 109

Figure 20 Reference diagram for LOSADD alarm . . . 112

Figure 21 Fiber connections from OLI cards to OPAPC . . . 125

Figure 22 OBLOS alarm with single fiber cut . . . 131

Figure 23 OBLOS alarm with double fiber cut . . . 132

Figure 24 Interstage devices for OBLOS alarm . . . 133

Figure 25 Example causes of an OPLOS alarm . . . 136

Figure 26 PQMLOS alarm diagram . . . 142

Figure 27 SBL alarm diagram for OTTU with OMDFIC + OMDFC . . . 153

Figure 28 SBL alarm diagram for OTTU with OMDFIC + OMD2IC . . . 154

Figure 29 SBL alarm diagram for OADM100U. . . 155

Figure 30 SBL alarm diagram for OADM100N. . . 156

Figure 31 BDI alarm diagram . . . 186

Figure 32 Reference network for EOCI alarm . . . 188

Figure 33 LCK alarm diagram . . . 193

Figure 34 LOF diagram for Case A . . . 198

Figure 35 LOF diagram for Case B . . . 199

Figure 36 LOF diagram for Case C . . . 200

Figure 37 PHF (Tx) alarm diagram . . . 217

Figure 38 PLF (Tx) alarm diagram . . . 220

Figure 39 SSF alarm examples . . . 226

Figure 40 SMISS alarm examples . . . 240

Figure 41 How to remove the FSU from a shelf. . . 245

Figure 42 How to remove the OTS-4000 air filter assembly . . . 267

Figure 43 How to remove the OTS-4000 air filter element. . . 268

Figure 44 How to remove/re-insert the Compact Flash on CCEP and CCMP cards . . . 273

(14)

Figure 45 HDS Shelf Fan Unit and Air Filter . . . 275

Figure 46 Reference network for Link Control troubleshooting . . . 282

Figure 47 Examples 1 and 2 for Link Control troubleshooting . . . 283

Figure 48 Example 3 for Link Control troubleshooting . . . 284

Figure 49 Example 4 for Link Control troubleshooting . . . 285

Figure 50 Link Control troubleshooting flowchart . . . 286

Figure 51 MIB replacement; basic steps. . . 304

Figure 52 MIBF alarm reporting . . . 305

Figure 53 Subrack-Config window . . . 306

Figure 54 Click Subrack name in the Navigation Tree . . . 307

Figure 55 MIB location in double-row shelf . . . 308

Figure 56 MIB Location in OCU Shelf . . . 309

Figure 57 MIB location in single-row shelf . . . 310

Figure 58 MIB locations in the MCU Shelf . . . 311

Figure 59 Storage location of MIB tool . . . 312

Figure 60 Removing a failed MIB . . . 313

Figure 61 Inserting the new MIB into the shelf . . . 314

Figure 62 MCU replacement flowchart . . . 316

Figure 63 “NE State” display . . . 317

(15)

15

List of Tables

Table 1 List of conventions used in this document . . . 18

Table 2 Document history . . . 19

Table 3 SURPASS hiT 7500 Equipment Alarms . . . 20

Table 4 SURPASS hiT 7500 Communication Alarms (Cont.) . . . 25

Table 5 SURPASS hiT 7500 Processing Error Alarms . . . 27

Table 6 SURPASS hiT 7500 Environmental Alarms . . . 27

Table 7 SURPASS hiT 7500 Security Alarms . . . 28

Table 8 SURPASS hiT 7500 Subsystem Alarms . . . 28

Table 9 OADM100U Fiber Interconnections (for up to a 4 x 4 PXC) . . . 113

Table 10 Summary Table for TIF Actors . . . 236

Table 11 First- and Second-generation 40G Cards . . . 263

Table 12 Last Block of OTS-4700 IP Address . . . 266

Table 13 Differences between Warm Start and Cold Start . . . 277

Table 14 Impact of Warm and Cold Start . . . 277

Table 15 Cold Start Affect on Traffic . . . 278

Table 16 Software download times to cards . . . 280

Table 17 Last Action Messages . . . 287

Table 18 Load Result messages on the Config DB Upload window . . . 294

Table 19 Load Result messages on the Config DB Download window . . . 295

Table 20 Load Result messages on both windows (Config DB Upload and Config DB Download) . . . 295

Table 21 Performance parameter for OCR10R, OCR10T and TEX cards, part 1 . . . 297

Table 22 Performance parameter for OCR10R, OCR10T and TEX cards, part 2 . . . 297

Table 23 Performance parameter for OTS-4000 cards, part 1 . . . 298

Table 24 Performance parameter for OTS-4000 cards, part 2 . . . 299

Table 25 Performance parameter for HDS transponder cards, part 1 . . . 300

Table 29 Monitored parameter definitions . . . 301

Table 30 MIB circuit board types . . . 303

(16)

(17)

17

1 Preface

This Troubleshooting Manual describes fault-clearing procedures to be performed in reaction to alarm events that may occur in the SURPASS hiT 7500 system.

1.1 Intended audience

This document is intended for anyone tasked with clearing fault conditions to restore normal system operation. Personnel performing these procedures must have general experience with long-haul optical DWDM networks as well as specific experience with Nokia Siemens Networks SURPASS hiT 7500 hardware components and network man-agement software. Personnel must also comply with all relevant safety practices whenever working with SURPASS hiT 7500 equipment. Please refer to the separate document named Safety Instructions (document number A42022-L5961-L082-*-7630).

1.2 Structure of this document

Alarm Lists

When a fault condition occurs, the relevant alarm notification will be generated and dis-played on craft terminal screens. All SURPASS hiT 7500 alarms are listed in the Alarm Lists in Chapter 2. The Alarm Lists are divided into separate tables that match the fault categories as presented on craft terminal screens. These categories are as follows: • Equipment alarms

• Communication alarms • Processing Error alarms • Environmental alarms • Security alarms • Subsystem alarms

Troubleshooting Instructions

For each entry in the Alarm Lists, specific fault-clearing procedures are contained in Chapter 3, Troubleshooting Instructions. Click the desired alarm name in the Alarm List to jump directly to the instructions for that alarm.

Described Features

g

Some feaures described in this document may not be available. To identify the features released for your project, please refer to the Release Notes delivered together with the product.

1.3 Symbols and conventions

(18)

Conventions used

Symbols used

g

Used for notes, tips, or additional information.

Representation Meaning

“Inverted commas” Window names and wizard titles are denoted with “inverted commas”.

Example: Open the “Help and Support Center” window. The “New Connection” wizard is displayed.

Bold Field names, buttons, and text on GUIs are denoted by bold type.

Example: Click Shutdown and then click OK to turn off the computer.

Italic Variables and file extensions are denoted by italic text.

Example: Enter 192.168.0.1 in the IP address field. Click OK to produce a .pdf rendition.

Courier Commands, screen output, file names and paths are denoted by courier font.

Example: # ping -t 192.168.0.1

<Angle brackets> Keyboard actions or place holders for distinct names or values are represented by enclosing them in <angle brackets>. If a file name is involved, the courier font will also be used.

Example: The naming convention for the log files is <NEname>.txt, where <NEName> is the name of the NE sending the messages. Press <CTRL>+<ALT><DEL> to open the task manager.

> Used for menu sequences.

Example: Click File > Print... to print the document.

Table 1 List of conventions used in this document

!

Caution: means that the reader must be careful. Loss of data or equipment damage are _{possible if caution is not exercised by the user.}

!

Warning: a warning symbol means danger. A situation exists that could cause bodily _{injury or death. Before working on any equipment, the user must be aware of the}

hazards involved with electrical circuitry and be familiar with standard practices for pre-venting accidents.

(19)

19

1.4 History of changes

1.5 Safety instructions

For safety instructions, see the Safety Instructions (SI) manual.

Issue Issue date Remarks

1 March 2008 Initial version 3 August 2008 Update for release 3.21.10

(20)

2 Alarm Lists

SURPASS hiT 7500 alarms are divided into the following categories:

• Equipment alarms: originate from specific hardware elements (e.g., traffic card, con-troller card, shelf, etc).

• Communication alarms: originate from termination points which represent a particu-lar function of the network.

• Processing Error alarms: originate from the NE software.

• Environmental alarms: originate from telemetry sensors that monitor condi-tions/events external to the NE.

• Security alarms: originate from the list of authorized users and passwords. • Subsystem alarms: originate from Main Agent MCU and Sub-Agent MCU cards.

2.1 Equipment alarms

Table 3 lists SURPASS hiT 7500 Equipment alarms. Click on any alarm name in the table to jump directly to the troubleshooting procedure for that alarm.

Alarm Name Alarm Message Text

ACTLP Active Loop (ACTLP)

AFEXRQ Air Filter Exchange Required (AFEXRQ)

ALRMPNLFAIL Alarm Panel Failure (ALRMPNLFAIL)

ALRMPNLMISS Alarm Panel Missing (ALRMPNLMISS)

APRM Automatic Power Reduction Mode (APRM)

APSBUF APS Backup Failed (APSBUF)

APSBUR APS Backup Running (APSBUR)

APSM APS Mismatch (APSM)

BTBM BTB Card Missing (BTBM)

CALIBRATION_FAIL Calibration Failure (CALIBRATION_FAIL)

CALIBRATION_FAILL Calibration Failure Line (CALIBRATION_FAILL)

CALIBRATION_FAILT1 Calibration Failure Tributary 1 (CALIBRATION_FAILT1)

CANFAIL CAN Bus Failure (CANFAIL)

CDL Coupler Drop Loss (CDL)

CFAIL Card Failure (CFAIL)

CFF Compact Flash Fail (CFF)

CHCNTMISM Channel Count Mismatch (CHCNTMISM)

CLOSSHDS Communication Loss to H73 (CLOSSH73)

(21)

21

CLOSSOTS Communication Loss to OTS (CLOSSOTS)

CMISM Card Mismatch (CMISM)

CMISS Card Missing (CMISS)

CONCABF OLI Connection Cable Fail (CONCABF)

CP Card Problem (CP)

CPHDS Communication Problem to H73 (CPH73)

CPOTS Connection Problem to OTS (CPOTS)

CTP Card Temperature Problem (CTP)

CTRLCABLP Control or Cabling Problem (CTRLCABLP)

CUPGVIOL1 Channel Upgrade Order Violation 1 (CUPGVIOL1)

DSPP DSP Problem (DSPP)

ETHSWFAIL Ethernet Switch Fail (ETHSWFAIL)

FAN_MAJOR Fan Major (FAN_MAJOR)

FAN_MINOR Fan Minor (FAN_MINOR)

FBSIG_ABSENT Feedback Absent (FBSIG_ABSENT)

FBSIG_DEGRADED Feedback Degraded (FBSIG_DEGRADED)

FIFOFLOWP Fifo Flow Problem (FIFOFLOWP)

FN11F Cooling Fan11 Failure (FN11F)

FN1CF Cooling Fan1 Comm Failure (FN1CF)

FN1M Cooling Fan 1 Missing (FN1M)

FNLOW Lower Cooling Fan Failure (FNLOW)

FNLOWM Lower Cooling Fan Missing (FNLOWM)

FNUPP Upper Cooling Fan Failure (FNUPP)

FNUPPM Upper Cooling Fan Missing (FNUPPM)

FREQNOTSUP Line Card Frequency Not Supported (FREQNOTSUP)

(22)

GNELOS Connection Loss to NE (GNELOS)

GTMMP Gain Tilt Monitor Module Problem (GTMMP)

GTP Gain Tilt Problem (GTP)

HDS_APSMISS HDS APS Missing (HDS_APSMISS)

HDSRECOVERMODE HDS Recover Mode (HDSRECOVERMODE)

ICP Internal Communication Problem (ICP)

ILOL Input Loss of Light (ILOL)

ILOL1 Input Loss of Light 1 (ILOL1)

IOPL Input Optical Power Too Low (IOPL)

ISLP Interstage Loss Problem (ISLP)

LNREFCLOCKP Line Ref Clock Problem (LNREFCLOCKP)

LOCNELOS Connection Loss to Local NE (LOCNELOS)

LOSADD Loss of Add Signal (LOSADD)

LOSIn1 Loss of Signal Input 1 (LOSIn1)

LSBFAIL Laser Safety Bus Failure (LSBFAIL)

LSS Loss of Sequence Synchronization (LSS)

MEASF Measurement Failure (MEASF)

MFNF Multiple Fans Failure (MFNF)

MIBF MIB Failure (MIBF) [OCU73 Subsystem]

MIBF MIB Flash Fail (MIBF) [other subsystems]

MIBM MIB Flash Missing (MIBM)

MIBS256 MIBS256 Required (MIBS256)

MTX_APSMISS MTX APS Missing (MTX_APSMISS)

MWBMP MWB Module Problem (MWBMP)

NLDC1 No Light Detected C1 (NLDC1)

NLDC2 No Light Detected C2 (NLDC2)

NOSYNCMSTR No Sync Master (NOSYNCMSTR)

NOTIMMSTR No Timing Master (NOTIMMSTR)

NQO Notification Queue Overflow (NQO)

(23)

23

NTPSVACCFAIL NTP Server Access Failed (NTPSVACCFAIL)

NVCDBMIG No VCDB Migration Possible (NVCDBMIG)

OBLOS Receiver Failure Booster (OBLOS)

OBTF Transmit Fail Booster (OBTF)

OLOL Output Loss of Light (OLOL)

OPLOS Receiver Failure Preamp (OPLOS)

OPTF Transmit Fail Preamp (OPTF)

OSAMP OSA Module Problem (OSAMP)

OSAPF OSA Power Fail (OSAPF)

OSCTD1 Transmit Degrade OSC1 (OSCTD1)

OSCTD2 Transmit Degrade OSC2 (OSCTD2)

OTS_APSMISS OTS APS Missing (OTS_APSMISS)

PbusF Power Bus Fail (PbusF)

PCBF PCB Bus Fail (PCBF)

PDIFF Power Differential Alarm (PDIFF)

PQMLOS Loss of Signal PQM (PQMLOS)

PQMMP PQM Module Problem (PQMMP)

PREEMPF Preemphase Fail (PREEMPF)

PU1TD, PU2TD, PU3TD, PU4TD, and PU5TD

Transmit Degrade Pump x (PUxTD)

PU1TF, PU2TF, PU3TF, PU4TF, and PU5TF

Transmit Fail Pump x (PUxTF)

PWCTLSUSP Power Control Suspicious (PWCTLSUSP)

PWR1, PWR2, PWR3, and PWR4 Power Problem x (PWRx) PWR12, PWR34, PWR13, and PWR24 Power problem xx (PWRxx)

PWREQFAIL Power Equalization Fail (PWREQFAIL)

REGEN_PAIR_UNAVAIL Regen Pair Unavailable (REGEN_PAIR_UNAVAIL)

REMNELOS Connection Loss to Remote NE (REMNELOS)

SABF Sub Address Board Failure (SABF)

SAMISS Partner Subagent Missing (SAMISS)

SBL Subband Loss (SBL)

SC_DISK_SPACE Flash Capacity Problem (SC_DISK_SPACE)

(24)

SFPMISM1, SFPMISM2, SFPMISM3, and SFPMISM4 SFP Mismatch x (SFPMISMx) SFPMISS1, SFPMISS2, SFPMISS3, and SFPMISS4 SFP Missing x (SFPMISSx) SFPMISS1, SFPMISS2, SFPMISS3, and SFPMISS4 SFP Missing Px (SFP_MISSx) SFPUNQ1, SFPUNQ2, SFPUNQ3, and SFPUNQ4 SFP Unqualified x (SFPUNQx)

SHLFADRCH Shelf Address Changed (SHLFADRCH)

SLH Span Loss High (SLH)

SLL Span Loss Low (SLL)

SPFAIL Swap Preparation Failure (SPFAIL)

SRCP Subrack Cooling Problem (SRCP)

STORAGEFAIL Storage Failure (STORAGEFAIL)

SUBSMISMHDS Subsystem Mismatch H73 (SUBSMISMH73)

SWDWNLD_OCU40FAIL SW Download OCU40 Fail (SWDWNLD_OCU40FAIL)

SWP Switch Problem (SWP)

SWP1, SWP2, SWP3, and SWP4

Switch Problem x (SWPx)

SYNCPROG Synchronization in Progress (SYNCPROG)

T3LOS No Valid T3 Signal (T3LOS)

TargetP Target Value Not Reached (TargetP)

TempHi Temperature too High (TempHi)

TempHiC Temperature Too High Critical (TempHiC)

TempP Temperature Problem (TempP)

TempPVOA Temperature Problem VOA (TempPVOA)

TempP1, TempP2, TempP3, and TempP4

Temperature Problem x (TempPx)

TempRegRun Temperature Regulation Running (TempRegRun)

TimP Timing Problem (TimP)

TSCh1TD Transmit Degrade TSCh1 (TSCh1TD)

(25)

25

2.2 Communication alarms

Table 4 lists SURPASS hiT 7500 Communication alarms. Click on any alarm name in the table to jump directly to the troubleshooting procedure for that alarm.

TSCh1TF Transmit Fail TSCh1 (TSCh1TF)

TSCh1TEMP Temperature Problem TSCh1 (TSCh1TEMP)

TWOSYNCMSTR Second Sync Master Detected (TWOSYNCMSTR)

TWOTIMMSTR Two Timing Masters (TWOTIMMSTR)

ULEDF ULed Fail (ULEF)

VOAP VOA Problem (VOAP)

VOAP# VOA # Problem (VOAPx)

VOLT Voltage Problem (VOLT)

VOLTL Voltage Problem Line (VOLTL)

VOLTT1, VOLTT2, VOLTT3, and VOLTT4

Voltage Problem Trib x (VOLTTx)

WSSMP WSS Module Problem (WSSMP)

XFP_MISM1 Mismatch Optical Module 1 (XFP_MISM1)

XFP_MISS1, XFP_MISS2, XFP_MISS3, and XFP_MISS4

Missing Optical Module x (XFP_MISSx)

XFP_QUAL1, XFP_QUAL2, XFP_QUAL3, and XFP_QUAL4

Unqualified Optical Module x (XFP_QUALx)

Table 3 SURPASS hiT 7500 Equipment Alarms (Cont.)

BDI Backward Defect Indication (BDI)

(26)

DMISM OSC Direction Mismatch (DMISM)

EOCI External Open Connection Indication (EOCI)

ETHNLNF Ethernet Link Fault (ETHNLNF)

EXC Bit Error Rate Excessive (EXC)

EXM Extension Header Mismatch (EXM)

FMISM Frequency Mismatch (FMISM)

GCCP GCC Connection Problem (GCCP)

HIPWRECD High Power Receive Detected (HIPWRECD)

HIPWRECF High Power Receive Failure (HIPWRECF)

LCK Locked Defect (LCK)

LFD Loss of Frame Delineation (LFD)

LOC Loss of Carrier (LOC)

LOF (OSCT cards)

Loss of Frame (LOF)

LOF (OCU cards) Loss of Frame (LOF)

LOFLOM Loss of Frame and Multiframe (LOFLOM)

LOM Loss of Multiframe (LOM)

LOS (OLI, OM20, and OSCT cards)

Loss of Signal (LOS)

LOS (OCU cards)

Loss of Signal (LOS)

LTC Loss of TCM (LTC)

MSIM Multiplex Structure Identifier Mismatch (MSIM)

OCI Open Connection Indication (OCI)

OPR Optical Power Received Too Low (OPR)

OSCVIM OSC Version Mismatch (OSCVIM)

PDHD Power Drift High Degrade (PDHD)

PDLD Power Drift Low Degrade (PDLD)

PDF (Rx) Power Drift Failure (PDF)

PDF (Tx) Power Drift Failure (PDF)

PHF Power too High Failure (PHF)

PHF (Rx) Power too High Failure (PHF)

PHF (Tx) Power too High Failure (PHF)

PLF Power too Low Failure (PLF)

PLF (Rx) Power too Low Failure (PLF)

(27)

27

2.3 Processing Error alarms

Table 5 lists SURPASS hiT 7500 Processing Error alarms. Click on any alarm name in the table to jump directly to the troubleshooting procedure for that alarm.

2.4 Environmental alarms

Table 6 lists SURPASS hiT 7500 Environmental alarms. Click on any alarm name in the table to jump directly to the troubleshooting procedure for that alarm.

PLF (Tx) Power too Low Failure (PLF)

PHF (OPA) Power too High Failure (PHF)

PLF (OPA) Power too Low Failure (PHF)

PLM Payload Mismatch (PLM)

RETHNLNF Remote Ethernet Link Fault (RETHNLNF)

SD (OLI and OSCT cards)

Signal Degraded (SD)

SD (OCU cards) Signal Degraded (SD)

SSF Server Signal Fail (SSF)

SYNCFail Synchronization Fail (SYNCFail)

TD (OLI cards) Transmit Degrade (TD)

TD (OCU cards) Transmit Degrade (TD)

TF (OLI and ODAxx cards)

Transmit Fail (TF)

TF (OCU cards) Transmit Fail (TF)

TIM (OSCT cards)

Trace Identifier Mismatch (TIM)

TIM (OCU cards) Trace Identifier Mismatch (TIM)

UPM User Payload Mismatch (UPM)

Table 4 SURPASS hiT 7500 Communication Alarms (Cont.) (Cont.)

SCP Storage Capacity Problem (SCP)

Table 5 SURPASS hiT 7500 Processing Error Alarms

EXT Telemetry Interface (Ext)

TIFACT TIF Activated Alarm (TIFACT)

(28)

2.5 Security alarms

Table 7 lists SURPASS hiT 7500 Security alarms. Click on any alarm name in the table to jump directly to the troubleshooting procedure for that alarm.

2.6 Subsystem alarms

Table 8 lists SURPASS hiT 7500 Subsystem alarms. Click on any alarm name in the table to jump directly to the troubleshooting procedure for that alarm.

EXCLOGIN Unsuccessful Logins Exceeded (EXCLOGIN)

PWEXP Password Expired (PWEXP)

PWEXPSON Password will expire soon (PWEXPSON)

Table 7 SURPASS hiT 7500 Security Alarms

SMISS Sub System Missing (SMISS)

SFAIL Sub System Failure (SFAIL)

(29)

29

3 Troubleshooting Instructions

3.1 Equipment Alarms

This section contains troubleshooting instructions for hiT 7500 Equipment alarms.

3.1.1 ACTLP

Troubleshooting instructions

1 Via the craft terminal, the user may set one or more interfaces on transponder cards

to loopback mode for test purposes. When this is done, the ACTLP alarm will be raised as a reminder that loopback(s) are active. The alarm will be raised by the MCU card managing the card in loopback. To view a list of a network element’s cur-rently-engaged loopbacks, start an Element Manager session for that network element. Then, open the Equipment View. Right-click on the Network Element Bar and select Configuration > Summary windows > Loopback. The resulting "Loop-back Summary-Config" window displays a list of all active loop"Loop-backs in this NE.

2 If the loopback(s) are no longer desired, deactivate them via the “Loopback

Summary-Config” window. When all loopbacks are disabled, the ACTLP alarm will clear.

3 If the alarm persists, contact your next higher level of technical support.

3.1.2 AFEXRQ

Alarm name Active Loop (ACTLP) Default severity Warning

Alarm object MCU-OCU, MCU-OCU40, and MCU-OCU73 cards General information

and causes

There is an active loopback on one or more cards in the NE managed by the MCU raising the alarm.

Alarm name Air Filter Exchange Required (AFEXRQ) Default severity Minor

Alarm object OTS-4000 shelves: alarm is raised by the shelf.

Other shelf types: alarm is raised by the Flow Sensor Unit (FSU).

General information and causes

The AFEXRQ alarm indicates that the shelf's air filter is clogged and needs to be replaced.

(30)

1 Troubleshooting instructions for the AFEXRQ alarm vary according to shelf type. Go

to the appropriate paragraph listed below that matches the shelf type raising the AFEXRQ alarm.

– 10G shelf: chapter 3.1.2.1.

– 40G (OTS-4000) shelf: chapter 3.1.2.2.

3.1.2.1 AFEXRQ alarm raised by 10G shelf

1 Dispatch personnel to the site raising the alarm. Refer to Figure 1. Open the shelf front door and remove the Air Filter Assembly from the shelf by sliding it straight out.

2 Carefully remove the old filter element from the assembly and discard.

3 With a soft cloth, remove any dust that may be present on the assembly’s metal

housing.

4 Insert a new Filter Element under the six clips provided. Make sure the side with the

manufacturer's logo is placed toward the top of the housing. Re-install the Air Filter Assembly in the shelf. Close and fully latch the shelf door.

5 To clear the AFEXRQ alarm, execute a new manual airflow measurement. To do so,

press the Lamp Test button at the top of the shelf, hold the button for at least five seconds, then release. The FSU will perform a new measurement. It requires 3 to 5 minutes for the measurement to complete and the AFEXRQ alarm to clear.

g

Note that during an FSU measurement (automatic or manual), the Lower Fan Unit is temporarily shut down, and the Upper Fan Unit is temporarily operated at its full speed. This is normal behavior during the measurement and does not indicate any problem with the Fan Units.

!

Caution!

The front door of the shelf must be latched in the closed position for the FSU to properly monitor the airflow through the filter and determine when to raise the AFEXRQ alarm.

(31)

31

Figure 1 Air Filter replacement in a 10G shelf

3.1.2.2 AFEXRQ alarm raised by 40G (OTS-4000) shelf

1 Dispatch personnel to the site raising the alarm. Perform the procedure in chapter

4.36 to replace the Air Filter in the OTS-4000 shelf raising the alarm.

2 Wait for the AFEXRQ alarm to clear. [The OTS-4000 shelf raises and clears the

AFEXRQ alarm based on the difference between air inlet temperature and the tem-perature of various components within the shelf. Therefore, after replacing the Air Filter, the alarm will clear only after the now-unimpeded airflow through the shelf returns the temperature difference to an acceptable level].

(32)

3 If any sympathetic temperature-related alarms (TempHi, TempHiC) were also raised

by this shelf due to the clogged filter, verify that they also clear after Air Filter replacement.

4 If all alarms have not cleared within 15 minutes, contact your next higher level of

technical support.

3.1.3 ALRMPNLFAIL

1 Remove the failed alarm panel from the front of the OTS-4000 shelf. Install a

replacement alarm panel.

3.1.4 ALRMPNLMISS

1 Install an alarm panel at the front of the OTS-4000 shelf raising the alarm. 2 If the alarm persists, contact your next higher level of technical support.

Alarm name Alarm Panel Failure (ALRMPNLFAIL) Default severity Major

Alarm object OTS-4000 shelf General information

and causes

The alarm panel on the indicated OTS-4000 shelf has failed.

Alarm name Alarm Panel Missing (ALRMPNLMISS) Default severity Major

Alarm object OTS-4000 shelf General information

and causes

The alarm panel on the indicated OTS-4000 shelf is not installed.

(33)

33

3.1.5 APRM

1 If an APRM alarm is raised, it means that OLI card raising the alarm has gone into

Automatic Power Reduction Mode. Troubleshooting instructions are as follows. First, troubleshoot any SBL or CP alarm that may be raised. This should also clear the APRM alarm. If there are no SBL or CP alarms raised, or if the APRM alarm persists after clearing them, continue to the next step.

2 Troubleshooting instructions for the APRM alarm vary according to network element

type. Go to the appropriate paragraph listed below that matches the network element raising the APRM alarm.

– OTTU: chapter 3.1.5.1. – OADM100U: chapter 3.1.5.2.

– OADM100N with CDAN and WBN: chapter 3.1.5.3. – OADM100N with CDN and WBAN: chapter 3.1.5.4.

3 If the APRM alarm persists after performing the appropriate procedure below,

contact your next higher level of technical support.

3.1.5.1 APRM in an OTTU

Figure 2 and Figure 3 show optical path diagrams for two OTT configurations: OTTU with OMDFIC + OMDFC, and OTTU with OMDFIC + OMD2IC. If an APRM alarm is raised, it will be raised by the Pre-amplifier OLI card as shown. Potential causes of an APRM alarm in these network element types are as follows:

• a problem with one of the fiber connections in the demux path as shown in the Figures (bad connection, damaged fiber, dirty connectors, etc).

• a defective OMDxx or OD card. • a disconnected PCB/CAN cable.

1 A card anomaly may be causing the APRM alarm. So first, execute a Warm Start on

any card raising an SBL or CP alarm. If alarms persist after recovery time (approx 3 minutes), execute a Cold Start. If alarms persist after recovery time (approx 3 min-Alarm name Automatic Power Reduction Mode (APRM)

Default severity Minor

Alarm object Pre-amplifier OLI cards General information

and causes

This alarm is raised when the indicated OLI card has entered Automatic Power Reduction Mode (an operational mode for laser power safety purposes).

At OADMs, traffic for drop and express channels will be interrupted as long as the APRM condition exists. The Wavelength Blocker cards at OADM nodes will set all channels to "blocked”.

(34)

34 A42022-L5961-L081-03-7619 Issue: 3 Issue date: August 2008 utes), the cause of the APRM alarm is likely a cabling problem or defective card. Dispatch personnel to the site and continue with the next step below.

2 Verify that all PCB/CAN cables are connected between shelves as specified in the

hiT 7500 Installation Manuals (ITMN and ICMA). If PCB/CAN connections were incorrect, the APRM alarm should clear when the cables are connected properly. If the alarm persists, continue with the next step below.

3 Refer to the drawing that matches your NE type ( Figure 2 or Figure 3). Verify that all fibers in the demux path are connected properly. Hint: SBL alarm(s) that are also raised in this network element will provide a clue about which fiber might be causing the problem as follows:

For OTTU with OMDFIC + OMDFC (Figure 2):

– If all installed ODA cards have raised an SBL alarm, then Fiber 1 is likely the problem.

– If only the ODAC1C2 and ODAC3C4 cards have raised an SBL alarm, then Fiber 2 is likely the problem.

– If only one of the installed ODA cards has raised an SBL alarm, then the input fiber to that card (Fiber 4, 5, 6, or 7) is likely the problem.

For OTTU with OMDFIC + OMD2IC (Figure 3):

– If all installed ODA cards have raised an SBL alarm, then Fiber 8 is likely the problem.

– If only one of the installed ODA cards has raised an SBL alarm, then the input fiber to that card (Fiber 11, 12, 13, or 14) is likely the problem.

If any cable is missing, bent/pinched, or improperly connected, correct the problem. The APRM alarm should clear when all correct connections are established. If the APRM alarm persists, disconnect fiber and clean connectors (start with the fiber identified as "most likely" according to the examples listed above). Re-connect the fiber and the APRM alarm should clear. If the alarm persists, replace the fiber cable with a spare. If the alarm persists after all fiber connections are ruled out as the cause, continue with the next step below

4 Contact your next higher level of technical support before proceeding. Replace any

(35)

35

(36)

Figure 3 APRM in an OTT that uses OMDFIC + OMD2IC

3.1.5.2 APRM in an OADM100U

Figure 4 shows the optical path diagram for one traffic side of an OADM100U. If an APRM alarm is raised, it will be raised by the Pre-amplifier OLI card as shown. Potential causes of an APRM alarm in this network element type are as follows:

• a problem with the fiber connection between the Pre-amplifier OLI card’s Out port and the CDU card’s In port (bad connection, damaged fiber, dirty connectors, etc). • a defective CDU card.

• a communication problem via the backplane bus between the Pre-amplifier OLI and the CDU.

• a disconnected PCB/CAN cable.

1 Dispatch personnel to the site raising the APRM alarm. Verify that all PCB/CAN

cables are connected between shelves as specified in the hiT 7500 Installation Manuals (ITMN and ICMA). If PCB/CAN connections were incorrect, the APRM

(37)

37 alarm should clear when the cables are connected properly. If the alarm persists, continue with the next step below.

2 Verify that the fiber cable designated in Figure 4 (between the Pre-amplifier OLI card and CDU card) is properly installed. If the cable is missing, bent/pinched, or improp-erly connected, correct the problem. The APRM alarm should clear when the correct connection is established:

If the APRM alarm persists, disconnect this fiber and clean all connectors. Re-connect the fiber and the APRM alarm should clear.

If the APRM alarm persists, replace the fiber cable with a spare. If the alarm persists after this fiber connection is ruled out as the cause, continue with the next step below

3 Contact your next higher level of technical support before proceeding. Replace the

CDU card. If the APRM alarm persists after card replacement, contact your next higher level of technical support.

g

Note the following for an APRM alarm at an OADM100U: – a CDL alarm will be raised by the CDU card.

– The drop-channel Booster-amp OLIs will each raise an OPLOS alarm. – The WBAU card on the other traffic side will set all channels to “blocked”.

(38)

Figure 4 APRM in an OADM100U

3.1.5.3 APRM in an OADM100N with CDAN and WBN

Figure 5 shows the optical path diagram for one traffic side of an OADM100N that uses CDAN and WBN cards. If an APRM alarm is raised, it will be raised by the Pre-amplifier OLI card as shown. Potential causes of an APRM alarm in this network element type are as follows:

• a problem with the fiber connection between the Pre-amplifier OLI card's Out port and the CDAN card's In port, or between the CDAN card's DrOut port and the OMDIFC card's 2C port (bad connection, damaged fiber, dirty connectors, etc). • a defective CDAN or OMDIFC card.

• a communication problem via the backplane bus between the Pre-amplifier OLI, CDAN, and OMDIFC.

(39)

39

1 Dispatch personnel to the site raising the APRM alarm. Verify that all PCB/CAN

cables are connected between shelves as specified in the hiT 7500 Installation Manuals (ITMN and ICMA). If PCB/CAN connections were incorrect, the APRM alarm should clear when the cables are connected properly. If the alarm persists, continue with the next step below.

2 Verify that the two fiber cables designated in Figure 5 (between the Pre-amplifier OLI card and CDAN and between the CDAN card and OMDIFC card) are properly installed.

If either cable is missing, bent/pinched, or improperly connected, correct the problem. The APRM alarm should clear when all correct connections are estab-lished.

If the APRM alarm persists, disconnect these fibers and clean connectors. Re-connect the fiber and the APRM alarm should clear. If the alarm persists, replace each fiber cable with a spare. If the alarm persists after all fiber connections are ruled out as the cause, continue with the next step below

3 Contact your next higher level of technical support before proceeding. Replace the

OMDIFC card and see if the alarm clears. If the alarm does not clear, replace the CDAN card.

(40)

Figure 5 APRM in an OADM100N with CDAN and WBN

3.1.5.4 APRM in an OADM100N with CDN and WBAN

Figure 6 shows the optical path diagram for one traffic side of an OADM100N that uses CDN and WBAN cards. If an APRM alarm is raised, it will be raised by the Pre-amplifier OLI card as shown. Potential causes of an APRM alarm in this network element type are as follows:

• a problem with the fiber connection between the Pre-amplifier OLI card and the CDN card.

• a problem with the fiber connection between the CDN card and the OMDIFC card. • a problem with the fiber connection between the CDN card and WBAN card. (This

is a duplex fiber carrying express traffic and a security signal. This duplex fiber is connected between the CDN and the WBAN card on the other traffic side of this OADM100N).

• an anomaly with the WBAN card's security signal or a failure of the laser diode on the WBAN that transmits the security signal.

(41)

41 • a communication problem via the backplane bus between the Pre-amplifier OLI,

CDN, and OMDIFC.

• a disconnected PCB/CAN cable.

g

Even if there are no drop channels at an OADM100N, APRM will still be activated if there is a problem with the interconnection between the CDN and the OMDIFC cards, or if there is a shelf backplane problem that affects OMDIFC card communi-cation.

1 Refer to Figure 7. For the OLITPNC card that has APRM activated, determine the channels that are entering the card. To do so, open the “OCh Monitor Points - Mea-surement” window for the OPAPC that monitors this OLITPNC (OPAPC1 in Figure 7). In the Display OCh Monitor Point drop-down box, select “Line Rx”. Make a record of all channels that are shown by this OPAPC to enter the OLITPNC.

2 Temporarily disable APRM according to the instructions in chapter 3.1.5.9.

3 Determine which channels are Express and which are Drop. To do so, open the

Cross-Connection Map for this OADM100N by right-clicking on the Functional View's Network Element Bar and selecting Configuration > Cross Connections. Make a record of which channel are Express and which are Drop.

4 From Step 3, it is known which channels are Express. Open the “OCh Monitor Points

- Measurement” window. To do so, right-click on the OPAPC Card Replica in the Equipment View (the OPAPC that monitors the OLITBNC Booster amplifier on the

other traffic side (i.e., OPAPC2 in Figure 7) and select OCh Monitor Points >

Mea-surement. Select Line Tx from the drop-down list at the top of the screen. Make a

note of how many of the Express channels are visible to this OPAPC. All? None?

5 From Step 3, it is known which channels are Drop. Open the “Traffic Configuration”

window for the ODA20 cards that handle the Drop channels. Make a note of how many of the Drop channels are present at the respective ODA20 inputs. All? None?

6 After gathering the information from Steps 1 through 5, refer to Figure 8 and Figure 9. These Figures will enable you to isolate the problem to Connection A, B, or C. Re-enable APRM according to the instructions in chapter 3.1.5.9 and dispatch person-nel to the site for further troubleshooting procedures as follows:

– If previous steps indicate that the Security connection is at fault, go to chapter

3.1.5.5.

– If previous steps indicate that Connection A is at fault, go to chapter 3.1.5.6. – If previous steps indicate that Connection B is at fault, go to chapter 3.1.5.7. – If previous steps indicate that Connection C is at fault, go to chapter 3.1.5.8.

!

Caution!

Since there are a large number of potential APRM causes with CDN and WBAN, the fault isolation procedures are more complex. Carefully perform the procedures below to identify and correct the problem.

(42)

(43)

43

Figure 7 Diagram for APRM troubleshooting in OADM100N with CDN and WBAN

(44)

(45)

45

(46)

3.1.5.5 If Security cable is causing the APRM alarm

Follow the instructions below if previous procedures indicated that a problem with the Security cable connection is causing the APRM alarm.

1 Disable APRM according to the instructions in chapter 3.1.5.9. With APRM disabled, ensure that all laser safety practices are followed!

2 Disconnect the duplex fiber between the CDN and WBAN. Disconnect at the WBAN

end. Using a fiber jumper with LC connector, measure the output power level from the "SecOut" port of the WBAN. Is the power -9 dBm or higher?

– Yes: skip to step 5.

– No: continue to the next step.

3 Clean the connector inside the WBAN card. Measure the power again. Is the power

-9 dBm or higher? – Yes: skip to step 5.

4 Replace the WBAN card with a spare and re-connect all fibers. Did the APRM alarm

clear?

– Yes: alarm cleared. Procedure complete. END.

– No: contact your next higher level of technical support. Do NOT continue with the next steps. END.

5 Re-connect the fiber to the WBAN. (Note: inspect the fiber connector that is being

connected to the "SecOut" port and if necessary, clean it prior to re-connecting it to WBAN. The duplex fiber connector may need to be separated prior to using the fiber inspection scope. Also, an adaptor may be necessary to open the dust cap).

6 Disconnect the duplex fiber at the CDN end. Measure the optical power out of the

fiber that was connected to the SecIn connector of the CDN card. Use a coupler and a jumper to connect the fiber to the power meter. Is the power level -9 dBm or higher?

7 If possible, clean the fiber connector (from step 6) using the adaptor to open the

pro-tective cover. Then, re-measure the optical power. Is the power level -9 dBm or higher?

8 Replace the duplex fiber between the CDN and WBAN with an inspected and

cleaned spare. Did the APRM alarm clear?

– Yes: alarm cleared. Procedure complete. END. – No: continue to the next step.

9 Disconnect the fiber and the CDN end.

10 Clean the connector inside the CDN’s SecIn port. Re-connect the fiber to the CDN

card. Did the APRM alarm clear?

(47)

47

11 Replace the CDN card with a spare and re-connect all fibers. Did the APRM alarm

clear?

12 Replace the OMDIFC card with a spare and re-connect all fibers. Did the APRM

alarm clear?

13 Replace the Pre-amplifier OLI card with a spare and re-connect all fibers. Did the

APRM alarm clear?

– No: contact your next higher level of technical support. END.

3.1.5.6 If Cable A is causing the APRM alarm

Follow the instructions below if previous procedures indicated that a problem with Cable A is causing the APRM alarm.

2 Start an Element Manager session for the OADM100N via the Craft Terminal. Open

the Equipment View. Right-click on the OLITPNC card that is raising the APRM alarm and select Traffic > Measurement. On the resulting "Traffic Measurement" window, read the OLI card's Stage III output power and record it for future reference.

3 Disconnect the fiber at the CDN "In" port. Clean the fiber and measure the power

level. Is the measured power approximately the same value as the OLI Stage III output power from step 2? (Allow a tolerance of +/- 1.5 dB).

4 Use a fiber test jumper with LC connector to measure the optical power from the

Pre-amplifier OLI’s "Line Out" port. Is the measured power approximately the same value as the OLI Stage III output power from step 2? (Allow a tolerance of +/- 1.5 dB).

5 Inspect and, if necessary, clean the connector inside the pre-amp OLI. Measure the

output power again. Is the measured power approximately the same value as the OLI Stage III output power from step 2? (Allow a tolerance of +/- 1.5 dB)

6 Replace the Pre-amplifier OLI card with a spare and re-connect all fibers. Did the

APRM alarm clear?

– No: contact your next higher level of technical support. Do NOT continue with the next steps. END.

(48)

7 Inspect and, if necessary, clean and re-connect the fiber at OLI Pre-amplifier end.

Measure the power again from the CDN end. Is the measured power approximately the same value as the OLI Stage III output power from step 2? (Allow a tolerance of +/- 1.5 dB).

– Yes: continue to the next step. – No: skip to step 9.

8 Inspect and if necessary, clean the connector at "In" port of the CDN card.

Re-connect the fiber at the CDN end. Did the APRM alarm clear? – Yes: alarm cleared. END.

– No: skip to step 10.

9 Replace the fiber between the Pre-amplifier OLI and the CDN with an inspected and

cleaned spare. Did the APRM alarm clear? – Yes: alarm cleared. END.

10 What type of cross-connections does this traffic side have?

– only express connections (no drop): go to Cable B instructions is chapter

3.1.5.7.

– only drop connections (no express): go to Cable C instructions in chapter

3.1.5.8.

– a mixture of drop and express: continue to the next step.

11 Replace the CDN card with a spare and re-connect all fibers. Did the APRM alarm

clear?

– No: contact your next higher level of technical support. END.

3.1.5.7 If Cable B is causing the APRM alarm

Follow the instructions below if previous procedures indicated that a problem with Cable B is causing the APRM alarm.

2 Disconnect both ends of the duplex fiber between the CDN (Out/SecIn) and the

WBAN (In/SecOut). Inspect and, if necessary, clean all connectors on the duplex fiber jumper at both ends. Re-connect the fiber. Did the APRM alarm clear? – Yes: alarm cleared. Procedure complete. END.

3 Disconnect the duplex cable again. Clean the connectors inside the CDN and

WBAN cards. Re-connect the duplex cable. Did the APRM alarm clear? – Yes: alarm cleared. Procedure complete. END.

4 Start an Element Manager session for the OADM100N via the Craft Terminal. Open

the Equipment View. Right-click on the OLITPNC card that is raising the APRM alarm and select Traffic > Measurement. On the resulting "Traffic Measurement" window, read the OLI card's Stage III output power and record it for future reference.

Troubleshooting_Manual[1].pdf

Troubleshooting Manual (TSMN)

A42022-L5961-L081-03-7619

f Important Notice on Product Safety

Statements of compliance

Table of Contents

List of Figures

List of Tables

1 Preface

1.1

Intended audience

1.2

Structure of this document

g

1.3

Symbols and conventions

g

!

!

1.4

History of changes

1.5

Safety instructions

2 Alarm Lists

2.1

Equipment alarms

2.2

Communication alarms

2.3

Processing Error alarms

2.4

Environmental alarms

2.5

Security alarms

2.6

Subsystem alarms

3 Troubleshooting Instructions

3.1

Equipment Alarms

3.1.1

ACTLP

3.1.2

AFEXRQ

3.1.2.1

AFEXRQ alarm raised by 10G shelf

g

!

3.1.2.2

AFEXRQ alarm raised by 40G (OTS-4000) shelf

3.1.3

ALRMPNLFAIL

3.1.4

ALRMPNLMISS

3.1.5

APRM

3.1.5.1

APRM in an OTTU

3.1.5.2

APRM in an OADM100U

g

3.1.5.3

APRM in an OADM100N with CDAN and WBN

3.1.5.4

APRM in an OADM100N with CDN and WBAN

g

!

3.1.5.5

If Security cable is causing the APRM alarm

3.1.5.6

If Cable A is causing the APRM alarm

3.1.5.7

If Cable B is causing the APRM alarm