You are on page 1of 244

RNC3267

Nokia WCDMA RAN, Rel. RAS06, System
Library, v. 5

Base Station Alarms (7000-7999)

DN99580892
Issue 6-3 en
12/06/2008

# Nokia Siemens Networks

1 (244)

Base Station Alarms (7000-7999)

2 (244)

# Nokia Siemens Networks

DN99580892
Issue 6-3 en
12/06/2008

Summary of changes

Summary of changes
Changes between document issues are cumulative. Therefore, the latest
document issue contains all changes made to previous issues.
Changes made between issues 6-3 and 6-2

Added new section called Default alarm indication preventions in the
system.
Modified alarms
7779

Changes made between issues 6-2 and 6-1

Modified alarms
7750

7665

Changes made between issues 6-1 and 6-0

Modified alarms
7650

7653

7660

7651

7654

7661

7652

7655

7665

Changes made between issues 6-0 and 5-1

New alarms
7780

7782

Modified alarms
7750

DN99580892
Issue 6-3 en
12/06/2008

7772

# Nokia Siemens Networks

3 (244)

Base Station Alarms (7000-7999)

Removed alarms
7773

4 (244)

7774

# Nokia Siemens Networks

DN99580892
Issue 6-3 en
12/06/2008

Alarm 7799 is an old test alarm for RNC testing purposes which is not set by RNC in any situation anymore. The alarm 7775 is indication prevented in RNC because alarm 3325 informs about WCEL parameter inconsistencies in RNC level. 7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS . For more information. The list of alarms below shows the affected alarms that are indication-prevented by default in RNC. This has been done to reduce the amount of alarm indications that RNC reports to NetAct. Base Station Alarms DN99580892 Issue 6-3 en 12/06/2008 . see the instructions given for alarm 7775 and 3325. 7799 RNC RADIO NETWORK TEST ALARM # Nokia Siemens Networks 5 (244) .Default alarm indication preventions in the system 1 Default alarm indication preventions in the system Alarm indication preventions for certain alarms have been set by default in RNC.

Base Station Alarms (7000-7999) 6 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

List of Alarms 2 List of Alarms 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7650 7651 7652 7653 DN99580892 Issue 6-3 en 12/06/2008 EXTERNAL AL 1 EXTERNAL AL 2 EXTERNAL AL 3 EXTERNAL AL 4 EXTERNAL AL 5 EXTERNAL AL 6 EXTERNAL AL 7 EXTERNAL AL 8 EXTERNAL AL 9 EXTERNAL AL 10 EXTERNAL AL 11 EXTERNAL AL 12 EXTERNAL AL 13 EXTERNAL AL 14 EXTERNAL AL 15 EXTERNAL AL 16 EXTERNAL AL 17 EXTERNAL AL 18 EXTERNAL AL 19 EXTERNAL AL 20 EXTERNAL AL 21 EXTERNAL AL 22 EXTERNAL AL 23 EXTERNAL AL 24 EXTERNAL AL 25 BASE STATION FAULTY BASE STATION OPERATION DEGRADED BASE STATION NOTIFICATION CELL FAULTY # Nokia Siemens Networks 7 (244) .

The information here is for documentation purposes only. The operator can modify them with an MML command. NR TEXT CLS OUT SDC SDD CDL LVT -------------------------------------------------------------------------------7401 7402 7403 8 (244) EXTERNAL AL 1 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 2 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 3 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - # Nokia Siemens Networks * NON * NON * NON DN99580892 Issue 6-3 en 12/06/2008 .Base Station Alarms (7000-7999) 7654 7655 7660 7661 7665 7740 7750 7761 7762 7771 7772 7775 CELL OPERATION DEGRADED CELL NOTIFICATION BASE STATION LICENCE EXPIRED BASE STATION LICENCE NOTIFICATION BASE STATION TRANSMISSION ALARM BEATING WCDMA BTS ALARM FAILURE IN WCDMA WBTS O&M CONNECTION RNW O&M SCENARIO FAILURE RNW DATABASE OPERATION FAILURE WCDMA CELL OUT OF USE HSDPA CONFIGURATION FAILED INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS HSDPA FAILURE IN WCEL WCDMA BTS DEDICATED MEASUREMENT FAILURE RECOVERY ACTIONS ONGOING HSUPA FAILURE IN WCEL HSUPA CONFIGURATION FAILED RNC RADIO NETWORK TEST ALARM 7776 7778 7779 7780 7782 7799 Alarm parameters The following parameter settings are the default settings. 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.

List of Alarms 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 EXTERNAL AL 4 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 5 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 6 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 7 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 8 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 9 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 10 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 11 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 12 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 13 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 14 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 15 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 16 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 17 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks * NON * NON * NON * NON * NON * NON * NON * NON * NON * NON * NON * NON * NON * NON 9 (244) .

Base Station Alarms (7000-7999) 7418 7419 7420 7421 7422 7423 7424 7425 EXTERNAL AL 18 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 19 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 20 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 21 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 22 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 23 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 24 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - EXTERNAL AL 25 00:10 00:10 EVENT TYPE: ENVIRONMENTAL - * NON * NON * NON * NON * NON * NON * NON * NON 7650 BASE STATION FAULTY 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE *** 3 7651 BASE STATION OPERATION DEGRADED 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE ** 5 7652 BASE STATION NOTIFICATION 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE * NON 7653 CELL FAULTY 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE *** 3 7654 CELL OPERATION DEGRADED 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE ** 5 7655 CELL NOTIFICATION 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE * NON 10 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

List of Alarms 7660 BASE STATION LICENCE EXPIRED 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE *** 3 7661 BASE STATION LICENCE NOTIFICATION 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE * NON 7665 BASE STATION TRANSMISSION ALARM 00:10 00:10 EVENT TYPE: QUALITY OF SERVICE * NON 7740 BEATING WCDMA BTS ALARM 00:00 00:00 EVENT TYPE: PROCESSING ** 5 - 7750 FAILURE IN WCDMA WBTS O&M CONNECTION 00:10 00:10 EVENT TYPE: COMMUNICATIONS * NON 7761 RNW O&M SCENARIO FAILURE 00:40 00:00 EVENT TYPE: QUALITY OF SERVICE ** 5 7762 RNW DATABASE OPERATION FAILURE 00:05 00:00 EVENT TYPE: PROCESSING ** 5 7771 WCDMA CELL OUT OF USE 02:00 00:20 EVENT TYPE: QUALITY OF SERVICE ** 5 7772 HSDPA CONFIGURATION FAILED 00:05 00:05 EVENT TYPE: QUALITY OF SERVICE ** 5 7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS 00:00 00:00 EVENT TYPE: PROCESSING * NON 7776 HSDPA FAILURE IN WCEL 00:05 00:00 EVENT TYPE: QUALITY OF SERVICE ** 5 7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE 00:00 00:00 EVENT TYPE: QUALITY OF SERVICE ** 5 7779 RECOVERY ACTIONS ONGOING 00:00 00:00 EVENT TYPE: QUALITY OF SERVICE * NON 7780 HSUPA FAILURE IN WCEL 00:05 00:00 EVENT TYPE: QUALITY OF SERVICE ** 5 DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 11 (244) .

Base Station Alarms (7000-7999) 7782 HSUPA CONFIGURATION FAILED 00:05 00:05 EVENT TYPE: QUALITY OF SERVICE ** 5 7799 RNC RADIO NETWORK TEST ALARM 00:10 00:10 EVENT TYPE: ENVIRONMENTAL * NON 12 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

1. The alarm is defined by the user in a HW database. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 13 (244) .7401 EXTERNAL AL 1 3 7401 EXTERNAL AL 1 Meaning This is an external user-defined alarm. The system cancels the alarm automatically when the fault has been corrected. Cancelling Do not cancel the alarm. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no.

Base Station Alarms (7000-7999) 14 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no.7402 EXTERNAL AL 2 4 7402 EXTERNAL AL 2 Meaning This is an external user-defined alarm. 2. Cancelling Do not cancel the alarm. The alarm is defined by the user in a HW database. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 15 (244) . The system cancels the alarm automatically when the fault has been corrected.

Base Station Alarms (7000-7999) 16 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Cancelling Do not cancel the alarm. The alarm is defined by the user in a HW database. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 17 (244) . Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. The system cancels the alarm automatically when the fault has been corrected.7403 EXTERNAL AL 3 5 7403 EXTERNAL AL 3 Meaning This is an external user-defined alarm. 3.

Base Station Alarms (7000-7999) 18 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 19 (244) . Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. The system cancels the alarm automatically when the fault has been corrected. 4.7404 EXTERNAL AL 4 6 7404 EXTERNAL AL 4 Meaning This is an external user-defined alarm. The alarm is defined by the user in a HW database. Cancelling Do not cancel the alarm.

Base Station Alarms (7000-7999) 20 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Cancelling Do not cancel the alarm.7405 EXTERNAL AL 5 7 7405 EXTERNAL AL 5 Meaning This is an external user-defined alarm. The alarm is defined by the user in a HW database. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 21 (244) . 5. The system cancels the alarm automatically when the fault has been corrected.

Base Station Alarms (7000-7999) 22 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

The system cancels the alarm automatically when the fault has been corrected. 6.7406 EXTERNAL AL 6 8 7406 EXTERNAL AL 6 Meaning This is an external user-defined alarm. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 23 (244) . Cancelling Do not cancel the alarm. The alarm is defined by the user in a HW database.

Base Station Alarms (7000-7999) 24 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. 7. The system cancels the alarm automatically when the fault has been corrected.7407 EXTERNAL AL 7 9 7407 EXTERNAL AL 7 Meaning This is an external user-defined alarm. The alarm is defined by the user in a HW database. Cancelling Do not cancel the alarm. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 25 (244) .

Base Station Alarms (7000-7999) 26 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

7408 EXTERNAL AL 8 10 7408 EXTERNAL AL 8 Meaning This is an external user-defined alarm. The alarm is defined by the user in a HW database. Cancelling Do not cancel the alarm. 8. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 27 (244) . The system cancels the alarm automatically when the fault has been corrected. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no.

Base Station Alarms (7000-7999) 28 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

7409 EXTERNAL AL 9 11 7409 EXTERNAL AL 9 Meaning This is an external user-defined alarm. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. The system cancels the alarm automatically when the fault has been corrected. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 29 (244) . 9. Cancelling Do not cancel the alarm. The alarm is defined by the user in a HW database.

Base Station Alarms (7000-7999) 30 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

7410 EXTERNAL AL 10

12

7410 EXTERNAL AL 10
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

DN99580892
Issue 6-3 en
12/06/2008

# Nokia Siemens Networks

31 (244)

Base Station Alarms (7000-7999)

32 (244)

# Nokia Siemens Networks

DN99580892
Issue 6-3 en
12/06/2008

7411 EXTERNAL AL 11

13

7411 EXTERNAL AL 11
Meaning

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

Supplementary information fields

Instructions

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

Cancelling

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

DN99580892
Issue 6-3 en
12/06/2008

# Nokia Siemens Networks

33 (244)

Base Station Alarms (7000-7999)

34 (244)

# Nokia Siemens Networks

DN99580892
Issue 6-3 en
12/06/2008

Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. The alarm is defined by the user in a HW database. 12.7412 EXTERNAL AL 12 14 7412 EXTERNAL AL 12 Meaning This is an external user-defined alarm. The system cancels the alarm automatically when the fault has been corrected. Cancelling Do not cancel the alarm. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 35 (244) .

Base Station Alarms (7000-7999) 36 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 37 (244) . The system cancels the alarm automatically when the fault has been corrected. Cancelling Do not cancel the alarm.7413 EXTERNAL AL 13 15 7413 EXTERNAL AL 13 Meaning This is an external user-defined alarm. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. The alarm is defined by the user in a HW database. 13.

Base Station Alarms (7000-7999) 38 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

7414 EXTERNAL AL 14 16 7414 EXTERNAL AL 14 Meaning This is an external user-defined alarm. The alarm is defined by the user in a HW database. 14. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 39 (244) . The system cancels the alarm automatically when the fault has been corrected. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. Cancelling Do not cancel the alarm.

Base Station Alarms (7000-7999) 40 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

7415 EXTERNAL AL 15 17 7415 EXTERNAL AL 15 Meaning This is an external user-defined alarm. Cancelling Do not cancel the alarm. 15. The system cancels the alarm automatically when the fault has been corrected. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 41 (244) . Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. The alarm is defined by the user in a HW database.

Base Station Alarms (7000-7999) 42 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

16.7416 EXTERNAL AL 16 18 7416 EXTERNAL AL 16 Meaning This is an external user-defined alarm. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 43 (244) . The alarm is defined by the user in a HW database. The system cancels the alarm automatically when the fault has been corrected. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. Cancelling Do not cancel the alarm.

Base Station Alarms (7000-7999) 44 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

The system cancels the alarm automatically when the fault has been corrected. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no.7417 EXTERNAL AL 17 19 7417 EXTERNAL AL 17 Meaning This is an external user-defined alarm. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 45 (244) . Cancelling Do not cancel the alarm. The alarm is defined by the user in a HW database. 17.

Base Station Alarms (7000-7999) 46 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

The alarm is defined by the user in a HW database. The system cancels the alarm automatically when the fault has been corrected. 18.7418 EXTERNAL AL 18 20 7418 EXTERNAL AL 18 Meaning This is an external user-defined alarm. Cancelling Do not cancel the alarm. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 47 (244) . Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no.

Base Station Alarms (7000-7999) 48 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Cancelling Do not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected. 19.7419 EXTERNAL AL 19 21 7419 EXTERNAL AL 19 Meaning This is an external user-defined alarm. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 49 (244) . Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. The alarm is defined by the user in a HW database.

Base Station Alarms (7000-7999) 50 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

The alarm is defined by the user in a HW database. Cancelling Do not cancel the alarm. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 51 (244) .7420 EXTERNAL AL 20 22 7420 EXTERNAL AL 20 Meaning This is an external user-defined alarm. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. 20. The system cancels the alarm automatically when the fault has been corrected.

Base Station Alarms (7000-7999) 52 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

7421 EXTERNAL AL 21 23 7421 EXTERNAL AL 21 Meaning This is an external user-defined alarm. The alarm is defined by the user in a HW database. The system cancels the alarm automatically when the fault has been corrected. 21. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 53 (244) . Cancelling Do not cancel the alarm. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no.

Base Station Alarms (7000-7999) 54 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 55 (244) .7422 EXTERNAL AL 22 24 7422 EXTERNAL AL 22 Meaning This is an external user-defined alarm. 22. The alarm is defined by the user in a HW database. Cancelling Do not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no.

Base Station Alarms (7000-7999) 56 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. Cancelling Do not cancel the alarm. The alarm is defined by the user in a HW database. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 57 (244) .7423 EXTERNAL AL 23 25 7423 EXTERNAL AL 23 Meaning This is an external user-defined alarm. 23. The system cancels the alarm automatically when the fault has been corrected.

Base Station Alarms (7000-7999) 58 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Cancelling Do not cancel the alarm. The alarm is defined by the user in a HW database. Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. The system cancels the alarm automatically when the fault has been corrected. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 59 (244) . 24.7424 EXTERNAL AL 24 26 7424 EXTERNAL AL 24 Meaning This is an external user-defined alarm.

Base Station Alarms (7000-7999) 60 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Supplementary information fields Instructions The operation depends on what kind of alarm is used as external alarm no. The system cancels the alarm automatically when the fault has been corrected. 25.7425 EXTERNAL AL 25 27 7425 EXTERNAL AL 25 Meaning This is an external user-defined alarm. Cancelling Do not cancel the alarm. The alarm is defined by the user in a HW database. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 61 (244) .

Base Station Alarms (7000-7999) 62 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

cabling and correct installation of the units at the BTS. Make sure the environment does not cause the fault. Refer also to the individual alarm instructions. If the site reset or unit block/unblock does not help. which might have caused the misbehaviour of the unit. see instructions on Alarm Structure. Check the reason for the fault from the supplementary text field of the alarm. the site should be reset to recover from any temporary faults.7650 BASE STATION FAULTY 28 7650 BASE STATION FAULTY Meaning A critical fault (or faults) has occurred in the base station. contact the DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 63 (244) . replace the faulty unit (see source of the alarm and instructions fields of the corresponding alarm). If that does not help. a site reset is required to cancel the alarm. When an active alarm is a 'Start' alarm. Supplementary information fields 1 rack (cabinet) number 2 shelf number 3 slot 4 type of unit 5 unit number 6 subunit number For more information. Before a unit is replaced at the BTS. Instructions Verify the configuration of a BTS by checking the commissioning.

If not working but ping to the AXC is working then restart the AXC remotely so that the BTS will also be restarted automatically.Base Station Alarms (7000-7999) local Help Desk. MetroSite50. If the BTS reset does not help. 2. INSTRUCTIONS : Replace the alarming unit. Ping the AXC. MetroSite. MetroSite. Ping the BTS. if it is not working but ping to the AXC is working. If not working. Reset the BTS. restart the BTS remotely. replace the alarming WAM unit. 3. do a site visit and restart the BTS. FAULT REASON : ATM processor faulty DESCRIPTION : UltraSite. The failure cannot be 64 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . see Nokia WCDMA BTS Alarm Description (SW and release document). INSTRUCTIONS : 1. restart the BTS remotely. replace the alarming WAM unit. FAULT REASON : Baseband bus configuration of <x> was rejected DESCRIPTION : The baseband bus related configuration of <x> was rejected by the HW SW. If ping to the BTS is working. There is a MCU failure in the WAM or the ATM loop test at startup has failed. change the alarming unit. For more information. FAULT REASON : ATM faulty DESCRIPTION : A WAM internal failure. FlexiBTS: 1. FAULT REASON : Baseband Bus failure DESCRIPTION : The FlexiBTS has detected an abnormal operation or a failure in the BTS internal baseband bus. 2. do a site visit and restart the BTS. then restart the AXC remotely so that the BTS will also be restarted automatically. If ping to the BTS is working. MetroSite50. DSP or LTX. Triple-mode: 1. 2. 3. Triple-mode: There is a fault in the WAM processor SFN interrupt or the SFN is not being updated in the WSPC MCU. INSTRUCTIONS : UltraSite. FlexiBTS: There is such a fault in the FSM that the SFN is not being updated in the FSP MCU. If not working. If this does not help. Ping the BTS. If this does not help. Ping the AXC.

INSTRUCTIONS : Replace the WSC. 3. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation. replace both WSC units. If there is only one clock unit in the cabinet. INSTRUCTIONS : 1. If a reset does not clear the fault situation. depending on the alarm source: a. OR 1. Check the cables between the Master System Module and RF Module / Extension System Module. replace the WCI. Check the other active BTS alarms and act accordingly. If Step 1 does not help. b. INSTRUCTIONS : 1. or the WSC does not distribute the clock source. Check the BB bus configuration.7650 BASE STATION FAULTY pointed to a specific module but there are several possible fault sources. FAULT REASON : Baseband reference clock missing (WSC) DESCRIPTION : The WSC is not able to deliver the clock signals required by the other units. Reset the master System Module. Check the cables between the System Module and RF Module/Extension System Module. Reset the RF Module and/or System Module. replace the WSC. FAULT REASON : BB bus message collision error DESCRIPTION : Routed RF BB bus messages have collided and the date lost in the output LVDS link because the BB bus is configured incorrectly. Reset the RF Module by blocking/unblocking it. 2. 2. because either the transceiver circuit in the WSC or the bus is faulty. If there are two clock units in the cabinet. 2. replace the alarming RF Module/Extension System Module. INSTRUCTIONS : You have two alternative procedures: 1. 2. FAULT REASON : Baseband reference clock missing (WCI) DESCRIPTION : The WCI does not deliver the Baseband Reference Clock (BRCLK) for the relevant units. replace the WCI. replace the alarming master System Module. Reset the Extension System Module by blocking/unblocking it. c. 4. If Step 1 does not help. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 65 (244) . 5.

FAULT REASON : BB bus reception error DESCRIPTION : The master frame in the received RF BB frame is not in the correct place related to the internally generated master frame pulse. INSTRUCTIONS : 1. 4.Base Station Alarms (7000-7999) 3. FAULT REASON : BTS config error (WSMA and WSMB can not coexist) DESCRIPTION : WSMA and WSMB units are detected in the same cabinet. replace the faulty module (System Module). INSTRUCTIONS : 1. INSTRUCTIONS : 1. FAULT REASON : BB bus reception error (MUKSU) DESCRIPTION : The master frame in the received BB frame is not in the correct place related to the internally generated master frame pulse. Block/unblock the FSM. Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place. If only one FSP in the BTS generates this alarm. Replace the alarming unit (System Module). the FSM is faulty. This situation is triggered also when the links will not synchronise with each other. Unblocking the BTS causes a site reset. 2. If that does not help. 2. The meaning of the fault is to avoid alarms that may rise during a BTS maintenance task. Replace the alarming unit (System Module). If all FSPs generate this alarm. 4. They cannot coexist in the BTS. 66 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . unblock the BTS. Replace the alarming unit (Master System Module). FAULT REASON : BTS Blocked DESCRIPTION : The BTS is blocked with the BTS Site Manager. Check the cables between the Master System Module and RF Module / Extension System Module. Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place. or vice versa. Replace the alarming unit (RF Module / Extension System Module). INSTRUCTIONS : To cancel the alarm. the FSP is faulty. The data packet is lost or the content is corrupted. 3. Check the cables between the Master System Module and RF Module/Extension System Module. 2. INSTRUCTIONS : Replace the conflicting unit WSMA with the WSMB. FAULT REASON : BB bus transmission error DESCRIPTION : A decoding error detected in a LVDS link.

Check that the unit is properly connected. 4. Reset the System Module. FlexiBTS: . or a corrupted SW file has been detected in the FLASH. 2. If the unit led does not light up. If the ROM disk is corrupted. Check the commissioning parameters with the BTS Site Manager Commissioning Wizard. check the SW files. Reset the RF Module and/or System Module. or there is a mismatch between them. FAULT REASON : BTS internal SW management problem DESCRIPTION : Software update to a module or subassembly has failed. If the fault still exists after 10 minutes. MetroSite50. MetroSite. Reset the RF Module by blocking/unblocking it.The BTS unit properties data is invalid or missing. depending on the alarm source: a. MetroSite. Check the other active alarms. Download the SW again. Replace the FCM. Download two different SW packages so that the faulty file will be removed from the BTS. Triple-mode: 1. FAULT REASON : Commissioning error: <x> DESCRIPTION : Some of the commissioning parameters are either missing or faulty. change the alarming module. Triple-mode: The BTS unit properties data is invalid or missing. FlexiBTS: 1. 3. INSTRUCTIONS : 1. replace the alarming unit. If that does not help. . 2.7650 BASE STATION FAULTY FAULT REASON : BTS file error DESCRIPTION : UltraSite. It has not replied to the message that has been sent/resent to it.WN4. b. INSTRUCTIONS : 1. 3. 3. Download the SW again. MetroSite50. Replace the alarming module. Update and activate the SW to the BTS. INSTRUCTIONS : UltraSite. Load the correct commissioning file to the BTS. the unit is faulty. INSTRUCTIONS : 1. .1 onwards: The FSP MCU SW file is invalid or missing.The optical interface FPGA file is invalid or missing. Check the alarming DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 67 (244) . FAULT REASON : Communication failed with application <x> DESCRIPTION : Communication with the application <x> failed. 2. 2. Download two different SW packages so that the faulty file will be removed from the BTS. 5.

3. the FSP is faulty. MetroSite 50. Recommission the BTS to ensure that all parameters are correctly configured. 3. replace the faulty module (System Module). INSTRUCTIONS : 1. Otherwise. 2. Block the alarming WSP. replace the alarming WSP unit. If only one FSP in the BTS generates this alarm. FlexiBTS: 1. FAULT REASON : Communication failure inside WSP DESCRIPTION : An internal communication failure between the DSP processors. 68 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 2. INSTRUCTIONS : 1. Check the RNC alarms for the alarming local cell (LCR). 2. the FSM is faulty. Check that the BTS cell parameters from the RNC match the BTS HW configuration (for example frequency. 4. If the "Unit autonomous reset as a recovery action" alarm has occurred for the alarming WSP. FAULT REASON : Configuration error: <x> DESCRIPTION : There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. If all FSPs generate this alarm. replace the faulty unit (System Module). INSTRUCTIONS : UltraSite. MetroSite.Base Station Alarms (7000-7999) unit. If that does not help. the FSP is faulty. power). the FSP/FSM reset recovery. the FSM is faulty. Restart the faulty unit. 2. FAULT REASON : Downlink data buffer synchronization failure DESCRIPTION : The downlink data buffer has lost synchronisation. If all FSPs generate this alarm. 4. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration. 2. Another possibility is that there is a mismatch between the BTS configuration and the RNC parameters. Triple-mode: 1. If only one FSP in the cabinet generates this alarm. 4. check for other alarms. Block/unblock the FSM. The fault may be in the WTR or WPA (see Troubleshooting instructions). If that does not help. 3. Check the alarm history.

FAULT REASON : Failure in optical RP3 interface DESCRIPTION : The FlexiBTS has detected an abnormal operation or a failure in an optical RP3 interface between two modules. If a reset does not clear the fault situation. 6. MetroSite 50. Otherwise. This alarm may occur if the WSP is hot removed or the WSP is crashed. If that does not clear the fault situation. 2. the WSP is faulty. Depending on the alarm source. If only one FSP in the BTS generates this alarm. replace the alarming RF Module/Extension System Module. MetroSite. The failure cannot be pointed to a specific module but there are several possible fault sources. 5. Extension System Module and/or System Module by blocking / unblocking it. INSTRUCTIONS : UltraSite. check for other alarms. Check also the SFP in the other end and replace it if needed. MetroSite. 2. the WAM is faulty. INSTRUCTIONS : If the failure still exists after the site reset. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 69 (244) . MetroSite 50. 3. 2. If all WSPs generate this alarm. Triple-mode: Synchronisation between the WAM and WSP is lost. Check the other active BTS alarms and act accordingly. Please notice that dirty optical connectors may cause the signal level to drop too low. 4. the FSP is faulty. reset the RF Module. If all FSPs generate this alarm. 3. the WSC/WMC is faulty. the FSM is faulty. If the "# autonomous reset as a recovery action" alarm has occurred for the faulty WSP. Block/unblock the FSM. 3. FAULT REASON : Fault between WAM and WSP SFN (WSP) DESCRIPTION : UltraSite. replace the alarming System Module. replace the faulty WSP unit. If the System Module is the only alarming source or replacing the RF Module/Extension System Module does not clear the fault situation.7650 BASE STATION FAULTY FAULT REASON : DSC-bus failure DESCRIPTION : There are communication problems between the WAM and WSP. FlexiBTS: Synchronisation between the FCM and FSP is lost. If all WSPs in a subrack generate this alarm. FlexiBTS: 1. If only one WSP in the cabinet generates this alarm. Triple-mode: 1. replace the alarming Modules Small Form Factor Pluggable (SFP). Check the cables between the System Module and RF Module/Extension System Module. replace the WAM unit. INSTRUCTIONS : 1.

AXC or CIF bus failure. Block/unblock the FSM. FAULT REASON : Frame Synchronization failure DESCRIPTION : The frame clock receiver has lost its synchronisation. INSTRUCTIONS : 1. 3. FAULT REASON : Fault in ATM interface DESCRIPTION : WAM ATM interface. This will reset the BTS. Reset the site. the FSM is faulty. replace the FCM unit. If all FSPs generate this alarm. If that does not help. replace the faulty module (System Module). Reset the alarming FSM. FAULT REASON : FSP Frame synchronisation failed DESCRIPTION : One of the following Frame synchronisation signals coming from the FCM is missing: the Frame synchronisation burst. 3. Check the AXU. If resetting of the alarming module does not help. 70 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Swap the WAM units between subracks and check if the alarm follows the unit. FAULT REASON : No connection to AXU DESCRIPTION : The master WAM detected that the AXU does not respond to polling messages. replace the alarming FSM. INSTRUCTIONS : Replace the unsupported unit with a unit of the correct type. 4. Replace the faulty WAM unit. 2. If that does not help. 2. replace the faulty module (System Module). WAM processor failure. WTRA. SFN or SFCLK. WSPA. 2. INSTRUCTIONS : 1. If that does not help. the FSP is faulty. If only one FSP in the BTS generates this alarm.Base Station Alarms (7000-7999) 4. INSTRUCTIONS : 1. Block/unblock the faulty unit. The AXC may have been reset. INSTRUCTIONS : 1. WMCM or WTRB) has been detected in the cabinet. The FSM internal frame clock is not synchronised with the FSM 100 Hz frame clock. 4. FAULT REASON : Frame number synchronisation error in optical interface DESCRIPTION : Optical interface (OIC) is not synchronised to the system frame number (SFN). FAULT REASON : Incompatible unit detected DESCRIPTION : An unsupported unit (for example a WSMA. 2. Check the backplane connection between the WAM and AXU.

Check for alarms on the AXC. 2. Check the power cables and connectors as well as the I2C bus cables. If that does not help. Check the alarm history. INSTRUCTIONS : Replace the alarming module. If the unit led does not light up. Check that the unit is properly connected. Check the faulty unit. INSTRUCTIONS : UltraSite. the unit is faulty. the unit is faulty. FAULT REASON : Optical interface FPGA sw crc check failed DESCRIPTION : The CRC check has failed in three consecutive optical interface FPGA SW downloading attempts. inserting the first removed WSC back into the cabinet causes a site reset. alarming unit and subrack. replace the faulty unit. 4. 5.7650 BASE STATION FAULTY INSTRUCTIONS : 1. 2. Restart the AXC remotely. Check the alarm history. reset the site. FAULT REASON : Not able to synchronize baseband bus with <x> DESCRIPTION : The baseband bus synchronisation towards <x> failed. Check that the unit is properly connected. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 71 (244) . This will also cause a BTS restart. MetroSite. If both WSCs are removed. If SW updates have been done recently. MetroSite50. 3. INSTRUCTIONS : Check the alarming unit. If the unit led does not light up. If the WAF or WIC is alarming. If the 7650 BASE STATION FAULTY alarm is issued. Cancel alarms: Removing and inserting the WIC. FAULT REASON : No connection to unit DESCRIPTION : The connection to a unit that belongs to the BTS configuration has been lost. 2. reload the SW. try recommissioning the site. First try to reset the site by the software. WSM or primary WAM causes a site reset. Change the alarming AXC unit. Triple-mode: 1. The fault may also be in the WPS unit or backplane. 3. FlexiBTS: 1.

Replace the alarming WPS unit. 2. FAULT REASON : Oven oscillator clock missing DESCRIPTION : The WSC is not able to deliver the clock signals required by the other units. FAULT REASON : R-bus error DESCRIPTION : UltraSite. INSTRUCTIONS : Replace the clock unit. FAULT REASON : Oven oscillator clock missing DESCRIPTION : The output signal of the OXCO is missing and the FCM cannot deliver the 30. The optical interface cannot attach the clock signal coming from the clock device. Check the units that are supplied by the alarming WPS.6MHz VCXO is broken . Replace the FSM. 2. it may affect the WPS and the "Output Voltage Fault" alarm is generated. Possible reasons: . Block/unblock the FSM.30. Check backplane connectors and cables. Usually the reason for the fault is the unit itself but in some cases the reason can be the unit that the WPS feeds. FAULT REASON : POST test failed DESCRIPTION : The unit or module has been tested during the BTS power-on self test (POST) and a failure has been detected. MetroSite 50. Block/unblock the FSM. If a short circuit occurs in the fed unit. Check the other active alarms. 4. 3.72MHz reference clock receiving signal interrupted . FAULT REASON : Power unit output voltage fault DESCRIPTION : The output voltage is too low or too high. Replace the alarming unit. INSTRUCTIONS : 1. 3.Cleaner lock or parallel 153. INSTRUCTIONS : 1. INSTRUCTIONS : 1. 2. MetroSite. Block/unblock the alarming unit 2.Base Station Alarms (7000-7999) FAULT REASON : Optical Interface Frame clock faulty DESCRIPTION : The Cleaner Clock lock VCXO of the PLL does not get the adjusting voltage.72 MHz System Clock required by other units. Remove/reinsert the alarming unit. Triple-mode: The bus 72 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . INSTRUCTIONS : 1. Replace the FSM.Cleaner lock initialisation has failed from the FPGA (not likely).

FAULT REASON : Starting temperature below minimum DESCRIPTION : The temperature measured from the FSPs is less than -10°C. Triple-mode: 1. 2. 2. Check the active RF Module alarms and act accordingly. Run a WCDMA BTS loop test to locate the faulty unit. 4. MetroSite. Update the BTS SW. the FSM is faulty. 2. the FSP is faulty. Replace the faulty unit (System Module). INSTRUCTIONS : Check the environmental conditions of the site. replace the faulty module (System Module). FAULT REASON : SFN Signal error DESCRIPTION : The system frame number receiving fault. Check the cabling between the System Module and RF Module. The BTS cannot start properly due to the FSPs that cannot be powered at cold conditions. The heating is needed. 3. 4. an illegal SFN value in uplink. Block/unblock the FSM. Replace the faulty unit. If the WSP is faulty. check the WTR and WSM cable.7650 BASE STATION FAULTY between the WSP and WTR does not work. Load the correct commissioning file to the BTS. If only one FSP in the BTS generates this alarm. 5. INSTRUCTIONS : 1. the reason for the alarm is a faulty WSM/WMC or WSP. The R bus errors are probably caused by a faulty WSM or WTR. If the WSM/WMC also generates an alarm from a WTR unit. block/unblock it. If all FSPs generate this alarm. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 73 (244) . Check and correct the contents of the commissioning file. If there are no active WSM/WMC alarms. INSTRUCTIONS : UltraSite. If that does not help. 3. MetroSite 50. 2. FlexiBTS: Error in the FSP or in the connection between the FSP and FCM. 3. FAULT REASON : SW does not support commissioning file DESCRIPTION : The software does not support the new commissioning file loaded to the BTS. FlexiBTS: 1. INSTRUCTIONS : 1.

INSTRUCTIONS : UltraSite. If all FSPs generate this alarm. 3. The FSM has already found the frame synchronisation but the FSM frame clock does not match to the FSM internal frame clock. MetroSite. If all FSPs generate this alarm. If that does not help. the FSP/FSM reset recovery. replace the faulty unit (System Module). MetroSite50. If a reset does not help the fault situation. INSTRUCTIONS : 1. Reset the System Module. Triple-mode: Block/unblock the alarming unit.Base Station Alarms (7000-7999) FAULT REASON : Synchronization failure DESCRIPTION : The frame burst phase has moved compared to the internal counter. replace the RF Module behind that link. If the alarming link remains the same. 74 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 2. If the alarming link changes. the FSM is faulty. If only one FSP in the cabinet generates this alarm. Block/unblock the FSM. Restart the faulty unit. 4. If only one FSP in the BTS generates this alarm. 2. 4. replace the faulty module (System Module). 3. replace the System Module. FAULT REASON : Tbus receiver parity fault DESCRIPTION : Data or synchronisation failure in the System Module. A unit RNW configuration failure. the FSP is faulty. FlexiBTS: a FSP unit to FCM allocation failure. A telecom RNW reconfiguration failure. MetroSite. FAULT REASON : Telecom configuration failure DESCRIPTION : A telecom slave configurations or registrations failure. MetroSite50. Or UltraSite. two antenna carriers are affected. replace the System Module. 2. the FSM is faulty. the FSP is faulty. Then check where the alarm is now reported. FAULT REASON : System Module failure DESCRIPTION : The FlexiBTS has detected an abnormal operation or a failure in the System Module internal functionality. Triple-mode: a WSP unit to WAM allocation failure. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. INSTRUCTIONS : 1. FAULT REASON : Synchronization failure in Optical Interface <opt link/RP3 link> DESCRIPTION : The RP3 channel has achieved the frame synchronisation state and then lost it. If that does not help. INSTRUCTIONS : Swap the alarming and working links. INSTRUCTIONS : 1.

If Step 2 does not help. If the WAM is the alarm source. it takes a while for the BTS/modules to heat themselves to the threshold value. replace the alarming unit. replace the alarming unit. make sure the airflow to the BTS modules is unobstructed. this alarm causes the alarm. 2. perform a power-off reset. Check the alarm history to know why the WAMs' switchover occurred. Check if the non-commissioned WAM is the Master WAM. FAULT REASON : Unit initialization failure DESCRIPTION : A unit or an IP address initialisation has failed. the BTS modules are not covered with anything. MetroSite. that is. or the ambient temperature of the module (s) is outside the specified limits. 2. replace the alarming unit. If step 3 does not help. 3.7650 BASE STATION FAULTY FlexiBTS: In case of a FR. INSTRUCTIONS : UltraSite. If the ambient temperature is too high. If that does not help. perform a power-off reset. If the FCM is the alarm source. 4. check the RNC IP address in the commissioning file and modify the file if needed. Check the ambient temperature of the BTS/modules. If so. MetroSite50. Check the other BTS alarms and act accordingly. Block/unblock the alarming unit. Reset the alarming module by blocking/unblocking it. replace the alarming Module. Triple-mode: 1. INSTRUCTIONS : 1. 2. 3. FlexiBTS: 1. FAULT REASON : Unit not supported by current BTS SW version DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 75 (244) . the module needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. FAULT REASON : Temperature alarm DESCRIPTION : The RF Module or System Module internal temperature exceeds the threshold value. If that does not help. 4. Block/unblock the alarming unit. check the RNC IP address in the commissioning file and modify the file if needed. If that does not help. If the ambient temperature is too low. If a reset does not clear the fault situation. 3.

3. FAULT REASON : Unit SW download failed DESCRIPTION : The software update to the unit or subunit has failed. If that does not help. Block/unblock the active WSC unit. FAULT REASON : Unknown HW resource DESCRIPTION : A unit cannot be identified by its product code or by its physical device address (object ID). INSTRUCTIONS : 1. INSTRUCTIONS : Replace the unit or upgrade the BTS SW. FAULT REASON : WCI baseband reference clock failure DESCRIPTION : 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. replace the faulty module (System Module). If only one FSP in the BTS generates this alarm. 4. the FSP is faulty. If all FSPs generate this alarm. The BTS power supply is cut off. INSTRUCTIONS : 1. 2. Replace the alarming unit. FAULT REASON : WIB unit AC line break fault DESCRIPTION : There is a mains break. INSTRUCTIONS : 1. INSTRUCTIONS : 1. INSTRUCTIONS : Replace the faulty unit. 76 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .Base Station Alarms (7000-7999) DESCRIPTION : An unsupported unit was found in the BTS. Block/unblock the FSM. 2. replace the faulty module. 2. Replace both WSC units. Reset the BTS. FAULT REASON : Uplink data buffer synchronization failure DESCRIPTION : The uplink data buffer loses the synchronisation. Replace the WCI unit. Block/unblock the alarming unit. 3. INSTRUCTIONS : Check the power supply to the BTS. INSTRUCTIONS : Replace the unit. 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. 2. FAULT REASON : Unknown product code DESCRIPTION : A unit cannot be identified by its product code but is known by its physical device address (object_ID). the FSM is faulty. If Step 1 does not help. FAULT REASON : Unit synchronization failed DESCRIPTION : The WAM/WSPC synchronisation has failed.

DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 77 (244) .7650 BASE STATION FAULTY FAULT REASON : WSP PCI-bus failure DESCRIPTION : There is a fault in the internal WSP/FSP PCI bus target (DSP) connections. Cancelling Do not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected. Some of the WSP/FSP DSP processors may be broken and out of use. INSTRUCTIONS : Replace the alarming unit.

Base Station Alarms (7000-7999) 78 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Before a unit/module is replaced at the BTS. If the site reset or unit/module block/unblock does not help. Instructions Verify the configuration of a BTS by checking the commissioning. cabling and correct installation of the units/modules at the BTS. When an active alarm is a 'Start' alarm. a site reset is required to cancel the alarm. which might have caused the misbehaviour of the unit/module.7651 BASE STATION OPERATION DEGRADED 29 7651 BASE STATION OPERATION DEGRADED Meaning A major fault (or faults) has occurred in the base station. replace the faulty unit/module (see source of the alarm and instructions fields of the corresponding alarm). see instructions on Alarm Structure. Supplementary information fields 1 rack (cabinet) number 2 shelf number 3 slot 4 type of unit 5 unit number 6 subunit number For more information. Make sure the environment does not cause the fault. Refer also to the individual DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 79 (244) . Check the reason for the fault from the supplementary text field of the alarm. the site should be reset to recover from any temporary faults.

Replace the alarming unit. FAULT NAME DESCRIPTION : Active clock tuning fault : The phase measurement cannot be performed in the active WSC or WMC. see Nokia WCDMA BTS Alarm Descriptions (SW and release document). If there is a WMC or only one WSC. INSTRUCTIONS : 1. Check the cabling. replace the alarming System Module. FAULT NAME DESCRIPTION : 10b8b coding error in Optical Interface device <opt link/RP3> : The fibre cable has interference. FAULT NAME DESCRIPTION 80 (244) : Address mismatch in summing : Address mismatch in the BB in summing. INSTRUCTIONS : 1. A physical connection failure between the optical interface and summing function (caused by bad circuit joints. 2. Note that because of a fault situation in the active clock. Run fast tuning with the BTS Site Manager. 3. replace the alarming module. If that does not help. 2. the tuning will continue but cells will remain disabled. reset the RF Module and/or Extension System Module by blocking/unblocking it. for example). FAULT NAME DESCRIPTION : 2M external reference missing : The reference clock monitoring has detected a loss of signal in the reference received from the external reference in the System Module. If that does not help. If that does not clear the fault situation. 2. contact the local Help Desk.Base Station Alarms (7000-7999) alarm instructions. To make sure that the tuning is correct. run "Fast Tune BTS Clock" with the BTS Site Manager after switchover when the new WSC is taken into use. reset the previous cabinet. the data becomes faulty. Block/unblock the alarming unit. 3. INSTRUCTIONS : 1. There are two possible causes: # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Depending on the alarm source. replace the alarming RF Module/Extension System Module. For more information. the redundant clock is not tuned. If the System Module is the only alarming source or replacing the RF Module/Extension System Module does not clear the fault situation. If it is correct.

There are two possible causes: Configuration error (2 different FSPs functioning) . Triple-mode: 1.appears once when unsynchronised data is sent by the BB.after acknowledgement the fault will return again.after acknowledgement the fault will return again. Ping the AXC. If this does not help.7651 BASE STATION OPERATION DEGRADED Configuration error (2 different FSPs functioning) . INSTRUCTIONS : Check the baseband bus configuration parameters from the commissioning file. If it is not working. MetroSite. 3. 3. INSTRUCTIONS : 1. Ping the AXC. If ping to the BTS is working. FlexiBTS: There is such a fault in the FSM that the SFN is not being updated in the FSP MCU. 2. FAULT NAME DESCRIPTION : ATM processor faulty : UltraSite. restart the BTS remotely. INSTRUCTIONS : UltraSite. If not working. MetroSite. MetroSite 50. do a site visit and restart the BTS. If not working but ping to the AXC is working. There is a MCU failure in the WAM or the ATM loop test at startup has failed. MetroSite 50. Ping the BTS. Data corruption on the bus . Ping the BTS.appears once when unsynchronised data is sent by the BB. then restart the AXC remotely so that the BTS will also be restarted automatically. FAULT NAME : ATM faulty DESCRIPTION : A WAM internal failure. do a site visit and restart DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 81 (244) . Triple-mode: There is a fault in the WAM processor SFN interrupt or the SFN is not being updated in the WSPC MCU. If ping to the BTS is working. restart the BTS remotely. FAULT NAME DESCRIPTION : Address mismatch in summing : Address mismatch in the BB in summing. 2. INSTRUCTIONS : Check the BB bus configuration parameters from the Site Configuration File (SCF). Data corruption on the bus . If it is not working but ping to the AXC is working. replace the alarming WAM unit. restart the AXC remotely so that the BTS will also be restarted automatically.

3. 2. FAULT NAME DESCRIPTION : ATM traffic overload : A buffer overflow caused by a traffic overload. 2. Replace the alarming unit (RF Module / Extension System Module). The failure cannot be pointed to a specific module but there are several possible fault sources. Check that bandwidths (cells/s) are the same at the BTS. Replace the alarming unit (Master System Module). The maximum capacity is exceeded and some data discarded. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : BB bus message collision error : Routed RF BB bus messages have collided and the data is lost in the output LVDS link because the BB bus is configured incorrectly. depending on the alarm source: a. 3. FlexiBTS: 1. 2. Check the BB bus configuration from commissioning. Reset the RF Module and/or System Module. 3. If this does not help.Base Station Alarms (7000-7999) the BTS. Reset the RF Module by blocking/unblocking it. INSTRUCTIONS : 1. Reset the BTS. 2. INSTRUCTIONS : 1. Check the other active BTS alarms and act accordingly. Check the data integrity from the incoming Iub (see Troubleshooting instructions). If the BTS reset does not help. replace the alarming WAM unit. Reset the Extension System Module by 82 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 4. FAULT NAME DESCRIPTION : Baseband bus configuration of <x> was rejected : The baseband bus related configuration of <x> was rejected by the HW SW. Check the cables between the System Module and RF Module/Extension System Module. DSP or LTX. INSTRUCTIONS : Replace the alarming module. Check the cables between the Master System Module and RF Module / Extension System Module. change the alarming module. AXC and RNC. Check the other transmission elements' active alarms (see the Alarms for AXC document). FAULT NAME DESCRIPTION : Baseband Bus failure : The FlexiBTS has detected an abnormal operation or a failure in the BTS internal baseband bus. b.

the FSP is faulty. replace the alarming RF Module/Extension System Module. INSTRUCTIONS : 1. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : BB bus reception error : The master frame in the received RF BB frame is not in the correct place related to the internally generated master frame pulse. INSTRUCTIONS : 1. 5. the FSM is faulty. Replace the alarming unit (System Module). Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place. c. FAULT NAME DESCRIPTION : BB bus transmission error : A decoding error detected in a LVDS link. 4.7651 BASE STATION OPERATION DEGRADED blocking/unblocking it. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation. FAULT NAME DESCRIPTION : BB bus reception error (MUKSU) : The master frame in the received BB frame is not in the correct place related to the internally generated master frame pulse. Check the cables between the Master System Module and RF Module/Extension System Module. Retry the SW update. 3. Block/unblock the FSM. 4. INSTRUCTIONS : 1. If only one FSP in the BTS generates this alarm. or a corrupted flash file system. Replace the alarming unit (the System Module). 2. The error can be caused by a unit reset during the SW update. 2. This situation is triggered also when the links will not synchronise with each other. Check the cables between the Master System Module and RF Module / Extension System Module. Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place. FAULT NAME DESCRIPTION : BS SW download or activation failed : The SW update to the BTS has failed. If the reset does not clear the fault situation. The data packet is lost or the content is corrupted. replace the alarming master System Module. If that does not help. If all FSPs generate this alarm. Reset the master System Module. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 83 (244) . replace the faulty module (System Module). a hardware problem in the unit or cabinet. 2.

FlexiBTS: . 2. 2. INSTRUCTIONS : 1. Triple-mode: The BTS unit properties data is invalid or missing. Triple-mode: 1. Download the SW again.The BTS unit properties data is invalid or missing.Base Station Alarms (7000-7999) 2. INSTRUCTIONS : UltraSite. Download two different SW packages so that the faulty file will be removed from the BTS. If the fault still exists after 10 minutes. 3. The error can be caused by a unit reset during the SW update. MetroSite 50.The optical interface FPGA file is invalid or missing. 3. FlexiBTS: . FAULT NAME DESCRIPTION : BTS file error : UltraSite. Triple-mode: 1. MetroSite50. 3. 84 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . a hardware problem in the unit or cabinet. FAULT NAME DESCRIPTION : BS SW download or activation failed : The SW update to the BTS has failed. If other flash memory-related alarms are active for the alarming unit at the same time. FlexiBTS: 1. Download two different SW packages so that the faulty file will be removed from the BTS. MetroSite.The BTS unit properties data is invalid or missing. Replace the FCM. 2.1 onwards: The FSP MCU SW file is invalid or missing. INSTRUCTIONS : UltraSite. 2. Download the SW again. Retry the SW update. MetroSite.The optical interface FPGA file is invalid or missing. or a corrupted flash file system. Download two different SW packages so that the faulty file will be removed from the BTS. replace the alarming unit. replace the alarming unit. . MetroSite. FAULT NAME DESCRIPTION : BTS file error : UltraSite. . replace the faulty unit. If the fault still exists after 10 minutes. Download the SW again. If the 'ROM disk corrupted during SW update' or other flash memory-related alarm is active for the faulty unit at the same time. Triple-mode: The BTS unit properties data is invalid or missing.WN4. replace the alarming unit. MetroSite50. MetroSite 50. MetroSite. .

4.4095. replace the system module. check the SW files. Reset the System Module.4095. Reset the RF Module by blocking/unblocking it. Reset the site. INSTRUCTIONS : 1. INSTRUCTIONS : 1. 2. FAULT NAME DESCRIPTION : BTS internal SW management problem : Software update to a module or subassembly has failed. If the ROM disk is corrupted. Replace the alarming module. 2. The DAC word value of the OCXO is lower than 205 or greater than 3891 (5% of the total adjustment area). 4. or a corrupted SW file has been detected in the FLASH. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 85 (244) . 4. 5. Start the fast tuning with BTS Site Manager. 2. FAULT NAME DESCRIPTION : BTS Master Clock tuning failure : The OCXO adjustment area is reaching its limit value. 3. FAULT NAME DESCRIPTION : BTS Master Clock tuning failure : The OCXO adjustment area is reaching its limit value. replace the FCM unit. The range for the DAC word is 0 . Replace the system module. b. INSTRUCTIONS : 1. Check the reference signal from the FTM. The DAC word value of the OCXO is lower than 205 or greater than 3891 (5% of the total adjustment area). Start the fast tuning with BTS Site Manager. 2.7651 BASE STATION OPERATION DEGRADED FlexiBTS: 1. 3. change the alarming module. 3. Check the other active alarms. Reset the site. The range for the DAC word is 0 . Update and activate the SW to the BTS. Download two different SW packages so that the faulty file will be removed from the BTS. Reset the RF Module and/or System Module. depending on the alarm source: a. If that does not help. If that does not help. If that does not help. Download the SW again. Check the reference signal from the FTM. 3.

it turns off the clock reference signal which is normally delivered to the BTS master clock. The clock of the BTS transmission unit (FT) is in locked mode (PLL) to the Iub. . 2. In case of a BTS equipment fault. Note! Normally the reason is not an equipment fault. Note! The BTS and the AXC can be restarted remotely. Especially alarm activity (frequent alarms/cancels instead of a stable alarm state) points to the instability of the transmission network.Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : BTS reference clock missing : The BTS master clock uses the Iub interface as a clock reference. FAULT NAME DESCRIPTION : BTS RNC interface signalling link failure : A common or a dedicated Node-B Application Protocol (NBAP) or an AAL2 signalling link failure. the RNC or a broken WAM. Reset the AXC. 3. the source may be: . MetroSite. 86 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .System Module: Check the operation and replace if needed. Check also the synchronisation settings of the BTS transmission unit. INSTRUCTIONS : UltraSite. In this case. the fault in the transmission network must be corrected. 4. 1. according to the synchronisation priority list of the transmission unit. but there are cuts in the Iub interface causing the FT clock to drop to holdover mode.Transport part: Check the alarms of the BTS transmission unit and act accordingly. MetroSite50. INSTRUCTIONS : The fault may be either in the BTS or Iub interface (in the transmission network). The BTS transmission unit operates so that if it is not locked to any synchronisation source. causing the transmission units internal clock to drop to hold-over mode. Change the WAM unit. 2. It can be caused either by a transmission network problem. The synchronisation source of the BTS transmission unit (set by the synchronisation priority setting) may be missing. Check the BTS and RNC transmission settings. This alarm is generated if the reference clock monitoring function of the BTS does not receive the clock reference signal from the transmission unit. Triple-mode: 1. not to a fault in the unit. The most common reason for this alarm is frequently breaking transmission. Check the other transmission elements' active alarms (see the Alarms for AXC document).

4. Triple-mode: 1. Reset the AXC. The most common reason for this alarm is a frequently breaking transmission. 3. INSTRUCTIONS : UltraSite. Check the BTS and RNC transmission settings. MetroSite. Check the transmission links to the RNC. Reset the site. Check the transmission links to the RNC. 3. INSTRUCTIONS : UltraSite. Change the WAM unit. FAULT NAME DESCRIPTION : BTS RNC interface signalling link failure : A common NBAP link failure. FAULT NAME DESCRIPTION : BTS RNC interface signalling link failure : A dedicated Node-B Application Protocol (NBAP) link failure. It can be caused by the RNC. 4. 2. MetroSite. Check the FCM. 2. Check the BTS and RNC transmission settings. 4. Reset the FT. MetroSite50. Check the other transmission elements' active alarms (see the Alarms for AXC document). Note! The BTS and the AXC can be restarted remotely. FlexiBTS: 1. Check the BTS and RNC transmission settings. Check the BTS and RNC transmission settings. 3. Triple-mode: 1. Reset the AXC. 3. 2. Check the FCM. Change the WAM unit. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 87 (244) . 2. 4. MetroSite50. Check the other transmission elements' active alarms (see the Alarms for AXC document).7651 BASE STATION OPERATION DEGRADED FlexiBTS: 1. It can be caused by a transmission network problem.

MetroSite. It can be caused by a transmission network problem. Change the WAM unit. FlexiBTS: 1. 88 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 4. Check the BTS and RNC transmission settings. 2. 3. 2. 2. Check the BTS and RNC transmission settings. Check the system module. 3. 3. Reset the BTS. Check the BTS and RNC transmission settings. Check the transmission links to the RNC. 4. FAULT NAME DESCRIPTION : BTS RNC interface signalling link failure : An AAL2 signalling link failure. It can be caused by a broken WAM. Reset the AXC. 4. MetroSite 50. Reset the BTS. Check the other transmission elements' active alarms (see the Alarms for AXC document). INSTRUCTIONS : UltraSite. Note! The BTS and the AXC can be restarted remotely. The most common reason for this alarm is a frequently breaking transmission. Check the other transmission elements' active alarms (see the Alarms for AXC document). Note! The BTS and the AXC can be restarted remotely. Check the BTS and RNC transmission settings. The most common reason for this alarm is a frequently breaking transmission.Base Station Alarms (7000-7999) Note! The BTS and the AXC can be restarted remotely. FAULT NAME DESCRIPTION : BTS RNC interface signalling link failure : A common NBAP link failure. 3. Change the WAM unit. Triple-mode: 1. FlexiBTS: 1. 2. Check the transmission links to the RNC. Reset the AXC. INSTRUCTIONS : 1.

2. or there is a mismatch between them. Check that the door switches function correctly and that they have been adjusted correctly. Triple-mode: 1. INSTRUCTIONS : Reconfigure the BTS with the Commissioning Wizard. INSTRUCTIONS : UltraSite. MetroSite. Note! The BTS and the AXC can be restarted remotely. Check the other transmission elements' active alarms (see the Alarms for AXC document). 2. INSTRUCTIONS : 1. FAULT NAME DN99580892 Issue 6-3 en 12/06/2008 : Communication failed with application <x> # Nokia Siemens Networks 89 (244) . 4. It can be caused by the RNC. Check the commissioning parameters with the BTS Site Manager Commissioning Wizard. or there are errors in the commissioning file.7651 BASE STATION OPERATION DEGRADED 4. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : Commissioning error: <x> : Some of the commissioning parameters are either missing or faulty. Replace the System Module. Check the BTS and RNC transmission settings. FlexiBTS: 1. FAULT NAME DESCRIPTION : BTS RNC interface signalling link failure : A dedicated Node-B Application Protocol (NBAP) link failure. 3. 3. Reset the AXC. Load the correct commissioning file to the BTS. 2. Check the transmission links to the RNC. Reset the BTS. FAULT NAME : Cabinet door open DESCRIPTION : The cabinet door is open or the cabinet door sensor is faulty. MetroSite 50. 2. Check the BTS and RNC transmission settings. 4. Replace the System Module. Change the WAM unit. FAULT NAME DESCRIPTION : Commissioning parameter mismatch : A commissioning parameter does not have a valid value (the parameter is missing or it has a value outside the value range). Ensure that the cabinet door (s) are properly closed.

Block the alarming WSP. 3. If the unit led unit is faulty. FAULT NAME DESCRIPTION : Configuration error: <x> : There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. power). FAULT NAME DESCRIPTION : Connection to transmission broken : UltraSite. the FSP is faulty. MetroSite. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration. is properly connected. Another possibility is that there is a mismatch between the BTS configuration and the RNC parameters. Check the RNC alarms for the alarming local cell (LCR). MetroSite 50. The fault may be in the WTR or WPA (see Troubleshooting instructions). Check that the BTS cell parameters from the RNC match the BTS HW configuration (for example frequency. Triple-mode: 1. MetroSite. It has not that has been sent/resent to it. If that does not help. 4. INSTRUCTIONS : 1. Check the alarming 2. data or states are corrupted in the ATM. MetroSite 50. 2. application <x> failed. Recommission the BTS to ensure that all parameters are correctly configured. 2. the FSM is faulty. check for other alarms. If all FSPs generate this alarm. the unit. Otherwise. FAULT NAME : Communication failure inside WSP DESCRIPTION : An internal communication failure between the DSP processors. 90 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . If only one FSP in the BTS generates this alarm. If the "# autonomous reset as recovery action" alarm has occurred for the alarming WSP. replace the alarming WSP unit. replace the faulty module (System Module). INSTRUCTIONS : UltraSite. Block/unblock the FSM. 2. Triple-mode: The AXC is missing. FlexiBTS: 1. 3. 4.Base Station Alarms (7000-7999) DESCRIPTION : Communication with the replied to the message INSTRUCTIONS : 1. Check that the unit does not light up. Check the alarm history.

replace the WAM unit. If the transmission type is the AXC. 3. 3. replace the alarming unit. reset the WAM. FAULT NAME DESCRIPTION : DSC-bus failure : There is a failure in the bus between the WAM and WSP (DSC bus). 2. Reset the site. replace the alarming System Module. replace the faulty module (System Module). FAULT NAME DESCRIPTION : DSC-bus failure : There are communication problems between the WAM and WSP. FAULT NAME : Downlink data buffer synchronization failure DESCRIPTION : The downlink data buffer has lost synchronisation. INSTRUCTIONS : If the failure still exists after the site reset. INSTRUCTIONS : 1. Check the transmission connections. 2. If only one FSP in the BTS generates this alarm. Check the transmission connections. FAULT NAME DESCRIPTION DN99580892 Issue 6-3 en 12/06/2008 : DSP failure in radiolink creation : Radiolink creation has failed repeatedly due to the DSP # Nokia Siemens Networks 91 (244) . If that does not help. If that does not help. FlexiBTS: Data or states are corrupted in the ATM. INSTRUCTIONS : 1. 2. Triple-mode: 1. which means that messages do not get through via that DSC bus. INSTRUCTIONS : UltraSite. 4. the FSP is faulty. 2. MetroSite 50. Replace the alarming unit. Block/unblock the FSM. or possible hardware or transmission related failures. If all FSPs generate this alarm. This alarm may occur if the WSP is hot removed or the WSP is crashed.7651 BASE STATION OPERATION DEGRADED or there are possible hardware or transmission related failures. 3. If that does not help. the FSM is faulty. Block/unblock the alarming unit. FlexiBTS: 1. MetroSite.

Check the AXC configuration. for example. 2. If the reset does not clear the fault situation. Check the cables between the System Module and RF Module/Extension System Module. Reconfiguration commissioning is required for correcting the values. replace the alarming Modules Small Form Factor Pluggable (SFP). local cell resources. The error can be caused by a missing parameter in the commissioning file: the cabling information (main. 2. Update the information if needed. Check that the cell parameters. INSTRUCTIONS : 1. 3. This will also cause a BTS restart. INSTRUCTIONS : 1. Restart the AXC remotely. FAULT NAME DESCRIPTION : Failure in AXU initialization : The BTS has lost connection to the AXU or the AXU SW is incompatible. Check the other active BTS alarms and act accordingly. Block/unblock the alarming unit. MetroSite. diversity). The failure cannot be pointed to a specific module but there are several possible fault sources. 92 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Replace the alarming unit. block/unblock the extension module. MetroSite 50. The AXU does not respond to requests from the BTS. RX cabling. 4. feeder loss. replace the alarming RF Module/Extension System Module. Extension System Module and/or System Module by blocking/unblocking it. 2. reset the RF Module. FAULT NAME DESCRIPTION : Error in commissioning data : The WTR initialisation parameters are faulty. Check also the SFP in the other end and replace it if needed. feeder loss and MHA gain are correct in the commissioning file. 2. If that does not clear the fault situation. Please notice that dirty optical connectors may cause the signal level to drop too low. If the faulty FSP is in the extension module. Triple-mode: 1. 5. Depending on the alarm source.Base Station Alarms (7000-7999) rejection. FlexiBTS: 1. otherwise block/unblock the BTS. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : Failure in optical RP3 interface : The FlexiBTS has detected an abnormal operation or a failure in an optical RP3 interface between two modules. INSTRUCTIONS : UltraSite.

4. INSTRUCTIONS : 1. If all FSPs generate this alarm. Block/unblock the FSM. If only one WSP in the cabinet generates this alarm. 2. 3. the WSP is faulty. If that does not help. FAULT NAME DESCRIPTION : Fault between WAM and WSP SFN (WSP) : UltraSite. INSTRUCTIONS : UltraSite. If only one FSP in the BTS generates this alarm. replace the faulty WSP unit. If all WSPs in a subrack generate this alarm. 2. the FSM is faulty. The AXC may have been reset. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 93 (244) . the WAM is faulty. INSTRUCTIONS : 1. Triple-mode: Synchronisation between the WAM and WSP is lost. FlexiBTS: 1. If the "# autonomous reset as a recovery action" alarm has occurred for the faulty WSP. check for other alarms. That will reset the BTS. FlexiBTS: Synchronisation between the FCM and FSP is lost. 2. If all WSPs generate this alarm. If that does not help. Check the AXU. the FSP is faulty.7651 BASE STATION OPERATION DEGRADED 6. 2. 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 faulty module (System Module). Block/unblock the alarming unit. Replace the alarming WAM unit. replace the alarming System Module. This will reset the BTS. Triple-mode: 1. FAULT NAME : Fault in ATM interface DESCRIPTION : WAM ATM interface is not responding correctly. the WSC/WMC is faulty. Swap the WAM units between subracks and check if the alarm follows the unit. MetroSite. FAULT NAME DESCRIPTION : Fault in ATM interface : WAM ATM interface. MetroSite. WAM processor failure. 3. Block/unblock the alarming unit. replace the alarming unit. MetroSite 50. MetroSite 50. Otherwise. 3. AXC or CIF bus failure.

INSTRUCTIONS : Remove Radio Modules from the intended extension system module and hot insert them to the intended master system module. If the ROM disk is corrupted. INSTRUCTIONS : UltraSite. 2. If the ROM disk is corrupted. If that does not help. The internally generated frame clock may have # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . MetroSite. MetroSite 50. MetroSite. FAULT NAME DESCRIPTION : Fault in O&M and DSP SW interface : UltraSite. If that does not help. change the alarming unit. FlexiBTS: 1. Check the backplane connection between the WAM and AXU. replace the alarming unit. the flash chip may be broken. Block/unblock the alarming unit. INSTRUCTIONS : UltraSite. FlexiBTS: 1. Triple-mode: 1. MetroSite 50. There are no recovery actions and due to that the block/unblock can be tried once. FAULT NAME DESCRIPTION : Faulty configuration of system modules : There is possibly a faulty configuration with the Radio Modules connected to both the master system module and intented extension system module. 2. Block/unblock the alarming unit. Triple-mode: 1. replace the alarming module. Triple-mode: A communication failure between the WAM and DSP. Replace the alarming unit. There are no recovery actions and due to that the block/unblock can be tried once. Block/unblock the alarming unit. 2. MetroSite 50. FAULT NAME DESCRIPTION : Flash operation failure : The flash memory operation failure. MetroSite. Check the other active alarms. FAULT NAME DESCRIPTION 94 (244) : Frame clock deviation fault : Synchronisation to the clock control unit frame pulse has been achieved earlier but it differs from the currently received frame pulse. FlexiBTS: A communication failure between the FCM and FSP. Replace the System Module. If this alarm appears continuously.Base Station Alarms (7000-7999) 4. 2. change the alarming module. Block/unblock the alarming module. Check the other active alarms.

If that does not help. INSTRUCTIONS : 1. unless it is automatically updated by the NetAct. FAULT NAME DESCRIPTION : Incompatible SW version detected : A new unit with an incompatible SW has probably been inserted in the BTS. and update the active SW version). FAULT NAME DESCRIPTION : Frame number synchronisation error in optical interface : Timing of the new RP1 sync burst deviates from the present RP1 timing maintained in the node. INSTRUCTIONS : 1. Related BTS . Replace the alarming System Module. Metrosite 50: Check the SW version of the BTS and AXC. and update compatible SW to the AXC or BTS. The FSM internal frame clock is not synchronised with the FSM 100 Hz frame clock. If all FSPs generate this alarm. replace the alarming FSM. 3. Metrosite. 2.AXC interface: check the SW version of the BTS and AXC. Check the cables between the System Module and RF Module. FAULT NAME DN99580892 Issue 6-3 en 12/06/2008 : Incompatible unit detected # Nokia Siemens Networks 95 (244) . the FSM is faulty. 3. UltraSite. 4. 2. FAULT NAME DESCRIPTION : Incompatible SW version detected : A new unit/module with an incompatible SW has probably been inserted in the BTS. Reset the System Module. INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version. 2. INSTRUCTIONS : 1. and update the active SW version). and update compatible SW to the AXC or BTS. If resetting of the alarming module does not help. unless it is automatically updated by the NetAct. FAULT NAME DESCRIPTION : Frame Synchronization failure : The frame clock receiver has lost its synchronisation. Block/unblock the FSM. the FSP is faulty. replace the faulty module (System Module). Triple-mode. If only one FSP in the BTS generates this alarm.7651 BASE STATION OPERATION DEGRADED drifted. INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version. Reset the alarming FSM.

Base Station Alarms (7000-7999) DESCRIPTION : An unsupported unit (for example a WSMA. The cell frequency is out of the minimum/maximum limit of the HW. defaults are used : An alarm is generated if even one cell parameter is missing from the RNC configuration data and the BTS commissioning file. INSTRUCTIONS : Check the parameters entered to the AXC and correct. FAULT NAME DESCRIPTION : Message type mismatch in summing : A type mismatch in the BB summing. The address is correct but the type fields do not match. WSPA. INSTRUCTIONS : Check the baseband bus configuration parameters from the commissioning file. The BTS has received a Battery Backup alarm and the Intelligent Shutdown procedure has been started. running Battery Backup : There is a fault in the mains power supply. FAULT NAME DESCRIPTION : Missing NBAP Cell parameters. There are two possible causes: Configuration error (2 different FSPs functioning) . that is.after acknowledgement the fault will return again. 2. FAULT NAME DESCRIPTION : Mains power break. Reconfigure the BTS with Commissioning Wizard if the default values for the cell parameters (such as cell radius. WMCM or WTRB) has been detected in the cabinet. If the parameters are configured to Nokia RNC. INSTRUCTIONS : Check the RNC cell parameters against the BTS HW configuration. or the carrier spacing limit is exceeded.appears once when unsynchronised data is sent by the BB. WTRA. FAULT NAME DESCRIPTION : Invalid frequency channel for the BTS HW : The requested channel in the cell setup is not acceptable. or the number of carriers for the HW type is exceeded. There are different type variations of the HW that may have limitations in the supported frequency range and bandwidth. if necessary. the frequency band and/or the carrier spacing and/or the number of carriers is/are not acceptable for the BTS HW. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : Incomplete network parameters received from AXU : Mandatory DCN and/or ATM parameters are only partially received from the AXU to a WAM unit. INSTRUCTIONS : Replace the unsupported unit with a unit of the correct type. INSTRUCTIONS : Check the mains power supply. delete and recreate BTS Object in NEMU. rampdown time/step) are not appropriate. Data corruption on the bus . 96 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

2. inserting the first removed WSC back into the cabinet causes a site reset. Check the alarm history. WSM or primary WAM causes a site reset. 3. Cancel alarms: Removing and inserting the WIC.7651 BASE STATION OPERATION DEGRADED FAULT NAME DESCRIPTION : No connection to unit : The connection to a unit that belongs to the BTS configuration has been lost. reload the SW. 2. If both WSCs are removed. the unit is faulty. replace the alarming unit. 3. Check the alarming unit. reload the SW. The fault may also be in the WPS unit or backplane. Check the power cables and connectors as well as the I2C bus cables. If the WAF or WIC is alarming. Check the alarm history. If that does not help. alarming unit and subrack. MetroSite. try recommissioning the site. 4. 2. If SW updates have been done recently. Check that the unit is properly connected. If the 7650 BASE STATION FAULTY alarm is issued. Check that the unit is properly connected. try recommissioning the site. If SW updates have been done recently. MetroSite 50. WSM or primary WAM causes a site reset. the unit is faulty. INSTRUCTIONS : 1. the unit is faulty. reset the site. The fault may also be in the WPS unit or backplane. Check that the unit is properly connected. If both WSCs are removed. alarming unit and subrack. INSTRUCTIONS : UltraSite. 5. 5. If the WAF or WIC is alarming. Check the power cables and connectors as well as the I2C bus cables. Triple-mode: 1. FlexiBTS: 1. FAULT NAME DESCRIPTION : No connection to unit : The connection to a unit belonging to the BTS configuration has been lost. Check the alarm history. If the unit led does not light up. If the unit led does not light up. 4. First try to reset the site by the software. If the unit led does not light up. Cancel alarms: Removing and inserting the WIC. inserting DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 97 (244) .

there must be at least one DSP present. If baseband pooling is in use. INSTRUCTIONS : Check the alarming unit. 2. If the alarming link changes. INSTRUCTIONS : Swap the alarming and working links. FAULT NAME DESCRIPTION : Not enough DSP resources per cell : The number of DSP units in the BTS is too small. replace the RF Module behind that link. Replace the SFP module. 2. Check the possible WSP. If that does not help. INSTRUCTIONS : Replace the alarming module. FAULT NAME DESCRIPTION : Optical Interface faulty : The Small Form Factor Pluggable (SFP) malfunction occured or the SFP module is not physically present (no electrical connection exists).Base Station Alarms (7000-7999) the first removed WSC back into the cabinet causes a site reset. there must be at least one WSP present. First try to reset the site by the software. The optical device has some malfunction. INSTRUCTIONS : 1. FAULT NAME : Not able to synchronize baseband bus with <x> DESCRIPTION : The baseband bus synchronisation towards <x> failed. WSM and WAM alarms. FAULT NAME DESCRIPTION : Not enough WSP resources per cell : The number of WSP units in the BTS is too small. Check that the SFP is connected properly. FAULT NAME DESCRIPTION : Optical interface FPGA sw crc check failed : The CRC check has failed in three consecutive optical interface FPGA SW downloading attempts. If the alarming link remains the same. If the 7650 BASE STATION FAULTY alarm is issued. check the LCG (Local Cell Group) commissioning. Check that all subracks are in working state. 98 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . For every three cells. Increase the number of WSP units in the BTS. reset the site. replace the System Module. The fault can be generated due to synchronisation problems or an incorrect initialisation. INSTRUCTIONS : Increase the number of DSP units in the BTS. replace the alarming unit. INSTRUCTIONS : 1. For every three cells. FAULT NAME DESCRIPTION : Optical Interface Data/Control/Ethernet Buffer Full : The RP3 or Ethernet buffering is not working and the buffer becomes full. The SFP is a part of the fibre cable package. Then check where the alarm is now reported.

FAULT NAME DESCRIPTION : Oven oscillator heating failure : The heating of oven oscillator fails and the unit is broken.6MHz VCXO is broken . 2. Possible reasons: . INSTRUCTIONS : 1. Replace the FSM. INSTRUCTIONS : 1. This may be because of an unsuccessful clock recovery in the optical interface due to a missing or degraded input signal.Cleaner lock or parallel 153. FAULT NAME DESCRIPTION : Oven oscillator heating failure : The OCXO warm-up takes too long and the OCXO does not become active within a period of eight minutes from the power-on. Block/unblock the FSM. FAULT NAME DESCRIPTION : Optical Interface Frame clock faulty : The VCXO does not get correct control voltage from the PLL filter of the clock cleaner. 2. The ambient temperature can also be too low or it changes too fast. The ambient temperature can also be too low or change too fast. 2.30. FAULT NAME DESCRIPTION : Oven oscillator Missing Pulse : The output signal of the OXCO has some problems and one or more clock pulses are missed. Replace the faulty System module.7651 BASE STATION OPERATION DEGRADED FAULT NAME DESCRIPTION : Optical Interface Frame clock faulty : The Cleaner Clock lock VCXO of the PLL does not get the adjusting voltage.Cleaner lock initialisation has failed from the FPGA (not likely). INSTRUCTIONS : 1. Block/unblock the FSM. Block/unblock the FSM. INSTRUCTIONS : 1. Check the active fan alarms. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 99 (244) . The optical interface cannot attach the clock signal coming from the clock device. INSTRUCTIONS : 1. The ambient temperature can also be too low or it changes too fast. INSTRUCTIONS : Replace the alarming System module. 2.72MHz reference clock receiving signal interrupted . An faulty action of a fan can also cause this alarm. Replace the FSM. Replace the clock unit. FAULT NAME DESCRIPTION : Oven oscillator heating failure : The OCXO warm-up takes too long and the OCXO does not become active within a period of eight minutes from the power-on.

Check the power unit. FAULT NAME DESCRIPTION : POST test failed : The unit or module has been tested during the BTS power-on self test (POST) and a failure has been detected. 2. MetroSite. 2. 4. Replace the alarming unit. INSTRUCTIONS : 1. Check the other MAINS related active alarms. 3. FAULT NAME : Power unit input voltage fault DESCRIPTION : The input voltage of the BTS has decreased. FAULT NAME DESCRIPTION : Power unit output voltage fault : The output voltage is too low or too high. 2. Replace the FSM. 3. Check the connection between the GPS receiver and FSM. FAULT NAME DESCRIPTION : PPS reference missing : The reference clock monitoring has detected a loss of PPS signal in the reference received from the GPS receiver. INSTRUCTIONS : 1. 2. If a short circuit occurs in the fed unit. Check the backplane connectors and cables. Replace the alarming WPS unit. INSTRUCTIONS : 1. 3. Usually the reason for the fault is the unit itself but in some cases the reason can be the unit that the WPS feeds. MetroSite 50. Check the power supply voltage. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : R-bus error : UltraSite. Check the units that are supplied by the alarming WPS. it may affect the WPS and the "Output Voltage Fault" alarm is generated. Triple-mode: The bus between the WSP and WTR does not work. Check the other active alarms. Remove/reinsert the alarming unit. If it is OK. 3. Check the GPS receiver installation.Base Station Alarms (7000-7999) 2. Block/unblock the alarming unit. The R bus errors are probably caused by a faulty WSM or WTR. FlexiBTS: Error in the FSP or in the connection between the 100 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . replace the power cable. Check the GPS receiver status.

3. INSTRUCTIONS : 1. the reason for the alarm is a faulty WSM/WMC or WSP. If that does not help. Replace the faulty unit. check the WTR and WSM cable. FlexiBTS: 1. 2. If that does not help. FAULT NAME DESCRIPTION : SFN Signal error : The system frame number receiving a fault. an illegal SFN value in uplink. If there are no active WSM/WMC alarms. replace the alarming unit. If only one FSP in the BTS generates this alarm. 3. Check the cabling between the System Module and RF Module. the FSP is faulty. Triple-mode: The WSP is not synchronised with the WAM. Run a WCDMA BTS loop test to locate the faulty unit.7651 BASE STATION OPERATION DEGRADED FSP and FCM. Replace the faulty module (System Module). block/unblock it. MetroSite. 4. INSTRUCTIONS : 1. 3. Block/unblock the alarming unit. Check the active RF Module alarms and act accordingly. If the WSP is faulty. the FSM is faulty. FAULT NAME : Self test failed DESCRIPTION : The self test of the unit/module has failed. Block/unblock the FSM. If that does not help. replace the faulty module (System Module). 2. FAULT NAME DESCRIPTION : SFN synchronization failure : UltraSite. 2. FAULT NAME DN99580892 Issue 6-3 en 12/06/2008 : SFN synchronization failure # Nokia Siemens Networks 101 (244) . FlexiBTS: The FSP is not synchronised with the FCM. replace the alarming unit/module. 5. Block/unblock the alarming unit/module. Triple-mode: 1. MetroSite 50. If all FSPs generate this alarm. INSTRUCTIONS : UltraSite. INSTRUCTIONS : 1. 4. 2. If the WSM/WMC also generates an alarm from a WTR unit. MetroSite 50. 2. MetroSite.

Check and correct the ATM configuration. FAULT NAME : Synchronization failure in Optical Interface <opt link/RP3 link> DESCRIPTION : The RP3 channel has achieved the frame synchronisation state and then lost it. Check the other active alarms. 2. 4. FAULT NAME DESCRIPTION : Synchronisation error in RP1 receiver : The frame alignment is lost or the frame burst has a CRC error when the System Module is working in extension mode. INSTRUCTIONS : 1. 102 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . FAULT NAME DESCRIPTION : SRAM operation failure : The SRAM memory operation failure. If the alarming link remains the same. Replace the alarming module. replace the System Module. 2. Block/unblock the FSM. The FSM has already found the frame synchronisation but the FSM frame clock does not match to the FSM internal frame clock. Reset the Extension System Module. Check the other active synchronisation alarms and follow the instructions of them. INSTRUCTIONS : Swap the alarming and working links. INSTRUCTIONS : 1.Base Station Alarms (7000-7999) DESCRIPTION : WAM internal synchronisation failure. 2. 2. INSTRUCTIONS : 1. 2. replace the alarming unit. 3. replace the RF Module behind that link. Replace the WAM. FAULT NAME DESCRIPTION : Synchronization failure : The frame burst phase has moved compared to the internal counter. If all FSPs generate this alarm. If that does not help. the SRAM chip may be broken. the FSM is faulty. INSTRUCTIONS : 1. replace the faulty module (System Module). FAULT NAME : SFN synchronization failure DESCRIPTION : The slave WAM is not synchronised with the master WAM. INSTRUCTIONS : 1. Then check where the alarm is now reported. the FSP is faulty. If only one FSP in the BTS generates this alarm. If the alarming link changes. If this alarm appears continuously. If that does not help. Block/unblock the alarming unit.

This ensures that nothing unexpected has happened in the unit start-up phase. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : Tbus receiver parity fault : Data or synchronisation failure in the System Module. 2. If all FSPs generate this alarm. replace the faulty module (System DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 103 (244) . If all FSPs generate this alarm. If only one FSP in the BTS generates this alarm. because of the transceiver circuit in the WCI. 2. FAULT NAME DESCRIPTION : System frame clock signal missing : The WAM does not receive a system frame clock (SFCLK) from the WCI/WMC. the FSP/FSM reset recovery. INSTRUCTIONS : 1. replace the module. the FSP is faulty. two antenna carriers are affected. Reset the System Module. 4. or the system frame clock bus is faulty. If there are no optical interface alarms. INSTRUCTIONS : 1. replace the alarming unit (WAM). If that does not help. If that does not help. FAULT NAME DESCRIPTION : System Module failure : The FlexiBTS has detected an abnormal operation or a failure in the System Module internal functionality. 2. 3. follow the instructions for those alarms. two antenna carriers are affected. 2. If there are. INSTRUCTIONS : 1. the FSM is faulty. If only one FSP in the cabinet generates this alarm. replace the faulty unit (System Module). Restart the faulty unit.7651 BASE STATION OPERATION DEGRADED FAULT NAME : System clock for extension system module not available DESCRIPTION : Extension system module does not receive the system clock. Block/unblock the FSM. 4. 2. replace the System Module. 3. FAULT NAME DESCRIPTION : Tbus receiver parity fault : Data or synchronisation failure in the System Module. INSTRUCTIONS : 1. the receiver circuit in the WAM. If that does not help. Block/unblock the alarming unit (WAM). the FSM is faulty. If the reset does not help the fault situation. Connect to the Extension System Module with BTS Site Manager to check if there are optical interface alarms. the FSP is faulty. 3.

the unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. FAULT NAME DESCRIPTION 104 (244) : Transmission clock missing : The clock of the BTS. the module needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. MetroSite 50.Base Station Alarms (7000-7999) Module). The signal is routed through the AXC and WCI to the WSC. FlexiBTS: A unit RNW configuration failure. A unit RNW configuration failure. INSTRUCTIONS : Recommission the site. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. A unit RNW configuration failure. INSTRUCTIONS : UltraSite. FlexiBTS: A FSP unit to FCM allocation failure. the WSC/WMC unit. MetroSite. FlexiBTS: In case of a FR. A telecom RNW reconfiguration failure. FAULT NAME DESCRIPTION : Telecom configuration failure : UltraSite. Or UltraSite. MetroSite50. Or a WSP unit to WAM allocation failure. This alarm is generated if the WCI does not receive the clock # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Triple-mode: Block/unblock the alarming unit. MetroSite. FAULT NAME DESCRIPTION : Telecom configuration failure : A telecom slave configurations or registrations failure. MetroSite. MetroSite 50. Triple-mode: A WSP unit to WAM allocation failure. MetroSite50. MetroSite. INSTRUCTIONS : UltraSite. FlexiBTS: In case of a FR. uses the Iub or the signal received from an external clock as a clock reference. FAULT NAME : Timeout. A telecom RNW reconfiguration failure. commissioned resource not ready DESCRIPTION : The faulty unit has not been configured or initialised. Triple-mode: Block/unblock the alarming unit. A telecom RNW reconfiguration failure. Triple-mode: A telecom slave configurations or registrations failure.

the FSM is faulty. FAULT NAME DESCRIPTION : TRANSU synchronization error : The RP3 Tx/Rx state machine or the Tbus receiver has changed its state. INSTRUCTIONS : 1. 3. If only one FSP in the BTS generates this alarm.7651 BASE STATION OPERATION DEGRADED reference signal. 2. If that does not help. Check the AXC settings. replace the faulty module (System Module). 2. Or the Tbus receiver has not synchronised. Check the transmission cablings. INSTRUCTIONS : To cancel the alarm. 4. If all FSPs generate this alarm. unblock the unit/module. MetroSite. INSTRUCTIONS : UltraSite. or transmission parameters have not been commissioned or properly set. FAULT NAME DESCRIPTION : Transmission parameters missing : A request to retrieve the public IP address information of the FCM from the FT fails. Check the Iub connection. Triple-mode: DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 105 (244) . the FSP is faulty. for example link breaks. 2. Replace the WCI unit. 3. FAULT NAME DESCRIPTION : Unit blocked : A unit/module is blocked with the BTS Site Manager. INSTRUCTIONS : 1. INSTRUCTIONS : Commission the transmission with the correct parameters. Check the connection between the FT and FSM. FAULT NAME : Unit initialization failure DESCRIPTION : A unit or an IP address initialisation has failed. Block/unblock the FSM. 3. The synchronisation is lost. Check the other transmission-related alarms. FAULT NAME DESCRIPTION : Transmission clock missing : The reference clock monitoring has detected a loss of signal in the reference received from the FT. either with a commissioning file or manually. 4. INSTRUCTIONS : 1. MetroSite50. The purpose of the fault is to avoid alarms that may rise during the unit/module maintenance task. Check the FT status.

this alarm causes the alarm. perform a power-off reset. replace the alarming module. If so. 2. If Step 2 does not help. If that does not help. replace the alarming unit. FCM: Reset the BTS. 2. If step 3 does not help.Base Station Alarms (7000-7999) 1. Check the alarm history to know why the WAMs' switchover occurred. replace the alarming unit. 2. check the RNC IP address in the commissioning file and modify the file if needed. 4. INSTRUCTIONS : 1. If Step 2 does not help. check the RNC IP address in the commissioning file and modify the file if needed. Reset the BTS. If that does not help. Block/unblock the alarming unit. INSTRUCTIONS : Replace the unit or upgrade the BTS SW. FAULT NAME : Unit initialization failure DESCRIPTION : Connection to the WSP fails due to a WSP internal failure. Block/unblock the alarming unit. Block/unblock the alarming unit. FlexiBTS: 1. FAULT NAME : Unit SW download failed DESCRIPTION : The software update to the unit or subunit has failed. Replace the alarming unit. Check if the non-commissioned WAM is the Master WAM. 2. 2. INSTRUCTIONS : 1. If the WAM is the alarm source. or 106 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 3. FAULT NAME DESCRIPTION : Unit not supported by current BTS SW version : An unsupported unit was found in the BTS. INSTRUCTIONS : 1. If that does not help. FAULT NAME : Unit SW download failed DESCRIPTION : The software update to the unit or subunit has failed. If the FCM is the alarm source. perform a power-off reset. 3. If Step 1 does not help. 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. 3. Download the BTS SW again. replace the alarming unit. replace the alarming unit.

FAULT NAME : Unit synchronization failed DESCRIPTION : The WAM/WSPC synchronisation has failed. Block/unblock the WSP. FAULT NAME DESCRIPTION : Unknown Cabinet Type : The cabinet cannot be identified by its product code (or object ID). INSTRUCTIONS : Replace the alarming module. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 107 (244) . INSTRUCTIONS : Check the WID connection and replace the WID. MetroSite. replace the alarming module. FlexiBTS: 1. The problem is probably in the WID id. FAULT NAME DESCRIPTION : Unknown HW resource : A unit cannot be identified by its product code or by its physical device address (object ID). or 1. Download the BTS SW again. 2. if necessary. FAULT NAME : Unit SW download failed DESCRIPTION : The software update to the unit or subunit has failed. INSTRUCTIONS : UltraSite. INSTRUCTIONS : Replace the alarming unit/module. If Step 2 does not help. If Step 1 does not help. WPA: Reset the BTS. Triple-mode: 1. MetroSite 50.7651 BASE STATION OPERATION DEGRADED 1. 2. Block/unblock the alarming unit. 2. Replace the alarming unit. FCM: Reset the BTS. 2. If Step 1 does not help. INSTRUCTIONS : 1. Download the BTS SW again. replace the alarming unit. WAM. replace the alarming unit. 3. FAULT NAME DESCRIPTION : Unknown product code : A module cannot be identified by its product code but is known by its physical device address (object_ID). or 1. Download the BTS SW again.

If all FSPs generate this alarm. INSTRUCTIONS : 1.There is an equipment fault in the BTS. The cause of the alarm can be: .Base Station Alarms (7000-7999) FAULT NAME : Uplink data buffer synchronization failure DESCRIPTION : The uplink data buffer loses the synchronisation. If the reference signal is incorrect during the fast tuning execution. 2. If that does not help. . the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' may have been active. Block/unblock the alarming unit.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).Due to the oven oscillator (OCXO) aging inside the WSC unit. replace the alarming unit. the alarm situation may be caused by a fault in that signal. Before activating this alarm. . FAULT NAME DESCRIPTION : WMC oven oscillator fault : The oven oscillator adjusting area is reaching its limit value. replace the faulty module (System Module). 4. the unit may be approaching the end of its lifetime. If that does not help. the FSM is faulty. the BTS will be restarted.If the BTS integrated transport part receives the synchronisation information via the 2. .The fast tuning action of the BTS master clock may have been executed without checking if the reference signal is correct or not. INSTRUCTIONS : 1. In that case the alarm behaviour notifications listed with the Iub signal (see above) are also valid in this case. The range for the DAC word is 0 . it may result in adjusting the BTS master clock frequency far from the nominal value. 3.4095. Block/unblock the FSM. Note: After the WAM block/unblock. which causes serious problems in the network performance. 2. FAULT NAME : WAM SFN polling timeout DESCRIPTION : The slave WAM is not synchronised with the master WAM.048 MHz synchronisation input (external clock source). . If only one FSP in the BTS generates this alarm. the FSP is faulty. 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). In such 108 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

015 ppm or better. the accuracy requirement of which is set by 3GPP. whereas in the other fault cases it may be very unstable or at the edge of the adjustment area (0 or 4095). Background information: The principle is that in a mobile network. The tuning may be done: . the location may be: a. . After the fault situation has been cleared. INSTRUCTIONS : 1. In case of a BTS equipment fault. however. 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). after the alarm activation. the BTS master clock may also require tuning.If there are no alarms.7651 BASE STATION OPERATION DEGRADED case.Manually.If that does not help. the synchronisation goes from MSC => RNC => BTS. WMC unit . But in reality that chain might be broken somewhere and.If there is no cure in a few minutes. by changing the DAC word (during a site visit).First check the alarms of the AXC node with the AXC Manager and act accordingly. Otherwise the BTS frequency may be tuned into a totally incorrect value. . because the BTS master clock adjustment is quite slow. 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. The BTS uses the incoming synchronisation signal as a reference for the Air interface. .Or with fast tuning. Note.If both the Iub reference signal accuracy and the AXC node are in order but the WMC unit is still alarming. for example. . reset the site. replace the WMC unit. In case of a fault in the transmission network synchronisation. 3. check the AXC synchronisation settings. This does not harm the system if also the synchronisation of the leased line service provider is accurate/stable enough. 2. b. causing serious problems in the network performance. that the fast tuning should only be used in case the Iub reference signal is known to be a good one. when using leased lines. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 109 (244) . run the fast tuning procedure with the BTS Site Manager. The long-term accuracy of the Iub signal must be 0. the network synchronisation must be corrected. the BTS may take the reference synchronisation from the transmission network of another operator. Transport part . the DAC value is quite stable.

4095. The range for the DAC word is 0 . The signal is routed through the AXC and WCI to the WSC.048 MHz synchronisation input (external clock source). which causes serious problems in the network performance. . the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' may have been active. the alarm situation may be caused by a fault in that signal. the unit may be approaching the end of its lifetime. for example link breaks. If the reference signal is incorrect during the fast tuning execution. This alarm is generated if the WCI does not receive the clock reference signal. after the alarm activation. whereas in the other fault cases it may be very unstable or at the edge of the adjustment area (0 or 4095).If the BTS integrated transport part receives the synchronisation information via the 2. The cause of the alarm can be: . Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WSC oven oscillator fault' becomes active. 4.Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : WSC/WMC transmission clock missing : The clock of the BTS. Check the other transmission-related alarms. it may result in adjusting the BTS master clock frequency far from the nominal value. 2. Check the transmission cablings. In such case.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).The fast tuning action of the BTS master clock may have been executed without checking if the reference signal is correct or not. uses the Iub or the signal received from an external clock as a clock reference. FAULT NAME DESCRIPTION : WSC oven oscillator fault : The oven oscillator adjusting area is reaching its limit value. In that case the alarm behavior notifications listed with the Iub signal (see above) are also valid in this case. the DAC value is quite stable. 3. 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). . Replace the WCI unit. . Check the AXC settings. it may cause the 110 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Before activating this alarm.There is an equipment fault in the BTS. . the WSC/WMC unit. INSTRUCTIONS : 1.Due to the oven oscillator (OCXO) aging inside the WSC unit.

Otherwise the BTS frequency may be tuned into a totally incorrect value. causing serious problems in the network DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 111 (244) .If both the Iub reference signal accuracy and the AXC node are in order but the WSC unit is still alarming. Note: In case the BTS is equipped with two WSCs. when using leased lines. The BTS uses the incoming synchronisation signal as a reference for the Air interface. the redundant unit takes over the operation of the faulty unit. the location may be: 2. 2. check the AXC synchronisation settings. because the BTS master clock adjustment is quite slow.2 WSC unit . by changing the DAC word (during a site visit) . 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.If that does not help. 1. The long-term accuracy of the Iub signal must be ± 0. . . .Or with fast tuning.Manually. both the WSC units may start alarming sooner or later. for example. replace the WSC unit. In case of fault in the transmission network synchronisation. run the fast tuning procedure with the BTS Site Manager. the synchronisation goes from MSC => RNC => BTS. But if the fault situation is caused by an incorrect reference signal. the accuracy requirement of which is set by 3GPP. The tuning may be done: . 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.First check the alarms of the AXC node with the AXC Manager and act accordingly.If there is no cure in a few minutes. that the fast tuning should only be used in case the Iub reference signal is known to be a good one.If there are no alarms. however. reset the site.015 ppm or better. 2.1 Transport part . 3. the network synchronisation must be corrected. INSTRUCTIONS : Background information: The principle is that in a mobile network. the BTS master clock may also require tuning. But in reality that chain might be broken somewhere and. After the fault situation has been cleared.7651 BASE STATION OPERATION DEGRADED alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel. In case of BTS equipment fault.

Base Station Alarms (7000-7999) performance.If the basic accuracy of the Iub signal is in order but there is too much instability. But in reality that chain might be broken somewhere and. for example. Background information: The principle in the mobile network is that the synchronization goes from MSC => RNC => BTS. The BTS uses the incoming synchronization signal as a reference for the Air interface. Block/unblock the alarming WSM. 3. when using leased lines the BTS may take the reference synchronization from the transmission network of another operator. the synchronization of the transmission network must be corrected. replace the unit. INSTRUCTIONS : 1. Check the backplane cables and connectors. replace the unit. This does not harm the system if also the synchronization of the leased line service provider is accurate/stable enough. Reset the site and wait about 10 minutes. If the alarm reappears during the next few weeks or the clock seems unstable. The problem can be caused by a WSC fault. or a too fast frequency change on the Iub. If the alarm reappears. FAULT NAME DESCRIPTION : WSC phase difference jammed to zero reading : The WSC phase measurement is jammed and the tuning operation is degraded. 2. FAULT NAME DESCRIPTION : WSMB SR-Bus error : UltraSite: The RX signal is transported from the WTR unit to all WSP units via the WSMs. the jitter/wander is outside the acceptable limits. Replace the WCI unit and check whether the alarm is cleared. 3. 2. No actions on the BTS are needed. This fault may appear if the only clock unit (WSC) is removed. The limits for the jitter/wander are defined in the ITU-T G. Try a power-on reset. that is. The WSM units in different subracks are 112 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . FAULT NAME DESCRIPTION : WSMB doesn't receive frame clock : The WSMB does not receive the System Frame Clock (SFCLK) correctly from the WCI unit. Note! This will cause a BTS reset.823. the accuracy requirement of which is set by 3GPP. INSTRUCTIONS : 1.

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 probably the WSP or WSM unit. Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions). FAULT NAME DESCRIPTION : WSMB ST-Bus error : The TX signal is transported from the WSP unit to all WTR units via the WSMs. INSTRUCTIONS : 1. Check the WSM cables. when the WSM unit detects errors in the incoming SR bus from the adjacent WSM unit. Run the WCDMA BTS loop test. when the WSM detects errors in the incoming SR bus from the WTR unit. FAULT NAME DESCRIPTION : WSMB T-Bus error : The signal is transported from the WSP unit to the WTR unit via the WSM. This alarm is generated when the WSM unit detects errors in the incoming T bus from the WSP unit. INSTRUCTIONS : 1. This alarm is generated. or the cable between the WSM front panel and the backplane. 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. The WSM units in different subracks are connected to each other via the ST buses. Run the WCDMA BTS loop test. Run the WCDMA BTS loop test. Check the WSM cables. The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm. This alarm is generated. INSTRUCTIONS : 1. 2. The reason for the failure is the WSM or WTR unit. 2. Check the WSM cables. 3. 3. Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions).7651 BASE STATION OPERATION DEGRADED connected to each other via the SR buses. 3. Replace the units indicated in the alarm one by one and DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 113 (244) . The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm. 2. The unit may have been installed incorrectly or the backplane cabling is faulty.

The system cancels the alarm automatically when the fault has been corrected. Some of the WSP/FSP DSP processors may be broken and out of use. 2.Base Station Alarms (7000-7999) check whether the problem is cleared (see Troubleshooting instructions). If that does not help. 114 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . FAULT NAME DESCRIPTION : WSP PCI-bus failure : There is a fault in the internal WSP/FSP PCI bus target (DSP) connections. Block/unblock the alarming unit. INSTRUCTIONS : Replace the alarming unit. FAULT NAME : WSP unit internal failure DESCRIPTION : The WAM and WSP are not synchronised. INSTRUCTIONS : 1. replace the alarming unit. Cancelling Do not cancel the alarm.

When an active alarm is a 'Start' alarm. If the site reset or unit/module block/unblock does not help. cabling and correct installation of the units/modules at the BTS. the site should be reset to recover from any temporary faults. replace the faulty unit/module (see source of the alarm and instructions fields of the corresponding alarm). contact the local Help Desk. Make sure the environment does not cause the fault. Instructions Verify the configuration of a BTS by checking the commissioning. Refer also to the individual alarm instructions. a site reset is required to cancel the alarm. Before a unit/module is replaced at the BTS. Check the reason for the fault from the supplementary text field of the alarm. which might have caused the misbehaviour of the unit/module. see instructions on Alarm Structure. If that does not help. Supplementary information fields 1 rack (cabinet) number 2 shelf number 3 slot 4 type of unit 5 unit number 6 subunit number For more information.7652 BASE STATION NOTIFICATION 30 7652 BASE STATION NOTIFICATION Meaning A minor fault (or faults) has occurred in the base station. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 115 (244) .

see Nokia WCDMA BTS Alarm Descriptions (SW and release document).Base Station Alarms (7000-7999) For more information. INSTRUCTIONS : Check the alarm history and other active alarms of the unit. The most common causes for this alarm are transmission network problems (causing unnecessary WAM changes). Note! This alarm does not require any (special) actions. AXC and RNC. RNC or BTS with the correct BTS A2EA addresses. the site or the BTS. or by the data corruption on the Iub (that is. FAULT NAME DESCRIPTION : ATM. 3. Check the data integrity from the incoming Iub (see Troubleshooting instructions). To make sure that the tuning is correct. Block/unblock the alarming unit. The cell loss can be caused by a traffic overload. by the WAM receiving an invalid ATM cell or AAL5 packet. A2EA configuration error : The RNC A2EA transport layer address does not comply with the given BTS A2EA address. 2. FAULT NAME DESCRIPTION : Active clock tuning fault : The phase measurement cannot be performed in the active WSC or WMC. If there is a WMC or only one WSC. Check that bandwidths (cells/s) are the same at the BTS. Note that because of a fault situation in the active clock. the redundant clock is not tuned. 2. INSTRUCTIONS : Check and re-commission the AXC (if AAL2 multiplexing is in use). Run fast tuning with the BTS Site Manager. INSTRUCTIONS : 1. INSTRUCTIONS : 1. This alarm is reported to the BTS Site Manager only. 3. run "Fast Tune BTS Clock" with the BTS Site Manager after switchover when the new WSC is taken into use. Check the other transmission elements' active alarms (see the Alarms for 116 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Replace the alarming unit. the tuning will continue but cells will remain disabled. FAULT NAME DESCRIPTION : ATM cell loss : ATM cells are lost. FAULT NAME DESCRIPTION : # autonomous reset as recovery action : The BTS tries to correct a fault situation by performing a recovery reset to a unit. a bad BER).

c. replace the alarming RF Module/Extension System Module. INSTRUCTIONS : 1. Reset the Extension System Module by blocking/unblocking it. 3. 2. The failure cannot be pointed to a specific module but there are several possible fault sources. FAULT NAME : Cabinet door open DESCRIPTION : The cabinet door is open or the cabinet door sensor is faulty. 4. Reset the RF Module and/or System Module. 4. INSTRUCTIONS : Reset the BTS. INSTRUCTIONS : 1. If the reset does not clear the fault situation. Check the WAM. Check the stratum parameter on the NTP server (value <14). FAULT NAME DESCRIPTION : BTS time not corrected : The SNTP time cannot be fetched from the transport system (FT) within the time limit. depending on the alarm source: a.7652 BASE STATION NOTIFICATION AXC document). Check that the door switches function correctly and that they have been adjusted correctly. replace the alarming master System Module. INSTRUCTIONS : Replace the WSC. FAULT NAME DESCRIPTION : Baseband reference clock missing (WSC) : The WSC is not able to deliver the clock signals required by the other units. Check the cables between the System Module and RF Module/Extension System Module. b. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation. FAULT NAME DESCRIPTION : Baseband Bus failure : The FlexiBTS has detected an abnormal operation or a failure in the BTS internal baseband bus. Ensure that the cabinet door (s) are properly closed. Check the NTP setting. 2. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 117 (244) . INSTRUCTIONS : 1. Reset the RF Module by blocking/unblocking it. 5. AXU and the cabling between them. FAULT NAME DESCRIPTION : BTS reset needed to activate a licence : The status of a licence has changed to valid and a BTS reset is needed to take the licence into use. Check the other active BTS alarms and act accordingly. 2. Reset the master System Module.

2.2 ppm. FAULT NAME DESCRIPTION : Difference between BTS master clock and reference frequency : The reference frequency that the BTS master clock receives from the transport part has changed by about 0. compared to the BTS master clock frequency. Note that if the network synchronisation malfunction lasts a long time. FAULT NAME DESCRIPTION : Configuration error: <x> : There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. INSTRUCTIONS : 1. Check that the BTS cell parameters from the RNC match the BTS HW configuration (for example frequency. If that does not help. 3. power). replace the faulty fan assembly. The alarm is cancelled whenever the difference becomes smaller than 0. Recommission the BTS to ensure that all parameters are correctly configured.2 ppm or more.2 ppm or more (which equals the change magnitude of 204 DAC steps or more) during the measurement period (about 20 minutes). INSTRUCTIONS : 1. the alarm is cancelled when the BTS frequency reaches the faulty Iub synchronisation. Another possibility is that there is a mismatch between the BTS configuration and the RNC parameters. The cause of the alarm can be: 1. 4. Check the RNC alarms for the alarming local cell (LCR). 2. 2. The 118 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 3. block/unblock the RF Module. The Iub reference frequency has changed due to a fault in the transmission network synchronisation (which in turn is caused by an equipment fault or a setting error). The Iub reference frequency fluctuates continuously due to a great deal of jitter/wander in the transmission network. INSTRUCTIONS : Check the signalling link settings and the RNC connections. The alarm can also be activated if the faulty Iub synchronisation is corrected and there is again the difference of 0. If that does not help.Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : Communication Failure with RNC : The BTS does not receive a response from the RNC (a block request). FAULT NAME DESCRIPTION : Cooling fan out of order : The RF Module cooling fan is not rotating at the specified speed. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration. Check the fan.

If the BTS integrated transport part receives the synchronisation information via the 2. Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WSC oven oscillator fault' becomes active. There is an equipment fault in the BTS. the network synchronisation must be corrected. No actions on the BTS are necessarily needed. 3. The history data can be used as a tool for finding out the reason for the fault/alarm situation (for further instructions about the history feature. The limits for the jitter/wander are defined in the ITU-T G.7652 BASE STATION NOTIFICATION alarm is continuously activated/cancelled (however. a BTS Clock Frequency History feature has been developed. Normally the reason can be found in the Iub/reference signal behaviour (see the descriptions above). 3. the jitter/wander is outside the acceptable limits. the synchronisation of the transmission network must be corrected. 4. If the basic accuracy of the Iub signal is in order but there is too much instability. see the online Help of the BTS Site Manager). The equipment fault is. the alarm situation may be caused by a fault of that signal. the alarming state may predominate). it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel. In case of BTS equipment fault. 2. No actions on the BTS are needed. There is always some jitter/wander in the transmission network.If there are no alarms.048 MHz synchronisation input (external clock source). follow the instructions below: 1. In case of fault in the transmission network synchronisation. not the most common reason. FCM unit .015 ppm or better (check the correct Iub accuracy by measuring it). check the AXC/FTM synchronisation settings. run the fast tuning DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 119 (244) . . the location may be: Transport part . Depending on the possible reason. INSTRUCTIONS : Because there are several possibilities for the alarm activation. that is. The stored history data can be accessed via the BTS Site Manager.First check the alarms of the AXC node with the AXC Manager.823/824/825. however. the alarm behaviour notifications listed with the Iub signal (see above) are also valid in this case. The long-term accuracy of the Iub signal must be 0. or FTM and act accordingly.If both the Iub reference signal accuracy and the FTM are in order but the WFCM unit is still alarming.823/824/825. the limits are defined in ITU-T G. In that case.

replace the FCM unit.If that does not help. 3. After the fault situation has been cleared. or the user does not have access rights for the files). for example. INSTRUCTIONS : 1. Otherwise the BTS frequency may be tuned into a totally incorrect value. or the path is incorrect. Note that if the reason is in the transmission network synchronisation.manually by changing the DAC word (during a site visit) . FAULT NAME DESCRIPTION : Error in file server during SW download : The BTS is unable to obtain a file from the file server (error in FTP open or FTP get).If the alarm is still active after the fast tuning is finished. Check the FTP account user settings. not to a fault in the unit. FAULT NAME DESCRIPTION 120 (244) : Failure in optical RP3 interface : The FlexiBTS has detected an abnormal operation or a failure # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . the BTS master clock may also require tuning because the BTS master clock adjustment is quite slow. or a user administration error (an invalid username or password. Check the file and path names. the BTS may take the reference synchronisation from the transmission network of another operator. Retry the SW update few times. The BTS uses the incoming synchronisation signal as a reference for the Air interface. causing serious problems in the network performance. reset the site. If the problem does not disappear in a few minutes. reset the site. Check the administration log on the file server. the accuracy requirement of which is set by 3GPP. Note. But in reality that chain might be broken somewhere and. the file is missing. the synchronisation goes from MSC => RNC => BTS. however. that the fast tuning should only be used in case the Iub reference signal is known as a good one. . 2. 4. Background information: The principle is that in the mobile network.or with fast tuning. the alarm activity (frequent alarms/cancels) points to instability in the transmission network. The tuning may be done: . 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). The file server is down. A possible error in the DCN and Iub.Base Station Alarms (7000-7999) with the BTS Site Manager. 4. when using leased lines. This does not harm the system if the synchronisation of the leased line service provider is also accurate/stabile enough. . replacing the faulty unit does not correct the situation. Furthermore.

If the reset does not clear the fault situation. Triple-mode: All the fans or more than one fan in the same fan group (WFA. Extension System Module and/or System Module by blocking/unblocking it. The reason for this fault can be too low supply voltage or a broken fan control board. Check the fan and cabling. WTR. replace the faulty fan module. Triple-mode: 1. WHX) are rotating slower than requested. MetroSite. INSTRUCTIONS : 1. replace the alarming RF Module/Extension System Module. INSTRUCTIONS : UltraSite. 4. Please notice that dirty optical connectors may cause the signal level to drop too low. 2. Check also the SFP in the other end and replace it if needed. MetroSite 50. 3. replace the alarming System Module. Check the Fan ID from the Alarm message and locate the DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 121 (244) . WFD or WHX fan control module also controls the fans in the RF section (same sector). If that does not help. MetroSite.7652 BASE STATION NOTIFICATION in an optical RP3 interface between two modules. 6. 5. FlexiBTS: All the fans or more than one fan in the same fan group are rotating slower than requested. reset the RF Module. Depending on the alarm source. and the LED of the unit is stable red although it is working correctly. If that does not clear the fault situation. FAULT NAME DESCRIPTION : Fan failure : All the fans or more than one fan in the same fan group are rotating slower than requested. Check the cables between the System Module and RF Module/Extension System Module. Check the other active BTS alarms and act accordingly. INSTRUCTIONS : 1. The failure cannot be pointed to a specific module but there are several possible fault sources. are not rotating at all. replace the alarming Modules Small Form Factor Pluggable (SFP). The reason for this fault can be too low supply voltage or a broken fan. 2. WPA/WMP. or the RPM info is not available for the fans. The WFA. WFD or WHX. FAULT NAME DESCRIPTION : Fan module faulty : UltraSite. are not rotating at all. A failure in the RF section fans is reported from that WFA. MetroSite 50. or the RPM information is not available for the fans. If the System Module is the only alarming source or replacing the RF Module/Extension System Module does not clear the fault situation.

FAULT NAME DESCRIPTION : Fan module operation degraded : A fan does not rotate or rotates slower than at the requested speed. Replace the alarming module. If that does not help. 3. 122 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . See the Fan mapping figures in the Alarms and Troubleshooting document. Check whether the heating element exists at all. replace the WFA. 2. Check the fan and cabling. Fan control: 'FAN UNIT' refers to a group of fans including the fan control unit. or the RPM info is not available for the fan. 3. Check the fan ID from the alarm message and locate the problematic fan. Check the fan and cabling. A 'fan' is a single blower. A 'fan' is a single blower. there is no heater or the heater is faulty. Fetch BTS log files and check the download status from the BTS SWDLreport. A 'fan' is a single blower. Retry the SW update. If that does not help. Fan control: 'FAN UNIT' refers to a group of fans including the fan control unit. Check the heater control connection and that the heater is working. Check the fan and cabling. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : Heating element not working : The heater control connection of the FSM is faulty. 2. replace the WFA. FAULT NAME : File corrupted in SW download DESCRIPTION : The SW being downloaded is corrupted or incorrectly formed. WFD or MFU. See the Fan mapping figures in the Alarms and Troubleshooting document. WFD or MFU module or the fan controlled by the WFA. INSTRUCTIONS : 1. Check the Fan ID from the Alarm message and locate the problematic fan. 2. 2. 2. INSTRUCTIONS : 1. WFD or MFU module or the fan controlled by the WFA. WFD or MFU. 3. FlexiBTS: 1. Fan control: 'FAN UNIT' refers to a group of fans including the fan control unit.Base Station Alarms (7000-7999) problematic fan. See the Fan mapping figures in the Alarms and Troubleshooting document.

Triple-mode: 1. and update the active SW version). FAULT NAME DESCRIPTION : Mast Head Amplifier fault : The FlexiBTS has detected an abnormal operation or a failure in the Mast Head Amplifier (MHA). Triple-mode. Metrosite 50: Check the SW version of the BTS and AXC. Related BTS . If the reset does not clear the fault situation. Reset the alarming MHA module by blocking/unblocking the RF Module which the MHA is connected to. and update compatible SW to the AXC or BTS. Check the alarm history.AXC interface: check the SW version of the BTS and AXC. INSTRUCTIONS : 1. replace the faulty device (s). unless it is automatically updated by the NetAct. FAULT NAME DESCRIPTION : No connection to unit : The connection to a unit that belongs to the BTS configuration has been lost. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 123 (244) . The fault reduces the gain performance or completely prevents the function of the MHA. 3. and update compatible SW to the AXC or BTS. FAULT NAME DESCRIPTION : Incompatible SW version detected : A new unit/module with an incompatible SW has probably been inserted in the BTS. 2. Replace the alarming component. Note that the Tower Mounted Amplifier (TMA) is a synonym for the MHA and is used by the Antenna Interface Standards Group (AISG).7652 BASE STATION NOTIFICATION 3. FAULT NAME DESCRIPTION : MHA unit operation failure : A fault in the TMA is detected. alarming unit and subrack. INSTRUCTIONS : Replace the alarming module. MetroSite. INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version. INSTRUCTIONS : UltraSite. and update the active SW version). UltraSite. MetroSite 50. Check the cables related to the Mast Head Amplifier (MHA). FAULT NAME DESCRIPTION : Incompatible SW version detected : A new unit with an incompatible SW has probably been inserted in the BTS. unless it is automatically updated by the NetAct. Metrosite. INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version.

or re-commission the 124 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . If SW updates have been done recently. If the 7650 BASE STATION FAULTY alarm is issued. no data is discarded yet. If that does not help. 3. The fault may also be in the WPS unit or backplane. INSTRUCTIONS : Check that the ATM configurations in the BTS. First try to reset the site by the software. Check the WEA and cabling. Check the alarming unit. If there are not enough resources. FAULT NAME DESCRIPTION : Non fatal ATM traffic overload : Traffic load is approaching the maximum capacity. Check the alarm history. 2. FAULT NAME : No connection to WEA and unable to detect External alarms DESCRIPTION : The WEA unit is missing from the BTS or it cannot be detected. MetroSite. See Troubleshooting instructions for how to check units behind the same bus. However. INSTRUCTIONS : UltraSite. WSM or primary WAM causes a site reset. replace the alarming unit. replace the alarming unit. AXC and RNC match. the unit is faulty. Check that the unit is properly connected. If both WSCs are removed. 5. FAULT NAME DESCRIPTION : Not enough resources for comissioned HSUPA : There are not enough resources for the HSUPA minimum capacity based on the commissioned parameters "Minimum Baseband Decoding Capacity" and "Minimum HSUPA Users". 2. If the WAF or WIC is alarming. Cancel alarms: Removing and inserting the WIC. Check the power cables and connectors as well as the I2C bus cables. add the required number of WSP units or replace the broken ones. reset the site. If the unit led does not light up. try recommissioning the site. MetroSite 50. Triple-mode: 1.Base Station Alarms (7000-7999) 2. inserting the first removed WSC back into the cabinet causes a site reset. INSTRUCTIONS : 1. 4. If that does not help. the unit is faulty. Check that the unit is properly connected. Check from the configuration that there are enough resources for the minimum HSUPA capacity. 2. If the unit led does not light up. reload the SW. FlexiBTS: 1.

Check the active fan alarms. FlexiBTS: 1. INSTRUCTIONS : 1. INSTRUCTIONS : Replace the clock unit. 2. make sure the airflow to the BTS modules is unobstructed. Check the other BTS alarms and act accordingly.7652 BASE STATION NOTIFICATION BTS and pre-reserve less capacity for the HSUPA. FAULT NAME DESCRIPTION : Temperature alarm : The RF Module or System Module internal temperature exceeds the threshold value. that is. Check the root cause. the BTS modules are not DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 125 (244) . The ambient temperature can also be too low or change too fast. If there are not enough resources. FAULT NAME DESCRIPTION : Oven oscillator heating failure : The heating of oven oscillator fails and the unit is broken. INSTRUCTIONS : 1. If the alarm was false. If the ambient temperature is too high. Reset the BTS to get the minimum capacity preselection for the HSUPA in use. FAULT NAME : Smoke alarm DESCRIPTION : The internal smoke detector has detected smoke in the cabinet. 2. Check from the configuration that there are enough resources for minimum HSUPA capacity. FAULT NAME DESCRIPTION : OIC MCU Buffer Full : The control message traffic is malfunctioning between the modules. 3. or the ambient temperature of the module (s) is outside the specified limits. Check the ambient temperature of the BTS/modules. replace the alarming smoke detector. INSTRUCTIONS : 1. INSTRUCTIONS : Check the RF Module alarms. Reset the BTS to get the minimum capacity preselection for the HSUPA in use. replace the broken module or re-commission the BTS and pre-reserve less capacity for HSUPA. 3. 2. FAULT NAME DESCRIPTION : Oven oscillator clock missing : The WSC is not able to deliver the clock signals required by the other units. 2. Replace the clock unit.

INSTRUCTIONS : Check the active fan alarms.after acknowledgement the fault will return again. FAULT NAME DESCRIPTION : Unit not supported by current BTS SW version : An unsupported unit was found in the BTS. If the ambient temperature is too low. If the reset does not clear the fault situation. 3. 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. but no Radio Module is connected to it.Base Station Alarms (7000-7999) covered with anything. Block/unblock the active WSC unit. Replace both WSC units. FAULT NAME : Unit temperature is high DESCRIPTION : The temperature of a unit exceeds the threshold value. replace the alarming module.appears once when unsynchronised data is sent by the BB. INSTRUCTIONS : 1. Data corruption on the bus . 4. it takes a while for the BTS/modules to heat themselves to the threshold value. INSTRUCTIONS : Check the baseband bus configuration parameters from the commissioning file. INSTRUCTIONS : Add Radio Modules to the System Module if it is intended to be the master System Module. FAULT NAME DESCRIPTION : WCI baseband reference clock failure : 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. FAULT NAME DESCRIPTION : Waiting for RF connections : The module has been configured as a master System Module. FAULT NAME DESCRIPTION 126 (244) : WEA power regulator fault : The WEA unit external interface connectors are connected incorrectly. Replace the WCI unit. INSTRUCTIONS : Replace the unit or upgrade the BTS SW. Reset the alarming module by blocking/unblocking it. Configuration error (2 different FSPs functioning) . # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 2. or there is a shot circuit in the +5 VCD. and the airflow of the BTS. 3. FAULT NAME DESCRIPTION : Timestamp mismatch in summing : Timestamp mismatch in the BB summing.

If the BTS integrated transport part receives the synchronisation information via the 2.The voltage of one cell is not compatible with the other cell voltages.Some of the battery blocks (cells) reached an overcharge or a discharge voltage in a stand-by condition. If the alarm does not disappear. 2. 3. The cause of the alarm can be: .048 MHz synchronisation DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 127 (244) . Replace the WIB unit or battery. the temperature measured inside the unit is out of the normal temperature range. FAULT NAME DESCRIPTION : WIB unit battery failure : WIB unit battery failure: . 2.Several battery blocks (cells) are dead and the back-up system is out of order.4095. 2.7652 BASE STATION NOTIFICATION INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : WIB unit battery temperature out of range : Because the heater or the heater control unit does not work correctly. Check the battery cablings and cells' voltage levels. Check the battery temperature sensor. Before activating this alarm. check the WEA and replace it if it is faulty. Check the battery space's temperature. INSTRUCTIONS : 1. . the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' may have been active. Disconnect the external cables and check whether the alarm disappeares.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). The range for the DAC word is 0 . 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). . INSTRUCTIONS : 1. INSTRUCTIONS : Replace the WIB unit. Check the external cables and connections. . FAULT NAME DESCRIPTION : WSC oven oscillator fault : The oven oscillator adjusting area is reaching its limit value. FAULT NAME DESCRIPTION : WIB unit power back-up time alarm : The WIB cannot supply nominal power for 10 seconds and/or the estimated battery life is 26 weeks or less.

after the alarm activation. the alarm situation may be caused by a fault in that signal. The long-term accuracy of the Iub signal must be ± 0. . 128 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . the synchronisation goes from MSC => RNC => BTS. the accuracy requirement of which is set by 3GPP. the network synchronisation must be corrected. it may cause the alarm 7652 BASE STATION NOTIFICATION: 'Difference between BTS master clock and reference frequency' to cancel. In case of BTS equipment fault. .There is an equipment fault in the BTS. 1. whereas in the other fault cases it may be very unstable or at the edge of the adjustment area (0 or 4095). In such case. run the fast tuning procedure with the BTS Site Manager. the location may be: 2. . . it may result in adjusting the BTS master clock frequency far from the nominal value.Base Station Alarms (7000-7999) input (external clock source).The fast tuning action of the BTS master clock may have been executed without checking if the reference signal is correct or not. the BTS may take the reference synchronisation from the transmission network of another operator. 2. In case of fault in the transmission network synchronisation.If both the Iub reference signal accuracy and the AXC node are in order but the WSC unit is still alarming. Note that if the alarm 7651 BASE STATION OPERATION DEGRADED: 'WSC oven oscillator fault' becomes active. But in reality that chain might be broken somewhere and. This does not harm the system if also the synchronisation of the leased line service provider is accurate/stable enough.1 Transport part . INSTRUCTIONS : Background information: The principle is that in a mobile network.2 WSC unit . for example. when using leased lines. 2.015 ppm or better. which causes serious problems in the network performance. If the reference signal is incorrect during the fast tuning execution.First check the alarms of the AXC node with the AXC Manager and act accordingly. the DAC value is quite stable. check the AXC synchronisation settings.Due to the oven oscillator (OCXO) aging inside the WSC unit. The BTS uses the incoming synchronisation signal as a reference for the Air interface. In that case the alarm behavior notifications listed with the Iub signal (see above) are also valid in this case. the unit may be approaching the end of its lifetime.If there are no alarms.

But if the fault situation is caused by an incorrect reference signal. This does not harm the system if also the synchronization of the leased line service provider is accurate/stable enough. that is. Background information: The principle in the mobile network is that the synchronization goes from MSC => RNC => BTS. 3. the BTS master clock may also require tuning.7652 BASE STATION NOTIFICATION .Manually. The BTS uses the incoming synchronization signal as a reference for the Air interface. The problem can be caused by a WSC fault. 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. Note: In case the BTS is equipped with two WSCs. No actions on the BTS are needed. by changing the DAC word (during a site visit) .If the basic accuracy of the Iub signal is in order but there is too much instability. If the alarm reappears during the next few weeks or the clock seems unstable. both the WSC units may start alarming sooner or later. replace the unit. the accuracy requirement of which is set by 3GPP. INSTRUCTIONS : 1. The limits for the jitter/wander are defined in the ITU-T G. Try a power-on reset. when using leased lines the BTS may take the reference synchronization from the transmission network of another operator. FAULT NAME DESCRIPTION : WSC phase difference jammed to zero reading : The WSC phase measurement is jammed and the tuning operation is degraded. Reset the site and wait about 10 minutes. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 129 (244) . the redundant unit takes over the operation of the faulty unit.823. 3. 2. replace the WSC unit. . that the fast tuning should only be used in case the Iub reference signal is known to be a good one. the jitter/wander is outside the acceptable limits. for example. causing serious problems in the network performance. Otherwise the BTS frequency may be tuned into a totally incorrect value.If there is no cure in a few minutes. replace the unit. the synchronization of the transmission network must be corrected.Or with fast tuning. or a too fast frequency change on the Iub. however.If that does not help. because the BTS master clock adjustment is quite slow. reset the site. After the fault situation has been cleared. But in reality that chain might be broken somewhere and. If the alarm reappears. The tuning may be done: .

The reason for the failure is probably the WSP or WSM/WMC unit. Check the WSM cables. INSTRUCTIONS : 1. Cancelling Do not cancel the alarm. 3. Run the WCDMA BTS loop test. The system cancels the alarm automatically when the fault has been corrected. The WSM units in different subracks are connected to each other via the ST buses. INSTRUCTIONS : Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions). FAULT NAME DESCRIPTION : WSMA ST-Bus error : The TX signal is transported from the WSP unit to all WTR units via the WSMs. 2. Block/unblock the alarming unit. 2. Fast tune the active unit.Base Station Alarms (7000-7999) FAULT NAME : WSC switch unsuccessful DESCRIPTION : The WSC recovery switch over failed. 130 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . This alarm is generated when the WSM unit detects errors in the incoming ST bus from the adjacent WSM unit. This may cause a BTS reset. The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm. This alarm is generated when the WSM unit detects errors in the incoming T bus from the WSP unit. The unit may have been installed incorrectly or the backplane cabling is faulty. FAULT NAME DESCRIPTION : WSMA T-Bus error : The signal is transported from the WSP unit to the WTR unit via the WSM/WMC. INSTRUCTIONS : 1. Replace the units indicated in the alarm one by one and check whether the problem is cleared (see Troubleshooting instructions).

If the site reset or unit/module block/unblock does not help. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 131 (244) . which might have caused the misbehaviour of the unit/module. replace the faulty unit/module (see source of the alarm and instructions fields of the corresponding alarm). a site reset is required to cancel the alarm.7653 CELL FAULTY 31 7653 CELL FAULTY Meaning A critical fault (or faults) has occurred in a unit/module (or units/modules) that belong to the sector indicated in the alarm. Instructions Verify the configuration of a BTS by checking the commissioning. If that does not help. Supplementary information fields 1 rack (cabinet) number 2 shelf number 3 slot 4 type of unit 5 unit number 6 subunit number For more information. contact the local Help Desk. see instructions on Alarm Structure. Check the reason for the fault from the supplementary text field of the alarm. Refer also to the individual alarm instructions. Before a unit/module is replaced at the BTS. the site should be reset to recover from any temporary faults. Make sure the environment does not cause the fault. cabling and correct installation of the units/modules at the BTS. When an active alarm is a 'Start' alarm.

The antenna cable between the WAF and MHA is faulty or the antenna is faulty. 4. Use the ARIO Local Management Tool and the Nokia Advanced Indoor Radio user documentation to diagnose the error cause. FAULT NAME DESCRIPTION : Antenna1 connection fault : The BIAS-T has detected that the reflected TX power from the antenna has increased. Check the PITA cable connection (RJ45). 2. overcurrent. INSTRUCTIONS : 1. Make sure 132 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Check the antenna line and antenna line devices. 4. Make sure the antenna line connectors are in the right torque. If the reset does not clear the fault situation. INSTRUCTIONS : 1. Check by cross connecting RJ45 cables between other sectors. Some ARIO alarms can be cancelled without a reset but most ARIO alarms require the WOU block/unblock to cancel. Check the bias-T and MHA commissioning. replace the faulty parts and/or devices along the antenna line. 3. FAULT NAME DESCRIPTION : AIR fatal alarm : ARIO has detected a Fatal level alarm. Check the right connection (see User Manual). Check the voltage (see connector pins in Troubleshooting instructions). Replace the RF Module. Check the antenna line (see Troubleshooting instructions). FAULT NAME DESCRIPTION : Antenna Line failure : The RF Module has detected an abnormal operation or a failure in the antenna line. for example. a. The BIAS-T may be faulty. c. VSWR out of range. INSTRUCTIONS : 1. Block/unblock the WAF unit (check if the alarm reappears after 5 minutes). Check the antenna line and antenna line devices.Base Station Alarms (7000-7999) For more information. Reset the alarming RF module by block/unblock. b. 2. see Nokia WCDMA BTS Alarm Descriptions (SW and release document). INSTRUCTIONS : Check the WOU or WRUs. FAULT NAME DESCRIPTION : Antenna Line Device failure : The System Module or device itself has detected an abnormal operation or a failure in the antenna line device. 3.

3. INSTRUCTIONS : 1. INSTRUCTIONS : Replace the alarming module. INSTRUCTIONS : 1. Replace the alarming unit (the System Module). Reset the alarming RF module by block / unblock. FAULT NAME DESCRIPTION : BB bus reception error (MUKSU) : The master frame in the received BB frame is not in the correct place related to the internally generated master frame pulse. Either the frame has been set into the wrong place (PI delay) or the data itself is in the wrong place. b. Replace the RF Module. 4. 2. Reset the Extension System Module by blocking/unblocking it. If a reset does not clear the fault situation. DSP or LTX. 3. The failure cannot be pointed to a specific module but there are several possible fault sources. Reset the RF Module and/or System Module. 4. 2. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation. depending on the alarm source: a. INSTRUCTIONS : Check the unit frequency types in the cell and replace the DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 133 (244) . If the reset does not clear the fault situation. Check the other active BTS alarms and act accordingly. replace the faulty parts and/or devices along the antenna line.7653 CELL FAULTY the antenna line connectors are in the right torque. 5. Check the cables between the Master System Module and RF Module/Extension System Module. 2. replace the alarming RF Module/Extension System Module. Check the cables between the System Module and RF Module/Extension System Module. Reset the RF Module by blocking/unblocking it. FAULT NAME DESCRIPTION : BTS config error (All units in a cell must be of same freq) : A unit with an incompatible frequency type has been detected. All units in the cell must be of the same frequency type. Reset the master System Module. replace the alarming master System Module. FAULT NAME DESCRIPTION : Baseband Bus failure : The FlexiBTS has detected an abnormal operation or a failure in the BTS internal baseband bus. c. FAULT NAME DESCRIPTION : Baseband bus configuration of <x> was rejected : The baseband bus related configuration of <x> was rejected by the HW SW.

INSTRUCTIONS : Replace the 50 W WPAs with the 28 W WPAs. MetroSite. MetroSite 50. Triple-mode: A dual carrier WTR has been replaced with a single carrier WTR. MetroSite 50. FlexiBTS: Replace the single PA RF module with a dual PA RF module.The optical interface FPGA file is invalid or missing. Triple-mode: Replace the single carrier WTR with a dual carrier WTR. MetroSite50. FAULT NAME DESCRIPTION : BTS config error (WAF overload. FAULT NAME DESCRIPTION : BTS config error (WTR used as dual TRX behind WSMA) : A WTR/WSM conflict is detected. FlexiBTS: A dual PA RF module has been replaced with a single PA RF module. and it cannot serve both cells commissioned to the WTR. INSTRUCTIONS : Replace the incompatible unit or recommission the BTS (Reconfiguration commissioning) with only one TRX on. Or replace the WPAI and WPAJ with a WPAA/WPAB. FAULT NAME DESCRIPTION : BTS config error : A WPAI/WPAJ with combination with INSTRUCTIONS : Replace the WSMA (WPA / WSMA version conflict in cell) two carriers and a WOC were detected in the a WSMA. Triple-mode: 1. MetroSite. FAULT NAME DESCRIPTION : BTS config error (Not enough HW for LCR) : UltraSite. The incompatible WTR cannot operate with the WSMA when two TRXs are used.Base Station Alarms (7000-7999) incompatible unit with a compatible one.1 onwards: The FSP MCU SW file is invalid or missing. MetroSite.The BTS unit properties data is invalid or missing. . MetroSite. with a WSMB.WN4. Triple-mode: The BTS unit properties data is invalid or missing. 50W not in dualWPA config) : Two 50 W WPAs are coupled to one WAF. FlexiBTS: . Download two different SW packages so that the faulty file 134 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . and it cannot serve all cells commissioned to the RF module. INSTRUCTIONS : UltraSite. INSTRUCTIONS : UltraSite. MetroSite50. or one 50 W WPA and one 28 W WPA are coupled to one WAF. . FAULT NAME DESCRIPTION : BTS file error : UltraSite. Only two 28 W WPAs can be coupled together to one WAF unit.

Download two different SW packages so that the faulty file will be removed from the BTS. Download the SW again. Download the SW again. 3. replace the alarming unit. 3. Check the other active alarms. Download two different SW packages so that the faulty file will be removed from the BTS. unblock the cell. INSTRUCTIONS : UltraSite.The BTS unit properties data is invalid or missing. for example if the RNC has rejected the normal cell blocking during the Intelligent Shutdown. 2. FlexiBTS: 1. . 2. FlexiBTS: 1. FAULT NAME : Cell blocked DESCRIPTION : The cell is blocked with the BTS Site Manager. FlexiBTS: . Replace the system module. MetroSite. 3. Replace the FCM. 2. Triple-mode: 1. FAULT NAME DN99580892 Issue 6-3 en 12/06/2008 : Cell calibration failure # Nokia Siemens Networks 135 (244) .The optical interface FPGA file is invalid or missing. FAULT NAME DESCRIPTION : BTS file error : UltraSite. Download two different SW packages so that the faulty file will be removed from the BTS. FAULT NAME DESCRIPTION : Cell block rejected by RNC : The cell has been disabled due to BTS internal reasons. Check the mains power supply. INSTRUCTIONS : 1.7653 CELL FAULTY will be removed from the BTS. Triple-mode: The BTS unit properties data is invalid or missing. Download the SW again. Download the SW again. MetroSite 50. INSTRUCTIONS : To cancel the alarm. 2. 2. If the fault still exists after 10 minutes. If the fault still exists after 10 minutes. replace the alarming unit. MetroSite 50. MetroSite. 3.

INSTRUCTIONS : UltraSite. There is a fault in the downlink transmission path. Block/unblock the WPA/WMP. INSTRUCTIONS : 1. The module needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure or sticking in the module SW. INSTRUCTIONS : UltraSite. The fault may be in the WTR or WPA.) 4. Replace the faulty module. MetroSite50. Run the WCDMA BTS Loop Test with the BTS Site Manager to check the WSM cabling. 4. WPA. FAULT NAME DESCRIPTION : Cell power monitoring : The WPA/Radio output power has dropped. Check the RF TX cabling. Check the RF and WSM cabling (for example. Check the commissioning (LCR cabling). 2. 2. or a general initial calibration failure.Base Station Alarms (7000-7999) DESCRIPTION : TX power calibration failure: a CPICH setup failure. Check the RF module. 5. Block/unblock the alarming unit or the WPA connected to the alarming WTR. 3. WSMs or WSP. Block/unblock the WPA. 2. Replace the WTR. 3. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. There is a fault in the downlink transmission path. 136 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Block/unblock the WTR belonging to the same LCR. (Note! The Loop test cannot be run if the cell is already blocked because of an alarm. Triple-mode: 1. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. MetroSite 50. Triple-mode: 1. MetroSite. Block/unblock the RF module. a CPICH release failure. in case of an incorrect cabling). 3. The unit needs to be blocked/unblocked to reinitialise/reconfigure it if there was an internal failure. MetroSite. a WTR power out of range. FlexiBTS: 1. FAULT NAME DESCRIPTION : Cell power monitoring : The WPA/Radio output power has dropped. WOU.

Block/unblock the RF module. 4. 3. Check the cables between the System Module and RF Module/Extension System Module. Block/unblock the WTR belonging to the same LCR. Check that the BTS cell parameters from the RNC match the BTS HW configuration (for example frequency.7653 CELL FAULTY 2. Check the alarm history. Check the other active BTS alarms and act accordingly. FAULT NAME DESCRIPTION : Failure in optical RP3 interface : The FlexiBTS has detected an abnormal operation or a failure in an optical RP3 interface between two modules. It has not replied to the message that has been sent/resent to it. 2. FAULT NAME DESCRIPTION : Communication failed with application <x> : Communication with the application <x> failed. 2. 3. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration. Check the alarming unit. FAULT NAME DESCRIPTION : Configuration error: <x> : There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. If the unit led does not light up. INSTRUCTIONS : 1. The failure cannot be pointed to a specific module but there are several possible fault sources. Recommission the BTS to ensure that all parameters are correctly configured. Depending on the alarm source. 3. Check the RNC alarms for the alarming local cell (LCR). INSTRUCTIONS : 1. Check that the unit is properly connected. Replace the faulty module. Another possibility is that there is a mismatch between the BTS configuration and the RNC parameters. The fault may be in the WTR or WPA. the unit is faulty. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 137 (244) . reset the RF Module. 2. Check the RF module. Check the RF TX cabling. Please notice that dirty optical connectors may cause the signal level to drop too low. power). The module needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure or sticking in the unit SW. 4. INSTRUCTIONS : 1. 3. 2. FlexiBTS: 1.

or another major failure detected by the filter (a unit faulty). INSTRUCTIONS : 1. block/unblock the site. 5. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : Filter unit operation failed : A filter has not been able to tune on an appropriate sub-band (a tuning failure) properly. Reset the alarming FSM. If that does not help. If the System Module is the only alarming source or replacing the RF Module/Extension System Module does not clear the fault situation. If resetting of the alarming module does not help. Check also the SFP in the other end and replace it if needed. replace the alarming RF Module. LCRs must be configured in a way that only one sector type is taken in use in one RF Module. FAULT NAME DESCRIPTION : Incoherency with RF Modules : A Radio Module with an incompatible frequency type has been detected. FAULT NAME DESCRIPTION : Frame Clock Missing : The System Module clock reference differs from the RF Module clock. Check the cables between the System Module and RF Module. FAULT NAME DESCRIPTION : Incoherency in cell configuration : Both sector types (A and B) are configured to the same RF Module in the two-carrier case. replace the alarming RF Module/Extension System Module. INSTRUCTIONS : Recommissioning is needed. Check which Radio Modules are for the faulty frequency. If that does not help. replace the alarming System Module. 6. FAULT NAME DESCRIPTION : Frame number synchronisation error in optical interface : Timing of the new RP1 sync burst deviates from the present RP1 timing maintained in the node. replace the alarming FSM. If that does not clear the fault situation. 4. 2.Base Station Alarms (7000-7999) Extension System Module and/or System Module by blocking/unblocking it. replace the alarming Modules Small Form Factor Pluggable (SFP). 2. 3. All Radio Modules need to be variants of the same frequency. 138 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . If the reset does not clear the fault situation. Block/unblock the RF Module. 4. INSTRUCTIONS : Replace the filter unit. INSTRUCTIONS : 1.

and update compatible SW to the AXC or BTS. INSTRUCTIONS : 1. the FPGA file downloading from the flash fails. Triple-mode. FAULT NAME DESCRIPTION : Invalid carrier in WTR : There was an attempt to set the WTR to a channel not supported by the WTR (on a different frequency band). INSTRUCTIONS : 1. and update the active SW version). WMCM or WTRB) has been detected in the cabinet. and update compatible SW to the AXC or BTS. Metrosite. and update the active SW version). Replace the incompatible Radio Module (s). Make sure that correct carrier numbers are in use in the RNC. Commission the BTS with the correct WCDMA carrier values for the WTR. This fault can only occur in the self-test phase. Metrosite 50: Check the SW version of the BTS and AXC. INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version. Related BTS . INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 139 (244) . 2.AXC interface: check the SW version of the BTS and AXC. WTRA. FAULT NAME DESCRIPTION : Incompatible unit detected : An unsupported unit (for example a WSMA. FAULT NAME DESCRIPTION : LPA faulty : The unit is broken. WSPA. FAULT NAME : Low Noise Amplifier failure DESCRIPTION : The Filter has detected malfunction in the LNA unit. because the startup self-test fails. FAULT NAME DESCRIPTION : Incompatible SW version detected : A new unit/module with an incompatible SW has probably been inserted in the BTS. INSTRUCTIONS : Replace the unsupported unit with a unit of the correct type. unless it is automatically updated by the NetAct. or the synthesizer is malfunctioning. INSTRUCTIONS : Replace the alarming Flexi Radio module. Block/unblock the WPA/WMP. unless it is automatically updated by the NetAct. UltraSite. 2. FAULT NAME DESCRIPTION : Incompatible SW version detected : A new unit with an incompatible SW has probably been inserted in the BTS.7653 CELL FAULTY 2. Replace the alarming WPA/WMP.

2. 5. 2. Check the RF TX cablings (see Troubleshooting instructions). Block/unblock the WPA/WMP. INSTRUCTIONS : 1. INSTRUCTIONS : 1. Check the RF cabling between the WPA and WAF. FAULT NAME : LPA power supply alarm DESCRIPTION : The internal power supply of the unit is malfunctioning. Block/unblock the WTR and WPA/WMP or WOU. Replace alarming unit. 2. Block/unblock the WPA/WMP. Block/unblock the WPA. the antenna cabling and cables. A cable may be broken or a cable connection may be faulty. 3. Check the WAF. FAULT NAME DESCRIPTION : LPA temperature is dangerously high : The temperature of the unit is critical. INSTRUCTIONS : 1. INSTRUCTIONS : 1. Replace the WPA. Check the PTx Target value with NEMU and the HSDPA power parameters (see Troubleshooting instructions). 2. The LPA gain is too low. Replace the alarming unit. 3. It has reached its maximum acceptable level. or the synthesizers are not locked. FAULT NAME DESCRIPTION : LPA linearization fault : The quality of the output signal is poor. Check the power supply and WPA cablings and connectors from the backplane (see Troubleshooting instructions). It is also possible that the temperature sensor is broken. WIC and WPA). 3.Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : LPA input signal level is too high : The input signal level from the WTR is critically high. Replace the alarming unit. 3. Check the WOC (in the redundant configuration) installation in accordance with the Installation instructions (that is. FAULT NAME DESCRIPTION : LPA reflected power too high : A serious increase in the output impedance. 140 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . check that cable lengths and codes are correct between the WTR. 4. WOU.

7653 CELL FAULTY

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
DESCRIPTION

: LPA temperature is dangerously high
: 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
: Module Clock Faulty
DESCRIPTION : The RF Module lost lock to the incoming clock.
INSTRUCTIONS : 1. Check the cables between the System Module and RF Module.
2. Block/unblock the RF Module.
3. If that does not help, replace the alarming RF Module.

FAULT NAME
DESCRIPTION

: No connection to unit
: The connection to a unit that belongs to the BTS configuration
has been lost.
INSTRUCTIONS : UltraSite, MetroSite, MetroSite 50, Triple-mode:
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 may also be
in the WPS unit or backplane.
5. Check the power cables and connectors as well as the I2C
bus cables.
Cancel alarms: Removing and inserting the WIC, WSM or primary
WAM causes a site reset. If both WSCs are removed, inserting
the first removed WSC back into the cabinet causes a site
reset.
If the 7650 BASE STATION FAULTY alarm is issued, reset the
site. First try to reset the site by the software. If that
does not help, replace the alarming unit.

DN99580892
Issue 6-3 en
12/06/2008

# Nokia Siemens Networks

141 (244)

Base Station Alarms (7000-7999)

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

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

FAULT NAME
DESCRIPTION

: No WSM resources
: 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
DESCRIPTION

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

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

FAULT NAME
DESCRIPTION

: R-bus error
: 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.

142 (244)

# Nokia Siemens Networks

DN99580892
Issue 6-3 en
12/06/2008

7653 CELL FAULTY

2. If there are no active WSM/WMC alarms, the reason for the
alarm is a faulty WSM/WMC or WSP.
3. Run a WCDMA BTS loop test to locate the faulty unit.
4. If the WSP is faulty, block/unblock it.
5. Replace the faulty unit.
FlexiBTS:
1. Check the cabling between the System Module and RF Module.
2. Check the active RF Module alarms and act accordingly.
3. Replace the faulty module (System Module).

FAULT NAME
DESCRIPTION

: Receiving failure in Optical Interface
: 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, etc.).
2. Check the SFP from both ends (the System Module and the
module behind the faulty link). The optical interface LED
indicates the faulty SFP. Replace the SFP if faulty.
3. Clean the connectors, test the fibre cable, replace if
faulty.
4. If the previous steps do not help, replace the module
behind the faulty link.

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

FAULT NAME
DESCRIPTION

: RF BB Bus Synchronisation Error
: The baseband bus between the System Module and RF Module is
out of synchronisation.
INSTRUCTIONS : 1. Check the cables between the System Module and RF Module.
2. Block/unblock the RF Module.
3. If that does not help, block/unblock the site.

DN99580892
Issue 6-3 en
12/06/2008

# Nokia Siemens Networks

143 (244)

Base Station Alarms (7000-7999)

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

FAULT NAME
DESCRIPTION

: RF Module configuring failed
: The RF Module configuration failed because of a HW failure or
a SW fault.
INSTRUCTIONS : Replace the alarming RF Module.

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

FAULT NAME
DESCRIPTION

: RF Module failure
: The FlexiBTS has detected an abnormal operation or a failure
in the RF Module internal functionality.
INSTRUCTIONS : 1. Check the other active BTS alarms (System Module failure,
Baseband Bus failure, Failure in optical RP3 interface and
Antenna Line failure) and act accordingly.
2. Reset the alarming RF Module by blocking/unblocking it.
3. Check the cables between the System Module and RF Module.
4. If that does not help, replace the faulty RF Module.

FAULT NAME
DESCRIPTION

: RF Module failure
: The FlexiBTS has detected an abnormal operation or a failure
in the RF Module internal functionality.
INSTRUCTIONS : 1. Check the other active BTS alarms (System Module failure,
Baseband Bus failure, Failure in optical RP3 interface and
Antenna Line Device failure) and act accordingly.
2. Reset the alarming RF Module by blocking/unblocking it.
3. Check the cables between the System Module and RF Module.
4. If that does not help, replace the faulty RF Module.

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

FAULT NAME
DESCRIPTION

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

144 (244)

# Nokia Siemens Networks

DN99580892
Issue 6-3 en
12/06/2008

2. INSTRUCTIONS : 1. A telecom RNW reconfiguration # Nokia Siemens Networks 145 (244) . FAULT NAME DESCRIPTION : Telecom configuration failure : UltraSite. Then check where the alarm is now reported. MetroSite. replace the System Module. If that does not help. FAULT NAME : RX out of order DESCRIPTION : The RF Module RX RF synthesizer is not locked. Check the fans and ensure that the ambient temperature on the site is acceptable. the unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. FAULT NAME : Synchronization failure in Optical Interface <opt link/RP3 link> DESCRIPTION : The RP3 channel has achieved the frame synchronisation state and then lost it. Triple-mode: Block/unblock the alarming unit. MetroSite50. Triple-mode: A telecom slave configurations or registrations failure. INSTRUCTIONS : Swap the alarming and working links. INSTRUCTIONS : 1.7653 CELL FAULTY FAULT NAME : RF Module Overheat DESCRIPTION : The RF Module temperature is too high. A telecom RNW reconfiguration failure. replace the alarming RF Module. If the alarming link remains the same. INSTRUCTIONS : UltraSite. replace the alarming RF Module. replace the RF Module behind that link. 2. If that does not help. A telecom RNW reconfiguration failure. FlexiBTS: In case of a FR. MetroSite. Block/unblock the RF Module. FAULT NAME DESCRIPTION : RF Module Power output faulty : The Power Supply has detected an overvoltage. If the alarming link changes. 2. INSTRUCTIONS : 1. MetroSite50. replace the alarming RF Module. undervoltage or overcurrent in the RF module. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. FlexiBTS: A unit RNW configuration failure. A unit RNW configuration failure. A unit RNW configuration failure. If that does not help. Or a WSP unit to WAM allocation failure. Block/unblock the RF module. FAULT NAME DESCRIPTION DN99580892 Issue 6-3 en 12/06/2008 : Telecom configuration failure : A telecom slave configurations or registrations failure.

146 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . MetroSite. or the ambient temperature of the module (s) is outside the specified limits. If the ambient temperature is too high. Block/unblock the RF Module. INSTRUCTIONS : Remove the additional carrier in the Reconfiguration commissioning. 2. FAULT NAME : TX out of order DESCRIPTION : The RF Module TX path is not usable. INSTRUCTIONS : 1. MetroSite 50. FAULT NAME : Too many carriers allocated for LPA DESCRIPTION : Too many carriers have been allocated to the WPA/WMP. FlexiBTS: In case of a FR. replace the alarming module. Check the ambient temperature of the BTS/modules. 2. commissioned resource not ready DESCRIPTION : The faulty unit has not been configured or initialised. Triple-mode: A WSP unit to WAM allocation failure. If the reset does not clear the fault situation. FAULT NAME DESCRIPTION : Temperature alarm : The RF Module or System Module internal temperature exceeds the threshold value. make sure the airflow to the BTS modules is unobstructed. MetroSite. that is. If the ambient temperature is too low. FAULT NAME : Timeout. INSTRUCTIONS : UltraSite. MetroSite 50. INSTRUCTIONS : Recommission the site. If that does not help. the BTS modules are not covered with anything. replace the alarming RF Module. 3. 4. Reset the alarming module by blocking/unblocking it.Base Station Alarms (7000-7999) failure. Check the other BTS alarms and act accordingly. INSTRUCTIONS : 1. the module needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. FlexiBTS: A FSP unit to FCM allocation failure. Triple-mode: Block/unblock the alarming unit. it takes a while for the BTS/modules to heat themselves to the threshold value. Or UltraSite. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure.

3. unblock the unit/module. The Module needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure or sticking in the unit SW. MetroSite 50. MetroSite. perform a power-off reset. this alarm causes the alarm. Triple-mode: 1. If that does not help. 3. MetroSite 50. MetroSite. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. 2. Triple-mode: The WTR or WPA/WMP/WOU output power measurement has failed. 2. FAULT NAME : Unit initialization failure DESCRIPTION : A unit or an IP address initialisation has failed. If so. If step 3 does not help. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 147 (244) . replace the alarming unit. If that does not help. Block/unblock the alarming unit. Block/unblock the alarming unit. 4. If the WAM is the alarm source. FlexiBTS: 1. 2. FlexiBTS: 1. FAULT NAME DESCRIPTION : Unit blocked : A unit/module is blocked with the BTS Site Manager. Reset the alarming RF Module with the block/unblock function. MetroSite. Block/unblock the alarming unit. The purpose of the fault is to avoid alarms that may rise during the unit/module maintenance task. Triple-mode: 1. Check if the non-commissioned WAM is the Master WAM. check the RNC IP address in the commissioning file and modify the file if needed. INSTRUCTIONS : UltraSite.7653 CELL FAULTY FAULT NAME DESCRIPTION : TX output power measurement fault : UltraSite. INSTRUCTIONS : UltraSite. If that does not help. INSTRUCTIONS : To cancel the alarm. replace the faulty RF Module. MetroSite50. Check the units and the RF cabling between the WPA/WMP/WOU and WTR units. FlexiBTS: The RF Module output power measurement has failed. Check the cables between the System Module and RF Module. Check the alarm history to know why the WAMs' switchover occurred.

FAULT NAME : Unit SW download failed DESCRIPTION : The software update to the unit or subunit has failed. WPA: Reset the BTS. FlexiBTS: 1. INSTRUCTIONS : Replace the alarming unit/module. perform a power-off reset. If Step 1 does not help. FAULT NAME DESCRIPTION : Unit not supported by current BTS SW version : An unsupported unit was found in the BTS.Base Station Alarms (7000-7999) replace the alarming unit. If Step 2 does not help. WAM. 3. INSTRUCTIONS : Replace the alarming module. Block/unblock the WSP. 3. If Step 2 does not help. replace the alarming unit. 2. Triple-mode: 1. 2. 148 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . FCM: Reset the BTS. If that does not help. FAULT NAME DESCRIPTION : Unknown product code : A module cannot be identified by its product code but is known by its physical device address (object_ID). 2. INSTRUCTIONS : Replace the unit or upgrade the BTS SW. replace the alarming unit. FAULT NAME DESCRIPTION : Unknown HW resource : A unit cannot be identified by its product code or by its physical device address (object ID). or 1. 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. MetroSite 50. If Step 1 does not help. replace the alarming module. replace the alarming unit. Download the BTS SW again. or 1. MetroSite. 2. INSTRUCTIONS : UltraSite. Download the BTS SW again. check the RNC IP address in the commissioning file and modify the file if needed. If the FCM is the alarm source.

The antenna line is mismatched or damaged. 2. INSTRUCTIONS : 1. Check the antenna line (TX-cable-antenna) impedance matching. The antenna line is mismatched or damaged. replace the WPA unit to the correct power level type of WPA. replace the alarming unit. This is most likely a HW fault. Check the antenna cables. <line> : The Filter has detected the VSWR exceeding the defined level. This alarm is generated when the WSM/WMC unit detects errors in the incoming RR bus from the WTR unit. <line> : The filter has detected a VSWR value exceeding the defined level. INSTRUCTIONS : 1. connectors. but blocking/unblocking the unit ensures that before a site visit. FAULT NAME DESCRIPTION : WSMB RR-Bus error : The signal is transported from the WTR to the WSP via the WSM. some or all of the RX preamplifiers (max 6) are faulty. 2. The LED indicates the faulty unit. antenna and possible antenna line devices. INSTRUCTIONS : If the WPA is accidently changed to a different power level type of WPA.7653 CELL FAULTY FAULT NAME DESCRIPTION : VSWR major alarm. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 149 (244) . Check the antenna line (TX-cable-antenna) impedance matching. The antenna connector information at the end of the alarm text specifies the defective antenna line. Run the WCDMA BTS loop test. Block/unblock the WAF unit. INSTRUCTIONS : 1. connectors. The antenna connector information at the end of the alarm text specifies the defective antenna line. MetroSite 50: One. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : WPA power level changed : The power level of a replaced WPA unit differs from the original WPA unit. FAULT NAME DESCRIPTION : WAF low noise amplifier faulty : One of the two RX preamplifiers (one in the main branch and the other in the diversity branch) is faulty. 2. The reason for the failure is probably the WTR or WSMB/WMC unit. The LED indicates the faulty unit. antenna and possible antenna line devices. The unit may have been installed incorrectly or the backplane cabling is faulty. If that does not help. FAULT NAME DESCRIPTION : VSWR alarm. Check the antenna cables.

Block/unblock the alarming unit. 3. INSTRUCTIONS : 1. 3. Check the backplane cables and connectors (see Troubleshooting instructions). Block/unblock the alarming unit. Block/unblock the alarming unit. Block/unblock the alarming unit. INSTRUCTIONS : 1. Replace the alarming unit. INSTRUCTIONS : 1. This can be caused by a missing or bad quality reference clock signal from the WSC or a WTR unit HW failure. The downlink transmission of the TX must be stopped. The TX is out of order and needs to be shut down. FAULT NAME DESCRIPTION : WTR internal clock faulty : The WTR internal system clock is missing. The transmitted and received frequencies are incorrect. INSTRUCTIONS : 1. or a WTR unit HW failure. Replace the units indicated in the alarm one by one and check whether the problem is cleared. 150 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .Base Station Alarms (7000-7999) 2. Replace the alarming unit. FAULT NAME DESCRIPTION : WTR local oscillator not locked : The TX IF synthesizer (common to both TX chains) cannot lock to the defined frequency. 2. Block/unblock the alarming unit. The transmitted and received frequencies are incorrect. 2. This can be caused by a missing or bad quality reference clock signal from the WSC. Replace the alarming unit. Check backplane cables and connectors. 3. FAULT NAME DESCRIPTION : WTR internal clock faulty : The WTR VCXO PLL is not locked. 2. Replace the alarming unit. FAULT NAME DESCRIPTION : WTR output power fault : An amplifier stage is out of order in the TX chain. 2. Chcek the backplane cables and connectors. Replace the alarming unit. INSTRUCTIONS : 1. 2. FAULT NAME DESCRIPTION : WTR output power decreased : The TX1 RF and/or TX2 RF signal level of the main RF output is lower than the predetermined level.

Replace the alarming unit. 2. FAULT NAME DESCRIPTION : WTR power supply voltage fault : There is a fault in the power feed or RF cabling. FAULT NAME DESCRIPTION : WTR synthesizer is not locked : The TX & RX RF synthesizer or the RX IF synthesizer is not locked (or the RF synthesizer buffer amplifier is faulty). The transmitter will be shut down. WSP and WTR. Block/unblock the WTR unit belonging to the alarming cell. INSTRUCTIONS : 1. Check the RF cabling. Note! The problem can be in the unit connector. See Troubleshooting instructions. Block/unblock the WAF unit belonging to the alarming cell. The signal frequency should be exactly half of the system clock frequency. 3. INSTRUCTIONS : 1. the sensor is probably broken. 2. cabinet cabling or backplane. One or more critical power supply voltages or BIAS currents are outside the allowed range.7653 CELL FAULTY FAULT NAME DESCRIPTION : WTR output power fault : An amplifier stage is out of order in the TX chain. Block/unblock the alarming unit. If you can find no reason. Check the WSM. WTR backplane connectors. or the receiver might receive a wrong frequency or is not receiving. 2. Block/unblock the alarming unit. Check the other active alarms. The output frequency of the transmitter can be wrong or missing. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 151 (244) . FAULT NAME : WTR temperature is high DESCRIPTION : The internal temperature of the WTR is dangerously high. Check the other active temperature or cooling fan-related alarms. or there is external interference. INSTRUCTIONS : 1. 2. connectors. INSTRUCTIONS : 1. 2. INSTRUCTIONS : 1. Replace the alarming unit. external devices in the antenna line (for example MHAs) and external interference of RX band (with a spetrum analyzer). FAULT NAME DESCRIPTION : WTR RT-bus fault : The bus clock signal is corrupted or missing in the RT bus. Replace the unit.

152 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .Base Station Alarms (7000-7999) Cancelling Do not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected.

DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 153 (244) . Instructions Verify the configuration of a BTS by checking the commissioning. cabling and correct installation of the units/modules at the BTS. Refer also to the individual alarm instructions. When an active alarm is a 'Start' alarm. Supplementary information fields 1 rack (cabinet) number 2 shelf number 3 slot 4 type of unit 5 unit number 6 subunit number For more information. Check the reason for the fault from the supplementary text field of the alarm. the site should be reset to recover from any temporary faults. Before a unit/module is replaced at the BTS.7654 CELL OPERATION DEGRADED 32 7654 CELL OPERATION DEGRADED Meaning A major fault (or faults) has occurred in a unit/module (or units/modules) that belong to the sector indicated in the alarm. replace the faulty unit/module (see source of the alarm and instructions fields of the corresponding alarm). a site reset is required to cancel the alarm. contact the local Help Desk. If that does not help. which might have caused the misbehaviour of the unit/module. If the site reset or unit/module block/unblock does not help. see instructions on Alarm Structure. Make sure the environment does not cause the fault.

Some ARIO alarms can be cancelled without a reset but most ARIO alarms require the WOU block/unblock to cancel. 154 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . FAULT NAME DESCRIPTION : AIR minor alarm : ARIO has detected a Minor level alarm. Check the antenna line (see Troubleshooting instructions). 4. 3. Block/unblock the WAF unit (check if the alarm reappears after 5 minutes). see Nokia WCDMA BTS Alarm Descriptions (SW and release document). Check the bias-T and MHA commissioning. If that does not clear the fault situation. INSTRUCTIONS : Check the WOU or WRUs. for example). 2. FAULT NAME DESCRIPTION : 10b8b coding error in Optical Interface device <opt link/RP3> : The fibre cable has interference. replace the alarming RF Module/Extension System Module. The BIAS-T may be faulty. If the System Module is the only alarming source or replacing the RF Module/Extension System Module does not clear the fault situation. INSTRUCTIONS : 1.Base Station Alarms (7000-7999) For more information. A physical connection failure between the optical interface and summing function (caused by bad circuit joints. the data becomes faulty. reset the RF Module and/or Extension System Module by blocking/unblocking it. The antenna cable between the WAF and MHA is faulty or the antenna is faulty. Check the PITA cable connection (RJ45). FAULT NAME DESCRIPTION : Antenna1 connection fault : The BIAS-T has detected that the reflected TX power from the antenna has increased. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : AIR major alarm : ARIO has detected a Major level alarm. 3. Depending on the alarm source. INSTRUCTIONS : Check the WOU or WRUs. 2. Use the ARIO Local Management Tool and the Nokia Advanced Indoor Radio user documentation to diagnose the error cause. replace the alarming System Module. Use the ARIO Local Management Tool and the Nokia Advanced Indoor Radio user documentation to diagnose the error cause. Some ARIO alarms can be cancelled without a reset but most ARIO alarms require the WOU block/unblock to cancel.

Check the right connection (see User Manual). 2. replace the antenna line device. FAULT NAME : Antenna line device configuration failure DESCRIPTION : An antenna line device is not properly configured. Reset the alarming RF module by block/unblock. 3. c. overcurrent. 2. Check / correct antenna line configuration.7654 CELL OPERATION DEGRADED a. Update proper SW to the device. INSTRUCTIONS : 1. VSWR out of range. 3. If the reset does not cancel the alarm or the alarm reappears continuously. Update proper SW to the device. # Nokia Siemens Networks 155 (244) . INSTRUCTIONS : 1. Check the voltage (see connector pins in Troubleshooting instructions). replace the faulty parts and/or devices along the antenna line. INSTRUCTIONS : 1. b. If the reset does not clear the fault situation. 2. FAULT NAME DESCRIPTION : Antenna Line Device failure : The System Module or device itself has detected an abnormal operation or a failure in the antenna line device. If that does cancel the alarm or the alarm continually reappears. Replace the RF Module. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION DN99580892 Issue 6-3 en 12/06/2008 : Antenna Line failure : The RF Module has detected an abnormal operation or a failure in the antenna line. for example. 4. Block/unblock the Flexi Radio module to give a power-off reset to antenna line devices. Make sure the antenna line connectors are in the right torque. Usually this is a permanent fault (the hardware is broken). FAULT NAME DESCRIPTION : Antenna line device HW failure : A hardware failure detected by an antenna line device. Check by cross connecting RJ45 cables between other sectors. replace the antenna line device. FAULT NAME DESCRIPTION : Antenna line device configuration failure : An antenna line or antenna line device is not properly configured. 2. replace the antenna line device. If that does cancel the alarm or the alarm continually reappears. Check the antenna line and antenna line devices.

If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault 156 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . If a reset does not clear the fault situation. Fix or replace the faulty parts/devices. The antenna connector information at the end of the alarm text specifies the defective antenna line. Check the cables between the System Module and RF Module/Extension System Module. INSTRUCTIONS : 1. The antenna line may be damaged (short circuit) or some antenna line device is causing overload. Reset the alarming RF module by block / unblock. replace the alarming RF Module/Extension System Module. 4. 2. depending on the alarm source: a. 3. Reset the alarming RET module by blocking/unblocking the RF Module which the RET is connected to. FAULT NAME DESCRIPTION : Baseband Bus failure : The FlexiBTS has detected an abnormal operation or a failure in the BTS internal baseband bus. INSTRUCTIONS : 1. replace the faulty device (s). 2. FAULT NAME DESCRIPTION : Antenna Line failure. Check the cables related to the antenna tilting system (RET). INSTRUCTIONS : Check the antenna line and antenna line devices. c. FAULT NAME DESCRIPTION : Antenna Tilting failure : Antenna tilting is not possible or cannot be done properly. Reset the RF Module by blocking/unblocking it. Or the connection to the TILT is lost. replace the faulty parts and/or devices along the antenna line. 4. Reset the master System Module. Reset the Extension System Module by blocking/unblocking it. Check the antenna line and antenna line devices. <line> : The Filter has detected overcurrent on the antenna line. The failure cannot be pointed to a specific module but there are several possible fault sources. 2. Make sure the antenna line connectors are in the right torque. 3. 3. 5. Check the other active BTS alarms and act accordingly. Reset the RF Module and/or System Module. If a reset does not clear the fault situation.Base Station Alarms (7000-7999) INSTRUCTIONS : 1. If the reset does not clear the fault situation. b. Replace the RF Module.

Triple-mode: The BTS unit properties data is invalid or missing. 3. FAULT NAME DESCRIPTION : BTS file error : UltraSite. Download two different SW packages so that the faulty file will be removed from the BTS. MetroSite. FlexiBTS: . a hardware problem in the unit or cabinet. The error can be caused by a unit reset during the SW update. FAULT NAME : BTS Config error (Different WTR variants cannot coexist in cell) DESCRIPTION : There are different WTR variants in the same cell. INSTRUCTIONS : Replace the conflicting WTR unit with a compatible unit.1 onwards: The FSP MCU SW file is invalid or missing. INSTRUCTIONS : 1.The optical interface FPGA file is invalid or missing. INSTRUCTIONS : UltraSite. replace the alarming unit. INSTRUCTIONS : Recommission (Reconfiguration commissioning) the BTS with the correct carrier candidate values. Download the SW again.The BTS unit properties data is invalid or missing. FlexiBTS: . MetroSite 50. MetroSite50. Replace the FCM.7654 CELL OPERATION DEGRADED situation. or a corrupted flash file system. Retry the SW update. MetroSite. If the fault still exists after 10 minutes. replace the alarming master System Module. .The BTS unit properties data is invalid or missing. Download two different SW packages so that the faulty file will be removed from the BTS. . 3.WN4. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 157 (244) . MetroSite. FAULT NAME DESCRIPTION : BTS config error (incorrect carrier candidates) : Carrier candidates are commissioned for each cell (not WTR/LTX specific). 2. 2. FlexiBTS: 1. 2. MetroSite50. FAULT NAME DESCRIPTION : BTS file error : UltraSite. Download the SW again. Triple-mode: 1. FAULT NAME DESCRIPTION : BS SW download or activation failed : The SW update to the BTS has failed. replace the alarming unit. Triple-mode: The BTS unit properties data is invalid or missing. If other flash memory-related alarms are active for the alarming unit at the same time.

If that does not help. Download two different SW packages so that the faulty file will be removed from the BTS. 2. FAULT NAME DESCRIPTION : Commissioning error: <x> : Some of the commissioning parameters are either missing or faulty. FAULT NAME DESCRIPTION : BTS internal SW management problem : Software update to a module or subassembly has failed. 4. 5. Update and activate the SW to the BTS. FAULT NAME DESCRIPTION : Cell power parameter out of range : The power values in the cell configuration data sent by the RNC are out of range. Reset the RF Module by blocking/unblocking it. change the alarming module. 2. MetroSite. or there is a mismatch between them. Reset the RF Module and/or System Module. 3. check the SW files. b. 3. 3. If the fault still exists after 10 minutes. FAULT NAME DESCRIPTION 158 (244) : Communication failed with application <x> : Communication with the application <x> failed. Replace the system module. Triple-mode: 1. Replace the alarming module. FlexiBTS: 1.The optical interface FPGA file is invalid or missing. Load the correct commissioning file to the BTS. INSTRUCTIONS : UltraSite. replace the alarming unit. Download the SW again. Check the other active alarms. INSTRUCTIONS : Set the correct power values to the RNC. INSTRUCTIONS : 1. or a corrupted SW file has been detected in the FLASH. If the ROM disk is corrupted. INSTRUCTIONS : 1. Download the SW again. 2. Reset the System Module. 2.Base Station Alarms (7000-7999) . Check the commissioning parameters with the BTS Site Manager Commissioning Wizard. MetroSite 50. depending on the alarm source: a. It has not # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Download two different SW packages so that the faulty file will be removed from the BTS.

Check that the unit is properly connected. Check the alarming unit. FAULT NAME DESCRIPTION DN99580892 Issue 6-3 en 12/06/2008 : Diversity antenna line fault : The operating voltage of the Mast Head Amplifier (MHA) is supplied through the BIAS-T from the WAF. The cable between the MHA and WAF is faulty. another antenna line device between the MHA and WAF is faulty. the unit is faulty. The WAF monitors the consumption of the current and generates an alarm if it deviates from normal. FAULT NAME DESCRIPTION : Diversity antenna line fault : The operating voltage of the Mast Head Amplifier (MHA) is supplied through the BIAS-T from the WAF. INSTRUCTIONS : 1. 2. INSTRUCTIONS : 1. 3. the Bias-T is faulty. the MHA is faulty. Bias-T or MHA (see Troubleshooting instructions). If that does not help. Check the alarm history. INSTRUCTIONS : 1. 4. The fault can be in the WAF. Check the installed HW/SW version compatibility and the HW compatibility with the current BTS configuration. FAULT NAME DESCRIPTION : Configuration file corrupted : The RF Module SW detected conflicting or corrupted configuration data. 4. 2. Another possibility is that there is a mismatch between the BTS configuration and the RNC parameters. Check that the BTS cell parameters from the RNC match the BTS HW configuration (for example frequency. or the MHA does not exist. Recommission the BTS to ensure that all parameters are correctly configured. FAULT NAME DESCRIPTION : Configuration error: <x> : There is a compatibility problem in the BTS HW/SW versions or the HW/HW configuration. 3.7654 CELL OPERATION DEGRADED replied to the message that has been sent/resent to it. The WAF monitors the consumption of the current and generates an alarm if it deviates from normal. If the unit led does not light up. Check the RF cabling and Bias-T. The cable between the MHA and WAF is # Nokia Siemens Networks 159 (244) . 2. Block/unblock the WAF in belonging LCR. replace the alarming RF Module. Check the MHA commissioning parameters. power). Block/unblock the RF Module 2. INSTRUCTIONS : 1. Check the RNC alarms for the alarming local cell (LCR).

3. MetroSite. Check the RF cabling and Bias-T. INSTRUCTIONS : UltraSite. Check the other active alarms. the MHA is faulty. replace the alarming System Module. Check the MHA commissioning parameters. Extension System Module and/or System Module by blocking/unblocking it. If the ROM disk is corrupted. INSTRUCTIONS : 1. The fault can be in the WAF. INSTRUCTIONS : 1. INSTRUCTIONS : Replace the filter unit. change the alarming unit. replace the alarming Modules Small Form Factor Pluggable (SFP). reset the RF Module. or the MHA does not exist. FAULT NAME DESCRIPTION : Flash operation failure : The flash memory operation failure.Base Station Alarms (7000-7999) faulty. or another major failure detected by the filter (a unit faulty). FAULT NAME DESCRIPTION : Failure in optical RP3 interface : The FlexiBTS has detected an abnormal operation or a failure in an optical RP3 interface between two modules. Block/unblock the related WAF. the flash chip may be broken. 6. 2. MetroSite 50. If the reset does not clear the fault situation. The failure cannot be pointed to a specific module but there are several possible fault sources. There are no recovery actions and due to that the block/unblock can be tried once. Bias-T or MHA (see Troubleshooting instructions). If that does not clear the fault situation. 3. If this alarm appears continuously. If the System Module is the only alarming source or replacing the RF Module/Extension System Module does not clear the fault situation. another antenna line device between the MHA and WAF is faulty. 4. replace the alarming RF Module/Extension System Module. 160 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Check the cables between the System Module and RF Module/Extension System Module. Triple-mode: 1. 4. 2. Block/unblock the alarming unit. 5. FAULT NAME DESCRIPTION : Filter unit operation failed : A filter has not been able to tune on an appropriate sub-band (a tuning failure) properly. Check also the SFP in the other end and replace it if needed. Please notice that dirty optical connectors may cause the signal level to drop too low. the Bias-T is faulty. 2. Check the other active BTS alarms and act accordingly. Depending on the alarm source.

Triple-mode. unless it is automatically updated by the NetAct. INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version. replace the alarming unit. FAULT NAME DESCRIPTION : Incompatible SW version detected : A new unit with an incompatible SW has probably been inserted in the BTS. Related BTS . and update the active SW version). Block/unblock the alarming module. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. and update compatible SW to the AXC or BTS. Check the WTR RF TX cabling. 3. FAULT NAME DESCRIPTION : Incompatible SW version detected : A new unit with an incompatible SW has probably been inserted in the BTS. and update compatible SW to the AXC or BTS. replace the alarming module. INSTRUCTIONS : 1. UltraSite. Check the other active alarms. 2. and update the active SW version). Metrosite 50: Check the SW version of the BTS and AXC. 2. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 161 (244) . 4. If the ROM disk is corrupted. FAULT NAME DESCRIPTION : Frame Clock Missing : The System Module clock reference differs from the RF Module clock. replace the alarming unit. INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version. 2. 3. There are no recovery actions and due to that the block/unblock can be tried once. INSTRUCTIONS : 1.AXC interface: check the SW version of the BTS and AXC. If that does not help. FlexiBTS: 1. replace the alarming RF Module. block/unblock the site.7654 CELL OPERATION DEGRADED If that does not help. Check the cables between the System Module and RF Module. If that does not help. Block/unblock the RF Module. If that does not help. unless it is automatically updated by the NetAct. Metrosite. FAULT NAME : Gain adjust alarm DESCRIPTION : The WTR cannot adjust the TX output power. Block/unblock the WTR. change the alarming module. If that does not help.

or the number of carriers for the HW type is exceeded. 2. Reset the site. or the carrier spacing limit is exceeded. FAULT NAME DESCRIPTION : Invalid frequency channel for the BTS HW : The requested channel in the cell setup is not acceptable for the BTS hardware. INSTRUCTIONS : Check the RNC cell parameters against the BTS HW configuration. FAULT NAME DESCRIPTION : Invalid frequency channel for the BTS HW : 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. the number of carriers for the HW type is exceeded. 162 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . The first cell needs to be calibrated and therefore the second active cell needs to be cleared. INSTRUCTIONS : 1. the frequency band and/or the carrier spacing and/or the number of carriers is/are not acceptable for the BTS HW. The cell frequency is out of the min/max limit of the HW. There are different type variations of the HW that may have limitations in the supported frequency range and bandwidth. or the carrier spacing limit is exceeded. that is. but the clearing fails. The cell frequency is out of the minimum/maximum limit of the HW. INSTRUCTIONS : Check the RNC cell parameters against the BTS HW configuration. The cell frequency is out of the min/max limit of the HW. because of an incorrect frequency band and/or a carrier spacing and/or the number of carriers. or the number of carriers for the HW type is exceeded. The unit needs to be blocked/unblocked to get it initialized/configured again if there was an internal failure. Block/unblock the WPA/WMP unit belonging to the same LCR as the alarming WTR. INSTRUCTIONS : Check the RNC cell parameters against the BTS HW configuration. There are different type variations of the HW that may have limitations in the supported frequency range and bandwidth. FAULT NAME : Low Noise Amplifier failure DESCRIPTION : The Filter has detected malfunction in the LNA unit. INSTRUCTIONS : Replace the alarming Flexi Radio module. FAULT NAME DESCRIPTION : Invalid frequency channel for the BTS HW : The requested channel in the cell setup is not acceptable. There are different type variations of the HW that may have limitations in the supported frequency range and bandwidth. or the carrier spacing limit is exceeded.Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : Initial calibration not started because other cell not cleared : There is a shared WPA/WMP in the configuration (the WPA serves two cells).

The cable between the MHA and WAF is faulty. Block/unblock the related WAF. which therefore cannot perform the specified gain. Bias-T or MHA (see Troubleshooting instructions). Check the cables related to the Mast Head Amplifier (MHA). another antenna line device between the MHA and WAF is faulty. The cable between the MHA and WAF is faulty. FAULT NAME DESCRIPTION : Main antenna line fault : The operating voltage of the MHA is supplied through the Bias-T from the WAF. Check the MHA commissioning parameters. Block/unblock the WAF in belonging LCR. INSTRUCTIONS : 1. replace the faulty device (s). FAULT NAME DESCRIPTION : Main antenna line fault : The operating voltage of the MHA is supplied through the Bias-T from the WAF. 4. the Bias-T is faulty. The fault can be in the WAF. 3. The WAF monitors the consumption of the current and generates an alarm if the consumption deviates from normal. Check the RF cabling and Bias-T. Reset the alarming MHA module by blocking/unblocking the RF Module which the MHA is connected to. the Bias-T is faulty. 3. INSTRUCTIONS : 1. or there is no connection to the MHA unit. 2. another antenna line device between the MHA and WAF is faulty. INSTRUCTIONS : 1. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 163 (244) . the MHA is faulty. the MHA is faulty. 2. Check the MHA commissioning parameters. The fault can be in the WAF. 2. Check the RF cabling and Bias-T.7654 CELL OPERATION DEGRADED FAULT NAME DESCRIPTION : LPA gain fault : A malfunction in some part of the amplifier. The WAF monitors the consumption of the current and generates an alarm if the consumption deviates from normal. FAULT NAME DESCRIPTION : Mast Head Amplifier fault : FlexiBTS has detected an abnormal operation or a failure in the Mast Head Amplifier (MHA). If a reset does not clear the fault situation. 3. or the MHA does not exist. Block/unblock the WPA/WMP. Bias-T or MHA (see Troubleshooting instructions). INSTRUCTIONS : 1. 4. or the MHA does not exist. Replace the alarming WPA/WMP. 2.

164 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : Mast Head Amplifier fault : The FlexiBTS has detected an abnormal operation or a failure in the Mast Head Amplifier (MHA). not just the faulty one! If the alarm re-appears. replace the faulty unit. NOTE! This operation affects to all antenna lines and cells in use within the FR Module. <line> : The Mast Head Amplifier does not work properly. If the reset does not clear the fault situation. If both stages of the LNA on the uplink path fail. the MHA has no gain but some loss. the MHA swithes the LNA to by-pass mode. FAULT NAME DESCRIPTION : Mast Head Amplifier fault. replace the faulty device (s). If only either stage of the LNA fails. If both stages of the LNA on the uplink path fails. Fix or replace the broken parts. Reset the alarming MHA module by blocking/unblocking the RF Module which the MHA is connected to. In the case of an integrated MHA (WMHC). the MHA swithes the LNA on the by-pass mode. This is done by blocking and unblocking the Flexi Radio (FR) Module. not just the faulty one! If the alarm re-appears. With an integrated MHA (WMHC). Restart the MHA by swithing the antenna line power off and on. the fault may cover both main and diversity branches or just either. Check the antenna cables and connectors towards the MHA. INSTRUCTIONS : 1. the MHA has no gain but some loss. On the by-pass mode. The received RF signal level is decreased. 2. 2. The received RF signal level is decreased. Fix and/or replace the broken parts. Check the cables related to the Mast Head Amplifier (MHA). In by-pass mode. Check the antenna cables and connectors towards the MHA. INSTRUCTIONS : 1. the fault may affect both main and diversity branches or just either. Note that the Tower Mounted Amplifier (TMA) is a synonym for the MHA and is used by the Antenna Interface Standards Group (AISG). FAULT NAME DESCRIPTION : Mast Head Amplifier fault. replace the alarming unit. 3. INSTRUCTIONS : 1. Restart the MHA by blocking and unblocking the Flexi Radio (FR) Module. the MHA still has about a half of its normal gain. the MHA still has about a half of its normal gain. If only either stage of the LNA fails. <line> : The Mast Head Amplifier does not work properly. NOTE! This operation affects all antenna lines and cells related to the FR Module. 2.

the unit is faulty. First try to reset the site by the software. replace the alarming unit. 2. If both WSCs are removed. reset the site. There are two possible causes: Configuration error (2 different FSPs functioning) . If that does not help. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 165 (244) . the unit is faulty. try recommissioning the site. If the unit led does not light up. MetroSite 50. WSM or primary WAM causes a site reset. If the unit led does not light up. INSTRUCTIONS : Check the baseband bus configuration parameters from the commissioning file. FlexiBTS: 1.after acknowledgement the fault will return again. Data corruption on the bus . If the 7650 BASE STATION FAULTY alarm is issued. Cancel alarms: Removing and inserting the WIC. Check that the unit is properly connected. The fault reduces the gain performance or completely prevents the function of the MHA.appears once when unsynchronised data is sent by the BB. 2. INSTRUCTIONS : UltraSite. 4. MetroSite. Triple-mode: 1. inserting the first removed WSC back into the cabinet causes a site reset. If SW updates have been done recently. The address is correct but the type fields do not match. reload the SW. INSTRUCTIONS : Replace the alarming module. Check that the unit is properly connected. FAULT NAME DESCRIPTION : No connection to unit : The connection to a unit that belongs to the BTS configuration has been lost. Check the power cables and connectors as well as the I2C bus cables. If the WAF or WIC is alarming. FAULT NAME DESCRIPTION : MHA unit operation failure : A fault in the TMA is detected. Check the alarm history. 5. Check the alarm history. Check the alarming unit.7654 CELL OPERATION DEGRADED FAULT NAME DESCRIPTION : Message type mismatch in summing : A type mismatch in the BB summing. 3. alarming unit and subrack. The fault may also be in the WPS unit or backplane.

replace the System Module. MetroSite 50. See the section No connection to unit in the troubleshooting instructions. If the WSP is faulty. block/unblock it. 3. FAULT NAME DESCRIPTION : Optical Interface Data/Control/Ethernet Buffer Full : The RP3 or Ethernet buffering is not working and the buffer becomes full. INSTRUCTIONS : UltraSite. 2. check the WTR and WSM cable. If the WSM/WMC also generates an alarm from a WTR unit. Replace the faulty unit. INSTRUCTIONS : 1. FlexiBTS: 166 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Increase the number of WAF units in the BTS. Triple-mode: The bus between the WSP and WTR does not work. The optical device has some malfunction. the reason for the alarm is a faulty WSM/WMC or WSP. FlexiBTS: Error in the FSP or in the connection between the FSP and FCM. 5. MetroSite and Triple-mode: 1. MetroSite 50. 4. If the alarming link changes. INSTRUCTIONS : UltraSite. The fault can be generated due to synchronisation problems or an incorrect initialisation. MetroSite 50: Change the WAF. replace the alarming RF Module. MetroSite. FAULT NAME DESCRIPTION : R-bus error : UltraSite. 2. If the alarming link remains the same. Run a WCDMA BTS loop test to locate the faulty unit.Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : No feedback signal : The feedback signal to predistortion is too weak or missing. INSTRUCTIONS : Swap the alarming and working links. Block/unblock the RF Module. Then check where the alarm is now reported. The R bus errors are probably caused by a faulty WSM or WTR. MetroSite. If that does not help. 2. replace the RF Module behind that link. Triple-mode: 1. If there are no active WSM/WMC alarms. The TX performance is degraded. FAULT NAME : Not enough WAF resources in LCR DESCRIPTION : There are not enough WAF units in a cell.

Failure in optical RP3 interface and Antenna Line failure) and act accordingly. INSTRUCTIONS : 1. replace the alarming RF Module. If that does not help. Block/unblock the RF Module. INSTRUCTIONS : 1. 2. replace the alarming RF Module FAULT NAME DESCRIPTION : RF BB Bus Synchronisation Error : The baseband bus between the System Module and RF Module is out of synchronisation. Replace the faulty module (System Module). INSTRUCTIONS : 1. If that does not help. 3. Baseband Bus failure. Block/unblock the RF Module. FAULT NAME : RF BB Bus Connection Transmission Error DESCRIPTION : There is an error in the baseband or optical bus. replace the alarming RF Module. FAULT NAME : RF BB Energy too high DESCRIPTION : The TX feedback signal power is too high. If that does not help.7654 CELL OPERATION DEGRADED 1. Block/unblock the RF Module. FAULT NAME DESCRIPTION : RF Module failure : The FlexiBTS has detected an abnormal operation or a failure in the RF Module internal functionality. Check the other active BTS alarms (System Module failure. 2. replace the alarming RF Module. 2. INSTRUCTIONS : 1. replace the RET unit. Recalibrate the RET antenna. FAULT NAME DESCRIPTION : RET antenna control failure : The antenna tilting is not possible or may not be done properly. Check the cabling between the System Module and RF Module. block/unblock the site. INSTRUCTIONS : 1. If that does not help. Block/unblock the RF Module. 2. 2. If that does not help. Check the active RF Module alarms and act accordingly. 2. Check the cables between the System Module and RF Module. If that does not cancel the alarm or the alarm continually reappears. INSTRUCTIONS : 1. 3. FAULT NAME : RF BB Bus Configuration Error DESCRIPTION : The RF Module baseband bus is configured incorrectly. 4. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 167 (244) .

replace the faulty RF Module. Check the cables between the System Module and RF Module. INSTRUCTIONS : 1. 168 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . If that does not help. Reset the alarming RF Module by blocking/unblocking it. INSTRUCTIONS : 1. 2. replace the alarming RF Module. 2. FAULT NAME DESCRIPTION : RF Module failure : The FlexiBTS has detected an abnormal operation or a failure in the RF Module internal functionality. Baseband Bus failure. FAULT NAME : RF Module Filter input power missing DESCRIPTION : The RF Module filter has measured too low TX power. 3. INSTRUCTIONS : 1. 4. 2. If that does not help. 3. Block/unblock the RF Module. Block/unblock the RF Module. INSTRUCTIONS : 1. replace the alarming RF Module. Failure in optical RP3 interface and Antenna Line Device failure) and act accordingly. INSTRUCTIONS : 1.If that does not help. Check the other active BTS alarms (System Module failure. Block/unblock the RF module. FAULT NAME : RX out of order DESCRIPTION : The RF Module RX RF synthesizer is not locked. Check the cables between the System Module and RF Module. FAULT NAME DESCRIPTION : RF Module Power output faulty : The Power Supply has detected an overvoltage. If that does not help. replace the alarming RF Module. FAULT NAME : RF Module Gain adjusting failure DESCRIPTION : The TX output power adjustment failed.Base Station Alarms (7000-7999) 2. INSTRUCTIONS : 1. If that does not help. FAULT NAME DESCRIPTION : RF Module file not found : The RF Module SW detected that a non-critical configuration file is missing. replace the alarming RF Module. 4. 2. 2.Block/unblock the RF Module. If that does not help. Reset the alarming RF Module by blocking/unblocking it. replace the faulty RF Module. undervoltage or overcurrent in the RF module. Block/unblock the RF Module.

Or UltraSite. the module needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. MetroSite 50. Or a WSP unit to WAM allocation failure.7654 CELL OPERATION DEGRADED 2. FlexiBTS: A FSP unit to FCM allocation failure. replace the alarming RF Module. or the ambient temperature of the module (s) is outside the specified limits. INSTRUCTIONS : 1. A telecom RNW reconfiguration failure. A unit RNW configuration failure. MetroSite50. FAULT NAME DESCRIPTION : Telecom configuration failure : A telecom slave configurations or registrations failure. FAULT NAME DESCRIPTION : Temperature alarm : The RF Module or System Module internal temperature exceeds the threshold value. A unit RNW configuration failure. FlexiBTS: In case of a FR. A telecom RNW reconfiguration failure. MetroSite. Check the other BTS alarms and act accordingly. Triple-mode: Block/unblock the alarming unit. FAULT NAME DESCRIPTION : Telecom configuration failure : UltraSite. INSTRUCTIONS : UltraSite. the unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. Triple-mode: A WSP unit to WAM allocation failure. FlexiBTS: In case of a FR. MetroSite. FAULT NAME : SW corrupted DESCRIPTION : A corrupted SW file in the FLASH is detected. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. MetroSite50. MetroSite. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. If that does not help. Triple-mode: A telecom slave configurations or registrations failure. MetroSite 50. INSTRUCTIONS : UltraSite. FlexiBTS: A unit RNW configuration failure. A telecom RNW reconfiguration failure. INSTRUCTIONS : Update the SW to the BTS. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 169 (244) . Triple-mode: Block/unblock the alarming unit. MetroSite.

MetroSite 50. INSTRUCTIONS : 1. If the reset does not clear the fault situation. Block/unblock the RF Module. MetroSite. the BTS modules are not covered with anything. MetroSite. FAULT NAME : TX out of order DESCRIPTION : The RF Module TX path is not usable. replace the alarming RF Module. Triple-mode: The WTR or WPA/WMP/WOU output power measurement has failed. Block/unblock the RF Module. INSTRUCTIONS : UltraSite. 3. FAULT NAME : Timeout. block/unblock the RF Module. INSTRUCTIONS : 1. If the ambient temperature is too low. MetroSite 50. 4. FAULT NAME : Temperature too low DESCRIPTION : The temperature inside the RF Module is too low. If the ambient temperature is too high. commissioned resource not ready DESCRIPTION : The faulty unit has not been configured or initialised. If that does not help. replace the alarming RF Module. FAULT NAME DESCRIPTION : TX output power measurement fault : UltraSite. Triple-mode: 170 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 2. make sure the airflow to the BTS modules is unobstructed. INSTRUCTIONS : Recommission the site. replace the faulty RF Module. Block/unblock the RF Module. INSTRUCTIONS : 1. If that does not help. If that does not help. 2. 2. Ensure that the ambient temperature on the site is acceptable. Check the ambient temperature of the BTS/modules.Base Station Alarms (7000-7999) 2. it takes a while for the BTS/modules to heat themselves to the threshold value. FlexiBTS: The RF Module output power measurement has failed. If that does not help. INSTRUCTIONS : 1. If that does not help. 3. 2. replace the alarming module. replace the alarming RF Module. Reset the alarming module by blocking/unblocking it. FAULT NAME : Transmission quality detoriated DESCRIPTION : The TX signal adjustment fails. that is. FAULT NAME : Transmission quality deteriorated DESCRIPTION : The TX signal adjustment fails.

The Module needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure or sticking in the unit SW. perform a power-off reset. The purpose of the fault is to avoid alarms that may rise during the unit/module maintenance task. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 171 (244) . replace the alarming unit. Block/unblock the alarming unit. MetroSite50.7654 CELL OPERATION DEGRADED 1. The unit needs to be blocked/unblocked to get it initialised/configured again if there was an internal failure. replace the faulty RF Module. 2. Reset the alarming RF Module with the block/unblock function. 2. FlexiBTS: 1. Check the cables between the System Module and RF Module. FAULT NAME : Unit initialization failure DESCRIPTION : A unit or an IP address initialisation has failed. INSTRUCTIONS : To cancel the alarm. If that does not help. unblock the unit/module. If so. check the RNC IP address in the commissioning file and modify the file if needed. this alarm causes the alarm. Block/unblock the alarming unit. 2. Check if the non-commissioned WAM is the Master WAM. If that does not help. 3. check the RNC IP address in the commissioning file and modify the file if needed. 4. Block/unblock the alarming unit. FAULT NAME DESCRIPTION : Unit blocked : A unit/module is blocked with the BTS Site Manager. perform a power-off reset. replace the alarming unit. If that does not help. FlexiBTS: 1. MetroSite. If that does not help. If Step 2 does not help. If step 3 does not help. replace the alarming unit. 3. Check the alarm history to know why the WAMs' switchover occurred. Check the units and the RF cabling between the WPA/WMP/WOU and WTR units. If the FCM is the alarm source. INSTRUCTIONS : UltraSite. Triple-mode: 1. 2. 3. If the WAM is the alarm source.

2. 3. MetroSite 50. <line> : The Filter has detected the VSWR exceeding the defined level. Block/unblock the WSP. WAM. FAULT NAME DESCRIPTION : Unknown HW resource : A unit cannot be identified by its product code or by its physical device address (object ID). If that does not help. Block/unblock the RF Module. FlexiBTS: 1. FAULT NAME : Unit SW download failed DESCRIPTION : The software update to the unit or subunit has failed. Triple-mode: 1. connectors. replace the alarming RF Module. or the module product code is unknown. or 1. INSTRUCTIONS : Check the antenna cables. replace the alarming module. Download the BTS SW again. 2. The antenna line is slightly mismatched. 2. 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. The antenna connector information at the end of the alarm text specifies the defective antenna line. If Step 1 does not help. or 1. replace the alarming unit. Download the BTS SW again. INSTRUCTIONS : Replace the alarming unit/module.Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : Unit not supported by current BTS SW version : An unsupported unit was found in the BTS. 2. INSTRUCTIONS : UltraSite. antenna and possible 172 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . WPA: Reset the BTS. MetroSite. replace the alarming unit. If Step 1 does not help. INSTRUCTIONS : 1. INSTRUCTIONS : Replace the unit or upgrade the BTS SW. If Step 2 does not help. FAULT NAME DESCRIPTION : Unit unidentified : The permanent memory in the module is corrupted and the module product code or serial number is missing. FAULT NAME DESCRIPTION : VSWR minor alarm. FCM: Reset the BTS.

FAULT NAME DESCRIPTION : WTR internal clock faulty : The WTR internal system clock is missing. The antenna connector information at the end of the alarm text specifies the defective antenna line. 2. FAULT NAME DESCRIPTION : WAF low noise amplifier faulty : One of the two RX preamplifiers (one in the main branch and the other in the diversity branch) is faulty. The antenna line is slightly mismatched. antenna and possible antenna line devices. Block/unblock the alarming unit. FAULT NAME DESCRIPTION : VSWR alarm. INSTRUCTIONS : 1. Check the antenna line (TX-cable-antenna) impedance matching. connectors. INSTRUCTIONS : 1. Check the backplane cables and connectors (see Troubleshooting instructions). MetroSite 50: One. Check backplane cables and connectors. The reason for the failure is probably the WTR or WSMB/WMC unit. Block/unblock the WAF unit. The LED indicates the faulty unit. 3. but blocking/unblocking the unit ensures that before a site visit. If that does not help.7654 CELL OPERATION DEGRADED antenna line devices. FAULT NAME DESCRIPTION : WSMB RR-Bus error : The signal is transported from the WTR to the WSP via the WSM. Run the WCDMA BTS loop test. INSTRUCTIONS : 1. <line> : The filter has detected a VSWR value exceeding the defined level. 2. INSTRUCTIONS : 1. or a WTR unit HW failure. Check the antenna cables. This alarm is generated when the WSM/WMC unit detects errors in the incoming RR bus from the WTR unit. The unit may have been installed incorrectly or the backplane cabling is faulty. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 173 (244) . Check the antenna line (TX-cable-antenna) impedance matching. The LED indicates the faulty unit. This is most likely a HW fault. some or all of the RX preamplifiers (max 6) are faulty. replace the alarming unit. This can be caused by a missing or bad quality reference clock signal from the WSC. The transmitted and received frequencies are incorrect. 2. Replace the units indicated in the alarm one by one and check whether the problem is cleared. 2.

Replace the alarming unit. FAULT NAME DESCRIPTION : WTR power supply voltage fault : There is a fault in the power feed or RF cabling. Check the other active alarms. 3. WSP and WTR. Note! The problem can be in the unit connector. Block/unblock the WTR unit belonging to the alarming cell. FAULT NAME DESCRIPTION : WTR RT-bus fault : The bus clock signal is corrupted or missing in the RT bus. INSTRUCTIONS : 1. INSTRUCTIONS : 1. Check the WSM. or there is external interference. The signal frequency should be exactly half of the system clock frequency.Base Station Alarms (7000-7999) 3. 2. WTR backplane connectors. FAULT NAME DESCRIPTION : WTR internal clock faulty : The WTR VCXO PLL is not locked. Replace the alarming unit. See Troubleshooting instructions. 2. or the receiver might receive a wrong frequency or is not # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . external devices in the antenna line (for example MHAs) and external interference of RX band (with a spetrum analyzer). FAULT NAME DESCRIPTION : WTR local oscillator not locked : The TX IF synthesizer (common to both TX chains) cannot lock to the defined frequency. Chcek the backplane cables and connectors. This can be caused by a missing or bad quality reference clock signal from the WSC or a WTR unit HW failure. Block/unblock the WAF unit belonging to the alarming cell. The output frequency of the transmitter can be wrong or missing. Block/unblock the alarming unit. INSTRUCTIONS : 1. 2. cabinet cabling or backplane. One or more critical power supply voltages or BIAS currents are outside the allowed range. INSTRUCTIONS : 1. The transmitted and received frequencies are incorrect. connectors. Block/unblock the alarming unit. 2. FAULT NAME DESCRIPTION 174 (244) : WTR synthesizer is not locked : The TX & RX RF synthesizer or the RX IF synthesizer is not locked (or the RF synthesizer buffer amplifier is faulty). 3. Replace the alarming unit. Check the RF cabling.

Replace the alarming unit. INSTRUCTIONS : 1. the sensor is probably broken. 2. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 175 (244) . Replace the unit. INSTRUCTIONS : 1. 2. Block/unblock the alarming unit. Check the other active temperature or cooling fan-related alarms.7654 CELL OPERATION DEGRADED receiving. The system cancels the alarm automatically when the fault has been corrected. FAULT NAME : WTR temperature is high DESCRIPTION : The internal temperature of the WTR is dangerously high. Cancelling Do not cancel the alarm. If you can find no reason.

Base Station Alarms (7000-7999) 176 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

see instructions on Alarm Structure. If the site reset or unit/module block/unblock does not help. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 177 (244) .7655 CELL NOTIFICATION 33 7655 CELL NOTIFICATION Meaning A minor fault (or faults) has occurred in a unit/module (or units/modules) that belong to the sector indicated in the alarm. replace the faulty unit/module (see source of the alarm and instructions fields of the corresponding alarm). a site reset is required to cancel the alarm. Refer also to the individual alarm instructions. Check the reason for the fault from the supplementary text field of the alarm. Instructions Verify the configuration of a BTS by checking the commissioning. Supplementary information fields 1 rack (cabinet) number 2 shelf number 3 slot 4 type of unit 5 unit number 6 subunit number For more information. Make sure the environment does not cause the fault. contact the local Help Desk. the site should be reset to recover from any temporary faults. If that does not help. When an active alarm is a 'Start' alarm. Before a unit/module is replaced at the BTS. which might have caused the misbehaviour of the unit/module. cabling and correct installation of the units/modules at the BTS.

FAULT NAME DESCRIPTION : Baseband Bus failure : The FlexiBTS has detected an abnormal operation or a failure in the BTS internal baseband bus. c. Reset the RF Module by blocking/unblocking it. 178 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Check the cables between the System Module and RF Module/Extension System Module. FAULT NAME DESCRIPTION : Antenna Line Device failure : The System Module or device itself has detected an abnormal operation or a failure in the antenna line device. 4. replace the faulty parts and/or devices along the antenna line. b. replace the alarming RF Module/Extension System Module. the configuration is not valid. 2. Reset the RF Module and/or System Module. and/or check that the given parameters are in the valid range. see Nokia WCDMA BTS Alarm Descriptions (SW and release document). If the reset does not clear the fault situation. Make sure the antenna line connectors are in the right torque. Check the antenna line and antenna line devices. Reset the Extension System Module by blocking/unblocking it. 3. depending on the alarm source: a. check the compatibility between the antenna line device and BTS.Base Station Alarms (7000-7999) For more information. If the reset does not clear the fault situation. If the master System Module is the source or replacing the RF Module/Extension System Module does not clear the fault situation. Replace the RF Module. replace the alarming master System Module. INSTRUCTIONS : Check the antenna line device functionality. FAULT NAME DESCRIPTION : Antenna Line Device Operation Failure : The device is not working properly. Reset the master System Module. 4. FAULT NAME : External Filter missing DESCRIPTION : An External Filter is missing from the Antenna line. 2. or a given parameter is incorrect. INSTRUCTIONS : 1. The failure cannot be pointed to a specific module but there are several possible fault sources. Reset the alarming RF module by block/unblock. 3. Check the other active BTS alarms and act accordingly. 5. INSTRUCTIONS : Install the External Filter to the Antenna line. INSTRUCTIONS : 1.

UltraSite. Related BTS . When baseband pooling is used. If that does not help. Baseband Bus failure. Triple-mode. INSTRUCTIONS : 1. BTS baseband resources are divided between different LCGs. FAULT NAME DESCRIPTION : Incompatible SW version detected : A new unit with an incompatible SW has probably been inserted in the BTS. FAULT NAME DESCRIPTION : LCRs using same carrier frequencies mismatch in LCGs : Two cells with the same carrier belong to different local cell groups (LCGs). Metrosite. Metrosite 50: Check the SW version of the BTS and AXC. INSTRUCTIONS : 1. and update the active SW version). unless it is automatically updated by the NetAct. This alarm is reported to the BTS Site Manager only. INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version. 2. Baseband Bus failure. 3. Check the other active BTS alarms (System Module failure. Failure in optical RP3 interface and Antenna Line Device failure) and act accordingly. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 179 (244) .7655 CELL NOTIFICATION FAULT NAME DESCRIPTION : Incompatible SW version detected : A new unit/module with an incompatible SW has probably been inserted in the BTS. Check the other active BTS alarms (System Module failure. FAULT NAME DESCRIPTION : RF Module failure : The FlexiBTS has detected an abnormal operation or a failure in the RF Module internal functionality. and update compatible SW to the AXC or BTS. INSTRUCTIONS : Check the RNC parameters for the BTS cells and change them if needed.AXC interface: check the SW version of the BTS and AXC. Reset the alarming RF Module by blocking/unblocking it. INSTRUCTIONS : Update compatible SW to the BTS (check the SW versions to see the active SW version. and update the active SW version). Failure in optical RP3 interface and Antenna Line failure) and act accordingly. Softer handover requires that cells with the same frequency in different sectors need to be assigned to the same LCG. Check the cables between the System Module and RF Module. and update compatible SW to the AXC or BTS. replace the faulty RF Module. 4. unless it is automatically updated by the NetAct. FAULT NAME DESCRIPTION : RF Module failure : The FlexiBTS has detected an abnormal operation or a failure in the RF Module internal functionality.

Base Station Alarms (7000-7999) 2. MetroSite 50. INSTRUCTIONS : 1. The reason for the failure is the cable between the WSM front panels or the WSM units indicated in the alarm. 4. Check the cables between the System Module and RF Module. Triple-mode: 180 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Check the other active alarms if the WSP capacity has been decreased. Configuration error (2 different FSPs functioning) . Check the number of FSP units. FAULT NAME DESCRIPTION : WSMA SR-Bus error : UltraSite: The WSM unit has detected errors in the incoming SR bus from the adjacent WSM unit. or the cell disabling (the release of common channels) failed. The reason could be a hardware or a bus problem. Check the other active alarms. FAULT NAME DESCRIPTION : RF Module temperature value missing : The RF Module cannot report the temperature value or the sensor is faulty. INSTRUCTIONS : Check the baseband bus configuration parameters from the commissioning file. 2. Reset the alarming RF Module by blocking/unblocking it. Block/unblock the RF Module.after acknowledgement the fault will return again. If that does not help. If that does not help. Triple-mode: 1. 2. Check if there are enough WSP units. Flexi BTS: 1. MetroSite. 2. replace the faulty RF Module. FAULT NAME DESCRIPTION : Timestamp mismatch in summing : Timestamp mismatch in the BB summing. Data corruption on the bus . or a lack of DSP or ATM resources. replace the alarming RF Module.appears once when unsynchronised data is sent by the BB. INSTRUCTIONS : UltraSite. 3. FAULT NAME DESCRIPTION : Telecom cell enabling or disabling failed : The cell enabling (the setup of CPICH and BCH) failed.

3. Replace the alarming unit. 2. 2. Replace the WSM units (and if that does not help. The reason for the failure is the WSM or WTR unit. also the WTR units) indicated in the alarm one by one and check whether the alarm is cleared. FAULT NAME DESCRIPTION : WTR synthesizer is not locked : The TX & RX RF synthesizer or the RX IF synthesizer is not locked (or the RF synthesizer buffer amplifier is faulty). or the receiver might receive a wrong frequency or is not receiving. Replace the alarming unit. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 181 (244) . Check the WSM cabling. Try to perform the loop test again. INSTRUCTIONS : 1. Remove/reinsert the alarming unit. or the cable between the WSM front panel and the backplane.7655 CELL NOTIFICATION The WSM has detected errors in the incoming SR bus from the WTR unit. The transmitter output signal is not downconverted to the receiver frequency. 2. Block/unblock the alarming unit. Check the other WSM units. INSTRUCTIONS : 1. FAULT NAME DESCRIPTION : WTR loop synthesizer not locked : The RF loop does not function. This alarm is generated only once and is reported to the BTS Site Manager only. The output frequency of the transmitter can be wrong or missing. The system cancels the alarm automatically when the fault has been corrected. 4. 3. Block/unblock the alarming unit. INSTRUCTIONS : 1. Cancelling Do not cancel the alarm.

Base Station Alarms (7000-7999) 182 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Check the reason for the fault from the supplementary text field of the alarm. Instructions See relevant BTS product release documentation for details about BTS licence management. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 183 (244) .7660 BASE STATION LICENCE EXPIRED 34 7660 BASE STATION LICENCE EXPIRED Meaning A licence fault (or faults) has occurred in the base station. The system cancels the alarm automatically when the fault has been corrected. Cancelling Do not cancel the alarm. see instructions on Alarm Structure. Supplementary information fields 1 rack (cabinet) number 2 shelf number 3 slot 4 type of unit 5 unit number 6 subunit number For more information.

Base Station Alarms (7000-7999) 184 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Instructions See relevant BTS product release documentation for details about BTS licence management. Supplementary information fields 1 rack (cabinet) number 2 shelf number 3 slot 4 type of unit 5 unit number 6 subunit number For more information. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 185 (244) . see instructions on Alarm Structure.7661 BASE STATION LICENCE NOTIFICATION 35 7661 BASE STATION LICENCE NOTIFICATION Meaning A licence fault (or faults) has occurred in the base station. <licenceName> : The HW capacity is too low to support all licences of an optional feature. Check the reason for the fault from the supplementary text field of the alarm. INSTRUCTIONS : Delete the licences or insert new hardware. FAULT NAME DESCRIPTION : HW capacity too low for feature <licenceCode>.

186 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . <licenceName> : The BTS detected a resource requiring a licence but no licence exists or is free. The system cancels the alarm automatically when the fault has been corrected. Cancelling Do not cancel the alarm.Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : Licence missing <licenceCode>. INSTRUCTIONS : An appropriate licence should be activated or the licence amount should be increased.

Encapsulation is used because RNC alarm system cannot support the FT alarms directly due to differences in alarm structure. see the instructions on Alarm Structure. Supplementary information fields 1 probable cause reported by FT taken from 3GPP 2 the managed object reported by FT 3 alarm number reported by the FT. Check the reason for the fault from the supplementary information fields and supplementary text field of the alarm. The FT has reserved alarm numbers from space 61000 .7665 BASE STATION TRANSMISSION ALARM 36 7665 BASE STATION TRANSMISSION ALARM Meaning A transmission fault (or faults) has occurred in the Nokia WCDMA Flexi Base Station. This means that the alarm number. The actual documentation for the encapsulated alarm can be found in Alarms for FTM document. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 187 (244) . This alarm is an encapsulation alarm that is used to transfer the Flexi Transport Submodule (FT) alarm data over BTS O&M connection through RNC to Nokia NetAct. Follow the instructions given in the Alarms for FTM for the alarm number shown in the supplementary information field 3. alarm text and supplementary information are shown in original FT format and the alarm printout is thus different in Nokia NetAct compared to alarm listings in RNC local user interfaces.61999. Instructions This alarm is an encapsulation alarm for original FT alarm. In Nokia NetAct this alarm is shown in opened format. For more information.

Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : AIS (Administrative Unit) on unit $U. FAULT NAME DESCRIPTION 188 (244) : BTS reset required : A change to the BTS IP settings has been received from TRS Manager. interface $IF : Alarm indication signal on the Administrative Unit. All other transmission alarms related to this signal are suppressed. The SDH interface receives an MS-AIS (Multiplexer Section . The user has to confirm the changes after the last BTS IP settings have been given. The SDH interface receives an AU-AIS (Administrative Unit . INSTRUCTIONS : Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. All other transmission alarms related to this signal are suppressed. FAULT NAME DESCRIPTION : AIS (Multiplexer Section) on unit $U. The confirmation is needed so that the BTS IP settings are taken in use through a BTS reset.Alarm Indication Signal). Probable cause: there is a transmission problem somewhere in the intermediate network and AIS is sent instead of the user traffic. interface $IF : Alarm indication signal is received. Probable cause: There is a transmission problem somewhere in the intermediate network and AIS is sent instead of the user traffic. INSTRUCTIONS : Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. This signal is generated by an intermediate PDH device in the forward direction because it detects a problem in its receive signal. interface $IF : Alarm indication signal on the Multiplexer Section. 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.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. FAULT NAME DESCRIPTION : AIS on unit $U. # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . This signal is generated by an intermediate SDH device in the forward direction because it detects a problem in its receive signal.

Check that the connectors are properly connected to the unit. The alarm is # Nokia Siemens Networks 189 (244) . The measured bit error rate exceeds the threshold value of BER-3 (10E-3). Follow the signal in the network and check whether any other alarms concerning the fault are on (such as Laser End of Life). All other transmission alarms related to this signal are suppressed. IMA Group $IMAG : Far end group start-up. IMA version and frame length). 2. IMA Group $IMAG DESCRIPTION : Configuration abort state. Change the configuration. INSTRUCTIONS : Check that the configurations at the near end and far end fit together (for example. if necessary.the signal level is too low (optical connectors or cables are dirty. FAULT NAME DESCRIPTION : EBER on unit $U. All other transmission alarms related to this signal are suppressed. electrical connectors or cables are corroded) . If this is the case. This alarm is raised when the far end tries to use unacceptable configuration parameters. 4. This alarm is raised when the far end indicates that it is in the start-up phase. interface $IF : Excessive bit error rate. FAULT NAME : Config-abort state on unit $U. Change the configuration if necessary. FAULT NAME DESCRIPTION : Far end config-abort state on unit $U. IMA Group $IMAG : Far end configuration abort state. follow the instructions for handling those alarms. This alarm is raised when the far end reports unacceptable configuration parameters.the receiver or the far end transmitter has failed INSTRUCTIONS : 1. the IMA versions are incompatible). INSTRUCTIONS : Check that the configurations at the near end and far end fit together (for example. FAULT NAME DESCRIPTION DN99580892 Issue 6-3 en 12/06/2008 : Far end group start-up on unit $U. the IMA versions are incompatible).the connector is not properly connected to the unit . IMA version and frame length). Probable causes: . Check that the cable connected to the interface in question is not damaged and it is within the specifications.7665 BASE STATION TRANSMISSION ALARM INSTRUCTIONS : Confirm the changes when all the required BTS IP settings have been made. 3. Clean the cables and connectors. Probable cause: The IMA group configuration is wrong (for example.the specified maximum length of the cable is exceeded . Probable cause: The IMA group configuration is wrong (for example.

FAULT NAME DESCRIPTION : Far-end transmit link unusable on unit $U. If the alarm stays active. FAULT NAME DESCRIPTION : Far end insufficient links on unit $U. correct them. IMA Group $IMAG : Far end insufficient links. reduce the minimum number of IMA links in the IMA group. The alarm is typically raised only temporarily during IMA configuration and it disappears when the configuration has been completed. 3. The IMA link is not yet in an IMA group. interface $IF : Far-end transmit link unusable. 4. 2. Change the configurations if necessary. check whether any other alarms related to this fault are on (such as problems on individual IMA links). Check that the configurations at the near end and far end fit together. Probable cause: IMA configuration is incomplete at the far-end interface. Probable cause: IMA configuration is incomplete.Base Station Alarms (7000-7999) typically active only temporarily. Probable causes: . If feasible. INSTRUCTIONS : Ensure that the far-end IMA link is configured to be part of an IMA group. Configure additional IMA links to the IMA group. Check the individual IMA links in the IMA group for problems. INSTRUCTIONS : Ensure that the IMA link is configured to be part of an IMA 190 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . There are usually other IMA-related alarms active at the same time. If this is the case. interface $IF : Far-end receive link unusable. Probable cause: The IMA group at the far end is not yet up and running. There are usually other IMA-related alarms active at the same time. The alarm is typically raised only temporarily during IMA configuration and it disappears when the configuration has been completed.IMA links within the IMA group are out of order .the value for the parameter Minimum number of links is set to be too high INSTRUCTIONS : 1. The far-end IMA group reports that there are less IMA links in the far-end IMA group than required by the parameter Minimum number of IMA links. no action is needed. The IMA link is not yet in an IMA group. INSTRUCTIONS : If the alarm is on only temporarily. If needed. FAULT NAME DESCRIPTION : Far-end receive link unusable on unit $U. follow the instructions for handling these alarms.there are not enough IMA links configured for the IMA group .

2. Take appropriate actions to reduce the delay. do as follows: 1. The far-end transmit clock mode is different from the near-end transmit clock mode. FAULT NAME DESCRIPTION : Five failed logins to FTM due to wrong user name or password : Five consecutive failed login attempts to the FTM have been performed. IMA Group $IMAG : Group timing mismatch. FAULT NAME DESCRIPTION : IMA link $IF : Link out when the links in delay. In this case. The far-end transmit clock mode is different from the near-end transmit clock mode. out of delay synchronization on unit $U. INSTRUCTIONS : Check your username and password. Check the delay of the IMA link in question. the problem might be located in the leased line network. INSTRUCTIONS : The IMA group reconfigures automatically. The IMA group might not be capable of carrying traffic on the IMA group referenced in the alarm text. If the alarm remains active. Check the physical line for errors. Special measurement equipment might be needed for this. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 191 (244) . The traffic of the IMA group does not function properly. the operator should be contacted. Probable cause: Too large differential delay between the IMA links. interface of delay synchronisation. FAULT NAME DESCRIPTION : Group timing mismatch on unit $U. The traffic of the IMA group does not function properly.there is disturbance on the line INSTRUCTIONS : Do as follows for the interface referenced in the alarm text: 1.7665 BASE STATION TRANSMISSION ALARM group. If necessary. IMA Group $IMAG : Group timing mismatch. 3. A LODS defect is reported link differential delay between the link and the other the group is higher than the tolerable link differential Probable causes: . The IMA group might not be capable of carrying traffic on the IMA group referenced in the alarm text. 2. Verify that the IMA configuration of the near end and far end is correct. If the IMA link is used over a leased line.the configuration of the IMA group is incomplete or faulty . FAULT NAME DESCRIPTION : Group timing mismatch on unit $U. Check the delay of the links.

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. interface $IF : Link out of delay synchronisation.loss of IMA frame . select another suitable link. 2.physical link defect . A Loss of IMA link (LIF) or Link out of delay synchronisation (LODS) alarm is active at the far end of the IMA link.loss of IMA frame .the differential delay of the IMA links belonging to one IMA group is too high INSTRUCTIONS : Do as follows for the interface referenced in the alarm text: 1. interface $IF : Remote failure indication. 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: . FAULT NAME DESCRIPTION : IMA remote failure indication on unit $U.the configuration of the IMA group is incomplete or faulty . interface $IF : Remote failure indication. Verify that the IMA configuration of the near end and far end is correct. If necessary. Probable causes: . Check the physical line for errors.disturbance on the line .Base Station Alarms (7000-7999) select another appropriate link. FAULT NAME DESCRIPTION : IMA remote failure indication on unit $U.loss of delay synchronisation INSTRUCTIONS : Follow the instructions for handling the alarms raised at the far end of the IMA link.disturbance on the line . FAULT NAME DESCRIPTION : IMA link out of delay synchronization on unit $U.link out of delay synchronisation INSTRUCTIONS : Follow the instructions for handling the alarms raised at the far end of the IMA link. 192 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 3. Check the delay of the IMA link in question. An IMA-related remote defect has been detected. Probable causes: .there is disturbance on the line .physical link defect .

follow the instructions on handling those alarms.there are disturbances in the traffic of the physical transmission link in question INSTRUCTIONS : 1. Ensure that the far end is using ATM cell mapping. 4.the far-end frames do not have ATM cell mapping . DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 193 (244) . INSTRUCTIONS : Download a valid licence to the WBTS. Change the configurations if necessary. 2. This opens the loop which cancels the alarm.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 . Check that the configurations at near end and far end fit together. There are less operable IMA links in the IMA group than the minimum number of IMA links required. Check whether any other alarms concerning the fault are on. Probable causes: . It is not possible to carry traffic on the interface referenced in the alarm text. The network interface receives frames whose ATM cells cannot be recognised. interface $IF : Loss of ATM cell delineation.the value for the parameter Minimum number of links is set to too high INSTRUCTIONS : 1. 3. If this is the case. Probable cause: A valid licence that would allow the operation of the feature is not available in the WBTS. FAULT NAME DESCRIPTION : LOCD on unit $U. Configure additional IMA links to the IMA group. INSTRUCTIONS : Switch the loopback off or wait for the timeout to expire.the far end does not insert idle cells . Check the individual IMA links in the IMA group for problems. interface $IF for $T minutes DESCRIPTION : A loopback has been configured by a management application.7665 BASE STATION TRANSMISSION ALARM FAULT NAME DESCRIPTION : Insufficient links on unit $U. If feasible. IMA Group $IMAG : Insufficient links. The IMA group referenced in the alarm text may not be able to carry all required traffic. FAULT NAME : Interface under test on unit $U. 2. Probable causes: . Correct them if necessary. FAULT NAME DESCRIPTION : Licence missing for feature $feature on interface $if : The feature referenced in the alarm text has been configured without installing a valid licence. reduce the minimum number of IMA links in the IMA group.

Probable cause: there are disturbances in the traffic on the link in question. All other transmission alarms related to this signal are suppressed. JT1 interfaces: Check that the interface type of the far-end interface is also configured to be a JT1 interface. interface $IF : Loss of frame. interface $IF : Loss of Pointer for the Administrative Unit. no action is needed. reconfigure the interfaces so that they match each other. All other transmission alarms related to this administrative unit are suppressed. interface $IF : Loss of multiframe. If this is the case. Probable causes for STM-1/STS-3c interfaces: .the SDH/SONET interface receives frames that have an incorrect frame pattern (A1 and A2 bytes) . If this is not the case. It is not possible to carry traffic on the interface referenced in the alarm text. The interface referenced in the alarm text lost the multiframe alignment. Probable cause for JT1 interfaces: The interface at the far end is not configured to be a JT1 interface. FAULT NAME DESCRIPTION : LOF on unit $U. INSTRUCTIONS : Check the intermediate VC-12 transmission network for alarms indicating the root cause and follow the instructions for 194 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . reconfigure the interfaces so that they match each other. If this is not the case. If the alarm is on only temporarily. For E1 interfaces. INSTRUCTIONS : E1 interfaces: Check that the interface type of the far-end interface is also configured to be a framed E1 interface. This alarm occurs when the SDH interface receives frames that have an incorrect Administrative Unit (AU) pointer.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 . the configuration of the far-end node must be E1 Multiframe. the problem is somewhere in the transmission network. FAULT NAME DESCRIPTION : LOP (Administrative Unit) on unit $U. Probable cause: the interface type is not configured to meet the framing of the interface at the far end.too low input level Probable cause for E1 interfaces: The interface at the far end is not configured to be a framed E1 interface.Base Station Alarms (7000-7999) 3. INSTRUCTIONS : Check that the configured interface type matches the configured interface type of the far end. FAULT NAME DESCRIPTION : LOMF on slot $U.

All other transmission alarms related to this signal are suppressed. connect a loop cable and check whether the alarm disappears.a cable is cut or there is no cable connected to the interface .the electrical signal is excessively attenuated . Check that the interface at the far-end interface is switched on. 2. To verify that the hardware of the interface unit works correctly.the electrical signal is excessively attenuated .a cable is cut or there is no cable connected to the interface . 2. follow the instructions for handling those alarms. connect a loop cable and check whether the alarm disappears.the port at the connected far-end node is switched off . Probable causes for PDH interfaces: . To verify that the hardware of the interface unit works correctly.transmit and receive cables are mixed up INSTRUCTIONS : 1.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 . interface $IF : No signal is received on the interface referenced in the alarm text. Check that the interface at the far-end interface is switched on. Probable causes for PDH interfaces: . If there are.the port at the connected far end node is switched off INSTRUCTIONS : 1. Check that the cables are connected to the correct connectors. follow the instructions for handling those alarms. FAULT NAME DESCRIPTION : LOS on unit $U.the electrical signal is excessively attenuated . 4. Check whether there are active alarms at the far end. All other transmission alarms related to this signal are suppressed. Check whether there are active alarms at the far end. 4. 3. [ethernet] interface $IF : No signal is received on the interface referenced in the alarm text.the port at the connected far-end node is switched off . If there are.7665 BASE STATION TRANSMISSION ALARM handling these alarms. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 195 (244) . FAULT NAME DESCRIPTION : LOS on unit $U. Check that the cables are connected to the correct connectors. 3.

FAULT NAME DESCRIPTION : Pseudowire $PW down in ingress direction on unit $U. interface $IF : Path Payload Label Mismatch on the High Order Path. FAULT NAME 196 (244) : RDI (High Order Path) on unit $U. All other transmission alarms related to this IMA link are suppressed. interface $IF : Loss of an IMA frame. FAULT NAME DESCRIPTION : Pseudowire $PW down in egress direction on unit $U : A Pseudowire has been detected to be down in the egress direction by using the BFD function. INSTRUCTIONS : Check that the Pseudowire configuration is complete.there is disturbance on the line INSTRUCTIONS : Do as follows for the interface referenced in the alarm text: 1. Probable causes: .the configuration of the IMA group is incomplete or faulty . : The Pseudowire has been detected to be down in the ingress direction by using the BFD function.Base Station Alarms (7000-7999) FAULT NAME DESCRIPTION : Loss of IMA frame on unit $U. INSTRUCTIONS : Ensure that the path payload label for the VC-3/VC-4 at the far end is configured to be "ATM". INSTRUCTIONS : Insert a valid SFP module. FAULT NAME DESCRIPTION : PLM (High Order Path) on unit $U. 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 far-end IMA link is not part of an IMA group. 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. interface $IF # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . FAULT NAME : No inserted or non-compliant SFP module on unit $U. The loss of an IMA frame was detected in one link of the IMA group. 2. interface $I DESCRIPTION : The SFP module detected in the interface connectors does not comply with the security requirements. Verify that the IMA configuration of the near end and far end is correct. 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". Check the physical line for errors. INSTRUCTIONS : Check that the Pseudowire configuration is complete.

It is sent by the intermediate or the far end equipment. connect a loop cable and check that LOS alarm is not raised. LOP-AU. Probable cause: The far end has a LOS. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. TIM-HP. UNEQ-HP). LOF.7665 BASE STATION TRANSMISSION ALARM DESCRIPTION : Remote defect indication on the High Order Path (VC-3/VC-4). because it detects a serious fault in the received signal. 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. connect a loop cable and check that LOS alarm is not raised. 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. FAULT NAME DESCRIPTION : RDI on unit $U. FAULT NAME DN99580892 Issue 6-3 en 12/06/2008 : STC connection to signalling peer not established on interface $ # Nokia Siemens Networks 197 (244) . 2. LOF or AIS alarm on its receiving interface. To check the transmit hardware. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. Check the intermediate transmission network for alarms indicating the root cause and follow the instructions for handling these alarms. The RDI indicates a serious fault in the received signal of the far-end equipment. 2. To check the transmit hardware. To check the transmit hardware. The far-end equipment signals this remote defect in the signal that it transmits. interface $ÍF : Remote defect indication (RDI) on the Multiplexer Section (MS). Probable cause: The far end has active alarms on its receiving interface (such as LOS. INSTRUCTIONS : 1. INSTRUCTIONS : 1. AIS-AU. AIS-AU. TIM-RS. interface $IF : Remote defect indication. 2. TIM-RS. This alarm occurs when the equipment at the far end of a bidirectional multiplexer section connection detected an error condition on the receiving signal. INSTRUCTIONS : 1. AIS-MS. FAULT NAME DESCRIPTION : RDI (Multiplexer Section) on unit $U. connect a loop cable and check that no alarms appear for this interface. LOF. LOP-AU). AIS-MS.

FAULT NAME DESCRIPTION : Synchronisation lost : Primary and secondary timing source lost. Check the AAL2 configuration. the WBTS switches automatically to the next clock source in the priority list. 3.problem on the ATM layer . 3.problem on the physical layer . Check that the RNC is up and running. port. 2. Check that there are no other alarms on physical or ATM layer active. The reason can be alarms on the interfaces (for example.incomplete or faulty configuration of AAL2 in the RNC INSTRUCTIONS : 1. VPI and VCI number in question. make sure that the VP/VC used for an AAL2 signalling link match between the RNC and WBTS.the link goes down because the peer (RNC) does not respond within the TIMER_NO_RESPONSE period.the peer (RNC) releases the connection .the link was never established .problem on ATM layer . Check that the RNC is up and running.the link goes down because the peer (RNC) does not respond within the TIMER_NO_RESPONSE period.problem on physical layer . LOF or AIS). 2. Probable cause: The transmission links selected for clock source are faulty. LOS. . For example. INSTRUCTIONS : Use the BTS Site Manager to check which interfaces have been configured as synchronization sources. Probable causes: . 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.Base Station Alarms (7000-7999) DESCRIPTION : The SSCOP link controlled by this STC is down. FAULT NAME DESCRIPTION : STC connection to signalling peer not established on interface $ : The SSCOP link controlled by this STC is down.incomplete or faulty configuration of AAL2 in RNC INSTRUCTIONS : 1. Check the AAL2 configuration.the peer (RNC) releases the connection . On failure. For example. Check that there are no other active alarms on the physical or ATM layer. The alarm text specifies the slot. make sure that the VPs/VCs used for AAL2 signalling in the RNC and WBTS match. 198 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Probable causes: . .the link was never established .

interface $IF : High Order Path Unequipped. Probable cause: The transmission link selected for the clock source is faulty. To verify that the hardware of the interface unit works correctly. and BIP-8 byte (B3) in the SDH path overhead (POH) have zero value. the path trace byte (J1). If there are. All the path signal label byte (C2). 2. FAULT NAME DESCRIPTION DN99580892 Issue 6-3 en 12/06/2008 : UNEQ (High Order Path) on unit $U. Check whether the interface at the far end is switched on. Check that the cables are connected to the correct connectors. If there are. LOF. The reason can be alarms on the interface (for example. follow the instructions on handling those alarms. If the primary clock source is lost. For the PDH interfaces. To verify that the hardware of the interface unit works correctly. 4. 3. connect a loop cable and check whether the alarm disappears. One of the synchronisation sources in the configured priority list is unavailable. follow the instructions on handling those alarms. Check whether there are active alarms at the far end. LOS. If the secondary clock source is lost. do as follows: 1. AIS or EBER). FAULT NAME : The FTM booted at $date due to $RCause DESCRIPTION : The transport part of the WBTS has been reset. a switch to the secondary source occurres. 4. # Nokia Siemens Networks 199 (244) . connect a loop cable and check whether the alarm disappears. Check whether there are active alarms at the far end. do as follows: 1. 2. INSTRUCTIONS : N/A FAULT NAME DESCRIPTION : Timing source lost on unit $U. Check whether the interface at the far end is switched on. The path is unusable for traffic transport. INSTRUCTIONS : Use Nokia BTS Site Manager to check which interfaces are configured as synchronization sources. interface $IF : Primary or secondary timing source is lost. Check that the cables are connected to the correct connectors. 3. the WBTS switches to the internal clock in case the primary clock source fails.7665 BASE STATION TRANSMISSION ALARM For the PDH interfaces.

follow the instructions for handling those alarms. INSTRUCTIONS : 1. 200 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 2. Follow the signal in the network and check whether any other alarms concerning the fault are active. Check the configuration and ensure that the cross-connections between the nodes are properly configured for transporting traffic.Base Station Alarms (7000-7999) 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. The system cancels the alarm automatically when the fault has been corrected. Cancelling Do not cancel the alarm. Ensure that the Path Payload Label for the VC-3/VC-4 at the far end is configured to be "ATM". If this is the case. 3.

The same radio network object is the object of both this alarm and the beating alarm that caused this alarm. and has thus been filtered by the alarm system. The system cancels the alarm automatically when the fault has been corrected. it is indicated here. always during informing or cancelling delay. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 201 (244) . You can find the number of that alarm in Supplementary information field 1. Instructions Correct the fault that caused the original beating alarm. Additional information is cut after 14 bytes and it is represented in hexadecimal format. Cancelling Do not cancel the alarm. Supplementary information fields 1 the alarm number of the beating BTS alarm 2-15 if the beating alarm has any additional information.7740 BEATING WCDMA BTS ALARM 37 7740 BEATING WCDMA BTS ALARM Meaning The same radio network alarm has changed its alarm state (start/cancel) 20 times consecutively.

Base Station Alarms (7000-7999) 202 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

HW configuration request and WBTS restart) cannot be performed in case of Iub O&M connection problem. It is also not possible for the WBTS to report its alarms to RNC.g.7750 FAILURE IN WCDMA WBTS O&M CONNECTION 38 7750 FAILURE IN WCDMA WBTS O&M CONNECTION Meaning This alarm indicates that a failure has occurred in WBTS O&M connection. SW download. the availability of WBTS O&M functionality may be limited. The states of the user plane links can be checked using RNC RNW Object Browser. User initiated or automatic O&M tasks (e. In Iub connection problem between RNC and WBTS this alarm is set by OMU unit in following situations: 1) WBTS has closed the O&M connection 2) WBTS O&M connection supervision message has not arrived within expected time 3) there is a problem in transmission network between RNC and WBTS 4) a WBTS id conflict has been detected in the network As a consequence of this alarm. in internal communication of RNC applications or in WBTS configuration. Supplementary information fields 1 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. The problem is related to Iub connection between RNC and WBTS. This alarm does not indicate a failure in WBTS user plane links. This field is DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 203 (244) . From RNC point of view the actual reason for the failure is either in transmission network between network elements (Iub).

Error reason = 1. If connection does not recover in couple of minutes. The connection is closed and the RNC is waiting for the new O&M connection opening from the WBTS. failure in the WBTS connection Error code: 14005 = CONNECTION RESET BY PEER WBTS has closed connection. Maintenance Manual) or from the document General Error Messages of System. But when the RNC attempted to receive data from this O&M connection.Base Station Alarms (7000-7999) 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. 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. 204 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . If configuration is ok. Error code: 13951 = NO DATA RECEIVED RNC queried the O&M connection to the WBTS and it found that there is some data to be received. Wait until WBTS opens new connection and system cancels the alarm. no data was received. Error code (field 2) indicates what caused the problem if the error reason (field 1) value is 1. check that WBTS is configured correctly to RNC and to Network. Supplementary References Instructions Error reason (field 1) indicates which part of the connection the problem is located. wait until WBTS opens new connection and system cancels the alarm.

7750 FAILURE IN WCDMA WBTS O&M CONNECTION

Wait until the system cancels the alarm.

Error code:
154 = TIME LIMIT EXCEEDED IN MESSAGE WAITING
WBTS supervision timer has expired. Connection is closed and
RNC is waiting new O&M connection opening from WBTS.
Wait until system cancels the alarm.

Error
14001
14011
14015

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

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

Error code:

DN99580892
Issue 6-3 en
12/06/2008

# Nokia Siemens Networks

205 (244)

Base Station Alarms (7000-7999)

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
This error code is used if OMU unit switchover has occurred in
the RNC and O&M connection to the WBTS has been closed because
of that. The WBTS O&M connections are always handled by the
OMU unit in WO-EX state so in switchover case the connections
are closed.
Wait until WBTS opens the O&M connection again and system
cancels this alarm.
Any other error code:
Contact the local Nokia Customer Service Center.

Error reason = 2, WBTS id conflict
More than one WBTS has been configured with the same id.
Error code:
255 = UNSUCCESSFUL
An O&M connection for a WBTS id already exists in the RNC.
This alarm was set because the same WBTS id was used in
new O&M connection establishment from a different IP address
that already existing connection was established from. This
happens if several WBTS have been configured with the same
WBTS id under the same RNC.
The supplementary text of alarm gives IP address of the
conflicting WBTS.
Use BTS Manager to connect the conflicting WBTS with its IP,
configure it with a different id. Depending on the WBTS
release, the reconfiguration may need to be done using AXC
Manager.
Cancel the alarm manually after resolving the WBTS id
conflict.

206 (244)

# Nokia Siemens Networks

DN99580892
Issue 6-3 en
12/06/2008

7750 FAILURE IN WCDMA WBTS O&M CONNECTION

Cancelling

Do not cancel the alarm with error reason 1. The system cancels
the alarm automatically when the fault has been corrected.
The alarm with error reason 2 must be canceled manually.
Error reason = 1
Alarm will be canceled when BTS O&M connection is working again.
Error reason = 2
Alarm must be canceled manually with MML command AAN or with
Fault Management application in RNC Element Manager after
conflicting WBTS id situation is corrected.

DN99580892
Issue 6-3 en
12/06/2008

# Nokia Siemens Networks

207 (244)

Base Station Alarms (7000-7999)

208 (244)

# Nokia Siemens Networks

DN99580892
Issue 6-3 en
12/06/2008

Common channel supervision . WCEL creation with RNC Object Browser or by plan. for example common channel supervision.Dedicated measurement initiation These scenarios can be a consequence of either user operation or operation performed by the system. In general all failures causes the cell (s) to be blocked and hence unavailable to traffic.RNC restart . User operation can be.WBTS capability information updating .Connection configuration (COCO) management .forced handover . Failure in WBTS capability updating or pid updating can cause incorrect WBTS capability data to be used in the RNC and thus problems in signalling or actual calls.WBTS initialization or WBTS reset .modification of configuration data .7761 RNW O&M SCENARIO FAILURE 39 7761 RNW O&M SCENARIO FAILURE Meaning The alarm indicates a failure in some of the following scenarios: .pid data updating (storing the process id of the telecom process which is responsible of managing the WBTS/WCELL in question) . Failure in User plane configuration (AAL2 path unblocking) causes a situation where the User plane traffic can not be transferred in the corresponding AAL2 VCC.Iu service barring . DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 209 (244) . for example. Failure in cell blocking can lead to erroneous cell state information in the RNC.Cell deletion .cell initialization.Audit handling . Operations performed by the system are in most cases related to recovery operations.WBTS recovery (system initiated COCO disconnect/connect operation) . activation or blocking .Common measurement supervision .

only 3GPP iub Cell deletion procedure has failed. only 3GPP iub Common measurement initiation has failed. Nokia iub Cell unlocking. only 3GPP iub Common or RRI measurement termination failed. 3GPP iub WBTS cell block. 3GPP iub Cell reconfiguration. Nokia iub RNC restart. 3GPP iub WBTS cell unblock. 3GPP iub Common measurement supervision Dedicated measurement initiation # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 3GPP iub WBTS initialization. 3GPP iub Cell unlocking. Nokia iub Configuration data modification. only 3GPP iub Cell setup procedure has failed. only 3GPP iub Cell reconfiguration procedure has failed. Nokia iub Local cell resource state change Forced handover WBTS reset initiation from RNC WBTS capability information update Pid update Connection configuration management Audit handling. 3GPP iub WBTS restart. 3GPP iub Resource status indication handling. only 3GPP iub RRI measurement initiation has failed.Base Station Alarms (7000-7999) Supplementary information fields 1 reason for the failure 01 02 03 04 05 06 07 08 09 0A 0B 0E 11 12 13 14 15 16 18 19 20 21 2 WBTS reservation has failed Configuration data updating has failed Inactivation of the cell has failed Activation of the cell has failed Common channel deletion has failed Common channel creation has failed BCCH information updating has failed WBTS capability information was not received Forced handover request was not accepted WBTS capability information update has failed AAL2 path unblocking has failed Unknown NBAP interface type Audit has failed. 3GPP iub CCH Supervision WBTS recovery Iu service barring Cell deletion. only 3GPP iub Cell barring has failed COCO disconnect has failed COCO connect has failed scenario that was being carried out when the failure occurred 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 81 82 83 84 8D 8E 8F 90 91 92 210 (244) Not specified WBTS initialization. 3GPP iub RNC restart.

-> If WBTS O&M connection is OK. If it is active indicating that there is something wrong with WBTS O&M connection (Iub). FFFF 6 Not specified Not specified virtual channel identifier. This field is significant only in case of User plane configuration fault. This field is significant only in case of User plane configuration fault. -> If WBTS O&M connection between RNC and WBTS is not OK. FFFF 5 virtual path identifier. Maintenance Manual) or from the document General Error Messages of System. Abbreviation SIF refers to supplementary information field. Step 2: In case the value of SIF 2 is 0A (Connection configuration management). then reset command cannot be sent from RNC to WBTS. Step 1: In case the value of SIF 2 (scenario) is 07 (WBTS reset): .Check that ATM resources related to COCO are not locked. The first four steps are specific to certain failure situations.Check also if alarm 7750 FAILURE IN WCDMA BTS O&M CONNECTION is active for this WBTS. .7761 RNW O&M SCENARIO FAILURE 3 general error code of the system You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials. This field is significant only in case of User plane configuration fault. Supplementary References 4 ATM interface identifier of network external or internal interface. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 211 (244) . It is also a default procedure to be performed if instructions given in previous steps do not solve the problem. 0 Not specified Instructions This instruction contains five main steps. It should match the configuration of the RNC. try to solve the situation with BTS Manager by examining the WBTS alarms and logs. The last step is a general operating procedure for all other failures indicated by this alarm. .First. retry to reset WBTS with RNC Object Browser.Check the configuration of the corresponding WBTS node using BTS Manager. verify using RNC Object Browser that WBTS id is valid in the system and COCO is connected to WBTS. and the value of the SIF 1 is 0B (AAL2 path unblocking has failed): .

or . WCDMA BTS DEDICATED MEASUREMENT FAILURE should be active. These operations clear and again init the BTS related resources: .Reset the WBTS with RNC Object Browser. act according to general operating instructions in step 3 below.Unlock the ATM-interface with MML command ZLAS and VP/VC with MML command ZLCS if needed.g. Step 5: General operation instructions for all other failure reasons: Wait a couple of minutes. Step 4: In case the SIF 2 value is 92 (Dedicated measurement initiation): . In case the alarm is still active after lock/unlock cell operation. . COCO creation. .50B. Follow the instructions given for that alarm. the related COCO id can be found from OMU computer log by searching for process family 50B writings (ZGSC:.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). disconnect the COCO manually using RNC RNW Object Browser by removing the WBTS id from the corresponding COCO object. system tries to recover from the problem by retrying the failed operation again and the alarm may be cancelled automatically.Base Station Alarms (7000-7999) Locked ATM resources will prevent the connection configuration operations.) that contain the also the WBTS id that this alarm is targeted to. .If this alarm was generated due to user initiated action. If COCO id related to this WBTS is not known. . . e. 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): . try to lock and then unlock the cell with RNC Object Browser manually.In case of COCO disconnect failure.In case of COCO connect failure.If configuration is correct and ATM resources are unlocked.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 212 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . Wait at least for 15 seconds and connect the COCO again by restoring the WBTS id to COCO object. try to connect the COCO again to the WBTS using RNC RNW Object Browser.Alarm 7778. In case the alarm is not cancelled due to system recovery while waiting. some of the following actions can be tried (each of these causes the WBTS to be unavailable during the operation). This causes the system to try to clear possible hanging cell related resources and then recreate (init) them. try to perform the operation again.

. The system cancels the alarm automatically when the fault has been corrected. 4FA. 4B7) during BTS reset Also RNC reset might help the situation if it is possible to be performed.OMU computer log. collect at least the following logs and contact the local Nokia Customer Service Center: . 4FD. Maintenance Manual) or from the document General Error Messages of System. More information about the exact failure reason can be found by examining the supplementary info field 3 (error code). You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials.7761 RNW O&M SCENARIO FAILURE manager. Cancelling Do not cancel the alarm. Supplementary References. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 213 (244) . monitor families 4FE. It can be studied with MML-command ZDDE::"ZGSC".message monitoring from OMU (families 50B. and no obvious reason behind it can be found. In many cases there is also more information in OMU computer log. 4EE and 4EF) and serving ICSU (check serving ICSU from COCO data in RNC Object Browser. 4FB. If the alarm still remains active after the steps above.

Base Station Alarms (7000-7999) 214 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

Storing the WBTS capability information .RNC restart .7762 RNW DATABASE OPERATION FAILURE 40 7762 RNW DATABASE OPERATION FAILURE Meaning RNW database operation has failed. this failure has lead to a situation where cell state could not be modified from blocked to working state or vice versa in RNC or it was not possible to send configuration data to WBTS.Storing the pids .WBTS initialization .Cell blocking .Storing cch parameters . Supplementary information fields 1 specifies if the error occurred during reading from or writing to database 01 02 DN99580892 Issue 6-3 en 12/06/2008 Reading failure Writing failure # Nokia Siemens Networks 215 (244) .Common measurement supervision Depending on the scenario. Failure in pid updating can cause troubles to other O&M scenarios where that information is needed. and failure in WBTS capability updating or cch parameter updating can cause inconsistent data to be used in RNC and thus problems in signalling or in actual calls.Cell reconfiguration . This reading or writing operation was tried to be carried out for some of the following scenarios: .Cell unlocking .Resource status indication handling .Modification of configuration data .Cell activation .Cell unblocking .Iu service barring .WBTS reset .Audit handling .

If database state is "waiting for dumping" or "dumping". State of database should be normal and memory (and disk) updates are not prevented. 3GPP iub Cell reconfiguration. 3GPP iub Failure in cell reconfiguration. Maintenance Manual) or from the document General Error Messages of System. you can resume them with command ZDBR:RAQUEL.0.Base Station Alarms (7000-7999) 2 reason of the failure 00 01 02 03 04 05 11 12 3 scenario that was being carried out when the failure occured 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 81 82 83 84 8D 8E 8F 90 91 4 Not specified Failure at initialization Configuration data Inactivation of the cell has failed Activation of the cell has failed NBAP-link state updating failure Failure in cell setup. 3GPP iub WBTS restart. If updates are prevented. 3GPP iub Common measurement supervision general error code of the system.0:<mem or disk>. 3GPP iub WBTS cell block. 3GPP iub Resource status indication handling. 3GPP iub WBTS cell unblock. 3GPP iub Iu service barring WBTS initialization. database 216 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials. Supplementary References Instructions At first check the functionality of Radio Network database with following MML-commands: ZDBS:RAQUEL. 3GPP iub WBTS initialization Cell unlocking Configuration data modification RNC restart Local cell resource state change Forced handover WBTS reset WBTS capability information update Pid update CCH data update Link failure/link failure cancel CCH Supervision Audit handling. 3GPP iub RNC restart. 3GPP iub Cell unlocking.

If this does not clear the alarm. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 217 (244) . Also RNC reset might help if it is possible to make.7762 RNW DATABASE OPERATION FAILURE should return to normal state automatically after dumping is ready. Also status of the disk updating system can be check with MML-command ZDBD:OMU. WBTS reset can be tried If database state stays abnormal for long time or the alarm appears constantly for several WBTSs and cells. It can be studied with MML-command ZDDE::"ZGSC". The system cancels the alarm automatically when the fault has been corrected. do as follows: Try to lock the cell and then unlock the cell with RNC Object Browser. More information about the exact fail reason can be found by examining the supplementary info field 4 (error code). In many cases there also more info in OMU computer log. contact the local Nokia Customer Service Center. Line "RAQUEL" specifies the state of Radio Network database. Cancelling Do not cancel the alarm. If database state is working (or becomes working after while).

Base Station Alarms (7000-7999) 218 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

WCEL is unlocked and COCO connection operation has been performed. meaning that user initiated state change does not cause the alarm to be set. and it can not transmit any traffic.WO -> BL (S). Alarm is cancelled automatically when WCEL recovers to WO state or when the cell is locked by the user. bl. 3. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 219 (244) . Such Local Cell does not exist in WBTS.WO -> BL (B). 2. bl. WCEL state is changed from .Common measurement failure . COCO connection operation is performed.WBTS .shutting down) and only after that to some of the above mentioned states. This alarm is set only when cell is moved to blocked state by the system. bl.init .system failure .C-NBAP link failure . but WCEL state does not change to WO state. Incorrect Local Cell Resource id has been given to this cell. bl.Blocked by user locally from WBTS It is possible that WCEL state changes first from WO to BL (H) (bl .7771 WCDMA CELL OUT OF USE 41 7771 WCDMA CELL OUT OF USE Meaning The alarm indicates that unlocked WCDMA cell is blocked for some reason. This alarm is NOT set when WCEL state changes from WO to BL (H).WO -> BL (I). The alarm is set when some of the following situations occur: 1. 4. bl.WO -> BL (L). WCEL has been unlocked but WCEL state does not change to WO state. it is set when BL (H) state is replaced by some of the above mentioned blocked states. bl.WO -> BL (Ub).WO -> BL (M).

block/unblock BTS with BTS element manager. 2. Typically there is still some recovery operation ongoing. check WBTS alarm that is related to this WCEL and follow operating instructions there. If automatic recovery does not correct the situation. If blocking reason in supplementary info field 1 (WCEL state) is 0400 (BL (N)).Common measurement failure (M) 0200: bl . try to lock and then unlock the cell manually with RNC Object Browser. Full information about the current cell state is available in RNC Object Browser.WBTS (WBTS has sent disabled state information) (B) 0020: bl . If the alarm is still active after the above operations have been performed. Instructions First task: wait 5 minutes.Blocked because cell does not exist in WBTS (N) 2 general error code of the system. Cell data must be corrected and then WBTS reset is required to remove the problem. You can check its meaning from General Error Messages of System. or . Alarm is cancelled if recovery is successful.system failure (S) 0040: bl . or . Meaning of the possible values and corresponding GUI abbreviation: 0008: bl . Such Local Cell does not exist in WBTS. follow these steps: 1. and no obvious reason behind it can be found. collect 220 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .init (also during resets) (I) 0080: bl .C-NBAP-link failure (L) 0100: bl .Blocked by user locally from WBTS (Ub) 0400: bl .reform connection between WBTS and COCO by first disconnecting the COCO and the reconnecting it (This can be done by changing the used COCO id in WBTS with RNC Object Browser). These operations clear and again init the BTS related resources: . If alarm is not cancelled due lock / unlock cell operation you can try some of the following actions (each of these causes WBTS to be unavailable during the operation). In case there are no alarms targeted to WCEL. incorrect Local Cell Resource id has been given to this cell.Base Station Alarms (7000-7999) Supplementary information fields 1 indicates the state that WCEL was changed into and what caused the alarm to be set.Reset WBTS with RNC Object Browser. If blocking reason in supplementary info field 1 (WCEL state) is 0008 (BL (B)) or 0200 (BL (Ub)). 4. 3. This causes system to try to clear possible hanging cell related resources and then recreate (init) them.

4FB. The system cancels the alarm automatically when the fault has been corrected. More information about the exact fail reason can be found by examining the supplementary info field 2 (error code). Maintenance Manual) or from the document General Error Messages of System. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 221 (244) . The alarm is cancelled by system if the cell in question becomes working again or it is locked by user. Cancelling Do not cancel the alarm. Also RNC reset might help if it is possible to make. 4EE and 4EF) and serving ICSU (check serving ICSU from COCO data in RNC Object Browser. 4B7) during BTS reset. It can be studied with MML-command ZDDE::"ZGSC".7771 WCDMA CELL OUT OF USE at least following logs and contact the local Nokia Customer Service Center: .message monitoring from OMU (families 50B.OMU computer log (service terminal command ZGSC). You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials. . monitor families 4FE. Supplementary References In many cases there also more info in OMU computer log. 4FD. 4FA.

Base Station Alarms (7000-7999) 222 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

the effect is that HSDPA connections cannot be used in this particular cell at all. Supplementary information fields 1 reason of the alarm Possible 01 = 02 = 03 = values: No reply from BTS BTS rejects the configuration 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 DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 223 (244) . . The causes which result in this alarm are: .BTS has rejected the configuration or reconfiguration of HSDPA channels . .a problem in transmission network between RNC and BTS . In this case also the HSUPA connections are unavailable if HSUPA is enabled in the cell.7772 HSDPA CONFIGURATION FAILED 42 7772 HSDPA CONFIGURATION FAILED Meaning This alarm indicates that there has been an error when RNC has requested configuration or reconfiguration of HSDPA channels to BTS via Physical Shared Channel Reconfiguration procedure.In case the initial configuration of HSDPA channels fails.RNC is unable to send the HSDPA configuration to BTS because of RNC internal problems (e.In case of reconfiguration of HSDPA channels the effect is that the cell may not work with intended HSDPA parameters. The consequence of this alarm depends on the HSDPA configuration phase.g. congestion in Iub interface) Location and the nature of the failure can be determined from the supplementary information fields of this alarm.

02: Reconfiguration of HSDPA The problem has occured during HSDPA reconfiguration to a cell. 224 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . In this case it is recommended that HSDPA is disabled and enabled in the cell to confirm that proper parameters are taken into use. The effect is that the HSDPA may not work with the intended parameters.Base Station Alarms (7000-7999) 5 Possible 00 = 01 = 02 = 03 = values: Error in radio network configuration Error in transport layer Error in NBAP protocol layer Miscellaneous possible 00 = 01 = 06 = 09 = values sent by the BTS: Unknown cell ID (RNW configuration) Cell not available (RNW configuration) Node B resources unavailable (RNW configuration) Requested configuration not supported (RNW configuration) 04 = Unspecified (Misc) 6 more detailed cause in case the value of the 1st supplementary information field is 3 ("RNC Internal error"). The 7th supplementary information field 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. 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 Instructions Check first the nature of the problem. The effect of this is that HSDPA cannot be used in the cell.

proceed according to instructions given for those alarms. If the working state of the BTS and the BTS HW configuration are OK but this fault still occurs contact the local Nokia Customer Service Center. The first supplementary information field value indicates the main reason for the problem. If ping does succeed. 01: No reply from WBTS Problem may reside somewhere in transmission network to BTS. Successful PING tells that the BTS is up and running: MML command: ZQRX If ping does not succeed. check the configuration of this WBTS object in RNC using RNW RNC Object Browser. If the C-NBAP link is working. If the working state of the BTS is OK. If the C-NBAP link is not working. then the problem is in lower level of the transmission network. In case the fault is related to RNW configuration (based on 4th and 5th alarm supplementary information fields of this alarm). If there are active alarms. If the fault cannot be resolved by correcting the configuration or DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 225 (244) .7772 HSDPA CONFIGURATION FAILED This action requires cell locking. Check physical connections in network. 02: BTS rejects the configuration Check that the concerned BTS is in working state using RNC RNW Object Browser. In many cases there is also more info in OMU computer log. check that the BTS has correct HW configuration so that HSDPA can be supported (WSPC cards) using BTS Manager. then the problem is in application level. and the configuration in BTS using BTS Manager. check the success of PING between RNC and BTS. Check the state of C-NBAP link of this WBTS object from RNC RNW Object Browser main dialog. the problem may reside in the BTS. Check if there are other active alarms for the WBTS object and follow the instructions given for those alarms. It can be studied with MML-command ZDDE::"ZGSC". 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. If there are no apparent problems shown via other alarms. Check also if other alarms are active targeted to this same WBTS object. Check the BTS configuration and logs using BTS Manager.

<index>:"ZGDIC. 510 or 529. Collect the logs and monitorings and contact the local Nokia Customer Service Center.g. the alarm should not appear again. The system cancels the alarm automatically when the fault has been corrected. If the 6th supplementary information field of this alarm has a value 306. 505. check the log writings from the concerned ICSU e. 506. 226 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . 03: RNC internal error An internal error in RNC has occured during Physical Shared Channel Configuration procedure. To collect the necessary data for troubleshooting.". If the problem was only temporary. or next succeeded configuration of HSDPA channels cancels the alarm. 504. If the alarm appears again after a while. 420. 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. This operation cancels the alarm and triggers the Physical Shared Channel Reconfiguration procedure again. The ICSU unit index to be used is shown in the 3rd supplementary information field of this alarm. Cancelling Do not cancel the alarm. the situation may be resolved by locking and unlocking the cell. 501. Locking or deleting of the cell. contact the local Nokia Customer Service Center. 508. by using MML command ZDDE:ICSU.Base Station Alarms (7000-7999) other BTS alarms. Start the Physical Shared Channel Reconfiguration procedure by locking and unlocking the cell and wait for the alarm to be set again.

Alarm indication preventions can be altered with MML command AFC. is related to this alarm and one instance of it is activated when Nokia specific configuration parameter sending has failed to one or more cells in certain RNC. Supplementary information fields 1 general error message of the system. The alarm is set when BTS has failed to accept the parameters send to it during cell setup or when BTS has not responded to the parameter sending during cell setup. Situation causing this alarm will not obstruct network operations. ShutdownWindow and ShutdownStepAmount in RNC using RNC Object Browser. The alarm is cell-specific and its indication has been prevented to NetAct by default. These parameters are CellRange. The RNC-specific alarm 3325.7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS 43 7775 INCONSISTENCY IN WCEL CONFIGURATION PARAMETERS Meaning The alarm indicates that the Nokia specific configuration parameters in BTS might not be consistent with the parameters in RNC. ShutdownWindow and ShutdownStepAmount. SIB7factor. SIB7factor. If these parameter values are the same as those in the BTS Site DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 227 (244) . RACHCapacity. You can check its meaning with a command of the service terminal extension MRS or in the General Error Messages of System Instructions Check the cell parameters CellRange. RACHCapacity. Alarm is cancelled automatically after these configuration parameters have been successfully sent. INCONSISTENCY IN NOKIA SPECIFIC CONFIGURATION PARAMETERS. This RNC-specific alarm is sent to NetAct by default.

If the cell parameters in RNC are not the same as those in the BTS Site Configuration File and these parameters need to be updated. * 15477 = EQUIPMENT FAILURE HW failure has occurred. 228 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . It can be studied with MML-command ZDDE::"ZGSC". cell state (WCEL state) is WO.Base Station Alarms (7000-7999) Configuration File. In many cases there also more info in OMU computer log. Fault cases with error code EQUIPMENT FAILURE may also require repairing of BTS HW. Maintenance Manual) or from the document General Error Messages of System. following actions can be taken to the cell that has failed to accept the parameters sent: * Modify these parameters with RNC Object Browser. * Lock the cell and then unlock it with RNC Object Browser. This operation causes the parameters to be resent to the BTS. * 15480 = NO RESOURCES IN WBTS Node B resources are unavailable. 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. then no actions are needed in RNC. In these fault cases the actions mentioned above should repair the situation.e. You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials. Supplementary References. Cancelling Do not cancel the alarm. Check if other alarms are active for the BTS or WCEL in question. More information about the exact fail reason can be found by examining the supplementary info field (error code). * 15472 = WBTS HARDWARE OVERLOAD BTS is temporarily too busy to handle new requests. This is recommended if cell is working i. * 16504 = INTERNAL NBAP ERROR PREVENTING PROCEDURE COMPLETION Internal error has occurred that prevents parameter sending. The system cancels the alarm automatically after these parameters are sent successfully to the WBTS.

Check the reason for the fault from BTS WSP related alarms. If HSDPA dedicated WSPC unit in BTS is faulty. BTS reserves another WSPC when it becomes free from another traffic. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 229 (244) . see Nokia WCDMA BTS Alarm Descriptions (SW and release document). Alarms to be checked are: 7650 BASE STATION FAULTY 7651 BASE STATION OPERATION DEGRADED 7652 BASE STATION NOTIFICATION Faulty unit is mentioned in supplementary information field 3 of these alarms. HSDPA connections cannot be used in the particular cell. Supplementary information fields Instructions The alarm requires no actions from the RNC side. All WSP related alarms must be checked because any WSP related fault may be a reason for this particular alarm. As a consequence of this alarm. A unit (or units) that take care of HSDPA traffic in WCEL may be faulty or there is not enough capacity available in BTS WSP cards for HSDPA service. Check WSP related active alarms in RNC that are targeted to this BTS. This alarm is set when HSDPA capable BTS has sent a Resource Status Indication message via NBAP to RNC indicating that HSDPA state is changed to disabled. For more information about BTS alarms.7776 HSDPA FAILURE IN WCEL 44 7776 HSDPA FAILURE IN WCEL Meaning A major fault (or faults) has occurred in the BTS.

Base Station Alarms (7000-7999) Cancelling Do not cancel the alarm. 230 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . The system cancels the alarm automatically when the fault has been corrected.

If the retry succeeds. the alarm will be cancelled.7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE 45 7778 WCDMA BTS DEDICATED MEASUREMENT FAILURE Meaning This alarm is set when Dedicated Measurement (for transmitted code power) Initiation fails due to following 3 cases during cell initialization. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 231 (244) . If there are no obvious faults indicated by active alarms and this alarm is not cancelled by system. Maintenance Manual) or from the document General Error Messages of System. This alarm is cancelled if the problem is solved by correcting the other active alarms. cells' capacity under the BTS might be affected. follow the instructions given in the steps below according to error code given in 1st supplementary information field. check if there are other alarms active for the BTS in question and follow the instructions given for those alarms. Supplementary information fields 1 general error code of the system. Supplementary References 2 communication control port id Instructions First. such as no response or nack 2) NBAP-D link is down 3) NBAP-D module has problem (RNC internal) RNC will retry Dedicated Measurement Initiation after the corresponding NBAP-D link is re-created to be ready. After this alarm. 1) BTS problem. You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials.

It should be analyzed by connecting to corresponding BTS using BTS Manager. OMU computer log and error log (MML-commands ZDDE::"ZGSC". the communication problem between RNC processes should be analyzed by taking message monitoring from RNC OMU when the unlocking of the cells is done. contact the local Nokia Customer Service Center.Base Station Alarms (7000-7999) 1. If this doesn't help. Error code 13247 no_answer_from_remote_end_ec 15479 nbap_bts_hw_res_not_avail_ec No response from BTS BTS hardware failure These code indicates that response from BTS was not received for Dedicated Measurement Indication or BTS hardware failure. Attach OMU message monitoring for process 3C6.) and alarm history (MML-command ZAHP or using Fault Management application in RNC EM). 2. Cancelling Do not cancel the alarm. it may help if the problem was only temporary. The operation can be retried by creating the corresponding NBAP-D again using RNC RNW Object Browser (this operation causes all the cells of the BTS being unavailable for traffic): 1) Lock all the cells under the BTS 2) Remove the WBTS id from the COCO 3) Add the WBTS id to the COCO again 4) Unlock these cells If creating the NBAP-D again does not help. The system cancels the alarm automatically when the fault has been corrected. all of ICSUs message monitoring for process 4FE. a BTS restart may be attempted to solve the situation. and ZDDE::"ZGLE". Any other error code: Try to perform NBAP-D link creation again using instructions given in step 1. the problem may reside on the BTS end. If the operation in step 1 does not help. Error code 13288 dst_link_failure_ec 13846 no_resp_from_serv_provider_ec NBAP-D link has been down NBAP-D process no response The operation in step 1 can be attempted. See the last part of this instruction for information about collecting the needed monitorings and logs. 232 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . If the problem persists after these steps. 3.

After this alarm has been cancelled and BTS recovery actions have ended. If common measurements are missing and common measurement recovery actions have failed. If common measurement initialization constantly fails. Supplementary information fields 1 this value indicates the cause that has lead to recovery actions: 00 01 02 DN99580892 Issue 6-3 en 12/06/2008 Common measurements are missing and common measurement recovery actions have failed. 6. Alarm 7761 or 7762 is set if some failure occurred during WBTS initialization after the WBTS reset.7779 RECOVERY ACTIONS ONGOING 46 7779 RECOVERY ACTIONS ONGOING Meaning The alarm indicates that RNC has started WBTS recovery actions due to non-performing WCDMA cell. Alarm is cancelled automatically after the WBTS recovery actions have been completed. 5. Poor FACH RRC connection setup/complete ratio. After this operator may start to do user actions again. it is possible that other recovery actions are started if cells are still in some block state. This alarm informs operator that recovery actions are ongoing. and during this recovery action no other user actions are recommended. # Nokia Siemens Networks 233 (244) . which will take a while. 2. The alarm is set when some of the following situations occur: 1. Base Station resource manager process family (BRM) hand crash in RNC. During recovery actions it can not transmit any traffic. Common channel creation constantly fails. Poor handover related radio link setup ratio. 3. If common channel creation fails constantly 4. The recovery actions include WBTS reset. Common measurement initialization constantly fails.

The system cancels the alarm automatically when the fault has been corrected. collect at least following logs and contact the local Nokia Customer Service Center: . Base Station resource manager process family (BRM) hand crash in RNC.). Instructions This alarm does require any actions. Cancelling Do not cancel the alarm. . 4B7) during WBTS reset. monitor families 4FE. 4FD. 4FB. The reason for WBTS recovery actions is indicated in 1st supplementary information field.alarm history (MML-command ZAHP or using Fault Management application in RNC EM) .OMU computer log (MML-commands ZDDE::"ZGSC". If cell is still not working after the WBTS recovery actions have ended and no reason behind it can be found.message monitoring from OMU (families 50B. 4FA) and serving ICSU (check serving ICSU from COCO data in RNC Object Browser. 234 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . and ZDDE::"ZGLE". WBTS recovery actions are started when other recovery actions have not recovered the cell. Poor FACH RRC connection setup/complete ratio.Base Station Alarms (7000-7999) 04 05 08 Poor handover related radio link setup ratio.

see Nokia WCDMA BTS Alarm Descriptions (SW and release document). All WSP related alarms must be checked. because any one of the WSP related If the HSUPA dedicated WSPC unit in the BTS is faulty. A unit (or units) taking care of HSUPA traffic in the WCEL may be faulty or there is not enough capacity available on the BTS WSP cards for HSUPA service. Check in the RNC the WSP related active alarms which are targeted to this BTS. Alarms to be checked are: 7650 BASE STATION FAULTY 7651 BASE STATION OPERATION DEGRADED 7652 BASE STATION NOTIFICATION The faulty unit is mentioned in the supplementary information field 3 of these alarms. For more information on BTS alarms. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 235 (244) . Check the reason for the fault from BTS WSP related alarms. Supplementary information fields Instructions This alarm requires no actions from the RNC side. the BTS reserves another WSPC when it becomes free from other traffic.7780 HSUPA FAILURE IN WCEL 47 7780 HSUPA FAILURE IN WCEL Meaning A major fault (or faults) has occurred in the BTS. HSUPA connections cannot be used in that particular cell. This alarm is set when an HSUPA capable BTS has sent a Resource Status Indication message via NBAP to the RNC indicating that HSUPA state has been changed to disabled. As a consequence of this alarm.

236 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 . The system cancels the alarm automatically when the fault has been corrected.Base Station Alarms (7000-7999) Cancelling Do not cancel the alarm.

a problem in transmission network between RNC and BTS .If the failure occurred in the reconfiguration of the HSUPA.g.If the failure occurred in the initial HSUPA configuration or in delivering the HSUPA parameters to the BTS. .7782 HSUPA CONFIGURATION FAILED 48 7782 HSUPA CONFIGURATION FAILED Meaning This alarm indicates that there has been an error when RNC has requested configuration or reconfiguration of HSUPA channels to BTS via Physical Shared Channel Reconfiguration (PSCR) procedure. the effect is that the cell may not work with intended HSUPA parameters Supplementary information fields 1 reason of the alarm Possible 01 = 02 = 03 = values: No reply from BTS BTS rejects the configuration 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 DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 237 (244) . the HSUPA connections cannot be used in this particular cell at all .RNC is unable to send the HSUPA configuration to BTS because of RNC internal problems (e.BTS has rejected the configuration or reconfiguration of HSUPA channels . The possible causes which result in this alarm are: . The consequence of this alarm depends on the HSUPA configuration phase where the failure occurred. congestion in Iub interface) Location and the nature of the failure can be determined from the supplementary information fields of this alarm.

Base Station Alarms (7000-7999) value is 01 5 more detailed cause in case the BTS rejects the configuration Possible 00 = 01 = 02 = 03 = values: Error in radio network configuration Error in transport layer Error in NBAP protocol layer Miscellaneous The value in this field is applicable if 8th supplementary information field value is 02 or 03 6 possible values sent by the BTS: 00 01 06 09 = = = = Unknown cell ID (RNW configuration) Cell not available (RNW configuration) Node B resources unavailable (RNW configuration) Requested configuration not supported (RNW configuration) 03 = Not enough user plane processing resources (Misc) 04 = Unspecified (Misc) The value in this field is applicable if 8th supplementary information field value is 02 or 03 7 more detailed cause in case the value of the 1st supplementary information field is 03 ("RNC Internal error"). Possible values: 306 328 402 404 420 501 504 505 506 507 508 510 529 = = = = = = = = = = = = = Internal waiting timer expired in BTS Resource Manager BTS overloaded Wrong BTS ID Wrong cell ID No free DL Spreading Codes available for HSUPA Internal waiting timer expired in NBAP interface Encoding failed in NBAP interface Decoding failed in NBAP interface Parallel procedure not allowed Unit switchover State conflict Table full NBAP link down The value in this field is applicable if 8th supplementary information field value is 02 or 03 8 phase of HSUPA configuration 01 = Delivering HSUPA parameters to BTS 02 = Initial HSUPA configuration 03 = Reconfiguration of HSUPA 238 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .

7782 HSUPA CONFIGURATION FAILED

Instructions

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

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

DN99580892
Issue 6-3 en
12/06/2008

# Nokia Siemens Networks

239 (244)

Base Station Alarms (7000-7999)

In many cases there is also more info in OMU computer
log. It can be studied with MML-command
ZDDE::"ZGSC";
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 Customer Service
Center.
In case the fault is related to RNW configuration (based on 4th and
5th alarm supplementary information fields of this alarm), check the
configuration of this WBTS object in RNC using RNW RNC Object
Browser, and the configuration in BTS using BTS Manager.
Check also if other alarms are active targeted to this same WBTS
object. If there are active alarms, proceed according to instructions
given for those alarms.
If the fault cannot be resolved by correcting the configuration or
other BTS alarms, contact the local Nokia Customer Service Center.
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 Customer Service Center.

240 (244)

# Nokia Siemens Networks

DN99580892
Issue 6-3 en
12/06/2008

7782 HSUPA CONFIGURATION FAILED

Cancelling

Do not cancel the alarm. The system cancels the alarm automatically
when the fault has been corrected.
Locking or deleting of the cell, or next succeeded configuration of HSDPA
channels cancels the alarm.

DN99580892
Issue 6-3 en
12/06/2008

# Nokia Siemens Networks

241 (244)

Base Station Alarms (7000-7999)

242 (244)

# Nokia Siemens Networks

DN99580892
Issue 6-3 en
12/06/2008

and it has the same adjustable alarm parameters as the actual alarms. 2 the one byte size of field which is output in decimal format. This alarm does not indicate any fault situation. 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. The field value is not significant. so all the alarm handling rules are valid for it. 7 the four byte size of field which is output in hexadecimal format. 6 the two byte size of field which is output in hexadecimal format.7799 RNC RADIO NETWORK TEST ALARM 49 7799 RNC RADIO NETWORK TEST ALARM Meaning This is a test alarm which is used only for testing purposes for the RNW alarm system of the RNC. and the system does not generate this alarm by itself in any circumstances. The field value is not significant. The alarm is however handled as any actual alarm. 5 the one byte size of field which is output in hexadecimal format. DN99580892 Issue 6-3 en 12/06/2008 # Nokia Siemens Networks 243 (244) . The field value is not significant. The field value is not significant. 3 the two byte size of field which is output in decimal format. Supplementary information fields 1 this is compared supplementary info field meaning that test alarms for same object can be identified by setting different values into this field.

Cancelling Cancel the alarm with an MML command. 244 (244) # Nokia Siemens Networks DN99580892 Issue 6-3 en 12/06/2008 .Base Station Alarms (7000-7999) Instructions No operation instruction.