DF6.0-2 GFR_2000 B6X 056759 AE

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE

http://slidepdf.com/reader/full/df60-2-gfr2000-b6x-056759-ae 1/30

B6X 056759 AEIssue 20.0.0

© Nokia Oyj 1 (30)

Nokia Talk-Family and Nokia PrimeSite BTSSW Release

Generic Failure Report

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE



2 (30) © Nokia Oyj B6X 056759 AEIssue 20.0.0

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for theuse of Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means withoutthe prior written permission of Nokia. The document has been prepared to be used by

professional and properly trained personnel, and the customer assumes full responsibilitywhen using it. Nokia welcomes customer comments as part of the process of continuousdevelopment and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However,Nokia has made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia will, if necessary,explain issues which may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDINGMONETARY LOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright accordingto the applicable laws.

NOKIA logo is a registered trademark of Nokia Oyj.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Oyj 2003. All rights reserved.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE



B6X 056759 AEIssue 20.0.0

© Nokia Oyj 3 (30)

Contents

1 Introduction ............................................................................................5

2 Open Problems.......................................................................................7 2.1 New Open Problems................................................................................8 2.2 Open TRX SW Problems .........................................................................9 2.3 Open BCF SW Problems .......................................................................10 2.4 Open MMI SW Problems........................................................................14 2.5 Open MMIDATA SW Problems..............................................................15 2.6 Other Open Problems ............................................................................16

3 Solved Problems..................................................................................19 3.1 Problems Solved in DF6.0-2 ..................................................................20 3.2 Problems Solved in DF6.0-1 ..................................................................22 3.3 Problems Solved in DF6.0......................................................................23 3.4 Problems Solved in DF5.1-1 ..................................................................27 3.5 Problems Solved in DF5.1......................................................................29 3.6 Problems Solved in DF5.0-1 ..................................................................30

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Introduction

B6X 056759 AEIssue 20.0.0

© Nokia Oyj 5 (30)

1 Introduction This document describes the current unsolved problems in Nokia Talk-family

and Nokia PrimeSite GSM 900 and 1800 BTS software (SW), firmware (FW),

and hardware (HW), and the corrections made to the existing problems.

This report is issued on 30th August, 2003.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Open Problems

B6X 056759 AEIssue 20.0.0

© Nokia Oyj 7 (30)

2 Open Problems This chapter lists the open problems of the Nokia Talk-family and Nokia

PrimeSite GSM 900 and GSM 1800 base stations. In the tables below, the

following information is displayed:

Int. Ref. / Date

This is the internal reference number of the problem. It is provided here to help

identify any particular problem. The date when the problem was observed or a

complaint was received is also included. If the letter 'S' precedes the FMS

number of the problem, the fault is classified as service affecting. That means

that the fault may affect ongoing calls.

The problems are tagged with ‘GSM 900’ if they are GSM 900 specific and

with ‘GSM 1800’ if they are GSM 1800 specific. Problems that are not

preceded by any frequency band identifier apply to both GSM 900 and GSM

1800 base stations.

The problems are tagged with ‘PrimeSite’ if they are Nokia PrimeSite specific

and with ‘Talk-fam.’ if they are Nokia Talk-family specific. Problems that are

not preceded by any generation identifier apply to both Nokia PrimeSite and

Nokia Talk-family base stations.

If the description of the problem has been updated or new information has been

added to or removed from the list of open problems, the problem number is

underlined.

Problem Description

This field includes the name of the problem, briefly describes the problem and

the symptoms, and may give instructions on how to avoid or get around the

problem.

Exists in

This field lists the SW, HW and FW versions in which the problem exists. The

FW version refers to the actual EPROM version.

Solved in

This is our latest and best estimation of the BTS SW release / HW or FW

version in which the problem will be corrected. When the field is marked with

'TBA', the correction schedule is yet to be defined. When the field is marked

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




with '-', the problem has only minor impact on BTS operation and will not be

corrected.

2.1 New Open Problems

This section lists all the new problems reported since the previous issue of the

Generic Failure Status Report.

Table 1. New Problems of Nokia Talk-family and Nokia PrimeSite GSM900 and 1800 BTSs

Int. Ref.Date

Problem Description Exists in Solved in

P2272416 TRX HW Test Shown as Failed During resetDF6.0 -

During a local reset of a site from the DF6.0 MMI, the TRXs are shown as havingfailed the HW test when they are not ready for the test. These messages are onlyfor diagnostic purposes as any real failures would be reported when the BCF is insupervisory state.

Workaround Solution: in the MMI options, set filter on so that the erroneous failmessages are not seen.

P2551016 7900 on one TRX may mask 7530 alarm on

another TRX

DF5.0 -

Occasionally, in a two TRX sector where one TRX is showing alarm "7900, Noconnection to TRX", and the other TRX is also shown as BL-TRX at the BSC, thereason for the TX failure may not be shown in the alarm history until after a sector reset.

Workaround Solution: reset the sector using the ZEQS command or the sector resetcommand in the BTS MMI. All alarms will then be shown in the alarm history.

P2610616 7976-Booster Gain Level Too Low' alarm when

Pmax<4dB

DF5.1-1 DF7.0

On some booster sites where PMAX is set to be less than 2, that is 4dB, the alarm"7976, Booster gain level too low" is sometimes raised.

Workaround Solution: set PMAX at the BSC to 2 (4dB) and reset the affected site.

P2684516 Remote Transcoder Failure message sent at

wrong interval

DF5.1-1 DF7.0

When there is noise on the TRAU frames some time the connection failuremessage is duplicated thus meaning that there a 1-second interval between themessages does not occur.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Open Problems

B6X 056759 AEIssue 20.0.0

© Nokia Oyj 9 (30)

2.2 Open TRX SW Problems

Table 2. Open Problems of Nokia Talk-family and Nokia PrimeSite GSM900 and 1800 BTSs, TRX SW

Int. Ref.Date


5623 TRX: Alarm/Cancel 7549 during ReconfigurationD1.0- -

18Nov97Talk-fam.

Occasionally, during a reconfiguration, alarm/cancel 7549 ‘Internal data transfer failure’ occurs.

5629 TRX: Alarm 7540 during ReconfigurationD1.0- -

18Nov97Talk-fam.

Occasionally, during a reconfiguration, alarm 7540 ‘Air interface dumb’ becomesactive.

For recovery, a TRX reset is required.

9061 TRX: With RF Hopping All TRXs Display 'Loop'

during TRX Loop Test

D1.0- -

12Sep98Talk-fam.

RF hopping is in use. If the TRX Loop Test is performed on one of the hoppingTRXs, all hopping TRXs in the BTS show 'Loop' on their displays.

2475316 TRX Boot SW Shown as Not definedDF6.0 -

12 Aug 02PrimeSite

Only

After BTS SW DF6.0 is downloaded to a PrimeSite the MMI shows that the TRXboot SW is “Not defined”. The SW can be brought in to use however with a sitereset.

DF7.0 will have no boot SW changes so once DF6.0 is brought into use thisproblem will no longer be seen

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




2.3 Open BCF SW Problems

Table 3. Open Problems of Nokia Talk-family and Nokia PrimeSite GSM900 and 1800 BTSs, BCF SW

Int. Ref.Date


218 BCF: Calls Fail after Floating TRX SwitchoverDF3.0- -

26Nov98Talk-fam.

RF hopping is used with a floating TRX configuration. When a floating TRX replacesthe faulty BCCH TRX, calls cannot be made via this sector.

583 BCF/STM: No 'BTS RX Level' in STM Test ReportDF3.0- –

10Sep98Talk-fam.

The BTS RX Level is not always given in the STM loop test report.

5113 BCF: BTS Lock/Unlock Does Not Work with Floating

TRX

DF3.0- –

29May98Talk-fam.

After a Floating TRX has replaced a faulty BCCH TRX, BTS lock/unlock does notwork.

TRX lock/unlock can be given instead.

5149 BCF: Poor Call Quality When Locked TRX in

BB-Hopping Sector

D1.0- -

03Apr98Talk-fam.

BB hopping is in use. A sector is locked and then one of the TRXs in that sector islocked. The OMU is reset. After the initialisation, the sector is unlocked while theTRX is left locked. After a while, the unlocked TRXs issue alarms 7515 ‘Failure inconnection to frequency hopping’, no other alarms become active. If calls are madevia this sector, the quality of the calls is poor.

For recovery, a site reset is required.

5395 BCF/STM: STM Loop Test Fails in Frequency

Hopping Sector if ARFN Separation Is Greater

than 112

DF3.0- –

08Jan98GSM 1800Talk-fam.

If an STM loop test is performed in a BB- or RF-hopping sector when the ARFNseparation is greater than 112, the loop test fails with the following test results: BER> 50%, BTS & STM RX level –110 and quality 7.

5605 BCF: Incorrect Alarm Diagnostics Information with

ICE Configuration

DF3.0- –

18Nov97Talk-fam.

In an ICE sector (i.e. the capacity and the coverage cells) with an AFE and RTC,RMUA LNA and AFE LNA alarms are reported incorrectly.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Open Problems

B6X 056759 AEIssue 20.0.0

© Nokia Oyj 11 (30)

Int. Ref.Date


5701 BCF: Diversity Branch Not Tested in RX SensitivityMeasurement

DF2.0- –

16Sep97Talk-fam.

The STM RX Sensitivity measurement does not test the diversity branch.

However, the diversity branch can be tested with the STM loop test via cable.

5899 BCF: Alarm 7514 May Occur after Site ResetDF2.0- –

24Jun97PrimeSite

A Slave Nokia PrimeSite may issue alarm 7514 ’13 MHz clock is missing in TRX’after a site reset. This alarm blocks the TRX.

For recovery, a new site reset is required.

6175 BCF: Incorrect Unit Statuses in HW Report

DF2.0- –

07Mar97 A HW inquiry is made from the NMS/2000. In the case of active minor alarms for theBCFA or TRXs, the unit statuses for the BCFA or TRX objects are reported in theHW Report as ’Failed’ instead of ‘Alive’.

6325 BCF: Alarm 7842 Not ActivatedDF2.0- –

17Nov96Talk-fam.

When the BCFA requests the BCCH power level from the BCCH TRX, and thetransmitter is reported to be off, the BCFA does not issue alarm 7842 ‘No BCCHtransmission activated’, nor any other alarms.

6409 BCF: BCF Configures STM too Early After BCCH

Field Strength Measurement

DF2.0- –

28Jun96Talk-fam.

BCCH measurement is performed with the STM. Occasionally, the BCF configuresthe STM with default parameters before the STM has sent the test report. The testfails with reason ‘STM communication failure’.

6553 BCF: MMI PC Restart May Cause BCF ResetD1.0- –

17Feb96 The MMI PC is connected to the BCF unit. If the user presses CTRL+ALT+DEL toboot the computer or if the computer starts while no physical mouse is installed, theBCF card may be reset.

To avoid this problem, disconnect the MMI-BCF cable before restarting your PC.

6571 BCF: Disable Abis Command from the MMI May Fail

D1.0- –

11Feb96Talk-fam.

When Disable Abis command is given from the MMI, the BCF initialisation may failand the BCF is started with LAPD connection.

For recovery, a new Disable Abis command has to be given.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




Int. Ref.Date


6583 BCF: Alarm 7860 after Reset if Service TerminalConnected

D1.0- –

08Jan96 The Service Terminal (ST) is connected to the TRUx. If the site or the BCF OMU isreset, alarm 7860 ‘No connection to transmission unit’ is unnecessarily activatedand cancelled.

6697 BCF/TRX: Unexpected Alarm 7548 to the MMID1.0- –

20Nov95 Alarm 7548 ‘Data transfer failure on Transcoder connection’ and its cancellation aresent to the MMI during data call and normal call set-ups in cases where frequencyhopping is in use. However, call set-ups are successful. This problem occurred withonly one MS model.

There will be no corrective actions to this problem.

6715 BCF: AFE Alarms Handled Differently in BCF Start-

Up Phase and in Online Phase

D1.0- –

06Nov95Talk-fam.

AFE alarms are handled differently during a site reset and when the BCF is inrunning state. If the control cable is disconnected from the AFE when the BCF is inreset state, alarms 7944 ‘Main Branch LNA out of order in antenna filter unit', 7946‘Diversity Branch LNA out of order in antenna filter unit’, 7937 ’Unit temperaturedangerously high’, 7939 ’Forward power too low at TX antenna’, and 7942 ’TXantenna faulty’ are sent to the BSC. If the same cable is disconnected when theBCF is in ‘WO’ state, alarm 7942 is not sent to the BSC.

However, the missing alarm does not affect the BTS operation because the BTS isblocked from use due to other fatal alarms.

16855 BCF: Incorrect Attenuation Information in STM

Test Report

DF4.0- –

07Sep99Talk-fam.

STM Loop Test is started from the BSC with default attenuation. In the loop testresults the reported level is correct but the text is incorrect. Loop test text is always"STM RX level with attenuation" even though the test was performed withoutattenuation.

21247 BCF: BTS Unlock Is Not Accepted after Hopping

Mode Change

DF2.0 –

1Dec99 Two sectors are locked from the BSC and the hopping mode is changed. When asector is unlocked, DX error 'BTS has detected mismatch between CA and MA' isseen on the BSC and unlocking fails.

When the hopping mode is changed only one sector should be locked at time.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Open Problems

B6X 056759 AEIssue 20.0.0


Int. Ref.Date


250053 BCF: Not all correct PSUs Power off WhenShutdown Mode is set to BCCH

DF4.0 –

31 Jul 01 In a 4+4+4 Citytalk configuration when BCCHs are on TRX7, 9 and 11 the PSUs for TRX 1-6 are not shutoff.

Workaround solution is to use preferred BCCH to keep the BCCH in the basiccabinet.

459073 BCF: TRX Connected to RTC in Slave BTS May

Stay Waiting for System Information

DF6.0 –

12 Sept 01Talk-Fam

When a 12 TRX Omni Dual RTC configuration is a slave in a synchronised BSS setup the TRXs may stay Waiting for Information when the site is recovering from a

loss of clock signal. A site reset will bring all TRXs to supervisory.

948316 STM/BCF: Alarm 7980 Starts and Cancels During

BCF Reset

DF5.0 –

11 July 01 Alarm 7980, No Connection to Site Test Monitor Unit, started and cancelled within10s when a BCF OMU reset is executed.

951716 BCF: MMI Shows SW Loading if TRX ID in the

HWDB and BSC are Different

DF5.0 –

10 Jul 00PrimeSite

If the TRX ID in the HWDB is different from the TRX ID at the BSC the device statusreport at the MMI shows SW Loading. TRX Loop Tests are not started and the

reason reported is "TRX number not consistent with database". This situation doesnot affect service.

968716 BCF: DAC Value Saved After Reset if changed less

than 10 Steps

DF5.0 DF7.0

21 Jul 00 When the DAC value is changed less than 10 steps from the saved value the newsetting is saved to flash after reset. Changes greater than 10 steps are not saved tothe flash after reset.

1457116 BCF: RTC SWR Local Test ResultDF5.0 DF7.0

23 Mar 01

Talk-Fam

During stand alone commissioning when the bit pattern 511 is sent the RTC SWR

measurement gives the result OUT OF RANGE even if the SWR is withinacceptable range.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




Int. Ref.Date


1626216 BCF: BTS Stays BL-RST after HWDB loaded toempty BCFA Card

DF5.0 DF7.0

09 Aug 01 If DF5.0 or late SW is running and there is no HWDB loaded in the BCFx flash thenany SW package that is downloaded which contains a HWDB will cause the BCF toremain in BL-RST.

Refer to Technical Note 153 for instructions on how SW and HWDB should beloaded from the BSC

1733051 HW Unit Status Fails for Minor ReasonsDF3.0 –

5 March 02When a HW enquiry is made at the NMS if there are active minor alarms the BCFAor TRX may be shown as failed in the HW report message.

2205016 Antenna Faulty alarm disables TRXDF6.0 –

27 March 02PrimeSite

Only

In PrimeSite, transmission of successive frames is alternated between the main anddiverse antennas. If the main antenna develops a fault, the transmission pathshould change to use diverse only and the TRX is not disabled.

When a DF6.0 HWDB is in use, the TRX is disabled when the 7591, AntennaFaulty, alarm is raised.

Workaround Solution: use a DF5.1 database even when using DF6.0 and later SW.

2601016 RACH Load Counters are Always 0DF6.0 DF7.0

4 Oct 02

When cell broadcast is used on an MBCCH the BTS does not increment the busycount or the access count. This means that the counters at the BSC are alwayszero. This is a purely statistical error and does not affect RACH operation.

2.4 Open MMI SW Problems

Table 4. Open Problems of Nokia Talk-family and Nokia PrimeSite GSM

900 and 1800 BTSs, MMI SW

Int. Ref.Date


2104316 Incorrect Number of RTC in MMIDF6.0 DF7.0

5 Feb 02When a HWDB is configured with only one RTC the MMI shows three RTC SWRreadings

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Open Problems

B6X 056759 AEIssue 20.0.0


Int. Ref.Date


2149216 MMI Error May be shown In MMI Window afterOMU Reset

DF6.0 DF7.0

27 Feb 02 After and OMU or Site reset from the MMI the following message may appear “MMIError #62: Response Timeout”. Neither MMI nor BTS operation is affected

2399616 Antenna Loop Test Cannot be Started IN MMI

with HWDB version 6.0

DF6.0 –

4 July 02PrimeSite

Only

When a HWDB created with DF6.0 is loaded on a PrimeSite the antenna loop testcannot be started. Error message “ Requested test cannot be carried out”.

2.5 Open MMIDATA SW Problems

Table 5. Open Problems of Nokia Talk-family and Nokia PrimeSite GSM900 and 1800 BTSs, MMIDATA SW

Int. Ref.Date


2420051 MMIDATA: Timeslot 0 defaults to wrong valuewhen AFx are used in extension cabinets

DF4.1 –

24 July 00 When AFx are defined in the extension cabinets for parallel sectoring the HWDB setsthe value of Timeslot 0 on the left hand TRX on the Shelf (7, 9 and 11) to 0 which isfor a BCCH timeslot. The result is that TRX loop tests cannot be run on the thoseTRX. Care should be taken to change the values to one of the other valid settings.

259073 Configuration Picture is not always correctDF5.1 TBA

13 March02

The configuration picture sometimes shows incorrect unit address numbers andomits some CCFx.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




2.6 Other Open Problems

Table 6. Open Problems of Nokia Talk-family and Nokia PrimeSite GSM900 and 1800 BTSs, Others

Int. Ref.Date


5293 High Interference Affects TRX Loop Test ResultsD1.0- -

19Mar98 TRX loop test is performed when the interference level is high. Depending on theinterference level, the loop test result shows increased BER level or the loop test failswith reason ‘HW failure’. However, there is no HW failure, but the high interferencereceived from the air interface confuses the loop test.

6169 STME Neighbour Report includes BCCHDF2.0- –

05Mar9GSM 1800Talk-fam.

When the STME BCCH measurement test including neighbour measurements isstarted from the BSC or the MMI, the first neighbour is always the BCCH being usedfor the test.

6229 Antenna Loop Test on Div-Main Branch Gives Wrong

Results

DF2.0- –

23Jan97PrimeSite

The Antenna Loop Test on 'Div-Main' branch gives in 50% of the cases the results TXPower = 0 dBm and SWR = 0.0. However, the test performed with either the branchselection 'Both Separately' or 'Main TX –Div RX’ always works correctly.

7753 STM: Noise during STM Call if Downlink DTX in UseDF2.0- –

21Oct96Talk-fam.

Downlink DTX is in use. During STM calls, if audio loop is used, some noise is heard.

There will be no corrective actions to this problem.

391051 Telecom: SDCCH Allocation with Satellite AbisDF4.0-1 BSC SW

21 Jun00Talk Fam

Satellite Abis is used with 2 TRX configuration. The timeslot configuration in thesecond (non-BCCH) TRX is TCHF+SDCCH+6 TCHF. Ie. SDCCH allocated totimeslot 2.The calls allocated to TCHF channels in the second TRX fail.

As a workaround solution the SDCCH channel can be moved to the timeslot 1. In that

case all TCHF channels work without problems.

940916 Telecom: BS Power Reported in the Next

Measurement report

DF5.0 DF7.0

05 July 00 After a BS power control message the BS Power reported in the next measurementresult is already the new Power Level even though the RxLev measured by themobile has not yet been affected by the change in BTS power

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Open Problems

B6X 056759 AEIssue 20.0.0


Int. Ref.Date


2068016 BTS O&M Alarm raised erroneously

DF6.0 S10.5

18 Jan 02 Alarm 7706, BTS O&M Link Failure is raised erroneously when DF6.0 SW isactivated. The BTS Service is not affected and the alarm should be cancelledmanually.

2216616 HO Failure Rate Increases with 32 kbit SignallingDF6.0 DF7.0

4 April 02When 32 kbit TRX signalling is implemented on a site the HO Failure rate increasesslightly.

Workaround Solution: switch off Intra cell handovers

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Solved Problems

B6X 056759 AEIssue 20.0.0


3 Solved Problems This chapter lists the problems solved in the release. The meaning of the fields

in the table is explained below.

Int. Ref.This is the number of the problem. It refers to Nokia internal lists and is

provided here to help identify any particular problem. The date when the

problem was observed or a complaint was received about it is also included.

If the description of the problem has been updated or new information has been

added to or removed from the list of open problems, the FMS problem number

is underlined.

Problem Description

This field includes the name of the problem, briefly describes the problem and

the symptoms, and may give instructions on how to avoid or get around the

problemExists in

This field lists the SW, FW, and HW versions in which the problem exists. If a

problem exists only in one version, the number of that version is given.

Solved in

This is the version of the BTS software release in which the problem has been

corrected.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




3.1 Problems Solved in DF6.0-2

DF6.0-2 SW consists of:

BTS SW DF6.0-2

MMI SW DF6.0-2

Table 7. Problems solved in DF6.0-2

Int. Ref.Date


305051 BCF: Alarm 7530 Stops TrafficD1.0- DF6.0-2

24Nov99 Alarm 7530 , TX Output Power Decreased is a non-blocking alarm, so no BCCHreconfiguration is carried out. When the power decreases a lot the calls are difficultto establish.

2299316 7825 13 MHz Source clock Missing from master

clock Alarm Raised

DF6.0 DF6.0-2

14 May 02When DF6.0 is loaded to the BCF in some cases the 7825 alarm may be raised, asa single pulse is enough to raise this alarm. In DF5.1 two missed pulses arerequired to raise the alarm.

The alarm can be cleared and the site returned to working by a BCF reset.

P2609316 Alarms 7524, 7526 after DF6.0 SW activationDF6.0 DF6.0-2

On some sites when RF Hopping is active, alarms 7524 and 7526 may be raisedwhen DF6.0 is activated.

Workaround Solution: switch off RF Hopping.

P2941216 Alarm 7530 BCCH causes restarts of a sectorDF6.0 DF6.0-2

Alarm 7530 was changed from a blocking to non-blocking alarm in DF6.0. Whenpreferred BCCH is in use on a BB Hopping sector and the alarm 7530 is raised the

sector will enter a reset loop. Alarm 7530 will be returned to a blocking alarm andGFR 305051 has been removed.

Workaround Solution: turn off preferred BCCH.

P2941316 Number of Samples to trigger 7949 Calculation is

not standard

DF6.0 DF6.0-2

In Talk Family the number of samples to trigger the RSSI by TRX feature is 1 000000. In Ultrasite it is 750 000. This figure will be standardised at 750 000.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Solved Problems

B6X 056759 AEIssue 20.0.0


Int. Ref.Date


P2661116 RX Uplink Quality Statistics Appear to beIncorrect.

DF6.0 DF6.0-2

The number of mobiles reporting RX quality 2, 3, 4 and 5 is increased.

P2438716 Alarm 7949 May be Raised ErroneouslyDF5.0 DF6.0-2

Alarm 7949 may be raised on a site where the antennas are operating in anacceptable range. When signal levels are very low then the level could be negative(that is appearing to be below -110).This is limited to 47dbm and this gives incorrectaveraging.

P2403316 7706 alarms occur without interventionDF6.0 DF6.0-2

Occasionally, on random sites, the alarm 7706, BTS O&M link Failure is raised. Itdoes not cancel and needs manual intervention to restart the site.

P1728516 7842 No Transmission Activated Raised After

Link Disturbance

DF5.0-1 DF6.0-2

After link disturbances, the alarm "7842, No BCCH transmission activated" may beraised and the BCCH reconfigured.

P3096116 AMR ‘Warble’ and Clicking on HandoverDF6.0 DF6.0-2

Warble and clicking heard during handover of calls when AMR in Use.

2841ES09P AMR Handover failed from Half Rate to FullRate.

DF6.0 DF6.0-2

Inter-cell handovers are done between half-rate and full-rate AMR codecs. After afew successful handovers, mobiles may not be able to hand over from half-rate tofull-rate. Mobiles respond to HANDOVER COMMAND message with HANDOVERFAILURE with cause timer expired. Call continues on half-rate codec.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE






BTS SW DF6.0-1

MMI SW DF6.0-1

Table 8. Problems Solved in DF6.0-1

Int. Ref.Date


577073 Modifying 2+2+2 to make 3+3+3 results in Blank

fields

DF6.0 DF6.0-1

18 Jan 02When adding additional TRXs the TRX settings were blank and TRX Mode nox wasnot present

Workaround solution: save the HWDB, close it and then re-open it. The fields will bepresent and can be edited.

713073 Reset TRX Remains Blocked for Incomplete SectorDF6.0 DF6.0-1

17 April 02When the BSC configuration is larger than the BTS physical configuration the TRXcan remain in WAITING FOR SYS INFO State after a manual TRX reset. A sector reset can bring the TRX in to supervisory state.

2015616 DF6.0 MMIDATA Changes 1 TRX FlexiTalk to 2TRXs by Default

DF6.0 DF6.0-1

13 Dec 01When a 1 TRX FlexiTalk Configuration has been created, the number of TRXsdefaults to two TRXs when the HWDB Configuration Picture is viewed.

2069016 DF6.0 MMIDATA Sometimes Has Incorrect

Information When Adding TRXs

DF6.0 DF6.0-1

18 Jan 02When adding TRXs to existing configurations the TRX mode may be missing andchannel configuration may be incorrect when first saved. Changes can be made tocorrect this by closing the hardware database and reopening it.

2085016 TRXs Can Become BL-RSL When Adding Q1Equipment

DF6.0 DF6.0-1

24 Jan 02When Q1 equipment is added to the BTS, some TRXs sometimes stay in theBL-RSL state.

2138316 MMI Contextual Help Produces Error MessageDF6.0 DF6.0-1

21 Feb 02When pressing the F1 key an error message is produced instead of a help window.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Solved Problems

B6X 056759 AEIssue 20.0.0


Int. Ref.Date


P2679116 DF6.0 MMIDATA Sometimes Has IncorrectInformation When Adding TRXs

DF6.0 DF6.0-1

When adding TRXs to existing RTC configurations the TRX mode may be missingand channel configuration may be incorrect when first saved.

Changes can be made to correct this by closing the hardware database andreopening it

3.3 Problems Solved in DF6.0

DF6.0 SW consists of:

BTS SW DF6.0

MMI SW DF6.0

Table 9. Problems Solved in DF6.0

Int. Ref.Date


80 BCF: STM Loop Test Fails with Intelligent Frequency

Hopping

DF4.0- DF6.0

25Sep98Talk-fam.

An IUO configuration is used. If the regular TRXs and super-reuse TRXs are indifferent hopping modes, the STM Loop Test will fail.

2072 MMIDATA: Incorrect Configuration View on the MMIDF4.0- DF6.0

17Feb00

Talk-fam

There are no TRXs installed on the uppermost rack of the cabinet. When theconfiguration is viewed with the MMI, it may be the case that all PSUs and CCFsare not shown on the MMI display.

The operation of the BTS is not affected.

5647 MMI: Faulty Radio Link Cannot Be Identified with

MMI

DF3.0- DF6.0

18Nov97Talk-fam.

An alarm occurs for one of the external radio links. With the MMI, it is not possibleto identify for which unit the alarm was issued.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




Int. Ref.Date


5569 BCF: Alarm 7220 Active after Reconfiguration

D1.0- DF6.0

18Nov97Talk-fam.

A TRX loop test is started with the MMI. Then, a BCCH reconfiguration is made for the TRX performing the loop test. After the reconfiguration, alarm 7220 ‘Radio loopor RX antenna test execution’ remains active in the BSC and the MMI. However,calls can be made in the tested timeslots.

5599 BCF: Unnecessary Disabling Booster Alarms after

Manual PSU Switch Off/On

DF3.0- DF6.0

18Nov97Talk-fam.

The PSU supplying a sector equipped with a booster TRX is manually switched off.When power is restored, disabling alarms 7975 ‘TRX connection’ and 7976 ‘Booster gain’ remain active and the TRX remains blocked.

When the Intelligent shutdown operation restores the power, this problem does notoccur; alarm filtering and BTS recovery are correct.

6187 BCF: Active Alarm 7996 Is Not Sent to BSC after BBU

Test

D1.0- DF6.0

05Mar97Talk-fam.

Nokia Citytalk with site support system is used. If, after the BBU test, alarm 7996‘Backup battery voltage low’ is active (indicating faulty batteries), it is not sent to theBSC.

6655 BCF: Unnecessary Alarm 7890 ‘Fault in Cooling Fan’D1.0- DF6.0

27Jun95

Talk-fam.

Unnecessary fan alarm 7890 ‘Fault in cooling fan’ is sent to the BSC if the CCF_C

is switched on with the MMI (Manage | EAC Set Output State). The cancel followsimmediately.

9457 BCF: New TRX Boot SW Brought into Use Too EarlyDF4.0- DF6.0

01Nov98Talk-fam.

New BTS SW is background downloaded to the BTS but not activated. If the BTS isreset before activation, the new TRX boot SW will be brought into use.

For recovery, another site reset is required.

9505 BCF: Incorrect AFx SWR Test ReportDF4.0- DF6.0

01Nov98Talk-fam.

The AFx SWR is measured in a sector with at least two AFxs. The Antenna Filteringsupervision is set to on. The test report gives 'Out of range' for the TCH AFxs in

other sectors, although it should give 'Not measured'.

9685 BCF: BTS Lock/Unlock May Block Two Sectors in ICE

Configuration

DF4.0- DF6.0

01Nov98Talk-fam.

An ICE configuration is used. If a disabled alarm occurs for the AFE in either capacity or coverage sector (duplicated as an enabling alarm in the other ICEsector) and BTS lock/unlock is given for the faulty sector, a disabled alarm will beissued for both sectors. This means that both sectors are blocked.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Solved Problems

B6X 056759 AEIssue 20.0.0


Int. Ref.Date


13489 BCF: Unnecessary alarm 7834 FREQUENCYHOPPING PROCESSOR RESET after OMU

Reset

DF4.0- DF6.0

14May99 Occasionally, there is an unnecessary alarm 7834 FREQUENCY HOPPINGPROCESSOR RESET after OMU reset.

For recovery, a site reset is needed.

14071 MMI: STM Tests Cannot Be Carried Out with Remote

MMI from the BSC

DF4.0- DF6.0

07Jun99

Talk-fam.

The following STM tests cannot be carried out with remote MMI from the BSC:

– STM BCCH field strength test – STM originated test call – STM receiver antenna test – STM BCCH synchronisation

20521 MMIDATA: TRX Signalling Speed May Change when

an Old HW DB Is Modified

DF4.0 DF6.0

26Nov99 The Hardware Database (HW DB) is updated. In some cases the HW DB Editor may change the TRX signalling speed.

21313 BCF: Incorrect Unit Type in Radio Link AlarmsD1.0- DF6.0

26Nov99 Alarm 8xxx is issued for RRS type radio link. In some cases the unit type in thealarms sent to the BSC is RRM, although it should be RRS.

389051 MMIDATA:LAPD Rates Default Signalling Speed is

64kbit/s

DF4.0 DF6.0

31 Jun00TalkFam

When new TRXs are added to a HWDB the signalling speed defaults to 64kbit./s for all TRXs instead of using the speed that is already defined. The values can bechanged be back in the TRX settings window.

1017716 BCF: Intermittent Alarm 7874DF5.0 DF6.0

15 Aug 00

Talk Fam

The alarm 7874 is sometimes active for 10s and then cancels on some sites.

1204016 MMIDATA: Unable to Edit Diversity in PrimeSite

Databases

DF5.0 DF6.0

30 Jan 01PrimeSite

When a PrimeSite Database created with DF4.0 or earlier MMIDATA is openedwith DF5.0 or later MMIDATA it is no longer possible edit the Diversity options.

The workaround solution is to create the HWDB in DF5.0 and use that HWDBinstead.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




Int. Ref.Date


1312816 MMIDATA: Configuration Changed when HWDBFile Opened

DF5.0 DF6.0

15 Jan 01Talk-Fam

When opening a file with boosters defined with MMIDATA 5.0.0 or 5.1.0 the TRXaddresses are incorrect. DF4.0 HWDB give the correct TRX addresses.

1333516 BCF: Booster TRX with BTS SW DF5.x-x causes

alarm 7976

DF5.0 DF6.0

24 Jan 01Talk-Fam

When using DF5.0 SW or later with boosters, GPRS and PMAX=0dB or 2dBalarms 7976, Booster Gain Level too low and 7705, LAPD Failure are raised. TheBCF SW should limit the power so if these levels of PMAX are set at the BSC theBCF should reduce the power by 4dB

1377816 BCF: Incorrect Alarm States after 2 Mbit or Power

Fault

DF4.0 DF6.0

14 Feb 01Some 8000 series (Transmission) alarms are still visible at the BSC and NMS evenafter a power or transmission fault has been corrected.

1458816 BCF: Alarm 7949 may be Raised Incorrectly if the

TRP value at the BSC is not set to 0

DF5.1 DF6.0

26 Mar 01 When the priority parameter at the BSC (TRP) is not set to 0 the calls are notallocated evenly across all TRXs in the sector. The decision to trigger the alarm iscalculated using an average of the RX difference values of all calls on the sector.

Where there are a small number of calls on one TRX that have a high value for theRX difference parameter then the alarm 7949, Difference in Rx Levels of Main andDiversity Antennas may be incorrectly raised.

1493916 BCF: RSSI Feature Works on Locked TRXsDF5.0 DF6.0

6 Apr. 00When a TRX is locked after the last site reset then the RSSI calculation will use theTRX as part of its RSSI calculations for that sector.

1508516 BCF: Transmission Alarms reported with Incorrect

Severity

DF5.0 DF6.0

12 Apr 00Some transmission alarms (8000 –8999) are denoted as disturbances when they

should have a different severity as denoted in BSC NED.

1742116 TELECOM: Large Number of T200 Timers expire

on Radio LAPDM During Half Rate Calls

DF5.0 DF6.0

10 Oct 01The T200 timer is incremented each timer a Layer 2 message is not received within the specified time, in the case of half rate 255ms. When DTMF tones were sentduring a half rate call the increments were frequent which produced either bad callquality or dropped calls.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Solved Problems

B6X 056759 AEIssue 20.0.0


Int. Ref.Date


2401051 MMI: SWR Measurement not Reported Accurately

DF4.0 DF6.0

21 Jun 00The SWR measurement reported at the MMI is sometime OUT OF RANGE even if the antenna line is alright.

1113816 HSCSD not Working Correctly when MS Call

Forwarding in Use

DF5.0 DF6.0

27 Nov 00 When an HSCSD data call is taken from an MS which is using call forwarding thecall will often fail with a Connection fail message (Remote Transcoder Alarm)

1677216 MMIDATA: MMIDATA DF5.0-1 Reverses the

Address of the Booster and TRX

DF5.0-1 DF6.0

05 Jul 01 If an existing HWDB is opened in DF5.0-1 MMIDATA then the HW address of theBooster and TRX are reversed. This results in the alarm 7705 LAPD failure.



BTS SW DF5.1-1

MMI SW DF5.0


Int. Ref.Date


57053 BCF: Site Continually Resets when RF Hopping is

used with certain frequencies

DF5.1 DF5.1-1

When RF Hopping is in use, the BCF will continually perform a self reset and willnot reach supervisory state.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE




Int. Ref.Date


1375816 BCF: TRXD temperature Alarm 7522

DF5.1 DF5.1-1

In some TRXs the alarm 7521, TRX Temperature increased is not reported socooling is not started. This causes the number of 7522, TRX Temperature High,alarms to increase. This is as a result of the TRX reporting the alarm to the BCFAbefore the BCFA is ready to action it. This only happens when the BTS is under BCF control if the BTS is under TMS control then the temperature alarm handlingoperates correctly.

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE


Solved Problems

B6X 056759 AEIssue 20.0.0


3.5 Problems Solved in DF5.1

DF5.1 SW consists of:

BTS SW DF5.1

MMI SW DF5.0

Table 11. Problems Solved in DF5.1

Int. Ref.Date


15277 BCF: Talk BTS Set Radiolink Alarm IncorrectlyDF3.0-1 DF5.1

14Jult99

Talk-fam

Remote session attempt (ZQUS:BCF=6,TRU=1:5;) from BSC to non existingfunctional entity (FE) in BTS transmission unit caused additional alarm. Alarm is notcancelled until BCF is locked.

18583 BCF: Unnecessary alarms 7526 TX Frequency Tuner

Out Of Order and 7524 RX Frequency Tuner

Out Of Order with RF Hopping

DF3.0- DF5.1

11Oct99

Talk-fam

12 TRX IUO configuration with RF hopping is used. TRX 12 may unnecessarilygenerate the following alarms 7524 TX FREQUENCY TUNER OUT OF ORDER

and 7526 RX FREQUENCY TUNER OUT OF ORDER.

21355 BCF: Remote Transmission Command from the BSC

May Fail

DF4.0- DF5.1

23Nov99 When BSC SW S8, or later, is used, the transmission command from the BSC mayfail. When this is the case, the following MML report is issued: DX ERROR: 10112Message Time-Out.

1113816 HSCSD Calls and HoppingDF5.0 DF5.1

Talk FamThe BTS sends the ASSIGNMENT COMMAND to the MS which replies with SABM.When the SABM is received by the BTS, the Remote Transcoder Alarm filtering

starts, but it was only active on the primary channel and the secondary channel wassending Conn Fail messages so the call was released before Est Ind was sent tothe BSC.

The workaround solution is to either disable the hopping or set the followingparameter at the BSC:

NUMBER OF IGNORED TRANSCODER FAILURES .(ITCF). 0 to be value 5(ZEOQ:ITCF=5;).

7/27/2019 DF6.0-2 GFR_2000 B6X 056759 AE





BTS SW DF5.0-1

MMI SW DF5.0


Int. Ref.Date


2402051 Telecom: Incorrect Mobile Allocation IE in

Immediate Assignment Extend Message

DF5.0 DF5.0-1

05 Jul 00Talk Fam

When the amount of simultaneus call attempst is higher than the amount of freeSDCCH timeslots in the BTS, the BTS compresses the Immediate Assigmentmessages for two separate mobiles into one Immediate Assigment Extendmessage. In that Immediate Assigment Extend message is Mobile Allocation IEvalue which indicates to the mobile if the given channel is hopping or not. The valuewas always set to zero n this problem that value was always zero so MS did notknow if the channel assigned was hopping or not.

395051 BCF: AFx Temperature Dangerously High, alarm

7937

DF2.0 DF5.0-1

18 Jul00

Talk Fam

The 7937alarm is being raised unnecessarily in some AFx units.

Documents

DF6.0-2 GFR_2000 B6X 056759 AE