Sie sind auf Seite 1von 46

List of Generic Faults

LGF-2GBTSu-2009-22 GSM/EDGE BTS UltraSite EDGE BTS

Nokia Siemens Networks

Company Confidential

1 (46)

Table of Contents

1.
1.1

About this document ..................................................................................................................5


Problem description .............................................................................................................................. 5

2.
2.1

Open problems............................................................................................................................6
Open problems 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 startup .................................................................................................................................................. 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

Nokia Siemens Networks

Company Confidential

2 (46)

3.3.6 3.3.7

Long delay in reconfiguration if RTC and DVxx units are configured in the same sector ............ 21 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

Nokia Siemens Networks

Company Confidential

3 (46)

3.10.1 3.10.2 3.10.3 3.10.4 3.10.5 3.10.6 3.10.7 3.10.8 3.10.9 3.10.10 3.10.11 3.10.12 3.10.13 3.10.14 3.10.15 3.10.16 3.10.17 3.10.18 3.10.19

(UPDATED) Bad downlink Mean BEP reported with DL DTX applied ......................................... 37 7606 TRX FAULTY FBUS HW Failure" with BB2F units............................................................. 37 Metro Hub SW Mismatch Alarm is not cancelled in BSC/NetAct.................................................. 38 Serial on USB port is not recognized by BTS Manager................................................................ 38 No local VSWR alarm in fault condition when OMU signaling is blocked..................................... 39 Problem with finding Timing Advance value in LBS equipment in compare with real situation......................................................................................................................................... 39 Codec first and codec last values are wrongly reported in some scenarios with BB2A ............... 40 TRX restart and alarm 7606 FBUS HW FAILURE during high call traffic after CX4.1 activation ....................................................................................................................................... 40 Alarm 7615 RTS IS IN TEST USE does not cancel after the completion of the TRX test ........... 41 Fans are running although their associated TSxx units are in intelligent shutdown mode........... 41 False Alarm 8150 on FXC board .................................................................................................. 41 Misleading TRX test failure reasons when high RF interference in the uplink frequency ............ 42 Alarm 7738 is not cancelled immediately...................................................................................... 43 Unexpected Abis loop test results in commissioning report when TCH timeslot allocation at BTS Traffic Manager does not match that at BSC.................................................................... 43 The cabinet fan does not restart when the intelligent shutdown situation is cancelled ................ 43 UltraSite CAFA cabinet fan speed control curve in the BTS SW does not match the actual fan rotation curve................................................................................................................ 44 OMU block in Abis sync mode causes chain reset when Site Sync Recovery Improvement feature is used ........................................................................................................ 44 Synchronisation problems in TalkTalkUltraSite co-siting configuration after mains shortage ........................................................................................................................................ 44 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

Nokia Siemens Networks

Company Confidential

4 (46)

1. ABOUT THIS DOCUMENT


This document describes the current unsolved problems in Nokia UltraSite EDGE Base Station 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 row The 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, the target has changed. The updated information is written in Italic text format. Problem report The internal reference number of the problem. It is provided here to help identify any particular problem. Exists in The problem has been verified to exist with this SW. The problem may exist also with earlier SW releases but it has not been verified. The problem exists with all the releases including this release until correction target release. Correction target This 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 SW as well. Element Managers are delivered within the SiteWizard. If the field is marked with , the problem has only minor effect on BTS operation and will not be corrected. If the field is marked with TBD, the schedule for correcting the problem is still open. Applies to This field lists which frequency band or product type the problem applies to, in the following 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 EDGE base stations

Note The Applies to field is not used in new problem cases after August 2006. The same information will be found in the Description field. The Applies to field will stay in old cases as long as the case is listed in the LGF.

Nokia Siemens Networks

Company Confidential

5 (46)

2. OPEN PROBLEMS 2.1 Open problems waiting for correction target


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

2.2 Open problems targeted for CX7 MP1.0


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

2.2.1 (NEW) TRX Test shows invalid behaviour when IDD is enabled on site
Problem report: 10548ESPE07 Exists in: CX5 Correction Target: CX7 MP1.0 Description: During Commissioning of a BTS with IDD, the IDD information is declared in the starting pages of commissioning. When the manual button is selected in the commissioning window 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 it should not be enabled for Aux TRXs.

2.2.2 (NEW) Abis loop test fails on UltraSite


Problem report: 10504ESPE06 Exists in: CX5 CD4.0 Correction 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.

Nokia Siemens Networks

Company Confidential

6 (46)

2.2.3 (NEW) Alarm not reported for EDGE TRX replaced with GSM TRX in EGPRS enabled sector.
Problem report: 4396C02 Exists in: CX5 Correction Target: CX7 MP1.0 Description: An EDGE enabled sector with a faulty EDGE TRX is in the locked state at the BSC. The TRX 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 is broken" is reported and then cancelled. The TRX and sector are now unlocked at the BSC. Sector comes into WO state but the inserted 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 reported with reason 14969d: No Nack for CONF-DATA sent to BTS. The sector is again Lock/ Unlocked at the BSC. Alarm 7607 TRX OPERATION DEGRADED: 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 are reported. Inserted GSM TRX doesn't come up and after 10 minute alarm 7606 "TRX FAULTY: 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: 3035C01 Exists in: CX5 Correction Target: CX7 MP1.0 Description: High number of Time Alignment Commands (15-20) are seen, when A-bis link is diconnected 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 HR calls.

2.2.5 (NEW) UltraSite BTS not passing transmission alarms


Problem report: NA04439425 Exists in: CX5 Correction Target: CX7 MP1.0

Nokia Siemens Networks

Company Confidential

7 (46)

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 stations via their Q1 connections. When one of these Talk sites was replaced by an UltraSite the alarms were no longer transfered to the BSC. A remote session confirmed that external alarms were active at the SSS, but these could not be seen locally at the UltraSite using BTS Manager, or at the BSC. Solution / Workaround: Use BSC polling to supervise the SSS. BSC polling requires spare transmission capacity to 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 when Supervisory Substation is polled by an UltraSite BTS via Q1.

2.2.6 (NEW) BTS sends STATE CHANGE message for the faulty TRX.
Problem report: 10470ESPE07 Exists in: CX5 Correction 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 is activated 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 to the BSC including also the faulty TRXs which are not in the actual hopping configuration anymore. The STATE CHANGE message should not be sent for the faulty TRX for which an alarm is active. Solution / Workaround: 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: 5139C01 Exists in: BTS Manager/HW Configurator CX5 Correction 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 HW Configurator application the RX Div cabling defined for both the sectors are from the same antenna 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.

Nokia Siemens Networks

Company Confidential

8 (46)

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, 46205ESPE02 Exists in: CX5 Correction Target: CX7 MP1.0 Description: When GPRS is enabled the CCCH capasity to handle high mobile Paging Message load appears 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 to the 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 and GPRS 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 in BSC 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: 6676D04 Exists in: CX6 Correction 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 to mobile SABM message. This causes the T200 timer to expire and consequentially SDCCH subslot 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.

Nokia Siemens Networks

Company Confidential

9 (46)

2.3.1 7607 VSWR monitoring alarm following AHOP activation


Problem report: NA04445483 Exists in: CX5.0 Correction Target: CX7 Description: When the antenna hopping feature is activated to BTS sites and these sites also have VSWR monitoring activated in the HW Configurator then there will be spurious 7607 Fault in VSWR antenna monitoring alarms generated. For successful VSWR monitoring the BCCH has to be continuously transmitting into the entenna being monitored. In the case of AHOP then the BCCH is hopping and therefore the monitoring is not possible. The two features are mutually incompatible. From the release of CX7 the VSWR monitoring alarms are automatically ignored when antenna hopping is enabled thus disabling monitoring from HW Configurator manually is not 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 as individual 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: NA04447952 Exists in: BTS Manager CX5 Correction Target: BTS Manager CX7 Description: During BTS commissioning, with no Abis connection, the TRX tests are not run automatically. There is a button to Manually run these tests. Although the Ultrasite is in Configuring, or if sufficient time has elapsed, Supervisory state, pressing this button raises a warning box No TRX in Configuring or Supervisory state and will not allow test exectution. Allowing commissioning to finish allows the TRX test to be run successfully from the Test menu, although the Ultrasite will normally appear to be in the same state as it was prior to completion of commissioning. Solution / Workaround: Ignore manual test and finish commissioning. TRX test can then be run, but results will not be in commissioning report. System Impact: Commissioning report does not include TRX testing results and the testing has to be started manually from BTS Manager after commissioning.

Nokia Siemens Networks

Company Confidential

10 (46)

2.3.3 Average RACH busy count is low in CCCH Load Indicationl


Problem report: 4357C02 Exists in: CX5 Correction Target: CX7 Description: The Busy RACH counter in CCCH Load Indication message from BCCH TRX to the BSC does not show correct values, with the counter values being less than expected. The problem is observed when adding interference on UL direction for BCCH channel with Combined channel configuration. Solution / Workaround: 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, NA04178176 Exists in: CX4.1 Correction 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 they have to be removed manually from NetAct or BSC. The transmission unit has to be checked remotely that there are no problems or alarms. Nokia Siemens Networks has identified one possible scenario which is leading to a situation where the alarm is not cancelled properly. There are several theoretical methods by which ghost alarms may be generated and it is not possible for this correction to resolve all of these. Therefore some alarms may still be seen in the network which should have been cancelled automatically. Solution / Workaround: 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: NA04202512 Exists in: CX5.0 Correction 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.

Nokia Siemens Networks

Company Confidential

11 (46)

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. STIRC may 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.

Nokia Siemens Networks

Company Confidential

12 (46)

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-356828482 Exists in: CX4.1 Correction Target: CX6 CD2.0 Description: When BTS hardware information is fetched for NetAct Hardware Browser the object (for example TSxx) BTS id is missing. Solution / Workaround: System Impact: No visibility of object BTS id.

3.1.2 Mismatch between the Air interface and LMU TDMA Frame Number
Problem report: 1-353257333 Exists 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 the LMU, 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 the proper 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 the problem will increase call setup failures.

3.1.3 Alarm 7616 OSCILLATOR ADJUSTING TEMPORARILY INTERRUPTED during startup


Problem report: 43295ESPE02 Exists in: CX5 CD3.0 Correction Target: CX6 CD2.0 Description:

Nokia Siemens Networks

Company Confidential

13 (46)

A chained Ultrasite configuration with LMU syncronisation and one or more slave cabinets is configured LMUMasterSlave. 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 restart 2) OMU in Master cabinet restart 3) 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 TEMPORARILY INTERRUPTED Oven oscillator adjustment function interrupted. may be activated for both master and slave cabinets. The fault clears after aproximatly 5 minutes. The site is not correctly synchronized until the BOIA 13MHz clock reference is within the correct network synchronization frequency. Solution / Workaround: System Impact: Handover and call drop KPIs are affected until the site is fully recovered and the alarms have cleared.

3.1.4 BCCH TRX stay in configuring state after reset from BTS Manager when NTIM expires
Problem report: 8803ESPE06 Exists in: CX6 Correction 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 BATTERY BACK-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 to the 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 BTS with 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: CX6 Correction Target: CX6 CD2.0

Nokia Siemens Networks

Company Confidential

14 (46)

Description: There is a noticeable downlink audio break after handover when AMR HR codec is used in target timeslot/cell. Comparison has been done to AMR FR codec and the audio break has been 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 the downlink direction. . Solution / Workaround: 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: 8348ESPE06 Exists 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.0 BTS Hardware Configurator. SiteWizard 6 BTS Hardware Configurator is launched and the previously saved xml file is opened. Previously opened file is selected from Hardware Configurator 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 trying to 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.0 Correction Target: CX6.0 CD2.0 Description: LMU-Abis sync is in use for the purpose of maintaining BSS syncronisation when GPS is lost 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 the incoming 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 as reference. If during the period when the synchronisation is from the PCM the PCM performance is not to the required specification and the FCLK clock slips more than 18s then DFCA performance will start to be compromised.

Nokia Siemens Networks

Company Confidential

15 (46)

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 the site or the correction of this error will take a great length of time during which the network performance for the site and its neighbours will be degraded. There are no alarms for these situations and these situations and they are only detectable either from KPI data or from drive tests.. Solution / Workaround: System Impact: KPI will be degraded by an increase in call drops, call setup and handover failures and degraded call quality.

3.2 Problems corrected in CX6 CD1.0 3.2.1 (UPDATED) 7606 TRX FAULTY FBUS HW Failure" with BB2A
Problem report: 1-328295312, NA04464446 Exists in: CX5 CD1.0 Correction 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 TRXs network wide. The problem does not clear even if the site is recommissioned 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 LGF version that the correction target could not be met. Further investigations were done and a correction for this issue was found for BB2A plug in units. Still further improvement needs to be done for BB2F (handled with another problem report). Further investigations have proven that the BB2F problem was due to random HW failure in 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 the BB2A 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-242632132 Exists in: CX4.1 CD4.0 Correction Target: CX6 CD1.0 Description:

Nokia Siemens Networks

Company Confidential

16 (46)

The alarm 7606 TRX Faulty No data is received from DIBA Asic traffic channels to CHDSP is randomly seen in some customer networks. The alarm can activate in BBhopping 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 also with 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.0 Correction 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 KPIs

3.2.4 UltraSite transmits in None Shutdown state after Abis break


Problem report: 7840ESPE07 Exists in: CX5 Correction Target: CX6 CD1.0 Description: UltraSite BBU is set as NONE. Parameters NTIM=2 and BTIM=7 are set. Mains breakdown alarm is generated. Alarm 7995 is activated and reported to BTS Manager and BSC. Site enters into None Shutdown state after expiry of timers. BCCH transmission is stopped. A short Abis break is generated. After the Abis break a BCCH transmission is accidentally started. The BCCH transmission is stopped after the time duration of NTIM + BTIM as BSC sends power supply off again for all TRXs. Solution / Workaround: 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.

Nokia Siemens Networks

Company Confidential

17 (46)

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


Problem report: 7729ESPE07 Exists in: CX5 Correction Target: CX6 CD1.0 Description: Clock Synchronization is defined as LMU at BSC (CS=LMU,SENA=T). Clock Synchronization 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 synchronization source. 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 this BCF shall cause loss of service to all slaved BTS" where as there are no slaved BTS. Solution / Workaround: System Impact: The Synchronization state is wrong. Wrong message is displayed at BTS Manager when the 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: 7758ESPE07 Exists in: CX5 CD4.0 Correction 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 BTS Manager and BSC. After Unblocking the BCCH TRX the TRX comes into working state and alarm 7208 is cancelled. Site goes into NONE shutdown state after some time and the alarm 7995 is cancelled. After about 5-6 minutes the BCCH TRX comes up into working state and non BCCH TRX remain 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 TRXs are not recovering from the Shutdown state after alarm 7995 cancellation if BCCH TRX is blocked/unblocked during Shutdown.

Nokia Siemens Networks

Company Confidential

18 (46)

3.3 Problems corrected in CX5 CD4.0 3.3.1 High SDCCH rejection on BB-hop or Antenna-hop sites
Problem report: 1-353848155, 1-358881121 Exists in: CX5 CD2.0 Correction 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 no blocking 76xx alarms and the BTS is in working state (WO). Alarms 7738 BTS with no transactions and 7745 Channel failure rate above defined threshold 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


Problem report: 1-339197891 Exists in: CX4.1 Correction Target: CX5 CD4.0 Description: When PSM4 alarm (warning) or Low Voltage alarm is active it duplicates a singular active PSM alarm. In the case of multiple active PSM alarms it will duplicate the alarm with the lowest severity at the BTS. When the PSM4 alarm (warning) or the low voltage alarm is cancelled it will cancel the severity alarm it is duplicating. PSM4 alarm can be generated by temperature, battery test event, door open or any alarm designated 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 the battery voltage is low when mains supply failure as occurred. The Low Voltage alarm is also used during the battery test procedure by changing the severity it will prevent this alarm 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 pull down menu.

Nokia Siemens Networks

Company Confidential

19 (46)

Change severity of Low Voltage alarm 1. 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 generation and 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: CX5 Correction Target: CX5 CD4.0 Description: Abis loop test is always failing for radio timeslot 6 when EGPRS is enabled. The test result in 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-252259905 Exists in: CX4.1 CD3.0 Correction Target: CX5 CD4.0 Description: Antenna hopping was activated to RF hopping sectors under the same BCF. The same channel number was used in both sectors MALs. Both sectors used different HSN. Only few calls were successfully established on the second sector and number of assignment failures increased on TCH TRX. Solution / Workaround: Remove or change overlapping frequency in MAL used in the other sector under the same BCF. If the amount of frequencies is small, then the same MAL and HSN can be used for all sectors 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
Problem report: 33787ES08P Exists in: CX4.1 CD4.0 Correction Target: CX5 CD4.0 & CX6

Nokia Siemens Networks

Company Confidential

20 (46)

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 will cause 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
Problem report: 1-275540244 Exists in: CX4.1 Correction Target: CX5 CD4.0 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 take approximately 5-10 minutes per TRX. It may take up to one hour until the BCCH is reconfigured 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-294637987 Exists 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 as an HW configuration candidate. The file is opened in HW Configurator with Configuration Wizard | Search for Configuration Candidate. After selecting the previously saved file all the 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.

Nokia Siemens Networks

Company Confidential

21 (46)

3.4 Problems corrected in CX6


The BTS SW CX6 release schedule was before CX5 CD4.0, thus the correction content in CX6 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-358881121 Exists in: CX5 CD2.0 Correction 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 no blocking 76xx alarms and the BTS is in working state (WO). Alarms 7738 BTS with no transactions and 7745 Channel failure rate above defined threshold 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: 33787ES08P Exists in: CX4.1 CD4.0 Correction Target: CX5 CD4.0 & CX6 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 will cause 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.

Nokia Siemens Networks

Company Confidential

22 (46)

3.5 Problems corrected in CX5 CD3.0 3.5.1 Problem with unnecessary 7606 alarms
Problem report: 1-232152255, 1-207163193 Exists in: CX4.1 CD2.0 Correction Target: CX5 CD3.0 Description: Two unnecessary TRX Faulty 7606 alarms are seen randomly in UltraSite BTS sites when using 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-312045192 Exists in: CX4.1 CD3.0 Correction Target: CX5 CD3.0 Description: Some UltraSite BTSs were alarming 7738 BTS WITH NO TRANSACTIONS and 7725 TRAFFIC CHANNEL ACTIVATION FAILURE. It was noticed that the BTS could not handle any traffic. Only alarms 7738 and 7725 were active. In some cases only alarm 7738 was active or alarm 7725. No calls were possible and the BTS needed to be restarted by Lock/Unlock from BSC. The root cause has been identified as combined DSP and O&M SW problem. The primary failure 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 DSP SW 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 30th 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 ODCM cabinet HWC SW
Problem report: 18133ES10P Exists in: SiteWizard5 CD2 (HW Configurator5 CD2) Correction Target: SiteWizard5 CD3 (HW Configurator5 CD3)

Nokia Siemens Networks

Company Confidential

23 (46)

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 Hardware Configurator 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). Solution / Workaround: System Impact: The WCxT can not be configured to BTS Configuration file thus the MHA and RSSI alarms might not work properly if the TX cable definitions are missing.

3.5.4 Interference with HR TCH during high traffic


Problem report: 1-288444521 Exists in: CX4.1 CD2.0 Correction Target: CX5 CD3.0 Description: When a Half Rate TCH is activated by the BSC but a mobile is not yet reached the channel, a RF Resource Indicator message is sent by the BTS for the TCH with a high ILEV value. The ILEV value can be seen with MML (ZERO). In BTS the ILEV values are reported from idle TCH channels only. When the Alerting - Connect phase is reached, the RF Resource Indication message is not reported for the TCH anymore as mobile has reached the channel. The BSC is using the high ILEV value which is received earlier from RF resource Indicator message and shows the 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 been deactivated. The incorrect value is reported to the BSC by the first RF Resource Indication message after the channel has been released. Solution / Workaround: System Impact: The ILEV value in ZERO printout shows high Interference Levels when there is no real Interference in the network. The problem does not affect to the normal operation of the BTS.

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


Problem report: 5286C02 Exists 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 HW Configurator 5 CD2.0. When MNTB units are configured to the HWC file, it can be seen that the units are correctly shown in the Cabinet Units view. When the antenna settings are set in the Antenna Settings view, no MHA is seen in the windows. The problem means that MNTB unit configurations cannot be set and sent to the BTS when configured with HW Configurator 5 CD2.0. The problem is specific to 800 band only.

Nokia Siemens Networks

Company Confidential

24 (46)

Solution / Workaround: Use HW Configurator 5 CD1.0 to set up the MNTBs. Select high gain in the Antenna Properties 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 is connected 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 is changed 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: 22280ES11P Reported in: CX4.1 Correction target: CX5 CD3.0 Description: Site Support System (SSS) supplies power to UltraSite master and slave cabinets in a chained configuration. The Mains Breakdown indication is sent to the UltraSite master cabinet from the SSS using 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 to get 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

Nokia Siemens Networks

Company Confidential

25 (46)

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 alarm 7606 TRX FAULTY Non EDGE TRX device type used accidentally in Edge Capable Mode is raised, and the TRX state is disabled (BL-TRX). The BCCH is reconfigured to an EDGE TRX. This is expected behaviour as STIRC is not supporting non-EDGE TRx with BB2A. When STIRC is disabled, alarm 7606 is cancelled but the TRX stays in BL-RSL state with alarm 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. The EDGE 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 is accidentally 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 the unit/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 slave BCFs on both BTS and BSC level. This will lead to a situation where the intelligent shutdown does not work properly and the capacity of Site Support System batteries is unnecessarily used. As there is no real need for OMU reset during intelligent shutdown and the problem is more in system design, Nokia has decided not to support the OMU reset during intelligent shutdown. 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

Nokia Siemens Networks

Company Confidential

26 (46)

Description: The problem occurs only when all TRXs under the BTS are first locally blocked and then the 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 the equipment view. Telecom working is displayed at the bottom of the window. The sector is still 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 BCCH TRX/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 made when 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 5 Correction 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 the figure of Configuration Candidate in Hardware Configurator (HWC) when connecting up TRX4, TRX8, or TRX12. The HWC displays the TX cabling in an incorrect position between 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 performance of 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 unblocked locally in IDD/4UD configuration
Problem report: 4026C02, 5126C01 Reported 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. The transmission 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 third sector from BTS Manager. When a local block/unblock is done in the first sector, all calls are dropped in the second sector. When BB2F is used for Aux TRXs of the second sector, alarms 7607 TRX OPERATION 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.

Nokia Siemens Networks

Company Confidential

27 (46)

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 from BTS 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 is selected 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 is started 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. The RTC is configured using the RTC Configure command with BTS Manager. Immediately after the RTC Configure command is sent to the RTC, the other sector goes down with alarm 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 the first sector stay in the configuring state. When the second sector is unblocked with BTS Manager, alarm 7208 LOCAL BLOCK is cancelled. Both sectors take multiple resets and the second sector stays in the BL-BTS state at BSC even though alarm 7208 is cancelled. Workaround: Do not unblock the sector with wrong RTC frequencies. BCF lock/unlock will clear the situation. 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 CRC checking included in the application files does not detect corruption in the files. In this case the 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 files stored on the BSC disk before downloading the BTS SW to the base stations.

Nokia Siemens Networks

Company Confidential

28 (46)

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 nonEDGE sector where BB2A boards are used. Alarm 7606 TRX FAULTY Non EDGE TRX device 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 Capable Mode 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 BB2A for BCCH TRX is red. Workaround: Restart the sector. System impact: Alarm 7606 TRX FAULTY EDGE TRX device type used accidentally in Edge Capable Mode 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: CX5 Correction target: CX5 CD2.0 Description: A site is configured as 2+2+2 IDD. Sector 3 has an active TSxx unit alarm 7606 TRX FAULTY 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 problem does 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 BTS Manager. 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

Nokia Siemens Networks

Company Confidential

29 (46)

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 indicates that 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. Cannot get response from BTS SW three times for the newest, reliable, and raw values respectively. Thereafter, the RSSI window opens with message Failed to get response in all three sub-windows. The correct message should be Requesting RSSI comparison values failed. Feature is not activated and it will be shown for the newest, reliable, and raw values. After selecting OK in each of the conditions stated above, the data comparison window will appear. RSSI Sections 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.

3.7 Problems corrected in BTS SW CX5 CD1.1


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-264900231 Exists in: CX4.1 CD2.0 Correction 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 maybe unable 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.0 Correction target: CX5 CD1.1

Nokia Siemens Networks

Company Confidential

30 (46)

Description: 7606 TRX FAULTY FBUS HW Failure" alarms are still rarely reported even when using the correction delivered with CX4.1 CD2.0. The alarms are seen only with BB-hopping configurations. Previously informed correction in CX4.1 CD2.0 did not correct these cases as further investigation has found another root cause which is caused by an unexplained TRX restart in BB-hopping sector. The reset was caused by a problem in internal message queue 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 the problem happens.

3.8 Problems corrected in BTS SW CX5 CD1.0

Note BTS SW CX5 does not include all the problem corrections that were targeted in BTS SW CX4.1 CD4.0. Please see the chapter Problems corrected in BTS SW CX4.1 CD4.0 below for further information. If BTS SW CX5 is not defined in the correction target field, then the correction is automatically implemented in CX5 CD1.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-282786191 Exists in: CX4.1 CD4.0 Correction 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 service is 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 CX5 CD1.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 visits are required to recover.

Nokia Siemens Networks

Company Confidential

31 (46)

3.8.2 Unnecessary cooling fan alarms


Problem report: 32891ES09P Exists in: CX4.0 Correction target: CX5 CD1.0 Description: When TSxB unit versions 4xx are used there is a possibility to see alarm 7602 BCF NOTIFICATION: Cooling fan speed has reduced from the set speed. The alarm is caused by the error in fan speed control where the set speed is just below the alarm threshold limits. Although this is seen only with UltraSite EDGE cabinet variant ODCM (Nokia UltraSite EDGE BTS Mini Outdoor), it is potentially possible also for other cabinet variants. The alarm is intermittent depending on TRX operating temperature, which will change depending 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 is dangerously high, consider the fan alarm as real and follow the normal troubleshooting instructions. 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 pre amplifier) 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 at BSC. A power off/power on of the PWSB units will recover the problem situation, but the problem might 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: 4918C01 Exists 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.

Nokia Siemens Networks

Company Confidential

32 (46)

In some cases when BCCH reconfiguration is attempted, alarms 7606 TRX Faulty F-BUS HW 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 in another 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: 19069ES11P Exists 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 Site Information 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 Degraded with a description 'RX levels differ too much between main and diversity antennas' is active, the detailed cause for the alarm can be seen in these RSSI results at BTS Manager. However, if the alarm condition and the alarm are cancelled, the alarm details are 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 7604 BTS Operation Degraded with a description 'RX levels differ too much between main and diversity 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 RSSI results are read.

3.8.6 User may change default cross connections with HW Configurator


Problem report: 6530ES07P Exists in: HW Configurator CX4.0 Correction target: HW Configurator with CX5 CD1.0 Description: It is possible to change the default Base Band - TRX unit cross connections with HW Configurator, even if the functionality is not supported any more. UltraSite TN10 informs that The cross connection functionality will be permanently removed in the CX4.0 SW release, but this change has not been implemented yet. Workaround: System impact: Non-supported BB2-TRX cross connections can be made with HW Configurator.

Nokia Siemens Networks

Company Confidential

33 (46)

3.9 Problems corrected in BTS SW CX5


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

3.9.1 Multiple resets of BTS after auxiliary TRX of another sector is removed
Problem report: 4328C01 Exists in: CX4.1 Correction target: CX5 Description: A second sector from 1+1 IDD (TSGB+BB2F) configuration is locked from the BSC. The auxiliary 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 and auxiliary 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 an auxiliary 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-Connect Phase. Although there is no speech, the FER statistics are still counted. The first few measurement reports always show high FER values. This problem does affect both non-AMR and AMR speech codecs. The correction will improve the BAD FER KPI values with all speech codecs. The first codec used information in the UL (sent every SACCH multi-frame) is sometimes corrupted and shows an incorrect first codec. This problem impacts the building of the correlation table that is used for updating the Estimated DL FER statistics. For the correlation table, the UL FER value is stored for all the codecs between the first codec used and the last codec used. If the first codec used is corrupted, it can cause too good or too bad Estimated DL FER to all AMR speech codecs. Workaround: -

Nokia Siemens Networks

Company Confidential

34 (46)

System impact: The problems might cause the Link Adaptation to work inefficiently, that is, codecs being changed when not supposed to. The KPI for UL RX Quality share of levels 6 and 7 will show slight increase in EDGE HW configurations with HR calls. The BAD FER KPIs will show a minor improvement with all speech codecs. This is largely a 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 BTS Manager
Problem report: 2701C02 Exists 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 is possible to perform a local Block/Unblock or Reset command via the BTS. If such an action is carried out, the TRX alarm will cancel and the faulty TRX will be added to the Hopping list after a sector reconfiguration. This behaviour is unexpected and against specification. 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: 6925ES05X Exists in: CX4.1 Correction target: CX5 Applies 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 show invalid 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.

Nokia Siemens Networks

Company Confidential

35 (46)

On the EAC Input Settings screen, the Open and Closed radio buttons are not updated when 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.1 Correction target: CX5 Applies 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 BCCH reconfiguration 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 is required. Workaround: Lock/Unlock the BCF. System impact: An IDD configuration fails in a BCCH reconfiguration after a local BCCH TRX Block is given 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.

Nokia Siemens Networks

Company Confidential

36 (46)

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

3.10.1 (UPDATED) Bad downlink Mean BEP reported with DL DTX applied
Problem report: 8174ESPE06 Exists in: CX4.1 Correction Target: N/A Description: During a speech call and silence period when DL DTX is applied the Mean BEP values degrades in downlink measurement report. DL Rx Quality calculation is affected since BSC uses 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 been delivered during 2007. There is no such problem reported when using later Nokia handsets. Solution / Workaround: 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: NA04204140 Exists in: CX4.1 CD2.0 Correction 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 with BB2A units has been solved in BTS SW CX6 CD1.0 but investigation with BB2F was inconclusive during the pilot. Further investigation of problem BTS HW units in laboratory was clearly showing that the issue 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 HWS according to normal repair process. Solution / Workaround: A TRX/BTS restart might solve the problem for few hours but the alarm reoccurs. Rollback to 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 do not 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.

Nokia Siemens Networks

Company Confidential

37 (46)

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


Problem report: 17305ESPE01 Exists in: CX6 Correction 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 and UltraSite. ITN C3 CD2 Software is remotely downloaded to all nodes. Activation of the Software is started first on RRI and then STM and Bridge last. During this operation Version Mismatch (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, the alarms are cancelled in the node. The node is free of alarms, but the alarm for Q1 address 4080 (PDH part) in BSC (and NetAct) is not cancelled. Further investigation revealed that the problem can be avoided when ITN SW upgraded in the correct sequence: starting with the node master unit (unit in slot 1). The upgrade process is documented in ITN SW installation documents. Further improvements are done for the installation instructions document to avoid situations where the alarm cancellation needs 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 cancel the alarm manually from BSC/NetAct. System Impact: Alarm 8221 is not cancelled from BSC/NetAct even if the MetroHub SW levels are correctly updated.

3.10.4 Serial on USB port is not recognized by BTS Manager


Problem report: 16481ESPE01 Exists in: BTS Manager 5 Correction Target: N/A Description: When using a serial on USB port the BTS Manager does not recognize the communication port. 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 only option is to use a USB to Serial adaptor. This problem has been seen using popular makes of USB to Serial adaptors: 1) Targus model PA088E 2) Belkin model F5U409 This fault needs more investigation in SiteWizard GCS side as it seems to be highly related 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

Nokia Siemens Networks

Company Confidential

38 (46)

to try different adaptor if problem arise or contact adaptor manufacturer for a windows driver which could correct the situation. Solution / Workaround: The problem is seen only with some adaptor models. It is recommended to try different adaptor 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: 7789ESPE07 Exists in: CX5 Correction Target: N/A Description: One sector has Antenna Hopping and second sector has RF + Antenna Hopping. The VSWR Monitoring is enabled on both antennas for the first sector. Power level for first sector 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 BTS Manager and BSC. NOTE: During further investigation this fault was found to be working as specified. The VSWR measurement is not done if the OMU signaling link is blocked. Solution / Workaround: System Impact: The alarm activation does not work locally when OMU signaling is blocked. When the OMU 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-320693602 Exists in: CX3.3-2 Correction 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 as specified. The purpose of TA is to ensure accurate reception of the transmitted burst and as 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.

Nokia Siemens Networks

Company Confidential

39 (46)

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

3.10.7 Codec first and codec last values are wrongly reported in some scenarios with BB2A
Problem report: 8704ES05X Reported in: CX4.1 Correction target: N/A Description: GSM baseband unit BB2A is used. During an AMR call setup or bad uplink RF interference conditions, AMR UL CODEC FIRST and AMR UL CODEC LAST values always show 3 instead of the codec used and irrespective 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 estimation algorithm). AMR UL CODEC LAST is used to map the uplink FER counts on BSC according to the codec. Originally this problem has been made according to findings in EDGE HW side. During investigations 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.1 activation
Problem reports: 1-111349391, 1-109258175, 1-126315871, 1-127937455, 1-199998801 Exists in: CX4.1 Correction target: N/A Description: After upgrading the BTS SW level to CX4.1, some TRXs in the BB-hopping sector restart under high traffic. The alarm 7606 FBUS HW FAILURE is activated after the TRX restart because of BB-hopping. The problem happens rarely. The problem has not been reported against CX4.1 CD2.0 and Nokia has not been able to reproduce the problem with that BTS SW. Further R&D analysis has shown that the problem has been corrected in BTS SW CX4.1 CD2.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:

Nokia Siemens Networks

Company Confidential

40 (46)

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

3.10.9 Alarm 7615 RTS IS IN TEST USE does not cancel after the completion of the TRX test
Problem report: 7134ES05X Exists in: CX4.1 Correction target: N/A Description: Sometimes, when a TRX test command is performed from the BTS Manager, alarm 7615 RTS 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 be planned 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 shutdown mode
Problem report: 14999ES09P Exists in: CX4.0-4 Correction target: N/A Description: When Intelligent Shutdown is activated, alarm 7995 is reported at the BSC and the TRXs are shut down (BL-PWR). However, the fans associated with the shutdown TRXs continue running. This is not the expected 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 the TRXs 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-88008859 Exists in: ITN2.1 Correction target: ITN C3.0 CD1.0 Description:

Nokia Siemens Networks

Company Confidential

41 (46)

Alarm 8150 FAULT IN UNIT is active for the transmission unit. The alarm cannot be cleared 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 reference voltage is used for calibration of the internal oscillator of the FXC unit. If no valid external synchronisation source is available (for example during a transmission break), the internal oscillator 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 the alarm may still be active after the SW upgrade if the reference voltage is outside the new supported range. 2) Recalibrate the internal oscillator in the transmission card and inhibit the alarm in the unit alarm properties window of the element manager. 3) If there is third party transmission equipment synchronized to the FXC unit and the behavior of the equipment when receiving a degraded reference clock 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, this could cause, in rare circumstances, the internal oscillator to run outside the specified frequency of +- 50ppm for E1 or 32ppm for T1. Although still unlikely, a network containing third 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 and there is no service degradation at the BTS and there 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 uplink frequency
Problem report: 3443ES07P Exists in: CX4.0-5 Correction 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 results deteriorated as expected. When the interference level was increased up to -85 dBm, the TRX test started failing. The reported failure reasons were: Failed High Bit Error in RF Loop detected or Unable to measure TX Power Level. Both failure reasons suggest a clear TSxx (HW) unit failure although the HW is working correctly. In a live network it is quite possible (depending on the frequency planning) to have interference on the UL frequency when a TRX test is run. This may cause unnecessary 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

Nokia Siemens Networks

Company Confidential

42 (46)

position/frequency still fails in the TRX test with the same reason, measure the possible interference 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-49110163 Exists in: N/A Correction 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 the first successful GPRS transaction. The problem may happen when using mixed EDGE and GSM HW and the GP timeslots are configured in an EDGE TRX. Workaround: System impact: No effect on end-user services.

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
Problem report: 1-20644204, 3-2742416, 1-19996945 Exists in: CX3.3 Correction target: N/A Description: Commissioning is performed on the BTS, where the TCH timeslot allocation at the BSC does not match the TCH timeslot allocation at the BTS Traffic Manager. However, the commissioning 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 always fail the test indicating that a mismatch might exist. Workaround: System impact: No effect on end-user services.

3.10.15 The cabinet fan does not restart when the intelligent shutdown situation is cancelled
Problem report: 19080ES09P Exists in: CX4.1 Correction 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 intelligent shutdown situation is cancelled. It is observed that after the cancellation of the 'Mains

Nokia Siemens Networks

Company Confidential

43 (46)

breakdown' alarm, although all the TRXs come back to working state, the cabinet door fan is 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 to the new temperature information. In Technical Note No. 60, Nokia informed about the existence of this problem with a correction target CX4.1 CD1.0. However, a further investigation has proved that this fault does 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 the actual fan rotation curve
Problem report: 3993ES03 Exists in: CX3.3-1 Correction target: N/A Description: The UltraSite CAFA cabinet fan speed control curve in the BTS SW does not match the actual 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 Recovery Improvement feature is used
Problem report: 4596ES01 Exists in: CX4.1 Correction target: N/A Description: An OMU block is incompatible with the Site Sync Recovery Improvement feature because it 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 Site Sync 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 TalkTalkUltraSite co-siting configuration after mains shortage


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

Nokia Siemens Networks

Company Confidential

44 (46)

Description: In the Talk-FamilyTalk-FamilyUltraSite co-siting configuration, the Slave UltraSite cabinet is without a battery backup. A mains power breakdown causes a situation where the synchronisation signal between the Master clock source/BTS and the Slave UltraSite BTS is lost. After the mains power is recovered, the Talk-Family Slave BTS might not recover the synchronisation from the Master clock source/BTS. This problem will not be corrected in the BTS SW. The recommendation is to use the workaround. Workaround: To avoid unwanted power breaks, it is recommended to use a battery backup for the UltraSite Slave cabinet. Reset the Slave BCFs/BTSs from the BSC. If the problem remains, change the synchronisation 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: 17438ES09P Exists in: CX4.1 Correction 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 that does 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 supported by the older SW have to be deactivated first. System impact: -

Nokia Siemens Networks

Company Confidential

45 (46)

Disclaimer The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given as is and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright Nokia Siemens Networks 2009. All rights reserved.

Nokia Siemens Networks

Company Confidential

46 (46)