rnc base station alarm

WCDMA RAN, Rel. RU40, Operating Documentation, Issue 04WCDMA RAN, Rel. RU40, Operating Documentation, Issue 04

Multicontroller RNC, IPA-RNC and Flexi Direct RNC Base Station Alarms (7000-7900)DN99580892

Issue 10BApproval Date 2013-06-14

Confidential

2 DN99580892Issue 10B

Multicontroller RNC, IPA-RNC and Flexi Direct RNCBase Station Alarms (7000-7900)

Id:0900d805809d5bdfConfidential

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 Solutions and 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 trans-mitted in any form or means without the prior written permission of Nokia Solutions and 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 Solutions and 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 Solutions and Networks and the customer. However, Nokia Solutions and 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 Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks, explain issues which may not be covered by the document.

Nokia Solutions and Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Solutions and Networks BE LIABLE FOR ERRORS IN THIS DOCU-MENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © 2013 Nokia Solutions and Networks. 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.

Nokia Solutions and 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 Solutions and Networks for any additional informa-tion.

DN99580892 3

Multicontroller RNC, IPA-RNC and Flexi Direct RNC Base Station Alarms (7000-7900)


Table of ContentsThis document has 292 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 List of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 7401 EXTERNAL AL 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3 7402 EXTERNAL AL 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4 7403 EXTERNAL AL 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5 7404 EXTERNAL AL 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

6 7405 EXTERNAL AL 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

7 7406 EXTERNAL AL 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

8 7407 EXTERNAL AL 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

9 7408 EXTERNAL AL 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

10 7409 EXTERNAL AL 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

11 7410 EXTERNAL AL 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

12 7411 EXTERNAL AL 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

13 7412 EXTERNAL AL 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

14 7413 EXTERNAL AL 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

15 7414 EXTERNAL AL 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

16 7415 EXTERNAL AL 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

17 7416 EXTERNAL AL 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

18 7417 EXTERNAL AL 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

19 7418 EXTERNAL AL 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

20 7419 EXTERNAL AL 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

21 7420 EXTERNAL AL 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

22 7421 EXTERNAL AL 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

23 7422 EXTERNAL AL 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

24 7423 EXTERNAL AL 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

25 7424 EXTERNAL AL 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

26 7425 EXTERNAL AL 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

27 7426 EXTERNAL AL 26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

28 7650 BASE STATION FAULTY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

29 7651 BASE STATION OPERATION DEGRADED . . . . . . . . . . . . . . . . 70

30 7652 BASE STATION NOTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . 119

4 DN99580892



31 7653 CELL FAULTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

32 7654 CELL OPERATION DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . 174

33 7655 CELL NOTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

34 7660 BASE STATION LICENCE EXPIRED . . . . . . . . . . . . . . . . . . . . . 211

35 7661 BASE STATION LICENCE NOTIFICATION . . . . . . . . . . . . . . . . 213

36 7665 BASE STATION TRANSMISSION ALARM . . . . . . . . . . . . . . . . . 216

37 7740 BEATING WCDMA BTS ALARM. . . . . . . . . . . . . . . . . . . . . . . . . 238

38 7750 FAILURE IN WCDMA WBTS O&M CONNECTION . . . . . . . . . . 239

39 7761 RNW O&M SCENARIO FAILURE . . . . . . . . . . . . . . . . . . . . . . . . 243

40 7762 RNW DATABASE OPERATION FAILURE . . . . . . . . . . . . . . . . . 249

41 7771 WCDMA CELL OUT OF USE . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

42 7772 HSDPA CONFIGURATION FAILED . . . . . . . . . . . . . . . . . . . . . . 255

43 7773 INSECURE O&M CONNECTION . . . . . . . . . . . . . . . . . . . . . . . . 260

44 7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS . .261

45 7776 HSDPA FAILURE IN WCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

46 7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE . . . . . . 266

47 7779 RECOVERY ACTIONS ONGOING . . . . . . . . . . . . . . . . . . . . . . . 268

48 7780 HSUPA FAILURE IN WCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

49 7781 NETWORK ELEMENT CONFIGURATION ERROR . . . . . . . . . . 272

50 7782 HSUPA CONFIGURATION FAILED . . . . . . . . . . . . . . . . . . . . . . 274

51 7783 IP BASED D-NBAP LINK FAILURE. . . . . . . . . . . . . . . . . . . . . . . 279

52 7784 RECOVERY ACTION FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . 280

53 7786 WCDMA BASE STATION OUT OF USE. . . . . . . . . . . . . . . . . . . 283

54 7794 ALARM STATUS REQUEST HAS TIMED OUT . . . . . . . . . . . . . 286

55 7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG . . . . . 287

56 7796 HIGH SPEED COMMON CHANNEL PROBLEM . . . . . . . . . . . . 290

DN99580892 5


Summary of changes

Id:0900d805809d5c0dConfidential

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

Changes made between issues 10A and 10B

Modified alarm

Changes made between issues 10 and 10A

Modified alarms

Changes made between issues 09F and 10

Modified alarms

7775

7651 7653

7650 7660 7772 7782

7651 7661 7773 7783

7652 7665 7775 7784

7653 7761 7778 7786

7654 7762 7779 7795

7655 7771 7781 7796

6 DN99580892



List of Alarms

1 List of Alarms7401 EXTERNAL AL 1

7402 EXTERNAL AL 2

7403 EXTERNAL AL 3

7404 EXTERNAL AL 4

7405 EXTERNAL AL 5

7406 EXTERNAL AL 6

7407 EXTERNAL AL 7

7408 EXTERNAL AL 8

7409 EXTERNAL AL 9

7410 EXTERNAL AL 10

7411 EXTERNAL AL 11

7412 EXTERNAL AL 12

7413 EXTERNAL AL 13

7414 EXTERNAL AL 14

7415 EXTERNAL AL 15

7416 EXTERNAL AL 16

7417 EXTERNAL AL 17

7418 EXTERNAL AL 18

7419 EXTERNAL AL 19

7420 EXTERNAL AL 20

7421 EXTERNAL AL 21

7422 EXTERNAL AL 22

7423 EXTERNAL AL 23

7424 EXTERNAL AL 24

7425 EXTERNAL AL 25

7426 EXTERNAL AL 26

7650 BASE STATION FAULTY

7651 BASE STATION OPERATION DEGRADED

7652 BASE STATION NOTIFICATION

7653 CELL FAULTY

7654 CELL OPERATION DEGRADED

7655 CELL NOTIFICATION

7660 BASE STATION LICENCE EXPIRED

7661 BASE STATION LICENCE NOTIFICATION

7665 BASE STATION TRANSMISSION ALARM

7740 BEATING WCDMA BTS ALARM

7750 FAILURE IN WCDMA WBTS O&M CONNECTION

DN99580892 7


List of Alarms


7761 RNW O&M SCENARIO FAILURE

7762 RNW DATABASE OPERATION FAILURE

7771 WCDMA CELL OUT OF USE

7772 HSDPA CONFIGURATION FAILED

7773 INSECURE O&M CONNECTION

7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS

7776 HSDPA FAILURE IN WCEL

7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE

7779 RECOVERY ACTIONS ONGOING

7780 HSUPA FAILURE IN WCEL

7781 NETWORK ELEMENT CONFIGURATION ERROR

7782 HSUPA CONFIGURATION FAILED

7783 IP BASED D-NBAP LINK FAILURE

7784 RECOVERY ACTION FAILURE

7786 WCDMA BASE STATION OUT OF USE

7794 ALARM STATUS REQUEST HAS TIMED OUT

7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG

7796 HIGH SPEED COMMON CHANNEL PROBLEM

Alarm parametersThe following parameter settings are the default settings. The operator can modify them with MML/SCLI command.

The following listing also contains alarm event types. Please note that this information is not part of the alarm parameter listing and it is not possible to change those values using MML/SCLI commands. The information here is for documentation purposes only.

NR TEXT CLS OUT SDC SDD CDL LVT--------------------------------------------------------------------------------

7401 EXTERNAL AL 1 * NONE 00:10 - 00:10 - EVENT TYPE: ENVIRONMENTAL




8 DN99580892



List of Alarms














DN99580892 9


List of Alarms











7650 BASE STATION FAULTY *** 0 00:10 - 00:10 - EVENT TYPE: EQUIPMENT

7651 BASE STATION OPERATION DEGRADED ** 5 00:10 - 00:10 - EVENT TYPE: EQUIPMENT

7652 BASE STATION NOTIFICATION * NONE 00:10 - 00:10 - EVENT TYPE: EQUIPMENT

7653 CELL FAULTY *** 0 00:10 - 00:10 -

10 DN99580892



List of Alarms

EVENT TYPE: EQUIPMENT

7654 CELL OPERATION DEGRADED ** 5 00:10 - 00:10 - EVENT TYPE: EQUIPMENT

7655 CELL NOTIFICATION * NONE 00:10 - 00:10 - EVENT TYPE: EQUIPMENT

7660 BASE STATION LICENCE EXPIRED *** 0 00:10 - 00:10 - EVENT TYPE: EQUIPMENT

7661 BASE STATION LICENCE NOTIFICATION * NONE 00:10 - 00:10 - EVENT TYPE: EQUIPMENT

7665 BASE STATION TRANSMISSION ALARM * NONE 00:10 - 00:10 - EVENT TYPE: EQUIPMENT

7740 BEATING WCDMA BTS ALARM ** 5 00:00 - 00:00 - EVENT TYPE: PROCESSING ERROR

7750 FAILURE IN WCDMA WBTS O&M CONNECTION * NONE 00:10 - 00:10 - EVENT TYPE: COMMUNICATIONS

7761 RNW O&M SCENARIO FAILURE ** 5 00:40 - 00:00 - EVENT TYPE: QUALITY OF SERVICE

7762 RNW DATABASE OPERATION FAILURE ** 5 00:05 - 00:00 - EVENT TYPE: PROCESSING ERROR

7771 WCDMA CELL OUT OF USE ** 5 02:00 - 00:20 - EVENT TYPE: QUALITY OF SERVICE

7772 HSDPA CONFIGURATION FAILED ** 5 00:05 - 00:05 - EVENT TYPE: QUALITY OF SERVICE

7773 INSECURE O&M CONNECTION ** 5 00:00 - 00:00 - EVENT TYPE: COMMUNICATIONS

7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS * NONE

DN99580892 11


List of Alarms


00:00 - 00:00 - EVENT TYPE: PROCESSING ERROR

7776 HSDPA FAILURE IN WCEL ** 5 00:05 - 00:00 - EVENT TYPE: QUALITY OF SERVICE

7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE ** 5 00:00 - 00:00 - EVENT TYPE: QUALITY OF SERVICE

7779 RECOVERY ACTIONS ONGOING * NONE 00:00 - 00:00 - EVENT TYPE: QUALITY OF SERVICE

7780 HSUPA FAILURE IN WCEL ** 5 00:05 - 00:00 - EVENT TYPE: QUALITY OF SERVICE

7781 NETWORK ELEMENT CONFIGURATION ERROR *** 2 00:00 - 00:00 - EVENT TYPE: PROCESSING ERROR

7782 HSUPA CONFIGURATION FAILED ** 5 00:05 - 00:05 - EVENT TYPE: QUALITY OF SERVICE

7783 IP BASED D-NBAP LINK FAILURE ** 5 00:30 - 00:30 - EVENT TYPE: COMMUNICATIONS

7784 RECOVERY ACTION FAILURE ** 5 00:00 - 00:00 - EVENT TYPE: COMMUNICATIONS

7786 WCMDA BASE STATION OUT OF USE ** 500:30 - 00:15 -EVENT TYPE: QUALITY OF SERVICE

7794 ALARM STATUS REQUEST HAS TIMED OUT ** 500:00 - 00:00 -EVENT TYPE: COMMUNICATIONS

7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG * NONE00:15 - 00:15 -EVENT TYPE: PROCESSING ERROR

7796 HIGH SPEED COMMON CHANNEL PROBLEM * NONE00:05 - 00:00 -EVENT TYPE: QUALITY OF SERVICE

12 DN99580892



List of Alarms

DN99580892 13


7401 EXTERNAL AL 1


2 7401 EXTERNAL AL 1Meaning

This is an external user-defined alarm. The alarm is defined bythe user in an HW database.

Supplementary information fields

InstructionsThe operation depends on what kind of alarm is used as externalalarm no. 1.

CancellingDo not cancel the alarm. The system cancels the alarm automaticallywhen the fault has been corrected.

14 DN99580892



7402 EXTERNAL AL 2


This is an external user-defined alarm. The alarm is defined bythe user in a HW database.




DN99580892 15


7403 EXTERNAL AL 3







16 DN99580892



7404 EXTERNAL AL 4






DN99580892 17


7405 EXTERNAL AL 5







18 DN99580892



7406 EXTERNAL AL 6






DN99580892 19


7407 EXTERNAL AL 7







20 DN99580892



7408 EXTERNAL AL 8






DN99580892 21


7409 EXTERNAL AL 9







22 DN99580892



7410 EXTERNAL AL 10






DN99580892 23


7411 EXTERNAL AL 11







24 DN99580892



7412 EXTERNAL AL 12






DN99580892 25


7413 EXTERNAL AL 13







26 DN99580892



7414 EXTERNAL AL 14






DN99580892 27


7415 EXTERNAL AL 15







28 DN99580892



7416 EXTERNAL AL 16






DN99580892 29


7417 EXTERNAL AL 17







30 DN99580892



7418 EXTERNAL AL 18






DN99580892 31


7419 EXTERNAL AL 19







32 DN99580892



7420 EXTERNAL AL 20






DN99580892 33


7421 EXTERNAL AL 21







34 DN99580892



7422 EXTERNAL AL 22






DN99580892 35


7423 EXTERNAL AL 23







36 DN99580892



7424 EXTERNAL AL 24






DN99580892 37


7425 EXTERNAL AL 25







38 DN99580892



7426 EXTERNAL AL 26



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 externalalarm number 26.


DN99580892 39




28 7650 BASE STATION FAULTYMeaning

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

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

The effect of the fault on the functioning of the network elementdepends on the fault description. For more information, see basestation fault descriptions in WCDMA RAN and Flexi Direct SystemLibraries.

Supplementary information fields1 rack (cabinet) number

2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number

For more information, see instructions on Alarm Structure.

InstructionsVerify the configuration of a BTS by checking thecommissioning, cabling and correct installation of theunits/modules at the BTS. Make sure the environment doesnot cause the fault.Before a unit/module is replaced at the BTS, the siteshould be reset to recover from any temporary faults whichmight have caused the malfunctioning of the unit/module.When an active alarm is a 'Start' alarm, a site reset isrequired to cancel the alarm. If the site reset or moduleblock/unblock does not help, replace the faulty unit/module(see the source of the alarm and instructions fields of thecorresponding alarms).Below is the list of BTS fault(s) which might have causedthis alarm in BTS WN 8.0 release. In case of earlier SWrelease and in case you need more detailed faultdescriptions refer to WCDMA RAN and Flexi Direct SystemLibraries. The BTS fault descriptions are also included inBTS SW release documentation. If that does not help,

40 DN99580892




contact your local Nokia Siemens Networks representative.

FAULT NAME : ATM faultyFAULT ID : 45: EFaultId_ATM_SFN_PollingTimeoutAlMEANING : A WAM internal failure.INSTRUCTIONS: 1. If ping to the BTS is working, restart the BTS remotely. 2. Ping the BTS. If it is not working but ping to the AXC is working, then restart the AXC remotely so that the BTS is also restarted automatically. 3. Ping the AXC. If it is not working, visit the site and restart the BTS. If this does not help, replace the alarming WAM unit.

FAULT NAME : ATM processor faultyFAULT ID : 590: EFaultId_AtmMcuBrokenAl 594: EFaultId_SfnIrqFailureAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: There is a fault in the WAM processor SFN interrupt or the SFN is not being updated in the WSPC MCU. There is a MCU failure in the WAM or the ATM loop test at start-up has failed. FlexiBTS: There is such a fault in the FSM that the SFN is not being updated in the FSP MCU.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. If ping to the BTS is working, restart the BTS remotely. 2. Ping the BTS. If it is not working but ping to the AXC is working, restart the AXC remotely so that the BTS is also automatically restarted. 3. Ping the AXC. If it is not working, visit the site and restart the BTS. If this does not help, replace the alarming WAM unit. FlexiBTS: 1. Reset the BTS. 2. If the BTS reset does not help, change the alarming module.

FAULT NAME : Antenna link is downFAULT ID : 476: EFaultId_Rp3BusErrorMEANING : Antenna (RP3) link is down: transmitter or receiver drops from synchronization.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears: FlexiBTS: 1. If the alarming module is the Extension System Module (FSM2), restart it. If the alarming module is the System Module (FSM1), restart the BTS. 2. If that does not help, replace the alarming FSM.

DN99580892 41




FlexiLiteBTS: 1. Reset the BTS. 2. Replace the Flexi Lite BTS. UltraSite/EUBB: 1. If the alarming unit is WSPF, or if all WSPFs generate this alarm, restart the BTS. 2. If that does not help, replace the WSMF.

FAULT NAME : BB bus message collision errorFAULT ID : 2018: EFaultId_Muksu_StxPortCollAlMEANING : Routed RF baseband bus messages have collided and the data in the output baseband internal link is lost because the baseband bus is incorrectly configured.INSTRUCTIONS: 1. Check antenna mapping to the local cells in the commissioning file. 2. Check the cables between the System Module and RF Module. 3. Replace the alarming module.

FAULT NAME : BB bus message in the wrong slotFAULT ID : 2057: EFaultId_MuksuMsgInWrongSlotAlMEANING : Baseband bus message multiplexing slot for the message is not possible to be fulfilled.INSTRUCTIONS: 1. Check antenna mapping to the local cells in the commissioning file. 2. Check the cables between the System Module and RF Module. 3. Replace the alarming module.

FAULT NAME : BB bus reception errorFAULT ID : 2044: EFaultId_TransuSMTimeOffAlMEANING : The master frame in the received RF BB 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.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : BB bus reception error (summing device)FAULT ID : 2016: EFaultId_Muksu_SMTimeOffAlMEANING : The master frame in the received baseband bus frame is not in the correct place related to the internally generated master frame pulse. Either the frame has been set in the

42 DN99580892




wrong place (PI delay), or the data itself is in the wrong place.INSTRUCTIONS: FlexiBTS: 1. Check the cables between the Master System Module and RF Module/Extension System Module. 2. Replace the unit causing the fault (Master System Module, Extension System Module, RF Module, FBIA). UltraSite/EUBB: 1. Replace the unit causing the fault (WSPF, WSMF).

FAULT NAME : BB bus transmission errorFAULT ID : 2017: EFaultId_Muksu_SRx10b8bAlMEANING : A decoding error has been detected in the baseband internal link. The data packet is lost or the content is corrupted. This situation is also triggered when the links do not synchronize with each other.INSTRUCTIONS: FlexiBTS: 1. Check the cables between the Master System Module and RF Module/Extension System Module. 2. Replace the alarming unit (System Module). UltraSite/EUBB: 1. Replace the alarming unit (WSMF).

FAULT NAME : BOFU Post failedFAULT ID : 4021: EFaultId_BOFU_Post_failedAlMEANING : The unit or module has been tested during BTS power-on self test (POST) and a failure has been detected.INSTRUCTIONS: 1. Block/unblock the alarming unit/module. 2. Remove/reinsert the alarming unit/module. 3. Replace the alarming unit/module.

FAULT NAME : BTS blockedFAULT ID : 50: EFaultId_BTSBlockedAlMEANING : The BTS is blocked with BTS Site Manager. The meaning of the fault is to avoid alarms that may be raised during a BTS maintenance task.INSTRUCTIONS: To cancel the alarm, unblock the BTS. Unblocking of the BTS causes a site reset.

FAULT NAME : BTS config error (WSMA and WSMB can not coexist)FAULT ID : 55: EFaultId_WsmaWsmbVersionConflictAlMEANING : WSMA and WSMB units are detected in the same cabinet. They cannot coexist in the BTS.INSTRUCTIONS: Replace the conflicting unit WSMA with the WSMB, or vice versa.

DN99580892 43




FAULT NAME : BTS configuration not supportedFAULT ID : 4097: EFaultId_BtsConfNotSupportedAlMEANING : FSP does not support requested BTS configuration.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears. 1. Change BTS configuration. 2. Reset BTS.

FAULT NAME : BTS file errorFAULT ID : 1802: EFaultId_FileRequestFlashAl 1803: EFaultId_FileParsingFailedAl 1866: EFaultId_RulesMissingAl 1867: EFaultId_RulesParsingAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: The BTS unit properties data is invalid or missing. FlexiBTS: The BTS module properties data or optical interface FPGA file is invalid or missing. The FSP MCU SW file is invalid or missing. FlexiLiteBTS: The BTS properties data or optical interface FPGA file is invalid or missing.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Download two different SW packages so that the faulty file is removed from the BTS. 2. Download the SW again. 3. If the fault still exists after 10 minutes, replace the alarming unit. FlexiBTS, FlexiLiteBTS: 1. Download two different SW packages so that the faulty file is removed from the BTS. 2. Download the SW again. 3. Replace the System Module.

FAULT NAME : BTS file errorFAULT ID : 136: EFaultId_TcomConfFileAlMEANING : Telecom configuration file(s) are invalid, missing, or not accessible.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Download two different SW packages so that the faulty file is removed from the BTS. 2. Download the SW again. 3. If the fault still exists after 10 minutes, replace the alarming unit. FlexiBTS:

44 DN99580892




1. Download two different SW packages so that the faulty file is removed from the BTS. 2. Download the SW again. 3. Replace the System Module or FBIA.

FAULT NAME : BTS internal SW management problemFAULT ID : 3090: EFaultId_BtsInternalSwManagementProblemMEANING : A software update to a unit/module or subassembly has failed, or a corrupted SW file has been detected in the FLASH.INSTRUCTIONS: Note: Perform the steps below in the listed order. FlexiBTS: 1. Check other active BTS faults. If the ROM disk is corrupted, change the alarming module. 2. Reset the RF Module and/or FBIA and/or System Module, depending on the alarm source: a. Reset the RF Module by blocking/unblocking it. b. Reset the FBIA by blocking/unblocking it. c. Reset the System Module. 3. Update and activate the SW to the BTS. 4. Check the SW files. 5. Replace the alarming module/unit. UltraSite/EUBB: 1. Check other active BTS faults. If the ROM disk is corrupted, change the alarming unit. 2. Reset the alarming unit. 3. Update and activate the SW to the BTS. 4. Check the SW files. 5. Replace the alarming unit. FlexiLiteBTS: 1. Reset the and/or DSP and/or CC&T, depending on the alarm source. 2. Update and activate the SW to the BTS. 3. Check the SW files. 4. Replace the alarming Flexi Lite BTS.

FAULT NAME : BTS is uncommissionedFAULT ID : 4030: EFaultId_NoCommDataAlMEANING : Commissioning file download has not started from BTS Site Manager nor from NetAct during autoconfiguration.INSTRUCTIONS: 1. Make sure that autoconfiguration is enabled in NetAct. 2. Check the autoconnection/autoconfiguration information with BTS Site Manager. 3. Load the correct commissioning file to BTS.

FAULT NAME : Baseband Bus failureFAULT ID : 3020: EFaultId_BaseBandBusFailureMEANING : The BTS has detected an abnormal operation or a failure in

DN99580892 45




the BTS internal baseband bus. The failure cannot be pointed to a specific unit/module but there are several possible fault sources.INSTRUCTIONS: Note: Perform the steps below in the listed order. FlexiBTS: 1. Check other active BTS alarms and act accordingly. 2. Check the cables between the System Module and RF Module/Extension System 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 Extension System Module by blocking/unblocking it. c. Reset the master System Module. 4. Replace the alarming RF Module/Extension System Module. 5. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation, replace the alarming master System Module. UltraSite/EUBB: 1. Check other active BTS alarms and act accordingly. 2. Reset the alarming unit. 3. Check the cables in backplane. 4. Replace the alarming unit. FlexiLiteBTS: 1. Check other active BTS faults and act accordingly. 2. Reset the BTS by blocking/unblocking it. 3. Replace the Flexi Lite BTS.

FAULT NAME : Baseband bus configuration of <x> was rejectedFAULT ID : 1811: EFaultId_BbBus_ConfFailedAlMEANING : The baseband bus related configuration of <x> was rejected by the HW, SW, DSP, or LTX.INSTRUCTIONS: Replace the alarming module. FlexiLiteBTS: Note! Perform the steps below in the listed order until the fault disappears: 1. Restart the BTS 2. Replace the FlexiLiteBTS unit

FAULT NAME : Baseband reference clock missing (WCI)FAULT ID : 1006: EFautlId_BaseBandReferenceClkMssMEANING : The WCI does not deliver the Baseband Reference Clock (BRCLK) for the relevant units, because either the transceiver circuit in the WSC or the bus is faulty, or the WSC does not distribute the clock source.INSTRUCTIONS: You have two alternative procedures: 1. If there is only one clock unit in the cabinet, replace the WSC. 2. If Step 1 does not help, replace the WCI.

46 DN99580892




OR 1. If there are two clock units in the cabinet, replace the WCI. 2. If Step 1 does not help, replace both WSC units.

FAULT NAME : Baseband reference clock missing (WSC)FAULT ID : 910: EFaultId_DualWscBrclkMssMEANING : The WSC is not able to deliver the clock signals required by the other units.INSTRUCTIONS: Replace the WSC.

FAULT NAME : Boot configuration inconsistency detectedFAULT ID : 4102: EFaultId_BootConfigurationInconsistencyAlMEANING : During SW update it has been detected that configurations of active and passive SW in HW unit are the same. Active and passive SW configurations are compared: - before SW download, - during SW activation, before active and passive SW switch, - during start-up.INSTRUCTIONS: Replace the faulty unit.

FAULT NAME : Commissioning error: <x>FAULT ID : 3060: EFaultId_CommissioningErrorMEANING : Some of the commissioning parameters are either missing or faulty. Or there is a mismatch between them.INSTRUCTIONS: Note: Perform the steps below in the listed order. 1. Check the commissioning parameters with the BTS Site Manager Commissioning Wizard. 2. Load the correct commissioning file to the BTS.

FAULT NAME : Communication failureFAULT ID : 1806: EFaultId_CommunicationFailureAlMEANING : Communication with the application <x> failed. The application has not replied to the message that has been sent/resent to it.INSTRUCTIONS: FlexiBTS: 1. Make surethatthe 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. FlexiLiteBTS: 1. If the Flexi Lite BTS LED does not light up, the BTS is faulty. Check the Flexi Lite BTS. 2. Check the fault history.

DN99580892 47




FAULT NAME : Communication failureFAULT ID : 458: EFaultId_VcpErrorMEANING : An internal communication fault in the decoding process in the module, for example, a decode co-processor error.INSTRUCTIONS: 1. Reset the alarming unit/module. 2. Replace the alarming unit/module.

FAULT NAME : Communication failure inside WSPFAULT ID : 414: EFaultId_McbspMessagePoolExhausted 446: EFaultId_McbspSwsErrorMEANING : An internal communication failure between the DSP processors.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Block the alarming WSP. 2. The fault might be in the WTR or WPA (see Troubleshooting instructions). Otherwise, check for other alarms. If the " autonomous reset as recovery action" alarm has occurred for the alarming WSP, replace the alarming WSP unit. FlexiBTS: 1. If only one FSP in BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module). UltraSite/EUBB: 1. If only one WSPF in the BTS generates this alarm, the WSPF is faulty. 2. If all WSPFs generate this alarm, the BTS is faulty. 3. Block/unblock the BTS. 4. If that does not help, replace the faulty module.

FAULT NAME : Configuration error: <x>FAULT ID : 3070: EFaultId_ConfigurationErrorMEANING : There is an incompatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch between the BTS configuration and the RNC/Flexi Direct RNC parameters.INSTRUCTIONS: Note: Perform the steps below in the listed order. 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 RNC/Flexi Direct RNC match the BTS HW configuration (for example frequency, power). 3. Check the RNC/Flexi Direct RNC BTS faults for the alarming local cell (LCR).

48 DN99580892




4. Recommission the BTS to ensure that all parameters are correctly configured.

FAULT NAME : Configuration file is not supportedFAULT ID : 4035: EFaultId_ConfigurationFileNotSupportedAlMEANING : BTS software does not support the commissioning file downloaded to the BTS.INSTRUCTIONS: 1. Check and correct the contents of the commissioning file. 2. Download the corrected commissioning file to the BTS and reset it.

FAULT NAME : Connection to transmission brokenFAULT ID : 1829: EFaultId_ConnToTransBrokenAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The AXC is missing, data or states are corrupted in the ATM, or there are possible hardware or transmission related failures. FlexiBTS: Data or states are corrupted in the ATM, or there are possible hardware or transmission related failures.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Check the transmission connections. 2. If the transmission type is the AXC, reset the WAM. 3. If that does not help, replace the alarming unit. FlexiBTS: 1. Check the transmission connections. 2. Reset the site. 3. If that does not help, replace the alarming System Module.

FAULT NAME : DSC-bus failureFAULT ID : 208: EFaultId_DscNodeBlockedAlMEANING : There is a failure in the bus between the WAM and WSP (DSC-bus), which means that messages do not get through via that DSC-bus.INSTRUCTIONS: 1. Block/unblock the alarming unit. 2. Replace the alarming unit.

FAULT NAME : DSC-bus failureFAULT ID : 597: EFaultId_DscFaultAlMEANING : There are communication problems between the WAM and WSP. This alarm may occur if the WSP is hot removed or the WSP crashes.INSTRUCTIONS: If the failure still exists after the site reset, replace the WAM unit.

DN99580892 49




FAULT NAME : DSP accelerator initialization failureFAULT ID : 2302: EFaultId_RsaInitializationErrorMEANING : There is a signal processing (DSP) related malfunction in the BTS. This might affect the signal processor receiver functionality processed by the alarming unit/module.INSTRUCTIONS: FlexiBTS: 1. If the alarming module is the Extension System Module (FSM2), restart it. If the alarming module is the System Module (FSM1), restart the BTS. 2. If that does not help, replace the alarming FSM or unit. UltraSite/EUBB: 1. If the alarming unit is WSPF, restart it. If all WSPFs generate this alarm, restart the BTS. 2. If that does not help, replace the alarming unit. Restart can be done by BTS block/unblock, system module block/unblock from BTS SEM and from NetAct to reset BTS.

FAULT NAME : DSP failure in radiolink creationFAULT ID : 129: EFaultId_DspHoldAlMEANING : Radio link creation has been failing repeatedly because of DSP rejection.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Block/unblock the alarming unit. 2. Replace the alarming unit. UltraSite/EUBB: 1. Block/unblock the EUBB subrack. 2. Replace the alarming unit. FlexiBTS: If the faulty FSP is in the extension module, block/unblock the extension module, otherwise block/unblock the BTS.

FAULT NAME : DSP mode change failedFAULT ID : 139: EFaultId_DspModeChangeFailAlMEANING : DSP configuration to correct mode was not successful.INSTRUCTIONS: Replace the alarming module/unit.

FAULT NAME : DSP overheatedFAULT ID : 4101: EFaultId_DspOverheatingAlMEANING : DSP overheating was detected during DSP initialization.INSTRUCTIONS: 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, replace the alarming FSP module.

50 DN99580892




FAULT NAME : Downlink data buffer synchronization failureFAULT ID : 2031: EFaultId_Transu_DlDbSynchChAlMEANING : The downlink data buffer has lost synchronization.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : FSP in resetting stateFAULT ID : 4068: EFaultId_FspResetAlMEANING : FSP is undergoing a cold reset.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears: FlexiBTS: 1. Reset the BTS. 2. Replace the faulty module/unit. FlexiLiteBTS: 1. Reset the BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : FSP overheatingFAULT ID : 4077: EFaultId_FspOverheatingAlMEANING : Temperature on the FSP board exceeds the critical threshold value.INSTRUCTIONS: 1. Check the fans andensurethat the ambient temperature on the site is acceptable. 2. If that does not help, replace the alarming module.

FAULT NAME : FSP/WSP Frame synchronisation failedFAULT ID : 1822: EFaultId_Fr_SyncAlMEANING : The frame synchronization burst, SFN or SFCLK signal from the FCM/WSPF is missing.INSTRUCTIONS: 1. Reset the site. 2. If that does not help, replace the System Module.

FAULT NAME : Failure in optical RP3 interfaceFAULT ID : 3030: EFaultId_FailureInOptical_Rp3InterfaceMEANING : The BTS has detected an abnormal operation or a failure in an optical RP3 interface between two modules. The failure cannot be pointed to a specific module but there are several possible fault sources.INSTRUCTIONS: Note: Perform the steps below in the listed order until the alarm disappears.

DN99580892 51




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

FAULT NAME : Failure in replaceable baseband unitFAULT ID : 3003: EFaultId_FbiaFailureAlMEANING : The BTS has detected an abnormal operation or a failure in the BTS replaceable baseband unit.INSTRUCTIONS: Note: Perform the steps below in the listed order until the BTS fault indication disappears. 1. Check the other active BTS faults and act accordingly. 2. Check if the plug-in type baseband unit is installed correctly. 3. Reset the alarming baseband unit. 4. Replace the alarming baseband unit.

FAULT NAME : Fatal OSE ErrorFAULT ID : 418: EFaultId_OseFatalErrMEANING : The operating system (OSE) goes into the error handler with a fatal status. The cause can be, for example, out of memory situation. If only one FSP in BTS generates this fault, there is a malfunction in one of the FSP submodules. If all FSPs generate this fault, there is a malfunction in the FSM.INSTRUCTIONS: FlexiBTS: Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the System Module. 2. Replace the System Module. FlexiLiteBTS: Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the FlexiLiteBTS 2. Replace the FlexiLiteBTS UltraSite/EUBB: 1. If only one WSPF in BTS generates this fault, the WSPF

52 DN99580892




is faulty. 2. If all WSPFs generate this fault, BTS is faulty. 3. Block/unblock BTS. 4. If that does not help, replace the faulty module.

FAULT NAME : Fault between WAM and WSP SFN (WSP)FAULT ID : 412: EFaultId_LostFrameSync 428: EFaultId_SystemFrameNumberParityMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: Synchronization between the WAM and WSP is lost. FlexiBTS: Synchronization between the FCM and FSP/FBIA is lost. UltraSite/EUBB: Synchronization between the WAMF and WSPF is lost.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. If only one WSP in the cabinet generates this alarm, the WSP is faulty. 2. If all WSPs in a subrack generate this alarm, the WAM is faulty. 3. If all WSPs generate this alarm, the WSC/WMC is faulty. Otherwise, check for other alarms. If the " autonomous reset as a recovery action" alarm has occurred for the faulty WSP, replace the faulty WSP unit. FlexiBTS: 1. If only one FSP/FBIA in the BTS generates this alarm, the FSP/FBIA is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module) or faulty FBIA. UltraSite/EUBB: 1. If only one WSPF in the BTS generates this alarm, the WSPF is faulty. 2. If all WSPFs generate this alarm, the BTS is faulty. 3. Block/unblock the BTS. 4. If that does not help, replace the faulty module.

FAULT NAME : Fault in ATM interfaceFAULT ID : 309: EFaultId_AtMuxAlMEANING : The WAM ATM interface is not responding correctly.INSTRUCTIONS: 1. Block/unblock the alarming unit. This resets the BTS. 2. If that does not help, replace the alarming unit.

FAULT NAME : Fault in ATM interfaceFAULT ID : 591: EFaultId_SarChipBrokenAl 592: EFaultId_UxAsicAl 593: EFaultId_AtmHostBrokenAlMEANING : WAM ATM interface, AXC or CIF bus failure. The AXC may have

DN99580892 53




been reset. WAM processor failure.INSTRUCTIONS: 1. Block/unblock the alarming unit. This will reset the BTS. 2. Swap the WAM units between subracks and check if the alarm follows the unit. Replace the alarming WAM unit. 3. Check the AXU. 4. Check the backplane connection between the WAM and AXU.

FAULT NAME : Fault in O&M and DSP SW interfaceFAULT ID : 42: EFaultId_ WSPC_PPC_SFN_PollingTimeoutAl 43: EFaultId_DSP_PollingTimeoutAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: Communication failure between the WAM and DSP. FlexiBTS: Communication failure between the FCM and FSP/FBIA. UltraSite/EUBB: Communication failure between the WSMF and WSPF. FlexiLiteBTS: Communication failure between the SCR and FSP.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Block/unblock the alarming unit. 2. Replace the alarming unit. UltraSite/EUBB: 1. Block/unblock the EUBB subrack. 2. Replace the alarming unit. FlexiBTS: 1. Block/unblock the alarming module. 2. Replace the system module/plug-in FSP. FlexiLiteBTS: 1. Block/unblock Flexi Lite BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : File System access failedFAULT ID : 4088: EFaultId_FileSystemAccessFailedAlMEANING : File System access operation like: - File System mounting - file opening failedINSTRUCTIONS: Update SW to the BTS, unless it is automatically updated by NetAct.

FAULT NAME : Firmware SW mismatchFAULT ID : 2056: EFaultId_SwMismatchAlMEANING : The SW update to the BTS has failed or the BTS SW got corrupted.INSTRUCTIONS: 1. Switch to the latest active BTS configuration. 2. Retry the SW update.

54 DN99580892




FAULT NAME : Frame clock deviation faultFAULT ID : 2014: EFaultId_Muksu_SFCRCompDevAlMEANING : Synchronization to the clock control unit frame pulse has been achieved earlier but it differs from the currently received frame pulse. The internally generated frame clock might have drifted.INSTRUCTIONS: FlexiBTS: 1. Check the cables between the System Module and RF Module/Extension System Module. 2. Reset the alarming System Module. 3. Replace the alarming System Module. UltraSite/EUBB: 1. Reset the alarming WSMF. 2. Replace the alarming WSMF.

FAULT NAME : Incompatible SW version detectedFAULT ID : 23: EFaultId_IncompatibleSwVersionAl 24: EFaultId_ObsoleteSwVersionAlMEANING : A new unit with incompatible SW has probably been inserted in the BTS.INSTRUCTIONS: Update compatible SW to the BTS (check the SW versions to see the active SW version, and update the active SW version), unless it is automatically updated by NetAct. NOTE: If also fault 10:EFaultId_NoConnectionToUnitAl is active on the source unit then SW update should be postponed until fault 10:EFaultId_NoConnectionToUnitAl is cancelled. Related BTS - AXC interface: check the SW version of the BTS and AXC, and update compatible SW to the AXC or BTS.

FAULT NAME : Incompatible unit detectedFAULT ID : 83: EFaultId_WtraWsmaWspaNotSupportedInCabinetAl 91: EFaultId_WrongUnitTypeInCabinetAlMEANING : An unsupported unit (for example a WSMA, WTRA, WSPA, WMCM or WTRB) has been detected in the cabinet.INSTRUCTIONS: Replace the unsupported unit with a unit of the correct type.

FAULT NAME : Internal MTU configuration failureFAULT ID : 4025: EFaultId_MtuConfigurationFailureAlMEANING : Internal Maximum Transfer Unit (MTU) configuration failed on FCM or FSP/FBIA.INSTRUCTIONS: 1. Reset the alarming System Module or unit. 2. Replace the alarming System Module or unit

DN99580892 55




FAULT NAME : Internal communication errorFAULT ID : 4087: EFaultId_InternalCommunicationErrorAlMEANING : Reliable message delivery service is not able to deliver an internal message to a recipient (FSP or FSM), and sends an asynchronous notification to the message sender about the unreachable recipient.INSTRUCTIONS: 1. Make sure that the unit/module is properly connected. 2. Reset the alarming unit. 3. Replace the alarming unit.

FAULT NAME : Internal delay measurement failureFAULT ID : 1893: EFaultId_InternalDelayMeasurementFailureAlMEANING : An autonomous internal delay measurement has failed. The TCOM was not able to measure the internal delay for a cell for any of the RAKEs in a certain BB unit.INSTRUCTIONS: None

FAULT NAME : Invalid configuration fileFAULT ID : 4036: EFaultId_InvalidConfigurationFileAlMEANING : The commissioning file is missing, or an incorrect commissioning file has been detected during a BTS startup as follows: "Validation failed because of incompatible data"INSTRUCTIONS: 1. Check and correct the contents of the commissioning file. 2. Recommission the BTS with a valid commissioning file.

FAULT NAME : Master unit has lost connection to the slave unitFAULT ID : 4019: EFaultId_KeepAliveStatusErrorAlMEANING : Connection to the DSP submodule has been lost or the submodule reports an error situation.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears: FlexiBTS: 1. Reset the BTS. 2. Replace the faulty module/unit. FlexiLiteBTS: 1. Reset the BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : Message routing problem in receiver (RX)FAULT ID : 2058: EFaultId_MuksuMsgRoutingFailedAlMEANING : If a message does not get routed an interrupt is generated. Considered normal when Faradays are starting up and RP3 sync done.INSTRUCTIONS: If RF is the source:

56 DN99580892




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

FAULT NAME : Module dangerously overheatingFAULT ID : 4071: EFaultId_SysDangerouslyOverheatAlMEANING : Highest validated temperature value on FSP board exceeds the threshold value.INSTRUCTIONS: Note! Perform the steps below in the listed order. 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 NAME : No baseband capacity for common channelsFAULT ID : 132: EFaultId_NoBBCapasityForCommonChannelsMEANING : There is not enough common channel capacity to set up any cells to the BTS, because Efficient Baseband or Full Baseband HSDPA is allocated (last WSP/FSP card is fully reserved).INSTRUCTIONS: None

FAULT NAME : No connection to AXUFAULT ID : 21: EFaultId_AxuResetAlMEANING : The master WAM detected that the AXU does not respond to polling messages.INSTRUCTIONS: 1. Check for alarms on the AXC. 2. Restart the AXC remotely. This will also cause a BTS restart. 3. Change the alarming AXC unit.

FAULT NAME : No connection to BTS transport submoduleFAULT ID : 3511: EFaultId_NoConnectionToFtAlMEANING : The connection to the BTS transport submodule is lost.INSTRUCTIONS: Note: Perform the steps below in the listed order. 1. Reset the site. 2. Replace the Transport submodule, which is located inside the System Module.

FAULT NAME : No connection to unitFAULT ID : 10: EFaultId_NoConnectionToUnitAl 4052: EFaultId_ConnectionToUnitLostAlMEANING : Connection to a unit that belongs to the BTS configuration

DN99580892 57




has been lost or FSP cannot be detected.INSTRUCTIONS: FlexiBTS: 1. Make sure that the module is properly connected. If the module LED does not light up, the module is faulty. Check the alarming module. In case of two FSM-r3, check also SRIO cable connection between the system modules. 2. Check the fault history. FlexiLiteBTS: Check the fault history. UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Check the fault history, alarming unit and subrack. 2. If the SW has been updated recently, reload the SW. 3. If the WAF or WIC is alarming, try recommissioning the site. 4. Make sure that the unit is properly connected. If the unit LED does not light up, the unit is faulty. The fault might also be in the WPS unit or backplane. 5. Check the power cables, connectors, and the I2C bus cables. Cancel alarms: Removing and inserting the WIC, WSM or primary WAM causes a site reset. If both WSCs are removed, inserting the first removed WSC back into the cabinet causes a site reset. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First, try to reset the site with the software. If that does not help, replace the alarming unit. If the WSMF unit is not present (replaced by WSMB)in BTS, alarming WSPFs are not used and should be removed from BTS. WSPFs can be removed, because without a WSMF unit BTS works as UltraSite not as EUBB.

FAULT NAME : Not able to synchronize baseband bus with <x>FAULT ID : 1815: EFaultId_BbBus_SyncFailedAlMEANING : The baseband bus synchronization towards <x> failed.INSTRUCTIONS: FlexiLite: Replace the alarming module/plug-in FSP. FlexiLiteBTS: Replace the Flexi Lite BTS.

FAULT NAME : Optical Interface Frame clock faultyFAULT ID : 2003: EFaultId_OIC_CleanerLockAlMEANING : The VCXO does not get correct control voltage from the PLL filter of the clock cleaner. This may happen because of an unsuccessful clock recovery in the optical interface because of a missing or degraded input signal.INSTRUCTIONS: 1. Block/unblock the System Module.

58 DN99580892




2. Replace the System Module.

FAULT NAME : Optical interface data/control/Ethernet buffer fullFAULT ID : 2006: EFaultId_OIC_DBRxFullAl 2007: EFaultId_OIC_DBTxFullAl 2008: EFaultId_OIC_CBRxFullAl 2009: EFaultId_OIC_CBTxFullAl 2010: EFaultId_OIC_EBFullAlMEANING : The RP3 or Ethernet buffering is not working and the buffer becomes full. The optical device is malfunctioning. The fault might be generated because of synchronization problems or incorrect initialization.INSTRUCTIONS: Swap the alarming and working links. Then check where the alarm is reported. If the alarming link remains the same, replace the System Module. If the alarming link changes, replace the RF Module behind that link.

FAULT NAME : Oven oscillator clock missingFAULT ID : 903: EFaultId_OcxoClkMss 911: EFaultId_DualWscOcxoClkMssMEANING : The WSC is not able to deliver the clock signals required by the other units.INSTRUCTIONS: Replace the clock unit.

FAULT NAME : Oven oscillator clock missingFAULT ID : 1819: EFaultId_OcxoClkMissAlMEANING : The 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.INSTRUCTIONS: 1. Block/unblock the System Module. 2. Replace the System Module.

FAULT NAME : Oven oscillator heating failureFAULT ID : 1817: EFaultId_Ov_Osc_HeatAlMEANING : The OCXO warm-up takes too long and the OCXO does not become active within a period of eight minutes from the power-on. The ambient temperature can also be too low or it changes too fast.INSTRUCTIONS: FlexiBTS: Replace the alarming module. FlexiLiteBTS: Replace the FlexiLiteBTS.

FAULT NAME : Oven oscillator missing pulseFAULT ID : 1820: EFaultId_OcxoPulseMissingAlMEANING : The output signal of the OXCO has some problems and one or

DN99580892 59




more clock pulses are missed.INSTRUCTIONS: 1. Block/unblock the System Module. 2. Replace the System Module.

FAULT NAME : PLL status not lockedFAULT ID : 4010: EFaultId_PLLStatusNotLockedAlMEANING : BTS monitors the FSP/FBIA/WSPF/WSMF PLL (Phase-Locked Loop) lock status and PLL locking fails.INSTRUCTIONS: FlexiBTS: 1. Block/unblock the FSM/FBIA. 2. If that does not help, replace the FSM/FBIA. UltraSite/EUBB: 1. Block/unblock the WSMF. 2. If that does not help, replace the WSMF. 3. Block/unblock the WSPF. 4. If that does not help, replace the WSPF.

FAULT NAME : POST test failedFAULT ID : 69: EFaultId_Post_test_failedAlMEANING : A failure in the unit/module has been detected during the BTS power-on self test (POST).INSTRUCTIONS: 1. Block/unblock the alarming unit/module. 2. Remove/re-insert the alarming unit/module. 3. Replace the alarming unit/module. FlexiLiteBTS: 1. Replace the FlexiLiteBTS.

FAULT NAME : Parallel Interference Cancellation stream failure detectedFAULT ID : 2310: EFaultId_PicStreamFailureMEANING : RACH RAKE sends this fault when Parallel Interference Cancellation stream failure is detected.INSTRUCTIONS: FlexiBTS: Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the System Module. 2. Replace the System Module. UltraSite/EUBB: 1. If only one WSPF in the BTS generates this fault, the WSPF is faulty. 2. If all WSPFs generate this fault, the BTS is faulty. 3. Block/unblock the BTS. 4. If that does not help, replace the faulty module.

FAULT NAME : Power unit output voltage faultFAULT ID : 1301: EFaultId_WpsPwrOutVoltageMEANING : The output voltage is too low or too high. Usually the reason for the fault is the unit itself but in

60 DN99580892




some cases the reason can be the unit that the WPS feeds. If a short circuit occurs in the fed unit, it may affect the WPS and the "Output Voltage Fault" alarm is generated.INSTRUCTIONS: 1. Check the other active alarms. 2. Check the units that are supplied by the alarming WPS. 3. Check the backplane connectors and cables. 4. Replace the alarming WPS unit.

FAULT NAME : R-bus errorFAULT ID : 425: EFaultId_RbusErrorMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The bus between the WSP and WTR does not work. The R-bus errors are probably caused by a faulty WSM or WTR. FlexiBTS: Error in the FSP or in the connection between the FSP and FCM.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. If the WSM/WMC also generates an alarm from a WTR unit, check the WTR and WSM cable. 2. If there are no active WSM/WMC alarms, the reason for the alarm is a faulty WSM/WMC or WSP. 3. Run a WCDMA BTS loop test to locate the faulty unit. 4. If the WSP is faulty, block/unblock it. 5. Replace the faulty unit. FlexiBTS: 1. Check the cabling between the System Module and RF Module. 2. Check the active RF Module alarms and act accordingly. 3. Replace the faulty module (System Module).

FAULT NAME : RP1 synchronization burst errorFAULT ID : 2052: EFaultId_OicRp1FcbAlMEANING : A new RP1 Frame Clock Burst (FCB) burst/message has been received from the RP3-01 interface while processing the previous burst/message.INSTRUCTIONS: 1. Reset the alarming Extension System Module by blocking/unblocking it. 2. If that does not clear the fault situation, replace the alarming Extension System Module. 3. If the System Module is the only alarming source or replacing the Extension System Module does not clear the fault situation, replace the alarming System Module.

FAULT NAME : SFN Signal errorFAULT ID : 2036: EFaultId_Transu_SfnSignalAlMEANING : A system frame number reception fault, an illegal SFN value in uplink.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.

DN99580892 61




2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : SFN synchronization failureFAULT ID : 41: EFaultId_WSPC_PPC_SFN_PollingSynchAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The WSP is not synchronized with the WAM. FlexiBTS: The FSP/FBIA is not synchronized with the FCM. FlexiLiteBTS: The FSP is not synchronizaed with the SCR UltraSite/EUBB: The WSPF is not synchronized with WSMF.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Block/unblock the alarming unit. 2. Replace the alarming unit. UltraSite/EUBB: 1. Block/unblock the EUBB subrack. 2. Replace the alarming unit. FlexiBTS: 1. Block/unblock the alarming module. 2. Replace the system module/plug-in FSP. FlexiLiteBTS: 1. Reset the BTS 2. Replace the FlexiLiteBTS unit

FAULT NAME : SRIO chain configuration was rejectedFAULT ID : 4015:EFaultId_Srio_ConfFailedAlMEANING : The platform SW rejected the baseband bus related SRIO configuration for Faraday core.INSTRUCTIONS: Replace the alarming unit/module.

FAULT NAME : SRIO multicast configuration failedFAULT ID : 4066: EFaultId_SrioMulticastConfFailedAlMEANING : Response is not received or response is received with unsuccessful status for SRIO multicast configuration related messages.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears. 1. Block/unblock the BTS. 2. Replace the alarming unit.

FAULT NAME : SW fallbackFAULT ID : 4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl 4083: EFaultId_FallbackDueToConfigurationDataMigrationFailureAl

62 DN99580892




4085: EfaultId_FallbackDueToTransportRequestAlMEANING : 4082: Source unit has reached the maximum number of reset attempts, that is the source unit cannot successfully finish start-up after the SW update. 4083: Source unit requests SW fallback due to a critical problem that occurred in start-up after the SW update, that is configuration data migration failed. 4085: Transport SW on the source unit indicates a need for software fallback.INSTRUCTIONS: If the 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 NAME : Starting temperature below minimumFAULT ID : 1827: EFaultId_StartTempBelowMinAlMEANING : BTS cannot start properly, because FSPs cannot be powered up at too cold conditions.INSTRUCTIONS: 1. Wait until the module is automatically heated to the required start-up temperature. 2. If the fault is active for more than 2 hours, check the environmental conditions of the site.

FAULT NAME : Summing not enabled for message typeFAULT ID : 2059: EFaultId_MuksuSummingNotEnabledAlMEANING : Summing checks headers of the messages to be summed. If the header is not any of the allowed types, no summing is performed and an empty message is sent instead.INSTRUCTIONS: If FCM is the source: Reset FCM unit.

FAULT NAME : Summing service default initialization failedFAULT ID : 4092: EFaultId_MurkkuDefaultInitFailedAlMEANING : Summing service default configuration has failedINSTRUCTIONS: 1. Reset the System Module. 2. If a reset does not resolve the fault situation, replace the System Module.

FAULT NAME : Summing service release from reset failedFAULT ID : 1891: EFaultId_MuksuReleaseFromResetFailedAlMEANING : Summing service release from reset failed.INSTRUCTIONS: 1. Reset the System Module. 2. If a reset does not resolve the fault situation, replace the System Module.

DN99580892 63




FAULT NAME : Summing service release from reset failedFAULT ID : 4081: EFaultId_MurkkuReleaseFromResetFailedAlMEANING : Summing service release from reset failed.INSTRUCTIONS: 1. Reset the System Module. 2. If a reset does not resolve the fault situation, replace the System Module.

FAULT NAME : Synchronization failureFAULT ID : 2030: EFaultId_Transu_CompDevBbRfAlMEANING : The frame burst phase has moved compared to the internal counter. The FSM has already found the frame synchronization but the FSM frame clock does not match the FSM internal frame clock.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : Synchronization failure in Optical Interface <opt link/RP3 link>FAULT ID : 2005: EFaultId_OIC_SyncChAlMEANING : The RP3 channel has lost the frame synchronization state that it had achieved.INSTRUCTIONS: Swap the alarming and working links and then check where the alarm is now reported. If the alarming link remains the same, replace the System Module. If the alarming link changes, replace the RF Module behind that link.

FAULT NAME : System Module failureFAULT ID : 3000: EFaultId_SystemModuleFailureMEANING : The Flexi BTS has detected an abnormal operation or a failure in the internal functionality of the System Module. The Flexi Lite BTS has detected an abnormal operation or a failure in the internal functionality of the BTS.INSTRUCTIONS: Note: Perform the steps below in the listed order. Flexi BTS: 1. Check cables between the modules and replace them if needed. 2. Reset the System Module. 3. Replace the System Module. Flexi Lite BTS: 1. Reset the BTS. 2. Replace the Flexi Lite BTS.

64 DN99580892




FAULT NAME : TRANSU synchronization errorFAULT ID : 2045: EFaultId_TransuSyncAlMEANING : The RP3 TX/RX state machine or the T-bus receiver has changed its state. The synchronization is lost or the T-bus receiver has not synchronized.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : Tbus receiver parity faultFAULT ID : 2027: EFaultId_Transu_TbusParityAlMEANING : Data or synchronization failure in the System Module, two antenna carriers are affected.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : Telecom configuration failureFAULT ID : 109: EFaultId_TcomSlaveRegAl 110: EFaultId_UnitRnwConfigAl 111: EFaultId_TcomSlaveConfigAl 119: EFaultId_WspAllocationAlMEANING : Telecom slave configuration or registration failure. Unit RNW configuration failure. Telecom RNW reconfiguration failure. FlexiBTS: - FSP unit to FCM allocation failure - Faraday unit to FSP allocation failure Note that depending on the fault source, unit status might relate either to the state of particular carrier resource on FR module or FSP board on FCM, and may not be in line with the state of source HW unit. Or UltraSite, MetroSite, MetroSite 50, Triple-mode: WSP unit to WAM allocation failure. UltraSite/EUBB: Faraday unit to WSPF allocation failure.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: Block/unblock the alarming unit. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again. UltraSite/EUBB: If the alarming unit is WSPF, block/unblock

DN99580892 65




the EUBB subrack. FlexiBTS: If there was an internal failure, in the case of an FR, the module needs to be blocked/unblocked to get it initialized/configured again. FlexiBTS Rel2: If the alarming unit is FSPC, block/unblock the alarming module.

FAULT NAME : Temperature alarmFAULT ID : 3040: EFaultId_TemperatureAlarmMEANING : The internal temperature of the RF Module or System Module exceeds the threshold value, orthe ambient temperature of the module(s) is beyond the specified limits.INSTRUCTIONS: Note: Perform the steps below in the listed order. 1. Check 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/unit by blocking/unblocking it. 4. Replace the alarming module/unit.

FAULT NAME : Ten consecutive Nacks received from a DSP at DCH setupFAULT ID : 149: EFaultId_DspNacksReceivedAlMEANING : One particular DSP Nacks DCH setup 10 times with cause "NotEnoughResources=10" or "AlreadyActivated_Allocated=22" within a 20 minute period.INSTRUCTIONS: FlexiBTS: If the faulty FSP is in the extension module, block/unblock the extension module, otherwise block/unblock the BTS. FlexiLiteBTS: 1. Block/unblock Flexi Lite BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : Unit SW download failedFAULT ID : 6: EFaultId_SwDownloadAlMEANING : Software update to a unit/subunit or module has failed. UltraSite, MetroSite: The fault can also be caused by disconnected CIF bus cables.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Download the BTS SW again. 2. If the alarming unit is WSP, block/unblock the WSP.

66 DN99580892




3. If the alarming unit is WAM or WPA, reset the BTS. 4. If that does not help, replace the alarming unit. FlexiBTS: 1. Download the BTS SW again. 2. FCM: Reset the BTS. 3. If Step 2 does not help, replace the alarming module. FlexiLiteBTS: 1. Download the BTS SW again. 2. Reset the BTS. 3. If Step 2 does not help, replace the Flexi Lite BTS.

FAULT NAME : Unit initialization failureFAULT ID : 12: EFaultId_TcomConfigAl 13: EFaultId_AtmConfigAl 15: EFaultId_InitializationAl 4040: EFaultId_InitFaultManAlMEANING : A unit/module or an IP address initialization has failed.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Block/unblock the alarming unit. 2. Check if the non-commissioned WAM is the Master WAM. If so, this causes the fault. Check the fault history to find out why the WAM switch-over occurred. 3. If the WAM is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 4. If step 3 does not help, replace the alarming unit. FlexiBTS: 1. Block/unblock the alarming module. If that does not help, replace the alarming module. 2. If the FCM/FCT is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the alarming module. FlexiLiteBTS: 1. Block/unblock the alarming module. If that does not help, replace the alarming module. 2. If the SCR is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the alarming module.

FAULT NAME : Unit not supported by current BTS SW versionFAULT ID : 95: EFaultId_NotSupportedUnitMEANING : An unsupported unit has been detected in the BTS. Typically, this happens when a new unit version is installed and there is older BTS SW in use that does not support the new unit version.INSTRUCTIONS: FlexiBTS, UltraSite/EUBB::

DN99580892 67




1. Upgrade the system module SW. 2. Replace the unit. FlexiLiteBTS: 1. Upgrade the Flexi Lite BTS software. 2. Replace the Flexi Lite BTS.

FAULT NAME : Unit synchronization failedFAULT ID : 16: EFaultId_SynchronizationAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The WAM/WSPC synchronization has failed. FlexiBTS: FCM/FCT/FSP synchronization has failed.INSTRUCTIONS: 1. Block/unblock the alarming unit. 2. Replace the alarming unit. FlexiLiteBTS: 1. Block/unblock the Flexi Lite BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : Unknown HW resourceFAULT ID : 94: EFaultId_UnknownUnitTypeMEANING : A unit cannot be identified by its product code or by its physical device address (object ID).INSTRUCTIONS: FlexiBTS: Replace the alarming unit/module. FlexiLiteBTS: Replace the Flexi Lite BTS.

FAULT NAME : Unknown product codeFAULT ID : 93: EFaultId_UnknownProductCodeMEANING : A module cannot be identified by its product code but is known by its physical device address (object_ID).INSTRUCTIONS: UltraSite/EUBB: Replace the alarming module. FlexiBTS: Replace the alarming module. FlexiLiteBTS: Replace the Flexi Lite BTS.

FAULT NAME : Uplink data buffer synchronization failureFAULT ID : 2033: EFaultId_Transu_UlDbSyncChAlMEANING : The uplink data buffer loses synchronization.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : Validation of signed file failedFAULT ID : 4145: EFaultId_SignatureValidationFailedAlMEANING : SW file validation against its signature failed.

68 DN99580892




INSTRUCTIONS: Trigger SW update for BTS to the requested SW version.

FAULT NAME : WAM internal errorFAULT ID : 300: EFaultId_AtmRmCommAlMEANING : The C-Plane Telecom SW does not communicate with the C-Plane TUPC SW because of a fault.INSTRUCTIONS: Replace the faulty unit

FAULT NAME : WCI baseband reference clock failureFAULT ID : 1001: EFaultId_RedundantClkMss 1002: EFaultId_MasterClkMssMEANING : The master or redundant WSC does not generate Baseband Reference Clock (BRCLK) to the WCI because of an internal failure or a clock driver failure in the WSC unit.INSTRUCTIONS: 1. Block/unblock the active WSC unit. 2. Replace the WCI unit. 3. Replace both WSC units.

FAULT NAME : WIB unit AC line break faultFAULT ID : 1309: EFaultId_AcLineBreakAlMEANING : There is a mains break. The BTS power supply is cut off.INSTRUCTIONS: Check the power supply to the BTS.

FAULT NAME : WSM failureFAULT ID : 3001: EFaultId_EubbWsmAlMEANING : The BTS has detected an abnormal operation or a failure in the internal functionality of the WSMF unit.INSTRUCTIONS: Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the alarm history, alarming unit and subrack. 2. Check that the unit is properly connected. If the unit LED does not light up, the unit is faulty. 3. Reset the BTS. 4. Replace the alarming unit.

FAULT NAME : WSMF WAM Interconnection FailureFAULT ID : 4049: EFaultId_WsmfWamInterconnectionFailureAlMEANING : Connection failure between WAMA and WSMFINSTRUCTIONS: Check that cables are connected between WAMA-WSMF and WSMF-AXCF.

FAULTNAME : WSP PCI-bus failureFAULT ID : 225: EFaultId_PCIInvalidDeviceAl

DN99580892 69




226: EFaultId_PCITargetNotFoundAl 227: EFaultId_PCITargetDSPAmountAlMEANING : There is a fault in the internal WSP/FSP PCI bus target (DSP) connections. Some of the WSP/FSP DSP processors may be broken and out of use.INSTRUCTIONS: Replace the alarming unit/module.


70 DN99580892




29 7651 BASE STATION OPERATION DEGRADEDMeaning

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

Check the reason for the fault from the supplementary text fieldof the alarm.



2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number

7 feature code


InstructionsVerify the configuration of a BTS by checking thecommissioning, cabling and correct installation of theunits/modules at the BTS. Make sure the environment doesnot cause the fault.Before a unit/module is replaced at the BTS, the siteshould be reset to recover from any temporary faults whichmight have caused the malfunctioning of the unit/module.When an active alarm is a 'Start' alarm, a site reset isrequired to cancel the alarm. If the site reset or moduleblock/unblock does not help, replace the faulty unit/module(see the source of the alarm and instructions fields of thecorresponding alarms).Below is the list of BTS fault(s) which might have causedthis alarm in BTS WN 8.0 release. In case of earlier SWrelease and in case you need more detailed fault

DN99580892 71




descriptions refer to WCDMA RAN and Flexi Direct SystemLibraries. The BTS fault descriptions are also included inBTS SW release documentation. If that does not help,contact your local Nokia Siemens Networks representative.

FAULT NAME : 10b8b coding error in Optical Interface device <opt link/RP3>FAULT ID : 2004: EFaultId_OIC_LVDSRecAlMEANING : The fiber cable has interference; the data becomes faulty. A physical connection failure between the optical interface and the summing function (caused by bad circuit joints, for example).INSTRUCTIONS: 1. 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 is causing the alarm. 3. If the System Module is the only source causing the alarm, or replacing the RF Module does not clear the fault situation, replace the System Module that is causing the alarm.

FAULT NAME : 2M external reference missingFAULT ID : 1899: EFaultId_2MExtRefMissAlMEANING : The reference clock monitoring has detected a loss of 2.048 MHz signal received from an external reference source, connected to the Sync In interface of the System Module.INSTRUCTIONS: Note! Perform the steps below in the listed order until the alarm disappears. 1. Check the cabling (connected to Sync In interface). 2. Check that the 2.048MHz reference source is working normally and the 2.048 MHz signal is available. 3. Replace the alarming module.FlexiLiteBTS: Replace the Flexi Lite BTS.

FAULT NAME : ATM faultyFAULT ID : 45: EFaultId_ATM_SFN_PollingTimeoutAlMEANING : A WAM internal failure.INSTRUCTIONS: 1. If ping to the BTS is working, restart the BTS remotely. 2. Ping the BTS. If it is not working but ping to the AXC is working, then restart the AXC remotely so that the BTS is also restarted automatically. 3. Ping the AXC. If it is not working, visit the site and restart the BTS. If this does not help, replace the alarming WAM unit.

FAULT NAME : ATM processor faultyFAULT ID : 590: EFaultId_AtmMcuBrokenAl

72 DN99580892




594: EFaultId_SfnIrqFailureAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: There is a fault in the WAM processor SFN interrupt or the SFN is not being updated in the WSPC MCU. There is a MCU failure in the WAM or the ATM loop test at start-up has failed. FlexiBTS: There is such a fault in the FSM that the SFN is not being updated in the FSP MCU.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. If ping to the BTS is working, restart the BTS remotely. 2. Ping the BTS. If it is not working but ping to the AXC is working, restart the AXC remotely so that the BTS is also automatically restarted. 3. Ping the AXC. If it is not working, visit the site and restart the BTS. If this does not help, replace the alarming WAM unit. FlexiBTS: 1. Reset the BTS. 2. If the BTS reset does not help, change the alarming module.

FAULT NAME : ATM traffic overloadFAULT ID : 304: EFaultId_TrafficCausedBufferOverflowAlMEANING : There is a buffer overflow caused by a traffic overload. The maximum capacity is exceeded and some data is discarded.INSTRUCTIONS: 1. Check that bandwidths (cells/s) are the same at the BTS, AXC and RNC. 2. Check the data integrity from the incoming Iub (see Troubleshooting instructions). 3. Check the other transmission elements' active faults (see the faults for AXC document).

FAULT NAME : Active clock tuning faultFAULT ID : 1831: EFaultId_ActiveClkTuningAlMEANING : The phase measurement cannot be performed in the active WSC or WMC.INSTRUCTIONS: 1. Run fast tuning with BTS Site Manager. 2. Block/unblock the alarming unit. 3. Replace the alarming unit. Note that because of a fault situation in the active clock, the redundant clock is not tuned. To make sure that the tuning is correct, run "Fast Tune BTS Clock" with BTS Site Manager after the switchover when the new WSC is taken into use. If there is a WMC or only one WSC, the tuning continues but the cells remain disabled.

DN99580892 73




FAULT NAME : Address mismatch in summingFAULT ID : 2019: EFaultId_Muksu_SsubMmAlMEANING : There is a baseband bus address mismatch in the summing. There are two possible causes: A configuration error (two different baseband units functioning) - after an acknowledgment the fault returns again. Data corruption on the bus - appears once when unsynchronized data is sent by the baseband.INSTRUCTIONS: Check the antenna mapping to the local cells in the commissioning file.

FAULT NAME : Antenna link is downFAULT ID : 476: EFaultId_Rp3BusErrorMEANING : Antenna (RP3) link is down: transmitter or receiver drops from synchronization.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears: FlexiBTS: 1. If the alarming module is the Extension System Module (FSM2), restart it. If the alarming module is the System Module (FSM1), restart the BTS. 2. If that does not help, replace the alarming FSM. FlexiLiteBTS: 1. Reset the BTS. 2. Replace the Flexi Lite BTS. UltraSite/EUBB: 1. If the alarming unit is WSPF, or if all WSPFs generate this alarm, restart the BTS. 2. If that does not help, replace the WSMF.

FAULT NAME : BB bus message in the wrong slotFAULT ID : 2057: EFaultId_MuksuMsgInWrongSlotAlMEANING : Baseband bus message multiplexing slot for the message is not possible to be fulfilled.INSTRUCTIONS: 1. Check antenna mapping to the local cells in the commissioning file. 2. Check the cables between the System Module and RF Module. 3. Replace the alarming module.

FAULT NAME : BB bus reception errorFAULT ID : 2044: EFaultId_TransuSMTimeOffAlMEANING : The master frame in the received RF BB 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.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP

74 DN99580892




is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : BB bus reception error (summing device)FAULT ID : 2016: EFaultId_Muksu_SMTimeOffAlMEANING : The master frame in the received baseband bus frame is not in the correct place related to the internally generated master frame pulse. Either the frame has been set in the wrong place (PI delay), or the data itself is in the wrong place.INSTRUCTIONS: FlexiBTS: 1. Check the cables between the Master System Module and RF Module/Extension System Module. 2. Replace the unit causing the fault (Master System Module, Extension System Module, RF Module, FBIA). UltraSite/EUBB: 1. Replace the unit causing the fault (WSPF, WSMF).

FAULT NAME : BB bus transmission errorFAULT ID : 2017: EFaultId_Muksu_SRx10b8bAlMEANING : A decoding error has been detected in the baseband internal link. The data packet is lost or the content is corrupted. This situation is also triggered when the links do not synchronize with each other.INSTRUCTIONS: FlexiBTS: 1. Check the cables between the Master System Module and RF Module/Extension System Module. 2. Replace the alarming unit (System Module). UltraSite/EUBB: 1. Replace the alarming unit (WSMF).

FAULT NAME : BOFU Post failedFAULT ID : 4021: EFaultId_BOFU_Post_failedAlMEANING : The unit or module has been tested during BTS power-on self test (POST) and a failure has been detected.INSTRUCTIONS: 1. Block/unblock the alarming unit/module. 2. Remove/reinsert the alarming unit/module. 3. Replace the alarming unit/module.

FAULT NAME : BTS Master Clock tuning failureFAULT ID : 1818: EFaultId_Ov_OscAl

DN99580892 75




MEANING : The OCXO adjustment area is reaching its limit value. The DAC word value of the OCXO is lower than 205 or greater than 3891 (5 of the total adjustment area). The range for the DAC word is 0 - 4095.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears. 1. Check the other alarms of the BTS and FTM and act accordingly. 2. If there are no other synchronization related alarms active, start the fast tuning with BTS Site Manager. 3. Reset the site. Run fast tuning again. 4. Check the reference signal accuracy by measuring it with a frequency counter (note: requires a good timebase for the counter). The reference signal can be found from the Sync Out interface of the Flexi System Module, the required accuracy is +/-0.015ppm. If the reference accuracy is correct, run fast tuning. 5. If that does not help, replace the system module FlexiLiteBTS: replace the Flexi Lite BTS.

FAULT NAME : BTS RNC/Flexi Direct RNC interface signalling link failureFAULT ID : 19: EFaultId_Aal2LinkAlMEANING : An AAL2 signaling link failure. The most common reason for this alarm is a frequently breaking transmission. In case of Ultra BTS, it can be caused by a broken WAM.INSTRUCTIONS: 1. Check the other transmission elements' active alarms (see the Alarms for AXC document). 2. Check the BTS and RNC transmission settings. 3. Reset the AXC. 4. Change the WAM unit. Note: The BTS and the AXC can be restarted remotely. FlexiBTS: 1. Reset the BTS. 2. Check the transmission links to the RNC. 3. Check the BTS and RNC transmission settings. 4. Replace the System Module

FAULT NAME : BTS RNC/Flexi Direct RNC interface signalling link failureFAULT ID : 17: EFaultId_CnbapLinkAlMEANING : A common NBAP link failure. It can be caused by a transmission network problem. The most common reason for this alarm is a frequent transmission breaking.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Check the other transmission elements' active alarms (see the Alarms for AXC document). 2. Check the BTS and RNC transmission settings. 3. Reset the AXC. 4. Change the WAM unit.

76 DN99580892




Note! The BTS and the AXC can be restarted remotely. FlexiBTS: 1. Reset the BTS. 2. Check the transmission links to the RNC/Flexi Direct RNC. 3. Check the BTS and RNC/Flexi Direct RNC transmission settings. 4. Replace the System Module.

FAULT NAME : BTS RNC/Flexi Direct RNC interface signalling link failureFAULT ID : 18: EFaultId_DnbapLinkAlMEANING : A dedicated Node-B Application Protocol (NBAP) link failure. It can be caused by the RNC.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Check the other transmission elements' active alarms (see the Alarms for AXC document). 2. Check the BTS and RNC transmission settings. 3. Reset the AXC. 4. Change the WAM unit. Note! The BTS and the AXC can be restarted remotely. FlexiBTS: 1. Reset the BTS. 2. Check the transmission links to the RNC. 3. Check the BTS and RNC transmission settings. 4. Replace the System Module.

FAULT NAME : BTS SW download or activation failedFAULT ID : 29: EFaultId_FileCorruptionAl 30: EFaultId_SwUpdateAlMEANING : The SW update to the BTS has failed. The error can be caused by a unit reset during the SW update, a hardware problem in the unit or cabinet, or a corrupted flash file system.INSTRUCTIONS: FlexiBTS: 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. FlexiLiteBTS: 1. Retry the SW update. 2. If other flash memory-related faults are active for the Flexi Lite BTS at the same time, replace the Flexi Lite BTS.

FAULT NAME : BTS configuration not supportedFAULT ID : 4097: EFaultId_BtsConfNotSupportedAlMEANING : FSP does not support requested BTS configuration.

DN99580892 77




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


FAULT NAME : BTS file errorFAULT ID : 136: EFaultId_TcomConfFileAlMEANING : Telecom configuration file(s)areinvalid, missing, or not accessible.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Download two different SW packages so that the faulty file is removed from the BTS. 2. Download the SW again. 3. If the fault still exists after 10 minutes, replace the alarming unit. FlexiBTS: 1. Download two different SW packages so that the faulty file is removed from the BTS. 2. Download the SW again. 3. Replace the System Module or FBIA.

78 DN99580892




FAULT NAME : BTS internal SW management problemFAULT ID : 3090: EFaultId_BtsInternalSwManagementProblemMEANING : A software update to a unit/module or subassembly has failed, or a corrupted SW file has been detected in the FLASH.INSTRUCTIONS: Note: Perform the steps below in the listed order. FlexiBTS: 1. Check other active BTS faults. If the ROM disk is corrupted, change the alarming module. 2. Reset the RF Module and/or FBIA and/or System Module, depending on the alarm source: a. Reset the RF Module by blocking/unblocking it. b. Reset the FBIA by blocking/unblocking it. c. Reset the System Module. 3. Update and activate the SW to the BTS. 4. Check the SW files. 5. Replace the alarming module/unit. UltraSite/EUBB: 1. Check other active BTS faults. If the ROM disk is corrupted, change the alarming unit. 2. Reset the alarming unit. 3. Update and activate the SW to the BTS. 4. Check the SW files. 5. Replace the alarming unit. FlexiLiteBTS: 1. Reset the and/or DSP and/or CC&T, depending on the alarm source. 2. Update and activate the SW to the BTS. 3. Check the SW files. 4. Replace the alarming Flexi Lite BTS.

FAULT NAME : BTS reference clock missingFAULT ID : 3080: EFaultId_BtsReferenceClockMissingMEANING : This BTS fault indication is generated if the reference clock monitoring function of the BTS does not receive the highest configured synchronization reference signal or if all the synchronization reference signals are missing. The BTS fault is not generated if the highest configured synchronization source is present, no matter what the lower level source statuses are. Background information: There is a fixed synchronization priority list in the FlexiBTS: -Priority 1: PPS (Pulse Per Second) signal connected to the Synchronization Input interface (Sync In) of the System Module. Normally the PPS signal is generated by the GPS receiver. -Priority 2: external 2.048MHz signal connected to the Sync

DN99580892 79




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 (for example 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.INSTRUCTIONS: Depending on the installed and commissioned synchronization source(s) listed in section "Meaning", see the commissioned synchronization option below and perform the steps in the listed order until the BTS fault indication disappears. GPS receiver (PPS source): 1. If there is a GPS receiver commissioned at the BTS site, note the following: If the GPS receiver is not locked to any satellite, it turns off the PPS signal which is normally delivered to the BTS (Sync In interface). The most common reason is that the GPS receiver does not see any satellites because of poor antenna installation (poor sky visibility). The only permanent cure for this is to change the GPS antenna location. One indication of a fairly poor sky visibility is that the BTS fault is activated/canceled every now and then. 2. There might be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver. 3. There might be a malfunction in the BTS. Perform a BTS site reset. 4. The GPS cable and/or connectors might be damaged. Check the cable and the connectors. 5. There might be a HW fault in the GPS receiver. Check the operation and change the HW, if needed. External 2.048MHz signal: 1. If there is an external 2.048MHz signal source commissioned at the BTS site, check the BTS faults of that device and act accordingly. If this does not help, check the cables. Note that since the device type is not known, detailed instructions cannot be given. For further actions refer to the appropriate user manual of the device.

80 DN99580892




2. There might be a malfunction in the BTS. Perform a BTS site reset. FTM reference (TDM, SyncE or ToP as source): 1. If there is an integrated transmission unit (FTM) commissioned at the BTS site, note the following: the FTM unit operates so that if it is not locked to a 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) might be missing, causing the FTM internal clock to drop to holdover mode. In this case, the fault in the transmission network must be corrected (FTM itself might be working fine). 2. Check the alarms of the FTM unit and act accordingly. 3. Check the synchronization settings of the FTM unit. 4. There might be a malfunction in the BTS. Perform a BTS site reset. 5. There might be an equipment failure in the FTM unit. Check the operation and replace the unit, if needed. Note: Normally the reason is not an equipment failure, but there might be connection failures in the transmission or packet 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 transmission network instability, not to a failure in the unit. If the previous steps do not help, there might be an equipment failure in the System Module. Check the operation and if resetting the BTS site does not help, replace the System Module.

FAULT NAME : Baseband Bus failureFAULT ID : 3020: EFaultId_BaseBandBusFailureMEANING : The BTS has detected an abnormal operation or a failure in the BTS internal basebandbus.The failure cannot be pointed to a specific unit/module but there are several possible fault sources.INSTRUCTIONS: Note: Perform the steps below in the listed order. FlexiBTS: 1. Check other active BTS alarms and act accordingly. 2. Check the cables between the System Module and RF Module/Extension System 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 Extension System Module by blocking/unblocking it. c. Reset the master System Module.

DN99580892 81




4. Replace the alarming RF Module/Extension System Module. 5. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation, replace the alarming master System Module. UltraSite/EUBB: 1. Check other active BTS alarms and act accordingly. 2. Reset the alarming unit. 3. Check the cables in backplane. 4. Replace the alarming unit. FlexiLiteBTS: 1. Check other active BTS faults and act accordingly. 2. Reset the BTS by blocking/unblocking it. 3. Replace the Flexi Lite BTS.


FAULT NAME : Baseband internal link test failedFAULT ID : 4053: EFaultId_SrioChainTestFailureAlMEANING : Echo test of Baseband (SRIO) link between FSP boards was not successful.INSTRUCTIONS: 1. Manually reset the BTS. 2. If alarm is still visible after BTS reset, replace the alarming FSM module.

FAULT NAME : Boot configuration inconsistency detectedFAULT ID : 4102: EFaultId_BootConfigurationInconsistencyAlMEANING : During SW update it has been detected that configurations of active and passive SW in HW unit are the same. Active and passive SW configurations are compared: - before SW download, - during SW activation, before active and passive SW switch, - during start-up.INSTRUCTIONS: Replace the faulty unit.

FAULT NAME : Cabinet door openFAULT ID : 1300: EFaultId_DoorAl0MEANING : The cabinet door is open or the cabinet door sensor is

82 DN99580892




faulty.INSTRUCTIONS: 1. Ensure that the cabinet doors are properly closed. 2. Check that the door switches function correctly and that they have been adjusted correctly. Note: this alarm can be enabled or disabled in commissioning.


FAULT NAME : Communication failureFAULT ID : 1806: EFaultId_CommunicationFailureAlMEANING : Communication with the application <x> failed. The application has not replied to the message that has been sent/resent to it.INSTRUCTIONS: FlexiBTS: 1. Make sure that the unit/module is properly connected. If the unit/module LED does not light up, the unit/module is faulty. Check the alarming unit/module. 2. Check the fault history. FlexiLiteBTS: 1. If the Flexi Lite BTS LED does not light up, the BTS is faulty. Check the Flexi Lite BTS. 2. Check the fault history.

FAULT NAME : Communication failureFAULT ID : 458: EFaultId_VcpErrorMEANING : An internal communication fault in the decoding process in the module, for example, a decode co-processor error.INSTRUCTIONS: 1. Reset the alarming unit/module. 2. Replace the alarming unit/module.

FAULT NAME : Communication failure inside WSPFAULT ID : 414: EFaultId_McbspMessagePoolExhausted 446: EFaultId_McbspSwsErrorMEANING : An internal communication failure between the DSP processors.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Block the alarming WSP. 2. The fault might be in the WTR or WPA (see Troubleshooting instructions).

DN99580892 83




Otherwise, check for other alarms. If the " autonomous reset as recovery action" alarm has occurred for the alarming WSP, replace the alarming WSP unit. FlexiBTS: 1. If only one FSP in BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module). UltraSite/EUBB: 1. If only one WSPF in the BTS generates this alarm, the WSPF is faulty. 2. If all WSPFs generate this alarm, the BTS is faulty. 3. Block/unblock the BTS. 4. If that does not help, replace the faulty module.

FAULT NAME : Configuration error: <x>FAULT ID : 3070: EFaultId_ConfigurationErrorMEANING : There is an incompatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch between the BTS configuration and the RNC/Flexi Direct RNC parameters.INSTRUCTIONS: Note: Perform the steps below in the listed order. 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 RNC/Flexi Direct RNC match the BTS HW configuration (for example frequency, power). 3. Check the RNC/Flexi Direct RNC BTS faults for the alarming local cell (LCR). 4. Recommission the BTS to ensure that all parameters are correctly configured.

FAULT NAME : Connection to ToP master missingFAULT ID : 4058: EFaultId_TopRefClkMissingAlMEANING : The reference clock monitoring has detected a loss of ToP reference clock signal received from the master clock.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears. 1. Check Ethernet interface functionality used by Timing Over Packet. Check if other faults related to the Ethernet interface exist. 2. Check Timing Over Packet configuration: the Master clock IP address is configured properly and the Master clock supports the given parameters. 3. Check the Master clock functionality. 4. Check that the IP connection between the Master clock and BTS is working.

84 DN99580892




FAULT NAME : Connection to transmission brokenFAULT ID : 1829: EFaultId_ConnToTransBrokenAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The AXC is missing, data or states are corrupted in the ATM, or there are possible hardware or transmission related failures. FlexiBTS: Data or states are corrupted in the ATM, or there are possible hardware or transmission related failures.INSTRUCTIONS: UltraSite, MetroSite, MetroSite50,Triple-mode: 1. Check the transmission connections. 2. If the transmission type is the AXC, reset the WAM. 3. If that does not help, replace the alarming unit. FlexiBTS: 1. Check the transmission connections. 2. Reset the site. 3. If that does not help, replace the alarming System Module.

FAULT NAME : DSC-bus failureFAULT ID : 208: EFaultId_DscNodeBlockedAlMEANING : There is a failure in the bus between the WAM and WSP (DSC-bus), which means that messages do not get through via that DSC-bus.INSTRUCTIONS: 1. Block/unblock the alarming unit. 2. Replace the alarming unit.

FAULT NAME : DSC-bus failureFAULT ID : 597: EFaultId_DscFaultAlMEANING : There are communication problems between the WAM and WSP. This alarm may occur if the WSP is hot removed or the WSP crashes.INSTRUCTIONS: If the failure still exists after the site reset, replace the WAM unit.

FAULT NAME : DSP accelerator initialization failureFAULT ID : 2302: EFaultId_RsaInitializationErrorMEANING : There is a signal processing (DSP) related malfunction in the BTS. This might affect the signal processor receiver functionality processed by the alarming unit/module.INSTRUCTIONS: FlexiBTS: 1. If the alarming module is the Extension System Module (FSM2), restart it. If the alarming module is the System Module (FSM1),

DN99580892 85




restart the BTS. 2. If that does not help, replace the alarming FSM or unit. UltraSite/EUBB: 1. If the alarming unit is WSPF, restart it. If all WSPFs generate this alarm, restart the BTS. 2. If that does not help, replace the alarming unit. Restart can be done by BTS block/unblock, system module block/unblock from BTS SEM and from NetAct to reset BTS.

FAULT NAME : DSP failure in radiolink creationFAULT ID : 129: EFaultId_DspHoldAlMEANING : Radio link creation has been failing repeatedly because of DSP rejection.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Block/unblock the alarming unit. 2. Replace the alarming unit. UltraSite/EUBB: 1. Block/unblock the EUBB subrack. 2. Replace the alarming unit. FlexiBTS: If the faulty FSP is in the extension module, block/unblock the extension module, otherwise block/unblock the BTS.

FAULT NAME : DSP mode change failedFAULT ID : 139: EFaultId_DspModeChangeFailAlMEANING : DSP configuration to correct mode was not successful.INSTRUCTIONS: Replace the alarming module/unit.

FAULT NAME : DSP overheatedFAULT ID : 4101: EFaultId_DspOverheatingAlMEANING : DSP overheating was detected during DSP initialization.INSTRUCTIONS: 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, replace the alarming FSP module.

FAULT NAME : Downlink data buffer synchronization failureFAULT ID : 2031: EFaultId_Transu_DlDbSynchChAlMEANING : The downlink data buffer has lost synchronization.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

86 DN99580892




FAULT NAME : Error in commissioning dataFAULT ID : 31: EFaultId_CommDataAlMEANING : The WTR initialisation parameters are faulty. The error can be caused by a missing parameter in the commissioning file: the cabling information (main, diversity), feeder loss, local cell resources, for example.INSTRUCTIONS: 1. Check that the cell parameters, RX cabling, feeder loss and MHA gain are correct in the commissioning file. 2. Update the information if needed. Reconfiguration commissioning is required for correcting the values.

FAULT NAME : FSP in resetting stateFAULT ID : 4068: EFaultId_FspResetAlMEANING : FSP is undergoing a cold reset.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears: FlexiBTS: 1. Reset the BTS. 2. Replace the faulty module/unit. FlexiLiteBTS: 1. Reset the BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : FSP overheatingFAULT ID : 4077: EFaultId_FspOverheatingAlMEANING : Temperature on the FSP board exceeds the critical threshold value.INSTRUCTIONS: 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, replace the alarming module.

FAULT NAME : FSP reset failureFAULT ID : 4100: EFaultId_FspResetFailureAlMEANING : FSMr2 FSP reset during BB reset recovery failed. FSMr3 FSP warm reset recovery failed.INSTRUCTIONS: Check the faulty FSP.

FAULT NAME : Failure in AXU initializationFAULT ID : 14: EFaultId_AxuConfigAlMEANING : The BTS has lost connection to the AXU or the AXU SW is incompatible. The AXU does not respond to requests from the BTS.INSTRUCTIONS: 1. Check the AXC configuration. 2. Restart the AXC remotely. This will also cause a BTS restart.

DN99580892 87




FAULT NAME : Failure in optical RP3 interfaceFAULT ID : 3030: EFaultId_FailureInOptical_Rp3InterfaceMEANING : The BTS has detected an abnormal operation or a failure in an optical RP3 interface between two modules. The failure cannot be pointed to a specific module but there are several possible fault sources.INSTRUCTIONS: Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the other active BTS alarms and act accordingly. 2. Check the cables between the System Module and RF Module/Extension System Module. Note that dirty optical connectors may cause the signal level to drop too low. 3. Depending on the alarm source, reset the RF Module, Extension System Module and/or System Module by blocking/unblocking it. 4. Replace the alarming module's Small Form Factor Pluggable (SFP). Check also the SFP in the other end and replace it, if needed. 5. Replace the alarming RF Module/Extension System Module. 6. If the System Module is the only alarming source or replacing the RF Module/Extension System Module does not clear the fault situation, replace the alarming System Module.

FAULT NAME : Failure in replaceable baseband unitFAULT ID : 3003: EFaultId_FbiaFailureAlMEANING : The BTS has detected an abnormal operation or a failure in the BTS replaceable baseband unit.INSTRUCTIONS: Note: Perform the steps below in the listed order until the BTS fault indication disappears. 1. Check the other active BTS faults and act accordingly. 2. Check if the plug-in type baseband unit is installed correctly. 3. Reset the alarming baseband unit. 4. Replace the alarming baseband unit.

FAULT NAME : Fatal OSE ErrorFAULT ID : 418: EFaultId_OseFatalErrMEANING : The operating system (OSE) goes into the error handler with a fatal status. The cause can be, for example, out of memory situation. If only one FSP in BTS generates this fault, there is a malfunction in one of the FSP submodules. If all FSPs generate this fault, there is a malfunction in the FSM.INSTRUCTIONS: FlexiBTS:

88 DN99580892




Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the System Module. 2. Replace the System Module. FlexiLiteBTS: Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the FlexiLiteBTS 2. Replace the FlexiLiteBTS UltraSite/EUBB: 1. If only one WSPF in BTS generates this fault, the WSPF is faulty. 2. If all WSPFs generate this fault, BTS is faulty. 3. Block/unblock BTS. 4. If that does not help, replace the faulty module.

FAULT NAME : Fault between WAM and WSP SFN (WSP)FAULT ID : 412: EFaultId_LostFrameSync 428: EFaultId_SystemFrameNumberParityMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: Synchronization between the WAM and WSP is lost. FlexiBTS: Synchronization between the FCM and FSP/FBIA is lost. UltraSite/EUBB: Synchronization between the WAMF and WSPF is lost.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. If only one WSP in the cabinet generates this alarm, the WSP is faulty. 2. If all WSPs in a subrack generate this alarm, the WAM is faulty. 3. If all WSPs generate this alarm, the WSC/WMC is faulty. Otherwise, check for other alarms. If the " autonomous reset as a recovery action" alarm has occurred for the faulty WSP, replace the faulty WSP unit. FlexiBTS: 1. If only one FSP/FBIA in the BTS generates this alarm, the FSP/FBIA is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module) or faulty FBIA. UltraSite/EUBB: 1. If only one WSPF in the BTS generates this alarm, the WSPF is faulty. 2. If all WSPFs generate this alarm, the BTS is faulty. 3. Block/unblock the BTS. 4. If that does not help, replace the faulty module.

FAULT NAME : Fault in ATM interface

DN99580892 89




FAULT ID : 309: EFaultId_AtMuxAlMEANING : The WAM ATM interface is not responding correctly.INSTRUCTIONS: 1. Block/unblock the alarming unit. This resets the BTS. 2. If that does not help, replace the alarming unit.

FAULT NAME : Fault in ATM interfaceFAULT ID : 591: EFaultId_SarChipBrokenAl 592: EFaultId_UxAsicAl 593: EFaultId_AtmHostBrokenAlMEANING : WAM ATM interface, AXC or CIF bus failure. The AXC may have been reset. WAM processor failure.INSTRUCTIONS: 1. Block/unblock the alarming unit. This will reset the BTS. 2. Swap the WAM units between subracks and check if the alarm follows the unit. Replace the alarming WAM unit. 3. Check the AXU. 4. Check the backplane connection between the WAM and AXU.

FAULT NAME : Fault in O&M and DSP SW interfaceFAULT ID : 42: EFaultId_ WSPC_PPC_SFN_PollingTimeoutAl 43: EFaultId_DSP_PollingTimeoutAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: Communication failure between the WAM and DSP. FlexiBTS: Communication failure between the FCM and FSP/FBIA. UltraSite/EUBB: Communication failure between the WSMF and WSPF. FlexiLiteBTS: Communication failure between the SCR and FSP.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Block/unblock the alarming unit. 2. Replace the alarming unit. UltraSite/EUBB: 1. Block/unblock the EUBB subrack. 2. Replace the alarming unit. FlexiBTS: 1. Block/unblock the alarming module. 2. Replace the system module/plug-in FSP. FlexiLiteBTS: 1. Block/unblock Flexi Lite BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : Faulty configuration of system modulesFAULT ID : 1858: EFaultId_FaultyFcmConfigurationAlMEANING : 1) There might be a faulty configuration with the Radio Modules connected to both the master system module and intended extension system module.

90 DN99580892




2) O&M master system module cannot be determined automatically.INSTRUCTIONS: 1) Remove Radio Modules from the intended extension system module and hot insert them to the intended master system module. 2) Connect IUB connection or LMT connection to system module that is intended to be O&M master.

FAULT NAME : Flash operation failureFAULT ID : 214: EFaultId_FlashWrAl 215: EFaultId_FlashRdAl 216: EFaultId_FlashEraseAl 217: EFaultId_FlashDrvAl 218: EFaultId_FlashDbChksumAlMEANING : A flash memory operation failure. If this fault continuously appears, the flash chip may be broken.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Check the other active faults. If the /rom-disk is corrupted, change the alarming unit. 2. Block/unblock the alarming unit. There are no recovery actions and because of that the block/unblock can be attempted once. If that does not help, replace the alarming unit. FlexiBTS, FlexiLiteBTS: 1. Check the other active faults. If the /rom-disk is corrupted, change the alarming unit/module. 2. Block/unblock the alarming unit/module. There are no recovery actions and blocking/unblocking can be attempted once. If that does not help, replace the alarming unit/module.

FAULT NAME : Frame burst receiving faultFAULT ID : 2013: EFaultId_OIC_Rp1CrcAlMEANING : The optical interface has detected a CRC error in the received synchronization burst from the clock function. This fault appears on the RX side.INSTRUCTIONS: 1. Depending on the alarm source, reset the RF Module and/or Extension System Module by blocking/unblocking it. 2. If that does not clear the fault situation, replace the RF Module/Extension System Module that causes the alarm. 3. If the System Module is the only alarming source, or replacing the RF Module/Extension System Module does not clear the fault situation, replace the System Module causing the alarm.

FAULT NAME : Frame clock deviation faultFAULT ID : 2014: EFaultId_Muksu_SFCRCompDevAl

DN99580892 91




MEANING : Synchronization to the clock control unit frame pulse has been achieved earlier but it differs from the currently received frame pulse. The internally generated frame clock might have drifted.INSTRUCTIONS: FlexiBTS: 1. Check the cables between the System Module and RF Module/Extension System Module. 2. Reset the alarming System Module. 3. Replace the alarming System Module. UltraSite/EUBB: 1. Reset the alarming WSMF. 2. Replace the alarming WSMF.

FAULT NAME : Frame number synchronization error in optical interfaceFAULT ID : 2047: EFaultId_OIC_FrSyncLostAlMEANING : The timing of the new RP1 synchronization burst deviates from the present RP1 timing maintained in the BTS.INSTRUCTIONS: 1. Reset the System Module causing the alarm. 2. If resetting of the module does not help, replace the System Module causing the alarm.

FAULT NAME : Incompatible SW version detectedFAULT ID : 23: EFaultId_IncompatibleSwVersionAl 24: EFaultId_ObsoleteSwVersionAlMEANING : A new unit with incompatible SW has probablybeeninserted in the BTS.INSTRUCTIONS: Update compatible SW to the BTS (check the SW versions to see the active SW version, and update the active SW version), unless it is automatically updated by NetAct. NOTE: If also fault 10:EFaultId_NoConnectionToUnitAl is active on the source unit then SW update should be postponed until fault 10:EFaultId_NoConnectionToUnitAl is cancelled. Related BTS - AXC interface: check the SW version of the BTS and AXC, and update compatible SW to the AXC or BTS.


FAULT NAME : Incomplete network parameters received from AXU

92 DN99580892




FAULT ID : 1851: EFaultId_CommDataNetworkParamAlMEANING : Mandatory DCN and/or ATM parameters are only partially received from the AXU to a WAM unit.INSTRUCTIONS: Check the parameters entered to the AXC and correct, if necessary.

FAULT NAME : Internal MTU configuration failureFAULT ID : 4025: EFaultId_MtuConfigurationFailureAlMEANING : Internal Maximum Transfer Unit (MTU) configuration failed on FCM or FSP/FBIA.INSTRUCTIONS: 1. Reset the alarming System Module or unit. 2. Replace the alarming System Module or unit

FAULT NAME : Internal communication errorFAULT ID : 4087: EFaultId_InternalCommunicationErrorAlMEANING : Reliable message delivery service is not able to deliver an internal message to a recipient (FSP or FSM), and sends an asynchronous notification to the message sender about the unreachable recipient.INSTRUCTIONS: 1. Make sure that the unit/module is properly connected. 2. Reset the alarming unit. 3. Replace the alarming unit.

FAULT NAME : Licence missing <licenceCode>, <licenceName>FAULT ID : 1885: EFaultId_MissingLicense AlMEANING : The BTS detected a resource requiring a license but no license exists or is available.INSTRUCTIONS: Activate the appropriate license or increase the license amount.

FAULT NAME : License missing <licenseCode>, <licenseName>FAULT ID : 1833: EFaultId_LicenceMissingAlMEANING : The BTS detected a resource needing a license. However, no license exists or is free.INSTRUCTIONS: An appropriate license should be provided to BTS.

FAULT NAME : Mains power break, running Battery BackupFAULT ID : 37: EFaultId_MainsBreakAlMEANING : There is a fault in the mains power supply. The BTS has received a Battery Backup alarm and the Intelligent Shutdown procedure has started.INSTRUCTIONS: Check the mains power supply.

FAULT NAME : Master unit has lost connection to the slave unitFAULT ID : 4019: EFaultId_KeepAliveStatusErrorAl

DN99580892 93




MEANING : Connection to the DSP submodule has been lost or the submodule reports an error situation.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears: FlexiBTS: 1. Reset the BTS. 2. Replace the faulty module/unit. FlexiLiteBTS: 1. Reset the BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : Message routing problem in receiver (RX)FAULT ID : 2058: EFaultId_MuksuMsgRoutingFailedAlMEANING : If a message does not get routed an interrupt is generated. Considered normal when Faradays are starting up and RP3 sync done.INSTRUCTIONS: If RF is the source: 1. Check antenna mapping to the local cells in the commissioning file. 2. Check the cables between the System Module and RF Module. 3. Replace the alarming module. If FSP is the source: Baseband reset should be performed.

FAULT NAME : Missing NBAP cell parameters, defaults are usedFAULT ID : 88: EFaultId_CommDataCellParamMEANING : One or more cell parameters are missing from the RNC/Flexi Direct RNC configuration data and the BTS commissioning file.INSTRUCTIONS: 1. Check the cell parameters in RNC/Flexi Direct RNC and BTS. 2. If the parameters configured to the RNC/Flexi Direct RNC are correct, lock and unlock all cells of this BTS using OMS Element Manager to trigger parameter sending from RNC to BTS again. 3. If the parameters configured to the RNC/Flexi Direct RNC are incorrect, lock the cells and configure the parameters to correct values. After that, unlock the cells. 4. If the default values for the cell parameters (such as rampdown time/step) are not appropriate in BTS, reconfigure the BTS with Commissioning Wizard.

FAULT NAME : Module dangerously overheatingFAULT ID : 4071: EFaultId_SysDangerouslyOverheatAlMEANING : Highest validated temperature value on FSP board exceeds the threshold value.INSTRUCTIONS: Note! Perform the steps below in the listed order.

94 DN99580892




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 NAME : No connection to unitFAULT ID : 10: EFaultId_NoConnectionToUnitAl 4052: EFaultId_ConnectionToUnitLostAlMEANING : Connection to a unit that belongs to the BTS configuration has been lost or FSP cannot be detected.INSTRUCTIONS: FlexiBTS: 1. Make sure that the module is properly connected. If the module LED does not light up, the module is faulty. Check the alarming module. In case of two FSM-r3, check also SRIO cable connection between the system modules. 2. Check the fault history. FlexiLiteBTS: Check the fault history. UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Check the fault history, alarming unit and subrack. 2. If the SW has been updated recently, reload the SW. 3. If the WAF or WIC is alarming, try recommissioning the site. 4. Make sure that the unit is properly connected. If the unit LED does not light up, the unit is faulty. The fault might also be in the WPS unit or backplane. 5. Check the power cables, connectors, and the I2C bus cables. Cancel alarms: Removing and inserting the WIC, WSM or primary WAM causes a site reset. If both WSCs are removed, inserting the first removed WSC back into the cabinet causes a site reset. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First, try to reset the site with the software. If that does not help, replace the alarming unit. If the WSMF unit is not present (replaced by WSMB)in BTS, alarming WSPFs are not used and should be removed from BTS. WSPFs can be removed, because without a WSMF unit BTS works as UltraSite not as EUBB.

FAULT NAME : No connection to unitFAULT ID : 75: EFaultId_WSP_memory_concistency_err1 76: EFaultId_WSP_memory_concistency_err2 77: EFaultId_WSP_memory_concistency_err3 78: EFaultId_WSP_memory_concistency_err4 79: EFaultId_WSP_memory_concistency_err5 80: EFaultId_WSP_memory_concistency_err6 81: EFaultId_WSP_memory_concistency_err7MEANING : The connection to a unit belonging to the BTS configuration

DN99580892 95




has been lost.INSTRUCTIONS: 1. Check the alarm history, alarming unit and subrack. 2.IfSW updates have been done recently, reload the SW. 3. If the WAF or WIC is alarming, try recommissioning the site. 4. Check that the unit is properly connected. If the unit led does not light up, the unit is faulty. The fault may also be in the WPS unit or backplane. 5. Check the power cables and connectors as well as the I2C bus cables. Cancel alarms: Removing and inserting the WIC, WSM or primary WAM causes a site reset. If both WSCs are removed, inserting the first removed WSC back into the cabinet causes a site reset. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First try to reset the site by the software. If that does not help, replace the alarming unit.


FAULT NAME : Not enough DSP resources per cellFAULT ID : 1861: EFaultId_NotEnoughFspResourcesPerCellAlMEANING : The number of DSP units in the BTS is too small. For every three cells, there must be at least one DSP present.INSTRUCTIONS: Increase the number of DSP units in the BTS.

FAULT NAME : Not enough WSP resources per cellFAULT ID : 60: EFaultId_NotEnoughWspResourcesPerCellAlMEANING : The number of WSP units in the BTS is too small. For every three cells, there must be at least one WSP present.INSTRUCTIONS: 1. Check the possible WSP, WSM and WAM alarms. If baseband pooling is in use, check the LCG (Local Cell Group) commissioning. Check that all subracks are in working state. 2. Increase the number of WSP units in the BTS.

FAULT NAME : Optical Interface Frame clock faultyFAULT ID : 2003: EFaultId_OIC_CleanerLockAlMEANING : The VCXO does not get correct control voltage from the PLL

96 DN99580892




filter of the clock cleaner. This may happen because of an unsuccessful clock recovery in the optical interface because of a missing or degraded input signal.INSTRUCTIONS: 1. Block/unblock the System Module. 2. Replace the System Module.

FAULT NAME : Optical interface buffer alarmFAULT ID : 2051: EFaultId_Muksu_BufferAlMEANING : RP3 or Ethernet buffering is not working and the buffer becomes full. The optical device malfunctions. The fault may be generated because of synchronization problems or incorrect initialization.INSTRUCTIONS: 1. Depending on the interface, reset the connected module/unit behind the interface that causes the alarm by blocking/unblocking it. 2. If that does not clear the fault situation, replace the connected module/unit behind the interface causing the alarm. FlexiBTS: 3. If the System Module is the only alarm source, or replacing the RF Module/Extension System Module does not clear the fault situation, replace the System Module causing the alarm. UltraSite/EUBB: 3. If WSMF is the only alarm source, or replacing the connected module/unit does not clear the fault situation, replace the WSMF that causes the alarm.

FAULT NAME : Optical interface data/control/Ethernet buffer fullFAULT ID : 2006: EFaultId_OIC_DBRxFullAl 2007: EFaultId_OIC_DBTxFullAl 2008: EFaultId_OIC_CBRxFullAl 2009: EFaultId_OIC_CBTxFullAl 2010: EFaultId_OIC_EBFullAlMEANING : The RP3 or Ethernet buffering is not working and the buffer becomes full. The optical device is malfunctioning. The fault might be generated because of synchronization problems or incorrect initialization.INSTRUCTIONS: Swap the alarming and working links. Then check where the alarm is reported. If the alarming link remains the same, replace the System Module. If the alarming link changes, replace the RF Module behind that link.

FAULT NAME : Optical interface faultyFAULT ID : 2000: EFaultId_OIC_TxAl 2001: EFaultId_OIC_PresAlMEANING : The Small Form Factor Pluggable (SFP) malfunction has occured or the SFP module is not physically present (no

DN99580892 97




electrical connection exists). The SFP is a part of the fibre cable package.INSTRUCTIONS: 1. Check that the SFP is properly connected. 2. Replace the SFP module.

FAULT NAME : Out Of Frame Data ErrorFAULT ID : 420: EFaultId_OutOfDataMEANING : An out of frame data error interrupt received from the SWS ASIC.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. The WSP is not necessarily faulty. Check also the state of the other units. 2. Block/unblock the WSP. 3. If that does not help, replace the faulty unit. FlexiBTS: 1. The FSPA is not necessarily faulty. Check also the state of the other units. 2. Block/unblock the FSM. 3. If that does not help, replace the faulty module (System Module).

FAULT NAME : Oven oscillator heating failureFAULT ID : 901: EFaultId_OcxoHeatingAl 912: EFaultId_DualWscOvAMssMEANING : The heating of oven oscillator fails and the unit is broken. The ambient temperature can also be too low or change too fast.INSTRUCTIONS: 1. Check the active fan alarms. 2. Replace the clock unit.

FAULT NAME : Oven oscillator missing pulseFAULT ID : 1820: EFaultId_OcxoPulseMissingAlMEANING : The output signal of the OXCO has some problems and one or more clock pulses are missed.INSTRUCTIONS: 1. Block/unblock the System Module. 2. Replace the System Module.

FAULT NAME : Overload collision in transmitterFAULT ID : 2061: EFaultId_MuksuOverloadCollisionAlMEANING : Transmitter detected more data coming from a summing than the current link rate can support.INSTRUCTIONS: 1. Check antenna mapping to the local cells in the commissioning file. 2. Replace the alarming module.

FAULT NAME : PLL status not locked

98 DN99580892




FAULT ID : 4010: EFaultId_PLLStatusNotLockedAlMEANING : BTS monitors the FSP/FBIA/WSPF/WSMF PLL (Phase-Locked Loop) lock status and PLL locking fails.INSTRUCTIONS: FlexiBTS: 1. Block/unblock the FSM/FBIA. 2. If that does not help, replace the FSM/FBIA. UltraSite/EUBB: 1. Block/unblock the WSMF. 2. If that does not help, replace the WSMF. 3. Block/unblock the WSPF. 4. If that does not help, replace the WSPF.

FAULT NAME : POST test failedFAULT ID : 69: EFaultId_Post_test_failedAlMEANING : A failure in the unit/module has been detected during the BTS power-on self test (POST).INSTRUCTIONS: 1. Block/unblock the alarming unit/module. 2. Remove/re-insert the alarming unit/module. 3. Replace the alarming unit/module. FlexiLiteBTS: 1. Replace the FlexiLiteBTS.

FAULT NAME : PPS reference missingFAULT ID : 1898: EFaultId_PpsRefMissAlMEANING : The reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver.INSTRUCTIONS: FlexiBTS: 1. Check the GPS receiver installation. 2. Check the GPS receiver status. 3. Check connection between the GPS receiver and FSM. FlexiLteBTS: 1. Check the GPS receiver installation. 2. Check the GPS receiver status. 3. Checkconnectionbetween the GPS receiver and Flexi Lite BTS.

FAULT NAME : Parallel Interference Cancellation stream failure detectedFAULT ID : 2310: EFaultId_PicStreamFailureMEANING : RACH RAKE sends this fault when Parallel Interference Cancellation stream failure is detected.INSTRUCTIONS: FlexiBTS: Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the System Module. 2. Replace the System Module. UltraSite/EUBB:

DN99580892 99




1. If only one WSPF in the BTS generates this fault, the WSPF is faulty. 2. If all WSPFs generate this fault, the BTS is faulty. 3. Block/unblock the BTS. 4. If that does not help, replace the faulty module.

FAULT NAME : Parallel RP3-01 link length mismatchFAULT ID : 4072: EFaultId_ParallelLinkDifferenceTooLargeAlMEANING : The parallel RP3-01 links towards one radio module have too large mutual length difference (more than 60 meters).INSTRUCTIONS: Replace parallel RP3-01 fiber links towards one radio module so that the maximum mutual length difference between fibers is less than 60 meters.

FAULT NAME : Performance not optimal due to Rel2 ESM HSPA capability not utilizedFAULT ID : 150: EFaultId_PerformanceNotOptimalRel2HspaCapabilityNotUsedAlMEANING : After Extension System Module is lost and 10 minutes timer expires, Telecom tries to re-allocate cells to Master System Module without HSPA capability. When the Extension System Module is back and if any cells have successfully been re-allocated to Master System Module, the performance is not optimal, because its HSPA capability is not utilized. Used in FSMr2+FSMr2, FSMr3+FSMr2 configurations.INSTRUCTIONS: In order to restore full performance reset BTS manually or lock-unlock all cells re-allocated from Extension System Module to Master System Module.

FAULT NAME : Power unit input voltage faultFAULT ID : 1302: EfaultId_WpsPwrInVoltageMEANING : The input voltage of the BTS has decreased.INSTRUCTIONS: 1. Check the other MAINS related active alarms. 2. Check the power supply voltage. If it is OK, replace the power cable. 3. Check the power unit.

FAULT NAME : Power unit output voltage faultFAULT ID : 1301: EFaultId_WpsPwrOutVoltageMEANING : The output voltage is too low or too high. Usually the reason for the fault is the unit itself but in some cases the reason can be the unit that the WPS feeds. If a short circuit occurs in the fed unit, it may affect the WPS and the "Output Voltage Fault" alarm is generated.INSTRUCTIONS: 1. Check the other active alarms. 2. Check the units that are supplied by the alarming WPS.

100 DN99580892




3. Check the backplane connectors and cables. 4. Replace the alarming WPS unit.


FAULT NAME : RP3-01 Link ConflictFAULT ID : 4039: EFaultId_Rp301LinkConflictAlMEANING : FSM notices a shared radio module is connected to different OptIF connectors on peer system modules.INSTRUCTIONS: RP3-01 cabling from peer system modules to shared radio module is to be corrected.

FAULT NAME : Radio Master ConflictFAULT ID : 4038: EFaultId_RadioMasterConflictAlMEANING : FSM should be the radio master for RFSW, but notices that RFSW already has another radio master defined.INSTRUCTIONS: Commissioning error. Only one System Module shall be set as master for particular radio resource.

FAULT NAME : Resource block not availableFAULT ID : 145: EFaultId_ResourceBlockNotAvailableAlMEANING : If there are no DSP resources for PIC configuration, Telecom rejects the PIC configuration and raises an alarm to indicate "Resource block not available".INSTRUCTIONS: 1) When the fault is detected, a new PIC configuration is to be provided by the BTS Site Manager. 2) If this is a repetitive problem, the FSP card has to be removed and re-inserted.

DN99580892 101




FAULT NAME : Resource block occupied by high priority servicesFAULT ID : 146: EFaultId_ResourceBlockOccupiedAlMEANING : If PIC configuration cannot be allocated to a DSP resource because the DSP is in use with some high-priority users, Telecom raises this fault. Telecom then tries to move the high-priority users to a different resource block and tries again to allocate PIC configuration to the DSP a number of times for 3 minutes. In case of failure, Telecom rejects the received configuration to indicate "Resource block occupied by high priority users".INSTRUCTIONS: 1) The alarm indicates that the PIC configuration has failed. New PIC pool configuration is to be provided by the BTS Site Manager. 2) If this is a repetitive problem, the FSP card has to be removed and re-inserted.

FAULT NAME : SFN Signal errorFAULT ID : 2036: EFaultId_Transu_SfnSignalAlMEANING : A system frame number reception fault, an illegal SFN value in uplink.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : SFN synchronization failureFAULT ID : 41: EFaultId_WSPC_PPC_SFN_PollingSynchAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The WSP is not synchronized with the WAM. FlexiBTS: The FSP/FBIA is not synchronized with the FCM. FlexiLiteBTS: The FSP is not synchronizaed with the SCR UltraSite/EUBB: The WSPF is not synchronized with WSMF.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Block/unblock the alarming unit. 2. Replace the alarming unit. UltraSite/EUBB: 1. Block/unblock the EUBB subrack. 2. Replace the alarming unit. FlexiBTS: 1. Block/unblock the alarming module. 2. Replace the system module/plug-in FSP. FlexiLiteBTS: 1. Reset the BTS 2. Replace the FlexiLiteBTS unit

102 DN99580892




FAULT NAME : SFN synchronization failureFAULT ID : 44: EFaultId_ATM_SFN_PollingSynchAlMEANING : There is a WAM internal synchronization failure.INSTRUCTIONS: 1. Check and correct the ATM configuration. 2. Replace the WAM.

FAULT NAME : SFN synchronization failureFAULT ID : 46: EFaultId_WAM_SFN_PollingSynchAlMEANING : The slave WAM is not synchronised with the master WAM.INSTRUCTIONS: 1. Block/unblock the alarming unit. 2. If that does not help, replace the alarming unit.

FAULT NAME : SRAM operation failureFAULT ID : 1875: EFaultId_SRAMRdAl 1876: EFaultId_SRAMWrAlMEANING : SRAM memory operation failure. If this alarm appears continuously, the SRAM chip may be broken.INSTRUCTIONS: 1. Check the other active alarms. 2. Replace the alarming module.

FAULT NAME : SRIO chain configuration was rejectedFAULT ID : 4015: EFaultId_Srio_ConfFailedAlMEANING : The platform SW rejected the baseband bus related SRIO configuration for Faraday core.INSTRUCTIONS: Replace the alarming unit/module.

FAULT NAME : SRIO link DegradationFAULT ID : 2326: EFaultId_SrioLinkDegradationMEANING : SRIO error rate too highINSTRUCTIONS: FlexiBTS: 1. Block/unblock the FSM. 2. If that does not help, replace the faulty module (System Module).

FAULT NAME : SW fallbackFAULT ID : 4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl 4083: EFaultId_FallbackDueToConfigurationDataMigrationFailureAl 4085: EfaultId_FallbackDueToTransportRequestAlMEANING : 4082: Source unit has reached the maximum number of reset attempts, that is the source unit cannot successfully

DN99580892 103




finish start-up after the SW update. 4083: Source unit requests SW fallback due to a critical problem that occurred in start-up after the SW update, that is configuration data migration failed. 4085: Transport SW on the source unit indicates a need for software fallback.INSTRUCTIONS: If the 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 NAME : Self test failedFAULT ID : 1882: EFaultId_SelfTestFailedAlMEANING : The self test of the unit/module has failed.INSTRUCTIONS: 1. Block/unblock the alarming unit/module. 2. If that does not help, replace the alarming unit/module.

FAULT NAME : Summing not enabled for message typeFAULT ID : 2059: EFaultId_MuksuSummingNotEnabledAlMEANING : Summing checks headers of the messages to be summed. If the header is not any of the allowed types, no summing is performed and an empty message is sent instead.INSTRUCTIONS: If FCM is the source: Reset FCM unit.

FAULT NAME : Summing service release from reset failedFAULT ID : 1891: EFaultId_MuksuReleaseFromResetFailedAlMEANING : Summing service release from reset failed.INSTRUCTIONS: 1. Reset the System Module. 2. If a reset does not resolve the fault situation, replace the System Module.

FAULT NAME : Synchronization error in RP1 receiverFAULT ID : 2048: EFaultId_Casa2Rp1CrcAl 2049: EFaultId_Casa2Rp1FramePhaseAlMEANING : The frame alignment is lost or the frame burst has a CRC error when the System Module is working in extension mode.INSTRUCTIONS: 1. Check the other active synchronization alarms and act accordingly. 2. Reset the Extension System Module.

FAULT NAME : Synchronization failureFAULT ID : 2030: EFaultId_Transu_CompDevBbRfAlMEANING : The frame burst phase has moved compared to the internal

104 DN99580892




counter. The FSM has already found the frame synchronization but the FSM frame clock does not match the FSM internal frame clock.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).


FAULT NAME : System Module failureFAULT ID : 3000: EFaultId_SystemModuleFailureMEANING : The Flexi BTS has detected an abnormal operation or a failure in the internal functionality of the System Module. The Flexi Lite BTS has detected an abnormal operation or a failure in the internal functionality of the BTS.INSTRUCTIONS: Note: Perform the steps below in the listed order. Flexi BTS: 1. Check cables between the modules and replace them if needed. 2. Reset the System Module. 3. Replace the System Module. Flexi Lite BTS: 1. Reset the BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : System clock for extension system module not availableFAULT ID : 1852: EFaultId_SystemClockExtensionNotAvailableAlMEANING : The Extension System Module does not receive the system clock.INSTRUCTIONS: 1. Connect to the Extension System Module with BTS Site Manager to check if there are optical interface alarms. 2. If there are, follow the instructions for those alarms. 3. If there are no optical interface alarms, replace the module.

FAULT NAME : System frame clock signal missing

DN99580892 105




FAULT ID : 219: EFaultId_SfclkMssAlMEANING : The WAM does not receive a system frame clock (SFCLK) from the WCI/WMC, because of the transceiver circuit in the WCI, the receiver circuit in the WAM, or the system frame clock bus is faulty.INSTRUCTIONS: 1. Block/unblock the alarming unit (WAM). This ensures that nothing unexpected has happened in the unit start-up phase. 2. If that does not help, replace the alarming unit (WAM).

FAULT NAME : TRANSU synchronization errorFAULT ID : 2045: EFaultId_TransuSyncAlMEANING : The RP3 TX/RX state machine or the T-bus receiver has changed its state. The synchronization is lost or the T-bus receiver has not synchronized.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : TargetId verification failureFAULT ID : 4056: EFaultId_TargetIdVerificationFailureAlMEANING : NetAct Licence Manager did not respond to the verification request. TargetId verification was not possible.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the NetAct Licence Manager. 2. Reset the BTS. 3. Check the BTS license situation: the correct licenses have been purchased and installed.

FAULT NAME : Tbus receiver parity faultFAULT ID : 2027: EFaultId_Transu_TbusParityAlMEANING : Data or synchronization failure in the System Module, two antenna carriers are affected.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : Telecom configuration failureFAULT ID : 109: EFaultId_TcomSlaveRegAl 110: EFaultId_UnitRnwConfigAl

106 DN99580892




111: EFaultId_TcomSlaveConfigAl 119: EFaultId_WspAllocationAlMEANING : Telecomslaveconfiguration or registration failure. Unit RNW configuration failure. Telecom RNW reconfiguration failure. FlexiBTS: - FSP unit to FCM allocation failure - Faraday unit to FSP allocation failure Note that depending on the fault source, unit status might relate either to the state of particular carrier resource on FR module or FSP board on FCM, and may not be in line with the state of source HW unit. Or UltraSite, MetroSite, MetroSite 50, Triple-mode: WSP unit to WAM allocation failure. UltraSite/EUBB: Faraday unit to WSPF allocation failure.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: Block/unblock the alarming unit. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again. UltraSite/EUBB: If the alarming unit is WSPF, block/unblock the EUBB subrack. FlexiBTS: If there was an internal failure, in the case of an FR, the module needs to be blocked/unblocked to get it initialized/configured again. FlexiBTS Rel2: If the alarming unit is FSPC, block/unblock the alarming module.

FAULT NAME : Ten consecutive Nacks received from a DSP at DCH setupFAULT ID : 149: EFaultId_DspNacksReceivedAlMEANING : One particular DSP Nacks DCH setup 10 times with cause "NotEnoughResources=10" or "AlreadyActivated_Allocated=22" within a 20 minute period.INSTRUCTIONS: FlexiBTS: If the faulty FSP is in the extension module, block/unblock the extension module, otherwise block/unblock the BTS. FlexiLiteBTS: 1. Block/unblock Flexi Lite BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : Timeout, commissioned resource not readyFAULT ID : 35: EFaultId_UnitIsNotInUseMEANING : The faulty unit has not been configured or initialised.INSTRUCTIONS: Recommission the site.

DN99580892 107




FAULT NAME : Transmission clock missingFAULT ID : 1003: EFaultId_TransmissionClk0Mss 1004: EFaultId_TransmissionClk1MssMEANING : The clock of the BTS, the WSC/WMC unit, uses the Iub or the signal received from an external clock as a clock reference. The signal is routed through the AXC and WCI to the WSC. This alarm is generated if the WCI does not receive the clock reference signal.INSTRUCTIONS: 1. Check the other transmission-related alarms, for example link breaks. 2. Check the AXC settings. 3. Check the transmission cablings. 4. Replace the WCI unit.

FAULT NAME : Transmission clock missingFAULT ID : 1816: EFaultId_Trans_Clk_MsgAlMEANING : The reference clock monitoring has detected a loss of signal in the reference received from the FT.INSTRUCTIONS: 1. Check the Iub connection. 2. Check the FT status. 3. Check the connection between the FT and FSM.

FAULT NAME : Transmission parameters missingFAULT ID : 1825: EFaultId_PublicIPmissingAl 1826: EFaultId_TrParamMissingAlMEANING : A request to retrieve the public IP address information of the FCM/FCT from the FT fails, or transmission parameters have not been commissioned or properly set.INSTRUCTIONS: Commission the transmission with the correct parameters, either with a commissioning file or manually.

FAULT NAME : Transmission rule collision in MuksuFAULT ID : 2060: EFaultId_MuksuTransmissionRuleCollisionAIMEANING : Transmitter detected an RP3 message from a summing coincident with a transmission rule.INSTRUCTIONS: 1. Check antenna mapping to the local cells in the commissioning file. 2. Replace the alarming module.

FAULT NAME : Unit SW download failedFAULT ID : 1824: EFaultId_AtmPostFailAlMEANING : The software update to the unit or subunit has failed.INSTRUCTIONS: 1. Reset the BTS. 2. If Step 1 does not help, replace the alarming unit. OR 1. Download the BTS SW again.

108 DN99580892




FAULT NAME : Unit SW download failedFAULT ID : 6: EFaultId_SwDownloadAlMEANING : Software update to a unit/subunit or module has failed. UltraSite, MetroSite: The fault can also be caused by disconnected CIF bus cables.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Download the BTS SW again. 2. If the alarming unit is WSP, block/unblock the WSP. 3. If the alarming unit is WAM or WPA, reset the BTS. 4. If that does not help, replace the alarming unit. FlexiBTS: 1. Download the BTS SW again. 2. FCM: Reset the BTS. 3. If Step 2 does not help, replace the alarming module. FlexiLiteBTS: 1. Download the BTS SW again. 2. Reset the BTS. 3. If Step 2 does not help, replace the Flexi Lite BTS.

FAULT NAME : Unit blockedFAULT ID : 48: EFaultId_UnitBlockedAlMEANING : A unit is blocked with BTS Site Manager. The purpose of the fault is to avoid alarms that might be raised during the unit maintenance task.INSTRUCTIONS: To cancel the alarm, unblock the unit/module.

FAULT NAME : Unit initialization failureFAULT ID : 12: EFaultId_TcomConfigAl 13: EFaultId_AtmConfigAl 15: EFaultId_InitializationAl 4040: EFaultId_InitFaultManAlMEANING : A unit/module or an IP address initialization has failed.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Block/unblock the alarming unit. 2. Check if the non-commissioned WAM is the Master WAM. If so, this causes the fault. Check the fault history to find out why the WAM switch-over occurred. 3. If the WAM is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 4. If step 3 does not help, replace the alarming unit. FlexiBTS: 1. Block/unblock the alarming module. If that does not help, replace the alarming module. 2. If the FCM/FCT is the fault source, check the RNC IP

DN99580892 109




address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the alarming module. FlexiLiteBTS: 1. Block/unblock the alarming module. If that does not help, replace the alarming module. 2. If the SCR is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the alarming module.

FAULT NAME : Unit initialization failureFAULT ID : 85: EFaultId_WSP_no_resp_from_PPCMEANING : The connection to the WSP fails because of a WSP internal failure.INSTRUCTIONS: 1. Block/unblock the alarming unit. 2. Replace the alarming unit.

FAULT NAME : Unit not supported by current BTS SW versionFAULT ID : 95: EFaultId_NotSupportedUnitMEANING : An unsupported unit has been detected in the BTS. Typically, this happens when a new unit version is installed and there is older BTS SW in use that does not support the new unit version.INSTRUCTIONS: FlexiBTS, UltraSite/EUBB:: 1. Upgrade the system module SW. 2. Replace the unit. FlexiLiteBTS: 1. Upgrade the Flexi Lite BTS software. 2. Replace the Flexi Lite BTS.

FAULTNAME : Unit synchronization failedFAULT ID : 16: EFaultId_SynchronizationAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The WAM/WSPC synchronization has failed. FlexiBTS: FCM/FCT/FSP synchronization has failed.INSTRUCTIONS: 1. Block/unblock the alarming unit. 2. Replace the alarming unit. FlexiLiteBTS: 1. Block/unblock the Flexi Lite BTS. 2. Replace the Flexi Lite BTS.

FAULT NAME : Unknown Cabinet TypeFAULT ID : 1804: EFaultId_UnknownCabinetTypeAl

110 DN99580892




MEANING : The cabinet cannot be identified by its product code (or object ID). The problem is probably in the WID id.INSTRUCTIONS: Check the WID connection and replace the WID, if necessary.



FAULT NAME : Uplink data buffer synchronization failureFAULT ID : 2033: EFaultId_Transu_UlDbSyncChAlMEANING : The uplink data buffer loses synchronization.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Block/unblock the FSM. 4. If that does not help, replace the faulty module (System Module).

FAULT NAME : WAM SFN polling timeoutFAULT ID : 47: EFaultId_WAM_SFN_PollingTimeoutAlMEANING : The slave WAM is not synchronised with the master WAM.INSTRUCTIONS: 1. Block/unblock the alarming unit. Note: After the WAM block/unblock, the BTS will be restarted. 2. If that does not help, replace the alarming unit.

FAULT NAME : WAM internal errorFAULT ID : 300: EFaultId_AtmRmCommAlMEANING : The C-Plane Telecom SW does not communicate with the C-Plane TUPC SW because of a fault.INSTRUCTIONS: Replace the faulty unit

FAULT NAME : WMC oven oscillator faultFAULT ID : 8: EFaultId_DacWordLimitAl

DN99580892 111




MEANING : The oven oscillator adjusting area is reaching its limit value. The alarm is activated if the WMC tunes the oven oscillator so that the DAC word (parameter to control the oven oscillator output frequency) value becomes lower than 205 or greater than 3891 (5 of the total adjustment area). The range for the DAC word is 0 - 4095. The cause of the alarm can be: - The Iub reference frequency has been incorrect for a long time (up to several days) due to a fault in the transmission network synchronisation (which in turn is caused by an equipment fault or a setting error). Before activating this alarm, the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' may have been active. - If the BTS integrated transport part receives the synchronisation information via the 2.048 MHz synchronisation input (external clock source), the alarm situation may be caused by a fault in that signal. In that case the alarm behaviour notifications listed with the Iub signal (see above) are also valid in this case. - The fast tuning action of the BTS master clock may have been executed without checking if the reference signal is correct or not. If the reference signal is incorrect during the fast tuning execution, it may result in adjusting the BTS master clock frequency far from the nominal value, which causes serious problems in the network performance. - There is an equipment fault in the BTS. - Due to the oven oscillator (OCXO) aging inside the WSC unit, the unit may be approaching the end of its lifetime. In such case, after the alarm activation, the DAC value is quite stable, whereas in the other fault cases it may be very unstable or at the edge of the adjustment area (0 or 4095). Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WMC oven oscillator fault' becomes active, it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel.INSTRUCTIONS: 1. In case of a fault in the transmission network synchronisation, the network synchronisation must be corrected. The long-term accuracy of the Iub signal must be 0.015 ppm or better. 2. In case of a BTS equipment fault, the location may be: a. Transport part - First check the alarms of the AXC node with the AXC Manager and act accordingly. - If there are no alarms, check the AXC synchronisation settings. b. WMC unit - If both the Iub reference signal accuracy and the AXC node are in order but the WMC unit is still alarming, run

112 DN99580892




the fast tuning procedure with the BTS Site Manager. - If there is no cure in a few minutes, reset the site. - If that does not help, replace the WMC unit. 3. After the fault situation has been cleared, the BTS master clock may also require tuning, because the BTS master clock adjustment is quite slow. The tuning may be done: - Manually, by changing the DAC word (during a site visit). - Or with fast tuning, by which the BTS master clock is tuned in a few minutes automatically near the Iub reference (normal tuning takes care of the fine tuning). Note, however, that the fast tuning should only be used 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 a mobile network, the synchronisation goes from MSC => RNC => BTS. But in reality that chain might be broken somewhere and, for example, when using leased lines, the BTS may take the reference synchronisation from the transmission network of another operator. This does not harm the system if also the synchronisation of the leased line service provider is accurate/stable enough. The BTS uses the incoming synchronisation signal as a reference for the Air interface, the accuracy requirement of which is set by 3GPP.

FAULT NAME : WSC oven oscillator faultFAULT ID : 907: EFaultId_DualWscDacWordAlarmMEANING : The oven oscillator adjusting area is reaching its limit value. The alarm is activated if the WSC tunes the oven oscillator so that the DAC word (parameter to control the oven oscillator output frequency) value becomes lower than 205 or greater than 3891 (5 of the total adjustment area). The range for the DAC word is 0 - 4095. The cause of the alarm can be: - The Iub reference frequency has been incorrect for a long time (up to several days) due to a fault in the transmission network synchronization (which in turn is caused by an equipment fault or a setting error). Before activating this alarm, the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' may have been active. - If the BTS integrated transport part receives the synchronization information via the 2.048 MHz synchronization input (external clock source), the alarm

DN99580892 113




situation may be caused by a fault in that signal. In that case, the alarm behavior notifications listed with the Iub signal (see above) are also valid in this case. - The fast tuning action of the BTS master clock may have been executed without checking if the reference signal is correct or not. If the reference signal is incorrect during the fast tuning execution, it may result in adjusting the BTS master clock frequency far from the nominal value, which causes serious problems in the network performance. - There is an equipment fault in the BTS. - Due to the oven oscillator (OCXO) aging inside the WSC unit, the unit may be approaching the end of its lifetime. In such case, after the alarm activation, the DAC value is quite stable, whereas in the other fault cases it may be very unstable or at the edge of the adjustment area (0 or 4095). Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WSC oven oscillator fault' becomes active, it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel.INSTRUCTIONS: 1. In the case of a fault in the transmission network synchronization, you need to correct the network synchronization. The long-term accuracy of the Iub signal must be +/- 0.015 ppm or better. 2. In case of BTS equipment fault, the location may be: 2.1 Transport part - First check the alarms of the AXC node with AXC Manager and act accordingly. - If there are no alarms, check the AXC synchronization settings. 2.2 WSC unit - If both the Iub reference signal accuracy and the AXC node are in order but the WSC unit is still alarming, run the fast tuning procedure with BTS Site Manager. - If that does not solve the problem in a few minutes, reset the site. - If that does not help, replace the WSC unit. Note: In case the BTS is equipped with two WSCs, the redundant unit takes over the operation of the faulty unit. But if the fault situation is caused by an incorrect reference signal, both the WSC units may start alarming sooner or later. 3. After the fault situation has been cleared, the BTS master clock may also require tuning, 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, where the BTS master clock is tuned automatically in a few minutes near the Iub reference (normal tuning takes care of the fine tuning)

114 DN99580892




Note, however, that the fast tuning should only be used 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 a mobile network, the synchronization goes from MSC > RNC > BTS. 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 also the synchronization of the leased line service provider is accurate/stable 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 NAME : WSC phase difference jammed to zero readingFAULT ID : 22: EFaultId_WscPhaseDiffJammedAlMEANING : The WSC phase measurement is jammed and the tuning operation is degraded. The problem can be caused by a WSC fault, or a too fast frequency change on the Iub.INSTRUCTIONS: 1.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, the synchronization of the transmission network must be corrected. The limits for the jitter/wander are defined in the ITU-T G.823. No actions on the BTS are needed. 2. Reset the site and wait about 10 minutes. 3. Try a power-on reset. If the alarm reappears, replace the unit. If the alarm reappears during the next few weeks or the clock seems unstable, replace the unit. Background information: The principle in the mobile network is that the synchronization goes from MSC => RNC => BTS. 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 also the synchronization of the leased line service provider is accurate/stable 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 NAME : WSC/WMC transmission clock missingFAULT ID : 900: EFaultId_TransmissionClkMss 909: EFaultId_DualWscTrclkMss

DN99580892 115




MEANING : The clock of the BTS, the WSC/WMC unit, uses the Iub or the signal received from an external clock as a clock reference. The signal is routed through the AXC and WCI to the WSC. This alarm is generated if the WCI does not receive the clock reference signal.INSTRUCTIONS: 1. Check the other transmission-related alarms, for example link breaks. 2. Check the AXC settings. 3. Check the transmission cablings. 4. Replace the WCI unit.

FAULT NAME : WSM SR-Bus errorFAULT ID : 1205: EFaultId_Srl0_0ParityErr2 1207: EFaultId_Srl0_0SyncErr2 1209: EFaultId_Srl0_1ParityErr2 1211: EFaultId_Srl0_1SyncErr2 1213: EFaultId_Srl1_0ParityErr2 1215: EFaultId_Srl1_0SyncErr2 1217: EFaultId_Srl1_1ParityErr2 1219: EFaultId_Srl1_1SyncErr2 1221: EFaultId_SRr0_0ParityErr2 1223: EFaultId_SRr0_0SyncErr2 1225: EFaultId_SRr0_1ParityErr2 1227: EFaultId_SRr0_1SyncErr2 1229: EFaultId_Srr1_0ParityErr2 1231: EFaultId_Srr1_0SyncErr2 1233: EFaultId_Srr1_1ParityErr2 1235: EFaultId_Srr1_1SyncErr2MEANING : UltraSite, UltraSite/EUBB: The RX signal is transported from the WTR unit to all WSP units via the WSMs. The WSM units in different subracks are connected to each other via the SR buses. This alarm is generated, when the WSM unit detects errors in the incoming SR bus from the adjacent WSM unit. The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm. Triple-mode: The RX signal is transported from the WTR30 and WRT20 units (connected to the SR bus) to the WSP units via the SR bus. This alarm is generated, when the WSM detects errors in the incoming SR bus from the WTR unit. The reason for the failure is the WSM or WTR unit, or the cable between the WSM front panelandthe backplane.INSTRUCTIONS: 1. Run the WCDMA BTS loop test. 2. Check the WSM cables. 3. Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions).

116 DN99580892




FAULT NAME : WSM ST-Bus errorFAULT ID : 1173: EFaultId_St_l0ParityErr2 1175: EFaultId_St_l0SyncErr2 1177: EFaultId_St_l1ParityErr2 1179: EFaultId_St_l1SyncErr2 1181: EFaultId_St_r0ParityErr2 1183: EFaultId_St_r0SyncErr2 1185: EFaultId_St_r1ParityErr2 1187: EFaultId_St_r1SyncErr2MEANING : The TX signal is transported from the WSP unit to all WTR units via the WSMs. The WSM units in different subracks are connected to each other via the ST buses. This alarm is generated when the WSM unit detects errors in the incoming ST bus from the adjacent WSM unit. The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm.INSTRUCTIONS: 1. Run the WCDMA BTS loop test. 2. Check the WSM cables. 3. Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions).

FAULT NAME : WSM T-Bus errorFAULT ID : 1149: EFaultId_Wspc0ParityErr2 1151: EFaultId_Wspc0SyncErr2 1153: EFaultId_Wspc1ParityErr2 1155: EFaultId_Wspc1SyncErr2 1157: EFaultId_Wspc2ParityErr2 1159: EFaultId_Wspc2SyncErr2 1161: EFaultId_Wspc3ParityErr2 1163: EFaultId_Wspc3SyncErr2 1165: EFaultId_Wspc4ParityErr2 1167: EFaultId_Wspc4SyncErr2 1169: EFaultId_Wspc5ParityErr2 1171: EFaultId_Wspc5SyncErr2MEANING : The signal is transported from the WSP unit to the WTR unit through the WSM. This alarm is generated when the WSM unit detects errors in the incoming T bus from the WSP unit. The reason for the failure is probably the WSP or WSM unit. The unit might have been installed incorrectly or the backplane cabling is faulty.INSTRUCTIONS: 1. Run the WCDMA BTS loop test. 2. Check the WSM cables. 3. Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions).

DN99580892 117




FAULT NAME : WSM does not receive frame clockFAULT ID : 1253: EFaultId_Dsax_SfclkStatusNegErr 1254: EFaultId_Dsax_SfclkStatusPosErr 1256: EFaultId_Umax_SfclkStatusErrMEANING : The WSM does not receive the System Frame Clock (SFCLK) correctly from the WCI unit. This fault may appear if the only clock unit (WSC) is removed.INSTRUCTIONS: 1. Block/unblock the alarming WSM. Note! This will cause a BTS reset. 2. Replace the WCI unit and check whether the alarm is cleared. 3. Check the backplane cables and connectors.


FAULT NAME : WSMF WAM Interconnection FailureFAULT ID : 4049: EFaultId_WsmfWamInterconnectionFailureAlMEANING : Connection failure between WAMA and WSMFINSTRUCTIONS: Check that cables are connected between WAMA-WSMF and WSMF-AXCF.

FAULT NAME : WSP PCI-bus failureFAULT ID : 225: EFaultId_PCIInvalidDeviceAl 226: EFaultId_PCITargetNotFoundAl 227: EFaultId_PCITargetDSPAmountAlMEANING : There is a fault in the internal WSP/FSP PCI bus target (DSP) connections. Some of the WSP/FSP DSP processors may be broken and out of use.INSTRUCTIONS: Replace the alarming unit/module.

FAULT NAME : WSP failureFAULT ID : 3002: EFaultId_EubbWspAlMEANING : BTS has detected an abnormal operation or a failure in the internal functionality of the WSPF unit.INSTRUCTIONS: Note: Perform the steps below in the listed order until the alarm disappears.

118 DN99580892




1. Check the alarm history, alarming unit and subrack. 2. Check that the unit is properly connected. If the unit LED does not light up, it is faulty. 3. Reset the alarming unit. 4. Replace the alarming unit.

FAULT NAME : WSP unit internal failureFAULT ID : 97: EFaultId_WamWspOutOfSyncAlMEANING : The WAM and WSP are not synchronized.INSTRUCTIONS: 1. Block/unblock the alarming unit. 2. If that does not help, replace the alarming unit.


DN99580892 119




30 7652 BASE STATION NOTIFICATIONMeaning

A 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


InstructionsVerify the configuration of a BTS by checking thecommissioning, cabling and correct installation of theunits/modules at the BTS. Make sure the environment doesnot cause the fault.Before a unit/module is replaced at the BTS, the siteshould be reset to recover from any temporary faults whichmight have caused the malfunctioning of the unit/module.When an active alarm is a 'Start' alarm, a site reset isrequired to cancel the alarm. If the site reset or moduleblock/unblock does not help, replace the faulty unit/module(see source of the alarm and instructions fields of thecorresponding alarms).Below is the list of BTS fault(s) which might have causedthis alarm in WN 8.0 release. In case of earlier SW releaseand in case you need more detailed fault descriptions referto WCDMA RAN and Flexi Direct System Libraries. The BTS faultdescriptions are also included in BTS SW releasedocumentation. If that does not help, contact your local

120 DN99580892




Nokia Siemens Networks representative.

FAULT NAME : autonomous reset as recovery actionFAULT ID : 52: EFaultId_UnitAutonomousResetAlMEANING : The BTS tries to correct a fault situation by performing a recovery reset to a unit, the site, or the BTS.INSTRUCTIONS: Check the alarm history and other active alarms of the unit. Note! This alarm does not require any (special) actions.

FAULT NAME : 2M external reference missingFAULT ID : 1899: EFaultId_2MExtRefMissAlMEANING : The reference clock monitoring has detected a loss of 2.048 MHz signal received from an external reference source, connected to the Sync In interface of the System Module.INSTRUCTIONS: Note! Perform the steps below in the listed order until the alarm disappears. 1. Check the cabling (connected to Sync In interface). 2. Check that the 2.048MHz reference source is working normally and the 2.048 MHz signal is available. 3. Replace the alarming module.FlexiLiteBTS: Replace the Flexi Lite BTS.

FAULT NAME : ATM cell lossFAULT ID : 306: EFaultId_CellLossAlMEANING : ATM cells are lost. The cell loss can be caused by a traffic overload, by the WAM receiving an invalid ATM cell or AAL5 packet, or by the data corruption on the Iub (that is, a bad BER). The most common causes for this alarm are transmission network problems (causing unnecessary WAM changes).INSTRUCTIONS: 1. Check that bandwidths (cells/s) are the same at the BTS, AXC and RNC. 2. Check the data integrity from the incoming Iub (see Troubleshooting instructions). 3. Check the other transmission elements' active alarms (see the Alarms for AXC document). 4. Check the WAM, AXU and the cabling between them.

FAULT NAME : ATM, A2EA configuration errorFAULT ID : 315: EFaultId_A2eaConfigAlMEANING : The RNC A2EA transport layer address does not comply with the given BTS A2EA address. This alarm is reported to the BTS Site Manager only.INSTRUCTIONS: Check and re-commission the AXC (if AAL2 multiplexing is in use), RNC or BTS with the correct BTS A2EA addresses.

DN99580892 121




FAULT NAME : Active clock tuning faultFAULT ID : 1831: EFaultId_ActiveClkTuningAlMEANING : The phase measurement cannot be performed in the active WSC or WMC.INSTRUCTIONS: 1. Run fast tuning with BTS Site Manager. 2. Block/unblock the alarming unit. 3. Replace the alarming unit. Note that because of a fault situation in the active clock, the redundant clock is not tuned. To make sure that the tuning is correct, run "Fast Tune BTS Clock" with BTS Site Manager after the switchover when the new WSC is taken into use. If there is a WMC or only one WSC, the tuning continues but the cells remain disabled.

FAULT NAME : Antenna Line Device Operation FailureFAULT ID : 1871: EFaultId_BusyAl 1872: EFaultId_FormatErrorAl 1873: EFaultId_UnsupportedProcedureAl 1874: EFaultId_OutOfRangeAlMEANING : The device is not working properly, the configuration is not valid, or a given parameter is incorrect.INSTRUCTIONS: 1. Check the functionality of the antenna line device. 2. Check the compatibility between the antenna line device and the BTS. 3. Check that the given parameters are in the valid range.

FAULT NAME : Antenna Line Device failureFAULT ID : 3100: EFaultId_AntennaLineFailureMEANING : The System Module or the device itself has detected an abnormal operation or a failure in the antenna line device.INSTRUCTIONS: Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the antenna line and antenna line devices. Make sure that the antenna line connectors are in the right torque. 2. Reset the alarming RF module by blocking/unblocking it. 3. Replace the faulty parts and/or devices along the antenna line. 4. Replace the RF Module.

FAULT NAME : Antenna line device HW failureFAULT ID : 1847: EFaultId_HardwareErrorAlMEANING : A hardware failure detected by an antenna line device. Usually this is a permanent fault (the hardware is broken).INSTRUCTIONS: 1. Block/unblock the Radio module to give a power-off reset to the antenna line devices. 2. If that does not help, replace the antenna line device.

122 DN99580892




FAULT NAME : Antenna line device configuration failureFAULT ID : 1848: EFaultId_WorkingSoftwareMissingAl 1888: EFaultId_AlConfigurationFailureAlMEANING : An antenna line or antenna line device is not properly configured.INSTRUCTIONS: 1. Update the proper SW to the device. 2. Check/correct the antenna line configuration. 3. If that does not help, replace the antenna line device.


FAULT NAME : BTS reference clock missingFAULT ID : 3080: EFaultId_BtsReferenceClockMissingMEANING : This BTS fault indication is generated if the reference clock monitoring function of the BTS does not receive the highest configured synchronization reference signal or if all the synchronization reference signals are missing. The BTS fault is not generated if the highest configured synchronization source is present, no matter what the lower level source statuses are. Background information: There is a fixed synchronization priority list in the FlexiBTS:

DN99580892 123




-Priority 1: PPS (Pulse Per Second) signal connected to the Synchronization Input interface (Sync In) of the System Module. Normally the PPS signal is generated by the GPS receiver. -Priority 2: external 2.048MHz signal connected to the Sync In interface. -Priority 3: the reference signal coming from the integrated 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 (for example 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.INSTRUCTIONS: Depending on the installed and commissioned synchronization source(s) listed in section "Meaning", see the commissioned synchronization option below and perform the steps in the listed order until the BTS fault indication disappears. GPS receiver (PPS source): 1. If there is a GPS receiver commissioned at the BTS site, note the following: If the GPS receiver is not locked to any satellite, it turns off the PPS signal which is normally delivered to the BTS (Sync In interface). The most common reason is that the GPS receiver does not see any satellites because of poor antenna installation (poor sky visibility). The only permanent cure for this is to change the GPS antenna location. One indication of a fairly poor sky visibility is that the BTS fault is activated/canceled every now and then. 2. There might be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver. 3. There might be a malfunction in the BTS. Perform a BTS site reset. 4. The GPS cable and/or connectors might be damaged. Check the cable and the connectors. 5. There might be a HW fault in the GPS receiver. Check the operation and change the HW, if needed.

124 DN99580892




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 since the device type is not known, detailed instructions cannot be given. For further actions refer to the appropriate user manual of the device. 2. There might be a malfunction in the BTS. Perform a BTS site reset. FTM reference (TDM, SyncE or ToP as source): 1. If there is an integrated transmission unit (FTM) commissioned at the BTS site, note the following: the FTM unit operates so that if it is not locked to a 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) might be missing, causing the FTM internal clock to drop to holdover mode. In this case, the fault in the transmission network must be corrected (FTM itself might be working fine). 2. Check the alarms of the FTM unit and act accordingly. 3. Check the synchronization settings of the FTM unit. 4. There might be a malfunction in the BTS. Perform a BTS site reset. 5. There might be an equipment failure in the FTM unit. Check the operation and replace the unit, if needed. Note: Normally the reason is not an equipment failure, but there might be connection failures in the transmission or packet 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 transmission network instability, not to a failure in the unit. If the previous steps do not help, there might be an equipment failure in the System Module. Check the operation and if resetting the BTS site does not help, replace the System Module.

FAULT NAME : BTS reset needed to activate a license <licenseCode>, <licenseName>FAULT ID : 1877: EFaultId_ResetNeededForLicenceAlMEANING : The license status has changed to valid and a BTS reset is needed to take the license into use.INSTRUCTIONS: Reset the BTS.

FAULT NAME : BTS reset requiredFAULT ID : 4001: EFaultId_BtsResetNeededAlMEANING : The BTS detected an Extension Module as a capacity enhancement.

DN99580892 125




The BTS detected an RF Module that cannot be taken into use without the BTS reset. The RF Module type differs from the previous one.INSTRUCTIONS: Reset (block/unblock) the BTS.

FAULT NAME : BTS reset time increasedFAULT ID : 4091: EFaultId_BtsResetTimeIncreasedAlMEANING : BTS has detected RF module power cycle failure and is trying to recover from the failure during BTS reset procedure. BTS reset lasts longer due to additional actions performed by BTS in order to recover from faulty situation.INSTRUCTIONS: None

FAULT NAME : BTS time not correctedFAULT ID : 26: EFaultId_NtpTimeNotSetAlMEANING : The SNTP time cannot be fetched from the transport system (FT) within the time limit.INSTRUCTIONS: 1. Check the NTP setting. 2. Check the stratum parameter on the NTP server.

FAULT NAME : Baseband Bus failureFAULT ID : 3020: EFaultId_BaseBandBusFailureMEANING : The BTS has detected an abnormal operation or a failure in the BTS internal baseband bus. The failure cannot be pointed to a specific unit/module but there are several possible fault sources.INSTRUCTIONS: Note: Perform the steps below in the listed order. FlexiBTS: 1. Check other active BTS alarms and act accordingly. 2. Check the cables between the System Module and RF Module/Extension System 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 Extension System Module by blocking/unblocking it. c. Reset the master System Module. 4. Replace the alarming RF Module/Extension System Module. 5. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation, replace the alarming master System Module. UltraSite/EUBB: 1. Check other active BTS alarms and act accordingly. 2. Reset the alarming unit. 3. Check the cables in backplane. 4. Replace the alarming unit. FlexiLiteBTS:

126 DN99580892




1. Check other active BTS faults and act accordingly. 2. Reset the BTS by blocking/unblocking it. 3. Replace the Flexi Lite BTS.

FAULT NAME : Baseband reference clock missing (WSC)FAULT ID : 910: EFaultId_DualWscBrclkMssMEANING : The WSC is not able to deliver the clock signals required by the other units.INSTRUCTIONS: Replace the WSC.

FAULT NAME : Baseband reset neededFAULT ID : 4109: EfaultId_BasabandResetNeededMEANING : Unit containing common channel devices is being blocked. Baseband reset is needed to proceed with blocking. OR FSP is hot removed. Baseband reset is needed to proceed.INSTRUCTIONS: None

FAULT NAME : Cabinet door openFAULT ID : 1300: EFaultId_DoorAl0MEANING : The cabinet door is open or the cabinet door sensor is faulty.INSTRUCTIONS: 1. Ensure that the cabinet doors are properly closed. 2. Check that the door switches function correctly and that they have been adjusted correctly. Note: this alarm can be enabled or disabled in commissioning.

FAULT NAME : Communication failure with RNCFAULT ID : 114: EFaultId_RncHoRespAlMEANING : The BTS does not receive a response from the RNC (a block request).INSTRUCTIONS: Check the signaling link settings and the RNC connections.

FAULT NAME : Configuration error: <x>FAULT ID : 3070: EFaultId_ConfigurationErrorMEANING : There is an incompatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch between the BTS configuration and the RNC/Flexi Direct RNC parameters.INSTRUCTIONS: Note: Perform the steps below in the listed order. 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 RNC/Flexi

DN99580892 127




Direct RNC match the BTS HW configuration (for example frequency, power). 3. Check the RNC/Flexi Direct RNC BTS faults for the alarming local cell (LCR). 4. Recommission the BTS to ensure that all parameters are correctly configured.

FAULT NAME : Cooling fan brokenFAULT ID : 1933: EFaultId_FrFanBrokenMEANING : Fan/s is/are not running.INSTRUCTIONS: 1. Make sure that the fan connector is properly mounted. 2. If that does not help, replace the fan module.

FAULT NAME : Cooling fan brokenFAULT ID : 4078: EFaultId_FanBrokenAlMEANING : Fan(s)are not running although control is higher than 0.INSTRUCTIONS: 1. Check that the fan is not blocked. 2. Check that the fan connector is properly mounted. 3. If that does not help, replace the fan.

FAULT NAME : Cooling fan has reduced from the set speedFAULT ID : 1934: EFaultId_FrFanReducedSetSpeedMEANING : Fan/s is/are rotating slower than required.INSTRUCTIONS: 1. Make sure that the fan connector is properly mounted. 2. If that does not help, replace the fan module.

FAULT NAME : Cooling fan is over speedingFAULT ID : 4080: EFaultId_FanOverSpeedAlMEANING : Fan(s) are running faster than requested.INSTRUCTIONS: Replace the fan(s).

FAULT NAME : Cooling fan is over speedingFAULT ID : 1935: EFaultId_FrFanOverSpeedMEANING : Fan/s is/are rotating faster than required.INSTRUCTIONS: Replace the fan module.

FAULT NAME : Cooling fan out of orderFAULT ID : 1917: EFaultId_FrFanOutOfOrderMEANING : The RF Module cooling fan is not rotating at the specified speed.INSTRUCTIONS: Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the fan and cabling. 2. Block/unblock the RF Module. 3. Replace the faulty fan assembly.

128 DN99580892




FAULT NAME : Cooling fan speed decreasedFAULT ID : 4079: EFaultId_CoolingFanSpeedDecreasedAlMEANING : Fan(s) speed is deviating too much from requested control.INSTRUCTIONS: 1. Check that the fan is not blocked. 2. Check that the fan connector is properly mounted. 3. If that does not help, replace the fan.

FAULT NAME : Difference between BTS master clock and reference frequencyFAULT ID : 9: EFaultId_DacWordChangeAlMEANING : The reference frequency that the BTS master clock receives from the transport part has changed by about 0.2 ppm or more (which equals the change magnitude of 204 DAC steps or more) during the measurement period (about 20 minutes), compared to the BTS master clock frequency. The cause of the alarm can be: 1. The Iub reference frequency has changed due to a fault in the transmission network synchronization (which in turn is caused by an equipment fault or a setting error). Note that if the network synchronization malfunction lasts for a long time, the alarm is canceled when the BTS frequency reaches the faulty Iub synchronization. The alarm can also be activated if the faulty Iub 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 Iub 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 transmission 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). UltraSite, MetroSite, MetroSite 50, Triple-mode: Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WSC oven oscillator fault' becomes active, it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel.INSTRUCTIONS: Because there are several possibilities for the alarm

DN99580892 129




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 AXC node with AXC Manager, or FTM and act accordingly. - If there are no alarms, check the AXC/FTM synchronization settings. WSC/FCM unit: - If both the Iub reference signal accuracy and the AXC/FTM are in order but the WSC/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, reset the site. If the problem does not disappear in a few minutes, reset the site. - If that does not help, replace the WSC/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 transmission network, not to a fault in the unit. 4. After the fault situation has been cleared, you might need to tune the BTS master clock because the BTS master clock adjustment is quite slow. You can perform the tuning: - manually by changing the DAC word (during a site visit) - or with fast tuning, in which the BTS master clock is tuned in a few minutes automatically near the Iub reference (normal tuning takes care of the fine tuning). Note, however, that you should only use the fast tuning in case the Iub reference signal is known to be a good one.

130 DN99580892




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 MSC => RNC => BTS. 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 NAME : Error in file server during file download type <fileTypeNumber>FAULT ID : 27: EFaultId_FileServerAlMEANING : The BTS is unable to obtain a file from the file server (error in FTP open or FTP get). The file server is down, the file is missing, or the path is incorrect. A possible error in the DCN and Iub, or a user administration error (an invalid username or password, or the user does not have access rights for the files). <fileTypeNumber> included in fault name is a variable parameter identifying the type of file for which the download failure has been reported.INSTRUCTIONS: 1.Check the file type according to the table below: <fileTypeNumber> - <fileType> 1 - hwConfigurationFile 2 - configurationPlanFile 3 - logFile 4 - swFile 5 - licFile 6 - measurementFile 7 - rnwConfigurationPlanFile 11 - combinedSiteConfigurationPlanFile 12 - allConfigurationPlanFile 14 - testResultFile 15 - autoConfReport 17 - measurementPlanFile 18 - rnwMetadataFile 19 - topologyFile 22 - togglingParFile 23 - troubleShootingData 2. Retry the file update a few times. 3. Check the FTP account user settings. 4. Check the file and path names. 5. Check the administration log on the file server.

DN99580892 131




FAULT NAME : Extended logging level is activeFAULT ID : 4143: EFaultId_ExtendedLoggingLevelActiveAlMEANING : This fault is generated for a notification that extended logging level is activated and may decrease the BTS performance.INSTRUCTIONS: Extended logging may decrease the performance of BTS. In critical case, disactivate extended logging categories with BTS Site Manager.

FAULT NAME : FSM's sector based LCG is missingFAULT ID : 4086: EFaultId_FsmSectorLcgMissingMEANING : FSM does not have sector-based LCG commissioned to it.INSTRUCTIONS: Re-commission the BTS with a correct number of sector-based LCGs so that every FSM has an LCG.


FAULT NAME : Fan failureFAULT ID : 3050: EFaultId_FanFailureMEANING : All the fans or more than one in the same fan group are rotating slower or faster than required, are not rotating at all, or the RPM information is not available for the fans. The reason for this fault can be too low supply voltage or a broken fan.INSTRUCTIONS: Note: Perform the steps below in the listed order.

132 DN99580892




1. Make sure that the fan is not blocked. 2. Check the fan and cabling. 3. Replace the faulty fan module.

FAULT NAME : Fan module faulty: <X>FAULT ID : 1: EFaultId_FanPowerAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: All the fans or more than one fan in the same fan group (WFA, WTR, WPA/WMP, WHX) are rotating more slowly than required, are not rotating at all, or the RPM information is not available for the fans. The reason for this fault is too low a supply voltage or a broken fan control board. The WFA, WFD, or WHX fan control module also controls the fans in the RF section (same sector). A failure in the RF section fans is reported from that WFA, WFD, or WHX, and the LED of the unit is stable red although it is working correctly. FlexiBTS: All the fans or more than one fan in the same fan group are rotating more slowly than required.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Check the Fan ID from the fault message and locate the problematic fan. See the Fan mapping figures in the Alarms and Troubleshooting document. 2. Check the fan and cabling. 3. If that does not help, replace the WFA, WFD, or MFU module. Or replace the fan controlled by the WFA, WFD, or MFU. Fan control: 'FAN UNIT' refers to a group of fans including the fan control unit. A 'fan' is a single blower. FlexiBTS: 1. Check the fans and connector. 2. Replace the fan module.

FAULT NAME : Fan module operation degraded: <X>FAULT ID : 0: EFaultId_ChangeFanAlMEANING : A fan does not rotate, rotates slower than required, or the RPM information is not available for the fan.INSTRUCTIONS: UltraSite, UltraSite/EUBB: 1. Check the fan ID from the fault message and locate the problematic fan. See the Fan mapping figures in the UltraSite and MetroSite WCDMA Base Station Faults document. 2. Check the fan and cabling. 3. If that does not help, replace the WFA, WFD, or MFU module. Or replace the fan controlled by the WFA, WFD, or

DN99580892 133




MFU. Fan control: 'FAN UNIT' refers to a group of fans including the fan control unit. A 'fan' is a single blower. FlexiBTS: 1. Check the fan and connector. 2. Replace the fan module.

FAULT NAME : Fan vendor not detectedFAULT ID : 4073: EFaultId_FanVendorNotDetectedAlMEANING : Fan speed is too low for successful detection. Detection is tried again after Fan.Test.Timer expires.INSTRUCTIONS: 1. Check the fan and connector. 2. Replace the fan.

FAULT NAME : File corrupted in SW downloadFAULT ID : 28: EFaultId_SwPackageAlMEANING : The download is corrupted or incorrectly formed SW.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Retry the SW update. 2. Fetch the BTS log files and check the download status from the BTS SWDLreport. FlexiBTS, FlexiLiteBTS: 1. Retry the SW update. 2. Save the snapshot and check the download status from the BTS SWDLreport in the snapshot file.

FAULT NAME : Filter unit operation failedFAULT ID : 1840: EFaultId_TuningFailureAl 1841: EFaultId_UnitFaultyAl 4043: EFaultId_TuningFrequencyOutOfRangeAlMEANING : A filter has not been able to tune on an appropriate sub-band properly (tuning failure), or another major failure has been detected by the filter (unit faulty).INSTRUCTIONS: In case of 4043:EFaultId_TuningFrequencyOutOfRangeAl: reconfigure the frequency settings. In case of 1840:EFaultId_TuningFailureAl, 1841:EFaultId_UnitFaultyAl: replace the filter unit.

FAULT NAME : GPS Receiver alarm: EEPROM invalidFAULT ID : 4126: EFaultId_GpsReceiverEepromInvalidAlMEANING : GPS receiver has detected that one or more EEPROM segments were corrupt at reset, and its/their factory default settings need to be restored.INSTRUCTIONS: Perform the steps below in the listed order until the fault disappears. EEPROM invalid: 1. The GPS receiver has detected a malfunction in the

134 DN99580892




EEPROM memory of the GPS receiver. Perform a (remote) power reset for the GPS receiver. 2. There might be an HW fault in the GPS receiver. Check the operation and change the GPS module if needed.

FAULT NAME : GPS Receiver alarm: no stored positionFAULT ID : 4124: EFaultId_GpsReceiverNoStoredPositionAlMEANING : There is no accurate position stored in EEPROM.INSTRUCTIONS: Perform the steps below in the listed order until the fault disappears. No stored position: 1. One of the GPS receiver settings is incorrect. Using the manager SW of the GPS receiver, set the receiver to store the position into non-volatile memory. If there is no tick mark in the position storage selection, the GPS receiver runs the site/self survey every time the GPS receiver is reset (either by manager command, power outage, or a GPS recovery reset). This means that if the GPS receiver installation quality is only 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 NAME : GPS Receiver alarm: not tracking satellitesFAULT ID : 4122: EFaultId_GpsReceiverNotTrackingSatellitesAlMEANING : Poor GPS antenna installation.INSTRUCTIONS: Perform the steps below in the listed order until the fault disappears. Not tracking satellites: 1. Definitely 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. See documentation for installations, and if there are discrepancies 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 disturbances to 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 NAME : GPS Receiver alarm: position questionableFAULT ID : 4125: EFaultId_GpsReceiverPositionQuestionableAl

DN99580892 135




MEANING : The receiver is used in a stored position, but then is moved to a new position.INSTRUCTIONS: Perform the steps below in the listed order until the fault disappears. Position questionable: 1. The GPS receiver has valid position data but it is not properly in line with the information estimated from the actual satellite visibility. The reason for this fault indication might be that the GPS antenna installation has not been done properly, that is the sky visibility is not good enough. Please refer the documentation for instructions and if there are deviations with the actual installation, re-install the GPS antenna. Please notice 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 NAME : GPS Receiver alarm: survey in progressFAULT ID : 4123: EFaultId_GpsReceiverSurveyInProgressAlMEANING : The GPS receiver is running a site/self survey.INSTRUCTIONS: Perform the steps below in the listed order until the fault disappears. Survey in progress: 1. Do nothing. The alarm is informative only. Normally, the GPS receiver runs the survey for two reasons: a) somebody has started the survey manually; b) the GPS receiver has detected that the position has changed and the receiver has started an automatic survey. Note also that an automatic survey takes place every time during the first start-up. 2. If an automatic survey takes place every now and then, it might be an indication that the sky visibility is poor, and based on the poorly tracked satellites, the GPS receiver concludes that the position has changed. In this case, check activity of other faults (BTS fault history data), and if feasible, re-install the GPS antenna. 3. If the GPS installation is good but still an automatic survey takes place every now and then, there might be a malfunction in the GPS receiver. Perform a (remote) power reset for the GPS receiver. 4. If the actions detailed in previous steps do not correct the situation, there might be an HW fault in the GPS receiver. Check the operation and change the GPS module if needed.

136 DN99580892




FAULT NAME : GPS receiver alarm: control interface not availableFAULT ID : 4011: EFaultId_GPSSystemElementAlMEANING : BTS has detected communication problem with the GPS receiver.INSTRUCTIONS: Perform the steps below in the listed order until the fault disappears. 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 do not support a common interface. Otherwise, perform a (remote) power reset for the GPS receiver. 2. Perform a (remote) BTS site reset for the whole BTS. 3. Perform a power reset for the whole BTS. 4. The cable between the GPS receiver and the BTS might work improperly. Make sure that 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 an HW fault in the GPS receiver. Check the operation and change the GPS module, if needed. 7. There might be an HW fault in the BTS System Module. Check the operation and change the System Module, if needed.

FAULT NAME : Heating element not workingFAULT ID : 1860: EFaultId_HeatingMatNotWorkingAlMEANING : The heater control connection of the FSM is faulty, there is no heater or the heater is faulty.INSTRUCTIONS: 1. Check whether the heating element exists at all. 2. Check the heater control connection and that the heater is working. 3. Replace the alarming component.

FAULT NAME : Incoherency in cell configurationFAULT ID : 4000: EFaultId_IncoherencyInConfigurationMEANING : Too many LCRs are commissioned to one RF Module.INSTRUCTIONS: Recommission the BTS with a correct number of LCRs per RF Module.

FAULT NAME : Incompatible SW version detectedFAULT ID : 23: EFaultId_IncompatibleSwVersionAl 24: EFaultId_ObsoleteSwVersionAlMEANING : A new unit with incompatible SW has probably been inserted

DN99580892 137




in the BTS.INSTRUCTIONS: Update compatible SW to the BTS (check the SW versions to see the active SW version, and update the active SW version), unless it is automatically updated by NetAct. NOTE: If also fault 10:EFaultId_NoConnectionToUnitAl is active on the source unit then SW update should be postponed until fault 10:EFaultId_NoConnectionToUnitAl is cancelled. Related BTS - AXC interface: check the SW version of the BTS and AXC, and update compatible SW to the AXC or BTS.

FAULT NAME : Invalid configuration fileFAULT ID : 4036: EFaultId_InvalidConfigurationFileAlMEANING : The commissioning file is missing, or an incorrect commissioning file has been detected during a BTS startup as follows: "Validation failed because of incompatible data"INSTRUCTIONS: 1. Check and correct the contents of the commissioning file. 2. Recommission the BTS with a valid commissioning file.

FAULT NAME : MHA unit operation failureFAULT ID : 1869: EFaultId_MinorTMAFaultAl 1870: EFaultId_MajorTMAFaultAlMEANING : A fault in the Masthead Amplifier (MHA) is detected. The fault reduces the gain performance or completely prevents the function of the MHA.INSTRUCTIONS: 1. Check the MHA type and configuration settings of BTS. If the given MHA requires DC voltage on BTS2 (Diversity) port, perform ALD commissioning properly and reset BTS. 2. Replace the alarming module.

FAULT NAME : Module not supported by current SW versionFAULT ID : 4063: EFaultId_NotSupportedModuleMixAlMEANING : An unsupported module was detected in the System Module. Typically, this happens when the System Module SW in use does not support the module.INSTRUCTIONS: Replace the unsupported module or upgrade the System Module SW.

FAULT NAME : No connection to WEA and unable to detect External alarmsFAULT ID : 70: EFaultId_UnableToDetectEacAlarmsAlMEANING : The WEA unit is missing from the BTS or it cannot be detected.INSTRUCTIONS: 1. Check the WEA and cabling. See Troubleshooting instructions for how to check units behind the same bus. 2. If that does not help, replace the alarming unit.

138 DN99580892





FAULT NAME : No module fan detectedFAULT ID : 1932: EFaultId_FrNoFansDetectedMEANING : Radio Module cannot identify the used fan type, or the fan is not installed.INSTRUCTIONS: 1. Make sure that the fan connector is properly mounted. 2. If that does not help, replace the fan module.

FAULT NAME : Non fatal ATM traffic overloadFAULT ID : 305: EFaultId_CongestionAlMEANING : Traffic load is approaching the maximum capacity. However, no data is discarded yet.

DN99580892 139




INSTRUCTIONS: Check that the ATM configurations in the BTS, AXC and RNC match.

FAULT NAME : Not enough DSP capacity to set up a cellFAULT ID : 124: EFaultId_NotEnoughWspCapasitySetupCellAlMEANING : Not enough BTS baseband capacity to set up a cell.INSTRUCTIONS: 1. Lock/unlock the cells. 2. Add more baseband capacity to BTS or replace the broken baseband unit, if that was the reason for the lack of capacity.

FAULT NAME : Not enough resources for commissioned HSUPAFAULT ID : 130: EFaultId_MinimumNumberOfClusterFractionsUnavailableAlMEANING : There are not enough resources for the HSUPA minimum capacity based on the commissioned parameters "Minimum Baseband Decoding Capacity" and "Minimum HSUPA Users".INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Check the configuration to make sure that there are enough resources for the minimum HSUPA capacity. 2. If there are not enough resources, add the required number of WSP units, replace the broken ones, or re-commission the BTS and pre-reserve less capacity for the HSUPA. 3. Reset the BTS to get the minimum capacity preselection for the HSUPA in use. FlexiBTS and FlexiLiteBTS: 1. Check the configuration to make sure that there are enough resources for minimum HSUPA capacity. 2. If there are not enough resources, replace the broken module or re-commission the BTS and pre-reserve less capacity for HSUPA. 3. Reset the BTS to get the minimum capacity preselection for the HSUPA in use. UltraSite/EUBB: 1. Check the configuration to make sure that there are enough resources for minimum HSUPA capacity. 2. If there are not enough resources, replace the broken WSPF or re-commission the BTS and pre-reserve less capacity for HSUPA. 3. Reset the BTS to get the minimum capacity preselection for the HSUPA in use.

FAULT NAME : OIC MCU Buffer FullFAULT ID : 2011: EFaultId_OIC_MCUBFullAlMEANING : The control message traffic between the modules is malfunctioning.

140 DN99580892




INSTRUCTIONS: Check the RF Module alarms.

FAULT NAME : Oven oscillator clock missingFAULT ID : 903: EFaultId_OcxoClkMss 911: EFaultId_DualWscOcxoClkMssMEANING : The WSC is not able to deliver the clock signals required by the other units.INSTRUCTIONS: Replace the clock unit.

FAULT NAME : Oven oscillator heating failureFAULT ID : 901: EFaultId_OcxoHeatingAl 912: EFaultId_DualWscOvAMssMEANING : The heating of oven oscillator fails and the unit is broken. The ambient temperature can also be too low or change too fast.INSTRUCTIONS: 1. Check the active fan alarms. 2. Replace the clock unit.

FAULT NAME : PIC pool configuration failureFAULT ID : 154: EFaultId_PicPoolConfigurationFailureAlMEANING : Problem with PIC pool mapping due to UARFCN mismatch occured (UARFCN received from RNC is not compatible with UARFCN determined by BTSSM). Telecom checks if current PIC pool configuration in BTS (determined based on UARFCN delivered by BTSSM) is valid for UARFCN received from RNC during Cell Setup procedure.INSTRUCTIONS: When the fault is detected, operator should check UARFCN configuration. If PIC is required then UARFCN values should be changed in BTSSM.

FAULT NAME : PPS reference missingFAULT ID : 1898: EFaultId_PpsRefMissAlMEANING : The reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver.INSTRUCTIONS: FlexiBTS: 1. Check the GPS receiver installation. 2. Check the GPS receiver status. 3. Check connection between the GPS receiver and FSM. FlexiLteBTS: 1. Check the GPS receiver installation. 2. Check the GPS receiver status. 3. Check connection between the GPS receiver and Flexi Lite BTS.

FAULT NAME : Peer system module connection lostFAULT ID : 4110: EFaultId_PeerSystemModuleConnectionLostAl

DN99580892 141




MEANING : The master system module has lost optical connection to the peer system module.INSTRUCTIONS: Check the optical connection between master and peer system modules.

FAULT NAME : Power on smodLogicalId pwrLineId line switched off remotely by userFAULT ID : 4107: EFaultId_RfPowerSwitchedOffFromBtsSmAlMEANING : Power feeding for the given Radio Module has been switched off by the user from BTS Site Manager remotely.INSTRUCTIONS: Enable power feeding towards Radio Module by switching RF power on in BTS Site Manager.

FAULT NAME : RET antenna control failureFAULT ID : 1842: EFaultId_MotorJamAl 1843: EFaultId_ActuatorJamAl 1844: EFaultId_NotCalibratedAl 1845: EFaultId_NotConfiguredAl 1846: EFaultId_ActuatorInterferenceAlMEANING : Antenna tilting is not possible or might function incorrectly.INSTRUCTIONS: 1. Recalibrate the RET antenna. 2. If that does not help, replace the RET unit.

FAULT NAME : RF Module failureFAULT ID : 3010: EFaultId_RfModuleFailureMEANING : The FlexiBTS has detected an abnormal operation or a failure in the internal functionality of the RF Module.INSTRUCTIONS: Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the other active BTS alarms (System Module failure, Baseband Bus failure, Failure in optical RP3 interface and Antenna Line Device failure) and act accordingly. 2. Reset the alarming RF Module by blocking/unblocking it. 3. Check cables between the System Module and the RF Module. 4. If that does not help, replace the faulty RF Module.

FAULT NAME : RF Module overvoltage protection faultyFAULT ID : 1942: EFaultId_FrOverVoltageProtectionFaultyMEANING : RF Module overvoltage protection is broken.INSTRUCTIONS: Replace the alarming RF Module.

FAULT NAME : RF loss of secondary optical interfaceFAULT ID : 1930: EFaultId_FRLossOfSecondaryOptIf

142 DN99580892




MEANING : Secondary optical link between the System Module and the RF Module is lost.INSTRUCTIONS: 1. Check cables between the System Module and the RF Module. 2. Block/unblock the RF Module. 3. If that does not help, block/unblock the site. 4. If that does not help, replace the alarming RF Module.

FAULT NAME : RF module temperature is highFAULT ID : 1941: EFaultId_FrOverTempAlMEANING : Validated module temperature is greater than the predefined value on unit property file. Relevant for Rel1 RF module only.INSTRUCTIONS: Check the fans and ensure that the ambient temperature on the site is is acceptable.

FAULT NAME : RF sensor temperature too high in Flexi LiteFAULT ID : 4074: EFaultId_RfModuleTempTooHighInSbfAlMEANING : Validated sensor temperature is greater than the predefined property value in BTS Property File. Relevant for Flexi Lite RF part only.INSTRUCTIONS: Check the fans and ensure that the sensor temperature on the site is acceptable.

FAULT NAME : Read-only field encountered in the antenna line deviceFAULT ID : 4140: EFaultId_ReadOnlyAlMEANING : An attempt to modify a field value in Antenna Line Device failed because the field is read-only.INSTRUCTIONS: No action required from the operator.

FAULT NAME : Reading license targetID from BTS failedFAULT ID : 4023: EFaultId_FrParameterReadFailedAlMEANING : Failure occured during reading parameter from the Radio Module.INSTRUCTIONS: Note! Perform the steps below in the listed order until the alarm disappears. 1. Check the other active alarms. If the memory is corrupted, change the alarming module. 2. Reset the RF Module by blocking/unblocking it. 3. Replace the alarming module.

FAULT NAME : Reduced receiver capacity in cellFAULT ID : 141: EFaultId_ReducedRachPreAmbleSignaturesAlMEANING : The RNC has requested a higher number of PRACH preamble signatures than the BTS can support for the requested cell range.

DN99580892 143




INSTRUCTIONS: Commissionasmaller amount of PRACH preamble signatures to the cell in the RNC and set up the cell again. This will trigger a new cell setup request for the BTS and the BTS cancels the fault, if the requested number of RACH preamble signatures is less or equal to the maximum number of supported RACH preamble signatures for the cell range in the BTS.

FAULT NAME : Retrieving backup license targetId information from BTS failedFAULT ID : 4041: EFaultId_FrParameterMOExistenceCheckFailedAlMEANING : Retrieving the list of all parameters available in the Radio Module memory failed. The list is retrieved in order to check whether it contains the license targetId parameter.INSTRUCTIONS: Note: Perform the steps below in the listed order until the fault disappears. 1.Check the other active faults. If the memory is corrupted, replace the alarming module. 2. Reset the RF Module by blocking/unblocking it. 3. Replace the alarming module.

FAULT NAME : Smoke alarmFAULT ID : 1310: EFaultId_SmokeAlMEANING : The internal smoke detector has detected smoke in the cabinet.INSTRUCTIONS: 1. Check the root cause. 2. If the alarm was false, replace the alarming smoke detector.

FAULT NAME : System frame clock synchronization error in clock deviceFAULT ID : 5004: EFaultId_BofuSfclkErr 5007: EFaultId_BofuFrameSyncErr 5008: EFaultId_BofuSfnSigErrMEANING : The system frame alignment is lost or a parity error is detected in the incoming frame burst of BOFU FPGA.INSTRUCTIONS: 1. Reset BTS. 2. If resetting the BTS does not help, replace the WSMF.

FAULT NAME : Temperature alarmFAULT ID : 3040: EFaultId_TemperatureAlarmMEANING : The internal temperature of the RF Module or System Module exceeds the threshold value, or the ambient temperature of the module(s) is beyond the specified limits.INSTRUCTIONS: Note: Perform the steps below in the listed order.

144 DN99580892




1. Check 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/unit by blocking/unblocking it. 4. Replace the alarming module/unit.


FAULT NAME : Unit temperature is highFAULT ID : 2: EFaultId_UnitOverheatAlMEANING : The temperature of a unit/module exceeds the threshold value.INSTRUCTIONS: Check the active fan alarms, and the airflow of the BTS.

FAULT NAME : User logging inactiveFAULT ID : 4151: EFaultId_UserLoggingInactiveAlMEANING : User-configured logging is temporarily suspended because of high load situation in BTS.INSTRUCTIONS: If the situation keeps repeating, consider modifying of custom logging to less detailed log settings.

FAULT NAME : WCI baseband reference clock failureFAULT ID : 1001: EFaultId_RedundantClkMss 1002: EFaultId_MasterClkMssMEANING : The master or redundant WSC does not generate Baseband Reference Clock (BRCLK) to the WCI because of an internal failure or a clock driver failure in the WSC unit.INSTRUCTIONS: 1. Block/unblock the active WSC unit. 2. Replace the WCI unit. 3. Replace both WSC units.

DN99580892 145




FAULT NAME : WEA power regulator faultFAULT ID : 1303: EFaultId_RegulatorAlMEANING : The WEA unit external interface connectors are connected incorrectly, or there is a shot circuit in the +5 VCD.INSTRUCTIONS: 1. Disconnect the external cables and check whether the alarm disappeares. 2. Check the external cables and connections. 3. If the alarm does not disappear, check the WEA and replace it if it is faulty.

FAULT NAME : WIB unit battery failureFAULT ID : 1304: EFaultId_BatteryVoltageAl 1307: EFaultId_BatteryFailure 1308: EFaultId_CellBalanceAlMEANING : WIB unit battery failure: - Several battery blocks (cells) are dead and the back-up system is out of order. - Some of the battery blocks (cells) reached an overcharge or a discharge voltage in a stand-by condition. - The voltage of one cell is not compatible with the other cell voltages.INSTRUCTIONS: 1. Check the battery cablings and cells' voltage levels. 2. Replace the WIB unit or battery.

FAULT NAME : WIB unit battery temperature out of rangeFAULT ID : 1306: EFaultId_BatteryTempAlMEANING : Because the heater or the heater control unit does not work correctly, the temperature measured inside the unit is out of the normal temperature range.INSTRUCTIONS: 1. Check the battery space's temperature. 2. Check the battery temperature sensor.

FAULT NAME : WIB unit power back-up time alarmFAULT ID : 1305: EFaultId_BackupTimeAlMEANING : The WIB cannot supply nominal power for 10 seconds and/or the estimated battery life is 26 weeks or less.INSTRUCTIONS: Replace the WIB unit.

FAULT NAME : WSC oven oscillator faultFAULT ID : 907: EFaultId_DualWscDacWordAlarmMEANING : The oven oscillator adjusting area is reaching its limit value. The alarm is activated if the WSC tunes the oven oscillator so that the DAC word (parameter to control the oven oscillator output frequency) value becomes lower than 205 or greater than 3891 (5 of the total adjustment area). The range for the DAC word is 0 - 4095. The cause of the

146 DN99580892




alarm can be: - The Iub reference frequency has been incorrect for a long time (up to several days) due to a fault in the transmission network synchronization (which in turn is caused by an equipment fault or a setting error). Before activating this alarm, the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' may have been active. - 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 in that signal. In that case, the alarm behavior notifications listed with the Iub signal (see above) are also valid in this case. - The fast tuning action of the BTS master clock may have been executed without checking if the reference signal is correct or not. If the reference signal is incorrect during the fast tuning execution, it may result in adjusting the BTS master clock frequency far from the nominal value, which causes serious problems in the network performance. - There is an equipment fault in the BTS. - Due to the oven oscillator (OCXO) aging inside the WSC unit, the unit may be approaching the end of its lifetime. In suchcase,after the alarm activation, the DAC value is quite stable, whereas in the other fault cases it may be very unstable or at the edge of the adjustment area (0 or 4095). Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WSC oven oscillator fault' becomes active, it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel.INSTRUCTIONS: 1. In the case of a fault in the transmission network synchronization, you need to correct the network synchronization. The long-term accuracy of the Iub signal must be +/- 0.015 ppm or better. 2. In case of BTS equipment fault, the location may be: 2.1 Transport part - First check the alarms of the AXC node with AXC Manager and act accordingly. - If there are no alarms, check the AXC synchronization settings. 2.2 WSC unit - If both the Iub reference signal accuracy and the AXC node are in order but the WSC unit is still alarming, run the fast tuning procedure with BTS Site Manager. - If that does not solve the problem in a few minutes, reset the site. - If that does not help, replace the WSC unit. Note: In

DN99580892 147




case the BTS is equipped with two WSCs, the redundant unit takes over the operation of the faulty unit. But if the fault situation is caused by an incorrect reference signal, both the WSC units may start alarming sooner or later. 3. After the fault situation has been cleared, the BTS master clock may also require tuning, 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, where the BTS master clock is tuned automatically in a few minutes near the Iub reference (normal tuning takes care of the fine tuning) Note, however, that the fast tuning should only be used 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 a mobile network, the synchronization goes from MSC > RNC > BTS. 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 also the synchronization of the leased line service provider is accurate/stable 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 NAME : WSC phase difference jammed to zero readingFAULT ID : 22: EFaultId_WscPhaseDiffJammedAlMEANING : The WSC phase measurement is jammed and the tuning operation is degraded. The problem can be caused by a WSC fault, or a too fast frequency change on the Iub.INSTRUCTIONS: 1.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, the synchronization of the transmission network must be corrected. The limits for the jitter/wander are defined in the ITU-T G.823. No actions on the BTS are needed. 2. Reset the site and wait about 10 minutes. 3. Try a power-on reset. If the alarm reappears, replace the unit. If the alarm reappears during the next few weeks or the clock seems unstable, replace the unit. Background information: The principle in the mobile network is that the synchronization goes from MSC => RNC => BTS. But in reality that chain might be broken somewhere and,

148 DN99580892




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 also the synchronization of the leased line service provider is accurate/stable 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 NAME : WSC switch unsuccessfulFAULT ID : 1823: EFaultId_ClkSwitchFailAlMEANING : The WSC recovery switch over failed.INSTRUCTIONS: 1. Fast tune the active unit. 2. Block/unblock the alarming unit. This may cause a BTS reset.


FAULT NAME : WSMA ST-Bus errorFAULT ID : 1117: EFaultId_WsmStLeftParityErr2 1119: EFaultId_WsmStLeftSyncErr2 1121: EfaultId_WsmStRightParityErr2 1123: EfaultId_WsmStRightSyncErr2MEANING : The TX signal is transported from the WSP unit to all WTR units via the WSMs. The WSM units in different subracks are connected to each other via the ST buses. This alarm is generated when the WSM unit detects errors in the incoming ST bus from the adjacent WSM unit. The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm.INSTRUCTIONS: 1. Run the WCDMA BTS loop test. 2. Check the WSM cables. 3. Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions).

FAULT NAME : WSMA T-Bus error

DN99580892 149




FAULT ID : 1125: EFaultId_Wsp0ParityErr2 1127: EFaultId_Wsp0SyncErr2 1129: EFaultId_Wsp1ParityErr2 1131: EFaultId_Wsp1SyncErr2 1133: EFaultId_Wsp2ParityErr2 1135: EFaultId_Wsp2SyncErr2 1137: EFaultId_Wsp3ParityErr2 1139: EFaultId_Wsp3SyncErr2 1141: EFaultId_Wsp4ParityErr2 1143: EFaultId_Wsp4SyncErr2 1145: EFaultId_Wsp5ParityErr2 1147: EFaultId_Wsp5SyncErr2 1248: EFaultId_Wsp1TbusParityErr2 1249: EFaultId_Wsp0TbusParityErr2 1250: EFaultId_Wsp1TbusSyncErr2 1251: EFaultId_Wsp0TbusSyncErr2MEANING : The signal is transported from the WSP unit to the WTR unit via the WSM/WMC. This alarm is generated when the WSM unit detects errors in the incoming T bus from the WSP unit. The reason for the failure is probably the WSP or WSM/WMC unit. The unit may have been installed incorrectly or the backplane cabling is faulty.INSTRUCTIONS: Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions).

FAULT NAME : Waiting for RF connectionsFAULT ID : 1859: EFaultId_WaitingRfConnectionAlMEANING : The module has been configured as a master System Module, but no Radio Module is connected to it.INSTRUCTIONS: Add Radio Modules to the System Module if it is intended to be the master System Module.

FAULTNAME : Writing parameter to Radio Module failedFAULT ID : 4022: EFaultId_FrParameterWriteFailedAlMEANING : Failure occured when writing parameter to the Radio Module was requested.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears. 1. Check the other active faults. If the memory is corrupted, change the alarming module. 2. Reset the RF Module by blocking/unblocking it. 3. Replace the alarming module.

150 DN99580892




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

DN99580892 151


7653 CELL FAULTY


31 7653 CELL FAULTYMeaning

A critical fault (or faults) has occurred in a unit/module (orunits/modules) that belong to the sector indicated in the alarm.

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



2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number


InstructionsVerify the configuration of a BTS by checking thecommissioning, cabling and correct installation of theunits/modules at the BTS. Make sure the environment doesnot cause the fault.Before a unit/module is replaced at the BTS, the siteshould be reset to recover from any temporary faults whichmight have caused the malfunctioning of the unit/module.When an active alarm is a 'Start' alarm, a site reset isrequired to cancel the alarm. If the site reset or moduleblock/unblock does not help, replace the faulty unit/module(see the source of the alarm and instructions fields of thecorresponding alarms).Below is the list of BTS fault(s) which might have causedthis alarm in BTS WN 8.0 release. In case of earlier SWrelease and in case you need more detailed faultdescriptions refer WCDMA RAN and Flexi Direct System Libraries.The BTS fault descriptions are also included in BTS SWrelease documentation. If that does not help, contact your

152 DN99580892



7653 CELL FAULTY

local Nokia Siemens Networks representative.

FAULT NAME : AIR fatal alarmFAULT ID : 1515: EFaultId_FatalAlMEANING : ARIO has detected a Fatal level alarm. Some ARIO alarms can be canceled without a reset but most ARIO alarms require the WOU block/unblock to cancel.INSTRUCTIONS: 1. Check the WOU or WRUs. 2. Use the ARIO Local Management Tool and the Advanced Indoor Radio user documentation to diagnose the cause of the error.


FAULT NAME : Antenna line faultyFAULT ID : 4045: EFaultId_AntennaLineFaultyAlMEANING : An alarm message has been received from the antenna line. The antenna line is faulty.INSTRUCTIONS: 1. Check the antenna line and antenna line device that causes the alarm. 2. Fix or replace the faulty parts/devices.

FAULT NAME : Antenna1 connection faultFAULT ID : 804: EFaultId_Ant1Al 809: EFaultId_Ant2Al 814: EFaultId_Ant3AlMEANING : The BIAS-T has detected that the reflected TX power from the antenna has increased. The antenna cable between the WAF and MHA is faulty or the antenna is faulty. The BIAS-T may be faulty.INSTRUCTIONS: 1. Check the bias-T and MHA commissioning. 2. Block/unblock the WAF unit (check if the alarm reappears after 5 minutes). 3. Check the antenna line (see Troubleshooting instructions).

DN99580892 153


7653 CELL FAULTY


4. Check the PITA cable connection (RJ45). a. Check the voltage (see connector pins in Troubleshooting instructions). b. Check the right connection (see User Manual). c. Check by cross connecting RJ45 cables between other sectors.

FAULT NAME : BB bus reception error (summing device)FAULT ID : 2016: EFaultId_Muksu_SMTimeOffAlMEANING : The master frame in the received baseband bus frame is not in the correct place related to the internally generated master frame pulse. Either the frame has been set in the wrong place (PI delay), or the data itself is in the wrong place.INSTRUCTIONS: FlexiBTS: 1. Check the cables between the Master System Module and RF Module/Extension System Module. 2. Replace the unit causing the fault (Master System Module, Extension System Module, RF Module, FBIA). UltraSite/EUBB: 1. Replace the unit causing the fault (WSPF, WSMF).

FAULT NAME : BTS config error (All units in a cell must be of same freq)FAULT ID : 58: EFaultId_FrequencyBandConflictInCellAlMEANING : A unit with an incompatible frequency type has been detected. All units in the cell must be of the same frequency type.INSTRUCTIONS: Check the unit frequency types in the cell and replace the incompatible unit with a compatible one.

FAULT NAME : BTS config error (Not enough HW for LCR)FAULT ID : 1868: EFaultId_NotEnoughHwForLcrAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: A dual carrier WTR has been replaced with a single carrier WTR, and it cannot serve both cells commissioned to the WTR. FlexiBTS: A dual PA RF Module has been replaced with a single PA RF Module, and it cannot serve all cells commissioned to the RF Module.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: Replace the single carrier WTR with a dual carrier WTR. FlexiBTS: Replace the single PA RF Module with a dual PA RF Module. Alternatively, recommission the BTS with fewer cells.

154 DN99580892



7653 CELL FAULTY

FAULT NAME : BTS config error (WAF overload, 50W not in dualWPA config)FAULT ID : 61: EFaultId_WafTxConnectorOverloadAlMEANING : Two 50 W WPAs are coupled to one WAF, or one 50 W WPA and one 28 W WPA are coupled to one WAF. Only two 28 W WPAs can be coupled together to one WAF unit.INSTRUCTIONS: Replace the 50 W WPAs with the 28 W WPAs.

FAULT NAME : BTS config error (WPA / WSMA version conflict in cell)FAULT ID : 68: EFaultId_WpaWsmaVersionConflictAlMEANING : A WPAI/WPAJ with two carriers and a WOC were detected in the combination with a WSMA.INSTRUCTIONS: Replace the WSMA with a WSMB. Or replace the WPAI and WPAJ with a WPAA/WPAB.

FAULT NAME : BTS config error (WTR used as dual TRX behind WSMA)FAULT ID : 54: EFaultId_WtrbWsmaVersionConflictAlMEANING : A WTR/WSM conflict is detected. The incompatible WTR cannot operate with the WSMA when two TRXs are used.INSTRUCTIONS: Replace the incompatible unit or recommission the BTS (Reconfiguration commissioning) with only one TRX on.


DN99580892 155


7653 CELL FAULTY


FAULT NAME : BTS internal SW management problemFAULT ID : 3090: EFaultId_BtsInternalSwManagementProblemMEANING : A software update to a unit/module or subassembly has failed, or a corrupted SW file has been detected in the FLASH.INSTRUCTIONS: Note: Perform the stepsbelowin the listed order. FlexiBTS: 1. Check other active BTS faults. If the ROM disk is corrupted, change the alarming module. 2. Reset the RF Module and/or FBIA and/or System Module, depending on the alarm source: a. Reset the RF Module by blocking/unblocking it. b. Reset the FBIA by blocking/unblocking it. c. Reset the System Module. 3. Update and activate the SW to the BTS. 4. Check the SW files. 5. Replace the alarming module/unit. UltraSite/EUBB: 1. Check other active BTS faults. If the ROM disk is corrupted, change the alarming unit. 2. Reset the alarming unit. 3. Update and activate the SW to the BTS. 4. Check the SW files. 5. Replace the alarming unit. FlexiLiteBTS: 1. Reset the and/or DSP and/or CC&T, depending on the alarm source. 2. Update and activate the SW to the BTS. 3. Check the SW files. 4. Replace the alarming Flexi Lite BTS.

FAULT NAME : BTS reset requiredFAULT ID : 4001: EFaultId_BtsResetNeededAlMEANING : The BTS detected an Extension Module as a capacity enhancement. The BTS detected an RF Module that cannot be taken into use without the BTS reset. The RF Module type differs from the previous one.INSTRUCTIONS: Reset (block/unblock) the BTS.

FAULT NAME : Baseband Bus failureFAULT ID : 3020: EFaultId_BaseBandBusFailureMEANING : The BTS has detected an abnormal operation or a failure in the BTS internal baseband bus. The failure cannot be pointed to a specific unit/module but there are several possible fault sources.INSTRUCTIONS: Note: Perform the steps below in the listed order.

156 DN99580892



7653 CELL FAULTY

FlexiBTS: 1. Check other active BTS alarms and act accordingly. 2. Check the cables between the System Module and RF Module/Extension System 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 Extension System Module by blocking/unblocking it. c. Reset the master System Module. 4. Replace the alarming RF Module/Extension System Module. 5. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation, replace the alarming master System Module. UltraSite/EUBB: 1. Check other active BTS alarms and act accordingly. 2. Reset the alarming unit. 3. Check the cables in backplane. 4. Replace the alarming unit. FlexiLiteBTS: 1. Check other active BTS faults and act accordingly. 2. Reset the BTS by blocking/unblocking it. 3. Replace the Flexi Lite BTS.


FAULT NAME : Cell block rejected by RNC/Flexi Direct RNCFAULT ID : 96: EFaultId_InternalCellBlockedAlMEANING : The cell has been disabled due to BTS internal reasons, for example, if the RNC has rejected the normal cell blocking during the Intelligent Shutdown.INSTRUCTIONS: 1. Check the other active alarms. 2. Check the mains power supply.

FAULT NAME : Cell blockedFAULT ID : 49: EFaultId_CellBlockedAlMEANING : The user has blocked the cell with BTS Site Manager.INSTRUCTIONS: To cancel the alarm, unblock the cell.

DN99580892 157


7653 CELL FAULTY


FAULT NAME : Cell calibration failureFAULT ID : 117: EFaultId_InitCalibAlMEANING : TX power calibration failure: a CPICH setup failure, CPICH release failure, WTR power out of range failure, or general initial calibration failure.INSTRUCTIONS: 1. Check the commissioning (LCR cabling). 2. Block/unblock the alarming unit or the WPA connected to the alarming WTR. If there was an internal failure, the unit needs to be blocked/unblocked to initialize/configure it again. 3. Run the WCDMA BTS loop test with BTS Site Manager to check the WSM cabling. (Note! The loop test cannot be run if the cell is already blocked because of an alarm.) 4. Check the RF and WSM cabling (for example, in the case of an incorrect cabling). 5. If the reported severity is 7653 Cell faulty, replace the WTR, WPA, WSMs or WSP. If the reported severity is 7654 Cell operation degraded (most probably the WPA cannot deliver enough output power), replace the WPA.

FAULT NAME : Cell power monitoringFAULT ID : 125: EFaultId_CellPowerAlMEANING : The WPA/Radio output power has dropped. There is a fault in the downlink transmission path.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Block/unblock the WPA. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again. 2. Block/unblock the WTR belonging to the same LCR. 3. Check the RF TX cabling. 4. The fault might be in the WTR or WPA. FlexiBTS: 1. Block/unblock the RF Module. If there was an internal failure or sticking in the unit SW, the module needs to be blocked/unblocked to get it initialized/configured again. 2. Check the RF Module. 3. Replace the alarming module. FlexiLiteBTS: 1. Block/unblock the BTS. 2. If this does not help, replace the module.

FAULT NAME : Commissioned antenna configuration not supported by HWFAULT ID : 4060: EFaultId_CommissionedAntConfNotSupportedByHwAlMEANING : The configuration in the commissioning file is not supported by the RF Module.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears.

158 DN99580892



7653 CELL FAULTY

1. Check that the antenna configuration defined in the commissioning file is correct. 2. Replace the Radio Module with one that supports the used antenna configuration type.



FAULT NAME : Configuration error: <x>FAULTID : 3070: EFaultId_ConfigurationErrorMEANING : There is an incompatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch between the BTS configuration and the RNC/Flexi Direct RNC parameters.INSTRUCTIONS: Note: Perform the steps below in the listed order. 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 RNC/Flexi Direct RNC match the BTS HW configuration (for example frequency, power). 3. Check the RNC/Flexi Direct RNC BTS faults for the alarming local cell (LCR). 4. Recommission the BTS to ensure that all parameters are correctly configured.

DN99580892 159


7653 CELL FAULTY


FAULT NAME : Delayed cell shutdown alarmFAULT ID : 38: EFaultId_DelayedCellShutdownAlMEANING : BTS cells are disabled because the Battery backup alarm (ID=37) is active.INSTRUCTIONS: Check external Power Line conditions and make sure if there is external power provided to BTS.

FAULT NAME : Distributed site support not enabledFAULT ID : 4076: EFaultId_DistributedSiteSupportNotEnabledAlMEANING : Long fiber between FSM and furthest FR detected but feature status in SCF is FALSE. - Fiber length 0.2km - 15km: (actDistributedSite15 = False) - Fiber length 15km - 40km: (actDistributedSite40 = False)INSTRUCTIONS: Perform the steps below in the listed order until the fault disappears: 1. Either activate the required license for 15/40km distributed site or switch to shorter fiber between FSM and FR. 2. Restart FSM.


FAULT NAME : Filter unit operation failedFAULT ID : 1840: EFaultId_TuningFailureAl 1841: EFaultId_UnitFaultyAl

160 DN99580892



7653 CELL FAULTY

4043: EFaultId_TuningFrequencyOutOfRangeAlMEANING : A filter has not been able to tune on an appropriate sub-band properly (tuning failure), or another major failure has been detected by the filter (unit faulty).INSTRUCTIONS: In case of 4043:EFaultId_TuningFrequencyOutOfRangeAl: reconfigure the frequency settings. In case of 1840:EFaultId_TuningFailureAl, 1841:EFaultId_UnitFaultyAl: replace the filter unit.

FAULT NAME : Frame clock missingFAULT ID : 1903: EFaultId_FrFrameClockMissingMEANING : The System Module clock reference differs from the RF Module clock.INSTRUCTIONS: 1. Check cables between the System Module and RF Module. 2. Block/unblock the RF Module. 3. If that does not help, block/unblock the site. 4. If that does not help, replace the faulty unit.

FAULT NAME : Immediate cell shutdown alarmFAULT ID : 39: EFaultId_ImmediateCellShutdownAlMEANING : BTS cells are disabled because the Battery backup alarm (ID=37) is active.INSTRUCTIONS: Check external Power Line conditions and make sure if there is external power provided to BTS.

FAULT NAME : Incoherency in cell configurationFAULT ID : 1856: EFaultId_IncoherencyInCellConfigurationAlMEANING : Both sector types (A and B) are configured to the same RF Module in the two-carrier case.INSTRUCTIONS: Recommission the LCRs in a way that only one sector type is used in one RF Module.

FAULT NAME : Incoherency in cell configurationFAULT ID : 4000: EFaultId_IncoherencyInConfigurationMEANING : Too many LCRs are commissioned to one RF Module.INSTRUCTIONS: Recommission the BTS with a correct number of LCRs per RF Module.

FAULT NAME : Incoherency with RF ModulesFAULT ID : 1857: EFaultId_IncoherencyWithRFModulesAlMEANING : Incorrect cell configuration for RF Modules with different frequency. The same cell is configured for two RF Modules which are not at the same frequency.INSTRUCTIONS: 1. Check which Radio Module is at the faulty frequency. 2. Replace the incompatible Radio Module.

DN99580892 161


7653 CELL FAULTY




FAULT NAME : Incorrect Rx bandwidthFAULT ID : 4137: EFaultId_IncorrectRxBandwidthAlMEANING : Unsupported Rx carrier bandwidth has been assigned to LCR.INSTRUCTIONS: Check if the assigned Rx carrier bandwidth is supported by the given RF module and change it if needed. BTS reset is needed to take the changed Rx carrier bandwidth into use and to clear the fault.

FAULT NAME : Incorrect Tx bandwidthFAULT ID : 4138: EFaultId_IncorrectTxBandwidthAlMEANING : Unsupported Tx carrier bandwidth has been assigned to LCR.INSTRUCTIONS: Check if the assigned Tx carrier bandwidth is supported by the given RF module and change it if needed. BTS reset is needed to take the changed Tx carrier bandwidth into use and to clear the fault.

FAULT NAME : Incorrect carrier separationFAULT ID : 4139: EFaultId_IncorrectCarrierSeparationAlMEANING : Unsupported carrier separation in Dual-Cell configuration has been assigned.INSTRUCTIONS: Check if the assigned carrier separation is supported by the given RF module and change it if needed. BTS reset is needed to take the changed carrier separation

162 DN99580892



7653 CELL FAULTY

into use and to clear the fault.

FAULT NAME : Invalid carrier in WTRFAULT ID : 127: EFaultId_InvalidCarrierInWtrMEANING : There was an attempt to set the WTR to a channel not supported by the WTR (on a different frequency band).INSTRUCTIONS:1.Make sure that correct carrier numbers are in use in the RNC. 2. Commission the BTS with the correct WCDMA carrier values for the WTR.

FAULT NAME : Invalid frequency channel for the BTS HWFAULT ID : 1807: EFaultId_InvalidFrequencyChannelForBTSHWMEANING : The requested channel in the cell setup is not acceptable for the BTS hardware, because of an incorrect frequency band and/or a carrier spacing and/or the number of carriers.INSTRUCTIONS: Check the RNC cell parameters against the BTS HW configuration. The cell 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 type variations of the HW that might have limitations in the supported frequency range and bandwidth.

FAULT NAME : Low noise amplifier failureFAULT ID : 1839: EFaultId_LNAFailureAlMEANING : The Filter has detected a malfunction in the LNA unit.INSTRUCTIONS: Replace the alarming Radio module.

FAULT NAME : Missing RP3-01 linkFAULT ID : 4064: EFaultId_MissingRp301LinkAlMEANING : Not enough RP3-01 links connected between FSM and FR. Commissioned cells cannot be routed via existing RP3-01 links.INSTRUCTIONS: Note! Perform the steps below in the listed order. 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.

FAULT NAME : Missing secondary RP3-01 link

DN99580892 163


7653 CELL FAULTY


FAULT ID : 4111: EFaultId_MissingSecondaryRp3LinkAlMEANING : Secondary optical link break / hot removal detected during BTS runtime.INSTRUCTIONS: Note! Perform the steps below in the listed order. 1. Check whether 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. Replace the broken fiber link.

FAULT NAME : Module Clock FaultyFAULT ID : 1926: EFaultId_FrModuleClockFaultyMEANING : The RF Module lost the lock to the incoming clock.INSTRUCTIONS: 1. Check the cables between the System Module and RF Module. 2. Block/unblock the RF Module. 3. If that does not help, replace the alarming RF Module.

FAULT NAME : No WSM resourcesFAULT ID : 82: EFaultId_NoPrimaryWsmInSubRackAlMEANING : There should be two WSM units in the subrack 1. The WSM2 must always be connected when the WSM1 is used. If there is no connection to the WSM2, this fault is generated for the WSM1.INSTRUCTIONS: Insert the WSM2.

FAULT NAME : No connection to unitFAULT ID : 10: EFaultId_NoConnectionToUnitAl 4052: EFaultId_ConnectionToUnitLostAlMEANING : Connection to a unit that belongs to the BTS configuration has been lost or FSP cannot be detected.INSTRUCTIONS: FlexiBTS: 1. Make sure that the module is properly connected. If the module LED does not light up, the module is faulty. Check the alarming module. In case of two FSM-r3, check also SRIO cable connection between the system modules. 2. Check the fault history. FlexiLiteBTS: Check the fault history. UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Check the fault history, alarming unit and subrack. 2. If the SW has been updated recently, reload the SW. 3. If the WAF or WIC is alarming, try recommissioning the site. 4. Make sure that the unit is properly connected. If the unit LED does not light up, the unit is faulty. The fault might also be in the WPS unit or backplane. 5. Check the power cables, connectors, and the I2C bus

164 DN99580892



7653 CELL FAULTY

cables. Cancel alarms: Removing and inserting the WIC, WSM or primary WAM causes a site reset. If both WSCs are removed, inserting the first removed WSC back into the cabinet causes a site reset. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First, try to reset the site with the software. If that does not help, replace the alarming unit. If the WSMF unit is not present (replaced by WSMB)in BTS, alarming WSPFs are not used and should be removed from BTS. WSPFs can be removed, because without a WSMF unit BTS works as UltraSite not as EUBB.


FAULT NAME : Not enough WAF resources in LCRFAULT ID : 98: EFaultId_NotEnoughWafResourcesPerCellAlMEANING : There are not enough WAF units in a cell.INSTRUCTIONS: UltraSite, MetroSite and Triple-mode: 1. See the section No connection to unit in the troubleshooting instructions. 2. Increase the number of WAF units in the BTS. MetroSite 50: Change the WAF.

FAULT NAME : Optical interface faultyFAULT ID : 2000: EFaultId_OIC_TxAl 2001: EFaultId_OIC_PresAlMEANING : The Small Form Factor Pluggable (SFP) malfunction has occured or the SFP module is not physically present (no electrical connection exists). The SFP is a part of the fibre cable package.INSTRUCTIONS: 1. Check that the SFP is properly connected. 2. Replace the SFP module.

FAULT NAME : Post test failedFAULT ID : 1925: EFaultId_FrPostTestFailedMEANING : An RF Module power-on self-test failed at start-up.INSTRUCTIONS: Replace the faulty unit.

DN99580892 165


7653 CELL FAULTY



FAULT NAME : RF BB bus configuration errorFAULT ID : 1905: EFaultId_FrRfBbBusConfigErrorMEANING : The RF Module baseband bus is configured incorrectly.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, block/unblock the site. 3. If that does not help, replace the faulty unit.

FAULT NAME : RF BB bus synchronization errorFAULT ID : 1904: EFaultId_FrRfBbBusSynchErrorMEANING : The baseband bus between the System Module and the RF Module is out of synchronization.INSTRUCTIONS: Note: In case of old RF HW rel1, start directly from step 2. 1. Check cables between the System Module and the RF Module. 2. Block/unblocktheRF Module. 3. If that does not help, block/unblock the site. 4. If that does not help, replace the faulty unit

FAULT NAME : RF Module Filter input power missingFAULT ID : 1910: EFaultId_FrFilterInputPowerMissingMEANING : The RF Module filter has measured a TX power that is too low.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, replace the alarming RF Module.

166 DN99580892



7653 CELL FAULTY

FAULT NAME : RF Module OverheatFAULT ID : 1913: EFaultId_FrOverheatMEANING : The RF Module temperature is too high.INSTRUCTIONS: 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, replace the faulty unit.

FAULT NAME : RF Module blockedFAULT ID : 1931: EFaultId_FrBlockedMEANING : A shared (Medusa) FR is blocked.INSTRUCTIONS: Unblock the alarming module.

FAULT NAME : RF Module configuring failedFAULT ID : 1900: EFaultId_FrConfiguringFailedMEANING : The RF Module configuration failed because of a HW or SW fault.INSTRUCTIONS: Replace the alarming RF Module.

FAULT NAME : RF Module critical file not foundFAULT ID : 1901: EFaultId_FrCriticalFileNotFoundMEANING : A critical configuration file is missing from the RF Module.INSTRUCTIONS: Replace the alarming RF Module.


FAULT NAME : RF Module out of orderFAULT ID : 1912: EFaultId_FrOutOfOrderMEANING : The RF Module is out of order because of a software or hardware fault.INSTRUCTIONS: 1. Block/unblock the RF Module.

DN99580892 167


7653 CELL FAULTY


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

FAULT NAME : RF Module power output faultyFAULT ID : 1918: EFaultId_FrPowerOutputFaultMEANING : The Power Supply has detected an overvoltage, undervoltage, or overcurrent in the RF Module.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty unit.

FAULT NAME : RX out of orderFAULT ID : 1911: EFaultId_FrRxOutOfOrderMEANING : The RF Module RX RF synthesizer is not locked.INSTRUCTIONS: FlexiBTS: 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty unit. FlexiLiteBTS: 1. BTS reset. 2. If that does not help, replace the FlexiLiteBTS.

FAULT NAME : Radio resources switched offFAULT ID : 4057: EfaultId_RfSwitchedOffAlMEANING : The TX carriers served by the affected antenna lines are disabled, which causes degradation of operation of the related cells or their deactivation. This reduces the power transmitted by the Power Amplifier in Radio Module for the sake of protecting the Power Amplifier against HW failure caused by operation under excessive VSWR value conditions (antenna line impedance mismatch).INSTRUCTIONS: 1. Check the antenna lines: antennas, antenna cables, connector torques, and antenna line devices. 2. Check the antenna line (TX-cable-antenna) impedance matching.

FAULT NAME : Receiving failure in optical interfaceFAULT ID : 2002: EFaultId_OIC_RxAlMEANING : The incoming optical signal to the Small Form Factor Pluggable (SFP) is missing, too weak, or the fiber cable has been detached. The connection between the System Module and the RF Module (LTX, Antenna Filter, Antenna Line Device) or between the Master System Module and the Extension System Module is broken. That might concern primary or secondary link.INSTRUCTIONS: 1. Check the status of the module behind the faulty link (Power on, and so on). 2. Check the SFP 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.

168 DN99580892



7653 CELL FAULTY

3. Clean the connectors, test the fiber cable, and replace it if faulty. 4. If the steps above do not help, replace the module behind the faulty link.


FAULT NAME : TX out of orderFAULT ID : 1907: EFaultId_FrTxOutOfOrderMEANING : The RF Module TX path is not usable.INSTRUCTIONS: FlexiBTS: 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty unit. FlexiLiteBTS: 1. Reset BTS. 2. If that does not help, replace the FlexiLiteBTS.

FAULT NAME : TX output power measurement faultFAULT ID : 103: EFaultId_MeasurementAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: The WTR or WPA/WMP/WOU output power measurement has failed. FlexiBTS: The RF Module output power measurement has failed.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Block/unblock the alarming unit. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again. 2. Check the units and the RF cabling between the WPA/WMP/WOU and WTR units. FlexiBTS: 1. Reset the alarming RF Module with the block/unblock function. If there was an internal failure or sticking in the unit SW, the Module needs to be blocked/unblocked to get it initialized/configured again. 2. Check the cables between the System Module and RF Module. 3. If that does not help, replace the faulty RF Module.

DN99580892 169


7653 CELL FAULTY


FAULT NAME : Telecom configuration failureFAULT ID : 109: EFaultId_TcomSlaveRegAl 110: EFaultId_UnitRnwConfigAl 111: EFaultId_TcomSlaveConfigAl 119: EFaultId_WspAllocationAlMEANING : Telecom slave configuration or registration failure. Unit RNW configuration failure. Telecom RNW reconfiguration failure. FlexiBTS: - FSP unit to FCM allocation failure - Faraday unit to FSP allocation failure Note that depending on the fault source, unit status might relate either to the state of particular carrier resource on FR module or FSP board on FCM, and may not be in line with the state of source HW unit. Or UltraSite, MetroSite, MetroSite 50, Triple-mode: WSP unit to WAM allocation failure. UltraSite/EUBB: Faraday unit to WSPF allocation failure.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: Block/unblock the alarming unit. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again. UltraSite/EUBB: If the alarming unit is WSPF, block/unblock the EUBB subrack. FlexiBTS: If there was an internal failure, in the case of an FR, the module needs to be blocked/unblocked to get it initialized/configured again. FlexiBTS Rel2: If the alarming unit is FSPC, block/unblock the alarming module.

FAULT NAME : Temperature alarmFAULT ID : 3040: EFaultId_TemperatureAlarmMEANING : The internal temperature of the RF Module or System Module exceeds the threshold value, or the ambient temperature of the module(s) is beyond the specified limits.INSTRUCTIONS: Note: Perform the steps below in the listed order. 1. Check 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/unit by blocking/unblocking

170 DN99580892



7653 CELL FAULTY

it. 4. Replace the alarming module/unit.

FAULT NAME : Temperature too low (heating ongoing)FAULT ID : 1922: EFaultId_FrTemperatureTooLowMEANING : During RF startup: the temperature inside the RF Module is too low. Heating of module is ongoing. Wait until the alarm is canceled. This might take up to 30 minutes. During RF runtime: the temperature inside the RF module is too low. A problem may occur.INSTRUCTIONS: During RF startup only: 1. Heating of module is ongoing. Wait until the alarm is canceled. This might take up to 30 minutes. 2. If that does not help, block/unblock the RF Module. 3. If that does not help, replace the alarming RF Module.


FAULT NAME : Too many LCGs for HW to supportFAULT ID : 4004: EFaultId_TooManyLCGForHwAlMEANING : There is not enough HW capacity to support the commissioned number of Local Cell Groups (LCG).INSTRUCTIONS: Re-commission the BTS with the correct number of LCGs.

FAULT NAME : Too many carriers allocated for LPAFAULT ID : 99: EFaultId_TooManyCarriersPerWpaAlMEANING : Too many carriers have been allocated to the WPA/WMP.INSTRUCTIONS: Remove the additional carrier in the Reconfiguration commissioning.

FAULT NAME : Unit (module) dangerously overheatingFAULT ID : 1937: EFaultId_FrDangerouslyOverheatMEANING : Validated sensor temperature is greater than or equal to the predefined value on unit property file.INSTRUCTIONS: 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, replace the faulty unit.

FAULT NAME : Unit SW download failedFAULT ID : 6: EFaultId_SwDownloadAlMEANING : Software update to a unit/subunit or module has failed. UltraSite, MetroSite: The fault can also be caused by

DN99580892 171


7653 CELL FAULTY


disconnected CIF bus cables.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Download the BTS SW again. 2. If the alarming unit is WSP, block/unblock the WSP. 3. If the alarming unit is WAM or WPA, reset the BTS. 4. If that does not help, replace the alarming unit. FlexiBTS: 1. Download the BTS SW again. 2. FCM: Reset the BTS. 3. If Step 2 does not help, replace the alarming module. FlexiLiteBTS: 1. Download the BTS SW again. 2. Reset the BTS. 3. If Step 2 does not help, replace the Flexi Lite BTS.


FAULT NAME : Unit initialization failureFAULT ID : 12: EFaultId_TcomConfigAl 13: EFaultId_AtmConfigAl 15: EFaultId_InitializationAl 4040: EFaultId_InitFaultManAlMEANING : A unit/module or an IP address initialization has failed.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Block/unblock the alarming unit. 2. Check if the non-commissioned WAM is the Master WAM. If so, this causes the fault. Check the fault history to find out why the WAM switch-over occurred. 3. If the WAM is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 4. If step 3 does not help, replace the alarming unit. FlexiBTS: 1. Block/unblock the alarming module. If that does not help, replace the alarming module. 2. If the FCM/FCT is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the alarming module. FlexiLiteBTS: 1. Block/unblock the alarming module. If that does not help, replace the alarming module.

172 DN99580892



7653 CELL FAULTY

2. If the SCR is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the alarming module.




FAULT NAME : VSWR major alarmFAULT ID : 1837: EFaultId_VSWRMajorAlMEANING : VSWR value exceeds the defined level. The antenna line is mismatched or damaged.INSTRUCTIONS: 1. Check the antenna cables, connectors, antenna, and possible antenna line devices. 2. Check the antenna line (TX-cable-antenna) impedance matching.

FAULT NAME : WAF low noise amplifier faultyFAULT ID : 800: EFaultId_Lna1Al 801: EFaultId_Lna2Al 805: EFaultId_Lna3Al

DN99580892 173


7653 CELL FAULTY


806: EFaultId_Lna4Al 810: EFaultId_Lna5Al 811: EFaultId_Lna6AlMEANING : One of the two RX pre-amplifiers (one in the main branch and the other in the diversity branch) is faulty. The LED indicates the faulty unit. MetroSite 50: One, some, or all of the RX pre-amplifiers (max 6) are faulty. The LED indicates the faulty unit(s).INSTRUCTIONS: 1. Block/unblock the WAF unit. This is most likely a HW fault, but blocking/unblocking the unit ensures that before a site visit. 2. If that does not help, replace the alarming unit.

FAULT NAME : WPA power level changedFAULT ID : 57: EFaultId_WpaPowerLevelChangedAlMEANING : The power level of a replaced WPA unit differs from the original WPA unit.INSTRUCTIONS: If the WPA is accidently changed to a different power level type of WPA, replace the WPA unit to the correct power level type of WPA.

FAULT NAME : WSM RR-Bus errorFAULT ID : 1189: EFaultId_Rr0_0ParityErr2 1191: EFaultId_Rr0_0SyncErr2 1193: EFaultId_Rr0_1ParityErr2 1195: EFaultId_Rr0_1SyncErr2 1197: EFaultId_Rr1_0ParityErr2 1199: EFaultId_Rr1_0SyncErr2 1201: EFaultId_Rr1_1ParityErr2 1203: EFaultId_Rr1_1SyncErr2MEANING : The signal is transported from the WTR to the WSP via the WSM. This alarm is generated when the WSM/WMC unit detects errors in the incoming RR bus from the WTR unit. The reason for the failure is probably the WTR or WSM/WMC unit. The unit may have been installed incorrectly or the backplane cabling is faulty.INSTRUCTIONS: 1. Run the WCDMA BTS loop test. 2. Replace the units indicated in the alarm one by one and check whether the problem is cleared. 3. Check the backplane cables and connectors (see Troubleshooting instructions).


174 DN99580892




32 7654 CELL OPERATION DEGRADEDMeaning

A major fault (or faults) has occurred in a unit/module (orunits/modules) that belong to the sector indicated in the alarm.




2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number


InstructionsVerify the configuration of a BTS by checking thecommissioning, cabling and correct installation of theunits/modules at the BTS. Make sure the environment doesnot cause the fault.Before a unit/module is replaced at the BTS, the siteshould be reset to recover from any temporary faults whichmight have caused the malfunctioning of the unit/module.When an active alarm is a 'Start' alarm, a site reset isrequired to cancel the alarm. If the site reset or moduleblock/unblock does not help, replace the faulty unit/module(see the source of the alarm and instructions fields of thecorresponding alarms).Below is the list of BTS fault(s) which might have causedthis alarm in BTS WN 8.0 release. In case of earlier SWrelease and in case you need more detailed faultdescriptions refer to WCDMA RAN and Flexi Direct SystemLibraries. The BTS fault descriptions are also included inBTS SW release documentation. If that does not help,

DN99580892 175





FAULT NAME : 10b8b coding error in Optical Interface device <opt link/RP3>FAULT ID : 2004: EFaultId_OIC_LVDSRecAlMEANING : The fiber cable has interference; the data becomes faulty. A physical connection failure between the optical interface and the summing function (caused by bad circuit joints, for example).INSTRUCTIONS: 1. 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 is causing the alarm. 3. If the System Module is the only source causing the alarm, or replacing the RF Module does not clear the fault situation, replace the System Module that is causing the alarm.

FAULT NAME : AIR major alarmFAULT ID : 1513: EFaultId_MajorAlMEANING : ARIO has detected a Major level alarm. Some ARIO alarms can be canceled without a reset but most ARIO alarms require the WOU block/unblock to cancel.INSTRUCTIONS: 1. Check the WOU or WRUs. 2. Use the ARIO Local Management Tool and the Advanced Indoor Radio user documentation to diagnose the cause of the error.

FAULT NAME : AIR minor alarmFAULT ID : 1514: EFaultId_MinorAlMEANING : ARIO has detected a Minor level alarm. Some ARIO alarms can be canceled without a reset but most ARIO alarms require the WOU block/unblock to cancel.INSTRUCTIONS: Check the WOU or WRUs. Use the ARIO Local Management Tool and the Advanced Indoor Radio user documentation to diagnose the cause of the error.

FAULT NAME : Antenna Line Device failureFAULT ID : 3100: EFaultId_AntennaLineFailureMEANING : The System Module or the device itself has detected an abnormal operation or a failure in the antenna line device.INSTRUCTIONS: Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the antenna line and antenna line devices. Make sure that the antenna line connectors are in the right torque. 2. Reset the alarming RF module by blocking/unblocking it.

176 DN99580892




3. Replace the faulty parts and/or devices along the antenna line. 4. Replace the RF Module.

FAULT NAME : Antenna line device HW failureFAULT ID : 1847: EFaultId_HardwareErrorAlMEANING : A hardware failure detected by an antenna line device. Usually this is a permanent fault (the hardware is broken).INSTRUCTIONS: 1. Block/unblock the Radio module to give a power-off reset to the antenna line devices. 2. If that does not help, replace the antenna line device.

FAULT NAME : Antenna line device configuration failureFAULT ID : 1848: EFaultId_WorkingSoftwareMissingAl 1888: EFaultId_AlConfigurationFailureAlMEANING : An antenna line or antenna line device is not properly configured.INSTRUCTIONS: 1. Update the proper SW to the device. 2. Check/correct the antenna line configuration. 3. If that does not help, replace the antenna line device.

FAULT NAME : Antenna line failureFAULT ID : 1836: EFaultId_ALOvercurrentAlMEANING : Radio Module (60W RRH) or Filter (all others) has detected overcurrent on the antenna line. The antenna line might be damaged (short circuit), or some antenna line device is causing overload. All antenna line devices powered by the antenna line are out of order.INSTRUCTIONS: 1. Check the antenna line and antenna line devices. Fix or replace the faulty parts/devices. 2. Alarm is canceled only at RF Module reset or BTS reset.

FAULT NAME : Antenna line operation degradedFAULT ID : 4046: EFaultId_AntennaLineDegradedAlMEANING : An alarm message has been received from the antenna line device. The antenna line operation is degraded.INSTRUCTIONS: 1. Check the antenna line and antenna line device that causes the alarm. 2. Fix or replace the faulty parts/devices.

FAULT NAME : Antenna1 connection faultFAULT ID : 804: EFaultId_Ant1Al 809: EFaultId_Ant2Al 814: EFaultId_Ant3AlMEANING : The BIAS-T has detected that the reflected TX power from

DN99580892 177




the antenna has increased. The antenna cable between the WAF and MHA is faulty or the antenna is faulty. The BIAS-T may be faulty.INSTRUCTIONS: 1. Check the bias-T and MHA commissioning. 2. Block/unblock the WAF unit (check if the alarm reappears after 5 minutes). 3. Check the antenna line (see Troubleshooting instructions). 4. Check the PITA cable connection (RJ45). a. Check the voltage (see connector pins in Troubleshooting instructions). b. Check the right connection (see User Manual). c. Check by cross connecting RJ45 cables between other sectors.

FAULT NAME : BTS Config error (Different WTR variants cannot coexist in cell)FAULT ID : 56: EFaultId_WtraWtrbVersionConflictInCellAlMEANING : There are different WTR variants in the same cell.INSTRUCTIONS: Replace the conflicting WTR unit with a compatible unit.

FAULT NAME : BTS SW download or activation failedFAULT ID : 29: EFaultId_FileCorruptionAl 30: EFaultId_SwUpdateAlMEANING : The SW update to the BTS has failed. The error can be caused by a unit reset during the SW update, a hardware problem in the unit or cabinet, or a corrupted flash file system.INSTRUCTIONS: FlexiBTS: 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. FlexiLiteBTS: 1. Retry the SW update. 2. If other flash memory-related faults are active for the Flexi Lite BTS at the same time, replace the Flexi Lite BTS.

FAULT NAME : BTS config error (WSM missing from RF subrack)FAULT ID : 62: EFaultId_NoWsmForWtrInSubrackAlMEANING : There is no WSM in commissioned RF subrack.INSTRUCTIONS: Add WSM capacity to the subrack.

FAULT NAME : BTS config error (incorrect carrier candidates)FAULT ID : 1808: EFaultId_IncorrectCarrierCandidateAl 1864: EFaultId_BTSConfigErrorAl

178 DN99580892




MEANING : Carrier candidates are commissioned for each cell (not WTR/LTX specific).INSTRUCTIONS: Recommission (Reconfiguration commissioning) the BTS with the correct carrier candidate values.


FAULT NAME : BTS internal SW management problemFAULT ID : 3090: EFaultId_BtsInternalSwManagementProblemMEANING : A software update to a unit/module or subassembly has failed, or a corrupted SW file has been detected in the FLASH.INSTRUCTIONS: Note: Perform the steps below in the listed order. FlexiBTS: 1. Check other active BTS faults. If the ROM disk is corrupted, change the alarming module. 2. Reset the RF Module and/or FBIA and/or System Module, depending on the alarm source: a. Reset the RF Module by blocking/unblocking it. b. Reset the FBIA by blocking/unblocking it. c. Reset the System Module. 3. Update and activate the SW to the BTS. 4. Check the SW files.

DN99580892 179




5. Replace the alarming module/unit. UltraSite/EUBB: 1. Check other active BTS faults. If the ROM disk is corrupted, change the alarming unit. 2. Reset the alarming unit. 3. Update and activate the SW to the BTS. 4. Check the SW files. 5. Replace the alarming unit. FlexiLiteBTS: 1. Reset the and/or DSP and/or CC&T, depending on the alarm source. 2. Update and activate the SW to the BTS. 3. Check the SW files. 4. Replace the alarming Flexi Lite BTS.

FAULT NAME : Baseband Bus failureFAULT ID : 3020: EFaultId_BaseBandBusFailureMEANING : The BTS has detected an abnormal operation or a failure in the BTS internal baseband bus. The failure cannot be pointed to a specific unit/module but there are several possible fault sources.INSTRUCTIONS: Note: Perform the steps below in the listed order. FlexiBTS: 1. Check other active BTS alarms and act accordingly. 2. Check the cables between the System Module and RF Module/Extension System 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 Extension System Module by blocking/unblocking it. c. Reset the master System Module. 4. Replace the alarming RF Module/Extension System Module. 5. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation, replace the alarming master System Module. UltraSite/EUBB: 1. Check other active BTS alarms and act accordingly. 2. Reset the alarming unit. 3. Check the cables in backplane. 4. Replace the alarming unit. FlexiLiteBTS: 1. Check other active BTS faults and act accordingly. 2. Reset the BTS by blocking/unblocking it. 3. Replace the Flexi Lite BTS.

FAULT NAME : Cell calibration failureFAULT ID : 117: EFaultId_InitCalibAlMEANING : TX power calibration failure: a CPICH setup failure, CPICH

180 DN99580892




release failure, WTR power out of range failure, or general initial calibration failure.INSTRUCTIONS: 1. Check the commissioning (LCR cabling). 2. Block/unblock the alarming unit or the WPA connected to the alarming WTR. If there was an internal failure, the unit needs to be blocked/unblocked to initialize/configure it again. 3. Run the WCDMA BTS loop test with BTS Site Manager to check the WSM cabling. (Note! The loop test cannot be run if the cell is already blocked because of an alarm.) 4. Check the RF and WSM cabling (for example, in the case of an incorrect cabling). 5. If the reported severity is 7653 Cell faulty, replace the WTR, WPA, WSMs or WSP. If the reported severity is 7654 Cell operation degraded (most probably the WPA cannot deliver enough output power), replace the WPA.

FAULT NAME : Cell power monitoringFAULT ID : 125: EFaultId_CellPowerAlMEANING : The WPA/Radio output power has dropped. There is a fault in the downlink transmission path.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Block/unblock the WPA. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again. 2. Block/unblock the WTR belonging to the same LCR. 3. Check the RF TX cabling. 4. The fault might be in the WTR or WPA. FlexiBTS: 1. Block/unblock the RF Module. If there was an internal failure or sticking in the unit SW, the module needs to be blocked/unblocked to get it initialized/configured again. 2. Check the RF Module. 3. Replace the alarming module. FlexiLiteBTS: 1. Block/unblock the BTS. 2. If this does not help, replace the module.

FAULT NAME : Cell power parameter out of rangeFAULT ID : 126: EFaultId_CellPowerParameterOutOfRangeAlMEANING : The power values in the cell configuration data sent by the RNC are out of range.INSTRUCTIONS: Set the correct power values to the RNC.

FAULT NAME : Commissioning error: <x>FAULT ID : 3060: EFaultId_CommissioningErrorMEANING : Some of the commissioning parameters are either missing or

DN99580892 181




faulty. Or there is a mismatch between them.INSTRUCTIONS: Note: Perform the steps below in the listed order. 1. Check the commissioning parameters with the BTS Site Manager Commissioning Wizard. 2. Load the correct commissioning file to the BTS.


FAULT NAME : Configuration error: <x>FAULT ID : 3070: EFaultId_ConfigurationErrorMEANING : There is an incompatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch between the BTS configuration and the RNC/Flexi Direct RNC parameters.INSTRUCTIONS: Note: Perform the steps below in the listed order. 1. Check the installedHW/SWversion compatibility and the HW compatibility with the current BTS configuration. 2. Check that the BTS cell parameters from the RNC/Flexi Direct RNC match the BTS HW configuration (for example frequency, power). 3. Check the RNC/Flexi Direct RNC BTS faults for the alarming local cell (LCR). 4. Recommission the BTS to ensure that all parameters are correctly configured.

FAULT NAME : Configuration file corruptedFAULT ID : 1924: EFaultId_FrConfigurationFileCorruptedMEANING : The RF Module SW detected conflicting or corrupted configuration data.INSTRUCTIONS: 1. Block/unblock the RF Module 2. If that does not help, replace the alarming RF Module.

182 DN99580892




FAULT NAME : Diversity antenna line faultFAULT ID : 803: EFaultId_Mha2Al 808: EFaultId_Mha4Al 813: EFaultId_Mha6AlMEANING : The operating voltage of the Mast Head Amplifier (MHA) is supplied through the BIAS-T from the WAF. The WAF monitors the consumption of the current and generates an alarm if it deviates from normal. The cable between the MHA and WAF is faulty, the Bias-T is faulty, the MHA is faulty, another antenna line device between the MHA and WAF is faulty, or the MHA does not exist.INSTRUCTIONS: 1. Check the MHA commissioning parameters. 2. Block/unblock the related WAF. 3. Check the RF cabling and Bias-T. 4. The fault can be in the WAF, Bias-T or MHA (see Troubleshooting instructions).

FAULT NAME : FPGA SW update failedFAULT ID : 1928: EFaultId_FrFpgaSwUpdateFailedMEANING : The FPGA software update has failed.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, replace the alarming RF Module.


FAULT NAME : Filter unit operation failed

DN99580892 183




FAULT ID : 1840: EFaultId_TuningFailureAl 1841: EFaultId_UnitFaultyAl 4043: EFaultId_TuningFrequencyOutOfRangeAlMEANING : A filter has not been able to tune on an appropriate sub-band properly (tuning failure), or another major failure has been detected by the filter (unit faulty).INSTRUCTIONS: In case of 4043:EFaultId_TuningFrequencyOutOfRangeAl: reconfigure the frequency settings. In case of 1840:EFaultId_TuningFailureAl, 1841:EFaultId_UnitFaultyAl: replace the filter unit.

FAULT NAME : Flash operation failureFAULT ID : 214: EFaultId_FlashWrAl 215: EFaultId_FlashRdAl 216: EFaultId_FlashEraseAl 217: EFaultId_FlashDrvAl 218: EFaultId_FlashDbChksumAlMEANING : A flash memory operation failure. If this fault continuously appears, the flash chip may be broken.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Check the other active faults. If the /rom-disk is corrupted, change the alarming unit. 2. Block/unblock the alarming unit. There are no recovery actions and because of that the block/unblock can be attempted once. If that does not help, replace the alarming unit. FlexiBTS, FlexiLiteBTS: 1. Check the other active faults. If the /rom-disk is corrupted, change the alarming unit/module. 2. Block/unblock the alarming unit/module. There are no recovery actions and blocking/unblocking can be attempted once. If that does not help, replace the alarming unit/module.

FAULT NAME : Frame clock missingFAULT ID : 1903: EFaultId_FrFrameClockMissingMEANING : The System Module clock reference differs from the RF Module clock.INSTRUCTIONS: 1. Check cables between the System Module and RF Module. 2. Block/unblock the RF Module. 3. If that does not help, block/unblock the site. 4. If that does not help, replace the faulty unit.

FAULT NAME : Gain adjust alarmFAULT ID : 118: EFaultId_GainAdjustAlMEANING : The WTR cannot adjust the TX output power.INSTRUCTIONS: 1. Block/unblock the WTR. The unit needs to be

184 DN99580892




blocked/unblocked to get it initialised/configured again if there was an internal failure. 2. Check the WTR RF TX cabling. 3. If that does not help, replace the alarming unit.


FAULT NAME : Increased BER detected on the optical connection to Radio ModuleFAULT ID : 1955: EFaultId_IncrBerOnRp3MEANING : Increased bit error rate has been detected on the optical link to radio module which results in LCV errors in downlink baseband processing.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears: 1. Check the optical connection between system module and FR module. Check SFP module(s) and/or re-adjust 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 that does not help, replace the SFP module(s) in which the malfunctioning optical connection is terminated and/or replace the fiber.

FAULT NAME : Initial calibration not started because other cell not clearedFAULT ID : 120: EFaultId_InitCalibNotStartedAlMEANING : There is a shared WPA/WMP in the configuration (the WPA serves two cells). The first cell needs to be calibrated and therefore the second active cell needs to be cleared, but the clearing fails.INSTRUCTIONS: 1. Block/unblock the WPA/WMP unit belonging to the same LCR as the alarming WTR. The unit needs to be blocked/unblocked to get it initialized/configured again if there was an

DN99580892 185




internal failure. 2. Reset the site.

FAULT NAME : Low noise amplifier failureFAULT ID : 1839: EFaultId_LNAFailureAlMEANING : The Filter has detected a malfunction in the LNA unit.INSTRUCTIONS: Replace the alarming Radio module.

FAULT NAME : MHA unit operation failureFAULT ID : 1869: EFaultId_MinorTMAFaultAl 1870: EFaultId_MajorTMAFaultAlMEANING : A fault in the Masthead Amplifier (MHA) is detected. The fault reduces the gain performance or completely prevents the function of the MHA.INSTRUCTIONS: 1. Check the MHA type and configuration settings of BTS. If the given MHA requires DC voltage on BTS2 (Diversity) port, perform ALD commissioning properly and reset BTS. 2. Replace the alarming module.

FAULT NAME : Main antenna line faultFAULT ID : 802: EFaultId_Mha1Al 807: EFaultId_Mha3Al 812: EFaultId_Mha5AlMEANING : The operating voltage of the MHA is supplied through the Bias-T from the WAF. The WAF monitors the consumption of the current and generates an alarm if the consumption deviates from normal. The cable between the MHA and WAF is faulty, the Bias-T is faulty, the MHA is faulty, another antenna line device between the MHA and WAF is faulty, or the MHA does not exist.INSTRUCTIONS: 1. Check the MHA commissioning parameters. 2. Block/unblock the related WAF. 3. Check the RF cabling and Bias-T. 4. The fault can be in the WAF, Bias-T or MHA (see Troubleshooting instructions).

FAULT NAME : Mast Head Amplifier above current window fault, <line>FAULT ID : 1834: EFaultId_AboveCurrentWindowAlMEANING : The Masthead Amplifier (MHA) does not work properly. The received RF signal level is decreased. If both stages of the LNA on the uplink path fail, the MHA swithes the LNA to the by-pass mode. In the 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, the fault may affect both

186 DN99580892




main and diversity branches or just either of them.INSTRUCTIONS: 1. Check the antenna cables and connectors towards the MHA. Fix or replace the broken parts. 2. Restart the MHA by blocking and unblocking the Flexi Radio (FR) Module. Note! This operation affects all the antenna lines and cells related to the FR Module, not just the faulty one. If the alarm re-appears, replace the alarming module.

FAULT NAME : Mast Head Amplifier below current window fault, <line>FAULT ID : 1835: EFaultId_BelowCurrentWindowAlMEANING : The Masthead Amplifier (MHA) does not work properly. The received RF signal level is decreased. If both stages of the LNA on the uplink path fail, the MHA switches the LNA to the by-pass mode. In the 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, the fault may affect both main and diversity branches or either of them.INSTRUCTIONS: 1. Check the antenna cables and connectors towards the MHA. Fix or replace the broken parts. 2. Restart the MHA by blocking and unblocking the Flexi Radio (FR) Module. Note! This operation affects all the antenna lines and cells related to the FR Module, not just the faulty one. If the alarm re-appears, replace the alarming module.

FAULT NAME : Missing RP3-01 linkFAULT ID : 4064: EFaultId_MissingRp301LinkAlMEANING : Not enough RP3-01 links connected between FSM and FR. Commissioned cells cannot be routed via existing RP3-01 links.INSTRUCTIONS: Note! Perform the steps below in the listed order. 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.

FAULT NAME : Missing secondary RP3-01 linkFAULT ID : 4111: EFaultId_MissingSecondaryRp3LinkAlMEANING : Secondary optical link break / hot removal detected during BTS runtime.INSTRUCTIONS: Note! Perform the steps below in the listed order. 1. Check whether 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

DN99580892 187




connected and working. Replace the broken fiber link.

FAULT NAME : Module Clock FaultyFAULT ID : 1926: EFaultId_FrModuleClockFaultyMEANING : The RF Module lost the lock to the incoming clock.INSTRUCTIONS: 1. Check the cables between the System Module and RF Module. 2. Block/unblock the RF Module. 3. If that does not help, replace the alarming RF Module.


FAULT NAME : No feedback signalFAULT ID : 1920: EFaultId_FrNoFeedBackSignal

188 DN99580892




MEANING : The feedback signal to predistortion is too weak or missing. The TX performance is degraded.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, replace the alarming RF Module.

FAULT NAME : Not enough WAF resources in LCRFAULT ID : 98: EFaultId_NotEnoughWafResourcesPerCellAlMEANING : There are not enough WAF units in a cell.INSTRUCTIONS: UltraSite, MetroSite and Triple-mode: 1. See the section No connection to unit in the troubleshooting instructions. 2. Increase the number of WAF units in the BTS. MetroSite 50: Change the WAF.

FAULT NAME : Optical interface buffer alarmFAULT ID : 2051: EFaultId_Muksu_BufferAlMEANING : RP3 or Ethernet buffering is not working and the buffer becomes full. The optical devicemalfunctions.The fault may be generated because of synchronization problems or incorrect initialization.INSTRUCTIONS: 1. Depending on the interface, reset the connected module/unit behind the interface that causes the alarm by blocking/unblocking it. 2. If that does not clear the fault situation, replace the connected module/unit behind the interface causing the alarm. FlexiBTS: 3. If the System Module is the only alarm source, or replacing the RF Module/Extension System Module does not clear the fault situation, replace the System Module causing the alarm. UltraSite/EUBB: 3. If WSMF is the only alarm source, or replacing the connected module/unit does not clear the fault situation, replace the WSMF that causes the alarm.

FAULT NAME : Optical interface data/control/Ethernet buffer fullFAULT ID : 2006: EFaultId_OIC_DBRxFullAl 2007: EFaultId_OIC_DBTxFullAl 2008: EFaultId_OIC_CBRxFullAl 2009: EFaultId_OIC_CBTxFullAl 2010: EFaultId_OIC_EBFullAlMEANING : The RP3 or Ethernet buffering is not working and the buffer becomes full. The optical device is malfunctioning. The fault might be generated because of synchronization

DN99580892 189




problems or incorrect initialization.INSTRUCTIONS: Swap the alarming and working links. Then check where the alarm is reported. If the alarming link remains the same, replace the System Module. If the alarming link changes, replace the RF Module behind that link.

FAULT NAME : Optical interface faultyFAULT ID : 2000: EFaultId_OIC_TxAl 2001: EFaultId_OIC_PresAlMEANING : The Small Form Factor Pluggable (SFP) malfunction has occured or the SFP module is not physically present (no electrical connection exists). The SFP is a part of the fibre cable package.INSTRUCTIONS: 1. Check that the SFP is properly connected. 2. Replace the SFP module.

FAULT NAME : Pipe dangerously overheatingFAULT ID : 1938: EFaultId_FrPipeOverheatMEANING : Validated temperature of any PA sensor is greater than or equal to the predefined value on unit property file.INSTRUCTIONS: 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, replace the alarming RF Module.

FAULT NAME : Post test failedFAULT ID : 1925: EFaultId_FrPostTestFailedMEANING : An RF Module power-on self-test failed at start-up.INSTRUCTIONS: Replace the faulty unit.

FAULT NAME : R-bus errorFAULT ID : 425: EFaultId_RbusErrorMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The bus between the WSP and WTR does not work. The R-bus errors are probably caused by a faulty WSM or WTR. FlexiBTS: Error in the FSP or in the connection between the FSP and FCM.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. If the WSM/WMC also generates an alarm from a WTR unit, check the WTR and WSM cable. 2. If there are no active WSM/WMC alarms, the reason for the alarm is a faulty WSM/WMC or WSP. 3. Run a WCDMA BTS loop test to locate the faulty unit. 4. If the WSP is faulty, block/unblock it. 5. Replace the faulty unit. FlexiBTS: 1. Check the cabling between the System Module and RF Module.

190 DN99580892




2. Check the active RF Module alarms and act accordingly. 3. Replace the faulty module (System Module).

FAULT NAME : RET antenna control failureFAULT ID : 1842: EFaultId_MotorJamAl 1843: EFaultId_ActuatorJamAl 1844: EFaultId_NotCalibratedAl 1845: EFaultId_NotConfiguredAl 1846: EFaultId_ActuatorInterferenceAlMEANING : Antenna tilting is not possible or might function incorrectly.INSTRUCTIONS: 1. Recalibrate the RET antenna. 2. If that does not help, replace the RET unit.

FAULT NAME : RF BB bus configuration errorFAULT ID : 1905: EFaultId_FrRfBbBusConfigErrorMEANING : The RF Module baseband bus is configured incorrectly.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, block/unblock the site. 3. If that does not help, replace the faulty unit.

FAULT NAME : RF BB bus connection transmission errorFAULT ID : 1906: EFaultId_FrRfBbBusConnTransErrorMEANING : There is an error in the baseband or optical bus.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, block/unblock the site. 3. If that does not help, replace the alarming RF Module.

FAULT NAME : RF BB bus synchronization errorFAULT ID : 1904: EFaultId_FrRfBbBusSynchErrorMEANING : The baseband bus between the System Module and the RF Module is out of synchronization.INSTRUCTIONS: Note: In case of old RF HW rel1, start directly from step 2. 1. Check cables between the System Module and the RF Module. 2. Block/unblock the RF Module. 3. If that does not help, block/unblock the site. 4. If that does not help, replace the faulty unit

FAULT NAME : RF Module Filter input power missingFAULT ID : 1910: EFaultId_FrFilterInputPowerMissingMEANING : The RF Module filter has measured a TX power that is too low.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, replace the alarming RF Module.

DN99580892 191




FAULT NAME : RF Module OverheatFAULT ID : 1913: EFaultId_FrOverheatMEANING : The RF Module temperature is too high.INSTRUCTIONS: 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, replace the faulty unit.

FAULT NAME : RF Module blockedFAULT ID : 1931: EFaultId_FrBlockedMEANING : A shared (Medusa) FR is blocked.INSTRUCTIONS: Unblock the alarming module.

FAULT NAME : RF Module configuring failedFAULT ID : 1900: EFaultId_FrConfiguringFailedMEANING : The RF Module configuration failed because of a HW or SW fault.INSTRUCTIONS: Replace the alarming RF Module.

FAULT NAME : RF Module critical file not foundFAULT ID : 1901: EFaultId_FrCriticalFileNotFoundMEANING : A critical configuration file is missing from the RF Module.INSTRUCTIONS: Replace the alarming RF Module.


FAULT NAME : RF Module file not foundFAULT ID : 1902: EFaultId_FrFileNotFoundMEANING : The RF Module SW detected that a non-critical configuration file is missing.INSTRUCTIONS: 1.Block/unblock the RF Module.

192 DN99580892




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

FAULT NAME : RF Module gain adjusting failureFAULT ID : 1908: EFaultId_FrGainAdjustMEANING : The TX output power adjustment failed.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, replace the alarming RF Module.

FAULT NAME : RFModuleout of orderFAULT ID : 1912: EFaultId_FrOutOfOrderMEANING : The RF Module is out of order because of a software or hardware fault.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, replace the alarming RF Module.

FAULT NAME : RF Module power output faultyFAULT ID : 1918: EFaultId_FrPowerOutputFaultMEANING : The Power Supply has detected an overvoltage, undervoltage, or overcurrent in the RF Module.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty unit.

FAULT NAME : RF power decreasedFAULT ID : 1927: EFaultId_FrPowerDecreasedMEANING : The highest temperature exceeds the power decrease limit.INSTRUCTIONS: 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, block/unblock the alarming RF Module. 3. If that does not help, replace the alarming RF Module.

FAULT NAME : RP3 RX data frame timing errorFAULT ID : 5003: EFaultId_BofuRxAlignErrMEANING : The RP3 RX receiver has detected that the incoming data frame is outside of the alignment window.INSTRUCTIONS: 1. Reset BTS. 2. If resetting the BTS does not help, replace the WSMF.

FAULT NAME : RP3 uplink/downlink buffering errorFAULT ID : 5005: EFaultId_BofuUlBufErr 5006: EFaultId_BofuDlBufErrMEANING : Uplink buffering from Rbus to RP3, or vice versa downlink buffering from RP3 to Tbus does not work. Timing parameters

DN99580892 193




DELTA/RBUS_START_TIME, and/or PI/TBUS_START_TIME are incorrectly set.INSTRUCTIONS: 1. Reset BTS. 2. If resetting the BTS does not help, replace the WSMF.

FAULT NAME : RS485 IUANT port failureFAULT ID : 4069: EFaultId_Rs485PowerFailureAlMEANING : Radio Module or Filter (all others) has detected overcurrent on RS485 IUANT port. 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. Overcurrect was detected on RS485 IUANT port. Some antenna line device is causing overload or shortcut exists on the port. Antenna line devices powered by the rs485 IUANT port are out of order.INSTRUCTIONS: 1. 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.

FAULT NAME : RX out of orderFAULT ID : 1911: EFaultId_FrRxOutOfOrderMEANING : The RF Module RX RF synthesizer is not locked.INSTRUCTIONS: FlexiBTS: 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty unit. FlexiLiteBTS: 1. BTS reset. 2. If that does not help, replace the FlexiLiteBTS.

FAULT NAME : Radio resources switched offFAULT ID : 4057: EfaultId_RfSwitchedOffAlMEANING : The TX carriers served by the affected antenna lines are disabled, which causes degradation of operation of the related cells or their deactivation. This reduces the power transmitted by the Power Amplifier in Radio Module for the sake of protecting the Power Amplifier against HW failure caused by operation under excessive VSWR value conditions (antenna line impedance mismatch).INSTRUCTIONS: 1. Check the antenna lines: antennas, antenna cables, connector torques, and antenna line devices. 2. Check the antenna line (TX-cable-antenna) impedance matching.

FAULT NAME : Rbus data clock missing

194 DN99580892




FAULT ID : 5011: EFaultId_BofuRbusClockErrorMEANING : Data traffic from Rbus to RP3 in BOFU FPGA is malfunctioning because of errors in the Rbus synchronization clock.INSTRUCTIONS: 1. Reset BTS. 2. If resetting the BTS does not help, replace the WSMF.

FAULT NAME : Receiving failure in optical interfaceFAULT ID : 2002: EFaultId_OIC_RxAlMEANING : The incoming optical signal to the Small Form Factor Pluggable (SFP) is missing, too weak, or the fiber cable has been detached. The connection between the System Module and the RF Module (LTX, Antenna Filter, Antenna Line Device) or between the Master System Module and the Extension System Module is broken. That might concern primary or secondary link.INSTRUCTIONS: 1. Check the status of the module behind the faulty link (Power on, and so on). 2. Check the SFP 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 fiber cable, and replace it if faulty. 4. If the steps above do not help, replace the module behind the faulty link.

FAULT NAME : Rx signal level failureFAULT ID : 133: EFaultId_RxAntennaSignalLevelTooLowAl 134: EFaultId_RxAntennaSignalLevelDifferenceTooHighAlMEANING : The RX signal level is less than -112dBm or the difference between the maximum and minimum power levels of all RX antennas in the same cell and sector is more than the limit (EUBB/Nora 4 dB/Flexi value of LCELW-rxSignalComparations (in dBm)).INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Check BTS Site Manager for received signal levels to find out which RX is causing the problem. 2. If an MHA is alarming, replace the MHA unit and check if the RX signal level failure alarm is canceled. 3. If the alarm still exists, check the antenna cables. Swap the main and diversity RF cables between the WTR and WAF to see if the problem is in the WTR. If RX values do not change between the WTR inputs when swapping the cables, the fault is in the WTR unit. Change the WTR unit. 4. If the WTR is not faulty, the WAF, antenna feeder, or antenna is faulty on the antenna line which has the inadequate RX level. Check and replace the faulty equipment. FlexiBTS:

DN99580892 195




1. Check BTS Site Manager for the received signal levels to find out which RX is causing the problem. 2. If an MHA is alarming, replace the MHA unit and check if the RX signal level failure alarm is canceled. 3. If there are some Antenna line devices, check them. 4. Check the antenna cables. The radio module, antenna feeder, or antenna is faulty on the antenna line which has the inadequate RX level. Check and replace the faulty equipment. Note: The RX value in BTS Site Manager is refreshed at one minute intervals.

FAULT NAME : SW corruptedFAULT ID : 1850: EFaultId_SwCorruptedAl 4029: EFaultId_SwCorruptedPermanentAlMEANING : A corrupted SW file in the FLASH is detected. Unit cannot complete start-up.INSTRUCTIONS: Update the SW to the BTS.

FAULT NAME : TX out of orderFAULT ID : 1907: EFaultId_FrTxOutOfOrderMEANING : The RF Module TX path is not usable.INSTRUCTIONS: FlexiBTS: 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty unit. FlexiLiteBTS: 1. Reset BTS. 2. If that does not help, replace the FlexiLiteBTS.

FAULT NAME : TX output power measurement faultFAULT ID : 103: EFaultId_MeasurementAlMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: The WTR or WPA/WMP/WOU output power measurement has failed. FlexiBTS: The RF Module output power measurement has failed.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Block/unblock the alarming unit. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again. 2. Check the units and the RF cabling between the WPA/WMP/WOU and WTR units. FlexiBTS: 1. Reset the alarming RF Module with the block/unblock function. If there was an internal failure or sticking in

196 DN99580892




the unit SW, the Module needs to be blocked/unblocked to get it initialized/configured again. 2. Check the cables between the System Module and RF Module. 3. If that does not help, replace the faulty RF Module.

FAULT NAME : Telecom configuration failureFAULT ID : 109: EFaultId_TcomSlaveRegAl 110: EFaultId_UnitRnwConfigAl 111: EFaultId_TcomSlaveConfigAl 119: EFaultId_WspAllocationAlMEANING : Telecom slave configuration or registration failure. Unit RNW configuration failure. Telecom RNW reconfiguration failure. FlexiBTS: - FSP unit to FCM allocation failure - Faraday unit to FSP allocation failure Note that depending on the fault source, unit status might relate either to the state of particular carrier resource on FR module or FSP board on FCM, and may not be in line with the state of source HW unit. Or UltraSite, MetroSite, MetroSite 50, Triple-mode: WSP unit to WAM allocation failure. UltraSite/EUBB: Faraday unit to WSPF allocation failure.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: Block/unblock the alarming unit. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again. UltraSite/EUBB: If the alarming unit is WSPF, block/unblock the EUBB subrack. FlexiBTS: If there was an internal failure, in the case of an FR, the module needs to be blocked/unblocked to get it initialized/configured again. FlexiBTS Rel2: If the alarming unit is FSPC, block/unblock the alarming module.

FAULT NAME : Temperature alarmFAULT ID : 3040: EFaultId_TemperatureAlarmMEANING : The internal temperature of the RF Module or System Module exceeds the threshold value, or the ambient temperature of the module(s) is beyond the specified limits.INSTRUCTIONS: Note: Perform the steps below in the listed order. 1. Check 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

DN99580892 197




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/unit by blocking/unblocking it. 4. Replace the alarming module/unit.


FAULT NAME : Transmission quality deterioratedFAULT ID : 1921: EFaultId_FrTransmissionQualityDetoriatedMEANING : The TX signal adjustment fails.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, replace the alarming RF Module.

FAULT NAME : Under- / overrunning error in RP3 serializer clock crossing FIFOFAULT ID : 5002: EFaultId_BofuRxClkErrorMEANING : Either too large clock jitter between received signal and internal clock, or missing data input signal. The receiver is started up again.INSTRUCTIONS: 1. Reset BTS. 2. If resetting the BTS does not help, replace the WSMF.

FAULT NAME : Unit (module) dangerously overheatingFAULT ID : 1937: EFaultId_FrDangerouslyOverheatMEANING : Validated sensor temperature is greater than or equal to the predefined value on unit property file.INSTRUCTIONS: 1. Check the fans and ensure that the ambient temperature on the site is acceptable. 2. If that does not help, replace the faulty unit.

FAULT NAME : Unit SW download failedFAULT ID : 6: EFaultId_SwDownloadAlMEANING : Software update to a unit/subunit or module has failed. UltraSite, MetroSite: The fault can also be caused by disconnected CIF bus cables.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Download the BTS SW again. 2. If the alarming unit is WSP, block/unblock the WSP. 3. If the alarming unit is WAM or WPA, reset the BTS. 4. If that does not help, replace the alarming unit.

198 DN99580892




FlexiBTS: 1. Download the BTS SW again. 2. FCM: Reset the BTS. 3. If Step 2 does not help, replace the alarming module. FlexiLiteBTS: 1. Download the BTS SW again. 2. Reset the BTS. 3. If Step 2 does not help, replace the Flexi Lite BTS.


FAULT NAME : Unit initialization failureFAULT ID : 12: EFaultId_TcomConfigAl 13: EFaultId_AtmConfigAl 15: EFaultId_InitializationAl 4040: EFaultId_InitFaultManAlMEANING : A unit/module or an IP address initialization has failed.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: 1. Block/unblock the alarming unit. 2. Check if the non-commissioned WAM is the Master WAM. If so, this causes the fault. Check the fault history to find out why the WAM switch-over occurred. 3. If the WAM is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 4. If step 3 does not help, replace the alarming unit. FlexiBTS: 1. Block/unblock the alarming module. If that does not help, replace the alarming module. 2. If the FCM/FCT is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the alarming module. FlexiLiteBTS: 1. Block/unblock the alarming module. If that does not help, replace the alarming module. 2. If the SCR is the fault source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the alarming module.

FAULT NAME : Unit not supported by current BTS SW version

DN99580892 199




FAULT ID : 95: EFaultId_NotSupportedUnitMEANING : An unsupported unit has been detected in the BTS. Typically, this happens when a new unit version is installed and there is older BTS SW in use that does not support the new unit version.INSTRUCTIONS: FlexiBTS, UltraSite/EUBB:: 1. Upgrade the system module SW. 2. Replace the unit. FlexiLiteBTS: 1. Upgrade the Flexi Lite BTS software. 2. Replace the Flexi Lite BTS.

FAULTNAME : Unit unidentifiedFAULT ID : 1923: EFaultId_FrUnitUnidentifiedMEANING : The permanent memory in the module is corrupted and the module product code or serial number is missing, or the module product code is unknown.INSTRUCTIONS: 1. Block/unblock the RF Module. 2. If that does not help, replace the alarming RF Module.



FAULT NAME : VSWR major alarmFAULT ID : 1837: EFaultId_VSWRMajorAlMEANING : VSWR value exceeds the defined level. The antenna line is mismatched or damaged.INSTRUCTIONS: 1. Check the antenna cables, connectors, antenna, and possible antenna line devices. 2. Check the antenna line (TX-cable-antenna) impedance matching.

200 DN99580892




FAULT NAME : VSWR minor alarmFAULT ID : 1838: EFaultId_VSWRMinorAlMEANING : Radio Module (60W RRH)/the Filter (all others) has detected a VSWR value exceeding the defined level. The antenna line is slightly mismatched.INSTRUCTIONS: 1. Check the antenna cables, connectors, antenna and possible antenna line devices. 2. Check the antenna line (TX-cable-antenna) impedance matching.

FAULT NAME : WAF low noise amplifier faultyFAULT ID : 800: EFaultId_Lna1Al 801: EFaultId_Lna2Al 805: EFaultId_Lna3Al 806: EFaultId_Lna4Al 810: EFaultId_Lna5Al 811: EFaultId_Lna6AlMEANING : One of the two RX pre-amplifiers (one in the main branch and the other in the diversity branch) is faulty. The LED indicates the faulty unit. MetroSite 50: One, some, or all of the RX pre-amplifiers (max 6) are faulty. The LED indicates the faulty unit(s).INSTRUCTIONS: 1. Block/unblock the WAF unit. This is most likely a HW fault, but blocking/unblocking the unit ensures that before a site visit. 2. If that does not help, replace the alarming unit.

FAULT NAME : WSM RR-Bus errorFAULT ID : 1189: EFaultId_Rr0_0ParityErr2 1191: EFaultId_Rr0_0SyncErr2 1193: EFaultId_Rr0_1ParityErr2 1195: EFaultId_Rr0_1SyncErr2 1197: EFaultId_Rr1_0ParityErr2 1199: EFaultId_Rr1_0SyncErr2 1201: EFaultId_Rr1_1ParityErr2 1203: EFaultId_Rr1_1SyncErr2MEANING : The signal is transported from the WTR to the WSP via the WSM. This alarm is generated when the WSM/WMC unit detects errors in the incoming RR bus from the WTR unit. The reason for the failure is probably the WTR or WSM/WMC unit. The unit may have been installed incorrectly or the backplane cabling is faulty.INSTRUCTIONS: 1. Run the WCDMA BTS loop test. 2. Replace the units indicated in the alarm one by one and check whether the problem is cleared. 3. Check the backplane cables and connectors (see Troubleshooting instructions).

DN99580892 201






202 DN99580892




33 7655 CELL NOTIFICATIONMeaning

A minor fault (or faults) has occurred in a unit/module (orunits/modules) that belong to the sector indicated in the alarm.




2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number


InstructionsVerify the configuration of a BTS by checking thecommissioning, cabling and correct installation of theunits/modules at the BTS. Make sure the environment doesnot cause the fault.Before a unit/module is replaced at the BTS, the siteshould be reset to recover from any temporary faults whichmight have caused the malfunctioning of the unit/module.When an active alarm is a 'Start' alarm, a site reset isrequired to cancel the alarm. If the site reset or moduleblock/unblock does not help, replace the faulty unit/module(see the source of the alarm and instructions fields of thecorresponding alarms).Below is the list of BTS fault(s) which may have causedthis alarm in BTS WN 8.0 release. In case of earlier SWrelease and in case you need more detailed faultdescriptions refer to WCDMA RAN and Flexi Direct SystemLibraries. The BTS fault descriptions are also included inBTS SW release documentation. If that does not help,

DN99580892 203





FAULT NAME : Antenna Line Device Operation FailureFAULT ID : 1871: EFaultId_BusyAl 1872: EFaultId_FormatErrorAl 1873: EFaultId_UnsupportedProcedureAl 1874: EFaultId_OutOfRangeAlMEANING : The device is not working properly, the configuration is not valid, or a given parameter is incorrect.INSTRUCTIONS: 1. Check the functionality of the antenna line device. 2. Check the compatibility between the antenna line device and the BTS. 3. Check that the given parameters are in the valid range.


FAULT NAME : Antenna line device SW download failureFAULT ID : 4047: EFaultId_FileCrcErrorAl 4048: EFaultId_FileContentErrorAlMEANING : SW download to an antenna line device failed due to incorrect checksum or file format.INSTRUCTIONS: Note: Perform the steps below in the listed order until the BTS fault disappears. 1. Check the SW package. 2. Download SW to the antenna line device again.

FAULT NAME : BTS SW download or activation failedFAULT ID : 29: EFaultId_FileCorruptionAl 30: EFaultId_SwUpdateAlMEANING : The SW update to the BTS has failed. The error can be caused by a unit reset during the SW update, a hardware problem in the unit or cabinet, or a corrupted flash file system.INSTRUCTIONS: FlexiBTS: 1. Retry the SW update.

204 DN99580892




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

FAULT NAME : Baseband Bus failureFAULT ID : 3020: EFaultId_BaseBandBusFailureMEANING : The BTS has detected an abnormal operation or a failure in the BTS internal baseband bus. The failure cannot be pointed to a specific unit/module but there are several possible fault sources.INSTRUCTIONS: Note: Perform the steps below in the listed order. FlexiBTS: 1. Check other active BTS alarms and act accordingly. 2. Check the cables between the System Module and RF Module/Extension System 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 Extension System Module by blocking/unblocking it. c. Reset the master System Module. 4. Replace the alarming RF Module/Extension System Module. 5. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation, replace the alarming master System Module. UltraSite/EUBB: 1. Check other active BTS alarms and act accordingly. 2. Reset the alarming unit. 3. Check the cables in backplane. 4. Replace the alarming unit. FlexiLiteBTS: 1. Check other active BTS faults and act accordingly. 2. Reset the BTS by blocking/unblocking it. 3. Replace the Flexi Lite BTS.

FAULT NAME : Configuration error: <x>FAULT ID : 3070: EFaultId_ConfigurationErrorMEANING : There is an incompatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch between the BTS configuration and the RNC/Flexi Direct RNC parameters.INSTRUCTIONS: Note: Perform the steps below in the listed order. 1. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration.

DN99580892 205




2. Check that the BTS cell parameters from the RNC/Flexi Direct RNC match the BTS HW configuration (for example frequency, power). 3. Check the RNC/Flexi Direct RNC BTS faults for the alarming local cell (LCR). 4. Recommission the BTS to ensure that all parameters are correctly configured.

FAULT NAME : External Filter missing from LCRFAULT ID : 1892: EFaultID_ExternalFilterMissingFromLcrAlMEANING : An external filter is missing from the antenna line.INSTRUCTIONS: Install an external filter to the antenna line.

FAULT NAME : Fan failureFAULT ID : 3050: EFaultId_FanFailureMEANING : All the fans or more than one in the same fan group are rotating slower or faster than required, are not rotating at all, or the RPM information is not available for the fans. The reason for this fault can be too low supply voltage or a broken fan.INSTRUCTIONS: Note: Perform the steps below in the listed order. 1. Make sure that the fan is not blocked. 2. Check the fan and cabling. 3. Replace the faulty fan module.

FAULT NAME : File corrupted in SW downloadFAULT ID : 28: EFaultId_SwPackageAlMEANING : The download is corrupted or incorrectly formed SW.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Retry the SW update. 2. Fetch the BTS log files and check the download status from the BTS SWDLreport. FlexiBTS, FlexiLiteBTS: 1. Retry the SW update. 2. Save the snapshot and check the download status from the BTS SWDLreport in the snapshot file.

FAULT NAME : HSUPA capacity decreasedFAULT ID : 135: EFaultId_HsupaCapacityDecreasedAlMEANING : Runtime recovery, for example, has changed the HSUPA allocation so that the maximal HSUPA capacity cannot be achieved with the current allocation of baseband resources.INSTRUCTIONS: 1. If you want to increase the maximal HSUPA capacity while the alarm is active, lock and unlock all the cells from the alarming LCG. 2. Reset the BTS.

206 DN99580892





FAULT NAME : LCRs using same carrier frequencies mismatch in LCGsFAULT ID : 1865: EFaultId_LcrCarrierFreqLcgAlMEANING : Two cells with the same carrier belong to different local cell groups (LCGs). When baseband pooling is used, BTS baseband resources are divided between the different LCGs. Softer handover requires that cells with the same frequency in different sectors need to be assigned to the same LCG. This alarm is reported to BTS Site Manager only.INSTRUCTIONS: Check the RNC parameters for the BTS cells and change them, if needed. BTS reset is needed to take changed frequencies into use and to clear the fault.

FAULT NAME : RF module optical interface confguration failureFAULT ID : 1929: EFaultId_FrOptIfConfFailAlMEANING : The rel 2.0 or rel2.1 RF Module with SW before the implementation of RAN2312( Radio Interface Harmonization in Rel2.x ) is connected to the system module using optical interface 2 that is not according to the user guidance. It is advised to use optical interface 1.INSTRUCTIONS: Reconnect the alarming release 2 RF Module to optical interface 1.

FAULT NAME : Radio resources switched offFAULT ID : 4057: EfaultId_RfSwitchedOffAlMEANING : The TX carriers served by the affected antenna lines are disabled, which causes degradation of operation of the related cells or their deactivation. This reduces the power

DN99580892 207




transmitted by the Power Amplifier in Radio Module for the sake of protecting the Power Amplifier against HW failure caused by operation under excessive VSWR value conditions (antenna line impedance mismatch).INSTRUCTIONS: 1. Check the antenna lines: antennas, antenna cables, connector torques, and antenna line devices. 2. Check the antenna line (TX-cable-antenna) impedance matching.

FAULT NAME : Rbus synchronization errorFAULT ID : 5010: EFaultId_BofuRbusParityError 5012: EFaultId_BofuRbusSyncLostMEANING : Data traffic into Rbus uplink buffers is malfunctioning because of errors in the Rbus synchronization clock. Either Rbus synchronization pattern not found or parity errors found in pattern.INSTRUCTIONS: 1. Reset BTS. 2. If resetting the BTS does not help, replace the WSMF.

FAULT NAME : Read-only field encountered in the antenna line deviceFAULT ID : 4140: EFaultId_ReadOnlyAlMEANING : An attempt to modify a field value in Antenna Line Device failed because the field is read-only.INSTRUCTIONS: No action required from the operator.

FAULT NAME : TX failure in MIMOFAULT ID : 4003: EFaultId_TxFailureTurnMimoOffAlMEANING : Due to TX path failure MIMO (Multiple Input Multiple Output) functionality is not operational in the cell related to the faulty TX.INSTRUCTIONS: The affected cell starts working as a non-MIMO cell automatically. It does not require any manual change. The cell operates as a non-MIMO cell as long as the TX that is responsible for transmission of S-CPICH for the cell remains in "Faulty" state. Check the other active BTS faults and act accordingly.

FAULT NAME : Telecom cell enabling or disabling failedFAULT ID : 115: EFaultId_CellEnablingFailureAl 116: EFaultId_CellDisablingFailureAlMEANING : The cell enabling (the setup of CPICH and BCH) failed, or the cell disabling (the release of common channels) failed. The reason could be a hardware or a bus problem, or a lack of DSP or transport resources.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. Check other active alarms if the WSP capacity has been decreased.

208 DN99580892




2. Check if there are enough WSP units. FlexiBTS: 1. Check other active alarms. 2. Check the number of FSP units. UltraSite/EUBB: 1. Check other active alarms if the WSPF capacity has been decreased. 2. Check if there are enough WSPF units.

FAULT NAME : Temperature alarmFAULT ID : 3040: EFaultId_TemperatureAlarmMEANING : The internal temperature of the RF Module or System Module exceeds the threshold value, or the ambient temperature of the module(s) is beyond the specified limits.INSTRUCTIONS: Note: Perform the steps below in the listed order. 1. Check 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/unit by blocking/unblocking it. 4. Replace the alarming module/unit.

FAULT NAME : Temperature too low (heating ongoing)FAULT ID : 1922: EFaultId_FrTemperatureTooLowMEANING : During RF startup: the temperature inside the RF Module is too low. Heating of module is ongoing. Wait until the alarm is canceled. This might take up to 30 minutes. During RF runtime: the temperature inside the RF module is too low. A problem may occur.INSTRUCTIONS: During RF startup only: 1. Heating of module is ongoing. Wait until the alarm is canceled. This might take up to 30 minutes. 2. If that does not help, block/unblock the RF Module. 3. If that does not help, replace the alarming RF Module.

FAULT NAME : Unit (module) temperature is highFAULT ID : 1936: EFaultId_FrTempHighMEANING : Validated module temperature is higher than the predefined maximum allowed value.INSTRUCTIONS: Check the fans and ensure that the ambient temperature on the site is acceptable.

FAULT NAME : WSM failure

DN99580892 209




FAULT ID : 3001: EFaultId_EubbWsmAlMEANING : The BTS has detected an abnormal operation or a failure in the internal functionality of the WSMF unit.INSTRUCTIONS: Note: Perform the steps below in the listed order until the alarm disappears. 1. Check the alarm history, alarming unit and subrack. 2. Check that the unit is properly connected. If the unit LED does not light up, the unit is faulty. 3. Reset the BTS. 4. Replace the alarming unit.

FAULT NAME : WSMA RR-Bus errorFAULT ID : 1101: EFaultId_Wtr0ParityErr2 1103: EFaultId_Wtr0SyncErr2 1105: EFaultId_Wtr1ParityErr2 1107: EFaultId_Wtr1SyncErr2 1236: EFaultId_Rr2BusSyncErr2 1238: EFaultId_Rr2BusParityErr2 1240: EFaultId_Rr1BusSyncErr2 1242: EFaultId_Rr1BusParityErr2MEANING : The WSMA/WMC unit has detected errors in the incoming RR bus from the WTR unit. The WTR or WSMA/WMC unit may have been installed incorrectly or the backplane cabling is faulty. This alarm is generated only once and reported to BTS Manager only.INSTRUCTIONS: 1. Check the WSM and Spider cabling. 2. Replace the WTR and WSMA/WMC units indicated in the alarm one by one.

FAULT NAME : WSMA SR-Bus errorFAULT ID : 1109: EFaultId_WsmSrLeftParityErr2 1111: EFaultId_WsmSrLeftSyncErr2 1113: EFaultId_WsmSrRightParityErr2 1115: EFaultId_WsmSrRightSyncErr2MEANING : UltraSite: The WSM unit has detected errors in the incoming SR bus from the adjacent WSM unit. The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm. Triple-mode: The WSM has detected errors in the incoming SR bus from the WTR unit. The reason for the failure is the WSM or WTR unit, or the cable between the WSM front panel and the backplane. This alarm is generated only once and is reported to the BTS Site Manager only.

210 DN99580892




INSTRUCTIONS: 1. Check the WSM cabling. 2. Remove/reinsert the alarming unit. 3. Check the other WSM units. 4. Replace the WSM units (and if that does not help, also the WTR units) indicated in the alarm one by one and check whether the alarm is cleared.


DN99580892 211




34 7660 BASE STATION LICENCE EXPIREDMeaning

A licence fault (or faults) has occurred in the base station.




2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number

7 feature code


InstructionsSee the BTS faults documents in WCDMA RAN and Flexi Direct SystemLibraries for details about BTS license management.

FAULT NAME : Feature <featCode> expires on <expDate>, <featName>FAULT ID : 4002: EFaultId_LicenceExpiredMEANING : The feature is expiring: - in one month or one week if the fault severity is minor (working); - has already expired if the fault severity is major (degraded).INSTRUCTIONS: Activate the required license.

212 DN99580892





DN99580892 213




35 7661 BASE STATION LICENCE NOTIFICA-TIONMeaning

A licence fault (or faults) has occurred in the base station.




2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number

7 feature code


InstructionsSee the BTS faults documents in WCDMA RAN and Flexi Direct SystemLibraries for details about BTS licence management.

FAULT NAME : Failure in license activationFAULT ID : 4037: EFaultId_FailureInLicenceActivationAlMEANING : Generation of target Id failed and therefore correct validation of license files in BTS is not possible. BTSOM is restarted and in consequence during startup all license files are deleted from BTS. All optional features are either disabled or their capacity is reduced to the basic (not licensed) level.INSTRUCTIONS: Note! Perform the steps below in the listed order until the alarm disappears. 1. Reset the NetAct Licence Manager.

214 DN99580892




2. Reset the BTS. 3. Check the BTS license situation: the correct licenses have been purchased and installed.

FAULT NAME : Feature <featCode> expires on <expDate>, <featName>FAULT ID : 4002: EFaultId_LicenceExpiredMEANING : The feature is expiring: - in one month or one week if the fault severity is minor (working); - has already expired if the fault severity is major (degraded).INSTRUCTIONS: Activate the required license.

FAULT NAME : HW capacity too low for feature <licenseCode>, <licenseName>FAULT ID : 1814: EFaultId_HWCapacityTooLowAlMEANING : The HW capacity is too low to support all licenses of an optional feature.INSTRUCTIONS: Delete the licenses or insert new hardware.

FAULT NAME : Licence missing <licenceCode>, <licenceName>FAULT ID : 1885: EFaultId_MissingLicense AlMEANING : The BTS detected a resource requiring a license but no license exists or is available.INSTRUCTIONS: Activate the appropriate license or increase the license amount.

FAULT NAME : License missing <licenseCode>, <licenseName>FAULT ID : 1833: EFaultId_LicenceMissingAlMEANING : The BTS detected a resource needing a license. However, no license exists or is free.INSTRUCTIONS: An appropriate license should be provided to BTS.

FAULT NAME : TargetId verification failureFAULT ID : 4056: EFaultId_TargetIdVerificationFailureAlMEANING : NetAct Licence Manager did not respond to the verification request. TargetId verification was not possible.INSTRUCTIONS: Note! Perform the steps below in the listed order until the fault disappears. 1. Reset the NetAct Licence Manager. 2. Reset the BTS. 3. Check the BTS license situation: the correct licenses have been purchased and installed.

DN99580892 215





216 DN99580892




36 7665 BASE STATION TRANSMISSION ALARMMeaning

A transmission fault (or faults) has occurred in the BTS. This alarm isan encapsulation alarm that is used to transfer the Flexi TransportSubmodule (FTM) alarm data over the BTS O&M connection through RNC andOMS to NetAct. Encapsulation is used because the RNC alarm system cannotsupport the FTM alarms directly due to differences in the alarm structure.

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

Check the reason for the fault from the supplementary information fieldsand supplementary text field of the alarm. The actual documentation forthe encapsulated alarm can be found in the BTS faults documents inWCDMA RAN and Flexi Direct System Libraries.

The effect of the fault on the functioning of the network element dependson the fault description. For more information, see base station faultdescriptions in WCDMA RAN and Flexi Direct System Libraries.

Supplementary information fields1 probable cause reported by FTM

2 the managed object reported by FTM

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

InstructionsThis alarm is an encapsulation alarm for original FTMalarm.Follow up the instructions given in the BTS faultsdocuments in WCDMA RAN and Flexi Direct System Libraries for thealarm number shown in supplementary information field 3.

FAULT NAME : AIS (Administrative Unit) on unit $U, interface $IFFAULT ID : 61106: FTM_AIS_AUMEANING : Alarm indication signal on the Administrative Unit. The SDH interface receives an AU-AIS (Administrative Unit - Alarm Indication Signal). This signal is generated by an intermediate SDH device in the forward direction because it detects a problem in its receive signal. All other

DN99580892 217




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.INSTRUCTIONS: Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

FAULT NAME : AIS (Multiplexer Section) on unit $U, interface $IFFAULT ID : 61102: FTM_AIS_MSMEANING : Alarm indication signal on the Multiplexer Section. The SDH interface receives an MS-AIS (Multiplexer Section - Alarm Indication Signal). This signal is generated by an intermediate SDH 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.INSTRUCTIONS: Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

FAULT NAME : AIS on unit $U, interface $IFFAULT ID : 61151: FTM_AISMEANING : Alarm indication signal is received. This signal is generated by an intermediate PDH device in the forward direction because it detects a problem in its receive signal. All other transmission alarms related to this signal are suppressed. Probable cause: There is a transmission problem somewhere in the intermediate network and AIS is sent instead of user traffic.INSTRUCTIONS: Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

FAULT NAME : Auto-negotiation mismatch, on unit $U, Ethernet interface $IFFAULT ID : 61607: AUTO NEGO MIS MATCHMEANING : This alarm indicates that there is a mismatch between BTS configuration and auto-negotiation result.INSTRUCTIONS: Try with local management or site support equipment.

FAULT NAME : Automatic BTS Operator Certificate retrieval unsuccessful

218 DN99580892




FAULT ID : 61510: NO_CERTIFICATEMEANING : A requested certificate could not be retrieved from the certificate repository server (RA) or certificate authority (CA). A requested certificate could not be renewed from the certificate authority (CA).INSTRUCTIONS: Provide the certificate.

FAULT NAME : BFD $session down, egress, $sourceIP to $destinationIPFAULT ID : 61606: BFD down egressMEANING : The alarm is raised if the alarm is enabled, the BFD state is not AdminDown, the BFD packet from the far end contains the diagnostic code = 'Control Detection Time Expired' AND no ingress alarm is present.INSTRUCTIONS: Check the BFD configuration at local end.

FAULT NAME : BFD $session down, ingress, $sourceIP to $destinationIPFAULT ID : 61605: BFD DOWN IngressMEANING : The alarm is raised if the alarm is enabled, the BFD state is not AdminDown, and no BFD packet is received at the local end during the detection time.INSTRUCTIONS: 1. Check the network between both BFD peers for physical link failures or misconfigurations. 2. Check if the BFD functionality in the peer is switched on and that the configurations of the BFD peers match.

FAULT NAME : BFD group $bfdGrpId downFAULT ID : 61022: BFD DOWNMEANING : The alarm is raised if the BFD service is not available anymore for all sessions of the BFD group. The BFD failure for each session might be either in ingress or egress direction. In case only 1 BFD session is configured and activated for the BFD group, the alarm is raised, if BFD on this session fails in either ingress or egress direction.INSTRUCTIONS: 1) Check if the far end has BFD switched on. 2)Check cabling and network connections to the far end.

FAULT NAME : BTS reset requiredFAULT ID : 61010: FTM_BTS_RESET_REQUIREDMEANING : A change to the BTS IP settings has been received from TRS Manager. The user has to confirm the changes after the last BTS IP settings have been given. The confirmation is needed so that the BTS IP settings are taken in use through a BTS reset.INSTRUCTIONS: Confirm the changes when all the required BTS IP settings have been made.

DN99580892 219




FAULT NAME : CCM fault md $d level $ fault $f prio $p cause $cFAULT ID : 61410: Ethernet OAM CCM faultMEANING : The alarm is triggered whenever a service OAM error related to the transmission of Continuity Check Messages (CCM) persists on a given Ethernet interface over the period 2,5 s. The following alarms are defined: 1) XC_CCM_defect, priority 5 (highest priority): Maintenace Domain level mismatch or Maintenance Association identification mismatch. 2) Error_CCM, priority 4: Maintenance End Point identifier unknown, wrong CCM interval. 3) Remote_CCM_Defect, priority 3: at least one of the remote peers does not receive CCM from its peers, or local does not receive CCM from peer since 3.5 times the transmission period. MA includes multiple VLANs, CCMs shall be received for each VLAN separately. 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 detectedINSTRUCTIONS: 1) Check cabling. 2) Check CCM configuration at remote peer.

FAULT NAME : CES pseudowire $W down on unit $UFAULT ID : 61071: CES_PW_DOWNMEANING : The alarm is raised if the CES pseudowire is in 'Up' state, but the number of received packets in the CES pseudowire is less than 10 relative to the expected number of packets for 1 second. The alarm is not be raised, if the CES pseudowire is in 'Init' state.INSTRUCTIONS: 1. Check that the cables are connected to the correct connectors. 2. Check that the interface at the far-end interface is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms. 4. Check the configuration of the CES pseudowire.

FAULT NAME : CES pseudowire remote packet loss on wire $W on unit $UFAULT ID : 61072: CES_PW_Remote_Packet_Loss

220 DN99580892




MEANING : This alarm is raised if the packet loss condition for packets of the given CES pseudowire persists for more than 1second in ingress. The packet loss condition is defined as follows: The CES over PSN pseudowire function is capable to detect lost and misordered packets. The sequence number in the control word is used for these purposes. The CES over PSN pseudowire function shall reorder misordered packets. Misordered packets that cannot be reordered, shall be discarded and treated as lost.INSTRUCTIONS: 1. Check that the cables are connected to the correct connectors. 2. Check that the interface at the far-end interface is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms. 4. Check the configuration of the CES pseudowire.

FAULT NAME : CES pseudowire tunnel $T down on unit $UFAULT ID : 61070: CES_PWT_DOWNMEANING : This alarm is raised if a CES pseudowire tunnel is in 'Up' state, but no IP packets were received on the tunnel in the last second. The alarm is not raised in case the CES pseudowire tunnel is in 'Init' state. In case that all CES pseudowires of the tunnel are taken out of use by the operator, also no "PW tunnel down" alarm is raised even when the CES pseudowire tunnel is still configured.INSTRUCTIONS: 1. Check that the cables are connected to the correct connectors. 2. Check that the interface at the far-end interface is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms. 4. Check the configuration of the related CES pseudowires.

FAULT NAME : CRL update failure due to cause $CFAULT ID : 61074: CRL Update failureMEANING : This alarm is raised if the BTS cannot update the Certificate Revocation List (CRL) for one of the following reasons: - The LDAP binding fails. - The LDAP search is emtpy (no CRL found). / The LDAP search contains more

DN99580892 221




than 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.INSTRUCTIONS: Execute general configuration checks: - Configuration of CMP server IP address and port and DNS server IP address - Configuration of routing entries towards remote peers - Configuration of IPSec policies towards remote peers Check remote peers and intermediate network elements interconnections. Check the LDAP connection towards the Certificate Revocation List server. Check DNS names. Check the size of the file at the Certificate Revocation List server.

FAULT NAME : Config-abort state on unit $U, IMA Group $IMAGFAULT ID : 61178: FTM_IMA_CONFIG_ABORTEDMEANING : Configuration abort state. This alarm is raised when the far end tries to use unacceptable configuration parameters. All other transmission alarms related to this signal are suppressed. Probable cause: The IMA group configuration is wrong (for example, the IMA versions are incompatible).INSTRUCTIONS: Check that the configurations at the near end and far end fit together (for example, IMA version and frame length). Change the configuration, if necessary.

FAULT NAME : DHCP client timeout or NACK received on $IF $VIDFAULT ID : 61608: DHCP_CLIENT_TIMEOUTMEANING : This alarm is raised if there is no response from any DHCP server after 6 minutes or a NACK is received. The alarm clears when the correct DHCPOFFER is received. VID will be displayed in case of VLAN.INSTRUCTIONS: Check the DHCP server configuration in BTS. Check the physical connectivity between DHCP server and BTS/FTM. Check whether the IP address is already assigned to another NE.

FAULT NAME : DSCP $D signalled but not configuredFAULT ID : 61020: DSCP UNKNOWNMEANING : DSCP $D signalled but not configured. $D specifies the first mismatch DSCP value. The combination of RNC and NodeB is misconfigured with regard to quality of the service configurations.

222 DN99580892




INSTRUCTIONS: 1. Check the configured DSCP value ranges in the RNC. 2. Check the configured DSCP value ranges in the BTS. 3. Ensure that both match each other.

FAULT NAME : Dead Peer DetectedFAULT ID : 61030: FTM_DPDMEANING : A dead peer was detected in one of the IPsec associations of the FTM. Possibly - a cable is cut or there is no cable connected to the interface - the signal is excessively attenuated - the port at the connected far end node is switched offINSTRUCTIONS: 1. Check that the cables are connected to the correct connectors. 2. Check that the interface at the far-end interface is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms.

FAULT NAME : EBER on unit $U, interface $IFFAULT ID : 61104: FTM_EBERMEANING : 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 failedINSTRUCTIONS: 1. Clean the cables and connectors. 2. Check that the connectors are properly connected to the unit. 3. Check that the cable connected to the interface in question is not damaged and is within the specifications. 4. Follow the signal in the network and check whether any other alarms concerning the fault are on (such as Laser End of Life). If this is the case, follow the instructions for handling those alarms.

FAULT NAME : ETH AIS fault interface $IF level $l mac addr $xFAULT ID : 61411: Ethernet OAM ETH_AIS_faultMEANING : A Maintenance Endpoint (MEP) received a valid ETH-AIS frame. The alarm shows the following information: - Maintenance Interface - Maintenance Domain level at which the alarm was detected

DN99580892 223




- Source MAC address of the MEP.INSTRUCTIONS: 1) Check cabling. 2) Check configuration at remote peer.

FAULT NAME : FTM booted at $date due to $RCauseFAULT ID : 61006: FTM_RESETMEANING : The transport part of the WBTS has been reset.INSTRUCTIONS: N/A

FAULT NAME : Far end config-abort state on unit $U, IMA Group $IMAGFAULT ID : 61179: FTM_IMA_CONFIG_ABORTED_FEMEANING : Far end configuration abort state. This alarm is raised when the far end reports unacceptable configuration parameters. All other transmission alarms related to this signal are suppressed. Probable cause: The IMA group configuration is wrong (for example, the IMA versions are incompatible).INSTRUCTIONS: Check that the configurations at the near end and far end fit together (for example, IMA version and frame length). Change the configuration if necessary.

FAULT NAME : Far end group start-up on unit $U, IMA Group $IMAGFAULT ID : 61177: FTM_IMA_START_UP_FEMEANING : Farendgroup start-up. This alarm is raised when the far end indicates that it is in the start-up phase. The alarm is typically active only temporarily. Probable cause: The IMA group at the far end is not yet up and running.INSTRUCTIONS: If the alarm is on only temporarily, no action is needed. If the alarm stays active, check whether any other alarms related to this fault are on (such as problems on individual IMA links). If this is the case, follow the instructions for handling these alarms.

FAULT NAME : Far end insufficient links on unit $U, IMA Group $IMAGFAULT ID : 61181: FTM_IMA_INSUFFICIENT_LINKS_FEMEANING : Far end insufficient links. The far-end IMA group reports that there are less IMA links in the far-end IMA group than required by the parameter Minimum number of IMA links. Probable causes: - IMA links within the IMA group are out of order - there are not enough IMA links configured for the IMA group - the value for the parameter Minimum number of links is set to be too high

224 DN99580892




INSTRUCTIONS: 1. Check the individual IMA links in the IMA group for problems. If needed, correct them. 2. Configure additional IMA links to the IMA group. 3. If feasible, reduce the minimum number of IMA links in the IMA group. 4. Check that the configurations at the near end and far end fit together. Change the configurations if necessary.

FAULT NAME : Far-end receive link unusable on unit $U, interface $IFFAULT ID : 61176: FTM_IMA_RX_UNUSABLEMEANING : Far-end receive link unusable. The IMA link is not yet in an IMA group. The alarm is typically raised only temporarily during IMA configuration and disappears when the configuration has been completed. There are usually other IMA-related alarms active at the same time. Probable cause: IMA configuration is incomplete at the far-end interface.INSTRUCTIONS: Ensure that the far-end IMA link is configured to be part of an IMA group.

FAULT NAME : Far-end transmit link unusable on unit $U, interface $IFFAULT ID : 61175: FTM_IMA_FE_TX_UNUSABLEMEANING : Far-end transmit link unusable. The IMA link is not yet in an IMA group. The alarm is typically raised only temporarily during IMA configuration and disappears when the configuration has been completed. There are usually other IMA-related alarms active at the same time. Probable cause: IMA configuration is incomplete.INSTRUCTIONS: Ensure that the IMA link is configured to be part of an IMA group.

FAULT NAME : Five failed logins to FTM due to wrong credentials on if $IFFAULT ID : 61500: FTM_SECURITYMEANING : Five consecutive failed login attempts to the FTM have been performed due to wrong username or password. This Fault has to be generated for each affected interface as below. The interface names are (e.g. HTTP, XoH or NWI3UltraBTS only.INSTRUCTIONS: Check your username and password.

FAULT NAME : Group timing mismatch on unit $U, IMA Group $IMAGFAULT ID : 61183: FTM_IMA_GR_TIMING_MISMATCHMEANING : Group timing mismatch. The far-end transmit clock mode is different from the near-end transmit clock mode. The traffic of the IMA group does not function properly. The IMA group might not be capable of carrying traffic on

DN99580892 225




the IMA group referenced in the alarm text. Probable cause: Too large differential delay between the IMA links.INSTRUCTIONS: The IMA group reconfigures automatically. If the alarm remains active, do as follows: 1. Check the delay of the links. Special measurement equipment might be needed for this. Take appropriate actions to reduce the delay. 2. If the IMA link is used over a leased line, the problem might be located in the leased line network. In this case, the operator should be contacted.

FAULT NAME : IMA link out of delay synchronization on unit $U, interface $IFFAULT ID : 61171: FTM_IMA_LODSMEANING : Link out of delay synchronisation. A LODS defect is reported when the link differential delay between the link and the other links in the group is higher than the tolerable link differential delay. Probable causes: - the configuration of the IMA group is incomplete or faulty - there is disturbance on the line - the differential delay of the IMA links belonging to one IMA group is too highINSTRUCTIONS: Do as follows for the interface referenced in the alarm text: 1. Verify that the IMA configuration of the near end and far end is correct. 2. Check the physical line for errors. 3. Check the delay of the IMA link in question. If necessary, select another suitable link.

FAULT NAME : IMA remote failure indication on unit $U, interface $IFFAULT ID : 61172: FTM_IMA_RFIMEANING : Remote failure indication. An IMA-related remote defect has been detected. A Loss of IMA link (LIF) or Link out of delay synchronisation (LODS) alarm is active at the far end of the IMA link. Probable causes: - disturbance on the line - physical link defect - loss of IMA frame - loss of delay synchronisationINSTRUCTIONS: Follow the instructions for handling the alarms raised at the far end of the IMA link.

FAULT NAME : IP address mismatch in dhcp allocated address on $IF $VID

226 DN99580892




FAULT ID : 61609: DHCP_IP_ADDRESS_MISMATCHMEANING : BTS raises this alarm if IP address received from DHCP server is different from that configured for corresponding Transport network interface. The alarm is cleared when the correct IP address is received in DHCPACK. VID will be displayed in case of VLAN.INSTRUCTIONS: Check the DHCP server configuration in BTS. Check the physical connectivity between DHCP server and BTS/FTM.

FAULT NAME : IPCP FailureFAULT ID : 61250: FTM_IPCPMEANING : The IPCP statemachine is in the Closed or Initial state and cannot reach the Opened state within 100 milliseconds.INSTRUCTIONS: Check the configuration of the far end

FAULT NAME : Insufficient links on unit $U, IMA Group $IMAGFAULT ID : 61180: FTM_IMA_INSUFFICIENT_LINKSMEANING : Insufficient links. There are less operable IMA links in the IMA group than the minimum number of IMA links required. The IMA group referenced in the alarm text may not be able to carry all required traffic. Probable causes: - IMA links within the IMA group are out of order - there are not enough IMA links configured for the IMA group at the far end - the value for the parameter Minimum number of links is set to be too highINSTRUCTIONS: 1. Check the individual IMA links in the IMA group for problems. Correct them if necessary. 2. Configure additional IMA links to the IMA group. 3. If feasible, reduce the minimum number of IMA links in the IMA group. 4. Check that the configurations at near end and far end fit together. Change the configurations if necessary.

FAULT NAME : Interface under test on unit $U, interface $IF for $T minutesFAULT ID : 61040: FTM_IF_TESTMEANING : A loopback has been configured by a management application.INSTRUCTIONS: Switch the loopback off or wait for the timeout to expire. This opens the loop which cancels the alarm.

FAULTNAME : LCP Failure on Interface $IF

DN99580892 227




FAULT ID : 61251: FTM_LCPMEANING : The alarm is raised if the LCP state machine on port $P is in the Closed or Initial state and cannot reach the Opened state within 100 milliseconds.INSTRUCTIONS: Check the configuration and corresponding alarms on the far end.

FAULT NAME : LOCD on unit $U, interface $IFFAULT ID : 61057: FTM_LOCDMEANING : Loss of ATM cell delineation. The network interface receives frames whose ATM cells cannot be recognised. It is not possible to carry traffic on the interface referenced in the alarm text. Probable causes: - the far-end frames do not have ATM cell mapping - the far end does not insert idle cells - there are disturbances in the traffic of the physical transmission link in questionINSTRUCTIONS: 1. Ensure that the far end is using ATM cell mapping. 2. Check whether any other alarms concerning the fault are on. If this is the case, follow the instructions on handling those alarms. 3. If the alarm is on only temporarily, no action is needed.

FAULT NAME : LOF on unit $U, interface $IFFAULT ID : 61028: FTM_LOFMEANING : Loss of frame. It is not possible to carry traffic on the interface referenced in the alarm text. All other transmission alarms related to this signal are suppressed. Probable causes for STM-1/STS-3c interfaces: - the SDH/SONET interface receives frames that have an incorrect frame pattern (A1 and A2 bytes) - the configuration of the framing (STM-1 or STS-3c) on the far-end interface does not match the configuration on the interface referenced in the alarm text - too low an input level Probable cause for E1 interfaces: The interface at the far end is not configured to be a framed E1 interface. Probable cause for JT1 interfaces: The interface at the far end is not configured to be a JT1 interface.INSTRUCTIONS: E1 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.

228 DN99580892




FAULT NAME : LOMF on slot $U, interface $IFFAULT ID : 61150: FTM_LOMFMEANING : Loss of multiframe. The interface referenced in the alarm text has lost the multiframe alignment. Probable cause: the interface type has not been configured to meet the framing of the interface at the far end. For E1 interfaces, the configuration of the far-end node should be E1 Multiframe.INSTRUCTIONS: Check that the configured interface type matches the configured interface type of the far end. If this is the case, the problem is somewhere in the transmission network.

FAULT NAME : LOP (Administrative Unit) on unit $U, interface $IFFAULT ID : 61105: FTM_LOP_AUMEANING : Loss of Pointer for the Administrative Unit. This alarm occurs when the SDH interface receives frames that have an incorrect Administrative Unit (AU) pointer. All other transmission alarms related to this administrative unit are suppressed. Probable cause: there are disturbances in the traffic on the link in question.INSTRUCTIONS: Check the intermediate VC-12 transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

FAULT NAME : LOS on unit $U, Ethernet interface $IFFAULT ID : 61029: FTM_LOSMEANING : No signal is received on the interface referenced in the alarm text. All other transmission alarms related to this signal are suppressed. Probable causes for PDH 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 - transmit and receive cables are mixed up 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 offINSTRUCTIONS: 1. Check that the cables are connected to the correct connectors. 2. Check that the interface at the far-end interface is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those

DN99580892 229




alarms. 4. To verify that the hardware of the interface unit works correctly, connect a loop cable and check whether the alarm disappears.

FAULT NAME : Licence missing <licenceCode>, <licenceName>FAULT ID : 61400: FTM_LICENSE_MISSINGMEANING : The feature referenced in the alarm text has been configured without installing a valid license. Probable cause: A valid license that would allow the operation of the feature is not available in the WBTS. This BTS fault can be displayed in the followings variants: License Missing 0000000598, E1, T1, JT1 interface License Missing 0000000616, IMA License Missing 0000000767, UBR+ for Iub User Plane License Missing 0000000768, ATM over Ethernet License Missing 0000001191, Timing Over Packet License Missing 0000001687, 2nd Flexbus interface License Missing 0000001688, Collocation Flexbus interface License Missing 0000001689, Flexbus Ethernet interface License Missing 0000001515, Synchronous Ethernet License Missing 0000001788, QoS aware Ethernet switching License Missing 0000001847, IP over ML-PPP on E1/T1/JT1 IF License Missing 0000001850, Ethernet OAM License Missing 0000001849, Fast IP Rerouting and OSPF License Missing 0000001905, IP Transport Network Measurement License Missing 0000001544, CES over PSN License Missing 0000001640, VLAN Traffic Differentiation License Missing 0000001848, IP Security for Iub in BTS License Missing 0000003876, Rapid Spanning Tree (RSTP) in the BTS License Missing 0000003906, Power over EthernetINSTRUCTIONS: Download a valid license to the WBTS.

FAULT NAME : Link OAM critical link event $E on unit $U, interface $FFAULT ID : 61077: Link OAM critical link event alarmMEANING : A Link OAM PDU containing a critical link event flag was received on the Ethernet interface. The alarm is raised with the first detection of the flag. The following critical link events are possible: - Critical Event: either an Errored Symbol Period Event, an Errored Frame Event an Errored Frame Period Event or an Errored Frame Seconds Summary Event was detected. - Dying Gasp: either the local or the remote peer has a fatal error and is about to restart. - Link Fault: the local peer has detected a physical link fault in receiving direction, for example a LOS.INSTRUCTIONS: 1)Inspect details of the type of the critical event through

230 DN99580892




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

FAULTNAME : Link OAM link lost on unit $U, interface $FFAULT ID : 61076: Link OAM link lost alarmMEANING : On an interface for which the Link OAM functionality was switched on, no Link OAM PDUs were received during the period specified in configuration parameter linkLostTime (2..10 seconds, step 1 second).INSTRUCTIONS: 1)Check cabling and network connections to the far end. 2)Check Link OAM event- and Link OAM state information. 3)Check Ethernet interface configuration at local and remote side. 4)Insert a Link OAM loopback.

FAULT NAME : Link OAM loopback inserted on unit $U, interface $F by $P peerFAULT ID : 61075: Link OAM loopback alarmMEANING : A loopback is requested for an Ethernet interface either locally at the BTS or the Link OAM client of the BTS is set into loopback mode by the remote Link OAM peer.INSTRUCTIONS: None.

FAULT NAME : Link flapping faultFAULT ID : 61617: LINK_FLAPPING_FAULTMEANING : The link flapping alarm shall be raised on the Ethernet interface, if the link status changes twice (DOWN-->UP, UP-->DOWN) during the duration of the link flapping prevention timer. If the link goes up and down again during that flapping period, the link flapping timer shall be restarted.INSTRUCTIONS: Check link breaks.

FAULT NAME : Loss of IMA frame on unit $U, interface $IFFAULT ID : 61170: FTM_IMA_LIFMEANING : Loss of an IMA frame. The loss of an IMA frame was detected in one link of the IMA group. The far-end IMA link is not part of an IMA group. All other transmission alarms related to this IMA link are suppressed. Probable causes:

DN99580892 231




- the configuration of the IMA group is incomplete or faulty - there is disturbance on the lineINSTRUCTIONS: Do as follows for the interface referenced in the alarm text: 1. Verify that the IMA configuration of the near end and far end is correct. 2. Check the physical line for errors.

FAULT NAME : MLPPP Interface downFAULT ID : 61252: MLPPP_INTERFACE_DOWNMEANING : MLPPP interface is not operational when all the links in the bundle are not available.INSTRUCTIONS: All session down due to out of order or unplugged cable or interface down

FAULT NAME : MLPPP link DegradeFAULT ID : 61622: MLPPP_LINKDEGRADEMEANING : At least one of the sessions in MLPPP bundle has gone down.INSTRUCTIONS: This alarm is because of FTM_IPCP or FTM_LCP alarms.

FAULT NAME : No inserted or non-compliant SFP module on unit $U, interface $IFAULT ID : 61050: FTM_SFPMEANING : The SFP module detected in the interface connectors does not comply with the security requirements.INSTRUCTIONS: Insert a valid SFP module.

FAULT NAME : OSPF neighbor $causeFAULT ID : 61085: OSPF neighbor downMEANING : The alarm notifies if the OSPF neighbor is down. The alarm cause can be: OSPF Neighbour down for destination address 1.2.3.4 or OSPF Neighbour up for destination address 1.2.3.4INSTRUCTIONS: 1) Check cabling 2) Check the configuration of the static routes towards the neigbor

FAULT NAME : PLM (High Order Path) on unit $U, interface $IFFAULT ID : 61108: FTM_PLM_HOPMEANING : Path Payload Label Mismatch on the High Order Path. The SDH interface receives frames on the VC-3/VC-4 that have a Path Payload Label that does not correspond to the "ATM" (Asynchronous Transfer Mode) signal. The path is not intended for ATM traffic transport. Probable cause: The Signal Type Identifier on the far end

232 DN99580892




interface has not been configured to be "ATM".INSTRUCTIONS: Ensure that the path payload label for the VC-3/VC-4 at the far end is configured to be "ATM".

FAULT NAME : Poor Quality SSM on unit $UID $IFFAULT ID : 61624: SSM_POORQUALITYMEANING : This alarm is raised when the received SSM indicates lower clock quality (e.g. "do not use" or "EEC") than required.INSTRUCTIONS:

FAULT NAME : Pseudowire $PW down in egress direction on unit $UFAULT ID : 61602: FTM_PWE_DOWN_EGRESSMEANING : A Pseudowire has been detected to be down in the egress direction by using the BFD function. The alarm is raised when the BFD message from the far end contains the diagnostic code 'Control Detection Time Expired' and the corresponding ingress alarm is not present.INSTRUCTIONS: Check that the Pseudowire configuration is complete.

FAULT NAME : Pseudowire $PW down in ingress direction on unit $U.FAULT ID : 61601: FTM_PWE_DOWN_INGRESSMEANING : The Pseudowire has been detected to be down in the ingress direction by using the BFD function.INSTRUCTIONS: Check that the Pseudowire configuration is complete.

FAULT NAME : RDI (High Order Path) on unit $U, interface $IFFAULT ID : 61109: FTM_RDI_HOPMEANING : Remote defect indication on the High Order Path (VC-3/VC-4). This alarm occurs when the equipment at the far end of a bidirectional VC-3/VC-4 connection has detected an error condition on the signal that it is receiving. The far-end equipment signals this remote defect in the signal that it transmits. The RDI indicates a serious fault in the received signal of the far-end equipment. Probable cause: The far end has active alarms on its receiving interface (such as LOS, LOF, TIM-RS, AIS-MS, AIS-AU, LOP-AU, TIM-HP, UNEQ-HP).INSTRUCTIONS: 1. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. 2. To check the transmit hardware, connect a loop cable and check that LOS alarm is not raised.

FAULT NAME : RDI (Multiplexer Section) on unit $U, interface $IFFAULT ID : 61103: FTM_RDI_MS

DN99580892 233




MEANING : Remote defect indication (RDI) on the Multiplexer Section (MS). This alarm occurs when the equipment at the far end of a bidirectional multiplexer section connection has detected an error condition on the signal that it is receiving. The RDI indicates a serious fault in the received signal of the far-end equipment. Probable cause: The far end has active alarms on its receiving interface (such as LOS, LOF, TIM-RS, AIS-MS, AIS-AU, LOP-AU).INSTRUCTIONS: 1. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. 2. To check the transmit hardware, connect a loop cable and check that LOS alarm is not raised.

FAULT NAME : RDI on unit $U, interface $IFFAULT ID : 61152: FTM_RDIMEANING : Remote defect indication. It is sent by the intermediate or the far end equipment, because it detects a serious fault in the received signal. Probable cause: The far end has a LOS, LOF or AIS alarm on its receiving interface.INSTRUCTIONS: 1. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. 2. To check the transmit hardware, connect a loop cable and check that no alarms appear for this interface.

FAULT NAME : Routing misconfiguration for application $aFAULT ID : 61073: ROUTING_MISCONFIGURATIONMEANING : A routing misconfiguration was detected. A management-plane, control-plane, a synchronization-plane packet, or a CES-packet was sent over a network interface forwhichit was not intended, as configured in the application IP addresses. Or a user-plane packet was sent over a network interface for which the 6 PHB priority queue scheduler was not activated by the operator. Since the actual egress network interface is selected based on the static routing table entries, a misconfiguration of the static routing table is suspected.INSTRUCTIONS: Correct the static routing table or change application IP addresses or assign the 6-PHB priority queue scheduler to another network interface.

FAULT NAME : SSM Timed Out on unit $UID $IFFAULT ID : 61623: SSM_TIMEOUT

234 DN99580892




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

FAULT NAME : STC connection to signalling peer not established on interface $FAULT ID : 61260: FTM_STC_LINK_DOWNMEANING : The SSCOP link controlled by this STC is down. The alarm text specifies the slot, port, VPI and VCI number in question. Probable causes: - the peer (RNC) releases the connection - the link goes down because the peer (RNC) does not respond within the TIMER_NO_RESPONSE period. - the link was never established - problem on the ATM layer - problem on the physical layer - incomplete or faulty configuration of AAL2 in the RNCINSTRUCTIONS: 1. Check that there are no other active alarms on the physical or ATM layer. 2. Check that the RNC is up and running. 3. Check the AAL2 configuration. For example, make sure that the VPs/VCs used for AAL2 signalling in the RNC and WBTS match.

FAULT NAME : Synchronisation lostFAULT ID : 61058: FTM_SYNC_LOSSMEANING : Primary and secondary timing source lost. The WBTS is running on internal clock or in hold-over mode and no timing signal is sent. The first and second synchronisation sources from the configured priority list are unavailable. On failure, the WBTS switches automatically to the next clock source in the priority list. Probable cause: The transmission links selected for clock source are faulty. The reason can be alarms on the interfaces (for example, LOS, LOF or AIS).INSTRUCTIONS: Use the BTS Site Manager to check which interfaces have been configured as synchronization sources. For the PDH 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

DN99580892 235




correctly, connect a loop cable and check whether the alarm disappears.

FAULT NAME : TWAMP session down for reason: $rFAULT ID : 61084: TWAMP SESSION DOWNMEANING : A TWAMP session has gone down.INSTRUCTIONS: Check the cabling towards the TWAMP responder. Check the configuration of the TWAMP responder.

FAULT NAME : Timing source lost on unit $U, master $IFFAULT ID : 61059: FTM_TIMING_SOURCE_LOSMEANING : Primary or secondary timing source is lost. One of the synchronisation sources in the configured priority list is unavailable. If the primary clock source has been lost, a switch to the secondary source has occurred. If the secondary clock source has been lost, the WBTS will switch to the internal clock in case the primary clock source fails. Probable cause: The transmission link selected for the clock source is faulty. The reason can be alarms on the interface (for example, LOS, LOF, AIS or EBER).INSTRUCTIONS: Use BTS Site Manager to check which interfaces have been configured as synchronization sources. For the PDH 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, connect a loop cable and check whether the alarm disappears.

FAULT NAME : ToP master service $IP unusableFAULT ID : 61631: TOP_MASTER_UNUSABLEMEANING : The reference clock monitoring has detected a loss of ToP reference clock signal received from the master clock behind $IP. - The eNB does not receive a reply from ToP Master within a certain time (5 sec) upon it has sent a sync request message - The eNB receives from ToP Master a granted message rates (sync message rate, delay message rate), that does not match the requested rate by eNBINSTRUCTIONS: Check the cable connectivity. Check the TOP configuration.

236 DN99580892




FAULT NAME : Transport module missing: $unitFAULT ID : 61201: TRANSPORT_MODULE_MISSINGMEANING : Unit missing. The slot has been configured to hold a unit but the plug-in unit is not physically present in the slot. Probable causes: - the unit has been configured but not detected - the unit is broken and therefore not detected NOTE: unit variable should be replaced by appropriate HW names configured (unitTypeConfigured) during runtime reporting.INSTRUCTIONS: Replacing faulty hardware: 1. Re-Plug in the expected transport unit referenced in the alarm text. 2. In case there is a unit present in the slot, remove it from the slot and plug it back in. If the unit is still not recognised and the alarm remains, replace the faulty unit with a new one. De-commissioning previously commissioned hardware: 1. Re-commission to remove the hardware unit referenced in the alarm text. NOTE: Before re-commissioning, the hardware unit must not be present in the slot.

FAULT NAME : UNEQ (High Order Path) on unit $U, interface $IFFAULT ID : 61107: FTM_UNEQ_HOPMEANING : High Order Path Unequipped. The path signal label byte (C2) and the path trace byte (J1), and BIP-8 byte (B3) in the SDH path overhead (POH) all have the value zero. The path is unusable for traffic transport. Probable cause: the unequipped VC-3/VC-4 comes from a VC-level cross-connection node and the VC-3/VC-4 is not connected anywhere in that node.INSTRUCTIONS: 1. Check the configuration and ensure that the cross-connections between the nodes have been properly configured for transporting traffic. 2. Ensure that the Path Payload Label for the VC-3/VC-4 at the far end is configured to be "ATM". 3. Follow the signal in the network and check whether any other alarms concerning the fault are active. If this is the case, follow the instructions for handling those alarms.

FAULT NAME : Vendor BTS certificate due to expireFAULT ID : 61616: VENDOR_CERTIFICATE_EXPIRINGMEANING : The BTS raises a "Vendor BTS certificate due to expire"

DN99580892 237




alarm when the Vendor BTS certificate is about to expire. The period of notificaton in advance is configurable and the same as for the CA certificate expirydescribedin WBTS_SEC_46333 1 day ... 4999 days with default 1825 days.INSTRUCTIONS: Check the vendor BTS certificate expiry date and extend it.


238 DN99580892



7740 BEATING WCDMA BTS ALARM

37 7740 BEATING WCDMA BTS ALARMMeaning

The same radio network alarm has changed its alarm state (start/cancel)20 times consecutively, always during informing or cancelling delay,and has thus been filtered by the alarm system. The same radio networkobject is the object of both: the alarm in question and the beatingalarm that caused it.

Supplementary information fields1 the alarm number of the beating BTS alarm

2-15 if the beating alarm has any additional information, it is indicated here. Additional information is cut after 14 bytes and it is represented in hexadecimal format.

InstructionsCorrect the fault that caused the original beating alarm. You canfind the number of that alarm in Supplementary information field 1.


DN99580892 239


7750 FAILURE IN WCDMA WBTS O&M CONNEC-TION


38 7750 FAILURE IN WCDMA WBTS O&M CON-NECTIONMeaning

This alarm indicates that a failure has occurred in WBTS O&Mconnection. The problem is related to Iub connection betweencontroller and WBTS.From controller point of view the actual reason for the failureis either in transmission network between controller and WBTS, ininternal communication of controller applications or in WBTSconfiguration.

This alarm is set by controller in the following situations: 1) WBTS has closed the O&M connection. 2) WBTS O&M connection supervision message has not arrived within expected time 3) there is a problem in transmission network between controller and WBTS 4) a WBTS id conflict has been detected in the network

As a consequence of this alarm, the availability of WBTS O&Mfunctionality may be limited.

User initiated or automatic O&M tasks (e.g. SW download, HWconfiguration request and WBTS restart) cannot be performed in caseof Iub O&M connection problem. It is also not possible for the WBTSto report its alarms to controller.

This alarm does not indicate a failure in WBTS user plane links. Thestates of the user plane links can be checked using OMS TopologyBrowser.

Supplementary information fields1 reason of the alarm

1 = failure in the controller - WBTS connection 2 = WBTS id conflict

2 error code is received from IUB O&M connection. This field is significant only if the value of 1st field is 1

You can check its meaning from the document General Error Messages of System, Supplementary References

InstructionsError reason (field 1) indicates which part of the connection theproblem is located.

240 DN99580892




Error code (field 2) indicates what caused the problem if the errorreason (field 1) value is 1.

Error reason = 1, failure in the WBTS connection

Error code: 14005 = CONNECTION RESET BY PEER WBTS has closed the connection. Wait until WBTS opens a new connection and system cancels the alarm. If connection does not recover in a couple of minutes, check that WBTS is configured correctly to controller and to Network.

Error codes: 13960 = BAD FILE DESCRIPTOR 13964 = PERMISSION DENIED 13965 = BAD ADDRESS(EFAULT) 13986 = RESOURCE TEMPORARILY UNAVAILABLE 13989 = SOCKET OPERATION ON NON-SOCKET 13991 = MESSAGE TOO LONG 14006 = NO BUFFER SPACE AVAILABLE 14008 = SOCKET IS NOT CONNECTED 14016 = NO ROUTE TO HOST 14608 = CONNECTION NOT EXIST Controller attempted to send an O&M message towards the WBTS, but the connection does not exist in the controller (code 14608) or some error occurred in TCP layer when message sending was attempted.

Check that WBTS is configured correctly to controller and to Network. If configuration is ok, wait until WBTS opens a new connection and system cancels the alarm.

Error code: 154 = TIME LIMIT EXCEEDED IN MESSAGE WAITING WBTS supervision timer has expired. Connection is closed and controller is waiting for a new O&M connection opening from WBTS.

Wait until system cancels the alarm.

Error codes: 14001 = NETWORK IS DOWN 14011 = OPERATION TIMED OUT 14015 = HOST IS DOWN

There are problems in transmission network between controller

DN99580892 241




and WBTS. Try to connect to BTS using BTS Site Manager and deduce the source of the problem with provided information.

Error code: 10149 = SWITCHOVER

This error code is used if OMU unit switchover has occurred in the RNC and O&M connection to the WBTS has been closed because of that. The WBTS O&M connections are always handled by the OMU unit in WO-EX state so in switchover case the connections are closed.

Wait until WBTS opens the O&M connection again and system cancels this alarm.

Any other error code: Contact the local Nokia Siemens Networks representative.

Error reason = 2, WBTS id conflict

More than one WBTS has been configured with the same id.

Error code: 255 = UNSUCCESSFUL

An O&M connection for a WBTS id already exists in the RNC. This alarm was set because the same WBTS id was used in new O&M connection establishment from a different IP address that already existing connection was established from. This happens if several WBTS have been configured with the same WBTS id under the same RNC. The supplementary text of alarm gives IP address of the conflicting WBTS.

Use BTS Manager to connect the conflicting WBTS with its IP, configure it with a different id. Depending on the WBTS release, the reconfiguration may need to be done using AXC Manager.

Cancel the alarm manually after resolving the WBTS id conflict.

CancellingDo not cancel the alarm with error reason 1. The system cancelsthe alarm automatically when the fault has been corrected.The alarm with error reason 2 must be canceled manually.

Error reason = 1 Alarm will be canceled when BTS O&M connection is working again.

242 DN99580892




Error reason = 2 Alarm must be canceled manually with MML command AAN or with Fault Management application in RNC Element Manager after conflicting WBTS id situation is corrected.

DN99580892 243




39 7761 RNW O&M SCENARIO FAILUREMeaning

The alarm indicates a failure in some of the following scenarios:- Controller restart- WBTS initialization or WBTS reset- cell initialization, activation or blocking- forced handover- modification of configuration data- pid data updating (storing the process id of the telecom process which is responsible of managing the WBTS/WCELL in question)- WBTS capability information updating- Connection configuration (COCO(IPA-RNC))/IPNB management- Audit handling- Common channel supervision- Common measurement supervision- WBTS recovery (system initiated BTS restart operation)- Iu service barring- Cell deletion- Dedicated measurement initiation

These scenarios can be a consequence of either user operation oroperation performed by the system. User operation can be, forexample, WCEL creation with Element Manager or by plan.Operations performed by the system are in most cases related torecovery operations, for example common channel supervision.

In general, all failures cause the cell(s) to be blocked and henceunavailable to traffic.

Failure in cell blocking can lead to erroneous cell stateinformation in the controller.

Failure in WBTS capability updating or pid updating can causeincorrect WBTS capability data to be used in the controller and thusproblems in signalling or actual calls.

Failure in User plane configuration (AAL2 path unblocking) causes asituation where the User plane traffic cannot be transferred inthe corresponding AAL2 VCC.

Supplementary information fields1 reason for the failure

01 WBTS reservation has failed 02 Configuration data updating has failed 03 Inactivation of the cell has failed 04 Activation of the cell has failed 05 Common channel deletion has failed

244 DN99580892




06 Common channel creation has failed 07 BCCH information updating has failed 08 WBTS capability information was not received 09 Forced handover request was not accepted 0A WBTS capability information update has failed 0B AAL2 path unblocking has failed 0E Unknown NBAP interface type 11 Audit has failed, only 3GPP Iub 12 Cell setup procedure has failed, only 3GPP Iub 13 Cell deletion procedure has failed, only 3GPP Iub 14 Common measurement initiation has failed, only 3GPP Iub 15 RRI measurement initiation has failed, only 3GPP Iub 16 Cell reconfiguration procedure has failed, only 3GPP Iub 18 Common or RRI measurement termination failed, only 3GPP Iub 19 Cell barring has failed 20 COCO (IPA-RNC)/IPNB disconnect has failed 21 COCO (IPA-RNC)/IPNB connect has failed

2 scenario that was being carried out when the failure occurred

00 Not specified 01 WBTS initialization, Nokia Siemens Networks Iub 02 Cell unlocking, Nokia Siemens Networks Iub 03 Configuration data modification, Nokia Siemens Networks Iub 04 Controller restart, Nokia Siemens Networks Iub 05 Local cell resource state change 06 Forced handover 07 WBTS reset initiation from controller 08 WBTS capability information update 09 Pid update 0A Connection configuration management 0B Audit handling, 3GPP Iub 0C CCH Supervision 0D WBTS recovery 0E Iu service barring 0F Cell deletion, 3GPP Iub 81 WBTS initialization, 3GPP Iub 82 Cell unlocking, 3GPP Iub 83 Cell reconfiguration, 3GPP Iub 84 controller restart, 3GPP Iub 8D WBTS restart, 3GPP Iub 8E WBTS cell block, 3GPP Iub 8F WBTS cell unblock, 3GPP Iub 90 Resource status indication handling, 3GPP Iub 91 Common measurement supervision 92 Dedicated measurement initiation 93 Cell activation due to power save 94 Cell shutdown due to power save

3 general error code of the system

DN99580892 245




You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials, Maintenance Manual) or from the document General Error Messages of System, Supplementary References

4 ATM interface identifier of network external or internal interface. This field is significant only in case of User plane configuration fault.

FFFF Not specified

5 virtual path identifier. This field is significant only in case of User plane configuration fault.

FFFF Not specified

6 virtual channel identifier. This field is significant only in case of User plane configuration fault.

0 Not specified

InstructionsThis instruction contains five main steps. The first four steps arespecific to certain failure situations. The last step is a generaloperating procedure for all other failures indicated by this alarm.It is also a default procedure to be performed if instructions givenin previous steps do not solve the problem.Abbreviation SIF refers to supplementary information field.

Step 1: In case the value of SIF 2 (scenario) is 07 (WBTS reset): - First, verify using Element Manager that WBTS id is valid in the system and COCO (IPA-RNC) is connected to WBTS. - Check also if alarm 7750 FAILURE IN WCDMA BTS O&M CONNECTION is active for this WBTS. If it is active indicating that there is something wrong with WBTS O&M connection (Iub), then reset command cannot be sent from RNC to WBTS. -> If WBTS O&M connection is OK, retry to reset WBTS with Element Manager. -> If WBTS O&M connection between RNC and WBTS is not OK, try to solve the situation with BTS Manager by examining the WBTS alarms and logs.

Step 2: In case the value of SIF 2 is 0A (Connection configuration management), and the value of the SIF 1 is 0B (AAL2 path unblocking has failed): - Check the configuration of the corresponding WBTS node using BTS Manager. It should match the configuration of the RNC. - Check that ATM/IP resources related to COCO (IPA-RNC) are

246 DN99580892




not locked. Locked ATM/IP resources prevent the connection configuration operations. IPA-RNC: - Use MML command ZLAI to print ATM interface information and MML command ZLCI to print VP/VC information (if ATM layer information is given by the user in controller Element Manager). - Unlock the ATM-interface with MML command ZLAS and VP/VC with MML command ZLCS if needed. - If this alarm was generated due to user initiated action, for example COCO (IPA-RNC) creation, try to perform the operation again. Multi-controller RNC or Flexi Direct RNC: Commands "fshclish > show ipnb" can be used to see the IPNB configurations.

- If configuration is correct and ATM/IP resources are unlocked, act according to the general operating instructions in step 3 below.

Step 3: In case the SIF 2 value is 0D (WBTS recovery) and the value of the SIF 1 is 20 (COCO(IPA-RNC)/IPNB disconnect has failed) or 21 (COCO (IPA-RNC)/IPNB connect has failed): - In case of COCO(IPA-RNC)/IPNB disconnect failure, disconnect the COCO/IPNB manually using Element Manager by removing the WBTS id from the corresponding COCO(IPA-RNC)/IPNB object. Wait at least for 15 seconds and connect the COCO(IPA-RNC) again by restoring the WBTS id to COCO (IPA-RNC)/IPNB object. - In case of COCO(IPA-RNC)/IPNB connect failure, try to connect the COCO(IPA-RNC)/IPNB again to the WBTS using Element Manager.

In IPA-RNC if COCO id related to this WBTS is not known, the related COCO id can be found from OMU computer log by searching for process family 50B writings (ZGSC:,50B;) that contain also the WBTS id that this alarm is targeted to. In Multi-controller RNC/Flexi Direct RNC the family 50B logs can be found from location "/srv/Log/log/" in the product. This contains the detailed logs for all the families.

Step 4: In case the SIF 2 value is 92 (Dedicated measurement initiation): - Alarm 7778, WCDMA BTS DEDICATED MEASUREMENT FAILURE should be active. Follow the instructions given for that alarm.

Step 5: General operation instructions for all other failure reasons:

Wait a couple of minutes, system tries to recover from the problem by retrying the failed operation again and the alarm

DN99580892 247




may be cancelled automatically.

In case the alarm is not cancelled due to system recovery while waiting, try to lock and then unlock the cell with controller Element Browser manually. This causes the system to try to clear possible hanging cell related resources and then recreate (init) them.

In case the alarm is still active after lock/unlock cell operation, some of the following actions can be tried (each of these causes the WBTS to be unavailable during the operation). These operations clear and again init the BTS related resources: - Reset the WBTS with Element Manager, or - Reform the connection between WBTS and COCO(IPA-RNC) by first disconnecting the COCO (IPA-RNC) and then reconnecting it (this can be done by changing the used COCO(IPA-RNC)id in the WBTS with controller Element Manager) or block/unblock the BTS with BTS element manager.

If the alarm still remains active after the steps above, and noobvious reason behind it can be found, collect at least thefollowing logs and contact the local Nokia Siemens Networksrepresentative:

IPA-RNC: - OMU computer log, - message monitoring from OMU (families 50B, 4FA, 4EE and 4EF) and serving ICSU (check serving ICSU from COCO(IPA-RNC) (data in Element Manager, monitor families 4FE, 4FB, 4FD, 4B7) during BTS reset

Also controller reset might help the situation if it is possible to beperformed.

More information about the exact failure reason can be found byexamining the supplementary info field 3 (error code). You can checkits meaning with a command of the service terminal extension MRS(see Service Terminal Essentials, Maintenance Manual) or from thedocument General Error Messages of System, Supplementary References.

In many cases there is also more information in OMU computer log. Itcan be studied with MML-command ZDDE::"ZGSC";

Multi-controller RNC/Flexi Direct RNC: The detailed logs of all families can be collected from "/srv/Log/log/" location in the product.

248 DN99580892





DN99580892 249




40 7762 RNW DATABASE OPERATION FAILUREMeaning

RNW database operation has failed. This reading or writing operationwas tried for some of the following scenarios: - WBTS reset - WBTS initialization - Cell activation - Cell blocking - Cell unblocking - Modification of configuration data - Storing the pids - Storing the WBTS capability information - Storing cch parameters - Cell unlocking - Cell reconfiguration - Controller restart - Audit handling - Iu service barring - Resource status indication handling - Common measurement supervision

Depending on the scenario, this failure has led to a situation wherecell state could not be modified from blocked to working state orvice versa in controller or it was not possible to send configurationdata to WBTS. Failure in pid updating can cause trouble to other O&Mscenarios where that information is needed, and failure in WBTScapability updating or CCH parameter updating can cause inconsistentdata to be used in controller and thus problems in signalling or inactual calls.

Supplementary information fields1 specifies if the error occurred during reading from or writing to database

01 Reading failure 02 Writing failure

2 reason of the failure

00 Not specified 01 Failure at initialization 02 Configuration data 03 Deactivation of the cell has failed 04 Activation of the cell has failed 05 NBAP-link state updating failure 11 Failure in cell setup, 3GPP Iub 12 Failure in cell reconfiguration, 3GPP Iub

250 DN99580892




3 scenario that was being carried out when the failure occurred

01 WBTS initialization 02 Cell unlocking 03 Configuration data modification 04 Controller restart 05 Local cell resource state change 06 Forced handover 07 WBTS reset 08 WBTS capability information update 09 Pid update 0A CCH data update 0B Link failure/link failure cancel 0C CCH Supervision 0D Audit handling, 3GPP Iub 0E Iu service barring 81 WBTS initialization, 3GPP Iub 82 Cell unlocking, 3GPP Iub 83 Cell reconfiguration, 3GPP Iub 84 controller restart, 3GPP Iub 8D WBTS restart, 3GPP Iub 8E WBTS cell block, 3GPP Iub 8F WBTS cell unblock, 3GPP Iub 90 Resource status indication handling, 3GPP Iub 91 Common measurement supervision

4 general error code of the system.

You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials, Maintenance Manual) or from the document General Error Messages of System, Supplementary References

InstructionsIPA-RNC: At first, check the functionality of Radio Network database with the following MML-commands: ZDBS:RAQUEL,0; State of database should be normal and memory (and disk) updates not prevented. If updates are prevented, you can resume them with command ZDBR:RAQUEL,0:<mem or disk>; If database state is "waiting for dumping" or "dumping", database should return to normal state automatically after dumping is ready. Also status of the disk updating system can be checked with MML-command ZDBD:OMU; Line "RAQUEL" specifies the state of Radio Network database.

If database state is working (or becomes working after a while), do asfollows:

DN99580892 251




Try to lock the cell and then unlock it with Element Manager.If this does not clear the alarm, try WBTS reset.

If database state remains abnormal for long time or the alarm appearsconstantly for several WBTSs and cells, contact the local NokiaSiemens Networks representative. Also controller reset might help ifit is possible to perform it.

More information about the exact failure reason can be foundby examining the supplementary info field 4 (error code).

In many cases there is also more information in OMU computer log.IPA-RNC: It can be studied with MML-command ZDDE::"ZGSC";Multi-Controller RNC or Flexi Direct RNC: Logs can be collected and studied from location "/srv/Log/log/"in the product.


252 DN99580892




41 7771 WCDMA CELL OUT OF USEMeaning

The alarm indicates that an unlocked WCDMA cell has been blocked forsome reason, and it cannot transmit any traffic. This alarm is setonly when a cell is moved to the blocked state by the system,meaning that a user initiated state change does not cause thisalarm.

The alarm is set when one of the following situations occurs: 1. WCEL state is changed from - WO -> BL(B), bl- WBTS - WO -> BL(S), bl- system failure - WO -> BL(I), bl- init - WO -> BL(L), bl- C-NBAP link failure - WO -> BL(M), bl- Common measurement failure - WO -> BL(Ub), bl- Blocked by user locally from WBTS

It is possible that the WCEL state changes first from WO to BL(H) (bl - shutting down) and only after that to one of the above mentioned states. This alarm is not set when the WCEL state changes from WO to BL(H), but it is set when the BL(H) state is replaced by one of the above mentioned blocked states.

2. WCEL is unlocked and the COCO(IPA-RNC)/IPNB connection operation has been performed, but the state of the WCEL does not change to WO.

3. COCO(IPA-RNC)/IPNB connection operation has been performed, the WCEL has been unlocked, but the state of the WCEL does not change to WO.

4. An incorrect Local Cell Resource id has been given to this cell. Such a Local Cell does not exist in the WBTS.

5. The NEType indicated by the BTS and the NBAP Communication Mode configured in the controller for the WBTS object do not match.

The alarm is cancelled automatically when the state of the WCELchanges back to WO or when the cell is locked by the user.

Supplementary information fields1 indicates the state that the WCEL was changed into and what caused the alarm to be set. Full information about the current cell state is available in the Element Manager. The meanings of the possible values and the corresponding GUI abbreviations are:

DN99580892 253




0008: bl - WBTS (WBTS has sent disabled state information) (B) 0020: bl - system failure (S) 0040: bl - init (also during resets) (I) 0080: bl - C-NBAP-link failure (L) 0100: bl - Common measurement failure (M) 0200: bl - Blocked by user locally from WBTS (Ub) 0400: bl - Blocked because cell does not exist in WBTS (N)

2 general error code of the system.

You can check its meaning from General Error Messages of System.

InstructionsFirst task: wait for 5 minutes. Typically, there is still somerecovery operation ongoing. The alarm gets cancelled if therecovery is successful.

If the automatic recovery does not correct the situation, followthese steps: 1. If the blocking reason in the supplementary information field 1 (WCEL state) is 0008 (BL(B)) or 0200 (BL(Ub)), check the WBTS alarm that is related to this WCEL, and follow the operating instructions there.

2. If the blocking reason in the supplementary information field 1 (WCEL state) is 0400 (BL(N)), an incorrect Local Cell Resource id has been given to this cell. Such Local Cell does not exist in the WBTS. The cell data must be corrected and, after that, a WBTS reset is required to remove the problem.

3. If the blocking reason in the supplementary information field 1 (WCEL state) is 0040 (BL(I)) and the value in the supplementary information field 2 (Error code) is 4434 (nbapcmode_netype_mismatch_ec), the NBAP Communication Mode and the Netype do not match. Check the WBTS alarm related to this WCEL, and follow its operating instructions.

4. In case there are no alarms targeted to the WCEL, try to lock and then unlock the cell manually with the controller Object Browser. This way the system tries to clear the possible hanging cell related resources and then recreate (init) them.

5. If the alarm is not cancelled by the lock/unlock cell operation, you can try some of the following actions (the WBTS is unavailable during these operations). These operations first clear and then recreate the BTS related resources: - reset the WBTS with the Element Manager, or - reform the connection between the WBTS and the COCO(IPA-RNC) /IPNB by first disconnecting the COCO(IPA-RNC)/IPNB and then

254 DN99580892




reconnecting it (this can be done by changing the used COCO(IPA-RNC)/IPNB id in the WBTS with the Element Manager), or - block/unblock the BTS with the BTS element manager.

If the alarm is still active after the above operations have been performed, and no obvious reason behind it can be found, collect at least the following logs and contact the local Nokia Siemens Networks representative: IPA-RNC: - OMU computer log (service terminal command ZGSC), - message monitoring from OMU (families 50B, 4FA, 4EE and 4EF) and the serving ICSU (check the serving ICSU from the COCO (IPA-RNC) data in the Element Manager, monitor families 4FE, 4FB, 4FD, 4B7) during the BTS reset. Multi-Controller RNC or Flexi Direct RNC: Logs can be collected and studied from location "/srv/Log/log/"in the product.

Also a controller reset can help if it is possible to perform it.

More information about the exact failure reason can be found byexamining the supplementary information field 2 (error code). You cancheck its meaning with a command of the service terminal extensionMRS (see Service Terminal Essentials), or from the document GeneralError Messages of System.

In many cases there is also more information in the OMU computer log.IPA-RNC: It can be studied with MML-command ZDDE::"ZGSC";Multi-Controller RNC or Flexi Direct RNC: Logs can be collected and studied from location "/srv/Log/log/"in the product:

CancellingDo not cancel the alarm. The system cancels the alarm automaticallywhen the fault has been corrected. The alarm is cancelled by systemif the cell in question starts to work again or it is locked byuser.

DN99580892 255




42 7772 HSDPA CONFIGURATION FAILEDMeaning

This alarm indicates that there has been an error when controller hasrequested configuration or reconfiguration of HSDPA channels to BTSvia Physical Shared Channel Reconfiguration procedure.

The causes which result in this alarm are:

- a problem in transmission network between controller and BTS- BTS has rejected the configuration or reconfiguration of HSDPA channels- Controller is unable to send the HSDPA configuration to BTS because of controller internal problems (for example congestion in Iub interface)

Location and the nature of the failure can be determined from thesupplementary information fields of this alarm.

The consequence of this alarm depends on the HSDPA configuration phase.- In case the initial configuration of HSDPA channels fails, the effect is that HSDPA connections cannot be used in this particular cell at all. In this case also the HSUPA connections are unavailable if HSUPA is enabled in the cell.- In case of reconfiguration of HSDPA channels the effect is that the cell may not work with the intended HSDPA parameters.


Possible values: 01 = No reply from BTS 02 = BTS rejects the configuration 03 = Controller internal error

2 computer unit where this alarm is generated from

3 index of the alarming unit

4 more detailed cause in case the BTS rejects the configuration

Possible values: 00 = Error in radio network configuration 01 = Error in transport layer 02 = Error in NBAP protocol layer 03 = Miscellaneous

5 possible values sent by the BTS, value meaning depends on the cause that is given in 4th supplementary information field:

256 DN99580892




00 = Unknown cell ID (RNW configuration) 01 = Cell not available (RNW configuration) 06 = Node B resources unavailable (RNW configuration) 09 = Requested configuration not supported (RNW configuration)

03 = Message Not Compatible With Receiver State (Protocol)

00 = Control processing overload (Misc) 03 = Not enough user plane processing resources (Misc) 04 = Unspecified (Misc)

6 more detailed cause in case the value of the 1st supplementary information field is 3 ("controller Internal error").

Possible values: 306 = Internal waiting timer expired in BTS Resource Manager 328 = BTS overloaded 402 = Wrong BTS ID 404 = Wrong cell ID 420 = No free DL Spreading Codes available for HSDPA 501 = Internal waiting timer expired in NBAP interface 504 = Encoding failed in NBAP interface 505 = Decoding failed in NBAP interface 506 = Parallel procedure not allowed 507 = Unit switchover 508 = State conflict 510 = Table full 529 = NBAP link down

7 phase of HSDPA configuration

01 = Initial HSDPA configuration 02 = Reconfiguration of HSDPA 03 = PWSM HSPA05 reconfiguration failure

InstructionsCheck first the nature of the problem. The 7th supplementary informationfield value indicates the phase in which the problem has occurred:

01: Initial HSDPA configuration

The problem has occurred during initial HSDPA setup to a cell. The effect of this is that HSDPA cannot be used in the cell.

02: Reconfiguration of HSDPA

The problem has occurred during HSDPA reconfiguration to a cell. The effect is that the HSDPA may not work with the intended parameters. In this case it is recommended that HSDPA is disabled and enabled

DN99580892 257




in the cell to confirm that proper parameters are taken into use. This action requires cell locking.

03: PWSM HSPA05 reconfiguration failure

The problem has occurred during HSDPA reconfiguration to a cell when Power Saving Mode For BTS (PWSM) feature has been making HSPA05 reconfiguration. HSPA05 reconfiguration has been stopped and no cell deletion or activation by PWSM feature will be done. In this case it is recommended to disable PWSM feature. Do cell lock/unlock to recover cell HSDPA parameters and state. If cell is not recovered using lock/unlock operation, a BTS restart can be attempted using Element Manager or BTS Site Manager.

The first supplementary information field value indicates the mainreason for the problem.

01: No reply from WBTS

Problem may reside somewhere in transmission network to BTS. Check if there are other active alarms for the WBTS object and follow the instructions given for those alarms.

If there are no apparent problems shown via other alarms, check the type of network problem with following instructions:

Precondition for Physical Shared Channel Reconfiguration procedure is that the C-NBAP link to WBTS is working. Check the state of C-NBAP link of this WBTS object from Element Manager main dialog. If the C-NBAP link works, the problem may reside in the BTS. Check the BTS configuration and logs using BTS Manager.

If the C-NBAP link does not work, check the success of PING between controller and BTS. Successful PING tells that the BTS is up and running: MML command: ZQRX (IPA-RNC) Normal Ping command : Multi-controller RNC/Flexi Direct RNC

If ping does not succeed, then the problem is in lower level of the transmission network. Check physical connections in the network. If ping succeeds, then the problem is in application level.

In many cases there is also more information in OMU computer log.

IPA-RNC : Logs can be studied with MML-command ZDDE::"ZGSC";

Multi-Controller RNC or Flexi Direct RNC: Logs can be collected and studied from location

258 DN99580892




"/srv/Log/log/" in the product.

02: BTS rejects the configuration

Check that the concerned BTS is in working state using Element Manager. If the working state of the BTS is OK, check that the BTS has correct HW configuration so that HSDPA can be supported (WSPC cards) using BTS Manager. If the working state of the BTS and the BTS HW configuration are OK but this fault still occurs, contact the local Nokia Siemens Networks representative.

In case the fault is related to RNW configuration (based on 4th and 5th alarm supplementary information fields of this alarm), check the configuration of this WBTS object in controller using Element Manager, and the configuration in BTS using BTS Manager.

Check also if other alarms are active targeted to this same WBTS object. If there are active alarms, proceed according to instructions given for those alarms.

If the fault cannot be resolved by correcting the configuration or other BTS alarms, contact the local Nokia Siemens Networks representative.

03: Controller internal error

An internal error in controller has occurred during Physical Shared Channel Configuration procedure.

If the 6th supplementary information field of this alarm has a value 306, 420, 501, 504, 505, 506, 508, 510 or 529, the situation may be resolved by locking and unlocking the cell. This operation cancels the alarm and triggers the Physical Shared Channel Reconfiguration procedure again. If the problem was only temporary, the alarm should not appear again.

If the alarm appears again after a while, check the log writings from the concerned ICSU (IPA-RNC Control plane unit) for example by using MML command ZDDE:ICSU,<index>:"ZGDIC;"; The ICSU unit index to be used is shown in the 3rd supplementary information field of this alarm.

To collect the necessary data for troubleshooting, initiate message monitorings in the concerned ICSU unit (IPA-RNC Control plane unit) mentioned in 2nd and 3rd supplementary information fields of this alarm (families 04FE, 04FB) and in active OMU unit.

In Multi-Controller RNC and Flexi Direct RNC the detailed family logs can be collected from location in the product "/srv/Log/log/".

DN99580892 259




Start the Physical Shared Channel Reconfiguration procedure by locking and unlocking the cell and wait for the alarm to be set again. Collect the logs and monitorings and contact the local Nokia Siemens Networks representative.


Locking or deleting of the cell, or next succeeded configuration of HSDPAchannels cancels the alarm.

260 DN99580892



7773 INSECURE O&M CONNECTION

43 7773 INSECURE O&M CONNECTIONMeaning

The alarm indicates that one or more network elements have establishedan O&M connection with insecure protocol while the controller is configuredin probing security mode. In probing mode the secure connections arepreferred, i.e. the alarm may be an indication of a failure in setting up asecure connection.

Problems in transport layer or incorrect certificates installation wouldcause the network element to establish the connection with controller withinsecure protocol when the controller is configured in probing mode.

Supplementary information fields1 this represents the actual reason for Controller accepting insecure connection. The field value may indicate:

- problems in transport layer Error code: 11728 = TRANSPORT PROTOCOL ERROR 11730 = TRANSPORT SERVICE MISBEHAVIOUR 16654 = TRANSPORT LAYER CAUSE UNSPECIFIED

- incorrect certificates installation in the network element Error code: 16212 = NO CERTIFICATES FOUND 16213 = FOUND MULTIPLE CERTIFICATES 17485 = CERTIFICATE IS EXPIRED

InstructionsTo analyze and correct the problem, check the 1st supplementary informationfield value. The 1st supplementary information field indicates the reasonwhy the network element is not able to establish the secure connection withthe controller when it is in probing mode.

To correct the problem, ensure that the correct certificates are installedin the controller as well as in the network element which is trying toestablish the secure O&M connection.

After the right certificates are installed at the Controller end, operatorshould trigger the TLSmode as probing which will make Controller to closethe server port and open the port with right certificates.


DN99580892 261


7775 INCONSISTENCY IN WCEL CONFIGURATIONPARAMETERS


44 7775 INCONSISTENCY IN WCEL CONFIGU-RATION PARAMETERSMeaning

The alarm indicates inconsistency in parameterization betweencontroller and BTS. It may be raised because of these reasons:1. Nokia Siemens Networks specific configuration parameters in BTS might not be consistent with the parameters in controller. These parameters are CellRange, RACHCapacity, SIB7factor, ShutdownWindow, and ShutdownStepAmount. The situation causing this alarm does not obstruct network operations.2. The WCEL in the object unit of the alarm has too many adjacencies configured so that the size of the System Information Block (SIB) would exceed the maximum size.

In case of parameter inconsistency, the alarm is set when BTS hasfailed to accept the parameters sent to it during cell setup orwhen BTS has not responded to the parameter sending during cellsetup. The alarm is cancelled automatically after these configurationparameters have been successfully sent to BTS.

In case of SIB data encoding failure, the controller has droppedsome of the configured adjacencies automatically to enable theSIB sending for the cell and allowing it to be activated. Thealarm is cancelled automatically after the adjacency configurationhas been modified so that SIB sending can be done normally for thecell.

A certain WCEL may have multiple instances of this alarm raised foreach different reason simultaneously.

The alarm is cell-specific and its indication to NetAct has beenprevented by default in IPA-RNC. The controller-specific alarm 3325,INCONSISTENCY IN CONFIGURATION PARAMETERS, is related to this alarmand one instance of it is activated when this alarm has been raisedto one or more cells in a certain controller. This controller-specificalarm is sent to NetAct by default.

Alarm indication preventions can be altered with MML command AFC inIPA-RNC.

Supplementary information fields1 name of the reason why the failure was observed. Possible values:

* SIB_FAIL = SIB sending failure * INCONSIS = BTS parameters are not consistent with the controller

2 general error message of the system. You can check its meaning

262 DN99580892



7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS

with a command of the service terminal extension MRS or in the General Error Messages of System

InstructionsCase 1: If the alarm reason given in the first supplementary information field is INCONSIS:

Check the cell parameters CellRange, RACHCapacity, SIB7factor, ShutdownWindow and ShutdownStepAmount in controller using Element Manager. If these parameter values are the same as those in the BTS Site Configuration File, no actions are needed in controller. Check if other alarms are active for the BTS or WCEL in question.

If the cell parameters in controller are not the same as those in the BTS Site Configuration File and these parameters need to be updated, the following actions can be taken to the cell that has failed to accept the parameters sent:

* Modify these parameters with Element Manager. This is recommended if the cell works, that is, cell state (WCEL state) is WO. * Lock the cell and then unlock it with Element Manager. This operation causes the parameters to be resent to the BTS.

More information about the exact failure reason can be found by examining the error code given in 2nd supplementary information field.

Probable error code values are: * 94 = NO RESPONSE BTS has not responded to parameter sending in time or response did not include all the cells the parameters where sent to. * 15472 = WBTS HARDWARE OVERLOAD BTS is temporarily too busy to handle new requests. * 15477 = EQUIPMENT FAILURE A HW failure has occurred. * 15480 = NO RESOURCES IN WBTS Node B resources are unavailable. * 16504 = INTERNAL NBAP ERROR PREVENTING PROCEDURE COMPLETION An internal error that prevents parameter sending has occurred.

In these fault cases the actions mentioned above should repair the situation. Fault cases with error code EQUIPMENT FAILURE may also require repairing of BTS HW.

Case 2: If the alarm reason given in the first supplementary information field is SIB_FAIL:

DN99580892 263


7775 INCONSISTENCY IN WCEL CONFIGURATIONPARAMETERS


Check the number of neighboring cells (ADJS, ADJI and ADJG) configured for the WCEL in question in controller. Reduce the number of neighboring cells either by modifying or deleting ADJS, ADJI and/or ADJG objects of this cell.

In many cases there is more information in the OMU computer log. InIPA-RNC it can be studied with the MML-command ZDDE::"ZGSC";Detailed information can be collected from location "/srv/Log/log/" inthe Multi-controller RNC/I-HSPA ADA. This contains the detailed logs forall the families.

CancellingDo not cancel the alarm. The system cancels the alarm automaticallyafter these parameters/SIBs have been sent successfully to the WBTS.

264 DN99580892




45 7776 HSDPA FAILURE IN WCELMeaning

A major fault (or faults) occurs in the BTS. A unit (or units)that take care of HSDPA traffic in WCEL can be faulty, or there is notenough capacity available in the BTS WSP cards for the HSDPA service.

This alarm is set when an HSDPA-capable BTS sends a Resource StatusIndication (RSI) message via NBAP to RNC indicating that HSDPA stateis changed to "disabled". As a consequence of this alarm, HSDPAconnections cannot be used in that particular cell.

The RSI message regarding HSDPA disabling can arrive also after thewhole cell is reported as "disabled" by BTS via another RSI message.This can happen in BTS recommissioning phase when the cell is disabledin the BTS end as part of the BTS maintenance operations. In this casethis alarm can appear together with the alarms for the same WCELobject:7761 RNW O&M SCENARIO FAILURE7771 WCDMA CELL OUT OF USE

In case the overall WCEL object state is WO (working) when this alarmappears, check the reason for the fault from the BTS WSP-related alarms.


InstructionsFirst check the WCEL operational state using RNW RNC Object Browser.

If the WCEL operational state is not WO (working), ignore this alarm andanalyze the problem with the WCEL taking into account the other activealarms for the same WCEL or its parent WBTS object.

If the WCEL operational state is WO, check in the RNC the WSP-relatedactive alarms that are targeted to the related WBTS object.The alarms to be checked are: 7650 BASE STATION FAULTY 7651 BASE STATION OPERATION DEGRADED 7652 BASE STATION NOTIFICATIONThe faulty unit is mentioned in supplementary information field 3 ofthese alarms. Check all WSP-related alarms because any of theWSP-related fault can be the reason for this alarm.

If a HSDPA-dedicated WSPC unit in BTS is faulty, the BTS reservesanother WSPC when it becomes free from other traffic.

For more information on BTS alarms, see WCDMA BTS Alarm

DN99580892 265




Descriptions (SW and release documentation).

CancellingDo not cancel the alarm. The system cancels the alarm automaticallywhen the fault is corrected.

266 DN99580892



7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE

46 7778 WCDMA BTS DEDICATED MEASURE-MENT FAILUREMeaning

This alarm is set when Dedicated Measurement (for transmitted code power)Initiation fails due to the following three cases during cellinitialization:1) BTS problem, such as no response or nack2) NBAP-D link is down3) NBAP-D module has a problem (controller internal)

Controller retries Dedicated Measurement Initiation after thecorresponding NBAP-D link is re-created to be ready. If the retrysucceeds, the alarm is cancelled.

After this alarm, cells' capacity under the BTS might be affected.

Supplementary information fields1 general error code of the system. You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials, Maintenance Manual) or from the document General Error Messages of System, Supplementary References

2 communication control port id

InstructionsFirst, check if there are other alarms active for the BTS in questionand follow the instructions given for those alarms. This alarm iscancelled if the problem is solved by correcting the other activealarms.

If there are no obvious faults indicated by active alarms and thisalarm is not cancelled by system, follow the instructions given in thesteps below according to error code given in the first supplementaryinformation field.

1. Error code 13247 no_answer_from_remote_end_ec No response from BTS 15479 nbap_bts_hw_res_not_avail_ec BTS hardware failure

These codes indicate that response from BTS was not received for Dedicated Measurement Indication or BTS hardware failure. The operation can be retried by creating the corresponding NBAP-D again using Element Manager (this operation causes all the cells of the BTS being unavailable for traffic): 1) Lock all the cells under the BTS. 2) Remove the WBTS id from the COCO(IPA-RNC)/IPNB.

DN99580892 267


7778 WCDMA BTS DEDICATED MEASUREMENTFAILURE


3) Add the WBTS id to the COCO(IPA-RNC)/IPNB again. 4) Unlock these cells.

If creating the NBAP-D again does not help, the problem may reside on the BTS end. It should be analyzed by connecting to corresponding BTS using BTS Manager.

2. Error code 13288 dst_link_failure_ec NBAP-D link has been down 13846 no_resp_from_serv_provider_ec NBAP-D process no response

The operation in step 1 can be attempted, it may help if the problem was only temporary. If the operation in step 1 does not help, the communication problem between controller processes should be analyzed by taking message monitoring from controller OMU when the unlocking of the cells is done. See the last part of this instruction for information about collecting the needed monitorings and logs.

3. Any other error code:

Try to perform NBAP-D link creation again using instructions given in step 1.

If this doesn't help, a BTS restart may be attempted to solve thesituation.

If the problem persists after these steps, contact the local NokiaSiemens Networks representative. Attach OMU message monitorings fortroubleshooting:IPA-RNC: For process 3C6, all of ICSUs message monitoring for process 4FE, OMU computer log and error log (MML-commands ZDDE::"ZGSC"; and ZDDE::"ZGLE";), and alarm history (MML-command ZAHP or using Fault Management application in controller EM). Multi-Controller RNC or Flexi Direct RNC: Message monitoring for families can be collected from location "/srv/Log/log/" in the product. Also alarm history can be collected by using SCLI command "fsclish -c "show alarm history"" or using Fault Management application in controller EM.


268 DN99580892




47 7779 RECOVERY ACTIONS ONGOINGMeaning

The alarm indicates that controller has started WBTS recovery actionsdue to a non-performing WCDMA cell. During recovery actions it cannottransmit any traffic.

The alarm is set when some of the following situations occur:1. Common measurements are missing and common measurement recovery actions have failed.2. Common measurement initialization constantly fails.3. Common channel creation constantly fails.4. There is poor handover-related radio link setup ratio.5. There is poor FACH RRC connection setup/complete ratio.6. Base Station resource manager process family (BRM) hand crashes in controller.7. There is constant radio link failure acknowledged by NodeB during RRC connection setup.

This alarm informs operator that recovery actions are ongoing.The recovery actions include WBTS reset that takes a while.During this recovery action no other user actions are recommended.

The alarm is cancelled automatically after the WBTS recovery actionshave been completed. After this operator can start to perform useractions again.

After this alarm has been cancelled and BTS recovery actions haveended, it is possible that other recovery actions are startedif cells are still in some block state. Alarm 7761 or 7762 is setif a failure occurred during WBTS initialization after theWBTS reset.

Supplementary information fields1 this value indicates the cause that has led to recovery actions:

00 Common measurements are missing and common measurement recovery actions have failed. 01 Common measurement initialization constantly fails. 02 Common channel creation constantly fails. 04 Poor handover related radio link setup ratio. 05 Poor FACH RRC connection setup/complete ratio. 06 Constant radio link failure acknowledged by NodeB. 08 Base Station resource manager process family (BRM) hand crash in controller.

DN99580892 269




InstructionsThis alarm does not require any actions.

WBTS recovery actions are started when other recovery actions have notrecovered the cell. The reason for WBTS recovery actions is indicatedin the 1st supplementary information field.

If cell still does not work after the WBTS recovery actions have endedand no reason behind it can be found, collect at least the following logsand contact the local Nokia Siemens Networks representative:IPA-RNC: - OMU computer log (MML-commands ZDDE::"ZGSC"; and ZDDE::"ZGLE";) - alarm history (MML-command ZAHP or using Fault Management application in controller EM) - message monitoring from OMU (families 50B, 4FA) and serving ICSU (check serving ICSU from COCO(IPA-RNC) data in Element Manager, monitor families 4FE, 4FB, 4FD, 4B7) during WBTS reset Multi-Controller RNC or Flexi Direct RNC: Message monitoring for all families can be collected from location "/srv/Log/log/" in the product. Also alarm history can be collected by using SCLI command "fsclish -c "show alarm history"" or using Fault Management application in controller EM


270 DN99580892




48 7780 HSUPA FAILURE IN WCELMeaning

A major fault (or faults) occurs in the BTS. A unit (or units)taking care of HSUPA traffic in the WCEL can be faulty, or there is notenough capacity available on the BTS WSP cards for HSUPA service.

This alarm is set when an HSUPA-capable BTS sends a Resource StatusIndication (RSI) message via NBAP to the RNC indicating that HSUPA stateis changed to "disabled". As a consequence of this alarm, HSUPAconnections cannot be used in that particular cell.

The RSI message regarding HSUPA disabling can arrive also after thewhole cell is reported as "disabled" by BTS via another RSI message.This can happen in BTS recommissioning phase when the cell is disabledin the BTS end as part of the BTS maintenance operations. In this casethis alarm can appear together with the alarms for the same WCELobject:7761 RNW O&M SCENARIO FAILURE7771 WCDMA CELL OUT OF USE

In case the overall WCEL object state is WO (working) when this alarmappears, check the reason for the fault from the BTS WSP-related alarms.


InstructionsFirst check the WCEL operational state using RNW RNC Object Browser.

If the WCEL operational state is not WO (working), ignore this alarm andanalyze the problem with the WCEL taking into account the other activealarms for the same WCEL or its parent WBTS object.

If the WCEL operational state is WO, check in the RNC the WSP-relatedactive alarms that are targeted to the related WBTS object.The alarms to be checked are: 7650 BASE STATION FAULTY 7651 BASE STATION OPERATION DEGRADED 7652 BASE STATION NOTIFICATIONThe faulty unit is mentioned in supplementary information field 3of these alarms. Check all WSP-related alarms because any of theWSP-related faults can be the reason for this alarm.

If a HSUPA-dedicated WSPC unit in the BTS is faulty, the BTSreserves another WSPC when it becomes free from other traffic.

For more information on BTS alarms, see WCDMA BTS Alarm

DN99580892 271




Descriptions (SW and release documentation).

CancellingDo not cancel the alarm. The system cancels the alarmautomatically when the fault is corrected.

272 DN99580892



7781 NETWORK ELEMENT CONFIGURATION ER-ROR

49 7781 NETWORK ELEMENT CONFIGURATION ERRORMeaning

The alarm indicates that the NEType indicated by the BTS and the IubWorking Mode configured in the controller for the WBTS object donot match. The controller sets this alarm when such a mismatchis detected after the BTS O&M link establishment.

The consequences of this alarm are: - WCEL unlocking operation under this BTS is denied. - WCEL creation under this BTS is denied. - WCEL modification under this BTS is denied. - The creation, modification, and connection of a related COCO (IPA-RNC)/IPNB are denied. - WBTS modification is denied. - WBTS and its child objects can be deleted. - WCEL can be locked.

The alarm is canceled automatically when the WBTS is deleted, orno mismatch is detected after the BTS O&M link establishment.

Supplementary information fields1 indicates the BTS model in the WCDMA. The meanings of the possible values and the corresponding GUI abbreviations are: 00 - Not used 01 - Other 02 - UltraSite BTS 03 - FlexiBTS 04 - PicoBTS 05 - Wimax 09 - NB/RSxxx 17 ? FlexiLiteBTS

2 indicates the used communication mode for NodeB via the NBAP interface. The meanings of the possible values and the corresponding GUI abbreviations are: 00 - UltraSite BTS, FlexiBTS, PicoBTS 01 - NB/RSxxx

InstructionsThe WBTS deletion and recreation are required when correcting theincorrect configuration. The WBTS recreation is needed because theIub Working Mode is a non-modifiable parameter that must begiven in the WBTS object creation phase.

Step 1:

DN99580892 273


7781 NETWORK ELEMENT CONFIGURATION ER-ROR


Check, using the Topology Browser, if there are WCELs under this WBTS. If so, lock all these WCEL objects and delete them.

Step 2:

Delete the WBTS object.

Step 3:

Recreate the WBTS object with the correct Iub Working Mode parameter value. Next, recreate the WCEL objects under this WBTS.

CancellingDo not cancel the alarm. The system cancels the alarm automaticallywhen the WBTS is deleted, or no mismatch is detected after theBTS O&M link establishment.

274 DN99580892




50 7782 HSUPA CONFIGURATION FAILEDMeaning

This alarm indicates that there has been an error when controllerrequested configuration or reconfiguration of HSUPA channels toBTS via Physical Shared Channel Reconfiguration (PSCR) procedure.

The possible causes which result in this alarm are:

- There has been a problem in transmission network between controller and BTS.- BTS has rejected the configuration or reconfiguration of HSUPA channels.- Controller is unable to send the HSUPA configuration to BTS because of controller internal problems (for example congestion in Iub interface)

Location and the nature of the failure can be determined from thesupplementary information fields of this alarm.

The consequence of this alarm depends on the HSUPA configuration phasewhere the failure occurred.- If the failure occurred in the initial HSUPA configuration or in delivering the HSUPA parameters to the BTS, the HSUPA connections cannot be used in this particular cell at all.- If the failure occurred in the reconfiguration of the HSUPA, the effect is that the cell may not work with the intended HSUPA parameters.


Possible values: 01 = No reply from BTS 02 = BTS rejects the configuration 03 = Controller internal error

2 computer unit where this alarm is generated from

3 index of the alarming unit

4 this info field is applicable if the 1st supplementary information field value is 01

5 more detailed cause in case the BTS rejects the configuration

Possible values: 00 = Error in radio network configuration 01 = Error in transport layer

DN99580892 275




02 = Error in NBAP protocol layer 03 = Miscellaneous

The value in this field is applicable if the 8th supplementary information field value is 02 or 03

6 possible values sent by the BTS, value meaning depends on the cause that is given in the 4th supplementary information field:

00 = Unknown cell ID (RNW configuration) 01 = Cell not available (RNW configuration) 06 = Node B resources unavailable (RNW configuration) 09 = Requested configuration not supported (RNW configuration)

03 = Message Not Compatible With Receiver State (protocol)

00 = Control processing overload (Misc) 03 = Not enough user plane processing resources (Misc) 04 = Unspecified (Misc)


7 more detailed cause in case the value of the 1st supplementary information field is 03 ("Controller Internal error").

Possible values:

306 = Internal waiting timer expired in BTS Resource Manager 328 = BTS overloaded 402 = Wrong BTS ID 404 = Wrong cell ID 420 = No free DL Spreading Codes available for HSUPA 501 = Internal waiting timer expired in NBAP interface 504 = Encoding failed in NBAP interface 505 = Decoding failed in NBAP interface 506 = Parallel procedure not allowed 507 = Unit switchover 508 = State conflict 510 = Table full 529 = NBAP link down


8 phase of HSUPA configuration

01 = Delivering HSUPA parameters to BTS 02 = Initial HSUPA configuration 03 = Reconfiguration of HSUPA

276 DN99580892




04 = PWSM HSPA05 reconfiguration failure

InstructionsStep 1:

Check first the nature of the problem. The 8th supplementary information field value indicates the phase in which the problem has occurred:

01: Delivering HSUPA parameters to BTS 02: Initial HSUPA configuration

The problem has occurred during initial HSUPA setup to a cell. The effect of this is that HSUPA cannot be used in the cell. Proceed to the step 2 in this instruction.

03: Reconfiguration of HSUPA

The problem has occurred during HSUPA reconfiguration to a cell. The effect is that the HSUPA may not work with the intended parameters. In this case it is recommended that HSUPA is disabled and enabled in the cell to confirm that proper parameters are taken into use. This action requires cell locking.

04: PWSM HSPA05 reconfiguration failure

The problem has occurred during HSUPA reconfiguration to a cell when Power Saving Mode For BTS (PWSM) feature was performing HSPA05 reconfiguration. HSPA05 reconfiguration has been stopped and no cell deletion or activation by PWSM feature is done. In this case it is recommended to disable PWSM feature. Do cell lock/unlock to recover cell HSUPA parameters and state. If cell is not recovered using lock/unlock operation, a BTS restart can be attempted using Element Manager or BTS Site Manager.

Step 2:

The first supplementary information field indicates the main reason for the problem.

01: No reply from WBTS

Problem may reside somewhere in transmission network to BTS. Check if there are other active alarms for the WBTS object and follow the instructions given for those alarms.

If there are no apparent problems shown via other alarms, check the type of network problem with the following instructions:

Precondition for Physical Shared Channel Reconfiguration

DN99580892 277




procedure is that the C-NBAP link to WBTS is active. Check the state of C-NBAP link of this WBTS object from Element Manager main dialog. If the C-NBAP link works, the problem may reside in the BTS. Check the BTS configuration and logs using BTS Manager.

If the C-NBAP link does not work, check the success of PING between controller and BTS. Successful PING tells that the BTS is up and running: MML command: ZQRX (IPA-RNC) Normal Ping command : Multi-controller RNC/Flexi Direct RNC If ping does not succeed, then the problem is in lower level of the transmission network. Check physical connections in network. If ping succeeds, then the problem is in application level.

In many cases there is also more information in OMU computer log. IPA-RNC : Logs can be studied with MML-command ZDDE::"ZGSC"; Multi-Controller RNC or Flexi Direct RNC: Logs can be collected and studied from location "/srv/Log/log/" in the product.

02: BTS rejects the configuration

Check that the concerned BTS is in working state using controller Element Manager. If the working state of the BTS is OK, check that the BTS has correct HW configuration so that HSUPA can be supported (WSPC cards) using BTS Manager. If the working state of the BTS and the BTS HW configuration are OK, but this fault still occurs, contact the local Nokia Siemens Networks representative.

In case the fault is related to RNW configuration (based on the 4th and the 5th alarm supplementary information fields of this alarm), check the configuration of this WBTS object in controller using Element Manager, and the configuration in BTS using BTS Manager.

Check also if other alarms are active targeted to this same WBTS object. If there are active alarms, proceed according to instructions given for those alarms.

If the fault cannot be resolved by correcting the configuration or other BTS alarms, contact the local Nokia Siemens Networks representative.

03: Controller internal error

An internal error in controller has occurred during Physical

278 DN99580892




Shared Channel Configuration procedure.

If the 6th supplementary information field of this alarm has a value 306, 420, 501, 504, 505, 506, 508, 510 or 529, the situation may be resolved by locking and unlocking the cell. This operation cancels the alarm and triggers the Physical Shared Channel Reconfiguration procedure again. If the problem was only temporary, the alarm should not appear again.

If the alarm appears again after a while, check the log writings from the concerned ICSU, for example by using MML command ZDDE:ICSU,<index>:"ZGDIC;"; The ICSU unit index to be used is shown in the 3rd supplementary information field of this alarm.

To collect the necessary data for troubleshooting, initiate message monitorings in the concerned ICSU (IPA-RNC Control plane unit) mentioned in the 2nd and the 3rd supplementary information fields of this alarm (families 04FE, 04FB) and in active OMU unit.

In Multi-Controller RNC and Flexi Direct RNC the detailed family logs can be collected from location in the product "/srv/Log/log/".

Start the Physical Shared Channel Reconfiguration procedure by locking and unlocking the cell and wait for the alarm to be set again. Collect the logs and monitorings and contact the local Nokia Siemens Networks representative.


Locking or deleting of the cell, or next succeeded configuration of HSDPAchannels cancels the alarm.

DN99580892 279


7783 IP BASED D-NBAP LINK FAILURE


51 7783 IP BASED D-NBAP LINK FAILUREMeaning

One or more IP-based D-NBAP links of a WCDMA BTS are detected lostby the controller.

The user plane traffic handling capability of the WCDMA BTS isdegraded, or the traffic capability of the whole WCDMA BTS istotally lost.

This alarm is set only if the fault is detected in IP-based D-NBAPlink(s) of the WCDMA BTS. The alarm is not set for IP-based D-NBAP linksif the C-NBAP link is unavailable at the same time.

Supplementary information fields1 IPv4 address of the remote end. This field is filled with zeroes if IPv6 addressing is in use.

2 IPv6 address of the remote end. This field is filled with zeroes if IPv4 addressing is in use.

InstructionsSee the NBAP link operational states for the WCDMA BTS from TopologyBrowser in controller OMS to see which of the configured D-NBAP linksare unavailable.

In case this alarm is set right after the WBTS is enabled in the system,verify using Topology Browser that the IPNB object configurationin controller is correct in relation to the network setup.

Otherwise, the problem is likely to be located either in the BTS or in IPtransmission between the BTS and the controller. See other possibleactive BTS-originated alarms (7650, 7651) that can indicate thereason for the failure.Use BTS Site Manager to see the operation status in the BTS end foradditional troubleshooting.


280 DN99580892




52 7784 RECOVERY ACTION FAILUREMeaning

This alarm indicates that automatic WCDMA BTS recovery action performedby controller has failed. The recovery has been attempted because someof the WCELs under the WBTS have been detected not to be performingproperly. The observed cause for the recovery is given in alarmsupplementary information. For more information about the recoveryfunctionality behind this alarm, see feature descriptions for featuresRAN1302 and RAN1810 in Product Documentation.

The reason for the recovery failure is one of the following: - The amount of WBTS recovery actions (restarts) have been used up for a specific WBTS object for the current day. - BTS restart failed due to missing BTS O&M connection. - BTS does not respond to restart request. - BTS is busy handling software upgrade and rejects the restart request.

As a result of this alarm the traffic handling capacity of the WCDMABTS may be reduced because some WCELs do not perform properly.

Recovery action is resumed by controller again after the faultpreventing the recovery action has been corrected and if the problemaffecting the WCEL performance still remains.

Supplementary information fields1 this value indicates the type of failure that prevented the recovery action. Possible values are:

00 Amount of BTS restarts as recovery action has been used up. 01 BTS restart failed due to missing BTS O&M connection. 02 BTS restart failed due to no response from BTS. 03 BTS restart rejected by BTS due to ongoing BTS SW upgrade. 04 BTS restart failed because of invalid BTS O&M message. 05 BTS restart failed due to non-supported field value in BTS O&M message. 06 BTS restart failed due to unknown object type in BTS O&M message. 07 BTS restart failed due to controller internal errors.

2 this value indicates the cause that has led to recovery actions:

00 Common measurements are missing and common measurement recovery actions have failed. 01 Common measurement initialization constantly fails. 02 Common channel creation constantly fails. 04 Poor handover related radio link setup ratio. 05 Poor FACH RRC connection setup/complete ratio. 06 Constant radio link failure acknowledged by NodeB.

DN99580892 281




08 Base Station resource manager process family (BRM) hand crash in controller.

3 this value indicates the Local WCEL resource id for the WCEL that was detected not to be performing properly. In case the problem is not related to any specific WCEL (if the 2nd supplementary information field value is 08) then this value is set to FFFFFFFF (4294967295d).

4 this value indicates the allowed amount of WBTS recovery actions (restarts) per day. It is defined in PRFILE parameter RN22_FEATURE_OPT_009 (002:1296).

InstructionsCheck the reason for the recovery failure from the 1st supplementaryinformation field and proceed accordingly.

00: The amount of performed BTS restarts as recovery action per day exceeds the limit which is given in the 4th alarm supplementary information field. In this case the BTS cannot be restarted by controller until next midnight when controller resets the BTS specific restart amount counters. The BTS can be recovered manually by restarting it using either Element Manager or BTS Site Manager. Increasing the allowed BTS restart amount in PRFILE enables controller to perform additional restarts for BTS sites that have no recovery attempts left.

01: BTS O&M connection between BTS and controller is not available and restart could not be performed. See if controller alarm 7750 is active for possible details on the fault concerning the BTS O&M connection. Check also the status of BTS O&M connection from BTS Site Manager. See instructions below for possible need to perform manual recovery actions depending on the 2nd supplementary information field value.

02: BTS does not respond to the reset request. This may be due to high load in BTS side. Check the BTS status using BTS Site Manager and restart the BTS manually if possible. See instructions below for possible need to perform manual recovery actions depending on the 2nd supplementary information field value.

03: BTS software upgrade is ongoing and BTS cannot be restarted at the moment. BTS restarts after the software upgrade has been completed.

04, 05, 06: Unexpected error has occurred in BTS O&M message handling. The reason might be that controller and BTS do not use compatible version of the BTS O&M interface. Collect OMU computer log from controller and also logs from the BTS in question. Fill in a problem report and send it to the local Nokia Siemens Networks representative.

282 DN99580892




See instructions below for possible need to perform manual recovery actions depending on the 2nd supplementary information field value.

07: controller internal errors might be that reading BTS related information from database failed or there are already some other recovery actions going on for the BTS. See if alarms 7761 or 7762 have been set for the WBTS in question. See instructions below for possible need to perform manual recovery actions depending on the 2nd supplementary information field value.

Check also the value of the 2nd supplementary information field and,if it's value is 08 (BRM hand crash), proceed accordingly basedon the 1st supplementary information field value.

01, 02, 04, 05, 06, 07: In these recovery failure cases the BTS must be restarted manually using the BTS Site Manager or, if that is not possible for some reason, COCO/IPNB object disconnect and connect operation from the WBTS object in controller using Element Manager must be performed. Both of these operations trigger C-NBAP link re-establishment and cause a complete reinitialization of the cells. These user actions are required to ensure that cells are properly recovered after BRM hand crash.

Controller OMU computer log can also provide further informationabout the attempted recovery actions.IPA-RNC : "ZGSC:,50B" and "ZGSC:,4FA"Multi-Controller RNC or Flexi Direct RNC: Use command "grep -i rekove /var/log/syslog", Use command "grep -i rezini /var/log/syslog"

It is recommended that controller OMU logs (ZGSC and ZGLE for IPA-RNC)are collected together with BTS logs for possible further troubleshootingwhen this alarm is observed.Detailed logs can be collected from location "/srv/Log/log/" inthe Multi-Controller RNC/Flexi Direct RNC. This contains the detailedlogs for all the families.


DN99580892 283




53 7786 WCDMA BASE STATION OUT OF USEMeaning

This alarm indicates that there is a WBTS-level failure that causesall the WCELs in the WO state under this specific WBTS to becomeunavailable.

This alarm is set when a known fault occurs and makes allthe WCELs under a certain WBTS to become unavailable at once.The reasons for this are the C-NBAP link break or Base StationResource Manager (BRM) hand crash in the controller.

As a result of this alarm, the whole WBTS is unavailable for traffic.There can be also individual WCEL level alarms active for the WCELsof this WBTS if they were active prior to the WBTS level failuredetection.

This alarm is set only if there is at least one cell in the WO stateunder the WBTS.

This alarm is canceled when at least one WCEL under the WBTS isrecovered back to the WO state, or if the user locks all the WCELsunder the WBTS.

For more information on this functionality, see Nokia SiemensNetworks WCDMA RAN documentation concerning feature RAN1461.

Supplementary information fields1 reason why all the WCELs became unavailable at once. The possible reasons are: 00 = C-NBAP link break 01 = BRM hand crash 02 = Link switch failure during rebalancing operation

InstructionsThe 1st supplementary information field indicates the reason whythe whole WBTS became unavailable. The field contains thefirst observed reason for the problem. This means that duringrecovery actions the whole WBTS can become unavailable, but thereason can change. For example, it is possible that the BRM hand crashcauses the original problem, but after its recovery the C-NBAP linkcan be unavailable. The original alarm is kept active, as from thesystem point of view the whole WBTS is still unavailable.

To analyze and correct the problem, check the 1st supplementaryinformation field value.

00: C-NBAP link break

284 DN99580892




This can be caused by different underlying reasons that are indicated as the C-NBAP link break to RNW O&M: - a transmission break between controller and BTS resulting from, for example, a cable or external transmission equipment failure, a BTS restart performed using BTS Site Manager, or a controller network interface unit failure. - an internal controller failure, for example a spontaneous ICSU (IPA-RNC)/ Control plane unit (Multi-controller RNC/Flexi Direct RNC) restart.

In case of the C-NBAP link failure the recommendation is to wait for a couple of minutes and check if the disturbance is only temporary. The system recovers automatically once the transmission between the controller and BTS is available again. In case of a longer WBTS unavailability, it can be checked if the controller has active alarms for (IPA-RNC)/ Control plane unit (Multi-controller RNC/Flexi Direct RNC) or network interface units that can cause the C-NBAP link unavailability. The relation between WBTS and (IPA-RNC)/ Control plane unit (Multi-controller RNC/Flexi Direct RNC) unit can be seen from WBTS data using the Element Manager (the controller GUI for BTS Connection Resources dialog). 01: BRM hand crash The system recovers from the situation automatically. This reason may trigger non-performing cell recovery actions in controller, meaning that the BTS gets restarted by the controller. 02: Link switch failure during rebalancing operation This value is valid only in Multi-controller RNC and it indicates that the link switch for this BTS from donating CSCP to receiving CSCP has failed. This situation cannot be recovered automatically. WBTS-IPNB needs to be disconnected and then connected again to recover this WBTS.

As for the behavior of this alarm when the WBTS level failureindication in feature RAN1461 state is changed, note the following:

1. When the WBTS level fault functionality is switched from OFF to ON state, there are no effects on the existing WCEL alarms under a certain WBTS. The effect can be seen on the following alarms set by the system.

2. When the WBTS level fault functionality is switched from ON to OFF state, and if this alarm is active for a WBTS, the functionality for this particular WBTS is still considered as working. This means that the WBTS level failure alarm is kept active as long as all the WCELs for that WBTS remain unavailable.

DN99580892 285





286 DN99580892



7794 ALARM STATUS REQUEST HAS TIMED OUT

54 7794 ALARM STATUS REQUEST HAS TIMED OUTMeaning

The alarm indicates that due to the lack of the upload acknowledgementmessage from the BTS, the alarm upload cannot be started between the BTSand the controller.

The alarm is set when two consecutive alarm upload requests have beensent by the controller without an acknowledgement from the BTS.

If this alarm occurs, there can be a difference in alarm conditionsbetween the controller and the BTS.

The precondition to set this alarm is that the BTS O&M link is active.If the BTS O&M link is not active at the moment of the alarm uploadattempt, alarm 7750 is set instead.


InstructionsNo actions are needed in the controller. Use the BTS Site Manager to seethe operation status in the BTS end for an additional troubleshooting.

CancellingDo not cancel the alarm. The system cancels the alarm after the BTS hasacknowledged the alarm upload status request and when the upload can bestarted.

DN99580892 287


7795 INCONSISTENCY IN HIGH PEAK RATE HSPACONFIG


55 7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIGMeaning

The alarm indicates that the High Peak Rate HSPA configurationparameters (for DC HSDPA or Dual Band HSDPA or HSUPA IC) in atleast one WCEL of the BTS might not be consistent with theparameters in the RNC.In DC HSDPA case this alarm is also raised if the BTS loses itscapability of supporting DC HSDPA. This is also a result if userlocks one of the cells in the cell pair during maintenanceactivities.

The situation causing this alarm does not obstruct network operations.

The alarm is cell-specific, and not indicated to NetAct by default.Instead, the RNC-specific alarm 3325, "INCONSISTENCY IN CONFIGURATIONPARAMETERS", is reported on NetAct when first instance of 7795 is set.

The alarm 7795 is cancelled by the system when configuration at BTS andRNC is consistent for High Rate HSPA features (DC HSDPA, Dual Band HSDPAand HSUPA IC) or when the cell is deleted/locked.

Alarm indication preventions can be altered with MML command AFC inIPA-RNC.

Supplementary information fields1 possible error code values are:

* 746d = DC HSDPA NOT AVAILABLE local Cell in the BTS is not Multi Cell Capable, whereas the Controller has the DC HSDPA feature enabled in the cell

* 1352d = ADMINPICSTATE SET BY OPERATOR IS MISMATCHING WITH PIC STATE RECEIVED FROM NODE-B PICState at BTS and AdminPICState set by Controller are inconsistent

* 2139d = Local Cell is not Dual Band Capable local Cell in the BTS is not Dual Band Capable whereas the Controller has the Dual band HSDPA feature enabled in the cell

2 name of the feature for which the setup failed. Possible values:

* DCHSDPA = Dual Cell HSDPA * HSUPAIC = HSUPA Interference Cancellation

288 DN99580892



7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG

* DBHSDPA = Dual Band HSDPA

InstructionsThe situation causing this alarm does not obstruct network operations,and therefore no immediate actions are required. However, you can takethe following actions to ensure consistency in configuration parameters.

In case of DC HSDPA related problem, check first that the cell pair ofthe cell indicated in this alarm is not locked by user before proceedingto the steps given below. If that is the case, then the eventualunlocking of the DC HSDPA cell pair will clear this alarm.

1. Find the cells that might have inconsistency in configuration parameters by checking the alarms in the RNC. For these cells, proceed to step 2.

2. a) If the 2nd supplementary information field value is "DCHSDPA": Check the cell parameter WCEL - DCellHSDPAEnabled in the RNC using the OMS EM. BTS may reject the Dual Cell HSDPA configuration if the HW mapped for the Cell is not supporting HSPA, or if the frequency configuration is not properly done, so: - Check from BTS side that the HW mapped to the Cell resource is capable of providing HSPA. - Check from RNC side that the WCEL UARFCN configuration is done according to instructions given in RAN1906 feature activation manual. - If configuration parameters have inconsistency then lock the cell, correct WCEL UARFCN configuration as well as other parameterization as mentioned in RAN1906 feature activation manual. - Unlock the cell if were locked in previous step.

b) If the 2nd supplementary information field value is "HSUPAIC": Check the cell parameter WCEL - AdminPICState in the RNC using the OMS EM.

If AdminPICState is "enabled" then this alarm indicates that BTS failed to configure HSUPA IC. If AdminPICState is "disabled" then it indicates that BTS has not disabled HSUPA IC even though configuration at RNC is changed to disable HSUPA IC. In such cases, proceed to step-3.

c) If the 2nd supplementary information field value is "DBHSDPA": Check the cell parameter WCEL- DBandHSDPAEnabled in the Controller using the OMS EM. BTS may reject the Dual Band HSDPA configuration if the HW mapped for the Cell is not supporting HSPA, or if the frequency configuration is not properly done, so: - Check from BTS side that the HW mapped to the Cell resource is

DN99580892 289


7795 INCONSISTENCY IN HIGH PEAK RATE HSPACONFIG


capable of providing HSPA. - Check from RNC side that the WCEL UARFCN configuration is done according to instructions given in RAN1906 feature activation manual. - If configuration parameters have inconsistency then lock the cell, correct WCEL UARFCN configuration as well as other parameterization as mentioned in RAN1906 feature activation manual. - Unlock the cell if were locked in previous step.3. Check if there are any BTS end failures that are indicated with 76xx alarms and that could affect this feature (e.g. some HW unit failure) Check if the relevant BTS is in the working state using the OMS EM. If the working state of the BTS and the BTS HW configuration are correct while this fault still occurs, contact the local Nokia Siemens Networks representative.

More information about the exact failure reason can be found by examiningthe 1st supplementary information field (error code). You can check itsmeaning in IPA-RNC with a command of the service terminal extensionMRS (see Service Terminal Essentials, Maintenance Manual), inmulti-controller RNC / Flexi Direct RNC using CLI command"dxserrcli <error code>" or from the document GeneralError Messages of System, Supplementary References.For more information about configuring DC HSDPA and DB HSDPA features,see the respective feature activation manuals in product documentation.

CancellingDo not cancel the alarm. The system cancels the alarm after the BTS hasindicated to the RNC that it supports the high peak rate HSPA feature inthe cell in case of DC HSDPA or Dual band HSDPA or BTS and RNC hasconsistent PIC States in case of HSUPA IC. The alarm will also becancelled when the cell is deleted or locked.

290 DN99580892




56 7796 HIGH SPEED COMMON CHANNEL PROBLEMMeaning

This alarm indicates a failure in HS FACH or HS RACH common channelsin the cell. It is set for the cell when- the creation of HS FACH/HS RACH common channel fails- the capability of the WCEL mismatches with HS FACH/HS RACH capability on BTS side- HS FACH/HS RACH common channels are unavailable due to sync loss between BTS and RNC.If this alarm is raised, then UE DRX feature becomes out of use(if it was already enabled) as both features (HS FACH and HS RACH)are pre-requisite for operation of UE DRX feature.

Supplementary information fields1 error code, possible values are:

- 1315d = High speed cell FACH is enabled in the controller but Disabled or not supported in the BTS.

- 1316d = Synchronization between the BTS and controller is lost for HS FACH channels and those are unavailable.

- 1914d = High Speed Cell FACH UL is enabled in the controller

but disabled or not supported in the BTS.

- Besides these above specific error code, there can be other error code corresponding to failures identified during High Speed FACH/ HS RACH channel creation. For instance, insufficient DSP resources.

InstructionsCase 1) The first supplementary information field value is 1315d (enh_fach_capb_mismatch_ec).

Possible reasons:

- There is a mismatch of the HS-DSCH channel configuration between the controller and BTS. - BTS HW does not support HS FACH common channels - BTS runs out of capability due to, for example, a HW failure.

Actions to be taken:

1) Check if there are any BTS end failures that are indicated with 76xx alarms and that could affect this feature (for example some HW unit failure).

DN99580892 291




2) Check if the relevant BTS is in the working state using the controller Element Manager. If so, check whether the BTS HW configuration is correct so that Enhanced HSFACH can be supported. If the working state of the BTS and the BTS HW configuration are correct while this fault still occurs, contact the local Nokia Siemens Networks representative.

Case 2) When the first supplementary information field value is 1316d (hs_cch_sync_ec):

Possible Reason:

Synchronization between the controller and BTS is lost for the HS FACH common channel.


The continuous recovery is performed by the controller. An attempt can be made to solve the problem by locking and unlocking the cell manually.

Case 3) The first supplementary information field value is 1914d (enh_rach_capb_mismatch_ec).

Possible reasons:

- There is a mismatch of the E-DCH channel configuration between the controller and BTS. - BTS HW does not support HS RACH common channels - BTS runs out of capability due to, for example, a HW failure.


1) If the fault is related to the RNW configuration, check the E-DCH configuration of this WBTS object in the controller using the Element Manager, and the configuration in the BTS using the BTS Manager.

2) Check if the relevant BTS is in the working state using the

controller Element Manager. If so, check whether the BTS HW configuration is correct so that Enhanced HS RACH can be

supported.

If the working state of the BTS and the BTS HW configuration

292 DN99580892




are correct while this fault still occurs, contact the local Nokia Siemens Networks representative.

If the fault cannot be fixed by correcting the configuration, checkingother BTS alarms, or continuous recovery attempts on the cell, contactthe local Nokia Siemens Networks representative.

For information on the exact reason of the failure, see the 1stsupplementary information field. You can check its meaning with acommand of the service terminal extension MRS (see Service TerminalEssentials, Maintenance Manual) or in the document General ErrorMessages of System, Supplementary References.

For more information, you can also examine the OMU computer logaccessed with the MML command ZDDE::"ZGSC" in IPA-RNC and inMulti-Controller RNC/Flexi Direct RNC logs can be found at location inthe product "/srv/Log/log/".


The alarm is cancelled when either of the following occurs:

- The creation of HS FACH/HS RACH common channel in the cell is successful. - The cell is deleted from the Node-B. - The cell is deleted internally from the controller as a result of the audit procedure.

Any earlier instance of this alarm in a WCEL is cancelled whenthe alarm is set with cause 1315d (enh_fach_capb_mismatch_ec).Any earlier instance of this alarm raised to indicate the transportchannel failure with cause 1316d (hs_cch_sync_ec) is cancelled whenthe request for setting the alarm is received with any another causefor the same cell.

rnc base station alarm

Documents

trademark of nokia solutions

use of nokia solutions

networks customers

operating documentation

product safetythis product

safety information applicable

product names

safety information section