WN6 0 MP4 2 SW CN Document

MENU
Change Note Forms

WCDMA BTS
WN6.0 MP4.2
WN6.0 22.12-292_E
MENU
WCDMA BTS CN-id: WN50048

Title: Node B without traffic HSDPA after break transmission Version of the SW-build: WN6.0 22.12-290 Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: NA04941075: Summary of the original problem: HSDPA not working after links break, GRM deletes cell after aal2 breaks down How end user/operator could detect the problem: Disable/enable aal2 link states for less than 10 seconds Description of the fault: Cell was unnecessarily deleted when aal2 links became out of service. Without cells having HSDPA was impossible. Description of the correction: Marking Cell as faulty instead of deleting it when aal2 breaks down, thus while still having cells HSDPA recovery is possible. Corrected Fault Reports: NA04941075 Node B without traffic HSDPA after break transmission NA05018306 A lot of HSDPA FAILURE IN WCEL alarms /HUE RNC/ VMS3
Nokia Siemens Networks
Company Confidential
2 (3)
MENU
Modified components: Component Version *Net element Grm3g.sun wn50_cd3#2 Grm_cell_configu wn50_cd3#1 ration_data.spd SeekSharedWpa wn50_cd3#1 Cell.spd ReserveResourc wn50_cd3#1 esForSharedWpa Cell.spd *SW-type *Unit -
Change effects: Effects on end-user No HSPA recovery after aal2 restores Effects on Operator No HSPA recovery after aal2 restores Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
3 (3)
MENU

Title: FXDA typeB configuration: throughput about 500kbps for HSUPA. Version of the SW-build: WN6.0 22.12-290_B Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Low T-put on BTS with FXDA unit Description of the fault: Radio module forces always two measurement messages for a radio pipe even though only one message would be enough for commissioned carriers. Description of the correction: New measurements Added to RFSW code ID implementation which compose ID name in right way. Corrected Fault Reports: NA05017107 FXDA type B configuration, throughput is 500kbps for HSUPA. NA05028359 HSUPA Mac-d Throughput issue with FXDA
4 (3)
MENU
Modified components: Component V12X.Version 01 *Net element *SW-type *Unit -
Change effects: Effects on end-user Low HSUPA through put Effects on Operator HSUPA service degreased Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
5 (3)
MENU

Title: HSPA over IuR: abnormal RRC Release - RLReconfFailure Version of the SW-build: WN6.0 22.12-290_C Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Radio link abnormal releases when switching from E/// cell to NSN cell. How end user/operator could detect the problem: Radio link abnormal releases when switching from E/// cell to NSN cell. Description of the fault: After SCC there is an RNC change .TUP-U send cause 20 as the response for Reconfig Commit Request, which is then causing RRC release. Description of the correction: TUP-U responds OK for RNC change and other resonable changes. Corrected Fault Reports: 85599ESPE04 HSPA over IuR (Ericsson - SRNC, NSN-DRNC) Abnormal RRC Release - RLReconfFailure NA05029810 HSPA over IuR (Ericsson - SRNC, NSN-DRNC) Abnormal RRC Release - RLReconfFailure Modified components: Component BTS_SC_TUP.Change effects: Effects on end-user Connection aborted Effects on Operator RL abnormal release Version 6566 *Net element *SW-type *Unit -
6 (3)
MENU

Title: BTS autonomous reset as recovery action (1811) Version of the SW-build: WN6.0 22.12-290_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: 1811 fault causing recovery reset. How end user/operator could detect the problem: Fault and BTS recovery reset Description of the fault: Earlier corrections done for extension module connection recoveries cause sometimes that optic link is disconnected one extra time while message sending between modules is already ongoing. When there is no response to some message due to link disconnect, fault 1811 is then sent and causing reset. This can happen in HW reset when default delay value is used and it needs adjusting. Workaround: BTS should recover by itself after reset(s) Description of the correction: Corrections done to optical interface recoveries when wrong delays are measured so that no extra link disconnects are performed which will prevent unnecessary 1811 fault and BTS recovery resets Corrected Fault Reports: 84127ESPE04 BTS autonomous reset as recovery action (1811) 31634ESPE05 BTS autonomous reset as recovery action after hard reset 86039ESPE04 Unexpected site reset during BTS start up.
7 (3)
MENU
8 (3)
MENU
Modified components: Component BBC_Pkg.sbs Change effects: Effects on end-user BTS start up time after HW reset increases. Effects on Operator BTS start up time after HW reset increases. Testing Instructions for the change Pre-requirements: Test execution: Expected results: Unexpected results: Version 60572 *Net element *SW-type *Unit -
9 (3)
MENU

Title: RF module failures with configuration 3+3+3 and FSMB + FSMD and FRGL/FRGC Version of the SW-build: WN6.0 22.12-290_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: How end user/operator could detect the problem: One TX in second sector, or whole RF module, may become inoperable due to fault 125 or fault 1905 Description of the fault: Occasionally DL antenna carrier enabling was done in incorrect order which leads to failures with FR modules Dependency on configuration: 1+2+1+2A / 1+2+1+2+1+2A, FSMB + FSMD/E Workaround: Switch BTS first on with extension FSM powered off. Then switch power on to extension. Description of the correction: Additional logic implemented to DL antenna carrier enabling. Corrected Fault Reports: NA05025290 3+3+3 with FSMB + FSMD and FRGL/FRGC Modified components: Component BBC_pkg.sbs Version 60899 *Net element *SW-type *Unit -
Change effects: Effects on end-user None Effects on Operator None
10 (3)
MENU
Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
11 (3)
MENU

Title: Dual Cell for certain UARFCNs not supported. Version of the SW-build: WN6.0 22.12-290_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: No dual cell possible with certain UARFCNs How end user/operator could detect the problem: Dual cell not working Description of the fault: BTS calculates adjacent frequencies for DC-HSDPA cell pair based on UARFCN values instead of frequencies. This is wrong implementation and does not work e.g. in band-IV. Description of the correction: BTS Telecom calculation corrected so that DC-HSDPA cell is based on adjacent frequencies, not UARFNCN values Corrected Fault Reports: 57120ESPE03 Dual Cell for a certain operator UARFCNs not supported. Modified components: Component TCOM_TOAM.c mp Version 32503 *Net element *SW-type *Unit -
12 (3)
MENU
Change effects: Effects on end-user None Effects on Operator None Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
13 (3)
MENU

Title: BTS autonomous reset as recovery action (1811) Version of the SW-build: WN6.0 22.12-290_E Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: 1811 fault causing recovery reset. How end user/operator could detect the problem: Fault and BTS recovery reset Description of the fault: With extension module connection recovery may cause extra optic link disconnection while message sending between modules is ongoing. When there is no response to some message due to link disconnection, fault 1811 is then causing reset. This can happen during HW reset when default delay value is used and default value is needed to be adjusted. Workaround: BTS should recover by itself after reset(s) Description of the correction: Corrections done to optic recoveries when wrong delays are measured so that no extra link disconnects are performed which will prevent unnecessary 1811 fault and BTS recovery resets. Corrected Fault Reports: 84127ESPE04 BTS autonomous reset as recovery action (1811) 31634ESPE05 BTS autonomous reset as recovery action after hard reset 86039ESPE04 Unexpected site reset during BTS start up. Modified components: Component BBC_Pkg.sbs Version 59264 *Net element *SW-type *Unit -
14 (3)
MENU
Change effects: Effects on end-user None Effects on Operator The problem causes that BTS start up time after HW reset increases. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
15 (3)
MENU

Title: Passage in FACH during traffic ftp - large impact on the rate Version of the SW-build: WN6.0 22.12-290_J Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: BTS does not reply to Capacity Request from RNC or replay with 0 credit to RNC. UE goes to cell FACH during transfer due to no response to capacity request send by RNC. How end user/operator could detect the problem: Problem can be seen during activation of PDP and long FTP download. RNC sends Mac-d flow capacity request expired and download transferring stops and UE goes automatically to cell FACH. After several repetitions of capacity request UE goes to cell DCH and transferring continues. Description of the correction: 1) Improving Compress Mode gap handling when this information is receiving from RAKE. In this situation re-transmission informs that sub-frames are not in MAC-HS and resulting no scheduling -> FACH drop 2) SW bug in the HARQ handling. During RNC PDSCH codes reduction (Hs codes) MACHS does not handle related reduction in the number of HARQS. As result User was not being scheduled and user POV dropped to FACH. 3) In a certain condition T1 timer is not working as expected. Corrected Fault Reports: NA05000487 Passage in FACH during traffic ftp - large impact on the rate Modified components: Component Version *Net element *SW-type -.-
*Unit -
16 (3)
MENU
Change effects: Effects on end-user Data download transferring stops time to time Effects on Operator Call throughput goes to 0 or call drop goes to R99.
Testing Instructions for the change Pre-requirements: Test execution: Expected results: Unexpected results: -
17 (3)
MENU

Title: WN6 MP4.1 caused degradation in RAB Access Fail CS Voice MS M1001C122 Version of the SW-build: WN6.0 22.12-290_H Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: When Radio Link reconfigures RBR messages from DCH to HSPA or from HSPA to DCH, those messages are lost and there is no response from UE which then causes Radio Link failure due to loss of synchronization Description of the fault: TUP-C have performance problem and as result RlReconfigCommit message was received too later in TUP-U. Workaround: Avoiding the problem function "too late Commit detection" was implemented in TUP-U. Description of the correction: TUP-C performance optimization so that TUP-C has faster Conman (resource manager). Corrected Fault Reports: NA05038424 WN6 MP4.1 caused degradation in RAB Access Fail CS Voice MS M1001C122 NA05033390 CSSR CS after WN6.0 MP4.07 NA05019482 CS call failures with iPhone4 after AMR+HSPA Multi RAB activation Modified components: Component Version BTS_SC_TUP.6666
*Net element -
*SW-type -
*Unit -
18 (3)
MENU
Change effects: Effects on end-user None Effects on Operator Degradation in RAB Access Fail CS Voice MS M1001C122 Testing Instructions for the change Pre-requirements: Test execution: Expected results: Unexpected results: -
19 (3)
MENU
WCDAM BTS CN-id: WN60829

Title: RF Module Failure (0125) Alarm on FRGQ on 3rd carrier in sector-2 after the 3rd carrier addition Version of the SW-build: WN6.0 22.12-290_E Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Data from TX2 on RF2 and TX5 on RF3 had conflict while they were routed in MUKSU on ESM to MSM How end user/operator could detect the problem: RF module faulty and calls not possible Dependency on configuration: 3+3+3 with RRH Description of the correction: MUKSU routing was changed Effects on end-user: Calls not possible Effects on operator: BTS functionality is degraded Faulty component and version: BBC_pkg.sbs Corrected Fault Reports: NA05027618 RF Module Failure (0125) Alarm on FRGQ on 3rd carrier in sector-2 after the 3rd carrier addition Modified components: Component Version BBC_pkg.sbs 61213
*Net element -
*SW-type -
*Unit -
20 (3)
MENU
Change effects: Effects on end-user None Effects on Operator None
Testing Instructions for the change Pre-requirements: Test execution: Passed Expected results: Problem disappeared Unexpected results: None
21 (3)
MENU

Title: ToP timing source lost alarm appeared Version of the SW-build: WN6.0 22.12-290_I Valid for Product(s): Flexi WCDMA Base Station Reason for the Change Note: Summary of the original problem: ToP timing source lost alarm appeared How end user/operator could detect the problem: Fake alarms seen on NE Description of the fault: After SW upgrade the ToP synchronization lost alarm is seen even though ToP timing is working fine. Related feature / functionality: Synchronization sources in FTM. Workaround: Recreate the ToP source or resetting the BTS to clear the alarm. Description of the correction: Earlier submitted alarms after ToP synchronization were not cancelled. Faulty component and version: FTM_A65_231.00 Corrected Fault Reports: NA05021453 ToP timing source lost alarm appeared NA05029219 ToP Timing source lost on unit 1 alarm after upgrade to 154C Modified components: Component Version *Net element IP.ip_pri_pr828 80_orb_han g_a65
*SW-type -
*Unit -
22 (3)
MENU
Change effects: Effects on end-user None Effects on Operator Only fake alarms are seen. Testing Instructions for the change Pre-requirements: Test execution: Expected results: Unexpected results:
23 (3)
MENU
Title: Unit autonomous reset as recovery action source of FSPC detected after unblock modules on WN6.0_22.12_280_D Version of the SW-build: WN6.0 22.12-290_H Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: TCOM configuration was done regardless of Primary TX configuration. Occasionally TCOM has not been informed about Primary TX How end user/operator could detect the problem: Cell is not operational or unit is in autonomous reset. Description of the fault: Primary TX setting was done regardless of sending configuration to TCOM Related feature / functionality: Flexi configuration Workaround: Cell block/unblock Description of the correction: TC_HW_CONFIGURATION_CHANGE MSG is sent after Primary TX has been configured. CONF checks if TX SW State is set to configured Faulty component and version: BTSOM Corrected Fault Reports: 84915ESPE04 Unit autonomous reset as recovery action source of FSPC detected after unblock modules on WN6.0_22.12_280_D
24 (3)
MENU
Modified components: Component CONF_Pkg.Change effects: Effects on end-user Traffic capacity decreased Effects on Operator Cell not operational Testing Instructions for the change Pre-requirements: Test execution: Expected results: Unexpected results: Version 61549 *Net element *SW-type *Unit -
25 (3)
MENU
Title: Faults 488 EFaultId_MacHsCorruptDataFromTup during stability test Version of the SW-build: WN6.0 22.12-290_H Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Faults 488 EFaultId_MacHsCorruptDataFromTup active during stability test How end user/operator could detect the problem: MAC-HS will report fault 488 EFaultId_MacHsCorruptDataFromTup when BTS received unexpected MAC-D PDU size from priority queue. Description of the fault: MAC-HS will raise fault 488 if Mac-d PDU header information is not in sync with PDU Related feature / functionality: MAC-HS (type 1) MAC-D PDU size should not be changed in the priority queue Description of the correction: Improved debug ability to find out some extra information and implemented protections in TUP-u: UP: when HSDSCH type 1 data frame received to change MAC-D PDU size, UP will print error and discard that wrong frame. CP: when HsRlReconfigPrepare received to modify MAC-D PDU size, CP will send NACK it and also generates print error
Corrected Fault Reports: 84432ESPE04 Faults 488 EFaultId_MacHsCorruptDataFromTup during stability test Modified components: Component Version
*Net element
*SW-type
*Unit
26 (3)
MENU
BTS_SC_TUP.-
6644
27 (3)
MENU
Change effects: Effects on end-user None Effects on Operator There is no fault 488 from MAC-HS
Testing Instructions for the change Pre-requirements: Test execution: Expected results: Unexpected results: -
28 (3)
MENU
Title: After SW upgrade from 22.12-145 to 22.12-159_B alarm "BTS requires restart because licence status has changed" became active. Version of the SW-build: WN6.0 22.12-290_E1 Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Alarm "BTS requires restart because license status has changed" activated after SW upgrade How end user/operator could detect the problem: Add feature code 649 Description of the fault: LM didn't manage to handle Code Error request on time. Description of the correction: Prioritizing OPT events queue so that feature code 649 will be checked first. Check also whether BTS is in Configured state and feature code 649 is set to off in SCF.
Corrected Fault Reports: NA05038853 After SW update from 22.12-145 to 22.12-159_B alarm "BTS requires restart because licence status has change". Modified components: Component OPT.sbs Version 60924 *Net element *SW-type *Unit -
29 (3)
MENU
Change effects: Effects on end-user BTS reset Effects on Operator BTS reset
30 (3)
MENU
Title: All 3 RETs not detected without any alarm at the Node B, SW MP1 212 Version of the SW-build: WN6.0 22.12-290_E Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: All 3 RETs not detected without any alarms at the Node B How end user/operator could detect the problem: RETs are not detected. Description of the fault: stConfigurePreviouslyDetected was disabled. Description of the correction: Enable stConfigurePreviouslyDetected Corrected Fault Reports: NA04871997 All 3 RETs not detected without any alarm at the NB, SW MP1 212 Modified components: Component Version ALMAG_CC_Pkg 58434 .sbs *Net element *SW-type *Unit -
31 (3)
MENU
Change effects: Effects on end-user RETs not detected from SEM Effects on Operator No effects Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
32 (3)
MENU
Title: Alarm "no connection to unit" causes site out of service after restart. Version of the SW-build: WN6.0 22.12-290_K Valid for Product(s): Ultra Site WCDMA Base Station References:
Reason for the Change Note: Summary of the original problem: When alarm "no connection to unit" occurred and BTS is not able to restore the unit functionalities. If BTS is restarted it doesn't reach state "integrated to RAN". Faulty unit(s) has to be removed by re-commissioning to get sector(s) work. Now detected Ultra site BTS site reaches "integrated to RAN" status in 15mins and then disables the sector(s) impacted by the faulty unit(s). How end user/operator could detect the problem: BTS cant reach On Air state and all cells stays as not active. Description of the fault: When there is no connection to WPA unit. BTS has to be forced to get in to On Air state. Dependency on configuration: No connection to WPA unit Description of the correction: Timeout for forcing resources was increased, so that proper event would be sent in time. Corrected Fault Reports: NA04970612 "No connection to unit" causes site out of service after restart
33 (3)
MENU
Modified components: Component Fore_sm.sbs Change effects: Effects on end-user Calls not possible Effects on Operator Calls not possible Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None Version 3288 *Net element *SW-type *Unit -
34 (3)
MENU

Title: Low or null throughput in Node Bs and getting rectified after reset of Node B's Version of the SW-build: WN6.0 22.12-290 Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Implementation is misalignment with specification. Summary of the original problem: Low or null throughput in Node B's and getting rectified after reset of Node B's How end user/operator could detect the problem: Cell trough put degraded. Description of the fault: FBIA was wrongly identified as Rel1 HW and in Rel2 HW and some functionalities of Rel2 are unavailable and causes lack of resources. Description of the correction: BPF corrected and variant is defined as F for FBIA.
Corrected Fault Reports: NA04970242 Low or null throughput in Node B's and getting rectified after reset of Node B's Modified components: Component FlexiBTSProperti es.xml Version . *Net element *SW-type *Unit -
35 (3)
MENU
Change effects: Effects on end-user: BTS operation is restored. Effects on operator: FBIA is properly handled and proper BTS operation is restored Testing Instructions for the change Pre-requirements: Test execution: Passed Expected results: Problem Disappeared Unexpected results: None
36 (3)
MENU

Title: Increase of HSUPA ACC fail due to BTS after MP4.1 Version of the SW-build: WN6.0 22.12-290_W Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: In high CPU load condition HSUPA user can go to undefined state and then the user cannot be deleted - user stays to hang. How end user/operator could detect the problem: HSUPA hanging connections during user reallocations and HsupaSetup rejections with cause fault 14 or HsupaDeletion rejections with fault cause 12. Description of the fault: HSUPA deletion error handling when re-allocation procedure has been interrupted by HSUPADelete and HSUPASetup request sequence Description of the correction: Correction in HSUPA Deletion procedure: HSUPA Deletion for existing and rejected user goes to buffer state. Corrected Fault Reports: NA05045643 Increase of HSUPA ACC fail due to BTS after MP4.1 Modified components: Component TUP.Version 6824 *Net element *SW-type *Unit -
37 (3)
MENU
Change effects: Effects on end-user HSUPA call drops or long pending connections Effects on Operator HSUPA access counter increases after WN6.0 MP4.1 SW load (Setup_Fail_Edch due to BTS) Testing Instructions for the change Pre-requirements: Test execution: Passed Expected results: Problem disappeared Unexpected results: None
38 (3)
MENU
Title: Alarm Not enough resources for commissioned HSUPA Version of the SW-build: WN6.0 22.12-290_N Valid for Product(s): Ultra Site WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Alarm 130 "Not enough resources for commissioned HSUPA" (or RNC notification 7652 with the same description "Not enough resources for commissioned HSUPA") is appearing frequently. How end user/operator could detect the problem: Alarm becomes active even after end of recovery Description of the fault: Pre-reservation is tried to be done although there is HSDPA recovery in another LCG or this LCG already has HSUPA Cell or it is in Link State. DspCapa are already received and alarm 130 is raised. Related feature / functionality: Pre-reservation and recovery. Dependency on configuration: Problem would appear in all HW configurations. Description of the correction: This alarm is correct during WSPC (autonomous) restart, when there are really not enough resources (CE). When such a WSPC is up and running again, all CE are available, and this alarm is now cancelled. Corrected Fault Reports: NA04996895 Alarm Not enough resources for commissioned HSUPA
39 (3)
MENU
Modified components: Component Version AddHsdpaCellTo 31707 RecoveryList.spd CommonRecover 31707 y.spd HsupaCapacityPr 31707 eReserving.spd StartHsdpaRecov 31707 ery.spd StartHsupaRecov 31707 ery.spd grm3g.sdt 31707 mt/GRM_mt_test 31707 _suite.itex mt/full_GRM_mt_ 31707 test_suite_flexi.cf g telecom/telecom. 31707 sdt mt/full_GRM_mt_ 31706 test_suite_nora.cf g_ultra GetHsupaMasterI 33368 ndex.spd IsLcgUnderHsdp 33368 aRecovery.spd GRM_mt_test_su 33368 ite.itex full_GRM_mt_tes 33368 t_suite_flexi.cfg full_GRM_mt_tes 33368 t_suite_nora.cfg telecom.sdt 33368 Change effects: Effects on end-user No effect on end users. Effects on Operator Hanging alarms. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared
Nokia Siemens Networks Company Confidential
*Net element -
*SW-type -
*Unit -
40 (3)
MENU
Unexpected results: None
41 (3)
MENU
Title: After WN6.0 MP4.1 upgrade WBTS rejects configuration with message not compatible with receiver state error at initial stage Version of the SW-build: WN6.0 22.12-290_X Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: After WBTS SW upgrade to WN6.0 MP4.1 some cells reject HSDPA configuration. Plenty of CEs lost in some sites with FSMB.
How end user/operator could detect the problem: After WBTS SW upgrade to WN6.0 MP4.1 some cells reject HSDPA configuration and Fault 1815 on FSP appears. Description of the fault: FSPA fails to recover after fault 1815 Dependency on configuration: SM Rel1 Description of the correction: Silent reset started correctly, fault (32) is not raised. Faulty component and version: FSP_Agent before rev. 62571 Corrected Fault Reports: NA05042821 After WN6.0 MP4.1 upgrade, WBTS rejects configuration with message not compatible with receiver state error at initial stage NA05051216 Missing 80 CEs in some sites with FSMB
42 (3)
MENU
NA05058230 CLRNC002 / CL20124A Reduction in Max Available CE after MP4.11 upgrade
43 (3)
MENU
Modified components: Component FSP_Agent_Pkg. sb Version 62571 *Net element *SW-type *Unit -
Change effects: Effects on end-user None Effects on Operator FSPA is missing from configuration and available CE of the site is degraded. Testing Instructions for the change Pre-requirements: Test execution: Expected results: Unexpected results: -
44 (3)
MENU
Title: Sudden loss of channel elements on Flexi (Issue 1) with MP4.1 Version of the SW-build: WN6.0 22.12-291_C Valid for Product(s): Flexi WCDMA Base Station References:
Reason for the Change Note: Summary of the original problem: Sudden loss of CEs in Flexi (Issue 1) with MP4.1 due to FSPA crash Description of the fault: Hanging user in slave decoder due to incomplete frame data User is in de-active state and buffer for hanging user is been tried to free for the new user setup at the same location of hanging user. This leads to crash situation since some buffer of hanging user allocated dynamically and corrupted unexpectedly. Workaround: 1. Activate the user even if incomplete frame data received at activate SFN. 2. Remove user in slave decoder mandatory if delete SFN come by sending deletion indication message with immediately SFN from master to keep database consistent between master decoder and slave decoder. Description of the correction: DSP Codec SW modification Corrected Fault Reports: NA05050532 Sudden loss of channel elements on Flexi (Issue 1) with MP4.1
Modified components: Component Version BTS_WN50_SC_ 321 DSP.*Net element *SW-type *Unit -
45 (3)
MENU
Change effects: Effects on end-user Effects on Operator Testing Instructions for the change Pre-requirements: Test execution: Expected results: Unexpected results: -
46 (3)
MENU
Title: FTLB cards don't support auto negotiation towards ABN Version of the SW-build: WN6.0 22.12-290_W Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Optical interface is connected to far end device ABN. When (ABN) is set to auto-detect mode and FTLB is set to auto-detect mode or 1000mbps then link goes down. Description of the fault: FTLBs optical port indicates to be set as Half Duplex. This FTM device should be Full Duplex not Half Duplex. Description of the correction: When Port interface is set, it is Full duplex. Corrected Fault Reports: NA05044624 1-3581810 FTLB cards don't support auto-negotiation towards ABN Modified components: Component Version *Net element os_vpr_na050446 FTM_A65_M 24_sfp_fix_a65_ P42_237.00 mp42.*SW-type *Unit -
47 (3)
MENU
Change effects: Effects on end-user Dropped call as link is going down. Effects on Operator Dropped call as link is going down. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
48 (3)
MENU
Title: Passive Units commissioning issue Version of the SW-build: WN6.0 22.12-290_S Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Passive Units commissioning issue Description of the fault: Wrong validation for Passive units Workaround: Validation is not needed, just remove it. Description of the correction: Remove the mismatch check when clicking ok button. Corrected Fault Reports: NA05000129 Passive Units commissioning issue Modified components: Component common.jar Version 313602 *Net element *SW-type *Unit -
49 (3)
MENU
Change effects: Effects on end-user None Effects on Operator Operator cannot configure same value for Passive units. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
50 (3)
MENU
Title: LCG1 Max available CE drop from 612 to 396 and stuck after MP4.01 upgrade - high blockage Version of the SW-build: WN6.0 22.12-290_P1 Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: TCOM does not restart after recovery - problem with loading rules and capacity files. How end user/operator could detect the problem: Problem becomes visible when TCOM cannot start after recovery. Fault is caused by un-received messages including address of capacity and rules files. Description of the fault: BTS O&M during recovery is too busy to send paths to TCOM LRM Description of the correction: Rules and Capacity configuration files are removed and their content is kept in code. Proper rules & capacity are used according to HW type where TCOM LRM is used.
Corrected Fault Reports: NA05018859 LCG1 Max available CE drop from 612 to 396 and stuck after MP4.01 upgrade - high blockage NA05042555 FSP recovery problem - (136 ) TcomConfFileAl after 1806 alarm.
51 (3)
MENU
Modified components: Component Version make/wn_tcomrm 34102 .mak TelecomSw/desig 34060 n/rm/Calculation/ RmCapacityUltra. cpp TelecomSw/desig 34058 n/rm/Calculation/ RmCapacityFlexi R1.cpp TelecomSw/desig 34058 n/rm/Calculation/ RmCapacityFlexi R2.cpp TelecomSw/desig 34058 n/rm/RuleParser/ RmRulesFlexiR1. cpp TelecomSw/desig 34058 n/rm/RuleParser/ RmRulesFlexiR2. cpp TelecomSw/desig 34058 n/rm/RuleParser/ RmRulesUltra.cp p TelecomSw/desig 34058 n/rm/RuleParser/ RuleParser.cpp TelecomSw/desig 34004 n/rm/CommonSer vices/LrmCommo nFunctions.cpp TelecomSw/desig 33988 n/rm/Calculation/ Calculation.vcproj TelecomSw/desig 33988 n/rm/Calculation/ ResourceCalc.cp p TelecomSw/desig 33988 n/rm/Ruleparser/ RuleParser.vcproj TelecomSw/desig 33954 n/rm/Calculation/ RmCapacity.hpp TelecomSw/desig 33954 n/rm/RuleParser/ RmRules.hpp TelecomSw/desig 33946 n/rm/ConfigMgmt/ ConfigMgmt.cpp *Net element *SW-type *Unit -
52 (3)
MENU
53 (3)
MENU
Title: UTC+4 MSK Time Zone Version of the SW-build: WN6.0 22.12-290_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: BTS commissioning supports only Moscow GMT+3 time zone .Moscow time zone has changed to GMT+4 permanently. DST (Daylight Saving Time) is not used anymore. How end user/operator could detect the problem: GMT definition for Russia is not always correct. Description of the fault: BTS Commissioning supports wrong (GMT+3) time zone for UTC+4 MSK. Workaround: Use another GTM+4 location instead of Moscow (GTM+3) Description of the correction: BTS Site Manager fixed to support GTM+4 Interface Effects: Synchronization between NE and EM Corrected Fault Reports: NA05024610 UTC+4 MSK NA05031239 Wrong time on all WBTS
54 (3)
MENU
Modified components: Component WBTS6.0 btsmanager.jar Version MP4.2 MP4.2 *Net element *SW-type *Unit -
Change effects: Effects on end-user If time synchronization signal is sent over Air IF then the UE shows wrong timing. Effects on Operator Use the workaround solution until correction available. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
55 (3)
MENU
Title: Very poor success rate of ADA SW Download (during commissioning) Version of the SW-build: WN6.0 22.12-291_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: ADA SW downloading failing due to SW DL supervision failing How end user/operator could detect the problem: SW DL fails Description of the fault: High CPU load during SW download which causing delays in handling supervision messages. Description of the correction: Improved handling of supervision messages Corrected Fault Reports: NA05018559 Very poor success rate of ADA SW Download (during commissioning)
56 (3)
MENU
Modified components: Component Version APW_pkg.63948 Default_Agent_pk 63948 g.LTX_Agent_pkg.- 63948 MRS_Agent_pkg. 63948 Multiradio_Agent 63948 _Pkg.RPMAG_Commo 63948 n_Pkg.RRH_Agent_pkg. 63948 SOAPMessageEv 63948 ents_Pkg.*Net element *SW-type *Unit -
Change effects: Effects on end-user Possible call drop Effects on Operator Spurious RF reset and so various RF problems with SW download. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
57 (3)
MENU
CN-id: WN60852
Title: Issue 224 Wrong behaviour Antenna Line Management Version of the SW-build: WN6.0 22.12-291_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: To undo commissioning of MHA and then Block/Unblock RF Unit does not take any effect and undo commission was not successful. Only BTS reset clears the situation. How end user/operator could detect the problem: Target test. Description of the fault: Performing RF module Block/Unblock does not work when doing undo MHA commissioning. Description of the correction: Update the DB status after performing RF module Block/Unblock. Corrected Fault Reports: NA05022859 Issue224 Wrong behaviour Antenna Line Management Modified components: Component ALMAG_MGMT_ Pkg.sbs Version 63837 *Net element *SW-type *Unit -
58 (3)
MENU
59 (3)
MENU
Title: Non-HSDPA power ratio incremented after upgrading to RU20 Version of the SW-build: WN6.0 22.12-290_C Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Non-HSDPA power ratio incremented after upgrading to RU20 How end user/operator could detect the problem: Leading to positive BIOS nonHsdpaPower may go high in a spike situation Description of the fault: When calculating sumOfNonHsdpaPower then the negative values were ignored and only positive values were taken into account. This may lead to positive BIOS and nonHsdpaPower values situation which then may lead to spike situation. Description of the correction: Correction takes into account positive and also negative values. Corrected Fault Reports: NA04938960 Non-HSDPA power ratio incremented after upgrading to RU20 Modified components: Component BTS_SC_DSP.Version 16318 *Net element *SW-type *Unit -
60 (3)
MENU
Change effects: Effects on end-user None Effects on Operator Positive BIOS and nonHsdpaPower high spike situation. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
61 (3)
MENU
Title: Missing CEs after recovery reset of FSPC1 Version of the SW-build: WN6.0 22.12-290_X Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Missing CEs after recovery reset of FSPC1 How end user/operator could detect the problem: Decreasing CEs after recovery reset of FSPC1 Description of the fault: When resetting Faraday it leads to FSPC1 reset. After reset FSPC1 card does not come configuration state which is caused by wrong values of parameter SrioInitContainer in BBC. Description of the correction: BBC changes related to SrioInitContainer Corrected Fault Reports: 87210ESPE04 Missing CEs after recovery reset of FSPC1 Modified components: Component BBC_pkg.sbs Version 63326 *Net element *SW-type *Unit -
62 (3)
MENU
Change effects: Effects on end-user N/A Effects on Operator Missing CEs after recovery reset of FSPC1 Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
63 (3)
MENU
Title: Sudden loss of channel elements on Ultra Site Version of the SW-build: WN6.0 22.12-291_C Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: BTS performance degraded after IUB line brake. How end user/operator could detect the problem: Some cells might change state to Degraded. Capacity Failure and Not Enough Resource faults are visible Description of the fault: Occasionally, after IUB line recovery on complex configurations: Telecom was not informed about links state change due to high load. Related feature / functionality: Cell configuration Workaround: BTS reset Description of the correction: When TUP informs slave WAM about link state change, WAM saves information. Then WAM waits link state change notification from DB. If notification from DB is not received within defined time period WAM reads links state from DB and publish changes. Corrected Fault Reports: NA05009882: Sudden loss of channel elements on Ultra Site NA05031873: Ultra site non-recovery after IUB break Modified components: Component CONF.sbs Version 3440 *Net element *SW-type *Unit -
64 (3)
MENU
Change effects: Effects on end-user BTS capacity degraded Effects on Operator BTS capacity degraded Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
65 (3)
MENU
Title: Throughput impacted while HSDPA and HSUPA performed simultaneously Version of the SW-build: WN6.0 22.12-291_E Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Throughput impacted while HSDPA and HSUPA performed simultaneously How end user/operator could detect the problem: Low Throughput Description of the fault: Users are not getting upgraded when RG UP is resulting in the same Serving Grant. Description of the correction: AG is used in the cases where RG UP results in same Serving Grant. Extra conditions added to be avoid unnecessary use of AG. Corrected Fault Reports: NA05019410 Throughput impacted while HSDPA and HSUPA performed simultaneously NA05035395 HSDPA decrease due to high BLER which caused by incorrect HS-SCCH decoding problem Modified components: Component Version WBTS_UP_1000 9.0 6.WBTS_UP_5753. 10.0 WBTS_UP_1260 1.0 1.WBTS_UP_9412. 12.0
*Net element -
*SW-type -
*Unit 66 (3)
MENU
BTS_SC_DSP.-
16396
67 (3)
MENU
Change effects: Effects on end-user Low Throughput (or) Call Drops Effects on Operator Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
68 (3)
MENU
Title: PCI_INVALID_RESET_PARAM_ERROR Version of the SW-build: WN6.0 22.12-290_Q Valid for Product(s): Ultra Site WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: PCI_INVALID_RESET_PARAM_ERRORs visible in WSPC logs How end user/operator could detect the problem: After BTS start up and fetch BTS technical report and check WSPC log files Description of the fault: Ethernet activity verification polling feature was deployed to WSPC MCU SW. Poll indicates complains about non-existent activity. . Description of the correction: Ethernet activity verification polling feature from WSPC MCU SW removed. Corrected Fault Reports: NA04976078 PCI_INVALID_RESET_PARAM_ERROR Modified components: Component *BTSPS-4276.Version *Net element *SW-type *Unit -
69 (3)
MENU
70 (3)
MENU
Title: BTS reset due to kernel error Rhaps_ALMAG_MGMT_CommonAgent on WN6.0 22.12290_I Version of the SW-build: WN6.0 22.12-291_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Kernel failure during blocking/unblocking RF module How end user/operator could detect the problem: After Unit block unblock or BTS reset there is additional BTS spontaneous reset and it's not possible to connect to BTS. Description of the fault: While performing some operation after unblock there was double deletion of a pointer Description of the correction: Double deletion of a pointer removed. Corrected Fault Reports: 86959ESPE04 BTS reset due to kernel error Rhaps_ALMAG_MGMT_CommonAgent on WN6.0 22.12290_I 87069ESPE04 Block/unblock of RF modules in C type configuration cause BTS reset Modified components: Component Version ALMAG_MGMT_ 62645 Pkg.sbs LTX_Agent_pkg.s 64115 bs RPMAG_Commo 64115
*Net element -
*SW-type -
*Unit 71 (3)
MENU
n_pkg.sbs
72 (3)
MENU
Change effects: Effects on end-user Service degraded. Effects on Operator RF Module Block/Unblock do not work correctly. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
73 (3)
MENU
Title: Missing AntennaConfigData.xml file after SW upgrade Version of the SW-build: WN6.0 22.12-290_X Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Missing AntennaConfigData.xml file How operator could detect the problem: Antenna configuration data were saved, because of missing AntennaConfigData.xml file Root cause: Kernel in ALMAG causing CFM OSE fails. Antenna configuration data file could not be created. Configuration files stored to /ROM directory hence all configuration data files were removed. The correction: Releasing of RAML file responsibility changed to CFM. Corrected Fault Reports: 29312ESPE06 Missing AntennaConfigData.xml file after SW upgrade. Modified components: Component ALMAG_MGMT_ Pkg.sbs CFM.sbs Version 61894 61894 *Net element *SW-type *Unit -
74 (3)
MENU
Change effects: Effects on end-user None Effects on Operator AntennaConfigData.xml file is not saved Testing Instructions for the change
Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
75 (3)
MENU
Title: Missing RET 1.1 Tilt parameters after SW upgrade/downgrade Version of the SW-build: WN6.0 22.12-290_X Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: TILT parameters were lost after SW upgrade/downgrade How end user/operator could detect the problem: No TILT parameters saved. Description of the fault: Missing AntennaConifigData.xml file Description of the correction: Kernel on edge of ALMAG and CFM corrected. Corrected Fault Reports: 29310ESPE06 Missing RET 1.1 Tilt parameters after SW upgrade/downgrade Modified components: Component CFM.sbs ALMAG_MGMT_ Pkg.sbs Version 62589 62612 *Net element *SW-type *Unit -
76 (3)
MENU
Change effects: Effects on end-user None Effects on Operator TILT values are now saved Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
77 (3)
MENU
Title: RET Fault (10) No connection to unit is not handled by FM Version of the SW-build: WN6.0 22.12-291_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: In RET-chaining the fault 10 appears when RETs are physically connected to FR1 but commissioned to FR2. RET chaining is not handled correctly. How end user/operator could detect the problem: Fault 10 appears Description of the fault: The fault 10 appears because FM uses the logical relation between FR-TILT. Dependency on configuration: RET-chaining Description of the correction: Updated the fdrule to correct fault 10 (No connection) problem situation. Parameter DYN_ScannedAntennaInterface.used to check relation between FR and TILT Corrected Fault Reports: 82097ESPE04 Fault (10), No connection to unit is not handled by FM for one of 7 RETs Modified components: Component FORE_FDCL_Pk g.sbs FlexiFDrules.txt Version 64034 64034 *Net element *SW-type *Unit -
78 (3)
MENU
79 (3)
MENU
Title: SiteEM.xml not updated in SW activation Version of the SW-build: WN6.0 22.12-291_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: SiteEM.xml was not copied properly during software activation. How end user/operator could detect the problem: Wrong version of BTS Site Manager used to connect BTS after restart. Description of the fault: Problem in getFullPath() usage. Description of the correction: Usage of getFullPath() function corrected. Faulty component and version: FLSH.sbs Corrected Fault Reports: 30454ESPE06 SiteEM.xml not updated in SW activation Modified components: Component FLSH.sbs Version 64056 *Net element *SW-type *Unit -
80 (3)
MENU
Change effects: Effects on end-user No effect Effects on Operator Wrong version of BTS Site Manager used to connect BTS. Limited functionality because of wrong version of BTS Site Manager. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
81 (3)
MENU
Title: RET's change antenna line assignment after upgrade to WN6 MP4.11 Version of the SW-build: WN6.0 22.12-291_K Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: After SW upgrade from WN6.0 MP3.2 to MP4.1 / MP4.11, some WBTS have RET(s) missing or commissioned on wrong RF module. How end user/operator could detect the problem: Upgrading BTS SW and SEM SW from MP3.2 - MP4.11 Description of the fault: Scanned "AntennaInterface" / "antlIdList" values not properly changed. RET(s) not properly displayed in SEM. Description of the correction: Remove MO sorting logic for RET and keep old id in SCF to avoid RET(s) mismatch problem when re-commissioning is done. Corrected Fault Reports: NA05048546 RET's change antenna line assignment after upgrade to WN6 MP4.11 NA05050833 RET Inversion between Sector 1 and 3 with RU20 MP4.1 Modified components: Component common.jar btsmanager.jar Version *Net element *SW-type *Unit -
82 (3)
MENU
Change effects: Effects on end-user Service degraded. Effects on Operator Re-commissioning has to be done on all effected sites due to SEM mismatch. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
83 (3)
MENU
Title: Missing local cells and ALDs view after SW upgrade to WN7.0 1.0 Version of the SW-build: WN6.0 22.12-291_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Event buffering in OXF library was not correct How end user/operator could detect the problem: After BTS SW upgrade to WN7.0 1.0 local cells and ADLs were not visible at BTS Site Manager. Description of the fault: Events are not queued correctly. Description of the correction: Upgrade of OXF library and switching on queuing of the events Corrected Fault Reports: 85968ESPE04 Missing local cells and ALDs view after SW upgrade to WN7.0 1.0 Modified components: Component RHAPSODY_OX F.Version *Net element 2011-04-28 *SW-type *Unit -
84 (3)
MENU
Change effects: Effects on end-user After BTS SW upgrade to WN7.0 1.0 local cells and ADLs were not visible at BTS Site Manager. Effects on Operator After BTS SW upgrade to WN7.0 1.0 local cells and ADLs were not visible at BTS Site Manager. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
85 (3)
MENU
Title: TRIAXS MHA commissioning issue. Version of the SW-build: WN6.0 22.12-290_P Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: TRIAXS MHA commissioning issue How end user/operator could detect the problem: Alarm min and max values and adjust step are read from filter property Antenna.Line.Current.Alarm which comes from DB dump. Description of the fault: The line voltage value is set automatically in WN3.2/WN3.3 but WN4.0 or later SW BTS Manager converts the line voltage to 12V Description of the correction: Antenna.Line.Current.Alarm changed from 120;1320;5;215 to 120;775;5;165 for FXDA Corrected Fault Reports: NA05001571 TRIAXS MHA commissioning issue Modified components: Component FlexiBTSProperti es.xml Version 1119 *Net element *SW-type *Unit -
86 (3)
MENU
Change effects: Effects on end-user None Effects on Operator MHA alarms are disabled as default. By enabling MHA Alarms then alarm limit is adjustable. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
87 (3)
MENU

Title: Telecom configuration failure (110) reported after site reset Version of the SW-build: WN6.0 22.12-290_L Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Unclear or misleading or inconsistent specification Summary of the original problem: Telecom configuration failure fault reported and all cells are out of service. How end user/operator could detect the problem: All cells are not working and there is a fault reported Description of the fault: Wrong values for some RXs in routing and scheduling tables .Wrong values used in baseband bus configuration which causes collisions in the bus. This will then cause the fault and cells do not work causes collisions in baseband bus Description of the correction: Used routing and scheduling values re-specified and implementation changed according to specification changes. Corrected Fault Reports: 86007ESPE04 : Telecom configuration failure (110) reported after site reset Modified components: Component Version BBC_Pkg.sbs 62363 WBTS_BBUS_69 2.0 996.WBTS_BBUS_70 2.0 007.WBTS_BBUS_69 7.0 990.WBTS_BBUS_70 7.0 006.-
*Net element -
*SW-type -
*Unit -
88 (3)
MENU
Change effects: Effects on end-user Service degraded. No calls Effects on Operator Cells out of service Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
89 (3)
MENU
Title: FAGE unit block / unblock from SEM doesn't work Version of the SW-build: WN6.0 22.12-290_E Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: FAGE unit block / unblock from SEM fails. How end user/operator could detect the problem: FAGE unit block / unblock fails. Description of the fault: Antenna line power tried to turn off. This is not needed to be done for FAGE unit. Dependency on configuration: Configuration must include FAGE units. Workaround: BTS reset Description of the correction: Line powers were not turned off before blocking FAGE units. Faulty component and version: FORE_SM in BTSOM Corrected Fault Reports: 80800ESPE04 FAGE unit block / unblock from SEM doesn't work
90 (3)
MENU
Modified components: Component Version WCDMABPFReq 248 uestExcel.FlexiBTSProperti 884 es.xml WBTS_STATE_2 31.0 8529.WCDMA_BTS_S 12.1.4 W_OAM_FS_FL EXI_BLOCK.bpf_def.h 60557 SM_BLOC_LOC 60558 K_Pkg.sbs REVIEW_ID.1685 Change effects: Effects on end-user FAGE unit blocking fails. Effects on Operator FAGE unit blocking fails. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None *Net element *SW-type *Unit -
91 (3)
MENU
Title: Flexi WCDMA BTS Branch Activation License is enabled in BPF for FAGE Version of the SW-build: WN6.0 22.12-290_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Tried to verify that Flexi WCDMA BTS Branch Activation License is not needed for FAGE How end user/operator could detect the problem: Alarm Licence missing was raised Description of the fault: Flexi WCDMA BTS Branch Activation License alarm license missing 00000001052 activated although Branch activation license is not needed in case of FAGE Description of the correction: BPF updated: Support.Of.Carrier.Pa.Licences property value changed from "2,2,6,2,0" to "2,2,6,0,0" for FAGE Corrected Fault Reports: 86136ESPE04 Flexi WCDMA BTS Branch Activation License is enabled in BPF for FAGE Modified components: Component FlexiBTSProperti es.xml Version 930 *Net element *SW-type *Unit -
92 (3)
MENU
Change effects: Effects on end-user None Effects on Operator Alarm not activated Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
93 (3)
MENU
Title: Bad HSPA KPI, due to lots of faults (493) HsupaL2HwModificationRejected Version of the SW-build: WM6.0 22.12-291_H Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: A lot of faults (493) HsupaL2HwModificationRejected causes bad HSPA KPI values. Description of the fault: Hardware Resource mismatching between HSUPA-L2 & L1 (RAKE) causing faults 493&470 which are causing KPI drops. Description of the correction: Two problems identified: 1) HW Resources are considered differently between L2 & L1 in the case of none users (users not yet granted HW).This causes resource mismatch. 2) HW Resources are blocked by the users which are having ongoing RL Reconfigurations. As a result there are failures with new user Set-ups. These 2 issues are corrected now from L2 side. Corrected Fault Reports: NA05041953 Bad HSPA KPI, due to lots of faults (493) HsupaL2HwModificationRejected (BTS-4 on MPT_23) NA05052597 Increase of RAB Access failure for HSUPA
Modified components: Component BTS_SC_DSP.Version 16433 *Net element *SW-type *Unit -
94 (3)
MENU
Change effects: Effects on end-user HSUPA Call Drops Effects on Operator KPI Drop Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem Disappeared Unexpected results: None
95 (3)
MENU
Title: Wrong voltage on WMHD (AISG mode) in C type configuration Version of the SW-build: WN6.0 22.12-291_K Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: BTS was manually commissioned and works in On Air state (RX signal levels are ok). Measured voltage at DIV line of every WMHD in AISG mode with or without connected RETs2.0 has value 23 V.WMHD in AISG mode should be 24 V on MAIN and 0 V at DIV line. Now voltage is 23 V instead of 0 V at Filter DIV How end user/operator could detect the problem: By measuring voltage at DIV line of every WMHD in AISG mode. Description of the fault: Measured voltage at DIV line of every WMHD in AISG mode with or without connected RETs2.0 has value 23 V.WMHD in AISG mode should be 24 V on MAIN and 0 V at DIV line. Now voltage is 23 V instead of 0 V at Filter DIV. Description of the correction: Faulty voltage is corrected by ALMAG. Corrected Fault Reports: 87761ESPE04 Wrong voltage on WMHD (AISG mode) in C type configuration Modified components: Component ALMAG_MGMT_ Pkg.sbs Version 65258 *Net element *SW-type *Unit -
96 (3)
MENU
Change effects: Effects on end-user None Effects on Operator None Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem Disappeared Unexpected results: None
97 (3)
MENU
Title: RET serial number not changed in BTS site manager after RET replacement Version of the SW-build: WN6.0 22.12-291_P Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: RET serial number wasn't changed after RET hot swap, in SEM How end user/operator could detect the problem: After hot swap (replacement) RET serial numbers are not changed in SEM Description of the correction: DB instructions updated after detecting new TILT unit. Also updating AntennaConfigData.xml enhanced Corrected Fault Reports: NA05058239 RET serial number not changed in BTS site manager after RET replacement Modified components: Component Version ALMAG_Faults_P 65901 kgs.sbs ALMAG_MGMT_ 66434 Pkg.sbs *Net element *SW-type *Unit -
98 (3)
MENU
Change effects: Effects on end-user Correct RET's serial number visible in SEM Effects on Operator Correct RET's serial number visible in SEM and in AntennaConfigData.xml Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
99 (3)
MENU
Title: Fault 1906 EFaultId_FrRfBbBusConnTransError on FRGL1/2/3 during block/unblock ESM when BTS runs on WN6.0_22.12-290_I Version of the SW-build: WN6.0 22.12-290_L Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Invalid checking for state of EMSs in LCG How end user/operator could detect the problem: Occasional alarms during RF start up. Description of the fault: State checking of ESM during fault 1906 handling was invalid. FM should check EMS faulty functionality during last 6 minutes Instead of checking changes of faulty states of ESM and alarming 1906 in last 6 minutes Description of the correction: FM will check faulty functionality of EMS during last 6 minutes not alarming.
Corrected Fault Reports: 86974ESPE04 Fault 1906 EFaultId_FrRfBbBusConnTransError on FRGL1/2/3 during block/unblock ESM when BTS runs on WN6.0_22.12-290_I Modified components: Component FORE_FDCL_Pk g.sbs Version 62375 *Net element *SW-type *Unit -
100 (3)
MENU
Change effects: Effects on end-user Extra block/unblock ESM causes cell unavailability during EMS reset Effects on Operator Extra block/unblock ESM causes cell unavailability during EMS reset Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
101 (3)
MENU
Title: RlReconfigFails with cause Transport Layer 1 Version of the SW-build: WN6.0 22.12-291_R Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: RlReconfigFails with cause Transport Layer 1 How end user/operator could detect the problem: Radio link reconfigurations fail due to "transport unspecified" Description of the fault: TUPU reject ReconfigPrep when hsdsch PDUSizeFormat is changed from type2 to type1. Description of the correction: TUPU should allow hsdsch PDUSizeFormat reconfiguration between type1 and type2. Corrected Fault Reports: 59208ESPE03 RlReconfigFails with cause Transport Layer 1 32439ESPE05 WN6 22.12-291H: nbap_rl_failure_s with the reason: unspecified trp_err Modified components: Component BTS_SC_TUP.Version 6904 *Net element *SW-type *Unit -
102 (3)
MENU
Change effects: Effects on end-user None Effects on Operator There are no RlReconfigPrepare Failure when PduSizeFormat type is reconfigured. It will improve KPI. Customer Impact Capacity & Performance
103 (3)
MENU
Title: Site autonomous reset as recovery action source of FTLB detected after IP Iub Physical Link Break with BTS SW WN6.0 22.12-291 D Version of the SW-build: WN6.0 22.12-291_N Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Site autonomous reset as recovery action. FTLB detected as source after IP IUB Physical Link Break with BTS SW WN6.0 22.12-291 _D How end user/operator could detect the problem: Site autonomous reset as recovery action after IP IUB Physical Link Break with BTS SW WN6.0 22.12-291 D Description of the fault: The FTM SMA file transfer crashes after IP IUB Physical Link Break due to the double delete in the SMA file transfer gateway. This causes the FTM crash, as a recovery action. Related feature / functionality: File transfer module (SMA) Description of the correction: Deletion of NULL pointer is protected to avoid the node crashes in some scenarios. Corrected Fault Reports: 88293ESPE04 Site autonomous reset as recovery action source of FTLB detected after IP IUB Physical Link Break with BTS SW WN6.0 22.12-291_D Modified components: Component SMA.Version *Net element nma_mwa_p r88293espe0
*SW-type -
*Unit -
104 (3)
MENU
4_crash_fix_ a70_to_a65 mp42
105 (3)
MENU
Change effects: Effects on end-user The FTM reboots and site is out of service few minutes. Effects on Operator The FTM reboots and site is out of service few minutes.
106 (3)
MENU
Title: TRS/SCF plan download from OMS EM fails Version of the SW-build: WN6.0 22.12-291_N Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: TRS/SCF plan download from OMS EM fails How end user/operator could detect the problem: Commissioning failure Description of the fault: Commissioning file download is failing in during IHSPA reconfigurations. Related feature / functionality: IHSPA Description of the correction: Reconfiguring BTS after ADA download failed. Problem fixed and reconfigurations are working successfully after ADA download. The NTP server IP has been also changed in IHSPA mode and reconfiguration is successfully.
Corrected Fault Reports: NA05064536 TRS/SCF plan download from OMS EM failure
Modified components: Component Version A65_MP42_nma_ WN6.0 psu_porting_qos_ traffic_types_ihsp a_trs_mp4_to_m p42. Nokia Siemens Networks
*Net element -
*SW-type -
*Unit -
107 (3)
MENU
108 (3)
MENU
Change effects: Effects on end-user None Effects on Operator Reconfiguration requires some more attempts. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
109 (3)
MENU
Title: Antenna line device failure after update to WN6.0_22.12-291_D Version of the SW-build: WN6.0 22.12-291_R Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Wrong handling of fault 1836 How end user/operator could detect the problem: Fault 1836 reported on WMHD LNA1 (BTS1) branch in current mode Description of the fault: Fault 1836 was reported in case of WMHD LNA1 branch in current mode but it should be filtered out. Related feature / functionality: WMHD in current mode Dependency on configuration: WMHD in current mode Description of the correction: In case of WMHD LNA1 branch in current mode reporting of Fault 1836 will be filtered out. Corrected Fault Reports: 88579ESPE04 Antenna line device failure after update to WN6.0_22.12-291_D Modified components: Component Almag_Faults.Almag_Tools.Version 66712 66712 *Net element *SW-type *Unit -
110 (3)
MENU
Change effects: Effects on end-user None Effects on Operator No unexpected 1836 fault Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
111 (3)
MENU
Title: No BB recovery on mature maintenance SW Version of the SW-build: WN6.0 22.12-291_Q Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: If all DSP sub modules are alarming then SM reset should be performed. Only FSP resets were performed. How end user/operator could detect the problem: Invalid state of FSM Description of the fault: ESM/BTS did not reset even if all DSP sub units were crashed Description of the correction: FSPs will be marked as faulty. If all FSPs are faulty then, BTS reset should be preformed Corrected Fault Reports: 32563ESPE05 No BB recovery on mature maintenance SW Modified components: Component Version FlexiFDRULES.tx 66589 t
*Net element -
*SW-type -
*Unit -
112 (3)
MENU
Change effects: Effects on end-user Longer network unavailability Effects on Operator BTS had to be restarted manually
113 (3)
MENU
Title: FSPC autonomous restart due 418 in KPI testing Version of the SW-build: WN6.0 22.12-290_Y Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: L1Tra doesn't clone user structure when performing PSCR deletion. If PSCR deletion fails, user structure is released twice (one when freeIndMsg, the other when free channelTa), which causes the user structure in database freed while the eventListPtr still exists and refers to the released memory. How end user/operator could detect the problem: When DSP crash will happens its causes decrease of KPI. Description of the fault: Two PSCR reconfiguration requests, one of ERGCH setup and the another of ERGCH deletion arrive at TX too closely. TX has no time to do the committing for the first setup when the deletion arrives. Thus TX NACK the deletion with cause = 9. And the NACK cause L1Tra pointing to a release memory. Crash will happen when the released memory is referred. Description of the correction: Add the procedure how to handle user clone when user deleted. Corrected Fault Reports: 58399ESPE03 FSPC autonomous restart due 418 in KPI testing Modified components: Component BTS_SC_DSP.Version 16132 *Net element *SW-type *Unit -
114 (3)
MENU
Change effects: Effects on end-user Possibly call drop. Effects on Operator Temporary CE degradation Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
115 (3)
MENU
Title: BTS cannot enter Test Dedicated state with BTS SW WN6.0 22.12-290_I Version of the SW-build: WN6.0 22.12-291_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Re-commissioning Time Out with BTS SW WN6.0_22.12-290_I How end user/operator could detect the problem: BTS cant enter to Test Dedicated state Description of the fault: After BTS reset BTS cannot enter Test Dedicated State. Dependency on configuration: IUB configuration: IP IUB Description of the correction After BTS reset to enter Test Dedicated State successfully and then Test Model 1 can be executed. Corrected Fault Reports: PR 86906ESPE04 BTS cannot enter Test Dedicated state on WN6.0 22.12-290 I PR 32015ESPE05 Extra BTS restart occurred at activation of WN6.0 22.12-290_L PR 87091ESPE04 Re-commissioning Time Out on package WN6.0_22.12-290_J PR 30487ESPE07 MP4.2 Site autonomous reset as recovery action reported and (0010) reported on FTLB
116 (3)
MENU
Modified components: Component Version sma_rse_32015e WN6.0 spe05_orb_mri_e xception_fix_a65 _mp42.Change effects: Effects on end-user Extra BTS resets Effects on Operator Extra BTS resets Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None *Net element *SW-type *Unit -
117 (3)
MENU
Title: Difference in Antenna line / MHA handling in MP4.1 compared to MP3 Version of the SW-build: WN6.0 22.12-291_R Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Wrong handling of 1836 fault How end user/operator could detect the problem: Fault 1836 reported on WMHD LNA1 (BTS1) branch in current mode Description of the fault: Fault 1836 was reported in case of WMHD LNA1 branch in current mode, however it should be filtered out. Related feature / functionality: WMHD in current mode Dependency on configuration: WMHD in current mode Description of the correction: Fixed handling of 1836 Corrected Fault Reports: NA05047369 Difference in Antenna line / MHA handling in MP4.1 compared to MP3 Modified components: Component Almag_Faults.Almag_Tools.Version 66712 66712 *Net element *SW-type *Unit -
118 (3)
MENU
Change effects: Effects on end-user Fault 1836 visible Effects on Operator No unexpected 1836 fault Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
119 (3)
MENU

Title: Failure in optical RP3 interface (0010) is reported on RF after site reset Version of the SW-build: WN6.0 22.12-290_J1 Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: It is not possible to shorten the 15min timer without unwanted side effects, since the timer needs to endure also normal delays during BTS start-up. It is not possible to remove the timer totally unless big changes are made in OAM and Telecom. Summary of the original problem: Unaligned interfaces in TCOM/OM/RFSW caused problems with configurations 3+3+3 and bigger. RFSW wasnt able to handle all requests in time that was expected by TCOM. TCOM reported failures (alarms 103 and 110) which caused failure in cells setup How end user/operator could detect the problem: Setup of configuration in pronto Description of the fault: Alarms 103 and 110 appear - RF module failure Description of the correction: 1. TCOM removed resending requests for carrier resources setup 2. OM handled all messages in parallel, not sequentially 3. Improvement on RFSW side to speed up requests handling Corrected Fault Reports: 84822ESPE04 Failure in optical RP3 interface (0010) is reported on RF after site reset 85988ESPE04 Alarm 1815 reported after BTS start up 86044ESPE04 Alarm 30291 Failure in optical RP3 interface reported after site reset 86441ESPE04 Delta Correction should be added to initial Delta value not each time when the same is received more than once
120 (3)
MENU
71402ESPE01 Alarm "Telecom Configuration failure (0110)" generated on configuration F333-G-118 20W
121 (3)
MENU
Modified components: Component Version MED02.11.V45 01 CCellProcedure.c 33372 ls MimoFailureAndR 33372 ecovery.ttcn CCarrierResourc 32375 eAgent.cls Multiradio_Agent 61051 _Pkg.sbs *Net element *SW-type *Unit -
Change effects: Effects on end-user Unknown Effects on Operator Unavailable cell resources
122 (3)
MENU
Title: Extension module not detected in FSMB + FSMB after MP4.0 Version of the SW-build: WN6.0 22.12-290_S Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Incorrect specification group or non-specification problem First both OPT Interfaces were successfully configured on time but messages from ESM did not received to MSM. But for some reason OPT I/f configuration take so long time that NoConnectionToUnit alarm is generated. Fault 10 to ESM causes the change of TCOM master and recovery reset. How end user/operator could detect the problem: Problems with Extension System Module detection causing fault 10 =NoConnectionToUnit and additional recovery to be performed. Description of the fault: Delay in Optical Interface configuration cause delay in Extension System module detection This resulted that fault 10 = NoConnectionToUnit was generated from Extension System Module and additional recovery reset was performed. Related feature / functionality: Extension System Module support Dependency on configuration: BTS configuration including Master - and Extension System Modules Description of the correction: Handshaking timer between MSM and ESM increased to 360 seconds. Starting of Timer is done before ESM detection begins.
123 (3)
MENU
Corrected Fault Reports: NA05048193 Extension module not detected in FSMB + FSMB after MP4.0 101592ESPE02 Extension FSMB cannot be detected after upgrade to MP4.1 Modified components: Component FlexiBTSProperti es.xml Version 1150 *Net element *SW-type *Unit -
Change effects: Effects on end-user ESM detection fails. Fault 10 = NoConnectionToUnit is generated from Extension System Module and an additional recovery reset performed. Effects on Operator ESM detection fails. Fault 10 = NoConnectionToUnit is generated from Extension System Module and an additional recovery reset performed. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
124 (3)
MENU
Title: Recovery action doesnt work after FSP crash on Flexi Rel. 1 Version of the SW-build: WN6.0 22.12-291_Z Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: BTS capacity permanently degraded after FSP crash How end user/operator could detect the problem: BTS capacity is permanently degraded Description of the fault: After FSP crash proper recovery action wasn't executed. Dependency on configuration: HW_rel1 only Workaround: BTS reset after FSP crash Description of the correction: CONF subsystem is registered for DYN_StatusWSPFaultActive dynamic parameter change in DB Corrected Fault Reports: NA05062940 Recovery action doesnt work after FSP crash on Flexi Rel. 1 Modified components: Component Version FlexiFDRULES.tx 66594 t CONF_Pkg.sbs 68424 *Net element *SW-type *Unit -
125 (3)
MENU
Change effects: Effects on end-user BTS capacity permanently degraded Effects on Operator BTS capacity permanently degraded Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
126 (3)
MENU
Title: BTS delays 15 min to report fault 94 Version of the SW-build: WN6.0 22.12-291_M Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: BTS delays 15 min to report faults 94 and 23. Reporting of faults could be faster without waiting for RFs availability due to unknown type or incompatible SW How end user/operator could detect the problem: BTS does not report availability of RFs during 15 min delay. Description of the fault: After hot insert RF module faults incompatible SW (fault 23) or unknown type (fault 94) activated and ReadyCheck function (availability check in start up) is waiting for timeout value for RF unit configuration which will never come. Description of the correction: Skipping of LTX unit in ReadyCheck function under specific conditions to avoid faults (23 and 94) Corrected Fault Reports: 87001ESPE04 BTS delays 15min to report fault 94 Modified components: Component Version CONF_Pkg.sbs 64766 CONF_TelecomC 64766 onf_Pkg.sbs *Net element *SW-type *Unit -
127 (3)
MENU
Change effects: Effects on end-user Faults are visible 15 min Effects on Operator Faults are visible 15 min Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
128 (3)
MENU
Title: Faulty measurements reports on RF2 after RF1 unblock Version of the SW-build: WN6.0 22.12-292_B Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: UPD power report subscription is removed for one carrier. RFM doesn't send reports for all other carriers on the same pipe. How end user/operator could detect the problem: Most of cells (4+4+4) are configured and only few of cells are locked Description of the fault: During UDP power subscription removal timer for slow measurements (one timer per pipe) was not restarted properly Dependency on configuration: All Description of the correction: Timer restart fixed. Corrected Fault Reports: 88775ESPE04 Measurements are broken on RF2 after RF1 unblock 32671ESPE05 Some cell goes to faulty with "RF module failure" after other cells locked
129 (3)
MENU
Modified components: Component BTSRFM.Version BTSRFM5932 *Net element *SW-type *Unit -
Change effects: Effects on end-user Some cells locked due to fault RF Module failure Effects on Operator Some cells locked due to fault RF Module failure
130 (3)
MENU
Title: Calls not possible after FSP reset caused by MAC-HS crash Version of the SW-build: WN6.0 22.12-291_W Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: CCH allocated even if there is no place for DCH How end user/operator could detect the problem: Cell allocation was possible even when there were no other resources for any further DCH usage Description of the fault: Cell was allocated wrongly using Free Faraday without any check of presence of other HW resources Description of the correction: During allocation procedure of CCH, GMR is checking if there is free space available for DCH Corrected Fault Reports: 87235ESPE04 Calls not possible after FSP reset caused by MAC-HS crash Modified components: Component Version 3g_cell_and_wa 36309 m_mapping.spd GRM_mt_test_su 36309 ite.itex *Net element *SW-type *Unit -
131 (3)
MENU
Change effects: Effects on end-user Cell allocation possible even if there were no other HW resources for any further DCH usage Effects on Operator Cell allocation possible even if there were no other HW resources for any further DCH usage Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
132 (3)
MENU
Title: Rx signal level failure (0133) faults appeared after BTS start up Version of the SW-build: WN6.0 22.12-291_S Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: RX signal to low. How end user/operator could detect the problem: Calls were not possible through some cells or signal level reduced. Description of the fault: Base Band configuration was wrongly selected. Configuration A was selected instead of configuration B Description of the correction: Base Band configuration selection repaired. When Ant1 and Ant3 used, antenna mapping type B selected Corrected Fault Reports: 88635ESPE04 Rx signal level failure (0133) faults appeared after BTS start up Modified components: Component BBC_pkg.sbs Version 66868 *Net element *SW-type *Unit -
133 (3)
MENU
Change effects: Effects on end-user Calls not possible or signal power reduced. Effects on Operator Cells are not fully operational. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
134 (3)
MENU
Title: Dual Cell Info missing in RL Setup Response for Rel1 and Rel2 SM HW Version of the SW-build: WN6.0 22.12-290_P1 Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: During DC call setup procedure BTS send RL Setup Response without secondary cell info. Then RRC will release the RL with cause needed param missing. Problem occurs when EDCH is 10ms in DC call setup, if EDCH is 2ms, DC call can be setup successfully. How end user/operator could detect the problem: HS AFR counter increases, CE resources not utilized Description of the fault: If DCH part of a HSPA user is located on FLEXI Rel1 and HSDPA and HSUPA parts are located on FLEXI Rel2. In case of DCH allocation and TCOM RLH HW type check are in Flexi Rel1 and DC-HSDPA request arrives to Flexi Rel1 then FLEXI Rel1 DC-HSDPA info isnt forwarded to HSDPA card. Description of the correction: HW Type will be checked only on HSDPA card if User is not at same HW card. HW Type will not be checked if the initialization of DC call set up and RL response are done at different HSDPA card Corrected Fault Reports: 100045ESPE02 Dual Cell Info missing in RL Setup Response for Rel1 and Rel2 SM HW Modified components: Component 3grlcontroller.spr Version 32895 *Net element *SW-type *Unit -
135 (3)
MENU
Change effects: Effects on end-user HSDPA performance degraded Effects on Operator HSDPA performance degraded Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
136 (3)
MENU
Title: Application error window is pop upped when SW version displayed in SEM Version of the SW-build: WN6.0 22.12-290_X Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Description of the fault: Wrong checking of unit that was removed, this affects CurrentBD.xml SW version info do not display on SEM How end user/operator could detect the problem: SW version info cannot be seen at SEM Description of the fault: CurrentBD.xml is not properly filled Description of the correction: Version Report Creator changes to be reverted to previous version
Corrected Fault Reports: 86966ESPE04 Application error window is pop upped when SW version displayed in SEM 86961ESPE04 The value for SW release version on site manager (6.2.2279) is empty. 87024ESPE04 SW version info do not display on SEM on WN6.0 22.12-290 J1 87092ESPE04 Unexpected Problem on SW version with package WN6.0 22.12-290_K 87175ESPE04 SW version cannot be seen on SEM after WN6.0_22.12-290_L upgrade
137 (3)
MENU
138 (3)
MENU
Modified components: Component Version FORE_FCM_Pkg 62659 .sbs MT_FORE_FCM. UC23 Change effects: Effects on end-user SW version not displayed Effects on Operator SW version not displayed Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None *Net element *SW-type *Unit -
139 (3)
MENU
Title: Not operational BTS (Kernel Error Handler, Process name: RHAPSODYSYSTEMTHREAD) Version of the SW-build: WN6.0 22.12-290_J1 Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Kernel Error after SW version report inquiry How end user/operator could detect the problem: BTS is not operational due to Kernel Error. Extension- and RF modules can't be pinged. Description of the fault: SW version response from extension module comes after site reset Workaround: BTS hard reset. Description of the correction: Preventing Kernel by checking that SW version response has correct information and Extension and R units are recognized Corrected Fault Reports: 85057ESPE04 Not operational BTS (Kernel Error Handler, Process name: RHAPSODYSYSTEMTHREAD) Modified components: Component Version FORE_FCM_Pkg 62058 .sbs MT_FORE_FCM. UC23 *Net element *SW-type *Unit -
140 (3)
MENU
Change effects: Effects on end-user BTS is not operational Effects on Operator BTS is not operational Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
141 (3)
MENU
Title: BTS internal SW management problem from FSMD SW MP4.04-154C Version of the SW-build: WN6.0 22.12-290 Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Internal DSP SW downloading problem Increased timeout while waiting for response from HWAPI How end user/operator could detect the problem: Start up BTS Description of the fault: Internal DSP SW downloading problem Description of the correction: Additional mechanism for downloading of DSP SW for DSP sub units Corrected Fault Reports: NA05020272 BTS internal SW management problem from FSMD SW MP4.04-154C Modified components: Component SWMG.sbs Version 52526 *Net element *SW-type *Unit -
142 (3)
MENU
Change effects: Effects on end-user None Effects on Operator No negative effect. Files will be downloaded successfully on FSP. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
Title: RF Unit does not reset as recovery action when all TX's under RF are faulty Version of the SW-build: WN6.0 22.12-291_F Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: RF was not resetting if there were working RXs How end user/operator could detect the problem: Loss of all TXs did not cause auto RF reset
143 (3)
MENU
Description of the fault: When all TX's under one RF are faulty, unit is degraded instead of faulty and there is no recovery reset as expected. Workaround: None Description of the correction: RF which doesn't have any working TX should be reset as recovery action. Corrected Fault Reports: 87768ESPE04 RF Unit does not reset as recovery action when all TX's under RF are faulty
Modified components: Component FORE_FDCL_Pk g.sbs Version 64611 *Net element *SW-type *Unit -
144 (3)
MENU
Change effects: Effects on end-user Cell performance degraded Effects on Operator Cell performance degraded Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
145 (3)
MENU
Title: BTS block/unblock Start-up time out on package WN6.0 22.12-290 J Version of the SW-build: WN6.0 22.12-291_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Re-commission Time Out with package WN6.0_22.12-290_J How end user/operator could detect the problem: BTS Reset timer limit 300s is exceeded. Description of the fault: Commission seems to ok, but most of the times re-commission is timed out. Related feature / functionality: Commissioning, SMA Dependency on configuration: IUB configuration: IP IUB Description of the correction: BTS Reset timer limit 300s is not exceeded to avoid delays. Corrected Fault Reports: 87147ESPE04 BTS block/unblock Start-up time out on package WN6.0 22.12-290 J Modified components: Component Version sma_rse_32015e WN6.0 spe05_orb_mri_e xception_fix_a65 _mp42.*Net element *SW-type *Unit -
146 (3)
MENU
Change effects: Effects on end-user Re-commission is timed out. Effects on Operator Re-commission is timed out. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
147 (3)
MENU
Title: BTS with SW WN6.0 22.12-273 can't be operated (reset or SWDL or other operations), after manual stop SWDL from SEM Version of the SW-build: WN6.0 22.12-290_W Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Stopping SW download manually from SEM causes BTS to be not operated state. How end user/operator could detect the problem: Manual SW download stop causes BTS to be not operated state. Description of the fault: Manual SW download stop causes BTS to be not operated state. SW down load and reset operations do not work. Power off is only recovery action that can be performed. Workaround: Power off/power on BTS Description of the correction: FORE_SM does not send FileUpdateReq message, when SW DL is stopped. BuildAbortReq response is always "ACK" when received. Corrected Fault Reports: 83805ESPE04 BTS SW WN6.0 22.12-273 can't be operated (reset or SWDL or other operations), after manual stop SWDL from SEM Modified components: Component SM_FILE_HAND LING_Pkg.sbs Version 62567 *Net element *SW-type *Unit -
148 (3)
MENU
Change effects: Effects on end-user BTS is not in operating state. Effects on Operator BTS is not in operating state. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
149 (3)
MENU
Title: Antenna Device Failure (10) fault is active for all cells Version of the SW-build: WN6.0 22.12-290_B Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Antenna Device Failure (10) fault is active for all cells How end user/operator could detect the problem: Alarm Antenna Device Failure (10) is visible in SEM and OMS. Description of the fault: Antenna Device Failure (10) means that there is no connection to Filter unit. Filter unit with processor is not exists in AAS. AAS has passive filter (duplexer). RF Modules has Filter module which contains: passive filter, processor (for AISG, filter tuning control etc.) Description of the correction: RF filter Configurations 1 changed to 0 for FAGE and FAGF; Is3GPP. Capable Yes changed to No for Ant1 of FAGE, FADM, FAGF, FAGO and FAGP. Corrected Fault Reports: 82963ESPE04 Antenna Device Failure (10) fault is active for all cells
Modified components: Component FlexiBTSProperti es.xml Version 857 *Net element *SW-type *Unit -
150 (3)
MENU
Change effects: Effects on end-user Alarm is only visible. All BTS functionalities are working. Effects on Operator Alarm is only visible. All BTS functionalities are working. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
151 (3)
MENU
Title: Discrepancy in CE license information Version of the SW-build: WN6.0 22.12-291_P Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Used CEs were calculated as minus value due to different interpretation of relation in two compilers How end user/operator could detect the problem: Change in available CEs. Description of the fault: Different interpretation of relation in two compilers Related feature / functionality: Licences Dependency on configuration: Flexi only Workaround: Not possible. Description of the correction: Used CEs after CCH allocation are updated immediately without waiting for report. Corrected Fault Reports: NA04948324 Discrepancy in CE license information
152 (3)
MENU
Modified components: Component Version 3g_cell_and_wa 35956 m_mapping.spd CalculateUsedCE 35956 sInRel2.spd grm3g.sun 35956 GRM_mt_test_su 35956 ite.itex full_GRM_mt_tes 35956 t_suite_flexi.cfg Change effects: Effects on end-user Performance varying due to CE changes Effects on Operator Performance varying due to CE changes Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None *Net element *SW-type *Unit -
153 (3)
MENU
Title: Calls are not possible through LCG1 after spontaneous reset with F444-G-118 Version of the SW-build: WN6.0 22.12-291_P Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: No calls possible on whole LCG How end user/operator could detect the problem: LCG does not work Description of the fault: EXT2 port on RF has wrong timing set Dependency on configuration: Configuration with two optic links to one RF (if v3) Description of the correction: Turn off unnecessary functionality Corrected Fault Reports: 87238ESPE04 Calls are not possible through LCG1 after spontaneous reset with F444-G-118 Modified components: Component BBC_pkg.sbs Version 66468 *Net element *SW-type *Unit -
Change effects: Effects on end-user

154 (3)
MENU
Performance degraded Effects on Operator Performance degraded Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
155 (3)
MENU
Title: MIMO + VAM cell is functional but not operational when "Primary TX" is faulty Version of the SW-build: WN6.0 22.12-290_X Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: MIMO + VAM cell is "functional but not operational" when "Primary TX" is faulty How end user/operator could detect the problem: Cells are not operational and calls impossible. Description of the fault: BBC should set Primary TX of both TX on same cell. Dependency on configuration: Configuration with MIMO cells Description of the correction: BBC set Primary TX of both TX on same cell. Corrected Fault Reports: 87132ESPE04 MIMO + VAM cell is functional but not operational when "Primary TX" is faulty Modified components: Component BBC_pkg.sbs Version 63472 *Net element *SW-type *Unit -
156 (3)
MENU
Change effects: Effects on end-user None Effects on Operator MIMO + VAM cells in state functional but not operational and service decreasing Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
157 (3)
MENU
Title: The recovery action was not performed after Fault 125 rise up and the related faults cant be seen at BTS Site Manager although they exist in logs. Version of the SW-build: WN6.0 22.12-291_D Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Recovery action was not performed after Fault 125 rose up How end user/operator could detect the problem: The recovery action was not performed after Fault 125 rise up and the related faults cant be seen at BTS Site Manager although they exist in logs. Description of the fault: Recovery action was not performed after Fault 125 rose up Description of the correction: If all cells are faulty due to fault 125, RF should be reset. When 125 fault will cancel, affected cells should be enabled (working). Corrected Fault Reports: 83765ESPE04 The recovery action was not performed after Fault 125 rise up, and BTS Site Manager cannot see the related faults turn up although they exist in logs. 69733ESPE01 Cell didn't set to faulty status after EFault (125) provoked more than 60 seconds Modified components: Component Version FlexiFDrules.txt 64030 UHND_AlarmHan 64030 dling.sbs *Net element *SW-type *Unit -
158 (3)
MENU
Change effects: Effects on end-user Related Cells cannot be recovered. Effects on Operator Fault 125 is not reported to SEM and TX recovery action is halt. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
159 (3)
MENU
Title: BTS internal SW management problem from FTM Version of the SW-build: WN6.0 22.12-291_N Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: SQUASHSFS error is seen during SW activation How end user/operator could detect the problem: Software upgrade/downgrade and activating, but is occasional Description of the fault: Post mortem dumps were written into the flash (log partition) before the FPGA was loaded. No problems with FCTB core boards (which have an initial FPGA) but problem appears on FTCC core boards. Occasionally the flash partition was not accessible properly, leading to the SquashFS error. Workaround: Reset the unit Description of the correction: Start up script changed. Writing post mortem dumps into flash (log partition) after FPGA is loaded. Corrected Fault Reports: NA05064399 BTS internal SW management problem from FTM Modified components: Component Version *Net element os_nis_27213_po FTM_A65_M rting_from_a65_t P42_239.00 o_a65_mp42.*SW-type *Unit -
160 (3)
MENU
Change effects: Effects on end-user Sometimes card ready but will not be noticed. Which will cause the card multiple reset and it leads to site outage for few minutes. Effects on Operator Extra reset needed to get the unit working. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
161 (3)
MENU
Title: WBTS alarm 7654-FPGA and SW update failed (CELL OPERATION DEGRADED) Version of the SW-build: WN6.0 22.12-292_A Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: RF triggered 1932 fault How end user/operator could detect the problem: Fault 1932 visible in BTS SM Description of the fault: Wrong CSSA version uploaded in factory caused FPGA SW update failure. Related feature / functionality: Occurred only affected RF HW Dependency on configuration: Occurred only affected RF HW Workaround: None Description of the correction: Workaround solution implemented in code to avoid triggering 1932 in case failed CSSA update.
Corrected Fault Reports: NA04979832 WBTSB alarm 7654-FPGA and SW update failed (CELL OPERATION DEGRADED) NA05079355 FPGA SW update failed on WBTS.
162 (3)
MENU
Modified components: Component V45.Version 01 *Net element *SW-type *Unit -
Change effects: Effects on end-user Fault 1932 visible in BTS SM Effects on Operator Fault 1932 visible in BTS SM Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
163 (3)
MENU
Title: Temporary degraded HSDPA accessibility in 1st sector SW MP4-154C Version of the SW-build: WN6.0 22.12-290_W Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Temporary degraded HSDPA accessibility in 1st sector SW MP4-154C How end user/operator could detect the problem: Temporary degraded HSDPA accessibility Description of the fault: OSE does not give time to TUP_AALM while TUP_CM is busy with bunch of requests. Sleeping TUP_CM does not do the job. Description of the correction: Improved mechanism implemented to force switching between TUP_Cmand TUP_Aalm. Faster IP routing process between TCOM and FTM modified.
Corrected Fault Reports: NA05022027 Temporary degraded HSDPA accessibility in 1st sector SW MP4-154C Modified components: Component SS_TUPC.Version 6533 *Net element *SW-type *Unit -
164 (3)
MENU
Change effects: Effects on end-user Decreased number of RL Setup and RL Reconfiguration failure Effects on Operator Decreased number of RL Setup and RL Re configuration failure Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
165 (3)
MENU
Title: RF module failures (1841, 0103) after commissioning RF from shared to 3G dedicated Version of the SW-build: WN6.0 22.12-290_X Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: During BTS start up RF Module failure (1841) activated due to broken communication between RF Module and Filter. How end user/operator could detect the problem: Alarm is visible on BTSSM. All cells related to this Filter (pipes & antennas) are disabled. Proper alarm for this action should be also visible. Description of the fault: ARP messages caused very high Ethernet traffic (also because of configuration). Filter SW was not able to handle such a big load of data. This was leading extreme usage of Rx Eth module and unit reset by Watch dog timer. Description of the correction: Changes in Rx Eth module in Filter SW related to handling incoming Ethernet frames. Corrected Fault Reports: 86633ESPE04 RF sharing: RF module failures (1841, 0103) after commissioning RF from shared to 3G dedicated Modified components: Component V48.Version 01 *Net element *SW-type *Unit -
166 (3)
MENU
Change effects: Effects on end-user None Effects on Operator Alarms visible at BTSSM and cells disabled Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
167 (3)
MENU
Title: WCDMA test model cannot be started at lowest supported carrier frequency 937.4 MHz with FXDJ. Version of the SW-build: WN6.0 22.12-291_K Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Carrier allocation at 937.4 MHz on FXDJ is rejected by RFM SW. How end user/operator could detect the problem: Cell is not created. Description of the fault: Bug in validation of carrier allocation procedure in RFM SW. Description of the correction: Problem visible only when TX and RX carrier bandwidth are different In this particular case it was 4.8 MHz for Rx and 4.2 MHz for TX. Such configuration was not tested internally by RF SW team. Corrected Fault Reports: 71945ESPE01 WCDMA test model cannot be started at lowest supported carrier frequency 937.4 MHz with FXDJ. Modified components: Component V13G.Version 01 *Net element *SW-type *Unit -
168 (3)
MENU
Change effects: Effects on end-user Cell is not created. Effects on Operator Cell is not created. Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
169 (3)
MENU
Title: Unknown HW resource alarm blocks WN SW upgrade Version of the SW-build: WN6.0 22.12-292_E Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Severe alarm blocks cell operation How end user/operator could detect the problem: Cell is faulty Description of the fault: Severe cell alarm is raised Description of the correction: Fault 7654 will be sent instead of 7653 Corrected Fault Reports: NA05042393 Unknown HW resource alarm blocks WN SW upgrade Modified components: Component FlexiFDRULES.x ml Version 69560 *Net element *SW-type *Unit -
170 (3)
MENU
Change effects: Effects on end-user BTS performance degraded due to faulty cell Effects on Operator BTS performance degraded due to faulty cell
171 (3)
MENU
Title: Error in file server during SW down load in file server alarm occurred Version of the SW-build: FTM_A65_MP42 _239.00 Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Error in file server during SW down load in file server alarm occurred How end user/operator could detect the problem: Error in file server during SW down load in file server alarm occurred Description of the fault: While downloading software, error during SW down load in file server was generated Description of the correction: The buffer handling modified and fixed to solve file recovery failure Corrected Fault Reports: NA05063722 Error in file server during SW download alarm occurred Modified components: Component Version *Net element sma_mks_83957 FTM_A65_M espe04_http_dow P42 nlaod_fix_a65_to _a65_mp3.*SW-type *Unit -
172 (3)
MENU
Change effects: Effects on end-user None Effects on Operator Extra SW down load Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
173 (3)
MENU
Title: Baseband allocation - 2xFSME+3xFRGQ Version of the SW-build: WN6.0 22.12-290_E Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Data from TX2 on RF2 and TX5 on RF3 were in collision while they were routed in MUKSU on ESM to MSM How end user/operator could detect the problem: RF module faulty and calls not possible Dependency on configuration: 3+3+3 with RRH Description of the correction (incl. risk analysis): MUKSU routing was changed Corrected Fault Reports: NA05044879 Baseband allocation - 2xFSME+3xFRGQ Modified components: Component BBC_pkg.sbs Version *Net element BBC_pkg.sb s *SW-type *Unit -
174 (3)
MENU
Change effects: Effects on end-user Calls not possible Effects on Operator BTS functionality is degraded Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
175 (3)
MENU
Title: BTS HW failures during SW download. Version of the SW-build: WN6.0 22.12-207 Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: RF/TCOM cannot handle rapid sequential LCR indications How end user/operator could detect the problem: RF modules Block/Unblock after RF module resets repeatedly Description of the fault: LCR indications are sent is too rapidly so RF/TCOM cannot handle LCR indications fast enough. RF cannot recover after RF reset. Description of the correction: Added 300s delay to LCR indication sending and removed some unnecessary looping while sending HW configuration changes Corrected Fault Reports: NA05036785 BTS HW failures during SW download. Modified components: Component CONF_PKG.CONF_TeleCOM CONF.Version 46318 46319 *Net element *SW-type *Unit -
176 (3)
MENU
Change effects: Effects on end-user RF module resets repeatedly Effects on Operator RF module resets repeatedly Testing Instructions for the change Pre-requirements: None Test execution: Passed Tested in MP4.1 (WN6.0 22.12-207) release tests CN for MP4.1 not available.CN created for MP4.2 CN document. Expected results: Problem does not exists Unexpected results: None
177 (3)
MENU
Title: F4 UL Noise Issue with FXFA RRU configuration Version of the SW-build: WN6.0 22.12-290_L Valid for Product(s): Flexi WCDMA Base Station References: Reason for the Change Note: Summary of the original problem: Wrong configuration sent to RF causes a lot of collision on MUSKU and some cells wont work. How end user/operator could detect the problem: Some cells are sleeping cell so calls are not possible via those cells Description of the fault: Wrong configuration sent to RF causes a lot of collision on MUSKU and some cells wont work. Wrong MUKSU configuration causes one sleeping cell because both RX have collision on problematic cell. Description of the correction: Routing tables corrected. Corrected Fault Reports: NA05066882 F4 UL Noise Issue with FXFA RRU configuration Modified components: Component BBC_pkg.sbs Version 62363 *Net element *SW-type *Unit -
178 (3)
MENU
Change effects: Effects on end-user BTS performance degraded due to sleeping cells Effects on Operator BTS performance degraded due to sleeping cells
179 (3)
MENU
Title: After BTS software activation, BTS does not come up properly. Version of the SW-build: WN6.0 22.12-290_X Valid for Product(s): Flexi WCDMA BTS References: Reason for the Change Note: Summary of the original problem: TRS module was not active (question mark seen in SEM) after update How end user/operator could detect the problem: Perform SW update from 6.0 to 7.0 or otherwise (very rare problem) Description of the fault: File SiteEM.xml was not updated during activation and SEM started with old version. File was not updated because there was synchronization problem, ex. two components were accessing file same time. Description of the correction: Additional loop was added which retries to write file if previous try was failed Corrected Fault Reports: 64529ESPE01 After BTS software activation, BTS does not come up properly. 67279ESPE01 BTS doesnt co-operate with proper SEM 82729ESPE04 SEM version can't be transferred to 6.0 after WBTS downgrade from WN7.0 1104 354 00 to WN6.0 22.12-263 83703ESPE04 SEM version not change and Transmission commission data missed when upgrading WN6.0 22.11-171 to WN7.0_1104_435_00 84645ESPE04
180 (3)
MENU
Problem with TRS connection after software download on WN10441
181 (3)
MENU
Modified components: Component FLSH.sbs Version 63382 *Net element *SW-type *Unit -
Change effects: Effects on end-user None Effects on Operator File SiteEM.xml was not updated when upgrading BTS SW Testing Instructions for the change Pre-requirements: None Test execution: Passed Expected results: Problem disappeared Unexpected results: None
182 (3)

WN6 0 MP4 2 SW CN Document

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

WN6 0 MP4 2 SW CN Document

Transféré par

Droits d'auteur :

Formats disponibles

MENU

Change Note Forms

WCDMA BTS CN-id: WN50048

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60757

Nokia Siemens Networks

Modified components: Component V12X.Version 01 *Net element *SW-type *Unit -

Nokia Siemens Networks

WCDMA BTS CN-id: WN60769

Nokia Siemens Networks

WCDMA BTS CN-id: WN60797

Nokia Siemens Networks

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60798

Change effects: Effects on end-user None Effects on Operator None

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60799

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60801

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60822

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60827

Nokia Siemens Networks

Nokia Siemens Networks

WCDAM BTS CN-id: WN60829

Nokia Siemens Networks

Change effects: Effects on end-user None Effects on Operator None

Nokia Siemens Networks

WCDMA BTS CN-id: WN60830

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60833

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60834

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60836

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60837

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60838

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60839

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60842

Nokia Siemens Networks

Nokia Siemens Networks

WCDMA BTS CN-id: WN60843

Nokia Siemens Networks

Unexpected results: None

Nokia Siemens Networks

Modified components: Component V12X.Version 01 Net element SW-type *Unit -