7761 RNW O&M SCENARIO FAILURE Meaning

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

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 WBTS reservation has failed Configuration data updating has failed Inactivation of the cell has failed Activation of the cell has failed Common channel deletion has failed Common channel creation has failed BCCH information updating has failed WBTS capability information was not received Forced handover request was not accepted WBTS capability information update has failed AAL2 path unblocking has failed Unknown NBAP interface type Audit has failed, only 3GPP iub Cell setup procedure has failed, only 3GPP iub Cell deletion procedure has failed, only 3GPP iub Common measurement initiation has failed, only 3GPP iub RRI measurement initiation has failed, only 3GPP iub Cell reconfiguration procedure has failed, only 3GPP iub

18 19 20 21 2

Common or RRI measurement termination failed, 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 93 94 Not specified WBTS initialization, Nokia Siemens Networks iub Cell unlocking, Nokia Siemens Networks iub Configuration data modification, Nokia Siemens Networks iub RNC restart, Nokia Siemens Networks iub Local cell resource state change Forced handover WBTS reset initiation from RNC WBTS capability information update Pid update Connection configuration management Audit handling, 3GPP iub CCH Supervision WBTS recovery Iu service barring Cell deletion, 3GPP iub WBTS initialization, 3GPP iub Cell unlocking, 3GPP iub Cell reconfiguration, 3GPP iub RNC restart, 3GPP iub WBTS restart, 3GPP iub WBTS cell block, 3GPP iub WBTS cell unblock, 3GPP iub Resource status indication handling, 3GPP iub Common measurement supervision Dedicated measurement initiation Cell activation due to power save Cell shutdown due to power save

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

ATM interface identifier of network external or internal interface. This field is significant only in case of User plane configuration fault. FFFF Not specified

virtual path identifier. This field is significant only in case of User plane configuration fault. FFFF Not specified

virtual channel identifier. This field is significant only in case of User plane configuration fault. 0 Not specified

Instructions
This instruction contains five main steps. The first four steps are specific to certain failure situations. The last step is a general

operating procedure for all other failures indicated by this alarm. It is also a default procedure to be performed if instructions given in previous steps do not solve the problem. Abbreviation SIF refers to supplementary information field. Step 1: In case the value of SIF 2 (scenario) is 07 (WBTS reset): - First, verify using RNC Object Browser that WBTS id is valid in the system and COCO is connected to WBTS. - Check also if alarm 7750 FAILURE IN WCDMA BTS O&M CONNECTION is active for this WBTS. If it is active indicating that there is something wrong with WBTS O&M connection (Iub), then reset command cannot be sent from RNC to WBTS. -> If WBTS O&M connection is OK, retry to reset WBTS with RNC Object Browser. -> If WBTS O&M connection between RNC and WBTS is not OK, try to solve the situation with BTS Manager by examining the WBTS alarms and logs. Step 2: In case the value of SIF 2 is 0A (Connection configuration management), and the value of the SIF 1 is 0B (AAL2 path unblocking has failed): - Check the configuration of the corresponding WBTS node using BTS Manager. It should match the configuration of the RNC. - Check that ATM resources related to COCO are not locked. Locked ATM resources will prevent the connection configuration operations. - Use MML command ZLAI to print ATM interface information and MML command ZLCI to print VP/VC information (if ATM layer information is given by the user in RNC Object Browser). - Unlock the ATM-interface with MML command ZLAS and VP/VC with MML command ZLCS if needed. - If this alarm was generated due to user initiated action, e.g. COCO creation, try to perform the operation again. - If configuration is correct and ATM resources are unlocked, act according to general operating instructions in step 3 below. Step 3: In case the SIF 2 value is 0D (WBTS recovery) and the value of the SIF 1 is 20 (COCO disconnect has failed) or 21 (COCO connect has failed): - In case of COCO disconnect failure, disconnect the COCO manually using RNC RNW Object Browser by removing the WBTS id from the corresponding COCO object. Wait at least for 15 seconds and connect the COCO again by restoring the WBTS id to COCO object. - In case of COCO connect failure, try to connect the COCO again to the WBTS using RNC RNW Object Browser. If COCO id related to this WBTS is not known, the related COCO id can be found from OMU computer log by searching for process family 50B writings (ZGSC:,50B;) that contain the also the WBTS id that this alarm is targeted to. Step 4: In case the SIF 2 value is 92 (Dedicated measurement initiation): - Alarm 7778, WCDMA BTS DEDICATED MEASUREMENT FAILURE should be active. Follow the instructions given for that alarm.

Step 5: General operation instructions for all other failure reasons: Wait a couple of minutes, system tries to recover from the problem by retrying the failed operation again and the alarm may be cancelled automatically. In case the alarm is not cancelled due to system recovery while waiting, try to lock and then unlock the cell with RNC Object Browser manually. This causes the system to try to clear possible hanging cell related resources and then recreate (init) them. In case the alarm is still active after lock/unlock cell operation, some of the following actions can be tried (each of these causes the WBTS to be unavailable during the operation). These operations clear and again init the BTS related resources: - Reset the WBTS with RNC Object Browser, or - Reform the connection between WBTS and COCO by first disconnecting the COCO and then reconnecting it (this can be done by changing the used COCO id in the WBTS with RNC Object Browser) or block/unblock the BTS with BTS element manager. If the alarm still remains active after the steps above, and no obvious reason behind it can be found, collect at least the following logs and contact the local Nokia Siemens Networks representative: - OMU computer log, - message monitoring from OMU (families 50B, 4FA, 4EE and 4EF) and serving ICSU (check serving ICSU from COCO data in RNC Object Browser, monitor families 4FE, 4FB, 4FD, 4B7) during BTS reset Also RNC reset might help the situation if it is possible to be performed. More information about the exact failure reason can be found by examining the supplementary info field 3 (error code). You can check its meaning with a command of the service terminal extension MRS (see Service Terminal Essentials, Maintenance Manual) or from the document General Error Messages of System, Supplementary References. In many cases there is also more information in OMU computer log. It can be studied with MML-command ZDDE::"ZGSC";

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

DN99580892

Id: 0900d80580829119

2010 Nokia Siemens Networks