ned 3

Nokia Siemens Networks WCDMA RAN, Rel. RU10, System Library, v. 6

Troubleshooting Node B

DN70580522

Issue 01AApproval Date 2009/09/18

Confidential

2 DN70580522Issue 01A


Id:0900d805806e513eConfidential

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 DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, 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 2009. 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 Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

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

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

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

DN70580522 Issue 01A

3



Table of contentsThis document has 313 pages.

Reason for Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.1 Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.2 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.2.1 Managed Object Class / Hardware Type . . . . . . . . . . . . . . . . . . . . . . . . 281.2.2 Event Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.2.3 Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.2.4 Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.2.4.1 Fault Escalation Strategy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.2.4.2 Configuration of Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.3 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.4 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2 200506 - Node B system start-up malfunction due to software/hardware problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3 200507 - System halt due to software watchdog detected problem . . . 333.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

4 200508 - System halt due to detected application process error. . . . . . 344.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

5 200509 - System halt due to detected hardware exception. . . . . . . . . . 355.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

6 200510 - System halt due to detected software loading malfunction. . . 366.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

7 200656 - Iub link broke down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

8 200657 - SSCOP sent overrun . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

4 DN70580522Issue 01A



9 200658 - Transmit bandwidth limit for NBAP reached . . . . . . . . . . . . . . 409.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

10 200659 - Core Controller overload protection activated . . . . . . . . . . . . . 4110.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4110.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4110.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

11 200660 - SSCOP Dedicated Link send overrun . . . . . . . . . . . . . . . . . . . 4211.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4211.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4211.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

12 200661 - SSCOP Common Link send overrun . . . . . . . . . . . . . . . . . . . . 4312.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4312.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4312.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

13 200706 - An error occurred in the nbDatabase. . . . . . . . . . . . . . . . . . . . 4413.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4413.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4413.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

14 200707 - A warning occurred in the nbDatabase . . . . . . . . . . . . . . . . . . 4614.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4614.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4614.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

15 200905 - VSWR alarm Low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4715.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4715.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4715.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

16 200906 - VSWR alarm High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4916.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4916.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4916.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

17 200907 - RX alarm Low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5117.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5117.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5117.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

18 200908 - RX alarm High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5318.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5318.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5318.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

19 200909 - TMA switched off, but not defective. . . . . . . . . . . . . . . . . . . . . 5519.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5519.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55


5



19.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

20 200910 - TMA feeder alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5620.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5620.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5620.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

21 200911 - TMA DC alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5821.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5821.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5821.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

22 200914 - Fan unit failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6022.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6022.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6022.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

23 200915 - Site input alarm detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6223.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6223.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6223.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

24 200916 - Rack Door open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6524.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6524.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6524.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

25 200918 - PA combiner interface fault. . . . . . . . . . . . . . . . . . . . . . . . . . . 6625.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6625.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6625.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

26 200919 - Failure in the DC supply of PA . . . . . . . . . . . . . . . . . . . . . . . . 6726.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6726.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6726.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

27 200920 - High temperature of PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6827.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6827.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6827.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

28 200921 - Over temperature of PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7028.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7028.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7028.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

29 200922 - RF performance not being met due to bad linearization. . . . . 7229.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7229.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7229.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

30 200923 - Internal failure of PA detected . . . . . . . . . . . . . . . . . . . . . . . . 73

6 DN70580522Issue 01A



30.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7330.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7330.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

31 200924 - Input power level of LPA too high but LPA can still hold its RF specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74


32 200925 - Input power level of PA too high . . . . . . . . . . . . . . . . . . . . . . . 7532.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7532.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7532.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

33 200926 - CPU failure of baseband card . . . . . . . . . . . . . . . . . . . . . . . . . 7633.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7633.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7633.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

34 200927 - Volatile memory failure of baseband card . . . . . . . . . . . . . . . . 7734.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7734.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7734.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

35 200928 - Non-volatile memory failure of baseband card . . . . . . . . . . . . 7835.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7835.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7835.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

36 200929 - DSP failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7936.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7936.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7936.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

37 200931 - FPGA failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8037.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8037.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8037.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

38 200932 - Control FPGA failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8138.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8138.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8138.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

39 200933 - External timing signal failure . . . . . . . . . . . . . . . . . . . . . . . . . . 8239.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8239.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8239.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

40 200934 - Failure of the RF part of the TRX. . . . . . . . . . . . . . . . . . . . . . . 8340.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8340.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83


7



40.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

41 200935 - LVDS Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8441.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8441.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8441.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

42 200936 - Local bus failure around the CPU. . . . . . . . . . . . . . . . . . . . . . 8542.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8542.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8542.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

43 200937 - FTP connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8643.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8643.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8643.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

44 200938 - CRC error during software image check. . . . . . . . . . . . . . . . . 8744.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8744.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8744.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

45 200939 - Static configuration file CRC check failed. . . . . . . . . . . . . . . . 8845.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8845.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8845.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

46 200940 - Software activation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8946.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8946.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8946.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

47 200941 - Internal clock failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9047.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9047.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9047.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

48 200942 - Configuration file inconsistent. . . . . . . . . . . . . . . . . . . . . . . . . 9148.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9148.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9148.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

49 200943 - IOR file inconsistent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9249.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9249.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9249.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

50 200944 - FTP put failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9350.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9350.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9350.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

51 200945 - FTP manage failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

8 DN70580522Issue 01A




52 200946 - Still alive supervision failure. . . . . . . . . . . . . . . . . . . . . . . . . . . 9552.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9552.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9552.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

53 200947 - Failure in the DC supply of DUAMCO . . . . . . . . . . . . . . . . . . . 9653.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9653.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9653.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

54 200948 - CORBA communication failed . . . . . . . . . . . . . . . . . . . . . . . . . 9754.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9754.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9754.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

55 200949 - Internal CORBA call failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9855.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9855.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9855.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

56 200950 - Timeout for request or modification . . . . . . . . . . . . . . . . . . . . . 9956.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9956.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9956.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

57 200951 - Status notification undefined . . . . . . . . . . . . . . . . . . . . . . . . . 10057.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10057.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10057.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

58 200952 - Maximum number of resets exceeded. . . . . . . . . . . . . . . . . . 10158.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10158.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10158.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

59 200953 - CAN bus off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10259.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10259.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10259.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

60 200954 - No message response on CAN . . . . . . . . . . . . . . . . . . . . . . . 10360.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10360.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10360.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

61 200955 - Mount supervision failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10461.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10461.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10461.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104


9



62 200956 - Watch dog timer expired. . . . . . . . . . . . . . . . . . . . . . . . . . . . 10562.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10562.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10562.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

63 200957 - Internal CAN processing failure . . . . . . . . . . . . . . . . . . . . . . 10663.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10663.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10663.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

64 200958 - Timer for the reset supervision expired . . . . . . . . . . . . . . . . 10764.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10764.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10764.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

65 200959 - Missing response from baseband card. . . . . . . . . . . . . . . . . 10865.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10865.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10865.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

66 200960 - Invalid response from baseband card. . . . . . . . . . . . . . . . . . 10966.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10966.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10966.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

67 200961 - Firmware download failure . . . . . . . . . . . . . . . . . . . . . . . . . . 11067.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11067.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11067.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

68 200980 - Invalid MO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11168.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11168.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11168.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

69 200981 - MO not mounted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11269.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11269.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11269.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

70 200982 - Invalid command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11370.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11370.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11370.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

71 200983 - Invalid parameter in command . . . . . . . . . . . . . . . . . . . . . . . 11471.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11471.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11471.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

72 200984 - Firmware download access file error . . . . . . . . . . . . . . . . . . 11572.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11572.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

10 DN70580522Issue 01A



72.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

73 200985 - CAN transaction error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11673.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11673.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11673.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

74 200986 - Temperature out of range in upper direction . . . . . . . . . . . . . 11774.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11774.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11774.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

75 200987 - Hardware parameter invalid. . . . . . . . . . . . . . . . . . . . . . . . . . 11975.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11975.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11975.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

76 200988 - Response unknown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12076.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12076.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12076.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

77 200989 - No CORBA proxy available for LRU . . . . . . . . . . . . . . . . . . . 12177.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12177.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12177.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

78 200990 - No still alive response from LRU . . . . . . . . . . . . . . . . . . . . . . 12278.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12278.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12278.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

79 200991 - Duplex error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12379.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12379.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12379.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

80 200992 - Software error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12480.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12480.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12480.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

81 200993 - Unexpected alarm status bit . . . . . . . . . . . . . . . . . . . . . . . . . 12581.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12581.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12581.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

82 200994 - Hardware Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12682.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12682.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12682.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

83 200995 - High Temperature Limit (Ht3) reached . . . . . . . . . . . . . . . . . 127


11



83.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12783.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12783.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

84 200996 - Critical Temperature Limit (Ht4) reached . . . . . . . . . . . . . . . 12984.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12984.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12984.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

85 200997 - Lower Temperature Limit (Ht0) reached. . . . . . . . . . . . . . . . 13185.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13185.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13185.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

86 200998 - Temperature out of range in lower direction . . . . . . . . . . . . . 13286.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13286.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13286.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

87 200999 - Unexpected loss of unlocked LRU . . . . . . . . . . . . . . . . . . . . 13387.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13387.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13387.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

88 201001 - RET power off. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13588.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13588.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13588.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

89 201002 - RET feeder alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13789.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13789.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13789.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

90 201003 - RET hardware alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13990.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13990.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13990.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

91 201004 - ALD communication error . . . . . . . . . . . . . . . . . . . . . . . . . . . 14091.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14091.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14091.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

92 201005 - RET is not calibrated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14292.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14292.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14292.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

93 201006 - RET is not scaled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14393.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14393.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14393.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

12 DN70580522Issue 01A



94 201007 - RET lost position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14494.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14494.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14494.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

95 201008 - RET received wrong configuration data. . . . . . . . . . . . . . . . . 14595.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14595.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14595.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

96 201009 - A mounted card is not used to its full capacity. . . . . . . . . . . . 14796.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14796.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14796.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

97 201010 - An incompatible card is mounted. . . . . . . . . . . . . . . . . . . . . . 14897.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14897.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14897.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

98 201011 - Alignment of standby CC failed . . . . . . . . . . . . . . . . . . . . . . . 14998.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14998.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14998.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

99 201012 - Timeout for connection to standby CC . . . . . . . . . . . . . . . . . 15099.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15099.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15099.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

100 201013 - Connection failure to standby CC . . . . . . . . . . . . . . . . . . . . . 151100.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151100.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151100.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

101 201014 - Standby CC forced to become active due to unreachable active CC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

101.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152101.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152101.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

102 201015 - Preparation of data to be aligned has failed . . . . . . . . . . . . . 153102.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153102.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153102.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

103 201016 - Non-fatal internal LVDS failure . . . . . . . . . . . . . . . . . . . . . . . 154103.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154103.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154103.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

104 201017 - Digital input power level too high, but gain reduced . . . . . . . 155104.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155


13



104.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155104.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

105 201018 - The LRU could not process a message from CC . . . . . . . . . 156105.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156105.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156105.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

106 201019 - Gain below threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157106.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157106.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157106.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

107 201020 - Loss of single DRIF interface detected. . . . . . . . . . . . . . . . . 158107.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158107.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158107.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

108 201022 - Alignment of file data has failed . . . . . . . . . . . . . . . . . . . . . . 159108.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159108.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159108.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

109 201023 - Bad signal quality of single DRIF interface detected . . . . . . 160109.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160109.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160109.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

110 201024 - Bad signal quality of all DRIF interfaces detected . . . . . . . . 162110.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162110.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162110.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

111 201025 - PID could not be read or is corrupted . . . . . . . . . . . . . . . . . . 164111.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164111.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164111.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

112 201026 - LRU sent illegal parameter . . . . . . . . . . . . . . . . . . . . . . . . . . 165112.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165112.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165112.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

113 201027 - LRU could not process a message from CC containing data from DB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166


114 201028 - Node B system clock hardware failure . . . . . . . . . . . . . . . . . 168114.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168114.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168114.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

14 DN70580522Issue 01A



115 201029 - MEF blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169115.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169115.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169115.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

116 201030 - Invalid hardware capacity licensing value . . . . . . . . . . . . . . . 170116.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170116.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170116.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

117 201031 - Wrong combination of licensed cards . . . . . . . . . . . . . . . . . . 171117.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171117.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171117.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

118 201032 - Not all cells are licensed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172118.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172118.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172118.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

119 201033 - PID could not be read or is corrupted - non-fatal . . . . . . . . . . 173119.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173119.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173119.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

120 201034 - Booster’s Fan unit failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174120.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174120.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174120.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

121 201035 - MEF completely blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175121.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175121.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175121.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

122 201036 - RRHs unable to establish communication links with the expected number of PSRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176


123 201037 - ALD unspecified error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177123.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177123.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177123.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

124 201038 - Resource conflict between CP and OAM . . . . . . . . . . . . . . . 178124.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178124.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178124.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

125 201039 - Inconsistency between hardware license and configuration . 179125.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179


15



125.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179125.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

126 201040 - Wrong cabling of LRU detected . . . . . . . . . . . . . . . . . . . . . . 180126.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180126.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180126.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

127 201041 - Test channels have been lost . . . . . . . . . . . . . . . . . . . . . . . . 181127.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181127.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181127.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

128 201042 - Incompatible Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182128.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182128.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182128.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

129 201043 - Missing software image . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183129.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183129.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183129.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

130 201044 - Non fatal configuration failure . . . . . . . . . . . . . . . . . . . . . . . . 184130.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184130.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184130.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

131 201045 - Fatal hardware error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185131.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185131.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185131.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

132 201046 - No ATM connection for OAM Autoconfiguration. . . . . . . . . . 186132.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186132.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186132.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

133 201047 - Fatal BB software failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . 188133.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188133.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188133.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

134 201048 - Non-fatal BB software failure . . . . . . . . . . . . . . . . . . . . . . . . 189134.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189134.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189134.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

135 201049 - Non-fatal DSP failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190135.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190135.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190135.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

16 DN70580522Issue 01A



136 201050 - Major hardware failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191136.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191136.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191136.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

137 202007 - A scanner could not be initialized . . . . . . . . . . . . . . . . . . . . . 192137.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192137.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192137.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

138 202008 - The temporary measurement results could not be stored . . . 193138.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193138.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193138.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

139 202009 - Unable to request measurement results . . . . . . . . . . . . . . . . 194139.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194139.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194139.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

140 202010 - The ScanCo could not be initialized . . . . . . . . . . . . . . . . . . . 195140.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195140.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195140.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

141 202011 - The final results files could not be generated . . . . . . . . . . . . 196141.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196141.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196141.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

142 202014 - The first sccpchUsageRatio Quality of Service alarm has oc-curred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197


143 202015 - The second sccpchUsageRatio Quality of Service alarm has oc-curred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198


144 202016 - The first prachUsageRatio Quality of Service alarm has occurred199


145 202017 - The second prachUsageRatio Quality of Service alarm has oc-curred . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200



17



146 202018 - The first cpUsageRatio Quality of Service alarm has occurred . 201


147 202019 - The second cpUsageRatio Quality of Service alarm has occurred202


148 202020 - The first prachCrciFailures Quality of Service alarm has occurred203


149 202021 - The second prachCrciFailures Quality of Service alarm has oc-curred. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204


150 202022 - The first bbUsageRatioLicense Quality of Service alarm has oc-curred. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205


151 202023 - The second bbUsageRatioLicense Quality of Service alarm has occurred. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206


152 202024 - The first bbUsageRatioHw Quality of Service alarm has occurred207


153 202025 - The second bbUsageRatioHw Quality of Service alarm has oc-curred. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208


154 202026 - The first e1Crc Quality of Service alarm has occurred . . . . . 209154.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209154.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209154.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

18 DN70580522Issue 01A



155 202027 - The second e1Crc Quality of Service alarm has occurred . . 211155.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211155.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211155.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

156 202028 - The first vcUsageRatio Quality of Service alarm has occurredA-larm added . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213


157 202029 - The second vcUsageRatio Quality of Service alarm has occurred214


158 202056 - Loss Of Signal on Physical Link . . . . . . . . . . . . . . . . . . . . . . 215158.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215158.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215158.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

159 202057 - Loss Of Frame on Physical Link . . . . . . . . . . . . . . . . . . . . . . 217159.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217159.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217159.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

160 202058 - Loss Of Cell Delineation on Physical Link . . . . . . . . . . . . . . . 220160.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220160.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220160.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

161 202059 - Alarm Indication Signal on Physical Link . . . . . . . . . . . . . . . . 223161.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223161.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223161.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

162 202060 - Remote Alarm Indication on Physical Link . . . . . . . . . . . . . . 225162.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225162.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225162.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

163 202061 - Loss of Multi Frame Alarm Indication on E1 Physical Link . . 227163.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227163.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227163.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

164 202062 - Line Alarm Indication Signal Indication on STM1 Physical Link .229



19



165 202063 - Line Remote Defect Indication on STM1 Physical Link . . . . 231165.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231165.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231165.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

166 202064 - Path Loss of Pointer Indication on STM1 Physical Link . . . . 233166.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233166.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233166.3 fcTroubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

167 202065 - Path Alarm Indication Signal on STM1 Physical Link . . . . . . 235167.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235167.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235167.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

168 202066 - Path Remote Defect Indication on STM1 Physical Link . . . . 237168.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237168.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237168.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

169 202068 - Signal Label Mismatch Indication on STM1 Physical Link . . 239169.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239169.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239169.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

170 202070 - Signal Degrade Indication on STM1 Physical Link. . . . . . . . 240170.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240170.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240170.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

171 202071 - Excessive Bit Error Rate Indication on STM1 Physical Link. 242171.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242171.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242171.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

172 202072 - Alarm Indication Signal on an ATM VC . . . . . . . . . . . . . . . . 244172.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244172.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244172.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

173 202073 - Remote Defect Indication on an ATM VC. . . . . . . . . . . . . . . 246173.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246173.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246173.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

174 202074 - SSCOP Failure Indication on an ATM VC used by ALCAP or NBAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248


175 202075 - Alarm Indication Signal on an ATM VP. . . . . . . . . . . . . . . . . 250175.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

20 DN70580522Issue 01A



175.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250175.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

176 202076 - Remote Defect Indication on an ATM VP . . . . . . . . . . . . . . . 252176.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252176.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252176.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

177 202077 - ALCAP PVC Out Of Service Indication . . . . . . . . . . . . . . . . . 254177.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254177.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254177.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

178 202078 - Loss Of Delay Synchronization on IMA Link . . . . . . . . . . . . . 255178.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255178.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255178.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

179 202079 - Loss Of IMA Frame on IMA Link . . . . . . . . . . . . . . . . . . . . . . 256179.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256179.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256179.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

180 202080 - Remote Failure Indicator on IMA Link . . . . . . . . . . . . . . . . . . 257180.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257180.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257180.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

181 202081 - IMA Tx link is detected as mis-connected . . . . . . . . . . . . . . . 258181.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258181.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258181.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

182 202082 - IMA Rx link is detected as mis-connected . . . . . . . . . . . . . . . 259182.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259182.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259182.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

183 202083 - Tx fault declared at the NE on IMA Link . . . . . . . . . . . . . . . . 260183.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260183.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260183.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

184 202084 - Rx fault declared at the NE on IMA Link . . . . . . . . . . . . . . . . 261184.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261184.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261184.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

185 202085 - FE has reported Tx-Unusable on IMA Link . . . . . . . . . . . . . . 262185.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262185.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262185.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262


21



186 202086 - FE has reported Rx-Unusable on IMA Link . . . . . . . . . . . . . 263186.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263186.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263186.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

187 202087 - Startup FE reported on IMA Group. . . . . . . . . . . . . . . . . . . . 264187.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264187.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264187.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

188 202088 - Config Abort reported on IMA Group . . . . . . . . . . . . . . . . . . 265188.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265188.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265188.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

189 202089 - Config Abort FE reported on IMA Group . . . . . . . . . . . . . . . 266189.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266189.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266189.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

190 202090 - Insufficient Links reported at NE on IMA Group . . . . . . . . . . 267190.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267190.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267190.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

191 202091 - Insufficient Links at FE reported on IMA Group . . . . . . . . . . 268191.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268191.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268191.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

192 202092 - Group Blocked at FE reported on IMA Group. . . . . . . . . . . . 269192.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269192.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269192.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

193 202093 - Timing Synch error reported on IMA Group . . . . . . . . . . . . . 270193.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270193.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270193.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

194 202095 - The Near End IMA has detected an invalid version set by the Far End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271


195 202097 - Loss of Continuity detected on an ATM VP . . . . . . . . . . . . . 272195.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272195.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272195.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

196 202098 - CRC4 not used by FE reported on E1TTP . . . . . . . . . . . . . . 273196.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

22 DN70580522Issue 01A




197 202106 - Software activation failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . 274197.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274197.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274197.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

198 202107 - Database activation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . 275198.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275198.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275198.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

199 202108 - Reliable software started without prior explicit activation . . . 276199.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276199.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276199.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

200 202109 - Reliable database started without prior explicit activation . . . 277200.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277200.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277200.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

201 202358 - CAN received an unexpected message . . . . . . . . . . . . . . . . 278201.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278201.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278201.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

202 202360 - A necessary resource is missed . . . . . . . . . . . . . . . . . . . . . . 279202.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279202.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279202.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

203 202406 - ALCAP protocol error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280203.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280203.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280203.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

204 202431 - ALCAP transaction to RNC initiated by transport timed out . 281204.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281204.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281204.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

205 202432 - ALCAP transaction to RNC initiated by NBAP timed out . . . . 282205.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282205.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282205.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

206 202433 - Configuration misalignment between RNC and CPA . . . . . . 283206.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283206.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283206.3 Troubleshooting (LMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283


23



207 202434 - RNC Establish Request message received which is invalid or cannot be handled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284


208 202435 - CPA to RNC communication (socket) problems. . . . . . . . . . 285208.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285208.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285208.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

209 202506 - Node B system clock in holdover mode . . . . . . . . . . . . . . . . 286209.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286209.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286209.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

210 202507 - Node B system clock in medium accuracy . . . . . . . . . . . . . . 288210.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288210.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288210.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

211 262041 - System call unsuccessful . . . . . . . . . . . . . . . . . . . . . . . . . . . 290211.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290211.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290211.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

212 262042 - Unexpected software error . . . . . . . . . . . . . . . . . . . . . . . . . . 291212.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291212.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291212.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

213 262043 - Error from device driver received . . . . . . . . . . . . . . . . . . . . . 292213.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292213.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292213.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

214 262044 - Not enough memory to initialize software. . . . . . . . . . . . . . . 293214.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293214.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293214.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

215 262045 - Memory allocation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 294215.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294215.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294215.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

216 262046 - Unexpected exception handling . . . . . . . . . . . . . . . . . . . . . . 295216.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295216.2 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295216.3 Troubleshooting (LMT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

217 262047 - Uncaught exception handling . . . . . . . . . . . . . . . . . . . . . . . . 296217.1 Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

24 DN70580522Issue 01A




218 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297218.1 Fault management in the NB/RSxxx. . . . . . . . . . . . . . . . . . . . . . . . . . . 297218.1.1 Equipment fault management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300218.1.2 Transport network fault management . . . . . . . . . . . . . . . . . . . . . . . . . . 301218.2 Mapping of NB/RSxxx alarms to NetAct alarms . . . . . . . . . . . . . . . . . . 304


25



List of tablesTable 1 Mapping of NB/RSxxx alarms to NetAct alarms . . . . . . . . . . . . . . . . . 304

26 DN70580522Issue 01A


Id:0900d805806241c3Confidential

Reason for Update

Reason for UpdateIssue History

Note that the issue numbering system is changing. For more information, see Guide to WCDMA RAN Documentation.

DetailsAll– First issue for new release.

201047 - Fatal BB software failure (133)

– Severity of 201047 failure has been updated.

Issue Number Date of Issue Reason for Update

01 09/2008 First issue for new release.

01A 09/2009 Severity of 201047 failure has been updated.


27

Troubleshooting Node B Introduction

Id:0900d8058022b398Confidential

1 Introductiong This document is prepared as a standard edition that may include descriptions not

applying to your system.

The goal of this manual is to describe all alarms and system information which can be generated by the Node B. The “Troubleshooting Node B” manual provides information on handling these alarms via the LMT.

A description of the general UTRAN maintenance concept and an example of how to solve an alarm are provided in this manual’s “Appendix”, section “Solving and clearing an alarm”.

The software attempts to provide a precise error description for each alarm containing all information for the operator and manufacturer in order to rapidly localize, investigate and eliminate the fault. There is no relation between the number of described faults and their frequency of occurrence in the system.

Error ceased messages clear all alarms for a specific probable cause of one object. Whenever a diagnosis of a faulty object fails, the operator has to replace the faulty module (specified in the test report) following the procedure described in the according maintenance manual.

This manual is organized according to the error-IDs where each one forms a chapter with: • Title • Failure Event Report • Error Description • Troubleshooting (LMT)

Suppression of toggling Node B alarmsOperators at the Node B can reduce the amount of alarms at the Itf-B interface to the really important alarms by means of alarm suppression. Applying alarm suppression, operators can prevent the system from alarms which fill the alarm buffers but do not provide further important information. Alarms which are raised and cleared in short periods (toggling alarms) and which do not give more detailed information on fault analysis and fault location will thus be suppressed.

The toggling condition is indicated by a specifically modified “additionalText”.

To achieve the suppression of toggling alarms, a specific algorithm is used. This algo-rithm detects toggling alarms as such and suppresses the toggling alarm notifications after a specified time. The suppression algorithm works as follows:

If the managed object (MO) raises the same alarm (see: Failure Event Report) for a specified number of times (x) within a predefined period (y seconds), the system assigns the ’Alarm Toggling Condition’ to this specific alarm in this specific MO. As long as the ’Alarm Toggling Condition’ is active, each single alarm notification and alarm clearance message is suppressed.

The following two scenarios lead to the cancellation of the ’Alarm Toggling Condition’: • Case 1: The alarm has not been present for a specified period (z seconds).

The ’Alarm Toggling Condition’ is cleared and the system sends an alarm clearance message, indicating the end of the ’Alarm Toggling Condition’.

28 DN70580522Issue 01A



Introduction

• Case 2: The previously toggling alarms becomes stable, i.e. non-toggling, for a specified period (z seconds).The ’Alarm Toggling Condition’ is cleared (see also Case 1) and the relevant alarm message of the specific alarm is sent to the management system.

Operators can enable or disable the suppression of toggling alarms in the Node B, via a CLI command by setting the togglingSuppressed parameter. This parameter specifies whether suppression of toggling alarms is active (TRUE) or not (FALSE).

Set to FALSE means that the suppression function is generally disabled for all external and internal alarms.

Operators can define or change toggling alarm conditions for NodeB2 to reduce the amount of alarms via a CLI command. Conditions for external toggling data and internal toggling data can be defined.

Example:Configure the toggling condition (TC: x=occurence, y=detection time, z=stable condition time) for following alarms: • External alarm (incoming port 0) and TC (x,y,z = 3, 300, 600) • External alarm (incoming port 3) and TC (x,y,z = 2, 100, 100) • Internal alarm with ID = 200908, which is mapped to the error string “RX alarm High”

and TC (x,y,z = 4, 300, 900)

In addition to the built-in default list, one modifiable list contains those alarms the operator wants to suppress in case of the toggling condition. This list also contains the related parameters, i.e. number of occurrences (x), period (y seconds), period of stable toggling (z seconds).

Detailed information about the actions mentioned above is available in “Node B Service Terminal Commands” reference manual.

1.1 TitleComposed of error-ID and error string

1.2 Failure Event ReportContains the following details: • Managed Object Class / Hardware Type • Event Type • Probable Cause • Severity

1.2.1 Managed Object Class / Hardware TypeThe managed object class / hardware type identifies the managed object class of the fault or error.

In the “Troubleshooting Node B” manual, an asterisk (’*’) symbol in the related field of the failure event report means that potentially any managed object class / hardware type can report this alarm.


29



1.2.2 Event TypeThe Event Type may have these possible values: • communicationsAlarm

An alarm of this type is principally associated with the procedures and/or processes required to convey information from one network node to another.

• environmentalAlarmAn alarm of this type is principally associated with a condition relating to an enclo-sure in which the equipment resides.

• equipmentAlarmAn alarm of this type is principally associated with an equipment fault.

• qualityOfServiceAlarmAn alarm of this type is principally associated with a degradation in the quality of a service and is issued as a result of performance measurements.QoS alarms help the operator to– Evaluate and gauge thresholds for performance management– Modify (add, remove, activate, deactivate) thresholds

• processingErrorAlarmAn alarm of this type is principally associated with a software or processing fault.

1.2.3 Probable CauseIdentifies the probable cause of the fault or error. The probable cause is taken out of a predefined set of values defined for each alarm type.

1.2.4 SeverityAccording to the CCITT Rec. X.733 all alarm notifications produced in switching systems have to be classified concerning the severity of their impact on the NE’s (Network Element) functionality.

The severity assigned to a specific alarm has one of the following values: • critical

The fault condition affects the ability to provide service. Immediate corrective action is required because (for example) a managed object has completely gone out of service.

• majorThe fault condition affects the ability to provide service. Urgent corrective action is required because (for example) a managed object has suffered from a severe deg-radation of its capabilities.

• minorThe fault condition does not affect the service as a whole. Corrective action is rec-ommended to prevent a more serious fault.

• warningA fault has been detected which potentially affects service. No significant effects have occurred. Action should be taken to further diagnose and (if necessary) correct the problem in order to prevent it from developing into a more serious service affect-ing fault.

30 DN70580522Issue 01A



Introduction

1.2.4.1 Fault Escalation StrategySome specific problems are handled according to the so-called “Fault Escalation Strat-egy”. This strategy consists of the following rules: • If the object raises the corresponding alarm for the first time, the alarm’s severity is

WARNING. • Upon each occurrence of this alarm, a dedicated escalation counter is incremented

and a corresponding dedicated escalation timer is (re-)started. • If the object operates normally for a specific period of time (the expiration period of

the escalation timer), i.e. if the object does not raise the same alarm again until the escalation timer expires, the escalation counter is reset.If the object raises the same alarm after expiry of the escalation timer, the alarm’s severity will be WARNING again.

• If the object raises the same alarm a predefined number of times without having operated normally for the escalation counter’s expiration period or longer, i.e. if the escalation counter crosses a predefined threshold, the severity will change from WARNING to a predefined final alarm severity.The alarm’s final severity is then set in the Failure Event Report. This manual describes the alarm’s final severity in the failure event report of the relevant alarm.

1.2.4.2 Configuration of Alarm SeveritiesThe operator can configure the severities of some alarms to either minor, major, or crit-ical, thus achieving a satisfying adaptation to actual needs. To adapt the alarm severity, the Node B’s database (DB) has to be changed. The FaultMng MOC in the Node B’s DB contains the severities parameter which is a list of all modified alarm severities. Several instances within this list can be created at the LMT. Each instance provides the following operator-configurable attributes: • Error ID of the alarm to be modified • ID of the MOC related to the alarm for which the severity is to be changed • Severity

Each instance within the severities parameter is evaluated by the Node B’s software (SW). Instances with MOC IDs or error IDs incompatible to the current Node B SW load are ignored.

To change the severity of an alarm, the following procedure has to be applied:1. Upload the DB to the LMT.

Use the TREE View window of the LMT or apply the uploadDataInitiate command to the relevant Osu managed object.

2. Modify the DB with the help of an XML editor or using scripts.Proceed according to the “Node B Database Editing Guide”.The following possibilities exist at the LMT:– Adding or removing an instance to or from, respectively, the severities list.– Modifying an existing instance within the list.

3. Download the modified DB.Use the TREE View window of the LMT or apply the downloadDataInitiate command to the relevant Osu managed object.

4. Activate the downloaded DB.Use the TREE View window or the Osu “activate”, nodeBDatabaseVersionType command.


31



For more information about DB parameters, refer to the “Node B Database Description”.

The severity assignment for a specific alarm is determined by the following sources, listed in descending priority:1. Severity setting for a particular managed object class (MOC), such as ExtEquipIn or

Scanner.2. Severity setting in the severities list of the Node B’s FaultMng MOI.3. Default built-in severity.

g NOTEThe severities attribute will be considered only for alarms that represent a con-dition for which a corresponding clearance event exists. In contrast, alarms that rep-resent only one single event, will always be sent with severity warning.

1.3 Error DescriptionDescribes the probable cause of the error concisely.

1.4 Troubleshooting (LMT)Describes the actions the operator must perform to attempt to solve the problem.

Collect Info for AssistanceIn some cases it is necessary to get support from customer services in order to isolate the fault. Prior to contacting the Technical Assistance Center (TAC) pay attention to the following questions and tasks: • Description of malfunction. • What is the suspected origin of the error? • What are the functional and hardware states of the affected system? • What are the issues of the affected boards? Check HW and FW states. • Observed system activities? • External influences (power supply, environment)? • What has been done (customer, local service staff)? • Exact time of error: synchronize the time stamp of all log files, if possible. • Save the database of the affected NE. • Save the IDF (Inventory Data File) of the affected NE. • Upload the log file of the affected NE.

The LMT provides a feature to upload diagnosis data from the Node B. The result of the diagnosis data upload is a zip file which should be attached to any fault report. The zip file contains information on the exact time of occurrence of the error, the database and the inventory data file (IDF) of the affected network element and the log file. For details about the diagnosis data upload, refer to the “Using Node B Service Terminal” guideline.

32 DN70580522Issue 01A


Id:0900d8058022b3a0Confidential

200506 - Node B system start-up malfunction due to software/hardware problem

2 200506 - Node B system start-up malfunction due to software/hardware problem

2.1 Failure Event Report

2.2 Error DescriptionThe Node B system start-up is maintained by a dedicated software subsystem (Mas-terServiceTask: MST). Any error encountered during initialization of this subsystem will generate this fault report. The affected Node B Core Controller is not available. Probable reasons for these conditions are problems related either to hardware (e.g.: memory problem, input/output malfunction) or operating system environment. This condition leads to a recovery reset of the whole Node B.

If the fault report relates to a HW problem, troubleshooting might require detailed knowl-edge of the Node B hardware structure (memory, boot system, ...). If the fault report relates to a SW problem, troubleshooting might require direct access to the Node B's operating system console.

2.3 Troubleshooting (LMT)Due to the imponderable system behavior in such cases there is no statement about further system operations. Contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

Managed Object Class / Hardware Type:

Osu

Event Type: processingErrorAlarm

Probable Cause: ApplicationSubsystemFailure

Severity: critical


33

Troubleshooting Node B 200507 - System halt due to software watchdog detect-ed problem


3 200507 - System halt due to software watchdog detected problem


3.2 Error DescriptionThis problem reports a situation, where the software health observation system has detected a missing health indication from any Node B software subsystem. The affected subsystem malfunction might (dependent of subsystem and error cause) be already noticeable by generated fault reports from it's own scope. This condition leads to a recovery reset of the whole Node B. The affected Node B Core Controller is temporary not available. This information has to be analyzed to find the malfunction originator. Due to the recovery reset, only the system log files could be used for 'post' analysis.

The probable reason for this alarm is a software problem.

3.3 Troubleshooting (LMT)Contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assis-tance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


Osu


Probable Cause: WatchDogTimerExpired

Severity: critical

34 DN70580522Issue 01A


Id:0900d8058022b3aeConfidential

200508 - System halt due to detected application pro-cess error

4 200508 - System halt due to detected applica-tion process error


4.2 Error DescriptionThis problem reports a situation, where the software health observation system has detected a 'dead' Node B software subsystem. The affected subsystem (generally) could not be indicated by generated fault reports from it's own scope, but this problem report contains information about the originator of the error. This condition leads to a recovery reset of the whole Node B. The affected Node B Core Controller is temporarily not available. Due to the recovery reset, only the system log files could be used for 'post' analysis.

The probable reason for this alarm is a software problem.



Osu


Probable Cause: SoftwareProgramAbnormallyTermi-nated

Severity: critical


35

Troubleshooting Node B 200509 - System halt due to detected hardware excep-tion

Id:0900d8058022b3b4Confidential

5 200509 - System halt due to detected hardware exception


5.2 Error DescriptionThis problem reports a situation, where the software health observation system has detected an 'unexpected' signal by the Node B hardware. This will be just logged by the observation system. This problem report contains information about the signal origina-tor. This condition leads to a recovery reset of the whole Node B. The affected Node B Core Controller is temporarily not available. Due to the recovery reset, only the system log files could be used for 'post' analysis.



Osu

Event Type: communicationsAlarm

Probable Cause: VendorSpecific

Severity: critical

36 DN70580522Issue 01A


Id:0900d8058022b3bcConfidential

200510 - System halt due to detected software loading malfunction

6 200510 - System halt due to detected software loading malfunction


6.2 Error DescriptionThis problem reports a situation, where the system loader detects a failure during software loading. This problem report contains information about the name of the failed software component. If the malfunction relates to a HW problem, it might be necessary to replace the addressed card. If the malfunction relates to a software problem, it might be solved by the recovery mechanisms of the software management subsystem (ISW). This condition leads to a recovery reset of the whole Node B. The affected Node B Core Controller is temporarily not available. Due to the recovery reset, only the system log files could be used for 'post' analysis.

6.3 Troubleshooting (LMT)1. Try to reset the addressed card.2. If there is a hardware failure, replace the addressed card.

Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.

3. It there is a software failure, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


Osu



Severity: critical


37

Troubleshooting Node B 200656 - Iub link broke down

Id:0900d8058022b3c4Confidential

7 200656 - Iub link broke down


7.2 Error DescriptionAn existing ATM connection between CRNC (controlling RNC) and Node B (Iub link) is broken because the CRNC is down, the cable has been plugged off or is broken. There-fore the Node B performs a reset.

The following subsequent alarms may also be initiated depending on the used interface type (E1/J1/T1, STM-1/OC-3):

• 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202058 - Loss Of Cell Delineation on Physical Link • 202059 - Alarm Indication Signal on Physical Link • 202060 - Remote Alarm Indication on Physical Link • 202061 - Loss of Multi Frame Alarm Indication on E1 Physical Link • 202062 - Line Alarm Indication Signal Indication on STM1 Physical Link • 202063 - Line Remote Defect Indication on STM1 Physical Link • 202064 - Path Loss of Pointer Indication on STM1 Physical Link • 202068 - Signal Label Mismatch Indication on STM1 Physical Link • 202070 - Signal Degrade Indication on STM1 Physical Link • 202071 - Excessive Bit Error Rate Indication on STM1 Physical Link • 202072 - Alarm Indication Signal on an ATM VC • 202073 - Remote Defect Indication on an ATM VC • 202074 - SSCOP Failure Indication on an ATM VC used by ALCAP or NBAP • 202075 - Alarm Indication Signal on an ATM VP • 202076 - Remote Defect Indication on an ATM VP • 202077 - ALCAP PVC Out Of Service Indication

The “Iub link broke down” alarm may be caused by:1. A failure in the RNC. In this case alarms from the RNC are additionally active.2. A failure of the link equipment or in the cable connection between Node B and link

equipment (LE).Usually the Node B is connected to the RNC or each other (Iub interface) via link equipment (LE) and in some rare cases by direct lines. If LE is involved the operation and maintenance system of this network has to be used for getting information about the state and status of the relevant network element (NE).Link equipment thus comprises network components such as SDH/PDH multiplex-ers, ATM switches, or repeaters.


Cc

Event Type: equipmentAlarm

Probable Cause: LinkFailure

Severity: critical

38 DN70580522Issue 01A



200656 - Iub link broke down

3. A failure within the OVPT or the IUBCON if an E1/J1/T1 interface is used.4. A failure in the CC (refer to 200994 - Hardware Failure). In this case, other CC initi-

ated alarms are additionally active.

The affected Node B is not working. All services will be interrupted. All cells will be lost.

7.3 Troubleshooting (LMT) • If RNC alarms for the Iub link to the affected Node B are reported to the RC concen-

trate the fault clearance actions on these alarms first. • Is the LE, which is connected to the relevant port, reporting an equipment alarm?

– If an equipment alarm at the LE is present try to fix this fault first which probably also eliminates the Iub link broke down alarm.

• Check the cable connections:

1. With regard to E1/J1/T1 lines check the OVPT or IUBCONElectrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (over-voltage protection and tracer module) equipped with surge arresters or an IUBCON (Iub connector). Both are available for coax and symmetrical cables.– Check surge arresters at OVPT and replace a defective one if necessary– Replace OVPT or IUBCON if no other reason was found

2. With regard to optical STM-1/OC-3 lines

Check for:– Proper connection at the LE (good contact, clean optical connector)– Proper connection at the Node B (good contact, clean optical connector)– Undamaged cable between Node B and LE respectively other Node B or RNC

• Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B present?Using the ALARM View window of the LMT:– Click on the “Alarm View” button or use the shortcut key Ctrl + A

– Use the filter and sort function to concentrate on CC alarmsIf an equipment alarm of the CC is present try to fix this fault first which probably also eliminates the Iub link broke down alarm.

!WARNING: Radiation from laser devices (EN 60825/IEC 60825).

Damage of health may occur.

To avoid damage to health, you must observe the regulations regarding protection against radiation from laser devices (EN 60825/IEC 60825). • You must always use dedicated laser-protective goggles. • Never look into open fiber-optic cable ends, as this may damage your eyes.


39

Troubleshooting Node B 200657 - SSCOP sent overrun

Id:0900d8058022b3caConfidential

8 200657 - SSCOP sent overrun


8.2 Error DescriptionNode B’s SSCOP is not able to transmit the messages to the CRNC (controlling RNC) since the configured bandwidth on this link is too low. Therefore, the Node B performs an automatic reset.



Cc



Severity: critical

40 DN70580522Issue 01A


Id:0900d8058022b3d0Confidential

200658 - Transmit bandwidth limit for NBAP reached

9 200658 - Transmit bandwidth limit for NBAP reached


9.2 Error DescriptionUnder conditions with high traffic, the NBAP bandwidth set at the reporting Node B’s Iub interface may not be sufficient. If the high-traffic condition persists, the Node B will start dropping messages.

This alarm therefore indicates a general lack of bandwidth to send messages at the Node B’s Iub interface. In other words, the Node B’s transmit bandwidth for NBAP con-nections toward the RNC has reached its limit and the message buffers are exhausted.

The Node B then started overload defence actions. This may affect service quality because dedicated measurement reports will be dropped and RL setup or reconfigura-tion attempts will be rejected.

The reporting Node B continues operation. Service quality, however, is decreased. The increased traffic thus requires appropriate settings for the transmit bandwidth at the Node B’s Iub interface. In other words, the Node B’s database (DB) settings have to be revised and the transmit bandwith at the Iub interface has to be increased.

9.3 Troubleshooting (LMT) Take the following measures to clear this alarm and to prevent this overload condition in the future:1. Revise the reporting Node B’s DB settings in such a way that the NBAP transmit

bandwidth is increased.Increase both the ingress and the egress peak cell rate to an identical value, using the following commands:– TrafficDescriptor “Set peakCellRateIngress”– TrafficDescriptor “Set peakCellRateEgress”

2. If the first action did not clear the cause for this alarm, contact the technical assis-tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


NodeBFddE

Event Type: qualityOfServiceAlarm

Probable Cause: SystemResourcesOverload

Severity: minor


41

Troubleshooting Node B 200659 - Core Controller overload protection activated


10 200659 - Core Controller overload protection activated


10.2 Error DescriptionA situation with peak load has occurred in the reporting Node B. Due to this situation, the Node B may activate an overload protection. Overload protection is a defence action of the Node B to maintain stable operation.

In fact, the reporting Node B’s core controller (CC) CPU capacity has reached its limit. As a consequence, RL setup or reconfiguration attempts will be rejected. Service quality is decreased.

The causes for the Node B’s high CPU load needs to be investigated.

10.3 Troubleshooting (LMT) Take the following measures to clear the alarm cause:1. First, investigate the causes for the high CC load.2. Contact the technical assistance center (TAC) to get support in isolating the fault.

For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


NodeBFddE


Probable Cause: SystemResourcesOverload

Severity: minor

42 DN70580522Issue 01A


Id:0900d8058022b3deConfidential

200660 - SSCOP Dedicated Link send overrun

11 200660 - SSCOP Dedicated Link send overrun


11.2 Error DescriptionThe bandwidth configured on the suspected link is too low. The Node B’s SSCOP is therefore not able to transmit messages over the NBAPDedicated link (“Communication Context Control” port, see usedByAttribute parameter) to the controlling RNC (CRNC).

As a consequence, the Node B performs an automatic reset.

11.3 Troubleshooting (LMT)Take the following measures to solve the reported problem:1. Make sure to adapt the link capacity to the expected traffic at this particular Node B.

The referenced VcCTP which supports the suspected link (VcTTP, see connectivity-Pointer parameter) points to a TrafficDescriptor object via the trafficDescriptor-Pointer parameter. This TrafficDescriptor object has to be configured as follows:– serviceCategory=“CBR”– peakCellRateIngress and peakCellRateEgress must have identical values☞ Also check whether the link capacity problem can be verified, using appropriate

performance measurements (PMs).2. If the problem persists after adapting the link capacity, contact the technical assis-

tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator's scope.


Cc



Severity: critical


43

Troubleshooting Node B 200661 - SSCOP Common Link send overrun

Id:0900d8058022b3e4Confidential

12 200661 - SSCOP Common Link send overrun


12.2 Error DescriptionThe bandwidth configured on the suspected link is too low. The Node B’s SSCOP is therefore not able to transmit messages over the NBAPCommon link (“Node B Control” port, see usedByAttribute parameter) to the controlling RNC (CRNC).

As a consequence, the Node B performs an automatic reset.

12.3 Troubleshooting (LMT)Take the following measures to solve the reported problem:1. Make sure to adapt the link capacity to the expected traffic at this particular Node B.

The referenced VcCTP which supports the suspected link (VcTTP, see connectivity-Pointer parameter) points to a TrafficDescriptor object via the trafficDescriptor-Pointer parameter. This TrafficDescriptor object has to be configured as follows:– serviceCategory=“CBR”– peakCellRateIngress and peakCellRateEgress must have identical values☞ Also check whether the link capacity problem can be verified, using appropriate

performance measurements (PMs).2. If the problem persists after adapting the link capacity, contact the technical assis-

tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator's scope.


Cc



Severity: critical

44 DN70580522Issue 01A


Id:0900d8058022b3ecConfidential

200706 - An error occurred in the nbDatabase

13 200706 - An error occurred in the nbDatabase


13.2 Error DescriptionNode B startup failed because of an error in the nbDatabase.

This may be caused by the following:

• A new database was installed but does not match release and version of the software load.

• A new database was installed but does not match the hardware configuration. • A new hardware equipment was installed but was not configured in the database. • A software error has occurred.

13.3 Troubleshooting (LMT)Depending on the cause due to which the Node B startup failed, perform one of the fol-lowing tasks: • If the new database does not match release and version of the software load:

– Check the Node B database with the mibCheck tool delivered with Node B soft-ware. Proceed according to the “Node B Database Editing Guide”.

– Adapt the database according to the results of this check. Proceed according to the “Node B Database Editing Guide”.

• If the new database does not match the hardware configuration:– Check that the current database version is used (from the RC or on site).

Proceed according to the “Node B Database Editing Guide”.– Upgrade the database if necessary. Use the mibUpgrader tool. Proceed accord-

ing to the “Node B Database Editing Guide”.– Check the Node B database to generate a new database that matches the

hardware configuration. Use the mibCheck or mibCheckWin tool. Proceed according to the “Node B Database Editing Guide”.

– If only little changes are necessary, enter new hardware equipment in database. To edit the Node B’s database, proceed according to the “Node B Database Editing Guide”.

• If new hardware equipment is not configured in the database:– Check the hardware configuration (on site). Use the mibCheck or mibCheckWin

tool. Proceed according to the “Node B Database Editing Guide”.– Enter new hardware equipment in database. To edit the Node B’s database,

proceed according to the “Node B Database Editing Guide”.


Osu


Probable Cause: SoftwareError

Severity: critical


45

Troubleshooting Node B 200706 - An error occurred in the nbDatabase


• If the error is not caused by an invalid DB or an unsuitable hardware configuration:Contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in ’Collect Info for Assistance’. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

46 DN70580522Issue 01A


Id:0900d8058022b3f4Confidential

200707 - A warning occurred in the nbDatabase

14 200707 - A warning occurred in the nbData-base


14.2 Error DescriptionThere may be an error in the nbDatabase. This warning only occurs during a version upgrade of the database.

There may be the following causes:

1. During version upgrade: There are missing attributes because of using a database from an older version.

2. No version upgrade: The database is defective or a new database was installed but does not match the software version.

14.3 Troubleshooting (LMT)1. There is no action necessary because default values will be used.2. If the new database does not match the software load:

– Check the Node B database with the mibCheck tool delivered with Node B soft-ware. Proceed according to the “Node B Database Editing Guide”.

– Adapt the database according to the results of this check. Proceed according to the “Node B Database Editing Guide”.

g NOTESoftware load and database must base on the same InfoModel which is also the basis for the “Node B Service Terminal Commands” reference manual.


Osu



Severity: warning


47

Troubleshooting Node B 200905 - VSWR alarm Low

Id:0900d805806e6cd1Confidential

15 200905 - VSWR alarm Low


15.2 Error DescriptionEach antenna port of the DUAMCO/RRH is monitored for the Voltage Standing Wave Ratio (VSWR) of the connected antenna system. Two levels for the antenna return loss can be defined for which an alarm of the appropriate severity will be generated as soon as the relevant threshold (vswrThreshold parameter) is exceeded. The “VSWR alarm Low” is the minor one - which is under consideration here - related with the lower thresh-old and may be received before alarm 200906 - VSWR alarm High. The most likely reason for the VSWR alarms is a defective antenna feeder cable or a damaged antenna.

g NOTEThis alarm does not occur when the TX power falls below the lower power level con-figured for VSWR monitoring.

15.3 Troubleshooting (LMT)To isolate the origin of the high return loss it is necessary to know whether the antenna system is equipped with a TMA/DTMA or not. This is known from the site specific doc-umentation or can be verified by checking the availability via LMT.

Probable causes: • A destroyed antenna due to a stroke of lightning or thunderstorms can trigger this

alarm • Water inleakage or an otherwise damaged feeder cable is the most likely reason • Other alarms related with the TMA, such as “200910 – TMA feeder alarm” or

“200911 – TMA DC alarm” may also be received previously indicating a bro-ken/short-circuit feeder cable or a faulty TMA itself


Duamco, Rrh


Probable Cause: TransmitterAntennaNotAdjusted

Severity: minor

!WARNING – Uncontrolled emission of microwave radiation

Microwave radiation may be emitted uncontrolled during the replacement of antenna cables, antennas, TMAs, DUAMCOs, or RRHs.

To avoid uncontrolled emission of microwave radiation during one of these replacement procedures, apply the following respective task: • When replacing antenna cables, antennas, TMAs, or DUAMCOs, switch off the

relevant breakers which supply the LPAs/CATs involved in the affected antenna branch in order to prevent an uncontrolled emission of microwave radiation.

• For RRHs, switch off the power supply to prevent uncontrolled emission of micro-wave radiation.

48 DN70580522Issue 01A


Id:0900d805806e6cd1Confidential

200905 - VSWR alarm Low

For an effective troubleshooting, the actions in the following order should be performed with reference to the relevant manuals:1. Inspect the antenna, the feeder cable and the TMA - if mounted - visually for any

damage caused by lightnings, thunderstorms or other impacts (e.g. bullets).– Replace the defective cable or antenna according to the OEM manual– Replace the defective TMA. Replacement must be done according to the

“Replacing Node B Units” manual, “Tasklist”.2. Check all connectors of the antenna system for correct and tight fit and if loose for

not being corroded.– Tighten loose connectors after removing corrosion or replacing destroyed ones.

3. Measure the antenna feeder cable parameters according to the OEM specification.– Replace the defective cable if minimum requirements are not met according to

the OEM manual.4. If none of the causes above can be identified for the alarm the DUAMCO or RRH is

assumed to be defective.– Replace the DUAMCO or RRH. Replacement must be done according to the

“Replacing Node B Units” manual, “Tasklist”.


49

Troubleshooting Node B 200906 - VSWR alarm High

Id:0900d805806e5198Confidential

16 200906 - VSWR alarm High


16.2 Error DescriptionEach antenna port of the DUAMCO/RRH is monitored for the Voltage Standing Wave Ratio (VSWR) of the connected antenna system. Two levels for the antenna return loss can be defined for which an alarm of the appropriate severity will be generated as soon as the relevant threshold (vswrThreshold parameter) is exceeded. The 200905 - VSWR alarm Low is the minor one related with the lower threshold and may be received before the “VSWR alarm High” which is under consideration here. The most likely reason for the VSWR alarms is a defective antenna feeder cable or a damaged antenna.

As a consequence, cells or calls could potenitally be lost. Furthermore, the states of all affected managed objects is changed accordingly.

g NOTEThis alarm does not occur when the TX power falls below the lower power level con-figured for VSWR monitoring.

16.3 Troubleshooting (LMT)To isolate the origin of the high return loss it is necessary to know whether the antenna system is equipped with a TMA / DTMA or not. This is known from the site specific doc-umentation or can be verified by checking the availability via LMT.

Probable causes: • A destroyed antenna due to a stroke of lightning or thunderstorms can trigger this

alarm • Water inleakage or an otherwise damaged feeder cable is the most likely reason


Duamco, Rrh


Probable Cause: TransmissionAntennaFailure

Severity: major

50 DN70580522Issue 01A



200906 - VSWR alarm High

• Other alarms related with the TMA, such as “200910 – TMA feeder alarm” or “200911 – TMA DC alarm” may also be received previously indicating a bro-ken/short-circuit feeder cable or a faulty TMA itself

For an effective trouble-shooting the actions in the following order should be performed with reference to the relevant manuals:1. Inspect the antenna, the feeder cable and the TMA - if mounted - visually for any

damage caused by lightnings, thunderstorms or other impacts (e.g. bullets).– Replace the defective cable or antenna according to the OEM manual– Replace the defective TMA. Replacement must be done according to the

“Replacing Node B Units” manual, “Tasklist”.2. Check all connectors of the antenna system for correct and tight fit and if loose for

not being corroded.– Tighten loose connectors after removing corrosion or replacing destroyed ones.

3. Measure the antenna feeder cable parameters according to the OEM specification.– Replace the defective cable if minimum requirements are not met according to

the OEM manual.4. If none of the causes above can be identified for the alarm the DUAMCO or RRH is

assumed to be defective.– Replace the DUAMCO or RRH. Replacement must be done according to the

“Replacing Node B Units” manual, “Tasklist”.

!WARNING – Uncontrolled emission of microwave radiation

Microwave radiation may be emitted uncontrolled during the replacement of antenna cables, antennas, TMAs, DUAMCOs, or RRHs.

To avoid uncontrolled emission of microwave radiation during one of these replacement procedures, apply the following respective task: • When replacing antenna cables, antennas, TMAs, or DUAMCOs, switch off the

relevant breakers which supply the LPAs/CATs involved in the affected antenna branch in order to prevent an uncontrolled emission of microwave radiation.

• For RRHs, switch off the power supply to prevent uncontrolled emission of micro-wave radiation.


51

Troubleshooting Node B 200907 - RX alarm Low

Id:0900d8058022b40aConfidential

17 200907 - RX alarm Low


17.2 Error DescriptionThis alarm occurred because one branch of an RX amplifier of the reporting LRU has failed. The RX amplifier is still working but degraded in its performance.

Among other scenarios, output of the alarm results from simultaneous occurrence of the following two events: • Misconfiguration (wrong installation) of the Node B

A DTMA for RF = 2100 MHz is installed in a Node B dedicated for use in the 1900 MHz RF band, or vice versa. As a consequence of this misconfiguration, the DTMA breaks.

• Operational state (OST) of the related cell is disabledIf both branches become out of order, the 200908 - RX alarm High will be sent.

17.3 Troubleshooting (LMT)An immediate action is not necessary, but it is recommended to replace the reporting DUAMCO, RRH, DRX, or TMA as soon as possible. Perform the following tasks in the order described:1. First, before replacing the equipment, try to reset the reporting managed object.

Use the TREE View window of the LMT and apply the respective command, depending on the reporting MO:DRX Drx “reset”DUAMCO Duamco “reset”RRH Rrh “reset”TMA Tma “reset”g NOTE

During the reset and the repair action the cell is not available.2. If the alarm persists after the reset, replace the reporting DUAMCO, RRH, DRX, or

TMA. Replacement must be done according to the “Replacing Node B Units” instructions.


Duamco, Tma, Rrh, Drx


Probable Cause: ReceiverFailure

Severity: minor

!DANGER: Uncontrolled emission of microwave radiation.


To avoid the danger of an uncontrolled emission of microwave radiation, switch off the breakers for the related LPAs/CATs before replacing antenna cables, antennas, RET, or DUAMCO.

52 DN70580522Issue 01A



200907 - RX alarm Low

g NOTEBefore replacing the DUAMCO, set the DIP-switches on the front side of the DUAMCO in the same configuration as it was on the replaced DUAMCO.

g NOTEAfter replacing the TMA, reset the DUAMCO via LMT or reset button. When resetting the DUAMCO via reset button. press the button for at least eight seconds. Otherwise, the reset will not become effective.Then reset the TMA (via LMT). Use the TREE View window or the Tma “reset” command.


53

Troubleshooting Node B 200908 - RX alarm High


18 200908 - RX alarm High


18.2 Error DescriptionThis alarm is output in consequence of various scenarious, depending on the reporting hardware. If this alarm message is sent by the • DUAMCO or direct receiver (DRX) module, both branches of an RX amplifier of the

reporting LRU have failed. • TMA, both branches of an RX amplifier of the reporting LRU have failed.

Furthermore, the MUCO mode in the DUAMCO will switch back to AMCO mode.After the reset, the DUAMCO will be in its original mode according to the DIP-switches on the front.

• RRH, the alarm is output in consequence of one of the following two events– Both branches of the RX-balanced LNA input stage fail.

g This failure cause is applicable for all RRH types.– The root mean square (RMS) of the digital signal has fallen below a specific

threshold for more than 60 seconds [s].Beside an LRU failure, this can also be caused by a general problem on one RX path, such as a cabling problem (DUAMCO – CAT or antenna cabling).g This failure cause is applicable for some RRH types only.

• CAT, the root mean square (RMS) of the digital signal has fallen below a specific threshold for more than 60 seconds [s].The alarm is raised only when some circuit within the RX chain has a malfunction.

Among other scenarios, output of the alarm results from simultaneous occurrence of the following two events: • Misconfiguration (wrong installation) of the Node B

A DTMA for RF = 2100 MHz is installed in a Node B dedicated for use in the 1900 MHz RF band, or vice versa. As a consequence of this misconfiguration, the DTMA breaks.

• Operational state (OST) of the related cell is enabledThere might have been an alarm 200907 - RX alarm Low before.

As a consequence, cells or calls could potentially be lost. Furthermore, the states of all affected managed objects change accordingly.

18.3 Troubleshooting (LMT)g NOTE


Duamco, Tma, Rrh, Drx, Cat



Severity: major

54 DN70580522Issue 01A



200908 - RX alarm High

During the reset and the repair action the cell is not available.

Take the following measures to clear the fault which led to this alarm:1. If this alarm is reported by a CAT or RRH, check the DUAMCO – CAT or antenna

cabling to rule out any cabling problem.

2. Reset the reporting managed object.Use the TREE View window of the LMT and apply the following action command, depending on the reporting MO:DUAMCO Duamco “Reset”TMA Tma “Reset”RRH Rrh “Reset”DRX Drx “Reset”CAT Cat “Reset”

3. If the alarm persists after the reset, replace the module which corresponds to the reporting managed object.Replacement must be done according to the “Replacing Node B Units” instructions.


4. After having replaced a defective TMA, take the following measures:4.1 Reset the DUAMCO via LMT or reset button.

When resetting the DUAMCO via LMT, use the TREE View window of the LMT and apply the Duamco “Reset” action command.When resetting the DUAMCO via reset button, press the button for at least eight seconds. Otherwise, the reset will not become effective.

4.2 Then reset the TMA (via LMT).Use the TREE View window of the LMT and apply the Tma “Reset” action command.



To avoid the danger of an uncontrolled emission of microwave radiation, switch off the breakers for the related LPAs/CATs before checking antenna cables, antennas, RET, or DUAMCO.





55

Troubleshooting Node B 200909 - TMA switched off, but not defective


19 200909 - TMA switched off, but not defective


19.2 Error Description The TMA is switched off, but not defective and the DUAMCO works in AMCO mode. This mode is indicated by the TMA LED which is off. The receiver is degraded in its per-formance. The failure occurs in one of the following situations:

• Most likely this alarm is raised during normal Node B operation if the DIP switch 1 of the corresponding DIP switch group of the DUAMCO is set to OFF position (AMCO mode/TMA off) by accident. The TMA is switched off, but not defective.

• In rare cases, the alarm can also be raised together with another more critical alarm such as 200908 - RX alarm High.

19.3 Troubleshooting (LMT)Check the power supply for the TMA at the associated DUAMCO. Furthermore, verify that the TMA is connected to the DUAMCO and check if the DIP switch 1 of the DUAMCO (TMA ON/OFF) is switched ON.

If the DIP switch 1 was set to the OFF position by accident do the following:

1. Switch the DUAMCO DIP switch 1 to the ON position. The TMA LED should now be on (green), but the alarm still exists at the LMT/RC.

2. Reset the TMA managed object in the TREE View window of the LMT. Apply the Tma “reset” action command to the reporting managed object.

If other critical alarms such as 200908 - RX alarm High are also raised, please refer to the corresponding alarm description. Please note that the DIP switch 1 may be in the ON position in this case.


Tma


Probable Cause: PowerSupplyFailure

Severity: minor

56 DN70580522Issue 01A


Id:0900d8058022b41cConfidential

200910 - TMA feeder alarm

20 200910 - TMA feeder alarm


20.2 Error DescriptionThe DUAMCO monitors the 2.176 MHz signaling carrier coming from the TMA. A break-down of this carrier initiates the TMA Feeder Alarm. The amplifier is degraded in its per-formance. The combination of OST/AVS for the addressed TMA and the related localCellE managed object instance changes to disabled/failed and enabled/degraded, respectively.

The “TMA feeder alarm” may be caused by: • A failure in the antenna feeder cable. In this case, the 200905 - VSWR alarm Low /

200906 - VSWR alarm High and uplink/downlink alarms may be additionally active. • A failure in the TMA. • A failure in the power supply, indicated by the 200911 - TMA DC alarm.

If a RET module is installed in the current configuration, the alarm 201004 – RET com-munication error will be output as a consequence of this alarm.

In addition to the above alarm causes, a wrong installation of the Node B may also lead to the “TMA feeder alarm”: whenever a DTMARET (supporting RET) and a DUAMCORT (without RET support) are installed in the same Node B, this alarm is output. As a con-sequence of the wrong configuration, the 201002 – RET feeder alarm may also be output.

For TMA recovery, a reset of the related DUAMCO is required in order to re-establish the communication between the DUAMCO and the TMA. A reset of the TMA managed object is not possible while this failure persists.

20.3 Troubleshooting (LMT)

1. First, reset the related DUAMCO to re-establish the communication between the DUAMCO and the TMA.Use the TREE View window and apply the Duamco “reset” command.


Tma



Severity: minor





57

Troubleshooting Node B 200910 - TMA feeder alarm


2. The further procedure depends on the actual problem. Refer to the following list:– If only the “TMA feeder alarm” exists, replace the TMA.

Replacement must be done according to the “Replacing Node B Units” instruc-tions.

– If an additional DC alarm (200911 - TMA DC alarm) is active in the ALARM View window, check the DC/DC converter of the DUAMCO: Unplug the antenna feeder cable and measure the voltage at the antenna port of the DUAMCO. If the voltage is below the defined threshold, the DC/DC converter of the DUAMCO is defective.Replace the DUAMCO. Replacement must be done according to the “Replacing Node B Units” instructions.

– If an additional VSWR alarm (200905 - VSWR alarm Low or 200906 - VSWR alarm High) is active in the ALARM View window, check the antenna feeder cable: If the alarm message is canceled after unplugging the antenna feeder cable, the fault is caused by a short circuit in the antenna feeder cable or an overcharged TMA.Check the antenna feeder cable.

– An additional RET feeder alarm (201002 – RET feeder alarm) normally is a strong indicator for a wrong configuration of the Node B, i.e. installation of a DTMARET (supporting RET) and a DUAMCORT (without RET support).To solve this error, replace the DUAMCORT with a DUAMCORET (supporting RET). Replacement must be done according to the “Replacing Node B Units” instructions.

3. If none of the above reasons could be verified, replace the TMA.Replacement must be done according to the “Replacing Node B Units” instructions.


g NOTEAfter replacing the TMA, reset the DUAMCO via LMT or reset button. When reset-ting the DUAMCO via reset button, press the button for at least eight (8) seconds. Otherwise the reset will not become effective. Then reset the TMA (via LMT). Use the TREE View window and apply the Tma “reset” command.

58 DN70580522Issue 01A



200911 - TMA DC alarm

21 200911 - TMA DC alarm


21.2 Error DescriptionThe power supply for the TMA is fed via the antenna feeder cable from the DUAMCO/DRX to the TMA. If the supply voltage for the TMA at the antenna port of the DUAMCO/DRX is below the defined threshold (11,3 V), the TMA DC Alarm is initiated.

The TMA DC Alarm may be caused by:

• A failure in the DC/DC converter of the DUAMCO/DRX. • A short circuit in the antenna feeder cable. In this case the alarms 200905 - VSWR

alarm Low or 200906 - VSWR alarm High and uplink/ downlink alarms are addition-ally active.

• The TMA is overcharged. The current consumption of the TMA is too high.

The amplifier is degraded in its performance.


1. Unplug the antenna feeder cable and measure the voltage at the antenna port of the DUAMCO/DRX. If the voltage is below the defined threshold, the DC/DC converter of the DUAMCO/DRX is defective. Replace the DUAMCO/DRX. Replacement must be done according to the “Replacing Node B Units” instructions.

2. If the alarm message is cleared after unplugging the antenna feeder cable, the fault is caused by a short circuit in the antenna feeder cable or an overcharged TMA. Check the antenna feeder cable.

3. If none of the above reasons could be verified, replace the TMA. Replacement must be done according to the “Replacing Node B Units” instructions.

g NOTEBefore replacing the DUAMCO/DRX, set the DIP-switches on the front side of the DUAMCO/DRX in the same configuration as it was on the replaced DUAMCO/DRX.


Duamco, Drx


Probable Cause: EquipmentFailure

Severity: minor





59

Troubleshooting Node B 200911 - TMA DC alarm


g NOTEAfter replacing the TMA, reset the DUAMCO/DRX via LMT or reset button. When resetting the DUAMCO/DRX via reset button, press the button for at least eight seconds. Otherwise, the reset will not become effective. Then reset the TMA (via LMT). Use the TREE View window and apply the Tma “reset” command.

60 DN70580522Issue 01A



200914 - Fan unit failed

22 200914 - Fan unit failed


22.2 Error DescriptionOne of the fan units in the Node B is defective. There might be a failure of components sensitive to heat. Caused by the lack of air circulation, there might occur temperature alarms, reported by the rack/ shelter or the cards.

This alarm message may occur in conjunction with temperature alarms: • 200920 - High temperature of PA • 200921 - Over temperature of PA • 200995 - High Temperature Limit (Ht3) reached • 200996 - Critical Temperature Limit (Ht4) reached

g NOTEIf the reporting Node B is of type NB-441/NB-881/NB-861, the lack of air circulation may be caused by a polluted membrane filter (MEF). Therefore, if the Node B site is located in heavily air-polluted environments combined with special temperature con-ditions, a maintenance of the MEF filters in the outdoor NB-441/NB-881/NB-861 might be necessary.

If the MEFs are polluted, the 201029 - MEF blocked or 201035 - MEF completely blocked alarm is output. Refer to the relevant alarm’s error description and follow the troubleshooting.

g NOTETo avoid toggling of this alarm from the same managed object, i.e. the alarm is raised and ceased alternately, the alarm will only be ceased if the following applies:

After having cleared the cause of this fault, the addressed LRU has not reported the same alarm again for at least 100 seconds.

Otherwise, this alarm will not be ceased but remains active. Troubleshooting tasks for this alarm must be taken.


Fan

Event Type: environmentalAlarm

Probable Cause: FanFailure

Severity: major


61

Troubleshooting Node B 200914 - Fan unit failed



If all fan units of the B-shelf are defective, self-disabling of B-shelf cards can occur as a consequence. The Node B handles self-disabled cards as if a fatal board failure, such as an on-board power supply failure, has occurred. In other words, the combination of OST/AVS changes to disabled/not installed and the LED of the self-disabled card is off.

g NOTEThe defective fan unit(s) are recommended to be exchanged within the next 24 hours!

Take the following measures to clear the alarm cause:1. Identify the defective fan unit.

Use either the TREE View window or the ALARM View window of the LMT.2. Replace the fan unit.


!CAUTION: Gyrating rotor!

Damage to health may occur.

When pulling out the fan module, the rotor may still rotate for a few seconds. Wait until the rotor stands still and watch your fingers!

62 DN70580522Issue 01A



200915 - Site input alarm detected

23 200915 - Site input alarm detected


23.2 Error Descriptiong NOTE

Changing the ExtEquipIn managed object’s alarm severity, alarm value, associ-ated string, and probable cause attributes does not affect an existing “200915 - Site input alarm detected” alarm. The modified attributes will take effect for the next occurrence of this alarm.

When modifying the attributes mentioned above, however, only one attribute can be changed simultaneously. In other words, when using the relevant command for setting these attributes, only one single attribute of one single managed object can be set.

A site input alarm was detected.

This alarm is raised if one of the connected site input sensors is active, e.g. water detec-tor, site door open switch, window broken, air condition system defect, etc.

The reported “Probable Cause” and “Severity” in the Failure Event Report depend on the configuration of the related ExtEquipIn managed object in the nbDatabase. • For the severity the value of the attribute label “alarmSeverity” of each object class

ExtEquipIn can be set to minor, major, or critical in the nbDatabase by an equiv-alent string.

• The ExtEquipIn instances ExtEquipIn.4 to ExtEquipIn.12 at the RRH are reserved for reporting alarms related to the power supply units for RRHs (PSRs). These ExtEquipIn instances have to exist in the database in configurations with RRHs.

• Whereas the value of the “probableCause” attribute label is represented by a number which is related to a string defined in the Infomodel, e. g.:4 Battery Breakdown22 Power Supply Failure147 Smoke Detected149 Fuse Failure

• With the AD panel HW, the alarm properties (Probable Cause: PowerSupplyFailure) listed below may be displayed.Source Additional TextExtEquipIn.7 AC/DC Converter - Mains Break Down AlarmExtEquipIn.8 AC/DC Converter - Battery Breakdown AlarmExtEquipIn.9 AC/DC Converter - Battery Charger FaultExtEquipIn.10 AC/DC Converter - DC Output Voltage out of Tolerance


ExtEquipIn


Probable Cause: ExternalEquipmentFailure

Severity: minor, major, critical


63

Troubleshooting Node B 200915 - Site input alarm detected


• A broken/defective DCBCTRL may be the cause of this alarm whenever the “200915 - Site input alarm detected” alarm is output four times, showing each of the alarm properties (Probable Cause: PowerSupplyFailure) mentioned below:Source Additional TextExtEquipIn.7 AC/DC Converter - Mains Break Down AlarmExtEquipIn.8 AC/DC Converter - Battery Breakdown AlarmExtEquipIn.9 AC/DC Converter - Battery Charger FaultExtEquipIn.10 AC/DC Converter - DC Output Voltage out of ToleranceDefective DCBCTRL modules have to be replaced.

• If the reporting Node B is of type NB-441 or NB-881, the alarm may also originate from a defect in the over voltage protection of the (optional) OVP box between the Node B and external equipment, such as RRHs.

For explanations of customizing a nbDatabase please refer to the relevant chapter of the “Node B Database Description”.

External equipment input identifier (extEquipInId) and pinning relations to the ACTM (Alarm Collection Terminal Master) can be found in the “Node B Cards/Modules Hardware Description”.

23.3 Troubleshooting (LMT)g If the following alarm properties are displayed after the system was in battery

backup operation, there is no need for further actions:

Source: ExtEquipIn.10 (of ServiceRack.0)


Additional Text: AC/DC Converter – DC Output Voltage out of Tolerance

Before re-charging is finished and battery is full again, it may happen that the alarm oszillates sometimes. When battery is fully charged the alarm is ceased durable.

If this alarm is caused by a defective DCBCTRL module, replace the DCBCTRL. Replacement must be done according to the “Replacing Node B Units” manual.

ChecksOtherwise, confirm whether the indicated root cause for this alarm is plausible: • Is this alarm at the reported ExtEquipIn port probable? Possible alarm causes may

be a broken window, defective air condition system, ingress of moisture, open site door, etc.Inspect the Node B visually. Depending on the result, continue with one of the fol-lowing tasks:– Reset Node B Hardware– On-Site Troubleshooting

• Is this alarm at the reported ExtEquipIn port not probable?Continue with the “Troubleshooting for Improbable Alarm Causes” task.

Troubleshooting for Improbable Alarm CausesA wrong configuration of the database could be the reason for such an alarm. If necces-sary correct the database as follows:1. Upload the database via LMT.

Apply the Osu “uploadDataInitiate”, fileType=database command.2. Find the alarmValue attribute of the extEquipInId of the alarm in question and verify

the setting:

64 DN70580522Issue 01A



200915 - Site input alarm detected

0 low active = closed contact1 high active = open contact

3. Correct the setting if necessary and download the database.Proceed according to the “Node B Database Editing Guide”.

4. Download the corrected database.Apply the Osu “downloadDataInitiate”, fileType=database command.

5. Activate the downloaded database.Apply the Osu “activate” command.

6. If the alarm is still active, continue with the “Reset Node B Hardware” task.

Reset Node B HardwareReset the following hardware of the Node B in the order provided:1. Reset the ACT.

Apply the Act “reset” command.2. Reset the core controller (CC).

Apply the Cc “reset” command.3. If the alarm is still active, continue with the “On-Site Troubleshooting” task.

On-Site Troubleshooting1. Inspect the supervised object for being in false condition and get rid of the conditions

which have caused the alarm. Examples are:– Supervision contacts (for doors, etc.)– Cabling– DIP switch settings– Air condition system

2. Replace suspicious Node B hardware in the following order:2.1 Replace the ACT module. Replacement must be done according to “Replacing

Node B Units”, “Tasklist”.☞ For information about the different ACT types, their locations, functions, and

interfaces, consult the “Node B Cards/Modules Hardware Description”, “ACT”.

2.2 Replace the CC card. Replacement must be done according to “Replacing Node B Units”, “Tasklist”.☞ For information about the different CC types and interfaces, consult the

“Node B Cards/Modules Hardware Description”, “CC”.3. Check and, if neccessary, fix the CAN bus cabling.4. Fix the backplane cabling and the respective terminators.

If the above measures did not help to cease this alarm, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


65

Troubleshooting Node B 200916 - Rack Door open


24 200916 - Rack Door open


24.2 Error DescriptionThe door condition is controlled by a reed switch together with a permanent magnet. This alarm occurs if one of the following doors is open:

• The door of a rack • The door of a single shelter • One or both doors of a double shelter

A damaged or misaligned supervision contact (reed switch - magnet) or a door that is not firmly closed (gap more than 10mm) should also be taken into consideration.

For outdoor shelters it has to be noted that the filter system (MEF = membrane filter) may be by-passed allowing dust to contaminate the equipment in the shelter, resulting in the malfunction.

24.3 Troubleshooting (LMT)Take the following measures to clear the alarm cause:1. Inspect the doors for perfect closing and locking.2. Damaged doors (vandalism) have to be replaced. Shelters must be air tight to

ensure effective air filtering and circulation as well as electromagnetic shielding requirements conformance.

3. If the alarm is active even though all doors are perfectly closed, the supervision contacts (reed switch - magnet) and the cabling should be checked:– Is the door supervision contact connected to the ACT board? For double

shelters the left door contact is connected to the ACTCM at the EMI-Panel, the right door contact is connected to the ACTCB at the DC-Panel. The door contact of single shelters is connected to the ACTCS at the EMI-Panel whereas the door contact of a rack to the ACTCB at the DC-Panel connected is.

– Is the permanent magnet at the top edge of the doors in place? If not, adjust the magnet or fit a new one.

– With the door open place a permanent magnet close to the reed switch at the top edge of the rack/shelter’s opening. Drawing the magnet far and near should activate/deactivate the alarm. If not, the reed switch has to be replaced.


BaseRack, ServiceRack, Booster


Probable Cause: EnclosureDoorOpen

Severity: minor

66 DN70580522Issue 01A



200918 - PA combiner interface fault

25 200918 - PA combiner interface fault


25.2 Error DescriptionAn excessive level of Radio Frequency (RF) reflected power occurred. The cable between the Power Amplifier (PA) and the DUAMCO may be damaged or not con-nected. As a consequence, the PA is switched off.

The PA was put out of service. This leads to a scenario in which cells or calls could potentially be lost. The states of all affected managed objects are then changed accord-ingly.

25.3 Troubleshooting (LMT)1. Check the cable connection between the PA and the DUAMCO:

• For correct attached and tightened connectors (N-type) at PA and DUAMCO • Undamaged cable (visual inspection)☞ Two different lengths of the RG142 cables are used, depending on whether the

PA is located left (80 mm) or right (250 mm) of the DUAMCO.

2. A damaged cable has to be replaced by the right type and length.3. If the error has not ceased yet, the related card has to be replaced. Replacement

must be done according to the “Replacing Node B Units” manual, “Tasklist”.


Lpa, Booster, Cat


Probable Cause: TransmitterFailure

Severity: major



To prevent uncontrolled emission of microwave radiation, switch off the relevant breakers which supply the LPAs/CATs involved in the affected antenna branch before replacing antenna cables, antennas, cables connected to the output of the power ampli-fier, TMAs, or DUAMCOs.


67

Troubleshooting Node B 200919 - Failure in the DC supply of PA


26 200919 - Failure in the DC supply of PA


26.2 Error DescriptionA failure in the internal DC supply of the Power Amplifier (PA) occurred. As a conse-quence, the PA is switched off.

The PA was put out of service. This leads to a scenario in which cells or calls could potentially be lost. The states of all affected managed objects change accordingly.

26.3 Troubleshooting (LMT)At the front of the PA the state of the DC supply is shown by an LED marked “POWER”. This LED can either be ON or OFF, depending on the failure cause inside the PA.

To clear the alarm cause, replace the reporting PA (or external module). Replacement must be done according to the “Repacing Node B Units” manual, “Tasklist”.


Lpa, Booster, Cat, Rrh, Drx



Severity: major

68 DN70580522Issue 01A



200920 - High temperature of PA

27 200920 - High temperature of PA


27.2 Error DescriptionThe temperature of the PA has exceeded the maximum operating temperature speci-fied. This could be caused by an internal problem of the PA or by insufficient cooling of the rack/shelter.

If this alarm is reported by a booster, the 201034 - Booster’s Fan unit failed alarm may be the root cause for the failure reported by this alarm.

An additional rack/shelter temperature alarm (200995 or 200996) or fan alarms (200914) may indicate that the air circulation is decreased. A fan unit could be defective or, especially for outdoor shelters, obstructed air in- or outlets could also reduce the cooling capability.

This alarm message may occur in conjunction with temperature alarms: • 200914 - Fan unit failed • 200995 - High Temperature Limit (Ht3) reached • 200996 - Critical Temperature Limit (Ht4) reached






Probable Cause: HighTemperature

Severity: minor


69

Troubleshooting Node B 200920 - High temperature of PA


27.3 Troubleshooting (LMT)Depending on the actual problem, perform one of the following tasks: • In the event that the following preconditions are met, i.e.

– The “200920 – High temperature of PA” alarm is reported by a booster and– The “201034 – Booster’s Fan unit failed” alarm has been output before,refer to the error description of the “201034 – Booster’s Fan unit failed” alarm and follow the troubleshooting accordingly. Reason: the “201034 – Booster’s Fan unit failed” alarm may indicate the root cause for the failure reported by this alarm.

• If this alarm is raised for one single PA only, it is most likely that the PA itself has got a problem. Replace the reporting PA. Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.

• If one or more fan alarms or a rack/shelter temperature alarm is reported the addressed fan unit should be checked and possibly replaced. Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.

• A rack/shelter temperature alarm leads one to assume that the air circulation is decreased by obstructed air in- or outlets. Check and clean the air in- and outlets according to the section “Cleaning of Air In- and Outlets” in the “Maintaining the Node B” manual.

70 DN70580522Issue 01A



200921 - Over temperature of PA

28 200921 - Over temperature of PA


28.2 Error DescriptionThe PA is overheated and a high temperature alarm (200920 - High temperature of PA) may be preceded. Because the temperature has reached a level that would cause damage, the PA is switched off. This could be caused by an internal problem of the PA or by insufficient cooling capacity of the rack/shelter.

If this alarm is reported by a booster, the 201034 - Booster’s Fan unit failed alarm may be the root cause for the failure reported by this alarm.

An additional rack/shelter temperature alarm (200995 or 200996) or fan alarms (200914) may indicate that the air circulation is decreased. A fan unit could be defective or, especially for outdoor shelters, obstructed air in- or outlets could also reduce the cooling capability.

As a consequence, the PA was put out of service. Cells and/or calls could potentially be lost. The states of all affected managed objects change accordingly.

This alarm message may occur in conjunction with temperature alarms: • 200914 - Fan unit failed • 200995 - High Temperature Limit (Ht3) reached • 200996 - Critical Temperature Limit (Ht4) reached



28.3 Troubleshooting (LMT)Depending on the actual problem, perform one of the following tasks: • In the event that the following preconditions are met, i.e.

– The “200921 – Over temperature of PA” alarm is reported by a booster and




Probable Cause: ExcessiveTransmitterTemperature

Severity: major


71

Troubleshooting Node B 200921 - Over temperature of PA


– The “201034 – Booster’s Fan unit failed” alarm has been output before,refer to the error description of the “201034 – Booster’s Fan unit failed” alarm and follow the troubleshooting accordingly. Reason: the “201034 – Booster’s Fan unit failed” alarm may indicate the root cause for the failure reported by this alarm.

• If this alarm is raised for one single PA only, it is most likely that the PA itself has got a problem. Replace the reporting PA. Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.

• If one or more fan alarms or a rack/shelter temperature alarm is reported, the addressed fan unit should be checked and possibly replaced. Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.

• A rack/shelter temperature alarm leads one to assume that the air circulation is decreased by obstructed air in- or outlets. Check and clean the air in- and outlets according to the section “Cleaning of Air In- and Outlets” in the “Maintaining the Node B” manual.

72 DN70580522Issue 01A



200922 - RF performance not being met due to bad linearization

29 200922 - RF performance not being met due to bad linearization


29.2 Error DescriptionThe PA linearization technics does not work correctly and could result in signal quality not being met. The PA is switched off. The PA was, furthermore, put out of service.

As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.

29.3 Troubleshooting (LMT)To clear the alarm cause, the addressed card or external module (such as RRHs) has to be replaced. Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.


Lpa, Booster, Cat, Rrh


Probable Cause: SignalQualityEvaluationFault

Severity: major


73

Troubleshooting Node B 200923 - Internal failure of PA detected


30 200923 - Internal failure of PA detected


30.2 Error DescriptionA fatal vendor specific hardware or software failure inside the PA was detected and the PA was switched off. Furthermore, the PA was put out of service.

The card should be replaced.

Cells or calls could potentially be lost. The states of all affected managed objects change accordingly.

30.3 Troubleshooting (LMT)1. First, reset the addressed card or external module.

Depending on the reporting managed object, use the TREE View window of the LMT and apply the respective command:Booster Booster “reset”CAT Cat “reset”DRX Drx “reset”LPA Lpa “reset”RRH Rrh “reset”

2. If the fault cannot be cleared by reset, the addressed card/external module has to be replaced. Replacement must be done according to the “Replacing Node B Units” instructions.





Severity: major

74 DN70580522Issue 01A


Id:0900d8058022b46eConfidential

200924 - Input power level of LPA too high but LPA can still hold its RF specification

31 200924 - Input power level of LPA too high but LPA can still hold its RF specification


31.2 Error DescriptionThe LPA detected an input power level from a TRX card that is above the nominal value. However, the specifications relating to the RF output are still met. There is no imminent danger for the LPA to be damaged.

A further power level increase will result in the error report 200925 - Input power level of PA too high with the higher severity level “major” and a shutdown of the LPA is inevita-ble.

31.3 Troubleshooting (LMT)Take the following measures to clear the alarm cause:1. Check the cables connections.2. Monitor the connected TRX card for a high output level.

g If the output power increases further, the error “200925 – Input power level of PA too high” will occur and the LPA will be switched off.

3. Precautionary, replace the TRX card.Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.


Lpa


Probable Cause: ExcessiveTransmitterOutputPower

Severity: minor


75

Troubleshooting Node B 200925 - Input power level of PA too high


32 200925 - Input power level of PA too high


32.2 Error DescriptionThe PA detected an input power level that would cause the PA to fail specifications relating to the RF output or damaging the PA. According to the following cases, the input power level may be either analog or digital:

• Case 1: This alarm occurred in an LPA, receiving its input power from a TRX card. Thus, the analog input power level is too high.

• Case 2: This alarm occurred in a CAT/RRH, receiving its input power from DRIC. The following causes may be the root for this failure:– The digital input power level has been too high for a certain period of time. In this

case, an autonomous gain correction was not possible.– Too rapid digital input signal variations could not be processed adequately.– The CAT/RRH itself produces too much power.

To avoid this the PA is switched off. As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.

It may be that the error reports 200924 - Input power level of LPA too high but LPA can still hold its RF specification if LPA is affected, or 201018 - The LRU could not process a message from CC if CAT/RRH is affected, were emitted before, being a sign of increasing power level input at the PA.

32.3 Troubleshooting (LMT)Take the following measures to clear the alarm cause:1. First, check the cables connections.2. The related card or external module (such as RRHs) has to be replaced.



Lpa, Booster, Cat, Rrh



Severity: major

76 DN70580522Issue 01A



200926 - CPU failure of baseband card

33 200926 - CPU failure of baseband card


33.2 Error DescriptionA fatal software or hardware error arose: a boot or watchdog error of a CPU occurred.

After an unsuccessful automatic recovery by means of a reset, the reporting BB card was put out of service.


33.3 Troubleshooting (LMT)1. First, reset the addressed card.

Use the TREE View window of the LMT and, depending on the reporting managed object, apply the respective command:CHC Ch “reset”DRIC Dric “reset”REP Rep “reset”TRX Trx “reset”

2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the “Replacing Node B Units” instructions.

3. Furthermore, contact the technical assistance center (TAC) to get support in isolat-ing the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


Ch, Rep, Trx, Dric


Probable Cause: ProcessorProblem

Severity: major (final), handled according to the Fault Escalation Strategy


77

Troubleshooting Node B 200927 - Volatile memory failure of baseband card


34 200927 - Volatile memory failure of baseband card


34.2 Error DescriptionA failure of an SDRAM (synchronous dynamic random access memory) was detected.







Ch, Rep, Trx, Dric


Probable Cause: EquipmentMalfunction


78 DN70580522Issue 01A



200928 - Non-volatile memory failure of baseband card

35 200928 - Non-volatile memory failure of baseband card


35.2 Error DescriptionA checksum error was found for a ROM (read only memory).

After an unsuccessful automatic recovery by means of a reset, the reporting BB card was put of service.






Ch, Rep, Trx, Dric


Probable Cause: CorruptData



79

Troubleshooting Node B 200929 - DSP failure

Id:0900d8058022b48fConfidential

36 200929 - DSP failure


36.2 Error DescriptionA boot or watchdog error of a UTOPIA relevant DSP (digital signal processor) occurred.







Ch, Rep, Trx, Dric




80 DN70580522Issue 01A



200931 - FPGA failure

37 200931 - FPGA failure


37.2 Error DescriptionA configuration failure of an FPGA (field programmable gate array) was detected.







Ch, Rep, Trx, Dric





81

Troubleshooting Node B 200932 - Control FPGA failure

Id:0900d8058022b49bConfidential

38 200932 - Control FPGA failure


38.2 Error DescriptionA control FPGA (field programmable gate array) failure occurred.







Ch, Rep, Trx, Dric




82 DN70580522Issue 01A



200933 - External timing signal failure

39 200933 - External timing signal failure


39.2 Error DescriptionFor synchronizing the baseband cards (CH, REP, TRX, DRIC) the Core Controller (CC) sends timing signals via the UTOPIA bus and clock busses. These timing signals derive from the master clock generator of the Core Controller.

• If only one baseband card sends the alarm message: There is a hardware failure in the baseband card. The Node B is degraded in its performance.

• If several baseband cards send the alarm message: There is a failure in the Core Controller. The uplink and downlink connections of the Node B are affected. All affected cells are lost.



39.3 Troubleshooting (LMT)1. Contact the technical assistance center (TAC) to get support in isolating the fault.


2. Reset the addressed card.Use the TREE View window of the LMT and, depending on the reporting managed object, apply the respective command:CHC Ch “reset”DRIC Dric “reset”REP Rep “reset”TRX Trx “reset”

3. If only one baseband card sends the alarm message and the fault cannot be cleared by reset, replace this baseband card. Replacement must be done according to the “Replacing Node B Units” instructions.

4. If several baseband cards send the alarm message and the fault cannot be cleared by reset, replace the CC. Replacement must be done according to the “Replacing Node B Units” instructions.


Ch, Rep, Trx, Dric





83

Troubleshooting Node B 200934 - Failure of the RF part of the TRX


40 200934 - Failure of the RF part of the TRX


40.2 Error DescriptionThere is a hardware failure in the TRX card. Within the TRX card, the radio frequency block (RF) handles the downlink signals. If there is a failure in the RF part, the TRX card does not transmit downlink signals any longer.

After an unsuccessful automatic recovery by means of a reset, the reporting TRX card was put out of service.


40.3 Troubleshooting (LMT)1. First, reset the addressed TRX card.

Use the TREE View window of the LMT and apply the Trx “reset” command to it.2. The TRX card can be blocked locally. The card or carrier can also be blocked from

the LMT.Make sure that the card is not blocked. In other words, confirm that the administra-tive state of the relevant TRX card is set to unlocked.Use either the TREE View window or the RACK View window of the LMT and apply the Trx “Set administrativeState Unlocked” command to the reporting TRX.



Trx




84 DN70580522Issue 01A


Id:0900d8058022b4adConfidential

200935 - LVDS Failure

41 200935 - LVDS Failure


41.2 Error DescriptionThe LVDS (low voltage differential signal) is an internal connection between the baseband cards. This alarm message occurs if the communication between the baseband cards is interrupted.



This alarm message may occur in conjunction with the 200933 - External timing signal failure.



2. Replace the defective card.Replacement must be done according to the “Replacing Node B Units” instructions.


Ch, Rep, Trx, Dric


Probable Cause: RemoteNodeTransmissionError



85

Troubleshooting Node B 200936 - Local bus failure around the CPU


42 200936 - Local bus failure around the CPU


42.2 Error DescriptionLocal bus failure around the CPU.







Ch, Rep, Trx, Dric


Probable Cause: RemoteNodeTransmissionError


86 DN70580522Issue 01A



200937 - FTP connection failure

43 200937 - FTP connection failure


43.2 Error DescriptionFTP (file transfer protocol) connection between CC card (Core Controller) and BB card (baseband) or CAT (combined amplifier and transceiver) or RRH (remote radio head) could not be established.

After an unsuccessful automatic recovery by means of a reset, the reporting LRU was put out of service.


The error should be reported to customer services. The root of the problem may be a hardware or software error.

43.3 Troubleshooting (LMT)1. First, reset the addressed card or external module (such as RRHs).

Use the TREE View window of the LMT and, depending on the reporting managed object, apply the respective command:CAT Cat “reset”CHC Ch “reset”DRIC Dric “reset”DRX Drx “reset”REP Rep “reset”RRH Rrh “reset”TRX Trx “reset”




Ch, Rep, Trx, Dric, Cat, Rrh, Drx


Probable Cause: TransmissionError



87

Troubleshooting Node B 200938 - CRC error during software image check

Id:0900d8058022b4bfConfidential

44 200938 - CRC error during software image check


44.2 Error DescriptionA CRC (cyclic redundancy check) error has been detected while checking the SWI (soft-ware image). This alarm message may occur if a new SW load is activated, which, however, is defective. If no new SW load has been activated, there is an error in the soft-ware.

After an unsuccessful automatic recovery by means of a reset, the reporting BB card was put out of service. As a consequence, cells and/or calls could potentially be lost. The states of all affected managed objects change accordingly.



Ch, Rep, Trx, Dric


Probable Cause: FileError


88 DN70580522Issue 01A



200939 - Static configuration file CRC check failed

45 200939 - Static configuration file CRC check failed


45.2 Error DescriptionA CRC (cyclic redundancy check) error has been detected while checking the static con-figuration file. This alarm message may occur if a new SW load is activated, which, however, is defective. If no new SW load has been activated, there is an error in the soft-ware.

After an unsuccessful automatic recovery by means of a reset, the reporting BB card was put out of service. As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.



Ch, Rep, Trx, Dric





89

Troubleshooting Node B 200940 - Software activation failed

Id:0900d8058022b4cbConfidential

46 200940 - Software activation failed


46.2 Error DescriptionThe SW version specified in the SW activation command could not be activated.



46.3 Troubleshooting (LMT)1. Report this error to the technical assistance center (TAC). For suitable preparation

save the error symptoms as described in “Collect Info for Assistance”. Special actions must be taken and log files need to be analyzed which are out of the opera-tor’s scope.

2. Reset the addressed card.Use the TREE View window of the LMT and, depending on the reporting managed object, apply the respective command:CHC Ch “reset”DRIC Dric “reset”REP Rep “reset”TRX Trx “reset”



Ch, Rep, Trx, Dric


Probable Cause: SoftwareProgramAbnormallyTermi-nated


90 DN70580522Issue 01A



200941 - Internal clock failure

47 200941 - Internal clock failure


47.2 Error DescriptionA failure of the internal clock occurred.








Ch, Rep, Trx, Dric


Probable Cause: TimingProblem



91

Troubleshooting Node B 200942 - Configuration file inconsistent


48 200942 - Configuration file inconsistent


48.2 Error DescriptionA configuration file contains inconsistent data.



48.3 Troubleshooting (LMT)1. Report this error to the technical assistance center (TAC). For suitable preparation

save the error symptoms as described in “Collect Info for Assistance”. Special actions must be taken and log files need to be analyzed which are out of the opera-tor’s scope.

2. Reset the addressed card or external module (such as RRHs).Use the TREE View window of the LMT and, depending on the reporting managed object, apply the respective command:CAT Cat “reset”CHC Ch “reset”DRIC Dric “reset”DRX Drx “reset”REP Rep “reset”RRH Rrh “reset”TRX Trx “reset”







92 DN70580522Issue 01A


Id:0900d8058022b4ddConfidential

200943 - IOR file inconsistent

49 200943 - IOR file inconsistent


49.2 Error DescriptionA fatal software error has occurred. The IOR (interoperable object reference) configura-tion file contains inconsistent data.






3. Report this error to the technical assistance center (TAC). For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Special actions must be taken and log files need to be analyzed which are out of the opera-tor’s scope.







93

Troubleshooting Node B 200944 - FTP put failed


50 200944 - FTP put failed


50.2 Error DescriptionA failure occurred while trying to put an FTP (file transfer protocol) file to the CC card (Core Controller). The addressed LRU is reset.

The error should be reported to customer services.

As a consequence of this failure, cells or calls could potentially be lost. The states of all affected managed objects furthermore change accordingly.






Ch, Rep, Trx, Dric



Severity: warning (final), handled according to the Fault Escalation Strategy

94 DN70580522Issue 01A



200945 - FTP manage failure

51 200945 - FTP manage failure


51.2 Error DescriptionA failure occurred in managing the RAM (random access memory) disc via FTP. The addressed LRU is reset.

The error should be reported to customer services.

As a consequence of this failure, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.






Ch, Rep, Trx, Dric



Severity: warning (final), handled according to the Fault Escalation Strategy


95

Troubleshooting Node B 200946 - Still alive supervision failure

Id:0900d8058022b4efConfidential

52 200946 - Still alive supervision failure


52.2 Error DescriptionA still alive supervision failure occurred. It is possible that a hardware or software error is the root of the problem.












96 DN70580522Issue 01A



200947 - Failure in the DC supply of DUAMCO

53 200947 - Failure in the DC supply of DUAMCO


53.2 Error DescriptionThe DUAMCO is switched off. As a consequence, the DUAMCO was put out of service.

Furthermore, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.


Use the TREE View window of the LMT and apply the Duamco “reset” command to the addressed card.

2. If the fault cannot be cleared by reset, the addressed card has to be replaced.Replacement must be done according to the “Replacing Node B Units” instructions.



Duamco



Severity: major



To prevent uncontrolled emission of microwave radiation, switch off the relevant breakers which supply the LPAs/CATs involved in the affected antenna branch before replacing antenna cables, antennas, TMAs, or DUAMCOs.


97

Troubleshooting Node B 200948 - CORBA communication failed

Id:0900d8058022b4fbConfidential

54 200948 - CORBA communication failed


54.2 Error DescriptionThis alarm message is output due to the following fatal error: a CORBA (common object request broker architecture) communication failure between CC and the reporting LRU occurred. It is possible that a hardware or a software error is the root of the problem.




Use the TREE View window of the LMT and, depending on the reporting managed object, apply the respective command:CAT Cat “reset”CHC Ch “reset”DRIC Dric “reset”REP Rep “reset”RRH Rrh “reset”TRX Trx “reset”


3. If the fault cannot be cleared by reset, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


Ch, Rep, Trx, Dric, Cat, Rrh




98 DN70580522Issue 01A



200949 - Internal CORBA call failed

55 200949 - Internal CORBA call failed


55.2 Error DescriptionA fatal software error has occurred! This is a recoverable error situation caused by a potentially serious software fault which should be reported to customer services! The recovery will result in a complete reset of the Node B. Due to the reset, all services will be interrupted.

This means:

• All cells will be lost. • The connection between the Node B and the RNC will be lost. • Uplink or downlink errors will be reported by other Node Bs if they are connected to

the resetting Node B.

All connections to the management system will also be interrupted during this reset period. Once the reset is completed, normal operational service should be resumed i.e. the cells are built up again, connection with the RNC will be re-established, and any cross connections will be built up again. Any calls that were in operation before the reset are lost.



Cc



Severity: warning


99

Troubleshooting Node B 200950 - Timeout for request or modification


56 200950 - Timeout for request or modification


56.2 Error DescriptionA fatal hardware error has occurred. The card did not send an expected response or notification.



56.3 Troubleshooting (LMT)Take the following measures to clear the alarm cause:1. First, reset the addressed card.2. If the fault cannot be cleared by reset, the addressed card has to be replaced.


3. Contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*


Probable Cause: TimeoutExpired


100 DN70580522Issue 01A



200951 - Status notification undefined

57 200951 - Status notification undefined


57.2 Error DescriptionA fatal hardware error has occurred. The card sends an unknown status notification.



57.3 Troubleshooting (LMT)1. First, reset the addressed card.2. If the fault cannot be cleared by reset, contact the technical assistance center (TAC)

to get support in isolating the fault. For suitable preparation save the error symptoms as described in ’Collect Info for Assistance’. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*





101

Troubleshooting Node B 200952 - Maximum number of resets exceeded


58 200952 - Maximum number of resets exceeded


58.2 Error DescriptionA fatal hardware error or software error occurred. The card was not able to start up com-pletely even after performing several numbers of resets.

The reporting LRU was put out of service.


58.3 Troubleshooting (LMT)Take the following actions to clear the alarm condition:1. Since the fault could not be cleared by the numerous resets, the addressed card has

to be replaced.Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.

2. If the fault cannot be cleared by card replacement, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*



Severity: major

102 DN70580522Issue 01A



200953 - CAN bus off

59 200953 - CAN bus off


59.2 Error DescriptionThere is an error detected in the physical CAN communication layer. Service may thus be affected.

This alarm message may occur in conjunction with other CAN-related alarms: • 200954 - No message response on CAN • 200955 - Mount supervision failure • 200956 - Watch dog timer expired • 200957 - Internal CAN processing failure



3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*



Severity: warning


103

Troubleshooting Node B 200954 - No message response on CAN


60 200954 - No message response on CAN


60.2 Error DescriptionThe watchdog timer on the CAN bus is expired. An object on the affected CAN bus therefore performed a reset.



This alarm message may occur in conjunction with other CAN-related alarms: • 200953 - CAN bus off • 200955 - Mount supervision failure • 200956 - Watch dog timer expired • 200957 - Internal CAN processing failure





*




104 DN70580522Issue 01A



200955 - Mount supervision failure

61 200955 - Mount supervision failure


61.2 Error DescriptionA CAN object performed a reset caused by expiration of the mount supervision timer.



This alarm message may occur in conjunction with other CAN-related alarms: • 200953 - CAN bus off • 200954 - No message response on CAN • 200956 - Watch dog timer expired • 200957 - Internal CAN processing failure





*





105

Troubleshooting Node B 200956 - Watch dog timer expired


62 200956 - Watch dog timer expired


62.2 Error DescriptionThe watch dog timer on CAN bus expired.

If the reporting managed object is a CAT (combined amplifier and transceiver) or a RRH (remote radio head), the following applies: The CAT’s/RRH’s CPU (central processing unit) watchdog detected a CPU failure.



This alarm message may occur in conjunction with other CAN-related alarms: • 200953 - CAN bus off • 200954 - No message response on CAN • 200955 - Mount supervision failure • 200957 - Internal CAN processing failure





*


Probable Cause: WatchDogTimerExpired


106 DN70580522Issue 01A



200957 - Internal CAN processing failure

63 200957 - Internal CAN processing failure


63.2 Error DescriptionA CAN object performed a reset caused by an internal processing failure.



This alarm message may occur in conjunction with other CAN-related alarms: • 200953 - CAN bus off • 200954 - No message response on CAN • 200955 - Mount supervision failure • 200956 - Watch dog timer expired





*





107

Troubleshooting Node B 200958 - Timer for the reset supervision expired


64 200958 - Timer for the reset supervision expired


64.2 Error DescriptionThe timer for the reset supervision has been expired.



64.3 Troubleshooting (LMT)1. First, reset the addressed card.2. If the fault cannot be cleared by reset, contact the technical assistance center (TAC)

to get support in isolating the fault. For suitable preparation save the error symptoms as described in ’Collect Info for Assistance’. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*




108 DN70580522Issue 01A



200959 - Missing response from baseband card

65 200959 - Missing response from baseband card


65.2 Error DescriptionThe following fatal error has occurred: NBAP (Node B application part) has detected a missing response from a baseband card. It is possible that a hardware or software error is the root of the problem. The problem may be located either in the reporting baseband (BB) card or in the core controller (CC).



The error should be reported to customer service.


Use the TREE View window of the LMT and, depending on the reporting baseband card, apply the following command:CHC (Ch) Ch “reset”REP (Rep) Rep “reset”TRX (Trx) Trx “reset”DRIC (Dric) Dric “reset”

2. If the fault cannot be cleared by reset, replace defective cards:2.1 Replace the addressed baseband card.2.2 Even though the alarm is reported by a baseband card, the core controller may

also be the root cause of the detected problem. Therefore, replace the core con-troller.

For either card, replacement must be done according to the “Replacing Node B Units” instructions.

3. If the card replacement did not clear the fault, either, contact the technical assis-tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


Ch, Rep, Trx, Dric





109

Troubleshooting Node B 200960 - Invalid response from baseband card


66 200960 - Invalid response from baseband card


66.2 Error DescriptionThe following fatal software error has occurred: NBAP (Node B application part) has detected an invalid response from a baseband card. It is possible that a hardware or software error is the root of the problem.



The error should be reported to customer service.






Ch, Rep, Trx, Dric


Probable Cause: InvalidMessageReceived


110 DN70580522Issue 01A


Id:0900d8058022b55dConfidential

200961 - Firmware download failure

67 200961 - Firmware download failure


67.2 Error DescriptionA fatal hardware error was detected while downloading the FW (firmware) or no FW is available at all at the card.

The reporting LRU was put out of service.






*


Probable Cause: SoftwareDownloadFailure

Severity: major


111

Troubleshooting Node B 200980 - Invalid MO


68 200980 - Invalid MO


68.2 Error DescriptionAn object was accessed at the CAN bus which does not exist or which is not mounted.

There may be following causes:

• The Node B database is defective. A new database was installed but does not match the hardware configuration.

• The hardware configuration is invalid. A new hardware equipment was installed but does not match the database.

• A software error has occurred.

68.3 Troubleshooting (LMT)Perform the following tasks in the given order to solve this alarm:1. Check if the Node B works with the newest version of the database. Use the

mibCheck or mibCheckWin tool delivered with the Node B’s software. Proceed according to the “Node B Database Editing Guide”.

2. If necessary, change the running database. Edit the database according to the “Node B Database Editing Guide”.

3. Otherwise, if the database was not defective, check the hardware configuration.Check the entry in the database and check the addressed MO on site. There might have been a change of the MO type on site or in the configuration, which was not edited in the database.

4. If the error is not caused by an invalid database or an unsuitable hardware configu-ration, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*


Probable Cause: DatabaseInconsistency

Perceived severity: warning

112 DN70580522Issue 01A



200981 - MO not mounted

69 200981 - MO not mounted


69.2 Error DescriptionThe specified MO is not mounted.

69.3 Troubleshooting (LMT)Check if the addressed card is equipped. If not, insert a card of the required type, HW and FW state. Proceed according to the installation manual (IMN) of the reporting Node B type: • For NB-440 or NB-880, refer to “Installing NB-440/NB-880”. • For NB-441 or NB-881, refer to “Installing NB-441/NB-881”. • For NB-420 or NB-860, refer to “Installing NB-420/NB-860”. • For NB-861, refer to “Installing NB-861”. • For NB-341, refer to “Installing NB-341”. • For Radio Server Slider Unit RSSU-380, refer to “Installing RSSU-380”. • For Radio Server RS-381, refer to “Installing RS-381”. • For Radio Server RS-880, refer to “Installing RS-880”.


*


Probable Cause: Unavailable

Severity: warning


113

Troubleshooting Node B 200982 - Invalid command


70 200982 - Invalid command


70.2 Error DescriptionA CAN command is invalid.

This alarm may be caused by one of the following: • The Node B database is defective. A new database was installed but does not

match the hardware configuration. • The hardware configuration is invalid. A new hardware equipment was installed but

does not match the database. • A software error has occurred.

70.3 Troubleshooting (LMT)Perform the following tasks in the given order to solve this alarm:1. Check the Node B database and software version. Use the mibCheck or mibCheck-

Win tool delivered with the Node B’s software. Proceed according to the “Node B Database Editing Guide”.



4. If the error is not caused by an invalid database or an unsuitable hardware configu-ration: Contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*



Severity: warning

114 DN70580522Issue 01A



200983 - Invalid parameter in command

71 200983 - Invalid parameter in command


71.2 Error DescriptionA CAN command contains an invalid parameter.

This alarm may be caused by one of the following: • The Node B database is defective. A new database was installed but does not

match the hardware configuration. • The hardware configuration is invalid. A new hardware equipment was installed but

does not match the database. • A software error has occurred.

71.3 Troubleshooting (LMT)Perform the following tasks in the given order to solve this alarm:1. Check the Node B database and software version. Use the mibCheck or mibCheck-

Win tool delivered with the Node B’s software. Proceed according to the “Node B Database Editing Guide”.



4. If the error is not caused by an invalid database or an unsuitable hardware configu-ration: Contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*


Probable Cause: InvalidParameter

Severity: warning


115

Troubleshooting Node B 200984 - Firmware download access file error


72 200984 - Firmware download access file error


72.2 Error DescriptionFW (firmware) download access file error. The access to the card firmware is not possi-ble. Probably providing a wrong software causes the problem.

72.3 Troubleshooting (LMT)Take the following measures to clear the alarm cause:1. Contact the technical assistance center (TAC) to get support in isolating the fault.


2. Choose the appropriate FW file for the selected card.3. Download the FW to the card. The download has to be done separately for each

card. (At a particular time, FW download is only possible to one card).


*



Severity: warning

116 DN70580522Issue 01A



200985 - CAN transaction error

73 200985 - CAN transaction error


73.2 Error DescriptionA CAN transaction error occurred. The card will be reset after inconsistency of data during communication over CAN, e.g. message time-outs, unexpected responses or errors while download of the firmware.






*



Severity: warning


117

Troubleshooting Node B 200986 - Temperature out of range in upper direction


74 200986 - Temperature out of range in upper direction


74.2 Error DescriptionNormally, this alarm is output when the temperature sensor wired to the ACTC board is not connected. In this case, the temperature may rise to critical values without any threshold alarms being raised.

The alarm may however also occur in combination with the 200996 - Critical Tempera-ture Limit (Ht4) reached alarm. In this case, the temperature at the temperature sensor wired to the ACTC board is out of range in upper direction. The temperature is above +87 °C (188.6 °F). When both the “200986 - Temperature out of range in upper direc-tion” and the “200996 - Critical Temperature Limit (Ht4) reached” alarm are output, immediate further proceeding according to the 200996 - Critical Temperature Limit (Ht4) reached alarm has to be done. Otherwise, severe hardware damage can occur.



74.3 Troubleshooting (LMT)The procedure to clear this alarm (“200986 – Temperature out of range in upper direc-tion”) depends on whether or not the “200996 – Critical Temperature Limit (Ht4) reached” alarm is output in combination with this alarm. Proceed as follows:1. Check whether the “200996 – Critical Temperature Limit (Ht4) reached” alarm is

also output.Using the ALARM View window of the LMT, proceed as follows:– Click on the “Alarm View” button or use the shortcut key combination Ctrl + A .– Look for a “200996 – Critical Temperature Limit (Ht4) reached” alarm in the

reporting Node B.2. The further proceeding depends on the result of the analysis in the previous step.


BaseRack, ServiceRack



Severity: minor

118 DN70580522Issue 01A



200986 - Temperature out of range in upper direction

– If the “200996 – Critical Temperature Limit (Ht4) reached” alarm is output, proceed according to the troubleshooting of the 200996 – Critical Temperature Limit (Ht4) reached alarm.

– If the “200996 – Critical Temperature Limit (Ht4) reached” alarm is not output, check the sensor connections.


119

Troubleshooting Node B 200987 - Hardware parameter invalid


75 200987 - Hardware parameter invalid


75.2 Error DescriptionThis alarm indicates that an unknown hardware parameter has been received. The reporting card will be reset after it has delivered an unknown hardware parameter.

Normally, this alarm would have been caused by an incompatible hardware configura-tion, a defective database, etc.

In this case, however, the Node B software reports an invalid hardware parameter although neither the hardware configuration nor the Node B database are mismatched! In fact, this is an error in the software which should be reported to customers service.

Due to the reason that this is a software error rather than an incompatibility in the database or hardware configuration, checking or changing the Node B’s database and hardware configuration would not help to solve this alarm.

As a consequence of this failure, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.



*



Severity: warning

120 DN70580522Issue 01A



200988 - Response unknown

76 200988 - Response unknown


76.2 Error DescriptionA non-fatal software error has occurred. An unknown response has been received.

76.3 Troubleshooting (LMT)Take the following measures to clear the alarm cause:1. Reset the addressed card.2. If the fault could not be cleared by the reset, replace the addressed card.


3. If the fault cannot be cleared by replacement of the card, contact the technical assis-tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*


Probable Cause: MessageNotExpected

Severity: warning


121

Troubleshooting Node B 200989 - No CORBA proxy available for LRU


77 200989 - No CORBA proxy available for LRU


77.2 Error DescriptionThis alarm is output due to the following fatal software error: there is no CORBA (common object request broker architecture) proxy available for the addressed LRU.



77.3 Troubleshooting (LMT)Perform the following tasks in the given order to solve this error:1. First, reset the addressed card or external module (such as RRHs).



3. If the card replacement did not clear the fault, either, contact the technical assis-tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.






122 DN70580522Issue 01A


Id:0900d8058022b5afConfidential

200990 - No still alive response from LRU

78 200990 - No still alive response from LRU


78.2 Error DescriptionThis alarm message is output due to the following fatal software error: no still alive response from the addressed LRU has been received.


The error should be reported to the customers service.


78.3 Troubleshooting (LMT)Perform the following tasks in the given order:1. First, reset the addressed card or external module (such as RRHs).



3. If the card/external module replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.







123

Troubleshooting Node B 200991 - Duplex error


79 200991 - Duplex error


79.2 Error DescriptionThe duplex error occurs in the event of: • Receive logical channel FIFO overrun on duplex. • Loss of signal alarm on duplex. • Loss of cell delineation. • HCS-error on RXD interface on duplex. • Cell delineation state out of sync. • Transmit logical channel FIFO overrun on duplex. • Unable to lock input reference clock on duplex. • Invalid start of cell sequence on utopia input port on duplex.

As a consequence of this failure, service may be affected. Thus, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.

79.3 Troubleshooting (LMT)Perform the following tasks in the given order:1. First, reset the addressed card. Use the TREE View window of the LMT or, alterna-

tively, apply the Cc “reset” command to the addressed card.2. If the fault cannot be cleared by reset, the addressed card has to be replaced.

Replacement must be done according to the “Replacing Node B Units” instructions.3. If the card replacement did not clear the fault, contact the technical assistance

center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


Cc




124 DN70580522Issue 01A


Id:0900d8058022b5bbConfidential

200992 - Software error

80 200992 - Software error


80.2 Error DescriptionThis error occurs in the event of: • Flash error • CAN receive or transmit queue overflow • Interrupt queue overflow


80.3 Troubleshooting (LMT)Perform the following tasks in the given order to solve this error:1. First, reset the addressed card. Use the TREE View window of the LMT or, alterna-





Cc



Severity: critical


125

Troubleshooting Node B 200993 - Unexpected alarm status bit


81 200993 - Unexpected alarm status bit


81.2 Error DescriptionUnexpected CAN status notification occurs in the event of:

• CRC-8 error for the whole received cell (RXD) on duplex.

• Remote defect indication (RDI) received on LVDS (low voltage differential signal) on duplex.

• SRAM, duplex, EEPROM or CAN voltage error.


81.3 Troubleshooting (LMT)Perform the following tasks in the given order to solve this error:1. First, reset the addressed card. Use the TREE View window of the LMT or, alterna-





Cc



Severity: critical

126 DN70580522Issue 01A



200994 - Hardware Failure

82 200994 - Hardware Failure


82.2 Error DescriptionThis alarm is output in the event of: • PLL of DC/DC-unit unlocked • Voltage or current out of range • Insufficient or excess temperature on DC/DC-unit • HSDPA throughput degraded • Boot parameter check failure

The different errors can be distinguished by means of the “Additional Text” field in this alarm’s row (ALARM View window of the LMT or “Alarm Monitoring” application of the Radio Commander).

82.3 Troubleshooting (LMT)If the alarm is output due to the “Boot parameter check failure”, contact the the technical assistance center (TAC) before resetting or replacing equipment. For suitable prepara-tion save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

Perform the following tasks in the given order to solve this error:1. First, reset the addressed card. Use the TREE View window of the LMT and apply

the Cc “reset” command to the addressed card.2. If the fault cannot be cleared by reset, the addressed card has to be replaced.




Cc



Severity: minor


127

Troubleshooting Node B 200995 - High Temperature Limit (Ht3) reached

Id:0900d8058022b5cfConfidential

83 200995 - High Temperature Limit (Ht3) reached


83.2 Error DescriptionThe Node B rack/shelter internal temperature has reached a high level (Ht3). If the tem-perature increases further (by 2 °C, which is equivalent to 3.6 °F) the critical level (Ht4) will be reached. See also 200996 - Critical Temperature Limit (Ht4) reached. The tem-perature level depends on the Node B type and is as follows:

• NB-441/NB-881/NB-861: Ht3 = 63 °C (125.6 °F) • NB-440/NB-880/RS-880/RSSU-380: Ht3 = 59 °C (138.2 °F) • NB-420/NB-860: Ht3 = 61 °C (141.8 °F) • NB-341/RS-381: Ht3 = 70 °C (158 °F)

This alarm message may occur in conjunction with 200920 - High temperature of PA and 200921 - Over temperature of PA.

This alarm is cleared if the temperature decreases to the Ht2 level, which depends also on the Node B type:


g NOTEIf the reporting Node B is of type NB-441/NB-881/NB-861, this alarm may be caused by a polluted membrane filter (MEF). Therefore, if the Node B site is located in heavily air-polluted environments combined with special temperature conditions, a maintenance of the MEF filters in the outdoor NB-441/NB-881/NB-861 might be nec-essary.


83.3 Troubleshooting (LMT)First, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assis-





Severity: major

128 DN70580522Issue 01A


Id:0900d8058022b5cfConfidential

200995 - High Temperature Limit (Ht3) reached

tance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

Additional fan alarms such as “200914 – Fan unit failed” may indicate the basic cause.

For indoor Node Bs:1. Check the fan units.2. Is the environmental temperature in the specified range?

For outdoor Node Bs:1. Check the fan units.2. Are the air in- and outlets free from air stream blocking material?3. Make sure the heater units are not switched on undesignedly.


129

Troubleshooting Node B 200996 - Critical Temperature Limit (Ht4) reached


84 200996 - Critical Temperature Limit (Ht4) reached


84.2 Error DescriptionThe Node B rack/shelter internal temperature has reached a critical level (Ht4). An immediate operator action is required: Switch off the Node B! Otherwise a severe hardware damage can occur.

The temperature level depends on the Node B type and is as follows:

• NB-441/NB-881/NB-861: Ht4 = 65 °C (149 °F) • NB-440/NB-880/RS-880/RSSU-380: Ht4 = 61 °C (141.8 °F) • NB-420/NB-860: Ht4 = 63 °C (145.4 °F) • NB-341/RS-381: Ht4 = 72 °C (161.6 °F)

This alarm message may occur in conjunction with 200920 - High temperature of PA, 200921 - Over temperature of PA, and 200986 - Temperature out of range in upper direction.

This alarm is cleared if the temperature decreases to the Ht2 level, which depends also on the Node B type:


g NOTEIf the reporting Node B is of type NB-441/NB-881/NB-861, this alarm may be caused by a polluted membrane filter (MEF). Therefore, if the Node B site is located in heavily air-polluted environments combined with special temperature conditions, a maintenance of the MEF filters in the outdoor NB-441/NB-881/NB-861 might be nec-essary.







Severity: major

130 DN70580522Issue 01A



200996 - Critical Temperature Limit (Ht4) reached

An overtemperature scenario in the Node B can lead to a self-disabling of B-shelf cards. The Node B handles self-disabled cards as if a fatal board failure, such as an on-board power supply failure, has occurred. In other words, the combination of OST/AVS then changes to disabled/not installed and the LED of the self-disabled card is off.

Switch off the Node B immediately! Otherwise, severe hardware damage can occur.

Additional fan alarms such as 200914 - Fan unit failed may indicate the basic cause.

For indoor Node Bs:1. Check the fan units.

Use the LMT’s TREE View window and apply the Fan “Get All Attributes” command to all related fan units.

2. Is the environmental temperature in the specified range?

For outdoor Node Bs:1. Check the fan units.

Use the LMT’s TREE View window and apply the Fan “Get All Attributes” command to all related fan units.

2. Are the air in- and outlets free from air stream blocking material?Perform a visual inspection and, if necessary, preventive maintenance tasks on site (check the air filter, heat exchanger). Both tasks must be done according to the “Replacing Node B Units” instructions.

3. Make sure the heater units are not switched on undesignedly.


131

Troubleshooting Node B 200997 - Lower Temperature Limit (Ht0) reached

Id:0900d8058022b5ddConfidential

85 200997 - Lower Temperature Limit (Ht0) reached


85.2 Error Description The Node B rack/shelter internal temperature has reached the lower limit (Ht0). Below this temperature electronic equipment does not work reliably.

The temperature level for all Node B types is: • Ht0 = -5 °C (23 °F)

This alarm is cleared, if the temperature increases to the Ht1 level, which is Node B dependent: • NB-441/NB-881/NB-881 HR/NB-861: Ht1 = 5 °C (41 °F) • NB-440/NB-880/NB-580/RS-880/RSSU-380: Ht1 = 5 °C (41 °F) • NB-420/NB-860: Ht1 = 5 °C (41 °F) • NB-341/RS-381: Ht1 = 0 °C (32 °F)

85.3 Troubleshooting (LMT)Even the Node B’s own power dissipation is not sufficient to keep the rack/shelter internal temperature above the lowest operating limit.

Take the following measures to clear the alarm cause: • For indoor Node Bs:

Rooms with electronic equipment are usually temperature-controlled by radiators and/or air condition systems:– Check radiator for sufficient heating– Check windows, doors etc. for perfect closing (infiltration)

• For outdoor Node Bs:– Are heater units installed for keeping the shelter internal temperature above -

5°C (23 °F) under worst environmental conditions?– Do the heater units work? Check the power supply, proper connection, and

ohmic resistance.– Replace the heater units if identified as defective.





Probable Cause: LowTemperature

Severity: minor

132 DN70580522Issue 01A



200998 - Temperature out of range in lower direction

86 200998 - Temperature out of range in lower direction


86.2 Error Description The temperature at the temperature sensor wired to the ACT is out of range in lower direction.

The temperature is below: • NB-441/NB-881/NB-861: -8 °C (17.6 °F) • NB-440/NB-880/RS-880/RSSU-380: -8 °C (17.6 °F) • NB-420/NB-860: -8 °C (17.6 °F) • NB-341/RS-381: -10 °C (14 °F)

This error message occurs also, if there is a short-circuit in the sensor or in the wires between sensor and ACT.

86.3 Troubleshooting (LMT)Even the Node Bs own power dissipation is not sufficient to keep the rack/shelter internal temperature above the lowest operating limit.

• For indoor Node Bs:Rooms with electronic equipment are usually temperature controlled by radiators and/or air condition systems:– Check radiator for sufficient heating.– Check windows, doors etc. for perfect closing (infiltration).

• For outdoor Node Bs:– Are heater units installed for keeping the shelter internal temperature above -

5 °C (23 °F) under worst environmental conditions?– Do the heater units work? Check the power supply, proper connection, and

ohmic resistance.– Replace the heater units if identified as defective. Replacement must be done

according to the “Replacing Node B Units” manual, “Tasklist”. • Check the temperature sensor and the wires to the ACT for a short-circuit if none of

the above reasons were identified.




Probable Cause: LowTemperature

Severity: minor


133

Troubleshooting Node B 200999 - Unexpected loss of unlocked LRU

Id:0900d8058022b5ebConfidential

87 200999 - Unexpected loss of unlocked LRU


87.2 Error DescriptionThe mentioned LRU was unmounted without being locked before. The unexpected loss of an unlocked LRU can be caused by one of the following: • Extracting the reporting LRU or disconnecting the cable at the DRIF (CPRI) to the

reporting internal or external module (such as CATs or RRHs, respectively) without setting the administrative state (AST) to locked before

• Occurrance of a fatal LRU failure • Self-disabling of the reporting LRU due to an overtemperature scenario

As a consequence of this scenario, cells or calls could potentially be lost. The states of all affected managed objects thus change accordingly.The Node B handles self-disabled LRUs as if a fatal LRU failure, such as an on-board power supply failure, has occurred. In other words, the combination of OST/AVS changes to disabled/not installed and the LED of the self-disabled LRU is off.g NOTE

If the reporting Node B is of type NB-441/NB-881/NB-861, the self-disabling of the reporting card may be caused by a polluted membrane filter (MEF). There-fore, if the Node B site is located in heavily air-polluted environments combined with special temperature conditions, a maintenance of the MEF filters in the outdoor NB-441/NB-881/NB-861 might be necessary.If the MEFs are polluted, the 201029 - MEF blocked or 201035 - MEF completely blocked alarm is output. Refer to the relevant alarm’s error description and follow the troubleshooting.

If this fatal board failure occurs, even a CAN communication is not possible anymore.

87.3 Troubleshooting (LMT)Depending on the current situation due to which this fault occurred, perform one of the following procedures to cease this alarm: • If this alarm occurs in combination with the “200914 – Fan unit failed” alarm and/or

the “200996 – Critical Temperature Limit (Ht4) reached” alarm, the probability is very high that the reporting LRU disabled itself due to an overtemperature scenario.Further repair actions must be done according to the “Replacing Node B Units” instructions.

• If the LRU was plugged out by mistake, just install the LRU again.


*



Severity: critical

134 DN70580522Issue 01A


Id:0900d8058022b5ebConfidential

200999 - Unexpected loss of unlocked LRU

• If the cable at the CPRI interface (between DRIC and CAT/RRH/DRX) was discon-nected by mistake, connect the cable again.

• If the card is not to be used anymore, perform a lock and unlock operation, using the TREE View window of the LMT.g NOTE

If an LPA, a DUAMCO, a TRX, a CAT, or a RRH has to be locked and unlocked, apply the following procedure:1. Deactivate the related WCDMA cell, using the RNC’s element manager or

NetAct.2. Lock the LPA, DUAMCO, TRX, CAT, or RRH.

Use the TREE View window and, depending on the reporting hardware type, apply the following command:– Lpa “Set administrativeState Locked”– Duamco “Set administrativeState Locked”– Trx “Set administrativeState Locked”– Cat “Set administrativeState Locked”– Rrh “Set administrativeState Locked”

3. Unlock the LPA, DUAMCO, TRX, CAT, or RRH.Use the TREE View window and, depending on the reporting HW type, apply the following command:– Lpa “Set administrativeState Unlocked”– Duamco “Set administrativeState Unlocked”– Trx “Set administrativeState Unlocked”– Cat “Set administrativeState Unlocked”– Rrh “Set administrativeState Unlocked”

4. Activate the related WCDMA cell, using the RNC’s element manager or NetAct.

• If the LRU is still plugged in, a board failure occurred and the addressed LRU has to be replaced. Replacement must be done according to the “Replacing Node B Units” instructions.





135

Troubleshooting Node B 201001 - RET power off


88 201001 - RET power off


88.2 Error DescriptionThe addressed RET module is switched off at the POWER ON/OFF switch, but not defective. This mode is indicated by the RET LED which is off. Most likely, this alarm is raised during normal Node B operation if the DIP switch 6 of the corresponding DIP switch group is set to OFF position by accident.

Please switch on the RET module.

This alarm will only be output if the power status of the RET module has changed from ON to OFF during operation. However, if the RET module is already switched off at boot time of the Node B, this alarm will not be raised.

• If the RET is supplied by a DUAMCO:For RET recovery, a reset of the related DUAMCO is required in order to re-estab-lish the communication between DUAMCO and RET. A reset of the RET managed object is not possible while this failure exists.

• If the RET is supplied by a DRX:For RET recovery, a reset of the RET itself is sufficient to re-establish the commu-nication.

For RET recovery, a reset of the related DUAMCO is required in order to re-establish the communication between DUAMCO and RET. A reset of the RET managed object is not possible while this failure exists.


If the DIP switch 6 was set to the OFF position by accident, perform the following steps in the given order:1. Confirm that the power is supplied to the relevant RET module from DUAMCO or

DRX. Check the cables, and switch the POWER ON/OFF DIP switch 6 in position ON.


Ret


Probable Cause: ExternalPowerSupplyFailure

Severity: minor




136 DN70580522Issue 01A



201001 - RET power off

2. The further proceeding depends on whether the RET is supplied by a DUAMCO or a DRX:– If the RET is supplied by a DUAMCO, reset the relevant DUAMCO managed

object. Use the TREE View window of the LMT and apply the Duamco “reset” command to the relevant managed object.

– If the RET is supplied by a DRX, reset the reporting RET. Use the TREE View window of the LMT and apply the Ret “reset” command to the relevant managed object.


137

Troubleshooting Node B 201002 - RET feeder alarm


89 201002 - RET feeder alarm


89.2 Error DescriptionRET operations of the reporting module are not possible because the 2.176 MHz carrier between the DUAMCO and DTMARET or the cable between DTMARET and RET is defective.

In correct configurations of the Node B (according to installation and configuration guidelines), this alarm should not occur at all. This alarm is designed for possible appli-cations in the future when no TMA will be used. If the carrier is defective in the current configuration, the alarms 200910 - TMA feeder alarm and 201004 - RET communication error are output.

However, the RET feeder alarm may be caused by a wrong configuration of the Node B: whenever a DTMARET (supporting RET) and a DUAMCORT (without RET support) are installed in the same Node B, this alarm is output. As a consequence of the wrong con-figuration, the 200910 – TMA feeder alarm may also be output.

For RET recovery a reset of the related DUAMCO is required in order to re-establish the communication between DUAMCO and RET. A reset of the RET managed object is not possible while this failure exists.


In order to solve this error, perform the following steps in the given order:1. Confirm that the cables between RET and DUAMCO are connected properly.2. Reset the relevant DUAMCO.

Use the TREE View window of the LMT and apply the Duamco “reset” command to the respective managed object.

3. If the above actins could not clear this alarm, check whether the 200910 – TMA feeder alarm is also output. This may be a strong indicator for a wrong configuration


Ret



Severity: minor




138 DN70580522Issue 01A



201002 - RET feeder alarm

of the Node B, i.e. installation of a DTMARET (supporting RET) and a DUAMCORT (without RET support).To solve this error, replace the DUAMCORT with a DUAMCORET (supporting RET). Replacement must be done according to the “Replacing Node B Units” instructions.

4. If the alarm has not ceased yet, the defective RET module must be replaced. Since both the RET module and the antenna are OEM products, replacement must be done according to the OEM vendor’s description.


139

Troubleshooting Node B 201003 - RET hardware alarm

Id:0900d8058022b5ffConfidential

90 201003 - RET hardware alarm


90.2 Error DescriptionThe addressed RET module reported a hardware error, such as a motor jam or an EPROM error.


Perform the following steps in the given order to solve this error:1. Replace the defective RET module. Since both the RET module and the antenna are

OEM products, replacement must be done according to the OEM vendor’s descrip-tion.



Ret



Severity: minor




140 DN70580522Issue 01A



201004 - ALD communication error

91 201004 - ALD communication error


91.2 Error DescriptionThe addressed antenna line device (ALD), i.e. RET or TMA module, reported a commu-nication error, such as a signaling interrupt. This alarm may be caused by one of the fol-lowing:

• An error occurred on the serial communication line (RS485) between RET/TMA and its controlling device (DUAMCO, RRH, or DRX).

• The cable toward the RET/TMA module is defective. • The communication to the RET/TMA module could not be established. • This alarm is output at the RET as a consequence of 200910 - TMA feeder alarm,

occurring whenever the 2.176 MHz carrier between DUAMCO and DTMARET or the cable between DTMARET and RET is defective.

• The reporting RET or TMA is supplied by a DUAMCO:For RET/TMA recovery, a reset of the related DUAMCO and the addressed RET/TMA is required in order to re-establish the communication between DUAMCO and RET/TMA. Only resetting the RET/TMA managed object is not possible while this failure exists.

• The reporting RET or TMA is supplied by an RRH or a DRX:For RET/TMA recovery, a reset of the RET itself is sufficient to re-establish the com-munication.


First, check whether alarm 200910 - TMA feeder alarm is output. If this alarm has occurred before, eliminate the cause of the fault. Proceed according to the troubleshoot-ing of 200910 - TMA feeder alarm. This may clear the communication error of the antenna line device (RET or TMA), as well.


Ret, Tma


Probable Cause: CommunicationProtocolError

Severity: minor





141

Troubleshooting Node B 201004 - ALD communication error


If either the TMA feeder alarm did not occur or the measures taken above did not clear this fault, perform the following steps in the given order:1. Confirm that the cables between RET/TMA and its controlling device (DUAMCO,

RRH, or DRX) are connected properly.2. The further proceeding depends on whether or not the reporting RET/TMA is con-

trolled by a DUAMCO:– If the RET/TMA is controlled by a DUAMCO, continue with step (3).– Otherwise, if the RET/TMA is not controlled by a DUAMCO, skip step (3) and

continue with step (4).3. Reset the relevant DUAMCO managed object.

Use the TREE View window of the LMT and apply the Duamco “reset” command to the relevant managed object.

4. Reset the addressed RET/TMA managed object.– For RET: use the TREE View window of the LMT and apply the Ret “reset”

command to the relevant RET managed object.– For TMA: use the TREE View window of the LMT and apply the Tma “reset”

command to the relevant TMA managed object.5. If the alarm is still active, replace the defective RET/TMA module.

– RET replacement: Since both the RET module and the antenna are OEM prod-ucts, replacement must be done according to the OEM vendor’s description.

– TMA replacement: Replacement must be done according to the “Replacing Node B Units” instructions.


142 DN70580522Issue 01A



201005 - RET is not calibrated

92 201005 - RET is not calibrated


92.2 Error DescriptionThe reporting RET module is disabled because it is not calibrated. Both the RET module and the antenna have to be calibrated after installation. The stepper motor drives to the end position.

To solve this error, the addressed RET module has to be calibrated.


Perform the following tasks in the order described to solve this error:1. Check the antenna for mechanical problems.

Since antennas are OEM products, proceed according to the OEM vendor’s descrip-tion.

2. Check the mechanical calibration of the antenna and, if necessary, calibrate the antenna again.As antennas are OEM products, proceed according to the OEM vendor’s descrip-tion.

3. If the alarm condition had not been caused by the antenna, calibrate the relevant RET moduleUse the TREE View window of the LMT and apply the Ret “calibrate” action command to the reporting managed object.



Ret


Probable Cause: ExternalIFDeviceProblem

Severity: minor

!DANGER! Emission of microwave radiation.

Damage to health may occur because the electromagnetic field (EMF) generated by a Node B may have detrimental effects on human health. This danger arises especially – but not exclusively! – in areas very close to the Node B antenna, where EMF levels can be high enough to cause human tissue heating.

To avoid the danger of uncontrolled emission of microwave radiation, switch off the breakers for the related amplifiers before checking antenna cables, antennas, or RETs on site. Furthermore, keep the required distance to the antenna system as described in the antenna documentation.


143

Troubleshooting Node B 201006 - RET is not scaled


93 201006 - RET is not scaled


93.2 Error DescriptionThe reporting RET module is disabled because it is not scaled. In other words, the trans-lation table has not been downloaded to the relevant RET module.

The spindle scale table of the relevant RET module must be re-programmed.

93.3 Troubleshooting (LMT)1. Upload the relevant configuration data.

As a precondition, the relevant RET module must be accessible to connect the RS485 interface.To upload (and update) the RET configuration data, use the TREE View window of the LMT and apply the Ret “updateTable” command to the reporting managed object.g Please note that the “201005 – RET is not calibrated” alarm is usually output

after having finished this step!2. Contact the technical assistance center (TAC) to get support in isolating the fault.



Ret



Severity: minor

144 DN70580522Issue 01A



201007 - RET lost position

94 201007 - RET lost position


94.2 Error DescriptionThe reporting RET module lost position of the stepper motor and is therefore disabled. The relevant RET module must be calibrated again.

This alarm may occur if the power supply was interrupted while adjusting the antenna tilt.

94.3 Troubleshooting (LMT)Perform the following steps in the given order to solve this error:1. First, calibrate the relevant RET module

Use the TREE View window of the LMT and apply the Ret “calibrate” action command to the reporting managed object.

2. Set the tilt value of the reporting RET moduleUse the TREE View window of the LMT and apply the Ret “setTilt” action command to this Ret managed object.



Ret



Severity: minor


145

Troubleshooting Node B 201008 - RET received wrong configuration data


95 201008 - RET received wrong configuration data


95.2 Error DescriptionThe addressed RET module received wrong configuration data and is therefore dis-abled.

Setting the appropriate configuration data may be required after installation of any RET module unless this task has already been performed by the vendor before delivery. It loads vendor and antenna specific configuration data to establish the relationship between the movement of the drive system and the beam position of the antenna.


In order to solve this error, perform the following steps in the given order:1. Check whether the correct configuration data (antenna type and antenna OEM

vendor) is used.– If the configuration data is OK, go to step (2).– Otherwise, if the configuration data is NG, the correct configuration data must be

uploaded using the LMT. To upload and update the RET configuration data, use the TREE View window of the LMT or, alternatively, apply the Ret “updateTable” command to the reporting RET.

2. Confirm that the cables between the RET and DUAMCO modules are connected properly.

3. If the alarm is still active, replace the defective RET module. Since both the RET module and the antenna are OEM products, replacement must be done according to the OEM vendor’s description.

4. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be


Ret



Severity: minor




146 DN70580522Issue 01A



201008 - RET received wrong configuration data

analyzed and specific measures must be taken which are out of the operator’s scope.


147

Troubleshooting Node B 201009 - A mounted card is not used to its full capacity


96 201009 - A mounted card is not used to its full capacity


96.2 Error DescriptionThe Node B's configuration does not use the mounted card's full capacity and/or fea-tures. This could be an unwanted waste of resources.

96.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. Check the hardware compatibility of the configuration.2. Replace the incompatible card.


3. If the error has not ceased yet, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*


Probable Cause: ConfigurationOrCustomizationError

Severity: warning

148 DN70580522Issue 01A



201010 - An incompatible card is mounted

97 201010 - An incompatible card is mounted


97.2 Error DescriptionThe mounted card does not fulfill the Node B's configuration requirements.

97.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. Check the hardware compatibility of the configuration.2. Replace the incompatible card.




*



Severity: major


149

Troubleshooting Node B 201011 - Alignment of standby CC failed


98 201011 - Alignment of standby CC failed


98.2 Error DescriptionThe alignment of the standby CC failed. The error should be reported to customer ser-vices. It is possible that a hardware or software error is the root of the problem.

98.3 Troubleshooting (LMT)Take the following steps to solve this error:1. First, reset the relevant card. Use the TREE View window of the LMT or, alterna-

tively, apply the Cc “reset” command to the addressed card.2. If the manual reset did not clear the fault, contact the technical assistance center

(TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


Cc




150 DN70580522Issue 01A



201012 - Timeout for connection to standby CC

99 201012 - Timeout for connection to standby CC


99.2 Error DescriptionAn expected message from the standby CC did not come in time. The error should be reported to customer services. It is possible that a hardware or software error is the root of the problem.

99.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. Reset the relevant card. Use the TREE View window of the LMT or, alternatively,

apply the Cc “reset” command to the addressed card.2. If the manual reset did not clear the fault, contact the technical assistance center



Cc



Severity: major


151

Troubleshooting Node B 201013 - Connection failure to standby CC


100 201013 - Connection failure to standby CC


100.2 Error DescriptionAn attempt to connect to the standby CC failed. The error should be reported to customer services. It is possible that a hardware or software error is the root of the problem.

100.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. Reset the addressed standby CC. Use the TREE View window of the LMT or, alter-

natively, apply the Cc “reset” command to the addressed card.2. Confirm that the relevant standby CC card is properly plugged into its slot.3. If the manual reset did not clear the fault, contact the technical assistance center



Cc



Severity: major

152 DN70580522Issue 01A



201014 - Standby CC forced to become active due to unreachable active CC

101 201014 - Standby CC forced to become active due to unreachable active CC


101.2 Error DescriptionThe former standby CC was not able to connect with the expected active CC and now became active. Please note that this CC became active due to a recovery action and might not contain the expected configuration. The other CC was not able to become active, thus it should be replaced.

101.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. Replace that CC which is in standby mode now and used to be active before.

Replacement must be done according to the “Replacing Node B Units” instructions.2. Confirm that the Node B is configured properly. Check the Node B’s versions of

database and SW load.Use the TREE View window of the LMT or apply the Osu “validateFile” command to the relevant Osu object.

3. Perform a switch-over of the standby CC. This CC will then become active.Take the following steps in the order provided:– Reset the standby CC, using the TREE View window of the LMT or, alterna-

tively, applying the Cc “reset” command to the standby CC.– Perform the actual switch-over. Use the TREE View window or apply the Cc

“redundancySwitch” command to the CC reset before.4. If the measures taken above did not clear the fault, contact the technical assistance



Cc



Severity: warning


153

Troubleshooting Node B 201015 - Preparation of data to be aligned has failed


102 201015 - Preparation of data to be aligned has failed


102.2 Error DescriptionData which has to be aligned could not be prepared. As a consequence, the standby CC will not be aligned correctly. The error should be reported to customer services. It is possible that a hardware or software error is the root of the problem.



Cc



Severity: warning

154 DN70580522Issue 01A



201016 - Non-fatal internal LVDS failure

103 201016 - Non-fatal internal LVDS failure


103.2 Error DescriptionA non-fatal hardware error has occurred (internal LVDS failure) in the reporting DRIC. The state of the card is changed accordingly (AVS is degraded). If the card is providing service (SBS is Providing Service), parts of the service could be lost and some of the cells get disabled.

The card is still working partly but should be replaced. If a redundant card is installed which is enabled, an operator-triggered switchover can be initiated from LMT.

103.3 Troubleshooting (LMT)1. If a redundant card is installed, perform a switch-over to this card. Afterwards, this

card will be active.To trigger a switch-over from the active to a redundant card installed, set the admin-istrative state of the reporting DRIC to shuttingDown. Use the TREE View window of the LMT or, alternatively, apply the Dric “Set administrativeState ShuttingDown” command to it.g NOTE

A switch-over to a redundant DRIC can only be triggered by setting the active DRIC’s AVS to shuttingDown. Setting the AVS to locked is not sufficient.Applying the Dric “Set administrativeState ShuttingDown” command is further-more only allowed if no cells would go down due to this operation.

2. Replace the defective card which used to be active before. Replacement must be done according to the “Replacing Node B Units” instructions.g NOTE

Replacing the formerly active card will lead to a scenario in which all services will be lost if there is not any redundant card installed.


Dric



Severity: minor


155

Troubleshooting Node B 201017 - Digital input power level too high, but gainreduced


104 201017 - Digital input power level too high, but gain reduced


104.2 Error DescriptionThe CAT/RRH detected a digital input power level from the DRIC that has continuously been too high. In fact, the digital input power level has been more than 5 dB above the maximum output power of the CAT/RRH for more than 60 seconds.

A root cause for the occurrence of the “201017 – Digital input power level too high, but gain reduced” alarm may be the following: the congestion control parameters for the related cell are not configured sufficiently in the RNC’s database.

For more information about setting up congestion control in a specific cell, please refer to the WCDMA RAN Parameter Dictionary and the Admission Control radio resource management functional area description.

104.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. Confirm that all relevant cables are connected properly.

2. Check the setting of the following parameters related to congestion control in the RNC database. The relevant parameters for the related cell of this Node B must be set to the following values:– Downlink congestion threshold < 90%– Downlink congestion hysteresis > 15%– Number of bearers that are switched/dropped in each step: more than one (1)– Bearer dropping has to be enabled

3. If the fault could not be cleared, the addressed card must be replaced. Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.


Cat, Rrh



Severity: minor




156 DN70580522Issue 01A



201018 - The LRU could not process a message from CC

105 201018 - The LRU could not process a message from CC


105.2 Error DescriptionA fatal software error has occurred: the addressed LRU indicates a messaging failure towards the CC.



105.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. Check the hardware compatibility of the configuration.

If necessary, replace the relevant card. Replacement must be done according to the “Replacing Node B Units” instructions.

2. Reset the relevant card or external module.Use the TREE View window of the LMT and apply the respective command, depending on the reporting managed object:CAT Cat “reset”CC Cc “reset”CHC Ch “reset”DRIC Dric “reset”DRX Drx “reset”REP Rep “reset”RET Ret “reset”RRH Rrh “reset”TMA Tma “reset”TRX Trx “reset”



Cc, Ch, Rep, Trx, Tma, Dric, Cat, Ret, Rrh, Drx





157

Troubleshooting Node B 201019 - Gain below threshold


106 201019 - Gain below threshold


106.2 Error DescriptionThe gain of the CAT/RRH falls below a certain threshold. The output power has been 3dB below the expected output power calculated from the digital input signal for more than a specified period of time.

As a consequence, the reporting CAT/RRH was put out of service. Cells or calls could potentially be lost. The states of all affected managed objects change accordingly.



Cat, Rrh


Probable Cause: SignalQualityEvaluationFault

Severity: major

158 DN70580522Issue 01A



201020 - Loss of single DRIF interface detected

107 201020 - Loss of single DRIF interface detected


107.2 Error DescriptionThe communiation to a specific CAT/RRH module over one CPRI-compliant DRIF inter-face was lost, whereas a second DRIF interface to this CAT/RRH exits and is still working.

The single DRIF loss may be caused by a missing cable connection, by hardware problems on the CAT/RRH-DRIF-interface side as well as on the DRIC side.

As a consequence, cells or calls could potentially be lost if the lost DRIF carried user plane data. Furthermore, the states of all affected managed objects change accordingly.


2. If the fault could not be cleared, replace the defective card. Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.


Dric



Severity: minor





159

Troubleshooting Node B 201022 - Alignment of file data has failed


108 201022 - Alignment of file data has failed


108.2 Error DescriptionAlignment of file data from the active to the standby CC failed.

The data to be aligned is not indispensable for redundancy in general. For example logging-, or PM-data can be affected.

The error should be reported to customer services. It is possible that a hardware or software error is the root of the problem.



Cc



Severity: minor, handled according to the Fault Escalation Strategy

160 DN70580522Issue 01A



201023 - Bad signal quality of single DRIF interface detected

109 201023 - Bad signal quality of single DRIF interface detected


109.2 Error DescriptionThe addressed CAT/RRH module detected that the signal quality on one DRIF will not ensure a reliable data transmission.

The following cases are possible: • Case 1: The DRIF to DRIC-N is affected and a second working DRIF connection to

DRIC-E exists. Therefore, CAT/RRH connects to DRIC-E. However, in this case cells and calls could potentially be lost.

• Case 2: The DRIF to DRIC-E is affected. This case has no direct impact for cells and calls until a switch over to DRIC-E occurs.

This alarm message may occur in conjunction with 201020 - Loss of single DRIF inter-face detected on DRIC-N.

The failure can be caused by one of the following:

• Failure to receive an expected response to a CORBA request within specified time limits.

• Indications of a connection failure from the communication stack, for example pointto-point protocol (PPP), internet protocol (IP), high level data link control protocol (HDLC), etc.


2. If the fault could not be cleared, replace the defective card/external module.Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.


Cat, Rrh



Severity: minor





161

Troubleshooting Node B 201023 - Bad signal quality of single DRIF interfacedetected


3. If the replacement of the card/external module could not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

162 DN70580522Issue 01A



201024 - Bad signal quality of all DRIF interfaces de-tected

110 201024 - Bad signal quality of all DRIF inter-faces detected


110.2 Error DescriptionThe addressed CAT/RRH/DRX module detected that the signal quality on all DRIF will not ensure a reliable data transmission. After an unsuccessful automatic recovery (card reset), the CAT/RRH/DRX was put out of service. The states of the CAT/RRH/DRX (operational state, availability status, and alarm status) changed accordingly.


The failure can be caused by one of the following: • Failure to receive an expected response to a CORBA request within specified time

limits • Indications of a connection failure from the communication stack, for example

pointto-point protocol (PPP), internet protocol (IP), high level data link control protocol (HDLC), etc.


2. If the fault could not be cleared, replace the defective card/external module.Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.

3. If the replacement of the card/external module could not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”.


Cat, Rrh, Drx








163

Troubleshooting Node B 201024 - Bad signal quality of all DRIF interfaces de-tected


Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

164 DN70580522Issue 01A



201025 - PID could not be read or is corrupted

111 201025 - PID could not be read or is corrupted


111.2 Error DescriptionA hardware error has occurred! The PID of the addressed LRU could not be read or is corrupted. Basic operation of the affected LRU is not possible.

The information contained in the PID is essential for the operation of the LRU. Therefore, the reporting LRU will fail.


Report this error to customer service. The PID of the failed LRU has to be updated.

111.3 Troubleshooting (LMT)Carrying out the following measures will help to solve this error:1. Replace the addressed card. Replacement must be done according to the “Replac-

ing Node B Units” manual, “Tasklist”.However, if OEM parts are affected, proceed according to the OEM vendor’s description.

2. If the replacement of the card could not clear the fault, contact the technical assis-tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*





165

Troubleshooting Node B 201026 - LRU sent illegal parameter


112 201026 - LRU sent illegal parameter


112.2 Error DescriptionThe following fatal software error has occurred: the addressed LRU sent an illegal parameter.

After an unsuccessful automatic recovery by means of a reset, the reporting LRU was put of of service.

As a result of this failure, cells or calls could potentially be lost. Furthermore, the states of all affected managed objects change accordingly.

As a matter of principle, this error should always be reported to customer service.

Manual recovery can be applied by an operator-triggered reset of the addressed card from the LMT.

112.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. Reset the addressed card.2. If the manual reset has not helped to cease the alarm, check the hardware compat-

ibility of the configuration.3. If the measures taken above have not been successful, contact the technical assis-

tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*




166 DN70580522Issue 01A



201027 - LRU could not process a message from CC containing data from DB

113 201027 - LRU could not process a message from CC containing data from DB


113.2 Error DescriptionA fatal error has occurred: the reporting LRU could not process a message from the core controller (CC) containing data from the Node B’s database (DB).

This alarm may be caused by one of the following: • Wrong database • A database attribute which has been changed via Itf-B from the LMT.

As a consequence of this failure, service may be affected.

The database should be verified. Manual recovery could be applied by an operator-trig-gered reset of the reporting object from the LMT.

113.3 Troubleshooting (LMT)The following measures must be taken in the given order to solve this error:

1 Reset the reporting card by means of the following procedure:

1. Lock the card/module.Use the TREE View window of the LMT and apply the respective command, depending on the reporting managed object:CAT Cat “Set administrativeState Locked”CHC Ch “Set administrativeState Locked”DRIC Dric “Set administrativeState Locked”DRX Drx “Set administrativeState Locked”REP Rep “Set administrativeState Locked”RRH Rrh “Set administrativeState Locked”TRX Trx “Set administrativeState Locked”

2. Reset the relevant card or external module.Use the TREE View window of the LMT and apply the respective command, depending on the reporting managed object:CAT Cat “reset”CHC Ch “reset”DRIC Dric “reset”DRX Drx “reset”REP Rep “reset”RRH Rrh “reset”





Severity: major


167

Troubleshooting Node B 201027 - LRU could not process a message from CCcontaining data from DB


TRX Trx “reset”

2 If the manual reset did not help to solve this error, check the Node B’s database. The DB check must be performed according to the OGL:Node B DB Editing Guide.

3 Change the Node B’s DB. The DB change must be performed according to the OGL:Node B DB Editing Guide.

4 If the measures taken above have not been successful, contact the technical assis-tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in ’Collect Info for Assistance’. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

168 DN70580522Issue 01A



201028 - Node B system clock hardware failure

114 201028 - Node B system clock hardware failure


114.2 Error DescriptionThis error is caused by a fatal HW failure of the active core controller’s (CC) clock pro-cessing unit. This failure may lead to impacts on the air interface’s synchronization.

If the clock processing failure occurs simultaneously with the 202506 - Node B system clock in holdover mode alarm, stable Node B operation may not be possible any longer.

As a consequence, cells or calls could be lost. The states (operational state and avail-ability status) of all affected managed objects change accordingly.

The card should be replaced. Furthermore, manual recovery could be applied by an operator-triggered reset of the CC from the LMT. If a standby CC is installed, a switch over to this CC can be initiated, too.

114.3 Troubleshooting (LMT)Perform the following steps in the given order to solve this alarm:1. Reset the defective core controller.

Use the TREE View window of the LMT and apply the Cc “reset” command to the (defective) active core controller (CC) MOI).

2. If a standby CC is installed, perform a switch over from the defective active CC to the standby CC.Use the TREE View window of the LMT and apply the Cc “redundancySwitch” command to the active CC.

3. Replace the defective CC. Replacement must be done according to the “Replacing Node B Units” instructions.


NodeBFddE



Severity: major


169

Troubleshooting Node B 201029 - MEF blocked


115 201029 - MEF blocked


115.2 Error DescriptionThe membrane filter (MEF) is polluted. Therefore, the MEF’s lifetime will run out.

The 200920 - High temperature of PA alarm has been output before. This alarm indi-cates a high temperature scenario in at least one PA installed in the Node B.

The MEF has to be exchanged within the next 2 weeks.

A further increase of the MEF’s pollution may lead to a severe defect. A heavily-polluted MEF can cause the following alarms: • 200921 - Over temperature of PA • 200986 - Temperature out of range in upper direction • 200995 - High Temperature Limit (Ht3) reached • 200996 - Critical Temperature Limit (Ht4) reached • 201035 - MEF completely blocked

115.3 Troubleshooting (LMT)Replace the MEF during the next two (2) weeks after occurrence of this alarm. Replace-ment must be done according to the “Replacing Node B Units”, manual, “Tasklist”.

Replacing the MEF will assure a sufficient air flow and therefore cooling of the Node B.


BaseRack



Severity: minor

170 DN70580522Issue 01A


Id:0900d8058022b6afConfidential

201030 - Invalid hardware capacity licensing value

116 201030 - Invalid hardware capacity licensing value


116.2 Error DescriptionThe hardware capacity licensing value read from the reporting card is invalid.

116.3 Troubleshooting (LMT)Perform the following steps in the given order to solve this error:1. Replace the reporting card by a licensed card. Replacement must be done accord-

ing to the “Replacing Node B Units” manual, “Tasklist”.2. If the replacement of the card could not clear the fault, contact the technical assis-

tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


Cat, Cc, Ch, Dric



Severity: warning


171

Troubleshooting Node B 201031 - Wrong combination of licensed cards


117 201031 - Wrong combination of licensed cards


117.2 Error DescriptionThe combination of hardware capacity licensing values is invalid. This error might be caused by using more cards that carry a restricted license than supported by the licens-ing terms and conditions.

117.3 Troubleshooting (LMT)Perform the following steps in the given order to solve this error:1. Check the hardware compatibility of the configuration.2. If the first step could not clear the fault, contact the technical assistance center



NodeBFddE



Severity: minor

172 DN70580522Issue 01A



201032 - Not all cells are licensed

118 201032 - Not all cells are licensed


118.2 Error DescriptionThe contracted hardware capacity licenses for UTRAN cells do not cover all cells con-figured in the Node B’s database. Those cells which are not licensed remain disabled after Node B’s start-up.

118.3 Troubleshooting (LMT)Carrying out the following steps in the given order will help to solve this alarm:1. Check the compatibility of the current configuration.2. Check the Node B’s database (DB), using the mibCheck or mibCheckWin tool deliv-

ered with the Node B’s software. The DB check must be performed according to the “Node B Database Editing Guide”.

3. Change the Node B’s DB in such a way that only the licensed number of UTRAN cells is configured. The DB change must be performed according to the “Node B Database Editing Guide”.


NodeBFddE



Severity: minor


173

Troubleshooting Node B 201033 - PID could not be read or is corrupted - non-fatal


119 201033 - PID could not be read or is corrupted - non-fatal


119.2 Error DescriptionA hardware error has occurred! The PID of the addressed LRU could not be read or is corrupted. Basic operation of the affected LRU is possible without the information con-tained in the PID.

Service is not affected.

Report this error to customer service. The PID of the failed LRU has to be updated.

119.3 Troubleshooting (LMT)Carrying out the following measures will help to solve this error:1. Replace the addressed card.

– Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.

– However, if OEM parts are affected, proceed according to the OEM vendor’s description.

2. If the replacement of the card could not clear the fault, contact the technical assis-tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


*



Severity: minor

174 DN70580522Issue 01A



201034 - Booster’s Fan unit failed

120 201034 - Booster’s Fan unit failed


120.2 Error DescriptionThe fan unit of the reporting booster is defective. This situation leads to a lack of air cir-culation in the affected Node B. A failure of components which are sensitive to heat may exist.

Caused by the insufficient air circulation in the Node B, related temperature alarms may be reported by the addressed booster. The following alarms may therefore occur in con-junction with the ’201034 - Booster’s Fan unit failed’ alarm: • 200920 - High temperature of PA • 200921 - Over temperature of PA


g NOTEThe defective fan unit(s) are recommended to be exchanged within the next 24 hours!

Replace the defective fan unit of the reporting booster within the next 24 hours. Replace-ment must be done according to the “Replacing Node B Units” manual, “Tasklist”.


Booster


Probable Cause: FanFailure

Severity: major

!DANGER: Circulating rotor of the fan module!

Damage to health may occur when fingers are cut.

When pulling out the fan module, the rotor may still rotate for a few seconds. To prevent serious injuries, watch your fingers.


175

Troubleshooting Node B 201035 - MEF completely blocked


121 201035 - MEF completely blocked


121.2 Error DescriptionThe membrane filter (MEF) is heavily polluted. Therefore, the MEF’s lifetime has run out.

The 200921 - Over temperature of PA alarm has been output before. This alarm indi-cates an over temperature scenario in at least one PA installed in the Node B.

Exchange the defective MEF immediately. Otherwise a severe hardware damage can occur.

A defective MEF can cause the following alarms: • 200986 - Temperature out of range in upper direction • 200995 - High Temperature Limit (Ht3) reached • 200996 - Critical Temperature Limit (Ht4) reached

121.3 Troubleshooting (LMT)Take the following measures to clear the fault which cause this alarm:1. Replace the MEF immediately.

Replacement must be done according to the “Replacing Node B Units” instructions.Replacing the defective MEF will assure a sufficient air flow and therefore cooling of the Node B.

2. As the 200921 - Over temperature of PA alarm is a fatal alarm (severity: major), all PAs which report this alarm have to be reset manually via LMT.Use the TREE View window of the LMT and apply the respective reset action com-mand(s) to the reporting PA(s).


BaseRack



Severity: critical

176 DN70580522Issue 01A


Id:0900d8058022b6deConfidential

201036 - RRHs unable to establish communication links with the expected number of PSRs

122 201036 - RRHs unable to establish communi-cation links with the expected number of PSRs


122.2 Error DescriptionRemote radio heads (RRHs) of the reporting Node B cannot establish communication links with the expected number of power supplies for the RRHs (PSRs).

The problem indicated by this alarm may occur in either of the following situations: • After Node B startup, not all configured PSRs managed to establish a communica-

tion link with a connected RRH within a specified period of time.Besides RRH and PSR hardware defects and wrong cable connections, this alarm can occur when the number of PSRs configured in the system is wrong.

• After breakdown of a communication link, a PSR failed to reconnect itself to an RRH within a specified period of time.The breakdown of a communication link may be caused by the following:– RRH or PSR hardware defect– Broken cable connection– Preceding reset of the related RRH

If no communication link between RRH and PSR exists, no PSR alarms can be reported by the Node B.

122.3 Troubleshooting (LMT)Take the following measures to clear the fault cause and, thus, the alarm:1. Confirm that all cables are connected properly.2. Replace the defective PSRs. Replacement must be done according to the “Replac-

ing Node B Units” manual, “Tasklist”.3. If the alarm has not ceased yet, check in the Node B’s database whether the number

of PSRs configured in the system is wrong.– Check the Node B database. Use the mibCheck or mibCheckWin tool delivered

with the Node B’s software. Proceed according to the “Node B Database Editing Guide”.

– If necessary, change the running database. Edit the database according to the “Node B Database Editing Guide”.


NodeBFddE



Severity: minor


177

Troubleshooting Node B 201037 - ALD unspecified error


123 201037 - ALD unspecified error


123.2 Error DescriptionAn unspecified error occurred in the reporting antenna line device (ALD), i.e. RET module or TMA. Due to this error, the addressed antenna line device is disabled.


Perform the following steps in the given order to solve this error:1. Replace the defective antenna line device:

– RET replacement: Since both the RET module and the antenna are OEM prod-ucts, replacement must be done according to the OEM vendor’s description.

– TMA replacement: Replacement must be done according to the “Replacing Node B Units” manual, “Tasklist”.



Ret, Tma



Severity: minor (final), handled according to the Fault Escalation Strategy




178 DN70580522Issue 01A


Id:0900d8058022b6eaConfidential

201038 - Resource conflict between CP and OAM

124 201038 - Resource conflict between CP and OAM


124.2 Error DescriptionThe CP rejected a request of the RNC, such as a radio link setup request, because the necessary resources are currently allocated by OAM, for instance channels for orthog-onal channel noise simulator (OCNS). These resources may be channelization codes or code trees occupied by DLLG or OCNS, issued by the startModulatedSignalTransmis-sion command.

The required resources have to be freed, releasing the OCNS channels, for example, before the RNC’s request can be processed.

This alarm is cleared as soon as all DLLG and OCNS channels are stopped on the affected cell.

124.3 Troubleshooting (LMT)To solve this problem, free the occupied resources of the reporting cell (LocalCellE MOI) by completely stopping the DLLG or OCNS channels. Use the TREE View window of the LMT and apply the endModulatedSignalTransmission action command to the LocalCellE object the occupied resources are assigned to.

This will clear the alarm and free the resources allocated by OAM. RNC requests can now be serviced again.

To avoid such collisions in the future, an adjustment of the channelization codes used for OCNS may be necessary.


LocalCellE


Probable Cause: UnderlyingResourceUnavailable

Severity: minor


179

Troubleshooting Node B 201039 - Inconsistency between hardware license andconfiguration


125 201039 - Inconsistency between hardware license and configuration


125.2 Error DescriptionThe hardware capacity license of the reporting LRU is not consistent with the current configuration. This error may be caused by using an LRU equipped with an insufficient license.

As a result, the addressed LRU is put out of service. Additionally, all cells related to this LRU remain disabled after startup.

125.3 Troubleshooting (LMT)To solve this error, perform the following steps in the order provided:1. Check the hardware compatibility of the Node B.2. Update the addressed LRU’s hardware capacity to the required value.3. If the first steps could not clear the fault, contact the technical assistance center



Cat, Ret, Rrh



Severity: major

180 DN70580522Issue 01A


Id:0900d8058022b6faConfidential

201040 - Wrong cabling of LRU detected

126 201040 - Wrong cabling of LRU detected


126.2 Error DescriptionThe reporting LRU was not cabled correctly according to the installation manual of the Node B. As a result, the addressed LRU has been put out of service. All cells related to this LRU remain disabled.

126.3 Troubleshooting (LMT)Perform the following steps in the order provided to solve this error: • For rack-mounted LRUs:

Check for the LRU’s correct position in the Node B’s rack. • Otherwise, confirm that cables are connected correctly to the addressed LRU. In the

event of wrong cabling, connect the cables correctly to the LRU. Proceed according to the installation manual (IMN) of the relevant Node B.– For NB-440 or NB-880, refer to the Installing NB-440/NB-880.– For NB-441 or NB-881, refer to the Installing NB-441/NB-881.– For NB-420 or NB-860, refer to the Installing NB-420/NB-860.– For NB-861, refer to to the Installing NB-861.– For NB-341, refer to the Installing NB-341.– For Radio Server Slider Unit RSSU-380, refer to the Installing RSSU-380.– For Radio Server RS-381, refer to the Installing RS-381.– For Radio Server RS-880, refer to the Installing RS-880.


Cat, Drx, Rrh



Severity: major


181

Troubleshooting Node B 201041 - Test channels have been lost

Id:0900d8058022b6feConfidential

127 201041 - Test channels have been lost


127.2 Error DescriptionUsing the startModulatedSignalTransmission or staModSTx actions at the LMT or RC, respectively, operators can start tests such as modulated signal transmission (MST), downlink load generation (DLLG), or orthogonal channel noise simulation (OCNS).

This alarm indicates that one or several test channels for MST, DLLG, or OCNS have been lost. The loss of test channels may be caused by one of the following: • Test channels have been lost due to a necessary channel card reconfiguration.The

reconfiguration of the CHC can be caused by a reset of the CHC or by a failure of the CHC which in turn led to a reset.

• The RNC has deleted a cell on which test channels were set up. • A cell on which test channels were set up has been disabled. Among other causes,

disabling the cell may have been caused by the following:– Hardware problem– Shutdown operation by the user– Lock operation by the user

• The RNC sent request to the reporting Node B, such as an NBAP: RADIO LINK SETUP REQUEST message. The RNC thus required resources which had previ-ously been allocated by one or several test channels.

As a consequence of the failure reported by this alarm, all test channels on the affected cell (LocalCellE MOI) have been stopped. Furthermore, this ’201041 - Test channels have been lost’ alarm has to be cleared before any new test channel can be set up again on the reporting cell (LocalCellE MOI).

127.3 Troubleshooting (LMT)To clear this alarm, free the resources occupied by the test channels. Use the TREE View window of the LMT and apply the endModulatedSignalTransmission action command to the LocalCellE object in which the test channels have been configured.

As a consequence, all test channels in the reporting cell (LocalCellE MOI) will be stopped.


LocalCellE


Probable Cause: UnderlyingResourceUnavailable

Severity: minor

182 DN70580522Issue 01A



201042 - Incompatible Firmware

128 201042 - Incompatible Firmware


128.2 Error DescriptionThe mounted card does not fulfill the Node B's configuration requirements. In other words, the reporting card’s firmware (FW) does not fit to one or several features, for example smart cell configuration, operated in this Node B.

128.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. Check the hardware compatibility of the configuration.2. Download a valid firmware to the specified card.

The update of the firmware must be done according to the “Replacing Node B Units” manual, “Tasklist”.



Cat, Duamco, Rrh



Severity: major


183

Troubleshooting Node B 201043 - Missing software image


129 201043 - Missing software image


129.2 Error DescriptionThe ’201043 - Missing software image’ alarm indicates that the mounted card, which reports this alarm, could not start up. The reporting card failed to start up because a software image (SWI) is missing.Due to the missing SWI, the automatic upgrade config-uration procedure either has failed or was not started at all. The upgrade configuration procedure ensures that missing SWIs are downloaded to the Node B and added to the currently running smart software package without resetting the Node B.

129.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. Start the update configuration procedure manually.

Use the TREE View window of the LMT and apply the Osu “updateConfiguration” command to the relevant Osu instance in the reporting Node B.



Cc, Ch, Dric, Rep, Trx



Severity: major

184 DN70580522Issue 01A



201044 - Non fatal configuration failure

130 201044 - Non fatal configuration failure


130.2 Error DescriptionThe addressed DUAMCO does not support a RET module in the current Node B config-uration. This mismatch is caused by one of the following: • If the Node B configuration does not contain a RET module, the DIP switch 6 is set

to ON position by accident. • Otherwise, if a RET module is installed in the Node B configuration and the Node B’s

DB contains a RET MO, the DUAMCO has to be replaced.

130.3 Troubleshooting (LMT)In order to solve this error, perform the following steps in the given order:1. If RET support is not required for the suspected Node B, switch OFF the DIP

switch 6.☞ For information about the DUAMCO’s DIP switches, refer to the “Node B

Cards/Modules Hardware Description”.2. If a RET module is installed and RET support is required for the suspected Node B,

replace the reporting DUAMCO by another type which is capable of supporting the RET module in the given configuration.Replacement of the DUAMCO must be done according to the “Replacing Node B Units” manual, “Tasklist”.



Duamco



Severity: minor


185

Troubleshooting Node B 201045 - Fatal hardware error


131 201045 - Fatal hardware error


131.2 Error DescriptionThis alarm indicates the occurrence of a fatal hardware failure in the reporting Node B. The actual details of the hardware failure are provided in the additional text field of the alarm.

Users at the LMT: To obtain information in the alarm’s additional text field, use the ALARM View window of the LMT:1. Click on the “Alarm View” button or use the shortcut key Ctrl + A .2. Concentrate on the ’Additional Text’ column.

Users at the RC: To obtain information in the alarm’s additional text field, use the Alarm Monitoring application of the Radio Commander:1. Select and open the icon “Alarm Monitoring” in the Application Launcher window

(double left-click).2. Concentrate on the ’Additional Text’ column

If “RAM parity error at the ATM switching hardware” is displayed in the additional text field, the error occurred due to a defective RAM mounted on the reporting core control-ler.

131.3 Troubleshooting (LMT)If this alarm occurred due to the RAM parity error at the ATM switching hardware, replace the defective core controller. Replacement must be done according to the “Replacing Node B Units” instructions.

Perform the following tasks in the given order to solve this error:1. First, reset the addressed card.

Use the TREE View window of the LMT or, alternatively, apply the Cc “reset” command to the addressed card.

2. If the fault cannot be cleared by the reset, replace the addressed card.Replacement must be done according to the “Replacing Node B Units” instructions.

3. If the card replacement has not cleared the fault, either, contact the technical assis-tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in ’Collect Info for Assistance’. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


Cc



Severity: critical

186 DN70580522Issue 01A



201046 - No ATM connection for OAM Autoconfigura-tion

132 201046 - No ATM connection for OAM Auto-configuration


132.2 Error DescriptionWhile executing the Node B OAM auto configuration, the following failure occurred: incorrect configuration of the default or dedicated transport path for VCs (VcTTP managed object) used for O&M and/or FTP (usedByAttribute = “ftpOAndMCommand”).

The Node B has restarted a predefined number of times to solve the misconfiguration before finally raising this alarm. The detailed failure cause has been logged in the Node B’s log file.

132.3 Troubleshooting (LMT)Taking the following steps will help to clear the failure cause which led to this alarm:1. Check for alarms of managed objects on the physical or ATM layer, which are used

for the “ftpOAndMCommand” connection. These alarms may indicate the failure cause.Open the ALARM VIEW window of the LMT by either clicking on the “Alarm View” button or using the shortcut key Ctrl + A .VcTTP alarms in question:– 202072 – Alarm Indication Signal on an ATM VC– 202073 – Remote Defect Indication on an ATM VC– 202074 – SSCOP Failure Indication on an ATM VC used by ALCAP or NBAP– 202077 – ALCAP PVC Out Of Service IndicationVpTTP alarms in question:– 202075 – Alarm Indication Signal on an ATM VP– 202076 – Remote Defect Indication on an ATM VPE1TTP and J1TTP alarms in question:– 202056 – Loss Of Signal on Physical Link– 202057 – Loss Of Frame on Physical Link– 202058 – Loss Of Cell Delineation on Physical Link– 202059 – Alarm Indication Signal on Physical Link– 202060 – Remote Alarm Indication on Physical Link– 202061 – Loss Of MultiFrame Alarm Indication on E1 Physical Link (E1TTP

only)– 202098 – CRC4 not used by FE reported on E1TTP (E1TTP only)


Cc


Probable Cause: ConnectionEstablishmentError

Severity: Major


187

Troubleshooting Node B 201046 - No ATM connection for OAM Autoconfigura-tion


Stm1TP alarms in question:– 202056 – Loss Of Signal on Physical Link– 202057 – Loss Of Frame on Physical Link– 202058 – Loss Of Cell Delineation on Physical Link– 202062 – Line Alarm Indication Signal Indication on STM1 Physical Link– 202063 – Line Remote Defect Indication on STM1 Physical Link– 202064 – Path Loss of Pointer Indication on STM1 Physical Link– 202065 – Path Alarm Indication Signal on STM1 Physical Link– 202066 – Path Remote Defect Indication on STM1 Physical Link– 202068 – Signal Label Mismatch Indication on STM1 Physical Link– 202070 – Signal Degrade Indication on STM1 Physical Link– 202071 – Excessive Bit Error Rate Indication on STM1 Physical Link


188 DN70580522Issue 01A



201047 - Fatal BB software failure

133 201047 - Fatal BB software failure


133.2 Error DescriptionA fatal software failure occurred in the reporting baseband (BB) card.


As a consequence, cells (LocalCellE instances) or calls could potentially be lost. The states of all affected managed objects change accordingly.

133.3 Troubleshooting (LMT)Take the following measures to clear the fault which had led to this alarm:1. Contact the technical assistance center (TAC) to get support in isolating the fault.


2. As a temporary solution, reset the defective baseband (BB) card again.Resetting the defective equipment may possibly put it into operation again.To reset the card, use the TREE View window of the LMT and apply the following action command, depending in the reporting card:CHC Ch “Reset”DRIC Dric “Reset”REP Rep “Reset”TRX Trx “Reset”


Ch, Dric, Rep, Trx





189

Troubleshooting Node B 201048 - Non-fatal BB software failure


134 201048 - Non-fatal BB software failure


134.2 Error DescriptionA non-fatal software failure occurred in the reporting baseband (BB) card. The BB card is still operational, but possibly with reduced performance.

As a consequence of the failure which led to this alarm, the Node B may be degraded in its performance.



Ch, Rep, Trx, Dric



Severity: warning

190 DN70580522Issue 01A



201049 - Non-fatal DSP failure

135 201049 - Non-fatal DSP failure


135.2 Error DescriptionA non-fatal digital signal processor (DSP) failure occurred in the reporting baseband (BB) card. The BB card is still operational, but possibly with reduced performance.

As a consequence of the BB card’s DSP failure, the Node B may be degraded in its per-formance.



Ch, Rep, Trx, Dric



Severity: warning


191

Troubleshooting Node B 201050 - Major hardware failure


136 201050 - Major hardware failure


136.2 Error DescriptionThis alarm is for future use. In the current release, this alarm should not be output at all.



Cc



Severity: major

192 DN70580522Issue 01A



202007 - A scanner could not be initialized

137 202007 - A scanner could not be initialized


137.2 Error DescriptionThe addressed scanner could not be initialized. The additional text will give the reason (e.g. too many scanners, invalid parameters).

Users at the LMT: To obtain information in the alarm’s additional text field, use the ALARM View window of the LMT:1. Click on the “Alarm View” button or use the shortcut key Ctrl + A .2. Concentrate on the ’Additional Text’ column.

Users at the RC: To obtain information in the alarm’s additional text field, use the Alarm Monitoring application of the Radio Commander:1. Select and open the icon “Alarm Monitoring” in the Application Launcher window

(double left-click).2. Concentrate on the ’Additional Text’ column

If the problem is a misconfiguration, the scanner will be created but will be disabled. Lock the scanner, fix the configuration, then unlock to clear the error.

137.3 Troubleshooting (LMT)Take the following measures to clear the alarm cause:1. Lock the reporting scanner type.

Use the TREE View window of the LMT in order to set the administrative state of the relevant scanner to locked.

2. Fix the configuration.3. Set the administrative state of the addressed scanner to unlocked in order to clear

the error.Use the TREE View window of the LMT.


Scanner, ScannerHsxpa, Scanner Tnl



Severity: minor


193

Troubleshooting Node B 202008 - The temporary measurement results couldnot be stored


138 202008 - The temporary measurement results could not be stored


138.2 Error DescriptionThe internal temporary measurement results could not be stored. The reporting scanner will no longer perform any measurements and will be set to disabled. The Node B may need to be reset before measurements can be restarted correctly.

138.3 Troubleshooting (LMT)Reset the Node B. Use the TREE View window of the LMT and apply the NodeBFddE “reset” command to the NodeBFddE managed object.





Severity: minor

194 DN70580522Issue 01A



202009 - Unable to request measurement results

139 202009 - Unable to request measurement results


139.2 Error DescriptionOne or more of the measurement results for the addressed scanner could not be requested. These measurements will be marked as suspect for the current granularity period. The scanner will try to request these measurements again at the end of the next granularity period. If the next request for reports is successful, the fault will automatically be cleared.





Probable Cause: SystemCallUnsuccessful

Severity: minor


195

Troubleshooting Node B 202010 - The ScanCo could not be initialized


140 202010 - The ScanCo could not be initialized


140.2 Error DescriptionA ScanCo could not be created. The additional text will give the reason for the failure. As a consequence, performance measurements will not be started on the relevant Node B.



ScanCo



Severity: minor

196 DN70580522Issue 01A



202011 - The final results files could not be generated

141 202011 - The final results files could not be generated


141.2 Error DescriptionThe temporary measurement results of the reporting ScanCo could not be converted into a final results files.

This failure will have the following impacts: • The upload in progress will be aborted. • Some measurement files will be lost. • A Node B reset may be required before further upload attempts will be successful.

141.3 Troubleshooting (LMT)Reset the associated Node B. Use the TREE View window of the LMT and apply the NodeBFddE “reset” command to the relevant NodeBFddE managed object.


ScanCo



Severity: minor


197

Troubleshooting Node B 202014 - The first sccpchUsageRatio Quality of Servicealarm has occurred


142 202014 - The first sccpchUsageRatio Quality of Service alarm has occurred


142.2 Error DescriptionThe first sccpchUsageRatio threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for sccpchUsageRatio: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202014 - The first sccpchUsageRatio Quality of Service alarm has occurred / 202015 - The second sccp-chUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Fur-thermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.

If many subscribers within one UTRAN cell use their UEs at the same time, a shortage of HW resources in this cell may occur as a consequence and this alarm will be output.

142.3 Troubleshooting (LMT)Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may help to solve the lack of resources without a system crash.

Furthermore, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

As soon as this QoS alarm is ceased, relevant threshold information will be displayed.


LocalCellE


Probable Cause: ThresholdCrossed

Severity: indeterminate

198 DN70580522Issue 01A



202015 - The second sccpchUsageRatio Quality of Service alarm has occurred

143 202015 - The second sccpchUsageRatio Quality of Service alarm has occurred


143.2 Error DescriptionThe second sccpchUsageRatio threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for sccpchUsageRatio: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202014 - The first sccpchUsageRatio Quality of Service alarm has occurred / 202015 - The second sccp-chUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Fur-thermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.






LocalCellE





199

Troubleshooting Node B 202016 - The first prachUsageRatio Quality of Servicealarm has occurred


144 202016 - The first prachUsageRatio Quality of Service alarm has occurred


144.2 Error DescriptionThe first prachUsageRatio threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for prachUsageRatio: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202016 - The first prachUsageRatio Quality of Service alarm has occurred / 202017 - The second pra-chUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Fur-thermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.






LocalCellE




200 DN70580522Issue 01A



202017 - The second prachUsageRatio Quality of Ser-vice alarm has occurred

145 202017 - The second prachUsageRatio Quality of Service alarm has occurred


145.2 Error DescriptionThe second prachUsageRatio threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for prachUsageRatio: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202016 - The first prachUsageRatio Quality of Service alarm has occurred / 202017 - The second pra-chUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Fur-thermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.






LocalCellE





201

Troubleshooting Node B 202018 - The first cpUsageRatio Quality of Servicealarm has occurred


146 202018 - The first cpUsageRatio Quality of Service alarm has occurred


146.2 Error DescriptionThe first cpUsageRatio threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for cpUsageRatio: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202018 - The first cpUsageRatio Quality of Service alarm has occurred / 202019 - The second cpUsageR-atio Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.






NodeBFddE




202 DN70580522Issue 01A



202019 - The second cpUsageRatio Quality of Service alarm has occurred

147 202019 - The second cpUsageRatio Quality of Service alarm has occurred


147.2 Error DescriptionThe second cpUsageRatio threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for cpUsageRatio: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202018 - The first cpUsageRatio Quality of Service alarm has occurred / 202019 - The second cpUsageR-atio Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.






NodeBFddE





203

Troubleshooting Node B 202020 - The first prachCrciFailures Quality of Servicealarm has occurred


148 202020 - The first prachCrciFailures Quality of Service alarm has occurred


148.2 Error DescriptionThe first prachCrciFailures threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for cpUsageRatio: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202020 - The first prachCrciFailures Quality of Service alarm has occurred / 202021 - The second prach-CrciFailures Quality of Service alarm has occurred), respectively, when crossed. Fur-thermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.






LocalCellE




204 DN70580522Issue 01A



202021 - The second prachCrciFailures Quality of Ser-vice alarm has occurred

149 202021 - The second prachCrciFailures Quality of Service alarm has occurred


149.2 Error DescriptionThe second prachCrciFailures threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for cpUsageRatio: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202020 - The first prachCrciFailures Quality of Service alarm has occurred / 202021 - The second prach-CrciFailures Quality of Service alarm has occurred), respectively, when crossed. Fur-thermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.






LocalCellE





205

Troubleshooting Node B 202022 - The first bbUsageRatioLicense Quality of Ser-vice alarm has occurred


150 202022 - The first bbUsageRatioLicense Quality of Service alarm has occurred


150.2 Error DescriptionThe first bbUsageRatioLicense threshold-crossing alarm was raised . This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for bbUsageRatioLicense: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202022 - The first bbUsageRatioLicense Quality of Service alarm has occurred / 202023 - The second bbUsageRatioLicense Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.

If many subscribers within one UTRAN cell use their UEs at the same time, a shortage of the purchased channel element (CE) license resources may occur as a consequence and this alarm will be output.

150.3 Troubleshooting (LMT)Take the following measures to clear this alarm:1. The number of channel element (CE) licenses available is not sufficient.

Purchase additional CE licenses.2. If purchasing additional CE licenses does not help to solve the error reported,

contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assis-tance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.



NodeBFddE




206 DN70580522Issue 01A



202023 - The second bbUsageRatioLicense Quality of Service alarm has occurred

151 202023 - The second bbUsageRatioLicense Quality of Service alarm has occurred


151.2 Error DescriptionThe second bbUsageRatioLicense threshold-crossing alarm was raised . This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for bbUsageRatioLicense: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202022 - The first bbUsageRatioLicense Quality of Service alarm has occurred / 202023 - The second bbUsageRatioLicense Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.

If many subscribers within one UTRAN cell use their UEs at the same time, a shortage of the purchased channel element (CE) license resources may occur as a consequence and this alarm will be output.

151.3 Troubleshooting (LMT)Take the following measures to clear this alarm:1. The number of channel element (CE) licenses, which are available, is not sufficient.

Purchase additional CE licenses.2. If purchasing additional CE licenses does not help to solve the error reported,

contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assis-tance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.



NodeBFddE





207

Troubleshooting Node B 202024 - The first bbUsageRatioHw Quality of Servicealarm has occurred


152 202024 - The first bbUsageRatioHw Quality of Service alarm has occurred


152.2 Error DescriptionThe first bbUsageRatioHw threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for bbUsageRatioHw: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202024 - The first bbUsageRatioHw Quality of Service alarm has occurred / 202025 - The second bbUs-ageRatioHw Quality of Service alarm has occurred), respectively, when crossed. Fur-thermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.

If many subscribers use their UEs at the same time, a shortage of hardware resources in this cell may occur as a consequence and this alarm will be output.

152.3 Troubleshooting (LMT)Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may help to solve the lack of resources without any system crash.




NodeBFddE




208 DN70580522Issue 01A


Id:0900d8058022b7acConfidential

202025 - The second bbUsageRatioHw Quality of Ser-vice alarm has occurred

153 202025 - The second bbUsageRatioHw Quality of Service alarm has occurred


153.2 Error DescriptionThe second bbUsageRatioHw threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any percentage for bbUsageRatioHw: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202024 - The first bbUs-ageRatioHw Quality of Service alarm has occurred / 202025 - The second bbUsageR-atioHw Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.

If many subscribers within one cell use their UEs at the same time, a shortage of hardware resources in this cell may occur as a consequence and this alarm will be output.

153.3 Troubleshooting (LMT)Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may help to solve the lack of resources without any system crash..




NodeBFddE





209

Troubleshooting Node B 202026 - The first e1Crc Quality of Service alarm hasoccurred


154 202026 - The first e1Crc Quality of Service alarm has occurred


154.2 Error DescriptionThe first e1Crc threshold crossing alarm has been raised. This is a QoS alarm which has been raised due to bad signal quality on the reporting E1 line, resulting in high bit error ratios (BERs).

Operators can set four thresholds of any values within the allowed range for e1Crc: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (“202026 – The first e1Crc Quality of Service alarm has occurred” / “202027 – The second e1Crc Quality of Service alarm has occurred”), respectively, when crossed.

If the BER increases, the “202027 – The second e1Crc Quality of Service alarm has occurred” alarm will be output in addition to the “202026 – The first e1Crc Quality of Service alarm has occurred” alarm.

Whenever the “202026 – The first e1Crc Quality of Service alarm has occurred” alarm is output, the consequence for the related E1 line depends on whether or not the “202027 – The second e1Crc Quality of Service alarm has occurred” is output, too. The consequences for the E1 line are provided subsequently.

154.3 Troubleshooting (LMT)Contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in Collect Info for Assis-tance. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

As soon as this QoS alarm is ceased • Relevant threshold information will be displayed


E1TTP



Severity: Indeterminate

Condition of QoS Alarm (ID)… Consequence for the E1 Line Remark

202026 (1st QoS Alarm) 202027 (2nd QoS Alarm) OST AVS RAI

Cleared Cleared enabled empty set cleared

Raised Cleared enabled degraded cleared

Raised Raised disabled failed raised Refer to the “Error Description” of the 2nd QoS Alarm (202027).

210 DN70580522Issue 01A



202026 - The first e1Crc Quality of Service alarm has occurred

• The AVS of the E1 line will be set to empty set.


211

Troubleshooting Node B 202027 - The second e1Crc Quality of Service alarmhas occurred

Id:0900d8058022ac61Confidential

155 202027 - The second e1Crc Quality of Service alarm has occurred


155.2 Error DescriptionThe second e1Crc threshold-crossing alarm has been raised. This is a QoS alarm which has been raised due to bad signal quality on the reporting E1 line, resulting in high bit error ratios (BERs).

Operators can set four thresholds of any values within the allowed range for e1Crc: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (“202026 – The first e1Crc Quality of Service alarm has occurred” / “202027 – The second e1Crc Quality of Service alarm has occurred”), respectively, when crossed.

☞ Whenever the “202027 – The second e1Crc Quality of Service alarm has occurred” alarm is active, the “202026 – The first e1Crc Quality of Service alarm has occurred” is active, too.

As a consequence of this alarm, the reporting managed object (E1TTP) will be set to OST = disabled and AVS = failed, except for E1 lines required by VCs (VcTTP managed object) used for • FTP and OAM • ALCAP • NBAPAdditionally, a remote alarm indication (RAI) signal will be sent to the far end in upstream direction. Depending on the network topology and if the far end (FE) equipment is an NB/RSAxxx, the RAI may be indicated by the following alarm: 202060 – Remote Alarm Indication on Physical Link.

Corresponding alarms may be reported for the RNC, other Node B types, or link equipment (LE).

The E1 line related to the reporting E1TTP object will not be used for traffic anymore until the “202027 – The second e1Crc Quality of Service alarm has occurred” alarm and the subsequent RAI signal are cleared. The exception mentioned before still applies, however.

155.3 Troubleshooting (LMT)Contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assis-


E1TTP



Severity: Indeterminate

212 DN70580522Issue 01A


Id:0900d8058022ac61Confidential

202027 - The second e1Crc Quality of Service alarm has occurred

tance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

As soon as this QoS alarm is ceased, relevant threshold information will be displayed. The consequence for the E1 line depends on whether or not the first e1Crc threshold-crossing QoS alarm is also ceased. For details, consult the “202026 – The first e1Crc Quality of Service alarm has occurred” alarm’s “Error Description”.


213

Troubleshooting Node B 202028 - The first vcUsageRatio Quality of Servicealarm has occurredAlarm added


156 202028 - The first vcUsageRatio Quality of Service alarm has occurredAlarm added


156.2 Error DescriptionThe first vcUsageRatio threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any values for prachCrciFailures: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202028 - The first vcUsag-eRatio Quality of Service alarm has occurred / 202029 - The second vcUsageRatio Quality of Service alarm has occurred),respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.





VcCTP




214 DN70580522Issue 01A



202029 - The second vcUsageRatio Quality of Service alarm has occurred

157 202029 - The second vcUsageRatio Quality of Service alarm has occurred


157.2 Error DescriptionThe second vcUsageRatio threshold-crossing alarm was raised. This is a QoS alarm which was not generated by any HW or SW error.

The operator can set four thresholds of any values for prachCrciFailures: notify high 1/2 and notify low 1/2 which raise and clear the related alarms (202028 - The first vcUsag-eRatio Quality of Service alarm has occurred / 202029 - The second vcUsageRatio Quality of Service alarm has occurred),respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS alarms. All values are related to call-processing resources of the Node B.





VcCTP





215

Troubleshooting Node B 202056 - Loss Of Signal on Physical Link


158 202056 - Loss Of Signal on Physical Link


158.2 Error DescriptionLoss of signal (LOS) indication has been received on a physical link E1, J1, T1 or STM-1/OC-3 (according to reported MOC in the failure event report). This indicates that the signal from the next device upstream is not present. This may be due to misconfig-uration of the hardware at either end, faulty hardware at either end or due to a break in the transmission medium between the two ends.

The loss of signal may be the root cause for alarms indicated by different NEs in the supervision of the RC. If this NE is an NB/RSxxx, the following subsequent alarms may be output: • Downstream direction:

– 202059 - Alarm Indication Signal on Physical Link– 202062 - Line Alarm Indication Signal Indication on STM1 Physical Link

• Upstream direction:– 202060 - Remote Alarm Indication on Physical Link– 202063 - Line Remote Defect Indication on STM1 Physical Link

Additionally, the LOS causes the reporting Node B’s system clock to switch in holdover mode, indicated by the 202506 - Node B system clock in holdover mode alarm.

158.3 Troubleshooting (LMT)Usually the Node B is connected to the RNC or each other (Iub interface) via Link Equip-ment (LE, such as SDH/PDH multiplexers, ATM switches, or repeaters) and in some rare cases by direct lines. If LE is involved the operation and maintenance system of this network has to be used for getting information about the state and status of the relevant network element (NE).

Depending on the applied configuration of the Node Bs such as star, hub, cascade or loop not only the reported Node B of this error message is affected but also subordi-nated Node Bs.

• Star configurationOnly the reported Node B

• Hub configurationIf the hub Node B is the reporting one for a connection to the RNC:– For E1/J1/T1: the supplied Node B of the relevant E1/J1/T1 link will report AIS– For STM-1/OC-3: all supplied Node Bs will report AIS


E1TTP, J1TTP, Stm1TP


Probable Cause: LossOfSignal

Severity: major

216 DN70580522Issue 01A



202056 - Loss Of Signal on Physical Link

• Cascade configurationAll Node Bs in the chain downstream the LOS reporting Node B will initiate a VP AIS error message for the relevant E1/J1/T1 link respectively all if the first Node B is reporting and connected to the RNC via STM-1/OC-3.

• Loop configurationThe redundant path in the loop configuration will take over the traffic

To isolate the fault check for other error messages in the following order:1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B

present?Using the ALARM View window of the LMT:– Click on the “Alarm View” button or use the shortcut key Ctrl + A

– Use the filter and sort function to concentrate on CC alarmsIf an equipment alarm of the CC is present try to fix this fault first which probably also eliminates the LOS alarm.

2. Is the LE, which is connected to the relevant port, reporting an equipment alarm?– If an equipment alarm at the LE is present try to fix this fault first which probably

also eliminates the LOS alarm.3. Check the cable connection

– Take special care if an optical STM-1/OC-3 line is used (see warning above)– Proper connection at the LE (good contact, clean optical connector)– Proper connection at the Node B (good contact, clean optical connector)– Undamaged cable between Node B and LE respectively other Node B or RNC

4. Check the OVPT or IUBCONElectrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (over-voltage protection and tracer module) equipped with surge arresters or an IUBCON (Iub connector). Both are available for coax and symmetrical cables.– Check surge arresters at OVPT and replace a defective one if necessary– Replace OVPT or IUBCON if any other reason could not be found. Replacement

must be done according to the “Replacing Node B Units” instructions.

Configuration mismatch?Is the configuration of the relevant ports at either end in accordance with each other? • For Node B use the LMT to upload the nbDatabase and analyze the settings for the

relevant port • For LE the appropriate local maintenance system has to be used

If the misconfiguration can be identified as probable cause for the error report the align-ment of the settings should clear the fault.





217

Troubleshooting Node B 202057 - Loss Of Frame on Physical Link


159 202057 - Loss Of Frame on Physical Link


159.2 Error DescriptionLoss of frame (LOF) indication has been received on a physical link E1, J1, T1 or STM-1/OC-3 (according to reported MOC in the failure event report).

This alarm indicates one of the following: • Basic frame synchronization has been lost on the transport interface between the

Node B and the next device upstream.This may be due to– Misconfiguration of the hardware at either end– Faulty hardware at either end– Problems on the transmission medium between the two endsThe loss of basic frame alignment always causes the output of this alarm, indepen-dent of the Node B’s mode of CRC operation (disabled, automatic, forced).

• Although both frame alignment is active and the reporting line is running, a great number of CRC-4 errors occurred. This failure causes the output of the ’Loss of Frame on Physical Link’ alarm only if the Node B operates in CRC forced mode.The loss of frame is indicated when the number of detected CRC-4 errors exceeds a threshold 914 negative comparisons out of 1,000 CRC-4 checks per second. In this case, the Node B goes out of synchronization.

The loss of frame may be the root cause for alarms indicated by different NEs in the supervision of the RC. If this NE is an NB/RSxxx, the following subsequent alarms may be output: • Downstream direction:

– 202059 - Alarm Indication Signal on Physical Link– 202062 - Line Alarm Indication Signal Indication on STM1 Physical Link

• Upstream direction:– 202060 - Remote Alarm Indication on Physical Link– 202063 - Line Remote Defect Indication on STM1 Physical Link

Additionally, the LOF causes the reporting Node B’s system clock to switch in holdover mode, indicated by the 202506 - Node B system clock in holdover mode alarm.

159.3 Troubleshooting (LMT)Usually the Node B is connected to the RNC or each other (Iub interface) via Link Equip-ment (LE, such as SDH/PDH multiplexers, ATM switches, or repeaters) and in some



Event Type: communicationAlarm

Probable Cause: LossOfFrame

Severity: major

218 DN70580522Issue 01A



202057 - Loss Of Frame on Physical Link

rare cases by direct lines. If LE is involved the operation and maintenance system of this network has to be used for getting information about the state and status of the relevant network element (NE).


• Star configurationonly the reported Node B

• Hub configurationif the hub Node B is the reporting one for a connection to the RNC:– for E1/J1/T1: the supplied Node B of the relevant E1/J1/T1 link will report VP

AIS– for STM-1/OC-3: all supplied Node Bs will report AIS

• Cascade configurationall Node Bs in the chain downstream the LOF reporting Node B will initiate a VP AIS error message for the relevant E1/J1/T1 link respectively all if the first Node B is reporting and connected to the RNC via STM-1/OC-3.

• Loop configurationthe redundant path in the loop configuration will take over the traffic

To isolate the fault check for other error messages in the following order:1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B


– Use the filter and sort function to concentrate on CC alarmsIf an equipment alarm of the CC is present try to fix this fault first which probably also eliminates the LOF alarm.


also eliminates the LOF alarm.3. Check the cable connection


4. Check the OVPT or IUBCONElectrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (over-voltage protection and tracer module) equipped with surge arresters or an IUBCON (Iub connector). Both are available for coax and symmetrical cables.– Check surge arresters at OVPT and replace a defective one if necessary





219

Troubleshooting Node B 202057 - Loss Of Frame on Physical Link


– Replace OVPT or IUBCON if any other reason could not be found. Replacement must be done according to the “Replacing Node B Units” instructions.

Configuration mismatch?Is the configuration of the relevant ports at either end in accordance with each other? • For Node B use the LMT to upload the nbDatabase and analyze the settings for the



220 DN70580522Issue 01A



202058 - Loss Of Cell Delineation on Physical Link

160 202058 - Loss Of Cell Delineation on Physical Link


160.2 Error DescriptionLoss of cell delineation (LCD) indication has been received on a physical link E1, J1, T1 or STM-1/OC-3 (according to reported MOC in the failure event report). This indicates that ATM cells are not being delineated correctly and so cannot be extracted from the received signal. This may be due to faulty hardware at either end or problems on the transmission medium between the two ends.

If the reporting Node B is equipped with a CCv3, this alarm may be output due to a database misconfiguration, caused by the following: the “local” Node B is directly con-nected to a “remote” Node B via E1, J1, or T1 line (cascade configuration). The line coding attribute of the E1 or J1/T1 line (e1LineCode or j1LineCode, respectively), however, is set to different values in the “local” and in the “remote” Node B’s DB.

The loss of cell delineation may be the root cause for alarms indicated by different NEs in the supervision of the RC. If this NE is an NB/RSxxx, the following subsequent alarms may be output: • Downstream direction:

– 202060 - Remote Alarm Indication Signal on Physical Link– 202075 - Alarm Indication Signal on an ATM VP

• Upstream direction:– 202076 - Remote Defect Indication on an ATM VP

160.3 Troubleshooting (LMT)Usually the Node B is connected to the RNC or each other (Iub interface) via Link Equip-ment (LE, such as SDH/PDH multiplexers, ATM switches, or repeaters) and in some rare cases by direct lines. If LE is involved the operation and maintenance system of this network has to be used for getting information about the state and status of the relevant network element (NE).


• Star configurationonly the reported Node B




Probable Cause: LossOfCellDelineation

Severity: major


221

Troubleshooting Node B 202058 - Loss Of Cell Delineation on Physical Link


• Hub configurationif the hub Node B is the reporting one for a connection to the RNC:– for E1/J1/T1: the supplied Node B of the relevant E1/J1/T1 link will report VPAIS– for STM-1/OC-3: all supplied Node Bs will report AIS

• Cascade configurationall Node Bs in the chain downstream the LCD reporting Node B will initiate a VPAIS error message for the relevant E1/J1/T1 link respectively all if the first Node B is reporting and connected to the RNC via STM-1/OC-3.

• Loop configurationthe redundant path in the loop configuration will take over the traffic

To isolate the fault check for other error messages in the following order:

1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B present?Using the ALARM View window of the LMT:– Click on the “Alarm View” button or use the shortcut key Ctrl + A

– Use the filter and sort function to concentrate on CC alarmsIf an equipment alarm of the CC is present try to fix this fault first which probably also eliminates the LCD alarm.


also eliminates the LCD alarm.3. Check the cable connection



must be done according to the “Replacing Node B Units” instructions.5. Configuration mismatch

Is the configuration of the relevant ports at either end in accordance with each other, for example with regard to the line coding?– for Node B use the LMT to upload the nbDatabase and analyze the settings for

the relevant port




222 DN70580522Issue 01A



202058 - Loss Of Cell Delineation on Physical Link

– for LE the appropriate local maintenance system has to be usedIf the misconfiguration can be identified as probable cause for the error report the alignment of the settings should clear the fault.

6. If none of the proposed actions results in a fault clearance contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


223

Troubleshooting Node B 202059 - Alarm Indication Signal on Physical Link


161 202059 - Alarm Indication Signal on Physical Link


161.2 Error DescriptionAlarm indication signal (AIS) indication has been received on a physical link E1, J1, or T1 (according to reported MOC in the failure event report). This alarm indicates that a problem has been detected upstream from the Node B (backward direction) on the physical link reporting the alarm. Transmission to the Node B from that direction has probably been interrupted on this link. The Node B forwards a VP AIS to the next NE in forward direction (downstream). The AIS are forwarded by all downstream NEs until they reach the NE which terminates the link affected by the failure.

This alarm is triggered by a preceded alarms from another upstream NE in the supervi-sion of the RC. If this NE is an NB/RSxxx, the following alarms may be the trigger: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link

Alternatively, an alarm from Link Equipment (LE, such as SDH/PDH multiplexers, ATM switches, or repeaters) in upstream direction may be the root cause, such as: • Loss Of Signal (LOS) • Loss Of Frame (LOF)

Additionally, the AIS causes the reporting Node B’s system clock to switch in holdover mode, indicated by the 202506 - Node B system clock in holdover mode alarm.

161.3 Troubleshooting (LMT)Because this error message is a consequence of a preceded alarm from an upstream NE in the supervision of the RC, the troubleshooting has to start with investigation of the trigger alarm.

As regards Node B PF2 alarms, find the relevant alarm in the list of the ALARM View window of the LMT:1. Click on the “Alarm View” button or use the shortkey Ctrl + A .2. Use the filter and sort function to concentrate on the relevant alarms

As regards any other NE in the supervision of the RC, find the relevant alarm in the list of the Alarm Monitoring Application:1. Select and open the icon “Alarm Monitoring” in the Application Launcher window

(double left-click)


E1TTP, J1TTP


Probable Cause: AlarmIndicationSignal

Severity: major

224 DN70580522Issue 01A



202059 - Alarm Indication Signal on Physical Link

2. Look for one of the alarms in the list below reported from an upstream NE

For troubleshooting instructions, refer to preceded alarms reported by NB/RSxxx: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link

LE-caused alarms and alarms caused by other NEs are handled accordingly.

After solving the problem which initiated the trigger alarm this error message will also be cleared.

If the fault cannot be cleared, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


225

Troubleshooting Node B 202060 - Remote Alarm Indication on Physical Link


162 202060 - Remote Alarm Indication on Physical Link


162.2 Error DescriptionRemote alarm indication (RAI) indication has been received on a physical link E1, J1, or T1 (according to reported MOC in the failure event report). Indicates that a problem has been detected downstream from the Node B on the physical link reporting the alarm. Reception from the Node B in that direction has probably been interrupted on this link. This may be due to faulty hardware at either end or problems on the transmission medium between the two ends.

This alarm is triggered by a preceded alarm from another downstream NE in the super-vision of the RC. If this NE is an NB/RSxxx, the following alarms may be the trigger: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202058 - Loss Of Cell Delineation on Physical Link

Alternatively, an alarm from Link Equipment (LE, such as SDH/PDH multiplexers, ATM switches, or repeaters) in downstream direction may be the root cause, such as: • Loss Of Signal (LOS) • Loss Of Frame (LOF) • Alarm Indication Signal (AIS)

162.3 Troubleshooting (LMT)Because this error message is a consequence of a preceded alarm from a downstream NE in the supervision of the RC, the troubleshooting has to start with investigation of the trigger alarm.



(double left-click)2. Look for one of the alarms in the list below reported from a downstream NE


E1TTP, J1TTP


Probable Cause: RemoteAlarmIndication

Severity: major

226 DN70580522Issue 01A



202060 - Remote Alarm Indication on Physical Link

For troubleshooting instructions refer to one of the following preceded alarms reported by another NB/RSxxx: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202058 - Loss Of Cell Delineation on Physical Link

LE-caused alarms and preceded alarms of other NEs are handled accordingly.




227

Troubleshooting Node B 202061 - Loss of Multi Frame Alarm Indication on E1Physical Link

Id:0900d8058022b7eeConfidential

163 202061 - Loss of Multi Frame Alarm Indica-tion on E1 Physical Link


163.2 Error DescriptionLoss of multi frame alarm (LOMF) indication has been received on an E1 physical link. This alarm indicates that multiframe synchronization has been lost on the E1 transport interface between the Node B and the next device upstream.

This may be due to: • Misconfiguration of the hardware at either end • Faulty hardware at either end • Problems on the transmission medium between the two ends

The “202061 - Loss of Multi Frame Alarm Indication on E1 Physical Link” alarm may be caused by the following:

The Node B's E1TTP managed object's attribute crcOperationMode, which indicates the mode of CRC operation, is set to its default value crcForced whereas the frame format for the RNC is set to 0 meaning that the CRC is disabled.

As a consequence of these settings, the E1TTP’s OST/AVS combination changes to disabled/failed.

If the Node B's E1TTP managed object's attribute crcOperationMode is set to crcAu-tomatic, however, the 202098 - CRC4 not used by FE reported on E1TTP alarm is output. Refer to the alarm’s error description and follow its troubleshooting.

163.3 Troubleshooting (LMT)Take the following measures to clear the alarm cause:1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B


– Use the filter and sort function to concentrate on CC alarmsIf an equipment alarm of the CC is present try to fix this fault first which probably also eliminates the LOMF alarm.


also eliminates the LOMF alarm.


E1TTP


Probable Cause: LossOfMultiFrame

Severity: major

228 DN70580522Issue 01A


Id:0900d8058022b7eeConfidential

202061 - Loss of Multi Frame Alarm Indication on E1 Physical Link

3. Check the cable connection


4. Check the OVPT or IUBCONElectrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (over-voltage protection and tracer module) equipped with surge arresters or an IUBCON (Iub connector). Both are available for coax and symmetrical cables.– Check surge arresters at OVPT and replace a defective one if necessary– Replace OVPT or IUBCON if any other reason could not be found.


5. Configuration mismatchIs the configuration of the relevant ports at either end in accordance with each other?– For Node B use the LMT to upload the nbDatabase and analyze the settings for

the relevant port– For LE the appropriate local maintenance system has to be usedIf the misconfiguration can be identified as probable cause for the error report the alignment of the settings should clear the fault.






229

Troubleshooting Node B 202062 - Line Alarm Indication Signal Indication onSTM1 Physical Link


164 202062 - Line Alarm Indication Signal Indica-tion on STM1 Physical Link


164.2 Error DescriptionLine alarm indication signal (L-AIS) indication has been received on an STM-1/OC-3 physical link. This alarm indicates that a problem (e.g. LOS, LOF, LOP) has been detected upstream from the Node B (backward direction) on the STM-1/OC-3 link reporting the alarm. Transmission to the Node B from that direction has probably been interrupted on this link. The Node B forwards a VP AIS to the next NE in forward direc-tion (downstream). The VP AIS are forwarded by all downstream NEs until they reach the NE which terminates the link affected by the failure.

This alarm is triggered by a preceded alarm from another upstream NE in the supervi-sion of the RC. If this NE is an NB/RSxxx, the following alarms may be the trigger: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202064 - Path Loss of Pointer Indication on STM1 Physical Link

Alternatively, an alarm from Link Equipment (LE, such as SDH/PDH multiplexers, ATM switches, or repeaters) in upstream direction may be the root cause, such as: • Loss Of Signal (LOS) • Loss Of Frame (LOF) • Loss Of Pointer (LOP)

Additionally, the L-AIS causes the reporting Node B’s system clock to switch in holdover mode, indicated by the 202506 - Node B system clock in holdover mode alarm.




Stm1TP



Severity: major

230 DN70580522Issue 01A



202062 - Line Alarm Indication Signal Indication on STM1 Physical Link


(double left-click)2. Look for one of the alarms in the list below reported from an upstreamNE

For troubleshooting instructions refer to the following preceded alarms reported by another NB/RSxxx: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202064 - Path Loss of Pointer Indication on STM1 Physical Link

LE caused alarms and preceded alarms of other NEs are handled accordingly.




231

Troubleshooting Node B 202063 - Line Remote Defect Indication on STM1Physical Link


165 202063 - Line Remote Defect Indication on STM1 Physical Link


165.2 Error DescriptionLine remote defect indication (L-RDI) has been received on an STM-1/OC-3 physical link. The L-RDI indicates that a problem has been detected downstream from the Node B on the link reporting the alarm. In other words, L-RDI is used by the node termi-nating the link to inform the other terminating NE in the backward direction (upstream) about a failure that was detected in forward direction. Reception from the Node B in that direction has probably been interrupted on the reporting link.

The fault leading to this alarm may have been caused by faulty hardware at either end or problems on the transmission medium between the two ends.

This alarm is triggered by a preceded alarm from another downstream NE in the super-vision of the RC. If this NE is an NB/RSxxx, the following alarms may be the trigger: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202064 - Path Loss of Pointer Indication on STM1 Physical Link

Alternatively, an alarm from Link Equipment (LE, such as SDH/PDH multiplexers, ATM switches, or repeaters) in downstream direction may be the root cause, such as: • Loss Of Signal (LOS) • Loss Of Frame (LOF) • Loss Of Pointer (LOP) • Alarm Indication Signal (AIS)




Stm1TP


Probable Cause: RemoteAlarmIndicator

Severity: major

232 DN70580522Issue 01A



202063 - Line Remote Defect Indication on STM1 Physical Link



For troubleshooting instructions refer to one of the following preceded alarms reported by another NB/RSxxx: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202064 - Path Loss of Pointer Indication on STM1 Physical Link

LE-caused alarms and preceded alarms of other NEs are handled accordingly.




233

Troubleshooting Node B 202064 - Path Loss of Pointer Indication on STM1Physical Link


166 202064 - Path Loss of Pointer Indication on STM1 Physical Link


166.2 Error DescriptionPath loss of pointer (P-LOP) indication has been received on an STM-1/OC-3 physical link. The pointer enables the STM-1/OC-3 device on the Node B to locate the payload within the signal. If the Node B STM-1/OC-3 interface has received an invalid path pointer, it will declare a loss of pointer condition. Because the STM-1/OC-3 interface cannot determine where the payload starts, all downstream traffic will be lost as long as the condition persists. This may be due to faulty hardware at either end or problems on the transmission medium between the two ends.

The path loss of pointer may be the root cause for alarms indicated by different NEs in the supervision of the RC. If this NE is an NB/RSxxx, the following subsequent alarms may be output: • Downstream direction:

202065 - Path Alarm Indication Signal on STM1 Physical Link • Upstream direction:

202066 - Path Remote Defect Indication on STM1 Physical Link

166.3 fcTroubleshooting (LMT)1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B


– Use the filter and sort function to concentrate on CC alarmsIf an equipment alarm of the CC is present try to fix this fault first which probably also eliminates the P-LOP alarm.


also eliminates the P-LOP alarm.


Stm1TP


Probable Cause: LossOfPointer

Severity: major

234 DN70580522Issue 01A



202064 - Path Loss of Pointer Indication on STM1 Physical Link

3. Check the cable connection



must be done according to the “Replacing Node B Units” instructions.5. If none of the proposed actions results in a fault clearance contact the technical

assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.





235

Troubleshooting Node B 202065 - Path Alarm Indication Signal on STM1 Physi-cal Link


167 202065 - Path Alarm Indication Signal on STM1 Physical Link


167.2 Error DescriptionA Path Alarm Indication Signal (P-AIS) has been received on an STM-1/OC-3 physical link. In other words, the value 1 was received for three times consecutively at all relevant pointer bytes. The mismatch may be caused by an incorrect configuration at the trans-mitting end.

AIS is used to inform the neighboring NE in forward direction (downstream) about a failure that was detected in in backward direction (upstream). AIS are forwarded by all NEs until they reach the NE which terminates the link that is affected by the failure.

The P-AIS indicates the following: • At least one of the following problems has been detected upstream from the Node B

on the STM-1/OC-3 link reporting this alarm:– Loss of Signal (LOS)– Loss of Frame (LOF)– Path Loss of Pointer (P-LOP)

• Transmission from upstream direction to the Node B has probably been interrupted on the reporting link.

The “202065 - Path Alarm Indication Signal on STM1 Physical Link” alarm may be trig-gered by a preceded alarm reported by another upstream NE in the supervision of the RC. If this NE is an NB/RSxxx, the following alarms may be the trigger: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202064 - Path Loss of Pointer Indication on STM1 Physical Link

Alternatively, an alarm from link equipment (LE, such as SDH/PDH multiplexers, ATM switches, or repeaters) in upstream direction may be the root cause: • Loss Of Signal (LOS) • Loss Of Frame (LOF) • Loss Of Pointer (LOP)


Stm1TP

Event Type: communicationAlarm


Severity: major

236 DN70580522Issue 01A



202065 - Path Alarm Indication Signal on STM1 Physi-cal Link




(double left-click)2. Look for one of the alarms in the list below reported from an upstream NE

For troubleshooting instructions refer to one of the following preceded alarms, reported by another NB/RSxxx: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202064 - Path Loss of Pointer Indication on STM1 Physical Link

Alarms caused by LE or other NEs are handled accordingly.

After having solved the problem which initiated the trigger alarm, this error message will also be cleared.

If the fault could not be cleared yet, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


237

Troubleshooting Node B 202066 - Path Remote Defect Indication on STM1Physical Link


168 202066 - Path Remote Defect Indication on STM1 Physical Link


168.2 Error DescriptionA Path Remote Defect Indication (P-RDI) indication has been received on the reporting STM-1/OC-3 physical link. The mismatch may be caused by an incorrect configuration at the transmitting end.

RDI is used by the node terminating the link to inform the other terminating NE in the backward (upstream) direction about a failure that was detected in forward (down-stream) direction.

The P-RDI indicates the following: • At least one of the following problems has been detected downsteam from the

Node B on the STM-1/OC-3 link reporting this alarm:– Loss of Signal (LOS)– Loss of Frame (LOF)– Path Loss of Pointer (P-LOP)

• Transmission in downstream direction of the Node B has probably been interrupted on the reporting link.

The “202066 - Path Remote Defect Indication on STM1 Physical Link” alarm may be trig-gered by a preceded alarm, reported by another downsteam NE in the supervision of the RC. If this NE is an NB/RSxxx, the following alarms may be the trigger: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202064 - Path Loss of Pointer Indication on STM1 Physical Link

Alternatively, an alarm from link equipment (LE, such as SDH/PDH multiplexers, ATM switches, or repeaters) in downstream direction may be the root cause, such as: • Loss Of Signal (LOS) • Loss Of Frame (LOF) • Loss Of Pointer (LOP)



Stm1TP



Severity: major

238 DN70580522Issue 01A



202066 - Path Remote Defect Indication on STM1 Physical Link




For troubleshooting instructions refer to one of the following preceded alarms, reported by another NB/RSxxx: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202064 - Path Loss of Pointer Indication on STM1 Physical Link

Alarms caused by LE or by other NEs are handled accordingly.

After having solved the problem which initiated the trigger alarm, this error message will also be cleared.

If the fault could not be cleared yet, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


239

Troubleshooting Node B 202068 - Signal Label Mismatch Indication on STM1Physical Link


169 202068 - Signal Label Mismatch Indication on STM1 Physical Link


169.2 Error DescriptionSignal label mismatch (SLM) indication has been received on an STM-1/OC-3 physical link. This may be because of corruptions on the STM-1/OC-3 line or incorrect configu-ration at the transmitting end.

169.3 Troubleshooting (LMT)Is the configuration of the relevant ports at either end in accordance with each other? • For Node B use the LMT to upload the nbDatabase and analyze the settings for the



If none of the proposed actions results in a fault clearance contact the technical assis-tance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.


Stm1TP


Probable Cause: SignalLabelMismatch

Severity: minor

240 DN70580522Issue 01A



202070 - Signal Degrade Indication on STM1 Physical Link

170 202070 - Signal Degrade Indication on STM1 Physical Link


170.2 Error DescriptionSignal degrade (SD) indication has been received on an STM-1/OC-3 physical link. This indicates that the bit error rate on the received STM-1/OC-3 signal has exceeded the threshold set in the signalDegradeThreshold configuration attribute. This may be due to faulty hardware at either end or problems on the transmission medium between the two ends.



– Use the filter and sort function to concentrate on CC alarmsIf an equipment alarm of the CC is present try to fix this fault first which probably also eliminates the SD alarm.


also eliminates the SD alarm.3. Check the cable connection



Stm1TP


Probable Cause: DegradedSignal

Severity: minor





241

Troubleshooting Node B 202070 - Signal Degrade Indication on STM1 PhysicalLink





242 DN70580522Issue 01A



202071 - Excessive Bit Error Rate Indication on STM1 Physical Link

171 202071 - Excessive Bit Error Rate Indication on STM1 Physical Link


171.2 Error DescriptionExcessive bit error rate (EBER) indication has been received on an STM-1/OC-3 physical link. This indicates that the bit error rate on the received STM-1/OC-3 signal has exceeded the threshold set in the signalFailThreshold configuration attribute. This may be due to faulty hardware at either end or problems on the transmission medium between the two ends.



– Use the filter and sort function to concentrate on CC alarmsIf an equipment alarm of the CC is present try to fix this fault first which probably also eliminates the EBER alarm.


also eliminates the EBER alarm.3. Check the cable connection



Stm1TP


Probable Cause: ExcessiveBER

Severity: major





243

Troubleshooting Node B 202071 - Excessive Bit Error Rate Indication on STM1Physical Link





244 DN70580522Issue 01A



202072 - Alarm Indication Signal on an ATM VC

172 202072 - Alarm Indication Signal on an ATM VC


172.2 Error DescriptionAn alarm indication signal (AIS) has been received on an ATM VC. The ATM cell stream on the affected VC will probably have been interrupted.

AIS indicates that another NE upstream (backward direction) from the Node B detected an alarm condition and thus sent the AIS. The alarm indication signal is used to inform neighboring NE in forward direction (downstream) about the alarm condition. AIS are then forwarded by all NEs in downstream direction until they reach the NE which termi-nates the link that is affected by the failure.

This alarm is triggered by a preceded alarms from another upstream NE in the supervi-sion of the RC. If this NE is an NB/RSxxx, the following alarms may be the trigger: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202058 - Loss Of Cell Delineation on Physical Link







VcTTP



Severity: minor


245

Troubleshooting Node B 202072 - Alarm Indication Signal on an ATM VC


For troubleshooting instructions refer to one of the following preceded alarms, reported by another NB/RSxxx: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202058 - Loss Of Cell Delineation on Physical Link

LE-caused alarms and alarms reported by other NEs are handled accordingly.



246 DN70580522Issue 01A



202073 - Remote Defect Indication on an ATM VC

173 202073 - Remote Defect Indication on an ATM VC


173.2 Error DescriptionA remote defect indication (RDI) indication has been received on an ATM VC. The ATM cell stream on the affected VC will probably have been interrupted.




173.3 Troubleshooting (LMT)Because this error message is a consequence of a preceded alarm from an upstream NE the troubleshooting has to start with investigation of the trigger alarm. Find the relevant alarm in the list of the ALARM View window of the LMT:1. Click on the “Alarm View” button or use the shortkey Ctrl + A .2. Use the filter and sort function to concentrate on the relevant alarms


LE-caused alarms and alarms cause by other NEs are handled accordingly.



VcTTP



Severity: minor


247

Troubleshooting Node B 202073 - Remote Defect Indication on an ATM VC



248 DN70580522Issue 01A



202074 - SSCOP Failure Indication on an ATM VC used by ALCAP or NBAP

174 202074 - SSCOP Failure Indication on an ATM VC used by ALCAP or NBAP


174.2 Error DescriptionA SAAL failure has been received on an ATM VC used for ALCAP or NBAP signaling. This may be only a temporary failure from which the link will have recovered by itself (e.g. by automatic retransmission). Persistent reports of this kind may be due to hardware or software failure at either end or problems on the transmission medium between the two ends.



– Use the filter and sort function to concentrate on CC alarmsIf an equipment alarm of the CC is present try to fix this fault first which probably also eliminates this alarm.


also eliminates this alarm.3. Check the cable connection



VcTTP


Probable Cause: SscopFailure

Severity: warning





249

Troubleshooting Node B 202074 - SSCOP Failure Indication on an ATM VCused by ALCAP or NBAP





250 DN70580522Issue 01A


Id:0900d80580228ba1Confidential

202075 - Alarm Indication Signal on an ATM VP

175 202075 - Alarm Indication Signal on an ATM VP


175.2 Error DescriptionAn alarm indication signal (AIS) indication has been received on an ATM VP. The ATM cell stream on the affected VP will probably have been interrupted.

AIS indicates that another NE upstream (backward direction) from the Node B detected an alarm condition and thus sent the AIS. The alarm indication signal is used to inform neighboring NE in forward direction (downstream) about the alarm condition. AIS are then forwarded by all NEs in downstream direction until they reach the NE which termi-nates the link that is affected by the failure.

This alarm is triggered by a preceded alarm from another upstream NE in the supervi-sion of the RC. If this NE is an NB/RSxxx, the following alarms may be trigger: • 202056 - Loss Of Signal on Physical Link • 202057 - Loss Of Frame on Physical Link • 202058 - Loss Of Cell Delineation on Physical Link







VpTTP



Severity: minor


251

Troubleshooting Node B 202075 - Alarm Indication Signal on an ATM VP



LE-caused alarms and alarms caused by other NEs are handled accordingly.



252 DN70580522Issue 01A



202076 - Remote Defect Indication on an ATM VP

176 202076 - Remote Defect Indication on an ATM VP


176.2 Error DescriptionA remote defect indication (RDI) indication has been received on an ATM VP. The ATM cell stream on the affected VP will probably have been interrupted.









VpTTP



Severity: minor


253

Troubleshooting Node B 202076 - Remote Defect Indication on an ATM VP



LE-caused alarms and alarms reported by other NEs are handled accordingly.



254 DN70580522Issue 01A



202077 - ALCAP PVC Out Of Service Indication

177 202077 - ALCAP PVC Out Of Service Indica-tion


177.2 Error DescriptionThe signaling protocol (STC) used by ALCAP has indicated that the connection is out of service. This may be due to traffic congestion or a failure in the network or because the far end is not configured. STC will repeatedly attempt to reconnect and will indicate when the connection is in service.



VcTTP



Severity: major


255

Troubleshooting Node B 202078 - Loss Of Delay Synchronization on IMA Link


178 202078 - Loss Of Delay Synchronization on IMA Link



If an IMA group has been configured, however, not being operational during start-up, the Node B possibly restarts some minutes after start-up.

A loss of delay synchronization (LODS) defect is reported when the link differential delay between the link and the other links in the group is over the tolerable link differential delay (as defined by the configuration attribute imaGroupDiffDelayMax). If this alarm occurs then the ImaGroup will automatically cease transmitting on the link and (assum-ing that there are sufficient good links for the Group to remain Operational) continue to operate using the remaining good links.



ImaLink



Severity: minor

256 DN70580522Issue 01A



202079 - Loss Of IMA Frame on IMA Link

179 202079 - Loss Of IMA Frame on IMA Link




The LIF (Loss of IMA Frame) defect is the occurrence of persistent OIF (Out of IMA Frame) anomalies for at least 2 IMA frames. This indicates that the IMA Frame synchro-nisation has been lost. If this alarm occurs then the ImaGroup will automatically cease transmitting on the link and (assuming that there are sufficient good links for the Group to remain Operational) continue to operate using the remaining good links.



ImaLink



Severity: minor


257

Troubleshooting Node B 202080 - Remote Failure Indicator on IMA Link


180 202080 - Remote Failure Indicator on IMA Link


180.2 Error DescriptionPersistence of an RDI-IMA defect at the near end (NE). An RDI-IMA is when one of the available remote defect indicators (including IMA link specific defect) is indicated in the link related Link Information field. This indicates that the IMA Link at the far end has detected a defect and has reported it to the near end. If this alarm occurs then the ImaGroup will automatically cease transmitting on the link and (assuming that there are sufficient good links for the Group to remain Operational) continue to operate using the remaining good links.



ImaLink



Severity: minor

258 DN70580522Issue 01A



202081 - IMA Tx link is detected as mis-connected

181 202081 - IMA Tx link is detected as mis-con-nected


181.2 Error DescriptionTX link is detected as mis-connected. This is reported when the IMA unit has determined that the Tx link is not connected to the same far end (FE) IMA unit as the other TX links in the group. This condition will be detected by the Test Pattern Procedure.

181.3 Troubleshooting (LMT)Check the cable connections.


ImaLink



Severity: minor


259

Troubleshooting Node B 202082 - IMA Rx link is detected as mis-connected


182 202082 - IMA Rx link is detected as mis-con-nected


182.2 Error DescriptionRX link is detected as mis-connected. This is reported when the IMA unit has deter-mined that the Rx link is not connected to the same far end (FE) IMA unit as the other Rx links in the group. This condition will be detected by the Test Pattern Procedure.

182.3 Troubleshooting (LMT)Check the cable connections.


ImaLink



Severity: minor

260 DN70580522Issue 01A



202083 - Tx fault declared at the NE on IMA Link

183 202083 - Tx fault declared at the NE on IMA Link


183.2 Error DescriptionImplementation specific TX fault declared at the near end (NE). This alarm indication that a hardware specific defect has been detected in the Tx direction on one link of the IMAGroup. If this alarm occurs then the ImaGroup will automatically cease transmitting on the link and (assuming that there are sufficient good links for the Group to remain Operational) continue to operate using the remaining good links. This alarm is likely to be due to faulty hardware at the near end.



ImaLink



Severity: minor


261

Troubleshooting Node B 202084 - Rx fault declared at the NE on IMA Link


184 202084 - Rx fault declared at the NE on IMA Link


184.2 Error DescriptionImplementation specific RX fault declared at the near end (NE). This alarm indication that a hardware specific defect has been detected in the Rx direction on one link of the IMAGroup. If this alarm occurs then the ImaGroup will automatically cease transmitting on the link and (assuming that there are sufficient good links for the Group to remain operation) continue to operate using the remaining good links. This alarm is likely to be due to faulty hardware at either end.



ImaLink



Severity: minor

262 DN70580522Issue 01A



202085 - FE has reported Tx-Unusable on IMA Link

185 202085 - FE has reported Tx-Unusable on IMA Link


185.2 Error DescriptionThe far end (FE) has reported that the link is unusable in the TX direction. When the ImaGroup is starting up this is an indication that would be expected before the link gets to its normal operating state and so does not necessarily indicate a problem. Thereafter this alarm indication means that the link is no longer active for some reason that may be indicated by other alarms. If this alarm occurs then the ImaGroup will automatically cease transmitting on the link and (assuming that there are sufficient good links for the Group to remain Operational) continue to operate using the remaining good links.

185.3 Troubleshooting (LMT)Take the following measures to clear the alarm cause:1. Check the cable connections.2. If the cable connections were not indicated as basic cause, contact the technical



ImaLink



Severity: minor


263

Troubleshooting Node B 202086 - FE has reported Rx-Unusable on IMA Link


186 202086 - FE has reported Rx-Unusable on IMA Link


186.2 Error DescriptionThe far end (FE) has reported that the link is unusable in the RX direction. When the ImaGroup is starting up this is an indication that would be expected before the link gets to its normal operating state and so does not necessarily indicate a problem. Thereafter this alarm indication means that the link is no longer active for some reason that may be indicated by other alarms. If this alarm occurs then the ImaGroup will automatically cease transmitting on the link and (assuming that there are sufficient good links for the Group to remain Operational) continue to operate using the remaining good links.

186.3 Troubleshooting (LMT)Take the following measures to clear the alarm cause:1. Check the cable connections.2. If the cable connections were not indicated as basic cause, contact the technical



ImaLink



Severity: minor

264 DN70580522Issue 01A



202087 - Startup FE reported on IMA Group

187 202087 - Startup FE reported on IMA Group


187.2 Error DescriptionThe far end (FE) IMA Group is in the Startup state. This alarm indication should be seen as part of the normal startup procedure of the Group and does not necessarily indicate a problem. Thereafter it indicates that the Group has reset to its startup state for some reason that may be explained by other alarms.



ImaGroup



Severity: major


265

Troubleshooting Node B 202088 - Config Abort reported on IMA Group


188 202088 - Config Abort reported on IMA Group




This indication means that the IMA Group has aborted its attempted startup for some reason. This may be because the IMA Group at the far end has been configured with incompatible attributes to those that have been used at the near end. Possible incom-patible attributes are: Frame Length, Group Symmetry or the IMA Version. These may be fixable by modification to the configuration at one or both ends.

188.3 Troubleshooting (LMT)Check the hardware compatibility of the configuration.


ImaGroup



Severity: major

266 DN70580522Issue 01A



202089 - Config Abort FE reported on IMA Group

189 202089 - Config Abort FE reported on IMA Group




This indication is the same as the imaGroupConfigAbort (see: 202088 - Config Abort reported on IMA Group) but has been reported by the far end (FE) IMA to the near end (NE). The causes and possible fixes are the same as for the imaGroupConfigAbort.

189.3 Troubleshooting (LMT)Check the hardware compatibility of the configuration.


ImaGroup



Severity: major


267

Troubleshooting Node B 202090 - Insufficient Links reported at NE on IMAGroup


190 202090 - Insufficient Links reported at NE on IMA Group




The near end (NE) has reported that the number of active links (operational state = enabled) is less than is required for the group to be operational.

This may be caused by one of the following: • The configuration of the group requires more links than have been configured. • One or more links are non-operational for other reasons, such as fault conditions. • One or more links have not yet completed their startup procedure.

If enough links have been configured, the status of these links must be examined to determine why not sufficiently enough of these links are in the operational state enabled.

At startup of the group this alarm indication would normally be expected to be seen as the group performs its startup procedure.

190.3 Troubleshooting (LMT)Perform the following tasks to solve this error:1. Check Node B database.

Use the mibCheck or mibCheckWin tool which is supplied with the Node B software. Refer to the “Node B Database Editing Guide”.The number of links required for the group to be operational is configured by the attri-bute “imaGroupMinNumLinks”

2. Change Node B database.Proceed according to the “Node B Database Editing Guide”.


ImaGroup



Severity: major

268 DN70580522Issue 01A


Id:0900d8058022b8aeConfidential

202091 - Insufficient Links at FE reported on IMA Group

191 202091 - Insufficient Links at FE reported on IMA Group




The far end (FE) has reported that the number of active links (operational state = enabled) is less than is required for the group to be operational.

The reasons and actions for this alarm are similar to those described for the Insufficient Links indication at the near end (see: 202090 - Insufficient Links reported at NE on IMA Group).





ImaGroup



Severity: major


269

Troubleshooting Node B 202092 - Group Blocked at FE reported on IMA Group


192 202092 - Group Blocked at FE reported on IMA Group


192.2 Error DescriptionThe far end (FE) IMA group has been blocked (i.e. its adminstrative state has been set to locked by the operator at the far end). As a consequence, the far end IMA group is not operating.

192.3 Troubleshooting (LMT)Perform the following tasks to solve this error:1. Check the administrative state of the IMA group at the far end (FE).2. Change the administrative state to unlocked at the far end.


ImaGroup



Severity: major

270 DN70580522Issue 01A


Id:0900d8058022b8beConfidential

202093 - Timing Synch error reported on IMA Group

193 202093 - Timing Synch error reported on IMA Group




The far end (FE) transmit clock mode is different from the near end (NE) transmit clock mode due to different configuration of the group. The imaGroupNeTxClkMode at both ends should be set to CTC (Common Transmit Clock).





ImaGroup



Severity: major


271

Troubleshooting Node B 202095 - The Near End IMA has detected an invalidversion set by the Far End


194 202095 - The Near End IMA has detected an invalid version set by the Far End


194.2 Error DescriptionThe Node B does only support IMA version 1.1. The far end IMA group, however, is using a different IMA version. This indicates that the far end hardware configuration is incompatible with the near end hardware.

194.3 Troubleshooting (LMT)Check the hardware compatibility of the configuration in the far end.


ImaGroup



Severity: major

272 DN70580522Issue 01A


Id:0900d8058022b8ceConfidential

202097 - Loss of Continuity detected on an ATM VP

195 202097 - Loss of Continuity detected on an ATM VP


195.2 Error DescriptionThe VpCTP or the VpTTP which contains the continuity monitor does not receive the expected continuity check cells from the source.

195.3 Troubleshooting (LMT)Troubleshooting has to start with investigation on other alarms. Therefore, check whether alarms at upstream NEs are present in the ALARM View window of the LMT:1. Click on the “Alarm View” button or use the shortkey Ctrl + A .2. Proceed according to the troubleshooting of the trigger alarm.

If either no such alarm is present or if the actions taken above did not clear the condition for this alarm, perform the following steps in the given order to cease this alarm:1. Confirm that all relevant cables are connected properly.2. If these actions did not help to solve this error, contact the technical assistance



ContinuityMonitor



Severity: minor


273

Troubleshooting Node B 202098 - CRC4 not used by FE reported on E1TTP


196 202098 - CRC4 not used by FE reported on E1TTP


196.2 Error DescriptionA loss of multiframe alignment occurred and the following indication has been received on the reporting E1 physical link: ’CRC4 not used by far end (FE)’.

The ’202098 - CRC4 not used by FE reported on E1TTP’ alarm indicates that no multi-frame synchronization could be found. This may be due to the follwing: • Misconfiguration of the hardware at either end • Faulty hardware at either end • Problems on the transmission medium between the two ends

The "202098 - CRC4 not used by FE Indication on E1 Physical Link" alarm may be caused by the following:

The Node B's E1TTP managed object's attribute crcOperationMode, which indicates the mode of CRC operation, is set to crcAutomatic whereas the frame format for the RNC is set to 0 meaning that the CRC is disabled.

The "202098 - CRC4 not used by FE Indication on E1 Physical Link" does not cause any change of the reporting E1TTP's OST/AVS.



E1TTP



Severity: warning

274 DN70580522Issue 01A


Id:0900d8058022b8daConfidential

202106 - Software activation failed

197 202106 - Software activation failed


197.2 Error DescriptionThe activation of a software load failed in the previous run.

As a consequence, the Node B now automatically switched back to the previously running software load.



Osu



Severity: warning


275

Troubleshooting Node B 202107 - Database activation failed


198 202107 - Database activation failed


198.2 Error DescriptionThe activation of a database failed in the previous run.

As a consequence, the Node B now automatically switched back to the previously running database.



Osu



Severity: warning

276 DN70580522Issue 01A



202108 - Reliable software started without prior explicit activation

199 202108 - Reliable software started without prior explicit activation


199.2 Error DescriptionThe reliable software was started without a prior explicit activation procedure (automatic fallback).

This case occurs due to one of the following situations: • No activation is running and the start-up with the running software failed three times

in a row. • An error occurred in a very early boot phase.



Osu



Severity: warning


277

Troubleshooting Node B 202109 - Reliable database started without prior explic-it activation


200 202109 - Reliable database started without prior explicit activation


200.2 Error DescriptionThe reliable database was started without a prior explicit activation procedure (auto-matic fallback).

This case occurs due to one of the following situations: • No activation is running and the start-up with the reliable database failed three times

in a row. • An error occurred in a very early boot phase.



Osu



Severity: warning

278 DN70580522Issue 01A



202358 - CAN received an unexpected message

201 202358 - CAN received an unexpected message


201.2 Error DescriptionThe Node B CAN communicates with various devices via CAN bus. The Core Controller software verifies the communication scenarios. This fault report will be generated, if the Core Controller software detects an unexpected message in the actual message sce-nario. The affected Node B may continue to operate in a degraded mode.

The probable cause for that condition could either be a hardware failure or a software failure.

201.3 Troubleshooting (LMT)1. Any CAN bus participant may cause the problem. Check all CAN bus participants in

order to isolate the fault.2. First, reset the addressed card. Use the TREE View window of the LMT or, alterna-





Cc


Probable Cause: InvalidMessageReceived

Severity: warning


279

Troubleshooting Node B 202360 - A necessary resource is missed


202 202360 - A necessary resource is missed


202.2 Error DescriptionThe Node B communicates with various devices via a CAN bus. This fault report will be generated, if the Core Controller cannot initialize its local resources. This condition leads to a recovery reset. The affected Node B is therefore temporarily not operational.

The probable cause for that condition could either be a hardware failure or a software failure.

202.3 Troubleshooting (LMT)1. Any CAN bus participant may cause the problem. Check all CAN bus participants in

order to isolate the fault.2. First, reset the addressed card.

Use the TREE View window of the LMT or, alternatively, apply the Cc “reset” command to the addressed card.

3. If the fault cannot be cleared by reset, the addressed card has to be replaced.Replacement must be done according to the “Replacing Node B Units” instructions.



Cc


Probable Cause: UnderlyingRessourceUnavailable

Severity: critical

280 DN70580522Issue 01A


Id:0900d8058022b8feConfidential

202406 - ALCAP protocol error

203 202406 - ALCAP protocol error


203.2 Error DescriptionALCAP (access link control application part) protocol errors are an indication of one of the following conditions:

• Messages are being corrupted over the Iub interface. • Software implementation problems between RNC and Node B. • ALCAP protocol in the RNC has been upgraded to a later version of the specifica-

tion (ITU-T Q.2630.1).



Cc



Severity: warning


281

Troubleshooting Node B 202431 - ALCAP transaction to RNC initiated by trans-port timed out


204 202431 - ALCAP transaction to RNC initiated by transport timed out


204.2 Error DescriptionAn ITR (transport management subsystem) initiated Iub request on ALCAP (access link control application part) has timed out. This means that block request, unblock request or reset request has been requested by ITR and has timed out before a reply has been received from the RNC.

This condition is fairly serious as it can lead to a configuration misalignment between RNC and Node B. This error could either be caused by congestion or a failure in the ALCAP socket between RNC and Node B.



Cc


Probable Cause: Congestion

Severity: warning

282 DN70580522Issue 01A



202432 - ALCAP transaction to RNC initiated by NBAP timed out

205 202432 - ALCAP transaction to RNC initiated by NBAP timed out


205.2 Error DescriptionA CPN (call processing NBAP) initiated Iub request on ALCAP (access link control application part) has timed out. This means that reset request or release request has been requested by CPN and has timed out before a reply has been received from the RNC.

This condition is fairly serious as it can lead to a configuration misalignment between RNC and Node B. This error could either be caused by congestion or a failure in the ALCAP socket between RNC and Node B.



Cc


Probable Cause: Congestion

Severity: warning


283

Troubleshooting Node B 202433 - Configuration misalignment between RNCand CPA


206 202433 - Configuration misalignment between RNC and CPA


206.2 Error DescriptionThis error occurs when RNC sends a message to CPA (call processing ALCAP) to perform an action which is not valid. Such actions include:

• RNC attempts to block a path which is already blocked or does not exist. • RNC attempts to unblock a path which is already unblocked or does not exist. • RNC attempts to reset a path which does not exist. • RNC attempts to release a non-existent connection.

While not a serious problem in itself, these unexpected actions could point to either a software error or a configuration misalignment between RNC and CPA which is serious.



Cc



Severity: warning

284 DN70580522Issue 01A



202434 - RNC Establish Request message received which is invalid or cannot be handled

207 202434 - RNC Establish Request message received which is invalid or cannot be handled


207.2 Error DescriptionThis error indicates that an ALCAP (access link control application part) establish request message has been received from the RNC which is either invalid or cannot be handled.

Possible errors include:

• Establish request for a connection which is destined to be routed to a BB (baseband) card that is not in service (this is an NBAP/BB card problem).

• Establish request which contains an invalid binding ID. • Establish request with an invalid NSEA (NSAP service endpoint address) address

for the Node B. • Establish request which contains unexpected parameters for this implementation. • Establish request for a path which does not exist • Establish request for a channel that is already in use. • Establish request with no TCI (test connection indication) for a path which is locally

blocked.

These either indicate a problem with the RNC or internal subsystems.



Cc



Severity: warning


285

Troubleshooting Node B 202435 - CPA to RNC communication (socket) prob-lems


208 202435 - CPA to RNC communication (socket) problems


208.2 Error DescriptionThis error occurs if data that is about to be sent is lost due to the TNP (transport network protocol) socket between Node B and RNC either being out-of-service or returning error.

This is a serious problem as, if there is no retry mechanism (e.g. for release requests), then configuration misalignment could result between RNC and Node B.

The following subsequent alarm may also be initiated: 200656 - Iub link broke down



Cc



Severity: critical

286 DN70580522Issue 01A



202506 - Node B system clock in holdover mode

209 202506 - Node B system clock in holdover mode


209.2 Error DescriptionThe reference input for the Node B system clock is not available or not stable enough for synchronization. System clock oscillator is running without external synchronization (holdover mode). This may be due to incorrect configuration of the clock management in the Node B database, or due to insufficient signal quality of the reference clock source.

The faults leading to the following alarms make the Node B’s system clock switch to holdover mode: • 202056 – Loss Of Signal on Physical Link • 202057 – Loss Of Frame on Physical Link • 202059 – Alarm Indication Signal on Physical Link • 202062 – Line Alarm Indication Signal Indication on STM1 Physical Link

g In the event of microwave links, the clock quality can be degraded due to either propagation problems or protection switching. As consequence, some other Node Bs in the same connected area may be affected, as well.

209.3 Troubleshooting (LMT)All clock signals in the Node B are derived from an internal high accuracy master clock (OC-VCXO) which is synchronized to a reference clock signal by PLL. This reference clock can be derived from the Iub interface (E1/J1/T1 or STM-1/OC-3) or from an external source connected to the external synchronization input.

With the ClMng managed object in the nbDatabase not only the source for the reference clock can be defined but also the priority order of up to four (4) possible sources can be selected. If the reference clock is lost or is not of sufficient quality the internal clock (OC-VCXO) will still work within 3GPP frequency stability limit of 0.05 ppm for at least two (2) days. The working state is holdover mode – high accuracy, see clockAccuracyStatus parameter.

1. Reference clock lostIf the reference clock is derived from an E1/J1/T1 or STM-1/OC-3 line and the relevant incoming Iub signal is lost or degraded concentrate on fixing the Iub inter-face alarm first as they are:– 202056 - Loss Of Signal on Physical Link


ClMng



Severity: minor


287

Troubleshooting Node B 202506 - Node B system clock in holdover mode


– 202057 - Loss Of Frame on Physical Link– 202070 - Signal Degrade Indication on STM1 Physical Link– 202071 - Excessive Bit Error Rate Indication on STM1 Physical Link

2. Clock management configuration incorrectThe ClMng managed object in the nbDatabase defines the reference clock sources and their priority. The prioClockSourceList parameter of the ClMng managed object contains one to four clock sources. In this priority list, the priority is assigned to the clock sources by the order of the elements in the list. Thus, the first entry has the highest priority.The list has to contain a minimum of one entry and a maximum of four entries. Fur-thermore clock sources must not be duplicated in the list and have to exist.Each entry consists of both a reference to a physical line MO (E1TTP, J1TTP, Stm1TP) via the MO’s FDN and the actual line type of the reference line.Thus, take the following measures:– Upload the nbDatabase

Use the TREE View window of the LMT and apply the Osu “uploadDataInitiate” command to the relevant Osu managed object.

– Check for right configuration of ports and line types within the ClMng managed object as well as the stm1Port and lineCircuitAddress parameters of the trans-port-related MOCs, Stm1TP and E1TTP/J1TTP, respectively. For details, consult the OGL:Node B DB Description.

3. Reference signal quality insufficientFor further investigation, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

288 DN70580522Issue 01A


Id:0900d805806e6c6cConfidential

202507 - Node B system clock in medium accuracy

210 202507 - Node B system clock in medium accuracy


210.2 Error DescriptionThe accuracy of the Node B system clock is in medium accuracy range. This may be due to insufficient signal quality of the reference clock source.

The following preceded alarm should have been reported: 202506 - Node B system clock in holdover mode

210.3 Troubleshooting (LMT)All clock signals in the Node B are derived from an internal high accuracy master clock (OC-VCXO) which is synchronized to a reference clock signal by PLL. This reference clock can be derived from the Iub interface (E1/J1/T1 or STM-1/OC-3) or from an external source connected to the external synchronization input.

With the ClMng managed object in the nbDatabase not only the source for the reference clock can be defined but also the priority order of up to four (4) possible sources can be selected. If the reference clock is lost or is not of sufficient quality the internal clock (OC-VCXO) will first change to the working state holdover mode – high accuracy, see clockAccuracyStatus parameter. But if the bad synchronization remains for up to two (2) days, the Node B will go from holdover mode – high accuracy to holdover mode – medium accuracy. In this case, the frequency stability can only be guaranteed for a few days and after this period there is a possibility that the Node B will transmit outside 0.05 ppm.

1. Reference clock lostIf the reference clock is derived from an E1/J1/T1 or STM-1/OC-3 line and the relevant incoming Iub signal is lost or degraded concentrate on fixing the Iub inter-face alarm first as they are:– 202056 - Loss Of Signal on Physical Link– 202057 - Loss Of Frame on Physical Link– 202070 - Signal Degrade Indication on STM1 Physical Link– 202071 - Excessive Bit Error Rate Indication on STM1 Physical Link

2. Clock management configuration incorrectThe ClMng managed object in the nbDatabase defines the reference clock sources and their priority. The prioClockSourceList parameter of the ClMng managed object contains one to four clock sources. In this priority list, the priority is assigned to the


ClMng



Severity: minor


289

Troubleshooting Node B 202507 - Node B system clock in medium accuracy

Id:0900d805806e6c6cConfidential

clock sources by the order of the elements in the list. Thus, the first entry has the highest priority.The list has to contain a minimum of one entry and a maximum of four entries. Fur-thermore clock sources must not be duplicated in the list and have to exist.Each entry consists of both a reference to a physical line MO (E1TTP, J1TTP, Stm1TP) via the MO’s FDN and the actual line type of the reference line.Thus, take the following measures:– Upload the nbDatabase

Use the TREE View window of the LMT and apply the Osu “uploadDataInitiate” command to the relevant Osu managed object.

– Check for right configuration of ports and line types within the ClMng managed object as well as the stm1Port and lineCircuitAddress parameters of the trans-port-related MOCs, Stm1TP and E1TTP/J1TTP, respectively. For details, consult the OGL:Node B DB Description.

3. Reference signal quality insufficientFor further investigation, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in “Collect Info for Assistance”. Log files need to be analyzed and specific measures must be taken which are out of the operator’s scope.

290 DN70580522Issue 01A



262041 - System call unsuccessful

211 262041 - System call unsuccessful


211.2 Error DescriptionA system call was not successful. As a consequence, the CC (Core Controller) will be reset, because the software is not capable of working stable any longer. The problem has to be analyzed by the customer service.



*


Probable Cause: SystemCallUnsuccessful

Severity: critical


291

Troubleshooting Node B 262042 - Unexpected software error


212 262042 - Unexpected software error


212.2 Error DescriptionAn unexpected software error occurred. As a consequence, the CC (Core Controller) will be reset, because the software is not capable of working stable any longer. The problem has to be analyzed by the customer service.



*



Severity: critical

292 DN70580522Issue 01A



262043 - Error from device driver received

213 262043 - Error from device driver received


213.2 Error DescriptionA function call to a device driver returned an error. In most of the cases the CC (Core Controller) will be reset as a consequence. The problem has to be analyzed by the customer service.



*



Severity: critical


293

Troubleshooting Node B 262044 - Not enough memory to initialize software


214 262044 - Not enough memory to initialize software


214.2 Error DescriptionAt start-up time the OS (operating system) could not allocate enough memory for task stacks, message buffers and dynamic memory management etc.. The problem has to be analyzed by the customer service.



Cc


Probable Cause: OutOfMemory

Severity: critical

294 DN70580522Issue 01A



262045 - Memory allocation failure

215 262045 - Memory allocation failure


215.2 Error DescriptionThe system did not have enough free memory to satisfy a memory allocation request. As a consequence, the CC (Core Controller) will be reset. The problem has to be analyzed by the customer service.



*


Probable Cause: OutOfMemory

Severity: critical


295

Troubleshooting Node B 262046 - Unexpected exception handling


216 262046 - Unexpected exception handling


216.2 Error DescriptionAn unexpected exception was thrown. As a consequence, the CC (Core Controller) will be reset, because the software is not capable of working stable any longer. The problem has to be analyzed by the customer service.



*



Severity: critical

296 DN70580522Issue 01A



262047 - Uncaught exception handling

217 262047 - Uncaught exception handling


217.2 Error DescriptionA thrown exception was not caught. As a consequence, the CC (Core Controller) will be reset, because the software is not capable of working stable any longer. The problem has to be analyzed by the customer service.



*



Severity: critical


297

Troubleshooting Node B Appendix


218 AppendixThis appendix contains information about the following topics: • Fault management in the NB/RSxxx • Mapping of NB/RSxxx alarms to NetAct alarms

218.1 Fault management in the NB/RSxxxThe fault management (FM) function implemented in the NB/RSxxx manages abnormal behavior of the NB/RSxxx, caused by faults. Faults are events which cause the NB/RSxxx to perform in a way that is different from the normal one. They are detected through errors in the operation of the NB/RSxxx and are then reported to users in various ways (LED status on cards and modules, alarms, etc.).

Failures and faults occurring in the NB/RSxxx may cause deterioration of the NB/RSxxx’s function and/or quality of service (QoS). In severe cases, this decay can lead to situations in which the NB/RSxxx is completely unavailable.

The NB/RSxxx’s fault management provides means to minimize the failures’ effects on the QoS perceived by network users. In general, fault management comprises the fol-lowing functions: • Monitoring the system • Detecting faults • Isolating faults • Generating event reports

The term ’event reports’ includes both failure event reports (FERs) and state change event reports (SCERs).

• Sending event reports to the NB/RSxxx’s local maintenance terminal (LMT) and to the connected OMC-B, such as the Radio Commander (RC)From there, alarms with severities minor, major, and critical are forwarded to NetAct via Itf-N. Major and critical alarms are mapped to dedicated NetAct alarms.

• Localizing faults • Correcting faults

The NB/RSxxx furthermore provides a common log for all failure event reports (FERs) and a log record per each FER. The alarm log is stored in a reset-safe storage area in the NB/RSxxx, i.e. the log will be kept upon NB/RSxxx restarts but not upon power-off, see “Alarm handling after NB/RSxxx reset”. For details about uploading these log files, refer to the “Using Node B Service Terminal” guideline. Additionally, the NB/RSxxx a list containing the NB/RSxxx’s active alarms of severities minor, major, and critical. In contrast to the alarm log, however, this list is neither kept upon NB/RSxxx restarts nor does it contain any alarm history.

The NB/RSxxx can only provide these functions and perform accurate remote fault analysis if it is synchronized with other elements of the UTRAN from operation, admin-istration, and maintenance (OAM) point of view. For an overview on the vendor’s OAM concept, refer to the “WCDMA RAN System Overview”, chapter “Network management architecture”.

298 DN70580522Issue 01A



Appendix

With regard to operation and maintenance (O&M) aspects, the NB/RSxxx’s fault man-agement function supports the following two separate parts: • Implementation-specific operation and maintenance

Implementation-specific O&M functions are functions which are actually imple-mented in the NB/RSxxx. They heavily depend both on the NB/RSxxx’s hardware components and on managing its software parts.Within this “Appendix”, section “Generating an alarm” describes the general handling of faults which are subject to implementation-specific O&M.

• Logical operation and maintenanceLogical O&M is the signaling associated with the control of logical resources, such as channels or cells. The RNC owns and controls these resources although they are physically implemented in the NB/RSxxx. Information is thus exchanged between the NB/RSxxx and the RNC via NBAP messages.In the event of a failure in the logical O&M part, the RNC sends a related alarm to the OAM management system (OMC-R). Failures related to logical O&M are:– Cell inoperable– Local cell not available– Downlink common channel (FACH) inoperable– Downlink common channel (PCH) inoperable– Downlink common channel (PCH/FACH) inoperable– Uplink common channel inoperable– HSDPA channel inoperable– HSUPA channel inoperable

g The present troubleshooting manual deals with implementation-specific O&M only.

Generating an alarmThe purpose of generating an alarm is to alert operators about failures which need to be corrected. Alerting operators is done by sending a failure event report to the manage-ment system (LMT/OMC-B). An entry in the NB/RSxxx’s log file is furthermore created.

If a failure occurs in the implementation-specific O&M part of the NB/RSxxx, fault man-agement processes as follows: • Sending failure event reports to the LMT/OMC-B

The NB/RSxxx sends only those reports which contain useful information. In the fol-lowing cases, fault management therefore suppresses reports: failures that are cleared immediately afterwards and reports that would repeat the same information over and over again.

• Sending both failure event reports and state change event reportsFor failures which also change the defective managed object’s (MO) alarm status (ALS) or other state attributes, fault management also sends state change event reports. State change event reports are sent in the event of changes to the opera-tional state (OST), availability status (AVS), and standby status (SBS).

• Logging the alarm event report in a history log in the NB/RSxxx • Storing the alarm event report in the list of active alarms in the NB/RSxxx

This task is done only for new alarm conditions, i.e. only once per alarm. • Running automatic recovery procedures

Examples are provided in section “Equipment fault management”.


299



Alarm handling after NB/RSxxx resetIn the event of a NB/RSxxx reset, the software cannot guarantee that the failure event report (FER) describing the reason for the reset is reliably sent to the management system. One reason for not sending the FER may be that the connection is already broken. The concept of “last error handling” therefore assures that the reason for the reset is always sent to the management system as soon as the NB/RSxxx will have recovered from the reset.

The last error, containing the main part of the FER, is thus persistently stored (“power-off safe”) in critical situations. Such situations comprise fatal faults and when forwarding the FER to the management system cannot be guaranteed. After NB/RSxxx restart and end of the alignment procedures, the software NB/RSxxx’s fault management applica-tion forwards the FER containing the last error to the management system.

The severity of this corresponding alarm will be warning only because • The fault occurred in the past. • The alarm cannot be cleared in the currently-running NB/RSxxx. • The reason for the reset, i.e. the fault, may no longer exist after the reset.

g NOTE: It may be possible that the alarm is output twice: first, immediately before the NB/RSxxx reset with originally-defined severity (such as critical or major) and then again after NB/RSxxx restart and alignment with severity warning.

Solving and clearing an alarmAlarms which have been raised in consequence of faults have to be solved. Repairing and removing the corresponding fault thus is essential to clear the alarm. The fault clear-ance procedure depends on the actual alarm. In general, however, the following princi-ple differentiation can be made, depending on the type of fault: • Equipment faults are repaired by replacing the defective units with working ones. • Software faults are repaired by means of software patches, database update, or

update of the software load. • Communication faults are cleared by

– Replacing the defective equipment (link interface, etc.)– Removing the cause of noise if this was the reason for raising the alarm

• Quality of service (QoS) alarms are cleared by– Removing the causes that degraded the QoS– Improving the system’s capability to react upon the causes that could result in a

degradation of the QoS • Environmental problems are solved by removing the bad environmental conditions

which led to the relevant alarm, such as high temperature or humidity.

Alarm treatment starts usually at the NetAct or Radio Commander (RC). RC trouble-shooting typically involves: selecting an alarm message from the alarm list that is dis-played on the RC screen and pressing F1 to lead to a troubleshooting procedure that can be carried out remotely from RC. This procedure may solve the fault or gather more symptoms. If it is not possible to solve the fault from RC, the NE documents have to be used to eliminate the fault on site.

300 DN70580522Issue 01A



Appendix

This complete troubleshooting procedure is explained in the following figure for a NB/RSxxx fault.

For on-site fault clearance, the error ID of the network element is the starting point. By means of this information the troubleshooting procedure can be found in the trouble-shooting manual (“Troubleshooting Node B”). If necessary a link will be given to the maintenance manual (“Replacing Node B Units”) for a module changing procedure.

As soon has the alarm cause is cleared, fault management sends an alarm event report with perceived severity cleared to the LMT/OMC-B. As a result, the corresponding active alarm (severity minor, major, or critical) is deleted from the NB/RSxxx’s list of active alarms and from the related list in the OMC-B, such as the Radio Commander (RC). Alarms of severity warning are not affected.

218.1.1 Equipment fault managementWhen a fault occurs in a card/module, the NB/RSxxx’s core controller (CC) card typically forces a reset of the alarmed card/module for quick recovery.

In the event of hardware failure, the following general fault detection and recovery actions are taken:1. Sending event reports

– Failure event reports and state change event reports are sent to the LMT/OMC-B.

– Resource status indications are sent to the RNC via NBAP signaling.2. Starting an automatic recovery procedure


301



– Redundancy switch: when a failure occurs on an active card, the card in standby mode becomes active and takes over the defective card’s operation. For more details on hardware redundancy, refer to section “NB/RSxxx hardware redundancy concept”.

– Resource switch for maintaining calls and Iub link changing: When one card fails, the other cards perform the tasks of the defective one in a load-sharing configuration.

– Automatic reset: Executing the reset of a card reinitialzes the card and clears the alarm. The latter, however, applies only for a subset of alarms whereas for others, the reset does not clear the alarm condition.

3. Handling cells which are down– The NB/RSxxx stops transmission of the amplifier (such as LPA, CAT, RRH).– The affected calls are released.

NB/RSxxx hardware redundancy conceptTo prevent interruptions of operation and assure maximum system reliability, redun-dancy concepts are incorporated in the hardware configuration of the NB/RSxxx. The following redundancy concepts exist, although not each concept may be available for all types of NB/RSxxx: • N/E redundancy

The N/E card redundancy concept uses two units. One of them is active while the other one remains in standby mode. The standby card becomes only active in the event of a failure in the active card.

• Load-sharing redundancyMore than one card/module is used in the system, depending on traffic, capacity, and power. All cards are active in parallel. The failure of one card may decrease the performance of the functionality. There is no total loss, however.

• N+1 redundancyIn the N+1 card redundancy concept, N+1 units are active while only N cards are necessary to perform the full functionality. All cards are equal.

• Diversity configuration (no redundancy)Only one card or module operates in the system, i.e. there is no redundancy. One path of this card/module has diversity configuration. A failure in one of the diversity paths decreases the performance. Services, however, are maintained.

The possible redundancy configuration depends on the actual platform which is used: • For NB-420, refer to the “NB-420 Product Description”. • For NB-440 and NB-441, refer to the “NB-440/NB-441 Product Description”. • For NB-860 or NB-861, refer to the “NB-860/NB-861 Product Description”. • For NB-880 and NB-881, refer to the “NB-880/NB-881 Product Description”. • For RSSU-380, refer to the “RSSU-380/RRHs Product Description”. • For RS-381, refer to the “RS-381/RRHs Product Description”. • For RS-880, refer to the “RS-880/RRHs Product Description”.

218.1.2 Transport network fault managementThis section deals with the fault and alarm management for the NB/RSxxx’s transport network domain.

Atomic functions in the fault management detect failure indications (anomalies) which, in turn, are input signals for the alarm management. The failure indications are routed

302 DN70580522Issue 01A



Appendix

through internal filters of the NB/RSxxx. These filters process the anomalies, add infor-mation, and generate appropriate alarms. Alarm management correlates relevant alarms and propagates alarms to the management system.

Fault and alarm management at the NB/RSxxx’s transport domain distinguishes between three basic indications and monitors them. The indications’ definitions are in accordance with “Bellcore GR-1248-CORE, Section 6.1“: • Anomaly (CRC error, OOF, out of cell delineation, etc.)

Anomalies are discrepancies between the current and the desired characteristics of an item. Normally, anomalies are determined by means of one or more detectable events. An anomaly is the first indicator for trouble in the network. If the density of anomalies is sufficiently high enough for a small fraction of a second, fault manage-ment declares a defect.

• Defect (LOS, LOF, etc.)Defects are limited interruptions in an item’s ability of performing the required func-tion. The item’s decrease of performance is caused by successive anomalies which are considered as a defect.When a defect is declared, fault management takes the following measures:– Generation of inband indications, such as AIS and RDI– Fault propagation to the upper layer

• Failure (AIS, RDI, etc.)Failures are defined as the termination of an item’s ability of performing the required function. When a defect was detected and has persisted for a certain time, fault management declares a failure and generates an alarm.

Alarm correlation at the transport network layer (TNL)

g NOTE: Alarm correlation applies for only one NB/RSxxx but not for various NB/RSxxxs which are monitored by one specific network management system such as the RC.

Four sub-features (filters) of the NB/RSxxx’s transport network alarm management take care of keeping the number of alarms sent to the LMT or OMC-B as low as possible. • Fault persistency

The NB/RSxxx’s TNL fault management checks whether defects, which cause alarms, remain present. On the one hand, if a fault cause continuously lasts for a certain time, fault management declares a defect. On the other hand, if a fault cause is absent for a certain time, fault management clears the defect.The fault persistency thus allows only continuous defects being propagated to the LMT/OMC-B.

• Fault priorizationAll defects at the transport network layer (TNL) have determined priorities. Alarm management reports only the defect with the highest priority but not defects which occur only in consequence to this defect.Fault priorization thus reduces the number of alarms which provide only redundant information and/or are caused by defects with higher priority.


303



• Fault propagationDefects occurring at lower layers are propagated to upper layers to initiate conse-quent actions at the higher layer. These actions include AIS and RDI insertion.Fault propagation thus provides information about defects at the respective lower layer’s resources to all transport network layers. As a consequence, upper layers retrieve information when their own services could become degraded.The propagation is also helpful for operators with regard to failure cause analysis.

• State propagationAs a consequence of the fault propagation, fault and alarm management also promotes the state information to the upper layer and to higher applications.State propagation thus provides means for the operator to verify the layer which is degraded and the corresponding layers which are also affected.

Benefits of the alarm correlationThe alarm correlation at the transport network layer drastically reduces the amount of alarm notifications at the Itf-B. This is achieved by alarming only these defects which contain useful information. Fault and alarm management suppresses all other defects which are caused by the initial defect, however.

As a consequence, operators get a better overview of the basic failure cause and can take troubleshooting tasks much quicker. Furthermore, the load of the transmission network and of the management system (LMT/OMC-B) is reduced.

304 DN70580522Issue 01A



Appendix

218.2 Mapping of NB/RSxxx alarms to NetAct alarmsIn the present release, alarms generated by the NB/RSxxx are also forwarded from the RC to NetAct via the Itf-N. Table 1 shows the mapping of the NB/RSxxx alarms to cor-responding NetAct alarms.

NetAct alarm(<ID> – <Name>)

NB/RSxxx alarm(<ID> – <Name>)

92001 – THIS IS A NODEB2 ALARM 200658 – Transmit bandwidth limit for NBAP reached

200659 – Core Controller overload protection activated

200905 – VSWR alarm Low

200907 – RX alarm Low

200909 – TMA switched off, but not defective.

200910 – TMA feeder alarm

200911 – TMA DC alarm

200915 – Site input alarm detected

200916 – Rack Door open

200920 – High temperature of PA

200924 – Input power level of LPA too high but LPA can still hold its RF specification

200986 – Temperature out of range in upper direction

200994 – Hardware Failure

200997 – Lower Temperature Limit (Ht0) reached

200998 – Temperature out of range in lower direction

201001 – RET power off

201002 – RET feeder alarm

201003 – RET hardware alarm

201004 – ALD communication error

201005 – RET is not calibrated

201006 – RET is not scaled

201007 – RET lost position

201008 – RET received wrong configuration data

201016 – Non-fatal internal LVDS failure

201017 – Digital input power level too high, but gain reduced

Table 1 Mapping of NB/RSxxx alarms to NetAct alarms


305



92001 – THIS IS A NODEB2 ALARM 201020 – Loss of single DRIF interface detected

201022 – Alignment of file data has failed

201023 – Bad signal quality of single DRIF interface detected

201029 – MEF blocked

201031 – Wrong combination of licensed cards.

201032 – Not all cells are licensed.

201033 – PID could not be read or is corrupted – non-fatal

201036 – RRHs unable to establish communication links with the expected number of PSRs.

201037 – ALD unspecified error

201038 – Resource conflict between CP and OAM

201041 – Test channels have been lost

201044 – Non fatal configuration failure

202007 – A scanner could not be initialised

202008 – The temporary measurement results could not be stored

202009 – Unable to request measurement results

202010 – The ScanCo could not be initialised

202011 – The final results files could not be generated

202068 – Signal Label Mismatch Indication on STM1 Physical Link

202070 – Signal Degrade Indication on STM1 Physical Link

202072 – Alarm Indication Signal on an ATM VC

202073 – Remote Defect Indication on an ATM VC

202075 – Alarm Indication Signal on an ATM VP

202076 – Remote Defect Indication on an ATM VP

202078 – Loss Of Delay Synchronisation on IMA Link

202079 – Loss Of IMA Frame on IMA Link



Table 1 Mapping of NB/RSxxx alarms to NetAct alarms (Cont.)

306 DN70580522Issue 01A



Appendix

92001 – THIS IS A NODEB2 ALARM 202080 – Remote Failure Indicator on IMA Link

202081 – IMA Tx link is detected as mis-connected

202082 – IMA Rx link is detected as mis-connected

202083 – Tx fault declared at the NE on IMA Link

202084 – Rx fault declared at the NE on IMA Link

202085 – FE has reported Tx-Unusable on IMA Link

202086 – FE has reported Rx-Unusable on IMA Link

202097 – Loss of Continuity detected on an ATM VP

202110 – A file upload is pending

202506 – NodeB system clock in holdover mode

202507 – NodeB system clock in medium accuracy

92002 – THIS IS A NODEB2 ALARM 200707 – A warning occurred in the nbDatabase

200944 – FTP put failed

200945 – FTP manage failure

200949 – Internal CORBA call failed

200953 – CAN bus off

200980 – Invalid MO

200981 – MO not mounted

200982 – Invalid command

200983 – Invalid parameter in command

200984 – Firmware download access file error

200985 – CAN transaction error

200987 – Hardware parameter invalid

200988 – Response unknown

201009 – A mounted card is not used to its full capacity

201014 – Standby CC forced to become active due to unreachable active CC.

201015 – Preparation of data to be aligned has failed

201030 – Invalid hardware capacity licensing value.

201048 – Non fatal BB software failure

201049 – Non fatal DSP failure





307



92002 – THIS IS A NODEB2 ALARM 202074 – SSCOP Failure Indication on an ATM VC used by ALCAP or NBAP

202098 – CRC4 not used by FE reported on E1TTP

202106 – Software activation failed

202107 – Database activation failed

202108 – Reliable software started without prior explicit activation

202109 – Reliable database started without prior explicit activation

202358 – CAN received an unexpected message

202406 – ALCAP protocol error

202431 – ALCAP transaction to RNC initiated by trans-port timed out

202432 – ALCAP transaction to RNC initiated by NBAP timed out

202433 – Configuration misalignment between RNC and CPA

202434 – RNC Establish Request message received which is invalid or cannot be handled




308 DN70580522Issue 01A



Appendix

92003 – THIS IS A NODEB2 ALARM 202014 – The first sccpchUsageRatio Quality of Service alarm has occurred

202015 – The second sccpchUsageRatio Quality of Service alarm has occurred

202016 – The first prachUsageRatio Quality of Service alarm has occurred

202017 – The second prachUsageRatio Quality of Service alarm has occurred

202018 – The first cpUsageRatio Quality of Service alarm has occurred

202019 – The second cpUsageRatio Quality of Service alarm has occurred

202020 – The first prachCrciFailures Quality of Service alarm has occurred

202021 – The second prachCrciFailures Quality of Service alarm has occurred

202022 – The first bbUsageRatioLicense Quality of Service alarm has occurred

202023 – The second bbUsageRatioLicense Quality of Service alarm has occurred

202024 – The first bbUsageRatioHw Quality of Service alarm has occurred

202025 – The second bbUsageRatioHw Quality of Service alarm has occurred

202026 – The first e1Crc Quality of Service alarm has occurred

202027 – The second e1Crc Quality of Service alarm has occurred

202028 – The first vcUsageRatio Quality of Service alarm has occurred

202029 – The second vcUsageRatio Quality of Service alarm has occurred

92004 – NODEB SYSTEM START-UP MALFUNC-TION DUE TO SOFTWARE/HARDWARE PROBLEM

200506 – NodeB system start-up malfunction due to software/hardware problem

92005 – SYSTEM HALT DUE TO SOFTWARE WATCHDOG DETECTED PROBLEM

200507 – System halt due to software watchdog detected problem

92006 – SYSTEM HALT DUE TO DETECTED APPLI-CATION PROCESS ERROR

200508 – System halt due to detected application process error





309



92007 – SYSTEM HALT DUE TO DETECTED HARDWARE EXCEPTION

200509 – System halt due to detected hardware exception

92008 – SYSTEM HALT DUE TO DETECTED SOFTWARE LOADING MALFUNCTION

200510 – System halt due to detected software loading malfunction

92009 – IUB LINK BROKE DOWN 200656 – Iub link broke down

92010 – SSCOP SEND OVERRUN 200657 – SSCOP send overrun

92011 – AN ERROR OCCURRED IN THE NBDATA-BASE

200706 – An error occurred in the nbDatabase

92012 – VSWR ALARM HIGH 200906 – VSWR alarm High

92013 – RX ALARM HIGH 200908 – RX alarm High

92014 – FAN UNIT FAILED 200914 – Fan unit failed

92015 – PA COMBINER INTERFACE FAULT 200918 – PA combiner interface fault

92016 – FAILURE IN THE DC SUPPLY OF PA 200919 – Failure in the DC supply of PA

92017 – OVER TEMPERATURE OF PA 200921 – Over temperature of PA

92018 – RF PERFORMANCE NOT BEING MET DUE TO BAD LINEARISATION

200922 – RF performance not being met due to bad lin-earisation

92019 – INTERNAL FAILURE OF PA DETECTED 200923 – Internal failure of PA detected

92020 – INPUT POWER LEVEL OF PA TOO HIGH 200925 – Input power level of PA too high

92021 – CPU FAILURE OF BASEBAND CARD 200926 – CPU failure of baseband card

92022 – VOLATILE MEMORY FAILURE OF BASEBAND CARD

200927 – Volatile memory failure of baseband card

92023 – NON-VOLATILE MEMORY FAILURE OF BASEBAND CARD

200928 – Non-volatile memory failure of baseband card

92024 – DSP FAILURE 200929 – DSP failure

92025 – FPGA FAILURE 200931 – FPGA failure

92026 – CONTROL FPGA FAILURE 200932 – Control FPGA failure

92027 – EXTERNAL TIMING SIGNAL FAILURE 200933 – External timing signal failure

92028 – FAILURE OF THE RF PART OF THE TRX 200934 – Failure of the RF part of the TRX

92029 – LVDS FAILURE 200935 – LVDS Failure

92030 – LOCAL BUS FAILURE AROUND THE CPU 200936 – Local bus failure around the CPU

92031 – FTP CONNECTION FAILURE 200937 – FTP connection failure

92032 – CRC ERROR DURING SOFTWARE IMAGE CHECK

200938 – CRC error during software image check

92033 – STATIC CONFIGURATION FILE CRC CHECK FAILED

200939 – Static configuration file CRC check failed




310 DN70580522Issue 01A



Appendix

92034 – SOFTWARE ACTIVATION FAILED 200940 – Software activation failed

92035 – INTERNAL CLOCK FAILURE 200941 – Internal clock failure

92036 – CONFIGURATION FILE INCONSISTENT 200942 – Configuration file inconsistent

92037 – IOR FILE INCONSISTENT 200943 – IOR file inconsistent

92038 – STILL ALIVE SUPERVISION FAILURE 200946 – Still alive supervision failure

92039 – FAILURE IN THE DC SUPPLY OF DUAMCO 200947 – Failure in the DC supply of DUAMCO

92040 – CORBA COMMUNICATION FAILED 200948 – CORBA communication failed

92041 – TIMEOUT FOR REQUEST OR MODIFICA-TION

200950 – Timeout for request or modification

92042 – STATUS NOTIFICATION UNDEFINED 200951 – Status notification undefined

92043 – MAXIMUM NUMBER OF RESETS EXCEEDED

200952 – Maximum number of resets exceeded

92044 – NO MESSAGE RESPONSE ON CAN 200954 – No message response on CAN

92045 – MOUNT SUPERVISION FAILURE 200955 – Mount supervision failure

92046 – WATCH DOG TIMER EXPIRED 200956 – Watch dog timer expired

92047 – INTERNAL CAN PROCESSING FAILURE 200957 – Internal CAN processing failure

92048 – TIMER FOR THE RESET SUPERVISION EXPIRED

200958 – Timer for the reset supervision expired

92049 – MISSING RESPONSE FROM BASEBAND CARD

200959 – Missing response from baseband card

92050 – INVALID RESPONSE FROM BASEBAND CARD

200960 – Invalid response from baseband card

92051 – FIRMWARE DOWNLOAD FAILURE 200961 – Firmware download failure

92052 – NO CORBA PROXY AVAILABLE FOR LRU 200989 – No CORBA proxy available for LRU

92053 – NO STILL ALIVE RESPONSE FROM LRU 200990 – No still alive response from LRU

92054 – DUPLEX ERROR 200991 – Duplex error

92055 – SOFTWARE ERROR 200992 – Software error

92056 – UNEXPECTED ALARM STATUS BIT 200993 – Unexpected alarm status bit

92057 – HIGH TEMPERATURE LIMIT (HT3) REACHED

200995 – High Temperature Limit (Ht3) reached

92058 – CRITICAL TEMPERATURE LIMIT (HT4) REACHED

200996 – Critical Temperature Limit (Ht4) reached

92059 – UNEXPECTED LOSS OF UNLOCKED LRU 200999 – Unexpected loss of unlocked LRU

92060 – AN INCOMPATIBLE CARD IS MOUNTED 201010 – An incompatible card is mounted

92061 – ALIGNMENT OF STANDBY CC FAILED 201011 – Alignment of standby CC failed





311



92062 – TIMEOUT FOR CONNECTION TO STANDBY CC

201012 – Timeout for connection to standby CC.

92063 – CONNECTION FAILURE TO STANDBY CC 201013 – Connection failure to standby CC.

92064 – THE LRU COULD NOT PROCESS A MESSAGE FROM CC

201018 – The LRU could not process a message from CC

92065 – GAIN BELOW THRESHOLD 201019 – Gain below threshold

92066 – BAD SIGNAL QUALITY OF ALL DRIF INTER-FACES DETECTED

201024 – Bad signal quality of all DRIF interfaces detected

92067 – PID COULD NOT BE READ OR IS COR-RUPTED

201025 – PID could not be read or is corrupted

92068 – LRU SENT ILLEGAL PARAMETER 201026 – LRU sent illegal parameter

92069 – LRU COULD NOT PROCESS A MESSAGE FROM CC CONTAINING DATA FROM DB

201027 – LRU could not process a message from CC containing data from DB

92070 – NODEB SYSTEM CLOCK HARDWARE FAILURE

201028 – NodeB system clock hardware failure

92071 – BOOSTERS FAN UNIT FAILED 201034 – Boosters Fan unit failed

92072 – MEF COMPLETELY BLOCKED 201035 – MEF completely blocked

92073 – INCONSISTENCY BETWEEN HARDWARE LICENSE AND CONFIGURATION

201039 – Inconsistency between hardware license and configuration.

92074 – WRONG CABLING OF LRU DETECTED 201040 – Wrong cabling of LRU detected.

92075 – INCOMPATIBLE FIRMWARE 201042 – Incompatible Firmware

92076 – MISSING SOFTWARE IMAGE 201043 – Missing software image

92077 – FATAL HARDWARE FAILURE 201045 – Fatal hardware failure

92078 – NO ATM CONNECTION FOR OAM AUTO-CONFIGURATION

201046 – No ATM connection for OAM Autoconfigura-tion

92079 – FATAL BB SOFTWARE FAILURE 201047 – Fatal BB software failure

92080 – LOSS OF SIGNAL ON PHYSICAL LINK 202056 – Loss Of Signal on Physical Link

92081 – LOSS OF FRAME ON PHYSICAL LINK 202057 – Loss Of Frame on Physical Link

92082 – LOSS OF CELL DELINEATION ON PHYSICAL LINK

202058 – Loss Of Cell Delineation on Physical Link

92083 – ALARM INDICATION SIGNAL ON PHYSICAL LINK

202059 – Alarm Indication Signal on Physical Link

92084 – REMOTE ALARM INDICATION ON PHYSICAL LINK

202060 – Remote Alarm Indication on Physical Link

92085 – LOSS OF MULTIFRAME ALARM INDICA-TION ON E1 PHYSICAL LINK

202061 – Loss Of MultiFrame Alarm Indication on E1 Physical Link




312 DN70580522Issue 01A



Appendix

92086 – LINE ALARM INDICATION SIGNAL INDICA-TION ON STM1 PHYSICAL LINK

202062 – Line Alarm Indication Signal Indication on STM1 Physical Link

92087 – LINE REMOTE DEFECT INDICATION ON STM1 PHYSICAL LINK

202063 – Line Remote Defect Indication on STM1 Physical Link

92088 – PATH LOSS OF POINTER INDICATION ON STM1 PHYSICAL LINK

202064 – Path Loss Of Pointer Indication on STM1 Physical Link

92089 – PATH ALARM INDICATION SIGNAL ON STM1 PHYSICAL LINK

202065 – Path Alarm Indication Signal on STM1 Physical Link

92090 – PATH REMOTE DEFECT INDICATION ON STM1 PHYSICAL LINK

202066 – Path Remote Defect Indication on STM1 Physical Link

92091 – EXCESSIVE BIT ERROR RATE INDICATION ON STM1 PHYSICAL LINK

202071 – Excessive Bit Error Rate Indication on STM1 Physical Link

92092 – ALCAP PVC OUT OF SERVICE INDICATION 202077 – ALCAP PVC Out Of Service Indication

92093 – STARTUP FE REPORTED ON IMA GROUP 202087 – Startup FE reported on IMA Group

92094 – CONFIG ABORT REPORTED ON IMA GROUP

202088 – Config Abort reported on IMA Group

92095 – CONFIG ABORT FE REPORTED ON IMA GROUP

202089 – Config Abort FE reported on IMA Group

92096 – INSUFFICIENT LINKS REPORTED AT NE ON IMA GROUP

202090 – Insufficient Links reported at NE on IMA Group

92097 – INSUFFICIENT LINKS AT FE REPORTED ON IMA GROUP

202091 – Insufficient Links at FE reported on IMA Group

92098 – GROUP BLOCKED AT FE REPORTED ON IMA GROUP

202092 – Group Blocked at FE reported on IMA Group

92099 – TIMING SYNCH ERROR REPORTED ON IMA GROUP

202093 – Timing Synch error reported on IMA Group

92100 – THE NEAR END IMA HAS DETECTED AN INVALID VERSION SET BY THE FAR END

202095 – The Near End IMA has detected an invalid version set by the Far End

92104 – A NECESSARY RESOURCE IS MISSED 202360 – A necessary resource is missed

92105 – CPA TO RNC COMMUNICATION (SOCKET) PROBLEMS

202435 – CPA to RNC communication (socket) problems

92106 – SYSTEM CALL UNSUCCESSFUL 262041 – System call unsuccessful

92107 – UNEXPECTED SOFTWARE ERROR 262042 – Unexpected software error

92108 – ERROR FROM DEVICE DRIVER RECEIVED 262043 – Error from device driver received

92109 – NOT ENOUGH MEMORY TO INITIALIZE SOFTWARE

262044 – Not enough memory to initialize software

92110 – MEMORY ALLOCATION FAILURE 262045 – Memory allocation failure





313



92111 – UNEXPECTED EXCEPTION HANDLING 262046 – Unexpected exception handling

92112 – UNCAUGHT EXCEPTION HANDLING 262047 – Uncaught exception handling




ned 3

Documents