Troubleshooting_Manual[1].pdf

SURPASS hiT 7500 valid as of 3.21.10 Troubleshooting Manual (TSMN)

Issue: 3

Issue date: August 2008

A42022-L5961-L081-03-7619

Troubleshooting Manual (TSMN)

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 DOCUMENTATION 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. Copyright © Nokia Siemens Networks 2008. All rights reserved.

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 Spannung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen. Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen 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.

2

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

Troubleshooting Manual (TSMN)

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 equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

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 problems which subsequently arise rests with the party responsible for deviating from the installation specifications.

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

3

Troubleshooting Manual (TSMN)

4

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

Troubleshooting Manual (TSMN)

Table of Contents This document has 335 pages. 1 1.1 1.2 1.3 1.4 1.5

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Structure of this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symbols and conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . History of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17 17 17 17 19 19

2 2.1 2.2 2.3 2.4 2.5 2.6

Alarm Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Communication alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing Error alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Environmental alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subsystem alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20 20 25 27 27 28 28

3 3.1 3.1.1 3.1.2 3.1.2.1 3.1.2.2 3.1.3 3.1.4 3.1.5 3.1.5.1 3.1.5.2 3.1.5.3 3.1.5.4 3.1.5.5 3.1.5.6 3.1.5.7 3.1.5.8 3.1.5.9 3.1.6 3.1.7 3.1.8 3.1.9 3.1.10 3.1.11 3.1.12 3.1.13 3.1.14 3.1.15 3.1.16 3.1.17

Troubleshooting Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Equipment Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACTLP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AFEXRQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AFEXRQ alarm raised by 10G shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AFEXRQ alarm raised by 40G (OTS-4000) shelf . . . . . . . . . . . . . . . . . . . . ALRMPNLFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ALRMPNLMISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APRM in an OTTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APRM in an OADM100U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APRM in an OADM100N with CDAN and WBN . . . . . . . . . . . . . . . . . . . . . APRM in an OADM100N with CDN and WBAN . . . . . . . . . . . . . . . . . . . . . If Security cable is causing the APRM alarm . . . . . . . . . . . . . . . . . . . . . . . If Cable A is causing the APRM alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . If Cable B is causing the APRM alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . If Cable C is causing the APRM alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to enable/disable APRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APSBUF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APSBUR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BTBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALIBRATION_FAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALIBRATION_FAILL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALIBRATION_FAILT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALIBRATION_FAILT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALIBRATION_FAILT3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CALIBRATION_FAILT4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CANFAIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

29 29 29 29 30 31 32 32 33 33 36 38 40 46 47 48 49 50 52 53 53 54 54 55 55 56 56 57 57 58

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

5

Troubleshooting Manual (TSMN)

3.1.18 3.1.18.1 3.1.18.2 3.1.18.3 3.1.18.4 3.1.18.5 3.1.18.6 3.1.19 3.1.20 3.1.21 3.1.22 3.1.23 3.1.24 3.1.25 3.1.26 3.1.26.1 3.1.26.2 3.1.27 3.1.28 3.1.29 3.1.30 3.1.31 3.1.31.1 3.1.32 3.1.33 3.1.34 3.1.35 3.1.36 3.1.37 3.1.38 3.1.39 3.1.40 3.1.41 3.1.42 3.1.43 3.1.44 3.1.45 3.1.46 3.1.47 3.1.48 3.1.49 3.1.50 3.1.51 3.1.52 3.1.53 3.1.54 3.1.55

6

CFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 CFAIL raised by OSCT slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 CFAIL raised by SMU slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 CFAIL raised by OCR10T-LH or TEX-LH slot . . . . . . . . . . . . . . . . . . . . . . . 61 CFAIL raised by 40G card slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 CFAIL raised by FSU slot in MCU-Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 CFAIL raised by other slot types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 CFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 CHCNTMISM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 CLOSSHDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 CLOSSOTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 CMISM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 CMISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 CONCABF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Special procedure “A” for CP alarm raised by PUMP card . . . . . . . . . . . . . 71 Special procedure “B” for CP alarm raised by PUMP card . . . . . . . . . . . . . 71 CPHDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 CPOTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 CTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 CTRLCABLP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 CUPGVIOL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Channel Upgrade Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 DSPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 ETHSWFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 FAN_MAJOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 FAN_MINOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 FBSIG_ABSENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 FBSIG_DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 FIFOFLOWP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 FN11F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 FN12F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 FN21F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 FN22F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 FN31F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 FN32F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 FN1CF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 FN2CF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 FN3CF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 FN1M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 FN2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 FN3M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 FNLOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 FNLOWM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 FNUPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 FNUPPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 FREQNOTSUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

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

Troubleshooting Manual (TSMN)

3.1.55.1 3.1.55.2 3.1.56 3.1.57 3.1.58 3.1.58.1 3.1.59 3.1.60 3.1.61 3.1.62 3.1.63 3.1.64 3.1.65 3.1.66 3.1.67 3.1.68 3.1.69 3.1.70 3.1.71 3.1.72 3.1.73 3.1.74 3.1.75 3.1.76 3.1.77 3.1.78 3.1.79 3.1.80 3.1.81 3.1.82 3.1.83 3.1.84 3.1.85 3.1.86 3.1.87 3.1.88 3.1.89 3.1.90 3.1.91 3.1.92 3.1.93 3.1.94 3.1.95 3.1.96 3.1.97 3.1.98 3.1.99

FREQNOTSUP raised by an OTS-4520 (TDCM) card . . . . . . . . . . . . . . . . 93 FREQNOTSUP raised by an OTS-4xxx V3 card . . . . . . . . . . . . . . . . . . . . 94 GNELOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 GTMMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 GTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Hints for multiple GTP alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 HDS_APSMISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 HDSRECOVERMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 ICP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 ILOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 ILOL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 ILOL2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 ILOL3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 IOPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 ISLP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 LNREFCLOCKP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 LOCNELOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 LOSADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 LOSIn1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 LOSIn2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 LOSIn3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 LOSIn4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 LSBFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 LSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 MEASF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 MFNF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 MIBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 MIBF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 MIBM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 MIBS256 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 MTX_APSMISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 MWBMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 NLDC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 NLDC2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 NOSYNCMSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 NOTIMMSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 NQO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 NTPSVACCFAIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 NVCDBMIG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 OBLOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 OBTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 OLOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 OPLOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 OPTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 OSAMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 OSAPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 OSCTD1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

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

7

Troubleshooting Manual (TSMN)

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 3.1.144 TSCh1TD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

8

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

Troubleshooting Manual (TSMN)

3.1.145 3.1.146 3.1.147 3.1.148 3.1.149 3.1.150 3.1.151 3.1.152 3.1.153 3.1.154 3.1.155 3.1.156 3.1.157 3.1.158 3.1.159 3.1.160 3.1.161 3.1.162 3.1.163 3.1.164 3.1.165 3.1.166 3.1.167 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8 3.2.9 3.2.10 3.2.11 3.2.12 3.2.13 3.2.14 3.2.15 3.2.15.1 3.2.15.2 3.2.15.3 3.2.16 3.2.17 3.2.18 3.2.19 3.2.19.1

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

TSCh2TD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSCh3TD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSCh4TD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSCh1TF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSCh2TF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSCh3TF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSCh4TF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSCh1TEMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSCh2TEMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSCh3TEMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSCh4TEMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TWOSYNCMSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TWOTIMMSTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ULEDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOAP# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOLT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOLTL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOLTT1, VOLTT2, VOLTT3, and VOLTT4. . . . . . . . . . . . . . . . . . . . . . . . WSSMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XFP_MISM1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XFP_MISS1, XFP_MISS2, XFP_MISS3, and XFP_MISS4 . . . . . . . . . . . XFP_QUAL1, XFP_QUAL2, XFP_QUAL3, and XFP_QUAL4 . . . . . . . . . Communication Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DMISM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EOCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ETHNLNF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EXC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EXM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMISM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GCCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIPWRECD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HIPWRECF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LOC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LOF (OSCT cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LOF (OCU cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case A: OTU Connection Termination Point LOF . . . . . . . . . . . . . . . . . . Case B: Client to Line LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case C: Line to Client LOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LOFLOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LOS (OLI, OM20, and OSCT cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LOS (OCU cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client In LOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

172 172 173 173 173 174 175 175 175 176 177 177 178 179 179 180 181 181 182 182 183 184 184 185 185 187 187 189 189 190 190 191 191 192 192 193 194 196 196 198 199 200 200 202 202 203 204

9

Troubleshooting Manual (TSMN)

10

3.2.19.2 3.2.20 3.2.21 3.2.22 3.2.23 3.2.24 3.2.25 3.2.26 3.2.27 3.2.28 3.2.29 3.2.30 3.2.31 3.2.32 3.2.33 3.2.34 3.2.35 3.2.35.1 3.2.36 3.2.37 3.2.38 3.2.39 3.2.40 3.2.41 3.2.42 3.2.43 3.2.44 3.2.45 3.2.46 3.2.47 3.2.48 3.2.49 3.3 3.3.1 3.4 3.4.1 3.4.2 3.5 3.5.1 3.5.2 3.5.3 3.6 3.6.1 3.6.2

Line In LOS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205 LTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 MSIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 OCI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207 OPR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 OSCVIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 PDHD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 PDLD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 PDF (Rx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 PDF (Tx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 PHF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 PHF (Rx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 PHF (Tx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 PLF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 PLF (Rx). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 PLF (Tx) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 PHF (OPA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Special Procedure for OPAPC connected to a Pre-amplifier OLI . . . . . . . 221 PLF (OPA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 PLM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 RETHNLNF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 SD (OLI and OSCT cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 SD (OCU cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 SSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 SYNCFail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 TD (OLI cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 TD (OCU cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 TF (OLI and ODAxx cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 TF (OCU cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 TIM (OSCT cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 TIM (OCU cards) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 UPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Processing Error Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 SCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Environmental Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 EXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 TIFACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Security Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 EXCLOGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 PWEXP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 PWEXPSON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Subsystem Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 SMISS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 SFAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

4 4.1 4.2

Card Replacement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 CAX card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 CDN, CDU, CDAN cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

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

Troubleshooting Manual (TSMN)

4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.19 4.20 4.21 4.22 4.23 4.24 4.25 4.26 4.27 4.28 4.29 4.30 4.31 4.32 4.33 4.34 4.35 4.36 4.37 4.38 4.39 4.40 4.40.1 4.40.2 4.40.3 4.41 4.42 4.43 4.44 4.45

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

FSU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MCU card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MIB circuit board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NEAP Circuit Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OCR10 and TEX cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ODA20, ODA20 cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OLI cards (except Add-OLI and Drop-OLI) . . . . . . . . . . . . . . . . . . . . . . . . Add-OLI cards (used in ADU or ADX: Shelf 2, Slot 013) . . . . . . . . . . . . . Drop-OLI cards (used in ADU or ADX: Shelf 2, Slots 007 and 010) . . . . OM10, OM20 cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMDFC, OMDFIC, OMDIFC cards (at OTTU) . . . . . . . . . . . . . . . . . . . . . OMDFC or OMDFIC cards (at OADM100U). . . . . . . . . . . . . . . . . . . . . . . OMDIFC cards (at OADM100N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMDFC card (when used for sub-band compensation) . . . . . . . . . . . . . . OPAPC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OSCTUT, OSCTUI cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PUMP cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PQMC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RPUMPC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SMU card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TSC card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UDCM Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VOA2 card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WBAN card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WBAU card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WBN card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WSSC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SFP and XFP modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OTS-4400, OTS-40xx cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OTS-4520 card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OTS-4540 card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OTS-4700 Controller card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OTS-4000 Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MTS Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OCU Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCEP card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCMP card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCMP replacement due to CP alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCMP replacement due to MIBF alarm . . . . . . . . . . . . . . . . . . . . . . . . . . CCMP replacement due to Loss of Communication . . . . . . . . . . . . . . . . . Compact Flash Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCSP card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HDS Transponder cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HDS Shelf Air Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How to enable/disable APRM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

244 245 246 246 247 247 248 248 249 249 250 250 251 251 252 252 253 253 254 255 255 256 257 258 259 259 260 261 261 262 263 264 265 267 268 269 270 270 270 270 271 272 274 274 274 275

11

Troubleshooting Manual (TSMN)

5 5.1 5.2 5.3 5.4 5.5

Cold Start and Warm Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Differences between Warm and Cold Start . . . . . . . . . . . . . . . . . . . . . . . . 277 Impact of Warm and Cold Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Use of Warm and Cold Start for troubleshooting . . . . . . . . . . . . . . . . . . . . 278 Time required for software download to cards . . . . . . . . . . . . . . . . . . . . . . 280 Fault LED behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

6 6.1

Link Control Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Potential Symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

7 7.1 7.2

Last Action and Load Result Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . 287 List of Last Action Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 List of Load Result Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

8 8.1 8.2 8.3 8.4

Performance Monitoring and TCAs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 OCU transponder card Performance Parameters . . . . . . . . . . . . . . . . . . . 297 OTS-4000 transponder cards Performance Parameters . . . . . . . . . . . . . . 298 HDS transponder card Performance Parameters . . . . . . . . . . . . . . . . . . . 300 Monitored parameter definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301

9 9.1 9.1.1 9.1.1.1 9.1.1.2 9.1.2 9.1.3 9.1.4 9.2 9.2.1 9.2.2 9.2.2.1 9.2.2.2 9.3

MIB, MCU, and SAB replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 MIB circuit board replacement procedures . . . . . . . . . . . . . . . . . . . . . . . . 303 Determine location of MCU raising the MIBF alarm. . . . . . . . . . . . . . . . . . 304 MCU-MTS, MCU-OCU, MCU-OCU40, and MCU-OCU73 location . . . . . . 306 MCU-CNE, MCU-TL1GNE, and MCU-Q3GNE location . . . . . . . . . . . . . . 306 Determine location of the failed MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Remove failed MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Install new MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 MCU replacement procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 MCU replacement if MIBS256 is used . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 MCU replacement if MIBS32 or MIBS32-2 is used . . . . . . . . . . . . . . . . . . 315 MCU-CNE and Stand-alone MCU replacement (for MIBS32/MIBS32-2) . 317 Sub-agent MCU replacement (for MIBS32/MIBS32-2) . . . . . . . . . . . . . . . 318 SAB replacement procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

10 10.1 10.2 10.3 10.4

Packing equipment for return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Requirements for packing and packaging . . . . . . . . . . . . . . . . . . . . . . . . . 320 Container requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Labeling requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

11

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

12

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

Troubleshooting Manual (TSMN)

List of Figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36 Figure 37 Figure 38 Figure 39 Figure 40 Figure 41 Figure 42 Figure 43 Figure 44

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

Air Filter replacement in a 10G shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 APRM in an OTT that uses OMDFIC + OMDFC . . . . . . . . . . . . . . . . . . 35 APRM in an OTT that uses OMDFIC + OMD2IC. . . . . . . . . . . . . . . . . . 36 APRM in an OADM100U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 APRM in an OADM100N with CDAN and WBN . . . . . . . . . . . . . . . . . . 40 APRM in an OADM100N with CDN and WBAN . . . . . . . . . . . . . . . . . . 42 Diagram for APRM troubleshooting in OADM100N with CDN and WBAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Isolating the APRM-causing fault in an OADM100N (1 of 2) . . . . . . . . . 44 Isolating the APRM-causing fault in an OADM100N (2 of 2) . . . . . . . . . 45 Diagram for CDL alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Identify the nearest upstream card . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 MTS shelf Lower Fan Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 MTS shelf Upper Fan Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 GNELOS alarm causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 “Connection Loss to GNE” alarm causes. . . . . . . . . . . . . . . . . . . . . . . . 98 Arrangement of OPAPCs in a network . . . . . . . . . . . . . . . . . . . . . . . . 100 Determining which OPAPC to Warm Start. . . . . . . . . . . . . . . . . . . . . . 100 Multiple GTP alarm diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 OLI card interstage devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Reference diagram for LOSADD alarm . . . . . . . . . . . . . . . . . . . . . . . . 112 Fiber connections from OLI cards to OPAPC . . . . . . . . . . . . . . . . . . . 125 OBLOS alarm with single fiber cut . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 OBLOS alarm with double fiber cut . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Interstage devices for OBLOS alarm . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Example causes of an OPLOS alarm . . . . . . . . . . . . . . . . . . . . . . . . . 136 PQMLOS alarm diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 SBL alarm diagram for OTTU with OMDFIC + OMDFC . . . . . . . . . . . 153 SBL alarm diagram for OTTU with OMDFIC + OMD2IC . . . . . . . . . . . 154 SBL alarm diagram for OADM100U. . . . . . . . . . . . . . . . . . . . . . . . . . . 155 SBL alarm diagram for OADM100N. . . . . . . . . . . . . . . . . . . . . . . . . . . 156 BDI alarm diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Reference network for EOCI alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 LCK alarm diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 LOF diagram for Case A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 LOF diagram for Case B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 LOF diagram for Case C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 PHF (Tx) alarm diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 PLF (Tx) alarm diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 SSF alarm examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 SMISS alarm examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 How to remove the FSU from a shelf. . . . . . . . . . . . . . . . . . . . . . . . . . 245 How to remove the OTS-4000 air filter assembly . . . . . . . . . . . . . . . . 267 How to remove the OTS-4000 air filter element. . . . . . . . . . . . . . . . . . 268 How to remove/re-insert the Compact Flash on CCEP and CCMP cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

13

Troubleshooting Manual (TSMN)

Figure 45 Figure 46 Figure 47 Figure 48 Figure 49 Figure 50 Figure 51 Figure 52 Figure 53 Figure 54 Figure 55 Figure 56 Figure 57 Figure 58 Figure 59 Figure 60 Figure 61 Figure 62 Figure 63 Figure 64

14

HDS Shelf Fan Unit and Air Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Reference network for Link Control troubleshooting. . . . . . . . . . . . . . . 282 Examples 1 and 2 for Link Control troubleshooting . . . . . . . . . . . . . . . 283 Example 3 for Link Control troubleshooting . . . . . . . . . . . . . . . . . . . . . 284 Example 4 for Link Control troubleshooting . . . . . . . . . . . . . . . . . . . . . 285 Link Control troubleshooting flowchart . . . . . . . . . . . . . . . . . . . . . . . . . 286 MIB replacement; basic steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 MIBF alarm reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 Subrack-Config window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 Click Subrack name in the Navigation Tree . . . . . . . . . . . . . . . . . . . . . 307 MIB location in double-row shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 MIB Location in OCU Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 MIB location in single-row shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310 MIB locations in the MCU Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311 Storage location of MIB tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Removing a failed MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313 Inserting the new MIB into the shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . 314 MCU replacement flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 “NE State” display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317 Set NE to Idle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

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

Troubleshooting Manual (TSMN)

List of Tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31

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

List of conventions used in this document . . . . . . . . . . . . . . . . . . . . . . 18 Document history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 SURPASS hiT 7500 Equipment Alarms . . . . . . . . . . . . . . . . . . . . . . . 20 SURPASS hiT 7500 Communication Alarms (Cont.) . . . . . . . . . . . . . . 25 SURPASS hiT 7500 Processing Error Alarms . . . . . . . . . . . . . . . . . . . 27 SURPASS hiT 7500 Environmental Alarms . . . . . . . . . . . . . . . . . . . . . 27 SURPASS hiT 7500 Security Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . 28 SURPASS hiT 7500 Subsystem Alarms . . . . . . . . . . . . . . . . . . . . . . . . 28 OADM100U Fiber Interconnections (for up to a 4 x 4 PXC) . . . . . . . . 113 Summary Table for TIF Actors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 First- and Second-generation 40G Cards . . . . . . . . . . . . . . . . . . . . . . 263 Last Block of OTS-4700 IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . 266 Differences between Warm Start and Cold Start . . . . . . . . . . . . . . . . 277 Impact of Warm and Cold Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277 Cold Start Affect on Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Software download times to cards . . . . . . . . . . . . . . . . . . . . . . . . . . . 280 Last Action Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Load Result messages on the Config DB Upload window . . . . . . . . . 294 Load Result messages on the Config DB Download window . . . . . . . 295 Load Result messages on both windows (Config DB Upload and Config DB Download) . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 Performance parameter for OCR10R, OCR10T and TEX cards, part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Performance parameter for OCR10R, OCR10T and TEX cards, part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 Performance parameter for OTS-4000 cards, part 1 . . . . . . . . . . . . . 298 Performance parameter for OTS-4000 cards, part 2 . . . . . . . . . . . . . 299 Performance parameter for HDS transponder cards, part 1 . . . . . . . . 300 Performance parameter for HDS transponder cards, part 2 . . . . . . . . 300 Performance parameter for HDS transponder cards, part 3 . . . . . . . . 301 Performance parameter for HDS transponder cards, part 4 . . . . . . . . 301 Monitored parameter definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 MIB circuit board types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 Location syntax of MIBF alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

15

Troubleshooting Manual (TSMN)

16

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

Troubleshooting Manual (TSMN)

Preface

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 management 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 displayed 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 The following symbols and conventions are used in this document:

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

17

Preface

Troubleshooting Manual (TSMN)

Conventions used Representation “Inverted commas”

Meaning 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. Commands, screen output, file names and paths are denoted by courier font.

Courier

Example: # ping -t 192.168.0.1

Keyboard actions or place holders for distinct names or values are represented by enclosing them in . If a file name is involved, the courier font will also be used. Example: The naming convention for the log files is .txt, where is the name of the NE sending the messages. Press + 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

Symbols used

g Used for notes, tips, or additional information. !

!

18

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 preventing accidents.

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

Troubleshooting Manual (TSMN)

1.4

Preface

History of changes Issue

Issue date

Remarks

1

March 2008

Initial version

3

August 2008

Update for release 3.21.10

Table 2

1.5

Document history

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

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

19

Alarm Lists

Troubleshooting Manual (TSMN)

2 Alarm Lists SURPASS hiT 7500 alarms are divided into the following categories: • • • • • •

2.1

Equipment alarms: originate from specific hardware elements (e.g., traffic card, controller card, shelf, etc). Communication alarms: originate from termination points which represent a particular function of the network. Processing Error alarms: originate from the NE software. Environmental alarms: originate from telemetry sensors that monitor conditions/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.

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 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)

CALIBRATION_FAILT2

Calibration Failure Tributary 2 (CALIBRATION_FAILT2)

CALIBRATION_FAILT3

Calibration Failure Tributary 3 (CALIBRATION_FAILT3)

CALIBRATION_FAILT4

Calibration Failure Tributary 4 (CALIBRATION_FAILT4)

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)

Table 3

20

Alarm Message Text

SURPASS hiT 7500 Equipment Alarms

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

Troubleshooting Manual (TSMN)

Alarm Lists

Alarm Name

Alarm Message Text

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)

FN12F

Cooling Fan12 Failure (FN12F)

FN21F

Cooling Fan21 Failure (FN21F)

FN22F

Cooling Fan22 Failure (FN22F)

FN31F

Cooling Fan31 Failure (FN31F)

FN32F

Cooling Fan32 Failure (FN32F)

FN1CF

Cooling Fan1 Comm Failure (FN1CF)

FN2CF

Cooling Fan2 Comm Failure (FN2CF)

FN3CF

Cooling Fan3 Comm Failure (FN3CF)

FN1M

Cooling Fan 1 Missing (FN1M)

FN2M

Cooling Fan 2 Missing (FN2M)

FN3M

Cooling Fan 3 Missing (FN3M)

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)

Table 3

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

SURPASS hiT 7500 Equipment Alarms (Cont.)

21

Alarm Lists

Troubleshooting Manual (TSMN)

Alarm Name 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)

ILOL2

Input Loss of Light 2 (ILOL2)

ILOL3

Input Loss of Light 3 (ILOL3)

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)

LOSIn2

Loss of Signal Input 2 (LOSIn2)

LOSIn3

Loss of Signal Input 3 (LOSIn3)

LOSIn4

Loss of Signal Input 4 (LOSIn4)

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)

Table 3

22

Alarm Message Text

SURPASS hiT 7500 Equipment Alarms (Cont.)

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

Troubleshooting Manual (TSMN)

Alarm Lists

Alarm Name

Alarm Message Text

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)

Table 3

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

SURPASS hiT 7500 Equipment Alarms (Cont.)

23

Alarm Lists

Troubleshooting Manual (TSMN)

Alarm Name

Alarm Message Text

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)

TSCh2TD

Transmit Degrade TSCh2 (TSCh2TD)

TSCh3TD

Transmit Degrade TSCh3 (TSCh3TD)

Table 3

24

SURPASS hiT 7500 Equipment Alarms (Cont.)

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

Troubleshooting Manual (TSMN)

Alarm Lists

Alarm Name TSCh4TD

Transmit Degrade TSCh4 (TSCh4TD)

TSCh1TF

Transmit Fail TSCh1 (TSCh1TF)

TSCh2TF

Transmit Fail TSCh2 (TSCh2TF)

TSCh3TF

Transmit Fail TSCh3 (TSCh3TF)

TSCh4TF

Transmit Fail TSCh4 (TSCh4TF)

TSCh1TEMP

Temperature Problem TSCh1 (TSCh1TEMP)

TSCh2TEMP

Temperature Problem TSCh2 (TSCh2TEMP)

TSCh3TEMP

Temperature Problem TSCh3 (TSCh3TEMP)

TSCh4TEMP

Temperature Problem TSCh4 (TSCh4TEMP)

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

2.2

Alarm Message Text

SURPASS hiT 7500 Equipment Alarms (Cont.)

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. Alarm Name BDI Table 4

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

Alarm Message Text Backward Defect Indication (BDI)

SURPASS hiT 7500 Communication Alarms (Cont.)

25

Alarm Lists

Troubleshooting Manual (TSMN)

Alarm Name

Alarm Message Text

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, Loss of Signal (LOS) and OSCT cards) 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)

Table 4

26

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

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

Troubleshooting Manual (TSMN)

Alarm Lists

Alarm Name

Alarm Message Text

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 Table 4

2.3

User Payload Mismatch (UPM) SURPASS hiT 7500 Communication Alarms (Cont.) (Cont.)

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. Alarm Name SCP Table 5

2.4

Alarm Message Text Storage Capacity Problem (SCP)

SURPASS hiT 7500 Processing Error Alarms

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. Alarm Name

Alarm Message Text

EXT

Telemetry Interface (Ext)

TIFACT

TIF Activated Alarm (TIFACT)

Table 6

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

SURPASS hiT 7500 Environmental Alarms

27

Alarm Lists

Troubleshooting Manual (TSMN)

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. Alarm Name EXCLOGIN

Unsuccessful Logins Exceeded (EXCLOGIN)

PWEXP

Password Expired (PWEXP)

PWEXPSON

Password will expire soon (PWEXPSON)

Table 7

2.6

Alarm Message Text

SURPASS hiT 7500 Security Alarms

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. Alarm Name SMISS

Sub System Missing (SMISS)

SFAIL

Sub System Failure (SFAIL)

Table 8

28

Alarm Message Text

SURPASS hiT 7500 Subsystem Alarms

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

3 Troubleshooting Instructions 3.1

Equipment Alarms This section contains troubleshooting instructions for hiT 7500 Equipment alarms.

3.1.1

ACTLP

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.

Troubleshooting instructions

3.1.2

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 currently-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 "Loopback Summary-Config" window displays a list of all active loopbacks 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.

AFEXRQ

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

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

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

29

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions 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. – –

3.1.2.1

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

AFEXRQ alarm raised by 10G shelf Troubleshooting instructions

!

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.

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.

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. 6

30

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

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

Troubleshooting Manual (TSMN)

Figure 1

3.1.2.2

Troubleshooting Instructions

Air Filter replacement in a 10G shelf

AFEXRQ alarm raised by 40G (OTS-4000) shelf Troubleshooting instructions 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 temperature 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].

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

31

Troubleshooting Instructions

3.1.3

Troubleshooting Manual (TSMN)

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.

ALRMPNLFAIL

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.

Troubleshooting instructions

3.1.4

1

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

2

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

ALRMPNLMISS

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.

Troubleshooting instructions

32

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.

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

Troubleshooting Manual (TSMN)

3.1.5

Troubleshooting Instructions

APRM

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”.

Troubleshooting instructions 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. – – – –

3

3.1.5.1

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.

If the APRM alarm persists after performing the appropriate procedure below, contact your next higher level of technical support.

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.

Troubleshooting instructions 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-

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

33

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

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 the ODAC5C6 and ODAC7C8 cards have raised an SBL alarm, then Fiber 3 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 the ODAC3C4 and ODAC7C8 cards have raised an SBL alarm, then Fiber 9 is likely the problem. If only the ODAC5C6 and ODAC1C2 cards have raised an SBL alarm, then Fiber 10 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

34

Contact your next higher level of technical support before proceeding. Replace any card still raising a CP alarm. This should clear the APRM and CP alarms.

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

Troubleshooting Manual (TSMN)

Figure 2

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

Troubleshooting Instructions

APRM in an OTT that uses OMDFIC + OMDFC

35

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Figure 3

3.1.5.2

APRM in an OTT that uses OMDFIC + OMD2IC

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.

Troubleshooting instructions 1

36

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

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

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 improperly 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. Reconnect 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: – – –

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

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”.

37

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Figure 4

3.1.5.3

APRM in an OADM100U

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: •

• • •

38

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. a disconnected PCB/CAN cable.

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Troubleshooting instructions 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 established. If the APRM alarm persists, disconnect these fibers and clean connectors. Reconnect 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.

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

39

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Figure 5

3.1.5.4

APRM in an OADM100N with CDAN and WBN

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: • • •

•

40

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.

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

Troubleshooting Manual (TSMN)

• •

Troubleshooting Instructions

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 communication.

!

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.

Troubleshooting instructions 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 - Measurement” 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 > Measurement. 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. Reenable APRM according to the instructions in chapter 3.1.5.9 and dispatch personnel 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.

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

41

Troubleshooting Instructions

Figure 6

42

Troubleshooting Manual (TSMN)

APRM in an OADM100N with CDN and WBAN

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

Troubleshooting Manual (TSMN)

Figure 7

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

Troubleshooting Instructions

Diagram for APRM troubleshooting in OADM100N with CDN and WBAN

43

Troubleshooting Instructions

Figure 8

44

Troubleshooting Manual (TSMN)

Isolating the APRM-causing fault in an OADM100N (1 of 2)

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

Troubleshooting Manual (TSMN)

Figure 9

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

Troubleshooting Instructions

Isolating the APRM-causing fault in an OADM100N (2 of 2)

45

Troubleshooting Instructions

3.1.5.5

Troubleshooting Manual (TSMN)

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. Troubleshooting instructions 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? – –

3

Clean the connector inside the WBAN card. Measure the power again. Is the power -9 dBm or higher? – –

4

Yes: skip to step 5. No: continue to the next step.

Yes: skip to step 5. No: continue to the next step.

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 protective cover. Then, re-measure the optical power. Is the power level -9 dBm or higher? – –

8

Yes: skip to step 10. No: continue to the next step.

Replace the duplex fiber between the CDN and WBAN with an inspected and cleaned spare. Did the APRM alarm clear? – –

9

Yes: skip to step 10. No: continue to the next step.

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

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? – –

46

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

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

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

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

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

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

13 Replace the Pre-amplifier OLI card with a spare and re-connect all fibers. Did the APRM alarm clear? – –

3.1.5.6

Yes: alarm cleared. Procedure complete. END. No: contact your next higher level of technical support. END.

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. Troubleshooting instructions 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

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 Preamplifier 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

Yes: skip to step 7. No: continue to the next step.

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

Yes: skip to step 8. No: continue to the next step.

Yes: skip to step 7. No: continue to the next step.

Replace the Pre-amplifier OLI 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.

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

47

Troubleshooting Instructions

7

Troubleshooting Manual (TSMN)

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). – –

8

Inspect and if necessary, clean the connector at "In" port of the CDN card. Reconnect the fiber at the CDN end. Did the APRM alarm clear? – –

9

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

Yes: alarm cleared. END. No: skip to step 10.

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. No: continue to the next step.

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? – –

3.1.5.7

Yes: alarm cleared. Procedure complete. END. No: contact your next higher level of technical support. END.

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. Troubleshooting instructions 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 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? – –

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? – –

4

48

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

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

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.

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

Troubleshooting Manual (TSMN)

5

Disconnect the fiber at the WBAN card’s In port. Measure the optical power being delivered to the end of this fiber. Use a coupler and jumper to connect the fiber to an optical power meter. Is the measured power approximately 6 dB less than the OLI Stage III output power from step 4? (Allow a tolerance of +/- 1.5 dB). – –

6

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

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

9

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

Clean the Out optical connector on the CDN card. Re-measure the output power at this port. Is the measured power approximately 6 dB less than the OLI Stage III output power from step 4? (Allow a tolerance of +/- 1.5 dB). – –

8

Yes: skip to step 10. No: continue to the next step.

Use a fiber jumper to measure the power from the CDN card’s Out port. Is the measured power approximately 6 dB less than the OLI Stage III output power from step 4? (Allow a tolerance of +/- 1.5 dB). – –

7

Troubleshooting Instructions

Yes: alarm cleared. Procedure complete. END. No: contact your next higher level of technical support. Do NOT continue with the next steps. END.

Replace the duplex cable 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.

10 Replace the WBAN card with a spare and re-connect all fibers. Did the APRM alarm clear? – –

3.1.5.8

Yes: alarm cleared. END. No: call your next higher level of technical support. END.

If Cable C is causing the APRM alarm Follow the instructions below if previous procedures indicated that a problem with Cable C is causing the APRM alarm. Troubleshooting instructions 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

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 "DrOut" port. Clean the fiber and measure the power level output from this port. Is the measured power approximately 2 dB less than the OLI Stage III output power from step 2? (Allow a tolerance of +/- 1.5 dB). – –

Yes: skip to step 6. No: continue to the next step.

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

49

Troubleshooting Instructions

4

Troubleshooting Manual (TSMN)

Clean the inside of the DrOut port on the CDN card. Re-measure the optical power being output from this port. Is the measured power approximately 2 dB less than the OLI Stage III output power from step 2? (Allow a tolerance of +/- 1.5 dB). – –

5

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

6

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

Replace the fiber between the CDN and OMDIFC with an inspected and clean spare. Did the APRM alarm clear? – –

9

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

Disconnect the fiber at the OMDIFC's "2C' port. Clean the fiber and measure the power being delivered to the end of this fiber. Is the measured power approximately 2 dB less than the OLI Stage III output power from step 2? (Allow a tolerance of +/1.5 dB). – –

8

Yes: alarm cleared. Procedure complete. END. No: contact your next higher level of technical support. Do NOT continue with the next steps. END.

Clean and re-connect the fiber that was disconnected in step 3. Did the APRM alarm clear? – –

7

Yes: skip to step 6. No: continue to the next step.

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

Clean the inside of the 2C connector on the OMDIFC card. Re-connect the cable removed in step 7. Did the APRM alarm clear? – –

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

10 Replace the OMDIFC card with a spare and re-connect all fibers. Did the APRM alarm clear? – –

3.1.5.9

Yes: alarm cleared. Procedure complete. END. No: contact your next higher level of technical support. END.

How to enable/disable APRM Follow the instructions below to temporarily disable/enable APRM.

g You must be User Class 10 to disable/enable APRM. !

50

Danger! If APRM is disabled, proper laser safety procedure must be followed. The output power at the Out port of the CDN card can be up to 22 dBm. The output power at the DrOut port of the CDN card can be up to 25 dBm.

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Disabling APRM 1

Open the Element Manager Equipment View. Locate the card replica of the desired Pre-amplifier OLI card. Right-click on this card replica and select Card > Configuration.

2

On the resulting “Card Configuration” window, right-click the "Automatic Power Shutdown" button. Note that this button is normally grayed out. The button is available only in Power User mode. To get to Power User mode, type: Ctrl-Alt-P and the PowerOn! password.

3

On the resulting “Automatic Power Shutdown” window, enter the desired disable time (in minutes) in the Disable Time field. Click the Apply button.

4

Click the Disable Automatic Power Shutdown button. A countdown display will show the number of APRM-disabled minutes remaining.

5

To log-out from this window, type Ctrl-Alt-P, then click Close to leave Power User mode. If the APRM disable time needs to be extended, repeat the above procedure anytime before the timer expires.

6

Disconnect the fiber at the OMDIFC's "2C' port. Clean the fiber and measure the power being delivered to the end of this fiber. Is the measured power approximately 2 dB less than the OLI Stage III output power from step 2? (Allow a tolerance of +/1.5 dB).

g When APRM is disabled on a Pre-amplifier OLI card, that card’s green OK LED will flash. Re-enabling APRM 1

To re-enable APRM, follow the same steps above, but set the Disable Time to 0, and then press the Disable Automatic Power Shutdown button. Alternatively, you can simply let the original Disable Time expire, after which APRM will be automatically re-enabled.

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

51

Troubleshooting Instructions

3.1.6

Troubleshooting Manual (TSMN)

APSBUF

Alarm name

APS Backup Failed (APSBUF)

Default severity

Minor

Alarm object

MCU cards

General information and causes

The MIBS256 board (as opposed to earlier MIBS32 and MIBS32-2 boards) contains additional memory to store a backup copy of the MCU's APS software. If the backup storage fails, the APSBUF alarm will be raised. Note therefore, that the APSBUF alarm is possible only for NEs equipped with the MIBS256 variant of the MIBS board.

Troubleshooting instructions 1

Cold Start the MCU card raising the alarm. If the APSBUF alarm is raised again after the MIBF and APSBUR alarms self-clear, dispatch personnel to the site. Take a spare MIBS256 board.

2

Uninstall the MIBS256 board associated with the MCU reporting the APSBUF alarm. (See chapter 9 for instructions how to determine the physical location of the MIBS board associated with a particular MCU). Once the MIBS256 is removed, a MIBM (MIB Missing) alarm will be raised.

3

Re-insert the MIBS256 card again. The MIBM alarm will clear and a MIBF alarm will be raised while the VCDB contents are being written into the MIB. The MCU should eventually start backing up its active APS software to the MIBS256 card, and therefore an APSBUR alarm will be raised. When the backup process has successfully completed, the APSBUR alarm will clear and the APSBUF alarm should remain cleared as well. However, if the APSBUF is raised again, continue to step 4.

4

Back-up the contents of the VCDB.

5

Withdraw the MCU card raising the APSBUF alarm from the shelf. Leave the MCU unseated for about 30 seconds, then re-insert it in the shelf. If this is a sub-agent MCU, a SMISS alarm will be raised until the sub-agent is visible again in the Tree View. If this is a Main Agent MCU, connectivity to the NE will be lost until the MCU boot-up is completed. Wait until the MIBF and APSBUR alarms are cleared. If the APSBUF alarm is raised again, continue to step 6.

6

If the APSBUF alarm persists, the MIBS256 board must be replaced. Refer to Chapter 9.1 for MIBS256 replacement instructions. IMPORTANT: the NE must remain powered-up when this procedure is performed. If power is disconnected prior to replacing a MIBS board, the database will be lost and traffic will likely be lost.

7

If the APSBUF alarm persists after replacing the MIBS256, contact your next higher level of technical support.

g On each MCU's “Card Configuration” window, make sure the MIBS256 Required checkbox is set appropriately. If an MCU uses a MIBS256, enable this checkbox. If an MCU uses one of the older MIBS variants, disable this checkbox. To obtain this window, right-click on the MCU card replica in the Equipment View add select Card > Configuration.

52

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

Troubleshooting Manual (TSMN)

3.1.7

Troubleshooting Instructions

APSBUR

Alarm name

APS Backup Running (APSBUR)

Default severity

Warning

Alarm object

MCU cards

General information and causes

The MIBS256 board (as opposed to earlier MIBS32 and MIBS32-2 boards) contains additional memory to store a backup copy of the MCU's APS software. When this backup is in progress, the APSBUR alarm will be raised. Note therefore, that the APSBUR alarm is possible only for NEs equipped with the MIBS256 variant of the MIBS board.

Troubleshooting instructions

3.1.8

1

The APSBUR alarm is simply a "warning" - a notification that the APS software backup routine is currently running. Simply wait for the backup process to complete and the APSBUR alarm will self-clear.

2

If the APSBUR alarm persists for an unreasonable length of time, there is likely something wrong with the backup process. In this case, follow the troubleshooting instructions for the APSBUF alarm.

APSM

Alarm name

APS Mismatch (APSM)

Default severity

Major

Alarm object

OCU73 Subsystem

General information and causes

Replacement of a faulty Compact Flash module on an NE Controller card (CCEP or CCMP) can cause an APSM alarm. See Compact Flash replacement in chapter 4.42. After replacement, the APS version that is present on the new Compact Flash is checked against the version number the network element thinks it should have. (The latter is stored on an EEPROM on the shelf backplane. If there is a mismatch, the system will enter the recovery mode, and the APSM alarm will be raised. Manual interventionis then required to download the proper APS to the NE.

Troubleshooting instructions 1

Manually download the APS that is correct for this OCU73 subsystem. Instructions for downloading the APS can be found in the hiT 7500 Operating Manual (OMN).

2

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

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

53

Troubleshooting Instructions

3.1.9

Troubleshooting Manual (TSMN)

BTBM

Alarm name

BTB Card Missing (BTBM)

Default severity

Critical

Alarm object

MCU cards

General information and causes

BTB = Bus Termination Board. A BTBM alarm indicates that the left and/or right Bus Termination Board is not installed on the indicated SURPASS hiT 7500 OCU Shelf. These boards are mounted on the interior surface of the backplane behind the upper Fan Unit. They should have been installed at the factory.

Troubleshooting instructions 1

!

3.1.10

Contact your next level of technical support before proceeding. Spare Bus Termination Board(s) are necessary. It will also be necessary to remove plug-in cards (which, of course, is traffic-affecting) in order to gain access to the mounting area for these boards.

Caution! The two boards are labeled "left" and "right". They must be mounted on the correct side of the shelf ("left" and "right" are referenced as you face the front of the shelf). The BTBM alarm is raised only if one or both boards are missing. The BTBM alarm will NOT be raised if the boards are swapped ( "left" board mounted on the right, or vice versa). Never swap the positions of these boards since doing so may drastically affect NE behavior.

CALIBRATION_FAIL

Alarm name

Calibration Failure (CALIBRATION_FAIL)

Default severity

Critical

Alarm object

OTS-4011, OTS-4040, OTS-4400, OTS-4520, and OTS4540 cards.

General information and causes

The calibration of a hardware component did not complete successfully.

Troubleshooting instructions 1

54

Contact your next level of technical support before proceeding since the following action is traffic-affecting. Execute a Warm Start of the affected card. If the CALIBRATION_FAIL alarm persists after Warm Start recovery time (approx 3 minutes), execute a Cold Start of the affected card. If the alarm persists after Cold Start

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

recovery time [approx 15 minutes (20 minutes for an OTS-4011)], the card is defective. Replace the affected card with a spare.

3.1.11

CALIBRATION_FAILL

Alarm name

Calibration Failure Line (CALIBRATION_FAILL)

Default severity

Critical

Alarm object

OTS-4011, OTS-4040, OTS-4400, OTS-4520, and OTS4540 cards.

General information and causes

The calibration of a hardware component at the Line interface did not complete successfully.

Troubleshooting instructions 1

3.1.12

Contact your next level of technical support before proceeding since the following action is traffic-affecting. Execute a Warm Start of the affected card. If the CALIBRATION_FAILL alarm persists after Warm Start recovery time (approx 3 minutes), execute a Cold Start of the affected card. If the alarm persists after Cold Start recovery time [approx 15 minutes (20 minutes for an OTS-4011)], the card is defective. Replace the affected card with a spare.

CALIBRATION_FAILT1

Alarm name

Calibration Failure Trib#1 (CALIBRATION_FAILT1)

Default severity

Critical

Alarm object

OTS-4011 and OTS-4040 cards.

General information and causes

The calibration of a hardware component at the Tributary 1 interface did not complete successfully.

Troubleshooting instructions 1

Contact your next level of technical support before proceeding since the following action is traffic-affecting. Execute a Warm Start of the affected card. If the CALIBRATION_FAILT1 alarm persists after Warm Start recovery time (approx 3 minutes), execute a Cold Start of the affected card. If the alarm persists after Cold Start recovery time (approximately 20 minutes), the card is defective. Replace the affected card with a spare.

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

55

Troubleshooting Instructions

3.1.13

Troubleshooting Manual (TSMN)

CALIBRATION_FAILT2

Alarm name

Calibration Failure Trib#2 (CALIBRATION_FAILT2)

Default severity

Critical

Alarm object

OTS-4011 cards.

General information and causes

The calibration of a hardware component at the Tributary 2 interface did not complete successfully.

Troubleshooting instructions 1

3.1.14

Contact your next level of technical support before proceeding since the following action is traffic-affecting. Execute a Warm Start of the affected card. If the CALIBRATION_FAILT2 alarm persists after Warm Start recovery time (approx 3 minutes), execute a Cold Start of the affected card. If the alarm persists after Cold Start recovery time (approximately 20 minutes), the card is defective. Replace the affected card with a spare.

CALIBRATION_FAILT3

Alarm name

Calibration Failure Trib#3 (CALIBRATION_FAILT3)

Default severity

Critical

Alarm object

OTS-4011 cards.

General information and causes

The calibration of a hardware component at the Tributary 3 interface did not complete successfully.

Troubleshooting instructions 1

56

Contact your next level of technical support before proceeding since the following action is traffic-affecting. Execute a Warm Start of the affected card. If the CALIBRATION_FAILT3 alarm persists after Warm Start recovery time (approx 3 minutes), execute a Cold Start of the affected card. If the alarm persists after Cold Start recovery time (approximately 20 minutes), the card is defective. Replace the affected card with a spare.

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

Troubleshooting Manual (TSMN)

3.1.15

Troubleshooting Instructions

CALIBRATION_FAILT4

Alarm name

Calibration Failure Trib#4 (CALIBRATION_FAILT4)

Default severity

Critical

Alarm object

OTS-4011 cards.

General information and causes

The calibration of a hardware component at the Tributary 4 interface did not complete successfully.

Troubleshooting instructions 1

3.1.16

Contact your next level of technical support before proceeding since the following action is traffic-affecting. Execute a Warm Start of the affected card. If the CALIBRATION_FAILT4 alarm persists after Warm Start recovery time (approx 3 minutes), execute a Cold Start of the affected card. If the alarm persists after Cold Start recovery time (approximately 20 minutes), the card is defective. Replace the affected card with a spare.

CANFAIL

Alarm name

CAN Bus Failure (CANFAIL)

Default severity

Minor

Alarm object

All plug-in cards types that communicate with the OSCT card via the CAN (Controller Area Network) bus.

General information and causes

The OSCT card periodically polls cards communicating with it over the CAN bus. The CANFAIL alarm will be raised if any of the OSCT's partner cards do not respond to a poll, thus indicating that there is some problem with communication via the CAN bus.

Troubleshooting instructions 1

Did the CANFAIL alarm clear itself in 5 minutes or less? If so, ignore the alarm - it was simply a transient. However, if the CANFAIL alarm persists for more than 5 minutes, continue with the next step.

2

How many cards in this network element are raising the CANFAIL alarm? If only one card is raising the alarm, go to step 3. If multiple cards are raising the alarm, go to step 4.

3

If only one card in the network element is raising the CANFAIL alarm, Warm Start the card raising the alarm. If the alarm persists after recovery time (approximately 3 minutes), Warm Start this network element’s OSCT card. If the alarm persists after recovery time (approximately 3 minutes), dispatch personnel to the site to replace the card raising the alarm. Go to step 5.

4

If multiple cards in the network element are raising the CANFAIL alarm, (especially the case where the alarm is raised by all cards in this network element that communicate with the OSCT), then the problem is likely a failure of the OSCT card

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

57

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

or a disconnected PCB/CAN cable. Warm Start this network element’s OSCT card. If the alarm persists after Warm Start recovery time (approximately 3 minutes), Cold Start the OSCT card. If the alarm persists after Cold Start recovery time (approximately 3 minutes), dispatch personnel to the site and verify that all PCB/CAN cables and termination resistors are installed according to the SURPASS hiT 7500 Installation and Test Manual (ITMN). Correct any cabling problems. If the alarm still persists, replace the OSCT card with a spare. 5

3.1.17

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

CDL

Alarm name

Coupler Drop Loss (CDL)

Default severity

Critical

Alarm object

CDU plug-in cards (note that CDN or CDAN cards do not raise this alarm).

General information and causes

The CDL alarm indicates loss of the input signal to the CDU card.

Troubleshooting instructions 1

Refer to Figure 10, which shows two degrees (ADU30 and ADX38) of a multi-degree OADM100U. This drawing is representative of all OADM100U configurations since the positioning of the CDU card is analagous in other portions (ADU31, ADX37, and ADX39) of any OADM100U. Dispatch personnel to the site raising the alarm. Verify that the fiber cable between the OLI Pre-amplifier card and CDU card raising the alarm is properly installed. If the cable is missing, bent/pinched, or improperly connected, correct the problem. The CDL alarm should clear when the correct connection is established.

58

2

If the alarm persists, open the “Traffic - Info” window for the OLI Pre-amplifier card (the Pre-amplifier card sending traffic to the CDU card raising the alarm) and note the Total Output Power value. This is the power that should reach the CDU card.

3

Contact your next level of technical support before proceeding since the following action is traffic-affecting. Disconnect the fiber at the In connector of the CDU card. With an optical power meter, measure the optical power being delivered to the end of this cable (from the OLI card output). If the measured value is considerably different than the OLI Total Output Power, clean all optical connectors and re-measure. If power is still out of range, replace the fiber cable with a clean, inspected spare.

4

If no other cause can be found, withdraw the CDU card raising the alarm a short distance from the shelf and re-insert it. If the alarm persists, the CDU card is defective. Replace the CDU card with a spare.

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

Troubleshooting Manual (TSMN)

Figure 10

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

Troubleshooting Instructions

Diagram for CDL alarm

59

Troubleshooting Instructions

3.1.18

Troubleshooting Manual (TSMN)

CFAIL

Alarm name

Card Failure (CFAIL)

Default severity

Major

Alarm object

Any plug-in card slot (note that this alarm is raised by an equipment shelf slot - not the plug-in card installed in that slot).

General information and causes

The CFAIL alarm indicates that the network element's MCU cannot communicate with the failed card (see exceptions explained below for an OSCT or SMU slot).

Troubleshooting instructions

g Behavior Note: basically, a CFAIL alarm is declared due to one of the following conditions: • • •

faulty communication between the card raising the alarm and the MCU card (via the Peripheral Control Bus). a software problem has occurred (example: failed software download). for slots equipped with OCR10 or TEX cards, there is a slight chance that a CFAIL alarm will be raised when the true condition is a Card Mismatch (slot configured for one kind of card, but another type is actually installed). So, first verify that the installed card type exactly matches how the slot has been configured via the craft terminal. Correct any mismatch, and the CFAIL alarm should clear.

For laser-equipped cards, this means the following: •

•

If the CFAIL alarm on a laser-equipped card was caused by communication failure, laser(s) may be on or off (depends on state the card was in before the communication failed). If the CFAIL alarm was caused by a software problem, the laser will NOT be shut off. The MCU sends a "soft disable" command* to the failed card which results in the following: – red LED on the failed card is turned on. – any configuration commands from the MCU to the failed card are suppressed (except Warm Start and Cold Start). – Controller Area Network (CAN) communication is disabled on the failed card. – the failed card will be shown in orange on craft terminal GUIs.

* Soft Disable feature not implemented on the following older card types: OCR10V2, OCR10-V3, TEX-V3, and OCP. 1

Troubleshooting instructions for the CFAIL alarm vary according to slot type. Go to the appropriate paragraph listed below that matches the slot raising the CFAIL alarm. – – – – – –

60

OSCT card slot: chapter 3.1.18.1. SMU card slot: chapter 3.1.18.2. OCR10T-LH or TEX-LH card slot: chapter 3.1.18.3. 40G Line card slot (OTS-40xx, OTS-4400, or OTS-45xx): chapter 3.1.18.4. FSU slot in an MCU-Shelf: chapter 3.1.18.5. Any other type of card slot: chapter 3.1.18.6.

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

Troubleshooting Manual (TSMN)

3.1.18.1

Troubleshooting Instructions

CFAIL raised by OSCT slot Check whether this slot is actually equipped with an OSCT card. Reason: the OSCT card contains the Card Presence Master. So, if the OSCT is missing, the MCU simply detects that the OSCT does not respond any longer and reports CFAIL in the corresponding slot [i.e., a CMISS (Card Missing) alarm will not be raised for the missing OSCT). The solution in this case is to install the proper OSCT card.

3.1.18.2

CFAIL raised by SMU slot Check whether this slot is actually equipped with an SMU card. Reason: the SMU card contains the Card Presence Master. So, if the SMU is missing, the MCU simply detects that the SMU does not respond any longer and reports CFAIL in the corresponding slot [i.e., a CMISS (Card Missing) alarm will not be raised for the missing SMU). The solution in this case is to install the proper SMU card.

3.1.18.3

CFAIL raised by OCR10T-LH or TEX-LH slot Figure 11 shows optical path diagrams where OCR10T-LH or TEX-LH cards are used. If a CFAIL alarm is raised by a slot containing one of these card types, troubleshoot according to the instructions below. Troubleshooting instructions 1

Warm Start the card in the slot raising the CFAIL alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card.

2

If the alarm persists, identify the nearest upstream card as shown in Figure 11. Turn off the line laser of the upstream card (in the direction toward the transponder raising the CFAIL alarm). Wait 5 minutes, then re-enable the laser.

3

If the alarm persists, replace the failed card with a spare.

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

61

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Figure 11

3.1.18.4

Identify the nearest upstream card

CFAIL raised by 40G card slots For 40G line cards slots (OTS-4011, OTS-4040, OTS-4400, OTS-4520, and OTS4540), follow the instructions below to troubleshoot a CFAIL alarm. Troubleshooting instructions

62

1

Warm Start the card in the slot raising the CFAIL alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. Wait 3 minutes for the card to recover from the Warm Start and see if the CFAIL alarm clears.

2

If the CFAIL alarm persists, Cold Start the card in the slot raising the CFAIL alarm. This will not be service-affecting. Wait up to 15 minutes for the card to recover from the Cold Start (up to 20 minutes for an OTS-4011). This should clear the CFAIL alarm.

3

If the CFAIL alarm persists, replace the affected card with a spare.

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

Troubleshooting Manual (TSMN)

3.1.18.5

Troubleshooting Instructions

CFAIL raised by FSU slot in MCU-Shelf The following information is valid only for an FSU installed in an MCU-Shelf. If an FSU slot in any other shelf type is raising the CFAIL alarm, use the procedure in chapter 3.1.18.6 to troubleshoot the alarm. Troubleshooting instructions 1

If an FSU containing software older than Release 3.21 is plugged into an MCUShelf running 3.21 software, the FSU slot will raise a CFAIL alarm. The root cause is that the MCU-Shelf running 3.21 software does not recognize an FSU that has earlier software loaded on it. The FSU needs to be upgraded to 3.21 software. If you like, you may simply return the FSU to Nokia Siemens Networks. The software will be upgraded and the FSU returned to you. Or, you can upgrade the FSU yourself via the following procedure: –

–

–

3.1.18.6

Remove the FSU from the MCU-Shelf. Take it to another shelf type (single-row optical shelf, double-row optical shelf, or OCU shelf) that is also running 3.21 software. Via Element Manager, open this shelf’s Shelf-Config window. In the “FSU Present Line Supervision” drop-down box, make sure “FSU Present” is selected. If this shelf already has an FSU installed, remove it. Ignore any alarm generated. Now install the “bad” FSU into the shelf running 3.21 software. The FSU will automatically be upgraded to 3.21. Wait for it to become visible in Element Manager. Verify that no CFAIL alarm is raised in this shelf. Since the FSU has now been upgraded to 3.21, it may be sucessfully installed in the MCU-Shelf. After doing so, if a CFAIL alarm is still generated, contact your next higher level of technical support.

CFAIL raised by other slot types For all other slot types (other than those covered in the paragraphs above), follow the instructions below to troubleshoot a CFAIL alarm. Troubleshooting instructions 1

Is traffic affected due to the CFAIL condition? –

–

Yes: Warm Start the card in the slot raising the CFAIL alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card in the slot raising the CFAIL alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

63

Troubleshooting Instructions

3.1.19

Troubleshooting Manual (TSMN)

CFF

Alarm name

Compact Flash Fail (CFF)

Default severity

Major

Alarm object

CCEP and CCMP Controller cards.

General information and causes

A Controller card will raise the CFF alarm if it cannot write data to its on-board Compact Flash memory module.

Troubleshooting instructions

3.1.20

1

Warm Start the card raising the CFF alarm. If the alarm persists, Cold Start the card.

2

If the alarm persists, dispatch service personnel to the site of the failed Controller card (take a spare Compact Flash Module). Once on-site, replace the Compact Flash module in the card raising the alarm according to the Compact Flash replacement procedure in chapter 4.42.

3

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

CHCNTMISM

Alarm name

Channel Count Mismatch (CHCNTMISM)

Default severity

Minor

Alarm object

Link Control 1 (OSCT card)

General information and causes

Channel count is continuously analyzed by two methods: the count according to the OSCT card (derived via the individual channel photodiodes on multiplexer cards and by monitoring information on the Electrical Supervisory Channel) and the channel count measured by the OPAPC card. The CHCNTMISM alarm will be raised if the OSCT-derived channel count and the OPAPC-measured channel counts detect three consecutive mismatches. The alarm will clear when the OSCT channel count and OPAPC channel count are identical. The CHCNTMISM alarm will be displayed on GUI windows as raised against the object "Link Control 1". Link Control 1 designates Tx direction. (Link Control 2 designates the Rx direction; however, this will never be seen in hiT 7500).

Troubleshooting instructions 1

If any of the following alarms are also raised, troubleshoot and clear that alarm first. These alarms generally indicate a faulty fiber connection problem (dirty, kinked, or disconnected fiber). Correcting this fault should also clear the CHCNTMISM alarm. – – –

64

CTRLCABLP LOSADD LOSIn1, LOSIn2, LOSIn3, or LOSIn4

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

Troubleshooting Manual (TSMN)

–

Troubleshooting Instructions

LOC

2

If the CHCNTMISM alarm persists, open the “Optical Link Control - Config” window for the OSCT card raising the alarm. To do so, right-click on the OSCT card replica in the Equipment View and select Optical Link Control. Check the “Last Action” message field. The mismatched channel(s) will be identified by messages that say “Channel count mismatch for channel x” where “x” is the Channel ID.

3

Now that the chanel IDs of the mismatched channel(s) are known: –

–

4

If Channel Count Mismatch is due to Add channels: Check the transponder card(s) supplying the mismatched channel(s). The transponder card user-configured output frequency may not be set to the correct value (it may not match the Optical Multiplexer (OM) card input port it is connected to (thus blocking the channel). Correct the transponder card’s output frequency and the CHCNTMISM alarm should clear. If the CHCNTMISM alarm persists, Warm Start the OM card(s) supplying the mismatched channel(s). If the Warm Start does not clear the alarm, contact your next higher level of technical support before proceeding. Cold Start the OM card(s) supplying the mismatched channel(s). If the Cold Start does not clear the alarm, dispatch personnel to the site and verify that all PCB/CAN cables and termination resistors are installed according to the SURPASS hiT 7500 Installation and Test Manual (ITMN). If the alarm persists, replace the OM card(s) supplying the mismatched channel(s). If Channel Count Mismatch is NOT due to Add channels: the problem is likely due to Express Channels. Warm Start the WBAx (WBAU or WBAN as applicable) in the same NE as the OSCT card raising the CHCNTMISM alarm. If the Warm Start does not clear the alarm, contact your next higher level of technical support before proceeding. Cold Start the WBAx card. If the Cold Start does not clear the alarm, dispatch personnel to the site and verify that all PCB/CAN cables and termination resistors are installed according to the SURPASS hiT 7500 Installation and Test Manual (ITMN). If the alarm persists, replace the WBAx card.

Contact your next higher level of technical support before proceeding. If none of the above procedures cleared the alarm, Warm Start the affected OSCT card. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OSCT. If the alarm persists after recovery time (approx 3 minutes), the OSCT card is defective. Replace the OSCT card with a spare.

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

65

Troubleshooting Instructions

3.1.21

Troubleshooting Manual (TSMN)

CLOSSHDS

Alarm name

Communication Loss to HDS (CLOSSHDS)

Default severity

Major

Alarm object

Shelf containing the MCU-OCU73 card.

General information and causes

If there is no connection detected between the MCU-OCU73 and an HDS shelf Controller card (CCEP or CCMP), the CLOSSHDS alarm will be raised.

Troubleshooting instructions 1

Cold Start the MCU-OCU73 card in the shelf raising the alarm and wait 10 minutes. If the alarm persists, dispatch personnel to the site.

2

Once on site, do the following: – –

–

3.1.22

Verify that all MCU cards and the Controller Card (CCEP or CCMP) are properly installed and powered. Check the Ethernet cabling between the MCU-OCU73 and the Controller card. Correct any errors based on cabling instructions in the Interconnection & Mechanical Assembly (ICMA) document. If the CLOSSHDS alarm persists, continue to step 3.

3

Withdraw the Controller Card (CCEP or CCMP) from its shelf, then re-seat it.

4

If the CLOSSHDS alarms persists, the Controller card is defective and must be replaced. Follow the procedure in chapter 4.40. Follow all steps carefully to avoid impacting traffic.

5

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

CLOSSOTS

Alarm name

Communication Loss to OTS (CLOSSOTS)

Default severity

Major

Alarm object

OTS-4000 shelf.

General information and causes

If there is no connection detected between the MCU-OCU40 and one of the OTS-4700 Controller card it manages, the CLOSSOTS alarm will be raised.

Troubleshooting instructions 1

Warm Start the OTS-4700 Controller card in the shelf raising the CLOSSOTS alarm. Did the alarm clear? – –

2

66

Yes: End of procedure. No: Go to step 2.

Cold Start the OTS-4700 Controller card in the shelf raising the CLOSSOTS alarm. Wait 10 minutes. Is the CLOSSOTS alarm cleared and a SYNCPROG alarm raised?

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

Troubleshooting Manual (TSMN)

–

– 3

Troubleshooting Instructions

Yes: Wait another 10 minutes. If the SYNCPROG alarm clears, then the procedure is finished. If the SYNCPROG alarm remains raised, go to the troubleshooting instructions for the SYNCPROG alarm. No: If the CLOSSOTS alarm is still raised, go to step 3.

Cold Start the MCU-OCU40 card that manages the shelf raising the CLOSSOTS alarm. Then, wait 5 minutes after the MCU-OCU40 is visible again on the GUI. Has the CLOSSOTS alarm cleared? – –

4

Dispatch personnel to the site. Once on site, do the following: – – –

–

3.1.23

Yes: End of procedure. No: Go to step 4. Verify that all MCU cards and the OTS-4700 Controller Card are properly installed and powered. Verify that the rack-mounted Ethernet Switch is functioning. Check the Ethernet Switch port LEDs where the cables from the MCU-OCU40 and from the OTS-4700 Controller are connected. Verify that the LEDs are lit. If they are not lit, check for cabling errors and correct them based on cabling instructions in the Interconnection & Mechanical Assembly (ICMA) document. If the CLOSSOTS alarm persists, continue to step 5.

5

In the OTS-4000 shelf raising the alarm, withdraw the OTS-4700 Controller card, then re-seat it in the shelf. The CLOSSOTS alarm should clear.

6

If the CLOSSOTS alarms persists, the OTS-4700 Controller Card is defective and must be replaced. Follow the procedure in chapter 4.35. Follow all steps carefully to avoid impacting traffic.

7

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

CMISM

Alarm name

Card Mismatch (CMISM)

Default severity

Minor

Alarm object

Any plug-in slot, including DCM slots.

General information and causes

A card slot will raise the CMISM alarm if the slot has been "configured" for a particular plug-in card, but a card of another type is actually installed in that slot.

Troubleshooting instructions 1

What type of card is in the slot raising the CMISM alarm? – –

2

DCM, CDN, CDAN, CDU, or OMDxx: go to step 2. All other types: skip step 2 and go directly to step 3.

If a CMISM alarm is raised by a DCM or one of the passive cards types listed above, first check if (in the same shelf), a CFAIL alarm is raised on the OSCT slot. If a CFAIL alarm exists on the OSCT slot, it may be a simple case of a missing OSCT card. Therefore, install the correct OSCT card to clear the alarm. Explanation: The OSCT is always equipped in Shelf 1. The OSCT controls DCMs and all passive cards in Shelf 1. Passive cards located in secondary shelves are

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

67

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

controlled by the corresponding SMU cards. The MCU routinely polls all cards. If the OSCT card is missing and a passive card (for example, a CDN) is still plugged in, the CDN cannot respond directly to the polling. CMISS and CMISM alarms will both be reported for the "missing" CDN card, since its real status is unknown. However, the real problem is a missing OSCT card. 3

If the CMISM alarm was not caused by a missing OSCT card as explained above, it can have three other possible causes: –

– –

The slot was configured for one type of plug-in card, but a card of a different type was installed in the slot. Solution: remove the incorrect card and install the correct one. Also, please see the note below for OTS-4520 cards. The slot was configured to be empty, but a plug-in card was installed in the slot. Solution: remove the incorrect plug-in card. The proper type of plug-in card is installed in the slot, but the slot was configured for a different card type. Solution: re-configure the slot for the type of card actually installed.

g Note that OTS-4520 (TDCM) cards are manufactured in different “grades” (Grade A and Grade B), the difference being the power penalty range for each type. If a slot was configured for one Grade of OTS-4520, but the other Grade is actually installed, a CMISM alarm will be raised. So, if a CMISM alarm is raised for an OTS-4520 slot, check that the correct OTS-4520 card (standard or offset channel grid) and the correct Grade (A or B) is installed. Available OTS-4520 cards are as follows: – – – – 4

!

68

OTS-4520-13 = Standard channel grid, Grade A type. OTS-4520-23 = Standard channel grid, Grade B type. OTS-4520-14 = Offset channel grid, Grade A type. OTS-4520-24 = Offset channel grid, Grade B type.

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

Caution! For multi-slot plug-in cards, always ensure that the card is installed to occupy only the correct slots.

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

Troubleshooting Manual (TSMN)

3.1.24

Troubleshooting Instructions

CMISS

Alarm name

Card Missing (CMISS)

Default severity

Minor

Alarm object

Any plug-in slot, including DCM slots.

General information and causes

A card slot will raise the CMISS alarm if the slot has been "configured" for a particular plug-in card, but no card is actually installed in that slot.

Troubleshooting instructions 1

What type of card is in the slot raising the CMISS alarm? – –

2

DCM, CDN, CDAN, CDU, or OMDxx: go to step 2. All other types: skip step 2 and go directly to step 3.

If a CMISS alarm is raised by a DCM or one of the passive cards types listed above, first check if (in the same shelf), a CFAIL alarm is raised on the OSCT slot. If a CFAIL alarm exists on the OSCT slot, it may be a simple case of a missing OSCT card. Therefore, install the correct OSCT card to clear the alarm. Explanation: The OSCT is always equipped in Shelf 1. The OSCT controls DCMs and all passive cards in Shelf 1. Passive cards located in secondary shelves are controlled by the corresponding SMUs. The MCU routinely polls all cards. If the OSCT card is missing and a passive card (for example, CDN) is still plugged in, the CDN cannot respond directly to the polling. CMISS and CMISM alarms will both be reported for the "missing" CDN card, since its real status is unknown. However, the real problem is a missing OSCT card.

!

3

If the CMISS alarm was not caused by a missing OSCT card as explained above, it is likely caused by the following: the slot was configured for one type of plug-in card, but no card has been installed in the slot. Solution: install the correct card or re-configure the slot to “empty” if it truly is supposed to be empty.

4

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

Caution! For multi-slot plug-in cards, always ensure that the card is installed to occupy only the correct slots.

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

69

Troubleshooting Instructions

3.1.25

Troubleshooting Manual (TSMN)

CONCABF

Alarm name

OLI Connection Cable Fail (CONCABF)

Default severity

Major

Alarm object

Pump cards (all types)

General information and causes

A "Standard" OLI card may have up to three optional PUMP plug-in cards connected to it via fiber pigtails that are integral to the OLI. These pigtails include a small, low-voltage electrical cable that provides the capability to detect if the connection is mated properly. If an OLI-to-PUMP pigtail is not connected, the affected PUMP card will raise a CONCABF alarm.

Troubleshooting instructions

3.1.26

1

Contact your next level of technical support before proceeding since the following action is traffic-affecting. Warm Start the PUMP card raising the alarm. If the alarm persists after Warm Start recovery time (approx 3 minutes), dispatch personnel to the site to check the cables.

2

Ensure that the fiber pigtails from the associated OLI card are connected properly to each PUMP card. If not, clean all optical connectors and make the correct fiber connections. This should clear the CONCABF alarm. Note that it is necessary to withdraw PUMP cards a short distance from the shelf in order to access its internal connector.

3

If the alarm persists, contact your next level of technical support before proceeding since the following action is traffic-affecting. Replace the failed PUMP card with a spare.

CP

Alarm name

Card Problem (CP)

Default severity

Major

Alarm object

Plug-in card (all types)

General information and causes

The CP alarm indicates an internal fault on the designated plug-in card. Note that the CFAIL alarm indicates a total card failure, while the CP alarm generally indicates a less serious fault that the card is still able to self-report.

Troubleshooting instructions 1

If the CP alarm is raised by a PUMP card, investigate the conditions described in chapter 3.1.26.1 and 3.1.26.2. For all other card types, continue to step 2.

2

Is traffic affected due to the CP condition? –

70

Yes: Warm Start the card raising the CP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the

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

Troubleshooting Manual (TSMN)

–

3.1.26.1

Troubleshooting Instructions

Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. Note for ODA20 cards: it is possible that a CP alarm for an ODA20 card is really indicating a Variable Optical Attenuator (VOA) problem. If the Cold Start does not clear the alarm on an ODA20 card, go to the troubleshooting instructions for the VOAP# alarm. No: Warm Start the card raising the CP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

Special procedure “A” for CP alarm raised by PUMP card A problem with the pigtail connection between a PUMP card and an OLI card may cause the PUMP card to raise a CP alarm. If a PUMP card has raised a CP alarm, check the following before performing other troubleshooting steps in chapter 3.1.26. Troubleshooting instructions 1

Check the PUMP card raising the CP alarm. Is it blinking its red Fault LED? –

– 2

Dispatch personnel to the site. Check the PUMP card’s pigtail connection to its OLI card. If the pigtail is connected, check to see if any connectors are damaged. [If the pigtail is not connected at all, the PUMP card should have raised a CONCABF alarm]. If the connection is OK, the problem is with the PUMP card or the OLI card. So, check the following: –

–

3.1.26.2

Yes: the PUMP card cannot start because the pigtail connection to the OLI card has a problem. Go to step 2 below. [Via this pigtail, the PUMP card receives a 5V laser safety signal from the OLI card it is connected to. The PUMP card will operate only when it detects this 5V signal]. No: Go to paragraph 3.1.26.2.

if all PUMP cards connected to this OLI show a blinking Fault LED and a CP alarm, the problem is with the OLI card's 5V generator circuitry. Replace the OLI card with a spare to clear the CP alarm on the PUMP card. if only one of the PUMP cards connected to an OLI shows a blinking Fault LED and a CP alarm, the problem is likely with that PUMP card. Return to chapter 3.1.26 for further troubleshooting instructions.

Special procedure “B” for CP alarm raised by PUMP card Under certain conditions, it is possible for PUMP cards to raise a toggling CP alarm (caused by electric noise in the laser current measurement circuit). If a PUMP card has raised a CP alarm, check the following before performing other troubleshooting steps in chapter 3.1.26. Troubleshooting instructions 1

Is the PUMP card CP alarm toggling, i.e., is the alarm raised and cleared automatically within approximately 2 minutes? [The raise / clear cycle may occur repeatedly]. Toggling of the CP alarm can be verified by the following. –

the alarm history log file (EMS or NCT/LCT) will show the CP alarm raise and clear automatically within approximately 2 minutes. To view the alarm log, right

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

71

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

– –

3.1.27

click on the node name in the Functional View Window and select NE Logs. Then, select Alarm and click the Log Records button. the PUMP card replica on the craft terminal Equipment View will toggle its alarm indication (card replica changes to red, then back to normal again). the red Fault LED on the PUMP card will toggle on and off.

2

Is the laser on the PUMP card switched off? To check, open the “Card Configuration” window of the PUMP card raising the CP alarm. If the Pump State is listed as disabled and the displayed Laser Current(s) are well below 100 mA, then this card's laser is switched off. [To open this window, right-click on the PUMP card replica in the Equipment View and select Card > Configuration.

3

If both conditions exist (CP alarm is toggling and PUMP card's laser is switched off), the problem is not traffic-affecting and the PUMP card does not need to be replaced, i.e., the CP alarm may be ignored. If only one (or neither) condition exists, return to chapter 3.1.26 for further troubleshooting instructions.

CPHDS

Alarm name

Communication Problem to HDS (CPHDS)

Default severity

Major

Alarm object

Shelf containing the MCU-OCU73 card.

General information and causes

If only a partial connection is detected between the MCUOCU73 and an HDS shelf Controller card (CCEP or CCMP), the CPHDS alarm will be raised.

Troubleshooting instructions 1

Are personnel currently at the site of the failure? – –

72

No: Cold Start the MCU-OCU73 card in the shelf raising the alarm. If the alarm persists, dispatch service personnel to the site. Go to step 2. Yes: Go to step 2.

2

Withdraw the Controller card (CCEP or CCMP) from its shelf, then re-seat it.

3

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

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

Troubleshooting Manual (TSMN)

3.1.28

Troubleshooting Instructions

CPOTS

Alarm name

Communication Problem to OTS (CPOTS)

Default severity

Major

Alarm object

OTS-4000 shelf.

General information and causes

If only a partial connection is detected between the MCUOCU40 and the OTS-4700 Controller card, the CPOTS alarm will be raised.

Troubleshooting instructions 1

Warm Start the OTS-4700 Controller card in the shelf raising the CPOTS alarm. Did the CPOTS alarm clear? – –

2

Cold Start the OTS-4700 card in the shelf raising the CPOTS alarm. A CLOSSOTS alarm and a SYNCPROG alarm will be raised. Wait 15 minutes. At the end of 15 minutes, are the CLOSSOTS or SYNCPROG alarms still raised? – –

3

Yes: End of procedure. No: Go to step 2.

Yes: Go to the troubleshooting instructions for CLOSSOTS or SYNCPROG as appropriate and trouble that alarm first. No: Go to step 3.

Wait 5 more minutes. Is the CPOTS alarm raised again? – –

4

No: End of procedure. Yes: Go to step 4.

Cold Start the MCU-OCU40 card that manages the OTS-4000 shelf raising the CPOTS alarm. Did the CPOTS alarm clear? – –

Yes: End of procedure. No: Go to step 5.

5

Dispatch personnel to the site. In the OTS-4000 shelf raising the alarm, withdraw the OTS-4700 Controller Card, then re-seat it in the shelf. The CPOTS alarm should clear.

6

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

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

73

Troubleshooting Instructions

3.1.29

Troubleshooting Manual (TSMN)

CTP

Alarm name

Card Temperature Problem (CTP)

Default severity

Minor

Alarm object

TEX and OCR10 cards (all types).

General information and causes

This alarm indicates that sensors on the card have determined that the temperature has exceeded the allowable threshold. The affected card will shut down its lasers when a CTP alarm is raised.

Troubleshooting instructions

3.1.30

1

Check if the shelf containing the affected card has raised a Fan alarm: FNLOW, FNLOWM, FNUPP, or FNUPPM, and troubleshoot any such alarm first.

2

If the CTP alarm persists, check the ambient temperature around the shelf. It must be lower than 50°C (122°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications.

3

Contact your next level of technical support before proceeding since the following action is traffic-affecting. If no other cause can be found, Warm Start the card raising the alarm. If the CTP alarm persists after Warm Start recovery time (approx 3 minutes), Cold Start the card. If the CTP alarm persists after Cold Start recovery time (approx 3 minutes), the card is defective. Replace the affected card with a spare.

CTRLCABLP

Alarm name

Control or Cabling Problem (CTRLCABLP)

Default severity

Minor

Alarm object

TSC card

General information and causes

The TSC card will raise a CTRLCABLP alarm if: • •

the TSC card’s control algorithm detects a fault. or, if the TSC card detects a missing or incorrectly routed fiber connection.

Troubleshooting instructions 1

Check the following fiber connections (which form the TSC card’s “control and insertion” loop). If any fibers are missing or connected to the wrong port, correct the error and the alarm should clear. –

– –

74

ADN20 or ADN21: – TSC “Out” to OMDIFC “AuxIn”. – OMDIFC “1C” to CDAN “AddIn”. ADU30 or ADU31 without WSSC: – TSC “Out” to WBAU “UpgIn”. ADU30 or ADU31 with WSSC: – TSC “Out” to WSSC “AuxIn”.

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

Troubleshooting Manual (TSMN)

–

3.1.31

Troubleshooting Instructions

– WSSC “ExpOut” to WBAU “UpgIn”. ADX37, ADX38, or ADX39: – TSC “Out” to WSSC “AuxIn” – WSSC “ExpOut” to CAX “ExpIn”.

2

If the fiber connections prove to be properly routed and the alarm persists, open the TSC card’s Card-Configuration window and disable Transient Suppression. Wait until the Transient Suppression Laser State field changes to “disabled” (this may take a few minutes). Then, disconnect the fiber connected to the TSC card and clean all connectors. Re-connect the fiber and see if the alarm clears.

3

If the alarm clears, re-enable Transient Suppression. Verify that the Transient Suppression Laser State field changes back to “enabled” (this may take a few minutes).

4

If the alarm persists, Warm Start the TSC card. If the alarm persists after recovering from the Warm Start, Cold Start the card.

5

If the alarm persists after recovering from the Cold Start, contact your next level of technical support before proceeding. The TSC is likely faulty and needs to be replaced with a spare.

CUPGVIOL1

Alarm name

Channel Upgrade Order Violation 1 (CUPGVIOL1)

Default severity

Minor

Alarm object

OSCT cards

General information and causes

This alarm is raised if the SURPASS hiT 7500 channel upgrade rules for power pre-emphasis are violated (see below). The CUPGVIOL alarm will be displayed on GUI windows as raised against the object "Link Control 1". Link Control 1 designates Tx direction. (Link Control 2 designates the Rx direction; however, this will never be seen in SURPASS hiT 7500.

Troubleshooting instructions 1

First, verify that the CUPGVIOL1 alarm is not transient. If either of the scenarios below caused a transient CUPGVIOL1 alarm, the alarm can safely be ignored. If the alarm is not transient, continue to step 2. –

Scenario 1: During a channel upgrade: When a channel is added (upgraded), the link control software receives the information that a new channel is available. If the new channel satisfies the Upgrade Rules (see chapter 3.1.31.1), the software will set the internal alarm indicator (which drives the CUPGVIOL1 alarm, add the channel, then reset the alarm indicator. The CUPGVIOL alarm will not be raised if the alarm raise time is set to a value of 2 seconds or higher. However, a shorter alarm integration time (100 msec for example) will result in a transient CUPGVIOL1 alarm, which will automatically

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

75

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

–

2

clear after the channel is successfully added. Since this is expected behavior, the transient CUPGVIOL1 alarm can be ignored Scenario 2: During channel recovery: When multiple channels are recovered, such as restoration from a fiber cut, these recovered channels must undergo the upgrade process. The link control software will automatically follow the Upgrade Rules (see chapter 3.1.31.1) to ensure that the incremental power does not exceed 1 dB per upgrade cycle. Hence, if there are many channels being recovered, they will be upgraded in a series of steps. The same activity described in Scenario 1 above will also occur in this case (i.e., the internal alarm indicator is set, the channels are added, and the internal alarm indicator is reset after ALL channels have been upgraded successfully). In this scenario, depending on the number of channels to be upgraded, a transient CUPGVIOL1 alarm may be raised for a few seconds. For Scenario 2, a transient CUPGVIOL1 alarm may be raised (even if the alarm raise time is set to 2 seconds), if the increase in optical power is greater than 3 dB (i.e. the number of channels being recovered is double (or more) the number of existing channels). Since this is expected behavior, the transient CUPGVIOL1 alarm can be ignored.

If step 1 did not verify that the CUPGVIOL1 alarm is an ignorable transient, it is assumed that it is a standing alarm. When a channel is upgraded, the link control software receives the information that a new channel is available. If the new channel does not satisfy the Upgrade Rules (see chapter 3.1.31.1), the software will raise a persistent CUPGVIOL1 alarm until the new channel is deleted (i.e. the relevant transponder must be deleted). So, in order to clear a standing CUPGVIOL1 alarm, the offending channel must first be deleted. Then re-add the new channel; only in accordance with the Upgrade Rules.

3

3.1.31.1

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

Channel Upgrade Rules Channel Upgrade Rules are as follows: A channel may be added only if its optical power is within a specific power window. The power window is defined as the normal output power range of the Nokia Siemens Networks 10G and 40G transponder card that is the source of the new channel. In other words, as long as the transponder Line Tx output power is within published specifications, it is possible to add the new channel. Note however, that external attenuation is needed with first-generation 40G transponder cards to reduce power to an acceptable level.

76

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

Troubleshooting Manual (TSMN)

3.1.32

Troubleshooting Instructions

DSPP

Alarm name

DSP Problem (DSPP)

Default severity

Minor

Alarm object

TSC card.

General information and causes

The TSC card will raise the DSPP alarm if it detects a fault in its on-board Digital Signal Processor.

Troubleshooting instructions

3.1.33

1

Warm Start the TSC card raising the alarm. If the alarm persists, Cold Start the card.

2

If the alarm persists, contact your next level of technical support before proceeding. Replace the failed TSC card with a spare.

ETHSWFAIL

Alarm name

Ethernet Switch Fail (ETHSWFAIL)

Default severity

Major

Alarm object

TL1-GNE and MCU-GNE cards

General information and causes

The cable connection between the GNE card and the rackmounted Ethernet Switch is supervised. If the link is down, the ETHSWFAIL alarm will be raised.

Troubleshooting instructions 1

Establish the proper cable connection between the GNE card and the Ethernet Switch. This will clear the ETHSWFAIL alarm.

2

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

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

77

Troubleshooting Instructions

3.1.34

Troubleshooting Manual (TSMN)

FAN_MAJOR

Alarm name

Fan Major (FAN_MAJOR)

Default severity

Major

Alarm object

HDS shelf.

General information and causes

An HDS shelf will raise the FAN_MAJOR alarm: • •

if the Fan Unit is removed from the shelf. or, if two or more fan packs inside the Fan Unit are faulty. Note: all working fan packs in the Fan Unit will go to high speed when a FAN_MAJOR alarm is active.

Troubleshooting instructions 1

!

Warning! Do NOT remove an HDS-shelf Fan Unit unless the replacement unit is readily at hand. When a shelf’s Fan Unit is removed, there is no cooling airflow. Therefore, the replacement unit must be inserted as quickly as possible after removing the old unit.

2

3.1.35

Immediately dispatch personnel to the site to replace the faulty (or missing) Fan Unit with a spare. In addition to the spare Fan Unit, take a spare air filter (it is a good idea to check the filter as long as you are there).

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

FAN_MINOR

Alarm name

Fan Minor (FAN_MINOR)

Default severity

Minor

Alarm object

HDS shelf.

General information and causes

An HDS shelf will raise the FAN_MINOR alarm if one fan pack inside the shelf Fan Unit is faulty. Note: all working fan packs in the unit will go to high speed when a FAN_MINOR alarm is active.

Troubleshooting instructions 1

78

Replace the faulty Fan Unit with a spare as soon as possible before a more serious FAN_MAJOR alarm has a chance to occur. It is recommended to replace the Fan

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Unit within 24 hours of a FAN_MINOR alarm. In addition to the spare Fan Unit, take a spare air filter (it is a good idea to check the filter as long as you are there).

!

Warning! Do NOT remove an HDS-shelf Fan Unit unless the replacement unit is readily at hand. When a shelf’s Fan Unit is removed, there is no cooling airflow. Therefore, the replacement unit must be inserted as quickly as possible after removing the old unit.

2

3.1.36

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

FBSIG_ABSENT

Alarm name

Feedback Absent (FBSIG_ABSENT)

Default severity

Major

Alarm object

OTS-4520 (TDCM) card and OTS-4540 (PMDC) card

General information and causes

A TDCM or PMDC card will raise a FBSIG_ABSENT alarm if it does not detect the required feedback signal from the associated line card. This is caused by some problem with the Ethernet connection between the two cards that carries the feedback signal.

Troubleshooting instructions

3.1.37

1

First, troubleshoot and clear any other alarms raised by the failed card or the Line Card to which it is connected.

2

If the FBSIG_ABSENT alarm persists, Warm Start the card raising the alarm. If the alarm persists, Warm Start the associated line card.

3

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

FBSIG_DEGRADED

Alarm name

Feedback Degraded (FBSIG_DEGRADED)

Default severity

Major

Alarm object

OTS-4520 (TDCM) card and OTS-4540 (PMDC) card

General information and causes

A TDCM or PMDC card will raise a FBSIG_DEGRADED alarm if it detects some problem with the feedback signal with the associated line card, preventing proper dispersion compensation adjustments. This is typically caused by a sudden change in dispersion conditions on the line.

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

79

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions

3.1.38

1

Often, the line anomaly that caused the FBSIG_DEGRADED alarm is only temporary. If the FBSIG_DEGRADED alarm clears itself in 5 minutes or less, ignore the alarm. However, if the alarm persists, continue to step 2.

2

Troubleshoot and clear any other alarms raised by the failed card or the Line Card to which it is connected.

3

If the FBSIG_ABSENT alarm persists, Warm Start the card raising the alarm. If the alarm persists, Warm Start the associated line card.

4

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

FIFOFLOWP

Alarm name

Fifo Flow Problem (FIFOFLOWP)

Default severity

??

Alarm object

V1 versions of OTS-4011, OTS-4040, and OTS-4400 cards

General information and causes

There is a clock alignment fault on the card raising the FIFOFLOWP alarm. This alarm indicates that the card has switched from the received line clock to its own internal clock, and a misalignment has occurred.

Troubleshooting instructions

80

1

Warm Start the card raising the alarm. If the alarm persists after the card recovers from the Warm Start, Cold Start the card. If the alarm persists after the card recovers from the Cold Start, dispatch personnel to the site to replace the failed card with a spare.

2

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

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

Troubleshooting Manual (TSMN)

3.1.39

Troubleshooting Instructions

FN11F

Alarm name

Cooling Fan11 Failure (FN11F)

Default severity

Major

Alarm object

OTS-4000 shelf

General information and causes

Fan Number 1 in Fan Tray 1 has failed.

Troubleshooting instructions

!

1

Dispatch personnel to the site raising the alarm. Be sure to take a spare Fan Tray and a spare air filter for the OTS-4000 shelf.

2

Once on site, replace the air filter in the shelf containing the failed fan. Refer to chapter 4.36 for air filter instructions. Sometimes, this will clear a fan failure alarm. If the FN11F alarm persists after replacing the air filter, continue to step 3.

3

Unlatch and withdraw Fan Tray 1 from the shelf. Inspect for the presence of any debris that may be preventing fans from spinning freely. Remove any debris.

4

Carefully re-install the Fan Tray in the shelf. Verify that both green OK LEDs on the Fan Tray light (this will take about 10 seconds). The FN11F alarm should then clear.

5

If the FN11F alarm persists, remove the failed Fan Tray and replace it with a spare. Verify that both green OK LEDs on the new Fan Tray light (this will take about 10 seconds). The FN11F alarm should then clear. Note: Each Fan Tray is replaceable as a complete assembly only. Individual interior components are not available as spares.

Warning! Never remove more than one Fan Tray from the shelf at a time. Before removing a faulty Fan Tray, have the replacement readily at hand. Do not delay insertion of the new Fan Tray.

6

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

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

81

Troubleshooting Instructions

3.1.40

Troubleshooting Manual (TSMN)

FN12F

Alarm name

Cooling Fan12 Failure (FN12F)

Default severity

Major

Alarm object

OTS-4000 shelf

General information and causes

Fan Number 2 in Fan Tray 1 has failed.

Troubleshooting instructions

!

1

Dispatch personnel to the site raising the alarm. Be sure to take a spare Fan Tray and a spare air filter for the OTS-4000 shelf.

2

Once on site, replace the air filter in the shelf containing the failed fan. Refer to chapter 4.36 for air filter instructions. Sometimes, this will clear a fan failure alarm. If the FN12F alarm persists after replacing the air filter, continue to step 3.

3

Unlatch and withdraw Fan Tray 1 from the shelf. Inspect for the presence of any debris that may be preventing fans from spinning freely. Remove any debris.

4

Carefully re-install the Fan Tray in the shelf. Verify that both green OK LEDs on the Fan Tray light (this will take about 10 seconds). The FN12F alarm should then clear.

5

If the FN12F alarm persists, remove the failed Fan Tray and replace it with a spare. Verify that both green OK LEDs on the new Fan Tray light (this will take about 10 seconds). The FN12F alarm should then clear. Note: Each Fan Tray is replaceable as a complete assembly only. Individual interior components are not available as spares.

Warning! Never remove more than one Fan Tray from the shelf at a time. Before removing a faulty Fan Tray, have the replacement readily at hand. Do not delay insertion of the new Fan Tray.

6

82

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

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

Troubleshooting Manual (TSMN)

3.1.41

Troubleshooting Instructions

FN21F

Alarm name

Cooling Fan21 Failure (FN21F)

Default severity

Major

Alarm object

OTS-4000 shelf

General information and causes

Fan Number 1 in Fan Tray 2 has failed.

Troubleshooting instructions

!

1

Dispatch personnel to the site raising the alarm. Be sure to take a spare Fan Tray and a spare air filter for the OTS-4000 shelf.

2

Once on site, replace the air filter in the shelf containing the failed fan. Refer to chapter 4.36 for air filter instructions. Sometimes, this will clear a fan failure alarm. If the FN21F alarm persists after replacing the air filter, continue to step 3.

3

Unlatch and withdraw Fan Tray 2 from the shelf. Inspect for the presence of any debris that may be preventing fans from spinning freely. Remove any debris.

4

Carefully re-install the Fan Tray in the shelf. Verify that both green OK LEDs on the Fan Tray light (this will take about 10 seconds). The FN21F alarm should then clear.

5

If the FN21F alarm persists, remove the failed Fan Tray and replace it with a spare. Verify that both green OK LEDs on the new Fan Tray light (this will take about 10 seconds). The FN21F alarm should then clear. Note: Each Fan Tray is replaceable as a complete assembly only. Individual interior components are not available as spares.

Warning! Never remove more than one Fan Tray from the shelf at a time. Before removing a faulty Fan Tray, have the replacement readily at hand. Do not delay insertion of the new Fan Tray.

6

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

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

83

Troubleshooting Instructions

3.1.42

Troubleshooting Manual (TSMN)

FN22F

Alarm name

Cooling Fan22 Failure (FN22F)

Default severity

Major

Alarm object

OTS-4000 shelf

General information and causes

Fan Number 2 in Fan Tray 2 has failed.

Troubleshooting instructions

!

1

Dispatch personnel to the site raising the alarm. Be sure to take a spare Fan Tray and a spare air filter for the OTS-4000 shelf.

2

Once on site, replace the air filter in the shelf containing the failed fan. Refer to chapter 4.36 for air filter instructions. Sometimes, this will clear a fan failure alarm. If the FN22F alarm persists after replacing the air filter, continue to step 3.

3

Unlatch and withdraw Fan Tray 2 from the shelf. Inspect for the presence of any debris that may be preventing fans from spinning freely. Remove any debris.

4

Carefully re-install the Fan Tray in the shelf. Verify that both green OK LEDs on the Fan Tray light (this will take about 10 seconds). The FN22F alarm should then clear.

5

If the FN22F alarm persists, remove the failed Fan Tray and replace it with a spare. Verify that both green OK LEDs on the new Fan Tray light (this will take about 10 seconds). The FN22F alarm should then clear. Note: Each Fan Tray is replaceable as a complete assembly only. Individual interior components are not available as spares.

Warning! Never remove more than one Fan Tray from the shelf at a time. Before removing a faulty Fan Tray, have the replacement readily at hand. Do not delay insertion of the new Fan Tray.

6

84

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

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

Troubleshooting Manual (TSMN)

3.1.43

Troubleshooting Instructions

FN31F

Alarm name

Cooling Fan31 Failure (FN31F)

Default severity

Major

Alarm object

OTS-4000 shelf

General information and causes

Fan Number 1 in Fan Tray 3 has failed.

Troubleshooting instructions

!

1

Dispatch personnel to the site raising the alarm. Be sure to take a spare Fan Tray and a spare air filter for the OTS-4000 shelf.

2

Once on site, replace the air filter in the shelf containing the failed fan. Refer to chapter 4.36 for air filter instructions. Sometimes, this will clear a fan failure alarm. If the FN31F alarm persists after replacing the air filter, continue to step 3.

3

Unlatch and withdraw Fan Tray 3 from the shelf. Inspect for the presence of any debris that may be preventing fans from spinning freely. Remove any debris.

4

Carefully re-install the Fan Tray in the shelf. Verify that both green OK LEDs on the Fan Tray light (this will take about 10 seconds). The FN31F alarm should then clear.

5

If the FN31F alarm persists, remove the failed Fan Tray and replace it with a spare. Verify that both green OK LEDs on the new Fan Tray light (this will take about 10 seconds). The FN31F alarm should then clear. Note: Each Fan Tray is replaceable as a complete assembly only. Individual interior components are not available as spares.

Warning! Never remove more than one Fan Tray from the shelf at a time. Before removing a faulty Fan Tray, have the replacement readily at hand. Do not delay insertion of the new Fan Tray.

6

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

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

85

Troubleshooting Instructions

3.1.44

Troubleshooting Manual (TSMN)

FN32F

Alarm name

Cooling Fan32 Failure (FN32F)

Default severity

Major

Alarm object

OTS-4000 shelf

General information and causes

Fan Number 2 in Fan Tray 3 has failed.

Troubleshooting instructions

!

1

Dispatch personnel to the site raising the alarm. Be sure to take a spare Fan Tray and a spare air filter for the OTS-4000 shelf.

2

Once on site, replace the air filter in the shelf containing the failed fan. Refer to chapter 4.36 for air filter instructions. Sometimes, this will clear a fan failure alarm. If the FN32F alarm persists after replacing the air filter, continue to step 3.

3

Unlatch and withdraw Fan Tray 3 from the shelf. Inspect for the presence of any debris that may be preventing fans from spinning freely. Remove any debris.

4

Carefully re-install the Fan Tray in the shelf. Verify that both green OK LEDs on the Fan Tray light (this will take about 10 seconds). The FN32F alarm should then clear.

5

If the FN32F alarm persists, remove the failed Fan Tray and replace it with a spare. Verify that both green OK LEDs on the new Fan Tray light (this will take about 10 seconds). The FN32F alarm should then clear. Note: Each Fan Tray is replaceable as a complete assembly only. Individual interior components are not available as spares.

Warning! Never remove more than one Fan Tray from the shelf at a time. Before removing a faulty Fan Tray, have the replacement readily at hand. Do not delay insertion of the new Fan Tray.

6

86

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

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

Troubleshooting Manual (TSMN)

3.1.45

Troubleshooting Instructions

FN1CF

Alarm name

Cooling Fan1 Comm Failure (FN1CF)

Default severity

Major

Alarm object

OTS-4000 shelf

General information and causes

This alarm will be raised if communication between Fan Tray 1 and the OTS-4700 Controller card has failed.

Troubleshooting instructions 1

Are all three Fan Communication alarms (FN1CF, FN2CF, and FN3CF) raised simultaneously? – –

Warning!

!

3.1.46

Yes: Cold Start the OTS-4700 Controller card in the shelf raising the alarm. This should clear the alarm. No, only the FN1CF alarm is raised: replace Fan Tray 1 with a spare at the earliest convenience. Verify that both green OK LEDs on the new Fan Tray light (this will take about 10 seconds). The FN1CF alarm should then clear. If the alarm persists, Cold Start the OTS-4700 Controller card.

Never remove more than one Fan Tray from the shelf at a time. Before removing a faulty Fan Tray, have the replacement readily at hand. Do not delay insertion of the new Fan Tray.

2

If the alarm persists, replace the OTS-4700 Controller card with a spare.

3

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

FN2CF

Alarm name

Cooling Fan2 Comm Failure (FN2CF)

Default severity

Major

Alarm object

OTS-4000 shelf

General information and causes

This alarm will be raised if communication between Fan Tray 2 and the OTS-4700 Controller card has failed.

Troubleshooting instructions 1

Are all three Fan Communication alarms (FN1CF, FN2CF, and FN3CF) raised simultaneously? – –

Yes: Cold Start the OTS-4700 Controller card in the shelf raising the alarm. This should clear the alarm. No, only the FN2CF alarm is raised: replace Fan Tray 2 with a spare at the earliest convenience. Verify that both green OK LEDs on the new Fan Tray light

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

87

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

(this will take about 10 seconds). The FN2CF alarm should then clear. If the alarm persists, Cold Start the OTS-4700 Controller card. Warning!

!

3.1.47

Never remove more than one Fan Tray from the shelf at a time. Before removing a faulty Fan Tray, have the replacement readily at hand. Do not delay insertion of the new Fan Tray.

2

If the alarm persists, replace the OTS-4700 Controller card with a spare.

3

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

FN3CF

Alarm name

Cooling Fan3 Comm Failure (FN3CF)

Default severity

Major

Alarm object

OTS-4000 shelf

General information and causes

This alarm will be raised if communication between Fan Tray 3 and the OTS-4700 Controller card has failed.

Troubleshooting instructions 1

Are all three Fan Communication alarms (FN1CF, FN2CF, and FN3CF) raised simultaneously? – –

Warning!

!

88

Yes: Cold Start the OTS-4700 Controller card in the shelf raising the alarm. This should clear the alarm. No, only the FN3CF alarm is raised: replace Fan Tray 3 with a spare at the earliest convenience. Verify that both green OK LEDs on the new Fan Tray light (this will take about 10 seconds). The FN3CF alarm should then clear. If the alarm persists, Cold Start the OTS-4700 Controller card.

Never remove more than one Fan Tray from the shelf at a time. Before removing a faulty Fan Tray, have the replacement readily at hand. Do not delay insertion of the new Fan Tray.

2

If the alarm persists, replace the OTS-4700 Controller card with a spare.

3

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

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

Troubleshooting Manual (TSMN)

3.1.48

Troubleshooting Instructions

FN1M

Alarm name

Cooling Fan 1 Missing (FN1M)

Default severity

Minor

Alarm object

OTS-4000 shelf

General information and causes

Fan Tray 1 is detected as missing from the shelf.

Troubleshooting instructions

3.1.49

1

Install the missing Fan Tray in the shelf. If the Fan Tray was already present, ensure that it is completely installed and latched in the shelf.

2

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

FN2M

Alarm name

Cooling Fan 2 Missing (FN2M)

Default severity

Minor

Alarm object

OTS-4000 shelf

General information and causes

Fan Tray 2 is detected as missing from the shelf.

Troubleshooting instructions

3.1.50

1

Install the missing Fan Tray in the shelf. If the Fan Tray was already present, ensure that it is completely installed and latched in the shelf.

2

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

FN3M

Alarm name

Cooling Fan 3 Missing (FN3M)

Default severity

Minor

Alarm object

OTS-4000 shelf

General information and causes

Fan Tray 3 is detected as missing from the shelf.

Troubleshooting instructions 1

Install the missing Fan Tray in the shelf. If the Fan Tray was already present, ensure that it is completely installed and latched in the shelf.

2

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

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

89

Troubleshooting Instructions

3.1.51

Troubleshooting Manual (TSMN)

FNLOW

Alarm name

Lower Cooling Fan Fail (FNLOW)

Default severity

Minor

Alarm object

All shelf types (except OTS-4000, HDS, and MCU-Slim shelf)

General information and causes

A shelf will raise the FNLOW alarm if one or more of the individual fans in the lower fan unit has failed.

Troubleshooting instructions 1

Open the shelf front door. Refer to Figure 12. Unlatch and withdraw the failed fan unit from the shelf. Inspect for the presence of any debris that may be preventing one or more fans from spinning freely. Remove any debris.

2

Carefully re-install the lower fan unit in the shelf. Make sure the fan unit is fully snapped into place so that the fan unit's connector engages properly with the connector on the shelf. Close the shelf front door.

3

If the FNLOW alarm persists, remove the failed lower fan unit and replace it with a spare. Close the shelf front door. Note the following: –

–

– 4

Each fan unit is replaceable as a complete assembly only. Individual interior components are not available as spares. The upper and lower fan units are identical (same part number). The upper and lower fan units provide complete redundancy for their shelf. Cooling airflow is sufficient when only one fan unit is functioning. So, replacement of a failed fan unit is not urgent, but should be performed as soon as practical. If both fan units in a shelf fail, the shelf will raise the SRCP (Subrack Cooling Problem) alarm.

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

Figure 12

90

MTS shelf Lower Fan Unit

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

Troubleshooting Manual (TSMN)

3.1.52

Troubleshooting Instructions

FNLOWM

Alarm name

Lower Cooling Fan Missing (FNLOWM)

Default severity

Minor

Alarm object

All shelf types (except OTS-4000, HDS, and MCU-Slim shelf)

General information and causes

A shelf will raise the FNLOWM alarm if the lower fan unit is not installed properly in the shelf.

Troubleshooting instructions 1

Open the shelf front door: – –

3.1.53

If there is no lower fan unit present, install one. If a lower fan unit is present, it may not be fully snapped into place. Unlatch and withdraw the lower fan unit from the shelf. Carefully re-install the lower fan unit in the shelf. Make sure the fan unit is fully snapped into place so that the fan unit's connector engages properly with the connector on the shelf.

2

Close the shelf front door.

3

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

FNUPP

Alarm name

Upper Cooling Fan Fail (FNUPP)

Default severity

Minor

Alarm object

All shelf types (except OTS-4000, HDS, and MCU-Slim shelf)

General information and causes

A shelf will raise the FNLOW alarm if one or more of the individual fans in the upper fan unit has failed.

Troubleshooting instructions 1

Open the shelf front door. Refer to Figure 13. Unlatch and withdraw the failed fan unit from the shelf. Inspect for the presence of any debris that may be preventing one or more fans from spinning freely. Remove any debris.

2

Carefully re-install the upper fan unit in the shelf. Make sure the fan unit is fully snapped into place so that the fan unit's connector engages properly with the connector on the shelf. Close the shelf front door.

3

If the FNUPP alarm persists, remove the failed upper fan unit and replace it with a spare. Close the shelf front door. Note the following: –

–

Each fan unit is replaceable as a complete assembly only. Individual interior components are not available as spares. The upper and lower fan units are identical (same part number). The upper and lower fan units provide complete redundancy for their shelf. Cooling airflow is sufficient when only one fan unit is functioning. So, replacement of a failed fan unit is not urgent, but should be performed as soon as practical.

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

91

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

– 4

If both fan units in a shelf fail, the shelf will raise the SRCP (Subrack Cooling Problem) alarm.

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

Figure 13

3.1.54

MTS shelf Upper Fan Unit

FNUPPM

Alarm name

Upper Cooling Fan Missing (FNUPPM)

Default severity

Minor

Alarm object

All shelf types (except OTS-4000, HDS, and MCU-Slim shelf)

General information and causes

A shelf will raise the FNUPPM alarm if the upper fan unit is not installed properly in the shelf.

Troubleshooting instructions 1

Open the shelf front door: – –

92

If there is no upper fan unit present, install one. If an upper fan unit is present, it may not be fully snapped into place. Unlatch and withdraw the upper fan unit from the shelf. Carefully re-install the upper fan unit in the shelf. Make sure the fan unit is fully snapped into place so that the fan unit's connector engages properly with the connector on the shelf.

2

Close the shelf front door.

3

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

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

Troubleshooting Manual (TSMN)

3.1.55

Troubleshooting Instructions

FREQNOTSUP

Alarm name

Line Card Frequency Not Supported (FREQNOTSUP)

Default severity

Major

Alarm object

The FREQNOTSUP alarm can be raised by: • •

General information and causes

OTS-4520 (TDCM) cards. “V3” versions of OTS-4040, OTS-4400, and OTS-4011 cards.

See troubleshooting instructions below.

Troubleshooting instructions 1

Go to the appropriate chapter below for troubleshooting instructions, depending on the card type raising the FREQNOTSUP alarm: – –

3.1.55.1

OTS-4520 card is raising the alarm: go to chapter 3.1.55.1. OTS-4040 V3, OTS-4400 V3, or OTS-4011 V3 card is raising the alarm: go to chapter 3.1.55.2.

FREQNOTSUP raised by an OTS-4520 (TDCM) card Troubleshooting instructions

g The following types of OTS-4520 cards are used in the hiT 7500 system [refer to the hiT 7500 Technical Description (TED) document for complete details]: • •

1

OTS-4520-13 and OTS-4520-23 support the Standard channel grid. OTS-4520-14 and OTS-4520-24 support the Offset channel grid. The operating channel of each OTS-4000 Line card and the TDCM connected to it must be compatible. Example: if an OTS-4000 Line card is configured to operate with an Offset-grid channel, but the TDCM connected to it is a Standardgrid type, a FREQNOTSUP alarm will be raised.

Determine which OTS-4000 Line Card is associated with the TDCM card raising the alarm (see Caution statement below about OTS-4400 Regenerator pairs). Verify that this Line Card is operating on the intended frequency by checking the following (as applicable): –

–

If Internal Port Connections (IPC), were originally used to set this Line Card's frequency, verify that they are configured as intended. Go to Equipment View: Configuration > Internal Port Connections. If IPC are configured incorrectly, delete them and re-create them as required. If manual wavelength selection (instead of IPC) was originally used to set this Line Card's frequency, check its Downstream Frequency setting. Go to Equipment View: Card > Output Frequency. If the Downstream Frequency is set incorrectly, change the setting to the correct value.

2

Once the Line Card's frequency is set correctly, the FREQNOTSUP alarm should clear. If the alarm persists, continue to step 3.

3

Since it is assumed that the operating frequency is now set correctly (from steps 1 and 2), then a still-active FREQNOTSUP alarm indicates that the problem is with the

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

93

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

TDCM card. The TDCM card raising the alarm does not support the operating frequency of the OTS-4000 Line Card connected to it. Dispatch personnel to the site to replace the TDCM card with the other TDCM type (Standard grid or Offset grid as appropriate). After the card is replaced, the FREQNOTSUP alarm should clear. 4

!

!

3.1.55.2

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

Caution! Note the following behavior for TDCMs used with OTS-4400 Regenerator cards. Since OTS-4400 cards must be deployed in pairs, the TDCM cards assigned to them base the FREQNOTSUP alarm on the Transmit frequency of the paired OTS-4400 card. Example: Suppose a pair of OTS-4400 cards are installed in Slots 4 and 5. And, suppose the OTS-4400 in Slot 4 is assigned to the TDCM card in Slot 6, and the OTS4400 card in Slot 5 is assigned to the TDCM in Slot 7. If the frequency of the OTS-4400 in Slot 4 is configured incorrectly, the FREQNOTSUP alarm will be raised by the TDCM in Slot 7 - not the TDCM in Slot 6. In other words, even though the incorrectly configured OTS-4400 is assigned to the TDCM in Slot 6, it is the other TDCM which raises the FREQNOTSUP alarm. Keep this behavior in mind when troubleshooting this alarm.

Caution! 40G Line Card operating frequency must be set to match the channel of the mux/demux port to which it is connected.

FREQNOTSUP raised by an OTS-4xxx V3 card Troubleshooting instructions

g the “V3” versions of OTS-4040, OTS-4400, and OTS-4011 cards are available in two types - one type for "standard grid" and one type for "offset grid". While both types support chanels spaced 100 GHz apart, the “standard” type supports channels of the ITU 100 GHz grid, while the “offset” type supports channels offset by 50 GHz. These card types have built-in Tunable Dispersion Compensators. 1

Deployment of OTS-4xxx V3 cards must be according to the following rules. If any of the following rules are violated, fix the problem and the FREQNOTSUP alarm will clear. •

•

•

2

94

For any particular V3 Transponder (OTS-4040 V3 or OTS-4011 V3), the transmitted frequency and the receive frequency AT THIS PARTICULAR CARD must be the the same type (standard grid or offset grid). For V3 Regen cards (OTS-4400 V3), the transmitted frequency type of one regen card must match the supported received frequency type of its PARTNER regen card (remember that these cards are deployed in pairs). The V3 cards serving an end-to-end channel do NOT NECESSARILY NEED to be the same type (example: you may have mid-span regen cards translate the frequency from standard-to-offset or offset-to-standard). Any arrangement of cards and frequency assignments that satisfy points 1) and 2) above is valid.

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

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

Troubleshooting Manual (TSMN)

3.1.56

Troubleshooting Instructions

GNELOS

Alarm name

Connection Loss to NE (GNELOS)

Default severity

Major

Alarm object

MCU-GNE card

General information and causes

Refer to Figure 14. All NEs that have been detected by the Element Manager System (EMS) are periodically checked to determine if they are still reachable (a proprietary "ping" signal is sent). If an NE does not respond, a GNELOS alarm is raised to indicate that this NE is no longer reachable. If the NE responds correctly to the next ping, the GNELOS alarm will be automatically cleared. Note: the interval between ping signals is user-configurable via the Connection Supervision Interval field on the GNE “Functional View” window.

Troubleshooting instructions 1

Is it possible to communicate with the affected network element via the redundant GNE? – –

2

Refer to Figure 14 and check the following: –

–

–

– 3

No, the redundant GNE is also reporting a GNELOS alarm for this NE: go to step 2. Yes, the redundant GNE is not reporting a GNELOS alarm for this NE: in this case, communication with the network element is possible via the redundant GNE. Solution: the problem is likely in the DCN connectivity; incorrect or changed IP Addressing. Check all assigned IP addresses and correct as necessary. Then, skip step 2 and go directly to step 3. If GNELOS is reported for a compound network element, check if the MCU-CNE card in that NE is reporting a CP (Card Problem) or CFAIL (Card Failed) alarm. A failed MCU-CNE card will cause a GNELOS alarm (Failure #1 in Figure 14). Refer to the CP alarm and CFAIL alarm troubleshooting instructions. DC power problems that cause a shutdown of the MCU-CNE card will also cause a GNELOS alarm. So, check for shelf Power (PWR) alarms in the affected NE. If any are raised, troubleshoot according to PWR1, PWR2, PWR3, and PWR4 alarm instructions. A failed Ethernet Switch, or an Ethernet Switch that has totally lost power (Failure #4 in Figure 14) will also cause a GNELOS alarm. Check for the corresponding Telemetry Interface (TIF) alarm that signifies total power failure to the Ethernet Switch. [The Ethernet Switch cannot report its power failure via an Equipment alarm, but it can activate a housekeeping TIF output]. If no other cause can be found, a cable failure is likely. Cable failures (Failures #2 and #3 in Figure 14) will also cause a GNELOS alarm.

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

g A separate GNELOS alarm will be raised by an MCU-GNE for each network element it loses communications with, including the far-end MCU-GNE.

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

95

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

g When a “GNELOS” alarm is raised (displayed on Element Manager / LCT GUIs), a corresponding “Connection Loss to NE (GNELOS)” alarm will also be raised (displayed on TNMS CT and TNMS DX Alarm Lists). Important: a similarly-named alarm, “Connection Loss to GNE” is raised under different circumstances (see explanation in Figure 15). Just like “Connection Loss to NE (GNELOS)”, this alarm is also displayed only on the TNMS CT and TNMS DX Alarm Lists, i.e., it is not an Element Manager alarm.

96

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

Troubleshooting Manual (TSMN)

Figure 14

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

Troubleshooting Instructions

GNELOS alarm causes

97

Troubleshooting Instructions

Figure 15

98

Troubleshooting Manual (TSMN)

“Connection Loss to GNE” alarm causes

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

Troubleshooting Manual (TSMN)

3.1.57

Troubleshooting Instructions

GTMMP

Alarm name

Gain Tilt Monitor Module Problem (GTMMP)

Default severity

Major

Alarm object

This alarm is raised only by OLI card types that are equipped with the Gain Tilt Monitor (GTM): – – –

General information and causes

OLITB with GTM OLII with GTM OLITP with GTM

The GTMMP alarm is raised if the indicated OLI card detects a failure of its onboard Gain Tilt Monitor. As a result of this failure, no Scan Spectrum Measurement is possible by the affected OLI. Also, the Gain Tilt measurement by this OLI card is no longer reliable.

Troubleshooting instructions 1

Is traffic affected due to the GTMMP condition? –

–

2

3.1.58

Yes: Warm Start the card raising the GTMMP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the GTMMP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

GTP

Alarm name

Gain Tilt Problem (GTP)

Default severity

Minor

Alarm object

Pre-amplifier and In-Line Amplifier OLI card types (OLIPxx and OLIIxx types).

General information and causes

The GTP alarm is raised if the OLI pre-tilt reaches its upper or lower limit. This can be caused by: • •

a stuck switch in the OPAPC in the local NE or the next downstream NE. a stuck VOA in the local OLI.

Traffic may or may not be affected by the cause of the GTP alarm. However, note that traffic may be affected before this alarm is raised, especially if the cause is a stuck OPAPC switch at an ADU or ADN network element.

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

99

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions 1

Refer to Figure 16 and note the following. – –

OPAPCs are not present at each NE. They are installed only at every second NE as shown. Each OPAPC provides gain tilt data to the OLIs in the same NE and to the OLI in the NE immediately upstream. Example: OPAPC 3 provides gain tilt data to its "local" OLIs (OLI 3a and OLI 3b) and to the upstream OLIs (OLI 2a and OLI 4b).

Figure 16 2

Warm Start the OPAPC card that provides the gain tilt data for the OLI card raising the GTP alarm. The correct OPAPC card can be determined by the following rules: – –

–

If the OLI card raising the GTP alarm is part of an NE that contains an OPAPC card, Warm Start the OPAPC in that same NE. If the OLI card raising the GTP alarm is part of an NE that does not contain an OPAPC card, Warm Start the OPAPC that is present in the next adjacent downstream NE. Examples (refer to Figure 17): If OLI 1a raises the GTP alarm, Warm Start OPAPC 1. If OLI 2a raises the GTP alarm, Warm Start OPAPC 3.

Figure 17

100

Arrangement of OPAPCs in a network

Determining which OPAPC to Warm Start

3

If the alarm persists after Warm Start recovery time (approx 3 minutes), Cold Start the same OPAPC. If the alarm persists after Cold Start recovery time (approx 3 minutes), go to Step 4.

4

Warm Start the OLI card raising the GTP alarm. If the alarm persists after Warm Start recovery time (approx 3 minutes), go to Step 5.

5

If the alarm has not cleared, dispatch personnel to the NE that contains the relevant OPAPC card (as determined in Step 2). Replace the OPAPC card with a spare.

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

Troubleshooting Manual (TSMN)

3.1.58.1

Troubleshooting Instructions

6

If the alarm has not cleared, contact your next level of technical support before proceeding since the following action is traffic-affecting. Cold Start the OLI card raising the GTP alarm.

7

If the alarm persists after Cold Start recovery time (approx 3 minutes), contact your next level of technical support before proceeding since the following action is trafficaffecting. Dispatch personnel to the NE that contains the OLI card raising the alarm. Replace this OLI card with a spare.

8

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

Hints for multiple GTP alarms Example 1: Multiple GTP alarms from OLIs under control of a common OPAPC Multiple GTP alarms may occur in NEs which share the same OPAPC for gain tilt data. As shown in Figure 18, if GTP alarms appear on any combination of OLI 2a, OLI 3a, OLI3b, or OLI 4b, it strongly suggests a problem with OPAPC 3, (not the OLIs raising the alarms) since OPAPC 3 provides gain tilt data for all four of these OLIs. The troubleshooting procedures in chapter 3.1.58 consider such a scenario since they begin with a Warm Start / Cold Start of the OPAPC in an attempt to clear the alarm.

g if a GTP alarm is raised on more than one of these OLIs, it is unlikely the alarms will occur simultaneously. Each OLI may reach the alarm trigger point (VOA at its upper or lower limit) at different times as they adjust their VOA in response to the data provided by the OPAPC.

Figure 18

Multiple GTP alarm diagram

Example 2: Multiple GTP alarms appearing downstream GTP alarms may be raised at NEs downstream from the true source of the problem. This is caused by the downstream NEs attempting to compensate for the gain tilt error caused by the faulty NE. In the example shown in Figure 18, if multiple OLIs are raising a GTP alarm (OLI 1a, OLI 2a, OLI 3a, OLI 4a, and so on), the problem is most likely in the most upstream NE raising the alarm (NE 1 in this example). So, concentrate on NE 1 when using the troubleshooting procedures in chapter 3.1.56. If the problem truly is at NE 1 (OPAPC or OLI at this site), the troubleshooting procedures will fix the problem and also clear all the downstream GTP alarms.

g As in Example 1, these multiple GTP alarms are unlikely to occur simultaneously.

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

101

Troubleshooting Instructions

3.1.59

Troubleshooting Manual (TSMN)

HDS_APSMISS

Alarm name

HDS APS Missing (HDS_APSMISS)

Default severity

Critical

Alarm object

Master MCU card

General information and causes

The HDS Software (H73 APS) is detected as missing.

Troubleshooting instructions

3.1.60

1

Download the HDS Software (H73 APS) to the card. This is done via the HDS Software tab on the “Software Management” window.

2

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

HDSRECOVERMODE

Alarm name

HDS Recover Mode (HDSRECOVERMODE)

Default severity

Critical

Alarm object

CCEP and CCMP Controller cards

General information and causes

The card raising the alarm has entered the Recovery Mode.

Troubleshooting instructions 1

The HDSRECOVERMODE alarm indicates that the card has entered the Recovery Mode. This is typically due to one of the following events: • • •

102

The Compact Flash on the card contains the wrong APS. The Compact Flash on the card does not contain any APS. The Compact Flash and the card do not have any MIB.

2

Troubleshoot the HDSRECOVERMODE alarm via the instructions for the MIBF alarm and the APSM alarm.

3

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

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

Troubleshooting Manual (TSMN)

3.1.61

Troubleshooting Instructions

ICP

Alarm name

Internal Communication Problem (ICP)

Default severity

Major

Alarm object

MCU card

General information and causes

The ICP alarm will be raised if there is a failure in the automatic evaluation of Channelized FBG or DCF Delay.

Troubleshooting instructions

3.1.62

1

Open the “Card Configuration” window for each DCM installed in the network element raising the ICP alarm. To do so, right-click on the DCM card replica in the Equipment View and select Card > Configuration. Verify that the Related Card field is set correctly for each DCM (ensure that the OLI card related to each DCM is specified correctly). If an incorrect OLI card was entered in the Related Card field, enter the correct value.

2

Open this NE's “Subsystem Configuration” window. Disable the Delay of DCF Automatic Setup checkbox. Then, re-enable it again. The ICP alarm should now clear.

3

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

ILOL

Alarm name

Input Loss of Light (ILOL)

Default severity

Major

Alarm object

OTS-4520 (TDCM) card and OTS-4540 (PMDC) card

General information and causes

A loss of signal condition has been detected at the input to the indicated card (OTS-4520 or OTS-4540).

Troubleshooting instructions 1

Troubleshoot any upstream alarms first. Then, if the ILOL alarm persists, proceed to Step 2.

2

There may be missing or loose connections at the input to the affected card. Verify that the input fiber cable is properly installed. Disconnect the fiber at the input of the card raising the alarm. Clean the fiber end and the input connector. Then, re-connect the fiber, ensuring that there are no bends or kinks in the fiber. The ILOL alarm should clear when the correct connection is established.

3

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

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

103

Troubleshooting Instructions

3.1.63

Troubleshooting Manual (TSMN)

ILOL1

Alarm name

Input Loss of Light 1 (ILOL1)

Default severity

Minor

Alarm object

TSC card.

General information and causes

Optical power that is input to the TSC card is monitored in three bands. The ILOL1 alarm will be raised if the TSC card detects loss of Band 1.

Troubleshooting instructions 1

Typically, all three ILOL alarms (ILOL1, ILOL2, and ILOL3) will be raised simultaneously. This nearly always means a fiber cut at the input side of the TSC card. Conversely, if only the ILOL1 alarm is raised, it usually means a fiber cut on the output side of the TSC card. Therefore, check the following fiber (listed by NE type). If any fiber is missing, or not connected properly, correct the cabling error. If all fiber is connected properly, the problem may be a dirty connector. In that case, open the TSC card’s Card-Configuration window and disable Transient Suppression. Wait until the Transient Suppression Laser State field changes to “disabled” (this may take a few minutes). Then, disconnect the fiber and clean all connectors. Reconnect the fiber and re-enable Transient Suppression. Verify that the Transient Suppression Laser State field changes back to “enabled” (this may take a few minutes). –

–

–

–

2

104

ADN20 or ADN21: – TSC “Out” to OMDIFC “AuxIn”. – OMDIFC “1C” to CDAN “AddIn”. – CDAN “CtrlOut” to TSC “MonIn”. ADU30 or ADU31 without WSSC: – TSC “Out” to WBAU “UpgIn”. – WBAU “MonExp” to TSC “MonIn”. ADU30 or ADU31 with WSSC: – TSC “Out” to WSSC “AuxIn”. – WSSC “ExpOut” to WBAU “UpgIn”. – WBAU “MonExp” to TSC “MonIn”. ADX37, ADX38, or ADX39: – TSC “Out” to WSSC “AuxIn” – WSSC “ExpOut” to CAX “ExpIn”. – CAX “MonOut” to TSC “MonIn”

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

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

Troubleshooting Manual (TSMN)

3.1.64

Troubleshooting Instructions

ILOL2

Alarm name

Input Loss of Light 2 (ILOL2)

Default severity

Major

Alarm object

TSC card

General information and causes

Optical power that is input to the TSC card is monitored in three bands. The ILOL2 alarm will be raised if the TSC card detects loss of Band 2.

Troubleshooting instructions 1

Typically, all three ILOL alarms (ILOL1, ILOL2, and ILOL3) will be raised simultaneously. This nearly always means a fiber cut at the input side of the TSC card. Conversely, if only the ILOL2 alarm is raised, it usually means a fiber cut on the output side of the TSC card. Therefore, check the following fiber (listed by NE type). If any fiber is missing, or not connected properly, correct the cabling error. If all fiber is connected properly, the problem may be a dirty connector. In that case, open the TSC card’s Card-Configuration window and disable Transient Suppression. Wait until the Transient Suppression Laser State field changes to “disabled” (this may take a few minutes). Then, disconnect the fiber and clean all connectors. Reconnect the fiber and re-enable Transient Suppression. Verify that the Transient Suppression Laser State field changes back to “enabled” (this may take a few minutes). –

–

–

–

2

ADN20 or ADN21: – TSC “Out” to OMDIFC “AuxIn”. – OMDIFC “1C” to CDAN “AddIn”. – CDAN “CtrlOut” to TSC “MonIn”. ADU30 or ADU31 without WSSC: – TSC “Out” to WBAU “UpgIn”. – WBAU “MonExp” to TSC “MonIn”. ADU30 or ADU31 with WSSC: – TSC “Out” to WSSC “AuxIn”. – WSSC “ExpOut” to WBAU “UpgIn”. – WBAU “MonExp” to TSC “MonIn”. ADX37, ADX38, or ADX39: – TSC “Out” to WSSC “AuxIn” – WSSC “ExpOut” to CAX “ExpIn”. – CAX “MonOut” to TSC “MonIn”

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

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

105

Troubleshooting Instructions

3.1.65

Troubleshooting Manual (TSMN)

ILOL3

Alarm name

Input Loss of Light 3 (ILOL3)

Default severity

Major

Alarm object

TSC card

General information and causes

Optical power that is input to the TSC card is monitored in three bands. The ILOL3 alarm will be raised if the TSC card detects loss of Band 3.

Troubleshooting instructions 1

Typically, all three ILOL alarms (ILOL1, ILOL2, and ILOL3) will be raised simultaneously. This nearly always means a fiber cut at the input side of the TSC card. Conversely, if only the ILOL3 alarm is raised, it usually means a fiber cut on the output side of the TSC card. Therefore, check the following fiber (listed by NE type). If any fiber is missing, or not connected properly, correct the cabling error. If all fiber is connected properly, the problem may be a dirty connector. In that case, open the TSC card’s Card-Configuration window and disable Transient Suppression. Wait until the Transient Suppression Laser State field changes to “disabled” (this may take a few minutes). Then, disconnect the fiber and clean all connectors. Reconnect the fiber and re-enable Transient Suppression. Verify that the Transient Suppression Laser State field changes back to “enabled” (this may take a few minutes). –

–

–

–

2

106

ADN20 or ADN21: – TSC “Out” to OMDIFC “AuxIn”. – OMDIFC “1C” to CDAN “AddIn”. – CDAN “CtrlOut” to TSC “MonIn”. ADU30 or ADU31 without WSSC: – TSC “Out” to WBAU “UpgIn”. – WBAU “MonExp” to TSC “MonIn”. ADU30 or ADU31 with WSSC: – TSC “Out” to WSSC “AuxIn”. – WSSC “ExpOut” to WBAU “UpgIn”. – WBAU “MonExp” to TSC “MonIn”. ADX37, ADX38, or ADX39: – TSC “Out” to WSSC “AuxIn” – WSSC “ExpOut” to CAX “ExpIn”. – CAX “MonOut” to TSC “MonIn”

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

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

Troubleshooting Manual (TSMN)

3.1.66

Troubleshooting Instructions

IOPL

Alarm name

Input Optical Power Too Low (IOPL)

Default severity

Major

Alarm object

The IOPL alarm can be raised by the Line In interface of: • •

General information and causes

OTS-4520 TDCM card. OTS-4540 PMDC card.

An IOPL alarm is raised together with an OPR alarm. If the optical power threshold is crossed, an OPR alarm is raised for the line side interface, and an IOPL alarm is raised by the card.

Troubleshooting instructions

3.1.67

1

The IOPL alarm is raised in sympathy with the OPR alarm. To troubleshoot the IOPL alarm, go to the instructions for the OPR alarm.

2

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

ISLP

Alarm name

Interstage Loss Problem (ISLP)

Default severity

Major

Alarm object

OLI cards (all types)

General information and causes

The ISLP alarm is raised if the interstage insertion loss for an OLI card is too high or too low. As shown in Figure 19, the "interstage" portion of an OLI card is defined as between the card's Stage II and Stage III amplifiers. Connectors are provided on the OLI card so that external device(s) such as UDCM, PQM, OMDFC, VOA2, or padded fiber attenuators) can be connected between Stage II and Stage III. If the total attenuation through all devices and fiber between Stage II and Stage III is too high or too low, the OLI card will raise an ISLP alarm. Important: The TransNet Commissioning Report lists the correct minimum and maximum interstage loss for each OLI card in your network. For correct network operation, the interstage loss for each OLI must be within its designated range.

Troubleshooting instructions 1

Verify that any and all interstage device(s) as specified by TransNet for the OLI raising the alarm are installed and cabled correctly. If TransNet specified a UDCM at this location, ensure that it is the exact type indicated. If interstage stuffing attenuation was specified, ensure that the correct attenuator is installed. If any required

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

107

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

interstage device is incorrect or missing, correct the problem to clear the ISLP alarm. If the alarm persists, continue to step 2.

108

2

Interstage device(s) are correct, but bent or kinked fiber connections at one of the points (A - F) in Figure 19 may cause the interstage loss to be too high. So, verify that each cable is properly installed. If a cable is bent/pinched, or improperly connected, correct the problem. The ISLP alarm should clear when the correct connection is established. If the alarm persists, continue to step 3.

3

Check for dirty connectors or damaged patchcords. Disconnect the interstage fiber patchcord(s), clean the optical connectors, and re-connect. If the ISLP alarm persists after cleaning, one or more of the patchcords may be defective. Replace the fiber patchord(s) one by one with cleaned, inspected spares until the alarm clears. (If an interstage stuffing attenuator fiber is used, ensure that any replacement cable is the same rating). If the alarm persists, continue to step 4.

4

The interstage device may be defective. If a UDCM is present, replace it with a spare of the same type and see if the alarm clears. If a PQM is present, replace it with a spare of the same type and see if the alarm clears. If a VOA2 is present, replace it with a spare of the same type and see if the alarm clears. If the alarm persists, continue to step 5.

5

If no other cause can be found, Warm Start the affected OLI card. If the alarm persists after recovery time (approx 3 minutes), Cold Start this OLI. If the alarm persists after recovery time (approx 3 minutes), the OLI card is defective. Replace the OLI card with a spare.

6

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

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

Troubleshooting Manual (TSMN)

Figure 19

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

Troubleshooting Instructions

OLI card interstage devices

109

Troubleshooting Instructions

3.1.68

Troubleshooting Manual (TSMN)

LNREFCLOCKP

Alarm name

Line Ref Clock Problem (LNREFCLOCKP)

Default severity

Major

Alarm object

OTS-4700 Controller card

General information and causes

If the OTS-4700 card’s clock (used for generation of the line signals of the OTS transponders) drifts beyond the allowable accuracy limit, the LNREFCLOCKP alarm will be raised. When this happens, the OTS-4700 card’s clock is automatically switched off and the system uses the local clocks on the transponder cards. If the alarm cannot be quickly cleared via Warm Start or Cold Start, the OTS-4700 should be replaced with a spare at the earliest opportunity.

Troubleshooting instructions

3.1.69

1

Warm Start the OTS-4700 card raising the alarm. If the alarm persists after the card recovers from the Warm Start, Cold Start the card. If the alarm persists after the card recovers from the Cold Start, dispatch personnel to the site to replace the failed card with a spare.

2

After the OTS-4700 card has been replaced, open the OTS-4700 “Card-Config” window. Check that the read-only field named “Line Ref Clock State” reads “enabled” (which means that the clock on the OTS-4700 card is being used).

3

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

LOCNELOS

Alarm name

Connection Loss to Local NE (LOCNELOS)

Default severity

Major

Alarm object

TL1-GNE card

General information and causes

The connection from the TL1-GNE to the supervised NEs is monitored. If the supervised NE is in the same subnet as the TL1-GNE, it is referred to as a Local NE. If such a supervised NE is not reachable (e.g., due to a reboot or network problems), the LOCNELOS alarm will be raised.

Troubleshooting instructions

110

1

Establish the correct cable connections as designated in the SURPASS hiT 7500 Interconnection, Configuration, and Mechanical Assembly (ICMA) document. Once connection to the supervised NE is established, the LOCNELOS alarm will clear.

2

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

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

Troubleshooting Manual (TSMN)

3.1.70

Troubleshooting Instructions

LOSADD

Alarm name

Loss of Add Signal (LOSADD)

Default severity

Critical

Alarm object

WBAU card and CAX card

General information and causes

A WBAU or CAX card will raise a LOSADD alarm if it detects a loss of signal at its "Add In" port (signal from the add-path OLI). The threshold for this alarm is fixed at -6 dBm.

Troubleshooting instructions 1

Troubleshoot any upstream alarms first, especially an OPLOS alarm raised by the “Add Channel” amplifier that feeds the WBAU or CAX raising the LOSADD alarm. If the LOSADD alarm persists, dispatch personnel to the site raising the alarm.

2

Refer to Figure 20, which shows two degrees (ADU30 and ADX38) of a multi-degree OADM100U. This drawing is representative of all OADM100U configurations since the positioning of the WBAU and CAX cards are analagous in other portions (ADU31, ADX37, and ADX39) of any OADM100U. There may be missing or loose connections from the Add Channel amplifier (OLI card) to the AddIn port of the card (WBAU or CAX) raising the LOSADD alarm. Verify that this fiber cable is properly installed. If the cable is missing, bent/pinched, or improperly connected, correct the problem. The LOSADD alarm should clear when the correct connection is established.

3

If the alarm persists, the power of the signal entering the card (WBAU or CAX) may be too low. Disconnect the fiber at the Add In connector of the card. With an optical power meter, measure the optical power being delivered to the end of this cable. Requirement: > - 6 dBm. If the power is too low, clean all optical connectors and reconnect the fiber. If the LOSADD alarm persists after cleaning, replace the fiber cable with a cleaned, inspected spare.

4

If no other cause can be found, Warm Start the card raising the alarm. If the alarm persists after reset recovery time (approx 3 minutes), Cold Start the card. If the alarm persists after recovery time (approx 3 minutes), the card is defective. Replace the card with a spare.

5

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

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

111

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Figure 20

3.1.71

Reference diagram for LOSADD alarm

LOSIn1

Alarm name

Loss of Signal Input 1 (LOSIn1)

Default severity

Major

Alarm object

WSSC card

General information and causes

The WSSC card will raise the LOSIn1 alarm if a loss of signal condition is detected at the card’s In1 port.

Troubleshooting instructions

112

1

Check for alarms raised by upstream equipment. If upstream alarms exist, troubleshoot those alarms first.

2

If the LOSIn1 alarm persists, verify that the fiber cable to the WSSC In1port is properly installed. If the cable is missing, bent/pinched, or improperly connected, correct the problem. The LOSIn1 alarm should clear when the correct connection is

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

established. For convenience, Table 9 lists the fiber connections between ADU30, ADU31, ADX37, ADX38, and ADX39 portions of an OADM100U network element. Determine from this table which fiber is supposed to be connected to a particular WSSC card’s In1 port. 3

If the LOSIn1 alarm persists, disconnect both ends of the fiber leading to the In1 port. Clean all optical connectors and re-connect. If the alarm persists, replace the fiber cable with a cleaned, inspected spare.

4

If the alarm persists, Warm Start the affected WSSC card. If the alarm persists after recovery time (approx 3 minutes), contact your next higher level of technical support before proceeding.

5

Cold Start the WSSC card. If the alarm persists after recovery time (approx 3 minutes), the WSSC card is defective. Replace the WSSC card with a spare.

6

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

TO

Subsystem - Card - Port

Subsystem - Card - Port

ADU30 - CDU - Out1

ADU31 - WBAU - In

ADU30 - CDU - Out2

ADX38 - WSSC - In1

ADU30 - CDU - Out3

ADX39 - WSSC - In1

ADU30 - CDU - Out4

ADX37 - WSSC - In1

ADU31 - CDU - Out1

ADU30 - WBAU - In

ADU31 - CDU - Out2

ADX38 - WSSC - In2

ADU31 - CDU - Out3

ADX39 - WSSC - In2

ADU31 - CDU - Out4

ADX37 - WSSC - In2

ADX38 - CDU - Out1

ADU30 - WSSC - In1

ADX38 - CDU - Out2

ADU31 - WSSC - In1

ADX38 - CDU - Out3

ADX39 - WSSC - In3

ADX38 - CDU - Out4

ADX37 - WSSC - In3

ADX39 - CDU - Out1

ADU30 - WSSC - In2

ADX39 - CDU - Out2

ADU31 - WSSC - In2

ADX39 - CDU - Out3

ADX38 - WSSC - In3

ADX39 - CDU - Out4

ADX37 - WSSC - In4

Table 9

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

OADM100U Fiber Interconnections (for up to a 4 x 4 PXC)

113

Troubleshooting Instructions

3.1.72

Troubleshooting Manual (TSMN)

LOSIn2

Alarm name

Loss of Signal Input 2 (LOSIn2)

Default severity

Major

Alarm object

WSSC card

General information and causes

The WSSC card will raise the LOSIn2 alarm if a loss of signal condition is detected at the card’s In2 port.

Troubleshooting instructions

3.1.73

1

Check for alarms raised by upstream equipment. If upstream alarms exist, troubleshoot those alarms first.

2

If the LOSIn2 alarm persists, verify that the fiber cable to the WSSC In2 port is properly installed. If the cable is missing, bent/pinched, or improperly connected, correct the problem. The LOSIn2 alarm should clear when the correct connection is established. For convenience, Table 9 lists the fiber connections between ADU30, ADU31, ADX37, ADX38, and ADX39 portions of an OADM100U network element. Determine from this table which fiber is supposed to be connected to a particular WSSC card’s In2 port.

3

If the LOSIn2 alarm persists, disconnect both ends of the fiber leading to the In2 port. Clean all optical connectors and re-connect. If the alarm persists, replace the fiber cable with a cleaned, inspected spare.

4

If the alarm persists, Warm Start the affected WSSC card. If the alarm persists after recovery time (approx 3 minutes), contact your next higher level of technical support before proceeding.

5

Cold Start the WSSC card. If the alarm persists after recovery time (approx 3 minutes), the WSSC card is defective. Replace the WSSC card with a spare.

6

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

LOSIn3

Alarm name

Loss of Signal Input 3 (LOSIn3)

Default severity

Major

Alarm object

WSSC card

General information and causes

The WSSC card will raise the LOSIn3 alarm if a loss of signal condition is detected at the card’s In3 port.

Troubleshooting instructions

114

1

Check for alarms raised by upstream equipment. If upstream alarms exist, troubleshoot those alarms first.

2

If the LOSIn3 alarm persists, verify that the fiber cable to the WSSC In3 port is properly installed. If the cable is missing, bent/pinched, or improperly connected, correct the problem. The LOSIn3 alarm should clear when the correct connection is

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

established. For convenience, Table 9 lists the fiber connections between ADU30, ADU31, ADX37, ADX38, and ADX39 portions of an OADM100U network element. Determine from this table which fiber is supposed to be connected to a particular WSSC card’s In3 port.

3.1.74

3

If the LOSIn3 alarm persists, disconnect both ends of the fiber leading to the In3 port. Clean all optical connectors and re-connect. If the alarm persists, replace the fiber cable with a cleaned, inspected spare.

4

If the alarm persists, Warm Start the affected WSSC card. If the alarm persists after recovery time (approx 3 minutes), contact your next higher level of technical support before proceeding.

5

Cold Start the WSSC card. If the alarm persists after recovery time (approx 3 minutes), the WSSC card is defective. Replace the WSSC card with a spare.

6

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

LOSIn4

Alarm name

Loss of Signal Input 4 (LOSIn4)

Default severity

Major

Alarm object

WSSC card

General information and causes

The WSSC card will raise the LOSIn4 alarm if a loss of signal condition is detected at the card’s In4 port.

Troubleshooting instructions 1

Check for alarms raised by upstream equipment. If upstream alarms exist, troubleshoot those alarms first.

2

If the LOSIn4 alarm persists, verify that the fiber cable to the WSSC In4 port is properly installed. If the cable is missing, bent/pinched, or improperly connected, correct the problem. The LOSIn4 alarm should clear when the correct connection is established. For convenience, Table 9 lists the fiber connections between ADU30, ADU31, ADX37, ADX38, and ADX39 portions of an OADM100U network element. Determine from this table which fiber is supposed to be connected to a particular WSSC card’s In4 port.

3

If the LOSIn4 alarm persists, disconnect both ends of the fiber leading to the In4 port. Clean all optical connectors and re-connect. If the alarm persists, replace the fiber cable with a cleaned, inspected spare.

4

If the alarm persists, Warm Start the affected WSSC card. If the alarm persists after recovery time (approx 3 minutes), contact your next higher level of technical support before proceeding.

5

Cold Start the WSSC card. If the alarm persists after recovery time (approx 3 minutes), the WSSC card is defective. Replace the WSSC card with a spare.

6

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

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

115

Troubleshooting Instructions

3.1.75

Troubleshooting Manual (TSMN)

LSBFAIL

Alarm name

Laser Safety Bus Failure (LSBFAIL)

Default severity

Minor

Alarm object

HDS shelf

General information and causes

The LSBFAIL alarm will be raised if the indicated shelf detects a failure of the Laser Safety Bus (also known as the APSD bus.

Troubleshooting instructions

3.1.76

1

Verify that the APSD IN / APSD OUT cable connections are correctly made to the shelf indicating the LSBFAIL alarm as directed in the Interconnection and Mechanical Assembly (ICMA) manual. Correct any cabling errors.

2

If the alarm persists, replace the APSD IN and APSD OUT cables connected to the shelf raising the alarm. If there was a bad cable, this should clear the alarm.

3

If the alarm persists, Warm Start the Controller card in the shelf raising the alarm. If the alarm persists, Cold Start that card.

4

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

LSS

Alarm name

Loss of Sequence Synchronization (LSS)

Default severity

Minor

Alarm object

OCR10T-V5 and TEX-V5 Transponder cards

General information and causes

V5 transponder cards support generation and detection of a PRBS (Pseudo-Random Bit Sequence) signal for test purposes. The LSS alarm will be raised if the indicated card does not detect the PRBS. For testing, the typical procedure is to provision a transponder at one end of a link to send a PRBS signal in the ODU2 payload. The matching receive transponder at the other end of the link is provisioned to detect the PRBS signal. If the PRBS is not detected at the receive end, the cause is likely incorrect cable connections, high bit errors on the line, or incorrect PRBS provisioning.

Troubleshooting instructions 1

116

Verify that the two transponder cards under test have the correct PRBS settings. On the “Line Traffic Configuration” window for each of the two cards, one card must be

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

set to PRBS Source and the other cad must be set to PRBS Sink. When set correctly, the test should work and the LSS alarm will clear.

3.1.77

2

If the alarm persists, verify that there has not been a cabling mistake. Check the endto-end path connections via the ODU2 TTI (Trail Trace Identifier) feature for the two cards under test. If the transmitted and received TTI strings do not match, then there is a cabling mistake somewhere. Correct the cabling error and re-test. The LSS alarm should clear.

3

If this does not clear the alarm, the problem may be due to a high bit error rate on the line. Follow the troubleshooting procedure for the LOS alarm and/or the SD/DEG alarm.

4

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

MEASF

Alarm name

Measurement Failure (MEASF)

Default severity

Minor

Alarm object

Flow Sensor Unit (FSU)

General information and causes

The MEASF alarm indicates that the shelf's Flow Sensor Unit failed to successfully complete an airflow measurement. The FSU automatically makes periodic airflow measurements to determine if the Air Filter is clogged. The interval between measurements is user-configurable via the craft terminal. The MEASF alarm will also be raised if the Air Filter is not installed in the shelf.

Troubleshooting instructions 1

Issue a manual measurement command to the Flow Sensor Unit. This can be done via GUI or locally: –

–

Via GUI: Right-click on the FSU replica in the Equipment View and select Card > Configuration to obtain the “FSU-Config” window. Then click the button named Manual Measurement. The FSU will begin a new measurement. Next, click the Update button. During the measurement, the Status field on the “FSUConfig” window will display Measurement in progress. It requires 3 - 5 minutes for a measurement to complete. Locally: Press the Lamp Test button at the top of the shelf, hold the button for at least five seconds, then release. The FSU will begin a new measurement. It requires 3 - 5 minutes for a measurement to complete.

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. 2

After the Manual Measurement is complete, open the “FSU-Config” window. Click the button and check the field named. –

If the Status field displays Last measurement cycle finished, the manual measurement was successful and the MEASF alarm will be cleared.

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

117

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

–

3

Once on-site, ensure that the Upper and Lower Fan Units are installed in the shelf correctly. If either is missing or not fully plugged-in, install the correct Fan Unit. Then, repeat step 1 (manual measurement) to see if the MEASF alarm clears. Remember to make all Manual Measurements with the shelf door fully closed and latched.

4

If the MEASF alarm persists, verify that the Air Filter is installed correctly. To do so, follow the steps below: – – –

–

3.1.78

If the Status field displays Last request rejected, or Last measurement failed, dispatch personnel to the site with replacement Upper and Lower Fan Units, a replacement Air Filter, and a replacement FSU. Go to step 3.

Open the shelf front door. Carefully remove the Air Filter Assembly (filter element and its metal housing). Verify that the filter element is correctly installed in its housing (manufacturer's logo must face upward (see Figure 1). Verify that the filter element is free from holes or other defects. If any are observed, replace the filter element with a spare and re-install the entire assembly in the shelf. Repeat Step 1 (manual measurement) to ensure that the MEASF alarm is not raised again. If the alarm persists, continue to step 5.

5

A properly-installed but defective Fan Unit may also cause a MEASF alarm (for example, the Upper Fan does not speed up as required during the FSU measurement). Replace the Upper Fan Unit with a spare and repeat Step 1. If the MEASF alarm does not clear, replace the Lower Fan Unit with a spare and repeat Step 1. Remember to make all manual measurements with the shelf door fully closed and latched.

6

If the alarm persists, replace the FSU with a spare (see chapter 4.3 for instructions. Then, repeat step 1 (manual measurement) to see if the alarm clears. Remember to make all Manual Measurements with the shelf door fully closed and latched.

7

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

MFNF

Alarm name

Multiple Fans Failure (MFNF)

Default severity

Critical

Alarm object

OTS-4000 shelf

General information and causes

Each OTS-4000 shelf contains three Fan Trays, each with two individual fans (i.e., a total of six fans). If two or more fans are simultaneously failed, the MFNF alarm will be raised.

Troubleshooting instructions 1

!

118

Dispatch personnel to the site raising the alarm. It is best to take at least three spare Fan Trays to the site. .

Caution! MFNF is a Critical alarm. Do not delay dispatching personnel to the site with spare fans.

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

Troubleshooting Manual (TSMN)

2

!

Troubleshooting Instructions

Once on-site, open the panel at the very top of the OTS-4000 shelf to gain access to the Fan Trays. Individual fan alarms (FN11F, FN22F, and so on) will also be raised. These identify which Fan Trays contain faulty fan(s). The red LEDs on the front of each Fan Tray will also show which contain faulty fan(s).

Caution! Work on only one Fan Tray at a time. Example: if Fan Tray 1 and Fan Tray 3 both contain failed fans, complete step 3 below for Fan Tray 1 first. Only then, repeat step 3 for Fan Tray 3.

3

Loosen the single front thumbscrew on the first Fan Tray that contains failed fan(s), and use the built-in handle to carefully slide it out of the shelf. Immediately insert the replacement Fan Tray fully into the shelf and tighten the thumbscrew. Verify that the two OK LEDs on this Fan Tray light.

4

Repeat step 3 for any other Fan Tray(s) that contain faulty fan(s).

5

Verify that the MFNF alarm has cleared. Also verify that there are no individual fan failure alarms (FN11F, FN12F, FN21F, FN22F, FN31F, or FN32F) still raised. Verify that both green OK LEDs are lit on each Fan Tray. Verify that all three FAN OK LEDs on the OTS-4000 shelf’s main LED panel are lit. Close and latch the top panel of the shelf.

6

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

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

119

Troubleshooting Instructions

3.1.79

!

Troubleshooting Manual (TSMN)

MIBF

Alarm name

MIB Failure (MIBF)

Default severity

Major

Alarm object

OCU73 subsystem

General information and causes

Each OCU73 subsystem’s Management Information Base (MIB) is stored in two places: the flash memory on-board the Controller card (CCEP or CCMP) and on the Controller card’s replaceable Compact Flash module. If both of these persistent storages fail, the MIBF alarm will be raised.

Warning! Do not confuse this OCU73 MIBF alarm with the MIBF alarm for other hiT 7500 subsystems. The other MIBF alarm is described in chapter 3.1.80.

Troubleshooting instructions 1

!

120

Do NOT Cold Start a CCEP or CCMP card when a MIBF alarm is active! When this alarm is raised, immediately make a backup copy of the MIB. Instructions for doing so are in the hiT 7500 Operating Manual (OMN).

Warning! When a MIBF alarm is raised, the NE can still function normally utilizing the working copy of the MIB residing on the Controller card’s PRAM. But, via whatever cause, if the Controller card is Cold Started while in this condition, the PRAM copy of the MIB will be lost, and the NE will not be able to recover to the state that existed prior to the Cold Start. This is why it is important to immediately make a backup copy of this NE’s MIB. If recovery is required, having the backup MIB copy available will make restoration easier. If a backup MIB is not available, the NE can be recovered with a default MIB, but traffic most likely will be impacted and all manual provisioning data will be lost.

2

Dispatch service personnel to replace the Controller card and the Compact Flash module. Take a spare card of the proper type (CCEP or CCMP) and a spare Compact Flash module. See 4.40.2 “CCMP replacement due to MIBF alarm”.

3

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

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

Troubleshooting Manual (TSMN)

3.1.80

Troubleshooting Instructions

MIBF

Alarm name

MIB Flash Fail (MIBF)

Default severity

Major

Alarm object

MCU card

General information and causes

A MIBF alarm indicates that the MIBS circuit board is present (correctly installed in the shelf) but has failed. This is typically caused by a read/write failure during an MIBS update. The MIBS circuit board stores a back-up version of the MCU card's configuration database. Contents of this database include transmission parameters, supervision and control parameters, card equipping data, and network element address. The MCU automatically updates the MIBS when changes are made to the system that affect the database contents. If the MIBS fails, the MCU has no back-up capability for persistent data.

!

Warning! When a MIBF alarm is active, do not unplug the network element’s MCU card, do not attempt a software upgrade, and do not attempt a VCDB upload.

Troubleshooting instructions

3.1.81

1

Remove the failed MIBS circuit board and replace it with a spare. See Chapter 9 of this document for complete MIBS removal and replacement instructions.

2

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

MIBM

Alarm name

MIB Flash Missing (MIBM)

Default severity

Major

Alarm object

MCU card

General information and causes

A MIBM alarm indicates that the MIBS circuit board is not installed in the shelf.

Troubleshooting instructions 1

Install the missing MIBS circuit board in the shelf. See Chapter 9 of this document for complete MIBS removal and replacement instructions.

2

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

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

121

Troubleshooting Instructions

3.1.82

Troubleshooting Manual (TSMN)

MIBS256

Alarm name

MIBS256 Required (MIBS256)

Default severity

Minor

Alarm object

MCU card

General information and causes

The MIBS256 alarm will be raised if a network element has been provisioned for a MIBS256 board, but another MIBS variant is installed instead.

Troubleshooting instructions 1

Open the “Card Configuration” window for the MCU card raising the MIBS256 alarm. To do so, right-click on the MCU card replica in the Equipment View and select Card > Configuration. Note the checkbox named MIBS256 Required. Ensure that the setting for this checkbox matches actual equipping as follows: –

–

If this MCU is supposed to be equipped with a MIBS256 board, enable the checkbox and ensure that a MIBS256 is actually installed in the associated slot in the shelf. If another variant of MIBS has been mistakenly installed, remove it and replace with a MIBS256. This will clear the MIBS256 alarm. If this MCU is not supposed to be equipped with a MIBS256 board, disable the checkbox and ensure that a MIBS32 or MIBS32-2 board is installed in the associated slot in the shelf. The MIBS256 alarm will clear.

g when the incorrect MIBS board is removed, a MIBM (MIB Missing) alarm will be raised - ignore this alarm. When the MIBS256 is inserted, the MIBM alarm will clear and the MCU will begin backing up its active APS to the MIBS256, thus raising a temporary APSBUR alarm - ignore this alarm too. When the backup process is finished, the APSBUR alarm will self-clear.

122

2

If the MIBS256 alarm persists, try removing and re-inserting the MIBS256 board once again and allow the system to go through its APS backup routine.

3

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

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

Troubleshooting Manual (TSMN)

3.1.83

Troubleshooting Instructions

MTX_APSMISS

Alarm name

MTX APS Missing (MTX_APSMISS)

Default severity

Critical

Alarm object

Master MCU card

General information and causes

The @CT or MTX software is detected as missing.

Troubleshooting instructions

3.1.84

1

Download the @CT software and/or the MTX software to the card. This is done via the Web CT Software tab or the TL1 Agent Software on the “Software Management” window, respectively.

2

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

MWBMP

Alarm name

MWB Module Problem (MWBMP)

Default severity

Major

Alarm object

WBAN, WBN, and WBAU cards

General information and causes

This alarm indicates either an internal error on the affected card's Multi-Wavelength Blocker (MWB) Module or a communication problem between the card's controller and the MWB Module.

Troubleshooting instructions 1

Is traffic affected due to the MWBMP condition? –

–

2

Yes: Warm Start the card raising the MWBMP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the MWBMP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

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

123

Troubleshooting Instructions

3.1.85

!

Troubleshooting Manual (TSMN)

NLDC1

Alarm name

No Light Detected C1 (NLDC1)

Default severity

Minor

Alarm object

OPAPC cards

General information and causes

This alarm is raised if the OPAPC cannot detect incoming light at the MonC1 monitoring port. This is typically caused by disconnected fiber or dirty connectors.

Warning! When the NLDC1 alarm is active, the OPAPC cannot execute any performance monitoring or execute any OPAPC-based link actions (for example, automatic pre-emphasis). Therefore, do not attempt any actions such as channel upgrade or downgrade while a NLDC1 alarm is active.

Troubleshooting instructions 1

Refer to Figure 21. Missing or loose fiber connections between OLI card and the OPAPC card’s MonC1 port can cause the NLDC1 alarm. Verify that the cable is properly installed. If the cable is missing, bent/pinched, or improperly connected, the NLDC1 alarm should clear when the correct connection is established.

2

If the alarm persists, disconnect the fiber patchcord from the OPAPC card’s MonC1 port and the corresponding MonSo port of the OLI card. Clean all optical connectors and re-connect. If the NLDC1 alarm persists after cleaning, replace the fiber patchcord with a cleaned, inspected spare.

3

If the alarm persists, there may be no light coming from the OLI card’s MonSo port. Perform the following steps: – –

124

Via the craft terminal, open the “Traffic - Info” window for the appropriate OLI and note the displayed Total Output Power value. Disconnect the fiber patchcord from the OPAPC card’s MonC1 port and the corresponding MonSo port of the OLI card. Use an optical power meter to measure the output power at the OLI's MonSo port. The value should be approximately 13 dB below the OLI's Total Output Power. If the actual output power is far below this value, replace the OLI card with a spare.

4

If no other cause can be found, Warm Start the affected OPAPC card. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OPAPC card. If the alarm persists after recovery time (approx 3 minutes), the OPAPC card is defective. Replace the OPAPC card with a spare.

5

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

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

Troubleshooting Manual (TSMN)

Figure 21

3.1.86

!

Troubleshooting Instructions

Fiber connections from OLI cards to OPAPC

NLDC2

Alarm name

No Light Detected C2 (NLDC2)

Default severity

Minor

Alarm object

OPAPC cards

General information and causes

This alarm is raised if the OPAPC cannot detect incoming light at the MonC2 monitoring port. This is typically caused by disconnected fiber or dirty connectors.

Warning! When the NLDC2 alarm is active, the OPAPC cannot execute any performance monitoring or execute any OPAPC-based link actions (for example, automatic pre-emphasis). Therefore, do not attempt any actions such as channel upgrade or downgrade while a NLDC2 alarm is active.

Troubleshooting instructions 1

Refer to Figure 21. Missing or loose fiber connections between OLI card and the OPAPC card’s MonC2 port can cause the NLDC2 alarm. Verify that the cable is

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

125

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

properly installed. If the cable is missing, bent/pinched, or improperly connected, the NLDC2 alarm should clear when the correct connection is established. 2

If the alarm persists, disconnect the fiber patchcord from the OPAPC card’s MonC2 port and the corresponding MonSo port of the OLI card. Clean all optical connectors and re-connect. If the NLDC2 alarm persists after cleaning, replace the fiber patchcord with a cleaned, inspected spare.

3

If the alarm persists, there may be no light coming from the OLI card’s MonSo port. Perform the following steps: – –

3.1.87

Via the craft terminal, open the “Traffic - Info” window for the appropriate OLI and note the displayed Total Output Power value. Disconnect the fiber patchcord from the OPAPC card’s MonC2 port and the corresponding MonSo port of the OLI card. Use an optical power meter to measure the output power at the OLI's MonSo port. The value should be approximately 13 dB below the OLI's Total Output Power. If the actual output power is far below this value, replace the OLI card with a spare.

4

If no other cause can be found, Warm Start the affected OPAPC card. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OPAPC card. If the alarm persists after recovery time (approx 3 minutes), the OPAPC card is defective. Replace the OPAPC card with a spare.

5

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

NOSYNCMSTR

Alarm name

No Sync Master (NOSYNCMSTR)

Default severity

Minor

Alarm object

Link Control 1 (OSCTUT card)

General information and causes

In networks featuring concatenated or meshed topologies, one OSCTUT card must be designated as the Synchronization Master, and all others must be designated as Synchronization Slaves. One Master is necessary to ensure that the continuous pre-emphasis process operates correctly. If no OSCTUT card has been designated to be Synchronization Master, the NOSYNCMSTR alarm will be raised. The NOSYNCMSTR alarm will be displayed on GUI windows as raised against the object "Link Control 1". Link Control 1 designates Tx direction. (Link Control 2 designates the Rx direction; however, this will never be seen in SURPASS hiT 7500).

Troubleshooting instructions 1

Configure the chosen OSCTUT card to be Synchronization Master. This will clear the NOSYNCMSTR alarm. To do so: –

126

Choose the OSCTUT that will be the Synchronization Master. Right-click on its Card Replica in the Equipment View and select Optical Link Control.

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

Troubleshooting Manual (TSMN)

– 2

3.1.88

Troubleshooting Instructions

On the resulting “Optical Link Control - Config” window, set the Link Synchronization Master to enabled. Click the Apply icon.

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

NOTIMMSTR

Alarm name

No Timing Master (NOTIMMSTR)

Default severity

Minor

Alarm object

OSCTUT card

General information and causes

A clock source (T2 internal oscillator on the OSCT or T3 external source) at either end of the link must be designated to be the link's Timing Master. At 1-minute intervals, the Master transmits a timing synchronization pulse that is used by all OPAPC and OSCT cards along the link. If no clock source has been designated to be the Master, the NOTIMMSTR alarm will be raised.

Troubleshooting instructions

3.1.89

1

Configure the priority ("high" or "low") of the T2 and optional T3 clocks correctly in order to specify one Timing Master. These priority settings are made on each OSCT’s “Card Configuration” window.

2

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

NQO

Alarm name

Notification Queue Overflow (NQO)

Default severity

Minor

Alarm object

HDS shelf

General information and causes

The NQO alarm indicates an internal overload of the Controller card software due to too many notification messages.

Troubleshooting instructions 1

Often, the NQO condition is only temporary. Wait a short time and see if the alarm clears by itself.

2

If the alarm persists, the problem could be due to too many Element Managers connected at once. Reduce the number of Element Managers connected.

3

If the alarm persists, contact your next higher level of technical support before proceeding. Warm Start the Controller card (CCEP or CCMP). If the alarm persists after recovery time, Cold Start the card. Management visibility to this NE will be lost while the Controller card executes its Cold Start routine.

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

127

Troubleshooting Instructions

4

3.1.90

Troubleshooting Manual (TSMN)

If the alarm persists, replace the Controller card (CCEP or CCMP). See Card Replacement Instructions in chapter 4.40.

NTPSVACCFAIL

Alarm name

NTP Server Access Failed (NTPSVACCFAIL)

Default severity

Warning

Alarm object

All stand-alone and Master MCU cards

General information and causes

If external Network Time Protocol (NTP) server(s) have been configured to supply network time synchronization, each NE periodically checks to verify that it still has access to at least one NTP server. If this periodic check fails, the NE will raise the NTPSVACCFAIL alarm.

Troubleshooting instructions 1

Is NTP capability actually desired? –

–

3.1.91

128

No: disable NTP to clear the alarm. To do so, right click on this NE’s Network Element Bar in the Equipment View and select Configuration > Network Time Protocol. Then, disable Network Time Protocol and click Apply. Yes: go to step 2.

2

If the alarm is simultaneously raised on multiple NEs, the problem is likely with the NTP Servers themselves. If the alarm is raised by a single NE, verify that all northbound EMS connections are intact and that NTP was set-up correctly during commissioning. [NTP server addresses must be provided by the customer network]. The MCU cards each support up to three NTP server addresses. At least two should be configured according to your DCN Plan. Refer to the appropriate NE Commissioning Manual for NTP set-up instructions.

3

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

NVCDBMIG

Alarm name

No VCDB Migration Possible (NVCDBMIG)

Default severity

Warning

Alarm object

MCU card

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

Troubleshooting Manual (TSMN)

General information and causes

Troubleshooting Instructions

As part of the procedure to download new APS (Application Program System) software to an NE, the user may first perform a Swap Preparation check before an attempt is made to swap the Inactive APS to the Active bank. This check verifies that the Active APS recognizes the currently-loaded Inactive APS. If the Inactive APS is not recognized as appropriate for migration, the NVCDBMIG alarm will be raised. The system will not permit the APS swap to proceed until the correct APS is loaded into the Inactive Bank.

Troubleshooting instructions 1

Verify that the Inactive bank contains the exact APS version proper for the NE raising the NVCDBMIG alarm. Check the Order Number, Version Number, and SW/FW Code as displayed on the “Software Management” window. If the Inactive APS is not the correct one, download the proper APS to the Inactive bank. Then, click the Swap Preparation button again on the “Software Management” window to re-run the compatibility check. If the check passes, the NVCDBMIG alarm will clear.

2

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

g VCDB migration while attempting an APS Fallback procedure is not supported, since doing so will cause a NVCDBMIG alarm. If a swap still needs to be performed, the Extended Swap Preconditions option in the "Software Management" window must be set to "No".

3.1.92

OBLOS

Alarm name

Receiver Fail Booster (OBLOS)

Default severity

Critical

Alarm object

All OLI card types

General information and causes

This alarm is raised if there is a Loss of Signal detected at the input of Amplifier Stage III of the indicated OLI card. The threshold for the detection of OBLOS is -20 +/- 2 dBm.

Troubleshooting instructions 1

Refer to Figure 22 and Figure 23. A fiber cut downstream of the card raising the OBLOS alarm (fiber cut in the very next span or the following span) could be causing the OBLOS alarm. If there is a fiber cut, two OLI cards will be raising OBLOS alarms as shown in these examples. The fiber cut (single or double) will always be somewhere in the two spans between these OLIs as shown. Repair the fiber cut to clear the OBLOS alarm.

2

If the alarm persists, a bent or kinked fiber connections at one of the points (A - F) in Figure 24 could be the cause. Verify that each cable is properly installed. If a cable is bent/pinched, or improperly connected, correct the problem. The OBLOS alarm should clear when the correct connection is established.

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

129

Troubleshooting Instructions

130

Troubleshooting Manual (TSMN)

3

If the alarm persists, disconnect the interstage fiber patchcord(s), clean the optical connectors, and re-connect. If the OBLOS alarm persists after cleaning, one or more of the patchcords may be defective. Replace the fiber patchcord(s) with cleaned, inspected spares one by one until the alarm clears. (If a special interstage stuffing attenuator fiber is used, ensure that any replacement cable is the same rating).

4

If the alarm persists, UDCM or PQM insertion loss may be too high. Verify that the type of installed UDCM exactly matches the type listed for this OLI on the Route Plan. If the incorrect type was used, remove it and install the correct type. If the correct UDCM is present and the OBLOS alarm persists, replace the UDCM with a spare of the same type. If a PQM module is used and the OBLOS alarm persists, replace the PQM module.

5

If the alarm persists, Warm Start the affected OLI card. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OLI card. If the alarm persists after recovery time (approx 3 minutes), the OLI card is defective. Replace the OLI card with a spare.

6

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

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

Troubleshooting Manual (TSMN)

Figure 22

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

Troubleshooting Instructions

OBLOS alarm with single fiber cut

131

Troubleshooting Instructions

Figure 23

132

Troubleshooting Manual (TSMN)

OBLOS alarm with double fiber cut

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

Troubleshooting Manual (TSMN)

Figure 24

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

Troubleshooting Instructions

Interstage devices for OBLOS alarm

133

Troubleshooting Instructions

3.1.93

Troubleshooting Manual (TSMN)

OBTF

Alarm name

Transmit Fail Booster (OBTF)

Default severity

Major

Alarm object

All OLI card types

General information and causes

An OLI card raises the OBTF alarm if its booster stage cannot achieve the required power gain. This can be caused by a hardware fault on the card or a booster stage power anomaly.

Troubleshooting instructions

3.1.94

1

Are other alarms active on this OLI card (ISLP, OPLOS)? If so, troubleshoot those alarms first since they could be causing the input power into the booster stage to be too low.

2

If the alarm persists, a back-reflection condition could exist at the OLI card output connector. Contact your next higher level of technical support before proceeding. Disconnect the fiber from the OLI card's output connector. Clean the fiber end and connector. Re-connect the fiber.

3

If the alarm persists, Warm Start the affected OLI card. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OLI card. If the alarm persists after recovery time (approx 3 minutes), the OLI card is defective. Replace the OLI card with a spare.

4

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

OLOL

Alarm name

Output Loss of Light (OLOL)

Default severity

Major

Alarm object

OTS-4520 (TDCM) card and OTS-4540 (PMDC) card

General information and causes

The OLOL alarm will be raised if the indicated card is not outputting an optical signal.

Troubleshooting instructions

134

1

Warm Start the card raising the alarm. If the alarm persists after Warm Start recovery time, Cold Start the card. If the alarm persists after Cold Start recovery time, replace the card with a spare.

2

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

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

Troubleshooting Manual (TSMN)

3.1.95

Troubleshooting Instructions

OPLOS

Alarm name

Receiver Fail Preamp (OPLOS)

Default severity

Critical

Alarm object

All OLI card types

General information and causes

This alarm is raised if there is a Loss of Signal detected at the input of Amplifier Stage I of the indicated OLI card. The threshold for the detection of OPLOS is -28 +/- 2 dBm, which is the Automatic Power Shutdown (APSD) threshold for all OLI card types. Note that OPLOS suppresses the OBTF, OPTF, SLH, and SLH alarms.

Troubleshooting instructions 1

Refer to Figure 25. An OPLOS alarm is typically caused by a fiber break or other fiber problem immediately prior to the OLI card raising the alarm. So, verify that the input fiber cable is properly installed. If the cable was missing, bent/pinched, or improperly connected, correct the problem. The OPLOS alarm should clear when the correct connection is established

2

If the alarm persists, disconnect the fiber at the In connector of the affected OLI card. Clean all optical connectors and re-connect. If OPLOS alarm persists, replace the fiber cable with a cleaned, inspected spare.

3

If the alarm persists, Warm Start the affected OLI card. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OLI card. If the alarm persists after recovery time (approx 3 minutes), the OLI card is defective. Replace the OLI card with a spare.

4

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

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

135

Troubleshooting Instructions

Figure 25

136

Troubleshooting Manual (TSMN)

Example causes of an OPLOS alarm

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

Troubleshooting Manual (TSMN)

3.1.96

Troubleshooting Instructions

OPTF

Alarm name

Transmit Fail Preamp (OPTF)

Default severity

Major

Alarm object

All OLI card types.

General information and causes

An OLI card raises the OPTF alarm if its pre-amplifier stages cannot achieve the required power gain. This can be caused by a hardware fault on the card or a pre-amplifier stage power anomaly.

Troubleshooting instructions

3.1.97

1

Are other alarms active on this OLI card (CP, OPLOS, APRM)? If so, troubleshoot those alarms first since they could be causing the input power into the pre-amplifier stage to be too low.

2

If the alarm persists, a back-reflection condition could exist at the OLI card’s IIOut connector. Contact your next higher level of technical support before proceeding. Disconnect the fiber from the OLI card's IIOut connector. Clean the fiber end and connector. Re-connect the fiber.

3

If the alarm persists, Warm Start the affected OLI card. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OLI card. If the alarm persists after recovery time (approx 3 minutes), the OLI card is defective. Replace the OLI card with a spare.

4

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

OSAMP

Alarm name

OSA Module Problem (OSAMP)

Default severity

Major

Alarm object

OPAPC cards

General information and causes

This alarm is raised if a failure of the OPAPC card's on-board Optical Spectrum Analyzer (OSA) is detected. As a result of this failure, the OPAPC cannot execute any performance monitoring or execute any OPAPC-based link actions (for example, automatic pre-emphasis).

Troubleshooting instructions 1

Is traffic affected due to the OSAMP condition? –

–

Yes: Warm Start the card raising the OSAMP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the OSAMP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary.

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

137

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card. 2

3.1.98

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

OSAPF

Alarm name

OSA Power Fail (OSAPF)

Default severity

Major

Alarm object

OPAPC cards

General information and causes

This alarm is raised if the power supply of the OPAPC card's on-board Optical Spectrum Analyzer (OSA) has failed. As a result of this failure, the OPAPC cannot execute any performance monitoring or execute any OPAPC-based link actions (for example, automatic pre-emphasis).

Troubleshooting instructions 1

Is traffic affected due to the OSAPF condition? –

–

2

3.1.99

Yes: Warm Start the card raising the OSAPF alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the OSAPF alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

OSCTD1

Alarm name

Transmit Degrade OSC1 (OSCTD1)

Default severity

Minor

Alarm object

OSCTUT and OSCTUI cards

General information and causes

This alarm is raised if a rise in laser current is detected on a transmit laser on the indicated OSCTUT or OSCTUI card.

Troubleshooting instructions 1

Is traffic affected due to the OSCTD1 condition? –

138

Yes: Warm Start the card raising the OSCTD1 alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare.

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

Troubleshooting Manual (TSMN)

–

2

3.1.100

Troubleshooting Instructions

No: Warm Start the card raising the OSCTD1 alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

OSCTD2

Alarm name

Transmit Degrade OSC2 (OSCTD2)

Default severity

Minor

Alarm object

OSCTUT and OSCTUI cards

General information and causes

This alarm is raised if a rise in laser current is detected on a transmit laser on the indicated OSCTUT or OSCTUI card.

Troubleshooting instructions 1

Is traffic affected due to the OSCTD2 condition? –

–

2

3.1.101

Yes: Warm Start the card raising the OSCTD2 alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the OSCTD2 alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

OTS_APSMISS

Alarm name

OTS APS Missing (OTS_APSMISS)

Default severity

Critical

Alarm object

Master MCU card

General information and causes

The OTS software is detected as missing.

Troubleshooting instructions 1

Download the OTS software to the card. This is done via the OTS Software tab on the “Software Management” window.

2

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

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

139

Troubleshooting Instructions

3.1.102

Troubleshooting Manual (TSMN)

PbusF

Alarm name

Power Bus Fail (PBusF)

Default severity

Minor

Alarm object

All shelf types (except OTS-4000, MCU-Shelf, and MCU-Slim shelf).

General information and causes

The PBusF alarm is raised when a failure of the backplane 5volt power bus is detected in the indicated shelf. Each shelf contains either an OSCT card or SMU card. These cards are responsible for supplying 5-volt power through the backplane to certain other cards in the shelf that require this voltage.

Troubleshooting instructions

3.1.103

1

Verify that the affected shelf has its OSCT card (or SMU card as applicable) installed properly in the correct slot.

2

If the OSCT (or SMU) card is installed properly and the PBusF alarm persists, Warm Start the affected shelf's OSCT (or SMU card). Sometimes, a Warm Start of this card will clear the PbusF alarm. Note however, that the recovery is often only temporary. If the alarm persists, Cold Start the card.

3

If the alarm persists, replace the OSCT (or SMU) card with a spare.

4

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

PCBF

Alarm name

PCB Bus Fail (PCBF)

Default severity

Major

Alarm object

MCU card

General information and causes

The PCBF alarm indicates that communication to any of the other configured cards managed by the indicated MCU cannot be established via the Peripheral Control Bus.

Troubleshooting instructions

140

1

If ALL configured cards managed by this MCU (including FSU) have simply been removed from the shelf, the PCBF alarm will be raised. The solution in this case is to re-insert the cards. The PCBF alarm will clear when the first card is re-inserted. If this was not the case, continue to step 2.

2

Incorrect shelf addresses can cause the PCBF alarm. Set all shelf addresses as directed in the Installation and Test Manual (ITMN). Addresses are set via the rotary switch at the top of each shelf.

3

If the alarm persists, check the termination plugs on the shelf’s PCB/CAN connectors. If they are missing, install the proper Termination Plugs as directed in the Instal-

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

lation and Test Manual (ITMN). If the plug were present and correctly installed, there is a slight chance that they are defective. replace the termination plugs with spares.

3.1.104

4

If the alarm persists, the MCU card’s PCB driver may be faulty. Cold Start the MCU card. If the PCBF alarm does not clear after Cold Start recovery (approx 3 to 5 minutes), replace the MCU with a spare.

5

If the alarm persists, there may be a PCB bus failure in the shelf (extremely unlikely). The only solution is to replace the entire shelf.

6

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

PDIFF

Alarm name

Power Differential Alarm (PDIFF)

Default severity

Minor

Alarm object

PQM card

General information and causes

Every 20 seconds, the PQM card calculates its own mean insertion loss (the difference between the total output and total input powers of the PQM card). If the PQM cannot control its insertion loss and hold it at the required value, the PDIFF alarm will be raised.

Troubleshooting instructions 1

The PDIFF alarm is only a concern if it does not quickly clear automatically. If the PDIFF alarm is raised, wait a few minutes. If the alarm self-clears, no action is necessary.

2

If the PDIFF alarm persists for a long time, is traffic affected? –

–

3

3.1.105

Yes: Warm Start the card raising the PDIFF alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the PDIFF alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

PQMLOS

Alarm name

Loss of Signal PQM (PQMLOS)

Default severity

Minor

Alarm object

PQM card

General information and causes

The PQMLOS alarm will be raised if the input power to the PQM card falls below the fixed threshold of -3 dBm.

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

141

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions 1

Refer to Figure 26. Check for alarms raised by upstream equipment, especially the associated OLI card (the OLI connected to the affected PQM card). If upstream alarms exist (for example CP or OPTF alarm on the associated OLI), troubleshoot those alarms first.

2

If the PQMLOS alarm persists, verify that the fiber cable from the OLI II Out port to the PQM In port is properly installed. If the cable is missing, bent/pinched, or improperly connected, correct the problem. The PQMLOS alarm should clear when the correct connection is established.

3

If the PQMLOS alarm persists, contact your next higher level of technical support before proceeding. Disconnect both ends of the fiber (at OLI II Out port and PQM In port). Clean all optical connectors and re-connect. If PQMLOS alarm persists, replace the fiber cable with a cleaned, inspected spare.

4

If the alarm persists, Warm Start the affected PQM card. If the alarm persists after recovery time (approx 3 minutes), Cold Start the PQM card. If the alarm persists after recovery time (approx 3 minutes), the PQM card is defective. Replace the PQM card with a spare.

5

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

Figure 26

3.1.106

142

PQMLOS alarm diagram

PQMMP

Alarm name

PQM Module Problem (PQMMP)

Default severity

Minor

Alarm object

PQM card

General information and causes

The PQMMP alarm indicates a fault on the PQM card's Dynamic Gain Equalizer (DGE) or a communication problem between the PQM card's controller and DGE.

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Troubleshooting instructions 1

Is traffic affected due to the PQMMP condition? –

–

2

3.1.107

Yes: Warm Start the card raising the PQMMP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the PQMMP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

PREEMPF

Alarm name

Preemphase Fail (PREEMPF)

Default severity

Minor

Alarm object

OSCT card

General information and causes

The PREEMPF alarm will be raised if 10 consecutive preemphasis cycles fail. The PREEMPF alarm will be displayed on GUI windows as raised against the object "Link Control 1". Link Control 1 designates Tx direction. (Link Control 2 designates the Rx direction; however, this will never be seen in SURPASS hiT 7500.

Troubleshooting instructions 1

Open the “Optical Link Control-Config” window for the OSCT card raising the PREEMPF alarm. To do so, right click on the OSCT card replica in the Equipment View and select Optical Link Control. On this window, check the “Last Action” field. One of the messages listed below will likely be displayed. Find it in the list below and follow the instructions. (If the displayed message is not in the list below, go to chapter 7.1, which contains all possible “Last Action” messages, and follow the appropriate instructions described there. – –

–

Adjustable VOA range exceeded: check cabling and powers: go to chapter 3.1.107.1. Amplifier Problem (OLI or RPUMP): Check for other alarms raised by the OLI card and troubleshoot those alarms first. If the PREEMPF alarm persists, Warm Start the amplifier card. No CAN communication to OPA card: Communication has been lost with the local OPAPC card. It could be that the card is missing altogether. If so, install an OPAPC card at the local site. If the card is present, verify that the PCB/CAN cables are properly connected between shelves. Also, check for other cardrelated alarms (CP, CFAIL, CMISS, etc) and troubleshoot those alarms. If the PREMPF alarm persists, Warm Start the local OPAPC card. If the PREEMPF alarm persists after Warm Start, Cold Start the local OPAPC card.

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

143

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

–

–

– –

– –

3.1.107.1

No CAN communication to far OPA card: Communication has been lost with the far-end OPAPC card. It could be that the card is missing altogether. If so, install an OPAPC card at the far-end site. If the card is present, verify that the PCB/CAN cables are properly connected between shelves. Also, check for other card-related alarms (CP, CFAIL, CMISS, etc) and troubleshoot those alarms. If the PREMPF alarm persists, Warm Start the far-end OPAPC card. If the PREEMPF alarm persists after Warm Start, Cold Start the far-end OPAPC card. No CAN communication to (card name): Verify that the PCB/CAN cabling is properly connected between shelves. Also, check for other card-related alarms (CP, CFAIL, CMISS, etc) and troubleshoot those alarms, which should clear the PREEMPF alarm. Precondition violation: go to chapter 3.1.107.2. Received POWER data are invalid - abort: all of the received measurement data from the local and/or far-end OPAPC cards are invalid. Warm Start the OPAPC cards. This should clear the PREEMPF alarm. If the PREMPF alarm persists, Cold Start the OPAPC cards. Requested data not received from local OPA: Warm Start the local OPAPC card. Requested data not received from far OPA: Warm Start the far-end OPAPC card.

2

If Last Action message(s) provided no assistance in clearing the PREEMPF alarm, perform the procedures in Chapter 6 “Link Control Troubleshooting”.

3

If the alarm persists, Warm Start the affected OSCT card. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OSCT card. If the alarm persists after recovery time (approx 3 minutes), the OSCT card is defective. Replace the OSCT card with a spare.

4

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

Last Action message: Adjustable VOA range exceeded This message indicates that at least one of the Variable Optical Attenuators (VOAs) in the system has reached the limit of its working range - usually the lower limit, which is 1.8 dB for add-path OM (Optical Multiplexer) cards and 0 dB for WB (Wave Blocker) cards and WSSC cards. The likely cause is a dirty fiber connection, either in the local NE (the NE raising the alarm), or perhaps even in an upstream NE. Troubleshooting instructions 1

Check the current VOA settings of each Wave Blocker card (WBAN, WBN, or WBAU) and each WSSC card. To do so, right-click on the card in the Equiment View and select Traffic - Configuration. The current VOA settings are listed on the resulting “Traffic - Config” window. Check if any VOA is at its lower limit (0 dB). Often, if one VOA on these card types card is at 0 dB, VOAs for other channels received from the same upstream direction will also be close to 0 dB. – –

144

If none of the VOAs on these cards are at the lower limit of 0 dB, go to step 2. However, if any VOAs on these cards are at the lower limit of 0 dB, then the bad fiber connection is likely in the fiber leading from the CDU card Out connectors or the fiber in the next upstream NE leading from the Pre-amp OLI Out connector to CDU In. Disconnect these fibers, clean, and re-connect. If the alarm persists, replace the fiber with a clean, inspected spare

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

Troubleshooting Manual (TSMN)

2

Troubleshooting Instructions

Check the current VOA settings of each OM (Optical Multiplexer) card at the site raising the alarm. To do so, right-click on the OM card in the Equiment View and select Traffic - Configuration. The current VOA settings are listed on the resulting “Traffic - Config” window. Check if any VOA is at its lower limit (1.8 dB). Often, if one VOA on an OM card is at 1.8 dB, multiple VOAs on the same card will also be near this level. If VOA(s) are at this level, it indicates a potential fiber connection problem. To isolate the problem, continue to step 3.

3

In the Equipment View, right-click on the OSCT card raising the PREEMPF alarm and click the Mux Loss button. On the resulting window, check the displayed Mux Loss values for wavelength bands C1 through C8. – –

4

In the Equipment View, right-click on the Add-OLI and select Traffic Measurement. Read the value displayed for “Total Output Power”. Then, open the Card-Config window for the card connected to the Add-OLI card’s output port (which will be a Wave Blocker card or CAX card). Read the “Power” value, which is the power input to the card’s AddIn connector. – –

5

3.1.107.2

If the Mux Loss values are consistent for all deployed wavelength bands, continue to step 4. However, if the Mux Loss of a wavelength band (example: the C1 and C2 bands) is considerably higher than the other bands, then the bad fiber connection is likely in the fiber leading from the OM20C1C2 card MuxOut connector. Disconnect this fiber, clean, and re-connect. If the alarm persists, replace the fiber with a clean, inspected spare.

If the difference between the Add-OLI card’s output power and the power input to the Wave Blocker (or CAX) card is close to 0, then continue to step 5. However, if the difference between the Add-OLI card’s output power and the power input to the Wave Blocker (or CAX) card is more than 3 dB, the fiber connection between the two cards is likely bad. Disconnect this fiber, clean, and reconnect. If the alarm persists, replace the fiber with a clean, inspected spare.

If the PREMPF alarm persists, return to chapter 3.1.107, step 2.

Last Action message: Precondition violation Follow the instructions below if the “Last Action” field displays “Precondition violation”. Troubleshooting instructions 1

In the Equipment View, right-click on the OSCT card raising the PREEMPF alarm and select Optical Link Control. On the resulting “Optical Link Control - Config” window, verify that the setting for “Attenuator Control” is set to “automatic”. Correct the setting if necessary.

2

If the PREEMPF alarm persists, it could be caused by a non-installed or defective card. If a WBAU, WBAN, WBN, WSSC, or PQMC card is present in the Required Equipping Table, but is unavailable to participate in the Link Control process, the PREEMPF alarm can result. So, make sure all required cards are actually installed in the shelf, fibered correctly, and powered. If any alarms are raised on these cards, troubleshoot and clear those alarms and the PREEMPF alarm should also clear.

3

If the PREEMPF alarm persists, return to chapter 3.1.107, step 2.

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

145

Troubleshooting Instructions

3.1.108

Troubleshooting Manual (TSMN)

PU1TD, PU2TD, PU3TD, PU4TD, and PU5TD

Alarm name

Transmit Degrade Pump# (PU#TD)

Default severity

Minor

Alarm object

OLI cards (all types), PUMP cards (all types), and RPUMPC cards.

General information and causes

The Pu#TD alarm is raised if one of the pump laser currents on the indicated card has risen above 120% of its Beginning of Life (BOL) value. The BOL value is set by the factory for each card individually. OLI and RPUMPC cards can have up to five on-board pump lasers, so RPUMPC and most OLI cards can raise PU1TD, PU2TD, PU3TD, PU4TD, or PU5TD alarm. Exceptions: OLIVxx types: only PU1TD. OLIMxx types: only PU1TD and PU2TD. PUMPA/B/C cards have two on-board pump lasers, so a PUMPA/B/C card can raise only a PU1TD or PU2TD alarm.

!

Caution! Note that the PU#TD alarm has raise and clear integration times of 900 seconds (15 minutes. Therefore, wait at least 15 minutes after performing any troubleshooting step to give the alarm time to clear.

Troubleshooting instructions 1

Has the card raising the alarm been in service a considerable length of time? –

–

146

Yes: in this case, the PUxTD alarm is providing advance warning of performance degradation due to end-of-life laser aging effects. Although not immediately required, the card indicating the alarm should be replaced with a spare as soon as practical. No: continue to step 2.

2

Check the settings of the Output Power per Channel in the OLI “Card Configuration” window. Verify that these settings have been made accurately according to your Commissioning Report.

3

If the PU#TD alarm persists, troubleshoot and clear any alarms raised by upstream equipment. A higher than normal temperature can also cause a PU#TD alarm. Verify that the shelf Fan Units are working.

4

If the PU#TD alarm persists, verify that all fiber cables to/from the affected card are properly installed. If a cable is missing, bent/pinched, or improperly connected, correct the problem.

5

If the PU#TD alarm persists, contact your next higher level of technical support before proceeding. Disconnect fibers leading to/from the affected card. Clean all optical connectors and re-connect. If PU#TD alarm persists, replace the fiber(s) with cleaned, inspected spares.

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

Troubleshooting Manual (TSMN)

3.1.109

Troubleshooting Instructions

6

If the alarm persists, Warm Start the card raising the alarm. If the alarm persists after recovery time, Cold Start the card. If the alarm persists after recovery time, the card is defective. Replace the card raising the alarm with a spare.

7

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

PU1TF, PU2TF, PU3TF, PU4TF, and PU5TF

Alarm name

Transmit Fail Pump# (PU#TF)

Default severity

Minor

Alarm object

OLI cards (all types), PUMP cards (all types), and RPUMPC cards.

General information and causes

The Pu#TD alarm is raised if one of the pump laser currents on the indicated card has risen a substantial amount above 120% of its Beginning of Life (BOL) value. The BOL value is set by the factory for each card individually. OLI and RPUMPC cards can have up to five on-board pump lasers, so RPUMPC and most OLI cards can raise PU1TF, PU2TF, PU3TF, PU4TF, or PU5TF alarm. Exceptions: OLIVxx types: only PU1TF. OLIMxx types: only PU1TF and PU2TF. PUMPA/B/C cards have two on-board pump lasers, so a PUMPA/B/C card can raise only a PU1TF or PU2TF alarm.

!

Caution! Note that the PU#TF alarm has raise and clear integration times of 900 seconds (15 minutes. Therefore, wait at least 15 minutes after performing any troubleshooting step to give the alarm time to clear.

Troubleshooting instructions 1

Has the card raising the alarm been in service a considerable length of time? – –

Yes: In this case, the PUxTF alarm indicates the pump laser has failed due to end-of-life laser aging effects. Replace the card with a spare. No: continue to step 2.

2

Check the settings of the Output Power per Channel in the OLI “Card Configuration” window. Verify that these settings have been made accurately according to your Commissioning Report.

3

If the PU#TF alarm persists, troubleshoot and clear any alarms raised by upstream equipment. A higher than normal temperature can also cause a PU#TF alarm. Verify that the shelf Fan Units are working.

4

If the PU#TF alarm persists, verify that all fiber cables to/from the affected card are properly installed. If a cable is missing, bent/pinched, or improperly connected, correct the problem.

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

147

Troubleshooting Instructions

3.1.110

Troubleshooting Manual (TSMN)

5

If the PU#TF alarm persists, contact your next higher level of technical support before proceeding. Disconnect fibers leading to/from the affected card. Clean all optical connectors and re-connect. If PU#TF alarm persists, replace the fiber(s) with cleaned, inspected spares.

6

If the alarm persists, Warm Start the card raising the alarm. If the alarm persists after recovery time, Cold Start the card. If the alarm persists after recovery time, the card is defective. Replace the card raising the alarm with a spare.

7

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

PWCTLSUSP

Alarm name

Power Control Suspicious (PWCTLSUSP)

Default severity

Warning

Alarm object

All OLI card types.

General information and causes

This alarm serves as a warning that the indicated OLI card’s output power control time-constant is in “frozen” state for longer than 200 seconds. The alarm will self-clear when the time constant is no longer “frozen”.

Troubleshooting instructions

3.1.111

1

The PWCTLSUSP alarm is simply a consequent warning due to some other alarm. In other words, some other failure which caused the OLI card output power control to assume the frozen state is the real problem. So, troubleshoot and clear that alarm and the PWCTLSUSP will also clear. One possible reason could be that the OSCT card is failed or missing (a CFAIL alarm will be raised).

2

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

PWR1, PWR2, PWR3, and PWR4

Alarm name

Power Problem # (PWR#)

Default severity

Minor

Alarm object

All shelf types (except OTS-4000). Also note that PWR3 and PWR4 do not exist on MCU-Shelf or MCU-Slim shelf.

General information and causes

This alarm is raised if there is a failure of the indicated DC voltage feed to the shelf: • • • •

148

PWR1 (failure of the shelf’s UBAT1 power feed). PWR2 (failure of the shelf’s UBAT2 power feed). PWR3 (failure of the shelf’s UBAT3 power feed). PWR4 (failure of the shelf’s UBAT4 power feed).

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Troubleshooting instructions

3.1.112

1

Check for a blown or missing fuse in the rack. Verify that the rack Fuse Panel is equipped with the correct quantity and type of working fuses.

2

If the alarm persists, verify that all cables are connected properly from the rack Fuse Panel to the shelf terminals.

3

If the alarm persists, there may be a disconnected cable or missing fuse elsewhere (at Low Voltage Disconnect, Facility Battery Bay, etc). Verify that all required fuses and cable connections are present.

4

If the alarm persists, the voltage may be out-of-range. Disconnect the affected power cable from the shelf and measure the voltage being delivered to the end of this cable. Requirement: - 48 Vdc nominal, allowed range is - 42 Vdc to - 54 Vdc. If the voltage is out of range, measure the voltage at other points to determine where the problem originates (Fuse Panel, Low Voltage Disconnect, Facility Battery Bay, etc).

5

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

PWR12, PWR34, PWR13, and PWR24

Alarm name

Power Problem # (PWR#)

Default severity

Minor

Alarm object

OTS-4000 shelves

General information and causes

This alarm is raised if there is a failure of the indicated DC voltage feed to the shelf: • • • •

PWR12 (failure of the shelf’s 1-2 power feed). PWR34 (failure of the shelf’s 3-4 power feed). PWR13 (failure of the shelf’s 1-3 power feed). PWR24 (failure of the shelf’s 2-4 power feed).

Troubleshooting instructions 1

Check for a blown or missing fuse in the rack. Verify that the rack Fuse Panel is equipped with the correct quantity and type of working fuses.

2

If the alarm persists, verify that all cables are connected properly from the rack Fuse Panel to the shelf terminals.

3

If the alarm persists, there may be a disconnected cable or missing fuse elsewhere (at Low Voltage Disconnect, Facility Battery Bay, etc). Verify that all required fuses and cable connections are present.

4

If the alarm persists, the voltage may be out-of-range. Disconnect the affected power cable from the shelf and measure the voltage being delivered to the end of this cable. Requirement: - 48 Vdc nominal, allowed range is - 42 Vdc to - 54 Vdc. If the voltage is out of range, measure the voltage at other points to determine where the problem originates (Fuse Panel, Low Voltage Disconnect, Facility Battery Bay, etc).

5

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

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

149

Troubleshooting Instructions

3.1.113

Troubleshooting Manual (TSMN)

PWREQFAIL

Alarm name

Power Equalization Fail (PWREQFAIL)

Default severity

Major

Alarm object

OSCT cards

General information and causes

The PWREQFAIL alarm is raised if a fault occurred during the Power Equalization process.

Troubleshooting instructions

3.1.114

1

Open the “Optical Link Control - Config” window for the OSCT card raising the alarm. To do so, right-click on the OSCT card replica in the Equipment View and select Optical Link Control. Check the “Last Action” message field. Follow the instructions in chapter 7.1 “List of Last Action Messages” for any message(s) that may be displayed in the “Last Action” field.

2

If the alarm persists, perform a Forced Prestart and Power Equalization again.

3

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

REGEN_PAIR_UNAVAIL

Alarm name

Regenerator Pair Unavailable (REGEN_PAIR_UNAVAIL)

Default severity

Critical

Alarm object

OTS-4400 cards

General information and causes

All OTS-4400 Regenerator cards must be operated in paired slots (slots 2/3, 4/5, 6/7, and 8/9). The REGEN_PAIR_UNAVAIL alarm will be raised if one card of a pair is not present or not communicating. Once both regenerator cards are installed and operational, the alarm should clear.

Troubleshooting instructions

150

1

Note the slot number of the OTS-4000 card raising the alarm. Then, check its paired slot (e.g., if the card in slot 7 is raising the alarm, check slot 6). If the card in the paired slot is currently undergoing a reset, wait for the reset to complete, and the alarm whould clear. If the paired slot has raised a CMISM, CMISS, or CFAIL alarm, troubleshoot that alarm first.

2

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

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

Troubleshooting Manual (TSMN)

3.1.115

Troubleshooting Instructions

REMNELOS

Alarm name

Connection Loss to Remote NE (REMNELOS)

Default severity

Major

Alarm object

TL1-GNE cards

General information and causes

The connection from the TL1-GNE to the supervised NEs is monitored. If the supervised NE is not in the same subnet as the TL1-GNE (i.e., access is via DCC links), it is referred to as a Remote NE. If such a supervised NE is not reachable, the REMNELOS alarm will be raised.

Troubleshooting instructions

3.1.116

1

Establish the correct cable connections as designated in the SURPASS hiT 7500 Interconnection and Mechanical Assembly (ICMA) document. Ensure that all DCN settings are made as instructed in the relevant Commissioning Manual. Once connection to the supervised NE is established, the REMNELOS alarm will clear.

2

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

SABF

Alarm name

Sub Address Board Failure (SABF)

Default severity

Critical

Alarm object

MTS shelves. Note that SABF does not exist on the MCUShelf or MCU-Slim shelf.

General information and causes

The SABF alarm indicates that the Subrack Address Board (SAB or SABM) is present (correctly installed in the shelf) but has failed.

Troubleshooting instructions

!

1

Replace the failed Shelf Address Board with a spare as instructed in chapter 9.3 “SAB replacement procedures”.

2

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

Caution! Although each shelf's address is set via the rotary switch at the top of the shelf, the Subrack Address Board is required to provide certain backplane termination resistors. Note that OADM network elements must use SABM boards. The SABM includes a CAN Bus Amplifier since, for OADMs, the CAN Bus must be extended a longer distance via cable to shelves in multiple equipment bays. Be sure to replace a failed Subrack Address Board with the matching type: SAB or SABM.

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

151

Troubleshooting Instructions

3.1.117

Troubleshooting Manual (TSMN)

SAMISS

Alarm name

Partner Subagent Missing (SAMISS)

Default severity

Critical

Alarm object

OSCTUT cards in OADM network elements.

General information and causes

The SAMISS alarm indicates that one of the OSCTUT cards in an OADM100N or OADM100U network element is not communicating.

Troubleshooting instructions

3.1.118

1

If an SMISS alarm is raised, or if an OSCT card has raised a CP or CFAIL alarm, troubleshoot that alarm first.

2

If a subsystem is configured which is not in use and not present (i.e., an MCU and OSCT card are not installed), delete this subsystem to clear the SAMISS alarm.

3

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

SBL

Alarm name

Subband Loss (SBL)

Default severity

Critical

Alarm object

OD10, ODA10, OD20, and ODA20 cards

General information and causes

The SBL alarm is raised if the indicated card detects the loss of all the input channels that it is supposed to be receiving.

Troubleshooting instructions

152

1

Refer to Figure 27 through Figure 30. The most likely causes of an SBL alarm is one of the fiber cuts shown in these Figures. Fiber cuts further upstream will usually insert an OMS-FDI signal, which suppressed the SBL alarm). So, check the fibers shown in the drawing appropriate for the NE type. Connecting the fiber properly will clear the alarm.

2

Contact your next level of technical support before proceeding since the following action is traffic-affecting. If no other cause can be found, execute a Warm Start of the card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), execute a Cold Start. If the alarm persists after recovery time (approx 3 minutes), the card is defective. Replace the card with a spare.

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

Troubleshooting Manual (TSMN)

Figure 27

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

Troubleshooting Instructions

SBL alarm diagram for OTTU with OMDFIC + OMDFC

153

Troubleshooting Instructions

Figure 28

154

Troubleshooting Manual (TSMN)

SBL alarm diagram for OTTU with OMDFIC + OMD2IC

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

Troubleshooting Manual (TSMN)

Figure 29

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

Troubleshooting Instructions

SBL alarm diagram for OADM100U

155

Troubleshooting Instructions

Figure 30

156

Troubleshooting Manual (TSMN)

SBL alarm diagram for OADM100N

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

Troubleshooting Manual (TSMN)

3.1.119

Troubleshooting Instructions

SC_DISK_SPACE

Alarm name

Flash Capacity Problem (SC_DISK_SPACE)

Default severity

Minor

Alarm object

OTS-4700 cards.

General information and causes

This alarm will be raised if the free space on the card’s flash memory is too low.

Troubleshooting instructions

3.1.120

1

Perform a Cold Start of the card raising the SC_DISK_SPACE alarm.

2

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

SFPMISM1, SFPMISM2, SFPMISM3, and SFPMISM4

Alarm name

SFP Mismatch # (SFPMISM#)

Default severity

Minor

Alarm object

TEX-LH2, TEX-REGIO2, and TEX-V5 cards.

General information and causes

The indicated 2.5G port (Port 1 2, 3, or 4) will raise an SFPMISM alarm if the port has been provisioned for one type of SFP module, but another type is actually installed.

Troubleshooting instructions 1

Open the “Card Configuration” window for the card raising the SFPMISM alarm. To do so, right-click on the card replica in the Equipment View and select Card > Configuration. Verify that the Required SFP Type for the port raising the alarm is configured as desired (choices are Empty, I-16, S-16.1, or L-16.2). Click the Apply button, then close the window.

2

Ensure that the matching type of SFP module is installed in the port If the port was provisioned to be empty, ensure that no SFP module is installed - this will clear the SFPMISM alarm. Similarly, if the port was configured for an I-16 module, the approved I-16 SFP module must be installed. Note: it is not allowed to install a nonapproved SFP, even if it has the correct reach specification. Installing a nonapproved SFP will also result in an SFPMISM alarm. If a non-approved SFP has been installed the Actual SFP Type field on the Card Configuration window will display sfpUnknown.

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

157

Troubleshooting Instructions

3.1.121

Troubleshooting Manual (TSMN)

SFPMISS1, SFPMISS2, SFPMISS3, and SFPMISS4

Alarm name

SFP Missing # (SFPMISS#)

Default severity

Major

Alarm object

TEX-LH2, TEX-REGIO2, and TEX-V5 cards.

General information and causes

The indicated 2.5G port (Port 1 2, 3, or 4) will raise an SFPMISS alarm if the port has been provisioned for an SFP module, but no SFP is actually installed.

Troubleshooting instructions

3.1.122

1

Open the “Card Configuration” window for the card raising the SFPMISS alarm. To do so, right-click on the card replica in the Equipment View and select Card > Configuration. Verify that the Required SFP Type for the port raising the alarm is configured as desired (choices are Empty, I-16, S-16.1, or L-16.2). Click the Apply button, then close the window.

2

Ensure that the matching type of SFP module is installed in the port.

SFPMISS1, SFPMISS2, SFPMISS3, and SFPMISS4

Alarm name

SFP Missing P# (SFPMISS#)

Default severity

Major

Alarm object

I04T2G5 card

General information and causes

The indicated 2.5G port (Port 1 2, 3, or 4) will raise an SFPMISS alarm if the port has been provisioned for an SFP module, but no SFP is actually installed.

Troubleshooting instructions

3.1.123

158

1

Open the “Card Configuration” window for the card raising the SFPMISS alarm. To do so, right-click on the card replica in the Equipment View and select Card > Configuration. Verify that the Required SFP Type for the port raising the alarm is configured as desired (choices are Empty, I-16, S-16.1, or L-16.2). Click the Apply button, then close the window.

2

Ensure that the matching type of SFP module is installed in the port.

SFPUNQ1, SFPUNQ2, SFPUNQ3, and SFPUNQ4

Alarm name

SFP Unqualified # (SFPUNQ#)

Default severity

Minor

Alarm object

I04T2G5 card

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

Troubleshooting Manual (TSMN)

General information and causes

Troubleshooting Instructions

A card will raise the SFPUNQ# alarm if a non-approved SFP module has been inserted into the indicated port (1, 2, 3, or 4).

Troubleshooting instructions

3.1.124

1

Remove the non-approved SFP module from the port indicating the alarm (1, 2, 3, or 4). Then, insert the required type approved by Nokia Siemens Networks.

2

If the alarm persists, contact your next higher level of technical support. It will probably be necessary to replace the affected I04T2G5 card with a spare.

SHLFADRCH

Alarm name

Shelf Address Changed (SHLFADRCH)

Default severity

Critical

Alarm object

Shelves that contain an OSCT or SMU2 card.

General information and causes

Shelves which contain an OSCT or SMU2 card automatically perform a periodic check of the shelf address. The shelf address, as read from the shelf backplane, is checked against the shelf address obtained at card startup. If a single address check fails, the SHLFADRCH alarm will be raised. A Warm Start or Cold Start of the OSCT or SMU2 card is necessary to clear this alarm.

Troubleshooting instructions 1

The shelf raising the alarm contains either an OSCT card or SMU2 card. Execute a Warm Start of that card. If the alarm persists after recovery time (approximately 3 minutes), execute a Cold Start of the card. If the alarm persists after recovery time (approximately 3 minutes), dispatch personnel to the site.

2

Once on-site, check the rotary switch on the Network Element Alarm Panel at the top of the shelf. Verify that the rotary switch is set to the proper address. The addresses for the various shelves in each NE type are specified in the hiT 7500 Installation and Test Manual (ITMN). If the setting is incorrect, set the switch to the proper value.

3

Repeat step 1. If the alarm persists, contact your next higher level of technical support. It may be necessary to replace the relevant card (OSCT or SMU2) or the entire shelf.

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

159

Troubleshooting Instructions

3.1.125

Troubleshooting Manual (TSMN)

SLH

Alarm name

Span Loss High (SLH)

Default severity

Minor

Alarm object

Pre-amplifier OLIs and In-Line OLIs (OLIPxx and OLIIxx types

General information and causes

The SLH alarm is raised if the currently-measured attenuation of the span (leading up to the OLI raising the alarm) is too high (1 dB or more above the user-specified value for Span End of Life Attenuation). The correct value for Span End of Life Attenuation is listed in the route Commissioning Report and must be entered by the user on the “OLI Card Configuration” window during commissioning.

Troubleshooting instructions 1

Was the SLH alarm raised during link turn-up procedures, or after the system has been in service? –

–

160

Alarm was raised during link turn-up: in this case, verify that the configured Span End of Life Attenuation value for the affected OLI has been set to the value specified in the Commissioning Report. Also, if optional VOA2 cards are used, refer to the Optical Link Commissioning (OLC) Manual. See the chapter entitled “Line padding via VOA2 card”. Follow the instructions there to adjust line padding to the proper value. A new link startup procedure probably be needed to clear the SLH alarm. Alarm was raised after the system has been in service: continue to step 2.

2

Something has caused the span attenuation to increase. Open the affected OLI card's Card Configuration window and read the value for Current attenuation of the span before the OLI. If it is very high, schedule an OTDR read of the outside fiber plant at the next maintenance window to determine the location of the fiber problem.

3

Contact your next level of technical support before proceeding since the following action is traffic-affecting. If no other cause can be found, execute a Warm Start of the affected OLI card. If the alarm persists after recovery time (approx 3 minutes), execute a Cold Start. If the alarm persists after recovery time (approx 3 minutes), the OLI card is defective. Replace the OLI card with a spare.

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

Troubleshooting Manual (TSMN)

3.1.126

Troubleshooting Instructions

SLL

Alarm name

Span Loss Low (SLL)

Default severity

Minor

Alarm object

Pre-amplifier OLIs and In-Line OLIs (OLIPxx and OLIIxx types).

General information and causes

The SLL alarm is raised if: •

•

the automatically-calculated attenuation of the span (leading up to the OLI raising the alarms) decreases 10 dB or more below the user-specified value for Span End of Life Attenuation. the automatically-calculated attenuation of the span (leading up to the OLI raising the alarm) is too low (less than the minimum allowed).

The correct value for Span End of Life Attenuation is listed in the route Commissioning Report and must be entered by the user on the “OLI Card Configuration” window during commissioning. Troubleshooting instructions 1

Open the “OLI Card Configuration” window for the card raising the alarm. Read the value for Current Attenuation of the Span before the OLI. If it is very low, additional padding attenuation probably needs to be added to the span. Instructions for calculating the amount of required padding are contained in the Optical Link Commissioning (OLC) Manual (see the chapter entitled “Checking Span Loss”).

2

If no other cause can be found, execute a Warm Start of the affected OLI card. If the alarm persists after recovery time (approx 3 minutes), contact your next level of technical support before proceeding since the following action is traffic-affecting. Execute a Cold Start of the affected OLI card. If the alarm persists after recovery time (approx 3 minutes), the OLI card is defective. Replace the OLI card with a spare.

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

161

Troubleshooting Instructions

3.1.127

Troubleshooting Manual (TSMN)

SPFAIL

Alarm name

Swap Preparation Failure (SPFAIL)

Default severity

Warning

Alarm object

MCU card

General information and causes

As part of the procedure to download new APS (Application Program System) software to an NE, the user may first perform a Swap Preparation check before an attempt is made to swap the Inactive APS to the Active bank. This check verifies that the migration to the new APS in the Inactive Bank is supported by this NE. If the Swap Preparation check fails, the SPFAIL alarm will be raised. The system will not permit the APS swap to proceed until the incompatible components are replaced and the system successfully completes a Swap Preparation check.

Troubleshooting instructions 1

Verify that the Inactive bank contains the exact APS version proper for the NE raising the SPFAIL alarm. Check the Order Number, Version Number, and SW/FW Code as displayed on the “Software Management” window. If the Inactive APS is not the correct one, download the proper APS to the Inactive bank. Then, click the Swap Preparation button again on the “Software Management” window to re-run the compatibility check. If the check passes, the SPFAIL alarm will clear when the Swap Preparation process completes.

2

If the SPFAIL alarm persists, perform a compatibility check. Click the Inactive APS Compatibility button. Verify that each installed component is compatible with the Inactive APS. If not, the incorrect components must be replaced with the proper versions. Once all compatible components are installed, click the Swap Preparation button again to re-run the compatibility check. This time, the check should pass successfully and the SPFAIL alarm will clear. The Inactive APS can then be swapped to the Active bank.

3

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

g The SPFAIL alarm will be raised only if the Extended Swap Preconditions feature is enabled. This option appears on the “Software Management” window. Set the drop-down box to yes to enable this feature.

162

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

Troubleshooting Manual (TSMN)

3.1.128

Troubleshooting Instructions

SRCP

Alarm name

Subrack Cooling Problem (SRCP)

Default severity

Major

Alarm object

All shelf types (except OTS-4000 and HDS)

General information and causes

A shelf will raise the SRCP alarm if both Fan Units (upper and lower) in the shelf have failed.

Troubleshooting instructions

3.1.129

1

Troubleshoot the FNLOW and FNUPP fan unit alarms individually to clear the SRCP alarm.

2

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

STORAGEFAIL

Alarm name

Storage Fail (STORAGEFAIL)

Default severity

Critical

Alarm object

All plug-in cards

General information and causes

Periodically, each NE checks the values stored in the "Card Label" for every card in the NE. If there is a problem reading any card's Card Label data, or if the retrieved data does not match the expected data, the STORAGEFAIL alarm will be raised for that card.

Troubleshooting instructions

!

!

1

Although traffic is not interrupted by a STORAGEFAIL alarm, replace the card raising the STORAGEFAIL alarm at the earliest opportunity.

2

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

Caution! Never Cold Start any card that has raised a STORAGEFAIL alarm. Doing so will likely cause traffic loss.

Caution! Never Warm Start any card that has raised a STORAGEFAIL alarm. Doing so will cause the MCU to lose visibility to that card.

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

163

Troubleshooting Instructions

!

3.1.130

Troubleshooting Manual (TSMN)

Caution! When a STORAGEFAIL alarm is active, it will not be possible to perform an APS swap/upgrade (example: an upgrade from SURPASS hiT 7500 Version 3.21 to 3.21.10). Any card that has an active STORAGEFAIL alarm is automatically set to "not prepared for swap". Therefore, it is necessary to clear any and all STORAGEFAIL alarms before an APS upgrade can be performed.

SUBSMISMHDS

Alarm name

Subsystem Mismatch HDS (SUBSMISMHDS)

Default severity

Major

Alarm object

OCU73 Subsystem

General information and causes

This alarm indicates that the connecting OCU73 subsystem cannot verify that it is the same system as before. Allowing a different OCU73 to connect would most likely result in traffic loss. Therefore, such a conection is not allowed and is indicated by raising the SUBSMISMHDS alarm.

Troubleshooting instructions

3.1.131

1

Check that the correct HDS shelf is phyiscally connected to the OCU73 subsystem raising the alarm. If not, make the correct connection and the alarm will clear (typically within one minute).

2

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

SWDWNLD_OCU40FAIL

Alarm name

Sw Download in OCU40 Failed (SWDWNLD_OCU40FAIL)

Default severity

Critical

Alarm object

OTS-4011, OTS-4040, OTS-4400, OTS-4520, and OTS4540 cards.

General information and causes

The SWDWNLD_OCU40FAIL alarm will be raised if a software download to the indicated card fails.

Troubleshooting instructions

164

1

Warm Start the card raising the SWDWNLD_OCU40 alarm. Wait up to 3 minutes for the card to recover from the Warm Start and see if the alarm clears.

2

If the alarm persists, Cold Start the card raising the SWDWNLD_OCU40FAIL alarm. Wait for the card to recover from the Cold Start. This can require up to 15 minutes (20 minutes for an OTS-4011).

3

If the alarm persists after the card recovers from the Cold Start, contact your next higher level of technical support.

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

Troubleshooting Manual (TSMN)

3.1.132

Troubleshooting Instructions

SWP

Alarm name

Switch Problem (SWP)

Default severity

Minor

Alarm object

OPAPC cards

General information and causes

The OPAPC card contains an on-board Optical Spectrum Analyzer (OSA). So, in order to monitor two input ports, the card must switch back and forth. The SWP alarm indicates a problem with this switch.

Troubleshooting instructions

3.1.133

1

Warm Start the card raising the SWP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare.

2

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

SWP1, SWP2, SWP3, and SWP4

Alarm name

Switch Problem # (SWP#)

Default severity

Minor

Alarm object

OCS and OCASC cards.

General information and causes

The OCS and OCASC cards each contain on-board optical switches. The SWP# alarm indicates a problem with the designated switch.

Troubleshooting instructions 1

Warm Start the card raising the SWP# alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare.

2

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

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

165

Troubleshooting Instructions

3.1.134

Troubleshooting Manual (TSMN)

SYNCPROG

Alarm name

Synchronization in Progress (SYNCPROG)

Default severity

Warning

Alarm object

The SYNCPROG alarm can be raised by: – – –

General information and causes

OTS-4000 shelf Line Card slots in OTS-4000 shelf HDS shelf

If the synchronization process is running between an MCUOCU40 card and one of the OTS-4000 shelves it manages, the affected OTS-4000 shelf will raise the SYNCPROG alarm. Similarly, if the synchronization process is running between an MCU-OCU73 card and one of the HDS shelves it manages, the affected HDS shelf will raise the SYNCPROG alarm.

Troubleshooting instructions 1

What object is raising the SYNCPROG alarm? – –

2

If the alarm is being raised by a Line Card slot in the OTS-4000 shelf, it indicates that there was a software or firmware crash on the card occupying that slot. Wait 20 minutes to see if the alarm self-clears. If the alarm does not self-clear, the problem can be considered equivalent to a card failure. Therefore, go to the troubleshooting instructions for CFAIL raised by 40G card slots in chapter 3.1.18.4.

3

The SYNCPROG alarm is only a warning that the synchronization process is being executed. When the process is complete, the SYNCPROG alarm will self-clear. However, if the SYNCPROG alarm remains active for more than 60 minutes, continue to step 4.

4

Warm Start the Controller card in the shelf raising the alarm as follows: – –

5

6

Yes: End of procedure. No: Cold Start the same controller card that was Warm Started in step 4. Wait 15 minutes. Ignore any other that may be generated due to the Cold Start. Continue to step 6.

Did the SYNCPROG alarm clear? – –

7

If an OTS-4000 shelf is raising the alarm, Warm Start the OTS-4700 card in that shelf. If an HDS shelf is raising the alarm, Warm Start the Controller card (CCEP, CCMP, or CCSP) in that shelf.

Did the SYNCPROG alarm clear? – –

166

Line Card slot in OTS-4000 shelf: go to step 2. OTS-4000 or HDS shelf: skip step 2 and go directly to step 3.

Yes: End of procedure. No: Continue to step 7.

Cold Start the following MCU card:

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

Troubleshooting Manual (TSMN)

– – 8

If an OTS-4000 shelf is raising the alarm, Cold Start the MCU-OCU40 card that manages the shelf raising the alarm. If an HDS shelf is raising the alarm, Cold Start the MCU-OCU73 card that manages the shelf raising the alarm.

Did the SYNCPROG alarm clear? – –

9

Troubleshooting Instructions

Yes: End of procedure. No: Continue to step 9.

Dispatch personnel to the site. Re-seat (withdraw from the shelf, then re-insert) the following card: –

–

If an OTS-4000 shelf is raising the alarm, withdraw the OTS-4700 card in that shelf, then re-seat it. After doing so, if the SYNCPROG alarm persists for more than 60 minutes, contact your next higher level of technical support. If an HDS shelf is raising the alarm, withdraw the CCxP (CCEP, CCMP or CCSP) card in that shelf, then re-seat it. After doing so, if the SYNCPROG alarm persists for more than 60 minutes, contact your next higher level of technical support.

g Any NE with one (or more) SYNCPROG alarms raised may experience long delays responding to management commands.

3.1.135

T3LOS

Alarm name

No Valid T3 Signal (T3LOS)

Default severity

Minor

Alarm object

OSCT cards

General information and causes

The T3LOS alarm indicates a loss of the optional external T3 clock signal. A loss of the T3 clock may affect services carried via the OSC (e.g. V.11), but does not lead to a loss of communication with the network element.

Troubleshooting instructions

3.1.136

1

Verify that the cable connection from the external clock generator to the T3 connector on the shelf Connector Panel (COPA) is made properly. Correct as necessary.

2

If the alarm persists, contact your next higher level of technical support. The external clock source may need to be replaced.

TargetP

Alarm name

Target Value not Reached (TargetP)

Default severity

Minor

Alarm object

Raman cards

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

167

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions 1

Is traffic affected due to the TargetP condition? –

–

2

3.1.137

Yes: Warm Start the card raising the TargetP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the TargetP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

TempHi

Alarm name

Temperature too High (TempHi)

Default severity

Major

Alarm object

All shelf types.

General information and causes

A TempHi alarm is raised if the temperature on the indicated shelf is too high.

Troubleshooting instructions

3.1.138

168

1

Troubleshoot and clear any fan-related alarm first since a cooling fan problem can result in elevated equipment temperatures. At the threshold where the TempHi alarm is triggered, a shelf cannot tolerate the failure of even a single fan.

2

If all fans are working correctly, but the TempHi alarm persists, check the ambient temperature around the relevant shelf. It must be lower than 40°C (104°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications. Once the ambient temperature is corrected, the TempHi alarm should clear. If the alarm persists, continue to step 3.

3

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

TempHiC

Alarm name

Temperature too High Critical (TempHiC)

Default severity

Critical

Alarm object

OTS-4000 shelves.

General information and causes

A TempHiC alarm is raised if the temperature on the indicated shelf has reached the critical threshold of 55°C (131°F). Due to its crtical nature, immediate action is necessary to clear this alarm to avoid service interruption.

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Troubleshooting instructions 1

!

3.1.139

Troubleshoot and clear any fan-related alarm first since a cooling fan problem can result in elevated equipment temperatures.

Caution! Since TempHiC is a critical alarm, immediate action to clear the alarm condition is necessary. Otherwise, loss of traffic can occur.

2

If the TempHiC alarm persists, check the ambient temperature around the relevant shelf. It must be lower than 40°C (104°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications. Once the ambient temperature is corrected, the TempHiC alarm should clear. If the alarm persists, continue to step 3.

3

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

TempP

Alarm name

Temperature Problem (TempP)

Default severity

Major

Alarm object

All types of OLI cards, PUMP cards, OM20 cards, OD20 cards, ODA20 cards, OMD cards, and PQM cards.

General information and causes

A TempP alarm is raised if the temperature on the indicated card is too high.

Troubleshooting instructions 1

Check if the shelf containing the affected card has raised a Fan alarm: FNLOW, FNLOWM, FNUPP, or FNUPPM, and troubleshoot any such alarm first.

2

If the TempP alarm persists, check the ambient temperature around the shelf. It must be lower than 50°C (122°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications.

3

Contact your next level of technical support before proceeding since the following action is traffic-affecting. If no other cause can be found, Warm Start the card raising the alarm. If the TempP alarm persists after Warm Start recovery time (approx 3 minutes), Cold Start the card. If the TempP alarm persists after Cold Start recovery time (approx 3 minutes), the card is defective. Replace the affected card with a spare.

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

169

Troubleshooting Instructions

3.1.140

Troubleshooting Manual (TSMN)

TempPVOA

Alarm name

Temperature Problem VOA (TempPVOA)

Default severity

Minor

Alarm object

TSC card

General information and causes

A TempPVOA alarm is raised if the temperature on the indicated card is too high.

Troubleshooting instructions

3.1.141

1

Check if the shelf containing the affected card has raised a Fan alarm: FNLOW, FNLOWM, FNUPP, or FNUPPM, and troubleshoot any such alarm first.

2

If the TempPVOA alarm persists, check the ambient temperature around the shelf. It must be lower than 50°C (122°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications.

3

If no other cause can be found, Warm Start the card raising the alarm. If the TempPVOA alarm persists after Warm Start recovery time (approx 3 minutes), contact your next level of technical support before proceeding. Cold Start the card raising the alarm. If the TempPVOA alarm persists after Cold Start recovery time (approx 3 minutes), the card is defective. Replace the defective card with a spare.

TempP1, TempP2, TempP3, and TempP4

Alarm name

Temperature Problem # (TempP#)

Default severity

Major

Alarm object

OCA and OCAS cards.

General information and causes

A TempP# alarm is raised if the temperature on the indicated card is too high.

Troubleshooting instructions

170

1

Check if the shelf containing the affected card has raised a Fan alarm: FNLOW, FNLOWM, FNUPP, or FNUPPM, and troubleshoot any such alarm first.

2

If the TempP# alarm persists, check the ambient temperature around the shelf. It must be lower than 50°C (122°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications.

3

Contact your next level of technical support before proceeding since the following action is traffic-affecting. If no other cause can be found, Warm Start the card raising the alarm. If the TempP# alarm persists after Warm Start recovery time (approx 3 minutes), Cold Start the card. If the TempP# alarm persists after Cold Start recovery time (approx 3 minutes), the card is defective. Replace the affected card with a spare.

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

Troubleshooting Manual (TSMN)

3.1.142

Troubleshooting Instructions

TempRegRun

Alarm name

Temperature Regulation Running (TempRegRun)

Default severity

Warning

Alarm object

Raman cards

General information and causes

A TempRegRun alarm is raised if the temperature on the indicated card is too high.

Troubleshooting instructions

3.1.143

1

Check if the shelf containing the affected card has raised a Fan alarm: FNLOW, FNLOWM, FNUPP, or FNUPPM, and troubleshoot any such alarm first.

2

If the TempRegRun alarm persists, check the ambient temperature around the shelf. It must be lower than 50°C (122°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications.

3

Contact your next level of technical support before proceeding since the following action is traffic-affecting. If no other cause can be found, Warm Start the card raising the alarm. If the TempRegRun alarm persists after Warm Start recovery time (approx 3 minutes), Cold Start the card. If the TempRegRun alarm persists after Cold Start recovery time (approx 3 minutes), the card is defective. Replace the affected card with a spare.

TimP

Alarm name

Timing Problem (TimP)

Default severity

Minor

Alarm object

OSCT card

General information and causes

The TimP alarm is raised if the precision oscillator on the indicated OSCT card fails.

Troubleshooting instructions 1

Is traffic affected due to the TimP condition? –

–

2

Yes: Warm Start the card raising the TimP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the TimP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

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

171

Troubleshooting Instructions

3.1.144

Troubleshooting Manual (TSMN)

TSCh1TD

Alarm name

Transmit Degrade TSCh1 (TSCh1TD)

Default severity

Minor

Alarm object

TSC card

General information and causes

A TSCh1TD alarm will be raised if the Transient Suppression Channel 1 laser current has degraded.

Troubleshooting instructions 1

3.1.145

The TSCh1TD alarm serves as an advance warning that a TSCh1TF alarm might soon occur. Immediate replacement of the card is not necessary. However, TSC card replacement should be scheduled for the next convenient maintenance period.

TSCh2TD

Alarm name

Transmit Degrade TSCh2 (TSCh2TD)

Default severity

Minor

Alarm object

TSC card

General information and causes

A TSCh2TD alarm will be raised if the Transient Suppression Channel 2 laser current has degraded.

Troubleshooting instructions 1

3.1.146

172

The TSCh2TD alarm serves as an advance warning that a TSCh2TF alarm might soon occur. Immediate replacement of the card is not necessary. However, TSC card replacement should be scheduled for the next convenient maintenance period.

TSCh3TD

Alarm name

Transmit Degrade TSCh3 (TSCh3TD)

Default severity

Minor

Alarm object

TSC card

General information and causes

A TSCh3TD alarm will be raised if the Transient Suppression Channel 3 laser current has degraded.

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Troubleshooting instructions 1

3.1.147

The TSCh3TD alarm serves as an advance warning that a TSCh3TF alarm might soon occur. Immediate replacement of the card is not necessary. However, TSC card replacement should be scheduled for the next convenient maintenance period.

TSCh4TD

Alarm name

Transmit Degrade TSCh4 (TSCh4TD)

Default severity

Minor

Alarm object

TSC card

General information and causes

A TSCh4TD alarm will be raised if the Transient Suppression Channel 4 laser current has degraded.

Troubleshooting instructions 1

3.1.148

The TSCh4TD alarm serves as an advance warning that a TSCh4TF alarm might soon occur. Immediate replacement of the card is not necessary. However, TSC card replacement should be scheduled for the next convenient maintenance period.

TSCh1TF

Alarm name

Transmit Fail TSCh1 (TSCh1TF)

Default severity

Minor

Alarm object

TSC card

General information and causes

A TSCh1TF alarm will be raised if the Transient Suppression Channel 1 laser has failed.

Troubleshooting instructions 1

3.1.149

Warm Start the card raising the TSCh1TF alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, TSC card replacement should be scheduled for the next convenient maintenance period.

TSCh2TF

Alarm name

Transmit Fail TSCh2 (TSCh2TF)

Default severity

Minor

Alarm object

TSC card

General information and causes

A TSCh2TF alarm will be raised if the Transient Suppression Channel 2 laser has failed.

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

173

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions 1

3.1.150

Warm Start the card raising the TSCh2TF alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, TSC card replacement should be scheduled for the next convenient maintenance period.

TSCh3TF

Alarm name

Transmit Fail TSCh3 (TSCh3TF)

Default severity

Minor

Alarm object

TSC card

General information and causes

A TSCh3TF alarm will be raised if the Transient Suppression Channel 3 laser has failed.

Troubleshooting instructions 1

174

Warm Start the card raising the TSCh3TF alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, TSC card replacement should be scheduled for the next convenient maintenance period.

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

Troubleshooting Manual (TSMN)

3.1.151

Troubleshooting Instructions

TSCh4TF

Alarm name

Transmit Fail TSCh4 (TSCh4TF)

Default severity

Minor

Alarm object

TSC card

General information and causes

A TSCh4TF alarm will be raised if the Transient Suppression Channel 4 laser has failed.

Troubleshooting instructions 1

3.1.152

Warm Start the card raising the TSCh4TF alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, TSC card replacement should be scheduled for the next convenient maintenance period.

TSCh1TEMP

Alarm name

Temperature Problem TSCh1 (TSCh1TEMP)

Default severity

Minor

Alarm object

TSC card

General information and causes

The TSC card will raise a TSCh1TEMP alarm if it detects an overtemperature condition on its Transient Suppression Channel 1 circuitry.

Troubleshooting instructions

3.1.153

1

Check if the shelf containing the affected card has raised a Fan alarm: FNLOW, FNLOWM, FNUPP, or FNUPPM, and troubleshoot any such alarm first.

2

If the TSCh1TEMP alarm persists, check the ambient temperature around the shelf. It must be lower than 50°C (122°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications.

3

If no other cause can be found, Warm Start the card raising the alarm. If the TSCh1TEMP alarm persists after Warm Start recovery time (approx 3 minutes), contact your next level of technical support before proceeding. Cold Start the card raising the alarm. If the TSCh1TEMP alarm persists after Cold Start recovery time (approx 3 minutes), the card is defective. Replace the defective card with a spare.

TSCh2TEMP

Alarm name

Temperature Problem TSCh21 (TSCh2TEMP)

Default severity

Minor

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

175

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Alarm object

TSC card

General information and causes

The TSC card will raise a TSCh2TEMP alarm if it detects an overtemperature condition on its Transient Suppression Channel 2 circuitry.

Troubleshooting instructions

3.1.154

1

Check if the shelf containing the affected card has raised a Fan alarm: FNLOW, FNLOWM, FNUPP, or FNUPPM, and troubleshoot any such alarm first.

2

If the TSCh2TEMP alarm persists, check the ambient temperature around the shelf. It must be lower than 50°C (122°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications.

3

If no other cause can be found, Warm Start the card raising the alarm. If the TSCh2TEMP alarm persists after Warm Start recovery time (approx 3 minutes), contact your next level of technical support before proceeding. Cold Start the card raising the alarm. If the TSCh2TEMP alarm persists after Cold Start recovery time (approx 3 minutes), the card is defective. Replace the defective card with a spare.

TSCh3TEMP

Alarm name

Temperature Problem TSCh3 (TSCh3TEMP)

Default severity

Minor

Alarm object

TSC card

General information and causes

The TSC card will raise a TSCh3TEMP alarm if it detects an overtemperature condition on its Transient Suppression Channel 3 circuitry.

Troubleshooting instructions

176

1

Check if the shelf containing the affected card has raised a Fan alarm: FNLOW, FNLOWM, FNUPP, or FNUPPM, and troubleshoot any such alarm first.

2

If the TSCh3TEMP alarm persists, check the ambient temperature around the shelf. It must be lower than 50°C (122°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications.

3

If no other cause can be found, Warm Start the card raising the alarm. If the TSCh3TEMP alarm persists after Warm Start recovery time (approx 3 minutes), contact your next level of technical support before proceeding. Cold Start the card raising the alarm. If the TSCh3TEMP alarm persists after Cold Start recovery time (approx 3 minutes), the card is defective. Replace the defective card with a spare.

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

Troubleshooting Manual (TSMN)

3.1.155

Troubleshooting Instructions

TSCh4TEMP

Alarm name

Temperature Problem TSCh4 (TSCh4TEMP)

Default severity

Minor

Alarm object

TSC card

General information and causes

The TSC card will raise a TSCh4TEMP alarm if it detects an overtemperature condition on its Transient Suppression Channel 4 circuitry.

Troubleshooting instructions

3.1.156

1

Check if the shelf containing the affected card has raised a Fan alarm: FNLOW, FNLOWM, FNUPP, or FNUPPM, and troubleshoot any such alarm first.

2

If the TSCh4TEMP alarm persists, check the ambient temperature around the shelf. It must be lower than 50°C (122°F) or as otherwise quoted in the official SURPASS hiT 7500 product specifications.

3

If no other cause can be found, Warm Start the card raising the alarm. If the TSCh4TEMP alarm persists after Warm Start recovery time (approx 3 minutes), contact your next level of technical support before proceeding. Cold Start the card raising the alarm. If the TSCh4TEMP alarm persists after Cold Start recovery time (approx 3 minutes), the card is defective. Replace the defective card with a spare.

TWOSYNCMSTR

Alarm name

Second Sync Master Detected (TWOSYNCMSTR)

Default severity

Minor

Alarm object

OSCTUT card

General information and causes

In networks featuring concatenated or meshed topologies, one OSCTUT card must be designated as the Synchronization Master, and all others must be designated as Synchronization Slaves. One Master is necessary to ensure that the continuous pre-emphasis process operates correctly. If more than one OSCTUT card has inadvertently been designated to be Synchronization Master, the TWOSYNCMSTR alarm will be raised. The TWOSYNCMSTR alarm will be displayed on GUI windows as raised against the object "Link Control 1". Link Control 1 designates Tx direction. (Link Control 2 designates the Rx direction; however, this will never be seen in SURPASS hiT 7500).

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

177

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions

3.1.157

1

Configure only one OSCTUT card to be Synchronization Master. This will clear the TWOSYNCMSTR alarm. To do so, follow the steps below.

2

Choose the OSCTUT that will be the Synchronization Master. Right-click on its Card Replica in the Equipment View and select Optical Link Control.

3

On the resulting “Optical Link Control - Config” window, set the Link Synchronization Master to enabled. Click the Apply icon.

4

Open the “Optical Link Control - Config” window for every other OSCTUT card in the network and ensure that Link Synchronization Master is set to disabled.

5

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

TWOTIMMSTR

Alarm name

Two Timing Masters (TWOTIMMSTR)

Default severity

Minor

Alarm object

OSCTUT card

General information and causes

A clock source (T2 internal oscillator on the OSCT or T3 external source) at either end of the link must be designated to be the link's Timing Master. At 1-minute intervals, the Master transmits a timing synchronization pulse that is used by all OPAPC and OSCT cards along the link. If two clock sources have inadvertently been designated to be the Master, the TWOTIMMSTR alarm will be raised.

g The Timing Master OSCT may raise a transient TWOTIMMSTR alarm when another OSCT card is undergoing a reboot. In this case, the TWOTIMMSTR alarm should quickly clear itself when conditions stabilize. Troubleshooting instructions

178

1

Configure the priority ("high" or "low") of the T2 and optional T3 clocks correctly in order to specify only one Timing Master. These priority settings are made on each OSCT “Card Configuration” window.

2

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

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

Troubleshooting Manual (TSMN)

3.1.158

Troubleshooting Instructions

ULEDF

Alarm name

ULed Fail (ULEDF)

Default severity

Warning

Alarm object

MCU and SMU cards

General information and causes

The ULEDF alarm indicates a low-voltage problem with the backplane LED bus. The MCU card (or the SMU card in shelves so equipped) supervises the backplane ULED bus. [This bus is routed to every active card in the shelf. If a card suffers a failure and cannot light its front panel red LED on its own, then voltage from the ULED bus is available to do so].

Troubleshooting instructions

3.1.159

1

The failure is typically on some other card managed by the MCU / SMU, or the problem could be in the LED bus itself. If the problem is on another card, it will probably be showing a CP (Card Problem) alarm. If a card is showing a CP alarm, execute a Warm Start of that card. Repeat for any other cards that might be showing a CP alarm.

2

If the alarm persists, contact your next higher level of technical support before proceeding. In extremely rare cases, the backplane voltage bus itself may have failed. The only solution is to replace the entire shelf.

VOAP

Alarm name

VOA Problem (VOAP)

Default severity

Minor

Alarm object

WBAU card and CAX card

General information and causes

The VOAP alarm indicates a problem with the variable optical attenuator (VOA) in the add-path of the reported card. Adjusting this VOA is necessary, for example, when performing a channel upgrade.

Troubleshooting instructions 1

Is traffic affected due to the VOAP condition? –

–

2

Yes: Warm Start the card raising the VOAP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the VOAP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

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

179

Troubleshooting Instructions

3.1.160

Troubleshooting Manual (TSMN)

VOAP#

Alarm name

VOA# Problem (VOAP#)

Default severity

Minor

Alarm object

OM10, OM20, ODA10, ODA20, VOAP2, and TSC cards.

General information and causes

A card will raise a VOAP# alarm if it detects a problem with one of its on-board variable optical attenuators (the particular VOA is identified by number, i.e., VOAP1, VOAP2, etc).

Troubleshooting instructions 1

What type of card has raised the VOAP# alarm? –

–

OM10, OM20, VOAP2, or TSC card: Warm Start the card raising the VOAP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the alarm persists, immediately replace the failed card with a spare. ODA10 or ODA20 cards: There is a small chance that the VOAP# alarm may be a false alarm. To determine if this is the case, begin with step 2 below

2

Open the “Traffic Configuration” window for the ODA card raising the VOAP# alarm. Decrease the value of the "Reference Power" of the affected channel by 2.5 dB.

3

Wait about 3 seconds and update the “Traffic Configuration” window. Check that the VOA movement has been completed. Then, wait 1 minute.

4

Change the value of the "Reference Power" back to its original value (i.e., increase it by 2.5 dB).

5

Wait about 3 seconds and update the Traffic Configuration Window. Check that the VOA movement has been completed. Wait 1 minute.

6

Warm Start the ODA card. Wait 3 minutes for the Warm Start process to complete.

7

Check the alarm list of the ODA card. If the VOAP# alarm is not raised again, then it was a falsely raised alarm due to a software anomaly. In this case, ignore the original occurrence of the VOAP# alarm. However, if the VOAP# alarm is still present, the alarm is not false. In that case, execute steps 8 - 12 below.

8

Open this network element's “Optical Link Control-Config” window. To do so, rightclick on the OSCTUT Card Replica in the Equipment View and select Optical Link Control. Select the Preamplifier tab.

9

Set Attenuator Control to disabled, then click the Apply button. This makes it possible to manually adjust the VOAs on the ODA cards (see next step).

10 Open the “Traffic-Config” window for the affected card. Note that the Manual VOA adjustment field is enabled (not grayed out) since Step 9 was performed. Locate the affected VOA in the list on the window. Increase the attenuation of this VOA by 1 dB by keying-in the correct value (example: if current attenuation is listed as 6.4 dB, key-in 7.4 dB). Click Apply. 11 Return to the “Optical Link Control - Config” window from Step 8. Set Optical Link Control back to enabled. Click Apply.

180

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

12 Return to the “Traffic-Config” window for this ODA card. Verify that the Manual VOA Adjustment field is grayed-out again (i.e., the field is disabled). At the next preemphasis cycle, the affected VOA will re-adjust and clear the VOAP# alarm. 13 If the alarm persists, contact your next higher level of technical support.

3.1.161

VOLT

Alarm name

Voltage Problem (VOLT)

Default severity

Minor

Alarm object

All OTS card types (OTS-4700 Controller card and OTS-4xxx traffic cards).

General information and causes

Various circuitry points on OTS cards are monitored for correct voltage levels. If a voltage level is too high, the VOLT alarm will be raised.

Troubleshooting instructions

3.1.162

1

Wait 5 minutes to see if the alarm self-clears. The overvoltage problem may have only been a temporary condition.

2

If the alarm persists, contact your next higher level of technical support before proceeding. Warm Start the card raising the alarm. If the VOLT alarm persists after Warm Start recovery time (approx 3 minutes), Cold Start the card. If the VOLT alarm persists after Cold Start recovery time (5 to 20 minutes), the card is defective. Replace the affected card with a spare.

VOLTL

Alarm name

Voltage Problem Line (VOLTL)

Default severity

Minor

Alarm object

OTS-4011, OTS-4040, OTS-4400, OTS-4520, OTS-4540 cards.

General information and causes

Various circuitry points on OTS card Line interfaces are monitored for correct voltage levels. If a voltage level is too high, the VOLTL alarm will be raised.

Troubleshooting instructions 1

Wait 5 minutes to see if the alarm self-clears. The overvoltage problem may have only been a temporary condition.

2

If the alarm persists, contact your next higher level of technical support before proceeding. Warm Start the card raising the alarm. If the VOLTL alarm persists after Warm Start recovery time (approx 3 minutes), Cold Start the card. If the VOLTL alarm persists after Cold Start recovery time (5 to 20 minutes), the card is defective. Replace the affected card with a spare.

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

181

Troubleshooting Instructions

3.1.163

Troubleshooting Manual (TSMN)

VOLTT1, VOLTT2, VOLTT3, and VOLTT4

Alarm name

Voltage Problem Trib # (VOLTT#)

Default severity

Minor

Alarm object

OTS-4011 and OTS-4040 cards. (OTS-4040 VOLTT1 only).

General information and causes

Various circuitry points on OTS card Tributary interfaces are monitored for correct voltage levels. If a voltage level is too high, the VOLTT# alarm will be raised.

Troubleshooting instructions

3.1.164

1

Wait 5 minutes to see if the alarm self-clears. The overvoltage problem may have only been a temporary condition.

2

If the alarm persists, contact your next higher level of technical support before proceeding. Warm Start the card raising the alarm. If the VOLTT# alarm persists after Warm Start recovery time (approx 3 minutes), Cold Start the card. If the VOLTT# alarm persists after Cold Start recovery time (5 to 20 minutes), the card is defective. Replace the affected card with a spare.

WSSMP

Alarm name

WSS Module Problem (WSSMP)

Default severity

Major

Alarm object

WSSC card

General information and causes

The WSSMP alarm indicates a fault on the WSSC card's switch module.

Troubleshooting instructions 1

Is traffic affected due to the WSSMP condition? –

–

2

182

Yes: Warm Start the card raising the WSSMP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare. No: Warm Start the card raising the WSSMP alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, do NOT execute a Cold Start. Wait for the next scheduled maintenance window to replace the faulty card.

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

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

Troubleshooting Manual (TSMN)

3.1.165

Troubleshooting Instructions

XFP_MISM1

Alarm name

Mismatch Optical Module 1 (XFP_MISM1)

Default severity

Minor

Alarm object

I01T10G card

General information and causes

The XFP_MISM1 alarm will be raised if the card detects that Port 1 is missing a provisioned XFP module.

Troubleshooting instructions 1

Insert the correct XFP module into the empty port.

2

If the alarm persists, contact your next higher level of technical support. It will probably be necessary to replace the affected I01T10G card with a spare.

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

183

Troubleshooting Instructions

3.1.166

Troubleshooting Manual (TSMN)

XFP_MISS1, XFP_MISS2, XFP_MISS3, and XFP_MISS4

Alarm name

Missing Optical Module # (XFP_MISS#)

Default severity

Major

Alarm object

OTS-4011 and I01T10G cards.

General information and causes

The XFP_MISS1/2/3/4 alarm will be raised if an OTS-40xx card detects that one of its ports (1, 2, 3, or 4) is missing a provisioned XFP module.

Troubleshooting instructions

3.1.167

1

Insert the correct XFP module into the empty port.

2

If the alarm persists, contact your next higher level of technical support. It will probably be necessary to replace the affected OTS-40xx card with a spare.

XFP_QUAL1, XFP_QUAL2, XFP_QUAL3, and XFP_QUAL4

Alarm name

Unqualified Optical Module# (XFP_QUAL#)

Default severity

Minor

Alarm object

OTS-4011 and I01T10G cards.

General information and causes

A card will raise the XFP_QUAL alarm if a non-approved XFP module has been inserted into the indicated port (1, 2, 3, or 4).

Troubleshooting instructions

184

1

Remove the non-approved XFP module from the port indicating the alarm (1, 2, 3, or 4). Then, insert the required type approved by Nokia Siemens Networks.

2

If the alarm persists, contact your next higher level of technical support. It will probably be necessary to replace the affected card with a spare.

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

Troubleshooting Manual (TSMN)

3.2

Troubleshooting Instructions

Communication Alarms This section contains troubleshooting instructions for hiT 7500 Communication alarms.

3.2.1

BDI

Alarm name

Backward Defect Indication (BDI)

Default severity

Minor

Alarm object

BDI can be raised by the following alarm objects: • • • • • • • • • • • • • • • • • •

General information and causes

OSCT card TEX card Section (OTU2-CTP) TEX card Path (ODU2-TTP) TEX card Tributary - Path (ODU1-CTP) OCR10-T Section (OTU2-CTP) OCR10T Path (ODU2-TTP) OCR10R Section (OTU2) OTS-4400 Section In TTP Sk OTS-4040 Section (OTU3-TTP) OTS-4040 Path (ODU3-TTP) OTS-4011 Section (OTU3-TTP) OTS-4011 Path (ODU3-TTP) OTS-4011 Trib - Path (ODU2-TTP) OLI Multiplex Section Rx from Line (OMS-CTP Sk) I04T2G5 and I01T10G ODU1 Layer I04T2G5 and I01T10G ODU2 Layer I04T2G5 and I01T10G OTU1 Layer I04T2G5 and I01T10G OTU2 Layer

BDI signals are maintenance signals placed on the line. BDI is a signal sent in the opposite direction to the direction that is experiencing a fiber cut or other problem. BDI allows a fault to be isolated to a particular equipment or Section.

Troubleshooting instructions 1

What object is raising the BDI alarm? –

–

2

Transponder cards: since BDI is a maintenance signal that indicates downstream alarms, check downstream cards for LOS, LOF, TIM, or other alarms. Clearing any such alarms will also clear the BDI. OSCT card: refer to the example in Figure 31. When an OSCT card raises a BDI alarm, the problem is that the next downstream OSCT card has detected LOS, LOF, or EXC. Therefore, troubleshoot the LOS (OLI, OM20, and OSCT cards), LOF (OSCT cards), or EXC alarm to clear the BDI.

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

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

185

Troubleshooting Instructions

Figure 31

186

Troubleshooting Manual (TSMN)

BDI alarm diagram

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

Troubleshooting Manual (TSMN)

3.2.2

Troubleshooting Instructions

DMISM

Alarm name

OSC Direction Mismatch (DMISM)

Default severity

Critical

Alarm object

OSCT card.

General information and causes

The DMISM alarm is raised if the indicated OSCT card detects that it is not communicating with the expected partner OSCT card. This is nearly always caused by a cabling mistake.

Troubleshooting instructions

!

1

Check all fiber cabling between the OSCT card raising the alarm and the associated OLI cards. Ensure that all cables are connected to the correct ports as specified in the Interconnection and Mechanical Assembly (ICMA) document.

2

If the DMISM alarm persists, Warm Start the OSCT card raising the alarm.

3

If the DMISM alarm persists, Cold Start the OSCT card raising the alarm.

4

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

Caution! This special note pertains only to hiT 7500 Basic link segments, and applies only if one link direction was in "running" state, and the opposite direction was in "prestart" state before the cabling mistake occurred (and therefore the running link was partly shutdown). If both directions had the same link state (prestart or running), this Special Note does not apply. Only if the above conditions apply, perform the following after correcting the cabling mistake and clearing the DMISM alarm: perform a Forced Prestart and Link Startup procedure as instructed in the Optical Link Commissioning - Basic manual (OLC-B manual). This will allow the OLIs to recalculate and reset all parameters. If this is not done, traffic will remain shut down on one of the link segments

3.2.3

EOCI

Alarm name

External Open Connection Indication (EOCI)

Default severity

Minor

Alarm object

The EOCI alarm can be raised by: • • • •

General information and causes

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

OCR10 cards (all types except V3) TEX cards (all types except V3) I04T2G5 cards I01T10G cards

EOCI (External Open Connection Indication) is a special maintenance signal which indicates a fault on the SONET/SDH (client) layer (i.e., no signal at the Client input).

187

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions 1

EOCI indicates an open connection at the signal source end. Troubleshoot the Client In LOS alarm raised at the head end (see example in Figure 32).

2

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

Figure 32

188

Reference network for EOCI alarm

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

Troubleshooting Manual (TSMN)

3.2.4

Troubleshooting Instructions

ETHNLNF

Alarm name

Ethernet Link Fault (ETHNLNF)

Default severity

Major

Alarm object

OTS-40xx cards.

General information and causes

Local fault ordered sets have been detected by the tributary port reconciliation layer.

Troubleshooting instructions

3.2.5

1

Follow the procedure for LOF alarm. Go to chapter 3.2.15.2 “Case B: Client to Line LOF”.

2

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

EXC

Alarm name

Bit Error Rate Excessive (EXC)

Default severity

Major

Alarm object

OSCT card.

General information and causes

The OSCT card will raise the EXC alarm if the Bit Error rate (BER) of the incoming Optical Supervisory Channel is 1 x 10E-3 or worse.

Troubleshooting instructions 1

There may be a problem with the upstream OSCT card. Check if the upstream OSCT card is showing an alarm (for example, a CP alarm). Troubleshoot that alarm first, which may require replacement of the upstream OSCT card. Also, verify that the output power from the upstream OSCT card is within the required range (0 dBm to -3 dBm.

2

If the alarm persists, there may be a problem with the fiber at the input to the OSCT card raising the alarm. Verify that the input fiber(s) for the OSCT card raising the alarm are properly installed. If the cable is missing, bent/pinched, or improperly connected, correct the problem. The EXC alarm should clear when the correct connection is established.

3

If the alarm persists, disconnect the input fiber(s) of the OSCT card raising the alarm. Clean all optical connectors. Measure the input power being delivered to the end of this cable. Requirement: - 15 dBm to -50 dBm. Reconnect the fiber. If the EXC alarm persists after cleaning, replace the fiber cable with a cleaned, inspected spare.

4

If the alarm persists, Warm Start the affected OSCT card. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OSCT card. If the alarm persists after recovery time (approx 3 minutes), the OSCT card is defective. Replace the OSCT card with a spare.

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

189

Troubleshooting Instructions

5

3.2.6

Troubleshooting Manual (TSMN)

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

EXM

Alarm name

Extension Header Mismatch GFP (EXM)

Default severity

Minor

Alarm object

I04T2G5 and I01T10G ODU1 Layer.

General information and causes

The EXM alarm is raised due to a mismatch between the received and expected values for the Generic Framing Procedure (GFP) payload Extension Header Identifier (EXI) field.

Troubleshooting instructions

3.2.7

1

Troubleshoot the EXM alarm with the same instructions for the LFD alarm.

2

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

FMISM

Alarm name

Frequency Mismatch (FMISM)

Default severity

Major

Alarm object

–

– – – General information and causes

Line Out interface of TEX cards (V3, LH, LH2, Regio2, V5 types), OCR10 cards (V3, LH, LH2, Regio2, V5 types), I04T2G5 cards, and I01T10G cards. ng8T10gGpiTTPBid interface for I08T10G card in Sonet/SDH client mode. ngETY3TTPBid interface for I04T2G5 and I08T10G cards in LAN client mode. ng4T2g5GpiTTPBid interface for I04T2G5 card in Sonet/SDH client mode.

The FMISM alarm is raised if: • •

a card has been installed in the shelf, but its transmit frequency has not yet been specified by the user. the user-configured transmit frequency of the indicated card is incompatible with the frequency range of the card type.

Troubleshooting instructions 1

190

Open the “Output Frequency - Config” window for the affected card. Select the desired transmit frequency from the list on the window and click the Apply button.

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

The card's transmit laser should now switch to "on" and should stabilize at the specified frequency in 50 msec or less.

3.2.8

2

Verify that the laser status symbol on the Card Replica shows "laser on". Open the “Line Interface Out - Config” window for this card and verify the transmit frequency is listed correctly. Also verify that the Current Laser State field shows "on".

3

If the alarm persists, contact your next higher level of technical support before proceeding. Warm Start the card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the card. If the alarm persists after recovery time (approx 3 minutes), the card is defective. Replace the card with a spare.

GCCP

Alarm name

GCC Connection Problem (GCCP)

Default severity

Minor

Alarm object

OCR10 cards (all types) and TEX cards (all types).

General information and causes

This alarm will be raised if the GCC Communications feature is enabled, but the transponder card is not compatible with its MCU card type.

Troubleshooting instructions 1

Verify that this network element's MCU card type is correct for the type of transponder card raising the GCCP alarm. Transponder cards must be used with MCU types as follows: – –

2

Is the correct type of MCU installed? – –

3

3.2.9

V3 transponder cards: use only with MCU-C. LH and V5 transponder cards: use only with MCU-G. No: remove the incorrect MCU and replace it with the correct type. This will clear the GCCP alarm. Yes: Warm Start the MCU card. This should clear the GCCP alarm.

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

HIPWRECD

Alarm name

High Power Receive Detected (HIPWRECD)

Default severity

Major

Alarm object

OTS-4xxx cards (Line interface).

General information and causes

The alarm is raised to indicate that the Line receiver detected excessive optical input power.

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

191

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions 1

Open the “Line Traffic Config” window of the card raising the alarm. Check the receiver optical input power: –

– 2

3.2.10

If the power exceeds the limit, then identify the ODA card and port connected to the card raising the alarm. The output power from that ODA is too high. Follow the troubleshooting procedures for the PHF (Tx) alarm to resolve the improper power output from the ODA card. If the power is within the limit, replace the card raising the alarm with a spare.

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

HIPWRECF

Alarm name

High Power Receive Failure (HIPWRECF)

Default severity

Major

Alarm object

OTS-4xxx cards (Line interface).

General information and causes

The alarm is raised to indicate that the Line receiver is shut down. This can be caused by: • • •

the front-end pump current exceeds the allowable limit. the front-end pump output exceeds the allowable limit. the optical detector input exceeds the allowable limit.

Troubleshooting instructions 1

Open the “Line Traffic Config” window of the card raising the alarm. Check the receiver optical input power: –

– 2

3.2.11

If the power exceeds the limit, then identify the ODA card and port connected to the card raising the alarm. The output power from that ODA is too high. Follow the troubleshooting procedures for the PHF (Tx) alarm to resolve the improper power output from the ODA card. If the power is within the limit, replace the card raising the alarm with a spare.

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

LCK

Alarm name

Locked Defect (LCK)

Default severity

Minor

Alarm object

The LCK alarm can be raised by: • • • •

192

OCR10 cards (all types except V3) TEX cards (all types except V3) I04T2G5 cards I01T10G cards

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

General information and causes

LCK is a special ODUk maintenance signal specified in ITU G.709. LCK is typically invoked to lock the signal from user access while, for example, performing set-up tests. The ODUk, ODUk-TCM and OPUk overhead bytes and the whole payload are overwritten with the LCK pattern (binary 01010101). The LCK signal is therefore always trafficaffecting. Note: It is not allowed to simultaneously enable the Client to Line LCK signal in the Client Path ODU2 layer and the Line Path ODU2 LCK Tx.

Troubleshooting instructions 1

There is no defect that inserts the LCK signal. Insertion of LCK is generated via user command. For TEX and OCR10-T/R cards, there are ODU Lock State Rx and Tx switches at all OTUk interfaces, i.e., at the line side and at the client side, when the client mode is set to OTUk. To remove the LCK signal, the parameter must be set to unlocked on the respective “Traffic Configuration” window.

2

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

3

For examples, refer to Figure 33. Example 1: If ODU Lock State Tx is enabled in TEX/OCR 1, then a ODUk-LCK will be sent to the line and TEX/OCR 2 will detect it and raise the LCK alarm. Normally, an AIS signal will be inserted in the direction to [3]. Exceptions: OCR10-T in OTU client mode without TCMs enabled. Also, downstream OCR10-R cards (which do not evaluate the ODU2 layers) transparently pass the LCK signal to the next downstream card. Once the LCK signal reaches a downstream transponder card, the LCK alarm will be raised in the highest ODU2 layer. If TCM (Tandem Connection Monitoring) is enabled, the LCK alarm is raised in the highest TCM layer, and all lower layers (lower TCM, ODU2, and Line-to-Client layers) will raise SSF. If no TCM layer is enabled, the LCK alarm is raised in the ODU2 layer. Hierarchy levels: – – – –

2. OTU2 3. ODU2-TCM Layer X (optional) 4. ODU2-TCM Layer Y (optional) 5. ODU2

Example 2: If the ODU Lock State Rx is enabled in [TEX/OCR 2], then this card reacts exactly in the same way as if receiving an ODUk-LCK signal (although the received signal may be 100% OK). TEX/OCR2 will show the same alarms and consequent actions as Example 1.

Figure 33

3.2.12

LCK alarm diagram

LFD

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

193

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Alarm name

Loss of Frame Delineation GFP (LFD)

Default severity

Minor

Alarm object

I04T2G5 and I01T10G ODU1 Layer.

General information and causes

The Generic Framing Procedure (GFP) frame alignment is not detected by the card raising the LFD alarm.

Troubleshooting instructions

3.2.13

194

1

Troubleshoot and clear any other raised alarms first (especially any LOS or LOF alarms).

2

If the LFD alarm persists, the problem is with the upstream transponder. Verify that it is configured for GbE traffic. Correct as necessary.

3

If the alarm persists, Warm Start the card raising the alarm.

4

If the alarm persists, Cold Start the card raising the alarm.

5

If the alarm persists, replace the card raising the alarm.

6

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

LOC

Alarm name

Loss of Carrier (LOC)

Default severity

Minor

Alarm object

OPAPC cards (OCh Monitor Point Line Rx or Tx).

General information and causes

The OPA card will raise the LOC alarm upon detection of the first occurrence of loss of an "expected" channel (a channel for which the "Supervision" box is checked on the OCh Monitor Points Measurement window). All expected channels must be present for the LOC alarm to clear.

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

Troubleshooting Manual (TSMN)

Most likely cause

Troubleshooting Instructions

OADM100N: fiber break between: • • • •

OMxx and OMDIFC. OMDIFC and WBAN / CDAN. CDN and WBAN (troubleshoot the resulting APRM alarm first). CDAN and WBN.

OADM100U: fiber break between: • • • • • •

OMxx and OMDFIC / OMDFC. OMDFC and OMDFIC. OMDFIC and Add-OLI. Add-OLI and WBAU. CDU and WBAU. OLI(M)TPNC and CDU.

OTTU / OTTC: fiber break between: • •

!

OMxx and OMDIFC / OMDFIC / OMDFC / OMD2IC. OMDFC / OMD2IC and OMDFIC.

Caution! Note that an NLDC alarm suppresses an LOC alarm. However, the raising of an NLDC alarm will sometimes be delayed up to 3 minutes after an LOC alarm is raised. Therefore, if an LOC alarm is raised, wait 3 minutes. If an NLDC alarm is subsequently raised, thus masking the LOC alarm, troubleshoot the NLDC1 or NLDC2 alarm.

Troubleshooting instructions 1

Equipment alarms (TF, CP, etc) or an LOS alarm on OLI, CDU, or WBAU cards can cause the LOC alarm to be raised. Fiber breaks that raise an APRM, LOSADD, or CTRLCABLP alarm can also cause an LOC alarm. Troubleshoot and clear any such alarms first.

2

For OADM100U or OADM100N network elements, is the LOC alarm being raised by both OPAPC cards in the same transmission direction? ("Both" refers to the OPAPC connected to the incoming pre-amplifier and the OPAPC connected to the outgoing booster amplifier in the same transmission direction. The LOC alarm will be raised by two objects in this case - OPA Rx Sink and OPA Tx Source). If yes, then it is highly likely that the root cause of the problem is NOT in this network element. Therefore, look for the OADM network element where only the OPA Tx Source is reporting the LOC alarm. The root cause of the LOC alarm is in that NE.

3

Open the “OCh Monitor Points Measurement” window for the NE identified as the root cause in Step 2. To do so, right-click on the Card Replica of the OPAPC card raising the LOC alarm and select OCh Monitor Points > Measurement. Check the column named Channel Failure State. This column will identify the channel that is lost.

4

Open the “Cross Connection - Config” window for the NE identified as the root cause in Step 2. To do so, right-click on the Functional View's Network Element Bar and select Configuration > Cross Connections. Step 3 identified the channel that is lost. Find this channel on the “Cross-Connection - Config” window. Is the lost channel an Add channel or an Express channel at this NE?

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

195

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

– – 5

3.2.14

Lost channel is an Add channel: check for a fiber break (or dirty connections) between the OMDxx and WBAU (or WBAN as applicable). Lost channel is an Express channel: check for a fiber break (or dirty connections) between CDU and WBAU (or CDN and WBAN as applicable).

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

LOF (OSCT cards)

Alarm name

Loss of Frame (LOF)

Default severity

Major

Alarm object

OSCT cards (OSC-TTP Termination Side x).

General information and causes

The LOF alarm is raised if the OSCT card detects loss of framing on the incoming Optical Supervisory Channel.

Troubleshooting instructions 1

The output power from the upstream OSCT card may be too low. Check if the upstream OSCT card is showing an alarm (for example, a CP alarm). Troubleshoot that alarm first, which may require replacement of the upstream OSCT card. Also, verify that the output power from the upstream OSCT card is within the required range (0 dBm to -3 dBm).

2

If the LOF alarm persists, there may be a loose connection at the input of the OSCT card raising the alarm. Verify that the input fiber(s) to this OSCT card are properly installed. If a cable is missing, bent/pinched, or improperly connected, correct the problem. The LOF alarm should clear when the correct connection is established. Note the following: – –

3.2.15

OSCTUT: OSCARx connects to OSC1 port on the OLI. OSCTUI: OSCTARx connects to OSC1 port on one OLI and OSCTBRx connects to OSC1 port on the other OLI.

3

If the alarm persists, the fiber may be connected properly at the input to the OSCT card raising the alarm, but the signal is degraded due to dirty connectors or bad fiber. Disconnect the input fiber(s) of the OSCT card raising the alarm. Clean all optical connectors. Measure the input power being delivered to the end of this cable(s). Requirement: -15 dBm to -50 dBm. Reconnect the fiber. If the LOF alarm persists after cleaning, replace the fiber cable with a cleaned, inspected spare.

4

If the alarm persists, Warm Start the OSCT card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OSCT card. If the alarm persists after recovery time (approx 3 minutes), the OSCT card is defective. Replace the OSCT card with a spare.

5

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

LOF (OCU cards)

Alarm name

196

Loss of Frame (LOF)

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Default severity

Major

Alarm object

The LOF alarm can be raised on: • • • • • • • • • • • • • • • • • • • •

General information and causes

TEX Client to Line - Client Layer. TEX Line to Client - Client Layer. TEX OTU Connection Termination Point (CTP). OCR10-T Client to Line - Client Layer. OCR10-T Line to Client - Client Layer. OCR10-T OTU Connection Termination Point (CTP). OCR10-R OTU Connection Termination Point (CTP). OTS-4011 Trib# Client to Line - Client Layer. OTS-4011 Trib# Path CTP. OTS-4011 Section (OTU3-CTP). OTS-4040 Client to Line - Client Layer. OTS-4040 Line to Client - Client Layer. OTS-4040 Section OTU3 CTP. OTS-4400 Section IN (OTU3-CTP Sk). I04T2G5 Client to Line interface. I04T2G5 Line to Client interface. I04T2G5 OTU Connection Termination Point (CTP). I01T10G Client to Line interface. I01T10G Line to Client interface. I01T10G OTU Connection Termination Point (CTP).

An LOF alarm is raised if a Loss of Frame condition is detected in the incoming signal. Typical causes of an LOF alarm are as follows: •

• • •

low signal-to-noise-ratio (low input signal optical power; high noise in the line, or damaged/dirty optical components). severely distorted signal (input signal with high impairments such as dispersion, or non-linear effects). Decision Circuit Optimization (DCO) algorithm outside the operating window. Wrong signal format (mapping of an input signal that is not accepted by Nokia Siemens transponders cards.

Note that an LOF condition is frequently accompanied by a high bit error rate. Troubleshooting instructions 1

LOF alarm troubleshooting is divided into three cases as listed below. Use the case that matches the interface raising the LOF alarm. – – –

2

Case A: OTU Connection Termination Point LOF: go to chapter 3.2.15.1. Case B: Client to Line LOF: go to chapter 3.2.15.2. Case C: Line to Client LOF: go to chapter 3.2.15.3.

If the LOF alarm persists after performing the appropriate procedure below, contact your next higher level of technical support.

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

197

Troubleshooting Instructions

3.2.15.1

Troubleshooting Manual (TSMN)

Case A: OTU Connection Termination Point LOF If an LOF alarm is raised by an OTU Connection Termination Point, follow the instructions below. Troubleshooting instructions 1

If an OTU LOF alarm occurs, system self-recovery to proper signal framing is often achieved very quickly. If self-recovery occurs, no further action is necessary.

2

If the LOF alarm persists, identify the card that is nearest upstream to the card raising the LOF alarm (see Figure 34 for examples).

Figure 34 3

Contact your next level of technical support before proceeding since the following actions are traffic-affecting. Once the nearest upstream card is identified, Warm Start that card. If the OTU LOF alarm on the downstream card persists after recovery time (approx 3 minutes), Cold Start the upstream card and wait for the card to fully recover (approx 5 to 10 minutes, depending on card type).

4

If the OTU LOF alarm on the downstream card persists, Warm Start that card. If the alarm persists after recovery time (approx 3 minutes), Cold Start that card and wait for the card to fully recover (approx 5 to 10 minutes, depending on card type.

5

If the LOF alarm persists, set the Manual Decision Threshold of the card raising the alarm back to its default value. To do so, perform the following steps: – – –

6

198

LOF diagram for Case A

From Element Manager, press Ctrl-Alt-P to display the Power User log-in. Enter the correct password to log-in as a Power User. Right-click on the Card Replica of the card raising the LOF alarm and select Traffic > Line Interface In > Configuration. On the resulting “Line - Traffic Config” window, change the value of Manual Decision Threshold as follows: for V2 and V3 cards, set to +122. For LH cards, set to +35. Click Apply, then Close. Changing the Manual Decision Threshold should clear the LOF alarm within approximately 15 seconds. If the alarm does not clear, proceed to Step 6.

If the OTU LOF alarm persists, check the card's Line input power. To do so, rightclick on the Card Replica of the card raising the LOF alarm and select Traffic > Line

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Interface In > Configuration. On the resulting window, read the displayed Optical Input Power. Is the input power too low and the OPR alarm raised? – –

3.2.15.2

Yes: go to the troubleshooting instructions for the OPR alarm. No: continue to step 7.

7

If the OTU LOF alarm persists, replace the card raising the alarm with a spare.

8

If the OTU LOF alarm persists, replace the nearest upstream card (as identified in step 2) with a spare.

9

If no other cause can be found, it is possible that there is a silent Channel Count Mismatch failure which, in turn, can adversely affect preemphasis results and Link Control operation, and thus cause the LOF alarm to be raised. Execute the procedures in Chapter 6 “Link Control Troubleshooting” to clear the problem.

Case B: Client to Line LOF If a Client to Line LOF alarm is raised, follow the instructions below. A Client to Line LOF alarm is raised when there is a loss of frame condition detected at a transponder's Client IN port. Troubleshooting instructions 1

Refer to Figure 35. If a Client to Line LOF alarm occurs, system self-recovery to proper signal framing is often achieved very quickly. If self-recovery occurs, no further action is necessary.

2

It is possible that the client (non-Nokia Siemens) equipment is faulty and is not supplying a properly-framed SONET/SDH signal. Troubleshoot the client equipment for problems according to the equipment manufacturer's instructions.

3

Contact your next level of technical support before proceeding since the following actions are traffic-affecting. Warm Start the card raising the Client to Line LOF alarm. If the alarm persists after recovery time (approx 3 minutes), execute a Cold Start of the card and wait for the card to fully recover (approx 5 to 10 minutes).

4

If the Client to Line LOF alarm persists, dispatch personnel to the site of the card raising the alarm. Disconnect the input fiber from the card raising the alarm. Clean all optical connectors and reconnect the fiber.

5

If the alarm persists, replace the card raising the alarm with a spare.

Figure 35

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

LOF diagram for Case B

199

Troubleshooting Instructions

3.2.15.3

Troubleshooting Manual (TSMN)

Case C: Line to Client LOF If a Line to Client LOF alarm is raised, follow the instructions below. Troubleshooting instructions 1

If a Line to Client LOF alarm occurs, system self-recovery to proper signal framing is often achieved very quickly. If self-recovery occurs, no further action is necessary.

2

See Figure 36. If Transponder Z has raised a Line to Client LOF alarm, it may be caused by upstream Transponder A transmitting a G-AIS signal. So, first determine if there is a problem upstream at Transponder A. Check for an LOS or LOF alarm at the Client IN interface of Transponder A. If either of these alarms exist, perform the relevant troubleshooting procedures on Transponder A first.

Figure 36

3.2.16

LOF diagram for Case C

3

Contact your next level of technical support before proceeding since the following actions are traffic-affecting. Warm Start the card raising the Line to Client LOF alarm. If the alarm persists after recovery time (approx 3 minutes), execute a Cold Start of the card and wait for the card to fully recover (approx 5 to 10 minutes).

4

If the Client to Line LOF alarm persists, dispatch personnel to the site of the card raising the alarm. Replace the card with a spare.

5

If the alarm persists, replace the upstream (Transponder A) card with a spare.

6

If the alarm persists, execute the procedures in Chapter 6 “Link Control Troubleshooting” to clear the problem.

LOFLOM

Alarm name

Loss of Frame and Multiframe (LOFLOM)

Default severity

Major

Alarm object

The LOFLOM alarm can be raised by: • •

200

TEX card Path (ODU1) Connection Termination Point. I08T10G card Odu1CTPBid Connection Termination Point.

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

Troubleshooting Manual (TSMN)

General information and causes

Troubleshooting Instructions

An LOFLOM alarm is raised if a Loss of Frame and Loss of Multiframe condition is detected in the incoming signal, i.e., Out of Frame (OOF) and Out of Multiframe (OOM) defects both exist. An OOF condition is declared after five consecutive bad frames. An OOM condition is declared if the received MultiFrame Alignment Signal (MFAS) does not match the expected multiframe number in 5 consecutive frames. To clear the alarm, the framing must be In-Frame continuously for 3 ms. This ensures that even intermittent OOF/OOM states will cause an LOFLOM alarm. Typical causes of an LOFLOM alarm are as follows: •

• • •

low signal-to-noise-ratio (low input signal optical power; high noise in the line, or damaged/dirty optical components). severely distorted signal (input signal with high impairments such as dispersion, or non linear effects). Decision Circuit Optimization (DCO) algorithm outside the operating window. Wrong signal format (mapping of an input signal that is not accepted by Nokia Siemens transponder cards.

Note that an LOFLOM condition is frequently accompanied by a high bit error rate. Troubleshooting instructions 1

If an LOFLOM alarm occurs, system self-recovery to proper signal framing is often achieved very quickly. If self-recovery occurs, no further action is necessary.

2

If the LOFLOM alarm persists, contact your next level of technical support before proceeding since the following action is traffic-affecting. Disconnect the fiber at the In connector of the affected transponder card. Clean all optical connectors and reconnect. If the LOFLOM alarm persists, replace the fiber cable with a cleaned, inspected spare.

3

If the alarm persists, Warm Start the card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the card. If the alarm persists after recovery time (approx 3 minutes), the card is defective. Replace the affected card with a spare.

4

If the alarm persists, it is possible that there is a silent Channel Count Mismatch failure which, in turn, can adversely affect preemphasis results and Link Control operation, and thus cause the LOM alarm to be raised. Execute the procedures in Chapter 6 “Link Control Troubleshooting”.

5

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

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

201

Troubleshooting Instructions

3.2.17

Troubleshooting Manual (TSMN)

LOM

Alarm name

Loss of Multiframe (LOM)

Default severity

Major

Alarm object

The LOM alarm can be raised by: • • • • •

General information and causes

TEX Section (OTU) Connection Termination Point. OCR10-T Section (OTU) Connection Termination Point. OCR10-R Section (OTU) Connection Termination Point. I04T2G5 Section (OTU) Connection Termination Point. I01T10G Section (OTU) Connection Termination Point.

The Multiframe Alignment byte in the G-709 overhead is read from every received frame (during a given cycle). An Out-ofMultiframe (OOM) condition is declared when the received MultiFrame Alignment Signal (MFAS) doesn't match the expected multiframe number in 5 consecutive frames. Multiframe alignment is recovered when in two consecutive frames occur with an error-free MFAS sequence.

Troubleshooting instructions

3.2.18

202

1

If an LOM alarm occurs, system self-recovery to proper signal framing is often achieved very quickly. If self-recovery occurs, no further action is necessary.

2

If the LOM alarm persists, contact your next level of technical support before proceeding since the following action is traffic-affecting. Disconnect the fiber at the In connector of the affected transponder card. Clean all optical connectors and reconnect. If the LOM alarm persists, replace the fiber cable with a cleaned, inspected spare.

3

If the alarm persists, Warm Start the card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the card. If the alarm persists after recovery time (approx 3 minutes), the card is defective. Replace the affected card with a spare.

4

If the alarm persists, it is possible that there is a silent Channel Count Mismatch failure which, in turn, can adversely affect preemphasis results and Link Control operation, and thus cause the LOM alarm to be raised. Execute the procedures in Chapter 6 “Link Control Troubleshooting”.

5

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

LOS (OLI, OM20, and OSCT cards)

Alarm name

Loss of Signal (LOS)

Default severity

Major

Alarm object

The LOS alarm can be raised by OLI cards (all types), OM20 cards (all types), and OSCT cards.

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

General information and causes

A card will raise the LOS alarm if the power of the incoming optical signal falls below a particular threshold.

Troubleshooting instructions 1

Use the appropriate instructions below for the type of card raising the LOS alarm: –

–

– 2

OLI card: LOS will be raised by an OLI card (together with the OMS LOS alarm if the optical input power falls below -28 dBm +/- 2 dB. Use the same Troubleshooting instructions as for the OPLOS alarm. OSCT card: LOS will be raised by an OSCT card if the optical input power is less than -50 dBm. Use the same Troubleshooting instructions as for the LOF alarm. OM20 card: go to step 2.

LOS will be raised by an OM20 card if the optical input power of any channel is less than - 16 dBm. Check if the upstream signal source (transponder card) is raising an alarm (Client In LOS, Transmit Fail, etc) and troubleshoot that alarm first. Ensure that the transponder Laser State is "ready for use" and that ALS is disabled.

g Behavior note for OM20 cards. Under some circumstances in OADM network elements, the LOS alarm is incorrectly shown raised by the corresponding AddOLI card, instead of the OM20 card (Add-OLI card replica flashes red, erroneously indicating an alarm on that card). In this case, check the NE-Alarm List, which will list the actual location of the OM20 card raising the LOS alarm.

3.2.19

3

If the alarm persists, open the “Traffic-Info” window for the associated upstream OM20 card. Make sure Port Mode is enabled. Verify that the input power for the channel is in the proper range.

4

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

LOS (OCU cards)

Alarm name

Loss of Signal (LOS)

Default severity

Major

Alarm object

The LOS alarm can be raised by: • • • • • • • • • • • • • •

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

TEX Trib# Client In interface. TEX Line In interface. OCR10-T Client In interface. OCR10-T Line In interface. OCR10-R Line In interface. OTS-4011 Trib# Client In interface. OTS-4011 Trib# Line to Client - Client Layer. OTS-4011 Line In interface. OTS-4040 Client In interface. OTS-4040 Line In interface. OTS-4400 LineIn interface. I04T2G5 and I01T10G OCh. I04T2G5 and I01T10G Ethernet Physical. I04T2G5 and I01T10G OS Sdh Sonet.

203

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

General information and causes

An LOS alarm will be raised if the incoming signal power at the indicated interface falls below the LOS threshold. These thresholds are as follows: • •

All Line In LOS thresholds are user-specified via the craft terminal. The range is -14 dBm to -23 dBm. All Client In LOS thresholds are a fixed value as follows: TEX Client In LOS threshold = -18 dBm and OCR10-T Client In LOS threshold = -16 dBm.

Also, if a non-Nokia Siemens compliant SFP (Small FormFactor, Pluggable) module with an optical signal applied at its input is inserted into a TEX Client In port, this TEX card will raise a Client In LOS alarm.

g Behavior Note: The Line In LOS alarm is based only on optical power level. The threshold is specified by the user. If the input power drops below the specified threshold, the Line In LOS alarm will be raised. Then, for TEX and OCR10-T cards, one of the following will occur (also controlled by user-specified selection: MS-AIS will be inserted into the client signal, or G-AIS will be inserted into the client signal, or the client laser will be completely shut down. Troubleshooting instructions 1

What interface is raising the LOS alarm? – –

2

3.2.19.1

Client In interface: go to chapter 3.2.19.1 for troubleshooting instructions. Line In interface: go to chapter 3.2.19.2 for troubleshooting instructions.

If the LOS alarm persists after performing the appropriate procedure below, contact your next higher level of technical support.

Client In LOS If an LOS alarm is raised by a Client In interface, follow the instructions below. Troubleshooting instructions 1

Troubleshoot any upstream alarms first. If the Client In LOS alarms persists, proceed to step 2.

2

There may be missing or loose connections at the Client input to the affected card. Verify that the Client input fiber cable is properly installed. If the cable was missing, bent/pinched, or improperly connected, correct the problem. The LOS alarm should clear when the correct connection is established.

3

Contact your next level of technical support before proceeding since the following actions are traffic-affecting. Disconnect the fiber at the Client In port of the affected card. Clean all optical connectors. Measure the optical power of the signal being carried by this fiber. Is the measured power higher or lower than the fixed Client In LOS threshold (-18 dBm for TEX cards and -16 dBm for OCR10-T cards)? –

204

Lower than the threshold: assuming upstream conditions are OK, the fiber connected to the transponder card is likely bad. Replace the fiber with a cleaned, inspected spare. Measure the power before connecting the fiber to the Client In port. If the power is higher than the LOS threshold, connect the fiber to the Client In port. The LOS alarm should clear within 15 seconds.

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

Troubleshooting Manual (TSMN)

–

3.2.19.2

Troubleshooting Instructions

Higher than the threshold: re-connect the fiber to the card raising the Client In LOS alarm. The LOS alarm should clear within 15 seconds. If it does not clear, there is likely something wrong with the transponder card itself. Go to step 4.

4

For TEX cards, a Client In LOS alarm will be raised if non-Nokia Siemens compliant SFP (Small Form-Factor, Pluggable) modules are used. If this is the case, replace the SFP with a Nokia Siemens-approved type and the Client In LOS alarm should clear. Otherwise, go to Step 5.

5

Open the “Traffic Configuration” window for the affected card and check the Rx Input Power level at the Client side. If the listed power level is too low, disconnect the fiber, re-clean all connectors and re-connect. If the listed power is within the acceptable range and the card is still reporting a Client In LOS alarm, Warm Start the card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the card. If the alarm persists after recovery time (approx 3 minutes), the card is defective. Replace the card with a spare.

Line In LOS If an LOS alarm is raised by a Line In interface, follow the instructions below. Troubleshooting instructions 1

Are there any alarms from the associated ODA20 card or other upstream equipment? – –

2

Via Element Manager GUI, right-click on the ODA20 card that is connected to the failed channel and select Traffic > Configuration. The “Traffic Configuration” window for this card will open. For the failed channel, is the "Reference Value" approximately equal to "Power level minus VOA current value"? Note: Power Level minus VOA Current Value should be approximately - 8.8 dBm +/- 1 dB –

– 3

Yes: troubleshoot and clear the upstream alarms first. No: go to step 2.

No: the ODA20 card may be defective. Refer to troubleshooting instructions for the PDF (Tx) alarm and the PLF (Tx) alarm. Also see Chapter 6 “Link Control Troubleshooting”. Yes: go to step 3.

Contact your next level of technical support before proceeding since the following action is traffic-affecting. Disconnect the fiber from the Line side of the card raising the Line IN LOS alarm. Measure the power received from the ODA 20 card with an optical power meter. Is the measured power consistent with the ODA20's output power as displayed on the GUI (-8.8 dBm +/- 1 dB)? –

–

No: clean the fiber end and measure again. If the power level is still too low, clean the fiber end again and re-connect the fiber to the Line In port. Then, go to Step 4. Yes: re-connect the fiber to the card raising the Line In LOS alarm. Via Element Manager GUIs, check the Rx Input Power level at the Line side of the affected Transponder card. If the power level is within the accepted range, verify that the LOS alarm threshold has been set to the correct value (Line Traffic-Config window). Correct if necessary. If the LOS alarm does not clear, go directly to Step 6.

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

205

Troubleshooting Instructions

4

Troubleshooting Manual (TSMN)

Disconnect the fiber from the ODA20, and measure the ODA20 output power using a clean jumper. Is the measured power consistent with the ODA20's output displayed on the GUI (-8.8 dBm +/- 1 dB)?. – –

5

Via Element Manager GUI, check the Rx Input Power level at the Line side of the affected Transponder card. Is the power level within the accepted range?. – –

6

3.2.20

No: Clean the fiber connector and measure again. If the power level is still too low, the ODA20 output port is likely bad. Replace the ODA20 card with a spare. Yes: Clean the original fiber connector, then re-connect back to the ODA20. Go to Step 5.

No: The fiber is bad. Replace the fiber between the ODA20 and the Transponder card. Yes: The LOS alarm should clear within 15 seconds. If it does not clear, continue to Step 6.

The card raising the alarm is faulty. Replace it with a spare.

LTC

Alarm name

Loss of TCM (LTC)

Default severity

Minor

Alarm object

The LTC alarm can be raised by: • • • •

General information and causes

OCR10 cards (all types except V3) TEX cards (all types except V3) I04T2G5 cards I01T10G cards

LTC functions according to ITU-G798. LTC is raised if the accepted STAT information (AcSTAT) is “000”. LTC will be cleared if the accepted STAT information is not equal to “000”.

Troubleshooting instruction

206

1

The LTC alarm is raised if only the TCM sink is configured (receiving side). To clear the alarm, make sure the TCM source is configured.

2

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

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

Troubleshooting Manual (TSMN)

3.2.21

Troubleshooting Instructions

MSIM

Alarm name

Multiplex Structure Identifier Mismatch (MISM)

Default severity

Minor

Alarm object

The MSIM alarm can be raised by: •

General information and causes

TEX cards (all types except V3)

If a card detects a mismatch between the expected Multiplex Structure Identifier (MSI) and that actually received, a MSIM alarm will be generated. MSI bytes are part of the PSI (Payload Structure Identifier) message in the OPU2 overhead.

Troubleshooting instructions

3.2.22

1

This alarm typically happens when upgrading the hiT 7500 system from a version (example; 3.13.90) which did not support MSI insertion/detection to a version (example; 3.21) that does. During an upgrade, it typically occurs that a transponder at one end of a link is still running older software (before upgrade). If the transponder at the other end of the link is the first to be upgraded, there will be a period of time where the transponder card running older software is connected to a transponder card running the new software. An MSIM alarm will be raised because the 3.21 card is expecting an MSI message which is does not receive. When the transponder cards at both ends are upgraded, the MSIM alarm will self-clear.

2

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

OCI

Alarm name

Open Connection Indication (OCI)

Default severity

Minor

Alarm object

The OCI alarm can be raised by: • • • • • •

General information and causes

OCR10 cards (all types except V3) TEX cards (all types except V3) OTS-4040 cards OTS-4011 cards I04T2G5 cards I01T10G cards

Open Connection Indication (OCI) is monitored at the OCh and ODUk layers. Detection of OCI signifies that there is a Loss of Signal defect due to an output connection point not connected to an input connection point.

Troubleshooting instructions 1

This alarm can be caused by a user-initiated change of the Client Mode without first clearing all TCMs (Tandem Connection Monitoring). Before a change in client

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

207

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

mode is made on a card, all previously-configured TCM Layers (tributary and line) must first be cleared. Otherwise, an OCI alarm (on the TCM layer) may be generated. If it is suspected, that a recent change in Client Mode triggered the OCI alarm, Warm Start the card raising the alarm and the OCI alarm should clear. If the alarm was not due to a recent change in Client Mode, continue to step 2.

3.2.23

2

There is an open connection upstream. Troubleshoot all LOS alarms to clear the OCI.

3

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

OPR

Alarm name

Optical Power Receive too Low (OPR)

Default severity

Major

Alarm object

The OPR alarm can be raised by the Line In interface of: • • • • • • •

General information and causes

!

TEX cards (all types). OCR10 cards (all types). OTS-4011, OTS-4040, and OTS-4400 cards. OTS-4520 TDCM Line In interface. OTS-4540 PMDC Line In interface. I04T2G5 cards. I01T10G cards.

An OPR alarm will be raised if the incoming signal power at the indicated interface falls below the user-specified threshold. OPR is intended to be a "degraded signal" alarm threshold that is reached before the more serious LOS threshold is reached. Therefore, set the OPR threshold a few dB higher than the LOS threshold.

Caution! Note that the OPR raise and clear time is 100 seconds. So, after each troubleshooting step, wait at least 100 seconds to see if the alarm clears.

Troubleshooting instructions 1

Are there any alarms from the associated ODA20 card or other upstream equipment? – –

2

208

Yes: troubleshoot the upstream alarms first. No: go to step 2.

Via Element Manager GUI, right-click on the ODA20 card that is connected to the failed channel and select Traffic > Configuration. The “Traffic Configuration” window for this card will open. For the failed channel, is the Reference Value approximately equal to Power level minus VOA current value? Note: Power Level minus VOA current value should be approximately - 8.8 dBm +/- 1 dB.

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

Troubleshooting Manual (TSMN)

–

– 3

–

–

No: Clean the fiber connector and measure again. If the power level is still too low, the ODA20 output port is likely bad. Replace the ODA20 card with a spare. Yes: Clean the original fiber connector, then re-connect back to the ODA20. Go to Step 5.

Via Element Manager GUI, check the Rx Input Power level at the Line side of the affected Transponder card. Is the power level within the accepted range? – –

3.2.24

No: Clean the fiber end and measure again. If the power level is still too low, clean the fiber end again and re-connect the fiber to the Line In port. Then, go to Step 4. Yes: Re-connect the fiber to the card raising the OPR alarm. Via Element Manager GUIs, check the Rx Input Power level at the Line side of the affected Transponder card. If the power level is within the accepted range, verify that the OPR alarm threshold has been set to the correct value (“Line Traffic-Config” window). Correct if necessary. If the OPR alarm does not clear, go directly to Step 6.

Disconnect the fiber from the ODA20, and measure the ODA20 output power using a clean jumper. Is the measured power consistent with the ODA20's output displayed on the GUI (-8.8 dBm +/- 1 dB)? –

5

No: the ODA20 card may be defective. Refer to troubleshooting instructions for the PDF (Tx) alarm and the PLF (Tx) alarm. Also see Chapter 6 “Link Control Troubleshooting”. Yes: go to step 3.

Contact your next level of technical support before proceeding since the following action is traffic-affecting. Disconnect the fiber from the Line side of the card raising the OPR alarm. Measure the power received from the ODA 20 card with an optical power meter. Is the measured power consistent with the ODA20's output power as displayed on the GUI (-8.8 dBm +/- 1 dB)? –

4

Troubleshooting Instructions

No: The fiber is bad. Replace the fiber between the ODA20 and the Transponder card with a cleaned, inspected spare. Yes: The OPR alarm should clear within 2 minutes. If it does not clear, continue to Step 6.

6

The transponder card raising the alarm is faulty. Replace it with a spare.

7

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

OSCVIM

Alarm name

OSC Version Mismatch (OSCVIM)

Default severity

Minor

Alarm object

OSCT card.

General information and causes

When network elements are upgraded, the Application Program Software (APS) is downloaded from the NE's MCU card to peripheral cards. If the OSCT card at one NE has a different software version than the OSCT at either adjacent NE, the OSCVIM alarm will be raised.

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

209

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions

3.2.25

!

1

Ensure that all NEs are running the same APS software. This will clear the OSCVIM alarm. Refer to the SURPASS hiT 7500 Operating Manual (OMN) document for instructions how to check the APS version and download a different APS.

2

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

PDHD

Alarm name

Power Drift High Degrade (PDHD)

Default severity

Minor

Alarm object

OPA, OPAC and OPAPC cards (OCh Monitor Point Line Rx and Tx).

General information and causes

OPA cards monitor all channels for power drift in relation to an initial reference value. If a channel's power drifts above the reference value by a user-selectable amount, the PDHD alarm will be raised. The alarm threshold is set on the “OCh Monitoring Points Config” window.

Caution! Note: the PDHD alarm is intended for Nokia Siemens Networks service personnel only. Snapshots are required for this drift alarm to be raised. PowerUser log-in is required to perform the Snapshot command.

Troubleshooting instructions

210

1

To clear the snapshot values (which will clear the PDHD alarm), go to the Equipment View, right-click on the Card Replica of the OPA card raising the PDHD alarm and select OCh Monitor Points... Clear Snapshot Values. Note that a PowerUser login is required; otherwise, Clear Snapshot Values is grayed-out. This should clear the PDHD alarm.

2

If the alarm persists, Warm Start the card raising the alarm.

3

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

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

Troubleshooting Manual (TSMN)

3.2.26

!

Troubleshooting Instructions

PDLD

Alarm name

Power Drift Low Degrade (PDLD)

Default severity

Minor

Alarm object

OPA, OPAC and OPAPC cards (OCh Monitor Point Line Rx and Tx).

General information and causes

OPA cards monitor all channels for power drift in relation to an initial reference value. If a channel's power drifts below the reference value by a user-selectable amount, the PDLD alarm will be raised. The alarm threshold is set on the “OCh Monitoring Points Config” window.

Caution! Note: the PDLD alarm is intended for Nokia Siemens Networks service personnel only. Snapshots are required for this drift alarm to be raised. PowerUser log-in is required to perform the Snapshot command.

Troubleshooting instructions 1

To clear the snapshot values (which will clear the PDLD alarm), go to the Equipment View, right-click on the Card Replica of the OPA card raising the PDHD alarm and select OCh Monitor Points... Clear Snapshot Values. Note that a PowerUser login is required; otherwise, Clear Snapshot Values is grayed-out. This should clear the PDLD alarm.

2

If the alarm persists, Warm Start the card raising the alarm.

3

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

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

211

Troubleshooting Instructions

3.2.27

Troubleshooting Manual (TSMN)

PDF (Rx)

Alarm name

Power Drift Failure (PDF)

Default severity

Minor

Alarm object

OM10 and OM20 cards (Channel Rx).

General information and causes

OM10 and OM20 cards keep each incoming channel power at a constant value by automatically adjusting a channel’s VOA if its input power changes. The goal is to keep the power level within +/- 0.5 dB of the required value. The required value is calculated by the system during power equalization and cannot be changed by the user. To view the required value, open the “OMxx Traffic Configuration” window. The PDF (Rx) alarm will be raised if the VOA reaches its minimum or maximum attenuation and is therefore no longer able to adjust the incoming power value.

Troubleshooting instructions

212

1

Troubleshoot any upstream alarms first.

2

If the alarm persists, go to the “Traffic Configuration” window for the affected OMxx card. Check the input power of each port. If the input power of any channel(s) entering the OMxx card is too high or too low, verify that the output power from the corresponding transponder is set correctly. To do so, open that transponder’s “Line Interface Out Traffic Configuration” window. If transponder outputs are incorrect, change them. Then, go back to the OMxx “Traffic Configuration” window and verify that input power to OMxx has changed. This should clear the PDF (Rx) alarm.

3

If the alarm persists, Warm Start the card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the card. If the alarm persists after recovery time (approx 3 minutes), the OMxx card is defective. Replace the OMxx card with a spare.

4

If the alarm persists, execute the procedures in Chapter 6 “Link Control Troubleshooting”.

5

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

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

Troubleshooting Manual (TSMN)

3.2.28

Troubleshooting Instructions

PDF (Tx)

Alarm name

Power Drift Failure (PDF)

Default severity

Minor

Alarm object

ODA10 and ODA20 cards (Channel Tx).

General information and causes

ODA10 and ODA20 cards keep each transmit channel power at a constant value by automatically adjusting a channel’s VOA if its output power changes. The goal is to keep the power level within +/- 2.0 dB of the "reference value". The reference value can be set for each channel via the card's “Traffic Configuration window”. Range: 0 dBm to -14 dBm. Default: - 8.8 dBm. The PDF (Tx) alarm will be raised if the VOA reaches its minimum or maximum attenuation and is therefore no longer able to adjust the outgoing power value.

Troubleshooting instructions 1

Troubleshoot and clear any upstream alarms first.

2

If the alarm persists, Warm Start the card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the card. If the alarm persists after recovery time (approx 3 minutes), the OMxx card is defective. Replace the OMxx card with a spare.

3

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

g Behavior note for ODA10 and ODA20 cards. Under some circumstances in OADM network elements, the PDF alarm is incorrectly shown raised by the corresponding Drop-OLI card, instead of the ODxx card (Drop-OLI card replica flashes red, erroneously indicating an alarm on that card). In this case, check the NE-Alarm List, which will list the actual location of the ODxx card raising the PDF alarm.

3.2.29

PHF

Alarm name

Power too High Failure (PHF)

Default severity

Minor

Alarm object

The PHF alarm can be raised by the Client In interface of: • • • • •

General information and causes

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

TEX cards (all types). OCR10T cards (all types). OTS-4011 and OTS-4040 cards. I04T2G5 cards. I01T10G cards.

The PHF alarm is raised if the input power is higher than the user-specified alarm threshold.

213

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

Troubleshooting instructions 1

Open the “Client Interface Config” window for the card raising the PHF alarm. Compare the displayed Optical Input Power with the value set for Upper Threshold. Is the Optical Input Power higher than the Upper Threshold? –

–

3.2.30

!

Yes: verify that the Upper Threshold is set correctly according to your network planning rules. If the value is set correctly, the signal level coming from the client equipment is likely too high. Check the output power of the client equipment and / or use an attenuation fiber to lower the signal level into the transponder card. This should clear the alarm. However, if the alarm persists, go to Step 2. No: go to Step 2.

2

If the alarm persists, Warm Start the card raising the alarm. Wait for the card to recover.

3

If alarm persists, contact your next higher level of Technical Support since the next step will be traffic affecting. Cold Start the card raising the alarm. Wait for the card to recover (recovery time can take up to 8 minutes).

4

If the alarm persists, replace the card raising the alarm with a spare.

PHF (Rx)

Alarm name

Power too High Failure (PHF)

Default severity

Minor

Alarm object

OM10 and OM20 cards (Channel Rx).

General information and causes

The alarm is raised if the channel input power is more than 3 dB above the user-specified value for Mean Accepted Input Power.

Caution! For first-generation 40G transponder cards: when 40G transponder cards (OTS-4011, OTS-4040) are used, a fixed attenuator is required between each transponder card and the OM card. Lack of these attenuators to decrease transponder output power to the level acceptable by the OM will result in a PHF alarm. Contact your next higher level of technical support if such attenuators are missing.

Troubleshooting instructions 1

Troubleshoot and clear any upstream alarms first.

2

If the alarm persists, how many channels are reporting a PHF (Rx) alarm? –

–

214

If only one channel is reporting a PHF (Rx) alarm, the problem is likely in that channel's source transponder. Open the transponder’s “Line Interface Out Traffic Configuration” window. If transponder output is incorrect, change it to the correct value. Then, open the “Traffic Configuration” window for the OMxx card raising the alarm and verify that input power to the OMxx has changed. The PHF (Rx) alarm should clear. Go to step 3. If multiple channels are reporting a PHF (Rx) alarm, verify that the Mean Accepted Input Power is set according to the Commissioning Report. Mean

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Accepted Input Power is set on the “Optical Link Control - Config” window. To obtain this window, right-click on the OSCT Card Replica in the Equipment View and select Optical Link Control. Note: Mean Accepted Input Power cannot be changed if the link state is "running". Range is -5 to 1.0 dBm. Default is 0 dBm. If Mean Accepted Input Power was set incorrectly, set it to its proper value and the alarm should clear. If Mean Accepted Input Power was set correctly, but the alarm persists, the problem is likely in the OMxx card. Go to step 3. 3

If the alarm persists, Warm Start the card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the card. If the alarm persists after recovery time (approx 3 minutes), the OMxx card is defective. Replace the OMxx card with a spare.

4

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

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

215

Troubleshooting Instructions

3.2.31

Troubleshooting Manual (TSMN)

PHF (Tx)

Alarm name

Power too High Failure (PHF)

Default severity

Minor

Alarm object

ODA10 and ODA20 cards (Channel Tx).

General information and causes

ODA10 and ODA20 cards keep each transmit channel power at a constant value by automatically adjusting a channel’s VOA if its output power changes. The goal is to keep the power level within +/- 2.0 dB of the "reference value". The reference value can be set for each channel via the ODAxx card's “Traffic Configuration” window. Range: 0 dBm to -14 dBm. Default: - 8.8 dBm. The PHF (Tx) alarm will be raised if a channel output power is higher than the reference value by 2.5 dB or more.

Troubleshooting instructions 1

Troubleshoot and clear any upstream alarms first.

2

If the PHF (Tx) alarm persists, go to the Equipment View, right-click on the Card Replica of the ODAxx card raising the alarm and select Traffic > Configuration. For the affected channel, check the following: Does the Current Power minus VOA setting = Reference Power +/- 2.5 dB? – –

3

See Figure 37. A problem in an upstream OMxx card can cause a PHF (Tx) alarm in the downstream ODAxx card. To determine which upstream OMxx card to investigate, examine the cross-connection status for the affected channel. The Channel Number is identified as part of the original alarm message, i.e., "CH# from ODA (PHF)". To investigate this channel's cross-connection status, go to the Equipment View, right-click on the NE Bar and select Configuration > Cross-Connection. This channel's cross-connection status will allow you to identify which upstream OMxx card sources the channel.

4

Once the upstream OMxx card is identified, right-click on this card's Card Replica in the Equipment View and select Traffic > Configuration. [As an alternative, use the OPAPC Scan Spectrum window to view the full spectrum of equipped channels]. Via either GUI, take multiple measurements at least 20 seconds apart by using the Update button on these windows. Does the affected channel's output power remain close to the power for each of the other channels? –

–

216

No: go directly to step 3. Yes: Warm Start the ODAxx card raising the PHF (Tx) alarm. After recovery time (approximately 3 minutes), the PHF (Tx) alarm should clear. If the alarm persists, continue to step 3.

No: the affected channel likely has a fluctuating VOA. Warm Start the OSCTUT card at the upstream node. After recovery time (approximately 3 minutes), the PHF (Tx) alarm should clear. If it does not clear, go to step 5. Yes: go directly to step 5.

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

Troubleshooting Manual (TSMN)

5

If the alarm persists, contact your next higher level of technical support. Cold Start the ODAxx card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), the ODAxx card is defective. Replace the ODAxx card with a spare

Figure 37

3.2.32

Troubleshooting Instructions

PHF (Tx) alarm diagram

PLF

Alarm name

Power too Low Failure (PLF)

Default severity

Minor

Alarm object

The PLF alarm can be raised by the Client In interface of: • • • • •

General information and causes

TEX cards (all types). OCR10T cards (all types). OTS-4011 and OTS-4040 cards. I04T2G5 cards. I01T10G cards.

The PLF alarm is raised if the input power is lower than the user-specified alarm threshold.

Troubleshooting instructions 1

For TEX cards equipped with pluggable SFP modules, it has been observed that a PLF alarm may be raised when one type of SFP is exchanged for another. Reason:

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

217

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

SFP calibration is performed only upon startup of the TEX card. When a new SFP with different reach characteristics is installed, the TEX card does not know the new PLF alarm threshold until the calibration procedure is peformed. So, if an SFP was recently replaced, causing a PLF alarm, simply Warm Start the TEX card. After the card completes the Warm Start, the PLF alarm should clear. If the alarm persists, go to Step 2. 2

Open the “Client Interface Config” window for the card raising the PLF alarm. Compare the displayed Optical Input Power with the value set for Lower Threshold. Is the Optical Input Power lower than the Lower Threshold? –

–

3.2.33

Yes: verify that the Lower Threshold is set correctly according to your network planning rules. If the value is set correctly, the signal level coming from the client equipment is likely too low. Check the output power of the client equipment and / or clean the fiber ends and connectors. This should clear the alarm. However, if the alarm persists, go to Step 3. No: go to Step 3.

3

If the alarm persists, Warm Start the card raising the alarm. Wait for the card to recover.

4

If alarm persists, contact your next higher level of Technical Support since the next step will be traffic affecting. Cold Start the card raising the alarm. Wait for the card to recover (recovery time can take up to 8 minutes).

5

If the alarm persists, replace the card raising the alarm with a spare.

PLF (Rx)

Alarm name

Power too Low Failure (PLF)

Default severity

Minor

Alarm object

OM10 and OM20 cards (Channel Rx).

General information and causes

The alarm is raised if the channel input power drops 3 dB or more below the user-specified value for Mean Accepted Input Power.

Troubleshooting instructions 1

Troubleshoot and clear any upstream alarms first.

2

If the alarm persists, how many channels are reporting a PLF (Rx) alarm? –

–

218

If only one channel is reporting a PLF (Rx) alarm, the problem is likely in that channel's source transponder. Open the transponder’s “Line Interface Out Traffic Configuration” window. If transponder output is incorrect, change it to the correct value. Then, open the “Traffic Configuration” window for the OMxx card raising the alarm and verify that input power to the OMxx has changed. The PLF (Rx) alarm should clear. If the alarm does not clear, check and clean the fiber between transponder and OMxx. If the alarm persists, go to step 3. If multiple channels are reporting a PLF (Rx) alarm, verify that the Mean Accepted Input Power is set according to the Commissioning Report. Mean Accepted Input Power is set on the “Optical Link Control - Config” window. To obtain this window, right-click on the OSCT Card Replica in the Equipment View

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

and select Optical Link Control. Note: Mean Accepted Input Power cannot be changed if the link state is "running". Range is -5 to 1.0 dBm. Default is 0 dBm. If Mean Accepted Input Power was set incorrectly, set it to its proper value and the alarm should clear. If Mean Accepted Input Power was set correctly, but the alarm persists, the problem is likely in the OMxx card. Go to step 3.

3.2.34

3

If the alarm persists, Warm Start the card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the card. If the alarm persists after recovery time (approx 3 minutes), the OMxx card is defective. Replace the OMxx card with a spare.

4

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

PLF (Tx)

Alarm name

Power too Low Failure (PLF)

Default severity

Minor

Alarm object

ODA10 and ODA20 cards (Channel Tx).

General information and causes

ODA10 and ODA20 cards keep each transmit channel power at a constant value by automatically adjusting a channel’s VOA if its output power changes. The goal is to keep the power level within +/- 2.0 dB of the "reference value". The reference value can be set for each channel via the ODAxx card's “Traffic Configuration” window. Range: 0 dBm to -14 dBm. Default: - 8.8 dBm. The PLF (Tx) alarm will be raised if a channel’s output power decreases below the reference value by 2.5 dB or more.

Troubleshooting instructions 1

Troubleshoot and clear any upstream alarms first.

2

If the PLF (Tx) alarm persists, go to the Equipment View, right-click on the Card Replica of the ODAxx card raising the alarm and select Traffic > Configuration. For the affected channel, check the following: Does the Current Power minus VOA setting = Reference Power +/- 2.5 dB? – –

3

No: go directly to step 3. Yes: Warm Start the ODAxx card raising the PLF (Tx) alarm. After recovery time (approximately 3 minutes), the PLF (Tx) alarm should clear. If the alarm persists, continue to step 3.

See Figure 38. A problem in an upstream OMxx card can cause a PLF (Tx) alarm in the downstream ODAxx card. To determine which upstream OMxx card to investigate, examine the cross-connection status for the affected channel. The Channel Number is identified as part of the original alarm message, i.e., "CH# from ODA (PLF)". To investigate this channel's cross-connection status, go to the Equipment View, right-click on the NE Bar and select Configuration > Cross-Connection. This channel's cross-connection status will allow you to identify which upstream OMxx card sources the channel.

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

219

Troubleshooting Instructions

4

Troubleshooting Manual (TSMN)

Once the upstream OMxx card is identified, right-click on this card's Card Replica in the Equipment View and select Traffic > Configuration. [As an alternative, use the OPAPC Scan Spectrum window to view the full spectrum of equipped channels]. Via either GUI, take multiple measurements at least 20 seconds apart by using the Update button on these windows. Does the affected channel's output power remain close to the power for each of the other channels? –

– 5

No: the affected channel likely has a fluctuating VOA. Warm Start the OSCTUT card at the upstream node. After recovery time (approximately 3 minutes), the PLF (Tx) alarm should clear. If it does not clear, go to step 5 Yes: go directly to step 5.

If the alarm persists, contact your next higher level of technical support. Cold Start the ODAxx card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), the ODAxx card is defective. Replace the ODAxx card with a spare

Figure 38

3.2.35

220

PLF (Tx) alarm diagram

PHF (OPA)

Alarm name

Power too High Failure (PHF)

Default severity

Minor

Alarm object

OPAPC cards (OCh Monitor Point Line Rx and Tx).

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

Troubleshooting Manual (TSMN)

General information and causes

Troubleshooting Instructions

OPAPC cards monitor the signals at the OLI outputs. The PHF (OPA) alarm is raised if one of the channel-power levels exceeds a user-specified threshold. This threshold is set on the “OCh Monitoring Points Configuration” window. The default PHF (OPA) alarm threshold is +10 dBm. The allowed range for this user-settable threshold is -45 dBm to +18 dBm.

Troubleshooting instructions

3.2.35.1

1

Check that the threshold value is set properly on the “OCh Monitoring points Configuration” window. Correct if necessary. See special procedure in chapter 3.2.31.1 for an OPAPC connected to the Pre-amplifier OLI at an OADM100N or OADM100U network element. If the threshold is not set as described in the special procedure, a false PHF (OPA) alarm may be raised when there are low channel counts.

2

If the alarm persists after verifying that the user-defined threshold was set correctly, an upstream problem may be the cause. Troubleshoot and clear any upstream alarm. If the PHF (OPA) alarm persists, go to step 3.

3

If the alarm persists, contact your next higher level of technical support. Warm Start the OPAPC card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OPAPC card. If the alarm persists after recovery time (approx 3 minutes), the OPAPC card is defective. Replace the OPAPC card with a spare.

Special Procedure for OPAPC connected to a Pre-amplifier OLI When an OPAPC card is connected to an OLITPNC card at an OADM100N or OADM100U network element, the threshold for the PHF (Power High Failure) alarm must be set as described below. This will ensure that a false PHF alarm is not raised when there are low channel counts. PHF (OPA) Threshold = OLITPNC Power Per Channel + 7.5 dB. The OLITPNC power per channel value is provided by the TransNet Commissioning Report and can also be read from Element Manager by right-clicking on the OLITPNC Card Replica and selecting Card > Configuration. To set the PHF (OPA) threshold, right-click on the OPAPC card replica in the Equipment View and select OCh Monitor Points . . . > Configuration. On the resulting window, enter the desired value for Power High Failure Threshold in the "Line Rx" column.

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

221

Troubleshooting Instructions

3.2.36

Troubleshooting Manual (TSMN)

PLF (OPA)

Alarm name

Power too Low Failure (PLF)

Default severity

Minor

Alarm object

OPAPC cards (OCh Monitor Point Line Rx and Tx).

General information and causes

OPAPC cards monitor the signals at the OLI outputs. The PLF (OPA) alarm is raised if one of the channel-power levels drops below a user-specified threshold. This threshold is set on the “OCh Monitoring Points Configuration” window. The default PLF (OPA) alarm threshold is -5 dBm. The allowed range for this user-settable threshold is -45 dBm to +18 dBm. The PLF alarm can also be raised if a supposedly blocked channel is leaking through the OM card (due to a VOA that is not fully closed). The OPAPC does not suppress the PLF alarm for an invalid channel. The small amount of light that can leak through triggers the PLF alarm - the OPAPC does not ignore this channel, and hence, raises PLF. Under some circumstances, indications of the Power Low Failure condition may not be displayed on the “OCh Monitoring Points - Measure” window (in the Channel Failure State column).

Troubleshooting instructions

222

1

Check that the threshold value is set properly on the “OCh Monitoring points Configuration” window. Correct if necessary.

2

If the alarm persists after verifying that the user-defined threshold was set correctly, an upstream problem may be the cause. Troubleshoot and clear any upstream alarm. If the PLF (OPA) alarm persists, go to step 3.

3

Verify that fiber cables between the OLI and OPAPC are properly installed. If a cable was bent/pinched or improperly connected, correct the problem. The PLF (OPA) alarm should clear when the correct connection is established.

4

If the alarm persists, disconnect the fibers between the OLIs and the OPAPC card. Clean all optical connectors and re-connect. If the PLF (OPA) alarm persists, replace the fiber cable(s) with cleaned, inspected spares.

5

If the alarm persists, contact your next higher level of technical support. Warm Start the OPAPC card raising the alarm. If the alarm persists after recovery time (approx 3 minutes), Cold Start the OPAPC card. If the alarm persists after recovery time (approx 3 minutes), the OPAPC card is defective. Replace the OPAPC card with a spare.

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

Troubleshooting Manual (TSMN)

3.2.37

Troubleshooting Instructions

PLM

Alarm name

Payload Mismatch (PLM)

Default severity

Minor

Alarm object

TEX V3, TEX LH, OCR10-T V3, OCR10T-LH, I04T2G5, and I01T10G cards.

General information and causes

A channel traversing the optical path (ODU) must use the same card type at each end. For example, it is not permitted to for a channel to originate at one end via a TEX card and the other end by an OCR10-T card (or vice versa). The PLM alarm will be raised to indicate such a mismatch of card types.

Troubleshooting instructions

3.2.38

1

Ensure that identical card types are used for each channel at both ends of the optical Path.

2

Then, if necessary to restore traffic, execute a Warm Start of the card(s) raising the PLM alarm. If the Warm Start does not restore traffic, execute a Cold Start.

3

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

RETHNLNF

Alarm name

Remote Ethernet Link Fault (RETHNLNF)

Default severity

Major

Alarm object

OTS-40xx cards.

General information and causes

Remote fault ordered sets have been detected by the tributary port reconciliation layer.

Troubleshooting instructions 1

Follow the procedure for LOF alarm. Use the "Case B" (Client to Line) procedure.

2

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

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

223

Troubleshooting Instructions

3.2.39

Troubleshooting Manual (TSMN)

SD (OLI and OSCT cards)

Alarm name

Signal Degraded (SD)

Default severity

Minor

Alarm object

Pre-amplifier OLIs, In-Line OLIs, and OSCT cards.

General information and causes

The SD alarm is raised by an OLI card if the input power falls below a user-specified threshold. The threshold is set via the OLI “Card Configuration” window. The SD alarm is raised by an OSCT card if the BER of the incoming optical supervisory channel is 1 x 10E-6 or worse. This is a fixed threshold and cannot be changed by the user.

Troubleshooting instructions

3.2.40

1

For OLI cards, troubleshoot the SD alarm using the same instructions for the OPLOS alarm. For OSCT cards, troubleshoot the SD alarm using the same instructions for the EXC alarm.

2

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

SD (OCU cards)

Alarm name

Signal Degraded (SD)

Default severity

Minor

Alarm object

The SD alarm can be raised by: • • • •

General information and causes

TEX cards (all types). OCR10T cards (all types). I04T2G5 cards. I01T10G cards.

This alarm is raised if the Bit Error Rate (after Forward Error Correction) of the received optical signal is worse than a user-specified threshold.

Troubleshooting instructions

224

1

Verify that the user-specified value for BER Degraded Threshold on the affected card is set properly.

2

If the alarm persists, follow the procedure for LOS alarm (Line In side).

3

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

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

Troubleshooting Manual (TSMN)

3.2.41

Troubleshooting Instructions

SSF

Alarm name

Server Signal Fail (SSF)

Default severity

Minor

Alarm object

The SSF alarm can be raised by: • • • • • • • • • • • • • • • • • • •

General information and causes

TEX and OCR10 Path (ODU2-TTP). TEX and OCR10 Section (OTU2-CTP). TEX Trib# Client to Line - Client Layer (RS16-CTP). TEX Trib# Line to Client - Client Layer (RS16-CTP). TEX Trib# Path (ODU1-CTP). OTS-4400 Section In TTP Sk. OTS-4040 Client to Line - Client Layer (RS256-CTP). OTS-4040 Line to Client - Client Layer (RS256-CTP). OTS-4040 Path (ODU3-TTP). OTS-4040 Section (OTU3-TTP). OTS-4011 Path (ODU3-TTP). OTS-4011 Section (OTU3-TTP). OTS-4011 Trib# Client to Line - Client Layer (RS64CTP). OTS-4011 Trib# Line to Client - Client Layer (RS64CTP). OTS-4011 Trib# Path (ODU2-TTP). I04T2G5 and I01T10G ODU2. I04T2G5 and I01T10G OTU2. I01T10G Ethernet 10G. I01T10G RS64.

An SSF alarm indicates a signal failure on a higher layer (refer to Figure 39 for examples). The signal failure could be on the card raising the SSF alarm, or on another upstream card.

Troubleshooting instructions 1

This alarm can be caused by a user-initiated change of the Client Mode without first clearing all TCMs (Tandem Connection Monitoring). Before a change in client mode is made on a card, all previously-configured TCM Layers (tributary and line) must first be cleared. Otherwise, an SSF alarm (on the TCM layer) may be generated. If it is suspected, that a recent change in Client Mode triggered the SSF alarm, Warm Start the card raising the alarm and the SSF alarm should clear. If the alarm was not due to a recent change in Client Mode, continue to step 2.

2

An SSF alarm always results from some other alarm in the system. Troubleshoot the other raised alarm(s) first.

3

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

g Background information about SSF: The principle of SSF (an alarm name defined by ITU-T) is very similar to an Alarm Indication Signal (AIS). The word "Server" in "Server Signal Fail" refers to lower transport server layers. If a layer receives SSF, it is not considered to be service-affecting because the layer that inserted the SSF

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

225

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

will have already reported the root-cause problem (incoming signal problem or equipment problem) as a service-affecting alarm. Note that when a client interface is in LAN, OTU2, or OTU2LAN mode, no SSF is defined on the Line-to-Client, Client-to-Line, or Client layers.

Figure 39

226

SSF alarm examples

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

Troubleshooting Manual (TSMN)

3.2.42

Troubleshooting Instructions

SYNCFail

Alarm name

Synchronization Fail (SYNCFAIL)

Default severity

Major

Alarm object

The SYNCFAIL alarm can be raised by: • • • •

General information and causes

TEX cards (all types). OCR10T cards (all types). I04T2G5 cards. I01T10G cards.

For OCU 10 Gbit Ethernet mode: if the 10 Gbit Ethernet is not detected for several consecutive frames, the SYNCFail alarm will be raised.

Troubleshooting instructions

3.2.43

1

Problem is with the Client signal. Check Client signal source.

2

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

TD (OLI cards)

Alarm name

Transmit Degrade (TD)

Default severity

Minor

Alarm object

Booster OLIs and In-Line OLIs. Note: OLIs used in the Droppath at OADM network elements do not raise the TD alarm.

General information and causes

This alarm indicates that the OLI output power has fallen below a user-settable threshold. This threshold can be set via the OLI “Card Configuration” window. The TD alarm serves as an advance warning that a TF alarm might soon occur.

Troubleshooting instructions 1

Wait 3 minutes. If the TD is still raised after 3 minutes, continue to step 2. But, if the TD alarm self-clears, another alarm may be raised which is the true root cause. Go to the troubleshooting instructions for whichever alarm(s) is raised (most likely CTRLCABLP, CHCNTMISM, LOC, ILOL1, ILOL2, or ILOL3, usually caused by a fiber break somewhere in the TSC card’s “control loop”.

2

Identify the OLI card raising the TD alarm. (See Behavior Note below for special cases in identifying which OLI card is suffering the TD condition).

3

When the OLI card raising the TD alarm is identified, check its TD alarm threshold setting on its “Card Configuration” window. Then, follow the same instructions for the OLI TF alarm.

g Behavior Note: When a TD alarm condition exists on an Add-path OLI, the alarm is shown on LCT as being raised by the Express Booster OLI. The Add-path OLI does

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

227

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

not raise an alarm, but the alarm will be shown as active on the Add-path OLI's alarm window. Therefore, keep in mind that when an Express Booster OLI raises a TD alarm, the actual fault may be on the Add-path OLI. Open the fault windows for the Add-path OLI (right-click on the Card Replicas and select Fault > Alarms). If the Add-path OLI is truly the card suffering the TD alarm, the corresponding fault window will show the alarm as raised.

3.2.44

TD (OCU cards)

Alarm name

Transmit Degrade (TD)

Default severity

Minor

Alarm object

The TD alarm can be raised by: • • • • • • • • • • • •

General information and causes

TEX Client Interface. TEX Line Interface Out. OCR10-R Line Interface Out. OCR10-T Client Interface Out. OCR10-T Line Interface Out. I04T2G5 Line Interface Out. I04T2G5 Client Interface Out. I01T10G Line Interface Out. I01T10G Client Interface Out. OTS-4011 Line Interface Out. OTS-4400 Line Interface Out. OTS-4040 Line Interface Out.

A TD alarm will be raised if the laser current on the indicated interface has risen above its Beginning-of-Life value.

Troubleshooting instructions

228

1

The TD alarm serves as an advance warning that a TF alarm might soon occur. Immediate replacement of the card is not necessary, but the transmit conditions should be monitored. Card replacement should probably be scheduled for the next convenient maintenance period.

2

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

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

Troubleshooting Manual (TSMN)

3.2.45

Troubleshooting Instructions

TF (OLI and ODAxx cards)

Alarm name

Transmit Fail (TF)

Default severity

Major

Alarm object

Booster OLIs, In-Line OLIs, and ODAxx cards Note: OLIs used in the Drop-path at OADM network elements do not raise the TF alarm.

General information and causes

OLI cards: The alarm is raised by a Booster or Inline OLI if the actual (measured) output power of the Amplifier differs from the internally-calculated "target" value by more than 9 dB. ODAxx cards: The alarm is raised if the output power level for a particular channel is below the fixed threshold of -18 dBm. This alarm suppresses PLF (Tx) alarm.

Troubleshooting instructions 1

If any of the alarms listed below are also raised, go to the instructions for that alarm and troubleshoot it first. – – – – – – –

PU1TD, PU2TD, PU3TD, PU4TD, and PU5TD (OLI card) PU1TF, PU2TF, PU3TF, PU4TF, and PU5TF(OLI card) OBLOS (OLI card) OBTF (OLI card) OPTF (OLI card) SBL (ODAxx card) PLF (Rx) (ODAxx card)

2

If the TF alarm persists, Warm Start the card raising the TF alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare.

3

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

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

229

Troubleshooting Instructions

3.2.46

Troubleshooting Manual (TSMN)

TF (OCU cards)

Alarm name

Transmit Fail (TF)

Default severity

Major

Alarm object

The TF alarm can be raised by: • • • • • • • • •

General information and causes

TEX Client Interface. TEX Line Interface Out. OCR10-R Line Interface Out. OCR10-T Client Interface Out. OCR10-T Line Interface Out. I04T2G5 Line Interface Out. I04T2G5 Client Interface Out. I01T10G Line Interface Out. I01T10G Client Interface Out.

A TF alarm will be raised if the indicated transmit laser is off when it should be on. This is likely due to an internal hardware fault.

Troubleshooting instructions

!

230

1

Warm Start the card raising the TF alarm. Sometimes, this allows a failed card to recover. Note however, that the recovery is often only temporary. If the Warm Start does not clear the alarm, Cold Start the card. If the Cold Start does not clear the alarm, immediately replace the failed card with a spare.

2

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

Caution! Important note for TEX cards with hot-pluggable SFP(s) installed: A TF alarm on the Client interface could be caused by a faulty SFP module. Replace the SFP module with a spare of the matching type to clear the alarm.

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

Troubleshooting Manual (TSMN)

3.2.47

Troubleshooting Instructions

TIM (OSCT cards)

Alarm name

Trace Identifier Mismatch (TIM)

Default severity

Minor

Alarm object

OSCT cards (OSC-TTP Termination Side x).

General information and causes

The TIM alarm is raised if the OSCT card detects a mismatch between the expected Trail Trace Identifier message string and the Trail Trace Identifier message string actually received. Trail Trace Identifier (TTI) is a feature that allows network operators to verify correct connectivity through the network elements. The basic principle is that specific overhead bytes are reserved for Trace Messages of the user's choosing. By specifying the "Actually Sent" (transmitted) and the "Expected" (received) trace messages on various craft terminal windows, the system can automatically verify that fiber connections have been made as intended. This is accomplished by comparing the expected Trace Message to that actually received. If they differ, the TIM alarm is raised, alerting personnel of the incorrect connections.

Troubleshooting instructions 1

Check the configuration of the Trail Trace Identifier message strings at both the upstream OSCT card and the OSCT card raising the alarm (from the OSC Termination/DCC windows). Verify that the Trace Messages were configured as desired.

2

If the Trace Messages were configured as desired and the TIM alarm persists, there is a fiber mis-connection somewhere between the two OSCT cards. Determine the location and make the correct fiber connection.

3

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

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

231

Troubleshooting Instructions

3.2.48

Troubleshooting Manual (TSMN)

TIM (OCU cards)

Alarm name

Trace Identifier Mismatch (TIM)

Default severity

Minor

Alarm object

The TIM alarm can be raised by: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •

232

OCR10R Section (OTU2) TTI. OCR10T / TEX Line side Section (OTU2) TTI. OCR10T / TEX Line side Path (ODU2) TTI. OCR10T / TEX Line side TCM Layer TTI. TEX Line side Path (ODU1) TTI. OCR10T / TEX Line to Client TTI. OCR10T / TEX Client to Line TTI. OCR10T Client Section (OTU2) TTI. OCR10T Client Path (ODU2) TTI. TEX Tributary Section (OTU1) TTI. TEX Tributary Path (ODU1) TTI. I08T10G / I01T10G Line side Section (OTU2) TTI. I08T10G / I01T10G Line side Path (ODU2) TTI. I08T10G / I01T10G / I04T2G5 Line side TCM layer TTI. I04T2G5 Line side Section (OTU1) TTI. I04T2G5 / I08T10G Line side Path (ODU1) TTI. I04T2G5 / I08T10G / I01T10G Line to Client TTI. I04T2G5 / I08T10G / I01T10G Client to Line TTI. I04T2G5 / I08T10G / I01T10G Tributary side Path (ODU1) TTI. I08T10G Tributary side Section (OTU1) TTI. I01T10G Tributary side Section (OTU2) TTI. I01T10G Tributary side Path (ODU2) TTI. OTS-4011/OTS-4040/OTS-4400 Line side Section (OTU3) TTI. OTS-4011/OTS-4040 Line side Path (ODU3) TTI. OTS-4011 Path (ODU2) TTI. OTS-4011/OTS-4040 Line side and Tributary side TCM layer TTI. OTS-4011/OTS-4040 Client to Line TTI. OTS-4011 Tributary side Section (OTU2) TTI. OTS-4011 Tributary side Path (ODU2) TTI. OTS-4040 Tributary side Section (OTU3) TTI. OTS-4040 Tributary side Path (ODU3) TTI.

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

Troubleshooting Manual (TSMN)

General information and causes

Troubleshooting Instructions

The TIM alarm is raised if the indicated card detects a mismatch between the expected Trail Trace Identifier message string and the Trail Trace Identifier message string actually received. Trail Trace Identifier (TTI) is a feature that allows network operators to verify correct connectivity through the network elements. The basic principle is that specific overhead bytes are reserved for Trace Messages of the user's choosing. By specifying the "transmitted" and the "expected received" trace messages on various craft terminal windows, the system can automatically verify that fiber connections have been made as intended. This is accomplished by comparing the expected Trace Message to that actually received. If they differ, the mismatch alarm is raised, alerting personnel of the incorrect connections.

Troubleshooting instructions

3.2.49

1

Check the configuration of the Trail Trace Identifier message strings at both the immediate upstream card and the card raising the alarm. Verify that the Trace Messages were configured as desired.

2

If the Trace Messages were configured as desired and the TIM alarm persists, there is a fiber mis-connection somewhere between the two cards. Determine the location and make the correct fiber connection.

3

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

UPM

Alarm name

User Payload Mismatch GFP (UPM)

Default severity

Minor

Alarm object

I04T2G5 and I01T10G cards

General information and causes

The UPM alarm is raised due to a mismatch between the received and expected values for the Generic Framing Procedure (GFP) payload User Payload Identifier (UPI) header field.

Troubleshooting instruction 1

Troubleshoot the UPM alarm via the same instructions for the LFD alarm.

2

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

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

233

Troubleshooting Instructions

3.3

Troubleshooting Manual (TSMN)

Processing Error Alarms This section contains troubleshooting instructions for hiT 7500 Processing Error alarms.

3.3.1

SCP

Alarm name

Storage Capacity Problem (SCP)

Default severity

Minor

Alarm object

MCU card: TCP Transport Connection x, OSI Transport Connection x

General information and causes

This alarm indicates an internal overload of the MCU card software.

Troubleshooting instructions 1

Often, the Storage Capacity Problem is only a temporary condition, due to a large number of alarms in a short period. Wait a short time and see if the alarm clears by itself.

2

If the alarm persists, the problem could be due to too many Element Managers connected at once. Reduce the number of Element Managers connected.

3

Contact your next level of technical support before proceeding. If no other cause can be found, Cold Start the MCU card raising the alarm (management visibility will be lost to this NE while the MCU executes its Cold Start routine). If the alarm persists after reset recovery time (approx 5 minutes), the MCU card is defective. Replace the affected MCU card with a spare.

g Behavior Note: If the NE loses the transport connection while an SCP alarm is raised, the object administering the transport connection is removed. Therefore, it is not possible to send a notification that the SCP alarm has cleared. In other words, when the SCP alarm clears, there will be no indication of this in the NE Alarm Log. In this case, it is the task of TNMS to clear the current problem list autonomously. Later, when TNMS rebuilds a connection, a new transport connection object will be created with its own new current problem list. Therefore, no SCP clear entry will be visible on the NE.

234

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

Troubleshooting Manual (TSMN)

3.4

Troubleshooting Instructions

Environmental Alarms This section contains troubleshooting instructions for hiT 7500 Environmental alarms.

3.4.1

EXT

Alarm name

Telemetry Interface (Ext)

Default severity

Minor

Alarm object

OSCT and SMU cards.

General information and causes

The EXT alarm is raised when one of the user-defined Telemetry Interface input relays (TIF Sensors) is activated. Note: The cable for TIF Sensors attaches to the connector named "TIF" on the shelf's Connector Panel.

Troubleshooting instructions 1

The input relays are intended to be used as traditional "housekeeping" alarm inputs connected to customer facilities of his choosing (door alarm, temperature alarm, etc). These inputs are configured via the craft terminal by right-clicking the mouse on the OSCT or SMU card replica and selecting Card > TIF Monitors. If a monitoring point raises a EXT alarm, check the external device assigned to that monitoring point.

2

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

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

235

Troubleshooting Instructions

3.4.2

Troubleshooting Manual (TSMN)

TIFACT

Alarm name

TIF Activated Alarm (TIFACT)

Default severity

Warning

Alarm object

OSCT and SMU cards.

General information and causes

The alarm is raised when the user issues an "Operate" command to one of the user-defined Telemetry Interface outputs ("actors"). The alarm message will identify the exact output as: TIF Actor n, where "n" is the number of the Actor (1 to 4). The output relays (user configurable as normally-open or normally-closed) are intended to be used as traditional "housekeeping" control relays connected to customer devices of his choosing. These outputs are configured via the craft terminal by right-clicking the mouse on the OSCT or SMU card replica and selecting Card > TIF Actors. The resulting “TIF Actors - Config” window features buttons named Operate and Release. The cable for TIF Actors attaches to the connector named "TIF" on the shelf's Connector Panel.

Troubleshooting instructions 1

The TIFACT alarm will be raised whenever an Actor's Operate command is in effect. As such, this alarm simply serves as a reminder that an Actor has been deliberately commanded by the user to activate and latch into its "non-normal" position (see Table 10). If you wish to latch the Actor back to its "normal" position (open or closed), press the Release button on the TIF Actors - Config window. Doing so will clear the TIFACT alarm.

2

If the alarm persists, contact your next higher level of technical support. If Actor has been configured as:

“Status”

NO (Normally Open)

Operate

Relay will latch closed. TIFACT alarm will raise.

NO (Normally Open)

Release

Relay will latch open. TIFACT alarm will clear.

NC (Normally Closed) Operate

Relay will latch open. TIFACT alarm will raise.

NC (Normally Closed) Release

Relay will latch closed. TIFACT alarm will clear.

Table 10

236

Issue this command

Summary Table for TIF Actors

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

Troubleshooting Manual (TSMN)

3.5

Troubleshooting Instructions

Security Alarms This section contains troubleshooting instructions for hiT 7500 Security alarms.

3.5.1

EXCLOGIN

Alarm name

Unsuccessful Logins Exceeded (EXCLOGIN)

Default severity

Major

Alarm object

Network Element.

General information and causes

This alarm is a security feature. It will be raised if a particular user account has five sequential unsuccessful log-in attempts, thereby warning of a possible break-in attempt.

Troubleshooting instructions 1

There are three ways to clear an EXCLOGIN alarm: – –

–

2

3.5.2

The legitimate user successfully logs-in and logs-out. “User Administration” window: an Administrator (User Class 10 / Security level user) can reset the user account, as long as the legitimate user is not currently logged-in. “User Administration” window: if the legitimate user is currently-logged-in, an Administrator can force him off to clear the alarm. The legitimate user must then log-in again.

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

PWEXP

Alarm name

Password Expired (PWEXP)

Default severity

Minor

Alarm object

Network Element.

General information and causes

This alarm is a security feature. It indicates that a user's password has expired. An Administrator (User Class 10 / Security level user) has full control over each user's password aging parameters.

Troubleshooting instructions 1

Contact the user with the expired password and inform him that he must log-in and change his password. The PWEXP alarm will be cleared as soon as the password is changed.

2

Alternatively, an Administrator can perform either of the following actions to clear the alarm: –

change this user's Password Aging parameter. Doing so will cause the password expired time to reset and clear the PWEXP alarm.

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

237

Troubleshooting Instructions

Troubleshooting Manual (TSMN)

–

3

3.5.3

change/reset this user's password. Be sure to inform the user of the new password. When the user next logs-in, he must change his password again for security purposes.

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

PWEXPSON

Alarm name

Password will expire soon (PWEXPSON)

Default severity

Warning

Alarm object

Network Element.

General information and causes

This alarm is a security feature. It indicates that a user's password will expire soon. An Administrator (User Class 10 / Security level user) has full control over each user's password aging parameters and amount of advance warning given the user for a soon-to-expire password.

Troubleshooting instructions

3.6

1

The PWEXPSON alarm will be cleared as soon as the user changes his password.

2

Alternatively, an Administrator can change/reset the user's password for him. Be sure to inform the user of the new password. When the user next logs-in, he should change his password again for security purposes.

3

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

Subsystem Alarms This section contains troubleshooting instructions for hiT 7500 Subsystem alarms.

3.6.1

SMISS

Alarm name

Sub System Missing (SMISS)

Default severity

Major

Alarm object

MCU-CNE card

General information and causes

The SMISS alarm will be raised if the indicated card loses communication with one or more Sub-Agent MCUs (MCUMTS, MCU-OCU, MCU-OCU40, or MCU-OCU73). See Figure 40 for examples. This condition can be caused by a missing or failed SubAgent MCU (or dc power problem that affects the Sub-Agent MCU), or incorrect/missing ethernet cabling between the shelves and the Ethernet Switch.

238

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

Troubleshooting Manual (TSMN)

Troubleshooting Instructions

Troubleshooting instructions 1

Verify that all MCU cards are properly installed and shelves are powered. DC power problems that cause a shutdown of a Sub-Agent MCU card will also cause a SMISS alarm. So, troubleshoot any PWR alarms first.

2

Verify that the ethernet cable from the COPA of the affected shelf to the Ethernet Switch is properly connected on both sides as follows: – – –

3

10BT_M1 -> Ethernet Switch, connection between MCU-MTS and Ethernet Switch. LAN_M1 -> Ethernet Switch, connection between MCU-OCU and Ethernet Switch. MM SB or SB port of MCU Shelf -> Ethernet Switch, connection between MCUOCU40 or MCU-OCU73 and Ethernet Switch.

Verify the LED activity on the Ethernet switch. All three LEDs for the port in question should be on (or at least flashing). –

– –

If all three LEDs are on, the communication between MCU-CNE and Sub-Agent MCU should be OK. Wait 5 minutes and see if the sub-agent re-connects on its own. If the SMISS persists, skip step 4 and go to step 5. If only the middle LED is flashing and the other two are off, the problem is with the MCU. Skip step 4 and go to step 5. If none of the LEDs for that port are on, move the Ethernet cable connector (related to the affected sub-agent) to another unused port on the Ethernet switch. Do not use ports 1 and 1x on the switch. – If all three green LEDs for the new port are lit, continue with step 4. – If only the middle LED is flashing, skip step 4 and go to step 5. – If none of the LEDs on the new port are lit, replace the cable between the affected shelf and the Ethernet switch. If LEDs remain off, skip step 4 and go to step 5.

4

Try to connect the cable to the original port on the Ethernet switch. If LEDs for that port remain off, the Ethernet switch port is defective. Keep the Ethernet cable connected to the "new" port, mark the defective port and schedule a replacement of the Ethernet switch. END OF PROCEDURE.

5

Unplug the Sub-Agent MCU for 1 minute and than plug it back in. Wait 10 minutes to see if the SMISS alarm clears (LEDs for that port on the Ethernet switch should be lit as well

6

If the SMISS alarm persists, replace the Sub-Agent MCU card.

7

If the SMISS alarm persists, call your next higher level of technical support.

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

239

Troubleshooting Instructions

Figure 40

240

Troubleshooting Manual (TSMN)

SMISS alarm examples

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

Troubleshooting Manual (TSMN)

3.6.2

Troubleshooting Instructions

SFAIL

Alarm name

Sub System Failure (SFAIL)

Default severity

Major

Alarm object

MCU cards.

General information and causes

The SFAIL alarm is raised if the Main Agent MCU / SubAgent MCU communication is working properly, but a defect exists in a Sub-Agent. For example, a defective flash on a Sub-Agent MCU, or the APS software is not properly loaded onto a Sub-Agent.

Troubleshooting instructions 1

Determine if one of the Sub-Agent MCU cards is raising a CP alarm and troubleshoot that alarm first.

2

If the alarm persists, Cold Start the MCU card raising the alarm. This may clear the SFAIL alarm.

3

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

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

241

Card Replacement Instructions

Troubleshooting Manual (TSMN)

4 Card Replacement Instructions This chapter provides instructions for removing and replacing failed hardware components. Please read the warnings and cautions below before replacing any component.

!

!

!

!

Danger! Always use appropriate laser eye protection when working with the system. The SURPASS hiT 7500 system operates with Laser Classes 1M, 3A, and 3B.

Warning! Always use appropriate ESD grounding devices and practices to avoid damaging the equipment.

Warning! Once a replacement card has been inserted into the shelf, software download begins. Never withdraw a card during this process as software corruption can result. See chapter 5.4 for the minimum wait times for each plug-in card type.

Caution! All plug-in cards must be inserted slowly and carefully to avoid damage to components. When inserting a card, make sure both latches on the card are unlocked and open. Never attempt to insert a plug-in card with a closed latch. If a card seems to require unusual effort to insert - STOP. If anything is physically interfering with card insertion - STOP. If a card is not correctly engaging the shelf guide rails or backplane connector - STOP. Never apply excessive force when installing a card; otherwise severe damage can occur to the card and shelf. Only after the card is fully inserted and properly seated in the backplane connector, carefully close and lock the card latches. Close both latches at the same time. Always insert one card at a time. Never attempt to simultaneously insert two or more cards into the shelf. Some card types have a special EMI gasket attached to them, which creates a tight seal with neighboring cards. If this gasket is loose, torn, or otherwise defective, do not attempt to install this card. Return the card for replacement.

g Depending on card type, replacement of a plug-in card may result in traffic interruption. If possible, always switch traffic to a protection facility before executing any card replacement procedure. After removing any failed card or other component, prepare it for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”.

242

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

Troubleshooting Manual (TSMN)

4.1

Card Replacement Instructions

CAX card Replacement instructions 1

Log-in as a Power User. To do so, type Ctrl-Alt-P and PowerOn! password.

2

If a TSC is present (connected to the card being replaced), right-click on the TSC card replica and select Card > Configuration. On the resulting TSC “Card Configuration” window, disable Transient Suppression. Wait until the Transient Suppression Laser State changes to “disabled”. This may take a few minutes. Then, refresh the Card > Configuration window and verify that all laser currents are displayed as “0”.

3

Identify the Add-OLI in the affected ADX network element - it will be in Shelf 2, Slot 013 - in the same shelf that contains the failed CAX card. Disable the pump laser on this OLI card. To do so, right-click on its card replica and select Card > Configuration. On the resulting OLI “Card Configuration” window, uncheck the Pump Enable checkbox.

4

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

5

Withdraw the failed card from the shelf a short distance. Disconnect the fibers from the failed card.

6

Remove the failed card fully from the shelf.

7

Insert the replacement card a short distance into the shelf. Do not fully insert it.

8

Clean all fiber ends and re-connect all fibers to the new card.

9

Fully insert the replacement card into the shelf.

10 Re-enable Transient Suppression if it was disabled in Step 2. Wait until the Transient Suppression Laser State changes to “enabled”. This may take a few minutes. 11 Re-enable the pump laser of the OLI card that was disabled in Step 3. 12 Log-off as Power User. To do so, type Ctrl-Alt-P, then click the Close button. 13 Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE. Impact Total loss of the express and add traffic passing through the CAX during card replacement.

4.2

CDN, CDU, CDAN cards Replacement instructions 1

Log-in as a Power User. To do so, type Ctrl-Alt-P and PowerOn! password.

2

If a TSC card is present (connected to the card being replaced), right-click on the TSC card replica and select Card > Configuration. On the resulting TSC “Card Configuration” window, disable Transient Suppression. Wait until the Transient Suppression Laser State changes to “disabled”. This may take a few minutes.

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

243

Card Replacement Instructions

Troubleshooting Manual (TSMN)

Then, refresh the Card > Configuration window and verify that all laser currents are displayed as “0”. 3

Identify the Pre-amplifier OLI in the affected ADU, ADX, or ADN sub-agent; it will be in Shelf 0, Slot 010 - in the same shelf that contains the failed CDx card. Disable the pump laser on this OLI card. To do so, right-click on its card replica and select Card > Configuration. On the resulting OLI “Card Configuration” window, uncheck the Pump Enable checkbox.

4

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

5

Withdraw the failed card from the shelf a short distance. Disconnect the fibers from the failed card.

6

Remove the failed card from the shelf.

7

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect all fibers to the new card.

8

Re-enable Transient Suppression if it was disabled in Step 2. Wait until the Transient Suppression Laser State changes to “enabled”. This may take a few minutes.

9

Re-enable the pump laser of the OLI Pre-amplifier that was disabled in Step 3.

10 Log-off as Power User. To do so, type Ctrl-Alt-P, then click the Close button. 11 Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE. Impact Total loss of the express and drop traffic passing through the failed card during card replacement.

4.3

FSU Replacement instructions

244

1

Refer to Figure 41. Open the shelf front door. Carefully remove the Lower Fan Unit and Air Filter Assembly to gain access to the FSU.

2

Press and release the two pushbuttons on the FSU to unlatch it. Then, carefully remove the FSU from the shelf.

3

Install the new FSU, making sure it snaps into place properly. Press the pushbuttons to latch the new FSU into the shelf.

4

Re-install the Lower Fan Unit and the Air Filter Assembly.

5

Close the shelf front door.

6

Verify that all alarms are cleared. PROCEDURE COMPLETE.

7

Prepare the failed FSU for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”.

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

Troubleshooting Manual (TSMN)

Figure 41

4.4

Card Replacement Instructions

How to remove the FSU from a shelf

MCU card For MCU replacement instructions, go to Chapter 9 of this document.

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

245

Card Replacement Instructions

4.5

Troubleshooting Manual (TSMN)

MIB circuit board For MIB replacement instructions, go to Chapter 9 of this document.

4.6

NEAP Circuit Board The NEAP (Network Element Alarm Panel) circuit board can be replaced without interrupting traffic by following the instructions below. This procedure can be fully completed from the front of the shelf - no rear access is required. Replacement instructions 1

Locate the defective NEAP and record the current Shelf Address.

2

Unplug the shelf's upper fan unit and withdraw it slightly from the shelf. When all fans have stopped turning, remove the fan unit completely from the shelf.

3

Before removing any of the screws, place a piece of cardboard (approximately 14" x 8") in the fan unit location to prevent screws from falling down into the shelf's plugin card area.

4

Remove the three plastic screws (no tool required) located at the bottom of the NEAP (accessible from underneath now that the fan unit has been removed from the shelf.

5

Use pliers to loosen the two screws of the DB9 connector at the NEAP. Use your hands to remove them completely.

6

Tilt the back of the NEAP circuit board slowly down towards an 80° angle while moving it back until the circuit board is fully accessible (no longer obstructed by the front panel).

7

Remove the ribbon cable connector by pressing the left and right release with one hand while twisting the circuit board with the other.

8

Set the defective NEAP circuit board aside and unpack the new one.

9

On the new NEAP, set the Shelf Address to the same value noted in Step 1.

10 Connect the ribbon cable to the new NEAP circuit board. 11 Tilt the front of the NEAP circuit board upward until the DB9 connector and the pushbuttons go through the openings in the NEAP front panel. 12 Press the rear of the NEAP circuit board up so that it returns to a vertical position. 13 Align the NEAP circuit board, so that the metal screws of the DB9 connector can be mounted, keeping them slightly loose. 14 Insert the three plastic screws removed in Step 4 into their respective holes and tighten them with your hands. The best approach is to work from right to left. Caution: use care when tightening the plastic screws to avoid damaging them. 15 Carefully tighten the metal screws of the DB9 connector. 16 Check the proper functioning of the new NEAP circuit board: – –

The four UBAT LEDs should be lit (assuming all four power feeds are connected and working). Press the Lamp test button. All LEDs in the shelf should light.

17 Remove the cardboard. Re-install the upper fan unit.

246

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

Troubleshooting Manual (TSMN)

Card Replacement Instructions

18 Prepare the failed NEAP circuit board for the return and repair process as described in chapter 10 “Packing equipment for return”. Mark the NEAP with a "defective" label and attach a short failure description. PROCEDURE COMPLETE.

4.7

OCR10 and TEX cards Replacement instructions 1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Disconnect all fibers from the failed card.

3

See instructions in chapter 4.31. Remove any SFP modules present on the failed card, noting carefully which SFP was installed in which port. Insert the SFPs into the corresponding ports on the replacement card.

4

Remove the failed card from the shelf.

5

Insert the replacement card into the shelf. Clean fiber ends and re-connect all fibers to the new card. The card will be displayed in orange color during initialization on the Element Manager Module View. Important: do not unplug the card during its first initialization period, which can take up to 15 minutes.

6

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Traffic interruption during card replacement for the channel(s) served by the failed card.

4.8

ODA20, ODA20 cards Replacement instructions 1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Withdraw the failed card from the shelf a short distance.

3

Disconnect all fibers from the failed card. Fully remove the card from the shelf.

4

Insert the replacement card partially into the shelf. Clean all fiber ends and reconnect all fibers to ithe new card.

5

Fully insert the replacement card into the shelf.

6

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Traffic interruption during card replacement for the channels served by the failed card. Remarks If an OD or ODA is plugged-in at an OTT network element and the Demux In port is open, the card will raise an SBL alarm (precondition: valid channels are configured for

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

247

Card Replacement Instructions

Troubleshooting Manual (TSMN)

the corresponding subband). This will cause Automatic Power Reduction Mode (APRM) at the OLI Pre-amplifier. In addition, traffic may be disturbed at other OD / ODA cards.

4.9

OLI cards (except Add-OLI and Drop-OLI) Replacement instructions 1

Determine the upstream terminal (OADM or OTT). Open the “Optical Link Control” window and click the Forced Prestart button to shut down the link.

2

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

3

Withdraw the failed OLI card from the shelf a short distance.

4

Disconnect all fibers from the failed card. If the failed OLI has pigtails connected to PUMP cards, unseat each of those PUMP cards and disconnect the pigtails from the OLI.

5

Fully remove the failed OLI card from the shelf.

6

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect all fibers to the new card. Caution: never withdraw a newly-installed OLI from the shelf until at least 6 minutes have passed - otherwise corruption of the controller software of the OLI can result.

7

Re-connect the OLI pigtails to the respective pump cards and re-insert the PUMP cards into the shelf.

8

Once the OLI and PUMP cards are back in service, go back to the upstream terminal (as determined in step 1), open the “Optical Link Control” window and execute Power Equalization and Link Start-up.

9

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Total traffic interruption during card replacement because of the Forced Prestart and new Link Startup routine. Remarks Link must be set to prestart. Otherwise, high output power will occur.

4.10

Add-OLI cards (used in ADU or ADX: Shelf 2, Slot 013) Replacement instructions

248

1

Determine all add ports and set port mode to disabled.

2

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

3

Withdraw the failed OLI card from the shelf a short distance.

4

Disconnect all fibers from the failed card.

5

Fully remove the failed OLI card from the shelf.

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

Troubleshooting Manual (TSMN)

Card Replacement Instructions

6

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect all fibers to the new card. Caution: never withdraw a newly-installed OLI from the shelf until at least 6 minutes have passed - otherwise corruption of the controller software of the OLI can result.

7

Once the card is back in service, set the port mode of the first channel to automatic. Once that channel is upgraded, the remaining ports can be set to automatic.

8

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Total traffic interruption during card replacement until channel upgrade is complete. Remarks OM port mode needs to be set to disabled. Otherwise, high output power will occur.

4.11

Drop-OLI cards (used in ADU or ADX: Shelf 2, Slots 007 and 010) Replacement instructions 1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Withdraw the failed OLI card from the shelf a short distance.

3

Disconnect all fibers from the failed card.

4

Fully remove the failed OLI card from the shelf.

5

Insert the replacement card partially into the shelf. Clean all fiber ends and reconnect all fibers to the new card.

6

Insert the replacement card fully into the shelf. Caution: never withdraw a newlyinstalled OLI from the shelf until at least 6 minutes have passed - otherwise corruption of the controller software of the OLI can result.

7

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Total traffic interruption during card replacement.

4.12

OM10, OM20 cards Replacement instructions 1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Disconnect all fibers from the failed card’s input ports first.

3

Disconnect the fiber from the failed card’s output port.

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

249

Card Replacement Instructions

Troubleshooting Manual (TSMN)

4

Fully remove the failed card from the shelf.

5

Insert the replacement card fully into the shelf. Clean all fiber ends. Re-connect the output fiber first. Then re-connect the input fibers.

6

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Traffic interruption during card replacement for the channels served by the failed card. Remarks Always disconnect the input fibers first, then the output. Otherwise, loss of other channels (not handled by the failed card) may occur. Similarly, always re-connect the output fiber first, then all the input fibers.

4.13

OMDFC, OMDFIC, OMDIFC cards (at OTTU) Replacement instructions 1

Identify the Sub-agent that contains the card to be replaced. Set the Link State for this Line Booster Amplifier to Pre-start and disable the pump laser in the Pre-amplifier.

2

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

3

Disconnect all fibers from the failed card. Fully remove the card from the shelf.

4

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect all fibers to the new card.

5

Re-enable the Pre-amplifier pump laser. Perform a Link Start-up for the Line Booster Amplifier.

6

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Total traffic interruption during card replacement, including express channels.

4.14

OMDFC or OMDFIC cards (at OADM100U) Replacement instructions

250

1

One-by-one, set all OM port modes to disabled.

2

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

3

Disconnect all fibers from the failed card and remove it from the shelf. Note that the Add-OLI amplifier will automatically shut down since there is no input to it.

4

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect all fibers to the new card.

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

Troubleshooting Manual (TSMN)

Card Replacement Instructions

5

One-by-one, set all OM port modes to automatic.

6

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Total interruption of add/drop traffic during card replacement.

4.15

OMDIFC cards (at OADM100N) Replacement instructions 1

If it is desired to preserve express traffic, disable APRM on the pre-amplifier connected to the failed OMD card. See chapter 4.45 for instructions.

2

If a TSC card is present (connected to the card being replaced), right-click on the TSC card replica and select Card > Configuration. On the resulting TSC “Card Configuration” window, disable Transient Suppression. Wait until the Transient Suppression Laser State changes to “disabled”. This may take a few minutes. Then, refresh the Card > Configuration window and verify that all laser currents are displayed as “0”.

3

One-by-one, set all OM port modes to disabled.

4

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

5

Disconnect all fibers from the failed card and remove it from the shelf.

6

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect all fibers to the new card.

7

Re-enable Transient Suppression if it was disabled in Step 2. Wait until the Transient Suppression Laser State changes to “enabled”. This may take a few minutes.

8

One-by-one, set all OM port modes to automatic.

9

Re-enable APRM according to the instructions in chapter 4.45.

10 Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE. Impact Total interruption of add/drop traffic during card replacement.

4.16

OMDFC card (when used for sub-band compensation) Replacement instructions 1

Disable the pump stage of the associated OLI card.

2

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

3

Disconnect all fibers from the failed card. Remove the card fully from the shelf.

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

251

Card Replacement Instructions

Troubleshooting Manual (TSMN)

4

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect all fibers to the new card.

5

Re-enable the OLI card’s pump stage.

6

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Total traffic interruption in one direction during card replacement.

4.17

OPAPC card Replacement instructions 1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Disconnect all fibers from the failed card.

3

Remove the failed card from the shelf.

4

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect all fibers to the new card.

5

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact No OPA-related functions are possible during card replacement.

4.18

OSCTUT, OSCTUI cards Replacement instructions

252

1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Disconnect all fibers from the failed card.

3

Remove the failed card from the shelf.

4

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect all fibers to the new card.

5

Ensure that there were no fiber cable mistakes. To verify proper cable connections, check the Trail Trace Identifiers.

6

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

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

Troubleshooting Manual (TSMN)

Card Replacement Instructions

Impact Loss of Optical Supervisory Channel during card replacement. Important: if your system uses Raman Amplifier cards, note that removing an OSCT card will disable Raman amplification. The OSCT controls DCMs and other passive cards. If an OSCT card is removed from the shelf for replacement, Card Missing (CMISS) and Card Mismatch (CMISM) alarms will be raised by any passive cards that are installed. Ignore these alarms since these passive cards are not really missing. The alarms will clear when the replacement OSCT is installed.

!

4.19

Danger! Incorrect fiber connections to/from the OSCT (i.e., mixing up the input and output) may cause laser safety problems. After OSCT replacement, check the Trail Trace Identifiers (TTI) to ensure that fibers are connected properly.

PUMP cards Replacement instructions 1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Withdraw the failed card from the shelf a short distance.

3

Disconnect the fiber from the failed card (the fiber pigtail from the OLI card).

4

Remove the failed card from the shelf.

5

Insert the replacement card a short distance into its slot. Do not fully insert it yet.

6

Clean the fiber pigtail from the OLI card, then re-connect it to the replacement PUMP card.

7

Insert the replacement PUMP card fully into the shelf.

8

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Bit errors may occur during card replacement since the required output power cannot be reached with a missing/failed PUMP card.

4.20

PQMC card Replacement instructions 1

Log-in as a Power User. To do so, type Ctrl-Alt-P and PowerOn! password.

2

Identify the Line Booster OLI in the affected ADU sub-agent; it will be in Shelf 0, Slot 013 - in the same shelf that contains the failed PQMC card. Disable the pump laser on this OLI card. To do so, right-click on its card replica and select Card > Configuration. On the resulting OLI “Card Configuration” window, uncheck the Pump Enable checkbox.

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

253

Card Replacement Instructions

Troubleshooting Manual (TSMN)

3

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

4

Withdraw the failed card from the shelf a short distance. Disconnect the fibers from the failed card.

5

Remove the failed card fully from the shelf.

6

Insert the replacement card a short distance into the shelf. Do not fully insert it.

7

Clean all fiber ends and re-connect all fibers to the new card.

8

Fully insert the replacement card into the shelf.

9

Re-enable the pump laser of the OLI card that was disabled in Step 2.

10 There is a small chance the new PQMC card could have a hardware fault. Open the “Card-Config” window for the newly-installed PQMC card. Check the “Current Attenuation” value listed for each channel. If the attenuation settings have “gone flat”, then the new card may have the hardware fault. • •

If the Current Attenuation for every channel is listed as 0 dB, then the card has the hardware fault. Check the field on this same window named “Mean Attenuation of PQM”. If the Current Attenuation for every channel is 2 x “Mean Attenuation of PQM”, then the card has the hardware fault. Example: “Mean Attenuation of PQM” is listed as 2.5 dB. If the Current Attenuation for every channel is listed as 5 dB, then the card has the hardware fault.

If either of the above conditions proves the card has the hardware fault, repeat all previous steps to remove this PQMC card from the shelf and install another spare card. The card with the hardware fault must be returned to Nokia Siemens Networks for repair. If the new card does not have the hardware fault, continue to step 11. 11 Log-off as Power User. To do so, type Ctrl-Alt-P, then click the Close button. 12 Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE. Impact Total loss of the express and add traffic passing through the associated OLI Booster Amplifier during card replacement.

4.21

RPUMPC card Replacement instructions

254

1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Withdraw the failed card from the shelf a short distance.

3

Disconnect the fibers from the failed card.

4

Remove the failed card from the shelf.

5

Insert the replacement card a short distance into its slot. Do not fully insert it yet.

6

Clean all fiber ends and re-connect all fibers to the new card.

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

Troubleshooting Manual (TSMN)

Card Replacement Instructions

7

Insert the replacement RPUMPC card fully into the shelf.

8

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Loss of traffic during card replacement.

4.22

SMU card Replacement instructions 1

Remove the failed card from the shelf.

2

Insert the replacement card fully into the shelf.

3

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Loss of management capability to the shelf containing the failed SMU during card replacement. Also, loss of management capability of all passive cards in the shelf during SMU replacement since they are locally managed by the SMU.

4.23

TSC card Replacement instructions 1

Right-click on the TSC card replica and select Card > Configuration. On the resulting TSC “Card Configuration” window, disable Transient Suppression. Wait until the Transient Suppression Laser State changes to “disabled”. This may take a few minutes. Then, refresh the Card > Configuration window and verify that all laser currents are displayed as “0”.

2

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

3

Disconnect the fiber from the TSC card “Out” port first. Then, disconnect the fiber from the card’s “MonIn” port.

4

Remove the failed card from the shelf.

5

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect the fiber to the “MonIn” port first. Then, re-connect the fiber to the “Out” port.

6

Wait for the card to come up and light its green OK LED.

7

Re-enable Transient Suppression via the Card > Configuration window. Wait until the Transient Suppression Laser State changes to “enabled”. This may take a few minutes.

8

Right-click on this NE’s OPAPC card replica and select OCh Monitor Points ... > Measurement ... The”OPAPC - OCh Monitor Points - MEqasure” window will open and display the list of available channels. Verify that all Transient Suppression channels are available. These channels are:

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

255

Card Replacement Instructions

– – – – 9

Troubleshooting Manual (TSMN)

196.1 THz 193.95 THz 193.85 THz 191.6 THz

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Loss of transient suppression capabaility during card replacement.

4.24

UDCM Replacement instructions 1

If the UDCM is being used for 40G single-channel pre- or post-compensation, skip steps 2 and 3, and go directly to step 4. Otherwise, continue to step 2.

2

Log-in as a Power User. To do so, type Ctrl-Alt-P and PowerOn! password.

3

Identify the OLI connected to the failed UDCM. Disable the pump laser on this OLI card. To do so, right-click on its card replica and select Card > Configuration. On the resulting OLI “Card Configuration” window, uncheck the Pump Enable checkbox.

4

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

5

Withdraw the failed card from the shelf a short distance. Disconnect the fibers from the failed card.

6

Remove the failed card fully from the shelf.

7

Insert the replacement card a short distance into the shelf. Do not fully insert it.

8

Clean all fiber ends and re-connect all fibers to the new card.

9

Fully insert the replacement card into the shelf.

10 If step 3 was performed, re-enable the pump laser of the OLI card. Log-off as Power User. To do so, type Ctrl-Alt-P, then click the Close button. 11 In some situations (example: sub-band compensation is used), it may be necessary to configure the delay of DCF. Refer to the chapter entitled “Configuring Delay of DCF” in the hiT 7500 Optical Link Commissioning (OLC) Manual to determine if it is necesary to perform this procedure. 12 Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE. Impact Total loss of traffic passing through the UDCM during card replacement.

256

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

Troubleshooting Manual (TSMN)

4.25

Card Replacement Instructions

UDCM Tray Before replacing a UDCM tray, verify that the actual failure is the tray - not one of the UDCMs housed in the tray. A failure of the tray is typically indicated by the inability to retrieve inventory data from any of the UDCMs in the tray. However, if inventory data can be retrieved from one of the DCM modules but not from the other, it is more likely that an individual UDCM module has failed - not the tray. The complete DCM tray can be replaced from the front without interrupting traffic by following the steps below. Rear access is not required to replace the DCM tray.

!

Warning! Do not bend, squeeze, or otherwise damage the optical fibers during this procedure.

Replacement instructions 1

Locate the defective DCM tray. The DCM tray is usually mounted at the bottom of the optical equipment bay.

2

Carefully uncover all optical fibers that lead to/from the DCM tray from the vertical plastic fiber duct without disconnecting or straining any of the optical connectors or fibers. Make sure that all fibers leading to/from the DCM tray are completely loose.

3

Place a lab trolley or sturdy box close to the DCM Tray. The top surface of the trolley or box must be approximately the same height as the DCM tray mounted in the bay and must be large enough to accommodate both UDCM modules. Caution: Make sure the fibers connected to the UDCM modules have enough slack to permit placing the modules onto the trolley/box.

4

Remove one UDCM module at a time from the faulty DCM tray and carefully place it on the trolley/box without straining or bending the fibers excessively.

5

Remove the Air Filter from this shelf - the Air Filter is located immediately above the shelf's Connector Panel (COPA). Doing so provides better access to the COPA.

6

The DCM tray is connected via cable (SPI bus cable) to the shelf that contains the MCU card. Disconnect the SPI bus cable from the COPA.

7

Remove the SPI bus cable from the cable duct of the bay until it is completely loose.

8

Unscrew the DCM tray's grounding cable - it is attached to the right-hand rack upright.

9

Carefully remove the four screws that attach the DCM tray to the rack (two each side). While loosening the screws, make sure to hold the DCM tray in place with your other hand. Note: if the mounting bracket of a bay end-guard is obstructing the direct removal of the faulty DCM tray, move the tray to the left or right (away from the bay end guard) until the tray's mounting flanges are free.

10 Lift the faulty DCM tray carefully out of the bay and prepare it for the return and repair process. Mark it with a "defective" label and attach a short failure description. 11 Unpack the new DCM tray and SPI cable. Do not fasten the cable to the tray yet. 12 Carefully route the SPI bus cable from the bottom of the bay, behind the mounting flanges, up and connect it to the SPI1 connector of the COPA. Note: due to tight access, you may want to use a pull cord to get the SPI DB15 connector from the bottom of the bay in to the COPA entry. 13 Fasten the SPI cable to the new DCM tray.

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

257

Card Replacement Instructions

Troubleshooting Manual (TSMN)

14 Roll up (and secure) the excess SPI bus cable and store it behind the mounting brackets. Place the new DCM tray in the same location in the rack as the one removed. 15 Align the mounting holes of the DCM tray with the ones of the rack beams. Hold the tray in place with one hand and attach the new tray to the rack with the four mounting screws that were removed in Step 9. 16 Attach the tray's grounding cable to the same hole in the rack upright. Use the same screw and lockwasher that were removed in Step 8. 17 Replace the Air Filter in the optical shelf. 18 Carefully place the UDCM modules into the new DCM tray without straining or bending the fibers excessively. 19 Carefully slide the optical fibers back into the vertical fiber duct and place the slack in the Fiber Storage area. Caution: do not disconnect any optical fiber! Ensure fibers are not squeezed, strained, or bent beyond the minimum allowed bend radius. 20 Verify operational status via the Craft Interface: – – –

4.26

No alarms should be raised. All UDCM modules can be "configured" via the Craft Interface. Inventory data from both UDCM modules can be retrieved. Prepare the failed tray for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”PROCEDURE COMPLETE.

VOA2 card Replacement instructions 1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

How is the failed VOA2 card being used? – –

258

Positioned as an OLI card interstage device or used for line padding: go to step 3. used with a Raman Pump: skip step 3 and go directly to step 4.

3

Determine the upstream terminal (OADM or OTT). Open the “Optical Link Control” window and click the Forced Prestart button to shut down the link.

4

Withdraw the failed VOA2 card from the shelf a short distance.

5

Disconnect all fibers from the failed card.

6

Fully remove the failed card from the shelf.

7

Insert the replacement card fully into the shelf. Clean all fiber ends and re-connect all fibers to the new card.

8

If step 3 was performed, open the upstream terminal’s “Optical Link Control” window and execute Power Equalization and Link Start-up.

9

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

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

Troubleshooting Manual (TSMN)

Card Replacement Instructions

Impact Total traffic interruption during card replacement because of the Forced Prestart and new Link Startup routine.

4.27

WBAN card Replacement instructions 1

To preserve the drop traffic on the partner ADN, Automatic Power Reduction Mode (APRM) for the partner ADN's Pre-amplifier (the OLITPxx card in Shelf 0, Slot 010) can be disabled. To do so, follow the instructions in chapter 4.45. Note: "partner ADN" means the opposing ADN - the one that does not contain the failed WBAN.

2

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

3

Withdraw the failed card from the shelf a short distance. Disconnect the fibers from the failed card.

4

Remove the failed card fully from the shelf.

5

Insert the replacement card a short distance into the shelf. Do not fully insert it.

6

Clean all fiber ends and re-connect all fibers to the new card.

7

Fully insert the replacement card into the shelf.

8

Re-enable APRM on the partner ADN's Pre-amplifier. To do so, follow the instructions in chapter 4.45.

9

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Total loss of the express and add traffic passing through the WBAN during card replacement. Remarks The APRM function on the partner ADN's Pre-amplifier must be disabled to avoid losing those drop channels.

4.28

WBAU card Replacement instructions 1

Log-in as a Power User. To do so, type Ctrl-Alt-P and PowerOn! password.

2

If a TSC is present (connected to the card being replaced), right-click on the TSC card replica and select Card > Configuration. On the resulting TSC “Card Configuration” window, disable Transient Suppression. Wait until the Transient Suppression Laser State changes to “disabled”. This may take a few minutes. Then, refresh the Card > Configuration window and verify that all laser currents are displayed as “0”.

3

Identify the Add-OLI in the affected ADU network element - it will be in Shelf 2, Slot 013 - in the same shelf that contains the failed WBAU card. Disable the pump laser

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

259

Card Replacement Instructions

Troubleshooting Manual (TSMN)

on this OLI card. To do so, right-click on its card replica and select Card > Configuration. On the resulting OLI “Card Configuration” window, uncheck the Pump Enable checkbox. 4

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

5

Withdraw the failed card from the shelf a short distance. Disconnect the fibers from the failed card.

6

Remove the failed card fully from the shelf.

7

Insert the replacement card a short distance into the shelf. Do not fully insert it.

8

Clean all fiber ends and re-connect all fibers to the new card.

9

Fully insert the replacement card into the shelf.

10 Re-enable Transient Suppression if it was disabled in Step 2. Wait until the Transient Suppression Laser State changes to “enabled”. This may take a few minutes. 11 Re-enable the pump laser of the OLI card that was disabled in Step 3. 12 Log-off as Power User. To do so, type Ctrl-Alt-P, then click the Close button. 13 Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE. Impact Total loss of the express and add traffic passing through the WBAU during card replacement.

4.29

WBN card Replacement instructions

260

1

Perform a channel downgrade of each channel passing through the failed WBN. Channel Downgrade instructions can be found in the SURPASS hiT 7500 Operating Manual (OMN).

2

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

3

Disconnect the failed card’s IN fiber first. Then, disconnect the ExpOut fiber.

4

Withdraw the failed card from the shelf.

5

Insert the replacement card fully into the shelf and latch it in place.

6

Clean all fiber ends. Re-connect the ExpOut fiber to the new card first. Then, reconnect the IN fiber.

7

Restore the channels that were downgraded in step 1, i.e., perform a Channel Upgrade on these channels. Channel Upgrade instructions can also be found in the SURPASS hiT 7500 Operating Manual (OMN).

8

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

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

Troubleshooting Manual (TSMN)

Card Replacement Instructions

Impact Total loss of the express traffic passing through the WBN during card replacement.

4.30

WSSC card Replacement instructions 1

If a TSC is present (connected to the card being replaced), right-click on the TSC card replica and select Card > Configuration. On the resulting TSC “Card Configuration” window, disable Transient Suppression. Wait until the Transient Suppression Laser State changes to “disabled”. This may take a few minutes. Then, refresh the Card > Configuration window and verify that all laser currents are displayed as “0”.

2

Perform a channel downgrade of each channel passing through the failed WSSC. Channel Downgrade instructions can be found in the SURPASS hiT 7500 Operating Manual (OMN).

3

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

4

Disconnect the failed card’s IN fibers first, i.e., the fibers connected to the failed card’s In1, In2, In3, In4, and AuxIn ports. Note that, depending on the configuration of the network element, a WSSC card may not have fiber connected to all of these ports.

5

Now, disconnect the ExpOut fiber from the failed card.

6

Withdraw the failed card from the shelf.

7

Insert the replacement card fully into the shelf and latch it in place.

8

Re-connect the ExpOut fiber to the new card first. Then, re-connect all the IN fibers.

9

Restore the channels that were downgraded in step 2, i.e., perform a Channel Upgrade on these channels. Channel Upgrade instructions can also be found in the SURPASS hiT 7500 Operating Manual (OMN).

10 Re-enable Transient Suppression if it was disabled in Step 1. Wait until the Transient Suppression Laser State changes to “enabled”. This may take a few minutes. 11 Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE. Impact Total loss of the express traffic passing through the WSSC during card replacement.

4.31

SFP and XFP modules Replacement instructions 1

If not already present, attach a label to each fiber connected to the failed module (to help ensure that each fiber will be connected to the correct port on the replacement module).

2

Disconnect all fibers from the failed module.

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

261

Card Replacement Instructions

3

SFPs and XFPs used with SURPASS hiT 7500 have one of the following latch mechanisms: –

–

4

Troubleshooting Manual (TSMN)

simple push-in to latch / pull out to unlatch. If this type of module is used, simply grasp it on both sides and pull it free from the card. If access space is tight, try carefully using a small screwdriver to lift the module for removal. a bale-type clasp that swings to locked and unlocked positions. If this type of module is used, carefully open the bale clasp, then grasp the module on both sides and pull it free of the card. If access space is tight, you can pull directly on the clasp to remove the module.

Slide the replacement module into the card's port as follows: – –

If the module does not feature a bale clasp, simply grasp it on both sides and push it gently into the port until it snaps into place. If the module features a bale-type clasp, make sure the clasp is open. Grasp the module on both side and gently push it fully into the port. Then, swing the locking clasp shut.

5

Remove any protective plugs present on the module. Clean fiber ends and reconnect all fibers to the new module.

6

Verify that all alarms are cleared. Prepare the failed module for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Traffic interruption during replacement for the channel(s) served by the failed module.

4.32

OTS-4400, OTS-40xx cards Replacement instructions

262

1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Disconnect all fibers from the failed card. See the Warning below about any external attenuator which may be present.

3

Remove the failed card from the shelf.

4

Insert the replacement card into the shelf. Clean fiber ends and re-connect all fibers to the new card. The card will be displayed in orange color during initialization on the Element Manager Module View. Important: never unplug the card during its first initialization period, which can take 20 minutes or more.

5

Note that replacement of these card types can sometimes cause an intermittent CFAIL alarm. Important: do not Warm Start or Cold Start the card until the CFAIL alarm totally clears, which can require 20 to 30 minutes. If the CFAIL alarm has not cleared after 30 minutes, Cold Start the card. Then, wait 20 more minutes for the card to recover from the Cold Start.

6

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

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

Troubleshooting Manual (TSMN)

Card Replacement Instructions

Impact Traffic interruption during card replacement for the channel(s) served by the failed card.

!

Warning! Note that there are two generations of 40G transponder and regenerator cards. Firstgeneration cards often required installation of an external attenuator (or external attenuating patchcord) for the Line Tx port. Second-generation cards have internal (built-in) attenuation, which negates the needs for the external attenuation. So, card replacement rules are as follows: –

–

–

See Table 11 below. When replacing a failed OTS-4040, OTS-4400, or OTS-4011, check the part number of the failed card and the replacement card. Determine if the cards are first-generation or second-generation. If the failed card and the replacement card are both first-generation, replicate the use of any external attenuation. In other words, if the failed card used an external attenuator, re-install the same attenuator with the new card. Conversely, if the failed card did not use an external attenuator, do not use one with the new card. If the failed card is first-generation, but the new card is second-generation, do NOT re-use any external attenuator. Connect fiber to the replacement card without any external attenuator.

First-generation cards Type

Part number

OTS-4040

S42024-Z5908-A100

OTS-4400

S42024-Z5909-A100

OTS-4011

S42024-Z5926-A100

Remarks

External attenuation often needed with these card types.

Second-generation cards OTS-4040-02

S42024-Z5962-A100

OTS-4400-02

S42024-Z5964-A100

OTS-4011-02

S42024-Z5960-A100

OTS-4040-04

S42024-Z5963-A100

OTS-4400-04

S42024-Z5965-A100

OTS-4011-04

S42024-Z5961-A100

Table 11

4.33

External attenuation not needed with these card types.

External attenuation not needed with these card types.

First- and Second-generation 40G Cards

OTS-4520 card Replacement instructions 1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Withdraw the Optical Module Carrier (OMC) chassis containing the failed OTS-4520 card a short distance from the shelf.

3

Disconnect all fibers from the failed OTS-4520.

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

263

Card Replacement Instructions

Troubleshooting Manual (TSMN)

4

Remove the failed OTS-4520 from the OMC (keeping the OMC loosely in its shelf slot).

5

Insert the replacement card into the OMC. Do not re-insert the OMC into its backplane connector yet. Clean all fiber ends and re-connect all fibers to the new card.

6

Now, fully insert the OMC into the shelf, latch it into place, and tighten the thumbscrews.

7

Note that replacement of these card types can sometimes cause an intermittent CFAIL alarm. Important: do not Warm Start or Cold Start the card until the CFAIL alarm totally clears, which can require 20 to 30 minutes. If the CFAIL alarm has not cleared after 30 minutes, Cold Start the card. Then, wait 20 more minutes for the card to recover from the Cold Start.

8

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Total loss of traffic passing through the OTS-4520 during card replacement.

4.34

OTS-4540 card Replacement instructions 1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Withdraw the Optical Module Carrier (OMC) chassis containing the failed OTS-4540 card a short distance from the shelf.

3

Disconnect all fibers from the failed OTS-4540.

4

Remove the failed OTS-4540 from the OMC (keeping the OMC loosely in its shelf slot).

5

Insert the replacement card into the OMC. Do not re-insert the OMC into its backplane connector yet. Clean all fiber ends and re-connect all fibers to the new card.

6

Now, fully insert the OMC into the shelf, latch it into place, and tighten the thumbscrews.

7

Note that replacement of these card types can sometimes cause an intermittent CFAIL alarm. Important: do not Warm Start or Cold Start the card until the CFAIL alarm totally clears, which can require 20 to 30 minutes. If the CFAIL alarm has not cleared after 30 minutes, Cold Start the card. Then, wait 20 more minutes for the card to recover from the Cold Start.

8

Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Impact Total loss of traffic passing through the OTS-4540 during card replacement.

264

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

Troubleshooting Manual (TSMN)

4.35

Card Replacement Instructions

OTS-4700 Controller card Replacement instructions 1

Remove the failed OTS-4700 Controller card from the shelf.

2

Fully insert the new OTS-4700 Controller card into the shelf, but do NOT connect the Ethernet cable to the MGMT port of the new OTS-4700 card.

3

Connect your laptop computer to the Craft interface of the OTS-4700 card via an RS-232 serial cable (Molex COMM-D, 9 SKT/D-SUB cable, delivered with the OTS4700). Log-on to the computer as an Administrator.

4

Select Start -> Programs ->Accessories -> Communications -> Hyperterminal to create a new hyperterminal session.

5

On the resulting Connection Description window, enter a name for the connection, e.g., OTS-4700.

6

Select COM1 or COM2 as the communication interface in the Connect Using field, and then click OK. (Select COM1 or COM2 depending on your laptop's setup).

7

On the resulting COM(x) properties window, configure the communication interface as follows: – – – – –

8

Log-on the OTS-4700 controller with the default factory user id and password: – –

9

Bits per second: 9600 Data bits: 8 Parity: None Stop Bits: 1 Flow Control: None. OTS-4000 log-in: diag Password: stratalight

Go to the following step, based upon your network’s configuration strategy: – – – –

For automatic IP Configuration with your DCN Plan available, proceed to step 10. For manual IP Configuration with your DCN Plan available, skip steps 10 through 12. Go directly to step 13. If your DCN Plan is not available, skip steps 10 and 11. Go directly to step 12. For additional information, refer to the hiT 7500 Operating Manual (OMN), chapters 5.8.1.2 and 5.8.1.6.

10 Set the OTS-4700 IP configuration according to your DCN plan with the following command: – –

diag@StrataLight:~$ set ipconfig where is the NE-ID of the Compound NE, is the subsystem ID of the OCU40 subagent, and is the shelf number of the corresponding OTS-4000 shelf. All parameters can be found in your DCN plan.

11 Skip steps 12 through 14. Go directly to step 15. 12 If the OTS-4700 is being replaced due to a communications problem with the OCU40 subsystem, and your DCN Plan is not available, determine the necessary values as follows. –

the IP address of the OCU40 Ethernet southbound (NEMA) interface and subnet mask can be determined from the IP Address - Config window. To access this window, go to the Element Manager Main Menu and select Commu-

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

265

Card Replacement Instructions

–

Troubleshooting Manual (TSMN)

nications -> TCP/IP -> IP addresses. On the resulting list, find the OCU40 that has the communication problem with the defective OTS-4700. Its IP Address and Subnet Mask will be listed on the window. the IP Address of the OTS-4700 card can be determined as follows: the first three blocks of the address are identical to the IP address of the OCU40 Ethernet southbound (NEMA) interface. The last block can be determined from the table below. Example: for OTS-4000 Shelf 3 in Subsystem OCU46, the last block of the OTS-4700 IP address is 167. Last Block of OTS-4700 IP Address

Subsystem Shelf 1

Shelf 2

Shelf 3

Shelf 4

Shelf 5

Shelf 6

Shelf 7

Shelf 8

Shelf 9

42

174

175

176

177

178

179

180

181

182

43

183

184

185

186

187

188

189

190

191

44

192

193

194

195

196

197

198

199

200

45

156

157

158

159

160

161

162

163

164

46

165

166

167

168

169

170

171

172

173

47

129

130

131

132

133

134

135

136

137

48

138

139

140

141

142

143

144

145

146

49

147

148

149

150

151

152

153

154

155

Table 12

Last Block of OTS-4700 IP Address 13 Set the OTS-4700 IP configuration with the following command: – –

diag@StrataLight:~$ set ip eth0 where is the IP address of the OTS-4700 card, is theIP address of the OCU40 Ethernet southbound (NEMA) interface, and is the subnet mask. All parameters can be found in your DCN plan, or as determined in step 12.

14 Set the IP-port configuration with the following command: – –

diag@StrataLight:~$ set mgmtport xml enabled where is the IP address of the OCU40 Ethernet southbound (NEMA) interface, is 57001 and is 57002.

15 When the message “settings applied” appears in the Terminal window, confirm them with the following command: diag@StrataLight:~$ show mgmtport 16 Connect the Ethernet cable to the MGMT port of the OTS-4700 and type reboot. 17 If the OTS-4700 automatically reboots, wait a few minutes for the process to complete. Once completed, the CLOSSOTS alarm should change to a SYNCPROG alarm which will self-clear when the synchronization process is complete. 18 Confirm the configurations with the following commands: – –

diag@StrataLight:~$ show ip diag@StrataLight:~$ show mgmtport

19 Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

266

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

Troubleshooting Manual (TSMN)

4.36

Card Replacement Instructions

OTS-4000 Air Filter The Air Filter Assembly of the OTS-4000 shelf consists of a metal cage and the replaceable air filter element.

!

Warning! Inspect the OTS-4000 Air Filter every 3 months. The filter element must be replaced at least every 12 months, or more often if contaminant levels warrant.

Replacement instructions 1

Refer to Figure 42. Loosen the thumbscrew on each side of the Air Filter Assembly and remove the assembly from the shelf.

2

Slide the filter element out of the metal frame as shown in Figure 43. Clean the metal frame with a soft cloth. Insert the new filter element into the frame.

3

Re-install the Air Filter Assembly into the shelf. Tighten the thumbscrews to hold it securely in place.

Figure 42

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

How to remove the OTS-4000 air filter assembly

267

Card Replacement Instructions

Figure 43

4.37

Troubleshooting Manual (TSMN)

How to remove the OTS-4000 air filter element

MTS Shelf If it is necessary to return an entire shelf for repair or replacement, follow the instructions below before preparing the shelf for shipment.

g It is assumed that all fibers, electrical cables, plug-in cards, and blank filler panels have already been removed from the faulty shelf and that the replacement shelf is on-site, ready to be installed. Replacement instructions

268

1

Remove the MIBS circuit board from the failed shelf - it will be installed in the new shelf.

2

Determine the type of Subrack Address Board in the failed shelf. If the failed shelf has an SABM circuit board, remove it. If the failed shelf has an SAB circuit board, let it remain in the shelf.

3

If the failed shelf is equipped with an FSU (Flow Sensor Unit), remove it according to the instructions in chapter 4.3.

4

Prepare the new shelf. All new MTS shelves are delivered with a pre-installed SAB. If the shelf requires an SAB, use the one that comes pre-installed. However, if the shelf requires an SABM, remove the pre-installed SAB and install the SABM that was removed from the failed shelf in Step 2. [Put the unneeded SAB into the failed shelf for return to Nokia Siemens Networks].

5

Install the FSU that was removed in Step 3 into the new shelf.

6

Remove the failed shelf from the rack. Install the new shelf according to all instructions in the SURPASS hiT 7500 Installation Manual (ITMN), including replacing all the previously-removed plug-in cards, fibers, and electrical cables. Be sure to install the MIB that was removed from the failed shelf in Step 1 into the new shelf. Also, ensure that the same MCU that was removed from the failed shelf is installed into the new shelf.

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

Troubleshooting Manual (TSMN)

4.38

Card Replacement Instructions

7

Power-up the new shelf according to the instructions in the ITMN.

8

Prepare the failed shelf for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”.

OCU Shelf If it is necessary to return an entire shelf for repair or replacement, follow the instructions below before preparing the shelf for shipment.

g It is assumed that all fibers, electrical cables, plug-in cards, and blank filler panels have already been removed from the faulty shelf and that the replacement shelf is on-site, ready to be installed. Replacement instructions 1

!

Remove both MIBS circuit boards from the failed shelf - they will be installed in the new shelf.

Caution! Always clearly label each removed MIBS board and the MCU card that it serves so they can be re-installed together again in the new shelf. If an OCU shelf contains two MCU cards (MCU-OCU and either MCU-Q3GNE or MCU-OCU40), the shelf will also contain two MIBS boards. Label each MIBS and MCU so they can be re-installed into the replacement shelf exactly as before.

2

If the failed shelf is equipped with an FSU (Flow Sensor Unit), remove it according to the instructions in chapter 4.3.

3

Prepare the new shelf. All new OCU shelves are delivered with a pre-installed MIBS for the MCU-OCU in Slot 17. Remove it and place it in the failed shelf for return to Nokia Siemens Networks.

4

Install the FSU that was removed in Step 3 into the new shelf.

5

Remove the failed shelf from the rack. Install the new shelf according to all instructions in the SURPASS hiT 7500 Installation Manual (ITMN), including replacing all the previously-removed plug-in cards, fibers, and electrical cables. Be sure to install both MIBS boards that were removed from the failed shelf in Step 1 into the new shelf. Also, ensure that the same MCUs that were removed from the failed shelf are installed into the new shelf.

6

Power-up the new shelf according to the instructions in the ITMN.

7

Prepare the failed shelf for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”.

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

269

Card Replacement Instructions

4.39

Troubleshooting Manual (TSMN)

CCEP card Replacement instructions 1

4.40

The CCEP card is newly supported for hiT 7500 Release 3.21.10. For replacement instructions, follow the procedure for the CCMP card in chapter 4.40.

CCMP card CCMP replacement requires special care since these cards contain a field-replaceable Compact Flash (CF) module used for persistent storage of the MIB and APS software. Card replacement procedures vary, depending on the failure scenario (as indicated by different alarms). These different scenarios are as follows: • • •

4.40.1

CCMP replacement due to CP alarm CCMP replacement due to MIBF alarm CCMP replacement due to Loss of Communication to NE

CCMP replacement due to CP alarm A CP (Card Problem) alarm raised by a CCMP card indicates that the card has suffered an internal fault, but the on-board Compact Flash module is still OK. Since the Compact Flash module contains the MIB and APS software, it must be physically transferred to the replacement card. Detailed instructions are as follows: Replacement instructions

4.40.2

1

IMPORTANT! Back-up the contents of the failed card’s MIB. Instructions for doing so are in the hiT 7500 Operating Manual (OMN).

2

Change the Administrative State of the failed card to “locked”.

3

If not already present, attach a label to each Ethernet, Orderwire, or Telemetry Interface cable that may be connected to the failed card (to help ensure that each cable will be connected to the correct port on the replacement card). Then, disconnect all cables from the failed card and remove the failed card from the shelf.

4

Remove the Compact Flash module from the failed card. Install it onto the new card.

5

Insert the new card into the shelf. Re-connect all cables. The card will automatically boot using the MIB contents of the Compact Flash module. Verify that the green OK LED on the card front panel lights, indicating a successful re-boot. If boot-up does not occur within 15 minutes, withdraw the card from the shelf and re-insert it. If bootup still does not occur within 15 minutes, stop. Contact your next higher level of technical support. If boot-up is successful, continue to the next step.

6

Re-connect to the NE over the Q or QF interface. Change the Administrative State of the new card to "unlocked". Verify that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

CCMP replacement due to MIBF alarm A network element’s MIB contents are persistently stored in two areas on the CCMP card; the on-board flash, and the replaceable Compact Flash module. A MIBF alarm indicates that both these storage areas have failed. The NE can still function normally via the working copy of the MIB residing on the PRAM. However, if the failed card is Cold

270

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

Troubleshooting Manual (TSMN)

Card Replacement Instructions

Started, the PRAM copy of the MIB will be lost, and the NE will not be able to recover to the state prior to the Cold Start. Hence, when a MIBF alarm is raised, immediately make a back-up copy of the MIB, and dispatch service personnel to replace the failed Controller card and its Compact Flash module, i.e., it is necessary to take a spare Controller card and a spare Compact Flash module to the site. Detailed instructions are as follows: Replacement instructions 1

IMPORTANT! Back-up the contents of the failed card’s MIB. Instructions for doing so are in the hiT 7500 Operating Manual (OMN).

2

If not already present, attach a label to each Ethernet, Orderwire, or Telemetry Interface cable that may be connected to the failed card (to help ensure that each cable will be connected to the correct port on the replacement card). Then, disconnect all cables from the failed card and remove the failed card from the shelf.

3

Install the replacement Compact Flash module onto the new card.

4

Insert the new card into the shelf. Re-connect all cables. Various automatic procedures will now be executed by the system in an attempt to get everything synchronized. The entire process may require up to 20 minutes to complete. – –

5

4.40.3

If the NE goes to recovery mode and an APSM alarm is raised, stop. Go to thetroubleshooting instructions for the APSM alarm. If the process completes successfully (indicated by the Controller card lighting its front-panel green OK LED, continue to step 5.

Download the back-up copy of the MIB (made in step 1) to the NE. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. Verify that all alarms are cleared. PROCEDURE COMPLETE.

CCMP replacement due to Loss of Communication There are cases in which the failure of a CCMP card is of such a nature that it affects the ability of the card (or the card’s software) to report its own failure, or even its ability to communicate with other devices such as the network management system. In such cases, the failure likely is detected by the Element Management System as a “loss of communications” to the network element. In such a case, a replacement of the relevant Controller card is warranted. Detailed instructions are as follows: Replacement instructions 1

If the network management system reports a Loss of Communication to an NE, dispatch service personnel to that site with a spare CCMP and a spare Compact Flash module. (It is impossible to know at this point whether the loss of communication was caused by a failed Controller card or a failure of its Compact Flash. So take both to the site to avoid making a second trip).

2

First, assume the problem is a faulty Controller card. Perform the procedures in chapter 4.40.1 “CCMP replacement due to CP alarm”.

3

If the problem persists, assume the problem is a Compact Flash failure. Perform the procedures in chapter 4.41 “Compact Flash Replacement”.

4

If the problem persists, assume there is a failure of the Controller card and the Compact Flash, which is equivalent to a MIBF condition. Perform the procedures in chapter 4.40.2 “CCMP replacement due to MIBF alarm”.

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

271

Card Replacement Instructions

5

4.41

Troubleshooting Manual (TSMN)

If the problem persists, contact your next higher level of technical support. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

Compact Flash Replacement Each CCEP and CCMP controller card contains a Compact Flash module. The Compact Flash module is used for persistent storage of the MIB and APS software. If the Compact Flash fails (indicated by the CFF alarm), the correct APS and the working MIB contents must be restored onto the replacement Compact Flash module (which should occur automatically). Detailed instructions are as follows: Replacement instructions 1

IMPORTANT! Back-up the contents of the NE’s MIB. Instructions for doing so are in the hiT 7500 Operating Manual (OMN).

2

Change the Administrative State of the Controller card that contains the failed Compact Flash to "locked". Then, remove this Controller card from the shelf.

3

Remove the failed Compact Flash from the Controller card. Install the replacement Compact Flash. Figure 44 shows the location of the Compact Flash and how to remove and re-insert it. After installing the new Compact Flash, be sure to rotate the hinged arm of the ejector button back to its folded position. Otherwise, the ejector button can be broken when the Controller card is re-inserted into the shelf.

4

Insert the new Controller card (with new Compact Flash) into the shelf. Various automatic procedures will now be executed by the system in an attempt to get the correct APS and MIB onto the new Compact Flash, synchronized with the Controller card software. The entire process may require up to 20 minutes to complete. – – –

5

272

If the MIBF alarm is raised, stop. Go to the troubleshooting instructions for the MIBF alarm in chapter 3.1.79. If the APSM alarm is raised, stop. Go to the troubleshooting instructions for the APSM alarm. If the process completes successfully (indicated by the Controller card lighting its front-panel green OK LED), continue to step 5.

Re-connect to the NE over the Q or QF interface. Change the Administrative State of the Controller card to "unlocked". PROCEDURE COMPLETE.

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

Troubleshooting Manual (TSMN)

Figure 44

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

Card Replacement Instructions

How to remove/re-insert the Compact Flash on CCEP and CCMP cards

273

Card Replacement Instructions

4.42

Troubleshooting Manual (TSMN)

CCSP card The CCSP does not contain any MIB data or APS. Therefore, replacement procedures are very simple as follows: Replacement instructions

4.43

1

Remove the failed CCSP from the shelf.

2

Insert the replacement CCSP into the shelf. Normal operation will automatically resume. Verify that all alarms are cleared and that the green OK LED on the CCSP front panel lights. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

HDS Transponder cards It is assumed that a Transponder card has suffered an on-board fault and that any SFP or XFP modules installed on the card are OK. Detailed Transponder replacement instructions are as follows: Replacement instructions

4.44

1

If not already present, attach a label to each fiber connected to the failed card (to help ensure that each fiber will be connected to the correct port on the replacement card).

2

Disconnect all fibers from the failed Transponder card. Remove any SFP or XFP modules present on this Transponder, noting carefully which module was installed in which port.

3

Remove the failed transponder card from the shelf.

4

Insert the new Transponder into the shelf. Re-install all SFP/XFP modules in their same positions. Clean fiber ends and re-attach all fibers to the new card. The transponder will execute its normal boot-up sequence and be restored with correct provisioning information. Full recovery time will require 5 minutes or less.

5

Verify that the new Transponder lights its front-panel OK LED and that all alarms are cleared. Prepare the failed card for return to Nokia Siemens Networks as described in chapter 10 “Packing equipment for return”. PROCEDURE COMPLETE.

HDS Shelf Air Filter The air filter element is mounted inside the HDS shelf’s Fan Unit. So, it is necessary to remove the Fan Unit from the shelf to replace the air filter.

!

Warning! Do NOT remove a Fan Unit unless the replacement air filter is readily at hand. There is only one Fan Unit in each HDS shelf. So, when a shelf’s Fan Unit is removed, there is no forced-airflow cooling. Therefore, perform all steps in the procedure below as quickly as possible to minimize the time the shelf is without a Fan Unit.

1

274

Open the latches of the Fan Unit. Carefully slide the Fan Unit a short distance out on its mounting rails. Wait for all fans to stop spinning. Note: FAN_MAJOR and

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

Troubleshooting Manual (TSMN)

Card Replacement Instructions

FAN_MINOR alarms will be generated when the Fan Unit is removed. Ignore these alarms; they will clear when the Fan Unit is re-installed. 2

Now, remove the Fan Unit completely from the shelf. Carefully place it on a surface (workbench, table) suitable for this work.

3

The filter element is contained in a dedicated cavity in the Fan Unit as shown in Figure 45. Slide the filter out of its housing. Wipe the entire Fan Unit clean with a soft cloth to remove any dust that may have accumulated.

4

Install the new filter element in the Fan Unit. One side of the filter will have the manufacturer’s logo printed on it - this is the filter’s higher-density side. Make sure the filter is installed with that side up (closest to the fans).

5

Re-install the Fan Unit in the shelf and latch it in place. Verify that the fans are running again and the Fan Alarm LED on the Fan Unit is off. Verify that the all alarms have cleared. Discard the old filter. PROCEDURE COMPLETE.

Figure 45

4.45

HDS Shelf Fan Unit and Air Filter

How to enable/disable APRM Follow the instructions below to temporarily disable/enable APRM (Automatic Power Reduction Mode).

g You must be User Class 10 to disable/enable APRM. !

Danger! If APRM is disabled, proper laser safety procedure must be followed. The output power at the Out port of the CDN card can be up to 22 dBm. The output power at the DrOut port of the CDN card can be up to 25 dBm.

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

275

Card Replacement Instructions

Troubleshooting Manual (TSMN)

Disabling APRM 1

Open the Element Manager Equipment View. Locate the card replica of the desired Pre-amplifier OLI card. Right-click on this card replica and select Card > Configuration.

2

On the resulting “Card Configuration” window, right-click the "Automatic Power Shutdown" button. Note that this button is normally grayed out. The button is available only in Power User mode. To get to Power User mode, type: Ctrl-Alt-P and the PowerOn! password.

3

On the resulting “Automatic Power Shutdown” window, enter the desired disable time (in minutes) in the Disable Time field. Click the Apply button.

4

Click the Disable Automatic Power Shutdown button. A countdown display will show the number of APRM-disabled minutes remaining.

5

To log-out from this window, type Ctrl-Alt-P, then click Close to leave Power User mode. If the APRM disable time needs to be extended, repeat the above procedure anytime before the timer expires.

6

Disconnect the fiber at the OMDIFC's "2C' port. Clean the fiber and measure the power being delivered to the end of this fiber. Is the measured power approximately 2 dB less than the OLI Stage III output power from step 2? (Allow a tolerance of +/1.5 dB).

g When APRM is disabled on a Pre-amplifier OLI card, that card’s green OK LED will flash. Re-enabling APRM 1

276

To re-enable APRM, follow the same steps above, but set the Disable Time to 0, and then press the Disable Automatic Power Shutdown button. Alternatively, you can simply let the original disable time expire, after which APRM will be automatically reenabled.

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

Troubleshooting Manual (TSMN)

Cold Start and Warm Start

5 Cold Start and Warm Start Many troubleshooting procedures covered in this document call for a Warm Start or Cold Start to be executed on a plug-in card raising an alarm. This chapter provides a complete description of these features.

5.1

Differences between Warm and Cold Start Via the craft terminal, the user can command individual plug-in cards to execute a Warm Start or Cold Start. The differences are explained in Table 13. Note the following: •

• • •

The NE State must be "active" in order to execute a Warm Start or Cold Start on any plug-in card. The current NE State is displayed in the Status Bar at the bottom of the Element Manager Main Window. For MCU cards, only Cold Start is possible. Plugging a card into the shelf will automatically cause a Cold Start of that card. After swapping the APS software during an APS Download procedure, a Cold Start of the MCU will be automatically triggered, and a Warm Start of all other cards managed by this MCU will also be automatically triggered. Warm Start

5.2

Cold Start

Possible on:

All cards except MCU, OMDxx, CDN, CDAN, CDU, and DCM.

All cards except OMDxx, CDN, CDAN, CDU, and DCM.

How to perform:

Right-click on the desired Card Replica in the Module View or Navigation Tree and select Card > Warm Start.

Right-click on the desired Card Replica in the Module View or Navigation Tree and select Card > Cold Start.

Time required for the card to execute the re-start:

Approximately 3 minutes.

Approximately 3 minutes (3 to 5 minutes for an MCU, 5 to 20 minutes for 40G Line cards).

Result:

Card software is re-started.

Card hardware and software are re-started.

Table 13

Differences between Warm Start and Cold Start

Impact of Warm and Cold Start Table 14 explains the impact of Warm and Cold Starts on various system functions. Warm Start MCU card*

Table 14

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

Not applicable.

Cold Start Traffic not interrupted. Data will be restored to the MCU from the MIB.

Impact of Warm and Cold Start

277

Cold Start and Warm Start

Troubleshooting Manual (TSMN)

Warm Start

Cold Start

Traffic-carrying cards

Traffic not interrupted. All card configuration data is restored**.

Performancemonitoring (PM) data

The PM data of the current monitoring interval will be marked by the "Suspect Interval" flag due to a Warm or Cold Start

Card alarm

If the alarm condition still exists after a Warm or Cold Start, the alarm will continue to be raised. If the alarm condition was cleared as a result of the Warm Start or Cold Start, it will no longer be raised.

Other card functions

After a Warm Start or Cold Start, provisioned configuration settings are restored. Transient data will be lost.

Table 14

Depending on card type, traffic may be interrupted. (see Table 15). All card configuration data is restored.

Impact of Warm and Cold Start (Cont.)

*An MCU Cold Start will cause the connection between the NE and Element Manager to be interrupted. The connection must be re-established by the user. Note that only the connection itself is lost - not the settings and parameters of the connection. During the disconnected time, no management of the NE is possible. **Important Note: A Warm Start of a V4 or V5 transponder card can result in the reporting of a BER degradation (preFEC BER). Note that this is simply a calculation error inherent in the ASIC used on these card types. It is emphasized that this is only a calculation error - it does not cause any post-FEC errors nor any traffic outage.

5.3

Use of Warm and Cold Start for troubleshooting In general, since a Warm Start is never traffic affecting, always try a Warm Start first when attempting to get a faulty plug-in card to recover. If the card does not recover after a Warm Start, a Cold Start may be attempted. Depending on card type, a Cold Start may interrupt traffic as listed in Table 15. When a requested Cold Start will interrupt traffic, a warning message is displayed, asking the user if he wishes to proceed. Card Type CAX

No

MCU (all types)

No

SMU

No

OCP

No

OSCT (all types)

May affect traffic (Note 1)

OM10, OM20, ODA10, ODA20

May affect traffic (Note 2)

OPAPC

No

Table 15

278

Does Cold Start interrupt traffic?

Cold Start Affect on Traffic

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

Troubleshooting Manual (TSMN)

Cold Start and Warm Start

Card Type

Does Cold Start interrupt traffic?

OCR10-T (all types)

Yes

OCR10-R (all types)

Yes (Note 3)

TEX (all types)

Yes

I04T2G5

Yes

I01T10G

Yes

OLI (all types)

Yes

PUMP A/B/C

Yes

RPUMP

Yes

PQM

May affect traffic (Note 4)

WBAN, WBAU

May affect traffic (Note 5)

WBN

Yes

OTS-4010, OTS-4011

No

OTS-4040

No

OTS-4400

No

OTS-4520

No

OTS-4540

No

OTS-4700

No

TSC

No

Table 15

Cold Start Affect on Traffic (Cont.)

Note 1: Cold Start of an OSCT card may affect traffic if the system employs Raman Pump cards. Note 2: Cold Start of an OM20 or ODA20 card is traffic-affecting only for those cards that contain MEMS Variable Optical Attenuators (VOAs). The following OM20 and ODA20 contain MEMS VOAs and thus are subject to traffic interruption due to a Cold Start. • • • • • • • •

OM20C1C2: Siemens part number S42024-L5271-C110. OM20C3C4: Siemens part number S42024-L5271-C120. OM20C5C6: Siemens part number S42024-L5271-C130. OM20C7C8: Siemens part number S42024-L5271-C140. ODA20C1C2: Siemens part number S42024-L5272-C110. ODA20C3C4: Siemens part number S42024-L5272-C120. ODA20C5C6: Siemens part number S42024-L5272-C130. ODA20C7C8: Siemens part number S42024-L5272-C140.

Note 3: OCR10-R cards are deployed in pairs to serve each transmission direction. If one OCR10-R card of a running pair is Cold Started, the MCU card managing that OCR10-R will also Cold Start (re-boot). Note 4: Cold Start of a PQM may affect traffic because each channel will undergo the mean attenuation defined for the card. Depending on the margin for the link, transmitted channels may or may not be interrupted. Note that in some early versions of SURPASS hit 7500, there is no GUI message warning of the potential traffic loss when Cold Starting a PQM card. This deficiency will be corrected in a later product release.

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

279

Cold Start and Warm Start

Troubleshooting Manual (TSMN)

Note 5: Cold Start of a WBAN or WBAU card will only impact express traffic. A Cold Start will first set all these channels to "blocked" state and then to the configured values. Add traffic is not affected.

5.4

Time required for software download to cards When a spare plug-in card is installed in the shelf, the MCU downloads software to it. The time required for software download varies according to card type, as listed in Table 16.

!

Caution! Once a replacement card has been inserted into the shelf, software download begins. Never withdraw a card during this process as software corruption can result. If it is desired to remove a newly-installed spare card, wait (at a minimum), the length of time listed Table 16.

Card

Software Download Time in minutes

CAX

2

FSU

2

OCP

2

OLI

4

ODA10, ODA20

3

OD10, OD20

3

OM10, OM20

3

OPAPC

3

OSCT

4

PQM

5

PUMP A/B/C

3

SMU

3

WBAN

5

WBAU

5

WBN

5

WSSC OCR10 V3

12

OCR10 Regio

9

OCR10 LH

9

OCR10 V2

2

OCR10 V5

9

Table 16

280

Software download times to cards

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

Troubleshooting Manual (TSMN)

Cold Start and Warm Start

Card

Software Download Time in minutes

TEX V3

12

TEX V5

10

TEX LH

10

TEX Regio

10

TSC I04T2G5 I01T10G Table 16

5.5

Software download times to cards (Cont.)

Fault LED behavior Each SURPASS hiT 7500 plug-in card has a front-panel red fault LED. If this LED is on, it indicates that there is an Equipment alarm active on that card.

g Note that the Fault LED will not light for an OBLOS, OPLOS, or PCBF alarm. A card will blink its red Fault LED under the following conditions. • • •

•

• •

If the red Fault LED is blinking on an OSCT card, it indicates a loss of signal of the Optical Supervisory Channel (see LOS alarm). If the red Fault LED is blinking on an OLI card, it indicates a loss of signal condition (see LOS alarm). If the red Fault LED is blinking on an OCR or TEX card, it indicates a loss of signal condition (see LOS alarm). The LED will blink for TEX card Line In LOS, OCR10-T Line In and Client In LOS, and OCR10-R Line In LOS. Note that for OCR and TEX cards where Supervision Mode is set to "not supervised", the red Fault LED will not blink to indicate any of these LOS conditions. If the red Fault LED is blinking on a PUMP card, and a CP alarm exists on the PUMP card at the same time, it indicates that the pigtail connection between the PUMP card and its OLI card has a problem (see CONCABF alarm). If the red Fault LED is blinking on an Optical Demux card (OD10, ODA10, OD20, or ODA20) it means that a Sub-band LOS (SBL) alarm is active on that card. If the red Fault LED is blinking on an MCU card, it means the card is undergoing its Cold Start routine or is downloading APS software to peripheral cards.

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

281

Link Control Troubleshooting

Troubleshooting Manual (TSMN)

6 Link Control Troubleshooting This chapter provides Link Control troubleshooting procedures for SURPASS hiT 7500. This chapter can be used as a supplementary procedure to troubleshoot failures such as transponder LOF when the normal troubleshooting procedure fails to isolate the problem.

6.1

Potential Symptoms The most likely causes of Link Control problems are communication errors between cards, an incorrect measurement performed by a card, cabling problems (dirty fiber), or erroneous configurations. Study the examples shown in Figure 46 through Figure 49 which show how to determine the "Link Start" location and the node at which troubleshooting should begin. Once this is done, execute the procedures in the flowchart in Figure 50.

Figure 46

282

Reference network for Link Control troubleshooting

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

Troubleshooting Manual (TSMN)

Figure 47

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

Link Control Troubleshooting

Examples 1 and 2 for Link Control troubleshooting

283

Link Control Troubleshooting

Figure 48

284

Troubleshooting Manual (TSMN)

Example 3 for Link Control troubleshooting

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

Troubleshooting Manual (TSMN)

Figure 49

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

Link Control Troubleshooting

Example 4 for Link Control troubleshooting

285

Link Control Troubleshooting

Troubleshooting Manual (TSMN)

Figure 50

Link Control troubleshooting flowchart

Pre-conditions before using the flowchart above: The procedure covered by the flowchart is supplementary to the "normal" troubleshooting procedures. Before using the flowchart, all conventional troubleshooting instructions must have been attempted first for the following alarms: • • • •

286

PREEMPF CUPGVIOL1 Alarms raised by OMxx cards LOF

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

Troubleshooting Manual (TSMN)

Last Action and Load Result Messages

7 Last Action and Load Result Messages This chapter provides troubleshooting tips for the following messages that can be displayed on the indicated Element Manager GUI windows: • •

7.1

“Last Action” messages on the OSCT card’s “Optical Link Control - Config” window. “Load Result” messages on the “Config DB Upload” and “Config DB Download” windows.

List of Last Action Messages The following tables list the "Last Action" messages that can appear on the OSCT card's Optical Link Control window. Last action messages could occur during different link state actions, indicated by one of the following prefixes: • • • •

FPR: link state in prestart or the "Forced Prestart" button was pressed PE: messages related to power equalization. PRE: messages related to pre-emphasis. SU: messages related to link start-up. “Last Action” Message

Cause

Action finished.

Remarks For information only. No problem as long it does not occur repeatedly.

Action finished - timeout.

Could occur during Link Control actions if several sequential steps take longer than expected (e.g., due to load).

Action rejected - CAN disabled.

Do not perform any further Occurs if CAN communication is disabled, action at this time. due to (for example) APS swap.

Action rejected - invalid for instance.

The MCU has sent a request to the OSCT that cannot be executed on this optical link instance.

Message is highly unlikely. But if seen, collect 4 x OSCT diagnostics. Warm Start the OSCT card. If message occurs again, try a Cold Start.

Action rejected - Output Power Control frozen.

Indicates that either no valid ESC or OSC data (e.g. channel count) are available or some problem with OLIs or RPUMP has been detected (in this case, the message "Amplifier Problem OLIs or RPUMP raised" is expected in the NE causing the problem.

Output Power Control of OLI is set to "frozen" to avoid errors due to missing/incorrect data.

Action started. Table 17

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

For information only.

Last Action Messages

287

Last Action and Load Result Messages

“Last Action” Message Adjustable VOA range exceeded: check cabling and powers.

Troubleshooting Manual (TSMN)

Cause

Remarks

Indicates that at least one VOA has reached its adjustment limit (usually the lower limit).

Amplifier Problem OLI or RPUMP cleared.

For information only.

Amplifier Problem OLI or RPUMP raised.

Either an OLI has switched its amplifiers off (due to a defect), or has limited its output power, or OSCT card was reset.

Check for other OLI-related alarms.

Amplifier Problem OLI or RPUMP raised (disabled).

OLI or RPUMP card is defective.

OLI is disabled. Check for other OLI, PUMP, RPUMP alarms.

Amplifier Problem OLI or RPUMP raised (limited).

Transmit Degrade (TD) on OLI or RPUMP.

Amplifier output power is reduced. Troubleshoot and clear the TD (OLI cards) alarm.

Attenuation setting: 'relative' mode for channel #

Occurs when the delta between requested attenuation and adjusted attenuation is larger than 0.5 dB.

OSCT will switch the OM20 port (for the listed channel #) to delta attenuation mode.

Booster Channel Input Power out of P1Min P1Max range.

Wrong power level into Booster OLI's In port.

Check for alarms and/or fiber problems.

Break - unexpected event.

Software could not complete a task.

Attempt to perform the action again.

Calc.: attenuation out of VOA range.

Invalid VOA value calculated. Possibly a dirty fiber connector.

VOA value calculated by OSCT is greater than 19.5 dB or less than 1.8 (OM) resp. 0 (WBA) dB. Very unlikely to happen even once.

Calc.: division by or logarithm of zero.

Software problem - division by 0 or logarithm of 0.

Ignore if single occurrence.This problem is not expected in the field.

Table 17

288

Troubleshoot according to the instructions for the PREEMPF alarm.

Last Action Messages (Cont.)

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

Troubleshooting Manual (TSMN)

Last Action and Load Result Messages

“Last Action” Message

Cause

Remarks

Calc.: TxDeltaPowerCompressio n performed.

The required power spread for pre-emphasis exceeds the allowed range for the NE, so compression of calculated powers has been performed to match the range.

For information only.

Calculate Power Preemphasis.

For "single step", this message indicates that Power Preemphasis is running.

For information only.

CAN partner OM 3 lost.

Indicates CAN communication problem to e.g. OM10C3. (Note: two messages will be displayed in case of OM20 cards, one for each subband).

CAN response missing.

Ignore if the message appears only once. If it continues to appear, perform 4x OSCT save diagnostics and evaluate the files.

Channel count mismatch for channel x.

Link Control has changed the “Channel Count Master from the OSCT card to the OPAPC card due to detection of a mismatch in channel count.

The wildcard “x” will display the Q3 Channel ID of the affected channel. Troubleshoot according to instructions for the CHCNTMISM alarm.

Force prestart.

Operator action.

For information only.

Invalid mean value per chan. pChSet.

Invalid value for PChSet (less than -50dBm). This would indicate a software problem.

Message is highly unlikely. But if seen, collect 4 x OSCT diagnostics. Warm Start the OSCT card. If message occurs again, try a Cold Start. If message occurs again, replace OSCT card. Send defective card and diagnostic data to Nokia Siemens Networks.

Table 17

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

Last Action Messages (Cont.)

289

Last Action and Load Result Messages

“Last Action” Message

Troubleshooting Manual (TSMN)

Cause

Remarks

No AddChannels available.

No CAN communication to far OPA card.

For all "No CAN communication to xxx card" - make sure that the PCB/CAN cabling between the shelves is OK.

Try Warm Start of OPA and OSCT in downstream terminal. If no improvement, replace OPA.

No CAN communication to OLI card.

For all "No CAN communication to xxx card" - make sure that the PCB/CAN cabling between the shelves is OK.

Check for card(s) with CANFAIL alarm and follow troubleshooting procedures.

No CAN communication to OM card.

For all "No CAN communication to xxx card" - make sure that the PCB/CAN cabling between the shelves is OK.

Check for card(s) with CANFAIL alarm and follow troubleshooting procedures.

No CAN communication to OPA card.

For all "No CAN communication to xxx card" - make sure that the PCB/CAN cabling between the shelves is OK.

Check for card(s) with CANFAIL alarm and follow troubleshooting procedures. Also, a PREEMPF alarm may be raised.

No CAN communication to far OPA card.

For all "No CAN communication to xxx card" - make sure that the PCB/CAN cabling between the shelves is OK.

Check for card(s) with CANFAIL alarm and follow troubleshooting procedures. Also, a PREEMPF alarm may be raised.

No CAN communication to PQM card.

For all "No CAN communication to xxx card" - make sure that the PCB/CAN cabling between the shelves is OK.

Check for card(s) with CANFAIL alarm and follow troubleshooting procedures.

No CAN communication to WB card.

For all "No CAN communication to xxx card" - make sure that the PCB/CAN cabling between the shelves is OK.

Check for card(s) with CANFAIL alarm and follow troubleshooting procedures.

Table 17

290

Add the cross-connection (CC) for Add/Express channels. If CC are present, Cold Start the OSCT and try again.

Last Action Messages (Cont.)

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

Troubleshooting Manual (TSMN)

Last Action and Load Result Messages

“Last Action” Message

Cause

Remarks

No CAN communication to WB/WSS card.

For all "No CAN communication to xxx card" - make sure that the PCB/CAN cabling between the shelves is OK.

Check for card(s) with CANFAIL alarm and follow troubleshooting procedures. This same message also appears if there is no CAN communication to the CAX card.

No channel for OLC instance in omsCTPSink.

Channel Count is zero for Pre-amplifier OLI.

Check line fiber.

No channel for OLC instance in omsCTPSource.

Channel Count is zero for Booster OLI, possibly due to downgrade to zero channels by removing CC or setting OM port mode to disabled.

Check alarms relating to add or express channels. In Link state Prestart, perform Power Equalization to adjust the configured channels.

No prestart ACK from far terminal: OLIs may still run.

Occurs if link state was in prestart or OSCT LOS is present while "Forced prestart" is performed.

No valid channel count available - startup paused.

After OSCT Warm Start or Cold Start, all OM / WB / WSS cards send a channel status telegram on CAN bus. If not, this message will be sent to MCU, and startup of the OSCT is delayed until all cards respond.

Not enough valid (express) channels.

Upstream link might not be in "running'" state yet.

OLI does not start in time.

Fiber interruption (e.g. DCF Expected at OADM100U if connection) during OLI Add-OLI does not have any startup. add channels. For all other cases, repeat last action again.

Table 17

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

Ensure CC established and channel status is valid.

Last Action Messages (Cont.)

291

Last Action and Load Result Messages

“Last Action” Message

Cause

Remarks

OM Channel Input Power x out of range.

The OM port for Channel “x” has an input power outside the allowed range of “mean accepted input power” +/- 3 dB.

Channel “x” cannot be taken into service. (The wildcard “x” will be displayed as the Q3 Channel ID of the affected channel). Check fiber connections and this channel’s transponder output power.

OpticalLinkControl startup ready.

OSCT card reset completed and OLC initialized.

For information only.

Optimization action pending.

This message appears whenever the user clicks the “action optimization” button.

Optimization suceeded at NE-Number %2u (%s)

For information only.

OSC PING not received from far terminal.

Ensure that none of the OSCT cards has an LOS, LOF or TIM alarm. Check for end-to-end OSC connectivity using OSCT TTI for each span within the link.

Precondition violation.

This message appears if preemphasis cannot be performed for the following reasons: automatic attenuator control is set to “manual” instead of “automatic”, or WB card WSS card, or PQM card is required equipping, but not reachable for link control purposes.

Troubleshoot according to the instructions for the PREEMPF alarm.

Received POWER data for channel # are invalid abort.

This message displayed only if single-step preemphasis was selected. If there is a problem with channel data (e.g., a missing channel), the preemphasis action will be interrupted.

This message shows which channel number has the problem. Check for LOC alarms.

Table 17

292

Troubleshooting Manual (TSMN)

Last Action Messages (Cont.)

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

Troubleshooting Manual (TSMN)

Last Action and Load Result Messages

“Last Action” Message

Cause

Received POWER data are All power values received invalid - abort. are -99.9dBm.

Remarks If it is a single message, ignore. If sent continuously by OSCT, reset OPA and check cabling of OPA monitor points to OLI. Preemphasis will not be performed.

Received POWER data are This message will be The preemphasis partially invalid - continue. displayed if continuous optimization will continue preemphasis was selected. even if sufficient channel data is not available. Preemphasis optimization will be performed for those channels that do have channel data available. Requested data not received from far OPA.

OPA available via CAN and Check link end OPAPC OSC, but no data received (most probable), or check if - check far OPA! OSC is working. If OSC is not working, there will be a OSCT LOS.

Requested data not received from local OPA.

When local OPA is not sending measurement data to OSCT this message is sent.

RPUMP does not start in time.

Check fibers to/from RPUMP card.

Startup fails by receiving Link State Prestart.

Link startup sequence interrupted by Operator.

Startup stopped at NENumber %2u (%s).

A local OLI is not available on the CAN bus, or is in a frozen state.

Startup succeeded at NENumber %2u (%s) Unexpected response or event.

Table 17

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

Communication telegrams with measurement data via CAN bus was not received, but general CAN communication between OPA and OSCT is still OK. Warm/Cold start local OPA.

Operator aborted link startup.

For information only. Software problem.

Ignore if it is a single event. Event sequence continues. No user action needed.

Last Action Messages (Cont.)

293

Last Action and Load Result Messages

Troubleshooting Manual (TSMN)

“Last Action” Message

Cause

Remarks

Unused channel x with light at input port.

The OM port for Channel “x” has a valid input power level, but its port mode is set to “disabled”.

The wildcard “x” will display the Q3 Channel ID of the affected port. If the channel is not desired, disable the line laser on the coresponding Transponder card. If the channel is desired, perform channel upgrade according to published procedure.

Wrong cabling in RPUMP detected at NE-Number %2u (%s). Wrong cabling in RPUMP detected.

Table 17

7.2

Fix the cabling error.

RPUMP is incorrectly connected to another span (i.e., connected to wrong OLI).

Fix the cabling error.

Last Action Messages (Cont.)

List of Load Result Messages The following tables list the "Load Result" messages that can appear on the followingwindows. • • •

Table 18: Load Result Messages on Config DB Upload window. Table 19: Load Result Messages on Config DB Download window. Table 20: Load Result Messages on both windows (Config DB Upload and Config DB Download).

“Load Result” message

Cause

Remarks Wait until the download is completed. Then, retry the upload. If download is stuck, Cold Start the MCU card and try again.

Download in Progress

A Config DB download is in progress when an upload was attempted.

Error building the VCDB header

An error occurred while getting info Try the upload again. If the same from the MIB to build the VCDB file. message is displayed, Cold Start the MCU and try again.

NE State Idle

Upload was attempted while NE is set to Idle state, which is not allowed.

Change NE state to Active and try the upload again.

Upload aborted at (date time)

The upload was manually aborted at the indicated date and time.

-

Upload completed

The upload completed successfully. -

Table 18

294

Load Result messages on the Config DB Upload window

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

Troubleshooting Manual (TSMN)

“Load Result” message

Last Action and Load Result Messages

Cause

Remarks

Upload failed at (date time)

The upload failed at the indicated date and time.

Try the upload again. If the same message is displayed, Cold Start the MCU and try again.

VCDB Upload complete: xx percent

Ongoing progress indicator - the indicated percentage of the upload has been completed so far.

-

Table 18

Load Result messages on the Config DB Upload window (Cont.)

“Load Result” message

Cause

Remarks

Abort from OS

The download was manually interrupted.

-

Download Reject: Incompatible NE-Type

Download is not possible because the VCDB file was uploaded from a different NE type.

Use the correct VCDB file.

Error reading VCDB Header

The VCDB file may be corrupted or may be an obsolete version.

Use a VCDB file that is compatible with the running software.

Old/incompatible VCDB file (wrong magic number)

The VCDB file header is an incompatible version.

Use a VCDB file that is compatible with the running software.

VCDB Download complete: xx percent

Ongoing progress indicator - the indicated percentage of the download has been completed so far.

-

VCDB Upload in Progress

A Config DB upload is in progress when a download was attempted.

Wait until the upload is completed. Then, retry the download. If upload is stuck, Cold Start the MCU card and try again.

Table 19

Load Result messages on the Config DB Download window

“Load Result” message

Cause

Remarks

Call to loadMibBlock with Invalid MO Instance x

Upload/download action issued incorrectly.

Try again. If same message displayed, Cold Start the MCU and try again.

Init Fail (info from flashPrepare)

Preparatory process failed.

Try again. If same message displayed, Cold Start the MCU and try again.

Lost SA Connection

Process aborted because the connection to the sub-agent was lost.

Re-establish the connection and try again.

Table 20

Load Result messages on both windows (Config DB Upload and Config DB Download)

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

295

Last Action and Load Result Messages

“Load Result” message

Troubleshooting Manual (TSMN)

Cause

Remarks

Mib Card Problem

MIB card has a hardware fault (MIBF alarm likely) or is missing from the shelf (MIBM alarm will be raised).

If MIB is missing, install it. If MIB has a hardware fault, try again. If same message displayed, replace the MIB card.

Mib card Pulled

Process was aborted because the MIB card was removed from the shelf.

Re-install the MIB card and try again.

No faults

Process completed.

-

Pers I/O Problem

Problem with MIB Flash. A MIBF alarm may or may not be raised.

If a MIBF alarm is raised, wait to see if it clears itself, Then, continue with the upload/download. If no alarm raised, try the upload/download again - if the same Load Result message is displayed, replace the MIB card.

Update Loadstate Fail

An error occurred writing to the MIB. Cold Start the MCU card and try again.

Wrong MO Addressed

The wrong managed object was addressed.

Table 20

296

Only likely when using TL1. Ensure that the TL1 command addresses the correct managed object.

Load Result messages on both windows (Config DB Upload and Config DB Download) (Cont.)

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

Troubleshooting Manual (TSMN)

Performance Monitoring and TCAs

8 Performance Monitoring and TCAs The performance parameters on the indicated layers/interfaces listed in this chapter can be monitored by SURPASS hiT 7500. The user may set the desired 15-minute and 24hour alarm threshold for each monitored parameter. The relevant Threshold Crossing Alert (TCA) will be raised if the count for a monitored parameter exceeds its user-designated threshold.

8.1

OCU transponder card Performance Parameters

Layer

Card type OCR10R

Line side Section (OTU2)

OCR10T

TEX

V2

V3 LH Re

V5

V2

V3 LH Re

V5

V3 LH Re

V5

1)

2)

2)

1)

2)

2)

2)

2)

2)

2)

9)

6)

6)

6)

6)

6)

6)

6)

2)

2)

2)

2)

Path (ODU1) Path (ODU2)

3)

6)

Section TCM layer Client side

Line to client

SDH /SONET

4)

7)

6)

6)

6)

6)

6)

6)

7)

7)

7)

LAN Client to line

6)

6)

7)

7)

7)

7)

8)

8)

8)

8)

6)

6)

9)

9)

10)

SDH /SONET

5)

8)

8)

8)

LAN

8) 10)

Section (OTU1) Section (OTU2)

2)

2)

2)

Path (ODU1)

6) 9)

Path (ODU2)

9)

9)

9)

Interface types 1) to 10): supported parameters see table part 2 below Table 21

Performance parameter for OCR10R, OCR10T and TEX cards, part 1

Interface type

Performance parameter BBE CBES CV ES SEFS SES UAS max. avg. BFR FCSE FR MFR UFR BER BER

1) near end

X

X

X 2) near end, far end, pre EFEC BER Table 22

X X

X

X X

X

X

X

Performance parameter for OCR10R, OCR10T and TEX cards, part 2

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

297

Performance Monitoring and TCAs

Troubleshooting Manual (TSMN)

Interface type

Performance parameter BBE CBES CV ES SEFS SES UAS max. avg. BFR FCSE FR MFR UFR BER BER

3) near end, far end

X

X

4) outgoing

X

X

X

X

5) near end

X

X

X

X

6) near end, far end

X

7) outgoing

X

X

X

8) near end

X

X

X

9) near end

X

X

X

X

X

X

X

X

X

X

X

X

X

X

10) outgoing Table 22

X

X

X

X

Performance parameter for OCR10R, OCR10T and TEX cards, part 2 (Cont.)

8.2

OTS-4000 transponder cards Performance Parameters Layer

Card type OTS-4011 OTS-4011 V3

Line side Section (OTU3)

Table 23

298

X

1)

OTS-4040 OTS-4040 V3 1)

Path (ODU2)

2)

Path (ODU3)

2)

2)

TCM layer

2)

2)

OTS-4400 OTS-4400 V3 1)

Performance parameter for OTS-4000 cards, part 1

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

Troubleshooting Manual (TSMN)

Performance Monitoring and TCAs

Layer

Card type OTS-4011 OTS-4011 V3

Client side

Line to client

Client to line

SDH /SONET

3)

LAN

4)

SDH /SONET

5)

LAN

6)

Section (OTU2)

OTS-4040 OTS-4040 V3

OTS-4400 OTS-4400 V3

8)

5)

2)

Section (OTU3)

1)

Path (ODU2)

7)

Path (ODU3)

7)

TCM layer

2)

2)

Interface types 1) to 8): supported parameters see table part 2 below Table 23

Performance parameter for OTS-4000 cards, part 1 (Cont.)

Interface type

Performance parameter BBE

CV

ES

SEFS

SES

UAS

max. BER

avg. BER

X

X

1) near end, X pre EFEC BER

X

X

X

2) near end

X

X

X

X

3) outgoing

X

X

X

X

X

X

4) outgoing 5) near end

X

X

X

X

X

8) outgoing Table 24

X

X X

X

X X

FR

MFR

UFR

X

X

X

X

X

X

X

X

X

6) incoming 7) near end

BFR

X

X

Performance parameter for OTS-4000 cards, part 2

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

299

Performance Monitoring and TCAs

8.3

Troubleshooting Manual (TSMN)

HDS transponder card Performance Parameters Layer

Card type I01T10G

I04T2G5

Line side Section (OTU1)

1)

Section (OTU2)

1)

1)

Path (ODU1)

Client side

I08T10G

2)

Path (ODU2)

2)

2)

TCM layer

2)

2)

Line to client

Client to line

SDH

3)

3)

3)

SONET

4)

4)

4)

LAN

5)

9)

9)

FC 1G

10)

FC 2G

10)

SDH

6)

6)

6)

SONET

7)

7)

7)

LAN

8)

8)

8)

FC 1G

11)

FC 2G

11)

Section (OTU1) Section (OTU2)

1)

1)

12)

12)

1)

Path (ODU1) Path (ODU2)

2)

TCM layer

2) Interface types 1) to 12): supported parameters see table parts 2 to 4 below

Table 25

Performance parameter for HDS transponder cards, part 1

Interface type

Performance parameter BBE

ES

SEFS

SES

UAS

max. BER

avg. BER

X

X

1) near end, X far end, pre EFEC BER

X

X

X

2) near end, far end

X

X

X

Table 26

300

CV

X

Performance parameter for HDS transponder cards, part 2

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

Troubleshooting Manual (TSMN)

Performance Monitoring and TCAs

Interface type

Performance parameter BBE

3) outgoing

X

4) outgoing

X

X

X

UAS

X X

X X

X

Performance parameter EFT

5) outgoing

X

FTO

OTO

X

X

EFT

DGF

ESB

8) incoming X

X

X

X

ORO

FRO

X

X

X

Performance parameter for HDS transponder cards, part 3

Interface type

Performance parameter CVDE

8.4

EF

X

9) outgoing

LF

LOSy

LOSi

10) outgoing

X

X

X

X

11) incoming

X

X

X

X

Table 28

avg. BER

Performance parameter for HDS transponder cards, part 2 (Cont.)

Interface type

Table 27

max. BER

X

X

X

X

SES X

X X

12) near end

SEFS

X

X

7) incoming

ES X

X

6) incoming

Table 26

CV

ESB X

DGF X

Performance parameter for HDS transponder cards, part 4

Monitored parameter definitions CV

Code Violations: This is the count of the incoming Client signal's SONET B1 BIP-8 errors (when SES-S is not present in the previous second). Based on the Bit Interleaved Parity algorithm, a checksum will be generated over the received frame and compared with the received BIP-8 checksum in the B1 byte. Code Violations are an indication of all bit errors in the B1 Block. The maximum which can be achieved in one frame is 8. Note that if there is an active Rx SONET LOS or LOF condition, CV is suppressed, since no frames, and hence, no CV information can be received. Near-end = the incoming signal. Outgoing = the transmitted signal.

BBE

Background Block Errors: An errored block not occurring as a result of an SES.

Table 29

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

Monitored parameter definitions

301

Performance Monitoring and TCAs

ES

Errored Seconds: For each layer, an Errored Second is defined as a second that contains an LOS of SEF defect, or when at least one CV has occurred in that layer in the previous second

SES

Severely Errored Seconds: For each layer, a Severely Errored Second is defined as a second that contains an LOS of SEF defect, or when at least 8554 CVs have occurred in that layer in the previous second. Once SES has been raised, CVs for this second will not be added to the CV count.

SEFS

Severely Errored Framing Seconds: This is the count of seconds that contain an SEF or LOS.

CBES

Corrected Bite Error Seconds: This is a count of the seconds in which the BER (Bit Error Rate) before FEC (Forward Error Correction) was worse than a user-specified threshold.

UAS

Unavailable Seconds: This is the count of seconds that the interface was "unavailable" due to 10 consecutive SESs (the 10 consecutive SESs are included in the unavailable time). The interface is considered "available" again when there are 10 consecutive seconds with no SESs (the 10 consecutive seconds with no SESs are excluded from the unavailable time).

BFR

Broadcast Frames Received

DGF

Discarded GFP Frames

EF

Errored Frames

EFT

Errored Frames Transmitted

ESB

Errored Super Blocks

FCSE

Frame Check Sequence Errors

FR

Frames Received

FRO

Frames Received OK

FTO

Frames Transmitted OK

LF

Link Failures

LOSi

Loss of Signal

LOSy

Loss of Sync

MFR

Multicast Frames Received

ORO

Octets Received OK

OTO

Octets Transmitted OK

UFR

Unicast Frames Received

Table 29

302

Troubleshooting Manual (TSMN)

Monitored parameter definitions (Cont.)

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

Troubleshooting Manual (TSMN)

MIB, MCU, and SAB replacement

9 MIB, MCU, and SAB replacement This chapter provides removal and replacement instructions for the following SURPASS hiT 7500 components: • • •

9.1

MIB (Management Information Base) circuit board. MCU (Main Controller Unit) plug-in card. SAB (Subrack Address Board).

MIB circuit board replacement procedures It is assumed that a MIBF (MIB Failure) alarm has occurred, necessitating removal of the failed MIB and replacement with a spare. Major points to note are as follows: •

•

a MIBF alarm is always raised by the MCU card served by the failed MIB. Therefore, it is necessary to first identify and locate the MCU card raising the alarm, then replace the MIB associated with that MCU. Table 30 lists the types of MIB boards used in SURPASS hiT 7500 network elements. MIB Type

!

Remarks

MIBS32

S42024-D5015-A102

32 Mbyte flash memory.

MIBS32-2

S42024-D5015-A202

32 Mbyte flash memory, 2 MAC addresses.

MIBS256

S42024-D5015-B100

256 Mbyte flash memory (accommodates APS backup).

Table 30

!

Siemens Part Number

MIB circuit board types

Caution! If an installed MIBS256 fails, the replacement board must also be a MIBS256. If an installed MIBS32 or MIBS32-2 fails, the replacement board can be any MIB type listed in the table above.

Caution! The NE must remain powered-up when replacing a MIB. If power is disconnected before replacing a MIB board, the database will be lost and traffic will likely be lost.

Execute, in sequence, the procedures in the following chapters to replace a failed MIB circuit board: • • • •

Chapter 9.1.1 “Determine location of MCU raising the MIBF alarm”. Chapter 9.1.2 “Determine location of the failed MIB”. Chapter 9.1.3 “Remove failed MIB”. Chapter 9.1.4 “Install new MIB”.

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

303

MIB, MCU, and SAB replacement

Figure 51

9.1.1

Troubleshooting Manual (TSMN)

MIB replacement; basic steps

Determine location of MCU raising the MIBF alarm Follow the steps below to determine the physical location of the MCU card that has raised the MIBF alarm. 1. Study Figure 52. Note how the "location" of a MIBF alarm is displayed. The syntax of the location will be one of the types listed in Table 31. 2. Determining the physical location of the MCU varies slightly depending on MCU type. Follow the appropriate set of instructions (chapter 9.1.1.1 or chapter 9.1.1.2) to determine the location of the MCU raising the MIBF alarm. If the "location" of the MIBF alarm is reported in this syntax (see Note 1):

It means the type of MCU reporting the MIBF is:

And the actual physical location of this MCU is:

xxx-019 MCU

MCU-MTS

Shelf xxx, Slot 19

yy1-017 MCU

MCU-OCU

Shelf yy1, Slot 17

zz0-001 MCU

MCU-OCU40

Shelf yy1, Slot 18 (see Note 2)

aa0-001 MCU

MCU-OCU73

Shelf yy1, Slot 18 (see Note 2)

10-001 MCU

MCU-CNE

Shelf yy1, Slot 18 (see Note 3)

80-001 MCU

MCU-TL1GNE

Shelf yy1, Slot 18 (see Note 2)

90-001 MCU

MCU-Q3GNE

Shelf yy1, Slot 18 (see Note 2)

Table 31

Location syntax of MIBF alarm

g Note 1: System defaults: xxx = 101 for OTTU, 121 for OLRU, 131 for CCU, 181 for the OTTU in an OTTC, 200 or 210 for the ADNs in OADM100N, 300 or 310 for the ADUs in an OADM100U, 370, 380, or 390 for the ADXs in an OADM100U.

304

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

Troubleshooting Manual (TSMN)

MIB, MCU, and SAB replacement

yy = 50 - 89 (or 14 for stand-alone OCU). zz = 42 - 49, aa = 90 - 95.

g Note 2: Instead of being installed in Slot 18 of an OCU Shelf, MCU-OCU-40, MCUOCU73, MCU-Q3GNE, and MCU-TL1GNE cards can also be installed in the optional MCU-Shelf (Shelf Number for physical location is 012). If these MCU type(s) are installed in the MCU-Shelf, they can be placed in any slot from Slot 3 to Slot 11.

g Note 3: Instead of being installed in Slot 18 of an OCU Shelf, the MCU-CNE card can also be installed in the optional MCU-Shelf (Shelf Number for physical location is 012). If the MCU-CNE is installed in the MCU-Shelf, it can be placed in Slot 12 only.

Figure 52

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

MIBF alarm reporting

305

MIB, MCU, and SAB replacement

9.1.1.1

Troubleshooting Manual (TSMN)

MCU-MTS, MCU-OCU, MCU-OCU40, and MCU-OCU73 location For these MCU types, the displayed "location" of the MIBF alarm essentially specifies the physical location of the MCU as in the following examples: • • •

If alarm location is 200-019 MCU: alarm is raised by MCU-MTS in Shelf 200, Slot 19. If alarm location is 531-017 MCU: alarm is raised by MCU-OCU in Shelf 531, Slot 17. If alarm location is 451-001 MCU: alarm is raised by MCU-OCU40 in Shelf 451, Slot 18.

Note the following: • •

•

The failed MIB is located in the same shelf as the MCU raising the alarm. For additional information, open this shelf's Subrack-Config window as shown in Figure 53. During commissioning, information may have been entered in the Location field on this window, which will further assist in determining the exact physical location of this shelf. So, now that the location of the MCU raising the alarm is known, continue with chapter 9.1.2 for instructions how to locate the MIB associated with this MCU.

g Note the System Default Values for xxx, yy, and zz listed in Table 31. If, during the NE commissioning procedures, a shelf's Bay/Shelf ID (set on the “Subrack-Config” window) was designated to be a value different than the default, the alarm message will reflect this value. For example, if the Bay/Shelf ID of Shelf 501 was user-specified to be 91, the location syntax will be displayed as 091-017 MCU. This example indicates an MCU-OCU in Slot 17 of the shelf now designated as 91.

Figure 53

9.1.1.2

Subrack-Config window

MCU-CNE, MCU-TL1GNE, and MCU-Q3GNE location Although each of these MCU types physically resides in an OCU shelf (or optionally in the dedicated MCU-Shelf), system software uses a logical representation to identify them on the craft terminal GUIs. As listed in Table 31: • • •

the MCU-CNE is represented in logical Shelf 10, logical Slot 1. the MCU-TL1GNE is represented in logical Shelf 80, logical Slot 1. the MCU-Q3GNE is represented in logical Shelf 90, logical Slot 1.

1. To determine the physical location of one of these MCU types, perform the following steps (MCU-Q3GNE in logical shelf 90 is used as an example). 2. In the Navigation Tree, click on Subrack 90 as shown in Figure 54. The Module View of this shelf will then be displayed. In the Module View, right-click on the Subrack panel and select Configuration.

306

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

Troubleshooting Manual (TSMN)

Figure 54

MIB, MCU, and SAB replacement

Click Subrack name in the Navigation Tree

3. The “Subrack Config” window for this shelf will be displayed (refer back to Figure 53 for an example). Note the information displayed in the Subrack Address, Location, and Bay/Shelf fields. With this information, the location of the shelf is known. Note the following: • •

9.1.2

The failed MIB is located in the same shelf as the MCU raising the alarm. So, now that the location of the MCU raising the alarm is known, continue with chapter 9.1.2 for instructions how to locate the MIB associated with this MCU.

Determine location of the failed MIB After determining the Shelf/Slot location of the MCU raising the MIBF alarm, the MIB circuit board associated with that MCU (i.e., the MIB board that has failed) can be located. Use Figure 55, Figure 56, Figure 57, or Figure 58 (whichever matches the type of shelf concerned) to locate the failed MIB.

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

307

MIB, MCU, and SAB replacement

Figure 55

308

Troubleshooting Manual (TSMN)

MIB location in double-row shelf

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

Troubleshooting Manual (TSMN)

Figure 56

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

MIB, MCU, and SAB replacement

MIB Location in OCU Shelf

309

MIB, MCU, and SAB replacement

Figure 57

310

Troubleshooting Manual (TSMN)

MIB location in single-row shelf

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

Troubleshooting Manual (TSMN)

Figure 58

9.1.3

MIB, MCU, and SAB replacement

MIB locations in the MCU Shelf

Remove failed MIB Follow the steps below to remove a failed MIB circuit board. 1. Put on an ESD wrist strap. Open the shelf front door. Carefully remove the door from its hinges and set aside. 2. For MTS Shelves (single- and double-row): directly to the right of the MCU card, there is a small protective cover over the MIB area. Remove this cover by simply pulling it loose. Carefully set it aside. 3. For OCU Shelves: a large protective plate covers Slot 17, Slot 18, and the MIB area. Loosen the attachment screw, remove the plate, and carefully set it aside. 4. Note that a special MIB Extraction/Replacement tool is required. It will be found stored in a clip on the shelf that contains the MCU-MTS as shown in Figure 59. Remove the tool from its storage clip. 5. Follow the instructions in Figure 60 to remove the failed MIB. Once the MIB board is removed, the MIBF alarm will be cleared and a MIBM (MIB Missing) alarm will be raised.

!

Caution! Never remove an MCU card from the shelf when its MIB is not installed.

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

311

MIB, MCU, and SAB replacement

Figure 59

312

Troubleshooting Manual (TSMN)

Storage location of MIB tool

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

Troubleshooting Manual (TSMN)

Figure 60

9.1.4

MIB, MCU, and SAB replacement

Removing a failed MIB

Install new MIB Follow the steps below to install a new MIB circuit board. 1. Install the new MIB using the special tool as shown in Figure 61. When the new MIB is inserted into its holder, the MIBM (MIB Missing) alarm will clear, and formatting of

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

313

MIB, MCU, and SAB replacement

2. 3. 4. 5.

the MIB begins. The formatting routine takes approximately 10 to 20 minutes to complete (depending on NE type). The MIBF (MIB Failure) alarm will be raised again throughout the formatting routine. When the formatting routine is completed, the MIBF alarm will clear. Do NOT unplug the MIB during the formatting routine! Re-install shelf protective covers. Re-install the shelf door and latch it fully closed. Verify that no alarms remain raised. Properly prepare the defective MIB for return shipping for repair or replacement. 10 “Packing equipment for return”. Place the special tool back in its storage clip on the shelf.

Figure 61

9.2

Troubleshooting Manual (TSMN)

Inserting the new MIB into the shelf

MCU replacement procedures It is assumed that an MCU card has failed, necessitating its removal and replacement. Procedures for MCU replacement vary according to the type of MIB board that is installed with the failed MCU. Follow the appropriate set of instructions in the following chapters: • •

9.2.1

Chapter 9.2.1 “MCU replacement if MIBS256 is used”. Chapter 9.2.2 “MCU replacement if MIBS32 or MIBS32-2 is used”.

MCU replacement if MIBS256 is used This procedure is valid for all MCU types deployed in the hiT 7500 system when the MCU is used with a MIBS256 board. Specifically, this procedure is valid for the following MCU types: • • • • • • •

MCU-MTS MCU-CNE (also known as the Main Agent MCU or Master MCU). MCU-OCU MCU-OCU40 MCU-OCU73 MCU-Q3GNE MCU-TL1GNE

If a MIBS256 board in installed with the failed MCU, it is permitted to simply remove the failed MCU and install a replacement MCU of the matching type. Follow the instructions below.

314

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

Troubleshooting Manual (TSMN)

MIB, MCU, and SAB replacement

1. Put on an ESD wrist strap. Open the front door of the shelf containing the failed MCU. Take the door off its hinges and carefully set aside. 2. For OCU shelves, remove the protective plate that covers Slot 17 and Slot 18. Set the plate aside. 3. Carefully remove the failed MCU from the shelf. Install the replacement MCU. Caution!

!

Ensure that the replacement MCU is the exact same type as the failed MCU. Examples: an MCU-MTS can only be replaced by an MCU-MTS. An MCU-OCU40 can only be replaced by an MCU-OCU40.

4. Verify that the replacement MCU initializes. Required data will be loaded from the MIBS256 onto the replacement MCU. It will take approximately 10 minutes for the replacement MCU to come on-line (verify that the MCU's green LED remains on). A MIBF alarm will also be raised during this time. Wait for it to self-clear. Re-connect to the NE. g There is a very remote chance that the replacement MCU may have old software on-board that does not recognize the MIBS256. The APS software on the new MCU must be Release 3.13.00 or higher. If the new MCU does not come-on-line, contact your next higher level of technical support. 5. Re-install protective covers. Re-install the shelf door and latch it fully closed 6. Verify that no alarms are present. 7. Properly prepare the defective MCU for return shipping for repair or replacement. Refer to chapter 10 “Packing equipment for return”.

9.2.2

MCU replacement if MIBS32 or MIBS32-2 is used This procedure is valid for all MCU types deployed in the hiT 7500 system when the MCU is used with a MIBS32 or MIBS32-2 board. Specifically, this procedure is valid for the following MCU types: • • • • • • •

MCU-MTS MCU-CNE (also known as the Main Agent MCU or Master MCU). MCU-OCU MCU-OCU40 MCU-OCU73 MCU-Q3GNE MCU-TL1GNE

If a MIBS32 or MIBS32-2 is installed with the failed MCU, note the following. •

•

•

Depending on your spares stock, software on the spare MCU may be an older version than the software on the failed card. This mismatch will become apparent when the card replacement is attempted. In this case, it may be required to manually upgrade the software on the spare MCU as explained in the instructions. Example: a failed MCU has 3.13 software but the replacement MCU has 3.11. The replacement MCU must be manually upgraded to 3.13. See Figure 62. Only the Main Agent (Master) MCU (i.e., the MCU-CNE) and MCUs deployed as “Stand-alone MCUs” require the manual software upgrade. MCUs deployed as “Sub-agent MCUs” do not require the manual software upgrade. Figure 62 provides an overview of the MCU replacement procedure. Detailed instructions follow the flowchart.

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

315

MIB, MCU, and SAB replacement

Troubleshooting Manual (TSMN)

There are two sets of instructions. Use the set that matches the type of MCU being replaced: • •

Chapter 9.2.2.1 for MCU-CNE and Stand-alone MCUs. Chapter 9.2.2.2 for Sub-Agent MCUs.

Figure 62

316

MCU replacement flowchart

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

Troubleshooting Manual (TSMN)

9.2.2.1

MIB, MCU, and SAB replacement

MCU-CNE and Stand-alone MCU replacement (for MIBS32/MIBS322) Follow the instructions below to replace a failed Main Agent (Master) MCU (i.e., the MCU-CNE) and MCUs deployed as “Stand-alone MCUs” (refer to Figure 62). Note: these procedures are necessary only if a MIBS32 or MIBS32-2 is used. If a MIBS256 is used, follow the instructions in chapter 9.2.1. 1. Put on an ESD wrist strap. Open the front door of the shelf containing the failed MCU. Take the door off its hinges and carefully set aside 2. For OCU Shelves, remove the protective plate that covers Slot 17 and Slot 18. Carefully set the plate aside. 3. The failed MCU will have its red "Fail" LED lit. Carefully remove this MCU from the shelf. Install the replacement MCU.

!

Caution! Ensure that the replacement MCU is the exact same type as the failed MCU. Examples: an MCU-MTS must only be replaced by an MCU-MTS. An MCU-CNE must only be replaced by an MCU-CNE.

4. Wait for the new MCU to initialize. MCU-CNEs and stand-alone MCUs require up to 15 minutes to initialize. g If the replacement MCU has an older software version, connectivity to the NE may be rejected since the User ID/password may not be recognized. If this happens, use the default User ID = superuser and the default password = Siemens4u! 5. After the new MCU initializes, start Element Manager and check the NE State (displayed in the Status Bar at the bottom of the Element Manager window as shown in Figure 63). • If the NE is in Idle state: go directly to Step 6. • If the NE is in Active state: check the APS version in the Active bank of the new MCU card. To do so, open the Functional View for the NE, then right-click on the Network Element Bar and select Software Management. On the resulting “Software Management” window, select the Network Element Software tab and check the Active APS listings. Verify that the Order Number and SW/FW Code are correct for the NE type. Is the correct APS in the active bank? No: go directly to step 6. Yes: skip steps 6 through 8, and go directly to step 9.

Figure 63

“NE State” display

6. To download the correct APS, perform the following steps: . • Open the “Software Management” window (right-click on the Functional View's Network Element Bar and select Software Management). • Download the correct APS file to the new MCU and perform the required swap. Note that the APS swap will cause an MCU re-boot. For APS Download instruc-

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

317

MIB, MCU, and SAB replacement

7. 8. 9. 10.

9.2.2.2

Troubleshooting Manual (TSMN)

tions, refer to the on-line Help for the “Software Management” window. [It is assumed that the correct APS is available on your server for download. If not, a CD with the correct APS version will need to be obtained for the download]. • After download and swap are complete, continue to Step 7. Is the NE in the “Active” state? (Step 5 explains how to determine this). Yes: skip step 8 and go directly to step 9. No: continue to step 8. Restore the correct VCDB to the NE. Then, re-connect to the NE and verify that it is in Active State as shown in Figure 63. Re-install protective covers. Re-install the shelf door and latch it fully closed. Verify that no alarms are raised. Properly prepare the defective MCU for return shipping for repair or replacement. Refer to chapter 10 “Packing equipment for return”.

Sub-agent MCU replacement (for MIBS32/MIBS32-2) Follow the instructions below to replace a failed Sub-agent MCU (refer to Figure 62). Note: these procedures are necessary only if a MIBS32 or MIBS32-2 is used. If a MIBS256 is used, follow the instructions in chapter 9.2.1. 1. Put on an ESD wrist strap. Open the front door of the shelf containing the failed MCU. Take the door off its hinges and carefully set aside. 2. For OCU Shelves, remove the protective plate that covers Slot 17 and Slot 18. Carefully set the plate aside. 3. Carefully remove the failed MCU from the shelf. Install the replacement MCU.

!

Caution! Ensure that the replacement MCU is the exact same type as the failed MCU. Examples: an MCU-MTS must only be replaced by an MCU-MTS. An MCU-OCU40 must only be replaced by an MCU-OCU40.

4. Wait at least 15 minutes for the replacement MCU card to initialize. If the replacement MCU has software on it older than that running the NE, SMISS and/or SFAIL alarms may be raised during this time while the MCU card’s software is automatically upgraded. Wait for the SMISS and SFAIL alarms to self-clear, which should occur by the end of the 15-minute period. 5. Is the Sub-Agent containing the new MCU visible in the Tree View? • Yes: skip steps 6 through 8. Go directly to step 9. • No: From the NE State pull-down menu (shown in Figure 64), set the NE to "Idle" state. Then, refer to the Commissioning document that matches the NE type (OADM100U Commissioning, OADM100N Commissioning, etc). Execute the instructions in the chapter titled "Service Menu configuration". When this is completed, go to Step 6.

Figure 64

318

Set NE to Idle

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

Troubleshooting Manual (TSMN)

MIB, MCU, and SAB replacement

6. Open the “Config DB Management” window (right-click on the Functional View's Network Element Bar and select Config DB Management). 7. Download the correct VCDB file to the NE and perform the required swap. Note that connection to the node will be lost and the system will re-boot. [It is assumed that a backup copy of the correct VCDB was previously uploaded and is available on your server for download. For VCDB Download instructions, refer to the on-line help for the “Config DB Management” window]. 8. Re-connect to the NE and check the bottom right corner of the craft terminal window as shown in Figure 63. Verify that the NE State is shown as "active". 9. Re-install protective covers. Re-install the shelf door and latch it fully closed. 10. Verify that no alarms are raised. 11. Properly prepare the defective MCU for return shipping for repair or replacement. Refer to chapter 10 “Packing equipment for return”.

9.3

SAB replacement procedures Each MTS shelf contains a Subrack Address Board (SAB) or Subrack Address Board Modified (SABM). If a SAB or SABM fails, the associated shelf will raise an SAB Failure (SABF) alarm. The shelf raising the alarm will be identified in the alarm message. Replacement instructions are as follows: 1. Put on an ESD wrist strap. Open the front door of the shelf containing the failed SAB. Take the door off its hinges and carefully set aside. 2. Directly to the right of the MCU card, there is a small protective cover over the MIB/SAB area. Remove this cover by simply pulling it loose. Carefully set it aside 3. For SAB(M) locations in the shelf, refer to Figure 55 and Figure 57. Remove the failed SAB(M) from the shelf using the special Siemens tool (order number C50165A32-C67). Use of the tool is similar to that for removing a MIB (refer to Figure 60). 4. Install the new SAB(M) using the special tool. Use of the tool is similar to that for inserting a new MIB (refer to Figure 61). Caution!

!

Ensure that the replacement board is the same type as the failed board - SAB or SABM.

5. 6. 7. 8.

Re-install the protective cover over the MIB/SAB area. Re-install the shelf door and latch it fully closed. Verify that the SABF alarm has cleared. Properly prepare the defective SAB(M) for return shipping for repair or replacement. Refer to chapter 10 “Packing equipment for return”.

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

319

Packing equipment for return

Troubleshooting Manual (TSMN)

10 Packing equipment for return This chapter provides requirements for the packing, packaging, and shipping of telecommunications systems, spares, printed wiring board assemblies, and other material.

!

10.1

Caution! This procedures herein must be followed by anyone involved in the packing, packaging, or shipping of equipment manufactured or supplied by Nokia Siemens Networks. Follow these procedures whenever returning defective equipment for repair or replacement.

Definitions Cushioning: packing material used to protect against force or shock. Dunnage: padding in a shipping container that protects contents from damage.

10.2

Requirements for packing and packaging Always follows the rules below for packing and packaging equipment for return: • •

• •

• • •

10.3

Maintain strict adherence to Electrostatic Discharge (ESD) practices when packing, packaging, and shipping electronic equipment and/or assemblies. In the absence of specific packing and packaging information, take all appropriate steps to ensure that items are adequately protected against damage during handling, storage and shipment. Cushioning and dunnage material must be used as necessary to prevent damage. Original packaging should be retained in the event the material requires reshipping. If the original packaging is not available, use a new box large enough to allow room for adequate cushioning material on all sides of the contents. Observe weight recommendations for the packaging. Weight recommendations are usually printed on the bottom of the box. Use enough cushioning material to ensure the contents cannot easily move when the box is shaken. Cushioning material must adhere to ESD requirements. Seal the box securely using pressure-sensitive or nylon-reinforced tape. Do not use masking tape, cellophane tape, or paper over-wrap.

Container requirements Use only containers that are in good condition. Wooden containers or skids that show decay and/or imperfections (such as warped surfaces, missing wood on corners) are unacceptable for use. Containers that have inadequate fastening, exposed nails, or strapping that is too loose or too tight are also unacceptable.

10.4

Labeling requirements Package labeling requirements are as follows: • • • • •

320

If re-using a shipping box, remove or cross out old labels or markings. Always include the recipient's zip code with a complete street address. Include a contact name and phone number (mandatory for international shipments). Include a complete return address. Put a duplicate label or other form of identification inside each package.

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

Troubleshooting Manual (TSMN)

•

Packing equipment for return

Verify and follow any other labeling requirements as specified by the chosen shipping service.

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

321

Abbreviations

Troubleshooting Manual (TSMN)

11 Abbreviations @CT

Web-based Craft Terminal

ACO

Alarm Cut Off

ADN

Add-Drop subsystem Non-upgradable

ADU

Add-Drop subsystem Upgradable

ADX

Add-Drop subsystem excluding wavelength blocker

AIS ALS

Automatic Laser Shutdown

ANSI

American National Standards Institute

APCD

Automatic Port Connection Detection

APRM

Automatic Power Reduction Mode

APS APSD AS

Application Program System Automatic Power Shutdown Autonomous System

ASE

Amplified Spontaneous Emission

ATT

Attenuator

avg. BER b2b BBE

average Bit Error Rate Back-to-back Background Block Error

BDI

Backward Defect Indication

BEI

Backward Error Indication

BER

Bit Error Rate

BFR

Broadcast Frames Received

BIP-8

Bit Interleaved Parity 8

Bw7R

Narrow-rack style 7R

BOL

Begin-Of-Life

CAN

Controller Area Network

CAX

Coupler Add in ADX

CBES CC CCM

322

Alarm Indication Signal

Corrected Bit Error Seconds Cross Connection Card Controller Module

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

Troubleshooting Manual (TSMN)

CCEP-1

Main controller card for OCU73 subsystem with TIF

CCMP-1

Main controller card for OCU73 subsystem without TIF

CCSP-1

Shelf controller card for OCU73 subsystem

CCU CDAN

Channel Connection Unit Coupler Drop Add, Non-Upgradable

CDM

Compressed Data Mode

CDN

Coupler Drop, Non-upgradable

CDR

Clock and Data Recovery

CDU

Coupler Drop, Upgradable

CDX

Couple Add device excluding wavelength blocker

CE CMI CMISE CNE COPA CPU

Communauté Européenne Code Mark Inversion Common Management Information Service Element Compound Network Element Connector Panel Central Processing Unit

CT

Craft Terminal

CV

Code Violations

DB

Data Base

DC

Direct Current

DCC

Data Communication Channel

DCCMo

Data Communication Channel Multiplex

DCCOo

Data Communication Channel Optical

DCF

Dispersion Compensating Fiber

DCM

Dispersion Compensation Module

DCN

Data Communication Network

DEMUX

Demultiplexer

DGE

Dynamic Gain/power Equalizer

DGF

Discarded GFP Frames

DMC

Dispersion Managed Cable

DPSK DSF

Abbreviations

Differential Phase Shift Keying Dispersion Shifted Fiber

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

323

Abbreviations

Troubleshooting Manual (TSMN)

D-SUB DTMF DWDM

Sub-Miniature Connector Dual Tone Multi Frequency Dense Wavelength Division Multiplexing

EAM

Electro-Absorption Modulator

ECC

Embedded Communication Channel

EDFA EF EFD EFEC EFT EM

Erbium Doped Fiber Amplifier Errored Frames Event Forwarding Discriminator Enhanced Forward Error Correction Errored Frames TFT Element Manager

EMC

Electromagnetic Compatibility

EMI

Electromagnetic Interference

EML

Element Management Layer

EMN

Expansion Manual

EM OS EMS EN EOCI EOL EOW ES

Element Managing Operating System Element Management System European Standard External Optical Connection Indicator End-Of-Life Engineering Order Wire Errored Seconds

ESB

Errored Super Blocks

ESD

(1) Electrostatic Discharge (2) Electrostatically Sensitive Device

ETH-CONN Eth-SB-s

Ethernet-Southbound interfaces

ETS

European Telecommunications Standards

ETSI

European Telecommunications Standards Institute

EXC

Excessive Bit Error Ratio

F FC

324

Ethernet Connector

Operating terminal interface Fiber Channel

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

Troubleshooting Manual (TSMN)

FCSE

Frame Check Sequence Errors

FCC

Federal Communications Commission

FEC

Forward Error Correction

FICON FR

Fiber Channel Connection Frames Received

FRO

Frames RCV OK

FSU

Flow Sensor Unit

FTO

Frames TMT OK

FTP

File Transfer Protocol

FTP(S) FW G-AIS GCC GE

File Transfer Protocol over SSL Firmware Generic Alarm Indication Signal Generic Communication Channel Gigabit Ethernet

GHz

Giga-Hertz (1 GHz = 1 000 000 000 Hz)

GMT

Greenwich Mean Time

GNE

Gateway Network Element

GND

Ground

GR

Generic Requirements

GTC

Gain Tilt Compensator

GUI HDLC

Graphical User Interface High Level Data Link Control

HDS

Next Generation Transponders

HRL

High Return Loss (connector type)

HTTP

Hypertext Transfer Protocol

HU

Height Unit

HW

Hardware

I01T10G-1

10 G Transponder card for OCU73 subsystem

I08T10G-1

10 G Muxponder card for OCU73 subsystem

I04T2G5-1

2.5 G Transponder / Regenerator card for OCU73 subsystem

ICMA ID

Abbreviations

Interconnect, Configuration and Mechanical Assembly Identification

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

325

Abbreviations

Troubleshooting Manual (TSMN)

IDN

Internal Data Network

IEC

International Electrotechnical Commission

IF

Interface

IP

Internet Protocol

ISL

Interstage Loss

ISLP

Interstage Loss Problem

IS-IS

Integrated system for fulfilling the infrastructure requirements of fiber optic systems

ITU

International Telecommunication Unit

ITU-T

Telecommunication Standardization Sector of ITU

ITMN

Installation and Test Manual

JRE

Java Runtime Environment

LAN

Local Area Network

LED

Light Emitting Diode

LH

Long Haul

LCC

Local Card Controller

LCT

Local Craft Terminal

LF

Link Failures

LOC

Loss of Carrier

LOF

Loss of Frame

LOM

(1) Loss of Multiframe (2) List of Material

LOS

Loss of Signal

LOSi

Loss of Signals

LOSy

Loss of Syncs

LVD LS MAF max. BER

Lambda Shifted fiber Management Application Functions maximum Bit Error Rate

MCF

Message Communication Function

MCU

Main Control Unit

MFR

Multicast Frames Received

MIBS

326

Low Voltage Disconnect (device)

Management Information Base

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

Troubleshooting Manual (TSMN)

MM NB

Master MCU North Bound (COPA connector)

MM SB

Master MCU South Bound (COPA connector)

MS-AIS

Multiplex Section AIS

MSN

Multi Service Node

MUX

Multiplexer

MWB

Multi-wavelength Blocker

MTS

Multiwavelength Transport System

NAT

Network Address Translation

NATP NC NCT NE

Network Address Translation with Port forwarding Normally Closed Network Craft Terminal Network Element

NEAP

Network Element Alarm Panel

NEBS

Network Equipment Building System

NIC

Network Interface Card

NMA

Network Management Agent

NML

Network Management Layer

NMS

Network Management System

NO NSAP

Normally Opened Network Service Access Point

NSIF

Network and Services Integration Forum

NTP

Network Time Protocol

NZDSF QF OADM

Non Zero Dispersion Shifted Fiber Operating terminal interface Optical Add Drop Multiplexer

OADM100N

100% Optical Add Drop Multiplexer Non-upgradable

OADM100U

100% Optical Add Drop Multiplexer Upgradable

OAM&P OC OCAC

Abbreviations

Operation, Administration, Maintenance and Provisioning Optical Carrier Optical Channel Amplifier for C band

OCASC

Optical Channel Amplifier and Switch for C band

OC-192

Optical Carrier 192

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

327

Abbreviations

Troubleshooting Manual (TSMN)

OC-48

Optical Carrier 48

OC-768

Optical Carrier 768

OCP OCR10R

Optical Channel Repeater 10 Gbit/s Regenerator

OCR10T

Optical Channel Repeater 10 Gbit/s Transponder

OCS

Optical Channel Switch

OCU

Optical Channel Unit

OCU40

Subagent for Optical Channel Unit - 40G (OTS-4000)

OCU73

Subagent for Optical Channel Unit (HDS)

OD10

Optical Demultiplexer, 10 channels

OD20

Optical Demultiplexer, 20 channels

ODA10

Optical Demultiplexer with VOAs, 10 channels

ODA20

Optical Demultiplexer with VOAs, 20 channels

ODB

Optical Duobinary

ODU

Optical Data Unit

OEM

Original Equipment Manufacturer

OH OLC OLI

Overhead Optical Link Commissioning Optical Line Interface

OLIINC

Optical Line Interface Inline amplifier (standard version) for C band

OLIMINC

Optical Line Interface Inline amplifier (compact version) for C band

OLIMTBNC

Optical Line Interface Terminal Booster (compact version) for C band

OLIMTPNC

Optical Line Interface Terminal Preamplifier (compact version) for C band

OLISINC

Optical Line Interface Inline amplifier (basic version) for C band systems

OLISTBNC

Optical Line Interface Short-span Terminal Booster (basic version) for C band

OLISTPNC

Optical Line Interface Short-span Terminal Preamplifier (basic version) for C band

OLITBNC

Optical Line Interface Terminal Booster (standard version) for C band

OLITPNC

Optical Line Interface Terminal Preamplifier (standard version) for C band

OLR

Optical Line Repeater

OLRB

Optical inLine Repeater Basic

OLRU

Optical inLine Repeater Unidirectional

OM

328

Optical Channel Protection

Optical Multiplexer

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

Troubleshooting Manual (TSMN)

OM10

Optical Multiplexer with VOAs, 10 channels

OM20

Optical Multiplexer with VOAs, 20 channels

OMD2IC

Optical Multiplexer/Demultiplexer, 2 Interleavers for C band

OMDFC

Optical Multiplexer/Demultiplexer Filters for C band

OMD4

Optical Multiplexer/Demultiplexer with four channel band filter

OMDFIC

Optical Multiplexer/Demultiplexer Filters/Interleavers for C band

OMDIFC

Optical Multiplexer/Demultiplexer Interleavers/Filters for C band

OMN

Operating Manual

OMS

Optical Multiplex Section

OOB EFEC OPA OPAPC OPS OPS/INE

Out-of-Band Enhanced Forward Error Correction Optical Performance Analyzer Optical Performance Analyzer “Power” card for C band Optical Physical Section Operations System / Intelligent Network

OPU

Optical Payload Unit

ORO

Octets RCV OK

OS OSA OSAR OSC OSCT OSCTUI OSCTUT OSI

Operating System Optical Spectrum Analyzer Optical Signal-to-accumulated-ASE Ratio Optical Supervisory Channel Optical Supervisory Channel Termination Optical Supervisory Channel Termination Unidirectional for the Intermediate nodes Optical Supervisory Channel Termination Unidirectional for the Terminal sites Open System Interconnection

OSNR

Optical Signal to Noise Ratio

OSPF

Open Shortest Path First

OSS

Operational Support Systems

OTH

Optical Transport Hierarchy

OTN

Optical Transport Network

OTO

Octets TMT OK

OTS

Optical Transmission System

OTS-4011

Abbreviations

10/40 Gbit/s multiplexing transponder

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

329

Abbreviations

Troubleshooting Manual (TSMN)

OTS-4040

40 Gbit/s transponder

OTS-4400

Unidirectional 40 Gbit/s regenerator

OTS-4510

Dispersion Compensation Module (DCM)

OTS-4520

Tunable Dispersion Compensation Module (TDCM)

OTS-4540

Polarization Mode Dispersion Compensator (PMDC)

OTS-4700

Shelf controller

OTT

Optical Transport Termination

OTTC

Optical Transport Terminal Compound

OTTU

Optical Transport Terminal Unidirectional

OTU PABX PC

Optical Transport Unit Private Automatic Branch Exchange Personal Computer

PAT

Port Allocation Table

PCB

(1) Peripheral Control Bus (2) Printed Circuit Board

PCM

Pulse Code Modulation

PDF

Portable Document Format

PDH

Plesiochronous Digital Hierarchy

PDL

Polarization Dependent Loss

PDP

Power Distribution Panel

PDU

Power Distribution Unit

PHF

Power High Failure

PLM

Payload Mismatch

PM PMD PMDC PPP PQMC

330

Performance Monitoring Polarization Mode Dispersion Polarization Mode Dispersion Compensator Point-to-Point Protocol Power Equalizer Module

PSC

Protection Switching Command

PSU

Power Supply Unit

PUMPA

Pump, 1480 nm

PUMPB

Pump, 1495 nm

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

Troubleshooting Manual (TSMN)

PUMPC PXC Q Q3 Q3 GNE QD2 Q-F

Pump, 1465 nm Photonic Cross Connect Interface to a Telecommunication Management Network Standardized Interface for Management Information Exchange Q3 Gateway Network Element System interface with SISA system Operating Terminal Interface

QoS

Quality of Service (alarms)

QST

Proprietary Q Interface

RAM

Random Access Memory

RDS

Relative Description Slope

RFC

Request For Comments

RID RPUMP RPUMPC RTC Rx SAB SABM SB SBS SC SDH SDRAM

Router-ID Raman Pump Raman Pump for the C band Real Time Clock Receive signal Subrack Address Board Subrack Address Board Modified Southbound Stimulated Brillouin Scattering Shelf Controller Synchronous Digital Hierarchy Synchronous Dynamic RAM

SEFS

Severely Errored Framing Seconds

SELV

Safety Extra Low Voltage

SEMF

Synchronous Equipment Management Function

SerDes SES S-FEC

Abbreviations

Serializer / Deserializer Severely Errored Seconds Super Forward Error Correction

SFP

2.5 Gbit/s Small Form-Factor Pluggable module

SID

Source Identifier

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

331

Abbreviations

Troubleshooting Manual (TSMN)

SIPAC SMU SNMP SONET SPI

Siemens Packaging System Subrack Management Unit Simple Network Management Protocol Synchronous Optical Network Synchronous Peripheral Interface

SPM

Self Phase Modulation

SRD

Double-Row Shelf

SRO

OCU Shelf

SRS

(1) Single-Row Shelf (2) Stimulated Raman Scattering

SSH

Secure Shell

SSL

Secure Socket Layer

SUB-ID SSM SSMF SU sV.11 SW Tbit/s TC

Synchronization Status Message Standard Single Mode Fiber System Unit Similar V.11 Interface Software Terabit per second (1 Tbit/s = 1000 Gbit/s) Telecommunications Center

TCA

Threshold Crossing Alert

TCM

Tandem Connection Monitoring

TCP

Transmission Control Protocol

TCP/IP TDCM

Transmission Control Protocol/Internet Protocol Tunable Dispersion Compensation Module

TDM

Time Division Multiplexing

TED

Technical Description

TEX

Ten Gigabit Multiplexer

TF

332

Subsystem ID

Transmit Fail (Alarm)

THz

Terahertz (1 THz = 1 000 000 000 000 Hz)

TID

Target Identifier

TIF

Telemetry Interface

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

Troubleshooting Manual (TSMN)

TIM

Trace Identifier Mismatch

TL1

Transaction Language 1

TL1 GNE TMN TMN-OS TNMS

TL1 Gateway Network Element Telecommunication Management Network Telecommunication Management Network Operating System Telecommunication Network Management System

TNMS CT

Telecommunication Network Management System Craft Terminal

TNMS DX

Telecommunication Network Management System Domain Unix

TOH

Transport Overhead

TSC

Transient Suppression for C band

TSCh

Transient Suppression Channel

TSMN

Troubleshooting Manual

TTI Tx

Trail Trace Identifier Transmit

UAP

User Access Privilege

UAS

Unavailable Seconds

UDCM

Abbreviations

Unidirectional Dispersion Compensation Module

UDCMB

Unidirectional Dispersion Compensation Module, Fiber Bragg Grating technology (FBG)

UDCMC

Unidirectional Dispersion Compensation Module for C band

UFR UL

Unicast Frames Received Underwriters Lab

ULH

Ultra Long Haul

UMN

User Manual

USB

Universal Serial Bus

UTC

Universal Time Coordinated

VCDB VM VOA VOA2

Variable Configuration Data Block Virtual Machine Variable Optical Attenuator Variable Optical Attenuator 2 (card)

WAN

Wide Area Network

WB

Wavelength Blocker

WBAN

Wavelength Blocker Add, Non-upgradable

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

333

Abbreviations

Troubleshooting Manual (TSMN)

WBAU

Wavelength Blocker Add, Upgradable

WBN

Wavelength Blocker, Non-upgradable

WDM

Wavelength Division Multiplexing

WSSC

334

Wavelength Selective Switch

XFP

10 Gbit/s Small Form-Factor Pluggable module

XML

Extensible Markup Language

XPM

Cross Phase Modulation

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

Troubleshooting Manual (TSMN)

Index S Safety instructions 19

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

335