alm fleximrlbts faults

Nokia Siemens Networks LTE Radio Access, Rel. RL20, Operating Documentation, Issue 02

Flexi Multiradio Base Station LTE Faults

DN0980455

Issue 02AApproval Date 2011-03-25

Confidential

2 DN0980455Issue 02A


Id:0900d80580863d12Confidential

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 2011. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

DN0980455 3



Table of contentsThis document has 104 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Overview of Flexi Multiradio BTS LTE Faults . . . . . . . . . . . . . . . . . . . . . 9

2 Flexi Multiradio BTS LTE fault and alarm handling . . . . . . . . . . . . . . . . 10

3 BTS fault table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4 Flexi Multiradio BTS LTE faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.1 61006 The FTM booted at $date due to $RCause . . . . . . . . . . . . . . . . 134.2 61010 BTS reset required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144.3 61028 LOF on unit $U, interface $IF . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.4 61029 LOS on unit $U, [ethernet] interface $IF . . . . . . . . . . . . . . . . . . . 164.5 61030 Dead Peer Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174.6 61050 Missing or non-compliant SFP module on unit $U, interface $I . 184.7 61058 Synchronization lost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.8 61059 $Protocol Timing source lost on unit $U [, interface $IF] . . . . . . 204.9 61073 Routing misconfiguration for application $a . . . . . . . . . . . . . . . . 224.10 61074 CRL Update failure due to cause $C . . . . . . . . . . . . . . . . . . . . . 234.11 61075 Link OAM loopback inserted on unit $U, interface $F by $P peer 244.12 61076 Link OAM link lost on unit $U, interface $F. . . . . . . . . . . . . . . . . 254.13 61077 Link OAM critical link event $E on unit $U, interface $F . . . . . . . 264.14 61104 EBER on unit $U, interface $IF. . . . . . . . . . . . . . . . . . . . . . . . . . 274.15 61150 LOMF on slot $U, interface $IF. . . . . . . . . . . . . . . . . . . . . . . . . . 284.16 61151 AIS on unit $U, interface $IF. . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.17 61152 RDI on unit $U, interface $IF . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.18 61400 License missing for feature $feature on interface $if . . . . . . . . . 314.19 61410 CCM fault md $d level $ fault $f prio $p cause $c . . . . . . . . . . . 324.20 61411 ETH AIS fault interface $IF assoc $a md $d level $l mac addr $x334.21 61500 Five failed logins to FTM due to wrong user name or password 344.22 61510 Automatic BTS Operator Certificate retrieval unsuccessful . . . . 354.23 61605 BFD Session down in ingress direction for session $S. . . . . . . . 364.24 61606 BFD Session down in egress direction for session $S . . . . . . . . 374.25 # autonomous reset as recovery action . . . . . . . . . . . . . . . . . . . . . . . . . 384.26 [User defined] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.27 Antenna Line Device failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.28 Antenna Line failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.29 Antenna Line Operation Degraded . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.30 Automatic neighbor relation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.31 Baseband Bus failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.32 BTS Blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474.33 BTS internal SW management problem . . . . . . . . . . . . . . . . . . . . . . . . 484.34 BTS is uncommissioned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.35 BTS Master Clock tuning failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.36 BTS reference clock missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524.37 BTS reset required. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4 DN0980455



4.38 BTS time not corrected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.39 Cell blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.40 Commissioning error: <x>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594.41 Configuration error: <x> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604.42 Failure in connection between BTS and iOMS or 3rd party tool . . . . . . . 624.43 Failure in optical RP3 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634.44 Failure in trace session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654.45 Fan failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674.46 FPGA SW update failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684.47 GPS Receiver alarm: <x> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.48 GTP-U Path Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714.49 Heating element not working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724.50 Incompatible SW version detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.51 Mains power break, running Battery Backup . . . . . . . . . . . . . . . . . . . . . 744.52 Mast Head Amplifier fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754.53 No connection to Flexi transport submodule. . . . . . . . . . . . . . . . . . . . . . 764.54 Parallel RP3-01 link length mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . 774.55 Radio resources switched off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784.56 RET Antenna control failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794.57 RF Loss of secondary optical interface. . . . . . . . . . . . . . . . . . . . . . . . . . 804.58 RF Module blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.59 RF Module failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.60 RF Module overvoltage protection faulty . . . . . . . . . . . . . . . . . . . . . . . . 834.61 S1 interface recovery failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844.62 S1 interface setup failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854.63 S1 SCTP path failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864.64 System information broadcast parameters overflow. . . . . . . . . . . . . . . . 874.65 System Module failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884.66 Technical log buffer freezing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894.67 Temperature alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904.68 Temperature too low (Heating ongoing) . . . . . . . . . . . . . . . . . . . . . . . . . 914.69 Toggling: <Fault name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924.70 Transport layer connection failure in S1 interface. . . . . . . . . . . . . . . . . . 944.71 Transport layer connection failure in S1/X2 interface . . . . . . . . . . . . . . . 954.72 Transport layer connection failure in X2 interface. . . . . . . . . . . . . . . . . . 964.73 TX failure in MIMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974.74 Unit blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984.75 VSWR alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994.76 VSWR alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004.77 X2 interface recovery failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014.78 X2 interface setup failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1024.79 X2 neighbor cell configuration inconsistency . . . . . . . . . . . . . . . . . . . . 103

DN0980455 5



List of tablesTable 1 Description of the fields in the fault table . . . . . . . . . . . . . . . . . . . . . . . 11Table 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Table 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Table 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Table 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Table 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Table 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Table 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Table 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Table 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Table 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Table 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Table 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Table 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Table 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Table 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Table 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Table 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Table 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Table 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Table 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Table 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Table 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Table 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Table 27 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Table 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Table 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Table 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Table 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Table 32 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Table 33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Table 34 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Table 35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Table 36 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Table 37 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Table 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Table 39 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Table 40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Table 41 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Table 42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Table 43 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Table 44 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Table 45 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

6 DN0980455



Table 46 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Table 47 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Table 48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Table 49 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Table 50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Table 51 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Table 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Table 53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Table 54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Table 55 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Table 56 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Table 57 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Table 58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Table 59 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Table 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Table 61 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Table 62 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Table 63 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Table 64 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Table 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Table 66 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Table 67 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Table 68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Table 69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Table 70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Table 71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Table 72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Table 73 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Table 74 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Table 75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Table 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Table 77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Table 78 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Table 79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Table 80 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

DN0980455 7

Flexi Multiradio Base Station LTE Faults Summary of changes

Id:0900d80580866506Confidential

Summary of changesChanges between issues 02 (2010-12-16, LTE, Rel. RL20) and 02A (2011-03-25, LTE, Rel. RL20)New faults:

– Automatic BTS Operator Certificate retrieval unsuccessful– CCM fault md $d level $ fault $f prio $p cause $c– ETH AIS fault interface $IF assoc $a md $d level $l mac addr $x

Updated faults:

– BTS internal SW management problem– BTS reference clock missing– BTS reset required– Transport layer connection failure in S1/X2 interface– RF Loss of secondary optical interface

Changes between issues 01 (2010-10-28, LTE, Rel. RL10) and 02 (2010-12-16, LTE, Rel. RL20)New faults:

– Antenna Line Operation Degraded– BFD Session down in egress direction for session $S– BFD Session down in ingress direction for session $S– Failure in trace session– Link OAM critical link event $E on unit $U, interface $F– Link OAM link lost on unit $U, interface $F– Link OAM loopback inserted on unit $U, interface $F by $P peer– No module fan detected– Parallel RP3-01 link length mismatch– RF Module blocked– RF Module overvoltage protection faulty– S1 SCTP path failure– System information broadcast parameters overflow– Transport layer connection failure in S1 interface– Transport layer connection failure in X2 interface

Updated faults:

– Antenna Line failure– CRL Update failure due to cause $C– Dead Peer Detected– Failure in connection between BTS and iOMS or 3rd party tool– Failure in optical RP3 interface– Fan failure– GTP-U Path Failure– Radio resources switched off– RET Antenna control failure– Transport layer connection failure in S1/X2 interface– TX failure in MIMO

8 DN0980455


Id:0900d80580866506Confidential

Summary of changes

– X2 neighbor cell configuration inconsistency

DN0980455 9

Flexi Multiradio Base Station LTE Faults Overview of Flexi Multiradio BTS LTE Faults

Id:0900d8058083088fConfidential

1 Overview of Flexi Multiradio BTS LTE FaultsThis document describes fault and alarm handling of the Flexi Multiradio Base Station LTE. The base station software uses these faults and alarms as a basis for internal diag-nosis and fault reporting to the Operations Support System (OSS) and BTS Site Manager.

For troubleshooting instructions, see Flexi Multiradio BTS LTE Troubleshooting.

10 DN0980455


Id:0900d805808057a2Confidential

Flexi Multiradio BTS LTE fault and alarm handling

2 Flexi Multiradio BTS LTE fault and alarm handlingBase station (BTS) alarm handling is based on unit or module state information. It prevents the sending of unnecessary alarms by checking and updating unit states. Fault messages come either from hardware devices or software components. The faults are system or hardware specific. The Fault Diagnosis System creates upper network alarms, which are based on an analysis of the faults, and sends them to the BTS Site Manager.

In addition NetAct is used for handling the BTS alarms.

The BTS is able to maintain alarm handling after it has been commissioned and is in a configured state. During the start-up, the BTS waits for the real-time clock from the Network Time Protocol (NTP) server, and the fault diagnosis starts after the time has been set or a time-out has been detected. If the BTS is unable to set the time using the NTP server, the default time (1.1.2004) will be used.

Flexi Multiradio BTS LTE transmission alarms In Flexi Multiradio BTS LTE, transmission alarms are reported as Base station transmis-sion alarms (7665) towards OMS or NetAct. In Flexi Multiradio BTS LTE, transmission equipment uses the base station interface. Therefore, retrieval of the alarm information will be mapped either in the OMS or in NetAct to distinguish between the alarms by using the fault ID.

Instructions for solving problemsWhen starting to solve a problem, first refer to the instructions given in the individual alarm descriptions.

Verify the configuration of a BTS by checking the commissioning, cabling and correct installation of the modules at the BTS. Make sure the environment does not cause the fault.

If an active alarm is a 'Start' alarm, a unit block/unblock (if supported by the unit) or a site reset is required to cancel it. If the site reset or unit block/unblock does not help, replace the faulty unit or module. See the fields 'Fault source' and 'Instructions' in the corresponding alarm description.

Blocking and unblockingThe 'Cancel' alarms are always sent to hosts (LTE BTS Site Manager). When the unit or cell is in a blocked state, the 'Start' alarms are only sent to LTE BTS Site Manager.

When a unit or cell is unblocked, all the active alarms related to the unblocked unit, module, or cell are automatically sent to the hosts.

DN0980455 11

Flexi Multiradio Base Station LTE Faults BTS fault table


3 BTS fault table

Fault name: The name of the fault.

Used in products: The name of the product in question.

Detecting unit: The unit that detects the fault.

Source: The equipment suspected to be faulty (sub-unit in parentheses).

Note that sometimes the actual source of the fault is different than the one that detects the fault.

Meaning: A description of the fault situation.

State: The options are:

Event (Transient or Distur)

• Notification type fault • 'Event' fault is not cancelled, because it is never active • No recovery actions • Event type fault is shown in the BTS Site Manager as 'Transient'

Start

• A fault situation • The fault is not automatically cleared (without manual operation and maintenance

work), even though the problem has been solved, but requires at least block-ing/unblocking the unit or site reset.

• Recovery actions depend on the reported severity

Start/Cancel

• Faults can be in a start or cancel state • The fault is automatically cleared when the problem has been solved

Unit status: The options are:

Out of order The unit does not work

Degraded The main functions of the unit work, but not all

Working All functions are working, but some trouble has been notified

Info Status change information

Unit status attributes:

Lists the statuses per product, when the status varies depending on the product.

Effect: A description of how this fault affects the operations of this unit, and how it affects the operations of other units. The following questions are considered:

Does the status of the unit or its sub-units have any effect on the interpretation of the fault?

Does the fault have an effect on other active faults?

Table 1 Description of the fields in the fault table

12 DN0980455



BTS fault table

Reported alarms: 7650 BASE STATION FAULTY

• Start, disables all cells • Cancel, causes a site reset • No new 7651, 7653 or 7654 alarms are reported when 7650 is active

7651 BASE STATION OPERATION DEGRADED

• There is no limit to how many 7651 alarms can be active at the same time

7652 BASE STATION NOTIFICATION


7653 CELL FAULTY

• Start, the affected cell state is set disabled • Cancel, the affected cell state is set enabled

7654 CELL OPERATION DEGRADED


7655 CELL NOTIFICATION


7665 BASE STATION TRANSMISSION ALARM

• In case of faulty transmission equipment or transmission software, this alarm is reported towards the OMS or NetAct.

• Transmission alarms do not have dependencies to other BTS alarms.

7660 BASE STATION LICENCE EXPIRED

• Licence alarms do not have dependencies to other BTS alarms.

7661 BASE STATION LICENCE NOTIFICATION

• Licence alarms do not have dependencies to other BTS alarms.

Reported alarms description:

If there are several reported alarms, explains the situation in which the given alarm is reported.

LED display: The colour of the LED representing the fault level of the unit. The options are:

Stable red Major alarm

Blinking red Minor alarm

Stable yellow Unit in standby state or unit blocking

Blinking yellow Unit in self-heating state or software downloading

Stable green Unit on and working

Alternating red and green MHA faulty

Instructions: Describes the actions required to clear the fault.

Table 1 Description of the fields in the fault table (Cont.)

DN0980455 13

Flexi Multiradio Base Station LTE Faults Flexi Multiradio BTS LTE faults


4 Flexi Multiradio BTS LTE faults

4.1 61006 The FTM booted at $date due to $RCause

Fault name The FTM booted at $date due to $RCause

Used in products LTE

Detecting unit FTLB, FTIB

Source FTM

Meaning The transport part of the BTS has been reset at the date and time given in the notification. The cause for the reset can be one of the following: "power-on reset": Cold start "watch-dog reset": System overload "startup failure": Failure during startup "soft-ware failure": Software failure "man-agement reset": Reset triggered by management interface "fallback": Fallback executed

State Transient

Unit status Minor

Unit status attributes

Effect The fault has no further conse-quences.

Reported alarms 7665 BASE STATION TRANSMIS-SION ALARM

LED display N/A

Instructions No actions are required

Table 2

14 DN0980455


Id:0900d8058086639eConfidential

4.2 61010 BTS reset required

Fault name BTS reset required



Source FTM

Meaning A change to the BTS IP settings has been received from the BTS Site Manager. To activate the change, the BTS needs to be restarted.

State Start

Unit status Warning


Effect The BTS does not take the new settings into use before a reset.


LED display N/A

Instructions Reset the BTS when all required BTS IP settings have been set.

Table 3

DN0980455 15


Id:0900d805808662acConfidential

4.3 61028 LOF on unit $U, interface $IF

Fault name LOF on unit $U, interface $IF



Source PPTT

Meaning Loss of frame. It is not possible to carry traffic on the interface refer-enced in the alarm text. All other trans-mission alarms related to this signal are suppressed. Probable cause for E1 interfaces: The interface at the far end is not configured to be a framed E1 interface. Probable cause for T1 interfaces: The interface at the far end is not configured to be a T1 interface.

State Start / Cancel

Unit status Critical


Effect Possible impact on the connections over this interface: - no calls are possible - loss of remote management access to other network elements in the RAN - loss of synchronization if the interface is used as synchronization source.


LED display Stable red

Instructions E1 interfaces: Check that the interface type of the far-end interface is also configured to be a framed E1 inter-face. If this is not the case, reconfigure the interfaces so that they match each other. JT1 interfaces: Check that the interface type of the far-end interface is also configured to be a JT1 inter-face. If this is not the case, reconfigure the interfaces so that they match each other.

Table 4

16 DN0980455


Id:0900d805808662abConfidential

4.4 61029 LOS on unit $U, [ethernet] interface $IF

Fault name LOS on unit $U, [ethernet] interface $IF



Source ETHLK

Meaning No signal is received on the interface referenced in the alarm text. All other transmission alarms related to this signal are suppressed. Probable causes for Ethernet interfaces: - a cable is cut or there is no cable con-nected to the interface - the electrical signal is excessively attenuated - the port at the connected far end node is switched off




Effect Possible impact on the connections over this interface: - no calls are possible anymore - loss of remote management access to other network elements in the RAN - loss of synchro-nization if the interface is used as a synchronization source



Instructions 1. Check that the cables are con-nected to the correct connectors. 2. Check that the interface at the far-end interface is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instruc-tions for handling those alarms. 4. To verify that the hardware of the inter-face unit works correctly, connect a loop cable and check whether the alarm disappears.

Table 5

DN0980455 17



4.5 61030 Dead Peer Detected

Fault name Dead Peer Detected



Source IKESA

Meaning A dead peer was detected in one of the IPsec associations of the FTM. Possibly - a cable is cut or there is no cable connected to the interface - the signal is excessively attenuated - the port at the connected far end node is switched off


Unit status Major


Effect Possible effects: - no calls are possible anymore - loss of remote manage-ment access to other network elements in the RAN - loss of synchro-nisation if the interface is used as a synchronisation source.


LED display Stable yellow

Instructions 1. Check that the cables are con-nected to the correct connectors. 2. Check that the interface at the far-end interface is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instruc-tions for handling those alarms.

Table 6

18 DN0980455


Id:0900d8058086639fConfidential

4.6 61050 Missing or non-compliant SFP module on unit $U, interface $I

Fault name Missing or non-compliant SFP module on unit $U, interface $I



Source ETHLK

Meaning The small form-factor pluggable (SFP) module detected in the interface con-nector does not comply with security requirements. It does not have a class 1 laser.




Effect The interface cannot be used for transmission.



Instructions Insert an SFP module with the correct laser type (class 1) to the Gigabit Ethernet interface of the unit.

Table 7

DN0980455 19


Id:0900d805808662b1Confidential

4.7 61058 Synchronization lost

Fault name Synchronization lost



Source STPG

Meaning Primary and secondary timing source lost. The LTE is running on internal clock or in hold-over mode and no timing signal is sent. The first and second synchronization sources from the configured priority list are unavail-able. On failure, the LTE switches automatically to the next clock source in the priority list. Probable cause: The transmission links selected for clock source are faulty. The reason can be alarms on the interfaces (for example, LOS).


Unit status Major


Effect Possible impact: The BTS is not syn-chronized to the network anymore.



Instructions Use the BTS Site Manager to check which interfaces have been configured as synchronization sources. 1. Check that the cables are connected to the correct connectors. 2. Check whether the interface at the far end is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions on handling those alarms. 4. To verify that the hardware of the interface unit works correctly, connect a loop cable and check whether the alarm disappears.

Table 8

20 DN0980455



4.8 61059 $Protocol Timing source lost on unit $U [, interface $IF]

Fault name $Protocol Timing source lost on unit $U [, interface $IF]



Source STPG

Meaning One of the synchronisation sources in the configured priority list is unavail-able. This can be the primary or the secondary clock source. In the alarm: Protocol can be PDH, Timing over Packet (ToP) and Synchronuous eth-ernet. Unit number is always 1. The interface value is optional: - For PDH the value range depends on the hardware unit type: 1..16 - For Syn-chonuous Ethernet the value range = 1..3 - It is not present for Timing over Packet.


Unit status Minor


Effect The BTS may have to use a synchro-nization interface that has a lower clock quality: if the primary clock source has been lost, the BTS switches automatically to the second-ary clock source. If both the primary and the secondary clock sources are lost, the BTS switches to the internal clock.


LED display Blinking red

Table 9

DN0980455 21



Instructions Use BTS Site Manager to check which interfaces have been configured as synchronization sources. For all inter-faces, do as follows: 1. Check that the cables are connected to the correct connectors. 2. Check whether the interface at the far end is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions on handling those alarms. 4. To verify that the hardware of the interface unit works correctly, connect a loop cable and check whether the alarm disappears. Monitor the received clock quality.

Table 9 (Cont.)

22 DN0980455



4.9 61073 Routing misconfiguration for application $a

Fault name Routing misconfiguration for applica-tion $a



Source IEIF and IVIF

Meaning A routing misconfiguration was detected. A packet was sent over an IP interface for which it was not intended, as configured in the VLAN traffic path map. For examplea user-plane packet was sent over an inter-face that is intended for control plane traffic. Since the interface selection is based on the routing table entries, a misconfiguration of the routing table is suspected.


Unit status Major


Effect A packet might not arrive at its destina-tion or it might arrive delayed at its destination or other traffic might arrive delayed at its destination, if the mis-routed packet is now scheduled with higher priority as to be expected without the misconfiguration.


LED display None

Instructions Correct the routing table or change the settings of the VLAN traffic path map.

Table 10

DN0980455 23



4.10 61074 CRL Update failure due to cause $C

Fault name CRL Update failure due to cause $C



Source CERTH

Meaning This alarm is raised if the BTS cannot update the Certificate Revocation List (CRL) for one of the following reasons: - the LDAP binding fails or - the LDAP search is emtpy (no CRL found) / the LDAP search contains more then one entry or - the CRL signature validation fails or - the CRL file exceeds the BTS storage limit or - the BTS certificate is part of the CRL or - DNS resolution for the CRL distribution point fails.


Unit status Minor


Effect The Certificate Revocation List could not be updated. New revoked certifi-cates remain unknown to the BTS.


LED display None

Instructions Execute general configuration checks: - Configuration of CMP server IP address and port and DNS server IP address. - Configuration of routing entries towards remote peers. - Con-figuration of IPSec policies towards remote peers. Check remote peers and intermediate network elements interconnections. Check the LDAP connection towards the Certificate Revocation List server. Check DNS names. Check the size of the file at the Certificate Revocation List server.

Table 11

24 DN0980455



4.11 61075 Link OAM loopback inserted on unit $U, interface $F by $P peer

Fault name Link OAM loopback inserted on unit $U, interface $F by $P peer


Detecting unit FTIB, FTFB, FTLB

Source ETHLK

Meaning A loopback is requested for an ethernet interface either locally at the BTS or the Link OAM client of the BTS is set into loopback mode by the remote Link OAM peer.


Unit status Major


Effect Normal traffic is interrupted. Only loopback OAM frames are transmitted and received over the interface. If the test frame generator is switched on, test frames are transmitted.


LED display None

Instructions None.

Table 12

DN0980455 25



4.12 61076 Link OAM link lost on unit $U, interface $F

Fault name Link OAM link lost on unit $U, interface $F



Source ETHLK

Meaning On an interface for which the Link OAM functionality was switched on, no Link OAM PDUs were received during the period specified in configuration parameter linkLostTime (2..10 seconds, step 1 second).


Unit status Major


Effect The ethernet interface might be out of order or the remote peer might be out of order. Traffic might get lost.

Reported alarms

LED display None

Instructions 1)Check cabling and network connec-tions to the far end. 2)Check Link OAM event- and Link OAM state informa-tion. 3)Check ethernet interface con-figuration at local and remote side. 4)Insert a Link OAM loopback.

Table 13

26 DN0980455



4.13 61077 Link OAM critical link event $E on unit $U, interface $F

Fault name Link OAM critical link event $E on unit $U, interface $F


Detecting unit FTIB, FTLB, FTFB

Source ETHLK

Meaning A Link OAM PDU containing a critical link event flag was received on the ethernet interface. The alarm is raised with the first detection of the flag. The following critical link events are possi-ble: - Critical Event: either an Errored Symbol Period Event, an Errored Frame Event an Errored Frame Period Event or an Errored Frame Seconds Summary Event was detected. - Dying Gasp: either the local or the remote peer has a fatal error and is about to restart. - Link Fault: the local peer has detected a physical link fault in receiv-ing direction, e.g. a LOS.


Unit status Major


Effect The ethernet interface is defected or the remote peer is defective. Traffic might get lost.


LED display None

Instructions 1)Inspect details of the type of the critical event through online configura-tion management. 2)Check Link OAM state information of the interface. 3)Check cabling and network connec-tions to the far end. 4)Check ethernet interface configuration at local and remote side. 5)Insert a Link OAM loop-back.

Table 14

DN0980455 27



4.14 61104 EBER on unit $U, interface $IF

Fault name EBER on unit $U, interface $IF



Source PPTT

Meaning Excessive bit error rate. The measured bit error rate exceeds the threshold value of BER-3 (10E-3). Probable causes: - the signal level is too low (optical connectors or cables are dirty, electrical connectors or cables are corroded) - the specified maximum length of the cable is exceeded - the connector is not properly connected to the unit - the receiver or the far end transmitter has failed


Unit status Major


Effect Possible impact: - slow management access to the WBTS and other network elements in the RAN - poor voice quality and data performance - if this interface is part of an IMA group, this IMA link is to be temporarily sus-pended from operation



Instructions 1. Clean the cables and connectors. 2. Check that the connectors are properly connected to the unit. 3. Check that the cable connected to the interface in question is not damaged and is within the specifications. 4. Follow the signal in the network and check whether any other alarms con-cerning the fault are on (such as Laser End of Life). If they are, follow the instructions for handling those alarms.

Table 15

28 DN0980455


Id:0900d805808662aeConfidential

4.15 61150 LOMF on slot $U, interface $IF

Fault name LOMF on slot $U, interface $IF



Source PPTT

Meaning Loss of multiframe. The interface ref-erenced in the alarm text has lost the multiframe alignment. Probable cause: the interface type has not been configured to meet the framing of the interface at the far end. For E1 inter-faces, the configuration of the far-end node should be E1 Multiframe.


Unit status Major


Effect Possible impact: the performance management data collected on this interface becomes invalid.



Instructions Check that the configured interface type matches the configured interface type of the far end. If this is the case, the problem is somewhere in the transmission network.

Table 16

DN0980455 29


Id:0900d805808662adConfidential

4.16 61151 AIS on unit $U, interface $IF

Fault name AIS on unit $U, interface $IF



Source PPTT

Meaning Alarm indication signal is received. This signal is generated by an interme-diate PDH device in the forward direc-tion because it detects a problem in its receive signal. All other transmission alarms related to this signal are sup-pressed. Probable cause: There is a transmission problem somewhere in the intermediate network and AIS is sent instead of user traffic.


Unit status Major


Effect Possible impact on the connections over the interface in question: - no calls are possible - loss of remote management access to other network elements in the RAN



Instructions Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

Table 17

30 DN0980455


Id:0900d805808662afConfidential

4.17 61152 RDI on unit $U, interface $IF

Fault name RDI on unit $U, interface $IF



Source PPTT

Meaning Remote defect indication. It is sent by the intermediate or the far end equip-ment because it detects a serious fault in the received signal. Probable cause: The far end has a LOS, LOF or AIS alarm on its receiving interface.


Unit status Major


Effect Possible impact on the connections over this interface: - no calls are possible - loss of remote management access to other network elements in the RAN - loss of synchronization if the interface is used as a synchronization source



Instructions 1. Check the intermediate transmis-sion network for alarms indicating the root cause and follow the instructions for handling these alarms. 2. To check the transmit hardware, connect a loop cable and check that no alarms appear for this interface.

Table 18

DN0980455 31


Id:0900d8058086639cConfidential

4.18 61400 License missing for feature $feature on interface $if

Fault name License missing for feature $feature on interface $if



Source PPTT, FTM

Meaning The feature referenced in the alarm text has been configured without installing a valid license. Probable cause: A valid license that would allow the operation of the feature is not available in the WBTS. This BTS fault can be displayed in the followings vari-ants: License Missing for additional 2 E1, T1 interface License Missing for Timing Over Packet


Unit status Major


Effect Possible impacts: PDH clock is not to be operable. TimeOverPacket clock is not to be operable.



Instructions Download a valid license to the WBTS.

Table 19

32 DN0980455


Id:0900d805808663aaConfidential

4.19 61410 CCM fault md $d level $ fault $f prio $p cause $c

Fault name CCM fault md $d level $ fault $f prio $p cause $c



Source OAMMEP

Meaning The alarm is triggered whenever a service OAM error related to the trans-mission of Continuity Check Messages (CCM) persists on a given Ethernet interface over the period 2,5 s. The following alarms are defined: 1) XC_CCM_defect, priority 5 (highest priority): Maintenace Domain level mismatch or Maintenance Association identification mismatch. 2) Error_CCM, priority 4: Maintenance End Point identifier unknown, wrong CCM interval. 3) Remote_CCM_Defect, priority 3: at least one of the remote peers does not receive CCM from its peers, or local does not receive CCM from peer since 3.5 times the transmission period. 4) RDI_CCM, priority 1 (lowest priority): one remote peer detects RDI flag in the CCM frames. The alarm shall display the following information: -Alarm Name -Alarm Priority -Alarm cause: if difference sources produce the same alarm - MD name -MD level at which the alarm was detected

State Active / Cleared

Unit status Major


Effect The transport connection towards the remote peer may be defective. Traffic may get lost.


LED display None

Instructions 1) Check cabling. 2) Check CCM con-figuration at remote peer.

Table 20

DN0980455 33


Id:0900d805808663abConfidential

4.20 61411 ETH AIS fault interface $IF assoc $a md $d level $l mac addr $x

Fault name ETH AIS fault interface $IF assoc $a md $d level $l mac addr $x



Source OAMMEP

Meaning A Maintenance Endpoint (MEP) received a valid ETH-AIS frame. The alarm shows the following information: Interface MAID MD name MD level Source MAC address


Unit status Major


Effect The transport connection towards the remote peer may be defective. Traffic may get lost.


LED display None

Instructions 1) Check cabling. 2) Check configura-tion at remote peer.

Table 21

34 DN0980455



4.21 61500 Five failed logins to FTM due to wrong user name or password

Fault name Five failed logins to FTM due to wrong user name or password



Source FTM

Meaning Five consecutive failed login attempts to the FTM have been performed.

State Transient

Unit status Warning


Effect None


LED display N/A

Instructions Check your username and password.

Table 22

DN0980455 35



4.22 61510 Automatic BTS Operator Certificate retrieval unsuc-cessful

Fault name Automatic BTS Operator Certificate retrieval unsuccessful

Certificate does not exist



Source CERTH

Meaning A requested certificate could not be retrieved from the certificate authority (CA). A requested certificate could not be renewed from the certificate authority (CA).


Unit status Major


Effect The requested service is not available.



Instructions Provide the certificate.

Table 23

36 DN0980455



4.23 61605 BFD Session down in ingress direction for session $S

Fault name BFD Session down in ingress direction for session $S



Source IEIF, IVIF

Meaning The alarm is raised if the alarm is enabled, the BFD state for the session is not AdminDown and nevertheless no BFD packet is received at the local end during the detection time.


Unit status Major


Effect The communication link between the BTS and the BTS peer is defective. Or the peer is defective. No communica-tion is possible.



Instructions 1. Check the network between both BFD peers for physical link failures or misconfigurations. 2. Check if the BFD functionality in the peer is switched on and that the configurations of the BFD peers match.

Table 24

DN0980455 37



4.24 61606 BFD Session down in egress direction for session $S

Fault name BFD Session down in egress direction for session $S



Source IEIF, IVIF

Meaning The alarm is raised if the alarm is enabled, the BFD state of the session is not AdminDown and the BFD packet from the far end contains the diagnos-tic code = 'Control Detection Time Expired' AND no ingress alarm is present.


Unit status Major


Effect The communication link between the BTS and the BFD peer is defective. No communication is possible.



Instructions Check if the far end has BFD switched on.

Table 25

38 DN0980455


Id:0900d805808663e2Confidential

4.25 # autonomous reset as recovery action

Fault name # autonomous reset as recovery action


Detecting unit FCM

Source FCM, RFSW, FSP

Meaning The BTS tries to correct a fault situa-tion by performing a recovery reset to a unit, the site or the BTS.

State Transient

Unit status Working


Effect The BTS is operational.

Reported alarms 7652 BASE STATION NOTIFICA-TION

LED display Stable green

Instructions Check the fault history and other active faults of the unit. Note! This fault does not require any (special) actions.

Table 26

DN0980455 39



4.26 [User defined]

Fault name [User defined]


Detecting unit FCM

Source FCM

Meaning High or low voltage on the external alarm line. The user specifies the fault text during commissioning.


Unit status Working


Effect No actual effect to BTS functionality. This is user specific.

Reported alarms

LED display N/A

Instructions [User defined]

Table 27

40 DN0980455


Id:0900d805808663c0Confidential

4.27 Antenna Line Device failure

Fault name Antenna Line Device failure


Detecting unit FSM, Antenna Line Device itself

Source FR, MHA, TILT, EFIL

Meaning The System Module or the device itself has detected an abnormal operation or a failure in the antenna line device.


Unit status N/A


Effect Depending on the reported alarms, the fault situation might have no impact on the operation (BASE STATION or CELL NOTIFICATION), the cell capacity might have decreased (CELL OPERATION DEGRADED), or the cell might not be operational at all (CELL FAULTY).

Reported alarms 7652 BASE STATION NOTIFICA-TION;7653 CELL FAULTY;7654 CELL OPERATION DEGRADED;7655 CELL NOTIFICA-TION

LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Check the antenna line and antenna line devices. Make sure that the antenna line connectors are in the right torque. 2. Reset the alarming RF module by blocking/unblocking it. 3. Replace the faulty parts and/or devices along the antenna line. 4. Replace the RF Module.

Table 28

DN0980455 41


Id:0900d805808663aeConfidential

4.28 Antenna Line failure

Fault name Antenna Line failure


Detecting unit Flexi Filter, FR

Source Antenna connector

Meaning Radio Module (60W RRH) or Filter (all others) has detected overcurrent on the antenna line (note: antenna line term here also refers to the RS485 i/f). The antenna line might be damaged (short circuit) or some antenna line device is causing overload. All antenna line devices powered by the antenna line are out of order.


Unit status Degraded


Effect The antenna line is not operating cor-rectly. The cell capacity decreases.

Reported alarms 7654 CELL OPERATION DEGRADED

LED display Alternating red and green (RF working, Antenna Line faulty)

Instructions Check the antenna line and antenna line devices. Fix or replace the faulty parts/devices.

Table 29

42 DN0980455



4.29 Antenna Line Operation Degraded

Fault name Antenna Line Operation Degraded


Detecting unit FR

Source MHA, RET, EFil

Meaning An alarm message has been received from the antenna line device. The antenna line operation is degraded.




Effect The antenna line is not operating cor-rectly. The cell capacity decreases.


LED display Alternating red and green (RF working, Antenna Line faulty)

Instructions Check the antenna line and antenna line device that causes the alarm. Fix or replace the faulty parts/devices.

Table 30

DN0980455 43



4.30 Automatic neighbor relation failure

Fault name Automatic neighbor relation failure


Detecting unit FCM

Source FCM

Meaning Automatic Neighbor Relation (ANR) procedure failed for a discovered neighbor cell identified by Physical Cell Identifier (PCI) and Earfcn Downlink Radio Frequency (dlEarfcn) because: 1. IP address of a neighbor BTS for the discovered neighbor cell (PCI, dlEarfcn) cannot be found in the pciIpAdrMap mapping table. 2. IP address of a neighbor BTS for the dis-covered neighbor cell (PCI, dlEarfcn) is present in the pciIpAdrMap mapping table but SCTP X2 connection with the neighbor BTS already exists. 3. IP address of a neighbor BTS for the dis-covered neighbor cell (PCI, dlEarfcn) is present in the pciIpAdrMap mapping table but SCTP X2 connection cannot be established with the neighbor BTS.

State Transient

Unit status Working


Effect The fault has no effect on the base station operation but handovers are not possible.


LED display Stable Green

Table 31

44 DN0980455



Instructions 1. Check in the configuration file (NPF/SCF) if the pciIpAdrMap mapping table includes the correct IP address for the neighbor BTS associ-ated with the discovered neighbor cell. The discovered neighbor cell is defined by the Physical Cell Identifier (PCI) and Earfcn Downlink Radio Fre-quency (dlEarfcn). 2. Check in the configuration file (NPF/SCF) if the pci-IpAdrMap mapping table includes the IP address for the neighbor BTS asso-ciated with the discovered neighbor cell. 3. If the IP address of neighbor BTS is correct, then find a reason why SCTP association cannot be estab-lished with the neighbor BTS. One of the reasons why SCTP association cannot be established could be short period of MaxTimeSctpSetup timer (SCTP association establishment supervision timer). In such a situation extend the value of MaxTi-meSctpSetup timer in the configura-tion file (NPF/SCF).

Table 31 (Cont.)

DN0980455 45



4.31 Baseband Bus failure

Fault name Baseband Bus failure


Detecting unit FSM, FR

Source FSM, FR

Meaning The FlexiBTS has detected an abnormal operation or a failure in the BTS internal baseband bus. The failure cannot be pointed to a specific module but there are several possible fault sources.


Unit status N/A


Effect Depending on the reported alarms, the fault situation may have no impact on the operation (BASE STATION or CELL NOTIFICATION), the BTS capacity might have decreased (BASE STATION or CELL OPERATION DEGRADED, or CELL FAULTY), or the BTS might not be operational at all (BASE STATION FAULTY).

Reported alarms 7650 BASE STATION FAULTY;7651 BASE STATION OPERATION DEGRADED;7652 BASE STATION NOTIFICATION;7653 CELL FAULTY;7654 CELL OPERATION DEGRADED;7655 CELL NOTIFICA-TION

LED display N/A

Table 32

46 DN0980455



Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Check the other active BTS faults and act accordingly. 2. Check the cables between the System Module and RF Module. 3. Reset the RF Module and/or System Module, depending on the alarm source: a. Reset the RF Module by block-ing/unblocking it. b. Reset the System Module by blocking/unblock-ing it. 4. Replace the alarming RF Module. 5. If the System Module is the source or replacing the RF Module does not clear the fault situation, replace the alarming System Module.

Table 32 (Cont.)

DN0980455 47



4.32 BTS Blocked

Fault name BTS Blocked


Detecting unit FCM

Source FCM

Meaning The BTS is blocked with BTS Site Manager. The purpose is to avoid fault indications that may be raised during a BTS maintenance task.

State Start

Unit status Working


Effect The BTS does not send faults to the network management system (NMS) when the BTS is blocked. The fault cancellations are sent to the NMS. All cells are disabled.

Reported alarms 7650 BASE STATION FAULTY


Instructions To cancel the fault, unblock the BTS. Unblocking the BTS causes a site reset.

Table 33

48 DN0980455


Id:0900d805808663bfConfidential

4.33 BTS internal SW management problem

Fault name BTS internal SW management problem


Detecting unit FSM

Source FSM, FR, FT, FSP, Faraday

Meaning A software update to a module or sub-assembly has failed, or a corrupted SW file has been detected in the FLASH.

State Start

Unit status N/A


Effect Depending on the reported alarms, the fault situation might have no impact on the operation (BASE STATION or CELL NOTIFICATION), the BTS capacity might have decreased (BASE STATION or CELL OPERATION DEGRADED, or CELL FAULTY) or the BTS might not be operational at all (BASE STATION FAULTY).


LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Check the other active BTS faults. If the ROM disk is corrupted, change the alarming module. 2. Reset the RF Module and/or System Module, depending on the BTS fault source: a. Reset the RF Module by block-ing/unblocking it. b. Reset the System Module by blocking/unblock-ing it. 3. Update and activate the SW to the BTS. 4. Check the SW files. 5. Replace the alarming module.

Table 34

DN0980455 49


Id:0900d805808663ceConfidential

4.34 BTS is uncommissioned

Fault name BTS is uncommissioned


Detecting unit FCM

Source FSM

Meaning Commissioning file download has been started neither from BTS Site Manager nor NetAct during Autocon-figuration. Autoconfiguration might not be enabled in NetAct, the license is missing or the commissioning file is not found.

State Start



Effect The BTS is not commissioned.

Reported alarms 7651 BASE STATION OPERATION DEGRADED


Instructions 1. Check in NetAct that Autoconfigura-tion is enabled and the required license and commissioning file are available. 2. Check the Autoconnec-tion/Autoconfiguration information with BTS Site Manager. 3. Load the correct commissioning file to the BTS.

Table 35

50 DN0980455



4.35 BTS Master Clock tuning failure

Fault name BTS Master Clock tuning failure


Detecting unit FCM

Source FCM

Meaning The OCXO adjustment area is reaching its limit value. The DAC word value of the OCXO is lower than 205 or greater than 3891 (5% of the total adjustment area). The range for the DAC word is 0 - 4095.




Effect The BTS can operate properly for months or even a year when being in the 5% margin area, but eventually the DAC value reaches the adjustment limit (0 or 4095) and the OCXO cannot follow the synchronization reference signal beyond the limit. Assuming that even in this phase the BTS reference signal has correct accuracy (meaning the alarm indication is real), the BTS air interface starts to drift from the correct value (after reaching the limit 0 or 4095) and after a while the 3GPP accuracy limits are not met. Even in that phase the BTS may still be opera-tional but the system performance may drop, affecting e.g. to handovers.



Table 36

DN0980455 51



Instructions Note! Perform the steps below in the listed order until the fault disappears. 1. Check the other alarms of the BTS and FTM and act accordingly. 2. If there are no other synchronization related alarms active, start the fast tuning with BTS Site Manager. 3. Reset the site. Run fast tuning again. 4. Check the reference signal accuracy by measuring it with a fre-quency counter (note: requires a good timebase for the counter). The refer-ence signal can be found from the Sync Out interface of the Flexi System Module, the required accuracy is +/-0.015ppm. If the reference accuracy is correct, run fast tuning. 5. If that does not help, replace the system module.

Table 36 (Cont.)

52 DN0980455


Id:0900d805808663beConfidential

4.36 BTS reference clock missing

Fault name BTS reference clock missing


Detecting unit FSM

Source FSM

Table 37

DN0980455 53



Meaning This BTS fault indication is generated if the reference clock monitoring function of the BTS does not receive the highest configured synchroniza-tion reference signal or if all the syn-chronization reference signals are missing. The BTS fault is not gener-ated if the highest configured synchro-nization source is present, no matter what the lower level source statuses are. Background information: There is a fixed synchronization priority list in the FlexiBTS: -Priority 1: PPS (Pulse Per Second) signal connected to the Synchronization Input interface (Sync In) of the System Module. Normally the PPS signal is generated by the GPS receiver. -Priority 2: external 2.048MHz signal connected to the Sync In interface. -Priority 3: the refer-ence signal coming from the inte-grated transmission unit (FTM). Normally, all the FlexiBTS sources are not in use at the same time (it depends on the network planning and BTS con-figuration). During the BTS start-up, the available sources are checked against the reference source list in the BTS commissioning file and devia-tions regarding the missing highest priority source generate a fault. During runtime operation, the BTS fault func-tionality runs autonomously - notices also added/vanished sources which are missing from the commissioning file. The source for the FTM (which is the priority 3 source for the FlexiBTS) can be TDM interface signal (e.g. E1, T1...), physical layer Synchronous Ethernet (SyncE) signal or application layer Timing over Packet (ToP) in which the timing information to BTS(s) is generated by a ToP master. The FTM reference source priority selec-tion is not fixed but user-selectable. Furthermore, if a signal listed in the FTM references is not received, a BASE STATION TRANSMISSION ALARM is reported.

Table 37 (Cont.)

54 DN0980455




Unit status N/A


Effect If the reported alarm is 7652 BASE STATION NOTIFICATION, the BTS is using the lower level synchronization source as a reference for tuning the BTS master clock (OCXO). This does not necessarily have any effect on the BTS operation, it depends on the quality of the used lower level source. If the reported alarm is 7651 BASE STATION OPERATION DEGRADED, the BTS has no valid synchronization sources as a reference for tuning the OCXO and the OCXO is in holdover mode, using the last calculated tuning control value. The fault situation does not affect the BTS air interface stabil-ity, but if the fault situation lasts for a long time, the accuracy starts to drift slowly. However, it may take several weeks before the BTS/RAN opera-tions start to be affected because of the very small OCXO aging factor.

Reported alarms 7651 BASE STATION OPERATION DEGRADED;7652 BASE STATION NOTIFICATION

LED display N/A

Table 37 (Cont.)

DN0980455 55



Instructions Depending on the installed and com-missioned synchronization source(s) listed in section "Meaning", see the commissioned synchronization option below and perform the steps in the listed order until the BTS fault indica-tion disappears. GPS receiver (PPS source): 1. If there is a GPS receiver commissioned at the BTS site, note the following: If the GPS receiver is not locked to any satellite, it turns off the PPS signal which is normally delivered to the BTS (Sync In interface). The most common reason is that the GPS receiver does not see any satellites because of poor antenna installation (poor sky visibility). For this, the only permanent cure is to change the GPS antenna location. One indication of a fairly poor sky visibility is that the BTS fault is activated/canceled every now and then. 2. There may be a malfunc-tion in the GPS receiver. Perform a (remote) power reset for the GPS receiver. 3. There may be a malfunc-tion in the BTS. Perform a BTS site reset. 4. The GPS cable and/or con-nectors may be damaged. Check the cable and the connectors. 5. There may be a HW fault in the GPS receiver. Check the operation and change the HW, if needed. External 2.048MHz signal: 1. If there is an external 2.048MHz signal source com-missioned at the BTS site, check the BTS faults of that device and act accordingly. If this does not help, check the cables. Note that because the device type is not known, detailed instructions cannot be given - refer to the appropriate user manual of the device for further actions. 2. There may be a malfunction in the BTS. Perform a BTS site reset. FTM refer-ence (TDM, SyncE or ToP as source): 1. If there is an integrated transmission unit (FTM) commissioned at the BTS site, note the following: The FTM unit operates so that if it is not locked to a synchronization source, it turns off the clock reference signal which is normally delivered to the BTS master clock. The synchronization source of the FTM (set by the FTM synchroniza-tion priority setting) may be missing, causing the FTM's internal clock to drop to holdover mode. In this case,

56 DN0980455



4.37 BTS reset required

Fault name BTS reset required


Detecting unit FSM

Source FR

Meaning The BTS detected an RF Module that cannot be taken into use without a BTS reset. The RF Module type differs from the previous one or the RF module was not present during startup.

State Start

Unit status Out of order


Effect The new installed HW resources are not available before the BTS has been reset.

Reported alarms 7653 CELL FAULTY


Instructions Reset (block/unblock) the BTS.

Table 38

DN0980455 57


Id:0900d805808663adConfidential

4.38 BTS time not corrected

Fault name BTS time not corrected


Detecting unit FCM

Source FCM

Meaning The SNTP time cannot be fetched from the transport system (FTM) within the time limit.


Unit status Working


Effect No real time available. Alarms, logs and all reports include an incorrect time.



Instructions 1. Check the NTP setting. 2. Check the stratum parameter on the NTP server.

Table 39

58 DN0980455



4.39 Cell blocked

Fault name Cell blocked


Detecting unit FSM

Source LCR

Meaning The user has blocked the cell with BTS Site Manager.




Effect The BTS does not send any faults related to the blocked cell or the modules commissioned to the blocked cell to the network management system (NMS). The fault sending to BTS Site Manager is always enabled. The fault cancellations are always sent to the NMS. Calls through the blocked cell are transferred to another cell. It is not possible to establish new calls through the blocked cell.



Instructions To cancel the fault, unblock the cell.

Table 40

DN0980455 59


Id:0900d805808663bcConfidential

4.40 Commissioning error: <x>

Fault name Commissioning error: <x>



Source FSM, FR, FT

Meaning Some of the commissioning parame-ters are either missing or faulty, or there is a mismatch between them.

State Start

Unit status N/A


Effect Depending on the reported alarms, the BTS capacity might have decreased (BASE STATION OPERATION DEGRADED), or the BTS might not be operational at all (BASE STATION FAULTY).

Reported alarms 7650 BASE STATION FAULTY;7651 BASE STATION OPERATION DEGRADED

LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Check the commissioning parameters with the BTS Site Manager Commissioning Wizard. 2. Load the correct commissioning file to the BTS.

Table 41

60 DN0980455


Id:0900d805808663bdConfidential

4.41 Configuration error: <x>

Fault name Configuration error: <x>


Detecting unit FSM

Source FSM, FR, AntennaLine, LCR, LCG

Meaning There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch in the BTS configuration.

State Start

Unit status N/A


Effect Depending on the reported alarms, the fault situation might have no impact on the operation (BASE STATION NOTI-FICATION), the BTS capacity might have decreased (BASE STATION OPERATION DEGRADED or CELL OPERATION DEGRADED, or CELL FAULTY), or the BTS might not be operational at all (BASE STATION FAULTY).


LED display N/A

Table 42

DN0980455 61


Id:0900d805808663bdConfidential

Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Check the installed HW/SW version compatibility and the HW com-patibility with the current BTS configu-ration. 2. Check that the BTS cell parameters from the Network man-agement system match the BTS HW configuration (for example frequency, power). 3. Check the Network man-agement system alarms for the alarming local cell (LCR). 4. Recom-mission the BTS to ensure that all parameters are correctly configured.

Table 42 (Cont.)

62 DN0980455



4.42 Failure in connection between BTS and iOMS or 3rd party tool

Fault name Failure in connection between BTS and iOMS or 3rd party tool


Detecting unit FCM

Source FCM

Meaning Failure in Trace connection between BTS and iOMS or 3rd Party Tool.




Effect In case of Subscriber trace activation, if the failed trace connection was to be used for sending the Trace Reports, then the BTS considers the trace acti-vation for that subscriber as failed. In case of cell trace and interface trace, if the failed trace connection was to be used for sending the Trace Reports, then the BTS does not start tracing until the trace connection is estab-lished successfully.


LED display N/A

Instructions Check the connection with iOMS/3rd Party tool.

Table 43

DN0980455 63



4.43 Failure in optical RP3 interface

Fault name Failure in optical RP3 interface



Source FSM, FR

Meaning The FlexiBTS has detected an abnormal operation or a failure in an optical RP3 interface between two modules. The failure cannot be pointed to a specific module but there are several possible fault sources.


Unit status N/A


Effect Depending on the reported alarms, the fault situation might have no impact on the operation (BASE STATION NOTI-FICATION) or the BTS capacity might have decreased (BASE STATION OPERATION DEGRADED or CELL OPERATION DEGRADED, or CELL FAULTY) or the BTS might not be operational at all (BASE STATION FAULTY).

Reported alarms 7650 BASE STATION FAULTY;7651 BASE STATION OPERATION DEGRADED;7652 BASE STATION NOTIFICATION;7653 CELL FAULTY;7654 CELL OPERATION DEGRADED

LED display N/A

Table 44

64 DN0980455



Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Check the other active BTS faults and act accordingly. 2. Check the cables between the System Module and RF Module. Note that dirty optical connectors may cause the signal level to drop too low. 3. Depending on the fault source, reset the RF Module and/or System Module by blocking/unblocking it. 4. Replace the alarming module's Small Form Factor Pluggable (SFP). Check also the SFP in the other end and replace it, if needed. 5. Replace the alarming RF Module. 6. If the System Module is the only alarming source or replacing the RF Module does not clear the fault situation, replace the alarming System Module.

Table 44 (Cont.)

DN0980455 65


Id:0900d805808663dbConfidential

4.44 Failure in trace session

Fault name Failure in trace session


Detecting unit FCM

Source FCM

Meaning Failure has occurred during activa-tion/deactivation of Trace Session (Subscriber trace or Cell trace ses-sion). In case of Subscriber trace, the possible reasons are: - Subscriber Trace feature has not been enabled at the BTS. - Id used for the subscriber trace session is already in use for another active subscriber trace session. - Count of subscriber trace sessions at the BTS has exceeded the maximum number of subscriber trace sessions supported by the BTS(which is 60). - Handover at BTS is ongoing for the UE to be traced In case of Cell trace, the possible reasons are: - Cell Trace feature has not been enabled at the BTS. - Id used for the cell trace session is already in use for another active cell trace session. - Count of cell trace sessions at the BTS has exceeded the maximum number of cell trace sessions supported by the BTS(which is 6).

State Transient

Unit status Working


Effect Trace session(for Subscriber/cell) cannot be activated/deactivated.


LED display N/A

Table 45

66 DN0980455


Id:0900d805808663dbConfidential

Instructions For failure in Subscriber trace session activation/deactivation: - Check if feature flag for Subscriber Trace feature has been enabled at the BTS. - If feature is enabled and problem per-sists, check if already 60 subscriber trace sessions are active. If yes, stop a subscriber trace session before acti-vating a new trace session. - If the problem is not yet resolved, try activat-ing/deactivating the trace session after some time (say after a couple of minutes) - If problem still persists, then stop all subscriber trace sessions and start them again. For failure in Cell trace session activation: - Check if feature flag for Cell Trace feature has been enabled at the BTS. - If feature is enabled and problem persists, check if already 6 cell trace sessions are active. If yes, stop a cell trace session before activating a new trace session. - If problem still persists, then stop all cell trace sessions and start them again.

Table 45 (Cont.)

DN0980455 67


Id:0900d805808663bbConfidential

4.45 Fan failure

Fault name Fan failure



Source FSM/FAN, FR

Meaning A fan, all the fans or more than one fan in the same fan group are rotating slower than requested, are not rotating at all, or the RPM information is not available for the fans. The reason for this fault can be a broken fan.


Unit status N/A


Effect If the fans are not rotating as expected, there is a risk that the module temperature rises too high. For example, a Temperature fault might be generated from the alarming module.


LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Check the fan and cabling. 2. Replace the faulty fan module.

Table 46

68 DN0980455



4.46 FPGA SW update failed

Fault name FPGA SW update failed

Used in products FlexiBTS

Detecting unit FRM2/LTX

Source LTX

Meaning The FPGA software update has failed.

State Start



Effect There can be problems in calls through the affected cell(s).



Instructions 1. Block/unblock the RF Module. 2. If that does not help, replace the alarming RF Module.

Table 47

DN0980455 69



4.47 GPS Receiver alarm: <x>

Fault name GPS Receiver alarm: <x>


Detecting unit FSM

Source FSM

Meaning Depending on the dynamic part of the fault indication, the reason for the indi-cation might be: - Poor GPS antenna installation - The GPS receiver is running a site/self survey - The GPS receiver settings are not correct - BTS has detected communication problem with the GPS receiver - GPS receiver has detected a deviation in its func-tionality


Unit status Working


Effect The fault has no direct impact on the operation (BASE STATION NOTIFI-CATION).



Table 48

70 DN0980455



Instructions Depending on the dynamic part of the fault indication, select the correct option and perform the steps below in the listed order until the fault disap-pears. Not tracking satellites: 1. The most common reason for this fault indi-cation is that the GPS antenna instal-lation has not been done properly, that is the sky visibility is not good enough. Please refer to the documentation for installations, and if there are devia-tions within the current installation, re-install the GPS antenna. Please notice that even when the GPS antenna has good sky visibility, the problem might be caused by installing the GPS antenna too close to the transmitter antenna(s) of the BTS, causing distur-bancies for the GPS receiver. 2. There might be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver. 3. There might be a HW fault in the GPS receiver. Check the operation and change the GPS module, if needed. Survey ongoing: 1. Do nothing. The alarm is informative only. Normally the GPS receiver runs the survey for two reasons: a) somebody has started the survey manually, b) the GPS receiver has noticed that the position has changed and the receiver has started an automatic survey. Please notice also that automatic survey takes place every time during first start-up. 2. If the automatic survey takes place every now and then, it might be an indication that the sky visibility is poor and according to the poorly tracked satel-lites, the GPS receiver concludes that the position has changed. In this case, check the activity of the other faults (BTS fault history data) and if found feasible, carry out a re-installation of the GPS antenna. 3. If the GPS instal-lation is good but still the automatic survey takes place every now and then, there might be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver. 4. If the actions detailed in previous steps do not correct the situation, there might be a HW fault in the GPS receiver. Check the operation and change the GPS module, if needed. No stored position: 1. One of the GPS receiver settings is incorrect. Using

DN0980455 71



4.48 GTP-U Path Failure

Fault name GTP-U Path Failure


Detecting unit FSM

Source GTP-U

Meaning In GTP-U supervision, a network element did not respond to the GTP-U: Echo Request message within time.




Effect For S1: The eNB lost the connection to S-GW. All calls using the failed GTP-U data path are released, and new GTP-U data tunnels are not created for the failed GTP-U data path until it works again.


LED display N/A

Instructions 1) Check the GTP-U path supervision configuration of the eNB. 2) Check the supervised network element for proper operation. 3) Check the communica-tion equipment in between eNB and the supervised network element.

Table 49

72 DN0980455



4.49 Heating element not working

Fault name Heating element not working


Detecting unit FCM

Source FCM

Meaning The heater control connection of the FSM is faulty, there is no heater or the heater is faulty.


Unit status Working


Effect Heating from the heating element is not available. The module tempera-ture may not reach the working level or may reach it very slowly.



Instructions 1. Check whether the heating element exists at all. 2. Check the heater control connection and that the heater is working. 3. Replace the alarming component.

Table 50

DN0980455 73


Id:0900d805808663deConfidential

4.50 Incompatible SW version detected

Fault name Incompatible SW version detected


Detecting unit FCM

Source FCM, FR, FF, FA, FSP, FTM

Meaning A new module with an incompatible SW has probably been inserted in the BTS.




Effect The resources provided by the module cannot be used, which means that some features do not necessarily work.

Reported alarms 7650 BASE STATION FAULTY;7651 BASE STATION OPERATION DEGRADED;7653 CELL FAULTY;7654 CELL OPERATION DEGRADED

LED display Stable red (7650, 7653), blinking red (7651, 7654)

Instructions Update compatible SW to the BTS (check the SW versions to see the active SW version, and update the active SW version), unless it is auto-matically updated by NetAct.

Table 51

74 DN0980455


Id:0900d805808663acConfidential

4.51 Mains power break, running Battery Backup

Fault name Mains power break, running Battery Backup


Detecting unit FCM

Source FCM

Meaning There is a fault in the mains power supply. Running on Battery Backup.




Effect The battery backup unit is partly or completely in use. If the mains power does not return, the cells are shut down according to the predefined parameters.



Instructions Check the mains power supply.

Table 52

DN0980455 75



4.52 Mast Head Amplifier fault

Fault name Mast Head Amplifier fault



Source FF, AISG MHA

Meaning The FlexiBTS has detected an abnormal operation or a failure in the Masthead Amplifier (MHA). Note that the Tower Mounted Amplifier (TMA) is a synonym for the MHA and is used by the Antenna Interface Standards Group (AISG).


Unit status N/A


Effect Depending on the reported alarms, the fault situation may have no impact on the operation (BASE STATION NOTI-FICATION), or the BTS capacity may have decreased (BASE STATION or CELL OPERATION DEGRADED).

Reported alarms 7652 BASE STATION NOTIFICA-TION;7654 CELL OPERATION DEGRADED

LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Check the cables related to the Masthead Amplifier (MHA). 2. Reset the alarming MHA module by blocking/unblocking the RF Module which the MHA is connected to. 3. Replace the faulty device(s).

Table 53

76 DN0980455



4.53 No connection to Flexi transport submodule

Fault name No connection to Flexi transport sub-module


Detecting unit FSM

Source FTM

Meaning The connection to the Flexi Transport submodule (FTM) is lost.


Unit status N/A


Effect The BTS is not operational.

Reported alarms 7650 BASE STATION FAULTY

LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Reset the site. 2. Replace the Transport submodule, which is located inside the System Module.

Table 54

DN0980455 77


Id:0900d805808663ddConfidential

4.54 Parallel RP3-01 link length mismatch

Fault name Parallel RP3-01 link length mismatch


Detecting unit FCM

Source OptIF

Meaning The parallel RP3-01 links towards one radio module have too large mutual length difference (more than 30 meters).




Effect All commissioned cells are not acti-vated.



Instructions Replace parallel RP3-01 fiber links towards one radio module so that the maximum mutual length difference between fibers is less than 30 meters.

Table 55

78 DN0980455



4.55 Radio resources switched off

Fault name Radio resources switched off


Detecting unit FCM

Source Antenna line

Meaning The radio resources are switched off to prevent possible Radio Module HW failure because of antenna line imped-ance mismatch. With other than FXCA, FXDA, FXEA, FXSA Radio Modules, switching off means that the I/Q data fed to the Radio Module has zero power due to deactivation of the cell handled by the Radio Module. With FXCA, FXDA, FXEA, FXSA Radio Modules, switching off means that the Power Amplifier within the Radio Module is switched off autono-mously by the Radio Module.


Unit status Out of order;Working

Unit status attributes Out of order: if VSWR alarm is not active for the same cell. Working: if VSWR alarm is active for the same cell.

Effect The affected cell is disabled.

Reported alarms 7653 CELL FAULTY;7655 CELL NOTIFICATION

LED display Stable red (7653, RF state "faulty"), Blinking red (7653, RF state "degraded"), Stable green (7655)

Instructions 1. Check the antenna lines: antennas, antenna cables, connector torques and antenna line devices. 2. Check the antenna line (TX-cable-antenna) impedance matching.

Table 56

DN0980455 79



4.56 RET Antenna control failure

Fault name RET Antenna control failure


Detecting unit TILT

Source TILT

Meaning Antenna tilting is not possible or might function incorrectly.




Effect The BTS capacity possibly decreases.


LED display Alternating red and green (RF module working, MHA faulty)

Instructions 1. Recalibrate the RET antenna. 2. If that does not help, replace the RET unit.

Table 57

80 DN0980455



4.57 RF Loss of secondary optical interface

Fault name RF Loss of secondary optical interface


Detecting unit FRx/LTX

Source OptIF

Meaning Secondary optical link between the System Module and RF Module is lost.




Effect Calls are not possible through the affected cell(s)



Instructions 1. Check the cables between the System Module and RF Module. 2. Block/unblock the RF Module. 3. If that does not help, block/unblock the site. 4. If that does not help, replace the alarming RF Module.

Table 58

DN0980455 81



4.58 RF Module blocked

Fault name RF Module blocked



Source LTX

Meaning A shared (Medusa) FR is blocked.




Effect It is not possible to establish phone calls through the blocked FR. The BTS does not send faults related to the blocked Flexi Radio module (FR) to the network management system (NMS). Fault sending to BTS Site Manager is always enabled. The fault cancels are always sent to the NMS.



Instructions Unblock the alarming module.

Table 59

82 DN0980455



4.59 RF Module failure

Fault name RF Module failure



Source FR

Meaning The FlexiBTS has detected an abnormal operation or a failure in the internal functionality of the RF Module.


Unit status N/A


Effect Depending on the reported alarms, the BTS capacity might have decreased (CELL OPERATION DEGRADED or CELL FAULTY).

Reported alarms 7653 CELL FAULTY;7654 CELL OPERATION DEGRADED

LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Check the other active BTS faults (System Module failure, Baseband Bus failure, Failure in optical RP3 interface and Antenna Line Device failure) and act accord-ingly. 2. Reset the alarming RF Module by blocking/unblocking it. 3. Check the cables between the System Module and RF Module. 4. If that does not help, replace the faulty RF Module.

Table 60

DN0980455 83



4.60 RF Module overvoltage protection faulty

Fault name RF Module overvoltage protection faulty

Used in products FlexiBTS

Detecting unit FR

Source LTX

Meaning RF Module's overvoltage protection is broken.

State Start

Unit status Working


Effect There is no immediate effect on the module operation, but the module might be severely damaged in the next overvoltage situation.



Instructions Replace the alarming RF Module.

Table 61

84 DN0980455



4.61 S1 interface recovery failure

Fault name S1 interface recovery failure


Detecting unit FSM

Source LNMME

Meaning S1 interface reset has failed after several attempts. This indicates that a severe failure has occurred, for example there is some configuration problem, there is no S1 connectivity, MME has failed, etc.


Unit status Out of order;Degraded

Unit status attributes Unit status is Degraded if at least one other S1 interface is operational, else the Unit status is Out of order

Effect The S1 interface is unavailable and the BTS is not available for call setup.


LED display N/A

Instructions Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the availability of MME. 2. Check the connection with MME. 3. Disconnect and reconnect MME.

Table 62

DN0980455 85


Id:0900d805808663cdConfidential

4.62 S1 interface setup failure

Fault name S1 interface setup failure


Detecting unit FSM

Source LNMME

Meaning There is no S1 connectivity to an MME, the MME has failed, etc. If the fault is canceled, autonomous recovery actions (reset) have solved the fault situation.



Unit status attributes Unit status is Degraded if at least one other S1 interface is operational, else the Unit status is Out of order

Effect The S1 interface is not available for call setup and existing calls are released.


LED display N/A

Instructions Note: Perform the steps below in the listed order until the alarm disappears. 1. Check availability of MME. 2. Check other faults on MME and BTS. 3. Check the parameters related to S1 interface in the BTS and MME. 4. Reset the BTS.

Table 63

86 DN0980455



4.63 S1 SCTP path failure

Fault name S1 SCTP path failure


Detecting unit FSM

Source SCTP link on S1 interface

Meaning One of the transport paths(SCTP) in SCTP connection to MME has failed. Only applicable when SCTP multi-homing is supported. An alternate transport path is available to pursue operation.




Effect One of the transport paths(SCTP) in SCTP connection to MME has failed. Only applicable when SCTP multi-homing is supported. An alternate transport path is available to pursue the operation.


LED display N/A

Instructions 1. Check whether the transport path is alive. 2. Check the configuration of transport addresses at MME.

Table 64

DN0980455 87


Id:0900d805808663dcConfidential

4.64 System information broadcast parameters overflow

Fault name System information broadcast param-eters overflow


Detecting unit FSP

Source FSP

Meaning System Information Broadcast related parameters have changed more than 32 times within 3 hours period.

State Transient

Unit status Working


Effect Some of the UEs with a complete set of system information of the cell stored which has left cell and comes back within 3 hours of time might not recog-nize, that there was a system informa-tion change.

Reported alarms 7655 CELL NOTIFICATION


Instructions Note! This fault does not require any (special) actions.

Table 65

88 DN0980455



4.65 System Module failure

Fault name System Module failure


Detecting unit FSM

Source FSM

Meaning The FlexiBTS has detected an abnormal operation or a failure in the internal functionality of the System Module.


Unit status N/A


Effect Depending on the reported alarms, the BTS capacity might have decreased (BASE STATION OPERATION DEGRADED) or the BTS might not be operational at all (BASE STATION FAULTY).


LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Reset the System Module. 2. Replace the System Module.

Table 66

DN0980455 89



4.66 Technical log buffer freezing

Fault name Technical log buffer freezing


Detecting unit FSP

Source FSP

Meaning The technical log buffer has been frozen in the BTS for an internal reason.

State Transient

Unit status Working


Effect This fault has no effect on BTS opera-tion.


LED display None

Instructions This fault does not require any actions.

Table 67

90 DN0980455


Id:0900d805808663baConfidential

4.67 Temperature alarm

Fault name Temperature alarm



Source FSM, FR

Meaning The internal temperature of the RF Module or System Module exceeds the threshold value, or the ambient temperature of the module(s) is outside the specified limits.


Unit status N/A


Effect Depending on the reported alarms, the fault situation might have no impact on the operation (BASE STATION NOTI-FICATION), the BTS capacity might have decreased (CELL OPERATION DEGRADED, or CELL FAULTY)) or the BTS might not be operational at all (BASE STATION FAULTY).

Reported alarms 7650 BASE STATION FAULTY;7652 BASE STATION NOTIFICA-TION;7653 CELL FAULTY;7654 CELL OPERATION DEGRADED

LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disap-pears. 1. Check the other BTS faults and act accordingly. 2. Check the ambient temperature of the BTS/mod-ules. If the ambient temperature is too high, make sure the airflow to the BTS modules is unobstructed, that is, the BTS modules are not covered with anything. If the ambient temperature is too low, it takes a while for the BTS/modules to heat themselves to the threshold value. 3. Reset the alarming module by blocking/unblock-ing it. 4. Replace the alarming module.

Table 68

DN0980455 91



4.68 Temperature too low (Heating ongoing)

Fault name Temperature too low (Heating ongoing)



Source LTX

Meaning The temperature inside the RF Module is too low and heating is ongoing.




Effect This fault should cancel itself. Heating of module is ongoing. During BTS startup affected cell resources will be reported to FCM as unavailable. During runtime (althought RF is restarted), fault is ignored.



Instructions 1. Wait until the fault is canceled. This may take up to 15 minutes. 2. If the fault is not canceled within the expected time, block/unblock the RF Module. 3. If that does not help, replace the alarming RF Module.

Table 69

92 DN0980455


Id:0900d805808663cfConfidential

4.69 Toggling: <Fault name>

Fault name Toggling: <Fault name>


Detecting unit FSM

Source FSM, FR, FT

Meaning BTS Fault, which fault name is men-tioned in the Fault name -field, is toggling in the BTS. Toggling alarm condition is informed to user with this new BTS Fault. Toggling alarms are supressed until the toggling alarm condition is cleared. Severity of this BTS Fault is the same than the severity of the toggling BTS Fault.


Unit status N/A


Effect Depending on the reported alarm, the fault situation might have no impact on the operation (BASE STATION or CELL NOTIFICATION), the BTS capacity might have decreased (BASE STATION or CELL OPERATION DEGRADED, or CELL FAULTY), or the BTS might not be operational at all (BASE STATION FAULTY).

Reported alarms 7650 BASE STATION FAULTY;7651 BASE STATION OPERATION DEGRADED;7652 BASE STATION NOTIFICATION;7653 CELL FAULTY;7654 CELL OPERATION DEGRADED;7655 CELL NOTIFICA-TION;7665 BASE STATION TRANS-MISSION ALARM

LED display N/A

Table 70

DN0980455 93


Id:0900d805808663cfConfidential

Instructions 1. Check the fault name of the toggling BTS fault from the Fault name of this fault. 2. Follow the instructions of the toggling BTS fault to clear the problem. Note! Detailed information about the toggling frequency can be found in alarm history file, which can be downloaded using BTS Site Manager. The log file is available with Snapshot."

Table 70 (Cont.)

94 DN0980455



4.70 Transport layer connection failure in S1 interface

Fault name Transport layer connection failure in S1 interface


Detecting unit FSM

Source SCTP link for S1 interface.

Meaning The transport path (SCTP) for connec-tion to MME has broken. The reason for this can be an unplugged cable to MME. No transport path available to pursue operation on the faulty connec-tion with the MME.



Unit status attributes Unit status is "Degraded" if the fault is on an S1 interface with at least one other S1 interface available for use. Unit status is "Out of Order" when all S1 interfaces are faulty.

Effect S1 interface is unavailable. If there is no other S1 interface available for use then BTS operation is considered faulty and no calls can be setup. If there is at least one other S1 interface available for use then BTS operation is considered degraded and BTS can continue operation(i.e. setup calls) using available S1 interface(s).


LED display N/A

Instructions Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the connection with MME based on whether the S1 link is broken respectively. 2. Check if MME is oper-ational. If this fault happens right after a commissioning or a configuration change, verify the following configura-tion data: IP address of the MME

Table 71

DN0980455 95



4.71 Transport layer connection failure in S1/X2 interface

Fault name Transport layer connection failure in S1/X2 interface

SCTP endpoint failure (6201)


Detecting unit FSM

Source SCTP link for S1/X2 interface.

Meaning The transport path (SCTP) for connec-tion to MME or to an adjacent BTS has broken. The reason for this can be an unplugged cable to MME/adjacent BTS. No transport path available to pursue operation.



Unit status attributes Unit status is Degraded if the fault is on the X2 interface Unit status is Out of Order when all S1 interfaces are faulty

Effect In case the transport path (SCTP) for S1 is broken, S1 interface is unavail-able. No calls can be setup. Base station is faulty. In case transport path (SCTP) for X2 is broken, X2 interface is unavailable. Handover of calls from or to cells of the associated adjacent BTS is not possible. Base station oper-ation is considered degraded.


LED display N/A

Instructions Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the connection with MME/adjacent BTS based on whether the S1/X2 link is broken respectively. 2. Check if MME or the adjacent BTS is operational. If this fault happens right after a commissioning or a config-uration change, verify the following configuration data: IP address of the MME or adjacent BTS

Table 72

96 DN0980455


Id:0900d805808663daConfidential

4.72 Transport layer connection failure in X2 interface

Fault name Transport layer connection failure in X2 interface


Detecting unit FSM

Source SCTP link for X2 interface.

Meaning The transport path (SCTP) for connec-tion to an adjacent BTS has broken. The reason for this can be an unplugged cable to the adjacent BTS. No transport path available to pursue operation on the faulty connection with the adjacent BTS.




Effect X2 interface is unavailable. Handover of calls from or to cells of the associ-ated adjacent BTS is not possible. Base station(BTS) operation is consid-ered degraded.


LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS Fault disap-pears. 1.Check the connection with adjacent BTS based on whether the X2 link is broken respectively. 2. Check if the adjacent BTS is opera-tional. If this fault happens right after a commissioning or a configuration change, verify the IP address of the adjacent BTS

Table 73

DN0980455 97



4.73 TX failure in MIMO

Fault name TX failure in MIMO


Detecting unit FSM

Source LCR

Meaning Due to TX path failure MIMO (Multiple Input Multiple Output) functionality is not operational in the cell related to the faulty TX.


Unit status Working


Effect The BTS continues working with a functioning TX paths in remaining cells, due to TX failure MIMO (Multiple Input Multiple Output) functionality is not operational for the cell related to the faulty TX. An attempt of the operator to configure any other mode than the single TX mode for the cell will be unsuccessful in this case.

Reported alarms 7655 CELL NOTIFICATION


Instructions The cell, which is related to the faulty TX, can be switched to the single TX mode by manual change of the value of the attribute dlMimoMode of the LCEL object, which corresponds to the cell related to the faulty TX, to "Sin-gleTX" (0) and manual triggering the BTS restart. Than the cell will operate in the single mode unless all the TXes related to the cell are faulty. Check the other active BTS faults and act accord-ingly.

Table 74

98 DN0980455


Id:0900d805808663dfConfidential

4.74 Unit blocked

Fault name Unit blocked


Detecting unit FSM

Source FR

Meaning A module is blocked with BTS Site Manager. The purpose is to avoid fault indications that may be raised during the module maintenance task.




Effect The BTS does not send faults related to the blocked module to the network management system (NMS). The fault sending to BTS Site Manager is always enabled. The fault cancella-tions are always sent to the NMS. It is not possible to establish phone calls through the blocked module.


LED display Stable yellow

Instructions Unblock the module with BTS Site Manager.

Table 75

DN0980455 99


Id:0900d805808663afConfidential

4.75 VSWR alarm

Fault name VSWR alarm




Meaning Radio Module (60W RRH)/the Filter (all others) has detected a VSWR value exceeding the defined level. The antenna line is mismatched or damaged.

State Start



Effect The cell is disabled.



Instructions 1. Check the antenna cables, connec-tors, antenna and possible antenna line devices. 2. Check the antenna line (TX-cable-antenna) impedance matching.

Table 76

100 DN0980455



4.76 VSWR alarm

Fault name VSWR alarm




Meaning Radio Module (60W RRH)/the Filter (all others) has detected a VSWR value exceeding the defined level. The antenna line is slightly mismatched.




Effect The output power at the antenna is decreased and the antenna is not working optimally.



Instructions 1. Check the antenna cables, connec-tors, antenna and possible antenna line devices. 2. Check the antenna line (TX-cable-antenna) impedance matching.

Table 77

DN0980455 101


Id:0900d805808663cbConfidential

4.77 X2 interface recovery failure

Fault name X2 interface recovery failure


Detecting unit FSM

Source LNADJ

Meaning The X2 interface reset has failed after several attempts. This indicates that a severe failure has occurred, for example there is some configuration problem, there is no X2 connectivity, the adjacent BTS has failed, etc.




Effect Handovers from or to cells of the related adjacent BTS are not possible.


LED display N/A

Instructions Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the availability of the adjacent BTS. 2. Check the connec-tion with the adjacent BTS. 3. Discon-nect and reconnect the adjacent BTS.

Table 78

102 DN0980455


Id:0900d805808663caConfidential

4.78 X2 interface setup failure

Fault name X2 interface setup failure


Detecting unit FSM

Source LNADJ

Meaning There is no X2 connectivity to an adjacent BTS, the adjacent BTS has failed, etc.




Effect Handovers to cells of the related adjacent BTS are not possible.


LED display N/A

Instructions Note: Perform the steps below in the listed order until the alarm disappears. 1. Check connectivity to the related adjacent BTS. 2. Check other faults. 3. Check the parameters related to the X2 interface to the adjacent BTS. 4. Reset the BTS.

Table 79

DN0980455 103


Id:0900d805808663ccConfidential

4.79 X2 neighbor cell configuration inconsistency

Fault name X2 neighbor cell configuration incon-sistency


Detecting unit FSM

Source LNADJ

Meaning Inconsistent cell information encoun-tered by BTS in: a) the configuration of an adjacent BTS or b) the configura-tion of an S1 handover target cell con-figured at BTS (in LNADLP Managed object) compared to the configuration received for that cell from an adjacent BTS. For case(a) above: The only cases when BTS reports inconsistent data currently are when cell informa-tion(Physical Cell ID and frequency i.e DL EARFCN) received from an adjacent BTS is found to be identical to - the cell information received from another adjacent BTS - one of own(i.e. local) BTS's configured cell informa-tion. For case(b) above: This case arises when BTS has a S1 handover target cell configured locally via O&M and also has an X2 link towards the BTS serving this target cell. In this case, BTS reports inconsistent data if the following cell information config-ured for the S1 handover target cell at BTS does not match the cell informa-tion received for that cell from adjacent BTS: - Physical Cell ID - Tracking Area Code - List of Broadcast PLMN IDs - Downlink EARFCN

State Transient

Unit status Working


Table 80

104 DN0980455


Id:0900d805808663ccConfidential

Effect In case of inconsistent adjacent BTS cell information in comparison to own BTS's cell information or some other BTS's(with which BTS has active X2 connection) cell information, han-dovers of calls from local BTS to those cells of adjacent BTS with inconsistent configuration might not be possible. In case of inconsistent S1 handover target cell information configured at BTS locally in comparison to the cell information from the adjacent BTS serving this target cell, S1 handover towards the target cell will not be impacted.


LED display N/A

Instructions In case of inconsistent adjacent BTS information, cross-check the correct-ness of the cell configuration of the already known cell(ECGI info identify-ing this cell is provided when alarm is raised) at BTS against the cell config-uration of the cell(ECGI info identifying this cell is provided as part of addi-tional info when alarm is raised) of adjacent BTS for which the error has been detected. In case of inconsistent S1 handover target cell information configured at own(i.e. local) BTS, cross-check the information in LNADLP managed object configured for this target cell with the information configured for this cell at adjacent BTS.

Table 80 (Cont.)

alm fleximrlbts faults

Documents

product safetythis product

operating documentation

documentation set

safety information applicable

safety information section

environmental information

product names

safety risks