alarm_3g_ru_30

7/25/2019 Alarm_3G_RU_30

http://slidepdf.com/reader/full/alarm3gru30 1/335

WCDMA RAN and I-HSPA, Rel.

RU30, Operating

Documentation, Issue 08

Multicontroller RNC, IPA-RNC and I-HSPA

Adapter Base Station Alarms (7000-7900)

DN99580892

Issue 09F

Approval Date 2012-05-28

Confidential

7/25/2019 Alarm_3G_RU_30


2 DN99580892

Issue 09F

Multicontroller RNC, IPA-RNC and I-HSPA Adapter Base Station Alarms (7000-7900)

Id:0900d80580938c03

Confidential

The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted

in any form or means without the prior written permission of Nokia Siemens Networks. The

documentation has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes

customer comments as part of the process of continuous development and improvement of the

documentation.

The information or statements given in this documentation concerning the suitability, capacity,

or performance of the mentioned hardware or software products are given "as is" and all liability

arising in connection with such hardware or software products shall be defined conclusively and

finally in a separate agreement between Nokia Siemens Networks and the customer. However,

Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions

contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO

EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-

TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-

RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED

TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY

OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION

IN IT.

This documentation and the product it describes are considered protected by copyrights and

other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark

of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2012. All rights reserved

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

of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle

this product and only after having carefully read the safety information applicable to this

product.

The safety information is provided in the Safety Information section in the “Legal, Safety

and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur ProduktsicherheitVon diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder

andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch

geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-

anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,

Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-

satzes.

7/25/2019 Alarm_3G_RU_30


DN99580892 3

Multicontroller RNC, IPA-RNC and I-HSPA AdapterBase Station Alarms (7000-7900)

Id:0900d80580938c03

Confidential

Table of contentsThis document has 336 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3323 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 . . . . . . . . . . . . . . . . 74

30 7652 BASE STATION NOTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . 131

7/25/2019 Alarm_3G_RU_30


4 DN99580892


Id:0900d80580938c03

Confidential

31 7653 CELL FAULTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

32 7654 CELL OPERATION DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . 192

33 7655 CELL NOTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

34 7660 BASE STATION LICENCE EXPIRED . . . . . . . . . . . . . . . . . . . . . 256

35 7661 BASE STATION LICENCE NOTIFICATION . . . . . . . . . . . . . . . . 258

36 7665 BASE STATION TRANSMISSION ALARM. . . . . . . . . . . . . . . . . 261

37 7740 BEATING WCDMA BTS ALARM. . . . . . . . . . . . . . . . . . . . . . . . . 283

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

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

40 7762 RNW DATABASE OPERATION FAILURE . . . . . . . . . . . . . . . . . 294

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

42 7772 HSDPA CONFIGURATION FAILED . . . . . . . . . . . . . . . . . . . . . . 300

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

44 7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS . .

306

45 7776 HSDPA FAILURE IN WCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

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

47 7779 RECOVERY ACTIONS ONGOING . . . . . . . . . . . . . . . . . . . . . . . 312

48 7780 HSUPA FAILURE IN WCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

49 7781 NETWORK ELEMENT CONFIGURATION ERROR . . . . . . . . . . 316

50 7782 HSUPA CONFIGURATION FAILED . . . . . . . . . . . . . . . . . . . . . . 318

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

52 7784 RECOVERY ACTION FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . 324

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

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

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

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

7/25/2019 Alarm_3G_RU_30


DN99580892 5


Summary of Changes

Id:0900d80580938c2b

Confidential

Summary of ChangesChanges between document issues are cumulative. Therefore, the latest document

issue contains all changes made to previous issues.

Changes made between issues 09E and 09F

Modified alarms

Changes made between issues 09D and 09E

Modified alarms

Removed alarms

Changes made between issues 09C and 09D

Modified alarms

7650 7653 7660 7795

7651 7654 7661

7652 7655 7665

7772 7782 7795 7796

7799

7781 7796

7/25/2019 Alarm_3G_RU_30


6 DN99580892


Id:0900d80580938c2b

Confidential

List of Alarms

1 List of Alarms7401 EXTERNAL AL 1

7402 EXTERNAL AL 27403 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

7/25/2019 Alarm_3G_RU_30


DN99580892 7


List of Alarms

Id:0900d80580938c2b

Confidential

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 parameters

The following parameter settings are the default settings. The operator can modify them

with an MML 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 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


00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -


7/25/2019 Alarm_3G_RU_30


8 DN99580892


Id:0900d80580938c2b

Confidential

List of Alarms


00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 - EVENT TYPE: ENVIRONMENTAL

7/25/2019 Alarm_3G_RU_30


DN99580892 9


List of Alarms

Id:0900d80580938c2b

Confidential


00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 -



00:10 - 00:10 - EVENT TYPE: ENVIRONMENTAL


00:10 - 00:10 -



00:10 - 00:10 -


7650 BASE STATION FAULTY *** 0

00:10 - 00:10 -

EVENT TYPE: EQUIPMENT

7651 BASE STATION OPERATION DEGRADED ** 5

00:10 - 00:10 -


7652 BASE STATION NOTIFICATION * NONE

00:10 - 00:10 -


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

7/25/2019 Alarm_3G_RU_30


10 DN99580892


Id:0900d80580938c2b

Confidential

List of Alarms


7654 CELL OPERATION DEGRADED ** 5

00:10 - 00:10 -


7655 CELL NOTIFICATION * NONE

00:10 - 00:10 -


7660 BASE STATION LICENCE EXPIRED *** 0

00:10 - 00:10 -


7661 BASE STATION LICENCE NOTIFICATION * NONE

00:10 - 00:10 - EVENT TYPE: EQUIPMENT

7665 BASE STATION TRANSMISSION ALARM * NONE

00:10 - 00:10 -


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 -


7771 WCDMA CELL OUT OF USE ** 5

02:00 - 00:20 -


7772 HSDPA CONFIGURATION FAILED ** 5

00:05 - 00:05 -


7773 INSECURE O&M CONNECTION ** 5

00:00 - 00:00 -


7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS * NONE

7/25/2019 Alarm_3G_RU_30


DN99580892 11


List of Alarms

Id:0900d80580938c2b

Confidential

00:00 - 00:00 -


7776 HSDPA FAILURE IN WCEL ** 5

00:05 - 00:00 -


7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE ** 5

00:00 - 00:00 -


7779 RECOVERY ACTIONS ONGOING * NONE

00:00 - 00:00 -


7780 HSUPA FAILURE IN WCEL ** 5 00:05 - 00:00 -


7781 NETWORK ELEMENT CONFIGURATION ERROR *** 2

00:00 - 00:00 -


7782 HSUPA CONFIGURATION FAILED ** 5

00:05 - 00:05 -


7783 IP BASED D-NBAP LINK FAILURE ** 5

00:30 - 00:30 -


7784 RECOVERY ACTION FAILURE ** 5

00:00 - 00:00 -


7786 WCDMA BASE STATION OUT OF USE ** 5

00:30 - 00:15 -


7794 ALARM STATUS REQUEST HAS TIMED OUT ** 5

00:00 - 00:00 -


7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG * NONE

00:00 - 00:00 -


7796 HIGH SPEED COMMON CHANNEL PROBLEM * NONE

00:05 - 00:00 -


7/25/2019 Alarm_3G_RU_30


12 DN99580892


Id:0900d80580938c2b

Confidential

List of Alarms

7/25/2019 Alarm_3G_RU_30


DN99580892 13


7401 EXTERNAL AL 1

Id:0900d80580938c2b

Confidential

2 7401 EXTERNAL AL 1

Meaning

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

Supplementary information fields

Instructions

The operation depends on what kind of alarm is used as external

alarm no. 1.

Cancelling

Do not cancel the alarm. The system cancels the alarm automatically

when the fault has been corrected.

7/25/2019 Alarm_3G_RU_30


14 DN99580892


Id:0900d80580938c2b

Confidential

7402 EXTERNAL AL 2


Meaning

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


Instructions


alarm no. 2.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 15


7403 EXTERNAL AL 3

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 3.

Cancelling



7/25/2019 Alarm_3G_RU_30


16 DN99580892


Id:0900d80580938c2b

Confidential

7404 EXTERNAL AL 4


Meaning



Instructions


alarm no. 4.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 17


7405 EXTERNAL AL 5

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 5.

Cancelling



7/25/2019 Alarm_3G_RU_30


18 DN99580892


Id:0900d80580938c2b

Confidential

7406 EXTERNAL AL 6


Meaning



Instructions


alarm no. 6.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 19


7407 EXTERNAL AL 7

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 7.

Cancelling



7/25/2019 Alarm_3G_RU_30


20 DN99580892


Id:0900d80580938c2b

Confidential

7408 EXTERNAL AL 8


Meaning



Instructions


alarm no. 8.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 21


7409 EXTERNAL AL 9

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 9.

Cancelling



7/25/2019 Alarm_3G_RU_30


22 DN99580892


Id:0900d80580938c2b

Confidential

7410 EXTERNAL AL 10


Meaning



Instructions


alarm no. 10.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 23


7411 EXTERNAL AL 11

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 11.

Cancelling



7/25/2019 Alarm_3G_RU_30


24 DN99580892


Id:0900d80580938c2b

Confidential

7412 EXTERNAL AL 12


Meaning



Instructions


alarm no. 12.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 25


7413 EXTERNAL AL 13

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 13.

Cancelling



7/25/2019 Alarm_3G_RU_30


26 DN99580892


Id:0900d80580938c2b

Confidential

7414 EXTERNAL AL 14


Meaning



Instructions


alarm no. 14.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 27


7415 EXTERNAL AL 15

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 15.

Cancelling



7/25/2019 Alarm_3G_RU_30


28 DN99580892


Id:0900d80580938c2b

Confidential

7416 EXTERNAL AL 16


Meaning



Instructions


alarm no. 16.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 29


7417 EXTERNAL AL 17

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 17.

Cancelling



7/25/2019 Alarm_3G_RU_30


30 DN99580892


Id:0900d80580938c2b

Confidential

7418 EXTERNAL AL 18


Meaning



Instructions


alarm no. 18.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 31


7419 EXTERNAL AL 19

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 19.

Cancelling



7/25/2019 Alarm_3G_RU_30


32 DN99580892


Id:0900d80580938c2b

Confidential

7420 EXTERNAL AL 20


Meaning



Instructions


alarm no. 20.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 33


7421 EXTERNAL AL 21

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 21.

Cancelling



7/25/2019 Alarm_3G_RU_30


34 DN99580892


Id:0900d80580938c2b

Confidential

7422 EXTERNAL AL 22


Meaning



Instructions


alarm no. 22.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 35


7423 EXTERNAL AL 23

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 23.

Cancelling



7/25/2019 Alarm_3G_RU_30


36 DN99580892


Id:0900d80580938c2b

Confidential

7424 EXTERNAL AL 24


Meaning



Instructions


alarm no. 24.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 37


7425 EXTERNAL AL 25

Id:0900d80580938c2b

Confidential


Meaning



Instructions


alarm no. 25.

Cancelling



7/25/2019 Alarm_3G_RU_30


38 DN99580892


Id:0900d80580938c2b

Confidential

7426 EXTERNAL AL 26


Meaning


The effect of the alarm depends on the purpose that was configured for

the user-defined alarm input in the BTS.


Instructions

The operation depends on the type of alarm that is used as external

alarm number 26.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 39



Id:0900d80580938c2b

Confidential

28 7650 BASE STATION FAULTY

Meaning

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

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

the alarm.

The effect of the fault on the functioning of the network element

depends on the fault description. For more information, see base

station fault descriptions in WCDMA RAN and I-HSPA System Libraries.


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

Instructions

Verify the configuration of a BTS by checking the

commissioning, cabling and correct installation of the

units/modules at the BTS. Make sure the environment does

not cause the fault.

Before a unit/module is replaced at the BTS, the site

should be reset to recover from any temporary faults whichmight have caused the malfunctioning of the unit/module.

When an active alarm is a 'Start' alarm, a site reset is

required to cancel the alarm. If the site reset or module

block/unblock does not help, replace the faulty unit/module

(see the source of the alarm and instructions fields of the

corresponding alarms).

Below is the list of BTS fault(s) which might have caused

this alarm in BTS WN 7.0.2.0 release. In case of earlier SW

release and in case you need more detailed fault

descriptions refer to WCDMA RAN and I-HSPA System

Libraries. The BTS fault descriptions are also included in

7/25/2019 Alarm_3G_RU_30


40 DN99580892


Id:0900d80580938c2b

Confidential


BTS SW release documentation. If that does not help,

contact your local Nokia Siemens Networks representative.

FAULT NAME : ATM faulty

FAULT ID : 45: EFaultId_ATM_SFN_PollingTimeoutAl

MEANING : 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 faulty

FAULT ID : 590: EFaultId_AtmMcuBrokenAl

594: EFaultId_SfnIrqFailureAl

MEANING : 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 a fault in the FSM such 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.


is working, restart the AXC remotely so that the BTS is

also automatically restarted.



alarming WAM unit.

FlexiBTS:

1. Reset the BTS.

2. If the BTS reset does not help, change the alarming

7/25/2019 Alarm_3G_RU_30


DN99580892 41



Id:0900d80580938c2b

Confidential

module.

FAULT NAME : Antenna link is down

FAULT ID : 476: EFaultId_Rp3BusError

MEANING : Antenna (RP3) link is down: transmitter or receiver drops

from synchronization.

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

2. If that does not help, replace the alarming FSM.

UltraSite/EUBB:

1. If the alarming unit is WSPF, restart the BTS. If all

WSPFs generate this alarm, restart the BTS.

2. If that does not help, replace the WSMF.

FAULT NAME : BB bus message collision error

FAULT 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 reception error

FAULT ID : 2044: EFaultId_TransuSMTimeOffAl

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

7/25/2019 Alarm_3G_RU_30


42 DN99580892


Id:0900d80580938c2b

Confidential


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_SMTimeOffAl

MEANING : The master frame in the received baseband bus frame is not

in the correct place related to the internally generated

master frame pulse. Either the frame has been set into the

wrong place (PI delay) or the data itself is in the wrong

place.


1. Check the cables between the Master System Module and RF

Module/Extension System Module.

2. Replace the unit that is causing the fault (Master

System Module, Extension System Module, RF Module, FBIA).

UltraSite/EUBB:

1. Replace the unit that is causing the fault (WSPF, WSMF).

FAULT NAME : BB bus transmission error

FAULT ID : 2017: EFaultId_Muksu_SRx10b8bAl

MEANING : A decoding error has been detected in the baseband internal

link. The data packet is lost or the content is corrupted.

This situation is also triggered when the links do not

synchronize with each other.




2. Replace the alarming unit (System Module).

UltraSite/EUBB:

1. Replace the alarming unit (WSMF).

FAULT NAME : BOFU Post failed

FAULT ID : 4021: EFaultId_BOFU_Post_failedAlMEANING : The unit or module has been tested during BTS power-on self

7/25/2019 Alarm_3G_RU_30


DN99580892 43



Id:0900d80580938c2b

Confidential

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 Blocked

FAULT ID : 50: EFaultId_BTSBlockedAl

MEANING : 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 the BTS

causes a site reset.

FAULT NAME : BTS config error (WSMA and WSMB can not coexist)

FAULT ID : 55: EFaultId_WsmaWsmbVersionConflictAl

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

FAULT NAME : BTS configuration not supported

FAULT ID : 4097: EFaultId_BtsConfNotSupportedAl

MEANING : 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 error

FAULT ID : 1802: EFaultId_FileRequestFlashAl

1803: EFaultId_FileParsingFailedAl

1866: EFaultId_RulesMissingAl

1867: EFaultId_RulesParsingAl

MEANING : 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

7/25/2019 Alarm_3G_RU_30


44 DN99580892


Id:0900d80580938c2b

Confidential


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:




3. Replace the System Module.


FAULT ID : 136: EFaultId_TcomConfFileAl

MEANING : Telecom configuration file(s) are invalid, missing, or not

accessible.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode,

UltraSite/EUBB:





alarming unit.

FlexiBTS:




3. Replace the System Module or FBIA.

FAULT NAME : BTS internal SW management problemFAULT ID : 3090: EFaultId_BtsInternalSwManagementProblem

7/25/2019 Alarm_3G_RU_30


DN99580892 45



Id:0900d80580938c2b

Confidential

MEANING : 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 until the

BTS fault indication disappears.

FlexiBTS:

1. Check the other active BTS faults. If the ROM disk is

corrupted, change the alarming module.

2. Reset the RF Module and/or 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:


corrupted, change the alarming unit.

2. Reset the alarming unit.



5. Replace the alarming unit.

FAULT NAME : BTS is uncommissioned

FAULT ID : 4030: EFaultId_NoCommDataAl

MEANING : Commissioning file download has not started from BTS Site

Manager nor from NetAct during autoconfiguration.

INSTRUCTIONS: 1. Check that autoconfiguration is enabled in NetAct.

2. Check the autoconnection/autoconfiguration information

with BTS Site Manager.

3. Load the correct commissioning file to BTS.

7/25/2019 Alarm_3G_RU_30


46 DN99580892


Id:0900d80580938c2b

Confidential


FAULT NAME : Baseband Bus failure

FAULT ID : 3020: EFaultId_BaseBandBusFailure

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


alarm disappears.

FlexiBTS:

1. Check the other active BTS alarms and act accordingly.



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

the alarm source:


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:



3. Check the cables in backplane.


FAULT NAME : Baseband bus configuration of <x> was rejected

FAULT ID : 1811: EFaultId_BbBus_ConfFailedAl

MEANING : The baseband bus related configuration of <x> was rejected

by the HW, SW, DSP, or LTX.

INSTRUCTIONS: Replace the alarming module.

FAULT NAME : Baseband loop test failureFAULT ID : 4016: EFaultId_Srio_TestFailedWithinBoardAl

7/25/2019 Alarm_3G_RU_30


DN99580892 47



Id:0900d80580938c2b

Confidential

MEANING : The test message sent to the baseband link (SRIO) did not

return within the required time.


1. Reset the BTS.

2. Replace the faulty module.

UltraSite/EUBB:

1. If the alarming module is WSPF, restart it by

blocking/unblocking.

2. If that does not help, replace the alarming WSPF.

FAULT NAME : Baseband reference clock missing (WCI)

FAULT ID : 1006: EFautlId_BaseBandReferenceClkMss

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

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_DualWscBrclkMss

MEANING : The WSC is not able to deliver the clock signals required

by the other units.

INSTRUCTIONS: Replace the WSC.

FAULT NAME : Commissioning error: <x>

FAULT ID : 3060: EFaultId_CommissioningError

MEANING : Some of the commissioning parameters are either missing or

faulty, or there is a mismatch between them.


alarm disappears.

1. Check the commissioning parameters with the BTS Site

7/25/2019 Alarm_3G_RU_30


48 DN99580892


Id:0900d80580938c2b

Confidential


Manager Commissioning Wizard.

2. Load the correct commissioning file to the BTS.

FAULT NAME : Communication failure

FAULT ID : 1806: EFaultId_CommunicationFailureAl

MEANING : Communication with the application <x> failed. It has not

replied to the message that has been sent/resent to it.

INSTRUCTIONS: 1. Check that the unit/module is properly connected. If the

unit/module LED does not light up, the unit/module is

faulty. Check the alarming unit/module.

2. Check the fault history.


FAULT ID : 458: EFaultId_VcpError

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


FAULT NAME : Communication failure inside WSP

FAULT ID : 414: EFaultId_McbspMessagePoolExhausted

446: EFaultId_McbspSwsError

MEANING : An internal communication failure between the DSP

processors.


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.

7/25/2019 Alarm_3G_RU_30


DN99580892 49



Id:0900d80580938c2b

Confidential




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_ConfigurationError

MEANING : There is a compatibility problem in the BTS HW/SW versions

or the HW/HW configuration. Another possibility is that

there is a mismatch between the BTS configuration and the

RNC/I-HSPA adapter parameters.

INSTRUCTIONS: Note: Perform the steps below in the listed order until the BTS fault indication disappears.

1. Check the installed HW/SW version compatibility and the

HW compatibility with the current BTS configuration.

2. Check that the BTS cell parameters from the RNC/I-HSPA

adapter match the BTS HW configuration (for example

frequency, power).

3. Check the RNC/I-HSPA adapter BTS faults for the alarming

local cell (LCR).

4. Recommission the BTS to ensure that all parameters are

correctly configured.

FAULT NAME : Configuration file is not supported

FAULT ID : 4035: EFaultId_ConfigurationFileNotSupportedAl

MEANING : BTS software does not support the commissioning file

downloaded to the BTS.

INSTRUCTIONS: 1. Check and correct the contents of the commissioning

file.

7/25/2019 Alarm_3G_RU_30


50 DN99580892


Id:0900d80580938c2b

Confidential


2. Download the corrected commissioning file to the BTS and

reset it.

FAULT NAME : Connection to transmission broken

FAULT ID : 1829: EFaultId_ConnToTransBrokenAl


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.


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:


2. Reset the site.

3. If that does not help, replace the alarming System

Module.

FAULT NAME : DSC-bus failure

FAULT ID : 208: EFaultId_DscNodeBlockedAl

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



FAULT ID : 597: EFaultId_DscFaultAl

MEANING : There are communication problems between the WAM and WSP. This alarm may occur if the WSP is hot removed or the WSP

7/25/2019 Alarm_3G_RU_30


DN99580892 51



Id:0900d80580938c2b

Confidential

crashes.

INSTRUCTIONS: If the failure still exists after the site reset, replace

the WAM unit.

FAULT NAME : DSP accelerator initialization failure

FAULT ID : 2302: EFaultId_RsaInitializationError

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



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


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 creation

FAULT ID : 129: EFaultId_DspHoldAl

MEANING : Radio link creation has failed repeatedly because of DSP

rejection.


1. Block/unblock the alarming unit.


UltraSite/EUBB:

1. Block/unblock the EUBB subrack.


7/25/2019 Alarm_3G_RU_30


52 DN99580892


Id:0900d80580938c2b

Confidential


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 failed

FAULT ID : 139: EFaultId_DspModeChangeFailAl

MEANING : DSP configuration to correct mode was not successful.

INSTRUCTIONS: Replace the alarming module/unit.

FAULT NAME : DSP overheated

FAULT 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 failure

FAULT ID : 2031: EFaultId_Transu_DlDbSynchChAl

MEANING : The downlink data buffer has lost synchronization.

INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.




Module).

FAULT NAME : FSP in resetting state

FAULT ID : 4068: EFaultId_FspResetAl

MEANING : FSP is undergoing a cold reset.


fault disappears:

1. Reset the BTS.

2. Replace the faulty module/unit.

FAULT NAME : FSP/WSP Frame synchronisation failed

7/25/2019 Alarm_3G_RU_30


DN99580892 53



Id:0900d80580938c2b

Confidential

FAULT ID : 1822: EFaultId_Fr_SyncAl

MEANING : 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 interface

FAULT ID : 3030: EFaultId_FailureInOptical_Rp3Interface


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.



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


4. Replace the alarming module's Small Form Factor

Pluggable (SFP). Check also the SFP in the other end and

replace it, if needed.


6. If the System Module is the only alarming source or

replacing the RF Module/Extension System Module does not

clear the fault situation, replace the alarming System

Module.

FAULT NAME : Failure in replaceable baseband unit

FAULT ID : 3003: EFaultId_FbiaFailureAl


the BTS replaceable

baseband unit.



1. Check the other active BTS faults and act accordingly.

7/25/2019 Alarm_3G_RU_30


54 DN99580892


Id:0900d80580938c2b

Confidential


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 Error

FAULT ID : 418: EFaultId_OseFatalErr

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


Note! Perform the steps below in the listed order until the

fault disappears.

1. Reset the System Module.


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.


FAULT NAME : Fault between WAM and WSP SFN (WSP)

FAULT ID : 412: EFaultId_LostFrameSync

428: EFaultId_SystemFrameNumberParity


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.

7/25/2019 Alarm_3G_RU_30


DN99580892 55



Id:0900d80580938c2b

Confidential


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.


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.




Module) or faulty FBIA.

UltraSite/EUBB: 1. If only one WSPF in the BTS generates this alarm, the

WSPF is faulty.




FAULT NAME : Fault in ATM interface

FAULT ID : 309: EFaultId_AtMuxAl

MEANING : The WAM ATM interface is not responding correctly.

INSTRUCTIONS: 1. Block/unblock the alarming unit. This resets the BTS.



FAULT ID : 591: EFaultId_SarChipBrokenAl

592: EFaultId_UxAsicAl 593: EFaultId_AtmHostBrokenAl

7/25/2019 Alarm_3G_RU_30


56 DN99580892


Id:0900d80580938c2b

Confidential


MEANING : 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 interface

FAULT ID : 42: EFaultId_ WSPC_PPC_SFN_PollingTimeoutAl

43: EFaultId_DSP_PollingTimeoutAl


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.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode:



UltraSite/EUBB:



FlexiBTS:

1. Block/unblock the alarming module.

2. Replace the system module/plug-in FSP.

FAULT NAME : File System access failed

FAULT ID : 4088: EFaultId_FileSystemAccessFailedAl

MEANING : File System access operation such as: - file opening failed

7/25/2019 Alarm_3G_RU_30


DN99580892 57



Id:0900d80580938c2b

Confidential

- file deletion

INSTRUCTIONS: Update SW to the BTS, unless it is automatically updated by

NetAct.

FAULT NAME : Frame clock deviation fault

FAULT ID : 2014: EFaultId_Muksu_SFCRCompDevAl

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.




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 synchronisation error in optical interface

FAULT ID : 2047: EFaultId_OIC_FrSyncLostAl

MEANING : The timing of the new RP1 synchronization burst deviates

from the present RP1 timing maintained in the BTS.

INSTRUCTIONS: 1. Reset the System Module that causes the alarm.

2. If resetting of the module does not help, replace the

System Module that causes the alarm.

FAULT NAME : Incompatible SW version detected

FAULT ID : 23: EFaultId_IncompatibleSwVersionAl

24: EFaultId_ObsoleteSwVersionAl

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

Related BTS - AXC interface: check the SW version of the

7/25/2019 Alarm_3G_RU_30


58 DN99580892


Id:0900d80580938c2b

Confidential


BTS and AXC, and update compatible SW to the AXC or BTS.

FAULT NAME : Incompatible unit detected

FAULT ID : 83: EFaultId_WtraWsmaWspaNotSupportedInCabinetAl

91: EFaultId_WrongUnitTypeInCabinetAl

MEANING : 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 failure

FAULT 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 error

FAULT ID : 4087: EFaultId_InternalCommunicationErrorAl

MEANING : 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. Check that the unit/module is properly connected.



FAULT NAME : Internal delay measurement failure

FAULT ID : 1893: EFaultId_InternalDelayMeasurementFailureAl

MEANING : 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 file

FAULT ID : 4036: EFaultId_InvalidConfigurationFileAl

MEANING : The commissioning file is missing, or an incorrect commissioning file has been detected during BTS startup as

7/25/2019 Alarm_3G_RU_30


DN99580892 59



Id:0900d80580938c2b

Confidential

follows: "Validation failed because of incompatible data"


file.

2. Recommission the BTS with the valid commissioning file.

FAULT NAME : Master unit has lost connection to the slave unit

FAULT ID : 4019: EFaultId_KeepAliveStatusErrorAl

MEANING : Connection to the DSP submodule has been lost or the

submodule reports an error situation.


fault disappears:

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

FAULT NAME : Module dangerously overheating

FAULT ID : 4071: EFaultId_SysDangerouslyOverheatAl

MEANING : 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 : Module not supported by current SW version

FAULT ID : 4063: EFaultId_NotSupportedModuleMixAl

MEANING : An unsupported module was found in the System Module.

Typically this happens when a System Module SW in use does

not support using the module.

INSTRUCTIONS: Replace the not supported module or upgrade the System

Module SW.

FAULT NAME : No baseband capacity for common channels

FAULT ID : 132: EFaultId_NoBBCapasityForCommonChannels

MEANING : 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/Faraday card is

fully reserved).

INSTRUCTIONS: None

7/25/2019 Alarm_3G_RU_30


60 DN99580892


Id:0900d80580938c2b

Confidential


FAULT NAME : No connection to AXU

FAULT ID : 21: EFaultId_AxuResetAl

MEANING : 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_NoConnectionToFtAl

MEANING : The connection to the BTS transport submodule is lost.


alarm disappears.

1. Reset the site.

2. Replace the Transport submodule, which is located inside

the System Module.

FAULT NAME : No connection to unit

FAULT ID : 10: EFaultId_NoConnectionToUnitAl

4052: EFaultId_ConnectionToUnitLostAl

MEANING : The connection to a unit that belongs to the BTS

configuration has been lost.


UltraSite/EUBB:

1. Check the fault history, alarming unit, and subrack.

2. If SW 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 might

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


7/25/2019 Alarm_3G_RU_30


DN99580892 61



Id:0900d80580938c2b

Confidential

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 WSMF unit BTS works as

UltraSite not as EUBB.

FlexiBTS:

1. Check that the module is properly connected. If the

module LED does not light up, the module is faulty. Check

the alarming module.


FAULT NAME : Not able to synchronize baseband bus with <x>

FAULT ID : 1815: EFaultId_BbBus_SyncFailedAl

MEANING : The baseband bus synchronization towards <x> failed.

INSTRUCTIONS: Replace the alarming module/plug-in FSP.

FAULT NAME : Optical Interface Frame clock faulty

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

2. Replace the FSM.

FAULT NAME : Optical interface FPGA sw crc check failed

FAULT ID : 1830: EFaultId_FpgaCrcCheckFailAl

MEANING : The CRC check has failed in three consecutive optical

interface FPGA SW downloading attempts.


FAULT NAME : Oven oscillator Missing Pulse

FAULT ID : 1820: EFaultId_OcxoPulseMissingAl

MEANING : The output signal of the OXCO has some problems and one or

more clock pulses are missed.


7/25/2019 Alarm_3G_RU_30


62 DN99580892


Id:0900d80580938c2b

Confidential


2. Replace the FSM.

FAULT NAME : Oven oscillator clock missing

FAULT ID : 903: EFaultId_OcxoClkMss

911: EFaultId_DualWscOcxoClkMss


by the other units.

INSTRUCTIONS: Replace the clock unit.


FAULT ID : 1819: EFaultId_OcxoClkMissAl

MEANING : The output signal of the OXCO is missing and the FCM cannot deliver the 30.72 MHz System Clock required by the other

units.


2. Replace the FSM.

FAULT NAME : Oven oscillator heating failure

FAULT ID : 1817: EFaultId_Ov_Osc_HeatAl

MEANING : The OCXO warm-up takes too long and the OCXO does not become active within a period of eight minutes from the

power-on. The ambient temperature can also be too low or it

changes too fast.

INSTRUCTIONS: Replace the alarming System Module.

FAULT NAME : PLL status not locked

FAULT ID : 4010: EFaultId_PLLStatusNotLockedAl

MEANING : BTS monitors the FSP/FBIA/WSPF/WSMF PLL (Phase-Locked Loop)

lock status and PLL locking fails.


1. Block/unblock the FSM/FBIA.

2. If that does not help, replace the FSM/FBIA.

UltraSite/EUBB:

1. Block/unblock the WSMF.


3. Block/unblock the WSPF.

4. If that does not help, replace the WSPF.

FAULT NAME : POST test failed

7/25/2019 Alarm_3G_RU_30


DN99580892 63



Id:0900d80580938c2b

Confidential

FAULT ID : 69: EFaultId_Post_test_failedAl

MEANING : A failure in the unit/module has been detected during the

BTS power-on self test (POST).




FAULT NAME : Parallel Interference Cancellation stream failure detected

FAULT ID : 2310: EFaultId_PicStreamFailure

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



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.



FAULT NAME : Power unit output voltage fault

FAULT ID : 1301: EFaultId_WpsPwrOutVoltage

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

3. Check the backplane connectors and cables.

4. Replace the alarming WPS unit.

FAULT NAME : R-bus errorFAULT ID : 425: EFaultId_RbusError

7/25/2019 Alarm_3G_RU_30


64 DN99580892


Id:0900d80580938c2b

Confidential


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


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 error

FAULT ID : 2052: EFaultId_OicRp1FcbAl

MEANING : 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


2. If that does not clear the fault situation, replace the

alarming Extension System Module.


replacing the Extension System Module does not clear the

fault situation, replace the alarming System Module.

FAULT NAME : SFN Signal error

FAULT ID : 2036: EFaultId_Transu_SfnSignalAlMEANING : A system frame number reception fault, an illegal SFN value

7/25/2019 Alarm_3G_RU_30


DN99580892 65



Id:0900d80580938c2b

Confidential

in uplink.


is faulty.




Module).

FAULT NAME : SFN synchronization failure

FAULT ID : 41: EFaultId_WSPC_PPC_SFN_PollingSynchAl

MEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The WSP is not synchronized with the WAM.

FlexiBTS: The FSP/FBIA is not synchronized with the FCM.

UltraSite/EUBB: The WSPF is not synchronized with WSMF.




UltraSite/EUBB:



FlexiBTS:



FAULT NAME : SRIO chain configuration was rejected

FAULT ID : 4015: EFaultId_Srio_ConfFailedAl

MEANING : The platform SW rejected the baseband bus related SRIO

configuration for Faraday core.

INSTRUCTIONS: Replace the alarming unit/module.

FAULT NAME : SRIO multicast configuration failed

7/25/2019 Alarm_3G_RU_30


66 DN99580892


Id:0900d80580938c2b

Confidential


FAULT ID : 4066: EFaultId_SrioMulticastConfFailedAl

MEANING : Response is not received or response is received with

unsuccessful status for SRIO multicast configuration

related messages.


fault disappears.



FAULT NAME : SW fallback

FAULT ID : 4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl

4083:

EFaultId_FallbackDueToConfigurationDataMigrationFailureAl

4085: EfaultId_FallbackDueToTransportRequestAlMEANING : 4082:

Source unit has reached the maximum number of reset

retries, i.e. source unit cannot successfully finish

start-up after the SW update.

4083:

Source unit requests SW fallback due to critical problem

that occurred in start-up after the SW update, i.e.

configuration data migration failure.

4085: Transport SW on source unit indicates a need for software

fallback.

INSTRUCTIONS: In case BTS is not automatically updated by NetAct and SW

versions are inconsistent: Update SW to the BTS with SW

version running on BTS before SW update causing SW

fallback.

FAULT NAME : Starting temperature below minimum

FAULT ID : 1827: EFaultId_StartTempBelowMinAl

MEANING : 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 service release from reset failed

FAULT ID : 1891: EFaultId_MuksuReleaseFromResetFailedAlMEANING : Summing service release from reset failed.

7/25/2019 Alarm_3G_RU_30


DN99580892 67



Id:0900d80580938c2b

Confidential

INSTRUCTIONS: 1. Reset the System Module.

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

the System Module.

FAULT NAME : Synchronization failure

FAULT ID : 2030: EFaultId_Transu_CompDevBbRfAl

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


is faulty.




Module).

FAULT NAME : Synchronization failure in Optical Interface <opt link/RP3

link>FAULT ID : 2005: EFaultId_OIC_SyncChAl

MEANING : 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 failure

FAULT ID : 3000: EFaultId_SystemModuleFailure

MEANING : The FlexiBTS has detected an abnormal operation or a

failure in the internal functionality of the System Module.


fault disappears.



FAULT NAME : TRANSU synchronization error

7/25/2019 Alarm_3G_RU_30


68 DN99580892


Id:0900d80580938c2b

Confidential


FAULT ID : 2045: EFaultId_TransuSyncAl

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


is faulty.




Module).

FAULT NAME : Tbus receiver parity fault

FAULT ID : 2027: EFaultId_Transu_TbusParityAl

MEANING : Data or synchronization failure in the System Module, two

antenna carriers are affected.


is faulty.




Module).

FAULT NAME : Telecom configuration failure

FAULT ID : 109: EFaultId_TcomSlaveRegAl

110: EFaultId_UnitRnwConfigAl

111: EFaultId_TcomSlaveConfigAl

119: EFaultId_WspAllocationAl

MEANING : 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

7/25/2019 Alarm_3G_RU_30


DN99580892 69



Id:0900d80580938c2b

Confidential

UltraSite, MetroSite, MetroSite 50, Triple-mode: WSP unit

to WAM allocation failure.

UltraSite/EUBB: Faraday unit to WSPF allocation failure.


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: In case 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


FlexiBTS Rel2: In case alarming unit is FSPC, block/unblock


FAULT NAME : Temperature alarmFAULT ID : 3040: EFaultId_TemperatureAlarm

MEANING : The internal temperature of the RF Module or System Module

exceeds the threshold value, or the ambient temperature of

the module(s) is outside the specified limits.



1. Check the other BTS faults and act accordingly.

2. Check the ambient temperature of the BTS modules. If the

ambient temperature is too high, make sure the airflow to

the BTS modules is unobstructed, that is, the BTS modules

are not covered with anything. If the ambient temperature

is too low, it takes a while for the BTS modules to heat

themselves to the threshold value.

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

it.


FAULT NAME : Ten consecutive Nacks received from a DSP at DCH setup

7/25/2019 Alarm_3G_RU_30


70 DN99580892


Id:0900d80580938c2b

Confidential


FAULT ID : 149: EFaultId_DspNacksReceivedAl

MEANING : One particular DSP Nacks DCH setup 10 times with cause

"NotEnoughResources=10" or "AlreadyActivated_Allocated=22"

within 20 minutes period.

INSTRUCTIONS: If the faulty FSP is in the extension module, block/unblock

the extension module, otherwise block/unblock the BTS.

FAULT NAME : Unit SW download failed

FAULT ID : 1828: EFaultId_FpgaSwDownloadAl

MEANING : The software update to the unit or subunit has failed.

INSTRUCTIONS: 1. Download the BTS SW again.

2. FCM: Reset the BTS.

3. If Step 2 does not help, replace the alarming module.


FAULT ID : 6: EFaultId_SwDownloadAl

MEANING : 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 then block/unblock the WSP.

3. If the alarming unit is WAM or WPA then reset the BTS.

4. If does not help, replace the alarming unit.

FlexiBTS:




FAULT NAME : Unit initialization failure

FAULT ID : 12: EFaultId_TcomConfigAl

13: EFaultId_AtmConfigAl

15: EFaultId_InitializationAl

4040: EFaultId_InitFaultManAl

MEANING : A unit/module or an IP address initialization has failed.


UltraSite/EUBB:

7/25/2019 Alarm_3G_RU_30


DN99580892 71



Id:0900d80580938c2b

Confidential


2. Check if the non-commissioned WAM is the Master WAM. If

so, this causes the fault. Check the fault history to know

why the WAM switchover 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 is the fault source, check the RNC IP address




FAULT NAME : Unit not supported by current BTS SW version

FAULT ID : 95: EFaultId_NotSupportedUnitMEANING : An unsupported unit was found in the BTS. Typically this

happens when a new unit version is installed and there is

an older BTS SW in use that does not support the new unit

version.

INSTRUCTIONS: Replace the unit or upgrade the BTS SW.

FAULT NAME : Unit synchronization failed

FAULT ID : 16: EFaultId_SynchronizationAl


The WAM/WSPC synchronization has failed.

FlexiBTS:

FCM/FSP synchronization has failed.



FAULT NAME : Unknown HW resource

FAULT ID : 94: EFaultId_UnknownUnitTypeMEANING : A unit cannot be identified by its product code or by its

7/25/2019 Alarm_3G_RU_30


72 DN99580892


Id:0900d80580938c2b

Confidential


physical device address (object ID).


FAULT NAME : Unknown product code

FAULT ID : 93: EFaultId_UnknownProductCode

MEANING : A module cannot be identified by its product code but is

known by its physical device address (object_ID).


FAULT NAME : Uplink data buffer synchronization failure

FAULT ID : 2033: EFaultId_Transu_UlDbSyncChAl

MEANING : The uplink data buffer loses synchronization.INSTRUCTIONS: 1. If only one FSP in the BTS generates this alarm, the FSP

is faulty.




Module).

FAULT NAME : WAM internal error

FAULT ID : 300: EFaultId_AtmRmCommAl

MEANING : The Telecom SW does not communicate with the ATM SW because

of a fault.

INSTRUCTIONS: Replace the faulty unit

FAULT NAME : WCI baseband reference clock failure

FAULT ID : 1001: EFaultId_RedundantClkMss

1002: EFaultId_MasterClkMss

MEANING : 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 fault

7/25/2019 Alarm_3G_RU_30


DN99580892 73



Id:0900d80580938c2b

Confidential

FAULT ID : 1309: EFaultId_AcLineBreakAl

MEANING : There is a mains break. The BTS power supply is cut off.

INSTRUCTIONS: Check the power supply to the BTS.

FAULT NAME : WSM failure

FAULT ID : 3001: EFaultId_EubbWsmAl


the internal functionality of the WSMF unit.


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.


FAULT NAME : WSMF WAM Interconnection Failure

FAULT ID : 4049: EFaultId_WsmfWamInterconnectionFailureAl

MEANING : Connection failure between WAMA and WSMFINSTRUCTIONS: Check that cables are connected between WAMA-WSMF and

WSMF-AXCF.

FAULT NAME : WSP PCI-bus failure

FAULT ID : 225: EFaultId_PCIInvalidDeviceAl

226: EFaultId_PCITargetNotFoundAl

227: EFaultId_PCITargetDSPAmountAl

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


Cancelling



7/25/2019 Alarm_3G_RU_30


74 DN99580892


Id:0900d80580938c2b

Confidential


29 7651 BASE STATION OPERATION

DEGRADED

Meaning

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

Check the reason for the fault from the supplementary text field

of the alarm.






2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number

7 feature code


Instructions






should be reset to recover from any temporary faults which

might have caused the malfunctioning of the unit/module.






Below is the list of BTS fault(s) which might have causedthis alarm in BTS WN7.0.2.0 release. In case of earlier SW

7/25/2019 Alarm_3G_RU_30


DN99580892 75



Id:0900d80580938c2b

Confidential






FAULT NAME : 10b8b coding error in Optical Interface device <opt

link/RP3>

FAULT ID : 2004: EFaultId_OIC_LVDSRecAl

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


RF Module causing the alarm.

3. If the System Module is the only source causing the

alarm, or if replacing the RF Module does not clear the

fault situation, replace the System Module causing the

alarm.

FAULT NAME : 2M external reference missing

FAULT ID : 1899: EFaultId_2MExtRefMissAl

MEANING : The reference clock monitoring has detected a loss of

2.048MHz signal received from an external reference source,

connected to Sync In interface of the System Module.


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.048MHz signal is available.


FAULT NAME : ATM faulty

FAULT ID : 45: EFaultId_ATM_SFN_PollingTimeoutAl

MEANING : 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

7/25/2019 Alarm_3G_RU_30


76 DN99580892


Id:0900d80580938c2b

Confidential


is also restarted automatically.



alarming WAM unit.

FAULT NAME : ATM processor faulty

FAULT ID : 590: EFaultId_AtmMcuBrokenAl

594: EFaultId_SfnIrqFailureAl


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 a fault in the FSM such that the SFN is not being

updated in the FSP MCU.


1. If ping to the BTS is working, restart the BTS remotely.


is working, restart the AXC remotely so that the BTS is

also automatically restarted.



alarming WAM unit.

FlexiBTS:

1. Reset the BTS.

2. If the BTS reset does not help, change the alarming

module.

FAULT NAME : ATM traffic overload

FAULT ID : 304: EFaultId_TrafficCausedBufferOverflowAl

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

7/25/2019 Alarm_3G_RU_30


DN99580892 77



Id:0900d80580938c2b

Confidential

2. Check the data integrity from the incoming Iub (see


3. Check the other transmission elements' active faults

(see the faults for AXC document).

FAULT NAME : Active clock tuning fault

FAULT ID : 1831: EFaultId_ActiveClkTuningAl

MEANING : The phase measurement cannot be performed in the active WSC

or WMC.

INSTRUCTIONS: 1. Run fast tuning with BTS Site Manager.



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 : Address mismatch in summing

FAULT ID : 2019: EFaultId_Muksu_SsubMmAl

MEANING : 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 acknowledgement 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 down

FAULT ID : 476: EFaultId_Rp3BusError

MEANING : Antenna (RP3) link is down: transmitter or receiver drops

from synchronization.



7/25/2019 Alarm_3G_RU_30


78 DN99580892


Id:0900d80580938c2b

Confidential


(FSM2), restart it. If the alarming module is the System

Module (FSM1), restart BTS.

2. If that does not help, replace the alarming FSM.

UltraSite/EUBB:

1. If the alarming unit is WSPF, restart the BTS. If all

WSPFs generate this alarm, restart the BTS.


FAULT NAME : BB bus reception error

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


is faulty.




Module).


FAULT ID : 2016: EFaultId_Muksu_SMTimeOffAl

MEANING : The master frame in the received baseband bus frame is not




place.






UltraSite/EUBB:


7/25/2019 Alarm_3G_RU_30


DN99580892 79



Id:0900d80580938c2b

Confidential

FAULT NAME : BB bus transmission error

FAULT ID : 2017: EFaultId_Muksu_SRx10b8bAl

MEANING : A decoding error has been detected in the baseband internal

link. The data packet is lost or the content is corrupted.

This situation is also triggered when the links do not

synchronize with each other.




2. Replace the alarming unit (System Module).

UltraSite/EUBB:

1. Replace the alarming unit (WSMF).

FAULT NAME : BOFU Post failed

FAULT ID : 4021: EFaultId_BOFU_Post_failedAl

MEANING : The unit or module has been tested during BTS power-on self

test (POST)

and a failure has been detected.




FAULT NAME : BTS Master Clock tuning failure

FAULT ID : 1818: EFaultId_Ov_OscAl

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.


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.

7/25/2019 Alarm_3G_RU_30


80 DN99580892


Id:0900d80580938c2b

Confidential


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.

FAULT NAME : BTS RNC/I-HSPA interface signalling link failure

FAULT ID : 19: EFaultId_Aal2LinkAl

MEANING : An AAL2 signaling link failure. It can be caused by a broken WAM. The most common reason for this alarm is a

frequent transmission breaking .

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.


FAULT ID : 17: EFaultId_CnbapLinkAl

MEANING : A common NBAP link failure. It can be caused by a

transmission network problem. The most common reason for

this alarm is a frequently breaking transmission.


UltraSite/EUBB:

1. Check the other transmission elements' active alarms



3. Reset the AXC.



FlexiBTS:

7/25/2019 Alarm_3G_RU_30


DN99580892 81



Id:0900d80580938c2b

Confidential

1. Reset the BTS.

2. Check the transmission links to the RNC/I-HSPA adapter.

3. Check the BTS and RNC/I-HSPA adapter transmission

settings.



FAULT ID : 18: EFaultId_DnbapLinkAl

MEANING : 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:




3. Reset the AXC.



FlexiBTS:

1. Reset the BTS.

2. Check the transmission links to the RNC.



FAULT NAME : BTS SW download or activation failed

FAULT ID : 29: EFaultId_FileCorruptionAl

30: EFaultId_SwUpdateAl

MEANING : 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: 1. Retry the SW update.

7/25/2019 Alarm_3G_RU_30


82 DN99580892


Id:0900d80580938c2b

Confidential


2. If other flash memory-related alarms are active for the

alarming unit at the same time, replace the alarming unit.

FAULT NAME : BTS configuration not supported

FAULT ID : 4097: EFaultId_BtsConfNotSupportedAl

MEANING : FSP does not support requested BTS configuration.


fault disappears.

1. Change BTS configuration.

2. Reset BTS.

FAULT NAME : BTS file errorFAULT ID : 1802: EFaultId_FileRequestFlashAl






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.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode,

UltraSite/EUBB:





alarming unit.

FlexiBTS:





FAULT NAME : BTS file errorFAULT ID : 136: EFaultId_TcomConfFileAl

7/25/2019 Alarm_3G_RU_30


DN99580892 83



Id:0900d80580938c2b

Confidential

MEANING : Telecom configuration file(s) are invalid, missing, or not

accessible.


UltraSite/EUBB:





alarming unit.

FlexiBTS:

1. Download two different SW packages so that the faulty file is removed from the BTS.


3. Replace the System Module or FBIA.

FAULT NAME : BTS internal SW management problem

FAULT ID : 3090: EFaultId_BtsInternalSwManagementProblem

MEANING : A software update to a unit/module or subassembly has failed, or a corrupted SW file has been detected in the

FLASH.



FlexiBTS:











UltraSite/EUBB:

7/25/2019 Alarm_3G_RU_30


84 DN99580892


Id:0900d80580938c2b

Confidential








FAULT NAME : BTS reference clock missing

FAULT ID : 3080: EFaultId_BtsReferenceClockMissing

MEANING : This BTS fault indication is generated if the reference clock monitoring function of the BTS does not receive the

highest configured synchronization reference signal or if

all the synchronization reference signals are missing. The

BTS fault is not generated if the highest configured

synchronization source is present, no matter what the lower

level source statuses are.

Background information:

There is a fixed synchronization priority list in the FlexiBTS:

-Priority 1: PPS (Pulse Per Second) signal connected to the

Synchronization Input interface (Sync In) of the System

Module. Normally the PPS signal is generated by the GPS

receiver.

-Priority 2: external 2.048MHz signal connected to the Sync

In interface.

-Priority 3: the reference signal coming from the

integrated 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

7/25/2019 Alarm_3G_RU_30


DN99580892 85



Id:0900d80580938c2b

Confidential

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 because the device type is not known,

detailed instructions cannot be given - refer to the

appropriate user manual of the device for further actions.


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

7/25/2019 Alarm_3G_RU_30


86 DN99580892


Id:0900d80580938c2b

Confidential


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.


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 instability of

the transmission network, not to a failure in the unit.

If the previous steps do not help, there might be an equipment failure in the System Module. Check the operation

and if performing a BTS site reset does not help, replace

the System Module.








alarm disappears.

FlexiBTS:




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

7/25/2019 Alarm_3G_RU_30


DN99580892 87



Id:0900d80580938c2b

Confidential







the RF Module/Extension System Module does not clear the

fault situation, replace the alarming master System Module.

UltraSite/EUBB:








by the HW, SW, DSP, or LTX.INSTRUCTIONS: Replace the alarming module.

FAULT NAME : Baseband loop test failure

FAULT ID : 4016: EFaultId_Srio_TestFailedWithinBoardAl

MEANING : The test message sent to the baseband link (SRIO) did not

return within the required time.


1. Reset the BTS.

2. Replace the faulty module.

UltraSite/EUBB:

1. If the alarming module is WSPF, restart it by

blocking/unblocking.

2. If that does not help, replace the alarming WSPF.

FAULT NAME : Baseband reset needed

FAULT ID : 4109: EfaultId_BasabandResetNeeded

MEANING : Unit containing common channel devices is being blocked.

Baseband reset is needed to proceed with blocking.INSTRUCTIONS: None

7/25/2019 Alarm_3G_RU_30


88 DN99580892


Id:0900d80580938c2b

Confidential


FAULT NAME : Cabinet door open

FAULT ID : 1300: EFaultId_DoorAl0

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






alarm disappears.













FAULT ID : 458: EFaultId_VcpError

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

7/25/2019 Alarm_3G_RU_30


DN99580892 89



Id:0900d80580938c2b

Confidential


FAULT NAME : Communication failure inside WSP

FAULT ID : 414: EFaultId_McbspMessagePoolExhausted

446: EFaultId_McbspSwsError

MEANING : An internal communication failure between the DSP

processors.


1. Block the alarming WSP.

2. The fault might be in the WTR or WPA (see



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.




Module).

UltraSite/EUBB:


WSPF is faulty.








there is a mismatch between the BTS configuration and the RNC/I-HSPA adapter parameters.

7/25/2019 Alarm_3G_RU_30


90 DN99580892


Id:0900d80580938c2b

Confidential








frequency, power).


local cell (LCR).



FAULT NAME : Connection to ToP master missing

FAULT ID : 4058: EFaultId_TopRefClkMissingAl

MEANING : The reference clock monitoring has detected a loss of ToP

reference clock signal received from the master clock.


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.

FAULT NAME : Connection to transmission broken

FAULT ID : 1829: EFaultId_ConnToTransBrokenAl


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.


7/25/2019 Alarm_3G_RU_30


DN99580892 91



Id:0900d80580938c2b

Confidential


2. If the transmission type is the AXC, reset the WAM.


FlexiBTS:


2. Reset the site.

3. If that does not help, replace the alarming System

Module.


FAULT ID : 208: EFaultId_DscNodeBlockedAl

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




FAULT ID : 597: EFaultId_DscFaultAl

MEANING : 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 failure

FAULT ID : 2302: EFaultId_RsaInitializationError

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



(FSM2), restart

it. If the alarming module is the System Module (FSM1),

restart the BTS.

2.

7/25/2019 Alarm_3G_RU_30


92 DN99580892


Id:0900d80580938c2b

Confidential


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.


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_DspHoldAl

MEANING : Radio link creation has failed repeatedly because of DSP

rejection.




UltraSite/EUBB:



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 failed

FAULT ID : 139: EFaultId_DspModeChangeFailAl

MEANING : DSP configuration to correct mode was not successful.

INSTRUCTIONS: Replace the alarming module/unit.

FAULT NAME : DSP overheated

FAULT ID : 4101: EFaultId_DspOverheatingAl

MEANING : DSP overheating was detected during DSP initialization.

INSTRUCTIONS: 1. Check the fans and ensure that the ambient temperature on the site is acceptable.

7/25/2019 Alarm_3G_RU_30


DN99580892 93



Id:0900d80580938c2b

Confidential

2. If that does not help, replace the alarming FSP module.

FAULT NAME : Downlink data buffer synchronization failure

FAULT ID : 2031: EFaultId_Transu_DlDbSynchChAl

MEANING : The downlink data buffer has lost synchronization.


is faulty.




Module).

FAULT NAME : Error in commissioning data

FAULT ID : 31: EFaultId_CommDataAl

MEANING : 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 state

FAULT ID : 4068: EFaultId_FspResetAl

MEANING : FSP is undergoing a cold reset.


fault disappears:

1. Reset the BTS.

2. Replace the faulty module/unit.

FAULT NAME : FSP reset failure

FAULT ID : 4100: EFaultId_FspResetFailureAl

MEANING : FSP reset during BB reset recovery did not succeed.

INSTRUCTIONS: Check the faulty FSP.

7/25/2019 Alarm_3G_RU_30


94 DN99580892


Id:0900d80580938c2b

Confidential


FAULT NAME : Failure in AXU initialization

FAULT ID : 14: EFaultId_AxuConfigAl

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



MEANING : The BTS has detected an abnormal operation or a failure in an optical RP3 interface between two modules. The failure




alarm disappears.















Module.

FAULT NAME : Failure in replaceable baseband unit

FAULT ID : 3003: EFaultId_FbiaFailureAl


the BTS replaceable

baseband unit.INSTRUCTIONS: Note: Perform the steps below in the listed order until the

7/25/2019 Alarm_3G_RU_30


DN99580892 95



Id:0900d80580938c2b

Confidential


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 : Fan failure

FAULT ID : 3050: EFaultId_FanFailure

MEANING : All the fans or more than one fan in the same fan group are rotating slower than requested, are not rotating at all, or

the RPM information is not available for the fans. The

reason for this fault can be too low supply voltage or a

broken fan.


alarm disappears.

1. Check the fan and cabling.

2. Replace the faulty fan module.

FAULT NAME : Fatal OSE Error

FAULT ID : 418: EFaultId_OseFatalErr

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


Note! Perform the steps below in the listed order until the

fault disappears.



UltraSite/EUBB:

1. If only one WSPF in BTS generates this fault, the WSPF is faulty.

7/25/2019 Alarm_3G_RU_30


96 DN99580892


Id:0900d80580938c2b

Confidential


2. If all WSPFs generate this fault, BTS is faulty.

3. Block/unblock BTS.


FAULT NAME : Fault between WAM and WSP SFN (WSP)

FAULT ID : 412: EFaultId_LostFrameSync

428: EFaultId_SystemFrameNumberParity


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.


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.


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.




Module) or faulty FBIA.

UltraSite/EUBB:


WSPF is faulty.


7/25/2019 Alarm_3G_RU_30


DN99580892 97



Id:0900d80580938c2b

Confidential




FAULT ID : 309: EFaultId_AtMuxAl

MEANING : The WAM ATM interface is not responding correctly.

INSTRUCTIONS: 1. Block/unblock the alarming unit. This resets the BTS.



FAULT ID : 591: EFaultId_SarChipBrokenAl

592: EFaultId_UxAsicAl

593: EFaultId_AtmHostBrokenAl

MEANING : 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 interface

FAULT ID : 42: EFaultId_ WSPC_PPC_SFN_PollingTimeoutAl

43: EFaultId_DSP_PollingTimeoutAl


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.



7/25/2019 Alarm_3G_RU_30


98 DN99580892


Id:0900d80580938c2b

Confidential



UltraSite/EUBB:



FlexiBTS:



FAULT NAME : Faulty configuration of system modules

FAULT ID : 1858: EFaultId_FaultyFcmConfigurationAl

MEANING : There is possibly a faulty configuration with the Radio

Modules connected to both the master system module and

intented extension system module.

INSTRUCTIONS: Remove Radio Modules from the intended extension system

module and hot insert them to the intended master system

module.

FAULT NAME : Flash operation failure

FAULT ID : 214: EFaultId_FlashWrAl

215: EFaultId_FlashRdAl

216: EFaultId_FlashEraseAl

217: EFaultId_FlashDrvAl

218: EFaultId_FlashDbChksumAl

MEANING : A flash memory operation failure. If this fault

continuously appears, the flash chip may be broken.


UltraSite/EUBB:

1. Check the other active faults. If the /rom-disk is


2. Block/unblock the alarming unit. There are no recovery

actions and because of that the block/unblock can be

attempteded once. If that does not help, replace the

alarming unit.

FlexiBTS:


corrupted, change the alarming unit/module.

7/25/2019 Alarm_3G_RU_30


DN99580892 99



Id:0900d80580938c2b

Confidential

2. Block/unblock the alarming unit/module. There are no

recovery actions and blocking/unblocking can be attempteded

once. If that does not help, replace the alarming

unit/module.

FAULT NAME : Frame burst receiving fault

FAULT ID : 2013: EFaultId_OIC_Rp1CrcAl

MEANING : 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


clear the fault situation, replace the System Module that

causes the alarm.

FAULT NAME : Frame clock deviation fault

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




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 ID : 2047: EFaultId_OIC_FrSyncLostAlMEANING : The timing of the new RP1 synchronization burst deviates

7/25/2019 Alarm_3G_RU_30


100 DN99580892


Id:0900d80580938c2b

Confidential










in the BTS.


see the active SW version, and update the active SW version), unless it is automatically updated by NetAct.






MEANING : 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 : Incomplete network parameters received from AXU

FAULT ID : 1851: EFaultId_CommDataNetworkParamAl

MEANING : 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 failure

FAULT ID : 4025: EFaultId_MtuConfigurationFailureAl

MEANING : 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

7/25/2019 Alarm_3G_RU_30


DN99580892 101



Id:0900d80580938c2b

Confidential

FAULT NAME : Internal communication error

FAULT ID : 4087: EFaultId_InternalCommunicationErrorAl

MEANING : 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. Check that the unit/module is properly connected.



FAULT NAME : Licence missing <licenceCode>, <licenceName>FAULT ID : 1885: EFaultId_MissingLicense Al

MEANING : The BTS detected a resource requiring a license but no

license exists nor is available.

INSTRUCTIONS: Activate the appropriate license or increase the license

amount.

FAULT NAME : License missing <licenseCode>, <licenseName>

FAULT ID : 1833: EFaultId_LicenceMissingAl

MEANING : The BTS detected a resource needing a license but no license exists or is free.

INSTRUCTIONS: An appropriate license should be activated or the license

amount should be increased.

FAULT NAME : Mains power break, running Battery Backup

FAULT ID : 37: EFaultId_MainsBreakAl

MEANING : 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 unit

FAULT ID : 4019: EFaultId_KeepAliveStatusErrorAl

MEANING : Connection to the DSP submodule has been lost or the

submodule reports an error situation.


fault disappears:

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

7/25/2019 Alarm_3G_RU_30


102 DN99580892


Id:0900d80580938c2b

Confidential


FAULT NAME : Missing NBAP Cell parameters, defaults are used

FAULT ID : 88: EFaultId_CommDataCellParam

MEANING : One or more cell parameters are missing from the RNC/I-HSPA

adapter configuration data and the BTS commissioning file.

INSTRUCTIONS: 1. Check the cell parameters in RNC/I-HSPA adapter and BTS.

2. If the parameters configured to the RNC/I-HSPA adapter

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/I-HSPA adapter

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 overheating

FAULT ID : 4071: EFaultId_SysDangerouslyOverheatAl

MEANING : Highest validated temperature value on FSP board exceeds the threshold value.


1. Check the fans and ensure that the ambient temperature


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







UltraSite/EUBB:




site.


LED does not light up, the unit is faulty. The fault might also be in the WPS unit or backplane.

7/25/2019 Alarm_3G_RU_30


DN99580892 103



Id:0900d80580938c2b

Confidential


bus cables.












FlexiBTS:





FAULT NAME : No connection to unitFAULT ID : 75: EFaultId_WSP_memory_concistency_err1

76: EFaultId_WSP_memory_concistency_err2






MEANING : The connection to a unit belonging to the BTS configuration

has been lost.

INSTRUCTIONS: 1. Check the alarm history, alarming unit and subrack.



site.


led does not light up, the unit is faulty. The fault may



bus cables.

Cancel alarms: Removing and inserting the WIC, WSM or

7/25/2019 Alarm_3G_RU_30


104 DN99580892


Id:0900d80580938c2b

Confidential






site. First try to reset the site by the software. If



FAULT ID : 1815: EFaultId_BbBus_SyncFailedAl

MEANING : The baseband bus synchronization towards <x> failed.


FAULT NAME : Not enough DSP resources per cell

FAULT ID : 1861: EFaultId_NotEnoughFspResourcesPerCellAl

MEANING : 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 cell

FAULT 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 Data/Control/Ethernet Buffer Full

FAULT ID : 2006: EFaultId_OIC_DBRxFullAl

2007: EFaultId_OIC_DBTxFullAl

2008: EFaultId_OIC_CBRxFullAl

2009: EFaultId_OIC_CBTxFullAl

2010: EFaultId_OIC_EBFullAl

MEANING : The RP3 or Ethernet buffering is not working and the buffer

becomes full. The optical device is malfunctioning. The

fault might be generated because of synchronization

problems or incorrect initialization.

INSTRUCTIONS: Swap the alarming and working links. Then check where the

alarm is now reported. If the alarming link remains the same, replace the System Module. If the alarming link

7/25/2019 Alarm_3G_RU_30


DN99580892 105



Id:0900d80580938c2b

Confidential


FAULT NAME : Optical Interface Frame clock faulty

FAULT ID : 2003: EFaultId_OIC_CleanerLockAl

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


2. Replace the FSM.

FAULT NAME : Optical Interface faulty

FAULT ID : 2000: EFaultId_OIC_TxAl

2001: EFaultId_OIC_PresAl

MEANING : 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 : Optical interface FPGA sw crc check failed

FAULT ID : 1830: EFaultId_FpgaCrcCheckFailAl

MEANING : The CRC check has failed in three consecutive optical

interface FPGA SW downloading attempts.


FAULT NAME : Optical interface buffer alarm

FAULT ID : 2051: EFaultId_Muksu_BufferAl

MEANING : 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



connected module/unit behind the interface that causes the alarm.

7/25/2019 Alarm_3G_RU_30


106 DN99580892


Id:0900d80580938c2b

Confidential


FlexiBTS:

3. If the System Module is the only alarm source, or



causes 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 : Out Of Frame Data Error

FAULT ID : 420: EFaultId_OutOfDataMEANING : An out of frame data error interrupt received from the SWS

ASIC.


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.


Module).

FAULT NAME : Oven oscillator Missing Pulse

FAULT ID : 1820: EFaultId_OcxoPulseMissingAl

MEANING : The output signal of the OXCO has some problems and one or

more clock pulses are missed.


2. Replace the FSM.


FAULT ID : 901: EFaultId_OcxoHeatingAl

912: EFaultId_DualWscOvAMss

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

7/25/2019 Alarm_3G_RU_30


DN99580892 107



Id:0900d80580938c2b

Confidential

2. Replace the clock unit.

FAULT NAME : PLL status not locked

FAULT ID : 4010: EFaultId_PLLStatusNotLockedAl

MEANING : BTS monitors the FSP/FBIA/WSPF/WSMF PLL (Phase-Locked Loop)

lock status and PLL locking fails.


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 failed

FAULT ID : 69: EFaultId_Post_test_failedAl

MEANING : A failure in the unit/module has been detected during the

BTS power-on self test (POST).




FAULT NAME : PPS reference missing

FAULT ID : 1898: EFaultId_PpsRefMissAl

MEANING : The reference clock monitoring has detected a loss of PPS

signal in the reference received from the GPS receiver.

INSTRUCTIONS: 1. Check the GPS receiver installation.

2. Check the GPS receiver status.

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

FAULT NAME : Parallel Interference Cancellation stream failure detected

FAULT ID : 2310: EFaultId_PicStreamFailure

MEANING : 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

7/25/2019 Alarm_3G_RU_30


108 DN99580892


Id:0900d80580938c2b

Confidential


fault disappears.



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.



FAULT NAME : Parallel RP3-01 link length mismatch

FAULT ID : 4072: EFaultId_ParallelLinkDifferenceTooLargeAl

MEANING : 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

utilized

FAULT 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 only in FSMr2+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 : Performance not optimal due to Rel2 System Module not fully

utilized

FAULT ID : 4112: EFaultId_PerformanceNotOptimalRel2NotFullyUtilizedAl

MEANING : The performance of the BTS is not optimal, because crucial

SW components are located in Rel1 MSM (instead of Rel2 ESM)

and connection to Rel2 ESM is restored. In result,

signaling performance is the same as with pure Rel1 MSM.

INSTRUCTIONS: In order to restore full performance reset BTS manually.

7/25/2019 Alarm_3G_RU_30


DN99580892 109



Id:0900d80580938c2b

Confidential

FAULT NAME : Power unit input voltage fault

FAULT ID : 1302: EfaultId_WpsPwrInVoltage

MEANING : 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 fault

FAULT ID : 1301: EFaultId_WpsPwrOutVoltage

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


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 error

FAULT ID : 425: EFaultId_RbusError





FSP and FCM.








7/25/2019 Alarm_3G_RU_30


110 DN99580892


Id:0900d80580938c2b

Confidential



FlexiBTS:


Module.



FAULT NAME : RP3-01 Link Conflict

FAULT 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 Conflict

FAULT ID : 4038: EFaultId_RadioMasterConflictAl

MEANING : 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 available

FAULT ID : 145: EFaultId_ResourceBlockNotAvailableAl

MEANING : 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 site manager.

2) If this is a repetitive problem, the FSP card has to be

removed and re-inserted.

FAULT NAME : Resource block occupied by high priority services

FAULT ID : 146: EFaultId_ResourceBlockOccupiedAl

MEANING : If the 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

7/25/2019 Alarm_3G_RU_30


DN99580892 111



Id:0900d80580938c2b

Confidential

and tries again to allocate the PIC configuration to the

DSP a number of times for three 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

Site Manager (BTSSM).

2) If this is a repetitive problem, the FSP card has to be

removed and

re-inserted.

FAULT NAME : SCF corrupted

FAULT ID : 4093: EFaultId_SiteConfigurationFileCorruptAl

MEANING : SCF file is not consistent. For example, SCF might get corrupted when opened for writing and uncontrolled BTS

restart might happen.

INSTRUCTIONS: Recommission the BTS.

FAULT NAME : SFN Signal error

FAULT ID : 2036: EFaultId_Transu_SfnSignalAl

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




Module).


FAULT ID : 41: EFaultId_WSPC_PPC_SFN_PollingSynchAl

MEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The WSP is

not synchronized with the WAM.

FlexiBTS: The FSP/FBIA is not synchronized with the FCM.

UltraSite/EUBB: The WSPF is not synchronized with WSMF.




7/25/2019 Alarm_3G_RU_30


112 DN99580892


Id:0900d80580938c2b

Confidential


UltraSite/EUBB:



FlexiBTS:



FAULT NAME : SFN synchronization failureFAULT ID : 44: EFaultId_ATM_SFN_PollingSynchAl

MEANING : There is a WAM internal synchronization failure.

INSTRUCTIONS: 1. Check and correct the ATM configuration.

2. Replace the WAM.


FAULT ID : 46: EFaultId_WAM_SFN_PollingSynchAl

MEANING : The slave WAM is not synchronised with the master WAM.INSTRUCTIONS: 1. Block/unblock the alarming unit.


FAULT NAME : SRAM operation failure

FAULT ID : 1875: EFaultId_SRAMRdAl

1876: EFaultId_SRAMWrAl

MEANING : The SRAM memory operation failure. If this alarm appears

continuously, the SRAM chip may be broken.



FAULT NAME : SRIO chain configuration was rejected

FAULT ID : 4015: EFaultId_Srio_ConfFailedAl

MEANING : The platform SW rejected the baseband bus related SRIO

configuration for Faraday core.


7/25/2019 Alarm_3G_RU_30


DN99580892 113



Id:0900d80580938c2b

Confidential

FAULT NAME : SW fallback

FAULT ID : 4082: EfaultId_FallbackDueToMaxResetLoopCounterValueAl

4083:

EFaultId_FallbackDueToConfigurationDataMigrationFailureAl

4085: EfaultId_FallbackDueToTransportRequestAl

MEANING : 4082:

Source unit has reached the maximum number of reset

retries, i.e. source unit cannot successfully finish

start-up after the SW update.

4083:

Source unit requests SW fallback due to critical problem

that occurred in start-up after the SW update, i.e.

configuration data migration failure.

4085:

Transport SW on source unit indicates a need for software

fallback.

INSTRUCTIONS: In case BTS is not automatically updated by NetAct and SW

versions are inconsistent: Update SW to the BTS with SW

version running on BTS before SW update causing SW

fallback.

FAULT NAME : Self test failed

FAULT ID : 1882: EFaultId_SelfTestFailedAl

MEANING : The self test of the unit/module has failed.


2. If that does not help, replace the alarming unit/module.

FAULT NAME : Summing service release from reset failed

FAULT ID : 1891: EFaultId_MuksuReleaseFromResetFailedAl

MEANING : 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 receiver

FAULT ID : 2048: EFaultId_Casa2Rp1CrcAl

2049: EFaultId_Casa2Rp1FramePhaseAl

MEANING : The frame alignment is lost or the frame burst has a CRC error when the System Module is working in extension mode.

7/25/2019 Alarm_3G_RU_30


114 DN99580892


Id:0900d80580938c2b

Confidential


INSTRUCTIONS: 1. Check the other active synchronization alarms and act

accordingly.

2. Reset the Extension System Module.

FAULT NAME : Synchronization failure

FAULT ID : 2030: EFaultId_Transu_CompDevBbRfAl

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


is faulty.




Module).


link>FAULT ID : 2005: EFaultId_OIC_SyncChAl

MEANING : The RP3 channel has lost the frame synchronization state






FAULT NAME : System Module failure

FAULT ID : 3000: EFaultId_SystemModuleFailure


failure in the internal functionality of the System Module.


fault disappears.



FAULT NAME : System clock for extension system module not available

7/25/2019 Alarm_3G_RU_30


DN99580892 115



Id:0900d80580938c2b

Confidential

FAULT ID : 1852: EFaultId_SystemClockExtensionNotAvailableAl

MEANING : 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

FAULT ID : 219: EFaultId_SfclkMssAl

MEANING : 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_TransuSyncAl

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


is faulty.




Module).

FAULT NAME : TargetId verification failure

FAULT ID : 4056: EFaultId_TargetIdVerificationFailureAl

MEANING : NetAct Licence Manager did not respond to the verification

request. TargetId verification was not possible.


fault disappears.

1. Reset the NetAct Licence Manager.

7/25/2019 Alarm_3G_RU_30


116 DN99580892


Id:0900d80580938c2b

Confidential


2. Reset the BTS.

3. Check the BTS license situation: the correct licenses

have been purchased

and installed.

FAULT NAME : Tbus receiver parity fault

FAULT ID : 2027: EFaultId_Transu_TbusParityAl

MEANING : Data or synchronization failure in the System Module, two

antenna carriers are affected.


is faulty.




Module).




111: EFaultId_TcomSlaveConfigAl 119: EFaultId_WspAllocationAl



failure.

FlexiBTS:







Or





UltraSite/EUBB:


7/25/2019 Alarm_3G_RU_30


DN99580892 117



Id:0900d80580938c2b

Confidential





FlexiBTS:






FAULT NAME : Ten consecutive Nacks received from a DSP at DCH setup

FAULT ID : 149: EFaultId_DspNacksReceivedAl

MEANING : One particular DSP Nacks DCH setup 10 times with cause

"NotEnoughResources=10" or "AlreadyActivated_Allocated=22"

within 20 minutes period.

INSTRUCTIONS: If the faulty FSP is in the extension module, block/unblock

the extension module, otherwise block/unblock the BTS.

FAULT NAME : Timeout, commissioned resource not ready

FAULT ID : 35: EFaultId_UnitIsNotInUse

MEANING : The faulty unit has not been configured or initialised.

INSTRUCTIONS: Recommission the site.

FAULT NAME : Transmission clock missing

FAULT ID : 1003: EFaultId_TransmissionClk0Mss

1004: EFaultId_TransmissionClk1Mss

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.


7/25/2019 Alarm_3G_RU_30


118 DN99580892


Id:0900d80580938c2b

Confidential


FAULT NAME : Transmission clock missing

FAULT ID : 1816: EFaultId_Trans_Clk_MsgAl

MEANING : 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 missing

FAULT ID : 1825: EFaultId_PublicIPmissingAl 1826: EFaultId_TrParamMissingAl

MEANING : A request to retrieve the public IP address information of

the FCM 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 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








UltraSite/EUBB:



3. If the alarming unit is WAM or WPA then reset the BTS. 4. If does not help, replace the alarming unit.

7/25/2019 Alarm_3G_RU_30


DN99580892 119



Id:0900d80580938c2b

Confidential

FlexiBTS:




FAULT NAME : Unit blocked

FAULT ID : 48: EFaultId_UnitBlockedAl

MEANING : A unit is blocked with BTS Site Manager.

The purpose of the fault is to avoid alarms that may be

raised during the unit maintenance task.

INSTRUCTIONS: To cancel the alarm, unblock the unit/module.








UltraSite/EUBB:









FlexiBTS:







7/25/2019 Alarm_3G_RU_30


120 DN99580892


Id:0900d80580938c2b

Confidential



FAULT ID : 85: EFaultId_WSP_no_resp_from_PPC

MEANING : The connection to the WSP fails due to a WSP internal

failure.




FAULT ID : 95: EFaultId_NotSupportedUnit

MEANING : An unsupported unit was found in the BTS. Typically this

happens when a new unit version is installed and there is an older BTS SW in use that does not support the new unit

version.


FAULT NAME : Unit synchronization failed

FAULT ID : 16: EFaultId_SynchronizationAl


The WAM/WSPC synchronization has failed.

FlexiBTS:

FCM/FSP synchronization has failed.



FAULT NAME : Unknown Cabinet Type

FAULT ID : 1804: EFaultId_UnknownCabinetTypeAl

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 ID : 94: EFaultId_UnknownUnitType

MEANING : A unit cannot be identified by its product code or by its



7/25/2019 Alarm_3G_RU_30


DN99580892 121



Id:0900d80580938c2b

Confidential






FAULT NAME : Uplink data buffer synchronization failure

FAULT ID : 2033: EFaultId_Transu_UlDbSyncChAl

MEANING : The uplink data buffer loses synchronization.


is faulty.




Module).

FAULT NAME : WAM SFN polling timeout

FAULT ID : 47: EFaultId_WAM_SFN_PollingTimeoutAl

MEANING : The slave WAM is not synchronised with the master WAM.


Note: After the WAM block/unblock, the BTS will be

restarted.


FAULT NAME : WAM internal error

FAULT ID : 300: EFaultId_AtmRmCommAl

MEANING : The Telecom SW does not communicate with the ATM SW because

of a fault.

INSTRUCTIONS: Replace the faulty unit

FAULT NAME : WMC oven oscillator fault

FAULT ID : 8: EFaultId_DacWordLimitAl

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

7/25/2019 Alarm_3G_RU_30


122 DN99580892


Id:0900d80580938c2b

Confidential


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.

7/25/2019 Alarm_3G_RU_30


DN99580892 123



Id:0900d80580938c2b

Confidential

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

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.


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 fault

FAULT ID : 907: EFaultId_DualWscDacWordAlarm


value. The alarm is activated if the WSC tunes the oven



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:


time (up to several days) due to a fault in the transmission network synchronization (which in turn is

7/25/2019 Alarm_3G_RU_30


124 DN99580892


Id:0900d80580938c2b

Confidential


caused by an equipment fault or a setting error). Before

activating this alarm, the alarm 7652 BASE STATION




synchronization information via the 2.048 MHz

synchronization input (external clock source), the alarm


case, the alarm behavior notifications listed with the Iub

signal (see above) are also valid in this case.




the fast tuning execution, it may result in adjusting the BTS master clock frequency far from the nominal value,








4095).


DEGRADED: 'WSC oven oscillator fault' becomes active, it




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


7/25/2019 Alarm_3G_RU_30


DN99580892 125



Id:0900d80580938c2b

Confidential

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.



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)



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


synchronization signal as a reference for the Air


3GPP.

FAULT NAME : WSC phase difference jammed to zero reading

FAULT ID : 22: EFaultId_WscPhaseDiffJammedAl

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

7/25/2019 Alarm_3G_RU_30


126 DN99580892


Id:0900d80580938c2b

Confidential


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







3GPP.

FAULT NAME : WSC/WMC transmission clock missing

FAULT ID : 900: EFaultId_TransmissionClkMss

909: EFaultId_DualWscTrclkMss

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.


FAULT NAME : WSM SR-Bus error

FAULT ID : 1205: EFaultId_Srl0_0ParityErr2 1207: EFaultId_Srl0_0SyncErr2

7/25/2019 Alarm_3G_RU_30


DN99580892 127



Id:0900d80580938c2b

Confidential

1209: EFaultId_Srl0_1ParityErr2

1211: EFaultId_Srl0_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_1SyncErr2

MEANING : 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 panel and the 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).

FAULT NAME : WSM ST-Bus error

FAULT 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

7/25/2019 Alarm_3G_RU_30


128 DN99580892


Id:0900d80580938c2b

Confidential


1185: EFaultId_St_r1ParityErr2

1187: EFaultId_St_r1SyncErr2

MEANING : The TX signal is transported from the WSP unit to all WTR


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.




check whether the problem is cleared (see Troubleshooting instructions).

FAULT NAME : WSM T-Bus error

FAULT ID : 1149: EFaultId_Wspc0ParityErr2

1151: EFaultId_Wspc0SyncErr2

1153: EFaultId_Wspc1ParityErr2



1159: EFaultId_Wspc2SyncErr2 1161: EFaultId_Wspc3ParityErr2






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

FAULT NAME : WSM does not receive frame clock

7/25/2019 Alarm_3G_RU_30


DN99580892 129



Id:0900d80580938c2b

Confidential

FAULT ID : 1253: EFaultId_Dsax_SfclkStatusNegErr

1254: EFaultId_Dsax_SfclkStatusPosErr

1256: EFaultId_Umax_SfclkStatusErr

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






alarm disappears.



LED does not light up, the unit is faulty.

3. Reset the BTS.


FAULT NAME : WSMF WAM Interconnection Failure

FAULT ID : 4049: EFaultId_WsmfWamInterconnectionFailureAl

MEANING : Connection failure between WAMA and WSMF

INSTRUCTIONS: Check that cables are connected between WAMA-WSMF and

WSMF-AXCF.

FAULT NAME : WSP PCI-bus failure

FAULT ID : 225: EFaultId_PCIInvalidDeviceAl

226: EFaultId_PCITargetNotFoundAl

227: EFaultId_PCITargetDSPAmountAl

MEANING : There is a fault in the internal WSP/FSP PCI bus target (DSP) connections. Some of the WSP/FSP DSP processors may

7/25/2019 Alarm_3G_RU_30


130 DN99580892


Id:0900d80580938c2b

Confidential


be broken and out of use.


FAULT NAME : WSP failure

FAULT ID : 3002: EFaultId_EubbWspAl

MEANING : BTS has detected an abnormal operation or a failure in the

internal functionality of the WSPF unit.


alarm disappears.



LED does not light up, it is faulty.



FAULT NAME : WSP unit internal failure

FAULT ID : 97: EFaultId_WamWspOutOfSyncAl

MEANING : The WAM and WSP are not synchronized.



Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 131



Id:0900d80580938c2b

Confidential

30 7652 BASE STATION NOTIFICATION

Meaning

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


of the alarm.






2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number


Instructions










(see source of the alarm and instructions fields of the



this alarm in WN7.0.2.0 release. In case of earlier SW




7/25/2019 Alarm_3G_RU_30


132 DN99580892


Id:0900d80580938c2b

Confidential




FAULT NAME : autonomous reset as recovery action

FAULT ID : 52: EFaultId_UnitAutonomousResetAl

MEANING : 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 missing

FAULT ID : 1899: EFaultId_2MExtRefMissAlMEANING : The reference clock monitoring has detected a loss of

2.048MHz signal received from an external reference source,

connected to Sync In interface of the System Module.


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.048MHz signal is available.


FAULT NAME : ATM cell loss

FAULT ID : 306: EFaultId_CellLossAl

MEANING : 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




4. Check the WAM, AXU and the cabling between them.

7/25/2019 Alarm_3G_RU_30


DN99580892 133



Id:0900d80580938c2b

Confidential

FAULT NAME : ATM, A2EA configuration error

FAULT ID : 315: EFaultId_A2eaConfigAl

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

FAULT NAME : Active clock tuning fault

FAULT ID : 1831: EFaultId_ActiveClkTuningAl

MEANING : The phase measurement cannot be performed in the active WSC or WMC.

INSTRUCTIONS: 1. Run fast tuning with BTS Site Manager.



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 Failure

FAULT ID : 1871: EFaultId_BusyAl

1872: EFaultId_FormatErrorAl

1873: EFaultId_UnsupportedProcedureAl

1874: EFaultId_OutOfRangeAl

MEANING : 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 failure

FAULT ID : 3100: EFaultId_AntennaLineFailureMEANING : The System Module or the device itself has detected an

7/25/2019 Alarm_3G_RU_30


134 DN99580892


Id:0900d80580938c2b

Confidential


abnormal operation or a failure in the antenna line device.


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 failure

FAULT ID : 1847: EFaultId_HardwareErrorAl

MEANING : 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 failure

FAULT ID : 1848: EFaultId_WorkingSoftwareMissingAl

1888: EFaultId_AlConfigurationFailureAl

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









missing.


7/25/2019 Alarm_3G_RU_30


DN99580892 135



Id:0900d80580938c2b

Confidential




UltraSite/EUBB:





alarming unit.

FlexiBTS:

1. Download two different SW packages so that the faulty file is removed from the BTS.



FAULT NAME : BTS reference clock missing

FAULT ID : 3080: EFaultId_BtsReferenceClockMissing

MEANING : This BTS fault indication is generated if the reference clock monitoring function of the BTS does not receive the

highest configured synchronization reference signal or if

all the synchronization reference signals are missing. The

BTS fault is not generated if the highest configured

synchronization source is present, no matter what the lower

level source statuses are.


There is a fixed synchronization priority list in the

FlexiBTS:

-Priority 1: PPS (Pulse Per Second) signal connected to the

Synchronization Input interface (Sync In) of the System

Module. Normally the PPS signal is generated by the GPS

receiver.

-Priority 2: external 2.048MHz signal connected to the Sync

In interface.

-Priority 3: the reference signal coming from the

integrated transmission unit (FTM).

7/25/2019 Alarm_3G_RU_30


136 DN99580892


Id:0900d80580938c2b

Confidential


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.




site reset.

4. The GPS cable and/or connectors might be damaged. Check

the cable and the connectors.


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

7/25/2019 Alarm_3G_RU_30


DN99580892 137



Id:0900d80580938c2b

Confidential

device and act accordingly. If this does not help, check

the cables. Note that because the device type is not known,

detailed instructions cannot be given - refer to the

appropriate user manual of the device for further actions.


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.


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 instability of

the transmission network, not to a failure in the unit.

If the previous steps do not help, there might be an

equipment failure in the System Module. Check the operation

and if performing a BTS site reset does not help, replace

the System Module.

FAULT NAME : BTS reset needed to activate a licence

FAULT ID : 1877: EFaultId_ResetNeededForLicenceAl

MEANING : The status of a license has changed to valid and a BTS

reset is needed to take the license into use.

INSTRUCTIONS: Reset the BTS.

7/25/2019 Alarm_3G_RU_30


138 DN99580892


Id:0900d80580938c2b

Confidential


FAULT NAME : BTS reset required

FAULT ID : 4001: EFaultId_BtsResetNeededAl

MEANING : 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 : BTS reset time increased

FAULT 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 will last longer due to additional actions

performed by BTS to recover from faulty situation.

INSTRUCTIONS: None

FAULT NAME : BTS time not corrected

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








alarm disappears.

FlexiBTS:




7/25/2019 Alarm_3G_RU_30


DN99580892 139



Id:0900d80580938c2b

Confidential


the alarm source:









UltraSite/EUBB:





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 : Cabinet door open

FAULT ID : 1300: EFaultId_DoorAl0

MEANING : 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 RNC

FAULT ID : 114: EFaultId_RncHoRespAl

MEANING : The BTS does not receive a response from the RNC (a block request).

7/25/2019 Alarm_3G_RU_30


140 DN99580892


Id:0900d80580938c2b

Confidential


INSTRUCTIONS: Check the signalling link settings and the RNC connections.













frequency, power).


local cell (LCR).



FAULT NAME : Difference between BTS master clock and reference frequency

FAULT ID : 9: EFaultId_DacWordChangeAl

MEANING : 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

7/25/2019 Alarm_3G_RU_30


DN99580892 141



Id:0900d80580938c2b

Confidential

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



situation may be caused by a fault of that signal. In that



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:






INSTRUCTIONS: Because there are several possibilities for the alarm

activation, a BTS Clock Frequency History feature has been

developed. You can access the stored history data via BTS

Site Manager. You can use the history data as a tool for finding out the reason for the fault/alarm situation (for

further instructions about the history feature, see the

online help of BTS Site Manager). Depending on the possible

reason, follow the instructions below:

1. In case of a fault in the transmission network

synchronization, you must correct the network

synchronization. The long-term accuracy of the Iub signal

must be 0.015 ppm or better (check the correct Iub accuracy

by measuring it). No actions on the BTS are necessarily

needed.

2. If the basic accuracy of the Iub signal is in order but


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,

7/25/2019 Alarm_3G_RU_30


142 DN99580892


Id:0900d80580938c2b

Confidential


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.



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


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



3GPP.

FAULT NAME : Error in file server during file download type

7/25/2019 Alarm_3G_RU_30


DN99580892 143



Id:0900d80580938c2b

Confidential

<fileTypeNumber>

FAULT ID : 27: EFaultId_FileServerAl

MEANING : The BTS is unable to obtain a file from the file server

(error in FTP open or FTP get). The file server is down,

the file is missing, or the path is incorrect. A possible

error in the DCN and Iub, or a user administration error

(an invalid username or password, or the user does not have

access rights for the files).

<fileTypeNumber> included in fault name is a variable

parameter identifying the type of file for which download

failure has been reported.

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.

FAULT NAME : FSM's sector based LCG is missing

FAULT ID : 4086: EFaultId_FsmSectorLcgMissing

MEANING : FSM does not have a sector-based LCG commissioned to it.

INSTRUCTIONS: Re-commission the BTS with a correct number of sector-based

LCGs so that every FSM has LCG.

FAULT NAME : Failure in optical RP3 interfaceFAULT ID : 3030: EFaultId_FailureInOptical_Rp3Interface

7/25/2019 Alarm_3G_RU_30


144 DN99580892


Id:0900d80580938c2b

Confidential







alarm disappears.















Module.

FAULT NAME : Fan failure

FAULT ID : 3050: EFaultId_FanFailure

MEANING : All the fans or more than one fan in the same fan group are

rotating slower than requested, are not rotating at all, or

the RPM information is not available for the fans. The

reason for this fault can be too low supply voltage or a

broken fan.


alarm disappears.


2. Replace the faulty fan module.

FAULT NAME : Fan module faulty

FAULT ID : 1: EFaultId_FanPowerAl


UltraSite/EUBB:

7/25/2019 Alarm_3G_RU_30


DN99580892 145



Id:0900d80580938c2b

Confidential

All the fans or more than one fan in the same fan group

(WFA, WTR, WPA/WMP, WHX) are rotating more slowly than

requested, do not rotate 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 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 works

correctly.

FlexiBTS:

All the fans or more than one fan in the same fan group

rotate more slowly than requested.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.


3. If that does not help, replace the WFA, WFD, or MFU

module or 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

FAULT ID : 0: EFaultId_ChangeFanAl

MEANING : A fan does not rotate or rotates slower than at the

requested speed, 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.


7/25/2019 Alarm_3G_RU_30


146 DN99580892


Id:0900d80580938c2b

Confidential


3. If that does not help, replace the WFA, WFD, or MFU

module or 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 fan and connector.

2. Replace the fan module.

FAULT NAME : File corrupted in SW downloadFAULT ID : 28: EFaultId_SwPackageAl

MEANING : The SW being downloaded is corrupted or incorrectly formed.


1. Retry the SW update.

2. Fetch the BTS log files and check the download status

from the BTS SWDLreport.

FlexiBTS:

1. Retry the SW update.

2. Save the snapshot and check the download status from the

BTS SWDLreport in the snapshot file.

FAULT NAME : GPS Receiver alarm: EEPROM invalid

FAULT ID : 4126: EFaultId_GpsReceiverEepromInvalidAl

MEANING : GPS receiver has detected that one or more EEPROM segments

were found to be corrupt at reset and had to be set to

their factory default settings.

INSTRUCTIONS: Perform the steps below in the listed order until the fault

disappears.

EEPROM invalid:

1. The GPS receiver has detected a malfunction in the

EEPROM memory of the GPS receiver. Perform a (remote) power

reset for the GPS receiver.


operation and change the GPS module, if needed.

7/25/2019 Alarm_3G_RU_30


DN99580892 147



Id:0900d80580938c2b

Confidential

FAULT NAME : GPS Receiver alarm: control interface not available

FAULT ID : 4011: EFaultId_GPSSystemElementAl

MEANING : BTS has detected communication problem with the GPS

receiver


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 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 a HW fault in the BTS System Module.

Check the operation and change the System Module, if

needed.

FAULT NAME : GPS Receiver alarm: no stored position

FAULT ID : 4124: EFaultId_GpsReceiverNoStoredPositionAl

MEANING : There is no accurate position stored in EEPROM.


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 reseted (either by manager command, by

power outage or by a GPS recovery reset). This means that

if the GPS receiver installation quality is only an average

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

7/25/2019 Alarm_3G_RU_30


148 DN99580892


Id:0900d80580938c2b

Confidential


FAULT NAME : GPS Receiver alarm: not tracking satellites

FAULT ID : 4122: EFaultId_GpsReceiverNotTrackingSatellitesAl

MEANING : Poor GPS antenna installation


disappears.

Not tracking satellites:

1. Absolutely the most common reason for this fault

indication is that the GPS antenna installation has not

been done properly, that is the sky visibility is not good

enough. Please refer the documentation for installations

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.





FAULT NAME : GPS Receiver alarm: position questionableFAULT ID : 4125: EFaultId_GpsReceiverPositionQuestionableAl

MEANING : The receiver is used stored position but has been moved to

a new position after that.


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.





7/25/2019 Alarm_3G_RU_30


DN99580892 149



Id:0900d80580938c2b

Confidential

FAULT NAME : GPS Receiver alarm: survey in progress

FAULT ID : 4123: EFaultId_GpsReceiverSurveyInProgressAl

MEANING : The GPS receiver is running a site/self survey


disappears.

Survey in progress:

1. Do nothing. The alarm is informative only. Normally the

GPS receiver runs the survey for two reasons: a) somebody

has started the survey manually, b) the GPS receiver has

noticed that the position has changed and the receiver has

started an automatic survey. Please notice also that

automatic survey takes place every time during first

start-up. 2. If the automatic survey takes place every now and then,

it might be an indication that the sky visibility is poor

and according to the poorly tracked satellites, the GPS

receiver concludes that the position has changed. In this

case, check the activity of the other faults (BTS fault

history data) and if found feasible, make re-installation

of the GPS antenna.

3. If the GPS installation is good but still the automatic

survey takes place every now and then, there might be a

malfunction in the GPS receiver. Perform a (remote) power

reset for the GPS receiver.

4. If the actions detailed in previous steps do not correct

the situation, there might be a HW fault in the GPS

receiver. Check the operation and change the GPS module, if

needed.

FAULT NAME : Heating element not working

FAULT ID : 1860: EFaultId_HeatingMatNotWorkingAl

MEANING : 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 configuration

FAULT ID : 4000: EFaultId_IncoherencyInConfigurationMEANING : Too many LCRs are commissioned to one RF Module.

7/25/2019 Alarm_3G_RU_30


150 DN99580892


Id:0900d80580938c2b

Confidential


INSTRUCTIONS: Recommission the BTS with a correct number of LCRs per RF

Module.





in the BTS.






FAULT NAME : Invalid Configuration file

FAULT ID : 4036: EFaultId_InvalidConfigurationFileAl

MEANING : The commissioning file is missing, or an incorrect

commissioning file has been detected during BTS startup as

follows: "Validation failed because of incompatible data"


file.

2. Recommission the BTS with the valid commissioning file.

FAULT NAME : MHA unit operation failure

FAULT ID : 1869: EFaultId_MinorTMAFaultAl

1870: EFaultId_MajorTMAFaultAl

MEANING : A fault in the Masthead Amplifier (MHA) is detected. The

fault reduces the gain performance or completely prevents

the MHA from functioning.

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.


FAULT NAME : Mast Head Amplifier fault

FAULT ID : 3120: EFaultId_MastHeadAmplifierFault


failure in the Masthead Amplifier (MHA).

Note that the Tower Mounted Amplifier (TMA) is a synonym

7/25/2019 Alarm_3G_RU_30


DN99580892 151



Id:0900d80580938c2b

Confidential

for the MHA and is used by the Antenna Interface Standards

Group (AISG).


alarm disappears.

1. Check the cables related to the Masthead Amplifier

(MHA).

2. Reset the alarming MHA module by blocking/unblocking the

RF Module which the MHA is connected to.

3. Replace the faulty device(s).

FAULT NAME : No connection to WEA and unable to detect External alarmsFAULT ID : 70: EFaultId_UnableToDetectEacAlarmsAl

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


FAULT NAME : No connection to unitFAULT ID : 10: EFaultId_NoConnectionToUnitAl





UltraSite/EUBB:




site.





bus cables.





If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First try to reset the site with the software. If

7/25/2019 Alarm_3G_RU_30


152 DN99580892


Id:0900d80580938c2b

Confidential







FlexiBTS:





FAULT NAME : Non fatal ATM traffic overload

FAULT ID : 305: EFaultId_CongestionAl

MEANING : Traffic load is approaching the maximum capacity. However,

no data is discarded yet.

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

match.

FAULT NAME : Not enough DSP capacity to set up a cell

FAULT 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 HSUPA

FAULT ID : 130: EFaultId_MinimumNumberOfClusterFractionsUnavailableAl

MEANING : There are not enough resources for the HSUPA minimum

capacity based on the commissioned parameters "Minimum

Baseband Decoding Capacity" and "Minimum HSUPA Users".


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 or replace the broken ones, or

re-commission the BTS and pre-reserve less capacity for the

HSUPA.

7/25/2019 Alarm_3G_RU_30


DN99580892 153



Id:0900d80580938c2b

Confidential

3. Reset the BTS to get the minimum capacity preselection

for the HSUPA in use.

FlexiBTS:


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.



UltraSite/EUBB:


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.



FAULT NAME : OIC MCU Buffer Full

FAULT ID : 2011: EFaultId_OIC_MCUBFullAl

MEANING : The control message traffic between the modules is

malfunctioning.

INSTRUCTIONS: Check the RF Module alarms.


FAULT ID : 903: EFaultId_OcxoClkMss

911: EFaultId_DualWscOcxoClkMss


by the other units.

INSTRUCTIONS: Replace the clock unit.


FAULT ID : 901: EFaultId_OcxoHeatingAl

912: EFaultId_DualWscOvAMss

MEANING : The heating of oven oscillator fails and the unit is broken. The ambient temperature can also be too low or

7/25/2019 Alarm_3G_RU_30


154 DN99580892


Id:0900d80580938c2b

Confidential


change too fast.

INSTRUCTIONS: 1. Check the active fan alarms.

2. Replace the clock unit.

FAULT NAME : PIC pool configuration mismatch

FAULT ID : 147: EFaultId_PicPoolConfigurationNotSupportedAl

MEANING : While sending the PIC pool configuration to Telecom, BTSSM

restricts the

use of "Large HSPA configuration" for an LCG with one or

three PIC pools in case of Flexi Rel2 BB HW (FSMC/D/E). But

during PIC pool reconfiguration at runtime, TCOM s checks

if operator changed PIC pool number to one or three. In

this case, Telecom rejects the PIC pool configuration and raises the fault saying "Large HSPA configuration needs two

PIC pools if PIC is active".

INSTRUCTIONS: When the fault is detected, BTSOM requests new PIC pool

configuration from BTSSM. Operator needs to commission PIC

pool configuration, so 0, 2 or 4 PIC pools are configured

in Rel2 HW for LCG with "Large HSPA configuration"

commissioned for Rel2 HW.

FAULT NAME : PPS reference missingFAULT ID : 1898: EFaultId_PpsRefMissAl

MEANING : The reference clock monitoring has detected a loss of PPS

signal in the reference received from the GPS receiver.

INSTRUCTIONS: 1. Check the GPS receiver installation.

2. Check the GPS receiver status.

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

FAULT NAME : Peer system module connection lost

FAULT ID : 4110: EFaultId_PeerSystemModuleConnectionLostAl

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 : RF Module failure

FAULT ID : 3010: EFaultId_RfModuleFailure

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

7/25/2019 Alarm_3G_RU_30


DN99580892 155



Id:0900d80580938c2b

Confidential


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.


Module.

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

FAULT NAME : RF Module overvoltage protection faulty

FAULT ID : 1942: EFaultId_FrOverVoltageProtectionFaulty

MEANING : RF Module overvoltage protection is broken.

INSTRUCTIONS: Replace the alarming RF Module.

FAULT NAME : RF module temperature is high

FAULT 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 power switched off remotely from BTS Site Manager

FAULT ID : 4107: EFaultId_RfPowerSwitchedOffFromBtsSmAl

MEANING : Power feeding for the given Radio Module has been switched

off by user from BTS Site Manager remotely.

INSTRUCTIONS: Enable power feeding towards Radio Module by switching RF

power on in BTS Site Manager.

FAULT NAME : Reading license targetID from BTS failed

FAULT ID : 4023: EFaultId_FrParameterReadFailedAl

MEANING : Failure occured during reading parameter from the Radio

Module.


alarm disappears.

7/25/2019 Alarm_3G_RU_30


156 DN99580892


Id:0900d80580938c2b

Confidential


1. Check the other active alarms. If the memory is


2. Reset the RF Module by blocking/unblocking it.


FAULT NAME : Reduced receiver capacity in cell

FAULT ID : 141: EFaultId_ReducedRachPreAmbleSignaturesAl

MEANING : The RNC has requested a higher number of PRACH preamble

signatures than the BTS can support for the requested cell

range.

INSTRUCTIONS: Commission a smaller 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_FrParameterMOExistenceCheckFailedAl

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


fault disappears.

1.Check the other active faults. If the memory is

corrupted, replace the alarming module.



FAULT NAME : Smoke alarm

FAULT ID : 1310: EFaultId_SmokeAl

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

7/25/2019 Alarm_3G_RU_30


DN99580892 157



Id:0900d80580938c2b

Confidential

FAULT NAME : System frame clock synchronization error in clock device

FAULT ID : 5004: EFaultId_BofuSfclkErr

5007: EFaultId_BofuFrameSyncErr

5008: EFaultId_BofuSfnSigErr

MEANING : 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 alarm

FAULT ID : 3040: EFaultId_TemperatureAlarmMEANING : The internal temperature of the RF Module or System Module








the BTS modules is unobstructed, that is, the BTS modules are not covered with anything. If the ambient temperature




it.







version.


FAULT NAME : Unit temperature is high

FAULT ID : 2: EFaultId_UnitOverheatAlMEANING : The temperature of a unit/module exceeds the threshold

7/25/2019 Alarm_3G_RU_30


158 DN99580892


Id:0900d80580938c2b

Confidential


value.

INSTRUCTIONS: Check the active fan alarms, and the airflow of the BTS.

FAULT NAME : WCI baseband reference clock failure

FAULT ID : 1001: EFaultId_RedundantClkMss

1002: EFaultId_MasterClkMss

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


3. Replace both WSC units.

FAULT NAME : WEA power regulator fault

FAULT ID : 1303: EFaultId_RegulatorAl

MEANING : 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 failure

FAULT ID : 1304: EFaultId_BatteryVoltageAl

1307: EFaultId_BatteryFailure

1308: EFaultId_CellBalanceAl

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

7/25/2019 Alarm_3G_RU_30


DN99580892 159



Id:0900d80580938c2b

Confidential

FAULT NAME : WIB unit battery temperature out of range

FAULT ID : 1306: EFaultId_BatteryTempAl

MEANING : 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 alarm

FAULT ID : 1305: EFaultId_BackupTimeAl

MEANING : 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 fault

FAULT ID : 907: EFaultId_DualWscDacWordAlarm


value. The alarm is activated if the WSC tunes the oven



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:


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












the fast tuning execution, it may result in adjusting the

BTS master clock frequency far from the nominal value,


7/25/2019 Alarm_3G_RU_30


160 DN99580892


Id:0900d80580938c2b

Confidential








4095).






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


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.



master clock adjustment is quite slow. You can perform the

tuning:

- manually, by changing the DAC word (during a site visit), or

7/25/2019 Alarm_3G_RU_30


DN99580892 161



Id:0900d80580938c2b

Confidential

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





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





3GPP.

FAULT NAME : WSC phase difference jammed to zero reading

FAULT 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


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

7/25/2019 Alarm_3G_RU_30


162 DN99580892


Id:0900d80580938c2b

Confidential








3GPP.

FAULT NAME : WSC switch unsuccessful

FAULT ID : 1823: EFaultId_ClkSwitchFailAl

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






alarm disappears.




3. Reset the BTS.


FAULT NAME : WSMA ST-Bus error

FAULT ID : 1117: EFaultId_WsmStLeftParityErr2

1119: EFaultId_WsmStLeftSyncErr2

1121: EfaultId_WsmStRightParityErr2

1123: EfaultId_WsmStRightSyncErr2

MEANING : The TX signal is transported from the WSP unit to all WTR


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.

7/25/2019 Alarm_3G_RU_30


DN99580892 163



Id:0900d80580938c2b

Confidential





instructions).

FAULT NAME : WSMA T-Bus error

FAULT ID : 1125: EFaultId_Wsp0ParityErr2

1127: EFaultId_Wsp0SyncErr2

1129: EFaultId_Wsp1ParityErr2


1133: EFaultId_Wsp2ParityErr2 1135: EFaultId_Wsp2SyncErr2







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


INSTRUCTIONS: Replace the units indicated in the alarm one by one and


instructions).

FAULT NAME : Waiting for RF connections

FAULT ID : 1859: EFaultId_WaitingRfConnectionAl

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

FAULT NAME : Writing parameter to Radio Module failed

7/25/2019 Alarm_3G_RU_30


164 DN99580892


Id:0900d80580938c2b

Confidential


FAULT ID : 4022: EFaultId_FrParameterWriteFailedAl

MEANING : Failure occured when writing parameter to the Radio Module

was requested.


fault disappears.

1. Check the other active faults. If the memory is




CancellingDo not cancel the alarm. The system cancels the alarm automatically when

the fault has been corrected.

7/25/2019 Alarm_3G_RU_30


DN99580892 165


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential

31 7653 CELL FAULTY

Meaning

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 of

the alarm.






2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number


Instructions













this alarm in BTS WN7.0.2.0 release. In case of earlier SW


descriptions refer WCDMA RAN and I-HSPA System Libraries.

The BTS fault descriptions are also included in BTS SW

7/25/2019 Alarm_3G_RU_30


166 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY

release documentation. If that does not help, contact your

local Nokia Siemens Networks representative.

FAULT NAME : AIR fatal alarm

FAULT ID : 1515: EFaultId_FatalAl

MEANING : 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 ID : 3100: EFaultId_AntennaLineFailure

MEANING : The System Module or the device itself has detected an



alarm disappears.



torque.



antenna line.


FAULT NAME : Antenna line faulty

FAULT ID : 4045: EFaultId_AntennaLineFaultyAl

MEANING : 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 fault

FAULT ID : 804: EFaultId_Ant1Al 809: EFaultId_Ant2Al

7/25/2019 Alarm_3G_RU_30


DN99580892 167


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential

814: EFaultId_Ant3Al

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

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 ID : 2016: EFaultId_Muksu_SMTimeOffAlMEANING : The master frame in the received baseband bus frame is not




place.






UltraSite/EUBB:


FAULT NAME : BTS config error (All units in a cell must be of same

freq)

FAULT ID : 58: EFaultId_FrequencyBandConflictInCellAl

MEANING : A unit with an incompatible frequency type has been detected. All units in the cell must be of the same

7/25/2019 Alarm_3G_RU_30


168 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY

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_NotEnoughHwForLcrAl


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.


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.

FAULT NAME : BTS config error (WAF overload, 50W not in dualWPA config)

FAULT ID : 61: EFaultId_WafTxConnectorOverloadAl

MEANING : 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_WpaWsmaVersionConflictAl

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

7/25/2019 Alarm_3G_RU_30


DN99580892 169


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential

FAULT NAME : BTS config error (WTR used as dual TRX behind WSMA)

FAULT ID : 54: EFaultId_WtrbWsmaVersionConflictAl

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







UltraSite/EUBB: The BTS unit properties data is invalid or missing.





UltraSite/EUBB:





alarming unit.

FlexiBTS:








failed, or a corrupted SW file has been detected in the

FLASH.



7/25/2019 Alarm_3G_RU_30


170 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY

FlexiBTS:











UltraSite/EUBB:







FAULT NAME : BTS reset required

FAULT ID : 4001: EFaultId_BtsResetNeededAl

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





pointed to a specific unit/module but there are several possible fault sources.

7/25/2019 Alarm_3G_RU_30


DN99580892 171


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential


alarm disappears.

FlexiBTS:





the alarm source:









UltraSite/EUBB:










FAULT NAME : Cell block rejected by RNC/I-HSPA

FAULT ID : 96: EFaultId_InternalCellBlockedAl

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


2. Check the mains power supply.

7/25/2019 Alarm_3G_RU_30


172 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY

FAULT NAME : Cell blocked

FAULT ID : 49: EFaultId_CellBlockedAl

MEANING : The user has blocked the cell with BTS Site Manager.

INSTRUCTIONS: To cancel the alarm, unblock the cell.

FAULT NAME : Cell calibration failure

FAULT ID : 117: EFaultId_InitCalibAl

MEANING : 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 monitoring

FAULT ID : 125: EFaultId_CellPowerAl

MEANING : The WPA/Radio output power has dropped.

There is a fault in the downlink transmission path.


UltraSite/EUBB:

1. Block/unblock the WPA. If there was an internal failure,

the unit needs to be blocked/unblocked to get it


2. Block/unblock the WTR belonging to the same LCR.

3. Check the RF TX cabling.

7/25/2019 Alarm_3G_RU_30


DN99580892 173


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential

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.


FAULT NAME : Commissioned antenna configuration not supported by HWFAULT ID : 4060: EFaultId_CommissionedAntConfNotSupportedByHwAl

MEANING : The configuration in the commissioning file is not

supported by the RF Module.


fault disappears.

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.






alarm disappears.








INSTRUCTIONS: 1. Check that the unit/module is properly connected. If the unit/module LED does not light up, the unit/module is

7/25/2019 Alarm_3G_RU_30


174 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY











1. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration.



frequency, power).


local cell (LCR).










alarm disappears.








4. Replace the alarming module's Small Form Factor Pluggable (SFP). Check also the SFP in the other end and

7/25/2019 Alarm_3G_RU_30


DN99580892 175


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential






Module.

FAULT NAME : Filter unit operation failed

FAULT ID : 1840: EFaultId_TuningFailureAl

1841: EFaultId_UnitFaultyAl

4043: EFaultId_TuningFrequencyOutOfRangeAl

MEANING : A filter has not been able to tune on an appropriate sub-band properly (tuning failure), or another major

failure has been detected by the filter (unit faulty).

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_FrFrameClockMissing

MEANING : The System Module clock reference differs from the RF

Module 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, block/unblock the site.

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


FAULT ID : 2047: EFaultId_OIC_FrSyncLostAl

MEANING : The timing of the new RP1 synchronization burst deviates





7/25/2019 Alarm_3G_RU_30


176 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY


FAULT ID : 1856: EFaultId_IncoherencyInCellConfigurationAl

MEANING : 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 ID : 4000: EFaultId_IncoherencyInConfiguration

MEANING : 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 Modules

FAULT ID : 1857: EFaultId_IncoherencyWithRFModulesAl

MEANING : 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 Modules are for the faulty frequency.

2. Replace the incompatible Radio Module(s).





in the BTS.









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

7/25/2019 Alarm_3G_RU_30


DN99580892 177


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential

FAULT NAME : Invalid carrier in WTR

FAULT ID : 127: EFaultId_InvalidCarrierInWtr

MEANING : 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_InvalidFrequencyChannelForBTSHW

MEANING : 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 failure

FAULT ID : 1839: EFaultId_LNAFailureAl

MEANING : The Filter has detected a malfunction in the LNA unit.

INSTRUCTIONS: Replace the alarming Radio module.

FAULT NAME : Missing RP3-01 link

FAULT ID : 4064: EFaultId_MissingRp301LinkAl

MEANING : Not enough RP3-01 links connected between FSM and FR.

Commissioned cells cannot be routed via existing RP3-01

links.


1. Check if other BTS fault indications are active.

2. Make sure that all RP3-01 fiber links and SFP

transceivers between system module and radio module are

properly connected and working. Add missing parallel RP3-01

links.

3. Restart the Radio Module. 4. Restart the BTS.

7/25/2019 Alarm_3G_RU_30


178 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY

FAULT NAME : Module Clock Faulty

FAULT ID : 1926: EFaultId_FrModuleClockFaulty

MEANING : The RF Module has lost the lock to the incoming clock.


Module.



FAULT NAME : Module not supported by current SW versionFAULT ID : 4063: EFaultId_NotSupportedModuleMixAl

MEANING : An unsupported module was found in the System Module.

Typically this happens when a System Module SW in use does

not support using the module.

INSTRUCTIONS: Replace the not supported module or upgrade the System

Module SW.

FAULT NAME : No WSM resources

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







UltraSite/EUBB:




site.



also be in the WPS unit or backplane. 5. Check the power cables and connectors as well as the I2C

7/25/2019 Alarm_3G_RU_30


DN99580892 179


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential

bus cables.












FlexiBTS:






FAULT ID : 1815: EFaultId_BbBus_SyncFailedAlMEANING : The baseband bus synchronization towards <x> failed.


FAULT NAME : Not enough WAF resources in LCR

FAULT ID : 98: EFaultId_NotEnoughWafResourcesPerCellAl

MEANING : 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 faulty

FAULT ID : 2000: EFaultId_OIC_TxAl 2001: EFaultId_OIC_PresAl

7/25/2019 Alarm_3G_RU_30


180 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY

MEANING : 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 failed

FAULT ID : 1925: EFaultId_FrPostTestFailed

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








FSP and FCM.









FlexiBTS:


Module.



7/25/2019 Alarm_3G_RU_30


DN99580892 181


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential

FAULT NAME : RF BB Bus Configuration Error

FAULT ID : 1905: EFaultId_FrRfBbBusConfigError

MEANING : The RF Module baseband bus is configured incorrectly.

INSTRUCTIONS: 1. Block/unblock the RF Module.



FAULT NAME : RF BB Bus Synchronisation Error

FAULT ID : 1904: EFaultId_FrRfBbBusSynchError

MEANING : The baseband bus between the System Module and RF Module is

out of synchronization.

INSTRUCTIONS: Note: In case of old RF HW rel1 start directly from step 2.


Module.




FAULT NAME : RF Module Filter input power missing

FAULT ID : 1910: EFaultId_FrFilterInputPowerMissing

MEANING : The RF Module filter has measured a TX power that is too

low.



FAULT NAME : RF Module Overheat

FAULT ID : 1913: EFaultId_FrOverheat

MEANING : The RF Module temperature is too high.




FAULT NAME : RF Module Power output faulty

FAULT ID : 1918: EFaultId_FrPowerOutputFaultMEANING : The Power Supply has detected an overvoltage, undervoltage,

7/25/2019 Alarm_3G_RU_30


182 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY

or overcurrent in the RF Module.



FAULT NAME : RF Module blocked

FAULT ID : 1931: EFaultId_FrBlocked

MEANING : A shared (Medusa) FR is blocked.

INSTRUCTIONS: Unblock the alarming module.

FAULT NAME : RF Module configuring failed

FAULT ID : 1900: EFaultId_FrConfiguringFailedMEANING : The RF Module configuration failed because of a HW or SW

fault.


FAULT NAME : RF Module critical file not found

FAULT ID : 1901: EFaultId_FrCriticalFileNotFound

MEANING : A critical configuration file is missing from the RF

Module.





failure in the internal functionality of the RF Module.


alarm disappears.




accordingly.



Module.


7/25/2019 Alarm_3G_RU_30


DN99580892 183


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential

FAULT NAME : RF Module out of order

FAULT ID : 1912: EFaultId_FrOutOfOrder

MEANING : The RF Module is out of order because of a software or

hardware fault.



FAULT NAME : RF loss of secondary optical interface

FAULT ID : 1930: EFaultId_FRLossOfSecondaryOptIf

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.




FAULT NAME : RX out of order

FAULT ID : 1911: EFaultId_FrRxOutOfOrderMEANING : The RF Module RX RF synthesizer is not locked.



FAULT NAME : Radio resources switched off

FAULT ID : 4057: EfaultId_RfSwitchedOffAl

MEANING : 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

due to operation under excessive VSWR value condition

(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 Interface

7/25/2019 Alarm_3G_RU_30


184 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY

FAULT ID : 2002: EFaultId_OIC_RxAl

MEANING : The incoming optical signal to the Small Form Factor

Pluggable (SFP) is missing or 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

Master System Module and Extension System Module is broken.

It may concern both 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 it is faulty.

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

behind the faulty link.


link>

FAULT ID : 2005: EFaultId_OIC_SyncChAlMEANING : The RP3 channel has lost the frame synchronization state






FAULT NAME : TX out of order

FAULT ID : 1907: EFaultId_FrTxOutOfOrder

MEANING : The RF Module TX path is not usable.



FAULT NAME : TX output power measurement fault

FAULT ID : 103: EFaultId_MeasurementAl


UltraSite/EUBB: The WTR or WPA/WMP/WOU output power

measurement has failed.

7/25/2019 Alarm_3G_RU_30


DN99580892 185


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential

FlexiBTS: The RF Module output power measurement has

failed.


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



Module.


FAULT NAME : Telecom configuration failureFAULT ID : 109: EFaultId_TcomSlaveRegAl






failure.

FlexiBTS:







Or



UltraSite/EUBB: Faraday unit to WSPF allocation failure.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode,

7/25/2019 Alarm_3G_RU_30


186 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY

UltraSite/EUBB:






FlexiBTS:




FlexiBTS Rel2: In case alarming unit is FSPC, block/unblock the alarming module.


FAULT ID : 3040: EFaultId_TemperatureAlarm









the BTS modules is unobstructed, that is, the BTS modules

are not covered with anything. If the ambient temperature




it.


FAULT NAME : Temperature too low (Heating ongoing)

FAULT ID : 1922: EFaultId_FrTemperatureTooLow

MEANING : During RF startup: The temperature inside the RF Module is

too low. Heating of module is ongoing. Wait until the alarm

is canceled. This might take up to 15 minutes.

During RF runtime: The temperature inside the RF module is

7/25/2019 Alarm_3G_RU_30


DN99580892 187


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential

going too low. 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 15 minutes.

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






FAULT NAME : Too many LCGs for HW to support

FAULT ID : 4004: EFaultId_TooManyLCGForHwAl

MEANING : 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 LPA

FAULT ID : 99: EFaultId_TooManyCarriersPerWpaAl

MEANING : Too many carriers have been allocated to the WPA/WMP.

INSTRUCTIONS: Remove the additional carrier in the Reconfiguration

commissioning.

FAULT NAME : Unit (module) dangerously overheating

FAULT ID : 1937: EFaultId_FrDangerouslyOverheat

MEANING : Validated sensor temperature is greater than or equal to

the predefined value on the unit property file.








7/25/2019 Alarm_3G_RU_30


188 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY



UltraSite/EUBB:





FlexiBTS:

















UltraSite/EUBB:









FlexiBTS:


7/25/2019 Alarm_3G_RU_30


DN99580892 189


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential











version.INSTRUCTIONS: Replace the unit or upgrade the BTS SW.











FAULT NAME : VSWR alarm

FAULT ID : 1837: EFaultId_VSWRMajorAl

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


matching.

FAULT NAME : WAF low noise amplifier faulty

FAULT ID : 800: EFaultId_Lna1Al 801: EFaultId_Lna2Al

7/25/2019 Alarm_3G_RU_30


190 DN99580892


Id:0900d80580938c2b

Confidential

7653 CELL FAULTY

805: EFaultId_Lna3Al




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


FAULT NAME : WPA power level changed

FAULT ID : 57: EFaultId_WpaPowerLevelChangedAl

MEANING : 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 error

FAULT ID : 1189: EFaultId_Rr0_0ParityErr2

1191: EFaultId_Rr0_0SyncErr2

1193: EFaultId_Rr0_1ParityErr2






MEANING : 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





check whether the problem is cleared.

3. Check the backplane cables and connectors (see

7/25/2019 Alarm_3G_RU_30


DN99580892 191


7653 CELL FAULTY

Id:0900d80580938c2b

Confidential


Cancelling

Do not cancel the alarm. The system cancels the alarm automatically when


7/25/2019 Alarm_3G_RU_30


192 DN99580892


Id:0900d80580938c2b

Confidential


32 7654 CELL OPERATION DEGRADED

Meaning

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


of the alarm.






2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number


Instructions













this alarm in BTS WN7.0.1.0 release. In case of earlier SW




7/25/2019 Alarm_3G_RU_30


DN99580892 193



Id:0900d80580938c2b

Confidential




link/RP3>


MEANING : The fibre cable has an interference; the data becomes

faulty.



example).



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


alarm, or replacing the RF Module does not clear the fault

situation, replace the System Module that causes the alarm.

FAULT NAME : AIR major alarm

FAULT ID : 1513: EFaultId_MajorAlMEANING : ARIO has detected a Major level alarm. Some ARIO alarms can






the error.

FAULT NAME : AIR minor alarm

FAULT ID : 1514: EFaultId_MinorAl

MEANING : ARIO has detected a Minor level alarm. Some ARIO alarms can



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_AntennaLineFailure

7/25/2019 Alarm_3G_RU_30


194 DN99580892


Id:0900d80580938c2b

Confidential


MEANING : The System Module or the device itself has detected an



alarm disappears.



torque.



antenna line.


FAULT NAME : Antenna Line Operation Degraded

FAULT ID : 4046: EFaultId_AntennaLineDegradedAl

MEANING : An alarm message has been received from the antenna line

device. The antenna line operation is degraded.

INSTRUCTIONS: Check the antenna line and antenna line device that causes

the alarm. Fix or replace the faulty parts/devices.

FAULT NAME : Antenna Line failure

FAULT ID : 1836: EFaultId_ALOvercurrentAl

4045: EFaultId_AntennaLineFaultyAl

MEANING : Radio Module (60W RRH) or Filter (all others) has detected

overcurrent on the antenna line. The antenna line might be

damaged (short circuit) or some antenna line device is

causing overload. All antenna line devices powered by the

antenna line are out of order.

INSTRUCTIONS: Check the antenna line and antenna line devices. Fix or

replace the faulty parts/devices.








7/25/2019 Alarm_3G_RU_30


DN99580892 195



Id:0900d80580938c2b

Confidential





configured.





FAULT ID : 804: EFaultId_Ant1Al

809: EFaultId_Ant2Al 814: EFaultId_Ant3Al




may be faulty.



after 5 minutes).

3. Check the antenna line (see Troubleshooting instructions).


a. Check the voltage (see connector pins in Troubleshooting

instructions).



sectors.

FAULT NAME : BTS Config error (Different WTR variants cannot coexist in

cell)

FAULT ID : 56: EFaultId_WtraWtrbVersionConflictInCellAl

MEANING : 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

7/25/2019 Alarm_3G_RU_30


196 DN99580892


Id:0900d80580938c2b

Confidential






system.




FAULT NAME : BTS config error (WSM missing from RF subrack)

FAULT ID : 62: EFaultId_NoWsmForWtrInSubrackAl

MEANING : 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

MEANING : Carrier candidates are commissioned for each cell (not

WTR/LTX specific).

INSTRUCTIONS: Recommission (Reconfiguration commissioning) the BTS with

the correct carrier candidate values.








missing.





UltraSite/EUBB:




3. If the fault still exists after 10 minutes, replace the alarming unit.

7/25/2019 Alarm_3G_RU_30


DN99580892 197



Id:0900d80580938c2b

Confidential

FlexiBTS:








failed, or a corrupted SW file has been detected in the FLASH.



FlexiBTS:




depending on the alarm source: a. Reset the RF Module by blocking/unblocking it.






UltraSite/EUBB:







7/25/2019 Alarm_3G_RU_30


198 DN99580892


Id:0900d80580938c2b

Confidential









alarm disappears.

FlexiBTS:





the alarm source:






5. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the


UltraSite/EUBB:











2. Block/unblock the alarming unit or the WPA connected to the alarming WTR. If there was an internal failure, the

7/25/2019 Alarm_3G_RU_30


DN99580892 199



Id:0900d80580938c2b

Confidential


it again.




4. Check the RF and WSM cabling (for example, in the case

of an incorrect cabling).






FAULT ID : 125: EFaultId_CellPowerAl

MEANING : The WPA/Radio output power has dropped.



UltraSite/EUBB:


the unit needs to be blocked/unblocked to get it initialized/configured again.




FlexiBTS:






FAULT NAME : Cell power parameter out of range

FAULT ID : 126: EFaultId_CellPowerParameterOutOfRangeAl

MEANING : The power values in the cell configuration data sent by the RNC are out of range.

7/25/2019 Alarm_3G_RU_30


200 DN99580892


Id:0900d80580938c2b

Confidential


INSTRUCTIONS: Set the correct power values to the RNC.






alarm disappears.
























frequency, power).


local cell (LCR).

7/25/2019 Alarm_3G_RU_30


DN99580892 201



Id:0900d80580938c2b

Confidential



FAULT NAME : Configuration file corrupted

FAULT ID : 1924: EFaultId_FrConfigurationFileCorrupted

MEANING : The RF Module SW detected conflicting or corrupted

configuration data.

INSTRUCTIONS: 1. Block/unblock the RF Module


FAULT NAME : Diversity antenna line faultFAULT ID : 803: EFaultId_Mha2Al

808: EFaultId_Mha4Al


MEANING : 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


FAULT NAME : FPGA SW update failed

FAULT ID : 1928: EFaultId_FrFpgaSwUpdateFailed

MEANING : The FPGA software update has failed.






an optical RP3 interface between two modules. The failure cannot be pointed to a specific module but there are

7/25/2019 Alarm_3G_RU_30


202 DN99580892


Id:0900d80580938c2b

Confidential




alarm disappears.









Pluggable (SFP). Check also the SFP in the other end and replace it, if needed.





Module.





MEANING : A filter has not been able to tune on an appropriate

sub-band properly (tuning failure), or another major







FAULT ID : 214: EFaultId_FlashWrAl

215: EFaultId_FlashRdAl

216: EFaultId_FlashEraseAl

217: EFaultId_FlashDrvAl

218: EFaultId_FlashDbChksumAl

MEANING : A flash memory operation failure. If this fault

continuously appears, the flash chip may be broken.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode,

7/25/2019 Alarm_3G_RU_30


DN99580892 203



Id:0900d80580938c2b

Confidential

UltraSite/EUBB:



2. Block/unblock the alarming unit. There are no recovery

actions and because of that the block/unblock can be

attempteded once. If that does not help, replace the

alarming unit.

FlexiBTS:


corrupted, change the alarming unit/module.

2. Block/unblock the alarming unit/module. There are no recovery actions and blocking/unblocking can be attempteded

once. If that does not help, replace the alarming

unit/module.

FAULT NAME : Frame clock missing

FAULT ID : 1903: EFaultId_FrFrameClockMissing

MEANING : The System Module clock reference differs from the RF

Module clock.

INSTRUCTIONS: 1. Check cables between the System Module and RF Module.




FAULT NAME : Gain adjust alarm

FAULT ID : 118: EFaultId_GainAdjustAl

MEANING : The WTR cannot adjust the TX output power.

INSTRUCTIONS: 1. Block/unblock the WTR. The unit needs to be

blocked/unblocked to get it initialised/configured again if

there was an internal failure.

2. Check the WTR RF TX cabling.


FAULT NAME : Incompatible SW version detectedFAULT ID : 23: EFaultId_IncompatibleSwVersionAl

7/25/2019 Alarm_3G_RU_30


204 DN99580892


Id:0900d80580938c2b

Confidential




in the BTS.






FAULT NAME : Initial calibration not started because other cell not

cleared

FAULT ID : 120: EFaultId_InitCalibNotStartedAl

MEANING : 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

internal failure.

2. Reset the site.










the function of the MHA.

INSTRUCTIONS: 1. Check the MHA type and configuration settings of BTS. If




FAULT NAME : Main antenna line faultFAULT ID : 802: EFaultId_Mha1Al

7/25/2019 Alarm_3G_RU_30


DN99580892 205



Id:0900d80580938c2b

Confidential



MEANING : 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








4. The fault can be in the WAF, Bias-T or MHA (see Troubleshooting instructions).






for the MHA and is used by the Antenna Interface Standards Group (AISG).


alarm disappears.


(MHA).




FAULT NAME : Mast Head Amplifier fault, <line>

FAULT ID : 1834: EFaultId_AboveCurrentWindowAl

1835: EFaultId_BelowCurrentWindowAl

MEANING : The Masthead Amplifier (MHA) does not work properly. The

received RF signal level is decreased.

If both stages of the LNA on the uplink path fail, the MHA

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 half of its normal gain.

7/25/2019 Alarm_3G_RU_30


206 DN99580892


Id:0900d80580938c2b

Confidential


With an integrated MHA (WMHC), the fault might affect both

main and diversity branches or just one 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 antenna lines and cells

related to the FR Module, not just the faulty one. If the

alarm reappears, replace the alarming module.



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

links.






links.

3. Restart the Radio Module.

4. Restart the BTS.





Module.









UltraSite/EUBB:

1. Check the fault history, alarming unit, and subrack. 2. If SW updates have been done recently, reload the SW.

7/25/2019 Alarm_3G_RU_30


DN99580892 207



Id:0900d80580938c2b

Confidential


site.





bus cables.












FlexiBTS:



the alarming module. 2. Check the fault history.

FAULT NAME : No feedback signal

FAULT ID : 1920: EFaultId_FrNoFeedBackSignal

MEANING : The feedback signal to predistortion is too weak or

missing. The TX performance is degraded.




FAULT ID : 98: EFaultId_NotEnoughWafResourcesPerCellAl

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

7/25/2019 Alarm_3G_RU_30


208 DN99580892


Id:0900d80580938c2b

Confidential


MetroSite 50:

Change the WAF.

FAULT NAME : Optical Interface Data/Control/Ethernet Buffer Full

FAULT ID : 2006: EFaultId_OIC_DBRxFullAl

2007: EFaultId_OIC_DBTxFullAl

2008: EFaultId_OIC_CBRxFullAl

2009: EFaultId_OIC_CBTxFullAl

2010: EFaultId_OIC_EBFullAl

MEANING : The RP3 or Ethernet buffering is not working and the buffer

becomes full. The optical device is malfunctioning. The

fault might be generated because of synchronization

problems or incorrect initialization.INSTRUCTIONS: Swap the alarming and working links. Then check where the

alarm is now reported. If the alarming link remains the



FAULT NAME : Optical interface buffer alarm

FAULT ID : 2051: EFaultId_Muksu_BufferAl

MEANING : 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



connected module/unit behind the interface that causes the

alarm.

FlexiBTS:

3. If the System Module is the only alarm source, or



causes 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 : Pipe dangerously overheating

7/25/2019 Alarm_3G_RU_30


DN99580892 209



Id:0900d80580938c2b

Confidential

FAULT ID : 1938: EFaultId_FrPipeOverheat

MEANING : Validated temperature of any PA sensor is greater than or

equal to the predefined value on unit property file.




FAULT NAME : Post test failed

FAULT ID : 1925: EFaultId_FrPostTestFailed

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








FSP and FCM.









FlexiBTS:


Module.



FAULT NAME : RET Antenna control failure

7/25/2019 Alarm_3G_RU_30


210 DN99580892


Id:0900d80580938c2b

Confidential


FAULT ID : 1842: EFaultId_MotorJamAl

1843: EFaultId_ActuatorJamAl

1844: EFaultId_NotCalibratedAl

1845: EFaultId_NotConfiguredAl

1846: EFaultId_ActuatorInterferenceAl

MEANING : 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 Energy too high

FAULT ID : 1909: EFaultId_FrBbEnergyTooHigh

MEANING : The TX feedback signal power is too high.INSTRUCTIONS: 1. Block/unblock the RF Module.


FAULT NAME : RF BB bus configuration error






FAULT NAME : RF BB bus connection transmission error

FAULT ID : 1906: EFaultId_FrRfBbBusConnTransError

MEANING : There is an error in the baseband or optical bus.



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

FAULT NAME : RF BB bus synchronisation error

FAULT ID : 1904: EFaultId_FrRfBbBusSynchError

MEANING : The baseband bus between the System Module and 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

7/25/2019 Alarm_3G_RU_30


DN99580892 211



Id:0900d80580938c2b

Confidential

Module.




FAULT NAME : RF Module Filter input power missing

FAULT ID : 1910: EFaultId_FrFilterInputPowerMissing

MEANING : The RF Module filter has measured a TX power that is too

low.



FAULT NAME : RF Module Gain adjusting failure

FAULT ID : 1908: EFaultId_FrGainAdjust

MEANING : The TX output power adjustment failed.










FAULT ID : 1918: EFaultId_FrPowerOutputFault

MEANING : The Power Supply has detected an overvoltage, undervoltage,




FAULT NAME : RF Module blockedFAULT ID : 1931: EFaultId_FrBlocked

7/25/2019 Alarm_3G_RU_30


212 DN99580892


Id:0900d80580938c2b

Confidential





FAULT ID : 1900: EFaultId_FrConfiguringFailed

MEANING : The RF Module configuration failed because of a HW or SW

fault.




MEANING : A critical configuration file is missing from the RF Module.







alarm disappears.




accordingly.



Module.


FAULT NAME : RF Module file not found

FAULT ID : 1902: EFaultId_FrFileNotFound

MEANING : The RF Module SW detected that a non-critical configuration

file is missing.

INSTRUCTIONS: 1.Block/unblock the RF Module.

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

7/25/2019 Alarm_3G_RU_30


DN99580892 213



Id:0900d80580938c2b

Confidential



MEANING : The RF Module is out of order because of a software or

hardware fault.



FAULT NAME : RF Power decreased

FAULT ID : 1927: EFaultId_FrPowerDecreased

MEANING : The highest temperature exceeds the power decrease limit.



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

Module.


FAULT NAME : RP3 RX data frame timing error

FAULT ID : 5003: EFaultId_BofuRxAlignErr

MEANING : The RP3 RX receiver has detected that the incoming data frame is outside of the alignment window.



FAULT NAME : RP3 uplink/downlink buffering error

FAULT ID : 5005: EFaultId_BofuUlBufErr

5006: EFaultId_BofuDlBufErr

MEANING : Uplink buffering from Rbus to RP3, or vice versa downlink

buffering from RP3 to Tbus does not work. Timing parameters

DELTA/RBUS_START_TIME, and/or PI/TBUS_START_TIME are

incorrectly set.



FAULT NAME : RS485 IUANT port failure

FAULT ID : 4069: EFaultId_Rs485PowerFailureAl

MEANING : Radio Module or Filter (all others) has detected overcurrent on RS485 IUANT

7/25/2019 Alarm_3G_RU_30


214 DN99580892


Id:0900d80580938c2b

Confidential


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 order

FAULT ID : 1911: EFaultId_FrRxOutOfOrder

MEANING : The RF Module RX RF synthesizer is not locked.



FAULT NAME : Radio resources switched offFAULT ID : 4057: EfaultId_RfSwitchedOffAl











matching.

FAULT NAME : Rbus data clock missing

FAULT ID : 5011: EFaultId_BofuRbusClockError

MEANING : Data traffic from Rbus to RP3 in BOFU FPGA is

malfunctioning because of errors in the Rbus

synchronization clock.



7/25/2019 Alarm_3G_RU_30


DN99580892 215



Id:0900d80580938c2b

Confidential


FAULT ID : 2002: EFaultId_OIC_RxAl

MEANING : The incoming optical signal to the Small Form Factor


has been detached.







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


it if faulty.



FAULT NAME : Rx signal level failure

FAULT ID : 133: EFaultId_RxAntennaSignalLevelTooLowAl

134: EFaultId_RxAntennaSignalLevelDifferenceTooHighAl

MEANING : 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 7dB).


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

7/25/2019 Alarm_3G_RU_30


216 DN99580892


Id:0900d80580938c2b

Confidential


inadequate RX level. Check and replace the faulty

equipment.

FlexiBTS:

1. Check BTS Site Manager for the received signal levels to




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

FAULT ID : 1850: EFaultId_SwCorruptedAl

4029: EFaultId_SwCorruptedPermanentAl

MEANING : A corrupted SW file in the FLASH is detected.

Unit cannot complete start-up.

INSTRUCTIONS: Update the SW to the BTS.












failed.


UltraSite/EUBB:


7/25/2019 Alarm_3G_RU_30


DN99580892 217



Id:0900d80580938c2b

Confidential



2. Check the units and the RF cabling between the

WPA/WMP/WOU and WTR units.

FlexiBTS:


function. If there was an internal failure or sticking in

the unit SW, the Module needs to be blocked/unblocked to



Module.








RNW configuration failure. Telecom RNW reconfiguration failure.

FlexiBTS:

- FSP unit to FCM allocation failure.

- Faraday unit to FSP allocation failure.





Or





UltraSite/EUBB:




7/25/2019 Alarm_3G_RU_30


218 DN99580892


Id:0900d80580938c2b

Confidential


UltraSite/EUBB: If alarming unit is WSPF, block/unblock the

EUBB subrack.

FlexiBTS:




FlexiBTS Rel2: If alarming unit is FSPC, block/unblock the

alarming module.


FAULT ID : 3040: EFaultId_TemperatureAlarmMEANING : The internal temperature of the RF Module or System Module







ambient temperature is too high, make sure the airflow

towards 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 and reach the threshold value.


it.






FAULT NAME : Transmission quality deteriorated

FAULT ID : 1921: EFaultId_FrTransmissionQualityDetoriated

MEANING : The TX signal adjustment fails.



7/25/2019 Alarm_3G_RU_30


DN99580892 219



Id:0900d80580938c2b

Confidential

FAULT NAME : Under- / overrunning error in RP3 serializer clock crossing

FIFO

FAULT ID : 5002: EFaultId_BofuRxClkError

MEANING : Either too large clock jitter between received signal and

internal clock, or missing data input signal. The receiver

is started up again.



FAULT NAME : Unit (module) dangerously overheatingFAULT ID : 1937: EFaultId_FrDangerouslyOverheat


the predefined value on unit property file.




FAULT NAME : Unit SW download failedFAULT ID : 6: EFaultId_SwDownloadAl





UltraSite/EUBB:





FlexiBTS:





FAULT ID : 48: EFaultId_UnitBlockedAlMEANING : A unit is blocked with BTS Site Manager.

7/25/2019 Alarm_3G_RU_30


220 DN99580892


Id:0900d80580938c2b

Confidential












UltraSite/EUBB:




why the WAM switch-over occurred.





FlexiBTS:












version.


7/25/2019 Alarm_3G_RU_30


DN99580892 221



Id:0900d80580938c2b

Confidential

FAULT NAME : Unit unidentified

FAULT ID : 1923: EFaultId_FrUnitUnidentified

MEANING : The permanent memory in the module is corrupted and the

module product code or serial number is missing, or the

module product code is unknown.




















matching.


FAULT ID : 1838: EFaultId_VSWRMinorAl

MEANING : Radio Module (60W RRH)/the Filter (all others) has detected

a VSWR value exceeding the defined level. The antenna line

is slightly mismatched.




matching.

7/25/2019 Alarm_3G_RU_30


222 DN99580892


Id:0900d80580938c2b

Confidential



FAULT ID : 800: EFaultId_Lna1Al












fault, but blocking/unblocking the unit ensures that before a site visit.






1195: EFaultId_Rr0_1SyncErr2 1197: EFaultId_Rr1_0ParityErr2













3. Check the backplane cables and connectors (see



FAULT ID : 3001: EFaultId_EubbWsmAlMEANING : The BTS has detected an abnormal operation or a failure in

7/25/2019 Alarm_3G_RU_30


DN99580892 223



Id:0900d80580938c2b

Confidential



alarm disappears.




3. Reset the BTS.


Cancelling

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

7/25/2019 Alarm_3G_RU_30


7/25/2019 Alarm_3G_RU_30


DN99580892 225



Id:0900d80580938c2b

Confidential




link/RP3>


MEANING : The fiber cable has interference; the data becomes faulty.



example).




RF Module causing the alarm.


alarm, or if replacing the RF Module does not clear the

fault situation, replace the System Module causing the

alarm.

FAULT NAME : AIR major alarm

FAULT ID : 1513: EFaultId_MajorAl

MEANING : ARIO has detected a Major level alarm. Some ARIO alarms can be canceled without a reset but most ARIO alarms require





the error.

FAULT NAME : AIR minor alarm

FAULT ID : 1514: EFaultId_MinorAl

MEANING : ARIO has detected a Minor level alarm. Some ARIO alarms can



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 ID : 3100: EFaultId_AntennaLineFailureMEANING : The System Module or the device itself has detected an

7/25/2019 Alarm_3G_RU_30


226 DN99580892


Id:0900d80580938c2b

Confidential




alarm disappears.



torque.



antenna line.


FAULT NAME : Antenna Line failure

FAULT ID : 1836: EFaultId_ALOvercurrentAl

MEANING : Radio Module (60W RRH) or Filter (all others) has detected

overcurrent on the antenna line. The antenna line might be

damaged (short circuit) or some antenna line device is

causing overload. All antenna line devices powered by the

antenna line are out of order.

INSTRUCTIONS: 1. Check the antenna line and antenna line devices. Fix or

replace the faulty parts/devices.

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












configured.




7/25/2019 Alarm_3G_RU_30


DN99580892 227



Id:0900d80580938c2b

Confidential

FAULT NAME : Antenna line operation degraded

FAULT ID : 4046: EFaultId_AntennaLineDegradedAl

MEANING : 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 ID : 804: EFaultId_Ant1Al

809: EFaultId_Ant2Al 814: EFaultId_Ant3Al




may be faulty.



after 5 minutes).

3. Check the antenna line (see Troubleshooting instructions).


a. Check the voltage (see connector pins in Troubleshooting

instructions).



sectors.

FAULT NAME : BTS Config error (Different WTR variants cannot coexist in

cell)

FAULT ID : 56: EFaultId_WtraWtrbVersionConflictInCellAl

MEANING : 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

7/25/2019 Alarm_3G_RU_30


228 DN99580892


Id:0900d80580938c2b

Confidential






system.




FAULT NAME : BTS config error (WSM missing from RF subrack)

FAULT ID : 62: EFaultId_NoWsmForWtrInSubrackAl

MEANING : 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

MEANING : Carrier candidates are commissioned for each cell (not

WTR/LTX specific).

INSTRUCTIONS: Recommission (Reconfiguration commissioning) the BTS with

the correct carrier candidate values.








missing.





UltraSite/EUBB:




3. If the fault still exists after 10 minutes, replace the alarming unit.

7/25/2019 Alarm_3G_RU_30


DN99580892 229



Id:0900d80580938c2b

Confidential

FlexiBTS:








failed, or a corrupted SW file has been detected in the FLASH.



FlexiBTS:




depending on the alarm source: a. Reset the RF Module by blocking/unblocking it.






UltraSite/EUBB:







7/25/2019 Alarm_3G_RU_30


230 DN99580892


Id:0900d80580938c2b

Confidential









alarm disappears.

FlexiBTS:





the alarm source:






5. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the


UltraSite/EUBB:











7/25/2019 Alarm_3G_RU_30


DN99580892 231



Id:0900d80580938c2b

Confidential






2. Block/unblock the alarming unit or the WPA connected to

the alarming WTR. If there was an internal failure, the


it again.




4. Check the RF and WSM cabling (for example, in the case of an incorrect cabling).






FAULT ID : 125: EFaultId_CellPowerAlMEANING : The WPA/Radio output power has dropped.



UltraSite/EUBB:


the unit needs to be blocked/unblocked to get it





FlexiBTS:





7/25/2019 Alarm_3G_RU_30


232 DN99580892


Id:0900d80580938c2b

Confidential



FAULT NAME : Cell power parameter out of range

FAULT ID : 126: EFaultId_CellPowerParameterOutOfRangeAl

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




faulty, or there is a mismatch between them.INSTRUCTIONS: Note: Perform the steps below in the listed order until the

alarm disappears.




FAULT NAME : Communication failureFAULT ID : 1806: EFaultId_CommunicationFailureAl















1. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration.

7/25/2019 Alarm_3G_RU_30


DN99580892 233



Id:0900d80580938c2b

Confidential



frequency, power).


local cell (LCR).



FAULT NAME : Configuration file corrupted

FAULT ID : 1924: EFaultId_FrConfigurationFileCorrupted

MEANING : The RF Module SW detected conflicting or corrupted configuration data.

INSTRUCTIONS: 1. Block/unblock the RF Module


FAULT NAME : Diversity antenna line fault

FAULT ID : 803: EFaultId_Mha2Al


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










FAULT NAME : FPGA SW update failed

FAULT ID : 1928: EFaultId_FrFpgaSwUpdateFailed

MEANING : The FPGA software update has failed.



7/25/2019 Alarm_3G_RU_30


234 DN99580892


Id:0900d80580938c2b

Confidential









alarm disappears.



Module/Extension System Module. Note that dirty optical connectors may cause the signal level to drop too low.











Module.





MEANING : A filter has not been able to tune on an appropriate

sub-band properly (tuning failure), or another major







7/25/2019 Alarm_3G_RU_30


7/25/2019 Alarm_3G_RU_30


236 DN99580892


Id:0900d80580938c2b

Confidential


2. Check the WTR RF TX cabling.






in the BTS.






FAULT NAME : Initial calibration not started because other cell not

cleared

FAULT ID : 120: EFaultId_InitCalibNotStartedAl

MEANING : 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

internal failure.

2. Reset the site.










the MHA from functioning.INSTRUCTIONS: 1. Check the MHA type and configuration settings of BTS. If

7/25/2019 Alarm_3G_RU_30


DN99580892 237



Id:0900d80580938c2b

Confidential




FAULT NAME : Main antenna line fault

FAULT ID : 802: EFaultId_Mha1Al



MEANING : 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


faulty, the Bias-T is faulty, the MHA is faulty, another antenna line device between the MHA and WAF is faulty, or












for the MHA and is used by the Antenna Interface Standards

Group (AISG).


alarm disappears.


(MHA).




FAULT NAME : Mast Head Amplifier fault, <line>

7/25/2019 Alarm_3G_RU_30


238 DN99580892


Id:0900d80580938c2b

Confidential


FAULT ID : 1834: EFaultId_AboveCurrentWindowAl

1835: EFaultId_BelowCurrentWindowAl

MEANING : The Masthead Amplifier (MHA) does not work properly. The

received RF signal level is decreased.

If both stages of the LNA on the uplink path fail, the MHA

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 half of its normal gain.

With an integrated MHA (WMHC), the fault might affect both

main and diversity branches or just one 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 antenna lines and cells

related to the FR Module, not just the faulty one. If the

alarm reappears, replace the alarming module.



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





links.

3. Restart the Radio Module.

4. Restart the BTS.





Module.




7/25/2019 Alarm_3G_RU_30


DN99580892 239



Id:0900d80580938c2b

Confidential






UltraSite/EUBB:




site.





bus cables.








If the WSMF unit is not present (replaced by WSMB)in BTS, alarming WSPFs are not used and should be removed from BTS.



FlexiBTS:





FAULT NAME : No feedback signal

FAULT ID : 1920: EFaultId_FrNoFeedBackSignal

MEANING : The feedback signal to predistortion is too weak or

missing. The TX performance is degraded.




7/25/2019 Alarm_3G_RU_30


7/25/2019 Alarm_3G_RU_30


242 DN99580892


Id:0900d80580938c2b

Confidential








FlexiBTS:


Module.



FAULT NAME : RET Antenna control failure

FAULT ID : 1842: EFaultId_MotorJamAl

1843: EFaultId_ActuatorJamAl

1844: EFaultId_NotCalibratedAl

1845: EFaultId_NotConfiguredAl 1846: EFaultId_ActuatorInterferenceAl

MEANING : 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 Error






FAULT NAME : RF BB Bus Connection Transmission Error

FAULT ID : 1906: EFaultId_FrRfBbBusConnTransError

MEANING : There is an error in the baseband or optical bus.INSTRUCTIONS: 1. Block/unblock the RF Module.

7/25/2019 Alarm_3G_RU_30


7/25/2019 Alarm_3G_RU_30


244 DN99580892


Id:0900d80580938c2b

Confidential









FAULT ID : 1918: EFaultId_FrPowerOutputFault

MEANING : The Power Supply has detected an overvoltage, undervoltage,




FAULT NAME : RF Module blocked

FAULT ID : 1931: EFaultId_FrBlocked




FAULT ID : 1900: EFaultId_FrConfiguringFailed

MEANING : The RF Module configuration failed because of a HW or SW

fault.




MEANING : A critical configuration file is missing from the RF

Module.







alarm disappears.

7/25/2019 Alarm_3G_RU_30


DN99580892 245



Id:0900d80580938c2b

Confidential




accordingly.



Module.


FAULT NAME : RF Module file not found

FAULT ID : 1902: EFaultId_FrFileNotFoundMEANING : The RF Module SW detected that a non-critical configuration

file is missing.

INSTRUCTIONS: 1.Block/unblock the RF Module.

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



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



FAULT NAME : RF Power decreased

FAULT ID : 1927: EFaultId_FrPowerDecreased

MEANING : The highest temperature exceeds the power decrease limit.



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

Module.


FAULT NAME : RP3 RX data frame timing error

FAULT ID : 5003: EFaultId_BofuRxAlignErr

MEANING : The RP3 RX receiver has detected that the incoming data frame is outside of the alignment window.

7/25/2019 Alarm_3G_RU_30


7/25/2019 Alarm_3G_RU_30


DN99580892 247



Id:0900d80580938c2b

Confidential











matching.

FAULT NAME : Rbus data clock missing

FAULT ID : 5011: EFaultId_BofuRbusClockErrorMEANING : Data traffic from Rbus to RP3 in BOFU FPGA is

malfunctioning because of errors in the Rbus

synchronization clock.




FAULT ID : 2002: EFaultId_OIC_RxAlMEANING : The incoming optical signal to the Small Form Factor


has been detached.







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.


it, if it is faulty.



FAULT NAME : Rx signal level failure

7/25/2019 Alarm_3G_RU_30


248 DN99580892


Id:0900d80580938c2b

Confidential


FAULT ID : 133: EFaultId_RxAntennaSignalLevelTooLowAl

134: EFaultId_RxAntennaSignalLevelDifferenceTooHighAl

MEANING : 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 7dB).


1. Check BTS Site Manager for received signal levels to




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:

1. Check BTS Site Manager for the received signal levels to




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

FAULT ID : 1850: EFaultId_SwCorruptedAl

4029: EFaultId_SwCorruptedPermanentAl

MEANING : A corrupted SW file in the FLASH is detected.

Unit cannot complete start-up.

INSTRUCTIONS: Update the SW to the BTS.

7/25/2019 Alarm_3G_RU_30


DN99580892 249



Id:0900d80580938c2b

Confidential












failed.


UltraSite/EUBB:




2. Check the units and the RF cabling between the WPA/WMP/WOU and WTR units.

FlexiBTS:


function. If there was an internal failure or sticking in

the unit SW, the Module needs to be blocked/unblocked to



Module.








RNW configuration failure. Telecom RNW reconfiguration failure.

7/25/2019 Alarm_3G_RU_30


250 DN99580892


Id:0900d80580938c2b

Confidential


FlexiBTS:







Or



UltraSite/EUBB: Faraday unit to WSPF allocation failure.INSTRUCTIONS: UltraSite, MetroSite, MetroSite 50, Triple-mode,

UltraSite/EUBB:






FlexiBTS:







FAULT ID : 3040: EFaultId_TemperatureAlarm









the BTS modules is unobstructed, that is, the BTS modules are not covered with anything. If the ambient temperature

7/25/2019 Alarm_3G_RU_30


DN99580892 251



Id:0900d80580938c2b

Confidential




it.






FAULT NAME : Transmission quality deteriorated

FAULT ID : 1921: EFaultId_FrTransmissionQualityDetoriated

MEANING : The TX signal adjustment fails.



FAULT NAME : Under- / overrunning error in RP3 serializer clock crossing FIFO

FAULT ID : 5002: EFaultId_BofuRxClkError

MEANING : Either too large clock jitter between received signal and

internal clock, or missing data input signal. The receiver

is started up again.



FAULT NAME : Unit (module) dangerously overheating

FAULT ID : 1937: EFaultId_FrDangerouslyOverheat


the predefined value on the unit property file.




FAULT NAME : Unit SW download failedFAULT ID : 6: EFaultId_SwDownloadAl

7/25/2019 Alarm_3G_RU_30


252 DN99580892


Id:0900d80580938c2b

Confidential






UltraSite/EUBB:





FlexiBTS:


2. FCM: Reset the BTS. 3. If Step 2 does not help, replace the alarming module.














UltraSite/EUBB:









7/25/2019 Alarm_3G_RU_30


7/25/2019 Alarm_3G_RU_30


254 DN99580892


Id:0900d80580938c2b

Confidential








matching.


FAULT ID : 1838: EFaultId_VSWRMinorAl

MEANING : 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



matching.


FAULT ID : 800: EFaultId_Lna1Al

801: EFaultId_Lna2Al 805: EFaultId_Lna3Al










fault, but blocking/unblocking the unit ensures that before

a site visit.






1195: EFaultId_Rr0_1SyncErr2 1197: EFaultId_Rr1_0ParityErr2

7/25/2019 Alarm_3G_RU_30


DN99580892 255



Id:0900d80580938c2b

Confidential













3. Check the backplane cables and connectors (see Troubleshooting instructions).






alarm disappears.




3. Reset the BTS.


Cancelling

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

7/25/2019 Alarm_3G_RU_30


256 DN99580892


Id:0900d80580938c2b

Confidential

7660 BASE STATION LICENCE EXPIRED

34 7660 BASE STATION LICENCE EXPIRED

Meaning

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


of the alarm.






2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number

7 feature code


Instructions

See the BTS faults documents in WCDMA RAN and I-HSPA System

Libraries for details about BTS license management.

FAULT NAME : Feature expiration notification <featCode>, <featName>, <expDate>

FAULT ID : 4002: EFaultId_LicenceExpired

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

7/25/2019 Alarm_3G_RU_30


7/25/2019 Alarm_3G_RU_30


258 DN99580892


Id:0900d80580938c2b

Confidential


35 7661 BASE STATION LICENCE NOTIFICA-

TION

Meaning

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


of the alarm.






2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number

7 feature code


Instructions

See the BTS faults documents in WCDMA RAN and I-HSPA System

Libraries for details about BTS licence management.

FAULT NAME : Failure in license activation

FAULT ID : 4037: EFaultId_FailureInLicenceActivationAl

MEANING : Generation of target Id failed and because of that 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.


alarm disappears.


7/25/2019 Alarm_3G_RU_30


DN99580892 259



Id:0900d80580938c2b

Confidential

2. Reset the BTS.


have been purchased and installed.

FAULT NAME : Feature expiration notification <featCode>, <featName>,

<expDate>

FAULT ID : 4002: EFaultId_LicenceExpired

MEANING : 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_HWCapacityTooLowAl

MEANING : 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 Al

MEANING : The BTS detected a resource requiring a license but no

license exists nor is available.

INSTRUCTIONS: Activate the appropriate license or increase the license

amount.

FAULT NAME : TargetId verification failure

FAULT ID : 4056: EFaultId_TargetIdVerificationFailureAl

MEANING : NetAct Licence Manager did not respond to the verification

request. TargetId verification was not possible.


fault disappears.


2. Reset the BTS.


have been purchased

and installed.

7/25/2019 Alarm_3G_RU_30


260 DN99580892


Id:0900d80580938c2b

Confidential


Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 261



Id:0900d80580938c2b

Confidential

36 7665 BASE STATION TRANSMISSION

ALARM

Meaning

A transmission fault (or faults) has occurred in the BTS. This alarm is

an encapsulation alarm that is used to transfer the Flexi Transport

Submodule (FTM) alarm data over the BTS O&M connection through RNC and

OMS to NetAct. Encapsulation is used because the RNC alarm system cannot

support the FTM alarms directly due to differences in the alarm structure.

In NetAct and OMS this alarm is shown in opened format. This means that

the alarm number, alarm text and supplementary information are shown in

original FTM format and the alarm printout is thus different in NetAct

compared to alarm listings in RNC MML interface that shows these FTM

alarms as instances of alarm number 7665.

Check the reason for the fault from the supplementary information fields

and supplementary text field of the alarm. The actual documentation for

the encapsulated alarm can be found in the BTS faults documents in

WCDMA RAN and I-HSPA System Libraries.

The effect of the fault on the functioning of the network element depends

on the fault description. For more information, see base station fault

descriptions in WCDMA RAN and I-HSPA System Libraries.


1 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

Instructions

This alarm is an encapsulation alarm for original FTM alarm.

Follow up the instructions given in the BTS faults documents in WCDMA RAN

and I-HSPA System Libraries for the alarm number shown in supplementary

information field 3.

FAULT NAME : AIS (Administrative Unit) on unit $U, interface $IF

FAULT ID : 61106: FTM_AIS_AU

MEANING : 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

7/25/2019 Alarm_3G_RU_30


262 DN99580892


Id:0900d80580938c2b

Confidential


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 $IF

FAULT ID : 61102: FTM_AIS_MS

MEANING : 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


traffic.


indicating the root cause and follow the instructions for handling these alarms.

FAULT NAME : AIS on unit $U, interface $IF

FAULT ID : 61151: FTM_AIS

MEANING : Alarm indication signal is received. This signal is

generated by an intermediate PDH device in the forward

direction because it detects a problem in its receive

signal.

All other transmission alarms related to this signal are

suppressed.

Probable cause: There is a transmission problem somewhere


traffic.




FAULT NAME : Auto-Negotiation mismatch with electrical GE interfaces

7/25/2019 Alarm_3G_RU_30


DN99580892 263



Id:0900d80580938c2b

Confidential

FAULT ID : 61607: AUTO NEGO MIS MATCH

MEANING : 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

FAULT ID : 61510: NO_CERTIFICATE

MEANING : 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 $destinationIP

FAULT ID : 61606: BFD down egress

MEANING : 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 the local end.

FAULT NAME : BFD $session down, ingress, $sourceIP to $destinationIP

FAULT ID : 61605: BFD DOWN Ingress

MEANING : 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 that the BFD functionality in the peer is switched

on and that the configurations of the BFD peers match.

FAULT NAME : BFD group $bfdGrpId down

FAULT ID : 61022: BFD DOWN

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

7/25/2019 Alarm_3G_RU_30


7/25/2019 Alarm_3G_RU_30


DN99580892 265



Id:0900d80580938c2b

Confidential

FAULT NAME : CES pseudowire $W down on unit $U

FAULT ID : 61071: CES_PW_DOWN

MEANING : 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 $U

FAULT ID : 61072: CES_PW_Remote_Packet_Loss

MEANING : This alarm is raised if the packet loss condition for

packets of the given CES pseudowire persists for more than

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


connectors.

2. Check that the interface at the far-end interface is

switched on.


there are, follow the instructions for handling those alarms.

7/25/2019 Alarm_3G_RU_30


266 DN99580892


Id:0900d80580938c2b

Confidential


4. Check the configuration of the CES pseudowire.

FAULT NAME : CES pseudowire tunnel $T down on unit $U

FAULT ID : 61070: CES_PWT_DOWN

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


connectors.


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 $C

FAULT ID : 61074: CRL Update failure

MEANING : This alarm is raised if the BTS cannot update the

Certificate Revocation List (CRL) for one of the following

reasons:

- the LDAP binding fails or

- the LDAP search is emtpy (no CRL found) / the LDAP search

contains more

then one entry or

- the CRL signature validation fails or

- the CRL file exceeds the BTS storage limit or

- the BTS certificate is part of the CRL or

- DNS resolution for the CRL distribution point fails

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.

7/25/2019 Alarm_3G_RU_30


DN99580892 267



Id:0900d80580938c2b

Confidential

- Configuration of IPSec policies towards remote peers.

Check remote peers and intermediate network element

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 $IMAG

FAULT ID : 61178: FTM_IMA_CONFIG_ABORTED

MEANING : 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 : DSCP $D signalled but not configured FAULT ID : 61020: DSCP UNKNOWN

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

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 : EBER on unit $U, interface $IF

FAULT ID : 61104: FTM_EBER

MEANING : Excessive bit error rate. The measured bit error rate

exceeds the threshold value of BER-3 (10E-3).

Probable causes:

- the signal level is too low (optical connectors or cables

are dirty, electrical connectors or cables are corroded)

- the specified maximum length of the cable is exceeded - the connector is not properly connected to the unit

7/25/2019 Alarm_3G_RU_30


268 DN99580892


Id:0900d80580938c2b

Confidential


- the receiver or the far end transmitter has failed

INSTRUCTIONS: 1. Clean the cables and connectors.

2. Check that the connectors are properly connected to the

unit.

3. Check that the cable connected to the interface in

question is not damaged and is within the specifications.

4. Follow the signal in the network and check whether any

other alarms 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 $x

FAULT ID : 61411: Ethernet OAM ETH_AIS_fault

MEANING : 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

- Source MAC address of the MEP

INSTRUCTIONS: 1) Check cabling.

2) Check configuration at remote peer.

FAULT NAME : FTM booted at $date due to $RCause

FAULT ID : 61006: FTM_RESET

MEANING : The transport part of the WBTS has been reset.

INSTRUCTIONS: N/A

FAULT NAME : Far end config-abort state on unit $U, IMA Group $IMAG

FAULT ID : 61179: FTM_IMA_CONFIG_ABORTED_FE

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

7/25/2019 Alarm_3G_RU_30


DN99580892 269



Id:0900d80580938c2b

Confidential

FAULT NAME : Far end group start-up on unit $U, IMA Group $IMAG

FAULT ID : 61177: FTM_IMA_START_UP_FE

MEANING : Far end group 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 $IMAG

FAULT ID : 61181: FTM_IMA_INSUFFICIENT_LINKS_FE

MEANING : 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

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 $IF

FAULT ID : 61176: FTM_IMA_RX_UNUSABLE

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

7/25/2019 Alarm_3G_RU_30


270 DN99580892


Id:0900d80580938c2b

Confidential


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 $IF

FAULT ID : 61175: FTM_IMA_FE_TX_UNUSABLE

MEANING : 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 user name or

password

FAULT ID : 61500: FTM_SECURITY

MEANING : Five consecutive failed login attempts to the FTM have been

performed.

INSTRUCTIONS: Check your username and password.

FAULT NAME : Group timing mismatch on unit $U, IMA Group $IMAG

FAULT ID : 61183: FTM_IMA_GR_TIMING_MISMATCH

MEANING : 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

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.

7/25/2019 Alarm_3G_RU_30


DN99580892 271



Id:0900d80580938c2b

Confidential

FAULT NAME : IMA link out of delay synchronization on unit $U, interface

$IF

FAULT ID : 61171: FTM_IMA_LODS

MEANING : 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 high

INSTRUCTIONS: 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 $IF

FAULT ID : 61172: FTM_IMA_RFI

MEANING : 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 synchronisation

INSTRUCTIONS: Follow the instructions for handling the alarms raised at

the far end of the IMA link.

FAULT NAME : IP Control Protocol Failure

FAULT ID : 61250: FTM_IPCP

MEANING : The IPCP statemachine is in the Closed or Initial state and cannot reach the Opened state within 100 milliseconds.

7/25/2019 Alarm_3G_RU_30


272 DN99580892


Id:0900d80580938c2b

Confidential


INSTRUCTIONS: Check the configuration of the far end

FAULT NAME : Insufficient links on unit $U, IMA Group $IMAG

FAULT ID : 61180: FTM_IMA_INSUFFICIENT_LINKS

MEANING : 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 high

INSTRUCTIONS: 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

minutes

FAULT ID : 61040: FTM_IF_TEST

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

FAULT NAME : LOCD on unit $U, interface $IF

FAULT ID : 61057: FTM_LOCD

MEANING : 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 question

7/25/2019 Alarm_3G_RU_30


DN99580892 273



Id:0900d80580938c2b

Confidential

INSTRUCTIONS: 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 $IF

FAULT ID : 61028: FTM_LOF

MEANING : Loss of frame. It is not possible to carry traffic on the

interface referenced in the alarm text. All other

transmission alarms related to this signal are suppressed.

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

FAULT NAME : LOMF on slot $U, interface $IF

FAULT ID : 61150: FTM_LOMF

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

7/25/2019 Alarm_3G_RU_30


274 DN99580892


Id:0900d80580938c2b

Confidential


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 $IF

FAULT ID : 61105: FTM_LOP_AU

MEANING : 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 $IF

FAULT ID : 61029: FTM_LOS

MEANING : No signal is received on the interface referenced in the

alarm text. All other transmission alarms related to this

signal are suppressed.

Probable causes for 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 off


connectors.


switched on.


there are, follow the instructions for handling those

alarms.

4. To verify that the hardware of the interface unit works

7/25/2019 Alarm_3G_RU_30


DN99580892 275



Id:0900d80580938c2b

Confidential

correctly, connect a loop cable and check whether the alarm

disappears.

FAULT NAME : Licence missing <licenceCode>, <licenceName>

FAULT ID : 61400: FTM_LICENSE_MISSING

MEANING : The feature referenced in the alarm text has been

configured without installing a valid license.

Probable cause: A valid license that would allow 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 for Flexi

WCDMA BTS 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

Interfaces 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

INSTRUCTIONS: Download a valid license to the WBTS.

FAULT NAME : Link Control Protocol failure on port $P

FAULT ID : 61251: FTM_LCP

MEANING : 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 : Link OAM critical link event $E on unit $U, interface $F

FAULT ID : 61077: Link OAM critical link event alarm

MEANING : A Link OAM PDU containing a critical link event flag was received on the Ethernet interface. The alarm is raised

7/25/2019 Alarm_3G_RU_30


276 DN99580892


Id:0900d80580938c2b

Confidential


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

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.

FAULT NAME : Link OAM link lost on unit $U, interface $F

FAULT ID : 61076: Link OAM link lost alarm

MEANING : On an interface for which the Link OAM functionality was

switched on, no Link OAM PDUs were received during the

period specified in configuration parameter linkLostTime

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

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

peer

FAULT ID : 61075: Link OAM loopback alarm

MEANING : A loopback is requested for an Ethernet interface either

locally at the BTS or the Link OAM client of the BTS is set

into loopback mode by the remote Link OAM peer.

INSTRUCTIONS: None.

FAULT NAME : Loss of IMA frame on unit $U, interface $IF

FAULT ID : 61170: FTM_IMA_LIF

MEANING : 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

7/25/2019 Alarm_3G_RU_30


DN99580892 277



Id:0900d80580938c2b

Confidential

suppressed.

Probable causes:

- the configuration of the IMA group is incomplete or

faulty

- there is disturbance on the line

INSTRUCTIONS: 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 : No inserted or non-compliant SFP module on unit $U,

interface $I

FAULT ID : 61050: FTM_SFP

MEANING : 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 $cause

FAULT ID : 61085: OSPF neighbor down MEANING : 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.4

INSTRUCTIONS: 1) Check cabling

2) Check the configuration of the static routes towards the

neigbor

FAULT NAME : PLM (High Order Path) on unit $U, interface $IF

FAULT ID : 61108: FTM_PLM_HOP

MEANING : 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

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

7/25/2019 Alarm_3G_RU_30


278 DN99580892


Id:0900d80580938c2b

Confidential


FAULT NAME : Pseudowire $PW down in egress direction on unit $U

FAULT ID : 61602: FTM_PWE_DOWN_EGRESS

MEANING : 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_INGRESS

MEANING : 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 $IF

FAULT ID : 61109: FTM_RDI_HOP

MEANING : 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



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 $IF

FAULT ID : 61103: FTM_RDI_MS

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

7/25/2019 Alarm_3G_RU_30


DN99580892 279



Id:0900d80580938c2b

Confidential

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




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 $IF

FAULT ID : 61152: FTM_RDI MEANING : Remote defect indication. It is sent by the intermediate or

the far end equipment, because it detects a serious fault

in the received signal.

Probable cause: The far end has a LOS, LOF or AIS alarm on

its receiving interface.




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 $a

FAULT ID : 61073: ROUTING_MISCONFIGURATION

MEANING : A routing misconfiguration was detected. A

management-plane, control-plane, a synchronization-plane

packet, or a CES-packet was sent over a network interface

for which it 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 : STC connection to signalling peer not established on

7/25/2019 Alarm_3G_RU_30


280 DN99580892


Id:0900d80580938c2b

Confidential


interface $

FAULT ID : 61260: FTM_STC_LINK_DOWN

MEANING : 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 RNC

INSTRUCTIONS: 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 lost

FAULT ID : 61058: FTM_SYNC_LOSS MEANING : 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.


7/25/2019 Alarm_3G_RU_30


DN99580892 281



Id:0900d80580938c2b

Confidential

there are, follow the instructions on handling those

alarms.



disappears.

FAULT NAME : TWAMP session down for reason: $r

FAULT ID : 61084: TWAMP SESSION DOWN

MEANING : 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, interface $IF

FAULT ID : 61059: FTM_TIMING_SOURCE_LOS

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


there are, follow the instructions on handling those

alarms.



disappears.

7/25/2019 Alarm_3G_RU_30


282 DN99580892


Id:0900d80580938c2b

Confidential


FAULT NAME : UNEQ (High Order Path) on unit $U, interface $IF

FAULT ID : 61107: FTM_UNEQ_HOP

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

Cancelling

Do not cancel the alarm. The system cancels the alarm automatically when


7/25/2019 Alarm_3G_RU_30


DN99580892 283


7740 BEATING WCDMA BTS ALARM

Id:0900d80580938c2b

Confidential

37 7740 BEATING WCDMA BTS ALARM

Meaning

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 network

object is the object of both: the alarm in question and the beating

alarm that caused it.


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

Instructions

Correct the fault that caused the original beating alarm. You can

find the number of that alarm in Supplementary information field 1.

Cancelling



7/25/2019 Alarm_3G_RU_30


284 DN99580892


Id:0900d80580938c2b

Confidential

7750 FAILURE IN WCDMA WBTS O&M CONNEC-TION

38 7750 FAILURE IN WCDMA WBTS O&M CON-

NECTION

Meaning

This alarm indicates that a failure has occurred in WBTS O&M

connection. The problem is related to Iub connection between

controller and WBTS.

From controller point of view the actual reason for the failure

is either in transmission network between controller and WBTS, in

internal communication of controller applications or in WBTS

configuration.

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&M

functionality may be limited.

User initiated or automatic O&M tasks (e.g. SW download, HW

configuration request and WBTS restart) cannot be performed in case

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

states of the user plane links can be checked using OMS Topology

Browser.


1 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

Instructions

Error reason (field 1) indicates which part of the connection the

problem is located.

7/25/2019 Alarm_3G_RU_30


DN99580892 285



Id:0900d80580938c2b

Confidential

Error code (field 2) indicates what caused the problem if the error

reason (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

7/25/2019 Alarm_3G_RU_30


286 DN99580892


Id:0900d80580938c2b

Confidential


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.

Cancelling

Do not cancel the alarm with error reason 1. The system cancels

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

7/25/2019 Alarm_3G_RU_30


DN99580892 287



Id:0900d80580938c2b

Confidential

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.

7/25/2019 Alarm_3G_RU_30


288 DN99580892


Id:0900d80580938c2b

Confidential


39 7761 RNW O&M SCENARIO FAILURE

Meaning

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 or

operation performed by the system. User operation can be, for

example, WCEL creation with Element Manager or by plan.

Operations performed by the system are in most cases related to

recovery operations, for example common channel supervision.

In general, all failures cause the cell(s) to be blocked and hence

unavailable to traffic.

Failure in cell blocking can lead to erroneous cell state

information in the controller.

Failure in WBTS capability updating or pid updating can cause

incorrect WBTS capability data to be used in the controller and thus

problems in signalling or actual calls.

Failure in User plane configuration (AAL2 path unblocking) causes asituation where the User plane traffic cannot be transferred in

the corresponding AAL2 VCC.


1 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

7/25/2019 Alarm_3G_RU_30


DN99580892 289



Id:0900d80580938c2b

Confidential

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

7/25/2019 Alarm_3G_RU_30


290 DN99580892


Id:0900d80580938c2b

Confidential


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

Instructions

This instruction contains five main steps. The first four steps are

specific to certain failure situations. The last step is a general

operating procedure for all other failures indicated by this alarm.

It is also a default procedure to be performed if instructions given

in 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

7/25/2019 Alarm_3G_RU_30


DN99580892 291



Id:0900d80580938c2b

Confidential

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/I-HSPA ADA:

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/I-HSPA ADA 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

7/25/2019 Alarm_3G_RU_30


292 DN99580892


Id:0900d80580938c2b

Confidential


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

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

performed.

More information about the exact failure reason can be found by

examining the supplementary info field 3 (error code). 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.

In many cases there is also more information in OMU computer log. It

can be studied with MML-command ZDDE::"ZGSC";

Multi-controller RNC/I-HSPA ADA:

The detailed logs of all families can be collected from

"/srv/Log/log/" location in the product.

7/25/2019 Alarm_3G_RU_30


DN99580892 293



Id:0900d80580938c2b

Confidential

Cancelling



7/25/2019 Alarm_3G_RU_30


294 DN99580892


Id:0900d80580938c2b

Confidential


40 7762 RNW DATABASE OPERATION

FAILURE

Meaning

RNW database operation has failed. This reading or writing operation

was 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 where

cell state could not be modified from blocked to working state or

vice versa in controller or it was not possible to send configurationdata to WBTS. Failure in pid updating can cause trouble to other O&M

scenarios where that information is needed, and failure in WBTS

capability updating or CCH parameter updating can cause inconsistent

data to be used in controller and thus problems in signalling or in

actual calls.


1 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

7/25/2019 Alarm_3G_RU_30


DN99580892 295



Id:0900d80580938c2b

Confidential

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.





Instructions

IPA-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:

7/25/2019 Alarm_3G_RU_30


296 DN99580892


Id:0900d80580938c2b

Confidential


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 appears

constantly for several WBTSs and cells, contact the local Nokia

Siemens Networks representative. Also controller reset might help if

it is possible to perform it.

More information about the exact failure reason can be found

by 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/I-HSPA ADA :

Logs can be collected and studied from location "/srv/Log/log/"in the product.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 297



Id:0900d80580938c2b

Confidential

41 7771 WCDMA CELL OUT OF USE

Meaning

The alarm indicates that an unlocked WCDMA cell has been blocked forsome reason, and it cannot transmit any traffic. This alarm is set

only when a cell is moved to the blocked state by the system,

meaning that a user initiated state change does not cause this

alarm.

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 WCEL

changes back to WO or when the cell is locked by the user.


1 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:

7/25/2019 Alarm_3G_RU_30


298 DN99580892


Id:0900d80580938c2b

Confidential


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)


You can check its meaning from General Error Messages of System.

Instructions

First task: wait for 5 minutes. Typically, there is still some

recovery operation ongoing. The alarm gets cancelled if therecovery is successful.

If the automatic recovery does not correct the situation, follow

these 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

7/25/2019 Alarm_3G_RU_30


DN99580892 299



Id:0900d80580938c2b

Confidential

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/I-HSPA ADA : 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 by

examining the supplementary information field 2 (error code). You can

check its meaning with a command of the service terminal extension

MRS (see Service Terminal Essentials), or from the document General

Error 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";


Logs can be collected and studied from location "/srv/Log/log/"in

the product:

Cancelling


when the fault has been corrected. The alarm is cancelled by system

if the cell in question starts to work again or it is locked byuser.

7/25/2019 Alarm_3G_RU_30


300 DN99580892


Id:0900d80580938c2b

Confidential


42 7772 HSDPA CONFIGURATION FAILED

Meaning

This alarm indicates that there has been an error when controller hasrequested configuration or reconfiguration of HSDPA channels to BTS

via 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 the

supplementary 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:

7/25/2019 Alarm_3G_RU_30


DN99580892 301



Id:0900d80580938c2b

Confidential

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

Instructions

Check 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

7/25/2019 Alarm_3G_RU_30


302 DN99580892


Id:0900d80580938c2b

Confidential


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 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 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/I-HSPA ADA

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.


IPA-RNC :

Logs can be studied with MML-command ZDDE::"ZGSC";

Multi-Controller RNC/I-HSPA ADA : Logs can be collected and studied from location

7/25/2019 Alarm_3G_RU_30


DN99580892 303



Id:0900d80580938c2b

Confidential

"/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


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/I-HSPA ADA the detailed family logs can be collected from location in the product"/srv/Log/log/".

7/25/2019 Alarm_3G_RU_30


304 DN99580892


Id:0900d80580938c2b

Confidential


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.

Cancelling



Locking or deleting of the cell, or next succeeded configuration of HSDPA

channels cancels the alarm.

7/25/2019 Alarm_3G_RU_30


DN99580892 305


7773 INSECURE O&M CONNECTION

Id:0900d80580938c2b

Confidential

43 7773 INSECURE O&M CONNECTION

Meaning

The alarm indicates that one or more network elements have establishedan O&M connection with insecure protocol while the controller is configured

in probing security mode. In probing mode the secure connections are

preferred, i.e. the alarm may be an indication of a failure in setting up a

secure connection.

Problems in transport layer or incorrect certificates installation would

cause the network element to establish the connection with controller with

insecure protocol when the controller is configured in probing mode.


1 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

Instructions

To analyze and correct the problem, check the 1st supplementary information

field value. The 1st supplementary information field indicates the reason

why the network element is not able to establish the secure connection with

the 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 to

establish the secure O&M connection.

After the right certificates are installed at the Controller end, operator

should trigger the TLSmode as probing which will make Controller to close

the server port and open the port with right certificates.

Cancelling



7/25/2019 Alarm_3G_RU_30


306 DN99580892


Id:0900d80580938c2b

Confidential

7775 INCONSISTENCY IN WCEL CONFIGURATIONPARAMETERS

44 7775 INCONSISTENCY IN WCEL CONFIGU-

RATION PARAMETERS

Meaning

The alarm indicates that the 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.

The alarm is set when BTS has failed to accept the parameters

sent to it during cell setup or when BTS has not responded to the

parameter sending during cell setup.

The alarm is cancelled automatically after these configuration

parameters have been successfully sent.

The alarm is cell-specific and its indication to NetAct has been

prevented by default in IPA-RNC. The controller-specific alarm 3325,

INCONSISTENCY IN CONFIGURATION PARAMETERS, is related to this alarm

and one instance of it is activated when Nokia Siemens Networks

specific configuration parameter sending has failed to one or more

cells in a certain controller. This controller-specific alarm is

sent to NetAct by default.

Alarm indication preventions can be altered with MML command AFC in

IPA-RNC.


1 general error message of the system. You can check its meaning

with a command of the service terminal extension MRS or in the

General Error Messages of System

Instructions

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

7/25/2019 Alarm_3G_RU_30


DN99580892 307


7775 INCONSISTENCY IN WCEL CONFIGURATIONPARAMETERS

Id:0900d80580938c2b

Confidential

(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 supplementary info field (error code). You can check its meaning

with a command of the service terminal extension MRS (see Service

Terminal Essentials) or from the document General Error Messages of

System.

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 alsorequire repairing of BTS HW.

In many cases there is more information in the OMU computer log. In

IPA-RNC it can be studied with the MML-command ZDDE::"ZGSC";

Detailed information can be collected from location "/srv/Log/log/" in

the Multi-controller RNC/I-HSPA ADA.This contains the detailed logs for

all the families.

Cancelling


after these parameters have been sent successfully to the WBTS.

7/25/2019 Alarm_3G_RU_30


308 DN99580892


Id:0900d80580938c2b

Confidential


45 7776 HSDPA FAILURE IN WCEL

Meaning

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 not

enough capacity available in the BTS WSP cards for the HSDPA service.

This alarm is set when an HSDPA-capable BTS sends a Resource Status

Indication (RSI) message via NBAP to RNC indicating that HSDPA state

is changed to "disabled". As a consequence of this alarm, HSDPA

connections cannot be used in that particular cell.

The RSI message regarding HSDPA disabling can arrive also after the

whole 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 case

this alarm can appear together with the alarms for the same WCEL

object:



In case the overall WCEL object state is WO (working) when this alarm

appears, check the reason for the fault from the BTS WSP-related alarms.


Instructions

First check the WCEL operational state using RNW RNC Object Browser.

If the WCEL operational state is not WO (working), ignore this alarm and

analyze the problem with the WCEL taking into account the other active

alarms for the same WCEL or its parent WBTS object.

If the WCEL operational state is WO, check in the RNC the WSP-related

active alarms that are targeted to the related WBTS object.

The alarms to be checked are: 7650 BASE STATION FAULTY



The faulty unit is mentioned in supplementary information field 3 of

these alarms. Check all WSP-related alarms because any of the

WSP-related fault can be the reason for this alarm.

If a HSDPA-dedicated WSPC unit in BTS is faulty, the BTS reserves

another WSPC when it becomes free from other traffic.

For more information on BTS alarms, see WCDMA BTS Alarm

7/25/2019 Alarm_3G_RU_30


DN99580892 309



Id:0900d80580938c2b

Confidential

Descriptions (SW and release documentation).

Cancelling


when the fault is corrected.

7/25/2019 Alarm_3G_RU_30


310 DN99580892


Id:0900d80580938c2b

Confidential

7778 WCDMA BTS DEDICATED MEASUREMENTFAILURE

46 7778 WCDMA BTS DEDICATED MEASURE-

MENT FAILURE

Meaning

This alarm is set when Dedicated Measurement (for transmitted code power)

Initiation fails due to the following three cases during cell

initialization:

1) BTS problem, such as no response or nack

2) NBAP-D link is down

3) NBAP-D module has a problem (controller internal)

Controller retries Dedicated Measurement Initiation after the

corresponding NBAP-D link is re-created to be ready. If the retry

succeeds, the alarm is cancelled.

After this alarm, cells' capacity under the BTS might be affected.







2 communication control port id

Instructions

First, check if there are other alarms active for the BTS in question

and follow the instructions given for those alarms. This alarm is

cancelled if the problem is solved by correcting the other active

alarms.

If there are no obvious faults indicated by active alarms and this

alarm is not cancelled by system, follow the instructions given in the

steps below according to error code given in the first supplementary

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

7/25/2019 Alarm_3G_RU_30


DN99580892 311


7778 WCDMA BTS DEDICATED MEASUREMENTFAILURE

Id:0900d80580938c2b

Confidential

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 the

situation.

If the problem persists after these steps, contact the local Nokia

Siemens Networks representative. Attach OMU message monitorings for

troubleshooting:

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


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.

Cancelling



7/25/2019 Alarm_3G_RU_30


312 DN99580892


Id:0900d80580938c2b

Confidential


47 7779 RECOVERY ACTIONS ONGOING

Meaning

The alarm indicates that controller has started WBTS recovery actionsdue to a non-performing WCDMA cell. During recovery actions it cannot

transmit 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 actions

have been completed. After this operator can start to perform user

actions again.

After this alarm has been cancelled and BTS recovery actions have

ended, it is possible that other recovery actions are started

if cells are still in some block state. Alarm 7761 or 7762 is set

if a failure occurred during WBTS initialization after the

WBTS reset.


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

7/25/2019 Alarm_3G_RU_30


DN99580892 313



Id:0900d80580938c2b

Confidential

Instructions

This 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 indicated

in the 1st supplementary information field.

If cell still does not work after the WBTS recovery actions have ended

and no 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 (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


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

Cancelling

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

7/25/2019 Alarm_3G_RU_30


314 DN99580892


Id:0900d80580938c2b

Confidential


48 7780 HSUPA FAILURE IN WCEL

Meaning

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 not

enough capacity available on the BTS WSP cards for HSUPA service.

This alarm is set when an HSUPA-capable BTS sends a Resource Status

Indication (RSI) message via NBAP to the RNC indicating that HSUPA state

is changed to "disabled". As a consequence of this alarm, HSUPA

connections cannot be used in that particular cell.

The RSI message regarding HSUPA disabling can arrive also after the

whole 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 case

this alarm can appear together with the alarms for the same WCEL

object:



In case the overall WCEL object state is WO (working) when this alarm

appears, check the reason for the fault from the BTS WSP-related alarms.


Instructions

First check the WCEL operational state using RNW RNC Object Browser.

If the WCEL operational state is not WO (working), ignore this alarm and

analyze the problem with the WCEL taking into account the other active

alarms for the same WCEL or its parent WBTS object.

If the WCEL operational state is WO, check in the RNC the WSP-related

active alarms that are targeted to the related WBTS object.

The alarms to be checked are: 7650 BASE STATION FAULTY



The faulty unit is mentioned in supplementary information field 3

of these alarms. Check all WSP-related alarms because any of the

WSP-related faults can be the reason for this alarm.

If a HSUPA-dedicated WSPC unit in the BTS is faulty, the BTS

reserves another WSPC when it becomes free from other traffic.

For more information on BTS alarms, see WCDMA BTS Alarm

7/25/2019 Alarm_3G_RU_30


DN99580892 315



Id:0900d80580938c2b

Confidential

Descriptions (SW and release documentation).

Cancelling

Do not cancel the alarm. The system cancels the alarm

automatically when the fault is corrected.

7/25/2019 Alarm_3G_RU_30


316 DN99580892


Id:0900d80580938c2b

Confidential

7781 NETWORK ELEMENT CONFIGURATION ER-ROR

49 7781 NETWORK ELEMENT CONFIGURATION

ERROR

Meaning

The alarm indicates that the NEType indicated by the BTS and the Iub

Working Mode configured in the controller for the WBTS object do

not match. The controller sets this alarm when such a mismatch

is 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, or

no mismatch is detected after the BTS O&M link establishment.


1 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

Instructions

The WBTS deletion and recreation are required when correcting the

incorrect configuration. The WBTS recreation is needed because the

Iub Working Mode is a non-modifiable parameter that must be

given in the WBTS object creation phase.

Step 1:

7/25/2019 Alarm_3G_RU_30


DN99580892 317


7781 NETWORK ELEMENT CONFIGURATION ER-ROR

Id:0900d80580938c2b

Confidential

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.

Cancelling

Do not cancel the alarm. The system cancels the alarm automaticallywhen the WBTS is deleted, or no mismatch is detected after the

BTS O&M link establishment.

7/25/2019 Alarm_3G_RU_30


318 DN99580892


Id:0900d80580938c2b

Confidential


50 7782 HSUPA CONFIGURATION FAILED

Meaning

This alarm indicates that there has been an error when controllerrequested configuration or reconfiguration of HSUPA channels to

BTS 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 the

supplementary information fields of this alarm.

The consequence of this alarm depends on the HSUPA configuration phase

where 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

7/25/2019 Alarm_3G_RU_30


DN99580892 319



Id:0900d80580938c2b

Confidential

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

7/25/2019 Alarm_3G_RU_30


320 DN99580892


Id:0900d80580938c2b

Confidential


04 = PWSM HSPA05 reconfiguration failure

Instructions

Step 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


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

7/25/2019 Alarm_3G_RU_30


DN99580892 321



Id:0900d80580938c2b

Confidential

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/I-HSPA ADA

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.


IPA-RNC :

Logs can be studied with MML-command ZDDE::"ZGSC";


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


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

7/25/2019 Alarm_3G_RU_30


322 DN99580892


Id:0900d80580938c2b

Confidential


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/I-HSPA ADA 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.

Cancelling



Locking or deleting of the cell, or next succeeded configuration of HSDPA

channels cancels the alarm.

7/25/2019 Alarm_3G_RU_30


DN99580892 323


7783 IP BASED D-NBAP LINK FAILURE

Id:0900d80580938c2b

Confidential

51 7783 IP BASED D-NBAP LINK FAILURE

Meaning

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 is

degraded, or the traffic capability of the whole WCDMA BTS is

totally lost.

This alarm is set only if the fault is detected in IP-based D-NBAP

link(s) of the WCDMA BTS. The alarm is not set for IP-based D-NBAP links

if the C-NBAP link is unavailable at the same time.


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

Instructions

See the NBAP link operational states for the WCDMA BTS from Topology

Browser in controller OMS to see which of the configured D-NBAP links

are unavailable.

In case this alarm is set right after the WBTS is enabled in the system,

verify using Topology Browser that the IPNB object configuration

in controller is correct in relation to the network setup.

Otherwise, the problem is likely to be located either in the BTS or in IP

transmission between the BTS and the controller. See other possible

active BTS-originated alarms (7650, 7651) that can indicate the

reason for the failure.

Use BTS Site Manager to see the operation status in the BTS end for

additional troubleshooting.

Cancelling



7/25/2019 Alarm_3G_RU_30


324 DN99580892


Id:0900d80580938c2b

Confidential


52 7784 RECOVERY ACTION FAILURE

Meaning

This alarm indicates that automatic WCDMA BTS recovery action performedby controller has failed. The recovery has been attempted because some

of the WCELs under the WBTS have been detected not to be performing

properly. The observed cause for the recovery is given in alarm

supplementary information. For more information about the recovery

functionality behind this alarm, see feature descriptions for features

RAN1302 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 WCDMA

BTS may be reduced because some WCELs do not perform properly.

Recovery action is resumed by controller again after the fault

preventing the recovery action has been corrected and if the problem

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

7/25/2019 Alarm_3G_RU_30


DN99580892 325



Id:0900d80580938c2b

Confidential

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

Instructions

Check the reason for the recovery failure from the 1st supplementary

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

7/25/2019 Alarm_3G_RU_30


326 DN99580892


Id:0900d80580938c2b

Confidential


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 based

on 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 information

about the attempted recovery actions.IPA-RNC :

"ZGSC:,50B" and "ZGSC:,4FA"


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 troubleshooting

when this alarm is observed.

Detailed logs can be collected from location "/srv/Log/log/" in

the Multi-Controller RNC/I-HSPA ADA. This contains the detailed logs for

all the families.

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 327



Id:0900d80580938c2b

Confidential

53 7786 WCDMA BASE STATION OUT OF USE

Meaning

This alarm indicates that there is a WBTS-level failure that causesall the WCELs in the WO state under this specific WBTS to become

unavailable.

This alarm is set when a known fault occurs and makes all

the WCELs under a certain WBTS to become unavailable at once.

The reasons for this are the C-NBAP link break or Base Station

Resource 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 WCELs

of 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 state

under the WBTS.

This alarm is canceled when at least one WCEL under the WBTS is

recovered back to the WO state, or if the user locks all the WCELs

under the WBTS.

For more information on this functionality, see Nokia Siemens

Networks WCDMA RAN documentation concerning feature RAN1461.


1 reason why all the WCELs became unavailable at once. The possible

reasons are:

00 = C-NBAP link break

01 = BRM hand crash

Instructions

The 1st supplementary information field indicates the reason why

the whole WBTS became unavailable. The field contains thefirst observed reason for the problem. This means that during

recovery actions the whole WBTS can become unavailable, but the

reason can change. For example, it is possible that the BRM hand crash

causes the original problem, but after its recovery the C-NBAP link

can be unavailable. The original alarm is kept active, as from the

system point of view the whole WBTS is still unavailable.

To analyze and correct the problem, check the 1st supplementary

information field value.

00: C-NBAP link break

This can be caused by different underlying reasons that

7/25/2019 Alarm_3G_RU_30


328 DN99580892


Id:0900d80580938c2b

Confidential


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/I-HSPA ADA)

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/I-HSPA ADA) 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/I-HSPA ADA) 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.

As for the behavior of this alarm when the WBTS level failure

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

Cancelling



7/25/2019 Alarm_3G_RU_30


DN99580892 329


7794 ALARM STATUS REQUEST HAS TIMED OUT

Id:0900d80580938c2b

Confidential

54 7794 ALARM STATUS REQUEST HAS TIMED

OUT

Meaning

The alarm indicates that due to the lack of the upload acknowledgement

message from the BTS, the alarm upload cannot be started between the BTS

and the controller.

The alarm is set when two consecutive alarm upload requests have been

sent by the controller without an acknowledgement from the BTS.

If this alarm occurs, there can be a difference in alarm conditions

between 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 upload

attempt, alarm 7750 is set instead.


Instructions

No actions are needed in the controller. Use the BTS Site Manager to see

the operation status in the BTS end for an additional troubleshooting.

Cancelling

Do not cancel the alarm. The system cancels the alarm after the BTS has

acknowledged the alarm upload status request and when the upload can be

started.

7/25/2019 Alarm_3G_RU_30


330 DN99580892


Id:0900d80580938c2b

Confidential

7795 INCONSISTENCY IN HIGH PEAK RATE HSPACONFIG

55 7795 INCONSISTENCY IN HIGH PEAK RATE

HSPA CONFIG

Meaning

The alarm indicates that the High Peak Rate HSPA configuration

parameters (for DC HSDPA or HSUPA IC) in at least one WCEL of the BTS

might not be consistent with the parameters in the RNC.

In DC HSDPA case this alarm is also raised if the BTS loses its

capability of supporting DC HSDPA. This is also a result if user

locks one of the cells in the cell pair during maintenance

activities.

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 CONFIGURATION

PARAMETERS", is reported on NetAct when first instance of 7795 is set.

The alarm 7795 is cancelled by the system when configuration at BTS and

RNC is consistent for High Rate HSPA features (DC HSDPA and HSUPA IC)

or when the cell is deleted/locked.

Alarm indication preventions can be altered with MML command AFC.


1 possible error code values are:

* 746d = DC HSDPA NOT AVAILABLE

local Cell in the BTS is not Multi Cell Capable, whereas

the RNC has the DC HSDPA feature enabled in the cell

* 1352d = pic_state_mismatch_ec

PICState at BTS and AdminPICState set by RNC are

inconsistent

2 name of the feature for which the setup failed.

Possible values:

* DCHSDPA = Dual Cell HSDPA

* HSUPAIC = HSUPA Interference Cancellation

Instructions

The situation causing this alarm does not obstruct network operations,

and therefore no immediate actions are required. However, you can take

the 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 proceeding

7/25/2019 Alarm_3G_RU_30


DN99580892 331



Id:0900d80580938c2b

Confidential

to the steps given below. If that is the case, then the eventual

unlocking 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 RNC RNW Object Browser.

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

RNC RNW Object Browser.

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.

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 RNC RNW

Object Browser.

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 examining

the 1st supplementary information field (error code). 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.

For more information about "how to configure DCHSDPA Feature", you can

refer the "Feature Activation Manual"

7/25/2019 Alarm_3G_RU_30


332 DN99580892


Id:0900d80580938c2b

Confidential


Cancelling

Do not cancel the alarm. The system cancels the alarm after the BTS has

indicated to the RNC that it supports the high peak rate HSPA feature in

the cell in case of DC HSDPA or BTS and RNC has consistent PIC States incase of HSUPA IC. The alarm will also be cancelled when the cell is

deleted or locked.

7/25/2019 Alarm_3G_RU_30


DN99580892 333



Id:0900d80580938c2b

Confidential

56 7796 HIGH SPEED COMMON CHANNEL

PROBLEM

Meaning

This alarm is set in a cell when the creation of HS FACH common

channel fails or the capability of the WCEL mismatches with HS FACH

capability on BTS side or HS FACH common channels are unavailable due

to sync loss between BTS and RNC.


1 error code, possible values are:

- 1315d = High speed cell FACH is enabled in the controller but

disabled in the BTS.

- 1316d = Synchronization between the BTS and controller is lost for

HS common channels and HS FACH channels are unavailable

- 1914d = High Speed Cell RACH is enabled in the controller but

disabled in the BTS.

- 2080d = High speed cell FACH UE DRX capability is enabled in the

controller but UE DRX capability is disabled at BTS.

- Besides these above specific error code, there can be other error code corresponding to failures identified during High Speed FACH

common channel creation. For instance, insufficient DSP resources.

Instructions

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

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

7/25/2019 Alarm_3G_RU_30


334 DN99580892


Id:0900d80580938c2b

Confidential


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.


(enh_rach_capb_mismatch_ec).

Possible reasons:

- There is a mismatch of the E-DCH channel configuration between




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 the cell parameter WCEL - HSRACHEnabled in the controller

using the Element Manager. If this parameter value for the cell

is the same as in the BTS Site Configuration File, no actions

are needed in the controller.

If the cell parameter in the controller is not the same as

the one in the BTS Site Configuration File and the parameter

needs to be updated, use the Element Manager to take the

following actions to the cell that has failed to accept

the parameter sent:

- Lock the WCEL.

- Modify the WCEL - HSRACHEnabled parameter.

- Unlock the WCEL.


7/25/2019 Alarm_3G_RU_30


DN99580892 335



Id:0900d80580938c2b

Confidential

(no_ue_drx_bts_support).

Possible reasons:

- There is a mismatch of the HS-DSCH channel configuration between




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

2) Check the cell parameter 'WCEL - HSFACHDRXEnabled' in the

controller using the Element Manager. If this parameter value for the cell is the same as in the BTS Site Configuration File,

no actions are needed in the controller.

If the cell parameter in the controller is not the same as

the one in the BTS Site Configuration File and the parameter

needs to be updated, use the Element Manager to take the

following actions to the cell that has failed to accept

the parameter sent:

- Lock the WCEL.

- Modify the 'WCEL - HSFACHDRXEnabled' parameter. - Unlock the WCEL.

If the fault cannot be fixed by correcting the configuration, checking

other BTS alarms, or continuous recovery attempts on the cell, contact

the local Nokia Siemens Networks representative.

For information on the exact reason of the failure, see the 1st

supplementary information field. You can check its meaning with a

command of the service terminal extension MRS (see Service Terminal

Essentials, Maintenance Manual) or in the document General Error

Messages of System, Supplementary References.

For more information, you can also examine the OMU computer log

accessed with the MML command ZDDE::"ZGSC" in IPA-RNC and in

Multi-Controller RNC/I-HSPA ADA logs can be found at location in the

product "/srv/Log/log/".

Cancelling



The alarm is cancelled when either of the following occurs:

alarm_3g_ru_30

Documents