enodeb faults

LTE Radio Access, Rel. RL50, Operating Documentation, Issue 01

Flexi Multiradio BTS LTE Faults

DN0980455

Issue 05AApproval Date 2013-09-23

Confidential

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their compo-nents.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information.

2 DN0980455


Id:0900d80580a2fb93Confidential

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 2013. 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 278 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1 Overview of Flexi Multiradio BTS LTE faults . . . . . . . . . . . . . . . . . . . . . 17

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

3 BTS fault table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4 Flexi Multiradio BTS LTE faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.1 # autonomous reset as recovery action . . . . . . . . . . . . . . . . . . . . . . . . . 214.2 $Protocol Timing source lost [on unit $U] [, interface $IF] . . . . . . . . . . . 224.3 10b8b coding error in optical interface device <opt link/RP3>. . . . . . . . 234.4 2M external reference missing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244.5 3GPP/AISG communication administratively disabled . . . . . . . . . . . . . 254.6 [User defined] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.7 Address mismatch in summing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.8 AIS on unit $U, interface $IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.9 Antenna Carrier configuration failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.10 Antenna Line Device failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.11 Antenna line device HW failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.12 Antenna line device missing software . . . . . . . . . . . . . . . . . . . . . . . . . . 344.13 Antenna Line Device Operation Failure . . . . . . . . . . . . . . . . . . . . . . . . . 354.14 Antenna line failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.15 Antenna line faulty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.16 Antenna line operation degraded. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.17 Antenna line switched off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.18 Antenna link is down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.19 Auto-negotiation mismatch, on unit $U, Ethernet interface $IF . . . . . . . 414.20 Automatic BTS Operator Certificate retrieval unsuccessful . . . . . . . . . . 424.21 Automatic cell recovery not possible . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.22 Base Station configuration alignment lost alarm . . . . . . . . . . . . . . . . . . 444.23 Baseband bus configuration of <x> was rejected . . . . . . . . . . . . . . . . . 454.24 Baseband bus failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464.25 BB bus message in the wrong slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484.26 BB bus reception error (summing device) . . . . . . . . . . . . . . . . . . . . . . . 494.27 BB bus transmission error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504.28 BFD $session down, egress, $sourceIP to $destinationIP . . . . . . . . . . 514.29 BFD $session down, ingress, $sourceIP to $destinationIP . . . . . . . . . . 524.30 BFD group $bfdGrpId down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.31 Boot configuration inconsistency detected. . . . . . . . . . . . . . . . . . . . . . . 544.32 BTS blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554.33 BTS config error (Not enough HW for LCR) . . . . . . . . . . . . . . . . . . . . . 564.34 BTS configuration not supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574.35 BTS file error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584.36 BTS internal SW management problem . . . . . . . . . . . . . . . . . . . . . . . . 594.37 BTS is uncommissioned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4 DN0980455



4.38 BTS master clock tuning failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624.39 BTS reference clock missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644.40 BTS reset required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674.41 BTS reset required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684.42 BTS reset time increased . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694.43 BTS SW download or activation failed . . . . . . . . . . . . . . . . . . . . . . . . . . 704.44 BTS time not corrected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714.45 BTS Trust Anchor expired or due to expire. . . . . . . . . . . . . . . . . . . . . . . 724.46 BTS vendor-specific file fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734.47 CCM fault level $ prio $p cause $c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744.48 Cell blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754.49 Cell configuration data distribution failed . . . . . . . . . . . . . . . . . . . . . . . . 764.50 Cell power failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 774.51 Cell reconfiguration data distribution failed . . . . . . . . . . . . . . . . . . . . . . . 784.52 Commissioning error: <x>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794.53 Communication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804.54 Configuration error: <x> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.55 Configuration file corrupted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834.56 Cooling fan broken . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844.57 Cooling fan broken: <X> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854.58 Cooling fan has reduced from the set speed . . . . . . . . . . . . . . . . . . . . . 864.59 Cooling fan is over speeding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874.60 Cooling fan is over speeding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884.61 Cooling fan speed decreased . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894.62 Critical BER detected on the optical connection to Radio Module . . . . . 904.63 Critical bit toggling error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914.64 CRL update failure due to $cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924.65 DC voltage administratively disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . 934.66 Dead Peer Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944.67 Difference between BTS master clock and reference frequency . . . . . . 954.68 Distributed site support not enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984.69 DSP overheated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994.70 EBER on unit $U, interface $IF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004.71 Error in file server during file download type <fileTypeNumber> . . . . . 1014.72 ETH AIS fault interface $IF level $l mac $x . . . . . . . . . . . . . . . . . . . . . 1034.73 Failure during cell activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044.74 Failure in connection between BTS and iOMS or 3rd party tool . . . . . . 1054.75 Failure in optical RP3 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064.76 Failure in replaceable baseband unit . . . . . . . . . . . . . . . . . . . . . . . . . . 1084.77 Failure in trace session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104.78 Fan failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.79 Fan module faulty: <X>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134.80 Fan module operation degraded: <X> . . . . . . . . . . . . . . . . . . . . . . . . . 1144.81 Fan vendor not detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154.82 Fatal OSE Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1164.83 Fault diagnostics rule file error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174.84 Faulty configuration of system modules . . . . . . . . . . . . . . . . . . . . . . . . 118

DN0980455 5



4.85 File corrupted in SW download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194.86 File System access failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204.87 Filter unit operation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1214.88 Five failed logins to FTM due to wrong user name or password . . . . . 1224.89 Flash operation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234.90 FPGA SW update failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244.91 Frame clock deviation fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1254.92 Frame clock missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1264.93 FSP in resetting state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1274.94 FSP overheating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284.95 FTM booted at $date due to $RCause . . . . . . . . . . . . . . . . . . . . . . . . 1294.96 FTM Toggling <Fault name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304.97 GPS Receiver alarm: control interface not available . . . . . . . . . . . . . . 1314.98 GPS receiver alarm: EEPROM invalid. . . . . . . . . . . . . . . . . . . . . . . . . 1324.99 GPS receiver alarm: no stored position . . . . . . . . . . . . . . . . . . . . . . . . 1334.100 GPS receiver alarm: not tracking satellites . . . . . . . . . . . . . . . . . . . . . 1344.101 GPS receiver alarm: position questionable . . . . . . . . . . . . . . . . . . . . . 1354.102 GPS receiver alarm: survey in progress . . . . . . . . . . . . . . . . . . . . . . . 1364.103 GTP-U Path Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1374.104 Heating element not working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384.105 High memory consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1394.106 Incoherency in cell configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1404.107 Incoherency in cell configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1414.108 Incoherency In Cell Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1424.109 Incoherency with RF Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1434.110 Incompatible SW version detected . . . . . . . . . . . . . . . . . . . . . . . . . . . 1444.111 Incorrect radio network parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 1454.112 Increased BER detected on the optical connection to Radio Module . 1464.113 Internal MTU configuration failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1474.114 Invalid configuration file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1484.115 Invalid frequency channel for the BTS HW . . . . . . . . . . . . . . . . . . . . . 1494.116 IP address conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1504.117 Link OAM critical link event $E on unit $U, interface $F . . . . . . . . . . . 1514.118 Link OAM link lost on unit $U, interface $F . . . . . . . . . . . . . . . . . . . . . 1524.119 Link OAM loopback inserted on unit $U, interface $F by $P peer . . . . 1534.120 LOF on unit $U, interface $IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1544.121 LOMF on slot $U, interface $IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1554.122 LOS on unit $U, [Ethernet] interface $IF . . . . . . . . . . . . . . . . . . . . . . . 1564.123 Loss of primary Opt IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1574.124 Low noise amplifier failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1584.125 Mast Head Amplifier fault. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1594.126 Mast Head Amplifier fault above current window, <line> . . . . . . . . . . . 1604.127 Mast Head Amplifier fault below current window, <line> . . . . . . . . . . . 1614.128 Master unit has lost connection to the slave unit . . . . . . . . . . . . . . . . . 1624.129 Maximum number of neighbor eNBs/cells exceeded. . . . . . . . . . . . . . 1634.130 Message routing problem in receiver (RX) . . . . . . . . . . . . . . . . . . . . . 1644.131 MHA unit operation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

6 DN0980455



4.132 Missing or non-compliant SFP module on unit $U, interface $I . . . . . . 1664.133 Missing RNW parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1674.134 Missing RP3-01 link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1684.135 Module Clock faulty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1694.136 Module dangerously overheating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1704.137 Neighbor cell ambiguity detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1714.138 No connection to Flexi transport submodule. . . . . . . . . . . . . . . . . . . . . 1724.139 No connection to unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1734.140 No feedback signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1744.141 No MME capacity assigned by Core Network. . . . . . . . . . . . . . . . . . . . 1754.142 No module fan detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1764.143 Not able to synchronize baseband bus with <x> . . . . . . . . . . . . . . . . . 1774.144 NTP server is not accessible . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1784.145 OIC MCU Buffer Full . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1794.146 Optical Interface Data/Control/Ethernet Buffer Full. . . . . . . . . . . . . . . . 1804.147 Optical Interface faulty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1814.148 Oven oscillator clock missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1824.149 Oven oscillator heating failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834.150 Oven oscillator Missing Pulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1844.151 Overload collision in transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1854.152 Parallel RP3-01 link length mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . 1864.153 Peer system module connection lost . . . . . . . . . . . . . . . . . . . . . . . . . . 1874.154 Phich Power Boost not applied . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1884.155 POST test failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1894.156 Post test failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1904.157 Power level not supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1914.158 Power level not supported for cells using the same radio module . . . . 1924.159 Power on #smodLogicalId #pwrLineId line switched off remotely by user .

1934.160 PPS reference clock missing in startup . . . . . . . . . . . . . . . . . . . . . . . . 1944.161 PPS reference missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1954.162 Radio master conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1974.163 Radio resources switched off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1984.164 RDI on unit $U, interface $IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1994.165 Receiving failure in Optical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 2004.166 RET Antenna control failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2014.167 RF BB bus configuration error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2024.168 RF BB bus connection transmission error . . . . . . . . . . . . . . . . . . . . . . 2034.169 RF BB bus synchronization error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2044.170 RF loss of secondary optical interface . . . . . . . . . . . . . . . . . . . . . . . . . 2054.171 RF Module blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2064.172 RF Module configuring failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2074.173 RF Module critical file not found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2084.174 RF Module failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2094.175 RF Module file not found. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2124.176 RF Module filter input power missing . . . . . . . . . . . . . . . . . . . . . . . . . . 2134.177 RF Module gain adjusting failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

DN0980455 7



4.178 RF Module out of order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2154.179 RF Module power output faulty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2164.180 RF Power decreased . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2174.181 RNW parameter mismatch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2184.182 RP3 routing collisions are detected on FR module . . . . . . . . . . . . . . . 2194.183 RP3-01 link conflict . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2204.184 RS485 IUANT port failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2214.185 RX out of order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2224.186 S1 eNB configuration update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2234.187 S1 interface recovery failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2244.188 S1 interface setup failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2254.189 S1 SCTP path failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2264.190 SFP HW Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2274.191 SRAM operation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2284.192 SRIO chain configuration was rejected . . . . . . . . . . . . . . . . . . . . . . . . 2294.193 Starting temperature below minimum . . . . . . . . . . . . . . . . . . . . . . . . . 2304.194 Summing not enabled for message type . . . . . . . . . . . . . . . . . . . . . . . 2314.195 Summing service default initialization failed . . . . . . . . . . . . . . . . . . . . 2324.196 Summing service release from reset failed . . . . . . . . . . . . . . . . . . . . . 2334.197 SW corrupted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2344.198 SW fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2354.199 SyncE Quality Level Degraded on unit $UID, interface $IF . . . . . . . . . 2364.200 SyncE SSM Timed Out on unit $UID, interface $IF . . . . . . . . . . . . . . . 2374.201 Synchronization error in RP1 receiver . . . . . . . . . . . . . . . . . . . . . . . . . 2384.202 Synchronization failure in Optical Interface <opt link/RP3 link>. . . . . . 2394.203 Synchronization lost. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2404.204 Synchronization master missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2414.205 System information broadcast parameters overflow . . . . . . . . . . . . . . 2424.206 System Module failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2434.207 Technical log buffer freezing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2454.208 Temperature alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2464.209 Temperature too low (heating ongoing) . . . . . . . . . . . . . . . . . . . . . . . . 2484.210 Toggling: <Fault name>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2494.211 ToP master service $IP unusable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2504.212 Transmission clock missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2514.213 Transmission parameters missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2524.214 Transmission quality deteriorated . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2534.215 Transmission rule collision in Muksu . . . . . . . . . . . . . . . . . . . . . . . . . . 2544.216 Transport layer connection failure in S1 interface . . . . . . . . . . . . . . . . 2554.217 Transport layer connection failure in X2 interface . . . . . . . . . . . . . . . . 2564.218 Transport module missing: $unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2574.219 TWAMP PLR Threshold Crossed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2584.220 TWAMP RTT Threshold Crossed . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2594.221 TX failure in MIMO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2604.222 TX out of order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2614.223 Unit (module) dangerously overheating . . . . . . . . . . . . . . . . . . . . . . . . 2624.224 Unit (module) temperature is high . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

8 DN0980455



4.225 Unit blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2644.226 Unit initialization failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2654.227 Unit not supported by current BTS SW version . . . . . . . . . . . . . . . . . . 2664.228 Unit SW download failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2674.229 Unit synchronization failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2684.230 Unit temperature is high . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2694.231 Unit unidentified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2704.232 Unknown HW resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2714.233 Unsupported HW device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2724.234 Validation of signed file failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2734.235 Vendor BTS certificate due to expire . . . . . . . . . . . . . . . . . . . . . . . . . . 2744.236 VSWR major alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2754.237 VSWR minor alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2764.238 X2 interface recovery failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2774.239 X2 interface setup failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

DN0980455 9



List of tablesTable 1 Description of the fields in the fault table . . . . . . . . . . . . . . . . . . . . . . . 19

10 DN0980455


Id:0900d80580a3014fConfidential

Summary of changes

Summary of changesChanges between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.

Changes between issues 05 (2013-06-21, RL50) and 05A (2013-09-23, RL50)New faults:

• Antenna line device missing software • Antenna line switched off • Antenna link is down • Automatic BTS Operator Certificate retrieval unsuccessful • BTS vendor-specific file fault • BTS SW download or activation failed • DC voltage administratively disabled • Failure in trace session • GPS Receiver alarm: control interface not available • High memory consumption • Neighbor cell ambiguity detected • Post test failed • PPS reference missing • SFP HW Failure • Unit synchronization failed • Unknown HW resource • Vendor BTS certificate due to expire • X2 interface setup failure

Modified faults:

• $Protocol Timing source lost [on unit $U] [, interface $IF] • AIS on unit $U, interface $IF • Antenna Carrier configuration failure • Auto-negotiation mismatch, on unit $U, Ethernet interface $IF • BFD group $bfdGrpId down • BFD $session down, egress, $sourceIP to $destinationIP • BFD $session down, ingress, $sourceIP to $destinationIP • BTS reset required • BTS time not corrected • BTS Trust Anchor expired or due to expire • CCM fault level $ prio $p cause $c • Cell configuration data distribution failed • Cell power failure • Cell reconfiguration data distribution failed • Commissioning error: <x> • Cooling fan broken • Cooling fan broken: <X> • Cooling fan has reduced from the set speed • Cooling fan is over speeding

DN0980455 11

Flexi Multiradio BTS LTE Faults Summary of changes


• Critical BER detected on the optical connection to Radio Module • CRL update failure due to $cause • Dead Peer Detected • EBER on unit $U, interface $IF • ETH AIS fault interface $IF level $l mac $x • Five failed logins to FTM due to wrong user name or password • FTM booted at $date due to $RCause • Incompatible SW version detected • 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 • LOF on unit $U, interface $IF • LOMF on slot $U, interface $IF • LOS on unit $U, [Ethernet] interface $IF • Master unit has lost connection to the slave unit • Maximum number of neighbor eNBs/cells exceeded • Missing or non-compliant SFP module on unit $U, interface $I • Missing RP3-01 link • Not able to synchronize baseband bus with <x> • NTP server is not accessible • Parallel RP3-01 link length mismatch • Radio master conflict • RDI on unit $U, interface $IF • RF Module failure • RX out of order • S1 interface recovery failure • S1 interface setup failure • SyncE Quality Level Degraded on unit $UID, interface $IF • SyncE SSM Timed Out on unit $UID, interface $IF • Synchronization lost • Technical log buffer freezing • ToP master service $IP unusable • Transport module missing: $unit • TWAMP PLR Threshold Crossed • TWAMP RTT Threshold Crossed • Unsupported HW device • VSWR minor alarm • X2 interface recovery failure

Removed fault:

• License missing for feature $feature on interface $if • Maximum number of LTE neighbor relations is exceeded • Maximum number of LTE NR per cell and carrier is exceeded • Pipe dangerously overheating • RF sensor temperature too high in Flexi Lite • Routing misconfiguration for application $a

12 DN0980455



Summary of changes

Changes between issues 04C (2013-04-22, RL40) and 05 (2013-06-21, RL50)New faults:

• 3GPP/AISG communication administratively disabled • Auto-negotiation mismatch, on unit $U, Ethernet interface $IF • Automatic cell recovery not possible • BB bus message in the wrong slot • BTS Trust Anchor expired or due to expire • Cell reconfiguration data distribution failed • Faulty configuration of system modules • Maximum number of LTE neighbor relations is exceeded • Maximum number of LTE NR per cell and carrier is exceeded • Message routing problem in receiver (RX) • Overload collision in transmitter • RP3 routing collisions are detected on FR module • S1 eNB configuration update • Summing not enabled for message type • Synchronization master missing • Transmission rule collision in Muksu

Modified faults:

• # autonomous reset as recovery action • $Protocol timing source lost on unit $U [, interface $IF] • 10b8b coding error in optical interface device <opt link/RP3> • 2M external reference missing • [User defined] • AIS on unit $U, interface $IF • Antenna Carrier configuration failure • Antenna line device HW failure • Antenna line faulty • Baseband bus configuration of <x> was rejected • Baseband bus failure • BB bus reception error (summing device) • BFD group $bfdGrpId down • BFD session down in egress direction for session $S • BFD session down in ingress direction for session $S • Boot configuration inconsistency detected • BTS blocked • BTS configuration not supported • BTS file error • BTS internal SW management problem • BTS is uncommissioned • BTS master clock tuning failure • BTS reference clock missing • BTS reset required • BTS time not corrected

DN0980455 13



• CCM fault level $ prio $p cause $c • Cell blocked • Cell configuration data distribution failed • Cell power failure • Commissioning error: <x> • Communication failure • Configuration error: <x> • Cooling fan broken: <X> • CRL update failure due to cause $C • Dead Peer Detected • Difference between BTS master clock and reference frequency • Distributed site support not enabled • EBER on unit $U, interface $IF • ETH AIS fault interface $IF level $l mac addr $x • Failure in connection between BTS and iOMS or 3rd party tool • Failure in optical RP3 interface • Fan module operation degraded: <X> • Fault diagnostics rule file error • File corrupted in SW download • File System access failed • Five failed logins to FTM due to wrong user name or password • Flash operation failure • Frame clock missing • FSP in resetting state • FSP overheating • FTM booted at $date due to $RCause • FTM Toggling <Fault name> • GPS receiver alarm: EEPROM invalid • GPS receiver alarm: no stored position • GPS receiver alarm: position questionable • GPS receiver alarm: survey in progress • GTP-U Path Failure • Incorrect radio network parameters • Increased BER detected on the optical connection to Radio Module • Internal MTU configuration failure • Invalid configuration file • License missing for feature $feature on interface $if • 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 • LOF on unit $U, interface $IF • LOMF on slot $U, interface $IF • LOS on unit $U, [Ethernet] interface $IF • Loss of primary Opt IF • Low noise amplifier failure • Master unit has lost connection to the slave unit

14 DN0980455



Summary of changes

• Missing or non-compliant SFP module on unit $U, interface $I • Missing RNW parameter • Missing RP3-01 link • Module Clock faulty • No connection to Flexi transport submodule • No connection to unit • Not able to synchronize baseband bus with <x> • NTP server is not accessible • OIC MCU Buffer Full • Optical Interface faulty • Oven oscillator clock missing • Oven oscillator heating failure • Oven oscillator Missing Pulse • Parallel RP3-01 link length mismatch • Pipe dangerously overheating • SyncE Quality Level Degraded on unit $UID, interface $IF • POST test failed • Power level not supported for cells using the same radio module • Power on #smodLogicalId #pwrLineId line switched off remotely by user • PPS reference clock missing in startup • Radio resources switched off • RDI on unit $U, interface $IF • Receiving failure in Optical Interface • RF BB bus configuration error • RF BB bus connection transmission error • RF loss of secondary optical interface • RF Module blocked • RF Module configuring failed • RF Module critical file not found • RF Module filter input power missing • RF Module gain adjusting failure • RF Module out of order • RF Module power output faulty • RNW parameter mismatch • Routing misconfiguration for application $a • RP3-01 link conflict • RS485 IUANT port failure • RX out of order • S1 interface recovery failure • S1 interface setup failure • S1 SCTP path failure • SRAM operation failure • SRIO chain configuration was rejected • SyncE SSM Timed Out on unit $UID, interface $IF • SW corrupted • SW fallback

DN0980455 15



• Synchronization lost • System information broadcast parameters overflow • System Module failure • Temperature alarm • Temperature too low (heating ongoing) • Toggling: <Fault name> • Transport layer connection failure in S1 interface • Transport layer connection failure in X2 interface • Transport module missing: $unit • TWAMP PLR Threshold Crossed • TWAMP RTT Threshold Crossed • TX failure in MIMO • TX out of order • Unit (module) dangerously overheating • Unit blocked • Unit initialization failure • Unit not supported by current BTS SW version • Unit SW download failed • Unit temperature is high • Vendor BTS certificate due to expire • VSWR major alarm • VSWR minor alarm • X2 interface recovery failure

Removed faults:

• Antenna link is down • Automatic BTS Operator Certificate retrieval unsuccessful • BB bus message collision error • BTS SW download or activation failed • Firmware SW mismatch • GPS Receiver alarm: control interface not available • GPS Receiver alarm: not tracking satellites • High memory consumption • Incoherency with RF Modules • Invalid frequency channel for the BTS HW • Post test failed • PPS reference missing • Unit synchronization failed • Unknown product code • X2 neighbor cell configuration inconsistency

Changes between issues 04B (2013-01-23, RL40) and 04C (2013-04-22, RL40)New faults:

• High memory consumption • Loss of primary Opt IF

Modified faults:

16 DN0980455



Summary of changes

• File System access failed • SW fallback

DN0980455 17

Flexi Multiradio BTS LTE Faults Overview of Flexi Multiradio BTS LTE faults

Id:0900d805809667b0Confidential

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.

18 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 19

Flexi Multiradio BTS 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:

Used when there is more than one unit status possible. In case multiple unit status options are possible, unit status depends on the fault source.

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

20 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


7656 BASE STATION CONNECTIVITY LOST

7657 BASE STATION CONNECTIVITY DEGRADED

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.

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 21

Flexi Multiradio BTS LTE Faults Flexi Multiradio BTS LTE faults


4 Flexi Multiradio BTS LTE faults

4.1 # autonomous reset as recovery action

Fault ID and name 52: EFaultId_UnitAutonomousResetAl

Used in products FlexiBTS, LTE

Detecting unit FCM/FCT

Source FCM/FCT, FR, FSP

Meaning The BTS tries to correct a fault situation by performing a recovery reset to a unit, the site or the BTS. In case of RF module reset in RF chaining configura-tion BTS resets also all RF modules that are further in chain.

State Transient

Unit status Working

Unit status attributes

Effect The BTS is operational.

Reported alarms 7652 BASE STATION NOTIFICATION

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.

Related faults

22 DN0980455



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

Fault ID and name 61059: FTM_TIMING_SOURCE_LOS

Used in products LTE

Detecting unit FTLB, FTIB, FSM, FTIF

Source STPG

Meaning One of the synchronisation sources in the configured priority list is unavailable. This can be the primary or the secondary clock source. In the alarm: Protocol can be PDH, Timing over Packet (ToP) and Synchronuous ethernet. Unit Number is optional: -For PDH and Synchronous Ethernet, Unit number is 0 or 1. -It is not present for Timing Over Packet(TOP). The interface value is optional: - For PDH the value range depends on the hardware unit type: 1..16 - For Synchonuous Ethernet the value range = 1..3 - It is not present for Timing over Packet.

State Start / Cancel

Unit status Minor


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

Reported alarms 7665 BASE STATION TRANSMISSION ALARM

LED display Stable Green

Instructions Use BTS Site Manager to check which interfaces have been configured assynchronization sources. For all interfaces, 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, connecta loop cable and check whether the alarm disappears. Monitor the received clock quality.

Related faults

DN0980455 23



4.3 10b8b coding error in optical interface device <opt link/RP3>

Fault ID and name 2004: EFaultId_OIC_LVDSRecAl


Detecting unit FCM, FCT

Source OptIF

Meaning The fibre cable has an interference; the data becomes faulty. A physical con-nection failure between the optical interface and the summing function (caused by bad circuit joints, for example).


Unit status Degraded


Effect The cell operation is degraded. The optical interface loses its synchronization if the amount of errors exceeds the defined limit.

Reported alarms 7654 CELL OPERATION DEGRADED

LED display Blinking red(optical interfaces)

Instructions 1. Reset the RF Module behind the faulty optical interface by blocking/unblock-ing it. 2. If that does not clear the fault situation, replace the RF Module that causes the alarm. 3. Reset the System Module. 4. If the System Module is the only source causing the alarm, or actions men-tioned above do not clear the fault situation, replace the System Module that causes the alarm.

Related faults Failure in optical RP3 interface3030: EFaultId_FailureInOptical_Rp3Interface

24 DN0980455


Id:0900d80580a300ecConfidential

4.4 2M external reference missing

Fault ID and name 1899: EFaultId_2MExtRefMissAl



Source FCM/FCT

Meaning The reference clock monitoring has detected a loss of 2.048MHz signal received from an external reference source, connected to Sync In interface of the System Module.




Effect If other references are available, the synchronization reference source changes to another source. Tuning then follows this new reference. If other ref-erences are not available, the BTS master clock (OCXO) tuning is halted and the BTS synchronization drops to holdover mode.

Reported alarms 7651 BASE STATION OPERATION DEGRADED


LED display Blinking red

Instructions Note! Perform the steps below in the listed order until the alarm disappears. 1. Check the cabling (connected to Sync In interface). 2. Check if the 2.048MHz reference source is working normally and the 2.048MHz signal is available. 3. Replace the alarming module.

Related faults BTS reference clock missing3080: EFaultId_BtsReferenceClockMissing

DN0980455 25


Id:0900d80580a300cdConfidential

4.5 3GPP/AISG communication administratively disabled

Fault ID and name 4142: EFaultId_Communication3gppAdministrativelyDisabledAl



Source ALD

Meaning HDLC link is disabled for reporting Antenna Line or IUANT port.


Unit status Out of order


Effect HDLC link will be disabled on reporting Antenna Line or IUANT port.



LED display STABLE GREEN

Instructions To revert change,the Communication3gppEnabled parameter should be enabled for reporting Antenna Line.

Related faults

26 DN0980455


Id:0900d80580a3002eConfidential

4.6 [User defined]

Fault ID and name 1400: EFaultId_ExtAl0

1401: EFaultId_ExtAl1



























Source FCM, FCT

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

DN0980455 27



LED display N/A

Instructions [User defined]

Related faults

28 DN0980455


Id:0900d80580a3003aConfidential

4.7 Address mismatch in summing

Fault ID and name 2019: EFaultId_Muksu_SsubMmAl



Source FCM, FCT, FSP

Meaning There is a baseband bus address mismatch in the summing. There are two possible causes: 1. A configuration error (two different baseband units function-ing) - after an acknowledgement the fault returns. 2. Data corruption on the bus - appears once when unsynchronized data is sent by the baseband.




Effect RP3 traffic from the baseband is malfunctioning. The System Module operation is degraded.



Instructions Check the antenna mapping to the local cells in the commissioning file.

Related faults Baseband Bus failure3020: EFaultId_BaseBandBusFailure

DN0980455 29



4.8 AIS on unit $U, interface $IF

Fault ID and name 61151: FTM_AIS



Source PPTT

Meaning Alarm indication signal is received. This signal is generated by an intermediate PDH device in the forward direction because it detects a problem in its receive signal. All other transmission alarms related to this signal are suppressed. Probable cause: There is a transmission problem somewhere in the intermedi-ate 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.

Related faults

30 DN0980455



4.9 Antenna Carrier configuration failure

Fault ID and name 6259: EFaultId_AntennaCarrierMessageFailed



Source TX1-n/RX1-n

Meaning Antenna carrier resources were not successfully set up during cell setup or cell deletion procedure because of failure of RX or TX resource. Affected cell might be not operational.

State Start



Effect Affected cell might be not fully operational.

Reported alarms 7653 CELL FAULTY


LED display N/A

Instructions Perform the steps below in the listed order until the BTS fault disappears.1.Check cables towards Radio Module2.Reset Radio Module3.Remove faulty unit

Related faults RF Module failure3010: EFaultId_RfModuleFailure

DN0980455 31



4.10 Antenna Line Device failure

Fault ID and name 3100: EFaultId_AntennaLineFailure


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


7653 CELL FAULTY



LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disappears. 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.

32 DN0980455



Related faults No connection to unit10: EFaultId_NoConnectionToUnitAl

Antenna line device HW failure1847: EFaultId_HardwareErrorAl

Communication failure1806: EFaultId_CommunicationFailureAl

Antenna Line Device Operation Failure1871: EFaultId_BusyAl1872: EFaultId_FormatErrorAl 1873: EFaultId_UnsupportedProcedureAl 1874: EFaultId_OutOfRangeAl

DN0980455 33



4.11 Antenna line device HW failure

Fault ID and name 1847: EFaultId_HardwareErrorAl


Detecting unit FR, TILT

Source RX, TX, TILT, MHA, EFIL

Meaning A hardware failure detected by an antenna line device. Usually this is a perma-nent fault (the hardware is broken).




Effect The antenna line device is not working properly. The cell operation is degraded.



LED display Stable Green (7652) Alternating Red and Green (7654)

Instructions 1. Block/unblock the Radio module to give a power-off reset to the antenna line devices. 2. If that does not help, replace the antenna line device.

Related faults Antenna Line Device failure3100: EFaultId_AntennaLineFailure

34 DN0980455


Id:0900d80580a300e9Confidential

4.12 Antenna line device missing software

Fault ID and name 1848: EFaultId_WorkingSoftwareMissingAl


Detecting unit MHA, TILT

Source MHA, TILT

Meaning The unit is in Download Mode State.




Effect The device is out of use.



LED display N/A

Instructions 1. Replace the antenna line device.

Related faults

DN0980455 35


Id:0900d80580a3003dConfidential

4.13 Antenna Line Device Operation Failure

Fault ID and name 1871: EFaultId_BusyAl

1872: EFaultId_FormatErrorAl

1873: EFaultId_UnsupportedProcedureAl

1874: EFaultId_OutOfRangeAl


Detecting unit FSM

Source Flexi Filter, FA, AISG MHA, TILT

Meaning The device is not working properly, the configuration is not valid, or a given parameter is incorrect.




Effect Some antenna line device functions may not work properly.



LED display Blinking red (Filter), Stable green (other)

Instructions 1. Check the functionality of the antenna line device. 2. Check the compatibility between the antenna line device and the BTS. 3. Check that the given parameters are in the valid range.

Related faults Antenna Line Device failure3100: EFaultId_AntennaLineFailure

36 DN0980455


Id:0900d80580a3000cConfidential

4.14 Antenna line failure

Fault ID and name 1836: EFaultId_ALOvercurrentAl


Detecting unit Flexi Filter, FR

Source Antenna line

Meaning Radio Module (60W RRH) or Filter (all others) has detected overcurrent on the antenna line. 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.




Effect The antenna line is not operating correctly. The cell capacity decreases.


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

Instructions 1. Check the antenna line and antenna line devices. Fix or replace the faulty parts/devices.2. Alarm is cancelled only at RF Module reset or BTS reset.

Related faults

DN0980455 37


Id:0900d80580a300b8Confidential

4.15 Antenna line faulty

Fault ID and name 4045: EFaultId_AntennaLineFaultyAl


Detecting unit FR

Source Antenna line

Meaning An alarm message has been received from the antenna line. The antenna line is faulty.




Effect The antenna line is not operating correctly. The cell is disabled.



LED display Periodic red and green

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

Related faults

38 DN0980455



4.16 Antenna line operation degraded

Fault ID and name 4046: EFaultId_AntennaLineDegradedAl


Detecting unit FR

Source Antenna Line

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 correctly. The cell capacity decreases.


LED display Periodic red and green (RF working, Antenna Line degraded)

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

Related faults

DN0980455 39


Id:0900d80580a300ddConfidential

4.17 Antenna line switched off

Fault ID and name 1957: EFaultId_AntennaLineSwitchedOffAl


Detecting unit FR

Source Antenna line

Meaning Antenna line has been disabled to protect HW, that is because of high reflection conditions.

State Start



Effect The cell is disabled. Downlink signal transmission on the given antenna line is disabled and corresponding FR transmitter is unusable, hence overall FR state is affected.



LED display Stable red (all antenna lines of the RF module are faulty); Blinking red (not all antenna lines of the RF module are faulty)

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

Related faults

40 DN0980455



4.18 Antenna link is down

Fault ID and name 476: EFaultId_Rp3BusError


Detecting unit FSPC

Source FSP, FSM

Meaning Antenna (RP3) link is down: transmitter or receiver drops from synchronization.

State Start



Effect BTS is not operational or the capacity is degraded.

Reported alarms 7650 BASE STATION FAULTY


LED display Stable red (7650), Blinking red (7651)

Instructions 1. If the alarming module is the System Module (FSM1), restart BTS.2. If that does not help, replace the alarming FSM.


Failure in replaceable baseband unit3003: EFaultId_FbiaFailureAl

DN0980455 41


Id:0900d80580a300a1Confidential

4.19 Auto-negotiation mismatch, on unit $U, Ethernet interface $IF

Fault ID and name 61607: AUTO NEGO MIS MATCH


Detecting unit FTIB, FTFB, FTLB

Source ETHLK

Meaning This alarm indicates that there is a mismatch between BTS configuration and auto-negotiation result.


Unit status Major


Effect If the alarm is active, then potentially there is a synchronization loop


LED display None

Instructions Try with local management or site support equipment.

Related faults

42 DN0980455



4.20 Automatic BTS Operator Certificate retrieval unsuccessful

Fault ID and name 61510: NO_CERTIFICATE



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). A requested certificate could not be retrieved as the number of certificates received from repository server (RA) or certificate authority (CA) are more than expected.


Unit status Major


Effect The requested service is not available.



Instructions Provide the certificate.

Related faults

DN0980455 43



4.21 Automatic cell recovery not possible

Fault ID and name 6277: EFaultId_AutomaticCellRecoveryNotPossible


Detecting unit FCT

Source LCR

Meaning Base station executed baseband board (FSP) recovery activities. All baseband boards are available again but not all cells could be restored. To restore the functionality of remaining cell, a base station reset is required.

State Start



Effect The cell that cannot be recovered remains unavailable.


LED display None

Instructions Reset (block/unblock) the BTS in order to recover the faulty cell.

Related faults

44 DN0980455



4.22 Base Station configuration alignment lost alarm

Fault ID and name 4171: EFaultId_BaseStationConfigurationAlignmentLostAl



Source FCM (FSMr2), FCT (FSMr3)

Meaning The configuration data alignment between BTS and NetAct is lost. No Ack or any nackReason from OMS for Configuration Change Notifications (CCN) or buffered CCNs is lost because too long BTS O&M interface connection break.


Unit status Working

Unit status attributes Working: There is only misalingment in NetAct database and BTS is working normally.

Effect The BTS continues working normally with all cells.


LED display N/A

Instructions Upload BTS configuration from NetAct.

Related faults

DN0980455 45



4.23 Baseband bus configuration of <x> was rejected

Fault ID and name 1811: EFaultId_BbBus_ConfFailedAl


Detecting unit FCM/FCT, FSP

Source FSM/FCT, FSP, OptIF

Meaning The baseband bus related configuration of <x> was rejected by the HW SW, DSP or RF SW.

State Start



Effect This fault prevents the BTS from functioning. Depending on <x>, some pro-cessing resources, some cells, or the whole BTS are out of order.



7653 CELL FAULTY


LED display Stable red ( 7650); Blinking Red (7651)

Instructions Replace the alarming module.

Related faults Baseband bus failure3020: EFaultId_BaseBandBusFailure

46 DN0980455



4.24 Baseband bus failure

Fault ID and name 3020: EFaultId_BaseBandBusFailure


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




7653 CELL FAULTY



LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disappears. 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 blocking/unblocking it. b. Reset the System Module by blocking/unblocking 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.

DN0980455 47



Related faults Baseband bus configuration of <x> was rejected1811: EFaultId_BbBus_ConfFailedAl

Not able to synchronize baseband bus with <x>1815: EFaultId_BbBus_SyncFailedAl

RF BB Bus Synchronization Error1904: EFaultId_FrRfBbBusSynchError

RF BB Bus Configuration Error1905: EFaultId_FrRfBbBusConfigError

RF BB Bus Connection Transmission Error1906: EFaultId_FrRfBbBusConnTransError

BB bus reception error (summing device)2016: EFaultId_Muksu_SMTimeOffAl

BB bus transmission error2017: EFaultId_Muksu_SRx10b8bAl

BB bus message collision error2018: EFaultId_Muksu_StxPortCollAl

Address mismatch in summing2019: EFaultId_Muksu_SsubMmAl

48 DN0980455


Id:0900d80580a300c3Confidential

4.25 BB bus message in the wrong slot

Fault ID and name 2057: EFaultId_MuksuMsgInWrongSlotAl

Used in products FlexiBTS


Source FSP, OptIF

Meaning Baseband bus message multiplexing slot for the message is not possible to be fulfilled.




Effect The BTS operation is degraded because some of the BTS resources are not available.



7653 CELL FAULTY


LED display Stable Red (7650), Blinking Red (7651), Stable Red (7653, 7654)

Instructions If RF is the source: 1. Check antenna mapping to the local cells in the commissioning file.2. Check the cables between the System Module and RF Module.3. RF block/unblock4. BTS reset 5. Replace the alarming module. If FSP is the source: System Module reset should be performed.


DN0980455 49


Id:0900d80580a300ebConfidential

4.26 BB bus reception error (summing device)

Fault ID and name 2016: EFaultId_Muksu_SMTimeOffAl



Source FSP, optIF

Meaning The master frame in the received baseband bus frame is not in the correct place related to the internally generated master frame pulse. Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place.




Effect The connection to the associated link is lost. The data is partly/completely lost. The worst-case fault effect can expand further from the cell level. This fault can prevent the BTS from operation when the RF Module is needed for the required cell configuration. Fault is visible for the first radio in chain only. Fault 10 is sending for the other FRs, when pooling breaks because of lost sync.



7653 CELL FAULTY


LED display Stable red

Instructions 1. Check the cables between the System Module and the connected module. 2. Replace the unit that causes the alarm (System Module).


50 DN0980455



4.27 BB bus transmission error

Fault ID and name 2017: EFaultId_Muksu_SRx10b8bAl



Source FCM, FCT

Meaning A decoding error has been detected in the baseband internal link. The data packet is lost, or the content is corrupted. This situation is also triggered when the links do not synchronize with each other.




Effect Data traffic to the connected RF Module is malfunctioning. BTS operation is faulty.



Instructions 1. Check the cables between the System Module and RF Module. 2. Reset the System Module. 3. Replace the alarming module (System Module).


DN0980455 51



4.28 BFD $session down, egress, $sourceIP to $destinationIP

Fault ID and name 61606: BFD DOWN Egress



Source BFD

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 diagnostic 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 the BFD configuration at local end.

Related faults

52 DN0980455



4.29 BFD $session down, ingress, $sourceIP to $destinationIP

Fault ID and name 61605: BFD DOWN Ingress



Source BFD

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



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

Related faults

DN0980455 53



4.30 BFD group $bfdGrpId down

Fault ID and name 61022: BFD DOWN



Source BFDGRP

Meaning The alarm is raised if the BFD service is not available anymore on the BTS for all BFD sessions belonging to that BFD group.


Unit status Critical


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



Instructions 1) Check if the far end has BFD switched on.2) Check cabling and network connections to the far end.

Related faults BFD Session down in ingress direction for session $S61605: BFD DOWN Ingress

BFD Session down in egress direction for session $S61606: BFD DOWN Egress

54 DN0980455



4.31 Boot configuration inconsistency detected

Fault ID and name 4102: EFaultId_BootConfigurationInconsistencyAl


Detecting unit (FSMr2): FCM, (FSMr3): FCT

Source FSMr2: FCM, FSP MCU FSMr3: FCT

Meaning During SW update it was detected that configurations of active and passive SW in HW unit are same. Active and passive SW configuration are compared: - before SW download - during SW activation before active and passive SW switch - during start-up

State Start



Effect Newly downloaded SW will overwrite active SW. Therefore, SW download and activation are not allowed. Currently active SW is still running.



LED display stable red (7650) , blinking red (7651)

Instructions Replace the faulty unit.

Related faults

DN0980455 55



4.32 BTS blocked

Fault ID and name 50: EFaultId_BTSBlockedAl



Source FCM (FSMr2), FCT (FSMr3)

Meaning The BTS is blocked with BTS Site Manager. The purpose is to avoid fault indi-cations that might 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.



Instructions To cancel the fault, unblock the BTS. Unblocking the BTS causes a Site Reset (FSMr3) or BTS Reset (FSMr2).

Related faults

56 DN0980455



4.33 BTS config error (Not enough HW for LCR)

Fault ID and name 1868: EFaultId_NotEnoughHwForLcrAl


Detecting unit FCM

Source LCR

Meaning RF Module cannot serve all cells commissioned to the RF module. Or Not enough FSP resources for commissioned cells during BTS startup phase.




Effect The BTS capacity drops.



Instructions RF module:Replace the single or dual PA RF module with a triple PA RF module.Alternatively, recommission the BTS with fewer cells. FSP:1.Block & unblock the system module2.If that does not help, replace the system module

Related faults Configuration error: <x>3070: EFaultId_ConfigurationError

DN0980455 57



4.34 BTS configuration not supported

Fault ID and name 4097: EFaultId_BtsConfNotSupportedAl


Detecting unit FCT

Source FSP

Meaning FSP does not support requested BTS configuration.

State Start



Effect BTS baseband processing power is decreased. If all FSPs are faulty BTS is not operational.




Instructions Note! Perform the steps below in the listed order until the fault disappears.1. Change BTS configuration.2. Reset BTS.


58 DN0980455



4.35 BTS file error

Fault ID and name 1802: EFaultId_FileRequestFlashAl


Detecting unit FCM [FSMr2] / FCT [FSMr3]

Source FCM, FSP [FSMr2] / FCT, FSP [FSMr3]

Meaning BPF file or optical interface FPGA file is invalid or missing. The FSP MCU SW file is invalid or missing.

State Start

Unit status Out of order;Working

Unit status attributes Working if there have been problems with the files in the SW package but the BTS is still operational. Out of order when the problems prevents the BTS from reaching the operational state.

Effect The BTS is not operating.




LED display Stable red (7650), Blinking red (7651), Stable green (7652)

Instructions Note: Perform the following steps in the listed order until the fault disappears: 1. Use BTS Site Manager to perform a full commissioning to the BTS using the NetAct backup upload SCF file as template. 2. Download two different software packages so that the faulty file is removed from the BTS. 3. Download the software again. 4. Replace the System Module.

Related faults BTS internal SW management problem3090: EFaultId_BtsInternalSwManagementProblem


DN0980455 59



4.36 BTS internal SW management problem

Fault ID and name 3090: EFaultId_BtsInternalSwManagementProblem


Detecting unit FSM

Source FSM, FCT, 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 the BTS might be not operational at all (BASE STATION FAULTY).






LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disappears. 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 blocking/unblocking it. b. Reset the System Module by blocking/unblocking it. 3. Update and activate the SW to the BTS. 4. Check the SW files. 5. Replace the alarming module.

60 DN0980455



Related faults BTS SW download or activation failed29: EFaultId_FileCorruptionAl 30: EFaultId_SwUpdateAl

File corrupted in SW download28: EFaultId_SwPackageAl

Flash operation failure214: EFaultId_FlashWrAl215: EFaultId_FlashRdAl216: EFaultId_FlashEraseAl217: EFaultId_FlashDrvAl218: EFaultId_FlashDbChksumAl

BTS file error1802: EFaultId_FileRequestFlashAl

SW corrupted1850: EFaultId_SwCorruptedAl4029: EFaultId_SwCorruptedPermanentAl

Unit SW download failed6: EFaultId_SwDownloadAl

BTS vendor specific file fault6262: EFaultId_InvalidVendorSpecificFile

Fault diagnostics rule file error1866: EFaultId_RulesMissingAl1867: EFaultId_RulesParsingAl

DN0980455 61



4.37 BTS is uncommissioned

Fault ID and name 4030: EFaultId_NoCommDataAl


Detecting unit FCM / FCT

Source FCM (FSMr2) / FCT (FSMr3)

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

State Start

Unit status Working


Effect The BTS is not commissioned.


LED display N/A

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

Related faults

62 DN0980455



4.38 BTS master clock tuning failure

Fault ID and name 1818: EFaultId_Ov_OscAl



Source FCM/FCT

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. When the DAC value is 0 or 4095, the effect depends on the network synchronization setting defined in the BTS commissioning. Effects in FDD Frequency Synchronization mode: Assuming that the BTS reference signal has correct accuracy when the DAC value reaches the adjustment limit 0 or 4095 (meaning the alarm indication is real, not caused by incorrect refer-ence), the BTS air interface starts to drift from the correct value and after a while (weeks...months) the 3GPP accuracy limit is not met any more. Even in that stage the BTS might still be operational but the system performance might drop, affecting for example to handovers. Effects in FDD Phase Synchroniza-tion mode: When the DAC value reaches the adjustment limit 0 or 4095 the basic LTE system operation effects are the same as in Frequency Synchroni-zation mode but the LTE feature(s) which require Phase Synchronization become(s) non-operational because the OCXO cannot adjust the phase syn-chronization any more.



DN0980455 63



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 frequency counter (note: requires a good timebase for the counter). The reference 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.

Related faults

64 DN0980455



4.39 BTS reference clock missing

Fault ID and name 3080: EFaultId_BtsReferenceClockMissing


Detecting unit FSM

Source FSM

Meaning This BTS fault indication is generated if the reference clock monitoring function of the BTS does not receive the highest configured synchronization reference signal or if all the synchronization reference signals are missing. The BTS fault is not generated if the highest configured synchronization 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 reference signal coming from the integrated transmis-sion unit (FTM). Normally, all the FlexiBTS sources are not in use at the same time (it depends on the network planning and BTS configuration). During the BTS start-up, the available sources are checked against the reference source list in the BTS commissioning file and deviations 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 selection 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.


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 syn-chronization sources as a reference for tuning the OCXO and the OCXO is in holdover mode, using the last calculated tuning control value. The fault situa-tion does not affect the BTS air interface stability, but if the fault situation lasts for a long time, the accuracy starts to drift slowly. However, it might take several weeks before the BTS/RAN operations start to be affected because of the very small OCXO aging factor.



LED display N/A

DN0980455 65



Instructions Depending on the installed and commissioned 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 indication 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 might be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver. 3. There might be a malfunction in the BTS. Perform a BTS site reset. 4. The GPS cable and/or connectors might be damaged. Check the cable and the connectors. 5. There might 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 commissioned 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 might be a malfunction in the BTS. Perform a BTS site reset. FTM reference (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 syn-chronization 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 synchronization priority setting) might be missing, causing the FTM's internal clock to drop to holdover mode. In this case, the fault in the transmission NETWORK must be corrected (FTM itself might be working fine). 2. Check the alarms of the FTM unit and act accordingly. 3. Check the synchronization settings of the FTM unit. 4. There might be a malfunction in the BTS. Perform a BTS site reset. 5. There might be an equipment failure in the FTM unit. Check the operation and replace the unit, if needed. Note: Normally, the reason is not an equipment failure, but there might be connection failures in the transmission or packet

66 DN0980455



network, causing the FTM clock to drop to holdover mode. Especially the BTS fault indication activity (frequent BTS fault indication activations/cancels instead of a stable BTS fault indication state) points to the instability of the transmission network, not to a failure in the unit. If the previous steps do not help, there might be an equipment failure in the System Module. Check the operation and if performing a BTS site reset does not help, replace the System Module.

Related faults Transmission clock missing 1816: EFaultId_Trans_Clk_MsgAl

PPS reference missing 1898: EFaultId_PpsRefMissAl

2M external reference missing 1899: EFaultId_2MExtRefMissAl

DN0980455 67



4.40 BTS reset required

Fault ID and name 61010: FTM_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 Major


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


LED display Blinking Red

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

Related faults

68 DN0980455



4.41 BTS reset required

Fault ID and name 4001: EFaultId_BtsResetNeededAl


Detecting unit FSM

Source FR, FSP

Meaning The BTS detected an RF Module that cannot be put into use without a BTS reset. The RF Module type differs from the previous one or the RF module was not present during startup. FSP overheat occurred. Restoring the FSP normal temperature and resetting BTS is needed to put the card back into use. BTS startup: No FSP units detected by the time RP3 configuration starts.




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



7653 CELL FAULTY



Instructions Reset (block/unblock) the BTS.

Related faults

DN0980455 69


Id:0900d80580a300acConfidential

4.42 BTS reset time increased

Fault ID and name 4091: EFaultId_BtsResetTimeIncreasedAl


Detecting unit FSM

Source FSM

Meaning BTS has detected RF module power cycle failure and is trying to recover from the failure during BTS reset procedure. BTS reset will last longer due to addi-tional actions performed by BTS to recover from faulty situation.

State Start

Unit status Working


Effect Ongoing BTS reset will last longer.



Instructions None

Related faults

70 DN0980455


Id:0900d80580a300d6Confidential

4.43 BTS SW download or activation failed

Fault ID and name 29: EFaultId_FileCorruptionAl

30: EFaultId_SwUpdateAl



Source FlexiBTS: FCM (FSMr2) / FCT (FSMr3), FR

Meaning The SW update to the BTS has failed. The error can be caused by a module reset during the SW update, a hardware problem in the module or a corrupted flash file system.


Unit status Degraded;Working

Unit status attributes Working - if incompatible software version has been detected on the same unit and corresponding fault 23:EFaultId_IncompatibleSwVersionAl has been already reported. Degraded - in any other case.

Effect If the SW download to any HW unit failed, eNB continues operating with the cur-rently running SW version. If the SW activation failed on FCM/FCT in the master FSM, eNB continues operating with the currently running SW version. If the SW activation failed on another HW unit (for example, RF unit), then: i. eNB restarts and operates with the new SW version installed ii. eventually, if eNB is integrated to NetAct, after the automatic recovery SW update, eNB restarts and operates with the old SW version installed




LED display Blinking red (7651, 7654)

Instructions 1. Retry the SW update.2. If other flash memory-related faults are active for the alarming module at the same time, replace the alarming module.


DN0980455 71



4.44 BTS time not corrected

Fault ID and name 26: EFaultId_NtpTimeNotSetAl



Source FCM/FCT

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 incorrect time.



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

Related faults

72 DN0980455



4.45 BTS Trust Anchor expired or due to expire

Fault ID and name 61618: TRUST_ANCHOR_EXPIRING



Source FTM

Meaning NE stores trust anchors for its own trust chain. When own bts trust anchors are about to expire this alarm is sent.

State Active / Cleared

Unit status Major


Effect



Instructions Update trust anchors.

Related faults

DN0980455 73



4.46 BTS vendor-specific file fault

Fault ID and name 6262: EFaultId_InvalidVendorSpecificFile



Source FSM

Meaning There was an opening, reading, or file content problem with a BTS vendor-specific file at BTS startup.

State Start



Effect BTS startup is interrupted and the BTS is not operational.



Instructions Note: Perform the steps below in the listed order until the BTS fault disappears. 1. Check the other active BTS faults. 2. Reset the System Module by blocking/unblocking it.3. Update and activate the SW to the BTS.4. Check the SW files.5. Replace FSM.


74 DN0980455



4.47 CCM fault level $ prio $p cause $c

Fault ID and name 61410: Ethernet OAM CCM fault



Source OAMMA, OAMMD

Meaning The alarm is triggered whenever a service OAM error related to the transmis-sion of Continuity Check Messages (CCM) persists on a given Ethernet inter-face as soon as one of the error condtions below occurs. The following alarms are defined: 1) MDL_MISMATCH, priority 5 (highest priority): CCM is received with MDL lower than the highest configured one in the BTS and not matching any of the configured ones. Ex: CCM fault level - prio 5 cause MDL_MISMATCH 2) MAID_MISMATCH priority 5: CCM is received with MDL which is configured in the BTS, but with MAID not matching any MA configured in the BTS on this MDL. Ex:CCM fault level 5 prio 5 cause MAID_MISMATCH 3) MAID_MISMATCH priority 5:CCM is received with matching MDL and MAID, but the VLAN membership of the received frame does not match the VLAN con-figuration of the addressed MA. Ex:CCM fault level 5 prio 5 cause MAID_MISMATCH 4) ERR_CCM, priority 4:CCM is received with known MDL and MAID, but MEPID is not configured in the Remote MEP list of the MA. Ex: CCM fault level 5 prio 4 cause REMOTEMEP_NOT_CONFIGURED 5) ERR_CCM, priority 4: CCM is received with known MDL, MAID and MEPID, but CCM interval coded in the received CCM does not match the interval config-ured in the BTS. Ex: CCM fault level 5 prio 4 cause WRONG_CCM_INTERVAL 6)REMOTE_CCM, priority 3: CCM was not received for 3.5 intervals from atleast one remote MEP in the MA. Ex: CCM fault level 5 prio 3 cause REMOTE_CCM_DEFECT 7) RDI_CCM, priority 1 (lowest priority): RDI flag detected in the CCM frames from one remote peer. Ex: CCM fault level 5 prio 1 cause REMOTE_DEFECT_INDICATION The alarm shall display the follow-ing information: - Alarm Name - Alarm Priority - Alarm cause: if difference sources produce the same alarm - MD level at which the alarm was detected


Unit status Major


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



Instructions 1) Check cabling.2) Check CCM configuration at remote peer.

Related faults

DN0980455 75


Id:0900d80580a300dfConfidential

4.48 Cell blocked

Fault ID and name 49: EFaultId_CellBlockedAl


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 cancella-tions 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.

Related faults

76 DN0980455



4.49 Cell configuration data distribution failed

Fault ID and name 6253: EFaultId_CellSetupFailed


Detecting unit FCM,FCT

Source LCR

Meaning BTS raises this fault if it experiences a problem in internal configuration data distribution (cell setup) to C- and U-Plane SW components

State Start



Effect Cell is disabled


LED display N/A

Instructions Block/unblock BTS

Related faults

DN0980455 77


Id:0900d80580a300eeConfidential

4.50 Cell power failure

Fault ID and name 4090: EFaultId_TxCarrierInputPowerLowAl


Detecting unit FSM

Source LCR

Meaning Flexi Radio Module has detected low downlink carrier input power from the Flexi System Module.

State Start



Effect The cell is disabled.


LED display None

Instructions 1. Check the other active alarms and act accordingly.2. If that does not help, block/unblock the system module.3. FSMr2: If that does not help, replace the system module. FSMr3: If the faulty cell is on the baseband extension module, replace the extension module.

Related faults

78 DN0980455



4.51 Cell reconfiguration data distribution failed

Fault ID and name 6257: EFaultId_CellReconfigurationFailed



Source LCR

Meaning BTS raises this fault if it experiences a problem in internal configuration data distribution (cell setup) to C-Plane and U-Plane SW components.

State Start



Effect Cell is disabled


LED display N/A

Instructions Block/unblock BTS

Related faults

DN0980455 79



4.52 Commissioning error: <x>

Fault ID and name 3060: EFaultId_CommissioningError



Source FSM, FR, FT

Meaning Some of the commissioning parameters 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 fault situation might have no impact on the operation (BASE STATION or CELL NOTIFICATION), 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 disappears. 1. Check the commissioning parameters with the BTS Site Manager Commis-sioning Wizard. 2. Load the correct commissioning file to the BTS.

Related faults Transmission parameters missing1825: EFaultId_PublicIPmissingAl

Invalid Configuration file4036: EFaultId_InvalidConfigurationFileAl

Incorrect radio network parameters6252: EFaultId_FailureInNetworkPlanFile

Radio master conflict4038: EFaultId_RadioMasterConflictAl

80 DN0980455



4.53 Communication failure

Fault ID and name 1806: EFaultId_CommunicationFailureAl



Source FCM/FCT, FSP, FTM, FR, FF, MHA, RET

Meaning Communication with an application failed. It has not replied to the message that has been sent/resent to it.




Effect Some action inside the BTS is interrupted. The BTS does not operate normally. The fault is in the unit reported in the fault source field.



7653 CELL FAULTY


LED display Stable red (7650) / (7653), Blinking red (7651) / (7654)

Instructions 1. Make sure that the unit/module is properly connected. If the unit/module LED does not light up, the unit/module is faulty. Check the alarming unit/module. 2. Check the fault history.

Related faults System Module failure 3000: EFaultId_SystemModuleFailure

Failure in optical RP3 interface 3030: EFaultId_FailureInOptical_Rp3Interface

Antenna Line Device failure 3100: EFaultId_AntennaLineFailure

No connection to Flexi transport submodule 3511: EFaultId_NoConnectionToFtAl

DN0980455 81



4.54 Configuration error: <x>

Fault ID and name 3070: EFaultId_ConfigurationError


Detecting unit FSM

Source FSM, FR, Antenna Line, 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 config-uration.

State Start

Unit status N/A


Effect Depending on the reported alarms, the fault situation might have no impact on the operation (BASE STATION NOTIFICATION), 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).




7653 CELL FAULTY



LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disappears. 1. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration. 2. Check that the BTS cell parameters from the Network management system matchthe BTS HW configuration (for example frequency, power). 3. Check the Network management system alarms for the alarming local cell (LCR). 4. Recommission the BTS to ensure that all parameters are correctly config-ured.

82 DN0980455



Related faults Unit initialization failure12: EFaultId_TcomConfigAl 4040: EFaultId_InitFaultManAl

Unknown HW resource94: EFaultId_UnknownUnitType

Unit not supported by current BTS SW version95: EFaultId_NotSupportedUnit

Invalid frequency channel for the BTS HW1807: EFaultId_InvalidFrequencyChannelForBTSHW

Incoherency in cell configuration1856: EFaultId_IncoherencyInCellConfigurationAl

Incoherency with RF Modules1857: EFaultId_IncoherencyWithRFModulesAl

BTS config error (Not enough HW for LCR)1868: EFaultId_NotEnoughHwForLcrAl

Incoherency in cell configuration4000: EFaultId_IncoherencyInConfiguration

Incoherency In Cell Configuration4044: EFaultId_IncoherencyCellConfigurationAl

BTS configuration not supported4097: EFaultId_BtsConfNotSupportedAl

DN0980455 83


Id:0900d80580a3002bConfidential

4.55 Configuration file corrupted

Fault ID and name 1924: EFaultId_FrConfigurationFileCorrupted


Detecting unit FRx/LTX

Source LTX/TX1-n/RX1-n

Meaning The RF Module SW detected conflicting or corrupted configuration data.




Effect The default configuration is used and the cell TX and/or RX performance is degraded. There can be problems in the calls through the affected cell(s).



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


84 DN0980455



4.56 Cooling fan broken

Fault ID and name 4078: EFaultId_FanBrokenAl


Detecting unit FCT

Source Fan/Fan group

Meaning Fan(s) are not running although the control is higher than 0.


Unit status Out of order;Degraded

Unit status attributes Not all fans failed: alarming fan = out of order, fan group = degraded All fans failed: all fans and fan group = out of order

Effect If the fans do not rotate as requested, there is a risk that the module tempera-ture rises too high.


LED display Stable Red(Fan Group Out Of Order), Stable Yellow(FAN Group Degraded)

Instructions 1. Check that the fan is not blocked. 2. Check that the fan connector is properly mounted. 3. If that does not help, replace the fan.

Related faults Fan failure3050: EFaultId_FanFailure

DN0980455 85



4.57 Cooling fan broken: <X>

Fault ID and name 1933: EFaultId_FrFanBroken


Detecting unit FR/RFSW

Source FAN, FAN_GROUP

Meaning Fan(s) are not running.



Unit status attributes Not all fans failed: Module = Degraded, Fan group = degraded All fans failed: Module = Degraded, Fan group = Out Of Order



LED display FR module LED: Blinking red (7652, Fan Group Degraded), Blinking red (7652, Fan Group Out of Order).

Instructions 1. Check if the fan connector is properly mounted. 2. If that does not help, replace the fan module.


86 DN0980455



4.58 Cooling fan has reduced from the set speed

Fault ID and name 1934: EFaultId_FrFanReducedSetSpeed



Source Fan supervision

Meaning Fan(s) are rotating slower than requested.



Unit status attributes Module = Degraded, Fan group = degraded



LED display Stable/Blinking Yellow

Instructions 1. Check if the fan connector is properly mounted. 2. If that does not help, replace the fan module.


DN0980455 87


Id:0900d80580a300aaConfidential

4.59 Cooling fan is over speeding

Fault ID and name 4080: EFaultId_FanOverSpeedAl


Detecting unit FCT


Meaning Fan(s) are running faster than requested.




Effect If the fans rotate faster than requested, unnecessary noise appears.


LED display None

Instructions Replace the fan(s).


88 DN0980455



4.60 Cooling fan is over speeding

Fault ID and name 1935: EFaultId_FrFanOverSpeed



Source RFSW

Meaning Fan(s) rotate faster than requested.


Unit status Working


Effect If the fans rotate faster than requested, they cause unnecessary noise.


LED display None

Instructions Replace the fan module.


DN0980455 89



4.61 Cooling fan speed decreased

Fault ID and name 4079: EFaultId_CoolingFanSpeedDecreasedAl


Detecting unit FCT


Meaning Fan(s) speed is deviating too much from the requested control.



Unit status attributes Alarming fan = degraded, fan group = degraded

Effect If the fan(s) do not rotate as requested, there is a risk that the module temper-ature rises too high.


LED display Stable Yellow

Instructions 1. Check if the fan is not blocked. 2. Check if the fan connector is properly mounted. 3. If that does not help, replace the fan.


90 DN0980455


Id:0900d80580a300bcConfidential

4.62 Critical BER detected on the optical connection to Radio Module

Fault ID and name 1956: EFaultId_CritBerOnRp3


Detecting unit FRx / LTX

Source FR

Meaning Abnormally high bit error rate has been detected on the optical link to radio module which results in permanent baseband processing failure. I/Q data stream cannot be successfully processed by FRM due to the burst of consec-utive LCV errors.

State Start



Effect Calls and data transmissions are not possible through the affected cell(s).

Reported alarms


Instructions Note! Perform the steps below in the listed order until the fault disappears.1. Check the optical connection between system module and FR module. Check SFP module(s) and/or readjust optical connectors and verify operation of any devices in the optical network between FSM and FRM, if such devices are in use.2. Block/unblock the FR module. 3. If the problem still exists, reset the site by blocking/unblocking the BTS. 4. If that does not help, replace the SFP module(s) in which the malfunctioning optical connection is terminated and/or replace the fiber.

Related faults

DN0980455 91



4.63 Critical bit toggling error

Fault ID and name 6701: EFaultId_CriticalBitTogglingError


Detecting unit FSP

Source FSP

Meaning Non correctable bit toggling error is detected in the critical DSP memory.

State Start

Unit status Working


Effect Critical impact on FSP operation.



Instructions Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the System Module. 2. Replace the System Module.

Related faults

92 DN0980455



4.64 CRL update failure due to $cause

Fault ID and name 61074: CRL Update failure



Source CERTH

Meaning This alarm is raised if the BTS cannot update the Certificate Revocation List (CRL) for one of the following reasons: - LDAP binding failure - LDAP search is empty (no CRL found) - LDAP search containing multiple entry - CRL signature validation failure - CRL file exceeding BTS storage limit - BTS certificate being part of the CRL - DNS resolution failure - DNS resolution contains multiple IP's - LDAP URL not supported by BTS General failure reasons could be invalid/incorrect CRL content, failed to store the CRL file due to permission error, etc.


Unit status Major


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



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

Related faults

DN0980455 93


Id:0900d80580a300ccConfidential

4.65 DC voltage administratively disabled

Fault ID and name 4141: EFaultId_DcVoltageAdministrativelyDisabledAl



Source Antenna Line, ALD

Meaning Feeding voltage is disabled for selected Antenna Line.



Unit status attributes Out of order (ALD) Working (Antenna Line)

Effect DC voltage is disabled on reporting Antenna Line.





Instructions To revert changes, DC Voltage should be enabled for reporting Antenna Line.

Related faults

94 DN0980455


Id:0900d80580a300edConfidential

4.66 Dead Peer Detected

Fault ID and name 61030: FTM_DPD



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 management access to other network elements in the RAN - loss of synchronisation if the interface is used as a synchronisation source.



Instructions 1. Check that the cables are connected 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 instructions for handling those alarms.

Related faults

DN0980455 95


Id:0900d80580a300daConfidential

4.67 Difference between BTS master clock and reference fre-quency

Fault ID and name 9: EFaultId_DacWordChangeAl


Detecting unit FCM

Source FCM

Meaning The reference frequency that the BTS master clock receives has changed by about 0.2 ppm or more (which equals the change magnitude of 204 DAC steps or more) during the measurement period, compared to the BTS master clock frequency. The cause of the alarm can be: 1. The reference frequency has changed due to a fault in the transmission network synchronization (which in turn is caused by an equipment fault or a setting error. Note that if the network synchronization malfunction lasts for a long time, the alarm is canceled when the BTS frequency reaches the faulty reference synchronization. The alarm can also be activated if the faulty reference synchronization is corrected and there is again the difference of 0.2 ppm or more. The alarm is canceled whenever the difference becomes smaller than 0.2 ppm. 2. The reference frequency fluctu-ates continuously due to a great deal of jitter/wander in the transmission network. The alarm is continuously activated/canceled (however, the alarming state might predominate). There is always some jitter/wander in the transmis-sion network; the limits are defined in ITU-T G.823/824/825. 3. If the BTS inte-grated transport part receives the synchronization information via the 2.048 MHz synchronization input (external clock source), the alarm situation might be caused by a fault of that signal. In that case, the alarm behavior notifications listed with the Iub signal (see above) are also valid in this case. 4. There is an equipment fault in the BTS. The equipment fault is, however, not the most common reason. Normally, the reason is in the Iub/reference signal behavior (see the descriptions above).


Unit status Working


Effect This fault does not immediately affect the operations of the BTS, but it is a noti-fication that the BTS master clock frequency deviates from the used reference frequency more than in normal circumstances. The BTS master clock tuning continues in spite of the alarm, but because the BTS master clock adjustment is quite slow to filter the instabilities of the reference clock interface, it takes some time (even several hours) before the BTS operations start to be affected.



96 DN0980455



Instructions Because there are several possibilities for the alarm activation, a BTS Clock Frequency History feature has been developed. You can access the stored history data via BTS Site Manager. You can use the history data as a tool for finding out the reason for the fault/alarm situation (for further instructions about the history feature, see the online help of BTS Site Manager). Depending on the possible reason, follow the instructions below: 1. In case of a fault in the transmission network synchronization, you must correct the network synchronization. The long-term accuracy of the Iub signal must be 0.015 ppm or better (check the correct Iub accuracy by measuring it). No actions on the BTS are necessary. 2. If the basic accuracy of the Iub signal is in order but there is too much insta-bility, that is, the jitter/wander is outside the acceptable limits, you must correct the synchronization of the transmission network. The limits for the jitter/wander are defined in the ITU-T G.823/824/825. No actions on the BTS are needed. 3. In case of a BTS equipment fault, the location might be: Transport part: - First check the alarms of the TRS with BTS Site Manager and act accordingly.- If there are no alarms, check the TRS synchronization settings. FCM unit: - If the TDM reference signal accuracy and the TRS are in order but the FCM unit is still alarming, run the fast tuning with BTS Site Manager.- If the alarm is still active after the fast tuning is finished, resetthe site. If the problem does not disappear in a few minutes, reset the site.- If that does not help, replace the FCM unit. Note that if the reason is in the transmission network synchronization, replacing the faulty unit does not correct the situation. Furthermore, the alarm activity (frequent alarms/cancels) points to an instability in the transmissionnetwork, not to a fault in the unit. 4. After the fault situation has been cleared, you might need to tune the BTS master clock because the BTS master clock adjustment is quite slow. You can perform the tuning: - manually by changing the DAC word (during a site visit)- or with fast tuning, in which the BTS master clock is tuned in a few minutes automatically near the Iub reference (normal tuning takes care of the fine tuning). Note, however, that you should only use the fast tuning in case the Iub refer-ence signal is known to be a good one. Otherwise the BTS frequency might be tuned into a totally incorrect value, causing serious problems in the network performance. Background information: The principle is that in the mobile network, the syn-

DN0980455 97



chronization goes from S1 interface. But in reality that chain might be broken somewhere and, for example, when using leased lines, the BTS may take the reference synchronization from the transmission network of another operator. This does not harm the system if the synchronization of the leased line service provider is also accurate/stabile enough. The BTS uses the incoming synchro-nization signal as a reference for the Air interface, the accuracy requirement of which is set by 3GPP.

Related faults

98 DN0980455



4.68 Distributed site support not enabled

Fault ID and name 4076: EFaultId_DistributedSiteSupportNotEnabledAl


Detecting unit FSM

Source OptIF

Meaning Long fiber between FSM and FR detected but Distributed Site feature not enabled (actDistributedSite = False).

State Start



Effect The Radio Module connected to this OptIF is not started.




Instructions Perform the steps below in the listed order until the fault disappears:1. Either enable the parameter actDistributedSite or switch to a shorter fiber between FSM and FR.2. Restart FSM.

Related faults

DN0980455 99



4.69 DSP overheated

Fault ID and name 4101: EFaultId_DspOverheatingAl


Detecting unit FCT

Source FSP

Meaning DSP overheating was detected during DSP initialization.




Effect FSP operation is not possible due to overheated and disabled DSP.




Instructions 1. Check the fans and ensure that the ambient temperature on the site is acceptable.2. If that does not help, replace the alarming FSP module.

Related faults Temperature alarm3040: EFaultId_TemperatureAlarm

100 DN0980455



4.70 EBER on unit $U, interface $IF

Fault ID and name 61104: FTM_EBER



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 suspended from oper-ation



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.

Related faults

DN0980455 101



4.71 Error in file server during file download type <fileTypeN-umber>

Fault ID and name 27: EFaultId_FileServerAl

Used in products Supreme, Optima, Optima IBBU, Optima Compact RF Extension, MetroSite, Triplemode, MetroSite 50, FlexiBTS

Detecting unit UltraSite, MetroSite, MetroSite 50, Triple-mode: WAM; FlexiBTS: FCM; Ultra-Site/EUBB: WAMA

Source UltraSite, MetroSite, MetroSite 50, Triple-mode: WAM FlexiBTS: FCM Ultra-Site/EUBB: WAMA

Meaning The BTS is unable to obtain a file from the file server (error in FTP open or FTP get). The file server is down, the file is missing, or the path is incorrect. A possible error in the DCN and Iub, or a user administration error (an invalid username or password, or the user does not have access rights for the files). <fileTypeNumber> included in fault name is a variable parameter identifying the type of file for which download failure has been reported.


Unit status Working


Effect The BTS continues its operation with the old file.



102 DN0980455



Instructions 1.Check the file type according to the table below: <fileTypeNumber> - <fileType> 1 - hwConfigurationFile 2 - configurationPlanFile 3 - logFile 4 - swFile 5 - licFile 6 - measurementFile 7 - rnwConfigurationPlanFile 11 - combinedSiteConfigurationPlanFile 12 - allConfigurationPlanFile 14 - testResultFile 15 - autoConfReport 17 - measurementPlanFile 18 - rnwMetadataFile 19 - topologyFile 22 - togglingParFile 23 - troubleShootingData 2. Retry the file update a few times. 3. Check the FTP account user settings. 4. Check the file and path names. 5. Check the administration log on the file server.

Related faults

DN0980455 103



4.72 ETH AIS fault interface $IF level $l mac $x

Fault ID and name 61411: Ethernet OAM ETH_AIS_fault


Detecting unit FTIB, FTFB, FTLB, FSM, FSI, FTIF, FIIF

Source OAMMEP

Meaning When a MEP receives a valid ETH-AIS frame and AIS is enabled, it shall trigger an AIS alarm containing the following information: -receiving interface -MD level -Source MAC address NOTE: In FSMr2, pure number interface are used (eg. 1,2,3). But for FSMr3 unit types, interface is provided as: "module type name" EIF "interface number".


Unit status Major


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



Instructions 1) Check cabling.2) Check configuration at remote peer.

Related faults

104 DN0980455



4.73 Failure during cell activation

Fault ID and name 6267: EFaultId_CellActivationFailedAl


Detecting unit FCM [FSM Rel2] / FCT [FSM Rel3] / CC&T [FQGA]

Source LCR

Meaning Cell activation procedure failed because of processing error of cell configura-tion data. The corresponding cell cannot be enabled.

State Start



Effect BTS continues to operate with remaining cells on air or goes to Integrated-ToRAN state if there are no more "enabled" cells left.


LED display N/A

Instructions 1) Try to block/unblock the cell. 2) Try to block/unblock FR module. 3) If it does not help, reset BTS.

Related faults

DN0980455 105



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

Fault ID and name 6261: EFaultId_TraceConnectionFaultyAl



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 activa-tion 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 would not start tracing until the trace connection is established success-fully.


LED display N/A

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

Related faults

106 DN0980455



4.75 Failure in optical RP3 interface

Fault ID and name 3030: EFaultId_FailureInOptical_Rp3Interface



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 attributed 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 NOTIFICATION) or the BTS capacity might have decreased (BASE STATION OPERATION DEGRADED or CELL OPER-ATION DEGRADED, or CELL FAULTY) or the BTS might not be operational at all (BASE STATION FAULTY).




7653 CELL FAULTY


LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disappears. 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.

DN0980455 107




Frame Clock Missing1903: EFaultId_FrFrameClockMissing


Module Clock Faulty1926: EFaultId_FrModuleClockFaulty

Optical Interface faulty2000: EFaultId_OIC_TxAl2001: EFaultId_OIC_PresAl

Receiving failure in Optical Interface2002: EFaultId_OIC_RxAl

10b8b coding error in Optical Interface device <opt link/RP3>2004: EFaultId_OIC_LVDSRecAl

Synchronization failure in Optical Interface <opt link/RP3 link>2005: EFaultId_OIC_SyncChAl

Optical Interface Data/Control/Ethernet Buffer Full2006: EFaultId_OIC_DBRxFullAl2007: EFaultId_OIC_DBTxFullAl2008: EFaultId_OIC_CBRxFullAl2009: EFaultId_OIC_CBTxFullAl2010: EFaultId_OIC_EBFullAl

OIC MCU Buffer Full2011: EFaultId_OIC_MCUBFullAl

Frame clock deviation fault2014: EFaultId_Muksu_SFCRCompDevAl

Frame number synchronization error in optical interface2047: EFaultId_OIC_FrSyncLostAl

Missing RP3-01 link4064: EFaultId_MissingRp301LinkAl

108 DN0980455



4.76 Failure in replaceable baseband unit

Fault ID and name 3003: EFaultId_FbiaFailureAl


Detecting unit FSM

Source FBB

Meaning The BTS has detected an abnormal operation or a failure in the BTS replace-able baseband unit.


Unit status N/A


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



LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault indication disappears.1. Check the other active BTS faults and act accordingly.2. Make sure that the plug-in type baseband unit is installed correctly.3. Reset the alarming baseband unit.4. Replace the alarming baseband unit.

DN0980455 109




POST test failed69: EFaultId_Post_test_failedAl

Unknown HW resource94: EFaultId_UnknownUnitType

Flash operation failure214: EFaultId_FlashWrAl215: EFaultId_FlashRdAl216: EFaultId_FlashEraseAl217: EFaultId_FlashDrvAl218: EFaultId_FlashDbChksumAl

BTS file error1802: EFaultId_FileRequestFlashAl1803: EFaultId_FileParsingFailedAl

Baseband bus configuration of <x> was rejected1811: EFaultId_BbBus_ConfFailedAl

Not able to synchronize baseband bus with <x>1815: EFaultId_BbBus_SyncFailedAl

BB bus reception error (summing device)2016: EFaultId_Muksu_SMTimeOffAl

Address mismatch in summing2019: EFaultId_Muksu_SsubMmAl

Antenna link is down476: EFaultId_Rp3BusError

Unit SW download failed6: EFaultId_SwDownloadAl

SRIO chain configuration was rejected4015: EFaultId_Srio_ConfFailedAl

Master unit has lost connection to the slave unit4019: EFaultId_KeepAliveStatusErrorAl

FSP overheating4077: EFaultId_FspOverheatingAl

110 DN0980455



4.77 Failure in trace session

Fault ID and name 6263: EFaultId_TraceSessionAl



Source FCM

Meaning Failure has occurred during activation/deactivation of Trace Session (Sub-scriber trace or Cell trace or Interface trace session). 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 reached 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/Interface trace, the possible reasons are: - Cell Trace feature has not been enabled at the BTS. - Id used for the cell/inter-face trace session is already in use for another active cell/interface trace session. - Count of cell and interface trace sessions at the BTS has reached the maximum number of cell and interface trace sessions supported by the BTS (which is 12).

State Transient

Unit status Working


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


LED display N/A

DN0980455 111



Instructions For failure in Subscriber trace session activation/deactivation, based on the error cause provided as part of the additional info for the alarm raised, following needs to be done: - "Subscriber & Equipment Trace feature not enabled": Enable the subscriber trace feature at BTS. Any events corresponding to the failed subscriber trace and any other subscriber traces started later, which need to be recorded, will be recorded at BTS after the feature has been enabled.- "trace reference in use, trace cannot be started": This problem is out of scope to be fixed at BTS and is scope of NMS(Network Management System) used to activate the subscriber trace. The error means that there is already an active subscriber trace at BTS using the same Trace Reference Number. Possible solution is to try deactivating all subscriber traces and activating them again. - "max number of UE trace session reached, trace cannot be started": This problem is out of scope to be fixed at BTS and is scope of NMS(Network Man-agement System) used for subscriber trace activation. This error indicates that already 60 active subscriber trace sessions (which is the maximum number of active subscriber traces supported at BTS at any point in time) has already been reached at BTS. Try to stop an already active subscriber trace session at NMS before activating any new subscriber trace(s).- "Trace session cannot be started because of ongoing handover for the UE" OR "Trace session cannot be stopped because of ongoing handover for the UE": This problem is out of scope to be fixed at BTS. This problem is transient. Possible solution is to retry activation of the failed subscriber trace at NMS. For failure in Cell/Interface trace session activation/deactivation, based on the error cause provided as part of the additional info for the alarm raised, following needs to be done: - "Cell trace feature is not enabled": Enable the cell trace feature at BTS. Then try to activate again the required cell/interface trace session(s). The feature flag used for activating cell trace and interface trace is the same.- "trace reference in use, trace cannot be started": This problem is out of scope to be fixed at BTS and is scope of NMS(Network Management System) used to activate the cell/interface trace. The error means that there is already an active cell/interface trace at BTS using the same Trace Reference Number. Possible solution is to try deactivating all cell and interfaces traces. Then try activating them again. - "max number of cell/interface trace sessions reached, trace cannot be started": This problem is out of scope to be fixed at BTS and is scope of NMS(Network Management System) used for cell/interface trace activation. This error indicates that already 12 active cell/interface trace sessions (which is the maximum number of active cell and interface trace sessions put together supported at BTS at any point in time) has already been reached at BTS. Try to stop an already active cell/interface trace session at NMS before activating any new cell/interface trace(s).

Related faults

112 DN0980455



4.78 Fan failure

Fault ID and name 3050: EFaultId_FanFailure



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 temper-ature 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 disappears. 1. Check the fan and cabling. 2. Replace the faulty fan module.

Related faults Fan module operation degraded0: EFaultId_ChangeFanAl

Fan module faulty1: EFaultId_FanPowerAl

No module fan detected1932: EFaultId_FrNoFansDetected

Cooling fan broken1933: EFaultId_FrFanBroken

Cooling fan has reduced from the set speed 1934: EFaultId_FrFanReducedSetSpeed

Cooling fan is over speeding 1935: EFaultId_FrFanOverSpeed

DN0980455 113



4.79 Fan module faulty: <X>

Fault ID and name 1: EFaultId_FanPowerAl


Detecting unit FCM

Source FAN

Meaning All the fans or more than one fan in the same fan group are rotating more slowly than requested.



Unit status attributes alarming fans = out of order, fan group = out of order

Effect If the fans are not rotating as requested, there is a risk that the module temper-ature rises too high.



Instructions 1. Check the fans and connector. 2. Replace the fan module.


114 DN0980455



4.80 Fan module operation degraded: <X>

Fault ID and name 0: EFaultId_ChangeFanAl


Detecting unit FCM

Source FAN

Meaning A fan is not rotating or is rotating more slowly than at the requested speed, or the RPM information is not available for the fan.



Unit status attributes alarming fan = out of order, fan group = degraded

Effect If the redundant fans cannot cool the module sufficiently, unit overheating might occur. For example, a temperature fault from the FCM may be generated.


LED display NORA: Blinking Red, Flexi: Stable Yellow(Fan Group Degraded)

Instructions 1. Check the fan and connector. 2. Replace the fan module.


DN0980455 115



4.81 Fan vendor not detected

Fault ID and name 4073: EFaultId_FanVendorNotDetectedAl


Detecting unit FCT

Source FAN1-n

Meaning Fan speed is too low for succesful detection. Detection attempt takes place again after the fan test timer expires.


Unit status Working


Effect Fan control is not optimized. Effect to noise/temperature level is marginal.



Instructions 1. Check the fan and connector.2. Replace the fan.


116 DN0980455



4.82 Fatal OSE Error

Fault ID and name 418: EFaultId_OseFatalErr


Detecting unit FSP

Source FSP

Meaning The operating system (OSE) goes into the error handler with a fatal status. The cause can be, for example, an out of memory situation. If only one FSP in BTS generates this fault, there is malfunction in one of the FSP submodules. If all FSPs generate this fault, there is malfunction in the FSM.

State Start



Effect The BTS capacity decreases or BTS is not operational. The Digital Signal Pro-cessing (DSP) does not work correctly.




Instructions Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the System Module. 2. Replace the System Module.

Related faults System Module failure3000: EFaultId_SystemModuleFailure

DN0980455 117


Id:0900d80580a300cbConfidential

4.83 Fault diagnostics rule file error

Fault ID and name 1866: EFaultId_RulesMissingAl

1867: EFaultId_RulesParsingAl


Detecting unit FCM [FSMr2] / FCT [FSMr3]

Source FCM [FSMr2]/FCT [FSMr3]

Meaning The Fault diagnostics rule file is missing or its parsing has failed.

State Start



Effect The BTS does not operate.


LED display Stable red (7650)

Instructions Note: Perform the following steps in the listed order until the fault disappears: 1. Download two different software packages so that the faulty file is removed from the BTS. 2. Download the software again. 3. Replace the System Module.


118 DN0980455



4.84 Faulty configuration of system modules

Fault ID and name 1858: EFaultId_FaultyFcmConfigurationAl



Source FCM/FCT

Meaning Synch slave BTS has not detected incoming synch.

State Start



Effect The BTS capacity is lost.



Instructions Check that Wn master module is connected to FSMr2: OptIf #4 FSMr3: OptIf #6 when SCF parameter "syncMaster" = "FALSE".


DN0980455 119



4.85 File corrupted in SW download

Fault ID and name 28: EFaultId_SwPackageAl



Source FlexiBTS: FCM (FSMr2) / FCT (FSMr3), FR

Meaning The downloaded SW is corrupted or incorrectly formed.


Unit status Working


Effect The BTS continues its operation with the old software.




Instructions 1. Retry the SW update.2. Save the snapshot and check the download status from the BTS SWDLre-port in the snapshot file.


120 DN0980455



4.86 File System access failed

Fault ID and name 4088: EFaultId_FileSystemAccessFailedAl



Source FCM, FCT

Meaning File System access operations like file System mounting or file opening failed.

State Start



Effect Module cannot: 1. save in file a cause of the SW fallback on request or 2. mount passive File System thus read the cause of SW fallback on request from the file.



Instructions Update SW to the BTS, unless it is automatically updated by NetAct.

Related faults

DN0980455 121



4.87 Filter unit operation failed

Fault ID and name 1840: EFaultId_TuningFailureAl

1841: EFaultId_UnitFaultyAl

4043: EFaultId_TuningFrequencyOutOfRangeAl


Detecting unit Flexi Filter, External Filter, RFM

Source TX1-n / RX1-n

Meaning A filter has not been able to tune on an appropriate sub-band properly (tuning failure), or another major failure has been detected by the filter (unit faulty).




Effect The signal path is unusable. The cells using the faulty unit might not work.


7653 CELL FAULTY



Instructions In case of 4043:EFaultId_TuningFrequencyOutOfRangeAl: reconfigure the fre-quency settings. In case of 1840:EFaultId_TuningFailureAl, 1841:EFaultId_UnitFaultyAl: replace the filter unit.


122 DN0980455



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

Fault ID and name 61500: FTM_SECURITY



Source FTM

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

State Transient

Unit status Warning


Effect None



Instructions Check your username and password.

Related faults

DN0980455 123


Id:0900d80580a2ffffConfidential

4.89 Flash operation failure

Fault ID and name 214: EFaultId_FlashWrAl

215: EFaultId_FlashRdAl

216: EFaultId_FlashEraseAl

217: EFaultId_FlashDrvAl

218: EFaultId_FlashDbChksumAl



Source FCM/FCT, FSP

Meaning A flash memory operation failure. If this alarm continuously appears, the flash chip might be broken.

State Start



Effect The BTS memory operations, for example the software download and param-eter updates, are not stable. ISTI (In Service Time Indicator) value for HW Repair Center might not be correct or readable.



Instructions 1. Check the other active alarms. If the ROM disk is corrupted, change the alarming module. 2. Block/unblock the alarming module. There are no recovery actions and because of that the block/unblock can be tried once. If that does not help, replace the alarming module.


124 DN0980455



4.90 FPGA SW update failed

Fault ID and name 1928: EFaultId_FrFpgaSwUpdateFailed


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.

Related faults

DN0980455 125



4.91 Frame clock deviation fault

Fault ID and name 2014: EFaultId_Muksu_SFCRCompDevAl



Source FCM, FCT

Meaning Synchronization to the clock control unit frame pulse has been achieved earlier, but it differs from the currently received frame pulse. The internally generated frame clock might have drifted.




Effect The traffic between the System Module and RF Module is unreliable. Some calls or other connections might be lost.



Instructions 1. Check the cables between the System Module and RF Module. 2. Reset the alarming System Module. 3. Replace the alarming System Module.


126 DN0980455



4.92 Frame clock missing

Fault ID and name 1903: EFaultId_FrFrameClockMissing



Source LTX, RX1-n

Meaning The System Module clock reference differs from the RF Module clock.




Effect Calls are not possible through the affected cell(s) (7653 CELL FAULTY). There might be problems in the calls through the affected cell(s) (7654 CELL OPER-ATION DEGRADED).




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.


DN0980455 127



4.93 FSP in resetting state

Fault ID and name 4068: EFaultId_FspResetAl



Source FSP

Meaning FSP is undergoing a cold reset.

State Start



Effect The BTS functionality is degraded and/or resources are unavailable.



LED display Blinking red (7651), Stable red (7650)

Instructions Note! Perform the steps below in the listed order until the fault disappears: 1. Reset the BTS.2. Replace the faulty module/unit.


128 DN0980455



4.94 FSP overheating

Fault ID and name 4077: EFaultId_FspOverheatingAl


Detecting unit FCT

Source FSP

Meaning Temperature on FSP board exceeds critical threshold value.




Effect FSP resource is shut down, the BTS operation will be degraded or faulty. FCT and possible other not alarming FSPs are kept powered.



LED display Stable red (FSP)

Instructions 1. Check the fans and ensure that the ambient temperature on the site is acceptable.2. If that does not help, replace the alarming module.


DN0980455 129



4.95 FTM booted at $date due to $RCause

Fault ID and name 61006: FTM_RESET



Source NE-FTM-1

Meaning The transport part of the BTS has been reset at the date and time given in the notification. FSMr2 supports the following cause for the reset: "power-on reset": Cold start : "watchdog reset": System overload "startup failure": Failure during startup "software failure": Software failure "management reset": Reset trig-gered by management interface: "fallback": Fallback executed FSMr3 supports the following cause for the reset: "power-on reset": Cold start "watchdog reset": System overload "software failure": Software failure "management reset": Reset triggered by management interface "spurious reset": Reset reason detection failed

State Transient

Unit status Minor


Effect The fault has no further consequences.



Instructions No actions are required

Related faults

130 DN0980455



4.96 FTM Toggling <Fault name>

Fault ID and name 61619: FTM_FAULT_TOGGLING



Source FTM

Meaning FTM Fault, for which fault name is mentioned in the Fault name -field, is toggling in the FTM. Toggling fault condition is informed to user with this new FTM Fault. Toggling faults are supressed until the toggling alarm condition is cleared. Severity of this FTM Fault is the same than the severity of the toggling FTM Fault.


Unit status

Unit status attributes Severity of this FTM Fault is the same than the severity of the toggling FTM Fault.

Effect


LED display None

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

Related faults

DN0980455 131



4.97 GPS Receiver alarm: control interface not available

Fault ID and name 4011: EFaultId_GPSSystemElementAl



Source FCM/FCT

Meaning BTS has detected communication problem with the GPS receiver. Fault is ignored until the GPS receiver has reached commissioned state.


Unit status Working


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



Instructions Perform the steps below in the listed order until the fault disappears. If after autonomous GPS power reset, fault does not get cancelled (wait 5min from fault start prior starting actions in below). Control Interface not available:1. The BTS has detected a malfunction in the control interface of the GPS receiver. Possible reason could be that BTS and GPS receiver does not support common interface. Otherwise, perform a (remote) power reset for the GPS receiver.2. Perform a (remote) BTS site reset for the whole BTS.3. Perform a power reset for the whole BTS.4. The cable between the GPS receiver and the BTS might work improperly. Check the pins of the connectors (both ends of the cable) are free from oxide and other kind of dirt, meaning that the pin connection quality is good. 5. The cable between the GPS receiver and the BTS might be faulty. Check the situation and change the cable, if needed.6. There might be a HW fault in the GPS receiver. Check the operation and change the GPS module, if needed.7. There might be a HW fault in the BTS System Module. Check the operation and change the System Module, if needed.

Related faults

132 DN0980455



4.98 GPS receiver alarm: EEPROM invalid

Fault ID and name 4126: EFaultId_GpsReceiverEepromInvalidAl



Source FCM/FCT

Meaning GPS receiver has detected that one or more EEPROM segments have been found to be corrupted at reset and had to be set to their factory default settings.


Unit status Working





Instructions Perform the steps below in the listed order until the fault disappears. EEPROM invalid:1. The GPS receiver has detected a malfunction in the EEPROM memory of the GPS receiver. Perform a (remote) power reset for the GPS receiver.2. There might be a HW fault in the GPS receiver. Check the operation and change the GPS module, if needed.

Related faults

DN0980455 133


Id:0900d80580a300bfConfidential

4.99 GPS receiver alarm: no stored position

Fault ID and name 4124: EFaultId_GpsReceiverNoStoredPositionAl



Source FCM/FCT

Meaning There is no accurate position stored in EEPROM.


Unit status Working





Instructions Perform the steps below in the listed order until the fault disappears. No stored position:1. One of the GPS receiver settings is incorrect. Using the manager SW of the GPS receiver, set the receiver to store the position into non-volatile memory. If there is no tick mark in the position storage selection, the GPS receiver runs the site/self survey every time the GPS receiver is reset (either by manager command, by power outage or by a GPS recovery reset). This means that if the GPS receiver installation quality is only an average - and especially if the instal-lation is a poor one - the GPS receiver turns the PPS reference OFF every now and then during the site survey. This means the BTS master clock drops to holdover mode much easier during the survey than during the normal opera-tion.

Related faults

134 DN0980455


Id:0900d80580a300beConfidential

4.100 GPS receiver alarm: not tracking satellites

Fault ID and name 4122: EFaultId_GpsReceiverNotTrackingSatellitesAl



Source FCM/FCT

Meaning Poor GPS antenna installation


Unit status Working





Instructions Perform the steps below in the listed order until the fault disappears. Not tracking satellites:1. Absolutely the most common reason for this fault indication is that the GPS antenna installation has not been done properly, that is the sky visibility is not good enough. Refer the documentation for installations and if there are devia-tions with the actual installation, re-install the GPS antenna. Note that even when the GPS antenna has a good sky visibility, the problem might be caused by installing the GPS antenna too close to the transmitter antenna(s) of the BTS, causing disturbancies 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.

Related faults

DN0980455 135



4.101 GPS receiver alarm: position questionable

Fault ID and name 4125: EFaultId_GpsReceiverPositionQuestionableAl



Source FCM/FCT

Meaning The receiver is used in stored position but has been moved to a new position after that.


Unit status Working





Instructions Perform the steps below in the listed order until the fault disappears. Position questionable:1. The GPS receiver has valid position data but it is not properly in line with the information estimated from the actual satellite visibility. The reason for this fault indication might be that the GPS antenna installation has not been done prop-erly, that is the sky visibility is not good enough. Refer the documentation for instructions and if there are deviations with the actual installation, re-install the GPS antenna. Note that even when the GPS antenna has a good sky visibility, the problem might be caused by installing the GPS antenna too close to the transmitter antenna(s) of the BTS, causing disturbancies 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.

Related faults

136 DN0980455



4.102 GPS receiver alarm: survey in progress

Fault ID and name 4123: EFaultId_GpsReceiverSurveyInProgressAl



Source FCM/FCT

Meaning The GPS receiver is running a site/self survey


Unit status Working





Instructions Perform the steps below in the listed order until the fault disappears. Survey in progress: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. Note 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 indi-cation 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 feasi-ble, make re-installation of the GPS antenna.3. If the GPS installation 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.

Related faults

DN0980455 137



4.103 GTP-U Path Failure

Fault ID and name 6150: EFaultId_GtpuPathFailure



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.

Reported alarms 7657 BASE STATION CONNECTIVITY DEGRADED

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 communication equipment in between the eNB and the super-vised network element.

Related faults

138 DN0980455



4.104 Heating element not working

Fault ID and name 1860: EFaultId_HeatingMatNotWorkingAl


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

Related faults

DN0980455 139



4.105 High memory consumption

Fault ID and name 6502: EFaultId_HighMemoryConsumptionAl


Detecting unit FSM

Source FCM/FCT, FSP

Meaning Physical memory supervision detects that usage of memory has exceeded 90%(FCM/FCT)/ 98%(FSP).


Unit status Working


Effect High memory usage (memory outage risk).



Instructions Source: - FCM/FCT: Perform eNB reset.- FSP: Change cell configuration to decrease call processing load.

Related faults

140 DN0980455



4.106 Incoherency in cell configuration

Fault ID and name 1856: EFaultId_IncoherencyInCellConfigurationAl


Detecting unit FCM

Source FR

Meaning More than one sector configuration types (A, G, H) are configured to the same RF Module.




Effect The capacity drops. Cell(s) might remain down.



Instructions Recommission the LCRs in a way that only one sector type is used in one RF Module.


DN0980455 141



4.107 Incoherency in cell configuration

Fault ID and name 4000: EFaultId_IncoherencyInConfiguration


Detecting unit FCM

Source FSM, LCR

Meaning Too many LCRs are commissioned to one RF Module.



Unit status attributes Working (FSM) Out of Order (LCR)

Effect The BTS capacity may have decreased.


7653 CELL FAULTY


Instructions Recommission the BTS with a correct number of LCRs per RF Module.


142 DN0980455



4.108 Incoherency In Cell Configuration

Fault ID and name 4044: EFaultId_IncoherencyCellConfigurationAl


Detecting unit FSM

Source LCR

Meaning Cell configuration is not officially supported.

State Start

Unit status Working


Effect This cell-specific fault does not prevent cell configuration. It is for informative purposes only.

Reported alarms 7655 CELL NOTIFICATION


Instructions Check the configuration of the configured cell.


DN0980455 143



4.109 Incoherency with RF Modules

Fault ID and name 1857: EFaultId_IncoherencyWithRFModulesAl


Detecting unit FCM

Source FR

Meaning Incorrect cell configuration for RF modules with a different frequency. The same cell is configured for two RF modules which are not at the same fre-quency.




Effect The capacity drops. Cell(s) might remain down.



Instructions 1. Check which Radio Modules are at for an incorrect frequency. 2. Replace the incompatible Radio Module(s).


144 DN0980455



4.110 Incompatible SW version detected

Fault ID and name 23: EFaultId_IncompatibleSwVersionAl

24: EFaultId_ObsoleteSwVersionAl


Detecting unit FCM

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

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



Unit status attributes Working (FCM detected unsupported fsType value in TargetBD downloaded in SW update) Out of Order (Otherwise)

Effect Resources provided by the module cannot be used, which means that some features might not work. If the fault is reported for FR module, BTSOM does not know the real FR module state, and thus BTS SM keeps FR LED display disabled (grayed). The reason for FR LED status inconsistency is the restriction of RP1 communication only to SW management procedures in case of SW mismatch situation. Hence, there is no possibility to align RF LED and BTS SM LED display status.




7653 CELL FAULTY


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 automatically updated by NetAct.

Related faults

DN0980455 145



4.111 Incorrect radio network parameters

Fault ID and name 6252: EFaultId_FailureInNetworkPlanFile



Source FSM

Meaning There was an opening, reading, or file content problem with a radio network configuration file at the BTS startup or at activation of delta configuration file. The detected problem can be a file handling problem (for example open, read, and write operations fail) as well as a contents problems (for example no valid RAML2.1 format).

State Start



Effect BTS is not configured according to radio network plan file. BTS is waiting for the correct radio network configuration file.



Instructions Note: Perform the steps below in the listed order until the BTS fault disappears. 1. Check the commissioning parameters with the BTS Site Manager Commis-sioningWizard. 2. Load the correct commissioning file to the BTS.

Related faults Commissioning error: <x>3060: EFaultId_CommissioningError

146 DN0980455


Id:0900d80580a300bbConfidential

4.112 Increased BER detected on the optical connection to Radio Module

Fault ID and name 1955: EFaultId_IncrBerOnRp3



Source FR

Meaning Increased bit error rate has been detected on the optical link to radio module which results in sporadical LCV errors in downlink baseband processing.




Effect Calls and data transmissions are possible with degraded quality and lower bandwidth due to increased bit error rate on optical connection.



Instructions Note! Perform the steps below in the listed order until the fault disappears: 1. Check the optical connection between system module and FR module. Check SFP module(s) and/or readjust optical connectors and verify operation of any devices in the optical network between FSM and FRM, if such devices are in use.2. Block/unblock the FR module.3. If it does not help, replace the SFP module(s) in which the malfunctioning optical connection is terminated and/or replace the fiber.

Related faults

DN0980455 147



4.113 Internal MTU configuration failure

Fault ID and name 4025: EFaultId_MtuConfigurationFailureAl


Detecting unit FCM

Source FCM, FSP

Meaning Internal Maximum Transfer Unit (MTU) configuration failed on FCM or FSP.

State Start



Effect The BTS operation is degraded (FSP) or the BTS is not operational (FCM/all FSPs).




Instructions 1. Reset the alarming System Module. 2. Replace the alarming System Module


148 DN0980455



4.114 Invalid configuration file

Fault ID and name 4036: EFaultId_InvalidConfigurationFileAl



Source FCM (FSMr2) / FCT (FSMr3)

Meaning The commissioning file is missing, or an incorrect SCF file has been detected during BTS startup as follows: 1. Commissioning data: the commissioning file is missing or a parameter has a missing or incorrect value. 2. RNW data: "RNW not found", "RNW has wrong format", "RNW could not be parsed", "RNW has wrong schema", "Validation failed due to incompatible data" or "no RNW cell managedObject is created"



Unit status attributes Out of order: when the problems prevents BTS to reach operational state (wrong or missing RNW data/active commissioning data not readable). Working: if there have been problems with commissioning data in SW package but still BTS is operational.

Effect The BTS capacity might decrease or there might be interference in calls (com-missioning data). BTS startup is interrupted and the BTS is out of order (RNW data).



LED display Stable red (7650), Stable green (7652)

Instructions 1. Check and correct the contents of the commissioning file. 2. Recommission the BTS with the valid commissioning file.


DN0980455 149



4.115 Invalid frequency channel for the BTS HW

Fault ID and name 1807: EFaultId_InvalidFrequencyChannelForBTSHW


Detecting unit FCM

Source LCR

Meaning The requested channel in the startup phase is not acceptable for the BTS hard-ware, because of an incorrect frequency band and/or a carrier spacing and/or the number of carriers.




Effect The BTS capacity possibly decreases.



Instructions Check the frequencies' parameters against the BTS HW configuration. The fre-quency is out of the min/max limit of the HW, or the number of carriers for the HW type is exceeded, or the carrier spacing limit is exceeded. There are differ-ent types of variations of the HW that might have limitations in the supported frequency range and bandwidth.


150 DN0980455


Id:0900d80580a300ceConfidential

4.116 IP address conflict

Fault ID and name 4144: EFaultId_IpAddressConflict



Source FCM, FCT

Meaning RF module cannot be detected due to IP address conflict between RP3-01 nodes.


Unit status Working


Effect IP address conflict has been reported between RP3-01 nodes. When there is the IP address conflict, the conflicting (later identified) RP3-01 node is not detected and thus it is not seen on the Site Manager view.


LED display N/A

Instructions Update compatible SW for all conflicting RP3-01 nodes (check the SW versions to see the active SW version and update the active SW version), unless it is automatically updated by NetAct.Note that in case of chained radio modules, the SW update in this particular case can only be done one-by-one along the RF chain. In case the IP conflict situation is not solved, check the conflicting RP3-01 node on the site and ensure the SW update procedure has been properly executed.

Related faults

DN0980455 151



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

Fault ID and name 61077: Link OAM critical link event alarm



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 possible: - 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 receiving direction, e.g. a LOS.


Unit status Major


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



Instructions 1)Inspect details of the type of the critical event through online configuration management.2)Check Link OAM state information of the interface.3)Check cabling and network connections to the far end.4)Check Ethernet interface configuration at local and remote side.5)Insert a Link OAM loopback.

Related faults

152 DN0980455



4.118 Link OAM link lost on unit $U, interface $F

Fault ID and name 61076: Link OAM link lost alarm



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 param-eter 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.


LED display None

Instructions 1)Check cabling and network connections to the far end.2)Check Link OAM event- and Link OAM state information.3)Check Ethernet interface configuration at local and remote side.4)Insert a Link OAM loopback.

Related faults

DN0980455 153



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

Fault ID and name 61075: Link OAM loopback alarm



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.



Instructions None.

Related faults

154 DN0980455



4.120 LOF on unit $U, interface $IF

Fault ID and name 61028: FTM_LOF



Source PPTT

Meaning Loss of frame. It is not possible to carry traffic on the interface referenced in the alarm text. All other transmission 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.




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.



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

Related faults

DN0980455 155



4.121 LOMF on slot $U, interface $IF

Fault ID and name 61150: FTM_LOMF



Source PPTT

Meaning Loss of multiframe. The interface referenced in the alarm text has lost the mul-tiframe alignment. Probable cause: the interface type has not been configured to meet the framing of the interface at the far end. For E1 interfaces, the con-figuration 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.

Related faults

156 DN0980455



4.122 LOS on unit $U, [Ethernet] interface $IF

Fault ID and name 61029: FTM_LOS



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 connected to the inter-face - 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 synchronization if the interface is used as a synchronization source



Instructions 1. Check that the cables are connected 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 instructions for 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.

Related faults

DN0980455 157



4.123 Loss of primary Opt IF

Fault ID and name 4161: EFaultId_LossOfPrimaryOptIfAl



Source OptIF

Meaning FSM notices that a primary optical link connection to the Radio Module has been lost and the radio has been detected only via the secondary (capacity) optical link.




Effect This fault prevents the impacted RF unit from working.




Instructions Optical cabling from the System Module to the Radio Module needs to be cor-rected.


158 DN0980455



4.124 Low noise amplifier failure

Fault ID and name 1839: EFaultId_LNAFailureAl


Detecting unit Flexi Filter

Source RX1-n

Meaning The filter has detected a malfunction in the LNA unit.




Effect The RX path operating performance has decreased.


7653 CELL FAULTY


LED display Stable red (if all LNAs of the RF module are faulty); Blinking red (if not all LNAs of the RF module are faulty)

Instructions Replace the alarming Radio module.


DN0980455 159



4.125 Mast Head Amplifier fault

Fault ID and name 3120: EFaultId_MastHeadAmplifierFault



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 might have no impact on the operation (BASE STATION NOTIFICATION), or the BTS capacity may have decreased (BASE STATION or CELL OPERATION DEGRADED).



LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disappears. 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).

Related faults Mast Head Amplifier fault, <line>1834: EFaultId_AboveCurrentWindowAl1835: EFaultId_BelowCurrentWindowAl

MHA unit operation failure1869: EFaultId_MinorTMAFaultAl1870: EFaultId_MajorTMAFaultAl

160 DN0980455



4.126 Mast Head Amplifier fault above current window, <line>

Fault ID and name 1834: EFaultId_AboveCurrentWindowAl


Detecting unit FR, FF

Source MHA

Meaning The Masthead Amplifier (MHA) does not work properly. The received RF signal level is decreased. If both stages of the LNA on the uplink path fail, the MHA swithes the LNA to by-pass mode. In by-pass mode, the MHA has no gain but some loss. If only one stage of the LNA fails, the MHA still has about half of its normal gain. With an integrated MHA (WMHC), the fault might affect both main and diversity branches or just one of them.




Effect If the MHA is faulty, the RX performance is degraded. The size of the cell might be reduced.


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

Instructions 1. Check the antenna cables and connectors towards the MHA. Fix or replace the broken parts. 2. Restart the MHA by blocking and unblocking the Flexi Radio (FR) Module.NOTE! This operation affects all antenna lines and cells related to the FR Module, not just the faulty one. If the alarm reappears, replace the alarming module.

Related faults Mast Head Amplifier fault3120: EFaultId_MastHeadAmplifierFault

DN0980455 161


Id:0900d80580a300caConfidential

4.127 Mast Head Amplifier fault below current window, <line>

Fault ID and name 1835: EFaultId_BelowCurrentWindowAl


Detecting unit FR, FF

Source MHA

Meaning The Masthead Amplifier (MHA) does not work properly. The received RF signal level is decreased. If both stages of the LNA on the uplink path fail, the MHA swithes the LNA to by-pass mode. In by-pass mode, the MHA has no gain but some loss. If only one stage of the LNA fails, the MHA still has about a half of its normal gain. With an integrated MHA (WMHC), the fault might affect both main and diversity branches or just one of them.

State Start



Effect If the MHA is faulty, the RX performance is degraded. The size of the cell might be reduced.


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

Instructions 1. Check the antenna cables and connectors towards the MHA. Fix or replace the broken parts. 2. Restart the MHA by blocking and unblocking the Flexi Radio (FR) Module. NOTE! This operation affects all antenna lines and cells related to the FR Module, not just the faulty one. If the alarm reappears, replace the alarming module.


162 DN0980455



4.128 Master unit has lost connection to the slave unit

Fault ID and name 4019: EFaultId_KeepAliveStatusErrorAl



Source FCM [FSMr2], FCT [FSMr3], FSP

Meaning Connection to the DSP submodule has been lost or the submodule reports an error situation.




Effect The BTS resources have decreased or the BTS is faulty.



LED display Stable red (7650) , Blinking red (7651)

Instructions Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the BTS.2. Replace the faulty module.



DN0980455 163



4.129 Maximum number of neighbor eNBs/cells exceeded

Fault ID and name 6265: EFaultId_MaximumNumberOfNeighbourEnbsOrCellsExceeded



Source FCM

Meaning This alarm indicates that the maximum number of LNADJ and/or LNADJL was exceeded in eNB and that the new object was not stored.

State Transient

Unit status Working


Effect The fault has no effect on the base station operation but LNADJ and/or LNADJL object was not stored in eNB.



Instructions 1.Check if maximum number of LNADJ was reached. If yes, check if there are LNADJ objects that can be manually deleted. This makes space for new LNADJ information. 2.Check if maximum number of LNADJL was reached. If yes, check if there are LNADJL objects related with LNADJ object that can be manually deleted. This makes space for new LNADJ information.

Related faults

164 DN0980455



4.130 Message routing problem in receiver (RX)

Fault ID and name 2058: EFaultId_MuksuMsgRoutingFailedAl



Source FSP, OptIF

Meaning If a message does not get routed an interrupt is generated. Considered normal when Faradays are starting up and RP3 sync done.







7653 CELL FAULTY


LED display Stable Red (7650), Blinking Red (7651), Stable Red (7653, 7654)

Instructions If RF is the source: 1. Check antenna mapping to the local cells in the commissioning file.2. Check the cables between the System Module and RF Module.3. RF block/unblock4. BTS reset 5. Replace the alarming module. If FSP is the source: System Module reset should be performed.


DN0980455 165



4.131 MHA unit operation failure

Fault ID and name 1869: EFaultId_MinorTMAFaultAl

1870: EFaultId_MajorTMAFaultAl


Detecting unit AISG MHA

Source AISG MHA

Meaning A fault in the Masthead Amplifier (MHA) is detected. The fault reduces the gain performance or completely prevents the MHA from functioning.



Unit status attributes Degraded (MinorTMAFault) Out of order (MajorTMAFault)

Effect The MHA gain is decreased or even producing a loss. The cell performance is decreased.



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

Instructions Replace the alarming module.


166 DN0980455



4.132 Missing or non-compliant SFP module on unit $U, inter-face $I

Fault ID and name 61050: FTM_SFP



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.

Related faults

DN0980455 167



4.133 Missing RNW parameter

Fault ID and name 4009: EFaultId_RnwParameterMissingAl


Detecting unit FSM

Source LCR

Meaning Mandatory parameter missing in the radio network configuration data.




Effect The related cell remains down.



Instructions 1. Check that all mandatory parameters exist in the radio network data for the specific cell. 2. Download and activate the corrected commissioning file to the BTS.


168 DN0980455



4.134 Missing RP3-01 link

Fault ID and name 4064: EFaultId_MissingRp301LinkAl


Detecting unit FCM

Source RX, TX

Meaning Not enough RP3-01 links connected between FSM and FR. Commissioned cells cannot be routed via existing RP3-01 links.




Effect Not enough RP3-01 capacity for commissioned cells. Commissioned cells using the missing RP3-01 link are not activated.




Instructions 4064 triggered during BTS startup:Note! Perform the steps below in the listed order until the fault disappears.1. Check if other BTS fault indications are active. 2. Make sure that all RP3-01 fiber links and SFP transceivers between system module and radio module are properly connected and working. Add missing parallel RP3-01 links.3. Restart the Radio Module.4. Restart the BTS. 4064 triggered during BTS runtime:Change the faulty optical cable.


DN0980455 169



4.135 Module Clock faulty

Fault ID and name 1926: EFaultId_FrModuleClockFaulty



Source LTX

Meaning The RF Module lost lock to the incoming clock.




Effect The communication between the System Module and RF Module might be cor-rupted. The 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, replace the alarming RF Module.


170 DN0980455



4.136 Module dangerously overheating

Fault ID and name 4071: EFaultId_SysDangerouslyOverheatAl


Detecting unit FCM

Source FSP

Meaning The highest validated temperature value on the FSP board exceeds the thresh-old value.




Effect BB resources are shut down, the BTS operation will be faulty. FCM and FTM are kept powered.



Instructions Note! Perform the steps below in the listed order until the fault disappears. 1. Check the fans and ensure that the ambient temperature on the site is acceptable.2. If that does not help, replace the alarming module.


DN0980455 171



4.137 Neighbor cell ambiguity detected

Fault ID and name 6274: EFaultId_NeighborCellAmbiguityDetected


Detecting unit FSP

Source LCR

Meaning A handover target cell cannot be uniquely selected because several candidates are available for a certain PCI value and carrier frequency.

State Transient

Unit status Working


Effect No handover can be performed to cells with the affected PCI and frequency.



Instructions Add the LNREL object pointing to the correct neighbor to allow the handover or enable the UE-based ANR.

Related faults

172 DN0980455



4.138 No connection to Flexi transport submodule

Fault ID and name 3511: EFaultId_NoConnectionToFtAl


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.


LED display N/A

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



DN0980455 173


Id:0900d80580a300efConfidential

4.139 No connection to unit

Fault ID and name 10: EFaultId_NoConnectionToUnitAl



Source FSP, FT, FF, MHA, TILT, FR, FA, extension FSM,

Meaning Connection to a module that belongs to the BTS configuration has been lost.




Effect The module in question is out of use. This fault cancels all the active faults for the same module.




7653 CELL FAULTY


LED display Stable red (7650; 7653), blinking red (7651; 7654), alt. red and green (7653 and 7654 [MHA, TILT]), stable green (7652)

Instructions 1. Make sure that the module is properly connected. If the module LED does not light up, the module is faulty. Check the alarming module.2. Check the fault history.


Failure in optical RP3 interface3030: EFaultId_FailureInOptical_Rp3Interface

Antenna Line Device failure3100: EFaultId_AntennaLineFailure

No connection to Flexi transport submodule3511: EFaultId_NoConnectionToFtAl

WSP failure3002: EFaultId_EubbWspAl


174 DN0980455



4.140 No feedback signal

Fault ID and name 1920: EFaultId_FrNoFeedBackSignal



Source TX1-n

Meaning The feedback signal to predistortion is too weak or missing. The TX perfor-mance is degraded.




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





DN0980455 175



4.141 No MME capacity assigned by Core Network

Fault ID and name 6264: EFaultId_S1ZeroCapPlmns


Detecting unit FCM

Source FCM

Meaning BTS has encountered few possibly misconfigured PLMNs that cannot be used by BTS for accepting calls from new UEs selecting those PLMNs. These PLMNs that are considered misconfigured by BTS are: - currently configured at BTS for one or more cells - served by one or more MMEs and therefore cur-rently broadcast by BTS's cells but none of these PLMNs have serving MME(s) with relative capacity greater than zero. Because of this, BTS cannot select any of these MMEs for any new UEs attempting registration in these PLMNs. All previously registered UEs in these PLMNs remain unaffected.


Unit status Working


Effect BTS cannot accept new UEs attempting registration in any of the reported mis-configured PLMNs. Such an attempt by new UEs results in call failure at BTS. The existing UEs that might have already registered in misconfigured PLMN(s) remain unimpacted.


LED display N/A

Instructions Check and ensure that the PLMNs that have been listed with this BTS fault and that have been configured at BTS for one or more cells have at least one MME serving them and relative capacity of that MME is greater than zero.

Related faults

176 DN0980455



4.142 No module fan detected

Fault ID and name 1932: EFaultId_FrNoFansDetected



Source RFSW

Meaning Radio Module cannot identify the used fan type or the fan is not installed at all.

State Start

Unit status Working


Effect Default values for fan parameters are to be used.


LED display Stable or blinking red (Fan)

Instructions 1. Check that the fan connector is properly mounted. 2. If that does not help, replace the fan module.


DN0980455 177



4.143 Not able to synchronize baseband bus with <x>

Fault ID and name 1815: EFaultId_BbBus_SyncFailedAl


Detecting unit FCM/FCT, FSP

Source FSP, FCM/FCT, OptIF

Meaning The baseband bus synchronization towards <x> failed.

State Start



Effect This fault can prevent the BTS from functioning when the RF Module is needed for the required cell configuration.



7653 CELL FAULTY


LED display Stable red(7650): Blinking red (7651)

Instructions Change the faulty module.



178 DN0980455



4.144 NTP server is not accessible

Fault ID and name 61613: NTP_SERVER_UNREACHABLE


Detecting unit FSM, FTIF

Source INTP

Meaning BTS shall report this alarm if the NTP server is not accessible or if the NTP server cannot be used.


Unit status Major


Effect BTS will not have time synchronisation.



Instructions check the connectivity to NTP servercheck the NTP server configuration at BTS.

Related faults

DN0980455 179



4.145 OIC MCU Buffer Full

Fault ID and name 2011: EFaultId_OIC_MCUBFullAl



Source FCM, FCT

Meaning The control message traffic between the modules is malfunctioning.


Unit status Working


Effect There is possibly no immediate effect on the BTS operation, but it might cause an optical interface alarm.



Instructions Check the alarms for the connected module.


180 DN0980455



4.146 Optical Interface Data/Control/Ethernet Buffer Full

Fault ID and name 2007: EFaultId_OIC_DBTxFullAl

2008: EFaultId_OIC_CBRxFullAl

2009: EFaultId_OIC_CBTxFullAl

2010: EFaultId_OIC_EBFullAl



Source OptIF

Meaning The RP3 or Ethernet buffering is not working, and the buffer becomes full. The optical device is malfunctioning. The fault might be generated because of syn-chronization problems or incorrect initialization.




Effect Baseband bus RP3 traffic to the RF Module is not working. Cell operation is degraded.



Instructions 1. Swap the alarming and working links, and check where the alarm is reported now. 2. If the alarming link remains the same, replace the System Module. 3. If the alarming link changes, replace the module behind that link.


DN0980455 181



4.147 Optical Interface faulty

Fault ID and name 2000: EFaultId_OIC_TxAl

2001: EFaultId_OIC_PresAl



Source OptIF

Meaning The Small Form Factor Pluggable (SFP) malfunction has occurred, or the SFP module is not physically present (there is no electrical connection). The SFP is a part of the fibre cable package.




Effect The traffic between the System Module and the connected module is inter-rupted. The cell operation is faulty. If the fault is reported for primary optical interface, then connection to further radio modules in chain is affected what is indicated via fault 10:EfaultId_NoConnectionToUnitAl for each module.



LED display Stable red (optical interfaces 1-5 leds)

Instructions 1. Check that the SFP (Small Form Factor Pluggable) is properly connected in the System Module. 2. Replace the SFP module.


182 DN0980455



4.148 Oven oscillator clock missing

Fault ID and name 1819: EFaultId_OcxoClkMissAl



Source FCM, FCT

Meaning The output signal of the OXCO is missing and the FCM/FCT cannot deliver the 30.72 MHz System Clock required by the other units.







Instructions 1. Block/unblock the System Module. 2. Replace the System Module.


DN0980455 183



4.149 Oven oscillator heating failure

Fault ID and name 1817: EFaultId_Ov_Osc_HeatAl



Source FCM, FCT

Meaning The OCXO warm-up takes too long and the OCXO does not become active within a period of eight minutes from the power-on. The ambient temperature might also be too low or it changes too fast.




Effect The system clock frequency starts drifting and the air interface frequency accuracy starts to degrade. The BTS might work properly for a few days without an external reference but the network performance might start to decrease gradually.



Instructions Replace the alarming System Module.


184 DN0980455



4.150 Oven oscillator Missing Pulse

Fault ID and name 1820: EFaultId_OcxoPulseMissingAl



Source FCM, FCT

Meaning The output signal of the OXCO has some problems and one or more clock pulses are missed.







Instructions 1. Block/unblock the System Module. 2. Replace the System Module.


DN0980455 185



4.151 Overload collision in transmitter

Fault ID and name 2061: EFaultId_MuksuOverloadCollisionAl



Source FCM, FCT

Meaning Transmitter detected more data coming from a summing than the current link rate can support.




Effect The BTS operation is degraded, because some of the BTS resources are not available.


LED display Blinking Red (7651)

Instructions 1. Block/unblock BTS. 2. Check baseband bus configuration related to RP3 link speeds.


186 DN0980455



4.152 Parallel RP3-01 link length mismatch

Fault ID and name 4072: EFaultId_ParallelLinkDifferenceTooLargeAl


Detecting unit FCM

Source OptIF

Meaning - The parallel RP3-01 links towards one radio module have too large mutual length difference (more than 60 meters). The main link is considered as a ref-erence and the secondary link is compared to the main link. - RF sharing has been disabled on master WCDMA.




Effect No commissioned cells are activated.


7653 CELL FAULTY



Instructions Replace parallel RP3-01 fiber links towards one radio module so that the maximum mutual length difference between fibers is less than 60 meters.In case the fault is triggered because of incorrect RF sharing configuration check that RF sharing feature is enabled on synchronization master system module.

Related faults

DN0980455 187



4.153 Peer system module connection lost

Fault ID and name 4110: EFaultId_PeerSystemModuleConnectionLostAl



Source FCM, FCT

Meaning The master system module has lost optical connection to the peer system module.


Unit status Working

Unit status attributes The master system module works properly.

Effect None


LED display N/A

Instructions Check the optical connection between master and peer system modules.

Related faults

188 DN0980455



4.154 Phich Power Boost not applied

Fault ID and name 6112: EFaultId_PhichPowerBoostAl


Detecting unit FSM

Source FSP

Meaning Configured PHICH transmission power boost cannot be applied either partly or at all due to a lack of remaining power after considering (boosted) cell-specific DL RS power, (boosted) PCFICH power and minimum reserved power for PDCCH.

State Transient

Unit status Working


Effect PHICH transmission power is not boosted enough or at all compared to opera-tor's setting.


LED display None

Instructions PHICH (Physical HARQ Indication Channel) transmission power boost can be increased by reducing the configured boosts for cell-specific downlink refer-ence signal and/or PCFICH.

Related faults

DN0980455 189



4.155 POST test failed

Fault ID and name 69: EFaultId_Post_test_failedAl


Detecting unit FCM/FCT, FT

Source FSP, DSP, FT, FCM/FCT

Meaning The unit or module has been tested during the BTS power-on self test (POST) and a failure has been detected.

State Start



Effect Because the faulty FSP is not configured, the BTS capacity decreases or the BTS is faulty.



LED display Stable red ( 7650) , Blinking red ( 7651)

Instructions FlexiBTS: 1. Block/unblock the alarming unit/module. 2. Remove/reinsert the alarming unit/module. 3. Replace the alarming unit/module.


190 DN0980455



4.156 Post test failed

Fault ID and name 1925: EFaultId_FrPostTestFailed



Source LTX

Meaning An RF Module power-on self-test failed at start-up.

State Start



Effect The cell TX and/or RX performance might be degraded because the failure or calls are not possible through the affected cell(s).






DN0980455 191



4.157 Power level not supported

Fault ID and name 4008: EFaultId_PowerLevelNotSupportedAl


Detecting unit FSM

Source LCR

Meaning The power level defined in the RNW file is not supported by the HW.




Effect Cells remain down.



Instructions Define a valid TX power level value in the Radio Network configuration file (RNW) and use the Commissioning Wizard in BTS Site Manager to send the file to the BTS.


192 DN0980455



4.158 Power level not supported for cells using the same radio module

Fault ID and name 4152: EFaultId_PowerLevelNotSuitableAl



Source LCR

Meaning Power level is too high for at least one of the cells using the same radio module while at the same time at least one of the cells using the same radio module has supported power level.



Unit status attributes Out of order (LCR)

Effect All cells using the same radio module are down.


LED display Stable green (refers to detecting unit)

Instructions Define a valid TX power level value in the Radio Network configuration RNW parameters for all cells using the same radio module and use the Commission-ing Wizard in BTS Site Manager to send the commissioning file to the BTS.


DN0980455 193



4.159 Power on #smodLogicalId #pwrLineId line switched off remotely by user

Fault ID and name 4107: EFaultId_RfPowerSwitchedOffFromBtsSmAl



Source FCM, FCT

Meaning Power feeding for given Radio Module has been switched off by user from BTS Site Manager remotely.


Unit status Working


Effect Radio module is powered off, therefore calls/data transfers cannot be served by that module.



Instructions Enable power feeding towards Radio Module by switching RF power on in BTS Site Manager.

Related faults

194 DN0980455



4.160 PPS reference clock missing in startup

Fault ID and name 4153: EFaultId_PpsRefClcMissInStrtAl



Source FCM/FCT

Meaning Phase synchronization has been commissioned at the btsSyncMode, but PPS reference clock has not become available during timeout, that is, waited for during startup.




Effect Startup is continued without reference clock but BTS is not directed to OnAir.



Instructions 1. Check the GPS receiver installation. 2. Check the GPS receiver status. 3. Check the connection between the GPS receiver and FSM.

Related faults

DN0980455 195



4.161 PPS reference missing

Fault ID and name 1898: EFaultId_PpsRefMissAl



Source FCM/FCT

Meaning The reference clock monitoring has detected a loss of 1PPS reference signal at the 1pps/GPS Sync Input interface of the System Module.


Unit status Degraded;Working

Unit status attributes Working: -other valid sync reference is available Degraded: -otherwise

Effect If other references are available, the synchronization reference source changes to another source. Then tuning follows this new reference. If other ref-erences are not available, tuning does not follow the external reference any more. Clock tuning is halted and the BTS continues its operation based on the internal oven oscillator. If the FCM [FSMr3: FCT] is approaching the end of its lifetime but the reference frequency is still correct, the BTS and system perfor-mance might be normal for months or even one year after the alarm activation (provided that the DAC is not at the edge of the adjustment area).



LED display Blinking red; Stable green

196 DN0980455



Instructions Perform the steps in the listed order until the BTS fault indication disappears. 1. When no GPS receiver is used, check the connection between the Synchro-nization Hub providing 1pps signal to Flexi System Module. 2. When a GPS receiver is used and the GPS receiver is not locked to any sat-ellite, it turns off the PPS signal which is normally delivered to the BTS (Sync Input 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 indi-cation of a fairly poor sky visibility is that the BTS fault is activated/canceled every now and then. The visible/tracked satellites can be seen also in the BTS manager - the amount of satellites varies but if the sky visibility is normal, 6...8 satellites should be visible almost all the time. 3. There might be a malfunction in the GPS receiver. Perform a (remote) reset for the GPS receiver. 4. There might be a malfunction in the BTS. Perform a BTS site reset. 5. The GPS cable and/or connectors might be damaged. Check the cable and the connectors. 6. There might be a HW fault in the GPS receiver. Check the operation and change the HW, if needed. 7. If the previous steps do not help, there might be an equipment failure in the System Module. Check the operation and if performing a BTS site reset does not help, replace the System Module.

Related faults BTS reference clock missing3080: EFaultId_BtsReferenceClockMissing

DN0980455 197



4.162 Radio master conflict

Fault ID and name 4038: EFaultId_RadioMasterConflictAl


Detecting unit FCM

Source FR

Meaning FSM should be the radio master for RFSW, but notices that RFSW already has another radio master defined.

State Start



Effect This fault can prevent BTS from functioning when the RF Module is needed for the required cell configuration.



Instructions Commissioning error. Only one System Module can be set as master for a par-ticular radio resource.


198 DN0980455



4.163 Radio resources switched off

Fault ID and name 4057: EfaultId_RfSwitchedOffAl


Detecting unit FCM

Source Antenna line

Meaning The cells, whose TX carriers are served by the affected Antenna Lines are deactivated to reduce the power transmitted by the Power Amplifier in Radio Module. This is to protect the Power Amplifier against a HW failure that may result from operating under excessive VSWR value condition (antenna line impedance mismatch).

State Start

Unit status Working


Effect The affected cells are disabled.


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.

Related faults

DN0980455 199



4.164 RDI on unit $U, interface $IF

Fault ID and name 61152: FTM_RDI



Source PPTT

Meaning Remote defect indication. It is sent by the intermediate or the far end equipment 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 transmission 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.

Related faults

200 DN0980455



4.165 Receiving failure in Optical Interface

Fault ID and name 2002: EFaultId_OIC_RxAl



Source OptIF

Meaning The incoming optical signal to the Small Form Factor Pluggable (SFP) is missing, too weak, or the fibre cable has been detached. The connection between the System Module and the RF Module units (Linear Transceiver, Antenna Filter or Antenna Line Device) is broken.




Effect The cell(s) of the RF Module behind the broken connection are not operational and the RF Module cannot be used.



LED display Stable red (appropriate OptIF led 1-5)

Instructions 1. Check the status of the module behind the faulty link (power on, and so on). 2. Check the SFP (Small Form Factor Pluggable) from both ends (the System Module and the module behind the faulty link). The optical interface LED indi-cates the faulty SFP. Replace the SFP if it is faulty. 3. Clean the connectors, test the fiber cable, and replace it if faulty. 4. If the previous steps do not help, replace the module behind the faulty link.


DN0980455 201



4.166 RET Antenna control failure

Fault ID and name 1842: EFaultId_MotorJamAl

1843: EFaultId_ActuatorJamAl

1844: EFaultId_NotCalibratedAl

1845: EFaultId_NotConfiguredAl

1846: EFaultId_ActuatorInterferenceAl


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.

Related faults

202 DN0980455



4.167 RF BB bus configuration error

Fault ID and name 1905: EFaultId_FrRfBbBusConfigError



Source LTX, TX1-n, RX1-n

Meaning The RF Module baseband bus is configured incorrectly.




Effect Calls are not possible through the affected cell(s) (7653 CELL FAULTY). There can be problems in calls through the affected cell(s) (7654 CELL OPERATION DEGRADED). No impact on system (7652 BASE STATION NOTIFICATION)


7653 CELL FAULTY


LED display Stable red (all Antenna Lines of the RF module are faulty); Blinking red (not all Antenna Lines of the RF module are faulty)



DN0980455 203



4.168 RF BB bus connection transmission error

Fault ID and name 1906: EFaultId_FrRfBbBusConnTransError



Source LTX / TX1-n

Meaning There is an error in the baseband or optical bus.




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




Instructions 1. Block/unblock the RF Module. 2. (RF sharing case only) Check that all RP3-01 fiber links and SFP transceiv-ers between system module and radio module are properly connected and working. Replace broken fiber link if needed. 3. If that does not help, replace the alarming RF Module.


204 DN0980455



4.169 RF BB bus synchronization error

Fault ID and name 1904: EFaultId_FrRfBbBusSynchError



Source LTX, TX1-n, RX1-n

Meaning The baseband bus between the System Module and RF Module is out of syn-chronization.




Effect Calls are not possible through the affected cell(s) (7653 CELL FAULTY). There might be problems in the calls through the affected cell(s) (7654 CELL OPER-ATION DEGRADED). No impact on system (7652 BASE STATION NOTIFICA-TION)


7653 CELL FAULTY





DN0980455 205



4.170 RF loss of secondary optical interface

Fault ID and name 1930: EFaultId_FRLossOfSecondaryOptIf



Source FR

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




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




Related faults

206 DN0980455



4.171 RF Module blocked

Fault ID and name 1931: EFaultId_FrBlocked



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.

Related faults

DN0980455 207



4.172 RF Module configuring failed

Fault ID and name 1900: EFaultId_FrConfiguringFailed



Source LTX

Meaning The RF Module configuration failed because of a HW or SW fault.

State Start



Effect The calls are not possible through the affected cell(s).




Instructions Replace the alarming RF Module.


208 DN0980455



4.173 RF Module critical file not found

Fault ID and name 1901: EFaultId_FrCriticalFileNotFound



Source LTX

Meaning A critical configuration file is missing from the RF Module.

State Start



Effect The calls are not possible through the affected cell(s).




Instructions Replace the alarming RF Module.


DN0980455 209



4.174 RF Module failure

Fault ID and name 3010: EFaultId_RfModuleFailure



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


7653 CELL FAULTY


LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disappears. 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 accordingly. 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.

210 DN0980455



Related faults Low noise amplifier failure 1839: EFaultId_LNAFailureAl

Filter unit operation failed 1840: EFaultId_TuningFailureAl 1841: EFaultId_UnitFaultyAl 4043: EFaultId_TuningFrequencyOutOfRangeAl

RF Module configuring failed 1900: EFaultId_FrConfiguringFailed

RF Module critical file not found 1901: EFaultId_FrCriticalFileNotFound

RF Module file not found 1902: EFaultId_FrFileNotFound

TX out of order 1907: EFaultId_FrTxOutOfOrder

RF Module Gain adjusting failure 1908: EFaultId_FrGainAdjust

RF BB Energy too high 1909: EFaultId_FrBbEnergyTooHigh

RF Module Filter input power missing 1910: EFaultId_FrFilterInputPowerMissing

RX out of order 1911: EFaultId_FrRxOutOfOrder

RF Module out of order 1912: EFaultId_FrOutOfOrder

No feedback signal 1920: EFaultId_FrNoFeedBackSignal

Transmission quality deteriorated 1921: EFaultId_FrTransmissionQualityDetoriated

Unit unidentified 1923: EFaultId_FrUnitUnidentified

Configuration file corrupted 1924: EFaultId_FrConfigurationFileCorrupted

DN0980455 211



Post test failed 1925: EFaultId_FrPostTestFailed

Antenna Carrier configuration failure 6259: EFaultId_AntennaCarrierMessageFailed

212 DN0980455



4.175 RF Module file not found

Fault ID and name 1902: EFaultId_FrFileNotFound



Source LTX

Meaning The RF Module SW detected that a non-critical configuration file is missing.

State Start



Effect The RF Module is configured using defaults and the performance is not as expected.



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


DN0980455 213



4.176 RF Module filter input power missing

Fault ID and name 1910: EFaultId_FrFilterInputPowerMissing



Source TX1-n

Meaning The RF Module filter has measured too low TX power.

State Start



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






214 DN0980455



4.177 RF Module gain adjusting failure

Fault ID and name 1908: EFaultId_FrGainAdjust



Source TX1-n

Meaning The TX output power adjustment failed.




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





DN0980455 215



4.178 RF Module out of order

Fault ID and name 1912: EFaultId_FrOutOfOrder



Source LTX

Meaning The RF Module is out of order because of a software or hardware fault.




Effect The TX/RX paths of the RF Module are out of order and phone calls through the affected cell(s) are not possible.






216 DN0980455



4.179 RF Module power output faulty

Fault ID and name 1918: EFaultId_FrPowerOutputFault


Detecting unit FR

Source FR, TX1-n

Meaning The Power Supply has detected an overvoltage, undervoltage or overcurrent in the RF Module.




Effect The TX part is out of power and calls are not possible through the affected cell(s).



LED display Stable red (all activated antenna-carriers faulty); Blinking red (at least one acti-vated antenna-carrier faulty or degraded )



DN0980455 217



4.180 RF Power decreased

Fault ID and name 1927: EFaultId_FrPowerDecreased


Detecting unit FRM2/LTX

Source TX1-n

Meaning The highest temperature exceeds the power decrease limit.




Effect The TX power level is decreased and there can be problems with phone calls through the affected cell(s).



Instructions 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, block/unblock the alarming RF Module. 3. If that does not help, replace the alarming RF Module.


218 DN0980455



4.181 RNW parameter mismatch

Fault ID and name 1896: EFaultId_RnwParameterMismatchAl



Source FlexiBTS: FCM (FSMr2) / FCT (FSMr3)

Meaning The RNW configuration data contains a request to create a cell for a non-existing LCR: the LCR ID parameter associated with the object cell does not exist.


Unit status Working


Effect The BTS resumes the startup but the cells assigned to non-existing LCR IDs are discarded.



Instructions 1. Check that each cell object is assigned to an existing LCR ID in the Config-uration file and make corrections if necessary. 2. Download the corrected Configuration file and reset BTS.


DN0980455 219



4.182 RP3 routing collisions are detected on FR module

Fault ID and name 1958: EFaultId_Rp3CollisionOnFr


Detecting unit FR

Source FR

Meaning FR module detected permanent RP3 routing collisions either in downlink (TX), or in uplink (RX) transmission direction.


Unit status Working


Effect Flexi BTS unit in question is transmitting or receiving data with degraded per-formance. Fault does not trigger special action on BTS.


LED display N/A

Instructions 1. Check BTS connections and commisionning settings.2. Block/unblock the BTS (using the local BTS Site Manager connection if a remote connection is not possible).

Related faults

220 DN0980455



4.183 RP3-01 link conflict

Fault ID and name 4039: EFaultId_Rp301LinkConflictAl


Detecting unit FCM

Source OptIF

Meaning FSM notices a shared radio module is connected to different OptIF connectors on peer system modules.




Effect This fault can prevent BTS from functioning when the RF Module is needed for the required cell configuration.



Instructions RP3-01 cabling from peer system modules to shared radio module is to be cor-rected.


DN0980455 221


Id:0900d80580a300bdConfidential

4.184 RS485 IUANT port failure

Fault ID and name 4069: EFaultId_Rs485PowerFailureAl



Source Antenna line

Meaning Radio Module or Filter (all others) has detected overcurrent on RS485 IUANT port. Some antenna line device is causing overload. Depending on HW imple-mentation antenna line devices powered by the RS485 IUANT and/or powered by antenna line are out of order. Overcurrent was detected on RS485 IUANT port. Some antenna line device is causing overload or shortcut exists on port. Antenna line devices powered by the rs485 IUANT port are out of order.

State Start



Effect The RS485 i/f is not operating correctly. The cell capacity decreases.


LED display Blinking red (RF working, Antenna Line faulty)

Instructions 1. Check the RS485 IUANT i/f and antenna line devices. Fix or replace the faulty parts/devices. 2. Alarm is canceled only at RF Module reset or the BTS reset.

Related faults

222 DN0980455



4.185 RX out of order

Fault ID and name 1911: EFaultId_FrRxOutOfOrder



Source LTX, RX1-n

Meaning The RF Module RX RF synthesizer is not locked.

State Start



Effect Calls are not possible through the affected cell(s) (7653 CELL FAULTY). The problems might occur in the calls through the affected cell(s) (7654 CELL OPERATION DEGRADED).



LED display Blinking red (7654), Stable red (7653).



DN0980455 223



4.186 S1 eNB configuration update

Fault ID and name 6321: EFaultId_S1EnbConfigurationUpdate


Detecting unit FCM

Source FCM

Meaning S1 eNB configuration update procedure has failed. The MME could not be informed about modification of at least one of the following eNB configuration data: - eNB Name - Supported TAs (TAC, PLMN Identities) - Default paging DRX

State Start

Unit status Working


Effect If the update of TAC or PLMN identities was not successful eNB performs S1 setup which means service loss for affected cell(s).



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.

Related faults

224 DN0980455



4.187 S1 interface recovery failure

Fault ID and name 6317: EFaultId_S1ResetRetryOut



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, and so on.



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

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

Reported alarms 7656 BASE STATION CONNECTIVITY LOST


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.

Related faults

DN0980455 225



4.188 S1 interface setup failure

Fault ID and name 6308: EFaultId_S1SetupRetryOut



Source LNMME

Meaning There is no S1 connectivity to an MME, the MME has failed, and so on. If the fault is cancelled, autonomous recovery actions (reset) solved the fault situa-tion.



Unit status attributes Unit status is Degraded if at least one other S1 interface is operational, or 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.

Related faults

226 DN0980455



4.189 S1 SCTP path failure

Fault ID and name 6204: EFaultId_S1SctpPathAl



Source LNMME

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.

Related faults

DN0980455 227



4.190 SFP HW Failure

Fault ID and name 61079: SFP HW Failure


Detecting unit FIIB, FILB, FSIB, FTIA, FTIB, FTLB, FTFB, FSM, FTIF

Source FTM

Meaning A malfunctioning of the SFP transceiver was detected. The SFP has reported a transmission fault condition and has disabled the laser tansmitter.




Effect The SFP is not operational.



Instructions Replace the faulty SFP. Note that only the SFP might be faulty, not necessarily the entire hardware unit.

Related faults

228 DN0980455



4.191 SRAM operation failure

Fault ID and name 1875: EFaultId_SRAMRdAl

1876: EFaultId_SRAMWrAl


Detecting unit FSM

Source FSM

Meaning The SRAM memory operation failure. If this fault appears continuously, the SRAM chip might be broken.

State Start



Effect The BTS functionality is degraded and/or resources are unavailable.



Instructions 1. Check the other active faults.2. Replace the alarming module.


DN0980455 229



4.192 SRIO chain configuration was rejected

Fault ID and name 4015: EFaultId_Srio_ConfFailedAl


Detecting unit FSM

Source FSPC

Meaning The baseband bus related SRIO configuration for Faraday core was rejected by the platform SW.

State Start



Effect The BTS does not function correctly. Some BB processing resources in the BTS are out of use.




Instructions Replace the alarming unit.


230 DN0980455



4.193 Starting temperature below minimum

Fault ID and name 1827: EFaultId_StartTempBelowMinAl


Detecting unit FCM

Source BTS

Meaning The temperature measured from sensor specified in "Temp.Cold.Start.Sensor" (= FSP)is less than "Temp.Cold.Start.Limit" The BTS cannot start properly, because the FSPs cannot be powered up at too cold conditions.




Effect The BTS cannot start to the operational state.



Instructions 1. Wait until the the module is automatically heated to the required start-up tem-perature. 2. If the fault has been active for more than 2 hours, check the environmental conditions of the site.

Related faults Temperature alarm 3040: EFaultId_TemperatureAlarm

DN0980455 231



4.194 Summing not enabled for message type

Fault ID and name 2059: EFaultId_MuksuSummingNotEnabledAl



Source FCM, FCT

Meaning Summing checks headers of the messages to be summed. If the header is not any of the allowed types, no summing is performed and an empty message is sent instead.







Instructions 1. Block/unblock the BTS. 2. Check log for line code violation (LCV) errors related to optical links. 3. Verify SFP (small form-factor pluggable transceiver) and fiber conditions.


232 DN0980455


Id:0900d80580a300afConfidential

4.195 Summing service default initialization failed

Fault ID and name 4092: EFaultId_MurkkuDefaultInitFailedAl


Detecting unit FCT

Source FCT

Meaning Summing service default configuration has failed.

State Start



Effect BTS is not operational.



Instructions 1. Reset the System Module. 2. If a reset does not resolve the fault situation, replace the System Module.


DN0980455 233


Id:0900d80580a300abConfidential

4.196 Summing service release from reset failed

Fault ID and name 4081: EFaultId_MurkkuReleaseFromResetFailedAl


Detecting unit FCT

Source FCT

Meaning Summing service release from reset failed.

State Start



Effect BTS is not operational.



Instructions 1. Reset the System Module. 2. If a reset does not resolve the fault situation, replace the System Module.

Related faults

234 DN0980455



4.197 SW corrupted

Fault ID and name 1850: EFaultId_SwCorruptedAl

4029: EFaultId_SwCorruptedPermanentAl



Source Filter, FR, FTM/FCT

Meaning A corrupted SW file in the FLASH has been detected. Unit cannot complete start-up.

State Start



Effect The module might have been started with an old SW version and is, therefore, not compatible with other modules.


7653 CELL FAULTY



Instructions Update the SW to the BTS.


DN0980455 235



4.198 SW fallback

Fault ID and name 4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl

4083: EFaultId_FallbackDueToConfigurationDataMigrationFailureAl

4085: EfaultId_FallbackDueToTransportRequestAl


Detecting unit FSMr2: FCM, FSMr3: FCT

Source 4082: FSMr2: FCM, FSP MCU FSMr3: FCT 4083: FSMr2: FCM FSMr3: FCT 4085: (for FSMr3 only) FSMr3: FCT

Meaning 4082: Source unit reached maximum number of reset retries, that is the source unit cannot finish successfully start-up after SW update. 4083: Source unit requests SW fallback due to critical problem which occurred in start-up after SW update, that is configuration data migration failure. 4085: Transport SW on source unit indicates need for software fallback.

State Start



Effect Source unit has inconsistent SW version.




Instructions In case BTS is not automatically updated by NetAct: Update SW to the BTS with SW version running on BTS before SW update causing SW fallback.

Related faults

236 DN0980455



4.199 SyncE Quality Level Degraded on unit $UID, interface $IF

Fault ID and name 61624: SSM_POORQUALITY


Detecting unit

Source STPG

Meaning This alarm is raised when the received SSM indicates lower clock quality (e.g. "do not use" or "EEC") than required.


Unit status Minor


Effect



Instructions

Related faults

DN0980455 237



4.200 SyncE SSM Timed Out on unit $UID, interface $IF

Fault ID and name 61623: SSM_TIMEOUT


Detecting unit

Source STPG

Meaning In case the incoming SSM is not received for a certain time period (configured via "ssmTimeout" parameter) this an alarm is raised.


Unit status Minor


Effect



Instructions

Related faults

238 DN0980455



4.201 Synchronization error in RP1 receiver

Fault ID and name 2048: EFaultId_Casa2Rp1CrcAl

2049: EFaultId_Casa2Rp1FramePhaseAl


Detecting unit FCM

Source FSM

Meaning The frame alignment is lost or the frame burst has a CRC error when the System Module is working as a synchronization slave system module.

State Start



Effect The System Module is out of order and the BTS is out of order.



Instructions 1. Check the RP3-01 cable between the synchronization master and synchro-nizationslave system modules.2. Check alarms in the synchronization master system module and act accord-ingly.3. Reset the synchronization master system module.


DN0980455 239



4.202 Synchronization failure in Optical Interface <opt link/RP3 link>

Fault ID and name 2005: EFaultId_OIC_SyncChAl



Source OptIF

Meaning The RP3 channel lost the frame synchronization state that it had achieved.




Effect RP3 traffic to the connected RF Module is malfunctioning. The related cell(s) are not operational.


LED display Stable red (SFP led)

Instructions 1. Swap the alarming and working links, and check where the alarm is reported now. 2. If the alarming link remains the same, replace the System Module. 3. If the alarming link changes, replace the module behind that link.


240 DN0980455



4.203 Synchronization lost

Fault ID and name 61058: FTM_SYNC_LOSS



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 synchro-nization sources from the configured priority list are unavailable. 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 synchronized 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.

Related faults

DN0980455 241


Id:0900d80580a300baConfidential

4.204 Synchronization master missing

Fault ID and name 4114: EFaultId_SynchronizationMasterMissingAl


Detecting unit FCM

Source FSM

Meaning Synchronization is lost when the system module is working as a synchroniza-tion slave system module. This indicates usually that a synchronization master system module has been reset.

State Start



Effect The System Module is out of order and the BTS is out of order.



Instructions 1. Wait for the startup to be completed if a synchronization master system module has been reset.2. If there is 1858: EFaultId_FaultyFcmConfigurationAl after synchronization slave's recovery reset then check the RP3-01 cable between the synchroniza-tion master and synchronization slave system modules.3. Check alarms in the synchronization master system module and act accord-ingly.4. Reset the synchronization master system module.


242 DN0980455



4.205 System information broadcast parameters overflow

Fault ID and name 6351: EFaultId_SystemInfoValueTagHandlingFailed


Detecting unit FSP

Source LCR

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

State Transient

Unit status Working


Effect Some of the UEs with a complete set of system information of the cell stored that has left cell and has come back within 3 hours might not recognize that there was a system information change.



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

Related faults

DN0980455 243



4.206 System Module failure

Fault ID and name 3000: EFaultId_SystemModuleFailure


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 be not opera-tional at all (BASE STATION FAULTY).



LED display N/A

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

244 DN0980455



Related faults No connection to unit 10: EFaultId_NoConnectionToUnitAl

Unit synchronization failed 16: EFaultId_SynchronizationAl

POST test failed 69: EFaultId_Post_test_failedAl

Oven oscillator heating failure 1817: EFaultId_Ov_Osc_HeatAl

Oven oscillator clock missing 1819: EFaultId_OcxoClkMissAl

Oven oscillator Missing Pulse 1820: EFaultId_OcxoPulseMissingAl

Communication failure 1806: EFaultId_CommunicationFailureAl

SRAM operation failure 1875: EFaultId_SRAMRdAl 1876: EFaultId_SRAMWrAl

Internal MTU configuration failure 4025: EFaultId_MtuConfigurationFailureAl

DN0980455 245



4.207 Technical log buffer freezing

Fault ID and name 6450: EFaultId_TechnicalLogUploadRecommended


Detecting unit FSP; FSM

Source FSP; FSM

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


LED display None

Instructions This fault does not require any actions.

Related faults

246 DN0980455



4.208 Temperature alarm

Fault ID and name 3040: EFaultId_TemperatureAlarm



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 beyond 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 NOTIFICATION), the BTS capacity might have decreased (CELL OPERATION DEGRADED, or CELL FAULTY)) or the BTS might not be operational at all (BASE STATION FAULTY).




7653 CELL FAULTY



LED display N/A

Instructions Note: Perform the steps below in the listed order until the BTS fault disappears. 1. Check the other BTS faults and act accordingly. 2. Check the ambient temperature of the BTS/modules. If the ambient temper-ature 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 temper-ature 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/unblocking it. 4. Replace the alarming module.

DN0980455 247



Related faults Unit temperature is high2: EFaultId_UnitOverheatAl

Starting temperature below minimum1827: EFaultId_StartTempBelowMinAl

RF Module Overheat1913: EFaultId_FrOverheat

RF Power decreased 1927: EFaultId_FrPowerDecreased

Unit (module) temperature is high 1936: EFaultId_FrTempHigh

Module dangerously overheating4071: EFaultId_SysDangerouslyOverheatAl

FSP overheating4077: EFaultId_FspOverheatingAl

248 DN0980455



4.209 Temperature too low (heating ongoing)

Fault ID and name 1922: EFaultId_FrTemperatureTooLow



Source LTX

Meaning During RF startup: The temperature inside the RF Module is too low. Heating of module is ongoing. Wait until the alarm is canceled. This might take up to 30 minutes. During RF runtime: The temperature inside the RF module is going too low. Problem might occur.



Unit status attributes Out of order during RF startup Working during RF runtime

Effect This fault should cancel itself. Heating of the module is ongoing. During RF startup affected cell resources are not reported to RROM.





Instructions During RF startup only: 1. Heating of module is ongoing. Wait until the alarm is canceled. This might take up to 30 minutes. 2. If that does not help, block/unblock the RF Module. 3. If that does not help, replace the alarming RF Module.

Related faults

DN0980455 249



4.210 Toggling: <Fault name>

Fault ID and name 4026: EFaultId_TogglingAl


Detecting unit FSM

Source FSM, FR

Meaning BTS Fault, which fault name is mentioned 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 suppressed 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).




7653 CELL FAULTY



7656 BASE STATION CONNECTIVITY LOST

LED display N/A

Instructions 1. Check the fault name of the toggling BTS 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."

Related faults

250 DN0980455



4.211 ToP master service $IP unusable

Fault ID and name 61631: TOP_MASTER_UNUSABLE


Detecting unit FSM,FSI,FTIF,FIIF,FTLB,FTIB

Source TOPF

Meaning The reference clock monitoring has detected a loss of ToP reference clock signal received from the master clock behind $IP. - The eNB does not receive a reply from ToP Master within a certain time (5 sec) upon it has sent a sync request message - The eNB receives from ToP Master a granted message rates (sync message rate, delay message rate), that does not match the requested rate by eNB


Unit status Minor


Effect There might be available another synchronization source at eNB; in that case the BTS switches automatically to the other clock source. If no other synchro-nization source is available at eNB, it runs in hold-over mode; Please refer to status of 3080: EFaultId_BtsReferenceClockMissing



Instructions Check the cable connectivity.Check the TOP configuration.

Related faults

DN0980455 251



4.212 Transmission clock missing

Fault ID and name 1816: EFaultId_Trans_Clk_MsgAl



Source FCM, FCT

Meaning The reference clock monitoring has detected a loss of signal in the reference received from the FT.




Effect Tuning does not follow the external reference. Clock tuning is halted and the BTS continues its operation based on the internal oven oscillator. The air inter-face accuracy of 0.05ppm is kept for at least 24 hours. Within that time the BTS can work properly but the network performance might start to gradually degrade.



Instructions 1. Check the Iub connection. 2. Check the FT (Flexi Transport SubModule) status. 3. Check the connection between the FT and FSM (Flexi System Module).

Related faults BTS reference clock missing 3080: EFaultId_BtsReferenceClockMissing

252 DN0980455



4.213 Transmission parameters missing

Fault ID and name 1825: EFaultId_PublicIPmissingAl



Source FT, FCT

Meaning A request to retrieve the public IP address information of the FCM/FCT from the FTM fails.




Effect The BTS is not commissioned or integrated to the network. The BTS cannot be accessed or configured remotely.



Instructions Commission the BTS site with correct IP addresses.


DN0980455 253



4.214 Transmission quality deteriorated

Fault ID and name 1921: EFaultId_FrTransmissionQualityDetoriated



Source TX1-n

Meaning The TX signal adjustment fails.




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





254 DN0980455



4.215 Transmission rule collision in Muksu

Fault ID and name 2060: EFaultId_MuksuTransmissionRuleCollisionAI



Source FCM, FCT

Meaning Transmitter detected an RP3 message from a summing coincident with a trans-mission rule.







Instructions 1. Block/unblock BTS. 2. Check configuration.


DN0980455 255



4.216 Transport layer connection failure in S1 interface

Fault ID and name 6202: EFaultId_S1SctpEndpointAl



Source LNMME

Meaning The transport path (SCTP) for connection 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 connection 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 inter-faces 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 consid-ered degraded and BTS can continue operation(that is setup calls) using avail-able 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 accordingly.2. Check if MME is operational.3. Check if the speed and duplex setting of eNB S1 port is consistent with switch port which is connected directly to the eNB, for example both "Autode-tect" or both "1000 Mbit/s Full duplex". If this fault happens right after a commissioning or a configuration change, verify the following configuration data: IP address of the MME.

Related faults

256 DN0980455



4.217 Transport layer connection failure in X2 interface

Fault ID and name 6203: EFaultId_X2SctpEndpointAl



Source LNADJ

Meaning The transport path (SCTP) for connection to an adjacent BTS has broken. The reason for this might 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 to or from cells of the associated adjacent BTS is not possible. Base station(BTS) operation is considered 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 operational. If this fault happens right after a commissioning or a configuration change, verify the IP address of the adjacent BTS.

Related faults

DN0980455 257


Id:0900d80580a300adConfidential

4.218 Transport module missing: $unit

Fault ID and name 61201: TRANSPORT_MODULE_MISSING


Detecting unit FSM, FTIF

Source UNIT

Meaning Unit missing. The slot has been configured to hold a unit but the plug-in unit is not physically present in the slot. Probable causes: - the unit has been config-ured but not detected - the unit is broken and therefore not detected NOTE: unit variable should be replaced by appropriate HW names configured (unitType-Configured) during runtime reporting.




Effect Possible impact: - no calls are possible for the connections over this unit - loss of remote management access to other network elements in the RAN



Instructions Replacing faulty hardware:1. Re-Plug in the expected transport unit referenced in the alarm text. 2. In case there is a unit present in the slot, remove it from the slotand plug it back in. If the unit is still not recognised and the alarmremains, replace the faulty unit with a new one. De-commissioning previously commissioned hardware:1. Re-commission to remove the hardware unit referenced in the alarm text. NOTE: Before re-commissioning, the hardware unit must not be present in the slot.

Related faults

258 DN0980455



4.219 TWAMP PLR Threshold Crossed

Fault ID and name 61611: PLR_THRESHOLD_CROSSED



Source TWAMP

Meaning The PLR threshold alarm shall be sent in case the configured value of PLR is exceeded.


Unit status Major


Effect None



Instructions

Related faults

DN0980455 259



4.220 TWAMP RTT Threshold Crossed

Fault ID and name 61610: RTT_THRESHOLD_CROSSED



Source TWAMP

Meaning The RTT threshold alarm shall be sent in case the configured value of RTT is exceeded.


Unit status Major


Effect None



Instructions

Related faults

260 DN0980455



4.221 TX failure in MIMO

Fault ID and name 4003: EFaultId_TxFailureTurnMimoOffAl


Detecting unit FSM

Source LCR

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


Unit status Working


Effect Because of TX failure MIMO (Multiple Input Multiple Output) functionality is not operational or degraded 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.



Instructions Software and hardware reconfiguration can be made, to the setup where faulty TX is not used.Then the cells will operate in the single mode unless all the TXes related to the proper cell are faulty.Check the other active BTS faults and act accordingly.

Related faults

DN0980455 261



4.222 TX out of order

Fault ID and name 1907: EFaultId_FrTxOutOfOrder



Source TX1-n

Meaning The RF Module TX path is not usable.




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






262 DN0980455



4.223 Unit (module) dangerously overheating

Fault ID and name 1937: EFaultId_FrDangerouslyOverheat



Source RFSW

Meaning Validated sensor temperature is greater than or equal to the predefined value on unit property file.




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




Instructions 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, replace the alarming RF Module.


DN0980455 263



4.224 Unit (module) temperature is high

Fault ID and name 1936: EFaultId_FrTempHigh



Source RFSW

Meaning Validated module temperature is higher than the predefined maximum allowed value.


Unit status Working


Effect The RF Module may overheat, but there is no immediate effect on the module operation.



Instructions Check the fans and ensure that the ambient temperature on the site is accept-able.


264 DN0980455


Id:0900d80580a300deConfidential

4.225 Unit blocked

Fault ID and name 48: EFaultId_UnitBlockedAl


Detecting unit FSM

Source FR

Meaning A module is blocked with BTS Site Manager. The purpose is to avoid fault indi-cations that might 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 cancellations are always sent to the NMS. It is not possible to establish phone calls through the blocked module.


7653 CELL FAULTY


LED display Stable yellow

Instructions Unblock the module with BTS Site Manager.

Related faults

DN0980455 265


Id:0900d80580a300dcConfidential

4.226 Unit initialization failure

Fault ID and name 12: EFaultId_TcomConfigAl

4040: EFaultId_InitFaultManAl



Source FCM/FCT, FSP

Meaning A module initialization has failed. OR Application of LTE505 feature-related transport network configuration or re-configuration has failed.



Unit status attributes Status "degraded" is used for failure of LTE505 re-configuration during eNB runtime. Status "out of order" is used for failure of LTE505 configuration at eNB startup.

Effect The BTS is not operational or degraded.



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

Instructions FlexiBTS:1. Block/unblock the alarming module. 2. If FSP is the fault source, FSP reset recovery. If FCM/FCT is the fault source, system module reset recovery. If that does not help, perform a power-off reset. 3. If Step 1 and 2 does not help, replace the alarming module. LTE505 specific case:Check the LTE505 related configuration. If the fault was raised at startup then correct the configuration and reset BTS. If the fault was raised during eNB runtime then correct the configuration and apply the changes at BTS.


266 DN0980455


Id:0900d80580a2fffeConfidential

4.227 Unit not supported by current BTS SW version

Fault ID and name 95: EFaultId_NotSupportedUnit



Source All possible units.

Meaning A non-supported unit has been detected in the System Module. Typically, this happens when a new unit version is installed while there is older System Module SW in use that does not support the new unit version.

State Start



Effect Depending on the reported severity, the BTS capacity might have decreased (BASE STATION OPERATION DEGRADED, CELL FAULTY) or the BTS might not be operational at all (BASE STATION FAULTY). For resources that are not in use (not commissioned) lack of support is reported by minor severity alarm (BASE STATION NOTIFICATION).




7653 CELL FAULTY


LED display Stable red (7650), Blinking red (7651), N/A (7652, 7653)

Instructions 1. Upgrade the system module SW.2. Replace the unit.


DN0980455 267



4.228 Unit SW download failed

Fault ID and name 6: EFaultId_SwDownloadAl



Source FCM/FCT, FSP, FR, Faraday / Nyquist

Meaning Software update in the module or submodule has failed.

State Start



Effect If the FSP update fails, the BTS capacity drops. If the optical interface FPGA SW update fails, communication to radio modules does not work and the BTS is not operational.



7653 CELL FAULTY


LED display Stable red ( 7650), Blinking Red ( 7651,7653)

Instructions 1. Download the BTS SW again.2. Reset (block/unblock) the BTS.3. If Step 2 does not help, replace the alarming module.


268 DN0980455


Id:0900d80580a300dbConfidential

4.229 Unit synchronization failed

Fault ID and name 16: EFaultId_SynchronizationAl



Source FCM/FCT, FSP

Meaning FCM/FSP synchronization has failed.

State Start



Effect The BTS capacity possibly decreases. Some cells might become disabled. The BTS is out of order.



LED display Stable red (FCM/FCT on MSM or all FSPs); Blinking red (not all FSPs)

Instructions 1. Block/unblock the alarming module.2. Replace the alarming module.


DN0980455 269



4.230 Unit temperature is high

Fault ID and name 2: EFaultId_UnitOverheatAl


Detecting unit FCM

Source FCM, FSP

Meaning The temperature of a unit exceeds the threshold value.


Unit status Working


Effect The operation of the BTS possibly decreases.



Instructions Check the active fan alarms and the airflow of the BTS.


270 DN0980455



4.231 Unit unidentified

Fault ID and name 1923: EFaultId_FrUnitUnidentified



Source LTX

Meaning The permanent memory in the module is corrupted and the module product code or serial number is missing, or the module product code is unknown.

State Start



Effect The RF Module configuration might fail and cause another fault, and there can be problems in the calls through the affected cell(s).





DN0980455 271


Id:0900d80580a2fffdConfidential

4.232 Unknown HW resource

Fault ID and name 94: EFaultId_UnknownUnitType



Source - FSP (fixed and plug-in cards) - FR - FTM - FF

Meaning A unit cannot be identified by its product code or by its physical device address (object ID).

State Start



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




7653 CELL FAULTY


LED display Stable red (7650), Blinking red (7651), N/A (7652, 7653, 7654)

Instructions Replace the alarming unit/module.



272 DN0980455



4.233 Unsupported HW device

Fault ID and name 61634: UNSUPPORTED_HW_DEVICE


Detecting unit FSM

Source UNIT

Meaning SW does not support the detected HW unit type. Probable causes: - The system module's SW version is too old - Supported HW variant not present in system module




Effect Possible impact: - No calls are possible for the connections over this unit



Instructions SW upgrading:- Upgrade the FSM SW release to the latest version that includes the support for the new external tranport device variant. Unit variant replacement:- Replace the unsupported device variant to another one that the currently running SW release supports.

Related faults

DN0980455 273


Id:0900d80580a300cfConfidential

4.234 Validation of signed file failed

Fault ID and name 4145: EFaultId_SignatureValidationFailedAl


Detecting unit FCT

Source FCT

Meaning SW file validation against its signature failed.




Effect In case of problem detection in SW activation - the SW activation and conse-quent reset are aborted. In case of problem detection in Start-up, BTS remains out of order. Rollback to previous SW and another SW download must be requested by Customer.



LED display Stable red (7650) Stable green (7652)

Instructions Trigger SW update for BTS to the requested SW version.

Related faults

274 DN0980455


Id:0900d80580a300aeConfidential

4.235 Vendor BTS certificate due to expire

Fault ID and name 61616: VENDOR_CERTIFICATE_EXPIRING



Source CERTH

Meaning The BTS shall raise a "Vendor BTS certificate due to expire" alarm when the Vendor BTS certificate is about to expire. The period of notificaton in advance is configurable and the same as for CA certificate expiary described in WBTS_SEC_46333 1 day ... 4999 days with default 1825 days.


Unit status Warning


Effect



Instructions check that the vendor BTS certificate expiry date and renew it.

Related faults

DN0980455 275



4.236 VSWR major alarm

Fault ID and name 1837: EFaultId_VSWRMajorAl



Source Antenna line

Meaning VSWR value exceeds the defined level. The antenna line is mismatched or damaged.

State Start



Effect The cell is disabled. Downlink signal transmission on the given antenna line is disabled and corresponding FR transmitter is unusable. Thus, the overall FR state is affected.


7653 CELL FAULTY





Related faults

276 DN0980455


Id:0900d80580a300eaConfidential

4.237 VSWR minor alarm

Fault ID and name 1838: EFaultId_VSWRMinorAl



Source Antenna connector

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.


7653 CELL FAULTY




Related faults

DN0980455 277



4.238 X2 interface recovery failure

Fault ID and name 6303: EFaultId_X2ResetRetryOut



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, and so on.




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 connection with the adjacent BTS.3. Disconnect and reconnect the adjacent BTS.

Related faults

278 DN0980455



4.239 X2 interface setup failure

Fault ID and name 6304: EFaultId_X2SetupRetryOut



Source LNADJ

Meaning There is no X2 connectivity to an adjacent BTS, the adjacent BTS has failed, and so on.




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.

Related faults

enodeb faults

Documents