Sie sind auf Seite 1von 105

Maintenance

Base Transceiver Station Equipment

MMN:BTSE BS-288
A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Important Notice on Product Safety


DANGER - RISK OF ELECTRICAL SHOCK OR DEATH - FOLLOW ALL INSTALLATION INSTRUCTIONS.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected to the system must
comply with the applicable safety standards.
Hazardous voltages are present at the AC power supply lines in this electrical equipment. Some components may
also have high operating temperatures.
Failure to observe and follow all installation and safety instructions can result in serious personal injury
or property damage.
Therefore, only trained and qualified personnel may install and maintain the system.

The same text in German:


Wichtiger Hinweis zur Produktsicherheit
LEBENSGEFAHR - BEACHTEN SIE ALLE INSTALLATIONSHINWEISE.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Alle an das System angeschlossenen
Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.
In diesen Anlagen stehen die Netzversorgungsleitungen unter gefhrlicher Spannung. Einige Komponenten
knnen auch eine hohe Betriebstemperatur aufweisen.
Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Krperverletzungen oder
Sachschden fhren.
Deshalb darf nur geschultes und qualifiziertes Personal das System installieren und warten.

Caution:
This equipment has been tested and found to comply with EN 301489. Its class of conformity is defined in table
A30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for a
Class A digital device, pursuant to part 15 of the FCC Rules.
These limits are designed to provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment.
This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the relevant standards referenced in the manual Guide to Documentation, may cause harmful interference to radio communications.
For system installations it is strictly required to choose all installation sites according to national and local requirements concerning construction rules and static load capacities of buildings and roofs.
For all sites, in particular in residential areas it is mandatory to observe all respectively applicable electromagnetic
field / force (EMF) limits. Otherwise harmful personal interference is possible.

Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their own purposes
could violate the rights of their owners.

Copyright (C) Siemens AG 2006


Issued by the Communications Group
Hofmannstrae 51
D-81359 Mnchen
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

Id:0900d8058008d529

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Table of Contents
This document has 105 pages.
Reason for Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1
1.1
1.2
1.3
1.4
1.5
1.5.1
1.5.2
1.5.3
1.5.4
1.6
1.6.1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Structure of the Maintenance Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Symbols Used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Fault Clearance Principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Fault Clearance Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Module Replacement Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
ESD Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Avoiding the Loss of Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Removing and Inserting Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Quick Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Preparatory Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Remove/Mount Top Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2
2.1

Task List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Filter Mat Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12
3.13
3.14
3.15
3.16
3.17
3.18
3.19
3.20
3.21

Fault Clearance Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ABISCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cable Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COBA2P8 COBA4P12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ECU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Filter Mat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FlexCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OVPT/ABISCON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCM Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Inventory Data Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Inventory Data Restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Inventory Data Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4
4.1

Tables, Lists and Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89


Hardware Architecture and Components (Modules, Frames and Racks etc.)
89
Front View of the BS-288 Rack and Mounting Positions . . . . . . . . . . . . . . 90

4.2

A50016-G5100-A185-01-7620

Id:0900d8058008d529

22
23
26
27
31
32
35
41
47
52
53
57
58
59
60
67
68
69
73
74
78
84

MMN:BTSE BS-288

5
5.1
5.2
5.3
5.3.1
5.3.2
5.3.2.1
5.3.2.2
5.3.2.3
5.3.2.4
5.3.2.5
5.3.3
5.3.3.1
5.3.3.2
5.3.3.3
5.3.3.4
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
5.4
5.4.1
5.4.2
5.5
5.5.1
5.5.2
5.5.2.1
5.5.2.2
5.5.3
5.6
5.6.1
5.6.2
5.6.2.1
5.6.2.2
5.6.2.3
5.6.2.4
5.6.2.5
5.6.2.6
5.6.2.7

Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
HW/SW Compatibility during Download from LMT/BSC . . . . . . . . . . . . . . . 92
State/Status Attributes of BTSE Managed Objects . . . . . . . . . . . . . . . . . . . 94
BTSE Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Equipment Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Processing Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Communication Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Quality of Service Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Environmental Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Severity Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Critical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Major . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Minor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Trend Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Immediate Defence Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Threshold Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Proposed Repair Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Fault Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Fault Messages at the Radio Commander. . . . . . . . . . . . . . . . . . . . . . . . . . 98
Fault Messages at the LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
BTSE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
BTSE Components Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Numbering of BTSE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
General Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Specific Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Remote Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Diagnostics / Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Requirements for Starting the BTSE Module Test . . . . . . . . . . . . . . . . . . . 101
Lock BTS Site Manager (only relevant for some modules) . . . . . . . . . . . . 101
Change BTSE from Phase 3 to Phase 2 (only relevant for some modules) . .
101
Lock Suspected Module (all modules) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Run the Test for the Replaced Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Unlock Suspected Module (all modules) . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Change BTSE from Phase 2 to Phase 3 (only relevant for some modules) . .
104
Unlock BTS Site Manager (only relevant for some modules) . . . . . . . . . . 105

Id:0900d8058008d529

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

List of Figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
Figure 12
Figure 13
Figure 14
Figure 15
Figure 16
Figure 17
Figure 18

A50016-G5100-A185-01-7620

Used Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Fault Clearance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
ESD Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Removing and Inserting Modules: Lever Fastening. . . . . . . . . . . . . . . . 15
Removing and Inserting Modules: Torx Screw Fastening . . . . . . . . . . . 16
Removing and Inserting Modules: Location of the Code Keys . . . . . . . 17
Flow Chart COBA Replacement (Same Module Type) (Part I) . . . . . . 36
Flow Chart COBA Replacement (Same Module Type) (Part II) . . . . . 37
Flow Chart "COBA2P8 with COBA4P12 Replacement" (Part I) . . . . . . 42
Flow Chart for COBA2P8 with COBA4P12 Replacement Procedure (Part
II) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Levers on the Fan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Flow Chart Remote Inventory Data Creation. . . . . . . . . . . . . . . . . . . . 74
Flow Chart Remote Inventory Data Restoration, Part I . . . . . . . . . . . . 79
Flow Chart Remote Inventory Data Restoration, Part II . . . . . . . . . . . 80
Flow Chart Remote Inventory Data Update. . . . . . . . . . . . . . . . . . . . . 85
BS-288 with BCOM 12:6 (front view) . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
BS-288 with BCOM 6:6 (front view) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Fault Messages at the Radio Commander . . . . . . . . . . . . . . . . . . . . . . 98

Id:0900d8058008d529

MMN:BTSE BS-288

List of Tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6
Table 7
Table 8
Table 9
Table 10

Structure of the Maintenance Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9


LEDs on COBA, Fault Clearance Procedure Abis . . . . . . . . . . . . . . . . 23
Comments for Flow Chart COBA Replacement (Same Module Type). 37
Comments for Flow Chart COBA2P8 with COBA4P12 Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Managed Objects for FlexCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Comments on Flow Chart Remote Inventory Data Creation . . . . . . . . 75
Comments on Flow Chart Remote Inventory Data Restoration . . . . . . 80
Comments on Flow Chart Remote Inventory Data Update . . . . . . . . . 86
State/Status Attributes of BTSE MOs . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
List of nob_RIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Id:0900d8058008d529

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Reason for Update

Reason for Update


Issue History
Issue
01

Date
09/2006

Summary
New release BR9.0

Issue 1 for Release BR9.0 (2006/15/12)

A50016-G5100-A185-01-7620

Id:0900d805800a9279

Reason for Update

MMN:BTSE BS-288

Id:0900d805800a9279

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Introduction

1 Introduction
1.1

Structure of the Maintenance Manual


The following diagram provides an overview of the structure of this manual and the
purpose of its chapters.
Chapter 1

Introduction

Chapter 2

Tasklist

Chapter 3

Chapter 4

Chapter 5

(Chapter 6)

1.2

Reference chapter

Overview of the HW architecture as


additional information

Appendix

Main part for fault clearance tasks

Fault clearance procedures for


modules, interfaces and Managed
Objects in alphabetical order

Tables, Lists and Figures

General maintenance

Information on routine tasks that need


to be carried out

Fault Clearance Procedures for Modules


and Interfaces

Table 1

Basic information on this manual


Basic information on fault clearance
Guidelines
General replacement instructions
Preparatory work if relevant

Important information to
make your work efficient and safe

Reference chapter

Basic required knowledge in more


detail, e.g. fault messages

(Index)

Reference chapter

Structure of the Maintenance Manual

Symbols Used
The following symbols are used throughout this manual (PDF version):

A50016-G5100-A185-01-7620

Id:0900d80580075a21

Introduction

MMN:BTSE BS-288

Safety note; the notes given here are to be followed with care. Nonobservance can lead to personal injury and property damage.

ESD (Electrostatic Sensitive Device) precautions to be taken

Reference to another procedure/procedure step

Reference to another procedure; return after having finished

PDF:

HTML:

Note; important information

Use the LMT to enter commands

Figure 1

1.3

Used Symbols

Fault Clearance Principle


The high system functionality of the Siemens Base Station System is achieved by
means of system-integrated routine tests. These routine tests continually check the
correct functioning of the base station subsystems including the BTSEs.
The fault clearance procedures in this manual are based on these routine tests. In most
cases, the results of these routine tests are sufficient to localize the fault and clear it
immediately at the BTSE.
The modular design of the BTSE allows you to clear a large percentage of faults in the
system by replacing a defective module.
Sometimes, however, it may happen that faults do not result from defective modules,
but from interface problems in general (for example interrupted cables). In this case,
special trouble shooting procedures for interfaces are provided.
This maintenance concept guarantees a simple and fast fault clearance and leads to
high operational efficiency.

10

Id:0900d80580075a21

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

1.4

Introduction

Fault Clearance Guidelines


The following diagram gives an overview of the fault clearance procedure (detailed
description below):
1.

2.
Fault and test
management at
the OMC via
Radio Commander

Fault at system
integrated routine test

Fault message displayed


at Radio Commander

3.
Local fault
clearance at BTSE
necessary?

no

yes
4.

Local fault
clearance at
the BTSE

7.

Fault clearance
procedure for suspected
module

Content of this manual


Reinsert replaced
module

yes
5.

6.

Fault
clearance
successful?

no

Another
probable
cause?

8.
no

Call TAC

yes

9.

Figure 2

End of fault
clearance procedure

Fault Clearance Overview

Fault Clearance Guidelines


(The numbering refers to the diagram displayed in Figure 2, Fault Clearance Overview.)
1. The system integrated routine test detects a fault.
2. A fault message is displayed at the Radio Commander.
3. The fault and test management at the OMC must verify whether a local fault clearance at the BTSE is required (see Radio Commander documentation).

g For the local fault clearance at the BTSE:

A50016-G5100-A185-01-7620

Id:0900d80580075a21

11

Introduction

MMN:BTSE BS-288

Make sure that all spare parts that might be required to clear the fault are available at the site. Note that sometimes more than one module may be suspected
of being defective. This is particularly important if the failure is located in the
TX/RX path (see fault clearance procedure "Cable Problems).
For general module replacement instructions also see section "Module Replacement Instructions".
4. Interpret the fault message and go to the fault clearance procedure of the suspected
module or interface in Chapter 3 "Fault Clearance Procedures" (module/interface
names as well as LMT terms (MOs) are listed in alphabetical order if they appear in
the fault message).
Localize the fault and clear it according to the corresponding procedure.
5. As described in the corresponding procedure, verify whether the fault clearance was
successful:
Was the outcome of the hardware test pass?
Are there any relevant active alarms?
Do the LEDs signal normal operation?
6. If the fault should still exist and the replaced module was not the cause of the fault,
check whether there is another probable cause.
7. If there is another probable cause, reinsert the recently replaced original module and
go to the corresponding fault clearance procedure for the next suspected module or
interface.
8. It should be possible to clear most faults that may occur in the BTSE by following the
fault clearance procedures described in this manual. However, if the fault should still
exist after considering all probable causes, contact TAC. Here you will obtain help
from specially trained troubleshooting experts.
9. End of fault clearance. Pack and tag all faulty modules for transport to a repair depot.
Write a fault report in which the following information is given in detail:
Name and code of the site
BSS area, cabinet and slot number
Name, code and serial number of the module
Description of the system response
Description of the fault
Name and phone number of the originator

1.5
1.5.1

Module Replacement Instructions


ESD Precautions

Figure 3

ESD Symbol

Many system modules are equipped with electrostatically sensitive components


(marked by an ESD symbol). Therefore, ESD precautions must be taken when removing
and inserting modules.

12

Id:0900d80580075a21

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Introduction

During module replacement, personnel must wear a conductive wrist strap to discharge
electrostatic charging. Before touching modules, lines or components, make sure to
connect this wrist strap to the ground potential of the rack by means of a flexible lead
integrating a 1 MOhm resistor. Note that the conducting parts of the split pin or the clamp
should not be touched when inserting/connecting (so as to avoid bypassing the 1 MOhm
resistor).

1.5.2

Avoiding the Loss of Calls


g The following procedure is only relevant if the BTSE is in phase 3. In phase 1 or 2,
the BTSE cannot establish calls.
If you lock or replace modules in the TX/RX path of the BTSE, calls may be lost. To avoid
the loss of calls, perform the following procedure before you lock or replace a module in
the TX/RX path.
1. Find out the corresponding TRX:
To find out which TRX is related to the module, perform the following LMT
command:
BSS
BE Btse* Br<no>:<NE id>
BSS-EQUIPMENT
BTSE*
BTSE*<no>
RACK
RACK<no>
<Module>
<Module><no>
GET <Module>
NAME=RACK:<no>/<Module>:<no>
The corresponding TRX is listed as related functional object (relatedFuncObject).
2. Check the state of the corresponding TRX (only possible in phase 3):
To check the state of the corresponding TRX, perform the following LMT command:
BSS
BE Btse* Br<no>:<NE id>
BSS-FUNCTIONAL
BTSM
BTSM<no>
BTS
TRX
TRX<no>
GET <TRX>
NAME=BTS:<no>/TRX:<no>
The states of the TRX are listed in the Object Details.
3. If the states of the TRX are either administrativeState = Unlocked / operationalState
= Disabled or administrativeState = Locked / operationalState = Enabled, the
module is not used for calls anymore. You can start with your maintenance task.
4. If the administrativeState = Shutting Down, the shutdown is in progress. Wait a few
minutes and check the state of the TRX again. As soon as the TRX is locked, you
can start with your maintenance task.

A50016-G5100-A185-01-7620

Id:0900d80580075a21

13

Introduction

MMN:BTSE BS-288

5. If the TRX is unlocked/enabled, call the OMC to have the TRX shut down. Wait a
few minutes and check the state of the TRX again. As soon as the TRX is locked,
you can start with your maintenance task.
For a description of the state/status attributes, refer to section State/Status Attributes
of BTSE Managed Objects in the Appendix.

1.5.3

Removing and Inserting Modules


There are two variants for fastening modules in the subracks.
Some modules,for example the COBA, are equipped with a lever mechanism at their
front panel. For removing or inserting these modules, they can be fastened/unfastened
by swivelling the levers at the top and bottom edges of the module.

14

Id:0900d80580075a21

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Introduction

Lever in closed position

Press the clip to open


the lever

Lever in open position

Figure 4

Removing and Inserting Modules: Lever Fastening

Other modules, for example the CU, are fastened with Torx-headed knurled screws.
Replacement of these modules requires special tools.

A50016-G5100-A185-01-7620

Id:0900d80580075a21

15

Introduction

MMN:BTSE BS-288

Figure 5

Removing and Inserting Modules: Torx Screw Fastening

The TMA must be replaced together with its housing (to be mounted on/unmounted from
the mast).
Semi-rigid/flexi cables, for example on CU, DUAMCO, FDUAMCO, must be fastened/unfastened with a torque spanner (2 sizes).

g It must be ensured that all cables are fastened correctly. Make sure that the connectors are aligned straight on the screw threads. Then tighten the cable connector
coupling nuts manually. The position and alignment is correct if the coupling nuts
can be turned easily.
Finally, fasten the cables by tightening their coupling nuts with a torque wrench.

g It must be ensured that the modules are only replaced by modules with the same or
a compatible HW and SW functional status!
Modules with switches or jumpers must be compared with the removed module for
safety reasons.
The modules should be removed and inserted as fast as possible, in order to prevent
reading in false module addresses from the CAN bus.
Handling Modules with Code Keys
To prevent the installation of the modules at incorrect mounting positions, code keys are
used on all relevant plug-in modules.

16

Id:0900d80580075a21

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Introduction

2
Figure 6

Code key number

Removing and Inserting Modules: Location of the Code Keys

In order to avoid module and backplane connector damage when modules are removed
from/inserted into a base station frame, please observe the following:
In general, after having removed a module from a base station frame, please make sure
that the code keys of the module (at the rear connector terminals) are mechanically
intact, and that a code key plug has not been torn out from its socket and is now jammed
in the backplane.
When replacing a module, please make sure
That the code keys of the new module have the same setting as those of the old one
(see Figure 6, Removing and Inserting Modules: Location of the Code Keys),
That all code keys (also those of the old module) are mechanically intact, and
That a code key plug has not been torn out from its socket and is now jammed in the
backplane.
When inserting a module, do not use excessive pressure.

1.5.4

Quick Module Replacement


In general, there are two replacement procedures:
The standard replacement procedure

A50016-G5100-A185-01-7620

Id:0900d80580075a21

17

Introduction

MMN:BTSE BS-288

The facilitated, quick replacement procedure (only applicable for some particular
modules).

For the standard replacement procedure, an LMT is required. The modules are locked
and, after their replacement, tested and unlocked via an LMT.
For the quick replacement procedure, an LMT is not required. The module can be
replaced directly and is put into service automatically after a successful replacement
(Autorecovery). Precondition for the quick replacement procedure: the attribute
Autorecovery (EAUTOREC) is enabled.
To check whether this attribute is enabled, perform the LMT command:
BSS
BE Btse* Br<no>:<NE id>
BSS-EQUIPMENT
BTSE*
BTSE*<no>
GET BTSE* NOSWL
In the Object Details you will find the attribute and the value for EAUTOREC.
You can set this attribute via the command SET BTSE* EAUTOREC:<enabled>.

g Special behaviour of modules that are connected by the CAN bus:


If Autorecovery is enabled and such a module is mistakenly locked before it is
exchanged, then this module will recover automatically after it is unlocked.
This has no further consequences for the system, but is an unspecified behaviour.

g Quick replacement procedure and semi-rigid/flexi cabling


Modules with semi-rigid/flexi cabling require special handling.
It is important that all semi-rigid/flexi cables are connected before the module is fully
inserted. Otherwise, the module is not put into service. The reason for this is that the
automatic recovery process starts as soon as the module comes into contact with the
backplane connectors. Semi-rigid/flexi cables that are not connected during this process
cause errors which will prevent the autorecovery of the module.
In order to be able to connect the semi-rigid/flexi cables, insert the prepared module
as far as necessary. It is recommended to leave about 2 cm (.75) distance between
module and backplane connectors.
Connect all semi-rigid/flexi cables.
Fully insert the module.

1.6
1.6.1

Preparatory Work
Remove/Mount Top Cover
The top cover is attached to the housing with four fitting holes that connect to four
clamping bolts at the upper corners of the BTSE housing.
Remove Top Cover
1. Open the door.
2. Detach the cover by pulling it towards the front.

18

Id:0900d80580075a21

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Introduction

3. Lift up the top cover from the BTSE housing.

4 fitting
holes

4 clamping
bolts

A50016-G5100-A185-01-7620

Id:0900d80580075a21

19

Introduction

MMN:BTSE BS-288

Mount Top Cover


1. Open the door.
2. Lift the top cover onto the BTSE housing. Make sure that the clamping bolts connect
to the fitting holes.
3. Attach the cover by moving it backwards.
4. Close the door.

20

Id:0900d80580075a21

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Task List

2 Task List
2.1

Filter Mat Tasks


The filter mat must be replaced annually. In a very dirty environment, the mat must be
replaced semi-annually. See corresponding procedure for details.

A50016-G5100-A185-01-7620

Id:0900d8058005ca93

21

Fault Clearance Procedures

MMN:BTSE BS-288

3 Fault Clearance Procedures

22

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

3.1

Abis
In some cases, Abis alarms originate from loose or damaged PCM cables on the BTSE
Abis interface (OVPT/ABISCON) or in the corresponding distribution frame in BSC
direction (NTPM). Therefore, the relevant cables must be checked first, according to the
following procedure.
Typical Abis alarms that concern cable problems are indicated by the alarm message
BPORT Loss of signal.
BPORT is the logical object that is related to the Abis interface (OVPT/ABISCON). The
Abis lines are also referred to as PCM lines.

Open the BTSE Door

Check the LEDs on the COBA


Abis/PCM problems are indicated by the red LEDs Abis on the COBA.
LED Name,
e.g.

Abis1 (on
COBA)

BPORT 0

Abis2 (on
COBA)

BPORT 1

Table 2

Meaning if
LED is
Flashing
Minor alarm

(...)

(...)

Corresponding
Managed
Object

Meaning if
LED is on
Permanently

Meaning if
LED is off

No ABIS/PCM
Major alarm:
no signal, loss problem
of synchronization (of the
PCM framing)

LEDs on COBA, Fault Clearance Procedure Abis

Optional: Check for Active Alarms


If an LMT is available, you can check for active Abis alarms.
Connect the LMT to the BTSE, start the log on procedure and enter the following
command:
b BSS
NE Btsexs BR<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
GETACTIVEALARMS BTSEXS
EVTYP=<type of the failure event>
Typical Failure Event Report for an Abis/PCM Cable Problem: Name =
BPORT:<no> / Event Type = Communication Failure Event / Probable Cause = 10270
Loss of signal / Severity = Major

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

23

Fault Clearance Procedures

MMN:BTSE BS-288

Check the Abis/PCM Cable Connections (OVPT/ABISCON)


Are the Abis/PCM lines fastened correctly in the terminal block of the OVPT/ABISCON
and in the distributing frame in BSC direction?
Y

........... 7

........... 5

For detailed information on the Abis/PCM cable connection, see the corresponding
Installation Manual.
5

Fasten the Abis/PCM Lines Correctly in their Terminals

Result of Fault Clearance?


The fault clearance was successful if all of the following conditions apply:
The red LEDs for Abis alarms on the COBA are off.
The green LEDs OK/SW on the CU indicate a running system.
There are no relevant active alarms.
It may take up to 10 minutes until the LEDs indicate a successful fault clearance.
Was the fault clearance successful?

........... 11

........... 7

Check the Abis/PCM Lines (OVPT/ABISCON)


Write down the cable colors and their corresponding terminals before disconnecting any
cables.
Remove the Abis/PCM lines in the terminal blocks (OVPT/ABISCON and distributing
frame in BSC direction) and examine the cables visually for damages.
Do you see a broken or corroded cable or an insulation that interrupts the contact?
Y

........... 8

........... 10

Repair Bad Abis/PCM Lines or Exchange the Abis/PCM Lines

Result of Fault Clearance?


The module replacement was successful if all of the following conditions apply:
The red LEDs for Abis alarms on the COBA are off.
The green LEDs OK/SW on the CU indicate a running system.
It may take up to 10 minutes until the LEDs indicate a successful fault clearance.
If an LMT is connected to the BTSE, you can also check for relevant active alarms.

24

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

Was the fault clearance successful?

10

........... 11

........... 10

Replace OVPT/ABISCON
To replace the OVPT/ABISCON, go to ...

h ......... fault clearance procedure "OVPT/ABISCON"


11

Finish Fault Clearance


1. If an LMT was connected, log off and disconnect the LMT.
2. Close the BTSE door.
END

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

25

Fault Clearance Procedures

3.2

MMN:BTSE BS-288

ABISCON
The fault clearance of the ABISCON is identical to the fault clearance of the OVPT.

Go to ...

h .......... fault clearance procedure "OVPT/ABISCON"


END

26

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

3.3

BCOM
WARNING Heavy Object

Module BCOM weighs approximately 18 kg/40 lbs. Risk of injury or product damage.
Consider the heaviness when removing and inserting the module.
This warning must appear in the original German text:
WARNUNG SCHWERES BAUTEIL

Modul BCOM wiegt ca. 18 kg. Gefahr der Krperverletzung oder Sachbeschdigung.
Bercksichtigen Sie beim Modultausch das Gewicht des Moduls.
CAUTION Electrostatically Sensitive Components

Modules are susceptible to damage by electrostatic discharge.


Follow ESD precautions when removing and inserting modules. See section ESD Precautions.
CAUTION Risk of Lost Calls

If you lock or remove modules in the TX/RX path of the BTSE, calls may be lost.
To avoid the loss of calls, please follow the instructions in section Avoiding the Loss of
Calls.
1

Open the BTSE Door

Interpret the Fault Message


Note the values specified in the fault message, for example:
Module(s)?
BTS-no?
Rack-no?
Module address?
Use these values for command input. Use the logical address to find the mounting
location of the module(s).

Interpret the Alarm Type


Note the following values in the fault message:
VSWR alarm
Cable problem
Transmitter problem
Receiver failure/problem
Transceiver problem
Is one of these values listed in the fault message?
Y

........... fault clearance procedure "Cable Problems"

........... 4

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

27

Fault Clearance Procedures

MMN:BTSE BS-288

Log on LMT
Connect the LMT to the BTSE and start the log on procedure.

Lock Suspected Module


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
BCOM
BCOM:<no>
LOCK BCOM

Replace the Module

WARNING Heavy Object

Module BCOM weighs approximately 18 kg/40 lbs. Risk of injury or product damage.
Consider the heaviness when removing and inserting the module.
This warning must appear in the original German text:
WARNUNG SCHWERES BAUTEIL

Modul BCOM wiegt ca. 18 kg. Gefahr der Krperverletzung oder Sachbeschdigung.
Bercksichtigen Sie beim Modultausch das Gewicht des Moduls.
1. Disconnect all cables.
2. Remove the affected module.
3. Select a module with a functional HW/SW state compatible to that of the module that
was just removed.
4. Insert the prepared module.
5. Connect all cables (use a torque spanner).
7

Run Test for Replaced Module


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>

28

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

BCOM
BCOM:<no>
PERFTEST BCOM
Note the test outcome.
8

Unlock Suspected Module


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
BCOM
BCOM:<no>
UNLOCK BCOM

Result of Fault Clearance?


Check LED PA on the CU. Wait until the boot process is finished (green LED OK and
SW flashing).
The fault clearance was successful if all of the following conditions apply:
The LEDs signal normal operation.
The outcome of the corresponding module test is pass.
There are no relevant active alarms.
Was the fault clearance successful?

10

........... 11

........... 10

Unsuccessful Fault Clearance


1. The removed (old) module was probably not defective and has to be reinserted.
Repeat steps 5-8 to reinsert the module. Afterwards, continue with this step.
2. If there is another suspected module/interface in the fault message, perform the fault
clearance procedure of the next suspected module/interface. Go to ...

h ......... the corresponding fault clearance procedure


3. Otherwise, call TAC and proceed to step ...

h ......... 13
11

Mark the Removed Module as Defective

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

29

Fault Clearance Procedures

12

MMN:BTSE BS-288

Update the Remote Inventory Data


Update the remote inventory data and renew the backup copy of the inventory data
table. Go to ...

h .......... procedure "Remote Inventory Data Update"


13

Finish Fault Clearance


1. Log off and disconnect the LMT.
2. Close the BTSE door.
END

30

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

3.4

BPORT
BPORT is the Managed Object that represents the Abis ports.

Go to ...

h ......... the corresponding fault clearance procedure "Abis"


END

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

31

Fault Clearance Procedures

3.5

MMN:BTSE BS-288

Cable Problems
CAUTION Electrostatically Sensitive Components

Modules are susceptible to damage by electrostatic discharge.


Follow ESD precautions when removing and inserting modules. See section ESD Precautions.
In most cases, alarms in the TX/RX path originate from loose or damaged cables. Therefore, the relevant cables should be checked first, according to the following procedure.
With the use of the FDUAMCO, additional error sources arise from the cabling.
If the alarm cannot be cleared in this way, the suspected module must be replaced. Note
that the failure cause may be located in the module(s) addressed in the error message
as well as in any other module of the TX/RX path and the antenna subsystem. It is recommended to start with the replacement of the module that is addressed in the fault
message. Afterwards if the error is still there take the other modules in the TX/RX
path into consideration.
Alarms in the TX/RX Path
The combining equipment BCOM provides a hardware indicator for VSWR supervision
but not an LNA failure detection.
VSWR Supervision by CU Powerstage
The existing VSWR supervision of the powerstage of the CU is used. The meaning of
the CU alarm RF power reflected into powerstage comprises the whole TX path
between the CU and the antenna.
VSWR Supervision

g BCOM 6:6: The carrier unit VSWR alarm may detect cable breaks close to the
carrier unit up to approximately 10 meters distance. Only timeslots with a TX signal
level higher than maximum power of CU - 20 dB are checked. The alarm is reported
if the VSWR detection reports an error for at least 10 of 16 timeslots.
BCOM 12:6: The supervision only covers the path between CU and BCOM.It is recommended for both BCOM types to activate the feature Online RF Loopback
because it supervises the whole RF path. See OMN:BSC, Management of Online
RF Loopback.
LNA Supervision by CU
A BCOM LNA failure can be indicated by the existing CU alarm One of the two diversity
receivers fails. If a subsequent CU test does not fail, the error may be located outside
the CU and may be caused by a defective BCOM LNA.

g The failure can only be detected if the TRX is used by traffic. If both diversity receivers fail (e.g., no power supply), the failure can only be detected via BSC alarms. For
example Sleeping cell/TRX detection.
1

Open the BTSE Door


Open the BTSE door.

32

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

If Necessary: Remove the Top Cover


Remove the top cover if the suspected module(s) are installed under the top cover.

Cable Connections Fastened Correctly?


Are the TX/RX cable connections of the suspected module(s) fastened correctly?

h ......... 8

h ......... 4

Fasten Cable Connections


Fasten the cables by tightening their coupling nuts with a torque wrench.

Optional: Log on LMT to Get Active Alarms


Connect the LMT to the BTSE and start the log on procedure.

Check for Active Alarms


b BSS
NE Btsep Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
GETACTIVEALARMS BTSEXS
EVTYP=<type of the failure event>

Result of Fault Clearance?


The fault clearance was successful if all of the following conditions apply:
The LEDs signal normal operation (the LEDs "OK" and "SW" on CU must be on).
There are no relevant active alarms.
Was the fault clearance successful?

........... 11

........... 8

Do the Cables Look O.K.?


Examine the cables visually for damages, such as sharp bends, cracks or bad soldering
connections. Do the cables look O.K.?
Y

h ......... 10

h ......... 9

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

33

Fault Clearance Procedures

MMN:BTSE BS-288

Call TAC
Call TAC to have the damaged cable(s) replaced.

h .......... 11
10

Continue with the Fault Clearance Procedure


Continue with the fault clearance procedure of the module that is addressed in the fault
message. Afterwards if the error is still there take the other modules in the TX/RX
path into consideration.
Additional suspected modules are BCOM, CU and antenna.
Go to ...

h .......... the corresponding fault clearance procedure


11

If the Top Cover was Removed: Mount the Top Cover

12

Finish Fault Clearance


1. If an LMT was connected, log off and disconnect the LMT.
2. Close the BTSE door.
END

34

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

3.6

Fault Clearance Procedures

COBA
CAUTION Electrostatically Sensitive Components
Modules are susceptible to damage by electrostatic discharge.
Follow ESD precautions when removing and inserting modules. See section "ESD Precautions".

g This procedure describes the replacement of COBAs of the same module types
(COBA4P12 COBA4P12 or COBA2P8 COBA2P8).
If you want to replace a COBA2P8 with a COBA4P12, refer to procedure "COBA2P8
COBA4P12.

g The BS-240XS and the BS-288 cannot be equipped with a COSA or COREXT
module.

g After the completion of this replacement procedure, it is necessary to perform the


procedure Remote Inventory Data Restoration as mentioned in the corresponding
step.
Module COBA may be removed while power is on.
Flow Chart and Comments
The following flow chart gives an overview of the fault clearance procedure. Comments
to the steps are included behind the flow chart, followed by the steps in detail.

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

35

Fault Clearance Procedures

MMN:BTSE BS-288

Steps:
1-3

4-6

7*

9*

10-13*

14,15

Fault clearance
procedure start
(LMT phase 2)

COBA
replacement

Requested logon
(LMT phase 1)

BTSEXS Flash
EPROM format

SW download
and activation
(LMT phase 2)

BTSE
reconfiguration

Connection
to BSC
(LMT phase 3)

continue below ...

Figure 7

36

Flow Chart COBA Replacement (Same Module Type) (Part I)

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

... continued from above

16

Fault
clearance
successful?

17
no

reinsertment;
next module check or
TAC call

yes
18

19*

20

Figure 8

Remote Inventory
Data restoration

Procedure Remote Inventory


Data Resotration

Fault clearance
procedure finish

Flow Chart COBA Replacement (Same Module Type) (Part II)

Step

*Comments

After the insertion of the new COBA, the system will automatically log off. It is
necessary to log on again. The BTSE is then in phase 1.

After the COBA replacement, the BTSE specific data base for this COBA is
lost. Therefore, it is necessary to download and activate the SW again.

10-13

After the COBA replacement, the BTSE specific data base is lost. This makes
it necessary to reconfigure the BTSE. Usually, a backup copy of the configuration is stored with the site specific documentation. If there is no backup,
TAC must be called.

19

It is necessary to rebuild the inventory data that was stored on the removed
COBA. Usually, a backup IDF file is available for this purpose, which is stored
on site with the site specific documentation. If there is no backup file, the data
can be extracted from the BSC IDF file via TAC, or can be entered by hand.

Table 3
1

Module marking
as defective

Comments for Flow Chart COBA Replacement (Same Module Type)

Open the BTSE Door

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

37

Fault Clearance Procedures

MMN:BTSE BS-288

Interpret the Fault Message


Note the values specified in the fault message, for example:
Module(s)?
BTS-no?
Rack-no?
Module address?
Use these values for command input. Use the logical address to find the mounting
location of the module(s).

Log on LMT
Connect the LMT to the BTSE and start the log on procedure.

Switch off COBA


Switch off the COBA with the corresponding breaker on the DC panel.

Replace the COBA


1.
2.
3.
4.

Remove the COBA2P8.


Select a module of the same type as the module that was just removed.
Check the DIP switch settings against the replaced module.
Insert the prepared COBA.

Switch on COBA
Switch on the COBA with the corresponding breaker on the DC panel.
The boot process starts. After the boot process is finished, the green LED ACT is
switched on.

Log on
b Local Logon at NE Btsexs
UserName:<user>
Password:<password>
Ok
The BTSE is now in phase 1.

Format BTSEXS Flash EPROM


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
FORMAT BTSEXS FLASH

38

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

g For COBA4P12 replacement: This process takes a few minutes. Please wait until
the process has finished.
9

Download and Activate the SW


Download and activate the software. Afterwards, log on again (the BTSE is then in
phase 2). Refer to...

i ......... Installation Test Manual ITMN, procedure "SW Download and Activation"
10

Backup Copy of the BTSE Reconfiguration Available?


Is a backup copy of the site specific configuration available?

11

........... 12

........... 11

Call TAC
Call TAC and proceed to step ...

h ......... 20
12

Copy the Backup Script Files to the BKBTS\BS240XS Directory


Copy the backup script files script*p.lmt from the storage media to the harddisk of the
LMT PC e.g., C:\...\LMT<version>\BKBTS\BS240XS\Backup1.

13

Restore the HW Configuration


1. Select File Backup BTS from the LMT menu or click on the corresponding icon
in the tool bar.
2. Click on the Restore button in the Backup BTS window or select File Restore.
3. Select the correct configuration (e.g. Backup1) and confirm by clicking on OK .
4. After the restore procedure you can repeat it or go on working with the LMT. Click
on the OK button to finish the process.

14

Connect BTS Site Manager to the BSC


b BSS
NE Btsexs Br<no>:<NE id>
BSS-FUNCTIONAL
BTSM
BTSM:<no>
CONNBSC BTSM

15

Log on
b Local Logon at NE Btsexs
UserName:<user>
Password:<password>

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

39

Fault Clearance Procedures

MMN:BTSE BS-288

Ok
The BTSE is now in phase 3. The BSC will start the alignment with the BTSE.
16

Result of Fault Clearance?


The fault clearance was successful if all of the following conditions apply:
The LEDs signal normal operation.
There are no relevant active alarms.
The object details for the COBA are as follows:
Availability Status

Null

Operational State

Enabled

Administrative State

Unlocked

Was the fault clearance successful?

17

........... 18

........... 17

Unsuccessful Fault Clearance


1. The removed (old) module was probably not defective and has to be reinserted.
Repeat steps 4-15 to reinsert the module. Afterwards, continue with this step.
2. If there is another suspected module/interface in the fault message, perform the fault
clearance procedure of the next suspected module/interface. Go to ...

h .......... the corresponding fault clearance procedure


3. Otherwise, call TAC and proceed to step ...

h .......... 20
18

Mark the Removed Module as Defective

19

Restore the Remote Inventory Data


For the remote inventory data restoration, go to ...

i .......... procedure "Remote Inventory Data Restore"


20

Finish Fault Clearance


Close the BTSE door.
END

40

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

3.7

Fault Clearance Procedures

COBA2P8 COBA4P12
CAUTION Electrostatically Sensitive Components
Modules are susceptible to damage by electrostatic discharge.
Follow ESD precautions when removing and inserting modules. See section "ESD Precautions".

g This procedure describes the replacement of a COBA2P8 with a COBA4P12.


If you want to replace a COBA with a COBA of the same module type, refer to procedure "COBA".

g The BS-240XS and the BS-288 cannot be equipped with a COSA or COREXT
module.

g After the completion of this replacement procedure, it is necessary to perform the


procedure Remote Inventory Data Restoration as mentioned in the corresponding
step.
Module COBA may be removed while power is on.
Flow Chart and Comments
The following flow chart gives an overview of the fault clearance procedure. Comments
to the steps are included behind the flow chart, followed by the steps in detail.

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

41

Fault Clearance Procedures

MMN:BTSE BS-288

Steps:
1-2

3-5

6*

8*

9-13*

14,15

Fault Clearance
Procedure Start
(LMT Phase 2)

COBA
Replacement

Requested Logon
(LMT Phase 1)

BTSEXS Flash
EPROM Format

SW Download
and Activation
(LMT Phase 2)

BTSE
Reconfiguration

Connection
to BSC
(LMT Phase 3)

continue below ...

Figure 9

42

Flow Chart "COBA2P8 with COBA4P12 Replacement" (Part I)

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

... continued from above

16

Fault
clearance
successful?

17
no

Reinsertment;
next module check or
TAC call

yes
18

19*

20

Figure 10

Remote Inventory
Data restoration

Procedure Remote Inventory


Data Resotration

Fault clearance
procedure finish

Flow Chart for COBA2P8 with COBA4P12 Replacement Procedure (Part


II)

Step

*Comments

After the insertion of the new COBA, the system automatically logs off. It is
necessary to log on again. The BTSE is then in phase 1.

After the COBA replacement the BTSE specific data base for this COBA is
lost. Therefore, it is necessary to download and activate the SW again.

9-13

After the COBA replacement, the BTSE specific data base is lost. This makes
it necessary to reconfigure the BTSE. Usually, a backup copy of the configuration is stored with the site specific documentation. If there is no backup,
TAC must be called.

19

It is necessary to rebuild the inventory data that was stored on the removed
COBA. Usually, a backup IDF file is available for this purpose, which is stored
on site with the site specific documentation. If there is no backup file, the data
can be extracted from the BSC IDF file via TAC, or can be entered by hand.

Table 4

Module marking
as defective

Comments for Flow Chart COBA2P8 with COBA4P12 Replacement Procedure

Open the BTSE Door

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

43

Fault Clearance Procedures

MMN:BTSE BS-288

Log on LMT
Connect the LMT to the BTSE.

Switch off COBA2P8


Switch off the COBA with the corresponding breaker on the DC panel.

Replace COBA2P8 with COBA4P12


1. Remove the COBA2P8.
2. Check the DIP switch settings of the removed COBA2P8. Set the DIP switches of
the prepared COBA4P12 correspondingly. Refer to hardware manual HW:BTSE
Modules, section "M:COBA4P12" for a desciption of the DIP switches.
3. Insert the prepared COBA4P12.

Switch on COBA
Switch on the COBA with the corresponding breaker on the DC panel.
The boot process starts. After the boot process is finished, the green LED ACT is
switched on.

Log on
b Local Logon at NE Btsexs
UserName:<user>
Password:<password>
Ok
The BTSE is now in phase 1.

Format BTSEXS Flash EPROM


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
FORMAT BTSEXS FLASH

g For COBA4P12 replacement: This process takes a few minutes. Please wait until
the process has finished.
8

Download and Activate the SW


Download and activate the software. Afterwards, log on again (the BTSE is then in
phase 2). Refer to ...

i .......... the corresponding Installation Test Manual ITMN SW Download and Activation

44

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

Backup Copy of the BTSE Reconfiguration Available?


Is a backup copy of the site specific configuration available?

10

........... 11

........... 10

Call TAC
Call TAC and proceed to step ...

h ......... 20
11

Copy the Backup Script Files to the BKBTS\BS240XS Directory


Copy the backup script files script*p.lmt from the storage media to the harddisk of the
LMT PC e.g., C:\...\LMT<version>\BKBTS\BtsPlus\Backup1.

12

If Required: Change Backup Script File Script3p.lmt

g This step is only necessary if the required line impedance setting ("LIMP") is
lmp75Ohm and does therefore not correspond to the default value. The operator is
responsible for the correct setting of the lineImpedance attribute.
1. Open the file Script3p.lmt with a text editor (e.g. NotePad).
2. Modify the command Create BPORT. Set the attribute "LIMP" to "lmp75Ohm".
3. Save the file as Script3p.lmt.
13

Restore the HW Configuration


1. Select File Backup BTS from the LMT menu or click on the corresponding icon
in the tool bar.
2. Click on the Restore button in the Backup BTS window or select File Restore.
3. Select the correct configuration (e.g. Backup1) and confirm by clicking on OK .
4. After the restore procedure you can repeat it or go on working with the LMT. Click
on the OK button to finish the process.

14

Connect BTS Site Manager to the BSC


b BSS
NE Btsexs Br<no>:<NE id>
BSS-FUNCTIONAL
BTSM
BTSM:<no>
CONNBSC BTSM

15

Log on
b Local Logon at NE Btsexs
UserName:<user>
Password:<password>

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

45

Fault Clearance Procedures

MMN:BTSE BS-288

Ok
The BTSE is now in phase 3. The BSC starts the alignment with the BTSE.
16

Result of Fault Clearance?


The fault clearance was successful if all of the following conditions apply:
The LEDs signal normal operation.
There are no relevant active alarms.
The object details for the COBA are as follows:
Availability Status

Null

Operational State

Enabled

Administrative State

Unlocked

Was the fault clearance successful?

17

........... 18

........... 17

Unsuccessful Fault Clearance


1. The removed (old) module was probably not defective and has to be reinserted.
Repeat steps 3-15 to reinsert the module. Afterwards, continue with this step.
2. If there is another suspected module/interface in the fault message, perform the fault
clearance procedure of the next suspected module/interface. Go to ...

h .......... the corresponding fault clearance procedure


3. Otherwise, call TAC and proceed to step ...

h .......... 20
18

Mark the Removed Module as Defective

19

Restore the Remote Inventory Data


For the remote inventory data restoration, please go to ...

i .......... procedure "Remote Inventory Data Restoration"


20

Finish Fault Clearance


1. Log off and disconnect the LMT.
2. Close the BTSE door.
END

46

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

3.8

CU
CAUTION Electrostatically Sensitive Components

Modules are susceptible to damage by electrostatic discharge.


Follow ESD precautions when removing and inserting modules. See section ESD Precautions.
CAUTION Risk of Overheating

BS-288: To ensure sufficient airflow, the CU slots must be equipped in a fixed order.
Empty CU slots must be covered by cover parts (CP:CU288V1 or CP:CUV2). It depends
on the CU slot which cover part must be used.
Install the CUs in the order described in the Installation Manual and use the appropriate
cover parts. Refer to the corresponding Installation Manual.
CAUTION Risk of Overheating

BS-240XS: To ensure sufficient airflow, empty CU slots must be covered by cover parts
(CP:CUVX (90 mm)). Only CU slot 1, 3 and 5 can be left unequipped with a CU and
covered by a cover part
Install the CUs in the order described in the Installation Manual and use the appropriate
cover parts. Refer to the corresponding Installation Manual.
CAUTION Risk of Lost Calls

If you lock or remove modules in the TX/RX path of the BTSE, calls may be lost.
To avoid the loss of calls, follow the instructions in section Avoiding the Loss of Calls.
NOTICE Avoid Reduced Quality
In case of locking a CU in a cell with enabled Antenna Hopping, the concerned CU is
blocked at once but Antenna Hopping is blocked only after 9.6 seconds. During this time
the quality is reduced.
To avoid this, switch off Antenna Hopping before locking the CU.

g It is possible to use GCU/ECU/FlexCU in mixed configurations, but note the following: Since the GSM 1800 GCU has more RF output power than the GSM 1800 CU,
mixed cell configurations might result in slight changes of some performance
counters and CU dependent coverage. It is not recommended to use the antenna
hopping mode in this configuration.

g BS-240XS: It is not possible to install a GCU or ECU in an adjacent slot to a FlexCU.


g All installed CUs must support the same GSM frequency band (dual band mode is
not supported).
Module CU may be removed while the power is on.
1

Open the BTSE Door

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

47

Fault Clearance Procedures

MMN:BTSE BS-288

Interpret the Fault Message


Note the values specified in the fault message, for example:
Module(s)?
BTS-no?
Rack-no?
Module address?
Use these values for command input. Use the logical address to find the mounting
location of the module(s).

Interpret the Alarm Type


Note the following values in the fault message:
VSWR alarm
Cable problem
Transmitter problem
Receiver failure/problem
Transceiver problem
Is one of these values listed in the fault message?

........... fault clearance procedure "Cable ProblemsCable Problems"

........... 4

Autorecovery (EAUTOREC) Enabled?


Is the attribute Autorecovery (EAUTOREC) enabled?
Y

........... 5

........... 7

If you have no information on this attribute, continue with No (N).


5

Replace the Module (Quick Module Replacement)


1. Mark the normal path and the diversity path of the semi-rigid/flexi cables before you
disconnect them.
2. Disconnect all semi-rigid/flexi cables.
3. Remove the affected module.
4. Select a module with a functional HW/SW state compatible to that of the module that
was just removed.
5. Partly insert the prepared module. Make sure that it does not yet come into contact
with the backplane connectors by leaving about 2 cm/0.75 distance between
module and backplane.
6. Connect all semi-rigid cables (use a torque spanner).
g If there was contact between the module and the backplane connectors before
all semi-rigid/flexi cables were connected, pull the module again about 2
cm/0.75 out of the rack until it is no longer connected to the backplane.
7. Fully insert the prepared module.

Result of Fault Clearance?


Wait until the boot process is finished (green LED OK and SW are flashing).

48

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

If no LMT is connected, the hardware can only be tested and checked for relevant active
alarms via Radio Commander at the OMC. It is recommended to call the OMC in order
to make sure that the BTSE has gone back to normal operation before you leave the
site. The main purpose of the test is to check the receivers, which cannot be supervised
completely during normal operation. The power amplifier is supervised during normal
operation, so that a fault can be detected immediately.
The fault clearance was successful if the following conditions apply:
The LEDs signal normal operation (no red LED PA on CU).
(The outcome of the corresponding module test is pass.)
(There are no relevant active alarms.)
Was the fault clearance successful?

........... 14

........... 13

Log on LMT
Connect the LMT to the BTSE and start the log on procedure.

Lock Suspected Module


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
CU
CU:<no>
LOCK CU

Replace the Module


1. Mark the normal path and the diversity path of the semi-rigid/flexi cables, before you
disconnect them.
2. Disconnect all semi-rigid/flexi cables.
3. Remove the affected module.
4. Select a module with a functional HW/SW state compatible to that of the module that
was just removed.
5. Insert the prepared module.
6. Connect all semi-rigid/flexi cables (use a torque spanner).

10

Run Test for Replaced Module


The main purpose of the test is to check the receivers, which cannot be supervised completely during normal operation. The power amplifier is supervised during normal operation, so a fault will be detected immediately.

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

49

Fault Clearance Procedures

MMN:BTSE BS-288

g During this test, a test signal with maximum power is transmitted for a duration of
one timeslot.
b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
CU
CU:<no>
PERFTEST CU
Note the test outcome.
11

Unlock Suspected Module


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
CU
CU:<no>
UNLOCK CU

12

Result of Fault Clearance?


Wait until the boot process is finished (green LED OK and SW are flashing).
The fault clearance was successful if all of the following conditions apply:
The LEDs signal normal operation (no red LED PA on CU).
The outcome of the corresponding module test is pass.
There are no relevant active alarms.
Was the fault clearance successful?

13

........... 14

........... 13

Unsuccessful Fault Clearance


1. The removed (old) module was probably not defective and has to be reinserted.
Repeat steps 8-11 to reinsert the module (for quick module replacement: step 5).
Afterwards, continue with this step.

50

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

2. If there is another suspected module/interface in the fault message, perform the fault
clearance procedure of the next suspected module/interface. Go to ...

h ......... the corresponding fault clearance procedure


3. Otherwise, call TAC and proceed to step ...

h ......... 15
14

Mark the Removed Module as Defective

15

Finish Fault Clearance


1. In an LMT was connected, log off and disconnect the LMT.
2. Close the BTSE door.
END

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

51

Fault Clearance Procedures

3.9

MMN:BTSE BS-288

ECU
ECU is the CU for the EDGE technology.

Go to ...

h .......... fault clearance procedure "CU"


END

52

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

3.10

Fan
WARNING Risk of Injury from Running Rotor

After the removal of the module, the rotor will keep running for a few seconds. Moving
rotor blades can crush and cut your hand.
Make sure not to touch the rotor.
This warning must appear in the original German text:
WARNUNG Verletzungsgefahr durch laufende Rotorbltter

Die Rotorbltter laufen noch fr einige Sekunden nach dem Herausziehen des Rotors.
Laufende Rotorbltter knnen Schnitt- und Quetschwunden an den Hnden verursachen.
Berhren Sie die Rotorbltter nicht.
CAUTION Electrostatically Sensitive Components

Modules are susceptible to damage by electrostatic discharge.


Follow ESD precautions when removing and inserting modules. See section ESD Precautions.
The fan is represented by the managed object FANP in the LMT.
1

Open the BTSE Door


Open the BTSE door.

Interpret the Fault Message


Note the values specified in the fault message, for example:
Module(s)?
BTS-no?
Rack-no?
Module address?
Use these values for command input. Use the logical address to find the mounting
location of the module(s).

Log on LMT
Connect the LMT to the BTSE and start the log on procedure.

Lock Suspected Module


b BSS
NE Btsep Br<no>:<NE id>
BSS-EQUIPMENT
BTSXS
BTSXS:<no>
RACK

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

53

Fault Clearance Procedures

MMN:BTSE BS-288

RACK:<no>
FANP
FANP:<no>
LOCK FANP
5

Replace the Module

WARNING Risk of Injury from Running Rotor

After the removal of the module, the rotor will keep running for a few seconds. Moving
rotor blades can crush and cut your hand.
Make sure not to touch the rotor.
This warning must appear in the original German text:
WARNUNG Verletzungsgefahr durch laufende Rotorbltter

Die Rotorbltter laufen noch fr einige Sekunden nach dem Herausziehen des Rotors.
Laufende Rotorbltter knnen Schnitt- und Quetschwunden an den Hnden
verursachen.
Berhren Sie die Rotorbltter nicht.
1. Remove the affected module by pressing the two levers up.

Lever
Figure 11

Lever

Levers on the Fan

2. Select a module with a functional HW/SW state compatible to that of the module that
was just removed.
3. Insert the prepared module. It needs to be firmly locked in place.
6

Run Test for Replaced Module


b BSS
NE Btsep Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS

54

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

BTSEXS:<no>
RACK
RACK:<no>
FANP
FANP:<no>
PERFTEST FANP
Note the test outcome.
7

Unlock Suspected Module


b BSS
NE Btsep Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK:<no>
FANP
FANP:<no>
UNLOCK FANP

Result of Fault Clearance?


The fault clearance was successful if all of the following conditions apply:
The outcome of the corresponding module test is pass.
There are no relevant active alarms.
Was the fault clearance successful?

........... 10

........... 9

Unsuccessful Fault Clearance


1. The removed (old) module was probably not defective and has to be reinserted.
Repeat steps 4-7 to reinsert the module. Afterwards, continue with this step.
2. If there is another suspected module/interface in the fault message, perform the fault
clearance procedure of the next suspected module/interface. Go to ...

h ......... the corresponding fault clearance procedure


3. Otherwise, call TAC and proceed to step ...

h ......... 12
10

Mark the Replaced Module as Defective

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

55

Fault Clearance Procedures

11

MMN:BTSE BS-288

Update the Remote Inventory Data


Update the remote inventory data and renew the backup copy of the inventory data
table. Go to...

h procedure Remote Inventory Data Update


12

Finish Fault Clearance


1. Log off and disconnect the LMT.
2. Close the BTSE door.
END

56

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

3.11

FCUMAIN
FCUMAIN is a functional part of the FlexCU.

Go to ...

h ......... fault clearance procedure "FlexCU"


END

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

57

Fault Clearance Procedures

3.12

MMN:BTSE BS-288

FCUTR
FCUTR is a functional part of the FlexCU.

Go to ...

h .......... fault clearance procedure "FlexCU"


END

58

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

3.13

Filter Mat
The filter mat must be exchanged annually. In a very dirty environment, the mat must be
exchanged every six months.

Open the BTSE Door


Open the BTSE door.

Replace the Filter Mat


1. Detach the spring bar and remove the mat.
2. Select a new filter mat with the same characteristics.
3. Insert the new mat and attach the spring bar.

Finish Fault Clearance


Close the BTSE door.
END

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

59

Fault Clearance Procedures

3.14

MMN:BTSE BS-288

FlexCU
CAUTION Electrostatically Sensitive Components
Modules are susceptible to damage by electrostatic discharge.
Follow ESD precautions when removing and inserting modules. See section ESD Precautions.

CAUTION Risk of Lost Calls


If you lock or remove modules in the TX/RX path of the BTSE, calls may be lost.
To avoid the loss of calls, follow the instructions in section Avoiding the Loss of Calls.

CAUTION Avoid Reduced Quality


In case of locking a FlexCU in a cell with enabled Antenna Hopping, the concerned
FlexCU is blocked at once but Antenna Hopping is blocked only after 9.6 seconds.
During this time the quality is reduced.
To avoid this, switch off Antenna Hopping before locking the CU.
The following table shows the Managed Objects related to the FlexCU. The FlexCU
comprises two carrier units in the size of one.
Managed
Object

Numbers
per Module

Additional Information

FCUMAIN

This Managed Object represents the part of the FlexCU


that is common to both carriers.

FCUTR

1-2

This Managed Object represents the carrier specific part


of the FlexCU.

Table 5

Managed Objects for FlexCU

This procedure covers the fault messages FCUMAIN and FCUTR.


The rack can operate GCU/ECU/FlexCU modules in mixed configurations.
All installed CUs must support the same GSM frequency band (dual band mode is not
supported).

g BS-240XS: Up to 3 FlexCUs can be used.


FlexCUs can be installed only in CU slot 0, 2 and 4.
To ensure sufficient airflow, only CU slot 1, 3 and 5 can be left unequipped with a
CU.
Empty CU slots must be covered by cover part CP:CUVX (90 mm).
It is not possible to install a GCU or ECU in an adjacent slot to a FlexCU.

g BS-288: Up to 6 FlexCUs can be used (3 FlexCUs with BCOM 6:6).


To ensure sufficient airflow empty CU slots must be covered by cover parts
(CP:CU288V1 or CP:CUV2). It depends on the CU slot which cover part must be
used.
The CU slots must be equipped in a fixed order. Refer to installation manual
IMN:BS-288.

60

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

Module FlexCU may be removed while the power is on.


1

Open the BTSE Door

Interpret the Fault Message


Note the values specified in the fault message, for example:
Module(s)?
BTS-no?
Rack-no?
Module address?
Use these values for command input. Use the logical address to find the mounting
location of the module(s).

Interpret the Alarm Type


Note the following values in the fault message:
VSWR alarm
Cable problem
Transmitter problem
Receiver failure/problem
Transceiver problem
Is one of these values listed in the fault message?

........... fault clearance procedure "Cable Problems"

........... 4

Autorecovery (EAUTOREC) Enabled?


Is autorecovery (attribute EAUTOREC) enabled?
Y

........... 5

........... 7

If you have no information on this attribute, continue with No (N).


5

Replace the Module (Quick Module Replacement)


1. Mark the normal and the diversity path of the semi-rigid/flexi cables before you disconnect them.
2. Disconnect all semi-rigid/flexi cables.
3. Remove the affected module.
4. Select a module with a functional HW/SW state compatible to that of the module that
was just removed.
5. Partly insert the prepared module. Make sure that it does not yet come into contact
with the back plane connectors by leaving about 2 cm/0.75 distance between
module and back plane.
6. Connect all semi-rigid/flexi cables. Use a torque spanner.

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

61

Fault Clearance Procedures

MMN:BTSE BS-288

g If there was contact between the module and the back plane connectors before
all semi-rigid/flexi cables were connected, pull the module again about 2
cm/0.75 out of the rack until it is no longer connected to the back plane.
7. Fully insert the prepared module.
6

Result of Fault Clearance?


Wait until the boot process is finished (green LEDs SW0, SW1 and OK are flashing).
If no LMT is connected, the hardware can only be tested and checked for relevant active
alarms via Radio Commander at the OMC. It is recommended to call the OMC in order
to make sure that the BTSE has gone back to normal operation before you leave the
site.
The fault clearance was successful if the following conditions apply:
The LEDs signal normal operation (no red LED PA0 or PA1 at the FlexCU).
(The outcome of the corresponding module test is pass.)
(There are no relevant active alarms.)
Was the fault clearance successful?

........... 20

........... 19

Log on LMT
Connect the LMT to the BTSE and start the log on procedure.

Lock FCUMAIN of the Suspected Module


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
FCUMAIN
FCUMAIN:<no>
LOCK FCUMAIN

Lock FCUTR(s) of the Suspected Module

g If 2 FCUTRs are created per module, both FCUTRs must be locked.


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS

62

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

BTSEXS:<no>
RACK
RACK<no>
FCUTR
FCUTR:<no>
LOCK FCUTR
Repeat this command for the second FCUTR if created.
10

Replace the Module


1. Mark the normal and the diversity path of the semi-rigid/flexi cables, before you disconnect them.
2. Disconnect all semi-rigid/flexi cables.
3. Remove the affected module.
4. Select a module with a functional HW/SW state compatible to that of the module that
was just removed.
5. Insert the prepared module.
6. Connect all semi-rigid/flexi cables. Use a torque spanner.

11

Run Test for FCUMAIN of the Replaced Module


The main purpose of the test is to check the receivers, which cannot be supervised completely during normal operation. The poweramplifier is supervised during normal operation, so a fault will be detected immediately.
b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
FCUMAIN
FCUMAIN:<no>
PERFTEST FCUMAIN
Note the test outcome.

12

Unlock FCUMAIN of the Suspected Module


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

63

Fault Clearance Procedures

MMN:BTSE BS-288

RACK<no>
FCUMAIN
FCUMAIN:<no>
UNLOCK FCUMAIN
13

Run Test for Even-Numbered FCUTR of the Replaced Module


If two FCUTRs are created per module and the FlexCU operates in 4RxTxDiv mode, the
even-numbered instance of FCUTR may affect the behaviour of the odd-numbered
FCUTR during the test. To avoid this, the even-numbered FCUTR must be in the state
enabled before the odd-numbered FCUTR is tested. Therefore, the even-numbered
FCUTR must be tested and unlocked prior to the odd-numbered one.

g During this test, a test signal with maximum power is transmitted for a duration of
one timeslot.
b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
FCUTR
FCUTR:<no>
PERFTEST FCUTR
Note the test outcome.
14

Unlock Even-Numbered FCUTR of the Suspected Module


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
FCUTR
FCUTR:<no>
UNLOCK FCUTR

15

Run Test for Odd-Numbered FCUTR of the Replaced Module (if Created)

g During this test, a test signal with maximum power is transmitted for a duration of
one timeslot.

64

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
FCUTR
FCUTR:<no>
PERFTEST FCUTR
Note the test outcome.
16

Unlock Odd-Numbered FCUTR of the Suspected Module (if Created)


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK<no>
FCUTR
FCUTR:<no>
UNLOCK FCUTR

17

Check for Active Alarms


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
GETACTIVEALARMS BTSEXS
EVTYP=<type of the failure event>

18

Result of Fault Clearance?


Wait until the boot process is finished (green LEDs SW0, SW1 and OK are flashing).
The fault clearance was successful if all of the following conditions apply:
The LEDs signal normal operation (no red LED PA0 or PA1 at the FlexCU).
The outcome of the corresponding module test is pass.
There are no relevant active alarms.

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

65

Fault Clearance Procedures

MMN:BTSE BS-288

Was the fault clearance successful?

19

........... 20

........... 19

Unsuccessful Fault Clearance


1. The removed (old) module was probably not defective and has to be reinserted.
Repeat steps 8-16 to reinsert the module (for quick module replacement: step 5).
Afterwards, continue with this step.
2. If there is another suspected module/interface in the fault message, perform the fault
clearance procedure of the next suspected module/interface. Go to ...

h .......... the corresponding fault clearance procedure


3. Otherwise, call TAC and proceed to step ...

h .......... 21
20

Mark the Removed Module as Defective

21

Finish Fault Clearance


1. In an LMT was connected, log off and disconnect the LMT.
2. Close the BTSE door.
END

66

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

3.15

GCU
GCU is a carrier unit. It is used for the GMSK technology only.

Go to ...

h ......... fault clearance procedure "CU"


END

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

67

Fault Clearance Procedures

3.16

MMN:BTSE BS-288

LAPDLE
A LAPDLE fault message indicates a problem with the connection to the BSC. This connection is checked in procedure Abis.

Go to ...

h .......... fault clearance procedure "Abis"


END

68

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

3.17

OVPT/ABISCON
CAUTION Electrostatically Sensitive Components

Modules are susceptible to damage by electrostatic discharge.


Follow ESD precautions when removing and inserting modules. See section ESD Precautions.

g If the OVPT/ABISCON fails in case of a multidrop configuration, the PCM line for all
subsequent BTSEs is also interrupted.
Module OVPT/ABISCON may be removed while power is on.
1

Open the BTSE Door

Remove the Top Cover

Interpret the Fault Message


Note the values specified in the fault message, for example:
Module(s)?
BTS-no?
Rack-no?
Module address?
Use these values for command input. Use the logical address to find the mounting
location of the module(s).

Log on LMT
Connect the LMT to the BTSE and start the log on procedure.

Lock Site Manager


b BSS
NE Btsexs Br<no>:<NE id>
BSS-FUNCTIONAL
BTSM
BTSM:<no>
LOCKREQUEST BTSM

Disconnect Site Manager from BSC/Switch from Phase 3 to Phase 2


b BSS
NE Btsexs Br<no>:<NE id>
BSS-FUNCTIONAL

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

69

Fault Clearance Procedures

MMN:BTSE BS-288

BTSM
BTSM:<no>
DISCBSC BTSM
7

Log on
b BSS
Logon
UserID: <user>
Password: <password>
Connect
The BTSE is now in phase 2.

Replace the Module


1. Disconnect all cables from the terminal block or the coaxial connectors and note
their positions.
2. Dismantle all cables from the clamping saddle.
3. Loosen the screws of the affected module.
4. Remove the module.
5. Select a module with a functional HW/SW state compatible to that of the module that
was just removed.
6. Insert the prepared module.
7. Fasten the screws.
8. Connect all cables to the terminal block or the coaxial connectors according to your
notes.

Connect Site Manager to BSC /Switch from Phase 2 to Phase 3


b BSS
NE Btsexs Br<no>:<NE id>
BSS-FUNCTIONAL
BTSM
BTSM:<no>
CONNBSC BTSM

10

Log on
b BSS
Logon
UserID: <user>
Password: <password>
Connect
The BTSE is now in phase 3. The BSC will start the alignment with the BTSE.

70

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

11

Fault Clearance Procedures

Check for Active Alarms


b BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
GETACTIVEALARMS BTSEXS
EVTYP=<type of the failure event>

12

Result of Fault Clearance?


The fault clearance was successful if all of the following conditions apply:
The LEDs signal normal operation.
There are no relevant active alarms.
Was the fault clearance successful?

13

........... 14

........... 13

Unsuccessful Fault Clearance


1. The removed (old) module was probably not defective and has to be reinserted.
Repeat steps 5-10 to reinsert the module. Afterwards, continue with this step.
2. If there is another suspected module/interface in the fault message, perform the fault
clearance procedure of the next suspected module/interface. Go to ...

h ......... the corresponding fault clearance procedure


3. Otherwise, call TAC and proceed to step ...

h ......... 16
14

Mark the Replaced Module as Defective

15

Update the Remote Inventory Data


Update the remote inventory data and renew the backup copy of the inventory data
table. Go to ...

h ......... procedure "Remote Inventory Data Update"


16

Mount the Top Cover

17

Finish Fault Clearance


1. Log off and disconnect the LMT.
2. Close the BTSE door.

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

71

Fault Clearance Procedures

MMN:BTSE BS-288

END

72

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

3.18

PCM Line
A PCM line fault message indicates a problem with the connection to the BSC. This connection is checked in procedure Abis.

Go to ...

h ......... fault clearance procedure "Abis"


END

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

73

Fault Clearance Procedures

3.19

MMN:BTSE BS-288

Remote Inventory Data Creation


After replacing the COBA, it is necessary to rebuild the inventory data that was stored
on the removed COBA. Usually, a backup IDF file is available for this purpose, which is
stored on site with the site specific documentation. The following procedure describes
how to enter the data by hand if there is no backup IDF file.
Flow Chart:
The following flow chart gives an overview of the fault clearance procedure. Comments
on the steps are included behind the flow chart, followed by the steps in detail.

Steps:
LMT

IDT file

1*

IDT file upload


from BTSE

(ob_RIUs)

IDF Evolution

2*

IDF evolution
start

Initial situation:
BTSE with
ob_RIU data only

IDF Evolution

3*

IDT file
open
IDF Evolution

4*
nob_RIU creation

IDF Evolution

IDF file

5*

IDF file generation


for backup

(ob/nob_RIUs)
IDF Evolution

6*

nob_RIU data export (NOB file)


LMT

NOB file

7*

NOB file download


to BTSE

(nob_RIUs)
8*

Figure 12

74

Return to COBA
replacement procedure

Flow Chart Remote Inventory Data Creation

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

Step

*Comments

The remote inventory data that is stored in the BTSE as IDT file must be
uploaded to the LMT PC. This file only contains the ob_RIU data.

2-4

The nob_RIU data has to be entered into the IDT file via the software IDF Evolution.

An IDF file, which contains the remote inventory data of the ob_RIU and
nob_RIU modules, must be created from the IDT file for backup purposes.

6-7

To load the nob_RIU data into the BTSE, it is necessary to export the nob_RIU
data from the IDT file into a NOB file and to download this file into the BTSE.

Table 6
1

Comments on Flow Chart Remote Inventory Data Creation

Upload IDT File from the BTSE


b BSS
NE Btsexs BR<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
REMINV
REMINV:<no>
UPLLIDF REMINV
(DESTDIR=<path>)
(FILE=<file name>)
OVERWRITE=<YES>
Additional Information: The attributes DESTDIR and FILE are optional. If no
special path or file name is entered, the file is uploaded to the default directory of the
IDF Evolution. Select the attribute OVERWRITE=<yes> to overwrite any former
version of the uploaded IDT file.

Start IDF Evolution


To start the IDF Evolution select IDF GSM IDF Editor from the Windows program
menu.

Open IDT File


1. Select File Open from the menu.
2. Select the uploaded file from the list in the appearing window; e.g.: C:...\LMT<version>\Idf\Upload\BTSE.idt.
3. Double-click on the file name or click on the Open button.

Create the Remote Inventory Data of the nob_RIU Units


1. Click the right mouse button on the N-Record.

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

75

Fault Clearance Procedures

MMN:BTSE BS-288

2. Click on the appearing Create button.


3. Select the Network entity type (Ney Type), Functional Address and Type (FunctionalAddress:FunctionalAddressType), Equipment position
(SBS_Equipment_Position) of the module you want to create.
4. Click on the Inventory button.
5. A pop-up window opens in which the data can be entered manually or automatically
via the 2D-Code Reader. Key in the data, or click on the Scan button to use the 2DCode Reader.
6. If required, select the serial port of the 2D-Code Reader in the appearing window.
7. To start the scanning process, press the button on the 2D-Code Reader. The data
will be inserted into the corresponding fields.
8. Confirm the data by clicking on the OK button.
9. Repeat these steps for the next module you want to create.
10. After creating all nob_RIU units, select File Save from the menu.
5

Export Remote Inventory Data for Backup


1. Select Export IDF from the menu.
2. Select the destination path in the appearing window, preferably A:\. The file name is
automatically composed of the SalesUniqueName with the extension .idf.
3. Click on the Save button.
4. Put the disk with the backup file of the inventory data to the site specific documentation.

Export Nob_RIU Data


1. Select Export NOB from the menu.
2. A window opens in which you can edit the file name and select the directory in which
the file is saved. By default, the file name is composed of the SalesUniqueName
with the extension .nob. Edit the file name and select the source directory or confirm
the default name and directory by clicking on the Save button.
3. The nob_RIU data are exported to the NOB file. The selected destination path of this
file is displayed in an attention window. Confirm by clicking on the OK button.
4. A question window is displayed: Create BTS_NRIU for download?. Confirm by
clicking on the Yes button. An attention window is displayed that informs you on the
destination path and file name to which the BTS_NRIU download is saved. Confirm
by clicking on the OK button.

Download the NOB File to the BTSE


Change to the LMT Evolution.
b BSS
NE Btsexs BR<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
REMINV
REMINV:<no>
DNLIDFD REMINV

76

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

SRCDIR=<source directory>
Additional Information: SRCDIR: enter the source directory in which the exported
NOB file was saved.
8

Finish Remote Inventory Data Creation


Return to ...

h ......... the corresponding COBA fault clearance procedure


END

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

77

Fault Clearance Procedures

3.20

MMN:BTSE BS-288

Remote Inventory Data Restoration


After the COBA replacement, the remote inventory data, which was stored on the
removed COBA, must be restored.
Flow Chart:
The following flow chart gives an overview of the fault clearance procedure. Comments
on the steps are included behind the flow chart, followed by the steps in detail.

78

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

Steps:
1*

Manual nob_RIUs
creation

3*

IDF backup file


availability?

IDF files from TAC


safe to LMT PC

4*

On-site IDF file


copy to LMT PC

Initial situation: BTSE


with ob_RIU data only

IDF file
(nob_RIUs/
ob_RIUs of former
configuation)

IDF Evolution

5*

6*

IDF evolution
start
IDF Evolution

IDF file
open
Procedure
Remote Inventory Data
Creation

IDF Evolution

7*

nob_RIU data export


(NOB file)
(nob_RIUs)
LMT

8*

NOB file download


to BTSE

NOB file
(nob_RIUs)

Result: BTSE with


ob/nob_RIU data
continue below ...

Figure 13

A50016-G5100-A185-01-7620

Flow Chart Remote Inventory Data Restoration, Part I

Id:0900d8058008d52b

79

Fault Clearance Procedures

MMN:BTSE BS-288

... continued from above

LMT

9*

10*

11*

IDT file

IDT File upload


from BTSE

(nob_RIUs/
up-to-date
ob_RIUs)

IDF Evolution

IDT file
open

IDF Evolution

IDF file

IDF file generation for backup

nob_RIUs/
up-to-date
ob_RIUs
12

Figure 14

Return to COBA replacement procedure

Flow Chart Remote Inventory Data Restoration, Part II

Step
1-4

*Comments
The inventory data of the BTSE modules were stored on the removed COBA.
After the COBA replacement, the data of the ob_RIU (which have their inventory data on board) is automatically loaded into the new COBA, but the data
of the nob_RIU must be restored.
Usually, a backup file (IDF file) is available for this purpose, which is stored on
site with the site specific documentation. If there is no backup file, the data can
be extracted from the BSC via TAC, or must be entered by hand.

5-8

Table 7

80

To load the nob_RIU data into the BTSE, it is necessary to export the nob_RIU
data from the IDF file into a NOB file and to download this file into the BTSE.
Comments on Flow Chart Remote Inventory Data Restoration

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

Step
9-11

Table 7

*Comments
After the NOB file download, the BTSE stores its complete Remote Inventory
Data as IDT file on the new COBA. To create an up-to-date backup file, the
IDT file should now be uploaded to the LMT PC and exported into an IDF file.
This IDF file should be stored on site with the site specific documentation. It
contains, for example, the data of the new ob_RIU module COBA.
Comments on Flow Chart Remote Inventory Data Restoration

Restore the Remote Inventory Data


A) Inventory data restore via backup file stored on site?
........... 4
B) Inventory data restore via extraction of the IDF data from the BSC IDF?
........... 3
C) Inventory data restore by hand?
........... 2

Create all nob_RIUs by Hand


For the creation of the inventory data for all nob_RIUs, go to ...

h procedure Remote Inventory Data Creation


Afterwards, return to ...

h ......... the corresponding COBA replacement procedure


3

Extract BTSE Data from BSC IDF


Call TAC to have the data extracted from the BSC IDF. Safe the file to the hard disk of
the LMT PC e.g., C:\...\LMT<version>\IDF\*.idf.
Afterwards, continue with step

h ......... 5
4

Copy IDF File to LMT PC


Copy the IDF backup file from the disk to the hard disk of the LMT PC e.g.,
C:\...\LMT<version>\IDF\*.idf.

Start IDF Evolution


To start the IDF Evolution select IDF GSM IDF Editor from the Windows program
menu.

Open IDF File


1. Select File Open from the menu.

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

81

Fault Clearance Procedures

MMN:BTSE BS-288

2. Select the uploaded file from the list in the appearing window; e.g.: C:...\LMT<version>\Idf\Upload\BTSE.idt.
3. Double-click on the file name or click on the Open button.
7

Export Nob_RIU Data


1. Select Export NOB from the menu.
2. A window opens in which you can edit the file name and select the directory in which
the file is saved. By default, the file name is composed of the SalesUniqueName
with the extension .nob. Edit the file name and select the source directory or confirm
the default name and directory by clicking on the Save button.
3. The nob_RIU data are exported into a NOB file. The selected destination path of this
file is displayed in an attention window. Confirm by clicking on the OK button.
4. A question window is displayed: Create BTS_NRIU for download? Confirm by
clicking on the Yes button. An attention window is displayed that informs you on the
destination path and file name to which the BTS_NRIU download is saved. Confirm
by clicking on the OK button.

Download the NOB File to the BTSE


Change to the LMT Evolution.
b BSS
NE Btsexs BR<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
REMINV
REMINV:<no>
DNLIDFD REMINV
SRCDIR=<source directory>
Additional Information: SRCDIR: enter the source directory in which the exported
NOB file was saved.

Upload IDT File from the BTSE


b BSS
NE Btsexs BR<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
REMINV
REMINV:<no>
UPLLIDF REMINV
(DESTDIR=<path>)
(FILE=<file name>)

82

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

OVERWRITE=<YES>
Additional Information: The attributes DESTDIR and FILE are optional. If no
special path or file name is entered, the file is uploaded to the default directory of the
IDF Evolution. Select the attribute OVERWRITE=<yes> to overwrite any former
version of the uploaded IDT file.
10

Open IDT File


1. Change to the IDF Evolution main window.
2. Select File Open from the menu.
3. Select the uploaded file from the list in the appearing window; e.g.: C:...\LMT<version>\Idf\Upload\BTSE.idt.
4. Double-click on the file name or click on the Open button.

11

Export Remote Inventory Data for Backup


1. Select Export IDF from the menu.
2. Select the destination path in the appearing window, preferably A:\. The file name is
automatically composed of the SalesUniqueName with the extension .idf.
3. Click on the Save button.
4. Put the disk with the backup file of the inventory data to the site specific documentation.

12

Finish Remote Inventory Data Creation


Return to ...

h ......... the corresponding COBA fault clearance procedure


END

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

83

Fault Clearance Procedures

3.21

MMN:BTSE BS-288

Remote Inventory Data Update


After the replacement of a nob_RIU component, the remote inventory data and the
backup copy must be updated.
Flow Chart:
The following flow chart gives an overview of the fault clearance procedure. Comments
on the steps are included behind the flow chart, followed by the steps in detail.

84

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

Steps:

Fault clearance
procedure finish
LMT

1*

IDT file

IDT file upload


from BTSE

(ob_RIUs/ old
nob_RIUs)

IDF Evolution

2*

IDF evolution
start

Initial situation:
BTSE with old
nob_RIU data

IDF Evolution

3*

IDT file
open
IDF Evolution

4*
nob_RIU update

IDF Evolution

5*

IDF file
(up-to-date
ob/nob_RIUs)

IDF file generation


for backup
IDF Evolution

6*

nob_RIU data export (NOB file)


LMT

7*

NOB file

NOB file download


to BTSE

(up-to-date
nob_RIUs)
8*
Result: BTSE with up-todate ob/nob_RIU data

Figure 15

A50016-G5100-A185-01-7620

Fault clearance
procedure finish

Flow Chart Remote Inventory Data Update

Id:0900d8058008d52b

85

Fault Clearance Procedures

MMN:BTSE BS-288

Step

*Comments

The remote inventory data that is stored in the BTSE as IDT file must be
uploaded to the LMT PC. This file only contains the remote inventory data of
the BTSE modules (ob_RIU/nob_RIU). After the replacement of a nob_RIU
module, the nob_RIU data must be updated.

2-4

The remote inventory data of the new nob_RIU module has to be entered into
the IDT file via the software IDF Evolution.

An IDF file that contains the up-to-date remote inventory data of all installed
modules must be created from the IDT file for backup purposes.

6-7

To load the up-to-date nob_RIU data into the BTSE, it is necessary to export
the nob_RIU data from the IDT file into a NOB file and to download this file into
the BTSE.

Table 8
1

Comments on Flow Chart Remote Inventory Data Update

Upload IDT File from the BTSE


b BSS
NE Btsexs BR<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
REMINV
REMINV:<no>
UPLLIDF REMINV
(DESTDIR=<path>)
(FILE=<file name>)
OVERWRITE=<YES>
Additional Information: The attributes DESTDIR and FILE are optional. If no
special path or file name is entered, the file is uploaded to the default directory of the
IDF Evolution. Select the attribute OVERWRITE=<yes> to overwrite any former
version of the uploaded IDT file.

Start IDF Evolution


To start the IDF Evolution select IDF GSM IDF Editor from the Windows program
menu.

Open IDT File


1. Select File Open from the menu.
2. Select the uploaded file from the list in the appearing window; e.g.: C:...\LMT<version>\Idf\Upload\BTSE.idt.
3. Double-click on the file name or click on the Open button.

86

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Fault Clearance Procedures

Update the Remote Inventory Data of the New nob_RIU Unit


The records of the nob-RIUs are shown in bold letters. Only these records are editable.
1. Click the right mouse button on the I-Record of the unit you need to update.
2. Click on the appearing Edit button.
3. A pop-up window opens in which the data can be entered manually or automatically
via the 2D-Code Reader. Key in the data, or click on the Scan button to use the 2DCode Reader.
4. If required, select the serial port of the 2D-Code Reader in the appearing window.
5. To start the scanning process, press the button on the 2D-Code Reader. The data
will be inserted into the corresponding fields.
6. Confirm the data by clicking on the OK button.
7. Select File Save from the menu.

Export Remote Inventory Data for Backup


1. Select Export IDF from the menu.
2. Select the destination path in the appearing window, preferably A:\. The file name is
automatically composed of the SalesUniqueName with the extension .idf.
3. Click on the Save button.
4. Put the disk with the backup file of the inventory data to the site specific documentation.

Export Nob_RIU Data


1. Select Export NOB from the menu.
2. A window opens in which you can edit the file name and select the directory in which
the file is saved. By default, the file name is composed of the SalesUniqueName
with the extension .nob. Edit the file name and select the source directory or confirm
the default name and directory by clicking on the Save button.
3. The nob_RIU data are exported to the NOB file. The selected destination path of this
file is displayed in an attention window. Confirm by clicking on the OK button.
4. A question window is displayed: Create BTS_NRIU for download? Confirm by
clicking on the Yes button. An attention window is displayed that informs you on the
destination path and file name to which the BTS_NRIU download is saved. Confirm
by clicking on the OK button.

Download the NOB File to the BTSE


Change to the LMT Evolution.
b BSS
NE Btsexs BR<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
REMINV
REMINV:<no>
DNLIDFD REMINV

A50016-G5100-A185-01-7620

Id:0900d8058008d52b

87

Fault Clearance Procedures

MMN:BTSE BS-288

SRCDIR=<source directory>
Additional Information: SRCDIR: enter the source directory in which the exported
NOB file was saved.
8

Finish Remote Inventory Data Creation


Return to ...

h .......... the corresponding COBA fault clearance procedure


END

88

Id:0900d8058008d52b

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Tables, Lists and Figures

4 Tables, Lists and Figures


4.1

Hardware Architecture and Components (Modules,


Frames and Racks etc.)
For detailed information on the system hardware, see the technical description
TED:GERAN Common and the technical description (TED) for your BTSE type.
For detailed information on hardware components, see the respective hardware manual
HW:BTSE Modules, HW:BTSE Frames/Panels, HW:BTSE Racks/Shelters.

A50016-G5100-A185-01-7620

Id:0900d805800a6e45

89

Tables, Lists and Figures

4.2

MMN:BTSE BS-288

Front View of the BS-288 Rack and Mounting Positions


Emi-Panel

ACTC
FAN0

*)CU *)CU
3
2

FAN1

HMO name:
FANP: 01
*) HMO name: CU
05; module
name: GCU or
ECU;
Or module name:
FlexCU 05: HMO
name: FCUMAIN,
FCUTR

BCOM
12:6

Additional HMOs:
BPORT 03
ENVABTSE 011
LAPDLE 07
XCONNECT 02

D
C

*)CU
0

Figure 16

90

C
O
B
*)CU
A
1 0

P
A
N
E
L

*)CU
4

*)CU
5

BS-288 with BCOM 12:6 (front view)

Id:0900d805800a6e45

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Tables, Lists and Figures

Emi-Panel

ACTC
FAN0

FAN1

HMO name:
FANP: 01
*) HMO name: CU 1, 3,
5; module name:
GCU or ECU

**)CU *)CU
3
2

HMO name: CU 0, 2, 4;
module name: GCU or
ECU;
Or module name:
FlexCU: HMO name:
FCUMAIN, FCUTR;

BCOM
6:6

D
C

**)CU
0

Figure 17

A50016-G5100-A185-01-7620

C
O
B
*)CU
A
1 0

P
A
N
E
L

**)CU
4

*)CU
5

Additional HMOs:
BPORT 03
ENVABTSE 011
LAPDLE 07
XCONNECT 02

BS-288 with BCOM 6:6 (front view)

Id:0900d805800a6e45

91

Appendix

MMN:BTSE BS-288

5 Appendix
5.1

HW/SW Compatibility during Download from LMT/BSC


This feature allows a compatibility check of the swLoad and the current HW situation of
the BTSE, there by preventing a download of a swLoad which will not run on the specific
BTSE.
This check is done by means of a compatibility matrix - the Version Attachment Mechanism (VAM) file which is the second file of the swLoad. The check is carried out when
this VAM file is received in the BTSE. Upon a negative result, the download of the
swImages is stopped.
swLoad: GSM notation for a complete SW package containing all the load SW of a
network element.
swImage: GSM notation for the load SW package for a single module inside a network
element.
VAM file: represents the context between the swImages and the HW-SW compatibility.

92

Id:0900d8058007e3d1

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Appendix

Output in Case of a Failed VAM Check (after the BTS received the VAM file):
JOB: <no>

PC Time&Date: <time> <date>


NE Time&Date: <time> <date>

USER:

<user>

COMMAND:

DNLALLEXE:SRCPATH=\...\...\... <name>.swl,OVERWRITE=YES

SW RELEASE:

<no>

COMMAND RESULT:

OPERATION FAILED

VAM check failed

END OF OUTPUT FOR JOB <no>

JOB: <no>

PC Time&Date: <time> <date>


NE Time&Date: <time> <date>

USER:

<user>

SW RELEASE:

<no>

COMMAND RESULT:

OPERATION COMPLETED

FAILURE EVENT REPORT

NAME = RACK:0/COBA:0
Event Type = Processing Failure Event
Event Time = <Date> <Time>
Probable Cause = Configuration or Customization Error
Specific Problems = 26676 - Board type not supported
Severity = Warning
Trend Indication = No Change
Notification Identifier = 48
Proposed Repair Action 1 = 189 - Check configuration data
Originator = 3329

A50016-G5100-A185-01-7620

Id:0900d8058007e3d1

93

Appendix

MMN:BTSE BS-288

Additional Words =
Octets 01 to 16: H6264 H6c78 H636d H6d73 H07ac H5a01 H0212 H3b3b
Octets 17 to 30: Hc304 Hffff Hffff Hffff Hffff Hffff Hffff
Software Version = <SW Version>

END OF OUTPUT FOR JOB <no>

5.2

State/Status Attributes of BTSE Managed Objects


The following state/status attributes are used for BTSE MOs:

State/Status Attribute

State/Status

Administrative State
(AST)

Explanation
This state informs whether or not the MO is permitted to
provide service.

Locked

The related MO is not permitted to provide service, but is


addressable for maintenance tasks and fully operable (it can,
for example, be tested). This state can be brought about via
the LMT Lock command.
Note: at the BTSE, only HMOs can be locked/unlocked.

Shutting Down

The MO is currently shutting down, i.e. ongoing calls are not


interrupted, but no new calls are permitted.
This state cannot be brought about via LMT at the BTSE.

Unlocked

Service is permitted.
This state can be brought about via the LMT Unlock
command.
Note: at the BTSE, only HMOs can be locked/unlocked.

Operational State
(OST)

This state informs whether or not the MO is able to provide


service.
Enabled (ena)

The MO is able to provide service.


(Exception: the MOs RACK, BTSE and ENVABTSE are
always Enabled, even if, for example, a service rack is not
installed.)

Disabled (dis)
Alarm Status (ALS)

Table 9

94

The MO is not able to provide service.


This status reports the severity level of pending alarms. If
more than one alarm is pending, the level of the alarm with
the highest severity level is reported.

Critical

At least one pending alarm with severity level critical (see


5.3.3.1).

Major

At least one pending alarm with severity level major (see


5.3.3.2).

State/Status Attributes of BTSE MOs

Id:0900d8058007e3d1

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Appendix

State/Status Attribute

State/Status

Explanation

Minor

At least one pending alarm with severity level minor (see


5.3.3.3).

Cleared

No pending alarms.

Availability Status

This status reports details on AST or OST.


In Test (tst)

Intrusive test under progress.

Failed (fail)

MO is defective/not operable.

Power Off (pof)

The power of the MO is switched off.

Degraded (deg)

The service is degraded.

Off Line (ofl)

The creation of the MO is in progress.

Dependency (Dep)

The MO cannot operate because of another MO on which it


depends.

Not Installed (noi)

The MO is not installed.

Null Value (nul)

Value after the creation of an MO (+Disabled/Locked).


Certain processes still in progress (e.g. alignment).
MO TRX: transient failure of a HMO.

Procedural Status
(PRS)

This status reports whether or not the MO performs an initialization procedure.


Initializing (ini)

Initialization is in progress.

Null Value (nul)

No initialization

Standby Status (STS)

Table 9

This status reports information on redundant MOs.


Null

This value is used in combination with OST Disabled.

Providing Service

This value is used in combination with OST Enabled/AST


Unlocked. The MO provides service.

Cold Standby

The MO is able to provide service but it is either not active or


it is locked.

State/Status Attributes of BTSE MOs

5.3

BTSE Alarm Information


On each BTSE module a local alarm queue for 30 alarms is available. Every 100 ms
there is one alarm sent to the COBA. If currently more alarms are generated than 10 per
second, the queue gets full and a reset is performed on the module. After the module is
restarted, a corresponding Failure Event Report is sent.
The following information is forwarded from the BTSE to the BSC:
1. Managed object class
2. Managed object instance
3. Event information
Probable cause
Severity (alarm level)
Trend indication
Threshold information

A50016-G5100-A185-01-7620

Id:0900d8058007e3d1

95

Appendix

MMN:BTSE BS-288

5.3.1

Additional information

Probable Cause
Identifies the probable cause of the fault or error. The probable cause is taken out of a
predefined set of values, defined for each alarm type.

5.3.2

Event Types
Errors are classified in the following categories (so called event types):

5.3.2.1

Equipment Errors
Detected by hardware check or application software

5.3.2.2

Processing Errors
Detected by on-line software checks and audits

5.3.2.3

Communication Errors
Detected by protocols

5.3.2.4

Quality of Service Errors


They depend on:
Traffic overload conditions
Excessive instability of the hardware
Loss of hardware components

5.3.2.5

Environmental Errors
These errors depend on environmental conditions e.g., temperature, door open or
smoke.
In general, these faults are signalled to the ACT module.

5.3.3
5.3.3.1

Severity Levels
Critical
The critical severity level indicates that a service affecting condition has occurred and
an immediate corrective action is required. Such a severity can be reported for example,
when an equipment related managed object (MO) goes totally out of service.

5.3.3.2

Major
The major severity level indicates that a service affecting condition has developed and
an urgent corrective action is required. Such a severity can be reported for example,
when there is a severe degradation in the capability of the equipment related managed
object (MO).

96

Id:0900d8058007e3d1

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

5.3.3.3

Appendix

Minor
The minor severity level indicates the existence of a non-service affecting fault condition
and that corrective action should be taken in order to prevent a more serious (for
example, service affecting) fault. Such a severity can be reported, for example, when
the detected alarm condition is not currently degrading the capacity of the equipment
related managed objects (MO).

5.3.3.4

Warning
The warning severity level indicates the detection of a potential or impending service
affecting fault, before any significant effects have been felt. Actions should be taken to
further diagnose (if necessary) and correct the problem in order to prevent it from
becoming a fault causing more severe interference to services.

5.3.4

Trend Indication
This parameter specifies the current severity trend of the equipment related managed
object.

5.3.5

Immediate Defence Action


The immediate defence action is performed by the BTSE software to try and solve the
problem. If there is no corresponding defense action, NA is reported.

5.3.6

Threshold Information
Actual value:

lower threshold (if any)


upper threshold (if any)

5.3.7

Additional Information
A fixed length buffer contains additional information concerning the detected fault/error.
This information is totally dependent on errors.

5.3.8

Proposed Repair Action


Suggested repair actions. Consult also the corresponding user manual.

5.3.9

Error Description
Detailed description of the error and its probable cause.

A50016-G5100-A185-01-7620

Id:0900d8058007e3d1

97

Appendix

MMN:BTSE BS-288

5.4
5.4.1

Fault Messages
Fault Messages at the Radio Commander

Figure 18

5.4.2

Fault Messages at the Radio Commander

Fault Messages at the LMT


JOB: <no>
PC Time&Date:<Time> <Date>
NE Time&Date:<Time> <Date>
USER: <Name>
SW RELEASE: <Release>
COMMAND RSULT: Operation successful
FAILURE EVENT REPORT:NAME = <modul>:<no>Event Type = Communication Failure
Event
Event Time = <Time> <Date>Probable Cause = Transmitter Error
Specivic Problems = 10270 - Loss of signal
Severity = Major
Trend Indication = More Severe
Notification Identifier = 322
Proposed Repair Actions_1 = 185 - Collect infor for assistance
Proposed Repair Actions_2 = 181 - Test the addressed card
Originator = 1281
Additional Words =
Octets 01 to 16: H6d63 H6e61, H6c72, H6d66 H0746 H0106 H1a19
Octets 17 to 30: H'ffff H'ffff H'ffff H'ffff H'ffff
Software Version = <Version>
END OF OUTPUT FOR JOB <no>

98

Id:0900d8058007e3d1

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

5.5
5.5.1

Appendix

BTSE Components
BTSE Components Overview
For a system overview of all BTSE components (modules, frames, racks and managed
objects), refer to chapter 4 Tables, Lists and Figures.

5.5.2
5.5.2.1

Numbering of BTSE Components


General Rules
Relative Numbering
In general, the relative numbering (i.e. logical numbering) of the units starts with the
figure zero (0). That means that the first of a set of devices, modules or racks / shelters
is assigned the number 0; the next one the number 1 in sequence, etc.
With the exception of Abis-lines, the numbering starts with 1, 2, 3 ...

5.5.2.2

Specific Rules
Rack Numbering
The first rack in a BTSE is called Base Rack and is assigned the number 0. If additional
space is required for transceivers and combining equipment, the base rack is extended
by an Extension Rack.
Slot Numbering inside the Racks or Shelters
In a rack slot numbers are defined for the accommodation of CUs. There are 6 CU slots
(0...5).

5.5.3

Remote Inventory Data


The function Remote Inventory of the Siemens Base station System performs electronic, non-volatile storing of the complete, individual product identification data (PID) of
each inventoried object.
Modules that have inventory data on board are called ob_RIU (on-board Remote Inventory Units). The PID of these ob_RIUs is automatically loaded to the inventory data file
(IDF).
In order to include inventory data of objects without a non volatile storage (e. g. frames,
racks, OEM components), the data of these so called nob_RIUs (not on-board Remote
Inventory Units) are entered into an inventory data table (IDT) via the LMT and the offline
tool IDF Evolution. These data is stored on the COBA as a nob_RIU file (NOB). Supplemented with a footer and header, the IDT can be exported and stored as an inventory
data file (IDF) for backup purposes.
In the event of the replacement of a nob_RIU component, the NOB file must be updated
manually and the backup IDF-file with the inventory data, which is stored on site, must
be updated as well.
In case of a COBA replacement, the inventory data that was stored on the removed
COBA must be rebuilt. This can be done by using the backup IDF-file.

A50016-G5100-A185-01-7620

Id:0900d8058007e3d1

99

Appendix

MMN:BTSE BS-288

For ob-RIU replacements the inventory data file is updated automatically.


The following list shows all nob_RIU components:
Functional Address

Range of n

Functional Address Type

ACT-C

ACTC3V1

BCOM

BCOMPG

DCP-m/n

DCP:RXSV1

FACOM-m/n

F:ACOMCUXS

FAN-m/n

0...1

0...1

FAN

FCORECU-m/n

F:CORECU

FFAN-m/n

F:FAN

MSUAC-m/n

MSUAC

MSUDC-m/n

MSU:DC

OVPT-m/n

M:OVPT

ABISCON-m/n

M:ABISCONV1

RACK-m/n

0
0

R:BS60XSV1

Table 10

100

Range of m

List of nob_RIUs

Id:0900d8058007e3d1

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

5.6
5.6.1

Appendix

Diagnostics / Test
General
In general the diagnosis subsystem is for testing the functionality of BTSE HW resources
to detect and localize hardware faults. The verification of the functionality of a new or
replaced hardware unit before operation is an especially important feature of diagnosis.
The task of diagnosis is to perform tests for the BTS processor modules, initiated from
the LMT
The successful replacement of analog modules can only be verified by reactivating the
BTSE.

5.6.2

Requirements for Starting the BTSE Module Test


The module test is controlled by the LMT; therefore the LMT must be plugged in at the
plug position and the user logged on. The principle sequence is as follows:
change the administrative state from unlocked to locked
start the module test
change the administrative state from locked to unlocked
The requisite command sequence is as follows:

5.6.2.1

Lock BTS Site Manager (only relevant for some modules)


BSS
NE Btsexs Br<no>:<NE id>
BSS-FUNCTIONAL
BTSM
BTSM:<no>
LOCKREQUEST BTSM

5.6.2.2

Change BTSE from Phase 3 to Phase 2 (only relevant for some


modules)
BSS
NE Btsexs Br<no>:<NE id>
BSS-FUNCTIONAL
BTSM
BTSM:<no>
DISCBSC BTSM

5.6.2.3

Lock Suspected Module (all modules)


BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS

A50016-G5100-A185-01-7620

Id:0900d8058007e3d1

101

Appendix

MMN:BTSE BS-288

BTSEXS:<no>
RACK
RACK:<no>
<module>
<module>:<no>
LOCK <module>

5.6.2.4

Run the Test for the Replaced Module


BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK:<no>
<module>
<module>:<no>
PERFTEST <module>
Explanation of the test parameters:
Refer to the manual CML:BS-240XS/288.

102

Id:0900d8058007e3d1

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

Appendix

System Response
Perftest <MO>:NAME=RACK:<no>/ <MO>:<no>;
<date> <time> Command
============================================
JOB: <no>
PC Time&Date = <time> <date>
NE Time&Date = <time> <date>
USER NAME: <user>
COMMAND: Perftest <MO>:NAME=RACK:<no>/ <MO>:<no>;
SW RELEASE: = <no>
COMMAND RESULT: OPERATION COMPLETED
PERFTEST ACK BTSEXS :

name = BTSEXS:<no>
MOT = RACK:<no>/<MO>:<no>
t0 = BTSETEST: <no>
END OF OUTPUT FOR JOB <no>

Example for Test Report


JOB: <no>
PC Time&Date = <time> <date>
NE Time&Date = <time> <date>
USER NAME: <user>
SW RELEASE: <no>
COMMAND RESULT: <command result>

Test Report:
name = BTSETEST:<no>
test Outcome = <test outcome> (see below)
testTermination = Normal
MOT = RACK:<no>/<MO>:<no>
executedPhases
phaseId = PreliminaryTests<MO>
phaseId = CheckAlarmStatus<MO>
phaseId = EndTest<MO>

A50016-G5100-A185-01-7620

Id:0900d8058007e3d1

103

Appendix

MMN:BTSE BS-288

END OF OUTPUT FOR JOB <no>


followed by some more information in case of Test Outcome = Fail like:
Proposed Repair Action
Card 1: ....
Card 2: ....
Card 3: ....
Card 4: ....
Failed Phases = <no>
Additional Words
Some tests have been skipped
Failed Phases: Start_Phase
Other Information = H01 H00 H00 H00 H00 H00 H00 H00

5.6.2.5

Unlock Suspected Module (all modules)


BSS
NE Btsexs Br<no>:<NE id>
BSS-EQUIPMENT
BTSEXS
BTSEXS:<no>
RACK
RACK:<no>
<module>
<module>:<no>
UNLOCK <module>

5.6.2.6

Change BTSE from Phase 2 to Phase 3 (only relevant for some


modules)
BSS
NE Btsexs Br<no>:<NE id>
BSS-FUNCTIONAL
BTSM
BTSM:<no>
CONNBSC BTSM

104

Id:0900d8058007e3d1

A50016-G5100-A185-01-7620

MMN:BTSE BS-288

5.6.2.7

Appendix

Unlock BTS Site Manager (only relevant for some modules)


BSS
NE Btsexs Br<no>:<NE id>
BSS-FUNCTIONAL
BTSM
BTSM:<no>
UNLOCKREQUEST BTSM

A50016-G5100-A185-01-7620

Id:0900d8058007e3d1

105