3G alarms

Nokia Siemens Networks WCDMA RAN, Rel. RU20, Operating Documentation, Issue 02

RNC Base Station Alarms (7000-7900)

DN99580892

Issue 08CApproval Date 2010-04-06

2 DN99580892Issue 08C


Id:0900d80580727d7b

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

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

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

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

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

Copyright © Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN99580892Issue 08C

3


Id:0900d80580727d7b

Table of ContentsThis document has 241 pages.

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Default alarm indication preventions in the system . . . . . . . . . . . . . . . . . 6

2 List of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3 7401 EXTERNAL AL 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4 7402 EXTERNAL AL 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

5 7403 EXTERNAL AL 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

6 7404 EXTERNAL AL 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

7 7405 EXTERNAL AL 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

8 7406 EXTERNAL AL 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

9 7407 EXTERNAL AL 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

10 7408 EXTERNAL AL 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

11 7409 EXTERNAL AL 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

12 7410 EXTERNAL AL 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

13 7411 EXTERNAL AL 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

14 7412 EXTERNAL AL 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

15 7413 EXTERNAL AL 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

16 7414 EXTERNAL AL 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

17 7415 EXTERNAL AL 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

18 7416 EXTERNAL AL 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

19 7417 EXTERNAL AL 17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

20 7418 EXTERNAL AL 18 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

21 7419 EXTERNAL AL 19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

22 7420 EXTERNAL AL 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

23 7421 EXTERNAL AL 21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

24 7422 EXTERNAL AL 22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

25 7423 EXTERNAL AL 23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

26 7424 EXTERNAL AL 24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

27 7425 EXTERNAL AL 25 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

28 7650 BASE STATION FAULTY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

29 7651 BASE STATION OPERATION DEGRADED . . . . . . . . . . . . . . . . 63

30 7652 BASE STATION NOTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . 103

4 DN99580892Issue 08C


Id:0900d80580727d7b

31 7653 CELL FAULTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

32 7654 CELL OPERATION DEGRADED . . . . . . . . . . . . . . . . . . . . . . . . 147

33 7655 CELL NOTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

34 7660 BASE STATION LICENCE EXPIRED . . . . . . . . . . . . . . . . . . . . . 176

35 7661 BASE STATION LICENCE NOTIFICATION . . . . . . . . . . . . . . . . 177

36 7665 BASE STATION TRANSMISSION ALARM . . . . . . . . . . . . . . . . . 179

37 7740 BEATING WCDMA BTS ALARM. . . . . . . . . . . . . . . . . . . . . . . . . 195

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

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

40 7762 RNW DATABASE OPERATION FAILURE . . . . . . . . . . . . . . . . . 206

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

42 7772 HSDPA CONFIGURATION FAILED . . . . . . . . . . . . . . . . . . . . . . 212

43 7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS . .216

44 7776 HSDPA FAILURE IN WCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

45 7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE . . . . . . 220

46 7779 RECOVERY ACTIONS ONGOING . . . . . . . . . . . . . . . . . . . . . . . 222

47 7780 HSUPA FAILURE IN WCEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

48 7781 NETWORK ELEMENT CONFIGURATION ERROR . . . . . . . . . . 226

49 7782 HSUPA CONFIGURATION FAILED . . . . . . . . . . . . . . . . . . . . . . 228

50 7783 IP BASED D-NBAP LINK FAILURE. . . . . . . . . . . . . . . . . . . . . . . 233

51 7784 RECOVERY ACTION FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . 234

52 7786 WCDMA BASE STATION OUT OF USE. . . . . . . . . . . . . . . . . . . 237

53 7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG . . . . . 239

54 7799 RNC RADIO NETWORK TEST ALARM . . . . . . . . . . . . . . . . . . . 241

DN99580892Issue 08C

5

RNC Base Station Alarms (7000-7900) Summary of Changes

Id:0900d80580727d78

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

Changes made between issues 08B and 08C

Modified alarms

Changes made between issues 08A and 08B

New alarms

Modified alarms

Note that the issue numbering system is changing. For more information, see Guide to WCDMA RAN operating documentation.

Changes made between issues 8-0 and 08A

New alarms

Modified alarms

7795

7795

7650 7653 7660 7772

7651 7654 7661 7782

7652 7655 7665

7786

7784

6 DN99580892Issue 08C


Id:0900d80580727d78

Default alarm indication preventions in the system

1 Default alarm indication preventions in the systemAlarm indication preventions for certain alarms have been set by default in RNC. This has been done to reduce the amount of alarm indications that RNC reports to NetAct. The list of alarms below shows the affected alarms that are indication-prevented by default in RNC.

The alarms 7775 and 7795 are indication prevented in RNC because alarm 3325 informs about WCEL parameter inconsistencies in RNC level. For more information, see the instructions given for alarms 7775, 7795, and 3325. Alarm 7799 is an old test alarm for RNC testing purposes which is not set by RNC in any situation anymore.

Base Station Alarms

• 7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS • 7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG • 7799 RNC RADIO NETWORK TEST ALARM

DN99580892Issue 08C

7

RNC Base Station Alarms (7000-7900) List of Alarms

Id:0900d80580727d78

2 List of Alarms7401 EXTERNAL AL 1

7402 EXTERNAL AL 2

7403 EXTERNAL AL 3

7404 EXTERNAL AL 4

7405 EXTERNAL AL 5

7406 EXTERNAL AL 6

7407 EXTERNAL AL 7

7408 EXTERNAL AL 8

7409 EXTERNAL AL 9

7410 EXTERNAL AL 10

7411 EXTERNAL AL 11

7412 EXTERNAL AL 12

7413 EXTERNAL AL 13

7414 EXTERNAL AL 14

7415 EXTERNAL AL 15

7416 EXTERNAL AL 16

7417 EXTERNAL AL 17

7418 EXTERNAL AL 18

7419 EXTERNAL AL 19

7420 EXTERNAL AL 20

7421 EXTERNAL AL 21

7422 EXTERNAL AL 22

7423 EXTERNAL AL 23

7424 EXTERNAL AL 24

7425 EXTERNAL AL 25

7650 BASE STATION FAULTY

7651 BASE STATION OPERATION DEGRADED

7652 BASE STATION NOTIFICATION

7653 CELL FAULTY

7654 CELL OPERATION DEGRADED

7655 CELL NOTIFICATION

7660 BASE STATION LICENCE EXPIRED

7661 BASE STATION LICENCE NOTIFICATION

7665 BASE STATION TRANSMISSION ALARM

7740 BEATING WCDMA BTS ALARM

7750 FAILURE IN WCDMA WBTS O&M CONNECTION

7761 RNW O&M SCENARIO FAILURE

8 DN99580892Issue 08C


Id:0900d80580727d78

List of Alarms

7762 RNW DATABASE OPERATION FAILURE

7771 WCDMA CELL OUT OF USE

7772 HSDPA CONFIGURATION FAILED

7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS

7776 HSDPA FAILURE IN WCEL

7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE

7779 RECOVERY ACTIONS ONGOING

7780 HSUPA FAILURE IN WCEL

7781 NETWORK ELEMENT CONFIGURATION ERROR

7782 HSUPA CONFIGURATION FAILED

7783 IP BASED D-NBAP LINK FAILURE

7784 RECOVERY ACTION FAILURE

7786 WCDMA BASE STATION OUT OF USE

7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG

7799 RNC RADIO NETWORK TEST ALARM

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

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

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

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





DN99580892Issue 08C

9


Id:0900d80580727d78














10 DN99580892Issue 08C


Id:0900d80580727d78

List of Alarms








7650 BASE STATION FAULTY *** 3 00:10 - 00:10 - EVENT TYPE: QUALITY OF SERVICE

7651 BASE STATION OPERATION DEGRADED ** 5 00:10 - 00:10 - EVENT TYPE: QUALITY OF SERVICE

7652 BASE STATION NOTIFICATION * NONE 00:10 - 00:10 - EVENT TYPE: QUALITY OF SERVICE

7653 CELL FAULTY *** 3 00:10 - 00:10 - EVENT TYPE: QUALITY OF SERVICE

7654 CELL OPERATION DEGRADED ** 5 00:10 - 00:10 - EVENT TYPE: QUALITY OF SERVICE

7655 CELL NOTIFICATION * NONE 00:10 - 00:10 -

DN99580892Issue 08C

11


Id:0900d80580727d78

EVENT TYPE: QUALITY OF SERVICE

7660 BASE STATION LICENCE EXPIRED *** 3 00:10 - 00:10 - EVENT TYPE: QUALITY OF SERVICE

7661 BASE STATION LICENCE NOTIFICATION * NONE 00:10 - 00:10 - EVENT TYPE: QUALITY OF SERVICE

7665 BASE STATION TRANSMISSION ALARM * NONE 00:10 - 00:10 - EVENT TYPE: QUALITY OF SERVICE

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

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

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

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

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

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

7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS * NONE 00:00 - 00:00 - EVENT TYPE: PROCESSING ERROR

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

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

7779 RECOVERY ACTIONS ONGOING * NONE

12 DN99580892Issue 08C


Id:0900d80580727d78

List of Alarms

00:00 - 00:00 - EVENT TYPE: QUALITY OF SERVICE

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

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

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

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

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

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

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

7799 RNC RADIO NETWORK TEST ALARM * NONE 00:10 - 00:10 - EVENT TYPE: ENVIRONMENTAL

DN99580892Issue 08C

13

RNC Base Station Alarms (7000-7900) 7401 EXTERNAL AL 1

Id:0900d80580727d78

3 7401 EXTERNAL AL 1Meaning

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

Supplementary information fields

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

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

14 DN99580892Issue 08C


Id:0900d80580727d78

7402 EXTERNAL AL 2


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




DN99580892Issue 08C

15


Id:0900d80580727d78






16 DN99580892Issue 08C


Id:0900d80580727d78

7404 EXTERNAL AL 4






DN99580892Issue 08C

17


Id:0900d80580727d78






18 DN99580892Issue 08C


Id:0900d80580727d78

7406 EXTERNAL AL 6






DN99580892Issue 08C

19


Id:0900d80580727d78






20 DN99580892Issue 08C


Id:0900d80580727d78

7408 EXTERNAL AL 8






DN99580892Issue 08C

21


Id:0900d80580727d78






22 DN99580892Issue 08C


Id:0900d80580727d78

7410 EXTERNAL AL 10






DN99580892Issue 08C

23


Id:0900d80580727d78






24 DN99580892Issue 08C


Id:0900d80580727d78

7412 EXTERNAL AL 12






DN99580892Issue 08C

25


Id:0900d80580727d78






26 DN99580892Issue 08C


Id:0900d80580727d78

7414 EXTERNAL AL 14






DN99580892Issue 08C

27


Id:0900d80580727d78






28 DN99580892Issue 08C


Id:0900d80580727d78

7416 EXTERNAL AL 16






DN99580892Issue 08C

29


Id:0900d80580727d78






30 DN99580892Issue 08C


Id:0900d80580727d78

7418 EXTERNAL AL 18






DN99580892Issue 08C

31


Id:0900d80580727d78






32 DN99580892Issue 08C


Id:0900d80580727d78

7420 EXTERNAL AL 20






DN99580892Issue 08C

33


Id:0900d80580727d78






34 DN99580892Issue 08C


Id:0900d80580727d78

7422 EXTERNAL AL 22






DN99580892Issue 08C

35


Id:0900d80580727d78






36 DN99580892Issue 08C


Id:0900d80580727d78

7424 EXTERNAL AL 24






DN99580892Issue 08C

37


Id:0900d80580727d78






38 DN99580892Issue 08C


Id:0900d80580727d78


28 7650 BASE STATION FAULTYMeaning

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

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

The effect of the fault on the functioning of the network elementdepends on the fault description. For more information, see basestation fault descriptions in WCDMA RAN and I-HSPA System Libraries.

Supplementary information fields1 rack (cabinet) number

2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number

For more information, see instructions on Alarm Structure.

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

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

Below is the list of BTS fault(s) which may have caused this alarm inBTS WN6.0 release. In case of earlier SW release and in case you needmore detailed fault descriptions refer to WCDMA RAN and I-HSPA SystemLibraries. The BTS fault descriptions are also included in BTS SW releasedocumentation. If that does not help, contact your local Nokia SiemensNetworks representative.

DN99580892Issue 08C

39

RNC Base Station Alarms (7000-7900) 7650 BASE STATION FAULTY

Id:0900d80580727d78

FAULT NAME : ATM faultyMEANING : A WAM internal failure.INSTRUCTIONS : 1. If ping to the BTS is working, restart the BTS remotely.

2. Ping the BTS. If it is not working but ping to the AXC is working, then restart the AXC remotely so that the BTS is also restarted automatically.

3. Ping the AXC. If it is not working, visit the site and restart the BTS. If this does not help, replace the alarming WAM unit.

FAULT NAME : ATM processor faultyMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode:

There is a fault in the WAM processor SFN interrupt or the SFN is not being updated in the WSPC MCU.

There is a MCU failure in the WAM or the ATM loop test at start-up has failed.

FlexiBTS:

There is such a fault in the FSM that the SFN is not being updated in the FSP MCU.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

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

2. Ping the BTS. If it is not working but ping to the AXC is working, restart the AXC remotely so that the BTS is also automatically restarted.


FlexiBTS:

1. Reset the BTS.

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

FAULT NAME : Antenna link is downMEANING : Antenna (RP3) link is down: transmitter or receiver drops from synchronization.INSTRUCTIONS : FlexiBTS:

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

40 DN99580892Issue 08C


Id:0900d80580727d78


Module (FSM1), restart BTS.

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

UltraSite/EUBB:

1. If the alarming module is WSMF, restart it. If the alarming module is WSMF, restart BTS.

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

FAULT NAME : BB bus message collision errorMEANING : Routed RF baseband bus messages have collided and the data in the output baseband internal link is lost because the baseband bus is incorrectly configured.INSTRUCTIONS : 1. Check antenna mapping to the local cells in the commissioning file.

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

3. Replace the alarming module.

FAULT NAME : BB bus reception errorMEANING : The master frame in the received RF BB frame is not in the correct place related to the internally generated master frame pulse. Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.

2. If all FSPs generate this alarm, the FSM is faulty.

3. Block/unblock the FSM.

4. If that does not help, replace the faulty module (System Module).

FAULT NAME : BB bus reception error (summing device)MEANING : The master frame in the received baseband bus frame is not in the correct place related to the internally generated master frame pulse. Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place.INSTRUCTIONS : FlexiBTS:

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

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

UltraSite/EUBB:

DN99580892Issue 08C

41


Id:0900d80580727d78

1. Replace the unit that causes the alarm (WSMF).

FAULT NAME : BB bus transmission errorMEANING : A decoding error has been detected in the baseband internal link. The data packet is lost or the content is corrupted.

This situation is also triggered when the links do not synchronize with each other.INSTRUCTIONS : FlexiBTS:

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

2. Replace the alarming unit (System Module).

UltraSite/EUBB:

1. Replace the alarming unit (WSMF).

FAULT NAME : BOFU Post failedMEANING : The unit or module has been tested during BTS power-on self test (POST) and a failure has been detected.INSTRUCTIONS : 1. Block/unblock the alarming unit/module.

2. Remove/reinsert the alarming unit/module.

3. Replace the alarming unit/module.

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

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

FAULT NAME : BTS file errorMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: The BTS unit properties data is invalid or missing.

FlexiBTS: The BTS module properties data or optical interface FPGA file is invalid or missing. The FSP MCU SW file is invalid or missing.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode,

42 DN99580892Issue 08C


Id:0900d80580727d78


UltraSite/EUBB:

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

2. Download the SW again.

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

FlexiBTS:



3. Replace the System Module.

FAULT NAME : BTS file errorMEANING : Telecom configuration file(s) are invalid or missing.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:




FlexiBTS:




FAULT NAME : BTS internal SW management problemMEANING : A software update to a unit/module or subassembly has failed, or a corrupted SW file has been detected in FLASH.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

FlexiBTS:

1. Check the other active alarms. If the ROM disk is corrupted, change the alarming module.

DN99580892Issue 08C

43


Id:0900d80580727d78

2. Reset the RF Module and/or System Module, depending on the alarm source: a. Reset the RF Module by blocking/unblocking it. b. Reset the System Module.

3. Update and activate the SW to the BTS.

4. Check the SW files.


UltraSite/EUBB:

1. Check the other active alarms. If the ROM disk is corrupted, change the alarming unit.

2. Reset the alarming unit.



5. Replace the alarming unit.

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

FlexiBTS:

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

2. Check the cables between the System Module and RF Module/Extension System Module.

3. Reset the RF Module and/or System Module, depending on the alarm source: a. Reset the RF Module by blocking/unblocking it. b. Reset the Extension System Module by blocking/unblocking it. c. Reset the master System Module.

4. Replace the alarming RF Module/Extension System Module.

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

44 DN99580892Issue 08C


Id:0900d80580727d78


situation, replace the alarming master System Module.

UltraSite/EUBB:



3. Check the cables in backplane.


FAULT NAME : Baseband bus configuration of <x> was rejectedMEANING : The baseband bus related configuration of <x> was rejected by the HW, SW, DSP or LTX.INSTRUCTIONS : Replace the alarming module.

FAULT NAME : Baseband reference clock missing (WCI)MEANING : The WCI does not deliver the Baseband Reference Clock (BRCLK) for the relevant units, because either the transceiver circuit in the WSC or the bus is faulty, or the WSC does not distribute the clock source.INSTRUCTIONS : You have two alternative procedures:

1. If there is only one clock unit in the cabinet, replace the WSC.

2. If Step 1 does not help, replace the WCI.

OR

1. If there are two clock units in the cabinet, replace the WCI.

2. If Step 1 does not help, replace both WSC units.

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

FAULT NAME : Commissioning error: <x>MEANING : Some of the commissioning parameters are either missing or faulty, or there is a mismatch between them.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

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

2. Load the correct commissioning file to the BTS.

DN99580892Issue 08C

45


Id:0900d80580727d78

FAULT NAME : Communication failureMEANING : Communication with the application <x> failed. It has not replied to the message that has been sent/resent to it.

FSP: Faraday has not sent a specific mandatory indication message in the start-up during the time limit the message is expected to arrive.INSTRUCTIONS : 1. Check that the unit/module is properly connected. If the unit/module LED does not light up, the unit/module is faulty. Check the alarming unit/module.

2. Check the fault history.

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


FAULT NAME : Communication failure inside WSPMEANING : An internal communication failure between the DSP processors.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

1. Block the alarming WSP.

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

Otherwise, check for other alarms. If the " autonomous reset as recovery action" alarm has occurred for the alarming WSP, replace the alarming WSP unit.

FlexiBTS:

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




FAULT NAME : Configuration error: <x>MEANING : There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch between the BTS configuration and the RNC/I-HSPA adapter parameters.

46 DN99580892Issue 08C


Id:0900d80580727d78


INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

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

2. Check that the BTS cell parameters from the RNC/I-HSPA adapter match the BTS HW configuration (for example frequency, power).

3. Check the RNC/I-HSPA adapter alarms for the alarming local cell (LCR).

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

FAULT NAME : Configuration file is not supportedMEANING : BTS software does not support the commissioning file downloaded to the BTS.INSTRUCTIONS : 1. Check and correct the contents of the commissioning file.

2. Download the corrected commissioning file to the BTS and reset it.

FAULT NAME : Connection to transmission brokenMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode:

The AXC is missing, data or states are corrupted in the ATM, or there are possible hardware or transmission related failures.

FlexiBTS:

Data or states are corrupted in the ATM, or there are possible hardware or transmission related failures.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

1. Check the transmission connections.

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

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

FlexiBTS:


2. Reset the site.

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

DN99580892Issue 08C

47


Id:0900d80580727d78

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


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

FAULT NAME : DSP accelerator initialization failureMEANING : There is a signal processing (DSP) related malfunction in the BTS. This may affect the signal processor receiver functionality processed by the alarming unit/module.INSTRUCTIONS : FlexiBTS:

1. If the alarming module is the Extension System Module (FSM2), restart it. If the alarming module is the System Module (FSM1), restart the BTS.


UltraSite/EUBB:

1. If the alarming unit is WSPF, restart it. If all WSPFs generate this alarm, restart the BTS.


Restart can be done by BTS block/unblock, system module block/unblock from BTS SEM and from NetAct to reset BTS.

FAULT NAME : DSP failure in radiolink creationMEANING : Radio link creation has failed repeatedly because of the DSP rejection.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:

1. Block/unblock the alarming unit.


FlexiBTS:

48 DN99580892Issue 08C


Id:0900d80580727d78


If the faulty FSP is in the extension module, block/unblock the extension module, otherwise block/unblock the BTS.

FAULT NAME : Downlink data buffer synchronization failureMEANING : The downlink data buffer has lost synchronization.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.




FAULT NAME : FSP/WSP Frame synchronisation failedMEANING : The frame synchronization burst, SFN or SFCLK signal from the FCM/WSPF is missing.INSTRUCTIONS : 1. Reset the site.

2. If that does not help, replace the System Module.

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


2. Check the cables between the System Module and RF Module/Extension System Module. Note that dirty optical connectors may cause the signal level to drop too low.

3. Depending on the alarm source, reset the RF Module, Extension System Module and/or System Module by blocking/unblocking it.

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


6. If the System Module is the only alarming source or replacing the RF Module/Extension System Module does not clear the fault situation, replace the alarming System Module.

FAULT NAME : Fatal OSE Error

DN99580892Issue 08C

49


Id:0900d80580727d78

MEANING : The operating system (OSE) goes into the error handler with a fatal status. The cause can be, for example, out of memory situation.

If only one FSP in BTS generates this fault, there is malfunction in one of the FSP submodules. If all FSPs generate this fault, there is malfunction in the FSM.INSTRUCTIONS : FlexiBTS:

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

1. Reset the System Module.


UltraSite/EUBB:

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

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

3. Block/unblock BTS.

4. If that does not help, replace the faulty module.

FAULT NAME : Fault between WAM and WSP SFN (WSP)MEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: Synchronization between the WAM and WSP is lost.

FlexiBTS: Synchronization between the FCM and FSP is lost.

UltraSite/EUBB: Synchronization between the WAMF and WSPF is lost.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

1. If only one WSP in the cabinet generates this alarm, the WSP is faulty.

2. If all WSPs in a subrack generate this alarm, the WAM is faulty.

3. If all WSPs generate this alarm, the WSC/WMC is faulty.

Otherwise, check for other alarms. If the " autonomous reset as a recovery action" alarm has occurred for the faulty WSP, replace the faulty WSP unit.

FlexiBTS:

50 DN99580892Issue 08C


Id:0900d80580727d78


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




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

2. If all WSPFs generate this alarm, the BTS is faulty.

3. Block/unblock the BTS.


FAULT NAME : Fault in ATM interfaceMEANING : The WAM ATM interface is not responding correctly.INSTRUCTIONS : 1. Block/unblock the alarming unit. This resets the BTS.


FAULT NAME : Fault in ATM interfaceMEANING : WAM ATM interface, AXC or CIF bus failure. The AXC may have been reset.

WAM processor failure.INSTRUCTIONS : 1. Block/unblock the alarming unit. This will reset the BTS.

2. Swap the WAM units between subracks and check if the alarm follows the unit. Replace the alarming WAM unit.

3. Check the AXU.

4. Check the backplane connection between the WAM and AXU.

FAULT NAME : Fault in O&M and DSP SW interfaceMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: Communication failure between the WAM and DSP.

FlexiBTS: Communication failure between the FCM and FSP.

UltraSite/EUBB: Communication failure between the WSMF and WSPF.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:

DN99580892Issue 08C

51


Id:0900d80580727d78



FlexiBTS:

1. Block/unblock the alarming module.


FAULT NAME : Frame Synchronization failureMEANING : The frame clock receiver has lost its synchronization. The FSM internal frame clock is not synchronized with the FSM 100 Hz frame clock.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.




FAULT NAME : Frame clock deviation faultMEANING : Synchronization to the clock control unit frame pulse has been achieved earlier but it differs from the currently received frame pulse. The internally generated frame clock might have drifted.INSTRUCTIONS : FlexiBTS:


2. Reset the alarming System Module.

3. Replace the alarming System Module.

UltraSite/EUBB:

1. Reset the alarming WSMF.

2. Replace the alarming WSMF.

FAULT NAME : Frame number synchronization error in optical interfaceMEANING : The timing of the new RP1 synchronization burst deviates from the present RP1 timing maintained in the BTS.INSTRUCTIONS : 1. Reset the System Module that causes the alarm.

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

52 DN99580892Issue 08C


Id:0900d80580727d78


FAULT NAME : Incompatible SW version detectedMEANING : A new unit with an incompatible SW has probably been inserted in the BTS.INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version, and update the active SW version), unless it is automatically updated by NetAct.

Related BTS - AXC interface: check the SW version of the BTS and AXC, and update compatible SW to the AXC or BTS.

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

FAULT NAME : Internal MTU configuration failureMEANING : Internal Maximum Transfer Unit (MTU) configuration failed on FCM or FSP.INSTRUCTIONS : 1. Reset the alarming System Module.

2. Replace the alarming System Module

FAULT NAME : Invalid Configuration fileMEANING : The commissioning file is missing, or an incorrect commissioning file has been detected during BTS startup as follows: "Validation failed due to wrong BTS ID" or "Validation failed due to incompatible data"INSTRUCTIONS : 1. Check and correct the contents of the commissioning file.

2. Recommission the BTS with the valid commissioning file.

FAULT NAME : Master unit has lost connection to the slave unitMEANING : O&M SW has not received a reply to the requested node polling from SW platform.INSTRUCTIONS : 1. Reset BTS.

2. Replace the faulty module.

FAULT NAME : No baseband capacity for common channelsMEANING : There is not enough common channel capacity to set up any cells to the BTS, because Efficient Baseband or Full Baseband HSDPA is allocated (last WSP/FSP/Faraday card is fully reserved).INSTRUCTIONS : None

FAULT NAME : No connection to AXUMEANING : The master WAM detected that the AXU does not respond to polling messages.INSTRUCTIONS : 1. Check for alarms on the AXC.

DN99580892Issue 08C

53


Id:0900d80580727d78

2. Restart the AXC remotely. This will also cause a BTS restart.

3. Change the alarming AXC unit.

FAULT NAME : No connection to BTS transport submoduleMEANING : The connection to the BTS transport submodule is lost.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

1. Reset the site.

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

FAULT NAME : No connection to unitMEANING : The connection to a unit that belongs to the BTS configuration has been lost.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:

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

2. If SW updates have been done recently, reload the SW.

3. If the WAF or WIC is alarming, try recommissioning the site.

4. Check that the unit is properly connected. If the unit LED does not light up, the unit is faulty. The fault might also be in the WPS unit or backplane.

5. Check the power cables and connectors as well as the I2C bus cables.

Cancel alarms: Removing and inserting the WIC, WSM or primary WAM causes a site reset. If both WSCs are removed, inserting the first removed WSC back into the cabinet causes a site reset.

If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First try to reset the site with the software. If that does not help, replace the alarming unit.

FlexiBTS:

1. Check that the module is properly connected. If the module LED does not light up, the module is faulty. Check the alarming module.

54 DN99580892Issue 08C


Id:0900d80580727d78


2. Check the alarm history.

FAULT NAME : Not able to synchronize baseband bus with <x>MEANING : The baseband bus synchronization towards <x> failed.INSTRUCTIONS : Replace the alarming module.

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

2. Replace the FSM.

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

FAULT NAME : Oven oscillator Missing PulseMEANING : The output signal of the OXCO has some problems and one or more clock pulses are missed.INSTRUCTIONS : 1. Block/unblock the FSM.

2. Replace the FSM.

FAULT NAME : Oven oscillator clock missingMEANING : The WSC is not able to deliver the clock signals required by the other units.INSTRUCTIONS : Replace the clock unit.

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

2. Replace the FSM.

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

FAULT NAME : PLL status not lockedMEANING : BTS monitors the FSP/WSPF/WSMF PLL lock status and PLL locking fails.INSTRUCTIONS : FlexiBTS:

DN99580892Issue 08C

55


Id:0900d80580727d78


2. Replace the FSM.

UltraSite/EUBB:

1. Block/unblock the WSMF.

2. Replace the WSMF.

3. Blocking/unblocking WSPF and replacing WSPF.

FAULT NAME : POST test failedMEANING : The unit or module has been tested during the BTS power-on self test (POST) and a failure has been detected.INSTRUCTIONS : 1. Block/unblock the alarming unit/module.



FAULT NAME : Power unit output voltage faultMEANING : The output voltage is too low or too high.

Usually the reason for the fault is the unit itself but in some cases the reason can be the unit that the WPS feeds.

If a short circuit occurs in the fed unit, it may affect the WPS and the "Output Voltage Fault" alarm is generated.INSTRUCTIONS : 1. Check the other active alarms.

2. Check the units that are supplied by the alarming WPS.

3. Check the backplane connectors and cables.

4. Replace the alarming WPS unit.

FAULT NAME : R-bus errorMEANING : 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

56 DN99580892Issue 08C


Id:0900d80580727d78


alarm is a faulty WSM/WMC or WSP.

3. Run a WCDMA BTS loop test to locate the faulty unit.

4. If the WSP is faulty, block/unblock it.

5. Replace the faulty unit.

FlexiBTS:

1. Check the cabling between the System Module and RF Module.

2. Check the active RF Module alarms and act accordingly.

3. Replace the faulty module (System Module).

FAULT NAME : RP1 synchronization burst errorMEANING : A new RP1 Frame Clock Burst (FCB) burst/message has been received from the RP3-01 interface while processing the previous burst/message.INSTRUCTIONS : 1. Reset the alarming Extension System Module by blocking/unblocking it.

2. If that does not clear the fault situation, replace the alarming Extension System Module.

3. If the System Module is the only alarming source or replacing the Extension System Module does not clear the fault situation, replace the alarming System Module.

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




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

FAULT NAME : SW does not support commissioning fileMEANING : The software does not support the new commissioning file loaded to the BTS.

DN99580892Issue 08C

57


Id:0900d80580727d78

INSTRUCTIONS : 1. Check and correct the contents of the commissioning file. Load the correct commissioning file to the BTS.

2. Update the BTS SW.

FAULT NAME : Starting temperature below minimumMEANING : BTS cannot start properly, because FSPs cannot be powered up at too cold conditions.INSTRUCTIONS : 1. Wait until the module is automatically heated to the required start-up temperature.

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

FAULT NAME : Summing service release from reset failedMEANING : Summing service release from reset failed.INSTRUCTIONS : 1. Reset the System Module.

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

FAULT NAME : Synchronization failureMEANING : The frame burst phase has moved compared to the internal counter. The FSM has already found the frame synchronization but the FSM frame clock does not match the FSM internal frame clock.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.




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

FAULT NAME : System Module failureMEANING : The FlexiBTS has detected an abnormal operation or a failure in the internal functionality of the System Module.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

58 DN99580892Issue 08C


Id:0900d80580727d78




FAULT NAME : TRANSU synchronization errorMEANING : The RP3 TX/RX state machine or the T-bus receiver has changed its state. The synchronization is lost or the T-bus receiver has not synchronized.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.




FAULT NAME : Tbus receiver parity faultMEANING : Data or synchronization failure in the System Module, two antenna carriers are affected.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.




FAULT NAME : Telecom configuration failureMEANING : Telecom slave configurations or registrations failure. Unit RNW configuration failure. Telecom RNW reconfiguration failure.

Or

UltraSite, MetroSite, MetroSite 50, Triple-mode: WSP unit to WAM allocation failure.

FlexiBTS: - FSP unit to FCM allocation failure. - Faraday unit to FSP allocation failure.

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

Block/unblock the alarming unit. If there was an internal failure, the unit needs to be blocked/unblocked to get it

DN99580892Issue 08C

59


Id:0900d80580727d78

initialized/configured again.

FlexiBTS:

If there was an internal failure, in the case of an FR, the module needs to be blocked/unblocked to get it initialized/configured again.

FAULT NAME : Temperature alarmMEANING : The internal temperature of the RF Module or System Module exceeds the threshold value, or the ambient temperature of the module(s) is outside the specified limits.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

1. Check the other BTS alarms and act accordingly.

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

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


FAULT NAME : Unit SW download failedMEANING : The software update to the unit or subunit has failed.INSTRUCTIONS : 1. Download the BTS SW again.

2. FCM: Reset the BTS.

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

FAULT NAME : Unit SW download failedMEANING : Software update to the unit or subunit has failed. The fault can also be caused by disconnected CIF bus cables.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:

1. Block/unblock the WSP.

2. If Step 1 does not help, replace the alarming unit.

OR

1. WAM, WPA: Reset the BTS.


60 DN99580892Issue 08C


Id:0900d80580727d78


OR

1. Download the BTS SW again.

FlexiBTS:




FAULT NAME : Unit Synchronization failedMEANING : WSMF synchronization has failed.INSTRUCTIONS : 1. Block/unblock BTS. 2. Replace the alarming unit.

FAULT NAME : Unit initialization failureMEANING : A unit or an IP address initialisation has failed.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:


2. Check if the non-commissioned WAM is the Master WAM. If so, this alarm causes the alarm. Check the alarm history to know why the WAMs' switchover occurred.

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

FlexiBTS:

1. Block/unblock the alarming unit. If that does not help, replace the alarming 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.


FAULT NAME : Unit not supported by current BTS SW versionMEANING : 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

DN99580892Issue 08C

61


Id:0900d80580727d78

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

FAULT NAME : Unit synchronization failedMEANING : The WAM/WSPC synchronization has failed.INSTRUCTIONS : 1. Block/unblock the alarming unit.


FAULT NAME : Unknown HW resourceMEANING : A unit cannot be identified by its product code or by its physical device address (object ID).INSTRUCTIONS : Replace the alarming unit/module.

FAULT NAME : Unknown product codeMEANING : A module cannot be identified by its product code but is known by its physical device address (object_ID).INSTRUCTIONS : Replace the alarming module.

FAULT NAME : Uplink data buffer synchronization failureMEANING : The uplink data buffer loses synchronization.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.




FAULT NAME : WAM internal errorMEANING : The Telecom SW does not communicate with the ATM SW because of a fault.INSTRUCTIONS : N/A

FAULT NAME : WCI baseband reference clock failureMEANING : The master or redundant WSC does not generate Baseband Reference Clock (BRCLK) to the WCI because of an internal failure or a clock driver failure in the WSC unit.INSTRUCTIONS : 1. Block/unblock the active WSC unit.

2. Replace the WCI unit.

3. Replace both WSC units.

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

FAULT NAME : WSM failure

62 DN99580892Issue 08C


Id:0900d80580727d78


MEANING : The BTS has detected an abnormal operation or a failure in the internal functionality of the WSMF unit.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.


2. Check that the unit is properly connected. If the unit LED does not light up, the unit is faulty.

3. Reset the BTS.


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

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


DN99580892Issue 08C

63

RNC Base Station Alarms (7000-7900) 7651 BASE STATION OPERATION DEGRADED

Id:0900d80580727d78

29 7651 BASE STATION OPERATION DEGRADEDMeaning

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

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



2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number





64 DN99580892Issue 08C


Id:0900d80580727d78


FAULT NAME : 10b8b coding error in Optical Interface device <opt link/RP3>MEANING : The fibre cable has an interference; the data becomes faulty.

A physical connection failure between the optical interface and the summing function (caused by bad circuit joints, for example).INSTRUCTIONS : 1. Reset the RF Module behind the faulty optical interface by blocking/unblocking it.

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

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

FAULT NAME : 2M external reference missingMEANING : The reference clock monitoring has detected a loss of 2.048MHz signal received from an external reference source, connected to Sync In interface of the System Module.INSTRUCTIONS : Note! Perform the steps below in the listed order until the alarm disappears.

1. Check the cabling (connected to Sync In interface).

2. Check that the 2.048MHz reference source is working normally and the 2.048MHz signal is available.


FAULT NAME : ATM faultyMEANING : A WAM internal failure.INSTRUCTIONS : 1. If ping to the BTS is working, restart the BTS remotely.

2. Ping the BTS. If it is not working but ping to the AXC is working, then restart the AXC remotely so that the BTS is also restarted automatically.


FAULT NAME : ATM processor faultyMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode:

There is a fault in the WAM processor SFN interrupt or the SFN is not being updated in the WSPC MCU.

There is a MCU failure in the WAM or the ATM loop test at

DN99580892Issue 08C

65


Id:0900d80580727d78

start-up has failed.

FlexiBTS:

There is such a fault in the FSM that the SFN is not being updated in the FSP MCU.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

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

2. Ping the BTS. If it is not working but ping to the AXC is working, restart the AXC remotely so that the BTS is also automatically restarted.


FlexiBTS:

1. Reset the BTS.

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

FAULT NAME : ATM traffic overloadMEANING : There is a buffer overflow caused by a traffic overload. The maximum capacity is exceeded and some data is discarded.INSTRUCTIONS : 1. Check that bandwidths (cells/s) are the same at the BTS, AXC and RNC.

2. Check the data integrity from the incoming Iub (see Troubleshooting instructions).

3. Check the other transmission elements' active alarms (see the Alarms for AXC document).

FAULT NAME : Active clock tuning faultMEANING : The phase measurement cannot be performed in the active WSC or WMC.INSTRUCTIONS : 1. Run fast tuning with BTS Site Manager.



Note that because of a fault situation in the active clock, the redundant clock is not tuned. To make sure that the tuning is correct, run "Fast Tune BTS Clock" with BTS Site Manager after the switchover when the new WSC is taken into use. If there is a WMC or only one WSC, the tuning continues but the cells remain disabled.

66 DN99580892Issue 08C


Id:0900d80580727d78


FAULT NAME : Address mismatch in summingMEANING : There is a baseband bus address mismatch in the summing. There are two possible causes:

A configuration error (two different baseband units functioning) - after an acknowledgement the fault returns again.

Data corruption on the bus - appears once when unsynchronized data is sent by the baseband.INSTRUCTIONS : Check the antenna mapping to the local cells in the commissioning file.

FAULT NAME : Antenna link is downMEANING : Antenna (RP3) link is down: transmitter or receiver drops from synchronization.INSTRUCTIONS : FlexiBTS:

1. If the alarming module is the Extension System Module (FSM2), restart it. If the alarming module is the System Module (FSM1), restart BTS.


UltraSite/EUBB:

1. If the alarming module is WSMF, restart it. If the alarming module is WSMF, restart BTS.

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

FAULT NAME : BB bus reception errorMEANING : The master frame in the received RF BB frame is not in the correct place related to the internally generated master frame pulse. Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.




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

DN99580892Issue 08C

67


Id:0900d80580727d78

place (PI delay) or the data itself is in the wrong place.INSTRUCTIONS : FlexiBTS:



UltraSite/EUBB:


FAULT NAME : BB bus transmission errorMEANING : A decoding error has been detected in the baseband internal link. The data packet is lost or the content is corrupted.

This situation is also triggered when the links do not synchronize with each other.INSTRUCTIONS : FlexiBTS:

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

2. Replace the alarming unit (System Module).

UltraSite/EUBB:

1. Replace the alarming unit (WSMF).

FAULT NAME : BOFU Post failedMEANING : The unit or module has been tested during BTS power-on self test (POST) and a failure has been detected.INSTRUCTIONS : 1. Block/unblock the alarming unit/module.



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

2. If other flash memory-related alarms are active for the alarming unit at the same time, replace the alarming unit.

FAULT NAME : BTS Master Clock tuning failureMEANING : The OCXO adjustment area is reaching its limit value. The DAC word value of the OCXO is lower than 205 or greater than 3891

68 DN99580892Issue 08C


Id:0900d80580727d78


(5 of the total adjustment area). The range for the DAC word is 0 - 4095.INSTRUCTIONS : 1. Start the fast tuning with BTS Site Manager.

2. Check the reference signal from the FTM.

3. Reset the site.

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

FAULT NAME : BTS RNC/I-HSPA interface signalling link failureMEANING : An AAL2 signalling link failure. It can be caused by a broken WAM. The most common reason for this alarm is a frequently breaking transmission.INSTRUCTIONS : 1. Check the other transmission elements' active alarms (see the Alarms for AXC document).

2. Check the BTS and RNC transmission settings.

3. Reset the AXC.

4. Change the WAM unit.

Note! The BTS and the AXC can be restarted remotely.

FAULT NAME : BTS RNC/I-HSPA interface signalling link failureMEANING : A common NBAP link failure. It can be caused by a transmission network problem. The most common reason for this alarm is a frequently breaking transmission.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:



3. Reset the AXC.



FlexiBTS:

1. Reset the BTS.

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

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

DN99580892Issue 08C

69


Id:0900d80580727d78


FAULT NAME : BTS RNC/I-HSPA interface signalling link failureMEANING : A dedicated Node-B Application Protocol (NBAP) link failure. It can be caused by the RNC.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:



3. Reset the AXC.



FlexiBTS:

1. Reset the BTS.

2. Check the transmission links to the RNC.




FlexiBTS: The BTS module properties data or optical interface FPGA file is invalid or missing. The FSP MCU SW file is invalid or missing.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:




FlexiBTS:

1. Download two different SW packages so that the faulty file

70 DN99580892Issue 08C


Id:0900d80580727d78


is removed from the BTS.



FAULT NAME : BTS file errorMEANING : Telecom configuration file(s) are invalid or missing.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:




FlexiBTS:





FlexiBTS:






UltraSite/EUBB:

DN99580892Issue 08C

71


Id:0900d80580727d78






FAULT NAME : BTS is uncommissionedMEANING : Commissioning file download has not been started neither from BTS Site Manager nor from NetAct during Autoconfiguration.INSTRUCTIONS : 1. Check that Autoconfiguration is enabled in NetAct.

2. Check the Autoconnection/Autoconfiguration information with BTS Site Manager.

3. Load the correct commissioning file to BTS.

FAULT NAME : BTS reference clock missingMEANING : This alarm is generated if the reference clock monitoring function of the BTS does not receive one, two or all the synchronization reference signal(s).

Background information: There is a fixed synchronization priority list in the FlexiBTS:

-Priority 1: PPS (Pulse Per Second) signal connected to the Synchronization Input interface (Sync In) of the System Module. Normally the PPS signal is generated by the GPS receiver.

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

-Priority 3: the reference coming from the integrated transmission unit (FTM).

Normally, all the sources are not in use at the same time (it depends on the network planning and BTS configuration). The used sources are defined into the BTS configuration during the commissioning phase.

The alarm is not generated if the highest commissioned synchronization source is present, no matter what the lower level source statuses are.INSTRUCTIONS : Depending on the installed and commissioned synchronization

72 DN99580892Issue 08C


Id:0900d80580727d78


source(s) listed in section "Meaning", select the commissioned synchronization option and perform the steps below in the listed order until the alarm disappears.

GPS receiver (PPS source):

1. If there is a GPS receiver commissioned at the BTS site, note the following: If the GPS receiver is not locked to any satellite, it turns off the PPS signal which is normally delivered to the BTS (Sync In interface). The most common reason is that the GPS receiver does not see any satellites because of poor antenna installation (poor sky visibility). For this, the only permanent cure is to change the GPS antenna location. One indication of a fairly poor sky visibility is that the alarm is activated/canceled every now and then.

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

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

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

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

External 2.048MHz signal:

1. If there is an external 2.048MHz signal source commissioned at the BTS site, check the alarms of that device and act accordingly. If this does not help, check the cables. Note that because the device type is not known, detailed instructions cannot be given - refer to the appropriate user manual of the device for further actions.


Iub reference (FTM as source):

1. If there is an integrated transmission unit (FTM) commissioned at the BTS site, note the following: The FTM unit operates so that if it is not locked to a synchronization source, it turns off the clock reference signal which is normally delivered to the BTS master clock. The synchronization source of the FTM (set by the FTM synchronization priority setting) may be missing, causing the FTM's internal clock to drop to holdover mode. In this case,

DN99580892Issue 08C

73


Id:0900d80580727d78

the fault in the transmission NETWORK must be corrected.

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

3. Check the synchronization settings of the FTM unit.


5. There may be an equipment failure in the FTM unit. Check the operation and replace the unit, if needed. Note: Normally the reason is not an equipment fault, but there may be cuts in the Iub interface causing the FTM clock to drop to holdover mode. Especially the alarm activity (frequent alarms/cancels instead of a stable alarm state) points to the instability of the transmission network, not to a fault in the unit.

If the previous steps do not help, there may be an equipment failure in the System Module. Check the operation and if performing a BTS site reset does not help, replace the System Module.


FlexiBTS:





5. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation, replace the alarming master System Module.

UltraSite/EUBB:

74 DN99580892Issue 08C


Id:0900d80580727d78







FAULT NAME : Cabinet door openMEANING : The cabinet door is open or the cabinet door sensor is faulty.INSTRUCTIONS : 1. Ensure that the cabinet doors are properly closed.

2. Check that the door switches function correctly and that they have been adjusted correctly.

Note: this alarm can be enabled or disabled in commissioning.




FAULT NAME : Commissioning parameter mismatchMEANING : A commissioning parameter does not have a valid value (the parameter is missing or it has a value outside the value range) or there are errors in the commissioning file.INSTRUCTIONS : Reconfigure the BTS with Commissioning Wizard.



DN99580892Issue 08C

75


Id:0900d80580727d78


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


FAULT NAME : Communication failure inside WSPMEANING : An internal communication failure between the DSP processors.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

1. Block the alarming WSP.

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

Otherwise, check for other alarms. If the " autonomous reset as recovery action" alarm has occurred for the alarming WSP, replace the alarming WSP unit.

FlexiBTS:

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




FAULT NAME : Configuration error: <x>MEANING : There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. Another possibility is that there is a mismatch between the BTS configuration and the RNC/I-HSPA adapter parameters.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.




76 DN99580892Issue 08C


Id:0900d80580727d78



FAULT NAME : Connection to transmission brokenMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode:

The AXC is missing, data or states are corrupted in the ATM, or there are possible hardware or transmission related failures.

FlexiBTS:

Data or states are corrupted in the ATM, or there are possible hardware or transmission related failures.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:


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


FlexiBTS:


2. Reset the site.

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

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


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

FAULT NAME : DSP accelerator initialization failureMEANING : There is a signal processing (DSP) related malfunction in the BTS. This may affect the signal processor receiver functionality processed by the alarming unit/module.INSTRUCTIONS : FlexiBTS:

DN99580892Issue 08C

77


Id:0900d80580727d78

1. If the alarming module is the Extension System Module (FSM2), restart it. If the alarming module is the System Module (FSM1), restart the BTS.


UltraSite/EUBB:

1. If the alarming unit is WSPF, restart it. If all WSPFs generate this alarm, restart the BTS.


Restart can be done by BTS block/unblock, system module block/unblock from BTS SEM and from NetAct to reset BTS.

FAULT NAME : DSP failure in radiolink creationMEANING : Radio link creation has failed repeatedly because of the DSP rejection.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:



FlexiBTS:

If the faulty FSP is in the extension module, block/unblock the extension module, otherwise block/unblock the BTS.

FAULT NAME : Downlink data buffer synchronization failureMEANING : The downlink data buffer has lost synchronization.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.




FAULT NAME : Error in commissioning dataMEANING : The WTR initialisation parameters are faulty. The error can be caused by a missing parameter in the commissioning file: the cabling information (main, diversity), feeder loss, local cell resources, for example.

78 DN99580892Issue 08C


Id:0900d80580727d78


INSTRUCTIONS : 1. Check that the cell parameters, RX cabling, feeder loss and MHA gain are correct in the commissioning file.

2. Update the information if needed. Reconfiguration commissioning is required for correcting the values.

FAULT NAME : Failure in AXU initializationMEANING : The BTS has lost connection to the AXU or the AXU SW is incompatible. The AXU does not respond to requests from the BTS.INSTRUCTIONS : 1. Check the AXC configuration.

2. Restart the AXC remotely. This will also cause a BTS restart.








FAULT NAME : Faraday core mode change was failedMEANING : Faraday core mode change was failed meaning that Telecom SW did not get the CONFIGURE_CORE_RESP_MSG from BTSOM or in message negative response was indicated from some of the configured cores or information from some of the configured cores was missing.INSTRUCTIONS : Replace the alarming module/unit.

DN99580892Issue 08C

79


Id:0900d80580727d78

FAULT NAME : Fatal OSE ErrorMEANING : The operating system (OSE) goes into the error handler with a fatal status. The cause can be, for example, out of memory situation.

If only one FSP in BTS generates this fault, there is malfunction in one of the FSP submodules. If all FSPs generate this fault, there is malfunction in the FSM.INSTRUCTIONS : FlexiBTS:

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



UltraSite/EUBB:

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

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

3. Block/unblock BTS.


FAULT NAME : Fault between WAM and WSP SFN (WSP)MEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: Synchronization between the WAM and WSP is lost.

FlexiBTS: Synchronization between the FCM and FSP is lost.

UltraSite/EUBB: Synchronization between the WAMF and WSPF is lost.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

1. If only one WSP in the cabinet generates this alarm, the WSP is faulty.

2. If all WSPs in a subrack generate this alarm, the WAM is faulty.

3. If all WSPs generate this alarm, the WSC/WMC is faulty.

Otherwise, check for other alarms. If the " autonomous reset as a recovery action" alarm has occurred for the faulty WSP, replace the faulty WSP unit.

FlexiBTS:

80 DN99580892Issue 08C


Id:0900d80580727d78


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




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

2. If all WSPFs generate this alarm, the BTS is faulty.

3. Block/unblock the BTS.


FAULT NAME : Fault in ATM interfaceMEANING : The WAM ATM interface is not responding correctly.INSTRUCTIONS : 1. Block/unblock the alarming unit. This resets the BTS.


FAULT NAME : Fault in ATM interfaceMEANING : WAM ATM interface, AXC or CIF bus failure. The AXC may have been reset.

WAM processor failure.INSTRUCTIONS : 1. Block/unblock the alarming unit. This will reset the BTS.

2. Swap the WAM units between subracks and check if the alarm follows the unit. Replace the alarming WAM unit.

3. Check the AXU.

4. Check the backplane connection between the WAM and AXU.

FAULT NAME : Fault in O&M and DSP SW interfaceMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: Communication failure between the WAM and DSP.

FlexiBTS: Communication failure between the FCM and FSP.

UltraSite/EUBB: Communication failure between the WSMF and WSPF.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:

DN99580892Issue 08C

81


Id:0900d80580727d78



FlexiBTS:

1. Block/unblock the alarming module.


FAULT NAME : Faulty configuration of system modulesMEANING : There is possibly a faulty configuration with the Radio Modules connected to both the master system module and intented extension system module.INSTRUCTIONS : Remove Radio Modules from the intended extension system module and hot insert them to the intended master system module.

FAULT NAME : Flash operation failureMEANING : A flash memory operation failure. If this alarm continuously appears, the flash chip may be broken.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:


2. Block/unblock the alarming unit. There are no recovery actions and due to that the block/unblock can be tried once. If that does not help, replace the alarming unit.

FlexiBTS:


2. Block/unblock the alarming module. There are no recovery actions and due to that the block/unblock can be tried once. If that does not help, replace the alarming module.

FAULT NAME : Frame Synchronization failureMEANING : The frame clock receiver has lost its synchronization. The FSM internal frame clock is not synchronized with the FSM 100 Hz frame clock.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.



82 DN99580892Issue 08C


Id:0900d80580727d78



FAULT NAME : Frame burst receiving faultMEANING : The optical interface has detected a CRC error in the received synchronization burst from the clock function. This fault appears on the RX side.INSTRUCTIONS : 1. Depending on the alarm source, reset the RF Module and/or Extension System Module by blocking/unblocking it.

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

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

FAULT NAME : Frame clock deviation faultMEANING : Synchronization to the clock control unit frame pulse has been achieved earlier but it differs from the currently received frame pulse. The internally generated frame clock might have drifted.INSTRUCTIONS : FlexiBTS:


2. Reset the alarming System Module.

3. Replace the alarming System Module.

UltraSite/EUBB:

1. Reset the alarming WSMF.

2. Replace the alarming WSMF.



FAULT NAME : Incompatible SW version detectedMEANING : A new unit with an incompatible SW has probably been inserted in the BTS.INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version, and update the active SW version),

DN99580892Issue 08C

83


Id:0900d80580727d78

unless it is automatically updated by NetAct.



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

FAULT NAME : Internal MTU configuration failureMEANING : Internal Maximum Transfer Unit (MTU) configuration failed on FCM or FSP.INSTRUCTIONS : 1. Reset the alarming System Module.

2. Replace the alarming System Module

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

FAULT NAME : Master unit has lost connection to the slave unitMEANING : O&M SW has not received a reply to the requested node polling from SW platform.INSTRUCTIONS : 1. Reset BTS.

2. Replace the faulty module.

FAULT NAME : Missing NBAP Cell parameters, defaults are usedMEANING : One or more cell parameters are missing from the RNC/I-HSPA adapter configuration data and the BTS commissioning file.INSTRUCTIONS : 1. If the parameters are configured to the RNC/I-HSPA adapter, delete and recreate the BTS Object in OMS.

2. Reconfigure the BTS with Commissioning Wizard if the default values for the cell parameters (such as rampdown time/step) are not appropriate.


84 DN99580892Issue 08C


Id:0900d80580727d78









FlexiBTS:



FAULT NAME : No connection to unitMEANING : The connection to a unit belonging to the BTS configuration has been lost.INSTRUCTIONS : 1. Check the alarm history, alarming unit and subrack.



4. Check that the unit is properly connected. If the unit led does not light up, the unit is faulty. The fault may also be in the WPS unit or backplane.


Cancel alarms: Removing and inserting the WIC, WSM or primary WAM causes a site reset. If both WSCs are removed, inserting

DN99580892Issue 08C

85


Id:0900d80580727d78

the first removed WSC back into the cabinet causes a site reset.

If the 7650 BASE STATION FAULTY alarm is issued, reset the site. First try to reset the site by the software. If that does not help, replace the alarming unit.


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

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

2. Increase the number of WSP units in the BTS.

FAULT NAME : Optical Interface Data/Control/Ethernet Buffer FullMEANING : The RP3 or Ethernet buffering is not working and the buffer becomes full. The optical device is malfunctioning. The fault may be generated due to synchronization problems or incorrect initialization.INSTRUCTIONS : Swap the alarming and working links. Then check where the alarm is now reported. If the alarming link remains the same, replace the System Module. If the alarming link changes, replace the RF Module behind that link.

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

2. Replace the FSM.

FAULT NAME : Optical Interface faultyMEANING : The Small Form Factor Pluggable (SFP) malfunction has occured or the SFP module is not physically present (no electrical connection exists). The SFP is a part of the fibre cable package.INSTRUCTIONS : 1. Check that the SFP is properly connected.

86 DN99580892Issue 08C


Id:0900d80580727d78


2. Replace the SFP module.

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

FAULT NAME : Optical interface buffer alarmMEANING : RP3 or Ethernet buffering is not working and the buffer becomes full. The optical device malfunctions. The fault may be generated because of synchronization problems or incorrect initialization.INSTRUCTIONS : 1. Depending on the interface, reset the connected module/unit behind the interface that causes the alarm by blocking/unblocking it.

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

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

UltraSite/EUBB: 3. If WSMF is the only alarm source, or replacing the connected module/unit does not clear the fault situation, replace the WSMF that causes the alarm.

FAULT NAME : Oven oscillator Missing PulseMEANING : The output signal of the OXCO has some problems and one or more clock pulses are missed.INSTRUCTIONS : 1. Block/unblock the FSM.

2. Replace the FSM.

FAULT NAME : Oven oscillator heating failureMEANING : The heating of oven oscillator fails and the unit is broken. The ambient temperature can also be too low or change too fast.INSTRUCTIONS : 1. Check the active fan alarms.

2. Replace the clock unit.

FAULT NAME : PLL status not lockedMEANING : BTS monitors the FSP/WSPF/WSMF PLL lock status and PLL locking fails.INSTRUCTIONS : FlexiBTS:


DN99580892Issue 08C

87


Id:0900d80580727d78

2. Replace the FSM.

UltraSite/EUBB:

1. Block/unblock the WSMF.

2. Replace the WSMF.

3. Blocking/unblocking WSPF and replacing WSPF.

FAULT NAME : POST test failedMEANING : The unit or module has been tested during the BTS power-on self test (POST) and a failure has been detected.INSTRUCTIONS : 1. Block/unblock the alarming unit/module.



FAULT NAME : PPS reference missingMEANING : The reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver.INSTRUCTIONS : 1. Check the GPS receiver installation.

2. Check the GPS receiver status.

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

FAULT NAME : Power unit input voltage faultMEANING : The input voltage of the BTS has decreased.INSTRUCTIONS : 1. Check the other MAINS related active alarms.

2. Check the power supply voltage. If it is OK, replace the power cable.

3. Check the power unit.

FAULT NAME : Power unit output voltage faultMEANING : The output voltage is too low or too high.

Usually the reason for the fault is the unit itself but in some cases the reason can be the unit that the WPS feeds.

If a short circuit occurs in the fed unit, it may affect the WPS and the "Output Voltage Fault" alarm is generated.INSTRUCTIONS : 1. Check the other active alarms.

2. Check the units that are supplied by the alarming WPS.

3. Check the backplane connectors and cables.

88 DN99580892Issue 08C


Id:0900d80580727d78


4. Replace the alarming WPS unit.




2. If there are no active WSM/WMC alarms, the reason for the alarm is a faulty WSM/WMC or WSP.




FlexiBTS:




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




FAULT NAME : SFN synchronization failureMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode: The WSP is not synchronized with the WAM.

FlexiBTS: The FSP is not synchronized with the FCM.

DN99580892Issue 08C

89


Id:0900d80580727d78

UltraSite/EUBB: The WSPF is not synchronized with WSMF.INSTRUCTIONS : 1. Block/unblock the alarming unit.


FAULT NAME : SFN synchronization failureMEANING : There is a WAM internal synchronization failure.INSTRUCTIONS : 1. Check and correct the ATM configuration.

2. Replace the WAM.

FAULT NAME : SFN synchronization failureMEANING : The slave WAM is not synchronised with the master WAM.INSTRUCTIONS : 1. Block/unblock the alarming unit.


FAULT NAME : SRAM operation failureMEANING : The SRAM memory operation failure. If this alarm appears continuously, the SRAM chip may be broken.INSTRUCTIONS : 1. Check the other active alarms.


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

FAULT NAME : Self test failedMEANING : The self test of the unit/module has failed.INSTRUCTIONS : 1. Block/unblock the alarming unit/module.

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

FAULT NAME : Summing service release from reset failedMEANING : Summing service release from reset failed.INSTRUCTIONS : 1. Reset the System Module.

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

FAULT NAME : Synchronization error in RP1 receiverMEANING : The frame alignment is lost or the frame burst has a CRC error when the System Module is working in extension mode.INSTRUCTIONS : 1. Check the other active synchronization alarms and act accordingly.

2. Reset the Extension System Module.

FAULT NAME : Synchronization failure

90 DN99580892Issue 08C


Id:0900d80580727d78


MEANING : The frame burst phase has moved compared to the internal counter. The FSM has already found the frame synchronization but the FSM frame clock does not match the FSM internal frame clock.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.





FAULT NAME : System Module failureMEANING : The FlexiBTS has detected an abnormal operation or a failure in the internal functionality of the System Module.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.



FAULT NAME : System clock for extension system module not availableMEANING : The Extension System Module does not receive the system clock.INSTRUCTIONS : 1. Connect to the Extension System Module with BTS Site Manager to check if there are optical interface alarms.

2. If there are, follow the instructions for those alarms.

3. If there are no optical interface alarms, replace the module.

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

DN99580892Issue 08C

91


Id:0900d80580727d78

2. If that does not help, replace the alarming unit (WAM).

FAULT NAME : TRANSU synchronization errorMEANING : The RP3 TX/RX state machine or the T-bus receiver has changed its state. The synchronization is lost or the T-bus receiver has not synchronized.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.




FAULT NAME : Tbus receiver parity faultMEANING : Data or synchronization failure in the System Module, two antenna carriers are affected.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.





Or




Block/unblock the alarming unit. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again.

92 DN99580892Issue 08C


Id:0900d80580727d78


FlexiBTS:


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

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

2. Check the AXC settings.

3. Check the transmission cablings.


FAULT NAME : Transmission clock missingMEANING : The reference clock monitoring has detected a loss of signal in the reference received from the FT.INSTRUCTIONS : 1. Check the Iub connection.

2. Check the FT status.

3. Check the connection between the FT and FSM.

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

FAULT NAME : Unit SW download failedMEANING : The software update to the unit or subunit has failed.INSTRUCTIONS : 1. Reset the BTS.


OR


DN99580892Issue 08C

93


Id:0900d80580727d78




OR



OR


FlexiBTS:




FAULT NAME : Unit blockedMEANING : A unit is blocked with BTS Site Manager.

The purpose of the fault is to avoid alarms that may be raised during the unit maintenance task.INSTRUCTIONS : To cancel the alarm, unblock the unit/module.






94 DN99580892Issue 08C


Id:0900d80580727d78


FlexiBTS:




FAULT NAME : Unit initialization failureMEANING : The connection to the WSP fails due to a WSP internal failure.INSTRUCTIONS : 1. Block/unblock the alarming unit.


FAULT NAME : Unit not supported by current BTS SW versionMEANING : An unsupported unit was found in the BTS. Typically this happens when a new unit version is installed and there is an older BTS SW in use that does not support the new unit version.INSTRUCTIONS : Replace the unit or upgrade the BTS SW.

FAULT NAME : Unit synchronization failedMEANING : The WAM/WSPC synchronization has failed.INSTRUCTIONS : 1. Block/unblock the alarming unit.


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



FAULT NAME : Uplink data buffer synchronization failureMEANING : The uplink data buffer loses synchronization.INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm, the FSP is faulty.

DN99580892Issue 08C

95


Id:0900d80580727d78




FAULT NAME : WAM SFN polling timeoutMEANING : The slave WAM is not synchronised with the master WAM.INSTRUCTIONS : 1. Block/unblock the alarming unit.

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


FAULT NAME : WAM internal errorMEANING : The Telecom SW does not communicate with the ATM SW because of a fault.INSTRUCTIONS : N/A

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

- The Iub reference frequency has been incorrect for a long time (up to several days) due to a fault in the transmission network synchronisation (which in turn is caused by an equipment fault or a setting error).

Before activating this alarm, the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' may have been active.

- If the BTS integrated transport part receives the synchronisation information via the 2.048 MHz synchronisation input (external clock source), the alarm situation may be caused by a fault in that signal. In that case the alarm behaviour notifications listed with the Iub signal (see above) are also valid in this case.

- The fast tuning action of the BTS master clock may have been executed without checking if the reference signal is correct or not. If the reference signal is incorrect during the fast tuning execution, it may result in adjusting the BTS master clock frequency far from the nominal value, which causes serious problems in the network performance.

96 DN99580892Issue 08C


Id:0900d80580727d78


- There is an equipment fault in the BTS.

- Due to the oven oscillator (OCXO) aging inside the WSC unit, the unit may be approaching the end of its lifetime. In such case, after the alarm activation, the DAC value is quite stable, whereas in the other fault cases it may be very unstable or at the edge of the adjustment area (0 or 4095).

Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WMC oven oscillator fault' becomes active, it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel.INSTRUCTIONS : 1. In case of a fault in the transmission network synchronisation, the network synchronisation must be corrected. The long-term accuracy of the Iub signal must be 0.015 ppm or better.

2. In case of a BTS equipment fault, the location may be:

a. Transport part - First check the alarms of the AXC node with the AXC Manager and act accordingly. - If there are no alarms, check the AXC synchronisation settings. b. WMC unit - If both the Iub reference signal accuracy and the AXC node are in order but the WMC unit is still alarming, run the fast tuning procedure with the BTS Site Manager. - If there is no cure in a few minutes, reset the site. - If that does not help, replace the WMC unit.

3. After the fault situation has been cleared, the BTS master clock may also require tuning, because the BTS master clock adjustment is quite slow. The tuning may be done: - Manually, by changing the DAC word (during a site visit). - Or with fast tuning, by which the BTS master clock is tuned in a few minutes automatically near the Iub reference (normal tuning takes care of the fine tuning).

Note, however, that the fast tuning should only be used in case the Iub reference signal is known to be a good one. Otherwise the BTS frequency may be tuned into a totally incorrect value, causing serious problems in the network performance.

Background information:

The principle is that in a mobile network, the synchronisation goes from MSC => RNC => BTS. But in reality that chain might

DN99580892Issue 08C

97


Id:0900d80580727d78

be broken somewhere and, for example, when using leased lines, the BTS may take the reference synchronisation from the transmission network of another operator. This does not harm the system if also the synchronisation of the leased line service provider is accurate/stable enough. The BTS uses the incoming synchronisation signal as a reference for the Air interface, the accuracy requirement of which is set by 3GPP.

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

- The Iub reference frequency has been incorrect for a long time (up to several days) due to a fault in the transmission network synchronization (which in turn is caused by an equipment fault or a setting error). Before activating this alarm, the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' may have been active.

- If the BTS integrated transport part receives the synchronization information via the 2.048 MHz synchronization input (external clock source), the alarm situation may be caused by a fault in that signal. In that case, the alarm behavior notifications listed with the Iub signal (see above) are also valid in this case.



- Due to the oven oscillator (OCXO) aging inside the WSC unit, the unit may be approaching the end of its lifetime. In such case, after the alarm activation, the DAC value is quite stable, whereas in the other fault cases it may be very unstable or at the edge of the adjustment area (0 or 4095).

Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WSC oven oscillator fault' becomes active, it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel.INSTRUCTIONS : 1. In the case of a fault in the transmission network

98 DN99580892Issue 08C


Id:0900d80580727d78


synchronization, you need to correct the network synchronization. The long-term accuracy of the Iub signal must be +/- 0.015 ppm or better.

2. In case of BTS equipment fault, the location may be:

2.1 Transport part

- First check the alarms of the AXC node with AXC Manager and act accordingly.

- If there are no alarms, check the AXC synchronization settings.

2.2 WSC unit

- If both the Iub reference signal accuracy and the AXC node are in order but the WSC unit is still alarming, run the fast tuning procedure with BTS Site Manager.

- If that does not solve the problem in a few minutes, reset the site.

- If that does not help, replace the WSC unit. Note: In case the BTS is equipped with two WSCs, the redundant unit takes over the operation of the faulty unit. But if the fault situation is caused by an incorrect reference signal, both the WSC units may start alarming sooner or later.

3. After the fault situation has been cleared, the BTS master clock may also require tuning, because the BTS master clock adjustment is quite slow. You can perform the tuning:

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

- with fast tuning, where the BTS master clock is tuned automatically in a few minutes near the Iub reference (normal tuning takes care of the fine tuning)

Note, however, that the fast tuning should only be used in case the Iub reference signal is known to be a good one. Otherwise the BTS frequency may be tuned into a totally incorrect value, causing serious problems in the network performance.

Background information: The principle is that in a mobile network, the synchronization goes from MSC > RNC > BTS. But in reality that chain might be broken somewhere and, for example, when using leased lines, the BTS may take the reference synchronization from the transmission network of another operator. This does not harm the system if also the

DN99580892Issue 08C

99


Id:0900d80580727d78

synchronization of the leased line service provider is accurate/stable enough. The BTS uses the incoming synchronization signal as a reference for the Air interface, the accuracy requirement of which is set by 3GPP.

FAULT NAME : WSC phase difference jammed to zero readingMEANING : The WSC phase measurement is jammed and the tuning operation is degraded.

The problem can be caused by a WSC fault, or a too fast frequency change on the Iub.INSTRUCTIONS : 1.If the basic accuracy of the Iub signal is in order but there is too much instability, that is, the jitter/wander is outside the acceptable limits, the synchronization of the transmission network must be corrected. The limits for the jitter/wander are defined in the ITU-T G.823. No actions on the BTS are needed.

2. Reset the site and wait about 10 minutes.

3. Try a power-on reset. If the alarm reappears, replace the unit.

If the alarm reappears during the next few weeks or the clock seems unstable, replace the unit.

Background information: The principle in the mobile network is that the synchronization goes from MSC => RNC => BTS. But in reality that chain might be broken somewhere and, for example, when using leased lines the BTS may take the reference synchronization from the transmission network of another operator. This does not harm the system if also the synchronization of the leased line service provider is accurate/stable enough. The BTS uses the incoming synchronization signal as a reference for the Air interface, the accuracy requirement of which is set by 3GPP.

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

2. Check the AXC settings.

3. Check the transmission cablings.


100 DN99580892Issue 08C


Id:0900d80580727d78


FAULT NAME : WSM SR-Bus errorMEANING : UltraSite, UltraSite/EUBB:

The RX signal is transported from the WTR unit to all WSP units via the WSMs. The WSM units in different subracks are connected to each other via the SR buses. This alarm is generated, when the WSM unit detects errors in the incoming SR bus from the adjacent WSM unit.

The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm.

Triple-mode:

The RX signal is transported from the WTR30 and WRT20 units (connected to the SR bus) to the WSP units via the SR bus. This alarm is generated, when the WSM detects errors in the incoming SR bus from the WTR unit.

The reason for the failure is the WSM or WTR unit, or the cable between the WSM front panel and the backplane.INSTRUCTIONS : 1. Run the WCDMA BTS loop test.

2. Check the WSM cables.

3. Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions).

FAULT NAME : WSM ST-Bus errorMEANING : The TX signal is transported from the WSP unit to all WTR units via the WSMs. The WSM units in different subracks are connected to each other via the ST buses. This alarm is generated when the WSM unit detects errors in the incoming ST bus from the adjacent WSM unit.

The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm.INSTRUCTIONS : 1. Run the WCDMA BTS loop test.



FAULT NAME : WSM T-Bus errorMEANING : The signal is transported from the WSP unit to the WTR unit through the WSM. This alarm is generated when the WSM unit detects errors in the incoming T bus from the WSP unit.

DN99580892Issue 08C

101


Id:0900d80580727d78

The reason for the failure is probably the WSP or WSM unit. The unit might have been installed incorrectly or the backplane cabling is faulty.INSTRUCTIONS : 1. Run the WCDMA BTS loop test.



FAULT NAME : WSM does not receive frame clockMEANING : The WSM does not receive the System Frame Clock (SFCLK) correctly from the WCI unit.

This fault may appear if the only clock unit (WSC) is removed.INSTRUCTIONS : 1. Block/unblock the alarming WSM.

Note! This will cause a BTS reset.

2. Replace the WCI unit and check whether the alarm is cleared.

3. Check the backplane cables and connectors.

FAULT NAME : WSM failureMEANING : The BTS has detected an abnormal operation or a failure in the internal functionality of the WSMF unit.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.



3. Reset the BTS.


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

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

102 DN99580892Issue 08C


Id:0900d80580727d78


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


2. Check that the unit is properly connected. If the unit LED does not light up, it is faulty.



FAULT NAME : WSP unit internal failureMEANING : The WAM and WSP are not synchronized.INSTRUCTIONS : 1. Block/unblock the alarming unit.



DN99580892Issue 08C

103

RNC Base Station Alarms (7000-7900) 7652 BASE STATION NOTIFICATION

Id:0900d80580727d78

30 7652 BASE STATION NOTIFICATIONMeaning

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




2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number



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


104 DN99580892Issue 08C


Id:0900d80580727d78


FAULT NAME : autonomous reset as recovery actionMEANING : The BTS tries to correct a fault situation by performing a recovery reset to a unit, the site or the BTS.INSTRUCTIONS : Check the alarm history and other active alarms of the unit.

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

FAULT NAME : 2M external reference missingMEANING : The reference clock monitoring has detected a loss of 2.048MHz signal received from an external reference source, connected to Sync In interface of the System Module.INSTRUCTIONS : Note! Perform the steps below in the listed order until the alarm disappears.

1. Check the cabling (connected to Sync In interface).

2. Check that the 2.048MHz reference source is working normally and the 2.048MHz signal is available.


FAULT NAME : ATM cell lossMEANING : ATM cells are lost. The cell loss can be caused by a traffic overload, by the WAM receiving an invalid ATM cell or AAL5 packet, or by the data corruption on the Iub (that is, a bad BER).

The most common causes for this alarm are transmission network problems (causing unnecessary WAM changes).INSTRUCTIONS : 1. Check that bandwidths (cells/s) are the same at the BTS, AXC and RNC.

2. Check the data integrity from the incoming Iub (see Troubleshooting instructions).


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

FAULT NAME : ATM, A2EA configuration errorMEANING : The RNC A2EA transport layer address does not comply with the given BTS A2EA address.

This alarm is reported to the BTS Site Manager only.INSTRUCTIONS : Check and re-commission the AXC (if AAL2 multiplexing is in use), RNC or BTS with the correct BTS A2EA addresses.

FAULT NAME : Active clock tuning faultMEANING : The phase measurement cannot be performed in the active WSC or

DN99580892Issue 08C

105


Id:0900d80580727d78

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



Note that because of a fault situation in the active clock, the redundant clock is not tuned. To make sure that the tuning is correct, run "Fast Tune BTS Clock" with BTS Site Manager after the switchover when the new WSC is taken into use. If there is a WMC or only one WSC, the tuning continues but the cells remain disabled.

FAULT NAME : Antenna Line Device Operation FailureMEANING : The device is not working properly, the configuration is not valid, or a given parameter is incorrect.INSTRUCTIONS : 1. Check the functionality of the antenna line device.

2. Check the compatibility between the antenna line device and the BTS.

3. Check that the given parameters are in the valid range.

FAULT NAME : Antenna Line Device failureMEANING : The System Module or the device itself has detected an abnormal operation or a failure in the antenna line device.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

1. Check the antenna line and antenna line devices. Make sure that the antenna line connectors are in the right torque.

2. Reset the alarming RF module by blocking/unblocking it.

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

4. Replace the RF Module.

FAULT NAME : Antenna line device HW failureMEANING : A hardware failure detected by an antenna line device. Usually this is a permanent fault (the hardware is broken).INSTRUCTIONS : 1. Block/unblock the Radio module to give a power-off reset to the antenna line devices.

2. If that does not help, replace the antenna line device.

FAULT NAME : Antenna line device configuration failureMEANING : An antenna line or antenna line device is not properly configured.

106 DN99580892Issue 08C


Id:0900d80580727d78


INSTRUCTIONS : 1. Update the proper SW to the device.

2. Check/correct the antenna line configuration.







FlexiBTS:




FAULT NAME : BTS reference clock missingMEANING : This alarm is generated if the reference clock monitoring function of the BTS does not receive one, two or all the synchronization reference signal(s).

Background information: There is a fixed synchronization priority list in the FlexiBTS:

-Priority 1: PPS (Pulse Per Second) signal connected to the Synchronization Input interface (Sync In) of the System Module. Normally the PPS signal is generated by the GPS receiver.

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

DN99580892Issue 08C

107


Id:0900d80580727d78

-Priority 3: the reference coming from the integrated transmission unit (FTM).

Normally, all the sources are not in use at the same time (it depends on the network planning and BTS configuration). The used sources are defined into the BTS configuration during the commissioning phase.

The alarm is not generated if the highest commissioned synchronization source is present, no matter what the lower level source statuses are.INSTRUCTIONS : Depending on the installed and commissioned synchronization source(s) listed in section "Meaning", select the commissioned synchronization option and perform the steps below in the listed order until the alarm disappears.

GPS receiver (PPS source):

1. If there is a GPS receiver commissioned at the BTS site, note the following: If the GPS receiver is not locked to any satellite, it turns off the PPS signal which is normally delivered to the BTS (Sync In interface). The most common reason is that the GPS receiver does not see any satellites because of poor antenna installation (poor sky visibility). For this, the only permanent cure is to change the GPS antenna location. One indication of a fairly poor sky visibility is that the alarm is activated/canceled every now and then.

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


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

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

External 2.048MHz signal:

1. If there is an external 2.048MHz signal source commissioned at the BTS site, check the alarms of that device and act accordingly. If this does not help, check the cables. Note that because the device type is not known, detailed instructions cannot be given - refer to the appropriate user manual of the device for further actions.

2. There may be a malfunction in the BTS. Perform a BTS site

108 DN99580892Issue 08C


Id:0900d80580727d78


reset.

Iub reference (FTM as source):

1. If there is an integrated transmission unit (FTM) commissioned at the BTS site, note the following: The FTM unit operates so that if it is not locked to a synchronization source, it turns off the clock reference signal which is normally delivered to the BTS master clock. The synchronization source of the FTM (set by the FTM synchronization priority setting) may be missing, causing the FTM's internal clock to drop to holdover mode. In this case, the fault in the transmission NETWORK must be corrected.

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

3. Check the synchronization settings of the FTM unit.


5. There may be an equipment failure in the FTM unit. Check the operation and replace the unit, if needed. Note: Normally the reason is not an equipment fault, but there may be cuts in the Iub interface causing the FTM clock to drop to holdover mode. Especially the alarm activity (frequent alarms/cancels instead of a stable alarm state) points to the instability of the transmission network, not to a fault in the unit.

If the previous steps do not help, there may be an equipment failure in the System Module. Check the operation and if performing a BTS site reset does not help, replace the System Module.

FAULT NAME : BTS reset needed to activate a licenceMEANING : The status of a license has changed to valid and a BTS reset is needed to take the license into use.INSTRUCTIONS : Reset the BTS.

FAULT NAME : BTS reset requiredMEANING : The BTS detected an Extension Module as a capacity enhancement.

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

FAULT NAME : BTS time not correctedMEANING : The SNTP time cannot be fetched from the transport system (FT) within the time limit.

DN99580892Issue 08C

109


Id:0900d80580727d78

INSTRUCTIONS : 1. Check the NTP setting.

2. Check the stratum parameter on the NTP server.


FlexiBTS:






UltraSite/EUBB:





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

FAULT NAME : Cabinet door openMEANING : The cabinet door is open or the cabinet door sensor is faulty.INSTRUCTIONS : 1. Ensure that the cabinet doors are properly closed.

110 DN99580892Issue 08C


Id:0900d80580727d78


2. Check that the door switches function correctly and that they have been adjusted correctly.

Note: this alarm can be enabled or disabled in commissioning.

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






FAULT NAME : Cooling fan out of orderMEANING : The RF Module cooling fan is not rotating at the specified speed.INSTRUCTIONS : Note! Perform the steps below in the listed order until the alarm disappears.

1. Check the fan and cabling.

2. Block/unblock the RF Module.

3. Replace the faulty fan assembly.

FAULT NAME : Difference between BTS master clock and reference frequencyMEANING : 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:

DN99580892Issue 08C

111


Id:0900d80580727d78

1. The Iub reference frequency has changed due to a fault in the transmission network synchronization (which in turn is caused by an equipment fault or a setting error). Note that if the network synchronization malfunction lasts for a long time, the alarm is canceled when the BTS frequency reaches the faulty Iub synchronization. The alarm can also be activated if the faulty Iub synchronization is corrected and there is again the difference of 0.2 ppm or more. The alarm is canceled whenever the difference becomes smaller than 0.2 ppm.

2. The Iub reference frequency fluctuates continuously due to a great deal of jitter/wander in the transmission network. The alarm is continuously activated/canceled (however, the alarming state may predominate). There is always some jitter/wander in the transmission network; the limits are defined in ITU-T G.823/824/825.

3. If the BTS integrated transport part receives the synchronization information via the 2.048 MHz synchronization input (external clock source), the alarm situation may be caused by a fault of that signal. In that case, the alarm behavior notifications listed with the Iub signal (see above) are also valid in this case.

4. There is an equipment fault in the BTS. The equipment fault is, however, not the most common reason. Normally the reason can be found in the Iub/reference signal behavior (see the descriptions above).

UltraSite, MetroSite, MetroSite 50, Triple-mode: Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WSC oven oscillator fault' becomes active, it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel.INSTRUCTIONS : Because there are several possibilities for the alarm activation, a BTS Clock Frequency History feature has been developed. You can access the stored history data via BTS Site Manager. You can use the history data as a tool for finding out the reason for the fault/alarm situation (for further instructions about the history feature, see the online help of BTS Site Manager). Depending on the possible reason, follow the instructions below:

1. In case of a fault in the transmission network synchronization, you must correct the network synchronization. The long-term accuracy of the Iub signal must be 0.015 ppm or better (check the correct Iub accuracy by measuring it). No actions on the BTS are necessarily needed.

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

112 DN99580892Issue 08C


Id:0900d80580727d78


there is too much instability, that is, the jitter/wander is outside the acceptable limits, you must correct the synchronization of the transmission network. The limits for the jitter/wander are defined in the ITU-T G.823/824/825. No actions on the BTS are needed.

3. In case of a BTS equipment fault, the location may be:

Transport part:

- First check the alarms of the AXC node with AXC Manager, or FTM and act accordingly. - If there are no alarms, check the AXC/FTM synchronization settings.

WSC/FCM unit:

- If both the Iub reference signal accuracy and the AXC/FTM are in order but the WSC/FCM unit is still alarming, run the fast tuning with BTS Site Manager. - If the alarm is still active after the fast tuning is finished, reset the site. If the problem does not disappear in a few minutes, reset the site. - If that does not help, replace the WSC/FCM unit.

Note that if the reason is in the transmission network synchronization, replacing the faulty unit does not correct the situation. Furthermore, the alarm activity (frequent alarms/cancels) points to an instability in the transmission network, not to a fault in the unit.

4. After the fault situation has been cleared, you might need to tune the BTS master clock because the BTS master clock adjustment is quite slow. You can perform the tuning:

- manually by changing the DAC word (during a site visit) - or with fast tuning, in which the BTS master clock is tuned in a few minutes automatically near the Iub reference (normal tuning takes care of the fine tuning). Note, however, that you should only use the fast tuning in case the Iub reference signal is known to be a good one. Otherwise the BTS frequency may be tuned into a totally incorrect value, causing serious problems in the network performance.

Background information: The principle is that in the mobile network, the synchronization goes from MSC => RNC => BTS. But in reality that chain might be broken somewhere and, for example, when using leased lines, the BTS may take the reference synchronization from the transmission network of another operator. This does not harm the system if the

DN99580892Issue 08C

113


Id:0900d80580727d78

synchronization of the leased line service provider is also accurate/stabile enough. The BTS uses the incoming synchronization signal as a reference for the Air interface, the accuracy requirement of which is set by 3GPP.

FAULT NAME : Error in file server during SW downloadMEANING : 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 a 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 NAME : Fan failureMEANING : All the fans or more than one fan in the same fan group are rotating slower than requested, are not rotating at all, or

114 DN99580892Issue 08C


Id:0900d80580727d78


the RPM information is not available for the fans. The reason for this fault can be too low supply voltage or a broken fan.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.


2. Replace the faulty fan module.

FAULT NAME : Fan module faultyMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:

All the fans or more than one fan in the same fan group (WFA, WTR, WPA/WMP, WHX) are rotating slower than requested, are not rotating at all, or the RPM information is not available for the fans. The reason for this fault can be too low supply voltage or a broken fan 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, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:

1. Check the Fan ID from the Alarm message and locate the problematic fan. See the Fan mapping figures in the Alarms and Troubleshooting document.


3. If that does not help, replace the WFA, WFD or MFU module or the fan controlled by the WFA, WFD or MFU.

Fan control: 'FAN UNIT' refers to a group of fans including the fan control unit. A 'fan' is a single blower.

FlexiBTS:

1. Check the Fan ID from the Alarm message and locate the problematic fan. See the Fan mapping figures in the Alarms and Troubleshooting document.


DN99580892Issue 08C

115


Id:0900d80580727d78


Fan control: 'FAN UNIT' refers to a group of fans including the fan control module. A 'fan' is a single blower.

FAULT NAME : Fan module operation degradedMEANING : A fan does not rotate or rotates slower than at the requested speed, or the RPM information is not available for the fan.INSTRUCTIONS : 1. Check the fan ID from the alarm message and locate the problematic fan. See the Fan mapping figures in the Alarms and Troubleshooting document.


3. If that does not help, replace the WFA, WFD or MFU module or the fan controlled by the WFA, WFD or MFU.

Fan control: 'FAN UNIT' refers to a group of fans including the fan control unit. A 'fan' is a single blower.

FAULT NAME : File corrupted in SW downloadMEANING : The SW being downloaded is corrupted or incorrectly formed.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

1. Retry the SW update.

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

FlexiBTS:


2. Save the snapshot and check the download status from the BTS SWDLreport in the snapshot file.

FAULT NAME : Heating element not workingMEANING : The heater control connection of the FSM is faulty, there is no heater or the heater is faulty.INSTRUCTIONS : 1. Check whether the heating element exists at all.

2. Check the heater control connection and that the heater is working.

3. Replace the alarming component.

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

116 DN99580892Issue 08C


Id:0900d80580727d78




FAULT NAME : Invalid Configuration fileMEANING : The commissioning file is missing, or an incorrect commissioning file has been detected during BTS startup as follows: "Validation failed due to wrong BTS ID" or "Validation failed due to incompatible data"INSTRUCTIONS : 1. Check and correct the contents of the commissioning file.

2. Recommission the BTS with the valid commissioning file.

FAULT NAME : MHA unit operation failureMEANING : A fault in the Masthead Amplifier (MHA) is detected. The fault reduces the gain performance or completely prevents the function of the MHA.INSTRUCTIONS : Replace the alarming module.

FAULT NAME : Mast Head Amplifier faultMEANING : The FlexiBTS has detected an abnormal operation or a failure in the Masthead Amplifier (MHA).

Note that the Tower Mounted Amplifier (TMA) is a synonym for the MHA and is used by the Antenna Interface Standards Group (AISG).INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

1. Check the cables related to the Masthead Amplifier (MHA).

2. Reset the alarming MHA module by blocking/unblocking the RF Module which the MHA is connected to.

3. Replace the faulty device(s).

FAULT NAME : No connection to WEA and unable to detect External alarmsMEANING : The WEA unit is missing from the BTS or it cannot be detected.INSTRUCTIONS : 1. Check the WEA and cabling. See Troubleshooting instructions for how to check units behind the same bus.


FAULT NAME : No connection to unit

DN99580892Issue 08C

117


Id:0900d80580727d78

MEANING : The connection to a unit that belongs to the BTS configuration has been lost.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:








FlexiBTS:



FAULT NAME : Non fatal ATM traffic overloadMEANING : Traffic load is approaching the maximum capacity. However, no data is discarded yet.INSTRUCTIONS : Check that the ATM configurations in the BTS, AXC and RNC match.

FAULT NAME : Not enough DSP capacity to set up a cellMEANING : Not enough BTS Baseband capacity to set up a cell.INSTRUCTIONS : 1. Lock/unlock the cells.

2. Add more baseband capacity into BTS or replace a broken baseband unit if that was a reason for the lack of capacity.

FAULT NAME : Not enough resources for commissioned HSUPAMEANING : There are not enough resources for the HSUPA minimum capacity

118 DN99580892Issue 08C


Id:0900d80580727d78


based on the commissioned parameters "Minimum Baseband Decoding Capacity" and "Minimum HSUPA Users".INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

1. Check the configuration to make sure that there are enough resources for the minimum HSUPA capacity.

2. If there are not enough resources, add the required number of WSP units or replace the broken ones, or re-commission the BTS and pre-reserve less capacity for the HSUPA.

3. Reset the BTS to get the minimum capacity preselection for the HSUPA in use.

FlexiBTS:

1. Check the configuration to make sure that there are enough resources for minimum HSUPA capacity.

2. If there are not enough resources, replace the broken module or re-commission the BTS and pre-reserve less capacity for HSUPA.


UltraSite/EUBB:

1. Check the configuration to make sure that there are enough resources for minimum HSUPA capacity.

2. If there are not enough resources, replace the broken WSPF or re-commission the BTS and pre-reserve less capacity for HSUPA.


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

FAULT NAME : Oven oscillator clock missingMEANING : The WSC is not able to deliver the clock signals required by the other units.INSTRUCTIONS : Replace the clock unit.

FAULT NAME : Oven oscillator heating failureMEANING : The heating of oven oscillator fails and the unit is broken. The ambient temperature can also be too low or change too

DN99580892Issue 08C

119


Id:0900d80580727d78

fast.INSTRUCTIONS : 1. Check the active fan alarms.

2. Replace the clock unit.

FAULT NAME : PPS reference missingMEANING : The reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver.INSTRUCTIONS : 1. Check the GPS receiver installation.

2. Check the GPS receiver status.

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

FAULT NAME : Reading license targetID from BTS failedMEANING : Failure occured during reading parameter from the Radio Module.INSTRUCTIONS : Note! Perform the steps below in the listed order until the alarm disappears.

1.Check the other active alarms. If the memory is corrupted, change the alarming module.

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


FAULT NAME : Smoke alarmMEANING : The internal smoke detector has detected smoke in the cabinet.INSTRUCTIONS : 1. Check the root cause.

2. If the alarm was false, replace the alarming smoke detector.

FAULT NAME : System frame clock synchronization error in clock deviceMEANING : The system frame alignment is lost or a parity error is detected in the incoming frame burst of BOFU FPGA.INSTRUCTIONS : 1. Reset BTS.

2. If resetting the BTS does not help, replace the WSMF.



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

120 DN99580892Issue 08C


Id:0900d80580727d78


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




FAULT NAME : Unit temperature is highMEANING : The temperature of a unit exceeds the threshold value.INSTRUCTIONS : Check the active fan alarms, and the airflow of the BTS.

FAULT NAME : WCI baseband reference clock failureMEANING : The master or redundant WSC does not generate Baseband Reference Clock (BRCLK) to the WCI because of an internal failure or a clock driver failure in the WSC unit.INSTRUCTIONS : 1. Block/unblock the active WSC unit.


3. Replace both WSC units.

FAULT NAME : WEA power regulator faultMEANING : The WEA unit external interface connectors are connected incorrectly, or there is a shot circuit in the +5 VCD.INSTRUCTIONS : 1. Disconnect the external cables and check whether the alarm disappeares.

2. Check the external cables and connections.

3. If the alarm does not disappear, check the WEA and replace it if it is faulty.

FAULT NAME : WIB unit battery failureMEANING : WIB unit battery failure:

- Several battery blocks (cells) are dead and the back-up system is out of order. - Some of the battery blocks (cells) reached an overcharge or a discharge voltage in a stand-by condition. - The voltage of one cell is not compatible with the other cell voltages.

DN99580892Issue 08C

121


Id:0900d80580727d78

INSTRUCTIONS : 1. Check the battery cablings and cells' voltage levels.

2. Replace the WIB unit or battery.

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

2. Check the battery temperature sensor.

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

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

- The Iub reference frequency has been incorrect for a long time (up to several days) due to a fault in the transmission network synchronization (which in turn is caused by an equipment fault or a setting error). Before activating this alarm, the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' may have been active.

- If the BTS integrated transport part receives the synchronization information via the 2.048 MHz synchronization input (external clock source), the alarm situation may be caused by a fault in that signal. In that case, the alarm behavior notifications listed with the Iub signal (see above) are also valid in this case.



- Due to the oven oscillator (OCXO) aging inside the WSC unit, the unit may be approaching the end of its lifetime. In such

122 DN99580892Issue 08C


Id:0900d80580727d78


case, after the alarm activation, the DAC value is quite stable, whereas in the other fault cases it may be very unstable or at the edge of the adjustment area (0 or 4095).

Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WSC oven oscillator fault' becomes active, it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel.INSTRUCTIONS : 1. In the case of a fault in the transmission network synchronization, you need to correct the network synchronization. The long-term accuracy of the Iub signal must be +/- 0.015 ppm or better.

2. In case of BTS equipment fault, the location may be:

2.1 Transport part

- First check the alarms of the AXC node with AXC Manager and act accordingly.

- If there are no alarms, check the AXC synchronization settings.

2.2 WSC unit

- If both the Iub reference signal accuracy and the AXC node are in order but the WSC unit is still alarming, run the fast tuning procedure with BTS Site Manager.

- If that does not solve the problem in a few minutes, reset the site.

- If that does not help, replace the WSC unit. Note: In case the BTS is equipped with two WSCs, the redundant unit takes over the operation of the faulty unit. But if the fault situation is caused by an incorrect reference signal, both the WSC units may start alarming sooner or later.

3. After the fault situation has been cleared, the BTS master clock may also require tuning, because the BTS master clock adjustment is quite slow. You can perform the tuning:

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

- with fast tuning, where the BTS master clock is tuned automatically in a few minutes near the Iub reference (normal tuning takes care of the fine tuning)

Note, however, that the fast tuning should only be used in case the Iub reference signal is known to be a good one. Otherwise the BTS frequency may be tuned into a totally

DN99580892Issue 08C

123


Id:0900d80580727d78

incorrect value, causing serious problems in the network performance.

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

FAULT NAME : WSC phase difference jammed to zero readingMEANING : The WSC phase measurement is jammed and the tuning operation is degraded.

The problem can be caused by a WSC fault, or a too fast frequency change on the Iub.INSTRUCTIONS : 1.If the basic accuracy of the Iub signal is in order but there is too much instability, that is, the jitter/wander is outside the acceptable limits, the synchronization of the transmission network must be corrected. The limits for the jitter/wander are defined in the ITU-T G.823. No actions on the BTS are needed.

2. Reset the site and wait about 10 minutes.

3. Try a power-on reset. If the alarm reappears, replace the unit.

If the alarm reappears during the next few weeks or the clock seems unstable, replace the unit.

Background information: The principle in the mobile network is that the synchronization goes from MSC => RNC => BTS. But in reality that chain might be broken somewhere and, for example, when using leased lines the BTS may take the reference synchronization from the transmission network of another operator. This does not harm the system if also the synchronization of the leased line service provider is accurate/stable enough. The BTS uses the incoming synchronization signal as a reference for the Air interface, the accuracy requirement of which is set by 3GPP.

FAULT NAME : WSC switch unsuccessfulMEANING : The WSC recovery switch over failed.INSTRUCTIONS : 1. Fast tune the active unit.

2. Block/unblock the alarming unit. This may cause a BTS

124 DN99580892Issue 08C


Id:0900d80580727d78


reset.




3. Reset the BTS.


FAULT NAME : WSMA ST-Bus errorMEANING : The TX signal is transported from the WSP unit to all WTR units via the WSMs. The WSM units in different subracks are connected to each other via the ST buses. This alarm is generated when the WSM unit detects errors in the incoming ST bus from the adjacent WSM unit.

The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm.INSTRUCTIONS : 1. Run the WCDMA BTS loop test.



FAULT NAME : WSMA T-Bus errorMEANING : The signal is transported from the WSP unit to the WTR unit via the WSM/WMC. This alarm is generated when the WSM unit detects errors in the incoming T bus from the WSP unit.

The reason for the failure is probably the WSP or WSM/WMC unit. The unit may have been installed incorrectly or the backplane cabling is faulty.INSTRUCTIONS : Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions).

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

DN99580892Issue 08C

125


Id:0900d80580727d78

the master System Module.

FAULT NAME : Writing parameter to Radio Module failedMEANING : Failure occured when writing parameter to the Radio Module was requested.INSTRUCTIONS : Note! Perform the steps below in the listed order until the fault disappears.

1.Check the other active fault. If the memory is corrupted, change the alarming module.

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


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

126 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

31 7653 CELL FAULTYMeaning

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

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



2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number




Below is the list of BTS fault(s) which may have caused this alarm inBTS WN6.0 release. In case of earlier SW release and in case you needmore detailed fault descriptions refer WCDMA RAN and I-HSPA SystemLibraries. The BTS fault descriptions are also included in BTS SW releasedocumentation. If that does not help, contact your local Nokia SiemensNetworks representative.

DN99580892Issue 08C

127

RNC Base Station Alarms (7000-7900) 7653 CELL FAULTY

Id:0900d80580727d78

FAULT NAME : AIR fatal alarmMEANING : ARIO has detected a Fatal level alarm. Some ARIO alarms can be canceled without a reset but most ARIO alarms require the WOU block/unblock to cancel.INSTRUCTIONS : 1. Check the WOU or WRUs.

2. Use the ARIO Local Management Tool and the Advanced Indoor Radio user documentation to diagnose the cause of the error.






FAULT NAME : Antenna1 connection faultMEANING : The BIAS-T has detected that the reflected TX power from the antenna has increased. The antenna cable between the WAF and MHA is faulty or the antenna is faulty. The BIAS-T may be faulty.INSTRUCTIONS : 1. Check the bias-T and MHA commissioning.

2. Block/unblock the WAF unit (check if the alarm reappears after 5 minutes).

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

4. Check the PITA cable connection (RJ45).

a. Check the voltage (see connector pins in Troubleshooting instructions).

b. Check the right connection (see User Manual).

c. Check by cross connecting RJ45 cables between other sectors.

FAULT NAME : BB bus reception error (summing device)MEANING : The master frame in the received baseband bus frame is not in the correct place related to the internally generated master

128 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

frame pulse. Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place.INSTRUCTIONS : FlexiBTS:



UltraSite/EUBB:


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

FAULT NAME : BTS config error (Not enough HW for LCR)MEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode:

A dual carrier WTR has been replaced with a single carrier WTR, and it cannot serve both cells commissioned to the WTR.

FlexiBTS:

A dual PA RF Module has been replaced with a single PA RF Module, and it cannot serve all cells commissioned to the RF Module.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

Replace the single carrier WTR with a dual carrier WTR.

FlexiBTS:

Replace the single PA RF Module with a dual PA RF Module.

Alternatively recommission the BTS with fewer cells.

FAULT NAME : BTS config error (WAF overload, 50W not in dualWPA config)MEANING : Two 50 W WPAs are coupled to one WAF, or one 50 W WPA and one 28 W WPA are coupled to one WAF.

Only two 28 W WPAs can be coupled together to one WAF unit.INSTRUCTIONS : Replace the 50 W WPAs with the 28 W WPAs.

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

DN99580892Issue 08C

129


Id:0900d80580727d78

Or replace the WPAI and WPAJ with a WPAA/WPAB.

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






FlexiBTS:





FlexiBTS:


2. Reset the RF Module and/or System Module, depending on the alarm source: a. Reset the RF Module by blocking/unblocking it.

130 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

b. Reset the System Module.




UltraSite/EUBB:






FAULT NAME : BTS reset requiredMEANING : The BTS detected an Extension Module as a capacity enhancement.

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


FlexiBTS:




DN99580892Issue 08C

131


Id:0900d80580727d78



UltraSite/EUBB:






FAULT NAME : Cell block rejected by RNC/I-HSPAMEANING : The cell has been disabled due to BTS internal reasons, for example if the RNC has rejected the normal cell blocking during the Intelligent Shutdown.INSTRUCTIONS : 1. Check the other active alarms.

2. Check the mains power supply.

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

FAULT NAME : Cell calibration failureMEANING : TX power calibration failure: a CPICH setup failure, CPICH release failure, WTR power out of range failure, or general initial calibration failure.INSTRUCTIONS : 1. Check the commissioning (LCR cabling).

2. Block/unblock the alarming unit or the WPA connected to the alarming WTR. If there was an internal failure, the unit needs to be blocked/unblocked to initialize/configure it again.

3. Run the WCDMA BTS loop test with BTS Site Manager to check the WSM cabling. (Note! The loop test cannot be run if the cell is already blocked because of an alarm.)

4. Check the RF and WSM cabling (for example, in the case of an incorrect cabling).

132 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

5. If the reported severity is 7653 Cell faulty, replace the WTR, WPA, WSMs or WSP. If the reported severity is 7654 Cell operation degraded (most probably the WPA cannot deliver enough output power), replace the WPA.

FAULT NAME : Cell power monitoringMEANING : The WPA/Radio output power has dropped.

There is a fault in the downlink transmission path.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:

1. Block/unblock the WPA. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again.

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

3. Check the RF TX cabling.

4. The fault may be in the WTR or WPA.

FlexiBTS:

1. Block/unblock the RF Module. If there was an internal failure or sticking in the unit SW, the module needs to be blocked/unblocked to get it initialized/configured again.

2. Check the RF Module.






FSP: Faraday has not sent a specific mandatory indication message in the start-up during the time limit the message is expected to arrive.INSTRUCTIONS : 1. Check that the unit/module is properly connected. If the

DN99580892Issue 08C

133


Id:0900d80580727d78

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













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

134 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

replacing the RF Module/Extension System Module does not clear the fault situation, replace the alarming System Module.

FAULT NAME : Filter unit operation failedMEANING : A filter has not been able to tune on an appropriate sub-band properly (tuning failure), or another major failure has been detected by the filter (unit faulty).INSTRUCTIONS : Replace the filter unit.

FAULT NAME : Frame Clock MissingMEANING : The System Module clock reference differs from the RF Module clock.INSTRUCTIONS : 1. Check the cables between the System Module and RF Module.


3. If that does not help, block/unblock the site.

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



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

FAULT NAME : Incoherency with RF ModulesMEANING : Incorrect cell configuration for RF Modules with different frequency. The same cell is configured for two RF Modules which are not at same frequency.INSTRUCTIONS : 1. Check which Radio Modules are for the faulty frequency.

2. Replace the incompatible Radio Module(s).



DN99580892Issue 08C

135


Id:0900d80580727d78


FAULT NAME : Invalid carrier in WTRMEANING : There was an attempt to set the WTR to a channel not supported by the WTR (on a different frequency band).INSTRUCTIONS : 1. Make sure that correct carrier numbers are in use in the RNC.

2. Commission the BTS with the correct WCDMA carrier values for the WTR.

FAULT NAME : LPA faultyMEANING : The unit is broken, because the startup self-test fails, the FPGA file downloading from the flash fails, or the synthesizer is malfunctioning.

This fault can only occur in the self-test phase.INSTRUCTIONS : 1. Block/unblock the WPA/WMP.

2. Replace the alarming WPA/WMP.

FAULT NAME : LPA input signal level is too highMEANING : The input signal level from the WTR is critically high. The LPA gain is too low.INSTRUCTIONS : 1. Block/unblock the WTR and WPA/WMP or WOU.

2. Check the PTx Target value with OMS and the HSDPA power parameters (see Troubleshooting instructions).


FAULT NAME : LPA linearization faultMEANING : The quality of the output signal is poor, or the synthesizers are not locked.INSTRUCTIONS : 1. Block/unblock the WPA/WMP.

2. Check the RF TX cablings (see Troubleshooting instructions).


FAULT NAME : LPA power supply alarmMEANING : The internal power supply of the unit is malfunctioning.INSTRUCTIONS : 1. Block/unblock the WPA/WMP, WOU.

2. Check the power supply and WPA cablings and connectors from the backplane (see Troubleshooting instructions).

136 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

3. Replace alarming unit.

FAULT NAME : LPA reflected power too highMEANING : A serious increase in the output impedance. A cable may be broken or a cable connection may be faulty.INSTRUCTIONS : 1. Block/unblock the WPA.

2. Check the RF cabling between the WPA and WAF.

3. Check the WOC (in the redundant configuration) installation in accordance with the Installation instructions (that is, check that cable lengths and codes are correct between the WTR, WIC and WPA).

4. Check the WAF, the antenna cabling and cables.

5. Replace the WPA.

FAULT NAME : LPA temperature is dangerously highMEANING : The temperature of the unit is critical. It has reached its maximum acceptable level.

It is also possible that the temperature sensor is broken.INSTRUCTIONS : 1. Check the other active alarms related to the temperature or cooling fan.

2. Block/unblock the WPA if no other alarming unit. If block/unblock does not help, replace the alarming unit.

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

FAULT NAME : Module Clock FaultyMEANING : The RF Module lost lock to the incoming clock.INSTRUCTIONS : 1. Check the cables between the System Module and RF Module.



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

FAULT NAME : No connection to unitMEANING : The connection to a unit that belongs to the BTS configuration has been lost.

DN99580892Issue 08C

137


Id:0900d80580727d78

INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:








FlexiBTS:




FAULT NAME : Not enough WAF resources in LCRMEANING : There are not enough WAF units in a cell.INSTRUCTIONS : UltraSite, MetroSite and Triple-mode:

1. See the section No connection to unit in the troubleshooting instructions.

2. Increase the number of WAF units in the BTS.

MetroSite 50:

Change the WAF.

138 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

FAULT NAME : Optical Interface faultyMEANING : The Small Form Factor Pluggable (SFP) malfunction has occured or the SFP module is not physically present (no electrical connection exists). The SFP is a part of the fibre cable package.INSTRUCTIONS : 1. Check that the SFP is properly connected.

2. Replace the SFP module.

FAULT NAME : Post test failedMEANING : An RF Module power-on self-test failed at start-up.INSTRUCTIONS : Replace the alarming RF Module.








FlexiBTS:




FAULT NAME : RF BB Bus Configuration ErrorMEANING : The RF Module baseband bus is configured incorrectly.INSTRUCTIONS : 1. Block/unblock the RF Module.


FAULT NAME : RF BB Bus Synchronisation ErrorMEANING : The baseband bus between the System Module and RF Module is out of synchronization.

DN99580892Issue 08C

139


Id:0900d80580727d78

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




FAULT NAME : RF Module Filter input power missingMEANING : The RF Module filter has measured a too low TX power.INSTRUCTIONS : 1. Block/unblock the RF Module.


FAULT NAME : RF Module OverheatMEANING : The RF Module temperature is too high.INSTRUCTIONS : 1. Check the fans and ensure that the ambient temperature on the site is acceptable.


FAULT NAME : RF Module Power output faultyMEANING : The Power Supply has detected an overvoltage, undervoltage or overcurrent in the RF Module.INSTRUCTIONS : 1. Block/unblock the RF Module.


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

FAULT NAME : RF Module critical file not foundMEANING : A critical configuration file is missing from the RF Module.INSTRUCTIONS : Replace the alarming RF Module.

FAULT NAME : RF Module failureMEANING : The FlexiBTS has detected an abnormal operation or a failure in the internal functionality of the RF Module.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

1. Check the other active BTS alarms (System Module failure, Baseband Bus failure, Failure in optical RP3 interface and Antenna Line Device failure) and act accordingly.

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


140 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

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

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


FAULT NAME : RX out of orderMEANING : The RF Module RX RF synthesizer is not locked.INSTRUCTIONS : 1. Block/unblock the RF Module.


FAULT NAME : Receiving failure in Optical InterfaceMEANING : The incoming optical signal to the Small Form Factor Pluggable (SFP) is missing or too weak, or the fibre cable has been detached.

The connection between the System Module and the RF Module units (LTX, Antenna Filter or Antenna Line Device) is broken.INSTRUCTIONS : 1. Check the status of the module behind the faulty link (Power on, and so on).

2. Check the SFP from both ends (the System Module and the module behind the faulty link). The optical interface LED indicates the faulty SFP. Replace the SFP, if it is faulty.

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

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


FAULT NAME : TX out of orderMEANING : The RF Module TX path is not usable.INSTRUCTIONS : 1. Block/unblock the RF Module.


FAULT NAME : TX output power measurement fault

DN99580892Issue 08C

141


Id:0900d80580727d78

MEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: The WTR or WPA/WMP/WOU output power measurement has failed.

FlexiBTS: The RF Module output power measurement has failed.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:

1. Block/unblock the alarming unit. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again.

2. Check the units and the RF cabling between the WPA/WMP/WOU and WTR units.

FlexiBTS:

1. Reset the alarming RF Module with the block/unblock function. If there was an internal failure or sticking in the unit SW, the Module needs to be blocked/unblocked to get it initialized/configured again.




Or





FlexiBTS:

If there was an internal failure, in the case of an FR, the

142 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

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







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

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




OR


DN99580892Issue 08C

143


Id:0900d80580727d78


OR


FlexiBTS:











FlexiBTS:




FAULT NAME : Unit not supported by current BTS SW version

144 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

MEANING : An unsupported unit was found in the BTS. Typically this happens when a new unit version is installed and there is an older BTS SW in use that does not support the new unit version.INSTRUCTIONS : Replace the unit or upgrade the BTS SW.



FAULT NAME : VSWR alarmMEANING : Radio Module (60W RRH)/the Filter (all others) has detected a VSWR value exceeding the defined level. The antenna line is mismatched or damaged.INSTRUCTIONS : 1. Check the antenna cables, connectors, antenna and possible antenna line devices.

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

FAULT NAME : WAF low noise amplifier faultyMEANING : One of the two RX pre-amplifiers (one in the main branch and the other in the diversity branch) is faulty. The LED indicates the faulty unit.

MetroSite 50: One, some, or all of the RX pre-amplifiers (max 6) are faulty. The LED indicates the faulty unit(s).INSTRUCTIONS : 1. Block/unblock the WAF unit. This is most likely a HW fault, but blocking/unblocking the unit ensures that before a site visit.


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

FAULT NAME : WSM RR-Bus errorMEANING : The signal is transported from the WTR to the WSP via the WSM. This alarm is generated when the WSM/WMC unit detects errors in the incoming RR bus from the WTR unit.

DN99580892Issue 08C

145


Id:0900d80580727d78

The reason for the failure is probably the WTR or WSM/WMC unit. The unit may have been installed incorrectly or the backplane cabling is faulty.INSTRUCTIONS : 1. Run the WCDMA BTS loop test.

2. Replace the units indicated in the alarm one by one and check whether the problem is cleared.

3. Check the backplane cables and connectors (see Troubleshooting instructions).

FAULT NAME : WTR RT-bus faultMEANING : The bus clock signal is corrupted or missing in the RT bus. The signal frequency should be exactly half of the system clock frequency.INSTRUCTIONS : 1. Check the other active alarms.

2. Check the WSM, WSP and WTR.

Note! The problem can be in the unit connector, cabinet cabling or backplane.

FAULT NAME : WTR internal clock faultyMEANING : The WTR internal system clock is missing. This can be caused by a missing or bad quality reference clock signal from the WSC, or a WTR unit HW failure. The transmitted and received frequencies are incorrect.INSTRUCTIONS : 1. Block/unblock the alarming unit.

2. Check backplane cables and connectors.


FAULT NAME : WTR internal clock faultyMEANING : The WTR VCXO PLL is not locked. This can be caused by a missing or bad quality reference clock signal from the WSC or a WTR unit HW failure. The transmitted and received frequencies are incorrect.INSTRUCTIONS : 1. Block/unblock the alarming unit.


3. Chcek the backplane cables and connectors.

FAULT NAME : WTR local oscillator not lockedMEANING : The TX IF synthesizer (common to both TX chains) cannot lock to the defined frequency.INSTRUCTIONS : 1. Block/unblock the alarming unit.


146 DN99580892Issue 08C


Id:0900d80580727d78

7653 CELL FAULTY

FAULT NAME : WTR output power decreasedMEANING : The TX1 RF and/or TX2 RF signal level of the main RF output is lower than the predetermined level.INSTRUCTIONS : 1. Block/unblock the alarming unit.


FAULT NAME : WTR output power faultMEANING : An amplifier stage is out of order in the TX chain. The transmitter will be shut down.INSTRUCTIONS : 1. Block/unblock the alarming unit.


FAULT NAME : WTR synthesizer is not lockedMEANING : The TX & RX RF synthesizer or the RX IF synthesizer is not locked (or the RF synthesizer buffer amplifier is faulty). The output frequency of the transmitter can be wrong or missing, or the receiver might receive a wrong frequency or is not receiving.INSTRUCTIONS : 1. Block/unblock the alarming unit.


FAULT NAME : WTR temperature is highMEANING : The internal temperature of the WTR is dangerously high.INSTRUCTIONS : 1. Check the other active temperature or cooling fan-related alarms.

2. If you can find no reason, the sensor is probably broken. Replace the unit.


DN99580892Issue 08C

147

RNC Base Station Alarms (7000-7900) 7654 CELL OPERATION DEGRADED

Id:0900d80580727d78

32 7654 CELL OPERATION DEGRADEDMeaning

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




2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number





148 DN99580892Issue 08C


Id:0900d80580727d78


FAULT NAME : 10b8b coding error in Optical Interface device <opt link/RP3>MEANING : The fibre cable has an interference; the data becomes faulty.

A physical connection failure between the optical interface and the summing function (caused by bad circuit joints, for example).INSTRUCTIONS : 1. Reset the RF Module behind the faulty optical interface by blocking/unblocking it.

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

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

FAULT NAME : AIR major alarmMEANING : ARIO has detected a Major level alarm. Some ARIO alarms can be canceled without a reset but most ARIO alarms require the WOU block/unblock to cancel.INSTRUCTIONS : 1. Check the WOU or WRUs.

2. Use the ARIO Local Management Tool and the Advanced Indoor Radio user documentation to diagnose the cause of the error.

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






FAULT NAME : Antenna Line failure

DN99580892Issue 08C

149


Id:0900d80580727d78

MEANING : Radio Module (60W RRH) or Filter (all others) has detected overcurrent on the antenna line. The antenna line might be damaged (short circuit) or some antenna line device is causing overload. All antenna line devices powered by the antenna line are out of order.INSTRUCTIONS : Check the antenna line and antenna line devices. Fix or replace the faulty parts/devices.

FAULT NAME : Antenna line device HW failureMEANING : A hardware failure detected by an antenna line device. Usually this is a permanent fault (the hardware is broken).INSTRUCTIONS : 1. Block/unblock the Radio module to give a power-off reset to the antenna line devices.


FAULT NAME : Antenna line device configuration failureMEANING : An antenna line or antenna line device is not properly configured.INSTRUCTIONS : 1. Update the proper SW to the device.

2. Check/correct the antenna line configuration.


FAULT NAME : Antenna1 connection faultMEANING : The BIAS-T has detected that the reflected TX power from the antenna has increased. The antenna cable between the WAF and MHA is faulty or the antenna is faulty. The BIAS-T may be faulty.INSTRUCTIONS : 1. Check the bias-T and MHA commissioning.

2. Block/unblock the WAF unit (check if the alarm reappears after 5 minutes).

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

4. Check the PITA cable connection (RJ45).

a. Check the voltage (see connector pins in Troubleshooting instructions).

b. Check the right connection (see User Manual).

c. Check by cross connecting RJ45 cables between other sectors.

FAULT NAME : BS SW download or activation failedMEANING : The SW update to the BTS has failed. The error can be caused by a unit reset during the SW update, a hardware problem in the unit or cabinet, or a corrupted flash file system.

150 DN99580892Issue 08C


Id:0900d80580727d78


INSTRUCTIONS : 1. Retry the SW update.

2. If other flash memory-related alarms are active for the alarming unit at the same time, replace the alarming unit.

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

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

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






FlexiBTS:




FAULT NAME : BTS internal SW management problemMEANING : A software update to a unit/module or subassembly has failed, or a corrupted SW file has been detected in FLASH.

DN99580892Issue 08C

151


Id:0900d80580727d78

INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

FlexiBTS:






UltraSite/EUBB:







FlexiBTS:



3. Reset the RF Module and/or System Module, depending on the alarm source: a. Reset the RF Module by blocking/unblocking it. b. Reset the Extension System Module by

152 DN99580892Issue 08C


Id:0900d80580727d78


blocking/unblocking it. c. Reset the master System Module.



UltraSite/EUBB:





FAULT NAME : Cell calibration failureMEANING : TX power calibration failure: a CPICH setup failure, CPICH release failure, WTR power out of range failure, or general initial calibration failure.INSTRUCTIONS : 1. Check the commissioning (LCR cabling).

2. Block/unblock the alarming unit or the WPA connected to the alarming WTR. If there was an internal failure, the unit needs to be blocked/unblocked to initialize/configure it again.

3. Run the WCDMA BTS loop test with BTS Site Manager to check the WSM cabling. (Note! The loop test cannot be run if the cell is already blocked because of an alarm.)

4. Check the RF and WSM cabling (for example, in the case of an incorrect cabling).

5. If the reported severity is 7653 Cell faulty, replace the WTR, WPA, WSMs or WSP. If the reported severity is 7654 Cell operation degraded (most probably the WPA cannot deliver enough output power), replace the WPA.

FAULT NAME : Cell power parameter out of rangeMEANING : 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.


DN99580892Issue 08C

153


Id:0900d80580727d78











FAULT NAME : Configuration file corruptedMEANING : The RF Module SW detected conflicting or corrupted configuration data.INSTRUCTIONS : 1. Block/unblock the RF Module


FAULT NAME : Diversity antenna line faultMEANING : The operating voltage of the Mast Head Amplifier (MHA) is supplied through the BIAS-T from the WAF. The WAF monitors the consumption of the current and generates an alarm if it

154 DN99580892Issue 08C


Id:0900d80580727d78


deviates from normal. The cable between the MHA and WAF is faulty, the Bias-T is faulty, the MHA is faulty, another antenna line device between the MHA and WAF is faulty, or the MHA does not exist.INSTRUCTIONS : 1. Check the MHA commissioning parameters.

2. Block/unblock the related WAF.

3. Check the RF cabling and Bias-T.

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

FAULT NAME : FPGA SW update failedMEANING : The FPGA software update has failed.INSTRUCTIONS : 1. Block/unblock the RF Module.









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

DN99580892Issue 08C

155


Id:0900d80580727d78

INSTRUCTIONS : Replace the filter unit.

FAULT NAME : Flash operation failureMEANING : A flash memory operation failure. If this alarm continuously appears, the flash chip may be broken.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:


2. Block/unblock the alarming unit. There are no recovery actions and due to that the block/unblock can be tried once. If that does not help, replace the alarming unit.

FlexiBTS:


2. Block/unblock the alarming module. There are no recovery actions and due to that the block/unblock can be tried once. If that does not help, replace the alarming module.

FAULT NAME : Frame Clock MissingMEANING : The System Module clock reference differs from the RF Module clock.INSTRUCTIONS : 1. Check the cables between the System Module and RF Module.




FAULT NAME : Gain adjust alarmMEANING : The WTR cannot adjust the TX output power.INSTRUCTIONS : 1. Block/unblock the WTR. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure.

2. Check the WTR RF TX cabling.



156 DN99580892Issue 08C


Id:0900d80580727d78



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

2. Reset the site.

FAULT NAME : Invalid frequency channel for the BTS HWMEANING : The requested channel in the cell setup is not acceptable for the BTS hardware, because of an incorrect frequency band and/or a carrier spacing and/or the number of carriers.INSTRUCTIONS : Check the RNC cell parameters against the BTS HW configuration. The cell frequency is out of the min/max limit of the HW, or the number of carriers for the HW type is exceeded, or the carrier spacing limit is exceeded. There are different type variations of the HW that may have limitations in the supported frequency range and bandwidth.

FAULT NAME : LPA gain faultMEANING : A malfunction in some part of the amplifier, which therefore cannot perform the specified gain.INSTRUCTIONS : 1. Block/unblock the WPA/WMP.

2. Replace the alarming WPA/WMP.

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

FAULT NAME : MHA unit operation failureMEANING : A fault in the Masthead Amplifier (MHA) is detected. The fault reduces the gain performance or completely prevents the function of the MHA.INSTRUCTIONS : Replace the alarming module.

FAULT NAME : Main antenna line faultMEANING : The operating voltage of the MHA is supplied through the Bias-T from the WAF. The WAF monitors the consumption of the current and generates an alarm if the consumption deviates from normal. The cable between the MHA and WAF is faulty, the Bias-T is faulty, the MHA is faulty, another antenna line device between the MHA and WAF is faulty, or the MHA does not

DN99580892Issue 08C

157


Id:0900d80580727d78

exist.INSTRUCTIONS : 1. Check the MHA commissioning parameters.

2. Block/unblock the related WAF.

3. Check the RF cabling and Bias-T.

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

FAULT NAME : Mast Head Amplifier faultMEANING : The FlexiBTS has detected an abnormal operation or a failure in the Masthead Amplifier (MHA).

Note that the Tower Mounted Amplifier (TMA) is a synonym for the MHA and is used by the Antenna Interface Standards Group (AISG).INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

1. Check the cables related to the Masthead Amplifier (MHA).

2. Reset the alarming MHA module by blocking/unblocking the RF Module which the MHA is connected to.

3. Replace the faulty device(s).

FAULT NAME : Mast Head Amplifier fault, <line>MEANING : The Masthead Amplifier (MHA) does not work properly. The received RF signal level is decreased.

If both stages of the LNA on the uplink path fail, the MHA swithes the LNA to by-pass mode. In by-pass mode, the MHA has no gain but some loss. If only one stage of the LNA fails, the MHA still has about a half of its normal gain. With an integrated MHA (WMHC), the fault may affect both main and diversity branches or just one of them.INSTRUCTIONS : 1. Check the antenna cables and connectors towards the MHA. Fix or replace the broken parts.

2. Restart the MHA by blocking and unblocking the Flexi Radio (FR) Module. NOTE! This operation affects all antenna lines and cells related to the FR Module, not just the faulty one. If the alarm reappears, replace the alarming module.


158 DN99580892Issue 08C


Id:0900d80580727d78









FlexiBTS:



FAULT NAME : No feedback signalMEANING : The feedback signal to predistortion is too weak or missing. The TX performance is degraded.INSTRUCTIONS : 1. Block/unblock the RF Module.


FAULT NAME : Not enough WAF resources in LCRMEANING : There are not enough WAF units in a cell.INSTRUCTIONS : UltraSite, MetroSite and Triple-mode:

1. See the section No connection to unit in the troubleshooting instructions.

2. Increase the number of WAF units in the BTS.

MetroSite 50:

Change the WAF.

DN99580892Issue 08C

159


Id:0900d80580727d78

FAULT NAME : Optical Interface Data/Control/Ethernet Buffer FullMEANING : The RP3 or Ethernet buffering is not working and the buffer becomes full. The optical device is malfunctioning. The fault may be generated due to synchronization problems or incorrect initialization.INSTRUCTIONS : Swap the alarming and working links. Then check where the alarm is now reported. If the alarming link remains the same, replace the System Module. If the alarming link changes, replace the RF Module behind that link.

FAULT NAME : Optical interface buffer alarmMEANING : RP3 or Ethernet buffering is not working and the buffer becomes full. The optical device malfunctions. The fault may be generated because of synchronization problems or incorrect initialization.INSTRUCTIONS : 1. Depending on the interface, reset the connected module/unit behind the interface that causes the alarm by blocking/unblocking it.

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

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

UltraSite/EUBB: 3. If WSMF is the only alarm source, or replacing the connected module/unit does not clear the fault situation, replace the WSMF that causes the alarm.







160 DN99580892Issue 08C


Id:0900d80580727d78



FlexiBTS:




FAULT NAME : RET Antenna control failureMEANING : Antenna tilting is not possible or might function incorrectly.INSTRUCTIONS : 1. Recalibrate the RET antenna.

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

FAULT NAME : RF BB Bus Configuration ErrorMEANING : The RF Module baseband bus is configured incorrectly.INSTRUCTIONS : 1. Block/unblock the RF Module.


FAULT NAME : RF BB Bus Connection Transmission ErrorMEANING : 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 alarming RF Module

FAULT NAME : RF BB Bus Synchronisation ErrorMEANING : The baseband bus between the System Module and RF Module is out of synchronization.INSTRUCTIONS : 1. Check the cables between the System Module and RF Module.




FAULT NAME : RF BB Energy too highMEANING : The TX feedback signal power is too high.INSTRUCTIONS : 1. Block/unblock the RF Module.


FAULT NAME : RF Module Gain adjusting failureMEANING : The TX output power adjustment failed.INSTRUCTIONS : 1. Block/unblock the RF Module.


DN99580892Issue 08C

161


Id:0900d80580727d78

FAULT NAME : RF Module OverheatMEANING : The RF Module temperature is too high.INSTRUCTIONS : 1. Check the fans and ensure that the ambient temperature on the site is acceptable.


FAULT NAME : RF Module failureMEANING : The FlexiBTS has detected an abnormal operation or a failure in the internal functionality of the RF Module.INSTRUCTIONS : Note: Perform the steps below in the listed order until the alarm disappears.

1. Check the other active BTS alarms (System Module failure, Baseband Bus failure, Failure in optical RP3 interface and Antenna Line Device failure) and act accordingly.

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



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

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

FAULT NAME : RF Power decreasedMEANING : The highest temperature exceeds the power decrease limit.INSTRUCTIONS : 1. Check the fans and ensure that the ambient temperature on the site is acceptable.

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


FAULT NAME : RP3 RX data frame timing errorMEANING : The RP3 RX receiver has detected that the incoming data frame is outside of the alignment window.INSTRUCTIONS : 1. Reset BTS.


FAULT NAME : RP3 uplink/downlink buffering errorMEANING : Uplink buffering from Rbus to RP3, or vice versa downlink buffering from RP3 to Tbus does not work. Timing parameters

162 DN99580892Issue 08C


Id:0900d80580727d78


DELTA/RBUS_START_TIME, and/or PI/TBUS_START_TIME are incorrectly set.INSTRUCTIONS : 1. Reset BTS.


FAULT NAME : RX out of orderMEANING : The RF Module RX RF synthesizer is not locked.INSTRUCTIONS : 1. Block/unblock the RF Module.


FAULT NAME : Rbus data clock missingMEANING : Data traffic from Rbus to RP3 in BOFU FPGA is malfunctioning because of errors in the Rbus synchronization clock.INSTRUCTIONS : 1. Reset BTS.


FAULT NAME : Rx signal level failureMEANING : The RX signal level is less than -112dBm or the difference between the maximum and minimum power levels of all RX antennas in the same cell and sector is more than the limit (4 dB).INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:

1. Check BTS Site Manager for received signal levels to find out which RX is causing the problem.

2. If an MHA is alarming, replace the MHA unit and check if the RX signal level failure alarm is canceled.

3. If the alarm still exists, check the antenna cables. Swap the main and diversity RF cables between the WTR and WAF to see if the problem is in the WTR. If RX values do not change between the WTR inputs when swapping the cables, the fault is in the WTR unit. Change the WTR unit.

4. If the WTR is not faulty, the WAF, antenna feeder, or antenna is faulty on the antenna line which has the inadequate RX level. Check and replace the faulty equipment.

FlexiBTS:

1. Check BTS Site Manager for the received signal levels to find out which RX is causing the problem.

2. If an MHA is alarming, replace the MHA unit and check if the RX signal level failure alarm is canceled.

3. Check the antenna cables. The radio module, antenna feeder,

DN99580892Issue 08C

163


Id:0900d80580727d78

or antenna is faulty on the antenna line which has the inadequate RX level. Check and replace the faulty equipment.

Note: The RX value in BTS Site Manager is refreshed at one minute intervals.

FAULT NAME : SW corruptedMEANING : A corrupted SW file in the FLASH is detected.INSTRUCTIONS : Update the SW to the BTS.

FAULT NAME : TX output power measurement faultMEANING : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB: The WTR or WPA/WMP/WOU output power measurement has failed.

FlexiBTS: The RF Module output power measurement has failed.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode, UltraSite/EUBB:

1. Block/unblock the alarming unit. If there was an internal failure, the unit needs to be blocked/unblocked to get it initialized/configured again.

2. Check the units and the RF cabling between the WPA/WMP/WOU and WTR units.

FlexiBTS:

1. Reset the alarming RF Module with the block/unblock function. If there was an internal failure or sticking in the unit SW, the Module needs to be blocked/unblocked to get it initialized/configured again.




Or



164 DN99580892Issue 08C


Id:0900d80580727d78




FlexiBTS:








FAULT NAME : Transmission quality deterioratedMEANING : The TX signal adjustment fails.INSTRUCTIONS : 1. Block/unblock the RF Module.


FAULT NAME : Under- / overrunning error in RP3 serializer clock crossing FIFOMEANING : Either too large clock jitter between received signal and internal clock, or missing data input signal. The receiver is started up again.INSTRUCTIONS : 1. Reset BTS.

DN99580892Issue 08C

165


Id:0900d80580727d78





OR



OR


FlexiBTS:










166 DN99580892Issue 08C


Id:0900d80580727d78



FlexiBTS:





FAULT NAME : Unit unidentifiedMEANING : The permanent memory in the module is corrupted and the module product code or serial number is missing, or the module product code is unknown.INSTRUCTIONS : 1. Block/unblock the RF Module.



FAULT NAME : VSWR alarmMEANING : Radio Module (60W RRH)/the Filter (all others) has detected a VSWR value exceeding the defined level. The antenna line is slightly mismatched.INSTRUCTIONS : 1. Check the antenna cables, connectors, antenna and possible antenna line devices.

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

FAULT NAME : WAF low noise amplifier faultyMEANING : One of the two RX pre-amplifiers (one in the main branch and the other in the diversity branch) is faulty. The LED indicates the faulty unit.

MetroSite 50: One, some, or all of the RX pre-amplifiers (max

DN99580892Issue 08C

167


Id:0900d80580727d78

6) are faulty. The LED indicates the faulty unit(s).INSTRUCTIONS : 1. Block/unblock the WAF unit. This is most likely a HW fault, but blocking/unblocking the unit ensures that before a site visit.


FAULT NAME : WSM RR-Bus errorMEANING : The signal is transported from the WTR to the WSP via the WSM. This alarm is generated when the WSM/WMC unit detects errors in the incoming RR bus from the WTR unit.

The reason for the failure is probably the WTR or WSM/WMC unit. The unit may have been installed incorrectly or the backplane cabling is faulty.INSTRUCTIONS : 1. Run the WCDMA BTS loop test.

2. Replace the units indicated in the alarm one by one and check whether the problem is cleared.

3. Check the backplane cables and connectors (see Troubleshooting instructions).




3. Reset the BTS.


FAULT NAME : WTR RT-bus faultMEANING : The bus clock signal is corrupted or missing in the RT bus. The signal frequency should be exactly half of the system clock frequency.INSTRUCTIONS : 1. Check the other active alarms.

2. Check the WSM, WSP and WTR.

Note! The problem can be in the unit connector, cabinet cabling or backplane.

FAULT NAME : WTR internal clock faultyMEANING : The WTR internal system clock is missing. This can be caused

168 DN99580892Issue 08C


Id:0900d80580727d78


by a missing or bad quality reference clock signal from the WSC, or a WTR unit HW failure. The transmitted and received frequencies are incorrect.INSTRUCTIONS : 1. Block/unblock the alarming unit.

2. Check backplane cables and connectors.


FAULT NAME : WTR internal clock faultyMEANING : The WTR VCXO PLL is not locked. This can be caused by a missing or bad quality reference clock signal from the WSC or a WTR unit HW failure. The transmitted and received frequencies are incorrect.INSTRUCTIONS : 1. Block/unblock the alarming unit.


3. Chcek the backplane cables and connectors.

FAULT NAME : WTR local oscillator not lockedMEANING : The TX IF synthesizer (common to both TX chains) cannot lock to the defined frequency.INSTRUCTIONS : 1. Block/unblock the alarming unit.


FAULT NAME : WTR synthesizer is not lockedMEANING : The TX & RX RF synthesizer or the RX IF synthesizer is not locked (or the RF synthesizer buffer amplifier is faulty). The output frequency of the transmitter can be wrong or missing, or the receiver might receive a wrong frequency or is not receiving.INSTRUCTIONS : 1. Block/unblock the alarming unit.


FAULT NAME : WTR temperature is highMEANING : The internal temperature of the WTR is dangerously high.INSTRUCTIONS : 1. Check the other active temperature or cooling fan-related alarms.

2. If you can find no reason, the sensor is probably broken. Replace the unit.


DN99580892Issue 08C

169

RNC Base Station Alarms (7000-7900) 7655 CELL NOTIFICATION

Id:0900d80580727d78

33 7655 CELL NOTIFICATIONMeaning

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




2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number





170 DN99580892Issue 08C


Id:0900d80580727d78


FAULT NAME : Antenna Line Device Operation FailureMEANING : The device is not working properly, the configuration is not valid, or a given parameter is incorrect.INSTRUCTIONS : 1. Check the functionality of the antenna line device.

2. Check the compatibility between the antenna line device and the BTS.

3. Check that the given parameters are in the valid range.







FlexiBTS:





DN99580892Issue 08C

171


Id:0900d80580727d78


UltraSite/EUBB:










FAULT NAME : External Filter missing from LCRMEANING : An external filter is missing from the antenna line.INSTRUCTIONS : Install an external filter to the antenna line.

FAULT NAME : File corrupted in SW downloadMEANING : The SW being downloaded is corrupted or incorrectly formed.INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:


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

FlexiBTS:


172 DN99580892Issue 08C


Id:0900d80580727d78


2. Save the snapshot and check the download status from the BTS SWDLreport in the snapshot file.

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



FAULT NAME : LCRs using same carrier frequencies mismatch in LCGsMEANING : Two cells with the same carrier belong to different local cell groups (LCGs). When baseband pooling is used, BTS baseband resources are divided between the different LCGs. Softer handover requires that cells with the same frequency in different sectors need to be assigned to the same LCG.

This alarm is reported to BTS Site Manager only.INSTRUCTIONS : Check the RNC parameters for the BTS cells and change them, if needed.

FAULT NAME : RF Module temperature value missingMEANING : The RF Module cannot report the temperature value or the sensor is faulty.INSTRUCTIONS : 1. Block/unblock the RF Module.


FAULT NAME : RF Test loop faultyMEANING : The RF Module cannot run the test loop.INSTRUCTIONS : 1. Block/unblock the RF Module and make the test loop again.


FAULT NAME : RF module optical interface confguration failureMEANING : The release 2 RF Module is connected to the system module using optical interface 2 that is not according to the user guidance. It is advised to use the optical interface 1.INSTRUCTIONS : Reconnect the alarming release 2 RF Module to the optical interface 1.

FAULT NAME : Rbus synchronization error

DN99580892Issue 08C

173


Id:0900d80580727d78

MEANING : Data traffic into Rbus uplink buffers is malfunctioning because of errors in the Rbus synchronisation clock. Either Rbus synchronization pattern not found or parity errors found in pattern.INSTRUCTIONS : 1. Reset BTS.


FAULT NAME : Telecom cell enabling or disabling failedMEANING : 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, MetroSite 50, Triple-mode:

1. Check the other active alarms if the WSP capacity has been decreased.

2. Check if there are enough WSP units.

FlexiBTS:

1. Check the other active alarms.

2. Check the number of FSP units.

UltraSite/EUBB:

1. Check the other active alarms if the WSPF capacity has been decreased.

2. Check if there are enough WSPF units.




3. Reset the BTS.


FAULT NAME : WSMA RR-Bus errorMEANING : The WSMA/WMC unit has detected errors in the incoming RR bus

174 DN99580892Issue 08C


Id:0900d80580727d78


from the WTR unit.

The WTR or WSMA/WMC unit may have been installed incorrectly or the backplane cabling is faulty.

This alarm is generated only once and reported to BTS Manager only.INSTRUCTIONS : 1. Check the WSM and Spider cabling.

2. Replace the WTR and WSMA/WMC units indicated in the alarm one by one.

FAULT NAME : WSMA SR-Bus errorMEANING : UltraSite: The WSM unit has detected errors in the incoming SR bus from the adjacent WSM unit. The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm.

Triple-mode: The WSM has detected errors in the incoming SR bus from the WTR unit. The reason for the failure is the WSM or WTR unit, or the cable between the WSM front panel and the backplane.

This alarm is generated only once and is reported to the BTS Site Manager only.INSTRUCTIONS : 1. Check the WSM cabling.

2. Remove/reinsert the alarming unit.

3. Check the other WSM units.

4. Replace the WSM units (and if that does not help, also the WTR units) indicated in the alarm one by one and check whether the alarm is cleared.

FAULT NAME : WTR loop synthesizer not lockedMEANING : The RF loop does not function.

The transmitter output signal is not downconverted to the receiver frequency.INSTRUCTIONS : 1. Try to perform the loop test again.



FAULT NAME : WTR synthesizer is not lockedMEANING : The TX & RX RF synthesizer or the RX IF synthesizer is not locked (or the RF synthesizer buffer amplifier is faulty). The output frequency of the transmitter can be wrong or missing,

DN99580892Issue 08C

175


Id:0900d80580727d78

or the receiver might receive a wrong frequency or is not receiving.INSTRUCTIONS : 1. Block/unblock the alarming unit.



176 DN99580892Issue 08C


Id:0900d80580727d78

7660 BASE STATION LICENCE EXPIRED

34 7660 BASE STATION LICENCE EXPIREDMeaning

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




2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number


InstructionsSee the BTS faults documents in WCDMA RAN and I-HSPA System Libraries fordetails about BTS licence management.

FAULT NAME : Licence expiration <featureCode>, <licenceName>MEANING : The licence for the given feature is expiring: - in one month, if the fault severity is warning - in one week, if the fault severity is minor - now, if the fault severity is major.INSTRUCTIONS : Activate the required license.


DN99580892Issue 08C

177

RNC Base Station Alarms (7000-7900) 7661 BASE STATION LICENCE NOTIFICATION

Id:0900d80580727d78

35 7661 BASE STATION LICENCE NOTIFICA-TIONMeaning

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




2 shelf number

3 slot

4 type of unit

5 unit number

6 subunit number


InstructionsSee the BTS faults documents in WCDMA RAN and I-HSPA System Libraries fordetails about BTS licence management.

FAULT NAME : Failure in licence activationMEANING : Generation of target Id failed and because of that correct validation of license files in BTS is not possible. BTSOM is restarted and in consequence during startup all license files are deleted from BTS. All optional features are either disabled or their capacity is reduced to the basic (not licensed) level.INSTRUCTIONS : Note! Perform the steps below in the listed order until the alarm disappears. 1. Reset the NetAct Licence Manager. 2. Reset the BTS. 3. Check the BTS licence situation: the correct licences have been purchased and installed.

178 DN99580892Issue 08C


Id:0900d80580727d78

7661 BASE STATION LICENCE NOTIFICATION

FAULT NAME : HW capacity too low for feature <licenceCode>, <licenceName>MEANING : The HW capacity is too low to support all licences of an optional feature.INSTRUCTIONS : Delete the licences or insert new hardware.

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

FAULT NAME : License missing <licenseCode>, <licenseName>MEANING : The BTS detected a resource needing a license but no license exists or is free.INSTRUCTIONS : An appropriate license should be activated or the license number should be increased.


DN99580892Issue 08C

179

RNC Base Station Alarms (7000-7900) 7665 BASE STATION TRANSMISSION ALARM

Id:0900d80580727d78

36 7665 BASE STATION TRANSMISSION ALARMMeaning

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

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

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

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

Supplementary information fields1 probable cause reported by FTM

2 the managed object reported by FTM

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

InstructionsThis alarm is an encapsulation alarm for original FTM alarm.

Follow up the instructions given in the BTS faults documents in WCDMA RANand I-HSPA System Libraries for the alarm number shown in supplementaryinformation field 3.

FAULT NAME : $Protocol Timing source lost on unit $U , interface $IFMEANING : One of the synchronisation sources in the configured priority list is unavailable. This can be the primary or the secondary clock source.

In the alarm: Protocol can be PDH, SDH, Timing over Packet (ToP) and

180 DN99580892Issue 08C


Id:0900d80580727d78


Synchronuous ethernet. Unit number is always 1. The interface value is optional: - For PDH and SDH the value range depends on the hardware unit type: 1..16 - For Synchonuous Ethernet the value range = 1..3 - It is not present for Timing over Packet.INSTRUCTIONS : Use BTS Site Manager to check which interfaces have been configured as synchronization sources.

For all interfaces, do as follows:

1. Check that the cables are connected to the correct connectors. 2. Check whether the interface at the far end is switched on. 3. Check whether there are active alarms at the far end. If there are, follow the instructions on handling those alarms. 4. To verify that the hardware of the interface unit works correctly, connect a loop cable and check whether the alarm disappears.

Monitor the received clock quality.

FAULT NAME : AIS (Administrative Unit) on unit $U, interface $IFMEANING : Alarm indication signal on the Administrative Unit. The SDH interface receives an AU-AIS (Administrative Unit - Alarm Indication Signal). This signal is generated by an intermediate SDH device in the forward direction because it detects a problem in its receive signal. All other transmission alarms related to this signal are suppressed.

Probable cause: There is a transmission problem somewhere in the intermediate network and AIS is sent instead of user traffic.INSTRUCTIONS : Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

FAULT NAME : AIS (Multiplexer Section) on unit $U, interface $IFMEANING : Alarm indication signal on the Multiplexer Section. The SDH interface receives an MS-AIS (Multiplexer Section - Alarm Indication Signal). This signal is generated by an intermediate SDH device in the forward direction because it detects a problem in its receive signal.

All other transmission alarms related to this signal are suppressed.

Probable cause: there is a transmission problem somewhere in the intermediate network and AIS is sent instead of user traffic.

DN99580892Issue 08C

181


Id:0900d80580727d78

INSTRUCTIONS : Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

FAULT NAME : AIS on unit $U, interface $IFMEANING : Alarm indication signal is received. This signal is generated by an intermediate PDH device in the forward direction because it detects a problem in its receive signal.

All other transmission alarms related to this signal are suppressed.

Probable cause: There is a transmission problem somewhere in the intermediate network and AIS is sent instead of user traffic.INSTRUCTIONS : Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

FAULT NAME : BFD DOWNMEANING : The alarm is raised if the BFD service is not available anymore on the BTS. In case only 1 BFD session is configured and activated, the alarm is raised if BFD on this session fails in either ingress or egress direction. In case 2 BFD sessions are configured and activated, the alarm is raised if there is a simulanuous BFD failure on both sessions only. The BFD failure for each session might be either on ingress or egress direction.INSTRUCTIONS : 1) Check if the far end has BFD switched on. 2)Check cabling and network connections to the far end.

FAULT NAME : BFD Session down in egress direction for session $SMEANING : The alarm is raised if the alarm is enabled, the BFD state is not AdminDown, the BFD packet from the far end contains the diagnostic code = 'Control Detection Time Expired' AND no ingress alarm is present.INSTRUCTIONS : Check if the far end has BFD switched on.

FAULT NAME : BFD Session down in ingress direction for session $SMEANING : The alarm is raised if the alarm is enabled, the BFD state is not AdminDown and no BFD packet is received at the local end during the detection time.INSTRUCTIONS : 1. Check the network between both BFD peers for physical link failures or misconfigurations.

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

FAULT NAME : BTS reset requiredMEANING : A change to the BTS IP settings has been received from TRS Manager. The user has to confirm the changes after the last

182 DN99580892Issue 08C


Id:0900d80580727d78


BTS IP settings have been given. The confirmation is needed so that the BTS IP settings are taken in use through a BTS reset.INSTRUCTIONS : Confirm the changes when all the required BTS IP settings have been made.

FAULT NAME : CES pseudowire $W down on unit $UMEANING : The alarm is raised if the CES pseudowire is in 'Up' state, but the number of received packets in the CES pseudowire is less than 10 relative to the expected number of packets for 1 second.

The alarm is not be raised, if the CES pseudowire is in 'Init' state.INSTRUCTIONS : 1. Check that the cables are connected to the correct connectors.

2. Check that the interface at the far-end interface is switched on.

3. Check whether there are active alarms at the far end. If there are, follow the instructions for handling those alarms.

4. Check the configuration of the CES pseudowire.

FAULT NAME : CES pseudowire remote packet loss on wire $W on unit $UMEANING : This alarm is raised if the packet loss condition for packets of the given CES pseudowire persists for more than 1 second in ingress.

The packet loss condition is defined as follows: The CES over PSN pseudowire function is capable to detect lost and misordered packets. The sequence number in the control word is used for these purposes. The CES over PSN pseudowire function shall reorder misordered packets. Misordered packets that cannot be reordered, shall be discarded and treated as lost.

INSTRUCTIONS : 1. Check that the cables are connected to the correct connectors.



4. Check the configuration of the CES pseudowire.

FAULT NAME : CES pseudowire tunnel $T down on unit $UMEANING : This alarm is raised if a CES pseudowire tunnel is in 'Up' state, but no IP packets were received on the tunnel in the

DN99580892Issue 08C

183


Id:0900d80580727d78

last second.

The alarm is not raised in case the CES pseudowire tunnel is in 'Init' state.

In case that all CES pseudowires of the tunnel are taken out of use by the operator, also no "PW tunnel down" alarm is raised even wenn the CES pseudowire tunnel is still configured.INSTRUCTIONS : 1. Check that the cables are connected to the correct connectors.



4. Check the configuration of the related CES pseudowires.

FAULT NAME : Certificate does not existMEANING : A requested certificate could not be retrieved from the certificate repository server (RA) or certificate authority (CA).INSTRUCTIONS : Provide the certificate.

FAULT NAME : Config-abort state on unit $U, IMA Group $IMAGMEANING : Configuration abort state. This alarm is raised when the far end tries to use unacceptable configuration parameters. All other transmission alarms related to this signal are suppressed.

Probable cause: The IMA group configuration is wrong (for example, the IMA versions are incompatible).INSTRUCTIONS : Check that the configurations at the near end and far end fit together (for example, IMA version and frame length). Change the configuration, if necessary.

FAULT NAME : DSCP $D signalled but not configuredMEANING : DSCP $D signalled but not configured. $D specifies the first mismatch DSCP value.

The combination of RNC and NodeB is misconfigured with regard to quality of the service configurations.INSTRUCTIONS : 1. Check the configured DSCP value ranges in the RNC.

2. Check the configured DSCP value ranges in the BTS.

3. Ensure that both match each other.

FAULT NAME : EBER on unit $U, interface $IF

184 DN99580892Issue 08C


Id:0900d80580727d78


MEANING : Excessive bit error rate. The measured bit error rate exceeds the threshold value of BER-3 (10E-3).

Probable causes: - the signal level is too low (optical connectors or cables are dirty, electrical connectors or cables are corroded) - the specified maximum length of the cable is exceeded - the connector is not properly connected to the unit - the receiver or the far end transmitter has failedINSTRUCTIONS : 1. Clean the cables and connectors.

2. Check that the connectors are properly connected to the unit.

3. Check that the cable connected to the interface in question is not damaged and is within the specifications.

4. Follow the signal in the network and check whether any other alarms concerning the fault are on (such as Laser End of Life). If this is the case, follow the instructions for handling those alarms.

FAULT NAME : Far end config-abort state on unit $U, IMA Group $IMAGMEANING : Far end configuration abort state. This alarm is raised when the far end reports unacceptable configuration parameters. All other transmission alarms related to this signal are suppressed.

Probable cause: The IMA group configuration is wrong (for example, the IMA versions are incompatible).INSTRUCTIONS : Check that the configurations at the near end and far end fit together (for example, IMA version and frame length). Change the configuration if necessary.

FAULT NAME : Far end group start-up on unit $U, IMA Group $IMAGMEANING : Far end group start-up. This alarm is raised when the far end indicates that it is in the start-up phase. The alarm is typically active only temporarily.

Probable cause: The IMA group at the far end is not yet up and running.INSTRUCTIONS : If the alarm is on only temporarily, no action is needed.

If the alarm stays active, check whether any other alarms related to this fault are on (such as problems on individual IMA links). If this is the case, follow the instructions for handling these alarms.

FAULT NAME : Far end insufficient links on unit $U, IMA Group $IMAGMEANING : Far end insufficient links. The far-end IMA group reports that there are less IMA links in the far-end IMA group than

DN99580892Issue 08C

185


Id:0900d80580727d78

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 highINSTRUCTIONS : 1. Check the individual IMA links in the IMA group for problems. If needed, correct them.

2. Configure additional IMA links to the IMA group.

3. If feasible, reduce the minimum number of IMA links in the IMA group.

4. Check that the configurations at the near end and far end fit together. Change the configurations if necessary.

FAULT NAME : Far-end receive link unusable on unit $U, interface $IFMEANING : Far-end receive link unusable. The IMA link is not yet in an IMA group. The alarm is typically raised only temporarily during IMA configuration and disappears when the configuration has been completed. There are usually other IMA-related alarms active at the same time.

Probable cause: IMA configuration is incomplete at the far-end interface.INSTRUCTIONS : Ensure that the far-end IMA link is configured to be part of an IMA group.

FAULT NAME : Far-end transmit link unusable on unit $U, interface $IFMEANING : Far-end transmit link unusable. The IMA link is not yet in an IMA group. The alarm is typically raised only temporarily during IMA configuration and disappears when the configuration has been completed. There are usually other IMA-related alarms active at the same time.

Probable cause: IMA configuration is incomplete.INSTRUCTIONS : Ensure that the IMA link is configured to be part of an IMA group.

FAULT NAME : Five failed logins to FTM due to wrong user name or passwordMEANING : Five consecutive failed login attempts to the FTM have been performed.INSTRUCTIONS : Check your username and password.

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

186 DN99580892Issue 08C


Id:0900d80580727d78


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 NAME : IMA link out of delay synchronization on unit $U, interface $IFMEANING : Link out of delay synchronisation. A LODS defect is reported when the link differential delay between the link and the other links in the group is higher than the tolerable link differential delay.

Probable causes: - the configuration of the IMA group is incomplete or faulty - there is disturbance on the line - the differential delay of the IMA links belonging to one IMA group is too highINSTRUCTIONS : Do as follows for the interface referenced in the alarm text:

1. Verify that the IMA configuration of the near end and far end is correct.

2. Check the physical line for errors.

3. Check the delay of the IMA link in question. If necessary, select another suitable link.

FAULT NAME : IMA remote failure indication on unit $U, interface $IFMEANING : Remote failure indication. An IMA-related remote defect has been detected. A Loss of IMA link (LIF) or Link out of delay synchronisation (LODS) alarm is active at the far end of the IMA link.

Probable causes: - disturbance on the line - physical link defect - loss of IMA frame - loss of delay synchronisationINSTRUCTIONS : Follow the instructions for handling the alarms raised at the far end of the IMA link.

DN99580892Issue 08C

187


Id:0900d80580727d78

FAULT NAME : Insufficient links on unit $U, IMA Group $IMAGMEANING : Insufficient links. There are less operable IMA links in the IMA group than the minimum number of IMA links required. The IMA group referenced in the alarm text may not be able to carry all required traffic.

Probable causes: - IMA links within the IMA group are out of order - there are not enough IMA links configured for the IMA group at the far end - the value for the parameter Minimum number of links is set to be too highINSTRUCTIONS : 1. Check the individual IMA links in the IMA group for problems. Correct them if necessary.

2. Configure additional IMA links to the IMA group.

3. If feasible, reduce the minimum number of IMA links in the IMA group.

4. Check that the configurations at near end and far end fit together. Change the configurations if necessary.

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

FAULT NAME : LOCD on unit $U, interface $IFMEANING : Loss of ATM cell delineation. The network interface receives frames whose ATM cells cannot be recognised. It is not possible to carry traffic on the interface referenced in the alarm text.

Probable causes: - the far-end frames do not have ATM cell mapping - the far end does not insert idle cells - there are disturbances in the traffic of the physical transmission link in questionINSTRUCTIONS : 1. Ensure that the far end is using ATM cell mapping.

2. Check whether any other alarms concerning the fault are on. If this is the case, follow the instructions on handling those alarms.

3. If the alarm is on only temporarily, no action is needed.

FAULT NAME : LOF on unit $U, interface $IFMEANING : Loss of frame. It is not possible to carry traffic on the interface referenced in the alarm text. All other transmission

188 DN99580892Issue 08C


Id:0900d80580727d78


alarms related to this signal are suppressed.

Probable causes for STM-1/STS-3c interfaces: - the SDH/SONET interface receives frames that have an incorrect frame pattern (A1 and A2 bytes) - the configuration of the framing (STM-1 or STS-3c) on the far-end interface does not match the configuration on the interface referenced in the alarm text - too low an input level

Probable cause for E1 interfaces: The interface at the far end is not configured to be a framed E1 interface.

Probable cause for JT1 interfaces: The interface at the far end is not configured to be a JT1 interface.INSTRUCTIONS : E1 interfaces: Check that the interface type of the far-end interface is also configured to be a framed E1 interface. If this is not the case, reconfigure the interfaces so that they match each other.

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

FAULT NAME : LOMF on slot $U, interface $IFMEANING : Loss of multiframe. The interface referenced in the alarm text has lost the multiframe alignment.

Probable cause: the interface type has not been configured to meet the framing of the interface at the far end. For E1 interfaces, the configuration of the far-end node should be E1 Multiframe.INSTRUCTIONS : Check that the configured interface type matches the configured interface type of the far end. If this is the case, the problem is somewhere in the transmission network.

FAULT NAME : LOP (Administrative Unit) on unit $U, interface $IFMEANING : Loss of Pointer for the Administrative Unit. This alarm occurs when the SDH interface receives frames that have an incorrect Administrative Unit (AU) pointer. All other transmission alarms related to this administrative unit are suppressed.

Probable cause: there are disturbances in the traffic on the link in question.INSTRUCTIONS : Check the intermediate VC-12 transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

FAULT NAME : LOS on unit $U, ethernet interface $IFMEANING : No signal is received on the interface referenced in the alarm

DN99580892Issue 08C

189


Id:0900d80580727d78

text. All other transmission alarms related to this signal are suppressed.

Probable causes for PDH interfaces: - a cable is cut or there is no cable connected to the interface - the electrical signal is excessively attenuated - the port at the connected far-end node is switched off - transmit and receive cables are mixed up

Probable causes for Ethernet interfaces: - a cable is cut or there is no cable connected to the interface - the electrical signal is excessively attenuated - the port at the connected far end node is switched offINSTRUCTIONS : 1. Check that the cables are connected to the correct connectors.



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

FAULT NAME : License missing for feature $feature on interface $ifMEANING : 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.

This BTS fault can be displayed in the followings variants: License Missing for Additional 2 E1, T1, JT1 interface License Missing for IMA License Missing for UBR+ License Missing for ATM over Ethernet License Missing for Timing Over Packet License Missing for Synchronous Ethernet License Missing for VLAN Traffic Differentiation License Missing for CES over PSN License Missing for second Flexbus interface License Missing for colocation Flexbus interface License Missing for Flexbus ethernet interface

INSTRUCTIONS : Download a valid licence to the WBTS.

190 DN99580892Issue 08C


Id:0900d80580727d78


FAULT NAME : Loss of IMA frame on unit $U, interface $IFMEANING : Loss of an IMA frame. The loss of an IMA frame was detected in one link of the IMA group. The far-end IMA link is not part of an IMA group.

All other transmission alarms related to this IMA link are suppressed.

Probable causes: - the configuration of the IMA group is incomplete or faulty - there is disturbance on the lineINSTRUCTIONS : Do as follows for the interface referenced in the alarm text:

1. Verify that the IMA configuration of the near end and far end is correct.

2. Check the physical line for errors.

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

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

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

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

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

FAULT NAME : RDI (High Order Path) on unit $U, interface $IFMEANING : Remote defect indication on the High Order Path (VC-3/VC-4).

DN99580892Issue 08C

191


Id:0900d80580727d78

This alarm occurs when the equipment at the far end of a bidirectional VC-3/VC-4 connection has detected an error condition on the signal that it is receiving. The far-end equipment signals this remote defect in the signal that it transmits.

The RDI indicates a serious fault in the received signal of the far-end equipment.

Probable cause: The far end has active alarms on its receiving interface (such as LOS, LOF, TIM-RS, AIS-MS, AIS-AU, LOP-AU, TIM-HP, UNEQ-HP).INSTRUCTIONS : 1. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

2. To check the transmit hardware, connect a loop cable and check that LOS alarm is not raised.

FAULT NAME : RDI (Multiplexer Section) on unit $U, interface $IFMEANING : Remote defect indication (RDI) on the Multiplexer Section (MS). This alarm occurs when the equipment at the far end of a bidirectional multiplexer section connection has detected an error condition on the signal that it is receiving. The RDI indicates a serious fault in the received signal of the far-end equipment.

Probable cause: The far end has active alarms on its receiving interface (such as LOS, LOF, TIM-RS, AIS-MS, AIS-AU, LOP-AU).INSTRUCTIONS : 1. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

2. To check the transmit hardware, connect a loop cable and check that LOS alarm is not raised.

FAULT NAME : RDI on unit $U, interface $IFMEANING : Remote defect indication. It is sent by the intermediate or the far end equipment, because it detects a serious fault in the received signal.

Probable cause: The far end has a LOS, LOF or AIS alarm on its receiving interface.INSTRUCTIONS : 1. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms.

2. To check the transmit hardware, connect a loop cable and check that no alarms appear for this interface.

FAULT NAME : Routing misconfiguration for application $a

192 DN99580892Issue 08C


Id:0900d80580727d78


MEANING : A routing misconfiguration was detected. A packet was sent over an IP interface for which it was not intended, as configured in the VLAN traffic path map. E.g. a user-plane packet was sent over an interface that is intended for control plane traffic. Since the interface selection is based on the routing table entries, a misconfiguration of the routing table is suspected.INSTRUCTIONS : Correct the routing table or change the settings of the VLAN traffic path map.

FAULT NAME : STC connection to signalling peer not established on interface $MEANING : The SSCOP link controlled by this STC is down. The alarm text specifies the slot, port, VPI and VCI number in question.

Probable causes: - the peer (RNC) releases the connection - the link goes down because the peer (RNC) does not respond within the TIMER_NO_RESPONSE period. - the link was never established - problem on the ATM layer - problem on the physical layer - incomplete or faulty configuration of AAL2 in the RNCINSTRUCTIONS : 1. Check that there are no other active alarms on the physical or ATM layer.

2. Check that the RNC is up and running.

3. Check the AAL2 configuration. For example, make sure that the VPs/VCs used for AAL2 signalling in the RNC and WBTS match.

FAULT NAME : Synchronisation lostMEANING : Primary and secondary timing source lost. The WBTS is running on internal clock or in hold-over mode and no timing signal is sent.

The first and second synchronisation sources from the configured priority list are unavailable. On failure, the WBTS switches automatically to the next clock source in the priority list.

Probable cause: The transmission links selected for clock source are faulty. The reason can be alarms on the interfaces (for example, LOS, LOF or AIS).INSTRUCTIONS : Use the BTS Site Manager to check which interfaces have been configured as synchronization sources.

DN99580892Issue 08C

193


Id:0900d80580727d78

For the PDH interfaces, do as follows:

1. Check that the cables are connected to the correct connectors.

2. Check whether the interface at the far end is switched on.

3. Check whether there are active alarms at the far end. If there are, follow the instructions on handling those alarms.

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

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

FAULT NAME : UNEQ (High Order Path) on unit $U, interface $IFMEANING : High Order Path Unequipped. The path signal label byte (C2) and the path trace byte (J1), and BIP-8 byte (B3) in the SDH path overhead (POH) all have the value zero. The path is unusable for traffic transport.

Probable cause: the unequipped VC-3/VC-4 comes from a VC-level cross-connection node and the VC-3/VC-4 is not connected anywhere in that node.INSTRUCTIONS : 1. Check the configuration and ensure that the cross-connections between the nodes have been properly configured for transporting traffic.

2. Ensure that the Path Payload Label for the VC-3/VC-4 at the far end is configured to be "ATM".

3. Follow the signal in the network and check whether any other alarms concerning the fault are active. If this is the case, follow the instructions for handling those alarms.

FAULT NAME : VLAN $V signalled but not configured.MEANING : VLAN $V signalled but not configured. $V specifies the first mismatch VLAN ID.

The combination of RNC and NodeB is misconfigured with regard to quality of the service configurations.INSTRUCTIONS : 1. Check the configured VLAN IDs in the RNC.

2. Check the configured VLAN IDs in the BTS.

3. Ensure that both match each other.

194 DN99580892Issue 08C


Id:0900d80580727d78



DN99580892Issue 08C

195

RNC Base Station Alarms (7000-7900) 7740 BEATING WCDMA BTS ALARM

Id:0900d80580727d78

37 7740 BEATING WCDMA BTS ALARMMeaning

The same radio network alarm has changed its alarm state (start/cancel)20 times consecutively, always during informing or cancelling delay,and has thus been filtered by the alarm system. The same radio networkobject is the object of both this alarm and the beating alarm thatcaused this alarm.

Supplementary information fields1 the alarm number of the beating BTS alarm

2-15 if the beating alarm has any additional information, it is indicated here. Additional information is cut after 14 bytes and it is represented in hexadecimal format.

InstructionsCorrect the fault that caused the original beating alarm. You canfind the number of that alarm in Supplementary information field 1.


196 DN99580892Issue 08C


Id:0900d80580727d78

7750 FAILURE IN WCDMA WBTS O&M CONNEC-TION

38 7750 FAILURE IN WCDMA WBTS O&M CON-NECTIONMeaning

This alarm indicates that a failure has occurred in WBTS O&Mconnection. The problem is related to Iub connection between RNCand WBTS.From RNC point of view the actual reason for the failure is eitherin transmission network between network elements (Iub), in internalcommunication of RNC applications or in WBTS configuration.

In Iub connection problem between RNC and WBTS this alarm is set byOMU 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

As a consequence of this alarm, the availability of WBTS O&Mfunctionality may be limited.

User initiated or automatic O&M tasks (e.g. SW download, HWconfiguration request and WBTS restart) cannot be performed in caseof Iub O&M connection problem. It is also not possible for the WBTSto report its alarms to RNC.

This alarm does not indicate a failure in WBTS user plane links. Thestates of the user plane links can be checked using RNC RNW ObjectBrowser.

Supplementary information fields1 reason of the alarm

1 = failure in the RNC-WBTS connection 2 = WBTS id conflict

2 error code is received from IUB O&M connection. This field is significant only if the value of 1st field is 1

You can check its meaning 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

InstructionsError reason (field 1) indicates which part of the connection theproblem is located.

DN99580892Issue 08C

197

RNC Base Station Alarms (7000-7900) 7750 FAILURE IN WCDMA WBTS O&M CONNEC-TION

Id:0900d80580727d78

Error code (field 2) indicates what caused the problem if the errorreason (field 1) value is 1.

Error reason = 1, failure in the WBTS connection

Error code: 14005 = CONNECTION RESET BY PEER WBTS has closed 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. 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 codes: 14001 = NETWORK IS DOWN 14011 = OPERATION TIMED OUT 14015 = HOST IS DOWN

There are problems in transmission network to WBTS.

198 DN99580892Issue 08C


Id:0900d80580727d78


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.


Error code: 14051 = POSIX ERROR 100

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

DN99580892Issue 08C

199

RNC Base Station Alarms (7000-7900) 7750 FAILURE IN WCDMA WBTS O&M CONNEC-TION

Id:0900d80580727d78

This error code is used if OMU unit switchover has occurred in the RNC and O&M connection to the WBTS has been closed because of that. The WBTS O&M connections are always handled by the OMU unit in WO-EX state so in switchover case the connections are closed.

Wait until WBTS opens the O&M connection again and system cancels this alarm.

Any other error code: Contact the local Nokia Siemens Networks representative.

Error reason = 2, WBTS id conflict

More than one WBTS has been configured with the same id.

Error code: 255 = UNSUCCESSFUL

An O&M connection for a WBTS id already exists in the RNC. This alarm was set because the same WBTS id was used in new O&M connection establishment from a different IP address that already existing connection was established from. This happens if several WBTS have been configured with the same WBTS id under the same RNC. The supplementary text of alarm gives IP address of the conflicting WBTS.

Use BTS Manager to connect the conflicting WBTS with its IP, configure it with a different id. Depending on the WBTS release, the reconfiguration may need to be done using AXC Manager.

Cancel the alarm manually after resolving the WBTS id conflict.

CancellingDo not cancel the alarm with error reason 1. The system cancelsthe alarm automatically when the fault has been corrected.The alarm with error reason 2 must be canceled manually.

Error reason = 1 Alarm will be canceled when BTS O&M connection is working again.

Error reason = 2 Alarm must be canceled manually with MML command AAN or with Fault Management application in RNC Element Manager after

200 DN99580892Issue 08C


Id:0900d80580727d78


conflicting WBTS id situation is corrected.

DN99580892Issue 08C

201

RNC Base Station Alarms (7000-7900) 7761 RNW O&M SCENARIO FAILURE

Id:0900d80580727d78

39 7761 RNW O&M SCENARIO FAILUREMeaning

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 oroperation performed by the system. User operation can be, forexample, WCEL creation with RNC Object Browser or by plan.Operations performed by the system are in most cases related torecovery operations, for example common channel supervision.

In general all failures causes the cell(s) to be blocked and henceunavailable to traffic.

Failure in cell blocking can lead to erroneous cell stateinformation in the RNC.

Failure in WBTS capability updating or pid updating can causeincorrect WBTS capability data to be used in the RNC and thusproblems in signalling or actual calls.

Failure in User plane configuration (AAL2 path unblocking) causes asituation where the User plane traffic can not be transferred inthe corresponding AAL2 VCC.

Supplementary information fields1 reason for the failure

01 WBTS reservation has failed 02 Configuration data updating has failed 03 Inactivation of the cell has failed 04 Activation of the cell has failed 05 Common channel deletion has failed

202 DN99580892Issue 08C


Id:0900d80580727d78


06 Common channel creation has failed 07 BCCH information updating has failed 08 WBTS capability information was not received 09 Forced handover request was not accepted 0A WBTS capability information update has failed 0B AAL2 path unblocking has failed 0E Unknown NBAP interface type 11 Audit has failed, only 3GPP iub 12 Cell setup procedure has failed, only 3GPP iub 13 Cell deletion procedure has failed, only 3GPP iub 14 Common measurement initiation has failed, only 3GPP iub 15 RRI measurement initiation has failed, only 3GPP iub 16 Cell reconfiguration procedure has failed, only 3GPP iub 18 Common or RRI measurement termination failed, only 3GPP iub 19 Cell barring has failed 20 COCO disconnect has failed 21 COCO connect has failed

2 scenario that was being carried out when the failure occurred

00 Not specified 01 WBTS initialization, Nokia Siemens Networks iub 02 Cell unlocking, Nokia Siemens Networks iub 03 Configuration data modification, Nokia Siemens Networks iub 04 RNC restart, Nokia Siemens Networks iub 05 Local cell resource state change 06 Forced handover 07 WBTS reset initiation from RNC 08 WBTS capability information update 09 Pid update 0A Connection configuration management 0B Audit handling, 3GPP iub 0C CCH Supervision 0D WBTS recovery 0E Iu service barring 0F Cell deletion, 3GPP iub 81 WBTS initialization, 3GPP iub 82 Cell unlocking, 3GPP iub 83 Cell reconfiguration, 3GPP iub 84 RNC restart, 3GPP iub 8D WBTS restart, 3GPP iub 8E WBTS cell block, 3GPP iub 8F WBTS cell unblock, 3GPP iub 90 Resource status indication handling, 3GPP iub 91 Common measurement supervision 92 Dedicated measurement initiation 93 Cell activation due to power save 94 Cell shutdown due to power save

3 general error code of the system

DN99580892Issue 08C

203


Id:0900d80580727d78


4 ATM interface identifier of network external or internal interface. This field is significant only in case of User plane configuration fault.

FFFF Not specified

5 virtual path identifier. This field is significant only in case of User plane configuration fault.

FFFF Not specified

6 virtual channel identifier. This field is significant only in case of User plane configuration fault.

0 Not specified

InstructionsThis instruction contains five main steps. The first four steps arespecific to certain failure situations. The last step is a generaloperating procedure for all other failures indicated by this alarm.It is also a default procedure to be performed if instructions givenin previous steps do not solve the problem.Abbreviation SIF refers to supplementary information field.

Step 1: In case the value of SIF 2 (scenario) is 07 (WBTS reset): - First, verify using 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.

204 DN99580892Issue 08C


Id:0900d80580727d78


Locked ATM resources will prevent the connection 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:

DN99580892Issue 08C

205


Id:0900d80580727d78

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

If the alarm still remains active after the steps above, and noobvious reason behind it can be found, collect at least thefollowing logs and contact the local Nokia Siemens Networksrepresentative: - 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 beperformed.

More information about the exact failure reason can be found byexamining the supplementary info field 3 (error code). You can checkits meaning with a command of the service terminal extension MRS(see Service Terminal Essentials, Maintenance Manual) or from thedocument General Error Messages of System, Supplementary References.

In many cases there is also more information in OMU computer log. Itcan be studied with MML-command ZDDE::"ZGSC";


206 DN99580892Issue 08C


Id:0900d80580727d78


40 7762 RNW DATABASE OPERATION FAILUREMeaning

RNW database operation has failed. This reading or writing operationwas 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 wherecell state could not be modified from blocked to working state orvice versa in RNC or it was not possible to send configuration datato WBTS. Failure in pid updating can cause troubles to other O&Mscenarios where that information is needed, and failure in WBTScapability updating or cch parameter updating can cause inconsistentdata to be used in RNC and thus problems in signalling or in actualcalls.

Supplementary information fields1 specifies if the error occurred during reading from or writing to database

01 Reading failure 02 Writing failure

2 reason of the failure

00 Not specified 01 Failure at initialization 02 Configuration data 03 Inactivation of the cell has failed 04 Activation of the cell has failed 05 NBAP-link state updating failure 11 Failure in cell setup, 3GPP iub 12 Failure in cell reconfiguration, 3GPP iub

DN99580892Issue 08C

207

RNC Base Station Alarms (7000-7900) 7762 RNW DATABASE OPERATION FAILURE

Id:0900d80580727d78

3 scenario that was being carried out when the failure occured

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

4 general error code of the system.


InstructionsAt first check the functionality of Radio Network database withfollowing MML-commands:ZDBS:RAQUEL,0;State of database should be normal and memory (and disk) updates arenot prevented. If updates are prevented, you can resume them withcommand ZDBR:RAQUEL,0:<mem or disk>;If database state is "waiting for dumping" or "dumping", databaseshould return to normal state automatically after dumping is ready.Also status of the disk updating system can be check withMML-command ZDBD:OMU; Line "RAQUEL" specifies the state of RadioNetwork database.

If database state is working (or becomes working after while), do asfollows:Try to lock the cell and then unlock the cell with RNC

208 DN99580892Issue 08C


Id:0900d80580727d78


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 appearsconstantly for several WBTSs and cells, contact the local NokiaSiemens Networks representative. Also RNC reset might help ifit is possible to make.

More information about the exact fail reason can be found byexamining the supplementary info field 4 (error code).In many cases there also more info in OMU computer log. It can bestudied with MML-command ZDDE::"ZGSC";


DN99580892Issue 08C

209

RNC Base Station Alarms (7000-7900) 7771 WCDMA CELL OUT OF USE

Id:0900d80580727d78

41 7771 WCDMA CELL OUT OF USEMeaning

The alarm indicates that an unlocked WCDMA cell has been blocked forsome reason, and it cannot transmit any traffic. This alarm is setonly when a cell is moved to the blocked state by the system,meaning that a user initiated state change will not cause thisalarm.

The alarm is set when one of the following situations occurs: 1. WCEL state is changed from - WO -> BL(B), bl- WBTS - WO -> BL(S), bl- system failure - WO -> BL(I), bl- init - WO -> BL(L), bl- C-NBAP link failure - WO -> BL(M), bl- Common measurement failure - WO -> BL(Ub), bl- Blocked by user locally from WBTS

It is possible that the WCEL state changes first from WO to BL(H) (bl - shutting down) and only after that to one of the above mentioned states. This alarm will not be set when the WCEL state changes from WO to BL(H), but it will be set when the BL(H) state is replaced by one of the above mentioned blocked states.

2. WCEL is unlocked and the COCO connection operation has been performed, but the state of the WCEL does not change to WO.

3. COCO connection operation has been performed, the WCEL has been unlocked, but the state of the WCEL does not change to WO.

4. An incorrect Local Cell Resource id has been given to this cell. Such Local Cell does not exist in the WBTS.

5. The NEType indicated by the BTS and the NBAP Communication Mode configured in the RNC for the WBTS object do not match

The alarm is cancelled automatically when the state of the WCELchanges back to WO or when the cell is locked by the user.

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

210 DN99580892Issue 08C


Id:0900d80580727d78

7771 WCDMA CELL OUT OF USE

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

2 general error code of the system.

You can check its meaning from General Error Messages of System.

InstructionsFirst task: wait for 5 minutes. Typically there is still somerecovery operation ongoing. The alarm will be cancelled if therecovery is successful.

If the automatic recovery does not correct the situation, followthese steps: 1. If the blocking reason in the supplementary information field 1 (WCEL state) is 0008 (BL(B)) or 0200 (BL(Ub)), check the WBTS alarm that is related to this WCEL, and follow the operating instructions there.

2. If the blocking reason in the supplementary information field 1 (WCEL state) is 0400 (BL(N)), an incorrect Local Cell Resource id has been given to this cell. Such Local Cell does not exist in the WBTS. The cell data must be corrected and, after that, a WBTS reset is required in order to remove the problem.

3. If the blocking reason in the supplementary information field 1 (WCEL state) is 0040 (BL(I)) and the value in the supplementary information field 2 (Error code) is 4434 (nbapcmode_netype_mismatch_ec), the NBAP Communication Mode and the Netype do not match. Check the WBTS alarm related to this WCEL, and follow its operating instructions.

4. In case there are no alarms targeted to the WCEL, try to lock and then unlock the cell manually with the RNC Object Browser. This way the system will try to clear the possible hanging cell related resources and then recreate (init) them.

5. If the alarm is not cancelled by the lock/unlock cell operation, you can try some of the following actions (the WBTS will be unavailable during these operations). These operations first clear and the recreate the BTS related resources: - reset the WBTS with the RNC Object Browser, or - reform the connection between the WBTS and the COCO by first disconnecting the COCO and then reconnecting it (this can be

DN99580892Issue 08C

211

RNC Base Station Alarms (7000-7900) 7771 WCDMA CELL OUT OF USE

Id:0900d80580727d78

done by changing the used COCO id in the WBTS with the RNC Object Browser), or - block/unblock the BTS with the BTS element manager.

If the alarm is still active after the above operations have been performed, and no obvious reason behind it can be found, collect at least the following logs and contact the local Nokia Siemens Networks representative: - OMU computer log (service terminal command ZGSC), - message monitoring from OMU (families 50B, 4FA, 4EE and 4EF) and the serving ICSU (check the serving ICSU from the COCO data in the RNC Object Browser, monitor families 4FE, 4FB, 4FD, 4B7) during the BTS reset.

Also an RNC reset might help if it is possible to make that.

More information about the exact fail reason can be found byexamining the supplementary information field 2 (error code). You cancheck its meaning with a command of the service terminal extensionMRS (see Service Terminal Essentials), or from the document GeneralError Messages of System.

In many cases there is also more information in the OMU computer log.It can be studied with the MML command ZDDE::"ZGSC";

CancellingDo not cancel the alarm. The system cancels the alarm automaticallywhen the fault has been corrected. The alarm is cancelled by systemif the cell in question starts to work again or it is locked byuser.

212 DN99580892Issue 08C


Id:0900d80580727d78


42 7772 HSDPA CONFIGURATION FAILEDMeaning

This alarm indicates that there has been an error when RNC has requestedconfiguration or reconfiguration of HSDPA channels to BTS via PhysicalShared Channel Reconfiguration procedure.

The causes which result in this alarm are:

- a problem in transmission network between RNC and BTS- BTS has rejected the configuration or reconfiguration 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 and the nature of the failure can be determined from thesupplementary information fields of this alarm.

The consequence of this alarm depends on the HSDPA configuration phase.- In case the initial configuration of HSDPA channels fails, the effect is that HSDPA connections cannot be used in this particular cell at all. In this case also the HSUPA connections are unavailable if HSUPA is enabled in the cell.- In case of reconfiguration of HSDPA channels the effect is that the cell may not work with intended HSDPA parameters.


Possible values: 01 = No reply from BTS 02 = BTS rejects the configuration 03 = RNC internal error

2 computer unit where this alarm is generated from

3 index of the alarming unit

4 more detailed cause in case the BTS rejects the configuration

Possible values: 00 = Error in radio network configuration 01 = Error in transport layer 02 = Error in NBAP protocol layer 03 = Miscellaneous

5 possible values sent by the BTS, value meaning depends on the cause that is given in 4th supplementary information field:

DN99580892Issue 08C

213

RNC Base Station Alarms (7000-7900) 7772 HSDPA CONFIGURATION FAILED

Id:0900d80580727d78

00 = Unknown cell ID (RNW configuration) 01 = Cell not available (RNW configuration) 06 = Node B resources unavailable (RNW configuration) 09 = Requested configuration not supported (RNW configuration)

03 = Message Not Compatible With Receiver State (Protocol)

03 = Not enough user plane processing resources (Misc) 04 = Unspecified (Misc)

6 more detailed cause in case the value of the 1st supplementary information field is 3 ("RNC Internal error").

Possible values: 306 = Internal waiting timer expired in BTS Resource Manager 328 = BTS overloaded 402 = Wrong BTS ID 404 = Wrong cell ID 420 = No free DL Spreading Codes available for HSDPA 501 = Internal waiting timer expired in NBAP interface 504 = Encoding failed in NBAP interface 505 = Decoding failed in NBAP interface 506 = Parallel procedure not allowed 507 = Unit switchover 508 = State conflict 510 = Table full 529 = NBAP link down

7 phase of HSDPA configuration

01 = Initial HSDPA configuration 02 = Reconfiguration of HSDPA 03 = PWSM HSPA05 reconfiguration failure

InstructionsCheck first the nature of the problem. The 7th supplementary informationfield value indicates the phase in which the problem has occured:

01: Initial HSDPA configuration

The problem has occured during initial HSDPA setup to a cell. The effect of this is that HSDPA cannot be used in the cell.

02: Reconfiguration of HSDPA

The problem has occured during HSDPA reconfiguration to a cell. The effect is that the HSDPA may not work with the intended parameters. In this case it is recommended that HSDPA is disabled and enabled in the cell to confirm that proper parameters are taken into use. This action requires cell locking.

214 DN99580892Issue 08C


Id:0900d80580727d78


03: PWSM HSPA05 reconfiguration failure

The problem has occured during HSDPA reconfiguration to a cell when Power Saving Mode For BTS (PWSM) feature has been making HSPA05 reconfiguration. HSPA05 reconfiguration has been stopped and no cell deletion or activation by PWSM feature will be done. In this case it is recommended to disable PWSM feature. Do cell lock/unlock to recover cell HSDPA parameters and state. If cell is not recovered using lock/unclock operation, a BTS restart can be attempted using RNC RNW Object Browser or BTS Site Manager.

The first supplementary information field value indicates the mainreason for the problem.

01: No reply from WBTS

Problem may reside somewhere in transmission network to BTS. Check if there are other active alarms for the WBTS object and follow the instructions given for those alarms.

If there are no apparent problems shown via other alarms, check the type of network problem with following instructions:

Precondition for Physical Shared Channel Reconfiguration procedure is that the C-NBAP link to WBTS is working. Check the state of C-NBAP link of this WBTS object from 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.


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

DN99580892Issue 08C

215

RNC Base Station Alarms (7000-7900) 7772 HSDPA CONFIGURATION FAILED

Id:0900d80580727d78

If the working state of the BTS and the BTS HW configuration are OK but this fault still occurs contact the local Nokia Siemens Networks representative.

In case the fault is related to RNW configuration (based on 4th and 5th alarm supplementary information fields of this alarm), check the configuration of this WBTS object in 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 Siemens Networks representative.

03: 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, 505, 506, 508, 510 or 529, the situation may be resolved by locking and unlocking the cell. This operation cancels the alarm and triggers the Physical Shared Channel Reconfiguration procedure again. If the problem was only temporary, the alarm should not appear again.

If the alarm appears again after a while, check the log writings from the concerned ICSU 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 Siemens Networks representative.


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

216 DN99580892Issue 08C


Id:0900d80580727d78

7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS

43 7775 INCONSISTENCY IN WCEL CONFIGU-RATION PARAMETERSMeaning

The alarm indicates that the Nokia Siemens Networks specificconfiguration parameters in BTS might not be consistent with theparameters in RNC. These parameters are CellRange, RACHCapacity,SIB7factor, ShutdownWindow and ShutdownStepAmount. The situationcausing this alarm will not obstruct network operations.

The alarm is set when BTS has failed to accept the parameterssend to it during cell setup or when BTS has not responded to theparameter sending during cell setup.

The alarm is cancelled automatically after these configurationparameters have been successfully sent.

The alarm is cell-specific and its indication to NetAct has beenprevented by default. The RNC-specific alarm 3325, INCONSISTENCY INCONFIGURATION PARAMETERS, is related to this alarmand one instance of it is activated when Nokia Siemens Networksspecific configuration parameter sending has failed to one or morecells in a certain RNC. This RNC-specific alarm is sent to NetActby default.

Alarm indication preventions can be altered with MML command AFC.

Supplementary information fields1 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

InstructionsCheck 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 SiteConfiguration File, no actions are needed in RNC. Check if otheralarms are active for the BTS or WCEL in question.

If the cell parameters in RNC are not the same as those in the BTSSite Configuration File and these parameters need to be updated,the following actions can be taken to the cell that has failed toaccept the parameters sent:

* Modify these parameters with RNC Object Browser. This is recommended if the cell is working, that is, cell state (WCEL state) is WO. * Lock the cell and then unlock it with RNC Object Browser.

DN99580892Issue 08C

217

RNC Base Station Alarms (7000-7900) 7775 INCONSISTENCY IN WCEL CONFIGURATIONPARAMETERS

Id:0900d80580727d78

This operation causes the parameters to be resent to the BTS.

More information about the exact fail reason can be found by examiningthe supplementary info field (error code). You can check its meaningwith a command of the service terminal extension MRS (see ServiceTerminal Essentials) or from the document GeneralError Messages of System.

Probable error code values are: * 94 = NO RESPONSE BTS has not responded to parameter sending in time or response did not include all the cells the parameters where sent to. * 15472 = WBTS HARDWARE OVERLOAD BTS is temporarily too busy to handle new requests. * 15477 = EQUIPMENT FAILURE A HW failure has occurred. * 15480 = NO RESOURCES IN WBTS Node B resources are unavailable. * 16504 = INTERNAL NBAP ERROR PREVENTING PROCEDURE COMPLETION An internal error that prevents parameter sending has occurred.

In these fault cases the actions mentioned above should repair thesituation. Fault cases with error code EQUIPMENT FAILURE may alsorequire repairing of BTS HW.

In many cases there is more information in the OMU computer log. Itcan be studied with the MML-command ZDDE::"ZGSC";

CancellingDo not cancel the alarm. The system cancels the alarm automaticallyafter these parameters are sent successfully to the WBTS.

218 DN99580892Issue 08C


Id:0900d80580727d78

7776 HSDPA FAILURE IN WCEL

44 7776 HSDPA FAILURE IN WCELMeaning

A major fault (or faults) occurs in the BTS. A unit (or units)that take care of HSDPA traffic in WCEL can be faulty, or there is notenough capacity available in the BTS WSP cards for the HSDPA service.

This alarm is set when an HSDPA-capable BTS sends a Resource StatusIndication (RSI) message via NBAP to RNC indicating that HSDPA stateis changed to "disabled". As a consequence of this alarm, HSDPAconnections cannot be used in that particular cell.

The RSI message regarding HSDPA disabling can arrive also after thewhole cell is reported as "disabled" by BTS via another RSI message.This can happen in BTS recommissioning phase when the cell is disabledin the BTS end as part of the BTS maintenance operations. In this casethis alarm can appear together with the alarms for the same WCELobject:7761 RNW O&M SCENARIO FAILURE7771 WCDMA CELL OUT OF USE

In case the overall WCEL object state is WO (working) when this alarmappears, check the reason for the fault from the BTS WSP-related alarms.


InstructionsFirst check the WCEL operational state using RNW RNC Object Browser.

If the WCEL operational state is not WO (working), ignore this alarm andanalyze the problem with the WCEL taking into account the other activealarms for the same WCEL or its parent WBTS object.

If the WCEL operational state is WO, check in the RNC the WSP-relatedactive alarms that are targeted to the related WBTS object.The alarms to be checked are: 7650 BASE STATION FAULTY 7651 BASE STATION OPERATION DEGRADED 7652 BASE STATION NOTIFICATIONThe faulty unit is mentioned in supplementary information field 3 ofthese alarms. Check all WSP-related alarms because any of theWSP-related fault can be the reason for this alarm.

If a HSDPA-dedicated WSPC unit in BTS is faulty, the BTS reservesanother WSPC when it becomes free from other traffic.

For more information on BTS alarms, see WCDMA BTS Alarm

DN99580892Issue 08C

219

RNC Base Station Alarms (7000-7900) 7776 HSDPA FAILURE IN WCEL

Id:0900d80580727d78

Descriptions (SW and release documentation).

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

220 DN99580892Issue 08C


Id:0900d80580727d78

7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE

45 7778 WCDMA BTS DEDICATED MEASURE-MENT FAILUREMeaning

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 nack2) NBAP-D link is down3) NBAP-D module has problem(RNC internal)

RNC will retry Dedicated Measurement Initiation after the correspondingNBAP-D link is re-created to be ready. If the retry succeeds, the alarmwill be cancelled.

After this alarm, cells' capacity under the BTS might be affected.

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

2 communication control port id

InstructionsFirst, check if there are other alarms active for the BTS in questionand follow the instructions given for those alarms. This alarm iscancelled if the problem is solved by correcting the other activealarms.

If there are no obvious faults indicated by active alarms and thisalarm is not cancelled by system, follow the instructions given in thesteps below according to error code given in 1st supplementaryinformation field.

1. Error code 13247 no_answer_from_remote_end_ec No response from BTS 15479 nbap_bts_hw_res_not_avail_ec BTS hardware failure

These 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

DN99580892Issue 08C

221

RNC Base Station Alarms (7000-7900) 7778 WCDMA BTS DEDICATED MEASUREMENTFAILURE

Id:0900d80580727d78

4) Unlock these cells

If creating the NBAP-D again does not help, the problem may reside on the BTS end. It should be analyzed by connecting to corresponding BTS using BTS Manager.

2. Error code 13288 dst_link_failure_ec NBAP-D link has been down 13846 no_resp_from_serv_provider_ec NBAP-D process no response

The operation in step 1 can be attempted, it may help if the problem was only temporary. If the operation in step 1 does not help, the communication problem between 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 thesituation.

If the problem persists after these steps, contact the local NokiaSiemens Networks representative. Attach OMU message monitoringfor 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 usingFault Management application in RNC EM).


222 DN99580892Issue 08C


Id:0900d80580727d78

7779 RECOVERY ACTIONS ONGOING

46 7779 RECOVERY ACTIONS ONGOINGMeaning

The alarm indicates that RNC has started WBTS recovery actionsdue to non-performing WCDMA cell. During recovery actions it cannot transmit any traffic.

The alarm is set when some of the following situations occur:1. If common measurements are missing and common measurement recovery actions have failed.2. If common measurement initialization constantly fails.3. If common channel creation constantly fails.4. Poor handover related radio link setup ratio.5. Poor FACH RRC connection setup/complete ratio.6. Base Station resource manager process family (BRM) hand crash in RNC.7. constant radio link failure acknowledged by NodeB during RRC connection setup.

This alarm informs operator that recovery actions are ongoing.The recovery actions include WBTS reset, which will takea while, and during this recovery action no other useractions are recommended.

Alarm is cancelled automatically after the WBTS recovery actionshave been completed. After this operator may start to do useractions again.

After this alarm has been cancelled and BTS recovery actions haveended, it is possible that other recovery actions are startedif cells are still in some block state. Alarm 7761 or 7762 is setif some failure occurred during WBTS initialization after theWBTS reset.

Supplementary information fields1 this value indicates the cause that has lead to recovery actions:

00 Common measurements are missing and common measurement recovery actions have failed. 01 Common measurement initialization constantly fails. 02 Common channel creation constantly fails. 04 Poor handover related radio link setup ratio. 05 Poor FACH RRC connection setup/complete ratio. 06 Constant radio link failure acknowledged by NodeB. 08 Base Station resource manager process family (BRM) hand crash in RNC.

DN99580892Issue 08C

223

RNC Base Station Alarms (7000-7900) 7779 RECOVERY ACTIONS ONGOING

Id:0900d80580727d78

InstructionsThis alarm does not require any actions.

WBTS recovery actions are started when other recovery actions have notrecovered the cell. The reason for WBTS recovery actions is indicatedin 1st supplementary information field.

If cell is still not working after the WBTS recovery actions have endedand no reason behind it can be found, collect at least following logsand contact the local Nokia Siemens Networks representative: - OMU computer log (MML-commands ZDDE::"ZGSC"; and ZDDE::"ZGLE";), - alarm history (MML-command ZAHP or using Fault Management application in RNC EM) - message monitoring from OMU (families 50B, 4FA) and serving ICSU (check serving ICSU from COCO data in RNC Object Browser, monitor families 4FE, 4FB, 4FD, 4B7) during WBTS reset.


224 DN99580892Issue 08C


Id:0900d80580727d78

7780 HSUPA FAILURE IN WCEL

47 7780 HSUPA FAILURE IN WCELMeaning

A major fault (or faults) occurs in the BTS. A unit (or units)taking care of HSUPA traffic in the WCEL can be faulty, or there is notenough capacity available on the BTS WSP cards for HSUPA service.

This alarm is set when an HSUPA-capable BTS sends a Resource StatusIndication (RSI) message via NBAP to the RNC indicating that HSUPA stateis changed to "disabled". As a consequence of this alarm, HSUPAconnections cannot be used in that particular cell.

The RSI message regarding HSUPA disabling can arrive also after thewhole cell is reported as "disabled" by BTS via another RSI message.This can happen in BTS recommissioning phase when the cell is disabledin the BTS end as part of the BTS maintenance operations. In this casethis alarm can appear together with the alarms for the same WCELobject:7761 RNW O&M SCENARIO FAILURE7771 WCDMA CELL OUT OF USE

In case the overall WCEL object state is WO (working) when this alarmappears, check the reason for the fault from the BTS WSP-related alarms.


InstructionsFirst check the WCEL operational state using RNW RNC Object Browser.

If the WCEL operational state is not WO (working), ignore this alarm andanalyze the problem with the WCEL taking into account the other activealarms for the same WCEL or its parent WBTS object.

If the WCEL operational state is WO, check in the RNC the WSP-relatedactive alarms that are targeted to the related WBTS object.The alarms to be checked are: 7650 BASE STATION FAULTY 7651 BASE STATION OPERATION DEGRADED 7652 BASE STATION NOTIFICATIONThe faulty unit is mentioned in supplementary information field 3of these alarms. Check all WSP-related alarms because any of theWSP-related faults can be the reason for this alarm.

If a HSUPA-dedicated WSPC unit in the BTS is faulty, the BTSreserves another WSPC when it becomes free from other traffic.

For more information on BTS alarms, see WCDMA BTS Alarm

DN99580892Issue 08C

225

RNC Base Station Alarms (7000-7900) 7780 HSUPA FAILURE IN WCEL

Id:0900d80580727d78

Descriptions (SW and release documentation).

CancellingDo not cancel the alarm. The system cancels the alarmautomatically when the fault is corrected.

226 DN99580892Issue 08C


Id:0900d80580727d78

7781 NETWORK ELEMENT CONFIGURATION ER-ROR

48 7781 NETWORK ELEMENT CONFIGURATION ERRORMeaning

The alarm indicates that the NEType indicated by the BTS and the NBAPCommunication Mode configured in the RNC for the WBTS object do notmatch. The RNC sets this alarm when such a mismatch is detected afterthe BTS O&M link establishment.

The consequences of this alarm are:- WCEL unlocking operation under this BTS is denied.- WCEL creation under this BTS is denied.- WCEL modification under this BTS is denied.- the creation, modification, and connection of a related COCO are denied.- WBTS modification is denied.- WBTS and its child objects can be deleted.- WCEL can be locked.

The alarm is cancelled automatically when the WBTS is deleted.

Supplementary information fields1 indicates the BTS model in the WCDMA. The meanings of the possible values and the corresponding GUI abbreviations are: 00 - Not used 01 - Other 02 - UltraSite BTS 03 - FlexiBTS 04 - PicoBTS 05 - Wimax 09 - NB/RSxxx

2 indicates the used communication mode for NodeB via the NBAP interface. The meanings of the possible values and the corresponding GUI abbreviations are: 00 - UltraSite BTS, FlexiBTS, PicoBTS 01 - NB/RSxxx

InstructionsThe WBTS deletion and recreation is required when correcting theincorrect configuration. The WBTS recreation is needed because theNBAP Communication Mode is a non-modifiable parameter that must begiven in the WBTS object creation phase.

Step 1:

Check, using the RNC RNW Object Browser, if there are WCELs under this WBTS. If yes, lock all these WCEL objects and delete them.

DN99580892Issue 08C

227

RNC Base Station Alarms (7000-7900) 7781 NETWORK ELEMENT CONFIGURATION ER-ROR

Id:0900d80580727d78

Step 2:

Delete the WBTS object.

Step 3:

Recreate the WBTS object with the correct NBAP Communication Mode parameter value. After this, recreate the WCEL objects under this WBTS.

CancellingDo not cancel the alarm. The system cancels the alarm automaticallywhen the WBTS is deleted.

228 DN99580892Issue 08C


Id:0900d80580727d78


49 7782 HSUPA CONFIGURATION FAILEDMeaning

This alarm indicates that there has been an error when RNC has requestedconfiguration or reconfiguration of HSUPA channels to BTS via PhysicalShared Channel Reconfiguration (PSCR) procedure.

The possible causes which result in this alarm are:

- a problem in transmission network between RNC and BTS- BTS has rejected the configuration or reconfiguration of HSUPA channels- RNC is unable to send the HSUPA configuration to BTS because of RNC internal problems (e.g. congestion in Iub interface)

Location and the nature of the failure can be determined from thesupplementary information fields of this alarm.

The consequence of this alarm depends on the HSUPA configuration phasewhere the failure occurred.- If the failure occurred in the initial HSUPA configuration or in delivering the HSUPA parameters to the BTS, the HSUPA connections cannot be used in this particular cell at all- If the failure occurred in the reconfiguration of the HSUPA, the effect is that the cell may not work with intended HSUPA parameters


Possible values: 01 = No reply from BTS 02 = BTS rejects the configuration 03 = RNC internal error

2 computer unit where this alarm is generated from

3 index of the alarming unit

4 this info field is applicable if 1st supplementary information field value is 01

5 more detailed cause in case the BTS rejects the configuration

Possible values: 00 = Error in radio network configuration 01 = Error in transport layer 02 = Error in NBAP protocol layer 03 = Miscellaneous

DN99580892Issue 08C

229

RNC Base Station Alarms (7000-7900) 7782 HSUPA CONFIGURATION FAILED

Id:0900d80580727d78

The value in this field is applicable if 8th supplementary information field value is 02 or 03

6 possible values sent by the BTS, value meaning depends on the cause that is given in 4th supplementary information field:

00 = Unknown cell ID (RNW configuration) 01 = Cell not available (RNW configuration) 06 = Node B resources unavailable (RNW configuration) 09 = Requested configuration not supported (RNW configuration)

03 = Message Not Compatible With Receiver State (protocol)

03 = Not enough user plane processing resources (Misc) 04 = Unspecified (Misc)


7 more detailed cause in case the value of the 1st supplementary information field is 03 ("RNC Internal error").

Possible values:

306 = Internal waiting timer expired in BTS Resource Manager 328 = BTS overloaded 402 = Wrong BTS ID 404 = Wrong cell ID 420 = No free DL Spreading Codes available for HSUPA 501 = Internal waiting timer expired in NBAP interface 504 = Encoding failed in NBAP interface 505 = Decoding failed in NBAP interface 506 = Parallel procedure not allowed 507 = Unit switchover 508 = State conflict 510 = Table full 529 = NBAP link down


8 phase of HSUPA configuration

01 = Delivering HSUPA parameters to BTS 02 = Initial HSUPA configuration 03 = Reconfiguration of HSUPA 04 = PWSM HSPA05 reconfiguration failure

230 DN99580892Issue 08C


Id:0900d80580727d78


InstructionsStep 1:

Check first the nature of the problem. The 8th supplementary information field value indicates the phase in which the problem has occured:

01: Delivering HSUPA parameters to BTS 02: Initial HSUPA configuration

The problem has occured during initial HSUPA setup to a cell. The effect of this is that HSUPA cannot be used in the cell. Proceed to the step 2 in this instruction.

03: Reconfiguration of HSUPA

The problem has occured during HSUPA reconfiguration to a cell. The effect is that the HSUPA may not work with the intended parameters. In this case it is recommended that HSUPA is disabled and enabled in the cell to confirm that proper parameters are taken into use. This action requires cell locking.

04: PWSM HSPA05 reconfiguration failure

The problem has occured during HSUPA reconfiguration to a cell when Power Saving Mode For BTS (PWSM) feature has been making HSPA05 reconfiguration. HSPA05 reconfiguration has been stopped and no cell deletion or activation by PWSM feature will be done. In this case it is recommended to disable PWSM feature. Do cell lock/unlock to recover cell HSUPA parameters and state. If cell is not recovered using lock/unclock operation, a BTS restart can be attempted using RNC RNW Object Browser or BTS Site Manager.

Step 2:

The first supplementary information field indicates the main reason for the problem.

01: No reply from WBTS

Problem may reside somewhere in transmission network to BTS. Check if there are other active alarms for the WBTS object and follow the instructions given for those alarms.

If there are no apparent problems shown via other alarms, check the type of network problem with 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

DN99580892Issue 08C

231

RNC Base Station Alarms (7000-7900) 7782 HSUPA CONFIGURATION FAILED

Id:0900d80580727d78

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.


02: 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 HSUPA can be supported (WSPC cards) using BTS Manager. If the working state of the BTS and the BTS HW configuration are OK but this fault still occurs contact the local Nokia Siemens Networks representative.

In case the fault is related to RNW configuration (based on 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 Siemens Networks representative.

03: 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, 505, 506, 508, 510 or 529, the situation may be resolved by locking and unlocking the cell. This operation cancels the alarm and triggers the Physical Shared Channel Reconfiguration procedure again.

232 DN99580892Issue 08C


Id:0900d80580727d78


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 Siemens Networks representative.


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

DN99580892Issue 08C

233

RNC Base Station Alarms (7000-7900) 7783 IP BASED D-NBAP LINK FAILURE

Id:0900d80580727d78

50 7783 IP BASED D-NBAP LINK FAILUREMeaning

One or more IP based D-NBAP links of a WCDMA BTS have been detected lostby the RNC.

The user plane traffic handling capability of the WCDMA BTS isdegraded or the traffic capability of the whole WCDMA BTS may betotally lost.

This alarm is set only if the fault is detected in IP based D-NBAPlink(s) of a WCDMA BTS. The alarm is not set for IP based D-NBAP linksif the C-NBAP link is also unavailable at the same time.

Supplementary information fields1 IPv4 address of the remote end. This field is filled with zeroes if IPv6 addressing is in use.

2 IPv6 address of the remote end. This field is filled with zeroes if IPv4 addressing is in use.

InstructionsSee the NBAP link operational states for the WCDMA BTS from RNCRNW Object Browser to see which of the configured D-NBAP links areunavailable.

In case this alarm was set right after WBTS was enabled in the system,verify using RNC RNW Object Browser that the IPNB object configurationin RNC is correct in relation to network setup.

Otherwise the problem is likely located either in BTS or in IPtransmission between BTS and RNC. See other possible active BTSoriginated alarms (7650, 7651) that may indicate the reason for thefailure.Use BTS Site Manager to see the operation status in BTS end foradditional troubleshooting.


234 DN99580892Issue 08C


Id:0900d80580727d78


51 7784 RECOVERY ACTION FAILUREMeaning

This alarm indicates that automatic WCDMA BTS recovery action performedby RNC has failed. The recovery has been attempted because some of theWCELs under the WBTS has been detected not to be performing properly.The observed cause for the recovery is given in alarm supplementaryinformation. For more information about the recovery functionalitybehind this alarm, see feature descriptions for features RAN1302 andRAN1810 in Product Documentation.

The reason for the recovery failure is one of the following: - amount of WBTS recovery actions (restarts) have been used up for a specific WBTS object for the current day - BTS restart failed due to missing BTS O&M connection - BTS does not respond to restart request - BTS is busy handling software upgrade and rejects the restart request

As a result of this alarm the traffic handling capacity of the WCDMABTS may be reduced because some WCELs are not performing properly.

Recovery action will be resumed by RNC again after the fault preventingthe recovery action has been corrected and if the problem affecting theWCEL performance still remains.

Supplementary information fields1 this value indicates the type of failure that prevented the recovery action. Possible values are:

00 Amount of BTS restarts as recovery action have been used up 01 BTS restart failed due to missing BTS O&M connection 02 BTS restart failed due to no response from BTS 03 BTS restart rejected by BTS due to ongoing BTS SW upgrade 04 BTS restart failed because of invalid BTS O&M message 05 BTS restart failed due to non-supported field value in BTS O&M message 06 BTS restart failed due to unknown object type in BTS O&M message 07 BTS restart failed due to RNC internal errors

2 this value indicates the cause that has lead to recovery actions:

00 Common measurements are missing and common measurement recovery actions have failed. 01 Common measurement initialization constantly fails. 02 Common channel creation constantly fails. 04 Poor handover related radio link setup ratio. 05 Poor FACH RRC connection setup/complete ratio. 06 Constant radio link failure acknowledged by NodeB.

DN99580892Issue 08C

235

RNC Base Station Alarms (7000-7900) 7784 RECOVERY ACTION FAILURE

Id:0900d80580727d78

08 Base Station resource manager process family (BRM) hand crash in RNC.

3 this value indicates the Local WCEL resource id for the WCEL that was detected not to be performing properly. In case the problem is not related to any specific WCEL (if 2nd supplementary information field value is 08) then this value is set to FFFFFFFF (4294967295d).

4 this value indicates the allowed amount of WBTS recovery actions (restarts) per day. It is defined in PRFILE parameter RN22_FEATURE_OPT_009 (002:1296).

InstructionsCheck the reason for the recovery failure from the 1st supplementaryinformation field and proceed accordingly.

00: The amount of performed BTS restarts as recovery action per day exceeds the limit which is given in the 4th alarm supplementary information field. In this case the BTS cannot be restarted by RNC until next midnight when RNC will reset the BTS specific restart amount counters. The BTS can be recovered manually by restarting it using either RNC RNW Object Browser or BTS Site Manager. Increasing the allowed BTS restart amount in PRFILE enables RNC to perform additional restarts for BTS sites that have no recovery attempts left.

01: BTS O&M connection between BTS and RNC is not available and restart could not be performed. See if RNC alarm 7750 is active for possible details on the fault concerning the BTS O&M connection. Check also the status of BTS O&M connection from BTS Site Manager. See instructions below for possible need to perform manual recovery actions depending on the 2nd supplementary information field value.

02: BTS does not respond to the reset request. This may be due to high load in BTS side. Check the BTS status using BTS Site Manager and restart the BTS manually if possible. See instructions below for possible need to perform manual recovery actions depending on the 2nd supplementary information field value.

03: BTS software upgrade is ongoing and BTS cannot be restarted at the moment. BTS will restart after software upgrade is completed.

04, 05, 06: Unexpected error has occurred in BTS O&M message handling. The reason might be that RNC and BTS do not use compatible version of the BTS O&M interface. Collect OMU computer log from RNC and also logs from the BTS in question. Fill in a problem report and send it to the local Nokia Siemens Networks representative. See instructions below for possible need to perform manual recovery actions depending on the 2nd supplementary information field value.

236 DN99580892Issue 08C


Id:0900d80580727d78


07: RNC internal errors might be that reading BTS related information from database failed or there are already some other recovery actions going on for the BTS. See if alarms 7761 or 7762 have been set for the WBTS in question. See instructions below for possible need to perform manual recovery actions depending on the 2nd supplementary information field value.

Check also the value of 2nd supplementary information field and, if it'svalue is 08 (BRM hand crash), proceed accordingly based on the 1stsupplementary information field value.

01, 02, 04, 05, 06, 07: In these recovery failure cases the BTS must be restarted manually using the BTS Site Manager or, if that is not possible for some reason, COCO/IPNB object disconnect and connect operation from the WBTS object in RNC using RNC RNW Object Browser must be performed. Both of these operations trigger C-NBAP link re-establishment and cause a complete reinitialization of the cells. These user actions are required in to ensure that cells are properly recovered after BRM hand crash.

RNC OMU computer log ("ZGSC:,50B" and "ZGSC:,4FA" ) can also providefurther information about the attempted recovery actions.

It is recommended that RNC OMU logs (ZGSC and ZGLE) are collectedtogether with BTS logs for possible further troubleshooting when thisalarm is observed.


DN99580892Issue 08C

237

RNC Base Station Alarms (7000-7900) 7786 WCDMA BASE STATION OUT OF USE

Id:0900d80580727d78

52 7786 WCDMA BASE STATION OUT OF USEMeaning

This alarm indicates that there is a WBTS-level failure that causesall the WCELs in the WO state under this specific WBTS to becomeunavailable.

This alarm is set when a known fault occurs and makes allthe WCELs under a certain WBTS to become unavailable at once.The reasons for this are the C-NBAP link break or Base StationResource Manager (BRM) hand crash in the RNC.

As a result of this alarm, the whole WBTS is unavailable for traffic.There can be also individual WCEL level alarms active for the WCELsof this WBTS if they were active prior to the WBTS level failuredetection.

This alarm is set only if there is at least one cell in the WO stateunder the WBTS.

This alarm is cancelled when at least one WCEL under the WBTS isrecovered back to the WO state, or if the user locks all the WCELsunder the WBTS.

For more information on this functionality, see Nokia SiemensNetworks WCDMA RAN documentation concerning feature RAN1461.

Supplementary information fields1 reason why all the WCELs became unavailable at once. The possible reasons are: 00 = C-NBAP link break 01 = BRM hand crash

InstructionsThe 1st supplementary information field indicates the reason whythe whole WBTS became unavailable. The field contains thefirst observed reason for the problem. This means that duringrecovery actions the whole WBTS can stay unavailable, but thereason can change. For example, it is possible that the BRM hand crashcauses the original problem, but after its recovery the C-NBAP linkcan be unavailable. The original alarm is kept active, as from thesystem point of view the whole WBTS is still unavailable.

To analyze and correct the problem, check the 1st supplementaryinformation field value.

00: C-NBAP link break This can be caused by different underlying reasons that

238 DN99580892Issue 08C


Id:0900d80580727d78

7786 WCDMA BASE STATION OUT OF USE

are indicated as the C-NBAP link break to RNW O&M: - a transmission break between RNC and BTS resulting from, for example, a cable or external transmission equipment failure, a BTS restart performed using BTS Site Manager, or an RNC network interface unit failure. - an internal RNC failure, for example a spontaneous ICSU restart.

In case of the C-NBAP link failure the recommendation is to wait for a couple of minutes and check if the disturbance is only temporary. The system recovers automatically once the transmission between the RNC and BTS is available again. In case of a longer WBTS unavailability, it can be checked if the RNC has active alarms for ICSU or network interface units that can cause the C-NBAP link unavailability. The relation between WBTS and ICSU unit can be seen from WBTS data using the RNC RNW Object Browser (the RNC GUI for BTS Connection Resources dialog). 01: BRM hand crash The system recovers from the situation automatically. This reason may trigger non-performing cell recovery actions in RNC, meaning that the BTS gets restarted by the RNC.

As for the behavior of this alarm when the WBTS level failureindication in feature RAN1461 state is changed, note the following:

1. When the WBTS level fault functionality is switched from OFF to ON state, there are no effects on the existing WCEL alarms under a certain WBTS. The effect can be seen on the following alarms set by the system.

2. When the WBTS level fault functionality is switched from ON to OFF state, and if this alarm is active for a WBTS, the functionality for this particular WBTS is still considered as working. This means that the WBTS level failure alarm is kept active as long as all the WCELs for that WBTS remain unavailable.


DN99580892Issue 08C

239

RNC Base Station Alarms (7000-7900) 7795 INCONSISTENCY IN HIGH PEAK RATE HSPACONFIG

Id:0900d80580727d78

53 7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIGMeaning

The alarm indicates that the High Peak Rate HSPA configurationparameters in at least one WCEL of the BTS might not be consistentwith the parameters in the RNC.

The RNC sets this alarm when inconsistency is detected, whichindicates that a high peak rate HSPA feature is enabled in the RNC, butthe BTS reports that it does not have support for it. The situationcausing this alarm does not obstruct network operations.

The alarm is cell-specific, and not indicated to NetAct by default.The RNC-specific alarm 3325, INCONSISTENCY IN CONFIGURATION PARAMETERS,is related to this alarm and one instance of it is activated when theHigh Peak Rate HSPA setup has failed in one or more cells in the RNC.

This alarm is cancelled by the system once the BTS has indicatedto the RNC that it supports the high peak rate HSPA feature in the cellor when the cell is deleted/locked.

Alarm indication preventions can be altered with MML command AFC.

Supplementary information fields1 possible error code values are:

* 746 = DC HSDPA NOT AVAILABLE local Cell in the BTS is not Multi Cell Capable, whereas the RNC has the DC HSDPA feature enabled in the cell

2 name of the feature for which the setup failed. Possible values:

DCHSDPA = Dual Cell HSDPA

InstructionsThe situation causing this alarm does not obstruct network operations,and therefore no immediate actions are required. However, you can takethe following actions to ensure consistency in configuration parameters.

1. Find the cells that might have inconsistency in configuration parameters by checking the alarms in the RNC. This particular alarm is set to cells for which the configuration parameter sending has failed. For these cells, proceed to step 2.

2. Check the cell parameter WCEL - DCellHSDPAEnabled in the RNC using the RNC RNW Object Browser. If this parameter value for the cell is

240 DN99580892Issue 08C


Id:0900d80580727d78

7795 INCONSISTENCY IN HIGH PEAK RATE HSPA CONFIG

the same as in the BTS Site Configuration File, then no actions are needed in the RNC.

3. If the cell parameters in the RNC are not the same as those in the BTS Site Configuration File and these parameters need to be updated, use the RNC RNW Object Browser to take the following actions to the cell that has failed to accept the parameters sent:

- Lock the WCEL. - Modify the DCellHSDPAEnabled parameter. - Unlock the WCEL. This operation causes the parameters to be resent to the BTS.

More information about the exact failure reason can be found by examiningthe 1st supplementary information field (error code). You can check itsmeaning with a command of the service terminal extension MRS (see ServiceTerminal Essentials, Maintenance Manual) or from the document GeneralError Messages of System, Supplementary References.

CancellingDo not cancel the alarm. The system cancels the alarm after the BTS hasindicated to the RNC that it supports the high peak rate HSPA feature inthe cell or when the cell is deleted or locked.

DN99580892Issue 08C

241

RNC Base Station Alarms (7000-7900) 7799 RNC RADIO NETWORK TEST ALARM

Id:0900d80580727d78

54 7799 RNC RADIO NETWORK TEST ALARMMeaning

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

Supplementary information fields1 this is compared supplementary info field meaning that test alarms for same object can be identified by setting different values into this field.

2 the one byte size of field which is output in decimal format. The field value is not significant.

3 the two byte size of field which is output in decimal format. The field value is not significant.

4 the four byte size of field which is output in decimal format. The field value is not significant.

5 the one byte size of field which is output in hexadecimal format. The field value is not significant.

6 the two byte size of field which is output in hexadecimal format. The field value is not significant.

7 the four byte size of field which is output in hexadecimal format. The field value is not significant.

InstructionsNo operation instruction.

CancellingCancel the alarm with an MML command.

3G alarms

Documents

service terminal essentials

iu service barring

poor sky visibility

ip address initialisation

path payload label

dedicated measurement initiation

frequently breaking transmission

nokia siemens networks