bs82mt

Maintenance

Base Transceiver Station Equipment

MMN:BTSE BS-82 eMicro

A30808-X3247-L291-3-7620

2 A30808-X3247-L291-3-7620

MMN:BTSE BS-82 eMicro MaintenanceBase Transceiver Station Equipment

f 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 mustcomply with the applicable safety standards.Hazardous voltages are present at the AC power supply lines in this electrical equipment. Some components mayalso have high operating temperatures.Failure to observe and follow all installation and safety instructions can result in serious personal injuryor 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 angeschlossenenGeräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.In diesen Anlagen stehen die Netzversorgungsleitungen unter gefährlicher Spannung. Einige Komponentenkönnen auch eine hohe Betriebstemperatur aufweisen.Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Körperverletzungen oderSachschäden führen.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 tableA30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for aClass 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 isoperated in a commercial environment.This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accor-dance with the relevant standards referenced in the manual “Guide to Documentation”, may cause harmful inter-ference to radio communications.For system installations it is strictly required to choose all installation sites according to national and local require-ments 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 electromagneticfield / 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 purposescould violate the rights of their owners.

Copyright (C) Siemens AG 2004.

Issued by the Information and Communication Mobile GroupHofmannstraße 51D-81359 München

Technical modifications possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

A30808-X3247-L291-3-7620 3

MaintenanceBase Transceiver Station Equipment


Reason for UpdateSummary:

Third Edition for Release BR 7.0

Details:

Chapter/Section Reason for Update

3.15 Remote Inventory Data

Update

Note inserted

Issue HistoryIssue Date of issue Reason for Update

1 07/2003 First Edition for New Release BR 7.0

2 12/2003 Second Edition for Release BR 7.0

3 08/2004 Third Edition for Release BR 7.0

4 A30808-X3247-L291-3-7620


This document consists of a total of 111 pages. All pages are issue 3.

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.1 Structure of the Maintenance Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Used Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.3 Fault Clearance Principle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.4 Fault Clearance Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.5 Module Replacement Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.5.1 ESD Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.5.2 Avoiding the Loss of Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.5.3 Removing and Inserting Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.5.4 Add-on Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.6 Preparatory Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.6.1 Open/Close Shelter Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.6.2 Shelter Additional Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.6.2.1 MK:AIRADAPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.6.2.2 MK:AIRGRILL and MK:AIRGRILLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191.6.2.3 MK:AIRBAFFLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.6.2.4 MK:CAPLOCK (Mounting Kit for CAP LOCK) . . . . . . . . . . . . . . . . . . . . . . . 201.6.2.5 MK:SERVLOCK (Mounting Kit for SERV LOCK) . . . . . . . . . . . . . . . . . . . . . 201.6.3 Open/Close Shelter Door . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.6.4 Remove/Mount Backplane Cover Plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2 Tasklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3 Fault Clearance Procedures for Modules and Interfaces. . . . . . . . . . . . . . . 243.1 Abis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2 ACDCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.3 ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.4 A:DUAMCOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.5 BATTERYM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.6 BPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.7 COBAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473.8 DCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.9 DILNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.10 DULNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.11 DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.12 FANM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723.13 LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.14 PCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.15 Remote Inventory Data (Update) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.16 TX/RX Path (e.g., VSWR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4 Tables, lists and figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884.1 Hardware Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894.2 Detailed Information on Hardware Components

(Modules, Frames and Racks) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924.3 Right View of the eMicroBTS Racks and Mounting Positions . . . . . . . . . . . 93

A30808-X3247-L291-3-7620 5



4.4 Connection field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944.5 TX/RX Paths of Some Configuration Examples . . . . . . . . . . . . . . . . . . . . . 95

5 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985.1 HW/SW Compatibility during Download from LMT/BSC. . . . . . . . . . . . . . . 985.2 Safeguarding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995.3 State/Status Attributes of BTSE Managed Objects. . . . . . . . . . . . . . . . . . . 995.4 BTSE Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015.4.1 Event Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015.4.2 Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.4.2.1 Equipment Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.4.2.2 Processing Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.4.2.3 Communication Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.4.2.4 Quality of Service Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.4.2.5 Environmental Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.4.3 Severity Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.4.3.1 Critical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.4.3.2 Major . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.4.3.3 Minor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.4.3.4 Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.4.4 Trend Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.4.5 Immediate Defence Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.4.6 Threshold Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.4.7 Proposed Repair Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.4.8 Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.4.9 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1035.5 Fault Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045.5.1 Fault Messages at the Radio Commander . . . . . . . . . . . . . . . . . . . . . . . . 1045.5.2 Fault Messages at the LMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055.6 BTSE Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055.6.1 BTSE Components Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055.6.2 Numbering of BTSE Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055.6.2.1 General Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055.6.2.2 Specific Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065.6.3 Remote Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065.7 Diagnostics / Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075.7.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075.7.2 Requirements for Starting the BTSE Module Test . . . . . . . . . . . . . . . . . . 1085.7.2.1 Lock BTS Site Manager (only valid for some modules - see REP:XXX) . 1085.7.2.2 Change BTSE from Phase 3 to Phase 2 (only valid for some modules) . 1085.7.2.3 Lock Suspected Module (all modules) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085.7.2.4 Run Test for Replaced Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085.7.2.5 Unlock Suspected Module (all Modules). . . . . . . . . . . . . . . . . . . . . . . . . . 110

6 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

6 A30808-X3247-L291-3-7620


IllustrationsFig. 1.1 Structure of the MMN:BTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Fig. 1.2 Used Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Fig. 1.3 Fault Clearance Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Fig. 1.4 ESD Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Fig. 1.5 Module Fastening Variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Fig. 1.6 Location of the Plug-in Module Code Keys. . . . . . . . . . . . . . . . . . . . . . . 16

Fig. 1.7 Location of the Code Key Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Fig. 1.8 Example for replacement of add-on modules . . . . . . . . . . . . . . . . . . . . . 17

Fig. 1.9 MK:AIRADPT in an advertising pillar . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Fig. 3.1 Replace FANM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Fig. 4.1 eMicro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Fig. 4.2 BS-82 eMicro (view from right side) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Fig. 4.3 Functional blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Fig. 4.4 BS-82 eMicro base configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Fig. 4.5 Master Cabinet with add-on modules . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Fig. 4.6 Connection field (view from above). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Fig. 4.7 TX/RX Paths of Configuration with A:DUAMCO . . . . . . . . . . . . . . . . . . . 96

Fig. 5.1 Fault Messages at the Radio Commander . . . . . . . . . . . . . . . . . . . . . . 104

A30808-X3247-L291-3-7620 7



TablesTab. 4.1 Failure Causes in the TX/RX Path, Configuration with A:DUAMCO . . . 97

Tab. 5.1 State/Status Attributes of BTSE MOs . . . . . . . . . . . . . . . . . . . . . . . . . 100

Tab. 5.2 Shelter Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Tab. 5.3 List of nob_RIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

8 A30808-X3247-L291-3-7620


1 Introduction

1.1 Structure of the Maintenance Manual

The following diagram gives an overview of the structure of this manual and the purposeof its chapters.

Fig. 1.1 Structure of the MMN:BTSE

Chapter 1

Chapter 2

Chapter 3

Chapter 5

Introduction– Basic information on this manual– Basic information on fault clearance– Guidelines– General replacement Instructions– Preparatory work if relevant

Task ListInformation on routine tasks that need to becarried out

Chapter 6 Abbreviations

AppendixBasic required knowledge in more detail,e.g. fault messages

Chapter 4

Fault Clearance Procedures for Modulesand Interfaces– Fault clearance procedures (modules/in-terfaces/MOs in alphabetical order– Concluding procedure “Remote InventoryData Update” that some fault clearance pro-cedures require (if necessary, links are pro-vided to this concluding procedure)

Tables, Lists and Figures– Information on replaceable modules,e.g. LEDs, connectors etc.– Overview of the HW architecture as ad-ditional information

(Important information to make your workefficient and safe)

(Main Part for Fault Clearance Tasks)

(Reference Chapter)

(Reference Chapter)

(General Maintenance)

(Reference Chapter)

Chapter 4

A30808-X3247-L291-3-7620 9



1.2 Used Symbols

The following symbols are used in this manual:

Fig. 1.2 Used Symbols

Reference to another procedure step

Symbol Meaning

ESD (Electrostatically Sensitive Devices) precautions to be taken

Note; important information

Warning; the notes given here are to be followed with care.

b

h

Use LMT to enter commands

☞ Reference to another chapter

Reference to another procedure. Return after finishing.i

i

!Non-observance can lead to personal injury or property damage.

10 A30808-X3247-L291-3-7620


1.3 Fault Clearance Principle

The high system functionality of the Siemens base station system is achieved by meansof system-integrated routine tests. These routine tests continually check the correctfunctioning of the base station subsystems including the BTSEs.

The fault clearance procedures in this manual are based on these routine tests. In mostcases, the results of these routine tests are sufficient to localize the fault and clear it im-mediately at the BTSE.

The modular design of the BTSE allows you to clear a large percentage of faults in thesystem 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 tohigh operational efficiency.

A30808-X3247-L291-3-7620 11



1.4 Fault Clearance Guidelines

The following diagram gives an overview of the fault clearance procedure (detailed de-scription below):

Fig. 1.3 Fault Clearance Overview

Fault Clearance Guidelines

(The numbering refers to the above diagram.)

1. The system integrated routine test detects a fault.

7.

YN

Y

6.AnotherProbableCause?

9. End of Fault Clearance : Faulty Modules are Sent to Repair Depot

Fault and Test Man-agement at theOMC via Radio-

commander

N

1. System Integrated Routine Test Detects a Fault

3.Local Fault

Clearance at theBTSE Neces-

sary?

YN

2. Fault Message Displayed at Radio Commander:Information for example on– probable cause– suspected module(s)/interface(s)– location...

Local FaultClearance at

the BTSE

4. Fault Clearance Proce-dure for the Suspected

Module or Interface

8. CallTAC

5.Fault

ClearanceSuccess-

ful?

Content of this Manual

12 A30808-X3247-L291-3-7620


2. A fault message is displayed at the Radio Commander.

3. The fault and test management at the Operation and Maintenance Center (OMC)must verify whether a local fault clearance at the BTSE is required (see Radio Com-mander documentation).

4. Interpret the fault message and go to the fault clearance procedure of the suspectedmodule or interface in 3 "Fault Clearance Procedures for Modules and Interfaces"(module/interface names as well as LMT terms (MOs) are listed in alphabetical orderif 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 wassuccessful:

– Was the outcome of the hardware test “pass”?

– Are there any relevant pending alarms?

– Do the LEDs signal normal operation?

6. If the fault should still exist and the replaced module was not the fault cause, checkwhether there is another probable cause.

7. If there is another probable cause, reinsert the recently replaced original module andgo to the corresponding fault clearance procedure for the next suspected module orinterface.

8. It should be possible to clear most faults that may occur in the BTSE by following thefault clearance procedures described in this manual. However, if the fault should stillexist after considering all probable causes, contact the Technical Assistance Center(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

iFor the local fault clearance at the BTSE:Make sure that all spare parts that might be required to clear the fault are availableat the site. Note that sometimes more than one module may be suspected of beingdefective. This is particularly important if the failure is located in the TX/RX path(see 3.16 "TX/RX Path (e.g., VSWR)").For general module instructions see also 1.5 "Module Replacement Instructions".

A30808-X3247-L291-3-7620 13



1.5 Module Replacement Instructions

1.5.1 ESD Precautions

Fig. 1.4 ESD Symbol

Many system modules are equipped with electrostatically sensitive components(marked by an ESD symbol). Therefore, ESD precautions must be taken when removingand inserting modules.

During module replacement, personnel must wear a conductive wrist strap to dischargeelectrostatic charging. Before modules, lines or components are touched, this wrist strapmust be connected to the ground potential of the rack/shelter by means of a flexible leadintegrating a 1 MOhm resistor. Note that the conducting parts of the split pin or the clampshould not be touched when inserting/connecting (so as to avoid bypassing the 1 MOhmresistor).

1.5.2 Avoiding the Loss of Calls

If you lock or replace modules in the TX/RX path of the BTSE, calls may be lost. To avoidthe loss of calls, perform the following procedure before you lock or replace a module inthe TX/RX path.

1. Find out the corresponding TRX:To find out which TRX is related to the module, perform the following LMT command:MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACK<Module>GET <Module>NAME=RACK:<no>/<Module>:<no>REQATTL=RELFUNCOBJGet <Module>:Name=BTSE:<no>/<Module>:<no>,REQATTL=RELFUNCOBJIn the system response, the corresponding TRX is listed as related Functional Ob-ject: relatedFuncObjects FMO = BTS:<no>/TRX:<no>.

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:MANAGED-ELEMENTBSS-EQUIPMENTBSS-FUNCTIONAL

iThe following procedure is only relevant if the BTSE is in phase 1 or 2, the BTSE cannotestablish calls.

14 A30808-X3247-L291-3-7620


BTSMBTSTRXGET TRXNAME=BTS:<no>/TRX:<no>REQATTL=OST/ASTGet TRX:Name=BTS:<no>/TRX:<no>,REQATTL=<AST>&<OST>The states of the TRX are listed in the system response.

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. Youcan start with your maintenance task.

4. If the administrativeState = Shutting Down, the shutdown is in progress. Wait a fewminutes and check the state of the TRX again. As soon as the TRX is locked, youcan start with your maintenance task.

5. If the TRX is unlocked/enabled, call the OMC to have the TRX shut down. Wait a fewminutes (about 5 minutes) and check the state of the TRX again. As soon as theTRX is locked, you can start with your maintenance task.

For an overview of the modules in the TX/RX path, refer to 3.16 "TX/RX Path (e.g.,VSWR)".

For a description of the state/status attributes, refer to 5.3 "State/Status Attributes ofBTSE Managed Objects".

A30808-X3247-L291-3-7620 15



1.5.3 Removing and Inserting Modules

There are two variants for fastening modules in the subracks.

Some modules, e.g. the COBA and COSA, are equipped with a lever mechanism at theirfront panel. For removing or inserting these modules, they can be fastened / unfastenedby swivelling the levers at the top and bottom edges of the module.

Other modules are fastened with TORX-headed knurled screws. Replacement of thesemodules requires special tools.

Fig. 1.5 Module Fastening Variants

The TMA (Tower Mounted Amplifier) must be replaced complete with its housing (to bemounted on / unmounted from the mast).The semi-rigid / flexi cables (e.g. on the CU, A:DUAMCO) must be fastened / unfastenedwith a torque spanner (2 sizes).

lever mechanism in open position

push together

lever mechanism in locked position torx screw

iIt must be ensured that the modules are only replaced by modules with the same (or acompatible) HW and SW functional status!Modules with switches or jumpers must be compared with the removed module for safe-ty reasons.The modules should be removed and inserted as fast as possible, in order to preventreading in false module addresses from the CAN BUS.

16 A30808-X3247-L291-3-7620


Handling Modules with Code Keys

To prevent the installation of the modules at incorrect mounting positions, code keys areused on all relevant plug-in modules.

Fig. 1.6 Location of the Plug-in Module Code Keys

In order to avoid module and backplane connector damage when modules are removedfrom / inserted into a base station frame, please observe the following:

In general, after having removed a module from a base station frame, please make surethat the module’s code keys (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 thebackplane.

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 below),

Fig. 1.7 Location of the Code Key Number

– 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 thebackplane.

When inserting a module, do not use excessive pressure.

Code Keys

2

code key number

A30808-X3247-L291-3-7620 17



1.5.4 Add-on Modules

To replace an add-on module all upper add-on modules have to be removed. To removean add on module, the 6 big bolts on the top have to be unfastened. The plates at thebackplane side have to be removed and all cables have to be disconnected.

If the suspected module is not on top of all add-on modules, the upper add-on moduleshave to be removed first, see Fig. 1.8.For the removing of the upper add-on modules, please follow the replacement proce-dures for the module type, but instead of replacing the module, insert the same (not sus-pected) add-on module again.

Fig. 1.8 Example for replacement of add-on modules

iFor the only removed and (after replacement of the suspected module) remounted add-on modules all HMOs have to be locked, unlocked and tested as it is described in thereplacement procedures!

eMicro Master/Extension Cabinet

Add-on module 0

Add-on module 1

Add-on module 2

Suspected module,can be replaced af-ter removing the up-per modules

Add-on module ontop has to be re-moved first

This add-on modulehas to be removedafter removing theadd-on module ontop

18 A30808-X3247-L291-3-7620


1.6 Preparatory Work

1.6.1 Open/Close Shelter Cover

In order to access the modules or the components placed in the cabinets, the cover ofthe shelter has to be removed. The cover is secured by 2 screws at both sides of theshelter. For each add-on module an additional cover part is installed, for getting accessto the cabinet, the cover directly above the cabinet has to be removed.For getting access to the add-on modules, only the cover parts of the add-on moduleand the upper ones have to be removed.

Open Cover

1. release the 2 screws, one on the right side (1) as marked in the figure below and oneon the left side (backplane side)

2. remove the cover by pulling it up (2) from the unit with the released screws, until itcan be removed from the shelter

Close Cover

1. make sure that all cables are securely fitted and properly fed through the cable entryblock

2. shut the cover and press it down

3. screw in the 2 screw sets (1) as marked in the figure above

View of right sideof BS-82

screw 1

1

1

1

22

A30808-X3247-L291-3-7620 19



1.6.2 Shelter Additional Modules

1.6.2.1 MK:AIRADAPTFor the installation in an advertising pillar, an additional part is constructed as a interfaceof the shelter’s air outlet at the fan position to a 150 mm (6”) diameter flexible tube. Thispart provides a 90˚ turn of the air flow and consists of a plastic part with 150 mm (6”)diameter on the tube side an rectangular shape on the shelter side. The grill at the airoutlet of the shelter has to be replaced by a grill having some threads for fixing the plasticpart with screws to the shelter. The modified grill is used for several possibilities and dif-fers for cap and add on. Therefore, it has to be ordered as a separate replacable unit.The 90˚ turn and some mounting material is combined as the kit MK:AIRADAPT.

Fig. 1.9 MK:AIRADPT in an advertising pillar

1.6.2.2 MK:AIRGRILL and MK:AIRGRILLAFor mounting the 90˚ turn or the airbuffle (described below) to the shelter, the grill andits corresponding parts as mounting plate, lamellas etc, are replaced as a complete kit.For the assembly only two screws have to be used. Depending on the position, two dif-ferent kits are provided: MK:AIRGRILL for assembly at the cap (i.e. no add on modulesare present) and MK:AIRGRILLA for assembly at the lowest add on ring of the shelter(i.e. one or more add on’s are present).

20 A30808-X3247-L291-3-7620


1.6.2.3 MK:AIRBAFFLEIn order to protect the fan and the lamella system at the air outlet from strong winds com-ing from the right side of the station, an airbuffle plate with the same size as the air outletis mounted at some cm distance in the front of the air outlet. From wind tests alreadyperformed, the operation is extended to a wider range of external air velocities. Theplate is mounted using the grill described above. The plate and some mounting material(again except the grill) is provided as a kit called MK:AIRBAFFLE.

1.6.2.4 MK:CAPLOCK (Mounting Kit for CAP LOCK)For safety reasons instead of the top cap of the shelter a different shelter cap (MK:CA-PLOCK) can be provided. This shelter element comprises in additional a mechanicallock to prevent removal of add-on modules and the opening of the rack doors.

The MK:CAPLOCK can be always used without modification as long as all add-on mod-ules have 100 mm (4”) height each. If add-on modules with 75 mm (“) height(A:DUAMCO2M modules) are part of a given configuration adapter brackets are neces-sary, which are part of the MK:CAPLOCK. If there are no such add-on modules, thesebrackets are left out.

1.6.2.5 MK:SERVLOCK (Mounting Kit for SERV LOCK)If the access to the OVPT module (M:OVPTM or M:OVPTCOAXM) shall be restricted,the MK:SERVLOCK module can be used. The MK:SERVLOCK consists of the front flapof the OVPT module comprising an additional lock mechanism.

The MK:SERVLOCK can be provided on customer demand and can be as well part ofthe original OVPT or being replaced on a later time. It has no other electrical or mechan-ical characteristics except of the lock mechanism.

1.6.3 Open/Close Shelter Door

Door Opening

1. remove the shelter cover “Open/Close Shelter Cover” on page 18

2. pull the 2 metal clamps at the front side up (1)

1 1

A30808-X3247-L291-3-7620 21



3. open the door to the right (2) and the left (3)

Door Closing

1. bring the two metal clamps at the front side in the uppermost position (1)

2. check that all cables are put in place and are not crushed by closing the door

3. check that the cover plate on the backplane side is mounted correctly and that thecover plate of all modules on the right side are mounted

4. close the doors

5. press the two metal clamps (1) down until they click into place

1.6.4 Remove/Mount Backplane Cover Plate

The cabinet is covered with plates. On the left side one cover plate has to be removedto get access to the backplane module. (On the right side each module is covered byplates. In some cases (COBAM, DCU, ACPSC/DCPSC/ACPSC/U) there is one smallcover plate for the LEDs and plugs, and one plate that covers the rest of the module.)

Open Cover Plate

1. open shelter cover first; see 1.6.1 "Open/Close Shelter Cover"

2. open shelter door; see 1.6.3 "Open/Close Shelter Door"

iTo get access to the backplane, the backplane cover plate has to be removed. The frontplates of the modules can stay during replacing a module.

3 2

22 A30808-X3247-L291-3-7620


Remove Backplane Cover Plate

1. unscrew the 4 screws at the backplane cover plate, the left two screws have to beunscrewed clockwise (1), the right two ones anticlockwise (2)

2. remove the whole backplane cover plate

Mount backplane Cover Plate

1. Place the cover plate over the backplane side

2. Fasten the 4 screws, the right two ones clockwise (1), the left two ones anticlockwise(2)

iBe careful that no cable will be trapped

2

2

1

1

A30808-X3247-L291-3-7620 23



2 Tasklist

24 A30808-X3247-L291-3-7620


3 Fault Clearance Procedures for Modules andInterfaces

A30808-X3247-L291-3-7620 25



3.1 Abis

In some cases, Abis alarms originate from loose or damaged PCM cables on the BTSEAbis Interface (OVPT) and in the corresponding distribution frame (NTPM) in BSC direc-tion. Therefore, the relevant cables must be checked first, according to the following pro-cedure.

Typical Abis alarms concerning cable problems may be indicated by the alarm message- BPORT - Loss of signal

1 Open the BTSE Door

To verify an Abis alarm you have to open the BTSE door and check the LEDs ofthe COBA.

2 Check the LEDs on the COBA

You can recognize an Abis alarm by the red LEDs for Abis 1 and Abis 2 alarmon the COBA.The Abis LEDs indicate the respective Managed Object BPORT, e.g.:

Abis 1 points to the Managed Object BPORT 0,Abis 2 points to the Managed Object BPORT 1.

iBPORT is the logical object that is related to the Abis Interface (OVPT).The Abis lines are also referred to as PCM lines.

26 A30808-X3247-L291-3-7620


3 Optional: Check the Active Alarms with the LMT

If an LMT is available you can check the active Abis alarms: perform the follow-ing command:MANAGED ELEMENTBSS EQUIPMENTBTSEEMGETACTIVEALARMS BTSEEM

All active alarms will be listed in the Message Browser Window.

Typical failure event report for an Abis cable problem:

NAME = BPORT:0Event Type = Communication Failure EventEvent Time = 26/Jan/2001 00:13:03Probable Cause = Transmission ErrorSpecific Problems = 10270 - Loss of signalSeverity = Major

4 Physical Check of the Abis/PCM Cable Connections (OVPT)

Are the PCM lines fastened correctly- in the terminal block of the OVPT and- in the distributing frame (NTPM) in BSC direction? Y h...6

N h...5

Further information on the Abis Interface on the OVPT are documented in theInstallation Manual. ☞ ......(see

IMN:BS-82)

5 Fasten the Abis/PCM Lines Correctly in their Terminals

Does the red LED of the Abis Alarm on the COBA and CUs go off?This may take up to 10 minutes. Y h...9

N h...6

6 Visual Check of the Abis/PCM Lines (OVPT)

Write down the cable colors and their corresponding terminals before discon-necting any cables.

Remove the PCM lines in the terminal blocks (OVPT) and distributing frame inBSC direction) and examine the cables visually for damages. Do you see a bro-ken or corroded cable, or an insulation, that interrupts the contact? Y h...7

N h...8

A30808-X3247-L291-3-7620 27



7 Repair bad Abis/PCM lines

Repair bad PCM lines or exchange the PCM line.Does the red LED of the Abis Alarm on the COBA and CUs go off?This may take up to 10 minutes. Y h...9

N h...8

8 Call TAC

Call TAC to clear the fault.

9 Prepare end of fault clearance

Close the BTSE door.

END

28 A30808-X3247-L291-3-7620


3.2 ACDCP

iOnly trained and qualified personnel (Siemens TAC2 and TAC3) is allowed to carry outthe replacement of the ACPSC/DCPSC units.

A30808-X3247-L291-3-7620 29



3.3 ACT

The ACT is a functionality provided by the ACPSC/DCPSC module which performs cen-tral control and alarm collection functions. The alarms and the digital temperature valueare communicated to the COBA via a CAN bus.

iOnly trained and qualified personnel (Siemens TAC2 and TAC3) is allowed to carry outthe replacement of the ACPSC/DCPSC units.

30 A30808-X3247-L291-3-7620


3.4 A:DUAMCOM

To replace an add-on module, all upper add-on modules have to be removed. The re-movement of the modules that are not suspected, is done similar to the replacement pro-cedures referring to that modules, but the same module is placed on the BTSE again,see 1.5.4 "Add-on Modules".The HMOs have to be handled separately.

1 Interpret the Fault Message ☞ ......(see 5.5.2)

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). ☞ ......(see Fig. 4.4)

2 Interpret the Alarm Type

Is one of the following values listed in the fault message?

- VSWR Alarm- Cable Problem- Transceiver Problem Y h...(see 3.16)

N h...3

iDULNA

DUVSWR

There is one managed object each of this type per moduleand it supplies the low noise amplifying.

There are two managed objects each of this type per moduleand they supply the VSWR logic.

iAll managed objects must be locked before replacement!Modules may be removed while power is on!

iIf you lock or replace modules in the TX/RX path of the BTSE, calls may be lost. To avoidthe loss of calls, please read 1.5.2 "Avoiding the Loss of Calls"

A30808-X3247-L291-3-7620 31



3 Open BTSE

1. open shelter cover; see 1.6.1 "Open/Close Shelter Cover"

2. open left door; see 1.6.3 "Open/Close Shelter Door"

3. open backplane cover; see 1.6.4 "Remove/Mount Backplane Cover Plate"

4 Connect the LMT to the BTSE

Plug the LMT cable into the corresponding socket. ☞ ...... (see HW:BTSEModules, figureOVPTMV1)

Start LOGON - Procedure. ☞ ...... (see OGL:LMT)

5 Lock the objects DULNA and DUVSWR of the suspected A:DUAMCO

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACK<MO>LOCK <MO>

☞ ...... (see OGL:LMT)

LOCK DULNA or DUVSWR:NAME=RACK:<no>/<MO>:<no>;

MO can be DULNA or DUVSWR.

32 A30808-X3247-L291-3-7620


6 System response

followed by several CHANGED STATE EVENT REPORTs which can be exam-ined in the LMT Message Browser window

7 Next DULNA or DUVSWR object if created

Is one of the DULNA or DUVSWR objects not yet locked? Y h...5N h...3

8 Position of A:DUAMCO

Is the suspected module on the top of all add-on modules? Y h...10N h...9

9 Remove upper add-on modules

Please refer to the Nonstandard Maintenance

10 Module replacement

Lock <MO>:NAME=RACK:<no>/<MO>:<no>

<date> <time> Command

============================================

JOB: <no>

PC Time&Date: <time> <date>

NE Time&Date: <time> <date>

USER: <user>

COMMAND: Lock <MO>:NAME=RACK:<no>/<MO>:<no>

SW RELEASE: <no>

COMMAND RESULT: <command result>

LOCK/UNLOCK <MO> ACK:

name = RACK:<no>/<MO>:<no>

administrativeState = Locked

END OF OUTPUT FOR JOB <no>

!All A:DUAMCO modules which are used for one cell must be of the sametype.The ESD precautions must be followed when pulling and inserting a module.Refer to 1.5.1 "ESD Precautions".

A30808-X3247-L291-3-7620 33



1. Open the front plate (optional)

2. Disconnect all Semi rigid (2) and the Antenna cable (3) on backplaneside , see figure below. In certain cases a coupler for power monitoring maybe used. Be careful not to mix up the connections for the input and the mon-itoring output when reconnecting the cables!

3. Remove the 6 bolts (1) on top of A:DUAMCO4M (4:1 comb.) orA:DUAMCO2M (2:1 comb.) respectively, see figure below.

iAll RX semi-rigid SMA connectors are left-screw threads!Pay attention to the different A:DUAMCO-types!

1

1

1

1

1

13

2 2

left-screwthreads!

The connectors for RX path on A:DUAMCO haveto be screwed counterclockwise! It is a left-screwthread.The connectors for TX path on A:DUAMCO haveto be screwed clockwise! It is a right-screwthread.

TXRX

A:DUAMCO2M with different Semi rigid cables

2 RX

2 RX

2 TX

2 TX

A:DUAMCO4M

34 A30808-X3247-L291-3-7620


4. Remove the antenna cable

5. Remove the affected module

6. Select a module with a functional HW / SW state compatible to that of themodule which is being replaced

7. Check the DIP Switch settings

8. Insert prepared module

9. Connect all Semi rigid (2) and the Antenna cable (3)

10. Check the DIP-switch settings against the replaced module! ( (see HW:BTSEModules, A:DUAMCO,)

11. The red alarm LEDs must not be switched on after module insertion!The green LED “POWER” is switched on!If LEDs are switched not correctly: check antenna connection.

11 Run the Test for all DULNA and DUVSWR objects of the Replaced Module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACK<MO>PERFTEST <MO>

☞ ......(see OGL:LMT)

PERFTEST <MO>:NAME=RACK:<no>/<MO>:<no> ;

12 System Response

iPay attention to the different positions of the connectors of A:DUAMCO2Mand A:DUAMCO4M

Perftest <MO>:NAME=RACK:<no>/<MO>:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Perftest <MO>:NAME=RACK:<no>/<MO>:<no>

SW RELEASE: <no>


PERFTEST ACK BTSE:

name = BTSETEST:<no>

MOT = RACK:<no>/<MO>:<no>

tO = BTSETEST:1

A30808-X3247-L291-3-7620 35



13 Test Result

The test results can be examined in the LMT Message Browser Window.

If the Test Outcome is "fail", some more information is given, such as "ProposedRepair Action" etc.

14 Next DULNA or DUVSWR object, if created

Are either the DULNA or DUVSWR objects not yet tested? Y h...11N h...18


JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:

name = BTSE:<no>

testOutcome = <test outcome> (see below)

testTermination = Normal

MOT = RACK:<no>/<MO>:<no>

executedPhases

phaseId = PreliminaryTests<MO>

phaseId = CheckAlarmStatus<MO>

phaseId = EndTest<MO>


36 A30808-X3247-L291-3-7620


15 Unlock the DULNA and DUVSWR objects of the suspected module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSERACK<MO>UNLOCK <MO>


UNLOCK <MO>:NAME=RACK:<no>/<MO>:<no>;

16 System Response

Several CHANGED STATE EVENT REPORTs will follow. They can be examinedin the LMT Message Browser Window.

17 Second DULNA or DUVSWR objects

Are either the DULNA or DUVSWR objects not yet unlocked? Y h...15N h...18

Unlock <MO>:NAME=RACK:<no>/<MO>:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Unlock <MO>:NAME=RACK:<no>/<MO>:<no>

SW RELEASE: <no>


LOCK/UNLOCK <MO> ACK:

name = RACK:<no>/<MO>:<no>

administrativeState = Unlocked


A30808-X3247-L291-3-7620 37



18 Get Active Alarms

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEGETACTIVEALARMS BTSEEM

GETACTIVEALARMS BTSE:NAME=RACK:<no>

The active alarms will be listed in the LMT Message Browser Window.

19 Result of Module Replacement

The module replacement was successful if:- the test outcome was "pass"and if- there are no relevant active alarms

Was the module replacement successful? Y h...24N h...20

20 Reinsert the Replaced Module

It is probable that the original module did not cause the failure and was not de-fective. Therefore, the currently inserted module must be removed and the origi-nal module must be reinserted.

Go back to the beginning of this procedure to reinsert the original module intothe BTSE. After having reinserted the original module, continue with the now fol-lowing step.

21 Another Suspected Module/Interface?

Is there another suspected module/Interface in the fault message? Y h...22N h...23

22 Replacement Procedure for the Next Suspected Module/Interface

Go to the replacement procedure for the next suspected module/interface. h... (see Procedure3.x)

23 Call TAC

24 Mark the Replaced Module as Defective

38 A30808-X3247-L291-3-7620


25 Close BTSE

1. Screw on front plate (if removed)

2. Mount the backplane cover plate, see 1.6.4 "Remove/Mount Backplane Cov-er Plate"

3. Close shelter cover, see 1.6.1 "Open/Close Shelter Cover"

4. Close frontdoor and backplane door, see 1.6.3 "Open/Close Shelter Door"

26 Prepare End of Fault Clearance

If an LMT was connected, log off the LMT and pull the LMT cable out of thesocket.


END

A30808-X3247-L291-3-7620 39



3.5 BATTERYM

1 Interpret the Fault Message ☞ ...... (see 5.5.2)


- 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). ☞ ...... (see Fig. 4.4)

2 Open BTSE

1. Open shelter cover, see 1.6.1 "Open/Close Shelter Cover"

2. Open frontdoor and backplane door, see 1.6.3 "Open/Close Shelter Door"

3. Remove the backplane cover plate, see 1.6.4 "Remove/Mount BackplaneCover Plate"




4 Lock suspected module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKBATTERYLOCK BATTERY


LOCK BATTERY :NAME=RACK:<no>/BATTERY :<no> ;

40 A30808-X3247-L291-3-7620


5 System response



Lock BATTERY:NAME=RACK:<no>/BATTERY:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Lock BATTERY:NAME=RACK:<no>/BATTERY:<no>

SW RELEASE: <no>


LOCK/UNLOCK BATTERY ACK:

name = RACK:<no>/BATTERY:<no>



!The ESD precautions must be taken when pulling and inserting a module.Refer to 1.5.1 "ESD Precautions"

A30808-X3247-L291-3-7620 41



1. Set the switch (4) on the backplane in position “OFF” , see figure below

2. Unfasten 4 screws (3) on the backplane, see figure below

3. Unfasten 4 screws (5) on the front

4. Install the grip for pulling modules on the frontside, see figure below

5. Pull affected module


7. Insert prepared module

8. Fasten screws on front and back

9. Fasten 4 screws (3) on the backplane, see figure above

10. Set the switch (4) on the backplane in position “on”

11. Remove the grip for pulling modules on the frontside

7 Run Test for Replaced Module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKBATTERYPERFTEST BATTERY


PERFTEST BATTERY :NAME=RACK:<no>/BATTERY :<no> ;

3

3 3

battery backplane battery frontside

4

3

5 5

5 5

42 A30808-X3247-L291-3-7620


8 System Response

Perftest BATTERY:NAME=RACK:<no>/BATTERY:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Perftest BATTERY:NAME=RACK:<no>/BATTERY:<no>

SW RELEASE: <no>


PERFTEST ACK BTSE:


MOT = RACK:<no>/BATTERY:<no>

tO = BTSETEST:1


A30808-X3247-L291-3-7620 43



9 Test Result



10 Unlock suspected module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKBATTERYUNLOCK BATTERY


UNLOCK BATTERY :NAME=RACK:<no>/BATTERY :<no> ;

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:

name = BTSE:<no>



MOT = RACK:<no>/BATTERY:<no>

executedPhases

phaseId = PreliminaryTestsBATTERY

phaseId = CheckAlarmStatusBATTERY

phaseId = EndTestBATTERY


44 A30808-X3247-L291-3-7620


11 System Response



b MANAGED-ELEMENTBSS-EQUIPMENTBTSEGETACTIVEALARMS BTSEEM






Unlock BATTERY:NAME=RACK:<no>/BATTERY:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Unlock BATTERY:NAME=RACK:<no>/BATTERY:<no>

SW RELEASE: <no>


LOCK/UNLOCK BATTERY ACK:

name = RACK:<no>/BATTERY:<no>



A30808-X3247-L291-3-7620 45







Is there another suspected module/interface in the fault message? Y h...16N h...17



17 Call TAC

18 Close BTSE




19 Mark the replaced module as defective




END

46 A30808-X3247-L291-3-7620


3.6 BPORT

Identifies the 2 PCM30/24 and 8 carrier unit interfaces (4DCUs each) provided by the COBA central core module.For error correction continue with procedure: h PROC: Abis

A30808-X3247-L291-3-7620 47



3.7 COBAM

– download and activate the software

– reconfigure the BTSE(If a backup copy of the site specific configuration is available, start the Backup BTSTool via the WINDOWS Start menu (“Start” -> “Programs” -> “LMT...” -> “BackupBTS”),orclick on the “Backup BTS” icon in the “LMT Control Center” window.

– rebuild the inventory data that was stored on the removed COBAM(Usually, a backup IDF-file is available, or the data can be extracted from the BSC-IDF.

1 Interpret the Fault Message ☞ ...... (see 5.5.2)



Use these values for command input.Use the logical address to find the mounting location of the module(s). ☞ ...... (see Fig. 4.4)

2 Open BTSE

1. Open shelter cover, see 1.6.1 "Open/Close Shelter Cover"

2. Open frontdoor and backplane door, see 1.6.3 "Open/Close Shelter Door"

3. Remove the backplane cover plate, see 1.6.4 "Remove/Mount BackplaneCover Plate"




iModule COBAM may be removed while the power is on!

iAfter replacement of COBAM, the BTSE specific data base on this COBAM is lost!It is necessary to:

48 A30808-X3247-L291-3-7620


4 Reaction

h...6

5 Reaction

The BTSE is in Phase 3. h...6

For the meaning of the phases refer to chapter 5.6.2 or the OGL:LMT. ☞ ......(see OGL:LMT)


It is possible that there is no access to the Network Element (NE)If the access to the NE is possible, make a backup copy of the HW configura-tion and the Remote Inventory Data, refer to ITMN:BTSE BS82 “BTS BackupFiles Generation”.

!ESD precautions must be taken when pulling and inserting a module. Referto 1.5.1 "ESD Precautions"

!The screws on the backplane referring to COBAM have to be unscrewed!

A30808-X3247-L291-3-7620 49



1. Unfasten 3 screws (3) on frontside

2. Unfasten 2 screws (1) on the backplane, see figure below

3. Install the grip for pulling modules. Fasten the two screws (2) on the frontsideof the COBA, see above.

4. Pull affected module

5. Select a module with a functional HW/SW state compatible to that of themodule which is being replaced

6. Check the DIP switch settings

7. Insert the new module (the insertion starts the boot process)


9. Wait a few minutes until the boot process is finished (green LED:ACT isswitched on see Fig. COBAMV1)

1

1

2

2

3

3

3

50 A30808-X3247-L291-3-7620


7 System response

CHANGED STATE EVENT REPORTs are displayed

8 SW Download

Perform the procedure SW Download and Activation ITMN:BTSE ☞ ......(seeITMN:BTSEBS-82)

9 Reconfiguration of the BTS

Is a backup copy of the former HW-configuration available? Y h...10N h...33

10 Moving the Backup files to the BKBTS\ENHMICRO directory

In order to reconfigure a BTS, in case of loosing all configuration data after aCOBAM replacement, a backup copy of the initial configuration can be used.


b Copy the 6 backup files “SCRIPT*EM.LMT” from storage media to the directory:

C:\...\LMT\BKBTS\ENHMICRO

iThe script files can be executed only if the LMT is connected to aBTSE in phase 2!

iWhen reconfigure in phase 2 a BS-82 using command files gotfrom Backup Script (Delete all HW, Create all HW), it may happenthat the BS-82 switch directly to zero configuration after an alarmon one of the AC/DC module.To avoid this, the backup script containing ACDCP and BATTERYmodules creation should be modified before execution.A sleep time has to be inserted between each ACDCP and BAT-TERY creation command (sleep:time=15;) in the script file“scrpt5em.lmt” got from the LMT backup tool. This file is a CLItext file and can be edited.

iIf the BKBTS\ENHMICRO directory and the necessary files arenot present on the LMT, see ITMN:BTSE BS-82 eMicro.

A30808-X3247-L291-3-7620 51



11 Start the Backup BTS Tool

b Start the Backup BTS Tool via the WINDOWS Start menu (“Start” -> “Programs”-> “LMT...” -> “Backup BTS”),orclick on the “Backup BTS” icon in the “LMT Control Center” window.

The “BACKUPBTS” window opens.

12 Restore the HW Configuration

b Click on the button “Restore HW Configuration”.

After the HW configuration is restored, the following message is displayed:

THE SCRIPT WAS DONE SUCCESSFULLY h...13


Is the result for all modules as follows?

*** INFORMATION ***CHANGED STATE EVENT REPORT

NAME = RACK:<no>/<module>:<no>Administrative State: UNLOCKEDOperational State: ENABLEDAvailability Status = NULL_value Y h...18

N h...14






52 A30808-X3247-L291-3-7620



Go to the replacement procedure for the next suspected module/interface. h...(see Procedure3.x)

17 Call TAC


19 Restore the Remote Inventory Data

The function “Remote Inventory” of the Siemens Basestation System performselectronic, non volatile storing of the complete, individual product identificationdata (PID) of each inventoried object.Modules with inventory data on board are called ob_RIUs (on-board Remote In-ventory Units). In order to include inventory data of objects without a non volatilestorage (e. g., frames, racks, OEM components), the data of the nob_RIUs (noton-board Remote Inventory Units) is entered into an inventory data table (IDT)via the LMT and the off-line tool ”IDF-Editor”. As a nob_RIU file (NOB) this datais stored on the COBA and must be rebuild in the event of a COBA replacement.Supplemented with a footer and header, the IDT can be exported and stored asan inventory data file (IDF) for backup reasons.Usually a backup of the IDF is available on site. If not, the data can be extractedfrom the BSC-IDF or it must be re-entered.

Is a backup copy of the former IDF- file available? Y h...20N h...33

20 Backup Copy of the BTSE IDF-File

Is a backup copy of the former IDF-file for the BTSE available? Y h...24N h...21

21 Backup Copy of the BSC IDF-File

Is a backup copy of the BSC IDF-file available? Y h...23N h...22

22 Create all nob_RIUs manually

For the creation of the inventory data for all nob_RIUs, refer to the ITMN:BTSEBS-82, chapter “Procedures”.

☞ ......(seeITMN:BTSEBS-82)

Continue with the download and backup storage of the inventory data. h...26

A30808-X3247-L291-3-7620 53



23 Extract BTSE data from BSC-IDF

The data for the relevant BTSE must be separated from the inventory datastored as central IDT in the BSC or its backup file of the BSC area where theBTSE belongs. Call TAC to get the data of the BTSE provided in an appropriateIDF-file.

Call TAC to get the data of the BTSE provided in an appropriate IDF-file. h...35

54 A30808-X3247-L291-3-7620


24 Start IDF Editor

The IDF editor is part of the LMT and the command “Idf Editor” for starting isadded to the relevant directory of the “Start” menu within the Windows applica-tion. Alternatively the icon “IDF” on the LMT Control Center window starts theIDF editor.

b Start IDF Editor

– Command “Idf Editor” in the relevant directory (where the LMT is installed) ofthe “Start” menu

or

– click on the “IDF” icon located in the LMT Control Center window

The IDF editor window is displayed.

25 Open IDF-File

The IDF-file is usually stored on a disk and archived with the site specific docu-mentation. Copy this file to the hard disk of the LMT PC.

b File

– Select “Open” in the “File” menu

– Enter the path and file name of the IDF-file or choose from the list in the ap-pearing window; e.g.: <c:\...\LMT<version>\idf\ (standard)>

– Double-click on the file name or click on the “Open” button with the file nameselected

A30808-X3247-L291-3-7620 55



26 Export nob_RIU File

Only the nob_RIU-part has to be exported for downloading into the BTSE.

b Export the nob_RIU-part:

– Select “NOB” in the “Export” menu.

The file name is automatically composed of the “SalesUniqueName” with theextension “.nob ” .

– Click on the “Save” button.

A question window opens: Create Nob RIUs file for Download?

– Click on the “Yes” button.

A window opens which displays the destination path of the NOB-file, for exam-ple:C:\...\LMT<version>\IDF\Dnload\BTS_NRIU.nob

– Click on the “OK” button.

27 Download nob_RIU File to BTSE

Change to the LMT application!

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMREMINVDNLIDFD REMINVSRCDIR=<C:\...\LMT<version>\IDF\DNLOAD (standard)>

DNLIDFD:SRCDIR=”C:\...\LMT<version>\IDF\DNLOAD (standard)”;

28 System response

============================================


COMMAND: DNLIDF REMINV:NAME=REMINV:0,SRCDIR=”C:\...\LMT<version>\IDF\DNLOAD”;

COMMAND RESULT: OPERATION COMPLETED

Downloading File: <for example BTS_NRIU>

100% of packets transferred

On Directory: C:\...\LMT<version>\IDF\DNLOAD (standard)

============================================


56 A30808-X3247-L291-3-7620


29 Upload IDT-File from BTSE

The remote inventory data of the ob-RIUs have to be loaded onto the LMT PC tocreate an up-to-date IDF file for backup.

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMREMINVUPLLIDF REMINVDESTDIR=<path>FILE=<file name>OVERWRITE=YES

The values DESTDIR and FILE are optional. If no special path or file name isentered, the file is uploaded to the default directory of the IDF editor.If the value OVERWRITE=YES is selected, a former version of an uploaded IDT-file will be overwritten.

For example: <path>=c:\...\LMT<version>\IDF\UPLOAD (standard); <filename>=BTSE.IDT

UPLLIDF:DESTDIR=”C:\...\LMT<version>\IDF\UPLOAD (standard)”,FILE=”BTSE.IDT”,OVERWRITE=YES;

30 System response



Download End: File BTS_NRIU Transfer Completed

============================================


COMMAND: UPLLIDF REMINV:NAME=REMINV:0,OVERWRITE=YES;


Uploading File: BTSE.IDT

To: BTSE.IDT

On Directory: C:\...\LMT<version>\IDF\UPLOAD (standard)

============================================


A30808-X3247-L291-3-7620 57



31 Open the Uploaded File

b Open the uploaded file:

– Change back to the IDF Editor application.

– Select “Open” in the “File” menu.

– Select the uploaded file from the list in the appearing window; e.g.:<C:\...\LMT<version>\IDF\UPLOAD\BTSE.idt”>.

– Click on the “Open” button.

32 Export File for Backup

b Export the IDF-file:

– Select “IDF” in the “Export” menu.

– Select the destination path in the appearing window, preferably “A:\”.

The file name is automatically composed of the “SalesUniqueName” with theextension “.idf ” .


– Put the disk with the backup file of the inventory data to the site specificdocumentation.

33 Start installation procedure

Manually create all nob-RIU-Boards as described in the Installation Test Manualof the BS-82 chapter 3!If a backup at the BSC is available, call TAC to extract the BTSE-data from theBSC backup!

☞ ...... (see ITMN:BTSE BS-82)

34 Close BTSE







END



Upload End: File BTSE.IDT Transfer Completed

58 A30808-X3247-L291-3-7620


3.8 DCU

Each module DCU (see HW:BTSE Modules, DCU) consists of two CUs and two DIL-NAs, see below. All HMOs on DCU have to be locked before pulling the module and un-locked after the replacement procedure.





2 Interpret the Alarm Type

Is one of the following values listed in the fault message?

- VSWR Alarm- Cable Problem- Transceiver Problem Y h...(see 3.16)

N h...3

CU There are two HMOs of this type per DCU, they have to behandled separately. This HMO has the same functions as themodule CU in BS 240.

DILNA There are two HMOs of this type per DCU, they have to behandled separately.

iModule DCU can be removed while power is on!

iTake care to disconnect cables from backside and take care of the high weight. To sendback DCU for repair please use the "special DCU-Box" for transportation.

iIf you lock or replace modules in the TX/RX path of the BTSE, calls may be lost. Toavoid the loss of calls, please read 1.5.2 "Avoiding the Loss of Calls"

A30808-X3247-L291-3-7620 59






4 Lock HMOs CU on suspected DCU

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKCULOCK CU

LOCK CU:NAME=RACK:<no>/CU:<no> ;

5 System response


iThere are always two CUs in one DCU

Lock CU:NAME=RACK:<no>/CU:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Lock CU:NAME=RACK:<no>/CU:<no>

SW RELEASE: <no>


LOCK/UNLOCK CU ACK:

name = RACK:<no>/CU:<no>



60 A30808-X3247-L291-3-7620


6 Lock the HMOs DILNA on the suspected DCU

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKDILNALOCK DILNA

LOCK DILNA:NAME=RACK:<no>/DILNA :<no> ;

7 System response

8 Open BTSE

1. Open shelter cover, see1.6.1 "Open/Close Shelter Cover"

2. Open frontdoor and backplane door, see1.6.3 "Open/Close Shelter Door"

3. Remove the backplane cover plate, see1.6.4 "Remove/Mount BackplaneCover Plate"


iThere are always two DILNAs in one DCU

Lock DILNA:NAME=RACK:<no>/DILNA:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Lock DILNA:NAME=RACK:<no>/DILNA:<no>

SW RELEASE: <no>


LOCK/UNLOCK DILNA ACK:

name = RACK:<no>/DILNA:<no>



!The ESD precautions must be followed when pulling and inserting a module.Refer to 1.5.1 "ESD Precautions"

A30808-X3247-L291-3-7620 61



1. Disconnect all Semi rigid cables (1) at the backplane .Attention: The RX cables have to be screwed anticlockwise!Attention: Mark the normal- and the diversity path!

!Remove the semi-rigid cables at the backplane side of DCU!Unscrew the 2 screws on backplane side of DCU!

iIn the picture below you see a DCULG with four connectors. Another type ofcarrier unit DCUDUX has two instead of four connectors.

1

2

2

DCULGx backplane side

Grip

Very important:The connectors for RX path on DCUhave to be screwed counterclock-wise! It is a left-screw thread.The connectors for TX path on DCUhave to be screwed clockwise! It is aright-screw thread.

RX

TX

33

33

DCULGx frontside

DCUDUX withtwo semi rigidcables

62 A30808-X3247-L291-3-7620


2. Unfasten the 2 screws (2) on the backplane side, see above

3. Unfasten the four screws (3) on the front side

4. Install the grip for pulling modules, see above

5. Pull the affected module


7. Insert the prepared module


9. Connect all Semi rigid cables


b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKCUPERFTEST CU


PERFTEST CU:NAME=RACK:<no>/CU:<no> ;

11 System Response

Perftest CU:NAME=RACK:<no>/CU:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Perftest CU:NAME=RACK:<no>/CU:<no>

SW RELEASE: <no>


PERFTEST ACK BTSE:


MOT = RACK:<no>/CU:<no>

tO = BTSETEST:1


A30808-X3247-L291-3-7620 63



12 Test Result



13 Unlock CUs on suspected module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKCUUNLOCK CU


UNLOCK CU:NAME=RACK:<no>/CU:<no> ;

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:

name = BTSE:<no>



MOT = RACK:<no>/CU:<no>

executedPhases

phaseId = PreliminaryTestsCU

phaseId = CheckAlarmStatusCU

phaseId = EndTestCU


64 A30808-X3247-L291-3-7620


14 System Response


15 Run the test on DILNAs of the replaced module

b MANAGED-ELEMENTBSS-FUNCTIONALBTSEEMRACKDILNAPERFTEST DILNA


PERFTEST DILNA :NAME=RACK:<no>/DILNA :<no> ;

The MO (Managed Object) can be: DILNA.

16 System Response

Unlock CU:NAME=RACK:<no>/CU:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Unlock CU:NAME=RACK:<no>/CU:<no>

SW RELEASE: <no>


LOCK/UNLOCK CU ACK:

name = RACK:<no>/CU:<no>



Perftest DILNA:NAME=RACK:<no>/DILNA:<no>


============================================

JOB: <no>



A30808-X3247-L291-3-7620 65



USER: <user>

COMMAND: Perftest DILNA:NAME=RACK:<no>/DILNA:<no>

SW RELEASE: <no>


PERFTEST ACK BTSE:


MOT = RACK:<no>/DILNA:<no>

tO = BTSETEST:1


66 A30808-X3247-L291-3-7620


17 Test Result



18 Unlock the DILNA objects of the suspected module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKDILNAUNLOCK DILNA


UNLOCK DILNA :NAME=RACK:<no>/DILNA :<no> ;

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:

name = BTSE:<no>



MOT = RACK:<no>/DILNA:<no>

executedPhases

phaseId = PreliminaryTestsDILNA

phaseId = CheckAlarmStatusDILNA

phaseId = EndTestDILNA


A30808-X3247-L291-3-7620 67



19 System Response



b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMGETACTIVEALARMS BTSEEM






Unlock DILNA:NAME=RACK:<no>/DILNA:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Unlock DILNA:NAME=RACK:<no>/DILNA:<no>

SW RELEASE: <no>


LOCK/UNLOCK DILNA ACK:

name = RACK:<no>/DILNA:<no>



68 A30808-X3247-L291-3-7620








Go to the replacement procedure for the next suspected module/interface. h...(see Procedure3.x)

25 Call TAC


27 Close BTSE







END

A30808-X3247-L291-3-7620 69



3.9 DILNA

DILNA is a functional part of DCU and can not be replacedseparately.For error correction continue with procedure: h PROC: DCU

70 A30808-X3247-L291-3-7620


3.10 DULNA

DULNA is a functional part of DUAMCO and can not be re-placed separately.For error correction continue with procedure: h PROC: A:DUAM-

COM

A30808-X3247-L291-3-7620 71



3.11 DUVSWR

An ASU (Antenna Supervision Unit) within the DUAMCO isresponsible for detecting certain reflection factors at the an-tenna connector. The ASU detects the VSWR failure andgenerates a failure information towards the O&M (CAN businterface) for the generation of “Antenna not Adjusted” or“Antenna Faulty” error messages.For error correction continue with procedure: h PROC: TX/RX

Path (e.g., VSWR)

72 A30808-X3247-L291-3-7620


3.12 FANM





2 Open BTSE

– Open shelter cover, see 1.6.1 "Open/Close Shelter Cover"


Plug the LMT cable into the corresponding socket. ☞ ......(see HW:BTSEModules, figureOVPTMV1)

Start LOGON - Procedure. ☞ ......(see OGL:LMT)

4 Lock suspected module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKFANPLOCK FANP


LOCK FANP:NAME=RACK:<no>/FANP:<no> ;

A30808-X3247-L291-3-7620 73



5 System response



1. Pull the plug on the right side of the fan, see Fig. 3.1 "Replace FANM" (1)

Fig. 3.1 Replace FANM

Lock FANP:NAME=RACK:<no>/FANP:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Lock FANP:NAME=RACK:<no>/FANP:<no>

SW RELEASE: <no>


LOCK/UNLOCK FANP ACK:

name = RACK:<no>/FANP:<no>



!The ESD precautions must be followed when pulling and inserting a module.Refer to 1.5.1 "ESD Precautions"

!Caution when pulling out the FAN, the rotor is still running for a few seconds.Watch your fingers!

1

2 2

3

3

74 A30808-X3247-L291-3-7620


2. press the two levers up Fig. 3.1 "Replace FANM" (2) and pull affected mod-ule using the small metal grips (3)

3. Insert the new module


b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKFANPPERFTEST FANP


PERFTEST FANP:NAME=RACK:<no>/FANP:<no> ;

8 System Response

Perftest FANP:NAME=RACK:<no>/FANP:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Perftest FANP:NAME=RACK:<no>/FANP:<no>

SW RELEASE: <no>


PERFTEST ACK BTSE:


MOT = RACK:<no>/FANP:<no>

tO = BTSETEST:1


A30808-X3247-L291-3-7620 75



9 Test Result


If the Test Outcome is “fail”, some more information is given, such as “ProposedRepair Action” etc.

10 Unlock suspected module

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACKFANPUNLOCK FANP


UNLOCK FANP:NAME=RACK:<no>/FANP:<no> ;

JOB: <no>



USER: <user>

SW RELEASE: <no>


Test Report:

name = BTSE:<no>



MOT = RACK:<no>/FANP:<no>

executedPhases

phaseId = PreliminaryTestsFANP

phaseId = CheckAlarmStatusFANP

phaseId = EndTestFANP


76 A30808-X3247-L291-3-7620


11 System Response



b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMGETACTIVEALARMS BTSEEM




The module replacement was successful if:- the test outcome was “pass”and if- there are no relevant active alarms


Unlock FANP:NAME=RACK:<no>/FANP:<no>


============================================

JOB: <no>



USER: <user>

COMMAND: Unlock FANP:NAME=RACK:<no>/FANP:<no>

SW RELEASE: <no>


LOCK/UNLOCK FANP ACK:

name = RACK:<no>/FANP:<no>



A30808-X3247-L291-3-7620 77










17 Call TAC

18 Close BTSE

– Close shelter cover, see 1.6.1 "Open/Close Shelter Cover"


20 Update the Remote Inventory Data i ...PROC: Re-mote InventoryData (Update)

Update the Remote Inventory Data. Renew the backup copy of the inventorydata table.For updating the remote inventory data and renewing the backup copy, refer toprocedure “Updating the Remote Inventory Data” in this manual.




END

78 A30808-X3247-L291-3-7620


3.13 LAPDLE

This error message indicates a problem with the connectionto the BSC.For error correction continue with procedure: h PROC: Abis

A30808-X3247-L291-3-7620 79



3.14 PCM

For error correction continue with procedure: h PROC: Abis

80 A30808-X3247-L291-3-7620


3.15 Remote Inventory Data (Update)

After replacement of a nob_RIU component, the remote inventory data and the backupcopy must be updated.

1 Upload IDT-File from BTSE

The remote inventory data has to be loaded onto the LMT PC.

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMREMINVUPLLIDF REMINV(DESTDIR=<path>)(FILE=<file name>)OVERWRITE=YES

The values DESTDIR and FILE are optional. If no special path or file name isentered, the file is uploaded to the default directory of the IDF editor.If the value OVERWRITE=YES is selected, a former version of an uploaded IDT-file will be overwritten.

For example: <path>=C:\....\LMT<version>\IDF\UPLOAD; <file name>=BT-SE.idt

UPLLIDF:DESTDIR=”C:\...\LMT<version>\IDF\UPLOAD (standard)”,OVER-WRITE=YES;

2 System response

iStarting with BR7.0, a second LMT version is available: the new LMT Evolution. Forperforming this procedure with the LMT Evolution, refer to the operator guidelinesOGL:LMT Evolution and OGL:IDF Evolution.

============================================




Uploading File: BTSE.IDT

To: BTSE.IDT

On Directory: C:\...\LMT<version>\IDF\UPLOAD (standard)

============================================

A30808-X3247-L291-3-7620 81






Upload End: File BTSE.IDT Transfer Completed

82 A30808-X3247-L291-3-7620


3 Start IDF Editor

The IDF editor is part of the LMT and the command “Idf Editor” is added to therelevant directory of the “Start” menu within the Windows application. Alterna-tively the icon “IDF” on the LMT Control Center window starts the IDF editor.

b Start

– Command “Idf Editor” in the relevant directory (where the LMT is installed) ofthe “Start” menu

or

– click on the “IDF” icon in the LMT Control Center window.

The IDF Editor window is displayed.

4 Open IDT-File

b Open the IDT-File

– Select “Open” in the “File” menu

– Select the uploaded file from the list displayed in the window; e.g.:<C:\...\LMT<version>\IDF\UPLOAD\BTSE.idt >

– Click on the “Open” button

5 Type of Replaced Module ☞ ......(see 5.6.3)

Is the replaced module listed in the column “Functional Address Type” of the ta-ble “List of nob_RIUs? Y h...6

N h...7

A30808-X3247-L291-3-7620 83



6 Edit Remote Inventory Data of the Replaced Unit

The records of the nob-RIUs are shown in bold letters. Only these records areeditable.

b Edit the remote inventory data of the replaced unit(s):

– Move the mouse cursor to the record of the replaced unit.

– Press the right mouse button.

– An “Edit”-button appears

– Click on the “Edit”-button and a window titled “PIDnobRIU’s” for editing theinventory data of the unit is opened

– Confirm the entered data by clicking on the “OK!”-button

– After “OK” you have to save the file with “Save as” in the “file” menu

SCAN:With the “Scan” button you activate a 2D-Code Reader.The FW Item Number,FW Functional Status, HW Item Number, HW Functional Status and SerialNumber nob_RIUs data can be automatically detected (if present on the label ofthe module) by using the 2D-Code Reader connected to the serial port of theLMT.

7 Export IDF-File for Backup

b Export

– Select “IDF” in “Export” menu

– Select the destination path in the displayed window, preferably “A:\”

(The file name is composed of the “SalesUniqueName” with the extension “.idf ”automatically).

– Click on the “Save” button

Put the disk with the backup file of the inventory data to the site specific docu-mentation.

8 Return of the Updated Remote Inventory Data to the BTSE

84 A30808-X3247-L291-3-7620


Has the inventory data been updated manually (for nob_RIUs only)? Y h...9N h...12

9 Export nob_RIU File for Download

Only the nob_RIU-part has to be exported for downloading into the BTSE.

b Export the nob_RIU-part:

– Select “NOB” in the “Export” menu.

The file name is automatically composed of the “SalesUniqueName” with theextension “.nob ”.


A question window opens: Create Nob RIUs file for Download?

– Click on the “Yes” button.

A window opens which displays the destination path of the NOB-file, for exam-ple:C:\...\LMT<version>\IDF\DNLOAD\BTS_NRIU.nob

– Click on the “OK” button.

10 Download nob_RIU File to BTSE

Change to the LMT application!

b MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMREMINVDNLIDFD REMINVSRCDIR=<C:\...\LMT<version>\IDF\DNLOAD (standard)>

SRCDIR: enter the source directory in which the exported NOB-file was saved,for example C:\...\LMT<version>\IDF\DNLOAD.

DNLIDFD:SRCDIR=”C:\...\LMT<version>\IDF\DNLOAD (standard)”;

11 System response

============================================




Downloading File: <for example BTS_NRIU>

100% of packets transferred

A30808-X3247-L291-3-7620 85




Log off the LMT and pull the LMT cable out of the socket.


END

On Directory: C:\...\LMT<version>\IDF\DNLOAD (standard)

============================================


COMMAND: DNLIDF REMINV:NAME=REMINV:0,SRCDIR=”C:\...\LMT<version>\IDF\DNLOAD (stan-dard)”;


Download End: File BTS_NRIU Transfer Completed

86 A30808-X3247-L291-3-7620


3.16 TX/RX Path (e.g., VSWR)

Examples for Alarms in the TX/RX Path

DUCOM: VSWR alarm 1 or 2

HYCOM: VSWR alarm 1 or 2

FICOM: VSWR alarm 1 or 2

RF power reflected into power stage

Cell 0,1,2: Antenna System TX

FICOM_VSWRP: VSWR alarm Low or High

DUAMCO: RX alarm Low or High

DIAMCO: RX alarm Low or High

TMA: RX alarm Low or High

CU: Diversity receive branch failed

1 Cable Connections Fastened Correctly?

Are the TX/RX cable connections of the suspected module fastened correctly? Y h...5N h...2

2 Fasten cable connections

Make sure to fasten all cables by tightening their coupling nuts with a torquewrench.

3 Check the LEDs on the suspected module

Do the LEDs signal normal operation after a few seconds?

(No red LEDs may be on) Y h...4N h...7

iIn most cases, alarms in the TX/RX path originate from loose or damaged cables.Therefore, the relevant cables must be checked first, according to the following proce-dure.

If the alarm cannot be cleared in this way, the suspected modules must be replaced.Note that the failure cause may be located in any module of the TX/RX path:- the module(s) addressed in the error message- combining equipment- antenna.

It is recommended to start with the replacement of the module which is addressed in thefault message. Afterwards - if the error is still there - take the other modules in the TX/RXpath into consideration.

A30808-X3247-L291-3-7620 87



4 Additional Check

Check the active alarms with the LMT:MANAGED ELEMENTBSS EQUIPEMENTBTSEEMGETACTIVEALARMS BTSEEM

All active alarms will be listed in the Message Browser Window.

Does the alarm still appear ? Y h...5N h...8

5 Do the Cables Look O.K.?

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

N h...6

6 Call Tac

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

7 Continue with the Replacement Procedure

Continue with the replacement procedure of the module, which is addressed inthe fault message. Afterwards - if the error is still there - take the other modulesin the TX/RX path into consideration.

– DCU

– A:DUAMCO

– A:DUXMEG ☞ ......See “FaultClearance Pro-cedures forModules andInterfaces” onpage 24.

The picture of the functional blocks gives an overview of the possible fault loca-tions in the TX/RX path. ☞ ...... (see Fig. 4.3)

8 Prepare end of fault clearance

Close the BTSE door

END

88 A30808-X3247-L291-3-7620


4 Tables, lists and figures

A30808-X3247-L291-3-7620 89



4.1 Hardware Architecture

Fig. 4.1 eMicro

90 A30808-X3247-L291-3-7620


Fig. 4.2 BS-82 eMicro (view from right side)

side door

FAN

DCU1

DCU 0

COBAM

TIF

battery

OVPT

xPSC

cable entry

ADD-ONmodule

INTENNA

air guide and heater

A30808-X3247-L291-3-7620 91



Fig. 4.3 Functional blocks

A:OVP16AMA:TIFxA:DUXMEGA:DUAMCOM

Add-On-Modules

TX

RX

CAN CAN

FAN

Temp

RDO

ExternalAlarms

DCU0

DUX

DCU1

DUX

RX

TX 4 AMCOalarms

CC-Links

M:COBAM

CAN NODE

CAN-Bus

Power-48V DC

CAN NODE alarm

ACPSC/DCPSC

BATTERYM

230V AC

115V AC

-48V DC

LMT

Ethernet

2 Abis-LinksMaster Base UnitOVPTxM

CC-Links

CC-Links

Antenna1..4

Antenna1..4

FAN

Temp

RDODCU0

DUX

DCU1

DUX

RX TX 4 AMCOalarms

CAN-Bus CAN NODE alarm

ACPSC/DCPSC

BATTERYM

Power-48V DC

230V AC

115V AC

-48V DC

Extension Base Unit

TX

RX

A:DUXMEGA:DUAMCOM

CAN

Extension Cabinet

Add-On-Modules

A:OVP16AM

Master Cabinet

PC

M 3

0

92 A30808-X3247-L291-3-7620


4.2 Detailed Information on Hardware Components(Modules, Frames and Racks)

For detailed information on the system hardware, please refer to the Technical Descrip-tion for Base Station Systems (see TED:BSS).

For detailed information on hardware components, please refer to the respective Hard-ware Manual (see HW:BTSE Modules, HW:BTSE Frames/Panels, HW:BTSERacks/Shelters).

A30808-X3247-L291-3-7620 93



4.3 Right View of the eMicroBTS Racks and Mounting Posi-tions

Fig. 4.4 BS-82 eMicro base configuration

Extension Cabinet

FANM

air guide

DCU1 DCU0

air guide

INTENNA

HEATERM

mounting

plate

airby

pass

BATTERYM

connection panel

M:COBAM

CP:TIF

air guide

DCU1 DCU0

air guide HEATERM

CP:COBAM

CP:TIF

FANM

Master Cabinet

OVPTM

ACPSC

OVPTCOAXMDCPSC, ACPSC/UCP:BATTERYM

*) **) ***)

*)**)

***)

INTENNA

mounting

plate

BATTERYM

airby

pass

BATTERYM

connection panel

CP:OVPT

ACPSC

**) ***)

BATTERYM

DCPSC, ACPSC/UCP:BATTERYM

**)***)


*)

***)

94 A30808-X3247-L291-3-7620


Fig. 4.5 Master Cabinet with add-on modules

4.4 Connection field

All external interfaces are available on connection field on the bottom of the backplane.Check whether all equipped interfaces are correctly connected.

Add-On Module 0

Add-On Module 1

Add-On Module 2

FANM

air guide

DCU1 DCU0

air guide

INTENNA

HEATERM

mounting

plate

airby

pass

BATTERYM

connection panel

M:COBAM

CP:TIF

OVPTM

ACPSC

*) **) ***)

BATTERYM


*)

***)

**)

Managed Objects(MO)ENVABTSE:0,21ACTACDCP

Managed Objects(MO):CU:0...3DILNA:0...3DUVSWR:0...1

Managed Objects(MO):FANP:0

Managed Object(MO):DUVSWR:0...1DULNA:0,1

Managed Objects(MO)LAPDLE:0...7BPORT:0...1

A30808-X3247-L291-3-7620 95



Fig. 4.6 Connection field (view from above)

4.5 TX/RX Paths of Some Configuration Examples

This chapter shows a diagram of the TX/RX paths of a configuration example. A table isgiven which lists some details on possible failures, their possible effects and how theycan be detected.

Failures in the TX/RX paths are detected by one or more failure detection systems/alarmtypes:

– VSWR MonitoringExamples of corresponding alarms:Combining Equipment:Error ID <no> – DUAMCO: VSWR alarm HIGHError ID <no> – FICOM_VSWRP: VSWR alarm HIGHCU:Error ID <no> – RF power reflected into powerstage

– RX Diversity AlarmsExample:Error ID <no> – One of the two diversity receivers fails

– TNF Monitoring (Filter Combiner)Example of corresponding alarms:Error ID <no> – FICOM_TNFP: TNF tuning alarm

– LNA AlarmsExamples:Error ID <no> – DIAMCO: RX alarm LOWError ID <no> – DIAMCO: RX alarm HIGHError ID <no> – DUAMCO: RX alarm LOWError ID <no> – DUAMCO: RX alarm HIGH

Exten-sion ca-ble ANT 1

ANT 0 ANT 2

ANT 3

Powerin

ENVA

Abis A

Abis B

CLKSYNC

iThis chapter provides an overview, but does not claim to provide complete lists of pos-sible errors, their possible effects and detection systems.The actual sets of error messages depend on customer specific conditions such as theindividual configuration of the base station system, customer defined thresholds and fur-ther details that cannot be taken into account here.The occurrence frequency of the errors is not considered and may differ considerably.

96 A30808-X3247-L291-3-7620


– Sleeping Cell DetectionBSC alarm: Transceiver Problem (Specific Problem: No call in cell within a pre-defined time frame)

– Online RF LoopbackError ID <no> – Increased path loss difference

Fig. 4.7 TX/RX Paths of Configuration with A:DUAMCO

A:DUAMCO

DCU DCU

1

3

4

6

5

6

2

The numbering in the figure refers to the numbering in the corresponding table.

A30808-X3247-L291-3-7620 97



No. Failure Cause Effect Detected by...

1 TX/RX antenna defect, cable dis-rupted

VSWR Alarm (dependant on at-tenuation figures);reduced sensitivity;reduced coverage area

VSWR monitoring;Sleeping Cell Detection if theBCCH carrier is affected (theBCCH carrier is always affected ifonly one TX antenna is used);Online RF Loopback;RX diversity alarm

2 TX/RX antenna out of bearing(e.g. after windstorms)

reduced coverage area;coverage area reduced to zero;no real on air combining (reduceddiversity gain; high drop call ratein case of handover to alternateantenna; reduced cell capacity);VSWR alarm

Online RF Loopback;Sleeping Cell Detection if theBCCH carrier is affected (theBCCH carrier is always affected ifonly one TX antenna is used);VSWR monitoring

3 RF feeder cable poorly assem-bled or disrupted

TX/RX cable: reduced coveragearea for affected antenna;VSWR Alarm;RX cable: reduced diversity gain;

Online RF Loopback;VSWR monitoring;RX Diversity Alarm;

4 RF-TX path interruption insideA:DUAMCO;

RF-RX path interruption insideA:DUAMCO

coverage area reduced to zerofor all carriers behind interruptionpoint;reduced signal sensitivity due tothe loss of diversity;

Online RF Loopback;Sleeping Cell Detection if theBCCH carrier is affected (theBCCH carrier is always affected ifonly one TX antenna is used);RX Diversity Alarm

5 RF-TX path interruption betweenA:DUAMCO and DCU;

RF-RX path interruption betweenA:DUAMCO and DCU

SW disables carrier due to VSWRAlarm

VSWR monitoring of HPA/DCU;Online RF Loopback if VSWRmonitoring fails (possible excep-tion if Baseband Hopping is acti-vated);RX Diversity Alarm

6 Failure inside DCU (HPA) (isola-tor not properly soldered)

SW disables DCU due to VSWRAlarm

VSWR monitoringOnline RF Loopback if VSWRmonitoring fails (possible excep-tion if Baseband Hopping is acti-vated)

Tab. 4.1 Failure Causes in the TX/RX Path, Configuration with A:DUAMCO

98 A30808-X3247-L291-3-7620


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 ofthe BTSE, there by preventing a download of a swLoad which will not run on the specificBTSE.

This check is done by means of a compatibility matrix - the Version Attachment Mecha-nism (VAM) file which is the second file of the swLoad. The check is carried out whenthis VAM file is received in the BTSE. Upon a negative result, the download of the swIm-ages is stopped.

swLoad : GSM notation for a complete SW package containing all the load SW of a net-work element.

swImage : GSM notation for the load SW package for a single module inside a networkelement.

VAM file : represents the context between the swImages and the HW-SW compatibility.

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”,OVER-

WRITE=YESSW RELEASE: <no>COMMAND RESULT: OPERATION FAILED

VAM check failed


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:0Event Type = Processing Failure Event

A30808-X3247-L291-3-7620 99



5.2 Safeguarding

Routine Test

In the BTSE concept, the SW subsystem Alarm & Error handling (AE) and Fault Pro-tection (FP) provide the required fault tolerance functionality.In general, the detection and treatment of faults / errors occurring during normal systemoperation is subject to the AE subsystem. This is contrary to the detection and handlingof 'sleeping' latent faults which have not yet disturbed the BTSE normal operation at thetime they are detected.

The main tasks of AE are:

– Fault detection and verification measures which can only be performed from a cen-tral position in the BTSE.

– Initiating deactivation of the BTSE's least replaceable units (LRU) and initiatingstate changes of the BTSE physical and functional objects.

– Generation of failure event reports, filtered, stored and forwarded to the BSC and /orto the BTSE-LMT.

This kind of supervision is achieved using:

– audits performed on the BTSE code and data

– communication supervision to detect the loss of peripheral processors.

Faults and errors detected by the FP subsystem are reported to the AE in charge of han-dling these faults or errors.

5.3 State/Status Attributes of BTSE Managed Objects

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

Event Time = <Date> <Time>Probable Cause = Configuration or Customization ErrorSpecific Problems = 26676 - Board type not supportedSeverity = WarningTrend Indication = No ChangeNotification Identifier = 48Proposed Repair Action 1 = 189 - Check configuration dataOriginator = 3329Additional Words =Octets 01 to 16: H’6264 H’6c78 H’636d H’6d73 H’07ac H’5a01 H’0212 H’3b3bOctets 17 to 30: H’c304 H’ffff H’ffff H’ffff H’ffff H’ffff H’ffffSoftware Version = <SW Version>


The main task of FP is:− Supervision of BTSE hardware and software controlled by processes running in

the background on a time triggered (periodical) non-permanent basis.

100 A30808-X3247-L291-3-7620


State/Status Attribute State/Status Explanation

Administrative State (AST) This state informs whether or not the MO is permitted toprovide service.

Locked The related MO is not permitted to provide service, butis addressable for maintenance tasks and fully operable(it can, for example, be tested). This state can bebrought 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 arenot interrupted, but no new calls are permitted.This state cannot be brought about via LMT at the BT-SE.

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 pro-vide 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 servicerack is not installed.)

Disabled (dis) The MO is not able to provide service.

Alarm Status (ALS) This status reports the severity level of pending alarms.If more than one alarm is pending, the level of the alarmwith the highest severity level is reported.

Critical At least one pending alarm with severity level “critical”(see 5.4.3.1).

Major At least one pending alarm with severity level “major”(see 5.4.3.2).

Minor At least one pending alarm with severity level “minor”(see 5.4.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.

Tab. 5.1 State/Status Attributes of BTSE MOs

A30808-X3247-L291-3-7620 101



5.4 BTSE Alarm Information

The following information is forwarded from the BTSE to the BSC :

1. Managed object class

2. Managed object instance

3. Event information

– event type

– probable cause

– severity (alarm level)

– trend indication

– immediate defence action

– threshold information

– proposed repair action

– error description

– additional information

5.4.1 Event Type

The event type corresponds to the detected fault/error.

Dependency (Dep) The MO cannot operate because of another MO onwhich 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 aninitialization procedure.

Initialising (ini) Initialization is in progress.

Null Value (nul) No initialization

Standby Status (STS) 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 “En-abled”/AST “Unlocked”. The MO provides service.

Cold Standby The MO is able to provide service but it is either not ac-tive or it is locked.

State/Status Attribute State/Status Explanation

Tab. 5.1 State/Status Attributes of BTSE MOs

102 A30808-X3247-L291-3-7620


5.4.2 Probable Cause

Identifies the probable cause of the fault or error. The probable cause is taken out of apredefined set of values defined for each alarm type.All the possible error types are classified in the following types:

5.4.2.1 Equipment Errors- detected by hardware check or application software

5.4.2.2 Processing Errors- detected by on-line software checks and audits

5.4.2.3 Communication Errors- detected by protocols

5.4.2.4 Quality of Service ErrorsThey depend on:

– Traffic overload conditions

– Excessive instability of the hardware

– Loss of hardware components

5.4.2.5 Environmental ErrorsThese errors depend on environmental conditions e.g. temperature, door open orsmoke.In general, these faults are signalled to the ACT module.

5.4.3 Severity Levels

5.4.3.1 CriticalThe critical severity level indicates that a service affecting condition has occurred andan immediate corrective action is required. Such a severity can be reported, for exam-ple, when an equipment related managed object (MO) becomes totally out of service.

5.4.3.2 MajorThe major severity level indicates that a service affecting condition has developed andan 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 managedobject (MO).

A30808-X3247-L291-3-7620 103



5.4.3.3 MinorThe minor severity level indicates the existence of a non-service affecting fault conditionand that corrective action should be taken in order to prevent a more serious (for exam-ple, service affecting) fault. Such a severity can be reported, for example, when the de-tected alarm condition is not currently degrading the capacity of the equipment relatedmanaged objects (MO).

5.4.3.4 WarningThe warning severity level indicates the detection of a potential or impending service af-fecting fault, before any significant effects have been felt. Actions should be taken to fur-ther diagnose (if necessary) and correct the problem in order to prevent it from becominga fault causing more severe interference to services.

5.4.4 Trend Indication

This parameter specifies the current severity trend of the equipment related managedobject.

5.4.5 Immediate Defence Action

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

5.4.6 Threshold Information

5.4.7 Proposed Repair Action

The Proposed Repair Action parameter suggests a solution to the operator to repair theproblem reported in the Failure Event Report.

5.4.8 Error Description

Detailed description of the error and its probable cause.

5.4.9 Additional Information

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

Actual value: lower threshold (if any)upper threshold (if any)

104 A30808-X3247-L291-3-7620


5.5 Fault Messages

5.5.1 Fault Messages at the Radio Commander

Fig. 5.1 Fault Messages at the Radio Commander

A30808-X3247-L291-3-7620 105



5.5.2 Fault Messages at the LMT

JOB: <no>

PC Time&Date: <Time> <Date>

NE Time&Date: <Time> <Date>

USER NAME: <Name>

SW RELEASE:<Release>

COMMAND RSULT: OPERATION COMPLETED

FAILURE EVENT REPORT:

NAME = RACK:0/FANP:1

Event Type = Environtmental Failure Event

Event Time = <Date> <Time>

Probable Cause = Fan Faillure

Specific Problems = 53278 - FANP: unit failed

Severity = Minor

Trend Indication = More Severe

Notification Identifier = 9

Proposed Repair Actions_1 = 181 - Test the addressed module(s)

Proposed Repair Actions_2 = 184 - Check the corresponding cables / connections,

consult the corresponding maintenance manual for details.

Originator = 5889

Additional Word =

Octets 01 to 16: H’6d63 H’6e61, H’6c72, H’6d66 H’0720 H’0100 H’0000

Octets 17 to 30: H'ffff H'ffff H'ffff H'ffff H'ffff

Software Version = <Version>


5.6 BTSE Components

5.6.1 BTSE Components Overview

For a system overview of all BTSE components (modules, frames, racks and managedobjects), refer to chapter 4 "Tables, lists and figures".

5.6.2 Numbering of BTSE Components

5.6.2.1 General Rules

Relative Numbering

In general, the relative numbering (i.e. logical numbering) of the units starts at zero (0).The first of a set of devices, modules or racks / shelters gets the number 0, the next onethe number 1 in sequence, etc.

With Abis-lines, the numbering starts with 1, 2, 3 ...

106 A30808-X3247-L291-3-7620


Slot-ID

For electrical coding each module equipped with a Bus1 Access Circuit (BAC) and a Preads a slot-ID number, supplied from the backplane by connector pins with a fixed log-ical level for a particular mounting location.

Mounting Location

A unique number is assigned to every mounting location in which a unit can be inserted,irrespective of whether a unit is equipped with a microprocessor or not. This number isrequired for installation, O&M and service purposes.

5.6.2.2 Specific Rules

Rack / Shelter Numbering

The main shelter in a BS-82 eMicro is called the Master Cabinet and gets the number0. One additional shelter can be connected to the Master Cabinet, it is called ExtensionCabinet and gets number 1.

A cabinet is defined to be a Master Cabinet by insertion of a COBAM module.

Slot Numbering inside Shelters

In shelter, slot numbers are defined for accommodation of DCUs. Each DCU contains 2CUs. There are 2 DCU slots (0, 1). The HMOs CU are numbered as shown in ITMNBS-82 eMicro.

The Figure Fig. 4.4 shows as an example the arrangement of a BS-82 eMicro with onemaster cabinet and one extension cabinet.

Add-on modules

On the top of each BS-82 eMicro add-on modules can be installed.

5.6.3 Remote Inventory Data

The “Remote Inventory” function of the Siemens Basestation System performs electron-ic, non volatile storing of the complete, individual product identification data (PID) ofeach inventory object. Modules that have its on board inventory data are called ob_RIUs(on-board Remote Inventory Units).

In order to include inventory data of objects without a non volatile storage (e. g., frames,racks, OEM components), the data of the nob_RIUs (not on-board Remote InventoryUnits) is entered into a inventory data table (IDT) via the LMT and supplemented with afooter and header to the inventory data file (IDF).

Shelter numbering Type of Shelter

0 Base shelter

1 Extension Shelter

Tab. 5.2 Shelter Numbering

iThis file is stored on the COBA and must be updated manually when replacing anob_RIU component.

A30808-X3247-L291-3-7620 107



For ob-RIU replacements, the file is automatically updated. The following list shows allnob_RIU components.

The backup file with the nob_RIUs, stored on site, has to be updated.

5.7 Diagnostics / Test

5.7.1 General

In general the diagnosis subsystem is for testing the functionality of BTSE HW resourc-es to detect and localize hardware faults. The verification of the functionality of a new orreplaced 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 fromthe LMT.

Replacement of analog modules can only be seen to have been successful by reactivat-ing the BTSE.

Functional Address Range of “m” Range of “n” Functional AddressType

AOVP 0 or 1 0 A:OVPxM

ATIF 0 0 A:TIFx

BATTERY-m/n 0 or 1 0 BATTERYM

DUX 0 or 1 0...1 A:DUXMEG

FAN 0 or 1 0 FANM

FEMICRO 0 or 1 0 F:EMICRO

HEATER 0 or 1 0 HEATERM

INTENNA 0 or 1 0 INTENNAx

MKEMICRO 0 or 1 0 MK:EMICRO

MKLPDUCT 0 or 1 0 MK:LPDUCTM

MKWP 0 or 1 0 MK:WPxM

OVPT 0 0 M:OVPTxM

RACK 0 or 1 0 SH:EMICRO

RACKADD 0 or 1 0...3 SH:EMICRO-A

TIF 0 0 M:TIFx

SH:EMICRO-B 0 0 SH:EMICRO-B

Note: column “m”: 0 = valid for base rack, 1 = valid for extension rack

Tab. 5.3 List of nob_RIUs

108 A30808-X3247-L291-3-7620


5.7.2 Requirements for Starting the BTSE Module Test

The module test is controlled by the LMT. It is therefore necessary that the LMT isplugged in at the plug position and that it is logged in. The principle sequence is as fol-lows:

– 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.7.2.1 Lock BTS Site Manager (only valid for some modules - seeREP:XXX)MANAGED-ELEMENTBSS-FUNCTIONALBTSMLOCK BTSMNAME=BTSM:0

LOCK BTSM:NAME=BTSM:0;

5.7.2.2 Change BTSE from Phase 3 to Phase 2 (only valid for some mod-ules)see OGL:LMT

MANAGED-ELEMENTBSS-FUNCTIONALBTSMDISCBSC BTSMNAME=BTSM:0

DISCBSC BTSM:NAME=BTSM:0;

5.7.2.3 Lock Suspected Module (all modules)MAMAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACK<module>LOCK <module>

LOCK <module>:NAME=RACK:<no>/<module>:<no>;

5.7.2.4 Run Test for Replaced ModuleMANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACK<module>PERFTEST <module>

A30808-X3247-L291-3-7620 109



PERFTEST <module>:NAME=RACK:<no>/<module>:<no>;

Explanation of the test parameters:

Refer to the manual “CML:BS-82 eMicro”.

System Response

Example for Test Result

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

PERFTEST ACK BTSE:

name = BTSETEST:<no>MOT = RACK:<no>/<module>:<no>tO = BTSETEST:1


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

Test Report:name = BTSE:<no>testOutcome = <test outcome> (see below)testTermination = NormalMOT = RACK:<no>/<module>:<no>

followed by some more information in case of “Test Outcome = Fail”, such as:Proposed Repair Action

Card 1: ....Card 2: ....Card 3: ....Card 4: ....

Failed Phases = <no>

110 A30808-X3247-L291-3-7620


5.7.2.5 Unlock Suspected Module (all Modules)MANAGED-ELEMENTBSS-EQUIPMENTBTSEEMRACK<module>UNLOCK <module>

UNLOCK <module>:NAME=RACK:<no>/<module>:<no>;

Additional WordsSome tests have been skippedFailed Phases: Start_PhaseOther Information = H’01 H’00 H’00 H’00 H’00 H’00 H’00 H’00

A30808-X3247-L291-3-7620 111



6 AbbreviationsAC/DC AC/DC Converter

AE Alarm & Error Handling

BSS Base Station Subsystem

BTS Base Transceiver Station

BTSE Base Transceiver Station Equipment

CAN Controller Area Network

COBA Core Basis

CU Carrier Unit ,DILNA Diversitiy Low Noise Amplifier

DUKIT Duplex Combiner Kit

DULNA Duplexer Low Noise Amplifier

ESD Electrostatically Sensitive Device

FP Fault Protection

HMO Hardware Related Managed Object

HW Hardware

IDF Inventory Data File

IDT Inventory Data Table

LED Light Emitting Diode

LMT Local Maintenance Terminal

LRU Least Replaceable Unit

MO Managed Object

MO Managed Object (e.g. functional part of amodule)

MOT Managed Object Under Test

n no

NOB nob_RIUs only

nob_RIU not on-board Remote Inventory Data

NT Network Termination

NTPM Network Termination Primary Access Multi-plex

ob_RIU on-board Remote Inventory Data

OMC Operation and Maintenance Center

PID Product Identification Data

SBS Siemens Base Station

SW Software

TAC Technical Assistance Center

TMA Tower Mounted Amplifier

VAM Version Attachment Mechanism

VSWR Voltage Standing Wave Ratio

y yes

Date post:	14-Dec-2015
Category:	Documents
Upload:	sinasabikona
View:	9 times
Download:	2 times

bs82mt

Documents