Base Station Alarms.pdf

RNC3186-1.0 Nokia WCDMA RNC, RN2.2, Product Documentation

Base Station Alarms (7000-7900)

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

1 (148)

Base Station Alarms (7000-7900)

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia's customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the document. Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright © Nokia Corporation 2006. All rights reserved.

2 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

Summary of changes

Summary of changes

Changes between document issues are cumulative. Therefore, the latest document issue contains all changes made to previous issues.
Changes made between issues 5-0 and 4-3 New alarms

7660

7661

7665

Modified alarms

7750

7761

7762

7771

Changes made between issues 4-3 and 4-2 Modified alarms

7650 7651 7652

7653 7654 7655

7761 7762 7771

Changes made between issues 4-2 and 4-1 New alarms

7778

Modified alarms

7750

7772

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

3 (148)

Base Station Alarms (7000-7900)

4 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

List of Alarms

1

List of Alarms
7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 EXTERNAL AL 1 EXTERNAL AL 2 EXTERNAL AL 3 EXTERNAL AL 4 EXTERNAL AL 5 EXTERNAL AL 6 EXTERNAL AL 7 EXTERNAL AL 8 EXTERNAL AL 9 EXTERNAL AL 10 EXTERNAL AL 11 EXTERNAL AL 12 EXTERNAL AL 13 EXTERNAL AL 14 EXTERNAL AL 15 EXTERNAL AL 16 EXTERNAL AL 17 EXTERNAL AL 18

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

5 (148)

Base Station Alarms (7000-7900)

7419 7420 7421 7422 7423 7424 7425 7650 7651 7652 7653 7654 7655 7660 7661 7665 7740 7750 7761 7762 7771 7772

EXTERNAL AL 19 EXTERNAL AL 20 EXTERNAL AL 21 EXTERNAL AL 22 EXTERNAL AL 23 EXTERNAL AL 24 EXTERNAL AL 25 BASE STATION FAULTY BASE STATION OPERATION DEGRADED BASE STATION NOTIFICATION CELL FAULTY CELL OPERATION DEGRADED CELL NOTIFICATION BASE STATION LICENCE EXPIRED BASE STATION LICENCE NOTIFICATION BASE STATION TRANSMISSION ALARM BEATING WCDMA BTS ALARM FAILURE IN WCDMA WBTS O&M CONNECTION RNW O&M SCENARIO FAILURE RNW DATABASE OPERATION FAILURE WCDMA CELL OUT OF USE PHYSICAL SHARED CHANNEL CONFIGURATION FAILED

6 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

List of Alarms

7773 7774

WCEL THRESHOLD MONITORING LIMIT EXCEEDED MEASUREMENT THRESHOLD MONITORING LIMIT EXCEEDED INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS HSDPA FAILURE IN WCEL WCDMA BTS DEDICATED MEASUREMENT FAILURE RNC RADIO NETWORK TEST ALARM

7775

7776 7778 7799
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.

TEXT CLS OUT SDL CDL LVT -----------------------------------------------------------------------------------7401 EXTERNAL AL 1 * NON 00:10 00:10 EVENT TYPE: ENVIRONMENTAL 7402 EXTERNAL AL 2 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 3 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 4 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 5 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 6 00:10 00:10 * NON

NR

7403

*

NON

7404

*

NON

7405

*

NON

7406

* -

NON

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

7 (148)

Base Station Alarms (7000-7900)

EVENT TYPE: ENVIRONMENTAL 7407 EXTERNAL AL 7 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 8 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 9 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 10 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 11 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 12 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 13 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 14 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 15 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 16 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 17 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 18 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 19 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 20 00:10 00:10 * NON

7408

*

NON

7409

*

NON

7410

*

NON

7411

*

NON

7412

*

NON

7413

*

NON

7414

*

NON

7415

*

NON

7416

*

NON

7417

*

NON

7418

*

NON

7419

*

NON

7420

* -

NON

8 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

List of Alarms

EVENT TYPE: ENVIRONMENTAL 7421 EXTERNAL AL 21 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 22 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 23 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 24 00:10 00:10 EVENT TYPE: ENVIRONMENTAL EXTERNAL AL 25 00:10 00:10 EVENT TYPE: ENVIRONMENTAL BASE STATION FAULTY 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE BASE STATION OPERATION DEGRADED 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE BASE STATION NOTIFICATION 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE CELL FAULTY 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE CELL OPERATION DEGRADED 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE CELL NOTIFICATION 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE BASE STATION LICENCE EXPIRED 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE BASE STATION LICENCE NOTIFICATION 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE BASE STATION TRANSMISSION ALARM 00:10 00:10 * NON

7422

*

NON

7423

*

NON

7424

*

NON

7425

*

NON

7650

***

3

7651

**

5

7652

*

NON

7653

***

3

7654

**

5

7655

*

NON

7660

***

0

7661

*

NON

7665

*

NON

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

9 (148)

Base Station Alarms (7000-7900)

EVENT TYPE: QUALITY OF SERVICE 7740 BEATING WCDMA BTS ALARM 00:00 00:00 EVENT TYPE: PROCESSING FAILURE IN WCDMA BTS O&M CONNECTION 00:10 00:10 EVENT TYPE: COMMUNICATIONS RNW O&M SCENARIO FAILURE 00:40 00:00 EVENT TYPE: QUALITY OF SERVICE RNW DATABASE OPERATION FAILURE 00:05 00:00 EVENT TYPE: PROCESSING WCDMA CELL OUT OF USE 02:00 00:20 EVENT TYPE: QUALITY OF SERVICE PHYSICAL SHARED CHANNEL CONFIGURATION FAILED 00:05 00:05 EVENT TYPE: QUALITY OF SERVICE WCEL THRESHOLD MONITORING LIMIT EXCEEDED 00:00 00:00 01:05:00 EVENT TYPE: QUALITY OF SERVICE MEASUREMENT THRESHOLD MONITORING LIMIT EXCEEDED 00:00 00:00 01:05:00 EVENT TYPE: QUALITY OF SERVICE INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS 00:00 00:00 EVENT TYPE: PROCESSING HSDPA FAILURE IN WCEL 00:05 00:00 EVENT TYPE: QUALITY OF SERVICE WCDMA BTS DEDICATED MEASUREMENT FAILURE 00:00 00:00 EVENT TYPE: QUALITY OF SERVICE RNC RADIO NETWORK TEST ALARM 00:10 00:10 EVENT TYPE: ENVIRONMENTAL ** 5

7750

*

NON

7761

**

5

7762

**

5

7771

**

5

7772

**

5

7773

*

NON

7774

*

NON

7775

*

NON

7776

**

5

7778

**

5

7799

*

NON

10 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7401 EXTERNAL AL 1

2

7401 EXTERNAL AL 1
Meaning

This is an external user-defined alarm. The alarm is defined by the user in a 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.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

11 (148)

Base Station Alarms (7000-7900)

12 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7402 EXTERNAL AL 2

3

7402 EXTERNAL AL 2
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

13 (148)

Base Station Alarms (7000-7900)

14 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7403 EXTERNAL AL 3

4

7403 EXTERNAL AL 3
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

15 (148)

Base Station Alarms (7000-7900)

16 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7404 EXTERNAL AL 4

5

7404 EXTERNAL AL 4
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

17 (148)

Base Station Alarms (7000-7900)

18 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7405 EXTERNAL AL 5

6

7405 EXTERNAL AL 5
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

19 (148)

Base Station Alarms (7000-7900)

20 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7406 EXTERNAL AL 6

7

7406 EXTERNAL AL 6
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

21 (148)

Base Station Alarms (7000-7900)

22 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7407 EXTERNAL AL 7

8

7407 EXTERNAL AL 7
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

23 (148)

Base Station Alarms (7000-7900)

24 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7408 EXTERNAL AL 8

9

7408 EXTERNAL AL 8
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

25 (148)

Base Station Alarms (7000-7900)

26 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7409 EXTERNAL AL 9

10

7409 EXTERNAL AL 9
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

27 (148)

Base Station Alarms (7000-7900)

28 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7410 EXTERNAL AL 10

11

7410 EXTERNAL AL 10
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

29 (148)

Base Station Alarms (7000-7900)

30 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7411 EXTERNAL AL 11

12

7411 EXTERNAL AL 11
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

31 (148)

Base Station Alarms (7000-7900)

32 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7412 EXTERNAL AL 12

13

7412 EXTERNAL AL 12
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

33 (148)

Base Station Alarms (7000-7900)

34 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7413 EXTERNAL AL 13

14

7413 EXTERNAL AL 13
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

35 (148)

Base Station Alarms (7000-7900)

36 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7414 EXTERNAL AL 14

15

7414 EXTERNAL AL 14
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

37 (148)

Base Station Alarms (7000-7900)

38 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7415 EXTERNAL AL 15

16

7415 EXTERNAL AL 15
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

39 (148)

Base Station Alarms (7000-7900)

40 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7416 EXTERNAL AL 16

17

7416 EXTERNAL AL 16
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

41 (148)

Base Station Alarms (7000-7900)

42 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7417 EXTERNAL AL 17

18

7417 EXTERNAL AL 17
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

43 (148)

Base Station Alarms (7000-7900)

44 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7418 EXTERNAL AL 18

19

7418 EXTERNAL AL 18
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

45 (148)

Base Station Alarms (7000-7900)

46 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7419 EXTERNAL AL 19

20

7419 EXTERNAL AL 19
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

47 (148)

Base Station Alarms (7000-7900)

48 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7420 EXTERNAL AL 20

21

7420 EXTERNAL AL 20
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

49 (148)

Base Station Alarms (7000-7900)

50 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7421 EXTERNAL AL 21

22

7421 EXTERNAL AL 21
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

51 (148)

Base Station Alarms (7000-7900)

52 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7422 EXTERNAL AL 22

23

7422 EXTERNAL AL 22
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

53 (148)

Base Station Alarms (7000-7900)

54 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7423 EXTERNAL AL 23

24

7423 EXTERNAL AL 23
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

55 (148)

Base Station Alarms (7000-7900)

56 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7424 EXTERNAL AL 24

25

7424 EXTERNAL AL 24
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

57 (148)

Base Station Alarms (7000-7900)

58 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7425 EXTERNAL AL 25

26

7425 EXTERNAL AL 25
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

59 (148)

Base Station Alarms (7000-7900)

60 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7650 BASE STATION FAULTY

27

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.

Supplementary information fields

1 2 3 4 5 6

rack (cabinet) number shelf number slot type of unit unit number 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 at the BTS. Make sure the environment does not cause the fault. Before a unit is replaced at the BTS, the site should be reset to recover from any temporary faults, which might have caused the misbehaviour of the unit. When an active alarm is a 'Start' alarm, a site reset is required to cancel the alarm. If the site reset or unit block/unblock does not help, replace the faulty unit (see source of the alarm and instructions fields of the corresponding alarm). Refer also to the individual alarm instructions. If that does not help, contact the local Help Desk. For more information, see Nokia WCDMA BTS Alarm Description

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

61 (148)

Base Station Alarms (7000-7900)

(SW and release document). FAULT REASON : ATM processor faulty DESCRIPTION : UltraSite, MetroSite, MetroSite50, 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 startup has failed. FlexiBTS: There is such a fault in the FSM that the SFN is not being updated in the FSP MCU. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Check the AXC settings (WAM loopback VC, for example). 2. Reset the BTS. 3. If the BTS reset does not help, change the alarming unit. FlexiBTS: 1. Reset the BTS. 2. If the BTS reset does not help, change the alarming unit.

FAULT REASON : Baseband bus configuration of <x> was rejected DESCRIPTION : The baseband bus related configuration of <x> was rejected by the HW SW, DSP or LTX. INSTRUCTIONS : Replace the faulty unit.

FAULT REASON : BB bus reception error DESCRIPTION : 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 cabinet generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Restart the faulty unit, the FSP/FSM reset recovery. 4. If that does not help, replace the faulty unit (System Module).

FAULT REASON : BTS Blocked DESCRIPTION : The BTS is blocked with the BTS Site Manager. The meaning of the fault is to avoid alarms that may rise during a BTS maintenance task. INSTRUCTIONS : To cancel the alarm, unblock the BTS. Unblocking the BTS causes a site reset.

FAULT REASON : BTS file error DESCRIPTION : UltraSite, MetroSite, MetroSite50, Triple-mode: The BTS unit properties data is invalid or missing.

62 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7650 BASE STATION FAULTY

FlexiBTS: The BTS unit properties data is invalid or missing. Or the optical interface FPGA file is invalid or missing. INSTRUCTIONS : 1. Download the SW again. 2. UltraSite, MetroSite, MetroSite50, Triple-mode: If the fault still exists after 10 minutes, replace the alarming unit. FlexiBTS: Replace the FCM.

FAULT REASON : Communication failed with application <x> DESCRIPTION : 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 is properly connected. If the unit led does not light up, the unit is faulty. Check the faulty unit. 2. Check the alarm history.

FAULT REASON : Communication failure inside WSP DESCRIPTION : An internal communication failure between the DSP processors. INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. If only one WSP in the cabinet generates this alarm, the WSP is faulty. 2. If all WSPs in a subrack generate this alarm, the WAM is faulty. 3. If all WSPs generate this alarm, the WSC/WMC is faulty. Otherwise, check for other alarms. If the "Unit autonomous reset as a recovery action" alarm has occurred for the faulty WSP, replace the faulty WSP unit. FlexiBTS: 1. If only one FSP in the cabinet generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Restart the faulty unit, the FSP/FSM reset recovery. 4. If that does not help, replace the faulty unit (System Module).

FAULT REASON : Downlink data buffer synchronization failure DESCRIPTION : The downlink data buffer has lost synchronisation. INSTRUCTIONS : 1. If only one FSP in the cabinet generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Restart the faulty unit, the FSP/FSM reset recovery. 4. If that does not help, replace the faulty unit (System Module).

FAULT REASON : DSC-bus failure DESCRIPTION : There are communication problems between the WAM and WSP. This alarm may occur if the WSP is hot removed or the WSP is crashed. INSTRUCTIONS : If the failure still exists after the site reset, replace the

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

63 (148)

Base Station Alarms (7000-7900)

WAM unit.

FAULT REASON : Fault between WAM and WSP SFN (WSP) DESCRIPTION : UltraSite, MetroSite, MetroSite 50, Triple-mode: Synchronisation between the WAM and WSP is lost. FlexiBTS: Synchronisation between the FCM and FSP is lost. INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. If only one WSP in the cabinet generates this alarm, the WSP is faulty. 2. If all WSPs in a subrack generate this alarm, the WAM is faulty. 3. If all WSPs generate this alarm, the WSC/WMC is faulty. Otherwise, check for other alarms. If the "Unit autonomous reset as a recovery action" alarm has occurred for the faulty WSP, replace the faulty WSP unit. FlexiBTS: 1. If only one FSP in the cabinet generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Restart the faulty unit, the FSP/FSM reset recovery. 4. If that does not help, replace the faulty unit (System Module).

FAULT REASON : Frame Synchronization failure DESCRIPTION : The frame clock receiver has lost its synchronisation. The FSM internal frame clock is not synchronised with the FSM 100 Hz frame clock. INSTRUCTIONS : 1. If only one FSP in the cabinet generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Restart the faulty unit, the FSP/FSM reset recovery. 4. If that does not help, replace the faulty unit (System Module).

FAULT REASON : FSP Frame synchronisation failed DESCRIPTION : One of the following Frame synchronisation signals coming from the FCM is missing: the Frame synchronisation burst, SFN or SFCLK. INSTRUCTIONS : 1. Reset the site. 2. If that does not help, replace the FCM unit.

FAULT REASON : No connection to unit DESCRIPTION : The connection to a unit that belongs to the BTS configuration has been lost. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Check that the unit is properly connected. If the unit led does not light up, the unit is faulty. The fault may also be in the WPS unit or backplane.

64 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7650 BASE STATION FAULTY

2. Check the faulty unit. 3. Check the alarm history. Cancel alarms: Removing and inserting the WIC, WSM or primary WAM causes a site reset. If both WSCs are removed, inserting the first removed WSC back into the cabinet causes a site reset. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First try to reset the site by the software. If that does not help, replace the faulty unit. FlexiBTS: 1. Check that the unit is properly connected. If the unit led does not light up, the unit is faulty. Check the faulty unit. 2. Check the alarm history.

FAULT REASON : Not able to synchronize baseband bus with <x> DESCRIPTION : The baseband bus synchronisation towards <x> failed. INSTRUCTIONS : Check the faulty unit.

FAULT REASON : Optical interface FPGA sw crc check failed DESCRIPTION : The CRC check has failed in three consecutive optical interface FPGA SW downloading attempts. INSTRUCTIONS : Replace the faulty module.

FAULT REASON : Optical Interface Frame clock faulty DESCRIPTION : The Cleaner Clock lock VCXO of the PLL does not get the adjusting voltage. The OIC cannot attach the clock signal coming from the CASA2. Possible reasons: -30.72MHz reference clock receiving signal interrupted -Cleaner lock or parallel 153.6MHz VCXO has been broken -Cleaner lock initialization has failed from the FPGA (not likely). INSTRUCTIONS : 1. Block/unblock the FSM. 2. Replace the FSM.

FAULT REASON : Oven oscillator clock missing DESCRIPTION : The output signal of the OXCO is missing and the FCM cannot deliver the 30.72 MHz System Clock required by other units. INSTRUCTIONS : 1. Block/unblock the FSM. 2. Replace the FSM.

FAULT REASON : R-bus error DESCRIPTION : 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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

65 (148)

Base Station Alarms (7000-7900)

FSP and FCM. INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode: 1. If the WSM/WMC also generates an alarm from a WTR unit, check the WTR and WSM cable. 2. If there are no active WSM/WMC alarms, the reason for the alarm is a faulty WSM/WMC or WSP. 3. Run a WCDMA BTS loop test to locate the faulty unit. 4. If the WSP is faulty, block/unblock it. 5. Replace the faulty unit. FlexiBTS: 1. Check the cabling between the System Module and RF Module. 2. Check the active RF Module alarms and act accordingly. 3. Replace the faulty unit (System Module).

FAULT REASON : SFN Signal error DESCRIPTION : The system frame number receiving fault, an illegal SFN value in uplink. INSTRUCTIONS : 1. If only one FSP in the cabinet generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Restart the faulty unit, the FSP/FSM reset recovery. 4. If that does not help, replace the faulty unit (System Module).

FAULT REASON : SW does not support commissioning DESCRIPTION : The software does not support the loaded to the BTS. INSTRUCTIONS : Check and correct the contents of the correct commissioning file to OR Update the BTS software.

file new commissioning file the commissioning file. Load the BTS.

FAULT REASON : Synchronization failure DESCRIPTION : The frame burst phase has moved compared to the internal counter. The FSM has already found the frame synchronisation but the FSM frame clock does not match to the FSM internal frame clock. INSTRUCTIONS : 1. If only one FSP in the cabinet generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Restart the faulty unit, the FSP/FSM reset recovery. 4. If that does not help, replace the faulty unit (System Module).

FAULT REASON : Synchronization failure in Optical Interface <opt link/RP3 link> DESCRIPTION : The RP3 channel has achieved the frame synchronisation state

66 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7650 BASE STATION FAULTY

and then lost it. 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 changes, replace the RF Module behind that link.

FAULT REASON : Tbus receiver parity fault DESCRIPTION : Data or synchronisation failure in the System Module, two antenna carriers are affected. INSTRUCTIONS : 1. If only one FSP in the cabinet generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Restart the faulty unit, the FSP/FSM reset recovery. 4. If that does not help, replace the faulty unit (System Module).

FAULT REASON : Unit initialization failure DESCRIPTION : A unit or an IP address initialisation has failed. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Block/unblock the faulty unit. If that does not help, replace the faulty unit. 2. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. 3. If the WAM is the alarm 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 faulty unit. FlexiBTS: 1. Block/unblock the faulty unit. If that does not help, replace the faulty unit. 2. If the FCM is the alarm source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the faulty unit.

FAULT REASON : Unit not supported by current BTS SW version DESCRIPTION : 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 REASON : Unit SW download failed DESCRIPTION : The software update to the unit or subunit has failed. INSTRUCTIONS : 1. Reset the BTS. 2. If Step 1 does not help, replace the faulty module.

FAULT REASON : Unknown HW resource

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

67 (148)

Base Station Alarms (7000-7900)

DESCRIPTION

: A unit cannot be identified by its product code or by its physical device address (object ID). INSTRUCTIONS : Replace the unit.

FAULT REASON : Unknown product code DESCRIPTION : A unit cannot be identified by its product code but is known by its physical device address (object_ID). INSTRUCTIONS : Replace the faulty unit.

FAULT REASON : Uplink data buffer synchronization failure DESCRIPTION : The uplink data buffer loses the synchronisation. INSTRUCTIONS : 1. If only one FSP in the cabinet generates this alarm, the FSP is faulty. 2. If all FSPs generate this alarm, the FSM is faulty. 3. Restart the faulty unit, the FSP/FSM reset recovery. 4. If that does not help, replace the faulty unit (System Module).

Cancelling

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

68 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7651 BASE STATION OPERATION DEGRADED

28

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.

Supplementary information fields

1 2 3 4 5 6

rack (cabinet) number shelf number slot type of unit unit number subunit number

For more information, see instructions on Alarm Structure.

Instructions

Cancelling

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

69 (148)

Base Station Alarms (7000-7900)

70 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7652 BASE STATION NOTIFICATION

29

7652 BASE STATION NOTIFICATION
Meaning

A minor fault (or faults) has occurred in the base station. Check the reason for the fault from the supplementary text field of the alarm.

Supplementary information fields

1 2 3 4 5 6

rack (cabinet) number shelf number slot type of unit unit number 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 at the BTS. Make sure the environment does not cause the fault. Before a unit is replaced at the BTS, the site should be reset to recover from any temporary faults, which might have caused the misbehaviour of the unit. When an active alarm is a 'Start' alarm, a site reset is required to cancel the alarm. If the site reset or unit block/unblock does not help, replace the faulty unit (see source of the alarm and instructions fields of the corresponding alarm). Refer also to the individual alarm instructions. If that does not help, contact the local Help Desk. For more information, see Nokia WCDMA BTS Alarm Descriptions.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

71 (148)

Base Station Alarms (7000-7900)

(SW and release document) FAULT REASON : # autonomous reset as recovery action DESCRIPTION : The BTS tries to correct a fault situation by performing a recovery unit, the site or the BTS reset. INSTRUCTIONS : Check the other active alarms.

FAULT REASON : BTS time not corrected DESCRIPTION : The SNTP time cannot be fetched from the transport system (FT/AXC) within the time limit. INSTRUCTIONS : Check the FT/AXC and RNC transmission, and the NTP settings.

FAULT REASON : Communication failed with application <x> DESCRIPTION : 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 is properly connected. If the unit led does not light up, the unit is faulty. Check the faulty unit. 2. Check the alarm history.

FAULT REASON : Communication Failure with RNC DESCRIPTION : The BTS does not receive a response from the RNC (a block request). INSTRUCTIONS : Check the signalling link settings and the RNC connections.

FAULT REASON : Difference between BTS master clock and reference frequency DESCRIPTION : 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 synchronisation (which in turn is caused by an equipment fault or a setting error). Note that if the network synchronisation malfunction lasts a long time, the alarm is cancelled when the BTS frequency reaches the faulty Iub synchronisation. The alarm can also be activated if the faulty Iub synchronisation is corrected and there is again the difference of 0.2 ppm or more. The alarm is cancelled whenever the difference becomes smaller than 0.2 ppm. 2. The Iub reference frequency fluctuates continuously due to a great deal of jitter/wander in the transmission network. The alarm is continuously activated/cancelled (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 synchronisation information via the 2.048 MHz synchronisation

72 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7652 BASE STATION NOTIFICATION

input (external clock source), the alarm situation may be caused by a fault of that signal. In that case, the alarm behaviour notifications listed with the Iub signal (see above) are also valid in this case. 4. There is an equipment fault in the BTS. The equipment fault is, however, not the most common reason. Normally the reason can be found in the Iub/reference signal behaviour (see the descriptions above). Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WSC oven oscillator fault' becomes active, it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel. INSTRUCTIONS : Because there are several possibilities for the alarm activation, a BTS Clock Frequency History feature has been developed. The stored history data can be accessed via the BTS Site Manager. The history data can be used 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 the BTS Site Manager). Depending on the possible reason, follow the instructions below: 1. In case of 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 (check the correct Iub accuracy by measuring it). No actions on the BTS are necessarily needed. 2. If the basic accuracy of the Iub signal is in order but there is too much instability, that is, the jitter/wander is outside the acceptable limits, the synchronisation of the transmission network must be corrected. 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 BTS equipment fault, the location may be: Transport part - First check the alarms of the AXC node with the AXC Manager, or FTM and act accordingly. - If there are no alarms, check the AXC/FTM synchronisation settings. FCM unit - If both the Iub reference signal accuracy and the FTM are in order but the WFCM unit is still alarming, run the fast tuning with the 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 FCM unit. Note that if the reason is in the transmission network synchronisation, replacing the faulty unit does not correct

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

73 (148)

Base Station Alarms (7000-7900)

the situation. Furthermore, the alarm activity (frequent alarms/cancels) points to instability in the transmission network, not to a fault in the unit. 4. 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, 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 the fast tuning should only be used in case the Iub reference signal is known as a good one. Otherwise the BTS frequency may be tuned into a totally incorrect value, causing serious problems in the network performance. Background information: The principle is that in the mobile network, the 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 the synchronisation of the leased line service provider is also accurate/stabile 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 REASON : Fan module faulty DESCRIPTION : Ultrasite, Triplemode, Metrosite, MetroSite50: All the fans or more than one fan in the same fan group (WFA, WTR, WPA/WMP, WHX) are rotating slower than requested, are not rotating at all, or the RPM info is not available for the fans. The reason for this fault can be too low a supply voltage or a broken fan control board. The WFA, WFD or WHX fan control module also controls the fans in the RF section (same sector). A failure in the RF section fans is reported from that WFA, WFD or WHX and the LED of the unit is stable red although it is working correctly. FlexiBTS: All the fans or more than one fan in the same fan group are rotating slower than requested. INSTRUCTIONS : Ultrasite, Triple-mode, Metrosite, MetroSite50: 1. Check the Fan ID from the Alarm text and locate the problematic fan. See the Fan mapping figures in the Alarm Description document. 2. Check the fan and cabling. 3. If that does not help, replace the WFA, WFD or MFU module or the fan controlled by the WFA, WFD or MFU.

74 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7652 BASE STATION NOTIFICATION

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 ID from the Alarm text and locate the problematic fan. See the Fan mapping figures in the Alarm Description document. 2. Check the fan and cabling. 3. Replace the faulty module or the fan controlled by the FSM. Fan control: 'FAN UNIT' refers to a group of fans including the fan control unit. A 'fan' is a single blower.

FAULT REASON : Fan module operation degraded DESCRIPTION : A fan does not rotate or rotates slower than at the requested speed, or the RPM info is not available for the fan. INSTRUCTIONS : 1. Check the fan ID from the alarm text and locate the problematic fan. See the Fan mapping figures in the Alarm Description document. 2. Check the fan and cabling. 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.

FAULT REASON : File corrupted in SW download DESCRIPTION : The SW being downloaded is corrupted or incorrectly formed. INSTRUCTIONS : 1. Retry the SW update. 2. Fetch BTS log files and check the download status from the BTS SWDLreport.

FAULT REASON : No connection to unit DESCRIPTION : The connection to a unit that belongs to the BTS configuration has been lost. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Check that the unit is properly connected. If the unit led does not light up, the unit is faulty. The fault may also be in the WPS unit or backplane. 2. Check the faulty unit. 3. Check the alarm history. Cancel alarms: Removing and inserting the WIC, WSM or primary WAM causes a site reset. If both WSCs are removed, inserting the first removed WSC back into the cabinet causes a site reset. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First try to reset the site by the software. If that does not help, replace the faulty unit.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

75 (148)

Base Station Alarms (7000-7900)

FlexiBTS: 1. Check that the unit is properly connected. If the unit led does not light up, the unit is faulty. Check the faulty unit. 2. Check the alarm history.

FAULT REASON : OIC MCU Buffer Full DESCRIPTION : The control message traffic is malfunctioning between the modules. INSTRUCTIONS : Check the RF Module alarms.

FAULT REASON : Timestamp mismatch in summing DESCRIPTION : The timestamp mismatch in summing. Configuration error (2 different FSP functioning) - after acknowledgement the fault will return again. Data corruption on the bus - it appears once when the unsynchronised data is sent by the BB. INSTRUCTIONS : Check the BB bus configuration.

FAULT REASON : Unit not supported by current BTS SW version DESCRIPTION : 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 REASON : Unit temperature is high DESCRIPTION : The temperature of a unit exceeds the threshold value. INSTRUCTIONS : Check the active fan alarms, the ambient temperature alarms and the airflow of the BTS.

Cancelling

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

76 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7653 CELL FAULTY

30

7653 CELL FAULTY
Meaning

A critical fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the alarm. Check the reason for the fault from the supplementary text field of the alarm.

Supplementary information fields

1 2 3 4 5 6

rack (cabinet) number shelf number slot type of unit unit number 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 at the BTS. Make sure the environment does not cause the fault. Before a unit is replaced at the BTS, the site should be reset to recover from any temporary faults, which might have caused the misbehaviour of the unit. When an active alarm is a 'Start' alarm, a site reset is required to cancel the alarm. If the site reset or unit block/unblock does not help, replace the faulty unit (see source of the alarm and instructions fields of the corresponding alarm). Refer also to the individual alarm instructions. If that does not help, contact the local Help Desk. For more information, see Nokia WCDMA BTS Alarm Descriptions. (SW and release document)

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

77 (148)

Base Station Alarms (7000-7900)

FAULT REASON : Antenna Line failure, <line> DESCRIPTION : The Filter has detected overcurrent on the antenna line. The antenna line may be damaged (short circuit) or some antenna line device is causing overload. The antenna connector information at the end of the alarm text specifies the defective antenna line. INSTRUCTIONS : Check the antenna line and antenna line devices. Fix the parts causing overload and/or replace the faulty parts and/or devices.

FAULT REASON : Baseband bus configuration of <x> was rejected DESCRIPTION : The baseband bus related configuration of <x> was rejected by the HW SW, DSP or LTX. INSTRUCTIONS : Replace the faulty unit.

FAULT REASON : BB bus reception error (MUKSU) DESCRIPTION : The master frame in the received 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. Check the PI delays (BPF file). 2. Check the cables between the System Module and RF Module. 3. Replace the faulty unit (System Module).

FAULT REASON : BTS config error (Not enough HW for LCR) DESCRIPTION : UltraSite, MetroSite, MetroSite50 and Triplemode: 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 module, and it cannot serve all cells module. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50 and Replace the single carrier WTR with a

with a single PA RF commissioned to the RF Triplemode: dual carrier WTR.

FlexiBTS: Replace the single PA RF module with a dual PA RF module.

FAULT REASON : BTS file error DESCRIPTION : UltraSite, MetroSite, MetroSite50, Triple-mode: The BTS unit properties data is invalid or missing. FlexiBTS: The BTS unit properties data is invalid or missing. Or the optical interface FPGA file is invalid or missing. INSTRUCTIONS : 1. Download the SW again. 2. UltraSite, MetroSite, MetroSite50, Triple-mode: If the fault still exists after 10 minutes, replace the alarming unit. FlexiBTS: Replace the FCM.

78 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7653 CELL FAULTY

FAULT REASON : Cell blocked DESCRIPTION : The user has blocked the cell with the BTS Site Manager. INSTRUCTIONS : To cancel the alarm, unblock the cell.

FAULT REASON : Cell block rejected by RNC DESCRIPTION : The cell has been disabled due to BTS internal reasons, for example if the RNC has rejected the normal cell blocking during the Intelligent Shutdown. INSTRUCTIONS : 1. Check the other active alarms. 2. Check the mains power supply.

FAULT REASON : Cell power monitoring DESCRIPTION : The WPA/Radio output power has dropped. There is a fault in the downlink transmission path. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Block/unblock the WPA. Unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure or sticking in the unit SW. 2. Check the RF TX cabling. 3. Check the WTR. 4. Replace the faulty unit. FlexiBTS: 1. Block/unblock the RF module. Unit needs to be blocked/unblocked to get it initialised/configured again if there was some internal failure or sticking in unit SW. 2. Check the RF module. 3. Replace the faulty unit.

FAULT REASON : Communication failed with application <x> DESCRIPTION : 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 is properly connected. If the unit led does not light up, the unit is faulty. Check the faulty unit. 2. Check the alarm history.

FAULT REASON : Fatal alarm DESCRIPTION : ARIO has detected a Fatal level alarm. Some ARIO alarms can be cancelled without reset, but most ARIO alarms require a WOU block/unblock to cancel. INSTRUCTIONS : Check the WOU or WRUs. Use the ARIO Local Management Tool and Nokia Advanced Indoor Radio user documentation to diagnose the error cause.

FAULT REASON : Filter unit operation failed DESCRIPTION : A filter has not been able to tune on an appropriate sub-band

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

79 (148)

Base Station Alarms (7000-7900)

(tuning failure) properly, or another major failure detected by the filter (unit faulty). INSTRUCTIONS : Replace the filter unit.

FAULT REASON : Frame Clock Missing DESCRIPTION : 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 faulty RF Module.

FAULT REASON : Incoherency in cell configuration DESCRIPTION : Both sector types (A and B) are configured to the same RF Module in the two-carrier case. INSTRUCTIONS : Recommissioning is needed. LCRs must be configured in a way that only one sector type is taken in use in one RF Module.

FAULT REASON : Incoherency with RF Modules DESCRIPTION : A Radio Module with an incompatible frequency type has been detected. All Radio Modules must have the same frequency variant. INSTRUCTIONS : Replace the incompatible Radio Module.

FAULT REASON : Incompatible SW version detected DESCRIPTION : A new unit with an incompatible SW has probably been inserted in the BTS. INSTRUCTIONS : Update the 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 the NetAct.

FAULT REASON : Low Noise Amplifier failure DESCRIPTION : The Filter has detected malfunction in the LNA unit. INSTRUCTIONS : Replace the FR module.

FAULT REASON : Module Clock Faulty DESCRIPTION : The RF Module lost lock to the incoming clock. INSTRUCTIONS : 1. Check the cables between the System Module and RF Module, and block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : No connection to unit DESCRIPTION : The connection to a unit that belongs to the BTS configuration has been lost. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Check that the unit is properly connected. If the unit led does not light up, the unit is faulty. The fault may also be in the WPS unit or backplane.

80 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7653 CELL FAULTY

2. Check the faulty unit. 3. Check the alarm history. Cancel alarms: Removing and inserting the WIC, WSM or primary WAM causes a site reset. If both WSCs are removed, inserting the first removed WSC back into the cabinet causes a site reset. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First try to reset the site by the software. If that does not help, replace the faulty unit. FlexiBTS: 1. Check that the unit is properly connected. If the unit led does not light up, the unit is faulty. Check the faulty unit. 2. Check the alarm history.

FAULT REASON : Not able to synchronize baseband bus with <x> DESCRIPTION : The baseband bus synchronisation towards <x> failed. INSTRUCTIONS : Check the faulty unit.

FAULT REASON : Optical Interface faulty DESCRIPTION : The Small Form Factor Pluggable (SFP) malfunction 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 connected properly. 2. Replace the SFP module.

FAULT REASON : Post test failed DESCRIPTION : An RF Module power-on-self-test failed at start-up. INSTRUCTIONS : Replace the faulty RF Module.

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

81 (148)

Base Station Alarms (7000-7900)

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 unit (System Module).

FAULT REASON : Receiving failure in Optical Interface DESCRIPTION : The incoming optical signal to the Small Form Factor Pluggable (SFP) is missing or too weak. Or the fibre cable has been detached. INSTRUCTIONS : 1. Check the status of the module behind the faulty link (Power on, et cetera). 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 faulty SFP. 3. Clean the connectors, test the fibre cable, replace if faulty. 4. Replace the module behind the faulty link.

FAULT REASON : RF BB Bus Configuration Error DESCRIPTION : The RF Module baseband bus is configured incorrectly. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : RF BB Bus Synchronisation Error DESCRIPTION : The Baseband bus between the System Module and RF Module is out of synchronisation. 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 faulty RF Module.

FAULT REASON : RF Module configuring failed DESCRIPTION : The RF Module configuration failed because of a HW failure or an SW fault. INSTRUCTIONS : Replace the faulty RF Module.

FAULT REASON : RF Module critical file not found DESCRIPTION : A critical configuration file is missing from the RF Module. INSTRUCTIONS : Replace the faulty RF Module.

FAULT REASON : RF Module Filter input power missing DESCRIPTION : The RF Module filter has measured too low TX power. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : RF Module out of order DESCRIPTION : The RF Module is out of order because of an SW fault. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

82 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7653 CELL FAULTY

FAULT REASON : RF Module Overheat DESCRIPTION : The RF Module temperature is too high. INSTRUCTIONS : 1. Check the fans and the ambient temperature. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : RF Module Power output faulty DESCRIPTION : The Power Supply has detected overvoltage, undervoltage or over current situation in a module. INSTRUCTIONS : 1. Block/unblock the RF module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : RX out of order DESCRIPTION : RF Module RX RF synthesizer is not locked. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : Synchronization failure in Optical Interface <opt link/RP3 link> DESCRIPTION : The RP3 channel has achieved the frame synchronisation state and then lost it. 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 changes, replace the RF Module behind that link.

FAULT REASON : Telecom configuration failure DESCRIPTION : A unit RNW configuration failure. A telecom RNW reconfiguration failure. INSTRUCTIONS : 1. Check the other active alarms. 2. Block/unblock the faulty unit.

FAULT REASON : TX out of order DESCRIPTION : The RF Module TX path is not usable. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : TX output power measurement fault DESCRIPTION : UltraSite, MetroSite, MetroSite50, Triple-mode: The WTR or WPA/WMP/WOU output power measurement has failed. FlexiBTS: The RF Module output power measurement has failed. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Reset the alarming unit with block/unblock function. Unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure or sticking in unit SW. 2. Check the units and the RF cabling between the WPA/WMP/WOU and WTR units.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

83 (148)

Base Station Alarms (7000-7900)

3. Replace the faulty unit. FlexiBTS: 1. Reset the alarming RF Module with block/unblock function. Module needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure or sticking in unit SW. 2. Check the cables between the System Module and RF Module. 3. If that does not help, replace the faulty RF Module.

FAULT REASON : Unit blocked DESCRIPTION : A unit is blocked with the BTS Site Manager. The purpose of the fault is to avoid alarms that may rise during the unit maintenance task. INSTRUCTIONS : To cancel the alarm, unblock the unit.

FAULT REASON : Unit initialization failure DESCRIPTION : A unit or an IP address initialisation has failed. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Block/unblock the faulty unit. If that does not help, replace the faulty unit. 2. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. 3. If the WAM is the alarm 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 faulty unit. FlexiBTS: 1. Block/unblock the faulty unit. If that does not help, replace the faulty unit. 2. If the FCM is the alarm source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the faulty unit.

FAULT REASON : Unit not supported by current BTS SW version DESCRIPTION : 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 REASON : Unknown HW resource DESCRIPTION : A unit cannot be identified by its product code or by its physical device address (object ID). INSTRUCTIONS : Replace the unit.

84 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7653 CELL FAULTY

FAULT REASON : Unknown product code DESCRIPTION : A unit cannot be identified by its product code but is known by its physical device address (object_ID). INSTRUCTIONS : Replace the faulty unit.

FAULT REASON : VSWR major alarm, <line> DESCRIPTION : The Filter has detected the VSWR exceeding the defined level. The antenna line is mismatched or damaged. The antenna connector information at the end of the alarm text specifies the defective antenna line. INSTRUCTIONS : 1. Check the antenna cables, connectors, antenna and possible antenna line devices. 2. Check the antenna line (TX-cable-antenna) impedance matching.

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

85 (148)

Base Station Alarms (7000-7900)

86 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7654 CELL OPERATION DEGRADED

31

7654 CELL OPERATION DEGRADED
Meaning

A major fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the alarm. Check the reason for the fault from the supplementary text field of the alarm.

Supplementary information fields

1 2 3 4 5 6

rack (cabinet) number shelf number slot type of unit unit number 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 at the BTS. Make sure the environment does not cause the fault. Before a unit is replaced at the BTS, the site should be reset to recover from any temporary faults, which might have caused the misbehaviour of the unit. When an active alarm is a 'Start' alarm, a site reset is required to cancel the alarm. If the site reset or unit block/unblock does not help, replace the faulty unit (see source of the alarm and instructions fields of the corresponding alarm). Refer also to the individual alarm instructions. If that does not help, contact the local Help Desk. For more information, see Nokia WCDMA BTS Alarm Descriptions. (SW and release document)

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

87 (148)

Base Station Alarms (7000-7900)

FAULT REASON : Antenna line device configuration failure DESCRIPTION : An antenna line device is not properly configured. INSTRUCTIONS : 1. Update proper SW to the device. 2. If that does cancel the alarm or the alarm continually reappears, replace the antenna line device.

FAULT REASON : BTS config error (incorrect carrier candidates) DESCRIPTION : Carrier candidates are commissioned for each cell (not WTR/LTX specific). INSTRUCTIONS : Recommission (Reconfiguration commissioning) the BTS with the correct carrier candidate values.

FAULT REASON : BTS file error DESCRIPTION : UltraSite, MetroSite, MetroSite50, Triple-mode: The BTS unit properties data is invalid or missing. FlexiBTS: The BTS unit properties data is invalid or missing. Or the optical interface FPGA file is invalid or missing. INSTRUCTIONS : 1. Download the SW again. 2. UltraSite, MetroSite, MetroSite50, Triple-mode: If the fault still exists after 10 minutes, replace the alarming unit. FlexiBTS: Replace the FCM.

FAULT REASON : Communication failed with application <x> DESCRIPTION : 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 is properly connected. If the unit led does not light up, the unit is faulty. Check the faulty unit. 2. Check the alarm history.

FAULT REASON : Configuration file corrupted DESCRIPTION : The RF Module SW detected conflicting or corrupted configuration data. INSTRUCTIONS : 1. Block/unblock the RF Module 2. If that does not help, replace the faulty RF Module.

FAULT REASON : Cooling fan out of order DESCRIPTION : The RF Module cooling fan is not rotating at the specified speed. INSTRUCTIONS : 1. Check the fan. 2. If that does not help, block/unblock the RF Module. 3. If that does not help, replace the faulty fan (Fan1 or Fan2).

FAULT REASON : Filter unit operation failed DESCRIPTION : A filter has not been able to tune on an appropriate sub-band (tuning failure) properly, or another major failure detected

88 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7654 CELL OPERATION DEGRADED

by the filter (unit faulty). INSTRUCTIONS : Replace the filter unit.

FAULT REASON : Flash operation failure DESCRIPTION : The flash memory operation failure. If this alarm appears continuously, the flash chip may be broken. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Check the other active alarms. If the ROM disk is corrupted, change the alarming unit. 2. Block/unblock the faulty unit. There are no recovery actions and due to that the block/unblock can be tried once. If that does not help, replace the faulty unit. FlexiBTS: 1. Check the other active alarms. If the ROM disk is corrupted, change the alarming module. 2. Block/unblock the faulty module. There are no recovery actions and due to that the block/unblock can be tried once. If that does not help, replace the faulty module.

FAULT REASON : Frame clock deviation fault DESCRIPTION : Synchronisation 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 may have drifted. INSTRUCTIONS : 1. Check the cables between the System Module and RF Module. 2. Replace the faulty unit (System Module).

FAULT REASON : Frame Clock Missing DESCRIPTION : 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 faulty RF Module.

FAULT REASON : Incompatible SW version detected DESCRIPTION : A new unit with an incompatible SW has probably been inserted in the BTS. INSTRUCTIONS : Update the 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 the NetAct.

FAULT REASON : Low Noise Amplifier failure DESCRIPTION : The Filter has detected malfunction in the LNA unit. INSTRUCTIONS : Replace the FR module.

FAULT REASON : Major alarm

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

89 (148)

Base Station Alarms (7000-7900)

DESCRIPTION

: ARIO has detected a Major level alarm. Some ARIO alarms can be cancelled without reset, but most ARIO alarms require a WOU block/unblock to cancel. INSTRUCTIONS : Check the WOU or WRUs. Use the ARIO Local Management Tool and Nokia Advanced Indoor Radio user documentation to diagnose the error cause.

FAULT REASON : Mast Head Amplifier fault, <line> DESCRIPTION : The Mast Head Amplifier does not work properly. The received RF signal level is decreased. If both stages of the LNA on the uplink path fails, the MHA swithes the LNA on the by-pass mode. On the by-pass mode, the MHA has no gain but some loss. If only either stage of the LNA fails, the MHA still has about a half of its normal gain. In the case of an integrated MHA (WMHC), the fault may cover both main and diversity branches or just either. INSTRUCTIONS : 1. Check the antenna cables and connectors towards the MHA. Fix and/or replace the broken parts. 2. Restart the MHA by swithing the antenna line power off and on. This is done by blocking and unblocking the Flexi Radio (FR) Module. NOTE! This operation affects to all antenna lines and cells in use within the FR Module, not just the faulty one! If the alarm re-appears, replace the faulty unit.

FAULT REASON : Minor alarm DESCRIPTION : ARIO has detected a Minor level alarm. Some ARIO alarms can be cancelled without reset, but most ARIO alarms require a WOU block/unblock to cancel. INSTRUCTIONS : Check the WOU or WRUs. Use the ARIO Local Management Tool and Nokia Advanced Indoor Radio user documentation to diagnose the error cause.

FAULT REASON : No connection to unit DESCRIPTION : The connection to a unit that belongs to the BTS configuration has been lost. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Check that the unit is properly connected. If the unit led does not light up, the unit is faulty. The fault may also be in the WPS unit or backplane. 2. Check the faulty unit. 3. Check the alarm history. Cancel alarms: Removing and inserting the WIC, WSM or primary WAM causes a site reset. If both WSCs are removed, inserting the first removed WSC back into the cabinet causes a site reset. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First try to reset the site by the software. If that does not help, replace the faulty unit. FlexiBTS:

90 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7654 CELL OPERATION DEGRADED

1. Check that the unit is properly connected. If the unit led does not light up, the unit is faulty. Check the faulty unit. 2. Check the alarm history.

FAULT REASON : No feedback signal DESCRIPTION : Feedback signal to predistortion is too weak or missing. The TX performance is degraded. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

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

FAULT REASON : RET antenna control failure DESCRIPTION : The antenna tilting is not possible or may not be done properly. INSTRUCTIONS : 1. Recalibrate the RET antenna. 2. If that does not cancel the alarm or the alarm continually reappears, replace the RET unit.

FAULT REASON : RF BB Bus Configuration Error DESCRIPTION : The RF Module baseband bus is configured incorrectly. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : RF BB Bus Connection Transmission Error DESCRIPTION : There is an error in the baseband or optical bus. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

91 (148)

Base Station Alarms (7000-7900)

FAULT REASON : RF BB Bus Synchronisation Error DESCRIPTION : The Baseband bus between the System Module and RF Module is out of synchronisation. 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 faulty RF Module.

FAULT REASON : RF BB Energy too high DESCRIPTION : TX feedback signal is too high. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : RF Module file not found DESCRIPTION : 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 faulty RF Module.

FAULT REASON : RF Module Filter input power missing DESCRIPTION : The RF Module filter has measured too low TX power. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : RF Module Gain adjusting failure DESCRIPTION : TX output power adjustment failed. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : RF Module Power output faulty DESCRIPTION : The Power Supply has detected overvoltage, undervoltage or over current situation in a module. INSTRUCTIONS : 1. Block/unblock the RF module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : RX out of order DESCRIPTION : RF Module RX RF synthesizer is not locked. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : Temperature too low DESCRIPTION : The temperature inside the RF Module is too low. INSTRUCTIONS : 1. Ensure that the ambient temperature on the site is acceptable. 2. Block/unblock the RF module. 3. If that does not help, replace the faulty RF Module.

92 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7654 CELL OPERATION DEGRADED

FAULT REASON : Transmission quality detoriated DESCRIPTION : The TX signal adjustment fails. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : TX out of order DESCRIPTION : The RF Module TX path is not usable. INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

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

FAULT REASON : Unit blocked DESCRIPTION : A unit is blocked with the BTS Site Manager. The purpose of the fault is to avoid alarms that may rise during the unit maintenance task. INSTRUCTIONS : To cancel the alarm, unblock the unit.

FAULT REASON : Unit initialization failure DESCRIPTION : A unit or an IP address initialisation has failed. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Block/unblock the faulty unit. If that does not help, replace the faulty unit. 2. If the 7650 BASE STATION FAULTY alarm is issued, reset the site. 3. If the WAM is the alarm 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 faulty unit.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

93 (148)

Base Station Alarms (7000-7900)

FlexiBTS: 1. Block/unblock the faulty unit. If that does not help, replace the faulty unit. 2. If the FCM is the alarm source, check the RNC IP address in the commissioning file and modify the file if needed. If that does not help, perform a power-off reset. 3. If Step 2 does not help, replace the faulty unit.

FAULT REASON : Unit not supported by current BTS SW version DESCRIPTION : 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 REASON : Unit unidentified DESCRIPTION : A corrupted flash memory or an unknown module product code. INSTRUCTIONS : 1. Block/unblock RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : Unknown HW resource DESCRIPTION : A unit cannot be identified by its product code or by its physical device address (object ID). INSTRUCTIONS : Replace the unit.

FAULT REASON : VSWR minor alarm, <line> DESCRIPTION : The Filter has detected the VSWR exceeding the defined level. The antenna line is slightly mismatched. The antenna connector information at the end of the alarm text specifies the defective antenna line. INSTRUCTIONS : Check the antenna cables, connectors, antenna and possible antenna line devices. Check the antenna line (TX-cable-antenna) impedance matching.

Cancelling

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

94 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7655 CELL NOTIFICATION

32

7655 CELL NOTIFICATION
Meaning

A minor fault (or faults) has occurred in a unit (or units) that belong to the sector indicated in the alarm. Check the reason for the fault from the supplementary text field of the alarm.

Supplementary information fields

1 2 3 4 5 6

rack (cabinet) number shelf number slot type of unit unit number 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 at the BTS. Make sure the environment does not cause the fault. Before a unit is replaced at the BTS, the site should be reset to recover from any temporary faults, which might have caused the misbehaviour of the unit. When an active alarm is a 'Start' alarm, a site reset is required to cancel the alarm. If the site reset or unit block/unblock does not help, replace the faulty unit (see source of the alarm and instructions fields of the corresponding alarm). Refer also to the individual alarm instructions. And if that does not help, contact the local Help Desk. For more information, see Nokia WCDMA BTS Alarm Descriptions. (SW and release document)

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

95 (148)

Base Station Alarms (7000-7900)

FAULT REASON : Cell power parameter out of range DESCRIPTION : The power values in the cell configuration data sent by the RNC are out of range. INSTRUCTIONS : Set the correct power values to the RNC.

FAULT REASON : Communication failed with application <x> DESCRIPTION : 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 is properly connected. If the unit led does not light up, the unit is faulty. Check the faulty unit. 2. Check the alarm history.

FAULT REASON : Cooling fan out of order DESCRIPTION : The RF Module cooling fan is not rotating at the specified speed. INSTRUCTIONS : 1. Check the fan. 2. If that does not help, block/unblock the RF Module. 3. If that does not help, replace the faulty fan (Fan1 or Fan2).

FAULT REASON : Error in file server during SW download DESCRIPTION : 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). INSTRUCTIONS : 1. Retry the SW update few times. 2. Check the FTP account user settings. 3. Check the file and path names. 4. Check the administration log on the file server.

FAULT REASON : RF Module ambient temperature above maximum DESCRIPTION : The ambient temperature is higher than the predefined maximum allowed value. INSTRUCTIONS : 1. Check the environment conditions of the site. 2. If that does not help, block/unblock the RF Module. 3. If that does not help, replace the faulty RF Module.

FAULT REASON : RF Module ambient temperature below minimum DESCRIPTION : The ambient temperature is lower than the predefined minimum allowed value. INSTRUCTIONS : 1. Check the environmental conditions of the site. 2. If that does not help, block/unblock the RF Module. 3. If that does not help, replace the faulty RF Module.

FAULT REASON : RF Module temperature value missing DESCRIPTION : The RF Module cannot report the temperature value or the sensor is faulty.

96 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7655 CELL NOTIFICATION

INSTRUCTIONS : 1. Block/unblock the RF Module. 2. If that does not help, replace the faulty RF Module.

FAULT REASON : Telecom cell enabling or disabling failed DESCRIPTION : The cell enabling (the setup of CPICH and BCH) failed, or the cell disabling (the release of common channels) failed. The reason could be a hardware or a bus problem, or a lack of DSP or ATM resources. INSTRUCTIONS : UltraSite, MetroSite, MetroSite50, Triple-mode: 1. Check the other active alarms. 2. Check the number of WSP units. Flexi BTS: 1. Check the other active alarms. 2. Check the number of FSP units.

FAULT REASON : Timestamp mismatch in summing DESCRIPTION : The timestamp mismatch in summing. Configuration error (2 different FSP functioning) - after acknowledgement the fault will return again. Data corruption on the bus - it appears once when the unsynchronised data is sent by the BB. INSTRUCTIONS : Check the BB bus configuration.

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

97 (148)

Base Station Alarms (7000-7900)

98 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7660 BASE STATION LICENCE EXPIRED

33

7660 BASE STATION LICENCE EXPIRED
Meaning

A licence fault (or faults) has occurred in the base station. Check the reason for the fault from the supplementary text field of the alarm.

Supplementary information fields

1 2 3 4 5 6

rack (cabinet) number shelf number slot type of unit unit number subunit number

For more information, see instructions on Alarm Structure.

Instructions

FAULT REASON: DESCRIPTION:

INSTRUCTIONS:

BTS licence for the feature is expired Licence for the feature is expired and the expired licence file (s) are deleted from flash memory. Buy or renew a licence for the feature.

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

99 (148)

Base Station Alarms (7000-7900)

100 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7661 BASE STATION LICENCE NOTIFICATION

34

7661 BASE STATION LICENCE NOTIFICATION
Meaning

A licence fault (or faults) has occurred in the base station. Check the reason for the fault from the supplementary text field of the alarm.

Supplementary information fields

1 2 3 4 5 6

rack (cabinet) number shelf number slot type of unit unit number subunit number

For more information, see instructions on Alarm Structure.

Instructions

FAULT REASON: DESCRIPTION: INSTRUCTIONS: FAULT REASON: DESCRIPTION: INSTRUCTIONS:

HW capacity too low for feature HW capacity too low to support all licences of an optional feature. Delete licence or insert new HW. Licence missing <licenceCode>, <licenceName> BTS detected a resource needing a license but no license exists or is free. An appropriate licence should be activated or the licence amount should be increased.

FAULT REASON : HW capacity too low for feature

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

101 (148)

Base Station Alarms (7000-7900)

DESCRIPTION

: The HW capacity is too low to support all licences of an optional feature. INSTRUCTIONS : Delete the licences or insert new hardware.

FAULT REASON : Licence missing <licenceCode>, <licenceName> DESCRIPTION : The BTS detected a resource needing a license but no license exists or is free. INSTRUCTIONS : An appropriate licence should be activated or the licence amount should be increased.

Cancelling

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

102 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7665 BASE STATION TRANSMISSION ALARM

35

7665 BASE STATION TRANSMISSION ALARM
Meaning

A transmission fault (or faults) has occurred in the Nokia WCDMA Flexi Base Station. This alarm is an encapsulation alarm that is used to transfer the Flexi Transport Submodule (FT) alarm data over BTS O&M connection through RNC to Nokia NetAct. Encapsulation is used because RNC alarm system cannot support the FT alarms directly due to differences in alarm structure. In Nokia NetAct this alarm is shown in opened format. This means that the alarm number, alarm text and supplementary information are shown in original FT format and the alarm printout is thus different in Nokia NetAct compared to alarm listings in RNC local user interfaces. 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 from Alarms for FTM document.

Supplementary information fields

1 2 3

probable cause reported by FT taken from 3GPP the managed object reported by FT alarm number reported by the FT. The FT has reserved alarm numbers from space 61000 - 61999 supplementary information fields reported by the FT. Each argument is separated by space For more information, see instructions on Alarm Structure.

4

Instructions

This alarm is an encapsulation alarm for original FT alarm. Follow up the instructions given in Alarms for FTM for the

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

103 (148)

Base Station Alarms (7000-7900)

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

FAULT REASON : Config-abort state on unit $U, IMA Group $IMAG DESCRIPTION : 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 near end and far end fit together (for example, IMA version and frame length). If needed, change the configuration accordingly.

FAULT REASON : EBER on unit $U, interface $IF DESCRIPTION : Excessive bit error rate. The measured bit error rate exceeds the configured threshold value (BER-3 or BER-6). Probable causes - the signal level is too low (optical connectors or cables are dirty, electrical connectors or cables are corroded) - the specified maximum length of the cable is exceeded - the connector is not properly connected to the unit - the receiver or the far end transmitter has failed 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 REASON : Far end config-abort state on unit $U, IMA Group $IMAG DESCRIPTION : 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 near end and far end fit

104 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7665 BASE STATION TRANSMISSION ALARM

together (for example, IMA version and frame length). If needed, change the configuration accordingly.

FAULT REASON : Far end group start-up on unit $U, IMA Group $IMAG DESCRIPTION : Far end group start-up. This alarm is raised when the far end indicates that it is in start-up phase. The alarm is typically active only temporarily. Probable cause: The IMA group at the far end is not up and running yet. 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 the individual IMA links). If this is the case, follow the instructions for handling those alarms.

FAULT REASON : Far end insufficient links on unit $U, IMA Group $IMAG DESCRIPTION : 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 near end and far end fit together. If needed, change the configurations accordingly.

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

FAULT REASON : Far-end transmit link unusable on unit $U, interface $IF DESCRIPTION : 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.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

105 (148)

Base Station Alarms (7000-7900)

FAULT REASON : Group timing mismatch on unit $U, IMA Group $IMAG DESCRIPTION : 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.

FAULT REASON : IMA link out of delay synchronization on unit $U, interface $IF DESCRIPTION : 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 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 appropriate link.

FAULT REASON : IMA remote failure indication on unit $U, interface $IF DESCRIPTION : 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 REASON : Insufficient links on unit $U, IMA Group $IMAG DESCRIPTION : 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

106 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7665 BASE STATION TRANSMISSION ALARM

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. 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 near end and far end fit together. If needed, change the configurations accordingly.

FAULT REASON : License Missing for feature $feature on interface $if DESCRIPTION : The feature referenced in the alarm text has been configured without installing a valid licence. Probable cause: A valid licence that would allow the operation of the feature is not available in the WBTS. INSTRUCTIONS : Download a valid licence to the WBTS as instructed in Managing licences.

FAULT REASON : LOCD on unit $U, interface $IF DESCRIPTION : 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 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 REASON : LOF on unit $U, interface $IF DESCRIPTION : Alarm text: LOF on unit$U, interface $IF Possible impact on the connections over this interface: - no calls are possible anymore - loss of remote management access to other network elements in the RAN 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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

107 (148)

Base Station Alarms (7000-7900)

match each other.

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

FAULT REASON : LOS on unit $U, interface $IF DESCRIPTION : Alarm text: LOS on unit$U, interface $IF Possible impact on the connections over this interface: - no calls are possible anymore - loss of remote management access to other network elements in the RAN - loss of synchronisation if the interface is used as a synchronisation source INSTRUCTIONS : 1. Check that the cables are connected to the correct connectors. 2. Check that the interface at the far end interface is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms. 4. To verify that the hardware of the interface unit works correctly, connect a loop cable and check whether the alarm disappears.

FAULT REASON : Loss of IMA frame on unit $U, interface $IF DESCRIPTION : Loss of IMA frame. The loss of the IMA frame was detected in one link of the IMA group. The far end IMA link is not part of an IMA group. All other transmission alarms related to this IMA link are suppressed. Probable causes: - 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 REASON : RDI on unit $U, interface $IF DESCRIPTION : 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 or LOF alarm on its receiving interface.

108 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7665 BASE STATION TRANSMISSION ALARM

INSTRUCTIONS : 1. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. 2. To check the transmit hardware of the FTM, connect a loop cable and check that no alarms appear for this interface.

FAULT REASON : STC connection to signalling peer not established on interface $ DESCRIPTION : The SSCOP link controlled by this STC is down. Probable causes: - the peer (RNC) releases the connection by sending an END PDU - the link goes down because the peer (RNC) does not respond within the TIMER_NO_RESPONSE period. - the link was never established - problem on ATM layer - problem on physical layer - incomplete or faulty configuration of AAL2 in RNC INSTRUCTIONS : 1. Check that there are no other alarms on physical or ATM layer active. 2. Check that the RNC is up and running. 3. Check the AAL2 configuration. For example, make sure that the VP/VC used for an AAL2 signalling link match between the RNC and WBTS.

FAULT REASON : Synchronisation lost DESCRIPTION : Primary and secondary timing source lost. FTM is running on internal clock or in hold-over mode. No timing signal is sent to the WBTS. The first and second synchronisation sources from the configured priority list are unavailable. On failure, FTM 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 or LOF). INSTRUCTIONS : Use the BTS Site Manager to check which interfaces have been configured as synchronization sources. For the PDH interfaces, do as follows: 1. Check that the cables are connected to the correct connectors. 2. Check whether the interface at the far end is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions on handling those alarms. 4. To verify that the hardware of the interface unit works correctly, connect a loop cable and check whether the alarm disappears.

FAULT REASON : The FTM booted at $date due to $RCause DESCRIPTION : The FTM has been reset. INSTRUCTIONS : N/A

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

109 (148)

Base Station Alarms (7000-7900)

FAULT REASON : Timing source lost on unit $U, interface $IF DESCRIPTION : Primary or secondary timing source 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, 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 Nokia BTS Site Manager to check which interfaces have been configured as synchronization sources. For the PDH interfaces, do as follows: 1. Check that the cables are connected to the correct connectors. 2. Check whether the interface at the far end is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions on handling those alarms. 4. To verify that the hardware of the interface unit works correctly, connect a loop cable and check whether the alarm disappears.

Cancelling

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

110 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7740 BEATING WCDMA BTS ALARM

36

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 this alarm and the beating alarm that caused this alarm.

Supplementary information fields

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

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

111 (148)

Base Station Alarms (7000-7900)

112 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7750 FAILURE IN WCDMA WBTS O&M CONNECTION

37

7750 FAILURE IN WCDMA WBTS O&M CONNECTION
Meaning

This alarm indicates that a failure has occurred in WBTS O&M connection. The problem is related either to Iub connection between RNC and WBTS, or to NWI3 connection between RNC and NMS. From RNC point of view the actual reason for the failure is either in transmission network between network elements (Iub or NWI3), in internal communication of RNC applications or in WBTS configuration. Location of the failure (Iub or NWI3) can be determined from the supplementary information fields of this alarm. In Iub connection problem between RNC and WBTS this alarm is set by OMU unit in 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 RNC and WBTS 4) a WBTS id conflict has been detected in the network In NWI3 connection problem between RNC and NEMU unit in following situations: 1) WBTS O&M operation reply sending from 2) Internal NEMU error in WBTS O&M reply 3) NEMU has received unexpected WBTS O&M NMS, this alarm is set by NEMU to NMS has failed handling has occurred reply

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 WBTS to report it's alarms to RNC. In case of NWI3 problem the WBTS O&M mediation tasks done by NEMU unit cannot be performed (SW download, SW version upload, HW configuration upload). This alarm does not indicate a failure in WBTS user plane links. The states of the user plane links can be checked using RNC Object Browser.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

113 (148)

Base Station Alarms (7000-7900)

Supplementary information fields

1

reason of the alarm 1 = failure in the RNC-WBTS connection 2 = WBTS id conflict 5 = failure in the RNC-NMS connection

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

Instructions

Error reason (field 1) indicates which part of the connection the problem is located. 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 connection. Wait until WBTS opens new connection and system cancels the alarm. If connection does not recover in couple of minutes, check that WBTS is configured correctly to RNC 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 RNC attempted to send an O&M message towards the WBTS, but the connection does not exist in the RNC for the WBTS in question (code 14608) or some error occurred in TCP layer when message sending was attempted. Check that WBTS is configured correctly to RNC and to Network.

114 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7750 FAILURE IN WCDMA WBTS O&M CONNECTION

If configuration is ok, wait until WBTS opens 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 RNC is waiting new O&M connection opening from WBTS. Wait until system cancels the alarm.

Error 14001 14011 14015

codes: = NETWORK IS DOWN = OPERATION TIMED OUT = HOST IS DOWN

There are problems in transmission network to WBTS. Check type of network problem with following instructions: Check that ATM-path is not locked. MML commands ZLA for interface and ZLC for VP/VC link termination points. Locked ATM-path will break O&M connection or prevent new connection opening. Unlock ATM-path to allow O&M connection to be established. Check success of PING between RNC and WBTS: MML command: ZQRX If ping does not succeed, then the problem is in lower level of the transmission network. Check physical connections in network. If ping does succeed, then the problem is in application level. In many cases there is also more info in OMU computer log. It can be studied with MML-command ZDDE::"ZGSC"; Check the state of TCP connection to WBTS. MML command: ZQRS Active Internet connections listing should contain BS-O&M connection in ESTABLISHED state for each WBTS. If the connection to WBTS does not exist, the problem is in application level with connection opening. If the connection is in other than ESTABLISHED state, the problem is in application level with connection handling. In many cases there is also more info in OMU computer log. It can be studied with MML-command ZDDE::"ZGSC";

Error code: 14051 = POSIX ERROR 100

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

115 (148)

Base Station Alarms (7000-7900)

This error code is used in a situation where RNC has received connection establishment from a WBTS but there is already a connection open for the same WBTS ID but from different IP address. This situation may occur e.g. if the WBTS sites have been improperly configured somewhere in the network so that two (or more) WBTSs have the same WBTS ID. In this case the RNC discards the new connection attempt and keeps the old connection open. The Iub O&M traffic should be analysed to find out the cause for this behavior. 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 Customer Service Center.

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.

Error reason = 5, failure in NMS connection WBTS O&M mediation reply data has been lost. Check WBTS id from NEMU event log (error log) and redo the operation that caused the failure after identifying and correcting the possible problem

116 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7750 FAILURE IN WCDMA WBTS O&M CONNECTION

using steps mentioned below. Supplementary information field 1 (reason of the alarm) value 5 specifies that some of the following cases has occurred: WBTS O&M reply sending from NEMU to NMS has failed 1. Open EM application Action Log Viewer 2. Search for event log writings that are written by "NWI3 SW Configuration Management" (SW Management) or "Nwi3HWAgentSrv" (HW Management) - If network connection to NMS is broken or NMS counterpart process is not available, NEMU event log writing contains text "COMM_FAILURE" -> Check NEMU - NMS connection state. Try to ping NEMU from NMS. -> If ping succeeds, check from NMS that appropriate counterpart process is up and running.

Internal NEMU error in WBTS O&M reply handling 1. Open EM application Action Log Viewer 2. Search for event log writings that are written by "NEMU WBTS O&M Manager" with timestamp near the time of the alarm and check the writings for following situations: - Event log writing contains text "Connection to Nwi3SWSender does not work" -> Open NetOp connection to NEMU -> Check from NEMU Platform Manager User Interface (PMUI) that process "NWI3 SW Configuration Management" is up and running. Use PMUI to restart the process if needed. - Event log writing contains error code 0x80047543 (NEMUBSOM_E_BSMSG_OPERATION_FAILED) -> Check event log writings written by "NWI3 SW Configuration Management" and "Nwi3HWAgentSrv" processes. Search error texts, for example "COMM_FAILURE" or "internal exception". If exception is found, it means that O&M reply sending to NMS failed. -> Open NetOp connection to NEMU -> Check using PMUI that process "NWI3 SW Configuration Management" is up and running. Use PMUI to restart the process if needed. NEMU has received unexpected WBTS O&M reply 1. Open EM application Action Log Viewer 2. Search for event log writings written by "NEMU WBTS O&M Manager" that contain text "BS-<bsid>, <saved reply name>, Pending <request name> not found" for following situations: -> Request has been removed from NEMU (timer has gone off) or WBTS has sent an extra message that has no corresponding request in NEMU. Timeout situation has occurred if event log contains also writing by "NEMU WBTS O&M Manager" that contains text "Timeout, removed <operation> to BS-<bsid>".

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

117 (148)

Base Station Alarms (7000-7900)

Extra message situation has occurred if event log contains also writing by "NEMU WBTS O&M Manager" that contains text "BS-<bsid>, <reply operation>, Pending <request operation> not found" Note that after the problem in NWI3 connection has been corrected, the system will cancel the alarm only after next O&M mediation event is sent to NMS successfully. Thus it is normal behaviour that alarm stays active for a while after the problem has been corrected. The operation that caused the failure should be tried again to verify that problem is corrected.

Cancelling

Do not cancel the alarm with error reason 1 and 5. 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. 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. Error reason = 5 Next succeeded BTS O&M operation cancels the alarm.

118 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7761 RNW O&M SCENARIO FAILURE

38

7761 RNW O&M SCENARIO FAILURE
Meaning

The alarm indicates a failure in some of the following scenarios: - RNC 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) management - Audit handling - Common channel supervision - Common measurement supervision - WBTS recovery (system initiated COCO disconnect/connect 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 RNC Object Browser 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 causes the cell (s) to be blocked and hence unavailable to traffic. Failure in cell blocking can lead to erroneous cell state information in the RNC. Failure in WBTS capability updating or pid updating can cause incorrect WBTS capability data to be used in the RNC and thus problems in signalling or actual calls. Failure in User plane configuration (AAL2 path unblocking) causes a situation where the User plane traffic can not be transferred in the corresponding AAL2 VCC.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

119 (148)

Base Station Alarms (7000-7900)

Supplementary information fields

1

reason for the failure 01 02 03 04 05 06 07 08 09 0A 0B 0E 11 12 13 14 15 16 18 19 20 21 WBTS reservation has failed Configuration data updating has failed Inactivation of the cell has failed Activation of the cell has failed Common channel deletion has failed Common channel creation has failed BCCH information updating has failed WBTS capability information was not received Forced handover request was not accepted WBTS capability information update has failed AAL2 path unblocking has failed Unknown NBAP interface type Audit has failed, only 3GPP iub Cell setup procedure has failed, only 3GPP iub Cell deletion procedure has failed, only 3GPP iub Common measurement initiation has failed, only 3GPP iub RRI measurement initiation has failed, only 3GPP iub Cell reconfiguration procedure has failed, only 3GPP iub Common or RRI measurement termination failed, only 3GPP iub Cell barring has failed COCO disconnect has failed COCO connect has failed

2

scenario that was being carried out when the failure occurred 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 81 82 83 84 8D 8E 8F 90 91 92 Not specified WBTS initialization, Nokia iub Cell unlocking, Nokia iub Configuration data modification, Nokia iub RNC restart, Nokia iub Local cell resource state change Forced handover WBTS reset initiation from RNC WBTS capability information update Pid update Connection configuration management Audit handling, 3GPP iub CCH Supervision WBTS recovery Iu service barring Cell deletion, 3GPP iub WBTS initialization, 3GPP iub Cell unlocking, 3GPP iub Cell reconfiguration, 3GPP iub RNC restart, 3GPP iub WBTS restart, 3GPP iub WBTS cell block, 3GPP iub WBTS cell unblock, 3GPP iub Resource status indication handling, 3GPP iub Common measurement supervision Dedicated measurement initiation

120 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7761 RNW O&M SCENARIO FAILURE

3

general error code of the system You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials, Maintenance Manual) or from the document General Error Messages of System, Supplementary References

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 RNC Object Browser that WBTS id is valid in the system and COCO 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 RNC Object Browser. -> 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 resources related to COCO are not locked. Locked ATM resources will prevent the connection

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

121 (148)

Base Station Alarms (7000-7900)

configuration operations. - 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 RNC Object Browser). - 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, e.g. COCO creation, try to perform the operation again. - If configuration is correct and ATM resources are unlocked, act according to 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 disconnect has failed) or 21 (COCO connect has failed): - In case of COCO disconnect failure, disconnect the COCO manually using RNC RNW Object Browser by removing the WBTS id from the corresponding COCO object. Wait at least for 15 seconds and connect the COCO again by restoring the WBTS id to COCO object. - In case of COCO connect failure, try to connect the COCO again to the WBTS using RNC RNW Object Browser. 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 the also the WBTS id that this alarm is targeted to. 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 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 RNC Object 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 RNC Object Browser, or - Reform the connection between WBTS and COCO by first disconnecting the COCO and then reconnecting it (this can be done by changing the used COCO id in the WBTS with RNC Object Browser) or block/unblock the BTS with BTS element manager.

122 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7761 RNW O&M SCENARIO FAILURE

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 Customer Service Center: - OMU computer log, - message monitoring from OMU (families 50B, 4FA, 4EE and 4EF) and serving ICSU (check serving ICSU from COCO data in RNC Object Browser, monitor families 4FE, 4FB, 4FD, 4B7) during BTS reset Also RNC 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";

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

123 (148)

Base Station Alarms (7000-7900)

124 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7762 RNW DATABASE OPERATION FAILURE

39

7762 RNW DATABASE OPERATION FAILURE
Meaning

RNW database operation has failed. This reading or writing operation was tried to be carried out 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 - RNC restart - Audit handling - Iu service barring - Resource status indication handling - Common measurement supervision Depending on the scenario, this failure has lead to a situation where cell state could not be modified from blocked to working state or vice versa in RNC or it was not possible to send configuration data to WBTS. Failure in pid updating can cause troubles 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 RNC and thus problems in signalling or in actual calls.

Supplementary information fields

1

specifies if the error occurred during reading from or writing to database 01 02 Reading failure Writing failure

2

reason of the failure

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

125 (148)

Base Station Alarms (7000-7900)

00 01 02 03 04 05 11 12 3

Not specified Failure at initialization Configuration data Inactivation of the cell has failed Activation of the cell has failed NBAP-link state updating failure Failure in cell setup, 3GPP iub Failure in cell reconfiguration, 3GPP iub

scenario that was being carried out when the failure occured 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 81 82 83 84 8D 8E 8F 90 91 WBTS initialization Cell unlocking Configuration data modification RNC restart Local cell resource state change Forced handover WBTS reset WBTS capability information update Pid update CCH data update Link failure/link failure cancel CCH Supervision Audit handling, 3GPP iub Iu service barring WBTS initialization, 3GPP iub Cell unlocking, 3GPP iub Cell reconfiguration, 3GPP iub RNC restart, 3GPP iub WBTS restart, 3GPP iub WBTS cell block, 3GPP iub WBTS cell unblock, 3GPP iub Resource status indication handling, 3GPP iub Common measurement supervision

4

general error code of the system. You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials, Maintenance Manual) or from the document General Error Messages of System, Supplementary References

Instructions

At first check the functionality of Radio Network database with following MML-commands: ZDBS:RAQUEL,0; State of database should be normal and memory (and disk) updates are 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 check with MML-command ZDBD:OMU; Line "RAQUEL" specifies the state of Radio

126 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7762 RNW DATABASE OPERATION FAILURE

Network database. If database state is working (or becomes working after while), do as follows: Try to lock the cell and then unlock the cell with RNC Object Browser. If this does not clear the alarm, WBTS reset can be tried If database state stays abnormal for long time or the alarm appears constantly for several WBTSs and cells, contact the local Nokia Customer Service Center. Also RNC reset might help if it is possible to make. More information about the exact fail reason can be found by examining the supplementary info field 4 (error code). In many cases there also more info in OMU computer log. It can be studied with MML-command ZDDE::"ZGSC";

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

127 (148)

Base Station Alarms (7000-7900)

128 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7771 WCDMA CELL OUT OF USE

40

7771 WCDMA CELL OUT OF USE
Meaning

The alarm indicates that unlocked WCDMA cell is blocked for some reason, and it can not transmit any traffic. This alarm is set only when cell is moved to blocked state by the system, meaning that user initiated state change does not cause the alarm to be set. The alarm is set when some of the following situations occur: 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 WCEL state changes first from WO to BL (H) (bl - shutting down) and only after that to some of the above mentioned states. This alarm is NOT set when WCEL state changes from WO to BL (H), it is set when BL (H) state is replaced by some of the above mentioned blocked states. 2. WCEL is unlocked and COCO connection operation has been performed, but WCEL state does not change to WO state. 3. COCO connection operation is performed, WCEL has been unlocked but WCEL state does not change to WO state. 4. Incorrect Local Cell Resource id has been given to this cell. Such Local Cell does not exist in WBTS. Alarm is cancelled automatically when WCEL recovers to WO state or when the cell is locked by the user.

Supplementary information fields

1

indicates the state that WCEL was changed into and what caused the alarm to be set. Full information about the current cell state is available in RNC Object Browser. Meaning of the possible values and corresponding GUI abbreviation:

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

129 (148)

Base Station Alarms (7000-7900)

0008: 0020: 0040: 0080: 0100: 0200: 0400: 2

bl bl bl bl bl bl bl

-

WBTS (WBTS has sent disabled state information) (B) system failure (S) init (also during resets) (I) C-NBAP-link failure (L) Common measurement failure (M) Blocked by user locally from WBTS (Ub) Blocked because cell does not exist in WBTS (N)

general error code of the system. You can check its meaning from General Error Messages of System.

Instructions

First task: wait 5 minutes. Typically there is still some recovery operation ongoing. Alarm is cancelled if recovery is successful. If automatic recovery does not correct the situation, follow these steps: 1. If blocking reason in supplementary info field 1 (WCEL state) is 0008 (BL (B)) or 0200 (BL (Ub)), check WBTS alarm that is related to this WCEL and follow operating instructions there. 2. If blocking reason in supplementary info field 1 (WCEL state) is 0400 (BL (N)), incorrect Local Cell Resource id has been given to this cell. Such Local Cell does not exist in WBTS. Cell data must be corrected and then WBTS reset is required to remove the problem. 3. In case there are no alarms targeted to WCEL, try to lock and then unlock the cell manually with RNC Object Browser. This causes system to try to clear possible hanging cell related resources and then recreate (init) them. 4. If alarm is not cancelled due lock / unlock cell operation you can try some of the following actions (each of these causes WBTS to be unavailable during the operation). These operations clear and again init the BTS related resources: - Reset WBTS with RNC Object Browser, or - reform connection between WBTS and COCO by first disconnecting the COCO and the reconnecting it (This can be done by changing the used COCO id in WBTS with RNC Object Browser), or - block/unblock BTS with 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 following logs and contact the local Nokia Customer Service Center: - OMU computer log (service terminal command ZGSC), - message monitoring from OMU (families 50B, 4FA, 4EE and 4EF) and serving ICSU (check serving ICSU from COCO data in RNC Object Browser, monitor families 4FE, 4FB, 4FD, 4B7) during BTS reset.

130 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7771 WCDMA CELL OUT OF USE

Also RNC reset might help if it is possible to make. More information about the exact fail reason can be found by examining the supplementary info field 2 (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 also more info in OMU computer log. It can be studied with MML-command ZDDE::"ZGSC";

Cancelling

Do not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected. The alarm is cancelled by system if the cell in question becomes working again or it is locked by user.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

131 (148)

Base Station Alarms (7000-7900)

132 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7772 PHYSICAL SHARED CHANNEL CONFIGURATION FAILED

41

7772 PHYSICAL SHARED CHANNEL CONFIGURATION FAILED
Meaning

This alarm indicates that there has been an error when RNC has requested configuration or reconfiguration of HSDPA channels to BTS. This possible causes which result in this alarm are: - a problem in transmission network between RNC and BTS - BTS has rejected the configuration of HSDPA channels - RNC is unable to send the HSDPA configuration to BTS because of RNC internal problems (e.g. congestion in Iub interface) Location of the failure can be determined from the supplementary information fields of this alarm. As a consequence of this alarm, HSDPA connections cannot be used in particular cell.

Supplementary information fields

1

reason of the alarm Possible values: 1 = No reply from BTS 2 = BTS rejects the configuration 3 = RNC internal error

2 3 4

computer unit where this alarm is generated from index of the alarming unit more detailed cause in case the BTS rejects the configuration Possible values: 0 1 2 3 = = = = Error in radio network configuration Error in transport layer Error in NBAP protocol layer Miscellaneous

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

133 (148)

Base Station Alarms (7000-7900)

5

possible values sent by the BTS: 0 1 6 9 = = = = Unknown cell ID (RNW configuration) Cell not available (RNW configuration) Node B resources unavailable (RNW configuration) Requested configuration not supported (RNW configuration)

4 = Unspecified (Misc) 6 more detailed cause in case the value of the 1st supplementary information field is 3 ("RNC Internal error"). Possible values: 306 402 404 420 501 504 505 = = = = = = = Internal waiting timer expired in BTS Resource Manager Wrong BTS ID Wrong cell ID No free DL Spreading Codes available for HSDPA Internal waiting timer expired in NBAP interface Encoding failed in NBAP interface Decoding failed in NBAP interface

Instructions

The first supplementary information field indicates the main reason for the problem. Reason 1: 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 RNC RNW Object Browser main dialog. If the C-NBAP link is working, the problem may reside in the BTS. Check the BTS configuration and logs using BTS Manager. If the C-NBAP link is not working, check the success of PING between RNC and BTS. Successful PING tells that the BTS is up and running: MML command: ZQRX If ping does not succeed, then the problem is in lower level of the transmission network. Check physical connections in network. If ping does succeed, then the problem is in application level. In many cases there is also more info in OMU computer

134 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7772 PHYSICAL SHARED CHANNEL CONFIGURATION FAILED

log. It can be studied with MML-command ZDDE::"ZGSC"; Reason 2: BTS rejects the configuration Check that the concerned BTS is in working state using RNC RNW Object Browser. 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 Customer Service Center. 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 RNC using RNW RNC Object Browser, and the configuration in BTS using BTS Manager. Check also if other alarms are active targeted to this same WBTS object. If there are active alarms, proceed according to instructions given for those alarms. If the fault cannot be resolved by correcting the configuration or other BTS alarms, contact the local Nokia Customer Service Center. Reason 3: RNC internal error An internal error in RNC has occured during Physical Shared Channel Configuration procedure. If the 6th supplementary information field of this alarm has a value 306, 420, 501, 504 or 505, 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 e.g. 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 mentioned in 2nd and 3rd supplementary information fields of this alarm (families 04FE, 04FB) and in active OMU unit. 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 Customer Service Center.

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

135 (148)

Base Station Alarms (7000-7900)

Locking or deleting of the cell, or next succeeded configuration of HSDPA channels cancels the alarm.

136 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7773 WCEL THRESHOLD MONITORING LIMIT EXCEEDED

42

7773 WCEL THRESHOLD MONITORING LIMIT EXCEEDED
Meaning

When this alarm has been triggered, it means that a threshold monitoring rule has been evaluated as true by NEMU for some WCDMA cell object in the Cell Resource measurement. More information on the event can be seen with the NE Threshold Management application in RNC Element Manager. Threshold monitoring makes it easier to detect faults, identify bottlenecks and optimise the network. Using RNC Element Manager GUI, appropriate performance thresholds are determined for each important variable, and exceeding these thresholds indicates a problem worth of attention. These variables can be either single counters or Key Performance Indicators (KPIs), which can be a combination of several counters. When performance data is gathered on variables of interest from the measured objects in the network, their values are compared against any active threshold limits. When a performance threshold is exceeded, an alarm is generated and sent to the network management system. In addition to this, a threshold event log is saved in the network element for further study of the events which have occurred in that NE during a certain period of time.

Supplementary information fields

1

measurement type of the threshold rule which has been exceeded. The measurement type number is the same which is used in NetAct name of the threshold rule which has been exceeded

2

Instructions

Threshold alarm does not necessarily mean that there are problems in the network element, because thresholds can be freely set by the operator, and some rules may have been set incorrectly. To get further information on the reason of the threshold alarm:

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

137 (148)

Base Station Alarms (7000-7900)

- Connect to the network element with Element Manager. - Open the NE Threshold Management application. - Select "Show Threshold Log" from the View menu and check the threshold log. When the target object and other information of the alarm have been checked from the log, you can obtain more information from the performance counters of measurements and, if necessary, take appropriate action to correct the problem. The counters can be browsed with RNW Measurement Presentation application or by using NetAct reporting tools.

Cancelling

The alarm is cancelled automatically after the defined alive-time has expired.

138 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7774 MEASUREMENT THRESHOLD MONITORING LIMIT EXCEEDED

43

7774 MEASUREMENT THRESHOLD MONITORING LIMIT EXCEEDED
Meaning

When this alarm has been triggered, it means that a threshold monitoring rule has been evaluated as true by NEMU for some WCDMA cell object in some other RNW measurement than Cell Resource measurement for which threshold limit breaks are reported with alarm wcel_threshold_a. More information on the event can be seen with the NE Threshold Management application in RNC Element Manager. Threshold monitoring makes it easier to detect faults, identify bottlenecks and optimise the network. Using RNC Element Manager GUI, appropriate performance thresholds are determined for each important variable, and exceeding these thresholds indicates a problem worth of attention. These variables can be either single counters or Key Performance Indicators (KPIs), which can be a combination of several counters. When performance data is gathered on variables of interest from the measured objects in the network, their values are compared against any active threshold limits. When a performance threshold is exceeded, an alarm is generated and sent to the network management system. In addition to this, a threshold event log is saved in the network element for further study of the events which have occurred in that NE during a certain period of time.

Supplementary information fields

1

measurement type of the threshold rule which has been exceeded. The measurement type number is the same which is used in NetAct name of the threshold rule which has been exceeded

2

Instructions

Threshold alarm does not necessarily mean that there are problems in the network element, because thresholds can be freely set by the operator, and some rules may have been set incorrectly.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

139 (148)

Base Station Alarms (7000-7900)

To get further information on the reason of the threshold alarm: - Connect to the network element with Element Manager. - Open the NE Threshold Management application. - Select "Show Threshold Log" from the View menu and check the threshold log. When the target object and other information of the alarm have been checked from the log, you can obtain more information from the performance counters of measurements and, if necessary, take appropriate action to correct the problem. The counters can be browsed with RNW Measurement Presentation application or by using NetAct reporting tools.

Cancelling

The alarm is cancelled automatically after the defined alive-time has expired.

140 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS

44

7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS
Meaning

The alarm indicates that the Nokia specific configuration parameters in BTS might not be consistent with the parameters in RNC. These parameters are CellRange, RACHCapacity, SIB7factor, ShutdownWindow and ShutdownStepAmount. Situation causing this alarm will not obstruct network operations. The alarm is set when BTS has failed to accept the parameters send to it during cell setup or when BTS has not responded to the parameter sending during cell setup. Alarm is cancelled automatically after these configuration parameters have been successfully sent. The alarm is cell-specific and its indication has been prevented to NetAct by default. The RNC-specific alarm 3325, INCONSISTENCY IN NOKIA SPECIFIC CONFIGURATION PARAMETERS, is related to this alarm and one instance of it is activated when Nokia specific configuration parameter sending has failed to one or more cells in certain RNC. This RNC-specific alarm is sent to NetAct by default. Alarm indication preventions can be altered with MML command AFC.

Supplementary information fields

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 RNC using RNC Object Browser. If these parameter values are the same as those in the BTS Site Configuration File, then no actions are needed in RNC. Check if other alarms are active for the BTS or WCEL in question.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

141 (148)

Base Station Alarms (7000-7900)

If the cell parameters in RNC are not the same as those in the BTS Site Configuration File and these parameters need to be updated, following actions can be taken to the cell that has failed to accept the parameters sent: * Modify these parameters with RNC Object Browser. This is recommended if cell is working i.e. cell state (WCEL state) is WO. * Lock the cell and then unlock it with RNC Object Browser. This operation causes the parameters to be resent to the BTS. More information about the exact fail 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, Maintenance Manual) or from the document General Error Messages of System, Supplementary References. 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 HW failure has occurred. * 15480 = NO RESOURCES IN WBTS Node B resources are unavailable. * 16504 = INTERNAL NBAP ERROR PREVENTING PROCEDURE COMPLETION Internal error has occurred that prevents parameter sending. In these fault cases the actions mentioned above should repair the situation. Fault cases with error code EQUIPMENT FAILURE may also require repairing of BTS HW. In many cases there also more info in OMU computer log. It can be studied with MML-command ZDDE::"ZGSC";

Cancelling

Do not cancel the alarm. The system cancels the alarm automatically after these parameters are sent successfully to the WBTS.

142 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7776 HSDPA FAILURE IN WCEL

45

7776 HSDPA FAILURE IN WCEL
Meaning

A major fault (or faults) has occurred in the BTS. A unit (or units) that take care of HSDPA traffic in WCEL may be faulty or there is not enough capacity available in BTS WSP cards for HSDPA service. This alarm is set when HSDPA capable BTS has sent a Resource Status Indication 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 the particular cell. Check the reason for the fault from BTS WSP related alarms.

Supplementary information fields

Instructions

The alarm requires no actions from the RNC side. Check WSP related active alarms in RNC that are targeted to this BTS. Alarms to be checked are: 7650 BASE STATION FAULTY 7651 BASE STATION OPERATION DEGRADED 7652 BASE STATION NOTIFICATION Faulty unit is mentioned in supplementary information field 3 of these alarms. All WSP related alarms must be checked because any WSP related fault may be a reason for this particular alarm. If HSDPA dedicated WSPC unit in BTS is faulty, BTS reserves another WSPC when it becomes free from another traffic. For more information about BTS alarms, see Nokia WCDMA BTS Alarm Descriptions (SW and release document).

Cancelling

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

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

143 (148)

Base Station Alarms (7000-7900)

144 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE

46

7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE
Meaning

This alarm is set when Dedicated Measurement (for transmitted code power) Initiation fails due to following 3 cases during cell initialization. 1) BTS problem, such as no response or nack 2) NBAP-D link is down 3) NBAP-D module has problem (RNC internal) RNC will retry Dedicated Measurement Initiation after the corresponding NBAP-D link is re-created to be ready. If the retry succeeds, the alarm will be cancelled. After this alarm, cells' capacity under the BTS might be affected.

Supplementary information fields

1

general error code of the system. You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials, Maintenance Manual) or from the document General Error Messages of System, Supplementary References communication control port id

2

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 1st supplementary information field. 1. Error code 13247 no_answer_from_remote_end_ec

No response from BTS

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

145 (148)

Base Station Alarms (7000-7900)

15479

nbap_bts_hw_res_not_avail_ec

BTS hardware failure

These code indicates 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 RNC RNW Object Browser (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 3) Add the WBTS id to the COCO 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 13846 no_resp_from_serv_provider_ec

NBAP-D link has been down 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 RNC processes should be analyzed by taking message monitoring from RNC 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 Customer Service Center. Attach OMU message monitoring 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 RNC EM).

Cancelling

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

146 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en

7799 RNC RADIO NETWORK TEST ALARM

47

7799 RNC RADIO NETWORK TEST ALARM
Meaning

This is a test alarm which is used only for testing purposes for the RNW alarm system of the RNC. This alarm does not indicate any fault situation, and the system does not generate this alarm by itself in any circumstances. The alarm is however handled as any actual alarm, so all the alarm handling rules are valid for it, and it has the same adjustable alarm parameters as the actual alarms.

Supplementary information fields

1

this is compared supplementary info field meaning that test alarms for same object can be identified by setting different values into this field. the one byte size of field which is output in decimal format. The field value is not significant. the two byte size of field which is output in decimal format. The field value is not significant. the four byte size of field which is output in decimal format. The field value is not significant. the one byte size of field which is output in hexadecimal format. The field value is not significant. the two byte size of field which is output in hexadecimal format. The field value is not significant. the four byte size of field which is output in hexadecimal format. The field value is not significant.

2

3

4

5

6

7

Instructions

No operation instruction.

dn99580892 Issue 5-0 en

# Nokia Corporation Nokia Proprietary and Confidential

147 (148)

Base Station Alarms (7000-7900)

Cancelling

Cancel the alarm with an MML command.

148 (148)

# Nokia Corporation Nokia Proprietary and Confidential

dn99580892 Issue 5-0 en