LGF-RNC-2011-10

List of Generic Faults LGF-RNC-2011-10

Radio Control lers

WCDMA RNC

RN4.0, RN5.0

© Nokia Siemens Networks CONFIDENTIAL Company Confidential 1 (288)

Table of Contents 1. RNC SW RELATED Outages ANALYSED P10 2011 ............................................................ 15

1.1 MXU not coming up after MP4 upgrade........................................................................... 15 1.2 A number of signalling links and WBTS down ................................................................. 15

2. Generic faults open in RN4.0 ................................................................................................. 17 2.1 Calls to voice mail if MTC paging was received during CS re-establishment .................. 17 2.2 Multi-RAB calls drops in congested cell........................................................................... 17 2.3 KPI degration occured after network interface modification by ZQRG ............................ 17 2.4 BRM hand process crash................................................................................................. 18 2.5 Output of ZNVI command shows abnormal printout ........................................................ 18 2.6 DSP's are restarting......................................................................................................... 19 2.7 PJOTOR has hanging RAB resources after overload situation ....................................... 19 2.8 Not possible to perform increment installation after full restore ....................................... 20 2.9 Bootprom upgrade execution (ZWDR) fails with empty info field..................................... 20 2.10 Working SFU spontaneous restart................................................................................... 21 2.11 Multi-RAB call drop .......................................................................................................... 21 2.12 M1001C150 RAB_ACT_FAIL_CS_VOICE_RNC counter is increasing in RNC.............. 22 2.13 Terminating Low Priority Signaling cannot initiate RT over NRT ..................................... 22 2.14 Alarm7652/7750 alarm type mismatch between NE/OSS ............................................... 23 2.15 ISHO 2G to 3G drop ........................................................................................................ 23 2.16 ICSU connectivity algorithm to consider cells per site as weighting factor ...................... 24 2.17 Call setup failure due to connection error ........................................................................ 24 2.18 Occasional NRM process exception during intra RNC IFHO........................................... 25 2.19 When SCTP state is down in association set, there is no active alarm in RNC2600....... 25 2.20 Call setup failure if previous RAB setup failed ................................................................. 26 2.21 OMS AlarmProcessor non-responsive - leading to 9047 alarm in Netact........................ 26 2.22 False cell alarm 7771 CELL OUT OF USE...................................................................... 26 2.23 SHO with Huawei being removed due to rnc_rab_no_sync_s......................................... 27 2.24 Excessive ICSU log writing coming from DI5_FISH_M1022C9 RN4.0 CD1.35............... 27 2.25 WBTS overload report handling....................................................................................... 28 2.26 Paging Delay counters show incorrect values ................................................................. 28 2.27 RNC restart in case other WDU has hardware problem even another WDU is fine ........ 29 2.28 MCC going in loop for triggering PCH to DCH transition all the time............................... 29 2.29 UL temporary lowered bitrate cannot be increased to 384 if BitrateSetPSNRT is ON .... 30 2.30 Alarm 70173 (Backend Database Required by CORBA Naming Service is Unavailable) ................................................................................................................................ 30 2.31 WBTS not showing alarms when it is off air..................................................................... 31 2.32 Illegal values from OLPC (outer loop power control) measurement ................................ 31 2.33 HSDPA retainability below 60%....................................................................................... 32 2.34 Occasional NPGEP unit start up failures after RNC reset ............................................... 32 2.35 HS-DSCH setup failure due to RNC for interactive.......................................................... 33 2.36 Alarm 3217 is reported to both 2N units .......................................................................... 33 2.37 SF10E SD4G-A HW block bitstream downgrade............................................................. 34 2.38 Boot prom updating printout changed to be line with real updating situation................... 34 2.39 Automatic MXU unit restarts ............................................................................................ 35 2.40 RNC remove active cell without consider CIO during Soft Handover .............................. 35 2.41 RRC does not update correct paging counters................................................................ 36 2.42 Missing daily 1013 AutoDef SHO measurement files ...................................................... 37 2.43 BTS IP-address shown on RNC RNW Object Browser ................................................... 37 2.44 Secondary PLMN ID consistency checking problem ....................................................... 38


2.45 Directed RRC Connection Setup currently re-directs UE to the UMTS900 layer ............ 38 2.46 Missing error description in GUI for some parameter modification cases........................ 39 2.47 RAB modification, MTC call failed on some R99 handset ............................................... 39 2.48 Cable configured with “no direction” remains after SW upgrade ..................................... 40 2.49 Occasional call drop after relocation from ADA to RNC due to failure in CFN calculation ................................................................................................................................... 40 2.50 CS call setup failure after incoming I-BTS sharing relocation.......................................... 41 2.51 Several Node-B sectors going to BL(I) ............................................................................ 41 2.52 Bootprom upgrade during RNW startup caused OMU restart ......................................... 42 2.53 The counters M1008C66, M1008C18, M1010C2 and M1010C40 are not updated if starting the compressed mode has failed in the UE.................................................................... 42

3. Generic faults open in RN5.0 ................................................................................................. 44 3.1 Unable to see alarm history in Fault Management .......................................................... 44 3.2 RNC cannot handle PS RAB Setup procedure if SCRI from UE is received for the PS CN same time.............................................................................................................................. 44 3.3 Cell Update is not handled correctly ................................................................................ 45 3.4 After changing the CN-ID for the IU-PS interfaces calls fail,............................................ 45 3.5 RNC sends incorrect SAI to the CN in the Initial Direct Transfer after failed Inter RNC SCC procedure,........................................................................................................................... 45 3.6 Fault Management issue after RU20 upgrade ................................................................. 46 3.7 RRC does not forward SecurityModeCommand to the UE.............................................. 46 3.8 Count of successes is more than attempts in Direct Resource Allocation Counters ....... 47 3.9 RRC was sending trace record to non existent PID after deactivation of trace ............... 48 3.10 Alarm 1024 HAND PROCESS ERROR IN PROGRAM BLOCK in ICSU ........................ 48 3.11 Problem in fetching data from RNW measurement presentation from RNC.................... 48 3.12 Security mode command not handle properly (Radio Link failure) .................................. 49 3.13 Incorrect packet call ticket................................................................................................ 49 3.14 Process exception during MultiRAB handover................................................................. 50 3.15 RRC process exception happens after failed relocation if new relocation is triggered by handover control during Iu release command waiting ............................................................ 50 3.16 E-DCH active set update failure....................................................................................... 51 3.17 M1002C423 still updated after SignallingConnectionReleaseIndication received. .......... 52 3.18 RNC does not know what DL PDU size is in use............................................................. 52 3.19 Security mode cancellation is not done properly ............................................................. 53 3.20 Call drop after MCC sent mcc_active_set_update_nack_s incorrectly........................... 53 3.21 No acknowledgement was received from the service provider within timeout limit (Error 13846) ............................................................................................................................... 53 3.22 The counter M661C4 doesn't reset after a measurement period..................................... 54 3.23 After SRNS relocation UE is not involved with HSPA from another vendor SRNC ......... 54 3.24 AMR call released suddenly ............................................................................................ 55 3.25 Packet Call Setup Failure after relocation........................................................................ 55 3.26 Packet Call Setup Failure due to MS ............................................................................... 56 3.27 Alarm7652/7750 alarm type mismatch between NE/OSS ............................................... 56 3.28 OBH process causes 100% CPU load during OMU start-up ........................................... 57 3.29 During Cell Reselection counter PS_SETUP_FAIL_OTHER_BGR (M1022C20) increase....................................................................................................................................... 57 3.30 ICSU switchover might fail ............................................................................................... 58 3.31 RRC does not allow Cell DCH transition.......................................................................... 58 3.32 SRNS failure when CS call started on I-ADA and moved to neighbouring RNC ............. 59 3.33 M1001C145 (RAB ACT FAIL CS VOICE IU) increased .................................................. 59 3.34 UE doesn't respond to Radio Bearer Release procedure................................................ 60


3.35 3344 UX LINK CONNECTION FAILURE alarm is not always cancelled automatically ... 60 3.36 OMU switchover when unsupported usb stick inserted ................................................... 61 3.37 PS-RAB setup failed due to Radio link failure.................................................................. 61 3.38 Counters M1010C11 IS_HHO_WO_CMOD_RSCP_RT and M1010C12 IS_HHO_WO_CMOD_CPICH_ECNO_RT updated incorrectly .................................................. 61 3.39 RNC use wrongly Start Value received from UE in the RRC Cell update to reconfigure DL ciphering ............................................................................................................. 62 3.40 Increased counter values for M1002C413: SETUP_FAIL_RNC_HS_DSCH_INT........... 62 3.41 1024 HAND PROCESS ERROR IN PROGRAM BLOCK alarms causing blocked WCELLs ...................................................................................................................................... 63 3.42 Changing LAC in RNW plan doesn't work ....................................................................... 63 3.43 Cell resource status is marked as frozen due to pre-emption in the cell specific AC entity 64 3.44 When ICSU and NPGEP FLTY SWO happens by subrack power off, the automatic IPoA will not run anymore leading cells down ............................................................................. 64 3.45 Layer change denied incorrectly in FACH to DCH transition ........................................... 65 3.46 Counter M1001C397 (RAB_ACT_FAIL_PS_INTER_UE) increased on inter RNC HO border cells.................................................................................................................................. 65 3.47 Iu object deletion needs locking all of WCELLs due to CBS configuration ...................... 66 3.48 DRRC is triggered incorrectly when blind IFHO is enabled ............................................. 66 3.49 Many RRC and RAB KPIs are suddenly degraded.......................................................... 67 3.50 RNC assigned two PSC with the same "intraFreqCellID" in the DL-MC message .......... 68 3.51 UERPRB does not send valid BLER target information to RRC...................................... 68 3.52 problems in AAL2 path (N-CID) release operation affecting to CS and PS access rate 69 3.53 SAS (SIP based Multimedia Application Server) Failover delay...................................... 69 3.54 The threshold alarm 71007 in OMS not forwarded to OSS after MP4............................. 70 3.55 Traffic measurement report e4a event being ignored during HSDPA/16kb UL call ......... 70 3.56 CS RAB establishment failures........................................................................................ 70 3.57 ICSU overload situation ................................................................................................... 71 3.58 RRC creates RLC unrecoverable error............................................................................ 71 3.59 Packet Call Setup Failures due to Other increased ......................................................... 72 3.60 Call setup failures due to hanging DRNC resources ....................................................... 72 3.61 WBTS state change of WBTS between WO and BL(S) observed................................... 73 3.62 RNW plan can not be activated ....................................................................................... 73 3.63 Occasional call setup failure due to incorrect Security Mode Command handling .......... 74 3.64 Occasional NPGEP unit start up failures after RNC reset ............................................... 74 3.65 High OMU CPU loadings ................................................................................................. 75 3.66 Duplicate entries in NE Measurement Explorer Object List field ..................................... 75 3.67 Extra unit restarts during system restart .......................................................................... 76 3.68 Spare ICSU start up failure after RNC restart .................................................................. 76 3.69 Sudden loss of OMU connection ..................................................................................... 77 3.70 Reset and Recovery unit is doing Non performing cell recovery even after WBTS are moved to Working state............................................................................................................... 77 3.71 7762 RNW database operation failure............................................................................. 78 3.72 RNW plan download fails: NO FREE HANDS AVAILABLE............................................. 78 3.73 CHECKSUM check failed for RAQUEL file RAQ2D8QX.IMG ......................................... 79 3.74 Cell PCH counter M1006C93 & M1006C95 updated incorrectly ..................................... 79 3.75 M1023 group (Cell_thrput) reporting multiple MNCs for the same cell ............................ 80 3.76 NPGEP replied ‘ICMP destination unreachable’ with MTU of next hop is 0 .................... 80 3.77 PS addition fails in NB-AMR7.95kbps.............................................................................. 80


3.78 SCTP retransmission in SCTP multihoming .................................................................... 81 3.79 RRC handles timer T315 expiry indication in Cell Update incorrectly.............................. 81 3.80 SP OMU database loading gets stuck ............................................................................. 82 3.81 DSP error after AMR relocation ....................................................................................... 82 3.82 Counter M1010C204 CANC_ISHO_CPICH_RSCP_RT is updated incorrectly............... 83 3.83 RNC sends wrong Activation Time to both UE and BTS ................................................. 83 3.84 Drop Call Followed By MTC Setup Failure - call to voicemail.......................................... 84 3.85 PS Drop due to UE increase after upgrade to PP2.11 (RU20) ........................................ 84 3.86 PS-NRT bit rate is not downgrading to 8/8 kbit/s ............................................................. 85 3.87 RNC OTO restart method does not update SF10E SD4G-A FPGA images.................... 85 3.88 RL deletion is delayed after CS call release and state change to URA-PCH .................. 86 3.89 After direct transition from DCH to PCH, RNC forgets the GTP tunnel ID for the PS RAB 86 3.90 Increase of DSP ERROR 0x7002004B in RN5.0............................................................. 87 3.91 On Top modules are not loaded to units after system restart if OMU fault happens before getting up ......................................................................................................................... 87 3.92 WCEL locking fails ........................................................................................................... 88 3.93 ESA cannot ping directly connected router when one link is down.................................. 88 3.94 Alarm 70030 DISK DATABASE IS GETTING FULL raised but database is never cleared......................................................................................................................................... 89 3.95 70158 alarm on OMS of QYRNC /var/mnt/local/backup is over limit after MP3 .............. 89 3.96 Degradation on Cell-FACH to Cell_DCH transition Success Rate after RU20 implementation ............................................................................................................................ 90 3.97 Occasional call drop due to BRM process exception during HSPDSCH code upgrade .. 90 3.98 HSDPA Code Allocation problem after RN5.0 MP4 Upgrade.......................................... 91 3.99 When incoming AMR “UE not involved” relocation is done from ZTE, NSN RNC releases the call .......................................................................................................................... 91 3.100 RAV on SP-OMU restarted to resolve RAV data checksum inconsistency on WO OMU 92 3.101 Data package drop when bit4 in GTP header is set to 1 instead of 0.............................. 92 3.102 Measurement handler server stops working .................................................................... 93 3.103 RNW plan activation fails with unexpected error ............................................................. 93 3.104 NPS1P failure leading to unit restart................................................................................ 94 3.105 After RU20 MP3.0 upgrade, HS drop due to non-RL increase with RNC DSP error ...... 94 3.106 Counter ICPS_OUTECHO (M563C55) is not updated correctly...................................... 95 3.107 Spare RSMU unit restarted due to ERROR IN SPARE UNIT UPDATE .......................... 95 3.108 Incorrect MSC id for counter M1003C45 NBR_OF_SENT_ERROR_IND ....................... 95 3.109 WBTS and IPNB DSCP values cannot be modified via the RNW plan ........................... 96 3.110 DRRC for HSPA call during transition to Cell_DCH causes periodic location update loop problem................................................................................................................................ 97 3.111 Cell PCH counter is not updated correctly ....................................................................... 97 3.112 Alarm 3485 - Scrambling Code Alarms all over the network ........................................... 98 3.113 Counter M615/267H DSP Resource Utilization counter is not pegging the correct DSP Pools ................................................................................................................................... 98 3.114 Inter MGW load based AMR does not downgrade the codecs to 5.9 .............................. 99 3.115 Alarm 3217 is reported to both 2N units .......................................................................... 99 3.116 DSP Restart due to Fatal Error 0x80000006 ................................................................. 100 3.117 When configuring BFD/ICMP session new call is rejected ............................................ 100 3.118 Huawei-NSN SRNS Relocation UE-involved HSPA failure due to 'Invalid Configuration' ............................................................................................................................ 101 3.119 RNC failing to respond to MTU packet sizes between 1501 to 1505............................. 101


3.120 B1B MSC clear code increased after RU20 - radio link lost during security mode procedure .................................................................................................................................. 102 3.121 RAB NRT Access failure due to Ue increases after RU20 upgrade .............................. 102 3.122 RNC system outage due to OMU unit happen alarm 2690 "POSIX HAS ENCOUNTERED AN UNRECOVERABLE ERROR" ................................................................ 103 3.123 MTU default value problem............................................................................................ 103 3.124 During CELL_FACH to CELL_DCH transition, RBR Complete is not received by RNC 104 3.125 UE is not responding to paging in URA_PCH state ....................................................... 104 3.126 Alarm 3568 IUR INTERFACE SIGNALING FAILURE raised incorrectly in case of UE involved SRNS relocation without IUR interface ....................................................................... 105 3.127 ICSU-12 automatic switchover after 3188 and 1290 alarms occur................................ 105 3.128 Several Node-B sectors going to BL(I) .......................................................................... 106 3.129 Data forwarding support for PS service fails during SRNS relocation ........................... 106 3.130 Cell bouncing problem after CMAS activation ............................................................... 107 3.131 Handsets are not receiving CMAS messages ............................................................... 107 3.132 NWI3TU crash repeatedly after unlocking cell ............................................................... 108 3.133 OMS backup issue......................................................................................................... 108 3.134 PS call drop during state transition/channel type switch (DSP error 70680017) ........... 109 3.135 70273 REQUIRED SERVICE UNAVAILABLE............................................................... 109 3.136 Delay in handling of UL user plane data in case of bursts of small UL packets ............ 110 3.137 RRC Connection Setup Success Ratio Degradation ..................................................... 110 3.138 After fast call setup PCH to DCH transition IFHO failed ................................................ 111 3.139 Alarm-flood of alarms 7750 FAILURE IN WDCMA WBTS O&M CONNECTION .......... 111 3.140 Maximum CPC gain can not be achieved...................................................................... 112 3.141 Reduction in HS throughput data rate after RN5 RU20 PP2.2 + UER ontop SW Upgrade..................................................................................................................................... 112 3.142 Plan operation failure due to internal process crash resulting alarm 70159, NEW........ 113 3.143 High AFR linked to Quality of Service implementation (M1002C555 increasing), NEW 113 3.144 Collision between Cell update (CU) and Security Mode Command (SMC) procedure in RNC, NEW ............................................................................................................................ 114 3.145 Occasional failure in handling of a long SMS in standalone CS signaling connection, NEW 114 3.146 Alarm 1078 Process Exception because RRC in hanging state, NEW.......................... 115 3.147 RNC cannot handle long delayed response to RBR, NEW ........................................... 115 3.148 SRNC relocation rejected when all radio links are under DRNC, NEW......................... 116 3.149 NBAP overload algorithm in IPRAN is too strict, NEW .................................................. 116 3.150 Delay in handling of Location Report procedure, NEW ................................................. 117 3.151 DL DPCH Slot Format change causing drop in SRNS relocation, NEW ....................... 117 3.152 Occasional PS call drop after radio link failure resulting counter M1022C58 HS-DSCH/E-DCH PACKET CALL increase, NEW ......................................................................... 118 3.153 Bad performance accessibility and RNC Hardware Congestion control after Direct Resource Allocation feature activation, NEW............................................................................ 118 3.154 Wcells remain locked after upgrade to RN5.0 MP4 SW, NEW...................................... 119 3.155 Voice quality problem after IFHO due to ciphering mismatch, NEW ............................. 119 3.156 MAC-hs Guaranteed Bit Rate IE value 'zero' is not supported by DRNC, NEW............ 120 3.157 NPGEP sync alarm 3245 appears if WO NPGEP receives continuous ARP packets, NEW 120 3.158 Connection with E398 mobile on some WBTS not possible, NEW................................ 121


3.159 Noise auto tuning resulting too low noise level if BTS uses MHA and reports very low RTWP values, NEW .................................................................................................................. 122 3.160 Not possible to create more than 65535 ADJS objects in RNC by RNW plan operation, NEW ......................................................................................................................... 122 3.161 "M1002C423 SETUP_FAIL_UE_HS_DSCH_BGR" was degraded after HSUPA 2msTTI & HSUPA5.8M activation, NEW................................................................................... 123 3.162 Transport layer address missing in RAB Assignment Response, NEW ........................ 124 3.163 Plan download causes OMS-OMU (EMT) connection break, NEW .............................. 124

4. Generic faults corrected in RN5.0 ........................................................................................ 126 4.1 Generic faults corrected in RN5.0 MP3 ......................................................................... 126

4.1.1 RRC is sending CUC although the RLC has been released 126 4.1.2 Increase of counter M1005C68 (RL DEL ON SRNC DUE TO ACT RL SYN FAIL) since RU20 MP2 upgrade 126 4.1.3 Spikes in HSDPA setup failures due to RNC 127 4.1.4 After signalling connection release, RRC will not handle RRC procedures properly 127 4.1.5 RRC is sending wrong counter (SUM OF HSDPA USER CONNECTION DURATION) value 128 4.1.6 Heavily loaded BTS causes ICSU spontaneous restart 128 4.1.7 DSP's are restarting 129 4.1.8 Alarm cancellation time is reporting as Alarm Generation time in OMS, where as in OMU alarm generated time & Cancellation times are different 129 4.1.9 OMS processes shut down 130 4.1.10 ATM COCO parameter "ALAL2PathType" is empty 130 4.1.11 Warning message for adding to many adjacency 130 4.1.12 The parameter value is changed after plan Pre-Activated 131 4.1.13 Inter RNC SCC fails occasionally if Source RNC Cell and Target RNC cell ids are same 131 4.1.14 RNC does not send band-XI InterFreq UARFCN with "Measurement Control" to Rel8-UE 132 4.1.15 RNW Plan download fail with no free hand 132 4.1.16 M1001C150 RAB_ACT_FAIL_CS_VOICE_RNC counter is increasing in RNC 133 4.1.17 DSP error during Compressed Mode start 133 4.1.18 ICSU RRC process exceptions after RU20 PP2.11 upgrade 134 4.1.19 Radio resource management entity is not able to handle partial failure happening during multiple RL 134 4.1.20 After failed SRNS relocation, RNC did not cancel relocation from the RNC RLC internally 135 4.1.21 TIIPRB process exception 135 4.1.22 RRA restarts (leading to WO-ICSU restart) while restarting traffic 136 4.1.23 Signalling Radio Bearer Enhanced DCH HARQ process ID change problem leading call drop 136 4.1.24 Unnecessary HSPA-R99 channel switch 136 4.1.25 Alarm 3194 LCS CAPACITY FAILURE is increasing gradually 137 4.1.26 WCEL unlocking fails with cause Unknown NBAP interface type after IP WBTS recreation 137 4.1.27 CS Call is dropped after successful RRC Connection re-establishment 138 4.1.28 Iuv master crash if CS domain sends RANAP reset for a relocation failure call scenario 138 4.1.29 SRNC relocation not performed thoroughly 139 4.1.30 M1002 counters not being updated correctly in case of HSDPA/HSUPA drop 139 4.1.31 After RU20 upgrade PS R99 drop rate increase to 2~3% from 0.7%, and HSDPA RAB setup success rate decrease to 98.9% from 99.6% 140 4.1.32 RNTI is not properly released on failed SRNC relocation scenario 140 4.1.33 Call drops after ICSU switchover 141 4.1.34 System failure when WCEL is attempted to be unlocked 141


4.1.35 NSN-Huawei Iur problems after RN5.0 142 4.1.36 Full outage after hard disk or switching fabric unit change 142 4.1.37 SP OMU can't cancel alarm 2816 IP Routing configuration error 143 4.1.38 NRM Process Exception (00020F12) 143 4.1.39 BRM hand process crash 144 4.1.40 WBTS ID included in IuPS route object of measurement M568 144 4.1.41 Some check boxes on OBRO are not controllable 144 4.1.42 BTS alarm cannot be cancel by MML 145 4.1.43 When CN releases tunnel too early, problem in RRC in updating the packet call ticket 145 4.1.44 UER provide process exception 146 4.1.45 Packet loss during RB reconfiguration 146 4.1.46 In AMR+R99 multi call case RNC does not change PS data rate after AMR release 147 4.1.47 RRC process exception 147 4.1.48 RRC access failures in RNC boundary 148 4.1.49 RM3 error in SP unit update during mass DMPG restart 148 4.1.50 Shutdown of remaining cell in PWSM RU20 PP2.03 doesn't work properly 149 4.1.51 Increment of Admission Control failures after activation of feature RAN1686 HSPA 72 Users Per Cell 149 4.1.52 RNC does not receive RadioBearerReleaseComplete message. 150 4.1.53 Some UEs are failing in MOCN relocation 150 4.1.54 HMS upgrade failed on some TBUF units 151 4.1.55 Re-establishment not successful after incoming ISHO from 2G causing AMR call drop 151 4.1.56 WCEL parameter modification problem 152 4.1.57 COCO detach during fallback copy making and COCO attach then COCO status is not WO 152 4.1.58 Unreasonable high value for M802C17 (AVE_RRC_CONN_MODE_USERS) and M802C18 (MAX_RRC_CONN_MODE_USERS) 153 4.1.59 HSDPA cannot be enabled in VCEL object 153 4.1.60 COCO modification failed with CM plan 153 4.1.61 M1006C188 RRC_RE_EST_FAIL_NOREPLY_RT counter not incrementing 154 4.1.62 Several DSP severe errors increasing call drops 154 4.1.63 CellUpdate over Iur after radio link failure does not update RAB active drops counter 155 4.1.64 UER sends uninitialized information to RRC 155 4.1.65 Packet loss during SRNS relocation procedure 156 4.1.66 Many sites down during the upgrade to RU20 156 4.1.67 TCP/IP ATM interface can not be deleted after upgrading RNC to RU20 MP2 PP2.03 157 4.1.68 Increase in NRT compressed Mode triggers in RU20 157 4.1.69 RAB_ACT_FAIL_PS_INTER_IU incorrectly updated 158 4.1.70 DMPG restarted due to no response to AAL5 CHANNEL SUPERVISION 158 4.1.71 Increase seen in Alarm 1078 Process exception 159 4.1.72 Degradation in IFHO (PS) KPI 159 4.1.73 HS Failure increase since PP2.11 on small number of sites 160 4.1.74 SIR error causes PS DCH bit rate downgrade during Compressed Mode after Iur HHO leading synchronization loss 160 4.1.75 Support for 72 HSPA users in a cell is not working simultaneously with HSUPA peak rate enabled in cell 161 4.1.76 Hanging RRC-D hand 161 4.1.77 All RLs are released when deactivating PS session from AMR+PS 0kbps during Compressed Mode 162 4.1.78 IP upload is failing 162 4.1.79 DSP Supervision Failure due to Fatal Error 80000003 causing a DSP reset 163


4.1.80 WCEL states incorrectly reported in NetAct RU20 163 4.1.81 Power control fails if FDPCH used 164 4.1.82 PS throughput is not restored while deactivating compressed mode 164 4.1.83 Incorrect values in M553 counters 165 4.1.84 Problem activating/deactivating Power Saving Mode for BTS, HSPA reconfiguration failed and cells remains in BL(I) after lock/unlock 165 4.1.85 70245 ILLEGAL INTERNAL USAGE OF EXTERNAL ALARM NOTIFICATION FORMAT 166 4.1.86 UL temporary lowered bitrate cannot be increased to 384 if BitrateSetPSNRT is ON 166 4.1.87 Reduced downlink throughput during SCC between DC-HSDPA&16QAM cells 167 4.1.88 WBTS not showing alarms when it is off air 167 4.1.89 LU Limiter too strict for busy RNCs 168 4.1.90 Inter Frequency H/O fails then UE does not receive Physical Channel Reconfiguration 168 4.1.91 Dual Cell HSDPA feature can't be activated without 15 HS-PDSCH codes 169 4.1.92 Spare RSMU restarted during DSP pool reconfiguration 169 4.1.93 HS-DSCH setup failure due to RNC for interactive 170 4.1.94 Cell BTS manager Block/Unblock causes sleeping cells 170 4.1.95 PS NRT DCH downgrade failure due to Iub AAL2 congestion causes pre-emption failure 171 4.1.96 RAN930 PS RAB Reconfiguiration doesn't work properly when HSPApeakratelimitmax is set to 1 (Limitation is active) 171 4.1.97 No PM data M568 (IP base route counters) after NPGEP-0 switchover 172 4.1.98 RU20 PP2.01: ALARM: HSDPA CONFIGURATION FAILED: RNC INTERNAL ERROR 172 4.1.99 CS RAB drop increase after HSPA over Iur activation 173 4.1.100 M1010C30 IS_HHO_ATT_CPICH_RSCP_RT counted on WBTS-0 after RAN1758: Multiple BSIC Identification activation 173 4.1.101 Dual Cell cannot be setup on certain WBTS 174 4.1.102 HSPA traffic allocation problem after pool optimization 174 4.1.103 DMCU automatic Unit Restarts in overload conditions (a submodule of CDSP-DH goes into SW recovery) 175 4.1.104 CU from UE during ongoing RAB setup in Cell_FACH is not handled correctly 175 4.1.105 When cell_FACH to cell_DCH transition is tried for PS NRT on HSPA, HSDPA is allocated 176 4.1.106 Domain-specific access control (DSAC) restrictions are not working 176 4.1.107 Random ICSU load (100%) peak since RU20 PP2.1 upgrade 177 4.1.108 JAFFIS consumed CPU load and hanging hand was observed 177 4.1.109 After command calendar triggered fallback, system did a full restart 178 4.1.110 Cable configured with “no direction” remains after SW upgrade 178 4.1.111 HSDPA will drop to R99 and won't come back to HSDPA after RU20 upgrade 179 4.1.112 Two ADJG objects pointing to same target WCEL exist in the same cell 179 4.1.113 Traffic Volume Measurement failure sent by UE occasionally in FDPCH setup 180 4.1.114 IUETOR Actor Exception causes NPGEP restart 180 4.1.115 Degrading in HSUPA traffic volume after MP2 181 4.1.116 RRC tries DC-HSDPA with secondary cell for REL6 and REL7 UEs 181 4.1.117 Low setup SSR HSDPA, HSUPA R.99 for UMTS network 182 4.1.118 ATM end point state mismatch 182 4.1.119 RNC450 to RNC2600 HW upgrade: some DMCUs may fail after reverse cutover 183 4.1.120 Problem with RNC196 step 5 upgrade to step 7 183 4.1.121 During DMPG multi restart DSP fatal error 3d 8FFFFF97 184 4.1.122 HSDPA serving cell change fails occasionally 184 4.1.123 Strange SCCPCH3 allocation on spreading factor 185 4.1.124 KIDATA error message 11991 appears when IPNB is deleted and created again having WBTS already attached 185


4.1.125 Cannot connect U-Plane after setting HSUPA with VCC bundle 186 4.1.126 When system is restarted by operator during traffic, SP OMU turned to TE state 186 4.1.127 Missing RadioBearerReleaseComp during the release of PS NRT call 187 4.1.128 ICSU load increase in RU20 187 4.1.129 Alarm 3384 (HMS TRANSMISSION LINE FAULTY) was generated when turn off the power from the sub rack and then TBU became unstable 188 4.1.130 After SRNC relocation from mac-ehs capable cell under Rel 7 RNC to RNC version below Rel 7, PS NRT UL throughput is unstable 188 4.1.131 Increased RAB setup failure ratio for PS calls after RN5.0 PP1.1 upgrade 189 4.1.132 Occasional DSP restarts 190 4.1.133 RNC450 to RNC2600 HW upgrade: DSP-DSP channel opening failure (alarm 3343) 190 4.1.134 Internal problem blocks single DMPG causing HSxPA drop rate increased due to RL 191

4.2 Generic faults corrected in RN5.0 MP4 ......................................................................... 192 4.2.1 RRC process exception after failure in handling of Signalling Connection Release Indication from UE 192 4.2.2 Not able to collect alarm history (zahp) from OMS 192 4.2.3 Hanging AMR DCH causing lot of packet call setup failures by single UE 193 4.2.4 OMS internal measurement handling process restarted in case of long WBTS name 193 4.2.5 OMS error 70159 MANAGED OBJECT FAILED 194 4.2.6 Timezone was not changed with changetimezone.sh script 194 4.2.7 ISHO failure counters are incorrectly updated after successful ISHO from 3G to GSM 194 4.2.8 Call drops after RNC relocation 195 4.2.9 Bootprom upgrade execution (ZWDR) fails with empty info field 195 4.2.10 ICSU got restarted automatically 196 4.2.11 Setup Fail Other counter (M1022C19) increased in case of RL setup failure during state transition 196 4.2.12 High increase in Packet Service RAB Setup Failures due to RNC after MP1 upgrade 197 4.2.13 Call drop since IUR is not sending response to dedicated measurement requests / terminations to SRNC 197 4.2.14 Occasionally RRC was not prepared to handle a new Initial Direct Transfer message. 198 4.2.15 NPGEP go to overload situation 198 4.2.16 Occasional call drop in case of RL failure 199 4.2.17 Physical Channel Reconfiguration Failure scenario handling improvement in RRC to avoid CU due to RLC unrecoverable error for the user plane 199 4.2.18 State transition to DCH fails if lossless PDU size change is used 200 4.2.19 Call Control not handle the Security procedure cancellation correctly 200 4.2.20 HSPA duration counter increased incorrectly in case of incoming SRNS relocation 201 4.2.21 AMR call setup failure due to DSP error 201 4.2.22 HSPA throughput degraded after inter-RNC handover 202 4.2.23 Internal timer handling problem UE involved relocation is interrupted by Cell Update 202 4.2.24 Degraded CSSR performance due the overloaded CDSP-C card DCH DMPG units 203 4.2.25 After partial failure during SHO of Multiple RL then UE Radio resource Management is not handling further processing request 203 4.2.26 After OMU switchover, GTP call cannot be created 204 4.2.27 Alarm 3986 ATM INTERFACE OPERATIONAL STATE CHANGE TO DISABLED was not cancel in RNC upgrade 204 4.2.28 CoCo modification is not possible 205 4.2.29 Incorrect UL initial bit rate selected for the second PSNRT RAB 205


4.2.30 ZT2C command cannot be executed via command calendar 206 4.2.31 Output of ZNVI command shows abnormal printout 206 4.2.32 No alarm when the control plane routes are not configured in RNC 207 4.2.33 Not possible to delete network interface 207 4.2.34 Spare update failure will cause 1258 alarm which lead to NPGEP spare unit restart 208 4.2.35 RNC sends successful RAB Assignment Response even if IuUP Initialization fails 208 4.2.36 Alarm 3385 PLUG-IN UNIT INSTALLATION ERROR occurs on RU20 MP3.0 208 4.2.37 DRNC allocated binding id is corrupted when it is sent over the IUR to SRNC 209 4.2.38 Due to RRC internal timer ongoing FACH relocation doesn't complete successfully resulting in HPL log writings 209 4.2.39 Bad manner of SNMPRO causes unexpected SIB updates 210 4.2.40 HMS system cannot set subrack fan speed which cause alarm 3198 (FAN SPEED CAN NOT BE SET) 210 4.2.41 Working SFU spontaneous restart 211 4.2.42 After SP-NPGEP restart some OSPF route is lost on SP-NPGEP 211 4.2.43 Increase in HCAP counters specifically HCAP_IFHO_MEAS_START_FAIL 212 4.2.44 Counter M1006C151 the number of attempted state transitions from FACH to HS-DSCH updated incorrectly during PCH-DCH transition cancel 212 4.2.45 Alarm 1078 resulting call drop 213 4.2.46 PS service abnormal after NPGEP switchover with FCD option 213 4.2.47 IUV sends an empty location report message to CN. 214 4.2.48 Inter-RNC handover failure with HSPA over IUR enabled 214 4.2.49 RRC hand crashes after receiving two Cell Updates from the UE 215 4.2.50 Fractional DPCH never activated at RRC connection setup 215 4.2.51 ZWPD command executed without warning message and customer confirmation 216 4.2.52 CS call setup fails due to cell update not handled correctly in cell_DCH state 216 4.2.53 Iub AAL2 signaling congestion control improvement 217 4.2.54 HS layer disabled but operational state enabled 217 4.2.55 Alarm 7771 WCDMA CELL OUT OF USE is not canceled correctly 218 4.2.56 AMR call rejections due to lack of DSP capacity 218 4.2.57 Fallback does not copy command calendar file (CTRCALGX.MIF) 219 4.2.58 Diversity handover was rejected by RNC admission control incorrectly 219 4.2.59 Inter-system handover from 2G to 3G fails when UE capability information is not available 220 4.2.60 HSPA Handover failure 220 4.2.61 RRC Connection Release is triggered due to Iu Release Command from CS domain 221 4.2.62 Ongoing FACH relocation incorretly handled resulting HPL log writings 221 4.2.63 Counter Compressed Mode Not Possible for NRT call updated incorrectly 222 4.2.64 Unable to associate COCO to WBTS 222 4.2.65 Unnecessary ISHO attempts after state change from DCH 0/0 to DCH with bitrate allocation 223 4.2.66 Alarms 7750 FAILURE IN WCDMA WBTS O&M CONNECTION 223 4.2.67 Call setup failure due to incorrectly handled RRC Connection Release procedure 224 4.2.68 Alarm 1078 due to RRC PROCESS EXCEPTION 224 4.2.69 Download IP plan to change bandwith is not possible 225 4.2.70 Paging degradation, 3G-2G IRAT RT HOF and 3G-2G RT ISHO failures post Iu-CS-IP 225 4.2.71 Alarm 1304 ACTOR EXCEPTION was generated from DMPG after bblog -command 226 4.2.72 Improvement of corrupted PDU handling (corrupted UL Cell update message from UE ) 226 4.2.73 RAB Reconfiguration failed due to RL failure during state transition 227 4.2.74 Unnecessary alarms 7772 and 7771 during cell shutdown when activating PCH 24kbps 227


4.2.75 Increase of RAB setup failures CS voice due to AC in case iBTS sharing relocation from ADA to RNC 228 4.2.76 Transport_resource_release_s message cause process exception 228 4.2.77 RRC sends an unnecessary M1022 ticket for cancelled UP setup 229 4.2.78 Call setup failure if FACH to DCH state transition in cancelled during ongoing location update 229 4.2.79 RRC gets confused with first CU over IUR received then CU from same RNC 230 4.2.80 Security Mode command not sent out from RNC when UE is in transition Fach - PCH 230 4.2.81 CS calls not possible since incoming relocations from ADA were rejected in RNC 231 4.2.82 HSUPA related (ERGCH/EHICH) DL spreading codes were left hanging in RNCs code resource tables 231 4.2.83 Corrupted downlink Echo Reply resulting to lost ping 232 4.2.84 M1001C16 RRC_CONN_ACT_FAIL_RADIO_INTERFACE updated incorrectly if CU received from DRNC 232 4.2.85 HSDPA Setup Failures in case of Iub congestion 233 4.2.86 Timeout in pinging the server after PDP context activation 233 4.2.87 Alarm 71007 are not reported anymore on NetAct after RNC SW upgrade MP3 234 4.2.88 RNC restart in case other WDU has hardware problem even another WDU is fine 234 4.2.89 Transport resource manager sends resource allocation message to non-existing Layer 2 PRB hand 235 4.2.90 CSSR Call Setup Success Rate for voice counters are not accurate 235 4.2.91 Call failures due to DSP errors (code 7008003a, 701f0023 and 70090011) 236 4.2.92 Service area broadcast process restarted when the operator changed the IP address of CBC 236 4.2.93 DSP restart due to fatal error 237 4.2.94 Inconsistency in counters for Paging in Cell PCH 237 4.2.95 All IUR BFD session gone and creation of BFD session ends up with error 238 4.2.96 Radio Bearer Reconfiguration procedure incorrectly completed resulting RLC error238 4.2.97 DSP SUPERVISION FAILURE with fatal error code 80000003 and extra info 0000000E 239 4.2.98 Partial backup size of OMS has decreased after MP3 239 4.2.99 Some of the counters are missing from Key Counters measurement (M1050) while transfering to NetAct 240 4.2.100 Cell Availability affected due to CCH DSP resets 240 4.2.101 Alarm 1078 indicating PROCESS EXCEPTION after CS call setup failure 241 4.2.102 Retry of Cell_DCH state transition with lower bitrate is not done correctly 241 4.2.103 HSDPA retainability below 60% 242 4.2.104 Direct RRC (DRRC) failures to HSDPA layer increasing RRC Access Failures due to RADIO 242 4.2.105 DMCU failed to come up after RN5.0 PP2.11 243 4.2.106 15th HS-PDSCH code not allocated if 72 HSPA Users Per Cell feature is enabled 243 4.2.107 During call release GTP tunnel remains hanging 244 4.2.108 SIB2 is transmitted even URA_PCH is not used 244 4.2.109 MXU problem leads other units to go faulty or restart too 245 4.2.110 Cell_PCH state counters increase since Cell_PCH transition happens even MsActivitySupervision is 0 245 4.2.111 WB-AMR CS over HSPA setup failure after state transition from FACH 246 4.2.112 Access restrictions are not applied in the SIB3 when changed by the operator 246 4.2.113 Alarm 7771 is visible for WCEL blocked by user 247 4.2.114 Unneccessary delay of sending iur rl addition request 247 4.2.115 Incorrect display of HSDPA calls on BTS Connection Resource 248 4.2.116 Call drop in SHO for CS over HSPA 248 4.2.117 SRB on DCH/HSUPA 2ms and PS streaming call on HSPA allocated which is invalid transport channel combination 249 4.2.118 Boot proms update execution failed 250


4.2.119 Iu connection towards CS CN fails occasionally due to incorrect MCC and MNC values sent to CN 250 4.2.120 Occasional MTC call failure due to failure in signalling connection release 251 4.2.121 HSPA data break with RN5.0 MP3 251 4.2.122 Spontaneous SP RSMU restart 252 4.2.123 PS service abnormal after NPGEP switchover with FCD option 252 4.2.124 Wrong counter values updated when Radio link reconfiguration request is internally rejected by RNC due to IUB link overload 253 4.2.125 Transport resource manager was not configuring PDCP when PDU size got changed in Serving cell change scenario 253 4.2.126 No fractional DPCH calls after disabling QoS Aware scheduling feature 254 4.2.127 Boot prom updating printout changed to be line with real updating situation 254 4.2.128 Service request nack from NRM PRB for CS over HSPA 255 4.2.129 PS call setup failure if DRRC is perfomed during Cell_FACH to Cell_DCH state transition and Iub transport is congested at the same time 255 4.2.130 UE cannot access a cell if operator configures ADJS/ADJI to SIB11 bis and uses HCS 256 4.2.131 RNW Configuration Manger is not setting bitmask os SIB3 for parameter Shcs_RAT when HCS is not in use 256 4.2.132 Unlocking HSPA-WCELs not able on any Dual-Iub site 257 4.2.133 Some F-DPCH parameters cannot be modified if QoS aware HSPA scheduling was disabled 257 4.2.134 Several DSPs in restart loop 258 4.2.135 Counter M1002C416 HS Access FAIL BTS incremented unnecessarily 259 4.2.136 Counter M1002C526 SETUP_FAIL_EDCH_BTS_BGR incremented unnecessarily 259 4.2.137 Small degradation in HSDPA Serving Cell change Success rate after the CPC activation 260 4.2.138 Call drop due to SHO failure resulting increase of Counter M1022C20 PS_SETUP_FAIL_OTHER_BGR 260 4.2.139 Cell is not operational due to WCEL initialization failure 261 4.2.140 NP2GE-B PQCPU diagnostic problem 261 4.2.141 WDU and SCSI LCK and WDU broken, no alarms raised 262 4.2.142 The cyclic restart of spare NPGEP 262 4.2.143 Unexpected NBAP RL deletion with CPC call 263 4.2.144 Mute calls increase/data througput low when RNC has no cable connection to some unit related to external IPOA. 263 4.2.145 DHCP server configuration delete fails 264 4.2.146 Ping lost due to collision between RLC resume and suspend 264 4.2.147 Decreased HSDPA throughput in a cell 264 4.2.148 Process exceptions during state transition from Cell_FACH to Cell_DCH in case of transport congestion 265 4.2.149 NBA PRB hanging after "nbap_cell_delete_req" message received on RU20 MP2 266 4.2.150 Latency and packet drop increased in network 266 4.2.151 HSPA over Iur UL RL Reconfiguration failure after AMR call release resulting PS call drop 267 4.2.152 SAB signalling throughput goes down leading cell state set as blocked periodically 267 4.2.153 Alarm 7771 was activated during cell shutdown 268 4.2.154 Occasional call drop after relocation from ADA to RNC due to failure in CFN calculation 268 4.2.155 DMPG load increased due to DSP connection was lost on RNC2600 environment 269 4.2.156 CS call setup failure after incoming I-BTS sharing relocation 269 4.2.157 Alarm 70159 increased due to OMS subsystems EmiCMOS and DXDIAG problems 270 4.2.158 Unexpected RL deletion during F-DPCH call on IP IUB Node-B 270 4.2.159 Increase the counter M1001C6 (RRC_CONN_STP_FAIL_RNC) number of RRC setup failures caused by RNC internal reason. 271


4.2.160 Unable to access external storage media on RNC's 271 4.2.161 Call setup failure after LU fails due to RL failure 272 4.2.162 RRC rejections due to IUB caused by NBAP OLC functionality with narrow Iub configuration 272 4.2.163 Illegal values from OLPC (outer loop power control) measurement 273 4.2.164 Decreased of DC and MIMO HSDPA call throughput 273 4.2.165 RNC Overload Control - Iub Smart Overload/Congestion Control for AAL2SIG 274 4.2.166 Platform alarm not visible in active alarms or alarm history 274 4.2.167 PS calls not possible after upgrading to RU20 PP2.11 275 4.2.168 Optional SIB optimization improvement PRFILE activation failed 276 4.2.169 Alarm 70159 was not cleared after cluster restart 276 4.2.170 Alarms 3344 UX LINK CONNECTION FAILURE cause MXU fault switchover 277 4.2.171 SF10E SD4G-A HW block bitstream downgrade 277 4.2.172 Incorrect counter update instead of normal release if HSDPA release due to inactivity after relocation 278 4.2.173 RNC Handover failure between ALU-RNC and NSN-RNC 278 4.2.174 Missing daily 1013 AutoDef SHO measurement files 279 4.2.175 Packet loss and duplicate packets in NSN RAN 279 4.2.176 Occassional call drops due to DSP severe errors 7002001a/006700b1, 700b0005/0, 7002001d/00670010 and 700b0016/0 280 4.2.177 After adding CS over HSPA in FACH state PS UP data can not go smoothly (several ping lost) 280 4.2.178 HSDPA throughput ramping has increased from 2-3 sec to about 15 sec 281 4.2.179 RNC450 to RNC2600 HW upgrade: OMU faulty switchover cause by active OMU restart 281 4.2.180 Cell resource counters (M1000) updated incorrectly 282 4.2.181 Plan upload failed with very large network configuration 282 4.2.182 Alarm 1239 and DSP restarts (code 80000007) leads to 100% DMPG Load 283 4.2.183 A2SPs restarting periodically 283 4.2.184 Occasional HSDPA throughput degradation after SCC 284 4.2.185 CPU usage increased to ~100% after login to OMS Web UI and selecting some menu entry 284 4.2.186 Measurements from random RNCs are being sent to the OSS corrupted 285 4.2.187 Bootprom upgrade during RNW startup caused OMU restart 285 4.2.188 Increase of PS AFR due to AC 286 4.2.189 Delayed DNS requests caused by RNC leading loss of PS service availability 286

Contact:

Contact your local Nokia Siemens Networks support.

Summary of changes:

30-10-2011 1.0 The first version of document.


PURPOSE

List of Generic Faults is a summary of outstanding system faults containing the problem description and the target correction schedule.

1. RNC SW RELATED OUTAGES ANALYSED P10 2011

In this chapter are listed lately reported critical RNC SW faults, which have caused major impairment of services from the operator or end user point of view. These cases have been reported as Emergency Cases for NSN.

1.1 MXU not coming up after MP4 upgrade

Emergency Case Number: NA04980083

Follow up Case Number: NA04980619 Reference case: Exists in: RN5.0 MP4 Correction Target: RN6.0 Severity: A – Critical Customer Impact: Capacity & Performance Attached PRs: - Probability: One occurrence Description: After installing the RU20 MP4.0, two MXUs in Subrack 1 did not start-up. MXU start-up failure caused the tributary units in same Subrack not to start-up (ICSU, DMCU). Because DMCU unit remain in restart phase, interface units (NPGEP or NPS1P) can't go to WO-EX/SP-EX state. MXU couldn't open internal ATM channel correctly. And tributary unit status delay the status change of the interface unit Solution / Workaround: Power off the whole RNC and then power on firstly subrack1only. Then power on for rest of the RNC. After this all units came up successfully. Impact to Operator: Capacity & Performance Impact to End user: No service.

1.2 A number of signalling links and WBTS down

Emergency Case Number: NA05012817, NA05012846

Follow up Case Number: NA05010993 Reference case:


Exists in: RN5.0 MP3 Correction Target: RN5.0 MP5 Severity: A – Critical Customer Impact: Capacity & Performance Attached PRs: - Probability: Occasional Description: WBTSs and Iu signalling under several NPGEPs were down. The disturbance caused system wide data packet corruptions and it got some HW blocks permanently to some kind of faulty state where they did not transfer data packets anymore. Solution / Workaround: NPS1 and NPGEP Switchovers . After the switchovers WBTSs and Iu signalling link recovered. Impact to Operator: Capacity & Performance Impact to End user: calls may fail.


2. GENERIC FAULTS OPEN IN RN4.0

2.1 Calls to voice mail if MTC paging was received during CS re-establishment

Problem report: NA04782840 Exists in: RN4.0 Correction Target: RN5.0 PP1.3, RN5.0 PP2.1 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: Problem was that occasionally RNC did not forward the Direct Transfer message from UE to the CN if MTC paging was received during ongoing CS re-establishment. This was caused due to RNC which did not release signaling connection for CS CN when the MTC paging was received, so UE had the connection still towards that CN domain while RNC and CN did not have. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: No impact.

2.2 Multi-RAB calls drops in congested cell

Problem report: NA04824856 Exists in: RN4.0 Correction Target: RN5.0 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: - Probability: Permanent Description: If SHO happens in case of AMR + PS to a congested cell, then call may drop if there is congestion in that cell and NRT downgrade is triggered. Solution / Workaround: No workaround. Impact to Operator: KPIs, PS Completion Setup Impact to End user: Multi-RAB call drops.

2.3 KPI degration occured after network interface modification by ZQRG


Problem report: NA04868456 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: NA04860418, NA04790275 Probability: Permanent Description: IP interfaces binding with IP based route are lost in the XIPIFC1X.XML file. It leads to all the PS calls cannot be created successfully. All the IP configurations are stored in buffer. When the IP interfaces buffer is over-written because the buffer is not protected properly for the parallel operation. The corrupted items will not be written into the XML file. Solution / Workaround: 1. Copy the fallback XIPIFC1X.XML into the current package. 2. Restart SP OMU with DSK mode. 3. After SP OMU enter SP-EX state, do OMU switchover. 4. Restart new SP OMU with DSK mode. Impact to Operator: Capacity & Performance: Call setup success Impact to End user: Call setup fails.

2.4 BRM hand process crash

Problem report: NA04819088 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Stability Attached PRs: NA04818175 Probability: Permanent Description: This problem was caused by failing BRM when updating overload control related information element in call allocation phase. Failure caused, because BRM was left stuck in a loop without recovery. Solution / Workaround: No workaround. Impact to Operator: Stability, occasional WBTS restarts Impact to End user: Occasional dropped call.

2.5 Output of ZNVI command shows abnormal printout

Problem report: NA04843388


Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: NVI MML command does not show all signalling routes of signalling route set even the routes exists in the system and files. This was because the MML output was not called properly. Same data can be seen correctly with other MML commands, like NRI or NER. Solution / Workaround: No workaround Impact to Operator: Operability Impact to End user: No impact

2.6 DSP's are restarting

Problem report: NA04758263 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If reserved DMCU resources were released during the last Cell_FACH to Cell_FACH transition then they need to be reserved again during Cell_PCH to Cell_FACH transition. Due to internal data structures not set correctly, RRCPRB forgets to ask to reserve the resources for the user RB and this cause later problem in the state transition to Cell_DCH causing invalid request to be sent to RNC L2 and Transport Manager in the RNC. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: No impact.

2.7 PJOTOR has hanging RAB resources after overload situation

Problem report: NA04721279 Exists in: RN4.0 Correction Target: RN5.0 PP2.1


Severity: B - Major Customer Impact: Capacity & Performance Attached PRs: - Probability: Permanent Description: If the CPU load persists long enough in DMPG, there will occur hanging resource reservations, which eventually leads to the situation where creation of new RABs is rejected by PJOTOR. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance Impact to End user: No impact.

2.8 Not possible to perform increment installation after full restore

Problem report: NA04690089 Exists in: RN4.0 Correction Target: RN5.0 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: OMS RN4.0 CD2.0 OMS 4.46 SW USB installation does not create /var/mnt/local/sysimg/tmp. As the tmp directory is excluded in the backup archive, after full restore if increment installation is performed, it will create problem in SS_Errata, which is the only sub-system with an rc0.d script using the tmp directory and it is not possible to perform increment installation. Solution / Workaround: If the RN4.0 CD2.0 OMS SW 4.46 has been installed as an USB installation, directory /var/mnt/local/sysimg/tmp are missing. Create the tmp directory manually before installing additional increments. Execute the following commands: # mkdir -p /var/mnt/local/sysimg/tmp # chmod 1777 /var/mnt/local/sysimg/tmp" Impact to Operator: Operation & Maintenance Impact to End user: No impact.

2.9 Bootprom upgrade execution (ZWDR) fails with empty info field

Problem report: NA04890035 Exists in: RN4.0


Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Boot programming (ZWDR) shows empty info field. This is caused because CBYPRB does not properly handle internal timer. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact

2.10 Working SFU spontaneous restart

Problem report: NA04870261 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, Unit restart Attached PRs: NA04988185 Probability: Permanent Description: Problem was that the WO-EX SFU get spontaneous restart. That was caused because CPU was stucked after accessing one SF10E's hardware register. Solution / Workaround: No workaround Impact to Operator: Unit restarts Impact to End user: No impact

2.11 Multi-RAB call drop

Problem report: NA04791969 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: A - Critical Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: -


Probability: Permanent Description: In case of AMR + HSDPA call ongoing, and soft handover to new cell fail then RNC tries to perform handover to that cell again after downgrading PS NRT to 0/0 but due to internal problem in the handling of PS NRT downgrade procedure, call is dropped. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance/Call completion success Impact to End user: Dropped call.

2.12 M1001C150 RAB_ACT_FAIL_CS_VOICE_RNC counter is increasing in RNC

Problem report: NA04805321 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: Due to wrong data received in RANAP: RELOCATION REQUEST message, RANAP protocol PRB was going down which leads to all the ongoing calls on the same ICSU are released. Solution / Workaround: No workaround. Impact to Operator: Call drop rate increases. Impact to End user: Call drops.

2.13 Terminating Low Priority Signaling cannot initiate RT over NRT

Problem report: NA04796190 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: B - Major Customer Impact: Capacity & Performance, RRC success Attached PRs: - Probability: Permanent Description: Problem is that resource congestion in the RAN can cause delayed SMS deliveries. This is caused by the following issue in RNC. In RRC connection establishment phase the establishment causes that can initiate RT-over-NRT actions in case of resource congestion do not include Terminating Low Priority Signaling cause. This cause has been


originally left out as MSC/SMS center will periodically retry SMS delivery. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, RRC success Impact to End user: No impact.

2.14 Alarm7652/7750 alarm type mismatch between NE/OSS

Problem report: NA04769728 Exists in: RN4.0 Correction Target: RN6.0 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Occasional Description: If a minor fault (or faults) has occurred in the base station. BTS sends notification in alarm 7652 to RNC. As per alarm manual, alarm 7652 is by default of type Quality of service. But when checked in alarm history, its type is shown as Equipment which is not as per the default value defined for the alarm 7652. Solution / Workaround: No workaround. Impact to Operator: Operation and maintenance Impact to End user: No impact.

2.15 ISHO 2G to 3G drop

Problem report: NA04791214 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: After ISHO from 2G to 3G, if UE drops to Cell_FACH during SRB4 setup due to radio link failure then UTRAN does not initiate RRC Connection re-establishment procedure for CS even if T314=0 causing the call to be dropped. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance/Call completion success


Impact to End user: Dropped call.

2.16 ICSU connectivity algorithm to consider cells per site as weighting factor

Problem report: NA04757720 Exists in: RN4.0 Correction Target: RN5.0 PP1.3, RN5.0 MP2 Severity: B - Major Customer Impact: Capacity & Performance Attached PRs: - Probability: Permanent Description: When a BTS is connected to IPNB/COCO object the ICSU is selected. Currently there is no means to define any weight for the created connection so that same size sites would be equally distributed over different ICSU units. Solution / Workaround: Small BTSs can be disconnected from their COCO/IPNB objects from ICSUs that have lower load than others. Then some large BTSs from higher loaded ICSUs can be disconnected and connected from their COCO/IPNB objects after which they are likely connected to the ICSU that has lowest level of signalling links. Impact to Operator: Capacity & performance Impact to End user: No impact.

2.17 Call setup failure due to connection error

Problem report: NA04747262 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Occasional Description: If RNC receives MTC paging for UE immediately after CN had asked last CS signaling connection to be removed then it can cause occasionally paging to be missed because RNC sends Signaling connection release indication to UE only after all SRBs RLC transmission buffer is empty but paging is still sent. So RNC sends first paging to UE and then signaling Connection Release which causes paging to be missed. Solution / Workaround: None. Impact to Operator: Capacity & Performance / Call Setup Success


Impact to End user: Call setup failure.

2.18 Occasional NRM process exception during intra RNC IFHO

Problem report: NA04776429 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: C - Minor Customer Impact: Operation & Maintenance, alarms Attached PRs: - Probability: Occasionally Description: If UE had DL PDU size 656 configured before Intra RNC IFHO and the RLC size was not changed during the IFHO procedure, RNC did not handle the IFHO procedure correctly resulting process exception. Solution / Workaround: NA Impact to Operator: Operation & Maintenance / Alarms Impact to End user: No impact

2.19 When SCTP state is down in association set, there is no active alarm in RNC2600

Problem report: NA04776945 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: B - Major Customer Impact: Operation & Maintenance, sub category: Alarms Attached PRs: - Probability: Permanent Description: When activation of the SCTP association doesn't succeed because of configuration error, there should be alarm 3159 in the client end too. Solution / Workaround: No workaround. Impact to Operator: Operator didn't detect the association configuration errors based on active alarms. Impact to End user: No impact.


2.20 Call setup failure if previous RAB setup failed

Problem report: NA04723676 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: B - Major Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Occasional Description: RNC did not send Release Request to CN, if no answer from UE was received during AMR call setup when UE was in Cell_FACH state resulting that new call can't be setup immediately. Solution / Workaround: NA Impact to Operator: Capacity & Performance / RRC Success Impact to End user: Call setup fails

2.21 OMS AlarmProcessor non-responsive - leading to 9047 alarm in Netact

Problem report: NA04639256 Exists in: RN4.0 Correction Target: RN5.0 MP2 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Alarm System MySQL database was stuck due to "Lock wait timeout" exceptions. As the result alarm processing didn't function and alarm flow was interrupted. Solution / Workaround: Deleting and recreating Alarm System database with deleting alarms file. Impact to Operator: Operation & Maintenance Impact to End user: No impact.

2.22 False cell alarm 7771 CELL OUT OF USE



Correction Target: RN5.0 PP2.1 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: After receiving audit failure from Node-B, the RNW reset and initialization module of RNC indicates alarms for cell out of use but the cells are not disabled. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance Impact to End user: No impact.

2.23 SHO with Huawei being removed due to rnc_rab_no_sync_s

Problem report: NA04787447 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: A - Critical Customer Impact: Stability Attached PRs: 73993ESPE02 Probability: Permanent Description: In SHO situation with Huawei the adding cell is successful but the same cell is removed from active set due to [RRC:-rnc_rab_no_sync_s] after 4-5 seconds. Solution / Workaround: No workaround. Impact to Operator: Stability Impact to End user: Possible call drop.

2.24 Excessive ICSU log writing coming from DI5_FISH_M1022C9 RN4.0 CD1.35

Problem report: NA04678003 Exists in: RN4.0 Correction Target: RN5.0 MP1 Severity: B - Major Customer Impact: Operation & Maintenance, Internal log system Attached PRs: - Probability: Permanent


Description: In RNC, the measurement counter updating information is either written to logs for verification or sent in message to self. But sometimes the log printing method cause lots of log writings and therefore leaving no space in log buffer for important problem logs. When the log writing is turned off, the information should instead be included into the message itself, which is the second way to verify the counter update. But this was not happening. As a result of turning off these log writings, the message was also not sent, therefore losing the complete information on counter updates. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Internal log system Impact to End user: No impact.

2.25 WBTS overload report handling

Problem report: NA04748353 Exists in: RN4.0 Correction Target: RN5.0 MP2 Severity: B - Major Customer Impact: Capacity & Performance Attached PRs: - Probability: Occasional Description: Shortcomings of NBAP Overload algorithm: As the BTS nack reason for overload and HSDPA call setup failure are same therefore RNC IUB protocol SW doesn't differentiates in both the cases and hence treated both as overload scenario in which overload limit is set to minimum value even if HSDPA call setup failure takes place. Shortcomings of RRC Overload algorithm: Currently RRC calculates the RRC connection limit at cell level. So sometimes it happens that even if the BTS could allow more number of RRC connections but RRC rejects it on its own because its cell level overload limit is already exceeded. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance / RRC setup Success Impact to End user: No impact.

2.26 Paging Delay counters show incorrect values

Problem report: NA04824328 Exists in: RN4.0 Correction Target: RN5.0 Severity: A - Critical


Customer Impact: Operation & Maintenance, Counters Attached PRs: - Probability: Permanent Description: Paging Delay counters for Cell_PCH or URA_PCH show totally junk value. Solution / Workaround: FACH Call Setup involving direct transition from PCH to DCH disabled. Impact to Operator: KPIs, Paging Delay counters Impact to End user: No impact.

2.27 RNC restart in case other WDU has hardware problem even another WDU is fine

Problem report: NA04882815 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, System restarts Attached PRs: - Probability: Permanent Description: One WDU has hardware problem but this lead to software works abnormal even the other WDU is fine. Solution / Workaround: Plug out the faulty WDU. Impact to Operator: Operator cannot use NE while system restarts. Effects cell availablity Impact to End user: Call no possible

2.28 MCC going in loop for triggering PCH to DCH transition all the time

Problem report: NA04818210 Exists in: RN4.0 Correction Target: RN5.0 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If Cell_PCH to Cell_DCH transition fails due to failure from AC then RNC still


keeps on trying the state transition forever instead of moving UE to Cell_FACH and try Cell_DCH attempt in the next capacity request received in UL or DL. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: No impact.

2.29 UL temporary lowered bitrate cannot be increased to 384 if BitrateSetPSNRT is ON

Problem report: NA04791474 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: User Plane Quality, HSDPA UL data rate Attached PRs: 55505ESPE01 Probability: Permanent Description: UL TMBR (Temporary lowered) bitrate in cell cannot be increased to 384 in case it has been decreased from its initial value 384. This happens in case RNP parameter BitRateSetPSNRT is ON. This affects HSDPA UL return channel bitrate. Solution / Workaround: Set BitrateSetPSNRT OFF. Impact to Operator: 384 cannot be used as UL data rate in HSDPA calls. Impact to End user: 384 cannot be used as UL data rate in HSDPA calls.

2.30 Alarm 70173 (Backend Database Required by CORBA Naming Service is Unavailable)

Problem report: NA04800109 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: A - Critical Customer Impact: Operation & Maintenance Attached PRs: NA04800832, NA04792960, NA04810441, NA04818986 Probability: Permanent Description: In big environment it seems that 4GB of RAM memory is not enough. Probably some processes have memory leaks, and after few days, that causes "Out Of Memory" Linux message. After that OMS is not stable anymore. Solution / Workaround: No workaround.


Impact to Operator: This problem is affecting whole OMS functionality, after "out of memory" message in syslog, some major functionalities may be not be accessible for short period of time. Impact to End user: This problem is affecting whole OMS functionality, after "out of memory" message in syslog, some major functionalities may be not accessible for short period of time.

2.31 WBTS not showing alarms when it is off air

Problem report: NA04814089 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability, BTS availability Attached PRs: - Probability: Permanent Description: Cell service creations failed because leg control in RSMU had invalid state information for DMPG-0 and DMPG-1. Invalid state information happened during active MXU restart (when tributary units behind MXU are also restarted and also active unit RSMU faulty switchover happened). Invalid state information occurs when recovery message re_unit_restart_imminent_s is lost or when Unit handling program block sends message to hand in SP unit (and this SP just changed to WO, so message is lost). Solution / Workaround: Restart every DMPG units that have invalid state information in leg control. Invalid state information can be seen from LGUTIL service terminal command IU (state should be empty when unit is OK). Impact to Operator: Stability, BTS availability Impact to End user: No impact.

2.32 Illegal values from OLPC (outer loop power control) measurement

Problem report: NA04179653 Exists in: RN3.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Occasional Description: The EbNo values from outer loop power control measurement show illogical values. E.g. the UL_AVERAGE_EBNO counter is much less than 0 for voice connections,


and for some packet connection it is close to 0 when divided by UL_AVERAGE_EBNO_DENOM. The original fault is that OLFTOR reports RCPM data only when a call comes in to an empty DMPG. Solution / Workaround: No workaround. Impact to Operator: Illegal values from OLPC measurement. Impact to End user: No impact.

2.33 HSDPA retainability below 60%

Problem report: NA04875477 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call completion Success. Attached PRs: - Probability: Permanent Description: In the message which Layer 3 sends to Transport Resource Manager for HSDPA user information, wbts_id is sent. Corresponding to that Wbts id an entry is created in the data table and a new HSDPA hand is created. The root cause of the problem is this: Entry for the HSDPA hand corresponding to that WBTS id already exists in the data tables at Transport Resource Manager but the hand doesn't exist.The library then throws the error and Layer 2 doesn't send any acknowledgment to Layer 3 Solution / Workaround: No workaround Impact to Operator: Call drops Impact to End user: Call drops

2.34 Occasional NPGEP unit start up failures after RNC reset

Problem report: NA04914735 Exists in: RN4.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Unit restart Attached PRs: - Probability: Permanent Description:


Occasional NPGEP unit start up fails after RNC reset. Some cable records are deleted if the record file is once corrupted before that prevents the start-up and NPGEP stays WO-RE state. Solution / Workaround: No workaround Impact to Operator: Stability: Unit Restarts Impact to End user: No impact

2.35 HS-DSCH setup failure due to RNC for interactive

Problem report: NA04821108 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: There is a general problem related to PRFILE reading in BRM. This specific case is related to PRFILE parameter (007:0298 RN40_MAINT_028). After changing it from 0 to 1 (minimum bitrate allocation through PBS is enabled). M1002C413 (HS-DSCH SETUP FAILURE DUE TO RNC FOR INTERA) counters started increasing heavily. This was due to inconsistency in bitrate determination between branches in different BTSs (BRMs located in different ICSU) because of the PRFILE reading problem. The timer used for periodic PRFILE reading had been lost at some ICSU and thus new PRFILE values were not taken into use. The fault situation is rare, related to switchovers under special circumstances. Solution / Workaround: Timer message can be sent to BRMPRB master in problematic ICSU, the timer will trigger periodic PRFILE reading. Impact to Operator: Capacity & Performance: Call setup success Impact to End user: No impact.

2.36 Alarm 3217 is reported to both 2N units

Problem report: NA04899338 Exists in: RN4.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Stability, Unit Restarts Attached PRs: - Probability: Permanent


Description: Alarm 3217 SYNCHRONIZATION CABLE FAILURE is reported to both 2N redundant units when the FSYNC synchronization cable between the 2N pair units has a fault. MXU (MX622) and SFU (SF10E) have the FSYNC cable. System reports the unnecessary alarm 3217 to the WO unit, as alarm should be raised only to SP unit in case FSYNC cable problem. Solution / Workaround: No workaround Impact to Operator: Spare MXU dropped to test state Impact to End user: No impact

2.37 SF10E SD4G-A HW block bitstream downgrade

Problem report: NA04887607 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Stability Attached PRs: NA04890116, NA04895805 Probability: Permanent Description: On some cases, the SF10E SD4G-A bit stream included in RN5.0 boot flash image can cause instability to other units due to data corruption (bit errors) in the SFU. This can lead even to system outage. The RN5.0 SD4G-A bit stream (version 129) has smaller timing margins compared to RN4.0 SD4G-A bit stream (version 125), because more logical functions have been added into the FPGA. This new logic means improvements to fault diagnostics that are not critical for normal operation and performance. Solution / Workaround: No workaround Impact to Operator: Stability: Outage Impact to End user: No impact

2.38 Boot prom updating printout changed to be line with real updating situation

Problem report: NA04860501 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major


Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: When updating the boot proms, MML printout "COMMAND EXECUTED" even there has happened timeout in message waiting and boot update was aborted. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact

2.39 Automatic MXU unit restarts

Problem report: NA04649372 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: B - Major Customer Impact: Capacity & Performance, Unit restarts Attached PRs: - Probability: Permanent Description: MX1G6/NP2GE/NP8S1 plug-in unit is restarted by the supervision. Alarm history shows unit restart due to 3510/3508 alarm the last info fields being 00 04. The unnecessary restart of plugin-unit may cause loss of calls depending if the unit has 2N redundancy. Solution / Workaround: No workaround. Impact to Operator: Stability: Capacity/Performance Impact to End user: Calls may drop.

2.40 RNC remove active cell without consider CIO during Soft Handover

Problem report: NA04719588 Exists in: RN4.0 Correction Target: RN5.0 MP2 Severity: C - Minor Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent


Description: The problem may occur when a positive cell individual offset (CIO) is defined for an intra-frequency neighbour cell. When positive cell individual offset is used, an intra-frequency neighbour cell is included in the active set earlier than should have been the case without the positive offset. The offset is controlled by the ADJS parameter AdjsEcNoOffset. Current NSN RNC SHO algorithm does not take into account CIO when it makes additional checkings for the radio conditions in case of events e1b and e1c. Thus the SHO algorithm can make a wrong decision and remove a cell with a positive cell individual offset from the active set. The SHO algorithm should not remove the cell, which was added with positive CIO value, until the combined measurement result and CIO meets the drop window. But now the SHO algorithm removes the cell already when the plain measurement result meets the drop window. This is causing SHO branch ping-pong effect and it may also cause a call drop occasionally. Solution / Workaround: No workaround. Impact to Operator: The problem makes more difficult to use CIO as a tool to move the cell border (due to street corners, for instance). The problem can decrease RRC Success Ratio (RNC_217e) slightly if positive cell individual offsets are used in the network frequently. Impact to End user: Occasional call drop in street corner, for instance.

2.41 RRC does not update correct paging counters

Problem report: NA04754779 Exists in: RN4.0 Correction Target: RN5.0 PP2.1 Severity: B - Major Customer Impact: Operation & Maintenance, Wrong statistics information Attached PRs: NA04823858, NA04830175 Probability: Permanent Description: - RRC initiates paging procedure due to IU release command when UE has not yet acknowledged FACH-PCH transition. - RRC does not update relevant paging counters when PCH-DCH transition is interrupted or accomplished successfully. - When PCH-FACH transition is performed then RRC does not update correct success counters when cellUpdate is received as response to a paging and when UL DCCH message is received as a response to a cellUpdateConfirm message. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Wrong statistics information Impact to End user: No impact.


2.42 Missing daily 1013 AutoDef SHO measurement files

Problem report: NA04803521 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics & Counters Attached PRs: NA04850630 Probability: Permanent Description: Missing RNC Measurement data during overload situation due to insufficient measurement object buffer size. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Statistics Impact to End user: No impact.

2.43 BTS IP-address shown on RNC RNW Object Browser

Problem report: NA04525822 Exists in: RN4.0 Correction Target: RN5.0 MP1 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: The value of the BTSIPAddress is got by RNC when BTS O&M link is established from BTS to RNC. The value is the IP address from where the O&M connection is established. This is how it is specified and it is also agreed that value is not necessary the real BTS IP address as in case of FlexiBTS the connection is established by transmission module. This is anyway ok because also that IP address can be used for the planned purpose which is like the parameter description already says "The value of the parameters is used to establish TCP/IP connection for O&M purposes to the BTS by other NEs e.g. in case of launching BTS Site Manager remotely." Solution / Workaround: No workaround. Impact to Operator: Parameter is displayed by new name "BTS O&M IP address". Impact to End user: No impact.


2.44 Secondary PLMN ID consistency checking problem

Problem report: 9995ESPE07 Exists in: RN4.0 Correction Target: RN5.0 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent. Description: The management parameter configuration for IMSI based handover cannot be modified in the RNC RNW configuration. When the network maintenance engineer modifies the RNC RNW configuration by trying to create or modify an IU connection towards the CS or PS core network (IUCS or IUPS managed object being created) using the RNC EM application Object Browser. In addition, all the following conditions must be true: 1. At least one core network connection exists (IUCS or IUPS managed object). 2. One or more of the existing IUCS or IUPS objects have the same PLMN identifier as that of the IUCS/IUPS being created or modified. 3. The list of "SharedAreaPLMN" values defined for the IUCS/IUPS being created is different from those defined for the existing IUCS/IUPS objects. Solution / Workaround: IMSI based handover configuration changes must be done by using the RNC RNW plan management interface. If the RNC EM application Object Browser is the only option for making configuration changes, then all core network connections for the PLMN identifier given must be deleted and re-created from the RNC RNW configuration. Impact to Operator: Decrease in the ability to perform RNW CM configuration changes in the RNC.This also has a certain effect on KPIs if IU connections need to be re-created. Impact to End user: Service unavailability during network re-configuration.

2.45 Directed RRC Connection Setup currently re-directs UE to the UMTS900 layer

Problem report: NA04696367 Exists in: RN4.0 Correction Target: RN5.0 MP2 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: NA04744732 Probability: Permanent Description: RNC directs UE to frequency band which is not supported by UE. This concerns both RRC connection setups and FACH to DCH state transitions. The above behavior if allowed on the network will virtually double the number of RRC attempts which will lead to sharp increase in signaling load and CCCH congestion. All with inevitable consequences of degrading PS accessibility and retainability metric.


Solution / Workaround: Use DRRC only with same frequency layers. In this case DRRC cannot transfer UE to non-capable frequency. Impact to Operator: Capacity & Performance/Call setup success Impact to End user: Degraded PS accessibility.

2.46 Missing error description in GUI for some parameter modification cases

Problem report: 47588ESPE02 Exists in: RN4.0 Correction Target: RN5.0 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: 48097ESPE02, 48090ESPE02 Probability: Permanent Description: In some cases, when parameters modification is (expectantly) denied due to consistency check for those parameter values, only an error code is returned by the GUI and textual description is missing. Tree such cases are known and relate to the following issues: 1) Dependency between HSUPAXUsersEnabled (HSUPA x users enabled) and NumberEDCHReservedSHOBranchAdditions (Number of E-DCHs reserved for SHO branch additions). 2) Dependency between a) HSDPA or HSUPA or HSPA and AAL2 path type is stringent&stringent-bilevel&tolerant, or b) AAL2 path usage is HSPA and AAL2 path type is stringent-bilevel&tolerant. 3) Dependency on VP service category changed when VC is not used by own COCO under this VP. Solution / Workaround: The actual reason why the consistency check has failed need to be searched for from the context. Impact to Operator: No explicit help available in GUI in some cases. Impact to End user: No impact.

2.47 RAB modification, MTC call failed on some R99 handset

Problem report: NA04697631 Exists in: RN4.0 Correction Target: RN5.0 MP1 Severity: B - Major Customer Impact: Capacity & Performance, Call setup, effects to AMR Attached PRs: - Probability: Permanent


Description: Other vendor MSS used Iu UP mode versions 1 and 2 with Multi-AMR modes in AMR call setup, but RNC AMR mode set algorithm removed version 2 from request because Multi-AMR mode request. After that MSS sent second RAB assignment request to start using TFO/TrFO, which was rejected by RNC. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call setup effects to AMR Impact to End user: Call setup failures.

2.48 Cable configured with “no direction” remains after SW upgrade

Problem report: NA04647255 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Cables configured with "no direction" cannot be deleted using the ZWFT commands. Cable connection is inherited in release SW upgrade from RN2.2 or older to RN3.0 or newer. So some cables remained configured with "no direction". These "no direction" cables cannot be deleted after upgrade in RN4.0 or RN5.0. This situation occurs very rarely. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact.

2.49 Occasional call drop after relocation from ADA to RNC due to failure in CFN calculation

Problem report: NA04880876 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: - Probability: Permanent Description:


After relocation from ADA to RNC due to incoming CS call, when Compressed Mode is started in anchoring, then Call Control did not calculate the CFN correctly during the Compressed Mode procedure which caused later overlapping CFN to be sent to BTS when new configuration was given to BTS. Solution / Workaround: No workaround Impact to Operator: Call Completion Success Impact to End user: No impact

2.50 CS call setup failure after incoming I-BTS sharing relocation

Problem report: NA04887483 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If there is standalone signalling DCH during UE involved relocation from ADA to RNC and slow signalling DCH in use, then standalone signalling DCH can be changed to fast signalling DCH bitrate during the handover procedure and later downgraded after the relocation and CS setup successfully. This will improve the transmission of SRB messages to be sent to UE faster in smaller TTI so that RBSetup is not delayed for long time in the RLC buffer when CS setup is tried. Solution / Workaround: No workaround Impact to Operator: Call Setup Success Impact to End user: No impact

2.51 Several Node-B sectors going to BL(I)

Problem report: NA04900861 Exists in: RN4.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Cell availability Attached PRs: NA04900324 Probability: Permanent Description:


During cell locking under high load MAC-c makes an exception and crashes. MCFTOR crashes into exception caused by a NULL pointer when capa_req_buffer is used to store capacity requests (load cutter is active). Solution / Workaround: No workaround Impact to Operator: Cell availability Impact to End user: Call drops

2.52 Bootprom upgrade during RNW startup caused OMU restart

Problem report: NA04860408 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, Outage NA04858802 Attached PRs: - Probability: Permanent Description: The problem was that high-priority process (RDISFS / A0) was using all available CPU time in WO-OMU so that RNW DB manager (RAVIOLI) did not got CPU time to serve the remote DB read requests. The number of accumulated requests became so high that system ran out of buffers in OMU and reseted the computer. That fault happens only if the boot upgrage is tried to be done too early after system restart when RNW is still under configuration. Solution / Workaround: No workaround Impact to Operator: Stability: Outage Impact to End user: No impact

2.53 The counters M1008C66, M1008C18, M1010C2 and M1010C40 are not updated if starting the compressed mode has failed in the UE

Problem report: 46746ESPE02 Exists in: RN4.0 Correction Target: RN5.0 Severity: C - Minor Customer Impact: Capacity & Performance, Compressed mode Attached PRs: - Probability: Occasional.


Description: This is an RNC-internal fault. Starting the compressed mode for Inter-frequency or Inter-system measurements fails due to the UE and no other failure counter is updated. Solution / Workaround: No workaround. Impact to Operator: Counters M1008C66 INTER FREQ COMPR MODE START NOT POSSIBLE FOR NRT, M1008C18 INTER FREQ COMPR MODE START NOT POSSIBLE FOR RT, M1010C2 INTER SYSTEM COMPR MODE START NOT POSSIBLE FOR RT and M1010C40 INTER SYSTEM COMPR MODE START NOT POSSIBLE FOR NRT are not updated if the compressed mode starting has failed in the UE. Impact to End user: No impact.


3. GENERIC FAULTS OPEN IN RN5.0

3.1 Unable to see alarm history in Fault Management

Problem report: NA04935504 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: It is not possible to see alarm history in OMS Fault Management application and the error message "History query in progress” stays in the screen. Solution / Workaround: No workaround Impact to Operator: Not able to see alarm history Impact to End user: No impact.

3.2 RNC cannot handle PS RAB Setup procedure if SCRI from UE is received for the PS CN same time

Problem report: NA04921932 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: If UE sends SCRI for PS core network during ongoing AMR case same time when PS core network had sent RAB Assignment Request to establish PS RAB, RNC can not handle the collision between SCRI from UE and RAB procedure from core network properly. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Alarms Impact to End user: No impact


3.3 Cell Update is not handled correctly

Problem report: NA04935401 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: If UE initiates Cell Update due to cell reselection after failed FACH to DCH transition, RNC does not handle the Cell Update correctly and performs a local transition to Cell_PCH and leaves UE in Cell_FACH. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Data throughput Impact to End user: No impact

3.4 After changing the CN-ID for the IU-PS interfaces calls fail,

Problem report: NA04969405 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: When CN Id is changed, old hand is stopped. Master create new hand, but it set wrong subsystem number and new hand stopped immediately. Solution / Workaround: Do not change PLMN Id or CN Id of CN. If them is needed to change, remove CN and create new. Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.5 RNC sends incorrect SAI to the CN in the Initial Direct Transfer after failed Inter RNC SCC procedure,


Problem report: NA04990745 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: RNC sends incorrect SAI (service area identifier) to the CN in the Initial Direct Transfer after failed Inter RNC SCC (Serving Cell Change) procedure. This happens because wrong SAI information is stored during inter RNC SCC procedure. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, RRC Success Impact to End user: No impact

3.6 Fault Management issue after RU20 upgrade

Problem report: NA04936554 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: NA04953307 Probability: Permanent Description: The problem only occurs for dynamic alarms which range is from[4000-5999] or [61000-62999], when the application retrieves alarms by using alarm agent API, for alarms in which applicationAdditionalInfo was encoded contains "rncAT=" element, alarm text will be retrieved OK, but if alarm text in applicationAdditionalInfo is encoded with "atext=", the alarm text in mentioned range will not be retrieved OK. Solution / Workaround: No workaround Impact to Operator: Dynamic alarms range from [4000-5999] or [61000-62999], alarm text might be missing in Fault Management after retrieving from alarm database. Impact to End user: No impact

3.7 RRC does not forward SecurityModeCommand to the UE



Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: RRC Call control in RNC did not handle RLC suspend and RLC resume command correctly if Security Procedure was started immediately after a procedure which had caused RLC to be suspended. Since Security procedure also requires SRB 1, 3 and 4 to be suspended, RNC could not remember the RLCs which were suspended due to earlier procedure and without waiting for those RLC to be resumed, it sent another suspend command causing problem in maintaining internally about the RLC status and then it rejected the Security procedure due to conflict in the internal RLC state maintained in the data structures. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, RRC Success Impact to End user: No impact

3.8 Count of successes is more than attempts in Direct Resource Allocation Counters

Problem report: NA04937105 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: UER and BRM program blocks internal message interface has a fault. Parameters which effect Direct Resource Allocation feature counters (from M1002C672 to M1002C675) are filled up incorrect. Solution / Workaround: - Impact to Operator: KPI counters are filled incorrectly. The success rate can be more than 100%. M1002C672 ATT_HSPA_DIREAL_BGR M1002C673 ATT_HSPA_DIREAL_INT M1002C674 ALLO_SUCC_HSPA_DIREAL_BGR M1002C675 ALLO_SUCC_HSPA_DIREAL_INT Impact to End user: No impact


3.9 RRC was sending trace record to non existent PID after deactivation of trace

Problem report: NA04933708 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Internal Log writing Attached PRs: - Probability: Permanent Description: RRC was sending trace record to non existent PID after deactivation of trace. After deactivation of trace, trace timer was not reseted which resulted in trace record being sent to non existent PID. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, internal log writing Impact to End user: No impact

3.10 Alarm 1024 HAND PROCESS ERROR IN PROGRAM BLOCK in ICSU

Problem report: NA04931359 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: When RNC receives too much maintenance messages (RESET, BLOCK, UNBLOCK) from WBTS, it triggers the alarm 1024 (HAND PROCESS ERROR IN PROGRAM BLOCK). The alarm means that MPH hand creation has failed. Solution / Workaround: Reset the faulty ICSU or make the switchover the ICSU. Impact to Operator: Operation & Maintenance, Alarms Impact to End user: No impact

3.11 Problem in fetching data from RNW measurement presentation from RNC


Problem report: NA04936486 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Stability Attached PRs: NA04921467 Probability: Permanent Description: Description: The pointer validation for NULL is missing, which might cause the crash. Due to a crash a RNW Measurement Presentation Error occurs when reading measurement data and it is not possible to get RNW Measurement Presentation. Solution / Workaround: No workaround Impact to Operator: Stability Impact to End user: No impact

3.12 Security mode command not handle properly (Radio Link failure)

Problem report: NA04922068 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: If radio connection with UE is lost in Cell_DCH state and there is received and saved Security Mode Command from CS CN, RNC does not reject the Security procedure but keeps it saved when waiting for Cell Update from UE to perform RRC Connection Re-establishment procedure. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, RRC Success Impact to End user: No impact

3.13 Incorrect packet call ticket



Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Counters Attached PRs: - Probability: Permanent Description: RRC Call control wrongly pegs packet session setup failure counter after successful completion of state transition to Cell_DCH from Cell_FACH procedure. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact

3.14 Process exception during MultiRAB handover

Problem report: NA04954665 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: - Probability: Permanent Description: During State transition to Cell_DCH state UE specific Resource Manager Entity uses an uninitialized variable as loop index causing process exception. Process exception happens during NSN RNC to other vendors RNC MultiRAB handover. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance: Call Completion Success Impact to End user: Call drops.

3.15 RRC process exception happens after failed relocation if new relocation is triggered by handover control during Iu release command waiting

Problem report: NA04975347 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor


Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: If relocation procedure in SRNC fails for PS CN with failure cause indicating relocation is not allowed, then SRNC sends Directed Signalling Connection Re-establishment command to the UE and waits for Iu Release Command from CN. During Iu release command waiting, if new relocation is triggered internally by the handover control in RNC, it causes process exception. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Alarms Impact to End user: No impact

3.16 E-DCH active set update failure

Problem report: NA04937881 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance Attached PRs: - Probability: Permanent Description: If during E-DCH AS update several branches are tried to be added into E-DCH AS and some E-DCH IP branch addition fails during RL reconfiguration and some other branch addition succeeds. The failed E-DCH Iub IP transport branch is not released correctly and this causes problems later when the same E-DCH branch is tried to be added into E-DCH AS again. Operator can see the failure situation in ICSU log: CALLER : 04B7 0B03 9B RETURN ADDRESS: 000C (L0001).000841D7 WRITE TIME: 2011-05-24 18:09:33.87 PARAMETERS: E-01 0000.000000FF 00000001 000C.0004434B USER TEXT : NRMSU0: Invalid form in nrm_dest_addr_t USER DATA : 20 Solution / Workaround: No workaround Impact to Operator: E-DCH active set update failure Impact to End user: No impact


3.17 M1002C423 still updated after SignallingConnectionReleaseIndication received.

Problem report: NA04944740 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Counters Attached PRs: - Probability: Permanent Description: If UE sends Signalling Connection Release Indication (SCRI) during ongoing Intra RNC IFHO procedure and then does not answer to the handover command or it rejects the DCH reconfiguration procedure after sending SCRI to the NW, then it is updated as failure in the counters for the failed procedure during which UE sent SCRI. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact

3.18 RNC does not know what DL PDU size is in use

Problem report: NA04909632 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: After failed state transition from Cell_FACH to Cell_DCH causing RLC PDU size change in downlink, RNC does not know what DL PDU size is in use. RNC assumes that UE has PDU size 336 for DL instead of checking if UE RLC had acknowledged UE receiving the DL RRC message. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Data Throughput Impact to End user: No impact


3.19 Security mode cancellation is not done properly

Problem report: NA04963233 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: If UE makes Cell update from DRNC cell during ongoing Security procedure then RNC cancels the Security procedure and triggers relocation procedure but it does not ciphering configuration internally to earlier configuration while SMC has been cancelled from UE and RNC L2. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, RRC Success Impact to End user: No impact

3.20 Call drop after MCC sent mcc_active_set_update_nack_s incorrectly

Problem report: NA04969394 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: - Probability: Permanent Description: Call control does not update the DCH utilization indication correctly, if the indication arrives during ongoing RRC procedure and this causes state transition to Cell_FACH triggered wrongly and ASU procedure is rejected due to the state transition. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Completion Success Impact to End user: Effects to quality of calls.

3.21 No acknowledgement was received from the service provider within timeout limit (Error 13846)



Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics Attached PRs: - Probability: Permanent Description: When Node B restart is ongoing, NBAP common hand (NBAP-C) and NBAP dedicated hand (NBAP-D) receives link down notification. NBAP-C does not send the reset response to RNC O&M program block hence error logs (Error 13846 Timeout limit in Object Browser) appears. This is due to reason that NBAP-C does not set its internal flag to handle NBAP-D link down situation correctly. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Statistics Impact to End user: No impact

3.22 The counter M661C4 doesn't reset after a measurement period

Problem report: NA04767787 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics / Counters Attached PRs: - Probability: Permanent Description: Counter M661C4 (M3UA_UNAVAILABLE) doesn't reset after a measurement period but it increases over days. It should be cumulative, but it is non-cumulative in the configuration file. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Statistics / Counters Impact to End user: No impact

3.23 After SRNS relocation UE is not involved with HSPA from another vendor SRNC



Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: - Probability: Permanent Description: After SRNS relocation UE is not involved with HSPA from another vendor SRNC, NSN Target RNC wrongly assumed SRB on HSDPA in DL even when SRB was on DCH. This caused call to drop after relocation in NSN RNC due to wrong activation time calculation. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Completion Success Impact to End user: Call drop.

3.24 AMR call released suddenly

Problem report: NA04933407 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: During AMR downgrade, Core Network initiates IU CS release which causes later AMR reconfiguration to fail. This problem happens because AMR's IU is released by Core network which causes RRC to release AMR later. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call completion success Impact to End user: AMR call is dropping suddenly.

3.25 Packet Call Setup Failure after relocation



Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: During Cell FACH relocation, if UE sends unexpected RRC messages in response to the handover command from Network, then Target RNC wrongly things the Radio Bearer Reconfiguration Complete to be the response of message sent by itself and then could not handle the failure situation correctly. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: No impact

3.26 Packet Call Setup Failure due to MS

Problem report: NA04975432 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If RNC RLC makes reset error for the user plane RB in Cell_DCH then RRC call control triggers state transition to Cell_FACH to perform RLC re-establishment but it forgets the RLC re-establishment need for the user plane RB if it receives CS call setup request from the CN. This causes later incorrect signalling when UE is moved to Cell_FACH and next attempt to setup PS NRT user plane fails. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: No impact

3.27 Alarm7652/7750 alarm type mismatch between NE/OSS

Problem report: NA04769728 Exists in: RN4.0 Correction Target: RN6.0 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: -


Probability: Occasional Description: If a minor fault (or faults) has occurred in the base station. BTS sends notification in alarm 7652 to RNC. As per alarm manual, alarm 7652 is by default of type Quality of service. But when checked in alarm history, its type is shown as Equipment which is not as per the default value defined for the alarm 7652. Solution / Workaround: No workaround. Impact to Operator: Operation and maintenance Impact to End user: No impact.

3.28 OBH process causes 100% CPU load during OMU start-up

Problem report: NA04944144 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, alarm Attached PRs: - Probability: Permanent Description: At start-up, OBH process reads alarm from BAIDAT database. However, if BAIDAT database has some inconsistency due to duplicate alarm instances leading to too many alarms then OBH process keeps on reading alarms from database and hence consumes lot of CPU time. Solution / Workaround: No workaround Impact to Operator: RNC unit does not start-up so RNC remains unavailable Impact to End user: Radio network unavailable to the user

3.29 During Cell Reselection counter PS_SETUP_FAIL_OTHER_BGR (M1022C20) increase

Problem report: NA04947370 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent


Description: If UE makes cell reselection during ongoing state transition to Cell_DCH before the state transition command has been sent to the UE, then although RNC cancels the state transition procedure and handles Cell Update, it pegs failure counters incorrectly. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: No impact

3.30 ICSU switchover might fail

Problem report: NA04899701 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Stability, switch over failure can cause call drops and KPI impacts Attached PRs: - Probability: Permanent Description: The periodic HSCAHO timer (HSCapabilityHOPeriod) is expiring many times during a second which causes ICSU switchover to fail. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, ICSU switchover failure can cause call drops and KPI impacts Impact to End user: Possible call drops

3.31 RRC does not allow Cell DCH transition

Problem report: NA04933988 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: RNC does not allow state transition to Cell_DCH to the UE when capacity request was received from RNC MAC. RNC should initiate state transition to Cell_DCH and should not allow HSDPA to be allocated if the HSDSCH prevention guard timer is running.


Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Data throughput Impact to End user: No impact

3.32 SRNS failure when CS call started on I-ADA and moved to neighbouring RNC

Problem report: NA04933978 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Handover Success Attached PRs: - Probability: Permanent Description: After incoming SRNS relocation from ADA to RNC due to CS setup RNC does not allow next relocation procedure if AMR call still continues. This is because RNC wrongly started treating the AMR call as USSD (unstructured supplementary service data). Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Handover Success Impact to End user: No impact

3.33 M1001C145 (RAB ACT FAIL CS VOICE IU) increased

Problem report: NA04928572 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: After radio connection is lost with UE, RNC initiates Iu Release procedure. RNC updates drop due to Iu counters, not to due to radio reason counters, in case core network sends cause Iu Release Command with Release due to UTRAN generated reason. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Statistics / counters


Impact to End user: No impact

3.34 UE doesn't respond to Radio Bearer Release procedure

Problem report: NA04928826 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: If UE looses radio connection during Iu release procedure in Cell_FACH and PS CN sends Iu Release Command at the same time, RNC can not handle the release procedure correctly and remains hanging. Solution / Workaround: No workaround Impact to Operator:Operation & Maintenance, Alarms Impact to End user: No impact

3.35 3344 UX LINK CONNECTION FAILURE alarm is not always cancelled automatically

Problem report: NA04953351 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Occasional Description: 3344 Alarm mechanism was not fully supported to all of the units and the alarms were not cancelled automatically. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Alarms Impact to End user: No impact


3.36 OMU switchover when unsupported usb stick inserted

Problem report: NA04981425 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Operation & Maintenance, File system Attached PRs: - Probability: Permanent Description: The max buffer for usb stick is 64K. If sector size of usb stick is greater than 64K, the buffer will overflow. Unit will restart. Solution / Workaround: Change a supported usb stick Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.37 PS-RAB setup failed due to Radio link failure

Problem report: NA04950769 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Statistics & counters Attached PRs: - Probability: Permanent Description: During PS Rab setup (Direct Resource Allocation) Radio link with the BTS fails and due to that RAB setup fails but packet call ticket was not going for that RAB setup failure. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Statistics & Counters Impact to End user: No impact

3.38 Counters M1010C11 IS_HHO_WO_CMOD_RSCP_RT and M1010C12 IS_HHO_WO_CMOD_CPICH_ECNO_RT updated incorrectly



Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Handover Success Attached PRs: - Probability: Permanent Description: When ISHO measurements are released due ISHO cancellation event but MBSIC is still running, handover tries to do the ISHO based on previously received BSIC report. As a result it update counter incorrectly for no CM case like M1010C11 IS_HHO_WO_CMOD_RSCP_RT, M1010C12 IS_HHO_WO_CMOD_CPICH_ECNO_RT. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Statistics / Counters Impact to End user: No impact

3.39 RNC use wrongly Start Value received from UE in the RRC Cell update to reconfigure DL ciphering

Problem report: NA04980806 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: RNC use wrongly Start Value received from UE in the RRC Cell update to reconfigure DL ciphering, if UE has made Cell update due to Cell reselection during Cell_DCH to Cell_FACH transition for HSPA call. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Data Throughput Impact to End user: Effects to quality of calls.

3.40 Increased counter values for M1002C413: SETUP_FAIL_RNC_HS_DSCH_INT



Customer Impact: Operation & Maintenance, Counters Attached PRs: - Probability: Permanent Description: If channel switch from DCH to HSPA is cancelled due to inactivity, it is incorrectly pegged as accessibility failure. Since the UE was already being moved to Cell_FACH due to inactivity, HSPA allocation was rejected by call control in RNC for such user but it sends incorrect cause for rejection of HSPA allocation which leads to access failure counter to be pegged. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact

3.41 1024 HAND PROCESS ERROR IN PROGRAM BLOCK alarms causing blocked WCELLs

Problem report: NA04982452 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: Triggered by AAL2 signaling area, all path level reset is caused when NNI link is recovered. Remote side NE doesn't response the reset request. Signaling module in the system sends reset request again and it doesn't get the response, every time trying to allocate the new resource. Hand resources (RS2PRB module) are exhausted and alarm 1024 will be reported. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance , call setup success Impact to End user: No impact

3.42 Changing LAC in RNW plan doesn't work

Problem report: NA04956484 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical


Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Timers for RNW plan download were different at OMS and RNC. Changing LAC for BTSs fails. Plan run from CM Operation manager shows no errors but LAC is not updated at NE. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.43 Cell resource status is marked as frozen due to pre-emption in the cell specific AC entity

Problem report: NA04975371 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, RRC/Call setup/handover success Attached PRs: NA04950391, NA04985198 Probability: Permanent Description: Cell resource status is marked as frozen due to pre-emption for the duration of the ongoing pre-emption procedure, but in some situation the cell resource status incorrectly remains frozen after the pre-emption and this results in the cell being not usable (AC rejects all call attempts). Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: RRC / Call Setup / Handover Success Impact to End user: No impact

3.44 When ICSU and NPGEP FLTY SWO happens by subrack power off, the automatic IPoA will not run anymore leading cells down



Customer Impact: Stability, Switchover Attached PRs: - Probability: Permanent Description: IPoA should be deleted and recreated after ICSU SWO. Before the first ICSU SWO, data in MNEPRB (IPoA management Program) is already inconsistent with HW data. After SWO, IPoA was not deleted from NPGEP properly, so it is also recreated wrongly because resource on NPGEP still exist there. This recreation causes one IPOA not to work, so two BTS sites are down. IPoA should not do anything during NPGEP SWO, at that time, state of 32 IPoAs are not run, so when NPGEP SWO, these IPoA were recreated, they are all recreated wrongly because resource on NPGEP still exist there. So alarm 2831 INTERNAL VC BUNDLE DOWN was raised for each IPoA. Many BTS sites down after this execution. Solution / Workaround: No workaround Impact to Operator: Stability: Switchover Impact to End user: No impact

3.45 Layer change denied incorrectly in FACH to DCH transition

Problem report: NA05000504 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: If PCH to DCH triggered DRRC and then it was cancelled in RNC internally when UE makes Cell Update, Call control wrongly marks that DRRC attempt also failed and does not allow DRRC in the next attempt. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, RRC Success Impact to End user: No impact

3.46 Counter M1001C397 (RAB_ACT_FAIL_PS_INTER_UE) increased on inter RNC HO border cells



Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: - Probability: Permanent Description: After SRNC relocation in Cell_FACH, RNC did not configure ciphering for signalling DCH correctly causing mismatch between UE and NW and SRBs stopped working. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Completion Success Impact to End user: No impact

3.47 Iu object deletion needs locking all of WCELLs due to CBS configuration

Problem report: NA04993919 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: All of the WCELLs need to be locked and SCCPCH value need to be modified other to value than 3 if both flexible Iu and CBS (cell broadcast system) are activated. It should be possible to delete the Iu object without locking WCELLs. There should be no need of direct checking between IUCS/IUPS and CBCPLMNlist. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact

3.48 DRRC is triggered incorrectly when blind IFHO is enabled



Customer Impact: Capacity & Performance, Operation & Maintenance, Handover Success, Statistics / Counters (DRRC attempt counters) Attached PRs: - Probability: Permanent Description: In case Blind IFHO is enabled in the Cell, DRRC connection should not be triggered. When Blind IFHO is enabled in the Cell, DRRC connection can be setup only in case for R99 capable UEs or for establishment cause 'conversational call'. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance : Handover Success Operation & Maintenance: Statistics / Counters (DRRC attempt counters) Impact to End user: No impact

3.49 Many RRC and RAB KPIs are suddenly degraded

Problem report: NA04960069 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04974837, 52004ESPE01, NA04988708, NA04985199 Probability: Permanent (but only in overload case) Description: KPI HSDPA accessibility degraded a lot. RNC restart recovered the problem but one or two day later it was back again. Affected KPIs are: M1001C21 RRC ACTIVE FAIL DUE TO RNC INTER REASONS M1001C15 RRC ACTIVE FAIL DUE TO IU INT M1001C185 RAB ACTIVE FAILURES DUE TO IU FOR PS DATA INTERA M1001C191 RAB ACTIVE FAILURES DUE TO IU FOR PS DATA BACKG M1001C196 RAB ACTIVE FAILURES DUE TO RNC FOR PS DATA BACKG M1001C190 RAB ACTIVE FAILURES DUE TO RNC FOR PS DATA INTERA M1002C421 HS-DSCH SETUP FAILURE DUE TO RNC INTERNAL FOR BACKGROUND M1002C413 HS-DSCH SETUP FAILURE DUE TO RNC INTERNAL FOR INTERACTIVE M1003C28 RAB REL REQ BY RNC M1003C33 RAB REL REQ DUE TO MISC CAUSE. Reason for this problem is that source CDSP-H does not respond NRM's request messages from ICSU. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: Call drop. Degraded HSDPA accessibility.


3.50 RNC assigned two PSC with the same "intraFreqCellID" in the DL-MC message

Problem report: NA04984405 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Handover Success, Call Completion Success Attached PRs: - Probability: Permanent Description: Measurement Control sent to UE contains same intraFreqCellID for two PSC (Primary scrambling code). This is not a correct behaviour. Solution / Workaround: No workaround Impact to Operator: KPI , Capacity & Performance Impact to End user: Call drop

3.51 UERPRB does not send valid BLER target information to RRC

Problem report: NA04935156 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Handover Success Attached PRs: - Probability: Permanent Description: In I-BTS Sharing environment when hard handover for PS+CS multi-RAB is performed, UE Radio Resource management entity incorrectly packs the BLER information. It (UERPRB) has received BLER information from Base station resource manager. Due to this the handover procedure fails. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Handover Success Impact to End user: Call drops suddenly.


3.52 problems in AAL2 path (N-CID) release operation affecting to CS and PS access rate

Problem report: NA04938321 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04956454 Probability: Permanent Description: Fault in unit handling program block,AAL2 path (N-CID) release operation due to MXU and A2SU unit restart messes up A2SP unit internal interface information. Fault causes timeout in release operations of the units behind MXU and this causes problems when recreating GTP subnetd/N-CIDs after A2SP/GTPU/DMPG units rises back to WO-EX after MXU restart. Solution / Workaround: No workaround Impact to Operator: KPI , Capacity & Performance Impact to End user: Call fails

3.53 SAS (SIP based Multimedia Application Server) Failover delay

Problem report: NA04983652 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If over-ride mode is in use and the active association is set down with MML command OYS, ASPAC (ASP management message) was not sent for another association in asp-inactive state. I.e. like when comm lost is received. As a consequence of this it took about 40s before the other asp-inactive association was activated. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: No impact


3.54 The threshold alarm 71007 in OMS not forwarded to OSS after MP4

Problem report: NA04954932 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04976669, NA04990560, NA04936204 Probability: Permanent Description: Alarms 71007 was not reported anymore on NetAct because there was wrong object mo_id. NetAct discarded the alarm because it couldn’t recognize origin of the alarm. Solution / Workaround: No Workaround. Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.55 Traffic measurement report e4a event being ignored during HSDPA/16kb UL call

Problem report: NA04940531 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: RNC does not initiate DCH upgrade procedure when it receives traffic volume measurement report which indicates high RLC payload. Because of that the RLC Payload which is indicated by the UE is not checked correctly. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Data throughput Impact to End user: Data throughput is lower than it should

3.56 CS RAB establishment failures



Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Rate Attached PRs: - Probability: Permanent Description: RRC is starting CS RAB establishment before RRC Connection re-establishment with standalone SRB (signalling radio bearer) is completed. This causes CS RAB establishment to fail. Solution / Workaround: No workaround Impact to Operator: CS RAB setup KPI drop Impact to End user: CS RAB establishment failure

3.57 ICSU overload situation

Problem report: NA04895987 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: NA04984941 Probability: Permanent Description: 3GPP definition of the ToTargetRNC-Container IE is a huge structure as it includes definition from release 99, release 4, release 5, release 6, up to release 9 so far. Initialization of that structure during encoding of the Container by SRNC or decoding of the container by the Target RNC causes CPU overload due to huge memory initialization operations. It is also very critical to have the structure initialized properly. It has several IEs and sub IEs and it needs to carry all the information about the ongoing call from SRNC to the Target RNC properly to establish the configuration same way in the Target RNC. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Alarms Impact to End user: No impact.

3.58 RRC creates RLC unrecoverable error



Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: If RLC re-establishment is done for SRBs but UE moves to new cell before receiving the CellUpdateConfirm, then RNC does not ask UE to re-establish the SRB RLCs again. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: RRC Success Impact to End user: No impact

3.59 Packet Call Setup Failures due to Other increased

Problem report: NA04978850 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Occasional Description: After Cell_fach to hspa transition failure, TRM(Transport Resource Manager) cleared it's internal content properly. During the handling of Cell_fach to hspa transition failure Transport Resource Manager did not revert the value of an internal parameter to the old one that should have been used. This caused later on to a failure when transition from Cell_fach to dch(x/y) was tried several times. This could cause later on problems in packet call setup and singe UE may generate hundreds of failures resulting increase of Packet Call Setup Failures due to Other. Solution / Workaround: No workaround Impact to Operator: KPI / PS call setup success Impact to End user: PS Call is dropped

3.60 Call setup failures due to hanging DRNC resources



Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If SRNC did not release DRNC radio links (or IUR connection), the internal supervision in DRNC did not always release hanging DRNC resources. As a result, new calls were not possible after there were enough such hanging DRNC resources. This problem can also lead to call drop in case handovers fails to a cell suffering this problem. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: Problem to setup calls.

3.61 WBTS state change of WBTS between WO and BL(S) observed

Problem report: NA04955954 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Cell Availability Attached PRs: - Probability: Permanent Description: Pool 3 memory allocation fails in RNC_CELL causing error during TRCH creation. When Pool3 allocation fails, memory should be allocated from Pool 4. These checks were missing at some places. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance: Cell Availability Impact to End user: Effects to service availability.

3.62 RNW plan can not be activated

Problem report: NA04945460 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: -


Probability: Permanent Description: During the download operation phase, RAYMAN prevents RNW database disk updating (dumping) and after download operation end RAYMAN resumes database disk update prevention. So if during this time if activation request comes and dumping in progress activation will abort with DB is not in normal state. Solution / Workaround: 1. DOWNLOAD succesful PLAN from NETACT 2. START PLAN ACTIVATION within 1 minute of download end Impact to Operator: RNW PLAN can not be activated Impact to End user: No impact

3.63 Occasional call setup failure due to incorrect Security Mode Command handling

Problem report: NA04922063 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call setup succes Attached PRs: - Probability: Occasional Description: If RNC receives radio link failure indication from BTS during ongoing Security procedure when upper layer (RRC) was waiting for RLCs to be stopped and then it received a radio link sync restore indication, then RNC forgot the ongoing security procedure after sync was restored and did not send the Command to the UE at all causing the Security procedure to fail. Solution / Workaround: No workaround. Impact to Operator: NA Impact to End user: Call setup failure

3.64 Occasional NPGEP unit start up failures after RNC reset

Problem report: NA04914735 Exists in: RN4.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Unit restart Attached PRs: -


Probability: Permanent Description: Occasional NPGEP unit start up fails after RNC reset. Some cable records are deleted if the record file is once corrupted before that prevents the start-up and NPGEP stays WO-RE state. Solution / Workaround: No workaround Impact to Operator: Stability: Unit Restarts Impact to End user: No impact

3.65 High OMU CPU loadings

Problem report: NA04958919 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Stability, Overload level Attached PRs: 89846ESPE02 Probability: Occasional Description: Radio Resource Management entity in RNC sent the Alarm Cancel request for 0x7772 (HSDPA configuration in BTS) and for 0x7782, HSUPA configuration in BTS irrespective of it being set. As a result there was unnecessary ALARM CANCEL initiated by BRM after each Physical Channel Reconfiguration Ack message leading to log writing and increasing OMU CPU load. Solution / Workaround: No workaround. Impact to Operator: Stability: Overload Level Impact to End user: No impact

3.66 Duplicate entries in NE Measurement Explorer Object List field

Problem report: NA04983038 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent


Description: When different logical interfaces configured with same IP-based route id, PI5 was sending duplicated ids to AMN. AMN after finding duplicate objects, treat this as error and stops requesting the measurement data further. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact

3.67 Extra unit restarts during system restart

Problem report: NA04935299 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Stability, Unit restarts Attached PRs: 88042ESPE02 Probability: Permanent Description: Some units (e.g.: ICSU, DMCU) have extra restart due to ATM port configuration problem during system restart. Sync lost on UX FPGA chip during ATM port configuration will cause the unit restart. Solution / Workaround: No workaround. Impact to Operator: Stability, unit restarts Impact to End user: No extra impact to end user caused by this problem.

3.68 Spare ICSU start up failure after RNC restart

Problem report: NA04924129 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Stability, unit restarts Attached PRs: - Probability: Permanent Description: Spare ICSU start up failure leads to SP-EX ICSU reset loop after RNC restart. This is caused by USB functionality in the ICSU which affect the start up progress. Solution / Workaround: No workaround


Impact to Operator: Stability: Unit restarts Impact to End user: No impact

3.69 Sudden loss of OMU connection

Problem report: NA04913300 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04934706 Probability: Permanent Description: OMU connection is lost suddenly because the CPU load is too high. There is a R/W mutex to protect the IP data. There is one dead loop in the mutex mechanism, which leads to the high CPU load. Solution / Workaround: No workaround Impact to Operator: Configuration of IP resource fails Impact to End user: No impact

3.70 Reset and Recovery unit is doing Non performing cell recovery even after WBTS are moved to Working state

Problem report: NA04955890 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: Reset and Recovery unit is doing non performing cell recovery, even after WBTS are moved to working state. When WBTS are moved to working state, Reset Unit should indicate about the same to Recovery unit. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance



3.71 7762 RNW database operation failure

Problem report: NA04950919 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: DBMS uses the time values given by MTIM as the time limit for the transaction hand that is reserved to execute the transaction. Originally this time value for transaction hands has been 1 second, but because of the message latencies in IPA platform, the recovery actions of DBCODE with retry timers was increased so that more time is taken and the default MTIM timer values was changed from 1 sec to 1.5 sec around the time when TDL compiler version TDLM was released. But it is still MTIM(100)in DB RAUELQX.H file, which overwrites the default parameter values normally generated by TDL compiler. Hence the error code db_committed_ec is given in some situations. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Alarms Impact to End user: No impact.

3.72 RNW plan download fails: NO FREE HANDS AVAILABLE

Problem report: NA04943039 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04931751 Probability: Permanent Description: During modification of cell level Common Transport Channel related parameters using RNWPLAN, RNW configuration manager reconfigures the Common Transport Channels and gets stuck while storing and sending the same information to Telecom program blocks because of incorrect usage of array index. This problem needs to be corrected at RNW configuration manager.


Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact

3.73 CHECKSUM check failed for RAQUEL file RAQ2D8QX.IMG

Problem report: NA04778943 Exists in: RN5.0 Correction Target: RN6.0 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04808929 Probability: Permanent Description: Some RAQUEL files integrity check fails as the checksum bit was incorrectly set. As a result few CRC errors were seen for database files. It would be removed in next release. Solution / Workaround: This can be ignored as checksum is not required in DB files. Impact to Operator: Operation & Maintenance, unnecessary checksum failure. Impact to End user: No impact.

3.74 Cell PCH counter M1006C93 & M1006C95 updated incorrectly

Problem report: NA04972911 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / Counters Attached PRs: - Probability: Permanent Description: Counters M1006C93 SUM OF UE OPERATING TIME IN CELL_PCH and M1006C95 NUM OF UE MEASURED IN CELL_PCH are updated even though UE is not in proper PCH state. Solution / Workaround: No workaround Impact to Operator: Statistics / Counters Impact to End user: No impact


3.75 M1023 group (Cell_thrput) reporting multiple MNCs for the same cell

Problem report: NA04841654 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Counters Attached PRs: - Probability: Permanent Description: If UE makes Cell Update from DRNC cell during Cell_DCH to Cell_FACH transition and PS CN already sent Iu Release Command, then RNC uses incorrect PLMN ID to update throughput counters. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact

3.76 NPGEP replied ‘ICMP destination unreachable’ with MTU of next hop is 0

Problem report: NA04939204 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: NPGEP replies ‘ICMP destination unreachable’ to Path MTU discovery even the MTU of next hop is configured with non zero value. That was caused by SW bug in data buffer handling in some special situations. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Data Throughput Impact to End user: No impact

3.77 PS addition fails in NB-AMR7.95kbps



Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: Upgrade/downgrade failed for AMR call during PS call addition at DRNC on IP IUB. PS call addition failed during AMR call bitrate modification at DRNC on IP IUB. Implementation was not done correctly to handle this scenario at RNC. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call completion success Impact to End user: No impact

3.78 SCTP retransmission in SCTP multihoming

Problem report: NA04973409 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: According to NED(wran_conf_ss7_trans_ip_rnc.pdf) and RFC 4960, if PATH.MAX is 4 and ASSOC.MAX is 8 there should be data retransmission 7 times and now retransmission is done 8 times. In addition the extra data retransmission is still on path where the 7th data transmission was sent out and SCTP don't select alternate path. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Data Throughput Impact to End user: No impact

3.79 RRC handles timer T315 expiry indication in Cell Update incorrectly



Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If timer T315 is expired and UE has indicated about it in Cell Update message then RRC was not releasing PS domain resources and was sending its information in Cell Update Confirm message. Hence UE responds with Cell Update with invalid configuration resulting process exception visible as alarm 1078 PROCESS EXCEPTION. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success Impact to End user: No impact

3.80 SP OMU database loading gets stuck

Problem report: NA04937976 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Stability, Unit Restarts Attached PRs: - Probability: Permanent Description: Spare OMU database loading gets stuck if more than one database processes are restarted in the unit. As several databases are restarted during start-up, many loading requests were sent to loading manager. Loading manager cannot handle these requests, so the database loading gets stuck and doesn’t recover. Solution / Workaround: Restarting the SP OMU Impact to Operator: Stability, Unit Restarts Impact to End user: No impact

3.81 DSP error after AMR relocation

Problem report: 68760ESPE02 Exists in: RN5.0 MP2 Correction Target: RN6.0 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success


Attached PRs: - Probability: Occasional Description: If after a succesfull incoming relocation with an AMR call, the AMR bitrate gets downgraded quickly after the relocation, it may result in an signal processing error (0x70340034). Solution / Workaround: No workaround. Impact to Operator: CS fall failure increase. Impact to End user: Call drop.

3.82 Counter M1010C204 CANC_ISHO_CPICH_RSCP_RT is updated incorrectly

Problem report: NA04846361 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / Counters Attached PRs: - Probability: Permanent Description: ISHO cancellation due to RsCp was getting triggered even if the trigger cause was not enabled by the operator. Solution / Workaround: No workaround Impact to Operator: ISHO will be cancelled even if the RNW parameter is OFF. Impact to End user: No impact

3.83 RNC sends wrong Activation Time to both UE and BTS

Problem report: NA04953060 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: When Signalling Link undergoes state transition from FACH to HSPA i.e. F-DPCH is allocated in case no reply is received from UE when UE sends cell update


message. Now in case if RRC could not send much information in Cell Update Confirm like dl_deleted Transport Channel Information for SRB then RRC wrongly sets the SRB-on-HSPA status in its internal tables. Due to that RNC could not provide the right Activation Time to both UE and BTS as Activation Time is calculated based on whether F-DPCH is allocated or not. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Data throughput Impact to End user: Effects on end-user throughput.

3.84 Drop Call Followed By MTC Setup Failure - call to voicemail

Problem report: NA04929108 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: Cell reselection from UE during ongoing state transiition to Cell_DCH causes CS RAB setup to be rejected, if the CS RAB Setup request was received during the state transition procedure. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: Call drop

3.85 PS Drop due to UE increase after upgrade to PP2.11 (RU20)

Problem report: NA04940867 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: NA04946995 Probability: Permanent Description: During state transition from Cell_DCH to Cell_FACH if UE makes Cell Update due to RLC error on user plane after RLC ack for the RRC message sent to command UE to perform transition to FACH, RNC still sends RB Information to the UE in the Cell Update


Confirm and UE does not accept CellUpdateConfirm since it has already reconfiguration ongoing from the previous state transition command. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call Completion Success Impact to End user: PS service drop.

3.86 PS-NRT bit rate is not downgrading to 8/8 kbit/s

Problem report: NA04935453 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: RNC BTS resource manager does not downgrade existing PS-NRT DCH service on 8/8 kbit/s when CS-T service is established. There is a problem inside RNC BTS resource manager leading to fault that PS NRT downgrade is not performed when minimum allowed bit rate in downlink is set to value 384. Solution / Workaround: Minimum allowed bit rate in downlink is defined to be lower than 384. Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.87 RNC OTO restart method does not update SF10E SD4G-A FPGA images

Problem report: NA04915682 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: New feature/functionality, Improvment, load all reset type fpga Attached PRs: - Probability: Permanent Description: SD4G-A FPGA disk images are not loaded to SFU units when RNC restart is performed with ZWSD command using OTO option. The fault happens only with SF10E plug-in units.


Solution / Workaround: Restart SFU units (configured with SF10E) by DSK mode. That loads the new SD4G-A FPGA disk image to the unit. Impact to Operator: No impact, since restart with OTO-option is declined in MP4 installation macro. Impact to End user: No impact

3.88 RL deletion is delayed after CS call release and state change to URA-PCH

Problem report: NA04932916 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: RNC have delay time till RL deletion after DCH-URAPCH state transition even URA update is already received from UE. URA update is handled before completion of URA/PCH transition. This problem is also present in DCH to PCH transition. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance Impact to End user: No impact

3.89 After direct transition from DCH to PCH, RNC forgets the GTP tunnel ID for the PS RAB

Problem report: NA04850449 Exists in: RN5.0 Correction Target: RN6.0 Severity: C - Minor Customer Impact: Operation & Maintenance, Log Attached PRs: - Probability: Occasional Description: If the state transition from DCH to PCH is triggered when there is only PS RAB on 0/0 configuration existing, then RNC forgets about the GTP tunnel established for the PS RAB and starts using new tunnel later when UE is moved to Cell_DCH. The old tunnel is released later on. Solution / Workaround: No workaround.


Impact to Operator: Only computer logs visible. Impact to End user: No impact.

3.90 Increase of DSP ERROR 0x7002004B in RN5.0

Problem report: NA04823925 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, RRC Success Attached PRs: NA04880187, 24245ESPE07, 83270ESPE02, NA04947411, NA04956966, NA04953747, NA04976844, NA04993091, NA05003866 Probability: Permanent Description: The problem is that DSP error 7002004B is observed first during the overload period and continues to occur even after overload period when there is normal traffic leading to the update of the following negative counters: M1001C11 RRC ACC FAIL DUE TO RNC INTER REASONS M1001C21 RRC ACTIVE FAIL DUE TO RNC INTER REASONS. The root cause is synchronization problem between PQ and DSP in some specific situation that the buffer address that DSP wrote data was different the buffer address that the PQ application read. It lead to DSP send date failed since both PQ application and DSP are referring to different buffer address. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: RRC success Impact to End user: No impact

3.91 On Top modules are not loaded to units after system restart if OMU fault happens before getting up

Problem report: NA04924001 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: The code load mode of system restart is recorded in the redbox of active


OMU. If the OMU happen faults before getting up during the system restart, the code load mode would be lost. As the result, OPT would be used as the default value. Solution / Workaround: Restart all units with DSK code load mode. Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.92 WCEL locking fails

Problem report: NA04959718 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: The problem exists in cell locking scenario through RNWPLAN. Here, cell locking acknowledgement gets skipped for cells of WBTS for which COCO/IPNB is not connected, or there is some problem with COCO/IPNB. Thus RNW PLAN manager keeps waiting for acknowledgement for such cells, and after timeout, PLAN operation fails with error 'NO REPLY FROM RNW MANAGER PROGRAM BLOCK (RAKTOR, RNC OMU) TO RNW PLAN MANAGER'. This problem occurs only if there is at least one ok cell as well, for which deletion is required. Cell locking is successful although plan activation failure message is observed. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact

3.93 ESA cannot ping directly connected router when one link is down

Problem report: NA04917273 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Stability, Switchover Attached PRs: - Probability: Permanent Description:


ESA24 is not compactable with HSRP protocol. If one link is broken, ESA24 does not update the HSRP MAC address correctly when gratuitous ARP is received. Solution / Workaround: No workaround Impact to Operator: Stability: Operation & Maintenance Impact to End user: No impact

3.94 Alarm 70030 DISK DATABASE IS GETTING FULL raised but database is never cleared

Problem report: NA04945192 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: DISK DATABASE IS GETTING FULL. OMS Alarm 70030 is raised but database is never cleared. PMGeneric starts db cleanup action periodically (every 1h as default). The cleanup action removed too less data in single period due to bug in algorithm. Solution / Workaround: No workaround Impact to Operator: Operation & Maaintenance Impact to End user: No impact

3.95 70158 alarm on OMS of QYRNC /var/mnt/local/backup is over limit after MP3

Problem report: NA04921218 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, statistics/Counters Attached PRs: NA04917355, NA04929136 Probability: Occasional Description: Alarm is raised to indicate over the limit usage of the /var/mnt/local/backup partition. The increase of the backup archive is because of the inclusion of “/home” directory inside the backup. This was developed as a new feature. Solution / Workaround: No workaround.


Impact to Operator: As the size grows gradually eventually it may consume all the space in the filesystem and thus no more archives can be further stored. This may affect the scheduled backups done by operator. Impact to End user: No impact.

3.96 Degradation on Cell-FACH to Cell_DCH transition Success Rate after RU20 implementation

Problem report: NA04949108 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, COUNTERS Attached PRs: NA04977707 Probability: Permanent Description: During Cell_PCH to Cell_DCH transition, RNC does not update attempt counter for FACH to HS-DSCH allocation but after completion of the procedure and UE transition to Cell_DCH with HS-DSCH allocation, it updates Success FACH to HS-DSCH counters which causes problem that there is more success than attempts. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, counters Impact to End user: No impact

3.97 Occasional call drop due to BRM process exception during HSPDSCH code upgrade

Problem report: NA04964516 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Call completion Attached PRs: - Probability: Occasional Description: Index used to access internal data structures was not handled correctly resulting Radio Resource management (BRM) hand process crashed leading to call drops in all the cells configured in the BTS corresponding to the problematic BRM hand process. Solution / Workaround: No workaround.


Impact to Operator: Capacity & Performance, Call completion Impact to End user: Call drop

3.98 HSDPA Code Allocation problem after RN5.0 MP4 Upgrade

Problem report: NA04964077 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Throughput and Performance of HSDPA calls Attached PRs: - Probability: Permanent Description: The original problem was that the HSDPA code upgrade was blocked in RNC due to the ERGCH/EHICH codes present in higher code ids. Due to this some cells where not given greater than 12 hsdpa codes by the RNC. The problem was, since there was only one ERGCH/EHICH code, there was no optimization done for this code and it was lying in a higher code id blocking the upgrade of hsdpa codes. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance Impact to End user: Data throughput

3.99 When incoming AMR “UE not involved” relocation is done from ZTE, NSN RNC releases the call

Problem report: NA04918730 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Handover Success Attached PRs: - Probability: Permanent Description: AMR intra-frequency HHO does not work leading call drop. Fault occurs because minimum value of TOAWS is too big. Solution / Workaround: No workaround.


Impact to Operator: IFHO fails. Impact to End user: Call is dropped during IFHO.

3.100 RAV on SP-OMU restarted to resolve RAV data checksum inconsistency on WO OMU

Problem report: NA04966257 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: AutoObjmLock is an RNC level parameter which was getting updated in active database through a DB transaction just before database files were copied from active database to new database. In this case there is a possibility where results of transaction are not yet updated to hard-disk and DB files with un-updated RNC record are copied from active data-base to new database causing finally Raviol restart. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.101 Data package drop when bit4 in GTP header is set to 1 instead of 0

Problem report: NA04971157 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: If data package from CN has GTP header's bit4 set to 1 , RNC will drop the package causing traffic problem Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Data Throughput


Impact to End user: data throughput

3.102 Measurement handler server stops working

Problem report: NA04928874 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: A measurement handler server (meahandlerserv) stops working because of a deadlock in EMT (mediator between OMS and OMU) during initiation of the connection with OMU. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact

3.103 RNW plan activation fails with unexpected error

Problem report: NA04954213 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04993137 Probability: Permanent Description: RNW PLAN Manager was unexpectedly trying WCEL unlocking for WCEL’s under a WBTS which was already deleted and for those RNW PLAN Manager was not getting response from RNW MANAGER and thus leads to that unusual WCEL-0 error. Solution / Workaround: No workaround. Impact to Operator: Operability Impact to End user: No impact.


3.104 NPS1P failure leading to unit restart

Problem report: NA04933780 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Stability, Unit Restarts, Fault management:recovery should print faulty PRB when restart because of 1023 alarm Attached PRs: NA04959805 Probability: Permanent Description: Program block JUNGLEs diagnostic thread tries to get service from the name server in OMU at the start-up of diagnostic thread and then with 5 minute interval. If OMU is not responding to the service requests (example in OMU overload situation) diagnostic thread supervision fails and this causes JUNGLE to fail to answer critical actor supervision. And that leads to unit restart. Solution / Workaround: No workaround. Impact to Operator: WBTS down. Impact to End user: UE is not able to connect network.

3.105 After RU20 MP3.0 upgrade, HS drop due to non-RL increase with RNC DSP error

Problem report: NA04924320 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: If PDCP PDU transfer from source to target fails in a DMPG switch scenario, Invalid handling of internal data structures leading to call drop because of sp_error with E_RLC_AM_UM_SE_INVALID_SDU_RESIDUAL. Solution / Workaround: No workaround Impact to Operator: KPI , call success rate Impact to End user: Call Drop


3.106 Counter ICPS_OUTECHO (M563C55) is not updated correctly

Problem report: NA04863081 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics / Counters Attached PRs: - Probability: Permanent Description: When a Internet Control Message Protocol (ICMP) Ec/Ho request is sent out the counter M563C55 (ICPS_OUTECHO) stays 0 even it should be incremented. IP stack is not updating the counter for ICMP echo request packet. The counter can be handled by ZT2 MML-commands. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Statistics / Counters Impact to End user: No impact

3.107 Spare RSMU unit restarted due to ERROR IN SPARE UNIT UPDATE

Problem report: NA04911133 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Stability, Unit restarts Attached PRs: - Probability: Permanent Description: Occasional delay in internal messaging causes temporary UCPROD message queue overload leading to SP RSMU unit restart. Solution / Workaround: No workaround. Impact to Operator: Stability Impact to End user: No impact.

3.108 Incorrect MSC id for counter M1003C45 NBR_OF_SENT_ERROR_IND



Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Counters Attached PRs: - Probability: Permanent Description: Problem was that counter M1003C45 was updated with the wrong PLMN id and CN id resulting that MSC id was incorrect in this counter. Problem occurred because the third object in the Measurement object is reserved for the PLMN id and if PLMN id was not received yet, it was incorrectly updated with default (65535). Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact.

3.109 WBTS and IPNB DSCP values cannot be modified via the RNW plan

Problem report: NA04962306 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04981171 Probability: Permanent Description: 1) User triggers the DSCP modification, the modification of this parameter requires object locking, so IUB link will be broken and then it will be re-established (with changed values of DSCP). 2) VEX (process handling the IUB connection and configuration) will first send message to RAK to delete all the cells from BTS for that particular BTS and will mark cells BL –U. 3) After the cells are Off Air, VEX will remove the IUB SCTP links and will modify the DSCP parameter in database. 4) Both C-NBAP and D-NBAP links will go down and same will be updated in the DATABASE with NBAP interface as NOT Defined. 5) After modification of the DSCP parameter in the RNW database, VEX will initiate the establishment of the IUB SCTP links with changed values of DSCP. 6) After the successful establishment of the IUB SCTP links, VEX will trigger the unlocking of the cells by sending message to the RAK. 7) RAK will remove the BL–U state from all the WCELs under that BTS and will try to make cell On Air. 8) The cell setup is not successful as the NBAP interface is still undefined. 9) So RAK reports the UNKNOWN_NBAP_INTERFACE ERROR and plan activation fails. 10) But once the IUB links come up and audit procedure is triggered which performs the cell setup and cells are On Air.


11) But operator gets information that plan activation is failed with error UNKNOWN_NBAP_INTERFACE ERROR. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact

3.110 DRRC for HSPA call during transition to Cell_DCH causes periodic location update loop problem

Problem report: NA04961124 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: If there is more than one LACs in the RNC area and moves to cell with another LAC then RNC sends new LAC to CN in the RANAP message to CN after a DRRC procedure during transition to DCH and this causes then incorrect LAC to be sent to the UE after completion of LU procedure and UE goes in loop. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: RRC Success Impact to End user: No impact

3.111 Cell PCH counter is not updated correctly

Problem report: NA04947822 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: RelatCell PCH related counters are still counting although the feature is turned off. Even counter CELL_FACH_STATE_CELL_PCH_UPD is zeroed, all others are still counting PCH time although feature is inactive. RRC incorrectly marks UE to be in PCH state but UE is never sent to CELL PCH. PCH to DCH transition is triggered paging is sent which causes


these counters to increment. Solution / Workaround: No workaround Impact to Operator: KPI report showing increment on counters for PCH (M1006C155, M1006C156 ) Impact to End user: No impact

3.112 Alarm 3485 - Scrambling Code Alarms all over the network

Problem report: NA04935063 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: Neighboring cells should not have same scrambling code. This is detected when Intra Frequency Measurement report is received from UE. If detected then Alarm 3485 is raised which prompts the operator to resolve the conflict. When conflict is resolved (By changing scrambling code of one of the cells or all of the cells) then alarm should be cancelled automatically. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance : Alarms Impact to End user: No impact

3.113 Counter M615/267H DSP Resource Utilization counter is not pegging the correct DSP Pools

Problem report: NA04924065 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / Counters Attached PRs: - Probability: Permanent Description: When DSP service pool reconfiguration is ongoing, it is normal that DSP resource utilization measurement does not show the data. However, when DSP service pool reconfiguration was cancelled with MML command “ZWPM:X”, still the measurement was not showing the


data. Solution / Workaround: Make successful DSP service pool reconfiguration so that at least one DSP changes pool. Impact to Operator: Counter M615/267H might stay in state where it is not available. Impact to End user: No impact

3.114 Inter MGW load based AMR does not downgrade the codecs to 5.9

Problem report: NA04938507 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, Call Completion Success. Attached PRs: - Probability: Permanent Description: During AMR reconfiguration, RRC sends AMR rate control message to transport resource manager (TRM). Due to ongoing parallel procedure TRM does not send acknowledgment for AMR rate control message to requester RRC pid, instead sends it to wrong RRC pid. As a result call fails suddenly. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call Completion Success Impact to End user: Call drops suddenly

3.115 Alarm 3217 is reported to both 2N units

Problem report: NA04899338 Exists in: RN4.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Stability, Unit Restarts Attached PRs: - Probability: Permanent Description: Alarm 3217 SYNCHRONIZATION CABLE FAILURE is reported to both 2N redundant units when the FSYNC synchronization cable between the 2N pair units has a fault. MXU (MX622) and SFU (SF10E) have the FSYNC cable.


System reports the unnecessary alarm 3217 to the WO unit, as alarm should be raised only to SP unit in case FSYNC cable problem. Solution / Workaround: No workaround Impact to Operator: Spare MXU dropped to test state Impact to End user: No impact

3.116 DSP Restart due to Fatal Error 0x80000006

Problem report: NA04933406 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, DSP reset Attached PRs: NA04981708 Probability: Permanent Description: NACK message sent for rnc_cip_security_info_req was bigger than the original signal, and was copied into the same memory area as original signal. When trying to release this memory , error was raised. Alarm 1239 DSP SUPERVISION FAILURE was visible and Fatal Error Event in DMPG log. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, DSP reset Impact to End user: No impact

3.117 When configuring BFD/ICMP session new call is rejected

Problem report: NA04914763 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: M1001C6 RRC_CONN_STP_FAIL_RNC and M1001C112 RAB_STP_FAIL_PS_BACKG_RNC are counted during ZYGS. When configure BFD/ICMP session, the configuration information should be synchronized to RSMU unit and rewrite old configuration. During this period the data block is marked as


unusable, so new call will be rejected. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success Impact to End user: Call drops

3.118 Huawei-NSN SRNS Relocation UE-involved HSPA failure due to 'Invalid Configuration'

Problem report: NA04935764 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Handover Success Attached PRs: - Probability: Permanent Description: NSN Target RNC did not use the information received from the Source RNC when SL is mapped on E-DCH correctly and this caused relocation to be rejected by the UE. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Handover Success Impact to End user: No impact

3.119 RNC failing to respond to MTU packet sizes between 1501 to 1505

Problem report: NA04952981 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: User Plane Quality Attached PRs: - Probability: Permanent Description: Nortel's PPX router incorrectly does not remove the Ethernet frame padding when PPX puts an IP over Ethernet tail fragment into an IP over ATM AAL5 frame. Those extra padding bytes at the end of the IP datagram causes that when the UDP length is checked agains the PDU total length in NPS1 of RNC2600 the check fails and the IP datagram is discarded. Solution / Workaround: No workaround


Impact to Operator: User Plane Quality Impact to End user: No impact

3.120 B1B MSC clear code increased after RU20 - radio link lost during security mode procedure

Problem report: NA04945495 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: Improvement has been made in the NSN RNC to three cases where Security procedure was rejected earlier. 1. If RLC was commanded to resume by upper layer and then immediately suspended due to security procedure then in collision cases, it can happen that RLC received the suspend command first before resume command and rejects the suspend command causing security procedure to fail. 2. RNC incorrectly thought that there is Cell_PCh transition ongoing in UE even when UE never received the PCH transition command since SRB 2 RLC made reset in the RNC RLC. 3. If Security procedure failed, RRC layer did not remove the buffered security message command from the RNC RLC in Cell_FACH. Later when UE makes a CU, it receives also the buffered SMC command from RNC RLC and handles it while procedure was cancelled in RNC RLC. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, RRC Success Impact to End user: No impact

3.121 RAB NRT Access failure due to Ue increases after RU20 upgrade

Problem report: NA04952326 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04952288 Probability: Permanent


Description: If UE makes Cell update due to cell reselection during ongoing Radio Bearer Setup procedure in CellFACH after having received the RRC message for setup, then UE continues the procedure for the setup after completion of the Cell reselection procedure while RNC sent new Radio Bearer setup message to the UE without knowing if UE received the previous message and processed it or not. This causes the procedure to fail due to UE having two request for the same RB to setup. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: No impact

3.122 RNC system outage due to OMU unit happen alarm 2690 "POSIX HAS ENCOUNTERED AN UNRECOVERABLE ERROR"

Problem report: NA04919442 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Stability, System restart Attached PRs: - Probability: Permanent Description: OMU restarted because of too many log files in the ST0LOG directory. Service terminal log system didn't delete the old log files because the length of the reference name and the log file name was different. Solution / Workaround: No workaround Impact to Operator: No service available. Impact to End user: No service available.

3.123 MTU default value problem

Problem report: NA04957588 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: 65555ESPE01 Probability: Permanent


Description: Fullmesh IPoA interface of local subnet is cleared in case of internal path between NPGEP and ICSU is broken, such as status of both NPGEP change to SE-NH. IP interface of IPoA is re-created and IP address is assigned again automatically when the internal path recover. But MTU size is configured as default setting. In another situation, when local subnet is deleted, IP address of fullmesh IPOA interface will be deleted, then configure the local subnet again, the MTU of IPOA interface will be set to default value (default MTU value is 1472 for ICSU and 1500 for NPGE(P)). MTU size is reflected to SCTP session when new session is created, so SCTP session has to be reset when the session is established before modifying MTU size. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact

3.124 During CELL_FACH to CELL_DCH transition, RBR Complete is not received by RNC

Problem report: NA04891743 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: During state transition to Cell_DCH, RNC does not inform the latest received propagation delay to BTS in the NBAP RL Setup Request which can impact during the RL sync procedure. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: Call setup does not succeed

3.125 UE is not responding to paging in URA_PCH state

Problem report: NA04905840 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: -


Probability: Permanent Description: UE is not responding to paging in URA_PCH state. RRBPRB sends paging to UE by using incorrect drx cycle length parameters. The current RRCPRB/RRBPRB implementation is such that all cells basically have to have the same DRX cycle length in case URA-PCH state is used. RRCPRB does not pass the current (or latest) cell of the UE in URA paging request. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Completion Success Impact to End user: No impact

3.126 Alarm 3568 IUR INTERFACE SIGNALING FAILURE raised incorrectly in case of UE involved SRNS relocation without IUR interface

Problem report: NA04926024 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: UE involved SRNC relocation can be performed to target-RNC without Iur connection between source and target RNCs. Required neighbouring RNC information is configured into the RNC radio network database. Also in these cases an Iur object can be created in order to get 3GPP release version of neighbouring RNC from Iur object (otherwise source RNC must just guess what is 3GPP version of target RNC). In these cases problem is that RNC sets an alarm 3568 IUR INTERFACE SIGNALING FAILURE, because Iur connection is not working. Solution / Workaround: No workaround Impact to Operator: Alarm 3568 IUR INTERFACE SIGNALING FAILURE is not set, if neighbour RNC signalling point code is zero. Impact to End user: No impact

3.127 ICSU-12 automatic switchover after 3188 and 1290 alarms occur



Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Stability, switchover Attached PRs: - Probability: occasional Description: ICSU-12(Wo-Ex) was continuously reporting 3188 - NO RESPONSE TO AAL5 CHANNEL SUPERVISION alarm and a Disturbance alarm 1290 - INTER-COMPUTER MESSAGE CONNECTIVITY LOST and took switchover with ICSU-8 (Spare) and ICSU-12 has taken to diagnose but the unit found OK.At the same time MXU's has also observed 3049- FAILURE IN PORT CONFIGURATION alarm. UX2FPGAF.IMG 1.11-0 is not working correctly. Solution / Workaround: ICSU switchover Impact to Operator: KPI Impact to End user: no impact

3.128 Several Node-B sectors going to BL(I)

Problem report: NA04900861 Exists in: RN4.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Cell availability Attached PRs: NA04900324 Probability: Permanent Description: During cell locking under high load MAC-c makes an exception and crashes. MCFTOR crashes into exception caused by a NULL pointer when capa_req_buffer is used to store capacity requests (load cutter is active). Solution / Workaround: No workaround Impact to Operator: Cell availability Impact to End user: Call drops

3.129 Data forwarding support for PS service fails during SRNS relocation



Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: During SRNS relocation, the buffered data in PDCP/RLC layer is not forwarded to target RNC. This buffered data is discarded by NSN RNC when acting as source RNC. As a result there can be a delay/stop in data transfer due to high layer retransmissions. It has been noticed that relocation can cause TCP traffic to stop for a short period of time. Solution / Workaround: No workaround Impact to Operator: KPI, Capacity & Performance Impact to End user: Data throughput

3.130 Cell bouncing problem after CMAS activation

Problem report: NA04988866 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Cell Availability Attached PRs: - Probability: Permanent Description: RNC was continuously deleting and creating common channels which have reported CMAS/SAI failure. RNC has an automatic recovery mechanism where CMAS/SAI failures are monitored and if some fault is seen CCH recovery is triggered. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Cell availability Impact to End user: No impact

3.131 Handsets are not receiving CMAS messages

Problem report: NA04988873 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: CMAS functionality Attached PRs: -


Probability: Permanent Description: Problem was that CMAS (Commercial Mobile Alert Service) messages did not reach UEs when N was set to 255. In some situations the mapping of CTCH blocksets to FACH TTIs was done incorrectly and in some cases incorrect scheduling message was sent breaking the scheduling message chain. As a result CMAS messages send by RNC were not possible to be received correctly by UEs. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.132 NWI3TU crash repeatedly after unlocking cell

Problem report: NA04973670 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: Coding error with parallel use of same pointer in few threads .As a result of this NWI3TU crash repeatedly after unlocking cell. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.133 OMS backup issue

Problem report: NA04917355 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04900935, NA04929136 Probability: Permanent


Description: As part of Security Hardening, the backup folder and the resulting archive have been given special permissions so that only root users can access those. This was needed because the backup archive contains licenses and other credentials in a plain format. So any non-root user can have access to these. Solution / Workaround: No workaround. Impact to Operator: OMS uses non-root account to access the backup folders and denying access to those folders means one cannot move the backup archive to other machines before one can do full restoration of the node. Impact to End user: There will be no impact to end user.

3.134 PS call drop during state transition/channel type switch (DSP error 70680017)

Problem report: NA04910079 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: NA04953656 Probability: Permanent Description: During DMPG switch (triggered by state transfer from DCH to FACH and vice versa), as part of context information, DL SDU residual information for first SDU is transferred from source DMPG to target DMPG. Later if first SDU is reached to the target DMPG from source DMPG, the SDU residual information should be used, otherwise not. In current scenario it is used even in data transfer failure case. So the first SDU actually comes from EIPU with different SDU size and it is tried to be wrongly decoded leading to severe error 70680017 and call drop. Solution / Workaround: No workaround Impact to Operator: Occasional call drop Impact to End user: Occasional call drop

3.135 70273 REQUIRED SERVICE UNAVAILABLE

Problem report: NA04918034 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04963355, NA04979969, NA04653609, NA04983773


Probability: Occasional Description: Problem occurs semi-randomly when low memory zones are exhausted by userspace allocations Solution / Workaround: Problem can be mitigated by enabling lower zone protection mechanism by issuing following command as a root user in OMS: Add line: vm.lower_zone_protection=200 to a file /etc/sysctl.conf , and after modification execute command: # fsdistribute /etc/sysctl.conf , Reset OMS with command: # fshascli -r / Impact to Operator: Out Of Memory -killer entries visible on master syslog, random failures of any OMS subsystems, with opening Application Launcher, Fault Management and other applications, as well as missing measurements or measurements not being transferred to Netact, are possible when problem happens. Impact to End user: No Impact

3.136 Delay in handling of UL user plane data in case of bursts of small UL packets

Problem report: NA04972604 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: User Plane Quality Attached PRs: - Probability: Permanent Description: Due to burst of data traffic, internal L2 functionality of sending multiple UL packets to upper layers was disabled. As a result, when UL packet size was small, the packets were first buffered inside RNC L2 and not forwarded to upper layers immediately causing delay in UP and resulted also to TCP retransmissions. Propability of the problem is higher when Dual Cell feature is in use when DL side throughput is higher. Solution / Workaround: No workaround Impact to Operator: User Plane Quality Impact to End user: No impact

3.137 RRC Connection Setup Success Ratio Degradation



Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, RRC success Attached PRs: - Probability: Permanent Description: Many resources are hanging in RNC which is causing failure in new call creation. The problem occurs because UP is sending Nack for NRT when PCH to DCH state transition ongoing. RRC assumes that this is a complete failure but resources remains hanging. Solution / Workaround: No workaround Impact to Operator: RRC success rate decreasing Impact to End user: Problems when making calls

3.138 After fast call setup PCH to DCH transition IFHO failed

Problem report: NA04873985 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: During transition from PCH-FACH-DCH , DCH state data is received during FACH state and hence severe error 7002001A was raised. That causes call drop leading to increase in M1001C196 (RAB ACTIVE FAILURES DUE TO RNC FOR PS DATA BACKG) counter. Solution / Workaround: No workaround Impact to Operator:Call Completion Success Impact to End user: Call failure

3.139 Alarm-flood of alarms 7750 FAILURE IN WDCMA WBTS O&M CONNECTION

Problem report: NA04887150 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP5 Severity: A - Critical


Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Occasional Description: When BTS O&M connection is established in “secure” mode simultaneously for large number of BTS (close to 600) then some of the existing connections start to get released. This happens because supervision timers at RNC are timing out for those BTS as during the supervision time, RNC is not receiving supervision messages from lower layers due to message flood created by secure connection establishments. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance Impact to End user: No Impact

3.140 Maximum CPC gain can not be achieved

Problem report: 25435ESPE05 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: User Plane Quality Attached PRs: - Probability: Permanent Description: SIR target moves slowly over 10% with low activity (ping). Target goes back to 10% when ftp transfer is started and increases again after FTP is stopped. Solution / Workaround: No workaround Impact to Operator: Increased roundtrip as more HARQ retransmissions are used. +40ms for 10ms TTI and +16ms for 2ms TTI UEs. Maximum CPC gain can not be achieved as air interface is less idle because of extra retransmissions. Impact to End user: Increased roundtrip times after some time and CPC gain not maximized.

3.141 Reduction in HS throughput data rate after RN5 RU20 PP2.2 + UER ontop SW Upgrade



Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Occasional Description: Wrong Kuorma sw version is loaded in EIPU for Iu-PS interface in system startup. This causes defragmentation function missing in APP for Iu-PS. Solution / Workaround: restart SP EIPU. Impact to Operator: Capacity & Performance Impact to End user: PS call Data throughput reduced

3.142 Plan operation failure due to internal process crash resulting alarm 70159, NEW

Problem report: NA05013933 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: It was possible that plan operation failed in very rare exception case due to internal problem in handling of thread cancellation resulting process crash. This resulted to exception "CORBA object not exists" or "Requested service not found" and was visible by following alarm - OMS ERROR 70159 MANAGED OBJECT FAILED. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact

3.143 High AFR linked to Quality of Service implementation (M1002C555 increasing), NEW

Problem report: NA05007073 Exists in: RN5.0 Correction Target: RN6.0 Severity: A - Critical Customer Impact: Operation & Maintenance, Statistics / Counters


Attached PRs: 97093ESPE02 Probability: Occasional Description: RNC BTS resource manager fault caused that counter M1002C556 (NRT DCH SETUP REJECT FOR INTERACTIVE DUE TO POWER LIMITS) was not updated when channel type switch from HSPA to DCH failed for background radio bearer. This caused significant increase of NRT DCH Failures due to DL Power Admission Control. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Statistics / Counters Impact to End user: No impact

3.144 Collision between Cell update (CU) and Security Mode Command (SMC) procedure in RNC, NEW

Problem report: NA05011406 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: If UE makes cell reselection during ongoing security procedure ,RNC will suspend the security procedure and it will start hanging Cell Update first but on completion of cell update procedure, it could not handle the security procedure correctly and this will cause all further security procedures to be rejected until UE has made new Cell update.RNC forgets to mark that RLC has been already re-established during the cell update procedure and as a result RNC keeps waiting another Cell Update to re-establish the RLCs. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, RRC Success Impact to End user: No impact

3.145 Occasional failure in handling of a long SMS in standalone CS signaling connection, NEW



Customer Impact: New feature/functionality, SMS handling Attached PRs:- Probability: Occasional Description: If there was standalone SRB active without PS connection and the RANAP timer for supevision of RAB setup procedure from CN expired in RNC, then RNC initiated Iu release immediately without checking activity of SRB. This can cause failure in sending or receiving of a long SMS if it can't be completed in 45 seconds before RANAP timer for supervision of RAB setup procedure from CN expires Solution / Workaround: No workaround. Impact to Operator: Functionality / SMS handling Impact to End user: Sending / receiving of very long SMS can fail

3.146 Alarm 1078 Process Exception because RRC in hanging state, NEW

Problem report: NA04969928 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Operation & Maintenance, Alarms, Call Setup Success Attached PRs: - Probability: Permanent Description: If attempt from Cell_PCH to Cell_DCH transition fails due to no response from paging from UE then hand process of RRC goes to hanging state in the next state transition to Cell_DCH attempts until it is forcibly released after failed supervision. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Operation & Maintenance, Alarms, Call Setup Success Impact to End user: No impact

3.147 RNC cannot handle long delayed response to RBR, NEW



Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: If Cell Update from UE arrived too late during Cell_DCH to Cell_FACH transition, UTRAN cannot handle the UE response correctly which caused mismatch in the HFN used in RNC. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Data Throughput Impact to End user: No impact

3.148 SRNC relocation rejected when all radio links are under DRNC, NEW

Problem report: NA05006516 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Handover Success Attached PRs: - Probability: Permanent Description: RNC does not perform SRNS relocation when all the radio links are in the DRNC because of standalone signaling connection with CS CN. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Handover Success Impact to End user: No impact

3.149 NBAP overload algorithm in IPRAN is too strict, NEW

Problem report: NA05006288 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: NA05005976, NA04919814 Probability: Occasional


Description: NBAP overload algorithm in IPRAN too strict as a result high amount of RRC connections got rejected in IP case. 1. This fault affects only pure IP Iub. No effect on Dual Iub or ATM Iub 2. Fault is visible to the customer via following counters: - M1001C4 RRC_CONN_STP_FAIL_BTS will show big figures in pure IP Iub - M1006C203 RRC_CONN_REJ_IUB_OVERLOAD is either not updated at all or showing very small figures in pure IP Iub 3. If one monitors the call traffic in ICSU, over 90% of the M1001C4 RRC_CONN_STP_FAIL_BTS counter updates are due RNC internal rejections with “due to BTS” cause. NBA does initially limits the RL setup but doesn't forward any limit values to RRB and also the limits values remain too strict and never changed for IP link. As a result, the overload limits are never adjusted in IP case. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success Impact to End user: No impact

3.150 Delay in handling of Location Report procedure, NEW

Problem report: NA04979897 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: RNC does not handle Location Reporting Control from CN during ongoing SRNS relocation until it has completed also internal signaling which delays the handling of Location Report procedure. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, RRC Success Impact to End user: No impact

3.151 DL DPCH Slot Format change causing drop in SRNS relocation, NEW



Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: During SRNS relocation from other vendor SRNC NSN RNC internally changed the multiplexing position from fixed position (used by source RNC) to flexible position (which is the NSN setting for this IE when DPCH slot format 9 is used) but this parameter wasn't sent to UE and BTS (as no reconfiguration is done during UE not-involved relocation) and this caused problems later. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call setup success Impact to End user: Call drops

3.152 Occasional PS call drop after radio link failure resulting counter M1022C58 HS-DSCH/E-DCH PACKET CALL increase, NEW

Problem report: NA04996868 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: NA04921912 Probability: Occasional Description: If radio link failure happens during DCH to HSPA/HSDPA channel switch before UE receives the command for performing channel switch, then RNC does not know what configuration UE has and after call re-establishment, it forgets to delete the DCH transport channel from UE if it allocates HSPA or HSDPA later. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Completion Success Impact to End user: PS call drop

3.153 Bad performance accessibility and RNC Hardware Congestion control after Direct Resource Allocation feature activation, NEW



Exists in: RN5.0 Correction Target: RN6.0 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: After activating the RABDRAEnabled (Usage of the direct resource allocation for PS NRT HSPA) feature to optimize PS call setup time, PS Accessibility went down. Quicker setup will cause messages to come earlier and that increases CPU load. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.154 Wcells remain locked after upgrade to RN5.0 MP4 SW, NEW

Problem report: NA04973732 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Cell availability Attached PRs: - Probability: Permanent Description: After RNC upgrade to RN5.0 MP4 SW lots of cells remains in BL-I state. During upgrade C_NBAP links gets re-distributed among ICSUs due to MNFILE conversion but RNW database and its NBAPRB pids are not modified or initialized and they get completely out of sync with the new link distribution .As a Consequence of this BTS manager got wrong wbts/wcel data in startup from RNW DB and in later stage during cell setup actually cell data was missing and this leads to cell setup failure. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Cell availability Impact to End user: No impact

3.155 Voice quality problem after IFHO due to ciphering mismatch, NEW



Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: User Plane Quality, Voice Quality Attached PRs:- Probability: Occasional Description:UE calculates new start for CS during RLC re-establishment which is not allowed according to specification.UTRAN did not store the new start value causing ciphering mismatch during IFHO which resulted to voice quality problems in this case Solution / Workaround: No workaround. Impact to Operator: User plane quality / Voice quality Impact to End user: Voice quality

3.156 MAC-hs Guaranteed Bit Rate IE value 'zero' is not supported by DRNC, NEW

Problem report: NA05000334 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: New feature/functionality, HSPA over IUR Attached PRs: - Probability: Permanent Description: NSN DRNC did not support HSDSCH setup or modification if Guaranteed Bit Rate for MAC-HS was set to zero .RNC rejected HSDSCH setup request over IUR in that case (though 3GPP allows DRNC to treat this as no GBR applied). Optimally, SRNC should not send the GBR 0 since it indicates GBR is not applied but NSN DRNC can also accept such suboptimal requests from another vendor SRNC because it is allowed behavior of Source RNC according to 3GPP. Solution / Workaround: No workaround Impact to Operator: New feature/functionality, HSPA over IUR Impact to End user: No impact

3.157 NPGEP sync alarm 3245 appears if WO NPGEP receives continuous ARP packets, NEW



Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: 81982ESPE02 Probability: Permanent Description: When WO NPGEP is synchronizing data to SP NPGEP, and if WO NPGEP receives continuous ARP packets, it will cause synchronization to exceed 5 minutes, and then SP NPGEP reports the alarm 3245 PEER SYNC PROBLEM IN REDUNDANT HW FORWARDING. Solution / Workaround: No workaround Impact to Operator: Operation & maintenance, alarms Impact to End user: No impact

3.158 Connection with E398 mobile on some WBTS not possible, NEW

Problem report: NA04986966 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: C - Minor Customer Impact: Capacity & Performance, Cell availability Attached PRs: NA05006384 Probability: Permanent Description: Two problems exist 1. Cell does not come up when both MOCN and LTE Interworking features are enabled for the cell. 2. UE do not camp on when operator enables LTE Interworking but do not define ADJL/HOPL objects, First fault came because RNC do not calculate SIB Scheduling parameters correctly. SIB update fails and cells do not come up. 2nd fault came because RNC send corrupt SIB19 when operator has enabled LTE Interworking but did not define ADJL/HOPL objects Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Cell availability Impact to End user: call not possible


3.159 Noise auto tuning resulting too low noise level if BTS uses MHA and reports very low RTWP values, NEW

Problem report: NA04981460 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup failures / AC reason Attached PRs: - Probability: Permanent Description: Noise auto tuning feature was not working correctly on case that BTS is using MHA feature and reports very low RTWP values to RNC. On this case RNC tuned noise level very low and noise value was not recovered correctly back to original level when traffic comes on cell. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance Impact to End user: No impact

3.160 Not possible to create more than 65535 ADJS objects in RNC by RNW plan operation, NEW

Problem report: NA04972576 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: More than 65535 ADJS objects cannot be created in RNC through RNW plan operation. But as per requirement ADJS limit to be created in Database are 148800. RNW plan manager did not allow more than 65535 ADJS objects because the data-type of the counter variable, which keeps track of maximum allowed ADJS objects was declared as "word (2-bytes)". And word is limited by 65535. Therefore, creation of more than 65535 ADJS objects through plan manager failed. Solution / Workaround: The additional ADJS objects can be created successfully through OMS. Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact


3.161 "M1002C423 SETUP_FAIL_UE_HS_DSCH_BGR" was degraded after HSUPA 2msTTI & HSUPA5.8M activation, NEW

Problem report: NA04996573 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, HSUPA accessibility and retainability Attached PRs: - Probability: Permanent Description: Following two problems have been identified for HSUPA accessibility and retainability problems: 1. E-DCH minimum set E-TFCI value change, if the UE is suffering from lack of Tx power it cannot send SRB PDU or RB PDU of the RAB. This will cause RLC reset and call dropping. The current UE parameterization does not guarantee any transmission in UE Tx power limited case. A minimum set of E-TFCs is the largest E-TFC that can be used by the UE independent of the UE power situation, given that a valid (absolute) grant is available and there is no transmission on DCH. UE determines the blocked or supported state of each E-TFC for every MAC-d flow configured based on its required transmit power versus the maximum UE transmit power. The UE shall consider that E-TFCs included in the minimum set of E-TFCs are always in supported state. Usage of HSUPA 2 ms TTI in too bad condition will cause RLC resets and call droppings and SIR target can rise up to the maximum value in such conditions. The current threshold value of the CPICH RSCP for HSUPA 2 ms TTI selection is not tight enough. Secondly due to low accuracy of UE reported CPICH RSCP values more safe margin is needed. That is why parameter change CPICHRSCPThreEDCH2MS (CPICH RSCP Threshold for E-DCH TTI 2 ms) is strongly recommended to avoid RTWP spiking. The current default value of the CPICHRSCPThreEDCH2MS (CPICH RSCP Threshold for E-DCH TTI 2 ms) parameter set to 136 dB gives too large coverage to use E-TTI=2ms within the cell. It has been seen that reported CPICH RSCP by UE is around -98 dam or worsen when the RLC resets occurs. Because of that it is recommended change default value to 125 dB, see the equation below. 2. Low DPCCH power with low bit rate 2ms TTI E-DCH connections , The current values of Dynamic HSUPA Power Offsets seem to drop DPCCH power of low bit rate 2ms TTI E-DCH connections too low. This means E-DPDCH power gets pretty high and SIR target goes down. This causes: - Higher RTWP values and low BLER because the minimum SIR target can be met - Lower throughput in the start of E-DCH allocations because the SIR target is higher and BTS schedules only certain grant (power) to the UE There was defined too high powers for E-DPDCH(s) TTI=2 ms relative to the amplitude ratio of DPCCH for used E-TFCI reference point when the HSUPA power offsets optimized for low bit rates was used causing very high initial SIR targets. For HSUPA accessibility and retainability problems refer also to RNC Technical note 159 “NSN recommended parameter set and enhanced algorithms for optimizing uplink RRM functionalities”.


Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: HSUPA accessibility and retainability Impact to End user: No impact

3.162 Transport layer address missing in RAB Assignment Response, NEW

Problem report: NA04986688 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: If the UE is in Cell_PCH and RNC sends RAB Assignment Request to release the PS RAB, RNC sends paging to the UE and sends response for successful release to PS CN. If CN immediately sends new RAB Assignment Request to setup same RAB, RNC sends response for that also to CN before previous RAB release has been executed and sends the response without any valid transport layer address in the response. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Data Throughput Impact to End user: No impact

3.163 Plan download causes OMS-OMU (EMT) connection break, NEW

Problem report: NA04989861 Exists in: RN5.0 Correction Target: RN5.0 MP5 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: NA05021814 Probability: Occasional Description: With RU20 EP1 release, Plan download gives errors in Netact-OMS and OMU RNW PLAN CONSISTENCY CHECK FAILED: ILLEGAL TARGET SUBDATABASE. This was observed when ADJL objects were tried for creation for at-least 2 WBTS objects having identical LCR ids.


Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact


4. GENERIC FAULTS CORRECTED IN RN5.0

4.1 Generic faults corrected in RN5.0 MP3

4.1.1 RRC is sending CUC although the RLC has been released

Problem report: NA04794998 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: New feature/functionality, Code optimization Attached PRs: - Probability: Permanent Description: After RRC have sent first Cell Update Confirm (CUC) message it set’s repeat timer. This timer is used to repeat CUC sending if UE is not answering to CUC. If UE is lost during Cell Update (CU) procedure and resources are released the RRC repeat timer still is going on. RRC needs to reset repeat timer during releasing resources to avoid extra CUC sending. Solution / Workaround: No workaround. Impact to Operator: Functionality / Code optimization Impact to End user: No impact.

4.1.2 Increase of counter M1005C68 (RL DEL ON SRNC DUE TO ACT RL SYN FAIL) since RU20 MP2 upgrade

Problem report: NA04829239 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: If synch indication hadn't been received when a radio link was deleted, counter M1005C68 (RL DEL ON SRNC DUE TO ACT RL SYN FAIL) was incremented even though radio link deletion was caused by some other reason. Solution / Workaround: No workaround.


Impact to Operator: Increase of counter M1005C68 since RU20 MP2 upgrade. Impact to End user: No impact.

4.1.3 Spikes in HSDPA setup failures due to RNC

Problem report: NA04835326 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: After incoming ISHO from GSM to 3G, RNC does not handle state transition to Cell_FACH correctly if there is HSDPA or HSPA call ongoing and UE looses radio connection with the network and later after re-establishment of the connection, all state transition attempts to Cell_DCH keep failing. Solution / Workaround: No workaround. Impact to Operator: HSDPA setup failures due to RNC increases. Impact to End user: UE looses radio connection with the network and later state transition attempts to Cell_DCH keep failing.

4.1.4 After signalling connection release, RRC will not handle RRC procedures properly

Problem report: NA04866257 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: If RRC connection release procedure started internally in RNC but during this processing the procedure was cancelled since UE triggered Initial direct transfer message for other CN domain, RRC internal resources remains hanging. During RRC Connection Release procedure, if Initial direct transfer has been initiated by UE for other CN domain, RRC connection release procedure has been cancelled internally and Signalling connection release procedure is initiated for the concerned CN. But RRC was not handling cancellation process properly, thus resulting in hanging resources. Solution / Workaround: No workaround.


Impact to Operator: Capacity & Performance / Call setup success Impact to End user: Call setup success.

4.1.5 RRC is sending wrong counter (SUM OF HSDPA USER CONNECTION DURATION) value

Problem report: NA04689721 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics Attached PRs: - Probability: Permanent Description: RRC is sending wrong counter (SUM OF HSDPA USER CONNECTION DURATION) value for updating at times and thus counter has unrealistic values at times. Problem was detected when log writing is generated for "corrupted counters". Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Statistics Impact to End user: No impact.

4.1.6 Heavily loaded BTS causes ICSU spontaneous restart

Problem report: NA04810765 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability, Unit restarts Attached PRs: - Probability: Permanent Description: Moving UE lost synchronization because of overloaded target unit in BTS which is not able to provide answer within time limit. Lost of synchronization caused extra acknowledge message to source unit. Acknowledge message after completed moved UE cause memory protection error of critical family master and spontaneous ICSU unit restart. Solution / Workaround: No workaround. Impact to Operator: Stability, Unit restarts Impact to End user: No impact.


4.1.7 DSP's are restarting

Problem report: NA04758263 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If reserved DMCU resources were released during the last Cell_FACH to Cell_FACH transition then they need to be reserved again during Cell_PCH to Cell_FACH transition. Due to internal data structures not set correctly, RRCPRB forgets to ask to reserve the resources for the user RB and this cause later problem in the state transition to Cell_DCH causing invalid request to be sent to RNC L2 and Transport Manager in the RNC. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: No impact.

4.1.8 Alarm cancellation time is reporting as Alarm Generation time in OMS, where as in OMU alarm generated time & Cancellation times are different

Problem report: NA04806222 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Problem is caused by synchronization mechanism which compares list of alarms received from NE and list of alarms from OMS database. In a case when there are alarms in OMS database but are missing in alarms received by NE such alarms are canceled automatically and rise time is put like cancel time. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact.


4.1.9 OMS processes shut down

Problem report: NA04808575 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04815921 Probability: Permanent Description: Finishing plan upload one of the LDAP session was not closed. This cause problem with connection and measurements transfer and CMPlan operations are not possible without OMS restart which clear the situation. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact.

4.1.10 ATM COCO parameter "ALAL2PathType" is empty

Problem report: NA04800935 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04813187 Probability: Permanent Description: COCO object can't be created by Object Browser when two licenses Path Type and HSUPA RRM aren't available. Solution / Workaround: No workaround. Impact to Operator: Can't create COCO object by GUI. Impact to End user: No impact.

4.1.11 Warning message for adding to many adjacency

Problem report: NA04854850 Exists in: RN5.0 Correction Target: RN5.0 MP3


Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: At present situation Object Browser GUI in OMS display warning window when number of ADJ (Adjacencies) under WCELL is equal 60. Limit in validation of ADJ quantity should be 48. Solution / Workaround: No workaround. Impact to Operator: Warning windows is currently seen only during creating 60th ADJ. Impact to End user: No impact.

4.1.12 The parameter value is changed after plan Pre-Activated

Problem report: NA04817651 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: The value of COCO parameter "AAL2LossRatio" was changed to default after Pre-Activate. The operator was not able to set required value for this parameter during COCO creation. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact.

4.1.13 Inter RNC SCC fails occasionally if Source RNC Cell and Target RNC cell ids are same

Problem report: NA04814357 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Handover Success. Call may also drop later in poor radio condition after the failed relocation Attached PRs: -


Probability: Permanent Description: If Inter RNC HSDPA mobility feature is enabled and the DRNC RL in the Active set of UE has the same Cell ID as the SRNC RL, then SRNC does not handle the Inter RNC relocation correctly and sends invalid configuration to UE, causing the call to be dropped. Solution / Workaround: The feature should be disabled. Impact to Operator: KPIs, Relocation failures in SRNC side Impact to End user: Call drops occasionally in the RNC border areas due to failed mobility attempts.

4.1.14 RNC does not send band-XI InterFreq UARFCN with "Measurement Control" to Rel8-UE

Problem report: NA04816579 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Capacity & Performance, Call Completion success Attached PRs: - Probability: Permanent Description: With Rel8 UE RNC does not read correctly the UE capability from the RRC Connection Setup Complete message and does not send band-XI InterFreq UARFCN on Measurement Control message to UE. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call Completion success Impact to End user: No impact.

4.1.15 RNW Plan download fail with no free hand

Problem report: NA04811027 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: RNW Configuration Manager sends incorrect response for cell unlocking to


RNW Plan manager, if some other operation is going on for same cell. This causes no response from RNW Plan manager, and the timer to wait for response is set incorrectly in RNW Configuration Manager. This causes deadlock between RNW Plan manager and RNW Configuration Manager, further causing no free hand error. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact.

4.1.16 M1001C150 RAB_ACT_FAIL_CS_VOICE_RNC counter is increasing in RNC

Problem report: NA04805321 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: Due to wrong data received in RANAP: RELOCATION REQUEST message, RANAP protocol PRB was going down which leads to all the ongoing calls on the same ICSU are released. Solution / Workaround: No workaround. Impact to Operator: Call drop rate increases. Impact to End user: Call drops.

4.1.17 DSP error during Compressed Mode start

Problem report: NA04866012 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: Sometimes timeout signal is in message queue when Iub connection is removed. Handling of the timeout after Iub connection removal caused null pointer usage and this leads to DSP severe error. Solution / Workaround: No workaround.


Impact to Operator: DSP severe errors (error code 70020007). Impact to End user: No effect to end user since call is in release phase and Iub connection is removed.

4.1.18 ICSU RRC process exceptions after RU20 PP2.11 upgrade

Problem report: NA04845391 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: Radio Resource Management entity in RNC is not able to handle the failure due to congestion during PS RAB user plane creation when congestion is faced in the opposite direction than the RAB specific direction Radio Resource Management entity keeps on retrying in the incorrect direction causing a structure overflow and hence memory protection error is observed. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance/Call completion success Impact to End user: Call drops to FACH.

4.1.19 Radio resource management entity is not able to handle partial failure happening during multiple RL

Problem report: NA04857266 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: Radio resource management entity is not able to handle partial failure happening during multiple RL addition in single request from Handover Control entity because of which it is not able to handle any new requests from other entities and prints error logs and finally UE drops to FACH state. Solution / Workaround: No workaround.


Impact to Operator: Capacity & Performance/Call completion success Impact to End user: UE drops to FACH state.

4.1.20 After failed SRNS relocation, RNC did not cancel relocation from the RNC RLC internally

Problem report: NA04856948 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: NA04896430 Probability: Permanent Description: After failed SRNS relocation, RNC did not cancel relocation from the RNC RLC internally which causes call to be dropped later when new configuration is given to RLC. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call completion success Impact to End user: Call drop

4.1.21 TIIPRB process exception

Problem report: NA04800303 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Counters and Statistics Attached PRs: - Probability: Occasional Description: TII PRB crashes occasionally causing loss of packet call statistics. Solution / Workaround: TII crash happens only when Traffica application is in use; stop using Traffica application is a workaround to prevent TII from crash. Impact to Operator: Packet call statistics not available. Impact to End user: No impact.


4.1.22 RRA restarts (leading to WO-ICSU restart) while restarting traffic

Problem report: NA04823848 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Capacity & Performance, Call setup success Attached PRs: 53603ESPE01 Probability: Permanent Description: IUB protocol entity in RNC i.e NBAP was sending duplicate link creation request message to BTS and Cell Manger entity in RNC which results into duplicate BTS specific hands of Admission control entity and ICSU restart problem. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance: Call setup success Impact to End user: No impact.

4.1.23 Signalling Radio Bearer Enhanced DCH HARQ process ID change problem leading call drop

Problem report: NA04862903 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: When BTS reallocated SRB E-DCH HARQ process ID during E-DCH power offset update the new HARQ process allocation was not sent to UE and other BTSs in E-DCH active set. Because of this UE and BTS were using different HARQ process for SRB and so SRB stopped working. Solution / Workaround: Disable E-DCH TTI 2ms. Impact to Operator: Call drops and is then re-established after a cell update. Impact to End user: Call drops and is then re-established after a cell update.

4.1.24 Unnecessary HSPA-R99 channel switch



Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, RAB reconfiguration Attached PRs: - Probability: Permanent Description: If event 1c replaces current SRNC HSDPA serving cell Handover control does not trigger SCC to other active set cells (both are DRNC cells), it assumes that UE go to the anchoring state and trigger channel type switch to DCH/DCH. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance: RAB reconfiguration Impact to End user: Unnecessary switch to R99 cell.

4.1.25 Alarm 3194 LCS CAPACITY FAILURE is increasing gradually

Problem report: NA04746053 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Other: LCS Attached PRs: 52152ESPE01 Probability: Permanent Description: DILPRB cheks the CPU load of OMU though it should check the CPU load of ICSU. Solution / Workaround: No workaround. Impact to Operator: After correction DILPRB raises alarm only when CPU load of ICSU is too high. Impact to End user: No impact.

4.1.26 WCEL unlocking fails with cause Unknown NBAP interface type after IP WBTS recreation



Customer Impact: Capacity & Performance, Cell availability Attached PRs: - Probability: Permanent Description: After WBTS IPNB modification and re-connection, WBTS and WCEL remains down. While IPNB disconnect, BTS manager got stuck in the CNBAP link removal procedure and due to fresh CNBAP link creation/activation was not handled properly and this lead to WCEL unlocking failure with unknown interface type. Solution / Workaround: No workaround. Impact to Operator: WBTS and WCEL down. Impact to End user: Call not possible.

4.1.27 CS Call is dropped after successful RRC Connection re-establishment

Problem report: NA04812879 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: NA04827774 Probability: Occasional Description: If the overall CS re-establishment procedure takes too long time then internal timer in the RNC supervising the re-establishment procedure elapses and it triggers the call to be dropped even when the re-establishment was done successfully. Solution / Workaround: No workaround. Impact to Operator: KPIs, CS RAB Act Fail counters Impact to End user: Call drops.

4.1.28 Iuv master crash if CS domain sends RANAP reset for a relocation failure call scenario

Problem report: NA04815585 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability Attached PRs: 68062ESPE04 Probability: Occasional in below error scenario


Description: Problem was that RNC could not manage RANAP reset indication from CN properly. When RNC started to release connection to the CN based on RANAP reset indication, RANAP protocol SW made an exception (IUV GPE at 000C.000BF9AB) resulting that it was possible that CN connections were lost also to correctly working CN which did not indicate RANAP reset. Problem occurs occasionally but probability is approximately 50% when RNC starts to release connection based on RANAP reset from CN. Solution / Workaround: Impact to Operator: Stability / possibly all connections for a CN released Impact to End user: Call drop

4.1.29 SRNC relocation not performed thoroughly

Problem report: NA04847143 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: 80631ESPE02, 23143ESPE07 Probability: Permanent Description: Radio Resource Manager entity in RNC selects non supported bit rate for the PS RABs during PS DCH reconfiguration procedures which is then rejected by the BTS resource manager entity in RNC. Call control then forces UE to Cell_FACH and deletes all the radio links as it does not expect the downgrade procedures to be rejected. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance/Call Completion Success Impact to End user: PS call is terminated due to radio failure.

4.1.30 M1002 counters not being updated correctly in case of HSDPA/HSUPA drop

Problem report: NA04856461 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: If user plane RLC makes reset error and state transition to Cell_FACH is


started to re-establish the RLC, counters indicating HSDPA drop due to reset error are not updated in KPIs. Solution / Workaround: No workaround. Impact to Operator: M1002 counters not being updated correctly in case of HSDPA/HSUPA drop. Impact to End user: No impact.

4.1.31 After RU20 upgrade PS R99 drop rate increase to 2~3% from 0.7%, and HSDPA RAB setup success rate decrease to 98.9% from 99.6%

Problem report: NA04833513 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Occasional Description: Incorrect PS Drop counters were incorrectly updated if RNC received Signalling Connection Release Indication from the UE during ongoing state change from Cell_PCH to Cell_FACH or Cell_FACH to Cell_DCH procedure. These cases, where UE sends Connection Release for fast dormancy to save battery when it detects inactivity should not be updated in KPIs as dropped call due to any reason. Solution / Workaround: None. Impact to Operator: Operation & Maintenance/Counters Impact to End user: No impact.

4.1.32 RNTI is not properly released on failed SRNC relocation scenario

Problem report: NA04827487 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: In case of incoming Inter-RNC Hard Handover, if reading of cell information fails then relocation is still continued by RRC PRB to incorrect BTS ID. When finally the relocation fails then RRC call control cannot handle the failure correctly and leaves hanging


RNTI reserved for the user. Solution / Workaround: No workaround. Impact to Operator: Increase of RRC setup failures due to RNC. Unnecessary hanging resources. Impact to End user: No direct impact since SRNC relocation should fail anyway if reading of cell information fails.

4.1.33 Call drops after ICSU switchover

Problem report: NA04825822 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04816935, NA04823272 Probability: Permanent Description: RNC ask BTS to reset signalling link by mistake during ICSU switchover. Solution / Workaround: No workaround. Impact to Operator: WBTS reset Iub signalling links. Impact to End user: Call drops when ICSU switchover.

4.1.34 System failure when WCEL is attempted to be unlocked

Problem report: NA04798949 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: Because IP QOS configuration synchronization failed, it leads that all IP resources are unavailable on RSMU and then IP calls cannot be created successfully. Solution / Workaround: 1. Restart the SP RSMU and wait it until SP-EX. 2. RSMU SWO. 3. Restart the new SP RSMU and wait it until SP-EX.


Impact to Operator: Call setup successful ratio is decreased. Impact to End user: IP calls cannot be created successfully.

4.1.35 NSN-Huawei Iur problems after RN5.0

Problem report: NA04802504 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: - Probability: Permanent Description: SRNC relocation fails quite often in case where the Huawei RNC acts as SRNC. If Target RNC receives RNSAP Radio Link Setup Request with TGPS information but no Activated Pattern Sequence Information indicating which CM pattern will be activated, then DRNC sends invalid APSI information to the BTS in the NBAP Radio Link Setup request. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call Completion Success Impact to End user: Dropped CS and PS calls.

4.1.36 Full outage after hard disk or switching fabric unit change

Problem report: NA04808440 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Capacity & Performance Attached PRs: 79533ESPE02 Probability: Occasional Description: Replacement of faulty WDU-01 was performed and after activation of the hard disk mirroring and OMU switchover caused RNC restart loop. The working disk WDU-1 had hardware problem. Many sectors in the working disk were damaged, so the data read from this disk was totally wrong. And because of two disks WDU-0 and WDU-1 were mirrored by each other. So the data in the WDU-0 was also wrong. POXLIB read error data and caused exception and RNC restarts. SCSI hardware alarm was set at this moment. Some check were added for the disk sector data, and informed to the user (by alarm 2690 and error log) that disk was damaged when POXLIB detected the hardware damaged disk.


Solution / Workaround: Problem solved by activating fallback SW package. RNC functionalities recovered fully. Impact to Operator: System out of use. Impact to End user: Lost calls. New calls are not possible.

4.1.37 SP OMU can't cancel alarm 2816 IP Routing configuration error

Problem report: NA04813398 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: Alarm 2816 will rise if the IP Routing configuration is missing or invalid on both WO and SP unit. Because of coding error, alarm 2816 can not be canceled by the system automatically. Solution / Workaround: Perform controlled Switchover between WO-OMU and SP-OMU. Impact to Operator: Alarm 2816 will not disappear on SP unit. Impact to End user: No impact.

4.1.38 NRM Process Exception (00020F12)

Problem report: NA04806226 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance Attached PRs: - Probability: Permanent Description: During user plane release scenario, UE has responded before the expiry of CFN. Since at RNC it has been assumed that UE has replied after expiry of CFN, RRC has initiated a new scenario for capacity request. This leads to process exception at TRM. Solution / Workaround: No workaround. Impact to Operator: Capacity and performance Impact to End user: No impact.


4.1.39 BRM hand process crash

Problem report: NA04819088 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Stability Attached PRs: NA04818175 Probability: Permanent Description: This problem was caused by failing BRM when updating overload control related information element in call allocation phase. Failure caused, because BRM was left stuck in a loop without recovery. Solution / Workaround: No workaround. Impact to Operator: Stability, occasional WBTS restarts Impact to End user: Occasional dropped call.

4.1.40 WBTS ID included in IuPS route object of measurement M568

Problem report: NA04819831 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: WBTS index is sometimes wrongly included in IuPS route object in xml files for measurement M568. WBTS identifier should be included for those ip routes are used in lub interface only, but is not valid. Operator can see it while opening and operating on Fault Management GUI. Solution / Workaround: No workaround. Impact to Operator: IP route id wasn’t mapped properly for WBTS. Impact to End user: No impact.

4.1.41 Some check boxes on OBRO are not controllable


Problem report: NA04842551 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Some check boxes were not modifiable in OMS Object Browser GUI. User cannot operate on OMS GUI in RNC and COCO object while modifying check boxes. There is no compatibility between RN5.0 MP2 AL and RN5.0 PP2.1 SW. Solution / Workaround: To temporary resolve this issue: two Application Launchers should be installed from OMS, one based on Java 1.5 version and other one on Java 1.6. Because AL is using Java version located in their directory so two of them should be installed on different location ie.: 1. AL based on 1.5 should be located ie.: c:\opt\Nokia 2. AL based on 1.6 should be located ie.: c:\opt1\Nokia Impact to Operator: User cannot operate on OMS GUI in RNC and COCO object while modifying check boxes. Impact to End user: No impact.

4.1.42 BTS alarm cannot be cancel by MML

Problem report: NA04842328 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: Alarm gate was blocked when WCEL blocking took place and meanwhile synchronization between RNW alarm system and centralized NE alarm system was lost due to which alarms forwarding to NE alarm system got blocked. Solution / Workaround: No workaround. Impact to Operator: Alarms cancellation is not successful. Impact to End user: No impact.

4.1.43 When CN releases tunnel too early, problem in RRC in updating the packet call ticket


Problem report: NA04847247 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: RNC does not update counters correctly in case Core Network releases the GTP tunnel for the PS RAB too early, before sending RANAP RAB Assignment Request to RNC to release the RAB. Correction will be made to update normal release counters if GTP tunnel has been released too early. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact.

4.1.44 UER provide process exception

Problem report: NA04819953 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: New feature/functionality, Call Completion Success Attached PRs: - Probability: Permanent Description: UER gives a process exception due to race condition with Handover controller (HC).Before HC receives the information regarding AMR establishment at the same moment it has triggered a channel type switch request for SRB and existing PS RBs without any AMR information in the request. UE specific radio resource manger is not able to handle request with incomplete data and gives exception while handling the request. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance:Call Completion Success Impact to End user: No impact.

4.1.45 Packet loss during RB reconfiguration



Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: RNC was not able to downgrade HS-PDSCH codes during code congestion because upgrade of HS-PDSCH codes was ongoing. This resulted in channel type switch nack because CTS was not waiting for next NRT scheduling period when HS-PDSCH codes could have been downgraded. Solution / Workaround: Keep parameter HSPDSCHMarginSF128 in its default value 8. Impact to Operator: Channel type switch from HSPA to DCH cannot be performed. Impact to End user: Channel type switch from HSPA to DCH cannot be performed.

4.1.46 In AMR+R99 multi call case RNC does not change PS data rate after AMR release

Problem report: NA04871150 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: 80383ESPE02 Probability: Permanent Description: Call Control in RNC incorrectly restricts PS NRT TFS during AMR Release in Multi-RAB situation which causes that later NRT DCH cannot be upgraded regardless of received capacity requests. Solution / Workaround: No workaround. Impact to Operator: Lower network utilization. Impact to End user: Minor impact on user data flow speed.

4.1.47 RRC process exception

Problem report: NA04856507 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: -


Probability: Permanent Description: If Call Control entity in RNC receives corrupted uplink RRC message from UE as a response to the UE Capability Enquiry procedure, it could not handle that response message correctly and instead of discarding the response, the call control entity goes to frozen state. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Alarms Impact to End user: No impact.

4.1.48 RRC access failures in RNC boundary

Problem report: NA04815748 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Counters Attached PRs: - Probability: Permanent Description: If UE makes cell reselection from another RNC area during ongoing Cell_FACH relocation and sends new Cell Update request to the Target RNC with new U-RNTI, Target RNC does not handle this as a response from UE even when UE indicated the new U-RNTI in the request. This causes incorrect counters indicating access failure to be updated even when the relocation was successful from UE point of view. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact.

4.1.49 RM3 error in SP unit update during mass DMPG restart

Problem report: NA04805865 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Stability, Unit restarts Attached PRs: 54945ESPE01, NA04808629,NA04907804 Probability: Permanent


Description: DSP resource management internal data was not consistent between WO- and SP-RSMUs. Problem occurred if DMPGs were restarted during high traffic. Solution / Workaround: No workaround. Impact to Operator: SP-RSMU redundancy is lost for a while. Impact to End user: No impact.

4.1.50 Shutdown of remaining cell in PWSM RU20 PP2.03 doesn't work properly

Problem report: NA04809656 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Cell Availability Attached PRs: NA04796722 Probability: Permanent Description: When remaining cells are configured as hspa0s and shutdown of remaining cells is set to true, shutdown of remaining cells is not fully completed which leads to situation that activation request is not sent to them when feature is disabled. Solution / Workaround: Avoid setting pwsm_shutdwn_rcel = yes, pwsm_hspa_type = hspa_0 for remaining cells. Impact to Operator: Remaining cells are available after feature is disabled and shutdown remaining cells are activated. Impact to End user: Remaining cells are available after feature is disabled and shutdown remaining cells are activated.

4.1.51 Increment of Admission Control failures after activation of feature RAN1686 HSPA 72 Users Per Cell

Problem report: NA04813141 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: NA04893497 Probability: Permanent Description: RNP parameter HSPDSCHMarginSF128 check failed in special case when HS-PDSCH codes were upgraded from 14 to 15, HSPA 72 users per cell feature is activated, 2 HS-SCCH codes were allocated in cell and there is only 1 HSPA call in cell.


Because HSPDSCHMarginSF128 check failed, it was possible that RNC initiated HS-PDSCH code upgrade so that no codes for RT calls were left as "margin". In case RNC received resource request for RT service during this kind of HS-PDSCH code upgrade in which there is no SF128 margin for RT left available, then this RT request will be rejected. RT request is rejected, because HS-PDSCH code downgrade cannot be started to release free DL channelization code for RT service when there is already HS-PDSCH code upgrade ongoing. Solution / Workaround: Disable 15th HS-PDSCH code usage (from parameter HSPDSCHCodeset) or Disable HSPA 72 users feature or Use only 1 HS-SCCH code in cell. Impact to Operator: KPI effect in low utilized cells. Impact to End user: Occasional RT call establishment failure.

4.1.52 RNC does not receive RadioBearerReleaseComplete message.

Problem report: NA04814265 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Capacity & Performance, RAB release KPI is dropped Attached PRs: NA04872330 Probability: Permanent Description: RRC was not sending the OLPC parameters of SL to Transport resource Manager (TRM) during AMR RAB Release procedure. Solution / Workaround: No workaround. Impact to Operator: Call Completion success ratio KPI is dropped. Impact to End user: Call drop.

4.1.53 Some UEs are failing in MOCN relocation

Problem report: NA04776944 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, RRC Success


Attached PRs: - Probability: Permanent Description: RNC does not send Selected PLMN ID during SRNS relocation to the UE during UE not involved relocation in MOCN configuration. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, RRC Success Impact to End user: Dropped calls.

4.1.54 HMS upgrade failed on some TBUF units

Problem report: NA04820199 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Operation & Maintenance, HMS upgrade Attached PRs: - Probability: Permanent Description: Low priority HMS upgrade is interrupted by high priority family when sending HMS message which cause the HMS upgrade failed. Solution / Workaround: Do OMU restart and make OMU switchover. Impact to Operator: HMS upgrade fails. Impact to End user: No impact.

4.1.55 Re-establishment not successful after incoming ISHO from 2G causing AMR call drop

Problem report: NA04792536 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: NA04819767, NA04880851 Probability: Permanent Description: Re-establishment did not work always correctly after 2G to 3G ISHO, because RB mappings were not ok in all cases. Solution / Workaround: No workaround.


Impact to Operator: Capacity & Performance, Call completion success Impact to End user: Call drop.

4.1.56 WCEL parameter modification problem

Problem report: NA04817446 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Operator can't configure multiple WCELs(with DRRC enabled/WIthout DRRC enabled) with the different power parameters (PtxTarget,PtxOffset,PrxTarget,PrxOffset) value in the same sector of BTS. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact.

4.1.57 COCO detach during fallback copy making and COCO attach then COCO status is not WO

Problem report: NA04851223 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Capacity & Performance, Cell availability Attached PRs: - Probability: Permanent Description: RNC application software does not check fallback copying operation while performing CoCo/IPNB operations. Solution / Workaround: No workaround. Impact to Operator: BTS might not come up properly. Impact to End user: UEs not able to connect cells under affected BTSs.


4.1.58 Unreasonable high value for M802C17 (AVE_RRC_CONN_MODE_USERS) and M802C18 (MAX_RRC_CONN_MODE_USERS)

Problem report: NA04835760 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics Attached PRs: - Probability: Permanent Description: If improper measurement data is received from data collectors and considered in statistical calculation then it corrupts the overall KPI data. Solution / Workaround: No workaround. Impact to Operator: Erroneous KPI data is visible to the operator. Impact to End user: No impact.

4.1.59 HSDPA cannot be enabled in VCEL object

Problem report: NA04841662 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: HSDPA cannot be enabled in VCEL object. RNW Configuration Manager was wrongly checking License state of I-BTS sharing for parameter VCEL-HSDPA-FMCGIdentifier. Solution / Workaround: No workaround. Impact to Operator: Operator is not able to configure parameter VCEL-HSDPA-FMCGIdentifier. Impact to End user: No impact.

4.1.60 COCO modification failed with CM plan



Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: NA04844699 Probability: Permanent Description: In case of any critical parameter modification in COCO object (i.e; the parameter for which the modification requires disconnection and re-connection of BTS-COCO association) then failure response is returned to operator. Solution / Workaround: No workaround. Impact to Operator: Plan activation fails. Impact to End user: Un-availability of cells on impacted BTS.

4.1.61 M1006C188 RRC_RE_EST_FAIL_NOREPLY_RT counter not incrementing

Problem report: NA04855636 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters, Missing counter update Attached PRs: - Probability: Permanent Description: The number of failed RRC connection re-establishments due to the UE not replying to an RRC: CELL UPDATE CONFIRM message sent by the RNC, for UEs with at least one RT RAB. The M1006C188 RRC_RE_EST_FAIL_NOREPLY_RT counter was not incremented as expected. Solution / Workaround: No workaround. Impact to Operator: The M1006C188 RRC_RE_EST_FAIL_NOREPLY_RT counter was not incremented as expected. Impact to End user: No impact.

4.1.62 Several DSP severe errors increasing call drops



Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: Drop counter calculation failed and DSP severe error (error code 70680033) was reported when double RLC reset was performed. The severe error was unnecessary. Solution / Workaround: No workaround. Impact to Operator: Call drop counter increases. Impact to End user: Call drop.

4.1.63 CellUpdate over Iur after radio link failure does not update RAB active drops counter

Problem report: NA04819974 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Operation & Maintenance, Counters Attached PRs: - Probability: Permanent Description: If T314 is greater than 0 and UE drops to Cell_FACH due to loosing radio connection and initiates Cell Update from DRNC cell then SRNC should send RRC Connection Release to the UE over IUR and update drop due to radio failure counters in KPIs which was not happening. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact.

4.1.64 UER sends uninitialized information to RRC

Problem report: NA04854040 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent


Description: Radio resource management entity in RNC sends uninitialized data over the interface to other entities in RNC during branch replacement failure retry scenario causing the other entity to cause a memory protection error. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance/Call completion success Impact to End user: No impact.

4.1.65 Packet loss during SRNS relocation procedure

Problem report: NA04844655 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: During Inter-RNC SRNS relocation procedure, SRNC RRC stops RLC in the UTRAN during data forwarding phase due to which RLC does not send L2 acknowledgements to the UE and discard the UL received PDUs. These packets are eventually lost since after SRNS relocation UE re-establishes its RLC. Solution / Workaround: No workaround. Impact to Operator: Data throughput. Impact to End user: No impact.

4.1.66 Many sites down during the upgrade to RU20

Problem report: NA04804218 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Capacity & Performance, Cell availability Attached PRs: - Probability: Permanent Description: When the VCCep is tried to be overwritten, the device driver for the AAF HW block returns an error code indicating already existing resource to the control software (JUNGLEGX) and JUNGLE then does a rollback to the resources configured to the network processor and error code is returned.


Solution / Workaround: Restart spare NPS1P and after the NPS1P is in SP-EX do a switchover. For NPS1 units NPS1 restart is required. Impact to Operator: CoCo creation fails for the BTS. Impact to End user: No calls are possible on the sites which are using the faulty VCCep.

4.1.67 TCP/IP ATM interface can not be deleted after upgrading RNC to RU20 MP2 PP2.03

Problem report: NA04824927 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04821559 Probability: Permanent Description: The process which was responsible for the maintenance of ATM logical resource was short of judgment conditions for the untagged TPI(interface/vp/vc) of IPOA when IPOA was deleted via the command ZQMD,RNC will produce the error" Inconsistent parameters", which cause the corresponding TPI will be hanging in system, furthermore this will block customer upgrade plan. Solution / Workaround: Changing the USAGE item of VCLTP from IPOAM to FREE in database via the commands. Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact.

4.1.68 Increase in NRT compressed Mode triggers in RU20

Problem report: NA04827041 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Capacity & Performance, Operation & Maintenance, Handover success, Counters Attached PRs: - Probability: Permanent Description: In RU10 AMR release was not possible during compressed mode and ISHO measurement. AMR release required CM stopping and after RAB modification restart need for CM was checked and if PS NRT ISHO was disabled, CM was not restarted. In RU20 AMR release can be made during CM and in such situation Handover control does not


check if CM and ISHO are supported for remaining RBs. This will cause unnecessary ISHO attempt and M1010 counter updating. Solution / Workaround: No workaround. Impact to Operator: No unnecessary handovers from 3G to 2G. Impact to End user: No unnecessary handovers from 3G to 2G.

4.1.69 RAB_ACT_FAIL_PS_INTER_IU incorrectly updated

Problem report: NA04815463 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Counters Attached PRs: - Probability: Permanent Description: RRCPRB updates incorrect counters indicating PS Drop due to Iu even if the call release is triggered due to inactivity in Cell_FACH and Cell_PCH not supported in the NW. This release due to inactivity should not be counted as drop in KPIs. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact.

4.1.70 DMPG restarted due to no response to AAL5 CHANNEL SUPERVISION

Problem report: NA04821529 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability, Unit restart Attached PRs: - Probability: Permanent Description: Due to a DSP HW bug in DMA subsystem, present up to silicon version 2.1, it may happen that DSP bus gets stalled and CPM crashes. Solution / Workaround: DMA monitor introduced, and a SW recovery of DSP has been introduced. Impact to Operator: DSP SW reset.


Impact to End user: Call drop.

4.1.71 Increase seen in Alarm 1078 Process exception

Problem report: NA04820207 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: NA04787623 Probability: Permanent Description: RRC makes process exception if there is Cell Update received from UE during ongoing Security Mode procedure towards one CN domain if there has been executed also another Security procedure towards another CN before this. RRCPRB makes process exception when it tries to send RANAP Security Mode Reject to CN on receiving the Cell Update from UE. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance: Alarms Impact to End user: No impact.

4.1.72 Degradation in IFHO (PS) KPI

Problem report: NA04848568 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: There has been two problems identified which need correction in the RRC call control. 1. Handover Control in SRNC triggers Intra-RNC IFHO same time when the PS NRT has been detected inactive and state transition to Cell_FACH triggered. On receiving Intra-RNC IFHO request, RRC call control entity goes in a hanging state where it cannot react to any new procedures until the time supervision releases the hanging situation. After this, the call is dropped to Cell_FACH, all radio links deleted and IFHO is rejected. Call is re-established after Cell Update has been received from the UE.


2. UE sends Signalling Connection Release Indication due to fast dormancy and then does not reply to the IFHO command at all. In case 1, RNC should continue with the state transition to Cell_FACH procedure if the PS RB has been passive already. In case 2, if Signalling Connection Release Indication is received, RNC should not mark the counter for IFHO failure as radio connection lost with UE. Solution / Workaround: No workaround. Impact to Operator: Degradation in IFHO (PS) counters. Impact to End user: No impact.

4.1.73 HS Failure increase since PP2.11 on small number of sites

Problem report: NA04833955 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance Attached PRs: NA04885736 Probability: Permanent Description: Congestion direction was indicated incorrectly in case of transport congestion for the HSDPA UL return channel and that's why retry with lower bit rate was not done and HSDPA allocation failed. Solution / Workaround: No workaround. Impact to Operator: HS Failure increase in case of transport congestion. Impact to End user: HS Failure increase in case of transport congestion.

4.1.74 SIR error causes PS DCH bit rate downgrade during Compressed Mode after Iur HHO leading synchronization loss

Problem report: NA04819106 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: SIR error causes PS DCH bit rate downgrade during Compressed Mode after


Iur HHO. Synchronization is lost after downgrade. When R99 reconfiguration from HSDPA (A-DCH) caused by SIR error with CM after Iur HO, PS DCH rate downgrade and PS call sync-loss occurred. Transport format selection fails in some HHO scenarios having CM involved. Solution / Workaround: No workaround. Impact to Operator: Increased dropped call count. Impact to End user: Dropped call.

4.1.75 Support for 72 HSPA users in a cell is not working simultaneously with HSUPA peak rate enabled in cell

Problem report: NA04815110 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: NA04832327 Probability: Permanent Description: Support for 72 HSPA users per cell was not possible simultaneously with HSUPA peak rate enabled in a cell. Problem existed because current power offsets were optimized for high bit data rates (HSUPA peak rates) resulting that power offsets were too high for low bit rates (low bit rates are used with large amount of HSUPA users). In addition to problem in supporting 72 HSPA users in a cell, also it is possible the throughput was degraded in cell edges. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance / Call setup success - 72 HSPA users per cell not possible simultaneously with HSUPA peak rate enabled in cell. Impact to End user: No impact.

4.1.76 Hanging RRC-D hand

Problem report: NA04850438 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent


Description: After failed security procedure due to radio link failure and no answer from UE, RNC could not continue the resource release procedure correctly. All the resources should be released on receiving Iu Release Command and send RRC Connection Release to the UE after failed security procedure due to no response from UE. Solution / Workaround: No workaround. Impact to Operator: Hanging resources. Impact to End user: No impact.

4.1.77 All RLs are released when deactivating PS session from AMR+PS 0kbps during Compressed Mode

Problem report: NA04831046 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: RNC sends wrong Activation Time for Compressed Mode reconfiguration if Radio Bearer Release procedure is executed on UE during ongoing Compressed Mode when the PS RB is passive. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance/Call completion success Impact to End user: AMR is released when deactivating PS session from AMR+PS 0kbps.

4.1.78 IP upload is failing

Problem report: NA04830560 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: After IP plan upload is successful for first time, all following IP plan uploads fail.


Solution / Workaround: No workaround. Impact to Operator: IP plan upload fails sometime. Impact to End user: No impact.

4.1.79 DSP Supervision Failure due to Fatal Error 80000003 causing a DSP reset

Problem report: NA04792883 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability, Unit Restarts Attached PRs: NA04810449 , NA04854833 Probability: One Occurrence Description: DSP Supervision Failure with Fatal Error 80000003 occurs when OSE is passed an Illegal PID (PID of a process which does not exist). Solution / Workaround: No workaround. Impact to Operator: Operator would see DSP Fatal Error. Calls will be dropped due to DSP reset. Impact to End user: Call drops due to DSP resets.

4.1.80 WCEL states incorrectly reported in NetAct RU20

Problem report: NA04825798 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04479507, NA04865588 Probability: Permanent Description: Problem occurred when customer made roll out from RU10 to RU20. Situation was hard to investigate because when trace logging was ON on OMS WCELL lock/unlock events worked fine and were correctly reported to NetAct. Solution / Workaround: Turn on trace logging on OMS. Impact to Operator: WCELL states as lock/unlock weren’t reported to NetAct and operator didn’t see any changes.


Impact to End user: No impact.

4.1.81 Power control fails if FDPCH used

Problem report: NA04820715 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Operation & Maintenance Attached PRs: 67053ESPE04 Probability: Permanent Description: Problem was that UEs in same FDPCH (Fractional Dedicated Physical Channel) code were not configured with correct timing offsets resulting that UEs were getting incorrect TPC (Transmit Power Control) command. Problem can cause power control not to work as it should and can be noticed also by CPC_STATUS_ERROR_IND_MSG in the BTS UDP-log. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance Impact to End user: No impact.

4.1.82 PS throughput is not restored while deactivating compressed mode

Problem report: NA04783214 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Occasional Description: AMR and Rel-99 PS call is established. Now compressed mode is activated and AMR call released which declined the throughput. When compressed mode is de-activated then throughput is not being re-stored. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance Impact to End user: Data throughput.


4.1.83 Incorrect values in M553 counters

Problem report: NA04731762 Exists in: RN4.0 Correction Target: RN4.0 CD2.3, RN5.0 MP3 Severity: C - Minor Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: Some counters of M553 underflow with a huge value after running the M553 statistic on the NCI for a long time with traffic. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance: Statistics / counters Impact to End user: No impact.

4.1.84 Problem activating/deactivating Power Saving Mode for BTS, HSPA reconfiguration failed and cells remains in BL(I) after lock/unlock

Problem report: NA04799820 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Cell availability Attached PRs: - Probability: Permanent Description: Problem was that Power Saving Mode HSPA reconfiguration implementation was missing from situation where cell shutdown and HSPA reconfiguration was executed and Power Saving Mode for BTS feature was disabled. RNC tried to configure remaining and non-remaining cells at the same time which leaded to situation where HSPA were not possible in non-remaining cells. Solution / Workaround: To avoid switching feature off when cells are shutdown and HSPA reconfigured. Impact to Operator: Capacity & Performance, Cell availability Impact to End user: Calls not possible.


4.1.85 70245 ILLEGAL INTERNAL USAGE OF EXTERNAL ALARM NOTIFICATION FORMAT

Problem report: NA04797179 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04792361, NA04784855, NA04800668, NA04810360, NA04814946, NA04806099 Probability: Permanent Description: Alarm Processor rejected alarms with raising an alarm 70245 when the external time of the original alarm was greater as its internal (Alarm System) one. RNC cannot guarantee time synchronization between NEs. So the system time on RNC NE can be greater than on OMS. Then the above mentioned restriction doesn't allow accepting this alarm. Solution / Workaround: No workaround. Impact to Operator: No alarm 70245 instead of the original alarm. Impact to End user: No impact.

4.1.86 UL temporary lowered bitrate cannot be increased to 384 if BitrateSetPSNRT is ON

Problem report: NA04791474 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: User Plane Quality, HSDPA UL data rate Attached PRs: 55505ESPE01 Probability: Permanent Description: UL TMBR (Temporary lowered) bitrate in cell cannot be increased to 384 in case it has been decreased from its initial value 384. This happens in case RNP parameter BitRateSetPSNRT is ON. This affects HSDPA UL return channel bitrate. Solution / Workaround: Set BitrateSetPSNRT OFF. Impact to Operator: 384 cannot be used as UL data rate in HSDPA calls. Impact to End user: 384 cannot be used as UL data rate in HSDPA calls.


4.1.87 Reduced downlink throughput during SCC between DC-HSDPA&16QAM cells

Problem report: NA04811612 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: User Plane Quality Attached PRs: - Probability: Permanent Description: During SCC between DC-HSDPA 16QAM cell pairs, when cells from both DC cell pairs are in the active set, downlink throughput is consistently observed to reduce to below 600 kbps and will not increase again even under good RF conditions. When HSPDSCH and E-DCH power control parameters were updated after branch addition/deletion "HS-DSCH TB size table" IE was not sent in PhysicalChannelReconfiguration. In this case it should be sent because "Downlink HS-PDSCH information" IE was sent. Because it was not sent the UE started using bit-aligned table and as the network was using octet-aligned table, this led to wrong HS-SCCH decoding and therefore a drop in throughput. Solution / Workaround: No workaround. Impact to Operator: User Plane Quality Impact to End user: Reduced throughput.

4.1.88 WBTS not showing alarms when it is off air

Problem report: NA04814089 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability, BTS availability Attached PRs: - Probability: Permanent Description: Cell service creations failed because leg control in RSMU had invalid state information for DMPG-0 and DMPG-1. Invalid state information happened during active MXU restart (when tributary units behind MXU are also restarted and also active unit RSMU faulty switchover happened). Invalid state information occurs when recovery message re_unit_restart_imminent_s is lost or when Unit handling program block sends message to hand in SP unit (and this SP just changed to WO, so message is lost). Solution / Workaround: Restart every DMPG units that have invalid state information in leg control. Invalid state information can be seen from LGUTIL service terminal command IU (state should be empty when unit is OK).


Impact to Operator: Stability, BTS availability Impact to End user: No impact.

4.1.89 LU Limiter too strict for busy RNCs

Problem report: NA04802673 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Capacity & Performance, RRC success Attached PRs: NA04857446 Probability: Occasional Description: RRBPRB has internal limit for maximum number of ongoing Location Update (LU) requests at RNC level, to ensure that RNC and CS core network are not overloaded if UEs under the radio network are generating large bursts of LU requests. If this limit is exceeded, RRBPRB rejects RRC connection requests that contain registration-type establish cause values and asks UE to retry a few seconds later. The default limit seems to be too low for some higher capacity customer RNCs and it causes RRC connection request rejections even though the RNC and CN would be able to handle the requests. Solution / Workaround: As workaround, the internal limit can be adjusted by setting PRFILE parameter 7,246 to higher value, e.g. 2000(dec). Impact to Operator: Counter M1006C204 is increased whenever RRBPRB rejects RRC connection request. Impact to End user: UE might not be able to receive a call during the first few seconds after changing location area if its Automatic Location Update happens to get delayed by this LU limiter mechanism.

4.1.90 Inter Frequency H/O fails then UE does not receive Physical Channel Reconfiguration

Problem report: NA04760626 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Handover Success Attached PRs: NA04818311, NA04829225 Probability: Permanent Description: When compressed mode is configured to allow UE to perform neighboring cell measurements, transport format set is limited to lower bit rates only. Then, when HHO takes place and HHO configuration for the target cell is done, RNC incorrectly starts using HHO


parameters also in the source cell if bi-casting is used. This causes too much data sent to WBTS which cannot transfer all to UE. Physical Channel Reconfiguration gets also dropped in such situation. Solution / Workaround: No workaround. Impact to Operator: Increased dropped call count, increased failed HHO count. Impact to End user: Dropped call.

4.1.91 Dual Cell HSDPA feature can't be activated without 15 HS-PDSCH codes

Problem report: NA04808308 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: System required incorrectly that 15 HS-PDSCH codes must be used in order to enable Dual Cell HSDPA feature in a cell pair. The description of the WCEL parameter DCellHSDAPEnabled incorrectly/unclearly required in related parameters, that HSDPA 15 Codes feature must be enabled with the WCEL parameter HSPDSCHCodeSet to enable the dual cell HSDPA feature. However, the activation of the Dual Cell HSDPA feature should not require any specific number of HS-PDSCH codes but dual cell operation should be possible with any configured number of HS-PDSCH codes. Solution / Workaround: No workaround. Impact to Operator: Effects to RAN1906 Dual Cell HSDPA 42 Mbps activation. Impact to End user: No impact.

4.1.92 Spare RSMU restarted during DSP pool reconfiguration

Problem report: NA04815579 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability, Unit restarts Attached PRs: - Probability: Permanent


Description: Spare RSMU restarts when DSP state is changed to TE state during service pool reconfiguration. DSP was moved to TE state manually in order to release it from ongoing calls. RM3 code performed operations in wrong order when DSP which was under pool reconfiguration was changed to TE state. This lead to RM3 capacity counter corruption and SP RSMU reset. Solution / Workaround: No workaround. Impact to Operator: RSMU redundancy is lost for the time SP RSMU restarts. Impact to End user: No impact.

4.1.93 HS-DSCH setup failure due to RNC for interactive

Problem report: NA04821108 Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: There is a general problem related to PRFILE reading in BRM. This specific case is related to PRFILE parameter (007:0298 RN40_MAINT_028). After changing it from 0 to 1 (minimum bitrate allocation through PBS is enabled). M1002C413 (HS-DSCH SETUP FAILURE DUE TO RNC FOR INTERA) counters started increasing heavily. This was due to inconsistency in bitrate determination between branches in different BTSs (BRMs located in different ICSU) because of the PRFILE reading problem. The timer used for periodic PRFILE reading had been lost at some ICSU and thus new PRFILE values were not taken into use. The fault situation is rare, related to switchovers under special circumstances. Solution / Workaround: Timer message can be sent to BRMPRB master in problematic ICSU, the timer will trigger periodic PRFILE reading. Impact to Operator: Capacity & Performance: Call setup success Impact to End user: No impact.

4.1.94 Cell BTS manager Block/Unblock causes sleeping cells

Problem report: NA04836303 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: -


Probability: Permanent Description: When cells are in working state, BTS initiates Block/Unblock of cells continuously. During the handling of block scenario, if Recovery Program Block receives unblocking of same cell, the block scenario is interrupted. But the queuing of message doesn't take place and Recovery Program Block starts doing operations to same cell at the same time which is not acceptable. Solution / Workaround: No workaround. Impact to Operator: It will have impact on availability of cells. Impact to End user: It will have impact on availability of cells.

4.1.95 PS NRT DCH downgrade failure due to Iub AAL2 congestion causes pre-emption failure

Problem report: NA04818197 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: When AMR setup faces Connection Admission Control (CAC ) congestion in UL and pre-emption is triggered to downgrade the uplink bit rate of NRT DCH user, the downgrade procedure can fail due to UL CAC congestion if Enhanced CAC feature is not enabled in the BTS. In this case RNC should drop the NRT user to DCH 0/0 or to FACH, but instead the pre-emption request is prematurely nacked to base station resource manager and this results in pre-emption failure and AMR setup failure. Solution / Workaround: Enable Enchanced CAC feature in BTS (which is the default). Impact to Operator: AMR success rate increase. Impact to End user: AMR call setup succeeds.

4.1.96 RAN930 PS RAB Reconfiguiration doesn't work properly when HSPApeakratelimitmax is set to 1 (Limitation is active)

Problem report: NA04813788 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: New feature/functionality, Call Completion Success


Attached PRs: 78708ESPE02 Probability: Permanent Description: 1.Channel type switch for SRB and/orAMR or, 2.EDCH-TTI reconfiguration RNC modifies the MAC-D PDU size of the existing PS-NRT RBs for which only EDCH-TTI modification was triggered which is not supported by the BTS and causes failure. Correction will be made to RNC to use the existing MAC-D PDU values for PS-NRT RBs during the reconfiguration procedures where only EDCH-TTI switch is being done for PS-NRT RBs. Solution / Workaround: No workaround. Impact to Operator: New Features/ Functionality:Call Completion Success Impact to End user: No impact.

4.1.97 No PM data M568 (IP base route counters) after NPGEP-0 switchover

Problem report: NA04827346 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics/counters Attached PRs: NA04814987 Probability: Permanent Description: When creating M568 measurement (IP route measurement), a timer would be created in WO-NPGEP unit. After NPGEP switch-over, the timer in the SP-NPGEP will be deleted after two hours. After NPGEP switch-over again, there is no timer in the WO-NPGEP. Solution / Workaround: Stop the measurement and then start the measurement again. The measurement would work on the new WO-NPGEP unit. Impact to Operator: The problem will impact IP based route measurement. Impact to End user: No impact.

4.1.98 RU20 PP2.01: ALARM: HSDPA CONFIGURATION FAILED: RNC INTERNAL ERROR



Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Occasional Description: Problem is possible after physical shared channel reconfiguration failed due to parallel transaction not allowed and RNC started re-try procedure with internal timer. When cell was blocked during this re-try procedure, RNC did not check the cell state but initiated PSCR procedure towards blocked cell. This was noticed in NBAP interface resulting that PSCR procedure was nacked and alarm raised for it. Alarm was cancelled after the next successful HSDPA configuration to cell so this is unnecessary alarm. Solution / Workaround: NA Impact to Operator: Operation & Maintenance / Alarms Impact to End user: No impact

4.1.99 CS RAB drop increase after HSPA over Iur activation

Problem report: NA04829673 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: Wrong L2 configuration for Signaling Link in Iur. Transport resource manager was sending overbooking parameter for signalling link at Iur interface to user plane. Overbooking parameters which are related to flow control is only needed for PS NRT. This problem was caused because there is different meaning of overbooking for TRM and user plane. Because of this misunderstanding TRM wrongly send this parameter to user plane. Solution / Workaround: No workaround. Impact to Operator: Increase in dropped CS call statistics. Impact to End user: Dropped CS call.

4.1.100 M1010C30 IS_HHO_ATT_CPICH_RSCP_RT counted on WBTS-0 after RAN1758: Multiple BSIC Identification activation



Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: After RAN1758 Multiple BSIC Identification feature was enabled, some misalignment in terms of number of handover attempts in family counters like M1010C30 IS_HHO_ATT_CPICH_RSCP_RT or M1010C34 IS_HHO_ATT_CPICH_EcNo_RT was observed. Some of the Handover attempts were missing in the counter and all the missing ATT disappeared from WCEL/WBTS were counted in the WBTS-1 Anchored WBTS. The reason for this behaviour is that the GSM measurement object information was not set for the message to be sent for ISHO. Without that, the counter data information was not getting filled properly. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Statistics/counters Impact to End user: No impact.

4.1.101 Dual Cell cannot be setup on certain WBTS

Problem report: NA04800349 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04846676 Probability: Permanent Description: RAKTOR should never send not defined (0xFF) value for Multi Cell Capability to RNW database or BRM, if there is valid value for the parameter in the RNW database. Not defined (0xFF) values are used to indicate not used field in Resource status indication message from NBAP. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact.

4.1.102 HSPA traffic allocation problem after pool optimization



Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04813693 Probability: Permanent Description: During DMPG restart "cell home" services from restarted DMPGs were lost. Cell home service is used between base station resource management and DSP resource management to concentrate HSPA users from same cell to same DSP. Now during DMPG restart, cell home was released from DSP resource management, but base station resource management did not know about that, and continued to use that cell home. DSP resource management rejected all call setups, which were using non-existent cell home. Solution / Workaround: Instead of DMPG restart use cell or RNC restart to complete long lasting DSP service pool reconfiguration. Impact to Operator: All HSPA call setups from certain cell(s) fail. Impact to End user: HSPA call setup fails, and DCH call will be established instead.

4.1.103 DMCU automatic Unit Restarts in overload conditions (a submodule of CDSP-DH goes into SW recovery)

Problem report: NA04739049 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, alarm Attached PRs: - Probability: Occasional Description: Under heavy traffic condition it may happen that a CDSP-DH submodule goes into a SW recovery. Solution / Workaround: No workaround. Impact to Operator: A DMCU on CDSP-DH goes into SW recovery. Capacity & Performance, Data Throughput. Impact to End user: Running calls are dropped.

4.1.104 CU from UE during ongoing RAB setup in Cell_FACH is not handled correctly



Severity: C - Minor Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If there is ongoing PS RAB Setup procedure in Cell_FACH and at the same time UE moves to new Cell and makes cell reselection, NW could not handle the RAB setup procedure correctly. Solution / Workaround: Activating DRA would help the PS RAB Setup in Cell_FACH. Impact to Operator: KPIs, PS Call Setup Impact to End user: PS call does not start.

4.1.105 When cell_FACH to cell_DCH transition is tried for PS NRT on HSPA, HSDPA is allocated

Problem report: 20790ESPE07 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: When cell_FACH to cell_DCH transition is tried for PS NRT on HSPA for a UE capable of HSPA, HSDPA is allocated. Solution / Workaround: No workaround. Impact to Operator: No impact. Impact to End user: Data rate in uplink is reduced for a brief time.

4.1.106 Domain-specific access control (DSAC) restrictions are not working

Problem report: NA04822318 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Application of Cell access class restrictions Attached PRs: -


Probability: Permanent Description: Domain-specific access control (DSAC) restrictions won't get into use even thought the operator had requested the restrictions. RRA does not send rnar_sib3_update_request_ack_s correctly during RNAR, DSAC restriction. RRA-CMA maintains 6 sec gap between two consecutive system information updates to Node-B. The requests coming during this period would be queued up. The queuing mechanism was found faulty. Solution / Workaround: Cell block/unblock works most of the times. If not cell lock and unlock is required. Impact to Operator: It may happen that the DSAC restrictions won't get into use even thought the operator had requested the restrictions. Impact to End user: UEs may not identify the DSAC restrictions that the operator wants to put on them.

4.1.107 Random ICSU load (100%) peak since RU20 PP2.1 upgrade

Problem report: NA04827879 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: NA04833172, NA04833309, NA04827879, NA04834386, NA04834371 Probability: Permanent Description: An increase in ICSU average load with 100% load peaks is observed when soft handover branch addition fails due to congestion. This is caused by the UE radio resource manager (UER) in the RNC. It should start PS-NRT downgrade task to cell minimum bit rates after congestion is observed, but the task fails and creates an infinite branch addition request loop that causes the ICSU load peak. Solution / Workaround: No workaround. Impact to Operator: Operator observes an increase and 100% peaks in ICSU load. Impact to End user: End user may observe PS-NRT call drop in some cases.

4.1.108 JAFFIS consumed CPU load and hanging hand was observed



Customer Impact: Stability, Switchover Attached PRs: - Probability: Permanent Description: FTP cause high CPU load and always one FTP process hanged even no FTP service used. When TCP socket connection have error event, FTP select it, but never handle it and in this way one dead loop appear. In the other side, the client for this FTP session is already released, but FTP has not active the TCP probe feature in stack. So it never releases the connection and repeats the dead loop, in this way high CPU load is produced. Solution / Workaround: No workaround. Impact to Operator: Stability/Switchover Impact to End user: No impact.

4.1.109 After command calendar triggered fallback, system did a full restart

Problem report: NA04823816 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability, Unit restarts, Network element restarts Attached PRs: NA04829303 Probability: Permanent Description: Message request for file dumping failed during fallback and file dumping was prevented. But alarm system which request for file dumping did not wait a while when send another time file dumping request. This caused OMU CPU load continuously high during fallback and PRB priority lower than ULAPRB (request for file dumping) and FEDSER (file dumping service provider) cannot get time to execute when SP-OMU is in TE or SE (or SP-RE RP0/1/2) state. Solution / Workaround: No workaround. Impact to Operator: If SP-OMU is in TE or SE (or SP-RE RP0/1/2) state, this error causes WO-OMU CPU overload and system restart happens. Else, this error causes WO-OMU to write too many error logs leading computer log buffer on WO-OMU to get full and message burst out. Impact to End user: In case system restart, it causes service break for RNC in question.

4.1.110 Cable configured with “no direction” remains after SW upgrade



Exists in: RN4.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Cables configured with "no direction" cannot be deleted using the ZWFT commands. Cable connection is inherited in release SW upgrade from RN2.2 or older to RN3.0 or newer. So some cables remained configured with "no direction". These "no direction" cables cannot be deleted after upgrade in RN4.0 or RN5.0. This situation occurs very rarely. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact.

4.1.111 HSDPA will drop to R99 and won't come back to HSDPA after RU20 upgrade

Problem report: NA04817019 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: NA04818153, NA04827907 Probability: Permanent Description: When the RABs are on DCH/HSDPA and when throughput indications are not received from Layer 2 in the RNC, the trigger from DCH/HSDPA to HSPA is not allowed by the UE radio resource manager (UER) in the RNC. Solution / Workaround: No workaround. Impact to Operator: Decreased throughput and traffic volume. Impact to End user: Decreased throughput with DCH channel.

4.1.112 Two ADJG objects pointing to same target WCEL exist in the same cell

Problem report: NA04784152 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP3 Severity: C - Minor


Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04823320, NA04698108, NA04853319 Probability: Permanent Description: RNW Configuration Manager was wrongly skipping consistency checking when there are more than 32 WCEL's in RNC. Solution / Workaround: No workaround. Impact to Operator: Operator ends up creating duplicate Adjacencies pointing to same target cell. Impact to End user: No impact.

4.1.113 Traffic Volume Measurement failure sent by UE occasionally in FDPCH setup

Problem report: NA04815323 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: C - Minor Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Occasional Description: Problem seen with one specific UE in case of FDPCH (Fractional Dedicated Physical Channel) when RRC connection is made in Cell_FACH and TVM (Traffic Volume Measurement) for Cell_FACH is sent to UE during CCH to DCH transition then UE rejects the TVM. Solution / Workaround: CCH Setup can be disabled. Impact to Operator: KPIs, UE may not enter Cell_DCH from Cell_FACH occasionally. Impact to End user: UE may not enter Cell_DCH from Cell_FACH occasionally.

4.1.114 IUETOR Actor Exception causes NPGEP restart

Problem report: NA04802769 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability, unit restart Attached PRs: NA04814463, NA04820606, NA04822374, NA04833520, NA0484060, NA04900780, NA049056684


Probability: Permanent Description: WO-NPGEP restart because of SW module exception. Solution / Workaround: No workaround. Impact to Operator: Stability/Unit restart Impact to End user: No impact.

4.1.115 Degrading in HSUPA traffic volume after MP2

Problem report: NA04807196 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success, Data Throughput Attached PRs: - Probability: Permanent Description: When PS-NRT user plane is created and the signaling radio bearer (SRB) is going to be mapped on HSPA or HSUPA, HSPA allocation is mandatory for all active set cells. Now when any of the BTSs in the active set face HSUPA resource congestion and HSPA allocation is not possible, the UE radio resource manager in the RNC decides to map the PS-NRT down to HSDPA. This has a negative effect on HSUPA allocations and causes the degrading in HSUPA traffic volume. The correct behavior in this case would be to retry the PS-NRT on HSPA and map the SRB on DCH, which would not require all active set cells to be mapped on HSPA anymore. Only if also this configuration faces HSUPA resource congestion for the minimum E-DCH active set cells, the PS-NRT can be mapped down to HSDPA. Solution / Workaround: No workaround. Impact to Operator: Degrading in HSUPA allocations and HSUPA traffic volumes. Impact to End user: Only HSDPA is granted for the user instead of HSPA.

4.1.116 RRC tries DC-HSDPA with secondary cell for REL6 and REL7 UEs

Problem report: NA04803353 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: New feature/functionality, Code optimization Attached PRs: NA04823486 Probability: Permanent


Description: RRC tries DC-HSDPA with secondary cell for REL6 and REL7 UE's. RRC reads UE capability and interpret wrongly to try DC-HSDPA with secondary cell for REL6 and REL7 UE's also. Solution / Workaround: No workaround. Impact to Operator: New feature/functionality: Code optimization Impact to End user: No impact.

4.1.117 Low setup SSR HSDPA, HSUPA R.99 for UMTS network

Problem report: NA04800615 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Capacity & Performance, RRC setup failures Attached PRs: NA04807339, NA04818369, NA04822465, NA04826596 Probability: Permanent Description: Leg control in RSMU unit receives double release request during ICSU switchover. Leg control does not check if the leg resource index coming in release message is pointing to same or different record data (IP address+ port). Leg control will always clear reserved UDP port and other leg data inside leg control. But this leg data can be in use for other leg. Then new leg setup would take this UDP port again into use and then the error code would come from KREIVI. When this new leg is released (that was cleared by double release), it will again clear some other leg resource, so this error happens over and over again. Solution / Workaround: Restart every NPGE(P) WO-EX unit at same time (so that no unit goes back to WO-EX before all are restarted). For 2N NPGEP, WO-EX unit must be restarted using FCD parameter in ZUSU MML command to avoid switchover. Impact to Operator: Capacity & Performance, RRC setup failures Impact to End user: No impact.

4.1.118 ATM end point state mismatch

Problem report: NA04819924 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Capacity & Performance, Call setup success Attached PRs: NA04783745


Probability: Permanent Description: There is AAL path state mismatch between RNC and MGW. When path operational state has changed to disabled state it is correctly updated to MGW but on RNC side path remains in working state. State mismatch leads to a situation where RNC continuously tries to select a path which is not in working state in MGW. Solution / Workaround: Locking AAL2 path (LCS MML) in RNC. By this way path is taken out of selection in RNC. Impact to Operator: Call success rate dropping for Iu-CS. Impact to End user: Call creation fails.

4.1.119 RNC450 to RNC2600 HW upgrade: some DMCUs may fail after reverse cutover

Problem report: 51700ESPE01 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Unit Restarts Attached PRs: - Probability: Occasional Description: During HW upgrade from RNC40 to RNC2600, some of DMCUs can’t startup for very long time after reverse cutover. Solution / Workaround: Change failed DMCU unit state to TE, then back to WO, start up will continue. Impact to Operator: No impact. Impact to End user: No impact.

4.1.120 Problem with RNC196 step 5 upgrade to step 7

Problem report: 75033ESPE02 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: The egress parameter set on MXU for OMU RT channel is wrong, because all RT messages sending from other units to OMU are failing.


Solution / Workaround: Fault is cleared with system restart at the end of upgrade. Impact to Operator: Operation and maintenance / configurability on OMU Impact to End user: No impact.

4.1.121 During DMPG multi restart DSP fatal error 3d 8FFFFF97

Problem report: NA04807036 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, cell availability Attached PRs: 54809ESPE01, 22094ESPE07, NA04807045, 22286ESPE07, NA04826071, NA04823756, NA04808388 Probability: Occasional Description: When the cell services are being released, due to the invalid order of release, memory corruption and DSP restart happens with DSP FATAL error leading to high CPU load. Solution / Workaround: The correction is that TRM releases common channels in reverse order compared to reservation order, example reserve RACH + FACH_U + PCH, Release PCH, FACH_U and last one RACH. As this change is effected at cell release time only, so it doesn't have any other impact for other services. It is not a very big change in terms of functionality; it is just releasing services in a reverse order. Impact to Operator: Due to the DSP re-start multiple cells immediately go down, all the calls setup on these cells go down leading to service disruption. Impact to End user: Call drops.

4.1.122 HSDPA serving cell change fails occasionally

Problem report: 20844ESPE07 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Stability Attached PRs: - Probability: Occasional Description: Serving cell change transport level configuration fails due to the lost message. Occurring only in one testing environment.


Solution / Workaround: No workaround. Impact to Operator: Can increase dropped PS calls during serving cell change / decrease of some KPIs. Impact to End user: Delay/termination of PS call.

4.1.123 Strange SCCPCH3 allocation on spreading factor

Problem report: NA04792847 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: When operator modifies number of SCCPCH from 2 to 3 for WBTS with links down, spreading factors are not properly allocated for the cell. Solution / Workaround: Operator can still modify number of SCCPCH from 2 to 3 for WBTS with working links. Impact to Operator: Cell is in working state but no call is allowed in this cell. Impact to End user: UE is not able to make call.

4.1.124 KIDATA error message 11991 appears when IPNB is deleted and created again having WBTS already attached

Problem report: NA04797556 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04788223 Probability: Permanent Description: Due to unconfirmed issues, there are duplicate SCTP links which are the transportation layer of IP based Iub singalling of specified WBTS in RNC. When IPNB is deleted, only one copy of SCTP link is deleted, and other copies of SCTP links are not deleted. So when customer tries to recreate IPNB object, and attached the IPNB to specified WBTS, the attachment operation will fail due the SCTP link to be created already exists. There are two known bugs in RNC responsible for the problem:


1. The known bug of DB conversion program for SCTP link Database from RU10 to RU20, which is already corrected. 2. RNC application does not synchronize the timer with RNC Platform for attachment operation between WBTS and IPNB. Solution / Workaround: None. Impact to Operator: IPNB can not be attached to WBTS via RNW Object Browser. Impact to End user: No impact.

4.1.125 Cannot connect U-Plane after setting HSUPA with VCC bundle

Problem report: NA04806981 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: Problem concerns only WBTSs which COCO is modified while it is detached. Solution / Workaround: Attach COCO before doing any modification. Impact to Operator: Degraded amount of HSPA users can connect. Impact to End user: No HSPA service.

4.1.126 When system is restarted by operator during traffic, SP OMU turned to TE state

Problem report: 51774ESPE01 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability, Unit restart Attached PRs: - Probability: Permanent Description: When radio network is running and performing some traffic, system is restarted with TOT option by operator, but there will be 1685 alarm reported and SP OMU will turn down to TE state. SP-OMU will rise after recovery from TE state. Solution / Workaround: No workaround. Impact to Operator: Alarm 1685 is reported and it takes more time that SP-OMU is in


normal operational state. Impact to End user: No impact.

4.1.127 Missing RadioBearerReleaseComp during the release of PS NRT call

Problem report: NA04820667 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: NA04813599 Probability: Permanent Description: Incorrect radio bearer release message is sent to UE by RNC during RAB release when SL is on HSPA and SRB modification happens. During RAB release SRBs HSPA flow changes from NST to ST, but RRC is not including this information in radio bearer release message which causes UE not to respond to RRC radio bearer release message. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance/Call completion success Impact to End user: Call drop.

4.1.128 ICSU load increase in RU20

Problem report: 75410ESPE02 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Stability, Overload control Attached PRs: NA04833308 Probability: Permanent Description: ICSU unit CPU load was reaching critical level, causing instability for the radio network. High ICSU unit CPU load was caused by BRM process, which was using too much CPU time. Because of the criticality of the BRM process, the CPU priority of BRM process has been set to higher value than for other processes located in ICSU unit. This caused CPU time shortage for the other processes in ICSU unit. Problem was caused by the BRM functionalities, which are calculating radio bearer


allocations having HS-DSCH (HSDPA) or E-DCH (HSUPA) allocation. Calculation is done for multiple objects (cell, Local cell group, BTS) under the BTS. Calculation is done in real time, so it is triggered in every scenario, which changes UEs radio bearer configuration from the HS channel usage point of view. The more frequently allocations, releases and serving cell changes are done for HS channels, the more CPU usage this causes in ICSU unit. Solution / Workaround: No workaround Impact to Operator: Stability of the radio network increases when the ICSU load is not too high. Impact to End user: No impact.

4.1.129 Alarm 3384 (HMS TRANSMISSION LINE FAULTY) was generated when turn off the power from the sub rack and then TBU became unstable

Problem report: NA04819911 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Stability, TBU can't reach WO-EX/SP-EX state Attached PRs: - Probability: Permanent Description: Fault 1: Two alarms 3384 were set both on TBU-0. And only one would be reset if recover power supply, the other would never be reset even no HW HMS line problem. Alarm 3384 is an alarm with recovery action. If it's alive, the TBU-0 can't return to WO-EX/SP-EX state. Fault 2: Alarm 3384 was always set in such case. None alarm 3384 should be set while all HMS lines actually work fine. Solution / Workaround: 1. Block alarm 3384 before power off. ZAFB:3384 2. Unblock alarm 3384 after power on. ZAFU:3384 You could use ZAFP to list all blocked alarms. Impact to Operator: TBU can't reach WO-EX/SP-EX state. Impact to End user: No impact.

4.1.130 After SRNC relocation from mac-ehs capable cell under Rel 7 RNC to RNC version below Rel 7, PS NRT UL throughput is unstable

Problem report: 67338ESPE02 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP3


Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Occasional Description: When UE is instructed to use special HE field for RLC PDUs (UE & cell are capable to handle flexible RLC PDUs) and SRNC relocation is triggered to RNC version below Rel 7, RRC does not instruct UE not to use special HE value before relocation as there is no provision to inform RLC at target RNC via relocation container fro Rel6 and below RNC. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance / Data Throughput Impact to End user: Unstable PS service data rate.

4.1.131 Increased RAB setup failure ratio for PS calls after RN5.0 PP1.1 upgrade

Problem report: NA04822514 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: PrxNoiseAutotuning functionality was changed in RN5.0 MP2 so in that case Prx measurement from BTS was lower than current PrxNoise value, the measurement value was taken into use as new PrxNoise value. After these changes RNP parameter "PrxNoiseMaxTuneAbsolute" was not checked during this operation. This caused PrxNoise to get very low values (-112) which was seen in logs and this could not be prevented by "PrxNoiseMaxTuneAbsolute" parameter setting. Solution / Workaround: PrxNoiseAutotuning can be disabled in cell by set PrxNoiseAutotuning parameter OFF and making cell lock/unlock after that. PrxNoiseautotuning can be disabled also without cell lock/unlock procedure so that value of PrxNoise RNP parameter is changed from its original value and PrxNoiseAutotuning will be set OFF simultaneously. Changing of PrxNoise will trigger NBAP:PhysicalSharedChannelReconfiguration procedure to signal new PrxNoise to BTS. PrxNoise is used as reference point for HSUPA scheduling in BTS. And in case PrxNoise is in too low value also HSUPA scheduling target in BTS is in too low value. And since PrxNoiseAutotuning is switched OFF simultaneously, PrxNoise is no longer updated and thus the reference point for HSUPA scheduling is not changed to too low value in BTS either. Impact to Operator: Better PS NRT success rate and throughput after the correction.


Impact to End user: Better PS NRT success rate and throughput after the correction.

4.1.132 Occasional DSP restarts

Problem report: NA04858819 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: A - Critical Customer Impact: Stability, Unit restarts Attached PRs: - Probability: Permanent Description: It is possible that in certain error scenarios, DSP sends DMX messages with a wrong destination address resulting that the message is routed to a wrong processor and to a wrong process. In some cases these wrong messages arrive to the "p_idle" process (pid=0) of a DSP and this causes the EP_BAD_SIG_IDLE fatal error which results to a DSP restart. Solution / Workaround: No workaround. Impact to Operator: Due to the DSP restart multiple cells immediately go down, all the calls setup on these cells go down leading to service disruption. Impact to End user: Call drops.

4.1.133 RNC450 to RNC2600 HW upgrade: DSP-DSP channel opening failure (alarm 3343)

Problem report: 53058ESPE01 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: 51964ESPE01 Probability: Occasional Description: When there is frequently OMU switchover during HW upgrade procedure, there is possibility that some notification message about unit installation and removal may get disturbed, such as lost or message order broken; which would cause some unit doesn't get notified so it updates new unit information incorrectly and don't try to open ATM connection to those new unit. Solution / Workaround: No workaround. Impact to Operator: The problem can be reproduced by making frequent OMU switchover


during HW upgrade procedure. Impact to End user: No impact.

4.1.134 Internal problem blocks single DMPG causing HSxPA drop rate increased due to RL

Problem report: NA04828346 Exists in: RN5.0 Correction Target: RN5.0 MP3 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: NA04858130, NA04801167, NA04841518, NA04848028, NA04846522, NA04858130, NA04850009, NA04851086, NA04865575 Probability: Occasional Description: Due to seldom occurring internal L2 error in PDCP layer the memory gets corrupted and RLC is not able to receive any UL packets. All upcoming HS services for that particular DMPG unit are released with cause RLC unrecoverable error. Without manually restarting the unit, coming errors finally causes DSP fatal and the situation is temporarily fixed. Solution / Workaround: There is no workaround for the issue. Since the issue is happening for one DSP so DMPG/DSP restart might help. Impact to Operator: HSPA retainability degradation. Impact to End user: HSPA service dropped.


4.2 Generic faults corrected in RN5.0 MP4

4.2.1 RRC process exception after failure in handling of Signalling Connection Release Indication from UE

Problem report: NA04892329 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: RNC could not handle Signalling Connection Release indication from UE correctly in Cell_FACH and went to a hanging state where it could not react to any new requests also. Solution / Workaround: No workaround Impact to Operator: Alarms Impact to End user: No impact

4.2.2 Not able to collect alarm history (zahp) from OMS

Problem report: NA04882518 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Too small temporary space. DISTINCT and ORDER was used in SQL query. MySQL creates temporary table for such queries. MySQL server uses temporary space to create temporary partitions. Because data size of queried table was bigger than /tmp partition then query was failing. Solution / Workaround: No workaround Impact to Operator: Operability Impact to End user: No impact


4.2.3 Hanging AMR DCH causing lot of packet call setup failures by single UE

Problem report: NA04869216 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: NA04877452 Probability: Permanent Description: RNC cancels the CS call release procedure during ongoing Security procedure while the CS does not exist anymore in the CN anymore and RNC L2. Due to the conflicting configuration stored in the L3 call control after the release procedure cancellation, all attempts to establish PS user plane are failed causing the packet call setup failure counters to be increment with each failed attempts. Solution / Workaround: No workaround. Impact to Operator: Call setup success. Impact to End user: No impact.

4.2.4 OMS internal measurement handling process restarted in case of long WBTS name

Problem report: NA04882440 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics Attached PRs: - Probability: Permanent Description: Problem was that OMS could not handle WBTS names longer that 31 characters. If longer WBTS names were used, OMS internal MeaHandlerServ process was restarted because generation of data for performance management used data structure which could not handle longer WBTS names that 31 characters. As a result, measurement data which was processed during meahandler restart was lost. This situation applies only specific measurements which are using incorrect implemented software element. Solution / Workaround: is to use WBTS names shorter than 32 characters Impact to Operator: Impact to End user: No impact


4.2.5 OMS error 70159 MANAGED OBJECT FAILED

Problem report: NA04894997 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: OMS error 70159 MANAGED OBJECT FAILED. EMT connection management causes CMOCH to crash. Solution / Workaround: No workaround Impact to Operator: Operability Impact to End user: No impact

4.2.6 Timezone was not changed with changetimezone.sh script

Problem report: NA04881767 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Timezone changes are stored only to localimg so during new correction installation they are not taken as a basis for creating new SW set. Solution / Workaround: Manually execute command fsdistribute /etc/timezone /etc/sysconfig/clock Impact to Operator: Operability Impact to End user: No impact

4.2.7 ISHO failure counters are incorrectly updated after successful ISHO from 3G to GSM



Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: ISHO failure counters are wrongly pegged after successful ISHO from 3G to GSM. RRC Call control remembers the previously stored values when PS release was initiated due to MSActivitySupervision Timer expiry and it uses same to update ISHO failure counters even after ISHO has been successful. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Statistics / counters Impact to End user: No impact

4.2.8 Call drops after RNC relocation

Problem report: NA04923703 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: 26609ESPE05 Probability: Permanent Description: During UE not involved relocation, the UE radio resource manager in the RNC(UER) did not indicate proper AMR mode set to the lower layers. This in turn led to Iu UP not being initialized with proper mode set. Solution / Workaround: No workaround Impact to Operator: Drop in AMR call after relocation Impact to End user: Drop in AMR call after relocation

4.2.9 Bootprom upgrade execution (ZWDR) fails with empty info field



Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Boot programming (ZWDR) shows empty info field. This is caused because CBYPRB does not properly handle internal timer. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact

4.2.10 ICSU got restarted automatically

Problem report: NA04853459 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, Improve the stability of DMX unit Attached PRs: - Probability: Permanent Description: Problem is that the transmitting buffer resource of MS-SAR chip on ICSU is used up due to temporarily hardware error in this chip, so no more data could be sent out on this ICSU to other units. After a while, the system would find this isolated unit by supervision and forced it to be restarted. Solution / Workaround: No workaround Impact to Operator: Stability: Improve the stability of DMX unit Impact to End user: No impact

4.2.11 Setup Fail Other counter (M1022C19) increased in case of RL setup failure during state transition



Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: During CCH-DCH state transition after RL setup failure RRC signaling entity used too short timer to wait for another resource setup request from Radio Resource Management entity. Because of this the timer elapsed an state transition failed resulting increase in PS Setup Fail Other counter (M1022C19). Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success Impact to End user: Call setup failure

4.2.12 High increase in Packet Service RAB Setup Failures due to RNC after MP1 upgrade

Problem report: NA04785968 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: If UE makes cell reselection during PS RAB setup procedure in Cell_FACH then RNC cancels the PS RAB setup procedure and continues only the Cell Update procedure handling. Improvement needed to call control to only cancel the PS RAB setup procedure and after completion of the Cell Update procedure, resume the PS RAB procedure again and send new RRC Radio Bearer Setup to the UE. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call setup success Impact to End user: PS RAB setup procedure stops and is not resumed.

4.2.13 Call drop since IUR is not sending response to dedicated measurement requests / terminations to SRNC



Severity: C - Minor Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: The DEDICATED INITIATION MEASUREMENT REQUEST has been triggerred for "sir error " and transmitted code power " measurement type to the DRNC. DRNC (RNSAP PROTOCOL ) does not forward the resposone to this request to the SRNC which can result to call drop. Solution / Workaround: No workaround Impact to Operator: Data throughput Impact to End user: Call drop

4.2.14 Occasionally RRC was not prepared to handle a new Initial Direct Transfer message.

Problem report: NA04858135 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Logs Attached PRs: NA04869427 Probability: Permanent Description: If RNC starts RRC Connection Release procedure on receiving Iu Release Command from the last CN connection but same time UE sent new Initial Direct Transfer towards another CN domain, RNC was not prepared to handle it causing later problem in the Active Setup procedure. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Logs Impact to End user: No impact

4.2.15 NPGEP go to overload situation



Customer Impact: Capacity & Performance Attached PRs: - Probability: Permanent Description: There are too much internal debugging logs printed via the serial port and it consumes much CPU load. These will be removed. Solution / Workaround: LGU IU command showing as "OL" state, NPGEP switchover release overload situation. Impact to Operator: The call is dropped. Impact to End user: The call is dropped.

4.2.16 Occasional call drop in case of RL failure

Problem report: NA04872663 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance Attached PRs: - Probability: Occasional Description: When RL Sync wait timer for some DRNC radio link expired, also other radio links which were previously combined with an already released radio link with the same RL ID as the new failed RL, were incorrectly considered broken and the call was dropped Solution / Workaround: No workaround Impact to Operator: KPI / Call completion success rate Impact to End user: Call drop

4.2.17 Physical Channel Reconfiguration Failure scenario handling improvement in RRC to avoid CU due to RLC unrecoverable error for the user plane

Problem report: NA04862010 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: NA04940413


Probability: Permanent Description: If UE makes cell reselection when NW is configuring UE to Cell_PCH from Cell_FACH and UE rejects the state transition procedure, UTRAN ignores the UE response for cancelled state transition procedure and continues to assume that UE is in Cell_PCH while UE is in Cell_FACH. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Data throughput Impact to End user: No impact.

4.2.18 State transition to DCH fails if lossless PDU size change is used

Problem report: NA04838769 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: If the UE supports lossless PDU size change and DL PDU size 656 is used for the HS, then during state transition from Cell_PCH to Cell_FACH, RNC does not configure the PDCP that lossless PDU size change has been configured to the UE and PDCP header is maintained. Solution / Workaround: Lossless PDU size change support can be disabled. Impact to Operator: KPI, HSDPA Setup failure Impact to End user: Data throughput drops.

4.2.19 Call Control not handle the Security procedure cancellation correctly

Problem report: NA04864177 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: Call Control in RNC did not handle the Security procedure cancellation


correctly which caused later process exceptions (CCM process exception 028990E) since too old procedures were internally being executed when they were not valid anymore (RNC started to handle already rejected procedures too late). Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Alarms Impact to End user: No impact.

4.2.20 HSPA duration counter increased incorrectly in case of incoming SRNS relocation

Problem report: NA04921933 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Counter Attached PRs: - Probability: Permanent Description: RRC Call control does not initialise data strucutres to HSPA duration counter during incoming SRNS relocation correctly. So if SRNC relocation fails, it tries to update the duration counter but fails to find a valid start time and generates log writings for the invalid values stored internally. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance Impact to End user: No impact

4.2.21 AMR call setup failure due to DSP error

Problem report: NA04902511 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04917291 Probability: Permanent Description: AMR call setup fails during retry due to DSP error. DSP error is caused by wrong ciphering configuration sent to DSP.


Solution / Workaround: No workaround Impact to Operator: Call Setup Success Impact to End user: No impact

4.2.22 HSPA throughput degraded after inter-RNC handover

Problem report: NA04924326 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: During HSUPA TTI switching 2 ms to 10 ms, PS NRT RABs should be allocated 10 ms TTI untill throughput indication is received to allow switch to 2 ms. This functionality was missed out for Inter-RNC hard handover cases resulting that HSPA throughput degraded after Inter-RNC handover. Solution / Workaround: No workaround Impact to Operator:Capacity & Performance: Data throughput Impact to End user: Lower data throughput than expected

4.2.23 Internal timer handling problem UE involved relocation is interrupted by Cell Update

Problem report: NA04892455 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Internal Log Writing Attached PRs: - Probability: Permanent Description: During SignallingConnectionRelease, Handover control process of RRC starts UE involved relocation. RRC sets ‘HHO timer offset’ timer when HHO command is send to UE. UE does not receive RRC:RadioBearerConfiguration because UE’s RLC is not sending RLC acknowledgement. Ue involved relocation is interrupted by Cell Update when waiting response from UE but Timer ‘HHO timer offset’ is not reset. Solution / Workaround: No workaround


Impact to Operator: Internal log writing Impact to End user: No impact

4.2.24 Degraded CSSR performance due the overloaded CDSP-C card DCH DMPG units

Problem report: NA04874346 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success: R99 calls Attached PRs: NA04916416, 28488ESPE05, NA04891485 Probability: Permanent Description: Bad KPI values (decreased CSSR performance) due the overloaded CDSP-C card DCH DMPG units. This effects only R99 calls, not HSPA calls. R99 traffic is concentrated to certain DMPG's (DCH DMPG's) and HS traffic to others (HS DMPG's). R99 traffic can overflow to HS DMPG's (to DCH2 pool) if DCH DMPG's are fully booked. The threshold to start overflow traffic was too tight. It was done only after DCH DMGP's were totally out of free resources and already causing call setup failures due the DMPG overload situation. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success Impact to End user: Call setup failure

4.2.25 After partial failure during SHO of Multiple RL then UE Radio resource Management is not handling further processing request

Problem report: NA04888897 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success, Handover Success Attached PRs: - Probability: Permanent Description: SHO addition procedure was ongoing for multiple RL. Partial failure happens and SHO addition procedure fails for one of the RL. After this failure UE radio resource management entity is not handling further processing request. This cause process queue overflow and the


process exception. Radio resource manager entity should delete the resources for the failed radio link and should be able to handle the further coming request. Solution / Workaround: No workaround Impact to Operator: Call completion success Impact to End user: No impact

4.2.26 After OMU switchover, GTP call cannot be created

Problem report: NA04901383 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: After OMU switchover, GTP call cannot be created successfully. Solution / Workaround: No workaround Impact to Operator: Call setup successful ratio increases Impact to End user: PS Setup failures

4.2.27 Alarm 3986 ATM INTERFACE OPERATIONAL STATE CHANGE TO DISABLED was not cancel in RNC upgrade

Problem report: NA04879330 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: The process of the fault management is normal. When the SET is in SE-NH state, the 3986 alarm is set to a nonexistent target unit and can't be canceled. So the alarm is hanging. Solution / Workaround: Change SET state to WO and restart NIS1 unit.


Impact to Operator: There is hanging alarm. Impact to End user: No impact

4.2.28 CoCo modification is not possible

Problem report: NA04932610 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: 22629ESPE07, 22636ESPE07 Probability: Permanent Description: The CoCo cannot be changed if the system is very busy at that time. The root cause is that AAL2 Signalling Protocol Entity sends mass useless messages to CM (call management) when handling the reset request from remote NE, which leads to CM being busy so that CM cannot handle the CoCo change request. Solution / Workaround: No workaround Impact to Operator: Changing the CoCo configuration is not possible Impact to End user: No impact

4.2.29 Incorrect UL initial bit rate selected for the second PSNRT RAB

Problem report: NA04886022 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Occasional Description: UE-specific radio resource management entity (RRM) requests invalid bit rate from Base station Resource Manager during user plane creation for second PSNRT RAB when on first attempt faces UE transport capabilities limitation for higher bitrates re-attempt on cell initial bit rate which is incorrectly chosen based on WCEL-InitialBitRateUL instead of WCEL-HSDPAinitialBitrateUL even when HSDPA is already allocated to first PS-NRT.This resulted in channel type switch for existing RAB on HSDPA. Solution / Workaround: Not available


Impact to Operator: KPI / data throughput - counter M1002C477 (REL_ALLO_HS_DSCH_OTH_DCH_INT) the number of HS-DSCH allocation normal releases due to other than mobility-related HS-DSCH to DCH switch (e.g. multi-RAB restrictions) for interactive class connections. Impact to End user: Decrease in UL data throughput

4.2.30 ZT2C command cannot be executed via command calendar

Problem report: NA04866568 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: ZT2D fails after ZT2E is executed via command calendar. The success result is returned before the renaming of definition file when ZT2E is executed. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance Impact to End user: No impact

4.2.31 Output of ZNVI command shows abnormal printout

Problem report: NA04843388 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: NVI MML command does not show all signalling routes of signalling route set even the routes exists in the system and files. This was because the MML output was not called properly. Same data can be seen correctly with other MML commands, like NRI or NER. Solution / Workaround: No workaround Impact to Operator: Operability



4.2.32 No alarm when the control plane routes are not configured in RNC

Problem report: NA04863091 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: Information text for alarm in measurement threshold was truncated as in OMS Fault Management GUI 500 characters were acceptable but on server side only 32 characters were allowed. Solution / Workaround: No workaround Impact to Operator: Unable to see full text for threshold alarm. Impact to End user: No impact

4.2.33 Not possible to delete network interface

Problem report: NA04887895 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operative Attached PRs: - Probability: Permanent Description: Not possible to delete network interface with command syntax ZQRG:OMU,0&&1. The function of deleting the interface on units with command syntax ZQRG:OMU,0&&1 was not supported. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Operative Impact to End user: No impact


4.2.34 Spare update failure will cause 1258 alarm which lead to NPGEP spare unit restart

Problem report: NA04876152 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Stability Attached PRs: NA04906719 Probability: Permanent Description: In mass traffic situation, internal resource reservation occasional go wrong in spare EIPU unit, it will cause spare update failure. Solution / Workaround: Restart spare EIPU unit in night when traffic is low, can maximal avoid warming failure of spare EIPU unit. Impact to Operator: Spare NPGEP unit restart Impact to End user: No impact

4.2.35 RNC sends successful RAB Assignment Response even if IuUP Initialization fails

Problem report: NA04875370 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: During CS RAB setup IuUP initialization failure occurs but RNC sends success RAB assignment response to CN. Solution / Workaround: No workaround Impact to Operator: RAB Setup failure KPI impacted Impact to End user: No impact

4.2.36 Alarm 3385 PLUG-IN UNIT INSTALLATION ERROR occurs on RU20 MP3.0



Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Alarm Attached PRs: - Probability: Permanent Description: Alarm 3385 PLUG-IN UNIT INSTALLATION ERROR was reported occasionally, and this alarm was cancelled in 10 minutes by system automatically. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Alarm Impact to End user: No impact

4.2.37 DRNC allocated binding id is corrupted when it is sent over the IUR to SRNC

Problem report: NA04905484 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: New feature/functionality, HSPA over iur Attached PRs: - Probability: Permanent Description: Sometimes DRNC alloated binding id is corrupted, when it is sent over the IUR to SRNC. When SRNC uses this binding id in AAL2:ERQ targeted to this DRNC, it causes binding id timeout in BIF. Solution / Workaround: No workaround Impact to Operator: Call drop Impact to End user: Call drop

4.2.38 Due to RRC internal timer ongoing FACH relocation doesn't complete successfully resulting in HPL log writings



Customer Impact: Capacity & Performance, RRC success Attached PRs: - Probability: Permanent Description: During state transition from Cell_DCH to Cell_FACH, UE sends Cell Update from IUR and FACH relocation triggers. During FACH relocation signalling messages come to RRC late which results in expiry of RRC internal timer. Solution / Workaround: No workaround Impact to Operator: RRC Success related KPI impacted and HPL monitoring Impact to End user: No impact

4.2.39 Bad manner of SNMPRO causes unexpected SIB updates

Problem report: NA04873094 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: When local subsystem inquiries the remote subsystem state with sccp_subsys_state_inq_s (8150), SMNPRO answered with the real state at that moment. However if SSP_FILTER timer is still running, subsystem should get the previous state i.e. available in the sccp_subsys_state_inq_ack_s response. The consequence was that RC3PRB started to update (SIB 1 CN domain indicator) states via REKOVE/RRAPRB. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success Impact to End user: Problems in vendor UE

4.2.40 HMS system cannot set subrack fan speed which cause alarm 3198 (FAN SPEED CAN NOT BE SET)



Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: HMS system cannot set subrack fan speed which cause alarm 3198 FAN SPEED CAN NOT BE SET is set. HMSS I2C bus between PD30 and FTRA is stucked and lost connection with fan array. Fans speed and temperature value cannot be set and get, Solution/ Workaround: Reset HMSS node of plut-in-unit and recover the connection Impact to Operator: Operation & Maintenance Impact to End user: No impact

4.2.41 Working SFU spontaneous restart

Problem report: NA04870261 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, Unit restart Attached PRs: NA04988185 Probability: Permanent Description: Problem was that the WO-EX SFU get spontaneous restart. That was caused because CPU was stucked after accessing one SF10E's hardware register. Solution / Workaround: No workaround Impact to Operator: Unit restarts Impact to End user: No impact

4.2.42 After SP-NPGEP restart some OSPF route is lost on SP-NPGEP

Problem report: NA04863094 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance Attached PRs: - Probability: Permanent


Description: Reception buffer for NPGEP on SP side is too small to copy the LSA data within OSPF area at the synchronization of OSPF protocol data (e.g. neighbor, Interface, Link State Database) between WO-NPGEP and SP-NPGEP. Solution / Workaround: Restart SP unit from disk. Impact to Operator: Alarm 3472 (IU-PS IP ROUTING ERROR) will generate Impact to End user: Uu/Iur/Iub/Iu-CS/Iu-PS traffic will be lost

4.2.43 Increase in HCAP counters specifically HCAP_IFHO_MEAS_START_FAIL

Problem report: NA04897172 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, M1008 counters Attached PRs: NA04907373 Probability: Permanent Description: If compressed mode is triggered due to HSCAHO DCH/DCH allocation and the CM preparation fails due to ongoing internal RNC procedure, handover control incorrectly updates M1008C263 counter. If same failure happens during HS-DSCH/DCH allocation, M1008C263 counter is not updated. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, M1008C counters Impact to End user: No impact

4.2.44 Counter M1006C151 the number of attempted state transitions from FACH to HS-DSCH updated incorrectly during PCH-DCH transition cancel

Problem report: NA04876595 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Wrong statistics information Attached PRs: - Probability: Permanent Description:


Counter M1006C151 was updated incorrectly during PCH-DCH transition cancel. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance / Statistics & Counters Impact to End user: No impact

4.2.45 Alarm 1078 resulting call drop

Problem report: NA04900351 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: - Probability: Permanent Description: Alarm 1078 PROCESS EXCEPTION when IFHO RL is added and sync indication for that arrives resulting call drop. Solution / Workaround: No workaround Impact to Operator: Call Completion Success Impact to End user: Call drop

4.2.46 PS service abnormal after NPGEP switchover with FCD option

Problem report: NA04881550 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04908705 Probability: Permanent Description: In NPGEP FCD switchover, current implementation is vulnerable to timing of recovery systems unit state updates to library. This means that in FCD switchover situation unit state in library is not what unit handling program block expects. This causes now that FCD switchover does not trigger call resource release operations as it should. Solution / Workaround: WO NPGEP unit restart


Impact to Operator: PS call through the NPGEP could not be made Impact to End user: Failed PS call

4.2.47 IUV sends an empty location report message to CN.

Problem report: NA04879216 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, Statistics / counters Attached PRs: - Probability: Permanent Description: RNC sends empty SCCP message to the CN, which cause "protocol error" indication from CN to the RNC. There was fault with Multi rab calls, where already released call (CS or PS) location reporting was continued, when another domain has still active connection. When that old RANAP resources will reserved again to new call and if that previous UE RRC connection is still active, then these location reporting messages will handled in these new RANAP connection, in case when location reporting is not activated RANAP notice that and skip message ASN.1 encoding but it still sends the SCCP message which is empty in this case. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance : Statistics / counters Impact to End user: No impact

4.2.48 Inter-RNC handover failure with HSPA over IUR enabled

Problem report: NA04878563 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Handover Success Attached PRs: - Probability: Permanent Description: AAL2 path selection allocates all HSDPA DL connections on Iur to one path although they should be divided to all paths on route. That causes uneven distribution of CIDs and CID allocation error. Solution / Workaround: No workaround


Impact to Operator: Call success drop on Iur Impact to End user: Unsuccessful handover

4.2.49 RRC hand crashes after receiving two Cell Updates from the UE

Problem report: NA04894709 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: 84149ESPE02 Probability: Permanent Description: When RRC receives Cell Update from the UE while a Radio Bearer Reconfiguration Process is ongoing the RRC sends Cell Update Confirm message to the UE. Then if the UE again sends a Cell Update message to the RRC with failure_cause filled as "Invalid Configuration", then RRC crashes due to incorrect filling of Radio Bearer Release Information in the Cell Update Confirm Message. Solution / Workaround: No workaround Impact to Operator: Call completion success Impact to End user: No impact

4.2.50 Fractional DPCH never activated at RRC connection setup

Problem report: NA04866934 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Long name of parameter FDPCHSetupEC was "F–DPCH Setup based on Establishment Cause" and it was source of some misunderstanding. Solution / Workaround: No workaround Impact to Operator: New name of parameter will be displayed OBRO



4.2.51 ZWPD command executed without warning message and customer confirmation

Problem report: NA04886104 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: There was no warning message when giving ZWPD MML command. The command has risk to cause RNC outage. Solution / Workaround: No workaround Impact to Operator: ZWPD now requires operators confirmation Impact to End user: No impact

4.2.52 CS call setup fails due to cell update not handled correctly in cell_DCH state

Problem report: NA04882388 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call completion Success Attached PRs: - Probability: Permanent Description: If UE makes Cell Update in Cell_DCH state and there is only CS signalling connection established, then RNC does not allow RRC Connection Re-establishment even if T314 is greater than zero. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call completion Success Impact to End user: Call drop


4.2.53 Iub AAL2 signaling congestion control improvement

Problem report: NA04846901 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, RRC Success Attached PRs: 84860ESPE02 Probability: Permanent Description: Currently there is no AAL2s signaling specific overload control implemented in RNC to protect AAL2 signaling link from overload situation in case of very limited Iub transmission configuration. Problem was that If AAL2 Signaling link load exceeded configured value and NBAP overload control algorithm was not able to limit the load, AAL2 signaling started to be congested. In case of severe, long lasting AAL2 signalling overload situation, RNC finally ended up in total AAL2 Signaling Link congestion (deadlock) situation. As a result, any of AAL2 signaling requests under that Iub connection could not be handled and all call attempts were rejected (100% RRC rejection rate due to Iub) and Alarm 1192 SSCOP TRANSMIT BUFFER OVERFLOW was raised. Situation could not be recovered without a BTS restart. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: RRC setup success Impact to End user: Call setup not succeed

4.2.54 HS layer disabled but operational state enabled

Problem report: NA04873125 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: HS layer is disabled but operational state is visible as enabled. It is almost impossible to catch the DMX monitoring from live network. The problem requires to be traced through code review. Solution / Workaround: No workaround


Impact to Operator: Operability Impact to End user: No impact

4.2.55 Alarm 7771 WCDMA CELL OUT OF USE is not canceled correctly

Problem report: NA04873101 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: During common channel recovery for several cells, if cell state notification sending to telecom program block fails for one or more cells, then the alarm 7771 WCDMA cell out of use is not cancelled even for successful cells. So the alarm remains in hanging state for working cells. Solution / Workaround: No workaround Impact to Operator: Hanging 7771 WCDMA CELL OUT OF USE alarms are not visible Impact to End user: No impact

4.2.56 AMR call rejections due to lack of DSP capacity

Problem report: NA04822201 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: AMR call rejections due to lack of DSP capacity, when AMR call is established on top of other call (Multi-RAB call) even RNC level DSP capacity usage is only 80%. To limit the amount of DSP-DSP communication overhead, AMR RABs must be allocated from the DSP unit where SRB is located. In Multi-RAB cases AMR RAB is established long time after SRB, thus it is possible that SRB DSP is full, even in total level RNC has some amount of DSP capacity left. Solution / Workaround: No workaround.


Impact to Operator: Slight decrease in KPIs due to small amount of rejected AMR calls. Impact to End user: AMR call attempt fails, when AMR call is attempted on top of other call.

4.2.57 Fallback does not copy command calendar file (CTRCALGX.MIF)

Problem report: NA04879349 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: The calendar file CTRCALGX.MIF is not copied during fallback copying, so the calendar tasks are lost after FB build is activated. Solution / Workaround: After fallback copying, the file CTRCALGX.MIF can be copied to FB build manually Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact

4.2.58 Diversity handover was rejected by RNC admission control incorrectly

Problem report: NA04875320 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Handover Success Attached PRs: - Probability: Permanent Description: Diversity handover was rejected by RNC admission control due it estimated DL power increase to be too high. RNC admission control was using wrongly calculated too high initial DL power value when it was doing DL admission decision for requested branch addition. Solution / Workaround: No workaround Impact to Operator: Increase in statistics which indicates number of failed diversity handovers.


Impact to End user: Diversity handover failed incorrectly

4.2.59 Inter-system handover from 2G to 3G fails when UE capability information is not available

Problem report: NA04901017 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Handover Success Attached PRs: - Probability: Permanent Description: The UE radio resource manager (UER) in the RNC rejects inter-system handover from 2G to 3G if UE transport channel capability information is not available when the UER module is started. In this case, a pre-defined default configuration shall be used and all UE capability related checks shall be omitted since the UE capability information is received only later during the ISHO call setup. Solution / Workaround: No workaround Impact to Operator: ISHO related counters increase. Impact to End user: Inter-system handover from 2G to 3G fails.

4.2.60 HSPA Handover failure

Problem report: NA04890088 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Handoverover Success and RRC success Attached PRs: - Probability: Permanent Description: During EDCH downgrade, SRNC is requesting DRNC to create new transport bearer resources but RRC at DRNC is not sending request to tranport resource manager(TRM) at DRNC to create new transport bearer paramters for EDCH link at DRNC due to which TRM is not creating new resources and DRNC is responding SRNC with wrong parameters in IUR radio link reconfiguration ready due to which EDCH reconfiguration is failed. Solution / Workaround: No workaround


Impact to Operator: Handover Success and RRC Success related KPIs impacted Impact to End user: Call Drop

4.2.61 RRC Connection Release is triggered due to Iu Release Command from CS domain

Problem report: NA04892469 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, RRC success Attached PRs: - Probability: Permanent Description: RRC Connection Release is triggered due to Iu Release Command from CS Domain. RRC receives Cell Update from UE from different cell and RRC Connection release on Common Channels is triggered. Before UE could receive RRC Connection release it triggered Iu-PS Signalling Connection Establishment by sending initial Direct transfer message to RNC. During Iu-PS Connection Acknowledgment from PS CN RNC triggeres Iu-PS Signalling Connection Release. Now Iu Release Command is received from PS CN which is not handled properly causing hanging network resources. Solution / Workaround: No workaround Impact to Operator: RRC Setup Success KPI impacted Impact to End user: No impact

4.2.62 Ongoing FACH relocation incorretly handled resulting HPL log writings

Problem report: NA04892495 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: During state transition from Cell_DCH to Cell_FACH, UE sends Cell Update from DRNC and Cell_FACH relocation triggers. Meanwhile UE sends Cell Update from SRNC which cancels ongoing FACH relocation. Then CN sends Iu release command to RNC. While handling Iu release command from CN, due to wrong updation of RRC internal data structure RRC hangs and later internal RRC timer expires which causes HPL monitorings.


Solution / Workaround: No workaround Impact to Operator: Capacity & Performance : RRC Success Impact to End user: UE resources hang

4.2.63 Counter Compressed Mode Not Possible for NRT call updated incorrectly

Problem report: NA04739804 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Statistics / counters Attached PRs: - Probability: Permanent Description: When compressed mode preparation is cancelled because of RRC connection release the failure counter is updated incorrectly. Solution / Workaround: No workaround Impact to Operator: Degradation of the KPI IS_COM_MOD_STA_NOT_POS_NRT Impact to End user: No impact

4.2.64 Unable to associate COCO to WBTS

Problem report: NA04869108 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: When MXU is in switchover, it could not accept requests from broker program block.The broker will set a barring flag and saved all requests. When MXU switchover end, broker program block will send out all these saved requests. If msg is lost or msg could not came in broker's msg queue,broker program block will not clear the barring flag forever. And all new requests to that MXU will be refused by broker forever. Solution / Workaround: No workaround


Impact to Operator: resources creation to that MXU will be refused Impact to End user: No impact

4.2.65 Unnecessary ISHO attempts after state change from DCH 0/0 to DCH with bitrate allocation

Problem report: NA04885081 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, ISHO NRT attempts Attached PRs: - Probability: Permanent Description: Problem was that handover control did not re-calculate ISHO triggering thresholds for DL TX PWR trigger when DCH allocation changed from DCH0/0 to DCH with bitrate (resource) allocation. When RAB configuration changed from HSDPA - DCH0/0 - DCH with bitrate, compressed mode and ISHO measurement could be started due to DL TX PWR trigger even when the thresholds were not exceeded resulting that call was handed over to GSM unnecessarily. When PS NRT is mapped to HSDPA (without AMR) DL TX PWR trigger is not used to trigger IFHO or ISHO measurement. However, DL TX PWR reports received from BTS are stored. If HSDPA was released and call was allocated to DCH 0/0, Handover control did not re-calculate ISHO triggering thresholds for DL TX PWR trigger when DCH allocation changed from DCH0/0 to DCH with bitrate (resource) allocation. This could cause that DL TX PWR reports received during HSDPA or DCH0/0 allocation unnecessarily triggered CM and ISHO measurement when DCH with resources was allocated. Solution / Workaround: No workaround Impact to Operator: Call is not handed over to GSM unnecessarily. Amount of ISHO NRT attempts should decrease. Impact to End user: Call is not handed over to GSM unnecessarily

4.2.66 Alarms 7750 FAILURE IN WCDMA WBTS O&M CONNECTION

Problem report: NA04868780 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: -


Probability: Permanent Description: In some cases, the L3 route will be created before L2 route, then the related gate of this L3 route will be set to default route. Then the connectivity of this path will be lost. Solution / Workaround: OMU swithover Impact to Operator: Capacity & Performance: Data throughput Impact to End user: No impact

4.2.67 Call setup failure due to incorrectly handled RRC Connection Release procedure

Problem report: NA04880114 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If UE makes new signalling connection towards CN for which it already sent Signalling Connection Release Indication earlier causing RRC Connection Release to be triggered. Then RNC cancels the RRC Connection Release procedure and continues only with the RBRelease procedure but it does not handle the cancellation of the RRC Connection Release procedure too nicely becase of which the Security Procedure is rejected if it is received during the RBRelease procedure. Solution / Workaround: No workaround Impact to Operator: Call Setup Success Impact to End user: No impact

4.2.68 Alarm 1078 due to RRC PROCESS EXCEPTION

Problem report: NA04888603 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent


Description: If UTRAN receives unexpected and corrupted RRC message from UE including invalid RB Uplink Activation Time Info IE then Call Control entity could not handle that and causes expection of the process. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Alarms Impact to End user: Call drop

4.2.69 Download IP plan to change bandwith is not possible

Problem report: NA04759738 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: This problem happened because in IP plan there is unnecessary restriction when change IP based route commited bandwidth, it will cause changing bandwidth via IP plan not possible. Solution / Workaround: Use MML to modify the committedBW or use IP plan to modify both committedBW and other BW related parameters. Impact to Operator: Configuration of IPBR is not feasible Impact to End user: No impact

4.2.70 Paging degradation, 3G-2G IRAT RT HOF and 3G-2G RT ISHO failures post Iu-CS-IP

Problem report: NA04904109 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Stability Attached PRs: - Probability: Permanent Description: S3CMAN stores MTP3 link number corresponding to the association set in temporal storage in its work file s3work. Now the link number in S3CMAN storage does not match the real link


number used by CCNETM from MTP3 configuration. In that case CCNETM sets alarm 2075 COMMUNICATION FAILURE BETWEEN SIGNALLING TERMINAL AND CCNETM, when S3CMAN sends init_request to CCNETM with wrong link number. Solution / Workaround: As a workaround S3CMAN can be restarted with ZOKR:592 command in the WO-EX RSMU. Impact to Operator: M3UA signalling links may not activate Impact to End user: No impact

4.2.71 Alarm 1304 ACTOR EXCEPTION was generated from DMPG after bblog -command

Problem report: NA04883253 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: After bblog -command alarm 1304 ACTOR EXCEPTION was generated from DMPG indicating DAKOTA exception. The reason of the exception was invalid address accessing. Exception was caused by print function which is not safe but will lead to accessing a invalid address if the string is not terminated correctly. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact

4.2.72 Improvement of corrupted PDU handling (corrupted UL Cell update message from UE )

Problem report: NA04928921 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent


Description: Call control in RNC goes into hanging state if during state transition from Cell_DCH to Cell_FACH, the UL response message from UE for the state transition command could not be decoded correctly and thus ignored and then RNC receives RRC Signalling Connection Release Indication from the UE. Solution / Workaround: No workaround Impact to Operator:Operation & Maintenance: Alarms Impact to End user: No impact

4.2.73 RAB Reconfiguration failed due to RL failure during state transition

Problem report: NA04882565 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04894866, NA04896573 Probability: Permanent Description: During state transition from Cell_FACH to Cell_DCH, if new RB Mapping is given to the UE and the state transition procedure fails due to UE not able to establish the connection and detects loss of radio link, then RNC does not provide RB Mapping for the RBs in the next state transition attempt which causes also the next attempt to fail. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: No impact

4.2.74 Unnecessary alarms 7772 and 7771 during cell shutdown when activating PCH 24kbps

Problem report: NA04882241 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Occasional Description: RNC tried to downgrade HS-PDSCH codes during cell shutdown from periodic


trigger because there were no HSDPA users in cell anymore. HS-PDSCH code downgrade failed because cell shutdown was ongoing and alarms 7772 and 7771 were unnecessary raised Solution / Workaround: Disable HSDPA 10/15 codes Impact to Operator: Operation & Maintenance - Alarms Impact to End user: No impact

4.2.75 Increase of RAB setup failures CS voice due to AC in case iBTS sharing relocation from ADA to RNC

Problem report: NA04899632 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: After CS triggered relocation from ADA to RNC, UE cannot be moved to Cell_DCH state again if it entered Cell_FACH/Cell_PCH state after CS release and inactivty on the PS RB because Call Control still remembers the previous setup in anchoring and next time when state transition to Cell_DCH is triggered, it tries to establish radio link with incorrect BTS id. Solution / Workaround: No workaround Impact to Operator: Call Setup Success Impact to End user: No impact

4.2.76 Transport_resource_release_s message cause process exception

Problem report: NA04890928 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability Attached PRs: - Probability: Permanent Description: Internal RL failure indication message used in DRNC has room only for 3 radio


links so when there were 4 RLs in DRNC and they all failed at the same time, it caused an alarm 1078 indicating RRC PROCESS EXCEPTION (FAM 4FD). Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Alarms Impact to End user: Call drop

4.2.77 RRC sends an unnecessary M1022 ticket for cancelled UP setup

Problem report: NA04843705 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: RRC sends packet call ticket indication PS RAB user plane allocation failure although the procedure was cancelled due to UE initiating release of the PS connection. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact.

4.2.78 Call setup failure if FACH to DCH state transition in cancelled during ongoing location update

Problem report: NA04910147 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If state transition from Cell_FACH to Cell_DCH is cancelled and there is ongoing location update same time then RNC could not handle the LU correctly after cancellation of the state transition procedure and Initial Direct Transfer from UE was sent to wrong RANAP signalling entity and LU attempt failed. Solution / Workaround: No workaround


Impact to Operator: Capacity & Performance: Call setup success Impact to End user: No impact

4.2.79 RRC gets confused with first CU over IUR received then CU from same RNC

Problem report: NA04908278 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If UE moves to another RNC area during state transition from Cell_FACH to Cell_DCH then SRNC cancels the state transition procedure but it does not make correct decision about the configuration stored in the UE for the RB Mapping which causes later incorrect configuration to be sent to UE during later attempts to move UE to Cell_DCH and UE keeps on rejecting the state transition procedure. Solution / Workaround: No workaround Impact to Operator: Call Setup Success Impact to End user: No impact

4.2.80 Security Mode command not sent out from RNC when UE is in transition Fach - PCH

Problem report: NA04895844 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If UE sends Initial Direct transfer for CS CN after UTRAN has sent out command for state transition from Cell_FACH to Cell_PCH and UE initiates Cell Update, RNC could cancel the state transition procedure from UE and continue with handling the Initial Direct Transfer after moving UE back to Cell_FACH. In other case, UE should be able to cancel the state transition procedure by transmitting Failure message in response if it has initiated CS call or then initiate Cell Udate with Uplink Data transmission.


Solution / Workaround: No workaround Impact to Operator: Call Setup Success Impact to End user: No impact

4.2.81 CS calls not possible since incoming relocations from ADA were rejected in RNC

Problem report: NA04904099 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: Incoming relocation triggered from ADA were rejected in RNC if the relocation was triggered for establishing radio link in the ADA. RNC could not identify this case as iBTS sharing relocation from ADA and so rejected the request because the Target cell was not found in the RNC. Solution / Workaround: No workaround Impact to Operator: Call setup success Impact to End user: No impact

4.2.82 HSUPA related (ERGCH/EHICH) DL spreading codes were left hanging in RNCs code resource tables

Problem report: NA04917485 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance Attached PRs: - Probability: Permanent Description: HSUPA related (ERGCH/EHICH) DL spreading codes were left hanging in RNCs code resource tables. Solution / Workaround: Disable HSPA 72 users per cell will eliminate hanging ERGCH/EHICH code possibility, because ERGCH/EHICH code allocation is then static.


CoCo detach/reattach is needed to reset RNCs code resource tables in case hanging ERGCH/EHICH codes exist in cell. Impact to Operator: Decreased DL Spreading code capacity in cell Impact to End user: Possibly lower data throughput because of decreased DL Spreading code capacity in cell

4.2.83 Corrupted downlink Echo Reply resulting to lost ping

Problem report: NA04887497 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data THroughput Attached PRs: - Probability: Permanent Description: During state transition to Cell_DCH from Cell_FACH, if the DL RLC size changes for the PS RB, then RNC starts to send DL PDU to UE even before the new HFN has been received from UE in the response message for the successful transition and configured to ciphering module in RNC. Solution / Workaround: No workaround Impact to Operator: Data Throughput Impact to End user: No impact

4.2.84 M1001C16 RRC_CONN_ACT_FAIL_RADIO_INTERFACE updated incorrectly if CU received from DRNC

Problem report: NA04908274 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: If UE sends Cell Update from DRNC area in Cell_FACH, RRCPRB updatesRRC drop due to Radio counters because it cannot different between Cell Update initiated due to radio connection lost from Cell Update due to cell reselection when T314 is greater than zero correctly.


Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Statistics / counters Impact to End user: No impact

4.2.85 HSDPA Setup Failures in case of Iub congestion

Problem report: NA04852747 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call setup time, Data Throughput Attached PRs: - Probability: Occasional Description: Resource Manager entity incorrectly re-attempts on the DRRC cell (selected with HSPA layering) instead of the source cell when first attempt on DRRC cell faces IUB congestion causing the failure of cell FACH to cell DCH transition for the UE. This was seen by customer as HSDPA setup failures due to Iub (M1002C422,SETUP_FAIL_IUB_MAC_D_BGR M1002C425,SETUP_FAIL_IUB_HS_TOTAL_BGR ) Solution / Workaround: NA Impact to Operator: KPI / HSDPA setup success Impact to End user: Delay in getting HSDPA connection

4.2.86 Timeout in pinging the server after PDP context activation

Problem report: NA04908999 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance Attached PRs: - Probability: Permanent Description: After PS NRT setup on HSPA, DMCU status was not updated correctly in the internal data structures which caused problem later during the state transition to Cell_FACH procedure when RRC tried to establish the resources again which are already existing. Solution / Workaround: No workaround


Impact to Operator: Call drop Impact to End user: Call drop

4.2.87 Alarm 71007 are not reported anymore on NetAct after RNC SW upgrade MP3

Problem report: NA04909622 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: NA04896355, 80763ESPE02, NA04922393 Probability: Permanent Description: If alarms 71007 are raised they are not visible on NetAct, due to an erroneous alarmevent conversion. The alarms in case are "Measurement Threshold Monitoring Limit Exceeded" and they are raised when conditions set on Application Launcher/NE Threshold Management are met. Solution / Workaround: No Workaround Impact to Operator: Alarms 71007 are not visible on NetAct Impact to End user: No impact

4.2.88 RNC restart in case other WDU has hardware problem even another WDU is fine

Problem report: NA04882815 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, System restarts Attached PRs: - Probability: Permanent Description: One WDU has hardware problem but this lead to software works abnormal even the other WDU is fine. Solution / Workaround: Plug out the faulty WDU. Impact to Operator: Operator cannot use NE while system restarts. Effects cell availablity Impact to End user: Call no possible


4.2.89 Transport resource manager sends resource allocation message to non-existing Layer 2 PRB hand

Problem report: NA04861443 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: NA04897018 Probability: Permanent Description: Transport resource manager sends resource allocation message to non-existing Layer 2 PRB hand. During the scenario of user plane re-establishment Signalling channel ATM DCH memory allocation at Transport resource manager is not properly released when Layer 2 sends error of IP link not available for HSPA IP branch. Solution / Workaround: No workaround. Impact to Operator: KPI drops. Impact to End user: Calls fails when DMCU re-establishment is taking place with dual IUB and transport fallback is happening.

4.2.90 CSSR Call Setup Success Rate for voice counters are not accurate

Problem report: NA04878470 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics / Counters Attached PRs: - Probability: Permanent Description: Voice call attempts that start from PCH-state and fail before successfull state change to FACH or DCH, are not counted to CSSR formula. Current Call Setup Success Rate (CSSR) formula for voice (e.g. RNC_565) does not take properly into account the calls started from cell_PCH state i.e. those that do not need RRC Connection setup procedure. Calls starting from cell_PCH can fail in state transition from cell_PCH to cell_DCH or cell_PCH ro cell_FACH to cell_DCH and none of the current CSSR formula counters are incremented. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Statistics / Counters



4.2.91 Call failures due to DSP errors (code 7008003a, 701f0023 and 70090011)

Problem report: 84415ESPE02 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion success Attached PRs: - Probability: Permanent Description: RNC does not handle Security procedure correctly if SRNS relocation has been cancelled due to incoming new CN connection establishment by the UE and it causes incorrect configuration to be sent to the RLC entity in the RNC and call is dropped. Solution / Workaround: No workaround Impact to Operator: Call Completion success Impact to End user: Call drop

4.2.92 Service area broadcast process restarted when the operator changed the IP address of CBC

Problem report: NA04876559 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Availability of SAB service,, SAB related counter KPIs Attached PRs: - Probability: Permanent Description: Service area broadcast process was restarted when the operator changed the IP address of CBC. When operator disconnects the old interface and connects to the interface, if SA3 has to send RESTART/FAILURE during that transition time, SA3 accidentally closes an invalid connection FD (file descriptor). When the CBC makes connection from the new interface, that connection is made on the invalid file descriptor which causes the reinitialization of all the existing file descriptors. But SA3 couldn't recover the invalid file descriptor forever which is retried on every supervision cycle. SA3 now got sab_sai_info_s. After handling this message, SA3 went on to listen on select call which it shoudn't because the file descriptors are not recovered. As SA3 is listening on invalid file descriptors, it get blocked forever and


doesn't reply to supervision leading PRB restart resulting that SAB services are unavailable for a short period of time. Solution / Workaround: No workaround Impact to Operator: Unavailability of SAB services for a short time Impact to End user: Unavailability of SAB services for a short time

4.2.93 DSP restart due to fatal error

Problem report: NA04833519 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Cell Availability Attached PRs: 22992ESPE06 Probability: Permanent Description: The problem is caused by lack of buffer for signaling connection. In case of high CPU load, signaling connection bandwidth will be exhausted by burst calls. When there is no free bandwidth to use, the fatal error will occur that causes unit restart and all calls are dropped. Solution / Workaround: No workaround Impact to Operator: Stability: Unit restarts (DSP restart) Impact to End user: Call drops

4.2.94 Inconsistency in counters for Paging in Cell PCH

Problem report: NA04875833 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / Counters Attached PRs: NA04830175 Probability: Permanent Description: Counter M1006C157 CELL_UPD_AFTER_CELL_PCH is sometimes greater than M1006C155 PAGING_OCCASION_CELL_PCH leading to a paging success rate 100%. Solution / Workaround: No workaround


Impact to Operator: Operation & Maintenance: Statistics / Counters Impact to End user: No impact

4.2.95 All IUR BFD session gone and creation of BFD session ends up with error

Problem report: NA04857655 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: NA04843807 Probability: Permanent Description: All Iur BFD sessions are lost. Creation of BFD session comes up with error. Part of XIPBFS1X.XML is lost and the file is corrupted. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call completion success Impact to End user: No impact

4.2.96 Radio Bearer Reconfiguration procedure incorrectly completed resulting RLC error

Problem report: NA04819218 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Internal Log Writting / Unnecessary RLC error Attached PRs: NA04872252 Probability: Permanent Description: Radio Bearer Reconfiguration Complete was not received by RNC L3, due to CDSP-DH RLC did not allow STATUS PDUs for the missing uplink PDUs to be sent in DL during SRB2 suspend resulting RLC error. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Internal Log Writting / Unnecessary RLC error Impact to End user: No impact


4.2.97 DSP SUPERVISION FAILURE with fatal error code 80000003 and extra info 0000000E

Problem report: NA04927123 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call completion success Attached PRs: NA04942208, 23143ESPE06 Probability: Permanent Description: In the L2 implementation in RNC some memory was erroneously overwritten resulting corrupted PID value and fatal error when this illegal PID is used. Operator can see the alarm 1239: DSP SUPERVISION FAILURE with fatal error code 80000003 and extra info 0000000E. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call completion success Impact to End user: No impact

4.2.98 Partial backup size of OMS has decreased after MP3

Problem report: NA04929136 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: Partial backup previously took lot of space and it has been changed to take a smaller size in MP3. The configuration was changed to optimize the memory usage by excluding some unnecessary directories. For operator the change is visible when comparing the sizes of current partial backup to previously taken partial backup. Solution / Workaround: No workaround Impact to Operator: Operation & maintenance Impact to End user: No impact


4.2.99 Some of the counters are missing from Key Counters measurement (M1050) while transfering to NetAct

Problem report: NA04902465 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Key Counter measurement is saved to omes by OMS and transferred to NetAct periodically. Key counter save operation is delayed. It occures, as default, 10 minutes later than measurement save timestamp. E.g. for source measurement saved at 23:00 the Key Counter will be saved at 23:10. On the other hand transfer of measurement files from OMU to OMS is executed, as default, every 5 minutes and lasts 1 min. So the files are transfered from OMU at e.g. 23:00, 23:05, 23:10, etc. It could happen that not all mesurement files for the same period are downloaded in more than one shot. E.g. measurements for 23:00 will be transfered within 23:10 - 23:11. In such case Key Counter measurement is already stored. Solution / Workaround: It is additional/alternative soulution to changing MeaDataNotifDelay provided in the correction. One can increase frequency of polling files from OMU by setting LDAP parameter FileMsgSendInterval. Path to the parameter in LDAP: fsClusterId=ClusterRoot fsFragmentId=OMS omsFragmentId=OMSPlatform omsFragmentId=SS_GenericPM omsFragmentId=OMSDXIPMNotif, The value's unit is seconds and as default 300 is set. Recommended value to fix the problem is 180. It is highly recommended not to change the value to less than 180 seconds. Decreasing the value of the attribute below 180 may result in duplicating measurement files. Decreasing this value can also increase network traffic due to more frequent data polls from OMU. Restart of PMGeneric process iis necessary after this param change: fshascli -rn /PMGeneric Impact to Operator: Key Counter measurement is available to NetAct 3 minutes later Impact to End user: No impact

4.2.100 Cell Availability affected due to CCH DSP resets



Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Stability, Cell Availability, Unit Restarts Attached PRs: 23098ESPE06, NA04882888, NA04845238, NA04806182, NA04923784, NA04882880 Probability: Permanent Description: The CCH DSP reset happens as the DSP Platform time out occurs when waiting for response for a signal that was sent to RNC_CELL process. The response from the RNC_CELL process does not come due to infinite loop caused by corruption of LCH data structure. Solution / Workaround: No workaround Impact to Operator: Cell availability Impact to End user: Call drops for UEs using common channels.

4.2.101 Alarm 1078 indicating PROCESS EXCEPTION after CS call setup failure

Problem report: NA04917877 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If CS call setup fails during state transition from Cell_FACH to Cell_DCH and there was a PS RB which was earlier mapped to HSDPA or HSPA, then RNC could not handle the next CS call setup attempts correctly and after several failures, it finally makes process exception. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success Impact to End user: No impact

4.2.102 Retry of Cell_DCH state transition with lower bitrate is not done correctly



Severity: A - Critical Customer Impact: Capacity & Performance, PS call setup success Attached PRs: - Probability: Permanent Description: Problem was that during Cell_FACH to Cell_DCH state transition, Transport Resource Manager (TRM) rejected the request from RRC because of shortage of DMCU resources, but RRC did not retry with lower bitrate. Instead it rejected the ongoing state transition which can be seen as increase in counter M1022C13 (PS_SETUP_FAIL_DMCU_INT). Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: PS call setup success Impact to End user: No impact

4.2.103 HSDPA retainability below 60%

Problem report: NA04875477 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call completion Success. Attached PRs: - Probability: Permanent Description: In the message which Layer 3 sends to Transport Resource Manager for HSDPA user information, wbts_id is sent. Corresponding to that Wbts id an entry is created in the data table and a new HSDPA hand is created. The root cause of the problem is this: Entry for the HSDPA hand corresponding to that WBTS id already exists in the data tables at Transport Resource Manager but the hand doesn't exist.The library then throws the error and Layer 2 doesn't send any acknowledgment to Layer 3 Solution / Workaround: No workaround Impact to Operator: Call drops Impact to End user: Call drops

4.2.104 Direct RRC (DRRC) failures to HSDPA layer increasing RRC Access Failures due to RADIO



Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04848538, NA04907348 Probability: Permanent Description: Problem was that Direct RRC (DRRC) connection setup failures to HSDPA layer increased in the edge of cells when the transmission power of target cell was high due to HSDPA transmission and UE reported low Ec/No values. In this case new DL initial transmission power value was calculated to be too low because Ec/No value of the source cell need to be used since target cell value is not available. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success (DRRC) Impact to End user: No impact

4.2.105 DMCU failed to come up after RN5.0 PP2.11

Problem report: NA04882831 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, Unit Startup Attached PRs: - Probability: Permanent Description: This DMCU startup failed case only happen to the feature upgraded DMCU based on CDSP-DH card which is under MX622 in some special condition. The root cause of this problem is that higher level resource records are inconsistency with physical resource. Solution / Workaround: No workaround Impact to Operator: Stability: Unit startup Impact to End user: No impact

4.2.106 15th HS-PDSCH code not allocated if 72 HSPA Users Per Cell feature is enabled

Problem report: 28758ESPE05 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4


Severity: C - Minor Customer Impact: Capacity & Performance, Data throughput Attached PRs: NA04910029 Probability: Permanent Description: 15th HS-PDSCH code could not be used in case 2 or more HS-SCCH channels are allocated although HSPA 72 users is activated and dynamic HS-SCCH channel usage of HSPA 72 users feature should allow 15th HS-PDSCH code. Solution / Workaround: Use only 1 HS-SCCH code in cell Impact to Operator: Not able to use full HSDPA capacity in cell in case of only user in cell. Impact to End user: Not able to use full HSDPA capacity in cell in case of only user in cell.

4.2.107 During call release GTP tunnel remains hanging

Problem report: NA04904002 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, RRC Success Attached PRs: - Probability: Permanent Description: During Cell_PCH to Cell_DCH state transition call release is initiated. RRC cancels on-going Cell_PCH to Cell_DCH transition and sends request to TRM (Transport Resource Manager) to release L2 resources for all DCHs including signalling DCH also. Instead of waiting response from TRM, RRC starts Call Release procedure and sends request to TRM to release GTP tunnel. Because of the previous request TRM is already stopped and does not release GTP tunnel and it remains hanging. Solution / Workaround: No workaround Impact to Operator: RRC Success Impact to End user: No impact

4.2.108 SIB2 is transmitted even URA_PCH is not used

Problem report: 84356ESPE02 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor


Customer Impact: Operation & Maintenance, Operability Attached PRs: 84424ESPE02 Probability: Permanent Description: SIB2 is transmitted even URA_PCH is not used. If RNC does not support UE moving to URA_PCH state which is indicated by “MaxCellReselections”,parameter of RNC, then RNC is wrongly transmitting SIB2 in cells. Solution / Workaround: No workaround Impact to Operator: SIB2 is transmitted even URA_PCH is not used. Impact to End user: No impact

4.2.109 MXU problem leads other units to go faulty or restart too

Problem report: NA04806618 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Stability, Unit restarts Attached PRs: - Probability: Permanent Description: MXU startup fails and seems to be faulty. Corruption found in UACFIL records and initial patching was not successful causing WO-EX OMU to go down too. Solution / Workaround: No workaround Impact to Operator: Stability: Unit restarts Impact to End user: No impact

4.2.110 Cell_PCH state counters increase since Cell_PCH transition happens even MsActivitySupervision is 0

Problem report: NA04906643 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, KPI report showing increment on counters for PCH (M1006C48) Attached PRs: -


Probability: Permanent Description: Cell_PCH transition happens even if MsActivitySupervision=0. The Cell Update message comes for a UE in CELL_FACH state, which does not support CELL_PCH state (MSActivitySupervision parameter to 0, this parameter disables Cell_PCH state). The UE state was set as Cell_PCH in the cell_update_cnf message Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Statistics / counters KPI report showing increment on counters for PCH (M1006C48) Impact to End user: No impact

4.2.111 WB-AMR CS over HSPA setup failure after state transition from FACH

Problem report: NA04904587 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success on CS over HSPA Attached PRs: - Probability: Permanent Description: The problem occurred during a WB-AMR CS over HSPA setup from FACH state. After setup, CPC is activated for UE. Immediately after setup, a reconfiguration is triggered to reconfigure the signalling radio bearers of the radio link controls. Unfortunately, UE then disables the CPC feature although the feature is still active within the network. This problem results in a mismatch between the state of the UE and the state of the network regarding the CPC feature as UE has its CPC feature deactivated. Operator can experience a slight drop in terms of call completion success concerning AMR over HSPA and UE loses the CPC feature hence its battery life can be slightly diminished. Solution / Workaround: No workaround Impact to Operator: Call Completion Success on CS over HSPA Impact to End user: No impact

4.2.112 Access restrictions are not applied in the SIB3 when changed by the operator



Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: The SIB3 encoding procedure is wrongly filling the DSAC related info when the system info update request comes immediately after the operator has changed the DSAC. But later the system information update requests that come on access restriction time supervsion expiry are being handled fine. Solution / Workaround: No workaround Impact to Operator: DSAC restrictions not applied Impact to End user: DSAC restrictions not applied

4.2.113 Alarm 7771 is visible for WCEL blocked by user

Problem report: NA04896738 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: When WBTS recovery is done, alarm for faulty WCEL under the recovered WBTS should not be set if WCEL state is other than working and powersaving. So in case of BL-UN state, alarm should not be set. RNW configuration manager should set 7771 alarm in case cell is deleted from BTS. Alarm system should not raise alarm in case cell state is BL-UN after restart. Solution / Workaround: No workaround Impact to Operator: Alarm 7771 is visible for WCEL blocked by user Impact to End user: No impact

4.2.114 Unneccessary delay of sending iur rl addition request



Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: In case of IUB link overload, RNC internally reject Dedicated measurment initiation requests. But there was unnecessarily delay in handling the overall scenario and hence caused delay in Radio link addition procedure on Serving RNC side. in case of IUB link overload, Rejection indication for dedicated measurements initiation request sent by IUB interface protocol S/w to RRC was not handled properly. Therefore this caused unnecessarily delay at RRC till the related timer expired and further handling could take place. Hence some changes are required in Dedicated measurement initiation rejection indication in NBAP protocol S/W. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance : Call completion success Impact to End user: Call can drop or at least affect on call quality.

4.2.115 Incorrect display of HSDPA calls on BTS Connection Resource

Problem report: NA04881267 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics Attached PRs: - Probability: Permanent Description: RNC is sending wrong statics information about per cell per UE for Signalling Link in cell DCH state if singnaling link is on HSUPA. This problem was occurred because RNC static counter for SL was updated twice when Signalling link was on HSUPA. Counter update happened one for E-DCH and other for DCH. Solution / Workaround: No workaround Impact to Operator: Statistics Impact to End user: No impact

4.2.116 Call drop in SHO for CS over HSPA


Problem report: NA04901117 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, call completion success rate Attached PRs: NA04899619, 28876ESPE05 Probability: Permanent Description: Problem was related to implementation of RAN1644: Continuous Packet Connectivity (CPC) There was a problem in Rel-8 specific ASN.1 encoding procedure and Dtx-drx-TimingInfo was not sent in Active Set Updated for Rel-8 UEs while doing Soft Handover for CS over HSPA resulting call drop. Solution / Workaround: No workaround Impact to Operator: Call completion success rate Impact to End user: Call Drop

4.2.117 SRB on DCH/HSUPA 2ms and PS streaming call on HSPA allocated which is invalid transport channel combination

Problem report: 59553ESPE01 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: New feature/functionality, Call setup success Attached PRs: - Probability: Occasional Description: Problem occurs when it is requested full HSPA (F-DPCH) resources for SRB and PS-RT service on CELL_FACH - CELL_DCH state transition scenario. Then if usage of F-DPCH is disabled in cell and it is enabled usage of E-DCH 2 ms TTI, it happens that incorrect transport combination of SRBs on HSUPA and PS-RT on HSPA with 2ms E-DCH TTI is allocated, which is not allowed transport channel combination. Solution / Workaround: Workaround is to enable F-DPCH usage in cell or if F-DPCH is not enabled, then also usage of E-DCH 2ms TTI usage shall be disabled. Impact to Operator: Increased PS-RT setup failure rate on HSPA. Impact to End user: Instead of getting PS-RT allocated on HSPA, it is allocated on DCH/DCH and lower data rate is achieved.


4.2.118 Boot proms update execution failed

Problem report: NA04859333 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: During boot update, WD MML shows "PREVIOUSLY GIVEN COMMAND IS STILL IN PROGRESS". It means that the previous ZWDI/R command is still ongoing. Solution / Workaround: Restart process family CBYPRB (0x55E). Impact to Operator: Operator cannot update boot SW and inquire boot versions (ZWDI/R commands). Impact to End user: No impact

4.2.119 Iu connection towards CS CN fails occasionally due to incorrect MCC and MNC values sent to CN

Problem report: NA04909138 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: Problem was that RNC sent incorrect RNC ID in the Initial Direct Transfer to CN occasionally when new Iu connection towards CS CN is tried to be established during ongoing PS call. Incorrect RNC ID value was due to uninitialized PLMN ID value stored in RNC. Storing of this uninitialized PLNM ID value is more likely to happen when F-DPCH is allowed (there is SRB on HSPA configured in UE). RRCPRB stores incorrect PLMN ID after PS call on HSPA setup, and it is used when the next Iu connection is tried to be established for the same user. As a result, this new Iu connection establishment towards CS CN fails in very early phase of setup procedure but NRT call continues to work as expected. So this impacts Location Update or new CS call setup. Solution / Workaround: No workaround


Impact to Operator: Other: Location update failures Impact to End user: No impact

4.2.120 Occasional MTC call failure due to failure in signalling connection release

Problem report: NA04888081 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: Problem was that RNC does not release signalling connection for the CN from the UE, if CN sends disconnect indication to RNC in response to Initial Direct Transfer without sending the RANAP PDU including the Iu Release Command. This problem scenario is seen only with 3rd vendor CN but impact is severe since as a result, MTC calls are not successful for the end user until user initiates a call. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success Impact to End user: MTC ist not possible.The subscriber is reachable again, after he has set up a call.

4.2.121 HSPA data break with RN5.0 MP3

Problem report: NA04919179 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: NA04929259 Probability: Permanent Description: After RNC upgrade to RN5.0 MP3 there was zero throughput after Inter-RNC HO. During relocation, for the PS NRT, HSDPA peak rate was not getting calculated properly. This in turn led to the zero throughput. Solution / Workaround: No workaround Impact to Operator: Zero throughput for NRT users and traffic volume


Impact to End user: Zero throughput for HSPA users

4.2.122 Spontaneous SP RSMU restart

Problem report: NA04880877 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Stability, Unit Restarts. Attached PRs: - Probability: Permanent Description: a configuration change was done resulting that all HSPA traffic is moved to CDSP-DH cards and CDSP-C cards will serve DCH traffic only. In a transition period, when only few "HSPA" pool CDSP-C cards DSPs exists, there is a possibility to exceed maximum amount of simultaneous service relocations that can be handled at once. Relocations are related to so called HS Cell Home services which will be packed to smaller and smaller DSP amount when "HSPA" pool DSP amount decreases. Solution / Workaround: No workaround Impact to Operator: SP RSMU restart / alarm 1258 seen Impact to End user: No impact

4.2.123 PS service abnormal after NPGEP switchover with FCD option

Problem report: NA04910455 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04908705, NA04881550 Probability: Permanent Description: In NPGEP switchover with forced-option, current implementation is vulnerable to timing of recovery systems unit state updates to library. This means that in FCD switchover situation unit state in library is not what unit handling program block expects. This causes now that FCD switchover does not trigger call resource release operations as it should. Due to that PS calls are not possible through the NPGEP. Solution / Workaround: WO NPGEP unit restart


Impact to Operator: PS call through the NPGEP could not be made. Impact to End user: Failed PS call

4.2.124 Wrong counter values updated when Radio link reconfiguration request is internally rejected by RNC due to IUB link overload

Problem report: NA04875981 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Permanent Description: RNCs IUB protocol is rejecting Radio link reconfiguration request with incorrect failure reason in case of IUB link overload. As a result incorrect counter M1001C83 (RAB_STP_FAIL_CS_VOICE_RNC) the number of RAB setup failures caused by RNC for CS voice were updated and problem is caused. In overload case, the failure reason should be counter M1001C81 (RAB_STP_FAIL_CS_VOICE_BTS) the number of RAB setup failures caused by BTS for CS voice. While internally rejecting any incoming request and the corresponding changes have been done in RNCs IUB protocol SW NBAP. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance : Statistics / counters Impact to End user: No impact

4.2.125 Transport resource manager was not configuring PDCP when PDU size got changed in Serving cell change scenario

Problem report: NA04907843 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: Transport resource manager was not configuring PDCP when PDU size got changed in Serving cell change scenario.


This problem was caused because in SCC scenarios PDCP was never being configured before but RRC now can change PDCP information when PDU size changes. This leads to configure PDCP again in SCC scenarios also. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Data throughput Impact to End user: No impact

4.2.126 No fractional DPCH calls after disabling QoS Aware scheduling feature

Problem report: NA04842153 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: RNW configuration manager restricted delivery of parameter FDPCHenable to Handover Control Program Block when licence QoS Aware HSPA Scheduling is OFF. This is incorrect behaviour and leads mismatch value in Handover Control Program Block and UE-specific radio resource management program block. Correction required in RNW configuration manager to remove the dependency of QoS Aware HSPA Scheduling licence on the delivery of parameter FDPCHenable. Solution / Workaround: No workaround. Impact to Operator: FDPCH calls are not possible after disabling QoS Aware scheduling feature. Impact to End user: FDPCH calls are not possible.

4.2.127 Boot prom updating printout changed to be line with real updating situation

Problem report: NA04860501 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description:


When updating the boot proms, MML printout "COMMAND EXECUTED" even there has happened timeout in message waiting and boot update was aborted. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact

4.2.128 Service request nack from NRM PRB for CS over HSPA

Problem report: 24171ESPE07 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Call setup success Attached PRs: - Probability: Occasional Description: Blind IFHO fails when AMR CS voice call is established. Then Iub connection is removed. After this, recovery takes place. It includes addition of new Iub connection but L3 does not resend full configuration to the RAB. RAB becomes unusable without valid configuration. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Call Setup Success Impact to End user: CS voice call establishment fails.

4.2.129 PS call setup failure if DRRC is perfomed during Cell_FACH to Cell_DCH state transition and Iub transport is congested at the same time

Problem report: 85913ESPE02 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: Packet call setup failure if DRRC is perfomed during Cell_FACH to Cell_DCH state transition and Iub transport is congested at the same time. After DRRC is performed in state transition from Cell_FACH to Cell_DCH and transport congestion is faced, the UE radio resource manager (UER) in the RNC shall make its retry on the original source cell. This is


ok, but the HSDPA serving cell-id is not reseted correctly, which causes the base station resource manager to reject the state transition and the re-try of call setup fails. Solution / Workaround: No workaround Impact to Operator: Occurence of this problem is rare. Problem scenario happens only when layering is used and Iub transport congestion is faced. Impact of this problem is packet call setup failure which can be seen as increase in following counters: -M1022C9 PACKET CALL SETUP FAIL DUE TO AC FOR INTERACTIVE -M1022C10 PACKET CALL SETUP FAIL DUE TO AC FOR BACKGROUND, Also follwing KPIs are impacted -Packet Session Setup Success Ratio -HSDPA Setup Success Ratio from user perspective -HSUPA Setup Success Ratio from user perspective Impact to End user: No impact

4.2.130 UE cannot access a cell if operator configures ADJS/ADJI to SIB11 bis and uses HCS

Problem report: NA04894418 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Cell availability Attached PRs: - Probability: Permanent Description: System Information is corrupted and UE cannot access a cell. This problem is seen when operator configures ADJS/ADJI to SIB11 bis and uses HCS. RNC corrupts SIB11 when operator configure all ADJI or all ADJS to SIB11bis. This problem can be seen in following 2 cases: 1) if operator configures all ADJS to SIB 11bis 2) if operator configures all ADJIs to SIB 11 bis and uses HCS. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Cell availability Impact to End user: No impact

4.2.131 RNW Configuration Manger is not setting bitmask os SIB3 for parameter Shcs_RAT when HCS is not in use



Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Operation & Maintenance, Operabillity Attached PRs: NA04906179 Probability: Permanent Description: According to RAN1138 and TS25.304 Shcs_RAT parameter should be transmitted from RNC into system information even if HCS is not used but currently this parameter is tranmitted only when HCS is in use. Solution / Workaround: No workaround Impact to Operator: This parameter is used by UEs for cell selection and re-selection in idle mode. Impact to End user: No impact

4.2.132 Unlocking HSPA-WCELs not able on any Dual-Iub site

Problem report: NA04903992 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04886894 Probability: Permanent Description: When the HSUPA feature is activated in a cell, and HSUPA configuration is missing from ATM pipe, RNW configuration manager does not allow the unlocking of the HSUPA enabled cell even if this ATM pipe is used only for AMR and signaling. RNW configuration manager will be corrected to not to perform specific HSUPA VCC checks. This is required to support the Dual Iub feature. Solution / Workaround: No workaround Impact to Operator: Operability Impact to End user: No impact

4.2.133 Some F-DPCH parameters cannot be modified if QoS aware HSPA scheduling was disabled



Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Certain F-DPCH parameters could not be modified if QoS aware HSPA scheduling feature was disabled. A specification fault is resulting incorrect relationship between F-DPCH parameters and QoS aware HSPA scheduling licence. Due to this problem, following F-DPCH related parameters were greyed in Object Browser and so they could not be modified: RNC/WBTS/WCEL FDPCHCodeChangeEnabled (F-DPCH code change enabled) RNC FDPCHAndSRBOnHSPATC (F-DPCH and SRBs on HSPA per TC) RNC/WBTS/WCEL PtxFDPCHMax (F-DPCH maximum transmission power) RNC/WBTS/WCEL PtxFDPCHMin (F-DPCH minimum transmission power) RNC/WBTS/WCEL PtxOffsetFDPCHSHO (The power offset of F-DPCH for SHO) RNC/WBTS/WCEL TPCCommandERTarget (TPC command error rate target) RNC FDPCHAllocMinInterval (Minimum interval between F-DPCH allocations) RNC/WBTS/WCEL CIRForFDPCH (Carrier to interference ratio for F-DPCH) Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact

4.2.134 Several DSPs in restart loop

Problem report: NA04882625 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, Unit restarts Attached PRs: - Probability: Permanent Description: Several DSPs in restart loop. One program module could not get enough memory. Solution / Workaround: Restart DMPG Impact to Operator: DSP restart Impact to End user: No impact


4.2.135 Counter M1002C416 HS Access FAIL BTS incremented unnecessarily

Problem report: NA04835192 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / Counters Attached PRs: - Probability: Permanent Description: When initial HSDPA or HSPA allocation fails due to BTS congestion, the UE radio resource manager in the RNC informs failure cause bts_failure_c to all base station resource managers in the current active set which increments counter M1002C416 HS Access FAIL BTS unnecessarily for all sites when the counter shall only be incremented for the congested site. Solution / Workaround: No workaround Impact to Operator: Counter M1002C416 HS Access FAIL BTS incremented unnecessarily. Impact to End user: No impact

4.2.136 Counter M1002C526 SETUP_FAIL_EDCH_BTS_BGR incremented unnecessarily

Problem report: NA04897052 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Operation & Maintenance, Statistics / Counters Attached PRs: - Probability: Permanent Description: Due to missing implementation, the UE radio resource manager (UER) in the RNC informs failure cause bts_failure_c to all base station resource managers (BRM) in the current active set which increments counter M1002C526 SETUP_FAIL_EDCH_BTS_BGR unnecessarily in all sites when the counter shall only be incremented for the congested site and failure cause default_c shall be used to other BRMs. Solution / Workaround: No workaround Impact to Operator: Counter M1002C526 SETUP_FAIL_EDCH_BTS_BGR incremented unnecessarily.



4.2.137 Small degradation in HSDPA Serving Cell change Success rate after the CPC activation

Problem report: NA04911956 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Handover success Attached PRs: - Probability: Permanent Description: Very small degradation in HSDPA Serving Cell change Success rate after the CPC activation. FDPCH configuration at RNC was incorrectly done leading to SCC failure and possible call drops and CUs from UE. Solution / Workaround: No workaround Impact to Operator: SCC success rates and KPI problems. Impact to End user: SCC failures, call drops and impacting KPIs

4.2.138 Call drop due to SHO failure resulting increase of Counter M1022C20 PS_SETUP_FAIL_OTHER_BGR

Problem report: NA04894314 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: NA04897519 Probability: Permanent Description: Compressed mode is active for the UE and Handover Control entity triggers SHO (radio link replacement) procedure for the UE. UE specific Radio Resource management entity requests CM preparation on the new radio link to be added which fails from Base station resource manager. UER specific radio resource management is not able to handle the failure correctly, after which it doesn’t handle any further requests from other entities and UE is dropped to FACH. Solution / Workaround: No workaround


Impact to Operator: Call Completion Success Impact to End user: No impact

4.2.139 Cell is not operational due to WCEL initialization failure

Problem report: NA04909424 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, cell availabilty Attached PRs: NA04911061 Probability: Permanent Description: Invalid DL spreading code value was tried to be used for DL common channel. Because of missing error handling functionality it was possible that illegal DL spreading code was allocated for DL common channel during cell start-up. This WCEL initialization failure resulted that cell was not operational. Solution / Workaround: Temporary change in SCCPCH code amount and BTS reset is needed to recover from this situation Impact to Operator: Cell not operational Impact to End user: No impact

4.2.140 NP2GE-B PQCPU diagnostic problem

Problem report: 59738ESPE01 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability Attached PRs: - Probability: Occasional Description: PQCPU part of the diagnostics routine sometimes fails on NP2GE-B unit due to the switch between 100M full duplex mode and 10M half duplex mode. Solution / Workaround: Operator may execute PQCPU diagnostics several times. If it success once, then the plug-in unit is ok. Impact to Operator: Plug-in Unit diagnostics may fail randomly (PQCPU sub-diagnostics part)


Impact to End user: No impact.

4.2.141 WDU and SCSI LCK and WDU broken, no alarms raised

Problem report: NA04848919 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: SCSI error from one WDU is informed to file system so the other WDU is locked. But I/O management process does not set any alarm in such situation. Solution / Workaround: Change the WDU which has no LCK info to non-WO state and then back to WO-EX state, then that WDU will be used by system again. Impact to Operator:Operator may not notice about such situation when only one WDU is used by system. Impact to End user: No impact

4.2.142 The cyclic restart of spare NPGEP

Problem report: NA04871171 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, Unit Restarts Attached PRs: - Probability: Permanent Description: Message congestion happens when data provider of M235, M236 and M238 call multiple times of DMX ID register function via SCZLIB, which causes the synchronization problem between WO and SP NPGEP. Solution / Workaround: Quit running M235/M236 and M238 concurrently Impact to Operator: SP NPGEP unit would restart spontaneously and cyclically whenever measurement report is to be produced. Impact to End user: No impact


4.2.143 Unexpected NBAP RL deletion with CPC call

Problem report: NA04882253 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: The inactivity timer inact_cpc_bat_opt has been set to 0. UE is thus expected to be transfered to FACH immediately after receiver low activity indication. RRC only deletes the user plane and leaves SRB on HSPA. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Data throughput Impact to End user: UE battery life is diminished and some UE might get stuck.

4.2.144 Mute calls increase/data througput low when RNC has no cable connection to some unit related to external IPOA.

Problem report: NA04895480 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: 75104ESPE02 Probability: Permanent Description: State of external IPOA inconsistent in the system and calls are tried to connect into that IPOA without cable. Solution / Workaround: Plug in cable, delete and recreate that external IPOA. Impact to Operator: Degraded call quality Impact to End user: Call fails


4.2.145 DHCP server configuration delete fails

Problem report: NA04859424 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: - Probability: Permanent Description: After configured DHCP server options with ZQ9N, it cannot be deleted because the default IP address 0.0.0.0 is forbidden when configuring. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance Impact to End user: No impact

4.2.146 Ping lost due to collision between RLC resume and suspend

Problem report: NA04891732 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: If RLC resume command and RLC suspend command are sent one after other then it was seen that sometimes the RLC receives the suspend command for the RB before receive the RLC resume command from the upper layers and RNC RLC could not handle the situation correctly which causes ping lost because later RLC could not be resumed to active state correctly. Solution / Workaround: No workaround Impact to Operator: Data Throughput Impact to End user: No impact

4.2.147 Decreased HSDPA throughput in a cell


Problem report: NA04897958 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: NA04897741, NA04910029 Probability: Permanent Description: There was some HS-PDSCH codes left hanging in RNC's BTS resource manager internal info and that disturbed dynamic HS-PDSCH code allocation so that the full HSDPA code capacity could not be used in cell. Solution / Workaround: CoCo detach/reattach is needed to reset RNC's BTS resource manager code resource tables when this problem is active. Impact to Operator: Not possible to use full HSDPA capacity in cell - effects HSDPA DL throughput Impact to End user: Effects HSDPA DL throughput

4.2.148 Process exceptions during state transition from Cell_FACH to Cell_DCH in case of transport congestion

Problem report: NA04897732 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04900599 Probability: Permanent Description: After numerous retries for state transition, the UE radio resource manager in the RNC (UER) makes a process exception when its internal error cause structure becomes full. The process is not able to downgrade the requested HSDPA uplink bitrate correctly in case of congestion which causes it to try the same configuration over and over again until the process exception happens. Solution / Workaround: No workaround Impact to Operator: Decrease in call setup success Impact to End user: PS-NRT call setup not going through


4.2.149 NBA PRB hanging after "nbap_cell_delete_req" message received on RU20 MP2

Problem report: NA04909243 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Cell availability Attached PRs: - Probability: Permanent Description: NBA PRB hanging after "nbap_cell_delete_req" message received on RU20 MP2 SW. NBA does not clean its procedure entry for a cell if BTS send error indication for any of the ongoing cell procedure and hence no further cell procedure is admitted by NBA. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Cell availability Impact to End user: No impact

4.2.150 Latency and packet drop increased in network

Problem report: NA04866902 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Data throughput Attached PRs: NA04909630 Probability: Permanent Description: If RLC size changes for the RB in downlink during state transition from Cell_DCH to Cell_FACH but UE makes cell reselection and sends Cell Update to UTRAN before completing the state transition procedure and sending the L3 acknowledgement for the procedure, UTRAN forgets about the RLC size change in DL and handles only Cell Update procedure. This causes ciphering mismatch in DL for user plane RB which had RLC size change since UE uses the new HFN while UTRAN still uses the old value. Solution / Workaround: No workaround. Impact to Operator: Capacity & Performance, Data throughput Impact to End user: No impact.


4.2.151 HSPA over Iur UL RL Reconfiguration failure after AMR call release resulting PS call drop

Problem report: NA04885447 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success / HSPA over iur Attached PRs: - Probability: Permanent Description: RL reconfiguring failure during AMR call release in DRNC resulted PS call drop. Problem was that existing UL DCH return channel is unnecessarily checked against RNP parameter HSDPAMaxBitrateUL in DRNC while AMR call was released. This can result to abnormal call/SHO branch termination. Problem is related to HSPA over Iur. Solution / Workaround: Is to keep RNP parameter "HSDPAMaxBitrateUL" in same value in all cells. Impact to Operator: Capacity & Performance: Call completion success / HSPA over Iur Impact to End user: PS call drop

4.2.152 SAB signalling throughput goes down leading cell state set as blocked periodically

Problem report: NA04865884 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: SAB signalling throughput goes down when HSDPA/HSUPA state is enabled/disabled on cell with cell lock/unlock procedure causing that RNC BTS resource manager is not acting correspondingly and it still continues supervision for measurements which has been already stopped. Solution / Workaround: Cell remove/cell addition since cell block/cell unblock is not enough. Impact to Operator: SAB signalling throughput will decrease. Impact to End user: No impact.


4.2.153 Alarm 7771 was activated during cell shutdown

Problem report: NA04900214 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Alarms Attached PRs: - Probability: Permanent Description: While cell was blocked and being shut down, unnesessary recovery actions were initiated when call attempts were still received for that cell. This fault happened because cell shutdown procedure has been modified inside RNC and the so called "blocked recovery" functionality was not considered enough during that modification. So this "blocked recovery" functionality triggered unnesessary recovery actions too early. Solution / Workaround: No workaround Impact to Operator: Unnesessary alarm because of unnesessary recovery actions. Impact to End user: No impact

4.2.154 Occasional call drop after relocation from ADA to RNC due to failure in CFN calculation

Problem report: NA04880876 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: - Probability: Permanent Description: After relocation from ADA to RNC due to incoming CS call, when Compressed Mode is started in anchoring, then Call Control did not calculate the CFN correctly during the Compressed Mode procedure which caused later overlapping CFN to be sent to BTS when new configuration was given to BTS. Solution / Workaround: No workaround Impact to Operator: Call Completion Success Impact to End user: No impact


4.2.155 DMPG load increased due to DSP connection was lost on RNC2600 environment

Problem report: NA04882761 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, high PQ load Attached PRs: - Probability: Permanent Description: During system startup some service provider might be too busy to provide service in some particular period, such as HW equipment management service could be unavailable for a short moment and will be available again in a very short time. HW equipment data is necessary for messaging system to create DSP connection, which will not be created on MX622 HW to prevent overloading MXU units. DSP connection will be missed from messaging system if MXU HW type cannot be identified successfully and DSP messages will be routed by DMPG, which will increase DMPG load. Solution / Workaround: No workaround Impact to Operator: Stability: High PQ load Impact to End user: No impact

4.2.156 CS call setup failure after incoming I-BTS sharing relocation

Problem report: NA04887483 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: If there is standalone signalling DCH during UE involved relocation from ADA to RNC and slow signalling DCH in use, then standalone signalling DCH can be changed to fast signalling DCH bitrate during the handover procedure and later downgraded after the relocation and CS setup successfully. This will improve the transmission of SRB messages to be sent to UE faster in smaller TTI so that RBSetup is not delayed for long time in the RLC buffer when CS setup is tried. Solution / Workaround: No workaround


Impact to Operator: Call Setup Success Impact to End user: No impact

4.2.157 Alarm 70159 increased due to OMS subsystems EmiCMOS and DXDIAG problems

Problem report: NA04782659 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: Operating on OMS for longer time user will observe a lot of coredump files in OMS directory /var/crash. Those are related to coding errors for threading mechanisms and glibc infrastructure provided by 3rd party software.This error may cause problems with OMS Fault Management GUI and Event Management which cannot be operated. Solution / Workaround: No workaround Impact to Operator: Problems can appear for OMS Fault Management GUI and Event Management which cannot be operated. Impact to End user: No impact

4.2.158 Unexpected RL deletion during F-DPCH call on IP IUB Node-B

Problem report: NA04793845 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, call completion success Attached PRs: NA04821699 Probability: Permanent Description: When FDPCH is configured, during mobility scenarios there is call drop and cell updates from UE resulting in KPI impacts for operator and call drops from end user. Solution / Workaround: No workaround Impact to Operator: KPI impacts


Impact to End user: Call drops

4.2.159 Increase the counter M1001C6 (RRC_CONN_STP_FAIL_RNC) number of RRC setup failures caused by RNC internal reason.

Problem report: NA04881469 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success/ Effects to RRC or RAB setup. Attached PRs: NA04892044, 23945ESPE06, NA04903155 Probability: Occasional Description: Problem was that failure in DMPG resource management could result to hanging physical resources regarding IP based IU-CS AMR call service. Problem was possible in case of high DMPG load and finally resulted to situation where high amount of RAB and RRC setup failures due to RNC internal reasons. The counter M1001C6 (RRC_CONN_STP_FAIL_RNC) number of RRC setup failures caused by RNC internal reason. Solution / Workaround: NA Impact to Operator: Capacity & Performance - Call Setup Success / RRC_CONN_STP_FAIL_RNC Impact to End user: Possible call setup failure

4.2.160 Unable to access external storage media on RNC's

Problem report: NA04859056 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: - Probability: Permanent Description: When USB stick is broken, EDU will miss to closedir in some situation, which leads that EDU open too much files therefore it can't open any dir anymore. ZIWX USB will always fail. Solution / Workaround: No workaround


Impact to Operator: Operation & Maintenance, Operability Impact to End user: No impact

4.2.161 Call setup failure after LU fails due to RL failure

Problem report: NA04907039 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: - Probability: Permanent Description: After SRNS relocation from another RNC, if UE initiates Location Update procedure then it can fail in situation when UE looses radio connection before the first DL message for CS CN has been sent to the UE. If UE repeats the LU procedure then the reattempt was then not handled correctly in RNC and the LU message was lost. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success Impact to End user: No impact

4.2.162 RRC rejections due to IUB caused by NBAP OLC functionality with narrow Iub configuration

Problem report: NA04875407 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call setup success Attached PRs: - Probability: Permanent Description: Problem was that after RNC NBAP BTS overload control was not taking into account situations where customer is using very limited Iub configuration resulting that some sites were suffering from total AAL2 signalling congestion in Iub and call drop rate could increase to 100% is those sites. In RN5.0 SW levels before PP1.3, there was a problem in NBAP OLC implementation that if there was no response from BTS (timeout from RL setup procedure), the used NBAP OLC limit was decreased directly to minimum value. As a result NBAP OLC limited unnecessary


C-NBAP signalling which caused delay and decrease of call setup success rate in case normal Iub configurations. Correction to above mentioned problem was to decrease used NBAP OLC limit only by one step in case of timeout from BTS. However, after this correction, NBAP OLC was allowing too much request in case of very limited Iub configurations. This incorrect NBAP behavior in previous RN5.0 SW levels is regarded as main reason why NBAP OLC functionality was working better in RN5.0 PP1.2 and older SW with very limited Iub configurations. Solution / Workaround: No workaround Impact to Operator: No full Iub congestion situation resulting very high call setup failure rate. Impact to End user: Call setup not succeed

4.2.163 Illegal values from OLPC (outer loop power control) measurement

Problem report: NA04179653 Exists in: RN3.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: - Probability: Occasional Description: The EbNo values from outer loop power control measurement show illogical values. E.g. the UL_AVERAGE_EBNO counter is much less than 0 for voice connections, and for some packet connection it is close to 0 when divided by UL_AVERAGE_EBNO_DENOM. The original fault is that OLFTOR reports RCPM data only when a call comes in to an empty DMPG. Solution / Workaround: No workaround. Impact to Operator: Illegal values from OLPC measurement. Impact to End user: No impact.

4.2.164 Decreased of DC and MIMO HSDPA call throughput

Problem report: NA04890700 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: A - Critical


Customer Impact: Capacity & Performance, Data Throughput Attached PRs: NA04906655, NA04909321 Probability: Permanent Description: Due to higher HSDPA throughputs (DC & MIMO) the internal flow control parameters were updated. Because of these increased parameter values the throughput calculations were overflowing and causing heavy throughput drops. Two different versions of this fault has been occurring: 1) Throughput is set to very low level after data transmission has started (~64kbit/s). 2) Thoughput per second sets to several Mbit/s, but in ms scale the throughput has saw-tooth behavior. Solution / Workaround: No workaround Impact to Operator: Data Throughput Impact to End user: No impact

4.2.165 RNC Overload Control - Iub Smart Overload/Congestion Control for AAL2SIG

Problem report: NA04895351 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: 84862ESPE02, 85801ESPE02, NA04943619 Probability: Permanent Description: Current RNC Overload Control for Iub transmission is based only on C-NBAP link's configuration, fully relying on network dimensioning to perform correctly. If AAL2 Signalling congestion occurs, it results in 100% RRC and RAB Setup Failures Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Call setup success Impact to End user: Call setup failure

4.2.166 Platform alarm not visible in active alarms or alarm history



Customer Impact: Operation & Maintenance, No platform alarm could be seen from alarm history Attached PRs: - Probability: Permanent Description: Lower level alarm program (ALARMP): it send alarm setting request to Upper level alarm program and handles alarm caused recovery action. Upper level alarm program (ULAPRB): it write alarm into alarm history and active alarm list. Alarm system Upper level program (ULAPRB) get alarm setting message from Lower level program (ALARMP) and normally Upper level program will reply acknowledge. If Lower level program do not get acknowledge in 10 s, it will resend the alarm setting message to Upper level. If sending 10 times setting alarm message but still do not get acknowledge, the Lower level alarm program will not send more setting alarm to Upper level but recovery action can still be taken. Since alarm setting message is not send to Upper level alarm program, alarm could not be seen in alarm history and active alarm both, but recovery action can still be taken. Solution / Workaround: OMU controlled switchover. Impact to Operator: Cannot see platform alarm in alarm history Impact to End user: No impact

4.2.167 PS calls not possible after upgrading to RU20 PP2.11

Problem report: NA04870858 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, Call Setup Success Attached PRs: NA04928574 Probability: Permanent Description: PS calls are not possible after upgrading to RU20 PP2.11. The root cause is when remote SGSN execute ATM OAM Loopback function, RNC doesn't respond the LB cells. As a result SGSN blocks the user plan, but the RNC side is working properly. Solution / Workaround: Deactivate LB from remote SGSN Impact to Operator: Capacity & Performance: Call setup success Impact to End user: PS calls are not possible


4.2.168 Optional SIB optimization improvement PRFILE activation failed

Problem report: NA04903047 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04932806 Probability: Permanent Description: The optional SIB optimization improvement (PRFILE 002:1684) is not working due to internal problem in handling of PRFILE parameter used for activation of this improvement. RNW database process decides the SIB contents based on PRFILE information. RNW database is supposed to receive PRFILE information from Telecom process, but due to software fault, PRFILE information is incorrectly handled and SIB optimization change is not activated even if configured with PRFILE parameter. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance: Operability Impact to End user: No impact

4.2.169 Alarm 70159 was not cleared after cluster restart

Problem report: NA04868422 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Alarms Attached PRs: NA04878254 Probability: Permanent Description: Cluster restart results alarm correlation. Alarm System gets notification about it through alarm 70168. Alarm 70168 requires manual clearing. If it was raised before and hasn't been cleared then at repetitive raise (a new cluster restart) it is filtered out and correlations actions are not initiated. Solution / Workaround: No workaround Impact to Operator: Alarm 70159 (as other alarms with automatic clearing) are cleared after cluster restart. Impact to End user: No impact


4.2.170 Alarms 3344 UX LINK CONNECTION FAILURE cause MXU fault switchover

Problem report: NA04887813 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Stability, Unit Restart Attached PRs: - Probability: Permanent Description: The problem was generated by MXU that was detected to be faulty. Due to SW bug in earlier workaround implementation alarms 3344 UX LINK CONNECTION FAILURE was reported to all the MXUs and they were also interpret as faulty. That workaround were implemented to try to recover the faulty MXU by MXU SWO but in some cases that workaround was dangerous and it caused the faulty MXU to be the WO MXU. Solution / Workaround: No workaround Impact to Operator: Stability: Unit restarts Impact to End user: No impact

4.2.171 SF10E SD4G-A HW block bitstream downgrade

Problem report: NA04887607 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Stability Attached PRs: NA04890116, NA04895805 Probability: Permanent Description: On some cases, the SF10E SD4G-A bit stream included in RN5.0 boot flash image can cause instability to other units due to data corruption (bit errors) in the SFU. This can lead even to system outage. The RN5.0 SD4G-A bit stream (version 129) has smaller timing margins compared to RN4.0 SD4G-A bit stream (version 125), because more logical functions have been added into the FPGA. This new logic means improvements to fault diagnostics that are not critical for normal operation and performance. Solution / Workaround: No workaround


Impact to Operator: Stability: Outage Impact to End user: No impact

4.2.172 Incorrect counter update instead of normal release if HSDPA release due to inactivity after relocation

Problem report: NA04871068 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Operation & Maintenance, Counters Attached PRs: - Probability: Permanent Description: After completion of SRNS relocation in Cell_FACH in the target RNC, if UE gets HSDPA or HSPA allocation in Cell_DCH and UE is moved to Cell_FACH due to inactivity, then RNC does not mark the release of HSPA reason correctly but instead of normal release it indicates marks it as failure due to UE. The counter M1002C539 (REL_EDCH_RL_FAIL_INT) the number of E-DCH releases for interactive class connections due to a radio link failure, an uplink RLC unrecoverable error, or due to the UE not responding to an RRC message sent by the RNC. Problem comes if after SRNS relocation, UE does not answer when UTRAN tries to give new mapping option for the RBs. After that if UE is moved to Cell_DCH, RNC remembers that UE did not answer to one procedure and finally when HSDPA is released, it uses that information to indicate release due to UE. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance, Counters Impact to End user: No impact

4.2.173 RNC Handover failure between ALU-RNC and NSN-RNC

Problem report: NA04875898 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call Completion Success, Handover Success Attached PRs: - Probability: Permanent


Description: If Source RNC prepares Compress Mode patterns during RL setup and triggers UE not involved SRNS relocation before the CM measurements have been activated, then the Target RNC could not handle the soft handover procedure after SRNS relocation correctly because NSN does not support SRNS relocation UE not involved with CM ongoing and if such configuration is used by another RNC, then Target RNC deactivates ongoing compressed mode after completion of relocation procedure. In this case, there was no actual CM measurements started, so Target RNC did not find anything to deactivate but still had those CM information stored, this caused SHO procedures failure after relocation completion. Solution / Workaround: No workaround Impact to Operator: SHO success KPIs impacted Impact to End user: SHO failures might cause call drop

4.2.174 Missing daily 1013 AutoDef SHO measurement files

Problem report: NA04803521 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics & Counters Attached PRs: NA04850630 Probability: Permanent Description: Missing RNC Measurement data during overload situation due to insufficient measurement object buffer size. Solution / Workaround: No workaround. Impact to Operator: Operation & Maintenance, Statistics Impact to End user: No impact.

4.2.175 Packet loss and duplicate packets in NSN RAN

Problem report: NA04675087 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance Attached PRs: - Probability: Permanent


Description: RN5.0 does not support UL DMPG switch and because of that some RLC UL SDUs might get dropped during DMPG switch. Solution / Workaround: No workaround Impact to Operator: Decrease in drop statistics on UL at RLC level Impact to End user: No impact

4.2.176 Occassional call drops due to DSP severe errors 7002001a/006700b1, 700b0005/0, 7002001d/00670010 and 700b0016/0

Problem report: 84399ESPE02 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Call completion success Attached PRs: - Probability: Permanent Description: Due to forced state change to cell_FACH from cell_DCH state there can be data transmission ongoing when state change is done. This could cause situation where DL data is requested from RLC in cell_DCH state but DL data is coming to MAC when state change is already done. DL DCH data size is too large for FACH state to handle and severe errors were reported. Solution / Workaround: No workaround Impact to Operator: KPI values might have impact Impact to End user: Calls might get dropped when forced state change to cell_FACH done.

4.2.177 After adding CS over HSPA in FACH state PS UP data can not go smoothly (several ping lost)

Problem report: NA04908744 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent


Description: After adding CS over HSPA in FACH state, PS UL data can not go smoothly (several ping lost). This happens when a PS-NRT RAB is added on top of CS Voice on HSPA with 2ms tti, UE radio resource manager (UER) in the RNC was not deactivating DL-DRX IE in continous packet connectivity properly. Solution / Workaround: No workaround Impact to Operator: Data Throughput Impact to End user: No impact

4.2.178 HSDPA throughput ramping has increased from 2-3 sec to about 15 sec

Problem report: NA04815118 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, HSDPA tput ramping time Attached PRs: - Probability: Permanent Description: HSDPA throughput ramping has increased from 2-3 sec to about 15 sec. Wrong IFC parameters were calculated by leg control in RSMU and in traffic and transport in EIPU unit. Calculation was not taking into account that AF1 +AF2 type IP traffic are also seen as HSPA traffic. Also maximum value for IFC slow start threshold was in older value 15000. Solution / Workaround: No workaround. Impact to Operator: HSDPA throughput ramping has increased from 2-3 sec to about 15 sec. Impact to End user: HSDPA throughput ramping has increased from 2-3 sec to about 15 sec.

4.2.179 RNC450 to RNC2600 HW upgrade: OMU faulty switchover cause by active OMU restart

Problem report: 57232ESPE01 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Stability, Unit restarts Attached PRs: -


Probability: Occasional Description: Re-organize DMPG/DSP indexing to be same as new delivery RNC2600 when doing RNC450 to RNC2600 HW upgrade then active OMU restart cause OMU faulty switchover. Solution / Workaround: No workaround. Impact to Operator: OMU faulty switchover cause by active OMU restart when doing RNC450 to RNC2600 HW upgrade but upgrade can still be success. There is no effect to KPI. Impact to End user: No impact.

4.2.180 Cell resource counters (M1000) updated incorrectly

Problem report: NA04864012 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Statistics / counters Attached PRs: NA04866787 Probability: Permanent Description: The timer used for periodic cell resource counter updating was lost in ICSU and it was not started again after this. This caused situation that M1000 level counters was not updated any more. Solution / Workaround: No workaround. Impact to Operator: KPIs that are formulated by using cell resource counters (M1000) show invalid values. Impact to End user: No impact.

4.2.181 Plan upload failed with very large network configuration

Problem report: NA04873316 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance Attached PRs: NA04873316 Probability: Permanent Description:


During plan upload if network configuration is very large and XML plan file bigger that 80MB is asked to be compressed, FCMPRS delays the response and take more than 2 minutes times to compress the given xml file. This compression takes too long time resulting timer to expire and plan upload plan operation is regarded to fail. System has quite lower priority for FCMPRS , so in the worst casesit may take more time to reschedule the process. Solution / Workaround: No workaround Impact to Operator: Operation & Maintenance Impact to End user: No impact

4.2.182 Alarm 1239 and DSP restarts (code 80000007) leads to 100% DMPG Load

Problem report: NA04863873 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Call Completion Success Attached PRs: - Probability: Permanent Description: If source RNC does not send Transport channel information during UE not involved relocation, then NSN Target RNC does not configure ciphering correctly for the Transparent Mode RLCs, it instead configures Transparent mode RLCs ciphering as AM RLCs which causes problem to RNC L2. Solution / Workaround: No workaround Impact to Operator: Multiple call drops Impact to End user: Call drop

4.2.183 A2SPs restarting periodically

Problem report: NA04792911 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Stability, Unit restart: A2SP Attached PRs: - Probability: Permanent Description:


A2SP is up and running for some time and CPM's APC will get stucked and cannot be recovered. Alarm 1349 INTER-COMPUTER MESSAGE CONNECTIVITY LOST ON SN+ UNIT is raised and A2SP will be restarted to recover it. Solution / Workaround: No workaround Impact to Operator: Stability: Unit restarts (A2SP) Impact to End user: No impact

4.2.184 Occasional HSDPA throughput degradation after SCC

Problem report: NA04831618 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Capacity & Performance, Data throughput Attached PRs: - Probability: Permanent Description: Problem was that RNC sent sometimes invalid RLC AMD PDU resulting that RLC SDU had extra octets in the beginning of the SDU when UE reassembled it. This invalid user data could lead e.g. TCP packet drop which can cause temporary decrease in HSDPA throughput. Problem was possible with CDSP-DH units when flexible RLC was used in downlink and RLC was configured to use concatenation. Solution / Workaround: No workaround Impact to Operator: Capacity & Performance: Data throughput Impact to End user: Occasionally data throughput decrease

4.2.185 CPU usage increased to ~100% after login to OMS Web UI and selecting some menu entry

Problem report: NA04879402 Exists in: RN5.0 MP2 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Operation & Maintenance, Operability Attached PRs: NA04899746 Probability: Permanent Description:


CPU usage increased to ~100% after login to OMS Web UI and selecting some menu entry, e.g. Application Launcher or Log Viewer. JDK1.6u17 used in OMS had problmes with new Input/Output mechanism (waiting for socket events) which in very rare cases used a lot of CPU. Solution / Workaround: Restart of TomcatPlat process temporarily solved the problem. Impact to Operator: OMS performance can be degraded Impact to End user: No impact

4.2.186 Measurements from random RNCs are being sent to the OSS corrupted

Problem report: NA04887192 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Operation & Maintenance Attached PRs: NA04867327, NA04865858, NA04903156, NA04848443, NA04915291, NA04918034, NA04875278, NA04909471, NA04930315, NA04889253, NA04942203 Probability: Permanent Description: Out of memory kernel error. This resulted in OMS being in unstable state, and not produce expected measurements. Solution / Workaround: No workaround Impact to Operator: Out of memory problem should not occurs anymore. Impact to End user: No impact

4.2.187 Bootprom upgrade during RNW startup caused OMU restart

Problem report: NA04860408 Exists in: RN4.0 Correction Target: RN5.0 MP4 Severity: B - Major Customer Impact: Stability, Outage NA04858802 Attached PRs: - Probability: Permanent Description: The problem was that high-priority process (RDISFS / A0) was using all available CPU time in WO-OMU so that RNW DB manager (RAVIOLI) did not got CPU time to serve the remote DB read requests.


The number of accumulated requests became so high that system ran out of buffers in OMU and reseted the computer. That fault happens only if the boot upgrage is tried to be done too early after system restart when RNW is still under configuration. Solution / Workaround: No workaround Impact to Operator: Stability: Outage Impact to End user: No impact

4.2.188 Increase of PS AFR due to AC

Problem report: NA04889232 Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: A - Critical Customer Impact: Capacity & Performance, Data Throughput Attached PRs: 70161ESPE04 Probability: Permanent Description: Dynamic HSUPA power offset functionality does not note Rel99 UL DCH load in the cell, only the number of E-DCH allocations Solution / Workaround: Dynamic HSUPA power offset load algorithm takes into account the number of HSPA users in the cell and the Rel99 UL DCH load of the cell. When the low bit rate optimized HSUPA power offsets are used for the UE, the maximum total uplink symbol rate of the E-DPDCH(s) of the UE is limited to the value 3840 kbps (2*SF2). Restrict maximum total uplink symbol rate of the E-DPDCH(s) of the UE to the value 960 kbps (1*SF4) with RNP parameter MaxTotalUplinkSymbolRate. Impact to Operator: Increase the HSUPA throughput in the high loaded cells and will cause decrease of HSUPA BLER. Impact to End user: Increase the HSUPA throughput in the high loaded cells and will cause decrease of HSUPA BLER.

4.2.189 Delayed DNS requests caused by RNC leading loss of PS service availability



Exists in: RN5.0 Correction Target: RN5.0 MP4 Severity: C - Minor Customer Impact: Capacity & Performance, Data Throughput Attached PRs: - Probability: Permanent Description: RRC state transition DCH (HSPA) to FACH triggers relocation of resources handling L2 protocols. During such relocation RLC (target) is initiating a RLC reset procedure which is not needed. Solution / Workaround: No workaround Impact to Operator: Loss of continuous availability of the PS services. Impact to End user: Experiencing issues in web-browsing. Sometimes, the pages will not be downloaded.



Disclaimer

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

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

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

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

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

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

Copyright © Nokia Siemens Networks 2011. All rights reserved.

LGF-RNC-2011-10

Documents

Transcript of LGF-RNC-2011-10