Bts

Soc Classification level Flexi EDGE Base Station Troubleshooting / September 20081 © Nokia Siemens Networks

Flexi EDGE BTS Troubleshooting


Objective

After completing this learning element, the participant will be able to:• Perform preventive maintenance tasks

• Perform corrective maintenance

• Identify the problem as part of troubleshooting process

• Recognize and recover the most common alarms in the BTS

• Group alarms and faults into a few main categories

• Use Flexi EDGE BTS Manager for troubleshooting

• Recognize current features and failures of the SW Configuration and compatibility

• Replace faulty modules process

• Perform the troubleshooting process to solve the cases


Table of Content

• Introduction

• Preventive Maintenance

• Corrective Maintenance

• Troubleshooting process

• Problem symptoms for Troubleshooting

• Troubleshooting Problem Situation

• Example Cases

• Appendix


IntroductionSome Definitions

MaintenanceIn Flexi EDGE BTSMaintenance

In Flexi EDGE BTS

Preventive Maintenance

Provide regular maintenance to the Flexi EDGE BTS in order to reduce the possibility of failures or decreasing of performance

Corrective Maintenance

The activity in order to rectify or solve faults happened in the network, which have main purpose is to solve the problem and get the system/unit in the network back into normal

Detecting, tracing and analysis the mistakes of fault in the system networks, in order to find the fault locating or root cause of the faults and also to recommend solution to solve the fault.

TroubleshootingTroubleshooting

So, based on above explanation the corrective maintenance tasks are executed after the troubleshooting has been done.


Preventive MaintenancePerforming Routine Maintenance Tasks

• The purpose of preventive maintenance is to provide regular maintenance to the exchange in order to reduce the possibility of failures.

• Before performing any tasks, determine whether there will be any interruption in service.

• If so, then certain steps need to be taken before the task is executed.

• It should be seen as a need to perform these on a regular basis, which can be different for each type of maintenance

• On the right hand, there is the example of how to perform routine maintenance tasks

Check that the grounding cables are properly connected

Check the fans and air circulation

Check the connector seals (rubber boots)

Check the cable connectors

Check the screws

11

22

33

44

55



Due to flexibility of installation of Flexi EDGE BTS, these following physical check should be done:

• Cleanness of the unit, especially for outdoor installation. Here is example of unit in flexi edge BTS which is dirty

in some circumstances, we need to provide more protective action to avoid Flexi EDGE BTS from unfriendly environment, such as rats as shown above

Mouse attack Mouse protection

Broken seal because of rats



• For cabling and connector installation, please follow the standard installation document from NED as recommended by NSN.

• These following pictures are example of mistakes that might happen in the field that can affect the performance of the system.

No cover on the LMP port TX Cable broken



Very sharp curve of TX CableUnnecessary bending of cable

(blue line is ideal way)

Transmission cable is left open Broken cable


Corrective Maintenance

• Corrective Maintenance is the activity in order to rectify or solve faults happened in the network, which have main purpose is to solve the problem and get the system/unit in the network back into normal.

• Usually, the corrective maintenance tasks are executed after the troubleshooting has been done.

• Replacing the module is the example of how the corrective maintenance is doing.

• Replacing the module could be one of the solution if there’s an alarm related to specific unit and after we do troubleshooting, we find out that specific unit is faulty.

• Here is the example of corrective maintenance related to the HW:– Disconnecting the cables

– Replacing the module Fans

– Disabling and enabling power with Flexi EDGE BTS

– Replacing modules, such as: EXxA, ERxA, ESMA, FIxA, EWxA/B, ECxA


Corrective Maintenance Disconnecting Cables

The steps how to disconnect cables:1. Remove any cable ties.

2. Detach the cable connector seal from the module mechanics.

3. Hold the cable with one hand and pull the seal backwards with your other hand so that the connector is exposed.

4. If you are disconnecting an optical cable or a power cable, push the locking clips all the way down and pull simultaneously.

5. Pull the connector out carefully.

6. If you are disconnecting an optical transceiver, first turn the locking ring into a horizontal position and then pull the optical transceiver out.

Grip the connector seal by the stiffened end of the seal (the end connected to the connector) as shown in the following figure

The optical cable has a locking clip on the top of the connector, and the power cable has locking clips on either side of the connector


Corrective MaintenanceReplacing Module Fans

• The purpose is if a module fan fails or becomes degraded, replace it with a new one.• In stack, wall, pole and Flexi Cabinet for Indoor (FCIA) installation, fans can be replaced

from the back of the module if there is enough space behind the BTS. • When removing fans from the back of FCIA, we need to remove the back panel. • When removing fans from the back, make sure we have a screwdriver that fits the

clearance. • If there is not enough space for replacing the fans from the back, you can also replace the

fans from the front. In this case you need to disable power to the module and pull it out from the casing or cabinet. In Flexi Cabinet for Outdoor (FCOA), fans are replaced from the front.

• Note that when replacing fans, an alarm indicating a broken fan may be seen. But after we have replaced the fan, the alarm is cancelled.


Corrective MaintenanceReplacing Module Fans – for Dual TRX Module (EXxA) and Remote Tune Combiner Module (ECxA)

Note :Before start, shut down the module before replacing fans.Do not touch the rotating fans.


Corrective MaintenanceReplacing Module Fans – for System Module (ESMA), System Extension Module (ESEA) and Power DC/DC Module 24V (FPDA)



Corrective MaintenanceReplacing Module Fans – Optical Converter Module (EOCA)



Corrective MaintenanceDisabling and enabling power with the Flexi EDGE BTS Manager

• We need to disable power from the Power Control dialog when adding modules to or removing modules from an operational BTS.

• The power control from the BTS Manager allows each power output to be controlled independently so that a single module can be added or removed.

• First disable the power to that output, add or remove the module, and then restore power.

Steps:

1. After local BTS Manager connection has been setup, open the Power Control dialog (from BTS Control | Power Control).

2. If BTS is the Outputs Controller, click Change.

3. Click Turn Off to disable power from the modules needed.

4. Perform the maintenance needed, for example,

add and remove modules.

5. To enable power in the modules,

click Turn On for each unit.

6. Click Change to change Outputs Controller to BTS.

7. Click Close.


Corrective MaintenanceReplacing Modules – Introduction

Purpose:

• If a module fails and we have carried out troubleshooting, replace the module with a new one.

• The module needs to be removed also when we are replacing a fan from the back of the module.

• Before start, make sure the configuration-specific instructions available for checking how to re-connect the cables.


Corrective MaintenanceReplacing Modules – Dual TRX (EXxA)

Note, If the Dual TRX Module carries the BCCH TRX or provides power for the Dual Duplexer Module, the whole sector may be disabled. In these cases it is recommended to block the sector.

General Procedure for replacing EXxA:

•Disable power with Flexi EDGE Manager.

•Disconnect cables and loosen the screw

•Pull out the module and also EWxx (if there is) submodule

• Install the new EXxA module and also install Ewxx (if there is) in a new EXxA module

•Connect the cables and fix the screw

•Enable the power and check functionality using Flexi EDGE BTS manager.

Please the slide notes for detail.Note that the Dual TRX Module is HW reset when the bus cables are removed and reconnected.


Note, if the Dual Duplexer Module is connected to the Dual TRX Module which carries the BCCH TRX, the whole sector may be disabled. In this case it is recommended to block the sector.

General Procedure for replacing ERxA:

•Disable power to EXxA connected to ERxA with Flexi EDGE Manager.


•Pull out the module

• Install the new one


•Enable the power and check the functionality using Flexi EDGE BTS manager.

Please the slide notes for detail.

Corrective MaintenanceReplacing Modules – Dual Duplexer (ERxA)


Corrective Maintenance Replacing Modules – System Module (ESMA)

Note, save the site configuration file (SCF) to the PC's hard disk by selecting 'Fetch SCF from BTS' from the Commission menu before replace ESMA module

General Procedure for replacing EXxA:

•Switch off power from the BTS

•Disconnect power main breaker, other cables and loosen the screw

•Pull out the module, and also transmission submodule

• Install the new EXxA module and also install transmission submodule in a new ESMA module


•Switch on the power and do commissioning using Flexi EDGE BTS manager.

Please the slide notes for detail.Note that the Dual TRX Module(s) and Remote Tune Combiner Module(s) are HW reset when the bus cables are removed and reconnected.


Corrective MaintenanceReplacing Modules – Transmission Submodule

General Procedure for replacing Transmission submodule:

•Switch off power from the BTS

•Disconnect cables on transmission submodule and loosen the screw

•Pull out transmission submodule

• Install the transmission submodule


•Switch on the power of BTS and check the functionality using Flexi EDGE BTS manager.


CautionNew transmission sub-modules may be damaged and will not operate correctly if the sub-modules are replaced when the BTS power is switched on. Switch off the Nokia Flexi EDGE BTS before replacing the transmission sub-modules.


Corrective MaintenanceReplacing Modules – Wideband Combiner (Ewxx)

General Procedure for replacing EWxx submodule:

•Disconnect cables on EWxx submodule and loosen the screw

•Pull out EWxx submodule

• Install the EWxx submodule


•Switch on the power of BTS and check the functionality using Flexi EDGE BTS manager.


Note: block the TRXs connected to the EWxx with Nokia Flexi EDGE BTS Manager or, if the module is in a sector where Baseband or Antenna Hopping is used, block the whole sector.


Corrective MaintenanceReplacing Modules – Remote Tine Combiner (ECxA)

General Procedure for replacing Remote Tune Combiner (ECxA):

•Disable power to Remote Tine Combiner Module and its connected EXxA module(s) with Flexi EDGE BTS Manager.


•Pull out the module

• Install the new one


•Enable the power and check the functionality using Flexi EDGE BTS manager.


Note: If the Remote Tune Combiner Module is connected to the Dual TRX Module which carries the BCCH TRX, the whole sector may be disabled. In this case it is recommended to block the sector.

Note that the Remote Tune Combiner Module is HW reset when the bus cables are removed and reconnected.


Troubleshooting Principle Troubleshooting learning model

Personal

comfort

level

T I M E

UNCONSCIOUSLY UNABLE

CONSCIOUSLY UNABLE

CONSCIOUSLY ABLE

UNCONSCIOUSLY ABLE

AWARENESS

PRACTICE

APPLICATION

EXPECTATION AFTER COURSE


Troubleshooting PrincipleTroubleshooting Style

Gambler

Tester

Thinker

Wanderer-random search

Risk Taker-experimental search

Odds maker-guess the fault

Swapper-change all

Sensor-look, listen, touch and smell

Tracer-follow diagram

Splitter- “divide and conquer”

Reader-use documents

Recaller-good memory

Designer-theoretical knowledge

Analyser-think before act


Troubleshooting PrincipleTroubleshooting Questions

When analyzing the problem, you might want to ask yourself the following questions:• When was the problem first reported?

• How did the problem become known?

• From which geographical area was it first reported?

• Are there similar complaints coming from other cells?

• Is the problem spreading in the network or is it happening only in one/few BTSs?

• Which types of calls are affected?

• Does it happen all the time or occasionally?

• …


Troubleshooting PrincipleBrainstormingWhat comes up in your mind when you read the questions?

Collect everything together at the board.

What kind of documents

could help me in

troubleshooting? Which people

could help me in

troubleshooting?

What kind of alarms could help me in

troubleshooting?

Which hard- and software could help me

in troubleshootin

g?


Troubleshooting Process

Find the symptoms of the problem

Assumptions

Analyze and verify the problem

Carry out corrective action

Make sure the problem has been solved

11

22

33

44

55


Troubleshooting ProcessFind the symptoms of the problem

• Symptoms are indication that represent problem might happen in the system.

• Symptoms also can help user to approach and identify the cause of the problem.

• For Flexi EDGE BTS, user can find the symptoms of the problem such as:– Alarms appear in the BSC and/or BTS (using BTS Manager)

– Message appear when executing a task with BTS Manager, e.g: MIV message box

– Reporting result, e.g: commissioning report, test result.

– Experience of the mobile user


Troubleshooting ProcessFind the symptoms of the problem

Error messageLED Indication

Alarm in BTS Manager

Alarm comes to BSC


Troubleshooting ProcessMake assumption

• Based on symptoms, user can make assumption of what happened actually in the equipment, what the probably cause of the problem, and also how to solve it.

• Making assumption is very important, due to:• Can be used for directing what should be done in order to approach

the problem

• Reduce the time of troubleshooting, if the problem has been experienced before.

• Assumption can be more than one.

• There could be that the assumption is not right (false), but after the verification/analysis process, user can prove it.


Troubleshooting ProcessMake assumption – example

• For example, during local connection with Flexi EDGE BTS Manager, comes up this following message:

• So, what is your assumption due to:– Problem might occur later on?

– Cause of the problem?

– How to solve it?


Troubleshooting ProcessAnalyze and verify the problem

• After make assumption, then user can start to analyze and verify what he/she assume. In this process actually need the troubleshooting skill.

• These tools could help user to identify the problem when do troubleshooting:• Software tools:

– Flexi EDGE BTS Manager, includes testing process, monitoring & supervision– Flexi Hub Manager– Latest Flexi EDGE BTS SW Package

• Hardware tools: – Personal Computer– Basic tools: multimeter, wrench– Handset + SIM card for call testing– Spare equipment : units, cables, connector– Advance measurement tool: site master, spectrum analyzer

• References:– Product Documentation– SW Package documentation– Technical Notes– Generic Failure Report


Troubleshooting ProcessAnalyze and verify the problem using BTS Manager

• If a fault occurs during BTS operation, connect Nokia Flexi EDGE BTS Manager laptop PC to the System Module (ESMA).

• These elements could help you identify the problem when do troubleshooting:– Flexi EDGE BTS Manager windows,

– Supervision,

– BTS Events,

– and Alarms


Troubleshooting ProcessAnalyze and verify the problem using BTS Manager

Alarms

BTS Events

Supervision

Flexi Edge BTS Manager Window


Troubleshooting ProcessAnalyze and verify the problem – define the caused

Find the caused problem:

Depending on the problem, one or more following causes may be as type of problem:

Commissioning Electrical power Nokia Flexi EDGE BTS Manager connection Dual TRX Module (EXxA) operation TRX test and TRX loop test failures Illegal modules Local software download from Flexi EDGE BTS Manager (E)GPRS packet switched data transfer Q1 management PseudoWire operation


Troubleshooting ProcessAnalyze and verify the problem – replacing unitIf replacing unit needed, after having replaced the faulty module/unit, send it to hardware service.

These following items should be provided when returning the faulty unit:

Exact failure details, such as the alarm number, environmental information Configuration information (such as dusty, hot SITE, large configuration) Exact alarm description for all modules. Except for the EXxx DTRX modules,

are capable of recording internally to nonvolatile memory the fault condition, including the environmental information and TRX-level configuration information in case a blocking alarm has occurred.


Troubleshooting ProcessAnalyze and verify the problem – failure reportIf a fault still exists after troubleshooting, contact your local Nokia Siemens Networks representative.

Report all damages, failures, or faults to Nokia Siemens Networks using the Failure Report Form (FRF) that your local Nokia Siemens Networks representative has provided.

Note : example of returning faulty unit form is as attached:Failure report

template


Problem symptoms for Troubleshooting BTS alarm in BSC (1/2)

• Nokia Flexi EDGE Base Station alarms issued at the BSC or NetAct have a four-digit alarm number and an alarm name, and an optional fault reason (see the figure below).

• To interrogate BTS alarm in BSC, use MML command: ZEOL

• For other fields in the figure below, refer to BSC/TCSM Product Documentation.

Severity/ urgency level*** requires immediate actions

** requires actions during working hours

* no actions required

MML command under BSC to interrogate the current BTS alarm under BSC number 99

Alarm number

BSC name

Printout type:

BCF numberTRX number

BTS number Event type

COMM communication failure

QUAL quality of service

PROCES processing failure

EQUIPM equipment failure

ENVIR environmental failure

DateTime

Date

ALARM fault situation

CANCEL fault terminated

DISTUR disturbance

NOTICE notice

Consecutive alarm number

A short description of the alarm.Supplementary information


Problem symptoms for Troubleshooting BTS alarm in BSC (2/2)

• Please note that one alarm can have more than one fault reason, although the alarm number remains the same.

• Different faults may have the same effect on the operation of a base station object, which is why they have the same alarm number and name.

• The fault reason specifies the fault and helps in troubleshooting.


Problem symptoms for Troubleshooting BTS alarm in Flexi EDGE BTS Manager

Alarm generation real Time stamp

The current event of alarm

Description of alarmStart – Indicates that an alarm has been started.

Cancel - Indicates that an active alarm has been cancelled

In alarm history option, there will be:Transient – Indicates that a transient (disturbances) alarm has occurred.

Description of alarm By selecting a specific alarm, there will be further explanation in alarms details box


Problem symptoms for Troubleshooting Alarm Classification (1/3)

• In fault situations, Nokia Flexi EDGE Base Station runs an automatic reclassification procedure for major (**) and critical (***) alarms before it sends an alarm to the BSC.

• When an object becomes faulty, only one critical (***) alarm from a BCF/BTS object or only one major (**) alarm from a faulty TRX can be active at a time.

• In reclassification, the alarm handling detects which logical base station object is affected by a module level fault.

• After reclassification, only one object level alarm with only one fault reason is sent to the BSC.

• However, the same alarm can be caused by several different fault reasons.



BCF BTS 1 TRX 1

TRX 2

TRX 3

TRX 4

BTS 1

Fault situation 1:

Alarm Output

7606 TRX FAULTY (TRX 1)

BCF BTS 1 TRX 1

TRX 2

TRX 3

TRX 4

BTS 1

Fault situation 2:

Alarm Output, in this order


7603 BTS FAULTY (BTS 1)

Functioning object

Degraded object

Faulty object

1. TRX 1 becomes faulty and ceases to operate. 7606 TRX FAULTY alarm is issued.


2. TRX 2 becomes faulty and ceases to operate.

3. Now both TRXs are not operating, which causes BTS 1 cease to operate. A BTS alarm, 7603 BTS FAULTY, is issued.



BCF BTS 1 TRX 1

TRX 2

TRX 3

TRX 4

BTS 1

Fault situation 3:

Alarm Output


7604 BTS OPERATION DEGRADED (BTS 1)

BCF BTS 1 TRX 1

TRX 2

TRX 3

TRX 4

BTS 1

Fault situation 4:

Alarm Output, in this order7607 TRX OPERATION DEGRADED (TRX 1) start


7607 TRX OPERATION DEGRADED (TRX 1) cancel

7607 BTS OPERATION DEGRADED (BTS 1)

Functioning object

Degraded object

Faulty object


2. TRX 2 becomes partially faulty but calls are getting through.

3. Now the sector is partially faulty, and a BTS alarm, 7604 BTS OPERATION DEGRADED, is issued.

1. TRX 1 becomes partially faulty but calls are getting through. 7607 TRX DEGRADED alarm is issued.

2. TRX 2 becomes faulty and ceases to operate. 7606 TRX FAULTY alarm is issued for TRX 2. 7607 TRX DEGRADED alarm is cancelled for TRX 1.

3. Now the sector is partially faulty and a BTS alarm, 7604 BTS OPERATION DEGRADED, is issued.


Problem symptoms for Troubleshooting Alarms Tables (1/2)

• The alarm tables show the faults and instructions on how to correct the fault (see an example of an alarm table below):

• Description of fields in the alarm table is shown below:


Problem symptoms for TroubleshootingAlarm Tables (2/2)

Instruction of troubleshooting activity in order to rectify the problem caused by specific fault reason

Fault reasonHow user can cancelling the alarm

Same alarm number can have different fault reason, instruction and how to cancel it


Problem symptoms for TroubleshootingAlarm based on object

Object

Alarm Title & Severity

Faulty

(Critical)

Operation Degraded

(Major)

Notification (Minor)

BCF 7600 7601 7602

BTS 7603 7604 7605

TRX 7606 7607 7608

Site Powering 7612 7613 7614

Other alarms:

• 7208 LOCAL BLOCK

• 7401 – 7424 EXTERNAL ALARM

• 7615 RTS IN TEST USE

• 7616 OSCILLATOR ADJUSTMENT TEMPORARILY INTERRUPTED

• 7621 INTOLERABLE CONDITIONS ON SITE

• 7801 MMI CONNECTED

• 7995 MAINS BREAKDOWN WITH BATTERY BACK-UP\

• 8xxx TRE related alarms

Alarms based on Radio Network Objects & Site Powering


Problem symptoms for TroubleshootingIdentifying faulty modules

• In the Alarms window of Nokia Flexi EDGE BTS Manager, you can see the object that the alarm refers to in the Object column.

• When troubleshooting the alarm at the site, follow the troubleshooting instructions in Nokia Flexi EDGE BTS Trouble Management.

• It is not always the alarming module that is faulty, it may also be the connected cable or the interworking module that causes the alarm.

• At the site, you can easily locate the alarming module by checking the colour of the LED.

• Depending on the unit, a fault can be indicated by a red LED, a blinking red LED or, in some cases, a blinking yellow LED.

• If the module does not have a LED (for example the Wideband Combiner sub-module EWxx) or the module is not responding and no LED colour is displayed, read carefully the alarm description to locate the module causing the alarm.

• For identifying a faulty transmission sub-module connected to the Q1 bus and its alarms, follow the troubleshooting instructions in the sub-module product documentation.


Problem symptoms for TroubleshootingLED in Units - System Module (ESMA)

States

BTS OM not runnin

g

Platform

Startup

Auto Detect CommsWait for

LAPD

BCF_SW Loading

BCF Configuring

BCF Supervisory

Background SW Loading

BCF ResetOMUSI

G onOMUSIG off

OMUSIG on

OMUSIG off

OMUSIG on

OMUSIG off

OMUSIG on

OMUSIG off

BCF Highlight SR BY CC CC CC CC CC CC CC CC CC CC CC SR

Alarm BCF Critical

SR BY SR SR SR SR SR SR SR SR SR SR SR SR

Alarm BCF Major

SR BYBR BR BR BR BR BR BR BR BR BR BR SR

Alarm TRS Critical

SR BY SY SY SY SY SY SY SY

Same Priority as BCF Alarms

SR

Alarm TRS Major SR BY SY SY SY SY SY SY SY SR

Local_Mode SR BY BY BY N/A N/A N/A BY BY SG N/A N/A BG SR

BCF OBJ Lock SR BY SY SY SY SY SY SY SY SY N/A SY SY SR

BCF OBJ Block SR BY N/A N/A N/A N/A N/A N/A N/A SY SY SY SY SR

Normal SR BY BY BY BY BG SY SY SY SG SG BG SG SR

Colour Explanation

SR = Stable Red

BTS_OM SW is not running

BCF/TRS critical alarm (except during platform startup), or

BCF reset

BR = Blinking Red

BCF/TRX major alarm (except during platform startup or BCF reset)

SY = Stable Yellow

BCF is locked (except during platform startup or BCF reset)

Normal mode: BCF SW is loading (OMU signal off); BCF is configuring (OMU signal off)

Blocked BCF: BCF is in supervisory mode or background SW loading

BY = Blinking Yellow

Platform startup

Normal mode: auto detection in progress; BCF is commissioning or waiting for LDAP; BCF is configuring (OMU signal on)

Local module: auto detection in progress; BCF is commissioning or configuring

SG = Stable Green

Normal mode: BCF is in supervisory mode; BCF background SW is loading (OMU signal off)

Local mode: BCF is in supervisory mode

BG = Blinking Green

Normal mode: BCF SW is loading or background SW is loading (OMU signal on)

Local mode: BCF background SW is loading

CC = Cycling colour

BCF Highlight

N/A Not Applicable


Troubleshooting Problem Situations

Problem situation that needs troubleshooting effort can be divided into following:

• Commissioning

• Electrical power

• Flexi EDGE BTS Manager connection

• Dual TRX Module (EXxA) operation

• TRX test and TRX loop test failures

• Illegal modules

• Local software download from Flexi EDGE BTS Manager

• (E)GPRS packet switched data Transfer

• Q1 management

• PseudoWire operation

Troubleshooting problem situation

Each of them has Potential Cause and Corrective Action tables that explained in Trouble Management of Nokia Flexi EDGE BTS document in NED


Flexi EDGE BTS Trouble ManagementExample cases


List of cases

Case 1:

MIV Message

Case 2:Commissioning partial failed due to test reporting failed

Case 3:Alarm 7606 when power reset given to split DTRX module

Case 4:Rx Diversity is not tested when apply to TRX testing

Case 5:TRX test failed in BSC

Case 6:EDAP is missing from the Abis Allocation view after modifying the TCH allocation

Case 7:External alarm input 24 doesn’t appear using FSEB


List of cases

Case 7:External alarm input 24 doesn’t appear using FSEBCase 8:Alarm 8179 FAR END Alarm is raised in the BSCCase 9:TRX Faulty alarm : EXxx TRX module has lost connection to ERxx DDU moduleCase 10:TRX Testing failed after RecomissioningCase 11:TRX test is failedCase 12:Alarm 7607 - Frequency band mismatch between commissioning fileCase 13:RSSI detected Rx signal difference exceeding thresholdCase 14:RSSI measurement results are lost when the alarm is cancelled


Case 1:MIV Message

Detail of the case• When user access the Flexi EDGE BTS locally,

comes the Management Interface Mismatch message.

• But after click on yes button, user can use as usual

• Advise needed according to:– What is the root cause ?

– What are the possible impact if user still go on?

– How to fix this problem

Product / SW Release

Nokia Flexi EDGE BTS / EP1.1 CD1.0

Impact • -


Case 2:Commissioning partial failed due to test reporting failed

Detail of the case• At the end of commissioning step, there comes up message as follow:

Commissioning has partially failed due to following:

One or more commissioning test failed.

See commissioning report for details

• There’s also red dot on TRX test in commissioning progress step

Product / SW ReleaseFlexi EDGE BTS EP1.1 CD.1.0

Impact • Flexi EDGE BTS cannot be used because of not

commissioned properly


Case 3:Alarm 7606 when power reset given to split DTRX module

Detail of the case• Operator configures the Flexi EDGE BTS with 3 +3

configurations this following specification:

– three DTRXs are provided,

– one DTRX is splitted to serve two sectors and both TRX are BCCH-TRX.

• When the power on DTRXs where both BCCH-TRX are there turn off using PDU control, then the BCCH on both sectors are reconfigured to other TRX objects as expected.

• However, when the power to the DTRX module is switched back on, alarm 7606 TRX Faulty 'ERxx DDU module has detected no Tx power at TxB input' is activated.

• Even though the traffic still can be there

Product / SW ReleaseFlexi EDGE BTS / EP1

Impact

• No impact to traffic


Case 4:Rx Diversity is not tested when apply to TRX testing

Detail of the case

• TRX testing is result is PASS, but no Rx diversity testing is performed (NOT_TESTED).

• Commissioning report and cabling have been checked, and they are ok.

Product / SW ReleaseFlexi EDGE BTS / EP1.1 CD1.0

Impact • No impact to traffic, but the Rx Diversity testing result


Case 5:TRX test failed in BSC

Detail of the case• When the TRX Test is run from BSC (remotely), it fails.

• 7735 – TRX TEST FAILED alarms also in the BSC.

• When user does TRX testing locally using BTS manager, the result is okay.

Product / SW ReleaseFlexi EDGE BTS / EP1.0

Impact • No impact to traffic, but misleading troubleshooting could

happen due to 7735 TRX test failed alarms.


Case 6:EDAP is missing from the Abis Allocation view after modifying the TCH allocation

Detail of the case• Operator modified TCH allocation in the transmission link that has EDAP

and sent to the BTS from the BTS manager.

• Once the allocations are retrieved from the BTS with the BTS manager it has been observed that the EDAP is missing from the Abis Allocation view.

• Alarm 7730 -“Configuration of BCF failed”, with supplementary information detail 15844d: “EGPRS_BTS_TRXS_NOT_IN_DAP_EC GPRS enabled TRX is not attached to Dynamic Abis Pool, when GPRS is enabled in the BTS”


Impact • The affected Sector will remain in BL-SYS state until the

problem is resolved.


Case 7:External alarm input 24 doesn’t appear using FSEB

Detail of the case• In order to have 13 up to 24 external alarm inputs, operator must

provide FSEB unit to be connected to ESMA in Flexi EDG BTS.

• To check the functionality of FSEB unit, user must create external input alarm in the BSC for external alarm 13 up to 24.

• During the external alarm testing, operator finds that even though FSEB has been installed, but they cannot see the alarm for 24 that they have created.

• Cable connection has been checked, and didn’t find any problems, and also there’s no alarms related to the FSEB

Product / SW Release

BSCi / S10.5 ED

Impact • Operator cannot use the external alarm 13 -24

Problem Type

BSCi / S10.5 ED


Case 8:Alarm 8179 FAR END Alarm is raised in the BSC

Detail of the case• 8179 FAR-END ALARM is raised in the BSC

• All LapD links are failed

• BCCH is missing


Impact • Since LapD links failed, no calls can be provided


Case 9:TRX Faulty alarm : EXxx TRX module has lost connection to Erxx DDU module

Detail of the case• Two kind of alarms come in the Flexi BTS manager:

– TRX Faulty alarm : EXxx TRX module has lost connection to Erxx DDU module for TRX 2 & TRX 3 (ERxA1)

– BTS Faulty alarm : EXxx TRX module has lost connection to Erxx DDU modules Sector 1 (ERxA1)

• What is the cause of these alarms?


Impact • No traffic can be handle by TRX2 & TRX3.


Case 10:TRX Testing failed after Recomissioning

Detail of the case• After recommissioning a Flexi EDGE BTS, operator find that the result of

this APPEND commissioning is successful, but without testing is performed.

• In order to complete the reporting, TRX testing is performed. In here operator found that TRX testing for TRX-1 is failed due to RF RX cable No connection.

• No alarms accordingly appear in alarm window.

• Physical checking on the RF cabling has been done, but no found problem there.

• Snapshot of APPEND commissioning and TRX testing result are attached

Product / SW ReleaseFlexi EDG BTS / EP 1.1

Impact • TRX test is failed


Case 11:TRX test is failed

Detail of the case

• When the TRX test is performed for TRX-1, the result of the test is failed.

• There are also alarm TRX Faulty: Erxx DDU module has detected no Tx power at TAxA input for TRX-1 & TRX-3

Product / SW ReleaseFlexi EDGE BTS EP1.1 CD.1.0

Impact • TRX test is failed


Case 12:Alarm 7607 - Frequency band mismatch between commissioning file

Detail of the case• Alarm 7607 TRX Operation Degraded - Frequency

band mismatch between commissioning file and detected hardware raise.

• This alarm rises when operator use this following configuration:

– 3+3+8 configuration with ESEA

– High gain MHA types in use for all DTRX

– DTRX-1 up to 6 are EXDA (1800 MHz)

– DTRX-7 up to 14 are EXGA (900 MHz)


Impact • -


Case 13:RSSI detected Rx signal difference exceeding threshold

Detail of the case• Alarm 7604 BTS Operation degraded and 7607 TRX Operation

Degraded – RSSI detected Rx signal difference exceeding threshold are appeared in the BSC.

Product / SW ReleaseFlexi EDGE BTS/ EP 1.1

Impact • TRX Operation Degraded


Case 14:RSSI measurement results are lost when the alarm is cancelled

Detail of the case

• After maintaining the Antenna problem the caused Alarm 7607 TRX Operation Degraded, “RSSI detected Rx signal difference exceeding threshold”, the alarm is automatically cancelled.

• The problem is, once it’s cleared, the alarm details are cleared from the RSSI Comparison Values and Site Information report.

• How can user get the historical reason alarm later on.


Impact • If the RSSI alarm is cancelled before the RSSI results are

read, it is difficult to find the reason for the alarm later on.


Flexi EDGE BTS TroubleshootingAppendix:• LED in Units

• Troubleshooting Problem Situation

• How to find the reference of Flexi EDGE BTS in NOLS


LED in Units


Troubleshooting Problem Situation


How to find the reference of Flexi EDGE BTS in NOLS

Bts

Documents

Transcript of Bts