You are on page 1of 6

7772 HSDPA CONFIGURATION FAILED Meaning

This alarm indicates that there has been an error when controller has requested configuration or reconfiguration of HSDPA channels to BTS via Physical Shared Channel Reconfiguration procedure. The causes which result in this alarm are: - a problem in transmission network between controller and BTS - BTS has rejected the configuration or reconfiguration of HSDPA channels - Controller is unable to send the HSDPA configuration to BTS because of controller internal problems (for example congestion in Iub interface) Location and the nature of the failure can be determined from the supplementary information fields of this alarm. The consequence of this alarm depends on the HSDPA configuration phase. - In case the initial configuration of HSDPA channels fails, the effect is that HSDPA connections cannot be used in this particular cell at all. In this case also the HSUPA connections are unavailable if HSUPA is enabled in the cell. - In case of reconfiguration of HSDPA channels the effect is that the cell may not work with the intended HSDPA parameters.

Supplementary information fields


1 reason of the alarm Possible values: 01 = No reply from BTS 02 = BTS rejects the configuration 03 = Controller internal error 2 3 4 computer unit where this alarm is generated from index of the alarming unit more detailed cause in case the BTS rejects the configuration Possible values: 00 = Error in radio network configuration 01 = Error in transport layer 02 = Error in NBAP protocol layer 03 = Miscellaneous 5 possible values sent by the BTS, value meaning depends on the cause that is given in 4th supplementary information field:

00 = Unknown cell ID (RNW configuration) 01 = Cell not available (RNW configuration) 06 = Node B resources unavailable (RNW configuration) 09 = Requested configuration not supported (RNW configuration) 03 = Message Not Compatible With Receiver State (Protocol) 00 = Control processing overload (Misc) 03 = Not enough user plane processing resources (Misc) 04 = Unspecified (Misc) 6 more detailed cause in case the value of the 1st supplementary information field is 3 ("controller Internal error"). Possible values: 306 = Internal waiting timer expired in BTS Resource Manager 328 = BTS overloaded 402 = Wrong BTS ID 404 = Wrong cell ID 420 = No free DL Spreading Codes available for HSDPA 501 = Internal waiting timer expired in NBAP interface 504 = Encoding failed in NBAP interface 505 = Decoding failed in NBAP interface 506 = Parallel procedure not allowed 507 = Unit switchover 508 = State conflict 510 = Table full 529 = NBAP link down 7 phase of HSDPA configuration 01 = Initial HSDPA configuration 02 = Reconfiguration of HSDPA 03 = PWSM HSPA05 reconfiguration failure

Instructions
Check first the nature of the problem. The 7th supplementary information field value indicates the phase in which the problem has occurred: 01: Initial HSDPA configuration The problem has occurred during initial HSDPA setup to a cell. The effect of this is that HSDPA cannot be used in the cell. 02: Reconfiguration of HSDPA The problem has occurred during HSDPA reconfiguration to a cell. The effect is that the HSDPA may not work with the intended parameters.

In this case it is recommended that HSDPA is disabled and enabled in the cell to confirm that proper parameters are taken into use. This action requires cell locking. 03: PWSM HSPA05 reconfiguration failure The problem has occurred during HSDPA reconfiguration to a cell when Power Saving Mode For BTS (PWSM) feature has been making HSPA05 reconfiguration. HSPA05 reconfiguration has been stopped and no cell deletion or activation by PWSM feature will be done. In this case it is recommended to disable PWSM feature. Do cell lock/unlock to recover cell HSDPA parameters and state. If cell is not recovered using lock/unlock operation, a BTS restart can be attempted using Element Manager or BTS Site Manager. The first supplementary information field value indicates the main reason for the problem. 01: No reply from WBTS Problem may reside somewhere in transmission network to BTS. Check if there are other active alarms for the WBTS object and follow the instructions given for those alarms. If there are no apparent problems shown via other alarms, check the type of network problem with following instructions: Precondition for Physical Shared Channel Reconfiguration procedure is that the C-NBAP link to WBTS is working. Check the state of C-NBAP link of this WBTS object from Element Manager main dialog. If the C-NBAP link works, the problem may reside in the BTS. Check the BTS configuration and logs using BTS Manager. If the C-NBAP link does not work, check the success of PING between controller and BTS. Successful PING tells that the BTS is up and running: MML command: ZQRX (IPA-RNC) Normal Ping command : Multi-controller RNC/I-HSPA ADA If ping does not succeed, then the problem is in lower level of the transmission network. Check physical connections in the network. If ping succeeds, then the problem is in application level. In many cases there is also more information in OMU computer log. IPA-RNC : Logs can be studied with MML-command ZDDE::"ZGSC";

Multi-Controller RNC/I-HSPA ADA : Logs can be collected and studied from location "/srv/Log/log/" in the product.

02: BTS rejects the configuration Check that the concerned BTS is in working state using Element Manager. If the working state of the BTS is OK, check that the BTS has correct HW configuration so that HSDPA can be supported (WSPC cards) using BTS Manager. If the working state of the BTS and the BTS HW configuration are OK but this fault still occurs, contact the local Nokia Siemens Networks representative. In case the fault is related to RNW configuration (based on 4th and 5th alarm supplementary information fields of this alarm), check the configuration of this WBTS object in controller using Element Manager, and the configuration in BTS using BTS Manager. Check also if other alarms are active targeted to this same WBTS object. If there are active alarms, proceed according to instructions given for those alarms. If the fault cannot be resolved by correcting the configuration or other BTS alarms, contact the local Nokia Siemens Networks representative. 03: Controller internal error An internal error in controller has occurred during Physical Shared Channel Configuration procedure. If the 6th supplementary information field of this alarm has a value 306, 420, 501, 504, 505, 506, 508, 510 or 529, the situation may be resolved by locking and unlocking the cell. This operation cancels the alarm and triggers the Physical Shared Channel Reconfiguration procedure again. If the problem was only temporary, the alarm should not appear again. If the alarm appears again after a while, check the log writings from the concerned ICSU (IPA-RNC Control plane unit) for example by using MML command ZDDE:ICSU,<index>:"ZGDIC;"; The ICSU unit index to be used is shown in the 3rd supplementary information field of this alarm. To collect the necessary data for troubleshooting, initiate message monitorings in the concerned ICSU unit (IPA-RNC Control plane unit) mentioned in 2nd and 3rd supplementary information fields of this alarm (families 04FE, 04FB) and in active OMU unit.

In Multi-Controller RNC/I-HSPA ADA the detailed family logs can be collected from location in the product"/srv/Log/log/". Start the Physical Shared Channel Reconfiguration procedure by locking and unlocking the cell and wait for the alarm to be set again. Collect the logs and monitorings and contact the local Nokia Siemens Networks representative.

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

= 6]>

HST (59903) KPRN24 QUAL ** ALARM WBTS-162 WCEL-3 IMBI 7772 HSDPA CONFIGURATION FAILED 04FBH ICSU-23 49 1701 62720d 01 00 768d 02

2012-09-22 13:41:15.00