lgf-2gbtsu-2009-22

7/29/2019 LGF-2GBTSu-2009-22

http://slidepdf.com/reader/full/lgf-2gbtsu-2009-22 1/46

List of Generic Faults

LGF-2GBTSu-2009-22

GSM/EDGE BTS

UltraSite EDGE BTS

© Nokia Siemens Networks Company Confidential 1 (46)

7/29/2019 LGF-2GBTSu-2009-22


Table of Contents

1. About this document .................................................................................................................. 5 1.1 Problem descr iption .............................................................................................................................. 5

2. Open problems ............................................................................................................................6 2.1 Open prob lems waiting for correction target ..................................................................................... 6 2.2 Open problems targeted for CX7 MP1.0.............................................................................................. 6

2.2.1 (NEW) TRX Test shows invalid behaviour when IDD is enabled on site........................................ 6 2.2.2 (NEW) Abis loop test fails on UltraSite ........................................................................................... 6 2.2.3 (NEW) Alarm not reported for EDGE TRX replaced with GSM TRX in EGPRS enabled

sector............................................................................................................................................... 7 2.2.4 (NEW) Repeated TAC in AHS calls when A-bis link is disturbed on GSM hardware..................... 7 2.2.5 (NEW) UltraSite BTS not passing transmission alarms.................................................................. 7 2.2.6 (NEW) BTS sends STATE CHANGE message for the faulty TRX................................................. 8 2.2.7 (UPDATED) Incorrect RX DIV cabling defined in the configuration wizard .................................... 8 2.2.8 GPRS signalling is decreasing CCCH signalling capacity during high traffic load ......................... 9 2.2.9 SDCCH Call Drop increased when SDCCH is configured to TS0 in TCH TRX ............................. 9

2.3 Open problems targeted for CX7 ......................................................................................................... 9 2.3.1 7607 VSWR monitoring alarm following AHOP activation............................................................ 10 2.3.2 Unable to perform Manual MMI Commissioning of Ultra BTS...................................................... 10 2.3.3 Average RACH busy count is low in CCCH Load Indicationl ....................................................... 11 2.3.4 Transmission unit alarms are not cleared at BSC and NetAct...................................................... 11 2.3.5

Unable to perform TRX test after BTS SW upgrade with STIRC feature enabled ....................... 11

3. Corrected problems ..................................................................................................................13

3.1 Problems corrected in CX6 CD2.0...................................................................................................... 13 3.1.1 BTS information is missing in NetAct Hardware Browser............................................................. 13 3.1.2 Mismatch between the Air interface and LMU TDMA Frame Number ......................................... 13 3.1.3 Alarm 7616 OSCILLATOR ADJUSTING TEMPORARILY INTERRUPTED during start-

up .................................................................................................................................................. 13 3.1.4 BCCH TRX stay in configuring state after reset from BTS Manager when NTIM expires............ 14 3.1.5 Audio break with AMR HR after handover with TRAU Bicasting feature......................................14 3.1.6 Truncated error message while opening CX6 CD1.0 ewb file with CX6 HWC............................. 15 3.1.7 No alarms for slip of internal frame clock following loss/restore of LMU sync.............................. 15

3.2 Problems corrected in CX6 CD1.0...................................................................................................... 16 3.2.1 (UPDATED) 7606 TRX FAULTY “FBUS HW Failure" with BB2A ................................................ 16 3.2.2 Alarm 7606 ‘No data is received from DIBA Asic traffic channels to CHDSP’.............................. 16 3.2.3 BER & FER degradation after EMR feature activation ................................................................. 17 3.2.4 UltraSite transmits in None Shutdown state after Abis break....................................................... 17 3.2.5 UltraSite comes up in wrong state after loss of LMU synchronization.......................................... 18 3.2.6 Non BCCH TRXs stuck after recovery from Shutdown state........................................................ 18

3.3 Problems corrected in CX5 CD4.0...................................................................................................... 19 3.3.1 High SDCCH rejection on BB-hop or Antenna-hop sites.............................................................. 19 3.3.2 Active alarms at PSM are not shown at BTS................................................................................ 19 3.3.3 Abis loop test fails with RTSL6 when EGPRS is enabled............................................................. 20 3.3.4 TCH TRX assignment failures in a combined AHOP and RF hop configuration.......................... 20 3.3.5 Alarm 8048 LOSS OF INCOMING SIGNAL is lost during a BCF reset........................................ 20


7/29/2019 LGF-2GBTSu-2009-22


3.3.6 Long delay in reconfiguration if RTC and DVxx units are configured in the same sector ............ 21 3.3.7 HW Configurator problem with WCxT........................................................................................... 21

3.4 Problems corrected in CX6................................................................................................................. 22 3.4.1 High SDCCH rejection on BB-hop or Antenna-hop sites.............................................................. 22 3.4.2 Alarm 8048 LOSS OF INCOMING SIGNAL is lost during a BCF reset........................................ 22

3.5 Problems corrected in CX5 CD3.0...................................................................................................... 23 3.5.1 Problem with unnecessary 7606 alarms....................................................................................... 23 3.5.2 Sleeping Cell problem with alarm 7738 and 7725 ........................................................................ 23 3.5.3 Triple Wide Band Combiner (WCxT) support is missing from UltraSite mini ODCM

cabinet HWC SW .......................................................................................................................... 23 3.5.4 Interference with HR TCH during high traffic ................................................................................24 3.5.5 MNTB cannot be added to UltraSite HW Configuration using HW Configurator 5 CD2.0............ 24 3.5.6 Mini UltraSite view changes to UltraSite view after Abis is disabled from BTS Manager............. 25 3.5.7 EAC generated MAINS alarm is not sent from master to slave cabinets ..................................... 25 3.5.8 Enabling/disabling STIRC for sector with non-EDGE capable preferred BCCH TRX.................. 25 3.5.9 OMU reset during intelligent shutdown......................................................................................... 26

3.6 Problems corrected in BTS SW CX5 CD2.0 ......................................................................................26 3.6.1 Locally blocked BTS can still handle traffic................................................................................... 26 3.6.2 Problem with WCxT TX cabling figure in HW Configurator .......................................................... 27 3.6.3 Calls are dropped in the 2nd sector when the 1st or 3rd sector is restarted or unblocked

locally in IDD/4UD configuration ................................................................................................... 27 3.6.4 Fault in a sector during RTC Configure with wrong frequencies after a sector block from

BTS Manager ................................................................................................................................ 28 3.6.5 BTS SW file corruption not detected............................................................................................. 28 3.6.6 Disabling STIRC from a non-EDGE sector where one TRX is set to preferred BCCH ................ 29 3.6.7 Cancellation of the 3rd sector alarm 7606 TRX FAULTY ‘Antenna Connection Faulty’

causes restart of other sectors in IDD configuration..................................................................... 29 3.6.8 BTS Manager displays an error message when RSSI comparison values are fetched ............... 29

3.7 Problems corrected in BTS SW CX5 CD1.1 ......................................................................................30 3.7.1 GSM TRX TSxA with BB2F does not carry traffic in BB-hopping................................................. 30 3.7.2 Alarm 7606 TRX FAULTY “FBUS HW Failure" with BB hopping ................................................. 30

3.8 Problems corrected in BTS SW CX5 CD1.0 ......................................................................................31 3.8.1 7606 TRX FAULTY ‘The RF Transmitter hopping frequency synthesizer 1 is not locked’

- alarms appear after SW activation.............................................................................................. 31 3.8.2 Unnecessary cooling fan alarms...................................................................................................32 3.8.3 Continuous OMU Restarts............................................................................................................ 32 3.8.4 BCF resets in IDD configuration if LAPD of BCCH TRX is blocked from the BSC....................... 32 3.8.5 RSSI measurement results are lost when the alarm is cancelled................................................. 33 3.8.6 User may change default cross connections with HW Configurator............................................. 33

3.9 Problems corrected in BTS SW CX5..................................................................................................34 3.9.1 Multiple resets of BTS after auxiliary TRX of another sector is removed ..................................... 34 3.9.2 Bad FER Call Time percentage for the AMR full rate is higher than for the EFR......................... 34 3.9.3 Faulty TRX in a BB Hopping sector can be blocked /unblocked or reset from BTS

Manager ........................................................................................................................................35 3.9.4 Invalid values reported on RSSI results........................................................................................ 35 3.9.5 EAC input settings do not update during commissioning ............................................................. 35 3.9.6 IDD BCF does not recover after BCCH TRX local Block/Unblock from BTS Manager ................ 36 3.9.7 BCCH keeps on transmitting in None shutdown mode................................................................. 36

3.10 Problems solved without changes in the BTS SW or problems not corrected............................. 37


7/29/2019 LGF-2GBTSu-2009-22


3.10.1 (UPDATED) Bad downlink Mean BEP reported with DL DTX applied ......................................... 37 3.10.2 7606 TRX FAULTY “FBUS HW Failure" with BB2F units............................................................. 37 3.10.3 Metro Hub SW Mismatch Alarm is not cancelled in BSC/NetAct.................................................. 38 3.10.4 Serial on USB port is not recognized by BTS Manager................................................................ 38 3.10.5 No local VSWR alarm in fault condition when OMU signaling is blocked..................................... 39 3.10.6 Problem with finding Timing Advance value in LBS equipment in compare with real

situation......................................................................................................................................... 39 3.10.7 Codec first and codec last values are wrongly reported in some scenarios with BB2A............... 40 3.10.8 TRX restart and alarm 7606 FBUS HW FAILURE during high call traffic after CX4.1

activation.......................................................................................................................................40 3.10.9 Alarm 7615 RTS IS IN TEST USE does not cancel after the completion of the TRX test ........... 41 3.10.10 Fans are running although their associated TSxx units are in intelligent shutdown mode........... 41 3.10.11 False Alarm 8150 on FXC board .................................................................................................. 41 3.10.12 Misleading TRX test failure reasons when high RF interference in the uplink frequency ............ 42 3.10.13 Alarm 7738 is not cancelled immediately...................................................................................... 43 3.10.14 Unexpected Abis loop test results in commissioning report when TCH timeslot allocation

at BTS Traffic Manager does not match that at BSC.................................................................... 43 3.10.15 The cabinet fan does not restart when the intelligent shutdown situation is cancelled ................ 43 3.10.16 UltraSite CAFA cabinet fan speed control curve in the BTS SW does not match the

actual fan rotation curve................................................................................................................44 3.10.17 OMU block in Abis sync mode causes chain reset when Site Sync Recovery

Improvement feature is used ........................................................................................................ 44 3.10.18 Synchronisation problems in Talk–Talk–UltraSite co-siting configuration after mains

shortage ........................................................................................................................................44 3.10.19 Roll back of BTS SW with IBHO active......................................................................................... 45

Contact:

Contact your local Nokia Siemens Networks support

Summary of changes:

<29-May-2009> 1.0 Approved version


7/29/2019 LGF-2GBTSu-2009-22


1. ABOUT THIS DOCUMENT

This document describes the current unsolved problems in Nokia UltraSite EDGE BaseStation Software, as well as the corrections made to the existing problems.

1.1 Problem description

In the problems below, the following information is displayed:

Heading rowThe name of the problem.

Note

A status flag may appear in front of the heading row:

(NEW): The problem report is new in this LGF version/update.

(UPDATED): Some of the problem information is updated, for example, thetarget has changed. The updated information is written in Italic text format.

Problem reportThe internal reference number of the problem. It is provided here to help identify anyparticular problem.

Exists inThe problem has been verified to exist with this SW. The problem may exist also withearlier SW releases but it has not been verified. The problem exists with all the releasesincluding this release until correction target release.

Correction targetThis is the latest estimation of the BTS SW release in which the problem will be corrected.

Note

The correction may be delivered or it might require a new Element Manager SWas well. Element Managers are delivered within the SiteWizard.

If the field is marked with ‘−‘, the problem has only minor effect on BTS operation and willnot be corrected.If the field is marked with ‘TBD’, the schedule for correcting the problem is still open.

Appl ies toThis field lists which frequency band or product type the problem applies to, in thefollowing manner:

• Problem applying only to GSM BTS is marked with ‘GSM’

• Problem applying only to EDGE BTS is marked with ‘EDGE’

• When the field is empty, the problem applies equally to GSM and EDGEbase stations

Note

The Appl ies to field is not used in new problem cases after August 2006. The

same information will be found in the Description field. The Appl ies to field willstay in old cases as long as the case is listed in the LGF.


7/29/2019 LGF-2GBTSu-2009-22


2. OPEN PROBLEMS

2.1 Open problems waiting for correction target

This section lists the major problems, which are currently being investigated as BTSproblems. However, as the root cause has not been found, no target has yet been set tothese problems.

-

2.2 Open problems targeted for CX7 MP1.0

This section lists all the existing problems, which have been targeted for correction in BTSSW CX7 MP1.0

2.2.1 (NEW) TRX Test shows invalid behaviour when IDD is enabled on site

Problem report: 10548ESPE07Exists in: CX5Correction Target: CX7 MP1.0

Description:During Commissioning of a BTS with IDD, the IDD information is declared in the startingpages of commissioning. When the “manual” button is selected in the commissioningwindow for running the TRX test it lists all the TRXs (main+auxillary). The radio button for selecting the Main /Auxiliary TRX is disabled. Although as per the required functionality,only the Main TRXs and the TRXs for which IDD is not defined should be shown in the

TRX list.

Solution / Workaround:Do not select Aux TRX as a target for TRX testing.

System Impact:During commissioning the TRX testing is enabled for Aux TRXs. The test will fail as itshould not be enabled for Aux TRXs.

2.2.2 (NEW) Abis loop test fails on UltraSite

Problem report: 10504ESPE06Exists in: CX5 CD4.0Correction Target: CX7 MP1.0

Description: Abis loop test script is continuously running on one (1900 Non EDGE GSM HW) sector with BB-hop enabled. Abis loop test fails occasionally with reason “Hardware Failure”.

Solution / Workaround:Retest the TRX to see if the failure was caused by this occasional BTS SW issue.

System Impact: Abis loop test may fail with reason “Hardware Failure”.


7/29/2019 LGF-2GBTSu-2009-22


2.2.3 (NEW) Alarm not reported for EDGE TRX replaced with GSM TRX in EGPRS enabledsector.

Problem report: 4396C02Exists in: CX5Correction Target: CX7 MP1.0

Description: An EDGE enabled sector with a faulty EDGE TRX is in the locked state at the BSC. TheTRX is also in the locked state. When the faulty TRX is replaced with a non-EDGE TRX,then alarm 7606 "TRX FAULTY: “There is disturbance in the serial DL bus or bus isbroken" is reported and then cancelled.

The TRX and sector are now unlocked at the BSC. Sector comes into WO state but theinserted GSM TRX is stuck in waiting for system info. No alarms are reported on BTS

Manager but on the BSC alarm 7730: “CONFIGURATION OF BCF FAILED” is reportedwith reason 14969d: “No Nack for CONF-DATA sent to BTS”.

The sector is again Lock/ Unlocked at the BSC. Alarm 7607 “TRX OPERATIONDEGRADED: TRX is unable to implement EDGE services." is reported on BTS Manager and BSC and then cancelled. The sector comes up and WO-state but no alarms arereported. Inserted GSM TRX doesn't come up and after 10 minute alarm 7606 "TRXFAULTY: TRX is stuck in waiting for system information state." is reported for this TRX.

Solution / Workaround:Do not replace EDGE TRX with non EDGE TRX when EGPRS is enabled in sector.

System Impact:

Misleading alarms are seen if EDGE TRX is replaced accidentally with Non EDGE TRX.

2.2.4 (NEW) Repeated TAC in AHS calls when A-bis link is disturbed on GSM hardware

Problem report: 3035C01Exists in: CX5Correction Target: CX7 MP1.0

Description:High number of Time Alignment Commands (15-20) are seen, when A-bis link isdiconnected for short duration (between 300-900ms). The issue is seen only with Non

EDGE TRX HW.

Solution / Workaround:-

System Impact:Short A-bis link disturbance causes degradation in Speech quality/UL MOS for AMR HRcalls.

2.2.5 (NEW) UltraSite BTS not passing transmission alarms

Problem report: NA04439425

Exists in: CX5Correction Target: CX7 MP1.0


7/29/2019 LGF-2GBTSu-2009-22


Description:Supervisory Substations (SSS) are used to collect external alarms from Radio Access

sites. Originally these were being supervised (ie BTS polling) by Talk family base stationsvia their Q1 connections. When one of these Talk sites was replaced by an UltraSite thealarms were no longer transfered to the BSC. A remote session confirmed that externalalarms were active at the SSS, but these could not be seen locally at the UltraSite usingBTS Manager, or at the BSC.

Solution / Workaround:Use BSC polling to supervise the SSS. BSC polling requires spare transmission capacityto carry the service channel from the BSC to the SSS.

System Impact:No external equipment alarms are visible to the BSC or locally at the BTS whenSupervisory Substation is polled by an UltraSite BTS via Q1.

2.2.6 (NEW) BTS sends STATE CHANGE message for the faulty TRX.

Problem report: 10470ESPE07Exists in: CX5Correction Target: CX7 MP1.0

Description: A BB-hopping 4TRX BTS is configured with mixed configuration (BB2F with 2 TSxB &BB2A with 2 TSxA) when ST-IRC is enabled. Alarm for the non-EDGE capable TRXs isactivated “Non EDGE TRX device type used accidentally in Edge Capable Mode”.BSC is sending new BTS configuration data where the faulty TRXs are removed from the

BB-hopping group. After reconfiguration the BTS is sending State Changed –message tothe BSC including also the faulty TRXs which are not in the actual hopping configurationanymore.

The STATE CHANGE message should not be sent for the faulty TRX for which an alarm isactive.


System Impact:Incorrect status of faulty TRXs in BSC. However the occurence is rare.

2.2.7 (UPDATED) Incorrect RX DIV cabling defined in the configuration wizard

Problem report: 5139C01Exists in: BTS Manager/HW Configurator CX5Correction Target: BTS Manager/HW Configurator CX7 MP1.0

Description:When a 6+6 (4:1) sector configuration is selected from the Configurator Wizard in the HWConfigurator application the RX Div cabling defined for both the sectors are from the sameantenna as Main RX path cabling. The RX path from second antenna is never used.

Solution / Workaround:The RX antenna settings need to be changed manually from HW Configurator.


7/29/2019 LGF-2GBTSu-2009-22


System Impact:When the RX cabling is incorrectly set the antenna monitoring with RSSI might not work

correctly.

2.2.8 GPRS signalling is decreasing CCCH signalling capacity during high traffic load

Problem report: NA04465908, 46205ESPE02Exists in: CX5Correction Target: CX7 MP1.0

Description:When GPRS is enabled the CCCH capasity to handle high mobile Paging Message loadappears to decrease according to BTS reported Paging Load and Delete Paging.

The problem is visible in CCCH Load Indication message sent by the BTS BCCH TRX tothe BSC. The CCCH Load Indication is showing wrong values for CS and PS Paging Load. Also the value in Delete Paging is not correct.The problem is seen when the hourly mobile Paging Message load is above 170 000 andGPRS is enabled.The values are used in KPIs to see Paging load situation in BCCH/sector level.

Solution / Workaround:Instead of using CCCH Load Indication Paging Load values please use counter values inBSC for CS and PS paging. For Delete Paging there is no workaround at the BSC side.

System Impact:Paging Load and Delete Paging values are not correct during high traffic/paging load when

GPRS is enabled.

2.2.9 SDCCH Call Drop increased when SDCCH is configured to TS0 in TCH TRX

Problem report: 6676D04Exists in: CX6Correction Target: CX7 MP1.0

Description:If a TCH TRX is configured with GP timeslots and SDCCH on TS0, during PS data transfer SDCCH activation may fail on Layer 2. This is because the BTS is not sending UA tomobile SABM message. This causes the T200 timer to expire and consequentially SDCCHsubslot activation failure resulting in the corresponding call to drop.

Solution / Workaround:Configure SDCCH to TS 1 or change GP timeslot configuration to non SDCCH TRX.

System Impact:Increase in SDCCH call drop KPI.

2.3 Open problems targeted for CX7

This section lists all the existing problems, which have been targeted for correction in BTS

SW CX7.


7/29/2019 LGF-2GBTSu-2009-22


2.3.1 7607 VSWR monitoring alarm following AHOP activation

Problem report: NA04445483Exists in: CX5.0Correction Target: CX7

Description:When the antenna hopping feature is activated to BTS sites and these sites also haveVSWR monitoring activated in the HW Configurator then there will be spurious 7607 “Faultin VSWR antenna monitoring” alarms generated.

For successful VSWR monitoring the BCCH has to be continuously transmitting into theentenna being monitored. In the case of AHOP then the BCCH is hopping and thereforethe monitoring is not possible. The two features are mutually incompatible.

From the release of CX7 the VSWR monitoring alarms are automatically ignored whenantenna hopping is enabled thus disabling monitoring from HW Configurator manually isnot needed.

Solution / Workaround:Disable VSWR monitoring on the AHOP sectors from HW Configurator.

System Impact:TRX will be blocked and service unavailable. In addition a sector reset will be caused asindividual manipulation of TRXs is not possible withing an Antenna Hopping sector.

2.3.2 Unable to perform Manual MMI Commissioning of Ultra BTS

Problem report: NA04447952Exists in: BTS Manager CX5Correction Target: BTS Manager CX7

Description:During BTS commissioning, with no Abis connection, the TRX tests are not runautomatically. There is a button to Manually run these tests. Although the Ultrasite is inConfiguring, or if sufficient time has elapsed, Supervisory state, pressing this button raisesa warning box “No TRX in Configuring or Supervisory state” and will not allow testexectution.

Allowing commissioning to finish allows the TRX test to be run successfully from the Testmenu, although the Ultrasite will normally appear to be in the same state as it was prior tocompletion of commissioning.

Solution / Workaround:Ignore manual test and finish commissioning. TRX test can then be run, but results will notbe in commissioning report.

System Impact:Commissioning report does not include TRX testing results and the testing has to bestarted manually from BTS Manager after commissioning.


7/29/2019 LGF-2GBTSu-2009-22


2.3.3 Average RACH busy count is low in CCCH Load Indicationl

Problem report: 4357C02Exists in: CX5Correction Target: CX7

Description:The Busy RACH counter in CCCH Load Indication message from BCCH TRX to the BSCdoes not show correct values, with the counter values being less than expected. Theproblem is observed when adding interference on UL direction for BCCH channel withCombined channel configuration.


System Impact:The reported Busy RACH counter value is less than the actual value.

2.3.4 Transmission unit alarms are not cleared at BSC and NetAct

Problem report: NA04177553, NA04178176Exists in: CX4.1Correction Target: CX7

Description:Several transmission alarms including 8059, 8060, 8066, 8064 are not cleared at NetAct or

BSC even the alarm is already cancelled at the equipment.This causes increased work and efforts in the maintenance of these ‘ghost’ alarms as theyhave to be removed manually from NetAct or BSC. The transmission unit has to bechecked remotely that there are no problems or alarms.Nokia Siemens Networks has identified one possible scenario which is leading to asituation where the alarm is not cancelled properly.There are several theoretical methods by which ‘ghost’ alarms may be generated and it isnot possible for this correction to resolve all of these. Therefore some alarms may still beseen in the network which should have been cancelled automatically.


System Impact: Alarms have to be cancelled manually after checking that transmission units are OK.

2.3.5 Unable to perform TRX test after BTS SW upgrade with STIRC feature enabled

Problem report: NA04202512Exists in: CX5.0Correction Target: CX7

Description: After the BTS SW is upgrade from CX4.1 CD4.0 to CX5 CD4.0, TRX test from BSC for

GMSK always fails if STIRC is enablled. The same TRX test works with CX4.1 CD4.0.

The TRX test functions correctly with CX5 CD4.0 if the STIRC feature is not used.


7/29/2019 LGF-2GBTSu-2009-22


The test functions correctly with CX4.1 CD4.0 both with and without the STIRC feature

active.

Solution / Workaround:If a TRX test is required and STIRC is active, disable STIRC and perform the test. STIRCmay be re-enabled after the TRX test has been performed.

System Impact: After BTS SW upgrade no TRX test is possible when the STIRC feature is active.


7/29/2019 LGF-2GBTSu-2009-22


3. CORRECTED PROBLEMS

3.1 Problems corrected in CX6 CD2.0

3.1.1 BTS information is missing in NetAct Hardware Browser

Problem report: 1-356828482Exists in: CX4.1Correction Target: CX6 CD2.0

Description:When BTS hardware information is fetched for NetAct Hardware Browser the object (for

example TSxx) BTS id is missing.


System Impact:No visibility of object BTS id.

3.1.2 Mismatch between the Air interface and LMU TDMA Frame Number

Problem report: 1-353257333Exists in: CX4.1

Correction Target: CX6 CD2.0

Description:When on start up BTSs syncronise to the LMU and the BTS frame number is set from theLMU, it is possible that the frame number may be syncronised to ±1 of the correct value.This may be seen on the Air interface using, for example, TEMS.

The problem causes the impacted cabinets to be out of BSS syncronisation. For DFCA theproper network synchronization is mandatory.

There is no alarms for this situation and it has been seen only by conducting drive tests.

Solution / Workaround:

-

System Impact:When problem is active it will cause network unsynchronization. When DFCA is active theproblem will increase call setup failures.

3.1.3 Alarm 7616 OSCILLATOR ADJUSTING TEMPORARILY INTERRUPTED during start-up

Problem report: 43295ESPE02Exists in: CX5 CD3.0Correction Target: CX6 CD2.0

Description:


7/29/2019 LGF-2GBTSu-2009-22


A chained Ultrasite configuration with LMU syncronisation and one or more slave cabinetsis configured LMU—Master—Slave. The fault has occurred whereby the master and slave

cabinets have become out of syncronisation. The recovery is done in the following order:1) LMU restart2) OMU in Master cabinet restart3) OMU in Slave cabinet restart

After steps 1,2,3 the sites come back into synchronization with LMU and network.However, randomly the alarm alarm “7616 OSCILLATOR ADJUSTING TEMPORARILYINTERRUPTED Oven oscillator adjustment function interrupted.” may be activated for bothmaster and slave cabinets. The fault clears after aproximatly 5 minutes.The site is not correctly synchronized until the BOIA 13MHz clock reference is within thecorrect network synchronization frequency.


-

System Impact:Handover and call drop KPI’s are affected until the site is fully recovered and the alarmshave cleared.

3.1.4 BCCH TRX stay in configuring state after reset from BTS Manager when NTIM expires

Problem report: 8803ESPE06Exists in: CX6Correction Target: CX6 CD2.0

Description: A site is configured with:-- Antenna Hopping enabled-- Intelligent Shutdown mode set to NONE.

A mains failure occurs and the alarm ‘7995:MAINS BREAKDOWN WITH BATTERYBACK-UP’ is activate. Following the expiry of NTIM the site starts the shutdown procedure.

If a BTS reset command is given from the BTS Manager then the BCCH should come tothe Supervisory state.

However the TRX stays in Configuring state until the expiry of BTIM. The BCCH TRX

should come to the supervisory state.

Solution / Workaround:The problem can happen only when Antenna Hopping is active. Instead of resetting BTSwith BTS Manager, use the sector Lock/Unlock, this will not cause BCCH TRX problems.

System Impact:The sector is out of service until Lock/Unlock is done from the BSC.

3.1.5 Audio break with AMR HR after handover with TRAU Bicasting feature

Problem report: 39524ESPE02 Exists in: CX6Correction Target: CX6 CD2.0


7/29/2019 LGF-2GBTSu-2009-22


Description:

There is a noticeable downlink audio break after handover when AMR HR codec is used intarget timeslot/cell. Comparison has been done to AMR FR codec and the audio break hasbeen noticed to be longer with AMR HR (~150ms). The problem is seen only when the‘TRAU Bicasting feature’ (BSS13) is used and there is a simultaneous audio in thedownlink direction. .


System Impact:The mobile user might hear an audio break in DL direction when the handover is done.

3.1.6 Truncated error message while opening CX6 CD1.0 ewb file with CX6 HWC.

Problem report: 8348ESPE06Exists in: SiteWizard 6 CD1.0 (BTS Hardware Configurator)Correction Target: CX6 CD2.0 BTS Hardware Configurator

Description:Hardware configuration file is created and saved in xml format using SiteWizard6 CD1.0BTS Hardware Configurator. SiteWizard 6 BTS Hardware Configurator is launched and thepreviously saved xml file is opened. Previously opened file is selected from HardwareConfigurator File menu."Fail to open the specified file" error message is displayed as it should. But the details for

the message is incomplete.

Solution / Workaround:Open the file with SiteWizard 6 CD1.0 BTS Hardware Configurator.

System Impact:BTS Hardware Configurator user will not see the reason for the error message when tryingto open new xml format HW Configurator file with older CX6 BTS HW Configurator.

3.1.7 No alarms for slip of internal frame clock following loss/restore of LMU sync

Problem report: 43345ESPE02, 21063ESPE05, 1-353257333

Exists in: CX5.0 CD3.0Correction Target: CX6.0 CD2.0

Description:LMU-Abis sync is in use for the purpose of maintaining BSS syncronisation when GPS islost for an extended time period.If the LMU loses the GPS signal and this is not restored before the LMU timeout period,then if LMU-Abis sync is used, the Master BTS clock source is changed to use theincoming PCM as a reference and passes the PCM derived synchronisation to its slaves.On restoration of the GPS signal the synchronisation is switched back to the LMU asreference.

If during the period when the synchronisation is from the PCM the PCM performance is notto the required specification and the FCLK clock slips more than 18μs then DFCAperformance will start to be compromised.


7/29/2019 LGF-2GBTSu-2009-22


Even after synchronisation to the LMU is restored this error will take time to be corrected.

In extreme cases it may not be possible to reliably correct this error without resetting thesite or the correction of this error will take a great length of time during which the networkperformance for the site and its neighbours will be degraded.

There are no alarms for these situations and these situations and they are only detectableeither from KPI data or from drive tests..


System Impact:KPI will be degraded by an increase in call drops, call setup and handover failures anddegraded call quality.


3.2.1 (UPDATED) 7606 TRX FAULTY “FBUS HW Failure" with BB2A

Problem report: 1-328295312, NA04464446 Exists in: CX5 CD1.0Correction Target: CX6 CD1.0

Description: After activation of BTS SW CX5 CD1.0, the alarm 7606 TRX Faulty “FBus HW Failure” is

seen in some TRX’s network wide. The problem does not clear even if the site isrecommissioned or the blocked unit is replaced with a new unit.

The original correction target was BTS SW CX6 CD1.0 and it was stated in a previous LGFversion that the correction target could not be met. Further investigations were done and acorrection for this issue was found for BB2A plug in units. Still further improvement needsto be done for BB2F (handled with another problem report).

Further investigations have proven that the BB2F problem was due to random HW failurein one BB2F unit. No further actions are planned for BTS SW side.

Solution / Workaround:Rollback to previous BTS SW is the only solution to get the TRX working again.

System Impact:TRX is out of service until BTS SW is rolled back to previous version. Do not send theBB2A unit to the HW Services until tested and failing also with the new BTS SW version.

3.2.2 Alarm 7606 ‘No data is received from DIBA Asic traffic channels to CHDSP’

Problem report: 1-304472751, 1-242632132Exists in: CX4.1 CD4.0Correction Target: CX6 CD1.0

Description:


7/29/2019 LGF-2GBTSu-2009-22


The alarm 7606 TRX Faulty ‘No data is received from DIBA Asic traffic channels toCHDSP’ is randomly seen in some customer networks. The alarm can activate in BB-

hopping configurations where BB2A or BB2A + BB2F baseband plugin units are in use.

Solution / Workaround:Restart the affected sector to get the faulty TRX in service again.

System Impact:Unnecessary alarm is activated which is blocking the TRX and causes a reconfiguration for BB-hopping sector. Do not send the unit to the HW Services until tested and failing alsowith the new BTS SW version where the correction is implemented.

3.2.3 BER & FER degradation after EMR feature activation

Problem report: 1-296629792 Exists in: CX4.1 CD2.0Correction Target: CX6 CD1.0

Description:When EMR feature is activated, an increase in FER and BER is observed in some sites.The FER and BER degradation affects to UL RX Quality measurements and reporting of quality bands 4-7 will increase.

Solution / Workaround:When such FER & BER degradation is noticed, disable EMR and restart the BTS with BTS

Lock/Unlock from BSC.

System Impact:The UL RX Quality bands 4-7 will show increase in KPI’s

3.2.4 UltraSite transmits in None Shutdown state after Abis break


Description:UltraSite BBU is set as NONE. Parameters NTIM=2 and BTIM=7 are set. Mainsbreakdown alarm is generated. Alarm 7995 is activated and reported to BTS Manager and BSC. Site enters into NoneShutdown state after expiry of timers. BCCH transmission is stopped. A short Abis break is generated. After the Abis break a BCCH transmission is accidentallystarted.The BCCH transmission is stopped after the time duration of NTIM + BTIM as BSC sends‘power supply off’ again for all TRXs.


System Impact:The BCCH is on air if there is an Abis break during mains breakdown in BBU configuration.Extra current is drawn from the battery backup.


7/29/2019 LGF-2GBTSu-2009-22


3.2.5 UltraSite comes up in wrong state after loss of LMU synchronization


Description:Clock Synchronization is defined as LMU at BSC (CS=LMU,SENA=T). ClockSynchronization at BTS Manager is showing "Clock Synchronization: Slave (Clock Master is LMU)"LMU power supply is switched off. Site is restarted due to loss of clock synchronizationsource. Site comes up in unsynchronized mode with "Clock Synchronization: Master".

It is expected to show “Independent” state instead of “Master”.When resetting BCF from BTS Manager. A message is displayed "BCF::Resetting thisBCF shall cause loss of service to all slaved BTS" where as there are no slaved BTS.


System Impact:The Synchronization state is wrong. Wrong message is displayed at BTS Manager whenthe BCF is restarted. However the site is able to carry traffic.

3.2.6 Non BCCH TRXs stuck after recovery from Shutdown state

Problem report: 7758ESPE07Exists in: CX5 CD4.0Correction Target: CX6 CD1.0

Description:6 Omni IDD RTC UltraSite is up and running without hopping. Parameters NTIM=2,BTIM=5 and BBU=NONE are set at BSC. Alarm 7995 is generated. Alarm is reported on both BTS Manager and BSC and site goes to BCCH shutdown state.BCCH TRX is blocked from BTS Manager. Alarm 7208 Local block is reported at BTSManager and BSC. After Unblocking the BCCH TRX the TRX comes into working state and alarm 7208 iscancelled. Site goes into NONE shutdown state after some time and the alarm 7995 iscancelled. After about 5-6 minutes the BCCH TRX comes up into working state and non BCCH TRXremain in configuring state at BTS Manager and BL-RSL state at BSC.

Solution / Workaround:Do not block BCCH TRX with BTS Manager when site is in Shutdown state.

System Impact:

Non BCCH TRX’s are not recovering from the Shutdown state after alarm 7995cancellation if BCCH TRX is blocked/unblocked during Shutdown.


7/29/2019 LGF-2GBTSu-2009-22



3.3.1 High SDCCH rejection on BB-hop or Antenna-hop sites

Problem report: 1-353848155, 1-358881121Exists in: CX5 CD2.0Correction Target: CX5 CD4.0 & CX6

Description: A sector is locked/unlocked from a BSC.Calls start dropping in other sector(s) but indication at the BSC is that this sector(s) has noblocking 76xx alarms and the BTS is in working state (WO). Alarms 7738 “BTS with no transactions” and 7745 “Channel failure rate above definedthreshold” are seen at the BSC for the sectors with dropped calls.

Calls can be initiated in the sector after sector restart (or BCF reset).

Problem can happen with a BCF site with more than one sector using BB-hopping or Antenna-hopping.

Solution / Workaround:Lock/unlock the BCF or locally restart the BTS.

System Impact: All calls are dropped until there is a sector restart and the BTS is back to working state(WO).

3.3.2 Active alarms at PSM are not shown at BTS


Description:When PSM4 alarm (warning) or Low Voltage alarm is active it duplicates a singular activePSM alarm. In the case of multiple active PSM alarms it will duplicate the alarm with thelowest severity at the BTS.When the PSM4 alarm (warning) or the low voltage alarm is cancelled it will cancel theseverity alarm it is duplicating.

PSM4 alarm can be generated by temperature, battery test event, door open or any alarmdesignated by the customer. The PSM4 is not used by the BTS so it can be inhibited.

The Low Voltage alarm cannot be inhibited as it is used to inform the network that thebattery voltage is low when mains supply failure as occurred. The Low Voltage alarm isalso used during the battery test procedure by changing the severity it will prevent thisalarm from interfering with other alarm.

Solution / Workaround:Inhibit PSM4 alarm

1. Right click on the alarm window and Choose properties from the drop down menu

2. Choose “0: CCUA/Q1IA/B/C” as the Functional entity (FE)

3. Right click on Warning Alarm [PSM4] choose Perm state – Inhibit from the pulldown menu.


7/29/2019 LGF-2GBTSu-2009-22


Change severity of Low Voltage alarm1. Right click on the alarm window and Choose properties from the drop down menu

2. Choose “2: Batteries” as the Functional entity (FE)

3. Right click on Low Voltage choose severity – Major.

System Impact:If severity alarms PSM1, 2 or 3 are active singularly or together at the BTS, the generationand cancellation of a PSM4 alarm will also cancel the active alarm with the lowest severity.

3.3.3 Abis loop test fails with RTSL6 when EGPRS is enabled

Problem report: 31487ES08P

Exists in: CX5Correction Target: CX5 CD4.0

Description: Abis loop test is always failing for radio timeslot 6 when EGPRS is enabled. The test resultin BSC is “Inconclusive: Hardware Failure”.

Solution / Workaround: -

System Impact: Abis loop test is not possible for RTSL 6 when EGPRS is enabled.

3.3.4 TCH TRX assignment failures in a combined AHOP and RF hop configuration

Problem report: 1-252259905Exists in: CX4.1 CD3.0Correction Target: CX5 CD4.0

Description: Antenna hopping was activated to RF hopping sectors under the same BCF. The samechannel number was used in both sectors MALs. Both sectors used different HSN. Onlyfew calls were successfully established on the second sector and number of assignmentfailures increased on TCH TRX.

Solution / Workaround:Remove or change overlapping frequency in MAL used in the other sector under the sameBCF.If the amount of frequencies is small, then the same MAL and HSN can be used for allsectors under the same BCF, however the MAIO needs to be unique for each sector.

System Impact:Problem causes a high number of TCH assignment failures on the TCH TRX.

3.3.5 Alarm 8048 LOSS OF INCOMING SIGNAL is lost during a BCF reset


Exists in: CX4.1 CD4.0Correction Target: CX5 CD4.0 & CX6


7/29/2019 LGF-2GBTSu-2009-22


Description:LMU is feeding clock signal to the BCF. The LMU is reset from LMU Manager or following

LMU SW activation. Alarm 8048 is raised.If the BSS11073 Recovery for BSS and Site Synchronisation feature is not in use, this willcause a BCF reset as well and during the BCF start-up alarm 8048 is not cancelled.The site will stay in UNSYNC mode and will never recover to LMU SYNC.

Solution / Workaround:Lock/unlock the BCF.

System Impact:No synchronisation to the BCF when alarm 8048 stays active.

3.3.6 Long delay in reconfiguration if RTC and DVxx units are configured in the same sector


Description: A BTS is configured to have an RTC unit and a DVxx unit in the same sector.When BCCH is active in a TRX connected to the RTC unit, a failure occurs in the RTC. Alarm 7606 TRX FAULTY is raised on each TRX connected to the RTC.The reconfiguration starts going through every TRX connected to the RTC, but it will takeapproximately 5-10 minutes per TRX. It may take up to one hour until the BCCH isreconfigured to a TRX connected to the DVxx unit.

Solution / Workaround:Lock/unlock the sector to speed up the reconfiguration.

System Impact:During the reconfiguration the sector is out of service.

3.3.7 HW Configurator problem with WCxT

Problem report: 1-294637987Exists in: SiteWizard 5 (HW Configurator 5)Correction Target: SiteWizard 5 CD4 (HW Configurator 5 CD4)

Description: A HW configuration file with WCxT and its cabling is created and saved on a hard disk asan HW configuration candidate. The file is opened in HW Configurator with “ConfigurationWizard” | “Search for Configuration Candidate”. After selecting the previously saved file allthe HW units and cabling show up correctly except WCxT and its cabling.

Solution / Workaround:Open the HW configuration file in HW Configurator. Manually add the missing units(WCxTs) and their cabling to the used HW configuration file before sending it to the BTS.

System Impact:

WCxT unit and cabling information is missing from HW configuration.


7/29/2019 LGF-2GBTSu-2009-22


3.4 Problems corrected in CX6

The BTS SW CX6 release schedule was before CX5 CD4.0, thus the correction content inCX6 does not include all new corrections which are included in CX5 CD4.0.

3.4.1 High SDCCH rejection on BB-hop or Antenna-hop sites

Problem report: 1-353848155, 1-358881121Exists in: CX5 CD2.0Correction Target: CX5 CD4.0 & CX6

Description: A sector is locked/unlocked from a BSC.

Calls start dropping in other sector(s) but indication at the BSC is that this sector(s) has noblocking 76xx alarms and the BTS is in working state (WO). Alarms 7738 “BTS with no transactions” and 7745 “Channel failure rate above definedthreshold” are seen at the BSC for the sectors with dropped calls.Calls can be initiated in the sector after sector restart (or BCF reset).

Problem can happen with a BCF site with more than one sector using BB-hopping or Antenna-hopping.

Solution / Workaround:Lock/unlock the BCF or locally restart the BTS.

System Impact:

All calls are dropped until there is a sector restart and the BTS is back to working state(WO).

3.4.2 Alarm 8048 LOSS OF INCOMING SIGNAL is lost during a BCF reset

Problem report: 33787ES08PExists in: CX4.1 CD4.0Correction Target: CX5 CD4.0 & CX6

Description:LMU is feeding clock signal to the BCF. The LMU is reset from LMU Manager or followingLMU SW activation. Alarm 8048 is raised.If the BSS11073 Recovery for BSS and Site Synchronisation feature is not in use, this willcause a BCF reset as well and during the BCF start-up alarm 8048 is not cancelled.The site will stay in UNSYNC mode and will never recover to LMU SYNC.

Solution / Workaround:Lock/unlock the BCF.

System Impact:

No synchronisation to the BCF when alarm 8048 stays active.


7/29/2019 LGF-2GBTSu-2009-22



3.5.1 Problem with unnecessary 7606 alarms

Problem report: 1-232152255, 1-207163193Exists in: CX4.1 CD2.0Correction Target: CX5 CD3.0

Description:Two unnecessary TRX Faulty 7606 alarms are seen randomly in UltraSite BTS sites whenusing BTS SW CX5 CD2.0. These alarm descriptions are:

• 7606 TRX Faulty “Interface problems between O&M and DSP SW”

• 7606 TRX Faulty “There is disturbance in the serial DL bus or bus is broken”

Solution / Workaround:The TRX needs to be restarted locally or remotely Lock/Unlock from the BSC.

System Impact:The TRX is out of service until restarted.

3.5.2 Sleeping Cell problem with alarm 7738 and 7725

Problem report: 1-215538071, 1-287924891, 1-307322301, 1-296528333, 1-276915962,1-312045192Exists in: CX4.1 CD3.0Correction Target: CX5 CD3.0

Description:Some UltraSite BTS’s were alarming 7738 ‘BTS WITH NO TRANSACTIONS’ and 7725‘TRAFFIC CHANNEL ACTIVATION FAILURE’. It was noticed that the BTS could nothandle any traffic. Only alarms 7738 and 7725 were active. In some cases only alarm 7738was active or alarm 7725. No calls were possible and the BTS needed to be restarted byLock/Unlock from BSC.The root cause has been identified as combined DSP and O&M SW problem. The primaryfailure is caused by an internal DSP SW malfunction. The secondary failure and cause of the 'sleeping cell' symptom is that the O&M software sometimes does not detect the DSPSW malfunction and initiate the required auto recovery procedure.The problem can happen only to BCCH TRX.

Solution / Workaround:Lock/Unlock the BTS with MML. A partial correction in BTS O&M SW is available in BTS SW CX4.1 CD4.2 released in 30

th

of January 2008. This CD can be used as a workaround until a final correction is available.

System Impact:The service is down until the BTS is restarted.

3.5.3 Triple Wide Band Combiner (WCxT) support is missing from UltraSite mini ODCMcabinet HWC SW

Problem report: 18133ES10PExists in: SiteWizard5 CD2 (HW Configurator5 CD2)Correction Target: SiteWizard5 CD3 (HW Configurator5 CD3)


7/29/2019 LGF-2GBTSu-2009-22


Description: As stated in UltraSite EDGE BTS HW Technical Note 105 the UltraSite mini cabinet is

supporting WCxT unit. The support is missing from SiteWizard5 CD2 HardwareConfigurator SW. With the current HW Configurator user can not select WCxT unit nor correctly set the TX cabling. The problem is only with mini cabinet (ODCM).


System Impact:The WCxT can not be configured to BTS Configuration file thus the MHA and RSSI alarmsmight not work properly if the TX cable definitions are missing.

3.5.4 Interference with HR TCH during high traffic

Problem report: 1-288444521Exists in: CX4.1 CD2.0Correction Target: CX5 CD3.0

Description:When a Half Rate TCH is activated by the BSC but a mobile is not yet reached thechannel, a RF Resource Indicator message is sent by the BTS for the TCH with a highILEV value. The ILEV value can be seen with MML (ZERO). In BTS the ILEV values arereported from idle TCH channels only.When the Alerting - Connect phase is reached, the RF Resource Indication message is notreported for the TCH anymore as mobile has reached the channel. The BSC is using thehigh ILEV value which is received earlier from RF resource Indicator message and showsthe value in ZERO command printout. This is normal operation for the BSC - the last value

reported is held by the BSC until the call is released.The problem happens also to the first idle channel measurement after the TCH has beendeactivated. The incorrect value is reported to the BSC by the first RF Resource Indicationmessage after the channel has been released.


System Impact:The ILEV value in ZERO printout shows high Interference Levels when there is no realInterference in the network. The problem does not affect to the normal operation of theBTS.

3.5.5 MNTB cannot be added to UltraSite HW Configuration using HW Configurator 5 CD2.0

Problem report: 5286C02Exists in: SiteWizard 5 CD2.0 (HW Configurator 5 CD2.0)Correction Target: SiteWizard 5 CD3.0 (HW Configurator 5 CD3.0)

Description:MNTB unit (800 band MHA co-sited with WCDMA) is being configured using HWConfigurator 5 CD2.0.When MNTB units are configured to the HWC file, it can be seen that the units arecorrectly shown in the Cabinet Units view.When the antenna settings are set in the Antenna Settings view, no MHA is seen in thewindows.The problem means that MNTB unit configurations cannot be set and sent to the BTSwhen configured with HW Configurator 5 CD2.0.The problem is specific to 800 band only.


7/29/2019 LGF-2GBTSu-2009-22



Use HW Configurator 5 CD1.0 to set up the MNTBs. Select high gain in the AntennaProperties dialog box.

System Impact:It is not possible to set up the MNTB unit to UltraSite configuration using HW Configurator 5 CD2.0.

3.5.6 Mini UltraSite view changes to UltraSite view after Abis is disabled from BTS Manager

Problem report: 5200C01 Reported in: CX5 CD1.0 Correction target: CX5 CD3.0

Description:UltraSite EDGE Mini Outdoor site is in the supervisory state and BTS Manager isconnected to the BTS. BTS Manager shows UltraSite Mini cabinet as expected.If the Abis is disabled from BTS Manager, the site resets and the BTS Manager view ischanged from Mini UltraSite to a standard UltraSite cabinet view.

Workaround:Enable the Abis with BTS Manager to get the view back to Mini UltraSite.

System impact:The fault has no effect on the operation of the BTS.

3.5.7 EAC generated MAINS alarm is not sent from master to slave cabinets

Problem report: 22280ES11PReported in: CX4.1 Correction target: CX5 CD3.0

Description:Site Support System (SSS) supplies power to UltraSite master and slave cabinets in achained configuration.The Mains Breakdown indication is sent to the UltraSite master cabinet from the SSSusing the External Input lines (EAC).The Mains Breakdown indication is not delivered to UltraSite slave cabinets.The behaviour is correct if Site Support alarms are delivered to UltraSite via Q1 instead of EAC.

Workaround: -

System impact:Intelligent shutdown does not work in the UltraSite Slave cabinets if EAC lines are used toget a Mains Breakdown indication to the UltraSite system.

3.5.8 Enabling/disabling STIRC for sector with non-EDGE capable preferred BCCH TRX

Problem report: 3182C02 Reported in: CX5

Correction target: CX5 CD3.0


7/29/2019 LGF-2GBTSu-2009-22


Description: A non-EDGE TRX with BB2A is the preferred BCCH TRX (PREF=P) and the Space-Time

Interference Rejection Combining (STIRC) feature is enabled for the sector. A TRX alarm7606 TRX FAULTY ‘Non EDGE TRX device type used accidentally in Edge CapableMode’ is raised, and the TRX state is disabled (BL-TRX). The BCCH is reconfigured to anEDGE TRX. This is expected behaviour as STIRC is not supporting non-EDGE TRx withBB2A.When STIRC is disabled, alarm 7606 is cancelled but the TRX stays in BL-RSL state withalarm 7705 LAPD FAILURE. When the TRX is reset, it will clear the alarm.When BCCH reconfiguration occurs for the preferred TRX, the EDGE TRXs in the sector may restart and stay in BL-SYS state with alarm ‘Failure in sending system info’. TheEDGE TRXs need to be restarted to clear the fault.

Workaround:Do not activate the STIRC feature in a sector with BB2A units. If STIRC needs to be

enabled, change the HW to EDGE capable units and restart the sector/TRX. If it isaccidentally enabled, disable STIRC and restart the TRXs or the sector.

System impact:Non-EDGE capable units are out of service until the STIRC feature is disabled and theunit/sector is restarted.

3.5.9 OMU reset during intelligent shutdown

Problem report: 3252C01 Reported in: CX5.0 Correction target: CX5 CD3.0

Description:In a multi-BCF configuration the master BCF OMU is reset during intelligent shutdown.This will cause differences in alarm and shutdown states between the master and slaveBCFs on both BTS and BSC level.This will lead to a situation where the intelligent shutdown does not work properly and thecapacity of Site Support System batteries is unnecessarily used. As there is no real need for OMU reset during intelligent shutdown and the problem ismore in system design, Nokia has decided not to support the OMU reset during intelligentshutdown.

Workaround:Use BCF lock/unlock or site restart instead of OMU reset during intelligent shutdown.

System impact: -

3.6 Problems corrected in BTS SW CX5 CD2.0

The corrections in BTS SW CX5 CD1.1 are merged in BTS SW CX5 CD2.0.

3.6.1 Locally blocked BTS can still handle traffic

Problem report: 1-262455362 Reported in: CX4.1 CD3.0 Correction target: CX5 CD2.0


7/29/2019 LGF-2GBTSu-2009-22


Description:

The problem occurs only when all TRXs under the BTS are first locally blocked and thenthe BTS is locally blocked. Finally all the TRXs are locally unblocked.The BTS starts to transmit and BTS Manager shows green light on BCCH TRX in theequipment view. ‘Telecom working’ is displayed at the bottom of the window. The sector isstill in a blocked state in BTS manager and in the BSC, but calls are possible.

Workaround:BCCH transmission is stopped correctly, when the BTS is locally blocked first, or BCCHTRX/BTS is locked from the BSC.

System impact:The BTS starts to transmit even when it is in a locally blocked state. Calls can be madewhen the BTS is in the BL-BTS state at the BSC.

3.6.2 Problem with WCxT TX cabling figure in HW Configurator

Problem report: 1-256542665 Reported in: Hardware Configurator 5Correction target: Hardware Configurator 5 CD2.0, SiteWizard 5 CD2.0

Description:When setting up TX cabling from TRXs to DVxx via the WCxT, a problem is seen in thefigure of Configuration Candidate in Hardware Configurator (HWC) when connecting upTRX4, TRX8, or TRX12. The HWC displays the TX cabling in an incorrect positionbetween WCxT and DVxx units. The problem is only in the figure and the correct cabling

path is listed in the TX cabling window. Thus the problem does not affect the performanceof the BTS.

Workaround: -

System impact:This problem does not affect the performance of the BTS.

3.6.3 Calls are dropped in the 2nd sector when the 1st or 3rd sector is restarted or unblockedlocally in IDD/4UD configuration

Problem report: 4026C02, 5126C01Reported in: CX4.1 CD3.0 Correction target: CX5 CD2.0

Description: A local BTS reset is done to the third sector in 2+2+2 IDD/4UD configuration. Thetransmission of the second sector stops for a moment and then comes back to normal.The problem is also observed when the local block/unblock command is given to the thirdsector from BTS Manager.When a local block/unblock is done in the first sector, all calls are dropped in the secondsector. When BB2F is used for Aux TRXs of the second sector, alarms 7607 TRXOPERATION DEGRADED: ‘FBUS HW failure’ and 7604 BTS OPERATION DEGRADED:‘FBUS HW failure’ are seen in the second sector.

Workaround:Use BTS lock/unlock from the BSC instead of a local restart in IDD configuration.


7/29/2019 LGF-2GBTSu-2009-22


System impact:Calls are dropped from the second sector when the first or third sector is locally unblocked

or restarted.

3.6.4 Fault in a sector during RTC Configure with wrong frequencies after a sector block fromBTS Manager

Problem report: 4636C01, 4953C01 Reported in: CX4.1 Correction target: CX5 CD2.0

Description: A sector with RTC is blocked locally with BTS Manager. The RTC Configure option isselected from BTS Manager with different frequencies than those given by the BSC for

each TRX. The sector is unblocked with BTS Manager.Two possible scenarios have been observed after the BTS unblock:The TRXs are tuned to the frequencies which were given manually. BCCH transmission isstarted with the wrong frequency and the sector is in the working state (WO) at the BSC,as well as at BTS Manager, with no alarms.The sector stays in the BL-RST state with all the TRXs in the configuring state.While testing the correction for this problem, a new issue was found:In two sector BB hopping configuration, the first sector is blocked with BTS Manager. TheRTC is configured using the RTC Configure command with BTS Manager. Immediatelyafter the RTC Configure command is sent to the RTC, the other sector goes down withalarm 7606 TRX FAULTY: ‘There is disturbance in the serial DL bus or bus is broken’ for all TRXs in the sector, which then correlates with alarm 7603 BTS FAULTY. TRXs in thefirst sector stay in the configuring state.

When the second sector is unblocked with BTS Manager, alarm 7208 LOCAL BLOCK iscancelled. Both sectors take multiple resets and the second sector stays in the BL-BTSstate at BSC even though alarm 7208 is cancelled.

Workaround:Do not unblock the sector with wrong RTC frequencies. BCF lock/unlock will clear thesituation.

System impact:Calls are not possible for the sector with wrong frequencies.

3.6.5 BTS SW file corruption not detected

Problem report: 31468ES08P Reported in: CX4.0 Correction target: CX5 CD2.0

Description:When new BTS software is downloaded to the base station, it might happen that the CRCchecking included in the application files does not detect corruption in the files. In this casethe SW activation may result in malfunction of the BTS.This is extremely rare (in fact seen on one occasion only).The CRC checking is further enhanced to include a more secure CRC calculation.

Workaround:

Run a binary comparison between the BTS SW files downloaded from NOLS and the filesstored on the BSC disk before downloading the BTS SW to the base stations.


7/29/2019 LGF-2GBTSu-2009-22


System impact:In extremely rare occasions, it may happen that corruption in the BTS SW is not detected,

resulting in malfunction of the base station.

3.6.6 Disabling STIRC from a non-EDGE sector where one TRX is set to preferred BCCH

Problem report: 3196C01 Reported in: CX5 Correction target: CX5 CD2.0

Description:The Space-Time Interference Rejection Combining (STIRC) feature is enabled for the non-EDGE sector where BB2A boards are used. Alarm 7606 TRX FAULTY ‘Non EDGE TRXdevice type used accidentally in Edge Capable Mode’ is reported for all TRXs, and alarm

7603 BTS FAULTY ‘Non EDGE TRX device type used accidentally in Edge CapableMode’ is reported. The STIRC feature is disabled. Alarm 7603 for BTS and alarm 7606 for non-BCCH TRXs are cancelled. Alarm 7606 for the preferred BCCH TRX is not cancelled from the BSC or BTS Manager.The sector moves into working state (WO) and calls are possible. The LED colour of BB2Afor BCCH TRX is red.

Workaround:Restart the sector.

System impact: Alarm 7606 TRX FAULTY ‘EDGE TRX device type used accidentally in Edge CapableMode’ is not cancelled correctly. BB2A LED is incorrectly red, which indicates a failure.

3.6.7 Cancellation of the 3rd sector alarm 7606 TRX FAULTY ‘Antenna Connection Faulty’causes restart of other sectors in IDD configuration

Problem report: 3820C01 Reported in: CX5Correction target: CX5 CD2.0

Description: A site is configured as 2+2+2 IDD. Sector 3 has an active TSxx unit alarm 7606 TRXFAULTY ‘Antenna Connection Faulty’ for the main TCH TRX.The alarm is cancelled by locking/unlocking the sector from the BSC. After the unlock,other sectors under the same BCF will restart and all calls are dropped. A similar problem occurs if RF hopping is applied to the third sector.This problem is seen only in the third sector and in an IDD configuration. The problemdoes not occur if the sector is restarted with BTS Manager.

Workaround: After a failed unit has been changed, restart the third sector with a local or remote BTSManager.

System impact: All calls are dropped when the alarm is cancelled.

3.6.8 BTS Manager displays an error message when RSSI comparison values are fetched

Problem report: 3943C01


7/29/2019 LGF-2GBTSu-2009-22


Reported in: CX5 and SiteWizard 5 (BTS Manager 5) Correction target: CX5 CD2.0 and SiteWizard 5 CD2.0 (BTS Manager 5 CD2.0)

Description:The RX Difference Limit (RXDL) parameter value is set to 64 at the BSC (64dB indicatesthat no RSSI measurement is done). The site is restarted. After the site is up and running,the RSSI comparison values are fetched using BTS Manager.BTS Manager prompts error message ‘Requesting RSSI comparison values failed. Cannotget response from BTS SW’ three times for the newest, reliable, and raw valuesrespectively. Thereafter, the RSSI window opens with message ‘Failed to get response’ inall three sub-windows.The correct message should be ‘Requesting RSSI comparison values failed. Feature is notactivated’ and it will be shown for the newest, reliable, and raw values. After selecting OKin each of the conditions stated above, the data comparison window will appear. RSSISections of each RSSI value will be opened with the message ‘Failed to get X RSSI

values’, where X = newest/reliable/raw.

Workaround:The RSSI value fetching is working correctly when the RXDL value is not 64.

System impact: A wrong error message is seen at BTS Manager.


This section includes the problem correction in customer specific CD CX5 CD1.1.

The BTS SW CX5 CD1.1 has to be requested separately from 2G BTS Technical Support.Note! Requires and order for CX5.The corrections in BTS SW CX5 CD1.1 are merged in BTS SW CX5 CD2.0.

3.7.1 GSM TRX TSxA with BB2F does not carry traffic in BB-hopping

Problem report: 1-264900231Exists in: CX4.1 CD2.0Correction target: CX5 CD1.1

Description:When Base band hopping is in use, the GSM TRX units connected to BB2F base band

units may not be able to carry any traffic.The problem results in dropped calls during the SDCCH call set up.

Workaround:If possible, switch of BB-hopping in the affected sectors.

System impact: A cell configured with GSM TRX units connected to EDGE capable base band units maybeunable to carry traffic in BB-hopping.

3.7.2 Alarm 7606 TRX FAULTY “FBUS HW Failure" with BB hopping

Problem report: 4307C02 Exists in: CX4.1 CD2.0Correction target: CX5 CD1.1


7/29/2019 LGF-2GBTSu-2009-22


Description:

7606 TRX FAULTY “FBUS HW Failure" alarms are still rarely reported even when usingthe correction delivered with CX4.1 CD2.0. The alarms are seen only with BB-hoppingconfigurations. Previously informed correction in CX4.1 CD2.0 did not correct these casesas further investigation has found another root cause which is caused by an unexplainedTRX restart in BB-hopping sector. The reset was caused by a problem in internal messagequeue which memory allocation was exceeding the TRX OS limits.

Workaround:BTS Lock/Unlock will clear the problem.

System impact:Unwanted TRX alarms are seen with BB-hopping sector. Calls are dropped when theproblem happens.


Note

BTS SW CX5 does not include all the problem corrections that were targeted inBTS SW CX4.1 CD4.0. Please see the chapter Problems corrected in BTS SWCX4.1 CD4.0 below for further information. If BTS SW CX5 is not defined in thecorrection target field, then the correction is automatically implemented in CX5CD1.0.

3.8.1 7606 TRX FAULTY ‘The RF Transmitter hopping frequency synthesizer 1 is not locked’- alarms appear after SW activation

Problem report: 1-279686587, 1-282786191Exists in: CX4.1 CD4.0Correction target: CX5 CD1.0

Description:Base Band hopping is in use.During the BTS W activation, unnecessary alarms 7606 TRX FAULTY ‘The RF transmitter hopping frequency synthesizer 1 is not locked’ may be seen on some TRX units.

The BTS or BCF resets will not recover the situation. The only way to recover the serviceis to pull the alarming units out of the cabinet and push them back in.

Note! The correction is linked to problem report 4918C01 also corrected in BTS SW CX5CD1.0.

Workaround:Pull the alarming TRX units out of the cabinet and push them back in.

System impact:Some TRX units are blocked after the SW activation when BB-hopping is in use. Site visitsare required to recover.


7/29/2019 LGF-2GBTSu-2009-22


3.8.2 Unnecessary cooling fan alarms

Problem report: 32891ES09PExists in: CX4.0Correction target: CX5 CD1.0

Description:When TSxB unit versions 4xx are used there is a possibility to see alarm 7602 BCFNOTIFICATION: Cooling fan speed has reduced from the set speed. The alarm is causedby the error in fan speed control where the set speed is just below the alarm thresholdlimits. Although this is seen only with UltraSite EDGE cabinet variant ODCM (Nokia UltraSiteEDGE BTS Mini Outdoor), it is potentially possible also for other cabinet variants.The alarm is intermittent depending on TRX operating temperature, which will changedepending on cabinet climate temperature and TRX loading. The alarm does not affect to

the performance of the TRXs.

Workaround:If the alarm is active with TRX temperature alarms: 7606 TRX Faulty “TSxx temperature isdangerously high”, consider the fan alarm as real and follow the normal troubleshootinginstructions.

System impact:Unnecessary fan alarms are seen. The problem does not affect to the service of the BTS.

3.8.3 Continuous OMU Restarts

Problem report: 30355ES08P Exists in: CX4.0 Correction target: CX5 CD1.0

Description:When DC power supply PWSB is used in configurations using MHA (mast head preamplifier) units, the UltraSite EDGE BTS might get into a continuous OMU restart loop. Alarms 7706 BTS O&M Link Failure and 7715 Continuous restarts of BCF/TRX are seen atBSC. A power off/power on of the PWSB units will recover the problem situation, but the problemmight come back after some time.

Workaround:

Power off/power on the power supplies at site.

System impact:Continuous OMU restarts prevent having a remote BTS Manager connection to the site.

3.8.4 BCF resets in IDD configuration if LAPD of BCCH TRX is blocked from the BSC

Problem report: 4918C01Exists in: CX5 Correction target: CX5 CD1.0

Description:

When the LAPD link of the BCCH TRX in an IDD configuration is either blocked at BSC or there are LAPD breaks due to transmission disturbances, the whole BCF resets.


7/29/2019 LGF-2GBTSu-2009-22


In some cases when BCCH reconfiguration is attempted, alarms 7606 TRX Faulty “F-BUSHW Failure” and “The RF Transmitter hopping frequency synthesizer 1 is not locked" are

seen in another sector under the same BCF.

Workaround: -

System impact:Unwanted BCF resets in IDD configurations after LAPD breaks. Calls are dropping inanother sector under the same BCF, if blocking alarms are activated unnecessarily.

3.8.5 RSSI measurement results are lost when the alarm is cancelled

Problem report: 19069ES11PExists in: CX4.0 and SiteWizard 4.0 (BTS Manager 4)

Correction target: CX5 CD1.0 and SiteWizard 5 CD1.0 (BTS Manager 5 CD1.0)

Description:The RSSI results can be seen in the BTS Manager RSSI Measurements and SiteInformation file. The new results are being updated to the report periodically once per hour (period count starts at OMU or site reset).When the alarm 7601 BCF OPERATION DEGRADED or 7604 BTS Operation Degradedwith a description 'RX levels differ too much between main and diversity antennas' isactive, the detailed cause for the alarm can be seen in these RSSI results at BTSManager. However, if the alarm condition and the alarm are cancelled, the alarm detailsare cleared from the RSSI results.The correction is to keep the history of the last alarm activations in the RSSI results.

Workaround:Check the RSSI results when the alarm 7601 BCF OPERATION DEGRADED or 7604BTS Operation Degraded with a description 'RX levels differ too much between main anddiversity antennas' is active and correct the problem on site.

System impact:It is difficult to find the reason for the RSSI alarm if the alarm is cancelled before the RSSIresults are read.

3.8.6 User may change default cross connections with HW Configurator

Problem report: 6530ES07P Exists in: HW Configurator CX4.0Correction target: HW Configurator with CX5 CD1.0

Description:It is possible to change the default Base Band - TRX unit cross connections with HWConfigurator, even if the functionality is not supported any more. UltraSite TN10 informsthat “The cross connection functionality will be permanently removed in the CX4.0 SWrelease”, but this change has not been implemented yet.

Workaround: -

System impact:Non-supported BB2-TRX cross connections can be made with HW Configurator.


7/29/2019 LGF-2GBTSu-2009-22


3.9 Problems corrected in BTS SW CX5

Note

BTS SW CX5 does not include all the problem corrections that were targeted inBTS SW CX4.1 CD4.0. Please see the chapter Problems corrected in BTS SWCX4.1 CD4.0 below for further information. If BTS SW CX5 is not defined in thecorrection target field, then the correction is automatically implemented in CX5CD1.0.

3.9.1 Multiple resets of BTS after auxiliary TRX of another sector is removed

Problem report: 4328C01

Exists in: CX4.1Correction target: CX5

Description: A second sector from 1+1 IDD (TSGB+BB2F) configuration is locked from the BSC. Theauxiliary TRX from the locked sector is removed and the sector is unlocked. The sector comes up and an alarm 7606 TRX FAULTY ‘There is disturbance in the serial DL bus or bus is broken’ for the auxiliary TRX appears after some time.The first sector takes multiple resets and the alarm states keep changing (both main andauxiliary TRXs). The LED in TRXs of the first sector changes to red after some time.This problem is seen only with BB2F and IDD.

Workaround:

Do not unlock the sector without an auxiliary TRX installed. Perform BTS Lock/Unlock for the first sector.

System impact:Calls are dropped from the first sector when the second sector is unlocked without anauxiliary TRX.

3.9.2 Bad FER Call Time percentage for the AMR full rate is higher than for the EFR

Problem reports: 1-62223179, 1-77993775 Exists in: CX4.0 Correction target: CX5 & CX4.1 CD4.0

Description:Three different problems were found:Some AMR mobiles cause the BTS to report 100% FER values during Alerting-ConnectPhase. Although there is no speech, the FER statistics are still counted.The first few measurement reports always show high FER values. This problem doesaffect both non-AMR and AMR speech codecs. The correction will improve the BAD FERKPI values with all speech codecs.The ‘first codec used’ information in the UL (sent every SACCH multi-frame) is sometimescorrupted and shows an incorrect first codec. This problem impacts the building of thecorrelation table that is used for updating the Estimated DL FER statistics. For thecorrelation table, the UL FER value is stored for all the codecs between the ‘first codecused’ and the ‘last codec used’. If the ‘first codec used’ is corrupted, it can cause too goodor too bad Estimated DL FER to all AMR speech codecs.

Workaround: -


7/29/2019 LGF-2GBTSu-2009-22


System impact:

The problems might cause the Link Adaptation to work inefficiently, that is, codecs beingchanged when not supposed to. The KPI for UL RX Quality share of levels 6 and 7 willshow slight increase in EDGE HW configurations with HR calls.The BAD FER KPI’s will show a minor improvement with all speech codecs. This is largelya statistical issue and thus has no impact on the end-user service.

3.9.3 Faulty TRX in a BB Hopping sector can be blocked /unblocked or reset from BTSManager

Problem report: 2701C02Exists in: CX4.1 CD1.0 Correction target: CX5

Description:When a TRX Faulty Alarm starts on a TRX which is a BB Hopping -enabled sector, it ispossible to perform a local Block/Unblock or Reset command via the BTS. If such anaction is carried out, the TRX alarm will cancel and the faulty TRX will be added to theHopping list after a sector reconfiguration. This behaviour is unexpected and againstspecification.

Workaround:Do not perform local Block/Unblock commands via BTS Manager in a BB Hopping sector.

System impact:During sector reconfiguration, all ongoing traffic is dropped.

3.9.4 Invalid values reported on RSSI results

Problem report: 6925ES05XExists in: CX4.1Correction target: CX5 Appl ies to: EDGE

Description: An IDD/4UD configuration is in use.When the TRX units are idle with no traffic, the RSSI report at the BTS Manager may showinvalid values in Frames and Time stamp fields.These values should be ‘n/a’.

Workaround: -

System impact:Invalid values may be seen in the RSSI report.

3.9.5 EAC input settings do not update during commissioning

Problem report: 20162ES08P Exists in: CX4.1 Correction target: CX5

Description: An UltraSite BTS is commissioned using BTS Manager 4.1.


7/29/2019 LGF-2GBTSu-2009-22


On the “EAC Input Settings” screen, the Open and Closed radio buttons are not updatedwhen the inputs are being tested.

Workaround:Update the radio buttons by using the Back and Next buttons.

System impact:No effect on end-user services.

3.9.6 IDD BCF does not recover after BCCH TRX local Block/Unblock from BTS Manager

Problem report: 14026ES11P Exists in: CX4.1Correction target: CX5

Appl ies to: EDGE

Description: An IDD configuration with two main-auxiliary TRX pairs is used.When a local Block is performed for the BCCH TRX using BTS Manager, the BCCHreconfiguration is started to the other TRX, but the BCF fails to recover.When an Unblock command is given, the BCF still does not recover. A new BCF restart isrequired.

Workaround:Lock/Unlock the BCF.

System impact:

An IDD configuration fails in a BCCH reconfiguration after a local BCCH TRX Block isgiven at BTS Manager.

3.9.7 BCCH keeps on transmitting in None shutdown mode

Problem report: 6572ES05X Exists in: CX4.0 Correction target: CX5

Description:The base station enters the None shutdown mode in Intelligent Shutdown.BCCH TRXs are still transmitting in the None shutdown mode.

Workaround: -

System impact:The BCCH transmission unnecessarily consumes the battery capacity.


7/29/2019 LGF-2GBTSu-2009-22


3.10 Problems solved without changes in the BTS SW or prob lems not corrected

3.10.1 (UPDATED) Bad downlink Mean BEP reported with DL DTX applied

Problem report: 8174ESPE06Exists in: CX4.1Correction Target: N/A

Description:During a speech call and silence period when DL DTX is applied the Mean BEP valuesdegrades in downlink measurement report. DL Rx Quality calculation is affected since BSCuses Mean BEP values to calculate DL quality in case DL DTX is applied.

This problem is possible with old mobile models only when EMR is active.

The problem solution has been delivered in Nokia mobile SWs which has already beendelivered during 2007. There is no such problem reported when using later Nokiahandsets.


System Impact:When DL DTX is active this problem may activate unnecessary handovers.

3.10.2 7606 TRX FAULTY “FBUS HW Failure" with BB2F units

Problem report: NA04204140Exists in: CX4.1 CD2.0Correction Target: N/A

Description:Following BTS SW CX4.1 CD2.0 activation the alarm 7606 TRX Faulty “FBus HW Failure”is seen in some BB2F units.This problem was observed during piloting of BTS SW CX6 CD1.0. The problem withBB2A units has been solved in BTS SW CX6 CD1.0 but investigation with BB2F wasinconclusive during the pilot.

Further investigation of problem BTS HW units in laboratory was clearly showing that theissue is with one faulty BB2F plug in unit. No further actions are planned for BTS SW side. As the failure is random and rare we recommend to send such BB2F unit to HWSaccording to normal repair process.

Solution / Workaround: A TRX/BTS restart might solve the problem for few hours but the alarm reoccurs. Rollbackto the previous BTS SW is the only solution to restore the TRX to a working state.

System Impact:The TRX is out of service until the BTS SW is rolled back to a previous version. Please donot send the unit to the HW Services until tested and failing with the previous BTS SW

version as well as with BTS SW CX6 CD1.0.


7/29/2019 LGF-2GBTSu-2009-22


3.10.3 Metro Hub SW Mismatch Alarm is not cancelled in BSC/NetAct

Problem report: 17305ESPE01Exists in: CX6Correction Target: N/A

Description:MetroHub Configuration is 1-Bridge, 2-STM and 3-RRI. Software Level is C3 CD1.

MetroHub is polled by an UltraSite BTS. The MetroHub is located between BSC andUltraSite.

ITN C3 CD2 Software is remotely downloaded to all nodes. Activation of the Software isstarted first on RRI and then STM and Bridge last. During this operation “VersionMismatch” (8221) alarm is raised on PDH part (Q1 4080) and SDH part (Q1 4086). Both

alarms are visible on the node, in BSC and Netact. After Bridge Software is updated, thealarms are cancelled in the node. The node is free of alarms, but the alarm for Q1 address4080 (PDH part) in BSC (and NetAct) is not cancelled.

Further investigation revealed that the problem can be avoided when ITN SW upgraded inthe correct sequence: starting with the node master unit (unit in slot 1). The upgradeprocess is documented in ITN SW installation documents. Further improvements are donefor the installation instructions document to avoid situations where the alarm cancellationneeds to be done manually. Thus this issue is not handled with BTS SW.

Solution / Workaround:If the alarm is not cancelled automatically after the successful SW upgrade please cancelthe alarm manually from BSC/NetAct.

System Impact: Alarm 8221 is not cancelled from BSC/NetAct even if the MetroHub SW levels arecorrectly updated.

3.10.4 Serial on USB port is not recognized by BTS Manager

Problem report: 16481ESPE01Exists in: BTS Manager 5Correction Target: N/A

Description:When using a serial on USB port the BTS Manager does not recognize the communicationport. This means the serial port is not visible/selectable in the BTS Manager options.Many laptop PCs do not have a serial communications port fitted as standard and the onlyoption is to use a USB to Serial adaptor. This problem has been seen using popular makesof USB to Serial adaptors:1) Targus model PA088E2) Belkin model F5U409

This fault needs more investigation in SiteWizard GCS side as it seems to be highlyrelated to USB adaptor drivers and windows environment.

Further investigations have revealed that the issue is with Windows operating system USB

adaptor drivers which could not be corrected by Nokia Siemens Networks. We recommend


7/29/2019 LGF-2GBTSu-2009-22


to try different adaptor if problem arise or contact adaptor manufacturer for a windowsdriver which could correct the situation.

Solution / Workaround:The problem is seen only with some adaptor models. It is recommended to try differentadaptor model if problem appears. Please remember to use the latest version of adaptor windows driver.

System Impact:Some USB to Serial port adaptors can not be used with BTS Manager.

3.10.5 No local VSWR alarm in fault condition when OMU signaling is blocked

Problem report: 7789ESPE07Exists in: CX5Correction Target: N/A

Description:One sector has Antenna Hopping and second sector has RF + Antenna Hopping. TheVSWR Monitoring is enabled on both antennas for the first sector. Power level for firstsector is set to max. OMU signaling is blocked from BSC using ZDTC command.The alarm cable is removed from Bias T. Calls are made to all TRXs.Even after 10-15 minutes no VSWR alarm is reported to BTS Manager. After OMU signaling is unblocked the BTS activates the alarms which are reported on BTSManager and BSC.

NOTE: During further investigation this fault was found to be working as specified. TheVSWR measurement is not done if the OMU signaling link is blocked.


System Impact:The alarm activation does not work locally when OMU signaling is blocked. When theOMU signaling is working again the alarm activation is working OK.

3.10.6 Problem with finding Timing Advance value in LBS equipment in compare with real

situation.Problem report: 1-268317602, 1-320693602Exists in: CX3.3-2Correction target: N/A

Description: UltraSite BTS is reporting higher TA value compared to actual distance of MS from BTS.Usually the reported TA value is higher by 1 to 3 steps.The problem does not affect to the normal operation of the BTS.New field tests and investigations have proven that the TA calculation is working asspecified. The purpose of TA is to ensure accurate reception of the transmitted burst andas such it is based on correcting the MS propagation delay calculated by the BTS.

Although this can be mapped approximately to a distance this is accurate only for propagation through free space.


7/29/2019 LGF-2GBTSu-2009-22


Workaround: -

System impact: Timing Advance KPI statistics are showing 1-3 steps higher than the actual MS-BTSdistance.

3.10.7 Codec first and codec last values are wrongly reported in some scenarios with BB2A

Problem report: 8704ES05XReported in: CX4.1Correction target: N/A

Description: GSM baseband unit BB2A is used.

During an AMR call setup or bad uplink RF interference conditions, AMR UL CODECFIRST and AMR UL CODEC LAST values always show ‘3’ instead of the codec used andirrespective of the number of codecs defined. AMR UL CODEC FIRST indicates the used codec of the first block in the multiframe. AMR UL CODEC LAST indicates the used codec of the last block in the multiframe. AMR UL CODEC FIRST is used in DL FER calculation (BSC DL FER estimationalgorithm). AMR UL CODEC LAST is used to map the uplink FER counts on BSC according to thecodec.Originally this problem has been made according to findings in EDGE HW side. Duringinvestigations it was noticed that this problem is not present with Non EDGE HW (BB2A)thus the case does not require correction in BTS SW.

Workaround: -

System impact: -

3.10.8 TRX restart and alarm 7606 FBUS HW FAILURE during high call traffic after CX4.1activation

Problem reports: 1-111349391, 1-109258175, 1-126315871,1-127937455, 1-199998801

Exists in: CX4.1Correction target: N/A

Description: After upgrading the BTS SW level to CX4.1, some TRXs in the BB-hopping sector restartunder high traffic. The alarm 7606 FBUS HW FAILURE is activated after the TRX restartbecause of BB-hopping.The problem happens rarely.The problem has not been reported against CX4.1 CD2.0 and Nokia has not been able toreproduce the problem with that BTS SW.Further R&D analysis has shown that the problem has been corrected in BTS SW CX4.1CD2.0 when correcting the problem report 1-11570932 Unnecessary alarms 1254'Unsolicited data link re-establishment’.

Workaround: Sector Lock/Unlock will clear the situation but the problem may reappear. If the problem

reappears turn off BB-hopping for the problem sectors.

System impact:


7/29/2019 LGF-2GBTSu-2009-22


Calls are dropped when the TRX is restarted. The BB-hopping sector is out of service untilthe BSC reconfigures the sector.

3.10.9 Alarm 7615 RTS IS IN TEST USE does not cancel after the completion of the TRXtest

Problem report: 7134ES05XExists in: CX4.1Correction target: N/A

Description: Sometimes, when a TRX test command is performed from the BTS Manager, alarm 7615RTS IS IN TEST USE does not cancel in the BTS Manager Alarms window after the test. Although the alarm stays active after the test, the timeslot is fully operational to take calls.

Problem could not be reproduced anymore in the BTS R&D, thus no correction can beplanned for the issue.

Workaround: -

System impact: An unwanted alarm may stay active in the BTS Manager.

3.10.10 Fans are running although their associated TSxx units are in intelligent shutdownmode


Exists in: CX4.0-4Correction target: N/A

Description: When Intelligent Shutdown is activated, alarm 7995 is reported at the BSC and the TRXsare shut down (BL-PWR).However, the fans associated with the shutdown TRXs continue running. This is not theexpected operation because the associated fans should shut down to save power.During the investigation of this problem it was noticed that the BTS is working as specified.When the ambient temperature is above 40 degrees Celsius the fans will rotate even if theTRXs are in intelligent shutdown mode. Thus no correction needed.

Workaround: -

System impact: No effect on end-user services.

3.10.11 False Alarm 8150 on FXC board

Problem report: 1-79773374, 1-89516742, 1-65991851, 1-69354588,1-75309061, 1-75557341, 1-88008859Exists in: ITN2.1Correction target: ITN C3.0 CD1.0

Description:


7/29/2019 LGF-2GBTSu-2009-22


Alarm 8150 FAULT IN UNIT is active for the transmission unit. The alarm cannot becleared by replacing the transmission unit. Despite the alarm, the BTS is operating

normally.The alarm is caused by a reference voltage outside its tolerance range. The referencevoltage is used for calibration of the internal oscillator of the FXC unit. If no valid externalsynchronisation source is available (for example during a transmission break), the internaloscillator may run outside the specified frequency of +- 50 ppm for E1 or 32 ppm for T1.No correction is needed for the BTS SW. The correction is done to the ITN SW.

Workaround: 1) The ITN SW on the FXC unit should be upgraded. The latest ITN SW C3

CD1 can operate in a wider range of reference voltages. In some cases thealarm may still be active after the SW upgrade if the reference voltage isoutside the new supported range.

2) Recalibrate the internal oscillator in the transmission card and inhibit thealarm in the unit alarm properties window of the element manager.

3) If there is third party transmission equipment synchronized to the FXC unitand the behavior of the equipment when receiving a degraded referenceclock signal is uncertain or critical, then the faulty transmission backplane of the BTS should be replaced.

System impact: When no valid sync source (external reference, for example, LMU or Abis) is available, thiscould cause, in rare circumstances, the internal oscillator to run outside the specifiedfrequency of +- 50ppm for E1 or 32ppm for T1. Although still unlikely, a network containingthird party transmission equipment may be affected by the degraded reference clock.The fault does not have any impact on the operation of the BTS or transmission if:

there are no other transmission alarms active andthere is no service degradation at the BTS andthere is no third party transmission equipment synchronized to the FXC unit.

3.10.12 Misleading TRX test failure reasons when high RF interference in the uplinkfrequency

Problem report: 3443ES07PExists in: CX4.0-5Correction target: UltraSite Product Documentation Release CX4.1 CD2.0

Description: TRX tests were run while injecting external interference into the RX DIV antenna line.When the interference level was increased, the reported ’Diversity Sensitivity’ resultsdeteriorated as expected.When the interference level was increased up to -85 dBm, the TRX test started failing. Thereported failure reasons were: ’Failed High Bit Error in RF Loop detected’ or ‘Unable tomeasure TX Power Level’.Both failure reasons suggest a clear TSxx (HW) unit failure although the HW is workingcorrectly. In a live network it is quite possible (depending on the frequency planning) tohave interference on the UL frequency when a TRX test is run. This may causeunnecessary TSxx unit returns to Repair Centres where no faults can be found.

Workaround: Check from the KPIs if the TRX service is at normal level. If not, swap the TSxx with some

other TSxx unit in the same sector/cabinet to see if the problem follows the TSxx unit. If the same unit still fails in the TRX test, it is most likely a HW failure. If the original


7/29/2019 LGF-2GBTSu-2009-22


position/frequency still fails in the TRX test with the same reason, measure the possibleinterference and correct the situation.

System impact: A TSxx might be returned to HW service without any HW fault.

3.10.13 Alarm 7738 is not cancelled immediately

Problem report: 1-49110163Exists in: N/ACorrection target: BSC SW S11.5 CD 4.0, S11 CD9.0 (see the BSC SW LGF for updates)

Description:

Alarm 7738 ‘BTS with no transactions’ for GP timeslots is cancelled several hours after thefirst successful GPRS transaction.The problem may happen when using mixed EDGE and GSM HW and the GP timeslotsare configured in an EDGE TRX.

Workaround: -


3.10.14 Unexpected Abis loop test results in commissioning report when TCH timeslotallocation at BTS Traffic Manager does not match that at BSC

Problem report: 1-20644204, 3-2742416, 1-19996945Exists in: CX3.3Correction target: N/A

Description: Commissioning is performed on the BTS, where the TCH timeslot allocation at the BSCdoes not match the TCH timeslot allocation at the BTS Traffic Manager. However, thecommissioning report shows that some timeslots have passed the TRX Abis loop test.No correction is required for these problem reports. Some sub-timeslots in the TRX alwaysfail the test indicating that a mismatch might exist.

Workaround: -


3.10.15 The cabinet fan does not restart when the intelligent shutdown situation is cancelled

Problem report: 19080ES09PExists in: CX4.1Correction target: N/A

Description: The UltraSite Outdoor cabinet door fan will stop when any of the TRXs is detected as a

shutdown TRX. However, the cabinet fan restart will take time once the intelligentshutdown situation is cancelled. It is observed that after the cancellation of the 'Mains


7/29/2019 LGF-2GBTSu-2009-22


breakdown' alarm, although all the TRXs come back to working state, the cabinet door fanis not immediately restarted. It will take a while until the TRXs are up and running and

report the temperature information to the BOIA. The cabinet fan is restarted according tothe new temperature information.In Technical Note No. 60, Nokia informed about the existence of this problem with acorrection target CX4.1 CD1.0. However, a further investigation has proved that this faultdoes not exist in the BTS SW, thus no correction for this problem is required.

Workaround: -

System impact: -

3.10.16 UltraSite CAFA cabinet fan speed control curve in the BTS SW does not match theactual fan rotation curve

Problem report: 3993ES03Exists in: CX3.3-1Correction target: N/A

Description: The UltraSite CAFA cabinet fan speed control curve in the BTS SW does not match theactual fan rotation curve. This may result in unnecessary 7602 BCF NOTIFICATION‘Cabinet fan speed has reduced from the set speed' alarms.

Workaround: -

System impact:

No effect on end-user services.

3.10.17 OMU block in Abis sync mode causes chain reset when Site Sync RecoveryImprovement feature is used

Problem report: 4596ES01Exists in: CX4.1Correction target: N/A

Description: An OMU block is incompatible with the Site Sync Recovery Improvement feature becauseit prevents the raising of alarms essential for correct feature operation.

Do not use the OMU link Block (BL)/Working (WO) commands (MML: ZDTC) with the SiteSync Recovery Improvement feature.

Workaround: -

System impact: The whole chain is reset instead of an OMU reset on one BCF.

3.10.18 Synchronisation problems in Talk–Talk–UltraSite co-siting configuration after mainsshortage

Problem report: 1-12359708Exists in: N/ACorrection target: N/A


7/29/2019 LGF-2GBTSu-2009-22


Description: In the Talk-Family–Talk-Family–UltraSite co-siting configuration, the Slave UltraSite

cabinet is without a battery backup. A mains power breakdown causes a situation where the synchronisation signal betweenthe Master clock source/BTS and the Slave UltraSite BTS is lost. After the mains power isrecovered, the Talk-Family Slave BTS might not recover the synchronisation from theMaster clock source/BTS.This problem will not be corrected in the BTS SW. The recommendation is to use theworkaround.

Workaround: To avoid unwanted power breaks, it is recommended to use a battery backup for theUltraSite Slave cabinet.Reset the Slave BCFs/BTSs from the BSC. If the problem remains, change thesynchronisation cable to the UltraSite Slave cabinet to a minimum length of 10 meters.

System impact: Dropped calls in the Talk-Family Slave cabinet.

3.10.19 Roll back of BTS SW with IBHO active

Problem report: 17438ES09PExists in: CX4.1Correction target: N/A

Description: IMSI based handover (IBHO) is supported in BTS SW CX4.1 or later SW releases. If the

IBHO is activated with CX4.1 and the BTS SW is rolled back to an earlier SW version thatdoes not support the IBHO, there will be a compatibility problem in the system.

Workaround: When rolling back to an older SW version than CX4.1, new features that are not supportedby the older SW have to be deactivated first.

System impact: -


7/29/2019 LGF-2GBTSu-2009-22


Disclaimer

The information in this document is subject to change without notice and describes only the productdefined in the introduction of this documentation. This documentation is intended for the use of NokiaSiemens Networks customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be used, reproduced, modified or transmitted in any form or meanswithout the prior written permission of Nokia Siemens Networks. The documentation has beenprepared to be used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia Siemens Networks welcomes customer comments as part of theprocess of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given “as is” and all liability arisingin connection with such hardware or software products shall be defined conclusively and finally in aseparate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens

Networks has made all reasonable efforts to ensure that the instructions contained in the documentare adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemednecessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENTWILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION ORFOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT,INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OFPROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THATMAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, andthey are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2009. All rights reserved.

lgf-2gbtsu-2009-22

Documents