alm_lte_lbts_alarms.pdf

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

Flexi Multiradio BTS LTE Alarms

DN0951924

Issue 04A Approval Date 2012-10-18

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 DN0951924


Id:0900d80580974d4aConfidential

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

DN0951924 3


Id:0900d80580974d4aConfidential

Table of contentsThis document has 184 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1 Overview of Flexi Multiradio BTS LTE Alarms . . . . . . . . . . . . . . . . . . . . . 5

2 Base Station Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1 7401 EXTERNAL AL 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 7402 EXTERNAL AL 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.3 7403 EXTERNAL AL 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.4 7404 EXTERNAL AL 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.5 7405 EXTERNAL AL 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.6 7406 EXTERNAL AL 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.7 7407 EXTERNAL AL 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.8 7408 EXTERNAL AL 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.9 7409 EXTERNAL AL 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.10 7410 EXTERNAL AL 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.11 7411 EXTERNAL AL 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.12 7412 EXTERNAL AL 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.13 7413 EXTERNAL AL 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.14 7414 EXTERNAL AL 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.15 7415 EXTERNAL AL 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.16 7416 EXTERNAL AL 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.17 7417 EXTERNAL AL 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.18 7418 EXTERNAL AL 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.19 7419 EXTERNAL AL 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.20 7420 EXTERNAL AL 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.21 7421 EXTERNAL AL 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.22 7422 EXTERNAL AL 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.23 7423 EXTERNAL AL 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.24 7424 EXTERNAL AL 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.25 7425 EXTERNAL AL 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.26 7426 EXTERNAL AL 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.27 7650 BASE STATION FAULTY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.28 7651 BASE STATION OPERATION DEGRADED . . . . . . . . . . . . . . . . 502.29 7652 BASE STATION NOTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . 742.30 7653 CELL FAULTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062.31 7654 CELL OPERATION DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . 1312.32 7655 CELL NOTIFICATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1532.33 7657 BASE STATION CONNECTIVITY DEGRADED. . . . . . . . . . . . . 1622.34 7657 BASE STATION CONNECTIVITY DEGRADED. . . . . . . . . . . . . 1642.35 7665 BASE STATION TRANSMISSION ALARM . . . . . . . . . . . . . . . . 168

4 DN0951924


Id:0900d80580976be9Confidential

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 04 (2012-07-24, RL40) and 04A (2012-10-18, RL40)The following alarms have been updated:

• BASE STATION FAULTY • BASE STATION NOTIFICATION • BASE STATION OPERATION DEGRADED • CELL FAULTY • CELL NOTIFICATION • CELL OPERATION DEGRADED • BASE STATION CONNECTIVITY DEGRADED • BASE STATION CONNECTIVITY LOST • BASE STATION TRANSMISSION ALARM

Changes between issues 04 DRAFT (2011-12-14, RL40) and 04 (2012-07-24, RL40)The following alarms have been updated:

• BASE STATION FAULTY • BASE STATION NOTIFICATION • BASE STATION OPERATION DEGRADED • CELL FAULTY • CELL NOTIFICATION • CELL OPERATION DEGRADED • BASE STATION CONNECTIVITY DEGRADED • BASE STATION TRANSMISSION ALARM

Changes between issues 03 (2011-09-17, RL30) and 04 DRAFT (2011-12-14, RL40)The following alarms have been updated:

• BASE STATION FAULTY • BASE STATION NOTIFICATION • BASE STATION OPERATION DEGRADED • CELL FAULTY • CELL NOTIFICATION • CELL OPERATION DEGRADED • BASE STATION CONNECTIVITY DEGRADED • BASE STATION CONNECTIVITY LOST • BASE STATION TRANSMISSION ALARM

DN0951924 5

Flexi Multiradio BTS LTE Alarms Overview of Flexi Multiradio BTS LTE Alarms

Id:0900d805807a7ba1Confidential

1 Overview of Flexi Multiradio BTS LTE AlarmsThis document describes the alarms and alarm handling of the Flexi Multiradio BTS LTE. The base station software uses these alarms as a basis for internal diagnosis and fault reporting through the OMS to the Operations Support System (OSS) and BTS Site Manager. For troubleshooting instructions, see Flexi Multiradio BTS LTE Troubleshoot-ing.

6 DN0951924


Id:0900d80580976aadConfidential

Base Station Alarms

2 Base Station Alarms

2.1 7401 EXTERNAL AL 1Probable cause: Indeterminate

Event type: Environmental

Default severity: Minor

MeaningThis is an external user-defined alarm. The alarm is defined by the user in a hardware database.

The effect of the alarm depends on the purpose that was configured for the user-defined alarm input in the BTS.

InstructionsThe operation depends on the type of alarm that is used as external alarm number 1.

ClearingDo not cancel the alarm. The system automatically cancels the alarm when the fault has been corrected.

DN0951924 7

Flexi Multiradio BTS LTE Alarms Base Station Alarms









8 DN0951924



Base Station Alarms








DN0951924 9










10 DN0951924



Base Station Alarms








DN0951924 11










12 DN0951924



Base Station Alarms








DN0951924 13










14 DN0951924



Base Station Alarms








DN0951924 15










16 DN0951924



Base Station Alarms








DN0951924 17










18 DN0951924



Base Station Alarms








DN0951924 19










20 DN0951924



Base Station Alarms








DN0951924 21










22 DN0951924



Base Station Alarms








DN0951924 23










24 DN0951924



Base Station Alarms








DN0951924 25










26 DN0951924



Base Station Alarms








DN0951924 27










28 DN0951924



Base Station Alarms








DN0951924 29










30 DN0951924



Base Station Alarms

2.25 7425 EXTERNAL AL 25 Probable cause: Indeterminate



MeaningThis is an external user-defined alarm. The alarm is defined by the userin a hardware database.

The effect of the alarm depends on the purpose that was configured forthe user-defined alarm input in the BTS.

InstructionsThe operation depends on the type of alarm that is used as external alarmnumber 25.

ClearingDo not cancel the alarm. The system automatically cancels the alarm whenthe fault has been corrected.

DN0951924 31






MeaningThis is an external user-defined alarm. The alarm is defined by the userin a hardware database.

The effect of the alarm depends on the purpose that was configured forthe user-defined alarm input in the BTS.

InstructionsThe operation depends on the type of alarm that is used as external alarmnumber 26.

ClearingDo not cancel the alarm. The system automatically cancels the alarm whenthe fault has been corrected.

32 DN0951924



Base Station Alarms

2.27 7650 BASE STATION FAULTYProbable cause: Indeterminate

Event type: Quality of service

Default severity: Critical

MeaningA critical fault (or faults) has occurred in the base station.

Check the reason for the fault from the supplementary text field of the alarm.

The effect of the fault on the functioning of the network element depends on the fault description. For more information, see base station fault descriptions in LTE System Libraries.

Identifying additional information fields1. rack (cabinet) number

2. shelf number

3. slot

4. type of unit

5. unit number

6. subunit number

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

Before a unit/module is replaced at the BTS, the site should be reset to recover from any temporary faults which might have caused the malfunctioning of the unit/module. When an active alarm is a 'Start' alarm, a site reset is required to cancel the alarm. If the site reset or module block/unblock does not help, replace the faulty unit/module (see the source of the alarm and instructions fields of the corresponding alarms).

In case of the FSM failure (FSM or FSM sub-unit is reported as source) it is possible that other units are also reported as faulty since it is impossible for them to continue func-tioning without a system module. In such case replace the system module first and check if the modules previously marked as Faulty are now in Working state.

Below is the list of BTS fault(s) which may have caused this alarm in BTS LN4.0 release. In the case of an earlier SW release and if you need more detailed fault descriptions, LTE System Libraries. The BTS fault descriptions are also included in BTS SW release documentation. If that does not help, contact your local Nokia Siemens Networks repre-sentative.

FAULT NAMEAntenna link is down

FAULT ID476: EFaultId_Rp3BusError

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

DN0951924 33



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

FAULT NAMEBB bus message collision error

FAULT ID2018: EFaultId_Muksu_StxPortCollAl

MEANINGRouted baseband bus messages towards the connected module have collided; the data in the output baseband internal link is lost because the baseband bus is incorrectly con-figured.

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

2. Check the cables between the System Module and the connected module.

3. Replace the alarming module.

FAULT NAMEBB bus reception error (summing device)

FAULT ID2016: EFaultId_Muksu_SMTimeOffAl

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

INSTRUCTIONS1. Check the cables between the System Module and the connected module.

2. Replace the unit that causes the alarm (System Module).

FAULT NAMEBB bus transmission error

FAULT ID2017: EFaultId_Muksu_SRx10b8bAl

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

INSTRUCTIONS1. Check the cables between the System Module and RF Module.

2. Reset the System Module.

3. Replace the alarming module (System Module).

FAULT NAMEBTS Blocked

34 DN0951924



Base Station Alarms

FAULT ID50: EFaultId_BTSBlockedAl

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

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

FAULT NAMEBTS configuration not supported

FAULT ID4097: EFaultId_BtsConfNotSupportedAl

MEANINGFSP does not support requested BTS configuration.

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

FAULT NAMEBTS file error

FAULT ID1802: EFaultId_FileRequestFlashAl

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

INSTRUCTIONSNote: 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 by 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.

FAULT NAMEBTS internal SW management problem

FAULT ID3090: EFaultId_BtsInternalSwManagementProblem

MEANINGA software update to a module or subassembly has failed, or a corrupted SW file has been detected in the FLASH.

INSTRUCTIONSNote: Perform the steps below in the listed order until the BTS fault disappears.

DN0951924 35



FlexiBTS: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.


FAULT NAMEBTS reset required

FAULT ID4001: EFaultId_BtsResetNeededAl

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

FSP overheat occured. FSP temeperature back to normal and BTS reset is needed to take the card back to use.

BTS startup: No FSP units detected by the time RP3 configuration starts.

INSTRUCTIONSReset (block/unblock) the BTS.

FAULT NAMEBTS vendor specific file fault

FAULT ID6262: EFaultId_InvalidVendorSpecificFile

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


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.

FAULT NAMEBaseband Bus failure

FAULT ID3020: EFaultId_BaseBandBusFailure

MEANINGThe FlexiBTS has detected an abnormal operation or a failure in the BTS internal

36 DN0951924



Base Station Alarms

baseband bus. The failure cannot be assigned to a specific module but there are several possible fault sources.


FlexiBTS: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.

FAULT NAMEBaseband bus configuration of <x> was rejected

FAULT ID1811: EFaultId_BbBus_ConfFailedAl

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

INSTRUCTIONSReplace the alarming module.

FAULT NAMEBoot configuration inconsistency detected

FAULT ID4102: EFaultId_BootConfigurationInconsistencyAl

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

INSTRUCTIONSReplace the faulty unit.

FAULT NAMECommissioning error: <x>

FAULT ID3060: EFaultId_CommissioningError

MEANINGSome of the commissioning parameters are either missing or faulty, or there is a mismatch between them.

DN0951924 37




1. Check the commissioning parameters with the BTS Site Manager Commissioning Wizard.

2. Load the correct commissioning file to the BTS.

FAULT NAMECommunication failure

FAULT ID1806: EFaultId_CommunicationFailureAl

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

INSTRUCTIONSFlexiBTS:

1. Check 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.

FAULT NAMEConfiguration error: <x>

FAULT ID3070: EFaultId_ConfigurationError

MEANINGThere is a compatibility problem in the BTS HW/SW versions or the HW/HW configura-tion. Another possibility is that there is a mismatch in the BTS configuration.


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

FAULT NAMEDSP overheated

FAULT ID4101: EFaultId_DspOverheatingAl

MEANINGDSP overheating was detected during DSP initialization.

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

38 DN0951924



Base Station Alarms

FAULT NAMEFSP in resetting state

FAULT ID4068: EFaultId_FspResetAl

MEANINGFSP is undergoing a cold reset.

INSTRUCTIONSNote! Perform the steps below in the listed order until the fault disappears:

FlexiBTS:1. Reset the BTS.2. Replace the faulty module/unit.

FAULT NAMEFSP overheating

FAULT ID4077: EFaultId_FspOverheatingAl

MEANINGTemperature on FSP board exceeds critical threshold value.

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

FAULT NAMEFailure in optical RP3 interface

FAULT ID3030: EFaultId_FailureInOptical_Rp3Interface

MEANINGThe FlexiBTS has detected an abnormal operation or a failure in an optical RP3 inter-face between two modules. The failure cannot be assigned to a specific module but there are several possible fault sources.


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 block-ing/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.


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.

DN0951924 39



FAULT NAMEFailure in replaceable baseband unit

FAULT ID3003: EFaultId_FbiaFailureAl

MEANINGThe BTS has detected an abnormal operation or a failure in the BTS replaceablebaseband unit.

INSTRUCTIONSNote: Perform the steps below in the listed order until the BTS fault indication disap-pears.


2. Check if the plug-in type baseband unit is installed correctly.

3. Reset the alarming baseband unit.

4. Replace the alarming baseband unit.

FAULT NAMEFatal OSE Error

FAULT ID418: EFaultId_OseFatalErr

MEANINGThe 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 sub-modules. If all FSPs generate this fault, there is malfunction in the FSM.

INSTRUCTIONSNote! Perform the steps below in the listed order until the fault disappears.



FAULT NAMEFault diagnostics rule file error

FAULT ID1866: EFaultId_RulesMissingAl1867: EFaultId_RulesParsingAl

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





40 DN0951924



Base Station Alarms

FAULT NAMEFile System access failed

FAULT ID4088: EFaultId_FileSystemAccessFailedAl

MEANINGFile System access operation like:- File System mounting- file opening failed.

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

FAULT NAMEFirmware SW mismatch

FAULT ID2056: EFaultId_SwMismatchAl

MEANINGThe SW update to the BTS has failed or BTS SW corrupted.

INSTRUCTIONS1. Switch to recently active BTS configuration.

2. Retry the SW update.

FAULT NAMEFrame clock deviation fault

FAULT ID2014: EFaultId_Muksu_SFCRCompDevAl

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


2. Reset the alarming System Module.

3. Replace the alarming System Module.

FAULT NAMEFrame number synchronization error in optical interface

FAULT ID2047: EFaultId_OIC_FrSyncLostAl

MEANINGThe timing of the new RP1 synchronization burst deviates from the present RP1 timing maintained in the System Module.

INSTRUCTIONS1. Reset the System Module that causes the alarm.

DN0951924 41



2. If resetting the module does not help, replace the System Module that causes the alarm.

FAULT NAMEIncompatible SW version detected

FAULT ID23: EFaultId_IncompatibleSwVersionAl 24: EFaultId_ObsoleteSwVersionAl

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

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

FAULT NAMEIncorrect radio network parameters

FAULT ID6252: EFaultId_FailureInNetworkPlanFile

MEANINGThere was an opening, reading or file content problem with a radio networkconfiguration file at the BTS startup or at activation of delta configurationfile. The detected problem can be a file handling problem (for exampleopen, read write operations fail) as well as a contents problems (for exampleno valid RAML2.1 format).


1.Check the commissioning parameters with the BTS Site Manager CommissioningWizard.

2.Load the correct commissioning file to the BTS.

FAULT NAMEInternal MTU configuration failure

FAULT ID4025: EFaultId_MtuConfigurationFailureAl

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

INSTRUCTIONS1. Reset the alarming System Module.

2. Replace the alarming System Module

FAULT NAMEInvalid Configuration file

FAULT ID4036: EFaultId_InvalidConfigurationFileAl

42 DN0951924



Base Station Alarms

MEANINGThe commissioning file is missing, or an incorrect SCF file has been detected during BTS startup as follows:

a) Commissioning data: the commissioning file is missing or a parameter has a missing or incorrect value.

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

INSTRUCTIONS1. Check and correct the contents of the commissioning file.

2. Recommission the BTS with the valid commissioning file.

FAULT NAMEMaster unit has lost connection to the slave unit

FAULT ID4019: EFaultId_KeepAliveStatusErrorAl

MEANINGConnection to the DSP submodule has been lost or the submodule reports an error sit-uation.


FlexiBTS:1. Reset the BTS.2. Replace the faulty module.

FAULT NAMEModule dangerously overheating

FAULT ID4071: EFaultId_SysDangerouslyOverheatAl

MEANINGThe highest validated temperature value on the FSP board exceeds the threshold value.


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.

FAULT NAMENo connection to Flexi transport submodule

FAULT ID3511: EFaultId_NoConnectionToFtAl

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


DN0951924 43



FlexiBTS:1. Reset the site.

2. Replace the Transport submodule, which is located inside the System Module.

FAULT NAMENo connection to unit

FAULT ID10: EFaultId_NoConnectionToUnitAl

MEANINGThe connection to a module that belongs to the BTS configuration has been lost.

INSTRUCTIONSFlexiBTS:1. Check 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.

FAULT NAMENot able to synchronize baseband bus with <x>

FAULT ID1815: EFaultId_BbBus_SyncFailedAl

MEANINGThe baseband bus synchronization towards <x> failed.

INSTRUCTIONSFlexiBTS:Change the faulty module.

FAULT NAMEOven oscillator Missing Pulse

FAULT ID1820: EFaultId_OcxoPulseMissingAl

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

INSTRUCTIONS1. Block/unblock the System Module.


FAULT NAMEOven oscillator clock missing

FAULT ID1819: EFaultId_OcxoClkMissAl

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

44 DN0951924



Base Station Alarms

INSTRUCTIONS1. Block/unblock the System Module.


FAULT NAMEOven oscillator heating failure

FAULT ID1817: EFaultId_Ov_Osc_HeatAl

MEANINGThe 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 can also be too low or it changes too fast.


Replace the alarming System Module.

FAULT NAMEPOST test failed

FAULT ID69: EFaultId_Post_test_failedAl

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


1. Block/unblock the alarming unit/module.

2. Remove/reinsert the alarming unit/module.

3. Replace the alarming unit/module.

FAULT NAMESRIO chain configuration was rejected

FAULT ID4015: EFaultId_Srio_ConfFailedAl

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

INSTRUCTIONSReplace the alarming unit.

FAULT NAMESW fallback

FAULT ID4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl4083: EFaultId_FallbackDueToConfigurationDataMigrationFailureAl4085: EfaultId_FallbackDueToTransportRequestAl

DN0951924 45



MEANING4082:Source unit reached maximum number of reset retries i.e source unit cannot finish suc-cessfully start-up after SW update.

4083:Source unit requests SW fallback due to critical problem which occurred in start-up after SW update i.e. configuration data migration failure.

4085:Transport SW on source unit indicates need for software fallback.

INSTRUCTIONSIn case BTS is not automatically updated by NetAct and SW versions are inconsistent: Update SW to the BTS with SW version running on BTS before SW update causing SW fallback.

FAULT NAMEStarting temperature below minimum

FAULT ID1827: EFaultId_StartTempBelowMinAl

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

INSTRUCTIONS1. Wait until the the module is automatically heated to the required start-up temperature.

2. If the fault has been active for more than 2 hours, check the environmental conditions of the site.

FAULT NAMESumming service default initialization failed

FAULT ID4092: EFaultId_MurkkuDefaultInitFailedAl

MEANINGSumming service default configuration has failed.

INSTRUCTIONS1. Reset the System Module.

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

FAULT NAMESumming service release from reset failed

FAULT ID4081: EFaultId_MurkkuReleaseFromResetFailedAl

MEANINGSumming service release from reset failed.

INSTRUCTIONS1. Reset the System Module.

46 DN0951924



Base Station Alarms

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

FAULT NAMESynchronization error in RP1 receiver

FAULT ID2048: EFaultId_Casa2Rp1CrcAl2049: EFaultId_Casa2Rp1FramePhaseAl

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

INSTRUCTIONS1. Check the RP3-01 cable between the synchronization master and synchronizationslave system modules.2. Check alarms in the synchronization master system module and act accordingly.3. Reset the synchronization master system module.

FAULT NAMESystem Module failure

FAULT ID3000: EFaultId_SystemModuleFailure

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


FlexiBTS1. Reset the System Module.


FAULT NAMETemperature alarm

FAULT ID3040: EFaultId_TemperatureAlarm

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


1. Check the other BTS faults and act accordingly.

2. Check the ambient temperature of the BTS/modules. If the ambient temperature is too high, make sure the airflow to the BTS modules is unobstructed, that is, the BTS modules are not covered with anything. If the ambient temperature is too low, it takes a while for the BTS/modules to heat themselves to the threshold value.

3. Reset the alarming module by blocking/unblocking it.


DN0951924 47



FAULT NAMEToggling: <Fault name>

FAULT ID4026: EFaultId_TogglingAl

MEANINGBTS 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 as the severity of the toggling BTS Fault.

INSTRUCTIONS1. 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."

FAULT NAMEUnit SW download failed

FAULT ID6: EFaultId_SwDownloadAl

MEANINGSoftware update to the module or submodule has failed.

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

FAULT NAMEUnit initialization failure

FAULT ID12: EFaultId_TcomConfigAl 4040: EFaultId_InitFaultManAl

MEANINGA module initialization has failed.

INSTRUCTIONSFlexiBTS: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.

48 DN0951924



Base Station Alarms

FAULT NAMEUnit not supported by current BTS SW version

FAULT ID95: EFaultId_NotSupportedUnit

MEANINGAn unsupported unit was found in the System Module. Typically this happens when a new unit version is installed and there is an older System Module SW in use that does not support the new unit version.

INSTRUCTIONSFlexiBTS:1. Upgrade the system module SW.2. Replace the unit.

FAULT NAMEUnit synchronization failed

FAULT ID16: EFaultId_SynchronizationAl

MEANINGFlexiBTS: FCM/FSP synchronisation has failed.

INSTRUCTIONSFlexiBTS:1. Block/unblock the alarming module.2. Replace the alarming module.

FAULT NAMEUnknown HW resource

FAULT ID94: EFaultId_UnknownUnitType

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

INSTRUCTIONSFlexiBTS: Replace the alarming unit/module.

FAULT NAMEUnknown product code

FAULT ID93: EFaultId_UnknownProductCode

MEANINGA module cannot be identified by its product code but is known by its physical device address (object_ID).

INSTRUCTIONSFlexiBTS: Replace the alarming module.

DN0951924 49



FAULT NAMEValidation of signed file failed

FAULT ID4145: EFaultId_SignatureValidationFailedAl

MEANINGSW file validation against its signature failed.

INSTRUCTIONSTrigger SW update for BTS to the requested SW version.


50 DN0951924



Base Station Alarms

2.28 7651 BASE STATION OPERATION DEGRADEDProbable cause: Indeterminate


Default severity: Major

MeaningA major fault (or faults) has occurred in the base station.




2. shelf number

3. slot

4. type of unit

5. unit number

6. subunit number



Below is the list of BTS fault(s) which might have caused this alarm in BTS LN4.0 release. In case of earlier SW release and in case you need more detailed fault descrip-tions refer to LTE System Libraries. The BTS fault descriptions are also included in BTS SW release documentation. If that does not help, contact your local Nokia Siemens Networks representative.

FAULT NAME2M external reference missing

FAULT ID1899: EFaultId_2MExtRefMissAl

DN0951924 51



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

INSTRUCTIONSNote! 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.


FAULT NAMEAddress mismatch in summing

FAULT ID2019: EFaultId_Muksu_SsubMmAl

MEANINGThere is a baseband bus address mismatch in the summing. There are two possible causes:

1. A configuration error (two different baseband units functioning) - after an acknowl-edgement the fault returns.

2. Data corruption on the bus - appears once when unsynchronized data is sent by the baseband.

INSTRUCTIONSCheck the antenna mapping to the local cells in the commissioning file.

FAULT NAMEAntenna link is down

FAULT ID476: EFaultId_Rp3BusError

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


52 DN0951924



Base Station Alarms

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






FAULT NAMEBTS Master Clock tuning failure

FAULT ID1818: EFaultId_Ov_OscAl

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


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.

DN0951924 53



5. If that does not help, replace the system module.

FAULT NAMEBTS SW download or activation failed

FAULT ID29: EFaultId_FileCorruptionAl 30: EFaultId_SwUpdateAl

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

INSTRUCTIONSFlexiBTS: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.

FAULT NAMEBTS configuration not supported

FAULT ID4097: EFaultId_BtsConfNotSupportedAl

MEANINGFSP does not support requested BTS configuration.

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



MEANING

54 DN0951924



Base Station Alarms

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















FAULT NAME

DN0951924 55



BTS reference clock missing

FAULT ID3080: EFaultId_BtsReferenceClockMissing

MEANINGThis 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 inter-face (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 transmission 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 functionality 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.

INSTRUCTIONSDepending 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 deliv-ered to the BTS (Sync In interface). The most common reason is that the GPS receiver does not see any satellites because of poor antenna installation (poor sky visibility). For this, the only permanent cure is to change the GPS antenna location. One indication of a fairly poor sky visibility is that the BTS fault is activated/canceled every now and then.

2. There may be a malfunction in the GPS receiver. Perform a (remote) power reset for

56 DN0951924



Base Station Alarms

the GPS receiver.

3. There may be a malfunction in the BTS. Perform a BTS site reset.

4. The GPS cable and/or connectors may be damaged. Check the cable and the con-nectors.

5. There may be a HW fault in the GPS receiver. Check the operation and change the HW, if needed.

External 2.048MHz signal:1. If there is an external 2.048MHz signal source 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.


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 synchronization source, it turns off the clock reference signal which is normally delivered to the BTS master clock. The synchronization source of the FTM (set by the FTM synchronization priority setting) may 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 may be working fine).

2. Check the alarms of the FTM unit and act accordingly.

3. Check the synchronization settings of the FTM unit.


5. There may 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 may be connection failures in the transmission or packet 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 may 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.


FAULT ID

DN0951924 57



4001: EFaultId_BtsResetNeededAl







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







FAULT NAME

58 DN0951924



Base Station Alarms

Baseband bus configuration of <x> was rejected




FAULT NAMEBoot configuration inconsistency detected

FAULT ID4102: EFaultId_BootConfigurationInconsistencyAl

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

INSTRUCTIONSReplace the faulty unit.







DN0951924 59

















60 DN0951924



Base Station Alarms

FAULT NAMEDSP overheated

FAULT ID4101: EFaultId_DspOverheatingAl

MEANINGDSP overheating was detected during DSP initialization.

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

FAULT NAMEFSP in resetting state

FAULT ID4068: EFaultId_FspResetAl

MEANINGFSP is undergoing a cold reset.

INSTRUCTIONSNote! Perform the steps below in the listed order until the fault disappears:

FlexiBTS:1. Reset the BTS.2. Replace the faulty module/unit.

FAULT NAMEFSP overheating

FAULT ID4077: EFaultId_FspOverheatingAl

MEANINGTemperature on FSP board exceeds critical threshold value.

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

DN0951924 61



FAULT NAMEFailure in connection between BTS and iOMS or 3rd party tool

FAULT ID6261: EFaultId_TraceConnectionFaultyAl

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

INSTRUCTIONSCheck the connection with iOMS/3rd Party tool.











62 DN0951924



Base Station Alarms

FAULT NAMEFailure in replaceable baseband unit

FAULT ID3003: EFaultId_FbiaFailureAl

MEANINGThe BTS has detected an abnormal operation or a failure in the BTS replaceablebaseband unit.

INSTRUCTIONSNote: Perform the steps below in the listed order until the BTS fault indication disap-pears.


2. Check if the plug-in type baseband unit is installed correctly.

3. Reset the alarming baseband unit.

4. Replace the alarming baseband unit.

FAULT NAMEFatal OSE Error

FAULT ID418: EFaultId_OseFatalErr

MEANINGThe 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 sub-modules. If all FSPs generate this fault, there is malfunction in the FSM.




FAULT NAME

DN0951924 63



Flash operation failure

FAULT ID214: EFaultId_FlashWrAl215: EFaultId_FlashRdAl216: EFaultId_FlashEraseAl217: EFaultId_FlashDrvAl218: EFaultId_FlashDbChksumAl

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


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.





FAULT NAMEInternal MTU configuration failure

FAULT ID4025: EFaultId_MtuConfigurationFailureAl

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

64 DN0951924



Base Station Alarms

INSTRUCTIONS1. Reset the alarming System Module.

2. Replace the alarming System Module

FAULT NAMEMaster unit has lost connection to the slave unit

FAULT ID4019: EFaultId_KeepAliveStatusErrorAl

MEANINGConnection to the DSP submodule has been lost or the submodule reports an error sit-uation.


FlexiBTS:1. Reset the BTS.2. Replace the faulty module.

FAULT NAMENo MME capacity assigned by Core Network

FAULT ID6264: EFaultId_S1ZeroCapPlmns

MEANINGBTS has encountered few possibly misconfigured PLMNs which cannot be used by BTS for accepting calls from new UEs selecting those PLMNs.

These PLMNs which are considered misconfigured by BTS are:- currently configured at BTS for one or more cells- served by one or more MMEs and hence currently broadcast by BTS's cellsbut none of these PLMNs have serving MME(s) with relative capacity greater than zero. Because of this reason BTS cannot select any of these MMEs for any new UEs attempt-ing registration in these PLMNs.

All previously registered UEs in these PLMNs remain unaffected.

INSTRUCTIONSCheck and ensure that the PLMNs that have been listed with this BTS fault and that

DN0951924 65



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.





FAULT NAMENot able to synchronize baseband bus with <x>

FAULT ID1815: EFaultId_BbBus_SyncFailedAl

MEANINGThe baseband bus synchronization towards <x> failed.

INSTRUCTIONSFlexiBTS:Change the faulty module.

FAULT NAMEPOST test failed

FAULT ID69: EFaultId_Post_test_failedAl

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

66 DN0951924



Base Station Alarms


1. Block/unblock the alarming unit/module.

2. Remove/reinsert the alarming unit/module.

3. Replace the alarming unit/module.

FAULT NAMEPPS reference missing

FAULT ID1898: EFaultId_PpsRefMissAl

MEANINGThe reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver.

INSTRUCTIONS1. Check the GPS receiver installation.

2. Check the GPS receiver status.

3. Check the connection between the GPS receiver and FSM.

FAULT NAMEParallel RP3-01 link length mismatch

FAULT ID4072: EFaultId_ParallelLinkDifferenceTooLargeAl

MEANINGThe parallel RP3-01 links towards one radio module have too large mutual length differ-ence (more than 60 meters). The main link is considered as reference and the second-ary link is compared to the main link.

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

DN0951924 67



FAULT NAMERP3-01 Link Conflict

FAULT ID4039: EFaultId_Rp301LinkConflictAl

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

INSTRUCTIONSRP3-01 cabling from peer system modules to shared radio module is to be corrected.

FAULT NAMERadio Master Conflict

FAULT ID4038: EFaultId_RadioMasterConflictAl

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

INSTRUCTIONSCommissioning error. Only one System Module can be set as master for a particular radio resource.

FAULT NAMESRAM operation failure

FAULT ID1875: EFaultId_SRAMRdAl1876: EFaultId_SRAMWrAl

MEANINGThe SRAM memory operation failure. If this fault appears continuously, the SRAM chip may be broken.

INSTRUCTIONSFlexiBTS:1. Check the other active faults.2. Replace the alarming module.

68 DN0951924



Base Station Alarms

FAULT NAMESRIO chain configuration was rejected

FAULT ID4015: EFaultId_Srio_ConfFailedAl

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

INSTRUCTIONSReplace the alarming unit.

FAULT NAMESW fallback

FAULT ID4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl4083: EFaultId_FallbackDueToConfigurationDataMigrationFailureAl4085: EfaultId_FallbackDueToTransportRequestAl

MEANING4082:Source unit reached maximum number of reset retries i.e source unit cannot finish suc-cessfully start-up after SW update.

4083:Source unit requests SW fallback due to critical problem which occurred in start-up after SW update i.e. configuration data migration failure.

4085:Transport SW on source unit indicates need for software fallback.

INSTRUCTIONSIn case BTS is not automatically updated by NetAct and SW versions are inconsistent: Update SW to the BTS with SW version running on BTS before SW update causing SW fallback.

FAULT NAMESystem Module failure

FAULT ID

DN0951924 69



3000: EFaultId_SystemModuleFailure

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


FlexiBTS1. Reset the System Module.












70 DN0951924



Base Station Alarms



FAULT NAMETransmission clock missing

FAULT ID1816: EFaultId_Trans_Clk_MsgAl

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

INSTRUCTIONS1. Check the Iub connection.

2. Check the FT (Flexi Transport SubModule) status.

3. Check the connection between the FT and FSM (Flexi System Module).

FAULT NAMETransmission parameters missing

FAULT ID1825: EFaultId_PublicIPmissingAl

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

INSTRUCTIONSCommission the BTS site with correct IP addresses.

DN0951924 71



FAULT NAMEUnit SW download failed




FAULT NAMEUnit initialization failure

FAULT ID12: EFaultId_TcomConfigAl 4040: EFaultId_InitFaultManAl

MEANINGA module initialization has failed.

INSTRUCTIONSFlexiBTS: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.



72 DN0951924



Base Station Alarms



FAULT NAMEUnit synchronization failed

FAULT ID16: EFaultId_SynchronizationAl

MEANINGFlexiBTS: FCM/FSP synchronisation has failed.

INSTRUCTIONSFlexiBTS:1. Block/unblock the alarming module.2. Replace the alarming module.





DN0951924 73








74 DN0951924



Base Station Alarms

2.29 7652 BASE STATION NOTIFICATIONProbable cause: Indeterminate



MeaningA minor fault (or faults) has occurred in the base station.




2. shelf number

3. slot

4. type of unit

5. unit number

6. subunit number


Before a unit/module is replaced at the BTS, the site should be reset to recover from any temporary faults which might have caused the malfunctioning of the unit/module. When an active alarm is a 'Start' alarm, a site reset is required to cancel the alarm. If the site reset or module block/unblock does not help, replace the faulty unit/module (see source of the alarm and instructions fields of the corresponding alarms).

Below is the list of BTS faults which might have caused this alarm in BTS LN4.0 release. In case of earlier SW release and in case you need more detailed fault descriptions refer to LTE System Libraries. The BTS fault descriptions are also included in BTS SW release documentation. If that does not help, contact your local Nokia Siemens Networks representative.

FAULT NAME# autonomous reset as recovery action

FAULT ID52: EFaultId_UnitAutonomousResetAl

DN0951924 75



MEANINGThe BTS tries to correct a fault situation by performing a recovery reset to a unit, to the site or to the BTS. In case of RF module reset in RF chaining configuration BTS resets also all RF modules which are further in chain.

INSTRUCTIONSCheck the fault history and other active faults of the unit.

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

FAULT NAME2M external reference missing

FAULT ID1899: EFaultId_2MExtRefMissAl

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

INSTRUCTIONSNote! 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.


FAULT NAMEAntenna Line Device Operation Failure

FAULT ID1871: EFaultId_BusyAl1872: EFaultId_FormatErrorAl 1873: EFaultId_UnsupportedProcedureAl 1874: EFaultId_OutOfRangeAl

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

76 DN0951924



Base Station Alarms

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

FAULT NAMEAntenna Line Device failure

FAULT ID3100: EFaultId_AntennaLineFailure

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


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.

FAULT NAMEAntenna line device HW failure

FAULT ID1847: EFaultId_HardwareErrorAl

MEANINGA hardware failure detected by an antenna line device. Usually, this is a permanent fault (the hardware is broken).

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

DN0951924 77



FAULT NAMEAntenna line device configuration failure

FAULT ID1848: EFaultId_WorkingSoftwareMissingAl1888: EFaultId_AlConfigurationFailureAl

MEANINGAn antenna line or antenna line device is not properly configured.

INSTRUCTIONS1. Update the proper SW to the device.

2. Check/correct the antenna line configuration.




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







78 DN0951924



Base Station Alarms









FAULT NAMEBTS is uncommissioned

FAULT ID4030: EFaultId_NoCommDataAl

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

INSTRUCTIONS1. Check in NetAct that autoconfiguration is enabled and the required license and com-missioning file are available.

2. Check the autoconnection/autoconfiguration information with BTS Site Manager.


FAULT NAME

DN0951924 79



BTS reference clock missing

FAULT ID3080: EFaultId_BtsReferenceClockMissing

MEANINGThis 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 inter-face (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 transmission 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 functionality 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.

INSTRUCTIONSDepending 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 deliv-ered to the BTS (Sync In interface). The most common reason is that the GPS receiver does not see any satellites because of poor antenna installation (poor sky visibility). For this, the only permanent cure is to change the GPS antenna location. One indication of a fairly poor sky visibility is that the BTS fault is activated/canceled every now and then.

2. There may be a malfunction in the GPS receiver. Perform a (remote) power reset for

80 DN0951924



Base Station Alarms

the GPS receiver.


4. The GPS cable and/or connectors may be damaged. Check the cable and the con-nectors.

5. There may be a HW fault in the GPS receiver. Check the operation and change the HW, if needed.

External 2.048MHz signal:1. If there is an external 2.048MHz signal source 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.


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 synchronization source, it turns off the clock reference signal which is normally delivered to the BTS master clock. The synchronization source of the FTM (set by the FTM synchronization priority setting) may 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 may be working fine).

2. Check the alarms of the FTM unit and act accordingly.

3. Check the synchronization settings of the FTM unit.


5. There may 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 may be connection failures in the transmission or packet 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 may 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.

FAULT NAMEBTS reset time increased

FAULT ID

DN0951924 81



4091: EFaultId_BtsResetTimeIncreasedAl

MEANINGBTS 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 additional actions performed by BTS to recover from faulty situation.

INSTRUCTIONSNone

FAULT NAMEBTS time not corrected

FAULT ID26: EFaultId_NtpTimeNotSetAl

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

INSTRUCTIONS1. Check the NTP setting.

2. Check the stratum parameter on the NTP server.







3. Reset the RF Module and/or System Module, depending on the alarm source:

82 DN0951924



Base Station Alarms

a. Reset the RF Module by blocking/unblocking it. b. Reset the System Module by blocking/unblocking it.















DN0951924 83





FAULT NAMECooling fan broken

FAULT ID1933: EFaultId_FrFanBroken

MEANINGFan(s) are not running.

INSTRUCTIONS1. Check if the fan connector is properly mounted.

2. If that does not help, replace the fan module.

FAULT NAMECooling fan broken

FAULT ID4078: EFaultId_FanBrokenAl

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

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

FAULT NAMECooling fan has reduced from the set speed

FAULT ID1934: EFaultId_FrFanReducedSetSpeed

MEANING

84 DN0951924



Base Station Alarms

Fan(s) are rotating slower than requested.

INSTRUCTIONS1. Check if the fan connector is properly mounted.


FAULT NAMECooling fan is over speeding

FAULT ID4080: EFaultId_FanOverSpeedAl

MEANINGFan(s) are running faster than requested.

INSTRUCTIONSReplace the fan(s).

FAULT NAMECooling fan is over speeding

FAULT ID1935: EFaultId_FrFanOverSpeed

MEANINGFan(s) rotate faster than requested.

INSTRUCTIONSReplace the fan module.

FAULT NAMECooling fan speed decreased

FAULT ID4079: EFaultId_CoolingFanSpeedDecreasedAl

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

INSTRUCTIONS1. Check if the fan is not blocked.

DN0951924 85



2. Check if the fan connector is properly mounted.

3. If that does not help, replace the fan.

FAULT NAMECritical bit toggling error

FAULT ID6701: EFaultId_CriticalBitTogglingError

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




FAULT NAMEDC voltage administratively disabled

FAULT ID4141: EFaultId_DcVoltageAdministrativelyDisabledAl

MEANINGFeeding voltage is disabled for selected Antenna Line.

INSTRUCTIONSIn order to revert changes, DC Voltage should be enabled for reporting Antenna Line.

FAULT NAMEDifference between BTS master clock and reference frequency

FAULT ID9: EFaultId_DacWordChangeAl

MEANINGThe 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

86 DN0951924



Base Station Alarms

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 syn-chronization (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 fluctuates continuously due to a great deal of jitter/wander in the transmission network. The alarm is continuously activated/canceled (however, the alarming state may 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 integrated transport part receives the synchronization information via the 2.048 MHz synchronization input (external clock source), the alarm situation may 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 can be found in the Iub/reference signal behavior (see the descriptions above).

INSTRUCTIONSBecause 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 necessarily needed.

2. If the basic accuracy of the Iub signal is in order but there is too much instability, 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 may 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.

DN0951924 87



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 automati-cally 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 reference signal is known to be a good one. Otherwise the BTS frequency may 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 synchronization 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 synchronization signal as a reference for the Air interface, the accuracy requirement of which is set by 3GPP.

FAULT NAMEError in file server during file download type <fileTypeNumber>

FAULT ID27: EFaultId_FileServerAl

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

INSTRUCTIONS

88 DN0951924



Base Station Alarms

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.







3. Depending on the fault source, reset the RF Module and/or System Module by block-

DN0951924 89



ing/unblocking it.




FAULT NAMEFailure in trace session

FAULT ID6263: EFaultId_TraceSessionAl

MEANINGFailure has occurred during activation/deactivation of Trace Session (Subscriber 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/interface trace session is already in use for another active cell/inter-face 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).

INSTRUCTIONSFor 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 sub-scriber traces and activating them again. - "max number of UE trace session reached, trace cannot be started": This problem is

90 DN0951924



Base Station Alarms

out of scope to be fixed at BTS and is scope of NMS(Network Management System) used for subscriber trace activation. This error indicates that already 60 active sub-scriber trace sessions (which is the maximum number of active subscriber traces sup-ported 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 due to ongoing handover for the UE" OR "Trace session cannot be stopped due to 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 acti-vating 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).

FAULT NAMEFan failure

FAULT ID3050: EFaultId_FanFailure

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


1. Check the fan and cabling.

2. Replace the faulty fan module.

DN0951924 91



FAULT NAMEFan module faulty: <X>

FAULT ID1: EFaultId_FanPowerAl

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

INSTRUCTIONS1. Check the fans and connector.

2. Replace the fan module.

FAULT NAMEFan module operation degraded: <X>

FAULT ID0: EFaultId_ChangeFanAl

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

INSTRUCTIONS1. Check the fan and connector.

2. Replace the fan module.

FAULT NAMEFan vendor not detected

FAULT ID4073: EFaultId_FanVendorNotDetectedAl

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

INSTRUCTIONS1. Check the fan and connector.

92 DN0951924



Base Station Alarms

2. Replace the fan.

FAULT NAMEFile corrupted in SW download

FAULT ID28: EFaultId_SwPackageAl

MEANINGThe SW being downloaded is corrupted or incorrectly formed.

INSTRUCTIONS1. Retry the SW update.2. Save the snapshot and check the download status from the BTS SWDLreport in the snapshot file.

FAULT NAMEFilter unit operation failed

FAULT ID1840: EFaultId_TuningFailureAl1841: EFaultId_UnitFaultyAl4043: EFaultId_TuningFrequencyOutOfRangeAl

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

INSTRUCTIONSIn case of 4043:EFaultId_TuningFrequencyOutOfRangeAl: reconfigure the frequency settings.

In case of 1840:EFaultId_TuningFailureAl, 1841:EFaultId_UnitFaultyAl: replace the filter unit.

FAULT NAMEGPS Receiver alarm: EEPROM invalid

FAULT ID4126: EFaultId_GpsReceiverEepromInvalidAl

MEANING

DN0951924 93



GPS receiver has detected that one or more EEPROM segments were found to be cor-rupted at reset and had to be set to their factory default settings.

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

FAULT NAMEGPS Receiver alarm: control interface not available

FAULT ID4011: EFaultId_GPSSystemElementAl

MEANINGBTS has detected communication problem with the GPS receiver


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 inter-face. 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.

FAULT NAMEGPS Receiver alarm: no stored position

FAULT ID

94 DN0951924



Base Station Alarms

4124: EFaultId_GpsReceiverNoStoredPositionAl

MEANINGThere is no accurate position stored in EEPROM.


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 reseted (either by manager command, by power outage or by a GPS recovery reset). This means that if the GPS receiver instal-lation quality is only an average - and especially if the installation 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 operation.

FAULT NAMEGPS Receiver alarm: not tracking satellites

FAULT ID4122: EFaultId_GpsReceiverNotTrackingSatellitesAl

MEANINGPoor GPS antenna installation


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

FAULT NAMEGPS Receiver alarm: position questionable

DN0951924 95



FAULT ID4125: EFaultId_GpsReceiverPositionQuestionableAl

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


Position questionable:1. The GPS receiver has valid position data but it is not properly in line with the informa-tion estimated from the actual satellite visibility. The reason for this fault indication might be that the GPS antenna installation has not been done properly, 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 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.

FAULT NAMEGPS Receiver alarm: survey in progress

FAULT ID4123: EFaultId_GpsReceiverSurveyInProgressAl

MEANINGThe GPS receiver is running a site/self survey


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. Please notice also that automatic survey takes place every time during first start-up.2. If the automatic survey takes place every now and then, it might be an indication that the sky visibility is poor and according to the poorly tracked satellites, the GPS receiver concludes that the position has changed. In this case, check the activity of the other faults (BTS fault history data) and if found feasible, 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

96 DN0951924



Base Station Alarms

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.

FAULT NAMEHeating element not working

FAULT ID1860: EFaultId_HeatingMatNotWorkingAl

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

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

FAULT NAMEIP Address Conflict

FAULT ID4144: EFaultId_IpAddressConflict

MEANINGIP address conflict detected between RP3-01 nodes.

INSTRUCTIONSWait until autonomous SW update procedure has been executed for all conflicting RP3-01 nodes. 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. Depending on the conditions this may take time from minutes to over an hour.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.

FAULT NAMEIncoherency in cell configuration

DN0951924 97



FAULT ID4000: EFaultId_IncoherencyInConfiguration

MEANINGToo many LCRs are commissioned to one RF Module.

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

FAULT NAMEInvalid Configuration file

FAULT ID4036: EFaultId_InvalidConfigurationFileAl

MEANINGThe commissioning file is missing, or an incorrect SCF file has been detected during BTS startup as follows:

a) Commissioning data: the commissioning file is missing or a parameter has a missing or incorrect value.

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

INSTRUCTIONS1. Check and correct the contents of the commissioning file.

2. Recommission the BTS with the valid commissioning file.

FAULT NAMELow noise amplifier failure

FAULT ID1839: EFaultId_LNAFailureAl

MEANINGThe Filter has detected a malfunction in the LNA unit.

INSTRUCTIONSReplace the alarming Radio module.

98 DN0951924



Base Station Alarms

FAULT NAMEMHA unit operation failure

FAULT ID1869: EFaultId_MinorTMAFaultAl1870: EFaultId_MajorTMAFaultAl

MEANINGA fault in the Masthead Amplifier (MHA) is detected. The fault reduces the gain perfor-mance or completely prevents the MHA from functioning.


FAULT NAMEMast Head Amplifier fault

FAULT ID3120: EFaultId_MastHeadAmplifierFault

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


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

FAULT NAMEMaximum number of neighbor eNBs/cells exceeded

FAULT ID6265: EFaultId_MaximumNumberOfNeighbourEnbsOrCellsExceeded

DN0951924 99



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

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





FAULT NAMENo module fan detected

FAULT ID1932: EFaultId_FrNoFansDetected

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

INSTRUCTIONS1. Check that the fan connector is properly mounted.


100 DN0951924



Base Station Alarms

FAULT NAMEOIC MCU Buffer Full

FAULT ID2011: EFaultId_OIC_MCUBFullAl

MEANINGThe control message traffic between the modules is malfunctioning.

INSTRUCTIONSCheck the alarms for the connected module.

FAULT NAMEPPS reference missing

FAULT ID1898: EFaultId_PpsRefMissAl

MEANINGThe reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver.

INSTRUCTIONS1. Check the GPS receiver installation.

2. Check the GPS receiver status.

3. Check the connection between the GPS receiver and FSM.

FAULT NAMEPeer system module connection lost

FAULT ID4110: EFaultId_PeerSystemModuleConnectionLostAl

MEANINGThe master system module has lost optical connection to the peer system module.

INSTRUCTIONSCheck the optical connection between master and peer system modules.

FAULT NAME

DN0951924 101



RF Module failure

FAULT ID3010: EFaultId_RfModuleFailure

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


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.


4. If that does not help, replace the faulty RF Module.

FAULT NAMERF Module overvoltage protection faulty

FAULT ID1942: EFaultId_FrOverVoltageProtectionFaulty

MEANINGRF Module's overvoltage protection is broken.

INSTRUCTIONSReplace the alarming RF Module.

FAULT NAMERF power switched off remotely from BTS Site Manager

FAULT ID4107: EFaultId_RfPowerSwitchedOffFromBtsSmAl

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

INSTRUCTIONS

102 DN0951924



Base Station Alarms

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

FAULT NAMERNW parameter mismatch

FAULT ID1896: EFaultId_RnwParameterMismatchAl

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

2. There is wrong RNW parameter related to each used Rf module in the MIMO config-uration.

INSTRUCTIONS1. Check that each cell object is assigned to an existing LCR ID in the Configuration file and make corrections if necessary. / Check that there is valid RNW parameters for instance pMax is suitable for each Rf modules used in the MIMO configuration.

2. Download the corrected Configuration file and reset BTS.

FAULT NAMETechnical log buffer freezing

FAULT ID6450: EFaultId_TechnicalLogUploadRecommended

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

INSTRUCTIONSThis fault does not require any actions.



DN0951924 103













FAULT NAMEUnit deleted

FAULT ID74: EFaultId_UnitDeletedAl

104 DN0951924



Base Station Alarms

MEANINGAn O&M internal fault. The fault diagnosis is that system deleted the unit. FDCLConfig-uration checker.

OR

An LNMME/LNADJ object is deleted.

INSTRUCTIONSNone

FAULT NAMEUnit temperature is high

FAULT ID2: EFaultId_UnitOverheatAl

MEANINGThe temperature of a unit exceeds the threshold value.

INSTRUCTIONSCheck the active fan alarms and the airflow of the BTS.

FAULT NAMEVSWR alarm

FAULT ID1837: EFaultId_VSWRMajorAl

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

INSTRUCTIONS1. Check the antenna cables, connectors, antenna and possible antenna line devices.

2. Check the antenna line (TX-cable-antenna) impedance matching.


FAULT ID1838: EFaultId_VSWRMinorAl

DN0951924 105



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



FAULT NAMEX2 neighbor cell configuration inconsistency

FAULT ID6307: EFaultId_X2NeighbourCellInfoInconsistency

MEANINGInconsistent cell information encountered by BTS in the configuration of an adjacent BTS.

The only cases when BTS reports inconsistent data currently are when cell informa-tion(Physical Cell ID and frequency that is EARFCN) received from an adjacent BTS is found to be identical to - the cell information received from another adjacent BTS- one of ownm(that is local) BTS's configured cell information.

INSTRUCTIONSCross-check the correctness of the cell configuration in the adjacent BTS and own (that is local) BTS.


106 DN0951924



Base Station Alarms

2.30 7653 CELL FAULTYProbable cause: Indeterminate


Default severity: Critical

MeaningA critical fault (or faults) has occurred in a unit (or units) that belong to the sector indi-cated in the alarm.




2. shelf number

3. slot

4. type of unit

5. unit number

6. subunit number




FAULT NAMEAntenna Carrier configuration failure

FAULT ID6259: EFaultId_AntennaCarrierMessageFailed

DN0951924 107



MEANINGAntenna carrier resources were not successfully set up during cell setup or cell deletion procedure due to failure of RX or TX resource. Affected cell might be not operational.

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









FAULT NAMEAntenna line faulty

FAULT ID4045: EFaultId_AntennaLineFaultyAl

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

INSTRUCTIONS1. Check the antenna line and antenna line device that causes the alarm.

108 DN0951924



Base Station Alarms

2. Fix or replace the faulty parts/devices.






FAULT NAMEBTS config error (Not enough HW for LCR)

FAULT ID1868: EFaultId_NotEnoughHwForLcrAl

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

INSTRUCTIONSRF 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


DN0951924 109



FAULT ID4001: EFaultId_BtsResetNeededAl














110 DN0951924



Base Station Alarms

FAULT NAMEBaseband bus configuration of <x> was rejected




FAULT NAMECell blocked

FAULT ID49: EFaultId_CellBlockedAl

MEANINGThe user has blocked the cell with BTS Site Manager.

INSTRUCTIONSTo cancel the fault, unblock the cell.

FAULT NAMECell power failure

FAULT ID4090: EFaultId_TxCarrierInputPowerLowAl

MEANINGFlexiBTS:

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


1. Check the other active alarms and act accordingly.2. If that does not help, block/unblock the system module.

DN0951924 111



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.














112 DN0951924



Base Station Alarms


FAULT NAMEDistributed site support not enabled

FAULT ID4076: EFaultId_DistributedSiteSupportNotEnabledAl

MEANINGLong fiber between FSM and FR detected but Distributed Site feature not enabled (act-DistributedSite = False).

INSTRUCTIONSPerform the steps below in the listed order until the fault disappears:

1. Either enable the parameter actDistributedSite or switch to shorter fiber between FSM and FR.2. Restart FSM.

FAULT NAMEFailure during cell activation

FAULT ID6267: EFaultId_CellActivationFailedAl

MEANINGCell activation procedure failed because of processing error of cell configuration data. The corresponding cell cannot be enabled.

INSTRUCTIONS1) Try to block/unblock the cell.

2) Try to block/unblock FR module.

3) If it does not help, reset BTS.



DN0951924 113
















FAULT NAMEFrame clock missing

114 DN0951924



Base Station Alarms

FAULT ID1903: EFaultId_FrFrameClockMissing

MEANINGThe System Module clock reference differs from the RF Module clock.


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.

FAULT NAMEFrame number synchronization error in optical interface

FAULT ID2047: EFaultId_OIC_FrSyncLostAl

MEANINGThe timing of the new RP1 synchronization burst deviates from the present RP1 timing maintained in the System Module.

INSTRUCTIONS1. Reset the System Module that causes the alarm.

2. If resetting the module does not help, replace the System Module that causes the alarm.


FAULT ID1856: EFaultId_IncoherencyInCellConfigurationAl

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

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

DN0951924 115




FAULT ID4000: EFaultId_IncoherencyInConfiguration

MEANINGToo many LCRs are commissioned to one RF Module.

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

FAULT NAMEIncoherency with RF Modules

FAULT ID1857: EFaultId_IncoherencyWithRFModulesAl

MEANINGIncorrect cell configuration for RF modules with a different frequency. The same cell is configured for two RF modules which are not at the same frequency.

INSTRUCTIONS1. Check which Radio Modules are at for an incorrect frequency.

2. Replace the incompatible Radio Module(s).





116 DN0951924



Base Station Alarms

FAULT NAMEInvalid frequency channel for the BTS HW

FAULT ID1807: EFaultId_InvalidFrequencyChannelForBTSHW

MEANINGThe requested channel in the startup phase is not acceptable for the BTS hardware, because of an incorrect frequency band and/or a carrier spacing and/or the number of carriers.

INSTRUCTIONSCheck the frequencies' parameters against the BTS HW configuration. The frequency 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 different types of variations of the HW that may have limitations in the supported frequency range and bandwidth.





FAULT NAMEMissing RNW parameter

FAULT ID4009: EFaultId_RnwParameterMissingAl

MEANINGMandatory parameter missing in the radio network configuration data.

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

DN0951924 117



FAULT NAMEMissing RP3-01 link

FAULT ID4064: EFaultId_MissingRp301LinkAl

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

INSTRUCTIONS4064 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. Check 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.

FAULT NAMEModule Clock Faulty

FAULT ID1926: EFaultId_FrModuleClockFaulty

MEANINGThe RF Module lost lock to the incoming clock.





118 DN0951924



Base Station Alarms




FAULT NAMEOptical Interface faulty

FAULT ID2000: EFaultId_OIC_TxAl2001: EFaultId_OIC_PresAl

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

INSTRUCTIONS1. Check that the SFP (Small Form Factor Pluggable) is properly connected in the System Module.

2. Replace the SFP module.

FAULT NAMEParallel RP3-01 link length mismatch

FAULT ID4072: EFaultId_ParallelLinkDifferenceTooLargeAl

MEANINGThe parallel RP3-01 links towards one radio module have too large mutual length differ-ence (more than 60 meters). The main link is considered as reference and the second-ary link is compared to the main link.

INSTRUCTIONSReplace parallel RP3-01 fiber links towards one radio module so that the maximum

DN0951924 119



mutual length difference between fibers is less than 60 meters.

FAULT NAMEPipe dangerously overheating

FAULT ID1938: EFaultId_FrPipeOverheat

MEANINGValidated temperature of any PA sensor is greater than or equal to the predefined value on unit property file.

INSTRUCTIONS1. Check the fans and ensure that the ambient temperature on the site is acceptable.


FAULT NAMEPower level not supported

FAULT ID4008: EFaultId_PowerLevelNotSupportedAl

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

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

FAULT NAMEPower level not supported for cells utilizing the same radio module

FAULT ID4152: EFaultId_PowerLevelNotSuitableAl

MEANINGPower level is too low or too high for at least one of the cells utilizing the same radio module while at the same time at least one of the cells utilizing the same radio module has supported power level.

120 DN0951924



Base Station Alarms

INSTRUCTIONSDefine a valid TX power level value in the Radio Network configuration file (RNW) for all cells utilizing the same radio module and use the Commissioning Wizard in BTS Site Manager to send the file to the BTS.

FAULT NAMERF BB Bus Configuration Error

FAULT ID1905: EFaultId_FrRfBbBusConfigError

MEANINGThe RF Module baseband bus is configured incorrectly.

INSTRUCTIONS1. Block/unblock the RF Module.


FAULT NAMERF BB Bus Synchronization Error

FAULT ID1904: EFaultId_FrRfBbBusSynchError

MEANINGThe baseband bus between the System Module and RF Module is out of synchroniza-tion.





FAULT NAMERF BB bus Connection transmission error

FAULT ID

DN0951924 121



1906: EFaultId_FrRfBbBusConnTransError

MEANINGThere is an error in the baseband or optical bus.


2. (RF sharing case only) Check that all RP3-01 fiber links and SFP transceivers between systemmodule and radio module are properly connected and working. Replace brokenfiber link if needed.


FAULT NAMERF Module blocked

FAULT ID1931: EFaultId_FrBlocked

MEANINGA shared (Medusa) FR is blocked.

INSTRUCTIONSUnblock the alarming module.

FAULT NAMERF Module configuring failed

FAULT ID1900: EFaultId_FrConfiguringFailed

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


FAULT NAMERF Module critical file not found

122 DN0951924



Base Station Alarms

FAULT ID1901: EFaultId_FrCriticalFileNotFound

MEANINGA critical configuration file is missing from the RF Module.


FAULT NAMERF Module failure








FAULT NAMERF Module out of order

FAULT ID1912: EFaultId_FrOutOfOrder

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



DN0951924 123



FAULT NAMERF loss of secondary optical interface

FAULT ID1930: EFaultId_FRLossOfSecondaryOptIf

MEANINGSecondary optical link between the System Module and RF Module is lost.





FAULT NAMERF module filter input power missing

FAULT ID1910: EFaultId_FrFilterInputPowerMissing

MEANINGThe RF Module filter has measured too low TX power.



FAULT NAMERF module power output faulty

FAULT ID1918: EFaultId_FrPowerOutputFault

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

124 DN0951924



Base Station Alarms



FAULT NAMERX out of order

FAULT ID1911: EFaultId_FrRxOutOfOrder

MEANINGThe RF Module RX RF synthesizer is not locked.



FAULT NAMERadio resources switched off

FAULT ID4057: EfaultId_RfSwitchedOffAl

MEANINGThe cells, whose TX carriers are served by the affected Antenna Lines are deactivated to reduce power transmitted by the Power Amplifier in Radio Module for the sake of pro-tecting the Power Amplifier against the HW failure due to operation under excessive VSWR value condition (antenna line impedance mismatch).

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

FAULT NAMEReceiving failure in Optical Interface

FAULT ID2002: EFaultId_OIC_RxAl

DN0951924 125



MEANINGThe 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 Trans-ceiver, Antenna Filter or Antenna Line Device) is broken.

INSTRUCTIONS1. 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 indicates the faulty SFP. Replace the SFP if it is faulty.

3. Clean the connectors, test the fibre cable, and replace it if it is faulty.

4. If the previous steps do not help, replace the module behind the faulty link.

FAULT NAMESynchronization failure in Optical Interface <opt link/RP3 link>

FAULT ID2005: EFaultId_OIC_SyncChAl

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

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

FAULT NAMETX out of order

FAULT ID1907: EFaultId_FrTxOutOfOrder

MEANINGThe RF Module TX path is not usable.


126 DN0951924



Base Station Alarms










FAULT NAMETemperature too low (Heating ongoing)

FAULT ID1922: EFaultId_FrTemperatureTooLow

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

INSTRUCTIONSDuring RF startup only:

1. Heating of module is ongoing. Wait until the alarm is canceled. This may take up to 30 minutes.

DN0951924 127



2. If that does not help, block/unblock the RF Module.






FAULT NAMEUnit (module) dangerously overheating

FAULT ID1937: EFaultId_FrDangerouslyOverheat

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



FAULT NAME

128 DN0951924



Base Station Alarms

Unit SW download failed




FAULT NAMEUnit blocked

FAULT ID48: EFaultId_UnitBlockedAl

MEANINGA module is blocked with BTS Site Manager.

The purpose is to avoid fault indications that may be raised during the module mainte-nance task.

INSTRUCTIONSUnblock the module with BTS Site Manager.





DN0951924 129












FAULT ID1837: EFaultId_VSWRMajorAl

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


130 DN0951924



Base Station Alarms



DN0951924 131



2.31 7654 CELL OPERATION DEGRADEDProbable cause: Indeterminate



MeaningA major fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the alarm.




2. shelf number

3. slot

4. type of unit

5. unit number

6. subunit number




FAULT NAME10b8b coding error in optical interface device <opt link/RP3>

FAULT ID2004: EFaultId_OIC_LVDSRecAl

132 DN0951924



Base Station Alarms

MEANINGThe fibre cable has an interference; the data becomes faulty.

A physical connection failure between the optical interface and the summing function (caused by bad circuit joints, for example).

INSTRUCTIONS1. Reset the RF Module behind the faulty optical interface by blocking/unblocking it.

2. If that does not clear the fault situation, replace the RF Module that causes the alarm.


4. If the System Module is the only source causing the alarm, or actions mentioned above do not clear the fault situation, Replace the System Module that causes the alarm.

FAULT NAME3GPP/AISG communication administratively disabled

FAULT ID4142: EFaultId_Communication3gppAdministrativelyDisabledAl

MEANINGHDLC Link is disabled for reporting Antenna Line or IUANT port.

INSTRUCTIONSIn order to revert change, parameter Communication3gppEnabled should be enabled for reporting Antenna Line.

FAULT NAMEAntenna Carrier configuration failure

FAULT ID6259: EFaultId_AntennaCarrierMessageFailed

MEANINGAntenna carrier resources were not successfully set up during cell setup or cell deletion procedure due to failure of RX or TX resource. Affected cell might be not operational.

INSTRUCTIONSPerform the steps below in the listed order until the BTS fault disappears:1.Check cables towards Radio Module2.Reset Radio Module

DN0951924 133



3.Remove faulty unit









FAULT NAMEAntenna line device HW failure

FAULT ID1847: EFaultId_HardwareErrorAl

MEANINGA hardware failure detected by an antenna line device. Usually, this is a permanent fault (the hardware is broken).

INSTRUCTIONS1. Block/unblock the Radio module to give a power-off reset to the antenna line devices.


FAULT NAMEAntenna line device configuration failure

134 DN0951924



Base Station Alarms

FAULT ID1848: EFaultId_WorkingSoftwareMissingAl1888: EFaultId_AlConfigurationFailureAl

MEANINGAn antenna line or antenna line device is not properly configured.

INSTRUCTIONS1. Update the proper SW to the device.

2. Check/correct the antenna line configuration.


FAULT NAMEAntenna line failure

FAULT ID1836: EFaultId_ALOvercurrentAl

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

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

FAULT NAMEAntenna line operation degraded

FAULT ID4046: EFaultId_AntennaLineDegradedAl

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

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

DN0951924 135
















136 DN0951924



Base Station Alarms










FAULT NAMEBuffer over/underflow in clock crossing logic

FAULT ID2054: EFaultId_MuksuRxClkErrorAl

MEANINGClock crossing buffer underflow or overflow in RX block and the received data might not be valid. The fault is an indication of either too large clock drift between received signal and internal clock or wrong RX rate setting.

INSTRUCTIONS1. Check the status of the module behind the faulty link (power on, and so on).

2. Check the alarming fiber connection.

DN0951924 137

















138 DN0951924



Base Station Alarms

FAULT NAMEConfiguration file corrupted

FAULT ID1924: EFaultId_FrConfigurationFileCorrupted

MEANINGThe RF Module SW detected conflicting or corrupted configuration data.

INSTRUCTIONS1. Block/unblock the RF Module


FAULT NAMEDC voltage administratively disabled

FAULT ID4141: EFaultId_DcVoltageAdministrativelyDisabledAl

MEANINGFeeding voltage is disabled for selected Antenna Line.

INSTRUCTIONSIn order to revert changes, DC Voltage should be enabled for reporting Antenna Line.

FAULT NAMEFPGA SW update failed

FAULT ID1928: EFaultId_FrFpgaSwUpdateFailed

MEANINGThe FPGA software update has failed.



FAULT NAME

DN0951924 139



Failure in optical RP3 interface















140 DN0951924



Base Station Alarms

FAULT NAMEFrame clock missing

FAULT ID1903: EFaultId_FrFrameClockMissing

MEANINGThe System Module clock reference differs from the RF Module clock.









FAULT NAMEIncreased BER detected on the optical connection to radio module

FAULT ID1955: EFaultId_IncrBerOnRp3

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

DN0951924 141



INSTRUCTIONSNote! 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 con-nection is terminated and/or replace the fiber.





FAULT NAMEMHA unit operation failure

FAULT ID1869: EFaultId_MinorTMAFaultAl1870: EFaultId_MajorTMAFaultAl

MEANINGA fault in the Masthead Amplifier (MHA) is detected. The fault reduces the gain perfor-mance or completely prevents the MHA from functioning.


FAULT NAMEMast Head Amplifier fault

FAULT ID3120: EFaultId_MastHeadAmplifierFault

MEANING

142 DN0951924



Base Station Alarms

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


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

FAULT NAMEMast Head Amplifier fault above current window, <line>

FAULT ID1834: EFaultId_AboveCurrentWindowAl

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

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

FAULT NAMEMast Head Amplifier fault below current window, <line>

FAULT ID1835: EFaultId_BelowCurrentWindowAl

DN0951924 143



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

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





FAULT NAMENo feedback signal

FAULT ID1920: EFaultId_FrNoFeedBackSignal

MEANINGThe feedback signal to predistortion is too weak or missing. The TX performance is degraded.

INSTRUCTIONS

144 DN0951924



Base Station Alarms



FAULT NAMEOptical Interface Data/Control/Ethernet Buffer Full

FAULT ID2007: EFaultId_OIC_DBTxFullAl2008: EFaultId_OIC_CBRxFullAl2009: EFaultId_OIC_CBTxFullAl2010: EFaultId_OIC_EBFullAl

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

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

FAULT NAMEOptical interface buffer alarm

FAULT ID2051: EFaultId_Muksu_BufferAl

MEANINGRP3 or Ethernet buffering is not working, and the buffer becomes full. The optical device malfunctions. The fault might be generated because of synchronization problems or incorrect initialization.

INSTRUCTIONS1. Depending on the optical interface, reset the module behind the optical interface that causes the alarm by blocking/unblocking it.

2. If that does not clear the fault situation, replace the module behind the optical interface that causes the alarm.

3. If the System Module is the only alarm source, or replacing the RF Module does not clear the fault situation, replace the System Module that causes the alarm.

DN0951924 145



FAULT NAMERET Antenna control failure

FAULT ID1842: EFaultId_MotorJamAl1843: EFaultId_ActuatorJamAl1844: EFaultId_NotCalibratedAl1845: EFaultId_NotConfiguredAl1846: EFaultId_ActuatorInterferenceAl

MEANINGAntenna tilting is not possible or might function incorrectly.

INSTRUCTIONS1. Recalibrate the RET antenna.

2. If that does not help, replace the RET unit.

FAULT NAMERF BB Bus Configuration Error

FAULT ID1905: EFaultId_FrRfBbBusConfigError

MEANINGThe RF Module baseband bus is configured incorrectly.



FAULT NAMERF BB Bus Synchronization Error

FAULT ID1904: EFaultId_FrRfBbBusSynchError

MEANINGThe baseband bus between the System Module and RF Module is out of synchroniza-tion.

146 DN0951924



Base Station Alarms





FAULT NAMERF BB bus Connection transmission error

FAULT ID1906: EFaultId_FrRfBbBusConnTransError

MEANINGThere is an error in the baseband or optical bus.


2. (RF sharing case only) Check that all RP3-01 fiber links and SFP transceivers between systemmodule and radio module are properly connected and working. Replace brokenfiber link if needed.


FAULT NAMERF BB energy too high

FAULT ID1909: EFaultId_FrBbEnergyTooHigh

MEANINGThe TX feedback signal power is too high.



DN0951924 147



FAULT NAMERF Module failure








FAULT NAMERF Module file not found

FAULT ID1902: EFaultId_FrFileNotFound

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

INSTRUCTIONS1.Block/unblock the RF Module.

2.If that does not help, replace the alarming RF Module.

FAULT NAMERF Power decreased

FAULT ID1927: EFaultId_FrPowerDecreased

MEANINGThe highest temperature exceeds the power decrease limit.

148 DN0951924



Base Station Alarms


2. If that does not help, block/unblock the alarming RF Module.


FAULT NAMERF module filter input power missing

FAULT ID1910: EFaultId_FrFilterInputPowerMissing

MEANINGThe RF Module filter has measured too low TX power.



FAULT NAMERS485 IUANT port failure

FAULT ID4069: EFaultId_Rs485PowerFailureAl

MEANINGRadio Module or Filter (all others) has detected overcurrent on RS485 IUANTport. Some antenna line device is causing overload. Depending on HW implementation 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 occurring on port. Antenna line devices powered by the rs485 IUANT port are out of order.

INSTRUCTIONS1. Check the RS485 IUANT i/f and antenna line devices. Fix or replace the faulty parts/devices.

2. Alarm is cancelled only at RF Module reset or the BTS reset.

DN0951924 149



FAULT NAMERX out of order

FAULT ID1911: EFaultId_FrRxOutOfOrder

MEANINGThe RF Module RX RF synthesizer is not locked.



FAULT NAMESW corrupted

FAULT ID1850: EFaultId_SwCorruptedAl4029: EFaultId_SwCorruptedPermanentAl

MEANINGA corrupted SW file in the FLASH is detected.Unit cannot complete start-up.

INSTRUCTIONSUpdate the SW to the BTS.

FAULT NAMETX out of order

FAULT ID1907: EFaultId_FrTxOutOfOrder

MEANINGThe RF Module TX path is not usable.



150 DN0951924



Base Station Alarms













DN0951924 151



FAULT NAMETransmission quality deteriorated

FAULT ID1921: EFaultId_FrTransmissionQualityDetoriated

MEANINGThe TX signal adjustment fails.



FAULT NAMEUnit unidentified

FAULT ID1923: EFaultId_FrUnitUnidentified

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

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





152 DN0951924



Base Station Alarms






FAULT ID1838: EFaultId_VSWRMinorAl

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




DN0951924 153



2.32 7655 CELL NOTIFICATIONProbable cause: Indeterminate



MeaningA minor fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the alarm.




2. shelf number

3. slot

4. type of unit

5. unit number

6. subunit number



Below is the list of BTS fault(s) which may have caused this alarm in BTS LN4.0 release. In case of earlier SW release and in case you need more detailed fault descriptions refer to LTE System Libraries. The BTS fault descriptions are also included in BTS SW release documentation. If that does not help, contact your local Nokia Siemens Networks representative.

FAULT NAMEAntenna Line Device Operation Failure

FAULT ID

154 DN0951924



Base Station Alarms

1871: EFaultId_BusyAl1872: EFaultId_FormatErrorAl 1873: EFaultId_UnsupportedProcedureAl 1874: EFaultId_OutOfRangeAl

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

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











DN0951924 155
















156 DN0951924



Base Station Alarms
















DN0951924 157



FAULT NAMEFan failure

FAULT ID3050: EFaultId_FanFailure

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


1. Check the fan and cabling.

2. Replace the faulty fan module.

FAULT NAMEFile corrupted in SW download

FAULT ID28: EFaultId_SwPackageAl

MEANINGThe SW being downloaded is corrupted or incorrectly formed.

INSTRUCTIONS1. Retry the SW update.2. Save the snapshot and check the download status from the BTS SWDLreport in the snapshot file.

FAULT NAMEIncoherency In Cell Configuration

FAULT ID4044: EFaultId_IncoherencyCellConfigurationAl

MEANINGCell configuration is not officially supported.

INSTRUCTIONSCheck the configuration of the configured cell.

158 DN0951924



Base Station Alarms

FAULT NAMEPhich Power Boost not applied

FAULT ID6112: EFaultId_PhichPowerBoostAl

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

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

FAULT NAMERF Test loop faulty

FAULT ID1919: EFaultId_FrRfTestLoopFault

MEANINGThe RF Module cannot run the test loop.

INSTRUCTIONS1. Block/unblock the RF Module and make the test loop again.


FAULT NAMERadio resources switched off

FAULT ID4057: EfaultId_RfSwitchedOffAl

MEANINGThe cells, whose TX carriers are served by the affected Antenna Lines are deactivated to reduce power transmitted by the Power Amplifier in Radio Module for the sake of pro-tecting the Power Amplifier against the HW failure due to operation under excessive VSWR value condition (antenna line impedance mismatch).

DN0951924 159



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

FAULT NAMESystem information broadcast parameters overflow

FAULT ID6351: EFaultId_SystemInfoValueTagHandlingFailed

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

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

FAULT NAMETX failure in MIMO

FAULT ID4003: EFaultId_TxFailureTurnMimoOffAl

MEANINGDue to TX path failure MIMO (Multiple Input Multiple Output) functionality is not opera-tional in the cell related to the faulty TX.

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



MEANING

160 DN0951924



Base Station Alarms

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






FAULT NAMETemperature too low (Heating ongoing)

FAULT ID1922: EFaultId_FrTemperatureTooLow

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

INSTRUCTIONSDuring RF startup only:

1. Heating of module is ongoing. Wait until the alarm is canceled. This may take up to 30 minutes.

2. If that does not help, block/unblock the RF Module.




DN0951924 161





FAULT NAMEUnit (module) temperature is high

FAULT ID1936: EFaultId_FrTempHigh

MEANINGValidated module temperature is higher than the predefined maximum allowed value.

INSTRUCTIONSCheck the fans and ensure that the ambient temperature on the site is acceptable.


162 DN0951924



Base Station Alarms

2.33 7657 BASE STATION CONNECTIVITY DEGRADEDProbable cause: Indeterminate

Event type: Communications


MeaningA major fault (or faults) has occured in the base station interface. Check the reason for the fault from the supplementary text field of the alarm.


2. shelf number

3. slot

4. type of unit

5. unit number

6. subunit number

Additional information fieldsDestination IP address

InstructionsFAULT NAMETransport layer connection failure in S1 interface

FAULT ID6202: EFaultId_S1SctpEndpointAl

MEANINGThe transport path (SCTP) for connection to MME has broken. The reason for this might be an unplugged cable to MME. No transport path available to pursue operation on the faulty connection with the MME.

INSTRUCTIONSNote: Perform the steps below in the listed order until the alarm disappears:1. Check the connection with MME-based on whether the S1 link is broken respectively.2. Check if MME is operational.

If this fault happens right after a commissioning or a configuration change, verify the fol-lowing configuration data: IP address of the MME

FAULT NAMETransport layer connection failure in X2 interface

FAULT ID6203: EFaultId_X2SctpEndpointAl

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

INSTRUCTIONSNote: Perform the steps below in the listed order until the BTS Fault disappears:

DN0951924 163



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.


164 DN0951924



Base Station Alarms

2.34 7657 BASE STATION CONNECTIVITY DEGRADEDProbable cause: Indeterminate

Event type: Communications


MeaningA major fault (or faults) has occured in the base station interface. Check the reason for the fault from the supplementary text field of the alarm.

Identifying additional information fields1. rack (cabinet) number2. shelf number3. slot4. type of unit5. unit number6. subunit number

Additional information fieldsDestination IP address

InstructionsFAULT NAMEGTP-U Path Failure

FAULT ID6150: EFaultId_GtpuPathFailure

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

INSTRUCTIONS1) 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 eNB and the supervised network element.

FAULT NAMES1 SCTP path failure

FAULT ID6204: EFaultId_S1SctpPathAl

MEANINGOne of the transport paths(SCTP) in SCTP connection to MME has failed. Only applica-

DN0951924 165



ble when SCTP multi-homing is supported. An alternate transport path is available to pursue operation.

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

FAULT NAMES1 interface recovery failure

FAULT ID6317: EFaultId_S1ResetRetryOut

MEANINGS1 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 connec-tivity, MME has failed, etc.

INSTRUCTIONSNote: 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.

FAULT NAMES1 interface setup failure

FAULT ID6308: EFaultId_S1SetupRetryOut

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

INSTRUCTIONSNote: 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.

166 DN0951924



Base Station Alarms

FAULT NAMETransport layer connection failure in S1 interface

FAULT ID6202: EFaultId_S1SctpEndpointAl

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

INSTRUCTIONSNote: Perform the steps below in the listed order until the alarm disappears:1. Check the connection with MME based on whether the S1 link is broken respectively.2. Check if MME is operational.

If this fault happens right after a commissioning or a configuration change, verify the fol-lowing configuration data: IP address of the MME

FAULT NAMETransport layer connection failure in X2 interface

FAULT ID6203: EFaultId_X2SctpEndpointAl

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

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

FAULT NAMEX2 interface recovery failure

FAULT ID6303: EFaultId_X2ResetRetryOut

DN0951924 167



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

INSTRUCTIONSNote: 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.

FAULT NAMEX2 interface setup failure

FAULT ID6304: EFaultId_X2SetupRetryOut

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

INSTRUCTIONSNote: 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.


168 DN0951924



Base Station Alarms

2.35 7665 BASE STATION TRANSMISSION ALARMProbable cause: Indeterminate



MeaningA transmission fault (or faults) has occurred in the BTS. This alarm is an encapsulation alarm that is used to transfer the Flexi Transport Submodule (FTM) alarm data over the BTS O&M connection through RNC and OMS to NetAct. Encapsulation is used because the RNC alarm system cannot support the FTM alarms directly because of differences in the alarm structure.

In NetAct and OMS this alarm is shown in opened format. This means that the alarm number, alarm text and supplementary information are shown in original FTM format and the alarm printout is thus different in NetAct compared to alarm listings in RNC MML interface that shows these FTM alarms as instances of alarm number 7665.

Check the reason for the fault from the supplementary information fields and supple-mentary text field of the alarm. The actual documentation for the encapsulated alarm can be found in the BTS faults documents in LTE System Libraries.


Identifying additional information fields1. probable cause reported by FTM

2. the managed object reported by FTM

3. alarm number reported by FTM. The FTM has reserved alarm numbers from space 61000-61999

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

FAULT ID61059: FTM_TIMING_SOURCE_LOS

MEANINGIf two synchronization sources are configured in priority list for transport module and one synchronization sources is unavailable. This can be the clock source with higher or lower priority.

The Timing source lost on unit fault is masked by Synchronization lost fault. Meaning if both synchronization sources fail Timing source lost fault are cleared and only Synchro-nization lost is raised.

In the alarm:

DN0951924 169



Protocol can be PDH, Timing over Packet (ToP) and Synchronuous Ethernet.Unit number is always 1.The interface value is optional:- For PDH the value range depends on the hardware unit type: 1...4 (FTIB, FTLB); 1...8 (FTIF)- For Synchonuous Ethernet the value range depends on the hardware unit type: 1...3 (FTIB, FTLB); 1..2 (FSMF); 1..4 (FTIF) - It is not present for Timing over Packet.

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

FAULT NAMEAIS on unit $U, interface $IF

FAULT ID61151: FTM_AIS

MEANINGAlarm 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 intermediate network and AIS is sent instead of user traffic.

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

FAULT NAMEAutomatic BTS Operator Certificate retrieval unsuccessful

170 DN0951924



Base Station Alarms

FAULT ID61510: NO_CERTIFICATE

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

INSTRUCTIONSProvide the certificate.

FAULT NAMEBFD Session down in egress direction for session $S

FAULT ID61606: BFD DOWN Egress

MEANINGThe alarm is raised if the alarm is enabled, the BFD state of the session is not AdminD-own and the BFD packet from the far end contains the diagnostic code = 'Control Detec-tion Time Expired' AND no ingress alarm is present.

INSTRUCTIONSCheck the BFD configuration at local end.

FAULT NAMEBFD Session down in ingress direction for session $S

FAULT ID61605: BFD DOWN Ingress

MEANINGThe alarm is raised if the alarm is enabled, the BFD state for the session is not Admin-Down and nevertheless no BFD packet is received at the local end during the detection time.

INSTRUCTIONS1. Check the network between both BFD peers for physical link failures or misconfigu-rations.

2. Check if the BFD functionality in the peer is switched on and that the configurations of the BFD peers match.

DN0951924 171



FAULT NAMEBFD group $bfdGrpId down

FAULT ID61022: BFD DOWN

MEANINGThe alarm is raised if the BFD service is not available anymore on the BTS for a partic-ular interface (plain Ethernet or VLAN interface). In case only 1 BFD session is config-ured and activated for the interface, the alarm is raised if BFD on this session fails in either ingress or egress direction.In case 2 BFD sessions are configured and activated for the interface, the alarm is raised if there is a simultaneous BFD failure on both sessions. The BFD failure for each session might be either on ingress or egress direction.

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

FAULT NAMEBTS Trust Anchor due to expire

FAULT ID61618: TRUST ANCHOR EXPIRING

MEANINGNE stores trust anchors for its own trust chain. When all trust anchors are about to expire this alarm is sent.

INSTRUCTIONSUpdate trust anchors.


FAULT ID61010: FTM_BTS_RESET_REQUIRED

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

INSTRUCTIONS

172 DN0951924



Base Station Alarms

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

FAULT NAMECCM fault md $d level $ fault $f prio $p cause $c

FAULT ID61410: Ethernet OAM CCM fault

MEANINGThe alarm is triggered whenever a service OAM error related to the transmission of Con-tinuity Check Messages (CCM) persists on a given Ethernet interface over the period 2,5 s. The following alarms are defined:1) XC_CCM_defect, priority 5 (highest priority): Maintenance Domain level mismatch or Maintenance Association identification mismatch.2) Error_CCM, priority 4: Maintenance End Point identifier unknown, wrong CCM inter-val.3) Remote_CCM_Defect, priority 3: at least one of the remote peers does not receive CCM from its peers, or local does not receive CCM from peer since 3.5 times the trans-mission period.4) RDI_CCM, priority 1 (lowest priority): one remote peer detects RDI flag in the CCM frames.

The alarm shall display the following information:- Alarm Name- Alarm Priority- Alarm cause: if difference sources produce the same alarm- MD name- MD level at which the alarm was detected

INSTRUCTIONS1) Check cabling.2) Check CCM configuration at remote peer.

FAULT NAMECRL update failure due to cause $C

FAULT ID61074: CRL Update failure

MEANINGThis alarm is raised if the BTS cannot update the Certificate Revocation List (CRL) for one of the following reasons:- the LDAP binding fails

DN0951924 173



- the LDAP search is empty (no CRL found)/the LDAP search contains morethan one entry- the CRL signature validation fails- the CRL file exceeds the BTS storage limit- the BTS certificate is part of the CRL- DNS resolution for the CRL distribution point fails

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

FAULT NAMEDead peer detected

FAULT ID61030: FTM_DPD

MEANINGA dead peer was detected in one of the IPSec associations of the FTM.

It is possible that:- 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

INSTRUCTIONS1. 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 instruc-tions for handling those alarms.

FAULT NAMEEBER on unit $U, interface $IF

FAULT ID61104: FTM_EBER

MEANING

174 DN0951924



Base Station Alarms

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

INSTRUCTIONS1. 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 concerning the fault are on (such as Laser End of Life). If they are, follow the instructions for handling those alarms.

FAULT NAMEETH AIS fault interface $IF level $l mac addr $x

FAULT ID61411: Ethernet OAM ETH_AIS_fault

MEANINGA Maintenance Endpoint (MEP) received a valid ETH-AIS frame.

The alarm shows the following information:- Source MAC address of the MEP.

Additional information shows the following:- Maintenance Interface- Maintenance Association ID- Maintenance Domain name- Maintenance Domain level at which the alarm was detected

INSTRUCTIONS1) Check cabling.2) Check configuration at remote peer.

FAULT NAME

DN0951924 175



FTM Toggling <Fault name>

FAULT ID61619: FTM_FAULT_TOGGLING

MEANINGFTM Fault, for which fault name is mentioned in the Fault name -field, is togglingin the FTM. Toggling fault condition is informed to user with this newFTM Fault. Toggling faults are suppressed until the toggling alarm conditionis cleared. Severity of this FTM Fault is the same than the severity ofthe toggling FTM Fault.

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

FAULT NAMEFTM booted at $date due to $RCause

FAULT ID61006: FTM_RESET

MEANINGThe transport part of the BTS has been reset at the date and time given in the notifica-tion. The cause for the reset can be one of the following:

"power-on reset": Cold start"watchdog reset": System overload"startup failure": Failure during startup"software failure": Software failure"management reset": Reset triggered by management interface"fallback": Fallback executed

INSTRUCTIONSNo actions are required

FAULT NAME

176 DN0951924



Base Station Alarms

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

FAULT ID61500: FTM_SECURITY

MEANINGFive consecutive failed login attempts to the FTM have been performed.

INSTRUCTIONSCheck your username and password.

FAULT NAMELOF on unit $U, interface $IF

FAULT ID61028: FTM_LOF

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

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

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

FAULT NAMELOMF on slot $U, interface $IF

FAULT ID61150: FTM_LOMF

MEANINGLoss of multiframe. The interface referenced in the alarm text has lost the multiframe alignment.

DN0951924 177



Probable cause: the interface type has not been configured to meet the framing of the interface at the far end. For E1 interfaces, the configuration of the far-end node should be E1 Multiframe.

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

FAULT NAMELOS on unit $U, [Ethernet] interface $IF

FAULT ID61029: FTM_LOS

MEANINGNo 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 interface- the electrical signal is excessively attenuated- the port at the connected far end node is switched off

INSTRUCTIONS1. 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 instruc-tions 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.

FAULT NAMELicense missing for feature $feature on interface $if

FAULT ID61400: FTM_LICENSE_MISSING

MEANINGThe feature referenced in the alarm text has been configured without installing a valid license.

178 DN0951924



Base Station Alarms

Probable cause: A valid license that would allow the operation of the feature is not avail-able in the WBTS.

This BTS fault can be displayed in the followings variants:License Missing for additional 2 E1, T1 interfaceLicense Missing for Timing Over Packet

INSTRUCTIONSDownload a valid license to the WBTS.

FAULT NAMELink OAM critical link event $E on unit $U, interface $F

FAULT ID61077: Link OAM critical link event alarm

MEANINGA Link OAM PDU containing a critical link event flag was received on the Ethernet inter-face. 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.

INSTRUCTIONS1)Inspect details of the type of the critical event through online configuration manage-ment.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.

FAULT NAMELink OAM link lost on unit $U, interface $F

FAULT ID61076: Link OAM link lost alarm

MEANINGOn an interface for which the Link OAM functionality was switched on, no Link OAM PDUs were received during the period specified in configuration parameter linkLostTime

DN0951924 179



(2..10 seconds, step 1 second).

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

FAULT NAMELink OAM loopback inserted on unit $U, interface $F by $P peer

FAULT ID61075: Link OAM loopback alarm

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

INSTRUCTIONSNone.

FAULT NAMEMissing or non-compliant SFP module on unit $U, interface $I

FAULT ID61050: FTM_SFP

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

INSTRUCTIONSInsert an SFP module with the correct laser type (class 1) to the Gigabit Ethernet inter-face of the unit.

FAULT NAMENTP server is not accessible

FAULT ID61613: NTP_SERVER_UNREACHABLE

MEANING

180 DN0951924



Base Station Alarms

BTS shall report BTS alarm if NTP server is not accessible.

INSTRUCTIONScheck the connectivity to NTP servercheck the NTP server configuration at BTS.

FAULT NAMEPoor Quality SSM on unit $UID $IF

FAULT ID61624: SSM_POORQUALITY

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

INSTRUCTIONS

FAULT NAMERDI on unit $U, interface $IF

FAULT ID61152: FTM_RDI

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

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

FAULT NAMERouting misconfiguration for application $a

FAULT ID61073: ROUTING_MISCONFIGURATION

DN0951924 181



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

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

FAULT NAMESSM Timed Out on unit $UID $IF

FAULT ID61623: SSM_TIMEOUT

MEANINGIn case the incoming SSM is not anymore received for a certain time period (configured via 'ssmTimeout' parameter) this an alarm is raised.

INSTRUCTIONS

FAULT NAMESynchronization lost

FAULT ID61058: FTM_SYNC_LOSS

MEANINGAll transport related timing sources are lost at transport module. All configured synchro-nization sources from the configured priority list are unavailable.

Probable cause: The transmission links selected for clock source are faulty. The reason can be alarms on the interfaces (for example, LOS).

The Synchronization lost fault is masking Timing source lost on unit fault.

Note 1: This fault/alarm doesn't indicate that eNb is running in hold-over mode; please refer for hold-over indication to fault/alarm BTS Reference clock missing (1816)

INSTRUCTIONSUse the BTS Site Manager to check which interfaces have been configured as synchro-nization sources.

182 DN0951924



Base Station Alarms

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

FAULT NAMETWAMP PLR Threshold Crossed

FAULT ID61611: PLR_THRESHOLD_CROSSED

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

INSTRUCTIONS

FAULT NAMETWAMP RTT Threshold Crossed

FAULT ID61610: RTT_THRESHOLD_CROSSED

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

INSTRUCTIONS

FAULT NAMEToP master service $IP unusable

FAULT ID61631: TOP_MASTER_UNUSABLE

MEANINGThe 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 doesn't match the requested rate by eNB

DN0951924 183



INSTRUCTIONSCheck the cable connectivity.Check the TOP configuration.

FAULT NAMETransport module missing

FAULT ID61201: TRANSPORT_MODULE_MISSING

MEANINGUnit missing. The slot has been configured to hold a unit but the plug-inunit is not physically present in the slot.

Probable causes:

- the unit has been configured but not detected- the unit is broken and therefore not detected

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

FAULT NAMEVendor BTS certificate due to expire

FAULT ID61616: VENDOR_CERTIFICATE_EXPIRING

MEANINGThe BTS raises 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 expiry described in WBTS_SEC_46333

1 day ... 4999 days with default 1825 days.

INSTRUCTIONSCheck that the vendor BTS certificate expiry date and renew it.

184 DN0951924



Base Station Alarms


alm_lte_lbts_alarms.pdf

Documents

operating documentation

software products

additional information

environmental services

product names

product packaging

mentioned hardware

power use