WN6 0 PP2 03 SW CN Document

Change Note Forms
WCDMA BTS
WN6.0 PP2.03 (WN6.0 22.9-23_D)

WCDMA BTS
CN-id: 60229
Title:
Cells down during cold weather due to Radio module failure (125) -alarm
Version of the SW-build:

WN6.0 22.9-23_D
Valid for Product(s):

Flexi WCDMA Base Station
References:
Reason for the Change Note:

Problem:
It was noticed during freezing weather, that some of the sites equipped with FRGF put cells
faulty with raw alarm 125 (cell gain reduced). The BTS were updated to WN6.0 PP2.01
shortly. Earlier, during past 2-3 months, this fault was not playing a role in network. The
failure was initiated, when RF module was reseted due to BTS sw upgrade or autonomous
recovery reset.
As a workaround BTS SW was downgraded to WN6.0 PP1.2, which brought the cells back
on-air.
Root cause:
The root cause of the problem was caused by improper mode switching, which did not
allowed transmission to begin.
During radio module start up in low temperature, a special heating procedure is being
performed. This phase is necessary to protect the temperature-sensitive components.
Power amplifiers are being used as the heating element. When the procedure is over, these
amplifiers should be switched to their regular operation mode (transmitting).
The problem exists only with Flexi Rel2 RF modules.
Correction:
Mode switching from heating state to transmission enabled was corrected .
Effects on end users

Capacity & Performance: No services under affected cell
Effects on operator
Capacity & Performance: Cell availability
© Nokia Siemens Networks Company Confidential 2 (36)

Corrected Fault Reports:
NA04818225 FRGF coming faulty with 125 alarm

NA04819963 RF module failure
Modified components:
Component Version *Net element *SW-type *Unit

FRM02.08 R05 - - -

WCDMA BTS
CN-id: 60230
Title:
Radio module failures of FRGF units

WN6.0 22.9-23_D

References:

Problem:
Radio module failure alarms (alarm id 1921, 1907, 1909) were occurring occasionally on
FRGF modules operating in dual carrier mode. Majority of the failures are initiated after
resetting BTS or RNC.
Analysis:
It was found that runtime mode of digital adaptive pre distortion (DAPD) can be run from two
different reasons, and furthermore there was some probability that these events happen in
one after another. This allowed a situation at start of runtime mode on DAPD2 (after
second carrier activation), that there were two instances of the second DAPD's runtime
mode trying to perform Nulling LO and delay synchronization. This led delay estimation to
fail, because two 'instances' were trying to work on the same RF pipe.
Correction:
Problem is eliminated by allowing only one instance to initiate DAPD runtime mode at a
time.
Effects on end users

Capacity & Performance: Temporarily reduced services
Effects on operator
Operation and Maintenance: Unnecessary alarms, increase in recovery actions
Capacity & Performance: Cell availability
NA04773876 Persistent failures of FRGF1 units

52659ESPE01 RF module failure (1907)
44267ESPE03 Major part of RF module failure (1909) alarm is seen in network
68267ESPE04 RF module failure alarm
76195ESPE02 FSMD: RF module failure (1921) after RNC manual reset.

66262ESPE04 CN4298: RF module failure

FRM02.08 R05 - - -
WN6.0 PP2.02 (WN6.0 22.9-23_B) correction
WCDMA BTS
CN-id: WN60228
Title:
Cells not always coming up at once with BTS software WN6.0 PP2.01

WN6.0 22.9-23_A

UltraSite WCDMA Base Station
References:

It has been noticed, that the message structure in WN6.0 PP2.01 TUP UltraSite SW is not
fully compatible with the other BTS SW system components, e.g. Telecom, O&M, DSP

78555ESPE02
Cells not coming up with BTS software PP2.01 WN6.0 22.9-23

-.- - - - -

Change effects:
Effects on end-user
Effects on Operator
Other effects
New functionality
Customer Impact
Due to the nature of the problem, it is difficult to define all the unexpected problems and
consequences that may occur for UltraSite BTS. So far it has been analyzed from the logs
that the problem causes occasional BTS cell set-up failures but also call performance
degradation is expected
Testing Instructions for the change
Pre-requirements:
-
Test execution:
-
Expected results:
-
Unexpected results:
-

WN6.0 PP2.01 (WN6.0 22.9-23) corrections
WCDMA BTS
CN-id: WN60193
Title:
External MHA (Other BTS MHA) greyed out in Site Manager view

WN6.0 22.9-7

References:

Problem: External MHA (Other BTS MHA) greyed out in Site Manager view
Root cause: Problem in alarm handling and MHA state update for external MHA (other BTS
MHA). Start timer for 'No connection to MHA unit' was missing and also MHA state was
incorrectly updated as 'lost' state to the database.
Correction: 'No connection to MHA unit' alarm start timer added and MHA state update to
the data base corrected.

26437ESPE05
External MHA (Other BTS MHA) greyed out in Site Manager view

FlexiFDRules.txt f_19#0.27 - - -
Change effects:
Effects on end-user

Effects on Operator
Other effects
New functionality
Customer Impact
Operation & Maintenance: MHA greyed out in BTS Site Manager view.
Pre-requirements:
Test execution:
This correction cannot be tested using the operator interface commands. The correction is
tested internally in Nokia Siemens Networks test lab and proved to be fully functional
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60195
Title:
Mismatch with CPC counters

WN6.0 19.5-199
WN6.0 22.9-16

References:

Problem: CPC counter problem. SUM_CPC_CONFIGURED_USERS is smaller than
SUM_ACTIVE_CPC_USERS
Root cause: SUM_ACTIVE_CPC_USERS (M5000C285) were incorrectly incremented.

When the last UE in the BTS was deleted, the new TTI function in CPCM was not called
resulting that the SUM_ACTIVE_CPC_USERS was not updated. This leads to situation
leading where SUM_ACTIVE_CPC_USERS can exceed the value of
SUM_CPC_CONFIGURED_USERS (M5000C288).
Correction: When the last UE is deleted from the BTS, SUM_ACTIVE_CPC_USERS is set
to 0.

NA04787223, 67676ESPE04
Mismatch with CPC counters SUM_CPC_CONFIGURED_USERS is smaller than
SUM_ACTIVE_CPC_USERS

SC_DSP.- r4482 - - -

Change effects:
Effects on end-user
Effects on Operator
Other effects
New functionality
Customer Impact
Operability: SUM_ACTIVE_CPC_USERS in not updated correctly.
Pre-requirements:
Test execution:
This correction cannot be tested using the operator interface commands. The correction is
tested internally in Nokia Siemens Networks test lab and proved to be fully functional
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60196
Title:
License missing alarm even though licence status as active

WN6.0 22.9-16

References:

Problem:
O&M didn't respond in time to telecom licence request, so BTS Site Manager displayed
incorrect license status.
Root cause:
Timer was too short.
Correction:
Timer was increased.

26324ESPE05
License missing alarm even though licence status as active
67254ESPE04
60W license not being activated
67272ESPE04
FRGP: Fault Branch Activation License missing in Site Manager despite license is active
53165ESPE01
Branch activation licence missing after power reset

CONF_TelecomC f_mp2#0.1 - - -
onf_pkg.sbs

Change effects:
Effects on end-user
Effects on Operator
Other effects
New functionality
Customer Impact
Operability:
BTS Site Manager is displaying wrong information.
Pre-requirements:
-
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60197
Title:
MHA and RET not always recognized after BTS restart

WN6.0 19.5-196

References:

Problem:
Sometimes after BTS restart MHA and RET devices are not recognized properly.
Root cause:
Some Antenna Line Devices (ALD) are not responding to XID Address Assignment
command.
Correction:
After first unsuccessful try the DC power is switched off / on and the whole procedure of
configure ALD devices is restarted

NA04711841
MHA and RET not always recognized after BTS restart.

ALMAG_CC.- f_mp2#1 - - -
ALMAG_MGMT.- f_mp2#1 - - -
FlexiFDRules.tst f_mp2#1 - - -
Change effects:
Effects on end-user
Effects on Operator

Other effects
New functionality
Customer Impact
Capacity & Performance: MHA and RET devices are out of use causing degraded cell
availability.
Pre-requirements:
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60198
Title:
7653 Too many carriers allocated for LPA

WN6.0 22.9-18

References:

Problem:
7653 Too many carriers allocated for LPA causing that ROC configuration doesn't work.
Root cause:
Local Cell Antenna mapping message was filled incorrectly in start-up when using ROC
configurations.
Correction:
Local Cell Antenna mapping message filling corrected.

NA04748335: 7653 Too many carriers allocated for LPA

FORE_CDM_Pkg um_19#0.13 - - -
.sbs
Change effects:
Effects on end-user
Effects on Operator
Other effects
New functionality

Customer Impact
Operability:
ROC configuration doesn't work.
Pre-requirements:
-
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60199
Title:
Site Performing Autonomous Restarts

WN6.0 22.9-20

References:

Problem: Site was performing multiple autonomous restarts. DSP errors were seen.
Root cause: Rake has not received all the BB_LOOP_DELAY_REPORT_REQ_MSG before
Telecom startup has begun. This was due to missing O&M requirement which allowed O&M
to mark FSP's as configured before it has configured loop delays to Faraday processors.
Correction: O&M implementation was modified so that RTT loop delays needs to configured
to all FSP Faradays before FSP is marked as "configured"

NA04764681
RU20 Performing Autonomous Restarts
NA04782460:
FSPC autonomous reset with fault code 1806

FSPB_Agent_Pk f_mp2#0.1 - - -
g.sbs
Change effects:
Effects on end-user
Possibly dropped call.
Effects on Operator
Site was performing multiple autonomous restarts.

Other effects
New functionality
Customer Impact
Pre-requirements:
-
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60201
Title:
Spontaneous FRGG reset

WN6.0 22.9-16

References:

Problem:
Spontaneous FRGG restart.
Root cause:
Problem was caused by the memory leak in FRGG unit SW. Problem occurs when System
Module sends high amount of broadcast messages to the FRGG unit within short period of
time. Memory leak causes problems in Ethernet connection and FRGG is spontaneously
restarted.
Correction:
Memory leak has been corrected.

NA04786513
FRGG could not be recognized after SW installation

FlexiBTSProperti f_22#0.85 - - -
es.xml
FlexiBPF.mdb f_22#0.85 - - -

Change effects:
Effects on end-user
Effects on Operator
Other effects
New functionality
Customer Impact
Performance: calls might be dropped, when FRGG makes a reset. That causes also short
service break.
Pre-requirements:
-
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60202
Title:
FXDA: RF module led is red even no alarms are active

WN6.0 22.9-16

References:

Problem:
The LED display on the RF module was not inline with the antenna line status set by the
BTSOM. When the alarm was filtered by the BTSOM the status of the antenna line was not
set back to "normal"
Correction:
LED indication corrected to be in line with the module status.

61350ESPE04
FXDA: RFM led is red even no alarms are active in BTSSM

Multiradio_Agent f_mp2#2 - - -
_Pkg.sbs

Change effects:
Effects on end-user
Effects on Operator
Other effects
New functionality
Customer Impact
Operability:
Wrong LED status indication.
Pre-requirements:
-
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60203
Title:
HSPA setup success rate decreased

WN6.0 22.9-22

References:

Problem: RL setup and RL addition failures
Root cause: Unreleased E-RGCH signature sequence indexes and PhysShChReaconf

parameter check problem.
Correction:
- userEntryTable indexing corrected in MngrCtrl Check_eRgchEHichCodes()-
- Added old E-HICH signature sequence index releasing to non-serving to serving reconfig.

NA04785031
The Counter for P502_HSUPA increased after Loading of PP1.2 at the Flexi NodeBs
NA04790068
HSPA setup successful rate decreased much suddenly

BTS_SC_DSP.- r4796 - - -
Change effects:
Effects on end-user
Effects on Operator
Other effects

New functionality
Customer Impact
Pre-requirements:
-
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60204
Title:
Flexi Rel1 system module failed

WN6.0 22.9-22

References:
Problem:
FSN Sync Ind message was sent multiple times instead of once. It was leading to overload
in control plane signalling. Cumulative delay made receiving responses impossible which
lead to system failure.
Root cause:
Multiple message sending was not prevented.
Correction:
Safety check was added to ensure that only one message is sent.

67355ESPE04
Flexi rel1 system module failed
67647ESPE04
WN6.0 EP1 Rel1, ERR/TUP_Cm ResetIndication:

BTS_SC_TUP.- 2760 - - -
Change effects:
Effects on end-user

Effects on Operator
Other effects
New functionality
Customer Impact
Stability problem in the network.
Pre-requirements:
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60205
Title:
Recommissioning fails with application error

WN6.0 22.9-20

References:

Problem:
Recommissioning fails with application error.
Root cause:
Recommissioning fails with application error.
When user is doing reconfiguration, Site Manager failed.
Correction:
Make sure each NTP server count only once when validate
recommissioning/reconfiquration.

67844ESPE04
CAN NOT RECOMMISSION AFTER MP2 UPGRADE

-.- - - - -
Change effects:
Effects on end-user
Effects on Operator
Can not recommission.
When user doing reconfiguration, SEM crashed.
Other effects

New functionality
Customer Impact
Operation & Maintenance
Pre-requirements:
-
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60206
Title:
UltraSite doesn't work correctly with Site Manager version 6.2.51

WN6.0 22.9-18

References:

Problem:
Site Element Manager (SEM) for Ultrasite WCDMA BTS and UltraSite BTS SW
WN6.0/WN6.0MP (increment -19 releases) use different versions of supported library than
WN6.0 MP2 release and SEM for Flexi. However they should be merged as one product, so
that only one version of SEM is required.
Correction:
The class path for each product to point to a different version of jars is modified. Site EM
6.2.51 is compatible UltraSite and MetroSite as well.

21468ESPE07
UltraSite doesn't want to cooperate with SEM 6.2.51

btsmanager.jar WN6.0 - - -
Change effects:
Effects on end-user
NA
Effects on Operator
Operability & Maintenance: Only one version of Site Element Manager required for the SW
release.
Other effects

New functionality
Customer Impact
Operability problem
Pre-requirements:
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60207
Title:
Site in continuous reset loop after ALD additional parameter modification

WN6.0 22.9-22

References:

Problem:
Site falls into continuously resetting state, when the Antenna Line Device (ALD) additional
data is modified in commissioning or re-commissioning for a Flexi BTS running with the
WN6.0 MP2 as active software.
In the regular start up following the commissioning, handling of the modified additional
antenna data fails, which initiates another resetting when start up has been nearly
accomplished. Recovery requires starting the BTS without any site configuration data.
Deleting such from the affected site may require actions to be performed on-site.
Correction:
Handling procedures of ALD database modified

67949ESPE04
Site in Reset loop (kernel) after ALD additional parameter modification

-.- - - - -

Change effects:
Effects on end-user
Effects on Operator
Other effects
New functionality
Customer Impact
Operation & Maintenance: Recovery actions required, site visit needed.
Performance & capacity: Cell availability degraded.
Pre-requirements:
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60208
Title:
Limited HSUPA throughput on Flexi with FSMD + 2 FRGP

WN6.0 22.9-22

References:

Problem:
The average HSUPA throughput is limited to about 400 Kbps in site when equipped with 2
FRGPs and one FSMD modules.
Root cause for the problem:

Receiving of measurement messages was incorrectly configured on DSP.
Dependency on configuration:
HSUPA traffic carried by FRGP radio module.
Description of the correction:

Configuration of measurement message receiving corrected.

NA04777434
Limited HSUPA throughput on Flexi 1 FSMD + 2 FRGP

BBC_pkg.sbs f_mp2#0.5 - - -
WCDMA_DSP_P - - - -
R_CD_1041.-

Change effects:
Effects on end-user
Low trough put in HSUPA service
Effects on Operator
Performance and capacity: Low trough put for HSUPA in cell
Other effects
New functionality
Customer Impact
Performance: lower HSUPA throughput.
Pre-requirements:
Test execution:
-
Expected results:
-
Unexpected results:
-

WCDMA BTS
CN-id: WN60209
Title:
HSDPA remained down after HSDPA DSP failure

WN6.0 22.9-13

References:

Problem:
HSDPA remained down after HSDPA DSP failure.
Root cause:
Request for modification of HSDPA cell with PSCR (physical shared channel
reconfiguration) interrupts ongoing local recovery. One of subsystem (CCHH) got
modification and local delete request in the same time but in different TCOM instances.
Correction.
Local Resource Manager (LRM) informs first Global Resource Manager (GRM) about
recovery and after that CCHH. Modification can be done and mean while deletion request is
stored. CCHH's data aren't overwritten.

67316ESPE04
HSDPA remained down after HSDPA DSP failure

3G_ctrl_ctrl_interf 10764 - - -
ace.sun
3G_ctrl_rm_interf 10764 - - -
ace.sun
Controller3g.spr 10764 - - -
ctrl_union_filter.s 10764 - - -
pr
tcom_msg_inc.h 10764 - - -
h2sdl_newLRM.h 10764 - - -
sctenv.c 10764 - - -

LrmRecovMain.c 10785 - - -
pp
RecovMgmt.cpp 10785 - - -
SLrmReconfCell 10753 - - -
HspaReq.h
SLrmReconfCell 10753 - - -
HspaResp.h
MessageId_Tcom 10753 - - -
Tcom.sig
Timeouts.- 10753 - - -
grm3.spt 10756 - - -
3G_ctrl_grm_inte 10756 - - -
rface.sun
SDLSignals.xls 10768 - - -
Change effects:
Effects on end-user
Effects on Operator
Other effects
New functionality
Customer Impact
Possibly no HSDPA service
Pre-requirements:
-
Test execution:
-
Expected results:
-
Unexpected results:
-

WN6 0 PP2 03 SW CN Document

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

WN6 0 PP2 03 SW CN Document

Hochgeladen von

Copyright:

Verfügbare Formate

Change Note Forms

WN6.0 PP2.03 (WN6.0 22.9-23_D)

Version of the SW-build:

Valid for Product(s):

Reason for the Change Note:

The problem exists only with Flexi Rel2 RF modules.

Effects on end users

© Nokia Siemens Networks Company Confidential 2 (36)

NA04818225 FRGF coming faulty with 125 alarm

Component Version *Net element *SW-type *Unit

© Nokia Siemens Networks Company Confidential 3 (36)

Version of the SW-build:

Valid for Product(s):

Reason for the Change Note:

Effects on end users

Corrected Fault Reports:

NA04773876 Persistent failures of FRGF1 units

© Nokia Siemens Networks Company Confidential 4 (36)

Component Version *Net element *SW-type *Unit

WN6.0 PP2.02 (WN6.0 22.9-23_B) correction

Version of the SW-build:

Valid for Product(s):

Reason for the Change Note:

Corrected Fault Reports:

Component Version *Net element *SW-type *Unit

© Nokia Siemens Networks Company Confidential 5 (36)

Testing Instructions for the change

© Nokia Siemens Networks Company Confidential 6 (36)

Version of the SW-build:

Valid for Product(s):

Reason for the Change Note:

Corrected Fault Reports:

Component Version *Net element *SW-type *Unit

© Nokia Siemens Networks Company Confidential 7 (36)

Testing Instructions for the change

© Nokia Siemens Networks Company Confidential 8 (36)

Version of the SW-build:

Valid for Product(s):

Reason for the Change Note:

Root cause: SUM_ACTIVE_CPC_USERS (M5000C285) were incorrectly incremented.

Corrected Fault Reports:

Component Version *Net element *SW-type *Unit

© Nokia Siemens Networks Company Confidential 9 (36)

Testing Instructions for the change

© Nokia Siemens Networks Company Confidential 10 (36)

Version of the SW-build:

Valid for Product(s):

Reason for the Change Note:

Corrected Fault Reports:

Component Version *Net element *SW-type *Unit

© Nokia Siemens Networks Company Confidential 11 (36)

Testing Instructions for the change

© Nokia Siemens Networks Company Confidential 12 (36)

Version of the SW-build:

Valid for Product(s):

Reason for the Change Note:

Corrected Fault Reports:

Component Version *Net element *SW-type *Unit

© Nokia Siemens Networks Company Confidential 13 (36)

Testing Instructions for the change

© Nokia Siemens Networks Company Confidential 14 (36)

Version of the SW-build:

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit

Component Version Net element SW-type *Unit